diff --git a/marked/Rel-11/23_series/23042/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg b/marked/Rel-11/23_series/23042/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af14d6ddb278203d6d4994e274e40ff4ee24baa9 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23042/raw.md b/marked/Rel-11/23_series/23042/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..83afe526f57bb04ea5e2cecd1ab556b851e85297 --- /dev/null +++ b/marked/Rel-11/23_series/23042/raw.md @@ -0,0 +1,2268 @@ + + + + + + +# 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 | PUunctuator 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 'Node 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 'Node f=6' (right). 'Node f=6' branches into 'Node f=2' (left) and 'Node f=4' (right). 'Node f=2' branches into 'Node f=1' (left) and 'Node f=1' (right). 'Node f=20' branches into 'Node f=10' (left) and 'Node f=10' (right). Leaf nodes are labeled with characters: 'Z' (f=1), 'W' (f=1), 'T' (f=4), 'R' (f=6), 'A' (f=10), 'O' (f=10), and 'E' (f=40).](5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg) + +``` + +graph TD + Root["Root Node f=72"] --> N32["Node f=32"] + Root --> N40["Node f=40"] + N32 --> N12["Node f=12"] + N32 --> N20["Node f=20"] + N12 --> N6L["Node f=6"] + N12 --> N6R["Node f=6"] + N6L --> N2["Node f=2"] + N6L --> N4["Node f=4"] + N2 --> N1L["Node f=1"] + N2 --> N1R["Node f=1"] + N20 --> N10L["Node f=10"] + N20 --> N10R["Node f=10"] + N1L --- Z["Z f=1"] + N1R --- W["W f=1"] + N4 --- T["T f=4"] + N6R --- R["R f=6"] + N10L --- A["A f=10"] + N10R --- O["O f=10"] + N40 --- E["E f=40"] + +``` + +Figure 1: Character frequency distribution tree diagram. The root node is 'Root Node f=72'. It branches into 'Node f=32' (left) and 'Node 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 'Node f=6' (right). 'Node f=6' branches into 'Node f=2' (left) and 'Node f=4' (right). 'Node f=2' branches into 'Node f=1' (left) and 'Node f=1' (right). 'Node f=20' branches into 'Node f=10' (left) and 'Node f=10' (right). Leaf nodes are labeled with characters: 'Z' (f=1), 'W' (f=1), 'T' (f=4), 'R' (f=6), 'A' (f=10), 'O' (f=10), and 'E' (f=40). + +**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:

| + +### 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 what whereby 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:
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:
| +| Step 7 | If the input symbol is the last symbol to be encoded:
| +| 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 is 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) Punctuation ID | 0 (decimal) | +| 4) Keyword Dictionary ID | 0 (decimal) | +| 5) Character Group ID | 0 (decimal) | +| 6) Huffman Initialization ID | 0 (decimal) | + +## --- R.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 >0 (decimal)** + +No other punctuations 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 | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23072/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-11/23_series/23072/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a576fd6842036d2f6c5c43f676ec738f27af9c71 --- /dev/null +++ b/marked/Rel-11/23_series/23072/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9beb905193fb45d0b75e680885c4dd78c0c147e8eaa8a92601708f771b30a227 +size 139121 diff --git a/marked/Rel-11/23_series/23072/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-11/23_series/23072/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa42606a2938029ff428b5afd3c31df474f112c9 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23072/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/marked/Rel-11/23_series/23072/2eb23c2210154279f8013a1594fbcc5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f4291886590521225b2ae9ccd78cec81bdedcf6 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23072/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/Rel-11/23_series/23072/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c8bd8504505e3f8b55686317a8dbf118fa334f0 --- /dev/null +++ b/marked/Rel-11/23_series/23072/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24228757c87365eae03d468042d1d1bebf4716e627cc3b21c37d0746486119a4 +size 18659 diff --git a/marked/Rel-11/23_series/23072/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-11/23_series/23072/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d9ba41eb80f469c2390348ed86f04f5a15038c8 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23072/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/23_series/23072/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8acb21f78fa24dd3a9f10989bb4153fd8730a81 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23072/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-11/23_series/23072/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06e28468595062d61494839580b93c2195741758 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23072/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-11/23_series/23072/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d28dc4cd1b3342542ae4ed63a97f0cf126b551d8 --- /dev/null +++ b/marked/Rel-11/23_series/23072/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b2312289c98709c0f7a94577ea3e1f30901f528692976e5f795db256e2853b9 +size 65154 diff --git a/marked/Rel-11/23_series/23072/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-11/23_series/23072/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75b83ea850b7ad3b576dbed2574ca51015132006 --- /dev/null +++ b/marked/Rel-11/23_series/23072/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9642877cc09e9bf374f203f385e58b600a273e4c362d116e49c2c19032cec66 +size 104033 diff --git a/marked/Rel-11/23_series/23072/f6d72d7c790e7f585532140f3971639a_img.jpg b/marked/Rel-11/23_series/23072/f6d72d7c790e7f585532140f3971639a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c7a7bd9976c006acd74bdd361b8bbf4fdd68ec0 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23072/raw.md b/marked/Rel-11/23_series/23072/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9c5ab9e932c8759db18d20eb0e7805a944198001 --- /dev/null +++ b/marked/Rel-11/23_series/23072/raw.md @@ -0,0 +1,587 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 Normative references ..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Abbreviations ..... | 5 | +| 4 Information flow ..... | 6 | +| 5 Messages and their Contents..... | 6 | +| 5.1 Messages between the MS and the MSC ..... | 6 | +| 5.1.1 CD Request..... | 6 | +| 5.1.2 CD Request ack ..... | 7 | +| 5.1.3 CD Request negative response ..... | 7 | +| 5.2 Messages between the MSC and the VLR..... | 7 | +| 5.2.1 Process Call Waiting negative response..... | 7 | +| 5.2.2 Complete Call negative response ..... | 7 | +| 5.2.3 Send Info for Incoming Call negative response ..... | 8 | +| 6 Functions of the serving MSC ..... | 8 | +| 6.1 Procedure Handling_CD_MSC..... | 8 | +| 6.2 Procedure CD_Reject..... | 8 | +| 6.3 Procedure CD_Failure..... | 8 | +| 6.4 Procedure CD_UUS_Interaction..... | 8 | +| 6.5 Procedure CD_Success ..... | 8 | +| 6.6 Procedure CD_Notify_SS_Invocation ..... | 8 | +| 7 Functions of the serving VLR..... | 15 | +| 7.1 Procedure CD_Authorization..... | 15 | +| 7.2 Procedure CAMEL_Check_CD_Interaction..... | 15 | +| 8 Interaction with other supplementary services..... | 18 | +| 8.1 Line Identification services ..... | 18 | +| 8.2 Call Forwarding services..... | 18 | +| 8.3 Call Waiting ..... | 18 | +| 8.4 Call Hold ..... | 18 | +| 8.5 Multi Party (MPTY)..... | 18 | +| 8.6 Closed User Group ..... | 18 | +| 8.7 Advice of Charge (AoC)..... | 18 | +| 8.8 Call Barring Services ..... | 18 | +| 8.9 Explicit call transfer (ECT)..... | 18 | +| 8.10 Completion of Calls to Busy Subscriber (CCBS)..... | 18 | +| 9 Interaction with other network features ..... | 19 | +| 9.1 Customised Applications for Mobile network Enhanced Logic (CAMEL) ..... | 19 | +| 9.2 Support of Optimal Routeing ..... | 19 | +| 10 Information stored in the HLR..... | 19 | +| 11 State transition model..... | 20 | +| 12 Transfer of information from HLR to VLR..... | 20 | +| 13 Information stored in the VLR..... | 20 | +| 14 Handover..... | 20 | +| Annex A (informative): Change history..... | 21 | + +# --- Foreword + +This Technical Specification has been produced by the 3GPP. + +This specification describes the technical realization of the Call Deflection supplementary service within the 3GPP system. + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version 3.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 Indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the specification; + +# --- 1 Scope + +This Technical Specification gives the stage 2 description of the Call Deflection supplementary service. + +# --- 2 Normative references + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TR 21.905: "3GPP Vocabulary". +- [2] 3GPP TS 23.011: "Technical realization of supplementary services". +- [3] 3GPP TS 23.018: "Basic call handling; Technical realization". +- [4] 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 2; Stage 2" +- [5] 3GPP TS 23.079: "Support of Optimal Routeing (SOR); Technical realisation" +- [6] 3GPP TS 23.081: "Line identification supplementary services - Stage 2". +- [7] 3GPP TS 23.085: "Closed User Group (CUG) supplementary services - Stage 2". +- [8] 3GPP TS 23.091: "Explicit Call Transfer (ECT) supplementary service - Stage 2". +- [9] 3GPP TS 23.093: "Technical Realisation of Completion of Calls to Busy Subscriber (CCBS)". + +# --- 3 Definitions and abbreviations + +## 3.1 Abbreviations + +Abbreviations used in this specification are listed in TR 21.905. + +For the purpose of this specification the following abbreviations apply: + +CD: Call Deflection + +# 4 Information flow + +![Flowchart for Call Deflection authorization procedure. It starts with a decision 'neg. resp. = CD?'. If No, Result := Abort. If Yes, GAMEL_CHECK_SII2_CDTI is called (See TS 23.078). Then 'Result = Pass?' is checked. If No, CD provisioned? is checked. If No, Number of max diversions reached? is checked. If Yes, BAOC A&O is checked. If No, GAMEL_Check_CD_Interaction is called. Then 'Result = Pass?' is checked. If No, DTN valid? is checked. If Yes, DTN is a special service code? is checked. If Yes, set negative resp: DTN is a special service code. If No, DTN is own basic MSISDN is checked. If Yes, set negative resp: DTN is own number. If No, set negative resp: number invalid. All negative response boxes lead to Result := Fail. If Result = Pass? at any point, the flow proceeds to connector 2.](f6d72d7c790e7f585532140f3971639a_img.jpg) + +Procedure CD\_Authorization 1(1) + +Call Deflection related authorization + +DTN: Deflected-To Number +BAOC: Barring of All Outgoing Calls +A&O: Active and Operative + +``` + +graph TD + Start([ ]) --> D1{neg. resp. = CD?} + D1 -- No --> R1[Result := Abort] + R1 --> E1(( )) + D1 -- Yes --> G1[GAMEL_CHECK_SII2_CDTI] + G1 -.-> S1[See TS 23.078] + G1 --> D2{Result = Pass?} + D2 -- No --> D3{CD provisioned?} + D3 -- No --> D4{Number of max diversions reached?} + D4 -- Yes --> D5{BAOC A&O} + D5 -- Yes --> R2[set negative resp: call barred] + D5 -- No --> G2[GAMEL_Check_CD_Interaction] + G2 --> D6{Result = Pass?} + D6 -- No --> D7{DTN valid?} + D7 -- Yes --> D8{DTN is a special service code?} + D8 -- Yes --> R3[set negative resp: DTN is a special service code] + D8 -- No --> D9{DTN is own basic MSISDN} + D9 -- Yes --> R4[set negative resp: DTN is own number] + D9 -- No --> R5[set negative resp: number invalid] + R3 --> R6[Result := Fail] + R4 --> R6 + R5 --> R6 + R6 --> E2(( )) + D2 -- Yes --> C2((2)) + D3 -- Yes --> C2 + D4 -- No --> C2 + D5 -- No --> C2 + D6 -- Yes --> C2 + D7 -- No --> C2 + D8 -- No --> C2 + D9 -- No --> C2 + +``` + +Flowchart for Call Deflection authorization procedure. It starts with a decision 'neg. resp. = CD?'. If No, Result := Abort. If Yes, GAMEL\_CHECK\_SII2\_CDTI is called (See TS 23.078). Then 'Result = Pass?' is checked. If No, CD provisioned? is checked. If No, Number of max diversions reached? is checked. If Yes, BAOC A&O is checked. If No, GAMEL\_Check\_CD\_Interaction is called. Then 'Result = Pass?' is checked. If No, DTN valid? is checked. If Yes, DTN is a special service code? is checked. If Yes, set negative resp: DTN is a special service code. If No, DTN is own basic MSISDN is checked. If Yes, set negative resp: DTN is own number. If No, set negative resp: number invalid. All negative response boxes lead to Result := Fail. If Result = Pass? at any point, the flow proceeds to connector 2. + +Figure 4.1: Information flow for Call Deflection + +# 5 Messages and their Contents + +## 5.1 Messages between the MS and the MSC + +### 5.1.1 CD Request + +The CD Request message is sent from the MS to MSC direction. + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------------------------------------------------------------------------------------| +| Deflected-to number | M | Number of the C subscriber as entered by the served subscriber. | +| Deflected-to subaddress | C | Subaddress of the C subscriber; shall be present if it was entered by the served subscriber; otherwise shall be absent | + +### 5.1.2 CD Request ack + +The CD Request ack message is sent from the MSC to MS direction. This message contains no information elements. + +### 5.1.3 CD Request negative response + +CD Request negative response message is sent from the MSC to MS direction. The negative response information element can take the following values: + +- service not subscribed; +- deflected-to number is own number; +- deflected-to number is a special service code; +- number invalid; +- call barred; +- SS incompatibility; +- forwarding violation; +- forwarding failure. + +## 5.2 Messages between the MSC and the VLR + +### 5.2.1 Process Call Waiting negative response + +For the description of the Process Call Waiting negative response message refer to TS 23.018. The negative response information element can take the following additional value: + +- Call Deflection. + +**For the purpose of the CD supplementary service the following additional information elements for the Process Call Waiting negative response message are required.** + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------------------------------------------------------------------------------------| +| Deflected-to number | M | Number of the C subscriber as entered by the served subscriber. | +| Deflected-to subaddress | C | Subaddress of the C subscriber; shall be present if it was entered by the served subscriber; otherwise shall be absent | + +### 5.2.2 Complete Call negative response + +For the description of the Complete Call negative response message refer to TS 23.018. The negative response information element can take the following additional value: + +- Call Deflection. + +**For the purpose of the CD supplementary service the following additional information elements for the Complete Call negative response message are required.** + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------------------------------------------------------------------------------------| +| Deflected-to number | M | Number of the C subscriber as entered by the served subscriber. | +| Deflected-to subaddress | C | Subaddress of the C subscriber; shall be present if it was entered by the served subscriber; otherwise shall be absent | + +### 5.2.3 Send Info for Incoming Call negative response + +For the description of the Send Info for Incoming Call negative response message refer to TS 23.018. The negative response information element can take the following additional values: + +- service not subscribed; +- deflected-to number is own number; +- deflected-to number is a special service code; + +- number invalid; +- call barred. + +# --- 6 Functions of the serving MSC + +The functions of the serving MSC are specified in TS 23.018. The procedures specific to the CD supplementary service are specified in this subclause. + +## 6.1 Procedure Handling\_CD\_MSC + +This procedure is called when a CD request is received from the MS. + +## 6.2 Procedure CD\_Reject + +This procedure is called if the CD request was treated unsuccessful in the VLR. + +## 6.3 Procedure CD\_Failure + +This procedure is called if the CD request was treated unsuccessful in the serving MSC. + +## 6.4 Procedure CD\_UUS\_Interaction + +This procedure is called if the CD request was treated unsuccessful in the serving MSC due to the interaction with the UUS supplementary service. + +## 6.5 Procedure CD\_Success + +This procedure is called if the CD request was treated successful in the serving MSC. + +## 6.6 Procedure CD\_Notify\_SS\_Invocation + +This procedure is called by the procedures CD\_OR\_Clear and CD\_Success to send notification of the CD invocation to the gsmSCF if required. + +The output signal SS Invocation Notify is sent if the SS-CSI was received in the SIFIC ack. The SS-CSI will only be included in the SIFIC ack if there is a requirement to notify the gsmSCF that CD has been invoked. + +![Flowchart for Procedure CAMEL_Check_CD_Interaction. It starts with a connector symbol, followed by a decision diamond 'TIF-CSI provided'. If 'No', it goes to 'Result:= Fail'. If 'Yes', it goes to 'Result:= Pass'. Both results lead to a merge point and then to an exit connector symbol.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +### Procedure CAMEL\_Check\_CD\_Interaction + +1(1) + +Procedure in the VLR to Check the Provision of TIF\_CSI + +``` +graph TD; Start([ ]) --> Decision{TIF-CSI provided}; Decision -- No --> Fail[Result:= Fail]; Decision -- Yes --> Pass[Result:= Pass]; Fail --> Merge(( )); Pass --> Merge; Merge --> End((X)) +``` + +Flowchart for Procedure CAMEL\_Check\_CD\_Interaction. It starts with a connector symbol, followed by a decision diamond 'TIF-CSI provided'. If 'No', it goes to 'Result:= Fail'. If 'Yes', it goes to 'Result:= Pass'. Both results lead to a merge point and then to an exit connector symbol. + +Figure 6.1: Procedure Handling\_CD\_MSC + +![A state transition diagram with two circular states. The left state contains the text '(Not Provisioned, Not Applicable, Not Active, Not Induced)'. The right state contains the text '(Provisioned, Not Applicable, Active and Operative, Not Induced)'. A curved arrow labeled 'Provision' points from the left state to the right state. A curved arrow labeled 'Withdrawal' points from the right state to the left state.](e6df2733626a85205c1db682e6259c46_img.jpg) + +**Provision** + +**(Not Provisioned, +Not Applicable, +Not Active, +Not Induced)** + +**(Provisioned, +Not Applicable, +Active and Operative, +Not Induced)** + +**Withdrawal** + +A state transition diagram with two circular states. The left state contains the text '(Not Provisioned, Not Applicable, Not Active, Not Induced)'. The right state contains the text '(Provisioned, Not Applicable, Active and Operative, Not Induced)'. A curved arrow labeled 'Provision' points from the left state to the right state. A curved arrow labeled 'Withdrawal' points from the right state to the left state. + +Figure 6.2: Procedure CD\_Reject + +![Flowchart for Procedure CD_Failure. It starts with a connector symbol, followed by a decision 'CD in progress'. If 'No', it goes to an exit connector. If 'Yes', it proceeds to 'Set negative response: forwarding failure', then 'CD Request negative response', then 'Release transaction', and finally to an exit connector.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +### Procedure CD\_Failure + +1(1) + +Procedure in the MSC to handle Call Deflection after unsuccessful invocation + +Signals to/from the left are to/from the BSS + +``` +graph TD; Start([ ]) --> CD{CD in progress}; CD -- No --> Exit((X)); CD -- Yes --> Set[Set negative response: forwarding failure]; Set --> CDReq{CD Request negative response}; CDReq --> Release{Release transaction}; Release --> Exit; +``` + +Flowchart for Procedure CD\_Failure. It starts with a connector symbol, followed by a decision 'CD in progress'. If 'No', it goes to an exit connector. If 'Yes', it proceeds to 'Set negative response: forwarding failure', then 'CD Request negative response', then 'Release transaction', and finally to an exit connector. + +Figure 6.3: Procedure CD\_Failure + +![Flowchart for Procedure CD_UUS_Interaction](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +### Procedure CD\_UUS\_Interaction + +1(1) + +Procedure in the MSC to handle the interaction scenario with UUS + +Signals to/from the left are to/from the BSS + +``` +graph TD; Start([ ]) --> Step1[Set negative response: SS incompatibility]; Step1 --> Step2{CD Request negative response}; Step2 --> Step3{Release transaction}; Step3 --> End((X)); +``` + +The flowchart illustrates the procedure for CD\_UUS\_Interaction. It begins with a start symbol (oval), followed by a process block 'Set negative response: SS incompatibility'. This is followed by a decision block 'CD Request negative response', which leads to another decision block 'Release transaction'. The process concludes with an end symbol (circle with an X). + +Flowchart for Procedure CD\_UUS\_Interaction + +Figure 6.4: Procedure CD\_UUS\_Interaction + +### Procedure CD\_Success + +1(1) + +Procedure in the MSC to handle +CD after successful invocation + +Signals to/from the left +are to/from the BSS + +![Flowchart for Procedure CD_Success](3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg) + +``` +graph TD; Start([ ]) --> Decision{CD in progress}; Decision -- No --> End(( )); Decision -- Yes --> Process[CD_Notify_SS_Invocation]; Process --> Decision2{CD Request ack}; Decision2 --> Decision3{Release transaction}; Decision3 --> End; +``` + +The flowchart illustrates the 'Procedure CD\_Success'. It begins with a start symbol (oval with a vertical line), leading to a decision diamond labeled 'CD in progress'. If the answer is 'No', the flow proceeds to an end symbol (circle with an 'X'). If the answer is 'Yes', the flow proceeds to a process box labeled 'CD\_Notify\_SS\_Invocation'. This is followed by a decision diamond labeled 'CD Request ack', which then leads to another decision diamond labeled 'Release transaction'. Both decision diamonds lead to the same end symbol. + +Flowchart for Procedure CD\_Success + +Figure 6.5: Procedure CD\_Success + +![Flowchart for Procedure CD_Notify_SS_Invocation. It starts with a connector symbol, followed by a decision diamond 'SS-CSI received in SIFIC ack?'. If 'Yes', it goes to a process box 'SS Invocation Notify'. If 'No', it goes to an exit connector symbol.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +### Procedure CD\_Notify\_SS\_Invocation + +1(1) + +Procedure in the MSC to notify the gsmSCF of the CD invocation. + +Signals to/from the left are to/from the gsmSCF. + +``` +graph TD; Start([ ]) --> Decision{SS-CSI received in SIFIC ack?}; Decision -- Yes --> Process[SS Invocation Notify]; Decision -- No --> End((X)); +``` + +Flowchart for Procedure CD\_Notify\_SS\_Invocation. It starts with a connector symbol, followed by a decision diamond 'SS-CSI received in SIFIC ack?'. If 'Yes', it goes to a process box 'SS Invocation Notify'. If 'No', it goes to an exit connector symbol. + +Figure 6.6 Procedure CD\_Notify\_SS\_Invocation + +# --- 7 Functions of the serving VLR + +The functions of the serving VLR are specified in TS 23.018. The procedure specific to the CD supplementary service is specified in this subclause. + +## 7.1 Procedure CD\_Authorization + +This procedure examines the authorization related to Call Deflection. + +The procedure CAMEL\_Check\_CD\_Interaction is specific to CAMEL phase 2. If CAMEL phase 2 is not supported in the VLR, processing continues from the "No" exit of the test "Result=Pass?". + +The procedure CAMEL\_CHECK\_SII2\_CDTI is specific to CAMEL Phase 3 or higher. If CAMEL Phase 3 or higher is not supported in the VLR, processing continues from the "Yes" exit of the test "Result = Pass?". + +## 7.2 Procedure CAMEL\_Check\_CD\_Interaction + +This procedure examines whether a Translation Interaction Flag (TIF-CSI) is provided for the served subscriber. + +![Flowchart for Procedure CD_Authorization. It starts with a decision 'neg. resp. = CD?'. If 'No', it sets 'Result := Abort' and ends. If 'Yes', it calls 'CAMEL_CHECK_SII2_CDTI' (refer to TS 23.078). This returns a 'Result = Pass?' decision. If 'No', it ends. If 'Yes', it checks 'CD provisioned?'. If 'No', it ends. If 'Yes', it checks 'Number of mac diversions reached?'. If 'Yes', it ends. If 'No', it checks 'BAOC A&O'. If 'Yes', it sets negative response 'call barred' and ends. If 'No', it calls 'CAMEL_Check_CD_Interaction'. This returns another 'Result = Pass?' decision. If 'Yes', it goes to connector '2'. If 'No', it checks 'DTN valid?'. If 'No', it sets negative response 'number invalid' and ends. If 'Yes', it checks 'DTN is a special service code?'. If 'Yes', it sets negative response 'DTN is a special service code' and ends. If 'No', it checks 'DTN is own basic MSISDN'. If 'Yes', it sets negative response 'DTN is own number' and ends. If 'No', it goes to connector '1'. All 'set negative resp:' blocks lead to 'Result := Fail' and then end.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +### Procedure CD\_Authorization + +1(1) + +Call Deflection related authorization + +DTN: Deflected-To Number +BAOC: Barring of All Outgoing Calls +A&O: Active and Operative + +``` +graph TD + Start([ ]) --> neg_resp_CD{neg. resp. = CD?} + neg_resp_CD -- No --> Abort[Result := Abort] + Abort --> End1(( )) + neg_resp_CD -- Yes --> CAMEL_CHECK_SII2_CDTI[CAMEL_CHECK_SII2_CDTI] + CAMEL_CHECK_SII2_CDTI --> Pass1{Result = Pass?} + Pass1 -- No --> End2(( )) + Pass1 -- Yes --> CD_provisioned{CD provisioned?} + CD_provisioned -- No --> End3(( )) + CD_provisioned -- Yes --> mac_diversions{Number of mac diversions reached?} + mac_diversions -- Yes --> End4(( )) + mac_diversions -- No --> BAOC_AO{BAOC A&O} + BAOC_AO -- Yes --> neg_resp_barred[set negative resp: call barred] + BAOC_AO -- No --> CAMEL_Check_CD_Interaction[CAMEL_Check_CD_Interaction] + neg_resp_barred --> Fail1[Result := Fail] + Fail1 --> End5(( )) + CAMEL_Check_CD_Interaction --> Pass2{Result = Pass?} + Pass2 -- Yes --> Connector2((2)) + Pass2 -- No --> DTN_valid{DTN valid?} + DTN_valid -- No --> neg_resp_invalid[set negative resp: number invalid] + DTN_valid -- Yes --> DTN_special{DTN is a special service code?} + DTN_special -- Yes --> neg_resp_special[set negative resp: DTN is a special service code] + DTN_special -- No --> DTN_own{DTN is own basic MSISDN} + DTN_own -- Yes --> neg_resp_own[set negative resp: DTN is own number] + DTN_own -- No --> Connector1((1)) + neg_resp_invalid --> Fail2[Result := Fail] + neg_resp_special --> Fail2 + neg_resp_own --> Fail2 + Fail2 --> End6(( )) +``` + +Flowchart for Procedure CD\_Authorization. It starts with a decision 'neg. resp. = CD?'. If 'No', it sets 'Result := Abort' and ends. If 'Yes', it calls 'CAMEL\_CHECK\_SII2\_CDTI' (refer to TS 23.078). This returns a 'Result = Pass?' decision. If 'No', it ends. If 'Yes', it checks 'CD provisioned?'. If 'No', it ends. If 'Yes', it checks 'Number of mac diversions reached?'. If 'Yes', it ends. If 'No', it checks 'BAOC A&O'. If 'Yes', it sets negative response 'call barred' and ends. If 'No', it calls 'CAMEL\_Check\_CD\_Interaction'. This returns another 'Result = Pass?' decision. If 'Yes', it goes to connector '2'. If 'No', it checks 'DTN valid?'. If 'No', it sets negative response 'number invalid' and ends. If 'Yes', it checks 'DTN is a special service code?'. If 'Yes', it sets negative response 'DTN is a special service code' and ends. If 'No', it checks 'DTN is own basic MSISDN'. If 'Yes', it sets negative response 'DTN is own number' and ends. If 'No', it goes to connector '1'. All 'set negative resp:' blocks lead to 'Result := Fail' and then end. + +Figure 7.1 (sheet 1): Procedure CD\_Authorization + +![Flowchart for Procedure CAMEL_Check_CD_Interaction. It starts with a connector symbol, leading to a decision diamond 'TIF_CSI provided'. If 'Yes', it goes to 'Result:= Pass'. If 'No', it goes to 'Result:= Fail'. Both results lead to a final connector symbol.](8307f6b04df072c9332f9987e034272c_img.jpg) + +### Procedure CAMEL\_Check\_CD\_Interaction + +1(1) + +Procedure in the VLR to +Check the Provision of TIF\_CSI + +``` +graph TD; Start([ ]) --> Decision{TIF_CSI provided}; Decision -- Yes --> Pass[Result:= Pass]; Decision -- No --> Fail[Result:= Fail]; Pass --> End(( )); Fail --> End +``` + +Flowchart for Procedure CAMEL\_Check\_CD\_Interaction. It starts with a connector symbol, leading to a decision diamond 'TIF\_CSI provided'. If 'Yes', it goes to 'Result:= Pass'. If 'No', it goes to 'Result:= Fail'. Both results lead to a final connector symbol. + +Figure 7.2: Procedure CAMEL\_Check\_CD\_Interaction + +# --- 8 Interaction with other supplementary services + +## 8.1 Line Identification services + +If the serving MSC receives an Answer message from the destination C network after the successful invocation of the call deflection supplementary service, the process MAF039 of TS 23.081 shall be performed. Refer to Process ICH\_MSC of TS 23.018 for further details. + +## 8.2 Call Forwarding services + +No impact. + +## 8.3 Call Waiting + +The MS may send a CD Request message for an incoming waiting call. Refer to procedure Process\_Call\_Waiting\_MSC of TS 23.018 for further details. + +## 8.4 Call Hold + +No impact. + +## 8.5 Multi Party (MPTY) + +No impact. + +## 8.6 Closed User Group + +The serving VLR shall perform the forwarding CUG authorisation as defined in TS 23.085 while processing a call deflection request. Refer to Process ICH\_VLR of TS 23.018 for details. + +## 8.7 Advice of Charge (AoC) + +No impact. + +## 8.8 Call Barring Services + +If a call deflection request is processed, the serving VLR shall check whether the requested deflected-to number contradicts active and operative outgoing barring programs. Refer to Procedure CD\_Authorization (figure 6.6) for details. + +## 8.9 Explicit call transfer (ECT) + +If in the originating network ECT is invoked (one call answered, the other alerting), the serving MSC shall map a redirection number parameter received in the ECT notification into the calling identity parameter of the outgoing IAM message. Refer to TS 23.091 (Interaction of Call Forwarding on mobile subscriber busy due to UDUB and explicit call transfer) for details. + +## 8.10 Completion of Calls to Busy Subscriber (CCBS) + +If a call is deflected to a NDUB destination, the serving MSC shall set the diagnostic to "CCBS not possible" when it releases the call towards the calling network. Refer to Process ICH\_MSC of TS 23.018 for further details. + +The serving MSC shall remove the CCBS call Indicator from the IAM message when deflecting a call. + +# --- 9 Interaction with other network features + +## 9.1 Customised Applications for Mobile network Enhanced Logic (CAMEL) + +If the served subscriber is provided with a Translation Information Flag (TIF-CSI) as defined in TS 23.018 the VLR shall neither perform checks regarding the validity of the deflected-to number nor perform interactions with BOIC and BOIC-exHC barring programs. Refer to Procedure CD\_Authorization for further details. + +## 9.2 Support of Optimal Routeing + +The procedures for optimal routeing of late call forwarding shall apply if the Call Deflection supplementary service is invoked. Refer to TS 23.079 for further details. + +# --- 10 Information stored in the HLR + +The following logical states are applicable for the Call Deflection service (refer to TS 23.011 for an explanation of the notation): + +| 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 + +| Change history | | | | | | | +|----------------|-----------|---------|-------|---------|-------------|----------------------------------------------------| +| TSG CN# | Spec | Version | CR | | New Version | Subject/Comment | +| Apr 1999 | GSM 03.72 | 7.0.0 | | | | Transferred to 3GPP CN1 | +| CN#03 | 23.072 | | | | 3.0.0 | Approved at CN#03 | +| CN#05 | 23.072 | 3.0.0 | 001 | | 3.1.0 | Approved at CN#05 | +| CN#05 | 23.072 | 3.0.0 | 003 | | 3.1.0 | Approved at CN#05 | +| CN#06 | 23.072 | 3.1.0 | 002r1 | | 3.2.0 | Approved at CN#06 | +| CN#09 | 23.072 | 3.2.0 | 004 | | 3.3.0 | Transfer of Procedure Check_CD_SII2 to TS 23.078 | +| CN#09 | 23.072 | 3.2.0 | 005 | | 3.3.0 | Handling of the Call Diversion Treatment Indicator | +| CN#11 | 23.072 | 3.3.0 | | Rel-4 | 4.0.0 | Release 4 after CN#11 | +| CN#16 | 23.072 | 4.0.0 | | Rel-4 | 4.0.1 | References updated | +| CN#16 | 23.072 | 4.0.1 | | Rel-5 | 5.0.0 | Release 5 after CN#16 | +| CN#26 | 23.072 | 5.0.0 | | Rel-6 | 6.0.0 | Release 6 after CN#26 | +| CT#36 | 23.072 | 6.0.0 | | Rel-7 | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 23.072 | 7.0.0 | | Rel-8 | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | - | 8.0.0 | - | Rel-9 | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | - | 9.0.0 | - | Rel-10 | 10.0.0 | Update to Rel-10 version (MCC) | +| 2012-09 | - | 10.0.0 | - | Rel-11 | 11.0.0 | Update to Rel-11 version (MCC) | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23081/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-11/23_series/23081/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..634c9141e7481a39d3624ebed999e23dac39a092 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23081/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-11/23_series/23081/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bb48438e73ec1dcfd63c6e77360eac59e7d43bf --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23081/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-11/23_series/23081/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ebfa7f1ba9c6d3d2976e6aeac351aca5c22211a --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23081/1dc5e74b1032f935e1b1ea3a9c876ac6_img.jpg b/marked/Rel-11/23_series/23081/1dc5e74b1032f935e1b1ea3a9c876ac6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..315040de0e7ef4eae1190ab696cb736dea4c1b9f --- /dev/null +++ b/marked/Rel-11/23_series/23081/1dc5e74b1032f935e1b1ea3a9c876ac6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ce88964bb60de3690d9f91ca1631802475e7c0fafeda448fe881118e28551b5 +size 22795 diff --git a/marked/Rel-11/23_series/23081/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-11/23_series/23081/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..608411a5a22ef7af329b156d9160795601328eeb --- /dev/null +++ b/marked/Rel-11/23_series/23081/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:890c6e77663b7d7d444420305f9fe752db3db6166ac0ad8b2a7fac3c946389a7 +size 97042 diff --git a/marked/Rel-11/23_series/23081/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-11/23_series/23081/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0814906a70c4a50b9ed24fca088d46f03fde834c --- /dev/null +++ b/marked/Rel-11/23_series/23081/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47789a0daeeaf27f75594d2813f4785abc7a9c9c7459132b3a80df588153fe1c +size 58979 diff --git a/marked/Rel-11/23_series/23081/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-11/23_series/23081/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adbb425f0a8fdfa0b25385b0a5eb34f782c67099 --- /dev/null +++ b/marked/Rel-11/23_series/23081/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87380f138f9f61f144a7e0655187ffb613e33810c1096bd9c005a19b2d915919 +size 32995 diff --git a/marked/Rel-11/23_series/23081/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-11/23_series/23081/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98bbbea0ccb23be7b59be63b8b9725302cf22ae6 --- /dev/null +++ b/marked/Rel-11/23_series/23081/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:badc1f8a0193796921c3d72dcabc198c9241038797d91288338381a112f298d6 +size 31315 diff --git a/marked/Rel-11/23_series/23081/392a79ccd95e682ccd08f35ab2e64144_img.jpg b/marked/Rel-11/23_series/23081/392a79ccd95e682ccd08f35ab2e64144_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8be6167f99b885612f92398b15ed058da01f490 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23081/40ef8b4d1d6b485e04c5edfeb6324b18_img.jpg b/marked/Rel-11/23_series/23081/40ef8b4d1d6b485e04c5edfeb6324b18_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21b41bbb8c647313cceda91a1e90ded67bf3914a --- /dev/null +++ b/marked/Rel-11/23_series/23081/40ef8b4d1d6b485e04c5edfeb6324b18_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b802558236a6d626f3b554d265e5dbf8cfc84168c4bdac39e091fecb8c79579b +size 31703 diff --git a/marked/Rel-11/23_series/23081/4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg b/marked/Rel-11/23_series/23081/4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07c0075b0518ac410818e581c2fff3ea71ebfd40 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23081/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Rel-11/23_series/23081/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3b7cf0bb561eeeb317e71600ef0b37336d2f016 --- /dev/null +++ b/marked/Rel-11/23_series/23081/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:093bfdb990044a3aa24d5b4bd94d9f112fac882e92541104f590d3c45694894a +size 40570 diff --git a/marked/Rel-11/23_series/23081/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-11/23_series/23081/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7d4a0bba3681569ff7ac38efca84ee6fedb7849 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23081/5fbb4f0de01736f1293333e599410c99_img.jpg b/marked/Rel-11/23_series/23081/5fbb4f0de01736f1293333e599410c99_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f3cefeeaf316c140df52ca0ea33bba2049c0427 --- /dev/null +++ b/marked/Rel-11/23_series/23081/5fbb4f0de01736f1293333e599410c99_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d8facac1a7a69c911973d22c1cb594d8c154821bb7d41a7d112f5bac5f4a17b +size 5962 diff --git a/marked/Rel-11/23_series/23081/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-11/23_series/23081/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39ea4902ab20ee2d1a7ea5bcf92f71ad76219a6a --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23081/6a5c8326029e6290e69a5f43d6ed4548_img.jpg b/marked/Rel-11/23_series/23081/6a5c8326029e6290e69a5f43d6ed4548_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab1dd1180532ec168ff2c6ee8028880b6301b26d --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23081/73dff6b45b2b9ffd384bab3235f869af_img.jpg b/marked/Rel-11/23_series/23081/73dff6b45b2b9ffd384bab3235f869af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b17581b09de99029014ca3ba68fd25310cdd083a --- /dev/null +++ b/marked/Rel-11/23_series/23081/73dff6b45b2b9ffd384bab3235f869af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d0e30cb695eb10d15768a438d144e9e06b7e04bf42572ae862f9803f4948851 +size 6360 diff --git a/marked/Rel-11/23_series/23081/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-11/23_series/23081/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee45cfd9452277b641f8cf4fc1af6a03e3102ce7 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23081/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-11/23_series/23081/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76628e7bd54ba2180e80693b276c67ececc74471 --- /dev/null +++ b/marked/Rel-11/23_series/23081/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb0cce3a0872f80a50ebd525d7675e8221c9fea62836023de38640bd6f06508f +size 65844 diff --git a/marked/Rel-11/23_series/23081/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-11/23_series/23081/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98bbbea0ccb23be7b59be63b8b9725302cf22ae6 --- /dev/null +++ b/marked/Rel-11/23_series/23081/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:badc1f8a0193796921c3d72dcabc198c9241038797d91288338381a112f298d6 +size 31315 diff --git a/marked/Rel-11/23_series/23081/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-11/23_series/23081/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aaff287f1cb6a15fe563f5730c9a7e16436d716f --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23081/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-11/23_series/23081/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cfd3f9a71c481d6c891cfd1dfad1b698b1944ab --- /dev/null +++ b/marked/Rel-11/23_series/23081/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3a4a1f298c69d2b31ae2aff866aadbedc3edde65e54b733c797a606b82af59d +size 53729 diff --git a/marked/Rel-11/23_series/23081/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-11/23_series/23081/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46ea6205ef6cbd951064a2b10fe4f8e175e5a01c --- /dev/null +++ b/marked/Rel-11/23_series/23081/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:805b1fc017594fee39f56465e03a9724226c0f7e2221139e680e5fd2a4003f91 +size 67393 diff --git a/marked/Rel-11/23_series/23081/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-11/23_series/23081/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f0024ad40275102b04ab199fd5f407dd3424849 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23081/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-11/23_series/23081/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0d0831d05eded1d701d87c4200408243123f769 --- /dev/null +++ b/marked/Rel-11/23_series/23081/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f885b6fce7c4b720784cf8c0464d0711d5d56fff9fa6d9686ad116d728e208ce +size 98366 diff --git a/marked/Rel-11/23_series/23081/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-11/23_series/23081/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..069e67d44392c0fa49e6dafe6ee1e27e66d13748 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23081/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/Rel-11/23_series/23081/ddc7460821484f1ae2835c67955c554c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb7c15c292b14950961f1bd0f390b0a42f2b019f --- /dev/null +++ b/marked/Rel-11/23_series/23081/ddc7460821484f1ae2835c67955c554c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:956dac3943b78d7f537926b5914002e68fcc220fdf835b6e0cc32de0f9b3192b +size 34109 diff --git a/marked/Rel-11/23_series/23081/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-11/23_series/23081/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4cf44bcef89f582a841c67cd4e38acbabd3b4642 --- /dev/null +++ b/marked/Rel-11/23_series/23081/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9388f6d8a142dad14a31db4c6f540288a157694d23496b3e94b744f7d7df796 +size 129490 diff --git a/marked/Rel-11/23_series/23081/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-11/23_series/23081/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e744a7004c1af951395bda2dca068ec4e97d8d65 --- /dev/null +++ b/marked/Rel-11/23_series/23081/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59b2aa908cde75a561cdcb23253e7e653ca352cdf13000e86890519da90ac518 +size 24229 diff --git a/marked/Rel-11/23_series/23081/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-11/23_series/23081/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6299561d96ebf2e0951e49e80c486f2bf690f59a --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23081/ead623e6a8ec701df64567695a57d01c_img.jpg b/marked/Rel-11/23_series/23081/ead623e6a8ec701df64567695a57d01c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..581629ee79935f6864d192cbb9c1ff186d039368 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23081/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-11/23_series/23081/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cab1523e10bd7169a247d75c2881020ad107f6c9 --- /dev/null +++ b/marked/Rel-11/23_series/23081/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d911c4da5927a1246543a698af414192284dc42ed1dae16e63c0eb1ad6346b6 +size 111362 diff --git a/marked/Rel-11/23_series/23081/eb22a8740f7c6a0f6ee98f16d99ed8b9_img.jpg b/marked/Rel-11/23_series/23081/eb22a8740f7c6a0f6ee98f16d99ed8b9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2010b37a7a92234bb2b7f6ae70582820094efa71 --- /dev/null +++ b/marked/Rel-11/23_series/23081/eb22a8740f7c6a0f6ee98f16d99ed8b9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9df58f4ee2635ab4ec20d504ffc86fe7519f4e380d4843a9a5398da297cdb52 +size 1718 diff --git a/marked/Rel-11/23_series/23081/raw.md b/marked/Rel-11/23_series/23081/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c35b1ab3de57adec4eeeaddd054847a79a16767c --- /dev/null +++ b/marked/Rel-11/23_series/23081/raw.md @@ -0,0 +1,1354 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 0 Scope..... | 6 | +| 0.1 References ..... | 6 | +| 0.2 Definitions and abbreviations..... | 6 | +| 0.2.1 Definitions ..... | 6 | +| 0.2.1.1 Definition of line identity ..... | 6 | +| 0.2.1.2 Definition of presentation and screening indicators ..... | 7 | +| 0.2.2 Abbreviations ..... | 7 | +| 1 Calling line identification presentation (CLIP)..... | 7 | +| 1.1 Handling of calling line identification presentation..... | 7 | +| 1.1.1 Interrogation ..... | 7 | +| 1.2 Functions and information flows..... | 8 | +| 1.2.1 Optional capability to carry calling line identification..... | 17 | +| 1.2.2 Information elements used in the messages ..... | 17 | +| 1.2.3 Parameters in Send Routeing Info and Provide Roaming Number for CLI..... | 18 | +| 1.2.4 Messages between MSC and VLR in destination network ..... | 19 | +| 1.3 Information stored in the HLR ..... | 19 | +| 1.4 State transition model..... | 19 | +| 1.5 Transfer of information from HLR to VLR ..... | 20 | +| 1.6 Information stored in the VLR ..... | 20 | +| 1.7 Handover ..... | 20 | +| 1.8 Interactions with other supplementary services ..... | 20 | +| 2 Calling line identification restriction (CLIR)..... | 20 | +| 2.1 Handling of calling line identification restriction ..... | 20 | +| 2.1.1 General ..... | 20 | +| 2.1.2 Permanent mode ..... | 21 | +| 2.1.3 Controlling presentation of the CLI when CLIR is provisioned in temporary mode..... | 21 | +| 2.1.4 Interrogation ..... | 21 | +| 2.2 Functions and information flows..... | 22 | +| 2.3 Information stored in the HLR ..... | 28 | +| 2.4 State transition model..... | 28 | +| 2.5 Transfer of information from HLR to VLR ..... | 28 | +| 2.6 Information stored in the VLR ..... | 28 | +| 2.7 Handover ..... | 29 | +| 2.8 Interworking ..... | 29 | +| 3 Connected line identification presentation (COLP)..... | 29 | +| 3.1 Handling of connected line identification presentation..... | 29 | +| 3.1.1 Interrogation ..... | 29 | +| 3.1.2 Interactions with call forwarding supplementary services ..... | 30 | +| 3.2 Functions and information flows..... | 30 | +| 3.3 Information stored in the HLR ..... | 35 | +| 3.4 State transition model..... | 35 | +| 3.5 Transfer of information from HLR to VLR ..... | 35 | +| 3.6 Information stored in the VLR ..... | 36 | +| 3.7 Handover ..... | 36 | +| 4 Connected line identification restriction (COLR)..... | 36 | +| 4.1 Handling of connected line identification restriction..... | 36 | +| 4.1.1 General ..... | 36 | +| 4.1.2 Interrogation ..... | 36 | +| 4.2 Functions and information flows..... | 37 | +| 4.3 Information stored in the HLR ..... | 40 | +| 4.4 State transition model..... | 40 | +| 4.5 Transfer of information from HLR to VLR ..... | 41 | +| 4.6 Information stored in the VLR ..... | 41 | +| 4.7 Handover ..... | 41 | + +4.8 Interworking .....41 + +**Annex A (informative): Mapping of CLI.....42** + +Annex B (informative): Change history.....44 + +# --- Foreword + +This Technical Specification has been produced by the 3GPP. + +This TS defines the stage 2 of the line identification supplementary services for the 3GPP system. + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version 3.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 Indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the specification; + +# 0 Scope + +The present document gives the stage 2 description of the call identification supplementary services. + +The group line identification supplementary services are divided into the following four supplementary services: + +- | | | | +|----------------------------------------------|------|-------------| +| - Calling line identification presentation | CLIP | (clause 1); | +| - Calling line identification restriction | CLIR | (clause 2); | +| - Connected line identification presentation | COLP | (clause 3); | +| - Connected line identification restriction | COLR | (clause 4). | + +## 0.1 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. +- For a specific reference, subsequent revisions do not apply. +- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. + +- [1] 3GPP TS 21.905: "3G Vocabulary". +- [2] 3GPP TS 23.011: "Technical Realization of Supplementary Services - General Aspects." +- [3] 3GPP TS 23.018 : "Basic Call Handling; Technical realization". +- [4] 3GPP TS 22.081: "Line Identification supplementary services - Stage 1". + +## 0.2 Definitions and abbreviations + +### 0.2.1 Definitions + +#### 0.2.1.1 Definition of line identity + +The line identity is made up of the following information units: + +- The subscriber's international ISDN/MSISDN number; +- Optionally subaddress information. + +For mobile originated calls, the ISDN/MSISDN shall always be provided within the network. The subaddress shall only be included if it is provided by the user (or user equipment). + +The calling line identity is the line identity of the calling party. The connected line identity is the line identity of the connected party. + +The additional calling line identity provides additional line information for the purpose of the calling line identification presentation service (CLIP). The additional connected line identity provides additional line information for the purpose of the connected line identification presentation service (COLP). + +For mobile originating calls the user (or user equipment) has no possibility to provide an additional line identity. For mobile terminating calls the user (or user equipment) has no possibility to provide an additional connected line identity. + +#### 0.2.1.2 Definition of presentation and screening indicators + +In addition to, or instead of, the line identity or additional line identity, the network may send a presentation indicator (PI) together with a Cause of no CLI (CoNC) and/or a screening indicator (SI) to the MS as follows: + +- Presentation Indicator: + - a) Presentation allowed; + - b) Presentation restricted; + - c) Number not available. +- If the Presentation Indicator indicates "presentation restricted" the Cause of no CLI may give a diagnostic: + - a) Unavailable; + - b) Rejected by user; + - c) Interaction with other services; + - d) Coin line/ Pay phone. +- Screening indicator: + - a) User provided, verified and passed; + - b) User provided, not screened; + - c) network provided. + +The screening indicator applies to the ISDN/MSISDN or the number given as additional line identity respectively. + +### 0.2.2 Abbreviations + +Abbreviations used in the present document are listed in 3GPP TR 21.905. + +# 1 Calling line identification presentation (CLIP) + +## 1.1 Handling of calling line identification presentation + +### 1.1.1 Interrogation + +#### Status check + +The mobile subscriber can request the status of the supplementary service and be informed if the service is provided to him/her. This procedure is illustrated in figure 1.1. + +![Sequence diagram illustrating the interrogation of calling line identification presentation (CLIP). The diagram shows four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence of messages is: 1. MS sends 'Interrogate CLIP' to MSC. 2. MSC sends 'Interrogate CLIP' to VLR. 3. VLR sends 'Acknowledge' back to MSC. 4. MSC sends 'Release Complete' back to MS. The HLR is shown but not involved in this specific sequence.](4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + MS->>MSC: Interrogate CLIP + MSC->>VLR: Interrogate CLIP + VLR-->>MSC: Acknowledge + MSC-->>MS: Release Complete +``` + +Sequence diagram illustrating the interrogation of calling line identification presentation (CLIP). The diagram shows four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence of messages is: 1. MS sends 'Interrogate CLIP' to MSC. 2. MSC sends 'Interrogate CLIP' to VLR. 3. VLR sends 'Acknowledge' back to MSC. 4. MSC sends 'Release Complete' back to MS. The HLR is shown but not involved in this specific sequence. + +Figure 1.1: Interrogation of calling line identification presentation + +## 1.2 Functions and information flows + +The following Mobile Additional Functions have been identified for the PLMN: + +### MAF001 + +Determination of the calling line identification presentation subscription + +The ability of a PLMN component to determine whether the supplementary service is provisioned for the mobile subscriber. See figure 1.2. + +Location: VLR. + +### MAF002 + +Determination of the calling party number for offering to the called party + +The ability of a PLMN component to determine and to forward the calling line identity and related indications to the called party. See figure 1.3. + +Location: destination MSC. + +The information flow is shown in figure 1.9. + +![Flowchart for Process CLIP_MAF001. It starts with 'idle', followed by 'initiate handling of CLIP'. A decision 'CLIP provisioned' follows. If 'no', it goes to 'set provision indication = not provisioned'. If 'yes', it goes to 'set provision indication = provisioned'. From there, a decision 'called subscriber in HPLMN country' is made. If 'no', it goes to 'set override category = no'. If 'yes', a decision 'override category' is made. If 'yes', it goes to 'set override category = yes'. If 'no', it goes to 'set override category = no'. Both 'set override category' paths lead to 'continue call handling', which then leads to 'idle'. A note at the bottom right says 'CLIP: Calling Line Identification Presentation.'](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +Process CLIP\_MAF001 + +381\_12(1) + +Figure 1.2 + +``` +graph TD; Start([idle]) --> Init[/initiate handling of CLIP/]; Init --> CLIP_Prov{CLIP provisioned}; CLIP_Prov -- no --> SetNotProv[set provision indication = not provisioned]; CLIP_Prov -- yes --> SetProv[set provision indication = provisioned]; SetProv --> HPLMN{called subscriber in HPLMN country}; HPLMN -- no --> SetOverrideNo[set override category = no]; HPLMN -- yes --> Override{override category}; Override -- no --> SetOverrideNo; Override -- yes --> SetOverrideYes[set override category = yes]; SetNotProv --> Continue{continue call handling}; SetOverrideYes --> Continue; SetOverrideNo --> Continue; Continue --> End([idle]); +``` + +CLIP: Calling Line Identification Presentation. + +Flowchart for Process CLIP\_MAF001. It starts with 'idle', followed by 'initiate handling of CLIP'. A decision 'CLIP provisioned' follows. If 'no', it goes to 'set provision indication = not provisioned'. If 'yes', it goes to 'set provision indication = provisioned'. From there, a decision 'called subscriber in HPLMN country' is made. If 'no', it goes to 'set override category = no'. If 'yes', a decision 'override category' is made. If 'yes', it goes to 'set override category = yes'. If 'no', it goes to 'set override category = no'. Both 'set override category' paths lead to 'continue call handling', which then leads to 'idle'. A note at the bottom right says 'CLIP: Calling Line Identification Presentation.' + +Figure 1.2: MAF001 Determination of calling line identification presentation subscription (VLR) + +![Flowchart for process CLIP_MAF002: Determination of the information for offering to the called party (destination MSC).](e6df2733626a85205c1db682e6259c46_img.jpg) + +process CLIP\_MAF002 + +381\_13(1) + +Figure 1.3 + +``` + +graph TD + Idle1([Idle]) --> Init[initiate handling of CLIP] + Init --> CLIP_Provisioned{CLIP Provisioned} + CLIP_Provisioned -- No --> End1(( )) + CLIP_Provisioned -- Yes --> CLI_available{CLI available} + CLI_available -- No --> End2(( )) + CLI_available -- Yes --> CLI_received_VLR{CLI received from VLR} + CLI_received_VLR -- No --> Use_CLI_Signalling[Use CLI received from signalling] + CLI_received_VLR -- Yes --> Use_CLI_VLR[Use CLI received from VLR] + Use_CLI_Signalling --> PI_Restricted{PI = Presentation restricted?} + Use_CLI_VLR --> PI_Restricted + PI_Restricted -- Yes --> Cause_No_CLI[Cause of No CLI] + PI_Restricted -- No --> Additional_CLI_Available{additional CLI available} + Cause_No_CLI --> Override_Category1{override category} + Override_Category1 -- Yes --> Additional_CLI_Available1{additional CLI available} + Override_Category1 -- No --> Additional_CLI_Available2{additional CLI available} + Additional_CLI_Available1 -- Yes --> CLI_Override[CLI in case of override category] + Additional_CLI_Available1 -- No --> Pass_CLI1[pass CLI] + CLI_Override --> Additional_CLI[additional CLI] + Additional_CLI --> Pass_Additional_CLI1[pass additional CLI] + Additional_CLI_Available2 -- Yes --> Override_Category2{override category} + Additional_CLI_Available2 -- No --> PI_Restricted_Network{PI = presentation restricted by network?} + Override_Category2 -- Yes --> Set_PI_Restricted[Set PI = presentation restricted] + Override_Category2 -- No --> Set_PI_Not_Available1[Set PI = number not available] + Set_PI_Restricted --> Pass_CLI2[pass CLI] + Set_PI_Not_Available1 --> Pass_CLI2 + Pass_CLI1 --> Continue[Continue Call Handling] + Pass_CLI2 --> Continue + Pass_Additional_CLI1 --> Continue + PI_Restricted_Network --> Pass_Additional_CLI2[pass additional CLI] + Pass_Additional_CLI2 --> Continue + End2 --> Set_PI_Not_Available2[set PI = number not available] + Set_PI_Not_Available2 --> Continue + Continue --> Idle2([Idle]) + +``` + +CLIP: Calling Line Identification Presentation +CLI: Calling Line Identity +PI: Presentation Indicator + +Flowchart for process CLIP\_MAF002: Determination of the information for offering to the called party (destination MSC). + +Figure 1.3: MAF002 Determination of the information for offering to the called party (destination MSC) + +![Flowchart for Procedure Cause_of_no_CLI](5a4e62bead259c258d069fd3663ea670_img.jpg) + +### Procedure Cause\_of\_no\_CLI + +1(1) + +``` +graph TD; Start([ ]) --> Q1{Cause of no CLI supported?}; Q1 -- Yes --> Q2{CoNC = reject by user?}; Q1 -- No --> End(( )); Q2 -- Yes --> End; Q2 -- No --> Q3{CoNC = interworking with other services?}; Q3 -- Yes --> Set3[Set CoNC = Interworking with other services]; Q3 -- No --> Q4{CoNC = Coin line/payphone?}; Q4 -- Yes --> Set2[Set CoNC = Coin line/payphone]; Q4 -- No --> Q5{CoNC = Unavailable?}; Q5 -- Yes --> Set1[Set CoNC = Unavailable]; Q5 -- No --> End; Set1 --> End; Set2 --> End; Set3 --> End; +``` + +The flowchart titled 'Procedure Cause\_of\_no\_CLI' starts with an oval connector. The first decision diamond asks 'Cause of no CLI supported?'. If 'Yes', it proceeds to the next decision 'CoNC = reject by user?'. If 'Yes' to this, it ends at a circle with an 'X'. If 'No', it proceeds to 'CoNC = interworking with other services?'. If 'Yes', it goes to 'Set CoNC = Interworking with other services'. If 'No', it proceeds to 'CoNC = Coin line/payphone?'. If 'Yes', it goes to 'Set CoNC = Coin line/payphone'. If 'No', it proceeds to 'CoNC = Unavailable?'. If 'Yes', it goes to 'Set CoNC = Unavailable'. If 'No', it ends at the circle with an 'X'. All four 'Set CoNC' boxes lead to the same end connector. A note box in the top right contains 'CoNC : Cause of no CLI'. + +Flowchart for Procedure Cause\_of\_no\_CLI + +Figure 1.4: Procedure Cause\_of\_no\_CLI + +![SDL diagram for Procedure CLI_MT_GMSC showing a start symbol, a process box to add calling party information to the SRI, and an end symbol.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Procedure CLI\_MT\_GMSC 1(1) + +``` + +graph TD + Start([ ]) + Process[ ] + Note[Add Calling Party +Number and Generic +Number to the SRI] + End((X)) + + Start --> Process + Process --- Note + Process --> End + +``` + +SDL diagram for Procedure CLI\_MT\_GMSC showing a start symbol, a process box to add calling party information to the SRI, and an end symbol. + +**Figure 1.5: Addition of line identification information to Send Routeing Info message.** + +#### Procedure CLI\_HLR\_Set\_CLI + +1(1) + +![Note box icon](eb22a8740f7c6a0f6ee98f16d99ed8b9_img.jpg) + +Note box icon + +![Flowchart for CLI_HLR_Set_CLI procedure](ddc7460821484f1ae2835c67955c554c_img.jpg) + +``` +graph TD; Start([ ]) --> D1{ }; D1 -- No --> End(( )); D1 -- Yes --> D2{ }; D2 -- No --> End; D2 -- Yes --> D3{ }; D3 -- No --> End; D3 -- Yes --> P1[Add Calling Party Number and Generic Number to the PRN]; P1 --> End; +``` + +The flowchart illustrates the procedure for adding line identification information. It begins with a start symbol (oval with a vertical line) leading to a decision diamond. The first decision is 'Subscriber roaming outside home country'. If 'No', the process ends at a circle with an 'X'. If 'Yes', it proceeds to the next decision diamond: 'Sending of CLI information allowed to destination NW'. If 'No', the process ends. If 'Yes', it proceeds to the third decision diamond: 'CLI information received from GMSC'. If 'No', the process ends. If 'Yes', it proceeds to a process box: 'Add Calling Party Number and Generic Number to the PRN', which then leads to the end symbol. + +Flowchart for CLI\_HLR\_Set\_CLI procedure + +Figure 1.6: Addition of line identification information to Provide Roaming Number message. + +![Flowchart for Procedure CLI_PRN_VLR. It starts with a connector symbol, followed by a decision diamond 'CLI Information received from HLR'. If 'No', it goes to another decision diamond 'Subscriber roaming outside home country'. If 'No' to the second diamond, it goes to a connector symbol. If 'Yes' to the second diamond, it goes to a process box 'Store CLI information', which then leads to a connector symbol. If 'Yes' to the first diamond, it also leads to the connector symbol.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Procedure CLI\_PRN\_VLR + +1(1) + +``` +graph TD; Start([ ]) --> D1{CLI Information received from HLR}; D1 -- No --> D2{Subscriber roaming outside home country}; D1 -- Yes --> End(( )); D2 -- No --> End; D2 -- Yes --> Process[Store CLI information]; Process --> End; +``` + +Flowchart for Procedure CLI\_PRN\_VLR. It starts with a connector symbol, followed by a decision diamond 'CLI Information received from HLR'. If 'No', it goes to another decision diamond 'Subscriber roaming outside home country'. If 'No' to the second diamond, it goes to a connector symbol. If 'Yes' to the second diamond, it goes to a process box 'Store CLI information', which then leads to a connector symbol. If 'Yes' to the first diamond, it also leads to the connector symbol. + +Figure 1.7: Storing of Line Identification in destination VLR + +![Flowchart for Procedure CLI_ICH_VLR_Add_CLI. It starts with a connector symbol, leading to a decision diamond 'CLI information stored in VLR'. If 'No', it goes to an exit connector. If 'Yes', it goes to a process block 'Add Calling Party Number and Generic Number to message to MSC', which then leads to an exit connector.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +Procedure CLI\_ICH\_VLR\_Add\_CLI + +1(1) + +``` +graph TD; Start([ ]) --> Decision{CLI information stored in VLR}; Decision -- No --> Exit1(( )); Decision -- Yes --> Process[Add Calling Party Number and Generic Number to message to MSC]; Process --> Exit2(( )); +``` + +Flowchart for Procedure CLI\_ICH\_VLR\_Add\_CLI. It starts with a connector symbol, leading to a decision diamond 'CLI information stored in VLR'. If 'No', it goes to an exit connector. If 'Yes', it goes to a process block 'Add Calling Party Number and Generic Number to message to MSC', which then leads to an exit connector. + +Figure 1.8: Addition of line identification information to Complete Call/Process Call Waiting message. + +![Sequence diagrams showing information flow for calling line identification presentation. The top diagram shows a direct path from MS/TE to MSb via MSCa/LE, VLRb, and MSCb. The bottom diagram shows a more complex path involving a GMSC and HLRb for routing information before reaching MSCb and MSb.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +**Top Sequence Diagram:** + +- MS/TE** sends a **set-up** message to **MSCa/LE**. +- MSCa/LE** sends a **set-up** message to **MSCb** containing **(SI+PI+CoNC+LI+aSI+aPI+aLI)**. +- MSCb** sends an **info req** to **VLRb** (labeled **MAF 001**). +- VLRb** sends an **info ack** to **MSCb** (labeled **MAF002**). +- MSCb** sends a **set-up** message to **MSb** containing **(SI+PI+CoNC+LI)**. + +**Bottom Sequence Diagram:** + +- MS/TE** sends a **set-up** message to **MSCa/LE**. +- MSCa/LE** sends a **set-up** message to **GMSC** containing **(SI+PI+CoNC+LI+aSI+aPI+aLI)**. +- GMSC** sends an **SRI** message to **HLRb**. +- HLRb** sends a response containing **(SI+PI+LI+aSI+aPI+aLI)** to **GMSC**. +- GMSC** sends an **SRI ack** message to **HLRb**. +- HLRb** sends a **PRN** message to **VLRb**. +- VLRb** sends a response containing **(SI+PI+LI+aSI+aPI+aLI)** to **HLRb**. +- HLRb** sends a **PRN ack** message to **VLRb**. +- GMSC** sends a **set-up** message to **MSCb** containing **(SI+PI+CoNC+LI+aSI+aPI+aLI)**. +- MSCb** sends an **info req** to **VLRb** (labeled **MAF 001**). +- VLRb** sends an **info ack** to **MSCb** (labeled **MAF 002**). +- MSCb** sends a **set-up** message to **MSba** containing **(SI+PI+CoNC+LI)**. + +Sequence diagrams showing information flow for calling line identification presentation. The top diagram shows a direct path from MS/TE to MSb via MSCa/LE, VLRb, and MSCb. The bottom diagram shows a more complex path involving a GMSC and HLRb for routing information before reaching MSCb and MSb. + +Figure 1.9: Information flow for calling line identification presentation: mobile station or fixed terminal to mobile station + +#### NOTE: + +\*\* : A subaddress may be received from the originating MS or the TE + info: information SI: screening indicator aSI: additional screening indicator + req: request PI: presentation indicator CoNC: cause of no CLI + aPI: additional presentation indicator + ack: acknowledge LI: line identity aLI: additional line identity + +NOTE: For mapping rules of CLI parameters refer to Annex A. + +### 1.2.1 Optional capability to carry calling line identification + +When GMSC is performing Send Routing Info query it may pass calling line identification to the HLRb. The calling line identification shall be in international format. If the HLRb receives calling line identification within Send Routing Info it may pass unmodified calling line identification within Provide Roaming Number to the VLRb. HLR shall not pass calling line identification in the HPLMN nor in the case where sending of the CLI information is explicitly denied to the destination network.. + +If MSCb receives calling line identification only from signalling it shall use that parameter for presentation purposes i.e. normal handling as described in the previous subclause applies. + +If MSCb receives Cause of no CLI from signalling it shall be sent to the VLRb by Send Info for Incoming Call query. + +If MSCb receives calling line identification and/or Cause of no CLI from VLRb and it supports the feature it shall use that parameter for presentation purposes. In this case calling line identification is stored in the VLRb and when the set-up message is processed the handling described in the previous subclause is done using the stored calling line identification. + +### 1.2.2 Information elements used in the messages + +**Table 1.2.2.1: Information elements used in messages** + +| Information Element | Logical Information element name | Information element Required | Information element description | +|----------------------|----------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Calling Party Number | SI | M | Calling Party Number contains screening indicator (SI), presentation indicator (PI) and line identity (LI) as mandatory information. | +| | PI | M | | +| | LI | M | | +| Generic Number | aSI | M | Generic Number contains additional screening indicator (aSI), additional presentation indicator (aPI) and additional line identity (aLI) as mandatory information. | +| | aPI | M | | +| | aLI | M | | +| Cause of no CLI | unavailable | M | Cause of no CLI contains detailed Cause of no CLI (unavailable, reject by user, interaction with other service, coin line/payphone) as mandatory information. | +| | reject by user | M | | +| | interaction with other service | M | | +| | coin line/payphone | M | | + +### 1.2.3 Parameters in Send Routeing Info and Provide Roaming Number for CLI + +**Table 1.2.3.1: Messages between GMSC and HLR** + +| Message | Message sender | Information element name | Information element Required | Information element description | +|--------------------|----------------|--------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Send Routeing Info | GMSC | - | - | Refer to 3GPP TS 23.018. | +| | | Calling Party Number | C | In addition:
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 of Figure 2.1: MS indicating presentation of CLI when CLIR is provisioned in temporary mode with default value 'presentation restricted'.](73dff6b45b2b9ffd384bab3235f869af_img.jpg) + +The diagram shows a Mobile Station (MS) on the left and a Mobile Switching Center (MSC) on the right. A horizontal arrow points from the MS to the MSC, with the text "Present CLI" written above it. Both the MS and MSC are represented by vertical rectangles with a small horizontal line at the top. + +Diagram of Figure 2.1: MS indicating presentation of CLI when CLIR is provisioned in temporary mode with default value 'presentation restricted'. + +**Figure 2.1: MS indicating presentation of CLI when CLIR is provisioned in temporary mode with default value "presentation restricted"** + +If the default value is set to presentation allowed, the default handling is to present the originating party's CLI to the terminating party (i.e. the terminating MS or TE). + +However, it is possible for the originating subscriber to restrict presentation of his CLI to the terminating party. The originating subscriber must indicate during call set-up that CLI presentation must be restricted. This procedure is illustrated in figure 2.2. + +![Diagram of Figure 2.2: MS invoking CLIR, when CLIR is provisioned in temporary mode with default value 'presentation allowed'.](5fbb4f0de01736f1293333e599410c99_img.jpg) + +The diagram shows a Mobile Station (MS) on the left and a Mobile Switching Center (MSC) on the right. A horizontal arrow points from the MS to the MSC, with the text "Restrict CLI" written above it. Both the MS and MSC are represented by vertical rectangles with a small horizontal line at the top. + +Diagram of Figure 2.2: MS invoking CLIR, when CLIR is provisioned in temporary mode with default value 'presentation allowed'. + +**Figure 2.2: MS invoking CLIR, when CLIR is provisioned in temporary mode with default value "presentation allowed"** + +### 2.1.4 Interrogation + +#### Data request + +The mobile subscriber can request the data of the supplementary service. + +In response the following information shall be given: + +- whether the service is provided or not; +- if provided which mode is subscribed; +- if subscribed to the temporary mode: which default value. + +This procedure is illustrated in figure 2.3. + +![Sequence diagram showing the interrogation of calling line identification restriction. The diagram involves four lifelines: MS, MSC, VLR, and HLR. The sequence of messages is: 1. MS sends 'Interrogate CLIR' to MSC. 2. MSC sends 'Interrogate CLIR' to VLR. 3. VLR sends 'Acknowledge' back to MSC. 4. MSC sends 'Release Complete' back to MS. The HLR lifeline is present but not involved in this sequence.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + MS->>MSC: Interrogate CLIR + MSC->>VLR: Interrogate CLIR + VLR-->>MSC: Acknowledge + MSC-->>MS: Release Complete +``` + +Sequence diagram showing the interrogation of calling line identification restriction. The diagram involves four lifelines: MS, MSC, VLR, and HLR. The sequence of messages is: 1. MS sends 'Interrogate CLIR' to MSC. 2. MSC sends 'Interrogate CLIR' to VLR. 3. VLR sends 'Acknowledge' back to MSC. 4. MSC sends 'Release Complete' back to MS. The HLR lifeline is present but not involved in this sequence. + +**Figure 2.3: Interrogation of calling line identification restriction** + +## 2.2 Functions and information flows + +The following Mobile Additional Functions have been identified for the PLMN: + +### MAF003 + +Determination of the calling line identification restriction subscription + +The ability of a PLMN component to determine whether the supplementary service is provisioned for the mobile subscriber. See figure 2.4. + +Location: VLR. + +### MAF004 + +Determination of the calling party number for offering to the called party + +The ability of a PLMN component to determine and to forward the calling line identity and related indications to the called party. See figure 2.5. + +Location: originating MSC. + +The information flows are shown in figures 2.6 to 2.9. + +![Flowchart for Process CLIR_MAF003: Determination of calling line identification restriction subscription (VLR).](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Process CLIR\_MAF003 381\_24(1) + +Figure 2.4 + +``` +graph TD; Start([idle]) --> Init[/initiate handling of CLIR/]; Init --> Decision1{CLIR provisioned}; Decision1 -- no --> SetNotProvisioned[set provision indication = not provisioned]; Decision1 -- yes --> SetProvisioned[set provision indication = provisioned]; SetProvisioned --> Decision2{subscription option = permanent}; SetNotProvisioned --> Decision2; Decision2 -- yes --> SetPermanent[set mode indication = permanent]; Decision2 -- no --> Decision3{temporary mode default = pres. restricted}; Decision3 -- no --> ModeAllowed[mode indication = temporary (pres. allowed)]; Decision3 -- yes --> ModeRestricted[mode indication = temporary (pres. restricted)]; ModeAllowed --> Continue{continue call handling}; ModeRestricted --> Continue; SetPermanent --> Continue; Continue --> End([idle]); +``` + +CLIR: Calling Line Identification Restriction + +Flowchart for Process CLIR\_MAF003: Determination of calling line identification restriction subscription (VLR). + +**Figure 2.4: MAF003 Determination of calling line identification restriction subscription (VLR)** + +![Flowchart for process CLIR_MAF004: Determination of the presentation indicator (originating MSC).](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +process CLIR\_MAF004 + +381\_25(1) + +Figure 2.5 + +``` +graph TD; Idle1([Idle]) --> Initiate[Initiate Handling of CLIR]; Initiate --> CLIR_Provisioned{CLIR Provisioned?}; CLIR_Provisioned -- No --> Restrict_CLI_note2{Restrict CLI? note 2}; CLIR_Provisioned -- Yes --> Permanent{Permanent?}; Restrict_CLI_note2 -- Yes --> ClearCall{{Clear Call}}; Restrict_CLI_note2 -- No --> SetPI_allowed1[Set PI = presentation allowed]; Permanent -- Yes --> Present_CLI_note1_1{present CLI? note 1}; Permanent -- No --> TempModeDefault{temporary mode default = pres. restricted?}; Present_CLI_note1_1 -- Yes --> SetPI_restricted1[Set PI = Presentation restricted]; Present_CLI_note1_1 -- No --> ErrorNotification{{Error Notification}}; TempModeDefault -- Yes --> Present_CLI_note1_2{present CLI note 1}; TempModeDefault -- No --> Restrict_CLI_note2_2{restrict CLI? note 2}; Present_CLI_note1_2 -- Yes --> SetPI_allowed2[Set PI = Presentation allowed]; Present_CLI_note1_2 -- No --> ErrorNotification; Restrict_CLI_note2_2 -- Yes --> SetPI_restricted2[Set PI = presentation restricted]; Restrict_CLI_note2_2 -- No --> SetPI_allowed2; SetPI_allowed1 --> Continue[Continue Call Handling]; SetPI_restricted1 --> Cause_of_no_CLI_CLIR1[Cause_of no_CLI_CLIR]; SetPI_allowed2 --> Continue; SetPI_restricted2 --> Cause_of_no_CLI_CLIR2[Cause_of no_CLI_CLIR]; Cause_of_no_CLI_CLIR1 --> Continue; Cause_of_no_CLI_CLIR2 --> Continue; Continue --> Idle2([Idle]); +``` + +Note 1: present CLI is input received from the mobile +Note 2: restrict CLI is input received from the mobile + +CLIR: Calling Line Identification Restriction +CLI: Calling Line Identity +PI: Presentation Indicator + +Flowchart for process CLIR\_MAF004: Determination of the presentation indicator (originating MSC). + +Figure 2.5: MAF004 Determination of the presentation indicator (originating MSC) + +![Flowchart for Procedure Cause_of_no_CLI_CLIR. It starts with a connector, then checks if 'Cause of no CLI supported?'. If 'No', it goes to a merge point. If 'Yes', it checks 'rejected by user?'. If 'Yes', it goes to 'Set CoNC = reject by user'. If 'No', it checks 'interacted with other services?'. If 'Yes', it goes to 'Set CoNC = interaction with other services'. If 'No', it checks 'coin line/ payphone?'. If 'Yes', it goes to 'Set CoNC = coin line/payphone'. If 'No', it checks 'Unavailable?'. If 'Yes', it goes to 'Set CoNC = unavailable'. If 'No', it goes to a merge point. All four 'Set CoNC' boxes lead to a common merge point, which then leads to an end connector.](26d664119ad25250780f554633444e54_img.jpg) + +Procedure Cause\_of\_no\_CLI\_CLIR 1(1) + +``` +graph TD; Start([ ]) --> Q1{Cause of no CLI supported?}; Q1 -- No --> Merge(( )); Q1 -- Yes --> Q2{rejected by user?}; Q2 -- Yes --> Set1[Set CoNC = reject by user]; Q2 -- No --> Q3{interacted with other services?}; Q3 -- Yes --> Set2[Set CoNC = interaction with other services]; Q3 -- No --> Q4{coin line/ payphone?}; Q4 -- Yes --> Set3[Set CoNC = coin line/payphone]; Q4 -- No --> Q5{Unavailable?}; Q5 -- Yes --> Set4[Set CoNC = unavailable]; Q5 -- No --> Merge; Set1 --> Merge; Set2 --> Merge; Set3 --> Merge; Set4 --> Merge; Merge --> End((X)) +``` + +Flowchart for Procedure Cause\_of\_no\_CLI\_CLIR. It starts with a connector, then checks if 'Cause of no CLI supported?'. If 'No', it goes to a merge point. If 'Yes', it checks 'rejected by user?'. If 'Yes', it goes to 'Set CoNC = reject by user'. If 'No', it checks 'interacted with other services?'. If 'Yes', it goes to 'Set CoNC = interaction with other services'. If 'No', it checks 'coin line/ payphone?'. If 'Yes', it goes to 'Set CoNC = coin line/payphone'. If 'No', it checks 'Unavailable?'. If 'Yes', it goes to 'Set CoNC = unavailable'. If 'No', it goes to a merge point. All four 'Set CoNC' boxes lead to a common merge point, which then leads to an end connector. + +Figure 2.6: Procedure Cause\_of\_no\_CLI\_CLIR + +![Sequence diagram for Figure 2.7 showing information flow for calling line identification restriction.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant MSCb/LE + Note right of MSC: MAF 004 + Note right of VLR: MAF 003 + MS->>MSC: set-up +** + MSC->>VLR: info request + VLR-->>MSC: info acknowledge + MSC->>MSCb/LE: set-up +(SI,PI=restricted, CoNC, +LI:Calling party number) + +``` + +The diagram illustrates the information flow for calling line identification restriction. It involves four lifelines: MS, MSC, VLR, and MSCb/LE. The MS sends a 'set-up' message to the MSC, which includes a subaddress (\*\*). The MSC then sends an 'info request' to the VLR. The VLR responds with an 'info acknowledge'. Finally, the MSC sends a 'set-up' message to the MSCb/LE, which includes the screening indicator (SI), presentation indicator (PI) set to 'restricted', CoNC, and the line identity (LI) of the calling party number. The MSC has a message authentication code (MAC) MAF 004, and the VLR has MAF 003. + +Sequence diagram for Figure 2.7 showing information flow for calling line identification restriction. + +**Figure 2.7: Information flow for calling line identification restriction in permanent or temporary mode with the default value "presentation restricted"** + +NOTE: \*\*: A subaddress may be received from the MS + SI: screening indicator + PI: presentation indicator + LI: line identity + +![Sequence diagram for Figure 2.8 showing information flow for allowing presentation of the CLI.](392a79ccd95e682ccd08f35ab2e64144_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant MSCb/LE + Note right of MSC: MAF 004 + Note right of VLR: MAF 003 + MS->>MSC: set-up +(present CLI) +** + MSC->>VLR: info request + VLR-->>MSC: info acknowledge + MSC->>MSCb/LE: set-up +(SI, PI=pres allowed, LI) + +``` + +The diagram illustrates the information flow for allowing the presentation of the calling line identity (CLI) when CLIR is provisioned in temporary mode. It involves four lifelines: MS, MSC, VLR, and MSCb/LE. The MS sends a 'set-up' message to the MSC, which includes the calling line identity (present CLI) and a subaddress (\*\*). The MSC then sends an 'info request' to the VLR. The VLR responds with an 'info acknowledge'. Finally, the MSC sends a 'set-up' message to the MSCb/LE, which includes the screening indicator (SI), presentation indicator (PI) set to 'pres allowed', and the line identity (LI). The MSC has a message authentication code (MAC) MAF 004, and the VLR has MAF 003. + +Sequence diagram for Figure 2.8 showing information flow for allowing presentation of the CLI. + +**Figure 2.8: Information flow for allowing presentation of the CLI when CLIR is provisioned in temporary mode with default value "presentation restricted"** + +NOTE: \*\*: A subaddress may be received from the MS + SI: screening indicator + PI: presentation indicator + LI: line identity + CLI: calling line identity + +![Sequence diagram for calling line identification presentation in temporary mode with default value 'presentation allowed'.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +This sequence diagram illustrates the information flow for calling line identification presentation in temporary mode with the default value "presentation allowed". The participants are MS, MSC, VLR, and MSCb/LE. The sequence of messages is as follows: 1. The MS sends a "set-up" message to the MSC, with a subaddress (\*\*). 2. The MSC sends an "info request" to the VLR, identified by MAF 004. 3. The VLR responds with an "info acknowledge" to the MSC, identified by MAF 003. 4. Finally, the MSC sends a "set-up" message to the MSCb/LE, including parameters (SI, PI=pres allowed, LI). + +Sequence diagram for calling line identification presentation in temporary mode with default value 'presentation allowed'. + +NOTE: \*\*: A subaddress may be received from the MS +SI: screening indicator +PI: presentation indicator +LI: line identity + +![Sequence diagram for calling line identification restriction in temporary mode with default value 'presentation allowed'.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg) + +This sequence diagram illustrates the information flow for calling line identification restriction in temporary mode with the default value "presentation allowed". The participants are MS, MSC, VLR, and MSCb/LE. The sequence of messages is as follows: 1. The MS sends a "set-up" message to the MSC, containing "(restrict CLI)" and a subaddress (\*\*). 2. The MSC sends an "info request" to the VLR, identified by MAF 004. 3. The VLR responds with an "info acknowledge" to the MSC, identified by MAF 003. 4. Finally, the MSC sends a "set-up" message to the MSCb/LE, including parameters (SI, PI=restricted, CoNC, LI:Calling party number). + +Sequence diagram for calling line identification restriction in temporary mode with default value 'presentation allowed'. + +**Figure 2.9 : Information flow for calling line identification restriction in temporary mode with default value "presentation allowed"** + +NOTE: \*\*: A subaddress may be received from the MS +SI: screening indicator +PI: presentation indicator +LI: line identity +CLI: calling line identity + +## 2.3 Information stored in the HLR + +CLIR may have the following logical states (refer to 3GPP TS 23.011 for an explanation of the notation): + +| Provisioning State | Registration State | Activation State | HLR Induction State | +|--------------------|--------------------|-----------------------|---------------------| +| (Not Provisioned, | Not Applicable, | Not Active, | Not Induced) | +| (Provisioned, | Not Applicable, | Active and Operative, | Not Induced) | + +The HLR shall store the logical state of CLIR (which shall be one of the valid states listed above) on a per subscriber basis. + +The HLR shall also store the subscription option "presentation mode" on a per subscriber basis. + +This parameter takes one of the following values: + +- permanent; +- temporary (presentation restricted); +- temporary (presentation allowed). + +## 2.4 State transition model + +The following figure shows the successful cases of transition between the applicable logical states of CLIR. The state changes are caused by actions of the service provider. + +Note that error cases are not shown in the diagram as they normally do not cause a state change. Additionally, some successful requests may not cause a state change. Hence they are not shown in the diagram. + +![State transition model for CLIR diagram showing two states and two transitions.](ead623e6a8ec701df64567695a57d01c_img.jpg) + +``` + +stateDiagram-v2 + [*] --> State1 : Provision + State1 --> State2 : Withdrawal + state " (Not Provisioned, Not Applicable, Not Active, Not Induced) " as State1 + state " (Provisioned, Not Applicable, Active and Operative, Not Induced) " as State2 + +``` + +The diagram illustrates the state transition model for CLIR. It consists of two states represented by ovals. The left state contains the logical state: (Not Provisioned, Not Applicable, Not Active, Not Induced). The right state contains the logical state: (Provisioned, Not Applicable, Active and Operative, Not Induced). A curved arrow labeled "Provision" points from the left state to the right state. A curved arrow labeled "Withdrawal" points from the right state back to the left state. + +State transition model for CLIR diagram showing two states and two transitions. + +Figure 2.10: State transition model for CLIR + +## 2.5 Transfer of information from HLR to VLR + +When the subscriber registers on a VLR, the HLR shall send that VLR information about the logical state of CLIR and the presentation mode. + +If the logical state of CLIR or the presentation mode is changed while a subscriber is registered on a VLR then the HLR shall inform the VLR of the new logical state of CLIR and (if the provisioning state is "Provisioned") the new presentation mode. + +## 2.6 Information stored in the VLR + +For CLIR, the VLR shall store the service state information and presentation mode received from the HLR. + +## 2.7 Handover + +Handover will have no impact on the control procedures and the operation of the service. + +## 2.8 Interworking + +The VPLMN needs to distinguish three cases in order to meet data privacy requirements in an environment where support of CLIP and CLIR is optional: + +- the HPLMN supports CLIR, and CLIR is provisioned for the subscriber; +- the HPLMN supports CLIR, but CLIR is not provisioned for the subscriber; +- the HPLMN does not support CLIR. + +In case a) the VPLMN must apply the CLIR subscription as indicated by the data sent by the HPLMN. + +In case b) the VPLMN must not apply CLIR. + +In case c) the VPLMN must apply an implicit CLIR subscription. + +To allow the VPLMN to make this distinction, the HLR and VLR behave as follows: + +- If the HLR supports CLIR, but CLIR is not provisioned for the subscriber, the HLR shall inform the VLR that CLIR is not provisioned. +- If the VLR supports CLIR, but the HLR does not support CLIR, the VLR shall behave in the same way as if CLIR (temporary (presentation restricted)) was provisioned for the subscriber, i.e. the calling line identity shall not be displayed to the called subscriber unless the called subscriber has CLIR override capability. When interrogating the service status the subscriber shall be informed that CLIR (temporary (presentation restricted)) is provided to him and is active. + +# 3 Connected line identification presentation (COLP) + +## 3.1 Handling of connected line identification presentation + +### 3.1.1 Interrogation + +#### Status check + +The mobile subscriber can request the status of the supplementary service and be informed if the service is provided to him/her. This procedure is illustrated in figure 3.1. + +![Sequence diagram illustrating the interrogation of connected line identification presentation (COLP). The diagram shows four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence of messages is: 1. MS sends 'Interrogate COLP' to MSC. 2. MSC sends 'Interrogate COLP' to VLR. 3. VLR sends 'Acknowledge' to MSC. 4. MSC sends 'Release Complete' to MS. The HLR is shown but not involved in this specific sequence.](6a5c8326029e6290e69a5f43d6ed4548_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + MS->>MSC: Interrogate COLP + MSC->>VLR: Interrogate COLP + VLR-->>MSC: Acknowledge + MSC-->>MS: Release Complete +``` + +Sequence diagram illustrating the interrogation of connected line identification presentation (COLP). The diagram shows four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence of messages is: 1. MS sends 'Interrogate COLP' to MSC. 2. MSC sends 'Interrogate COLP' to VLR. 3. VLR sends 'Acknowledge' to MSC. 4. MSC sends 'Release Complete' to MS. The HLR is shown but not involved in this specific sequence. + +Figure 3.1: Interrogation of connected line identification presentation + +### 3.1.2 Interactions with call forwarding supplementary services + +If the forwarding user selects the option that the calling user is not notified of the call forwarding, then the calling user shall receive no forwarding notification, and the calling user shall not receive the connected user's identity when the call is answered, unless the calling user has override capability. + +## 3.2 Functions and information flows + +The following Mobile Additional Functions have been identified for the PLMN: + +### MAF005 + +Determination of the connected line identification presentation subscription + +The ability of a PLMN component to determine whether the supplementary service is provisioned for the mobile subscriber. See figure 3.2. + +Location: VLR. + +### MAF006 + +Determination of the connected party number for offering to the calling party + +The ability of a PLMN component to determine and to forward the connected line identity and related indications to the calling party. See figure 3.3. + +Location: originating MSC. + +### MAF039 + +Interaction of connected line identification presentation with the call forwarding supplementary services + +The ability of a PLMN component to determine the presentation indicator of the connected party number after invocation of a call forwarding service. See figure 3.4. + +Location: forwarding MSC. + +The information flow is shown in figure 3.5. + +![Flowchart for Process COLP_MAF005: Determination of connected line identification presentation subscription (VLR).](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +Process COLP\_MAF005 381\_32(1) + +Figure 3.2 + +``` +graph TD; Start1([idle]) --> Init[/initiate handling of COLP/]; Init --> Decision1{COLP provisioned}; Decision1 -- yes --> Action1[set provision indication = provisioned]; Decision1 -- no --> Action2[set provision indication = not provisioned]; Action1 --> Decision2{calling subscriber in HPLMN country}; Decision2 -- yes --> Decision3{override category}; Decision2 -- no --> Action3[set override category = no]; Decision3 -- yes --> Action4[set override category = yes]; Decision3 -- no --> Action3; Action2 --> Decision4[/continue call handling/]; Action3 --> Decision4; Action4 --> Decision4; Decision4 --> Start2([idle]); +``` + +COLP: Connected Line Identification Presentation. + +Flowchart for Process COLP\_MAF005: Determination of connected line identification presentation subscription (VLR). + +**Figure 3.2: MAF005 Determination of connected line identification presentation subscription (VLR)** + +![Flowchart for Process COLP_MAF006 showing the determination of information for offering to the connected party. It starts with 'idle', followed by 'initiate handling of COLP', then checks if 'COLP provisioned', 'COL available', and 'presentation restricted'. Depending on these checks, it either passes additional COL, passes COL, or sets PI to 'number not available' before continuing call handling and returning to 'idle'.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +Process COLP\_MAF006 + +381\_33(1) + +Figure 3.3 + +``` +graph TD; idle1([idle]) --> initiate[initiate handling of COLP]; initiate --> provisioned{COLP provisioned}; provisioned -- no --> continue_handling{continue call handling}; provisioned -- yes --> available{COL available}; available -- no --> set_pi[set PI = number not available]; available -- yes --> restricted{presentation restricted}; restricted -- yes --> override{override category}; restricted -- no --> additional_available{additional COL available}; override -- yes --> additional_available; override -- no --> continue_handling; additional_available -- yes --> pass_additional1[pass additional COL]; additional_available -- no --> pass_col[pass COL]; additional_available -- yes --> additional_in_override{COL in case of override category}; additional_in_override --> additional_col[additional COL]; additional_col --> pass_additional2[pass additional COL]; pass_additional1 --> continue_handling; pass_col --> continue_handling; pass_additional2 --> continue_handling; set_pi --> continue_handling; continue_handling --> idle2([idle]); +``` + +COLP: Connected Line Identification Presentation. +COL: Connected Line Identity. +PI: Presentation Indicator. + +Flowchart for Process COLP\_MAF006 showing the determination of information for offering to the connected party. It starts with 'idle', followed by 'initiate handling of COLP', then checks if 'COLP provisioned', 'COL available', and 'presentation restricted'. Depending on these checks, it either passes additional COL, passes COL, or sets PI to 'number not available' before continuing call handling and returning to 'idle'. + +Figure 3.3: MAF006 Determination of the information for offering to the connected party (originating MSC) + +![Flowchart for Process COLP_MAF039. The process starts at an 'idle' state, proceeds to 'initiate handling of COLP', then checks if a 'connected number received'. If 'no', it goes to 'continue call handling'. If 'yes', it checks if to 'notify calling user of forwarding'. If 'yes', it goes to 'continue call handling'. If 'no', it 'set PI = presentation restricted' and then goes to 'continue call handling'. The process ends at an 'idle' state. A note defines COLP as Connected Line Identification Presentation and PI as Presentation Indicator.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +Process COLP\_MAF039 + +381\_34(1) + +Figure 3.4 + +``` +graph TD; idle1([idle]) --> initiate[initiate handling of COLP]; initiate --> connected{connected number received}; connected -- no --> continue{continue call handling}; connected -- yes --> notify{notify calling user of forwarding}; notify -- yes --> continue; notify -- no --> setPI[set PI = presentation restricted]; setPI --> continue; continue --> idle2([idle]); +``` + +COLP: Connected Line Identification Presentation. +PI: Presentation Indicator. + +Flowchart for Process COLP\_MAF039. The process starts at an 'idle' state, proceeds to 'initiate handling of COLP', then checks if a 'connected number received'. If 'no', it goes to 'continue call handling'. If 'yes', it checks if to 'notify calling user of forwarding'. If 'yes', it goes to 'continue call handling'. If 'no', it 'set PI = presentation restricted' and then goes to 'continue call handling'. The process ends at an 'idle' state. A note defines COLP as Connected Line Identification Presentation and PI as Presentation Indicator. + +Figure 3.4: MAF039 Interaction between COLP and call forwarding services (forwarding MSC) + +![Sequence diagram showing information flow for connected line identification presentation from MSa to MSb/TE via MSCa, VLRa, and MSCb/LE. The diagram includes messages like set-up, info req, info ack, and answer with various parameters (SI, PI, LI, aSI, aLI, OR1-OR5).](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +``` + +sequenceDiagram + participant MSa + participant MSCa + participant VLRa + participant MSCb/LE + participant MSb/TE + + Note right of VLRa: MAF 005 + + MSa->>MSCa: set-up + MSCa->>VLRa: info req + VLRa-->>MSCa: info ack + MSCa->>MSCb/LE: set-up + MSCb/LE->>MSb/TE: set-up + MSb/TE-->>MSCb/LE: answer ** + MSCb/LE-->>MSCa: answer (SI+PI+LI+aSI+aLI) + Note right of MSCa: MAF006 + MSCa-->>MSa: answer OR1:N + Note right of MSCa: OR1:Y + MSCa-->>MSa: answer OR2:c + Note right of MSCa: OR1:Y + MSCa-->>MSa: (PI) + Note right of MSCa: OR1:Y + MSCa-->>MSa: answer OR2:b + Note right of MSCa: OR3:N + MSCa-->>MSa: (PI) + Note right of MSCa: OR1:Y + MSCa-->>MSa: answer OR2:b + Note right of MSCa: OR3:Y + MSCa-->>MSa: (SI+PI+LI) + Note right of MSCa: OR1:Y + MSCa-->>MSa: answer OR2:b + Note right of MSCa: OR3:Y + MSCa-->>MSa: (SI+PI+LI) + Note right of MSCa: OR1:Y + MSCa-->>MSa: answer OR2:b + Note right of MSCa: OR3:Y + MSCa-->>MSa: (aSI+PI+aLI) + Note right of MSCa: OR1:Y + MSCa-->>MSa: answer OR2:a + Note right of MSCa: OR4:N + MSCa-->>MSa: (SI+PI+LI) + Note right of MSCa: OR1:Y + MSCa-->>MSa: answer OR2:a + Note right of MSCa: OR4:Y + MSCa-->>MSa: (aSI+PI+aLI) + +``` + +Sequence diagram showing information flow for connected line identification presentation from MSa to MSb/TE via MSCa, VLRa, and MSCb/LE. The diagram includes messages like set-up, info req, info ack, and answer with various parameters (SI, PI, LI, aSI, aLI, OR1-OR5). + +**Figure 3.5: Information flow for connected line identification presentation: mobile station to mobile station or fixed terminal** + +NOTE: OR1: COLP provisioned Y: yes N: no + OR2: Presentation Indicator Value a: allowed b: restricted c: not available + OR3: Override category + OR4: additional line identity available Y: yes N: no + OR5: COL in case of override category a: LI b: aLI + \*\*: A connected subaddress may be received from the MS + info: information SI: screening indicator aSI: additional screening indicator + req: request PI: presentation indicator + ack: acknowledge LI: line identity aLI: additional line identity + +## 3.3 Information stored in the HLR + +COLP may have the following logical states (refer to 3GPP TS 23.011 for an explanation of the notation): + +| Provisioning State | Registration State | Activation State | HLR Induction State | +|--------------------|--------------------|-----------------------|---------------------| +| (Not Provisioned, | Not Applicable, | Not Active, | Not Induced) | +| (Provisioned, | Not Applicable, | Active and Operative, | Not Induced) | + +The HLR shall store the logical state of COLP (which shall be one of the valid states listed above) on a per subscriber basis. + +The HLR shall also store the subscription option "override category" on a per subscriber basis. + +This parameter takes one of the following values: + +- yes; +- no. + +## 3.4 State transition model + +The following figure shows the successful cases of transition between the applicable logical states of COLP. The state changes are caused by actions of the service provider. + +Note that error cases are not shown in the diagram as they normally do not cause a state change. Additionally, some successful requests may not cause a state change. Hence they are not shown in the diagram. + +![State transition model for COLP diagram showing two states and two transitions.](40ef8b4d1d6b485e04c5edfeb6324b18_img.jpg) + +``` + +stateDiagram-v2 + state "(Not Provisioned, Not Applicable, Not Active, Not Induced)" as state1 + state "(Provisioned, Not Applicable, Active and Operative, Not Induced)" as state2 + state1 --> state2 : Provision + state2 --> state1 : Withdrawal + +``` + +The diagram illustrates the state transition model for COLP. It consists of two states represented by ovals. The left state is labeled "(Not Provisioned, Not Applicable, Not Active, Not Induced)". The right state is labeled "(Provisioned, Not Applicable, Active and Operative, Not Induced)". A curved arrow labeled "Provision" points from the left state to the right state. A curved arrow labeled "Withdrawal" points from the right state to the left state. + +State transition model for COLP diagram showing two states and two transitions. + +Figure 3.6: State transition model for COLP + +## 3.5 Transfer of information from HLR to VLR + +If the provisioning state for COLP is "Provisioned" then, when the subscriber registers on a VLR, the HLR shall send that VLR information about the logical state of COLP. The HLR shall send the override category if the VLR is in the HPLMN country. The HLR may send the override category if the VLR is outside the HPLMN country. + +If the logical state of COLP or the override category is changed while a subscriber is registered on a VLR then the HLR shall inform the VLR of the new logical state of COLP. If the override category is changed and the provisioning state of COLP is "Provisioned" then the HLR shall inform the VLR about the new override category when the VLR is in the HPLMN country. The HLR may inform the VLR about the new override category when the VLR is outside the HPLMN country. + +## 3.6 Information stored in the VLR + +For COLP, the VLR shall store the service state information and override category received from the HLR. + +If not received from the HLR (case of roaming outside the HPLMN country), the override category shall be set to the default value "no". + +## 3.7 Handover + +Handover will have no impact on the control procedures and the operation of the service. + +# 4 Connected line identification restriction (COLR) + +## 4.1 Handling of connected line identification restriction + +### 4.1.1 General + +If the terminating party has connected line identification restriction provisioned and it is impossible to indicate to the originating network (due to interworking) that the number should not be presented to the originating party, the connected line identity shall not be delivered to the originating network. + +### 4.1.2 Interrogation + +#### Status check + +The mobile subscriber can request the status of the supplementary service and be informed if the service is provided to him/her. This procedure is illustrated in figure 4.1. + +![Sequence diagram illustrating the interrogation of connected line identification restriction (COLR). The diagram shows four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence of messages is: 1. MS sends 'Interrogate COLR' to MSC. 2. MSC sends 'Interrogate COLR' to VLR. 3. VLR sends 'Acknowledge' back to MSC. 4. MSC sends 'Release Complete' back to MS. The HLR is shown but not involved in this sequence.](1dc5e74b1032f935e1b1ea3a9c876ac6_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: HLR is not involved in this sequence + MS->>MSC: Interrogate COLR + MSC->>VLR: Interrogate COLR + VLR-->>MSC: Acknowledge + MSC-->>MS: Release Complete + +``` + +Sequence diagram illustrating the interrogation of connected line identification restriction (COLR). The diagram shows four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence of messages is: 1. MS sends 'Interrogate COLR' to MSC. 2. MSC sends 'Interrogate COLR' to VLR. 3. VLR sends 'Acknowledge' back to MSC. 4. MSC sends 'Release Complete' back to MS. The HLR is shown but not involved in this sequence. + +Figure 4.1: Interrogation of connected line identification restriction + +## 4.2 Functions and information flows + +The following Mobile Additional Functions have been identified for the PLMN: + +### MAF040 + +Determination of the connected line identification restriction subscription + +The ability of a PLMN component to determine whether the supplementary service is provisioned for the mobile subscriber. See figure 4.2. + +Location: VLR. + +### MAF041 + +Determination of the connected party number for offering to the calling party + +The ability of a PLMN component to determine and to forward the connected line identity and related indications to the calling party. See figure 4.3. + +Location: terminating MSC. + +The information flow is shown in figures 4.4. + +![Flowchart for Process COLR_MAF040. It starts with 'idle', followed by 'initiate handling of COLR'. A decision diamond 'COLR provisioned' has 'yes' and 'no' paths. 'yes' leads to 'set provision indication = provisioned', 'no' leads to 'set provision indication = not provisioned'. Both paths merge at 'continue call handling', which leads to 'idle'. A note indicates 'COLR: Connected Line Identification Restriction.'](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +Process COLR\_MAF040 381\_42(1) + +Figure 4.2 + +``` +graph TD; idle1([idle]) --> initiate[initiate handling of COLR]; initiate --> provisioned{COLR provisioned}; provisioned -- yes --> set_provisioned[set provision indication = provisioned]; provisioned -- no --> set_not_provisioned[set provision indication = not provisioned]; set_provisioned --> continue{continue call handling}; set_not_provisioned --> continue; continue --> idle2([idle]); note[COLR: Connected Line Identification Restriction.]; +``` + +Flowchart for Process COLR\_MAF040. It starts with 'idle', followed by 'initiate handling of COLR'. A decision diamond 'COLR provisioned' has 'yes' and 'no' paths. 'yes' leads to 'set provision indication = provisioned', 'no' leads to 'set provision indication = not provisioned'. Both paths merge at 'continue call handling', which leads to 'idle'. A note indicates 'COLR: Connected Line Identification Restriction.' + +**Figure 4.2: MAF040 Determination of connected line identification restriction subscription (VLR)** + +![Flowchart for Process COLR_MAF041. It starts with 'idle', followed by 'initiate handling of COLR'. A decision diamond 'COLR provisioned' has 'yes' leading to 'set PI = presentation restricted' and 'no' leading to 'set PI = presentation allowed'. Both paths merge to 'continue call handling', which ends at 'idle'. A note defines COLR as Connected Line Identification Restriction and PI as Presentation Indicator.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +Process COLR\_MAF041 + +381\_43(1) + +Figure 4.3 + +``` +graph TD; idle1([idle]) --> initiate[initiate handling of COLR]; initiate --> provisioned{COLR provisioned}; provisioned -- yes --> set_restricted[set PI = presentation restricted]; provisioned -- no --> set_allowed[set PI = presentation allowed]; set_restricted --> continue{continue call handling}; set_allowed --> continue; continue --> idle2([idle]); +``` + +COLR: Connected Line Identification Restriction. +PI: Presentation Indicator. + +Flowchart for Process COLR\_MAF041. It starts with 'idle', followed by 'initiate handling of COLR'. A decision diamond 'COLR provisioned' has 'yes' leading to 'set PI = presentation restricted' and 'no' leading to 'set PI = presentation allowed'. Both paths merge to 'continue call handling', which ends at 'idle'. A note defines COLR as Connected Line Identification Restriction and PI as Presentation Indicator. + +Figure 4.3: MAF041 Determination of the presentation indicator + +![Sequence diagram showing information flow for connected line identification restriction from MS/TE to MSb via MSC/LE, VLRb, and MSCb.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +``` + +sequenceDiagram + participant MS/TE + participant MSC/LE + participant VLRb + participant MSCb + participant MSb + + MS/TE->>MSC/LE: set-up + MSC/LE->>MSCb: set-up + MSCb->>VLRb: info req + VLRb-->>MSCb: MAF040 + MSCb->>VLRb: info ack + MSCb->>MSb: set-up + MSb-->>MSCb: answer ** + MSCb->>MSC/LE: answer (SI+PI+LI) + Note right of MSCb: MAF041 +OR1:N +OR2:a + MSCb->>MSC/LE: answer (SI+PI+LI) + Note right of MSCb: OR1:Y +OR2:b + +``` + +Sequence diagram showing information flow for connected line identification restriction from MS/TE to MSb via MSC/LE, VLRb, and MSCb. + +**Figure 4.4: Information flow for connected line identification restriction: mobile station or fixed terminal to mobile station** + +NOTE: OR1: COLR provisioned Y: yes N: no + OR2: Presentation Indicator Value a: allowed + b: restricted + OR3: Override category + \*\*: A subaddress may be received from the MS + info: information SI: screening indicator + req: request PI: presentation indicator + ack: acknowledge LI: line identity + +## 4.3 Information stored in the HLR + +COLR may have the following logical states (refer to 3GPP TS 23.011 for an explanation of the notation): + +| Provisioning State | Registration State | Activation State | HLR Induction State | +|--------------------|--------------------|-----------------------|---------------------| +| (Not Provisioned, | Not Applicable, | Not Active, | Not Induced) | +| (Provisioned, | Not Applicable, | Active and Operative, | Not Induced) | + +The HLR shall store the logical state of COLR (which shall be one of the valid states listed above) on a per subscriber basis. + +## 4.4 State transition model + +The following figure shows the successful cases of transition between the applicable logical states of COLR. The state changes are caused by actions of the service provider. + +Note that error cases are not shown in the diagram as they normally do not cause a state change. Additionally, some successful requests may not cause a state change. Hence they are not shown in the diagram. + +![State transition model for COLR diagram showing two states and two transitions.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +``` + +stateDiagram-v2 + [*] --> State1 : Provision + State1 --> [*] : Withdrawal + state " (Not Provisioned, Not Applicable, Not Active, Not Induced) " as State1 + state " (Provisioned, Not Applicable, Active and Operative, Not Induced) " as State2 + +``` + +The diagram illustrates the state transition model for COLR. It consists of two states represented by ovals. The left state is labeled "(Not Provisioned, Not Applicable, Not Active, Not Induced)". The right state is labeled "(Provisioned, Not Applicable, Active and Operative, Not Induced)". A curved arrow labeled "Provision" points from the left state to the right state. A curved arrow labeled "Withdrawal" points from the right state back to the left state. + +State transition model for COLR diagram showing two states and two transitions. + +**Figure 4.5: State transition model for COLR** + +## 4.5 Transfer of information from HLR to VLR + +When the subscriber registers on a VLR, the HLR shall send that VLR information about the logical state of COLR. + +If the logical state of COLR is changed while a subscriber is registered on a VLR then the HLR shall inform the VLR of the new logical state of COLR. + +## 4.6 Information stored in the VLR + +For COLR, the VLR shall store the service state information received from the HLR. + +## 4.7 Handover + +Handover will have no impact on the control procedures and the operation of the service. + +## 4.8 Interworking + +The VPLMN needs to distinguish three cases in order to meet data privacy requirements in an environment where support of COLP and COLR is optional: + +- the HPLMN supports COLR, and COLR is provisioned for the subscriber; +- the HPLMN supports COLR, but COLR is not provisioned for the subscriber; +- the HPLMN does not support COLR. + +In case a) the VPLMN must apply the COLR subscription as indicated by the data sent by the HPLMN. + +In case b) the VPLMN must not apply COLR. + +In case c) the VPLMN must apply an implicit COLR subscription. + +To allow the VPLMN to make this distinction, the HLR and VLR behave as follows: + +- If the HLR supports COLR, but COLR is not provisioned for the subscriber, the HLR shall inform the VLR that COLR is not provisioned. +- If the VLR supports COLR, but the HLR does not support COLR, the VLR shall behave in the same way as if COLR was provisioned for the subscriber, i.e. the connected line identity shall not be displayed to the calling subscriber unless the calling subscriber has COLR override capability. When interrogating the service status the subscriber shall be informed that COLR is provided to him and is active. + +# Annex A (informative): Mapping of CLI + +This annex defines the mapping rules of CLI parameters received via the NW-NW interface to CLI parameters to be sent to the MS. + +| | Information received over the NW-NW interface | | | | | Information sent to the MS | | | +|--------------------------------------------|-----------------------------------------------|---------------|-----------------------------------|--------------------------|--------------------------------|----------------------------|------------------------------------|--------------------------------| +| | presentation indicator | line identity | additional presentation indicator | additional line identity | Cause of No CLI | presentation indicator | line identity | Cause of No CLI | +| CLIP not provisioned | * | * | * | * | * | - | - | - | +| CLIP provisioned without override category | - | - | - | - | - | not available | - | - | +| | not available | - | - | - | - | not available | - | - | +| | allowed | digits | - | - | - | allowed | digits of line identity | - | +| | allowed | digits | + | digits | - | allowed | digits of additional line identity | - | +| | restricted | digits | * | * | - | restricted | - | - | +| | restricted | digits | * | * | unavailable | restricted | - | unavailable | +| | restricted | digits | * | * | reject by user | restricted | - | reject by user | +| | restricted | digits | * | * | interaction with other service | restricted | - | interaction with other service | +| | restricted | digits | * | * | payphone | restricted | - | payphone | +| | restricted by network | digits | - | - | - | not available | - | - | +| | restricted by network | digits | allowed | digits | - | allowed | digits of additional line identity | - | + +| | Information received over the NW-NW interface | | | | | Information sent to the MS | | | +|------------------------------------------------|-----------------------------------------------|---------------|-----------------------------------|--------------------------|--------------------------------|----------------------------|------------------------------------|--------------------------------| +| | presentation indicator | line identity | additional presentation indicator | additional line identity | Cause of No CLI | presentation indicator | line identity | Cause of No CLI | +| CLIP provisioned with override category | - | - | - | - | - | not available | - | - | +| | not available | - | - | - | - | not available | - | - | +| | allowed | digits | - | - | - | allowed | digits of line identity | - | +| | allowed | digits | + | digits | - | allowed | digits of additional line identity | - | +| | restricted | digits | - | - | - | restricted | digits of line identity | - | +| | restricted | digits | + | digits | - | restricted | NOTE 1 | - | +| | restricted | digits | + | digits | unavailable | restricted | NOTE 1 | unavailable | +| | restricted | digits | + | digits | reject by user | restricted | NOTE 1 | reject by user | +| | restricted | digits | + | digits | interaction with other service | restricted | NOTE 1 | interaction with other service | +| | restricted | digits | + | digits | payphone | restricted | NOTE 1 | payphone | +| | restricted | digits | - | - | unavailable | restricted | digits of line identity | unavailable | +| | restricted | digits | - | - | reject by user | restricted | digits of line identity | reject by user | +| | restricted | digits | - | - | interaction with other service | restricted | digits of line identity | interaction with other service | +| | restricted | digits | - | - | payphone | restricted | digits of line identity | payphone | +| | restricted by network | digits | - | - | - | restricted | digits of line identity | - | +| | restricted by network | digits | allowed | digits | - | allowed | digits of additional line identity | - | + +- parameter not present + +\* parameter absent or present, if present it may have any value + ++ parameter present, it may have any value + +NOTE 1: Network Option to send either digits of the line identity or digits of additional line identity applies. + +# Annex B (informative): Change history + +| Change history | | | | | | | +|----------------|-----------|---------|--------|---------|-------------|---------------------------------------------------------------| +| TSG CN# | Spec | Version | CR | | New Version | Subject/Comment | +| Apr 1999 | GSM 03.81 | 7.0.0 | | | | Transferred to 3GPP CN1 | +| CN#03 | 23.081 | | | R99 | 3.0.0 | Approved at CN#03 | +| | 23.081 | 3.0.0 | | R99 | 3.0.1 | Upgrade of references from 2G to 3G | +| CN#08 | 23.081 | 3.0.1 | | R99 | 3.1.0 | Enhanced handling of presentation indicators for CLIP | +| CN#11 | 23.081 | 3.1.0 | | Rel-4 | 4.0.0 | Release 4 after CN#11 | +| CN#16 | 23.081 | 4.0.0 | | Rel-5 | 5.0.0 | Release 5 after CN#16 | +| CN#17 | 23.081 | 5.0.0 | 0006 | Rel-5 | 5.1.0 | Correction of 'Cause of no CLI' handling in SDLs | +| CN#19 | 23.081 | 5.1.0 | 0007r1 | Rel-5 | 5.2.0 | Correction to interworking between CLIP enhancement and CAMEL | +| CN#25 | 23.081 | 5.2.0 | 0008 | Rel-6 | 6.0.0 | Editorial correction of table definition | +| CT#36 | 23.081 | 6.0.0 | | Rel-7 | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 23.081 | 7.0.0 | | Rel-8 | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | - | 8.0.0 | - | Rel-9 | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | - | 9.0.0 | - | Rel-10 | 10.0.0 | Update to Rel-10 version (MCC) | +| 2011-12 | 23.081 | 10.0.0 | 0009 | Rel-11 | 11.0.0 | CLI interactions with ACR | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23086/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-11/23_series/23086/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc087fab509fec403dd74d5f7d46f98bce101476 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23086/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/Rel-11/23_series/23086/41a438d7e4adc17c3a4005e7c9500091_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c63a2919d0755dcbbfb95c2a06210b82441e644b --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23086/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-11/23_series/23086/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6c7d7b3fb49aca05d08618e1b90bfef710ce9c8 --- /dev/null +++ b/marked/Rel-11/23_series/23086/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f16c5137920581f5f87a061914605f27c42f5b16c5d22e32feef92cf808a8b1f +size 101266 diff --git a/marked/Rel-11/23_series/23086/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-11/23_series/23086/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..524b0f559cc8e234eaa3ae74f61b14c015489bad --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23086/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-11/23_series/23086/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b636acd1726d8fd2a56690ac5e59cae10c606120 --- /dev/null +++ b/marked/Rel-11/23_series/23086/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aff40eacfa89749dcef6d78777534102608a64ad8ed59a6217fae00b839d570e +size 103119 diff --git a/marked/Rel-11/23_series/23086/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-11/23_series/23086/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cff121845b431233836c318d84e0b186f0bdb5b8 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23086/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-11/23_series/23086/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9764fdacc98cc79d20584c080fe5a74cb43c4e3f --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23086/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Rel-11/23_series/23086/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee2bd4c9bc9ce5492ee39e6d29bb4dec8c72444e --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23086/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-11/23_series/23086/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d1d53d0d2baf135e143872d4ecc896222a38d54 --- /dev/null +++ b/marked/Rel-11/23_series/23086/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4802cebd9bb7d32ca9161d73d7576706254ad9d926514188980d365f88e4a35 +size 120077 diff --git a/marked/Rel-11/23_series/23086/raw.md b/marked/Rel-11/23_series/23086/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..459f1354c01d033e4505e4ea083f345690d7c2b5 --- /dev/null +++ b/marked/Rel-11/23_series/23086/raw.md @@ -0,0 +1,506 @@ + + + + + + +# --- 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 process 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 'generate CAI', then 'send CAI', and finally '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 + [*] --> start + start --> call_in_progress_or_call_set_up_in_progress : call in progress or call set up in progress + call_in_progress_or_call_set_up_in_progress --> request_generation_of_CAI : request generation of CAI + request_generation_of_CAI --> generate_CAI : generate CAI + generate_CAI --> send_CAI : send CAI + send_CAI --> continue_call_or_call_set_up : 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 process 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 'generate CAI', then 'send CAI', and finally '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 for successful originated call, successful terminated call, and charge modification scenarios.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +The diagram illustrates the information flow for Advice of Charge (Information) across three scenarios: + +- Successful MS originated call set-up with AoC (Information)**: + - MS sends a **set-up** message to MSC. + - MSC sends a **send information** message to VLR. + - VLR responds with **o/g call set-up** and **complete call** messages to MSC. + - MSC sends a **B answer** message to MS. + - MSC sends **charging information** to MS. + - MS responds with an **AoC acknowledge** message to MSC. +- Successful MS terminated call set-up with AoC (Information)**: + - MSC receives an **IAM** message from the network. + - MSC sends a **send information** message to VLR. + - VLR responds with **i/c call set-up** and **complete call** messages to MSC. + - MSC sends a **B answer** message to MS. + - MSC sends **charging information** to MS. + - MS responds with an **AoC acknowledge** message to MSC. +- MS unable to charge, AoCI, originated and terminated call set-up**: + - MSC sends **charging information** to MS. +- Charge modification, AoC (Information)**: + - MSC sends **charging information** to MS. + - MS responds with an **AoC acknowledge** message to MSC. + +Sequence diagrams showing information flow for Advice of Charge (Information) between MS, MSC, and VLR for successful originated call, successful terminated call, and charge modification scenarios. + +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 back 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 state machines. The left one starts at 'call in progress or call set up in progress', goes through 'request generation of CAI' (with a note: 'Request of generation of CAI applies to AoC initiation or charge modification.'), 'generate CAI', 'send CAI', and 'start timer T(AoC)' to reach 'wait for AoC acknowledge'. The right one starts at 'wait for AoC acknowledge' and branches into three paths: 'AoC acknowledge' leading to 'stop timer T(AoC)' and 'call in progress'; 'timer T(AoC) expired' leading to 'clear call' and 'idle'; and 'call cleared' leading to 'stop timer T(AoC)' and 'idle'. A note at the bottom defines 'CAI: Charge Advice Information'.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Process AoCC\_MSC 386\_21(1) + +``` +stateDiagram-v2 + [*] --> call_in_progress_or_call_set_up_in_progress : call in progress or call set up in progress + call_in_progress_or_call_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_L : wait for AoC acknowledge + + [*] --> wait_for_AoC_acknowledge_R : wait for AoC acknowledge + wait_for_AoC_acknowledge_R --> AoC_acknowledge : AoC acknowledge + wait_for_AoC_acknowledge_R --> timer_T_AoC_expired : timer T(AoC) expired + wait_for_AoC_acknowledge_R --> call_cleared : call cleared + AoC_acknowledge --> stop_timer_T_AoC_L : stop timer T(AoC) + stop_timer_T_AoC_L --> call_in_progress : call in progress + timer_T_AoC_expired --> clear_call : clear call + clear_call --> idle + call_cleared --> stop_timer_T_AoC_R : stop timer T(AoC) + stop_timer_T_AoC_R --> idle + + note right of start_timer_T_AoC : CAI: Charge Advice Information +``` + +SDL diagram for advice of charge (charging) in the MSC. The diagram shows two state machines. The left one starts at 'call in progress or call set up in progress', goes through 'request generation of CAI' (with a note: 'Request of generation of CAI applies to AoC initiation or charge modification.'), 'generate CAI', 'send CAI', and 'start timer T(AoC)' to reach 'wait for AoC acknowledge'. The right one starts at 'wait for AoC acknowledge' and branches into three paths: 'AoC acknowledge' leading to 'stop timer T(AoC)' and 'call in progress'; 'timer T(AoC) expired' leading to 'clear call' and 'idle'; and 'call cleared' leading to 'stop timer T(AoC)' and 'idle'. A note at the bottom defines 'CAI: Charge Advice Information'. + +Figure 2.1: SDL diagram of advice of charge (charging) in the MSC + +![SDL diagram of advice of charge (charging) in the mobile equipment. The process starts with 'call set up in progress', followed by 'charging information'. A decision 'CAI = 0' leads to 'AoC acknowledge' (yes) or 'ACM >= ACMmax' (no). From 'ACM >= ACMmax', 'yes' leads to 'clear call' and 'no' leads to 'start charge calculations'. 'start charge calculations' leads to 'AoC acknowledge', which leads to 'AoC active'. From 'AoC active', three paths emerge: 'ACM >= ACMmax' (yes) leads to 'stop charge calculations' then 'clear call'; 'call ends' leads to 'stop charge calculations' then 'AoC inactive'; 'charging information' leads to 'CAI = 0' (yes) then 'AoC acknowledge' then 'stop charge calculations' then 'AoC inactive', or (no) then 'AoC acknowledge' then 'amend charging calculations' then 'AoC active'. A note indicates that charging calculations can be amended before or after sending the AoC acknowledge. Another note states that a mobile originated call set-up shall not be allowed if ACM >= ACMmax.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Process AoCC\_ME + +386\_22(1) + +``` + +stateDiagram-v2 + [*] --> call_set_up_in_progress : call set up in progress + call_set_up_in_progress --> charging_information_1 : charging information + charging_information_1 --> CAI_0_1 : CAI = 0 + CAI_0_1 --> AoC_acknowledge_1 : AoC acknowledge (yes) + CAI_0_1 --> ACM_leq_ACMmax_1 : ACM >= ACMmax (no) + AoC_acknowledge_1 --> AoC_inactive_1 : AoC inactive + AoC_inactive_1 --> charging_information_2 : charging information + AoC_inactive_1 --> call_ends_1 : call ends + call_ends_1 --> clear_call_1 : clear call + charging_information_2 --> CAI_0_2 : CAI = 0 + CAI_0_2 --> AoC_acknowledge_2 : AoC acknowledge (yes) + CAI_0_2 --> AoC_inactive_2 : AoC inactive (no) + ACM_leq_ACMmax_1 --> clear_call_2 : clear call (yes) + ACM_leq_ACMmax_1 --> start_charge_calculations : start charge calculations (no) + start_charge_calculations --> AoC_acknowledge_3 : AoC acknowledge + AoC_acknowledge_3 --> AoC_active : AoC active + AoC_active --> ACM_leq_ACMmax_2 : ACM >= ACMmax + ACM_leq_ACMmax_2 --> stop_charge_calculations_1 : stop charge calculations (yes) + stop_charge_calculations_1 --> clear_call_3 : clear call + ACM_leq_ACMmax_2 --> call_ends_2 : call ends + call_ends_2 --> stop_charge_calculations_2 : stop charge calculations + stop_charge_calculations_2 --> AoC_inactive_3 : AoC inactive + ACM_leq_ACMmax_2 --> charging_information_3 : charging information + charging_information_3 --> CAI_0_3 : CAI = 0 + CAI_0_3 --> AoC_acknowledge_4 : AoC acknowledge (yes) + AoC_acknowledge_4 --> stop_charge_calculations_3 : stop charge calculations + stop_charge_calculations_3 --> AoC_inactive_4 : AoC inactive + CAI_0_3 --> AoC_acknowledge_5 : AoC acknowledge (no) + AoC_acknowledge_5 --> amend_charging_calculations : amend charging calculations + amend_charging_calculations --> AoC_active_2 : AoC active + +``` + +A mobile originated call set-up shall not be allowed if $ACM \geq ACM_{max}$ + +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. The process starts with 'call set up in progress', followed by 'charging information'. A decision 'CAI = 0' leads to 'AoC acknowledge' (yes) or 'ACM >= ACMmax' (no). From 'ACM >= ACMmax', 'yes' leads to 'clear call' and 'no' leads to 'start charge calculations'. 'start charge calculations' leads to 'AoC acknowledge', which leads to 'AoC active'. From 'AoC active', three paths emerge: 'ACM >= ACMmax' (yes) leads to 'stop charge calculations' then 'clear call'; 'call ends' leads to 'stop charge calculations' then 'AoC inactive'; 'charging information' leads to 'CAI = 0' (yes) then 'AoC acknowledge' then 'stop charge calculations' then 'AoC inactive', or (no) then 'AoC acknowledge' then 'amend charging calculations' then 'AoC active'. A note indicates that charging calculations can be amended before or after sending the AoC acknowledge. Another note states that a mobile originated call set-up shall not be allowed if ACM >= ACMmax. + +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 diagrams for Advice of Charge (Charging) involving MS (Mobile Station), MSC (Mobile Switching Center), and VLR (Visitor Location Register). + +**Successful MS originated call set-up with AoC (Charging)** + +- MS sends a **set-up** message to MSC. +- MSC sends **send information** to VLR. +- VLR responds with **o/g call set-up** to MSC. +- MSC sends **complete call** to VLR. +- VLR sends **B answer** to MSC. +- MSC sends **charging information** to MS. +- MS responds with **AoC acknowledge** to MSC. +- MSC starts timer **T(AoC)**. +- MSC stops timer **T(AoC)**. + +**Successful MS terminated call set-up with AoC (Charging)** + +- MSC receives **IAM** from an external source. +- MSC sends **send information** to VLR. +- VLR responds with **i/c call set-up** to MSC. +- MSC sends **complete call** to VLR. +- VLR sends **B answer** to MSC. +- MSC sends **charging information** to MS. +- MS responds with **AoC acknowledge** to MSC. +- MSC starts timer **T(AoC)**. +- MSC stops timer **T(AoC)**. + +**Charge modification, AoC (Charging)** + +- MSC sends **charging information** to MS. +- MS responds with **AoC acknowledge** to MSC. +- MSC starts timer **T(AoC)**. +- MSC stops 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 call, successful terminated call, and charge modification.](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. +- 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 call, successful terminated call, and charge modification. + +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 S1 + state " (Provisioned, Not Applicable, Active and Operative, Not Induced) " as S2 + S1 --> S2 : Provision + S2 --> S1 : 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 + +| Change history | | | | | | | | | +|----------------|-----------|---------|------|-----|--------|-----|---------|--------------------------------------| +| TSG CN# | Spec | Old Ver | CR | Rev | Phase | Cat | New Ver | Subject/Comment | +| Apr 1999 | GSM 03.86 | 6.0.0 | | | R97 | | | Transferred to 3GPP CN1 | +| CN#03 | 23.086 | | | | R99 | | 3.0.0 | Approved at CN#03 | +| | 23.086 | 3.0.0 | | | R99 | | 3.0.1 | Reference list updated from 2G to 3G | +| CN#09 | 23.086 | 3.0.1 | 001 | 1 | R99 | F | 3.1.0 | SDL refresh | +| CN#11 | 23.086 | 3.1.0 | | | Rel-4 | | 4.0.0 | Release 4 after CN#11 | +| CN#16 | 23.086 | 4.0.0 | | | Rel-5 | | 5.0.0 | Release 5 after CN#16 | +| CN#26 | 23.086 | 5.0.0 | | | Rel-6 | | 6.0.0 | Release 6 after CN#26 | +| CT#30 | 23.086 | 6.0.0 | 0002 | | Rel-6 | | 6.1.0 | Incorrect References | +| CT#36 | 23.086 | 6.1.0 | | | Rel-7 | | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 23.086 | 7.0.0 | | | Rel-8 | | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | 23.086 | 8.0.0 | - | - | Rel-9 | | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | 23.086 | 9.0.0 | - | - | Rel-10 | | 10.0.0 | Update to Rel-10 version (MCC) | +| 2012-09 | 23.086 | 10.0.0 | - | - | Rel-11 | | 11.0.0 | Update to Rel-11 version (MCC) | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23087/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-11/23_series/23087/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50da8321d787b0053a66620a821b9115a557b26d --- /dev/null +++ b/marked/Rel-11/23_series/23087/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bdbafedc1681c523d35e4564408df668f57aaac255a3b931f33f031bf6a8669 +size 63318 diff --git a/marked/Rel-11/23_series/23087/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-11/23_series/23087/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b180f45e46397155bd57ad99d8f01c42c561ea83 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23087/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-11/23_series/23087/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6254c734aadc80aed2db5dc8a5124482c1529411 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23087/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-11/23_series/23087/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d34c67818369606356eda0c8194b30795198375b --- /dev/null +++ b/marked/Rel-11/23_series/23087/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06643c93553721bc5f96747c29a8ef84a28d8a2d8db6c772b74e241174180f04 +size 101839 diff --git a/marked/Rel-11/23_series/23087/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-11/23_series/23087/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11e3f2987126b26cdac35a4066796bbd40eb30d9 --- /dev/null +++ b/marked/Rel-11/23_series/23087/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3409325ab62621353171b94599d38072d8c82737b7f0244181f754e9aded7cc3 +size 63397 diff --git a/marked/Rel-11/23_series/23087/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-11/23_series/23087/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ca616d10bbcd8fb8e615c2c5554331352f1249d --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23087/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-11/23_series/23087/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7383966bb7161c8d06f90e1e0c041051575d1e30 --- /dev/null +++ b/marked/Rel-11/23_series/23087/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82088ac907664a1bcef8d7cd91fe0dd8cb7c5cbca759fbb575333b312d5883da +size 71106 diff --git a/marked/Rel-11/23_series/23087/392a79ccd95e682ccd08f35ab2e64144_img.jpg b/marked/Rel-11/23_series/23087/392a79ccd95e682ccd08f35ab2e64144_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8382d510bb34bf3908b523a44ca9ed02c97e62ce --- /dev/null +++ b/marked/Rel-11/23_series/23087/392a79ccd95e682ccd08f35ab2e64144_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5e199eed8f1c72cb3456e35ab77fce9494ac13a77f44069997a8e2dc0d304d7 +size 95263 diff --git a/marked/Rel-11/23_series/23087/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-11/23_series/23087/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..606d78c4bec711b9c72e019e8c8de9d8aad79211 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23087/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-11/23_series/23087/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..339e734989e55efccb1de7aba564dec8297d8c0c --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23087/552328a9daaf3bc0069424b500025880_img.jpg b/marked/Rel-11/23_series/23087/552328a9daaf3bc0069424b500025880_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1df0f39384654a283e240a08af1149a5be541b3a --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23087/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-11/23_series/23087/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30e7381c617ba76617b32122c5387f644d92b126 --- /dev/null +++ b/marked/Rel-11/23_series/23087/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3e5c60adbe3e601270d15be1081d0ce093e4bc7413f69d06e03af484330784c +size 62574 diff --git a/marked/Rel-11/23_series/23087/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-11/23_series/23087/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e0fbd1e766191e3c35d2f6d3bd032989ad9ab4e --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23087/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg b/marked/Rel-11/23_series/23087/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bd261b68afa47db99fb4bed5f80620178fb69b9 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23087/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/Rel-11/23_series/23087/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3db80415db866fe4f44dba27aec1089fda5adbf3 --- /dev/null +++ b/marked/Rel-11/23_series/23087/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69dd3114b52f29e320819b098192a6e1e1ab8bc39063bbb352f16fac70a70d2a +size 60691 diff --git a/marked/Rel-11/23_series/23087/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-11/23_series/23087/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab3c05394f1081876c62cb55b69bb3fd2ca147b5 --- /dev/null +++ b/marked/Rel-11/23_series/23087/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc277853a4a1e04273ebecec592f26f0c465ed78533400c0b479f79c72480b4c +size 71035 diff --git a/marked/Rel-11/23_series/23087/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-11/23_series/23087/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcf68fc0073286d47dcbca63b6694bbdcd22cea4 --- /dev/null +++ b/marked/Rel-11/23_series/23087/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f41726df1ea978ba21a879ab382b81c83912db18216fe0e88d9265b8ea925ff +size 74975 diff --git a/marked/Rel-11/23_series/23087/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/23_series/23087/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ba5fd68fbbaa9064a932035794914a470e97792 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23087/84db9bf6e93779b67aa320d1dfd38d91_img.jpg b/marked/Rel-11/23_series/23087/84db9bf6e93779b67aa320d1dfd38d91_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ebf7b814e982eedef175884d6c9fa4ffb73f2738 --- /dev/null +++ b/marked/Rel-11/23_series/23087/84db9bf6e93779b67aa320d1dfd38d91_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:350edbe83e67f865f0b49fa4d4e8f20b832fad329c20e8b83aade9b7a9af35d3 +size 32393 diff --git a/marked/Rel-11/23_series/23087/853f59c89931a666c07903b31d098277_img.jpg b/marked/Rel-11/23_series/23087/853f59c89931a666c07903b31d098277_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb971a26e3671d5b0afd13d5612549d35d772af7 --- /dev/null +++ b/marked/Rel-11/23_series/23087/853f59c89931a666c07903b31d098277_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec7cb88fbcc25f3581800b89e4e2418687695ea438d21445750799b645a348f9 +size 59049 diff --git a/marked/Rel-11/23_series/23087/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-11/23_series/23087/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15b2b3e9c2e2d50bf3eaab32f2ffc86fb300d637 --- /dev/null +++ b/marked/Rel-11/23_series/23087/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2d9c1f0d1d3386b4702ebe8eb65281b86b4b6667cdf041cc7bccaa38288680e +size 100295 diff --git a/marked/Rel-11/23_series/23087/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-11/23_series/23087/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..131f5d19dcaebd162ffb6ac11726a4e9d3b1aa22 --- /dev/null +++ b/marked/Rel-11/23_series/23087/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:453ce5092aec3654450939296c8573907810c222d5b3da102a39e2b54ce7dd2b +size 113063 diff --git a/marked/Rel-11/23_series/23087/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-11/23_series/23087/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7ae12c7c9b82f22a8de8aa8461527e22ad5a6b3 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23087/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-11/23_series/23087/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0dcadac7d269d73200cb4b4543e304b7e1630917 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23087/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-11/23_series/23087/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32f069c19ff450a8ed3bb89d51f59aebb1566a01 --- /dev/null +++ b/marked/Rel-11/23_series/23087/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13048aae1ebd3d8c085077aeeda3884fcb001ef1647162be711361acbc1f7a3f +size 104542 diff --git a/marked/Rel-11/23_series/23087/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-11/23_series/23087/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..918b4f60ab061cb1f0cec9a8f7fe147e79c1727d --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23087/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Rel-11/23_series/23087/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1d0a72f14587dd766240919f474382acdcf77d6 --- /dev/null +++ b/marked/Rel-11/23_series/23087/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69983c04d19dbe4b91d06317581fd3d5b784deb2532841a38a303400d2e19aa2 +size 58751 diff --git a/marked/Rel-11/23_series/23087/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-11/23_series/23087/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bc6174b999c92c51f4d3f0c8f69002e11164df3 --- /dev/null +++ b/marked/Rel-11/23_series/23087/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08f41ea6f1649806b85e0d74d881a6090f0decab91aa065605e5cab9d7012dfb +size 121878 diff --git a/marked/Rel-11/23_series/23087/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-11/23_series/23087/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f70bceeff80082572bd15291a3411db6b3df3f34 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23087/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-11/23_series/23087/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2a61fc9205e84e800241c0c8943ed5759845394 --- /dev/null +++ b/marked/Rel-11/23_series/23087/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51d74ae8db364c8c9ed10a2e1871ff47798004fdc5682970e4a5fe37f1093ce7 +size 98552 diff --git a/marked/Rel-11/23_series/23087/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-11/23_series/23087/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8afb289f27dfa563f9e7fdbf373748d6d6d81f02 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23087/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Rel-11/23_series/23087/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ee18a1d2f186320c9fc9232a69218090a330012 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23087/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Rel-11/23_series/23087/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91defca32a99c6f2b8e7ccbe0acf1e4c2989da05 --- /dev/null +++ b/marked/Rel-11/23_series/23087/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c46f69157e174fd40be00857f8aa0efdc7efd6bb69e0f3f6dcf708315e9322c4 +size 116629 diff --git a/marked/Rel-11/23_series/23087/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-11/23_series/23087/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e20963897d8bd673e029b4e106fb61bee3d11fef --- /dev/null +++ b/marked/Rel-11/23_series/23087/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:621d63984e4726a39eb22f877b698ec3627818a72581a63a9b511629aeae8628 +size 104726 diff --git a/marked/Rel-11/23_series/23087/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-11/23_series/23087/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84baadfc63c80e1e90a1e1e2349689156276654e --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23087/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/marked/Rel-11/23_series/23087/e29665b8abcea967ef289c6aff07ae4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6f2521630e7ca688cfdf9757292219e9926ec71 --- /dev/null +++ b/marked/Rel-11/23_series/23087/e29665b8abcea967ef289c6aff07ae4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4f96e5088ac4398c67669f85137319c2981345c82544eaaf9c9064a87382337 +size 69638 diff --git a/marked/Rel-11/23_series/23087/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-11/23_series/23087/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50c8eeef01fc0d6376362d212110994999061f5b --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23087/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-11/23_series/23087/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48e80e59cea1ad8b59b243ae4007a618f3b2b2ba --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23087/raw.md b/marked/Rel-11/23_series/23087/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..bf86d0f101bd0d26d2018bad4e9e582c6d915646 --- /dev/null +++ b/marked/Rel-11/23_series/23087/raw.md @@ -0,0 +1,1692 @@ + + + + + + +# 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', receives an 'Activation UUS1 request', checks if 'UUS1 provisioned'. If 'no', it sets 'Set indication = UUS1 not available'. If 'yes', it sets '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]) --> Request{Activation UUS1 request}; Request --> Provisioned{UUS1 provisioned}; Provisioned -- no --> NotAvailable[Set indication = UUS1 not available]; Provisioned -- yes --> Available[set indication = UUS1 available]; NotAvailable --> Continue{continue call handling}; Available --> Continue; Continue --> Idle2([Idle]) +``` + +Flowchart for Process MAF043 showing information flows for UUS1. The process starts at 'Idle', receives an 'Activation UUS1 request', checks if 'UUS1 provisioned'. If 'no', it sets 'Set indication = UUS1 not available'. If 'yes', it sets '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. The diagram illustrates the exchange of messages like Set-up, SIFOC, Complete call, IAM, SRI, ACM/ANM/CPG, CON, and REL, with associated User-to-User Information (UUI and UUI*).](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +The sequence diagram illustrates the information flow for a UUS1 implicit request (mobile to mobile call) involving the following entities: MSa, MSCa, VLRa, GMSCb, HLRb, MSCb, and MSb. The interaction proceeds as follows: + +- MSa sends a **Set-up** message to MSCa with **UUI\***. +- MSCa sends a **SIFOC** message to VLRa. +- VLRa sends a **Complete call** message back to MSCa. +- MSCa sends an **IAM** message to GMSCb with **UUI\***. +- GMSCb sends an **SRI** message to HLRb. +- HLRb responds with an **SRI ack** message. +- GMSCb sends an **IAM** message to MSCb with **UUI\***. +- MSCb sends a **Set-up** message to MSb with **UUI\***. +- MSb responds with an **Alert** message to MSCb with **UUI**. +- MSCb sends an **ACM/ANM/CPG** message to GMSCb with **UUI**. +- GMSCb sends an **ACM/ANM/CPG** message to MSCa with **UUI**. +- MSCa sends an **Alert** message to MSa with **UUI**. +- GMSCb sends a **CON** message to MSCb with **UUI**. +- MSCb sends a **Connect** message to MSb with **UUI**. +- GMSCb sends a **CON** message to MSCa with **UUI**. +- MSCa sends a **Connect** message to MSa with **UUI**. +- MSa sends a **Disconnect** message to MSCa with **UUI**. +- MSCa sends a **REL** message to GMSCb with **UUI**. +- GMSCb sends a **REL** message to MSCb with **UUI**. +- MSCb sends a **Disconnect** message to MSb with **UUI**. + +**Note:** + +- UUI\*** User-to-user information required for requesting the UUS service +- UUI** User-to-user information can be sent optionally + +Sequence diagram showing information flow for UUS1 implicit 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, Complete call, IAM, SRI, ACM/ANM/CPG, CON, and REL, with associated User-to-User Information (UUI and UUI\*). + +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 + GMSCb->>HLRb: S1=p; 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). Lifelines: MSa, MSCa, VLRa, GMSCb, HLRb, MSCb, MSb. The diagram shows the exchange of messages like Set-up, SIFOC, Complete call, IAM, SRI, SRI ack, ACM/ANM/CPG, CON, User info, UUI, and REL between these entities.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +sequenceDiagram + participant MSa + participant MSCa + participant VLRa + participant GMSCb + participant HLRb + participant MSCb + participant MSb + + Note left of MSa: Note: S3 UUS Service 3 +UUI User-to-user information +r,nr requested, not required +p provided + + MSa->>MSCa: Set-up + Note right of MSCa: S3=r,nr + MSCa->>VLRa: SIFOC + Note right of VLRa: + VLRa->>MSCa: Complete call + Note right of MSCa: + MSCa->>GMSCb: IAM + Note right of GMSCb: S3=r,nr + GMSCb->>HLRb: SRI + Note right of HLRb: + HLRb->>GMSCb: SRI ack + Note right of GMSCb: + GMSCb->>MSCb: IAM + Note right of MSCb: + MSCb->>MSb: Set-up + Note right of MSb: S3=r,nr + MSb->>MSCb: Alert + Note right of MSCb: + MSCb->>GMSCb: ACM/ANM/CPG + Note right of GMSCb: + GMSCb->>MSCa: CON + Note right of MSCa: S3=p + MSCa->>MSa: Connect + Note right of MSa: S3=p + MSa->>MSCa: User info + Note right of MSCa: + MSCa->>GMSCb: UUI + Note right of GMSCb: + GMSCb->>MSCb: User info + Note right of MSCb: + MSCb->>MSb: UUI + Note right of MSb: + MSb->>MSCb: User info + Note right of MSCb: + MSCb->>GMSCb: UUI + Note right of GMSCb: + GMSCb->>MSCa: REL + Note right of MSCa: + MSCa->>MSa: Disconnect + Note right of MSa: + +``` + +Sequence diagram showing information flow for UUS3 explicit request during call establishment (mobile to mobile call). Lifelines: MSa, MSCa, VLRa, GMSCb, HLRb, MSCb, MSb. The diagram shows the exchange of messages like Set-up, SIFOC, Complete call, IAM, SRI, SRI ack, ACM/ANM/CPG, CON, User info, UUI, and REL between these entities. + +Figure 5.2.3.2.1: Information flow for UUS3 explicit request during call establishment (mobile to mobile call) + +![Sequence diagram showing information flow for UUS3 explicit request during active call (mobile to mobile call) between MSa, MSCa, VLRa, GMSCb, HLRb, MSCb, and MSb.](8307f6b04df072c9332f9987e034272c_img.jpg) + +The sequence diagram illustrates the information flow for a UUS3 explicit request during an active call between two mobile stations, MSa and MSb. The participants involved are MSa, MSCa, VLRa, GMSCb, HLRb, MSCb, and MSb. The process begins with an 'Active call A-B' indicated by a dashed line at the top. MSa sends a 'Facility' message with 'S3=r' to MSCa. MSCa responds with 'Uus act' to VLRa, which returns 'Uus act ack' to MSCa. MSCa then sends a 'Facility' message with 'S3=r' to GMSCb. GMSCb forwards this to MSCb, which in turn sends it to MSb. MSb responds with a 'Facility' message with 'S3=p' back to MSCb. MSCb sends this back to GMSCb, which then sends it to MSCa. MSCa sends the 'Facility' message with 'S3=p' to MSa. Following this, MSa sends 'User info' with 'UUI' to MSCa, which is forwarded through VLRa, GMSCb, and MSCb to MSb. MSb returns 'User info' with 'UUI' to MSCb, which is then forwarded back through GMSCb, VLRa, and MSCa to MSa. Finally, MSa sends a 'Disconnect' message to MSCa, which is forwarded through GMSCb to MSCb, which then sends a 'Disconnect' message to MSb. MSCb also sends a 'REL' message to GMSCb, which is forwarded to MSCa, which then sends a 'REL' message to VLRa. + +``` +sequenceDiagram + participant MSa + participant MSCa + participant VLRa + participant GMSCb + participant HLRb + participant MSCb + participant MSb + + Note over VLRa: 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->>VLRa: User info UUI + VLRa->>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-->>VLRa: User info UUI + VLRa-->>MSCa: User info UUI + MSCa-->>MSa: User info UUI + MSa->>MSCa: Disconnect + MSCa->>GMSCb: REL + GMSCb->>MSCb: Disconnect + MSCb->>MSb: Disconnect +``` + +Note: +S3 UUS Service 3 +UUI User-to-user information +r requested +p provided + +Sequence diagram showing information flow for UUS3 explicit request during active call (mobile to mobile call) between MSa, MSCa, VLRa, GMSCb, HLRb, MSCb, and MSb. + +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.](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 --> SetUUS1NotReq[Set UUS1 "not required" to SIFOC]; UUS1_ReqAsReq -- Yes --> SetUUS1Req[Set UUS1 "required" to SIFOC]; SetUUS1NotReq --> Join1(( )); SetUUS1Req --> Join1; Join1 --> UUS2_Req; UUS2_Req -- No --> UUS3_Req{UUS3 requested}; UUS2_Req -- Yes --> UUS2_ReqAsReq{Requested as required}; UUS2_ReqAsReq -- No --> SetUUS2NotReq[Set UUS2 "not required" to SIFOC]; UUS2_ReqAsReq -- Yes --> SetUUS2Req[Set UUS2 "required" to SIFOC]; SetUUS2NotReq --> Join2(( )); SetUUS2Req --> Join2; Join2 --> UUS3_Req; UUS3_Req -- No --> End(( )); UUS3_Req -- Yes --> UUS3_ReqAsReq{Requested as required}; UUS3_ReqAsReq -- No --> SetUUS3NotReq[Set UUS3 "not required" to SIFOC]; UUS3_ReqAsReq -- Yes --> SetUUS3Req[Set UUS3 "required" to SIFOC]; SetUUS3NotReq --> Join3(( )); SetUUS3Req --> 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. + +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 loops back. 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 not an implicit request, it checks if requested as required. If yes, it sets S1:=r,r and copies S1 to IAM. If not required, 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 provisioned. If provisioned, it checks if requested as required. If yes, S2:=r,r; if no, S2:=r,nr. Then it copies S2 to IAM and reaches connector 1. If UUS2 is not requested or not provisioned, it bypasses these steps to connector 1. From connector 1, it checks if UUS3 is requested. If yes, it checks if provisioned. If provisioned, it checks if requested as required. If yes, S3:=r,r; if no, S3:=r,nr. Then it copies S3 to IAM and reaches the end connector. If UUS3 is not requested or not provisioned, it bypasses these steps to the end connector.](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 --> UUS1_Req + UUS1_Prov -- Yes --> Implicit{Implicit request} + Implicit -- Yes --> UUS1_Active[UUS1 implicit active:=True] + Implicit -- No --> ReqAsReq{Requested as required} + ReqAsReq -- Yes --> S1_rr[S1:=r,r] + ReqAsReq -- No --> S1_rnr[S1:=r,nr] + S1_rr --> CopyS1[Copy S1 to IAM] + S1_rnr --> CopyS1 + CopyS1 --> UUS1_Data{UUS1 data present} + UUS1_Data -- Yes --> CopyUUS1[Copy UUS data to IAM] + UUS1_Data -- No --> Junction(( )) + UUS1_Active --> CopyUUS1 + CopyUUS1 --> Junction + Junction --> UUS2_Req{UUS2 requested} + UUS2_Req -- No --> Junction2(( )) + UUS2_Req -- Yes --> UUS2_Prov{UUS2 provisioned} + UUS2_Prov -- No --> Junction2 + UUS2_Prov -- Yes --> ReqAsReq2{Requested as required} + ReqAsReq2 -- Yes --> S2_rr[S2:=r,r] + ReqAsReq2 -- No --> S2_rnr[S2:=r,nr] + S2_rr --> CopyS2[Copy S2 to IAM] + S2_rnr --> CopyS2 + CopyS2 --> Junction2 + Junction2 --> Connector1((1)) + Connector1 --> UUS3_Req{UUS3 requested} + UUS3_Req -- No --> End(( )) + UUS3_Req -- Yes --> UUS3_Prov{UUS3 provisioned} + UUS3_Prov -- No --> End + UUS3_Prov -- Yes --> ReqAsReq3{Requested as required} + ReqAsReq3 -- Yes --> S3_rr[S3:=r,r] + ReqAsReq3 -- No --> S3_rnr[S3:=r,nr] + S3_rr --> CopyS3[Copy S3 to IAM] + S3_rnr --> CopyS3 + CopyS3 --> End +``` + +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 loops back. 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 not an implicit request, it checks if requested as required. If yes, it sets S1:=r,r and copies S1 to IAM. If not required, 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 provisioned. If provisioned, it checks if requested as required. If yes, S2:=r,r; if no, S2:=r,nr. Then it copies S2 to IAM and reaches connector 1. If UUS2 is not requested or not provisioned, it bypasses these steps to connector 1. From connector 1, it checks if UUS3 is requested. If yes, it checks if provisioned. If provisioned, it checks if requested as required. If yes, S3:=r,r; if no, S3:=r,nr. Then it copies S3 to IAM and reaches the end connector. If UUS3 is not requested or not provisioned, it bypasses these steps to the end connector. + +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 ends with either Result := Pass or Result := Fail, both leading to 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}; UUS1_MSC --> UUS2; UUS2 -- Yes --> UUS2_MSC[UUS_MSC_Check_UUS2]; UUS2 -- No --> UUS3{UUS3 requested}; UUS2_MSC --> UUS3; UUS3 -- Yes --> UUS3_MSC[UUS_MSC_Check_UUS3]; UUS3 -- No --> UUS1_UUI[UUS_MSC_Check_UUS1_UUI]; UUS3_MSC --> UUS1_UUI; UUS1_UUI --> Pass[Result := Pass]; UUS1_UUI --> Fail[Result := Fail]; Pass --> End([X]); 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 ends with either Result := Pass or Result := Fail, both leading to 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. It checks three UUS services (UUS1, UUS2, UUS3) for being requested and provisioned. If any is requested as required and not provisioned, it fails. Otherwise, it passes.](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_Prov -- Yes --> SetUUS1[Set UUS1 "provisioned" to Complete Call]; SetUUS1 --> Join1(( )); UUS1_Reqd -- Yes --> Fail[Set negative response:= UUS Reject]; UUS1_Reqd -- No --> Join1; UUS2_Req -- No --> UUS3_Req{UUS3 requested}; UUS2_Req -- Yes --> UUS2_Prov{UUS2 provisioned}; UUS2_Prov -- No --> UUS2_Reqd{UUS2 required}; UUS2_Prov -- Yes --> SetUUS2[Set UUS2 "provisioned" to Complete Call]; SetUUS2 --> Join2(( )); UUS2_Reqd -- Yes --> Fail; UUS2_Reqd -- No --> Join2; UUS3_Req -- No --> Pass[Result := Pass]; UUS3_Req -- Yes --> UUS3_Prov{UUS3 provisioned}; UUS3_Prov -- No --> UUS3_Reqd{UUS3 required}; UUS3_Prov -- Yes --> SetUUS3[Set UUS3 "provisioned" to Complete Call]; SetUUS3 --> Join3(( )); UUS3_Reqd -- Yes --> Fail; UUS3_Reqd -- No --> Join3; Join1 --> Join3; Join2 --> Join3; Join3 --> Pass; Fail --> FailResult[Result := Fail]; Pass --> EndPass(( )); FailResult --> EndFail(( )); +``` + +This procedure is running in the VLR and it does the UUS specific provisioning checks + +Flowchart for Procedure UUS\_OCH\_Check\_Provision. It checks three UUS services (UUS1, UUS2, UUS3) for being requested and provisioned. If any is requested as required and not provisioned, it fails. Otherwise, it passes. + +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. It starts with an oval connector, followed by a decision diamond 'UUS data received in RCH message?'. If 'No', it goes to an exit circle. If 'Yes', it goes to another decision diamond 'UUS CF interaction set in RCH message?'. If 'No', it goes to an exit circle. If 'Yes', it goes to a process box 'UUS CF interaction := True', then to a process box 'Add received UUS information to IAM', and finally to an exit circle.](e29665b8abcea967ef289c6aff07ae4c_img.jpg) + +Procedure UUS\_GMSC\_Check\_Forwarding 1(1) + +``` +graph TD; Start([ ]) --> D1{UUS data received in RCH message?}; D1 -- No --> Exit1(( )); D1 -- Yes --> D2{UUS CF interaction set in RCH message?}; D2 -- No --> Exit2(( )); D2 -- Yes --> P1[UUS CF interaction := True]; P1 --> P2[Add received UUS information to IAM]; P2 --> Exit3(( )); Note[This procedure is running in the GMSC and it checks whether UUS specific data shall be forwarded in the optimal routing case]; +``` + +This procedure is running in the GMSC and it checks whether UUS specific data shall be forwarded in the optimal routing case + +Flowchart for Procedure UUS\_GMSC\_Check\_Forwarding. It starts with an oval connector, followed by a decision diamond 'UUS data received in RCH message?'. If 'No', it goes to an exit circle. If 'Yes', it goes to another decision diamond 'UUS CF interaction set in RCH message?'. If 'No', it goes to an exit circle. If 'Yes', it goes to a process box 'UUS CF interaction := True', then to a process box 'Add received UUS information to IAM', and finally to an exit circle. + +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](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +### Procedure UUS\_ICH\_Check\_Support + +1(1) + +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 + +``` + + graph TD + Start([ ]) --> UUS1_Req{UUS1 +requested} + + UUS1_Req -- No --> UUS_MSC_Check_UUS1[UUS_MSC_ +Check_UUS1] + UUS1_Req -- Yes --> UUS2_Req{UUS2 +requested} + + UUS_MSC_Check_UUS1 -- Pass --> UUS2_Req + UUS_MSC_Check_UUS1 -- Fail --> UUS2_Req_Fail{UUS2 +requested} + + UUS2_Req -- No --> UUS3_Req{UUS3 +requested} + UUS2_Req -- Yes --> UUS_MSC_Check_UUS2[UUS_MSC_ +Check_UUS2] + UUS_MSC_Check_UUS2 -- Pass --> UUS3_Req + + UUS2_Req_Fail -- No --> UUS3_Req_Fail{UUS3 +requested} + UUS2_Req_Fail -- Yes --> UUS_MSC_Check_UUS2_Fail[UUS_MSC_ +Check_UUS2] + UUS_MSC_Check_UUS2_Fail -- Fail --> UUS3_Req_Fail + + UUS3_Req -- No --> Set_UUS_Pass[Set UUS options +to first backward +message] + UUS3_Req -- Yes --> UUS_MSC_Check_UUS3[UUS_MSC_ +Check_UUS3] + UUS_MSC_Check_UUS3 -- Pass --> Set_UUS_Pass + + UUS3_Req_Fail -- No --> Set_UUS_Fail[Set UUS options +to first backward +message] + UUS3_Req_Fail -- Yes --> UUS_MSC_Check_UUS3_Fail[UUS_MSC_ +Check_UUS3] + UUS_MSC_Check_UUS3_Fail -- Fail --> Set_UUS_Fail + + Set_UUS_Pass --> UUS_MSC_Check_UUI_Pass[[UUS_MSC_ +Check_UUS1_ +UUI]] + UUS_MSC_Check_UUI_Pass --> Result_Pass[Result:= +Pass] + Result_Pass --> End_Pass(( )) + + Set_UUS_Fail --> UUS_MSC_Check_UUI_Fail[[UUS_MSC_ +Check_UUS1_ +UUI]] + UUS_MSC_Check_UUI_Fail --> Result_Fail[Result:= +Fail] + Result_Fail --> End_Fail(( )) + +``` + +From the originating GMSC (multiple instances) + +NOTE: UUS options is never set for implicit UUS1 service + +Flowchart for Procedure UUS\_ICH\_Check\_Support + +**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 no, it goes to Result:= Fail. If yes, it checks if requested as required. If no, it clears stored UUS2 service request. Both lead to Result:= Pass. If yes, it goes to Result:= Fail.](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_as_required1{requested as required}; Requested_as_required1 -- No --> Fail3[Result:= Fail]; Requested_as_required1 -- Yes --> UUS1_explicit_active{UUS1 explicit active?}; UUS1_explicit_active -- True --> UUS_CF_interaction[UUS CF interaction := True]; UUS1_explicit_active -- False --> Clear_UUS1[Clear stored UUS1 service request (and UUI)]; UUS_CF_interaction --> UUS2_present{UUS2 present}; Clear_UUS1 --> UUS2_present; UUS2_present -- No --> Fail4[Result:= Fail]; UUS2_present -- Yes --> Requested_as_required2{requested as required}; Requested_as_required2 -- No --> Clear_UUS2[Clear stored UUS2 service request]; Requested_as_required2 -- Yes --> Fail5[Result:= Fail]; Clear_UUS2 --> Pass1[Result:= Pass]; Pass1 --> End1(( )); Fail4 --> End2(( )); Fail5 --> End3(( )); Pass1 --> End4(( )); Fail1 --> End5(( )); +``` + +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 no, it goes to Result:= Fail. If yes, it checks if requested as required. If no, it clears stored UUS2 service request. Both lead to Result:= Pass. If yes, it goes to Result:= Fail. + +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 exit 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 exit 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' path bypasses the 'Yes' path's action block. The 'Yes' path leads to a process block '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' path bypasses the 'Yes' path's action block. The 'Yes' path leads to a process block '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' block and then to an end symbol (circle with X). If 'No', it bypasses the 'User To User' block and goes directly to the end symbol. There are three callout boxes: one empty, one stating 'This procedure is running in the MSC and it checks whether UUI can be passed over', and another explaining signal directions: 'Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination exchange unless otherwise marked.'](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +Procedure UUS\_MSC\_Check\_UUS2\_UUI\_to\_MS + +1(1) + +``` +graph TD; Start([ ]) --> Decision{UUS2 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\_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' block and then to an end symbol (circle with X). If 'No', it bypasses the 'User To User' block and goes directly to the end symbol. There are three callout boxes: one empty, one stating 'This procedure is running in the MSC and it checks whether UUI can be passed over', and another explaining signal directions: 'Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination exchange unless otherwise marked.' + +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 the same 'UTU2Cnt' decision. From 'UTU2Cnt', if '<2', it goes to a process 'UTU2Cnt:= UTU2Cnt + 1', then to an output 'User To User', and finally to an exit connector. There are also callouts explaining the procedure's purpose and signal directions.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +Procedure UUS\_MSC\_Check\_UUS2\_UUI\_to\_NW + +1(1) + +``` +graph TD; Start([ ]) --> UUS2Active{UUS2 active = True?}; UUS2Active -- No --> UTU2Cnt{UTU2Cnt}; UUS2Active -- Yes --> UTU2Cnt; UTU2Cnt -- "2" --> UTU2Cnt; UTU2Cnt -- "<2" --> UTU2CntInc[UTU2Cnt:= UTU2Cnt + 1]; UTU2CntInc --> UserToUser[/User To User/]; UserToUser --> End((X)); +``` + +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. + +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 the same 'UTU2Cnt' decision. From 'UTU2Cnt', if '<2', it goes to a process 'UTU2Cnt:= UTU2Cnt + 1', then to an output 'User To User', and finally to an exit connector. There are also callouts explaining the procedure's purpose and signal directions. + +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 callouts: one explaining the procedure's purpose, one about signal directions, and one about informing the MS of congestion control.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +Procedure UUS\_MSC\_Check\_UUS3\_UUI\_to\_NW + +1(1) + +``` +graph TD; Start([ ]) --> UUS3{UUS3 active = True?}; UUS3 -- No --> Exit(( )); UUS3 -- Yes --> Ngt0{N > 0?}; Ngt0 -- No --> CongestionSent{Congestion control sent?}; Ngt0 -- Yes --> Nminus[N := N - 1]; Nminus --> UserToUser[/User To User/]; UserToUser --> Exit; CongestionSent -- True --> Exit; CongestionSent -- False --> CongestionSentTrue[Congestion control sent := True]; CongestionSentTrue --> Exit; +``` + +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 callouts: one explaining the procedure's purpose, one about signal directions, and one about informing the MS of congestion control. + +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 an exit connector. If 'No', it goes to a process box 'Clear received (if any) UUI', then to an 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 --> Exit1(( )); D1 -- Yes --> P1[Clear received (if any) S1]; P1 --> D2{Received msg was Answer or Connect?}; D2 -- Yes --> Exit2(( )); D2 -- No --> P2[Clear received (if any) UUI]; P2 --> Exit3(( )); +``` + +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 an exit connector. If 'No', it goes to a process box 'Clear received (if any) UUI', then to an exit connector. + +Figure 9.3.6: Procedure UUS\_MSC\_Clear\_UUS + +![Flowchart for Macrodefinition UUS_MSC_Check_UUS1. It starts with a connector, leading to 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 'No', it goes to 'Connect received?'. If 'Yes', it goes to 'explicit request'. If 'No', it goes to 'Do not send S1' and then to a 'Pass' terminal. From 'explicit request', if 'Yes', it goes to 'UUS1 result sent := True' and then to 'S1 received'. If 'No', it goes to 'S1 received'. From 'S1 received', if 'Yes', it goes to 'UUS1 result sent := True' and then to 'Pass received S1'. If 'No', it goes to 'Do not send S1' and then to a 'Pass' terminal. From 'Pass received S1', it goes to 'S1=np?'. If 'Yes', it goes to 'UUS1 explicit active:=True' and then to 'UUS1 Required?'. If 'No', it goes to 'UUS1 Required?'. From 'UUS1 Required?', if 'Yes', it goes to a 'Fail' terminal. If 'No', it goes to a 'Pass' terminal. From 'S1=np?', if 'Yes', it goes to 'S1:=np' and then to 'Pass received S1'. From 'Pass received S1', it goes to 'S1=np?'. If 'Yes', it goes to 'UUS1 explicit active:=True' and then to 'UUS1 Required?'. If 'No', it goes to 'UUS1 Required?'. From 'UUS1 Required?', if 'Yes', it goes to a 'Fail' terminal. If 'No', it goes 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([ ]) --> D1{UUS1 result sent?}; D1 -- True --> S1[Do not send S1]; S1 --> P1((Pass)); D1 -- False --> D2{Alert received?}; D2 -- No --> D3{Connect received?}; D2 -- Yes --> D4{explicit request}; D3 -- Yes --> D4; D3 -- No --> S2[Do not send S1]; S2 --> P2((Pass)); D4 -- Yes --> S3[UUS1 result sent := True]; S3 --> D5{S1 received}; D4 -- No --> D5; D5 -- Yes --> S4[UUS1 result sent := True]; S4 --> S5[Pass received S1]; D5 -- No --> S2; S5 --> D6{S1=np?}; D6 -- Yes --> S6[UUS1 explicit active:=True]; S6 --> D7{UUS1 Required?}; D6 -- No --> D7; D7 -- Yes --> F1((Fail)); D7 -- No --> P3((Pass)); D6 -- Yes --> S7[S1:=np]; S7 --> S5; S5 --> D6; D6 -- Yes --> S6; S6 --> D7; D7 -- Yes --> F2((Fail)); D7 -- No --> P4((Pass)); +``` + +np = service is not provided by network or remote end + +Flowchart for Macrodefinition UUS\_MSC\_Check\_UUS1. It starts with a connector, leading to 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 'No', it goes to 'Connect received?'. If 'Yes', it goes to 'explicit request'. If 'No', it goes to 'Do not send S1' and then to a 'Pass' terminal. From 'explicit request', if 'Yes', it goes to 'UUS1 result sent := True' and then to 'S1 received'. If 'No', it goes to 'S1 received'. From 'S1 received', if 'Yes', it goes to 'UUS1 result sent := True' and then to 'Pass received S1'. If 'No', it goes to 'Do not send S1' and then to a 'Pass' terminal. From 'Pass received S1', it goes to 'S1=np?'. If 'Yes', it goes to 'UUS1 explicit active:=True' and then to 'UUS1 Required?'. If 'No', it goes to 'UUS1 Required?'. From 'UUS1 Required?', if 'Yes', it goes to a 'Fail' terminal. If 'No', it goes to a 'Pass' terminal. From 'S1=np?', if 'Yes', it goes to 'S1:=np' and then to 'Pass received S1'. From 'Pass received S1', it goes to 'S1=np?'. If 'Yes', it goes to 'UUS1 explicit active:=True' and then to 'UUS1 Required?'. If 'No', it goes to 'UUS1 Required?'. From 'UUS1 Required?', if 'Yes', it goes to a 'Fail' terminal. If 'No', it goes 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'. A note indicates 'np = service is not provided by network or remote end'.](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'. A note indicates 'np = service is not provided by network or remote end'. + +Figure 9.3.8: Macrodefinition UUS\_MSC\_Check\_UUS2 + +![Flowchart for UUS_MSC_Check_UUS3 macrodefinition. The logic flow determines if UUS3 is active or if the process fails based on 'Connect received' and 'S3 received' signals.](8269648391c59363ea61243864a2adf7_img.jpg) + +Macrodefinition UUS\_MSC\_Check\_UUS3 + +1(1) + +np = service is not provided by network or remote end + +``` + +graph TD + Start([ ]) --> D1{Connect +received?} + D1 -- No --> D2{S3 +received?} + D1 -- Yes --> D3{S3 +received?} + D2 -- Yes --> Fail1((Fail)) + D2 -- No --> Pass1((Pass)) + D3 -- No --> P1[S3:=np] + D3 -- Yes --> P2[Pass received +S3] + P1 --> D4{S3 = np} + P2 --> D4 + D4 -- Yes --> D5{UUS3 +Required?} + D4 -- No --> P3[UUS3 active +:=True] + P3 --> D5 + D5 -- No --> Pass1 + D5 -- Yes --> Fail2((Fail)) + +``` + +Flowchart for UUS\_MSC\_Check\_UUS3 macrodefinition. The logic flow determines if UUS3 is active or if the process fails based on 'Connect received' and 'S3 received' signals. + +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 process starts at an initial state, sets Congestion control to False, and enters IDLE. From IDLE, it can receive a Facility or Connect signal. The Facility signal leads to UUS_MSC_Check_UUS3_Activation, which results in Aborted, Pass, or Fail. Pass leads to Start T4-UUS3 and then Wait_For_Activation_Response. Fail leads to S3:=np and then IDLE. The Connect signal (from GSM 03.18 processes) leads to another Connect state, then a decision UUS3 active=True?. If No, it goes to IDLE. If Yes, it sets flow control parameters (X:=16, N:=X, Y:=8) and enters Active_Call. Annotations explain the process's role, signal directions, and parameter meanings.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +### Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call + +1(4) + +``` +stateDiagram-v2 + [*] --> Congestion_control_set + Congestion_control_set : Congestion control sent := False + Congestion_control_set --> IDLE + IDLE --> Facility + IDLE --> Connect + Facility --> UUS_MSC_Check_UUS3_Activation + UUS_MSC_Check_UUS3_Activation --> Result? + Result? -- Aborted --> [*] + Result? -- Pass --> Start_T4_UUS3 + Start_T4_UUS3 --> Facility + Facility --> Wait_For_Activation_Response + Result? -- Fail --> S3_np + S3_np : S3:=np + S3_np --> Facility + Facility --> IDLE + Connect --> Connect + Connect --> UUS3_active_True? + UUS3_active_True? -- No --> IDLE + UUS3_active_True? -- Yes --> Flow_control_params + Flow_control_params : X:=16, N:=X, Y:=8 + Flow_control_params --> 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 + +From GSM 03.18 processes + +UUS3 flow control parameters + +State transition diagram for Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call. The process starts at an initial state, sets Congestion control to False, and enters IDLE. From IDLE, it can receive a Facility or Connect signal. The Facility signal leads to UUS\_MSC\_Check\_UUS3\_Activation, which results in Aborted, Pass, or Fail. Pass leads to Start T4-UUS3 and then Wait\_For\_Activation\_Response. Fail leads to S3:=np and then IDLE. The Connect signal (from GSM 03.18 processes) leads to another Connect state, then a decision UUS3 active=True?. If No, it goes to IDLE. If Yes, it sets flow control parameters (X:=16, N:=X, Y:=8) and enters Active\_Call. Annotations explain the process's role, signal directions, and parameter meanings. + +Figure 9.4.1.1: Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call (sheet 1) + +![SDL Diagram for Process Serving_MSC_Handle_UUS_In_Active_Call (sheet 2)](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +### Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call + +2(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. + +p = provided i.e. UUS3 service is provided + np = not provided i.e. UUS3 service is not provided + +``` + +stateDiagram-v2 + state "Wait_For_Activation_Response" as State1 + state "Facility" as Input1 + state "Stop T4-UUS3" as Task1 + state "S3=p?" as Decision + state "UUS3 active :=True" as Task2 + state "X:=16\nN:=X\nY:=8" as Task3 + state "Facility" as Output1 + state "Start T2-UUS3" as Task4 + state "Wait_For_UUI" as State2 + state "T4-UUS3 expiry" as Input2 + state "Facility" as Output2 + state "IDLE" as State3 + + [*] --> State1 + State1 --> Input1 + Input1 --> Task1 + Task1 --> Decision + Decision --> Task2 : Yes + Decision --> Input2 : No + Task2 --> Task3 + Task3 --> Output1 + Output1 --> Task4 + Task4 --> State2 + Input2 --> Output2 + Output2 --> State3 + +``` + +UUS3 flow control parameters + +SDL Diagram for Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call (sheet 2) + +**Figure 9.4.1.1: Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call (sheet 2)** + +![Sequence diagram for Process Serving_MSC_Handle_UUS_In_Active_Call. The diagram shows four parallel lifelines starting from a '*' lifeline. Lifeline 1: Release transaction (outward) -> Release transaction (inward, labeled 'To GSM 03.18 processes') -> End. Lifeline 2: Release transaction (outward, labeled 'From GSM 03.18 processes') -> Release transaction (inward) -> End. Lifeline 3: NOTIFY (ECT) (outward) -> NOTIFY (ECT) (inward) -> Action block (UUS1 implicit active := False, UUS1 explicit active := False, UUS2 active := False, UUS3 active := False, Stop T2-UUS3) -> IDLE. Lifeline 4: NOTIFY (ECT) (outward) -> NOTIFY (ECT) (inward). Callouts explain the process and signal directions.](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 + +UUS1 implicit active := False +UUS1 explicit active := False +UUS2 active := False +UUS3 active := False +Stop T2-UUS3 + +Sequence diagram for Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call. The diagram shows four parallel lifelines starting from a '\*' lifeline. Lifeline 1: Release transaction (outward) -> Release transaction (inward, labeled 'To GSM 03.18 processes') -> End. Lifeline 2: Release transaction (outward, labeled 'From GSM 03.18 processes') -> Release transaction (inward) -> End. Lifeline 3: NOTIFY (ECT) (outward) -> NOTIFY (ECT) (inward) -> Action block (UUS1 implicit active := False, UUS1 explicit active := False, UUS2 active := False, UUS3 active := False, Stop T2-UUS3) -> IDLE. Lifeline 4: NOTIFY (ECT) (outward) -> NOTIFY (ECT) (inward). Callouts explain the process and signal directions. + +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' after 'Start T2-UUS3'. Includes callouts about the process and signal directions.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call 4(4) + +``` +graph TD; Start([Active_Call]) --> U2U1[/User To User/]; Start --> U2U2[/User To User/]; Start --> T2UUS3[/T2-UUS3 expiry/]; U2U1 --> UUS_MCH[UUS_MCH Check_UUS3 UUI To MS]; UUS_MCH --> U2U2; U2U2 --> UUS_MSC[UUS_MSC Check_UUS3 UUI To NW]; U2U2 --> Start; T2UUS3 --> N0{N = 0?}; N0 -- No --> NNY1[N:=N+Y]; N0 -- Yes --> NNY2[N:=N+Y]; NNY2 --> CC{Congestion control sent?}; CC -- True --> CC_Cond{Congestion Control}; CC -- False --> Start; CC_Cond --> InformMS[Inform MS that it is allowed to send UUIs]; InformMS --> CC_Sent[Congestion control sent := False]; CC_Sent --> Start; NNY1 --> NX{N > X?}; NX -- Yes --> NX_Val[N := X]; NX -- No --> Start; NX_Val --> Start; Start --> End([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. + +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' after 'Start T2-UUS3'. Includes callouts about the process and signal directions. + +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', then 'Release transaction' (From GSM 03.18 to To BSS), then 'Release transaction' (From BSS to To GSM 03.18), then 'Send_Info_For_UUS3_Ack', and finally 'Result:= Aborted'. Callouts indicate the procedure runs in the MSC and signals are to/from the VLR.](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]; ResultPass --> EndPass(( )); Decision -- No --> ResultFail[Result:= Fail]; ResultFail --> EndFail(( )); Decision -- Neither --> SendAck1[Send_Info_For_UUS3_Ack]; SendAck1 --> WaitAck((Wait_For_Ack)); WaitAck --> Release1[Release transaction]; Release1 -- "From GSM 03.18 to To BSS" --> Release2[Release transaction]; Release2 -- "From BSS to To GSM 03.18" --> SendAck2[Send_Info_For_UUS3_Ack]; SendAck2 --> ResultAbort[Result:= Aborted]; ResultAbort --> EndAbort(( )); +``` + +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', then 'Release transaction' (From GSM 03.18 to To BSS), then 'Release transaction' (From BSS to To GSM 03.18), then 'Send\_Info\_For\_UUS3\_Ack', and finally 'Result:= Aborted'. Callouts indicate the procedure runs in the MSC and signals are to/from the VLR. + +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 process starts at an IDLE state, sends info for UUS3, checks if UUS3 is provisioned, sets the provisioned status if yes, sends an ack, and returns to IDLE. If not provisioned, it skips to the ack step. Includes two callout boxes explaining the process's location and signaling conventions.](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 --> Provisioned{UUS3 provisioned?}; Provisioned -- Yes --> SetUUS[Set UUS provisioned]; Provisioned -- 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 process starts at an IDLE state, sends info for UUS3, checks if UUS3 is provisioned, sets the provisioned status if yes, sends an ack, and returns to IDLE. If not provisioned, it skips to the ack step. Includes two callout boxes explaining the process's location and signaling conventions. + +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 an Active_Call state. If No, it returns to IDLE. The Facility path leads to another Facility connector, then starts T1_UUS3 and enters a Wait_For_Activation_Response state. A note indicates the Connect path leads to GSM 03.18 processes. Other notes explain the process runs in the remote MSC 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 an Active\_Call state. If No, it returns to IDLE. The Facility path leads to another Facility connector, then starts T1\_UUS3 and enters a Wait\_For\_Activation\_Response state. A note indicates the Connect path leads to GSM 03.18 processes. Other notes explain the process runs in the remote MSC 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 goes to UUS3 active:= True, then X:= 16, N:= X, Y:= 8, then Facility, then Start T2-UUS3, and finally Wait_For_UUI. If No, it goes to T1-UUS3 expiry, then S3 := np, then 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 + state "Wait_For_Activation_Response" as Wait_For_Activation_Response + state "Facility" as Facility + state "Stop T1-UUS3" as Stop_T1_UUS3 + state "S3 := np" as S3_np + state "S3=p?" as S3_p + state "UUS3 active:= True" as UUS3_active + state "X := 16, N := X, Y := 8" as X_N_Y + state "Start T2-UUS3" as Start_T2_UUS3 + state "Wait_For_UUI" as Wait_For_UUI + state "IDLE" as IDLE + state "T1-UUS3 expiry" as T1_UUS3_expiry + + Wait_For_Activation_Response --> Facility + Facility --> Stop_T1_UUS3 + Stop_T1_UUS3 --> S3_p + S3_p -- Yes --> UUS3_active + UUS3_active --> X_N_Y + X_N_Y --> Facility + Facility --> Start_T2_UUS3 + Start_T2_UUS3 --> Wait_For_UUI + S3_p -- No --> T1_UUS3_expiry + T1_UUS3_expiry --> 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 goes to UUS3 active:= True, then X:= 16, N:= X, Y:= 8, then Facility, then Start T2-UUS3, and finally Wait\_For\_UUI. If No, it goes to T1-UUS3 expiry, then S3 := np, then 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 'No', it goes to 'N := N + Y'. If 'Yes', it goes to 'N := N + Y'. Both lead to a decision 'N > X?'. If 'Yes', it goes to 'N := X'. If 'No', it leads to 'Start T2-UUS3'. The 'N := N + Y' path also leads to a decision 'Congestion control sent'. If 'True', it goes to 'Congestion Control' (with a note 'Inform MS that it is allowed to send UUIs'), then 'Congestion control sent := False', then 'Start T2-UUS3'. If 'False', it leads directly to 'Start T2-UUS3'. All paths converge to 'Start T2-UUS3', 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; AC1([Active_Call]) --> U1[User To User]; AC1 --> U2[User To User]; AC1 --> T2[T2-UUS3 expiry]; U1 --> U1M[UUS_MSC Check_UUS3_UUI to MS]; U2 --> U2N[UUS_MSC Check_UUS3_UUI to NW]; T2 --> N0{N = 0?}; N0 -- No --> NY1[N := N + Y]; N0 -- Yes --> NY2[N := N + Y]; NY1 --> NX{N > X?}; NY2 --> NX; NX -- Yes --> NX_val[N := X]; NX -- No --> STU[Start T2-UUS3]; NX_val --> STU; NY1 --> CCS{Congestion control sent}; CCS -- True --> CC{Congestion Control}; CCS -- False --> STU; CC -.-> InformMS[Inform MS that it is allowed to send UUIs]; CC --> CCSF[Congestion control sent := False]; CCSF --> STU; STU --> AC2([Active_Call]); +``` + +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 'No', it goes to 'N := N + Y'. If 'Yes', it goes to 'N := N + Y'. Both lead to a decision 'N > X?'. If 'Yes', it goes to 'N := X'. If 'No', it leads to 'Start T2-UUS3'. The 'N := N + Y' path also leads to a decision 'Congestion control sent'. If 'True', it goes to 'Congestion Control' (with a note 'Inform MS that it is allowed to send UUIs'), then 'Congestion control sent := False', then 'Start T2-UUS3'. If 'False', it leads directly to 'Start T2-UUS3'. All paths converge to 'Start T2-UUS3', 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. It starts with a start state pointing to 'Wait_For_Activation_Response_Active_Call'. From there, it branches into four parallel paths: 1) 'Release transaction' (outward) -> 'Release transaction' (inward) with a note 'From GSM 03.18 processes' and 'To GSM 03.18 processes'. 2) 'Release transaction' (outward) -> 'Release transaction' (inward). 3) 'NOTIFY (ECT)' (outward) -> 'NOTIFY (ECT)' (inward). 4) 'NOTIFY (ECT)' (outward) -> 'NOTIFY (ECT)' (inward). All four inward paths converge to a common state box containing: 'UUS1 implicit active := False', 'UUS1 explicit active := False', 'UUS2 active := False', 'UUS3 active := False', and 'Stop T2-UUS3'. From this state box, the process transitions to an 'IDLE' state.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +### Process Remote\_MSC\_Handle\_UUS\_In\_Active\_Call + +4(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. + +``` +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 "NOTIFY (ECT)" as NOTIFY_1 + state "NOTIFY (ECT)" as NOTIFY_2 + state "Release transaction" as Release_Transaction_2 + state "Release transaction" as Release_Transaction_3 + state "NOTIFY (ECT)" as NOTIFY_3 + state "NOTIFY (ECT)" as NOTIFY_4 + state "UUS1 implicit active := False
UUS1 explicit active := False
UUS2 active := False
UUS3 active := False
Stop T2-UUS3" as Common_State + state IDLE as IDLE + + Wait_For_Activation_Response_Active_Call --> Release_Transaction_1 + Wait_For_Activation_Response_Active_Call --> NOTIFY_1 + Wait_For_Activation_Response_Active_Call --> NOTIFY_2 + Wait_For_Activation_Response_Active_Call --> Release_Transaction_2 + + Release_Transaction_1 --> Release_Transaction_3 + NOTIFY_1 --> NOTIFY_3 + NOTIFY_2 --> NOTIFY_4 + Release_Transaction_2 --> Release_Transaction_3 + + Release_Transaction_3 --> Common_State + NOTIFY_3 --> Common_State + NOTIFY_4 --> Common_State + + Common_State --> IDLE +``` + +State transition diagram for Process Remote\_MSC\_Handle\_UUS\_In\_Active\_Call. It starts with a start state pointing to 'Wait\_For\_Activation\_Response\_Active\_Call'. From there, it branches into four parallel paths: 1) 'Release transaction' (outward) -> 'Release transaction' (inward) with a note 'From GSM 03.18 processes' and 'To GSM 03.18 processes'. 2) 'Release transaction' (outward) -> 'Release transaction' (inward). 3) 'NOTIFY (ECT)' (outward) -> 'NOTIFY (ECT)' (inward). 4) 'NOTIFY (ECT)' (outward) -> 'NOTIFY (ECT)' (inward). All four inward paths converge to a common state box containing: 'UUS1 implicit active := False', 'UUS1 explicit active := False', 'UUS2 active := False', 'UUS3 active := False', and 'Stop T2-UUS3'. From this state box, the process transitions to an 'IDLE' state. + +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 + state "((Not Provisioned, Not Registered, Not Active, Not Induced))" as S1 + state "((Provisioned, Not Registered, Active and Operative, Not Induced))" as S2 + S1 --> S2 : Provision + S2 --> S1 : Withdrawal + +``` + +The diagram illustrates the state transition model for the service. It consists of two states represented by ovals. 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 + +| Change history | | | | | | | | | +|----------------|-----------|---------|-----|-----|--------|-----|---------|----------------------------------| +| TSG CN# | Spec | Old Ver | CR | Rev | Phase | Cat | New Ver | Subject/Comment | +| Apr 1999 | GSM 03.87 | 7.0.0 | | | R98 | | | Transferred to 3GPP CN1 | +| CN#03 | 23.087 | | | | R99 | | 3.0.0 | Approved at CN#03 | +| | 23.087 | 3.0.0 | | | R99 | | 3.0.1 | References updated from 2G to 3G | +| CN#09 | 23.087 | 3.0.1 | 001 | 1 | R99 | F | 3.1.0 | SDL refresh | +| CN#11 | 23.087 | 3.1.0 | | | Rel-4 | | 4.0.0 | Release 4 after CN#11 | +| CN#16 | 23.087 | 4.0.0 | | | Rel-5 | | 5.0.0 | Release 5 after CN#16 | +| CN#26 | 23.087 | 5.0.0 | | | Rel-6 | | 6.0.0 | Release 6 after CN#26 | +| CT#36 | 23.087 | 6.0.0 | | | Rel-7 | | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 23.087 | 7.0.0 | | | Rel-8 | | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | 23.087 | 8.0.0 | - | - | Rel-9 | | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | 23.087 | 9.0.0 | - | - | Rel-10 | | 10.0.0 | Update to Rel-10 version (MCC) | +| 2012-09 | 23.087 | 10.0.0 | - | - | Rel-11 | | 11.0.0 | Update to Rel-11 version (MCC) | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23088/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-11/23_series/23088/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f70ad14efe1d502dc7e67102ebe6473f4d564c39 --- /dev/null +++ b/marked/Rel-11/23_series/23088/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7214668031b1765a98971c7fdfdedac4f4d3977bc80037771095a206ee7ec751 +size 76962 diff --git a/marked/Rel-11/23_series/23088/02d0c8a07c481d880b73a25d02050fad_img.jpg b/marked/Rel-11/23_series/23088/02d0c8a07c481d880b73a25d02050fad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..779f02b94a6d697e1354b59829ca73f84059360d --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23088/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-11/23_series/23088/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fc72657239e917105322c29622b53e245cfd086 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23088/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/Rel-11/23_series/23088/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2843ac671920171110fe29753591e2faccf1a682 --- /dev/null +++ b/marked/Rel-11/23_series/23088/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a741eb9868cd905ea33b1306ada428839934cc80bac19c39bee64e43294c3b63 +size 48350 diff --git a/marked/Rel-11/23_series/23088/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-11/23_series/23088/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fff62742dfa71cdcaeeb4e1142d2eafef6b5601b --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23088/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-11/23_series/23088/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d08aab537cd7ad38643cc1dff130d1787fd444b --- /dev/null +++ b/marked/Rel-11/23_series/23088/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42c9b6ae8e164a949b883f138620f16e50f86fb9e0e9a3d5553bacac6de198a1 +size 85828 diff --git a/marked/Rel-11/23_series/23088/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-11/23_series/23088/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6aabcad05c6abfffd04fe069cddc053247b87b7a --- /dev/null +++ b/marked/Rel-11/23_series/23088/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06ec255a6de2e9588d95c2c529c575c9d987339b9359578f2d05f13fdc552860 +size 54412 diff --git a/marked/Rel-11/23_series/23088/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-11/23_series/23088/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cf86706037951cef25b82a1f39cdd4524bf3d84 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23088/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-11/23_series/23088/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62c9edf7393bcdddefb1a86da401f92e691467ae --- /dev/null +++ b/marked/Rel-11/23_series/23088/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d010de50b70185fd695a188b7e37527a38a6fdddf56fab4fbba2019558986c5 +size 78013 diff --git a/marked/Rel-11/23_series/23088/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-11/23_series/23088/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e075516899cfee6b4d2cef24b67a96cafe87be1f --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23088/6361dfaef83c9ffc3b147e1627ba76a1_img.jpg b/marked/Rel-11/23_series/23088/6361dfaef83c9ffc3b147e1627ba76a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..798d1a0a9474ee707e200e900175a9957c1c333e --- /dev/null +++ b/marked/Rel-11/23_series/23088/6361dfaef83c9ffc3b147e1627ba76a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0819af5df77bbdef657f21dfb2cab4ace89bd51c2386ab6667fd5dfb79b2e5c0 +size 51417 diff --git a/marked/Rel-11/23_series/23088/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-11/23_series/23088/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa142036cf2431ac239335bdc8efe4fa644e2e5c --- /dev/null +++ b/marked/Rel-11/23_series/23088/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3431c2502400ad0ac62440c9a1046be9fc20b2e178ba483112f8ae38a0edd345 +size 72567 diff --git a/marked/Rel-11/23_series/23088/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/marked/Rel-11/23_series/23088/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b78efa3d5524592f176a42ecf4e526dd0ce1e0aa --- /dev/null +++ b/marked/Rel-11/23_series/23088/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6df3d74c860e273536074dd233d3621781ccdb428457bfc8472e41d4262d7e7 +size 31800 diff --git a/marked/Rel-11/23_series/23088/73dff6b45b2b9ffd384bab3235f869af_img.jpg b/marked/Rel-11/23_series/23088/73dff6b45b2b9ffd384bab3235f869af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb8625096a962190df10b3bab4693878fa753aaf --- /dev/null +++ b/marked/Rel-11/23_series/23088/73dff6b45b2b9ffd384bab3235f869af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfdaedf65d48d217cc46febb1f6456de07cad9fbf4bd4aeacce507f9658f331a +size 145706 diff --git a/marked/Rel-11/23_series/23088/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-11/23_series/23088/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..019100288be803547c6a4a840e91aa2eac44864b --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23088/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/23_series/23088/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb118f48587d8d501c399d1b2b0629feb765486a --- /dev/null +++ b/marked/Rel-11/23_series/23088/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e617a238cc5b9f811d4e37819ef1386cab39b2d7645103be85f9a37ead5c2c41 +size 85651 diff --git a/marked/Rel-11/23_series/23088/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-11/23_series/23088/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..391af53f56851a7961cf76005cd4d7b7b84498e3 --- /dev/null +++ b/marked/Rel-11/23_series/23088/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85b6bfdc7c0b05784a6237026dda07c850f75e588d99be9b2f402caadaf36ab3 +size 41117 diff --git a/marked/Rel-11/23_series/23088/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-11/23_series/23088/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50944166ea1c87f87e47f5e6c3a1a6221b2ff7a7 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23088/a734898ce18e972938949637c32a34f4_img.jpg b/marked/Rel-11/23_series/23088/a734898ce18e972938949637c32a34f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..860063b2578b0c6a8fea8f797c855f3ecf50206f --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23088/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-11/23_series/23088/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a20c6fdff8ff49e4af22eb197494be8f1eb3fad --- /dev/null +++ b/marked/Rel-11/23_series/23088/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d1120ed98f6022f251357c5cc84f1a087e62d578585c56e8ccbec706208495e +size 53043 diff --git a/marked/Rel-11/23_series/23088/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-11/23_series/23088/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51bb402177f518711328b9ff06bdf8f71de57dc7 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23088/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-11/23_series/23088/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb3b86ef7a3fc91a873247a4cb8e40c7de2b25d8 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23088/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-11/23_series/23088/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d4b9d7d15e1822d48e2a65a66a89ac89607e43f --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23088/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-11/23_series/23088/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28ed60d115fa2f66fa6387f37b995d2a35cf5de9 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23088/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/marked/Rel-11/23_series/23088/e9d825d87c5f85c8dba0664eace96ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a66b141751b2b5d4a9f6c03c724ca3da026020f --- /dev/null +++ b/marked/Rel-11/23_series/23088/e9d825d87c5f85c8dba0664eace96ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e54c379bd407800dd3faf4c5f6152b81b111dad9527e8fef112d72e080d5d087 +size 26595 diff --git a/marked/Rel-11/23_series/23088/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-11/23_series/23088/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54161323058afb138845fa1359532156dcb04d51 --- /dev/null +++ b/marked/Rel-11/23_series/23088/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01152164fb532fc4c6200975d05cb6d8c8c790f58e9dc2b998e83af920ceed15 +size 51394 diff --git a/marked/Rel-11/23_series/23088/raw.md b/marked/Rel-11/23_series/23088/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ce519f3208ee0351ac5d33260de94b12c9a27c05 --- /dev/null +++ b/marked/Rel-11/23_series/23088/raw.md @@ -0,0 +1,1314 @@ + + + + + + +# 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. + +![Flowchart for Process BO1 showing the possible change of barring of outgoing international calls. The process starts at an 'idle' state, proceeds to 'activate BOIC-exHC', then checks if 'BOIC-exHC supported'. If 'no', it goes to 'change into BOIC' and then to 'acknowledge'. If 'yes', it goes directly to 'acknowledge'. Finally, it returns to an 'idle' state. A note defines BOIC-exHC and BOIC.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +Process BO1 + +388\_11(1) + +``` +graph TD; idle1([idle]) --> activate[activate BOIC-exHC]; activate --> supported{BOIC-exHC supported}; supported -- no --> change[change into BOIC]; supported -- yes --> acknowledge{acknowledge}; change --> 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. + +Flowchart for Process BO1 showing the possible change of barring of outgoing international calls. The process starts at an 'idle' state, proceeds to 'activate BOIC-exHC', then checks if 'BOIC-exHC supported'. If 'no', it goes to 'change into BOIC' and then to 'acknowledge'. If 'yes', it goes directly to 'acknowledge'. Finally, it returns to an 'idle' state. A note defines BOIC-exHC and BOIC. + +**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 interaction between call barring programs. The flow starts at 'idle', goes to 'register outgoing barring program', then to a decision 'other program active'. If 'yes', it goes to 'deactivate other outgoing barring program' and then loops back to the decision. If 'no', it goes to 'activate outgoing barring program', then to 'acknowledge', and finally back to 'idle'.](e6df2733626a85205c1db682e6259c46_img.jpg) + +Process BO2 + +388\_12(1) + +``` +graph TD; idle1([idle]) --> register[register outgoing barring program]; register --> decision{other program active}; decision -- yes --> deactivate[deactivate other outgoing barring program]; deactivate --> decision; decision -- no --> activate[activate outgoing barring program]; activate --> acknowledge{acknowledge}; acknowledge --> idle2([idle]); +``` + +Flowchart for Process BO2 showing interaction between call barring programs. The flow starts at 'idle', goes to 'register outgoing barring program', then to a decision 'other program active'. If 'yes', it goes to 'deactivate other outgoing barring program' and then loops back to the decision. If 'no', it goes to 'activate outgoing barring program', then to 'acknowledge', and finally back to 'idle'. + +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 --> setResult5; setResult1 --> acknowledge{acknowledge}; setResult2 --> acknowledge; setResult3 --> acknowledge; setResult4 --> acknowledge; setResult5 --> 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](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 sequence of messages for activating 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 sequence 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 to the VLR, which is then passed to the MSC and finally to the MS. The MS sends a 'Password' message back to the MSC, which is forwarded to the VLR and then to the HLR. The HLR sends an 'Acknowledge' message to the VLR, which is passed to the MSC and then to the MS. The MSC sends a 'Release complete' message to the MS, with a note indicating '\Facility'. On the HLR side, there are notes 'PW1' after the 'Activate BX' message and 'PW2', 'BO2', 'BO3' after the 'Password' message. + +Sequence diagram for activation of barring of outgoing calls + +**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) + +``` +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: Get password + VLR-->>MSC: Get password + MSC-->>MS: 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 outgoing 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 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 a 'Get password' message to the VLR, which is then passed to the MSC and finally to the MS. The MS sends a 'Password' message back to the MSC, which is forwarded to the VLR and then to the HLR. The HLR sends an 'Acknowledge' message back to the VLR, which is passed to the MSC and then to the MS. Finally, the MSC sends a 'Release complete' message to the MS, with a '\Facility' parameter. + +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) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + MS->>MSC: Interrogate BX + MSC->>VLR: Interrogate BX + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note left of MS: \Facility +``` + +The diagram illustrates the sequence of messages for interrogating barring of outgoing 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 an 'Interrogate BX' message to the MSC. The MSC then forwards this to the VLR. The VLR responds with an 'Acknowledge' message back to the MSC, which is then passed to the MS. Finally, the MSC sends a 'Release complete' message to the MS, with a '\Facility' parameter. + +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 skips to 'continue call handling'. If 'yes', it sets 'barring indicator = 'yes'', then goes to 'continue call handling'. If 'activated for basic service' is 'no', it sets 'barring indicator = 'no'', then goes to 'continue call handling'. The process ends at 'idle'. A note indicates BAOC: Barring of All Outgoing Calls.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +Process MAF017 + +388\_17(1) + +``` +graph TD; idle1([idle]) --> init[initiate handling of BAOC]; init --> emergency{emergency call}; emergency -- yes --> continue{continue call handling}; emergency -- no --> activated{activated for basic service}; activated -- no --> continue; activated -- yes --> setYes[set barring indicator = 'yes']; setYes --> continue; activated -- no --> setNo[set barring indicator = 'no']; setNo --> continue; continue --> idle2([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 skips to 'continue call handling'. If 'yes', it sets 'barring indicator = 'yes'', then goes to 'continue call handling'. If 'activated for basic service' is 'no', it sets 'barring indicator = 'no'', then goes to 'continue call handling'. The process ends at 'idle'. A note indicates BAOC: Barring of All Outgoing Calls. + +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. The process starts at 'idle', goes to 'initiate handling of BOIC', then checks if it's an 'emergency call'. If 'yes', it goes to 'set barring indicator = 'no''. If 'no', it checks if it's an 'international call'. If 'no', it goes to 'set barring indicator = 'no''. If 'yes', it checks if it's 'activated for basic service'. If 'no', it goes to 'set barring indicator = 'no''. If 'yes', it goes to 'set barring indicator = 'yes''. Both 'yes' and 'no' paths for 'set barring indicator' lead to 'continue call handling', which then returns to 'idle'.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +Process MAF018 388\_18(1) + +``` +graph TD; idle1([idle]) --> init[initiate handling of BOIC]; init --> ec{emergency call}; ec -- yes --> setno[set barring indicator = 'no']; ec -- no --> ic{international call}; ic -- no --> setno; ic -- yes --> abs{activated for basic service}; abs -- no --> setno; abs -- yes --> setyes[set barring indicator = 'yes']; setyes --> continue{continue call handling}; setno --> continue; continue --> idle2([idle]); +``` + +BOIC: Barring of Outgoing International Calls. + +Flowchart for Process MAF018: Barring of all outgoing international calls related authorisations examination. The process starts at 'idle', goes to 'initiate handling of BOIC', then checks if it's an 'emergency call'. If 'yes', it goes to 'set barring indicator = 'no''. If 'no', it checks if it's an 'international call'. If 'no', it goes to 'set barring indicator = 'no''. If 'yes', it checks if it's 'activated for basic service'. If 'no', it goes to 'set barring indicator = 'no''. If 'yes', it goes to 'set barring indicator = 'yes''. Both 'yes' and 'no' paths for 'set barring indicator' lead to 'continue call handling', which then returns to 'idle'. + +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 BOIC-exHC handling. It starts at 'Idle', goes to 'initiate handling of BOIC-exHC', then checks 'emergency call'. If 'yes', it goes to 'set barring indicator = 'no''. If 'no', it checks 'SMS'. If 'yes', it goes to 'continue call handling'. If 'no', it checks 'international call'. If 'yes', it goes to 'continue call handling'. If 'no', it checks 'destination in HPLMN country'. If 'yes', it goes to 'set barring indicator = 'no''. If 'no', it checks 'activated for basic service'. If 'yes', it goes to 'set barring indicator = 'yes''. If 'no', it goes to 'set barring indicator = 'no''. All 'set barring indicator' blocks lead to 'continue call handling', which then leads to 'Idle'.](8307f6b04df072c9332f9987e034272c_img.jpg) + +Process MAF020 388\_19(1) + +``` +graph TD; Idle1([Idle]) --> Init[initiate handling of BOIC-exHC]; Init --> EC{emergency call}; EC -- yes --> SetNo[set barring indicator = 'no']; EC -- no --> SMS{SMS}; SMS -- yes --> Cont[continue call handling]; SMS -- no --> IC{international call}; IC -- yes --> Cont; IC -- no --> 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 --> Cont; SetNo --> Cont; Cont --> Idle2([Idle]); +``` + +BOIC-exHC: Barring of Outgoing International Calls except those to the home PLMN country. + +Flowchart for BOIC-exHC handling. It starts at 'Idle', goes to 'initiate handling of BOIC-exHC', then checks 'emergency call'. If 'yes', it goes to 'set barring indicator = 'no''. If 'no', it checks 'SMS'. If 'yes', it goes to 'continue call handling'. If 'no', it checks 'international call'. If 'yes', it goes to 'continue call handling'. If 'no', it checks 'destination in HPLMN country'. If 'yes', it goes to 'set barring indicator = 'no''. If 'no', it checks 'activated for basic service'. If 'yes', it goes to 'set barring indicator = 'yes''. If 'no', it goes to 'set barring indicator = 'no''. All 'set barring indicator' blocks lead to 'continue call handling', which then leads 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: Information flow for barring of outgoing circuit switched calls. Lifelines: MS, MSC, VLR, MSC/LE. The sequence starts with MS sending a 'set-up' to MSC. MSC sends an 'information request' to VLR. VLR responds with 'information acknowledge' containing MAF017, MAF018, and MAF020. MSC checks OR1 (call barred). If Y (yes), it sends a 'call reject' with a cause to MS. If N (no), it sends a 'set-up' to MSC/LE. The text 'CONTINUE AS NORMAL CALL ESTABLISHMENT' is shown below the MSC lifeline.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant MSC/LE + MS->>MSC: set-up + MSC->>VLR: information request + VLR-->>MSC: information acknowledge +MAF017 +MAF018 +MAF020 + Note over MSC: OR1 Y + MSC-->>MS: call reject +(cause) + Note over MSC: OR1 N + MSC->>MSC/LE: set-up + Note over MSC, MSC/LE: CONTINUE AS NORMAL CALL ESTABLISHMENT + +``` + +Sequence diagram for Figure 6.10A: Information flow for barring of outgoing circuit switched calls. Lifelines: MS, MSC, VLR, MSC/LE. The sequence starts with MS sending a 'set-up' to MSC. MSC sends an 'information request' to VLR. VLR responds with 'information acknowledge' containing MAF017, MAF018, and MAF020. MSC checks OR1 (call barred). If Y (yes), it sends a 'call reject' with a cause to MS. If N (no), it sends a 'set-up' to MSC/LE. The text 'CONTINUE AS NORMAL CALL ESTABLISHMENT' is shown below the MSC lifeline. + +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: Information flow for barring of MO SMS. Lifelines: MS, SGSN or MSC/VLR or MME, IW-MSC. MS sends a 'Message Transfer' to SGSN or MSC/VLR or MME. The entity checks MAF017, MAF018, and MAF020. If OR1 is Y (yes), it sends a 'Failure Report' to MS. If OR1 is N (no), it sends a 'Forward Short Message' to IW-MSC.](a734898ce18e972938949637c32a34f4_img.jpg) + +``` + +sequenceDiagram + participant MS + participant SGSN or MSC/VLR or MME + participant IW-MSC + MS->>SGSN or MSC/VLR or MME: Message Transfer + Note over SGSN or MSC/VLR or MME: MAF017 +MAF018 +MAF020 + Note over SGSN or MSC/VLR or MME: OR1 Y + SGSN or MSC/VLR or MME-->>MS: Failure Report + Note over SGSN or MSC/VLR or MME: OR1 N + SGSN or MSC/VLR or MME->>IW-MSC: Forward Short Message + +``` + +Sequence diagram for Figure 6.10B: Information flow for barring of MO SMS. Lifelines: MS, SGSN or MSC/VLR or MME, IW-MSC. MS sends a 'Message Transfer' to SGSN or MSC/VLR or MME. The entity checks MAF017, MAF018, and MAF020. If OR1 is Y (yes), it sends a 'Failure Report' to MS. If OR1 is N (no), it sends a 'Forward Short Message' to 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 diagram for BAOC, BOIC and BOIC-exHC showing five states and their transitions.](73dff6b45b2b9ffd384bab3235f869af_img.jpg) + +``` + +stateDiagram-v2 + [*] --> S0 : Provision + S0 --> S1 : Deactivation + S1 --> S0 : Activation + S0 --> S2 : Network Induced + S2 --> S0 : Network Induced Ended + S1 --> S3 : Network Induced + S3 --> S1 : Network Induced Ended + S2 --> S4 : Deactivation + S4 --> S2 : Activation + S3 --> S4 : Deactivation + S4 --> S3 : Activation + S2 --> S0 : Withdrawal + S3 --> S0 : Withdrawal + S4 --> S0 : Withdrawal + +``` + +The diagram illustrates the state transition model for BAOC, BOIC and BOIC-exHC. It consists of five states represented by ovals, arranged in a circular fashion with additional internal transitions. + +- 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-Left State:** (Provisioned, Not Applicable, Not Active, Induced) +- Bottom-Right State:** (Provisioned, Not Applicable, Active and Operative, Induced) + +Transitions are as follows: + +- An arrow labeled **Provision** points from the top state to the left state. +- A double-headed arrow between the left and right states: **Deactivation** (left to right) and **Activation** (right to left). +- A double-headed arrow between the top and left states: **Withdrawal** (top to left) and **Provision** (left to top). +- A double-headed arrow between the top and right states: **Withdrawal** (top to right) and **Withdrawal** (right to top). +- A double-headed arrow between the left and bottom-left states: **Network Induced** (left to bottom-left) and **Network Induced Ended** (bottom-left to left). +- A double-headed arrow between the right and bottom-right states: **Network Induced** (right to bottom-right) and **Network Induced Ended** (bottom-right to right). +- A double-headed arrow between the bottom-left and bottom-right states: **Deactivation** (bottom-left to bottom-right) and **Activation** (bottom-right to bottom-left). +- A double-headed arrow between the top and bottom-right states: **Withdrawal** (top to bottom-right) and **Withdrawal** (bottom-right to top). +- A double-headed arrow between the left and bottom-right states: **Provision** (left to bottom-right) and **Withdrawal** (bottom-right to left). + +State transition model diagram for BAOC, BOIC and BOIC-exHC showing five states and their transitions. + +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. + +![Flowchart for Process BI1 showing the interaction between call barring programs. The process starts at an 'idle' state, proceeds to 'activate incoming barring program', then checks if 'other program active'. If 'yes', it goes to 'deactivate other program' before continuing. If 'no', it proceeds directly to 'activate requested program'. Both paths lead to 'acknowledge' and then back to an 'idle' state.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +Process BI1 + +388\_21(1) + +``` +graph TD; idle1([idle]) --> activate_incoming[activate incoming barring program]; activate_incoming --> other_active{other program active}; other_active -- yes --> deactivate[deactivate other program]; deactivate --> activate_requested[activate requested program]; other_active -- no --> activate_requested; activate_requested --> acknowledge{acknowledge}; acknowledge --> idle2([idle]); +``` + +Flowchart for Process BI1 showing the interaction between call barring programs. The process starts at an 'idle' state, proceeds to 'activate incoming barring program', then checks if 'other program active'. If 'yes', it goes to 'deactivate other program' before continuing. If 'no', it proceeds directly to 'activate requested program'. Both paths lead to 'acknowledge' and then back to an 'idle' state. + +Figure 7.1: BI1 Interaction between call barring programs + +![Flowchart for Process BI2 showing interactions between call forwarding and barring services. It starts with 'idle', branches into 'activate BAIC' and 'activate BIC-Roam', includes 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 'acknowledge' steps, ending at 'idle'. A legend defines CF, CCF, BAIC, and BIC-Roam.](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 with 'idle', branches into 'activate BAIC' and 'activate BIC-Roam', includes 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 'acknowledge' steps, ending at 'idle'. A legend defines CF, CCF, BAIC, and BIC-Roam. + +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 + + MS->>MSC: Activate BX + MSC->>VLR: Activate BX + VLR->>HLR: Activate BX + 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 +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. Upon receiving the activation request, the HLR enters state 'PW1' and responds with a 'Get password' message that cascades back through the VLR and MSC to the MS. The MS replies with a 'Password' message, which is passed back up the chain to the HLR. After processing the password, the HLR enters a state indicated by 'PW2', 'BI1', and 'BI2', then sends an 'Acknowledge' message back down to the VLR and then to the MSC. Finally, the MSC sends a 'Release complete' message to the MS, accompanied by a '\Facility' parameter. + +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 + + Note right of HLR: PW1 + MS->>MSC: Deactivate BI + MSC->>VLR: Deactivate BI + VLR->>HLR: Deactivate BI + 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. 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, which is passed back through the MSC and VLR to the HLR. The HLR sends an 'Acknowledge' message back to the VLR, which is passed back to the MSC and then to the MS. Finally, the MSC sends a 'Release complete' message to the MS, with a note indicating the inclusion of the '\Facility' parameter. Two password handling programs, PW1 and PW2, are indicated on the HLR side. + +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. The diagram involves four entities: MS, MSC, VLR, and HLR. The sequence of messages is: 1. MS sends 'Interrogate BX' to MSC. 2. MSC sends 'Interrogate BX' to VLR. 3. VLR sends 'Interrogate BX' to HLR. 4. HLR sends 'Acknowledge' back to VLR. 5. VLR sends 'Acknowledge' back to MSC. 6. MSC sends 'Release complete' back to MS, with a sub-parameter '\Facility'.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note left of MS: MS + MS->>MSC: Interrogate BX + Note right of MSC: MSC + MSC->>VLR: Interrogate BX + Note right of VLR: VLR + VLR->>HLR: Interrogate BX + Note right of HLR: HLR + HLR-->>VLR: Acknowledge + Note right of VLR: VLR + VLR-->>MSC: Acknowledge + Note right of MSC: MSC + MSC-->>MS: Release complete + Note left of MS: \Facility + +``` + +Sequence diagram showing the interrogation of barring of incoming calls. The diagram involves four entities: MS, MSC, VLR, and HLR. The sequence of messages is: 1. MS sends 'Interrogate BX' to MSC. 2. MSC sends 'Interrogate BX' to VLR. 3. VLR sends 'Interrogate BX' to HLR. 4. HLR sends 'Acknowledge' back to VLR. 5. VLR sends 'Acknowledge' back to MSC. 6. MSC sends 'Release complete' back to MS, with a sub-parameter '\Facility'. + +**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 Calls. The process starts at an 'idle' state, initiates handling of BAIC, checks if activated for basic service, sets the barring indicator to 'yes' or 'no', continues call handling, and returns to an 'idle' state. A note indicates BAIC: Barring of All Incoming Calls.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +Process MAF022 388\_26(1) + +``` +graph TD; idle1([idle]) --> initiate[initiate handling of BAIC]; initiate --> activated{activated for basic service}; activated -- yes --> setYes[set barring indicator = 'yes']; activated -- no --> setNo[set barring indicator = 'no']; setYes --> continue{continue call handling}; setNo --> continue; continue --> idle2([idle]); note[BAIC: Barring of All Incoming Calls.]; +``` + +Flowchart for Process MAF022: Barring of All Incoming Calls. The process starts at an 'idle' state, initiates handling of BAIC, checks if activated for basic service, sets the barring indicator to 'yes' or 'no', continues call handling, and returns to an 'idle' state. A note indicates BAIC: Barring of All Incoming Calls. + +**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. The flow starts at 'idle', goes to 'initiate handling of BIC-Roam', then checks 'roaming abroad'. If 'no', it goes to 'set barring indicator = 'no''. If 'yes', it checks 'activated for basic service'. If 'no', it goes to 'set barring indicator = 'no''. If 'yes', it goes to 'set barring indicator = 'yes''. Both 'yes' and 'no' paths lead to 'continue call handling', which then returns to 'idle'. A note indicates BIC-Roam is for calls when roaming outside the home PLMN country.](dd5771673aececa53d42ece89218299d_img.jpg) + +Process MAF023 388\_27(1) + +``` +graph TD; idle1([idle]) --> initiate[initiate handling of BIC-Roam]; initiate --> roaming{roaming abroad}; roaming -- no --> setNo[set barring indicator = 'no']; roaming -- yes --> activated{activated for basic service}; activated -- no --> setNo; activated -- yes --> setYes[set barring indicator = 'yes']; setYes --> continue{continue call handling}; setNo --> continue; continue --> idle2([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. The flow starts at 'idle', goes to 'initiate handling of BIC-Roam', then checks 'roaming abroad'. If 'no', it goes to 'set barring indicator = 'no''. If 'yes', it checks 'activated for basic service'. If 'no', it goes to 'set barring indicator = 'no''. If 'yes', it goes to 'set barring indicator = 'yes''. Both 'yes' and 'no' paths lead to 'continue call handling', which then returns to 'idle'. A note indicates BIC-Roam is for calls when roaming outside the home PLMN country. + +**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 shows interactions between MSa, MSCa, HLRb, MSCb, and MSb. The bottom diagram shows interactions between TE, LE, HLRb, MSCb, and MSb. Both diagrams show a 'set-up' message from MSa/TE to MSCa/LE, followed by an 'info req' from MSCa/LE to HLRb, an 'info ack' from HLRb to MSCa/LE, a 'call reject' with '(cause)' from MSCa/LE to MSa/TE, and a 'set-up' message from MSCa/LE to MSCb to MSb. A 'CONTINUE AS NORMAL CALL ESTABLISHMENT' message is also shown.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +The diagram consists of two sequence diagrams illustrating the information flow for barring of incoming circuit switched calls. + +**Top Sequence Diagram:** + +- Participants: MSa, MSCa, HLRb, MSCb, MSb. +- MSa sends a **set-up** message to MSCa. +- MSCa sends an **info req** message to HLRb. +- HLRb responds with **info ack** (containing MAF022, MAF023). +- MSCa sends a **call reject** message with **(cause)** to MSa. +- MSCa also sends a **set-up** message to MSCb. +- MSCb sends a **set-up** message to MSb. +- MSCa sends a **CONTINUE AS NORMAL CALL ESTABLISHMENT** message to HLRb. +- MSCa has two internal states: **OR1 Y** and **OR1 N**. + +**Bottom Sequence Diagram:** + +- Participants: TE, LE, HLRb, MSCb, MSb. +- TE sends a **set-up** message to LE. +- LE sends an **info req** message to HLRb. +- HLRb responds with **info ack** (containing MAF022, MAF023). +- LE sends a **call reject** message with **(cause)** to TE. +- LE also sends a **set-up** message to MSCb. +- MSCb sends a **set-up** message to MSb. +- LE sends a **CONTINUE AS NORMAL CALL ESTABLISHMENT** message to HLRb. +- LE has two internal states: **OR1 Y** and **OR1 N**. + +Sequence diagrams showing information flow for barring of incoming circuit switched calls. The top diagram shows interactions between MSa, MSCa, HLRb, MSCb, and MSb. The bottom diagram shows interactions between TE, LE, HLRb, MSCb, and MSb. Both diagrams show a 'set-up' message from MSa/TE to MSCa/LE, followed by an 'info req' from MSCa/LE to HLRb, an 'info ack' from HLRb to MSCa/LE, a 'call reject' with '(cause)' from MSCa/LE to MSa/TE, and a 'set-up' message from MSCa/LE to MSCb to MSb. A 'CONTINUE AS NORMAL CALL ESTABLISHMENT' message is also shown. + +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 + + Note right of SMS-GMSC: OR1 Y + SMS-GMSC->>HSS/HLR: Info req + HSS/HLR-->>SMS-GMSC: Info ack + Note right of HSS/HLR: MAF022 +MAF023 + Note right of SMS-GMSC: OR1 N + SMS-GMSC->>SGSN or MSC/VLR or MME: Forward Short Message + Note right of SMS-GMSC: Continue as normal SMS transfer + SMS-GMSC->>SC: Failure Report + +``` + +The diagram illustrates the interaction for barring MT SMS. It starts with the SC sending a 'Message Transfer' to the SMS-GMSC. The SMS-GMSC sends an 'Info req' to the HSS/HLR. The HSS/HLR responds with an 'Info ack' and includes error codes 'MAF022' and 'MAF023'. Inside the HSS/HLR, there are two logical paths for 'OR1' (call barred): 'Y' (yes) and 'N' (no). If 'OR1 Y', the SMS-GMSC sends a 'Failure Report' back to the SC. If 'OR1 N', the SMS-GMSC sends a 'Forward Short Message' to the SGSN or MSC/VLR or MME and continues with 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 --> [*] : Withdrawal + S1 --> S2 : Deactivation + S2 --> S1 : Activation + S2 --> [*] : 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 + +``` + +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. + +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 --> S2 : SS-I + S3 --> S1 : SS-I/E + S3 --> S2 : Withdrawal + S4 --> S1 : Deactivation + S4 --> S3 : SS-I + 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, each containing a set of conditions. The states are: + + +- State 1 (Top):** (Not Provisioned, Not Applicable, Not Active, Not Induced) +- State 2 (Left):** (Provisioned, Not Applicable, Not Active, Not Induced) +- State 3 (Right):** (Provisioned, Not Applicable, Active and Operative, Not Induced) +- State 4 (Bottom):** (Provisioned, Not Applicable, Active and Quiescent, Not Induced) + + Transitions between states are as follows: + + +- An arrow labeled **Provision** points from an external source to State 1. +- A double-headed arrow labeled **Withdrawal** connects State 1 and State 2. +- A double-headed arrow labeled **Deactivation** connects State 2 and State 1. +- A double-headed arrow labeled **Activation** connects State 2 and State 3. +- A curved arrow labeled **Withdrawal** points from State 3 back to State 1. +- A double-headed arrow labeled **SS-I** connects State 3 and State 4. +- A curved arrow labeled **SS-I/E** points from State 3 to State 1. +- A curved arrow labeled **Withdrawal** points from State 3 to State 2. +- A double-headed arrow labeled **Deactivation** connects State 4 and State 1. + +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: 1. Top state: (Not Provisioned, Not Applicable, Not Active, Not Induced). 2. Bottom-left state: (Provisioned, Not Applicable, Not Active, Not Induced). 3. Bottom-right state: (Provisioned, Not Applicable, Active and Operative, Not Induced). Transitions: 'Provision' from Top to Bottom-left; 'Withdrawal' from Bottom-left to Top; 'Deactivation' from Bottom-right to Bottom-left; 'Activation' from Bottom-left to Bottom-right; 'Withdrawal' from Bottom-right to Top.](02d0c8a07c481d880b73a25d02050fad_img.jpg) + +``` + +stateDiagram-v2 + [*] --> State1 : (Not Provisioned, Not Applicable, Not Active, Not Induced) + State1 --> State2 : Provision + State2 --> State1 : Withdrawal + State2 --> State3 : Activation + State3 --> State2 : Deactivation + State3 --> State1 : Withdrawal + +``` + +State transition model for ACR. The diagram shows three states represented by ovals: 1. Top state: (Not Provisioned, Not Applicable, Not Active, Not Induced). 2. Bottom-left state: (Provisioned, Not Applicable, Not Active, Not Induced). 3. Bottom-right state: (Provisioned, Not Applicable, Active and Operative, Not Induced). Transitions: 'Provision' from Top to Bottom-left; 'Withdrawal' from Bottom-left to Top; 'Deactivation' from Bottom-right to Bottom-left; 'Activation' from Bottom-left to Bottom-right; 'Withdrawal' from 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) + GMSC->>HLR: Response (MSRN) + + Note over GMSC, 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 + +| Change history | | | | | | | | | +|----------------|-----------|---------|------|-----|--------|-----|---------|---------------------------------------------------------------------------------------| +| TSG CN# | Spec | Old Ver | CR | Rev | Phase | Cat | New Ver | Subject/Comment | +| Apr 1999 | GSM 03.88 | 6.0.0 | | | R97 | | | Transferred to 3GPP CN1 | +| CN#03 | 23.088 | | | | R99 | | 3.0.0 | Approved at CN#03 | +| CN#07 | 23.088 | 3.0.0 | 001 | 1 | R99 | | 3.1.0 | Introduction of 'Notification to CSE flag' to the call barring supplementary service. | +| CN#09 | 23.088 | 3.1.0 | 002 | 1 | R99 | F | 3.2.0 | SDL refresh | +| CN#11 | 23.088 | 3.2.0 | | | Rel-4 | | 4.0.0 | Release 4 after CN#11 | +| CN#16 | 23.088 | 4.0.0 | | | Rel-5 | | 5.0.0 | Release 5 after CN#16 | +| CN#19 | 23.088 | 5.0.0 | 003 | 1 | Rel-6 | | 6.0.0 | Introducing SMS Call Barring in PS domain | +| CT#36 | 23.088 | 6.0.0 | | | Rel-7 | | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 23.088 | 7.0.0 | | | Rel-8 | | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | 23.088 | 8.0.0 | - | - | Rel-9 | | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | 23.088 | 9.0.0 | - | - | Rel-10 | | 10.0.0 | Update to Rel-10 version (MCC) | +| CT#53 | 23.088 | 10.0.0 | 0004 | 2 | Rel-11 | B | 11.0.0 | Addition of Anonymous Call Rejection in the CS domain | +| CT#54 | 23.088 | 11.0.0 | 0005 | 1 | Rel-11 | B | 11.1.0 | Originating & Terminating network Information Flows | +| CT#62 | 23.088 | 11.1.0 | 0006 | 1 | Rel-11 | F | 11.2.0 | SMSC Usage Restriction in Roaming | +| - | | 11.2.0 | | | | | 11.2.1 | Change History updated to include CR#0006r1 | +| CT#63 | 23.088 | 11.2.1 | 0007 | 1 | Rel-11 | F | 11.3.0 | Call barring services with the SMS in MME option | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23240/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-11/23_series/23240/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..634ae8bbab91d7fa9c3f6af1e1b7bccfe29f4048 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23240/6470d350326789d5306eabcb76533951_img.jpg b/marked/Rel-11/23_series/23240/6470d350326789d5306eabcb76533951_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc59803fc36fe4fb84ae6c73356379717d94ae83 --- /dev/null +++ b/marked/Rel-11/23_series/23240/6470d350326789d5306eabcb76533951_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b689c1abd1a33ea619b26f26a543deb93b6b9368537145192952f865dd566eb5 +size 92012 diff --git a/marked/Rel-11/23_series/23240/68d8089266ace7197304b43dcaf5d08e_img.jpg b/marked/Rel-11/23_series/23240/68d8089266ace7197304b43dcaf5d08e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acca8f3616fb212c05fd1a80ff73360ffe9824ac --- /dev/null +++ b/marked/Rel-11/23_series/23240/68d8089266ace7197304b43dcaf5d08e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f42e898ee3f6b6104ed5790532b13eab37bcac1575c5ed0d02cd6713be9700c5 +size 43256 diff --git a/marked/Rel-11/23_series/23240/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-11/23_series/23240/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..605f8c0baadd22e4bec5a93e1894db12ea2f7335 --- /dev/null +++ b/marked/Rel-11/23_series/23240/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:958bb471bdb37cd2a16f1036bd4909149f9c3d93c99eb783b57ed515d16edcd9 +size 113526 diff --git a/marked/Rel-11/23_series/23240/94fd137860c16c8dfd75512f10161fe8_img.jpg b/marked/Rel-11/23_series/23240/94fd137860c16c8dfd75512f10161fe8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e553f842e2126299128f6bf90b658d8ad532ea2e --- /dev/null +++ b/marked/Rel-11/23_series/23240/94fd137860c16c8dfd75512f10161fe8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d310adbfe27b7951d2ef6bbb2a02d7d323fc8e18ae8b80a20715bd12671ddfa +size 28832 diff --git a/marked/Rel-11/23_series/23240/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-11/23_series/23240/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7d0db17231d62c9ef18c4d0484414237ae2a92a --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23240/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-11/23_series/23240/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98ecb2a8a216fe469052c6ea4f674e38eebec29f --- /dev/null +++ b/marked/Rel-11/23_series/23240/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:248a882a7e0a1cd2901bb61ae997baa8b2e6ee3d1d619a3fd0765f4414c29360 +size 32659 diff --git a/marked/Rel-11/23_series/23240/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/Rel-11/23_series/23240/c2fc2621e8206d24427b56bcb2398fc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e5d0cc4f39b9d8bd5e74e4bb2b6832eb985176c --- /dev/null +++ b/marked/Rel-11/23_series/23240/c2fc2621e8206d24427b56bcb2398fc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6ec59c2127a01da7bcf176f94acefdc144d265e772cb52f6929fd3b74fb81e3 +size 34532 diff --git a/marked/Rel-11/23_series/23240/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/Rel-11/23_series/23240/dbe553cf16dd14073b89a8263a428664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e2dfd654d314115918331ad70831a7cfa71d346 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23240/raw.md b/marked/Rel-11/23_series/23240/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d8462a1ae2fb48a69e3f303149cc1e2a05011cd6 --- /dev/null +++ b/marked/Rel-11/23_series/23240/raw.md @@ -0,0 +1,1112 @@ + + + + + + +# 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, + +# --- 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. Below the 'GUP Server' box is a line labeled 'Rp'. Below this line, three boxes are shown: 'RAF', 'RAF', and '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.)'. A vertical line connects the 'GUP Server' box to the first 'RAF' box. A vertical line connects the 'GUP Server' box to the second 'RAF' box. A vertical line connects the 'GUP Server' box to the third 'RAF' box. A legend indicates that the dashed line represents communication that can take place directly between the 'Application in HPLMN' and 'GUP Data Repositories'. + +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 locates (b) data in a GUP Data Repository. The GUP Server then sends a request (c) to the GUP Data Repository, which returns a response (d) to the GUP Server. Finally, the GUP Server sends a response (e) to the Requestor.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg) + +``` +graph TD; Requestor[Requestor] -- "a) request" --> GUPServer[GUP Server]; GUPServer -- "b) locate" --> GUPDataRepo1[GUP Data Repository]; GUPServer -- "c) request" --> GUPDataRepo2[GUP Data Repository]; GUPDataRepo1 -- "d) response" --> GUPServer; GUPDataRepo2 -- "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 locates (b) data in a GUP Data Repository. The GUP Server then sends a request (c) to the GUP Data Repository, which returns a response (d) to the GUP Server. Finally, the GUP Server sends a response (e) to the Requestor. + +Figure 4.3: GUP Server acting as a Proxy Server + +![Diagram illustrating the GUP Server acting as a Redirect Server. A Requestor sends a request (a) to the GUP Server, which responds (c). The GUP Server then sends a locate (b) to the GUP Server. The GUP Server sends a request (d) to the GUP Data Repository, which responds (e). The GUP Data Repository then sends a response (e) back to the GUP Server, which in turn sends a response (c) back to the Requestor.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` + +sequenceDiagram + participant Requestor + participant GUP Server + participant GUP Data Repository 1 as GUP Data Repository + participant GUP Data Repository 2 as GUP Data Repository + Note right of GUP Server: b) locate + Requestor->>GUP Server: a) request + GUP Server-->>Requestor: c) response + Note left of GUP Data Repository 1: d) request + Note left of GUP Data Repository 2: e) response + Requestor->>GUP Data Repository 1: d) request + Requestor->>GUP Data Repository 2: e) response + +``` + +Diagram illustrating the GUP Server acting as a Redirect Server. A Requestor sends a request (a) to the GUP Server, which responds (c). The GUP Server then sends a locate (b) to the GUP Server. The GUP Server sends a request (d) to the GUP Data Repository, which responds (e). The GUP Data Repository then sends a response (e) back to the GUP Server, which in turn sends a response (c) back 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 a GUP request from the Application to the GUP Server, followed by authentication and data element identification. The GUP Server then requests data elements A and B from the RAF, which in turn requests them from the GUP Data Repository, receives them, and returns them to the RAF and then the GUP Server. Finally, the GUP Server composes the GUP component and delivers it to the Application. Interface labels Rg, Rp, and vendor-specific interface are shown at the bottom.](a33da0f14e456f92539ce3e9b7d81f9a_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. + Note right of GUP Server: Identify and localise data elements. + + Application->>GUP Server: GUP request + 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 + Note right of GUP Server: Compose GUP component = data element A + data element B + GUP Server-->>Application: Deliver GUP component +``` + +The diagram illustrates the interaction between four entities: Application, GUP Server, RAF, and GUP Data Repository. The sequence of messages is as follows: 1. The Application sends a 'GUP request' to the GUP Server. 2. The GUP Server performs internal actions: 'Authenticate the application and check authorisation.' and 'Identify and localise data elements.' 3. The GUP Server sends a 'Request GUP data element A' to the RAF. 4. The RAF sends a 'Request GUP data element A' to the GUP Data Repository. 5. The GUP Data Repository returns 'Deliver GUP data element A' to the RAF. 6. The RAF returns 'Deliver GUP data element A' to the GUP Server. 7. The GUP Server sends a 'Request GUP data element B' to the RAF. 8. The RAF sends a 'Request GUP data element B' to the GUP Data Repository. 9. The GUP Data Repository returns 'Deliver GUP data element B' to the RAF. 10. The RAF returns 'Deliver GUP data element B' to the GUP Server. 11. The GUP Server performs an internal action: 'Compose GUP component = data element A + data element B'. 12. The GUP Server sends a 'Deliver GUP component' message to the Application. At the bottom, interface labels are present: 'Rg' under the Application/GUP Server boundary, 'Rp' under the GUP Server/RAF boundary, and 'vendor-specific interface' under the RAF/GUP Data Repository boundary. + +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 a GUP request from the Application to the GUP Server, followed by authentication and data element identification. The GUP Server then requests data elements A and B from the RAF, which in turn requests them from the GUP Data Repository, receives them, and returns them to the RAF and then the GUP Server. Finally, the GUP Server composes the GUP component and delivers it to the Application. Interface labels Rg, Rp, and vendor-specific interface are shown at the bottom. + +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 GUP Server, which redirects it to 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. The Application then requests GUP data element B from the GUP Server, which again redirects it to 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. The diagram is divided into three sections: Rg (between Application and GUP Server), Rp (between GUP Server and RAF), and vendor-specific interface (between RAF and GUP Data Repository).](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +sequenceDiagram + participant Application + participant GUP Server + participant RAF + participant GUP Data Repository + + Note left of Application: Rg + Application->>GUP Server: GUP request + Note right of GUP Server: Rp + GUP Server-->>Application: Authenticate the application and check authorization. +Identify and localise data elements. +Deliver references and authorisation credentials for data elements A and B + Note right of Application: vendor-specific interface + Application->>GUP Server: Request GUP data element A + GUP Server->>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->>GUP Server: Request GUP data element B + GUP Server->>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 + +``` + +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 GUP Server, which redirects it to 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. The Application then requests GUP data element B from the GUP Server, which again redirects it to 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. The diagram is divided into three sections: Rg (between Application and GUP Server), Rp (between GUP Server and RAF), and vendor-specific interface (between RAF and GUP Data Repository). + +Figure 4.6: An Application requesting GUP data component(s) message flow (Redirect mode) + +## 4.3 Rg reference point procedures + +This subclause 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 subclause. + +#### 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 subclause 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 subclause 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 subclause 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 subclause 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 subclause 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 subclause 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 subclause. + +#### 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 the interaction between Application A, GUP Server, HSS 1, and HSS 2. Step 1: Application A sends an Rg (Request) to GUP Server. Step 2: GUP Server sends an Rp (Response) to HSS 1. Step 3: HSS 1 sends an Rp (Response) to GUP Server. Step 4: GUP Server sends an Rg (Request) to HSS 2. Step 5: GUP Server sends an Rp (Response) 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 + HSS 1->>GUP Server: Step 4 Rp + GUP Server->>HSS 2: Step 5 Rg + GUP Server->>Application A: Step 5 Rp + +``` + +Figure A.2: An Example of the Interworking Diagram between GUP and an Application. The diagram shows the interaction between Application A, GUP Server, HSS 1, and HSS 2. Step 1: Application A sends an Rg (Request) to GUP Server. Step 2: GUP Server sends an Rp (Response) to HSS 1. Step 3: HSS 1 sends an Rp (Response) to GUP Server. Step 4: GUP Server sends an Rg (Request) to HSS 2. Step 5: GUP Server sends an Rp (Response) 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](mailto: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 23.141 | 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 | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23246/02d0c8a07c481d880b73a25d02050fad_img.jpg b/marked/Rel-11/23_series/23246/02d0c8a07c481d880b73a25d02050fad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3147dc005cbe9c986d4c073ddaade7b7b2e658aa --- /dev/null +++ b/marked/Rel-11/23_series/23246/02d0c8a07c481d880b73a25d02050fad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6399cbf9cbeda902441d1c996244c6fe8927034b04d310e44a9be86a26aed0cb +size 61688 diff --git a/marked/Rel-11/23_series/23246/030c758fd425016b03290c8f11bef69d_img.jpg b/marked/Rel-11/23_series/23246/030c758fd425016b03290c8f11bef69d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19c1ad36ccb7493050b10ac209379fe805f7ecb5 --- /dev/null +++ b/marked/Rel-11/23_series/23246/030c758fd425016b03290c8f11bef69d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca5f0e9fe9c5bcdcbb150adec9d529a0340c1b966c126d7674941a0ee8e2e23d +size 59650 diff --git a/marked/Rel-11/23_series/23246/1841f348dfa81a3438d4e1f8465d9ac7_img.jpg b/marked/Rel-11/23_series/23246/1841f348dfa81a3438d4e1f8465d9ac7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93c3fb9c9c79f1f0d98b64235075a780bbf6faad --- /dev/null +++ b/marked/Rel-11/23_series/23246/1841f348dfa81a3438d4e1f8465d9ac7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b28b80a94f16974524afa131c89114cbb4acfecf8bc607ad19c63a651ab792e5 +size 112807 diff --git a/marked/Rel-11/23_series/23246/1e8c50ad4fca7f315a407347dd5091cc_img.jpg b/marked/Rel-11/23_series/23246/1e8c50ad4fca7f315a407347dd5091cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22d5aff09fdd87375416ee447a4619d95eacb2af --- /dev/null +++ b/marked/Rel-11/23_series/23246/1e8c50ad4fca7f315a407347dd5091cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbdace43b27ca48211d688786d944d2717e1e6487492bb7ad429d16bb2819422 +size 54646 diff --git a/marked/Rel-11/23_series/23246/65550960f5c5afd9d27706aaeddb0638_img.jpg b/marked/Rel-11/23_series/23246/65550960f5c5afd9d27706aaeddb0638_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38f8a0b4d4a07096cf633b1ed7a3931de2ce8b99 --- /dev/null +++ b/marked/Rel-11/23_series/23246/65550960f5c5afd9d27706aaeddb0638_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5241f7b00425584840a627094198fb5746adfe0abad43a12bab3221e26e4ba32 +size 42532 diff --git a/marked/Rel-11/23_series/23246/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-11/23_series/23246/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50f60aac729edce31da16daa15711443f5340a78 --- /dev/null +++ b/marked/Rel-11/23_series/23246/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8be5ad60a7dfcae8b37040aec6af8c0f97b41c38301a556709b7ee6be86f5386 +size 102548 diff --git a/marked/Rel-11/23_series/23246/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-11/23_series/23246/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3410e07e1bc8b9b6541ee462140521d4e761d685 --- /dev/null +++ b/marked/Rel-11/23_series/23246/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2e4af78a151c481f13344641d6b99d877448a5f636a8ab15faf07aa1efd15f6 +size 16332 diff --git a/marked/Rel-11/23_series/23246/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-11/23_series/23246/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eefc55aa8abfccc29ab6a4909de8c53e20119d46 --- /dev/null +++ b/marked/Rel-11/23_series/23246/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1025c3e642c5965d54075e1a96998418915b2b0fa09d170b6a568663d6488b89 +size 68527 diff --git a/marked/Rel-11/23_series/23246/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-11/23_series/23246/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c96128a82e8d51c54d5a06f52ea4c4b35d52f25b --- /dev/null +++ b/marked/Rel-11/23_series/23246/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cca8790cb06eb03abe0e73d68be1d0def5e864902726340ff5e210baa724720d +size 159403 diff --git a/marked/Rel-11/23_series/23246/aeb2a26a07219661191294dba528067a_img.jpg b/marked/Rel-11/23_series/23246/aeb2a26a07219661191294dba528067a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b057e9619f3c92879db2fce5a58f9f8792f7f94b --- /dev/null +++ b/marked/Rel-11/23_series/23246/aeb2a26a07219661191294dba528067a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19c81346dc3597e6e5611bc5c3da9243cd450af121296c89d2cedd8ebd0c3653 +size 13680 diff --git a/marked/Rel-11/23_series/23246/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-11/23_series/23246/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bd053759c7acdceef2285f99cdef823e7ad3706 --- /dev/null +++ b/marked/Rel-11/23_series/23246/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c0fdf48344b114700083c02de566a5e7dec284de8b5cf6e73cb50cbd815c3b8 +size 104492 diff --git a/marked/Rel-11/23_series/23271/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg b/marked/Rel-11/23_series/23271/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43705977691b87420b1f0918d1f9972f9c2c6ed1 --- /dev/null +++ b/marked/Rel-11/23_series/23271/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62ae71e80da9d7525f1dadb7a76c5e34523fc945c720fe1b5737a46317ed7190 +size 28248 diff --git a/marked/Rel-11/23_series/23271/070352b751dd0711b8ac6ddfa6df1d98_img.jpg b/marked/Rel-11/23_series/23271/070352b751dd0711b8ac6ddfa6df1d98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47b162ba0d12cfcee6acbc06741a72b30fc13fc1 --- /dev/null +++ b/marked/Rel-11/23_series/23271/070352b751dd0711b8ac6ddfa6df1d98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba9af6c6ccb602a6b497716d53b305182118a8f1938555d497c6b4772258a653 +size 75141 diff --git a/marked/Rel-11/23_series/23271/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/marked/Rel-11/23_series/23271/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d9589c2f0d2df6a64753decb65d0bb3d8f5c52a9 --- /dev/null +++ b/marked/Rel-11/23_series/23271/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d586c8d2834029557af4db310cd25b6d0851c9828627b129c4fb15e13d702a97 +size 74035 diff --git a/marked/Rel-11/23_series/23271/0f7871077bba48a2c97f7859a5edda0d_img.jpg b/marked/Rel-11/23_series/23271/0f7871077bba48a2c97f7859a5edda0d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4dfea8f185f0087b01d4612d881f7d06271708db --- /dev/null +++ b/marked/Rel-11/23_series/23271/0f7871077bba48a2c97f7859a5edda0d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d15b8b11513d04ca19893291e3e31adc7b6cc3182d0acebfea357ba07c1c6630 +size 45866 diff --git a/marked/Rel-11/23_series/23271/10ceb47973510a1b47421741263146cc_img.jpg b/marked/Rel-11/23_series/23271/10ceb47973510a1b47421741263146cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fcb096457b9d181806720f06290062dd67a5b760 --- /dev/null +++ b/marked/Rel-11/23_series/23271/10ceb47973510a1b47421741263146cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:659d6909ce3ac66f7f7e7eaf8c248b89d2ef19a68ab09e4282ff2ca6a1c0ddf7 +size 59211 diff --git a/marked/Rel-11/23_series/23271/195611c20b2dc7ed0fa3033392e22908_img.jpg b/marked/Rel-11/23_series/23271/195611c20b2dc7ed0fa3033392e22908_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b70795a35a4f259f6726f66b77d20ebd82b58ea0 --- /dev/null +++ b/marked/Rel-11/23_series/23271/195611c20b2dc7ed0fa3033392e22908_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee2c19d96fc966f354472d7b0aa2757262c0c2a2293ab9b714a63a5472996ad1 +size 94301 diff --git a/marked/Rel-11/23_series/23271/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg b/marked/Rel-11/23_series/23271/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ad3d731cc9c4d21c5ad8555eda36c8e37490fe1 --- /dev/null +++ b/marked/Rel-11/23_series/23271/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c078a8c6646542dbdd314bf828b74d7ea0030094ef9e513e48a3fec227e78e1f +size 169442 diff --git a/marked/Rel-11/23_series/23271/2b00743506f6a3bbd17af764162dc76d_img.jpg b/marked/Rel-11/23_series/23271/2b00743506f6a3bbd17af764162dc76d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6bc3bffc9cf854c91be83779fb94db885f684ff --- /dev/null +++ b/marked/Rel-11/23_series/23271/2b00743506f6a3bbd17af764162dc76d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ac52d0b9b6ca16bfcede6c74c8e25605469f68cfe4a8d09e95faed15491b810 +size 107186 diff --git a/marked/Rel-11/23_series/23271/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/marked/Rel-11/23_series/23271/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43dc09aef60518cc55bf69ac02db5d9a39e47804 --- /dev/null +++ b/marked/Rel-11/23_series/23271/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:189f94226926c8f6eeb23af10959e1f0483f4462d6222601375c82d40b0e19d8 +size 94066 diff --git a/marked/Rel-11/23_series/23271/497d7e14540664a2914557cad79f3791_img.jpg b/marked/Rel-11/23_series/23271/497d7e14540664a2914557cad79f3791_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e296c6e6d80491121f288bfe1624e261ec84a93d --- /dev/null +++ b/marked/Rel-11/23_series/23271/497d7e14540664a2914557cad79f3791_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a185f0ebf0ba1db1289abe9285d784577097644b261bd6343bb49de944d3a796 +size 49446 diff --git a/marked/Rel-11/23_series/23271/4f7470055bfc22c4aa6b007a4056940e_img.jpg b/marked/Rel-11/23_series/23271/4f7470055bfc22c4aa6b007a4056940e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..311774dfe37ce1b3397f8fe0680978ff86a0113d --- /dev/null +++ b/marked/Rel-11/23_series/23271/4f7470055bfc22c4aa6b007a4056940e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b240bc424bc6d775cb8688110230a87e9faa7209084aaeb0cc43857e39f144a +size 56155 diff --git a/marked/Rel-11/23_series/23271/5a01395925fc88802da68fb5ac0f31ff_img.jpg b/marked/Rel-11/23_series/23271/5a01395925fc88802da68fb5ac0f31ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6f23a45756b88c2d172076c2555ab7b89d9a669 --- /dev/null +++ b/marked/Rel-11/23_series/23271/5a01395925fc88802da68fb5ac0f31ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5bf7d6345aae1c2502d92b1903a05ed6d6b25600fe8612379e540b1d4dc7266 +size 86719 diff --git a/marked/Rel-11/23_series/23271/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/marked/Rel-11/23_series/23271/5cf80bac69830ea773ac17c87e0ae24d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9c6040754a82788ba6c341ea04ba77cfa5c6957 --- /dev/null +++ b/marked/Rel-11/23_series/23271/5cf80bac69830ea773ac17c87e0ae24d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3ebcb605152813a4d750e3fe4abf02b50ec8ad9042205a6c635e410e880075e +size 75345 diff --git a/marked/Rel-11/23_series/23271/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-11/23_series/23271/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fa73b7be57ce89382b6d790bcce7aca68eeaa3e --- /dev/null +++ b/marked/Rel-11/23_series/23271/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60a97f884530beb37824103f9904451db1d9b95e4558674576185901315da888 +size 56689 diff --git a/marked/Rel-11/23_series/23271/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-11/23_series/23271/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..285b4d6075da5abdd0b5827bf3ed3cb6b72c7328 --- /dev/null +++ b/marked/Rel-11/23_series/23271/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:870b1b335d3b520e7abaf17e7ffc4012d86a0c0d655fbfa985d164e29b5ac082 +size 173272 diff --git a/marked/Rel-11/23_series/23271/69467ece0a576b4c2ec3e0c89ba61527_img.jpg b/marked/Rel-11/23_series/23271/69467ece0a576b4c2ec3e0c89ba61527_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56a80fd0062463b1074e2590e477e13c660d999c --- /dev/null +++ b/marked/Rel-11/23_series/23271/69467ece0a576b4c2ec3e0c89ba61527_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8b204c26d617c3e6986e58a0e66db9b4a5f5cfb68dfe50c1976242075f166f4 +size 84417 diff --git a/marked/Rel-11/23_series/23271/6ba310120ebcd99661c4ee1c58a1586c_img.jpg b/marked/Rel-11/23_series/23271/6ba310120ebcd99661c4ee1c58a1586c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b92702244ab515e6e40361f8fc267e597069e094 --- /dev/null +++ b/marked/Rel-11/23_series/23271/6ba310120ebcd99661c4ee1c58a1586c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b05915263de524610ae81061c096602cb86a1a6a1bf2254e8a4784c1193f5fde +size 52344 diff --git a/marked/Rel-11/23_series/23271/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-11/23_series/23271/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..403bff9ec34ce24136e48437641bb12f8b794592 --- /dev/null +++ b/marked/Rel-11/23_series/23271/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c37903378bc7e62b626b87c901e4ee1f02145115ebd60bca81caed9fd6c6901 +size 105891 diff --git a/marked/Rel-11/23_series/23271/74e409e1548dd2606c4de9bdfe9806e4_img.jpg b/marked/Rel-11/23_series/23271/74e409e1548dd2606c4de9bdfe9806e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..623f04382cfb8f61959df4a6aa87bd3e4e9abb05 --- /dev/null +++ b/marked/Rel-11/23_series/23271/74e409e1548dd2606c4de9bdfe9806e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:077e0b178689e4eac451c8d52d29ed584daaf7857fbb387672975fba7690e12a +size 38632 diff --git a/marked/Rel-11/23_series/23271/7b18671bc31881a5c474883bf6a300fd_img.jpg b/marked/Rel-11/23_series/23271/7b18671bc31881a5c474883bf6a300fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74b6ba5b4f5d4000ddc1ee7366b0ec13efdfe1d2 --- /dev/null +++ b/marked/Rel-11/23_series/23271/7b18671bc31881a5c474883bf6a300fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7483036bf7b7cff784d3e59245ddcd2df208810f7ade9faf29812b39f96439c +size 68620 diff --git a/marked/Rel-11/23_series/23271/86986d4dfd54f298d7b9fa9f82ab3009_img.jpg b/marked/Rel-11/23_series/23271/86986d4dfd54f298d7b9fa9f82ab3009_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1def566af5f3d414067e62ea600182b4298c786a --- /dev/null +++ b/marked/Rel-11/23_series/23271/86986d4dfd54f298d7b9fa9f82ab3009_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46282f542a00d10486bdfee56a685b1684bccdf13ce0699f9d97a1c8737299c8 +size 85975 diff --git a/marked/Rel-11/23_series/23271/86b4670fc1a5a694821ee92b99c1209a_img.jpg b/marked/Rel-11/23_series/23271/86b4670fc1a5a694821ee92b99c1209a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ce4dc1c0bbb7ec66d5daddbc2310086f2002195 --- /dev/null +++ b/marked/Rel-11/23_series/23271/86b4670fc1a5a694821ee92b99c1209a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ff5b593a2274960e225417b8a859b4f0800b14d3aedf8010968d19e6529676e +size 62725 diff --git a/marked/Rel-11/23_series/23271/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg b/marked/Rel-11/23_series/23271/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..063bca3ce458213d2015f90c2d34d7a03b7b0055 --- /dev/null +++ b/marked/Rel-11/23_series/23271/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3f6001a272a3ae459e677da1e208f4ac6093c9219e5446ac4ee3aa1c35cdf5b +size 18595 diff --git a/marked/Rel-11/23_series/23271/8bdf315853992d21f389da554f3a8215_img.jpg b/marked/Rel-11/23_series/23271/8bdf315853992d21f389da554f3a8215_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ccc1bae3abdc33b82d83aed8621881a39fcfa35 --- /dev/null +++ b/marked/Rel-11/23_series/23271/8bdf315853992d21f389da554f3a8215_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f3a83c982a0f6eea2fae5c0f82196e01fdf3736ed0b837518f017c6e3c4a5e3 +size 47373 diff --git a/marked/Rel-11/23_series/23271/8edfc370769207831f060f44d2281084_img.jpg b/marked/Rel-11/23_series/23271/8edfc370769207831f060f44d2281084_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f0693436f62794a089c9c79537b5f2f7d876522 --- /dev/null +++ b/marked/Rel-11/23_series/23271/8edfc370769207831f060f44d2281084_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:789be23e09472ddb612a9a20d3fcaa5fc2b7a936e2f1309b20dcf0bb7cba77b3 +size 104368 diff --git a/marked/Rel-11/23_series/23271/92724c769da9d46b730fde1a6dccb023_img.jpg b/marked/Rel-11/23_series/23271/92724c769da9d46b730fde1a6dccb023_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f4e3945c2f34bf16d650c256cf70fb9237b92a9 --- /dev/null +++ b/marked/Rel-11/23_series/23271/92724c769da9d46b730fde1a6dccb023_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4625f5f01657b2586bb80914f876e393fc668cc22d884e82cb782c74e471ad0 +size 125523 diff --git a/marked/Rel-11/23_series/23271/92c4d3a4d29d64c167855449f1aeba2a_img.jpg b/marked/Rel-11/23_series/23271/92c4d3a4d29d64c167855449f1aeba2a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a24510bb40abb7b9f1918a1ee3f68decaea6f94a --- /dev/null +++ b/marked/Rel-11/23_series/23271/92c4d3a4d29d64c167855449f1aeba2a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0db6e4ea794161a61fefa9dad46876e66a73d38bb404274aeecd4a9fcefc9707 +size 28783 diff --git a/marked/Rel-11/23_series/23271/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-11/23_series/23271/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a660134ce2a00b7169d898734bbe9e8bb26751d --- /dev/null +++ b/marked/Rel-11/23_series/23271/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bb45a8680459abebf10aab20de1aab22d904482fe84dd70e4bb85a2f96519d7a +size 65473 diff --git a/marked/Rel-11/23_series/23271/9b9262a549828579ab904148450734f6_img.jpg b/marked/Rel-11/23_series/23271/9b9262a549828579ab904148450734f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf0dad17f73f3a54d4e3e58e2723c510d87e86fe --- /dev/null +++ b/marked/Rel-11/23_series/23271/9b9262a549828579ab904148450734f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5ecb4aadf65a4688f4218f3d5344fefbc68e1caf7fca0a8319fb63f0c67c9ca +size 122953 diff --git a/marked/Rel-11/23_series/23271/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg b/marked/Rel-11/23_series/23271/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70e8a45b78b0837068b4867b42c0f06601332abe --- /dev/null +++ b/marked/Rel-11/23_series/23271/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f088ec71275c0d2e022ba4440ec7a97632292b645b1f70ed1252af9cf5af99d2 +size 30710 diff --git a/marked/Rel-11/23_series/23271/a02b188a5fd52c99f84255322873bf29_img.jpg b/marked/Rel-11/23_series/23271/a02b188a5fd52c99f84255322873bf29_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47d1e18b608bd90cc36af825f1398fb594e6e1e4 --- /dev/null +++ b/marked/Rel-11/23_series/23271/a02b188a5fd52c99f84255322873bf29_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:310a01e209e65e3f0cfba067228b094d542d8afd0eb0267412d35521625b237b +size 89975 diff --git a/marked/Rel-11/23_series/23271/a5404b7275b06497eecf9b5883604753_img.jpg b/marked/Rel-11/23_series/23271/a5404b7275b06497eecf9b5883604753_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10e907f948014e88df46119eb30f04cac59c1423 --- /dev/null +++ b/marked/Rel-11/23_series/23271/a5404b7275b06497eecf9b5883604753_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33b9465f5f7c3fef390fd25d9e6d8d55dae8cd3f5e6637040efc9eb59f0b2edf +size 115448 diff --git a/marked/Rel-11/23_series/23271/a963ca41bde1669b18a4b783616f228b_img.jpg b/marked/Rel-11/23_series/23271/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4b4103d2d82bec4ef52dcc88d75de1fc1a08e8f --- /dev/null +++ b/marked/Rel-11/23_series/23271/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b266c09f933f69028c6d92b33edcc3e251b6658da1818e97ba857b41ea5cac3f +size 100068 diff --git a/marked/Rel-11/23_series/23271/a9fa8656fd01e4e407bc91dba6ac0ad5_img.jpg b/marked/Rel-11/23_series/23271/a9fa8656fd01e4e407bc91dba6ac0ad5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..451c93f0c56a8055e7ca1b76c19545d33ef0b934 --- /dev/null +++ b/marked/Rel-11/23_series/23271/a9fa8656fd01e4e407bc91dba6ac0ad5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d52227a2f2ebc8116964480088c49e98387ea6cc1c672589712d27ff4c3cde01 +size 15477 diff --git a/marked/Rel-11/23_series/23271/b1e7bb95fa1587d870de03df02477df4_img.jpg b/marked/Rel-11/23_series/23271/b1e7bb95fa1587d870de03df02477df4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2d6eaf01bedc153fbd38cfc89e44f63b2405cfa --- /dev/null +++ b/marked/Rel-11/23_series/23271/b1e7bb95fa1587d870de03df02477df4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c59cfb7f2c0e016136f8a6294ff7e74100169d577f99677c7ab418b1aa3d67fd +size 73162 diff --git a/marked/Rel-11/23_series/23271/b2b3b6b051e9108f340d1789b1296667_img.jpg b/marked/Rel-11/23_series/23271/b2b3b6b051e9108f340d1789b1296667_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08a0436cecd2ca70924d238420d8d2e991c24785 --- /dev/null +++ b/marked/Rel-11/23_series/23271/b2b3b6b051e9108f340d1789b1296667_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bf5bcb072d7304a0b6dcdec1c24ac9bef43cf2d203c8a6868ffdb7d89a51853 +size 66858 diff --git a/marked/Rel-11/23_series/23271/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-11/23_series/23271/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1b06af004d1a601540e592ffa7c8accfbac505a --- /dev/null +++ b/marked/Rel-11/23_series/23271/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c93740595a0d5df5561ee81f17a7aa882c9f973146cab313878070e489346f9 +size 64263 diff --git a/marked/Rel-11/23_series/23271/b5987d63203a5fa601921039922ac520_img.jpg b/marked/Rel-11/23_series/23271/b5987d63203a5fa601921039922ac520_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa968a2e7604f6f69f7116310ebc24483ba1d432 --- /dev/null +++ b/marked/Rel-11/23_series/23271/b5987d63203a5fa601921039922ac520_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d839e498c24a95d68def7899fa042871c1294fd9ee5704e06cbe3057b5add747 +size 18236 diff --git a/marked/Rel-11/23_series/23271/b8efedb73292a798b3f2050f9335cae6_img.jpg b/marked/Rel-11/23_series/23271/b8efedb73292a798b3f2050f9335cae6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e285502e787d0d796b4e14041e148d6f7a0692ce --- /dev/null +++ b/marked/Rel-11/23_series/23271/b8efedb73292a798b3f2050f9335cae6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca1881811296cb63d0b1792aa3a2de74c7f7f4b57b03c342ba3e45e7e5563ece +size 43577 diff --git a/marked/Rel-11/23_series/23271/c0ca823603794512478906b302176bca_img.jpg b/marked/Rel-11/23_series/23271/c0ca823603794512478906b302176bca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76fb1030badc0d14c070e8afe82771e4aff38277 --- /dev/null +++ b/marked/Rel-11/23_series/23271/c0ca823603794512478906b302176bca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b99ab84b93b8f654a018676aa0801617040ed7c90b1f36a3188fc639c8af6641 +size 50333 diff --git a/marked/Rel-11/23_series/23271/c15cb6383bc35906e6b3c7c3aac621ed_img.jpg b/marked/Rel-11/23_series/23271/c15cb6383bc35906e6b3c7c3aac621ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ef0950b0c74b9f8ef49c49bb5ae8deaa5bb01f3 --- /dev/null +++ b/marked/Rel-11/23_series/23271/c15cb6383bc35906e6b3c7c3aac621ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9e6c8c266bb4fb0b888285579ce51bccaac147d3cf063bd08abacee397f3af8 +size 73544 diff --git a/marked/Rel-11/23_series/23271/c1b762c358fd423d6686563b3fde7750_img.jpg b/marked/Rel-11/23_series/23271/c1b762c358fd423d6686563b3fde7750_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af1410f7c1483bfb1c4778e625db99b97cce1702 --- /dev/null +++ b/marked/Rel-11/23_series/23271/c1b762c358fd423d6686563b3fde7750_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:376fda33151a11f7816269953e8080d56bec65a189c57518f6913571d5a6e7cf +size 103108 diff --git a/marked/Rel-11/23_series/23271/c2f36c545b190860d04e1d84e58d22cc_img.jpg b/marked/Rel-11/23_series/23271/c2f36c545b190860d04e1d84e58d22cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24652ed710ad15a337f5153d276cf8df996af30b --- /dev/null +++ b/marked/Rel-11/23_series/23271/c2f36c545b190860d04e1d84e58d22cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7117ddc601b6fd42a6a10285371dff8610a5698ed367950b6414cf423db280f +size 123705 diff --git a/marked/Rel-11/23_series/23271/ca1fca41d037482ce500c69cf727b8aa_img.jpg b/marked/Rel-11/23_series/23271/ca1fca41d037482ce500c69cf727b8aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce9c38ca068776c5271c8dd8ba26d65981d89def --- /dev/null +++ b/marked/Rel-11/23_series/23271/ca1fca41d037482ce500c69cf727b8aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea0f7a655836887a5c52838f35ffc9c12811e1570651332c78f1a4bfc5f2df3b +size 49042 diff --git a/marked/Rel-11/23_series/23271/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg b/marked/Rel-11/23_series/23271/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5297ee0c289bdf71f717a9a297df61da962e789 --- /dev/null +++ b/marked/Rel-11/23_series/23271/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be0b4d44d44b4896205f76b5233f0543dedb5a580b0070dcc64648fd3e272d3e +size 94957 diff --git a/marked/Rel-11/23_series/23271/dbbc0baac7341cda76cc4f8355dce23f_img.jpg b/marked/Rel-11/23_series/23271/dbbc0baac7341cda76cc4f8355dce23f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1586bdf219dc7ab14c8f7feb445fe82d7ea6852 --- /dev/null +++ b/marked/Rel-11/23_series/23271/dbbc0baac7341cda76cc4f8355dce23f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74715a665864b9fde135c7cb2905e75dfbf29a8124895c29ce2a0d422d9a4184 +size 85273 diff --git a/marked/Rel-11/23_series/23271/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-11/23_series/23271/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bba2e4f07337ee25f5fce6a7a9991f9d92fccba --- /dev/null +++ b/marked/Rel-11/23_series/23271/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:442706846adab018678460122f78d048308a6ab4c84c63e68377d47be8881de7 +size 76031 diff --git a/marked/Rel-11/23_series/23271/e1ce114c43dcefce51eadcd12f2da6d2_img.jpg b/marked/Rel-11/23_series/23271/e1ce114c43dcefce51eadcd12f2da6d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f802bb89ee779342ec0808a0467627b0468ac32a --- /dev/null +++ b/marked/Rel-11/23_series/23271/e1ce114c43dcefce51eadcd12f2da6d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c12b55b3640186ee9074a424889fa27eaff43dca6c5d07627df0b43ee4231ca +size 71346 diff --git a/marked/Rel-11/23_series/23271/e20792fef9de6560b2d6c5441da7614a_img.jpg b/marked/Rel-11/23_series/23271/e20792fef9de6560b2d6c5441da7614a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..277284fdb02136d3db6d9bbf252c454604cd1330 --- /dev/null +++ b/marked/Rel-11/23_series/23271/e20792fef9de6560b2d6c5441da7614a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38b6880799d21ee7436e41ab0c28c5d0d5ecb0872d3c87d85bf7a0cec8f38eea +size 50811 diff --git a/marked/Rel-11/23_series/23271/e5ded42f8e352da02ee86cb55550c45d_img.jpg b/marked/Rel-11/23_series/23271/e5ded42f8e352da02ee86cb55550c45d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..344ff01721e274a9174cd144494ad95f13296500 --- /dev/null +++ b/marked/Rel-11/23_series/23271/e5ded42f8e352da02ee86cb55550c45d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3eb3baf7781d802b23a46259810ea24c3004a12907eea15fdf88c2609d85107 +size 58991 diff --git a/marked/Rel-11/23_series/23271/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-11/23_series/23271/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e7c27d5f73c571972a7c256696774a0c772a5ef --- /dev/null +++ b/marked/Rel-11/23_series/23271/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:111eda969ca2cc3ed0dab0c1df755166547033ab5681dee9b845ee4ed518c931 +size 25568 diff --git a/marked/Rel-11/23_series/23271/ef45b00396c293be0b18d32b97118bf4_img.jpg b/marked/Rel-11/23_series/23271/ef45b00396c293be0b18d32b97118bf4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6de4ecd336200182ef43f7429f16ff29b133e32c --- /dev/null +++ b/marked/Rel-11/23_series/23271/ef45b00396c293be0b18d32b97118bf4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d849fd8f6e5c065e384fd3806da8bfadc5ccb484560974c80009870668f560b9 +size 103949 diff --git a/marked/Rel-11/23_series/23271/efb282bed9f06eef1987a14fb27bc599_img.jpg b/marked/Rel-11/23_series/23271/efb282bed9f06eef1987a14fb27bc599_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31f7726f0e08ccc64652e6ee1a99ac42b7a5eca8 --- /dev/null +++ b/marked/Rel-11/23_series/23271/efb282bed9f06eef1987a14fb27bc599_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95a3b626a553ad8233d5020ce580aeb81a29d9117373f095bc7f71e24145d744 +size 117001 diff --git a/marked/Rel-11/23_series/23271/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg b/marked/Rel-11/23_series/23271/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4d720d252eef37096702b4ac0e42ff22b0b7aa3 --- /dev/null +++ b/marked/Rel-11/23_series/23271/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:505b93e8adaf6e71ba3d25c14d78b8231a4c50523f2dd952a5e063d6deaddbac +size 109292 diff --git a/marked/Rel-11/23_series/23271/fb73a07d61dc5c47709b9802b894d716_img.jpg b/marked/Rel-11/23_series/23271/fb73a07d61dc5c47709b9802b894d716_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d28f6c32ded21923ab8378e3b6b33c66fcd21cfe --- /dev/null +++ b/marked/Rel-11/23_series/23271/fb73a07d61dc5c47709b9802b894d716_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a5cae64b3cbc11bb84fdae02562b177ef3c04898e29128129652851c2a91f6b +size 43299 diff --git a/marked/Rel-11/23_series/23271/raw.md b/marked/Rel-11/23_series/23271/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..04b104e0acab99c84d5757d7cf9e3eebf1d8c32c --- /dev/null +++ b/marked/Rel-11/23_series/23271/raw.md @@ -0,0 +1,5360 @@ + + + + +**Error:** + +**2** + +**Error: Reference source not** + +# 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..... | 19 | +| 4.1 Assumptions..... | 19 | +| 4.2 Location Services Categories..... | 20 | +| 4.3 Positioning methods..... | 20 | +| 4.3.1 Standard LCS Methods in UTRAN..... | 20 | +| 4.3.2 Standard LCS Methods in GERAN..... | 20 | +| 4.3.3 Standard LCS Methods in E-UTRAN..... | 21 | +| 4.4 Types of Location Request..... | 21 | +| 4.4.1 Immediate Location Request..... | 21 | +| 4.4.2 Deferred Location Request..... | 21 | +| 4.4.2.1 Types of event..... | 21 | +| 4.5 Concurrent Location Requests..... | 22 | +| 5 General LCS architecture..... | 22 | +| 5.1 LCS access interfaces..... | 22 | +| 5.2 LCS Functional diagram, high level functions..... | 23 | +| 5.3 LCS Client functional group..... | 24 | +| 5.3.1 External Location Client Function (LCF)..... | 24 | +| 5.4 LCS Server functional group..... | 24 | +| 5.4.1 Client handling component..... | 24 | +| 5.4.1.1 Location Client Control Function (LCCF)..... | 24 | +| 5.4.1.2 Location Client Authorization Function (LCAF)..... | 25 | +| 5.4.1.2.1 Access Subfunction..... | 25 | +| 5.4.1.2.2 Subscription Subfunction..... | 25 | +| 5.4.1.3 Location Client Co-ordinate Transformation Function (LCCTF)..... | 25 | +| 5.4.1.4 Location Client Zone Transformation Function (LCZTF)..... | 26 | +| 5.4.2 System handling component..... | 26 | +| 5.4.2.1 Location System Control Function(LSCF)..... | 26 | +| 5.4.2.2 Location System Billing Function (LSBF)..... | 26 | +| 5.4.2.3 Location System Operations Function (LSOF)..... | 26 | +| 5.4.2.4 Location System Broadcast Function (LSBcF)..... | 26 | +| 5.4.2.5 Location System Co-ordinate Transformation Function (LSCTF)..... | 26 | +| 5.4.2.6 Location IMS – Interworking Function (LIMS-IWF)..... | 26 | +| 5.4.3 Subscriber handling Component..... | 26 | +| 5.4.3.1 Location Subscriber Authorization Function (LSAF)..... | 26 | +| 5.4.3.2 Location Subscriber Translation Function (LSTF)..... | 27 | +| 5.4.3.3 Location Subscriber Privacy Function (LSPF)..... | 27 | +| 5.4.4 Positioning components..... | 27 | +| 5.5 Information Flows between Client and Server..... | 27 | +| 5.5.1 Location Service Request..... | 27 | +| 5.5.2 Location Service Response..... | 28 | +| 5.6 Information Flows between LCS Servers..... | 29 | +| 5.6.1 Location Service Request..... | 29 | +| 5.6.2 Location Service Response..... | 30 | +| 6 LCS Architecture..... | 31 | +| 6.1 Schematic functional description of LCS operations..... | 34 | +| 6.2 Allocation of LCS functions to network elements..... | 34 | +| 6.3 Functional description of LCS per network element..... | 38 | +| 6.3.1 Access Network..... | 38 | + +| | | | +|---------|------------------------------------------------------------------------------------------|----| +| 6.3.2 | LCS Clients, LCS applications and Requestors..... | 39 | +| 6.3.3 | Gateway Mobile Location Centre, GMLC..... | 39 | +| 6.3.3A | Location Retrieval Function, LRF..... | 39 | +| 6.3.4 | LCS support in the UE..... | 40 | +| 6.3.5 | MSC/VLR..... | 40 | +| 6.3.6 | MSC Server..... | 40 | +| 6.3.7 | SGSN..... | 40 | +| 6.3.8 | Home Location Register, HLR..... | 41 | +| 6.3.9 | HSS..... | 41 | +| 6.3.10 | gsmSCF..... | 41 | +| 6.3.11 | Privacy Profile Register, PPR..... | 41 | +| 6.3.12 | Pseudonym Mediation Device, PMD..... | 41 | +| 6.3.13 | Mobility Management Entity, MME..... | 41 | +| 6.3.14 | Evolved Serving Mobile Location Centre, E-SMLC..... | 41 | +| 6.4 | Addressing the target UE for LCS purposes..... | 42 | +| 6.4.1 | Verinymns for the target UE..... | 42 | +| 6.4.2 | Pseudonyms for the target UE..... | 42 | +| 6.4.3 | Non-dialable callback numbers..... | 42 | +| 6.5 | Quality of Service Information..... | 42 | +| 6.5.1 | LCS QoS Class..... | 42 | +| 6.5.1.1 | Best Effort Class..... | 43 | +| 6.5.1.2 | Assured Class..... | 43 | +| 7 | Signalling and Interfaces..... | 43 | +| 7.1 | LCS signalling between Access and Core Networks for GERAN and UTRAN access networks..... | 43 | +| 7.1.1 | Core network Location Request..... | 43 | +| 7.1.2 | Location Report..... | 43 | +| 7.1a | LCS signalling between Access and Core Networks for E-UTRAN access networks..... | 44 | +| 7.1a.1 | Core network Measurement Request..... | 44 | +| 7.1a.2 | Location Measurement Report..... | 44 | +| 7.2 | Um, Uu and Uu-LTE Interfaces..... | 44 | +| 7.3 | MAP Interfaces..... | 44 | +| 7.4 | Lpp interface..... | 45 | +| 7.4.1 | LCS Authorisation Request..... | 45 | +| 7.4.2 | LCS Authorisation Response..... | 46 | +| 7.4.3 | LCS Privacy Profile Update notification..... | 47 | +| 7.4.4 | LCS Privacy Profile Update notification ack..... | 47 | +| 7.5 | Lid interface..... | 47 | +| 7.5.1 | LCS Identity Request..... | 47 | +| 7.5.2 | LCS Identity Response..... | 47 | +| 7.6 | IMS related Interfaces..... | 47 | +| 7.6.1 | Dh Interface..... | 47 | +| 7.6.2 | Sh Interface..... | 47 | +| 7.6.3 | Ml Interface..... | 47 | +| 7.7 | SLg Interface..... | 47 | +| 7.8 | SLs Interface..... | 48 | +| 7.9 | SLh Interface..... | 48 | +| 7.10 | SLm Interface..... | 48 | +| 8 | General network location procedures..... | 48 | +| 8.1 | State description for GMLC..... | 48 | +| 8.1.1 | GMLC states..... | 48 | +| 8.1.1.1 | NULL State..... | 48 | +| 8.1.1.2 | INTERROGATION State..... | 48 | +| 8.1.1.3 | LOCATION State..... | 48 | +| 8.1.2 | State functionality..... | 49 | +| 8.1.2.1 | State Transitions..... | 49 | +| 8.1.2.2 | INTERROGATION Timer Function..... | 49 | +| 8.1.2.3 | LOCATION Timer Function..... | 50 | +| 8.2 | State description for VMSC and MSC Server..... | 50 | +| 8.2.1 | VMSC and MSC Server States..... | 50 | +| 8.2.1.1 | LCS IDLE State..... | 50 | + +| | | | +|-----------|---------------------------------------------------------------------------------------------|----| +| 8.2.1.2 | LOCATION State..... | 50 | +| 8.2.2 | State Functionality..... | 50 | +| 8.2.2.1 | State Transitions..... | 50 | +| 8.2.2.2 | LOCATION Timer Function..... | 51 | +| 8.3 | LCS State description for SGSN..... | 51 | +| 8.3.1 | SGSN States..... | 51 | +| 8.3.1.1 | LCS IDLE State..... | 51 | +| 8.3.1.2 | LOCATION State..... | 51 | +| 8.3.2 | State Functionality..... | 51 | +| 8.3.2.1 | State Transitions..... | 51 | +| 8.3.2.2 | LOCATION Timer Function..... | 52 | +| 8.4 | Signalling connection for the Iu interface..... | 52 | +| 8.5 | Signalling connection for the A-interface..... | 52 | +| 8.6 | Gb interface mapping of target UE..... | 52 | +| 8.7 | LCS State description for MME..... | 52 | +| 8.7.1 | MME States..... | 52 | +| 8.7.1.1 | LCS IDLE State..... | 52 | +| 8.7.1.2 | LOCATION State..... | 52 | +| 8.7.2 | State Functionality..... | 53 | +| 8.7.2.1 | State Transitions..... | 53 | +| 8.7.2.2 | LOCATION Timer Function..... | 53 | +| 8.8 | Signalling connection for the S1 interface..... | 53 | +| 9 | General Network Positioning Procedures..... | 53 | +| 9.1 | Mobile Terminating Location Request..... | 54 | +| 9.1.1 | Common MT-LR procedure in PS and CS domain..... | 55 | +| 9.1.1A | Common MT-LR procedure in PS and CS domain for Emergency MT-LR..... | 59 | +| 9.1.1.1 | LCS Authorisation request..... | 61 | +| 9.1.1.2 | LCS Privacy Profile Update..... | 62 | +| 9.1.1.3 | LCS identity request..... | 62 | +| 9.1.2 | Circuit Switched Mobile Terminating Location Request (CS-MT-LR)..... | 63 | +| 9.1.2.1 | Location Preparation Procedure..... | 64 | +| 9.1.2.2 | Positioning Measurement Establishment Procedure..... | 65 | +| 9.1.2.3 | Location Calculation and Release Procedure..... | 65 | +| 9.1.3 | CS-MT-LR without HLR Query..... | 65 | +| 9.1.4 | CS-MT-LR and PS-MT-LR for a previously obtained location estimate..... | 66 | +| 9.1.4.1 | Initial Location..... | 67 | +| 9.1.4.2 | Current Location..... | 67 | +| 9.1.4.3 | Last known Location..... | 67 | +| 9.1.4.4 | Security and Privacy..... | 67 | +| 9.1.4.5 | Failing to locate the target UE..... | 67 | +| 9.1.4.5.1 | Target UE is "Not Reachable"..... | 67 | +| 9.1.4.5.2 | Target UE is "Detached"..... | 68 | +| 9.1.4.5.3 | Target UE is Reachable but Positioning Fails..... | 68 | +| 9.1.4.5.4 | MSC Server or SGSN Target UE is "Purged"..... | 68 | +| 9.1.5 | Network Induced Location Request (NI-LR)..... | 69 | +| 9.1.5.1 | Location Preparation Procedure..... | 69 | +| 9.1.5.2 | Positioning Measurement Establishment Procedure..... | 70 | +| 9.1.5.3 | Location Calculation and Release Procedure..... | 70 | +| 9.1.5A | NI-LR using Location Based Routing – applicable to North American Emergency Calls only..... | 71 | +| 9.1.5A.1 | Location Preparation Procedure..... | 72 | +| 9.1.5A.2 | Positioning Measurement Establishment Procedure..... | 72 | +| 9.1.5A.3 | Location Calculation and Release Procedure..... | 72 | +| 9.1.5A.4 | Location Preparation Procedure..... | 72 | +| 9.1.5A.5 | Positioning Measurement Establishment Procedure..... | 73 | +| 9.1.5A.6 | Location Calculation and Release Procedure..... | 73 | +| 9.1.6 | Packet Switched Mobile Terminating Location Request (PS-MT-LR)..... | 73 | +| 9.1.6.1 | Location Preparation Procedure..... | 74 | +| 9.1.6.2 | Positioning Measurement Establishment Procedure..... | 75 | +| 9.1.6.3 | Location Calculation and Release Procedure..... | 76 | +| 9.1.6A | PS-MT-LR without HLR Query..... | 76 | +| 9.1.7 | Packet Switched Network Induced Location Request (PS-NI-LR)..... | 77 | + +| | | | +|----------|-----------------------------------------------------------------------------------------------|-----| +| 9.1.7.1 | Positioning Measurement Establishment Procedure..... | 78 | +| 9.1.7.2 | Location Calculation and Release Procedure..... | 78 | +| 9.1.8 | Mobile Terminating Deferred Location Request – UE available event..... | 78 | +| 9.1.8.1 | Deferred Location Request Procedure..... | 79 | +| 9.1.8.2 | Location Report Procedure..... | 80 | +| 9.1.8.3 | Combined Periodical/Deferred Mobile Terminating Location Request with UE available event..... | 81 | +| 9.1.8.4 | Cancellation of a Deferred Location Request – UE available event..... | 83 | +| 9.1.9 | Deferred Location Request Procedure for the change of area event..... | 84 | +| 9.1.9.1 | Cancellation of a Deferred Location Request – Change of Area event..... | 87 | +| 9.1.10 | Circuit Switched Post Positioning Notification and Verification Procedure..... | 88 | +| 9.1.11 | Packet Switched Post Positioning Notification and Verification Procedure..... | 91 | +| 9.1.12 | Deferred Location Request Procedure for the Periodic Location Event..... | 92 | +| 9.1.12.1 | Instigation of an MT-LR Request for Periodic Location..... | 92 | +| 9.1.12.2 | Reporting of Periodic Location..... | 94 | +| 9.1.12.3 | LCS Client cancellation of a Deferred Location Request – Periodic Location Event..... | 97 | +| 9.1.12.4 | UE cancellation of a Deferred Location Request – Periodic Location Event..... | 99 | +| 9.1.13 | IW-MT-LR Procedure..... | 101 | +| 9.1.14 | IW-MT-LR Procedure without HLR/HSS or AAA Query..... | 102 | +| 9.1.15 | EPC Mobile Terminating Location Request (EPC-MT-LR)..... | 104 | +| 9.1.15.1 | Location Preparation Procedure..... | 104 | +| 9.1.15.2 | Positioning Measurement Establishment Procedure..... | 105 | +| 9.1.15.3 | Location Calculation and Release Procedure..... | 105 | +| 9.1.16 | EPC-MT-LR without HLR Query..... | 106 | +| 9.1.17 | EPC Network Induced Location Request (EPC-NI-LR)..... | 107 | +| 9.1.17.1 | Positioning Measurement Establishment Procedure..... | 107 | +| 9.1.17.2 | Location Calculation and Release Procedure..... | 108 | +| 9.1.18 | EPC Post Positioning Notification and Verification Procedure..... | 108 | +| 9.2 | Mobile Originating Location Request..... | 110 | +| 9.2.1 | Mobile Originating Location Request, Circuit Switched (CS-MO-LR)..... | 110 | +| 9.2.1.1 | Location Preparation Procedure..... | 111 | +| 9.2.1.2 | Positioning Measurement Establishment Procedure..... | 112 | +| 9.2.1.3 | Location Calculation and Release Procedure..... | 112 | +| 9.2.2 | Mobile Originating Location Request, Packet Switched (PS-MO-LR)..... | 114 | +| 9.2.2.1 | Location Preparation Procedure..... | 114 | +| 9.2.2.2 | Positioning Measurement Establishment Procedure..... | 115 | +| 9.2.2.3 | Location Calculation and Release Procedure..... | 115 | +| 9.2.3 | MO-LR Request for Periodic Location Transfer to a Third Party..... | 116 | +| 9.2.4 | MO-LR Request for Periodic Self Location..... | 118 | +| 9.2.5 | WLAN UE Originated Procedure in I-WLAN..... | 120 | +| 9.2.6 | Mobile Originating Location Request, EPC (EPC-MO-LR)..... | 121 | +| 9.2.6.1 | Location Preparation Procedure..... | 121 | +| 9.2.6.2 | Positioning Measurement Establishment Procedure..... | 122 | +| 9.2.6.3 | Location Calculation and Release Procedure..... | 122 | +| 9.3 | LCS signalling procedures specified in UTRAN and GERAN Stage 2..... | 123 | +| 9.3a | LCS signalling procedures applicable to E-UTRAN..... | 123 | +| 9.3a.1 | UE Assisted and UE Based Positioning and Assistance Delivery..... | 123 | +| 9.3a.2 | Network Assisted and Network Based Positioning Procedure..... | 124 | +| 9.3a.3 | Obtaining Non-UE Associated Network Assistance Data..... | 125 | +| 9.4 | Exception Procedures..... | 126 | +| 9.4.1 | Procedures in the VMSC /MSC server..... | 127 | +| 9.4.2 | Void..... | 127 | +| 9.4.3 | Procedures in the SGSN..... | 127 | +| 9.4.3a | Procedures in the MME..... | 128 | +| 9.4.4 | Void..... | 129 | +| 9.4.5 | Handover handling..... | 129 | +| 9.4.5.1 | VMSC /MSC server procedure for Inter-VMSC /MSC server Handover..... | 129 | +| 9.4.5.2 | Handling of an ongoing handover while a request for positioning arrives..... | 129 | +| 9.4.5.3 | Handover handling in Iu mode..... | 129 | +| 9.4.5.4 | Handover of an IMS Emergency Call with EPS/GPRS Access..... | 129 | +| 9.5 | Privacy..... | 134 | +| 9.5.1 | Privacy Override Indicator (POI)..... | 134 | + +| | | | +|-----------|------------------------------------------------------------------------------|-----| +| 9.5.2 | Privacy Procedures..... | 134 | +| 9.5.3 | UE Privacy Options..... | 135 | +| 9.5.3.1 | Universal class..... | 135 | +| 9.5.3.2 | Call/Session related class..... | 135 | +| 9.5.3.2.1 | Call/session-related class in the CS-domain..... | 136 | +| 9.5.3.2.2 | Call/session-related class in the PS-domain..... | 136 | +| 9.5.3.2.3 | Call/session-related class when LCS client not in SLPP..... | 137 | +| 9.5.3.3 | Call/Session-unrelated class..... | 137 | +| 9.5.3.3.1 | Call/session-unrelated class when LCS client identities match..... | 137 | +| 9.5.3.3.2 | Call/session-unrelated class when LCS client identities do not match..... | 138 | +| 9.5.3.4 | PLMN operator class..... | 138 | +| 9.5.3.5 | Service type checking..... | 138 | +| 9.5.3.6 | Matching of LCS client identities..... | 138 | +| 9.5.4 | Indicator of privacy check related action..... | 139 | +| 9.6 | Mobile Originating Location..... | 140 | +| 9.7 | CM Procedures..... | 140 | +| 9.7.1 | Location request for a mobile in idle-mode..... | 140 | +| 9.7.2 | Location request for a mobile in dedicated-mode..... | 140 | +| 9.8 | Interworking with the IMS..... | 140 | +| 9.8.1 | Standard Location Request using a SIP-URI..... | 140 | +| 9.8.2 | Standard Location Request using a TEL-URL..... | 142 | +| 9.8.3 | Mobile Originated Location Requests in the IMS..... | 142 | +| 9.8.4 | IMS Emergency Location Procedure..... | 142 | +| 10 | Information storage..... | 142 | +| 10.1 | HLR and HSS..... | 142 | +| 10.1.1 | LCS Data in the HLR/HSS for an UE Subscriber..... | 143 | +| 10.2 | VLR/SGSN..... | 146 | +| 10.2a | MME..... | 146 | +| 10.3 | GMMLC..... | 146 | +| 10.3.1 | LCS Data in the GMMLC for a LCS Client..... | 146 | +| 10.3.2 | LCS Data in the GMMLC/PPR for a UE Subscriber..... | 148 | +| 10.4 | Recovery and Restoration Procedures..... | 151 | +| 10.5 | Interworking between network nodes in different releases..... | 151 | +| 10.5.1 | LCS capability set..... | 151 | +| 10.5.2 | Interworking between pre Rel-4 serving node and Rel-4 or later HLR/HSS..... | 152 | +| 10.5.3 | Interworking between pre Rel-5 serving node and Rel-5 or later HLR/HSS..... | 152 | +| 10.5.4 | Interworking between pre Rel-6 network nodes and Rel-6 or later HLR/HSS..... | 152 | +| 10.5.4.1 | Rel-6 or later HLR/HSS with pre Rel-6 serving node..... | 152 | +| 10.6 | LIMS-IWF..... | 152 | +| 11 | Operational Aspects..... | 152 | +| 11.1 | Charging..... | 152 | +| 11.2 | Charging Information Collected by the Visited PLMN..... | 153 | + +| | | | +|-------------------------------|---------------------------------------------------------------------|------------| +| Annex A (normative): | Privacy Class selection rule in serving node..... | 154 | +| A.1 | Interrelation among privacy settings..... | 154 | +| A.2 | Privacy class selection rule for pre Rel-6 mechanism..... | 154 | +| A.3 | Privacy related action selection rule for Rel-6 and later..... | 155 | +| Annex B (normative): | Presence of LCS client ID Components in MT-LR..... | 157 | +| Annex C (Informative): | Pseudo external ID..... | 158 | +| Annex D (normative): | including Requestor identity to LCS client name..... | 162 | +| Annex E (Informative): | Handling of pseudonyms in location services..... | 163 | +| Annex F (Informative): | Mechanism for performing Change of Area Event Detection..... | 166 | +| F.1 | (U)SIM Application Toolkit (USAT) Based Solution..... | 166 | +| Annex G (normative): | Defined Service Types and numbering..... | 168 | +| Annex H (informative): | Change history..... | 169 | + +--- + +## 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. + +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] (void). +- [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: "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 (S1AP)". +- [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". + +--- + +## 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. + +**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. + +**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) | +| 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 | +| 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 | +| 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 | +| 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 | +| 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 | +| TEL-URL | Telephone Uniform Resource Locator | +| TMSI | Temporary Mobile Subscriber Identity | +| TOA | Time Of Arrival | +| TTTP | Transfer To Third Party | +| UDT | SCCP Unidata message | +| UE | User Equipment | +| UL | Uplink | +| UMTS | Universal Mobile Telecommunication System | +| 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 commonalities 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. + +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. + +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. + +NOTE: Deferred Location Request is not supported for E-UTRAN Access in this version of the TS. + +#### 4.4.2.1 Types of event + +- a) UE available: Any event in which the MSC/SGSN 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. 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, 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. +- c) Periodic Location: An event where a defined periodic timer expires in the UE and activates a location report or a location request. +- d) 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 showing LCS network 1 connected to LCS network 2 via Lg or Lr interface, and to LCS Clients or other networks via Le interface.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +The diagram illustrates the network architecture for LCS. It features three main entities: 'LCS network 1', 'LCS network 2', and '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 'LCS Clients or other networks' via a horizontal line labeled 'Le'. + +Diagram showing LCS network 1 connected to LCS network 2 via Lg or Lr interface, and to LCS Clients or other networks via Le interface. + +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. + +![Functional diagram of the LCS capability server showing the interaction between the LCS Client and the LCS Server components.](86b4670fc1a5a694821ee92b99c1209a_img.jpg) + +This functional 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). A 'Location Service Request' is sent from the client to the 'LCS Server'. The 'LCS Server' contains three main components: 'Subscriber handling component' (with 'LSAF -- LSPF'), 'System handling component' (with 'LMMF', 'LSCF', 'LIMS-IWF', and 'LSOF-LSBF'), and 'Client handling component' (with 'LCCF', 'LCCTF', and 'LCAF'). Arrows show the flow of information between these components and the 'Positioning component' (with 'PRCF', 'PCF', 'PSMF', and 'PRRM'). A 'Location Service Response' is sent back to the client. A note indicates 'Resources: Signalling protocols' with an arrow pointing to the positioning component. + +Functional diagram of the LCS capability server showing the interaction between the LCS Client and the LCS Server components. + +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 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 interval time between area event reports, if multiple event reports is 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; +- 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 + +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-NI, if the request is call or session related; +- Type of Event definition, i.e. UE available, change of area 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 interval time between area event reports; + - d) Start time, stop time, i.e. specifying the validity time of LCS area event request; +- 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; + - d) Reporting PLMN list; +- 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 + +In addition the information attributes of the location service request may be used also in the location service response. + +--- + +## 6 LCS Architecture + +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. To the left, three RAN types are shown: GERAN (connected via Um and Lu interfaces), UTRAN (connected via Uu and Lu interfaces), and E-UTRAN (connected via LTE-Uu and S1 interfaces). Each RAN is associated with specific core network elements: GERAN with 2G-MSC and 2G-SGSN; UTRAN with 3G-SGSN and MSC server; and E-UTRAN with MME, E-SMLC, and SLP (*Note 7). The GMLC connects to several other functional blocks: PPR (*Note 3), E-CSCF, gsmSCF (*Note 2), LRF, HSS (*Note 1), PMD (*Note 4), LIMS-IWF (*Note 5), and External LCS Client. Interfaces between these elements are labeled with codes like Lg, Lpp, MI, Lc, Le, Lid, SLg, SLs, and SLm. The External LCS Client connects to the GMLC via Le and Le interfaces, and to the gsmSCF via Proprietary and OSA API interfaces.](e05b36c0d46549e681ce6581422c66b2_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. To the left, three RAN types are shown: GERAN (connected via Um and Lu interfaces), UTRAN (connected via Uu and Lu interfaces), and E-UTRAN (connected via LTE-Uu and S1 interfaces). Each RAN is associated with specific core network elements: GERAN with 2G-MSC and 2G-SGSN; UTRAN with 3G-SGSN and MSC server; and E-UTRAN with MME, E-SMLC, and SLP (\*Note 7). The GMLC connects to several other functional blocks: PPR (\*Note 3), E-CSCF, gsmSCF (\*Note 2), LRF, HSS (\*Note 1), PMD (\*Note 4), LIMS-IWF (\*Note 5), and External LCS Client. Interfaces between these elements are labeled with codes like Lg, Lpp, MI, Lc, Le, Lid, SLg, SLs, and SLm. The External LCS Client connects to the GMLC via Le and Le interfaces, and to the gsmSCF via Proprietary and OSA API interfaces. + +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] and TS 29.198 [27, 28, 29 and 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]. + +**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. + +![Figure 6.1-1a: General arrangement of LCS for I-WLAN. This diagram shows the network architecture for location services in an I-WLAN environment. On the left, an 'Intranet / Internet' cloud is connected to a 'WLAN Access Network'. A 'WLAN UE' is connected to this network via the 'Ww' interface. The 'WLAN Access Network' connects to a '3GPP AAA Server' via the 'Wa' interface. The '3GPP AAA Server' is part of the '3GPP Home Network', which also contains 'SLF', 'HSS', 'HLR', 'E-CSCF', 'LRF', 'GMLC', 'Offline Charging System', 'OCS', 'WAG', and 'PDG'. Various interfaces are labeled: 'Dw', 'Wx', 'D'/Gr'', 'Lh/SLh', 'Lh', 'MI', 'La', 'Le', 'Wo', 'Wf', 'Wm', 'Wz', 'Wy', 'Wn', 'Wp', 'Wi', and 'Wu'. A shaded oval at the bottom of the 3GPP Home Network is labeled 'WLAN 3GPP IP Access' and contains the 'WAG' and 'PDG' components.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +Figure 6.1-1a: General arrangement of LCS for I-WLAN. This diagram shows the network architecture for location services in an I-WLAN environment. On the left, an 'Intranet / Internet' cloud is connected to a 'WLAN Access Network'. A 'WLAN UE' is connected to this network via the 'Ww' interface. The 'WLAN Access Network' connects to a '3GPP AAA Server' via the 'Wa' interface. The '3GPP AAA Server' is part of the '3GPP Home Network', which also contains 'SLF', 'HSS', 'HLR', 'E-CSCF', 'LRF', 'GMLC', 'Offline Charging System', 'OCS', 'WAG', and 'PDG'. Various interfaces are labeled: 'Dw', 'Wx', 'D'/Gr'', 'Lh/SLh', 'Lh', 'MI', 'La', 'Le', 'Wo', 'Wf', 'Wm', 'Wz', 'Wy', 'Wn', 'Wp', 'Wi', and 'Wu'. A shaded oval at the bottom of the 3GPP Home Network is labeled 'WLAN 3GPP IP Access' and contains the 'WAG' and 'PDG' components. + +- 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** + +![Figure 6.1-2: General arrangement of LCS with inter-GMLC and LIMS-IWF [Lr] interface. This diagram illustrates a more complex network architecture for location services. At the top, a 'VPMLN' (Virtual Packet Mobile Network) is shown. Below it, various radio access networks are depicted: 'GERAN' (connected to '2G-MSC' and '2G-SGSN'), 'UTRAN' (connected to '3G-SGSN' and 'MSC server'), and 'E-UTRAN' (connected to 'MME'). User Equipment ('UE') is shown connecting to these networks via interfaces like 'Um', 'Lu', 'Uu', and 'LTE-Uu'. The core network includes 'E-CSCF', 'PMD', 'OSA-LCS' (External LCS Client), 'gsmSCF', 'LRF', 'VGMLC *Note1', 'HGMLC *Note1', 'RGMLC', 'PPR', 'HSS/HLR', 'HLIMS-IWF', and 'RLIMS-IWF'. Interfaces between these elements are labeled 'A', 'Gb', 'Lu', 'Lg', 'MI', 'Lid', 'Lc', 'Le', 'Lr', 'Lh/SLh', 'S1', 'SLs', and 'SLm'. At the bottom, 'LMU *Note3', 'E-SMLC', and 'SLP *Note2' are shown with their respective interfaces.](dbbc0baac7341cda76cc4f8355dce23f_img.jpg) + +Figure 6.1-2: General arrangement of LCS with inter-GMLC and LIMS-IWF [Lr] interface. This diagram illustrates a more complex network architecture for location services. At the top, a 'VPMLN' (Virtual Packet Mobile Network) is shown. Below it, various radio access networks are depicted: 'GERAN' (connected to '2G-MSC' and '2G-SGSN'), 'UTRAN' (connected to '3G-SGSN' and 'MSC server'), and 'E-UTRAN' (connected to 'MME'). User Equipment ('UE') is shown connecting to these networks via interfaces like 'Um', 'Lu', 'Uu', and 'LTE-Uu'. The core network includes 'E-CSCF', 'PMD', 'OSA-LCS' (External LCS Client), 'gsmSCF', 'LRF', 'VGMLC \*Note1', 'HGMLC \*Note1', 'RGMLC', 'PPR', 'HSS/HLR', 'HLIMS-IWF', and 'RLIMS-IWF'. Interfaces between these elements are labeled 'A', 'Gb', 'Lu', 'Lg', 'MI', 'Lid', 'Lc', 'Le', 'Lr', 'Lh/SLh', 'S1', 'SLs', and 'SLm'. At the bottom, 'LMU \*Note3', 'E-SMLC', and 'SLP \*Note2' are shown with their respective interfaces. + +- 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]. + +**Figure 6.1-2: General arrangement of LCS with inter-GMLC and LIMS-IWF [Lr] interface** + +## 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. Client | Location Client Component | (External) Location Client Function | LCF | +| | | 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 | +| | | Location IMS – Interworking Function | LIMS-IWF | +| | Subscriber Handling component | 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 E-UTRAN, GERAN/UTRAN, and Core Network components and their interfaces.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +The diagram illustrates the Generic LCS Logical Architecture, showing the interaction between various network elements and an external LCS client. + +- E-UTRAN (Top Left):** Contains PSMF, LSOF, LSBcF, and PRRM. It connects to the Core Network via the S1 interface. The LTE-Uu interface is shown on its left. +- GERAN/UTRAN (Bottom Left):** Contains PSMF, LCF, LSCF, LSOF, LSBcF, PRCF, PCF, and PRRM. It connects to the Core Network via the A/Iu interface. The Um/Uu interface is shown on its left. +- Core Network (Right):** A large box containing several functional blocks: + - Top Block:** PRCF, LSOF, PCF, LSBcF. It connects to the S1 interface. + - SLs Interface:** A vertical interface between the top block and the next block. + - Second Block:** LSOF, LSAF, LCF, LSPF, LSBF, LSCF. It connects to the SLg interface. + - Gs Interface:** A vertical interface between the second and third blocks. + - Third Block:** LSOF, LSAF, LCF, LSPF, LSBF, LSCF. It connects to the Lg interface. + - Fourth Block:** LSAF, LSPF. It connects to the Lpp interface. + - Lid Interface:** A vertical interface between the fourth and fifth blocks. + - Fifth Block:** LSTF. It connects to the Le interface. + - Right Column:** A vertical stack of components: LSPF, Lh, LCCF, LCAF, LSOF, LSBF, LCCTF, LSAF, LSPF, LSCTF, LCZTF, LIMS-IWF (marked with \* See 1). This column connects to the Lg, Lpp, Lid, and Le interfaces. +- External LCS Client (Bottom Right):** Represented by a computer icon, connected to the Le interface. +- Interfaces:** + - LTE-Uu:** Between E-UTRAN and the network. + - S1:** Between E-UTRAN and the Core Network. + - Um/Uu:** Between GERAN/UTRAN and the network. + - A/Iu:** Between GERAN/UTRAN and the Core Network. + - SLs, Gs, Lg, Lpp, Lid, Le:** Internal interfaces within the Core Network. + +Figure 6.2: Generic LCS Logical Architecture diagram showing E-UTRAN, GERAN/UTRAN, and Core Network components and their interfaces. + +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 or SLg interface. 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 Ml 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 interface. The LCS functions of SGSN are related to charging and billing, LCS co-ordination, location request, authorization and operation of the LCS services. + +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. + +### 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. + +## 6.4 Addressing the target UE for LCS purposes + +### 6.4.1 Verinyms 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 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). + +## 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 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]. + +## 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 + +![State transition diagram for the GMLC showing three states: NULL, INTERROGATION, and LOCATION. Transitions are triggered by specific location requests or responses from the HLR/HSS.](ca1fca41d037482ce500c69cf727b8aa_img.jpg) + +``` + +stateDiagram-v2 + [*] --> NULL + NULL --> INTERROGATION : Location Request - Interrogate HLR/HSS for VGMLC/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 + +``` + +State transition diagram for the GMLC showing three states: NULL, INTERROGATION, and LOCATION. Transitions are triggered by specific location requests or responses from the HLR/HSS. + +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 the VMSC/MSC Server. It shows two states: LCS-IDLE and LOCATION. Transitions are: LCS-IDLE to LOCATION (Request Location from the RAN), LOCATION to LCS-IDLE (Receive Location results from the RAN or Timeout), and a self-loop on LOCATION (Transfer Positioning Messages).](9cbc1ebd80813fc36e499f7d70ed6881_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 VMSC/MSC Server. It shows two states: LCS-IDLE and LOCATION. Transitions are: LCS-IDLE to LOCATION (Request Location from the RAN), LOCATION to LCS-IDLE (Receive Location results from the RAN or Timeout), and a self-loop on LOCATION (Transfer Positioning Messages). + +**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'.](036c200da9b64c3eb5aae2d67bb53e1f_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', 'Receive Location results from the E-SMLC or Timeout', and 'Transfer Positioning Messages'.](92c4d3a4d29d64c167855449f1aeba2a_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', 'Receive Location results from the E-SMLC or Timeout', and 'Transfer Positioning Messages'. + +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 locations 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 chapter 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 chapter 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 routing information exchange, privacy checks, and MT-LR procedures for CS and PS domains.](195611c20b2dc7ed0fa3033392e22908_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 . + + 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->>MSC_SGSN_MME: 9. MT-LR procedures for CS and PS domain . + GMLC_V-->>GMLC_H: 10. LCS Service Response + GMLC_H->>GMLC_V: 12. LCS Service Request + GMLC_V->>MSC_SGSN_MME: 13. Post positioning notification procedure for CS and PS domain + 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 routing information exchange, privacy checks, and MT-LR procedures for CS and PS domains. + +**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 verinum for the pseudonym. In this case the R-GMLC may access to its associated PMD as described in 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 verinum (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 verinum 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 verinum 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 chapter 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 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. The H-GMLC shall forward a request for a deferred MT-LR only to an SGSN and/or VMSC/MSC server. If neither was indicated by the HLR/HSS in step 7 in the case of a deferred MT-LR (e.g. if the HLR/HSS returned the current MME but not a current SGSN or VMSVC/MSC server), the H-GMLC shall return an error to the R-GMLC. + +Also 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 chapter 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. + +**Editor's Note:** The restriction for a deferred MT-LR in the case of a current MME may be removed in a later version of this TS. + +- 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 LCS Client indicated deferred location request, GMLC shall indicate this together with applicable event type (e.g. UE available) in the requested PS/CS-MT-LR, see 9.1.8. + +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 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 shows a request from Client to GMLC (Requesting), which then queries HLR/HSS for routing info. HLR/HSS returns routing info, which GMLC (Requesting) passes to GMLC (Visited). GMLC (Visited) initiates common MT-LR procedures with MSC/SGSN/MME, RAN, and UE. Finally, a response is returned from GMLC (Visited) back to Client.](9b1ec0090070bdf52ea28763b8d52477_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 + + Note right of GMLC_V: Error: Reference source not + 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 + GMLC_V->>MSC_SGSN_MME: 5. Common MT-LR procedures in CS and PS domain. + 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 shows a request from Client to GMLC (Requesting), which then queries HLR/HSS for routing info. HLR/HSS returns routing info, which GMLC (Requesting) passes to GMLC (Visited). GMLC (Visited) initiates common MT-LR procedures with MSC/SGSN/MME, RAN, and UE. Finally, a response is returned from GMLC (Visited) back to 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. 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'.](b5987d63203a5fa601921039922ac520_img.jpg) + +``` +sequenceDiagram + participant GMLC + participant PPR + Note right of GMLC: 1. LCS Authorisation Request + GMLC->>PPR: 1. LCS Authorisation Request + Note left of PPR: 2. LCS Authorisation Response + 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 for Figure 9.1C: PPR notification to GMLC about LCS privacy profile change. The diagram shows two lifelines: GMLC and PPR. A solid arrow labeled '1. LCS privacy profile update notification' points from PPR to GMLC. A dashed arrow labeled '2. LCS profile update notification ack.' points from GMLC to PPR.](8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg) + +``` +sequenceDiagram + participant GMLC + participant PPR + 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. +``` + +Sequence diagram for Figure 9.1C: PPR notification to GMLC about LCS privacy profile change. The diagram shows two lifelines: GMLC and PPR. A solid arrow labeled '1. LCS privacy profile update notification' points from PPR to GMLC. A dashed arrow labeled '2. LCS profile update notification ack.' points from GMLC to PPR. + +**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 verinum of the UE from the PMD, see figure 9.1D. + +![Sequence diagram for Figure 9.1D: LCS identity request. The diagram shows two lifelines: GMLC and PMD. A solid arrow labeled '1. Identity Request' points from GMLC to PMD. A dashed arrow labeled '2. Identity Response' points from PMD to GMLC.](a9fa8656fd01e4e407bc91dba6ac0ad5_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 +``` + +Sequence diagram for Figure 9.1D: LCS identity request. The diagram shows two lifelines: GMLC and PMD. A solid arrow labeled '1. Identity Request' points from GMLC to PMD. A dashed arrow labeled '2. Identity Response' points from PMD to GMLC. + +**Figure 9.1D: LCS identity request** + +- 1) The GMLC sends the pseudonym to its associated PMD and requests the corresponding verinum 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 CS-MT-LR network positioning](cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg) + +``` +sequenceDiagram + participant Client + participant GMMLC + 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 + GMMLC->>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->>GMMLC: 9. Provide Subscriber Location ack. + Note over Client, HLR/HSS: 10. Common MT-LR procedure in CS and PS domain +``` + +The sequence diagram illustrates the network positioning process for a CS-MT-LR. It involves six lifelines: Client, GMMLC, HLR/HSS, VMSC/MSC SERVER, RAN, and UE. The process begins with a 'Common MT-LR procedure in CS and PS domain' involving the Client, GMMLC, and HLR/HSS. The GMMLC sends a 'Provide Subscriber Location' message to the VMSC/MSC SERVER. The VMSC/MSC SERVER then performs 'UE Paging, Authentication, Ciphering' and sends an 'LCS Location Notification Invoke' to the UE. The UE responds with an 'LCS Location Notification Return Result'. The VMSC/MSC SERVER sends a 'Location Request' to the RAN. The RAN and UE exchange 'Messages for individual positioning methods'. The RAN sends a 'Location Report' to the VMSC/MSC SERVER. The VMSC/MSC SERVER sends a 'Provide Subscriber Location ack.' to the GMMLC. Finally, another 'Common MT-LR procedure in CS and PS domain' is shown involving the Client, GMMLC, and HLR/HSS. + +Sequence diagram for CS-MT-LR network positioning + +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 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 chapter 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 chapter 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 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. The Client sends an LCS Service Request to the GMLC. The GMLC sends a Provide Subscriber Location request to the VMSC/MSC SERVER. The VMSC/MSC SERVER sends a Location Request to the RAN. The RAN sends Messages for individual positioning methods to the UE. The UE sends a Location Report back to the RAN. The RAN sends a Provide Subscriber Location ack to the VMSC/MSC SERVER. The VMSC/MSC SERVER sends an LCS Service Response back to the GMLC, which then sends it to the Client.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC + participant HLR/HSS + participant VMSC/MSC SERVER + participant RAN + participant UE + + Note right of RAN: Error: Reference source not + Client->>GMLC: 1. LCS Service Request + GMLC->>VMSC/MSC SERVER: 2. Provide Subscriber Location + VMSC/MSC SERVER->>RAN: 3. Location Request + RAN->>UE: 4. Messages for individual positioning methods + UE-->>RAN: 5. Location Report + RAN->>VMSC/MSC SERVER: 6. Provide Subscriber Location ack. + VMSC/MSC SERVER->>GMLC: 7. LCS Service Response + GMLC->>Client: + +``` + +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. The Client sends an LCS Service Request to the GMLC. The GMLC sends a Provide Subscriber Location request to the VMSC/MSC SERVER. The VMSC/MSC SERVER sends a Location Request to the RAN. The RAN sends Messages for individual positioning methods to the UE. The UE sends a Location Report back to the RAN. The RAN sends a Provide Subscriber Location ack to the VMSC/MSC SERVER. The VMSC/MSC SERVER sends an LCS Service Response back to the GMLC, which then sends it to the Client. + +**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 passed to the VMSC/MSC Server. The VMSC/MSC Server sends an Emergency Call Origination message to the GMLC. The GMLC sends a Location Request to the VMSC/MSC Server. The VMSC/MSC Server then sends messages for individual positioning methods to the RAN. The RAN sends a Location Report to the VMSC/MSC Server, which in turn sends a MAP Subscriber Location Report to the GMLC. The GMLC sends a MAP Subscriber Location Report ack to the VMSC/MSC Server. The VMSC/MSC Server then sends Location Information to the GMLC. Finally, the GMLC sends an Emergency Call Release message to the UE. The sequence ends with the GMLC sending another MAP Subscriber Location Report to the VMSC/MSC Server, which responds with a MAP Subscriber Location Report ack.](a02b188a5fd52c99f84255322873bf29_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->>GMLC: 3. Emergency Call Origination + GMLC->>VMSC/MSC Server: 4. Location Request + VMSC/MSC Server->>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->>GMLC: 9. Location Information + GMLC->>UE: 10. Emergency Call Release + GMLC->>VMSC/MSC Server: 11. MAP Subscriber Location Report + VMSC/MSC Server->>GMLC: 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 passed to the VMSC/MSC Server. The VMSC/MSC Server sends an Emergency Call Origination message to the GMLC. The GMLC sends a Location Request to the VMSC/MSC Server. The VMSC/MSC Server then sends messages for individual positioning methods to the RAN. The RAN sends a Location Report to the VMSC/MSC Server, which in turn sends a MAP Subscriber Location Report to the GMLC. The GMLC sends a MAP Subscriber Location Report ack to the VMSC/MSC Server. The VMSC/MSC Server then sends Location Information to the GMLC. Finally, the GMLC sends an Emergency Call Release message to the UE. The sequence ends with the GMLC sending another MAP Subscriber Location Report to the VMSC/MSC Server, which responds with a MAP Subscriber Location Report ack. + +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 section 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 showing the interaction between Client, GMLC, VMSC/MSC SERVER, RAN, and UE for an emergency service call using location based routing.](9b9262a549828579ab904148450734f6_img.jpg) + +``` +sequenceDiagram + participant Client + participant GMLC + participant VMSC/MSC SERVER + participant RAN + participant UE + + Note right of RAN: 4. Messages for individual positioning methods + Note right of RAN: 12. Messages for individual positioning methods + + 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 + 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 + 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 +``` + +Sequence diagram showing the interaction between Client, GMLC, VMSC/MSC SERVER, RAN, and UE for an 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 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 the 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' involving Client, GMLC, and HLR/HSS. The GMLC sends a 'Provide Subscriber Location' message to the SGSN. The SGSN performs 'UE Paging' and 'Security procedures' with the UE. The SGSN then sends an 'LCS Location Notification Invoke' to the UE, which returns an 'LCS Location Notification Return Result'. The SGSN sends a 'Location Request' to the RAN. The RAN performs 'Messages for individual positioning methods' and returns a 'Location Report' to the SGSN. The SGSN sends a 'Provide Subscriber Location ack.' to the GMLC. Finally, another 'Common MT-LR procedure in PS and CS domain' is shown involving Client, GMLC, and HLR/HSS.](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC + participant HLR/HSS + participant SGSN + participant RAN + participant UE + + Note left of Client: 1. Common MT-LR procedure in PS and CS domain + GMLC->>SGSN: 2. Provide Subscriber Location + 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 right of RAN: 8. Messages for individual positioning methods + RAN->>SGSN: 9. Location Report + SGSN->>GMLC: 10. Provide Subscriber Location ack. + Note left of Client: 11. Common MT-LR procedure in PS and CS domain + +``` + +Sequence diagram illustrating the 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' involving Client, GMLC, and HLR/HSS. The GMLC sends a 'Provide Subscriber Location' message to the SGSN. The SGSN performs 'UE Paging' and 'Security procedures' with the UE. The SGSN then sends an 'LCS Location Notification Invoke' to the UE, which returns an 'LCS Location Notification Return Result'. The SGSN sends a 'Location Request' to the RAN. The RAN performs 'Messages for individual positioning methods' and returns a 'Location Report' to the SGSN. The SGSN sends a 'Provide Subscriber Location ack.' to the GMLC. Finally, another 'Common MT-LR procedure in PS and CS domain' is shown involving Client, GMLC, and HLR/HSS. + +**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 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 chapter 9.5.4 , if it is provided by H-GMLC. + +- 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) 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. +- 11) Common MT-LR procedure in PS and CS domain as described in 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 Emergency Services PS-MT-LR without HLR Query. The diagram shows the interaction 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 (RAN to 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.](0f7871077bba48a2c97f7859a5edda0d_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 right of GMLC: 2. Provide Subscriber Location + GMLC->>SGSN: 2. Provide Subscriber Location + Note right 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 + Note right of RAN: 5. Location Report + RAN->>SGSN: 5. Location Report + Note right 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 Emergency Services PS-MT-LR without HLR Query. The diagram shows the interaction 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 (RAN to 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 a 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 MAP\_PROVIDE\_SUBSCRIBER\_LOCATION message 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 illustrating the Network Induced Location Request for the PS Domain. The diagram shows interactions between LCS Client, GMLC, HLR/HSS, SGSN, RAN, and UE. The sequence is: 1. Location Request from SGSN to RAN; 2. Messages for individual positioning methods between RAN and UE; 3. Location Report from RAN to SGSN; 4. Subscriber LCS Report from SGSN to GMLC; 5. Subscriber LCS Report ACK from GMLC to SGSN; 6. Location Information from GMLC to LCS Client.](b8efedb73292a798b3f2050f9335cae6_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: + UE-->>RAN: + Note right of 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 illustrating the Network Induced Location Request for the PS Domain. The diagram shows interactions between LCS Client, GMLC, HLR/HSS, SGSN, RAN, and UE. The sequence is: 1. Location Request from SGSN to RAN; 2. Messages for individual positioning methods between RAN and UE; 3. Location Report from RAN to SGSN; 4. Subscriber LCS Report from SGSN to GMLC; 5. Subscriber LCS Report ACK from GMLC to SGSN; 6. Location Information from GMLC to 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 MAP 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 for General Network Positioning for a Deferred MT-LR with UE available event. Lifelines: Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, UE. The process involves an LCS Service Request from Client to Requesting GMLC, followed by handling between Requesting and Home GMLCs, then transfer to Visited GMLC. Visited GMLC sends a Provide Subscriber Location to MSC/SGSN, which returns an ack. MSC/SGSN detects the 'Requested event is detected' from RAN/UE. Location procedures for PS and CS MT-LR are initiated, resulting in a Subscriber Location Report from MSC/SGSN to Visited GMLC, which returns an ack. Visited GMLC sends an LCS Service Response to Home GMLC. A dashed box indicates that Home GMLC repeats the deferred MT-LR UE available request with new SGSN/MSC. Home GMLC performs a privacy check and returns an LCS Service Response to Requesting GMLC, which finally sends the LCS Service Response to the Client.](719ef0f734259484038b2434e5dc3f24_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: Error: Reference source not + Client->>GMLC_R: 1. LCS Service Request + Note over GMLC_R, GMLC_H: 2. LCS service request handling between GMLCs + GMLC_R->>GMLC_H: 5. LCS Service Response + GMLC_H->>GMLC_V: 3. Provide Subscriber Location + GMLC_V->>MSC_SGSN: 3. Provide Subscriber Location + MSC_SGSN->>GMLC_V: 4. Provide Subscriber Location ack. + GMLC_V->>GMLC_H: 6. LCS Service Response + GMLC_H->>Client: 7. LCS Service Response + UE->>RAN: 8 "Requested event is detected" + RAN->>MSC_SGSN: 8 "Requested event is detected" + Note over MSC_SGSN, UE: 9. Location procedures as for PS and CS MT-LR + 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 + Note over GMLC_H, GMLC_V: (12. H-GMLC repeats the deferred MT-LR UE available request with new SGSN/MSC) + Note over GMLC_H: 13. Privacy check + GMLC_H->>GMLC_R: 14. LCS Service Response + GMLC_R->>Client: 15. LCS Service Response + +``` + +Sequence diagram for General Network Positioning for a Deferred MT-LR with UE available event. Lifelines: Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, UE. The process involves an LCS Service Request from Client to Requesting GMLC, followed by handling between Requesting and Home GMLCs, then transfer to Visited GMLC. Visited GMLC sends a Provide Subscriber Location to MSC/SGSN, which returns an ack. MSC/SGSN detects the 'Requested event is detected' from RAN/UE. Location procedures for PS and CS MT-LR are initiated, resulting in a Subscriber Location Report from MSC/SGSN to Visited GMLC, which returns an ack. Visited GMLC sends an LCS Service Response to Home GMLC. A dashed box indicates that Home GMLC repeats the deferred MT-LR UE available request with new SGSN/MSC. Home GMLC performs a privacy check and returns an LCS Service Response to Requesting GMLC, which finally sends the LCS Service Response to the Client. + +**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 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 Combined Periodical/Deferred Mobile Terminating Location Request with UE available event. Lifelines: Client, R-GMLC, H-GMLC/V-GMLC, SGSN/MSC, RAN, UE. The diagram shows two periodic location requests initiated by the Client. The first request is processed by the R-GMLC, which starts a timer and calls the H-GMLC. The H-GMLC calls the SGSN/MSC, which returns the location. The R-GMLC then sends the response to the Client. When the timer expires, the R-GMLC calls the H-GMLC again, which calls the SGSN/MSC. The SGSN/MSC detects the 'Requested event is detected' from the UE and initiates location procedures. The H-GMLC receives the location report and sends it to the R-GMLC, which then sends the response to the Client. The second request follows a similar pattern, but the event is already satisfied, so the location procedures are skipped.](efb282bed9f06eef1987a14fb27bc599_img.jpg) + +``` + +sequenceDiagram + participant Client + participant R-GMLC + participant H-GMLC_V-GMLC as H-GMLC +V-GMLC + participant SGSN_MSC as SGSN / MSC + participant RAN + participant UE + + Note right of H-GMLC_V-GMLC: 2. Start Periodical timer + + Note right of R-GMLC: 6a. Periodical timer timeout + + Note right of H-GMLC_V-GMLC: 10. Periodical timer timeout + + Note right of SGSN_MSC: 7b. Location procedures as for PS and CS MT-LR + + Note right of SGSN_MSC: 14b. Location procedures as for PS and CS MT-LR + + Client->>R-GMLC: 1. LCS Service Request + R-GMLC-->>H-GMLC_V-GMLC: + H-GMLC_V-GMLC->>SGSN_MSC: 3. Provide Subscriber Location + SGSN_MSC-->>H-GMLC_V-GMLC: 4. Provide Subscriber Location ack. + H-GMLC_V-GMLC-->>R-GMLC: + R-GMLC->>Client: 5. LCS Service Response + + R-GMLC-->>H-GMLC_V-GMLC: + H-GMLC_V-GMLC->>SGSN_MSC: 8a. Subscriber Location Report + SGSN_MSC-->>H-GMLC_V-GMLC: 8b. Subscriber Location Report ack. + H-GMLC_V-GMLC-->>R-GMLC: + R-GMLC->>Client: 9. LCS Service Response + + Note right of SGSN_MSC: 7a. "Requested event is detected". + R-GMLC-->>H-GMLC_V-GMLC: + H-GMLC_V-GMLC->>SGSN_MSC: 11. Provide Subscriber Location + SGSN_MSC-->>H-GMLC_V-GMLC: 12. Provide Subscriber Location ack. + H-GMLC_V-GMLC-->>R-GMLC: + R-GMLC->>Client: 13. LCS Service Response + + Note right of SGSN_MSC: 14a. Event is already satisfied.. + R-GMLC-->>H-GMLC_V-GMLC: + H-GMLC_V-GMLC->>SGSN_MSC: 15a. Subscriber Location Report + SGSN_MSC-->>H-GMLC_V-GMLC: 15b. Subscriber Location Report ack. + H-GMLC_V-GMLC-->>R-GMLC: + R-GMLC->>Client: 16. LCS Service Response + +``` + +Sequence diagram for Combined Periodical/Deferred Mobile Terminating Location Request with UE available event. Lifelines: Client, R-GMLC, H-GMLC/V-GMLC, SGSN/MSC, RAN, UE. The diagram shows two periodic location requests initiated by the Client. The first request is processed by the R-GMLC, which starts a timer and calls the H-GMLC. The H-GMLC calls the SGSN/MSC, which returns the location. The R-GMLC then sends the response to the Client. When the timer expires, the R-GMLC calls the H-GMLC again, which calls the SGSN/MSC. The SGSN/MSC detects the 'Requested event is detected' from the UE and initiates location procedures. The H-GMLC receives the location report and sends it to the R-GMLC, which then sends the response to the Client. The second request follows a similar pattern, but the event is already satisfied, so the location procedures are skipped. + +**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 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 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 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 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 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 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 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 for Cancellation of a Deferred MT-LR – UE available event procedure. The diagram shows the interaction between a Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, and UE. The sequence of messages is: 1. LCS Cancel Service Request (Client to GMLC (Requesting)), 2. LCS Cancel Service Request (GMLC (Requesting) to GMLC (Home)), 3. LCS Cancel Service Request (GMLC (Home) to GMLC (Visited)), 4. Provide Subscriber Location (GMLC (Visited) to MSC/SGSN), 5. Provide Subscriber Location ack. (MSC/SGSN to GMLC (Visited)), 6. LCS Cancel Service Response (GMLC (Visited) to GMLC (Home)), 7. LCS Cancel Service Response (GMLC (Home) to GMLC (Requesting)), 8. LCS Cancel Service Response (GMLC (Requesting) to Client).](e5ded42f8e352da02ee86cb55550c45d_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 for Cancellation of a Deferred MT-LR – UE available event procedure. The diagram shows the interaction between a Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, and UE. The sequence of messages is: 1. LCS Cancel Service Request (Client to GMLC (Requesting)), 2. LCS Cancel Service Request (GMLC (Requesting) to GMLC (Home)), 3. LCS Cancel Service Request (GMLC (Home) to GMLC (Visited)), 4. Provide Subscriber Location (GMLC (Visited) to MSC/SGSN), 5. Provide Subscriber Location ack. (MSC/SGSN to GMLC (Visited)), 6. LCS Cancel Service Response (GMLC (Visited) to GMLC (Home)), 7. LCS Cancel Service Response (GMLC (Home) to GMLC (Requesting)), 8. LCS Cancel Service Response (GMLC (Requesting) 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 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 for Deferred MT-LR procedure for the Area event. Lifelines: Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, UE. The process involves an initial LCS Service Request, handling between GMLCs, providing subscriber location, paging, invoking area events, and subsequent reports and responses.](c2f36c545b190860d04e1d84e58d22cc_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 UE: 11. Area event occurs + + 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: 4. Paging, Authentication, Notification + MSC->>UE: 5. LCS Area Event Invoke + UE->>MSC: 6. LCS Area Event Invoke ack. + 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 + + Note right of UE: 11. Area event occurs + UE->>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 + + Note right of GMLC_H: 15. Repeat sending the Area Event Request to the new PLMN (Only applicable to the roaming case) + GMLC_H->>GMLC_R: 16. Privacy check + GMLC_R->>GMLC_H: 17. LCS Service Response + GMLC_H->>Client: 18. LCS Service Response + +``` + +Sequence diagram for Deferred MT-LR procedure for the Area event. Lifelines: Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, UE. The process involves an initial LCS Service Request, handling between GMLCs, providing subscriber location, paging, invoking area events, and subsequent reports and responses. + +**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.](7b18671bc31881a5c474883bf6a300fd_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 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 sequence starts with a 'Common MT-LR procedure in CS and PS domain' (1). The GMLC sends a 'Provide Subscriber Location' message (2) to the VMSC/MSC SERVER. The VMSC/MSC SERVER sends a 'UE Paging, Authentication, Ciphering' message (3) to the UE. The UE sends an 'LCS Location Notification' (4) to the VMSC/MSC SERVER. The VMSC/MSC SERVER sends an 'LCS Location Notification Return' (5) to the UE. The UE sends a 'Provide Subscriber Location ack' (6) to the GMLC. Finally, a 'Common ML-LR procedure in CS and PS domain' (7) is performed.](5cf80bac69830ea773ac17c87e0ae24d_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 + UE->>VMSC/MSC SERVER: 4. LCS Location Notification + VMSC/MSC SERVER->>UE: 5. LCS Location Notification Return + UE->>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 sequence starts with a 'Common MT-LR procedure in CS and PS domain' (1). The GMLC sends a 'Provide Subscriber Location' message (2) to the VMSC/MSC SERVER. The VMSC/MSC SERVER sends a 'UE Paging, Authentication, Ciphering' message (3) to the UE. The UE sends an 'LCS Location Notification' (4) to the VMSC/MSC SERVER. The VMSC/MSC SERVER sends an 'LCS Location Notification Return' (5) to the UE. The UE sends a 'Provide Subscriber Location ack' (6) to the GMLC. Finally, a 'Common ML-LR procedure in CS and PS domain' (7) is performed. + +**Figure 9.10: CS Post Positioning Notification and Verification Procedure** + +- 1) Common PS and CS MT-LR procedure as described in 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 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, followed by a Provide Subscriber Location message from GMLC to SGSN. The SGSN then pages the UE, performs security procedures, invokes the LCS Location Notification, receives a return result, sends a Provide Subscriber Location ack to the GMLC, and concludes with another common MT-LR procedure.](070352b751dd0711b8ac6ddfa6df1d98_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC + participant HLR/HSS + participant SGSN + participant RAN + participant UE + + Note over Client, HLR/HSS: 1. Common MT-LR procedure in PS and CS domain + GMLC->>SGSN: 2. Provide Subscriber Location + SGSN->>UE: 3. Paging + Note over SGSN, UE: 4. Security procedures + Note over RAN, UE: 5. LCS Location Notification Invoke + UE-->>SGSN: 6. LCS Location Notification Return Result + SGSN->>GMLC: 7. Provide Subscriber Location ack + Note over Client, 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, followed by a Provide Subscriber Location message from GMLC to SGSN. The SGSN then pages the UE, performs security procedures, invokes the LCS Location Notification, receives a return result, sends a Provide Subscriber Location ack to the GMLC, and concludes with another common MT-LR procedure. + +**Figure 9.11: PS Post Positioning Notification and Verification Procedure** + +- 1) Common PS and CS MT-LR procedure as described in 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 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 interactions between Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, and UE. The steps are: 1. Client sends LCS Service Request to GMLC (Requesting); 2. LCS service request handling between GMLCs; 3. GMLC (Visited) sends Provide Subscriber Location to MSC/SGSN; 4. MSC/SGSN performs Paging, Authentication, Notification; 5. MSC/SGSN sends LCS Periodic Location Invoke to UE; 6. UE sends LCS Periodic Location Invoke ack. to MSC/SGSN; 7. MSC/SGSN sends Provide Subscriber Location ack. to GMLC (Visited); 8. GMLC (Visited) sends LCS Service Response to GMLC (Home); 9. GMLC (Home) sends LCS Service Response to GMLC (Requesting); 10. GMLC (Requesting) sends LCS Service Response to Client.](b1e7bb95fa1587d870de03df02477df4_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 + + Client->>GMLC_Req: 1. LCS Service Request + GMLC_Req->>GMLC_Visited: 2. LCS service request handling between GMLCs + 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 interactions between Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, and UE. The steps are: 1. Client sends LCS Service Request to GMLC (Requesting); 2. LCS service request handling between GMLCs; 3. GMLC (Visited) sends Provide Subscriber Location to MSC/SGSN; 4. MSC/SGSN performs Paging, Authentication, Notification; 5. MSC/SGSN sends LCS Periodic Location Invoke to UE; 6. UE sends LCS Periodic Location Invoke ack. to MSC/SGSN; 7. MSC/SGSN sends Provide Subscriber Location ack. to GMLC (Visited); 8. GMLC (Visited) sends LCS Service Response to GMLC (Home); 9. GMLC (Home) sends LCS Service Response to GMLC (Requesting); 10. GMLC (Requesting) sends LCS Service Response 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. The first cycle (steps 1-12) involves a CS/PS Service Request, authentication, MO-LR Invoke, Location Request/Report, MAP Subscriber messages, Privacy Check, and final LCS Service Responses. The second cycle (steps 13-22) involves an LCS Location Update, Ack, Messages for individual positioning, Location Report, MAP Subscriber messages, Privacy Check, and final LCS Service Responses. The diagram ends with an ellipsis, an LCS MO-LR Return Result, and a release of connections.](1e5a58dcaf0936bf18dc3dd0d9cd43ff_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 UE: Error: Reference source not + + UE->>MSC/SGSN: 1. CS: CM Service Request +PS: Service Request + MSC/SGSN->>UE: 2. CS: Authentication, Ciphering or CM Service Accept +(PS: Part of 1: Possible Security Procedures) + MSC/SGSN->>RAN: 3. LCS MO-LR Invoke (+ location estimate) + Note right of RAN: Messages for individual positioning + RAN->>MSC/SGSN: 4. Location Request + MSC/SGSN->>RAN: 6. Location Report + MSC/SGSN->>V-GMLC: 7. MAP Subscriber Location Report + V-GMLC->>MSC/SGSN: 8. MAP Subscriber Location Report ack. + 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 right of UE: Error: Reference source not + + MSC/SGSN->>UE: 13. LCS Location Update + UE->>MSC/SGSN: 14. LCS Location Update Ack. + Note right of RAN: Messages for individual positioning + RAN->>MSC/SGSN: 16. Location Report + MSC/SGSN->>V-GMLC: 17. MAP Subscriber Location Report + V-GMLC->>MSC/SGSN: 18. MAP Subscriber Location Report ack. + 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 right of UE: Error: Reference source not + + Note right of MSC/SGSN: ... + MSC/SGSN->>UE: 25. LCS MO-LR Return Result + UE->>MSC/SGSN: 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. The first cycle (steps 1-12) involves a CS/PS Service Request, authentication, MO-LR Invoke, Location Request/Report, MAP Subscriber messages, Privacy Check, and final LCS Service Responses. The second cycle (steps 13-22) involves an LCS Location Update, Ack, Messages for individual positioning, Location Report, MAP Subscriber messages, Privacy Check, and final LCS Service Responses. The diagram ends with an ellipsis, an LCS MO-LR Return Result, and a release of 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 MAP 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. Lifelines: Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, UE. The sequence shows the Client sending an LCS Cancel Service Request to the Requesting GMLC, which then forwards it to the Home GMLC. The Home GMLC sends routing info to the HLR/HSS, which returns it. The Home GMLC then sends the request to the Visited GMLC, which provides the subscriber location to the MSC/SGSN. The MSC/SGSN sends a periodic location cancel to the UE, which responds. The MSC/SGSN then provides the subscriber location ack to the Visited GMLC, which sends an LCS Cancel Service Response back to the Home GMLC, which finally sends the response to the Requesting GMLC, which then sends it to the Client.](0dfdff10c725fe9c332b07ade9d23a5e_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_V: Error: Reference source not + 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. Lifelines: Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, UE. The sequence shows the Client sending an LCS Cancel Service Request to the Requesting GMLC, which then forwards it to the Home GMLC. The Home GMLC sends routing info to the HLR/HSS, which returns it. The Home GMLC then sends the request to the Visited GMLC, which provides the subscriber location to the MSC/SGSN. The MSC/SGSN sends a periodic location cancel to the UE, which responds. The MSC/SGSN then provides the subscriber location ack to the Visited GMLC, which sends an LCS Cancel Service Response back 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 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, and PS: Part 1: Possible Security Procedures. The UE then sends an MO-LR Invoke (+ termination cause + LCS Client Address) to the MSC/SGSN. The MSC/SGSN sends a MAP Subscriber Location Report to the V-GMLC. The V-GMLC sends an MO-LR Location Cancellation to the H-GMLC. The H-GMLC sends an MO-LR Location Cancellation to the R-GMLC. The R-GMLC sends a Location Cancellation to the LCS Client. The LCS Client sends a Location Cancellation ack to the R-GMLC. The R-GMLC sends an MO-LR Location Cancellation Ack to the H-GMLC. The H-GMLC sends an MO-LR Location Cancellation Ack to the V-GMLC. The V-GMLC sends a MAP Subscriber Location Report ack. to the MSC/SGSN. The MSC/SGSN sends an LCS MO-LR Return Result to the UE. Finally, the UE sends a Release CM, MM/GMM, RR/RRC connections or message to the MSC/SGSN.](a963ca41bde1669b18a4b783616f228b_img.jpg) + +``` + +sequenceDiagram + participant UE + 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 + participant RAN + + Note right of UE: Error: Reference source not + UE->>MSC_SGSN: 1. CS: CM Service Request +PS: Service Request + MSC_SGSN-->>UE: 2. CS: Authentication, Ciphering or +CM Service Accept +PS: Part 1: Possible Security Procedures + UE->>MSC_SGSN: 3. MO-LR Invoke (+ termination cause + +LCS Client Address) + MSC_SGSN->>V_GMLC: 4. MAP Subscriber Location Report + V_GMLC->>H_GMLC: 5. MO-LR Location Cancellation + H_GMLC->>R_GMLC: 6. MO-LR Location Cancellation + R_GMLC->>LCS_Client: 7. Location Cancellation + LCS_Client->>R_GMLC: 8. Location Cancellation ack + R_GMLC->>H_GMLC: 9. MO-LR Location Cancellation Ack + H_GMLC->>V_GMLC: 10. MO-LR Location Cancellation Ack + V_GMLC->>MSC_SGSN: 11. MAP Subscriber Location Report ack. + MSC_SGSN->>UE: 12. LCS MO-LR Return Result + UE->>MSC_SGSN: 13. Release CM, MM/GMM, RR/RRC connections +or + +``` + +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 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, and PS: Part 1: Possible Security Procedures. The UE then sends an MO-LR Invoke (+ termination cause + LCS Client Address) to the MSC/SGSN. The MSC/SGSN sends a MAP Subscriber Location Report to the V-GMLC. The V-GMLC sends an MO-LR Location Cancellation to the H-GMLC. The H-GMLC sends an MO-LR Location Cancellation to the R-GMLC. The R-GMLC sends a Location Cancellation to the LCS Client. The LCS Client sends a Location Cancellation ack to the R-GMLC. The R-GMLC sends an MO-LR Location Cancellation Ack to the H-GMLC. The H-GMLC sends an MO-LR Location Cancellation Ack to the V-GMLC. The V-GMLC sends a MAP Subscriber Location Report ack. to the MSC/SGSN. The MSC/SGSN sends an LCS MO-LR Return Result to the UE. Finally, the UE sends a Release CM, MM/GMM, RR/RRC connections or message to the 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. + +![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 exchanges, UE routing info inquiries, positioning procedures, and finally an LCS response.](e1ce114c43dcefce51eadcd12f2da6d2_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 exchanges, UE routing info inquiries, 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 + +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.](c0ca823603794512478906b302176bca_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, 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. + +![Sequence diagram illustrating the General Network Positioning for EPC-MT-LR. The diagram shows interactions between Client, GMLC, HLR/HSS, E-SMLC, MME, RAN, and UE. The process starts with a 'Common MT-LR procedure in PS and CS domain' involving Client, GMLC, and HLR/HSS. GMLC sends a 'Provide Subscriber Location' message to MME. MME initiates a 'Network Triggered Service Request' to UE. UE responds with 'NAS Location Notification Return Result' to MME. MME sends a 'Location Request' to E-SMLC. E-SMLC performs a 'Positioning Procedure' and sends a 'Location Response' to MME. MME sends a 'Provide Subscriber Location ack.' to GMLC. The process ends with another 'Common MT-LR procedure in PS and CS domain' involving Client, GMLC, and HLR/HSS.](5a01395925fc88802da68fb5ac0f31ff_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC + participant HLR/HSS + participant E-SMLC + participant MME + participant RAN + participant UE + + Note over Client, GMLC, HLR/HSS: 1. Common MT-LR procedure in PS and CS domain + GMLC->>MME: 2. Provide Subscriber Location + Note over MME, RAN, 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, MME: 7. Positioning Procedure + E-SMLC->>MME: 8. Location Response + MME->>GMLC: 9. Provide Subscriber Location ack. + Note over Client, GMLC, HLR/HSS: 10. Common MT-LR procedure in PS and CS domain + +``` + +Sequence diagram illustrating the General Network Positioning for EPC-MT-LR. The diagram shows interactions between Client, GMLC, HLR/HSS, E-SMLC, MME, RAN, and UE. The process starts with a 'Common MT-LR procedure in PS and CS domain' involving Client, GMLC, and HLR/HSS. GMLC sends a 'Provide Subscriber Location' message to MME. MME initiates a 'Network Triggered Service Request' to UE. UE responds with 'NAS Location Notification Return Result' to MME. MME sends a 'Location Request' to E-SMLC. E-SMLC performs a 'Positioning Procedure' and sends a 'Location Response' to MME. MME sends a 'Provide Subscriber Location ack.' to GMLC. The process ends with another 'Common MT-LR procedure in PS and CS domain' involving Client, GMLC, and HLR/HSS. + +Figure 9.18: General Network Positioning for EPC-MT-LR + +#### 9.1.15.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 MME 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 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. + +- 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 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. +- 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 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: 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. 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 co ordinate is requested but the E-SMLC can only obtain horizontal co-ordinates, these may be returned. + +### 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) 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. +- 10) Common MT-LR procedure in PS and CS domain as described in clause 9.1.1. + +### 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 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 and UE via RAN); 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.](e20792fef9de6560b2d6c5441da7614a_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: Emergency Services Call + 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 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 and UE via RAN); 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 a 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) procedure. The diagram shows interactions between LCS Client, LRF/GMLC, HLR/HSS, E-SMLC, MME, RAN, and UE. The sequence starts with the UE performing an emergency attach or setup emergency bearer with the RAN and MME. The MME then sends a location request to the E-SMLC. The E-SMLC sends messages for individual positioning methods to the RAN and UE. The E-SMLC returns a location response to the MME. The MME sends a subscriber LCS report to the LRF/GMLC, which responds with a subscriber LCS report ACK. Finally, the LRF/GMLC sends location information to the LCS Client.](6ba310120ebcd99661c4ee1c58a1586c_img.jpg) + +``` + +sequenceDiagram + participant LCS Client + participant LRF/GMLC + participant HLR/HSS + participant E-SMLC + participant MME + participant RAN + participant UE + + Note over MME, UE: 1. Emergency Attach or Setup Emergency Bearer + MME->>E-SMLC: 2. Location Request + Note over E-SMLC, UE: 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 + LRF/GMLC-->>LCS Client: 7. Location Information + +``` + +Sequence diagram for EPC Network Induced Location Request (EPC-NI-LR) procedure. The diagram shows interactions between LCS Client, LRF/GMLC, HLR/HSS, E-SMLC, MME, RAN, and UE. The sequence starts with the UE performing an emergency attach or setup emergency bearer with the RAN and MME. The MME then sends a location request to the E-SMLC. The E-SMLC sends messages for individual positioning methods to the RAN and UE. The E-SMLC returns a location response to the MME. The MME sends a subscriber LCS report to the LRF/GMLC, which responds with a subscriber LCS report ACK. Finally, the LRF/GMLC sends location information to the LCS Client. + +**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 (EPC NI LR), 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. + +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 procedure involves a common MT-LR procedure, a Provide Subscriber Location message from GMLC to MME, a Network Triggered Service Request from MME to UE, a NAS Location Notification Invoke from MME to UE, a NAS Location Notification Return Result from UE to MME, a Provide Subscriber Location ack from MME to GMLC, and a final common MT-LR procedure.](69467ece0a576b4c2ec3e0c89ba61527_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 + Note right of UE: 5. NAS Location Notification Return Result + 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 procedure involves a common MT-LR procedure, a Provide Subscriber Location message from GMLC to MME, a Network Triggered Service Request from MME to UE, a NAS Location Notification Invoke from MME to UE, a NAS Location Notification Return Result from UE to MME, a Provide Subscriber Location ack from MME to GMLC, and a final common MT-LR procedure. + +**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 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. +- 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.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. Lifelines: LCS Client, GMLC, H-GMLC, V-GMLC, MSC SERVER (MSC), RAN, UE. The sequence shows the flow of location requests and reports between these entities.](a5404b7275b06497eecf9b5883604753_img.jpg) + +``` + +sequenceDiagram + participant LCS Client + participant GMLC + participant H-GMLC + participant V-GMLC + participant MSC SERVER as MSC SERVER (MSC) + participant RAN + participant UE + + Note right of RAN: Error: Reference source not + + UE->>RAN: 1. CM Service Request + RAN->>MSC: 2. CM Service Request + MSC->>UE: 3. Authentication, Ciphering or CM Service Accept + MSC->>MSC: 4. Location Services Invoke + MSC->>RAN: 5. Location Request + Note right of MSC: 6. Messages for individual positioning methods or transfer of location assistance data + MSC->>V-GMLC: 7. Location Report. + V-GMLC->>H-GMLC: 8. MAP Subscriber Location Report + H-GMLC->>GMLC: 9. MO-LR Location Information + GMLC->>LCS Client: 10. MO-LR Location Information + LCS Client->>GMLC: 11. Location Information + GMLC->>LCS Client: 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: 15. MAP Subscriber Location Report ack. + MSC->>UE: 16. LCS MO-LR Return Result + MSC->>RAN: 17. Release CM, MM, RRC connections + +``` + +Sequence diagram for General Network Positioning for CS-MO-LR. Lifelines: LCS Client, GMLC, H-GMLC, V-GMLC, MSC SERVER (MSC), RAN, UE. The sequence shows the flow of location requests and reports between these entities. + +**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 chapter 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. The diagram shows interactions between LCS Client, GMLC, H-GMLC, V-GMLC, HLR/HSS, SGSN, RAN, and UE. The process starts with a Service Request from UE to SGSN, followed by security procedures, Services Invoke, Location Request, positioning messages, Location Report, MAP Subscriber Location Report, and various acknowledgments back to the LCS Client.](8edfc370769207831f060f44d2281084_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 + Note right of SGSN: (Part of 1: Possible security procedures) + SGSN->>UE: 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->>SGSN: 5. Location Report. + SGSN->>V-GMLC: 6. MAP 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. MAP Subscriber Location Report ack. + SGSN->>UE: 14. Service 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, SGSN, RAN, and UE. The process starts with a Service Request from UE to SGSN, followed by security procedures, Services Invoke, Location Request, positioning messages, Location Report, MAP Subscriber Location Report, and various acknowledgments back to the LCS Client. + +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 MAP 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 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. +- 7) 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 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 MAP 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 MAP 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 MAP 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. Lifelines: LCS Client, R-GMLC, H-GMLC, V-GMLC, MSC/SGSN, RAN, UE. The sequence shows the UE sending a Service Request to the RAN, which is forwarded to the MSC/SGSN. The MSC/SGSN then sends an MO-LR Invoke to the V-GMLC, which is passed through the H-GMLC and R-GMLC to the LCS Client. The LCS Client responds with Location Information, which is passed back through the chain. The MSC/SGSN also sends a MAP Subscriber Location Report to the V-GMLC, which is acknowledged. Finally, the MSC/SGSN sends an LCS MO-LR Return Result to the UE, and either releases connections or sends another MO-LR Invoke.](2b00743506f6a3bbd17af764162dc76d_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->>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->>UE: 13b. MO-LR Invoke (+ location estimate or request) + +``` + +Sequence diagram for Deferred MO-LR Initiation for Periodic Location in CS and PS domain. Lifelines: LCS Client, R-GMLC, H-GMLC, V-GMLC, MSC/SGSN, RAN, UE. The sequence shows the UE sending a Service Request to the RAN, which is forwarded to the MSC/SGSN. The MSC/SGSN then sends an MO-LR Invoke to the V-GMLC, which is passed through the H-GMLC and R-GMLC to the LCS Client. The LCS Client responds with Location Information, which is passed back through the chain. The MSC/SGSN also sends a MAP Subscriber Location Report to the V-GMLC, which is acknowledged. Finally, the MSC/SGSN sends an LCS MO-LR Return Result to the UE, and either releases connections or sends another MO-LR Invoke. + +**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. Lifelines: LCS Client, R-GMLC, H-GMLC, V-GMLC, MSC/SGSN, RAN, UE. The sequence shows 14 steps of interaction between these entities.](ef45b00396c293be0b18d32b97118bf4_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 UE: Error: Reference source not + UE->>MSC/SGSN: 1. CS: CM Service Request +PS: Service Request + MSC/SGSN-->>UE: 2. CS: Authentication, Ciphering or CM Service Accept +PS: Part of 1: Possible Security Procedures + UE->>MSC/SGSN: 3. LCS MO-LR Invoke + MSC/SGSN->>RAN: 4. Location Request + Note right of RAN: 5. Messages for individual positioning + RAN-->>MSC/SGSN: 6. Location Report + MSC/SGSN->>UE: 7. LCS Location Update + UE-->>MSC/SGSN: 8. LCS Location Update Ack + Note right of RAN: 9. Messages for individual positioning + RAN-->>MSC/SGSN: 10. Location Report + MSC/SGSN->>UE: 11. LCS Location Update + UE-->>MSC/SGSN: 12. LCS Location Update Ack + Note right of MSC/SGSN: ... + MSC/SGSN->>UE: 13. LCS MO-LR Return Result + UE-->>MSC/SGSN: 14. Release CM, MM/GMM, RR/RRC connections + +``` + +Sequence diagram for MO-LR for Periodic Self Location with Periodic Positioning in the RAN. Lifelines: LCS Client, R-GMLC, H-GMLC, V-GMLC, MSC/SGSN, RAN, UE. The sequence shows 14 steps of interaction between these entities. + +**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 + +Figure 9.8c describes the MO-LR procedure for LCS for I-WLAN. + +![Sequence diagram of the 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. The External LCS Client sends a request to the GMLC/SLP, which then interacts with the PDG and WAG to establish a connection with the WLAN UE via the WLAN AN. The GMLC/SLP then sends a response back to the External LCS Client.](74e409e1548dd2606c4de9bdfe9806e4_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 of the 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. The External LCS Client sends a request to the GMLC/SLP, which then interacts with the PDG and WAG to establish a connection with the WLAN UE via the WLAN AN. The GMLC/SLP then sends a response back to the External LCS Client. + +**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. The process starts with a UE Triggered Service Request from UE to HLR/HSS, followed by a NAS MO-LR Request from UE to MME. The MME sends a Location Request to E-SMLC, which then sends messages for individual positioning methods or transfer of location assistance data. The E-SMLC sends a Location Response to MME, which then sends a Subscriber Location Report to V-GMLC. The V-GMLC sends an MO-LR Location Information to H-GMLC, which then sends an MO-LR Location Information to GMLC. The GMLC sends a Location Information to LCS Client, which responds with a Location Information Ack. The GMLC also sends an MO-LR Location Information Ack to H-GMLC, which sends an MO-LR Location Information Ack to V-GMLC. The V-GMLC sends a Subscriber Location Report ack. to MME, which then sends a NAS MO-LR Response to UE.](c1b762c358fd423d6686563b3fde7750_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant MME + participant E-SMLC + participant HLR/HSS + participant V-GMLC + participant H-GMLC + participant GMLC + participant LCS Client + + Note right of HLR/HSS: 1. UE Triggered Service Request + UE->>MME: 2. NAS MO-LR Request + MME->>E-SMLC: 3. Location Request + Note right of E-SMLC: 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. The process starts with a UE Triggered Service Request from UE to HLR/HSS, followed by a NAS MO-LR Request from UE to MME. The MME sends a Location Request to E-SMLC, which then sends messages for individual positioning methods or transfer of location assistance data. The E-SMLC sends a Location Response to MME, which then sends a Subscriber Location Report to V-GMLC. The V-GMLC sends an MO-LR Location Information to H-GMLC, which then sends an MO-LR Location Information to GMLC. The GMLC sends a Location Information to LCS Client, which responds with a Location Information Ack. The GMLC also sends an MO-LR Location Information Ack to H-GMLC, which sends an MO-LR Location Information Ack to V-GMLC. The V-GMLC sends a Subscriber Location Report ack. to MME, which then sends a NAS MO-LR Response to UE. + +Figure 9.8d: General Network Positioning for packet switched MO-LR + +### 9.2.6.1 Location Preparation Procedure + +- 1) 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. +- 2) The UE sends a NAS PDU containing an MO-LR Request inside an RRC UL Information Transfer message to the eNodeB. 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. + +### 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. + +### 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 except that the V-GMLC receives a Subscriber Location Report instead of a MAP Subscriber Location Report. +- 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. +- 13) 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. + +- 14) 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 of 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 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.](10ceb47973510a1b47421741263146cc_img.jpg) + +``` + +sequenceDiagram + participant E-SMLC + participant MME + participant eNodeB + participant UE + Note right of UE: 5. Positioning Measurements and Computation + E-SMLC->>MME: 1. Positioning Request (DL Positioning Message) + MME->>UE: 2. Network Triggered Service Request + MME->>eNodeB: 3. NAS Transport (DL Positioning Message) + eNodeB->>UE: 4. DL Positioning Message + UE->>MME: 6. UE Triggered Service Request + 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 of 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 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 EPC-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 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. +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. +6. If the UE is in ECM-IDLE state, the UE instigates a UE triggered service request as defined in TS 23.401 [41] in order 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. The sequence starts with E-SMLC sending '1. Location Information (Network Positioning Information)' to MME. MME then sends a '2. Network Triggered Service Request' to eNode B. eNode B sends '3. S1-AP Transport Message (Network Positioning Information)' to UE. UE performs '4. Obtain Measurements'. eNode B then sends '5. S1-AP Transport Message (Network Positioning Information)' to MME. Finally, MME sends '6. Location Information (Network Positioning Information)' to E-SMLC.](497d7e14540664a2914557cad79f3791_img.jpg) + +``` + +sequenceDiagram + participant E-SMLC + participant MME + participant eNode B + participant UE + Note right of eNode B: 4. Obtain Measurements + E-SMLC->>MME: 1. Location Information (Network Positioning Information) + MME->>eNode B: 2. Network Triggered Service Request + eNode B->>UE: 3. S1-AP Transport Message (Network Positioning Information) + eNode B->>MME: 5. S1-AP Transport Message (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. The sequence starts with E-SMLC sending '1. Location Information (Network Positioning Information)' to MME. MME then sends a '2. Network Triggered Service Request' to eNode B. eNode B sends '3. S1-AP Transport Message (Network Positioning Information)' to UE. UE performs '4. Obtain Measurements'. eNode B then sends '5. S1-AP Transport Message (Network Positioning Information)' to MME. Finally, MME sends '6. Location Information (Network Positioning Information)' to E-SMLC. + +**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 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. +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' (internal step); 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.](fb73a07d61dc5c47709b9802b894d716_img.jpg) + +``` + +sequenceDiagram + participant E-SMLC + participant MME + participant eNode B + participant UE + E-SMLC->>MME: 1. Location Information (Network Positioning Information) + MME->>eNode B: 2. S1-AP Transport Message (Network Positioning Information) + Note over eNode B: 3. Obtain Measurements + 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' (internal step); 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.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.2a: 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 Access + +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 or E-UTRAN to HRPD) 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]. 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.2b 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.2b. + +**Table 9.2b: 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 SUPL [38], [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 SUPL [38], [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 | E-UTRAN, UTRAN PS | OMA SUPL [38], [39] | OMA SUPL [38], [39] | None identified | +| E-UTRAN | HRPD | TS 23.271 | OMA SUPL [38], [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 SUPL [38], [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 SUPL [38], [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) | +| 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. | | | | | + +Details concerning the interactions between the LRF, GMLCs, E-SLPs and any 1xRTT location servers to support the reconfiguration requirements in Table 9.2b 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 procedures, and reconfiguration of location servers.](92724c769da9d46b730fde1a6dccb023_img.jpg) + +``` + +sequenceDiagram + participant LRF + participant TLS as Target Location Server + participant SLS as Source Location Server + participant TSNode as Target Serving Node + participant SMME as Source MME/SG SN + participant UE + + Note over LRF, UE: 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 Required + SMME->>TSNode: 5. Handover Request + Note over TSNode, UE: 6. Handover + Note over SMME, UE: 7. Terminate Location Session + SMME->>SLS: 8a. Provide Subscriber Location response (location estimate, Target Serving Node Identity or Reference Cell ID) + SMME->>SLS: 8b. Subscriber Location Report (Handover event, IMSI, MSISDN, IMEI, Location Estimate, Target Serving Node Identity or Reference Cell ID) + SLS->>SMME: 9. Subscriber Location Report Ack. + TSNode->>SLS: 10. Subscriber Location Report (Handover event, IMSI, MSISDN, IMEI, Target Serving Node Identity) + SLS->>TSNode: 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 procedures, and 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.2b 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. + +## 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 chapters 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 sends 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 of MT-LR procedure for IMS Public User Identities. Lifelines: LCS Client, GMLC (Requesting), LIMS-IWF (Requesting), LIMS-IWF (Home), HLR/HSS, SLF, GMLC (Home), GMLC (Visited). The sequence shows the flow of LCS Service Request and Response messages between these entities, including SLF queries and HSS routing information exchanges.](f4e5a86da5c799372a7c1ea2397dedb7_img.jpg) + +``` + +sequenceDiagram + participant LCS Client + participant GMLC_R 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_R: 1. LCS Service Request + GMLC_R->>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_R: 20. LCS Service Response + GMLC_R->>LCS Client: 21. LCS Service Response + +``` + +Sequence diagram of MT-LR procedure for IMS Public User Identities. Lifelines: LCS Client, GMLC (Requesting), LIMS-IWF (Requesting), LIMS-IWF (Home), HLR/HSS, SLF, GMLC (Home), GMLC (Visited). The sequence shows the flow of LCS Service Request and Response messages between these entities, including SLF queries and HSS routing information exchanges. + +**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
| +| | 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 | | +| | 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
| +| | 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 | | +| | 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. | + +## 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 chapter 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 chapter 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 section, 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 [Note4]'. 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'. If 'No' to 'Call Unrelated class criteria met?', it leads to 'The location request is not allowed unconditionally'.](86986d4dfd54f298d7b9fa9f82ab3009_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 [Note4]] + 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 [Note4]'. 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'. If 'No' to 'Call Unrelated class criteria met?', 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 for privacy related action selection flow diagram of the serving node. The process starts at 'Start' and proceeds through several decision points regarding call/session related and unrelated class indicators and criteria. Final outcomes include 'Call/session related class', 'Call/session unrelated class', or 'The location request is not allowed unconditionally'.](c15cb6383bc35906e6b3c7c3aac621ed_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 -- NO --> R1[Call/session +related class] + D4 -- YES --> D5{call/session related +class is looser?} + D5 -- YES --> R1 + D5 -- NO --> R2[Call/session +unrelated class] + R2 --> D3 + D3 -- YES --> R2 + D3 -- NO --> R3[The location request +is not allowed +unconditionally] + +``` + +Flowchart for privacy related action selection flow diagram of the serving node. The process starts at 'Start' and proceeds through several decision points regarding call/session related and unrelated class indicators and criteria. Final outcomes include 'Call/session related class', 'Call/session unrelated class', or 'The location request is not allowed unconditionally'. + +**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, TS22.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 illustrates the interaction between five entities: Terminal, Gateway, PMD, LCS client, and GMLC/PPR. The sequence of messages is as follows: 1. Terminal sends a 'Service request' to Gateway. 2. Gateway sends an 'Obtain pseudonym' request to PMD. 3. Gateway sends a 'Service request with pseudonym' to LCS client. 4. LCS client sends a 'Location request with pseudonym' to GMLC/PPR. 5. GMLC/PPR sends an 'Obtain verinym' request to PMD. 6. GMLC/PPR sends a 'Location response' to LCS client. 7. LCS client sends a 'Service response' to Gateway. 8. Gateway sends an 'Obtain MSISDN' request to PMD. 9. Gateway sends a 'Service response' to Terminal.](8bdf315853992d21f389da554f3a8215_img.jpg) + +``` + +sequenceDiagram + participant Terminal + participant Gateway + participant PMD + participant LCS_client as LCS client + participant GMLC_PPR as 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 illustrates the interaction between five entities: Terminal, Gateway, PMD, LCS client, and GMLC/PPR. The sequence of messages is as follows: 1. Terminal sends a 'Service request' to Gateway. 2. Gateway sends an 'Obtain pseudonym' request to PMD. 3. Gateway sends a 'Service request with pseudonym' to LCS client. 4. LCS client sends a 'Location request with pseudonym' to GMLC/PPR. 5. GMLC/PPR sends an 'Obtain verinym' request to PMD. 6. GMLC/PPR sends a 'Location response' to LCS client. 7. LCS client sends a 'Service response' to Gateway. 8. Gateway sends an 'Obtain MSISDN' request to PMD. 9. Gateway sends a '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. LCS client sends a Pseudonym Req to Proxy/Gateway. Proxy/Gateway sends an Obtain pseudonym request to PPR/PMD (IPD). PPR/PMD (IPD) sends an Obtain Verinym request to GMLC. GMLC sends a Location request with pseudonym to LCS client. LCS client sends a Location Response to GMLC. GMLC sends a Pseudonym Resp to PPR/PMD (IPD). PPR/PMD (IPD) sends a Pseudonym Resp to Proxy/Gateway. Proxy/Gateway sends an Anonym Ser. Resp to LCS client. Finally, Proxy/Gateway sends a Final Ser. Resp to Terminal.](4f7470055bfc22c4aa6b007a4056940e_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: 5. Pseudonym Resp + Proxy->>LCS: 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. LCS client sends a Pseudonym Req to Proxy/Gateway. Proxy/Gateway sends an Obtain pseudonym request to PPR/PMD (IPD). PPR/PMD (IPD) sends an Obtain Verinym request to GMLC. GMLC sends a Location request with pseudonym to LCS client. LCS client sends a Location Response to GMLC. GMLC sends a Pseudonym Resp to PPR/PMD (IPD). PPR/PMD (IPD) sends a Pseudonym Resp to Proxy/Gateway. Proxy/Gateway sends an Anonym Ser. Resp to LCS client. Finally, 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 chapter 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 section 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. + +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.](b2b3b6b051e9108f340d1789b1296667_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 + LCS Client->>R-GMLC: 1. LCS Service Request + R-GMLC->>H-GMLC: + 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 + Note right of UE/(U)SIM: 6. Event Occurs + UE/(U)SIM->>H-GMLC: 7. Change of Area Event Report + Note right of H-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 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 | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | Old | New | +| 06/2010 | SP-48 | SP-100348 | 0385 | 2 | C | Provide Service Type to E-SMLC | 9.4.0 | 10.0.0 | +| 12/2010 | SP-50 | SP-100678 | 0390 | - | A | Clarification on Cell ID notification to E-SMLC | 10.0.0 | 10.1.0 | +| 01/2011 | - | - | - | - | - | Update of LTE logo to LTE-Advanced logo | 10.1.0 | 10.1.1 | +| 03/2011 | SP-51 | SP-110076 | 0389 | 2 | F | Correction of Service Type assignments | 10.1.1 | 10.2.0 | +| 03/2011 | SP-51 | SP-110062 | 0392 | 1 | A | Clarification on Home eNodeB support | 10.1.1 | 10.2.0 | +| 2012-09 | - | - | - | - | - | Update to Rel-11 version (MCC) | 10.2.0 | 11.0.0 | +| 2012-12 | SP-58 | SP-120711 | 0395 | 2 | A | Continuation of LCS Session in EPS after S1 Connection Release | 11.0.0 | 11.1.0 | +| 2012-12 | SP-58 | SP-120726 | 0396 | 3 | B | Addition of UTDOA technology and SLm interface in LTE | 11.0.0 | 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.1.0 | 11.2.0 | +| 2014-06 | SP-64 | SP-140255 | 0402 | 2 | F | Correction on location reporting in emergency 1xSRVCC | 11.2.0 | 11.3.0 | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23278/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-11/23_series/23278/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf92538fbef296df0d89499ffcb1d96071b6c644 --- /dev/null +++ b/marked/Rel-11/23_series/23278/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5876418df59a7d118c130237d60029f7a563cc24b930386db4ef66cb0776f981 +size 79682 diff --git a/marked/Rel-11/23_series/23278/052543d8c9c0643b05b3ce45c6decca1_img.jpg b/marked/Rel-11/23_series/23278/052543d8c9c0643b05b3ce45c6decca1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..270ca491ea65acd968ed53124e27c0ac23d02d73 --- /dev/null +++ b/marked/Rel-11/23_series/23278/052543d8c9c0643b05b3ce45c6decca1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c166beaad1992e685df66e1140d12048998568c68dc68f170f25a39035225d64 +size 72836 diff --git a/marked/Rel-11/23_series/23278/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-11/23_series/23278/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a4f8ff53111193b5afbd9cb0b2bc4cd1fdec0f0 --- /dev/null +++ b/marked/Rel-11/23_series/23278/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df40ae0d5040338e879f41d598bdfb2c38cbf438205677d687cf06cf793c226d +size 94827 diff --git a/marked/Rel-11/23_series/23278/0b998e3ad8f9d104768642612605cb35_img.jpg b/marked/Rel-11/23_series/23278/0b998e3ad8f9d104768642612605cb35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dad57ab2b0849413428f6047bba26cad6576a60c --- /dev/null +++ b/marked/Rel-11/23_series/23278/0b998e3ad8f9d104768642612605cb35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0923f5c71e99d5a16bff8cd8edd47895ced8e5e1ff81ac88f0c86df8064d9e3f +size 157862 diff --git a/marked/Rel-11/23_series/23278/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/marked/Rel-11/23_series/23278/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f8abfbf6bdd6ad34121918dff3b83bde9c5ebce --- /dev/null +++ b/marked/Rel-11/23_series/23278/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0296e8c9188fcb1e397df57cb78e352a0530a7bd83b06574efd6f7552a1270c8 +size 225971 diff --git a/marked/Rel-11/23_series/23278/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-11/23_series/23278/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c28c9cdc07765ca7a041c80126a221044f54304 --- /dev/null +++ b/marked/Rel-11/23_series/23278/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a69b019c2793a19098dbd0f2ca9cc51250c07b3dc11f436ede7c4e0d7931a347 +size 100374 diff --git a/marked/Rel-11/23_series/23278/0f7871077bba48a2c97f7859a5edda0d_img.jpg b/marked/Rel-11/23_series/23278/0f7871077bba48a2c97f7859a5edda0d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69818ca994d5fc13b9fb61d6107d89483568e4a3 --- /dev/null +++ b/marked/Rel-11/23_series/23278/0f7871077bba48a2c97f7859a5edda0d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6c83c0f744fce7ec29354694a18b0ab0cc6efa6aace4be449649a482a5e1f85 +size 51509 diff --git a/marked/Rel-11/23_series/23278/10b0dda884baae493ad958422d11b552_img.jpg b/marked/Rel-11/23_series/23278/10b0dda884baae493ad958422d11b552_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d75d57ed49c61b4828f50446860247f493558a99 --- /dev/null +++ b/marked/Rel-11/23_series/23278/10b0dda884baae493ad958422d11b552_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ad2276225127fbe342ee5127dbc208e945ec9e86d84c8355d4227c481adcf38 +size 134741 diff --git a/marked/Rel-11/23_series/23278/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/Rel-11/23_series/23278/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf596d152355f87131a810706914e4b10757e187 --- /dev/null +++ b/marked/Rel-11/23_series/23278/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:502dc266c9fc8ec5a31b60d58196e8f65b5f2ee713fa94dd5a9b33ae9a46cd2c +size 97373 diff --git a/marked/Rel-11/23_series/23278/1316d63eca7b84e13c27f55f0027b7b5_img.jpg b/marked/Rel-11/23_series/23278/1316d63eca7b84e13c27f55f0027b7b5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc3d12f2833c2ee36daa2fd8acb21f890ae7f8b9 --- /dev/null +++ b/marked/Rel-11/23_series/23278/1316d63eca7b84e13c27f55f0027b7b5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e63d372a9a74f357f1dfb833e80ec88b910d335ee51734bf003d98f66e000520 +size 40836 diff --git a/marked/Rel-11/23_series/23278/1399c76ef88f22b70d05ed3f781d3c48_img.jpg b/marked/Rel-11/23_series/23278/1399c76ef88f22b70d05ed3f781d3c48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46fc9a9ea0156773baa9b99904ffa67b30ae76b4 --- /dev/null +++ b/marked/Rel-11/23_series/23278/1399c76ef88f22b70d05ed3f781d3c48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4f94d7da36983a79b19d82766a575b6125a0aea807c9fe769d4ad3cca811d38 +size 71208 diff --git a/marked/Rel-11/23_series/23278/17431d8b59408f09df7552d8bdbaa015_img.jpg b/marked/Rel-11/23_series/23278/17431d8b59408f09df7552d8bdbaa015_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15be28322d65d37fae86b5548416403fcb37c157 --- /dev/null +++ b/marked/Rel-11/23_series/23278/17431d8b59408f09df7552d8bdbaa015_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad37a33d77a72cca906547e4f6a17f0dbd4d31828ce6aae0ce5c43547669c676 +size 136873 diff --git a/marked/Rel-11/23_series/23278/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/marked/Rel-11/23_series/23278/18003425d0e8638dde4acc9c5c468c5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45ddac4629324e9a28f1e82dea32070c7617f2c2 --- /dev/null +++ b/marked/Rel-11/23_series/23278/18003425d0e8638dde4acc9c5c468c5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b6c62970c696a22a730d035e36b21127c739129a0daf073ba0ef93e3cc50af7 +size 149908 diff --git a/marked/Rel-11/23_series/23278/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/marked/Rel-11/23_series/23278/1eadbbe42cfcac5c0023577110aec5e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..421b225dee1a2d3ec296224bae6e7ac44af09df4 --- /dev/null +++ b/marked/Rel-11/23_series/23278/1eadbbe42cfcac5c0023577110aec5e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d369b5be9a3ce341fa896b0f38d41b34d80a8fce1e7fbbedfbc3b25b65b847c +size 34459 diff --git a/marked/Rel-11/23_series/23278/20809e79dee38f3d6e03e1ad565a9cf5_img.jpg b/marked/Rel-11/23_series/23278/20809e79dee38f3d6e03e1ad565a9cf5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fffc26c81ad6143b1444f0f630de2cdccd00c3c3 --- /dev/null +++ b/marked/Rel-11/23_series/23278/20809e79dee38f3d6e03e1ad565a9cf5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:619526d2b8162ad9d9921b0015069ddda3992befb918c01e5139047bf7124901 +size 54743 diff --git a/marked/Rel-11/23_series/23278/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg b/marked/Rel-11/23_series/23278/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1eda6ffe83c3b5ef605cbcc4e4e1789575b74b88 --- /dev/null +++ b/marked/Rel-11/23_series/23278/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:452f3fbaedfbdda878e78814e9b79474f3b34f40c45d2410af535c948ef41811 +size 125644 diff --git a/marked/Rel-11/23_series/23278/26e334e61dd059cff029338a2a604d8d_img.jpg b/marked/Rel-11/23_series/23278/26e334e61dd059cff029338a2a604d8d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3acb33f23bfd6884ffd1ec5e1ec13a5635d8b710 --- /dev/null +++ b/marked/Rel-11/23_series/23278/26e334e61dd059cff029338a2a604d8d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c983a87058d09e57084de66d92a26d19763aa853e2f0d708426a53c5c78f2a66 +size 66721 diff --git a/marked/Rel-11/23_series/23278/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-11/23_series/23278/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4bccdfe0fc71d095b74bb0b0982d2babb08c66d --- /dev/null +++ b/marked/Rel-11/23_series/23278/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0306c159a2d9c0a1bebd96bcbafb69c13cbadade5c16fbcfaca30fe542e8aacf +size 138349 diff --git a/marked/Rel-11/23_series/23278/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-11/23_series/23278/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75ff61888a7684a6726919be1d43ff0b47f118e3 --- /dev/null +++ b/marked/Rel-11/23_series/23278/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42dbce8720a567d7bc5cbcdcbbba2af85d2b8cf672f3b17d10b3ed714b2921f7 +size 74916 diff --git a/marked/Rel-11/23_series/23278/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-11/23_series/23278/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b7c26e121567a3982352947fd11a98e19e2b7f9 --- /dev/null +++ b/marked/Rel-11/23_series/23278/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:574da0ac2a9c0e1683906555882b1d48cac90422c7df9841744c665fb25bb6cb +size 81684 diff --git a/marked/Rel-11/23_series/23278/2b00743506f6a3bbd17af764162dc76d_img.jpg b/marked/Rel-11/23_series/23278/2b00743506f6a3bbd17af764162dc76d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..221632abef14d480334bfb925b7c1f768f73122f --- /dev/null +++ b/marked/Rel-11/23_series/23278/2b00743506f6a3bbd17af764162dc76d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9c3e1d387838e88d3862e3e9d6ef9ab0dcc2ab3324961a4f4ef65b7562183f5 +size 84532 diff --git a/marked/Rel-11/23_series/23278/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-11/23_series/23278/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13cc68c8dd57828f499a1ed29dd512472edd43d2 --- /dev/null +++ b/marked/Rel-11/23_series/23278/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f3667202bdca2c082b911eb4f841f9f8fe8ea0f5cc053909f01e067d8af4073 +size 152206 diff --git a/marked/Rel-11/23_series/23278/2f587210e4f97c32758c5972e2e83d20_img.jpg b/marked/Rel-11/23_series/23278/2f587210e4f97c32758c5972e2e83d20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fcf98d3b1f8219d5eee4666defc39d38ea8fa67e --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23278/2fc2e531b3b3c695cca497516ec79f20_img.jpg b/marked/Rel-11/23_series/23278/2fc2e531b3b3c695cca497516ec79f20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f136caedc721327d1cf5602665dc9c5f0ef1204f --- /dev/null +++ b/marked/Rel-11/23_series/23278/2fc2e531b3b3c695cca497516ec79f20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b5fa1d7994566390ce8a7e8a57170ad7b23fc88343a44cf9397f1151b969b87 +size 38400 diff --git a/marked/Rel-11/23_series/23278/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Rel-11/23_series/23278/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..659496e1e0da125f333a562b5bb5e08f7efa9982 --- /dev/null +++ b/marked/Rel-11/23_series/23278/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bddfd94036295af8d5d28f35d75ff688bd12d41acb47e562641a7eee64d73846 +size 93619 diff --git a/marked/Rel-11/23_series/23278/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-11/23_series/23278/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24fb3f6cf6d52c7704a8378c670c75b11f664bdd --- /dev/null +++ b/marked/Rel-11/23_series/23278/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:075a1800a72bc8f8c3740522b5d96a0bda506de9438853d0b6432e05cae53ee1 +size 111798 diff --git a/marked/Rel-11/23_series/23278/3750b0149a6380885998ab3ca6a8787c_img.jpg b/marked/Rel-11/23_series/23278/3750b0149a6380885998ab3ca6a8787c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..254a1957c53be656a77e333cbebb946c176c8081 --- /dev/null +++ b/marked/Rel-11/23_series/23278/3750b0149a6380885998ab3ca6a8787c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aef1306b9226b812f2f4cc4307297489168f9d7bd271c8ac5d10866a690ea7c6 +size 103372 diff --git a/marked/Rel-11/23_series/23278/396197257cf9437b526bb6585b6a9c8a_img.jpg b/marked/Rel-11/23_series/23278/396197257cf9437b526bb6585b6a9c8a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d8c9834b87d53d27369a1ec87927cc7e6b75207 --- /dev/null +++ b/marked/Rel-11/23_series/23278/396197257cf9437b526bb6585b6a9c8a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69f76b70e4116190554692ed9c30ca5acaf739797fb19d25cfcf12434b99ee31 +size 73028 diff --git a/marked/Rel-11/23_series/23278/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-11/23_series/23278/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49f5f9fa6e58c45472d0e2a15a135b5729ffe662 --- /dev/null +++ b/marked/Rel-11/23_series/23278/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9984c383a0c8a70e2751c67d8ceb2c5cdf22482f3102d2dac6180fceafef9fc7 +size 130167 diff --git a/marked/Rel-11/23_series/23278/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-11/23_series/23278/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc9e9953eef978130351321c551bc68270fa5d77 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23278/43837b056625d3d6ce615e4c02f163bb_img.jpg b/marked/Rel-11/23_series/23278/43837b056625d3d6ce615e4c02f163bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2240c78ef10a27e317ebd068f578e2760c46c8e0 --- /dev/null +++ b/marked/Rel-11/23_series/23278/43837b056625d3d6ce615e4c02f163bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b07ed679c931d371a492b624cc6ba2cdd101e26b18df18536db4b7aa4b6ca08c +size 6077 diff --git a/marked/Rel-11/23_series/23278/43979979715bb3304389a0cb18f34444_img.jpg b/marked/Rel-11/23_series/23278/43979979715bb3304389a0cb18f34444_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0396eb2b04d70493dde2ee9f3dc2f49b0789bda2 --- /dev/null +++ b/marked/Rel-11/23_series/23278/43979979715bb3304389a0cb18f34444_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99a57607f7c9c040558e326ce260fbe34bae9ca580bb1df98443f997cf664d98 +size 53019 diff --git a/marked/Rel-11/23_series/23278/4806f9f95fff13a30d6523bd6ffeac63_img.jpg b/marked/Rel-11/23_series/23278/4806f9f95fff13a30d6523bd6ffeac63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a222becb556ded519a46010cd9a558f9be8d761b --- /dev/null +++ b/marked/Rel-11/23_series/23278/4806f9f95fff13a30d6523bd6ffeac63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:faec74d88ced53401c295f3550ac37e3376d64a9c92f5b2a503e8ff98f40e061 +size 132125 diff --git a/marked/Rel-11/23_series/23278/52e112d1ba42a3c660bf62a0fea927d3_img.jpg b/marked/Rel-11/23_series/23278/52e112d1ba42a3c660bf62a0fea927d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adcfa6c95f0cd79cbb0c165475ed1f8950a3347e --- /dev/null +++ b/marked/Rel-11/23_series/23278/52e112d1ba42a3c660bf62a0fea927d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c01e8fae06c6f080d5e9e797b91d0ea82106f1f2158510252b4ec2748e24d8e8 +size 57885 diff --git a/marked/Rel-11/23_series/23278/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-11/23_series/23278/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..845c3ea30bdbfd1e4346fdbd180b60089c2bf9d1 --- /dev/null +++ b/marked/Rel-11/23_series/23278/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d9606ecc7d3003b5ff78625c845c9cb56b95f2c0f0daa85f4ec99deec21f6db +size 100255 diff --git a/marked/Rel-11/23_series/23278/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-11/23_series/23278/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e72a028db80dba40f29d34578f89bcf52436b87 --- /dev/null +++ b/marked/Rel-11/23_series/23278/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98a16a87c8d8a6860a2661eabff7b3df6570d80b9d786cda92a22dae15a6a2f9 +size 140467 diff --git a/marked/Rel-11/23_series/23278/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-11/23_series/23278/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98429021e99088b3f4c8ee604ddbc507c1352dac --- /dev/null +++ b/marked/Rel-11/23_series/23278/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:941a21a37b6772ec2fa9020d4be53a642607c61aee22ef9add034546c7ef62f3 +size 35116 diff --git a/marked/Rel-11/23_series/23278/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/marked/Rel-11/23_series/23278/5cf80bac69830ea773ac17c87e0ae24d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b146d734bcdc6e35759ced6eee1227ffdfce5fa --- /dev/null +++ b/marked/Rel-11/23_series/23278/5cf80bac69830ea773ac17c87e0ae24d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7340a72145826491b71b0b82fcad3d77a9696eada773a5f8687dc468f4228328 +size 64958 diff --git a/marked/Rel-11/23_series/23278/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-11/23_series/23278/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92cc50c3d255fb45bad3cedec6550725d8aa8834 --- /dev/null +++ b/marked/Rel-11/23_series/23278/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8cba4c1c0b4478e2a5de2439fbaa46206fd9da524bbf0f3225f822859db0ebd7 +size 98718 diff --git a/marked/Rel-11/23_series/23278/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-11/23_series/23278/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e87ac6b609fe34e137ef0d532bc5171c935646f7 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23278/69467ece0a576b4c2ec3e0c89ba61527_img.jpg b/marked/Rel-11/23_series/23278/69467ece0a576b4c2ec3e0c89ba61527_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8906e1c94bda7a650ae7bd4cf960a2c2414e1cc6 --- /dev/null +++ b/marked/Rel-11/23_series/23278/69467ece0a576b4c2ec3e0c89ba61527_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97dbdbf6f553ffbfe41612ecbeb94b79dd487933dc11ffaf8901ffada3246be3 +size 166684 diff --git a/marked/Rel-11/23_series/23278/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/marked/Rel-11/23_series/23278/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6afaaa1b754b447ead1544f613511365101aa27d --- /dev/null +++ b/marked/Rel-11/23_series/23278/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32df8231ce38970c3a31bfe44abdf123522d8e16a5d408d6ff6eb311f54c27de +size 110565 diff --git a/marked/Rel-11/23_series/23278/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-11/23_series/23278/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6125a1b1cfd1312f19624c332fbc00a34d35b01e --- /dev/null +++ b/marked/Rel-11/23_series/23278/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82b5996b7d8e5bff63d5a7ae07806188ff6eea93b65e69e5ff52b3a986838012 +size 127726 diff --git a/marked/Rel-11/23_series/23278/6e9d059430baba0c363e33749f68b107_img.jpg b/marked/Rel-11/23_series/23278/6e9d059430baba0c363e33749f68b107_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd4e613a1c57578c9b83a6ebaf236dcec057b146 --- /dev/null +++ b/marked/Rel-11/23_series/23278/6e9d059430baba0c363e33749f68b107_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4be411f8613d08e7cc81b3f2331071522912f45fbc10769f94449539998033a1 +size 114868 diff --git a/marked/Rel-11/23_series/23278/708e4c9a044ef61f586126676eb2eeb8_img.jpg b/marked/Rel-11/23_series/23278/708e4c9a044ef61f586126676eb2eeb8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3995f772d7365e86710e7b7e78afca990777f410 --- /dev/null +++ b/marked/Rel-11/23_series/23278/708e4c9a044ef61f586126676eb2eeb8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23d3081fc15a07b07c5116a41c5f12a9c3e2dba0b592a8ac6e0b7aac5c63e657 +size 56737 diff --git a/marked/Rel-11/23_series/23278/72d448a65347c51989171748789c7d4b_img.jpg b/marked/Rel-11/23_series/23278/72d448a65347c51989171748789c7d4b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9627ee769c73f57da7f5f777c267cd505574b6a2 --- /dev/null +++ b/marked/Rel-11/23_series/23278/72d448a65347c51989171748789c7d4b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df95a76073da1eab920cd04ae79e87eca29d2907dba9f6fecaff58920e2653b2 +size 74264 diff --git a/marked/Rel-11/23_series/23278/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/marked/Rel-11/23_series/23278/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..435b6b519f190ab6581a3718e7147d77741b2abe --- /dev/null +++ b/marked/Rel-11/23_series/23278/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ffad16b7eef276ad8a2d80343d580f6d9e2ea1af26bdc88c1760bc118dc92aa +size 176149 diff --git a/marked/Rel-11/23_series/23278/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-11/23_series/23278/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8a17d2a152a06e8db63e274a550a5c0b9bf925f --- /dev/null +++ b/marked/Rel-11/23_series/23278/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c153d23a85b6ee7cca0ddd4202ba19b27419f30e3bc9f66d73b7e773e19c4eb +size 151087 diff --git a/marked/Rel-11/23_series/23278/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-11/23_series/23278/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..312085c2018ad3c6a6f85d6f2a576255fc33d7e8 --- /dev/null +++ b/marked/Rel-11/23_series/23278/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df019d112d27c983177c565140157f1a05e38562c3331285d44c714dedf57b39 +size 115680 diff --git a/marked/Rel-11/23_series/23278/869c547c11ac7e123c51aba22289f2cd_img.jpg b/marked/Rel-11/23_series/23278/869c547c11ac7e123c51aba22289f2cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e82e501d69f0797d7bdb14b742e73473eaed29a --- /dev/null +++ b/marked/Rel-11/23_series/23278/869c547c11ac7e123c51aba22289f2cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8224941e6283f29f3937a063eb47054f7dd35bbcdaeb5e1a4e072adaef4ef554 +size 56055 diff --git a/marked/Rel-11/23_series/23278/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/marked/Rel-11/23_series/23278/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1ae018692789b65afc5fda7a817dc41f6390711 --- /dev/null +++ b/marked/Rel-11/23_series/23278/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6e65ecd2f6c850a8cbf5716887e8006df6a8e4e847fb1a7eebc925d9a51cbfb +size 54810 diff --git a/marked/Rel-11/23_series/23278/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-11/23_series/23278/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4170eeca2cfbe541e07fafb5c8fd8fed48285712 --- /dev/null +++ b/marked/Rel-11/23_series/23278/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:685ebbca166d6306abc07a54fa333e4670cdbf14810806eb835e0be8ea494a2b +size 101520 diff --git a/marked/Rel-11/23_series/23278/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-11/23_series/23278/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6ce6a6896c687e024b60864425eceef1ec0b86e --- /dev/null +++ b/marked/Rel-11/23_series/23278/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:509cc167cda0b03c50de8043102c25492c8c94fbe9648f2fa5a4686261178507 +size 53339 diff --git a/marked/Rel-11/23_series/23278/91c33f8e1713989e8192322ec2d1212b_img.jpg b/marked/Rel-11/23_series/23278/91c33f8e1713989e8192322ec2d1212b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac73eeb3c59f62ef256740acc8af16b31c2361fd --- /dev/null +++ b/marked/Rel-11/23_series/23278/91c33f8e1713989e8192322ec2d1212b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c32252def78366e197502804210af2985569b4247efa6f3608069c0fe8dab74 +size 60133 diff --git a/marked/Rel-11/23_series/23278/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg b/marked/Rel-11/23_series/23278/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d92faf798d8a190a3306aa78539667cce4f4d91b --- /dev/null +++ b/marked/Rel-11/23_series/23278/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82f5af387edd7ccb9f03859f7b41efa68d0db82ed9bdd12686793a3fb33a4a17 +size 102886 diff --git a/marked/Rel-11/23_series/23278/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-11/23_series/23278/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3281083afc1188f5e3427bf88e247f346f7af8e9 --- /dev/null +++ b/marked/Rel-11/23_series/23278/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cffe7adb7b493b9600612e72f151f26fe71181e39ae0d4052995dbe503407a58 +size 134350 diff --git a/marked/Rel-11/23_series/23278/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg b/marked/Rel-11/23_series/23278/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94e0af704ea226cd34dee62cb665dd437ac3ee91 --- /dev/null +++ b/marked/Rel-11/23_series/23278/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b54b49b2cdbdc1c8d2dd0549ca37fc5180df51b1500d8ec4116db4c9ba9c975c +size 91706 diff --git a/marked/Rel-11/23_series/23278/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg b/marked/Rel-11/23_series/23278/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ee6b4e12cde4c7e970c6a71040f5a50fd3b6590 --- /dev/null +++ b/marked/Rel-11/23_series/23278/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66726f8244968d9ee398151152021ee45c3acfd7b69e5ef632b81a503fc76ce0 +size 184484 diff --git a/marked/Rel-11/23_series/23278/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-11/23_series/23278/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27d8dbfa4ea42c5d2a8997c4e26f4558b524dc88 --- /dev/null +++ b/marked/Rel-11/23_series/23278/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf378a4b5568cd4415d2af5009957a179babe4cd43d1d43408dd142463605178 +size 138220 diff --git a/marked/Rel-11/23_series/23278/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-11/23_series/23278/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..547dfc0785d985b9bfee9eb3937f636573d90266 --- /dev/null +++ b/marked/Rel-11/23_series/23278/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7727363ef316d60859ff603efa839f1f5b8550c291512f3932ca0aefe082e169 +size 104064 diff --git a/marked/Rel-11/23_series/23278/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/Rel-11/23_series/23278/a0739aaf13fa5a632d4faa830f6b2708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f50f238fbb9e99e77de66ae1b264018effd2c9dd --- /dev/null +++ b/marked/Rel-11/23_series/23278/a0739aaf13fa5a632d4faa830f6b2708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e44fa27e6e16b2485be378137e2ab61ffe91e901c7c675058da215632ecfbe09 +size 52016 diff --git a/marked/Rel-11/23_series/23278/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-11/23_series/23278/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad91f279c8fa73e83946003fe3a1706ae7c03aa0 --- /dev/null +++ b/marked/Rel-11/23_series/23278/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b44a0024ace1a70e281e8c4418ee382a6f50b4d4a5c57c29c7353c27b3f3e88c +size 125753 diff --git a/marked/Rel-11/23_series/23278/a5404b7275b06497eecf9b5883604753_img.jpg b/marked/Rel-11/23_series/23278/a5404b7275b06497eecf9b5883604753_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..030eb92d0a01feeee18d7fa77cd684349607fc38 --- /dev/null +++ b/marked/Rel-11/23_series/23278/a5404b7275b06497eecf9b5883604753_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b622e35a17b855fcb60743e65a0e01288afaf790fa081702b1f6c91f8735bd5 +size 145685 diff --git a/marked/Rel-11/23_series/23278/a7450c80e88ad3f6ca1427ad84020998_img.jpg b/marked/Rel-11/23_series/23278/a7450c80e88ad3f6ca1427ad84020998_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2ed136114e2a0cfdb9f54e9fff784c76d59937a --- /dev/null +++ b/marked/Rel-11/23_series/23278/a7450c80e88ad3f6ca1427ad84020998_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce73431162ba8c2059203132de6c3ed4621c2bd7d37b982bf14ceebf835affd6 +size 177718 diff --git a/marked/Rel-11/23_series/23278/a93de4c3f80bd4a972ab65510b09b68d_img.jpg b/marked/Rel-11/23_series/23278/a93de4c3f80bd4a972ab65510b09b68d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8745cd67d5e81cd7159e99f644d690ede2748123 --- /dev/null +++ b/marked/Rel-11/23_series/23278/a93de4c3f80bd4a972ab65510b09b68d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb34887ddfb51b4283ce582358afcafd33a451a10429ff88aaecd432e52ee445 +size 20749 diff --git a/marked/Rel-11/23_series/23278/a963ca41bde1669b18a4b783616f228b_img.jpg b/marked/Rel-11/23_series/23278/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d408b9e6126e88af306f629f26ad227501f0bab --- /dev/null +++ b/marked/Rel-11/23_series/23278/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08d830494c6a5600e9c3a7ff8617c810dc290ef230f72c0c40c99859701742e2 +size 108223 diff --git a/marked/Rel-11/23_series/23278/ad555483986d7170a46ce72d164b5bc8_img.jpg b/marked/Rel-11/23_series/23278/ad555483986d7170a46ce72d164b5bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ba9ccf0e75cad4c4c203d9d73abcaab381eb9c4 --- /dev/null +++ b/marked/Rel-11/23_series/23278/ad555483986d7170a46ce72d164b5bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e7c4d5582f16d1a31b548202d0815073b34a90818778ea8de4c251713552daf +size 64916 diff --git a/marked/Rel-11/23_series/23278/b13465efdac63129aef9b6f1787d0d00_img.jpg b/marked/Rel-11/23_series/23278/b13465efdac63129aef9b6f1787d0d00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1c22b18d8c63c04e09b9abad9e83a4c9d9b21f7 --- /dev/null +++ b/marked/Rel-11/23_series/23278/b13465efdac63129aef9b6f1787d0d00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61c9cd47799a67d5e01ed09359e00b8848b76579366c791913fa501475e22ff0 +size 108977 diff --git a/marked/Rel-11/23_series/23278/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-11/23_series/23278/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f9730fc31edec42249093355431e27edd1472d7 --- /dev/null +++ b/marked/Rel-11/23_series/23278/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f77dc08e8c46bdda72c1fbe84cf5605b1a0d6e3b4a6a801962ab2ca2350254c4 +size 100256 diff --git a/marked/Rel-11/23_series/23278/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg b/marked/Rel-11/23_series/23278/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f69ff0147db94031f6d66afc9174437c65157db8 --- /dev/null +++ b/marked/Rel-11/23_series/23278/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3abc7ed6b5953cf39e44c93d2865cf4eaa6c6742e088c8c68ec87321a75b7504 +size 45733 diff --git a/marked/Rel-11/23_series/23278/b50f38be091844d58b11e3d47bc71e73_img.jpg b/marked/Rel-11/23_series/23278/b50f38be091844d58b11e3d47bc71e73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d1edddc8bc9e2ceac867f9771c432ce34f0a472 --- /dev/null +++ b/marked/Rel-11/23_series/23278/b50f38be091844d58b11e3d47bc71e73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15dec49fccfd7d7ff6cfb35f6554a61014d3c473af5f7a8f9a85720396959100 +size 130856 diff --git a/marked/Rel-11/23_series/23278/b774dfc5023e15e9c352b97ca25a56d4_img.jpg b/marked/Rel-11/23_series/23278/b774dfc5023e15e9c352b97ca25a56d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3731203eb6b877134dd93eb42ae1c2c6ee2fd91d --- /dev/null +++ b/marked/Rel-11/23_series/23278/b774dfc5023e15e9c352b97ca25a56d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39ca1a5c373aaa35e9405519b689b83389f7ca2817f7d91408868ea86fd7a6e4 +size 96945 diff --git a/marked/Rel-11/23_series/23278/b8efedb73292a798b3f2050f9335cae6_img.jpg b/marked/Rel-11/23_series/23278/b8efedb73292a798b3f2050f9335cae6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb34fe2149c70683df393586f08d2230cd2174d0 --- /dev/null +++ b/marked/Rel-11/23_series/23278/b8efedb73292a798b3f2050f9335cae6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6986e8a8b0fbf54fba22c74fd85bd164c0b20a082e244a4745ed9654aafa96c6 +size 20930 diff --git a/marked/Rel-11/23_series/23278/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg b/marked/Rel-11/23_series/23278/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29595fd09832c23c117691eb83c37a7a3faff117 --- /dev/null +++ b/marked/Rel-11/23_series/23278/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:776f36d461ace3b009cd0c54471346d33a97bd6bf7104f5dcd3ac2140c28e26d +size 164553 diff --git a/marked/Rel-11/23_series/23278/bd50d56ae2c12a92466ba2aea1a78040_img.jpg b/marked/Rel-11/23_series/23278/bd50d56ae2c12a92466ba2aea1a78040_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c9c76fe2ea00d97a0a2bf036694c77ada10ff42 --- /dev/null +++ b/marked/Rel-11/23_series/23278/bd50d56ae2c12a92466ba2aea1a78040_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c313ae465d0e456eef915b3a947bd268f0f4d67ed35ade28268970a63c971c63 +size 76775 diff --git a/marked/Rel-11/23_series/23278/beefc2239bc009e7b97963ac4f166db1_img.jpg b/marked/Rel-11/23_series/23278/beefc2239bc009e7b97963ac4f166db1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09985d33a0ba51fa0f64c6905594c9876f870c8d --- /dev/null +++ b/marked/Rel-11/23_series/23278/beefc2239bc009e7b97963ac4f166db1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8cc444a560532da384bc024a448bfd719f747d56cfaac660c2d45a253241a06 +size 28834 diff --git a/marked/Rel-11/23_series/23278/c07e21a8d65991db04263322f859c94f_img.jpg b/marked/Rel-11/23_series/23278/c07e21a8d65991db04263322f859c94f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d1f50a9718ebe8c9f8eca9fa2ebfb28f594c462 --- /dev/null +++ b/marked/Rel-11/23_series/23278/c07e21a8d65991db04263322f859c94f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8107060cacdd90c48ff9b0f7edfc30eb5d1095bc68099556729d0b87edee1ad6 +size 160044 diff --git a/marked/Rel-11/23_series/23278/c0ca823603794512478906b302176bca_img.jpg b/marked/Rel-11/23_series/23278/c0ca823603794512478906b302176bca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fcd3380c24cdf7011071959381c38d27a6965dc6 --- /dev/null +++ b/marked/Rel-11/23_series/23278/c0ca823603794512478906b302176bca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef17c8acdf3a50fda2f5509ec7f4a11d24c3775843c3fe0bc3d87a48c8e38645 +size 161240 diff --git a/marked/Rel-11/23_series/23278/c21bad844b5cb6026c067a1f43ce67c3_img.jpg b/marked/Rel-11/23_series/23278/c21bad844b5cb6026c067a1f43ce67c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb3365af5f756c953b947cb4949decdee04a3963 --- /dev/null +++ b/marked/Rel-11/23_series/23278/c21bad844b5cb6026c067a1f43ce67c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8862c919a617414bedd61c0a055c794cd3264319fd9be355c8ea25996a64fe2c +size 143461 diff --git a/marked/Rel-11/23_series/23278/cc7baa8e5118f4b42c01166637c738ea_img.jpg b/marked/Rel-11/23_series/23278/cc7baa8e5118f4b42c01166637c738ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d30460874672b5e28a8a8d31afb82e866151c38b --- /dev/null +++ b/marked/Rel-11/23_series/23278/cc7baa8e5118f4b42c01166637c738ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98d248eb16e3b3a651288686d78de4f758458b8ce43e9ef455206c4804f684ac +size 66620 diff --git a/marked/Rel-11/23_series/23278/d04c50badc78d5ba47bf4e352af4a754_img.jpg b/marked/Rel-11/23_series/23278/d04c50badc78d5ba47bf4e352af4a754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13160892aa3df592cdcf303ca3b550cedea46a3c --- /dev/null +++ b/marked/Rel-11/23_series/23278/d04c50badc78d5ba47bf4e352af4a754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19b5efc63b1f0c50fe98de32651516709068e78367be40c6e24c899bf1422ff9 +size 105431 diff --git a/marked/Rel-11/23_series/23278/d7948c38a18636aefecdd95388196460_img.jpg b/marked/Rel-11/23_series/23278/d7948c38a18636aefecdd95388196460_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39394de4cb3025a12af555b25fa613775dec7b86 --- /dev/null +++ b/marked/Rel-11/23_series/23278/d7948c38a18636aefecdd95388196460_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8fa1e225b6fdd885f0e535ef56793ae9fcb9cee39652f8531348e2684a8afc6 +size 29612 diff --git a/marked/Rel-11/23_series/23278/da85343976fdbb19f866d9ddbdad0eae_img.jpg b/marked/Rel-11/23_series/23278/da85343976fdbb19f866d9ddbdad0eae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36cb22b33775f81c6d6c66b8cc1ad7557156d6af --- /dev/null +++ b/marked/Rel-11/23_series/23278/da85343976fdbb19f866d9ddbdad0eae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9440694520e2917ca26e89e8118652fb9d51bf3e5a53052d85087ae21f4af472 +size 82611 diff --git a/marked/Rel-11/23_series/23278/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-11/23_series/23278/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d90b43914234dbcc7ec13c8d41c37a35a1ad0105 --- /dev/null +++ b/marked/Rel-11/23_series/23278/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0eccd3e5d34e8c1de2591e43997940311e15338f8d531379f08be5a9f4c30fce +size 151034 diff --git a/marked/Rel-11/23_series/23278/db5deafdae53dbc7d5972957f708c691_img.jpg b/marked/Rel-11/23_series/23278/db5deafdae53dbc7d5972957f708c691_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ed87b9ae6063867c32b97c5eeee036bfc0a8a78 --- /dev/null +++ b/marked/Rel-11/23_series/23278/db5deafdae53dbc7d5972957f708c691_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22ed17664c341dca949b62ada36e7b40d62870d49a7fff08c361dbafa7633b3b +size 48834 diff --git a/marked/Rel-11/23_series/23278/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg b/marked/Rel-11/23_series/23278/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..daa95ed43bb1f6c31e402040c3a6d2762aade874 --- /dev/null +++ b/marked/Rel-11/23_series/23278/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96e34241e62d608d8fd025d940a3361977310194be739f25067f83918be4daa7 +size 83222 diff --git a/marked/Rel-11/23_series/23278/e16bfa31d748f4d99ec4ae3d16656926_img.jpg b/marked/Rel-11/23_series/23278/e16bfa31d748f4d99ec4ae3d16656926_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a69a1112df5f4b50d7394a94a6b0a1c975f225f --- /dev/null +++ b/marked/Rel-11/23_series/23278/e16bfa31d748f4d99ec4ae3d16656926_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0ca6734d59778934fc6cecf109cc44b4bf8a4134fa5e98b50211094c1188a76 +size 246207 diff --git a/marked/Rel-11/23_series/23278/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-11/23_series/23278/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88e843da98c0517a4d1154795ef409a3621c6c75 --- /dev/null +++ b/marked/Rel-11/23_series/23278/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61c873de3018805aea7acdcf4bf4e9cec1e0b2713ecbe49a32343056ebf3d752 +size 54461 diff --git a/marked/Rel-11/23_series/23278/e18841eb4a995df8354a793459e12fd0_img.jpg b/marked/Rel-11/23_series/23278/e18841eb4a995df8354a793459e12fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88693260d8acf1c3d381431ac2d2c4fab29bf36a --- /dev/null +++ b/marked/Rel-11/23_series/23278/e18841eb4a995df8354a793459e12fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c03aaaacb2249290dcb3b8680f1a79ca9fc7b2b1a74fc027b1561b940aceef39 +size 187264 diff --git a/marked/Rel-11/23_series/23278/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-11/23_series/23278/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7883c61b6017f2f925e7572cf51314bce40a104f --- /dev/null +++ b/marked/Rel-11/23_series/23278/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:753cc0f8d4afd5a2ea7f9f56eed3a630b3bd646099b34a72516569fb34f59bbd +size 137578 diff --git a/marked/Rel-11/23_series/23278/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Rel-11/23_series/23278/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43b56945baeaa719fddcdf84fe2381439786ac1b --- /dev/null +++ b/marked/Rel-11/23_series/23278/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a857dafb1ed48ab8174f761eef2d1355e35fa2ddb1720d8adf4438d6fab0cd1e +size 134251 diff --git a/marked/Rel-11/23_series/23278/eabcb2f8b9acedb194571d5bc734b463_img.jpg b/marked/Rel-11/23_series/23278/eabcb2f8b9acedb194571d5bc734b463_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dfba354314c9b938e24fe4cb0994cf2a627b58dd --- /dev/null +++ b/marked/Rel-11/23_series/23278/eabcb2f8b9acedb194571d5bc734b463_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3cd951f05f030d23d09c958ba8fc337076e4a2fd92a57047d7dbf545d76a2dc +size 103479 diff --git a/marked/Rel-11/23_series/23278/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg b/marked/Rel-11/23_series/23278/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae8aff7d6d89cd0a78dcee24c978d7fbcd2dde81 --- /dev/null +++ b/marked/Rel-11/23_series/23278/ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30e19a479aaee669d3f7534d7a657e489748a70326b1d7cb87757106717d044f +size 40759 diff --git a/marked/Rel-11/23_series/23278/ef45b00396c293be0b18d32b97118bf4_img.jpg b/marked/Rel-11/23_series/23278/ef45b00396c293be0b18d32b97118bf4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e19bad30e1df49518952cb1a3e7f11adbf1d154b --- /dev/null +++ b/marked/Rel-11/23_series/23278/ef45b00396c293be0b18d32b97118bf4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32c29394994b55ba45f50fe53826977b6cff15b5858022aae49eb93e3029a14e +size 146622 diff --git a/marked/Rel-11/23_series/23278/f06d7a2fad72d80fe12fca1b65fc805b_img.jpg b/marked/Rel-11/23_series/23278/f06d7a2fad72d80fe12fca1b65fc805b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbc541d669e5a6173994c37765ebd69a8a71b156 --- /dev/null +++ b/marked/Rel-11/23_series/23278/f06d7a2fad72d80fe12fca1b65fc805b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e42fcd47acaa647720d678e6a2ce6dc3dabbba6b6ef8f958d4955dd1814a10d +size 63229 diff --git a/marked/Rel-11/23_series/23278/f61d0925551545b5938b3a4d1bbf63c3_img.jpg b/marked/Rel-11/23_series/23278/f61d0925551545b5938b3a4d1bbf63c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91eda5b18976689cd7b1fc3102884ea952da508a --- /dev/null +++ b/marked/Rel-11/23_series/23278/f61d0925551545b5938b3a4d1bbf63c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed9ba67225164975262ffc51eb8da9975bce93c0c7ceb0c34bc58b7ea0131865 +size 125639 diff --git a/marked/Rel-11/23_series/23278/fc3e2b49a9f850951570e502393b697f_img.jpg b/marked/Rel-11/23_series/23278/fc3e2b49a9f850951570e502393b697f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d854c9ba4b0d4592abcb364919cde072bbe2a87 --- /dev/null +++ b/marked/Rel-11/23_series/23278/fc3e2b49a9f850951570e502393b697f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad2b4e5046a3e839dae9b0f62f7c89113a164d4a760f12d8fb8d3a4c96f3ae4b +size 82757 diff --git a/marked/Rel-11/23_series/23278/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Rel-11/23_series/23278/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..946610d67d412501504bf9cd424748f2d8b54e1c --- /dev/null +++ b/marked/Rel-11/23_series/23278/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bcde1b9bbb8201b9d32aa1027984a2747b59f6a5763cfa0ceb310da60dea69c +size 123661 diff --git a/marked/Rel-11/23_series/23278/fd76efce549d3713543bb5ed9b023c2e_img.jpg b/marked/Rel-11/23_series/23278/fd76efce549d3713543bb5ed9b023c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..032a8460c6bc6218e668809b14bbd40484dc9978 --- /dev/null +++ b/marked/Rel-11/23_series/23278/fd76efce549d3713543bb5ed9b023c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e235247d8ef80d25408d97410d57cf83791c0816e01928045923063837c97a71 +size 72878 diff --git a/marked/Rel-11/23_series/23278/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg b/marked/Rel-11/23_series/23278/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51367e931183dd37982ad195f021a2665e3be197 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23278/ffe0fef452a0ae9a20253c319c54e13c_img.jpg b/marked/Rel-11/23_series/23278/ffe0fef452a0ae9a20253c319c54e13c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42f2ee79ce8c9df3a7891eec19aa5ae04d0fabd1 --- /dev/null +++ b/marked/Rel-11/23_series/23278/ffe0fef452a0ae9a20253c319c54e13c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75c16d493cbec533c79ac6be7e524531853a370d79271afa9fde431f9ba17ef3 +size 118640 diff --git a/marked/Rel-11/23_series/23278/raw.md b/marked/Rel-11/23_series/23278/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..156551fdc86f67dc5057093dec670c063ce02d89 --- /dev/null +++ b/marked/Rel-11/23_series/23278/raw.md @@ -0,0 +1,4940 @@ + + + + + + +# Contents + +| | | +|----------------------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions and abbreviations ..... | 9 | +| 3.1 Definitions..... | 9 | +| 3.2 Abbreviations ..... | 9 | +| 4 CAMEL/IP Multimedia Core Network Interworking..... | 10 | +| 4.1 Architecture..... | 10 | +| 4.1.1 Functional Entities used for CAMEL at IP Multimedia Registration ..... | 10 | +| 4.1.2 Functional Entities used for CAMEL for MO and MT IP Multimedia session ..... | 11 | +| 4.2 Interfaces defined for an IM-SSF based Application Server ..... | 11 | +| 4.2.1 CSCF – IM-SSF interface ..... | 11 | +| 4.2.2 IM-SSF - gsmSCF interface ..... | 11 | +| 4.2.3 HSS – IM-SSF interface..... | 11 | +| 4.3 Detection Points (DPs)..... | 11 | +| 4.3.1 Arming/Disarming mechanism ..... | 12 | +| 4.3.2 Criteria ..... | 12 | +| 4.3.2.1 Criteria at Collected_Info ..... | 13 | +| 4.3.2.2 Criteria at DP Analysed_Information ..... | 13 | +| 4.3.2.2.1 General ..... | 13 | +| 4.3.2.2.2 Number comparison ..... | 14 | +| 4.3.2.3 Criteria at DP Route_Select_Failure..... | 14 | +| 4.3.2.4 Criteria at DP T_Busy and T_No_Answer ..... | 15 | +| 4.4 Description of CAMEL Subscriber Data ..... | 15 | +| 4.4.1 IP Multimedia CAMEL Subscription Information (IM-CSI) ..... | 15 | +| 4.4.1.1 Originating IP Multimedia CAMEL Subscription Information (O-IM-CSI) ..... | 15 | +| 4.4.1.1.1 gsmSCF Address..... | 15 | +| 4.4.1.1.2 Service Key ..... | 15 | +| 4.4.1.1.3 Default Call Handling ..... | 15 | +| 4.4.1.1.4 TDP List..... | 15 | +| 4.4.1.1.5 CAMEL Capability Handling ..... | 15 | +| 4.4.1.1.6 CSI Status..... | 15 | +| 4.4.1.1.7 Notification Flag ..... | 15 | +| 4.4.1.1.8 DP Criteria..... | 16 | +| 4.4.1.2 Dialled Services IP Multimedia CAMEL Subscription Information (D-IM-CSI) ..... | 16 | +| 4.4.1.2.1 gsmSCF Address..... | 16 | +| 4.4.1.2.2 Service Key ..... | 16 | +| 4.4.1.2.3 Default Call Handling ..... | 16 | +| 4.4.1.2.4 CAMEL Capability Handling ..... | 16 | +| 4.4.1.2.5 CSI Status..... | 16 | +| 4.4.1.2.6 Notification Flag ..... | 16 | +| 4.4.1.2.7 DP Criteria..... | 16 | +| 4.4.1.3 Terminating IP Multimedia CAMEL Subscription Information (VT-IM-CSI) ..... | 16 | +| 4.4.1.3.1 gsmSCF Address..... | 16 | +| 4.4.1.3.2 Service Key ..... | 16 | +| 4.4.1.3.3 Default Call Handling ..... | 16 | +| 4.4.1.3.4 TDP List..... | 16 | +| 4.4.1.3.5 CAMEL Capability Handling ..... | 17 | +| 4.4.1.3.6 CSI Status..... | 17 | +| 4.4.1.3.7 Notification Flag ..... | 17 | +| 4.4.1.3.8 DP Criteria..... | 17 | +| 4.4.1.4 Other CAMEL Data..... | 17 | +| 4.4.1.4.1 gsmSCF address list for CSI ..... | 17 | +| 4.5 Description of CAMEL State Models..... | 17 | +| 4.5.1 General Handling..... | 17 | +| 4.5.2 Originating CAMEL Basic Call State Model (O-IM-BCSM) ..... | 18 | + +| | | | +|-----------|---------------------------------------------------------------------------------------|-----| +| 4.5.2.1 | Description of the O-IM-BCSM ..... | 18 | +| 4.5.2.2 | Description of Points In Call ..... | 19 | +| 4.5.2.2.1 | O_Null & Authorise_Origination_Attempt_Collect_Info ..... | 19 | +| 4.5.2.2.2 | Analyse_Information..... | 20 | +| 4.5.2.2.3 | Routing and Alerting..... | 20 | +| 4.5.2.2.4 | O_Active ..... | 20 | +| 4.5.2.2.5 | O_Exception..... | 21 | +| 4.5.3 | Mapping of SIP Method/Response to O-IM-BCSM Detection Points ..... | 21 | +| 4.5.4 | Terminating CAMEL Basic Call State Model (T-IM-BCSM)..... | 22 | +| 4.5.4.1 | Description of the T-IM-BCSM ..... | 22 | +| 4.5.4.2 | Description of Points In Call ..... | 23 | +| 4.5.4.2.1 | T_Null ..... | 23 | +| 4.5.4.2.2 | Terminating Call Handling..... | 23 | +| 4.5.4.2.3 | T_Active..... | 24 | +| 4.5.4.2.4 | T_Exception ..... | 24 | +| 4.5.5 | Mapping of SIP Method/Response to T-IM-BCSM Detection Points ..... | 25 | +| 4.6 | Procedures for IM-SSF Application Server ..... | 25 | +| 4.6.1 | Overall SDL Architecture..... | 26 | +| 4.6.1.1 | Handling of Registration and De-registration in the IM-SSF ..... | 27 | +| 4.6.1.1.1 | Procedure CAMEL_IMCN_Register..... | 27 | +| 4.6.1.2 | Handling of Notify Subscriber Data Change ..... | 30 | +| 4.6.1.3 | Handling of Mobile Originated Calls in the IM-SSF ..... | 33 | +| 4.6.1.3.1 | Actions of the IM-SSF on receipt of Int_Error ..... | 33 | +| 4.6.1.3.2 | Actions of the IM-SSF on receipt of Int_Continue ..... | 33 | +| 4.6.1.3.3 | Actions of the IM-SSF on receipt of Int_Continue_With_Argument..... | 33 | +| 4.6.1.3.4 | Actions of the IM-SSF on receipt of Int_Connect ..... | 33 | +| 4.6.1.3.5 | Actions of the IM-SSF on receipt of Int_Release_Call..... | 33 | +| 4.6.1.3.6 | Handling of procedure CAMEL_OCH_CTR, sheet 1 ..... | 33 | +| 4.6.1.3.7 | Handling of procedure CAMEL_OCH_CTR, sheet 5 ..... | 34 | +| 4.6.1.3.8 | Receipt of 100 Trying Provisional Response (Process MO_IM_SSF) ..... | 34 | +| 4.6.1.3.9 | Handling of internal timers in Process MO_IM_SSF ..... | 34 | +| 4.6.1.4 | Handling of Mobile Terminated IP Multimedia sessions in the IM-SSF ..... | 64 | +| 4.6.1.4.1 | Actions of the IM-SSF on receipt of Int_Error ..... | 64 | +| 4.6.1.4.2 | Actions of the IM-SSF on receipt of Int_Release_Call..... | 64 | +| 4.6.1.4.3 | Actions of the IM-SSF on receipt of Int_Continue_With_Argument..... | 64 | +| 4.6.1.4.4 | Actions of IM-SSF in procedure CAMEL_IMCN_MT_INVITE for Unregistered Subscriber ..... | 64 | +| 4.6.1.4.5 | Handling of procedure CAMEL_MT_CTR, sheet 1 ..... | 64 | +| 4.6.1.4.6 | Handling of procedure CAMEL_MT_CTR, sheet 5..... | 65 | +| 4.6.1.4.7 | Receipt of 100 Trying Provisional Response (Process MT_IM_SSF) ..... | 65 | +| 4.6.1.4.8 | Handling of internal timers in Process MT_IM_SSF..... | 65 | +| 4.6.1.5 | Handling of call in the imcnSSF ..... | 95 | +| 4.6.1.5.1 | Process imcnSSF ..... | 95 | +| 4.6.1.6 | Process imcn_SSME_SSF and procedures..... | 126 | +| 4.7 | Descriptions of information Flows..... | 129 | +| 4.7.1 | IM-SSF to gsmSCF information flows..... | 129 | +| 4.7.1.1 | Activity Test ack..... | 129 | +| 4.7.1.1.1 | Description ..... | 129 | +| 4.7.1.1.2 | Information Elements..... | 129 | +| 4.7.1.2 | Apply Charging Report..... | 129 | +| 4.7.1.2.1 | Description ..... | 129 | +| 4.7.1.2.2 | Information Elements..... | 129 | +| 4.7.1.3 | Call Gap ..... | 131 | +| 4.7.1.3.1 | Description ..... | 131 | +| 4.7.1.3.2 | Information Elements..... | 131 | +| 4.7.1.4 | Call Information Report..... | 133 | +| 4.7.1.4.1 | Description ..... | 133 | +| 4.7.1.4.2 | Information Elements..... | 133 | +| 4.7.1.5 | Event Report BCSM ..... | 133 | +| 4.7.1.5.1 | Description ..... | 133 | +| 4.7.1.5.2 | Information Elements..... | 133 | +| 4.7.1.6 | Initial DP..... | 134 | +| 4.7.1.6.1 | Description ..... | 134 | + +| | | | +|------------|---------------------------------------------------------------------|-----| +| 4.7.1.6.2 | Information Elements..... | 135 | +| 4.7.1.7 | Specialized Resource Report..... | 136 | +| 4.7.1.7.1 | Description..... | 136 | +| 4.7.1.7.2 | Information Elements..... | 136 | +| 4.7.2 | gsmSCF to IM-SSF information flows..... | 137 | +| 4.7.2.1 | Activity Test..... | 137 | +| 4.7.2.1.1 | Description..... | 137 | +| 4.7.2.1.2 | Information Elements..... | 137 | +| 4.7.2.2 | Apply Charging..... | 137 | +| 4.7.2.2.1 | Description..... | 137 | +| 4.7.2.2.2 | Information Elements..... | 137 | +| 4.7.2.3 | Call Information Request..... | 138 | +| 4.7.2.3.1 | Description..... | 138 | +| 4.7.2.3.2 | Information Elements..... | 138 | +| 4.7.2.4 | Cancel..... | 138 | +| 4.7.2.4.1 | Description..... | 138 | +| 4.7.2.4.2 | Information Elements..... | 138 | +| 4.7.2.5 | Connect..... | 139 | +| 4.7.2.5.1 | Description..... | 139 | +| 4.7.2.5.2 | Information Elements..... | 139 | +| 4.7.2.6 | Connect To Resource..... | 139 | +| 4.7.2.6.1 | Description..... | 139 | +| 4.7.2.6.2 | Information Elements..... | 139 | +| 4.7.2.7 | Continue..... | 139 | +| 4.7.2.7.1 | Description..... | 139 | +| 4.7.2.7.2 | Information Elements..... | 139 | +| 4.7.2.8 | Continue With Argument..... | 140 | +| 4.7.2.8.1 | Description..... | 140 | +| 4.7.2.8.2 | Information Elements..... | 140 | +| 4.7.2.9 | Disconnect Forward Connection..... | 140 | +| 4.7.2.9.1 | Description..... | 140 | +| 4.7.2.9.2 | Information Elements..... | 140 | +| 4.7.2.10 | Furnish Charging Information..... | 140 | +| 4.7.2.10.1 | Description..... | 140 | +| 4.7.2.10.2 | Information Elements..... | 140 | +| 4.7.2.11 | Release Call..... | 141 | +| 4.7.2.11.1 | Description..... | 141 | +| 4.7.2.11.2 | Information Elements..... | 141 | +| 4.7.2.12 | Request Report BCSM Event..... | 141 | +| 4.7.2.12.1 | Description..... | 141 | +| 4.7.2.12.2 | Information Elements..... | 141 | +| 4.7.2.13 | Reset Timer..... | 142 | +| 4.7.2.13.1 | Description..... | 142 | +| 4.7.2.13.2 | Information Elements..... | 142 | +| 4.7.3 | gsmSCF – IM-SSF information flows for MRFC related operations..... | 142 | +| 4.7.3.1 | Cancel..... | 142 | +| 4.7.3.1.1 | Description..... | 142 | +| 4.7.3.1.2 | Information Elements..... | 143 | +| 4.7.3.2 | Play Announcement..... | 143 | +| 4.7.3.2.1 | Description..... | 143 | +| 4.7.3.2.2 | Information Elements..... | 143 | +| 4.7.3.3 | Prompt And Collect User Information (received information)..... | 144 | +| 4.7.3.3.1 | Description..... | 144 | +| 4.7.3.3.2 | Information Elements..... | 144 | +| 4.7.3.4 | Prompt And Collect User Information ack (received information)..... | 145 | +| 4.7.3.4.1 | Description..... | 145 | +| 4.7.3.4.2 | Information Elements..... | 145 | +| 4.7.3.5 | Specialized Resource Report..... | 146 | +| 4.7.3.5.1 | Description..... | 146 | +| 4.7.3.5.2 | Information Elements..... | 146 | +| 4.7.4 | IM-SSF to HSS information flows..... | 146 | +| 4.7.4.1 | Any Time Subscription Interrogation request..... | 146 | + +| | | | +|------------------------|------------------------------------------------------|-----| +| 4.7.4.1.1 | Description ..... | 146 | +| 4.7.4.1.2 | Information Elements ..... | 146 | +| 4.7.4.2 | Notify Subscriber Data Change ack..... | 146 | +| 4.7.4.2.1 | Description ..... | 146 | +| 4.7.4.2.2 | Information Elements ..... | 146 | +| 4.7.5 | HSS to IM-SSF information flows ..... | 146 | +| 4.7.5.1 | Any Time Subscription Interrogation ack ..... | 146 | +| 4.7.5.1.1 | Description ..... | 146 | +| 4.7.5.1.2 | Information Elements ..... | 147 | +| 4.7.5.2 | Notify Subscriber Data Change ..... | 147 | +| 4.7.5.2.1 | Description ..... | 147 | +| 4.7.5.2.2 | Information Elements ..... | 147 | +| 5 | Control and interrogation of subscription data ..... | 148 | +| 5.1 | Architecture ..... | 148 | +| 5.2 | Procedures for CAMEL ..... | 148 | +| 5.2.1 | Any Time Subscription Interrogation..... | 148 | +| 5.2.2 | Any Time Modification..... | 148 | +| 5.2.3 | Notify Subscriber Data Change..... | 148 | +| 5.3 | Description of information flows ..... | 148 | +| 5.3.1 | gsmSCF to HSS information flows ..... | 149 | +| 5.3.1.1 | Any Time Modification Request ..... | 149 | +| 5.3.1.1.1 | Description ..... | 149 | +| 5.3.1.2 | Any Time Subscription Interrogation Request ..... | 149 | +| 5.3.1.2.1 | Description ..... | 149 | +| 5.3.1.2.2 | Information Elements ..... | 149 | +| 5.3.1.3 | Notify Subscriber Data Change response ..... | 149 | +| 5.3.1.3.1 | Description ..... | 149 | +| 5.3.2 | HSS to gsmSCF information flows ..... | 149 | +| 5.3.2.1 | Any Time Modification ack..... | 149 | +| 5.3.2.1.1 | Description ..... | 149 | +| 5.3.2.1.2 | Information Elements ..... | 149 | +| 5.3.2.2 | Any Time Subscription Interrogation ack ..... | 150 | +| 5.3.2.2.1 | Description ..... | 150 | +| 5.3.2.2.2 | Information Elements ..... | 150 | +| 5.3.2.3 | Notify Subscriber Data Change ..... | 150 | +| 5.3.2.3.1 | Description ..... | 150 | +| 5.3.2.3.2 | Information Elements ..... | 150 | +| 6 | Subscriber Location and State retrieval ..... | 150 | +| 6.1 | Architecture ..... | 150 | +| 6.2 | Procedures for CAMEL ..... | 150 | +| 6.2.1 | Any Time Interrogation..... | 150 | +| 6.3 | Description of information flows ..... | 151 | +| 6.3.1 | gsmSCF to HSS information flows ..... | 151 | +| 6.3.1.1 | Any Time Interrogation Request ..... | 151 | +| 6.3.1.1.1 | Description ..... | 151 | +| 6.3.2 | HSS to gsmSCF information flows ..... | 151 | +| 6.3.2.1 | Any Time Interrogation ack..... | 151 | +| 6.3.2.1.1 | Description ..... | 151 | +| Annex A (informative): | Change history..... | 152 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document specifies the stage 2 description for the fourth phase (see 3GPP TS 22.078 [2]) of the Customized Applications for Mobile network Enhanced Logic (CAMEL) feature 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 specifies the stage 2 description for the Customized Applications for Mobile network Enhanced Logic (CAMEL) feature which provides the mechanisms to support services for the IP Multimedia Core Network (IM CN) Subsystem. + +# --- 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: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.078: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Customised Applications for Mobile network Enhanced Logic (CAMEL); Service description, Stage 1". +- [3] 3GPP TS 22.228: "3rd Generation Partnership Project; Technical Specification Group Systems Aspects; IP Multimedia (IM) Subsystem –Stage 1". +- [4] 3GPP TS 23.078: "3rd Generation Partnership Project; Technical Specification Group Core Networks; Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 3 Stage 2 specification (Release 99)". +- [5] 3GPP TS 23.218: "3rd Generation Partnership Project; Technical Specification Group Core Networks; IP Multimedia (IM) Session Handling; IP Multimedia Call Model. +- [6] 3GPP TS 23.228: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS) Stage 2". +- [7] Void +- [8] 3GPP TS 24.229: "3rd Generation Partnership Project; Technical Specification Group Core Networks; IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3". +- [9] 3GPP TS 29.002: "3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile Application Part (MAP) specification". +- [10] 3GPP TS 29.229: "3rd Generation Partnership Project; Technical Specification Group Core Networks; Cx and Dx Interfaces Based on the Diameter Protocol; Protocol details". +- [11] 3GPP TS 29.278: "3rd Generation Partnership Project; Technical Specification Group Core Network; Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4 CAMEL Application Part (CAP) specification for IP Multimedia Subsystems (IMS)". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +**Home Subscriber Server (HSS):** Functional entity containing the subscription related information to support the network entities actually handling calls/sessions. For subscribers requiring CAMEL support, the HSS includes some + +functionality that was present in the HLR in previous 3GPP releases for storing the information relevant to the current subscription regarding CAMEL Subscription Information for IMS. The HSS sends IM CAMEL Subscription Information data to the IM-SSF and CSE using a MAP interface. + +**IP Multimedia Service Switching Function (IM-SSF):** CAMEL functional entity that provides the interworking between SIP session control and the CAMEL state models. The IM-SSF also provides the CAMEL interface to HSS for downloading the subscriber's CAMEL Subscription Information data for IMS. + +**IP Multimedia Basic Call State Model (IM-BCSM):** IM-BCSM provides a high-level model of CSCF activities required to establish and maintain communication paths for users. As such, it identifies a set of basic call activities in a CSCF and shows how these activities are joined together to process a basic call. + +**IP Multimedia CAMEL Subscription Information (IM-CSI):** IM-CSI identifies the subscriber as having IP Multimedia CAMEL services. + +**IP Multimedia session:** IP Multimedia session and IP Multimedia call are treated as equivalent in this specification. + +**Originating IP Multimedia Basic Call State Model (O-IM-BCSM):** originating half of the IM-BCSM. The O-IM-BCSM corresponds to that portion of the IM-BCSM associated with the originating party. + +**Originating IP Multimedia CAMEL Subscription Information (O-IM-CSI):** O-IM-CSI identifies the subscriber as having originating IP Multimedia CAMEL services. + +**Terminating IP Multimedia Basic Call State Model (T-IM-BCSM):** terminating half of the IM-BCSM. The T-IM-BCSM corresponds to that portion of the IM-BCSM associated with the terminating party. + +**Terminating IP Multimedia CAMEL Subscription Information (T-IM-CSI):** T-IM-CSI identifies the subscriber as having terminating IP Multimedia CAMEL services. + +## 3.2 Abbreviations + +Abbreviations used in the present document are listed in 3GPP TR 21.905 [1]. + +For the purposes of the present document, the following abbreviations apply: + +| | | +|----------|--------------------------------------------------------------| +| BCSM | Basic Call State Model | +| CAMEL | Customized Applications for Mobile network Enhanced Logic | +| CAP | CAMEL Application Part | +| CSCF | Call State Control Function | +| DP | Detection Point | +| D-IM-CSI | Dialled Service IP Multimedia CAMEL Subscription Information | +| EDP | Event Detection Point | +| FTN | Forwarded To Number | +| GPRS | General Packet Radio Service | +| gsmSCF | GSM Service Control Function | +| gsmSRF | GSM Specialised Resource Function | +| gsmSSF | GSM Service Switching Function | +| HPLMN | Home PLMN | +| HSS | Home Subscriber Server | +| IE | Information Element | +| IF | Information Flow | +| IP | Internet Protocol | +| ISC | IM-CN Service Control | +| I-CSCF | Interrogating CSCF | +| IM | IP Multimedia | +| IM-BCSM | IP Multimedia Basic Call State Model | +| IMCN | IP Multimedia Core Network | +| imenSSF | IM CN Service Switching Function | +| IM-CSI | IP Multimedia CAMEL Subscription Information | +| IM-SSF | IP Multimedia Service Switching Function | +| IPLMN | Interrogating PLMN | +| MGCF | Media Gateway Control Function | +| MO | Mobile Originating | +| MT | Mobile Terminating | + +| | | +|-----------|----------------------------------------------------------| +| NNI | Network Node Interface | +| O-IM-BCSM | Originating IP Multimedia Basic Call State Model | +| O-IM-CSI | Originating IP Multimedia CAMEL Subscription Information | +| PIC | Point In Call | +| PLMN | Public Land Mobile Network | +| P-CSCF | Proxy CSCF | +| SIP | Session Initiation Protocol | +| S-CSCF | Serving CSCF | +| SSME | Service Switching Function Management Entity | +| T-IM-BCSM | Terminating IP Multimedia Basic Call State Model | +| VT-IM-CSI | Terminating IP Multimedia CAMEL Subscription Information | +| TDP | Trigger Detection Point | +| UNI | User Network Interface | +| VPLMN | Visited PLMN | + +# 4 CAMEL/IP Multimedia Core Network Interworking + +## 4.1 Architecture + +This subclause describes the functional architecture needed to support CAMEL interactions with the S-CSCF in the IP Multimedia Subsystem. The IM-SSF is a SIP Application Server that interfaces SIP to CAP. The generic SIP Application Server behaviour of the IM-SSF is specified in 3GPP TS 23.218 [5]. + +### 4.1.1 Functional Entities used for CAMEL at IP Multimedia Registration + +Figure 4.1 shows the functional entities involved when an MS registers for IP Multimedia session requiring CAMEL support. General registration procedure is detailed in 3GPP TS 23.228 [6]. Upon notification of a UE's registration, the IM-SSF requests O-IM-CSI, D-IM-CSI, VT-IM-CSI data from the HSS over the Si interface. + +![Figure 4.1: Functional architecture for support of CAMEL when mobile registers for IP Multimedia session. The diagram shows the Home Network containing HSS, IM-SSF, and S-CSCF, and the Interrogating Network containing the MS. Interfaces shown are Cx, Si, and ISC.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg) + +The diagram illustrates the functional architecture for CAMEL support during IP Multimedia registration. It is divided into two main areas by a dashed line: the 'Home Network' (top) and the 'Interrogating Network' (bottom). In the Home Network, there are three functional entities: HSS (Home Subscriber Server), IM-SSF (IP Multimedia Subsystem Service Function), and S-CSCF (Serving CSCF). The HSS is connected to the IM-SSF via a 'Si Interface'. The IM-SSF is connected to the S-CSCF via an 'ISC Interface'. The S-CSCF is connected to the HSS via a 'Cx Interface'. In the Interrogating Network, there is an 'MS' (Mobile Station) which is connected to the S-CSCF. The S-CSCF is also connected to the HSS via the Cx Interface. + +Figure 4.1: Functional architecture for support of CAMEL when mobile registers for IP Multimedia session. The diagram shows the Home Network containing HSS, IM-SSF, and S-CSCF, and the Interrogating Network containing the MS. Interfaces shown are Cx, Si, and ISC. + +Figure 4.1: Functional architecture for support of CAMEL when mobile registers for IP Multimedia session + +### 4.1.2 Functional Entities used for CAMEL for MO and MT IP Multimedia session + +Figure 4.2 shows the functional entities involved in a Mobile Originated IP Multimedia session requiring CAMEL support. The same functional architecture applies in a Mobile Terminated IP Multimedia session for CAMEL. + +![Figure 4.2: Functional architecture for support of CAMEL control of a MO IP Multimedia session. The diagram shows a 'Home Network' containing HSS, gsmSCF, and IM-SSF. The HSS is connected to the gsmSCF via a MAP interface and to the IM-SSF via a Si interface. The gsmSCF is connected to the IM-SSF via a CAP interface. The IM-SSF is connected to an S-CSCF via an ISC Interface. The S-CSCF is located in an 'Interrogating Network' (indicated by a dashed line) and is connected to an MS (Mobile Station).](5a4e62bead259c258d069fd3663ea670_img.jpg) + +Figure 4.2: Functional architecture for support of CAMEL control of a MO IP Multimedia session. The diagram shows a 'Home Network' containing HSS, gsmSCF, and IM-SSF. The HSS is connected to the gsmSCF via a MAP interface and to the IM-SSF via a Si interface. The gsmSCF is connected to the IM-SSF via a CAP interface. The IM-SSF is connected to an S-CSCF via an ISC Interface. The S-CSCF is located in an 'Interrogating Network' (indicated by a dashed line) and is connected to an MS (Mobile Station). + +Figure 4.2: Functional architecture for support of CAMEL control of a MO IP Multimedia session + +## 4.2 Interfaces defined for an IM-SSF based Application Server + +### 4.2.1 CSCF – IM-SSF interface + +This interface is the IP Multimedia Service Control interface (ISC). This interface shall be based on SIP as detailed in 3GPP TS 24.229 [8]. + +### 4.2.2 IM-SSF - gsmSCF interface + +This interface is used by the gsmSCF to control an IP Multimedia session in a certain IM-SSF. Relationships between the IM-SSF and the gsmSCF on this interface are opened as a result of the IM-SSF sending a request for instructions to the gsmSCF. This interface shall be based on 3GPP TS 29.278 [11]. + +### 4.2.3 HSS – IM-SSF interface + +This interface is the Si interface and is used to send CAMEL related subscriber data to the IM-SSF, e.g. IM-CSI. This interface shall be a MAP interface as described in 3GPP TS 29.002 [9]. + +## 4.3 Detection Points (DPs) + +Certain basic call events may be visible to the GSM Service Control Function (gsmSCF). The DPs are the points in call at which these events are detected. + +A DP can be armed in order to notify the gsmSCF that the DP was encountered, and potentially to allow the gsmSCF to influence subsequent handling of the call. If the DP is not armed, the processing entity continues the processing without gsmSCF involvement. + +Three different types of DPs are identified: + +- Trigger Detection Point - Request (TDP-R). + +This detection point is statically armed and initiates a CAMEL control relationship when encountered and there is no existing relationship due to the same CSI. Processing is suspended when the DP is encountered. + +- Event Detection Point - Request (EDP-R). + +This detection point is dynamically armed within the context of a CAMEL control relationship. Processing is suspended when encountering the DP and the IM-SSF waits for instructions from the gsmSCF. + +- Event Detection Point - Notification (EDP-N). + +This detection point is dynamically armed within the context of a CAMEL control relationship. Processing is not suspended when encountering the DP. + +The DPs are characterized in the following clauses. + +### 4.3.1 Arming/Disarming mechanism + +A DP may be statically armed or dynamically armed. + +The following arming rules apply: + +- DP for a mobile originating call handling is statically armed in the IM-SSF as a result of O-IM-CSI and D-IM-CSI data delivery from the HSS. Likewise, DP for mobile terminating call handling is statically armed in the IM-SSF as a result of VT-IM-CSI data delivery from the HSS. Static arming of DPs in the IM-SSF occurs during the UE's registration in the IMS CN. Basically, when the IM-SSF is notified of the UE's initial registration, the IM-SSF queries the HSS for the subscriber's CAMEL Subscription Information via the Si interface. +- A DP is dynamically armed by the gsmSCF within the context of a CAMEL control relationship as a result of IM-SSF receiving the RequestReportBCSMEVENT operation. +- A Request Report BCSM Event information flow for a detection point for a leg overwrites any previous Request Report BCSM Event information flow for that detection point for that leg. + +The following disarming rules apply: + +- A statically armed DP is disarmed when the IP Multimedia CSI data is withdrawn in the HSS. Only TDP-Rs can be disarmed using this mechanism. +- If an armed EDP is met, then it is disarmed. +- If an EDP is met that causes the release of the related leg, then all EDPs related to that leg are disarmed. +- If a call session is released, then all EDPs related to that call session are disarmed. +- If an EDP is met, then other EDPs are disarmed, in accordance with the implicit disarming rule table specified in TS 23.078 Rel-99 4 (refer to the section for "Rules for Implicit Disarming of Event Detection Points"). + +If an EDP is armed, it can be explicitly disarmed by the gsmSCF by means of the RequestReportBCSMEVENT information flow. + +### 4.3.2 Criteria + +Criteria are the conditions that must be met in order for the IM-SSF to request instructions from the gsmSCF. + +DP criteria are checked in the IM-SSF. Criteria for originating DPs (i.e. Collected\_Info, Analysed\_Information, and Route\_Select\_Failure TDPs) are checked in the IM-SSF associated with the originating UE's S-CSCF. Criteria for terminating DPs (i.e. T\_Busy and T\_No\_Answer) are checked in the IM-SSF associated with the terminating UE's S-CSCF. + +Based on the Initial Filter Criteria information, the S-CSCF forwards the SIP message to the IM-SSF. The DP encountered is identified based on the SIP message received from the S-CSCF. Refer to table 4.2 and table 4.4 for mapping of SIP messages to CAMEL IM-BCSM Detection Points. + +#### 4.3.2.1 Criteria at Collected\_Info + +The following criteria are applicable for DP Collected\_Info: + +- Destination number triggering criterion: The HSS may store a list of up to 10 destination numbers and/or up to 3 number lengths. There is no restriction on the nature of address. There is no restriction on the numbering plan indicator. This criterion may be defined to be either "enabling" or "inhibiting". This criterion does not match when the destination number received from the S-CSCF is not an ISDN number. In this case, a dialogue with the gsmSCF may or may not be established depending on whether the criterion is inhibiting or enabling respectively. + +Triggering at DP Collected\_Info shall be strictly based on the destination number received from the S-CSCF. + +The destination number received from the S-CSCF shall not be modified before conditional triggering check takes place. + +If the destination number triggering criterion is enabling, then the IM-SSF may establish a dialogue with the gsmSCF if: + +- the destination number matches one of the destination number strings defined in the list; or +- the length of the destination number matches one of the destination number lengths defined in the list. + +In this test the destination number matches one of the destination number strings in the list if: + +- the nature of address of destination number is the same as the nature of address of the destination number string; +- the destination number is at least as long as the destination number string in the list; and +- all the digits in the destination number string in the list match the leading digits of the destination number. + +If the destination number triggering criterion is inhibiting, then the IM-SSF may establish a dialogue with the gsmSCF if: + +- the destination number does not match any of the destination number strings defined in the list; and +- the length of the destination number does not match any of the destination number lengths defined in the list. + +In this test the destination number matches one of the destination number strings in the list if: + +- the nature of address of destination number is the same as the nature of address of the destination number string; +- the destination number is at least as long as the destination number string in the list; and +- all the digits in the destination number string in the list match the leading digits of the destination number. + +#### 4.3.2.2 Criteria at DP Analysed\_Information + +##### 4.3.2.2.1 General + +The following criteria are applicable for DP Analysed\_Information: + +- Destination number triggering criterion: The HSS may store a list of up to 10 destination numbers. There is no restriction on the nature of address. There is no restriction on the numbering plan indicator. This criterion does not match when the destination number received from the S-CSCF or the gsmSCF is not an ISDN number. + +NOTE: The order in which the destination number criteria are checked in the IM-SSF is not determined. Hence, overlapping destination number criteria (e.g. use of "0800" and "0800123" for two different services) should be avoided, because they lead to unpredictable behaviour (i.e. either service might be triggered). + +Triggering at DP Analysed\_Info shall be based on the destination number received in the Connect operation from the gsmSCF during a Mobile Originating CAMEL Service. + +##### 4.3.2.2.2 Number comparison + +The following procedure shall be performed for the comparison of the destination number triggering criterion and the address information in the given order. + +1. The numbering plan indicators of both numbers are ignored. +2. The type of number/nature of address indicators of both numbers are compared. If there is a match of the type of number indicator, then the check shall be performed by comparing the digits as defined in step 6. If there is no match of the type of number the comparison procedure shall continue as follows. +3. If either or both of the address information and destination number triggering criterion includes a type of number/nature of address indicator other than "unknown", "national (significant) number" or "international number" then the destination number does not match the destination number triggering criterion. Otherwise the comparison procedure shall continue as follows. + +4. If there is a number (address information or destination number triggering criterion) with type of number/nature of address "unknown" this number shall be translated based on the numbering plan of the serving entity in either of the following ways: + - if the leading digits refer to an international prefix, those digits shall be removed and the type of number/nature of address shall be set to "international number". + - if the leading digits refer to a national (trunk) prefix, those digits shall be removed and the type of number/nature of address shall be set to "national (significant) number". + +If the leading digits refer neither to an international prefix nor to a national (trunk) prefix, then the destination number does not match the destination number triggering criterion. + +If there is a match of the type of number/nature of address indicator after this number modification, then the check shall be performed by comparing the digits as defined in step 6, otherwise the comparison procedure shall continue as follows. + +5. If the type of number/nature of address of the address information or of the destination number triggering criterion is "national (significant) number" this number shall be translated based on the numbering plan of the serving entity to international format by adding the country code of the serving entity to the number string. After this modification both numbers shall be in international format and shall be checked by comparing the digits as defined in step 6. +- 6 If the number digits of the address information are compared with the number digits of the destination number triggering criterion, then there is a match if: + - the destination number is at least as long as the destination number string of the destination number triggering criterion; and + - all the digits in the destination number string of the destination number triggering criterion match the leading digits of the destination number. + +The check described in this clause shall be repeated for every number contained in the destination number triggering criterion of the D-IM-CSI until a match is recognised and DP Analysed\_Info is triggered, or until all the destination numbers have been checked without a match being recognised. In the latter case DP Analysed\_Info is not triggered. + +#### 4.3.2.3 Criteria at DP Route\_Select\_Failure + +The HSS may store a list of up to 5 cause values. + +The following criteria are applicable for DP Route\_Select\_Failure: + +- Release cause code. + +The trigger criteria is met if the cause code received from the terminating party's network (could be a PSTN or an IMS network) is equal to at least one of the cause codes in the trigger criteria list. + +If a O-IM-BCSM was already invoked and there is a relationship with the gsmSCF at that moment, then no additional relationship shall be initiated. + +#### 4.3.2.4 Criteria at DP T\_Busy and T\_No\_Answer + +The HSS may store a list of up to 5 cause values. + +The triggering is based on the release cause code received from terminating UE's P-CSCF. + +The following criteria are applicable for DP T\_Busy and T\_No\_Answer: + +- Release cause code. + +The trigger criteria are met if the cause code received from the terminating UE's P-CSCF is equal to at least one of the cause codes in the trigger criteria list. + +If trigger criteria are satisfied, then the corresponding Service Logic shall be invoked. + +## 4.4 Description of CAMEL Subscriber Data + +### 4.4.1 IP Multimedia CAMEL Subscription Information (IM-CSI) + +This subclause defines the contents of the IP Multimedia CAMEL Subscription Information. IM-CSI data are provisioned in the HSS for subscribers having originating and/or terminating IP Multimedia CAMEL services. This information shall be sent by the HSS to the IM-SSF via the Si Interface. The IM-CSI data contains the O-IM-CSI, D-IM-CSI, and VT-IM-CSI. + +#### 4.4.1.1 Originating IP Multimedia CAMEL Subscription Information (O-IM-CSI) + +##### 4.4.1.1.1 gsmSCF Address + +Address to be used to access the gsmSCF for a particular subscriber. The address shall be an E.164 number to be used for routing. + +##### 4.4.1.1.2 Service Key + +The Service Key identifies to the gsmSCF the service logic that shall apply. + +##### 4.4.1.1.3 Default Call Handling + +The Default Call Handling indicates whether the IP Multimedia session shall be released or continued as requested in case of error in the IM-SSF to gsmSCF dialogue. + +##### 4.4.1.1.4 TDP List + +The TDP List indicates on which detection point triggering shall take place. The following trigger detection points are possible: DP Collected\_Info and DP Route\_Select\_Failure. + +##### 4.4.1.1.5 CAMEL Capability Handling + +CAMEL Capability Handling indicates the phase of CAMEL which is asked by the gsmSCF for the service. + +##### 4.4.1.1.6 CSI Status + +The CSI state indicates whether the O-IM-CSI is active or not. + +##### 4.4.1.1.7 Notification Flag + +The notification flag indicates whether changes of the O-IM-CSI shall trigger the Notification on Change of Subscriber Data. In order to update the IM-SSF of IM CSI changes, this flag shall be set to yes. + +##### 4.4.1.1.8 DP Criteria + +The DP criteria indicate whether the IM-SSF shall request the gsmSCF for instructions. + +#### 4.4.1.2 Dialled Services IP Multimedia CAMEL Subscription Information (D-IM-CSI) + +##### 4.4.1.2.1 gsmSCF Address + +Address to be used to access the gsmSCF for a particular subscriber. The address shall be an E.164 number to be used for routing. + +##### 4.4.1.2.2 Service Key + +The Service Key identifies to the gsmSCF the service logic that shall apply. + +##### 4.4.1.2.3 Default Call Handling + +The Default Call Handling indicates whether the IP Multimedia session shall be released or continued as requested in case of error in the IM-SSF to gsmSCF dialogue. + +##### 4.4.1.2.4 CAMEL Capability Handling + +CAMEL Capability Handling indicates the phase of CAMEL which is asked by the gsmSCF for the service. + +##### 4.4.1.2.5 CSI Status + +The CSI state indicates whether the D-IM-CSI is active or not. + +##### 4.4.1.2.6 Notification Flag + +The notification flag indicates whether changes of the D-IM-CSI shall trigger the Notification on Change of Subscriber Data. In order to update the IM-SSF of IM CSI changes, this flag shall be set to yes. + +##### 4.4.1.2.7 DP Criteria + +The DP criteria indicate whether the IM-SSF shall request the gsmSCF for instructions. + +#### 4.4.1.3 Terminating IP Multimedia CAMEL Subscription Information (VT-IM-CSI) + +##### 4.4.1.3.1 gsmSCF Address + +Address to be used to access the gsmSCF for a particular subscriber. The address shall be an E.164 number to be used for routing. + +##### 4.4.1.3.2 Service Key + +The Service Key identifies to the gsmSCF the service logic that shall apply. + +##### 4.4.1.3.3 Default Call Handling + +The Default Call Handling indicates whether the IP Multimedia session shall be released or continued as requested in case of error in the IM-SSF to gsmSCF dialogue. + +##### 4.4.1.3.4 TDP List + +The TDP List indicates on which detection point triggering shall take place. The following trigger detection points are allowed: DP Terminating\_Attempt\_Authorised, DP T\_Busy, and DP T\_No\_Answer. + +##### 4.4.1.3.5 CAMEL Capability Handling + +CAMEL Capability Handling indicates the phase of CAMEL which is asked by the gsmSCF for the service. + +##### 4.4.1.3.6 CSI Status + +The CSI state indicates whether the VT-IM-CSI is active or not. + +##### 4.4.1.3.7 Notification Flag + +The notification flag indicates whether changes of the VT-IM-CSI shall trigger the Notification on Change of Subscriber Data. In order to update the IM-SSF of IM CSI changes, this flag shall be set to yes. + +##### 4.4.1.3.8 DP Criteria + +The DP criteria indicate whether the IM-SSF shall request the gsmSCF for instructions. + +#### 4.4.1.4 Other CAMEL Data + +##### 4.4.1.4.1 gsmSCF address list for CSI + +The gsmSCF address list for CSI indicates a list of gsmSCF addresses to which Notification on Change of Subscriber Data is to be sent. In order to provide Notification on Change of Subscriber Data to the IM-SSF, the IM-SSF address shall be included in the gsmSCF address list. + +The IM-SSF address is added to the address list for notification in the HSS as described in subclause 4.6.1.2. + +The IM-SSF shall handle the receipt of the Notification on Change of Subscriber Data using the same procedure as that of a gsmSCF. + +## 4.5 Description of CAMEL State Models + +In the IM Subsystem, calls are controlled by the Serving CSCF (S-CSCF) where a subscriber is registered. A state model describes the call control behaviour of an IM-SSF. + +### 4.5.1 General Handling + +The Basic Call State Model (BCSM) is used to describe the handling of originating and terminating calls. It identifies the points in a call where gsmSCF based service applications is permitted to interact with the call control capabilities of an IM-SSF. Figure 4.3 illustrates how transitions between states, Detection Points and Points In Call components are shown in the BCSM diagrams. + +![Diagram of BCSM Components showing a Transition arrow pointing to a DP box, which is part of a Point In Call (PIC) box.](43837b056625d3d6ce615e4c02f163bb_img.jpg) + +The diagram illustrates the components of a Basic Call State Model (BCSM). It features a vertical arrow labeled "Transition" pointing downwards to a small square box labeled "DP". This "DP" box is situated above a larger rectangular box labeled "Point In Call (PIC)". The "DP" box is partially overlaid by the top edge of the "PIC" box, indicating that the Detection Point is a component within the Point In Call. + +Diagram of BCSM Components showing a Transition arrow pointing to a DP box, which is part of a Point In Call (PIC) box. + +Figure 4.3: BCSM Components + +### 4.5.2 Originating CAMEL Basic Call State Model (O-IM-BCSM) + +#### 4.5.2.1 Description of the O-IM-BCSM + +The O-IM-BCSM is used to model the behaviour of an IM-SSF for an originating call. When an armed DP is encountered, O-IM-BCSM processing is suspended at the DP and the IM-SSF indicates this to the gsmSCF if appropriate. + +![State transition diagram for Originating CAMEL Basic Call State Model (O-IM-BCSM).](4356776ca004ecba5d599667a155d7d4_img.jpg) + +The diagram illustrates the state transitions for the Originating CAMEL Basic Call State Model (O-IM-BCSM). It consists of five main states: **O\_Null & Authorise\_Origination\_Attempt\_Collect\_Info**, **Analyse\_Information**, **Routing & Alerting**, **O\_Active**, and **O\_Exception**. Transitions are triggered by specific events or data outputs. + +- Initial State:** The process begins at **O\_Null & Authorise\_Origination\_Attempt\_Collect\_Info**. +- Transition to Analyse\_Information:** Triggered by **Collected\_Info**. This leads to **Analyse\_Information**. +- From Analyse\_Information:** + - invalid\_information** leads to **O\_Exception**. + - Analysed\_Information** leads to **Routing & Alerting**. +- From Routing & Alerting:** + - Route\_Select\_Failure**, **O\_Busy**, **O\_No\_Answer**, and **O\_routing\_and\_alerting\_failure** all lead to **O\_Exception**. + - O\_Answer** leads to **O\_Active**. +- From O\_Active:** + - O\_Disconnect** leads to an unlabeled state (likely a termination state). + - O\_active\_failure** leads to **O\_Exception**. +- Transitions to O\_Exception:** **O\_Exception** receives transitions from **O\_Null & Authorise\_Origination\_Attempt\_Collect\_Info**, **Analyse\_Information** (via *invalid\_information*), **Routing & Alerting** (via *Route\_Select\_Failure*, *O\_Busy*, *O\_No\_Answer*, and *O\_routing\_and\_alerting\_failure*), and **O\_Active** (via *O\_active\_failure*). +- Other Transitions:** + - O\_Abandon** is a transition from **O\_Active** back to **O\_Null & Authorise\_Origination\_Attempt\_Collect\_Info**. + +→ Basic Call transition + +State transition diagram for Originating CAMEL Basic Call State Model (O-IM-BCSM). + +**Figure 4.4: Originating CAMEL Basic Call State Model (O-IM-BCSM)** + +The following table 4.1 defines the DPs that apply to originating calls. + +**Table 4.1: Description of the O-IM-BCSM DPs in an IM-SSF** + +| CAMEL Detection Point: | DP Type | Description: | +|-------------------------------|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| DP Collected_Info | TDP-R | Indication that the O-IM-CSI is analysed | +| DP Analysed_Information | TDP-R | Availability of routeing address and nature of address. | +| DP Route_Select_Failure | TDP-R, EDP-N, EDP-R | Indication that the session establishment failed. | +| DP O_Busy | EDP-N, EDP-R | Indication that:
- a busy indication is received from the terminating party,
- a not reachable event is determined upon a SIP error response. | +| DP O_No_Answer | EDP-N, EDP-R | Indication that:
- an application timer associated with the O_No_Answer DP expires,
- a no answer event is determined upon SIP a error response | +| DP O_Answer | EDP-N, EDP-R | Indication that the session is accepted and answered by the terminating party. | +| DP O_Disconnect | EDP-N, EDP-R | A disconnect indication is received from the originating party or from the terminating party. | +| DP O_Abandon | EDP-N, EDP-R | Indication that a disconnect indication is received from the originating party during the session establishment procedure. | + +#### 4.5.2.2 Description of Points In Call + +This subclause describes the Points In Call for originating calls. The entry events, actions and exit events are described for each Point in Call. + +##### 4.5.2.2.1 O\_Null & Authorise\_Origination\_Attempt\_Collect\_Info + +Entry events: + +- Disconnection and clearing of a previous call (DP O\_Disconnect) or default handling of exceptions by IM-SSF completed. +- Abandon event is reported from Analyse\_Information or Routing and Alerting PIC. +- Exception event is reported. + +Actions: + +- Interface is idled. +- Originating call: SIP INVITE request message containing the dialled number is received from MS. +- Information being analysed e.g., O-IM-CSI is analysed. + +Exit events: + +- Originating CSI is analysed. +- An exception condition is encountered. For this PIC, if the call encounters one of these exceptions during the PIC processing, the exception event is not visible because there is no corresponding DP. Example exception condition: Calling party abandons call. + +##### 4.5.2.2.2 Analyse\_Information + +Entry events: + +- Originating CSI is analysed. (DP Collected Info). +- New routeing information is received when Busy event (DP O\_Busy), Route Select Failure event (DP Route\_Select\_Failure), Not Reachable event (DP O\_Busy) or No Answer event (DP O\_No\_Answer) is reported from Routing and Alerting PIC. +- New routeing information is received when Disconnect event is reported from O\_Active PIC. + +###### Actions: + +- Compare the called party number with the dialled services information. + +###### Exit events: + +- Availability of routeing address and nature of address. (DP Analysed\_Information). +- An exception condition is encountered (e.g. wrong number)- this leads to the O\_Exception PIC. +- Calling party abandons the call- this leads to the O\_Abandon DP. + +##### 4.5.2.2.3            Routing and Alerting + +###### Entry events: + +- Availability of routeing address and nature of address. (DP Analysed\_Information). + +###### Actions: + +- Information is being analysed and/or translated according to dialling plan to determine routeing address. +- Routeing address being interpreted. +- Call is being processed by the terminating half BCSM. Continued processing of SIP call session setup (e.g., ringing) is taking place. Waiting for indication from terminating half BCSM that the call has been answered by terminating party. + +###### Exit events: + +- Indication from the terminating half BCSM that the call is accepted and answered by terminating party (DP O\_Answer). +- An exception condition is encountered - this leads to the O\_Exception PIC. +- Calling party abandons the call- this leads to the O\_Abandon DP. +- A busy indication is received from the terminating party - this leads to the O\_Busy DP. +- A not reachable indication is received from the terminating party - this leads to the O\_Busy DP. +- Attempt to select the route for the call fails - this leads to the Route\_Select\_Failure DP. + +If the no reply timer expires and DP O\_No\_Answer is armed - this leads to the O\_No\_Answer DP. + +##### 4.5.2.2.4            O\_Active + +###### Entry events: + +- Indication from the terminating half BCSM that the call is accepted and answered by the terminating party (DP O\_Answer). + +###### Actions: + +- SIP session established between originating party and terminating party. - Call release is awaited. + +###### Exit events: + +- A disconnection indication is received from the originating party, or received from the terminating party via the terminating half BCSM. (DP - O\_Disconnect). + +- An exception condition is encountered. + +##### 4.5.2.2.5 O\_Exception + +Entry events: + +- An exception condition is encountered. In addition to specific examples listed above, exception events include any type of failure, which means that the normal exit events for a PIC can not be met. + +Actions: + +- Default handling of the exception condition is being provided. This includes general actions necessary to ensure that no resources remain inappropriately allocated such as: +- If any relationship exists between the IM-SSF and the gsmSCF, the IM-SSF shall send an error information flow closing the relationships and indicating that any outstanding call handling instructions will not run to completion. +- Resources made available for setting up the SIP call session are released. + +Exit events: + +- Default handling of the exception condition by IM-SSF completed. + +### 4.5.3 Mapping of SIP Method/Response to O-IM-BCSM Detection Points + +This subclause describes mapping of SIP methods and responses to CAMEL Detection Points. + +**Table 4.2: Mapping of SIP Method/Response to CAMEL O-IM-BCSM DPs** + +| CAMEL O-IM-BCSM DP: | SIP Method/Response | +|-------------------------|-------------------------------------------------------------------------| +| DP Collected_Info | INVITE | +| DP Analysed_Information | N/A | +| DP Route_Select_Failure | 4XX (except 401, 407, 408, 480, 486),
5xx, and 6xx (except 600, 603) | +| DP O_Busy | 486 Busy Here
600 Busy Everywhere | +| DP O_No_Answer | 603 Decline
408 Request Timeout
480 Temp Unavailable | +| DP O_Answer | 200 OK | +| DP O_Disconnect | BYE | +| DP O_Abandon | CANCEL | + +### 4.5.4 Terminating CAMEL Basic Call State Model (T-IM-BCSM) + +#### 4.5.4.1 Description of the T-IM-BCSM + +The T-IM-BCSM is used to model the behaviour of an IM-SSF for a terminating call. When a DP is encountered, T-IM-BCSM processing is suspended at the DP and IM-SSF indicates this to the gsmSCF if appropriate. + +![Figure 4.5: Terminating CAMEL Basic Call State Model (T-IM-BCSM) state transition diagram. The diagram shows three main states: T_Null, Terminating Call Handling, and T_Active. Transitions are labeled with events like T_Abandon, Terminating_Attempt_Authorised, T_Busy, T_No_Answer, T_call_handling_failure, T_Disconnect, T_Answer, and T_active_failure. A legend indicates that solid arrows represent 'Basic Call transition'.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` + +stateDiagram-v2 + [*] --> T_Null + T_Null --> Terminating_Call_Handling : Terminating_Attempt_Authorised + Terminating_Call_Handling --> T_Busy : T_Busy + Terminating_Call_Handling --> T_No_Answer : T_No_Answer + Terminating_Call_Handling --> T_call_handling_failure : T_call_handling_failure + Terminating_Call_Handling --> T_Active : T_Answer + T_Active --> [*] : T_Disconnect + T_Active --> T_Null : T_Abandon + T_Active --> T_Exception : T_active_failure + T_Exception --> T_Null + +``` + +→ Basic Call transition + +Figure 4.5: Terminating CAMEL Basic Call State Model (T-IM-BCSM) state transition diagram. The diagram shows three main states: T\_Null, Terminating Call Handling, and T\_Active. Transitions are labeled with events like T\_Abandon, Terminating\_Attempt\_Authorised, T\_Busy, T\_No\_Answer, T\_call\_handling\_failure, T\_Disconnect, T\_Answer, and T\_active\_failure. A legend indicates that solid arrows represent 'Basic Call transition'. + +**Figure 4.5: Terminating CAMEL Basic Call State Model (T-IM-BCSM)** + +The following table 4.3 defines the DPs that apply to terminating calls. + +**Table 4.3: Description of T-IM-BCSM DPs in the S-CSCF** + +| CAMEL DP: | DP Type | Description: | +|-----------------------------------|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DP Terminating_Attempt_Authorised | TDP-R | Indication that the VT-IM-CSI is analysed. | +| DP T_Busy | TDP-R, EDP-N, EDP-R | Indication that:
- a busy indication is received from the terminating party,
- a not reachable event is determined (e.g. terminating party is not currently registered). | +| DP T_No_Answer | TDP-R, EDP-N, EDP-R | Indication that an application timer associated with the T_No_Answer DP expires. | +| DP T_Answer | EDP-N, EDP-R | Session is accepted and answered by terminating party. | +| DP T_Disconnect | EDP-N, EDP-R | A disconnect indication is received from the terminating party or from the originating party. | +| DP T_Abandon | EDP-N, EDP-R | A disconnect indication is received from the originating party during the session establishment procedure. | + +#### 4.5.4.2 Description of Points In Call + +This subclause describes the Points In Call for terminating calls. The entry events, actions and exit events are described for each Point in Call. + +##### 4.5.4.2.1 T\_Null + +Entry events: + +- Disconnection and clearing of a previous call (DP T\_Disconnect) or default handling of exceptions by IM-SSF completed. +- Abandon event is reported from Terminating Call Handling PIC. +- Exception event is reported. + +Actions: + +- Interface is idled. +- SIP INVITE message for terminating call request is received, the appropriate information is analysed. +- VT-IM-CSI is analysed. + +Exit events: + +- Terminating CSI is analysed. +- An exception condition is encountered. For this PIC, if the call encounters one of these exceptions during the PIC processing, the exception event is not visible because there is no corresponding DP. + +Example exception condition is: + +- Calling party abandons call. + +##### 4.5.4.2.2 Terminating Call Handling + +Entry events: + +- Terminating CSI (if available) is analysed. (DP Terminating\_Attempt\_Authorised). +- New routeing information is received when Busy event (DP T\_Busy) or No Answer event (DP T\_No\_Answer) is reported from Terminating Call Handling PIC. +- New routeing information is received when Disconnect event is reported from T\_Active PIC. +- New routeing information is received when the terminating party not reachable is reported from Terminating Call Handling PIC. + +Actions: + +- Routeing address and call type being interpreted. The next route or terminating access is being selected. +- The terminating party is being alerted. Waiting for the call to be answered by terminating party. + +Exit events: + +- Call is accepted and answered by terminating party. +- An exception condition is encountered - this leads to the T\_Exception PIC. Example exception conditions: the SIP call session request was not successful. +- Calling party abandons the call - this leads to the T\_Abandon DP. +- A busy indication is received from the terminating party's P-CSCF - this leads to the T\_Busy DP. +- Not reachable event detected from the terminating party's P-CSCF - this leads to the T\_Busy DP. +- If no reply timer expires and DP T\_No\_Answer is armed - this leads to the T\_No\_Answer DP. + +##### 4.5.4.2.3 T\_Active + +Entry events: + +- Indication that the call is accepted and answered by the terminating party. (DP T\_Answer). + +###### Actions: + +- SIP session established between originating party and terminating party. +- Call release is awaited. + +###### Exit events: + +- A disconnection indication is received from the terminating party, or received from the originating party via the originating half BCSM. (DP T\_Disconnect). +- An exception condition is encountered. In addition to specific examples listed above, exception events include any type of failure that means that the normal exit events for a PIC can not be met. + +##### 4.5.4.2.4 T\_Exception + +###### Entry events: + +- An exception condition is encountered. In addition to specific examples listed above, exception events include any type of failure, which means that the normal exit events for PIC cannot be met. + +###### Actions: + +- Default handling of the exception condition is being provided. This includes general actions necessary to ensure that no resources remain inappropriately allocated such as: + - If any relationship exists between the IM-SSF and the gsmSCF, the IM-SSF shall send an error information flow closing the relationships and indicating that any outstanding call handling instructions will not run to completion. + - Resources made available for setting up the SIP call session are released. + +###### Exit events: + +- Default handling of the exception condition by IM-SSF completed. + +### 4.5.5 Mapping of SIP Method/Response to T-IM-BCSM Detection Points + +This subclause describes mapping of SIP methods and responses to CAMEL Detection Points. + +**Table 4.4: Mapping of SIP Method/Response to CAMEL T-IM-BCSM DPs** + +| CAMEL T-IM-BCSM DP: | SIP Method/Response | +|----------------------------------------|---------------------------------------------------------------| +| DP Terminating_Attempt_
_Authorised | INVITE | +| DP T_Busy | 4XX (except 401, 407, 408, 480),
5xx, and 6xx (except 603) | +| DP T_No_Answer | 603 Decline
408 Request Timeout
480 Temp Unavailable | +| DP T_Answer | 200 OK | +| DP T_Disconnect | BYE | +| DP T_Abandon | CANCEL | + +## 4.6 Procedures for IM-SSF Application Server + +The SDLs in this specification illustrate how CAMEL modifies the normal multimedia call. They do not attempt to show all the details of multimedia handling in all the modes that support CAMEL. + +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. + +### 4.6.1 Overall SDL Architecture + +![Diagram of SIP Registration into IM-SSF architecture](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +This diagram illustrates the architecture for SIP registration into the IM-SSF. At the top, a yellow box labeled 'gsmSCF' is shown with a note: 'The gsmSCF is not involved in this procedure.' Below it, a dashed box labeled 'IM-SSF' contains two white boxes: 'imcnSSF' and 'Register\_IM\_SSF'. To the left, a yellow box labeled 'HSS' is connected to the 'Register\_IM\_SSF' box via a dashed line labeled 'Si interface (MAP)'. Below the HSS, a yellow box labeled 'Mobile Station' is connected to a white box labeled 'S-CSCF' via a dashed line labeled 'SIP'. A diagonal dashed line labeled 'Cx interface (DIAMETER)' connects the HSS to the S-CSCF. A vertical dashed line labeled 'ISC interface' connects the 'Register\_IM\_SSF' box to the 'S-CSCF' box. + +Diagram of SIP Registration into IM-SSF architecture + +Figure 4.6: SIP Registration into IM-SSF + +![Diagram of Originating Case architecture](8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg) + +This diagram illustrates the architecture for the Originating Case. At the top, a yellow box labeled 'gsmSCF' is connected to a dashed box labeled 'IM-SSF' via a dashed line labeled 'CAP interface'. The 'IM-SSF' box contains two white boxes: 'imcnSSF' and 'MO\_IM\_SSF', connected by a dashed line labeled 'Internal interface'. Below the 'IM-SSF' box, a vertical dashed line labeled 'ISC interface' connects to a white box labeled 'S-CSCF'. To the left, a yellow box labeled 'MRFC' is connected to the 'S-CSCF' box via a dashed line labeled 'Mr interface (SIP)'. Below the MRFC, a yellow box labeled 'Mobile Station' is connected to the 'S-CSCF' box via a dashed line labeled 'SIP'. To the right of the 'S-CSCF' box, a yellow box labeled 'Destination CSCF' is connected via a dashed line labeled 'SIP'. + +Diagram of Originating Case architecture + +Figure 4.7: Originating Case + +![Figure 4.8: Terminating Case. A network architecture diagram showing the interaction between various components for a terminating call. At the top is gsmSCF. Below it is a dashed box labeled IM-SSF containing imcnSSF and MT_IM_SSF. To the left is MRFC. At the bottom are Mobile Station, S-CSCF, and Originating CSCF. Interfaces shown include CAP interface (gsmSCF to IM-SSF), Internal interface (imcnSSF to MT_IM_SSF), ISC interface (MT_IM_SSF to S-CSCF), Mr interface (SIP) (MRFC to S-CSCF), SIP (Mobile Station to S-CSCF), and SIP (S-CSCF to Originating CSCF).](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +Figure 4.8: Terminating Case. A network architecture diagram showing the interaction between various components for a terminating call. At the top is gsmSCF. Below it is a dashed box labeled IM-SSF containing imcnSSF and MT\_IM\_SSF. To the left is MRFC. At the bottom are Mobile Station, S-CSCF, and Originating CSCF. Interfaces shown include CAP interface (gsmSCF to IM-SSF), Internal interface (imcnSSF to MT\_IM\_SSF), ISC interface (MT\_IM\_SSF to S-CSCF), Mr interface (SIP) (MRFC to S-CSCF), SIP (Mobile Station to S-CSCF), and SIP (S-CSCF to Originating CSCF). + +**Figure 4.8: Terminating Case** + +#### 4.6.1.1 Handling of Registration and De-registration in the IM-SSF + +During the UE registration, the HSS shall send the filter criteria for the IM-SSF to the S-CSCF if the subscriber is provisioned with IP Multimedia CAMEL Subscription Information data at the HSS. + +- The HSS shall include the IMSI data for the subscriber within the Service Information element of the filter criteria for IM-SSF. The IMSI shall be used for querying the HSS for CAMEL Subscription Information data via a MAP interface. + +The CAMEL service provider determines the actual format of the data sent within the Service Information element of the filter criteria (e.g. IMSI). The actual format is transparent to the S-CSCF i.e. CAMEL service information is not processed, analysed, or evaluated by the S-CSCF. It is, however, known to the IM-SSF, gsmSCF, and the HSS (for provisioning of the service information data). + +If a registration/de-registration request matches the filter criteria of the IM-SSF, the S-CSCF informs the IM-SSF of the request by performing a third party registration/de-registration i.e. a SIP REGISTER message is sent from the S-CSCF to the IM-SSF. + +General handling of IP Multimedia registration, re-registration, de-registration and receipt of initial filter criteria at the S-CSCF is specified in 3GPP TS 23.228 [6] and 23.218 [5]. + +The process and the procedures specific to CAMEL are specified in this subclause: + +- Process Register\_IM\_SSF; +- Procedure CAMEL\_IMCN\_Register; +- Procedure CAMEL\_IMCN\_DeRegister. + +##### 4.6.1.1.1 Procedure CAMEL\_IMCN\_Register + +When querying the HSS for the subscriber's IM CSI data, the IM-SSF does not have to wait for the HSS's response on the first query before the subsequent queries are done. i.e. Sending of multiple Any Time Interrogation operations can be done in parallel. However, the IM-SSF shall wait for all the responses from the HSS before it shall send a SIP response message to the S-CSCF. + +![Flowchart for Process Register_IM_SSF](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +### Process Register\_IM\_SSF 1(1) + +Process in IM-SSF for handling receipt of a SIP REGISTER method from the S-CSCF. + +Signals to/from the left are to/from the S-CSCF. + +``` +graph TD; Start([ ]) --> idle([idle]); idle --> REGISTER[/REGISTER/]; REGISTER --> Expires{Expires > 0}; Expires -- No --> DeRegister[CAMEL_IMCN DeRegister]; Expires -- Yes --> Register[CAMEL_IMCN Register]; DeRegister --> Idle([Idle]); Register --> Idle; +``` + +The flowchart illustrates the process for handling a SIP REGISTER method in the IM-SSF. It begins with an initial state leading to an 'idle' state. Upon receiving a 'REGISTER' message, it checks if 'Expires > 0'. If 'No', it executes 'CAMEL\_IMCN DeRegister' and then enters an 'Idle' state. If 'Yes', it executes 'CAMEL\_IMCN Register' and then enters an 'Idle' state. + +Flowchart for Process Register\_IM\_SSF + +Figure 4.9: Process Register\_IM\_SSF (sheet 1) + +![Flowchart for procedure CAMEL_IMCN_Register. It starts with a decision 'Subscriber profile downloaded?'. If 'Yes', it sends '200 OK' and ends. If 'No', it sends 'ATSI_query' with 'Requested IM CSI: O-IM-CSI, VT-IM-CSI, D-IM-CSI', then 'Wait for response'. From 'Wait for response', it branches to 'ATSI_Ack' or 'ATSI negative Response'. 'ATSI_Ack' leads to 'Store Subscriber info', then a decision 'More IM CSI to be requested?'. If 'Yes', it ends at connector '1'. If 'No', it leads to another decision 'Atleast one IM CSI is received?'. If 'Yes', it sends '200 OK' and ends. If 'No', it sends '606 Not Acceptable' and ends. 'ATSI negative Response' leads to a decision diamond. If 'Yes', it sends an error 'Information Not Available?' and ends at connector '1'. If 'No', it leads to the 'Atleast one IM CSI is received?' decision. There is also a connector '1' at the top right leading to the 'ATSI_query' step.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +### procedure CAMEL\_IMCN\_Register + +Procedure in IM-SSF when notified of a UE's registration in the IM CN. + +Signals to/from the left are to/from the S-CSCF, and signals to/from the right are to/from the HSS. + +1(1) + +``` +graph TD; Start([ ]) --> Q1{Subscriber profile downloaded?}; Q1 -- Yes --> OK1{{200 OK}}; OK1 --> End1(( )); Q1 -- No --> ATSI_query{{ATSI_query}}; ATSI_query --> Wait[Wait for response]; ATSI_query --- Info[Requested IM CSI: +O-IM-CSI +VT-IM-CSI +D-IM-CSI]; Wait --> ATSI_Ack{{ATSI_Ack}}; Wait --> ATSI_Neg[ATSI negative Response]; ATSI_Ack --> Store[Store Subscriber info]; Store --> More1{More IM CSI to be requested?}; More1 -- Yes --> End1((1)); More1 -- No --> Atleast{Atleast one IM CSI is received?}; Atleast -- Yes --> OK2{{200 OK}}; OK2 --> End2(( )); Atleast -- No --> NotAcc[606 Not Acceptable]; NotAcc --> End3(( )); ATSI_Neg --> NegDec{ }; NegDec -- Yes --> Error[Error = "Information Not Available?"]; NegDec -- No --> Atleast; NegDec --- Error; End2((1)); +``` + +Flowchart for procedure CAMEL\_IMCN\_Register. It starts with a decision 'Subscriber profile downloaded?'. If 'Yes', it sends '200 OK' and ends. If 'No', it sends 'ATSI\_query' with 'Requested IM CSI: O-IM-CSI, VT-IM-CSI, D-IM-CSI', then 'Wait for response'. From 'Wait for response', it branches to 'ATSI\_Ack' or 'ATSI negative Response'. 'ATSI\_Ack' leads to 'Store Subscriber info', then a decision 'More IM CSI to be requested?'. If 'Yes', it ends at connector '1'. If 'No', it leads to another decision 'Atleast one IM CSI is received?'. If 'Yes', it sends '200 OK' and ends. If 'No', it sends '606 Not Acceptable' and ends. 'ATSI negative Response' leads to a decision diamond. If 'Yes', it sends an error 'Information Not Available?' and ends at connector '1'. If 'No', it leads to the 'Atleast one IM CSI is received?' decision. There is also a connector '1' at the top right leading to the 'ATSI\_query' step. + +Figure 4.10: Procedure CAMEL\_IMCN\_Register (sheet 1) + +![Flowchart for procedure CAMEL_IMCN_DeRegister. It starts with a start symbol, followed by a decision 'Subscriber IM-CSI data available'. If 'Yes', it proceeds to 'Delete Subscriber IM-CSI data'. If 'No', it bypasses the delete step. Both paths lead to a '200 OK' response symbol, which then leads to an end symbol.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +procedure CAMEL\_IMCN\_DeRegister 1(1) + +Procedure in IM-SSF when notified of a UE's de-Registration. + +Signals to/from the left are to /from the S-CSCF. + +``` +graph TD; Start([Start]) --> Decision{Subscriber IM-CSI data available}; Decision -- Yes --> Delete[Delete Subscriber IM-CSI data]; Decision -- No --> OK{200 OK}; Delete --> OK; OK --> End((End)); +``` + +Flowchart for procedure CAMEL\_IMCN\_DeRegister. It starts with a start symbol, followed by a decision 'Subscriber IM-CSI data available'. If 'Yes', it proceeds to 'Delete Subscriber IM-CSI data'. If 'No', it bypasses the delete step. Both paths lead to a '200 OK' response symbol, which then leads to an end symbol. + +**Figure 4.11: Procedure CAMEL\_IMCN\_DeRegister (sheet 1)** + +#### 4.6.1.2 Handling of Notify Subscriber Data Change + +When the HSS updates the CSI for a subscriber in the IP Multimedia CN subsystem, the HSS shall send a Notify Subscriber Data Change to the IM-SSF if all of the following conditions are true: + +- The IM CSI data is marked with the Notification Flag + +- The IM-SSF address is included in the gsmSCF address list + +The IM-SSF address shall be added in the gsmSCF address list at the HSS for notification of IM-CSI updates if one of the following conditions occurs: + +- a. The HSS is notified of the subscriber's registration at the S-CSCF (via Cx interface), and the subscriber is provisioned with IM CSI data. +- b. Operator provisions HSS subscriber data with IMS CAMEL service while the subscriber is currently registered in the IMS network i.e. one or more IM CSI data is added to the subscriber's profile in the HSS. +- c. The HSS is notified of mobile termination for an unregistered subscriber (via Cx interface), and the subscriber is provisioned with IM CSI data + +The IM-SSF address shall be deleted from the gsmSCF address list when the HSS initiates, or is notified of, the UE's deregistration. + +The IM-SSF address in the gsmSCF address list may be changed when the HSS receives a notification of a registration for a UE with a S-CSCF name different from the previously assigned S-CSCF name (i.e. re-registration from HSS point of view). The HSS shall overwrite the existing IM-SSF address with the IM-SSF address associated with the new S-CSCF name. + +The HSS procedure for sending the Notify Subscriber Data Change to the IM-SSF is the same procedure used for notifying the gsmSCFs in the Circuit Switched CN. This procedure is described in Procedure CAMEL\_NSDC\_HLR specified in 3GPP TS 23.078 Rel-99[4]. + +The process specific to IM-SSF's handling of the Notify Subscriber Data Change is specified in this subclause: + +- Process Update\_CSI + +![Flowchart for Process Update_CSI](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +### Process Update\_CSI + +1(1) + +Process in IM-SSF when notified of a change of subscriber IM CSI data from the HSS. + +Signals signals to/from the right are to/from the HSS. + +``` +graph TD; Start([ ]) --> idle1([idle]); idle1 --> NOTIFY1[/NOTIFY SUBSCRIBER DATA CHANGE/]; NOTIFY1 --> Update[Update/Delete Subscriber Data]; Update --> NOTIFY2[/NOTIFY SUBSCRIBER DATA CHANGE ACK/]; NOTIFY2 --> Idle2([Idle]); +``` + +The flowchart illustrates the 'Process Update\_CSI' in an IM-SSF. It begins with an oval connector, leading to a state labeled 'idle'. An arrow points down to a parallelogram labeled 'NOTIFY SUBSCRIBER DATA CHANGE'. This is followed by a rectangular process block 'Update/Delete Subscriber Data'. An arrow then points to another parallelogram labeled 'NOTIFY SUBSCRIBER DATA CHANGE ACK'. Finally, an arrow points down to an oval connector labeled 'Idle'. + +Flowchart for Process Update\_CSI + +Figure 4.12: Process Update\_CSI (sheet 1) + +#### 4.6.1.3 Handling of Mobile Originated Calls in the IM-SSF + +The functional behaviour of the S-CSCF is specified in 3GPP TS 23.218 [5]. The process and the procedures specific to CAMEL are specified in this subclause: + +- Process MO\_IM\_SSF; +- Procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT; +- Procedure CAMEL\_IMCN\_MO\_D\_IM\_CSI\_INIT; +- Procedure CAMEL\_IMCN\_MO\_CANCEL; +- Procedure CAMEL\_IMCN\_MO\_ANSWER; +- Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL; +- Procedure CAMEL\_IMCN\_MO\_DISC1; +- Procedure CAMEL\_IMCN\_MO\_DISC2; +- Procedure CAMEL\_OCH\_CTR. + +Internal interface indicated with the "Int\_SRF\_" prefix within this subclause indicates internal interface with the MRFC. + +##### 4.6.1.3.1 Actions of the IM-SSF on receipt of Int\_Error + +The IM-SSF checks the default Call Handling parameter in the relevant CSI. + +If the default call handling is release, a BYE indication is sent to the MS. The IM-SSF then releases all resources and the invoked CAMEL procedure ends. + +If the call handling is continue, the IM-SSF continues processing without CAMEL support. + +##### 4.6.1.3.2 Actions of the IM-SSF on receipt of Int\_Continue + +The IM-SSF continues processing without any modification of call parameters. + +#### 4.6.1.3.3 Actions of the IM-SSF on receipt of Int\_Continue\_With\_Argument + +The IM-SSF continues processing with modified call parameters. The IM-SSF shall modify the call parameters by the information received in the Int\_Continue\_With\_Argument message. Call parameters that are not included in the Int\_Continue\_With\_Argument\_Message are unchanged. + +##### 4.6.1.3.4 Actions of the IM-SSF on receipt of Int\_Connect + +The IM-SSF continues processing with modified call parameters. The IM-SSF shall transparently modify the call parameters with the received information. Call parameters, which are not included in the Int\_Connect message, are unchanged. + +##### 4.6.1.3.5 Actions of the IM-SSF on receipt of Int\_Release\_Call + +A BYE is sent to the MS, and a BYE is sent to the destination CSCF. The release cause received in the Int\_Release\_Call is used. The IM-SSF then releases all call resources and all CAMEL processing ends. + +##### 4.6.1.3.6 Handling of procedure CAMEL\_OCH\_CTR, sheet 1 + +The IM-SSF behaves as a B2BUA (Back-2-Back User Agent) when a SIP INVITE is received for an outgoing call and SIP INVITE is sent to the MRFC (via S-CSCF) as a result of a CAP ConnectToResource request received from the SCF. + +A SIP response 100 Trying is sent after each INVITE but is not shown in the SDLs. + +The IM-SSF shall handle the 200 OK response from the MRFC as specified in 3GPP TS 23.218 [5]. + +#### 4.6.1.3.7 Handling of procedure CAMEL\_OCH\_CTR, sheet 5 + +The specifics on transporting information between the MRFC and the Application Server such as the IM-SSF, has not been standardised in 3GPP Rel-5 specifications for IMS. i.e. the SIP method to return the Prompt\_and\_Collect result from the MRFC to the IM-SSF, the SIP method for sending notification of play announcement completion to the IM-SSF when a request for a Specialised Resource Report was received, the SIP method to request the MRFC to play announcement and the SIP method to request the MRFC to prompt and collect user information, are not standardised. + +#### 4.6.1.3.8 Receipt of 100 Trying Provisional Response (Process MO\_IM\_SSF) + +The IM-SSF (acting as B2BUA) uses the S-CSCF as the next-hop server when sending the SIP INVITE to the destination S-CSCF. The 100 Trying provisional response received in the IM-SSF is actually generated and sent from the S-CSCF to indicate that the INVITE request has been received by the next-hop server (i.e. the S-CSCF) and is currently being processed. + +#### 4.6.1.3.9 Handling of internal timers in Process MO\_IM\_SSF + +The SIP B timer defined in 3GPP TS 24.229 [8] is used for IM-SSF handling of no response condition for an INVITE request, similar to the Circuit Switched handling of TNRy Timer for No Reply. The use of B timer in the IM-SSF is indicated in the SDL Process MO\_IM\_SSF. There are other SIP timers defined in 3GPP TS 24.229 [8] that are not specified in the SDLs for IM-SSF processing. The usage of these timers is based on the network's implementation of the IM-SSF (e.g. choice of UDP or TCP for transport of SIP, and how IM-SSF operates as both a UAS and a UAC - i.e. back-to-back UA). + +The following sub-clauses provide additional information on Process MO\_IM\_SSF's handling of the internal timers: + +Sheets 1-2: The inclusion of Expires header field in the INVITE method is optional and is used to indicate the duration of the invitation in seconds. When the timer fires before a final response is generated by the IM-SSF, the INVITE message is considered to be "expired". The IM-SSF shall report a call abandon event to the gsmSCF if requested and return a 487 Request Terminated to the originating S-CSCF. + +When the IM-SSF (taking the role of a UAC) sends out the INVITE request, the B timer (i.e. Tb timer) shall be used for the INVITE transaction timeout timer. Refer to 3GPP TS 24.229 [8] for the recommended B timer value. + +Sheet 3: When the IM-SSF (taking the role of a UAS) sends the 200 OK final response to the S-CSCF that sent the INVITE request, the IM-SSF shall start the Tack timer to monitor the receipt of the ACK request. Refer to 3GPP TS 24.229 [8] for the recommended ACK timer value. + +Sheet 4: The expiration of Tb timer shall be reported as a no answer event to the gsmSCF if requested. If the Tinvite timer expires, the IM-SSF shall report a call abandon event to the gsmSCF if requested. + +Sheet 5: The expiration of the Tack shall be reported to the gsmSCF as a call disconnect from the originating party if requested. + +![Flowchart for Process MO_IM_SSF (sheet 1). The process starts with an oval connector, followed by an 'Idle' state. It then receives an 'INVITE' message, followed by a '100 Trying' response. Next, it enters an 'Initialise values' state where several variables are set to False. A decision diamond asks 'INVITE Expires received?'. If 'Yes', it sets 'Tinvite := INVITE Expires received' and starts 'Tinvite'. If 'No', it skips to connector '3'. Both paths lead to connector '3'.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +**Process MO\_IM\_SSF** 1(6) + +Process in IM-SSF to perform +Mobile Originating Call +in IMS. + +/\* Signals to/from the left are to/from the MS +via S-CSCF; signals to/from right are to/from +the destination S-CSCF +via S-CSCF, unless otherwise stated. \*/ + +``` +graph TD; Start([ ]) --> Idle[Idle]; Idle --> INVITE[/INVITE/]; INVITE --> 100Trying{100 Trying}; 100Trying --> Init[Initialise values]; Init --> InitNote["CAMEL_Invocation := False; +Provisional_Response_Received := False; +Final_Response_Received := False; +Cancel_Received := False;"]; Init --> Decision{INVITE Expires received?}; Decision -- Yes --> Tset[Tinvite := INVITE Expires received]; Tset --> Tstart[Start Tinvite]; Decision -- No --> Connector3((3)); Tstart --> Connector3; Connector3 --> End((3)); +``` + +Flowchart for Process MO\_IM\_SSF (sheet 1). The process starts with an oval connector, followed by an 'Idle' state. It then receives an 'INVITE' message, followed by a '100 Trying' response. Next, it enters an 'Initialise values' state where several variables are set to False. A decision diamond asks 'INVITE Expires received?'. If 'Yes', it sets 'Tinvite := INVITE Expires received' and starts 'Tinvite'. If 'No', it skips to connector '3'. Both paths lead to connector '3'. + +Figure 4.13-1: Process MO\_IM\_SSF (sheet 1) + +![Flowchart for Process MO_IM_SSF (sheet 2). The process starts at connector 3, calls CAMEL_IMCN MO_O_IM_CSI_INIT, then checks the result. If 'Pass', it calls CAMEL_IMCN MO_D_IM_CSI_INIT and checks the result again. If 'Pass', it checks for a CAMEL_Invocation. If 'True', it sends an INVITE, starts timer Tb, and waits for an answer. If 'False', it checks for 606 Not Acceptable. If 'Fail' at the first result check, it checks for 606 Not Acceptable. If 'Abort', it checks for 487 Request Terminated. If 'INVITE Expires', it sets an event 'Timer expired', calls CAMEL_IMCN MO_CANCEL, and checks for 487 Request Terminated. All successful paths lead to connector 2, then Release Call Resources, and finally Idle. All error/abort paths lead to connector 2, then Release Call Resources, and finally Idle.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +### Process MO\_IM\_SSF 2(6) + +Process in IM-SSF to perform Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the destination S-CSCF via S-CSCF, unless otherwise stated. \*/ + +``` +graph TD; 3((3)) --> C1[CAMEL_IMCN MO_O_IM_CSI_INIT]; C1 --> R1{Result ?}; R1 -- Pass --> C2[CAMEL_IMCN MO_D_IM_CSI_INIT]; R1 -- Fail --> R606_1{606 Not Acceptable}; R1 -- Abort --> R487_1{487 Request Terminated}; R1 -- "INVITE Expires" --> E1[Event := "Timer expired"]; E1 --> C3[CAMEL_IMCN MO_CANCEL]; C3 --> R487_2{487 Request Terminated}; C2 --> R2{Result ?}; R2 -- Pass --> CI{CAMEL_Invocation ?}; R2 -- Fail --> R606_2{606 Not Acceptable}; R2 -- Abort --> R487_3{487 Request Terminated}; R2 -- "INVITE Expires" --> E2[Event := "Timer expired"]; E2 --> C4[CAMEL_IMCN MO_CANCEL]; C4 --> R487_4{487 Request Terminated}; CI -- True --> INVITE[INVITE]; INVITE --> STb[Start Tb]; STb --> WFA[Wait_For_Answer]; CI -- False --> R606_3{606 Not Acceptable}; R606_1 --> R200{200 OK}; R606_2 --> R200; R606_3 --> R200; R487_1 --> R200; R487_2 --> R200; R487_3 --> R200; R487_4 --> R200; R200 --> 2((2)); 2 --> RCR[Release Call Resources]; RCR --> Idle([Idle]); +``` + +Flowchart for Process MO\_IM\_SSF (sheet 2). The process starts at connector 3, calls CAMEL\_IMCN MO\_O\_IM\_CSI\_INIT, then checks the result. If 'Pass', it calls CAMEL\_IMCN MO\_D\_IM\_CSI\_INIT and checks the result again. If 'Pass', it checks for a CAMEL\_Invocation. If 'True', it sends an INVITE, starts timer Tb, and waits for an answer. If 'False', it checks for 606 Not Acceptable. If 'Fail' at the first result check, it checks for 606 Not Acceptable. If 'Abort', it checks for 487 Request Terminated. If 'INVITE Expires', it sets an event 'Timer expired', calls CAMEL\_IMCN MO\_CANCEL, and checks for 487 Request Terminated. All successful paths lead to connector 2, then Release Call Resources, and finally Idle. All error/abort paths lead to connector 2, then Release Call Resources, and finally Idle. + +Figure 4.13-2: Process MO\_IM\_SSF (sheet 2) + +![Flowchart for Process MO_IM_SSF. The process starts with 'Wait_For_Answer'. It branches based on responses: '100 Trying' leads to 'Cancel_Received?'; '1xx except 100' leads to '1xx' and then to 'Cancel_Received?'; '200 OK' leads to 'Final_Response_Received := True', 'Stop Tb', and 'CAMEL_IMCN MO_ANSWER'. From 'Cancel_Received?', 'False' leads to 'Provisional_Response_Received := True' and 'Wait_For_Answer'; 'True' leads to 'CANCEL', 'CAMEL_IMCN MO_CANCEL', '487 Request Terminated', '200 OK', and connector '2'. From 'Final_Response_Received := True', the flow goes to 'CAMEL_IMCN MO_ANSWER' and then to 'Result?'. 'Result?' has 'Pass' leading to '200 OK', 'Stop Tininvite', 'Start Tack', and 'Wait_For_ACK'; 'Reconnect' leads to connector '1'; 'Fail' leads to connector '2'.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +**Process MO\_IM\_SSF** 3(6) + +Process in IM-SSF to perform Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the destination S-CSCF via S-CSCF, unless otherwise stated. \*/ + +Same Response Code + +``` +graph TD; Start([Wait_For_Answer]) --> J1(( )); J1 --> T1{100 Trying}; J1 --> T2{1xx except 100}; J1 --> T3{200 OK}; T1 --> CR{Cancel_Received?}; T2 --> T2_1{1xx}; T2_1 --> CR; T3 --> FR[Final_Response_Received := True]; FR --> ST[Stop Tb]; ST --> CIMO[CAMEL_IMCN MO_ANSWER]; CIMO --> R{Result?}; R -- Pass --> R200{200 OK}; R200 --> STI[Stop Tininvite]; STI --> STK[Start Tack]; STK --> WFA([Wait_For_ACK]); R -- Reconnect --> C1((1)); R -- Fail --> C2((2)); CR -- True --> CANCEL{CANCEL}; CANCEL --> CIMOC[CAMEL_IMCN MO_CANCEL]; CIMOC --> RT{487 Request Terminated}; RT --> OK2{200 OK}; OK2 --> C2; CR -- False --> PR[Provisional_Response_Received := True]; PR --> WFA; WFA --> J1; +``` + +Flowchart for Process MO\_IM\_SSF. The process starts with 'Wait\_For\_Answer'. It branches based on responses: '100 Trying' leads to 'Cancel\_Received?'; '1xx except 100' leads to '1xx' and then to 'Cancel\_Received?'; '200 OK' leads to 'Final\_Response\_Received := True', 'Stop Tb', and 'CAMEL\_IMCN MO\_ANSWER'. From 'Cancel\_Received?', 'False' leads to 'Provisional\_Response\_Received := True' and 'Wait\_For\_Answer'; 'True' leads to 'CANCEL', 'CAMEL\_IMCN MO\_CANCEL', '487 Request Terminated', '200 OK', and connector '2'. From 'Final\_Response\_Received := True', the flow goes to 'CAMEL\_IMCN MO\_ANSWER' and then to 'Result?'. 'Result?' has 'Pass' leading to '200 OK', 'Stop Tininvite', 'Start Tack', and 'Wait\_For\_ACK'; 'Reconnect' leads to connector '1'; 'Fail' leads to connector '2'. + +Figure 4.13-3: Process MO\_IM\_SSF (sheet 3) + +![State transition diagram for Process MO_IM_SSF. It starts with 'Wait_For_Answer' and branches based on 'CANCEL', '4xx, 5xx, 6xx', 'Tb expiry', and 'Tinvite expiry' events. It includes decision diamonds for 'Provisional Response Received?', 'Cancel_Received := True', 'CAMEL_IMCN_MO_CANCEL', 'CAMEL_IMCN_MO_UNSUCCESSFUL', and 'Result = Reconnect?'. It ends at connector circles 1, 2, and 4.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +### Process MO\_IM\_SSF 4(6) + +Process in IM-SSF to perform Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the destination S-CSCF via S-CSCF, unless otherwise stated. \*/ + +``` +stateDiagram-v2 + [*] --> Wait_For_Answer + state "Wait_For_Answer" as Wait_For_Answer + state "Provisional Response Received ?" as Provisional_Response_Received + state "Cancel_Received := True" as Cancel_Received + state "CAMEL_IMCN_MO_CANCEL" as CAMEL_IMCN_MO_CANCEL + state "CAMEL_IMCN_MO_UNSUCCESSFUL" as CAMEL_IMCN_MO_UNSUCCESSFUL + state "Result = Reconnect ?" as Result_Reconnect + state "Event := (Response Code)" as Event_Response_Code + state "Event := 'Timer expired'" as Event_Timer_Expired + state "4xx, 5xx, 6xx" as Four_xx_5_xx_6_xx + state "ACK" as ACK + state "487 Request Terminated" as Four_8_7_Request_Terminated + state "200 OK" as Two_0_0_OK + state "Tb expiry" as Tb_expiry + state "Tinvite expiry" as Tinvite_expiry + state "1" as Connector_1 + state "2" as Connector_2 + state "4" as Connector_4 + + Wait_For_Answer --> Provisional_Response_Received + Provisional_Response_Received --> Wait_For_Answer : False + Provisional_Response_Received --> Cancel_Received : True + Provisional_Response_Received --> CAMEL_IMCN_MO_CANCEL : True + Provisional_Response_Received --> Four_xx_5_xx_6_xx : True + Provisional_Response_Received --> Tb_expiry : True + Provisional_Response_Received --> Tinvite_expiry : True + Cancel_Received --> Wait_For_Answer + CAMEL_IMCN_MO_CANCEL --> Four_8_7_Request_Terminated + Four_8_7_Request_Terminated --> Two_0_0_OK + Two_0_0_OK --> Connector_2 + Event_Response_Code --> Event_Timer_Expired + Event_Timer_Expired --> CAMEL_IMCN_MO_UNSUCCESSFUL + CAMEL_IMCN_MO_UNSUCCESSFUL --> Result_Reconnect + Result_Reconnect --> Connector_1 : Yes + Result_Reconnect --> Connector_2 : No + Tb_expiry --> Provisional_Response_Received + Provisional_Response_Received --> CANCEL : No + Provisional_Response_Received --> Event_Timer_Expired : Yes + Tinvite_expiry --> Provisional_Response_Received + Provisional_Response_Received --> CANCEL : No + Provisional_Response_Received --> Connector_4 : Yes +``` + +State transition diagram for Process MO\_IM\_SSF. It starts with 'Wait\_For\_Answer' and branches based on 'CANCEL', '4xx, 5xx, 6xx', 'Tb expiry', and 'Tinvite expiry' events. It includes decision diamonds for 'Provisional Response Received?', 'Cancel\_Received := True', 'CAMEL\_IMCN\_MO\_CANCEL', 'CAMEL\_IMCN\_MO\_UNSUCCESSFUL', and 'Result = Reconnect?'. It ends at connector circles 1, 2, and 4. + +Figure 4.13-4: Process MO\_IM\_SSF (sheet 4) + +![State transition diagram for Process MO_IM_SSF. It starts with a 'Wait_For_ACK' state. Transitions include: ACK leading to 'Stop Tack' then a 'Bye_Received?' decision; BYE leading to an 'Ack_Received?' decision; another BYE leading to 'CAMEL_IMCN MO_DISC1'; and 'Tack expiry' leading to a 'BYE' state. The 'Ack_Received?' decision leads to 'CAMEL_IMCN MO_DISC2' (True) or 'Bye_Received := True' (False). 'CAMEL_IMCN MO_DISC2' leads to a 'Result = Reconnect?' decision. 'Bye_Received := True' leads to 'Wait_For_ACK'. 'Result = Reconnect?' leads to state 1 (Yes) or state 2 (No). 'Bye_Received?' (after Stop Tack) leads to 'Ack_Received := True' (False) or state 1 (True). 'Ack_Received := True' leads to 'ACK' then 'Wait_For_Clear'. 'ACK' (after BYE) leads to 'BYE' then 'CAMEL_IMCN MO_DISC1'. 'CAMEL_IMCN MO_DISC1' leads to state 2.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +### Process MO\_IM\_SSF + +5(6) + +Process in IM-SSF to perform Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the destination S-CSCF via S-CSCF, unless otherwise stated. \*/ + +``` +stateDiagram-v2 + [*] --> Wait_For_ACK + state "ACK" as ACK + state "BYE" as BYE + state "BYE" as BYE2 + state "Tack expiry" as Tack_expiry + state "BYE" as BYE3 + state "Stop Tack" as Stop_Tack + state "Ack_Received?" as Ack_Received + state "CAMEL_IMCN MO_DISC2" as CAMEL_IMCN_MO_DISC2 + state "Bye_Received := True" as Bye_Received_T + state "Wait_For_ACK" as Wait_For_ACK2 + state "Result = Reconnect?" as Result_Reconnect + state "Bye_Received?" as Bye_Received + state "Ack_Received := True" as Ack_Received_T + state "ACK" as ACK2 + state "Wait_For_Clear" as Wait_For_Clear + state "1" as 1 + state "2" as 2 + state "CAMEL_IMCN MO_DISC1" as CAMEL_IMCN_MO_DISC1 + + Note right of [*] : Internal + + Wait_For_ACK --> ACK + Wait_For_ACK --> BYE + Wait_For_ACK --> BYE2 + Wait_For_ACK --> Tack_expiry + + ACK --> Stop_Tack + Stop_Tack --> Bye_Received + Bye_Received -- True --> [*] + Bye_Received -- False --> Ack_Received_T + Ack_Received_T --> ACK2 + ACK2 --> Wait_For_Clear + + BYE --> Ack_Received + Ack_Received -- True --> CAMEL_IMCN_MO_DISC2 + Ack_Received -- False --> Bye_Received_T + Bye_Received_T --> Wait_For_ACK2 + + BYE2 --> CAMEL_IMCN_MO_DISC1 + CAMEL_IMCN_MO_DISC1 --> 2 + + Tack_expiry --> BYE3 + BYE3 --> Bye_Received + Bye_Received -- True --> [*] + Bye_Received -- False --> ACK2 + ACK2 --> BYE3 + BYE3 --> CAMEL_IMCN_MO_DISC1 + CAMEL_IMCN_MO_DISC1 --> 2 + + CAMEL_IMCN_MO_DISC2 --> Result_Reconnect + Result_Reconnect -- Yes --> 1 + Result_Reconnect -- No --> [*] +``` + +State transition diagram for Process MO\_IM\_SSF. It starts with a 'Wait\_For\_ACK' state. Transitions include: ACK leading to 'Stop Tack' then a 'Bye\_Received?' decision; BYE leading to an 'Ack\_Received?' decision; another BYE leading to 'CAMEL\_IMCN MO\_DISC1'; and 'Tack expiry' leading to a 'BYE' state. The 'Ack\_Received?' decision leads to 'CAMEL\_IMCN MO\_DISC2' (True) or 'Bye\_Received := True' (False). 'CAMEL\_IMCN MO\_DISC2' leads to a 'Result = Reconnect?' decision. 'Bye\_Received := True' leads to 'Wait\_For\_ACK'. 'Result = Reconnect?' leads to state 1 (Yes) or state 2 (No). 'Bye\_Received?' (after Stop Tack) leads to 'Ack\_Received := True' (False) or state 1 (True). 'Ack\_Received := True' leads to 'ACK' then 'Wait\_For\_Clear'. 'ACK' (after BYE) leads to 'BYE' then 'CAMEL\_IMCN MO\_DISC1'. 'CAMEL\_IMCN MO\_DISC1' leads to state 2. + +Figure 4.13-5: Process MO\_IM\_SSF (sheet 5) + +![Flowchart for Process MO_IM_SSF. It starts with 'Wait_For_Clear', then branches into three paths: 1) BYE -> CAMEL_IMCN_MO_DISC1 -> connector 2; 2) BYE -> CAMEL_IMCN_MO_DISC2 -> Result = Reconnect? (No -> connector 2, Yes -> connector 1); 3) Int_Release Call (From imcnSSF) -> BYE -> BYE -> connector 2.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +### Process MO\_IM\_SSF + +6(6) + +Process in IM-SSF to perform Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the destination S-CSCF via S-CSCF, unless otherwise stated. \*/ + +``` +graph TD; Start([Wait_For_Clear]) --> BYE1[/BYE/]; Start --> BYE2[/BYE/]; Start --> Int_Release[Int_Release Call]; Int_Release --- From_imcnSSF[From imcnSSF]; BYE1 --> CAMEL_IMCN_MO_DISC1[CAMEL_IMCN_MO_DISC1]; BYE2 --> CAMEL_IMCN_MO_DISC2[CAMEL_IMCN_MO_DISC2]; CAMEL_IMCN_MO_DISC1 --> J1(( )); CAMEL_IMCN_MO_DISC2 --> Reconnect{Result = Reconnect?}; Reconnect -- No --> J1; Reconnect -- Yes --> J2(( )); Int_Release --> BYE3[/BYE/]; BYE3 --> BYE4[/BYE/]; BYE4 --> J1; +``` + +Flowchart for Process MO\_IM\_SSF. It starts with 'Wait\_For\_Clear', then branches into three paths: 1) BYE -> CAMEL\_IMCN\_MO\_DISC1 -> connector 2; 2) BYE -> CAMEL\_IMCN\_MO\_DISC2 -> Result = Reconnect? (No -> connector 2, Yes -> connector 1); 3) Int\_Release Call (From imcnSSF) -> BYE -> BYE -> connector 2. + +Figure 4.13-6: Process MO\_IM\_SSF (sheet 6) + +## Procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT + +1(3) + +/\* Procedure in the IM-SSF to perform CAMEL handling for an outgoing call INVITE request \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_O_IM_CSI_INIT](26e334e61dd059cff029338a2a604d8d_img.jpg) + +``` +graph TD; Start([ ]) --> Decision{O-IM-CSI invocation?}; Decision -- No --> Pass[Result:= Pass]; Pass --> Exit1(( )); Decision -- Yes --> True[CAMEL_Invocation := True]; True --> Store[Store original call parameters]; Store --> Invoke[Int_Invoke_imcnSSF O-IM-CSI]; Invoke --> Wait[Wait for imcnSSF_Invoked]; Wait --> Error{Int_Error}; Wait --> Invoked{Int_imcnSSF_Invoked}; Wait --> Cancel{CANCEL}; Error --> Fail[Result:= Fail]; Fail --> Exit2(( )); Invoked --> Info[Int_DP_Collected_Info]; Info --> DP[DP_Collected_Info]; DP --> Exit3(( )); Cancel --> CANCEL_MSG[CAMEL_IMCN_MO_CANCEL]; CANCEL_MSG --> Abort[Result:= Abort]; Abort --> Exit4(( )); +``` + +The flowchart illustrates the procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT. It begins with a start symbol leading to a decision diamond 'O-IM-CSI invocation?'. If 'No', it proceeds to 'Result:= Pass' and then to an exit symbol. If 'Yes', it proceeds to 'CAMEL\_Invocation := True', then 'Store original call parameters', then 'Int\_Invoke\_imcnSSF (O-IM-CSI)', and then 'Wait for imcnSSF\_Invoked'. From the wait state, three paths emerge: 'Int\_Error' leads to 'Result:= Fail' and an exit symbol; 'Int\_imcnSSF\_Invoked' leads to 'Int\_DP\_Collected\_Info', then 'DP\_Collected\_Info', and then an exit symbol; 'CANCEL' leads to 'CAMEL\_IMCN\_MO\_CANCEL', then 'Result:= Abort', and then an exit symbol. + +Flowchart for Procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT + +Figure 4.14-1: Procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT (sheet 1) + +### Procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT + +2(3) + +/\* Procedure in the IM-SSF to perform CAMEL handling for an outgoing call INVITE request \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_O_IM_CSI_INIT. It starts with 'DP Collected_Info' leading to five signal options: Int_Release_Call, Int_Error, Int_Connect, Int_Continue_With_Argument, and Int_Continue. Int_Continue_With_Argument leads to a 'Modify call parameters' block, which then leads to a decision 'Default call handling = continue call?'. Int_Error also leads to this decision. Int_Release_Call leads to 'Result:= Fail'. Int_Connect and Int_Continue lead to 'Result:= Pass'. Both results lead to a final connector symbol.](52e112d1ba42a3c660bf62a0fea927d3_img.jpg) + +``` +graph TD; DP[DP Collected_Info] --> Int_Release_Call[Int_Release_Call]; DP --> Int_Error[Int_Error]; DP --> Int_Connect[Int_Connect]; DP --> Int_Continue_With_Argument[Int_Continue_With_Argument]; DP --> Int_Continue[Int_Continue]; Int_Continue_With_Argument --> Modify[Modify call parameters with received information]; Modify --> Decision{Default call handling = continue call?}; Int_Error --> Decision; Int_Release_Call --> Fail[Result:= Fail]; Int_Connect --> Pass[Result:= Pass]; Int_Continue --> Pass; Fail --> End(( )); Pass --> End; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT. It starts with 'DP Collected\_Info' leading to five signal options: Int\_Release\_Call, Int\_Error, Int\_Connect, Int\_Continue\_With\_Argument, and Int\_Continue. Int\_Continue\_With\_Argument leads to a 'Modify call parameters' block, which then leads to a decision 'Default call handling = continue call?'. Int\_Error also leads to this decision. Int\_Release\_Call leads to 'Result:= Fail'. Int\_Connect and Int\_Continue lead to 'Result:= Pass'. Both results lead to a final connector symbol. + +Figure 4.14-2: Procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT (sheet 2) + +### Procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT + +3(3) + +/\* Procedure in the IM-SSF to perform CAMEL handling for an outgoing call INVITE request \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_O_IM_CSI_INIT. It starts with 'Internal' and 'DP_Collected_Info' leading to a parallel block. The parallel block contains 'Tinvite expiry' leading to 'Result := INVITE Expires', 'Int_Connect_To_Resource' leading to 'CAMEL_OCH_CTR', and 'CANCEL' leading to 'CAMEL_IMCN_MO_CANCEL'. 'CAMEL_OCH_CTR' leads to a decision 'Result = Fail?'. If 'No', it leads to 'DP_Collected_Info'. If 'Yes', it leads to 'Result := Fail'. Both 'Result := Fail' and 'CAMEL_IMCN_MO_CANCEL' leading to 'Result := Abort' lead to a common exit point.](43979979715bb3304389a0cb18f34444_img.jpg) + +``` +graph TD; Internal[Internal] --- DP_Collected_Info_1((DP_Collected_Info)); DP_Collected_Info_1 --- Tinvite_expiry{Tinvite expiry}; DP_Collected_Info_1 --- Int_Connect_To_Resource{Int_Connect_To_Resource}; DP_Collected_Info_1 --- CANCEL{CANCEL}; Tinvite_expiry --- Result_Inv[Result := INVITE Expires]; Result_Inv --- Exit1(( )); Int_Connect_To_Resource --- CAMEL_OCH_CTR[CAMEL_OCH_CTR]; CAMEL_OCH_CTR --- Result_Fail{Result = Fail?}; Result_Fail -- No --> DP_Collected_Info_2((DP_Collected_Info)); Result_Fail -- Yes --> Result_Fail_2[Result := Fail]; CANCEL --- CAMEL_IMCN_MO_CANCEL[CAMEL_IMCN_MO_CANCEL]; CAMEL_IMCN_MO_CANCEL --- Result_Abort[Result := Abort]; Result_Fail_2 --- Exit2(( )); Result_Abort --- Exit2; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT. It starts with 'Internal' and 'DP\_Collected\_Info' leading to a parallel block. The parallel block contains 'Tinvite expiry' leading to 'Result := INVITE Expires', 'Int\_Connect\_To\_Resource' leading to 'CAMEL\_OCH\_CTR', and 'CANCEL' leading to 'CAMEL\_IMCN\_MO\_CANCEL'. 'CAMEL\_OCH\_CTR' leads to a decision 'Result = Fail?'. If 'No', it leads to 'DP\_Collected\_Info'. If 'Yes', it leads to 'Result := Fail'. Both 'Result := Fail' and 'CAMEL\_IMCN\_MO\_CANCEL' leading to 'Result := Abort' lead to a common exit point. + +Figure 4.14-3: Procedure CAMEL\_IMCN\_MO\_O\_IM\_CSI\_INIT (sheet 3) + +![Flowchart for Procedure CAMEL_IMCN_MO_D_IM_CSI_INIT. The process starts with a connector, leading to a decision 'D-IM-CSI invocation?'. If 'No', it goes to 'Result := Pass' and ends. If 'Yes', it sets 'CAMEL_Invocation := True', stores original call parameters, invokes 'Int_Invoke_imcnSSF (D-IM-CSI)', and waits for 'imcnSSF_Invoked'. From there, it branches: if 'Int_imcnSSF_Invoked' is true, it proceeds to 'Int_DP_Analysed_Info', then 'DP_Analysed_Info', and ends; if 'CANCEL' is received, it sends 'CAMEL_IMCN MO_CANCEL', sets 'Result := Abort', and ends.](8269648391c59363ea61243864a2adf7_img.jpg) + +### Procedure CAMEL\_IMCN\_MO\_D\_IM\_CSI\_INIT 1(3) + +/\* Procedure in the IM-SSF to perform CAMEL handling for a subscribed Dialled Service \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; Start([ ]) --> Decision{D-IM-CSI invocation?}; Decision -- No --> ResultPass[Result := Pass]; ResultPass --> EndPass(( )); Decision -- Yes --> CAMELTrue[CAMEL_Invocation := True]; CAMELTrue --> StoreParams[Store Original Call Parameters]; StoreParams --> InvokeImcnSSF{Int_Invoke_imcnSSF (D-IM-CSI)}; InvokeImcnSSF --> WaitImcnSSF([Wait_for_imcnSSF_Invoked]); WaitImcnSSF --> ImcnSSFInvoked{Int_imcnSSF_Invoked}; ImcnSSFInvoked -- Yes --> DPAnalysedInfo{Int_DP_Analysed_Info}; DPAnalysedInfo --> DPAnalysedInfoOut([DP_Analysed_Info]); DPAnalysedInfoOut --> EndDP(( )); ImcnSSFInvoked -- No --> CANCEL{CANCEL}; CANCEL --> IMCNCancel[CAMEL_IMCN MO_CANCEL]; IMCNCancel --> ResultAbort[Result := Abort]; ResultAbort --> EndAbort(( )); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_D\_IM\_CSI\_INIT. The process starts with a connector, leading to a decision 'D-IM-CSI invocation?'. If 'No', it goes to 'Result := Pass' and ends. If 'Yes', it sets 'CAMEL\_Invocation := True', stores original call parameters, invokes 'Int\_Invoke\_imcnSSF (D-IM-CSI)', and waits for 'imcnSSF\_Invoked'. From there, it branches: if 'Int\_imcnSSF\_Invoked' is true, it proceeds to 'Int\_DP\_Analysed\_Info', then 'DP\_Analysed\_Info', and ends; if 'CANCEL' is received, it sends 'CAMEL\_IMCN MO\_CANCEL', sets 'Result := Abort', and ends. + +Figure 4.15-1: Procedure CAMEL\_IMCN\_MO\_D\_IM\_CSI\_INIT (sheet 1) + +![Flowchart for Procedure CAMEL_IMCN_MO_D_IM_CSI_INIT. It starts with DP_Analysed_Info, leading to a horizontal line with five options: Int_Release_Call, Int_Error, Int_Connect, Int_Continue_With_Argument, and Int_Continue. Int_Continue_With_Argument leads to a 'Modify call parameters with received information' block, which then leads to a decision diamond 'Default call handling = continue call?'. From the diamond, 'No' leads to Result:= Fail and 'Yes' leads to Result:= Pass. Both Result blocks lead to a common exit circle.](32ff77da4286b58c4778033acaa10836_img.jpg) + +### Procedure CAMEL\_IMCN\_MO\_D\_IM\_CSI\_INIT 2(3) + +/\* Procedure in the IM-SSF to perform CAMEL handling for a subscribed Dialled Service \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; DP[DP_Analysed_Info] --> H1(( )); subgraph H1 [ ]; direction LR; I1[Int_Release_Call]; I2[Int_Error]; I3[Int_Connect]; I4[Int_Continue_With_Argument]; I5[Int_Continue]; end; I4 --> M[Modify call parameters with received information]; M --> D{Default call handling = continue call?}; D -- No --> R1[Result:= Fail]; D -- Yes --> R2[Result:= Pass]; R1 --> E(( )); R2 --> E +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_D\_IM\_CSI\_INIT. It starts with DP\_Analysed\_Info, leading to a horizontal line with five options: Int\_Release\_Call, Int\_Error, Int\_Connect, Int\_Continue\_With\_Argument, and Int\_Continue. Int\_Continue\_With\_Argument leads to a 'Modify call parameters with received information' block, which then leads to a decision diamond 'Default call handling = continue call?'. From the diamond, 'No' leads to Result:= Fail and 'Yes' leads to Result:= Pass. Both Result blocks lead to a common exit circle. + +Figure 4.15-2: Procedure CAMEL\_IMCN\_MO\_D\_IM\_CSI\_INIT (sheet 2) + +Procedure CAMEL\_IMCN\_MO\_D\_IM\_CSI\_INIT + +3(3) + +/\* Procedure in the IM-SSF to perform CAMEL handling for a subscribed Dialled Service \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_D_IM_CSI_INIT. It starts with 'Internal' and 'DP_Analysed_Info' leading to a decision 'Int_Connect_To_Resource'. From this decision, three paths emerge: 'Tinvite expiry' leading to 'Result := INVITE Expires' and an exit circle; 'CAMEL_OCH_CTR' leading to a decision 'Result = Fail?'; and 'CANCEL' leading to 'CAMEL_IMCN_MO_CANCEL' and 'Result := Abort'. The 'Result = Fail?' decision has a 'Yes' path to 'Result := Fail' and a 'No' path to 'DP_Analysed_Info'. Both 'Result := Fail' and 'Result := Abort' lead to a common exit circle.](ff5f89b660edddb67971d7d3d4ce87ef_img.jpg) + +``` +graph TD; Internal[Internal] --- DI1(( )); DI1 --- ICR{Int_Connect_To_Resource}; DI1 --- TINV{Tinvite expiry}; DI1 --- CANCEL{T}; ICR --> COCH[CAMEL_OCH_CTR]; COCH --> RF{Result = Fail?}; RF -- Yes --> RFail[Result := Fail]; RFail --> DI2(( )); RF -- No --> DI3[DP_Analysed_Info]; TINV --> RINV[Result := INVITE Expires]; RINV --> DI4(( )); CANCEL --> CIMC[CAMEL_IMCN_MO_CANCEL]; CIMC --> RAbort[Result := Abort]; RAbort --> DI2; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_D\_IM\_CSI\_INIT. It starts with 'Internal' and 'DP\_Analysed\_Info' leading to a decision 'Int\_Connect\_To\_Resource'. From this decision, three paths emerge: 'Tinvite expiry' leading to 'Result := INVITE Expires' and an exit circle; 'CAMEL\_OCH\_CTR' leading to a decision 'Result = Fail?'; and 'CANCEL' leading to 'CAMEL\_IMCN\_MO\_CANCEL' and 'Result := Abort'. The 'Result = Fail?' decision has a 'Yes' path to 'Result := Fail' and a 'No' path to 'DP\_Analysed\_Info'. Both 'Result := Fail' and 'Result := Abort' lead to a common exit circle. + +Figure 4.15-3: Procedure CAMEL\_IMCN\_MO\_D\_IM\_CSI\_INIT (sheet 3) + +# Procedure CAMEL\_IMCN\_MO\_CANCEL + +1(1) + +/\* Procedure in IM-SSF to perform CAMEL handling for an outgoing call CANCEL request. \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_CANCEL. It starts with a connector symbol, followed by a decision diamond 'imcnSSF Invoked?'. If 'No', it goes to a connector symbol. If 'Yes', it goes through 'Int_DP_O_Abandon', 'DP_O_Abandon', and 'Int_Continue' to a connector symbol.](a93de4c3f80bd4a972ab65510b09b68d_img.jpg) + +``` +graph TD; Start([ ]) --> Decision{imcnSSF Invoked?}; Decision -- No --> End([ ]); Decision -- Yes --> Int_DP_O_Abandon[Int_DP_O_Abandon]; Int_DP_O_Abandon --> DP_O_Abandon[DP_O_Abandon]; DP_O_Abandon --> Int_Continue[Int_Continue]; Int_Continue --> End; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_CANCEL. It starts with a connector symbol, followed by a decision diamond 'imcnSSF Invoked?'. If 'No', it goes to a connector symbol. If 'Yes', it goes through 'Int\_DP\_O\_Abandon', 'DP\_O\_Abandon', and 'Int\_Continue' to a connector symbol. + +Figure 4.16: Procedure CAMEL\_IMCN\_MO\_CANCEL (sheet 1) + +# Procedure CAMEL\_IMCN\_MO\_ANSWER + +1(2) + +/\* Procedure in the IM-SSF to handle an outgoing call Answer (200 OK) response from the terminating subscriber \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_ANSWER. It starts with a decision 'imcnSSF invoked?'. If 'No', it sets 'Result := Pass' and ends. If 'Yes', it sends 'Int_DP_O_Answer' and receives 'DP_O_Answer'. Then it branches into 'Int_Continue', 'Int_Release_Call', or 'Int_Error'. 'Int_Continue' leads to 'Result := Pass'. 'Int_Release_Call' leads to a '606 Not Acceptable' decision. If 'No', it goes to 'Default call handling = continue call?'. If 'Yes', it sends 'BYE' to the destination S-CSCF and sets 'Result := Fail'. 'Int_Error' leads to 'Result := Pass'. All three paths converge to an end connector.](052543d8c9c0643b05b3ce45c6decca1_img.jpg) + +``` +graph TD; Start([ ]) --> Decision1{imcnSSF invoked?}; Decision1 -- No --> Result1[Result := Pass]; Result1 --> End1(( )); Decision1 -- Yes --> Int_DP_O_Answer[Int_DP_O_Answer]; Int_DP_O_Answer --> DP_O_Answer[DP_O_Answer]; DP_O_Answer --> Int_Continue[Int_Continue]; DP_O_Answer --> Int_Release_Call[Int_Release_Call]; DP_O_Answer --> Int_Error[Int_Error]; Int_Continue --> Result2[Result := Pass]; Int_Release_Call --> 606{606 Not Acceptable}; 606 -- No --> Default[Default call handling = continue call?]; Default --> Int_Release_Call; 606 -- Yes --> BYE[BYE]; BYE --> Dest[To the destination S-CSCF]; BYE --> Result3[Result := Fail]; Int_Error --> Result4[Result := Pass]; Result2 --> End2(( )); Result3 --> End2; Result4 --> End2; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_ANSWER. It starts with a decision 'imcnSSF invoked?'. If 'No', it sets 'Result := Pass' and ends. If 'Yes', it sends 'Int\_DP\_O\_Answer' and receives 'DP\_O\_Answer'. Then it branches into 'Int\_Continue', 'Int\_Release\_Call', or 'Int\_Error'. 'Int\_Continue' leads to 'Result := Pass'. 'Int\_Release\_Call' leads to a '606 Not Acceptable' decision. If 'No', it goes to 'Default call handling = continue call?'. If 'Yes', it sends 'BYE' to the destination S-CSCF and sets 'Result := Fail'. 'Int\_Error' leads to 'Result := Pass'. All three paths converge to an end connector. + +Figure 4.17-1: Procedure CAMEL\_IMCN\_MO\_ANSWER (sheet 1) + +### Procedure CAMEL\_IMCN\_MO\_ANSWER + +2(2) + +/\* Procedure in the IM-SSF to handle an outgoing call Answer (200 OK) response from the terminating subscriber \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_ANSWER. It starts with DP_O_Answer, branches into two BYE messages (one from destination S-CSCF), followed by CAMEL_IMCN_MO_DISC1 and CAMEL_IMCN_MO_DISC2. A decision diamond 'Result = Reconnect?' follows. If 'No', Result := Fail. If 'Yes', Result := Reconnect. Both paths lead to a connector circle.](1316d63eca7b84e13c27f55f0027b7b5_img.jpg) + +``` +graph TD; DP_O_Answer([DP_O_Answer]) --> BYE1[/BYE/]; DP_O_Answer --> BYE2[/BYE/]; BYE2 --- Note[From the destination S-CSCF]; BYE1 --> DISC1[CAMEL_IMCN_MO_DISC1]; BYE2 --> DISC2[CAMEL_IMCN_MO_DISC2]; DISC1 --> Reconnect{Result = Reconnect?}; DISC2 --> Reconnect; Reconnect -- No --> Fail[Result := Fail]; Reconnect -- Yes --> ReconnectRes[Result := Reconnect]; Fail --> Connector(( )); ReconnectRes --> Connector +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_ANSWER. It starts with DP\_O\_Answer, branches into two BYE messages (one from destination S-CSCF), followed by CAMEL\_IMCN\_MO\_DISC1 and CAMEL\_IMCN\_MO\_DISC2. A decision diamond 'Result = Reconnect?' follows. If 'No', Result := Fail. If 'Yes', Result := Reconnect. Both paths lead to a connector circle. + +Figure 4.17-2: Procedure CAMEL\_IMCN\_MO\_ANSWER (sheet 2) + +![Flowchart for Procedure CAMEL_IMCN_MO_UNSUCCESSFUL. It starts with an oval connector, leading to a decision diamond 'Event?'. From the diamond, four paths lead to numbered circles 1, 2, 3, and 4. Path 1 is labeled with error codes: 4xx except 401, 407, 408, 413, 420, 480, 486; or 5xx; or 6xx except 600, 603. Path 2 is labeled 486, 600. Path 3 is labeled 480, 408, 603. Path 4 is labeled 'Timer expiry'.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +### Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL 1(6) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; Start([ ]) --> Event{Event?}; Event --> Path1[4xx except 401, 407, 408, 413, 420, 480, 486; or 5xx; or 6xx except 600, 603.]; Event --> Path2[486, 600]; Event --> Path3[480, 408, 603]; Event --> Path4[Timer expiry]; Path1 --> Circle1((1)); Path2 --> Circle2((2)); Path3 --> Circle3((3)); Path4 --> Circle4((4)); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL. It starts with an oval connector, leading to a decision diamond 'Event?'. From the diamond, four paths lead to numbered circles 1, 2, 3, and 4. Path 1 is labeled with error codes: 4xx except 401, 407, 408, 413, 420, 480, 486; or 5xx; or 6xx except 600, 603. Path 2 is labeled 486, 600. Path 3 is labeled 480, 408, 603. Path 4 is labeled 'Timer expiry'. + +Figure 4.18-1: Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL (sheet 1) + +### Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL + +2(6) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_UNSUCCESSFUL. It starts with a connector '1', followed by a decision 'imcnSSF invoked?'. If 'Yes', it goes through 'Int_DP_Route_Select_Failure' (input) and 'DP_Route_Select_Failure' (output). If 'No', it bypasses these. The flow then splits into four parallel paths: 'Int_Connect', 'Int_Continue', 'Int_Release_Call', and 'Int_Error'. 'Int_Connect' leads to 'Modify call parameters with received information' and 'Result := Reconnect'. 'Int_Continue', 'Int_Release_Call', and 'Int_Error' merge at a junction. From this junction, one path leads to a box labeled 'Same SIP 4XX, 5XX, or 6XX response received'. The other path from the junction leads to 'Wait_For_ACK_For_Error', then 'ACK', then 'Result := Continue'. Both 'Result := Reconnect' and 'Result := Continue' lead to an end connector.](fd76efce549d3713543bb5ed9b023c2e_img.jpg) + +Flowchart for Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL. It starts with a connector '1', followed by a decision 'imcnSSF invoked?'. If 'Yes', it goes through 'Int\_DP\_Route\_Select\_Failure' (input) and 'DP\_Route\_Select\_Failure' (output). If 'No', it bypasses these. The flow then splits into four parallel paths: 'Int\_Connect', 'Int\_Continue', 'Int\_Release\_Call', and 'Int\_Error'. 'Int\_Connect' leads to 'Modify call parameters with received information' and 'Result := Reconnect'. 'Int\_Continue', 'Int\_Release\_Call', and 'Int\_Error' merge at a junction. From this junction, one path leads to a box labeled 'Same SIP 4XX, 5XX, or 6XX response received'. The other path from the junction leads to 'Wait\_For\_ACK\_For\_Error', then 'ACK', then 'Result := Continue'. Both 'Result := Reconnect' and 'Result := Continue' lead to an end connector. + +Figure 4.18-2: Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL (sheet 2) + +### Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL + +3(6) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_UNSUCCESSFUL. It starts at connector '2', checks if 'imcnSSF invoked?'. If 'No', it goes to the right side. If 'Yes', it goes through 'Int_DP_O_Busy' and 'DP_O_Busy'. Then it branches into four options: 'Int_Connect', 'Int_Continue', 'Int_Error', and 'Int_Release_Call'. 'Int_Connect' leads to 'Modify call parameters with received information' and 'Result := Reconnect'. 'Int_Continue', 'Int_Error', and 'Int_Release_Call' all lead to a common junction. From this junction, 'Int_Error' leads to a box 'Same SIP 4XX, or 6XX response received', then 'Wait_For_ACK_For_Error', 'ACK', and 'Result := Continue'. Both 'Result := Reconnect' and 'Result := Continue' lead to a final connector symbol.](396197257cf9437b526bb6585b6a9c8a_img.jpg) + +Flowchart for Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL. It starts at connector '2', checks if 'imcnSSF invoked?'. If 'No', it goes to the right side. If 'Yes', it goes through 'Int\_DP\_O\_Busy' and 'DP\_O\_Busy'. Then it branches into four options: 'Int\_Connect', 'Int\_Continue', 'Int\_Error', and 'Int\_Release\_Call'. 'Int\_Connect' leads to 'Modify call parameters with received information' and 'Result := Reconnect'. 'Int\_Continue', 'Int\_Error', and 'Int\_Release\_Call' all lead to a common junction. From this junction, 'Int\_Error' leads to a box 'Same SIP 4XX, or 6XX response received', then 'Wait\_For\_ACK\_For\_Error', 'ACK', and 'Result := Continue'. Both 'Result := Reconnect' and 'Result := Continue' lead to a final connector symbol. + +Figure 4.18-3: Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL (sheet 3) + +![Flowchart for Procedure CAMEL_IMCN_MO_UNSUCCESSFUL. It starts at connector 3, checks if imcnSSF is invoked. If No, it goes to Int_Release_Call. If Yes, it sends Int_DP_O_No_Answer, then DP_O_No_Answer. It then branches into Int_Connect, Int_Continue, Int_Error, and Int_Release_Call. Int_Continue leads to Int_O_Exception. Int_Error leads to a merge point. Int_Release_Call leads to 'Same SIP 4XX response received' and then to the merge point. The merge point leads to Wait_For_ACK_For_Error, then ACK, then Result := Continue. Int_Connect leads to 'Modify call parameters with received information', then Result := Reconnect, which then leads to the exit connector.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +### Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL 4(6) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; 3((3)) --> imcnSSF{imcnSSF invoked?}; imcnSSF -- No --> Int_Release_Call[/Int_Release_Call/]; imcnSSF -- Yes --> Int_DP_O_No_Answer[/Int_DP_O_No_Answer/]; Int_DP_O_No_Answer --> DP_O_No_Answer([DP_O_No_Answer]); DP_O_No_Answer --> Int_Connect[/Int_Connect/]; DP_O_No_Answer --> Int_Continue[/Int_Continue/]; DP_O_No_Answer --> Int_Error[/Int_Error/]; DP_O_No_Answer --> Int_Release_Call; Int_Continue --> Int_O_Exception[/Int_O_Exception/]; Int_Error --> Merge{ }; Int_Release_Call --> SameSIP[Same SIP 4XX response received]; SameSIP --> Merge; Merge --> Wait_For_ACK_For_Error([Wait_For_ACK_For_Error]); Wait_For_ACK_For_Error --> ACK[/ACK/]; ACK --> Result_Continue[Result := Continue]; Int_Connect --> Modify[Modify call parameters with received information]; Modify --> Result_Reconnect[Result := Reconnect]; Result_Reconnect --> Exit((X)); Result_Continue --> Exit +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL. It starts at connector 3, checks if imcnSSF is invoked. If No, it goes to Int\_Release\_Call. If Yes, it sends Int\_DP\_O\_No\_Answer, then DP\_O\_No\_Answer. It then branches into Int\_Connect, Int\_Continue, Int\_Error, and Int\_Release\_Call. Int\_Continue leads to Int\_O\_Exception. Int\_Error leads to a merge point. Int\_Release\_Call leads to 'Same SIP 4XX response received' and then to the merge point. The merge point leads to Wait\_For\_ACK\_For\_Error, then ACK, then Result := Continue. Int\_Connect leads to 'Modify call parameters with received information', then Result := Reconnect, which then leads to the exit connector. + +Figure 4.18-4: Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL (sheet 4) + +![Flowchart for Procedure CAMEL_IMCN_MO_UNSUCCESSFUL. It starts at connector 4, checks if imcnSSF is invoked. If No, it goes to Int_Release_Call. If Yes, it sends Int_DP_O_No_Answer, then DP_O_No_Answer. From DP_O_No_Answer, it branches to Int_Connect, Int_Continue, Int_Error, and Int_Release_Call. Int_Connect leads to Modify call parameters and Result := Reconnect. Int_Continue leads to Int_O_Exception. Int_Error and Int_Release_Call both lead to 487 Request Terminated. From 487 Request Terminated, it goes to Wait_For_ACK_For_Error, then ACK, then Result := Continue. All three results (Reconnect, Continue, and the path from Int_O_Exception) lead to the end connector.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +### Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL 5(6) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; 4((4)) --> imcnSSF{imcnSSF invoked?}; imcnSSF -- No --> Int_Release_Call[/Int_Release_Call/]; imcnSSF -- Yes --> Int_DP_O_No_Answer[/Int_DP_O_No_Answer/]; Int_DP_O_No_Answer --> DP_O_No_Answer([DP_O_No_Answer]); DP_O_No_Answer --> Int_Connect[/Int_Connect/]; DP_O_No_Answer --> Int_Continue[/Int_Continue/]; DP_O_No_Answer --> Int_Error[/Int_Error/]; DP_O_No_Answer --> Int_Release_Call; Int_Connect --> Modify[Modify call parameters with received information]; Modify --> Result_Reconnect[Result := Reconnect]; Int_Continue --> Int_O_Exception[/Int_O_Exception/]; Int_Error --> 487{487 Request Terminated}; Int_Release_Call --> 487; 487 --> Wait_For_ACK[Wait_For_ACK_For_Error]; Wait_For_ACK --> ACK[/ACK/]; ACK --> Result_Continue[Result := Continue]; Result_Reconnect --> End((X)); Result_Continue --> End; Int_O_Exception --> End; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL. It starts at connector 4, checks if imcnSSF is invoked. If No, it goes to Int\_Release\_Call. If Yes, it sends Int\_DP\_O\_No\_Answer, then DP\_O\_No\_Answer. From DP\_O\_No\_Answer, it branches to Int\_Connect, Int\_Continue, Int\_Error, and Int\_Release\_Call. Int\_Connect leads to Modify call parameters and Result := Reconnect. Int\_Continue leads to Int\_O\_Exception. Int\_Error and Int\_Release\_Call both lead to 487 Request Terminated. From 487 Request Terminated, it goes to Wait\_For\_ACK\_For\_Error, then ACK, then Result := Continue. All three results (Reconnect, Continue, and the path from Int\_O\_Exception) lead to the end connector. + +Figure 4.18-5: Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL (sheet 5) + +### Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL + +6(6) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Originating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_UNSUCCESSFUL. It starts with an event box containing DP_O_Busy, DP_O_No_Answer, and DP_Route_Select_Failure. The flow splits into two paths: one labeled 'CANCEL' leading to 'CAMEL_IMCN_MO_CANCEL' and then to a 'Result ?' decision; the other labeled 'Int_Connect_To_Resource' leading to 'CAMEL_OCH_CTR' and then to the same 'Result ?' decision. From 'Result ?', a 'Fail' path leads to '487 Request Terminated' -> '200 OK' -> 'Result := Fail' -> exit symbol. A 'Pass' path leads to an exit symbol labeled '-'.](db5deafdae53dbc7d5972957f708c691_img.jpg) + +``` +graph TD; Start([DP_O_Busy
DP_O_No_Answer
DP_Route_Select_Failure]) --> CANCEL{CANCEL}; Start --> Int_Connect_To_Resource{Int_Connect_To_Resource}; CANCEL --> CAMEL_IMCN_MO_CANCEL[CAMEL_IMCN_MO_CANCEL]; Int_Connect_To_Resource --> CAMEL_OCH_CTR[CAMEL_OCH_CTR]; CAMEL_IMCN_MO_CANCEL --> Result{Result ?}; CAMEL_OCH_CTR --> Result; Result -- Fail --> 487[487 Request Terminated]; 487 --> 200[200 OK]; 200 --> Result_Fail[Result := Fail]; Result_Fail --> Exit1((X)); Result -- Pass --> Exit2([-]) +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL. It starts with an event box containing DP\_O\_Busy, DP\_O\_No\_Answer, and DP\_Route\_Select\_Failure. The flow splits into two paths: one labeled 'CANCEL' leading to 'CAMEL\_IMCN\_MO\_CANCEL' and then to a 'Result ?' decision; the other labeled 'Int\_Connect\_To\_Resource' leading to 'CAMEL\_OCH\_CTR' and then to the same 'Result ?' decision. From 'Result ?', a 'Fail' path leads to '487 Request Terminated' -> '200 OK' -> 'Result := Fail' -> exit symbol. A 'Pass' path leads to an exit symbol labeled '-'. + +Figure 4.18-6: Procedure CAMEL\_IMCN\_MO\_UNSUCCESSFUL (sheet 6) + +![Flowchart for Procedure CAMEL_IMCN_MO_DISC1. It starts with a connector, then a decision 'imcnSSF invoked?'. If 'No', it goes to 'Result := Continue'. If 'Yes', it sends 'Int_DP_O_Disconnect' (legId=1) to 'DP_O_Disconnect_1'. From there, it branches into 'Int_Error', 'Int_Release_Call', 'Int_Continue', and 'BYE' (from destination S-CSCF). 'Int_Error', 'Int_Release_Call', and 'Int_Continue' lead to a 'BYE' to destination S-CSCF, which then leads to '200 OK'. 'BYE' (from destination S-CSCF) leads to 'Int_DP_O_Disconnect' (legId=2) to 'DP_O_Disconnect_2'. From 'DP_O_Disconnect_2', it branches into 'Int_Continue', 'Int_Error', and 'Int_ReleaseCall', which all lead to a '200 OK' to destination S-CSCF. Both '200 OK' paths lead to 'Result := Continue'.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +### Procedure CAMEL\_IMCN\_MO\_DISC1 1(1) + +/\* Procedure in the IM-SSF to handle an outgoing call on the BYE request from caller\*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; Start([ ]) --> Decision{imcnSSF invoked?}; Decision -- No --> Result[Result := Continue]; Decision -- Yes --> Int_DP_O_Disconnect_1[Int_DP_O_Disconnect
[* legId = 1*]]; Int_DP_O_Disconnect_1 --> DP_O_Disconnect_1(DP_O_Disconnect_1); DP_O_Disconnect_1 --> Int_Error_1[Int_Error]; DP_O_Disconnect_1 --> Int_Release_Call_1[Int_Release_Call]; DP_O_Disconnect_1 --> Int_Continue_1[Int_Continue]; DP_O_Disconnect_1 --> BYE_1[BYE]; BYE_1 -- From the destination S-CSCF --> BYE_1; Int_Error_1 --> BYE_2[BYE]; Int_Release_Call_1 --> BYE_2; Int_Continue_1 --> BYE_2; BYE_2 -- To the destination S-CSCF --> BYE_2; BYE_2 --> OK_1{200 OK}; OK_1 --> Result; BYE_1 --> Int_DP_O_Disconnect_2[Int_DP_O_Disconnect
[* legId = 2*]]; Int_DP_O_Disconnect_2 --> DP_O_Disconnect_2(DP_O_Disconnect_2); DP_O_Disconnect_2 --> Int_Continue_2[Int_Continue]; DP_O_Disconnect_2 --> Int_Error_2[Int_Error]; DP_O_Disconnect_2 --> Int_ReleaseCall_2[Int_ReleaseCall]; Int_Continue_2 --> OK_2{200 OK}; Int_Error_2 --> OK_2; Int_ReleaseCall_2 --> OK_2; OK_2 -- To the destination S-CSCF --> OK_2; OK_2 --> Result; Result --> End(( )) +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_DISC1. It starts with a connector, then a decision 'imcnSSF invoked?'. If 'No', it goes to 'Result := Continue'. If 'Yes', it sends 'Int\_DP\_O\_Disconnect' (legId=1) to 'DP\_O\_Disconnect\_1'. From there, it branches into 'Int\_Error', 'Int\_Release\_Call', 'Int\_Continue', and 'BYE' (from destination S-CSCF). 'Int\_Error', 'Int\_Release\_Call', and 'Int\_Continue' lead to a 'BYE' to destination S-CSCF, which then leads to '200 OK'. 'BYE' (from destination S-CSCF) leads to 'Int\_DP\_O\_Disconnect' (legId=2) to 'DP\_O\_Disconnect\_2'. From 'DP\_O\_Disconnect\_2', it branches into 'Int\_Continue', 'Int\_Error', and 'Int\_ReleaseCall', which all lead to a '200 OK' to destination S-CSCF. Both '200 OK' paths lead to 'Result := Continue'. + +Figure 4.19: Procedure CAMEL\_IMCN\_MO\_DISC1 (sheet 1) + +![Flowchart for Procedure CAMEL_IMCN_MO_DISC2. It starts with a connector, leading to a decision 'imcnSSF invoked?'. If 'No', it goes to 'Result := Continue' and then to a connector. If 'Yes', it sends 'Int_DP_O_Disconnect' (legId=2) to the imcnSSF, then 'DP_O_Disconnect_2' to the MS. The MS responds with 'BYE', 'Int_Continue', 'Int_Release_Call', 'Int_Error', or 'Int_Connect'. 'Int_Continue', 'Int_Release_Call', and 'Int_Error' lead to a '200 OK' response. 'BYE' leads to 'Result := Continue' and then '200 OK'. 'Int_Connect' leads to 'Modify call parameters with received information', then 'Final Response Received := False', then 'Result := Reconnect', and finally '200 OK'. All '200 OK' responses lead to 'To the destination S-CSCF' and then to a connector. A 'BYE' from the imcnSSF also leads to 'Result := Continue' and then '200 OK'.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +### Procedure CAMEL\_IMCN\_MO\_DISC2 1(2) + +/\* Procedure in the IM-SSF to handle an outgoing call on the BYE request from callee\*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; Start(( )) --> Decision{imcnSSF invoked?}; Decision -- No --> Result1[Result := Continue]; Result1 --> Connector1(( )); Decision -- Yes --> IntDP[Int_DP_O_Disconnect +/* legId = 2 */]; IntDP --> DPO2[DP_O_Disconnect_2]; DPO2 --> BYE1[BYE]; DPO2 --> IntContinue1[Int_Continue]; DPO2 --> IntReleaseCall1[Int_Release_Call]; DPO2 --> IntError1[Int_Error]; DPO2 --> IntConnect1[Int_Connect]; BYE1 --> IntDP1[Int_DP_O_Disconnect +/* legId = 1 */]; IntDP1 --> DPO1[DP_O_Disconnect_1]; DPO1 --> IntError2[Int_Error]; DPO1 --> IntContinue2[Int_Continue]; DPO1 --> IntReleaseCall2[Int_Release_Call]; IntError2 --> OK1[200 OK]; IntContinue2 --> OK1; IntReleaseCall2 --> OK1; OK1 --> ResultContinue1[Result := Continue]; IntContinue1 --> BYE2[BYE]; IntReleaseCall1 --> BYE2; IntError1 --> BYE2; IntConnect1 --> Modify[Modify call parameters with received information]; Modify --> Final[Final Response Received := False]; Final --> ResultReconnect[Result := Reconnect]; ResultReconnect --> OK2[200 OK]; BYE2 --> ResultContinue2[Result := Continue]; ResultContinue2 --> OK2; OK2 --> ToS-CSCF[To the destination S-CSCF]; ToS-CSCF --> Connector2(( )); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_DISC2. It starts with a connector, leading to a decision 'imcnSSF invoked?'. If 'No', it goes to 'Result := Continue' and then to a connector. If 'Yes', it sends 'Int\_DP\_O\_Disconnect' (legId=2) to the imcnSSF, then 'DP\_O\_Disconnect\_2' to the MS. The MS responds with 'BYE', 'Int\_Continue', 'Int\_Release\_Call', 'Int\_Error', or 'Int\_Connect'. 'Int\_Continue', 'Int\_Release\_Call', and 'Int\_Error' lead to a '200 OK' response. 'BYE' leads to 'Result := Continue' and then '200 OK'. 'Int\_Connect' leads to 'Modify call parameters with received information', then 'Final Response Received := False', then 'Result := Reconnect', and finally '200 OK'. All '200 OK' responses lead to 'To the destination S-CSCF' and then to a connector. A 'BYE' from the imcnSSF also leads to 'Result := Continue' and then '200 OK'. + +Figure 4.20-1: Procedure CAMEL\_IMCN\_MO\_DISC2 (sheet 1) + +### Procedure CAMEL\_IMCN\_MO\_DISC2 + +2(2) + +/\* Procedure in the IM-SSF to handle an outgoing call on the BYE request from callee\*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MO_DISC2. The flow starts with DP_O_Disconnect_2, followed by Int_Connect_To_Resource, then CAMEL_OCH_CTR. A decision diamond 'Result = Fail?' follows. If 'No', it goes to DP_O_Disconnect_2. If 'Yes', it goes to Result := Continue, which then leads to a connector symbol.](d7948c38a18636aefecdd95388196460_img.jpg) + +``` +graph TD; A[DP_O_Disconnect_2] --> B[/Int_Connect_To_Resource/]; B --> C[CAMEL_OCH_CTR]; C --> D{Result = Fail?}; D -- No --> E[DP_O_Disconnect_2]; D -- Yes --> F[Result := Continue]; F --> G((X)); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MO\_DISC2. The flow starts with DP\_O\_Disconnect\_2, followed by Int\_Connect\_To\_Resource, then CAMEL\_OCH\_CTR. A decision diamond 'Result = Fail?' follows. If 'No', it goes to DP\_O\_Disconnect\_2. If 'Yes', it goes to Result := Continue, which then leads to a connector symbol. + +Figure 4.20-2: Procedure CAMEL\_IMCN\_MO\_DISC2 (sheet 2) + +Procedure CAMEL\_OCH\_CTR + +1(5) + +Procedure in the IM-SSF to handle a Connect To Resource operation. + +Signals to/from the left are to/from the MS. Signals to/from the right are to/from the imcnSSF unless otherwise stated. + +![Flowchart for Procedure CAMEL_OCH_CTR. It starts with a wait for PlayAnnc or Prompt_And_Collect request, then branches based on CAP_Play_Announcement, CAP_Prompt_And_Collect_User_Information, or Int_Disconnect_Forward_Connection. It handles 200 OK, Error response, BYE, and CANCEL messages, leading to states like Int_SRF_Connected, Int_CTR_Failed, or Await_SRF_Disconnection_Fail.](10b0dda884baae493ad958422d11b552_img.jpg) + +``` + +graph TD + Start([Start]) --> Wait1[Wait for PlayAnnc or Prompt_And_Collect request] + Wait1 --> CAP1[CAP_Play_Announcement] + Wait1 --> CAP2[CAP_Prompt_And_Collect_User_Information] + Wait1 --> Int1[Int_Disconnect_Forward_Connection] + CAP1 --> INVITE1[INVITE] + INVITE1 --> ToMRFC1[To MRFC] + CAP2 --> INVITE2[INVITE] + INVITE2 --> ToMRFC2[To MRFC] + Int1 --> Result1[Result:= pass] + ToMRFC1 --> Wait2[Wait for 200 OK] + ToMRFC2 --> Wait2 + Result1 --> Join1(( )) + Wait2 --> OK1[200 OK] + Wait2 --> Error[Error response] + Wait2 --> BYE1[BYE] + Wait2 --> CANCEL1[CANCEL] + OK1 --> FromMRFC1[From MRFC] + FromMRFC1 --> OK2[200 OK] + OK2 --> FromMRFC2[From MRFC] + FromMRFC2 --> ACK[ACK] + ACK --> ToMRFC3[To MRFC] + ToMRFC3 --> IntSRF[Int_SRF_Connected] + IntSRF --> Relay[Relay] + Error --> IntCTR[Int_CTR_Failed] + IntCTR --> Result2[Result:= pass] + Result2 --> Join2(( )) + BYE1 --> OK3[200 OK] + OK3 --> IntDP[Int_DP_O_Disconnect /* legID */] + IntDP --> BYE2[BYE] + BYE2 --> AwaitSRF[Await_SRF_Disconnection_Active] + AwaitSRF --> ToMRFC4[To MRFC] + CANCEL1 --> OK4[200 OK] + OK4 --> ReqTerminated[487 Request Terminated] + ReqTerminated --> IntDPA[Int_DP_O_Abandon /* legID */] + IntDPA --> DPA[DP_O_Abandon_DFC] + DPA --> IntContinue[Int_Continue] + IntContinue --> CANCEL2[CANCEL] + CANCEL2 --> ToMRFC5[To MRFC] + ToMRFC5 --> AwaitFail[Await_SRF_Disconnection_Fail] + +``` + +Flowchart for Procedure CAMEL\_OCH\_CTR. It starts with a wait for PlayAnnc or Prompt\_And\_Collect request, then branches based on CAP\_Play\_Announcement, CAP\_Prompt\_And\_Collect\_User\_Information, or Int\_Disconnect\_Forward\_Connection. It handles 200 OK, Error response, BYE, and CANCEL messages, leading to states like Int\_SRF\_Connected, Int\_CTR\_Failed, or Await\_SRF\_Disconnection\_Fail. + +Figure 4.21-1: Procedure CAMEL\_OCH\_CTR (sheet 1) + +# Procedure CAMEL\_OCH\_CTR + +2(5) + +Procedure in the IM-SSF to handle a Connect To Resource operation. + +Signals to/from the left are to/from the MS. Signals to/from the right are to/from the imcnSSF unless otherwise stated. + +![Sequence diagram for Procedure CAMEL_OCH_CTR. The process starts with a 'Relay' block. It branches into two main paths. The left path handles a 'BYE' signal from the MRFC, responds with '200 OK' to the MRFC, releases the SRF, and returns a 'pass' result. The right path handles an 'Int_Disconnect_Forward_Connection', sends a 'BYE' to the MRFC, and then enters an 'Await_SRF_Disconnection_Continue' state. From this state, it can receive 'BYE', 'CANCEL', or '200 OK' from the MRFC. 'BYE' leads to '200 OK', 'Int_DP_O_Disconnect', and a 'pass' result. 'CANCEL' leads to '200 OK', 'Int_DP_O_Abandon', 'DP_O_Abandon_Fail', 'Int_continue', and a 'fail' result. '200 OK' leads to 'Int_SRF_Released' and a 'pass' result.](b774dfc5023e15e9c352b97ca25a56d4_img.jpg) + +``` +graph TD; Relay([Relay]) --> BYE_L[BYE]; BYE_L --> From_MRFC_L[From MRFC]; BYE_L --> OK_L[200 OK]; OK_L --> To_MRFC_L[To MRFC]; OK_L --> SRF_L[Int_SRF_Released]; SRF_L --> Result_L[Result:= pass]; Result_L --> End_L(( )); Relay --> IDFC[Int_Disconnect_Forward_Connection]; IDFC --> BYE_R[BYE]; BYE_R --> To_MRFC_R[To MRFC]; BYE_R --> Await[Await_SRF_Disconnection_Continue]; Await --> BYE_R2[BYE]; BYE_R2 --> OK_R2[200 OK]; OK_R2 --> DP_O_D[Int_DP_O_Disconnect /* legID */]; DP_O_D --> Result_R2[Result:= pass]; Result_R2 --> End_R2(( )); Await --> CANCEL_R[CANCEL]; CANCEL_R --> OK_R3[200 OK]; OK_R3 --> DP_O_A[Int_DP_O_Abandon /* legID */]; DP_O_A --> Fail[DP_O_Abandon_Fail]; Fail --> Continue[Int_continue]; Continue --> Result_R3[Result:= fail]; Result_R3 --> End_R3(( )); Await --> OK_R4[200 OK]; OK_R4 --> From_MRFC_R[From MRFC]; OK_R4 --> SRF_R[Int_SRF_Released]; SRF_R --> Result_R4[Result:= pass]; Result_R4 --> End_R4(( )); +``` + +Sequence diagram for Procedure CAMEL\_OCH\_CTR. The process starts with a 'Relay' block. It branches into two main paths. The left path handles a 'BYE' signal from the MRFC, responds with '200 OK' to the MRFC, releases the SRF, and returns a 'pass' result. The right path handles an 'Int\_Disconnect\_Forward\_Connection', sends a 'BYE' to the MRFC, and then enters an 'Await\_SRF\_Disconnection\_Continue' state. From this state, it can receive 'BYE', 'CANCEL', or '200 OK' from the MRFC. 'BYE' leads to '200 OK', 'Int\_DP\_O\_Disconnect', and a 'pass' result. 'CANCEL' leads to '200 OK', 'Int\_DP\_O\_Abandon', 'DP\_O\_Abandon\_Fail', 'Int\_continue', and a 'fail' result. '200 OK' leads to 'Int\_SRF\_Released' and a 'pass' result. + +Figure 4.21-2: Procedure CAMEL\_OCH\_CTR (sheet 2) + +![Sequence diagram for Procedure CAMEL_OCH_CTR. The process starts with a relay and wait for PlayAnnc or Prompt_And_Collect_request. It then branches into three paths: BYE, CANCEL, and ACK. The BYE path leads to 200 OK, then Int_DP_O_Disconnect, then Wait_For_Disconnect_Forward_Connection. The CANCEL path leads to 200 OK, then Int_DP_O_Abandon, then DP_O_Abandon_DFC, then Int_Continue, then Wait_For_Disconnect_Forward_Connection. The ACK path leads to a terminal state.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +### Procedure CAMEL\_OCH\_CTR + +3(5) + +Procedure in the IM-SSF to handle a Connect To Resource operation. + +Signals to/from the left are to/from the MS. +Signals to/from the right are to/from the imcnSSF unless otherwise stated. + +``` +sequenceDiagram + participant MS + participant IM-SSF + Note right of IM-SSF: Relay, Wait for PlayAnnc or Prompt_And_Collect_request + IM-SSF->>MS: BYE + MS-->>IM-SSF: 200 OK + IM-SSF->>MS: Int_DP_O_Disconnect /* legID */ + MS-->>IM-SSF: Wait_For_Disconnect_Forward_Connection + IM-SSF->>MS: CANCEL + MS-->>IM-SSF: 200 OK + IM-SSF->>MS: Int_DP_O_Abandon /* legID */ + MS-->>IM-SSF: DP_O_Abandon_DFC + IM-SSF->>MS: Int_Continue + MS-->>IM-SSF: Wait_For_Disconnect_Forward_Connection + IM-SSF->>MS: ACK + MS-->>IM-SSF: - +``` + +Sequence diagram for Procedure CAMEL\_OCH\_CTR. The process starts with a relay and wait for PlayAnnc or Prompt\_And\_Collect\_request. It then branches into three paths: BYE, CANCEL, and ACK. The BYE path leads to 200 OK, then Int\_DP\_O\_Disconnect, then Wait\_For\_Disconnect\_Forward\_Connection. The CANCEL path leads to 200 OK, then Int\_DP\_O\_Abandon, then DP\_O\_Abandon\_DFC, then Int\_Continue, then Wait\_For\_Disconnect\_Forward\_Connection. The ACK path leads to a terminal state. + +Figure 4.21-3: Procedure CAMEL\_OCH\_CTR (sheet 3) + +# Procedure CAMEL\_OCH\_CTR + +4(5) + +Procedure in the IM-SSF to handle a Connect To Resource operation. + +Signals to/from the left are to/from the MS. +Signals to/from the right are to/from the imcnSSF unless otherwise stated. + +![Flowchart for Procedure CAMEL_OCH_CTR. The process starts with 'Wait_For_Disconnect_Forward_Connection', followed by 'Int_Disconnect_Forward_Connection'. A 'BYE' signal is sent 'To MRFC'. A decision 'Answer Received?' follows. If 'True', it goes to 'Await_SRF_Disconnection_Active', then receives a '200 OK From MRFC', sets 'Result:= pass', and ends. If 'False', it goes to 'Await_SRF_Disconnection_Fail', then receives a '200 OK From MRFC', sets 'Result:= fail', and ends.](ad555483986d7170a46ce72d164b5bc8_img.jpg) + +``` +graph TD; A[Wait_For_Disconnect_Forward_Connection] --> B[Int_Disconnect_Forward_Connection]; B --> C[BYE]; C --> D[To MRFC]; C --> E{Answer Received?}; E -- True --> F[Await_SRF_Disconnection_Active]; E -- False --> G[Await_SRF_Disconnection_Fail]; F --> H[200 OK]; H --> I[From MRFC]; I --> J[Result:= pass]; J --> K(( )); G --> L[200 OK]; L --> M[From MRFC]; M --> N[Result:= fail]; N --> O(( )); +``` + +Flowchart for Procedure CAMEL\_OCH\_CTR. The process starts with 'Wait\_For\_Disconnect\_Forward\_Connection', followed by 'Int\_Disconnect\_Forward\_Connection'. A 'BYE' signal is sent 'To MRFC'. A decision 'Answer Received?' follows. If 'True', it goes to 'Await\_SRF\_Disconnection\_Active', then receives a '200 OK From MRFC', sets 'Result:= pass', and ends. If 'False', it goes to 'Await\_SRF\_Disconnection\_Fail', then receives a '200 OK From MRFC', sets 'Result:= fail', and ends. + +Figure 4.21-4: Procedure CAMEL\_OCH\_CTR (sheet 4) + +![Sequence diagram for Procedure CAMEL_OCH_CTR. It shows four parallel lifelines: (Notification of PlayAnnc Completed), (Return of Prompt & Collect Result), CAP_Play_Announcement, and CAP_Prompt_And_Collect_User_Information. The first two lead to CAP_Specialised_ResourceReport and CAP_Prompt_And_Collect_User_Information ack respectively. The last two lead to (Play_Announcement) and (Prompt_And_Collect_User_Information) respectively. All four converge to a bottom Relay block.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +### Procedure CAMEL\_OCH\_CTR + +5(5) + +Procedure in the IM-SSF to handle a Connect To Resource operation. + +Signals to/from the left are to/from the MRFC. +Signals to/from the right are to/from the imcnSSF. + +``` +sequenceDiagram + participant MRFC + participant IMSSF + Note left of MRFC: Procedure in the IM-SSF to handle a Connect To Resource operation. + Note right of IMSSF: Signals to/from the left are to/from the MRFC. Signals to/from the right are to/from the imcnSSF. + + MRFC->>IMSSF: (Notification of PlayAnnc Completed) + IMSSF-->>MRFC: CAP_Specialised_ResourceReport + + MRFC->>IMSSF: (Return of Prompt & Collect Result) + IMSSF-->>MRFC: CAP_Prompt_And_Collect_User_Information ack + + MRFC->>IMSSF: CAP_Play_Announcement + IMSSF-->>MRFC: (Play_Announcement) + + MRFC->>IMSSF: CAP_Prompt_And_Collect_User_Information + IMSSF-->>MRFC: (Prompt_And_Collect_User_Information) + + Note right of IMSSF: Relay +``` + +Sequence diagram for Procedure CAMEL\_OCH\_CTR. It shows four parallel lifelines: (Notification of PlayAnnc Completed), (Return of Prompt & Collect Result), CAP\_Play\_Announcement, and CAP\_Prompt\_And\_Collect\_User\_Information. The first two lead to CAP\_Specialised\_ResourceReport and CAP\_Prompt\_And\_Collect\_User\_Information ack respectively. The last two lead to (Play\_Announcement) and (Prompt\_And\_Collect\_User\_Information) respectively. All four converge to a bottom Relay block. + +Figure 4.21-5: Procedure CAMEL\_OCH\_CTR (sheet 5) + +#### 4.6.1.4 Handling of Mobile Terminated IP Multimedia sessions in the IM-SSF + +The functional behaviour of the S-CSCF for handling terminating calls is specified in 3GPP TS 23.218[5]. The process and the procedures specific to CAMEL are specified in this subclause: + +- Process MT\_IM\_SSF; +- Procedure Check\_Registration; +- Procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT; +- Procedure CAMEL\_IMCN\_MT\_RECONNECT; +- Procedure CAMEL\_IMCN\_MT\_CANCEL; +- Procedure CAMEL\_IMCN\_MT\_ANSWER; +- Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL; +- Procedure CAMEL\_IMCN\_MT\_DISC1; +- Procedure CAMEL\_IMCN\_MT\_DISC2; +- Procedure CAMEL\_CAMEL\_MT\_CTR. + +Internal interface indicated with the "Int\_SRF\_" prefix within this subclause indicates internal interface with the MRFC. + +##### 4.6.1.4.1 Actions of the IM-SSF on receipt of Int\_Error + +The IM-SSF checks the default Call Handling parameter in the relevant CSI. + +If the default call handling is release, a BYE indication is sent to the originating CSCF. The IM-SSF then releases all resources and the invoked CAMEL procedure ends. + +If the call handling is continue, the IM-SSF continues processing without CAMEL support. + +##### 4.6.1.4.2 Actions of the IM-SSF on receipt of Int\_Release\_Call + +The IM-SSF BYE message is sent to the originating CSCF and resources are released. + +##### 4.6.1.4.3 Actions of the IM-SSF on receipt of Int\_Continue\_With\_Argument + +The IM-SSF shall replace the call parameters by the information received in the Int\_Continue\_With\_Argument message. Call parameters that are not included in the Int\_Continue\_With\_Argument\_Message are unchanged. + +##### 4.6.1.4.4 Actions of IM-SSF in procedure CAMEL\_IMCN\_MT\_INVITE for Unregistered Subscriber + +When querying the HSS for the subscriber's IM CSI data, the IM-SSF does not have to wait for the HSS's response on the first query before the subsequent queries are done. i.e. Sending of multiple Any Time Interrogation operations can be done in parallel. However, the IM-SSF shall wait for all the responses from the HSS before it shall continue with the handling of the terminating IP multimedia session. + +##### 4.6.1.4.5 Handling of procedure CAMEL\_MT\_CTR, sheet 1 + +The IM-SSF behaves as a B2BUA (Back-2-Back User Agent) when a SIP INVITE is received for an terminating call and SIP INVITE is sent to the MRFC (via S-CSCF) as a result of a CAP ConnectToResource request received from the SCF. + +A SIP response 100 Trying is sent after each INVITE but is not shown in the SDLs. + +The IM-SSF shall handle the 200 OK response from the MRFC as specified in 3GPP TS 23.218 [5]. + +##### 4.6.1.4.6 Handling of procedure CAMEL\_MT\_CTR, sheet 5 + +The specifics on transporting information between the MRFC and the Application Server such as the IM-SSF, has not been standardised in 3GPP Rel-5 specifications for IMS. i.e. the SIP method to return Prompt\_And\_Collect result from + +the MRFC to the IM-SSF, the SIP method for sending notification of play announcement completion to the IM-SSF when a request for a Specialised Resource Report was received, the SIP method to request the MRFC to play announcement and the SIP method to request the MRFC to prompt and collect user information, are not standardised. + +#### 4.6.1.4.7 Receipt of 100 Trying Provisional Response (Process MT\_IM\_SSF) + +The IM-SSF (acting as a B2BUA) uses the S-CSCF as a next-hop server when sending the SIP INVITE to the terminating subscriber. The 100 Trying provisional response received in the IM-SSF is actually generated and sent from the S-CSCF to indicate that the INVITE request has been received by the next-hop server (i.e. the S-CSCF) and is currently being processed. + +#### 4.6.1.4.8 Handling of internal timers in Process MT\_IM\_SSF + +For additional description on usage of internal timers in Process MT\_IM\_SSF, please refer to the description in clause 4.6.1.3.9. + +![Flowchart for Process MT_IM_SSF. The flow starts with an oval, followed by 'Idle', 'INVITE', '100 Trying', and 'Initialise values'. A callout box for 'Initialise values' lists: CAMEL_Invocation := False; Provisional_Response_Received := False; Final_Response_Received := False; Ack_Received := False; Cancel_Received := False; Bye_Received := False. Next is a decision 'INVITE Expires received?'. 'Yes' leads to 'Tinvite := INVITE Expires received' and 'Start Tinvite'. 'No' leads to connector '3'. Both 'Start Tinvite' and '3' lead to a final connector '3'.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +### Process MT\_IM\_SSF 1(6) + +Process in IM-SSF to perform Mobile Terminating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the originating S-CSCF via S-CSCF, unless otherwise stated. \*/ + +``` +graph TD; Start([ ]) --> Idle[Idle]; Idle --> INVITE[INVITE]; INVITE --> 100Trying[100 Trying]; 100Trying --> Init[Initialise values]; Init --> InitCallout[CAMEL_Invocation := False; Provisional_Response_Received := False; Final_Response_Received := False; Ack_Received := False; Cancel_Received := False; Bye_Received := False]; Init --> Decision{INVITE Expires received?}; Decision -- Yes --> TinviteCalc[Tinvite := INVITE Expires received]; TinviteCalc --> StartTinvite[Start Tinvite]; Decision -- No --> Connector3((3)); StartTinvite --> Connector3; Connector3 --> EndConnector((3)); +``` + +Flowchart for Process MT\_IM\_SSF. The flow starts with an oval, followed by 'Idle', 'INVITE', '100 Trying', and 'Initialise values'. A callout box for 'Initialise values' lists: CAMEL\_Invocation := False; Provisional\_Response\_Received := False; Final\_Response\_Received := False; Ack\_Received := False; Cancel\_Received := False; Bye\_Received := False. Next is a decision 'INVITE Expires received?'. 'Yes' leads to 'Tinvite := INVITE Expires received' and 'Start Tinvite'. 'No' leads to connector '3'. Both 'Start Tinvite' and '3' lead to a final connector '3'. + +Figure 4.22-1: Process MT\_IM\_SSF (sheet 1) + +![Flowchart for Process MT_IM_SSF (sheet 2). The process starts at connector 3, proceeds to Check Registration, then a Result? decision. If Fail, it goes to connector 1. If Pass, it sends CAMEL_IMCN_MT_VT_IM_CSI_INIT, then another Result? decision. If Fail, it goes to connector 1. If Pass, it sends an INVITE message, starts timer Tb, and waits for an MT Answer. If the INVITE result is Pass, it establishes the connection and goes Idle. If the INVITE result is Fail, it sends CAMEL_IMCN_MT_RECONNECT, then a Result? decision. If Fail, it goes to connector 1. If Pass, it establishes the connection and goes Idle. If the second Result? decision fails, it sends a 606 Not Acceptable message and goes to connector 2. If the INVITE message expires (connector 4), it sets an event 'Timer expired', sends CAMEL_IMCN_MT_CANCEL, a 487 Request Terminated message, and goes to connector 2. Both connectors 1 and 2 lead to Release Call Resources, which then leads to Idle.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +**Process MT\_IM\_SSF** 2(6) + +Process in IM-SSF to perform Mobile Terminating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the originating S-CSCF via S-CSCF, unless otherwise stated. \*/ + +``` +graph TD; 3((3)) --> Check[Check Registration]; Check --> Result1{Result ?}; Result1 -- Fail --> 1((1)); Result1 -- Pass --> Init[CAMEL_IMCN
MT_VT_IM
CSI_INIT]; Init --> Result2{Result ?}; Result2 -- Fail --> 1; Result2 -- Pass --> INVITE{{INVITE}}; INVITE --> StartTb[Start Tb]; StartTb --> Wait[Wait_For
MT_Answer]; Wait --> Result3{Result ?}; Result3 -- Fail --> 1; Result3 -- Pass --> Establish[Establish
Through
Connection]; Establish --> Idle([Idle]); Result2 -- Fail --> 1; Result2 -- Pass --> Reconnect[CAMEL_IMCN
MT_RECONNECT]; Reconnect --> Result4{Result ?}; Result4 -- Fail --> 1; Result4 -- Pass --> Establish; 4((4)) --> Expire[INVITE Expires]; Expire --> Event[Event :=
"Timer
expired"]; Event --> Cancel[CAMEL_IMCN
MT_CANCEL]; Cancel --> Terminated[487 Request
Terminated]; Terminated --> 2((2)); 1 --> Release[Release
Call
Resources]; 2 --> Release; Release --> Idle; +``` + +Flowchart for Process MT\_IM\_SSF (sheet 2). The process starts at connector 3, proceeds to Check Registration, then a Result? decision. If Fail, it goes to connector 1. If Pass, it sends CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT, then another Result? decision. If Fail, it goes to connector 1. If Pass, it sends an INVITE message, starts timer Tb, and waits for an MT Answer. If the INVITE result is Pass, it establishes the connection and goes Idle. If the INVITE result is Fail, it sends CAMEL\_IMCN\_MT\_RECONNECT, then a Result? decision. If Fail, it goes to connector 1. If Pass, it establishes the connection and goes Idle. If the second Result? decision fails, it sends a 606 Not Acceptable message and goes to connector 2. If the INVITE message expires (connector 4), it sets an event 'Timer expired', sends CAMEL\_IMCN\_MT\_CANCEL, a 487 Request Terminated message, and goes to connector 2. Both connectors 1 and 2 lead to Release Call Resources, which then leads to Idle. + +Figure 4.22-2: Process MT\_IM\_SSF (sheet 2) + +![Flowchart for Process MT_IM_SSF. It starts with 'Wait_For_MT_Answer' and branches based on responses: 100 Trying, 1xx (except 100), and 200 OK. The 100 Trying path leads to 'Cancel Received?' which branches to 'Provisional_Response_Received := True' (False) or 'CANCEL' (True). The 1xx path leads to '1xx' response with 'Same Response Code'. The 200 OK path leads to 'Final_Response_Received := True', 'Stop Tb', and 'CAMEL_IMCN_MT_ANSWER'. The 'Result?' decision follows, leading to 'Pass' (200 OK, Stop Tininvite, Start Tack, Wait_For_ACK), 'Reconnect' (1), or 'Fail' (606 Not Acceptable, 2).](5801c19431e76330430e92a598cc7a16_img.jpg) + +### Process MT\_IM\_SSF 3(6) + +Process in IM-SSF to perform Mobile Terminating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the originating S-CSCF via S-CSCF, unless otherwise stated. \*/ + +``` +graph TD; Start([Wait_For_MT_Answer]) --> 100[100 Trying]; Start --> 1xx[1xx except 100]; Start --> 200[200 OK]; 1xx --> 1xx_resp[1xx]; 1xx_resp --> SameCode[Same Response Code]; SameCode --> 100; 200 --> Final[Final_Response_Received := True]; Final --> StopTb[Stop Tb]; StopTb --> CAMEL_ANSWER[CAMEL_IMCN_MT_ANSWER]; CAMEL_ANSWER --> Result{Result?}; Result -- Pass --> OK[200 OK]; OK --> StopTin[Stop Tininvite]; StopTin --> StartTack[Start Tack]; StartTack --> ACK([Wait_For_ACK]); Result -- Reconnect --> 1((1)); Result -- Fail --> NotAcceptable[606 Not Acceptable]; NotAcceptable --> 2((2)); 100 --> Cancel{Cancel Received?}; Cancel -- True --> CANCEL[CANCEL]; CANCEL --> CAMEL_CANCEL[CAMEL_IMCN_MT_CANCEL]; CAMEL_CANCEL --> Terminated[487 Request Terminated]; Terminated --> OK2[200 OK]; OK2 --> 2((2)); Cancel -- False --> Provisional[Provisional_Response_Received := True]; Provisional --> WaitAnswer([Wait_For_MT_Answer]); +``` + +Flowchart for Process MT\_IM\_SSF. It starts with 'Wait\_For\_MT\_Answer' and branches based on responses: 100 Trying, 1xx (except 100), and 200 OK. The 100 Trying path leads to 'Cancel Received?' which branches to 'Provisional\_Response\_Received := True' (False) or 'CANCEL' (True). The 1xx path leads to '1xx' response with 'Same Response Code'. The 200 OK path leads to 'Final\_Response\_Received := True', 'Stop Tb', and 'CAMEL\_IMCN\_MT\_ANSWER'. The 'Result?' decision follows, leading to 'Pass' (200 OK, Stop Tininvite, Start Tack, Wait\_For\_ACK), 'Reconnect' (1), or 'Fail' (606 Not Acceptable, 2). + +Figure 4.22-3: Process MT\_IM\_SSF (sheet 3) + +![Flowchart for Process MT_IM_SSF. It starts with 'Wait_For_MT_Answer' and branches into four main paths: 1) CANCEL -> Provisional_Response_Received? (True leads to CAMEL_IMCN_MT_CANCEL, 487 Request Terminated, 200 OK; False leads to Cancel_Received := True, then back to Wait_For_MT_Answer); 2) 4xx, 5xx, 6xx -> ACK -> Event := (Response Code); 3) Tb expiry -> Provisional_Response_Recvd? (Yes leads to CANCEL, No leads to Event := 'Timer expired'); 4) Tinvite expiry -> Provisional_Response_Received? (Yes leads to CANCEL, No leads to connector 4). All three main paths converge to CAMEL_IMCN_MT_UNSUCCESSFUL -> Result = Reconnect? (Yes leads to connector 1, No leads to connector 2).](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +### Process MT\_IM\_SSF + +4(6) + +Process in IM-SSF to perform Mobile Terminating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the originating S-CSCF via S-CSCF, unless otherwise stated. \*/ + +``` +graph TD; Start([Wait_For_MT_Answer]) --> CANCEL{CANCEL}; Start --> 4xx[4xx, 5xx, 6xx]; Start --> Tb[Tb expiry]; Start --> Tinvite[Tinvite expiry]; CANCEL --> PR{Provisional_Response_Received?}; PR -- True --> CAMEL_IMCN_MT_CANCEL[CAMEL_IMCN_MT_CANCEL]; PR -- False --> Cancel_Received[Cancel_Received := True]; Cancel_Received --> Start; 4xx --> ACK{ACK}; ACK --> Event1[Event := (Response Code)]; Event1 --> CAMEL_IMCN_MT_UNSUCCESSFUL[CAMEL_IMCN_MT_UNSUCCESSFUL]; Tb --> PR2{Provisional_Response_Recvd?}; PR2 -- Yes --> CANCEL2{CANCEL}; PR2 -- No --> Event2[Event := "Timer expired"]; Event2 --> CAMEL_IMCN_MT_UNSUCCESSFUL; Tinvite --> PR3{Provisional_Response_Received?}; PR3 -- Yes --> CANCEL3{CANCEL}; PR3 -- No --> Connector4((4)); CANCEL3 --> Connector4; CAMEL_IMCN_MT_CANCEL --> 487[487 Request Terminated]; 487 --> 200[200 OK]; 200 --> CAMEL_IMCN_MT_UNSUCCESSFUL; CAMEL_IMCN_MT_UNSUCCESSFUL --> Reconnect{Result = Reconnect?}; Reconnect -- Yes --> Connector1((1)); Reconnect -- No --> Connector2((2)); +``` + +Flowchart for Process MT\_IM\_SSF. It starts with 'Wait\_For\_MT\_Answer' and branches into four main paths: 1) CANCEL -> Provisional\_Response\_Received? (True leads to CAMEL\_IMCN\_MT\_CANCEL, 487 Request Terminated, 200 OK; False leads to Cancel\_Received := True, then back to Wait\_For\_MT\_Answer); 2) 4xx, 5xx, 6xx -> ACK -> Event := (Response Code); 3) Tb expiry -> Provisional\_Response\_Recvd? (Yes leads to CANCEL, No leads to Event := 'Timer expired'); 4) Tinvite expiry -> Provisional\_Response\_Received? (Yes leads to CANCEL, No leads to connector 4). All three main paths converge to CAMEL\_IMCN\_MT\_UNSUCCESSFUL -> Result = Reconnect? (Yes leads to connector 1, No leads to connector 2). + +Figure 4.22-4: Process MT\_IM\_SSF (sheet 4) + +![State transition diagram for Process MT_IM_SSF. It starts at 'Wait_For_ACK' and branches into four paths: 1) ACK -> Stop Tack -> Bye_Received? (True leads to ACK -> Wait_For_Clear; False leads to Ack_Received := True -> ACK -> Wait_For_Clear); 2) BYE -> Ack_Received? (True leads to CAMEL_IMCN MT_DISC2 -> Result = Reconnect? (Yes leads to 1, No leads to 2); False leads to Bye_Received := True -> Wait_For_ACK); 3) BYE -> CAMEL_IMCN MT_DISC1 -> 2; 4) Tack expiry (Internal) -> BYE -> Bye_Received? (True leads to ACK -> BYE -> CAMEL_IMCN MT_DISC1 -> 2; False leads to CAMEL_IMCN MT_DISC1 -> 2).](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +### Process MT\_IM\_SSF + +5(6) + +Process in IM-SSF to perform Mobile Terminating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the originating S-CSCF via S-CSCF, unless otherwise stated. \*/ + +``` +stateDiagram-v2 + [*] --> Wait_For_ACK + state "ACK" as ACK + state "BYE" as BYE + state "BYE" as BYE + state "Tack expiry" as Tack_expiry + state "Stop Tack" as Stop_Tack + state "Ack_Received?" as Ack_Received + state "CAMEL_IMCN MT_DISC1" as CAMEL_IMCN_MT_DISC1 + state "Bye_Received?" as Bye_Received + state "Ack_Received := True" as Ack_Received_T + state "CAMEL_IMCN MT_DISC2" as CAMEL_IMCN_MT_DISC2 + state "Result = Reconnect?" as Result_Reconnect + state "Bye_Received := True" as Bye_Received_T + state "ACK" as ACK + state "BYE" as BYE + state "Wait_For_Clear" as Wait_For_Clear + state "1" as 1 + state "2" as 2 + state "Wait_For_ACK" as Wait_For_ACK + + Wait_For_ACK --> ACK + Wait_For_ACK --> BYE + Wait_For_ACK --> BYE + Wait_For_ACK --> Tack_expiry + + ACK --> Stop_Tack + Stop_Tack --> Bye_Received + Bye_Received -- True --> ACK + Bye_Received -- False --> Ack_Received_T + Ack_Received_T --> ACK + ACK --> Wait_For_Clear + + BYE --> Ack_Received + Ack_Received -- True --> CAMEL_IMCN_MT_DISC2 + Ack_Received -- False --> Bye_Received_T + Bye_Received_T --> Wait_For_ACK + CAMEL_IMCN_MT_DISC2 --> Result_Reconnect + Result_Reconnect -- Yes --> 1 + Result_Reconnect -- No --> 2 + + BYE --> CAMEL_IMCN_MT_DISC1 + CAMEL_IMCN_MT_DISC1 --> 2 + + Tack_expiry --> BYE + BYE --> Bye_Received + Bye_Received -- True --> ACK + ACK --> BYE + BYE --> CAMEL_IMCN_MT_DISC1 + CAMEL_IMCN_MT_DISC1 --> 2 + Bye_Received -- False --> CAMEL_IMCN_MT_DISC1 + CAMEL_IMCN_MT_DISC1 --> 2 +``` + +State transition diagram for Process MT\_IM\_SSF. It starts at 'Wait\_For\_ACK' and branches into four paths: 1) ACK -> Stop Tack -> Bye\_Received? (True leads to ACK -> Wait\_For\_Clear; False leads to Ack\_Received := True -> ACK -> Wait\_For\_Clear); 2) BYE -> Ack\_Received? (True leads to CAMEL\_IMCN MT\_DISC2 -> Result = Reconnect? (Yes leads to 1, No leads to 2); False leads to Bye\_Received := True -> Wait\_For\_ACK); 3) BYE -> CAMEL\_IMCN MT\_DISC1 -> 2; 4) Tack expiry (Internal) -> BYE -> Bye\_Received? (True leads to ACK -> BYE -> CAMEL\_IMCN MT\_DISC1 -> 2; False leads to CAMEL\_IMCN MT\_DISC1 -> 2). + +Figure 4.22-5: Process MT\_IM\_SSF (sheet 5) + +![State transition diagram for Process MT_IM_SSF. It starts at 'Wait_For_Clear' and branches into three paths: 1) BYE -> CAMEL_IMCN MT_DISC2 -> Result = Reconnect? (Yes leads to 1, No leads to 2); 2) BYE -> CAMEL_IMCN MT_DISC1 -> 2; 3) Int_Release Call (From imcnSSF) -> BYE -> BYE -> 2.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +### Process MT\_IM\_SSF 6(6) + +Process in IM-SSF to perform Mobile Terminating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the originating S-CSCF via S-CSCF, unless otherwise stated. \*/ + +``` +stateDiagram-v2 + [*] --> Wait_For_Clear + state "Wait_For_Clear" as Wait_For_Clear + state "BYE" as BYE1[BYE] + state "BYE" as BYE2[BYE] + state "Int_Release Call" as Int_Release_Call[Int_Release Call] + state "CAMEL_IMCN MT_DISC2" as CAMEL_IMCN_MT_DISC2[CAMEL_IMCN MT_DISC2] + state "CAMEL_IMCN MT_DISC1" as CAMEL_IMCN_MT_DISC1[CAMEL_IMCN MT_DISC1] + state "Result = Reconnect?" as Result_Reconnect{Result = Reconnect?} + state "1" as 1((1)) + state "2" as 2((2)) + state "BYE" as BYE3[BYE] + state "BYE" as BYE4[BYE] + state "From imcnSSF" as From_imcnSSF[From imcnSSF] + + Wait_For_Clear --> BYE1 + Wait_For_Clear --> BYE2 + Wait_For_Clear --> Int_Release_Call + Int_Release_Call --> From_imcnSSF + Int_Release_Call --> BYE3 + BYE3 --> BYE4 + BYE4 --> 2 + BYE1 --> CAMEL_IMCN_MT_DISC2 + CAMEL_IMCN_MT_DISC2 --> Result_Reconnect + Result_Reconnect -- Yes --> 1 + Result_Reconnect -- No --> 2 + BYE2 --> CAMEL_IMCN_MT_DISC1 + CAMEL_IMCN_MT_DISC1 --> 2 +``` + +State transition diagram for Process MT\_IM\_SSF. It starts at 'Wait\_For\_Clear' and branches into three paths: 1) BYE -> CAMEL\_IMCN MT\_DISC2 -> Result = Reconnect? (Yes leads to 1, No leads to 2); 2) BYE -> CAMEL\_IMCN MT\_DISC1 -> 2; 3) Int\_Release Call (From imcnSSF) -> BYE -> BYE -> 2. + +Figure 4.22-6: Process MT\_IM\_SSF (sheet 6) + +### Procedure Check\_Registration + +1(1) + +Procedure in IM-SSF to check and obtain CSI for a terminating unregistered subscriber + +/\* Signals to/from the right are to/from the HSS. \*/ + +![Flowchart for Procedure Check_Registration. It starts with a connector, followed by a decision 'VT-IM-CSI present?'. If 'Yes', it goes to 'Result := Pass'. If 'No', it goes to 'ATSI_query' (which sends 'Requested CSI: VT-IM-CSI'), then 'Wait for response', then either 'ATSI_Ack' (leading to 'Store Subscriber info' and then 'Result := Pass') or 'ATSI Negative Response' (leading to 'Result := Fail'). Both 'Result := Pass' and 'Result := Fail' lead to an exit connector.](b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg) + +``` +graph TD; Start([ ]) --> Decision{VT-IM-CSI present?}; Decision -- Yes --> ResultPass[Result := Pass]; Decision -- No --> ATSI_query[/ATSI_query/]; ATSI_query --> ATSI_query_note[Requested CSI: VT-IM-CSI]; ATSI_query --> Wait[Wait for response]; Wait --> ATSI_Ack[/ATSI_Ack/]; Wait --> ATSI_Neg[ATSI Negative Response]; ATSI_Ack --> Store[Store Subscriber info]; Store --> ResultPass; ATSI_Neg --> ResultFail[Result := Fail]; ResultPass --> End((X)); ResultFail --> End; +``` + +Flowchart for Procedure Check\_Registration. It starts with a connector, followed by a decision 'VT-IM-CSI present?'. If 'Yes', it goes to 'Result := Pass'. If 'No', it goes to 'ATSI\_query' (which sends 'Requested CSI: VT-IM-CSI'), then 'Wait for response', then either 'ATSI\_Ack' (leading to 'Store Subscriber info' and then 'Result := Pass') or 'ATSI Negative Response' (leading to 'Result := Fail'). Both 'Result := Pass' and 'Result := Fail' lead to an exit connector. + +Figure 4.23: Procedure Check\_Registration (sheet 1) + +# Procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT + +1(3) + +/\* Procedure in the IM-SSF to perform CAMEL handling for a terminating call INVITE request \*/ + +/\* Signals to/from the left are to/from the originating S-CSCF via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MT_VT_IM_CSI_INIT. The process starts with a decision 'VT-IM-CSI invocation?'. If 'No', it goes to 'Result:= Pass' and ends. If 'Yes', it sets 'CAMEL_Invocation := True', stores original call parameters, and invokes 'Int_Invoke_imcnSSF (VT-IM-CSI)'. It then waits for 'imcnSSF_Invoked'. From there, it branches: one path goes to 'Int_imcnSSF_Invoked' -> 'Int_DP_Termination_Attempt_Autorised' -> 'DP_Termination_Attempt_Autorised' -> end; the other path goes to 'CANCEL' -> 'CAMEL_IMCN MT_CANCEL' -> 'Result := Abort' -> end.](f06d7a2fad72d80fe12fca1b65fc805b_img.jpg) + +``` +graph TD; Start([Start]) --> Decision{VT-IM-CSI invocation?}; Decision -- No --> ResultPass[Result:= Pass]; ResultPass --> EndPass(( )); Decision -- Yes --> CAMELTrue[CAMEL_Invocation := True]; CAMELTrue --> StoreParams[Store original call parameters]; StoreParams --> InvokeImcnSSF[Int_Invoke_imcnSSF (VT-IM-CSI)]; InvokeImcnSSF --> WaitImcnSSF[wait_for_imcnSSF_Invoked]; WaitImcnSSF --> ImcnSSFInvoked[Int_imcnSSF_Invoked]; ImcnSSFInvoked --> DPAttemptAutorised[Int_DP_Termination_Attempt_Autorised]; DPAttemptAutorised --> DPAutorised[DP_Termination_Attempt_Autorised]; DPAutorised --> EndPass; WaitImcnSSF --> CANCEL{CANCEL}; CANCEL --> MT_CANCEL[CAMEL_IMCN MT_CANCEL]; MT_CANCEL --> ResultAbort[Result := Abort]; ResultAbort --> EndAbort(( )); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT. The process starts with a decision 'VT-IM-CSI invocation?'. If 'No', it goes to 'Result:= Pass' and ends. If 'Yes', it sets 'CAMEL\_Invocation := True', stores original call parameters, and invokes 'Int\_Invoke\_imcnSSF (VT-IM-CSI)'. It then waits for 'imcnSSF\_Invoked'. From there, it branches: one path goes to 'Int\_imcnSSF\_Invoked' -> 'Int\_DP\_Termination\_Attempt\_Autorised' -> 'DP\_Termination\_Attempt\_Autorised' -> end; the other path goes to 'CANCEL' -> 'CAMEL\_IMCN MT\_CANCEL' -> 'Result := Abort' -> end. + +Figure 4.24-1: Procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT (sheet 1) + +## Procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT + +2(3) + +/\* Procedure in the IM-SSF to perform CAMEL handling for a terminating call INVITE request \*/ + +/\* Signals to/from the left are to/from the originating S-CSCF via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MT_VT_IM_CSI_INIT](1399c76ef88f22b70d05ed3f781d3c48_img.jpg) + +``` +graph TD; Start([DP_Termination_Attempt_Authorised]) --> Int_Connect[/Int_Connect/]; Start --> Int_Continue_With_Argument[/Int_Continue_With_Argument/]; Start --> Int_Continue[/Int_Continue/]; Start --> Int_Error[/Int_Error/]; Start --> Int_Release_Call[/Int_Release_Call/]; Int_Connect --> 181[181 Call Is Being Forwarded]; 181 --> Modify1[Modify call parameters with received information]; Int_Continue_With_Argument --> Modify2[Modify call parameters with received information]; Int_Continue --> Decision{Default Call Handling = Continue Call?}; Modify1 --> Decision; Modify2 --> Decision; Decision -- Yes --> INVITE[/INVITE/]; INVITE --> ToTerminatingMS[To the terminating MS]; ToTerminatingMS --> ResultPass[Result := Pass]; ResultPass --> EndPass(( )); Decision -- No --> ResultFail[Result := Fail]; ResultFail --> EndFail(( )); +``` + +The flowchart illustrates the procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT. It begins with a decision node 'DP\_Termination\_Attempt\_Authorised'. From this node, five paths emerge: 'Int\_Connect', 'Int\_Continue\_With\_Argument', 'Int\_Continue', 'Int\_Error', and 'Int\_Release\_Call'. The 'Int\_Connect' path leads to '181 Call Is Being Forwarded', which then leads to 'Modify call parameters with received information'. The 'Int\_Continue\_With\_Argument' path also leads to 'Modify call parameters with received information'. Both of these paths then lead to a decision node 'Default Call Handling = Continue Call?'. The 'Int\_Continue' path leads directly to this decision node. If the answer is 'Yes', the flow proceeds to 'INVITE', which is then sent 'To the terminating MS', resulting in 'Result := Pass'. If the answer is 'No', the flow proceeds to 'Result := Fail'. Both 'Result := Pass' and 'Result := Fail' lead to end nodes. + +Flowchart for Procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT + +Figure 4.24-2: Procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT (sheet 2) + +### Procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT + +3(3) + +/\* Procedure in the IM-SSF to perform CAMEL handling for a terminating call INVITE request \*/ + +/\* Signals to/from the left are to/from the originating S-CSCF via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MT_VT_IM_CSI_INIT. It starts with DP_Termination_Attempt_Authorised, branching into Tinvite expiry, CANCEL, and Int_Connect_To_Resource paths. The CANCEL path leads to CAMEL_IMCN_MT_CANCEL and then to a decision diamond 'Result= Fail?'. The Int_Connect_To_Resource path leads to CAMEL_MT_CTR and then to the same decision diamond. The Tinvite expiry path leads to Result := INVITE Expires. The decision diamond has 'No' and 'Yes' branches. The 'No' branch leads to DP_Termination_Attempt_Authorised and the 'Yes' branch leads to Result := Fail. All three main paths end at connector circles.](708e4c9a044ef61f586126676eb2eeb8_img.jpg) + +``` +graph TD; Start([DP_Termination_Attempt_Authorised]) --> Tinvite[Tinvite expiry]; Start --> CANCEL[CANCEL]; Start --> IntConnect[Int_Connect_To_Resource]; Tinvite --> R1[Result := INVITE Expires]; R1 --> End1(( )); CANCEL --> CAMELMT[CAMEL_IMCN_MT_CANCEL]; CAMELMT --> R2[Result := Abort]; R2 --> End2(( )); IntConnect --> CAMELCTR[CAMEL_MT_CTR]; CAMELCTR --> Decision{Result= Fail?}; Decision -- No --> End3([DP_Termination_Attempt_Authorised]); Decision -- Yes --> R3[Result := Fail]; R3 --> End4(( )); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT. It starts with DP\_Termination\_Attempt\_Authorised, branching into Tinvite expiry, CANCEL, and Int\_Connect\_To\_Resource paths. The CANCEL path leads to CAMEL\_IMCN\_MT\_CANCEL and then to a decision diamond 'Result= Fail?'. The Int\_Connect\_To\_Resource path leads to CAMEL\_MT\_CTR and then to the same decision diamond. The Tinvite expiry path leads to Result := INVITE Expires. The decision diamond has 'No' and 'Yes' branches. The 'No' branch leads to DP\_Termination\_Attempt\_Authorised and the 'Yes' branch leads to Result := Fail. All three main paths end at connector circles. + +Figure 4.24-3: Procedure CAMEL\_IMCN\_MT\_VT\_IM\_CSI\_INIT (sheet 3) + +# Procedure CAMEL\_IMCN\_MT\_RECONNECT + +1(1) + +Procedure in IM-SSF to handle MT call to redirect the call. + +/\* Signals to/from the right are to/from the process MO\_IM\_SSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MT_RECONNECT. It starts with an INVITE message, followed by a Wait_For_Response state. From there, it branches based on responses: 1xx Provisional Response (loops back to Wait_For_Response), 200 OK (Result := Pass), any other response codes (loops back to Wait_For_Response), and Timer expiry (Result := Fail, then Internal).](0f7871077bba48a2c97f7859a5edda0d_img.jpg) + +``` +graph TD; Start([ ]) --> INVITE[INVITE]; INVITE --> WFR1[Wait_For_Response]; WFR1 --> Branch1(( )); Branch1 --> P[1xx Provisional Response]; P --> WFR2[Wait_For_Response]; WFR2 --> Branch1; Branch1 --> OK[200 OK]; OK --> Pass[Result := Pass]; Pass --> End1(( )); Branch1 --> Other[ ]; Other --> WFR1; Branch1 --> Timer[Timer expiry]; Timer --> Fail[Result := Fail]; Fail --> End2(( )); Fail --> Internal[Internal]; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_RECONNECT. It starts with an INVITE message, followed by a Wait\_For\_Response state. From there, it branches based on responses: 1xx Provisional Response (loops back to Wait\_For\_Response), 200 OK (Result := Pass), any other response codes (loops back to Wait\_For\_Response), and Timer expiry (Result := Fail, then Internal). + +Figure 4.25: Procedure CAMEL\_IMCN\_MT\_RECONNECT (sheet 1) + +# Procedure CAMEL\_IMCN\_MT\_CANCEL + +1(1) + +/\* Procedure in IM-SSF to perform CAMEL handling for an incoming call CANCEL request. \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MT_CANCEL. It starts with an oval connector, followed by a decision diamond 'imcnSSF Invoked?'. If 'No', it goes to a circular connector. If 'Yes', it goes through 'Int_DP_T_Abandon', 'DP_T_Abandon', and 'Int_Continue' to the same circular connector.](b8efedb73292a798b3f2050f9335cae6_img.jpg) + +``` +graph TD; Start([ ]) --> Decision{imcnSSF Invoked?}; Decision -- No --> End(( )); Decision -- Yes --> Int_DP_T_Abandon[Int_DP_T_Abandon]; Int_DP_T_Abandon --> DP_T_Abandon[DP_T_Abandon]; DP_T_Abandon --> Int_Continue[Int_Continue]; Int_Continue --> End; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_CANCEL. It starts with an oval connector, followed by a decision diamond 'imcnSSF Invoked?'. If 'No', it goes to a circular connector. If 'Yes', it goes through 'Int\_DP\_T\_Abandon', 'DP\_T\_Abandon', and 'Int\_Continue' to the same circular connector. + +Figure 4.26: Procedure CAMEL\_IMCN\_MT\_CANCEL (sheet 1) + +# Procedure CAMEL\_IMCN\_MT\_ANSWER + +1(2) + +/\* Procedure in the IM-SSF to perform CAMEL handling for a terminating call upon 200 OK message \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MT_ANSWER. It starts with a connector, leading to a decision 'imcnSSF invoked?'. If 'No', it goes to 'Result:= Pass' and ends. If 'Yes', it sends 'Int_DP_T_Answer' and receives 'DP_T_Answer'. Then it branches into 'Int_Continue', 'Int_Release', and 'Int_Error'. 'Int_Continue' leads to 'Result:= Pass'. 'Int_Release' leads to 'Result := Fail'. 'Int_Error' leads to a decision 'Default call handling = continue call ?'. If 'No', it leads to 'Result := Fail'. If 'Yes', it leads to 'Result:= Pass'. All three results ('Pass', 'Fail', 'Pass') converge to a final connector.](91c33f8e1713989e8192322ec2d1212b_img.jpg) + +``` +graph TD; Start([ ]) --> Decision1{imcnSSF invoked?}; Decision1 -- No --> Result1[Result:= Pass]; Result1 --> End1(( )); Decision1 -- Yes --> Signal1[Int_DP_T_Answer]; Signal1 --> Signal2[DP_T_Answer]; Signal2 --> Int_Continue[Int_Continue]; Signal2 --> Int_Release[Int_Release]; Signal2 --> Int_Error[Int_Error]; Int_Continue --> Result2[Result:= Pass]; Int_Release --> Result3[Result := Fail]; Int_Error --> Decision2{Default call handling = continue call ?}; Decision2 -- No --> Result4[Result := Fail]; Decision2 -- Yes --> Result5[Result:= Pass]; Result2 --> End2(( )); Result3 --> End2; Result5 --> End2; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_ANSWER. It starts with a connector, leading to a decision 'imcnSSF invoked?'. If 'No', it goes to 'Result:= Pass' and ends. If 'Yes', it sends 'Int\_DP\_T\_Answer' and receives 'DP\_T\_Answer'. Then it branches into 'Int\_Continue', 'Int\_Release', and 'Int\_Error'. 'Int\_Continue' leads to 'Result:= Pass'. 'Int\_Release' leads to 'Result := Fail'. 'Int\_Error' leads to a decision 'Default call handling = continue call ?'. If 'No', it leads to 'Result := Fail'. If 'Yes', it leads to 'Result:= Pass'. All three results ('Pass', 'Fail', 'Pass') converge to a final connector. + +Figure 4.27-1: Procedure CAMEL\_IMCN\_MT\_ANSWER (sheet 1) + +### Procedure CAMEL\_IMCN\_MT\_ANSWER + +2(2) + +/\* Procedure in the IM-SSF to perform CAMEL handling for a terminating call upon 200 OK message \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MT_ANSWER. It starts with DP_T_Answer, branches into two BYE message paths (one to the left, one from the originating S-CSCF), followed by CAMEL_IMCN MT_DISC2 and MT_DISC1 processing. A decision diamond 'Result = Reconnect?' follows. If 'Yes', Result := Reconnect. If 'No', Result := Fail. Both paths converge to a merge circle.](ee0bf6a260cff72af8f0df0639b6a7c5_img.jpg) + +``` +graph TD; DP_T_Answer([DP_T_Answer]) --> BYE_L[/BYE/]; DP_T_Answer --> BYE_R[/BYE/]; BYE_R -.-> Note1[From the originating S-CSCF]; BYE_L --> MT_DISC2[CAMEL_IMCN MT_DISC2]; BYE_R --> MT_DISC1[CAMEL_IMCN MT_DISC1]; MT_DISC2 --> Decision{Result = Reconnect?}; MT_DISC1 --> Decision; Decision -- Yes --> Result_Reconnect[Result := Reconnect]; Decision -- No --> Result_Fail[Result := Fail]; Result_Reconnect --> Merge(( )); Result_Fail --> Merge +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_ANSWER. It starts with DP\_T\_Answer, branches into two BYE message paths (one to the left, one from the originating S-CSCF), followed by CAMEL\_IMCN MT\_DISC2 and MT\_DISC1 processing. A decision diamond 'Result = Reconnect?' follows. If 'Yes', Result := Reconnect. If 'No', Result := Fail. Both paths converge to a merge circle. + +Figure 4.27-2: Procedure CAMEL\_IMCN\_MT\_ANSWER (sheet 2) + +![Flowchart for Procedure CAMEL_IMCN_MT_UNSUCCESSFUL. It starts with a connector symbol leading to a decision diamond 'Event?'. From the diamond, three paths lead to numbered circles 1, 2, and 3. Path 1 is labeled with SIP error codes: 4xx except 401, 407, 408, 413, 420, 480; or 5xx; or 6xx except 603. Path 2 is labeled with SIP error codes: 408, 480, 603. Path 3 is labeled 'Timer expiry'.](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +### Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL 1(5) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Terminating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; Start([ ]) --> Event{Event?}; Event -- "4xx except 401, 407, 408, 413, 420, 480; or 5xx; or 6xx except 603." --> 1((1)); Event -- "408, 480, 603" --> 2((2)); Event -- "Timer expiry" --> 3((3)); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL. It starts with a connector symbol leading to a decision diamond 'Event?'. From the diamond, three paths lead to numbered circles 1, 2, and 3. Path 1 is labeled with SIP error codes: 4xx except 401, 407, 408, 413, 420, 480; or 5xx; or 6xx except 603. Path 2 is labeled with SIP error codes: 408, 480, 603. Path 3 is labeled 'Timer expiry'. + +Figure 4.28-1: Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL (sheet 1) + +# Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL + +2(5) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Terminating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MT_UNSUCCESSFUL. It starts at connector 1, checks if imcnSSF is invoked. If No, it goes to Int_Release_Call. If Yes, it sends Int_DP_T_Busy, then DP_T_Busy. It then branches into Int_Connect, Int_Continue, Int_Error, and Int_Release_Call. Int_Connect leads to Modify call parameters and Result := Reconnect. Int_Continue leads to Same SIP 4XX, 5XX, or 6XX response received. Int_Error leads to a merge point, then Wait_For_ACK_For_Error, then ACK from originating S-CSCF, then Result := Continue. Int_Release_Call leads to To originating S-CSCF. All paths lead to a final connector.](bd50d56ae2c12a92466ba2aea1a78040_img.jpg) + +``` +graph TD; 1((1)) --> imcnSSF{imcnSSF invoked?}; imcnSSF -- No --> Int_Release_Call[/Int_Release_Call/]; imcnSSF -- Yes --> Int_DP_T_Busy[/Int_DP_T_Busy/]; Int_DP_T_Busy --> DP_T_Busy([DP_T_Busy]); DP_T_Busy --> Int_Connect[/Int_Connect/]; DP_T_Busy --> Int_Continue[/Int_Continue/]; DP_T_Busy --> Int_Error[/Int_Error/]; DP_T_Busy --> Int_Release_Call; Int_Connect --> Modify[Modify call parameters with received information]; Modify --> Result_Reconnect[Result := Reconnect]; Int_Continue --> SameSIP[Same SIP 4XX, 5XX, or 6XX response received]; Int_Error --> Merge{ }; SameSIP --> Merge; Merge --> Wait[Wait_For_ACK_For_Error]; Wait --> ACK[/ACK/]; ACK -- From originating S-CSCF --> ACK; ACK --> Result_Continue[Result := Continue]; Int_Release_Call --> ToS-CSCF[To originating S-CSCF]; Result_Reconnect --> End(( )); Result_Continue --> End; ToS-CSCF --> End; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL. It starts at connector 1, checks if imcnSSF is invoked. If No, it goes to Int\_Release\_Call. If Yes, it sends Int\_DP\_T\_Busy, then DP\_T\_Busy. It then branches into Int\_Connect, Int\_Continue, Int\_Error, and Int\_Release\_Call. Int\_Connect leads to Modify call parameters and Result := Reconnect. Int\_Continue leads to Same SIP 4XX, 5XX, or 6XX response received. Int\_Error leads to a merge point, then Wait\_For\_ACK\_For\_Error, then ACK from originating S-CSCF, then Result := Continue. Int\_Release\_Call leads to To originating S-CSCF. All paths lead to a final connector. + +Figure 4.28-2: Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL (sheet 2) + +![Flowchart for Procedure CAMEL_IMCN_MT_UNSUCCESSFUL. It starts at connector 2, checks if imcnSSF is invoked. If No, it goes to 'To originating S-CSCF'. If Yes, it sends 'Int_DP_T_No_Answer', receives 'DP_T_No_Answer', then branches into Int_Connect, Int_Continue, Int_Error, or Int_Release_Call. Int_Connect leads to 'Modify call parameters with received information' and 'Result := Reconnect'. Int_Continue leads to 'Int_T_Exception'. Int_Error and Int_Release_Call lead to a merge point. From the merge point, it checks 'Same SIP 4XX response received'. If Yes, it goes to 'To originating S-CSCF'. If No, it goes to 'Wait_For_ACK_For_Error', receives 'ACK' from originating S-CSCF, sets 'Result := Continue', and ends at the connector.](2f587210e4f97c32758c5972e2e83d20_img.jpg) + +### Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL 3(5) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Terminating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; Start((2)) --> Decision{imcnSSF invoked?}; Decision -- No --> ToOrig[To originating S-CSCF]; Decision -- Yes --> Out1{{Int_DP_T_No_Answer}}; Out1 --> In1([DP_T_No_Answer]); In1 --> Branch[ ]; Branch --> Int_Connect{{Int_Connect}}; Branch --> Int_Continue{{Int_Continue}}; Branch --> Int_Error{{Int_Error}}; Branch --> Int_Release_Call{{Int_Release_Call}}; Int_Connect --> Modify[Modify call parameters with received information]; Modify --> Result_Reconnect[Result := Reconnect]; Int_Continue --> Int_T_Exception{{Int_T_Exception}}; Int_Error --> Merge(( )); Int_Release_Call --> Merge; Merge --> SameSIP{Same SIP 4XX response received}; SameSIP -- Yes --> ToOrig; SameSIP -- No --> Wait[Wait_For_ACK_For_Error]; Wait --> ACK{{ACK}}; ACK -- FromOrig[From originating S-CSCF]; ACK --> Result_Continue[Result := Continue]; Result_Reconnect --> End(( )); Result_Continue --> End; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL. It starts at connector 2, checks if imcnSSF is invoked. If No, it goes to 'To originating S-CSCF'. If Yes, it sends 'Int\_DP\_T\_No\_Answer', receives 'DP\_T\_No\_Answer', then branches into Int\_Connect, Int\_Continue, Int\_Error, or Int\_Release\_Call. Int\_Connect leads to 'Modify call parameters with received information' and 'Result := Reconnect'. Int\_Continue leads to 'Int\_T\_Exception'. Int\_Error and Int\_Release\_Call lead to a merge point. From the merge point, it checks 'Same SIP 4XX response received'. If Yes, it goes to 'To originating S-CSCF'. If No, it goes to 'Wait\_For\_ACK\_For\_Error', receives 'ACK' from originating S-CSCF, sets 'Result := Continue', and ends at the connector. + +Figure 4.28-3: Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL (sheet 3) + +![Flowchart for Procedure CAMEL_IMCN_MT_UNSUCCESSFUL. It starts at connector '3', checks if 'imcnSSF invoked?'. If 'No', it goes to the end connector. If 'Yes', it sends 'Int_DP_T_No_Answer' to 'DP_T_No_Answer'. From there, it branches into four options: 'Int_Connect' (leading to 'Modify call parameters with received information' then 'Result := Reconnect'), 'Int_Continue' (leading to 'Int_T_Exception'), 'Int_Error' (leading to '487 Request Terminated' then 'To originating S-CSCF'), and 'Int_Release_Call'. All four paths merge at a junction point. From the junction, the flow goes to 'Wait_For_ACK_For_Error', then 'ACK' (from originating S-CSCF), then 'Result := Continue', and finally to the end connector.](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +### Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL 4(5) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Terminating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; Start((3)) --> Decision{imcnSSF invoked?}; Decision -- No --> End((X)); Decision -- Yes --> Int_DP_T_No_Answer{{Int_DP_T_No_Answer}}; Int_DP_T_No_Answer --> DP_T_No_Answer([DP_T_No_Answer]); DP_T_No_Answer --> Int_Connect[/Int_Connect/]; DP_T_No_Answer --> Int_Continue[/Int_Continue/]; DP_T_No_Answer --> Int_Error[/Int_Error/]; DP_T_No_Answer --> Int_Release_Call[/Int_Release_Call/]; Int_Connect --> Modify[Modify call parameters with received information]; Modify --> Result_Reconnect[Result := Reconnect]; Int_Continue --> Int_T_Exception[/Int_T_Exception/]; Int_Error --> Request_Terminated[/487 Request Terminated/]; Request_Terminated --> To_S_CSCF[To originating S-CSCF]; Int_Release_Call --> Junction(( )); Int_T_Exception --> Junction; Result_Reconnect --> Junction; Junction --> Wait_For_ACK[Wait_For_ACK_For_Error]; Wait_For_ACK --> ACK[/ACK/]; ACK --> From_S_CSCF[From originating S-CSCF]; ACK --> Result_Continue[Result := Continue]; Result_Continue --> Junction; Junction --> End; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL. It starts at connector '3', checks if 'imcnSSF invoked?'. If 'No', it goes to the end connector. If 'Yes', it sends 'Int\_DP\_T\_No\_Answer' to 'DP\_T\_No\_Answer'. From there, it branches into four options: 'Int\_Connect' (leading to 'Modify call parameters with received information' then 'Result := Reconnect'), 'Int\_Continue' (leading to 'Int\_T\_Exception'), 'Int\_Error' (leading to '487 Request Terminated' then 'To originating S-CSCF'), and 'Int\_Release\_Call'. All four paths merge at a junction point. From the junction, the flow goes to 'Wait\_For\_ACK\_For\_Error', then 'ACK' (from originating S-CSCF), then 'Result := Continue', and finally to the end connector. + +Figure 4.28-4: Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL (sheet 4) + +# Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL + +5(5) + +Procedure in IM-SSF to handle unsuccessful events in Mobile Terminating Call in IMS. + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MT_UNSUCCESSFUL. It starts with an event (DP_T_Busy, DP_T_No_Answer), branches into CANCEL (from originating S-CSCF) and Int_Connect_To_Resource. CANCEL leads to CAMEL_IMCN_MT_CANCEL, which leads to a 'Result?' decision. If 'Fail', it sends a 487 Request Terminated to the originating S-CSCF, then a 200 OK, and sets Result := Fail. If 'Pass', it leads to a terminal state.](20809e79dee38f3d6e03e1ad565a9cf5_img.jpg) + +``` +graph TD; Start([DP_T_Busy +DP_T_No_Answer]) --> CANCEL{CANCEL}; Start --> Int_Connect_To_Resource{Int_Connect_To_Resource}; CANCEL --> From_Originating_S_CSCF[From the originating S-CSCF]; From_Originating_S_CSCF --> CAMEL_IMCN_MT_CANCEL[CAMEL_IMCN_MT_CANCEL]; Int_Connect_To_Resource --> CAMEL_MT_CTR[CAMEL_MT_CTR]; CAMEL_IMCN_MT_CANCEL --> Result{Result?}; CAMEL_MT_CTR --> Result; Result -- Fail --> 487[487 Request Terminated]; 487 --> To_Originating_S_CSCF[To the originating S-CSCF]; To_Originating_S_CSCF --> 200[200 OK]; 200 --> Result_Fail[Result := Fail]; Result_Fail --> End(( )); Result -- Pass --> EndState([ - ]); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL. It starts with an event (DP\_T\_Busy, DP\_T\_No\_Answer), branches into CANCEL (from originating S-CSCF) and Int\_Connect\_To\_Resource. CANCEL leads to CAMEL\_IMCN\_MT\_CANCEL, which leads to a 'Result?' decision. If 'Fail', it sends a 487 Request Terminated to the originating S-CSCF, then a 200 OK, and sets Result := Fail. If 'Pass', it leads to a terminal state. + +Figure 4.28-5: Procedure CAMEL\_IMCN\_MT\_UNSUCCESSFUL (sheet 5) + +![Flowchart for Procedure CAMEL_IMCN_MT_DISC1. It starts with a connector, checks if imcnSSF is invoked. If No, it goes to Result:= Continue. If Yes, it sends Int_DP_T_Disconnect (legId=1), then DP_T_Disconnect_1. From there, it branches into Int_Error, Int_Release_Call, Int_Continue, and BYE. The first three lead to a common BYE message, which leads to 200 OK and then Result:= Continue. The BYE branch leads to Int_DP_T_Disconnect (legId=2), then DP_T_Disconnect_2, then branches into Int_Continue, Int_Error, and Int_ReleaseCall, which lead to 200 OK and then To the originating S-CSCF.](4806f9f95fff13a30d6523bd6ffeac63_img.jpg) + +### Procedure CAMEL\_IMCN\_MT\_DISC1 1(1) + +/\* Procedure in the IM-SSF to handle an outgoing call on the BYE request from caller \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; Start([ ]) --> Decision{imcnSSF invoked?}; Decision -- No --> Result[Result:= Continue]; Decision -- Yes --> Int_DP_T_Disconnect_1[Int_DP_T_Disconnect
/* legId = 1 */]; Int_DP_T_Disconnect_1 --> DP_T_Disconnect_1((DP_T_Disconnect_1)); DP_T_Disconnect_1 --> Int_Error_1[Int_Error]; DP_T_Disconnect_1 --> Int_Release_Call_1[Int_Release_Call]; DP_T_Disconnect_1 --> Int_Continue_1[Int_Continue]; DP_T_Disconnect_1 --> BYE_1[BYE]; Int_Error_1 --> BYE_2[BYE]; Int_Release_Call_1 --> BYE_2; Int_Continue_1 --> BYE_2; BYE_1 --> Int_DP_T_Disconnect_2[Int_DP_T_Disconnect
/* legId = 2 */]; Int_DP_T_Disconnect_2 --> DP_T_Disconnect_2((DP_T_Disconnect_2)); DP_T_Disconnect_2 --> Int_Continue_2[Int_Continue]; DP_T_Disconnect_2 --> Int_Error_2[Int_Error]; DP_T_Disconnect_2 --> Int_ReleaseCall_2[Int_ReleaseCall]; Int_Continue_2 --> 200_OK_2[200 OK]; Int_Error_2 --> 200_OK_2; Int_ReleaseCall_2 --> 200_OK_2; 200_OK_2 --> To_S_CSCF[To the originating S-CSCF]; BYE_2 --> 200_OK_1[200 OK]; 200_OK_1 --> Result; +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_DISC1. It starts with a connector, checks if imcnSSF is invoked. If No, it goes to Result:= Continue. If Yes, it sends Int\_DP\_T\_Disconnect (legId=1), then DP\_T\_Disconnect\_1. From there, it branches into Int\_Error, Int\_Release\_Call, Int\_Continue, and BYE. The first three lead to a common BYE message, which leads to 200 OK and then Result:= Continue. The BYE branch leads to Int\_DP\_T\_Disconnect (legId=2), then DP\_T\_Disconnect\_2, then branches into Int\_Continue, Int\_Error, and Int\_ReleaseCall, which lead to 200 OK and then To the originating S-CSCF. + +Figure 4.29: Procedure CAMEL\_IMCN\_MT\_DISC1 (sheet 1) + +![Flowchart for Procedure CAMEL_IMCN_MT_DISC2. It starts with a connector, leading to a decision 'imcnSSF invoked?'. If 'No', it goes to 'Result := Continue' and ends. If 'Yes', it sends 'Int_DP_T_Disconnect' (legId=2) to the imcnSSF, then 'DP_T_Disconnect_2' to the S-CSCF. From the S-CSCF, it receives 'BYE', 'Int_Continue', 'Int_Release_Call', 'Int_error', or 'Int_Connect'. The 'BYE' path leads to 'Int_DP_T_Disconnect' (legId=1), 'DP_T_Disconnect_1', then a choice of 'Int_Error', 'Int_Continue', or 'Int_Release_Call', followed by '200 OK' to the S-CSCF. The 'Int_Continue' and 'Int_Release_Call' paths lead to a 'BYE' to the S-CSCF. The 'Int_Connect' path leads to 'Modify call parameters with received information', 'Final_Response_Received := False', and 'Result := Reconnect'. All paths converge to a '200 OK' connector.](c07e21a8d65991db04263322f859c94f_img.jpg) + +### Procedure CAMEL\_IMCN\_MT\_DISC2 + +1(2) + +/\* Procedure in the IM-SSF to handle an outgoing call on the BYE request from callee \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +``` +graph TD; Start(( )) --> Decision{imcnSSF invoked?}; Decision -- No --> ResultContinue1[Result := Continue]; ResultContinue1 --> End1(( )); Decision -- Yes --> IntDP_T_Disconnect2[Int_DP_T_Disconnect
[* legId = 2 */]; IntDP_T_Disconnect2 --> DP_T_Disconnect2[DP_T_Disconnect_2]; DP_T_Disconnect2 --> BYE1[BYE]; DP_T_Disconnect2 --> Int_Continue1[Int_Continue]; DP_T_Disconnect2 --> Int_Release_Call1[Int_Release_Call]; DP_T_Disconnect2 --> Int_error1[Int_error]; DP_T_Disconnect2 --> Int_Connect1[Int_Connect]; BYE1 --> IntDP_T_Disconnect1[Int_DP_T_Disconnect
[* legId = 1 */]; IntDP_T_Disconnect1 --> DP_T_Disconnect1[DP_T_Disconnect_1]; DP_T_Disconnect1 --> Int_Error1[Int_Error]; DP_T_Disconnect1 --> Int_Continue2[Int_Continue]; DP_T_Disconnect1 --> Int_Release_Call2[Int_Release_Call]; Int_Error1 --> OK1[200 OK]; Int_Continue2 --> OK1; Int_Release_Call2 --> OK1; OK1 --> ToS-CSCF1[To the originating S-CSCF]; Int_Continue1 --> BYE2[BYE]; Int_Release_Call1 --> BYE2; BYE2 --> ToS-CSCF2[To the originating S-CSCF]; Int_Connect1 --> Modify[Modify call parameters with received information]; Modify --> FinalResponse[Final_Response_Received := False]; FinalResponse --> ResultReconnect[Result := Reconnect]; ResultReconnect --> OK2[200 OK]; ResultContinue1 --> OK2; ToS-CSCF1 --> OK2; ToS-CSCF2 --> OK2; OK2 --> End2(( )); +``` + +Flowchart for Procedure CAMEL\_IMCN\_MT\_DISC2. It starts with a connector, leading to a decision 'imcnSSF invoked?'. If 'No', it goes to 'Result := Continue' and ends. If 'Yes', it sends 'Int\_DP\_T\_Disconnect' (legId=2) to the imcnSSF, then 'DP\_T\_Disconnect\_2' to the S-CSCF. From the S-CSCF, it receives 'BYE', 'Int\_Continue', 'Int\_Release\_Call', 'Int\_error', or 'Int\_Connect'. The 'BYE' path leads to 'Int\_DP\_T\_Disconnect' (legId=1), 'DP\_T\_Disconnect\_1', then a choice of 'Int\_Error', 'Int\_Continue', or 'Int\_Release\_Call', followed by '200 OK' to the S-CSCF. The 'Int\_Continue' and 'Int\_Release\_Call' paths lead to a 'BYE' to the S-CSCF. The 'Int\_Connect' path leads to 'Modify call parameters with received information', 'Final\_Response\_Received := False', and 'Result := Reconnect'. All paths converge to a '200 OK' connector. + +Figure 4.30-1: Procedure CAMEL\_IMCN\_MT\_DISC2 (sheet 1) + +## Procedure CAMEL\_IMCN\_MT\_DISC2 + +2(2) + +/\* Procedure in the IM-SSF to handle an outgoing call on the BYE request from callee \*/ + +/\* Signals to/from the left are to/from the MS via S-CSCF; signals to/from right are to/from the imcnSSF, unless otherwise stated. \*/ + +![Flowchart for Procedure CAMEL_IMCN_MT_DISC2](beefc2239bc009e7b97963ac4f166db1_img.jpg) + +``` +graph TD; A[DP_T_Disconnect_2] --> B[Int_Connect_To_Resource]; B --> C[CAMEL_MT_CTR]; C --> D{Result = Fail?}; D -- No --> E[DP_T_Disconnect_2]; D -- Yes --> F[Result := Continue]; F --> G((X)); +``` + +The flowchart illustrates the procedure CAMEL\_IMCN\_MT\_DISC2. It begins with a process block labeled 'DP\_T\_Disconnect\_2', which leads to a connector block labeled 'Int\_Connect\_To\_Resource'. This is followed by a process block labeled 'CAMEL\_MT\_CTR'. A decision diamond labeled 'Result = Fail?' follows. If the result is 'No', the flow returns to the 'DP\_T\_Disconnect\_2' process block. If the result is 'Yes', the flow proceeds to a process block labeled 'Result := Continue', which then leads to a connector symbol (a circle with an 'X'). + +Flowchart for Procedure CAMEL\_IMCN\_MT\_DISC2 + +Figure 4.30-2: Procedure CAMEL\_IMCN\_MT\_DISC2 (sheet 2) + +# Procedure CAMEL\_Start\_TNRy + +1(1) + +Procedure in IM-SSF to start the timer TNRy + +![Flowchart for Procedure CAMEL_Start_TNRy](2fc2e531b3b3c695cca497516ec79f20_img.jpg) + +``` +graph TD; Start([Start]) --> imcnSSF{imcnSSF invoked?}; imcnSSF -- No --> Join(( )); imcnSSF -- Yes --> DP6orDP14{DP6 or DP14 armed?}; DP6orDP14 -- No --> Join; DP6orDP14 -- Yes --> TNRyReceived{TNRy received?}; TNRyReceived -- Yes --> StartTNRyReceived[Start TNRy with received time value]; TNRyReceived -- No --> DefaultValue{TNRy default value available?}; DefaultValue -- No --> Join; DefaultValue -- Yes --> StartTNRyDefault[Start TNRy with default value]; StartTNRyReceived --> Join; StartTNRyDefault --> Join; +``` + +The flowchart illustrates the procedure for starting the TNRy timer. It begins with an oval start symbol. The first decision diamond asks 'imcnSSF invoked?'. If 'No', the flow proceeds directly to a circular join symbol. If 'Yes', it proceeds to the next decision diamond: 'DP6 or DP14 armed?'. If 'No', it also proceeds to the join symbol. If 'Yes', it proceeds to the decision diamond 'TNRy received?'. If 'Yes', it goes to a rectangular process box 'Start TNRy with received time value'. If 'No', it goes to the decision diamond 'TNRy default value available?'. If 'No', it goes to the join symbol. If 'Yes', it goes to a rectangular process box 'Start TNRy with default value'. Both process boxes lead to the join symbol. + +Flowchart for Procedure CAMEL\_Start\_TNRy + +Figure 4.31: Procedure CAMEL\_Start\_TNRy (sheet 1) + +![Flowchart for Procedure CAMEL_Stop_TNRy. It starts with a start symbol, followed by a decision 'imcnSSF invoked?'. If 'No', it goes to an exit symbol. If 'Yes', it goes to another decision 'TNRy running?'. If 'No', it goes to an exit symbol. If 'Yes', it goes to a process 'Stop TNRy', which then leads to an exit symbol.](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +### Procedure CAMEL\_Stop\_TNRy + +1(1) + +Procedure in the IM-SSF +to stop the timer TNRy + +``` +graph TD; Start([ ]) --> D1{imcnSSF invoked?}; D1 -- No --> Exit1(( )); D1 -- Yes --> D2{TNRy running?}; D2 -- No --> Exit2(( )); D2 -- Yes --> Process[Stop TNRy]; Process --> Exit3(( )); +``` + +Flowchart for Procedure CAMEL\_Stop\_TNRy. It starts with a start symbol, followed by a decision 'imcnSSF invoked?'. If 'No', it goes to an exit symbol. If 'Yes', it goes to another decision 'TNRy running?'. If 'No', it goes to an exit symbol. If 'Yes', it goes to a process 'Stop TNRy', which then leads to an exit symbol. + +Figure 4.32: Procedure CAMEL\_Stop\_TNRy (sheet 1) + +![Flowchart of Procedure CAMEL_MT_CTR (sheet 1) showing the logic for handling Connect To Resource operations, including branching for Play Announcement, Prompt and Collect, and Disconnect Forward Connection, followed by SIP signaling states like Wait for 200 OK and subsequent error or success handling.](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +## Procedure CAMEL\_MT\_CTR + +1(5) + + +Procedure in the IM-SSF to handle a Connect To Resource operation. + +Signals to/from the left are to/from the originating party. + Signals to/from the right are to/from the imcnSSF unless otherwise stated. + +``` + + graph TD + Start([ ]) --> Wait1[Wait_for_PlayAnno_or_Prompt_And_Collect_request] + + Wait1 --> CAP_Play[CAP_Play_Announcement] + Wait1 --> CAP_Prompt[CAP_Prompt_And_Collect_User_Information] + Wait1 --> Int_Disc[Int_Disconnect_Forward_Connection] + + CAP_Play --> INVITE1{INVITE} -- To MRFC --> Wait2[Wait_for_200_OK] + CAP_Prompt --> INVITE2{INVITE} -- To MRFC --> Wait2 + Int_Disc --> Result1[Result:= pass] --> End1((X)) + + Wait2 --> OK_In{200 OK} -- From MRFC --> OK_Out{200 OK} --> ACK{ACK} -- To MRFC --> Int_SRF_Conn[Int_SRF_Connected] --> Relay([Relay]) + + Wait2 --> Err_In{Error response} -- From MRFC --> Int_Fail[Int_CTR_Failed] --> Result2[Result:= pass] --> End2((X)) + + Wait2 --> BYE_In{BYE} --> OK_BYE{200 OK} --> Int_DP_Disc[Int_DP_T_Disconnect +/* legID */] --> BYE_Out{BYE} -- To MRFC --> Await_Act[Await_SRF_Disconnection_Active] + + Wait2 --> CANCEL_In{CANCEL} --> OK_CAN{200 OK} --> Req_Term[487 Request Terminated] --> Int_DP_Aban[Int_DP_T_Abandon +/* legID */] --> DP_Aban_DFC[DP_T_Abandon_DFC] --> Int_Cont{Int_Continue} --> CANCEL_Out{CANCEL} -- To MRFC --> Await_Fail[Await_SRF_Disconnection_Fail] + +``` + +Flowchart of Procedure CAMEL\_MT\_CTR (sheet 1) showing the logic for handling Connect To Resource operations, including branching for Play Announcement, Prompt and Collect, and Disconnect Forward Connection, followed by SIP signaling states like Wait for 200 OK and subsequent error or success handling. + +**Figure 4.33-1: Procedure CAMEL\_MT\_CTR (sheet 1)** + +![Flowchart for Procedure CAMEL_MT_CTR (sheet 2). The process starts with 'Relay', which branches into two main paths. The left path involves receiving a 'BYE' from MRFC, sending a '200 OK' to MRFC, releasing the internal SRF, and returning a 'Result:= pass'. The right path involves sending an 'Int_Disconnect_Forward_Connection', receiving a 'BYE' from MRFC, and then entering an 'Await_SRF_Disconnection_Continue' state. From this state, three outcomes are possible: 1) Receiving a 'BYE', sending a '200 OK', performing an 'Int_DP_T_Disconnect', returning a 'Result:= pass'. 2) Receiving a 'CANCEL', sending a '200 OK', performing an 'Int_DP_T_Abandon', encountering a 'DP_T_Abandon_Fail', continuing internally, and returning a 'Result:= fail'. 3) Receiving a '200 OK' from MRFC, releasing the internal SRF, and returning a 'Result:= pass'.](f61d0925551545b5938b3a4d1bbf63c3_img.jpg) + +### Procedure CAMEL\_MT\_CTR + +2(5) + +Procedure in the IM-SSF to handle a Connect To Resource operation. + +Signals to/from the left are to/from the originating party. +Signals to/from the right are to/from the imcnSSF unless otherwise stated. + +``` +graph TD; Relay([Relay]) --> BYE_L{BYE}; BYE_L --> From_MRFC_L[From MRFC]; BYE_L --> BYE_R{BYE}; BYE_R --> To_MRFC_R[To MRFC]; BYE_L --> 200_OK_L{200 OK}; 200_OK_L --> To_MRFC_L[To MRFC]; 200_OK_L --> Int_SRF_Released_L{Int_SRF_Released}; Int_SRF_Released_L --> Result_Pass_L[Result:= pass]; Result_Pass_L --> End_L((X)); Relay --> Int_Disconnect_Forward_Connection{Int_Disconnect_Forward_Connection}; Int_Disconnect_Forward_Connection --> BYE_R; BYE_R --> To_MRFC_R; BYE_R --> Await_SRF_Disconnection_Continue{Await_SRF_Disconnection_Continue}; Await_SRF_Disconnection_Continue --> BYE_R2{BYE}; BYE_R2 --> 200_OK_R2{200 OK}; 200_OK_R2 --> Int_DP_T_Disconnect{Int_DP_T_Disconnect /* legID */}; Int_DP_T_Disconnect --> Result_Pass_R2[Result:= pass]; Result_Pass_R2 --> End_R2((X)); Await_SRF_Disconnection_Continue --> CANCEL{CANCEL}; CANCEL --> 200_OK_R3{200 OK}; 200_OK_R3 --> Int_DP_T_Abandon{Int_DP_T_Abandon /* legID */}; Int_DP_T_Abandon --> DP_T_Abandon_Fail{DP_T_Abandon_Fail}; DP_T_Abandon_Fail --> Int_continue{Int_continue}; Int_continue --> Result_Fail[Result:= fail]; Result_Fail --> End_R3((X)); Await_SRF_Disconnection_Continue --> 200_OK_R4{200 OK}; 200_OK_R4 --> From_MRFC_R4[From MRFC]; 200_OK_R4 --> Int_SRF_Released_R4{Int_SRF_Released}; Int_SRF_Released_R4 --> Result_Pass_R4[Result:= pass]; Result_Pass_R4 --> End_R4((X)); +``` + +Flowchart for Procedure CAMEL\_MT\_CTR (sheet 2). The process starts with 'Relay', which branches into two main paths. The left path involves receiving a 'BYE' from MRFC, sending a '200 OK' to MRFC, releasing the internal SRF, and returning a 'Result:= pass'. The right path involves sending an 'Int\_Disconnect\_Forward\_Connection', receiving a 'BYE' from MRFC, and then entering an 'Await\_SRF\_Disconnection\_Continue' state. From this state, three outcomes are possible: 1) Receiving a 'BYE', sending a '200 OK', performing an 'Int\_DP\_T\_Disconnect', returning a 'Result:= pass'. 2) Receiving a 'CANCEL', sending a '200 OK', performing an 'Int\_DP\_T\_Abandon', encountering a 'DP\_T\_Abandon\_Fail', continuing internally, and returning a 'Result:= fail'. 3) Receiving a '200 OK' from MRFC, releasing the internal SRF, and returning a 'Result:= pass'. + +Figure 4.33-2: Procedure CAMEL\_MT\_CTR (sheet 2) + +![Flowchart for Procedure CAMEL_MT_CTR. It starts with a relay and wait for PlayAnnc or Prompt And Collect request. It then branches into three paths: BYE, CANCEL, and ACK. The BYE path leads to 200 OK, then Int_DP_T_Disconnect, then Wait_For_Disconnect_Forward_Connection. The CANCEL path leads to 200 OK, then Int_DP_T_Abandon, then DP_T_Abandon_DFC, then Int_Continue, then Wait_For_Disconnect_Forward_Connection. The ACK path leads to a dash.](3750b0149a6380885998ab3ca6a8787c_img.jpg) + +### Procedure CAMEL\_MT\_CTR 3(5) + +Procedure in the IM-SSF to handle a Connect To Resource operation. + +Signals to/from the left are to/from the originating party. +Signals to/from the right are to/from the imcnSSF unless otherwise stated. + +``` +graph TD; Start([Relay, Wait_for_PlayAnnc_or_Prompt_And_Collect_request]) --> BYE{BYE}; Start --> CANCEL{CANCEL}; Start --> ACK{ACK}; BYE --> OK1{200 OK}; OK1 --> Disconnect[Int_DP_T_Disconnect / * legID */]; Disconnect --> Wait1[Wait_For_Disconnect_Forward_Connection]; CANCEL --> OK2{200 OK}; OK2 --> Abandon[Int_DP_T_Abandon / * legID */]; Abandon --> DFC[DP_T_Abandon_DFC]; DFC --> Continue[Int_Continue]; Continue --> Wait2[Wait_For_Disconnect_Forward_Connection]; ACK --> Dash[-]; +``` + +Flowchart for Procedure CAMEL\_MT\_CTR. It starts with a relay and wait for PlayAnnc or Prompt And Collect request. It then branches into three paths: BYE, CANCEL, and ACK. The BYE path leads to 200 OK, then Int\_DP\_T\_Disconnect, then Wait\_For\_Disconnect\_Forward\_Connection. The CANCEL path leads to 200 OK, then Int\_DP\_T\_Abandon, then DP\_T\_Abandon\_DFC, then Int\_Continue, then Wait\_For\_Disconnect\_Forward\_Connection. The ACK path leads to a dash. + +Figure 4.33-3: Procedure CAMEL\_MT\_CTR (sheet 3) + +## Procedure CAMEL\_MT\_CTR + +4(5) + +Procedure in the IM-SSF +to handle a Connect To Resource +operation. + +Signals to/from the left are to/from +the originating party. +Signals to/from the right are to/from +the imcnSSF unless otherwise stated. + +![Flowchart for Procedure CAMEL_MT_CTR](869c547c11ac7e123c51aba22289f2cd_img.jpg) + +``` +graph TD; A[Wait_For_Disconnect_Forward_Connection] --> B[Int_Disconnect_Forward_Connection]; B --> C{BYE}; C --> D[To MRFC]; C --> E{Answer Received?}; E -- True --> F[Await_SRF_Disconnection_Active]; E -- False --> G[Await_SRF_Disconnection_Fail]; F --> H[200 OK]; H --> I[From MRFC]; I --> J[Result:= pass]; J --> K(( )); G --> L[200 OK]; L --> M[From MRFC]; M --> N[Result:= fail]; N --> O(( )); +``` + +The flowchart illustrates the procedure CAMEL\_MT\_CTR. It begins with a state 'Wait\_For\_Disconnect\_Forward\_Connection', followed by an action 'Int\_Disconnect\_Forward\_Connection'. A decision 'BYE' follows, leading to 'To MRFC'. Another decision 'Answer Received?' follows. If 'True', it leads to 'Await\_SRF\_Disconnection\_Active', then '200 OK' (From MRFC), then 'Result:= pass', and finally an end state. If 'False', it leads to 'Await\_SRF\_Disconnection\_Fail', then '200 OK' (From MRFC), then 'Result:= fail', and finally an end state. + +Flowchart for Procedure CAMEL\_MT\_CTR + +Figure 4.33-4: Procedure CAMEL\_MT\_CTR (sheet 4) + +![Sequence diagram for Procedure CAMEL_MT_CTR. It shows a 'Relay' node at the top branching into four parallel paths. From left to right: 1. A 'CAP_Specialised ResourceReport' message followed by a '(Notification of PlayAnn completed)' event. 2. A 'CAP_Prompt And Collect User_Information' message followed by a '(Return of Prompt & Collect Result)' event. 3. A 'CAP_Play_Announcement' message followed by a '(Play_Announcement)' event. 4. A 'CAP_Prompt And Collect User_Information' message followed by a '(Prompt And Collect User_Information)' event. All four paths converge to a horizontal line labeled 'ack', which then leads to a 'Relay' node at the bottom.](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +### Procedure CAMEL\_MT\_CTR + +5(5) + +Procedure in the IM-SSF to handle a Connect To Resource operation. + +Signals to/from the left are to/from the MRFC. Signals to/from the right are to/from the imcnSSF. + +``` +graph TD; Relay1([Relay]) --> CAP_SRR[CAP_Specialised ResourceReport]; CAP_SRR --> NPNC{Notification of PlayAnn completed}; NPNC --> ack[ack]; Relay1 --> CAP_PCU[CAP_Prompt And Collect User_Information]; CAP_PCU --> RPCR{Return of Prompt & Collect Result}; RPCR --> ack; Relay1 --> CAP_PA[CAP_Play_Announcement]; CAP_PA --> PA{Play_Announcement}; PA --> ack; Relay1 --> CAP_PCU2[CAP_Prompt And Collect User_Information]; CAP_PCU2 --> PAU{Prompt And Collect User_Information}; PAU --> ack; ack --> Relay2([Relay]) +``` + +Sequence diagram for Procedure CAMEL\_MT\_CTR. It shows a 'Relay' node at the top branching into four parallel paths. From left to right: 1. A 'CAP\_Specialised ResourceReport' message followed by a '(Notification of PlayAnn completed)' event. 2. A 'CAP\_Prompt And Collect User\_Information' message followed by a '(Return of Prompt & Collect Result)' event. 3. A 'CAP\_Play\_Announcement' message followed by a '(Play\_Announcement)' event. 4. A 'CAP\_Prompt And Collect User\_Information' message followed by a '(Prompt And Collect User\_Information)' event. All four paths converge to a horizontal line labeled 'ack', which then leads to a 'Relay' node at the bottom. + +Figure 4.33-5: Procedure CAMEL\_MT\_CTR (sheet 5) + +#### 4.6.1.5 Handling of call in the imcnSSF + +Handling of mobile calls in the imcnSSF may involve the following process and procedures: + +- Process imcnSSF; + +Note that the following procedures are specified in 3GPP TS 23.078 Rel-99 [4]. For these procedures, the imcnSSF shall take the role of the gsmSSF. + +- Procedure Check\_Criteria\_Collected\_Info; +- Procedure Check\_Criteria\_Analysed\_Info; +- Procedure Check\_Criteria\_Unsuccessful; +- Procedure Connect\_To\_Resource; +- Procedure Handle\_AC; +- Procedure Handle\_ACR; +- Procedure Handle\_CIR; +- Procedure Handle\_CIR\_leg; +- Procedure Complete\_FCI\_record; +- Procedure Complete\_all\_FCI\_records; +- Procedure Handle\_O\_Answer; +- Procedure Handle\_T\_Answer. + +The detailed error handling for the process imcnSSF and the associated procedures is specified in 3GPP TS 29.278 [11]. + +##### 4.6.1.5.1 Process imcnSSF + +**Process imcnSSF** + +1(30) + +``` +/* Invocation of imcnSSF in MO, +MT call case. */ +``` + +``` +/* Timers used in the imcnSSF process: +``` + +``` +Tssf: Application timer in the ssf. +``` + +``` +Tcp: Timer for call period. +``` + +``` +This timer measures the duration of a call period. +``` + +``` +Tsw: Timer for tariff switch. +``` + +``` +At the expiration of this timer, a new tariff switch shall be started. +``` + +``` +Tw: Warning timer. +``` + +``` +At the expiration of this timer, a warning tone shall be played to the calling party. +``` + +``` +DELTA: time, measured in the imcnSSF, elapsed between the time an +``` + +``` +ApplyChargingReport operation is sent to the gsmSCF and an +``` + +``` +ApplyCharging operation is received from the gsmSCF. +``` + +``` +Tccd: Control of call duration timer. +``` + +``` +This timer supervises if after sending of ACR a new AC is received. +``` + +``` +Tccd has a value range of 1 to 20 seconds. +``` + +``` +Ranges for the default values for Tssf. +``` + +``` +- non user interaction Tssf timer value: 1 second to 20 seconds +``` + +``` +- user interaction Tssf timer value: 1 minute to 30 minutes +``` + +``` +*/ +``` + +``` +/* TASK definition: +``` + +``` +The sending of an Application_Begin signal opens a new relationship to the gsmSCF. +``` + +``` +The sending of an Application_End or Abort signal terminates the relationship to the gsmSCF. +``` + +``` +*/ +``` + +``` +/* Decision box definitions (1) +``` + +``` +'armed TDPs for this CSI?' +``` + +``` +It is questioned whether or not the ongoing call can encounter further TDPs which are indicated in the current CSI. +``` + +``` +'Call to be released?' +``` + +``` +It is questioned whether or not the ongoing call will be released immediately after imcnSSF has responded; that is the ongoing call will not send any signals further on to the imcnSSF. +NOTE: In this case the imcnSSF shall also go to idle. +``` + +``` +*/ +``` + +``` +/* Decision box definitions (2) +``` + +``` +The following decisions are used by procedures in CCF. +``` + +``` +'imcnSSF invoked?' +``` + +``` +Is the imcnSSF process in any state other than Idle? +``` + +``` +*/ +``` + +**Figure 4.34-1: Process imcnSSF (sheet 1)** + +![State transition diagram for Process imcnSSF. It starts at a Start_State, leading to an Idle state. From Idle, it branches into three parallel paths: Int_Invoke imcnSSF (O-IM-CSI), Int_Invoke imcnSSF (VT-IM-CSI), and Int_Invoke imcnSSF (D-IM-CSI). These paths merge at an Arm DP state, which leads to Int_imcnSSF Invoked and then Wait_For_Request. Another path from Idle leads to Int_O_Exception, Int_T_Exception, which then leads to another Idle state. A third path from Idle leads to an unlabeled state, which then leads to Int_Continue, which finally leads to the second Idle state. A return path from the second Idle state goes back to the Start_State.](18003425d0e8638dde4acc9c5c468c5c_img.jpg) + +### Process imcnSSF + +2(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +The received CSI states whether DP Collected\_Info or DP Analysed\_Information or DP Route\_Select\_Failure or DP T\_Busy or DP T\_No\_Answer or DP Terminating\_Attempt\_Authorised shall be armed as TDP. + +Int\_DP\_O\_Answer, +Int\_DP\_T\_Answer, +Int\_DP\_O\_Abandon, +Int\_DP\_T\_Abandon, +Int\_DP\_Route\_Select\_Failure, +Int\_DP\_O\_No\_Answer, +Int\_DP\_T\_No\_Answer, +Int\_DP\_O\_Busy, +Int\_DP\_T\_Busy, +Int\_DP\_O\_Disconnect, +Int\_DP\_T\_Disconnect, +Int\_DP\_Analysed\_Info + +``` +stateDiagram-v2 + [*] --> Start_State + Start_State --> Idle + Idle --> Int_Invoke_O[Int_Invoke imcnSSF (O-IM-CSI)] + Idle --> Int_Invoke_VT[Int_Invoke imcnSSF (VT-IM-CSI)] + Idle --> Int_Invoke_D[Int_Invoke imcnSSF (D-IM-CSI)] + Int_Invoke_O --> Arm_DP + Int_Invoke_VT --> Arm_DP + Int_Invoke_D --> Arm_DP + Arm_DP --> Int_imcnSSF_Invoked{Int_imcnSSF Invoked} + Int_imcnSSF_Invoked --> Wait_For_Request + Idle --> Int_O_Exception[Int_O_Exception, Int_T_Exception] + Int_O_Exception --> Idle_2[Idle] + Idle --> Unlabeled[ ] + Unlabeled --> Int_Continue{Int_Continue} + Int_Continue --> Idle_2 + Idle_2 --> Start_State +``` + +State transition diagram for Process imcnSSF. It starts at a Start\_State, leading to an Idle state. From Idle, it branches into three parallel paths: Int\_Invoke imcnSSF (O-IM-CSI), Int\_Invoke imcnSSF (VT-IM-CSI), and Int\_Invoke imcnSSF (D-IM-CSI). These paths merge at an Arm DP state, which leads to Int\_imcnSSF Invoked and then Wait\_For\_Request. Another path from Idle leads to Int\_O\_Exception, Int\_T\_Exception, which then leads to another Idle state. A third path from Idle leads to an unlabeled state, which then leads to Int\_Continue, which finally leads to the second Idle state. A return path from the second Idle state goes back to the Start\_State. + +Figure 4.34-2: Process imcnSSF (sheet 2) + +![](0dfdff10c725fe9c332b07ade9d23a5e_img.jpg) + +**Process imcnSSF** + +**3(30)** + +*/\* Invocation of imcnSSF in MO, +MT call case. \*/* + +*/\* Signals to/from the left are to/from the IM-SSF; +signals to/from the right are +to/from the gsmSCF. \*/* + +``` + + graph TD + %% States and Inputs + Wait_For_Request([Wait_For_Request]) + + Input1[/Int_DP_Route_Select_Failure, +Int_DP_T_Busy, +Int_DP_T_No_Answer/] + Input2[/Int_DP_Terminating_ +Attempt_ +Authorized/] + Input3[/Int_DP_ +Collected_ +Information/] + Input4[/Int_T_Exception, +Int_O_Exception/] + Input5[/Int_DP_O_Abandon, +Int_DP_T_Abandon, +Int_DP_O_Disconnect, +Int_DP_T_Disconnect, +Int_DP_O_Answer, +Int_DP_T_Answer, +Int_DP_O_Busy, +Int_DP_O_No_Answer/] + Input6[/Int_DP_ +Analysed_ +Information/] + + Wait_For_Request --> Input1 + Wait_For_Request --> Input2 + Wait_For_Request --> Input3 + Wait_For_Request --> Input4 + Wait_For_Request --> Input5 + Wait_For_Request --> Input6 + + Input4 --> Idle1([Idle]) + Input5 --> Int_Continue1([Int_Continue]) --> Idle2([Idle]) + + Input2 --> Dec1{DP_ +Terminating_ +Attempt_ +Authorized_ +armed?} + Dec1 -- No --> Task1[Check_Criteria_ +Unsuccessful] --> Wait_For_Request + Dec1 -- Yes --> Task2[Check_Gap_ +Criteria] + + Input3 --> Task3[Check_Criteria_ +Collected_Info] + Task3 --> Dec2{Result= +pass?} + Dec2 -- Yes --> Task2 + Dec2 -- No --> Int_Continue2([Int_Continue]) --> Dec3{armed TDPs +for this CSI?} + Dec3 -- Yes --> Wait_For_Request + Dec3 -- No --> Idle3([Idle]) + + Input6 --> Task4[Check_Criteria_ +Analysed_Info] + Task4 --> Dec4{Result= +pass?} + Dec4 -- Yes --> Task2 + Dec4 -- No --> Int_Continue3([Int_Continue]) --> Idle4([Idle]) + + Task2 --> Dec5{Result= +pass?} + Dec5 -- Yes --> Conn1((1)) + Dec5 -- No --> Dec6{Default Call Handling = +Continue Call?} + + Dec6 -- Yes --> Int_Continue4([Int_Continue]) --> Dec7{armed TDPs +for this CSI?} + Dec7 -- Yes --> Wait_For_Request + Dec7 -- No --> Idle5([Idle]) + + Dec6 -- No --> Task5[Apply Gap +treatment +if present] --> Int_ReleaseCall([Int_ReleaseCall]) --> Idle6([Idle]) + + %% Additional logic for Result=pass? from Input2 path + Input2_Pass{Result= +pass?} + Input2_Pass -- Yes --> Task2 + Input2_Pass -- No --> Int_Continue5([Int_Continue]) --> Idle7([Idle]) + + %% Connector 2 logic + Conn2((2)) --> Dec8{Result = +pass?} + Dec8 -- Yes --> Conn2 + Dec8 -- No --> Task2 + +``` + +*Gap treatment depends on the info received in the Call Gap message (i.e. tone/announce, cause, etc.)* + +Figure 4.34-3: Process imcnSSF (sheet 3) + +![State transition diagram for Process imcnSSF. It consists of two parallel vertical flows labeled 1 and 2. Flow 1 starts with 'Set Tssf to default non user interaction Tssf timer interval and restart Tssf', followed by 'Application_Begin', 'Set Control Relationship', 'CAP_InitialDB', an empty box, and 'Waiting_for_Instructions'. Flow 2 starts with the same 'Set Tssf...' step, followed by 'Application_Begin', 'Set Control Relationship', 'CAP_InitialDB', and 'Waiting_for_Instructions_for_DS'. A horizontal line connects the empty box in Flow 1 to a box containing initialization variables: ACR sent:=false, AC pending:=false, Outstanding requests = 1, and Outstanding Call Information Report = 0.](ffe0fef452a0ae9a20253c319c54e13c_img.jpg) + +### Process imcnSSF 4(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` +graph TD; subgraph Flow1 [Flow 1]; S1((1)) --> T1['Set Tssf to default non user interaction Tssf timer interval and restart Tssf']; T1 --> A1{{Application_Begin}}; A1 --> R1['Set Control Relationship']; R1 --> C1{{CAP_InitialDB}}; C1 --> E1[ ]; E1 --> W1([Waiting_for_Instructions]); E1 --> I1[ACR sent:=false
AC pending:=false
Outstanding requests = 1
Outstanding Call Information Report = 0]; subgraph Flow2 [Flow 2]; S2((2)) --> T2['Set Tssf to default non user interaction Tssf timer interval and restart Tssf']; T2 --> A2{{Application_Begin}}; A2 --> R2['Set Control Relationship']; R2 --> C2{{CAP_InitialDB}}; C2 --> W2([Waiting_for_Instructions_for_DS]); end +``` + +State transition diagram for Process imcnSSF. It consists of two parallel vertical flows labeled 1 and 2. Flow 1 starts with 'Set Tssf to default non user interaction Tssf timer interval and restart Tssf', followed by 'Application\_Begin', 'Set Control Relationship', 'CAP\_InitialDB', an empty box, and 'Waiting\_for\_Instructions'. Flow 2 starts with the same 'Set Tssf...' step, followed by 'Application\_Begin', 'Set Control Relationship', 'CAP\_InitialDB', and 'Waiting\_for\_Instructions\_for\_DS'. A horizontal line connects the empty box in Flow 1 to a box containing initialization variables: ACR sent:=false, AC pending:=false, Outstanding requests = 1, and Outstanding Call Information Report = 0. + +Figure 4.34-4: Process imcnSSF (sheet 4) + +![State transition diagram for Process imcnSSF. It starts at 'Waiting_for_Instructions', branches into 'CAP_Apply_Charging' and 'Timer expiry Tssf'. The 'CAP_Apply_Charging' path leads to 'Handle_AC', then 'Set Tssf to CAP_Reset_Timer time interval and restart Tssf', and back to 'Waiting_For_Instructions'. The 'Timer expiry Tssf' path leads to 'Internal', 'Abort', 'Int_Error', and 'Complete_all_FCI_records'. From 'Complete_all_FCI_records', a decision 'Default call handling = continue call?' leads to 'Wait_For_Request' (Yes) or another decision 'armed TDPs for this CSI?' (No). The 'armed TDPs for this CSI?' decision leads to 'Wait_For_Request' (Yes) or 'Idle' (No).](a963ca41bde1669b18a4b783616f228b_img.jpg) + +**Process imcnSSF** 5(30) + +``` +/* Invocation of imcnSSF in MO, MT call case. */ +``` + +``` +/* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. */ +``` + +``` +stateDiagram-v2 + [*] --> Waiting_for_Instructions + Waiting_for_Instructions --> CAP_Apply_Charging + Waiting_for_Instructions --> Timer_expiry_Tssf + CAP_Apply_Charging --> Handle_AC + Handle_AC --> Set_Tssf_to_CAP_Reset_Timer_time_interval_and_restart_Tssf + Set_Tssf_to_CAP_Reset_Timer_time_interval_and_restart_Tssf --> Waiting_For_Instructions + Timer_expiry_Tssf --> Internal + Timer_expiry_Tssf --> Abort + Abort --> Int_Error + Int_Error --> Complete_all_FCI_records + Complete_all_FCI_records --> Default_call_handling_continue_call + Default_call_handling_continue_call --> Wait_For_Request : Yes + Default_call_handling_continue_call --> armed_TDPs_for_this_CSI : No + armed_TDPs_for_this_CSI --> Wait_For_Request : Yes + armed_TDPs_for_this_CSI --> Idle : No +``` + +State transition diagram for Process imcnSSF. It starts at 'Waiting\_for\_Instructions', branches into 'CAP\_Apply\_Charging' and 'Timer expiry Tssf'. The 'CAP\_Apply\_Charging' path leads to 'Handle\_AC', then 'Set Tssf to CAP\_Reset\_Timer time interval and restart Tssf', and back to 'Waiting\_For\_Instructions'. The 'Timer expiry Tssf' path leads to 'Internal', 'Abort', 'Int\_Error', and 'Complete\_all\_FCI\_records'. From 'Complete\_all\_FCI\_records', a decision 'Default call handling = continue call?' leads to 'Wait\_For\_Request' (Yes) or another decision 'armed TDPs for this CSI?' (No). The 'armed TDPs for this CSI?' decision leads to 'Wait\_For\_Request' (Yes) or 'Idle' (No). + +Figure 4.34-5: Process imcnSSF (sheet 5) + +![Flowchart for Process imcnSSF. It starts with an initial node labeled 'Waiting_for_Instructions, Waiting_for_Instructions_for_DS'. This leads to a 'CAP_Reset_Timer' process block. Below that is a decision diamond with the condition 'Not Waiting for first response after IDP OR first reset Timer in this dialogue ?'. If 'Yes', it leads to a 'Set Tssf to CAP_Reset_Timer time interval and restart Tssf' process block. If 'No', it bypasses this block. Both paths lead to a final node labeled '-'.](de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg) + +### Process imcnSSF 6(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` +graph TD; Start([Waiting_for_Instructions, Waiting_for_Instructions_for_DS]) --> CAP_Reset_Timer[CAP_Reset_Timer]; CAP_Reset_Timer --> Decision{Not Waiting for first response after IDP OR first reset Timer in this dialogue ?}; Decision -- Yes --> Set_Tssf[Set Tssf to CAP_Reset_Timer time interval and restart Tssf]; Decision -- No --> End([-]); Set_Tssf --> End; +``` + +Flowchart for Process imcnSSF. It starts with an initial node labeled 'Waiting\_for\_Instructions, Waiting\_for\_Instructions\_for\_DS'. This leads to a 'CAP\_Reset\_Timer' process block. Below that is a decision diamond with the condition 'Not Waiting for first response after IDP OR first reset Timer in this dialogue ?'. If 'Yes', it leads to a 'Set Tssf to CAP\_Reset\_Timer time interval and restart Tssf' process block. If 'No', it bypasses this block. Both paths lead to a final node labeled '-'. + +Figure 4.34-6: Process imcnSSF (sheet 6) + +![](e16bfa31d748f4d99ec4ae3d16656926_img.jpg) + +**Process imcnSSF** 7(30) + +*/\* Invocation of imcnSSF in MO, +MT call case. \*/* + +*/\* Signals to/from the left are to/from the IM-SSF; +signals to/from the right are +to/from the gsmSCF. \*/* + +**Waiting\_for\_Instructions** + +CAP\_Continue + +Stop Tssf + +CAP\_Continue\_ +WithArgument + +Stop Tssf + +CAP\_Connect + +Stop Tssf + +DP\_O\_No\_answer of leg2 +DP\_T\_No\_answer of leg2 +DP\_O\_Busy of leg2 +DP\_T\_Busy of leg2 +DP\_Route\_Select\_Failure of leg2 +DP\_O\_Disconnect of leg2 +DP\_T\_Disconnect of leg2 + +DP\_O\_Disconnect of leg1 +DP\_T\_Disconnect of leg1 + +Message was received due to +DP of Leg ID + +Complete\_ +FCI\_record +(leg2) + +DP was due to +Call Forwarding + +No → Handle\_CIR\_ +leg(leg1) + +Yes + +ELSE + +Complete\_ +FCI\_record +(leg1) + +Handle\_CIR\_ +leg(leg2) + +Int\_Continue\_ +\_With\_ +\_Argument + +Leg 1 is available + +No → Int\_Continue + +Yes → Int\_Connect + +Message was received due to +DP of Leg ID + +ELSE → Complete\_ +FCI\_record +(leg2) + +DP\_O\_No\_answer of leg2 +DP\_T\_No\_answer of leg2 +DP\_O\_Busy of leg2 +DP\_T\_Busy of leg2 +DP\_Route\_Select\_Failure of leg2 +DP\_O\_Disconnect of leg2 +DP\_T\_Disconnect of leg2 + +Current DP is +O\_Disconnect or +T\_Disconnect? + +Yes → Outstanding\_ +Requests := +Outstanding\_ +Requests - 1 + +No → Int\_Continue + +Outstanding\_ +Requests > 0? + +Yes → Set Tssf to last +used time interval +and restart Tssf → **Waiting\_For\_ +Instructions** + +No → Int\_Continue + +Any remaining +armed EDP-Rs? + +Yes → **Monitoring** + +No → Outstanding\_ +Requests := 0 + +Any remaining No +armed EDP or +report pending? + +Yes → 'Set Monitor +Relationship' → **Wait\_For\_ +\_Request** + +Application\_ +End + +Complete\_all\_ +FCI\_records + +'Call to be +released?' + +Yes → 'armed TDPs +for this CSI?' + +No → **Idle** + +Figure 4.34-7: Process imcnSSF (sheet 7) + +![State transition diagram for Process imcnSSF. The process starts at 'Waiting_for_Instructions'. It branches into three main paths: 1) CAP_Request_ReportBCSM_Event leads to 'Set Tssf to last used time interval and restart Tssf', then 'Arming rules fulfilled?'. If 'No', it goes to 'Error Unexpected Data Value' and back to 'Waiting_For_Instructions'. If 'Yes', it goes to 'Arm EDP and/or disarm EDP', then 'Waiting_For_Instructions'. 2) CAP_ReleaseCall leads to 'AC pending?'. If 'False', it goes to 'CallActive := FALSE' and then to 'CAP_Apply_Charging_Report'. If 'True', it goes to 'CAP_Apply_Charging_Report'. 3) Int_T_Exception, Int_O_Exception leads to 'AC pending?'. If 'False', it goes to 'CAP_Apply_Charging_Report'. If 'True', it goes to 'CAP_Apply_Charging_Report', then 'Handle_CIR', 'Complete_all_FCI_records', and 'Abort'. All paths lead to 'Application_End', 'Int_Release Call', 'Stop Tssf', and finally 'Idle'.](c0ca823603794512478906b302176bca_img.jpg) + +### Process imcnSSF + +8(30) + +``` +/* Invocation of imcnSSF in MO, MT call case. */ +``` + +``` +/* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. */ +``` + +``` +stateDiagram-v2 + [*] --> Waiting_for_Instructions + Waiting_for_Instructions --> CAP_Request_ReportBCSM_Event + Waiting_for_Instructions --> CAP_ReleaseCall + Waiting_for_Instructions --> Int_T_Exception_Int_O_Exception + + CAP_Request_ReportBCSM_Event --> Set_Tssf + Set_Tssf --> Arming_rules_fulfilled + Arming_rules_fulfilled --> No + Arming_rules_fulfilled --> Yes + No --> Error_Unexpected_Data_Value + Error_Unexpected_Data_Value --> Waiting_For_Instructions + Yes --> Arm_EDP + Arm_EDP --> Waiting_For_Instructions + + CAP_ReleaseCall --> AC_pending_1 + AC_pending_1 --> False_1 + AC_pending_1 --> True_1 + False_1 --> CallActive_FALSE + True_1 --> CAP_Apply_Charging_Report_1 + CallActive_FALSE --> CAP_Apply_Charging_Report_1 + + Int_T_Exception_Int_O_Exception --> AC_pending_2 + AC_pending_2 --> False_2 + AC_pending_2 --> True_2 + False_2 --> CAP_Apply_Charging_Report_2 + True_2 --> CAP_Apply_Charging_Report_2 + CAP_Apply_Charging_Report_2 --> Handle_CIR_2 + Handle_CIR_2 --> Complete_all_FCI_records_2 + Complete_all_FCI_records_2 --> Abort + + CAP_Apply_Charging_Report_1 --> Handle_CIR_1 + Handle_CIR_1 --> Complete_all_FCI_records_1 + Complete_all_FCI_records_1 --> Application_End + + Application_End --> Int_Release_Call + Int_Release_Call --> Stop_Tssf + Stop_Tssf --> Idle + + Note right of Arming_rules_fulfilled: Depending on the Monitoring parameter received for the indicated detection point. For DP O/T Disconnect a DP is only disarmed for the leg for which the event was received. +``` + +State transition diagram for Process imcnSSF: + +- Initial state: **Waiting\_for\_Instructions** +- Transitions from **Waiting\_for\_Instructions**: + - CAP\_Request\_ReportBCSM\_Event** (to left) + - CAP\_ReleaseCall** (to left) + - Int\_T\_Exception, Int\_O\_Exception** (to right) +- Path 1 (CAP\_Request\_ReportBCSM\_Event): + - Process: **Set Tssf to last used time interval and restart Tssf** + - Decision: **Arming rules fulfilled?** + - If **No**: **Error Unexpected Data Value** (to right) -> **Waiting\_For\_Instructions** (to left) + - If **Yes**: **Arm EDP and/or disarm EDP** (to left) -> **Waiting\_For\_Instructions** (to left) +- Path 2 (CAP\_ReleaseCall): + - Decision: **AC pending?** + - If **False**: **CallActive := FALSE** (to left) -> **CAP\_Apply\_Charging\_Report** (to left) + - If **True**: **CAP\_Apply\_Charging\_Report** (to left) +- Path 3 (Int\_T\_Exception, Int\_O\_Exception): + - Decision: **AC pending?** + - If **False**: **CAP\_Apply\_Charging\_Report** (to left) + - If **True**: **CAP\_Apply\_Charging\_Report** (to left) -> **Handle\_CIR** (to right) -> **Complete\_all\_FCI\_records** (to right) -> **Abort** (to right) +- Common Path: + - CAP\_Apply\_Charging\_Report** (to left) -> **Handle\_CIR** (to left) -> **Complete\_all\_FCI\_records** (to left) -> **Application\_End** (to left) -> **Int\_Release Call** (to left) -> **Stop Tssf** (to left) -> **Idle** (to left) + +State transition diagram for Process imcnSSF. The process starts at 'Waiting\_for\_Instructions'. It branches into three main paths: 1) CAP\_Request\_ReportBCSM\_Event leads to 'Set Tssf to last used time interval and restart Tssf', then 'Arming rules fulfilled?'. If 'No', it goes to 'Error Unexpected Data Value' and back to 'Waiting\_For\_Instructions'. If 'Yes', it goes to 'Arm EDP and/or disarm EDP', then 'Waiting\_For\_Instructions'. 2) CAP\_ReleaseCall leads to 'AC pending?'. If 'False', it goes to 'CallActive := FALSE' and then to 'CAP\_Apply\_Charging\_Report'. If 'True', it goes to 'CAP\_Apply\_Charging\_Report'. 3) Int\_T\_Exception, Int\_O\_Exception leads to 'AC pending?'. If 'False', it goes to 'CAP\_Apply\_Charging\_Report'. If 'True', it goes to 'CAP\_Apply\_Charging\_Report', then 'Handle\_CIR', 'Complete\_all\_FCI\_records', and 'Abort'. All paths lead to 'Application\_End', 'Int\_Release Call', 'Stop Tssf', and finally 'Idle'. + +Figure 4.34-8: Process imcnSSF (sheet 8) + +![Flowchart for Process imcnSSF. The sequence is: Waiting_For_Instructions -> CAP_Cancel_(All) -> Disarm all EDPs -> Cancel all reports -> Set Tssf to last used time interval and restart Tssf -> Waiting_For_Instructions.](fc3e2b49a9f850951570e502393b697f_img.jpg) + +### Process imcnSSF 9(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` +graph TD; A([Waiting_For_Instructions]) --> B[/CAP_Cancel_(All)/]; B --> C[Disarm all EDPs]; C --> D[Cancel all reports]; D --> E[Set Tssf to last used time interval and restart Tssf]; E --> F([Waiting_For_Instructions]); +``` + +Flowchart for Process imcnSSF. The sequence is: Waiting\_For\_Instructions -> CAP\_Cancel\_(All) -> Disarm all EDPs -> Cancel all reports -> Set Tssf to last used time interval and restart Tssf -> Waiting\_For\_Instructions. + +Figure 4.34-9: Process imcnSSF (sheet 9) + +![Flowchart for Process imcnSSF. The process starts with 'Waiting_for_Instructions', followed by 'CAP_ConnectToResource', 'Stop Tssf', and 'Connect_To_Resource'. A decision 'result' follows. If 'fail', it goes to 'Set Tssf to last used time interval and restart Tssf', then 'Return appropriate error to the imcnSCF', and back to 'Waiting_For_Instructions'. If 'pass', it goes to 'AC pending?'. If 'No', it goes to 'Start Tcp'. If 'Yes', it goes to 'Start Tcp'. From 'Start Tcp', it goes to 'Tw>0'. If 'No', it goes to 'Start Tw'. If 'Yes', it goes to 'Start Tw'. From 'Start Tw', it goes to 'Set Tssf to user interaction timer value and restart Tssf', which then leads to 'Waiting_For_End_Of_User_Interaction'.](6a993bfdf2e00cfad01c4d2188a75d86_img.jpg) + +### Process imcnSSF + +10(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` +graph TD; A([Waiting_for_Instructions]) --> B[/CAP_ConnectToResource/]; B --> C[Stop Tssf]; C --> D[Connect_To_Resource]; D --> E{result}; E -- fail --> F[Set Tssf to last used time interval and restart Tssf]; F --> G[/Return appropriate error to the imcnSCF/]; G --> H([Waiting_For_Instructions]); E -- pass --> I{AC pending?}; I -- No --> J[Start Tcp]; I -- Yes --> J; J --> K{Tw>0}; K -- No --> L[Start Tw]; K -- Yes --> L; L --> M[Set Tssf to user interaction timer value and restart Tssf]; M --> N([Waiting_For_End_Of_User_Interaction]); +``` + +Flowchart for Process imcnSSF. The process starts with 'Waiting\_for\_Instructions', followed by 'CAP\_ConnectToResource', 'Stop Tssf', and 'Connect\_To\_Resource'. A decision 'result' follows. If 'fail', it goes to 'Set Tssf to last used time interval and restart Tssf', then 'Return appropriate error to the imcnSCF', and back to 'Waiting\_For\_Instructions'. If 'pass', it goes to 'AC pending?'. If 'No', it goes to 'Start Tcp'. If 'Yes', it goes to 'Start Tcp'. From 'Start Tcp', it goes to 'Tw>0'. If 'No', it goes to 'Start Tw'. If 'Yes', it goes to 'Start Tw'. From 'Start Tw', it goes to 'Set Tssf to user interaction timer value and restart Tssf', which then leads to 'Waiting\_For\_End\_Of\_User\_Interaction'. + +Figure 4.34-10: Process imcnSSF (sheet 10) + +![State transition diagram for Process imcnSSF. The process starts in the 'Monitoring' state, receives a 'CAP_Request_Report_BCSM_Event', checks if 'Arming rules fulfilled?'. If 'No', it goes to 'Error: Unexpected Data Value' and back to 'Monitoring'. If 'Yes', it performs 'Arm DP and/or disarm DP', then checks if 'Any armed EDP or report pending'. If 'Yes', it goes to 'Monitoring'. If 'No', it performs 'Complete_all_FCI_records', then 'Application_End', then checks if ''armed TDPs for this CSI?'. If 'Yes', it goes to 'Wait_For_Request'. If 'No', it goes to 'Idle'. A note indicates that in 'Monitoring', only requests to disarm DPs or to sent notifications are allowed.](d04c50badc78d5ba47bf4e352af4a754_img.jpg) + +**Process imcnSSF** 11(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the right are to/from the gsmSCF. \*/ + +``` +stateDiagram-v2 + [*] --> Monitoring + Monitoring --> CAP_Request_Report_BCSM_Event + CAP_Request_Report_BCSM_Event --> Arming_rules_fulfilled{Arming rules fulfilled?} + Arming_rules_fulfilled -- No --> Error: Unexpected Data Value + Error: Unexpected Data Value --> Monitoring + Arming_rules_fulfilled -- Yes --> Arm_DP_and_or_disarm_DP[Arm DP and/or disarm DP] + Arm_DP_and_or_disarm_DP --> Any_armEDP_or_report_pending{Any armed EDP or report pending} + Any_armEDP_or_report_pending -- Yes --> Monitoring + Any_armEDP_or_report_pending -- No --> Complete_all_FCI_records[Complete_all_FCI_records] + Complete_all_FCI_records --> Application_End + Application_End --> armed_TDPs{''armed TDPs for this CSI?} + armed_TDPs -- Yes --> Wait_For_Request[Wait_For_Request] + armed_TDPs -- No --> Idle +``` + +In state 'Monitoring', only requests to disarm DPs or to sent notifications are allowed + +State transition diagram for Process imcnSSF. The process starts in the 'Monitoring' state, receives a 'CAP\_Request\_Report\_BCSM\_Event', checks if 'Arming rules fulfilled?'. If 'No', it goes to 'Error: Unexpected Data Value' and back to 'Monitoring'. If 'Yes', it performs 'Arm DP and/or disarm DP', then checks if 'Any armed EDP or report pending'. If 'Yes', it goes to 'Monitoring'. If 'No', it performs 'Complete\_all\_FCI\_records', then 'Application\_End', then checks if ''armed TDPs for this CSI?'. If 'Yes', it goes to 'Wait\_For\_Request'. If 'No', it goes to 'Idle'. A note indicates that in 'Monitoring', only requests to disarm DPs or to sent notifications are allowed. + +Figure 4.34-11: Process imcnSSF (sheet 11) + +![Flowchart for Process imcnSSF. It starts with an initial state leading to four parallel signal inputs: Int_DP_O_Disconnect, Int_DP_T_Disconnect, Int_DP_O_Abandon, and Int_DP_T_Abandon. A decision diamond 'DP armed for legID?' follows. If 'No', it goes to 'Perform implicit disarming of DPs' -> 'Stop Tssf' -> 'Int_Continue' -> 'Handle_ACR' -> 'Handle_CIR' -> 'Complete_all_FCI_records' -> 'Application_End' -> 'Idle'. If 'Yes', it goes to another decision 'DP armed as EDP-R?'. If 'Yes', it goes to 'Perform implicit disarming of DPs' -> 'Handle_ACR' -> 'Handle_CIR leg (legID)' -> 'CAP_Event_Report_BCSM (Interrupted)' -> 'Set Tssf to default non user interaction timer value and restart Tssf' -> 'Outstanding_Requests := Outstanding_Requests + 1' -> 'Waiting_for_Instructions'. If 'No', it goes to 'Perform implicit disarming of DPs' -> 'CAP_Event_Report_BCSM (Notify & Continue)' -> 'Handle_ACR' -> 'Handle_CIR' -> 'Stop Tssf' -> 'Int_Continue' -> 'Complete_all_FCI_records' -> 'Application_End' -> 'Idle'. There are also 'CallActive := FALSE' assignments in the flow.](e18841eb4a995df8354a793459e12fd0_img.jpg) + +### Process imcnSSF + +12(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +Waiting\_for\_Instructions, +Monitoring , +Waiting\_for\_End\_Of\_User\_Interaction + +``` + + graph TD + Start([ ]) --> In1[Int_DP_O_Disconnect +/* legID */] + Start --> In2[Int_DP_T_Disconnect +/* legID */] + Start --> In3[Int_DP_O_Abandon] + Start --> In4[Int_DP_T_Abandon] + + In1 & In2 & In3 & In4 --> D1{DP armed for legID?} + + D1 -- No --> P1[Perform implicit disarming of DPs] + P1 --> S1[Stop Tssf] + S1 --> I1{Int_Continue} + I1 --> H1[Handle_ACR] + H1 --> C1[Handle_CIR] + C1 --> F1[Complete_all_FCI_records] + F1 --> AE1[Application_End] + AE1 --> Idle1([Idle]) + + D1 -- Yes --> D2{DP armed as EDP-R?} + + D2 -- Yes --> P2[Perform implicit disarming of DPs] + P2 --> H2[Handle_ACR] + H2 --> C2[Handle_CIR leg (legID)] + C2 --> CB2[CAP_Event_Report_BCSM (Interrupted)] + CB2 --> ST[Set Tssf to default non user interaction timer value and restart Tssf] + ST --> OR[Outstanding_Requests := Outstanding_Requests + 1] + OR --> WI1([Waiting_for_Instructions]) + + D2 -- No --> P3[Perform implicit disarming of DPs] + P3 --> CB3[CAP_Event_Report_BCSM (Notify & Continue)] + CB3 --> H3[Handle_ACR] + H3 --> C3[Handle_CIR] + C3 --> S3[Stop Tssf] + S3 --> I3{Int_Continue} + I3 --> F3[Complete_all_FCI_records] + F3 --> AE3[Application_End] + AE3 --> Idle3([Idle]) + + CB3 -.-> CF1[CallActive := FALSE] + CB2 -.-> CF2[CallActive := FALSE] + + Note1[/* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. */] + +``` + +Flowchart for Process imcnSSF. It starts with an initial state leading to four parallel signal inputs: Int\_DP\_O\_Disconnect, Int\_DP\_T\_Disconnect, Int\_DP\_O\_Abandon, and Int\_DP\_T\_Abandon. A decision diamond 'DP armed for legID?' follows. If 'No', it goes to 'Perform implicit disarming of DPs' -> 'Stop Tssf' -> 'Int\_Continue' -> 'Handle\_ACR' -> 'Handle\_CIR' -> 'Complete\_all\_FCI\_records' -> 'Application\_End' -> 'Idle'. If 'Yes', it goes to another decision 'DP armed as EDP-R?'. If 'Yes', it goes to 'Perform implicit disarming of DPs' -> 'Handle\_ACR' -> 'Handle\_CIR leg (legID)' -> 'CAP\_Event\_Report\_BCSM (Interrupted)' -> 'Set Tssf to default non user interaction timer value and restart Tssf' -> 'Outstanding\_Requests := Outstanding\_Requests + 1' -> 'Waiting\_for\_Instructions'. If 'No', it goes to 'Perform implicit disarming of DPs' -> 'CAP\_Event\_Report\_BCSM (Notify & Continue)' -> 'Handle\_ACR' -> 'Handle\_CIR' -> 'Stop Tssf' -> 'Int\_Continue' -> 'Complete\_all\_FCI\_records' -> 'Application\_End' -> 'Idle'. There are also 'CallActive := FALSE' assignments in the flow. + +Figure 4.34-12: Process imcnSSF (sheet 12) + +![State transition diagram for Process imcnSSF. It starts at 'Waiting_for_End_Of_User_Interaction' and branches based on four expiration events: 'Tw expired', 'Tsw expired', 'Tcp expired', and 'Tccd expired'. 'Tw expired' leads to 'Int_Apply_Warning_Tone' and then to a junction. 'Tsw expired' leads to 'Store current value of Tcp' and then to the same junction. 'Tcp expired' leads to a 'Release?' decision. If 'No', it goes to 'Handle_ACR', 'Set Tssf to last used time interval and restart Tssf', 'Start Tccd', and then to the junction. If 'Yes', it goes to 'CAP_Apply_Charging_Report', 'Int_Disconnect_Forward_Connections', 'Handle_CIR', 'Complete_all_FCI_record', 'Int_Release', 'Stop Tssf', 'Application_End', and finally 'Idle'. A note indicates that 'Tw expired' provokes the IM-SSF to play a tone. At the junction, 'CallActive := TRUE' is set. From 'Idle', a transition leads to a final state with 'CallActive := FALSE; 'CallReleasedAtTcpExpiry' present;'.](0b998e3ad8f9d104768642612605cb35_img.jpg) + +### Process imcnSSF 13(30) + +*/\* Invocation of imcnSSF in MO, MT call case. \*/* + +*/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/* + +``` +stateDiagram-v2 + [*] --> Waiting_for_End_Of_User_Interaction + Waiting_for_End_Of_User_Interaction --> Tw_expired + Waiting_for_End_Of_User_Interaction --> Tsw_expired + Waiting_for_End_Of_User_Interaction --> Tcp_expired + Waiting_for_End_Of_User_Interaction --> Tccd_expired + + Tw_expired --> Int_Apply_Warning_Tone + Int_Apply_Warning_Tone --> Junction + + Tsw_expired --> Store_current_value_of_Tcp[Store current value of Tcp] + Store_current_value_of_Tcp --> Junction + + Tcp_expired --> Release_Q{Release?} + Release_Q -- No --> Handle_ACR + Handle_ACR --> Set_Tssf[Set Tssf to last used time interval and restart Tssf] + Set_Tssf --> Start_Tccd[Start Tccd] + Start_Tccd --> Junction + + Release_Q -- Yes --> CAP_Apply_Charging_Report + CAP_Apply_Charging_Report --> Int_Disconnect_Forward_Connections + Int_Disconnect_Forward_Connections --> Handle_CIR + Handle_CIR --> Complete_all_FCI_record + Complete_all_FCI_record --> Int_Release + Int_Release --> Stop_Tssf[Stop Tssf] + Stop_Tssf --> Application_End + Application_End --> Idle + + Junction --> CallActive_TRUE[CallActive := TRUE] + CallActive_TRUE --> [*] + + Idle --> CallActive_FALSE[CallActive := FALSE; 'CallReleasedAtTcpExpiry' present;] + CallActive_FALSE --> [*] +``` + +This provokes the IM-SSF to play a tone to the party for whom the BCSM is operating + +CallActive := TRUE + +CallActive := FALSE; 'CallReleasedAtTcpExpiry' present; + +State transition diagram for Process imcnSSF. It starts at 'Waiting\_for\_End\_Of\_User\_Interaction' and branches based on four expiration events: 'Tw expired', 'Tsw expired', 'Tcp expired', and 'Tccd expired'. 'Tw expired' leads to 'Int\_Apply\_Warning\_Tone' and then to a junction. 'Tsw expired' leads to 'Store current value of Tcp' and then to the same junction. 'Tcp expired' leads to a 'Release?' decision. If 'No', it goes to 'Handle\_ACR', 'Set Tssf to last used time interval and restart Tssf', 'Start Tccd', and then to the junction. If 'Yes', it goes to 'CAP\_Apply\_Charging\_Report', 'Int\_Disconnect\_Forward\_Connections', 'Handle\_CIR', 'Complete\_all\_FCI\_record', 'Int\_Release', 'Stop Tssf', 'Application\_End', and finally 'Idle'. A note indicates that 'Tw expired' provokes the IM-SSF to play a tone. At the junction, 'CallActive := TRUE' is set. From 'Idle', a transition leads to a final state with 'CallActive := FALSE; 'CallReleasedAtTcpExpiry' present;'. + +Figure 4.34-13: Process imcnSSF (sheet 13) + +![State transition diagram for Process imcnSSF. The process starts in 'Monitoring' state. Transitions are triggered by 'Tw expired', 'Tsw expired', 'Tcp expired', and 'Tccd expired'. 'Tw expired' leads to 'Int_Apply_Warning_Tone' (note: provokes IM-SSF to play a tone) and then to a merge point. 'Tsw expired' leads to 'Store current value of Tcp' and then to the same merge point. 'Tcp expired' leads to a 'Release?' decision. If 'Yes', it goes to 'CAP_Apply_Charging_Report', 'Handle_CIR', 'Complete_all_FCI_record', 'Int_Release', 'Application_End', and 'Idle'. If 'No', it goes to another decision: ''Any EDP or reports outstanding?''. If 'Yes', it goes to 'CAP_Apply_Charging_Report', 'Complete_all_FCI_record', 'Application_End', and 'Idle'. If 'No', it goes to 'Handle_ACR', 'Set Tssf to last used time interval and restart Tssf', 'Start Tccd', and then to the merge point. A note near the merge point indicates 'CallActive := TRUE'. A final note indicates 'CallActive := FALSE; 'CallReleasedAtTcpExpiry' present'.](69467ece0a576b4c2ec3e0c89ba61527_img.jpg) + +**Process imcnSSF** 14(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` + +stateDiagram-v2 + [*] --> Monitoring + Monitoring --> Tw_expired: Tw expired + Monitoring --> Tsw_expired: Tsw expired + Monitoring --> Tcp_expired: Tcp expired + Monitoring --> Tccd_expired: Tccd expired + + Tw_expired --> Int_Apply_Warning_Tone + Int_Apply_Warning_Tone --> MergePoint + + Tsw_expired --> Store_current_value_of_Tcp: Store current value of Tcp + Store_current_value_of_Tcp --> MergePoint + + Tcp_expired --> Release_Q: Release? + Release_Q -- Yes --> CAP_Apply_Charging_Report_1: CAP_Apply_Charging_Report + Release_Q -- No --> Any_EDP_outstanding_Q: 'Any EDP or reports outstanding?' + + Any_EDP_outstanding_Q -- Yes --> CAP_Apply_Charging_Report_2: CAP_Apply_Charging_Report + Any_EDP_outstanding_Q -- No --> Handle_ACR + + CAP_Apply_Charging_Report_1 --> Handle_CIR + Handle_CIR --> Complete_all_FCI_record_1: Complete_all_FCI_record + Complete_all_FCI_record_1 --> Int_Release + Int_Release --> Application_End_1: Application_End + Application_End_1 --> Idle_1: Idle + + CAP_Apply_Charging_Report_2 --> Complete_all_FCI_record_2: Complete_all_FCI_record + Complete_all_FCI_record_2 --> Application_End_2: Application_End + Application_End_2 --> Idle_2: Idle + + Handle_ACR --> Set_Tssf: Set Tssf to last used time interval and restart Tssf + Set_Tssf --> Start_Tccd: Start Tccd + Start_Tccd --> MergePoint + + MergePoint --> Note1: CallActive := TRUE + Note1 --> Note2: CallActive := FALSE; 'CallReleasedAtTcpExpiry' present + +``` + +This provokes the IM-SSF to play a tone to the party for whom the BCSM is operating + +CallActive := TRUE + +CallActive := FALSE; 'CallReleasedAtTcpExpiry' present + +State transition diagram for Process imcnSSF. The process starts in 'Monitoring' state. Transitions are triggered by 'Tw expired', 'Tsw expired', 'Tcp expired', and 'Tccd expired'. 'Tw expired' leads to 'Int\_Apply\_Warning\_Tone' (note: provokes IM-SSF to play a tone) and then to a merge point. 'Tsw expired' leads to 'Store current value of Tcp' and then to the same merge point. 'Tcp expired' leads to a 'Release?' decision. If 'Yes', it goes to 'CAP\_Apply\_Charging\_Report', 'Handle\_CIR', 'Complete\_all\_FCI\_record', 'Int\_Release', 'Application\_End', and 'Idle'. If 'No', it goes to another decision: ''Any EDP or reports outstanding?''. If 'Yes', it goes to 'CAP\_Apply\_Charging\_Report', 'Complete\_all\_FCI\_record', 'Application\_End', and 'Idle'. If 'No', it goes to 'Handle\_ACR', 'Set Tssf to last used time interval and restart Tssf', 'Start Tccd', and then to the merge point. A note near the merge point indicates 'CallActive := TRUE'. A final note indicates 'CallActive := FALSE; 'CallReleasedAtTcpExpiry' present'. + +Figure 4.34-14: Process imcnSSF (sheet 14) + +![State transition diagram for Process imcnSSF. The diagram shows transitions between states based on CAP messages and internal actions. States include Waiting_for_End_Of_User_Interaction, Handle_AC, Handle_ACR, Int_Disconnect_Forward_Connection, Set_Tssf_to_last/default_time_interval_and_restart_Tssf, Waiting_For_End_Of_User_Interaction, Waiting_For_Instructions, CallActive := FALSE, Set_Tssf_to_CAP_Reset_Timer_time_interval_and_restart_Tssf, To_SRF, Relay_the_operation_to_the_SRF, and Set_Tssf_to_last_used_time_interval_and_restart_Tssf. Transitions are triggered by CAP messages like CAP_Apply_Charging, CAP_Disconnect_ForwardConnection, Int_SRF_Released, CAP_Reset_Timer, CAP_Play_Announcement, CAP_Prompt_&Collect_User_Information, and CAP_Cancel_(Invoke_ID).](ba676d18b6a00f27c5bfaec9eeec20be_img.jpg) + +**Process imcnSSF** 15(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` + +stateDiagram-v2 + [*] --> Waiting_for_End_Of_User_Interaction + Waiting_for_End_Of_User_Interaction --> CAP_Apply_Charging + Waiting_for_End_Of_User_Interaction --> CAP_Disconnect_ForwardConnection + Waiting_for_End_Of_User_Interaction --> Int_SRF_Released + Waiting_for_End_Of_User_Interaction --> CAP_Reset_Timer + Waiting_for_End_Of_User_Interaction --> CAP_Play_Announcement + Waiting_for_End_Of_User_Interaction --> CAP_Prompt_&Collect_User_Information + CAP_Apply_Charging --> Handle_AC + CAP_Disconnect_ForwardConnection --> Handle_ACR + Int_SRF_Released --> Handle_ACR + CAP_Reset_Timer --> CallActive := FALSE + CAP_Prompt_&Collect_User_Information --> CAP_Cancel_(Invoke_ID) + CAP_Cancel_(Invoke_ID) --> CAP_Play_Announcement + CAP_Play_Announcement --> To_SRF + CAP_Play_Announcement --> Relay_the_operation_to_the_SRF + Handle_AC --> Set_Tssf_to_last_used_time_interval_and_restart_Tssf + Set_Tssf_to_last_used_time_interval_and_restart_Tssf --> Waiting_For_End_Of_User_Interaction + Handle_ACR --> Int_Disconnect_Forward_Connection + Int_Disconnect_Forward_Connection --> Set_Tssf_to_default_time_interval_and_restart_Tssf + Set_Tssf_to_default_time_interval_and_restart_Tssf --> Waiting_For_Instructions + CallActive := FALSE --> Set_Tssf_to_CAP_Reset_Timer_time_interval_and_restart_Tssf + Set_Tssf_to_CAP_Reset_Timer_time_interval_and_restart_Tssf --> Waiting_for_End_Of_User_Interaction + Relay_the_operation_to_the_SRF --> Set_Tssf_to_last_used_time_interval_and_restart_Tssf + Set_Tssf_to_last_used_time_interval_and_restart_Tssf --> Waiting_for_End_Of_User_Interaction + +``` + +State transition diagram for Process imcnSSF. The diagram shows transitions between states based on CAP messages and internal actions. States include Waiting\_for\_End\_Of\_User\_Interaction, Handle\_AC, Handle\_ACR, Int\_Disconnect\_Forward\_Connection, Set\_Tssf\_to\_last/default\_time\_interval\_and\_restart\_Tssf, Waiting\_For\_End\_Of\_User\_Interaction, Waiting\_For\_Instructions, CallActive := FALSE, Set\_Tssf\_to\_CAP\_Reset\_Timer\_time\_interval\_and\_restart\_Tssf, To\_SRF, Relay\_the\_operation\_to\_the\_SRF, and Set\_Tssf\_to\_last\_used\_time\_interval\_and\_restart\_Tssf. Transitions are triggered by CAP messages like CAP\_Apply\_Charging, CAP\_Disconnect\_ForwardConnection, Int\_SRF\_Released, CAP\_Reset\_Timer, CAP\_Play\_Announcement, CAP\_Prompt\_&Collect\_User\_Information, and CAP\_Cancel\_(Invoke\_ID). + +Figure 4.34-15: Process imcnSSF (sheet 15) + +![State transition diagram for Process imcnSSF. The process starts in 'Waiting for End_Of_User_Interaction'. It receives signals 'CAP_Cancelled_error' and 'CAP_Cancel_Failed_error' from SRF, and 'CAP_Prompt_&Collect_User_Information_Result' and 'CAP_Specialised_Resource_Report' from SRF. It relays these to gsmSCF and returns to the initial state. An internal 'Timer expiry Tssf' leads to 'Abort', 'Int_Disconnect_Forward_Connection', and 'SRF_Release_Pending'. 'Int_SRF_Released' leads to 'Int_Error' and 'Complete_all_FCI_record'. From 'Complete_all_FCI_record', a decision 'Default call handling = continue call?' leads to 'Wait_For_Request' (Yes) or 'Idle' (No). Another decision 'armed TDPs for this CSI?' also leads to 'Idle' (No) or 'Wait_For_Request' (Yes).](a5404b7275b06497eecf9b5883604753_img.jpg) + +### Process imcnSSF + +16(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the process Generic\_SRF; signals to/from the right are to/from the gsmSCF unless otherwise stated. \*/ + +``` +stateDiagram-v2 + [*] --> Waiting_for_End_Of_User_Interaction + state "Waiting for End_Of_User_Interaction" as Waiting_for_End_Of_User_Interaction + Waiting_for_End_Of_User_Interaction --> CAP_Cancelled_error : From SRF + Waiting_for_End_Of_User_Interaction --> CAP_Cancel_Failed_error : From SRF + Waiting_for_End_Of_User_Interaction --> CAP_Prompt_&Collect_User_Information_Result : From SRF + Waiting_for_End_Of_User_Interaction --> CAP_Specialised_Resource_Report : From SRF + CAP_Cancelled_error --> Relay_the_operation_result_error_to_the_gsmSCF + CAP_Cancel_Failed_error --> Relay_the_operation_result_error_to_the_gsmSCF + CAP_Prompt_&Collect_User_Information_Result --> Relay_the_operation_result_error_to_the_gsmSCF + CAP_Specialised_Resource_Report --> Relay_the_operation_result_error_to_the_gsmSCF + Relay_the_operation_result_error_to_the_gsmSCF --> Waiting_for_End_Of_User_Interaction + Waiting_for_End_Of_User_Interaction --> Timer_expiry_Tssf : Internal + Timer_expiry_Tssf --> Abort + Abort --> Int_Disconnect_Forward_Connection + Int_Disconnect_Forward_Connection --> SRF_Release_Pending + SRF_Release_Pending --> Waiting_for_End_Of_User_Interaction + Waiting_for_End_Of_User_Interaction --> Int_SRF_Released + Int_SRF_Released --> Int_Error + Int_Error --> Complete_all_FCI_record + Complete_all_FCI_record --> Default_call_handling_continue_call + Default_call_handling_continue_call --> Wait_For_Request : Yes + Default_call_handling_continue_call --> Idle : No + Default_call_handling_continue_call --> armed_TDPs_for_this_CSI + armed_TDPs_for_this_CSI --> Wait_For_Request : Yes + armed_TDPs_for_this_CSI --> Idle : No +``` + +State transition diagram for Process imcnSSF. The process starts in 'Waiting for End\_Of\_User\_Interaction'. It receives signals 'CAP\_Cancelled\_error' and 'CAP\_Cancel\_Failed\_error' from SRF, and 'CAP\_Prompt\_&Collect\_User\_Information\_Result' and 'CAP\_Specialised\_Resource\_Report' from SRF. It relays these to gsmSCF and returns to the initial state. An internal 'Timer expiry Tssf' leads to 'Abort', 'Int\_Disconnect\_Forward\_Connection', and 'SRF\_Release\_Pending'. 'Int\_SRF\_Released' leads to 'Int\_Error' and 'Complete\_all\_FCI\_record'. From 'Complete\_all\_FCI\_record', a decision 'Default call handling = continue call?' leads to 'Wait\_For\_Request' (Yes) or 'Idle' (No). Another decision 'armed TDPs for this CSI?' also leads to 'Idle' (No) or 'Wait\_For\_Request' (Yes). + +Figure 4.34-16: Process imcnSSF (sheet 16) + +![State transition diagram for Process imcnSSF. It starts at 'Monitoring' and branches based on 'CAP_Cancel_(All)', 'Int_DP_O_Answer', and 'Int_DP_T_Answer'. The diagram includes states like 'Disarm all EDPs', 'Cancel all reports', 'Handle_O_Answer', 'Handle_T_Answer', 'Perform implicit disarming of DPs.', 'CAP_Event_Report_BCSM (Notify & Continue)', 'CAP_Event_Report_BCSM (Interrupted)', 'Disarm this DP. Perform implicit disarming of DPs.', 'Outstanding_Requests := 1', 'Set Tssf to default non user interaction Tssf timer value and restart Tssf', 'Waiting_For_Instructions', 'Application_End', 'Complete_all_FCI_record', 'Int_Continue', 'armed TDPs for this CSI?', 'Wait_For_Request', and 'Idle'. Decision diamonds include 'DP armed for legID', 'DP armed as EDP-R?', 'Any remaining armed EDPs or outstanding report?', and 'armed TDPs for this CSI?'. A note indicates that for DP O/T, disarming is only for the leg where the event was received.](a7450c80e88ad3f6ca1427ad84020998_img.jpg) + +**Process imcnSSF** 17(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` + +stateDiagram-v2 + [*] --> Monitoring + Monitoring --> CAP_Cancel_(All) + Monitoring --> Int_DP_O_Answer + Monitoring --> Int_DP_T_Answer + + CAP_Cancel_(All) --> Disarm_all_EDPs[Disarm all EDPs] + Disarm_all_EDPs --> Cancel_all_reports[Cancel all reports] + Cancel_all_reports --> Perform_implicit_disarming_of_DPs[Perform implicit disarming of DPs.] + + Int_DP_O_Answer --> Handle_O_Answer[Handle_O_Answer] + Int_DP_T_Answer --> Handle_T_Answer[Handle_T_Answer] + + Handle_O_Answer --> DP_armed_for_legID{DP armed for legID} + Handle_T_Answer --> DP_armed_for_legID + + DP_armed_for_legID -- No --> Perform_implicit_disarming_of_DPs + DP_armed_for_legID -- Yes --> DP_armed_as_EDP_R{DP armed as EDP-R?} + + DP_armed_as_EDP_R -- No --> CAP_Event_Report_BCSM_Notify[CAP_Event_Report_BCSM (Notify & Continue)] + CAP_Event_Report_BCSM_Notify --> Disarm_this_DP_implicit[Disarm this DP. Perform implicit disarming of DPs.] + + DP_armed_as_EDP_R -- Yes --> CAP_Event_Report_BCSM_Interrupted[CAP_Event_Report_BCSM (Interrupted)] + CAP_Event_Report_BCSM_Interrupted --> Disarm_this_DP_implicit + + Disarm_this_DP_implicit --> Outstanding_Requests[Outstanding_Requests := 1] + Outstanding_Requests --> Set_Tssf[Set Tssf to default non user interaction Tssf timer value and restart Tssf] + Set_Tssf --> Waiting_For_Instructions[Waiting_For_Instructions] + + Perform_implicit_disarming_of_DPs --> Any_remaining_armed{Any remaining armed EDPs or outstanding report?} + Any_remaining_armed -- Yes --> Int_Continue + Any_remaining_armed -- No --> Application_End + + Int_Continue --> Monitoring + + Application_End --> Complete_all_FCI_record[Complete_all_FCI_record] + Complete_all_FCI_record --> Int_Continue + + Int_Continue --> armed_TDPs{armed TDPs for this CSI?} + armed_TDPs -- Yes --> Wait_For_Request[Wait_For_Request] + armed_TDPs -- No --> Idle + + Note right of Perform_implicit_disarming_of_DPs: For DP O/T Disconnect the DP is only disarmed for the leg for which the event was received. + +``` + +State transition diagram for Process imcnSSF. It starts at 'Monitoring' and branches based on 'CAP\_Cancel\_(All)', 'Int\_DP\_O\_Answer', and 'Int\_DP\_T\_Answer'. The diagram includes states like 'Disarm all EDPs', 'Cancel all reports', 'Handle\_O\_Answer', 'Handle\_T\_Answer', 'Perform implicit disarming of DPs.', 'CAP\_Event\_Report\_BCSM (Notify & Continue)', 'CAP\_Event\_Report\_BCSM (Interrupted)', 'Disarm this DP. Perform implicit disarming of DPs.', 'Outstanding\_Requests := 1', 'Set Tssf to default non user interaction Tssf timer value and restart Tssf', 'Waiting\_For\_Instructions', 'Application\_End', 'Complete\_all\_FCI\_record', 'Int\_Continue', 'armed TDPs for this CSI?', 'Wait\_For\_Request', and 'Idle'. Decision diamonds include 'DP armed for legID', 'DP armed as EDP-R?', 'Any remaining armed EDPs or outstanding report?', and 'armed TDPs for this CSI?'. A note indicates that for DP O/T, disarming is only for the leg where the event was received. + +Figure 4.34-17: Process imcnSSF (sheet 17) + +![Flowchart for Process imcnSSF (sheet 18). The process starts in a Monitoring state. It receives various events (Int_DP_O_No_Answer, Int_DP_T_No_Answer, Int_DP_O_Busy, Int_DP_T_Busy, Int_DP_Route_Select_Failure). A decision 'EDP type?' follows. If 'EDP_N', it sends a CAP_Event_Report_BCSM (Notify & Continue), then Handle_ACR, Stop Delta, and Perform implicit disarming of DPs. If 'EDP_R', it checks if 'Not armed for LegID'. If not armed, it goes to Handle_ACR, Stop Delta, and Handle_CIR leg (leg2). If armed, it sends a CAP_Event_Report_BCSM (Interrupted), Disarm this DP, Perform implicit disarming of DPs, sets Outstanding_Requests := 1, sets Tssf to default non user interaction Tssf timer value and restart Tssf, and goes to Waiting_For_Instructions. Both paths lead to a 'Call Forwarding pending?' decision. If 'No', it goes to Handle_CIR, then Complete_all_FCI_records, Application_End, Int_Continue, and Idle. If 'Yes', it goes to Handle_CIR leg (leg2), then a decision 'Any remaining armed EDPs or outstanding report?'. If 'No', it goes to Complete_FCI_record (leg2), Int_Continue, and Monitoring. If 'Yes', it goes to Complete_FCI_record (leg2), Int_Continue, and Monitoring.](9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg) + +**Process imcnSSF** 18(30) + +*/\* Invocation of imcnSSF in MO, +MT call case. \*/* + +*/\* Signals to/from the left are to/from the IM-SSF; +signals to/from the right are to/from the gsmSCF. \*/* + +Monitoring + +Int\_DP\_O\_No\_Answer, +Int\_DP\_T\_No\_Answer, +Int\_DP\_O\_Busy, +Int\_DP\_T\_Busy, +Int\_DP\_Route\_Select\_Failure + +EDP type? + +EDP\_N + +CAP\_Event\_ +Report\_BCSM +(Notify & Continue) + +Handle\_ACR + +Stop Delta + +Perform implicit +disarming of DPs. + +EDP\_R + +Not armed for LegID + +Handle\_ACR + +Stop Delta + +Handle\_CIR\_ +leg (leg2) + +CAP\_Event\_ +Report\_BCSM +(Interrupted) + +Disarm this DP. +Perform implicit +disarming of DPs. + +Outstanding\_ +Requests := 1 + +Set Tssf to default +non user interaction +Tssf timer value and +restart Tssf + +Waiting\_For\_ +Instructions + +CallActive := +FALSE + +For DP O/T Disconnect the DP +is only disarmed for the leg +for which the event was +received. + +Call Forwarding +pending? + +No + +Handle\_CIR + +Complete\_all\_ +FCI\_records + +Application\_ +End + +Int\_Continue + +Idle + +Yes + +Handle\_CIR\_ +leg (leg2) + +Any remaining armed +EDPs or +outstanding report? + +No / Yes + +Complete\_ +FCI\_record +(leg2) + +Int\_Continue + +Monitoring + +Flowchart for Process imcnSSF (sheet 18). The process starts in a Monitoring state. It receives various events (Int\_DP\_O\_No\_Answer, Int\_DP\_T\_No\_Answer, Int\_DP\_O\_Busy, Int\_DP\_T\_Busy, Int\_DP\_Route\_Select\_Failure). A decision 'EDP type?' follows. If 'EDP\_N', it sends a CAP\_Event\_Report\_BCSM (Notify & Continue), then Handle\_ACR, Stop Delta, and Perform implicit disarming of DPs. If 'EDP\_R', it checks if 'Not armed for LegID'. If not armed, it goes to Handle\_ACR, Stop Delta, and Handle\_CIR leg (leg2). If armed, it sends a CAP\_Event\_Report\_BCSM (Interrupted), Disarm this DP, Perform implicit disarming of DPs, sets Outstanding\_Requests := 1, sets Tssf to default non user interaction Tssf timer value and restart Tssf, and goes to Waiting\_For\_Instructions. Both paths lead to a 'Call Forwarding pending?' decision. If 'No', it goes to Handle\_CIR, then Complete\_all\_FCI\_records, Application\_End, Int\_Continue, and Idle. If 'Yes', it goes to Handle\_CIR leg (leg2), then a decision 'Any remaining armed EDPs or outstanding report?'. If 'No', it goes to Complete\_FCI\_record (leg2), Int\_Continue, and Monitoring. If 'Yes', it goes to Complete\_FCI\_record (leg2), Int\_Continue, and Monitoring. + +Figure 4.34-18: Process imcnSSF (sheet 18) + +![Flowchart for Process imcnSSF. It starts with 'Monitoring'. A horizontal line branches into three paths. The left path: CAP_ReleaseCall -> AC pending (True) -> CAP_Apply_Charging_Report -> Handle_CIR -> Complete_all_FCI_records -> Application_End -> Int_Release_Call -> Idle. The middle path: Handling of CAP_Release_Call (note: only specified in control relationship, gsmSCF shall not send in monitor relationship) -> Int_O_Exception, Int_T_Exception -> AC pending (True) -> CAP_Apply_Charging_Report -> Handle_CIR -> Complete_all_FCI_records -> Abort -> Idle. A decision 'CallActive := FALSE' is shown near the middle path. The right path: CAP_Apply_Charging -> Handle_AC -> Monitoring.](17431d8b59408f09df7552d8bdbaa015_img.jpg) + +### Process imcnSSF + +19(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` +graph TD; Monitoring([Monitoring]) --> CAP_ReleaseCall{{CAP_ReleaseCall}}; Monitoring --> CAP_Apply_Charging{{CAP_Apply_Charging}}; CAP_ReleaseCall --> AC_pending_1{AC pending}; AC_pending_1 -- True --> CAP_Apply_Charging_Report_1{{CAP_Apply_Charging_Report}}; CAP_Apply_Charging_Report_1 --> Handle_CIR_1[Handle_CIR]; Handle_CIR_1 --> Complete_all_FCI_records_1[Complete_all_FCI_records]; Complete_all_FCI_records_1 --> Application_End{{Application_End}}; Application_End --> Int_Release_Call{{Int_Release_Call}}; Int_Release_Call --> Idle_1([Idle]); CAP_Apply_Charging --> Handle_AC[Handle_AC]; Handle_AC --> Monitoring_2([Monitoring]); CAP_ReleaseCall -.-> Note1[Handling of CAP_Release_Call is only specified in a control relationship. The gsmSCF shall not send a CAP_Release_Call in a monitor relationship]; Note1 --> Int_O_Exception[Int_O_Exception, Int_T_Exception]; Int_O_Exception --> AC_pending_2{AC pending}; AC_pending_2 -- True --> CAP_Apply_Charging_Report_2{{CAP_Apply_Charging_Report}}; CAP_Apply_Charging_Report_2 --> Handle_CIR_2[Handle_CIR]; Handle_CIR_2 --> Complete_all_FCI_records_2[Complete_all_FCI_records]; Complete_all_FCI_records_2 --> Abort{{Abort}}; Abort --> Idle_2([Idle]); CallActive[CallActive := FALSE] -.-> Int_O_Exception; +``` + +Flowchart for Process imcnSSF. It starts with 'Monitoring'. A horizontal line branches into three paths. The left path: CAP\_ReleaseCall -> AC pending (True) -> CAP\_Apply\_Charging\_Report -> Handle\_CIR -> Complete\_all\_FCI\_records -> Application\_End -> Int\_Release\_Call -> Idle. The middle path: Handling of CAP\_Release\_Call (note: only specified in control relationship, gsmSCF shall not send in monitor relationship) -> Int\_O\_Exception, Int\_T\_Exception -> AC pending (True) -> CAP\_Apply\_Charging\_Report -> Handle\_CIR -> Complete\_all\_FCI\_records -> Abort -> Idle. A decision 'CallActive := FALSE' is shown near the middle path. The right path: CAP\_Apply\_Charging -> Handle\_AC -> Monitoring. + +Figure 4.34-19: Process imcnSSF (sheet 19) + +![Flowchart for Process imcnSSF. It starts with an initial state leading to 'Waiting_For_Instructions, Waiting_For_End_Of_User_Interaction'. Then a 'CAP_Furnish_Charging_Information' message is received. Next, 'Set Tssf to last used time interval and restart Tssf' is performed. A decision diamond asks 'Non-completed CAMEL logical call record exists for this legID?'. If 'Yes', it goes to 'AppendFree FormatData in FCI?'. If 'No', it goes to 'Create CAMEL logical call record'. From 'AppendFree FormatData in FCI?', three paths emerge: 'Append' leads to 'Append free format data to existing logical call record'; 'Not present, Overwrite' leads to 'Overwrite all CAMEL logical call record data with this FCI data'; and an unlabeled path leads to 'Write FCI data in CAMEL logical call record'. All three paths merge at a junction leading to a final state.](6e9d059430baba0c363e33749f68b107_img.jpg) + +### Process imcnSSF + +20(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the right are to/from the gsmSCF. \*/ + +``` +graph TD; Start([ ]) --> W[Waiting_For_Instructions, Waiting_For_End_Of_User_Interaction]; W --> CAP{CAP_Furnish_Charging_Information}; CAP --> SetTssf[Set Tssf to last used time interval and restart Tssf]; SetTssf --> Decision1{Non-completed CAMEL logical call record exists for this legID?}; Decision1 -- Yes --> Decision2{AppendFree FormatData in FCI?}; Decision1 -- No --> CreateRecord[Create CAMEL logical call record]; Decision2 -- "Append" --> AppendData[Append free format data to existing logical call record]; Decision2 -- "Not present, Overwrite" --> OverwriteData[Overwrite all CAMEL logical call record data with this FCI data]; Decision2 --> WriteFCI[Write FCI data in CAMEL logical call record]; AppendData --> Junction(( )); OverwriteData --> Junction; WriteFCI --> Junction; Junction --> End([ - ]); +``` + +Flowchart for Process imcnSSF. It starts with an initial state leading to 'Waiting\_For\_Instructions, Waiting\_For\_End\_Of\_User\_Interaction'. Then a 'CAP\_Furnish\_Charging\_Information' message is received. Next, 'Set Tssf to last used time interval and restart Tssf' is performed. A decision diamond asks 'Non-completed CAMEL logical call record exists for this legID?'. If 'Yes', it goes to 'AppendFree FormatData in FCI?'. If 'No', it goes to 'Create CAMEL logical call record'. From 'AppendFree FormatData in FCI?', three paths emerge: 'Append' leads to 'Append free format data to existing logical call record'; 'Not present, Overwrite' leads to 'Overwrite all CAMEL logical call record data with this FCI data'; and an unlabeled path leads to 'Write FCI data in CAMEL logical call record'. All three paths merge at a junction leading to a final state. + +Figure 4.34-20: Process imcnSSF (sheet 20) + +![Flowchart for Process imcnSSF. It starts with Monitoring, followed by CAP_Furnish_Charging_Information. A decision diamond asks 'Non-completed CAMEL logical call record exists for this legID?'. If 'No', it goes to 'Create CAMEL logical call record' then 'Write FCI data in CAMEL logical call record'. If 'Yes', it goes to another decision 'AppendFreeFormatData in FCI?'. If 'Yes', it goes to 'Append free format data to existing logical call record'. If 'Not present, Overwrite', it goes to 'Overwrite all CAMEL logical call record data with this FCI data'. All three paths merge and lead to Monitoring.](eabcb2f8b9acedb194571d5bc734b463_img.jpg) + +### Process imcnSSF + +21(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the right are to/from the gsmSCF. \*/ + +``` +graph TD; Monitoring1([Monitoring]) --> CAP[CAP_Furnish_Charging_Information]; CAP --> D1{Non-completed CAMEL logical call record exists for this legID?}; D1 -- No --> Create[Create CAMEL logical call record]; Create --> Write[Write FCI data in CAMEL logical call record]; D1 -- Yes --> D2{AppendFreeFormatData in FCI?}; D2 -- Yes --> Append[Append free format data to existing logical call record]; D2 -- "Not present, Overwrite" --> Overwrite[Overwrite all CAMEL logical call record data with this FCI data]; Append --> Merge(( )); Overwrite --> Merge; Write --> Merge; Merge --> Monitoring2([Monitoring]) +``` + +Flowchart for Process imcnSSF. It starts with Monitoring, followed by CAP\_Furnish\_Charging\_Information. A decision diamond asks 'Non-completed CAMEL logical call record exists for this legID?'. If 'No', it goes to 'Create CAMEL logical call record' then 'Write FCI data in CAMEL logical call record'. If 'Yes', it goes to another decision 'AppendFreeFormatData in FCI?'. If 'Yes', it goes to 'Append free format data to existing logical call record'. If 'Not present, Overwrite', it goes to 'Overwrite all CAMEL logical call record data with this FCI data'. All three paths merge and lead to Monitoring. + +Figure 4.34-21: Process imcnSSF (sheet 21) + +![State transition diagram for Process imcnSSF. It starts at 'Waiting_For_Instructions', receives a 'CAP Call_Information_Request', sets Tssf, stores the request, increments the Outstanding Call Information Report, and returns to 'Waiting_For_Instructions'.](2b00743506f6a3bbd17af764162dc76d_img.jpg) + +### Process imcnSSF 22(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the right are to/from the gsmSCF. \*/ + +``` +stateDiagram-v2 + [*] --> Waiting_For_Instructions + Waiting_For_Instructions --> CAP_Call_Information_Request : CAP Call_Information_Request + CAP_Call_Information_Request --> Set_Tssf : Set Tssf to last used time interval and restart Tssf + Set_Tssf --> store_request : store request + store_request --> Increment_Report : Outstanding Call Information Report := Outstanding Call Information Report + 1 + Increment_Report --> Waiting_For_Instructions +``` + +The diagram illustrates the state transitions for the imcnSSF process. It begins in the 'Waiting\_For\_Instructions' state, which is an initial state. Upon receiving a 'CAP Call\_Information\_Request', the process moves to a state where it 'Set Tssf to last used time interval and restart Tssf'. This is followed by a 'store request' state. From there, it transitions to a state that updates the 'Outstanding Call Information Report' to 'Outstanding Call Information Report + 1'. Finally, it returns to the 'Waiting\_For\_Instructions' state. + +State transition diagram for Process imcnSSF. It starts at 'Waiting\_For\_Instructions', receives a 'CAP Call\_Information\_Request', sets Tssf, stores the request, increments the Outstanding Call Information Report, and returns to 'Waiting\_For\_Instructions'. + +Figure 4.34-22: Process imcnSSF (sheet 22) + +![Flowchart for Process imcnSSF. It starts with a 'Monitoring' block, followed by an 'Int_DP_Analysed_Information' block, then an 'Int_Continue' block, and ends with another 'Monitoring' block.](cc7baa8e5118f4b42c01166637c738ea_img.jpg) + +### Process imcnSSF + +23(30) + +/\* Invocation of imcnSSF in MO, +MT call case. \*/ + +/\* Signals to/from the left are +to/from the IM-SSF. \*/ + +``` +graph TD; A[Monitoring] --> B[Int_DP_Analysed_Information]; B --> C[Int_Continue]; C --> D[Monitoring]; +``` + +Flowchart for Process imcnSSF. It starts with a 'Monitoring' block, followed by an 'Int\_DP\_Analysed\_Information' block, then an 'Int\_Continue' block, and ends with another 'Monitoring' block. + +Figure 4.34-23: Process imcnSSF (sheet 23) + +![Flowchart for Process imcnSSF. It starts with 'Waiting_for_Instructions_for_DS'. A horizontal line branches into five CAP messages: CAP_Furnish_Charging_Information, CAP_Continue_With_Argument, CAP_Continue, CAP_Connect, and CAP_ReleaseCall. The first CAP message leads to 'Set Tssf to last used time interval and restart Tssf', which then leads to a decision diamond. The other four CAP messages each lead to 'Stop Tssf', which then leads to an internal message (Int_Continue_With_Argument, Int_Continue, Int_Connect, or Int_ReleaseCall). All four internal messages converge to 'Application_End', which leads to 'Complete_all_FCI_Records' and finally 'Idle'. The decision diamond from the first path has a 'Yes' path that bypasses record creation and a 'No' path that leads to 'Create CAMEL logical call record', then 'Write FCI data in CAMEL logical call record' and 'Overwrite CAMEL logical call record with FCI data', both leading to 'Waiting_for_Instructions_for_DS'. A note at the bottom left asks 'Non-completed CAMEL logical call record exists for this legID?'.](ef45b00396c293be0b18d32b97118bf4_img.jpg) + +### Process imcnSSF + +24(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` +graph TD; Start([Waiting_for_Instructions_for_DS]) --> CAP_Furnish[CAP_Furnish_Charging_Information]; Start --> CAP_Continue_W[CAP_Continue_With_Argument]; Start --> CAP_Continue[CAP_Continue]; Start --> CAP_Connect[CAP_Connect]; Start --> CAP_Release[CAP_ReleaseCall]; CAP_Furnish --> SetTssf[Set Tssf to last used time interval and restart Tssf]; SetTssf --> Decision{ }; CAP_Continue_W --> StopTssf1[Stop Tssf]; StopTssf1 --> Int_Continue_W[Int_Continue_With_Argument]; CAP_Continue --> StopTssf2[Stop Tssf]; StopTssf2 --> Int_Continue[Int_Continue]; CAP_Connect --> StopTssf3[Stop Tssf]; StopTssf3 --> Int_Connect[Int_Connect]; CAP_Release --> StopTssf4[Stop Tssf]; StopTssf4 --> Int_Release[Int_ReleaseCall]; Int_Continue_W --> AppEnd{Application_End}; Int_Continue --> AppEnd; Int_Connect --> AppEnd; Int_Release --> AppEnd; AppEnd --> CompleteFCI[Complete_all_FCI_Records]; CompleteFCI --> Idle([Idle]); Decision -- Yes --> AppEnd; Decision -- No --> CreateRecord[Create CAMEL logical call record]; CreateRecord --> WriteFCI[Write FCI data in CAMEL logical call record]; WriteFCI --> OverwriteFCI[Overwrite CAMEL logical call record with FCI data]; OverwriteFCI --> WaitingDS2([Waiting_for_Instructions_for_DS]); Note1[Non-completed CAMEL logical call record exists for this legID?]; +``` + +Flowchart for Process imcnSSF. It starts with 'Waiting\_for\_Instructions\_for\_DS'. A horizontal line branches into five CAP messages: CAP\_Furnish\_Charging\_Information, CAP\_Continue\_With\_Argument, CAP\_Continue, CAP\_Connect, and CAP\_ReleaseCall. The first CAP message leads to 'Set Tssf to last used time interval and restart Tssf', which then leads to a decision diamond. The other four CAP messages each lead to 'Stop Tssf', which then leads to an internal message (Int\_Continue\_With\_Argument, Int\_Continue, Int\_Connect, or Int\_ReleaseCall). All four internal messages converge to 'Application\_End', which leads to 'Complete\_all\_FCI\_Records' and finally 'Idle'. The decision diamond from the first path has a 'Yes' path that bypasses record creation and a 'No' path that leads to 'Create CAMEL logical call record', then 'Write FCI data in CAMEL logical call record' and 'Overwrite CAMEL logical call record with FCI data', both leading to 'Waiting\_for\_Instructions\_for\_DS'. A note at the bottom left asks 'Non-completed CAMEL logical call record exists for this legID?'. + +Figure 4.34-24: Process imcnSSF (sheet 24) + +![State transition diagram for Process imcnSSF. The process starts in 'Waiting_for_Instructions_For_DS'. It has two main branches: one for 'Internal' events leading to 'Timer expiry Tssf' and then 'Abort', and another for 'Int_DP_O Abandon' leading to 'Stop Tssf'. Both branches lead to 'Complete_all_FCI_records' and then to 'Idle' state. An 'Int_Error' state is also shown between 'Abort' and 'Complete_all_FCI_records'.](9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg) + +### Process imcnSSF 25(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` +stateDiagram-v2 + [*] --> Waiting_for_Instructions_For_DS + Waiting_for_Instructions_For_DS --> Timer_expiry_Tssf + Waiting_for_Instructions_For_DS --> Int_DP_O_Abandon + Timer_expiry_Tssf --> Abort + Int_DP_O_Abandon --> Stop_Tssf + Abort --> Int_Error + Stop_Tssf --> Complete_all_FCI_records_1 + Int_Error --> Complete_all_FCI_records_2 + Complete_all_FCI_records_1 --> Application_End + Complete_all_FCI_records_2 --> Idle_1 + Application_End --> Idle_2 +``` + +The diagram illustrates the state transitions for the **Process imcnSSF**. It begins in the **Waiting\_for\_Instructions\_For\_DS** state. From here, an **Internal** event leads to **Timer expiry Tssf**, which then leads to **Abort**. **Abort** leads to **Int\_Error**, which then leads to **Complete\_all\_FCI\_records**, which finally leads to the **Idle** state. Alternatively, an **Int\_DP\_O Abandon** event from the **Waiting\_for\_Instructions\_For\_DS** state leads to **Stop Tssf**, which then leads to **Complete\_all\_FCI\_records**, which then leads to **Application\_End**, which finally leads to the **Idle** state. + +State transition diagram for Process imcnSSF. The process starts in 'Waiting\_for\_Instructions\_For\_DS'. It has two main branches: one for 'Internal' events leading to 'Timer expiry Tssf' and then 'Abort', and another for 'Int\_DP\_O Abandon' leading to 'Stop Tssf'. Both branches lead to 'Complete\_all\_FCI\_records' and then to 'Idle' state. An 'Int\_Error' state is also shown between 'Abort' and 'Complete\_all\_FCI\_records'. + +Figure 4.34-25: Process imcnSSF (sheet 25) + +![Flowchart for Process imcnSSF. The process starts with 'Waiting_for_Instructions_For_DS', followed by 'CAP_ConnectToResource', 'Stop Tssf', and 'Connect_To_Resource'. A 'result' decision diamond follows. If 'pass', it goes to 'Set Tssf to user interaction timer value and restart Tssf' and then 'Waiting_For_End_Of_User_Interaction_For_DS'. If 'fail', it goes to 'Set Tssf to last used time interval and restart Tssf', then 'Return appropriate error to the gsmSCF', and finally 'Waiting_For_Instructions_For_DS'.](9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg) + +### Process imcnSSF + +26(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` +graph TD; A[Waiting_for_Instructions_For_DS] --> B[/CAP_ConnectToResource/]; B --> C[Stop Tssf]; C --> D[Connect_To_Resource]; D --> E{result}; E -- pass --> F[Set Tssf to user interaction timer value and restart Tssf]; F --> G[Waiting_For_End_Of_User_Interaction_For_DS]; E -- fail --> H[Set Tssf to last used time interval and restart Tssf]; H --> I[/Return appropriate error to the gsmSCF/]; I --> J[Waiting_For_Instructions_For_DS]; +``` + +Flowchart for Process imcnSSF. The process starts with 'Waiting\_for\_Instructions\_For\_DS', followed by 'CAP\_ConnectToResource', 'Stop Tssf', and 'Connect\_To\_Resource'. A 'result' decision diamond follows. If 'pass', it goes to 'Set Tssf to user interaction timer value and restart Tssf' and then 'Waiting\_For\_End\_Of\_User\_Interaction\_For\_DS'. If 'fail', it goes to 'Set Tssf to last used time interval and restart Tssf', then 'Return appropriate error to the gsmSCF', and finally 'Waiting\_For\_Instructions\_For\_DS'. + +Figure 4.34-26: Process imcnSSF (sheet 26) + +![State transition diagram for Process imcnSSF. The diagram shows a vertical sequence of states and transitions: an initial state (oval) leading to 'Waiting_for_End_Of_User_Interaction_For_DS' (rectangle); a transition 'Int_DP_O_Abandon' (chevron) leading to 'Stop Tssf' (rectangle); a transition 'Complete_all_FCI_records' (double rectangle) leading to 'Application_End' (chevron); and a final transition leading to 'Idle' (oval).](da85343976fdbb19f866d9ddbdad0eae_img.jpg) + +**Process imcnSSF** 27(30) + +``` +/* Invocation of imcnSSF in MO, +MT call case. */ +``` + +``` +/* Signals to/from the left are +to/from the IM-SSF; +signals to/from the right are +to/from the gsmSCF. */ +``` + +``` +stateDiagram-v2 + [*] --> Waiting_for_End_Of_User_Interaction_For_DS + Waiting_for_End_Of_User_Interaction_For_DS --> Int_DP_O_Abandon + Int_DP_O_Abandon --> Stop_Tssf : Stop Tssf + Stop_Tssf --> Complete_all_FCI_records + Complete_all_FCI_records --> Application_End + Application_End --> Idle +``` + +State transition diagram for Process imcnSSF. The diagram shows a vertical sequence of states and transitions: an initial state (oval) leading to 'Waiting\_for\_End\_Of\_User\_Interaction\_For\_DS' (rectangle); a transition 'Int\_DP\_O\_Abandon' (chevron) leading to 'Stop Tssf' (rectangle); a transition 'Complete\_all\_FCI\_records' (double rectangle) leading to 'Application\_End' (chevron); and a final transition leading to 'Idle' (oval). + +Figure 4.34-27: Process imcnSSF (sheet 27) + +![State transition diagram for Process imcnSSF. The diagram shows transitions between states based on CAP and Int_SRF signals. Initial state: Waiting_for_End_Of_User_Interaction_For_DS. Transitions: CAP_Disconnect_ForwardConnection leads to Int_Disconnect_Forward_Connection leading to Set Tssf to default non user interaction time interval and restart Tssf leading to Waiting_For_Instructions_For_DS. Int_SRF_Released leads to Set Tssf to default non user interaction time interval and restart Tssf leading to Waiting_For_Instructions_For_DS. CAP_Reset_Timer leads to Set Tssf to CAP_Reset_Timer time interval and restart Tssf leading to Waiting_for_End_Of_User_Interaction_For_DS. CAP_Play_Announcement leads to CAP_Prompt_&Collect_User_Information leading to Relay the operation to the SRF leading to to SRF. CAP_Cancel_(Invoke_ID) also leads to CAP_Prompt_&Collect_User_Information. CAP_Prompt_&Collect_User_Information also leads to Set Tssf to last used time interval and restart Tssf leading to Waiting_for_End_Of_User_Interaction_For_DS.](c21bad844b5cb6026c067a1f43ce67c3_img.jpg) + +**Process imcnSSF** 28(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` + +stateDiagram-v2 + [*] --> Waiting_for_End_Of_User_Interaction_For_DS + Waiting_for_End_Of_User_Interaction_For_DS --> CAP_Disconnect_ForwardConnection + Waiting_for_End_Of_User_Interaction_For_DS --> Int_SRF_Released + Waiting_for_End_Of_User_Interaction_For_DS --> CAP_Reset_Timer + Waiting_for_End_Of_User_Interaction_For_DS --> CAP_Play_Announcement + Waiting_for_End_Of_User_Interaction_For_DS --> CAP_Prompt_&Collect_User_Information + Waiting_for_End_Of_User_Interaction_For_DS --> CAP_Cancel_(Invoke_ID) + + CAP_Disconnect_ForwardConnection --> Int_Disconnect_Forward_Connection + Int_Disconnect_Forward_Connection --> Set_Tssf_Default_1[Set Tssf to default non user interaction time interval and restart Tssf] + Set_Tssf_Default_1 --> Waiting_For_Instructions_For_DS + + Int_SRF_Released --> Set_Tssf_Default_2[Set Tssf to default non user interaction time interval and restart Tssf] + Set_Tssf_Default_2 --> Waiting_For_Instructions_For_DS + + CAP_Reset_Timer --> Set_Tssf_Reset[Set Tssf to CAP_Reset_Timer time interval and restart Tssf] + Set_Tssf_Reset --> Waiting_for_End_Of_User_Interaction_For_DS + + CAP_Play_Announcement --> CAP_Prompt_&Collect_User_Information + CAP_Cancel_(Invoke_ID) --> CAP_Prompt_&Collect_User_Information + + CAP_Prompt_&Collect_User_Information --> Relay_the_operation_to_the_SRF[Relay the operation to the SRF] + Relay_the_operation_to_the_SRF --> to_SRF[to SRF] + + CAP_Prompt_&Collect_User_Information --> Set_Tssf_Last[Set Tssf to last used time interval and restart Tssf] + Set_Tssf_Last --> Waiting_for_End_Of_User_Interaction_For_DS + +``` + +State transition diagram for Process imcnSSF. The diagram shows transitions between states based on CAP and Int\_SRF signals. Initial state: Waiting\_for\_End\_Of\_User\_Interaction\_For\_DS. Transitions: CAP\_Disconnect\_ForwardConnection leads to Int\_Disconnect\_Forward\_Connection leading to Set Tssf to default non user interaction time interval and restart Tssf leading to Waiting\_For\_Instructions\_For\_DS. Int\_SRF\_Released leads to Set Tssf to default non user interaction time interval and restart Tssf leading to Waiting\_For\_Instructions\_For\_DS. CAP\_Reset\_Timer leads to Set Tssf to CAP\_Reset\_Timer time interval and restart Tssf leading to Waiting\_for\_End\_Of\_User\_Interaction\_For\_DS. CAP\_Play\_Announcement leads to CAP\_Prompt\_&Collect\_User\_Information leading to Relay the operation to the SRF leading to to SRF. CAP\_Cancel\_(Invoke\_ID) also leads to CAP\_Prompt\_&Collect\_User\_Information. CAP\_Prompt\_&Collect\_User\_Information also leads to Set Tssf to last used time interval and restart Tssf leading to Waiting\_for\_End\_Of\_User\_Interaction\_For\_DS. + +Figure 4.34-28: Process imcnSSF (sheet 28) + +![State transition diagram for Process imcnSSF. The diagram shows various states and transitions. States include CAP_Cancelled_error, CAP_Cancel_Failed_error, CAP_Prompt_&Collect_User_Information_Result, CAP_Specialised_Resource_Report, Waiting_for_End_Of_User_Interaction_For_DS, Relay the operation/result/error to the gsmSCF, Abort, Int_Disconnect_Forward_Connection, SRF_Release_Pending_DS, Int_SRF_Released, Int_Error, Complete_all_FCI_record, and Idle. Transitions are labeled with 'from SRF', 'Timer expiry Tssf', and 'Internal'.](b50f38be091844d58b11e3d47bc71e73_img.jpg) + +### Process imcnSSF + +29(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the process Generic\_SRF; signals to/from the right are to/from the imcnSCF unless otherwise stated. \*/ + +``` +stateDiagram-v2 + [*] --> CAP_Cancelled_error + [*] --> CAP_Cancel_Failed_error + [*] --> CAP_Prompt_&Collect_User_Information_Result + [*] --> CAP_Specialised_Resource_Report + [*] --> Waiting_for_End_Of_User_Interaction_For_DS + + CAP_Cancelled_error --> CAP_Cancel_Failed_error + CAP_Cancel_Failed_error --> CAP_Prompt_&Collect_User_Information_Result + CAP_Prompt_&Collect_User_Information_Result --> CAP_Specialised_Resource_Report + CAP_Specialised_Resource_Report --> Waiting_for_End_Of_User_Interaction_For_DS + + CAP_Prompt_&Collect_User_Information_Result --> Relay_the_operation_result_error_to_the_gsmSCF[Relay the operation/result/error to the gsmSCF] + Relay_the_operation_result_error_to_the_gsmSCF --> Waiting_for_End_Of_User_Interaction_For_DS + + CAP_Specialised_Resource_Report --> Abort + Abort --> Int_Disconnect_Forward_Connection + Int_Disconnect_Forward_Connection --> SRF_Release_Pending_DS + SRF_Release_Pending_DS --> Int_SRF_Released + Int_SRF_Released --> Int_Error + Int_Error --> Complete_all_FCI_record + Complete_all_FCI_record --> Idle + + CAP_Prompt_&Collect_User_Information_Result --> from_SRF_1[from SRF] + CAP_Specialised_Resource_Report --> from_SRF_2[from SRF] + from_SRF_1 --> Timer_expiry_Tssf[Timer expiry Tssf] + from_SRF_2 --> Timer_expiry_Tssf + Timer_expiry_Tssf --> Internal[Internal] +``` + +State transition diagram for Process imcnSSF. The diagram shows various states and transitions. States include CAP\_Cancelled\_error, CAP\_Cancel\_Failed\_error, CAP\_Prompt\_&Collect\_User\_Information\_Result, CAP\_Specialised\_Resource\_Report, Waiting\_for\_End\_Of\_User\_Interaction\_For\_DS, Relay the operation/result/error to the gsmSCF, Abort, Int\_Disconnect\_Forward\_Connection, SRF\_Release\_Pending\_DS, Int\_SRF\_Released, Int\_Error, Complete\_all\_FCI\_record, and Idle. Transitions are labeled with 'from SRF', 'Timer expiry Tssf', and 'Internal'. + +Figure 4.34-29: Process imcnSSF (sheet 29) + +![State transition diagram for Process imcnSSF. It starts with an initial state '*' (Idle, Wait_For_Request), followed by a transition 'CAP_CallGap', then a decision 'Int_CallGap' which leads to a new 'imcn_SSME_SSF' process, and finally an end state '-'.](72d448a65347c51989171748789c7d4b_img.jpg) + +### Process imcnSSF + +30(30) + +/\* Invocation of imcnSSF in MO, MT call case. \*/ + +/\* Signals to/from the left are to/from the IM-SSF; signals to/from the right are to/from the gsmSCF. \*/ + +``` +stateDiagram-v2 + [*] --> Idle + state "Idle, Wait_For_Request" as Idle + Idle --> CAP_CallGap : CAP_CallGap + CAP_CallGap --> Int_CallGap : Int_CallGap + state "Int_CallGap" as Int_CallGap + Int_CallGap --> End : to a new imcn_SSME_SSF process + state "-" as End +``` + +State transition diagram for Process imcnSSF. It starts with an initial state '\*' (Idle, Wait\_For\_Request), followed by a transition 'CAP\_CallGap', then a decision 'Int\_CallGap' which leads to a new 'imcn\_SSME\_SSF' process, and finally an end state '-'. + +Figure 4.34-30: Process imcnSSF (sheet 30) + +#### 4.6.1.6 Process imcn\_SSME\_SSF and procedures + +One process is instantiated at the IM-SSF for each Call Gap message received from a gsmSCF. + +This subclause contains the SDL process for IM-SSF handling of the CallGap operation received from a gsmSCF. + +The following Call Gap procedures specified in 3GPP TS 23.078 Rel-99 [4] shall also be applicable for IM-SSF. The IM-SSF shall take the role of the gsmSSF in the following: + +- Procedure Store\_Call\_Gap\_Criteria; +- Procedure Check\_Gap\_Criteria. + +![Flowchart for Process imcn_SSME_SSF. It starts with an oval connector, followed by an 'Idle' state. An arrow points to an 'Int_CallGap' input symbol. A decision diamond asks 'Gap context with same criteria and gsmSCF address (if available) already exists ?'. If 'Yes', it goes to a 'Remove CallGap' process, which then points to a note 'To imcn_SSME_SSF process that handles the old Call Gapping context'. If 'No', it goes to a 'Store_Call_Gap_Criteria' process. Both paths lead to a 'Result = pass?' decision diamond. If 'Yes', it goes to an 'Active' state. If 'No', it goes to an 'Idle' state.](24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg) + +### Process imcn\_SSME\_SSF 1(2) + +IM-SSF handling of SCF requests for Call Gapping. + +/\* Signals to/from the left are to/from the imcnSSF ; signals to/from the right are to/from internal processes \*/ + +/\* Timers used in the imcnSSF process: +Tcgd : Timer for call gapping duration (set with the Gap duration parameter) +Tcgi : Timer for call gapping interval (set with the Gap interval parameter) +\*/ + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> Int_CallGap{Int_CallGap}; Int_CallGap --> Decision1{Gap context with same criteria and gsmSCF address (if available) already exists ?}; Decision1 -- Yes --> RemoveCallGap[/Remove CallGap/]; RemoveCallGap --> Note[To imcn_SSME_SSF process that handles the old Call Gapping context]; Note --> Decision1; Decision1 -- No --> StoreCallGapCriteria[Store_Call_Gap_Criteria]; StoreCallGapCriteria --> Decision2{Result = pass?}; Decision2 -- Yes --> Active([Active]); Decision2 -- No --> Idle2([Idle]); +``` + +Flowchart for Process imcn\_SSME\_SSF. It starts with an oval connector, followed by an 'Idle' state. An arrow points to an 'Int\_CallGap' input symbol. A decision diamond asks 'Gap context with same criteria and gsmSCF address (if available) already exists ?'. If 'Yes', it goes to a 'Remove CallGap' process, which then points to a note 'To imcn\_SSME\_SSF process that handles the old Call Gapping context'. If 'No', it goes to a 'Store\_Call\_Gap\_Criteria' process. Both paths lead to a 'Result = pass?' decision diamond. If 'Yes', it goes to an 'Active' state. If 'No', it goes to an 'Idle' state. + +Figure 4.35-1: Process imcn\_SSME\_SSF (sheet 1) + +![State transition diagram for Process imcn_SSME_SSF. The diagram starts with an 'Active' state. From 'Active', four transitions are possible: 'Tcgi expiry', 'Trigger Tcgi', 'Tcgd expiry', and 'Remove CallGap'. 'Tcgi expiry' leads to 'CG Reject := False', which then leads back to 'Active'. 'Trigger Tcgi' leads to 'Start Tcgi', which leads to 'CG Reject := True', which then leads to 'Idle'. 'Tcgd expiry' leads to 'Clear Call Gapping Context (i.e. remove timers and criteria)', which then leads to 'Idle'. 'Remove CallGap' also leads to 'Clear Call Gapping Context (i.e. remove timers and criteria)'. A note at the bottom right states: 'NOTE: The timer Tcgi is started for the first time after the first call encountering the call gapping criteria is met.'](b13465efdac63129aef9b6f1787d0d00_img.jpg) + +### Process imcn\_SSME\_SSF + +2(2) + +IM-SSF handling of SCF requests for Call Gapping. + +/\* Signals to/from the left are to/from the imcnSSF ; signals to/from the right are to/from internal processes \*/ + +``` +stateDiagram-v2 + [*] --> Active + state "Active" as Active + Active --> Tcgi_expiry : Tcgi expiry + Active --> Trigger_Tcgi : Trigger Tcgi + Active --> Tcgd_expiry : Tcgd expiry + Active --> Remove_CallGap : Remove CallGap + Tcgi_expiry --> CG_Reject_False : CG Reject := False + CG_Reject_False --> Active + Trigger_Tcgi --> Start_Tcgi : Start Tcgi + Start_Tcgi --> CG_Reject_True : CG Reject := True + CG_Reject_True --> Idle + Tcgd_expiry --> Clear_Context : Clear Call Gapping Context (i.e. remove timers and criteria) + Remove_CallGap --> Clear_Context + Clear_Context --> Idle +``` + +NOTE: The timer Tcgi is started for the first time after the first call encountering the call gapping criteria is met. + +State transition diagram for Process imcn\_SSME\_SSF. The diagram starts with an 'Active' state. From 'Active', four transitions are possible: 'Tcgi expiry', 'Trigger Tcgi', 'Tcgd expiry', and 'Remove CallGap'. 'Tcgi expiry' leads to 'CG Reject := False', which then leads back to 'Active'. 'Trigger Tcgi' leads to 'Start Tcgi', which leads to 'CG Reject := True', which then leads to 'Idle'. 'Tcgd expiry' leads to 'Clear Call Gapping Context (i.e. remove timers and criteria)', which then leads to 'Idle'. 'Remove CallGap' also leads to 'Clear Call Gapping Context (i.e. remove timers and criteria)'. A note at the bottom right states: 'NOTE: The timer Tcgi is started for the first time after the first call encountering the call gapping criteria is met.' + +Figure 4.35-2: Process imcn\_SSME\_SSF (sheet 2) + +## 4.7 Descriptions of information Flows + +This clause contains the detailed description of the information flows used by CAMEL for IP Multimedia Subsystems call control. + +Each Information Element (IE) is marked as Mandatory (M), Conditional (C), Specific conditions (S), mutually Exclusive (E), Optional (O) or not applicable (-) for each different traffic case: IP Multimedia Origination (IM\_Orig), IP Multimedia Termination (IM\_Term). The distinction between IM\_Orig and IM\_Term calls is not applicable to all Information Flows. + +An 'M' IE shall always be included for the corresponding traffic case. A 'C' IE shall be included if the sending entity has the necessary information to populate the IE. The conditions for the inclusion of an 'S' IE are shown in the 'Description' column of the definition table. When a set of 'E' IEs is shown in the definition of an Information Flow or compound IE, only one of those IEs may be included. An 'O' IE may be included or omitted as required by the service logic. A '-' IE shall always be omitted for the corresponding traffic case. This categorization is a functional classification, i.e. it defines the requirements for the stage 2 information. It is not a stage 3 classification to be used for the ASN.1 syntax of the protocol. + +Details of errors and exceptions to these rules are specified in 3GPP TS 29.278 [11]. + +### 4.7.1 IM-SSF to gsmSCF information flows + +#### 4.7.1.1 Activity Test ack + +##### 4.7.1.1.1 Description + +This IF is the response to the Activity Test. + +##### 4.7.1.1.2 Information Elements + +This IF contains no information elements. + +#### 4.7.1.2 Apply Charging Report + +##### 4.7.1.2.1 Description + +This IF is used by the IM-SSF to report to the gsmSCF the information requested in the Apply Charging IF. + +##### 4.7.1.2.2 Information Elements + +| Information element name | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------| +| Call Result | M | This IE contains the charging information to be provided by the IM-SSF. | + +Call Result contains the following information: + +| Information element name | Status | Description | +|-------------------------------|--------|----------------------------------------------| +| Time Duration Charging Result | M | This IE is a list defined in the next table. | + +Time Duration Charging Result contains the following information: + +| Information element name | Status | Description | +|-----------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Time Information | M | This IE is a choice between Time if No Tariff Switch and Time if Tariff Switch. This IE is described in the next table. | +| Party To Charge | M | This IE is received in the related ApplyCharging operation to correlate the result to the request. This IE shall be a copy of the corresponding IE received in the Apply Charging operation. | +| Call Active | M | This IE indicates whether the call is active or not. | +| Call Released at Tcp Expiry | C | This element is an indication that the IM-SSF has released the call and terminated the dialogue, due to Tcp expiry.
It shall be present when ACR is sent due to Tcp expiry and the IM-SSF has released the call (because "ReleaseIfExceeded" was present in ACH operation).
In all other circumstances, this element shall be absent. | + +Time Information contains one of the following information: + +| Information element name | Status | Description | +|--------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Time If No Tariff Switch | C | This IE will be present if no tariff switch has occurred since the reception of the first Apply Charging IF for the connection to the Called Party or the MRFC connection, otherwise it will be absent.
If Answer was detected for the connection to the Called Party or the MRFC connection, then the elapsed time since detection of Answer shall be reported.
If answer was not detected, it shall be set to "0". | +| Time If Tariff Switch | C | This IE will be present if a tariff switch has occurred since the reception of the first Apply Charging IF for the connection to the Called Party or the MRFC connection, otherwise it will be absent. | + +#### 4.7.1.3 Call Gap + +##### 4.7.1.3.1 Description + +This IF is used to activate/modify/remove a call gap mechanism in the IM-SSF. The call gap mechanism is used to reduce the rate at which specific service requests are sent to a gsmSCF. + +A Call Gap operation can only be sent on an opened dialogue between a gsmSCF and the IM-SSF. + +It is possible to have several call gapping conditions applicable to the same IM-SSF (i.e. each conditions were activated for a defined Service (identified by the serviceKey) by a defined gsmSCF (identified by the gsmSCFAddress)). + +##### 4.7.1.3.2 Information Elements + +| Information element name | Status | Description | +|--------------------------|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Gap Criteria | M | This IE specifies the criteria for a call to be subject to call gapping. | +| Gap Indicators | M | This parameter indicates the gapping characteristics. | +| Control Type | O | This parameter indicates the reason for activating call gapping.
The value "sCPOverloaded" indicates that an automatic congestion detection and control mechanism in the SCP has detected a congestion situation.
The value "manuallyInitiated" indicates that the service and or network/service management centre has detected a congestion situation, or any other situation that requires manually initiated controls.
The controlType "manuallyInitiated" will have priority over "sCPOverloaded" call gap. | +| Gap Treatment | O | This parameter indicates how calls that were rejected due to the call gapping condition and for which the Default Call Handling was set to "Release Call" shall be treated. | +| M | Mandatory (The IE shall always be sent). | | +| O | Optional (Service logic dependent). | | + +Gap Criteria contains one of the following (Choice): + +| Information element name | Status | Description | +|--------------------------|-------------------------------------|-------------------------------------------------------------| +| Basic Gap Criteria | O | This IE is a choice of various basic criteria. | +| Compound Gap Criteria | O | This IE is a choice of various criteria including an ScfID. | +| O | Optional (Service logic dependent). | | + +Compound Gap Criteria contains the following Information: + +| Information element name | Status | Description | +|--------------------------|------------------------------------------|-----------------------------------------------------------------------------| +| Basic Gap Criteria | M | This IE is a choice of various criteria. | +| ScfID | O | This IE contains the address of the gsmSCF which initiated the CallGapping. | +| M | Mandatory (The IE shall always be sent). | | +| O | Optional (Service logic dependent). | | + +Basic Gap Criteria contains one of the following (Choice): + +| Information element name | Status | Description | +|---------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Called Address | O | This parameter contains a string of digits. At each call attempt, when the leading digits of the dialled number match this specific value, the call gapping treatment shall be applied to this call. | +| Service | O | This parameter contains a service key value. At each call attempt, when the service key matches this specific value, the call gapping treatment shall be applied to this call. | +| Called Address and Service | O | This parameter contains a specific string of digits and a service key value. At each call attempt, when the leading digits of the dialled number and the service key of a call match these specific values, the call gapping treatment shall be applied to this call. | +| Calling Address and Service | O | This parameter contains a specific string of digits and a service key value. At each call attempt, when the leading digits of the calling party number and the service key match these specific values, the call gapping treatment shall be applied to this call. | +| O Optional (Service logic dependent). | | | + +Gap Indicators contains the following information: + +| Information element name | Status | Description | +|--------------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Duration | M | Duration specifies the total time interval during which call gapping for the specified gap criteria will be active.
A duration of 0 indicates that gapping is to be removed.
A duration of -2 indicates a network specific duration.
Other values indicate duration in seconds. | +| Interval | M | This parameter specifies the minimum time between calls being allowed through.
An interval of 0 indicates that calls meeting the gap criteria are not to be rejected.
An interval of -1 indicates that all calls meeting the gap criteria are to be rejected.
Other values indicate interval in milliseconds. | +| M Mandatory (The IE shall always be sent). | | | + +Gap Treatment contains one of the following (choice): + +| Information element name | Status | Description | +|---------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| Information To Send | O | This parameter indicates an announcement or a tone to be sent to the calling party. At the end of information sending, the call shall be released. | +| Release Cause | O | If the call is to be released, this IE indicates a specific cause value to be sent in the release message. See ETSI EN 300 356-1 [20] for the coding. | +| O Optional (Service logic dependent). | | | + +Information To Send contains one of the following (choice): + +| Information element name | Status | Description | +|---------------------------------------|--------|--------------------------------------------------------------| +| In-band Info | O | This parameter specifies the in-band information to be sent. | +| Tone | O | This parameter specifies a tone to be sent to the end-user. | +| O Optional (Service logic dependent). | | | + +In-band Info contains the following information: + +| Information element name | Status | Description | +|--------------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------| +| Message Id | M | This parameter indicates the message(s) to be sent, it can be one of the following. | +| Message Duration | O | This parameter indicates the maximum time duration in seconds that the message shall be played/repeated. ZERO indicates endless repetition. | +| M Mandatory (The IE shall always be sent). | | | +| O Optional (Service logic dependent). | | | + +Message Id contains one of the following (choice): + +| Information element name | Status | Description | +|--------------------------|-------------------------------------|-------------------------------------------------| +| Elementary Message Id | O | This parameter indicates a single announcement. | +| O | Optional (Service logic dependent). | | + +#### 4.7.1.4 Call Information Report + +##### 4.7.1.4.1 Description + +This IF is used to send specific call information for a single call to the gsmSCF as requested from the gsmSCF in a previous Call Information Request. + +##### 4.7.1.4.2 Information Elements + +| Information element name | Status | Description | +|----------------------------|--------|-----------------------------------------------------------------------------------| +| Requested Information List | M | This IE specifies a list of Requested information Values which are requested. | +| Leg ID | M | This IE indicates the party in the call for which information shall be collected. | + +#### 4.7.1.5 Event Report BCSM + +##### 4.7.1.5.1 Description + +This IF is used to notify the gsmSCF of a call-related event (i.e. BCSM events as answer and disconnect) previously requested by the gsmSCF in a Request Report BCSM Event IF. + +##### 4.7.1.5.2 Information Elements + +| Information element name | Status | Description | +|---------------------------------|--------|--------------------------------------------------------------------------| +| Event type BCSM | M | This IE specifies the type of event that is reported. | +| Event Specific Information BCSM | C | This IE indicates the call related information specific to the event. | +| Leg ID | M | This IE indicates the party in the call for which the event is reported. | +| Misc Call Info | M | This IE indicates the DP type. | + +If the Event Type BCSM IE contains either O\_Answer or T\_Answer, then the Event Specific Information BCSM IE contains the following information elements: + +| Information element name | Status | Description | +|--------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Destination address | M | This IE specifies the destination address for the call leg.
The NatureOfAddress indicator may contain a national-specific value. For some national-specific NatureOfAddress indicator values the length of the digit part of destination address may be zero. | + +If the Event Type BCSM IE contains one of Route\_Select\_Failure, O\_Called\_Party\_Busy, O\_Disconnect, T\_Busy, or T\_Disconnect, then the Event Specific Information BCSM IE contains the following information element: + +| Information element name | Status | Description | +|--------------------------|--------|------------------------------| +| Cause | C | This IE indicates the cause. | + +If the Event Type BCSM IE contains O\_No\_Answer then the Event Specific Information BCSM IE is not included. + +#### 4.7.1.6 Initial DP + +##### 4.7.1.6.1 Description + +This IF is generated by the IM-SSF when a trigger is detected at a DP in the BCSM, to request instructions from the gsmSCF. + +#### **4.7.1.6.2 Information Elements** + +| Information element name | IM_Orig | IM_Term | Description | +|--------------------------|---------|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Media Type Info List | M | M | This IE indicates the media types associated with the SIP call session. This IE shall contain the media description(s) received from the S-CSCF. | +| Called Party Number | C | C |

This IE contains the ISDN number used to identify the called party in the forward direction.

The ISDN called party number is received from the gsmSCF due to the previous CAMEL processing or is derived from the SIP URL received from the S-CSCF for the destination address.

For all IM terminating call scenarios, at least one of the following IEs shall be present:

  • - CalledPartyNumber
  • - CalledPartyURL
| +| Called Party URL | C | C |

This IE contains the SIP URL used to identify the called party in the forward direction.

For all IM terminating call scenarios, at least one of the following IEs shall be present:

  • - CalledPartyNumber
  • - CalledPartyURL
| +| Calling Party Number | C | C |

This IE carries the ISDN calling party number to identify the calling party or the origin of the call.

For all IM originating call scenarios, at least one of the following IEs shall be present:

  • - CallingPartyNumber
  • - CallingPartyURL
| +| Calling Party URL | C | C |

This IE contains the SIP URL used to identify the calling party or the origin of the call.

For all IM originating call scenarios, at least one of the following IEs shall be present:

  • - CallingPartyNumber
  • - CallingPartyURL
| +| Calling Party Category | C | C | Indicates the type of calling party (e.g., operator, pay phone, ordinary subscriber). | +| CallGap Encountered | C | C |

This parameter indicates the type of gapping the related call has been subjected to.

This parameter shall be present only if a call gapping context is applicable to the initialDP operation.

| +| SIP Call ID | M | M |

This IE represents a globally unique identifier for the SIP call. This IE may be used by the gsmSCF for inclusion in a network optional gsmSCF call record.

This IE is received from the SIP request message from S-CSCF.

| +| Cause | C | C |

This IE indicates the cause specific to the armed BCSM DP event. This IE is applicable to DP Route_Select_Failure and DP T_Busy. The cause may be used by the SCF to decide about the further handling of the call.

For IM Termination for an unregistered subscriber, the Cause IE shall be set to indicate Subscriber Absent.

| +| Event Type BCSM | M | M |

This IE indicates the armed BCSM DP event, resulting in the Initial DP IF.

This IE shall be set to indicate DP T_Busy if a not reachable event is detected (e.g. IM termination to a subscriber not currently registered).

| + +| Information element name | IM_Orig | IM_Term | Description | +|---------------------------|---------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | M | M | This IE identifies the mobile subscriber.

This IE shall contain the IMSI value received from the S-CSCF during notification of a SIP registration. | +| IP SSP Capabilities | C | C | This IE indicates which MRFC resources are supported within the IM-SSF and are available. If this IE is absent, this indicates that no MRFC is attached and available. | +| IM-SSF Address | M | M | This IE represents the E.164 address of the IM-SSF from which the InitialDP operation is sent from. | +| Original Called Party ID | C | C | This contains the ISDN number used to identify the original destination number if the call has been forwarded on route to the IM-SSF or is forwarded by the gsmSCF due to the previous CAMEL processing. | +| Original Called Party URL | C | C | This IE contains the SIP URL identifying the original destination number if the call has been forwarded on route to the IM—SSF or is forwarded by the gsmSCF due to the previous CAMEL processing. | +| Redirecting Party ID | C | C | This IE indicates the ISDN number identifying the directory number the call was redirected from. This IE shall also be sent if it was received from the gsmSCF due to the previous CAMEL processing. | +| Redirecting Party URL | C | C | This IE indicates the SIP URL identifying the directory number the call was redirected from. This IE shall also be sent if it was received from the gsmSCF due to the previous CAMEL processing. | +| Redirection Information | C | C | This IE contains forwarding related information, such as redirection reason. This IE shall also be sent if it was received from the gsmSCF due to the previous CAMEL processing. | +| Service Key | M | M | This IE indicates to the gsmSCF the requested CAMEL Service. It is used to address the required application/SLP within the gsmSCF. | +| Subscriber State | - | C | This IE indicates the status of the IMS Subscriber. The states are:
- CAMELBusy: The IMS subscriber is engaged on a transaction for an originating or terminating IM call session.
- NetworkDeterminedNotReachable: The network can determine from its internal data that the IMS subscriber is not reachable.
- AssumedIdle: The state of the IMS subscriber is neither "CAMELBusy" nor "NetworkDeterminedNotReachable". | +| Time And Timezone | M | M | This IE contains the time that the IM-SSF was triggered, and the time zone the IM-SSF resides in. | + +#### 4.7.1.7 Specialized Resource Report + +##### 4.7.1.7.1 Description + +This IF is used to response to a PlayAnnouncement IF when the announcement complete indication is set. + +##### 4.7.1.7.2 Information Elements + +This IF contains no information elements. + +## 4.7.2 gsmSCF to IM-SSF information flows + +### 4.7.2.1 Activity Test + +#### 4.7.2.1.1 Description + +This IF is used to check for the continued existence of a relationship between the gsmSCF and IM-SSF. If the relationship is still in existence, then the IM-SSF will respond. If no reply is received, then the gsmSCF will assume that the IM-SSF has failed in some way and will take the appropriate action. + +#### 4.7.2.1.2 Information Elements + +This IF contains no information elements. + +### 4.7.2.2 Apply Charging + +#### 4.7.2.2.1 Description + +This IF is used for interacting from the gsmSCF with the IM-SSF charging mechanisms to control the call duration. + +#### 4.7.2.2.2 Information Elements + +| Information element name | Status | Description | +|--------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ACh Billing Charging Characteristics | M | This IE specifies the charging related information to be provided by the IM-SSF and the conditions on which this information has to be provided back to the gsmSCF. | +| Party To Charge | M | This IE shall be reflected in the corresponding IE of the Apply Charging Report operation. This IE has no effect on the charging procedures in the MSC. | + +ACh Billing Charging Characteristics contains the following information: + +| Information element name | Status | Description | +|--------------------------|--------|-----------------------------------------| +| Time Duration Charging | M | This IE is described in the next table. | + +Time Duration Charging contains the following information: + +| Information element name | Status | Description | +|------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Max Call Period Duration | M | This IE indicates the maximum call period duration timer. | +| Tariff Switch Interval | O | This IE indicates the tariff switch time until the next tariff switch applies. | +| Release If Duration Exceeded | O | This IE indicates that the call shall be released when the Max call Period Duration expires, with a warning tone if the Play Tone IE is present. The cause used in the release message shall be "normal unspecified".
Default is to continue the call. | +| Play Tone | O | This IE is set if a tone has to be played to the party for whom the BCSM is operating. If present, this IE indicates that 30 seconds before the Max Call Period Duration timer expires, a triple tone of 900 Hz (200 milliseconds tone, 200 milliseconds pause) shall be played. | + +### 4.7.2.3 Call Information Request + +#### 4.7.2.3.1 Description + +This IF is used to request the IM-SSF to record specific information about a single call and report it to the gsmSCF (with a CallInformationReport). + +#### 4.7.2.3.2 Information Elements + +| Information element name | Status | Description | +|---------------------------------|--------|-----------------------------------------------------------------------------------| +| Requested Information Type List | M | This IE specifies a list of specific items of information which are requested. | +| Leg ID | M | This IE indicates the party in the call for which information shall be collected. | + +Requested Information Type List contains the following information: + +| Information element name | Status | Description | +|-----------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Call Attempt Elapsed Time | O | This IE indicates that the Call Attempt Elapsed Time is requested in the Call Information Report.
Call Attempt Elapsed Time is the duration between the end of the CAMEL processing initiating call setup (Connect, Continue or Continue With Argument IF) and the received answer indication from the called party side.
For the Calling Party, the value of Call Attempt Elapsed Time in the Call Information Report shall be set to 0. | +| Call Stop Time | O | This IE indicates that the Call Stop Time is requested in the Call Information Report.
Call Stop Time is the time stamp when the connection is released. | +| Call Connected Elapsed Time | O | This IE indicates that the Call Connected Elapsed Time is requested in the Call Information Report.
Call Connected Elapsed Time is the duration between the received answer indication from the called party side and the release of the connection.
For a Calling Party, it indicates the duration between the sending of IDP and the release of that party | +| Release Cause | O | This IE indicates that the Release Cause is requested in the Call Information Report.
Release Cause is the release cause for the call. | + +#### 4.7.2.4 Cancel + +##### 4.7.2.4.1 Description + +This IF is used by the gsmSCF to request the IM-SSF to cancel all EDPs and reports. + +##### 4.7.2.4.2 Information Elements + +| Information element name | Status | Description | +|--------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------| +| All Requests | M | This IE indicates that all active requests for EventReportBCSM, ApplyChargingReport and CallInformationReport shall be cancelled. | + +#### 4.7.2.5 Connect + +##### 4.7.2.5.1 Description + +This IF is used to request the IM-SSF to perform the call processing actions to route a call to a specific destination. To do so, the IM-SSF may use destination information from the calling party and existing call set-up information depending on the information provided by the gsmSCF. + +#### 4.7.2.5.2 Information Elements + +| Information element name | Status | Description | +|---------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Calling Party Category | O | This IE indicates the type of calling party (e.g., operator, pay phone, ordinary subscriber). | +| Destination Routing Address | E1 | This IE contains the called party number towards which the call is to be routed using an ISDN value. | +| Destination Routing Address URL | E1 | This IE contains the called party number towards which the call is to be routed using a SIP URL. | +| Original Called Party ID | O,E2 | This contains the original destination number if the call has been forwarded on route to the IM-SSF or is forwarded by the gsmSCF.

This IE shall use an ISDN value to identify the original destination number. | +| Original Called Party URL | O,E2 | This contains the original destination number if the call has been forwarded on route to the IM-SSF or is forwarded by the gsmSCF.

This IE shall use a SIP URL to identify the original destination number. | +| Redirecting Party ID | O,E3 | This IE indicates the directory number the call was redirected from. This IE shall use an ISDN value to identify the redirecting party. | +| Redirecting Party URL | O,E3 | This IE indicates the directory number the call was redirected from. This IE shall use a SIP URL to identify the redirecting party. | + +#### 4.7.2.6 Connect To Resource + +##### 4.7.2.6.1 Description + +This IF is used to connect a call from the IM-SSF to MRFC via S-CSCF. + +##### 4.7.2.6.2 Information Elements + +This IF requires no information elements for IMS. + +#### 4.7.2.7 Continue + +##### 4.7.2.7.1 Description + +This IF requests the IM-SSF to proceed with call processing at the DP at which it previously suspended call processing to await gsmSCF instructions. The IM-SSF completes DP processing, and continues basic call processing (i.e. proceeds to the next point in call in the BCSM) without substituting new data from the gsmSCF. + +##### 4.7.2.7.2 Information Elements + +This IF contains no information elements. + +#### 4.7.2.8 Continue With Argument + +##### 4.7.2.8.1 Description + +This information flow requests the IM-SSF to proceed the call processing with modified information at the DP at which it previously suspended call processing to await gsmSCF instructions. The IM-SSF completes DP processing, and continues basic call processing (i.e. proceeds to the next point in call in the BCSM) with the modified call setup information as received from the gsmSCF. + +##### 4.7.2.8.2 Information Elements + +| Information element name | Status | Description | +|--------------------------|--------|-----------------------------------------------------------------------------------------------| +| Calling Party Category | O | This IE indicates the type of calling party (e.g., operator, pay phone, ordinary subscriber). | + +#### 4.7.2.9 Disconnect Forward Connection + +##### 4.7.2.9.1 Description + +This IF is used to disconnect a connection with a MRFC previously established with a Connect To Resource IF. + +##### 4.7.2.9.2 Information Elements + +This IF contains no information elements. + +#### 4.7.2.10 Furnish Charging Information + +##### 4.7.2.10.1 Description + +This IF is used to request the IM-SSF to include call related information in the CAMEL specific logical call record. The logical call record is created when FCI is received and a logical call record for that leg does not exist. For modelling purposes the logical call record is buffered in the IM-SSF. The IM-SSF completes logical call records as defined in the SDLs. Once the logical call record is completed, then its free format data is moved to the corresponding CDR and the logical call record is deleted. + +The CSE can send multiple concatenated FCIs per leg for completion. The total maximum of free format data is 160 octets per leg. The 160 octets may be sent in one or more FCI operations. If there is non-completed free format data and new FCI operation(s) is/are received to overwrite the non-completed data, then the non-completed data is discarded and the gsmSCF can send another 160 octets per leg. The SDLs of 3GPP TS 23.078 Rel-99 [4] define when Logical CDRs are completed. After the completion the gsmSCF can send another 160 octets of free format data in one or more FCI operations for the called leg. + +##### 4.7.2.10.2 Information Elements + +| Information element name | Status | Description | +|--------------------------------------|--------|-----------------------------------------| +| FCI Billing Charging Characteristics | M | This IE is described in the next table. | + +FCI Billing Charging Characteristics contains the following information: + +| Information element name | Status | Description | +|--------------------------|--------|-----------------------------------------| +| FCIBCCCAMEL Sequence 1 | M | This IE is described in the next table. | + +FCIBCCCAMEL Sequence 1 contains the following information: + +| Information element name | Status | Description | +|--------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Free Format Data | M | This IE is a free format data to be inserted in the CAMEL logical call record. | +| Party To Charge | M | This IE indicates the party for whom a CAMEL logical call record will be created. | +| Append Free Format Data | O | This IE indicates that the IM-SSF shall append the free format data to the Logical call record.
  • - If this IE is present and indicates "Append", the IM-SSF shall append the free format data received in this IF to the free format data already present in the Logical call record for that leg of the call.
  • - If this IE is absent or in value "Overwrite", then the IM-SSF shall overwrite all free format data already present in the Logical call record for that leg of the call, by the free format data received in this IF. If no Logical call record exists yet for that leg of the call, then the IM-SSF shall ignore this IE.
| + +#### 4.7.2.11 Release Call + +##### 4.7.2.11.1 Description + +This IF is used to tear down by the gsmSCF an existing call at any phase of the call for all parties involved in the call. + +#### 4.7.2.11.2 Information Elements + +The following information elements are required: + +| Information element name | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Release Cause | M | A number giving an indication to the IM-SSF about the reason of releasing this specific call. This may be used by MSC/GMSC for generating specific tones to the different parties in the call or to fill in the "cause" in the release message. | + +#### 4.7.2.12 Request Report BCSM Event + +##### 4.7.2.12.1 Description + +This IF is used to request the IM-SSF to monitor for a call-related event, then send a notification back to the gsmSCF when the event is detected (see Event Report BCSM). + +##### 4.7.2.12.2 Information Elements + +| Information element name | Status | Description | +|--------------------------|--------|-----------------------------------------------------------------------| +| BCSM Event | M | This IE specifies the event or events of which a report is requested. | + +BCSM Event contains the following information: + +| Information element name | Status | Description | +|--------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Event type | M | This IE specifies the type of event of which a report is requested. | +| Leg ID | C | This IE indicates the party in the call for which the event shall be reported. | +| Monitor Mode | M | When this IE is "interrupted", the event shall be reported as a request, if it is "notifyAndContinue", the event shall be reported as a notification, if the IE is "transparent", the event shall not be reported. | +| DP Specific Criteria | O | This IE is described in the next table. | + +DP Specific Criteria is defined as: + +| Information element name | Status | Description | +|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Application Timer | O | This IE carries additional timer duration information (timer values for No Answer event) required for arming No_Answer EDPs in the IM-SSF. The TNRY timer (value defined between 10 s and 40 s) shall be shorter than the network no answer timer. | +| NOTE | If a Request Report BCSM Event information flow overwrites previous Request Report BCSM Event information flow which contained Application Timer IE for No_Answer DP, the behaviour of the IM-SSF is unpredictable. | | + +#### 4.7.2.13 Reset Timer + +##### 4.7.2.13.1 Description + +This IF is used to refresh a timer. + +#### 4.7.2.13.2 Information Elements + +| Information element name | Status | Description | +|--------------------------|--------|--------------------------------------------------------------------------| +| Timer Value | M | This IE specifies the value to which the indicated timer shall be set. | +| Timer ID | O | This IE indicates which timer shall be reset. It shall be set to "Tssf". | + +### 4.7.3 gsmSCF – IM-SSF information flows for MRFC related operations + +In an IMS Core Network, the Multimedia Resource Function Controller (MRFC) is used for providing specialised resource functions like playing announcements and tones. Requests from the gsmSCF that requires a specialised resource function are sent to the MRFC via the IM-SSF and S-CSCF using SIP signalling as specified in the functional requirements of the MRFC found in 3GPP TS 23.218 [5]. + +This subclause contains the information flows descriptions between the gsmSCF and the IM-SSF for MRFC-related operations. + +#### 4.7.3.1 Cancel + +##### 4.7.3.1.1 Description + +This IF is used by the gsmSCF to request the IM-SSF to cancel a correlated previous operation in the MRFC. + +##### 4.7.3.1.2 Information Elements + +The following information elements are used: + +| Information element name | Status | Description | +|--------------------------|--------|--------------------------------------------------| +| Invoke ID | M | This IE specifies the operation to be cancelled. | + +#### 4.7.3.2 Play Announcement + +##### 4.7.3.2.1 Description + +This IF is sent from the gsmSCF to the IM-SSF and is used to specify information for playing announcements or tones in the MRFC. + +##### 4.7.3.2.2 Information Elements + +The following information elements are required: + +| Information element name | Status | Description | +|-------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------| +| Information To Send | M | This IE indicates an announcement or a tone to be sent to the end user by the MRFC. | +| Disconnect From IP Forbidden | M | This IE indicates whether or not the MRFC may be disconnected from the user when all information has been sent. | +| Request Announcement Complete | M | This IE indicates whether or not a SpecializedResourceReport shall be sent to the gsmSCF when all information has been sent. | + +Information To Send contains the following information: + +| Information element name | Status | Description | +|--------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Inband Info | C | This IE indicates the inband information to be sent. | +| Tone | C | This IE indicates the tone to be sent. The mapping from the code points of this IE to tones is a matter for agreement between the gsmSCF operator and the MRFC operator. | + +Inband Info contains the following information: + +| Information element name | Status | Description | +|--------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------| +| Message ID | M | This IE is described in the next table. | +| Number Of Repetitions | M | This IE indicates the maximum number of times the message shall be sent to the end-user. | +| Duration | O | This IE indicates the maximum duration time in seconds that the message shall be played/repeated. Zero indicates endless repetition. | +| Interval | O | This IE indicates the time interval in seconds between two repetitions. | + +Message ID contains the following information: + +| Information element name | Status | Description | +|--------------------------|--------|----------------------------------------------------------------------------------------------------------------| +| Elementary Message ID | C | This IE indicates a single announcement | +| Text | C | This IE indicates a text to be sent. The text shall be transformed to inband information (speech) by the MRFC. | +| Elementary Message IDs | C | This IE indicates a sequence of announcements | +| Variable Message | C | This IE indicates an announcement with one or more variable parts. | + +Tone contains the following information: + +| Information element name | Status | Description | +|--------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------| +| Tone ID | M | This IE indicates the tone to be sent. | +| Duration | O | This IE indicates the maximum duration time in seconds that the message shall be played/repeated. Zero indicates endless repetition. | + +#### 4.7.3.3 Prompt And Collect User Information (received information) + +##### 4.7.3.3.1 Description + +This IF is sent from the gsmSCF to the IM-SSF and is used to interact with a call party in order to collect information. + +##### 4.7.3.3.2 Information Elements + +The following information elements are required: + +| Information element name | Status | Description | +|------------------------------|--------|----------------------------------------------------------------------------------------------------------| +| Collected Info | M | This IE is described in the next table. | +| Information To Send | O | This IE indicates an announcement or a tone to be sent to the end user by the MRFC. | +| Disconnect From IP Forbidden | M | This IE indicates whether the MRFC may be disconnected from the user when all information has been sent. | + +Collected Info contains the following information: + +| Information element name | Status | Description | +|--------------------------|--------|-----------------------------------------| +| Collected Digits | M | This IE is described in the next table. | + +Collected Digits contains the following information: + +| Information element name | Status | Description | +|--------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Minimum Number Of Digits | M | This IE indicates the minimum number of valid digits to be collected. | +| Maximum Number Of Digits | M | This IE specifies the maximum number of valid digits to be collected | +| End Of Reply Digit | O | This IE indicates the digit(s) used to signal the end of input. | +| Cancel Digit | O | If this IE is present, the cancel digit can be entered by the user to request a possible retry | +| Start Digit | O | If this IE is present, the start digit(s) indicates the start of the valid digits to be collected. | +| First Digit Time Out | O | If this IE is present, the first digit shall be received before the expiration of the first digit timer expiration | +| Inter Digit Time Out | O | If this IE is present, any subsequent valid or invalid digit shall be received by the MRFC before the inter digit timer expires. | +| Error Treatment | O | This IE indicates what specific action shall be taken by the MRFC in the event of error conditions occurring. | +| Interruptable Ann Ind | O | If this IE is set to TRUE (default value) the announcement is interrupted after the first valid or invalid digit received by the MRFC. If this IE is present and explicitly set to FALSE, the announcement will not be interrupted after the first digit is received by the MRFC | +| Voice Information | O | This IE is optional, where the default value is specified being FALSE. If the VoiceInformation IE is set to FALSE, all valid or invalid digits are entered by DTMF If this IE is present and explicitly set to TRUE, calling user is required to provide all valid or invalid information by speech | +| Voice Back | O | This IE is optional, where the default value is specified being FALSE. If the VoiceBack IE is set to FALSE, no voice back information is given by the MRFC If this IE is present and explicitly set to TRUE, the valid input digits received by the MRFC will be announced back to the calling user immediately after the end of input is received | + +InformationToSend is defined in subclause 4.7.3.2.2. + +#### 4.7.3.4 Prompt And Collect User Information ack (received information) + +##### 4.7.3.4.1 Description + +This IF is used by the IM-SSF to indicate the result a Prompt And Collect User Information IF to the gsmSCF. + +##### 4.7.3.4.2 Information Elements + +The following information elements are required: + +| Information element name | Status | Description | +|--------------------------|--------|-----------------------------------------------------------------| +| Digits Response | C | This IE indicates the digit sequence received from the end user | + +#### 4.7.3.5 Specialized Resource Report + +##### 4.7.3.5.1 Description + +This IF is used by the IM-SSF to response to a PlayAnnouncement IF when the announcement complete indication is set. + +#### 4.7.3.5.2 Information Elements + +This IF contains no information elements. + +### 4.7.4 IM-SSF to HSS information flows + +#### 4.7.4.1 Any Time Subscription Interrogation request + +##### 4.7.4.1.1 Description + +This IF is used by the IM-SSF to request subscription information from the HSS. For example, the IM-SSF shall send this as a result of receiving a third party SIP registration from the S-CSCF (over the ISC interface). The IM-SSF shall also send the MAP ATSI request when a SIP INVITE message on a MT session for an unregistered subscriber is received. + +##### 4.7.4.1.2 Information Elements + +| Information element name | Status | Description | +|--------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| gsmSCF Address | M | This IE shall indicate the address of the interrogating IM-SSF. The address shall be in international E.164 format. | +| Requested Info | M | This IE indicates the type of subscriber information being requested. This shall consist of the CAMEL Subscription Information; the CAMEL Subscription Information is described in a table below. | +| Subscriber Identity | M | This IE identifies the subscriber for which the information is requested. The identity shall be an IMSI. | + +CAMEL subscription information contains the following information elements: + +| Information element name | Status | Description | +|----------------------------------------------|--------|-------------------------------------------------------------------------| +| Additional Requested CAMEL Subscription Info | M | This IE shall contain one of the following: O-IM-CSI/VT-IM-CSI/D-IM-CSI | + +#### 4.7.4.2 Notify Subscriber Data Change ack + +##### 4.7.4.2.1 Description + +This IF is used to respond to the HSS's notification of the change of subscriber data. + +##### 4.7.4.2.2 Information Elements + +This IF contains no information elements. + +### 4.7.5 HSS to IM-SSF information flows + +#### 4.7.5.1 Any Time Subscription Interrogation ack + +##### 4.7.5.1.1 Description + +This IF is used by the HSS to provide the requested subscriber's IM-CSI data to the IM-SSF. + +##### 4.7.5.1.2 Information Elements + +| Information element name | Status | Description | +|--------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| CAMEL Subscription Information | C | This IE shall be present if the subscriber is provisioned with a CAMEL Subscription Information for IM CN. This IE is described in a table below. | + +CAMEL Subscription Information contains the following information elements: + +| Information element name | Status | Description | +|--------------------------|--------|-----------------------| +| O-IM-CSI | C | See subclause 4.4.1.1 | +| D-IM-CSI | C | See subclause 4.4.1.2 | +| VT-IM-CSI | C | See subclause 4.4.1.3 | + +#### 4.7.5.2 Notify Subscriber Data Change + +##### 4.7.5.2.1 Description + +This IF is used by the HSS to notify to the IM-SSF of the change of subscriber IM CSI data. This IF is sent at each time subscriber IM CSI data is changed. + +##### 4.7.5.2.2 Information Elements + +| Information element name | Status | Description | +|--------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | M | The IMSI is used to identify the subscriber. | +| MSISDN | C | This shall consist of the subscriber's MSISDN if available. If no MSISDN is available, the parameter shall be set with a dummy MSISDN value. | +| CAMEL Subscription Information | M | The CAMEL Subscription Information IE is used to indicate the modified or deleted CAMEL Subscription Information data. This IE is described in a table below. | + +CAMEL Subscription Information Modified contains the following information elements: + +| Information element name | Status | Description | +|---------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| O-IM-CSI | S | See subclause 4.4.1.1. It shall be present if it was modified. | +| D-IM-CSI | S | See subclause 4.4.1.2. It shall be present if it was modified. | +| VT-IM-CSI | S | See subclause 4.4.1.3. It shall be present if it was modified. | +| Specific CSI Deleted List | S | This IE indicates that one or more specific elements of IMS CAMEL Subscription Information have been deleted from the HSS. It shall indicate any of the following;
  • - O-IM-CSI (with TDP criteria for O-IM-CSI);
  • - D-IM-CSI;
  • - VT-IM-CSI with TDP criteria for VT-IM-CSI;
This IE shall be present if IM CSI is/are deleted. | + +## 5 Control and interrogation of subscription data + +Support of the procedures described in this clause in CAMEL Phase 4 is a network operator option. + +### 5.1 Architecture + +The architecture for the control and the interrogation of subscription data described in the clause 10 in 3GPP TS 23.078 Rel-99 [4] for the HLR and the gsmSCF also applies for the HSS and the gsmSCF. + +### 5.2 Procedures for CAMEL + +#### 5.2.1 Any Time Subscription Interrogation + +The following process in the HLR described in 3GPP TS 23.078 Rel-99 [4] applies for the handling of Any Time Interrogation for Subscription Information Retrieval in the HSS: + +- CAMEL\_ATSI\_HLR. + +#### 5.2.2 Any Time Modification + +The following process in the HLR described in 3GPP TS 23.078 Rel-99 [4] applies for the handling of Any Time Modification in the HSS: + +- CAMEL\_ATM\_HLR. + +## 5.2.3 Notify Subscriber Data Change + +The description of the procedure in 3GPP TS 23.078 Rel-99 [4] applies for the handling of Notify Subscriber Data Change in the HSS. + +## 5.3 Description of information flows + +This subclause contains the detailed description of the information flows used by CAMEL for control and interrogation of subscription data. + +Each Information Element (IE) is marked as Mandatory (M), Conditional (C), Specific conditions (S), mutually Exclusive (E) or Optional (O). + +An 'M' IE shall always be included. A 'C' IE shall be included if the sending entity has the necessary information to populate the IE. The conditions for the inclusion of an 'S' IE are shown in the 'Description' column of the definition table. An 'O' IE may be included or omitted as required by the service logic. This categorization is a functional classification, i.e. it defines the requirements for the stage 2 information. It is not a stage 3 classification to be used for the ASN.1 syntax of the protocol. + +The following principles apply for the handling of the IEs by the receiving entity: + +- The gsmSCF may silently discard any IE which it does not functionally support. +- The HSS shall return an error if it does not functionally support an IE which it receives. + +Details of errors and exceptions to these rules are specified in 3GPP TS 29.002 [9]. + +### 5.3.1 gsmSCF to HSS information flows + +#### 5.3.1.1 Any Time Modification Request + +##### 5.3.1.1.1 Description + +This IF is used to modify information in the HSS at any time. The IF from the gsmSCF to the HLR is specified in 3GPP TS 23.078 Rel-99 [4]. The IF is also applied to the interface between the gsmSCF to the HSS. + +#### 5.3.1.2 Any Time Subscription Interrogation Request + +##### 5.3.1.2.1 Description + +This IF is used to request subscription information from the HSS at any time. The IF from the gsmSCF to the HLR is specified in 3GPP TS 23.078 Rel-99 [4]. The IF is also applied to the interface between the gsmSCF to the HSS. + +##### 5.3.1.2.2 Information Elements + +Any Time Subscription Interrogation Request is specified in 3GPP TS 23.078 Rel-99 [4]. Additionally the following IMS specific information elements are required: + +| Information element name | Status | Description | +|--------------------------|--------|-----------------------------------------------------| +| Requested Info | M | This IE may indicate supported CAMEL phases in HSS. | + +| | | | +|------------------------------------|-----|-----------------------------------------------------------------------------------| +| Additional CAMEL Subscription Info | S,E | This IE may be one of the following elements:
O-IM-CSI / VT-IM-CSI / D-IM-CSI. | +|------------------------------------|-----|-----------------------------------------------------------------------------------| + +#### 5.3.1.3 Notify Subscriber Data Change response + +##### 5.3.1.3.1 Description + +This IF is used by the gsmSCF to respond to the HSS of the change of subscriber data notify. The IF from the gsmSCF to the HLR is specified in 3GPP TS 23.078 Rel-99 [4]. The IF is also applied to the interface between the gsmSCF to the HSS. + +## 5.3.2 HSS to gsmSCF information flows + +### 5.3.2.1 Any Time Modification ack + +#### 5.3.2.1.1 Description + +This IF is used by the HSS to provide the modified information to the gsmSCF. The IF from the HLR to the gsmSCF is specified in 3GPP TS 23.078 Rel-99 [4]. The IF is also applied to the interface between the gsmSCF to the HSS. + +#### 5.3.2.1.2 Information Elements + +Any Time Modification ack is specified in 3GPP TS 23.078 Rel-99 [4]. Additionally the following IMS specific information elements are required: + +| Information element name | Status | Description | +|--------------------------|--------|----------------------------------------------------------------| +| O-IM-CSI | S | See subclause 4.4.1.1. It shall be present if it was modified. | +| VT-IM-CSI | S | See subclause 4.4.1.3. It shall be present if it was modified. | +| D-IM-CSI | S | See subclause 4.4.1.2. It shall be present if it was modified. | + +### 5.3.2.2 Any Time Subscription Interrogation ack + +#### 5.3.2.2.1 Description + +This IF is used by the HSS to provide the requested subscription information to the gsmSCF. The IF from the HLR to the gsmSCF is specified in 3GPP TS 23.078 Rel-99 [4]. The IF is also applied to the interface between the gsmSCF to the HSS. + +#### 5.3.2.2.2 Information Elements + +Any Time Subscription Interrogation ack is specified in 3GPP TS 23.078 Rel-99 [4]. Additionally the following IMS specific information elements are required: + +| Information element name | Status | Description | +|-------------------------------|--------|---------------------------------------------------------| +| Supported CAMEL Phases In HSS | C | This IE indicates the CAMEL phase supported in the HSS. | +| O-IM-CSI | C | See subclause 4.4.1.1. | +| VT-IM-CSI | C | See subclause 4.4.1.3. | +| D-IM-CSI | C | See subclause 4.4.1.2. | + +### 5.3.2.3 Notify Subscriber Data Change + +#### 5.3.2.3.1 Description + +This IF is used by the HSS to notify to the gsmSCF of the change of subscriber data. This IF is sent at each time subscriber data is changed. The IF from the HLR to the gsmSCF is specified in 3GPP TS 23.078 Rel-99 [4]. The IF is also applied to the interface between the gsmSCF to the HSS. + +#### 5.3.2.3.2 Information Elements + +Notify Subscriber Data Change is specified in 3GPP TS 23.078 Rel-99 [4]. Additionally the following IMS specific information elements are required: + +| Information element name | Status | Description | +|---------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Specific CSI Deleted List | S | This IE shall indicate any of the following;
- O-IM-CSI (with TDP criteria for O-IM-CSI);
- D-IM-CSI (with TDP criteria for D-IM-CSI);
- VT-IM-CSI with TDP criteria for VT-IM-CSI; | + +## 6 Subscriber Location and State retrieval + +Support of the procedures described in this clause in CAMEL Phase 4 is a network operator option. + +### 6.1 Architecture + +The architecture for the subscriber location and state retrieval described in the clause 11 in 3GPP TS 23.078 Rel-99 [4] for the HLR and the gsmSCF applies for the HSS and the gsmSCF. + +### 6.2 Procedures for CAMEL + +#### 6.2.1 Any Time Interrogation + +The description of the procedure in 3GPP TS 23.078 Rel-99 [4] applies for the Any Time Interrogation in the HSS. + +### 6.3 Description of information flows + +This subclause contains the detailed description of the information flows used by CAMEL for the retrieval of information about the location and state of a subscriber. + +Each Information Element (IE) is marked as Mandatory (M), Conditional (C), Specific conditions (S), mutually Exclusive (E) or not applicable (-). + +An 'M' IE shall always be included. A 'C' IE shall be included if the sending entity has the necessary information to populate the IE. The conditions for the inclusion of an 'S' IE are shown in the 'Description' column of the definition table. When a set of 'E' IEs is shown in the definition of an Information Flow or compound IE, only one of those IEs may be included. A '-' IE shall always be omitted. This categorization is a functional classification, i.e. it defines the requirements for the stage 2 information. It is not a stage 3 classification to be used for the ASN.1 syntax of the protocol. + +The following principles apply for the handling of the IEs by the receiving entity: + +- The gsmSCF may silently discard any IE which it does not functionally support. +- The GMLC shall return an error if it does not functionally support an IE which it receives. + +Details of errors and exceptions to these rules are specified in 3GPP TS 29.002 [9]. + +#### 6.3.1 gsmSCF to HSS information flows + +##### 6.3.1.1 Any Time Interrogation Request + +###### 6.3.1.1.1 Description + +This IF is used to request information (any one or more of subscriber state, subscriber location, IMEI & software version, MS classmark information for the CS domain and GPRS MS classmark information) from the HSS at any time. The IF from the gsmSCF to the HLR is specified in 3GPP TS 23.078 Rel-99 [4]. The IF is also applied to the interface between the gsmSCF to the HSS. + +#### 6.3.2 HSS to gsmSCF information flows + +##### 6.3.2.1 Any Time Interrogation ack + +###### 6.3.2.1.1 Description + +This IF is used by the HSS to provide the requested subscriber location and/or subscriber state information to the gsmSCF. The IF from the HLR to the gsmSCF is specified in 3GPP TS 23.078 Rel-99 [4]. The IF is also applied to the interface between the gsmSCF to the HSS. + +--- + +## Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-------------|------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | R
e
v | Subject/Comment | Old | New | +| 09/2002 | CN#17 | NP-020348 | | | Creation of version 5.0.0 | 2.1.0 | 5.0.0 | +| 12/2002 | CN#18 | NP-020530 | 001 | 2 | Correction and improvement in the overall SDL structure | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020530 | 002 | | Correction and improvement in the registration procedures | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020532 | 003 | 2 | Correction and improvement in MO procedures | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020532 | 004 | 3 | Correction and improvement in MT procedures | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020530 | 005 | | Correction and improvement in CSI update | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020530 | 006 | | Clarification in the case multiple RRBs are sent for a DP | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020530 | 007 | 1 | Inconsistent description on ACR: time information | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020530 | 008 | | Remove support of SCI operation from imcnSSF SDL process | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020530 | 009 | | Removal of ETC processing from IM-SSF SDL Procedures | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020530 | 010 | 1 | Correction of InitialDP MediaType parameter | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020532 | 012 | 1 | IF Description for gsmSRF-related operations for IMS | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020529 | 014 | | Figure and table numbers editorial changes | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020531 | 015 | | For better document structure - editorial | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020531 | 016 | | Editorial improvement - clause 2 | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020531 | 017 | | Editorial improvement - clause 3 | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020531 | 018 | | Editorial improvement - clause 4 | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020531 | 019 | | Editorial improvement - clause 5 | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020531 | 020 | | Editorial improvement - clause 6 | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020531 | 021 | | Editorial improvement - clause 7 | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020532 | 022 | | SDL Procedure for Connect To Resource | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020532 | 023 | 1 | Stage 2 specifications for Call Gap for IMS | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020532 | 024 | 2 | Clarification of DP destination number trigger criteria for IMS | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020532 | 025 | | Number comparison for D-CSI | 5.0.0 | 5.1.0 | +| 12/2002 | CN#18 | NP-020532 | 026 | | Correction to Dialled Services criteria | 5.0.0 | 5.1.0 | +| 03/2003 | CN#19 | NP-030090 | 027 | 1 | Implementing of Connect to Resource handling in CAMEL for IMS | 5.1.0 | 5.2.0 | +| 03/2003 | CN#19 | NP-030090 | 028 | 1 | Introduction of ResetTimer input in state WFI-DS (IMS) | 5.1.0 | 5.2.0 | +| 03/2003 | CN#19 | NP-030090 | 029 | | Correction of imcnSSF procedure names | 5.1.0 | 5.2.0 | +| 03/2003 | CN#19 | NP-030090 | 030 | | Incorrect procedure names used for CAMEL_MT_CTR and CAMEL_MO_CTR | 5.1.0 | 5.2.0 | +| 03/2003 | CN#19 | NP-030090 | 031 | | Incorrect procedures called in CAMEL_IMCN_MT_ANSWER | 5.1.0 | 5.2.0 | +| 03/2003 | CN#19 | NP-030091 | 032 | | Sending of provisional response for the INVITE | 5.1.0 | 5.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|----------------------------------------------------------------------------|--------|--------| +| 03/2003 | CN#19 | NP-030091 | 033 | | Incorrect SIP response when no CAMEL is invoked | 5.1.0 | 5.2.0 | +| 03/2003 | CN#19 | NP-030091 | 035 | 1 | Corrections in CAMEL_IMCN_MO_ANSWER | 5.1.0 | 5.2.0 | +| 03/2003 | CN#19 | NP-030091 | 036 | | Corrections in the procedures for handling failure SIP response | 5.1.0 | 5.2.0 | +| 03/2003 | CN#19 | NP-030091 | 039 | | Inconsistency in Call Information Report in Re-Connect Case | 5.1.0 | 5.2.0 | +| 06/2003 | CN#20 | NP-030191 | 040 | 1 | Incorrect list of TDPs listed for O-IM-CSI | 5.2.0 | 5.3.0 | +| 06/2003 | CN#20 | NP-030191 | 041 | | Corrections to process IM-SSF | 5.2.0 | 5.3.0 | +| 06/2003 | CN#20 | NP-030191 | 042 | | Redundant check for Final_Response_Received in Disconnect procedures | 5.2.0 | 5.3.0 | +| 09/2003 | CN#21 | NP-030374 | 043 | 2 | Incorrect handling of failure SIP response for MT | 5.3.0 | 5.4.0 | +| 09/2003 | CN#21 | NP-030374 | 044 | 2 | Setting of Timers not specified for IM-SSF process | 5.3.0 | 5.4.0 | +| 09/2003 | CN#21 | NP-030374 | 045 | 1 | Incorrect handling of failure SIP response for MO | 5.3.0 | 5.4.0 | +| 12/2003 | CN#22 | NP-030525 | 046 | 1 | Correction to the definition of interfaces for the IM-SSF | 5.4.0 | 5.5.0 | +| 09/2004 | CN#25 | NP-040397 | 047 | | Correction of Check_Criteria Procedure names referenced in Process imcnSSF | 5.5.0 | 5.6.0 | +| 12/2004 | CN#26 | | | | Rel-6 created after CN#26 | 5.6.0 | 6.0.0 | +| 06/2005 | CT#28 | CP-050097 | 0048 | | Removal of references to HLR for CAMEL control of IMS | 6.0.0 | 6.1.0 | +| 12/2005 | CT#30 | CP-050665 | 0049 | | Incorrect References | 6.1.0 | 6.2.0 | +| 12/2005 | CT#30 | | | | Rel-7 version was created because of ETSI TISPAN references. | 6.2.0 | 7.0.0 | +| 03/2006 | CT#31 | CP-060082 | 0050 | | Specification of gsmSCF Address format in AnyTime request messages | 7.0.0 | 7.1.0 | +| 12/2008 | CT#42 | | | | Upgraded unchanged from Rel-7 | 7.1.0 | 8.0.0 | +| 2009-12 | - | - | - | - | Update to Rel-9 version (MCC) | 8.0.0 | 9.0.0 | +| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-09 | CT#57 | CP-120467 | 0052 | 1 | Mapping of SIP Responses code and Camel Detection Points | 10.0.0 | 11.0.0 | +| 2012-10 | | | | | Missing SDLs related to CR 0052 added. | 11.0.0 | 11.0.1 | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23279/12de9b926df0384ec07702671827c9cd_img.jpg b/marked/Rel-11/23_series/23279/12de9b926df0384ec07702671827c9cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90bb8c7f92ed3b828ef4e0d4c07cbb1a0f813fd1 --- /dev/null +++ b/marked/Rel-11/23_series/23279/12de9b926df0384ec07702671827c9cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e64152dfdd10182288ca4e2e695fd88af2b0b86e7b02bc6010d1af581d2ab6f4 +size 84450 diff --git a/marked/Rel-11/23_series/23279/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-11/23_series/23279/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c436ee6c8742647fdaa8efef6e1d6139c545d59a --- /dev/null +++ b/marked/Rel-11/23_series/23279/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:264810c075e29af5b8ce14a9b588d72b13e246dc7cdb569858b0c6796d978028 +size 59239 diff --git a/marked/Rel-11/23_series/23279/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-11/23_series/23279/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2b68a21158c992c0918599122a166093b5e0cf1 --- /dev/null +++ b/marked/Rel-11/23_series/23279/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73bfcdeaba5b802b6915dfcc73ee02892decf3b79ef7cf26ee1d7441ae533277 +size 94723 diff --git a/marked/Rel-11/23_series/23279/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-11/23_series/23279/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2a3a5b6cb844afda92ddfbcc64fafc63e52a0d8 --- /dev/null +++ b/marked/Rel-11/23_series/23279/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:367cd147b114a8d173d9e97d8da277afe8e65e05fea8fbf7dccdc642d69381e7 +size 75960 diff --git a/marked/Rel-11/23_series/23279/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg b/marked/Rel-11/23_series/23279/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..719dca1955f76ba86a6184d78dfab340b9a3724c --- /dev/null +++ b/marked/Rel-11/23_series/23279/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9819b86d0b302f34cf3e5f32a1054deba09698791c91aea3f678c406b47d5851 +size 53234 diff --git a/marked/Rel-11/23_series/23279/6470d350326789d5306eabcb76533951_img.jpg b/marked/Rel-11/23_series/23279/6470d350326789d5306eabcb76533951_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..700aa05d0d0f4bca49014e0dbbbd11d70fc334e6 --- /dev/null +++ b/marked/Rel-11/23_series/23279/6470d350326789d5306eabcb76533951_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec828d7889a041cd55ec4f7c63277846a993fba643fba1725228b58cfe23eee0 +size 70992 diff --git a/marked/Rel-11/23_series/23279/803776dff64331076ffc951fc95358ee_img.jpg b/marked/Rel-11/23_series/23279/803776dff64331076ffc951fc95358ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5764f107ab3dcf0313e299b1dc95681ee80463f5 --- /dev/null +++ b/marked/Rel-11/23_series/23279/803776dff64331076ffc951fc95358ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:215018c3055666b2a34b15b2c005fd258b788e509f86fd61d022ea44380df180 +size 60868 diff --git a/marked/Rel-11/23_series/23279/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-11/23_series/23279/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bae4e3300307d6731acae87f9ff87014188eac7d --- /dev/null +++ b/marked/Rel-11/23_series/23279/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3eda0bcfba8d5fed92a6cf3b3293e233c3226584edd11ca9a5bc6de7f0c54a1c +size 62709 diff --git a/marked/Rel-11/23_series/23279/a3472689858b068ef469213682965325_img.jpg b/marked/Rel-11/23_series/23279/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18a70f7f4e55631e49b190930edd0dbe38365207 --- /dev/null +++ b/marked/Rel-11/23_series/23279/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9dab441e461e26c8e1471bf9d4264f9cc1568787b51c079314dde4962049e6b +size 113302 diff --git a/marked/Rel-11/23_series/23279/dfaa8b98082261913dac00eae86b2889_img.jpg b/marked/Rel-11/23_series/23279/dfaa8b98082261913dac00eae86b2889_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4a704366c6206ffb752889ef1920e46c1bc8d55 --- /dev/null +++ b/marked/Rel-11/23_series/23279/dfaa8b98082261913dac00eae86b2889_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:465486385ce26eccb89d2c9693e66975065589ed875f791f80788240bf9c0de2 +size 102901 diff --git a/marked/Rel-11/23_series/23279/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-11/23_series/23279/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f85f3d408e62578027cc809cca3ced1bb5804030 --- /dev/null +++ b/marked/Rel-11/23_series/23279/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93deadcc937a7bd05b1836f55a99bb2e05a16f6015813355f5a37f2f4e5d0ddf +size 73427 diff --git a/marked/Rel-11/23_series/23279/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-11/23_series/23279/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc6f0896aed83db2821e49cfa43663e452c5c42e --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23279/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg b/marked/Rel-11/23_series/23279/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05cf8ab77253295d95cd1fcf45b215d7e1c03c65 --- /dev/null +++ b/marked/Rel-11/23_series/23279/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c998828df324acfe001286cc0b7c47f38688d4ba21f24c8fd66ecb8f5c8ed7e +size 66074 diff --git a/marked/Rel-11/23_series/23279/f6e8acf9f931452d01688d311b5c0364_img.jpg b/marked/Rel-11/23_series/23279/f6e8acf9f931452d01688d311b5c0364_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6801bed8c412a4c8b6cf6b1ad02e3d1218d9076e --- /dev/null +++ b/marked/Rel-11/23_series/23279/f6e8acf9f931452d01688d311b5c0364_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:260a2b205c52ccd80f70acb90c764a85e18b96e5d58ed47ff9346c7362a12614 +size 73780 diff --git a/marked/Rel-11/23_series/23279/raw.md b/marked/Rel-11/23_series/23279/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..05bcd7c72a3800986e592ecc1b165da18f4e30fe --- /dev/null +++ b/marked/Rel-11/23_series/23279/raw.md @@ -0,0 +1,1185 @@ + + + + + + +# 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..... | 7 | +| 4.1 General description ..... | 7 | +| 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..... | 9 | +| 6.1 General Architecture ..... | 9 | +| 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". + +# --- 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 to 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 Section 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 Section 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 interconnection between CS and IMS domains for CSI. The diagram is split into 'Originating session side' and 'Terminating session side'. On the originating side, a UE with CS and IMS Client components connects to an xRAN, which in turn connects to a PS Core and a CS Core. The PS Core connects to an IMS Core via a Gm interface. The CS Core connects to the IMS Core via an ISC interface and to another CS Core via Nc and Nb interfaces. The IMS Core connects to the second IMS Core via Mw and Mb interfaces. The second IMS Core connects to a PS Core via Gm, which connects to an xRAN, which connects to a UE with CS and IMS Client components on the terminating side. Dashed lines represent Uu/Um interfaces between the UE and the xRAN.](e6df2733626a85205c1db682e6259c46_img.jpg) + +Figure 6-1: High level architecture diagram showing the interconnection between CS and IMS domains for CSI. The diagram is split into 'Originating session side' and 'Terminating session side'. On the originating side, a UE with CS and IMS Client components connects to an xRAN, which in turn connects to a PS Core and a CS Core. The PS Core connects to an IMS Core via a Gm interface. The CS Core connects to the IMS Core via an ISC interface and to another CS Core via Nc and Nb interfaces. The IMS Core connects to the second IMS Core via Mw and Mb interfaces. The second IMS Core connects to a PS Core via Gm, which connects to an xRAN, which connects to a UE with CS and IMS Client components on the terminating side. Dashed lines represent Uu/Um interfaces between the UE and the xRAN. + +**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 Section 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 [x]). + +### - **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 3GPP 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 subclause 7.4). + +The information flows for exchanging this information are shown in subclause 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 subclause. 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 subclause 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 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 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 subclause 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 illustrating the exchange of current radio environment information at CS call setup between UE-A, CS Domain (A), IMS Core (A), IMS Core (B), CS Domain (B), and UE-B.](f6e8acf9f931452d01688d311b5c0364_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 + + UE-A->>CS Domain (A): 1. SETUP + CS Domain (A)->>CS Domain (B): 2. IAM + CS Domain (B)->>UE-B: 3. SETUP + UE-B->>CS Domain (B): 4. CONNECT + Note right of UE-B: 4a. UE-B may trigger to do the IMS registration based on preconfigured user's preference + CS Domain (B)->>CS Domain (A): 5. CON/ANM + CS Domain (A)->>UE-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 illustrating the exchange of current radio environment information at CS call setup between UE-A, CS Domain (A), IMS Core (A), IMS Core (B), CS Domain (B), and UE-B. + +**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 subclause 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 sub-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 Section 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 subclause 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 showing 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 showing 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 subclause 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, in the SIP OPTIONS request and any registered caller capabilities, as defined in RFC 3840, (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 subclause 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 illustrating the process of adding an IMS session to an ongoing CS call. The diagram shows interactions between UE-A, CS Domain (A), IMS Core (A), IMS Core (B), CS Domain (B), and UE-B. The process starts with CS Call Setup and IMS Capability exchange. Then, User A triggers an IMS service, leading to a series of SIP INVITE, 200 OK, and ACK messages that establish a media session.](4356776ca004ecba5d599667a155d7d4_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->>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 illustrating the process of adding an IMS session to an ongoing CS call. The diagram shows interactions between UE-A, CS Domain (A), IMS Core (A), IMS Core (B), CS Domain (B), and UE-B. The process starts with CS Call Setup and IMS Capability exchange. Then, User A triggers an IMS service, leading to a series of SIP INVITE, 200 OK, and ACK messages that establish a media session. + +**Figure 8.3-1: User adds an IMS session to an ongoing CS call** + +1) A CS call is setup as per subclause 8.1. + +2) The UE-A should initiate an IMS capability exchange as described in section 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 illustrating the IMS session setup with media requiring resource reservation. The diagram shows the interaction between UE-A, CS Domain (A), IMS Core (A), IMS Core (B), CS Domain (B), and UE-B. The process starts with CS Call Setup (1) and IMS Capability exchange (2). UE-A triggers an IMS service (3). The INVITE(inactive) message is sent from UE-A to IMS Core (A) (3), then to IMS Core (B) (4), then to CS Domain (B) (5), and finally to UE-B (6). UE-B associates the INVITE with the CS call (6). The 200 OK (inactive) message is sent from UE-B to CS Domain (B) (7), then to IMS Core (B) (8), then to IMS Core (A) (9), and finally to UE-A (10). The ACK message is sent from UE-A to IMS Core (A) (11), then to IMS Core (B) (12), then to CS Domain (B) (13), and finally to UE-B (14). The INVITE(active) message is sent from UE-A to IMS Core (A) (15), then to IMS Core (B) (16), then to CS Domain (B) (17), and finally to UE-B (18). UE-B accepts the service (19). The 200 OK (active) message is sent from UE-B to CS Domain (B) (20), then to IMS Core (B) (21), then to IMS Core (A) (22), and finally to UE-A (23). The ACK message is sent from UE-A to IMS Core (A) (24), then to IMS Core (B) (25), then to CS Domain (B) (26), and finally to UE-B (27). The Media session is established (28).](12de9b926df0384ec07702671827c9cd_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 + + Note right of UE-B: bear-er set up + + 1. CS Call Setup + 2. IMS Capability exchange (see Note) + + 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: 6. INVITE(inactive) + Note right of UE-B: 6. UE-B associate the INVITE with the CS call + UE-B->>CS Domain (B): 7. 200 OK (inactive) + CS Domain (B)->>IMS Core (B): 8. 200 OK (inactive) + IMS Core (B)->>IMS Core (A): 9. 200 OK (inactive) + IMS Core (A)->>UE-A: 10. 200 OK (inactive) + UE-A->>IMS Core (A): 11. ACK + IMS Core (A)->>IMS Core (B): 12. ACK + IMS Core (B)->>CS Domain (B): 13. ACK + CS Domain (B)->>UE-B: 14. ACK + UE-A->>IMS Core (A): 15. INVITE(active) + IMS Core (A)->>IMS Core (B): 16. INVITE(active) + IMS Core (B)->>CS Domain (B): 17. INVITE(active) + CS Domain (B)->>UE-B: 18. INVITE(active) + Note right of UE-B: 16. User B accepts the service + UE-B->>CS Domain (B): 19. 200 OK (active) + CS Domain (B)->>IMS Core (B): 20. 200 OK (active) + IMS Core (B)->>IMS Core (A): 21. 200 OK (active) + IMS Core (A)->>UE-A: 22. 200 OK (active) + UE-A->>IMS Core (A): 23. ACK + IMS Core (A)->>IMS Core (B): 24. ACK + IMS Core (B)->>CS Domain (B): 25. ACK + CS Domain (B)->>UE-B: 26. ACK + Note bottom: 23. Media session established + +``` + +Sequence diagram illustrating the IMS session setup with media requiring resource reservation. The diagram shows the interaction between UE-A, CS Domain (A), IMS Core (A), IMS Core (B), CS Domain (B), and UE-B. The process starts with CS Call Setup (1) and IMS Capability exchange (2). UE-A triggers an IMS service (3). The INVITE(inactive) message is sent from UE-A to IMS Core (A) (3), then to IMS Core (B) (4), then to CS Domain (B) (5), and finally to UE-B (6). UE-B associates the INVITE with the CS call (6). The 200 OK (inactive) message is sent from UE-B to CS Domain (B) (7), then to IMS Core (B) (8), then to IMS Core (A) (9), and finally to UE-A (10). The ACK message is sent from UE-A to IMS Core (A) (11), then to IMS Core (B) (12), then to CS Domain (B) (13), and finally to UE-B (14). The INVITE(active) message is sent from UE-A to IMS Core (A) (15), then to IMS Core (B) (16), then to CS Domain (B) (17), and finally to UE-B (18). UE-B accepts the service (19). The 200 OK (active) message is sent from UE-B to CS Domain (B) (20), then to IMS Core (B) (21), then to IMS Core (A) (22), and finally to UE-A (23). The ACK message is sent from UE-A to IMS Core (A) (24), then to IMS Core (B) (25), then to CS Domain (B) (26), and finally to UE-B (27). The Media session is established (28). + +**Figure 8.3-2: User adds an IMS session to an ongoing CS call** + +- 1) A CS call is setup as per subclause 8.1. +- 2) The UE-A should initiate an IMS capability exchange as described in section 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 split into two parts: the initial IMS session setup (steps 1-6) and the subsequent CS call setup (steps 8-16), separated by a note that the IMS flow continues as per standard (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-->>CS-A: 12. ACM + CS-A-->>UE-A: 13. ALERTING + UE-B-->>CS-B: 14. CONNECT. + CS-B-->>CS-A: 15. ANM + 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 split into two parts: the initial IMS session setup (steps 1-6) and the subsequent CS call setup (steps 8-16), separated by a note that the IMS flow continues as per standard (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 subclause 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 CSI AS to S-CSCF 1; 10. INVITE (MSRP) from S-CSCF 1 to CS Domain 1; 11. CONNECT from CS Domain 1 to UE 1; 12. CON from CS Domain 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 CS Domain 1 to S-CSCF 1; 16. 200 OK (for MSRP) from S-CSCF 1 to CSI AS; 17. 200 OK (for Voice + MSRP) from CSI AS to S-CSCF 1; 18. 200 OK (for Voice + MSRP) from S-CSCF 1 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 CSI AS to S-CSCF 1; 10. INVITE (MSRP) from S-CSCF 1 to CS Domain 1; 11. CONNECT from CS Domain 1 to UE 1; 12. CON from CS Domain 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 CS Domain 1 to S-CSCF 1; 16. 200 OK (for MSRP) from S-CSCF 1 to CSI AS; 17. 200 OK (for Voice + MSRP) from CSI AS to S-CSCF 1; 18. 200 OK (for Voice + MSRP) from S-CSCF 1 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 section 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 sections 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. + +![Diagram of General architecture and signalling flow in case of CSI origination and IMS termination with CSI interworking in originating network. The diagram is split into two halves by a vertical dashed line. The left half, 'CSI Origination', shows UE 1 with CS and IMS components connected to an xRAN. The CS component connects to 'CS domain 1' via a Uu/Um interface. The IMS component connects to 'PS domain 1' via a Gm interface. Both domains connect to a 'CSI AS' (CSI Application Server) in 'IMS domain 1'. The right half, 'IMS termination', shows 'IMS domain 2' connected to 'PS domain 2' via an Mw interface. 'PS domain 2' connects to an xRAN, which connects to UE 2 with an IMS component via a Gm interface. A blue arrow (Multimedia IMS session) goes from UE 1 (IMS) to UE 2 (IMS). An orange arrow (CS call) goes from UE 1 (CS) to the CSI AS. A green arrow (IMS session) goes from UE 1 (IMS) to the CSI AS. A legend at the bottom right defines the arrow colors: blue for Multimedia IMS session (for voice and other), orange for CS call (for voice), and green for IMS session (for other).](803776dff64331076ffc951fc95358ee_img.jpg) + +Diagram of General architecture and signalling flow in case of CSI origination and IMS termination with CSI interworking in originating network. The diagram is split into two halves by a vertical dashed line. The left half, 'CSI Origination', shows UE 1 with CS and IMS components connected to an xRAN. The CS component connects to 'CS domain 1' via a Uu/Um interface. The IMS component connects to 'PS domain 1' via a Gm interface. Both domains connect to a 'CSI AS' (CSI Application Server) in 'IMS domain 1'. The right half, 'IMS termination', shows 'IMS domain 2' connected to 'PS domain 2' via an Mw interface. 'PS domain 2' connects to an xRAN, which connects to UE 2 with an IMS component via a Gm interface. A blue arrow (Multimedia IMS session) goes from UE 1 (IMS) to UE 2 (IMS). An orange arrow (CS call) goes from UE 1 (CS) to the CSI AS. A green arrow (IMS session) goes from UE 1 (IMS) to the CSI AS. A legend at the bottom right defines the arrow colors: blue for Multimedia IMS session (for voice and other), orange 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), xRAN, CS domain 1, PS domain 1, and IMS domain 1. On the right, 'IMS termination' includes IMS domain 2, CSI AS, PS domain 2, xRAN, and UE 2 (with IMS). Signalling flows are: a yellow line (CS call) from UE 1 CS via xRAN and CS domain 1 to CSI AS; a green line (IMS session) from UE 1 IMS via xRAN, PS domain 1, and IMS domain 1 to CSI AS; and a blue line (Multimedia IMS session) from CSI AS via PS domain 2 and xRAN to UE 2 IMS. Interfaces labeled include Uu/Um, Gm, and Mw.](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), xRAN, CS domain 1, PS domain 1, and IMS domain 1. On the right, 'IMS termination' includes IMS domain 2, CSI AS, PS domain 2, xRAN, and UE 2 (with IMS). Signalling flows are: a yellow line (CS call) from UE 1 CS via xRAN and CS domain 1 to CSI AS; a green line (IMS session) from UE 1 IMS via xRAN, PS domain 1, and IMS domain 1 to CSI AS; and a blue line (Multimedia IMS session) from CSI AS via PS domain 2 and xRAN to UE 2 IMS. Interfaces labeled include Uu/Um, Gm, and Mw. + +**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 + participant CSI-AS + participant gsmSCF + participant CAMEL_Svc as CAMEL Svc + participant CSAF + participant IMS_Core_B as IMS Core B + + Note right of gsmSCF: 3.Rerouting to IMS + Note right of CSAF: 8. CS origination processing + + UE->>VMSC: 1.Setup (B-party DN) + VMSC->>gsmSCF: 2. IDP ( ) + gsmSCF->>CAMEL_Svc: + CAMEL_Svc->>gsmSCF: + gsmSCF->>VMSC: 4. Connect ( IMRN ) + VMSC->>MGCF: 5. IAM ( IMRN ) + MGCF->>I-CSCF: 6. INVITE ( IMRN ) + Note left of S-CSCF: + I-CSCF->>S-CSCF: 7a1. INVITE ( IMRN ) + S-CSCF->>CSI-AS: 7a2. INVITE ( IMRN ) + CSI-AS->>CSAF: 7b. INVITE ( IMRN ) + CSAF->>CAMEL_Svc: + CAMEL_Svc->>S-CSCF: 9. INVITE ( B-party DN ) + S-CSCF->>I-CSCF: 10. INVITE ( B-party DN ) + I-CSCF->>S-CSCF: 11. INVITE ( B-party DN ) + S-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: "Voice Call Continuity (VCC) between Circuit Switched (CS) and IP Multimedia Subsystem (IMS); Stage 2". + +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. + +![Sequence diagram showing the call flow for adding an IMS session to an existing voice call. The diagram is divided into two main sections: 'Terminating side for IMS session' (left) and 'Originating side for IMS session' (right). The entities involved are UE1, CS domain 1, S-CSCF1, CSI-AS1, MGCF/MGW, S-CSCF2, and UE2. The initial call flow involves UE1 and UE2 connected via a 'CS voice bearer' through CS domain 1, S-CSCF1, MGCF/MGW, and S-CSCF2. The IMS session addition flow starts with UE2 sending a RE-INVITE (1) to S-CSCF2, which is forwarded (2) to S-CSCF1. S-CSCF1 then sends an INVITE (4) to CSI-AS1, which responds with a RE-INVITE (3) to S-CSCF1. S-CSCF1 then sends an INVITE (5) to UE1, which responds with a 200 OK (6). S-CSCF1 then sends a 200 OK (7) to CSI-AS1, which responds with a 200 OK (8) to S-CSCF1. S-CSCF1 then sends a 200 OK (9) to MGCF/MGW, which in turn sends a 200 OK (10) to S-CSCF2, which finally sends a 200 OK (11) to UE2. A 'Userplane for MSRP' is established between UE1 and UE2.](5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg) + +Sequence diagram showing the call flow for adding an IMS session to an existing voice call. The diagram is divided into two main sections: 'Terminating side for IMS session' (left) and 'Originating side for IMS session' (right). The entities involved are UE1, CS domain 1, S-CSCF1, CSI-AS1, MGCF/MGW, S-CSCF2, and UE2. The initial call flow involves UE1 and UE2 connected via a 'CS voice bearer' through CS domain 1, S-CSCF1, MGCF/MGW, and S-CSCF2. The IMS session addition flow starts with UE2 sending a RE-INVITE (1) to S-CSCF2, which is forwarded (2) to S-CSCF1. S-CSCF1 then sends an INVITE (4) to CSI-AS1, which responds with a RE-INVITE (3) to S-CSCF1. S-CSCF1 then sends an INVITE (5) to UE1, which responds with a 200 OK (6). S-CSCF1 then sends a 200 OK (7) to CSI-AS1, which responds with a 200 OK (8) to S-CSCF1. S-CSCF1 then sends a 200 OK (9) to MGCF/MGW, which in turn sends a 200 OK (10) to S-CSCF2, which finally sends a 200 OK (11) 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 a 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 sends 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 sends it to S-CSCF1. S-CSCF1 sends the 200 OK to UE1. Finally, a userplane for MSRP is established between UE1 and UE2.](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 UE1: 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 sends 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 sends it to S-CSCF1. S-CSCF1 sends the 200 OK to UE1. Finally, a userplane for MSRP is established between UE1 and UE2. + +**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 several network entities: UE, VMSC, MGCF, I-CSCF, S-CSCF, CSI-AS, gsmSCF, CAMEL Svc, CSAF, and IMS Core B. The process starts with a Setup message from the UE to the VMSC, followed by an IDP message to the gsmSCF. The gsmSCF then triggers a 'Rerouting to IMS' block involving the CAMEL Svc and CSAF. Subsequent messages include Connect (IMRN), IAM (IMRN), and INVITE (IMRN) messages passed through the MGCF and I-CSCF. A dashed box contains three INVITE (IMRN) messages (7a1, 7a2, 7b) between the I-CSCF and the CSAF. After 'CS origination processing' in the CSAF, the call continues with INVITE and RE-INVITE messages (B-party DN) between the S-CSCF and the IMS Core B. At the bottom, a 'CS voice bearer' is shown between the UE and the MGCF, and a 'VoIP voice bearer' is shown between the MGCF and the IMS Core B.](dfaa8b98082261913dac00eae86b2889_img.jpg) + +Sequence diagram showing the call flow for adding a voice call to an existing IMS session. The diagram involves several network entities: UE, VMSC, MGCF, I-CSCF, S-CSCF, CSI-AS, gsmSCF, CAMEL Svc, CSAF, and IMS Core B. The process starts with a Setup message from the UE to the VMSC, followed by an IDP message to the gsmSCF. The gsmSCF then triggers a 'Rerouting to IMS' block involving the CAMEL Svc and CSAF. Subsequent messages include Connect (IMRN), IAM (IMRN), and INVITE (IMRN) messages passed through the MGCF and I-CSCF. A dashed box contains three INVITE (IMRN) messages (7a1, 7a2, 7b) between the I-CSCF and the CSAF. After 'CS origination processing' in the CSAF, the call continues with INVITE and RE-INVITE messages (B-party DN) between the S-CSCF and the IMS Core B. At the bottom, a 'CS voice bearer' is shown between the UE and the MGCF, and a 'VoIP voice bearer' is shown between the MGCF and the IMS Core B. + +NOTE: The functionality of the CAMEL Svc and CSAF are the same as described in TS 23.206: "Voice Call Continuity (VCC) between Circuit Switched (CS) and IP Multimedia Subsystem (IMS); Stage 2". + +**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 | +| | | | | | | | | | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23284/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-11/23_series/23284/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7857ad25ef2a07ecd557d2db6de0c3282d80b93 --- /dev/null +++ b/marked/Rel-11/23_series/23284/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0cabf726353ce824bb64e6604e4d0d59b85526a861f524ebbaa7d51c8d507249 +size 95377 diff --git a/marked/Rel-11/23_series/23284/0cc154cbdde7cc6c39f394597c7aca0c_img.jpg b/marked/Rel-11/23_series/23284/0cc154cbdde7cc6c39f394597c7aca0c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..beb8cdfe9c25e1712ab5bc03530e851a05dbab6a --- /dev/null +++ b/marked/Rel-11/23_series/23284/0cc154cbdde7cc6c39f394597c7aca0c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d95c60d073b171601d62cebc6be2f9abd2f5544de6b55341f868caf5956e327d +size 95295 diff --git a/marked/Rel-11/23_series/23284/0ee9d674085524d589646a6c3fb21ec3_img.jpg b/marked/Rel-11/23_series/23284/0ee9d674085524d589646a6c3fb21ec3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0027931c50c9554a286cee0ee3f84f045a70c047 --- /dev/null +++ b/marked/Rel-11/23_series/23284/0ee9d674085524d589646a6c3fb21ec3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4fba5a4d325b6a48a852f78bdaecd599d17f2026ab264de0bd8a1e65cd96d43e +size 46287 diff --git a/marked/Rel-11/23_series/23284/1018d0db7bb02c169f646cb9cc244dc6_img.jpg b/marked/Rel-11/23_series/23284/1018d0db7bb02c169f646cb9cc244dc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8604ed7f2acc70461c70c1050e559de133a97c8 --- /dev/null +++ b/marked/Rel-11/23_series/23284/1018d0db7bb02c169f646cb9cc244dc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b800fa483a1a8532f7132fd2785f472bf9ad788fb28b12637f5724510b232bb +size 47742 diff --git a/marked/Rel-11/23_series/23284/114902bbeea56bda01b64b43fad41920_img.jpg b/marked/Rel-11/23_series/23284/114902bbeea56bda01b64b43fad41920_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59cc45b5dbb6734602562d161faa566c69f36331 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg b/marked/Rel-11/23_series/23284/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab467b220fca7fcdd01fe703ed0423b5aef6b828 --- /dev/null +++ b/marked/Rel-11/23_series/23284/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd421e19ba5296fd2f3e5a0f0b2205935d1060582e60a339741736204091f02b +size 77011 diff --git a/marked/Rel-11/23_series/23284/1399c76ef88f22b70d05ed3f781d3c48_img.jpg b/marked/Rel-11/23_series/23284/1399c76ef88f22b70d05ed3f781d3c48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..172b1cb6f0b480f3458f35c273577e72d80de735 --- /dev/null +++ b/marked/Rel-11/23_series/23284/1399c76ef88f22b70d05ed3f781d3c48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d19d157e4f99eef5940a162278ddf2b279a5dc3d2ffbab5c1578c821e0494c9c +size 72123 diff --git a/marked/Rel-11/23_series/23284/13fde41de77bf026013a0b81684d1fc9_img.jpg b/marked/Rel-11/23_series/23284/13fde41de77bf026013a0b81684d1fc9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9491b809b94042cb2f29b433ce5823a1816b9da --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-11/23_series/23284/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a72b345b872a2d0f62b5cf13ce5bfce70e2fddc --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-11/23_series/23284/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10dff6d30bb3cc926f928f54d079e993405042a8 --- /dev/null +++ b/marked/Rel-11/23_series/23284/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:adff70d8d3f15983328f7197f50b568a02ec0062e1f6dce82386705680d0630b +size 176878 diff --git a/marked/Rel-11/23_series/23284/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg b/marked/Rel-11/23_series/23284/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d2b9d010f6bac2a139fae077a1d92e342952e86 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/215165a27ad7d72bd39fdf55a3cb7486_img.jpg b/marked/Rel-11/23_series/23284/215165a27ad7d72bd39fdf55a3cb7486_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2a46e525d0201797814cab46bc0a2044a3a305b --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/237b76118be454462fc9b4e96adaa6c7_img.jpg b/marked/Rel-11/23_series/23284/237b76118be454462fc9b4e96adaa6c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4be2360e5b28ea1190d82a11430c8e05674d0d54 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-11/23_series/23284/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54e22ee575a93bedce52117f6d090211eac6cc82 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-11/23_series/23284/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ccc9f9da5a581fe6ccdba293e3976153d686c00b --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-11/23_series/23284/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bc8bb0ac01af10d7e1c3e5e47cb42c1b6835899 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-11/23_series/23284/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a189bb66d1f95e628438da597d9f874ea549655 --- /dev/null +++ b/marked/Rel-11/23_series/23284/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:238ebb909cdcf83d838097d9fc3a069585a52bd625c0e897c3c6bbf9e10f74da +size 140592 diff --git a/marked/Rel-11/23_series/23284/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-11/23_series/23284/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96159397458323b0dcf29188fc43d01e7b399af3 --- /dev/null +++ b/marked/Rel-11/23_series/23284/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d149cb0f4b97511058dd462658307feb0db9dfe8f7d15baae1f2daa63cebdfdc +size 170957 diff --git a/marked/Rel-11/23_series/23284/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-11/23_series/23284/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..795b48c80c18c08708925196f4b7075d693f5ec9 --- /dev/null +++ b/marked/Rel-11/23_series/23284/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f472dd180712d3713d00f54361b390c53521db5271a765513418b6bb3ae700a9 +size 169628 diff --git a/marked/Rel-11/23_series/23284/2f587210e4f97c32758c5972e2e83d20_img.jpg b/marked/Rel-11/23_series/23284/2f587210e4f97c32758c5972e2e83d20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b485cdc7616cb8397a57d95aa7e9ac64ec202ac3 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/30387053b5b3fede6873f6a46a9ca4a9_img.jpg b/marked/Rel-11/23_series/23284/30387053b5b3fede6873f6a46a9ca4a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..117e0be2389dff20abb919fe1aa708f25cab515c --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Rel-11/23_series/23284/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81dd83063e9689c271bfb2d7290152b7c1bf1b38 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/31ef15d175af5babdbf4d2fbac884c1b_img.jpg b/marked/Rel-11/23_series/23284/31ef15d175af5babdbf4d2fbac884c1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3db5d895fe3872026be4e18a37cb0be57ad34c3 --- /dev/null +++ b/marked/Rel-11/23_series/23284/31ef15d175af5babdbf4d2fbac884c1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06e2bab85350fe66195f2b055de5676e472e58ac49c01b8f0dc397f8c7014429 +size 71618 diff --git a/marked/Rel-11/23_series/23284/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-11/23_series/23284/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85ea84aa3d49f2e5bcaa78afa486696434687f73 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg b/marked/Rel-11/23_series/23284/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8b17e2eb17b6fda399c04bc24bebd644ea6e315 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/marked/Rel-11/23_series/23284/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd7799dcae490cc88c8b99f48dafd4170ed703cb --- /dev/null +++ b/marked/Rel-11/23_series/23284/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:211246888864d95a7317030bc636b8a029243c25fb3c0f5fe76fe7558420449d +size 79851 diff --git a/marked/Rel-11/23_series/23284/3750b0149a6380885998ab3ca6a8787c_img.jpg b/marked/Rel-11/23_series/23284/3750b0149a6380885998ab3ca6a8787c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e324390ccb56c7acea3414217d191a3bcf5ed8f --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/37a6ab1d23efb9dc00cfae09d353b1da_img.jpg b/marked/Rel-11/23_series/23284/37a6ab1d23efb9dc00cfae09d353b1da_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..246206efa5a9b2547bea3e525293e40b6bf24556 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg b/marked/Rel-11/23_series/23284/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..429b93355cbd353eb073e11727fd14ca0e1d184c --- /dev/null +++ b/marked/Rel-11/23_series/23284/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8910872b3d51d66a2f5991f391b8337be956055a862b72a1455012e61a5f9548 +size 64068 diff --git a/marked/Rel-11/23_series/23284/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg b/marked/Rel-11/23_series/23284/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..978df33e2f3c1b70d1903a4b3605cfc1760e1656 --- /dev/null +++ b/marked/Rel-11/23_series/23284/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:517007d0d71cccecf165e7269db99d579e501841ac82a7cf0ac9fb7be49cfe1d +size 172067 diff --git a/marked/Rel-11/23_series/23284/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg b/marked/Rel-11/23_series/23284/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0424451fa61b06213f904415d4dc98169719c827 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-11/23_series/23284/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21d5792984c0a5df88ec2860a3a926e9abce8a40 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg b/marked/Rel-11/23_series/23284/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f36ba35b31a2a07030ba734a2ee2349074eef208 --- /dev/null +++ b/marked/Rel-11/23_series/23284/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a7690f201b902ca65a95edc7d99e2fc6c32b63c59df58cbf36c6d75b451618e +size 112427 diff --git a/marked/Rel-11/23_series/23284/458fdbcb4015a4ee90bd84809afc4aac_img.jpg b/marked/Rel-11/23_series/23284/458fdbcb4015a4ee90bd84809afc4aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80627d82c904aaf24d2b25463493417f9034c9f2 --- /dev/null +++ b/marked/Rel-11/23_series/23284/458fdbcb4015a4ee90bd84809afc4aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07899d74f562aea7d951757ab0cc7a8305c0b51896a9ba2371b257fbad89c70d +size 114302 diff --git a/marked/Rel-11/23_series/23284/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/marked/Rel-11/23_series/23284/49fe8fe978c0f7e73112d231feb377eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f1ebde1fa5219204cc72d2fecb74f6f976b399e --- /dev/null +++ b/marked/Rel-11/23_series/23284/49fe8fe978c0f7e73112d231feb377eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:590ed1950be931c386d1ecc59bb953cce7ebb8bf2cad40fc0f87ebed8b3c0b99 +size 91121 diff --git a/marked/Rel-11/23_series/23284/4af57aad638888edf2062306f8a54a6c_img.jpg b/marked/Rel-11/23_series/23284/4af57aad638888edf2062306f8a54a6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e811582acb46f85d66810d964c94f23101c41be3 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-11/23_series/23284/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b066997c58a2d6a935fa59f6bd765e4dd879d50 --- /dev/null +++ b/marked/Rel-11/23_series/23284/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86d6abd8cd62602b3341c37fbc52d5c55bd41cbcdb4bb17110a7bafde6f5b760 +size 55278 diff --git a/marked/Rel-11/23_series/23284/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg b/marked/Rel-11/23_series/23284/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7366ccede1b6e9dec29983e865f5e25e322f835c --- /dev/null +++ b/marked/Rel-11/23_series/23284/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b772c48ee77c75122cba120623a2100b10a4e23f4dc4f034e20523a81f3b972b +size 95648 diff --git a/marked/Rel-11/23_series/23284/4ff00a489baaa34a0c01070de1d613db_img.jpg b/marked/Rel-11/23_series/23284/4ff00a489baaa34a0c01070de1d613db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33c0e2d779440b2bbf3fb30ccaa61d3955945011 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg b/marked/Rel-11/23_series/23284/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..766882cf1ee8a6c49abfe9105e4409f7fe5d4dc9 --- /dev/null +++ b/marked/Rel-11/23_series/23284/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37a27eb4047256dd0c34beafeef08393932d99699fb226bfc194c29e3fe413ae +size 81159 diff --git a/marked/Rel-11/23_series/23284/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-11/23_series/23284/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6b0f9deec7eb9dbb8e9a2f16112d101ef1c527e --- /dev/null +++ b/marked/Rel-11/23_series/23284/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3774ffe5a01d2d8b53229c652bd261fb5c64bb672c00a6dd1b2d33c21bea52da +size 117862 diff --git a/marked/Rel-11/23_series/23284/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-11/23_series/23284/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09b4905d6314d96a645fa43b0f132b596cd0332b --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-11/23_series/23284/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c32838fdbf3a3d59a314452767a259736c61a3e --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/marked/Rel-11/23_series/23284/5cf80bac69830ea773ac17c87e0ae24d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b45a5e9cc42d11d958abc47aba6a053bf0c33183 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg b/marked/Rel-11/23_series/23284/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f37a25942c1c2e7c7227e86d5ef589dea78e24c7 --- /dev/null +++ b/marked/Rel-11/23_series/23284/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46727eacee9180bb69001903064abc403b96661807fa3fcc2bfd5cbb821d9841 +size 143346 diff --git a/marked/Rel-11/23_series/23284/5dadcfbae18c4b3f91ea3a5e84d0a47a_img.jpg b/marked/Rel-11/23_series/23284/5dadcfbae18c4b3f91ea3a5e84d0a47a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89b286c5e7dfd4eb27f3d2790a33fe856eb291f5 --- /dev/null +++ b/marked/Rel-11/23_series/23284/5dadcfbae18c4b3f91ea3a5e84d0a47a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d1b811111b1386173f3f06d652b919fc4a78630aacac55b18eb88d04c9fecbd +size 38349 diff --git a/marked/Rel-11/23_series/23284/605ad256780bc1b6022dfb65a6e24a3b_img.jpg b/marked/Rel-11/23_series/23284/605ad256780bc1b6022dfb65a6e24a3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8d56583d77f149efc9da07ab047ebfe31b19ff6 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg b/marked/Rel-11/23_series/23284/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..276a5121db9375d0216cc3c5537e81b80bec6ee4 --- /dev/null +++ b/marked/Rel-11/23_series/23284/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cea9930a6785b5628f77d313887b0e12ea3cde6e941312a55ddddc95cb65626 +size 188423 diff --git a/marked/Rel-11/23_series/23284/64323b705244afc70bf77babdacb6ce5_img.jpg b/marked/Rel-11/23_series/23284/64323b705244afc70bf77babdacb6ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3966e1f0ac1ba37465573f781d0ddd873ce716fa --- /dev/null +++ b/marked/Rel-11/23_series/23284/64323b705244afc70bf77babdacb6ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:867fb841929095ffef5f5812531079de82498dbce6708b11265ce5aacc8445cb +size 67713 diff --git a/marked/Rel-11/23_series/23284/6584b95e34ea1f0b67144aa841db0863_img.jpg b/marked/Rel-11/23_series/23284/6584b95e34ea1f0b67144aa841db0863_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c0f2c1867f9eebe8dcd34575a5a2c399823c7ba --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-11/23_series/23284/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12cecc0500c0e2ab6fab676b4aec80ba5f3c82c9 --- /dev/null +++ b/marked/Rel-11/23_series/23284/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:efcabd42efae08009f75a2c223b1087c5d61cc7698f5b290a87a3ddb1d189123 +size 188133 diff --git a/marked/Rel-11/23_series/23284/677bcb564410628b8b966ad87b394888_img.jpg b/marked/Rel-11/23_series/23284/677bcb564410628b8b966ad87b394888_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fff9a41d0c73326c5cb2bc19e533453a392bd17 --- /dev/null +++ b/marked/Rel-11/23_series/23284/677bcb564410628b8b966ad87b394888_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bc1b7f1d317e2aca3b31813ad851090b5fb53ca4b27686857689609d0c9e97e +size 55180 diff --git a/marked/Rel-11/23_series/23284/694df81535f89c7bfb9ef0df6f130dc0_img.jpg b/marked/Rel-11/23_series/23284/694df81535f89c7bfb9ef0df6f130dc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b25443005895c9236f8d973e7c958a7216d9ea0 --- /dev/null +++ b/marked/Rel-11/23_series/23284/694df81535f89c7bfb9ef0df6f130dc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70b894fe42ef43f747953e9e6deff58c4c746dc2fe6f48a619306d5e71ff1630 +size 164240 diff --git a/marked/Rel-11/23_series/23284/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/marked/Rel-11/23_series/23284/6ca05954842b17f14dfd52f26b9d43d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b505a589743e8a0eb4820d67b7d171265201a32 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-11/23_series/23284/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..036f0d09e88bb865f96ade7806bb421efd44bc14 --- /dev/null +++ b/marked/Rel-11/23_series/23284/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:debbaf11b13b44db44ffff45eb5f4d8baf874728a435393143f62adb2c9f044f +size 56834 diff --git a/marked/Rel-11/23_series/23284/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-11/23_series/23284/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce0a74900c1ded67659d230d68c01a94c0e9e1d9 --- /dev/null +++ b/marked/Rel-11/23_series/23284/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60ef44f4a5db10c5f2f21bf6199dd1e80b90e1cb46cd7f532e48cf89d388b21b +size 66895 diff --git a/marked/Rel-11/23_series/23284/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg b/marked/Rel-11/23_series/23284/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e301a8446e566f11d3847542e1d6a3ede849968f --- /dev/null +++ b/marked/Rel-11/23_series/23284/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b02e1235c08186e61b1b969e0cefead294b19d153d2cca0104e0f5dd5203a8f8 +size 48696 diff --git a/marked/Rel-11/23_series/23284/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/marked/Rel-11/23_series/23284/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..035c795d2a0d77cc1507646574e0c89e0c04fd76 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/7722d62e33dcc894cc8555e9474c5606_img.jpg b/marked/Rel-11/23_series/23284/7722d62e33dcc894cc8555e9474c5606_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0cc4223073b4353ac042591818d3c0690ae1adbe --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-11/23_series/23284/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc6f79d4ba14972a388cbbecdcc68439b09f3f5f --- /dev/null +++ b/marked/Rel-11/23_series/23284/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e898cddd2aeb898df2680d9140a15084d19ddc740c28ef18eac188d9a8f8a209 +size 151318 diff --git a/marked/Rel-11/23_series/23284/79aaab5889060cf8264226764a109cdb_img.jpg b/marked/Rel-11/23_series/23284/79aaab5889060cf8264226764a109cdb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa3c7a6316d37e25a5e3a303dd8156d414be3804 --- /dev/null +++ b/marked/Rel-11/23_series/23284/79aaab5889060cf8264226764a109cdb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8ccdd4f418e1b9a7c80f6c28833ebe4d35c24c3c0d4475ab3f16be0279d016a +size 51291 diff --git a/marked/Rel-11/23_series/23284/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-11/23_series/23284/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7720bedb7bbd0fcbf8ef6f2730707bdca1914794 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-11/23_series/23284/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0324ce068f6b350676f3bba8ae14274a1bdbcfd --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/7e74ac663f3e644b589ed28f5fd29398_img.jpg b/marked/Rel-11/23_series/23284/7e74ac663f3e644b589ed28f5fd29398_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f03e20e2d6daa33f558a3fc1b7ff643416162701 --- /dev/null +++ b/marked/Rel-11/23_series/23284/7e74ac663f3e644b589ed28f5fd29398_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d16b99833f1593b52a174416c67c2bb5722de7a2777f991d51867fdb8794eebf +size 73884 diff --git a/marked/Rel-11/23_series/23284/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-11/23_series/23284/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..634e0aa2b4348d73bbcfc3abd3734507b6f6b371 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-11/23_series/23284/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f5be78686aab40d02406a650407dc4b6040edf8 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/820515db47ded68f5e0b625f4ec7d2c1_img.jpg b/marked/Rel-11/23_series/23284/820515db47ded68f5e0b625f4ec7d2c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b879ab28d0cb10948713fa6eb7fa6041fb1ce073 --- /dev/null +++ b/marked/Rel-11/23_series/23284/820515db47ded68f5e0b625f4ec7d2c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54c3a4f0e2a774d4303cb17746c246d2d7b363fde76344ec95c52bce248d7b84 +size 238579 diff --git a/marked/Rel-11/23_series/23284/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg b/marked/Rel-11/23_series/23284/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b0c68323d7d2a8edbfb5d66ae6f8fe1bb9b68fc --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/8658cfab6a458b4a80ab2e384c61ff89_img.jpg b/marked/Rel-11/23_series/23284/8658cfab6a458b4a80ab2e384c61ff89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c92a245cec6a0964c49cb1ef411c1c9a933581e --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/88b0f3f4393228e9ea4d6542aef7c399_img.jpg b/marked/Rel-11/23_series/23284/88b0f3f4393228e9ea4d6542aef7c399_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..048e9ae3285b5c02ef7ae62248d0a87e1485b127 --- /dev/null +++ b/marked/Rel-11/23_series/23284/88b0f3f4393228e9ea4d6542aef7c399_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc91b96d6beb60078e7fb48c352ab59793294d037be91d3537579be97d68e8c3 +size 46462 diff --git a/marked/Rel-11/23_series/23284/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-11/23_series/23284/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a327ed2ccfee2f96e58d9e30631c7bc1d23141a2 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-11/23_series/23284/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f611d815827a315fee665f3b54a57dc72dc3220 --- /dev/null +++ b/marked/Rel-11/23_series/23284/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bce8988a9e2b3c047639772ed3d560ec7ff7d6822ff04cc63f39c49a87df6bd +size 57075 diff --git a/marked/Rel-11/23_series/23284/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-11/23_series/23284/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51cfd60ffeb8ebd5d86c7b396a9fd523a1aa3f91 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/933ecd14c858bf3fc919222d8e357bc8_img.jpg b/marked/Rel-11/23_series/23284/933ecd14c858bf3fc919222d8e357bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33f85e7c7eef51c91730818e93656f7bfafde33d --- /dev/null +++ b/marked/Rel-11/23_series/23284/933ecd14c858bf3fc919222d8e357bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:912fe42809531051ac20adca3f51b0b7a83d450a59b0b3b0b83315b49f7e5dab +size 47133 diff --git a/marked/Rel-11/23_series/23284/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-11/23_series/23284/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b12a408e25ace2c8fc43b9eb6756e6e155927ae4 --- /dev/null +++ b/marked/Rel-11/23_series/23284/997233d405f0d4b89ddeb7683e047f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78bd9786866f5f5367b8b8fc189a5738efe8b18e5de95e76a05e3039bec55964 +size 195057 diff --git a/marked/Rel-11/23_series/23284/99e9a4791d2e5bb5afa1bb884652d4db_img.jpg b/marked/Rel-11/23_series/23284/99e9a4791d2e5bb5afa1bb884652d4db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90d31de441964d32c2ff11e654c50cec1f0d70fc --- /dev/null +++ b/marked/Rel-11/23_series/23284/99e9a4791d2e5bb5afa1bb884652d4db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6b811d24c62e895f1b74e0dacb9b6b2ab3f7ec5ab0243dae30bcd3f76bdf169 +size 98140 diff --git a/marked/Rel-11/23_series/23284/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-11/23_series/23284/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f3ca8a3c927d0b8479d84877559562e21eb85bb --- /dev/null +++ b/marked/Rel-11/23_series/23284/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22fe3b98bae86bac9da72277849c4ca653c21120c29e4bf878cec021f3dcb716 +size 163009 diff --git a/marked/Rel-11/23_series/23284/9c45844d796e85ae05505870a54e4eb4_img.jpg b/marked/Rel-11/23_series/23284/9c45844d796e85ae05505870a54e4eb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9babc0c61ec44854b0a423acf5f2b80479b3a3f8 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-11/23_series/23284/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..637bd7375965db6a115fa6df95fe5b87a7f13c04 --- /dev/null +++ b/marked/Rel-11/23_series/23284/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1222c626515f90c8d4d49daf458b474c41615d0be37f159f8bb76cd30094f7cf +size 70538 diff --git a/marked/Rel-11/23_series/23284/9ed248b025d766251d58be10b01a1cc0_img.jpg b/marked/Rel-11/23_series/23284/9ed248b025d766251d58be10b01a1cc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42256b8247ba845661944719a4a018ca19556dd4 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/9f51a76cae7309a296cbc6997941eb3f_img.jpg b/marked/Rel-11/23_series/23284/9f51a76cae7309a296cbc6997941eb3f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..174710edf47fe208d66cb2011d558114d75416ad --- /dev/null +++ b/marked/Rel-11/23_series/23284/9f51a76cae7309a296cbc6997941eb3f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05f5d974ad8d33aa39e1755710a1c5b39dc521e204a6f9183a1fc3e2449ae726 +size 78293 diff --git a/marked/Rel-11/23_series/23284/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-11/23_series/23284/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6afcc6e903c67a0fc8974b0b1636a1eb38170490 --- /dev/null +++ b/marked/Rel-11/23_series/23284/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c9e2019603bd38e9bc03d1a5467860bd1e8544aae4e5fe2d86613540b682731 +size 76063 diff --git a/marked/Rel-11/23_series/23284/9f862801bce82634d3b5a1e0a195a799_img.jpg b/marked/Rel-11/23_series/23284/9f862801bce82634d3b5a1e0a195a799_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e44e14b0ece1762f90e78859fc8bec6dd8b2f4b --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/marked/Rel-11/23_series/23284/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca7519f019e6412bdaaed0d68f2c9e1f825e60c1 --- /dev/null +++ b/marked/Rel-11/23_series/23284/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e23946a5067d4d687910121319b3f2ccc6485e4b232977d8121cc541a323397a +size 158784 diff --git a/marked/Rel-11/23_series/23284/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-11/23_series/23284/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04a61c6e113418e5c3e459fcd1b5be37257145d8 --- /dev/null +++ b/marked/Rel-11/23_series/23284/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bac8f479099cb5e241cb91eeed102a13368bfc0e3933f5da1d212ce5b6449832 +size 218432 diff --git a/marked/Rel-11/23_series/23284/a5184899f915014fa38608754efcc9c7_img.jpg b/marked/Rel-11/23_series/23284/a5184899f915014fa38608754efcc9c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83ac41499cff7f3fae8c37259a5ccd376e525e86 --- /dev/null +++ b/marked/Rel-11/23_series/23284/a5184899f915014fa38608754efcc9c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:915fdcfe672e1f39f278f515ef2427eb1650f5f03ffd8989829c8a5cb4ee9333 +size 61425 diff --git a/marked/Rel-11/23_series/23284/aa6e28822419dba9f22129fee66c9c4c_img.jpg b/marked/Rel-11/23_series/23284/aa6e28822419dba9f22129fee66c9c4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0aee9e69fa1933d3e209af992519ecef4a070a6 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/aa81b9b80bd1e3d723922b3a033564a2_img.jpg b/marked/Rel-11/23_series/23284/aa81b9b80bd1e3d723922b3a033564a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1575d43b011e1d28b0347acb7c35e3e096a4650 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/ad555483986d7170a46ce72d164b5bc8_img.jpg b/marked/Rel-11/23_series/23284/ad555483986d7170a46ce72d164b5bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..249f23a59d2ac5623256d71181a10ac82f086545 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/aeb2a26a07219661191294dba528067a_img.jpg b/marked/Rel-11/23_series/23284/aeb2a26a07219661191294dba528067a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0e90b477db1d322ea03ba5fc04d647aa1f36b62 --- /dev/null +++ b/marked/Rel-11/23_series/23284/aeb2a26a07219661191294dba528067a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0345064d5c253ef6e9cacd758b59b6b1e2b972e8f1e5f115e4bcc23d93e2fab8 +size 190327 diff --git a/marked/Rel-11/23_series/23284/b033fab424e6df728345cfa04df83fcc_img.jpg b/marked/Rel-11/23_series/23284/b033fab424e6df728345cfa04df83fcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..641855ea7303b6702d1a80485bd3bbd1535cc857 --- /dev/null +++ b/marked/Rel-11/23_series/23284/b033fab424e6df728345cfa04df83fcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a59dd75c4a0697e22bca07fd5d007755dc4ade926103f4de674add7ef572af78 +size 148398 diff --git a/marked/Rel-11/23_series/23284/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-11/23_series/23284/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9730d6fc052ffdcbc3a71a0b3accbc0513a1889 --- /dev/null +++ b/marked/Rel-11/23_series/23284/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86a826b5fdc8c0d6ab952dc68cacdeb703f95a114ecebcfa3973841ecd6f19c7 +size 149990 diff --git a/marked/Rel-11/23_series/23284/b63f41ca262d8ce9ef8affb62607f32b_img.jpg b/marked/Rel-11/23_series/23284/b63f41ca262d8ce9ef8affb62607f32b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c2b83bd0ca53bf0179cc6ae3ba567d059f873d7 --- /dev/null +++ b/marked/Rel-11/23_series/23284/b63f41ca262d8ce9ef8affb62607f32b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ba65a952a8d979d061da16eba93910c7d8b7aea382111133a6dbe001a30aa0d +size 67005 diff --git a/marked/Rel-11/23_series/23284/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/Rel-11/23_series/23284/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5522a0475badcb92e4f785dee85f1ade2f2d21f9 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-11/23_series/23284/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22c57a40e8c8a5da2c255822cde72d4de885cb9c --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/c07e21a8d65991db04263322f859c94f_img.jpg b/marked/Rel-11/23_series/23284/c07e21a8d65991db04263322f859c94f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c779634b807f1aee39edb92f9b304a053c5ea997 --- /dev/null +++ b/marked/Rel-11/23_series/23284/c07e21a8d65991db04263322f859c94f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa0f1e42bed725fc59599407acb1457710a5760b5b332d83e0b9df7fe2def28e +size 81326 diff --git a/marked/Rel-11/23_series/23284/cd48273072c5c3a23e11fde892d1b6b6_img.jpg b/marked/Rel-11/23_series/23284/cd48273072c5c3a23e11fde892d1b6b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56c9a464fab6b61c740c913ca68553b2b07b1877 --- /dev/null +++ b/marked/Rel-11/23_series/23284/cd48273072c5c3a23e11fde892d1b6b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4b3527fb31ee78103bf96006f4642210d08d4e7cff8805d8daf1ce0dd9d50d5 +size 38418 diff --git a/marked/Rel-11/23_series/23284/cf8bd014a50b7c69435e804f67f9617f_img.jpg b/marked/Rel-11/23_series/23284/cf8bd014a50b7c69435e804f67f9617f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26c43f26257430a2592ea0b592bd8300e5f5b584 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg b/marked/Rel-11/23_series/23284/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2227b01ef60ddf95aabace0c060192396aa162d --- /dev/null +++ b/marked/Rel-11/23_series/23284/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1f1af6fe49407fa97b02ad9a082e93ee814047a81a3a5c11b65859447c3c2b3 +size 183103 diff --git a/marked/Rel-11/23_series/23284/d6c377ae3e619ff992bd3647dbf43593_img.jpg b/marked/Rel-11/23_series/23284/d6c377ae3e619ff992bd3647dbf43593_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..082e2f494b4152ea040c62d2f0559e3766ade705 --- /dev/null +++ b/marked/Rel-11/23_series/23284/d6c377ae3e619ff992bd3647dbf43593_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af62b25dbea4f7a4537a9aa6d300b0f6476201b48bf1cfbe8f2ca7caceed0434 +size 42865 diff --git a/marked/Rel-11/23_series/23284/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg b/marked/Rel-11/23_series/23284/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f022fc0de1268de8567beb895e04306ef1bc1b0 --- /dev/null +++ b/marked/Rel-11/23_series/23284/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f76028581a05744e69ae332caf13ea21983eff7ca4b1b9275e380fb49fa581e +size 46175 diff --git a/marked/Rel-11/23_series/23284/dd380ccd5aca1151074fede04826f1a4_img.jpg b/marked/Rel-11/23_series/23284/dd380ccd5aca1151074fede04826f1a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67379f38ae0a9468e109d1ec29bf89c698dbaf24 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-11/23_series/23284/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bb35cd6e9a79b6b37f41725a42c85002b312d31 --- /dev/null +++ b/marked/Rel-11/23_series/23284/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7894e56de72abdf39b9a9cbb1d41648d1e58044090a78357f2d34a66db65caac +size 161521 diff --git a/marked/Rel-11/23_series/23284/ddee3e67e0dfc22e25188fa635a19558_img.jpg b/marked/Rel-11/23_series/23284/ddee3e67e0dfc22e25188fa635a19558_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9522a7f5d79b8101b569449867c8424beb6471f7 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-11/23_series/23284/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4626ceb24602a622bdeb907da7afb86807a4af0 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/e417ae35ab07134888be901c201d54cd_img.jpg b/marked/Rel-11/23_series/23284/e417ae35ab07134888be901c201d54cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..634513d8dad5f26b6feefd21ba582d6baa40e044 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/Rel-11/23_series/23284/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33f85e7c7eef51c91730818e93656f7bfafde33d --- /dev/null +++ b/marked/Rel-11/23_series/23284/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:912fe42809531051ac20adca3f51b0b7a83d450a59b0b3b0b83315b49f7e5dab +size 47133 diff --git a/marked/Rel-11/23_series/23284/e90b25c8d90cadc3f76c376701cf27ed_img.jpg b/marked/Rel-11/23_series/23284/e90b25c8d90cadc3f76c376701cf27ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a1692d15271a63f25ee21806c9bba1e621cce63 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-11/23_series/23284/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ecd702663c491060ef8536a80ed24ddbd96de6c --- /dev/null +++ b/marked/Rel-11/23_series/23284/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed6d983968cc3eefea13d728859f3b7f7a071682af5c4fc4523fda8bbfbaffa5 +size 133484 diff --git a/marked/Rel-11/23_series/23284/f2486d5031b55e42b300903a716b0a00_img.jpg b/marked/Rel-11/23_series/23284/f2486d5031b55e42b300903a716b0a00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d238890f1d01d6295a9b1fdf40bf756c949e3d41 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/f468e577645d646f5157ce3eefb4ed96_img.jpg b/marked/Rel-11/23_series/23284/f468e577645d646f5157ce3eefb4ed96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9041d681709da136256a24cfd806a981b801ea5f --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/f5deee2f3301ee351c4008283ffafbb3_img.jpg b/marked/Rel-11/23_series/23284/f5deee2f3301ee351c4008283ffafbb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..310547663692dc37c03fd91db3a1e50d0492f84b --- /dev/null +++ b/marked/Rel-11/23_series/23284/f5deee2f3301ee351c4008283ffafbb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ecfbd638ca76ed6614c8b88b3b1c9d4a3d9d73cf91e23531f3742c7aabe8e413 +size 116138 diff --git a/marked/Rel-11/23_series/23284/f61d0925551545b5938b3a4d1bbf63c3_img.jpg b/marked/Rel-11/23_series/23284/f61d0925551545b5938b3a4d1bbf63c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fb94deb9b9a9d31519469d46bc5511f88411d3b --- /dev/null +++ b/marked/Rel-11/23_series/23284/f61d0925551545b5938b3a4d1bbf63c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c36fc78a2d6bbe88acc7094468ff01723bcd270fb806ef7eef8beecd8623bfce +size 93662 diff --git a/marked/Rel-11/23_series/23284/f76f0f5dfff2511b51f6b875867c029f_img.jpg b/marked/Rel-11/23_series/23284/f76f0f5dfff2511b51f6b875867c029f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e4cfb99c8f656221961d35b1b8163cbf51037d0 --- /dev/null +++ b/marked/Rel-11/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-11/23_series/23284/f97535cdaa4fe017f4659512f4f78028_img.jpg b/marked/Rel-11/23_series/23284/f97535cdaa4fe017f4659512f4f78028_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ed3b446dce6304d1522ea5857482cba62894079 --- /dev/null +++ b/marked/Rel-11/23_series/23284/f97535cdaa4fe017f4659512f4f78028_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6171045e3bfc1aec4279ed0e56cb033f7d1bdff338bf0463b1086f4873f51f37 +size 228030 diff --git a/marked/Rel-11/23_series/23284/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-11/23_series/23284/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..abbc0883daff89242feef5e664548050d0236e2b --- /dev/null +++ b/marked/Rel-11/23_series/23284/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5058f87afbe0f117789b039ee14b2a1077628b93cb6b9f617bb59de1c7ad3c86 +size 125079 diff --git a/marked/Rel-11/23_series/23284/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-11/23_series/23284/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..309fd9e0ed180f77b06aa27773ba3dcdec25fc39 --- /dev/null +++ b/marked/Rel-11/23_series/23284/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81d9340aa8d0c6a2348a88a9180faace2b925e89c8380ab95681818c836bf782 +size 57263 diff --git a/marked/Rel-11/23_series/23284/ff7977984f2552f326b2089d7595fff3_img.jpg b/marked/Rel-11/23_series/23284/ff7977984f2552f326b2089d7595fff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09099aeb515029ca45c86edab8aa5a4ff3952fca --- /dev/null +++ b/marked/Rel-11/23_series/23284/ff7977984f2552f326b2089d7595fff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a655fbd1df1bf8a68fdc22bcf0532d17640c749cced3176b0292ab017a84bb51 +size 55420 diff --git a/marked/Rel-11/23_series/23284/raw.md b/marked/Rel-11/23_series/23284/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..443a0611ac5b2c00a391562047cb2b7f057a72ea --- /dev/null +++ b/marked/Rel-11/23_series/23284/raw.md @@ -0,0 +1,6039 @@ +# 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. + +--- + +# 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. These BTS units are connected to a BSC (Base Station Controller) with local switching capability via oAbis and tAbis interfaces. The BSC is connected to an originating MSC (oMSC) via oA and tA interfaces. The oMSC is connected to an intermediate MSC (iMSC) via oMGW and tMGW interfaces, which are further connected to a terminating MSC (tMSC) via Mc and Nc interfaces. 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. These BTS units are connected to a BSC (Base Station Controller) with local switching capability via oAbis and tAbis interfaces. The BSC is connected to an originating MSC (oMSC) via oA and tA interfaces. The oMSC is connected to an intermediate MSC (iMSC) via oMGW and tMGW interfaces, which are further connected to a terminating MSC (tMSC) via Mc and Nc interfaces. 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 server nodes, 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 signaling paths (LCLS-Negotiation Request/Response). Below them, three MGWs (MGW-o, MGW-i, MGW-t) are connected via a User Plane (connection). MGW-o is connected to UE-o via BSS-1/BSS-2. MGW-t is connected to UE-t. MGW-i is connected to MGW-o and MGW-t. The diagram shows data flows: DL send requested to apply a tone or announcement (red arrow), UL data requested from oUE (yellow arrow), Local DL data not blocked by BSS (yellow arrow), Local DL data blocked by BSS (red arrow with X), and UL data requested from tUE (cyan arrow).](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 signaling paths (LCLS-Negotiation Request/Response). Below them, three MGWs (MGW-o, MGW-i, MGW-t) are connected via a User Plane (connection). MGW-o is connected to UE-o via BSS-1/BSS-2. MGW-t is connected to UE-t. MGW-i is connected to MGW-o and MGW-t. The diagram shows data flows: DL send requested to apply a tone or announcement (red arrow), UL data requested from oUE (yellow arrow), Local DL data not blocked by BSS (yellow arrow), Local DL data blocked by BSS (red arrow with X), and UL data requested from tUE (cyan arrow). + +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 network architecture with oMSC-S, iMSC-S, and tMSC-S connected via control plane links (green dashed). Below them are oMGW, iMGW, and tMGW connected via user plane links (blue solid). On the left, a box contains oBSS/tBSS, tUE, and oUE. Control signalling is shown within the BSS and between the BSS and oMSC-S. User plane data is shown flowing from the oUE through the oBSS/tBSS, then through the oMGW, iMGW, and tMGW, and finally back to the oUE via a backward user plane link (blue dashed).](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 network architecture with oMSC-S, iMSC-S, and tMSC-S connected via control plane links (green dashed). Below them are oMGW, iMGW, and tMGW connected via user plane links (blue solid). On the left, a box contains oBSS/tBSS, tUE, and oUE. Control signalling is shown within the BSS and between the BSS and oMSC-S. User plane data is shown flowing from the oUE through the oBSS/tBSS, then through the oMGW, iMGW, and tMGW, and finally back to the oUE via a backward user plane link (blue dashed). + +Connection Model 1: After Alerting, Backward Through Connection + +![Diagram of Connection Model 2: After answer, Call is locally switched. This diagram shows the same network architecture as Model 1. However, after the call is answered, the user plane data is locally switched within the oBSS/tBSS. A red solid line labeled 'User Plane Data' shows the data flowing from the tUE through the oBSS/tBSS to the oUE. The path through the MGWs is labeled 'Non LCLS User Plane' and is shown as a dotted line.](3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg) + +Diagram of Connection Model 2: After answer, Call is locally switched. This diagram shows the same network architecture as Model 1. However, after the call is answered, the user plane data is locally switched within the oBSS/tBSS. A red solid line labeled 'User Plane Data' shows the data flowing from the tUE through the oBSS/tBSS to the oUE. The path through the MGWs is labeled 'Non LCLS User Plane' and is shown as a dotted line. + +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 the oUE replies with 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, which responds with a Paging response + CL3. The tMSC sends a SETUP message to the tUE, which confirms the call. The tMSC then sends an Add network side termination request to the tMGW, which responds with an ADD reply. The tMSC sends an APM message to the iMSC, which in turn sends an APM message to the oMSC. The oMSC sends an Add network side termination request to the iMGW, which responds with an ADD reply. Finally, the oMSC sends an APM message to the oMGW. A green bar labeled 'Network side Bearer Establishment' spans from the iMGW to the tMGW lifelines between steps 11a and 11b.](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 + oUE-->>oMSC: 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) + tMGW-->>tMSC: Context (tC) + tMSC->>iMSC: 10. APM [SC, ACL, LCLS-Negotiation Response, LCLS-Configuration-Preference] + iMSC-->>tMSC: Context (iC) + oMSC->>iMGW: 11a. Add network side termination: ADD request ($) / ADD reply (T6) + iMGW-->>oMSC: Context (iC) + Note right of iMGW: Network side Bearer Establishment + oMSC->>iMGW: 11b. Add network side termination: ADD request ($) / ADD reply (T5) + iMGW-->>oMSC: Context (iC) + oMSC->>oMGW: 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 the oUE replies with 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, which responds with a Paging response + CL3. The tMSC sends a SETUP message to the tUE, which confirms the call. The tMSC then sends an Add network side termination request to the tMGW, which responds with an ADD reply. The tMSC sends an APM message to the iMSC, which in turn sends an APM message to the oMSC. The oMSC sends an Add network side termination request to the iMGW, which responds with an ADD reply. Finally, the oMSC sends an APM message to the oMGW. A green bar labeled 'Network side Bearer Establishment' spans from the iMGW to the tMGW lifelines between steps 11a and 11b. + +**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 the interaction between these entities to establish a call, including bearer establishment, assignment requests, and alerting messages.](3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg) + +``` + +sequenceDiagram + participant oUE + participant oBSS + participant oMGW + participant oMSC + participant iMGW + participant iMSC + participant tMSC + participant tMGW + participant tBSS + participant tUE + + Note right of oMSC: 13a. Add network side termination: ADD request ($) / ADD reply (T2) Context (oC) + oMSC->>oMGW: 13a. Add network side termination: ADD request ($) / ADD reply (T2) Context (oC) + oMGW-->>oMSC: 13a. Add network side termination: ADD request ($) / ADD reply (T2) Context (oC) + Note right of oMSC: Network side Bearer Establishment + Note right of oMSC: 13b. Add access side termination: ADD request ($) / ADD reply (T1) Context (oC) + oMSC->>oMGW: 13b. Add access side termination: ADD request ($) / ADD reply (T1) Context (oC) + oMGW-->>oMSC: 13b. Add access side termination: ADD request ($) / ADD reply (T1) Context (oC) + Note right of oMSC: Access side Bearer Establishment + Note right of iMGW: NOTE: For AoTDM step 13b is: ADD (T1). + oMSC->>oBSS: 14. ASSIGNMENT REQUEST (GCR, LCLS-Configuration) + oBSS-->>oUE: 15. ASSIGNMENT COMPLETE (LCLS-BSS-Status = "call not possible to be locally switched") + oMSC->>iMSC: 16. COT + iMSC-->>tMSC: 17. COT Context (tC) + Note right of tMSC: 18. Add access side termination: ADD request ($) / ADD reply (T4) + tMSC->>tMGW: 18. Add access side termination: ADD request ($) / ADD reply (T4) + tMGW-->>tMSC: 18. Add access side termination: ADD request ($) / ADD reply (T4) + Note right of tMGW: NOTE: For AoTDM step 18 is: ADD (T4). + Note right of tMSC: 19a. If optional Intra-Network call detection and/or optional Intra-BSS call detection procedure/s supported perform check. + tMSC->>tBSS: 19b. ASSIGNMENT REQUEST (GCR, LCLS-Configuration) + tBSS-->>tUE: 20. ASSIGNMENT COMPLETE (LCLS-BSS-Status = "call not yet locally switched") + Note right of tBSS: Access Side Bearer Establishment + tBSS->>tUE: 21. tUE reports: Alerting + tMSC->>iMSC: 22a. ACM + iMSC-->>oMSC: 23. ACM Context (tC) + oMSC->>oBSS: 24. oMSC reports: Alerting + oBSS-->>oUE: Ring-back Tone + tMSC->>tMGW: 22b. MOD request: send Ring-back tone + +``` + +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 the interaction between these entities to establish a call, including bearer establishment, assignment requests, and alerting messages. + +**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. Lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, tUE. The diagram shows the interaction between these entities to establish a call, with a focus on Local Call Loop Start (LCLS) and bearer isolation. A large red arrow at the bottom indicates the call is locally switched.](6e15fc9ea763541c5913d26f85072ae1_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. The process involves several steps: + +- 25. tUE reports: Connect to tMSC. +- 25a. tMSC sends CONNECT ACK to tUE. +- 26. tMSC sends LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "connect") to tBSS. +- 27. tBSS sends LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status = "call not yet locally switched") to tMSC. +- 28. tMSC sends a MOD request to tMGW to stop tone and bothway through-connect. Context (tC) is passed. +- 29. tMSC sends an ANM message to iMSC with LCLS status "LCLS feasible but not yet connected". +- 30. iMSC sends an ANM message to oMSC with LCLS status "LCLS feasible but not yet connected". +- 31. oMSC sends a MOD request to oMGW for bothway through-connect. Context (oC) is passed. +- 32. oMSC reports: Connect to oBSS. +- 32a. oBSS sends CONNECT ACK to oMSC. +- 33. oMSC sends LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "connect") to oBSS. +- 34a. oBSS sends 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 a MOV request (T1)/ MOV reply to oMGW. Context (Cs) Isolate bearer termination. (Conditional: 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 a MOV request (T4)/ MOV reply to tMGW. Context (Cs) Isolate bearer termination. (Conditional: 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 an LCLS status update to iMSC: APM [LCLS-Status = "LCLS connected"]. +- 36. tMSC sends an LCLS status update to iMSC: APM [LCLS-Status = "LCLS connected"]. + +A large red arrow at the bottom, labeled "Call is locally Switched", spans from the oBSS to the tBSS, indicating the successful local switching of the call. + +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 the interaction between these entities to establish a call, with a focus on Local Call Loop Start (LCLS) and bearer isolation. 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 between the originating and terminating sides.](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** + +The sequence diagram illustrates the signaling flow for call establishment when the call is not locally switched. The participants are oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, and tUE. The process begins with step 19a, where the tMSC performs optional Intra-Network Call Detection and/or Intra-BSS Call Detection. This is followed by step 19b, an ASSIGNMENT REQUEST from the tMSC to the tBSS. Step 20 is an ASSIGNMENT COMPLETE from the tBSS to the tMSC. Step 21 is a report from the tUE. Step 22a is an ACM from the tMSC to the iMSC. Step 23 is an ACM from the iMSC to the oMSC. Step 24 is a report from the oMSC. A Ring-back Tone is sent from the oMSC to the oUE. Step 25a is a CONNECT from the tMSC to the tBSS. Step 25b is a CONNECT ACK from the tBSS to the tMSC. Step 26 is a MOD request from the tMSC to the tBSS. Step 27 is an ANM from the tMSC to the iMSC. Step 28 is an ANM from the iMSC to the oMSC. Step 29 is a MOD request from the oMSC to the oBSS. Step 30a is a CONNECT from the oBSS to the oMSC. Step 30b is a CONNECT ACK from the oMSC to the oBSS. Context (tC) and Context (oC) messages are also shown between the MSCs and MGWs. + +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 between the originating and terminating sides. + +**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 ($)/ADD reply (T2) to the oMGW, creating Context (oC). The oMSC sends an INVITE [SDP, IAM (GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference)] to the iMSC. The iMSC responds with 100 Trying. The oMSC sends another ADD request ($)/ADD reply (T6) to the iMGW, creating Context (iC). The iMSC sends an INVITE [SDP, IAM (GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference)] to the tMSC. The tMSC responds with 100 Trying, then pages the tUE. The tUE responds with a Paging response + CL3. The tMSC sends SETUP, then CALL CONFIRMED. The tMSC sends an ADD request ($)/ADD reply (T3) to the tMGW, creating Context (tC). The tMSC sends a 183 Session Progress [SDP, APM (LCLS-Negotiation Response, LCLS-Configuration-Preference)] to the iMSC. The iMSC responds with PRACK. The oMSC sends a MOD request (T6)/MOD reply (T6) to the iMGW, creating Context (iC). 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 (\$)/ADD reply (T2) to the oMGW, creating Context (oC). The oMSC sends an INVITE [SDP, IAM (GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference)] to the iMSC. The iMSC responds with 100 Trying. The oMSC sends another ADD request (\$)/ADD reply (T6) to the iMGW, creating Context (iC). The iMSC sends an INVITE [SDP, IAM (GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference)] to the tMSC. The tMSC responds with 100 Trying, then pages the tUE. The tUE responds with a Paging response + CL3. The tMSC sends SETUP, then CALL CONFIRMED. The tMSC sends an ADD request (\$)/ADD reply (T3) to the tMGW, creating Context (tC). The tMSC sends a 183 Session Progress [SDP, APM (LCLS-Negotiation Response, LCLS-Configuration-Preference)] to the iMSC. The iMSC responds with PRACK. The oMSC sends a MOD request (T6)/MOD reply (T6) to the iMGW, creating Context (iC). 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 (continuation of figure 6.3.4.1). The diagram shows interactions between oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, and tUE. Key steps include: 19. Add network side termination (ADD request ($)/ADD reply (T5)) with Context (iC); 20. 183 Session Progress [SDP, APM (LCLS-Negotiation Response, LCLS-Configuration-Preference)]; 21. PRACK; 22. Configure remote IP address & port (MOD request (T2)/MOD reply (T2)) with Context (oC); 23. Add access side termination (ADD request ($)/ADD reply (T1)) with Context (oC); NOTE: For AoTDM step 23 is: ADD (T1).; 24. 200 OK PRACK; 25. ASSIGNMENT REQUEST (GCR, LCLS-Configuration); 26. ASSIGNMENT COMPLETE (LCLS-BSS-Status = ](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +Sequence diagram for Basic Call Establishment when call is locally switched (continuation of figure 6.3.4.1). The diagram shows interactions between oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, and tUE. Key steps include: 19. Add network side termination (ADD request (\$)/ADD reply (T5)) with Context (iC); 20. 183 Session Progress [SDP, APM (LCLS-Negotiation Response, LCLS-Configuration-Preference)]; 21. PRACK; 22. Configure remote IP address & port (MOD request (T2)/MOD reply (T2)) with Context (oC); 23. Add access side termination (ADD request (\$)/ADD reply (T1)) with Context (oC); NOTE: For AoTDM step 23 is: ADD (T1).; 24. 200 OK PRACK; 25. ASSIGNMENT REQUEST (GCR, LCLS-Configuration); 26. ASSIGNMENT COMPLETE (LCLS-BSS-Status = + +**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 call establishment process between a UE (oUE) and a UE (tUE) via various network elements: oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, and tUE. The process involves several steps: + + +- 34. ASSIGNMENT REQUEST (GCR, LCLS-Configuration)**: tMSC to tBSS. +- 35a. ASSIGNMENT COMPLETE (LCLS-BSS-Status = "call not yet locally switched")**: tBSS to tMSC. +- 35b. LCLS\_NOTIFICATION (LCLS-BSS-Status = "call not yet locally switched")**: oBSS to oMSC. +- 36. ALERTING**: tUE to tMSC. +- 37. MOD request: send Ring-back tone**: tMSC to tMGW. Context (tC) is passed. +- 38. 180 Ringing [ACM]**: tMSC to iMSC. +- 39. PRACK**: iMSC to tMSC. +- 40. 180 Ringing [ACM]**: iMSC to iMGW. +- 41. PRACK**: iMGW to iMSC. +- 42. 200 OK PRACK**: tMSC to iMSC. +- 43. ALERTING**: oMSC to oUE. +- 44. 200 OK PRACK**: iMSC to iMGW. +- Ring-back Tone**: A continuous signal from tMGW to oUE. +- 45. CONNECT**: tMSC to tBSS. +- 46. CONNECT ACK**: tBSS to tUE. +- 47. LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "connect")**: tMSC to tBSS. +- 48. LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status = "call not yet locally switched")**: tBSS to tMSC. +- 49. MOD request: stop tone, bothway through-connect**: tMSC to tMGW. Context (tC) is passed. +- 50. 200 OK INVITE [ANM (LCLS status = "LCLS feasible but not yet connected")]**: tMSC to iMSC. +- 51. 200 OK INVITE [ANM (LCLS status = "LCLS feasible but not yet connected")]**: iMSC to iMGW. + +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. +- Call is locally Switched:** A large red double-headed arrow spans from oBSS to tBSS, indicating the successful local switching of the call. + +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 the 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 shows 12 steps of message exchange between these entities to establish a call and bearers.](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 right 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: 2. SETUP + oBSS-->>oMSC: 3. CALL PROCEEDING + oMSC-->>oUE: 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: 6. ASSIGNMENT REQUEST (GCR, LCLS-Configuration) + oMSC-->>oBSS: 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 the 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 shows 12 steps of message exchange between these entities to establish a call and bearers. + +**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. After 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, bearer establishment, and alerting messages.](a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg) + +The sequence diagram illustrates the signaling flow for call establishment. The lifelines are oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, and tUE. The sequence of messages is as follows: + +- 13. Paging tUE: tMSC to tBSS. +- Paging response + CL3: tBSS to tMSC. +- 14. SETUP: tMSC to tBSS. +- 15. Call Confirmed: tBSS to tMSC. +- 16. Add access side termination: ADD request (\$) / ADD reply (T3): tMSC to iMSC (Context (tC)). +- Network side Bearer Establishment** (green bar): iMGW to iMSC. +- 17. Add access side termination: ADD request (\$) / ADD reply (T4): iMSC to tMSC (Context (tC)). +- 18. If optional Intra-Network call detection and/or optional Intra-BSS call detection procedure/s supported perform check. (dashed box): iMSC to iMSC. +- 19. ASSIGNMENT REQUEST (GCR, LCLS-Configuration): tMSC to tBSS. +- 20. ASSIGNMENT COMPLETE (LCLS-BSS-Status = "call not yet locally switched"): tBSS to tMSC. +- Access Side Bearer Establishment** (green bar): tBSS to tUE. +- 21. LCLS\_NOTIFICATION (LCLS-BSS-Status = "call not yet locally switched"): oBSS to oMSC. +- 22. tUE reports: Alerting: tUE to tMSC. +- 23. ACM [LCLS-Negotiation Response, LCLS-Configuration-Preference]: tMSC to iMSC. +- 24. MOD request: send Ring-back tone: tMSC to tBSS. +- 25. ACM [LCLS-Negotiation Response, LCLS-Configuration-Preference]: iMSC to oMSC (Context (tC)). +- 26. oMSC reports: Alerting: oMSC to oUE. +- Ring-back Tone: oMSC to oUE (blue line). +- 27. For succeeding signalling sequence see figure 6.3.2.3. (note box). + +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, bearer establishment, and alerting messages. + +**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) originates from the UE (tUE and oUE) through the oBSS/tBSS, then connects to the oMSC-S, iMSC-S, and tMSC-S. The user plane data (red solid line) originates from the UE (tUE and oUE) through the oBSS/tBSS, then connects to the oMGW (terminations T1 and T2), iMGW (terminations T3 and T4), and tMGW (terminations T5 and T6). The oMGW, iMGW, and tMGW are connected to the oMSC-S, iMSC-S, and tMSC-S respectively. The oMSC-S, iMSC-S, and tMSC-S are connected to the oBSS/tBSS. The oBSS/tBSS is connected to the UE (tUE and oUE). The oMGW, iMGW, and tMGW are connected to the oMSC-S, iMSC-S, and tMSC-S respectively. The oMSC-S, iMSC-S, and tMSC-S are connected to the oBSS/tBSS. The oBSS/tBSS is connected to the UE (tUE and oUE). + +**Connection Model 2: After LCLS Break** + +In this model, the control signalling (green dashed line) remains the same as in Model 1. However, the user plane data (red solid line) is rerouted. It originates from the UE (tUE and oUE) through the oBSS/tBSS, then connects to the oMGW (terminations T1 and T2), iMGW (terminations T3 and T4), and tMGW (terminations T5 and T6). The oMGW, iMGW, and tMGW are connected to the oMSC-S, iMSC-S, and tMSC-S respectively. The oMSC-S, iMSC-S, and tMSC-S are connected to the oBSS/tBSS. The oBSS/tBSS is connected to the UE (tUE and oUE). The oMGW, iMGW, and tMGW are connected to the oMSC-S, iMSC-S, and tMSC-S respectively. The oMSC-S, iMSC-S, and tMSC-S are connected to the oBSS/tBSS. The oBSS/tBSS is connected to the UE (tUE and oUE). + +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 a series of messages starting with '1. Release LCLS' from oMSC-S, followed by status change requests and acknowledgments between MSC servers and BSSs, and finally status updates. A red curved arrow at the top indicates 'Call is locally Switched' between oBSS and tBSS.](aeb2a26a07219661191294dba528067a_img.jpg) + +The sequence diagram illustrates the interaction 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 curved 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 iMSC-S. +- oMSC-S sends a **2. LCLS Status Change Request** [LCLS-Status-Change = "LCLS-Disconnection-Preparation"] to iMSC-S. +- iMSC-S transfers the request to tMSC-S via **3. LCLS Status Change Request** [LCLS-Status-Change = "LCLS-Disconnection-Preparation"]. +- tMSC-S sends **4. LCLS\_CONNECT\_CONTROL** (LCLS-Connection-Status-Control = "Release LCLS") to tBSS. +- tBSS responds with **5. LCLS\_CONNECT\_CONTROL\_ACK** (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration"). +- tMSC-S sends **6. LCLS Status Change Request Acknowledge** [LCLS-Status-Change = "LCLS-Disconnection-Preparation", Result Code="Status Change Req Accepted"] to iMSC-S. +- iMSC-S transfers the acknowledgment to oMSC-S via **7. LCLS Status Change Request Acknowledge** [LCLS-Status-Change = "LCLS-Disconnection-Preparation", Result Code="Status Change Req Accepted"]. +- oMSC-S sends **8. LCLS\_CONNECT\_CONTROL** (LCLS-Connection-Status-Control = "Release LCLS") to oBSS. +- oBSS responds with **9a. LCLS\_CONNECT\_CONTROL\_ACK** (LCLS-BSS-Status = "call is no longer locally switched"). +- tMSC-S sends **9b. LCLS\_NOTIFICATION** (LCLS-BSS-Status = "call is no longer locally switched") to tBSS. +- oMSC-S sends **10. LCLS Status Update** [LCLS-Status = "LCLS not connected"] to iMSC-S. +- iMSC-S transfers the update to tMSC-S via **11. LCLS Status Update** [LCLS-Status = "LCLS not connected"]. +- tMSC-S sends **12. LCLS Status Update** [LCLS-Status = "LCLS not connected"] to tBSS. + +A note indicates: "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 a series of messages starting with '1. Release LCLS' from oMSC-S, followed by status change requests and acknowledgments between MSC servers and BSSs, and finally status updates. A red curved arrow at the top indicates 'Call is locally Switched' between oBSS and tBSS. + +Figure 7.2.4.2.1: MSC Server initiated LCLS break + +1. The oMSC server determines that local switching should be disconnected. +2. 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". +3. The iMSC server transfers the LCLS Status Change Request message to the succeeding node. +4. The tMSC server sends to the tBSS the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "Release LCLS". +5. 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. +6. 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. +7. 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. A red double-headed arrow labeled 'Call is locally Switched' spans from oBSS to tBSS. Step 1: oBSS and tBSS both have a box '1. Locally switched call is no longer locally switched'. Step 2b: oBSS sends '2b. LCLS_NOTIFICATION (LCLS-BSS-Status = "call is no longer locally switched")' to oMSC-S. Step 2a: tBSS sends '2a. LCLS_NOTIFICATION (LCLS-BSS-Status = "call is no longer locally switched")' to tMSC-S. Step 3b: oMSC-S sends '3b. LCLS Status Update [LCLS-Status = "LCLS not connected"]' to iMSC-S. Step 3a: tMSC-S sends '3a. LCLS Status Update [LCLS-Status = "LCLS not connected"]' to iMSC-S. Step 4a: iMSC-S sends '4a. LCLS Status Update [LCLS-Status = "LCLS not connected"]' to oMSC-S. A note in the iMSC-S lifeline states: 'LCLS Status Update is not sent to the succeeding MSC server since the same info is already received from the succeeding MSC server.'](458fdbcb4015a4ee90bd84809afc4aac_img.jpg) + +Sequence diagram for BSS initiated, immediate LCLS break. Lifelines: oUE, oBSS, oMGW, oMSC-S, iMGW, iMSC-S, tMSC-S, tMGW, tBSS, tUE. A red double-headed arrow labeled 'Call is locally Switched' spans from oBSS to tBSS. Step 1: oBSS and tBSS both have a box '1. Locally switched call is no longer locally switched'. Step 2b: oBSS sends '2b. LCLS\_NOTIFICATION (LCLS-BSS-Status = "call is no longer locally switched")' to oMSC-S. Step 2a: tBSS sends '2a. LCLS\_NOTIFICATION (LCLS-BSS-Status = "call is no longer locally switched")' to tMSC-S. Step 3b: oMSC-S sends '3b. LCLS Status Update [LCLS-Status = "LCLS not connected"]' to iMSC-S. Step 3a: tMSC-S sends '3a. LCLS Status Update [LCLS-Status = "LCLS not connected"]' to iMSC-S. Step 4a: iMSC-S sends '4a. LCLS Status Update [LCLS-Status = "LCLS not connected"]' to oMSC-S. A note in the iMSC-S lifeline states: 'LCLS Status Update is not sent to the succeeding MSC server since the same info is already received from the succeeding MSC server.' + +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 the flow of LCLS messages between these entities, with a red arrow indicating 'Call is locally Switched' between oBSS and tBSS. A blue box at the bottom indicates 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 interaction for BSS initiated LCLS release. The lifelines are oUE, oBSS, oMGW, oMSC-S, iMGW, iMSC-S, tMSC-S, tMGW, tBSS, and tUE. A red arrow labeled 'Call is locally Switched' spans from oBSS to tBSS. The message sequence is as follows: + +- 1. oBSS sends 'Release LCLS' to oUE. +- 2a. oBSS sends 'LCLS\_NOTIFICATION (LCLS-Break-Request)' to oMSC-S. +- 2b. tBSS sends 'LCLS\_NOTIFICATION (LCLS-Break-Request)' to tMSC-S. +- 3a. oMSC-S sends 'LCLS Status Change Request [LCLS-Status-Change = "LCLS-Disconnection-Preparation"]' to iMSC-S. +- 3b. tMSC-S sends 'LCLS Status Change Request [LCLS-Status-Change = "LCLS-Disconnection-Preparation"]' to iMSC-S. +- 4a. iMSC-S sends 'LCLS Status Change Request [LCLS-Status-Change = "LCLS-Disconnection-Preparation"]' to oMSC-S. +- 4b. iMSC-S sends 'LCLS Status Change Request [LCLS-Status-Change = "LCLS-Disconnection-Preparation"]' to tMSC-S. +- 5a. tMSC-S sends 'LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "Release LCLS")' to tBSS. +- 5b. oMSC-S sends 'LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "Release LCLS")' to oBSS. +- 6a. tBSS sends 'LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration")' to tMSC-S. +- 6b. oBSS sends 'LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status = "call is no longer locally switched")' to oMSC-S. +- 7a. tMSC-S sends 'LCLS Status Change Request Acknowledge [LCLS-Status-Change = "LCLS-Disconnection-Preparation", Result Code="Status Change Req Accepted"]' to iMSC-S. +- 7b. oMSC-S sends 'LCLS Status Change Request Acknowledge [LCLS-Status-Change = "LCLS-Disconnection-Preparation", Result Code="Status Change Req Accepted"]' to iMSC-S. +- 8a. iMSC-S sends 'LCLS Status Change Request Acknowledge [LCLS-Status-Change = "LCLS-Disconnection-Preparation", Result Code="Status Change Req Accepted"]' to oMSC-S. +- 8b. iMSC-S sends 'LCLS Status Change Request Acknowledge [LCLS-Status-Change = "LCLS-Disconnection-Preparation", Result Code="Status Change Req Accepted"]' to tMSC-S. +- 9. oMSC-S sends 'LCLS Status Update [LCLS-Status = "LCLS not connected"]' to iMSC-S. +- 10. tMSC-S sends 'LCLS Status Update [LCLS-Status = "LCLS not connected"]' to iMSC-S. +- 11. tMSC-S sends 'LCLS Status Update [LCLS-Status = "LCLS not connected"]' to tBSS. + +A blue box at the bottom indicates: "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 the flow of LCLS messages between these entities, with a red arrow indicating 'Call is locally Switched' between oBSS and tBSS. A blue box at the bottom indicates 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 + +- 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. + - 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 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. + - 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. + - Initial state: Red double-headed arrow between oUE and tUE labeled 'Call is locally Switched'. + - Step 1: Internal action at iMSC-S labeled '1. Release LCLS'. + - Step 2a: 'LCLS Status Change Request [LCLS-Status-Change = ](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. + - Initial state: Red double-headed arrow between oUE and tUE labeled 'Call is locally Switched'. + - Step 1: Internal action at iMSC-S labeled '1. Release LCLS'. + - Step 2a: 'LCLS Status Change Request [LCLS-Status-Change = + +**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 oBSS 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. oMGW sends 'Context oC' to iMGW and 'Join Bearer Termination' to iMSC. 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 oBSS 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. oMGW sends 'Context oC' to iMGW and 'Join Bearer Termination' to iMSC. 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 showing Connection Model 1: Before LCLS Re-establishment. It illustrates the network architecture with oMSC-S, iMSC-S, and tMSC-S connected via control signalling (green dashed lines). User plane data (red solid lines) flows from tUE/oUE through oBSS/tBSS to oMGW, then through iMGW to tMGW. Bearers are terminated at oMGW (T1, T2), iMGW (T3, T4), and tMGW (T5, T6).](3e8e3bdb3d90f0856266d4eaf36abba1_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 (red solid line) + +Diagram showing Connection Model 1: Before LCLS Re-establishment. It illustrates the network architecture with oMSC-S, iMSC-S, and tMSC-S connected via control signalling (green dashed lines). User plane data (red solid lines) flows from tUE/oUE through oBSS/tBSS to oMGW, then through iMGW to tMGW. Bearers are terminated at oMGW (T1, T2), iMGW (T3, T4), and tMGW (T5, T6). + +Connection Model 1: Before LCLS Re-establishment + +![Diagram showing Connection Model 2: After LCLS Re-establishment. This model shows the state after re-establishment where the user plane data path is rerouted. The 'Non LCLS User Plane' (dotted line) is shown, and the 'User Plane Data' (red solid line) is rerouted back to the oBSS/tBSS from the tMGW.](e90b25c8d90cadc3f76c376701cf27ed_img.jpg) + +Diagram showing Connection Model 2: After LCLS Re-establishment. This model shows the state after re-establishment where the user plane data path is rerouted. The 'Non LCLS User Plane' (dotted line) is shown, and the 'User Plane Data' (red solid line) is rerouted back to the oBSS/tBSS from the tMGW. + +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, oMSC-S, iMSC-S, tMSC-S, 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) + +The sequence diagram illustrates the MSC server Initiated LCLS Re-establishment process. The lifelines are oUE, oBSS, oMSC-S, iMSC-S, tMSC-S, tBSS, and tUE. The process starts with the oMSC-S sending an LCLS Status Change Request to the iMSC-S. The iMSC-S then forwards this to the tMSC-S. The tMSC-S sends an LCLS Status Change Request Acknowledge to the iMSC-S and an LCLS-Connect-Control to the tBSS. The iMSC-S then sends an LCLS Status Change Request Acknowledge to the oMSC-S. The oMSC-S sends an LCLS-Connect-Control to the oBSS. A red arrow labeled 'Call is locally Switched' connects the oBSS and tBSS. The oBSS sends an LCLS-Connect-Control\_ACK to the oMSC-S. The tMSC-S sends an LCLS-Notification to the tBSS. Finally, both the oMSC-S and tMSC-S send LCLS status updates to their respective BSSs. + +``` + +sequenceDiagram + participant oUE + participant oBSS + participant oMSC-S + participant iMSC-S + participant tMSC-S + participant tBSS + participant tUE + + Note left of oBSS: 8. LCLS Re-establishment + + 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 right of oBSS: Call is locally Switched + oBSS->>oMSC-S: 9. LCLS-Connect-Control_ACK (LCLS-BSS-Status = "Call is Locally Switched with requested LCLS configuration") + tMSC-S->>tBSS: 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") + iMSC-S->>oMSC-S: 13. LCLS status update: (LCLS-Status = "LCLS connected") + +``` + +Sequence diagram for MSC server Initiated LCLS Re-establishment. Lifelines: oUE, oBSS, oMSC-S, iMSC-S, tMSC-S, 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. The diagram shows the interaction between oUE, oBSS, oMGW, oMSC-S, iMGW, iMSC-S, tMSC-S, tMGW, tBSS, and tUE. The process starts with the iMSC-S initiating the re-establishment. The sequence includes LCLS Status Change Requests, Acknowledges, LCLS_CONNECT_CONTROL messages, and LCLS Status Updates. A red curved arrow labeled 'Call is locally Switched' spans from the oBSS to the tBSS. A blue box at the bottom indicates that the LCLS Status Update indicating LCLS connected is received from the succeeding MSC server and the preceding MSC server.](cfc2672ccfdf7b47212ef2b8d72c0ff3_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 iMSC-S, tMSC-S: 1. Re-establish LCLS + iMSC-S->>oMSC-S: 2. LCLS Status Change Request +[LCLS-Status-Change = "LCLS-Connection-Preparation"] + iMSC-S->>tMSC-S: 3. LCLS Status Change Request +[LCLS-Status-Change = "LCLS-Connection-Preparation"] + oMSC-S->>iMSC-S: 4. LCLS Status Change Request Acknowledge +[LCLS-Status-Change = "LCLS-Connection-Preparation", +Result Code="Status Change Req Accepted"] + tMSC-S->>iMSC-S: 5. LCLS Status Change Request Acknowledge +[LCLS-Status-Change = "LCLS-Connection-Preparation", +Result Code="Status Change Req Accepted"] + oMSC-S->>oBSS: 6. LCLS_CONNECT_CONTROL +(LCLS-Connection-Status-Control = "connect") + oBSS->>oMSC-S: 7. LCLS_CONNECT_CONTROL_ACK +(LCLS-BSS-Status = "call is no longer locally switched") + tMSC-S->>tBSS: 8. LCLS_CONNECT_CONTROL +(LCLS-Connection-Status-Control = "connect") + tBSS->>tMSC-S: 9a. LCLS_CONNECT_CONTROL_ACK +(LCLS-BSS-Status = "Call is locally switched with requested LCLS configuration") + oBSS->>oMSC-S: 9b. LCLS_NOTIFICATION +(LCLS-BSS-Status = "call is locally switched with requested LCLS configuration") + + Note over oBSS, tBSS: Call is locally Switched + + oMSC-S->>iMSC-S: 11. LCLS Status update [LCLS-Status = "LCLS connected"] + tMSC-S->>iMSC-S: 10. LCLS Status update [LCLS-Status = "LCLS connected"] + + Note over iMSC-S: LCLS Status Update indicating LCLS connected +is received from the succeeding MSC server and +the preceding MSC server. + +``` + +Sequence diagram for Intermediate Node / GMSC Server Initiated LCLS Re-establishment. The diagram shows the interaction between oUE, oBSS, oMGW, oMSC-S, iMGW, iMSC-S, tMSC-S, tMGW, tBSS, and tUE. The process starts with the iMSC-S initiating the re-establishment. The sequence includes LCLS Status Change Requests, Acknowledges, LCLS\_CONNECT\_CONTROL messages, and LCLS Status Updates. A red curved arrow labeled 'Call is locally Switched' spans from the oBSS to the tBSS. A blue box at the bottom indicates that the LCLS Status Update indicating LCLS connected is received from the succeeding MSC server and the preceding MSC server. + +**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 lifelines for oUE, oBSS, oMGW, oMSC-S, iMSC-S, iMGW, tMSC-S, tMGW, tBSS, and tUE. A horizontal box indicates 'For preceding signaling sequences see figure 7.3.4.2.1 steps 1- 10'. Step 11a shows a MOV request (T1) / MOV reply with 'Context (Cs) Isolate bearer termination' between oMSC-S and oMGW. Step 11b is an 'LCLS status update: (LCLS-Status = "LCLS connected")' from oMSC-S to iMSC-S. Step 12 is an 'LCLS status update: (LCLS-Status = "LCLS connected")' from iMSC-S to tMSC-S. Step 13 is an 'LCLS status update: (LCLS-Status = "LCLS connected")' from tMSC-S to oMSC-S.](31ef15d175af5babdbf4d2fbac884c1b_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 + + Note over oUE, tUE: For preceding signaling sequences see figure 7.3.4.2.1 steps 1- 10 + oMSC-S->>oMGW: 11a. MOV request (T1) / MOV reply + Note right of oMGW: Context (Cs) +Isolate bearer termination + oMSC-S->>iMSC-S: 11b. LCLS status update: (LCLS-Status = "LCLS connected") + iMSC-S->>tMSC-S: 12. LCLS status update: (LCLS-Status = "LCLS connected") + tMSC-S->>oMSC-S: 13. LCLS status update: (LCLS-Status = "LCLS connected") + +``` + +Sequence diagram for MSC server Initiated LCLS Re-establishment, access side termination isolated in MGW. The diagram shows lifelines for oUE, oBSS, oMGW, oMSC-S, iMSC-S, iMGW, tMSC-S, tMGW, tBSS, and tUE. A horizontal box indicates 'For preceding signaling sequences see figure 7.3.4.2.1 steps 1- 10'. Step 11a shows a MOV request (T1) / MOV reply with 'Context (Cs) Isolate bearer termination' between oMSC-S and oMGW. Step 11b is an 'LCLS status update: (LCLS-Status = "LCLS connected")' from oMSC-S to iMSC-S. Step 12 is an 'LCLS status update: (LCLS-Status = "LCLS connected")' from iMSC-S to tMSC-S. Step 13 is an 'LCLS status update: (LCLS-Status = "LCLS connected")' from tMSC-S to oMSC-S. + +**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. Shows RNC, BSS-2, 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, and MGW-1 to MGW-2. Green dashed lines show control plane connections between MSCs and other nodes.](74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg) + +Before Handover + $T_S$ = Serving + $T_A$ = Anchor + +Diagram of Connection Model 1: Before Handover. Shows RNC, BSS-2, 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, and MGW-1 to MGW-2. Green dashed lines show control plane connections between MSCs and other nodes. + +**Connection Model 1: Before Handover** + +![Diagram of Connection Model 2: During Handover. Similar to Model 1, but now includes a Target BSS (BSS-2) and a new port T_T on MGW-1. The RNC is now connected to T_T. T_S is isolated. T_A is one-way connected to T_T.](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 now includes a Target BSS (BSS-2) and a new port T\_T on MGW-1. The RNC is now connected to T\_T. T\_S is isolated. T\_A is one-way connected to T\_T. + +**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. It shows two MSCs (MSC-1 S and MSC-2 S) connected to two MGWs (MGW-1 and MGW-2). MGW-1 is connected to BSS-2 and Target BSS. MGW-2 is connected to BSS-2. Solid lines represent active call legs, while dashed lines represent inactive or potential connections. A red line highlights the connection between Target BSS and MGW-1.](5801c19431e76330430e92a598cc7a16_img.jpg) + +The diagram illustrates a network model for Connection Model 3. At the top, two MSCs labeled 'MSC-1 S' and 'MSC-2 S' are shown. Below them, two MGWs labeled 'MGW-1' and 'MGW-2' are shown. MGW-1 has two ports labeled 'TT' and 'TA', and MGW-2 has two ports labeled 'T1' and 'T2'. On the left, there are two BSS units: 'BSS-2' and 'Target BSS'. Solid lines represent active call legs: from MSC-1 S to MGW-1, from MSC-2 S to MGW-2, from MGW-1 to BSS-2, and from MGW-2 to BSS-2. Dashed lines represent inactive or potential connections: from MSC-1 S to MSC-2 S, from MSC-1 S to BSS-2, from MSC-1 S to Target BSS, from MSC-2 S to BSS-2, from MSC-2 S to Target BSS, from MGW-1 to Target BSS, and from MGW-2 to Target BSS. A red line highlights the connection between Target BSS and MGW-1. + +Network model diagram for Connection Model 3. It shows two MSCs (MSC-1 S and MSC-2 S) connected to two MGWs (MGW-1 and MGW-2). MGW-1 is connected to BSS-2 and Target BSS. MGW-2 is connected to BSS-2. Solid lines represent active call legs, while dashed lines represent inactive or potential connections. A red line highlights the connection between Target BSS and MGW-1. + +**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: 4a. LCLS_NOTIFICATION (LCLS-BSS-Status: "Call not yet locally switched") + 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 + Note right of MSC-2 S: 4b. LCLS_CONNECT_CONTROL (LCLS-Connection-Status-Control = "Connect") + Note right of 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 + MSC-1 S->>RNC: 11. Context C1: SUB Ts + RNC->>MSC-1 S: 12. LCLS-Status-Update (LCLS-Status: "LCLS connected") + MSC-1 S->>MSC-2 S: 12. LCLS-Status-Update (LCLS-Status: "LCLS connected") + Note right of 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. Shows a sequence of nodes: RNC connected to MGW-1 (terminations Ts, T1), which connects to MGW-2 (T3, T4), which connects to Target MGW (T5, TT). Above them, MSC-1 S controls MGW-1, MSC-2 S controls MGW-2, and Target MSC S controls Target MGW. Control plane (green dashed) links the MSCs and RNC. User plane (black solid) links the MGWs. Blue lines connect MSCs to their respective MGWs.](d6c377ae3e619ff992bd3647dbf43593_img.jpg) + +Diagram of Connection Model 1: Before Handover. Shows a sequence of nodes: RNC connected to MGW-1 (terminations Ts, T1), which connects to MGW-2 (T3, T4), which connects to Target MGW (T5, TT). Above them, MSC-1 S controls MGW-1, MSC-2 S controls MGW-2, and Target MSC S controls Target MGW. Control plane (green dashed) links the MSCs and RNC. User plane (black solid) links the MGWs. Blue lines connect MSCs to their respective MGWs. + +**Connection Model 1: Before Handover** + +![Diagram of Connection Model 2: During Handover. Similar to Model 1, but MGW-1 now includes termination T2. The caption indicates T2 is isolated from Ts and T1 is one-way connected to T2. The green dashed control plane path now includes the Target BSS and BSS-2 nodes.](ff7977984f2552f326b2089d7595fff3_img.jpg) + +Diagram of Connection Model 2: During Handover. Similar to Model 1, but MGW-1 now includes termination T2. The caption indicates T2 is isolated from Ts and T1 is one-way connected to T2. The green dashed control plane path now includes the Target BSS and BSS-2 nodes. + +**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 data paths, while dashed lines represent signaling 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 data paths, while dashed lines represent signaling 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 showing the initial phase of Inter-MSC UMTS to GSM Handover establishing Local Switching. The diagram involves 11 steps between 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. Red text indicates LCLS-related messages.](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +UE-1 (oMS) is communicating with UE-2 (tMS) via the core network + +``` + +sequenceDiagram + participant UE-1 + participant RNC + 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 over UE-1, UE-2: UE-1 (oMS) is communicating with UE-2 (tMS) via the core network + + RNC->>MSC-1 S: 1. Relocation Required + MSC-1 S->>Target MSC-S: 2. MAP Prepare-Handover Request (target LAC, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference) + Target MSC-S->>Target MGW: 3a. Add request Access side TT reserve circuit, Connection Point + Target MGW->>Target MSC-S: 3b. Add reply TT + Target MSC-S->>Target BSS: 4. Handover Request (GCR, LCLS-Configuration, LCLS-Connection-Status-Control = "Connect") + Target BSS->>Target MSC-S: 5. HO Request Ack (LCLS-BSS-Status: "Call not yet locally switched") + Note right of Target BSS: IF call has been answered and MSC permits LCLS to be connected then update the Connection Status in BSS + Target MSC-S->>MSC-2 S: 5a. LCLS_NOTIFICATION (LCLS-BSS-Status: "Call not yet locally switched") + Target MSC-S->>MGW-1: 6a. MOD request TT, configure Connection Point, only AoIP + MGW-1->>Target MSC-S: 6b. MOD reply TT + Target MSC-S->>MSC-1 S: 7. MAP Prepare-Handover Response + MSC-1 S->>MGW-1: 8a. TopDescr ({*, T2, isolate}, {T1, T2 oneway}) + ADD request(T2) + MGW-1->>MSC-1 S: 8b. TopDescr() + ADD reply (T2) + Note right of Target BSS: 5b. LCLS_CONNECT_CONTROL (LCLS-Connection-Status-Control = "Connect") + Note right of Target BSS: 5c. LCLS_CONNECT_CONTROL_ACK (LCLS-BSS-Status: "Call not yet locally switched") + MSC-1 S->>Target MSC-S: 9. IAM (Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference), see NOTE 1, NOTE 2 + Target MSC-S->>Target MGW: 10a. Add request Network side T5 + Target MGW->>Target MSC-S: 10b. Add reply T5 + Target MSC-S->>MSC-1 S: 11. APM (SC, SCL, LCLS-Negotiation Response, LCLS-Configuration-Preference), see NOTE 1 + +``` + +Sequence diagram showing the initial phase of Inter-MSC UMTS to GSM Handover establishing Local Switching. The diagram involves 11 steps between 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. Red text indicates LCLS-related messages. + +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/BSS-2. UE-1's data path is shown in red, looping within the BSS. UE-2's data path is shown in black, going through the CN. Control signalling is shown in green dashed lines. MSC-S-1 and MSC-S-2 are connected to MGW-1 and MGW-2 respectively. MGW-1 has terminations T_S, T_A, and T_T. MGW-2 has terminations T_1 and T_2. The diagram is labeled 'Before Handover'.](1018d0db7bb02c169f646cb9cc244dc6_img.jpg) + +The diagram illustrates the network architecture for Intra-MSC GSM to UMTS Handover. On the left, two User Equipment (UE) units, UE-1 and UE-2, are connected to a Base Station Subsystem (BSS) containing BSS-1 and BSS-2. UE-1 is associated with BSS-1, and UE-2 with BSS-2. A red solid line represents the user plane data for UE-1, which is locally switched within the BSS. A black solid line represents the user plane data for UE-2, which passes through the Core Network (CN). Green dashed lines represent control plane signalling, connecting the BSS to MSC-S-1 and MSC-S-2. MSC-S-1 is connected to MGW-1, and MSC-S-2 is connected to MGW-2. MGW-1 has three bearer terminations: $T_S$ (towards BSS-1), $T_A$ (towards the CN), and $T_T$ (towards the Target RNC). MGW-2 has two bearer terminations: $T_1$ (towards the CN) and $T_2$ (towards BSS-2). A dotted line labeled 'Non-LCLS User Plane' connects the CN to the MGWs. The diagram is labeled 'Before Handover'. + +Diagram of Connection Model 1: The call is locally switched. It shows UE-1 and UE-2 connected to BSS-1/BSS-2. UE-1's data path is shown in red, looping within the BSS. UE-2's data path is shown in black, going through the CN. Control signalling is shown in green dashed lines. MSC-S-1 and MSC-S-2 are connected to MGW-1 and MGW-2 respectively. MGW-1 has terminations T\_S, T\_A, and T\_T. MGW-2 has terminations T\_1 and T\_2. The diagram is labeled 'Before Handover'. + +Connection Model 1: The call is locally switched + +![Diagram of Connection Model 1 showing UE-1 and UE-2 connected to BSS-1/BSS-2, which are connected to Target RNC. Control signaling flows from Target RNC through MGW-1 (Ts, TA, TT) to MSC-S-1 and MSC-S-2. User plane data flows from Target RNC through MGW-1 (TA, TT) to MGW-2 (T1, T2) and then to the core network.](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 1 showing UE-1 and UE-2 connected to BSS-1/BSS-2, which are connected to Target RNC. Control signaling flows from Target RNC through MGW-1 (Ts, TA, TT) to MSC-S-1 and MSC-S-2. User plane data flows from Target RNC through MGW-1 (TA, TT) to MGW-2 (T1, T2) and then to the core network. + +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 2 showing UE-1 and UE-2 connected to BSS-1/BSS-2, which are connected to Target RNC. Control signaling flows from Target RNC through MGW-1 (TA, TT) to MSC-S-1 and MSC-S-2. User plane data flows from Target RNC through MGW-1 (TA, TT) to MGW-2 (T1, T2) and then to the core network. UE-2 is shown bicasting data to both BSS-1 and BSS-2.](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 2 showing UE-1 and UE-2 connected to BSS-1/BSS-2, which are connected to Target RNC. Control signaling flows from Target RNC through MGW-1 (TA, TT) to MSC-S-1 and MSC-S-2. User plane data flows from Target RNC through MGW-1 (TA, TT) to MGW-2 (T1, T2) and then to the core network. UE-2 is shown bicasting data to both BSS-1 and BSS-2. + +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, which is connected to MSC-S-1. UE-1 is connected to Target RNC, which is connected to MGW-1 (with Terminations TT and TA). MGW-1 is connected to MGW-2 (with Terminations T1 and T2). MSC-S-1 and MSC-S-2 are connected. Control Signalling is shown as green dashed lines. User Plane Data is shown as a solid black line path.](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +Control Signalling + +MSC-S-1      MSC-S-2 + +UE-2 — BSS-1/BSS-2      User Plane Data + +UE-1 — Target RNC      TT MGW-1 TA      T1 MGW-2 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, which is connected to MSC-S-1. UE-1 is connected to Target RNC, which is connected to MGW-1 (with Terminations TT and TA). MGW-1 is connected to MGW-2 (with Terminations T1 and T2). MSC-S-1 and MSC-S-2 are connected. Control Signalling is shown as green dashed lines. User Plane Data is shown as a solid black line path. + +**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. Lifelines: UE-1, BSS-1, MGW-1, MSC-S-1, Target RNC, MSC-S-2, MGW-2, BSS-2, UE-2. The diagram shows signaling steps 1-14, with red arrows indicating locally switched user plane and black arrows indicating normally switched user plane. A 'Break local switching' box is present near UE-1.](f97535cdaa4fe017f4659512f4f78028_img.jpg) + +The sequence diagram illustrates the signaling flow for a GSM to UMTS handover that breaks local switching. The lifelines 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:** Indicated by red double-headed arrows between UE-1 and BSS-1, and between BSS-1 and BSS-2. + +**Normally Switched User Plane:** Indicated by black double-headed arrows between UE-1 and Target RNC, and between Target RNC and UE-2. + +**Signaling Steps:** + +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) +6. HO CMD (MSC-S-1 to BSS-1) +- 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) +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) +- 8a. LCLS-Status-Change-Request (LCLS-Status-Change: "IndicateDLdataAfterHandover") (MSC-S-1 to MSC-S-2) +- 8b. LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "DLDataAtHandover") (MSC-S-2 to BSS-2) +9. Iu Relocation Complete (Target RNC to MSC-S-1) +- 8c. LCLS\_CONNECT\_CONTROL Ack (LCLS-BSS-Status "the call is locally switched with requested LCLS configuration") (BSS-2 to MSC-S-2) +- 8d. LCLS-Status-Change-Request Ack (LCLS-Status-Change: "IndicateDLdataAfterHandover", Result Code="Status Change Req Accepted") (MSC-S-2 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 box labeled "Break local switching" is located near UE-1, indicating the point where local switching is terminated. + +Sequence diagram for GSM to UMTS handover that breaks Local Switching. Lifelines: UE-1, BSS-1, MGW-1, MSC-S-1, Target RNC, MSC-S-2, MGW-2, BSS-2, UE-2. The diagram shows signaling steps 1-14, with red arrows indicating locally switched user plane and black arrows indicating normally switched user plane. A 'Break local switching' box is present near UE-1. + +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 signaling steps for a handover that ends local switching, including messages like HO Required, Context C1: ADD Termination for Target RNC, Iu Relocation Request, and various LCLS status changes. A red arrow at the top indicates the 'Locally Switched User Plane in the BSS', and a black arrow at the bottom indicates the 'Normally Switched User Plane'.](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. The process begins with BSS-1 sending an 'HO Required' message to MSC-S-1. MSC-S-1 then sends a 'Context C1: ADD Termination for Target RNC (TT) – bothway; MOD Ts Isolate' message to MGW-1. MGW-1 responds with '3. Iu Relocation Request' to Target RNC, which returns '4. Iu Relocation Request Ack'. MSC-S-1 then sends '5. LCLS-Status-Change-Request (LCLS-Status-Change: "LCLS-disconnection-preparationForHandover")' to MSC-S-2. MSC-S-2 responds with '5a. LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "BicastaHandover")' and '5b. LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration")'. MSC-S-1 sends '6. HO CMD' to BSS-1, which triggers 'Break local switching'. BSS-1 sends '7. LCLS Status Change Request Acknowledge (LCLS-Status-Change = "LCLS-Disconnection-PreparationForHandover", Result Code="Status Change Req Accepted")' to MSC-S-1. Target RNC sends '8. Iu Relocation Detect' to MSC-S-1, which returns '9. Iu Relocation Complete'. MSC-S-1 sends '10. Clear Command' to BSS-1, which returns '12. Clear Complete'. MSC-S-1 sends '13. Context C1: SUB Ts' to MGW-1, which returns '14. LCLS-Status-Update (LCLS-Status: "LCLS not connected")' to MSC-S-2. The diagram also shows the 'Locally Switched User Plane in the BSS' (red arrow) and the 'Normally Switched User Plane' (black arrow). + +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 signaling steps for a handover that ends local switching, including messages like HO Required, Context C1: ADD Termination for Target RNC, Iu Relocation Request, and various LCLS status changes. A red arrow at the top indicates the 'Locally Switched User Plane in the BSS', and a black arrow at the bottom indicates the 'Normally Switched User Plane'. + +**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 "BicatatHandover", 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 $T_2$ in MGW-2 is used for the bearer towards BSS-2, which is not affected by this handover. Bearer termination $T_S$ in MGW-1 is used for the bearer towards BSS-1 and the bearer terminations $T_A$ and $T_3$ in MGW-1, $T_1$ in MGW-2 and $T_4$ in Target-MGW are used for the bearer towards the succeeding/preceding MGW. Bearer termination $T_T$ 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. The diagram shows a network architecture with two MSC Servers (MSC-1 S and MSC-2 S) and two Media Gateways (MGW-1 and MGW-2). A Base Station (BSS-1/BSS-2) is connected to MSC-1 S. A User Equipment (UE) is connected to the BSS. The diagram illustrates the user plane and control plane paths. The user plane path (solid red line) goes from the UE through the BSS to MGW-1, then through MGW-2 to the UE. The control plane path (dashed green line) goes from the UE through the BSS to MSC-1 S, then through MSC-2 S to MGW-2, and finally to the UE. The diagram also shows various bearer terminations: T_S and T_A in MGW-1, and T_1, T_2, and T_3 in MGW-2.](5dadcfbae18c4b3f91ea3a5e84d0a47a_img.jpg) + +Diagram of Connection Model 1: Before handover, Local Switching is established. The diagram shows a network architecture with two MSC Servers (MSC-1 S and MSC-2 S) and two Media Gateways (MGW-1 and MGW-2). A Base Station (BSS-1/BSS-2) is connected to MSC-1 S. A User Equipment (UE) is connected to the BSS. The diagram illustrates the user plane and control plane paths. The user plane path (solid red line) goes from the UE through the BSS to MGW-1, then through MGW-2 to the UE. The control plane path (dashed green line) goes from the UE through the BSS to MSC-1 S, then through MSC-2 S to MGW-2, and finally to the UE. The diagram also shows various bearer terminations: T\_S and T\_A in MGW-1, and T\_1, T\_2, and T\_3 in MGW-2. + +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 encloses the MSCs and MGWs, while a dashed blue line encloses the MGWs and Target RNC. + +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 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 bidirectional connection between BSS-2/BSS-1 and MGW-1. A solid black line also connects the Target RNC to MGW-1. A solid black line connects MGW-1 to MGW-2. A solid black line connects MGW-2 to the Target MGW. A solid black line connects the Target MGW back to MGW-1. A dashed blue line connects MGW-1 and MGW-2. A dashed green line encloses the MSCs and MGWs, while a dashed blue line encloses the MGWs and Target RNC. + +Diagram of Connection Model 3 showing network components and their connections when UE-1 is not yet detected in 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 T7. A red line indicates a specific connection path within the BSS-2/BSS-1 unit.](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 T7. A red line indicates a specific connection path within the BSS-2/BSS-1 unit. + +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. A red line is shown within the BSS-2/BSS-1 unit, and a blue dashed line connects the Target RNC to MGW-1. The caption notes that TA is both-way connected to T3.](64323b705244afc70bf77babdacb6ce5_img.jpg) + +Diagram of Connection Model 5 showing network architecture similar to Model 4, but with a different user plane routing. A red line is shown within the BSS-2/BSS-1 unit, and a blue dashed line connects the Target RNC to MGW-1. The caption notes that TA is both-way connected to T3. + +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 and MSC-2 S at the top, connected by a dashed green line. Below them are BSS-2 and Target RNC on the left, and MGW-1, MGW-2, and Target MGW on the right. Solid black lines represent data paths, while dashed green lines represent signaling paths. MGW-1 and MGW-2 have internal ports labeled T3, TA, T1, and T2. Target MGW has ports labeled T4 and T.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +Diagram of Connection Model 6: Handover completed, Ts termination was removed. The diagram shows a network architecture with MSC-1 S and MSC-2 S at the top, connected by a dashed green line. Below them are BSS-2 and Target RNC on the left, and MGW-1, MGW-2, and Target MGW on the right. Solid black lines represent data paths, while dashed green lines represent signaling paths. MGW-1 and MGW-2 have internal ports labeled T3, TA, T1, and T2. Target MGW has ports labeled T4 and T. + +**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 from MSC-1 S to MGW-1; 9b. TopDescr()+ADD.reply from MGW-1 to MSC-1 S; 10. LCLS Status Change Request Acknowledge from MSC-2 S to MSC-1 S; 11. IAM from MSC-1 S to Target MSC-S; 12a. Add request Network side T_4 from Target MSC-S to Target MGW; 12b. Add reply T_4 from Target MGW to Target MSC-S; 13. APM from Target MSC-S to MSC-1 S.](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +oMS is communicating with tMS via locally switched path in the BSS + +1. HO Required (target LAC) + +2. MAP Prepare-Handover Request (target LAC, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference) + +3a. Add request Access side $T_T$ + +3b. Add reply $T_T$ + +Prepare Bearer + +4. Iu Relocation Request + +5. Iu Relocation Ack + +6. MAP Prepare-Handover Response + +7. LCLS-Status-Change-Request (LCLS-Status-Change: "LCLS-Disconnection-PreparationForHandover"), see NOTE 1 + +8a. LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "BicastaHandover") + +8b. LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status = "Call is locally switched with requested LCLS configuration") + +9a. TopDescr ({\*, $T_3$ , isolate}, { $T_A$ , $T_3$ , oneway}) + ADD.request( $T_3$ ) + +9b. TopDescr()+ADD.reply ( $T_3$ ) + +10. LCLS Status Change Request Acknowledge (LCLS-Status-Change = "LCLS-Disconnection-PreparationForHandover", Result Code = "Status Change Req Accepted") + +11. IAM (Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference), see NOTE 2, NOTE 3 + +12a. Add request Network side $T_4$ + +12b. Add reply $T_4$ + +13. APM (SC, SCL, LCLS-Negotiation Response, LCLS-Configuration-Preference), see NOTE 2 + +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 from MSC-1 S to MGW-1; 9b. TopDescr()+ADD.reply from MGW-1 to MSC-1 S; 10. LCLS Status Change Request Acknowledge from MSC-2 S to MSC-1 S; 11. IAM from MSC-1 S to Target MSC-S; 12a. Add request Network side T\_4 from Target MSC-S to Target MGW; 12b. Add reply T\_4 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. +- 3a, 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 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 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 'Break local switching' box is shown in 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 + Target MSC-S->>MSC-2 S: 24. LCLS NOTIFICATION (LCLS-BSS-Status: "Call is no longer locally switched") + MSC-1 S->>MSC-2 S: 25. LCLS Status Update: (LCLS-Status: "LCLS not connected"), see NOTE 5 + 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 'Break local switching' box is shown in 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 TS and set TT 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 (TS) 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 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: The call is locally switched. It shows two User Equipment (UE-1, UE-2) connected to a Base Station Subsystem (BSS-1/BSS-2). A red line represents the user plane data path within the BSS. A green dashed line represents the control signalling path, connecting 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. A dotted line represents the Non-LCLS User Plane path between MGW-1 and MGW-2. The diagram is labeled 'Before Handover'.](114902bbeea56bda01b64b43fad41920_img.jpg) + +**Before Handover** + +Components: UE-1, UE-2, BSS-1/BSS-2, MSC-S-1, MSC-S-2, MGW-1 (Ports TS, TA), MGW-2 (Ports T1, T2). + Path: User Plane Data (red) is local to BSS. Control Signalling (green dashed) connects BSS to MSC-S-1/2. Non-LCLS User Plane (dotted) connects MGW-1 and 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-1/BSS-2). A red line represents the user plane data path within the BSS. A green dashed line represents the control signalling path, connecting 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. A dotted line represents the Non-LCLS User Plane path between MGW-1 and MGW-2. 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. A black line represents the user plane data path, which now goes from the Target BSS through MGW-1 (specifically through its TA and TT ports) to MGW-2. A red line shows the user plane data path within BSS-1/BSS-2. A green dashed line shows the control signalling path. A legend defines: TS = Serving, TA = Anchor, TT = Target.](f2486d5031b55e42b300903a716b0a00_img.jpg) + +**During Handover** +TS = Serving +TA = Anchor +TT = Target + +Components: UE-1, UE-2, BSS-1/BSS-2, Target BSS, MSC-S-1, MSC-S-2, MGW-1 (Ports TS, TA, TT), MGW-2 (Ports T1, T2). + Path: User Plane Data (red) remains in BSS-1/2. A new User Plane Data path (black solid) connects Target BSS to MGW-1 (TT to TA) and then to MGW-2. + +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. A black line represents the user plane data path, which now goes from the Target BSS through MGW-1 (specifically through its TA and TT ports) to MGW-2. A red line shows the user plane data path within BSS-1/BSS-2. A green dashed line shows the control signalling path. 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 shows network nodes UE-1, UE-2, BSS-1/BSS-2, Target BSS, MSC-S-1, MSC-S-2, MGW-1, and MGW-2. Control signaling (green dashed lines) connects MSCs to BSSs. User Plane Data (thick black lines) flows between BSSs and MGWs. A red arrow indicates local user plane data within BSS-1/BSS-2. Terminations are labeled TS, TA, TT, T1, and T2.](1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg) + +Control Signalling + +MSC-S-1 MSC-S-2 + +UE-2 + +BSS-1/ +BSS-2 + +User Plane Data + +User Plane +Data + +TS TA T1 T2 + +UE-1 + +Target BSS + +TT + +MGW-1 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 shows network nodes UE-1, UE-2, BSS-1/BSS-2, Target BSS, MSC-S-1, MSC-S-2, MGW-1, and MGW-2. Control signaling (green dashed lines) connects MSCs to BSSs. User Plane Data (thick black lines) flows between BSSs and MGWs. A red arrow indicates local user plane data within BSS-1/BSS-2. Terminations are labeled TS, TA, TT, T1, and T2. + +**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. The diagram shows the same network nodes as Model 3. The User Plane Data path now goes from UE-2 through BSS-1/BSS-2 to MGW-1, and from UE-1 through Target BSS to MGW-1. The local user plane data path in BSS-1/BSS-2 and termination TS have been removed.](79aaab5889060cf8264226764a109cdb_img.jpg) + +Control Signalling + +MSC-S-1 MSC-S-2 + +UE-2 + +BSS-1/BSS-2 + +User Plane Data + +TT TA T1 T2 + +UE-1 + +Target BSS + +MGW-1 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. The diagram shows the same network nodes as Model 3. The User Plane Data path now goes from UE-2 through BSS-1/BSS-2 to MGW-1, and from UE-1 through Target BSS to MGW-1. The local user plane data path in BSS-1/BSS-2 and termination TS have been removed. + +**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 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 then sends a 7. LCLS Status Change Request Acknowledge to MSC-S-1, indicating LCLS-Disconnection-PreparationForHandover and a Result Code of "Status Change Req Accepted". MSC-S-1 sends an HO Detect to TargetBSS. TargetBSS then 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. MSC-S-1 sends a 10. Clear Command to BSS-1. BSS-1 then sends a 8d. LCLS-Status-Change-Request Ack to MSC-S-1, indicating IndicateDLdataAfterHandover and a Result Code of "Status Change Req Accepted". MSC-S-1 sends a 12. Clear Complete to BSS-1. BSS-1 then sends a 13. Context C1: SUB Ts to MSC-S-1. MSC-S-1 sends a 14. LCLS-Status-Update to MSC-S-2, indicating LCLS-Status: "LCLS not connected". MSC-S-2 then sends an 11. LCLS\_NOTIFICATION to MGW-2, indicating LCLS-BSS-Status = "Call is no longer locally switched". The diagram also shows the user plane switching from a locally switched state (indicated by red arrows) to a normally switched state (indicated by black arrows) after the handover. A box labeled "Break local switching" is shown near UE-1. + +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 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 ( $T_T$ ) from the termination to the Serving BSS ( $T_S$ ) and configures the Anchor termination ( $T_A$ ) one-way DL towards the Target BSS termination ( $T_T$ ). Termination to the Serving BSS ( $T_S$ ) is both-way connected to Anchor termination ( $T_A$ ) since it is also receiving UL user data from termination to the Serving BSS ( $T_S$ ). + +##### 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 UE-2. MSC-1 S and MSC-2 S are shown above the MGWs, connected to them. Control signalling is shown as green dashed lines, and user plane data as black solid lines.](37a6ab1d23efb9dc00cfae09d353b1da_img.jpg) + +The diagram illustrates the network architecture before a handover. UE-1 is connected to BSS-1. BSS-1 is connected to MGW-1 via a user plane link (black solid line). MGW-1 has two terminations: TS (connected to BSS-1) and TA (connected to MGW-2). MGW-2 has two terminations: T1 (connected to MGW-1) and T2 (connected to BSS-2). BSS-2 is labeled as 'Target BSS' and is connected to UE-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 connecting the UEs, BSSs, MGWs, and MSCs. User plane data is shown as black solid lines connecting the UEs, BSSs, and MGWs. + +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 UE-2. MSC-1 S and MSC-2 S are shown above the MGWs, connected to them. Control signalling is shown as green dashed lines, and user plane data as black solid lines. + +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 signaling and user plane data paths through MSC-1 S, MSC-2 S, MGW-1, and MGW-2.](aa81b9b80bd1e3d723922b3a033564a2_img.jpg) + +This diagram illustrates Connection Model 1. UE-2 is connected to BSS-2/Target BSS, which is connected to MSC-1 S. UE-1 is connected to BSS-1, which is connected to MGW-1. MSC-1 S and MSC-2 S are connected by a dashed green line representing Control Signalling. A solid black line represents User Plane Data, connecting UE-2 through BSS-2/Target BSS, MSC-1 S, MGW-1, MGW-2, and MSC-2 S. MGW-1 has interfaces TT, TA, and TS. MGW-2 has interfaces T1 and T2. + +Diagram of Connection Model 1 showing UE-1 and UE-2 connected to BSS-1 and BSS-2/Target BSS respectively, with control signaling and user plane data paths through MSC-1 S, MSC-2 S, MGW-1, and MGW-2. + +Connection Model 2: During handover, TS and TA are both-way connected, TT is isolated from TS + +![Diagram of Connection Model 2 during handover, showing UE-1 moving to Target BSS. A red arrow indicates user plane data flow from BSS-1 to Target BSS. A blue arrow points to UE-1.](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 arrow). UE-2 remains connected to BSS-2/Target BSS. Control signalling (dashed green) and user plane data (solid black) paths are shown. A red arrow indicates the user plane data flow from BSS-1 to Target BSS. MGW-1 interfaces TS and TA are both-way connected, while TT is isolated from TS. + +Diagram of Connection Model 2 during handover, showing UE-1 moving to Target BSS. A red arrow indicates user plane data flow from BSS-1 to Target BSS. A blue arrow points to UE-1. + +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 for inter-BSS handover. 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 a 'Control Signalling' path (green dashed line) and a 'User Plane Data' path (red solid line). MSC-1 S is connected to MGW-1, which is connected to the 'Non-LCLS User Plane' (dotted line). MSC-2 S is also connected to the 'Non-LCLS User Plane' and to MGW-2. The diagram illustrates the local switching of calls during a handover process.](88b0f3f4393228e9ea4d6542aef7c399_img.jpg) + +Diagram of Connection Model 4 for inter-BSS handover. 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 a 'Control Signalling' path (green dashed line) and a 'User Plane Data' path (red solid line). MSC-1 S is connected to MGW-1, which is connected to the 'Non-LCLS User Plane' (dotted line). MSC-2 S is also connected to the 'Non-LCLS User Plane' and to MGW-2. The diagram illustrates the local switching of calls during a handover process. + +**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 signaling steps for a handover that results in local switching within the BSS.](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +The diagram illustrates the sequence of messages for an Inter-BSS Handover that establishes Local Switching. The participants are UE-1, BSS-1, MGW-1, MSC-1 S, TargetBSS, MSC-2 S, MGW-2, BSS-2, and UE-2. The process starts with a 'Normally Switched User Plane' and transitions to a 'Locally Switched User Plane in the BSS'. + +Sequence of messages: + +- UE-1 sends 1. HO Required to BSS-1. +- BSS-1 sends 2a. TopDescr({TA, TS, isolate}, {TA, TT oneway})+ADD.request (TT) to MSC-1 S. +- MSC-1 S sends 2b. TopDescr()+ADD reply (TT) to BSS-1. +- BSS-1 sends 3. HO Request (GCR, LCLS-Configuration, LCLS-Connection-Status-Control = "Connect") to TargetBSS. +- TargetBSS sends 4. HO Request Ack (LCLS-BSS-Status: "Call not yet locally switched") to MSC-1 S. +- MSC-1 S sends 4a. LCLS\_NOTIFICATION (LCLS-BSS-Status: "Call not yet locally switched") to MSC-2 S. +- IF call has been answered and MSC permits LCLS to be connected then update the Connection Status in BSS (dashed box). +- MSC-2 S sends 4b. LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "Connect") to BSS-2. +- BSS-2 sends 4c. LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status: "Call not yet locally switched") to MSC-2 S. +- MSC-1 S sends 5a. MOD request TT, configure Connection Point, only AoIP to BSS-1. +- BSS-1 sends 5b. MOD reply TT to MSC-1 S. +- MSC-1 S sends 6. HO CMD to BSS-1. +- BSS-1 sends 7. HO Detect to TargetBSS. +- TargetBSS sends 8a. TopDescr, change flow direction ({TA, TS oneway}, {TA, TT bothway}) to MSC-1 S. +- MSC-1 S sends 8b. TopDescr reply to TargetBSS. +- TargetBSS sends 9. HO Complete (LCLS-BSS-Status: "call is locally switched with requested LCLS configuration") to MSC-1 S. +- MSC-1 S sends 10. LCLS\_NOTIFICATION (LCLS-BSS-Status: "call is locally switched with requested LCLS configuration") to MSC-2 S. +- MSC-1 S sends 11. Clear Command to BSS-1. +- BSS-1 sends 12. Clear Complete to MSC-1 S. +- MSC-1 S sends 13. Context C1: SUB TS to BSS-1. +- BSS-1 sends 14. LCLS-Status-Update (LCLS-Status: "LCLS connected") to MSC-1 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 signaling 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. +- 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". +- 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 ( $T_T$ ) from the termination to the Serving BSS-1 ( $T_S$ ) and to configure the Anchor termination ( $T_A$ ) one-way DL towards the Target BSS termination ( $T_T$ ). +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 $T_S$ 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 $T_2$ in MGW-2 is used for the bearer towards BSS-2, which is not affected by this handover. Bearer termination $T_S$ in MGW-1 is used for the bearer towards BSS-1 and the bearer terminations $T_A$ and $T_3$ in MGW-1, $T_1$ in MGW-2 and $T_4$ in Target-MGW are used for the bearer towards the succeeding/preceding MGW. Bearer termination $T_T$ 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 of Connection Model 1: Before handover, LCLS is established. The diagram shows a network architecture with two Base Station Subsystems (BSS-1 and BSS-2) on the left, two Mobile Switching Center Servers (MSC-1 S and MSC-2 S) in the top center, and two Media Gateway units (MGW-1 and MGW-2) in the bottom center. A red solid line represents the user plane link within BSS-1 to the UE. A black solid line represents the user plane link from BSS-1 through MSC-1 S and MGW-1 to the UE. A blue dashed line represents the user plane link path through the CN (MSC-1 S, MGW-1, MGW-2) to the UE. A black dashed line represents the user plane uplink path from the Target BSS (BSS-2) through MGW-2 and MSC-2 S. A green dashed line represents the control plane link between BSS-1 and MSC-1 S. The diagram also shows various bearer terminations: T_S and T_A in MGW-1, T_1 and T_2 in MGW-2, and T_3 and T_4 in the Target-MGW (not fully shown).](cd48273072c5c3a23e11fde892d1b6b6_img.jpg) + +Diagram of Connection Model 1: Before handover, LCLS is established. The diagram shows a network architecture with two Base Station Subsystems (BSS-1 and BSS-2) on the left, two Mobile Switching Center Servers (MSC-1 S and MSC-2 S) in the top center, and two Media Gateway units (MGW-1 and MGW-2) in the bottom center. A red solid line represents the user plane link within BSS-1 to the UE. A black solid line represents the user plane link from BSS-1 through MSC-1 S and MGW-1 to the UE. A blue dashed line represents the user plane link path through the CN (MSC-1 S, MGW-1, MGW-2) to the UE. A black dashed line represents the user plane uplink path from the Target BSS (BSS-2) through MGW-2 and MSC-2 S. A green dashed line represents the control plane link between BSS-1 and MSC-1 S. The diagram also shows various bearer terminations: T\_S and T\_A in MGW-1, T\_1 and T\_2 in MGW-2, and T\_3 and T\_4 in the Target-MGW (not fully shown). + +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 Target MGW, and then returning to BSS-2/BSS-1. This indicates that BSS-2 is bicasting user plane data uplink (UL) even though the UE is not yet detected in the 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 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 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: 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 BSS, 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 interfaces labeled T3, TA, T1, and T2. The Target MGW has interfaces labeled T4 and T.](ff0952ef692c9d960ce5f6708bcc9711_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 BSS, 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 interfaces labeled T3, TA, T1, and T2. The Target MGW has interfaces labeled T4 and T. + +**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. The process starts with UE-1(oMS) communicating with UE-2(tMS) via a locally switched path in the BSS. The handover process involves several steps: 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 TT, reserve circuit, Connection Point from Target MSC-S to Target MGW; 3b. Add reply TT 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 TT, configure Connection Point, only AoIP from Target MSC-S to Target MGW; 6b. MOD reply TT 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; 9a. TopDescr ({*, T3, isolate}, {TA, T3, oneway}) + ADD request(T3) from Target MSC-S to Target MGW; 9b. TopDescr() + ADD reply (T3) from Target MGW to Target MSC-S; 8b. LCLS-Connect-Control (LCLS-Connection-Status-Control = 'BicastaHandover') 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; 10. Initial Address (Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference), see NOTE 4 from MSC-1 S to Target MSC-S; 11a. Add request Network side T4 from Target MSC-S to Target MGW; 11b. Add reply T4 from Target MGW to Target MSC-S; 12. Bearer and Codec Information (SC, ACL, LCLS-Negotiation Response, LCLS-Configuration-Preference), see NOTE 4 from Target MSC-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. The process starts with UE-1(oMS) communicating with UE-2(tMS) via a locally switched path in the BSS. The handover process involves several steps: 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 TT, reserve circuit, Connection Point from Target MSC-S to Target MGW; 3b. Add reply TT 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 TT, configure Connection Point, only AoIP from Target MSC-S to Target MGW; 6b. MOD reply TT 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; 9a. TopDescr ({\*, T3, isolate}, {TA, T3, oneway}) + ADD request(T3) from Target MSC-S to Target MGW; 9b. TopDescr() + ADD reply (T3) from Target MGW to Target MSC-S; 8b. LCLS-Connect-Control (LCLS-Connection-Status-Control = 'BicastaHandover') 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; 10. Initial Address (Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference), see NOTE 4 from MSC-1 S to Target MSC-S; 11a. Add request Network side T4 from Target MSC-S to Target MGW; 11b. Add reply T4 from Target MGW to Target MSC-S; 12. Bearer and Codec Information (SC, ACL, LCLS-Negotiation Response, LCLS-Configuration-Preference), see NOTE 4 from Target MSC-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 TT 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.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +sequenceDiagram + participant UE1 as UE-1 + participant BSS1 as BSS-1 + participant MSC1S as MSC-1 S + participant MGW1 as MGW-1 + participant TMSCS as Target MSC-S + participant TMGW as Target MGW + participant TBSS as Target BSS + participant MSC2S as MSC-2 S + participant MGW2 as MGW-2 + participant BSS2 as BSS-2 + participant UE2 as UE-2 + + TMSCS->>MSC1S: 13. ACM, see NOTE 3 + MSC1S->>BSS1: 14. HO CMD + BSS1->>UE1: 15. HO CMD + TBSS->>TMGW: 16. HO Detect + TMGW->>MSC1S: 17. MAP Process-Access-Signalling Request + MSC1S->>MSC2S: 17a. LCLS-Status-Change-Request (LCLS-Status-Change: "IndicatedDLdataAfterHandover") + MSC2S->>MGW2: 17b. LCLS_CONNECT_CONTROL (LCLS-Connection-Status-Control = "DLDataAtHandover") + MGW2->>BSS2: 17c. LCLS_CONNECT_CONTROL Ack (LCLS-BSS-Status "the call is locally switched with requested LCLS configuration") + BSS2->>MSC2S: 17d. LCLS-Status-Change-Request Ack (LCLS-Status-Change: "IndicatedDLdataAfterHandover", Result Code="Status Change Req Accepted") + MSC1S->>MGW1: 18a. TopDescr, change flow direction ({TA, TS, oneway}, {TA, TS, bothway}) + MGW1->>MSC1S: 18b. TopDescr reply + TBSS->>TMGW: 19. Handover Complete (LCLS-BSS-Status: "Call not possible to be locally switched") + TMGW->>MSC1S: 20. MAP Send-End-Signalling Request + MSC1S->>TMGW: 21. Answer (LCLS-Status: "LCLS not connected") + Note over MGW2, BSS2: Break local switching + MSC1S->>BSS1: 22. Clear Command + MSC1S->>MSC2S: 23. LCLS Status Update (LCLS-Status: "LCLS not connected"), see NOTE 6 + MSC2S->>MGW2: 24. LCLS-Notification (LCLS-BSS-Status: "Call is no longer locally switched") + BSS1->>MSC1S: 25. Clear Complete + MSC1S->>MGW1: 26a. SUB request, release TS + MGW1->>MSC1S: 26b. SUB reply + +``` + +Sequence diagram for Inter-MSC Handover that breaks LCLS when user plane active, completion phase. + +**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 TA-T3 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 TS 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 ( $T_2$ ) from the termination to the Serving BSS ( $T_S$ ) and configures the Anchor termination ( $T_1$ ) one-way DL towards the Target MGW termination ( $T_2$ ). Termination to the Serving BSS ( $T_S$ ) is both-way connected to Anchor termination ( $T_1$ ) since it is also receiving UL user data from termination to the Serving BSS ( $T_S$ ). + +###### 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 $T_S$ is used for the bearer towards BSS-1, bearer termination $T_A$ is used for the bearer towards the succeeding/preceding MGW, that is MGW-2 and bearer termination $T_3$ is used towards the Target MGW. 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 Target-MGW the bearer termination $T_T$ is used towards the Target-BSS and bearer termination $T_4$ 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 + +![Two-part network diagram showing 'Before Handover' and 'During Handover' states. Network nodes include MSC-1 S, MSC-2 S, Target MSC-S, BSS-1, BSS-2, Target BSS, MGW-1, MGW-2, and Target MGW. In the 'Before' state, MGW-1 and MGW-2 are connected via terminations T_A and T_1. In the 'During' state, a new connection is established from MGW-1 (T_3) to Target MGW (T_4). The caption notes that T_3 is isolated from T_S, and T_A is one-way connected to T_3.](40f30e4d577a17052f8b1e6dc802a0d8_img.jpg) + +**Before Handover** + +**During Handover, $T_3$ is isolated from $T_S$ , $T_A$ is one-way connected to $T_3$** + +Two-part network diagram showing 'Before Handover' and 'During Handover' states. Network nodes include MSC-1 S, MSC-2 S, Target MSC-S, BSS-1, BSS-2, Target BSS, MGW-1, MGW-2, and Target MGW. In the 'Before' state, MGW-1 and MGW-2 are connected via terminations T\_A and T\_1. In the 'During' state, a new connection is established from MGW-1 (T\_3) to Target MGW (T\_4). The caption notes that T\_3 is isolated from T\_S, and T\_A is one-way connected to T\_3. + +![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 involves 11 steps 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 includes HO Required, MAP Prepare-Handover Request, Add request/reply for T_T and T_4, Handover Request/ACK, MOD request/reply for T_T, MAP Prepare-Handover Response, TopDescr/ADD request/reply, IAM, and APM messages. A dashed box indicates a condition where the call has been answered and MSC permits LCLS to be connected.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +UE-1 (oMS) is communicating with UE-2 (tMS) via the core network + +``` + +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 over UE-1, UE-2: UE-1 (oMS) is communicating with UE-2 (tMS) via the core network + + BSS-1->>MSC-1 S: 1. HO Required (target LAC) + MSC-1 S->>Target MSC-S: 2. MAP Prepare-Handover Request (target LAC, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference) + Target MSC-S->>Target MGW: 3a. Add request Access side T_T reserve circuit, Connection Point + Target MGW->>Target MSC-S: 3b. Add reply T_T + Target MSC-S->>Target BSS: 4. Handover Request (GCR, LCLS-Configuration, LCLS-Connection-Status-Control = "Connect") + Target BSS->>Target MSC-S: 5. HO Request Ack (LCLS-BSS-Status: "Call not yet locally switched") + Target MSC-S->>MSC-2 S: 5a. LCLS_NOTIFICATION (LCLS-BSS-Status: "Call not yet locally switched") + 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 + Target MSC-S->>Target MGW: 6a. MOD request T_T, configure Connection Point, only AoIP + Target MGW->>Target MSC-S: 6b. MOD reply T_T + Target MSC-S->>MSC-1 S: 7. MAP Prepare-Handover Response + MSC-1 S->>Target MSC-S: 8a. TopDescr ({*, T_3, isolate}, {T_A, T_3, oneway}) + ADD request(T_3) + Target MSC-S->>MSC-1 S: 8b. TopDescr() + ADD reply (T_3) + MSC-1 S->>Target MSC-S: 9. IAM (Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference), see NOTE 1, NOTE 2 + Target MSC-S->>Target MGW: 10a. Add request Network side T_4 + Target MGW->>Target MSC-S: 10b. Add reply T_4 + Target MSC-S->>MSC-1 S: 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 involves 11 steps 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 includes HO Required, MAP Prepare-Handover Request, Add request/reply for T\_T and T\_4, Handover Request/ACK, MOD request/reply for T\_T, MAP Prepare-Handover Response, TopDescr/ADD request/reply, IAM, and APM messages. A dashed box indicates a condition where the call has been answered and MSC permits LCLS to be connected. + +**Figure 8.4.2.2.4.2.1: Initial phase of Inter-MSC Handover establishing Local Switching** + +- Handover Required message is received from BSS-1 requesting an inter-MSC handover. The call is currently not locally switched. +- 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. +- a, b. Target-MSC-Server reserves circuit or Connection Point towards the Target-BSS +- 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. +- 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. +- a. 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 (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). +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 T4 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 long red arrow from UE-1 to 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 long red arrow from UE-1 to 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 Connection Model 1: Before BSS Internal Handover. The diagram depicts UE-1 and UE-2 connected to a BSS-1/BSS-2 node. Control signalling (dashed green line) connects BSS-1/BSS-2 to MSC-S-1 and MSC-S-2. User plane data (solid black line) flows from BSS-1/BSS-2 through MGW-1 (terminations Ts, TA) and MGW-2 (terminations T1, T2). A label 'Non-LCLS User Plane Data' indicates the path between MGWs. The state is labeled 'Before Handover'.](dd380ccd5aca1151074fede04826f1a4_img.jpg) + +Diagram showing Connection Model 1: Before BSS Internal Handover. The diagram depicts UE-1 and UE-2 connected to a BSS-1/BSS-2 node. Control signalling (dashed green line) connects BSS-1/BSS-2 to MSC-S-1 and MSC-S-2. User plane data (solid black line) flows from BSS-1/BSS-2 through MGW-1 (terminations Ts, TA) and MGW-2 (terminations T1, T2). A label 'Non-LCLS User Plane Data' indicates the path between MGWs. The state is labeled 'Before Handover'. + +**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 BSS-1/BSS-2. Control signaling (green dashed lines) flows from the BSS to MSC-S-1 and MSC-S-2. Non-LCLS User Plane Data (black solid lines) flows from the BSS through MGW-1 (with Serving (Ts), Anchor (TA), and Target (TT) ports) to MGW-2 (with ports T1 and T2) and then to MSC-S-2. A legend indicates: TS = Serving, TA = Anchor, TT = Target.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +Control Signalling + +UE-2 + +UE-1 + +BSS-1/ +BSS-2 + +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 BSS-1/BSS-2. Control signaling (green dashed lines) flows from the BSS to MSC-S-1 and MSC-S-2. Non-LCLS User Plane Data (black solid lines) flows from the BSS through MGW-1 (with Serving (Ts), Anchor (TA), and Target (TT) ports) to MGW-2 (with ports T1 and T2) and then to MSC-S-2. A legend indicates: TS = Serving, TA = Anchor, TT = Target. + +**Connection Model 2: During BSS Internal Handover** + +![Diagram of Connection Model 3: After BSS Internal Handover – Call is Locally Switched. UE-1 and UE-2 are now connected to BSS-2. User Plane Data (red solid lines) is locally switched within the BSS. Control signaling (green dashed lines) remains connected to MSC-S-1 and MSC-S-2. MGW-1 and MGW-2 are shown with different port configurations (TT, TA for MGW-1; T1, T2 for MGW-2).](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) + +Control Signalling + +UE-2 + +UE-1 + +BSS-1/ +BSS-2 + +User Plane Data + +MSC-S-1 + +MSC-S-2 + +MGW-1 + +MGW-2 + +After Handover + +Diagram of Connection Model 3: After BSS Internal Handover – Call is Locally Switched. UE-1 and UE-2 are now connected to BSS-2. User Plane Data (red solid lines) is locally switched within the BSS. Control signaling (green dashed lines) remains connected to MSC-S-1 and MSC-S-2. MGW-1 and MGW-2 are shown with different port configurations (TT, TA for MGW-1; T1, T2 for MGW-2). + +**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. Lifelines: UE-1, BSS-1, MGW-1, MSC-S-1, MSC-S-2, MGW-2, BSS-2, UE-2. The diagram shows the flow of messages for a handover where local switching is established. A 'Normally Switched User Plane' is shown at the top, and a 'Locally Switched User Plane in the BSS' is shown at the bottom, connected by a red curved arrow. Steps include: 1. Internal Handover Required; 2. Context C1: ADD Termination T_T; 3. Internal Handover Command (LCLS-Connection-Status-Control = 'Connect'); 3a. LCLS_NOTIFICATION (LCLS-BSS-Status: 'Call not yet locally switched'); 3b. LCLS_CONNECT_CONTROL (LCLS-Connection-Status-Control = 'Connect'); 3c. LCLS_CONNECT_CONTROL_ACK (LCLS-BSS-Status: 'Call not yet locally switched'); 4. Handover Detected; 5. Context C1: MOD Termination (T_A, T_S); 6. HandoverComplete (LCLS-BSS-Status = 'call is locally switched with requested LCLS configuration'); 7. LCLS-Status-Update (LCLS-Status: 'LCLS connected'); 8. LCLS_NOTIFICATION (LCLS-BSS-Status = 'call is locally switched with requested LCLS configuration'); 9. Context C1: SUB T_S. A red box labeled 'Handover Detected In Target Cell' is also present.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +Sequence diagram for BSS Internal Handover for AoIP that Establishes Local Switching. Lifelines: UE-1, BSS-1, MGW-1, MSC-S-1, MSC-S-2, MGW-2, BSS-2, UE-2. The diagram shows the flow of messages for a handover where local switching is established. A 'Normally Switched User Plane' is shown at the top, and a 'Locally Switched User Plane in the BSS' is shown at the bottom, connected by a red curved arrow. Steps include: 1. Internal Handover Required; 2. Context C1: ADD Termination T\_T; 3. Internal Handover Command (LCLS-Connection-Status-Control = 'Connect'); 3a. LCLS\_NOTIFICATION (LCLS-BSS-Status: 'Call not yet locally switched'); 3b. LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = 'Connect'); 3c. LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status: 'Call not yet locally switched'); 4. Handover Detected; 5. Context C1: MOD Termination (T\_A, T\_S); 6. HandoverComplete (LCLS-BSS-Status = 'call is locally switched with requested LCLS configuration'); 7. LCLS-Status-Update (LCLS-Status: 'LCLS connected'); 8. LCLS\_NOTIFICATION (LCLS-BSS-Status = 'call is locally switched with requested LCLS configuration'); 9. Context C1: SUB T\_S. A red box labeled 'Handover Detected In Target Cell' is also present. + +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. It includes UE-1 and UE-2 connected to BSS-1/BSS-2, which are connected to MSC-S-1 and MSC-S-2. MSC-S-1 is connected to MGW-1 (with terminations T_S and T_A), and MSC-S-2 is connected to MGW-2 (with terminations T_1 and T_2). Control signalling is shown with green dashed lines, and user plane data is shown with red solid lines for UE-1 and black solid lines for UE-2. The diagram is labeled 'Before Handover'.](4af57aad638888edf2062306f8a54a6c_img.jpg) + +Detailed Diagram Description: The diagram illustrates a network architecture with several nodes. At the left, UE-1 and UE-2 are connected to a block labeled BSS-1/BSS-2. A red solid line (User Plane Data) connects UE-1 through BSS-1/BSS-2 to a local switching point. A black solid line connects UE-2 through BSS-1/BSS-2. Above this, a green dashed line (Control Signalling) connects BSS-1/BSS-2 to MSC-S-1 and MSC-S-2. MSC-S-1 is linked to MGW-1, which contains terminations $T_S$ and $T_A$ . MSC-S-2 is linked to MGW-2, which contains terminations $T_1$ and $T_2$ . A dotted line (User plane path through CN) connects the BSS-1/BSS-2 block to MGW-1 and MGW-2, and also connects MGW-1 to MGW-2. The text 'Before Handover' is placed below the BSS and MGW-1 area. + +Diagram showing the connection model before BSS internal handover. It includes UE-1 and UE-2 connected to BSS-1/BSS-2, which are connected to MSC-S-1 and MSC-S-2. MSC-S-1 is connected to MGW-1 (with terminations T\_S and T\_A), and MSC-S-2 is connected to MGW-2 (with terminations T\_1 and T\_2). Control signalling is shown with green dashed lines, and user plane data is shown with red solid lines for UE-1 and black solid lines for UE-2. The diagram is labeled 'Before Handover'. + +**Connection Model 1: Before BSS Internal Handover - Call is locally switched** + +![Diagram showing Connection Model 2: During BSS Internal Handover. It illustrates the network architecture with UE-1 and UE-2 connected to BSS-1/ BSS-2. Control signaling is shown in green dashed lines connecting the BSS to MSC-S-1 and MSC-S-2. User plane data is shown in red solid lines. The diagram includes MSC-S-1, MSC-S-2, MGW-1, and MGW-2. MGW-1 has ports TS (Serving), TA (Anchor), and TT (Target). MGW-2 has ports T1 and T2. A legend indicates: TS = Serving, TA = Anchor, TT = Target.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +Control Signalling + +UE-2 + +BSS-1/ BSS-2 + +UE-1 + +User Plane Data + +MSC-S-1 + +MSC-S-2 + +TS + +TA + +TT + +MGW-1 + +T1 + +T2 + +MGW-2 + +During Handover + TS = Serving + TA = Anchor + TT = Target + +Diagram showing Connection Model 2: During BSS Internal Handover. It illustrates the network architecture with UE-1 and UE-2 connected to BSS-1/ BSS-2. Control signaling is shown in green dashed lines connecting the BSS to MSC-S-1 and MSC-S-2. User plane data is shown in red solid lines. The diagram includes MSC-S-1, MSC-S-2, MGW-1, and MGW-2. MGW-1 has ports TS (Serving), TA (Anchor), and TT (Target). MGW-2 has ports T1 and T2. A legend indicates: TS = Serving, TA = Anchor, TT = Target. + +Connection Model 2: During BSS Internal Handover + +![Diagram showing Connection Model 3: After BSS Internal Handover – Call is not Locally Switched. It shows the network state after the handover. The user plane path is now a 'Non-LCLS User Plane' connecting UE-2 through BSS-1/ BSS-2, MGW-1, and MGW-2. Control signaling remains in green dashed lines. MGW-1 ports are TT (Target), TA (Anchor), and TS (Serving). MGW-2 ports are T1 and T2.](6ca05954842b17f14dfd52f26b9d43d2_img.jpg) + +Control Signalling + +UE-2 + +BSS-1/ BSS-2 + +UE-1 + +Non-LCLS User Plane + +After Handover + +MSC-S-1 + +MSC-S-2 + +TT + +TA + +TS + +MGW-1 + +T1 + +T2 + +MGW-2 + +Diagram showing Connection Model 3: After BSS Internal Handover – Call is not Locally Switched. It shows the network state after the handover. The user plane path is now a 'Non-LCLS User Plane' connecting UE-2 through BSS-1/ BSS-2, MGW-1, and MGW-2. Control signaling remains in green dashed lines. MGW-1 ports are TT (Target), TA (Anchor), and TS (Serving). MGW-2 ports are T1 and T2. + +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 vertical lifelines for UE-1, BSS-1, MGW-1, MSC-S-1, MSC-S-2, MGW-2, BSS-2, and UE-2. At the top, a red double-headed arrow spans from BSS-1 to BSS-2 labeled 'Locally Switched User Plane in the BSS'. At the bottom, black double-headed arrows span the entire width labeled 'Normally Switched User Plane'. The message sequence is: 1. Internal Handover Required (BSS-1 to MSC-S-1); 2. Context C1: ADD Termination TT (*, TT) - isolate; (TA, TT) - bothway (MSC-S-1 to MGW-1); 3. LCLS-Status-Change Request [LCLS-Status-Change: 'LCLS-disconnection-preparationforHandover'] (MSC-S-1 to MSC-S-2); 3a. LCLS_CONNECT_CONTROL (LCLS-Connection-Status-Control = 'BicastatHandover') (MSC-S-2 to BSS-2); 3b. LCLS_CONNECT_CONTROL ACK (LCLS-BSS-Status = 'call is locally switched with requested LCLS configuration') (BSS-2 to MSC-S-2); 3c. LCLS-Status-Change Request Acknowledge [LCLS-Status-Change: 'LCLS-disconnection-preparationforHandover', Result Code = 'Status Change Req Accepted'] (MSC-S-2 to MSC-S-1); 4. Internal Handover Command (LCLS-Connection-Control-Status = 'Connect') (MSC-S-1 to BSS-1); A red box in BSS-1 says 'Handover Detected In Target Cell'; 4a. Handover Detected (BSS-1 to MSC-S-1); 5. HandoverComplete (LCLS-BSS-Status = 'Call is no longer locally switched') (BSS-1 to MSC-S-1); 6. LCLS-Status-Update [LCLS-Status: 'LCLS not connected'] (MSC-S-1 to MSC-S-2); 7. LCLS_NOTIFICATION (LCLS-BSS-Status = 'Call is no longer locally switched') (MSC-S-2 to BSS-2); 8. Context C1: SUB TS (MSC-S-1 to MGW-1).](dd5771673aececa53d42ece89218299d_img.jpg) + +Sequence diagram for BSS Internal Handover for AoIP that Breaks Local Switching. The diagram shows vertical lifelines for UE-1, BSS-1, MGW-1, MSC-S-1, MSC-S-2, MGW-2, BSS-2, and UE-2. At the top, a red double-headed arrow spans from BSS-1 to BSS-2 labeled 'Locally Switched User Plane in the BSS'. At the bottom, black double-headed arrows span the entire width labeled 'Normally Switched User Plane'. The message sequence is: 1. Internal Handover Required (BSS-1 to MSC-S-1); 2. Context C1: ADD Termination TT (\*, TT) - isolate; (TA, TT) - bothway (MSC-S-1 to MGW-1); 3. LCLS-Status-Change Request [LCLS-Status-Change: 'LCLS-disconnection-preparationforHandover'] (MSC-S-1 to MSC-S-2); 3a. LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = 'BicastatHandover') (MSC-S-2 to BSS-2); 3b. LCLS\_CONNECT\_CONTROL ACK (LCLS-BSS-Status = 'call is locally switched with requested LCLS configuration') (BSS-2 to MSC-S-2); 3c. LCLS-Status-Change Request Acknowledge [LCLS-Status-Change: 'LCLS-disconnection-preparationforHandover', Result Code = 'Status Change Req Accepted'] (MSC-S-2 to MSC-S-1); 4. Internal Handover Command (LCLS-Connection-Control-Status = 'Connect') (MSC-S-1 to BSS-1); A red box in BSS-1 says 'Handover Detected In Target Cell'; 4a. Handover Detected (BSS-1 to MSC-S-1); 5. HandoverComplete (LCLS-BSS-Status = 'Call is no longer locally switched') (BSS-1 to MSC-S-1); 6. LCLS-Status-Update [LCLS-Status: 'LCLS not connected'] (MSC-S-1 to MSC-S-2); 7. LCLS\_NOTIFICATION (LCLS-BSS-Status = 'Call is no longer locally switched') (MSC-S-2 to BSS-2); 8. Context C1: SUB TS (MSC-S-1 to MGW-1). + +**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 (TS) 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 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 of Connection Model 1: Before BSS Internal Handover. The diagram shows UE-1 and UE-2 connected to a BSS-1/BSS-2 block. A red solid line (User Plane Data) connects UE-1 and UE-2 through a switch in the BSS. A green dashed line (Control Signalling) loops from the BSS to MSC-S-1 and MSC-S-2. MSC-S-1 is connected to MGW-1 via a blue line, and MSC-S-2 is connected to MGW-2 via a blue line. MGW-1 contains terminations Ts and TA. MGW-2 contains terminations T1 and T2. A dotted black line (User plane path through CN) connects the BSS to MGW-1, then to MGW-2, and continues further. The diagram is labeled 'Before Handover'.](dc1f232cfd39be5c20b21374ad4c04c0_img.jpg) + +Diagram of Connection Model 1: Before BSS Internal Handover. The diagram shows UE-1 and UE-2 connected to a BSS-1/BSS-2 block. A red solid line (User Plane Data) connects UE-1 and UE-2 through a switch in the BSS. A green dashed line (Control Signalling) loops from the BSS to MSC-S-1 and MSC-S-2. MSC-S-1 is connected to MGW-1 via a blue line, and MSC-S-2 is connected to MGW-2 via a blue line. MGW-1 contains terminations Ts and TA. MGW-2 contains terminations T1 and T2. A dotted black line (User plane path through CN) connects the BSS to MGW-1, then to MGW-2, and continues further. The diagram is labeled 'Before Handover'. + +**Connection Model 1: Before BSS Internal Handover - Call is locally switched** + +![Diagram showing Connection Model 2: During BSS Internal Handover. It illustrates the network architecture with UE-1 and UE-2 connected to BSS-1/ BSS-2. Control signaling is shown in green dashed lines connecting the BSS to MSC-S-1 and MSC-S-2. User plane data is shown in red solid lines. The BSS is connected to MGW-1 and MGW-2 via MSC-S-1 and MSC-S-2 respectively. MGW-1 has ports TS (Serving), TA (Anchor), and TT (Target). MGW-2 has ports T1 and T2. A legend indicates: TS = Serving, TA = Anchor, TT = Target.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +During Handover + TS = Serving + TA = Anchor + TT = Target + +Diagram showing Connection Model 2: During BSS Internal Handover. It illustrates the network architecture with UE-1 and UE-2 connected to BSS-1/ BSS-2. Control signaling is shown in green dashed lines connecting the BSS to MSC-S-1 and MSC-S-2. User plane data is shown in red solid lines. The BSS is connected to MGW-1 and MGW-2 via MSC-S-1 and MSC-S-2 respectively. MGW-1 has ports TS (Serving), TA (Anchor), and TT (Target). MGW-2 has ports T1 and T2. A legend indicates: TS = Serving, TA = Anchor, TT = Target. + +**Connection Model 2: During BSS Internal Handover** + +![Diagram showing Connection Model 3: After BSS Internal Handover – Call is Locally Switched. This diagram is similar to the previous one but shows the state 'After Handover'. The user plane data (red solid line) is now locally switched within the BSS (BSS-1/ BSS-2) between UE-1 and UE-2, bypassing the MGW-1 and MGW-2.](933ecd14c858bf3fc919222d8e357bc8_img.jpg) + +After Handover + +Diagram showing Connection Model 3: After BSS Internal Handover – Call is Locally Switched. This diagram is similar to the previous one but shows the state 'After Handover'. The user plane data (red solid line) is now locally switched within the BSS (BSS-1/ BSS-2) between UE-1 and UE-2, bypassing the MGW-1 and MGW-2. + +**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, MSC-S-1, MSC-S-2, BSS-2, and UE-2, with MGW-1 and MGW-2. Red arrows indicate the locally switched user plane in the BSS.](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, MSC-S-1, MSC-S-2, BSS-2, and UE-2, with MGW-1 and MGW-2. Red arrows at the top and bottom indicate the 'Locally Switched User Plane in the BSS'. + +``` + +sequenceDiagram + participant UE-1 + participant BSS-1 + participant MGW-1 + participant MSC-S-1 + participant MSC-S-2 + participant MGW-2 + participant BSS-2 + participant UE-2 + + Note right of BSS-1: Locally Switched User Plane in the BSS + BSS-1->>MSC-S-1: 1. Internal Handover Required + BSS-1->>MSC-S-1: 2. Context C1: ADD Termination TT (*, TT) - isolate; (TA, TT) - bothway + MSC-S-1->>MSC-S-2: 3. LCLS-Status-Change Request [LCLS-Status-Change: "LCLS-disconnection-preparationforHandover"] + MSC-S-2->>BSS-2: 3a. LCLS_CONNECT_CONTROL (LCLS-Connection-Status-Control = "BicastaHandover") + BSS-2->>MSC-S-2: 3b. LCLS_CONNECT_CONTROL ACK (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration") + MSC-S-2->>MSC-S-1: 3c. LCLS-Status-Change Request Acknowledge [LCLS-Status-Change: "LCLS-disconnection-preparationforHandover", Result Code = "Status Change Req Accepted"] + MSC-S-1->>BSS-1: 4. Internal Handover Command (LCLS-Connection-Control-Status = "Connect") + Note left of BSS-1: Handover Detected In Target Cell + BSS-1->>MSC-S-1: [4a. Handover Detected] + BSS-1->>MSC-S-1: 5. HandoverComplete (LCLS-BSS-Status = "Call is locally switched with requested LCLS configuration") + MSC-S-1->>MGW-1: 6. Context C1: SUB TS + Note right of BSS-2: Locally Switched User Plane in the BSS + +``` + +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, MSC-S-1, MSC-S-2, BSS-2, and UE-2, with MGW-1 and MGW-2. Red arrows indicate the locally switched user plane in the BSS. + +**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 a bearer termination labeled T_S. UE-2 is connected via a solid black line to MGW-1 through a bearer termination labeled T_A. MGW-1 is connected to MGW-2 via a solid black line. MGW-2 has two bearer terminations, T_1 and T_2, connected to two Mobile Switching Center-Serving (MSC-S) units, MSC-S-1 and MSC-S-2 respectively, via solid blue lines. A dashed green line (Control plane link) labeled 'Control Signalling' connects the BSS-1/BSS-2 unit to both MSC-S-1 and MSC-S-2. A dashed green line also connects MSC-S-1 and MSC-S-2. A label 'Non-LCLS User Plane Data' is placed near the MGW-2 to MSC-S-2 connection. The text 'Before Handover' is located below the BSS-1/BSS-2 unit.](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 a bearer termination labeled T\_S. UE-2 is connected via a solid black line to MGW-1 through a bearer termination labeled T\_A. MGW-1 is connected to MGW-2 via a solid black line. MGW-2 has two bearer terminations, T\_1 and T\_2, connected to two Mobile Switching Center-Serving (MSC-S) units, MSC-S-1 and MSC-S-2 respectively, via solid blue lines. A dashed green line (Control plane link) labeled 'Control Signalling' connects the BSS-1/BSS-2 unit to both MSC-S-1 and MSC-S-2. A dashed green line also connects MSC-S-1 and MSC-S-2. A label 'Non-LCLS User Plane Data' is placed near the MGW-2 to MSC-S-2 connection. The text 'Before Handover' is located below the BSS-1/BSS-2 unit. + +Connection Model 1: Before BSS Internal Handover - Call is not locally switched + +![Diagram showing Connection Model 2: During BSS Internal Handover. It illustrates the network architecture with UE-1 and UE-2 connected to BSS-1/BSS-2. Control signaling is shown between the BSS and MSC-S-1, MSC-S-2, MGW-1, and MGW-2. The Non-LCLS User Plane Data path is shown. A legend indicates: TS = Serving, TA = Anchor, TT = Target.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +Control Signalling + +UE-2 + +BSS-1/ +BSS-2 + +UE-1 + +Non-LCLS User Plane Data + +MSC-S-1 + +MSC-S-2 + +TS + +TA + +TT + +MGW-1 + +T1 + +T2 + +MGW-2 + +During Handover +TS = Serving +TA = Anchor +TT = Target + +Diagram showing Connection Model 2: During BSS Internal Handover. It illustrates the network architecture with UE-1 and UE-2 connected to BSS-1/BSS-2. Control signaling is shown between the BSS and MSC-S-1, MSC-S-2, MGW-1, and MGW-2. The Non-LCLS User Plane Data path is shown. A legend indicates: TS = Serving, TA = Anchor, TT = Target. + +**Connection Model 2: During BSS Internal Handover** + +![Diagram showing Connection Model 3: After BSS Internal Handover – Call is not Locally Switched. It shows the network state after the handover, with UE-1 and UE-2 still connected to BSS-1/BSS-2. The Non-LCLS User Plane path remains unchanged. The legend indicates: TT = Target, TA = Anchor.](0ee9d674085524d589646a6c3fb21ec3_img.jpg) + +Control Signalling + +UE-2 + +BSS-1/ +BSS-2 + +UE-1 + +Non-LCLS User Plane + +MSC-S-1 + +MSC-S-2 + +TT + +TA + +MGW-1 + +T1 + +T2 + +MGW-2 + +After Handover + +Diagram showing Connection Model 3: After BSS Internal Handover – Call is not Locally Switched. It shows the network state after the handover, with UE-1 and UE-2 still connected to BSS-1/BSS-2. The Non-LCLS User Plane path remains unchanged. The legend indicates: TT = Target, TA = Anchor. + +**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 flow of messages for an internal handover where the user plane remains normally switched through the MGWs. Key messages include: 1. Internal Handover Required; 2. Context C1: ADD Termination T_T; 3. Internal Handover Command (LCLS-Connection-Control-Status = 'Connect'); 3a. Handover Detected In Target Cell; 4. HandoverComplete (LCLS-BSS-Status = 'Call is not locally switched'); 5. Context C1: SUB T_S.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +The diagram illustrates a BSS internal handover for AoIP. The sequence of events 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 options for TT isolation: (\*, TT) - isolate; (TA, TT) - bothway. +- 3. Internal Handover Command (LCLS-Connection-Control-Status = "Connect"):** MSC-1 sends a message to BSS-1. +- Handover Detected In Target Cell:** A red box indicates this event in BSS-1. +- 3a. Handover Detected:** BSS-1 sends a message to MSC-1. +- 4. HandoverComplete (LCLS-BSS-Status = "Call is not locally switched"):** BSS-1 sends a message to MSC-1. +- 5. Context C1: SUB TS:** MSC-1 sends a message to MGW-1. + +The user plane is labeled as "Normally Switched User Plane" at the top and bottom of the diagram, indicating that the call remains switched through the core network (MGW-1 and MGW-2) throughout the handover process. + +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 flow of messages for an internal handover where the user plane remains normally switched through the MGWs. Key messages include: 1. Internal Handover Required; 2. Context C1: ADD Termination T\_T; 3. Internal Handover Command (LCLS-Connection-Control-Status = 'Connect'); 3a. Handover Detected In Target Cell; 4. HandoverComplete (LCLS-BSS-Status = 'Call is not locally switched'); 5. Context C1: SUB T\_S. + +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 CD is accepted, the user plane is rerouted. A red solid line shows user plane data from tUE through oBSS/tBSS to oMGW. A green dashed line shows control signalling from oBSS/tBSS to oMSC-S. A blue dash-dot line shows user plane data from sMGW back to oUE. The path from oMGW to tMGW is labeled 'Non LCLS User Plane'.](9f862801bce82634d3b5a1e0a195a799_img.jpg) + +Diagram for Connection Model 2. After CD is accepted, the user plane is rerouted. A red solid line shows user plane data from tUE through oBSS/tBSS to oMGW. A green dashed line shows control signalling from oBSS/tBSS to oMSC-S. A blue dash-dot line shows user plane data from sMGW back to oUE. The path from oMGW to tMGW is labeled 'Non LCLS User Plane'. + +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 note 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 through 13, detailing call deflection, resource clearing, and announcement handling.](f5deee2f3301ee351c4008283ffafbb3_img.jpg) + +Sequence diagram illustrating the 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: Context (sC) 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. Context (sC) (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. Context (sC) (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 note 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 through 13, detailing call deflection, resource clearing, and announcement handling. + +**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 various APM and LCLS messages. 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. + +Key messages and steps shown: + +- 14. IAM** [Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference] from sMSC to tMSC. +- 15. Paging tUE** from tMSC to tUE. +- Paging response + CL3** from tUE to tMSC. +- 16. SETUP** from tMSC to tUE. +- 17. Call Confirmed** from tUE to tMSC. +- 18. Add network side termination: ADD request (\$)/ADD reply (T7)** from tMSC to tMGW. +- 19. APM** [SCt, ACLt, LCLS-Negotiation Response, LCLS-Configuration-Preference] from tMGW to sMSC. +- 20. APM** [SCt, ACLt, LCLS-Negotiation Response, LCLS-Configuration-Preference] from sMSC to iMGW. +- 21. APM** [SCt, ACLt, LCLS-Negotiation Response, LCLS-Configuration-Preference] from iMGW to oMSC. +- 22. 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.** (Note in a red box) +- 23. For succeeding signalling sequence see basic call establishment, figures 6.3.2.2 and 6.3.2.3, steps 18 - 32** (Separator line) +- 24. if "LCLS-Configuration update needed" determine new value of LCLS-Configuration IE** (Note in a dashed box) +- 25. LCLS\_CONNECT\_CONTROL** (LCLS-Connection-Status-Control = "connect", [LCLS-Configuration]) from oMSC to oBSS. +- 26a. LCLS\_CONNECT\_CONTROL\_ACK** (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration") from oBSS to oMSC. +- 27. LCLS status update: APM** [LCLS-Status = "LCLS connected"] from oMSC to GMSC. +- 28. LCLS status update: APM** [LCLS-Status = "LCLS connected"] from GMSC to sMSC. +- 29. LCLS status update: APM** [LCLS-Status = "LCLS connected"] from sMSC to tMSC. +- 26b. LCLS\_NOTIFICATION** (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration") from tMSC to tBSS. + +A large red arrow at the bottom, 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 various APM and LCLS messages. 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 oBSS is also connected to an oMGW via a solid red user plane link. The oMGW is connected to an iMGW via a dotted blue user plane link. The iMGW is connected to the GMSC-S via a solid blue user plane link. A blue dashed arrow points from the oMGW back to the oUE, representing an announcement or 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 oBSS is also connected to an oMGW via a solid red user plane link. The oMGW is connected to an iMGW via a dotted blue user plane link. The iMGW is connected to the GMSC-S via a solid blue user plane link. A blue dashed arrow points from the oMGW back to the oUE, representing an announcement or 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 via a solid red user plane link. The oMGW is connected to an iMGW via a dotted blue user plane link. The iMGW is connected to a tMGW via a dotted blue user plane link. The tMGW is connected to the tMSC-S via a solid blue user plane link. A red solid arrow points from the oBSS/tBSS to the tUE, representing the user plane data. A green dashed arrow points from the oBSS/tBSS to the oUE, representing the user plane data. A dotted line labeled 'Non LCLS User Plane' runs horizontally across the diagram, passing through the oMGW, iMGW, and 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 via a solid red user plane link. The oMGW is connected to an iMGW via a dotted blue user plane link. The iMGW is connected to a tMGW via a dotted blue user plane link. The tMGW is connected to the tMSC-S via a solid blue user plane link. A red solid arrow points from the oBSS/tBSS to the tUE, representing the user plane data. A green dashed arrow points from the oBSS/tBSS to the oUE, representing the user plane data. A dotted line labeled 'Non LCLS User Plane' runs horizontally across the diagram, passing through the oMGW, iMGW, and 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 the interaction between these entities for call establishment, including Service Request, SETUP, IAM, HLR Interrogation, ADD requests, ASSIGNMENT REQUEST, and FACILITY messages.](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->>oBSS: 2. SETUP + Note right of oMSC: 3. Retrieve oBSS ID and use it to generate Global Call Reference. + Note right of oMSC: 4. IAM [Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference] + oMSC->>GMSC: 4. IAM [Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference] + Note right of GMSC: 5. HLR Interrogation: CFU service active and calling party should be notified + Note right of GMSC: 6. Add network side termination: ADD request ($) / ADD reply (T3) Context (iC) + GMSC->>iMGW: 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: 7. APM [SC, ACL, LCLS-Negotiation Response, LCLS-Configuration-Preference] + Note right of oMSC: 8a. Add network side termination: ADD request ($) / ADD reply (T2) Context (oC) + oMSC->>oMGW: 8a. Add network side termination: ADD request ($) / ADD reply (T2) Context (oC) + Note right of oMGW: Network side Bearer Establishment + oMGW->>oMSC: Network side Bearer Establishment + Note right of oMSC: 8b. Add access side termination: ADD request ($) / ADD reply (T1) Context (oC) + oMSC->>oBSS: 8b. Add access side termination: ADD request ($) / ADD reply (T1) Context (oC) + Note right of oBSS: NOTE: For AoTDM step 8b is: ADD (T1). + Note right of oMSC: 9. ASSIGNMENT REQUEST (GCR, LCLS-Configuration) + oMSC->>oUE: 9. ASSIGNMENT REQUEST (GCR, LCLS-Configuration) + Note right of oUE: 10. ASSIGNMENT COMPLETE (LCLS-BSS-Status = "call not possible to be locally switched") + oUE->>oBSS: 10. ASSIGNMENT COMPLETE (LCLS-BSS-Status = "call not possible to be locally switched") + Note right of oBSS: Access side Bearer Establishment + oBSS->>oMSC: Access side Bearer Establishment + Note right of oMSC: 11. BICC COT + oMSC->>GMSC: 11. BICC COT + Note right of GMSC: 12. ACM [BCI=no indication, Generic Notification indicator=call is diverting] + GMSC->>oMSC: 12. ACM [BCI=no indication, Generic Notification indicator=call is diverting] + Note right of GMSC: 13. MOD (T3): play announcement / send tone Context (iC) + GMSC->>iMGW: 13. MOD (T3): play announcement / send tone Context (iC) + Note right of oMSC: 14. FACILITY with call forwarding notification + oMSC->>oUE: 14. FACILITY with call forwarding notification + Note right of oUE: Announcement / Tone + oUE->>oBSS: Announcement / Tone + +``` + +Sequence diagram for CFU, Call Establishment Flow. Lifelines: oUE, oBSS, oMGW, oMSC, iMGW, GMSC, tMSC, tMGW, tBSS, tUE. The diagram shows the interaction between these entities for call establishment, including Service Request, SETUP, IAM, HLR Interrogation, ADD requests, ASSIGNMENT REQUEST, and FACILITY messages. + +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 (T3), IAM, Paging, SETUP, Call Confirmed, ADD request, APM messages, and LCLS status updates. 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 oMSC) +- 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 . (oMSC to oBSS) +- 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 (oBSS to oMGW) +- 26. LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "connect", [LCLS-Configuration]) (oMGW to oBSS) +- 27a. LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration") (oBSS to oMGW) +- 28. LCLS status update: BICC APM [LCLS-Status = "LCLS connected"] (oMGW to GMSC) +- 29. LCLS status update: BICC APM [LCLS-Status = "LCLS connected"] (GMSC to tMSC) +- 27b. LCLS\_NOTIFICATION (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration") (tMSC to tBSS) + +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 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 (T3), IAM, Paging, SETUP, Call Confirmed, ADD request, APM messages, and LCLS status updates. 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 stations (oBSS, sBSS). User plane links are shown as dotted lines through the CN and solid lines within BSS/UEs. Bearer terminations T1 through Ts are indicated at the gateway interfaces. + +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 back towards the oUE.](215165a27ad7d72bd39fdf55a3cb7486_img.jpg) + +This diagram shows the network state after Call Forwarding Busy (CFB) is activated. 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). These links are used to send announcements or tones to the calling party. + +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 back towards the oUE. + +Connection Model 2: After CFB (UDUB), Announcement towards calling party + +![Diagram of Connection Model 3: CFB (UDUB), After Answer, Call locally switched. It shows a network architecture with two horizontal layers. The top layer is the 'Control Signalling' plane, enclosed in a dashed green box, containing oMSC-S, GMSC-S, sMSC-S, and tMSC-S. The bottom layer is the 'Non LCLS User Plane', enclosed in a dashed black box, containing oMGW, iMGW, sMGW, and tMGW. Vertical blue lines connect each MSC-S to its corresponding MGW. On the left, a box labeled 'oBSS/tBSS' contains 'tUE' and 'oUE'. Red arrows show 'Control Signalling' (green dashed line) and 'User Plane Data' (red dashed line) paths between the UEs and the oMSC-S/oMGW.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +Diagram of Connection Model 3: CFB (UDUB), After Answer, Call locally switched. It shows a network architecture with two horizontal layers. The top layer is the 'Control Signalling' plane, enclosed in a dashed green box, containing oMSC-S, GMSC-S, sMSC-S, and tMSC-S. The bottom layer is the 'Non LCLS User Plane', enclosed in a dashed black box, containing oMGW, iMGW, sMGW, and tMGW. Vertical blue lines connect each MSC-S to its corresponding MGW. On the left, a box labeled 'oBSS/tBSS' contains 'tUE' and 'oUE'. Red arrows show 'Control Signalling' (green dashed line) and 'User Plane Data' (red dashed line) paths between the UEs and the oMSC-S/oMGW. + +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 notifications, bearer termination, and message exchanges between the sMSC, sMGW, and GMSC.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +The diagram illustrates the call establishment flow for CFB UDUB. It begins with a note for call establishment towards a served subscriber sUE, referencing basic call establishment, figures 6.3.2.1 and 6.3.2.2. The sequence of messages is as follows: + +1. CFB service active & calling party should be notified; expiry of no reply condition timer (at sMSC). +2. Release termination to served UE: Context (sC) 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: Context (sC) (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). +7. NOTIFY (T5): Announcement / Tone completed: Context (sC) (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 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 notifications, bearer termination, and message exchanges between the sMSC, sMGW, and GMSC. + +**Figure 13.4.3.2.7.2.1: CFB UDUB, Call establishment flow** + +1. 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). +2. 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). +3. The sMSC server sends the CPG message with the Generic Notification Indicator parameter set to "Call is diverting". +4. 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. +5. The GMSC server sends the CPG message with the Generic Notification Indicator parameter set to "Call is diverting". +6. The oMSC server notifies the calling user (oUE) about call forwarding. +7. The sMGW notifies the sMSC server when the announcement/tone is completed using the Announcement Completed or Tone Completed procedure. +8. 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. +9. 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) + +**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 +- - - 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 the network architecture for Connection Model 1. It shows a sequence of nodes: oUE connected to oBSS, which is connected to oMGW (with bearers T1, T2, oC). oMGW is connected to iMGW (with bearers T3, T4, iC). iMGW is connected to sMGW (with bearers T5, Ts, sC). sMGW is connected to sBSS, which is connected to sUE. Control plane links (green dashed lines) connect oUE to oBSS, oBSS to oMSC-S, oMSC-S to GMSC-S, GMSC-S to sMSC-S, sMSC-S to sBSS, and sBSS to sUE. User plane links (solid red lines) connect oUE to oBSS, oBSS to oMGW, oMGW to iMGW, iMGW to sMGW, sMGW to sBSS, and sBSS to sUE. A dotted line represents the user plane link path through the CN. + +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 showing network architecture for Connection Model 2, similar to Model 1 but with a blue dashed line indicating announcement towards the calling party from sMGW back to oMGW.](605ad256780bc1b6022dfb65a6e24a3b_img.jpg) + +The diagram illustrates the network architecture for Connection Model 2. It is similar to Connection Model 1 but includes a blue dashed line representing the 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). This link originates from the sMGW (specifically from bearer Ts) and points back towards the oMGW (specifically towards bearer T1). + +Diagram showing network architecture for Connection Model 2, similar to Model 1 but with a blue dashed line indicating announcement towards the calling party from sMGW back to oMGW. + +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 oBSS/tBSS, which is linked to oMGW. Control signaling is shown in green dashed lines, and user plane data in red solid lines.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +The diagram illustrates the 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:** A UE (tUE and oUE) is connected to an oBSS/tBSS. The oBSS/tBSS is connected to an oMSC-S. The oMSC-S is connected to a GMSC-S, which is connected to an sMSC-S, which is connected to a tMSC-S. All MSCs are part of the control plane. + - **User Plane Data:** 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. All MGWs are part of the user plane. The oMGW has two interfaces, T1 and T2. The iMGW has two interfaces, T3 and T4. The sMGW has two interfaces, T5 and T6. The tMGW has two interfaces, T7 and T8. The oMGW also has two interfaces, oC and tC. + - **Connections:** The oMSC-S is connected to the oMGW. The GMSC-S is connected to the iMGW. The sMSC-S is connected to the sMGW. The tMSC-S is connected to the tMGW. The oBSS/tBSS is connected to the oMGW. The oBSS/tBSS is also connected to the oMSC-S. The oBSS/tBSS is connected to the UE (tUE and oUE). The oBSS/tBSS is connected to the oMGW. The oBSS/tBSS is connected to the oMSC-S. The oBSS/tBSS is connected to the UE (tUE and oUE). + +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 oBSS/tBSS, which is linked to 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 showing interactions between oUE, oBSS, oMGW, oMSC, iMGW, GMSC, sMSC, sMGW, tMSC, and tUE. The flow includes service activation, bearer termination, CPG messages for call diversion, announcement/tone procedures, and IAM/APM messages for LCLS negotiation.](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 +2. Release termination to served UE: Context (sC) SUB request(Ts) / SUB reply (Ts) +3. CPG [Generic Notification indicator = call is diverting] +4. MOD (T5): play Context (sC) announcement / send tone +5. CPG [Generic Notification indicator = call is diverting] +6. FACILITY with call forwarding notification +- Announcement / Tone +7. NOTIFY (T5): Announcement / Context (sC) Tone completed +8. IAM [Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference] +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] +11. APM [SCt, ACLt, LCLS-Negotiation Response, LCLS-Configuration-Preference] +12. APM [SCt, ACLt, LCLS-Negotiation Response, LCLS-Configuration-Preference] +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 showing interactions between oUE, oBSS, oMGW, oMSC, iMGW, GMSC, sMSC, sMGW, tMSC, and tUE. The flow includes service activation, bearer termination, CPG messages for call diversion, announcement/tone procedures, and IAM/APM messages for LCLS negotiation. + +**Figure 13.4.4.7.2.1: CFNRy, Call establishment flow** + +1. 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). +2. 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). +3. The sMSC server sends the CPG message with the Generic Notification Indicator parameter set to "Call is diverting". +4. 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. +5. The GMSC server sends the CPG message with the Generic Notification Indicator parameter set to "Call is diverting". +6. The oMSC server notifies the calling user (oUE) about call forwarding. +7. The sMGW notifies the sMSC server when the announcement/tone is completed using the Announcement Completed or Tone Completed procedure. +8. 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/tones as blue dashed lines. Termination points T1 through T6 are labeled on the MGWs.](e417ae35ab07134888be901c201d54cd_img.jpg) + +Legend: + +- Control plane link which transmits signalling (green dashed line) +- User plane link path through CN, connected or disconnected (black dotted line) +- User plane link which transmits real user plane data within BSS and UEs (red solid line) +- Announcement / tone (blue dashed line) + +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/tones 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 to 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 to 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 showing call establishment and switching between UE-A, BSS-A, MGW-A, MSC-A, iMGW, iMSC, MSC-B, MGW-B, BSS-B, UE-B, and UE-C. The diagram includes steps for call setup, IAM messages, hold procedures, and local switching. Red arrows indicate 'Call is locally Switched' between UE-A and UE-B.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +The sequence diagram illustrates the interaction between various network elements for call handling. The participants are UE-A, BSS-A, MGW-A, MSC-A, iMGW, iMSC, MSC-B, MGW-B, BSS-B, UE-B, and UE-C. +Key interactions include: + + +- At the top, a red curved arrow between UE-A and UE-B is labeled "Call is locally Switched". +- 1. SETUP: UE-C to MSC-B. +- 2. CALL PROCEEDING: MSC-B to UE-C. +- 3. IAM [Codec List, GCR(new), LCLS-Negotiation Request, LCLS-Configuration-Preference]: MSC-B to iMSC. +- 4. IAM [Codec List, GCR(new), LCLS-Negotiation Request, LCLS-Configuration-Preference]: iMSC to MSC-A. +- 5. UE-A busy, Call waiting available: Internal to MSC-A. +- 6. SETUP: MSC-A to UE-A. +- 7. CALL CONFIRMED: UE-A to MSC-A. +- 8. A horizontal box indicates: "normal LCLS call establishment procedure between UE-A and UE-C from step 8 to 17 in 6.3.2". +- 9. HOLD: UE-A to MSC-A. +- 10. A horizontal box indicates: "The session between UE-A and UE-B is put on hold". +- 11. HOLD ACKNOWLEDGE: MSC-A to UE-A. +- 12. CONNECT: MSC-A to UE-A. +- 13. Move access side termination: MOV request (T6) / MOV reply (T6) between MSC-A and MGW-A (Context C1-2). +- 14. A horizontal box indicates: "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." +- At the bottom, a red curved arrow between UE-A and UE-B is labeled "Call is locally Switched". + +Sequence diagram showing call establishment and switching between UE-A, BSS-A, MGW-A, MSC-A, iMGW, iMSC, MSC-B, MGW-B, BSS-B, UE-B, and UE-C. The diagram includes steps for call setup, IAM messages, hold procedures, and local switching. Red arrows indicate 'Call is locally Switched' between UE-A and UE-B. + +**Figure 13.5.2.2.2.1: Accept Incoming call, original call is held** + +1. UE-C sends a SETUP message to the Core Network. +2. MSC-B responds with CALL PROCEEDING message. +3. 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. +4. iMSC transfers the IAM message to MSC-A. +5. MSC-A determines that UE-A is busy and that call waiting is available. +6. MSC-A sends a SETUP message to UE-A. +7. UE-A responds with CALL CONFIRM message. +8. The normal LCLS call establishment procedures from step 8 to 17 in 6.3.2 are applied. +9. UE-A requests to hold the call with UE-B. +10. The session between UE-A and UE-B is put on hold. The procedure in 13.6.2.3.2 is applied. +11. 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 plane links (green dashed) and user plane links (red solid) between UE-A, UE-B, BSS-A/B, MSC-S-B, iMSC-S, MSC-S-A, MGW-B, iMGW, and MGW-A. The user plane data flows directly between UE-A and UE-B through the BSS-A/B node.](50ef8602c7c9edd2da0e2133e772c2a2_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 + +Detailed description: The diagram shows a network architecture for LCLS. At the top, three MSC servers (MSC-S-B, iMSC-S, MSC-S-A) are connected via green dashed control plane links. Below them are three Media Gateways (MGW-B, iMGW, MGW-A) connected to their respective MSCs via blue control links. MGW-B has terminations T1, T2; iMGW has T3, T4; MGW-A has T5, T6. A dotted line represents the 'Non LCLS User Plane' path through the MGWs. On the left, UE-A and UE-B are connected to a BSS-A/B node. A red solid line shows 'User Plane Data' looping back within the BSS-A/B node between UE-A and UE-B, bypassing the core network MGWs. A green dashed line labeled 'Control Signalling' connects the BSS-A/B to the MSC-S-B. + +Diagram showing Connection Model 1: Before Call Hold, LCLS established. It illustrates control plane links (green dashed) and user plane links (red solid) between UE-A, UE-B, BSS-A/B, MSC-S-B, iMSC-S, MSC-S-A, MGW-B, iMGW, and MGW-A. The user plane data flows directly between UE-A and UE-B through the BSS-A/B node. + +**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 is similar to the first but shows the state after a hold procedure where the user plane link to UE-B is broken (indicated by an 'X') and an announcement path (blue dash-dot) is established from MGW-A back towards the BSS.](ad555483986d7170a46ce72d164b5bc8_img.jpg) + +Detailed description: This diagram shows the state after a call hold. The red user plane loop in BSS-A/B is broken with a black 'X' on the path to UE-B. Instead, a blue dash-dot line representing an 'Announcement / tone' originates from MGW-A (termination T5/T6 area), passes through iMGW (T3/T4) and MGW-B (T1/T2), and reaches the BSS-A/B node to be delivered to the held party. The control plane links remain the same as in the first diagram. + +Diagram showing Connection Model 2: After Hold procedure, LCLS released; Announcement towards held party. This diagram is similar to the first but shows the state after a hold procedure where the user plane link to UE-B is broken (indicated by an 'X') and an announcement path (blue dash-dot) 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; and a blue arrow at the bottom indicates 'Announcement' from MGW-A to UE-B.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +For LCLS release procedure initiated by MSC server see the corresponding signalling sequence in sub-clause 7.2.1 + +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; and a blue arrow at the bottom indicates 'Announcement' from MGW-A to UE-B. + +**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. The sequence of messages is: 1. RETRIEVE from UE-A to MSC-A; 2. MSC accepts RETRIEVE request; 3. MOD request (T5): Stop announcement / MOD reply from MSC-A to MGW-A; 4. MOD request (T6): sendrecv / MOD reply from MGW-A to MSC-A; 5. CPG [Generic Notification Indicator = 'remote retrieval'] from MSC-A to iMSC; 6. CPG [Generic Notification Indicator = 'remote retrieval'] from iMSC to MSC-B; 7. FACILITY with call hold notification from MSC-B to UE-B; 8. RETRIEVE ACKNOWLEDGE from MSC-A to UE-A; 9. LCLS Re-establishment from MSC-A to MGW-A. A note at the bottom states: 'For LCLS re-establishment procedure initiated by MSC server see the corresponding signalling sequence in sub-clause 7.3.1'.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +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. The sequence of messages is: 1. RETRIEVE from UE-A to MSC-A; 2. MSC accepts RETRIEVE request; 3. MOD request (T5): Stop announcement / MOD reply from MSC-A to MGW-A; 4. MOD request (T6): sendrecv / MOD reply from MGW-A to MSC-A; 5. CPG [Generic Notification Indicator = 'remote retrieval'] from MSC-A to iMSC; 6. CPG [Generic Notification Indicator = 'remote retrieval'] from iMSC to MSC-B; 7. FACILITY with call hold notification from MSC-B to UE-B; 8. RETRIEVE ACKNOWLEDGE from MSC-A to UE-A; 9. LCLS Re-establishment from MSC-A to MGW-A. A note at the bottom states: 'For LCLS re-establishment procedure initiated by MSC server see the corresponding signalling sequence in sub-clause 7.3.1'. + +**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 14 lifelines: 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 14 lifelines: 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. 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 +- ... User plane link path through CN +- User plane link which transmits real user plane data within BSS and UEs +- .- Announcement / tone + +**Connection Model 1: Locally switched call** + +In this model, the call is locally switched within the oBSS/tBSS. The oUE is connected to the oBSS/tBSS, and the tUE is also connected to it. The oMSC-S, iMSC-S, and tMSC-S are connected to the oBSS/tBSS. The oMGW, iMGW, and tMGW are connected to the oMSC-S, iMSC-S, and tMSC-S respectively. The oMGW is connected to the oBSS/tBSS via T1 and T2. The iMGW is connected to the oBSS/tBSS via T3 and T4. The tMGW is connected to the oBSS/tBSS via T5 and T6. The oUE is connected to the oBSS/tBSS via a red line. The tUE is connected to the oBSS/tBSS via a red line. The oBSS/tBSS is connected to the oMSC-S via a green dashed line. The oMSC-S is connected to the iMSC-S via a green dashed line. The iMSC-S is connected to the tMSC-S via a green dashed line. The oMSC-S is connected to the oMGW via a blue line. The iMSC-S is connected to the iMGW via a blue line. The tMSC-S is connected to the tMGW via a blue line. The oMGW is connected to the iMGW via a dotted line. The iMGW is connected to the tMGW via a dotted line. The oBSS/tBSS is connected to the oUE via a red line. The oBSS/tBSS is connected to the tUE via a red line. The oBSS/tBSS is connected to the oMSC-S via a green dashed line. The oMSC-S is connected to the iMSC-S via a green dashed line. The iMSC-S is connected to the tMSC-S via a green dashed line. The oMSC-S is connected to the oMGW via a blue line. The iMSC-S is connected to the iMGW via a blue line. The tMSC-S is connected to the tMGW via a blue line. The oMGW is connected to the iMGW via a dotted line. The iMGW is connected to the tMGW via a dotted line. + +**Connection Model 2: Locally switched call, playing of Announcement/tone** + +In this model, the call is locally switched within the oBSS/tBSS, but the oUE is blocked from receiving data from the tUE. The oUE is connected to the oBSS/tBSS, and the tUE is also connected to it. The oMSC-S, iMSC-S, and tMSC-S are connected to the oBSS/tBSS. The oMGW, iMGW, and tMGW are connected to the oMSC-S, iMSC-S, and tMSC-S respectively. The oMGW is connected to the oBSS/tBSS via T1 and T2. The iMGW is connected to the oBSS/tBSS via T3 and T4. The tMGW is connected to the oBSS/tBSS via T5 and T6. The oUE is connected to the oBSS/tBSS via a red line. The tUE is connected to the oBSS/tBSS via a red line. The oBSS/tBSS is connected to the oMSC-S via a green dashed line. The oMSC-S is connected to the iMSC-S via a green dashed line. The iMSC-S is connected to the tMSC-S via a green dashed line. The oMSC-S is connected to the oMGW via a blue line. The iMSC-S is connected to the iMGW via a blue line. The tMSC-S is connected to the tMGW via a blue line. The oMGW is connected to the iMGW via a dotted line. The iMGW is connected to the tMGW via a dotted line. The oBSS/tBSS is connected to the oUE via a red line. The oBSS/tBSS is connected to the tUE via a red line. The oBSS/tBSS is connected to the oMSC-S via a green dashed line. The oMSC-S is connected to the iMSC-S via a green dashed line. The iMSC-S is connected to the tMSC-S via a green dashed line. The oMSC-S is connected to the oMGW via a blue line. The iMSC-S is connected to the iMGW via a blue line. The tMSC-S is connected to the tMGW via a blue line. The oMGW is connected to the iMGW via a dotted line. The iMGW is connected to the tMGW via a dotted line. An announcement/tone is being played from the iMGW to the oUE via a blue dashed line. + +Diagram showing two connection models for mid-call announcement/tone. 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. + +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 towards the oUE, including LCLS configuration changes and MOD/NOTIFY messages.](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 sends a "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" points 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 sends a "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 towards the oUE, including LCLS configuration changes and MOD/NOTIFY messages. + +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 oMGW, iMGW, and tMGW, and then to the respective MSCs. The oMGW, iMGW, and tMGW are connected in a chain.](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 oMGW, iMGW, and tMGW, and then to the respective MSCs. The oMGW, iMGW, and tMGW are connected in a chain. + +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 an 'X' mark 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 an 'X' mark 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. This diagram shows the oMGW isolating the access side (oBSS/tBSS) from the rest of the network. The downlink path from the oMGW to the oBSS/tBSS is shown, but the path from the oBSS/tBSS back to the oMGW is blocked, isolating 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. This diagram shows the oMGW isolating the access side (oBSS/tBSS) from the rest of the network. The downlink path from the oMGW to the oBSS/tBSS is shown, but the path from the oBSS/tBSS back to the oMGW is blocked, isolating 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. The diagram illustrates the interaction between oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, and tUE. A red arrow indicates the call is locally switched. The sequence includes: 1. Play announcement/tone towards oUE; 2. LCLS_CONNECT_CONTROL (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 (call is locally switched with requested LCLS configuration); 4. MOD request (T1): Play announcement/Send Tone / MOD reply; 5. NOTIFY (T1): Announcement completed/ Tone completed; 6. LCLS_CONNECT_CONTROL (connected both-way in the BSS and bi-casted UL to the Core Network); 7. LCLS_CONNECT_CONTROL_ACK (call is locally switched with requested LCLS configuration).](694df81535f89c7bfb9ef0df6f130dc0_img.jpg) + +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** + +1. Play announcement/ tone towards oUE +2. LCLS\_CONNECT\_CONTROL (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 (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration") +4. MOD request (T1): Play announcement/Send Tone / MOD reply +Context (oC) +5. NOTIFY (T1): Announcement completed/ Tone completed +Context (oC) +6. LCLS\_CONNECT\_CONTROL (LCLS-Configuration = "connected both-way in the BSS and bi-casted UL to the Core Network") +7. LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration") + +Sequence diagram showing Mid-Call Announcement/Tone Flow with Block Local Data Request. The diagram illustrates the interaction between oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, and tUE. A red arrow indicates the call is locally switched. The sequence includes: 1. Play announcement/tone towards oUE; 2. LCLS\_CONNECT\_CONTROL (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 (call is locally switched with requested LCLS configuration); 4. MOD request (T1): Play announcement/Send Tone / MOD reply; 5. NOTIFY (T1): Announcement completed/ Tone completed; 6. LCLS\_CONNECT\_CONTROL (connected both-way in the BSS and bi-casted UL to the Core Network); 7. LCLS\_CONNECT\_CONTROL\_ACK (call is locally switched with requested LCLS configuration). + +**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 oBSS to tBSS. The sequence of messages is: 1. oMSC sends 'Play announcement/ tone towards oUE' to oMGW; 2. oMSC sends 'MOV request (T1) / MOV reply' to oMGW with context Cg, indicating 'Isolate bearer termination'; 3. oMGW 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 oMGW with status 'call is locally switched with requested LCLS configuration'; 5. oMGW sends 'MOD request (T1): Play announcement/Send Tone / MOD reply' to oMSC; 6. oMSC sends 'NOTIFY (T1): Announcement completed/ Tone completed' to oMGW; 7. oMGW 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 oMGW with status 'call is locally switched with requested LCLS configuration'; 9. oMGW sends 'MOV request (T1) / MOV reply' to oMSC with context oC, indicating '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 oBSS to tBSS. The sequence of messages is: 1. oMSC sends 'Play announcement/ tone towards oUE' to oMGW; 2. oMSC sends 'MOV request (T1) / MOV reply' to oMGW with context Cg, indicating 'Isolate bearer termination'; 3. oMGW 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 oMGW with status 'call is locally switched with requested LCLS configuration'; 5. oMGW sends 'MOD request (T1): Play announcement/Send Tone / MOD reply' to oMSC; 6. oMSC sends 'NOTIFY (T1): Announcement completed/ Tone completed' to oMGW; 7. oMGW 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 oMGW with status 'call is locally switched with requested LCLS configuration'; 9. oMGW sends 'MOV request (T1) / MOV reply' to oMSC with context oC, indicating '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 series. Below each MSC is a corresponding MGW (MGW-o, MGW-i, MGW-t). The User Plane (connection) is shown between MGW-o and MGW-t. At the bottom, a BSS (BSS-1/ BSS-2) contains two UEs (UE-o and UE-t). UE-o is sending UL data to the BSS, which is then forwarded to MGW-o and then to MSC-S-o. MSC-S-o is sending DL data to UE-o. A red box indicates 'UL data requested from tUE' and 'DL send requested to apply a tone or announcement'. A blue box indicates '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' indicates 'Local DL data blocked by BSS'.](99e9a4791d2e5bb5afa1bb884652d4db_img.jpg) + +The diagram illustrates the network architecture and data flow for Case Study 1. At the top, three MSCs are shown: MSC-S-o (Originating), MSC-S-i (Intermediate), and MSC-S-t (Terminating). Each MSC is connected to a corresponding MGW (MGW-o, MGW-i, MGW-t). The User Plane (connection) is shown between MGW-o and MGW-t. At the bottom, a BSS (BSS-1/ BSS-2) contains two UEs: UE-o (Originating) and UE-t (Terminating). UE-o is sending UL data to the BSS, which is then forwarded to MGW-o and then to MSC-S-o. MSC-S-o is sending DL data to UE-o. A red box indicates 'UL data requested from tUE' and 'DL send requested to apply a tone or announcement'. A blue box indicates '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' indicates 'Local DL data blocked by BSS'. + +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 series. Below each MSC is a corresponding MGW (MGW-o, MGW-i, MGW-t). The User Plane (connection) is shown between MGW-o and MGW-t. At the bottom, a BSS (BSS-1/ BSS-2) contains two UEs (UE-o and UE-t). UE-o is sending UL data to the BSS, which is then forwarded to MGW-o and then to MSC-S-o. MSC-S-o is sending DL data to UE-o. A red box indicates 'UL data requested from tUE' and 'DL send requested to apply a tone or announcement'. A blue box indicates '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' indicates '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 sending an LCLS-Negotiation request with 'Need Receive Forward=yes' to MSC-S-l, which then forwards it to MSC-S-t. The User Plane (connection) is shown with MGW-o, MGW-l, and MGW-t. Data flows from UE-o and UE-t through BSS-1/ BSS-2 and MGW-t, but is blocked at MGW-t by a large 'X', indicating isolation of the access side termination.](9c45844d796e85ae05505870a54e4eb4_img.jpg) + +Diagram of oMSC requesting UL data from oUE indicated in LCLS-Negotiation. It shows MSC-S-o sending an LCLS-Negotiation request with 'Need Receive Forward=yes' to MSC-S-l, which then forwards it to MSC-S-t. The User Plane (connection) is shown with MGW-o, MGW-l, and MGW-t. Data flows from UE-o and UE-t through BSS-1/ BSS-2 and MGW-t, but is blocked at MGW-t by a large 'X', indicating isolation of the access side termination. + +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 sending an LCLS-Negotiation request with 'Need Receive Forward=no' to MSC-S-l, which then forwards it to MSC-S-t. The User Plane (connection) is shown with MGW-o, MGW-l, and MGW-t. Data flows from UE-o and UE-t through BSS-1/ BSS-2 and MGW-t. A red dashed arrow points to MGW-o with the text 'Option with Need_Receive_Forward = No: Isolate access side termination from network side termination'.](1314748d1fff41b2d57a8ba9e9687c6a_img.jpg) + +Diagram of oMSC requesting UL data from oUE not indicated in LCLS-Negotiation. It shows MSC-S-o sending an LCLS-Negotiation request with 'Need Receive Forward=no' to MSC-S-l, which then forwards it to MSC-S-t. The User Plane (connection) is shown with MGW-o, MGW-l, and MGW-t. Data flows from UE-o and UE-t through BSS-1/ BSS-2 and MGW-t. A red dashed arrow points to MGW-o with the text 'Option with Need\_Receive\_Forward = No: Isolate access side termination from network side termination'. + +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 '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 UE-o and UE-t. Local User Plane Data is shown within the BSS, with a red 'X' indicating a blocked path from UE-t to the 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 '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 UE-o and UE-t. Local User Plane Data is shown within the BSS, with a red 'X' indicating a blocked path from UE-t to the 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 'Need Receive Backward, Need Send Backward'. MSC-S-t also sends 'UL data requested from tUE'. 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 UE-o and UE-t. Local User Plane Data is shown within the BSS, with a red 'X' indicating '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 'Need Receive Backward, Need Send Backward'. MSC-S-t also sends 'UL data requested from tUE'. 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 UE-o and UE-t. Local User Plane Data is shown within the BSS, with a red 'X' indicating '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 of tMSC LCLS-Negotiation handling. It shows three MSCs (MSC-S-o, MSC-S-l, MSC-S-t) connected to three MGWs (MGW-o, MGW-l, MGW-t) via a User Plane connection. MSC-S-o is connected to UE-o, and MSC-S-t is connected to UE-t. LCLS-Negotiation messages are exchanged between MSCs. A red box indicates 'DL send requested to apply a tone or announcement' and a purple box indicates 'UL data requested from oUE'. A red arrow shows data flow from MSC-S-l to MGW-l. A blue arrow shows data flow from MGW-t to UE-t, labeled 'Option with LCLS-Configuration IE: "Send Access DL, block local DL"'. A red 'X' over a blue arrow in the BSS indicates 'Local DL data blocked by BSS'. A label 'Local User Plane Data' is present in the BSS area.](4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg) + +Diagram of tMSC LCLS-Negotiation handling. It shows three MSCs (MSC-S-o, MSC-S-l, MSC-S-t) connected to three MGWs (MGW-o, MGW-l, MGW-t) via a User Plane connection. MSC-S-o is connected to UE-o, and MSC-S-t is connected to UE-t. LCLS-Negotiation messages are exchanged between MSCs. A red box indicates 'DL send requested to apply a tone or announcement' and a purple box indicates 'UL data requested from oUE'. A red arrow shows data flow from MSC-S-l to MGW-l. A blue arrow shows data flow from MGW-t to UE-t, labeled 'Option with LCLS-Configuration IE: "Send Access DL, block local DL"'. A red 'X' over a blue arrow in the BSS indicates 'Local DL data blocked by BSS'. A label 'Local User Plane Data' is present in the BSS area. + +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 a network architecture with three MSCs (MSC-S-o, MSC-S-l, MSC-S-t) and three MGWs (MGW-o, MGW-l, MGW-t). MSC-S-o is connected to MGW-o, MSC-S-l to MGW-l, and MSC-S-t to MGW-t. MSC-S-o and MSC-S-l exchange LCLS-Negotiation messages. MSC-S-l and MSC-S-t exchange LCLS-Negotiation messages with 'Need Receive Forward' flags. A 'User Plane (connection)' links the MGWs. Below the MGWs is a BSS containing UE-o and UE-t. A purple arrow shows 'Local User Plane Data' from UE-o to MSC-S-o. A red arrow shows 'DL send requested to apply a tone or announcement' from MSC-S-t to UE-t. A red box on the right indicates an option: '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 UL and DL data flow between oUE, iMSC, tMSC, and tUE. It shows MSC-S-o, MSC-S-i, and MSC-S-t connected via LCLS-Negotiation messages. Below them, MGW-o, MGW-i, and MGW-t are connected via a User Plane. At the bottom, UE-o and UE-t are connected to a BSS (BSS-1/BSS-2) which has Local User Plane Data. Arrows indicate data flow from oUE to iMSC, then to tMSC, and finally to tUE. A red box indicates that DL send is requested to apply a tone or announcement. A red 'X' marks blocked local DL data by the BSS. A red text option with LCLS-Configuration IE 'Send Access DL, block local DL' is shown.](f61d0925551545b5938b3a4d1bbf63c3_img.jpg) + +The diagram shows a network architecture with three MSCs (MSC-S-o, MSC-S-i, MSC-S-t) and three MGWs (MGW-o, MGW-i, MGW-t) connected in a chain. MSC-S-o is connected to UE-o, and MSC-S-t is connected to UE-t. MSC-S-i is the central MSC. LCLS-Negotiation messages are exchanged between the MSCs. The User Plane (connection) is shown between the MGWs. Local User Plane Data is shown within the BSS (BSS-1/BSS-2). A red box indicates that DL send is requested to apply a tone or announcement. A red 'X' marks blocked local DL data by the BSS. A red text option with LCLS-Configuration IE "Send Access DL, block local DL" is shown. + +Diagram illustrating the network architecture for UL and DL data flow between oUE, iMSC, tMSC, and tUE. It shows MSC-S-o, MSC-S-i, and MSC-S-t connected via LCLS-Negotiation messages. Below them, MGW-o, MGW-i, and MGW-t are connected via a User Plane. At the bottom, UE-o and UE-t are connected to a BSS (BSS-1/BSS-2) which has Local User Plane Data. Arrows indicate data flow from oUE to iMSC, then to tMSC, and finally to tUE. A red box indicates that DL send is requested to apply a tone or announcement. A red 'X' marks blocked local DL data by the BSS. A red text option with LCLS-Configuration IE 'Send Access DL, block local DL' is shown. + +**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 and tUE data flow with MGWs and MSCs.](3750b0149a6380885998ab3ca6a8787c_img.jpg) + +The diagram illustrates a network architecture involving three MSCs (MSC-S-o, MSC-S-l, MSC-S-t) and three MGWs (MGW-o, MGW-l, MGW-t). Each MGW is connected to its corresponding MSC via a signaling link and to a User Plane (connection). The User Plane connects to a BSS (Base Station System) containing UE-o and UE-t. The MSCs are interconnected via LCLS-Negotiation messages. A red dashed arrow indicates a request for UL data from tUE. A red text box highlights an option with Need\_Receive\_Backward = No, which isolates access side termination from network side termination. + +MSC-S-o + +MSC-S-l + +MSC-S-t + +LCLS-Negotiation + +LCLS-Negotiation (Need Receive Backward=No) + +LCLS-Negotiation (Need Receive Backward=No) + +UL data requested from tUE + +MGW-o + +MGW-l + +MGW-t + +T1 + +T2 + +User Plane (connection) + +Local User Plane Data + +BSS-1/ BSS-2 + +UE-o + +UE-t + +Option with Need\_Receive\_Backward = No: Isolate access side termination from network side termination + +Diagram of tMSC and tUE data flow with MGWs and MSCs. + +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 | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23813/04dc3838022e96d8d5548bb1b777b38c_img.jpg b/marked/Rel-11/23_series/23813/04dc3838022e96d8d5548bb1b777b38c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a28168f8ba6eba54b6e4ce48579b476290c3ff5e --- /dev/null +++ b/marked/Rel-11/23_series/23813/04dc3838022e96d8d5548bb1b777b38c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dad8e51c184695922a77f54db1dd18bc438d9a9ac3e0f6a987460f1c8b02d256 +size 61152 diff --git a/marked/Rel-11/23_series/23813/07b17a620c75522d53916a11e12d1bff_img.jpg b/marked/Rel-11/23_series/23813/07b17a620c75522d53916a11e12d1bff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..002b32be40bb29414e8b26fdaeec3b9faafec22b --- /dev/null +++ b/marked/Rel-11/23_series/23813/07b17a620c75522d53916a11e12d1bff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92dd236e9df60315d56c318f45386b6ac5dfc309a8aca879800f49d7a3705719 +size 49718 diff --git a/marked/Rel-11/23_series/23813/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/Rel-11/23_series/23813/21ad58fee90f2be50708ff541d225507_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a1a5ec48f6b362298c3d5d55aee04f88ddd1ecb --- /dev/null +++ b/marked/Rel-11/23_series/23813/21ad58fee90f2be50708ff541d225507_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b061eeb80392dbe109aec16cb5327daa1a69e08a2bad6aac06331befe97c7300 +size 69339 diff --git a/marked/Rel-11/23_series/23813/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-11/23_series/23813/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44970b4bdc08cf7602f453664571062711342f7e --- /dev/null +++ b/marked/Rel-11/23_series/23813/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30b3f860fdb0d23f4cdc30d08aeba193d41b1643c03b60e14fff46d25cc999b8 +size 33312 diff --git a/marked/Rel-11/23_series/23813/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg b/marked/Rel-11/23_series/23813/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0ee9e6244a91c66ef6ab3ac10f94bbe01fff3b0 --- /dev/null +++ b/marked/Rel-11/23_series/23813/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a01082c79950e51fc5a3d170e0e0cfc3a54cc6e7e947e546cfd0f91e52be7699 +size 68390 diff --git a/marked/Rel-11/23_series/23813/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/Rel-11/23_series/23813/3da1a07cb87051bf616c9876db958cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4ed2e45a2effd2d5535fb7c477b6cff54255981 --- /dev/null +++ b/marked/Rel-11/23_series/23813/3da1a07cb87051bf616c9876db958cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e996703595d33314e21755a58e1d1350152fad6676308926c54e333e3879918 +size 131114 diff --git a/marked/Rel-11/23_series/23813/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-11/23_series/23813/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38aa5febe1331dd367c3899825da0bd1171da5af --- /dev/null +++ b/marked/Rel-11/23_series/23813/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36b875c798b10ac77c95d022e13297bc9cff9afaf1094fbcda22487678563462 +size 91701 diff --git a/marked/Rel-11/23_series/23813/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Rel-11/23_series/23813/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..328194ea8b068fba5e72effc978126ec5167a90c --- /dev/null +++ b/marked/Rel-11/23_series/23813/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32365c5742eedb9770796b48615a23d123e5a284ae67a1d047798409d727e73e +size 116664 diff --git a/marked/Rel-11/23_series/23813/4ff00a489baaa34a0c01070de1d613db_img.jpg b/marked/Rel-11/23_series/23813/4ff00a489baaa34a0c01070de1d613db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c460d2faaadf23fa44cf93bf7fc6a7ff99f6423 --- /dev/null +++ b/marked/Rel-11/23_series/23813/4ff00a489baaa34a0c01070de1d613db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd39d049651f032307fe9b76f7047469a0013e544427c1dc821af96bc2f048b4 +size 113620 diff --git a/marked/Rel-11/23_series/23813/5e92d9e8e9ce204e405bff2367f88176_img.jpg b/marked/Rel-11/23_series/23813/5e92d9e8e9ce204e405bff2367f88176_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c700f6316b89b6b917751c2d58769bd035b2142 --- /dev/null +++ b/marked/Rel-11/23_series/23813/5e92d9e8e9ce204e405bff2367f88176_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83a3a915519698ca92961c9d9730451d63859f4aa099db58be2bc34f5ce0f8be +size 29193 diff --git a/marked/Rel-11/23_series/23813/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-11/23_series/23813/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82b1699e2f3c159951ed2e2246e5bd15c9068f72 --- /dev/null +++ b/marked/Rel-11/23_series/23813/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70c4be8135371de50eb1d79af522fddf8fa1dd53ce90e3409f5c348abbb536f3 +size 42153 diff --git a/marked/Rel-11/23_series/23813/7d2d1d3870cd224c4430d19334557716_img.jpg b/marked/Rel-11/23_series/23813/7d2d1d3870cd224c4430d19334557716_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54b7a3f1211074ebe13bcce4b7d5ec2778707525 --- /dev/null +++ b/marked/Rel-11/23_series/23813/7d2d1d3870cd224c4430d19334557716_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eab75362f889059ed0c39b22b0f9f359d43b276600fa8720c3eb8d8a658132bd +size 67775 diff --git a/marked/Rel-11/23_series/23813/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/marked/Rel-11/23_series/23813/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d771ea59353cfb104ec64c513ef1753ffbf5aac3 --- /dev/null +++ b/marked/Rel-11/23_series/23813/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40644639a42f5741cef476937eb3a215e7d94320331d95a89dd51ca5ccd022e0 +size 48697 diff --git a/marked/Rel-11/23_series/23813/8658cfab6a458b4a80ab2e384c61ff89_img.jpg b/marked/Rel-11/23_series/23813/8658cfab6a458b4a80ab2e384c61ff89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca74ba8271699c1f96bf52b2370909b8919c044b --- /dev/null +++ b/marked/Rel-11/23_series/23813/8658cfab6a458b4a80ab2e384c61ff89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e959b8771659a367e088e2b36e719f666bae796704f27318bdf41b62bcab62d4 +size 68100 diff --git a/marked/Rel-11/23_series/23813/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/marked/Rel-11/23_series/23813/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1af658d8226355422594f2485cbeab7ab8cec891 --- /dev/null +++ b/marked/Rel-11/23_series/23813/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8df592f1cd218c92bc1caff37824a584603c5f0dd09af50aac816895f82dcbbc +size 23475 diff --git a/marked/Rel-11/23_series/23813/933ecd14c858bf3fc919222d8e357bc8_img.jpg b/marked/Rel-11/23_series/23813/933ecd14c858bf3fc919222d8e357bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3796a2dc8f4ed628bcb194612ba2f16f88f8c694 --- /dev/null +++ b/marked/Rel-11/23_series/23813/933ecd14c858bf3fc919222d8e357bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d0a2aa17f02770556787082080656d01cb4624c84fbd9ee2e0fbcfcfbdd9220 +size 121971 diff --git a/marked/Rel-11/23_series/23813/94acd33fcad85bb6f207a308f9b63191_img.jpg b/marked/Rel-11/23_series/23813/94acd33fcad85bb6f207a308f9b63191_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e05c18b0814a08f15a43fc16d48db587a1656c4d --- /dev/null +++ b/marked/Rel-11/23_series/23813/94acd33fcad85bb6f207a308f9b63191_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44e0cd6fb041d43bc2e087248a5139b62c8aff73e1be26732a235137747306b9 +size 64492 diff --git a/marked/Rel-11/23_series/23813/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-11/23_series/23813/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..651e88a16ef1587ed3845252eefe1c14dd3a1461 --- /dev/null +++ b/marked/Rel-11/23_series/23813/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c59a59d5016585d1c41b86344dedab2339911acebbef03fa665b6284c40a312 +size 100612 diff --git a/marked/Rel-11/23_series/23813/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-11/23_series/23813/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94dc043d8e8ebfae81eddfebbd5d91810ce36486 --- /dev/null +++ b/marked/Rel-11/23_series/23813/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea0ac9dd482b000e9259025db21e923286437e3d4b34827e4e1c931b73bae8f3 +size 36296 diff --git a/marked/Rel-11/23_series/23813/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/Rel-11/23_series/23813/c2fc2621e8206d24427b56bcb2398fc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..109a8c5481cbd1744f6af542f7c3feb99eebdbd6 --- /dev/null +++ b/marked/Rel-11/23_series/23813/c2fc2621e8206d24427b56bcb2398fc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce829e0a60bf5b487e5ea084b316bb6135fc8629384abecefa31c241b7bbf84a +size 79917 diff --git a/marked/Rel-11/23_series/23813/f2ea0f64a770b22b902820457d262265_img.jpg b/marked/Rel-11/23_series/23813/f2ea0f64a770b22b902820457d262265_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e983de7079e40def3cd5f8e635c74b37101d5496 --- /dev/null +++ b/marked/Rel-11/23_series/23813/f2ea0f64a770b22b902820457d262265_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2eb7ad06e5605cec51364c7764f6325b17192642a495e0bc18ca245a774c2cf8 +size 68331 diff --git a/marked/Rel-11/23_series/23813/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-11/23_series/23813/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab0d0098f01999df7ecb8bb381137231480429b8 --- /dev/null +++ b/marked/Rel-11/23_series/23813/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc12961da17d7a57e44b5a2084a528fd57937498cd5d81f74392abacd5215e21 +size 38468 diff --git a/marked/Rel-11/23_series/23813/raw.md b/marked/Rel-11/23_series/23813/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..edb9ad262a897671b41620466c5de2ddeed544d2 --- /dev/null +++ b/marked/Rel-11/23_series/23813/raw.md @@ -0,0 +1,1511 @@ + + + + + + +# 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 Key issues ..... | 7 | +| 4.1 Key Issue 1: Policy enhancement for sponsored data connectivity ..... | 7 | +| 4.1.1 Introduction ..... | 7 | +| 4.1.2 Alternative solutions..... | 8 | +| 4.1.2.1 Alternative 1 ..... | 8 | +| 4.1.2.1.1 Reference points enhancements ..... | 9 | +| 4.1.2.1.2 Call flows ..... | 10 | +| 4.2 Key issue 2: Coherent access to Policy related databases..... | 12 | +| 4.2.1 Description ..... | 12 | +| 4.2.2 Alternative solutions..... | 12 | +| 4.2.2.1 SPR as an Application Front-End of the UDC Architecture ..... | 12 | +| 4.2.2.2 PCRF as an Application Front-End of the UDC Architecture..... | 13 | +| 4.2.3 Comparison of alternatives..... | 14 | +| 4.2.4 Conclusion..... | 14 | +| 4.3 Key issue 3: QoS and gating control based on spending limits ..... | 15 | +| 4.3.1 Description ..... | 15 | +| 4.3.1.1 Common Principles..... | 15 | +| 4.3.2 Alternative solutions..... | 15 | +| 4.3.2.1 Alternative solution 1 - configuration based solution..... | 15 | +| 4.3.2.2 New reference point (Sy) between PCRF and OCS ..... | 17 | +| 4.3.2.2.1 General ..... | 17 | +| 4.3.2.2.2 PCRF contacting the OCS (PCRF-Centric approach)..... | 18 | +| 4.3.2.2.2.5 Signalling flows..... | 19 | +| 4.3.2.2.3 OCS contacting the PCRF (OCS-Centric approach)..... | 23 | +| 4.3.2.3 Alternative solution 3 - enhancing Gy and Gx ..... | 23 | +| 4.3.3 Conclusion..... | 23 | +| 4.4 Key issue 4: Service Awareness and Privacy Policies..... | 24 | +| 4.4.1 Description ..... | 24 | +| 4.4.2 Actions resulting from service detection..... | 24 | +| 4.4.3 Alternative solutions..... | 24 | +| 4.4.3.1 Alternative 1 ..... | 24 | +| 4.4.3.1.1 Reference Points..... | 25 | +| 4.4.3.1.2 Functional entities ..... | 25 | +| 4.4.3.2 Solicited service detection reporting..... | 26 | +| 4.4.3.2.1 Specific functions description..... | 26 | +| 4.4.3.2.2 Signalling Flows..... | 27 | +| 4.4.3.3 Unsolicited service detection reporting ..... | 33 | +| 4.4.3.3.1 Signalling Flows..... | 33 | +| 4.4.3.4 Service Detection and Policy rules definition and structure ..... | 34 | +| 4.4.3.4.1 General ..... | 35 | +| 4.4.3.4.2 Service Detection and Policy rule relevant operations..... | 36 | +| 4.4.3.4.3 PCC rules modifications..... | 36 | +| 4.4.4 Conclusion..... | 36 | +| 4.5 Key issue 5: Service Based Traffic Steering..... | 36 | +| 4.5.1 Description ..... | 36 | +| 4.5.2 Conclusion..... | 37 | +| 4.6 Key issue 6: Extending Policy Architecture to handle transactional services ..... | 37 | +| 4.6.1 Description ..... | 37 | +| 4.6.2 Alternative solutions..... | 37 | + +4.6.2.1        Alternative 1 - Use Rx to authorize transactional services..... 37 +4.6.2.1.1        General ..... 37 +4.6.2.1.2        Architecture ..... 37 +4.6.2.1.3        Reference points..... 38 +4.6.2.1.4        PCC Information Flows ..... 38 +4.6.3        Comparison of alternatives..... 40 +4.6.4        Conclusion..... 40 + +Annex A:        Change history..... 41 + +# --- 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 importance of policy based service delivery has been recognized within 3GPP and has resulted in following work in the last few releases: + +- QoS and Charging related policies + - PCRF +- Non 3GPP access inter-working + - ANDSF + - Mobility protocol selection + +In addition there has been work done in IMS that defines policies related to selection of IMS for service delivery vs other mechanisms. 3GPP work in this area reflects efforts to improve service delivery based on operator policy, user preferences etc. However the approach so far has been fragmented and a more comprehensive approach would ensure better policy decisions. Some examples of what is missing are: + +- Deep Packet Inspection coupled with user privacy policies to improve user experience. For example, by intelligently identifying service in use and providing service enhancement via e.g. appropriate QoS for the service, location related info for use with the service etc. +- Service based traffic steering e.g. to use different PDNs for different services. For example issues such as source address selection when the UE is connected to multiple PDNs. +- Standardized and extensible ways to implement service policies that go beyond existing PCC IP flow policies. For example transactional service policies such as a policy to enforce max limit on SMSIP/month based on user profile etc. Other example could be service policy such as redirect and firewall control. + +# --- 1 Scope + +The objective is to study an evolved policy solution through enhancement of 3GPP policy framework. One of the aims of the study is to ensure a policy architecture that provides an extensible framework for easy reuse with new IP based services by identifying areas where improvement of specifications are feasible. The study item will look into solutions for the examples in the section above. + +Existing components for consideration in the Policy Study are functions and interfaces to/from + +- PCRF, PCEF and BBERF; +- SPR, HSS; +- ANDSF; +- IMS policy decision making entities. + +The study aims to provide a more comprehensive way (e.g. going beyond existing 3GPP PCC framework) to handle operator policies for all IP / service flows (IMS and non-IMS) in a coordinated manner and under varying network conditions while keeping in view aspects such as: + +- user preferences; +- user subscriptions; +- service requirements; +- terminal capabilities (including converged terminals); +- network capabilities (3GPP and those non 3GPP accesses inter- working with 3GPP); +- Session transfer and terminating policies; +- Security policy control, e.g. firewalling and gating. + +Roaming scenarios are considered as part of this study. Compatibility with existing system architecture elements are protected and backward compatibility is expected. All types of policies i.e. static/pre-provisioned, dynamic, network based, UE based are considered in the study. + +When a key issue is resolved sufficiently to be incorporated into the specification in an independent manner, the study work may move forward for a decision for normative specification work on such issue(s) using a new work item or a TEI. + +# --- 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 TR 41.001: "GSM Release specifications". +- [3] 3GPP TS 23.203: "Policy and charging control architecture". +- [4] 3GPP TS 22.101: "Service aspects; Service principles". + +- [5] 3GPP TS 23.335: "User Data Convergence (UDC); Technical realization and information flows". +- [6] 3GPP TS 23.198 v9.0.0: "Open Service Access (OSA)". +- [7] 3GPP TS 32.296: "Online Charging System (OCS): Applications and interfaces". +- [8] 3GPP TS 32.299: "Charging management: Diameter charging applications". + +# --- 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]. + +## 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]. + +# --- 4 Key issues + +## 4.1 Key Issue 1: Policy enhancement for sponsored data connectivity + +### 4.1.1 Introduction + +The target of this key issue is to study policy enhancement needed for sponsored data connectivity. With sponsored data connectivity, the sponsor has a business relationship with the operator and compensates the operator for user's connectivity in order to allow the user access to one or more services provided by the sponsor, a 3rd party service provider or the operator. For example, existing OSA standards, defined in 3GPP TS 23.198 [6] provide a comprehensive framework to support 3rd party applications. The framework supports security, authentication and authorisation of 3rd party providers, and open APIs to facilitate controlled access to SP's resources, QoS requests, charging and other capabilities. Whether the user pays the sponsor for the connectivity or not, in the context of sponsored IP-CAN connectivity, makes no difference with respect to the handling of end user charges for the connectivity. + +The following actors are involved in a scenario of sponsored connectivity: + +**Sponsor:** the one willing to take the operator's charge for connectivity. + +**Application Service provider:** the one providing the sponsored service. May coincide with the sponsor. + +**Operator:** the one providing connectivity. May also be service provider. + +**End user:** the one using the sponsored service. Is a subscriber at the operator. + +It is assumed the user has already a subscription for PDN access with a mobile operator. In particular, the following areas will be studied: + +- Capability for a service provider's application functions to authorize IP flows that are subject to a specific sponsorship. +- Capability to validate dynamic authorizations for sponsored IP flows . +- Capability to exclude the sponsored IP flows from the monitoring for user's volume cap. +- Capability to charge the end user, including pre-paid credits users, at a different rate when the service is sponsored (often, but not necessarily, free of charge) compared to non-sponsored usage of the same service. + +- Capability to create accounting and/or usage data records where the usage data associated with sponsorship is separated from other usage data. + +### 4.1.2 Alternative solutions + +#### 4.1.2.1 Alternative 1 + +A possible architecture for sponsored data connectivity is shown illustrated in Figure 4.1.2.1-1 in the non roaming case. In the roaming case a S9 reference point is present between the H-PCRF and the V-PCRF. + +![Architecture for sponsored data connectivity diagram](07b17a620c75522d53916a11e12d1bff_img.jpg) + +The diagram illustrates the architecture for sponsored data connectivity. At the top, a dashed box contains two components: 'Non-SIP ASP' and 'AF'. Below this box, the 'AF' is connected to a 'PCRF' via an 'Rx' interface. The 'PCRF' is connected to a 'PCEF' via a 'Gx' interface and to a 'BBERF' via a 'Gxx' interface. The 'BBERF' is connected to a 'UE' (User Equipment). A dashed line labeled 'Application level signaling' connects the 'UE' to the 'Non-SIP ASP'. + +Architecture for sponsored data connectivity diagram + +NOTE: The interface between the AF and Non-SIP ASP which requires sponsored data connectivity may be based on the OSA standards per 3GPP TS 23.198 [6] but is out of scope of this specification. A one to one mapping between the Non-SIP ASP and the AF is not needed as a single AF can be used to serve multiple Non-SIP ASPs. + +**Figure 4.1.2.1-1: Architecture for sponsored data connectivity** + +There are two scenarios for the Non-SIP ASP possible: the ASP is only involved in the application level signalling or the ASP is in addition involved in the user data exchange, i.e. the IP packets carrying the payload of the application. + +In the latter case it is possible to keep the decision about the duration of the sponsored data connectivity at the ASP so that the interaction with the PCRF follows the existing Rx procedures. The PCRF does only need to know the required information to identify the service (e.g. via the AF Application identifier and the AF Application event identifier) and to describe the sponsored IP flows that the ASP wants to get authorized. The ASP can initiate the Rx session termination once the sponsored usage of the ASP service can be stopped, e.g. if a download is complete. + +If the ASP is only involved in the application level signalling, the PCRF needs to know in addition the information about the duration and/or the volume which is authorized by the ASP because the ASP does not necessarily know when the sponsored usage of the ASP service can be stopped. These parameters would have to be added to the Rx signalling. + +NOTE: Retransmissions should be taken into account in the duration/volume allowance given by the ASP. + +In both scenarios the charging systems and the PCRF need to be configured in the following way: + +- In case a Sponsor Identity is not used a service specific Charging Key and Monitoring Key has to be used for the sponsored IP flows (that is not shared with any other service of the UE in this PDN connection) so that the PCEF can generate separate accounting and/or usage data records. +- In case a Sponsor Identity is used to separate accounting and/or usage data records the same Charging Key and Monitoring Key may be used both for sponsored IP flows and for the IP flows that are not sponsored. The Sponsor Identifier will be used to correlate measurements from different users and for different services for accounting purposes. +- The PCRF needs to know the ASPs that have a business relationship with the operator and the policies that are related to them, primarily the QoS that is to be authorized for the sponsored IP flows. +- If the AF is in the operator's network and is based on the OSA/Parlay X GW as defined in TS 23.198 [6] OSA specification the PCRF is not required to verify that a trust relationship exists the operator and the 3rd party ASP + +##### 4.1.2.1.1 Reference points enhancements + +###### 4.1.2.1.1.1 AF - PCRF reference point (Rx) + +The Rx reference point between the AF and the PCRF is described in TS 23.203 [3]. The Rx reference point is further enhanced to optionally provide service information related to sponsored data connectivity. The following information shall be possible to provide over the Rx reference point: + +- Sponsor Identifier; +- Information identifying the application service provider and application; +- Optionally allowed volume of the sponsored connectivity and/or a time interval and whether the PCRF reports these events to the AF. + +###### 4.1.2.1.1.2 PCEF- PCRF reference point (Gx) + +The charging part of the PCC rule is augmented with the possibility to include the Sponsor Identity and Application Service Provider Identity with the rule. + +###### 4.1.2.1.1.3 PCEF - OCS and PCEF - OFCS reference points (Gy and Rf/Gz) + +The normal usage reporting per user (a.k.a. containers) is augmented with the Sponsor Identity and Application Service Provider Identity. + +**Editor's note: This is potentially SA WG5 domain.** + +For Gy the quota handling is separate for Charging keys accompanied by a Sponsor Identity and Application Service Provider Identity. + +In the charging domain, reports are extracted and consolidated, possibly from all users when that applies for the sponsored service, to form the usage data for a Service Identifier. The Sponsor Identity, The Application Service Provider Identity, the Service Identifier and the usage data suffice to make the settlement with the sponsor and Application Service Provider. + +###### 4.1.2.1.1.4 PCRF - SPR reference point (Sp) + +The SPR includes profiles for sponsor data connectivity containing Sponsor Identities and list of applications per Application Service Provider. + +##### 4.1.2.1.2 Call flows + +###### 4.1.2.1.2.1 General + +This clause contains call flows to demonstrate the PCC interaction for sponsored data connectivity under various scenarios, including rule installation when sponsored data connectivity is activated, rule modification when sponsored data connectivity is extended, usage reporting for sponsored data connectivity, and rule remove when sponsored data connectivity is terminated. + +###### 4.1.2.1.2.2 Call flow for sponsored data connectivity rule installation + +![Sequence diagram showing the call flow for sponsored data connectivity rule installation between UE, IP-CAN, PCRF, and AF.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg) + +``` +sequenceDiagram + participant UE + participant IP-CAN + participant PCRF + participant AF + + Note left of UE: 1. UE attaches to the IP-CAN + UE->>IP-CAN: + Note right of IP-CAN: 2. IP-CAN session and gateway control session established + IP-CAN->>PCRF: + Note left of UE: 3. UE connects to the ASP server and request service + UE->>AF: + Note right of AF: 4. ASP triggers Dynamic data connection + AF->>PCRF: 5. Rx (Id, flow info, Volume allowance, specific-action) + PCRF->>AF: 6. Ack + Note right of PCRF: 7. Rule derivation + PCRF->>IP-CAN: 8. Rule provisioning (rule, allowances, Event-trigger) + Note left of IP-CAN: 9. Rule installation + IP-CAN->>PCRF: 10. Ack + Note left of UE: 11. UE receives the desired service + UE->>AF: +``` + +Sequence diagram showing the call flow for sponsored data connectivity rule installation between UE, IP-CAN, PCRF, and AF. + +**Figure 4.1.2.1.2.2-1: Call flow for sponsored data connectivity rule installation** + +1. The UE attaches to the IP-CAN following the normal procedures specific to the IP-CAN. +2. The PCEF and/or the BBERF establish IP-CAN session and/or gateway control session toward the PCRF following the procedures described in TS 23.203 [3]. The UE's IP connection may have a limited amount of data usage. +3. The UE connects to the 3rd party ASP server and requests services from the ASP. +4. The ASP server decides to sponsor the data connection used to access the ASP service for the user and provide dynamic sponsoring information, as agreed with the operator, to the AF within the operator's network. The dynamic sponsoring information includes the user identity to be sponsored (e.g. the IP address), the IP flow information to be sponsored, Sponsor Identity, Application Service Provider Identifier. Optionally the usage amount to be sponsored and the threshold request related to the sponsored data connectivity. + +5. For each sponsored service occasion, the AF establishes an Rx session toward the PCRF as described in TS 23.203 [3] and provides the identity of the AF, a Sponsor Identity, an Application Identity, the user identity and the service information optionally including volume allowance and specific-actions related to the service. +6. The PCRF authorizes and acknowledges the service information received from the AF. +7. The PCRF derives PCC/QoS rules related to the sponsored data connectivity and may take into account the Sponsor Identity and Application Identifier. +8. The PCRF provision the rules and event triggers for the sponsored data connectivity to the PCEF/BBERF within the IP-CAN. +9. The PCEF/BBERF installs the provisioned rules and event triggers. +10. The PCEF/BBERF sends acknowledgement to the PCRF. +11. The UE uses the sponsored connectivity to receive the desired service from the ASP. + +###### 4.1.2.1.2.2 Call flow for sponsored data connectivity usage report + +This call flow is only required if the ASP is not involved in the user data exchange and thus the PCRF needs to manage the information about the duration and/or the volume which is authorized by the ASP. + +![Sequence diagram showing the call flow for sponsored data connectivity usage report. Lifelines: UE, IP-CAN, PCRF, AF. The sequence starts with a message '1. Volume allowances reached' from IP-CAN to PCRF. PCRF sends '2. Event report (volume reached)' to IP-CAN. IP-CAN sends '3. Ack (update/remove/keep)' to PCRF. PCRF sends '4. Rx (specific action)' to AF. AF sends '5. Ack' to PCRF.](5e92d9e8e9ce204e405bff2367f88176_img.jpg) + +``` +sequenceDiagram + participant UE + participant IP-CAN + participant PCRF + participant AF + Note right of IP-CAN: 1. Volume allowances reached + IP-CAN->>PCRF: 2. Event report (volume reached) + PCRF->>IP-CAN: 3. Ack (update/remove/keep) + PCRF->>AF: 4. Rx (specific action) + AF->>PCRF: 5. Ack +``` + +Sequence diagram showing the call flow for sponsored data connectivity usage report. Lifelines: UE, IP-CAN, PCRF, AF. The sequence starts with a message '1. Volume allowances reached' from IP-CAN to PCRF. PCRF sends '2. Event report (volume reached)' to IP-CAN. IP-CAN sends '3. Ack (update/remove/keep)' to PCRF. PCRF sends '4. Rx (specific action)' to AF. AF sends '5. Ack' to PCRF. + +**Figure 4.1.2.1.2.2-1: Call flow for sponsored data connectivity usage report** + +1. At one point of time, the volume allowance set for the sponsored data connectivity is reached. +2. The PCEF sends an IP-CAN session modification request toward the PCRF including an event trigger to indicate that the data usage has reached the volume threshold. +3. The PCRF, based on information received from the AF, may update the threshold or remove the PCC rule and QoS rule related to the sponsored connectivity; the PCRF may also keep the same rules active but notify the AF as described in the subsequent steps. +4. The PCRF sends an notification message to notify the AF that data usage has reached threshold. +5. The AF acknowledge the notification from the PCRF. If needed, the AF may follow the procedures described in clause 4.1.2.1.2.3 to extend the sponsorship or the procedures described in clause 4.1.2.1.2.4 to terminate the sponsorship. + +###### 4.1.2.1.2.3 Call flow for sponsored data connectivity extension + +This call flow is only required if the ASP is not involved in the user data exchange and thus the PCRF needs to manage the information about the duration and/or the volume which is authorized by the ASP. + +![Sequence diagram for sponsored data connectivity extension. Lifelines: UE, IP-CAN, PCRF, AF. The sequence starts with the AF receiving a trigger from the ASP (1). The AF sends an Rx update with volume allowance to the PCRF (2). The PCRF sends an Ack to the AF (3). The PCRF sends a rule update with volume allowance to the IP-CAN (4). The IP-CAN sends an Ack to the PCRF (5).](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +sequenceDiagram + participant UE + participant IP-CAN + participant PCRF + participant AF + Note right of AF: 1. Receive trigger from ASP to increase Volume allowance or receive report from PCRF. + AF->>PCRF: 2. Rx update (Volume allowance) + PCRF->>AF: 3. Ack + PCRF->>IP-CAN: 4. Rule update (Volume allowance) + IP-CAN->>PCRF: 5. Ack + +``` + +Sequence diagram for sponsored data connectivity extension. Lifelines: UE, IP-CAN, PCRF, AF. The sequence starts with the AF receiving a trigger from the ASP (1). The AF sends an Rx update with volume allowance to the PCRF (2). The PCRF sends an Ack to the AF (3). The PCRF sends a rule update with volume allowance to the IP-CAN (4). The IP-CAN sends an Ack to the PCRF (5). + +**Figure 4.1.2.1.2.3-1: Call flow for sponsored data connectivity extension** + +1. The AF receives trigger from the ASP to increase volume allowance or receives report from the PCRF to indicate that previously set threshold has been met. +2. The AF sends new allowance information to the PCRF to extend the previous sponsored connectivity. +3. The PCRF sends acknowledgement to the AF. +4. The PCRF updates the corresponding PCC rules with new volume allowance information received. +5. The PCEF acknowledges the updated PCC rules. + +###### 4.1.2.1.2.4 Call flow for sponsored data connectivity release + +When the AF receives a trigger from the ASP or an internal trigger to terminate the sponsorship, the AF terminates the Rx session as specified in TS 23.203 [3]. + +## 4.2 Key issue 2: Coherent access to Policy related databases + +### 4.2.1 Description + +To enable operator policies, currently a number of logical databases have to be accessed. These include HSS, SPR and possible databases tied to ANDSF functionality. While implementation of many of these databases will continue to be deployment specific it is possible to consolidate them logically by providing a single logical interface to access them. + +### 4.2.2 Alternative solutions + +#### 4.2.2.1 SPR as an Application Front-End of the UDC Architecture + +In order to provide coherent accesses to operator policy databases, the SPR shall be part of the 3GPP UDC architecture. According to TS 22.101 [4], the UDC concept supports a layered architecture, separating the data from the application logic in the 3GPP system. In that way user data is stored in a logically unique repository allowing access from core and service layer entities, named application front-ends + +For such purpose, the SPR shall be an Application Front-End according to TS 23.335 [5]. This SPR-FE shall support the Ud reference point for querying, creating, updating or deleting data from the UDR. The SPR-FE shall make also use of the Ud reference point for subscribing to and receiving notifications from the UDR. + +The SPR Application Front-End shall interact with the PCRF via Sp reference point. + +![Diagram of SPR as Application Front-End within the User Data Convergence architecture. The diagram shows a PCRF connected via the Sp reference point to a UDC (User Data Convergence) block. Inside the UDC block, there are three entities: SPR-FE, Appl-FE, and Appl-FE. The SPR-FE is connected to the UDR (User Data Repository) via the Ud reference point. The Appl-FE entities are also connected to the UDR via the Ud reference point.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` +graph TD; PCRF[PCRF] -- Sp --> UDC; subgraph UDC; SPR-FE[SPR-FE]; Appl-FE1[Appl-FE]; Appl-FE2[Appl-FE]; UDR[UDR]; SPR-FE -- Ud --> UDR; Appl-FE1 -- Ud --> UDR; Appl-FE2 -- Ud --> UDR; end; +``` + +Diagram of SPR as Application Front-End within the User Data Convergence architecture. The diagram shows a PCRF connected via the Sp reference point to a UDC (User Data Convergence) block. Inside the UDC block, there are three entities: SPR-FE, Appl-FE, and Appl-FE. The SPR-FE is connected to the UDR (User Data Repository) via the Ud reference point. The Appl-FE entities are also connected to the UDR via the Ud reference point. + +**Figure 4.2.2.1-1: SPR as Application Front-End within the User Data Convergence architecture** + +In order to fulfil the requirements that UDC architecture sets into the Application Front-Ends (clause 4.1 of TS 22.101 [4]), the SPR-FE shall be a subscriber dataless entity. + +#### 4.2.2.2 PCRF as an Application Front-End of the UDC Architecture + +An alternative solution is that the PCRF as an entity without persistent subscriber data has direct access to the User Data Repository (UDR) which is part of the 3GPP UDC architecture. Sp reference point and SPR entity would disappear in such a configuration. PCC related persistent subscriber data are stored in the UDR while the related application logic is implemented in the PCRF. + +![Diagram of PCRF as Application Front-End within the User Data Convergence architecture. The PCRF is connected to a UDC box. Inside the UDC box, there are two Appl-FE boxes and a UDR box. The Appl-FE boxes are connected to a common horizontal line, which is then connected to the UDR box via a vertical line labeled 'Ud'. The PCRF is also connected to this same horizontal line inside the UDC box.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +graph TD + PCRF[PCRF] --- UDC[UDC] + subgraph UDC + direction TB + ApplFE1[Appl-FE] --- HLine(( )) + ApplFE2[Appl-FE] --- HLine + HLine --- Ud[Ud] + Ud --- UDR[UDR] + end + PCRF --- HLine + style HLine fill:none,stroke:none + +``` + +Diagram of PCRF as Application Front-End within the User Data Convergence architecture. The PCRF is connected to a UDC box. Inside the UDC box, there are two Appl-FE boxes and a UDR box. The Appl-FE boxes are connected to a common horizontal line, which is then connected to the UDR box via a vertical line labeled 'Ud'. The PCRF is also connected to this same horizontal line inside the UDC box. + +**Figure 4.2.2.2-1: PCRF as Application Front-End within the User Data Convergence architecture** + +CT WG4 concluded that the PCRF meets the requirements of an application front end. Consequently, this alternative does fulfil 3GPP UDC requirements as they are specified in TS 22.101 [4], clause 4.11. While the PCRF is not a subscriber dataless entity, due to its managing the user context for IP-CAN sessions, it only stores user data temporarily while an IP-CAN session for the user is ongoing. When no IP-CAN session is ongoing for a user, no user data need to be kept in the PCRF. + +In this use case the PCRF shall support the Ud reference point instead of Sp to access PCC related data stored in the UDR. It shall also use the Ud reference point for subscribing to and receiving notifications from the UDR. + +### 4.2.3 Comparison of alternatives + +According to the CT WG4 evaluation both alternatives describe valid architectures to integrate PCC related subscriber data into the UDC architecture and to access these data from the UDR. + +As the PCRF can be seen as a network element, which represents pure application logic with no persistent data storage functionality but with user data access towards an external database, it may be assumed to perform the functionality of an application frontend and access the user data via the Ud interface directly from the UDR. + +On the other hand PCC implementations may already exist where the Sp interface has been implemented in a vendor specific manner. In those cases, without impacting the existing PCRF implementation, PCC related persistent subscriber data stored in the SPR can be moved to the UDR with the SPR migrating to a pure Application Frontend from the UDC point of view that interworks between Sp and Ud interface. + +### 4.2.4 Conclusion + +The alternative architecture options as described in clauses 4.2.2.1 and 4.2.2.2 are both valid. Whether the one or other is chosen depends on the actual network deployment. + +If the SPR is used in a network to store the PCC related subscriber data, introducing the UDC concept (i.e. the UDR as centralized subscriber database) can be done in an evolutionary step by migrating from the existing SPR database to a SPR Application Frontend that provides interworking between Sp and Ud interfaces. This alternative is covered by the general UDC system architecture that can be found in TS 23.335 [5]. + +NOTE: The SPR information model has to be replaced by an appropriate UDR information model. + +Alternatively data stored in the SPR can be moved to the UDR requiring the PCRF to support the Ud interface in order to fetch PCC related subscriber data instead of Sp. This architectural option needs to be documented in TS 23.203 [3], introducing the UDR as an alternative to the existing SPR and Ud as alternative to Sp. + +## 4.3 Key issue 3: QoS and gating control based on spending limits + +### 4.3.1 Description + +The following use case has been identified, which requires the PCRF to perform QoS and gating control decisions based on information only available in the OCS: + +- **QoS control based on spending limits** - ability to change the QoS level based on spending limits. Example scenario: the subscriber plan allows for high QoS up to \$2 per day and a lower QoS beyond that. + +#### 4.3.1.1 Common Principles + +These principles apply to all of the proposed alternative solutions. Signalling may take place directly between OCS and PCRF or via PCEF as outlined in the alternative solutions. + +- A counter as defined in TS 32.296 [7] shall exist in the ABMF within the OCS that tracks a subscriber's spend over a period of time. +- The OCS may have more than one counter per subscriber. Each counter can track a subscriber's overall spend or that of an individual service. An identification mechanism will be required to differentiate counters. +- Counter management is the responsibility of the OCS, including any associated threshold value(s) (e.g. \$2). +- Policy decisions relating to gating and QoS are the responsibility of the PCRF. +- When the counter value reaches an associated threshold, the OCS notifies the PCRF. + +**Editor's note: Further information being passed from OCS to PCRF is not excluded by this principle.** + +- At least two conditions shall trigger information flow between OCS and PCRF in relation to these use cases: + - On IP-CAN session establishment, the OCS will inform the PCRF what thresholds have already been reached, allowing the PCRF to make an initial policy decision for the session. + - When a threshold is reached mid-session, the OCS shall notify the PCRF triggering modification of the subscriber's policy appropriately. + +### 4.3.2 Alternative solutions + +#### 4.3.2.1 Alternative solution 1 - configuration based solution + +A QoS control based on spending limits can be realized based on existing PCC and online charging functionality. This requires however, that the OCS and the PCRF are configured in the following way: + +- A service specific Charging Key has to be used for the service for the time the service has not reached its spending limits. This service specific Charging Key cannot be shared with any other service of the UE in this PDN connection.- A second Charging Key has to be available for the service after reaching the spending limit (i.e. the "out of credit" event). This Charging Key can only be shared with other services if the service can remain with the current setting until the service is terminated. If the service should ever return to the original setting (e.g. after a certain time interval has been passed), the second Charging Key cannot be shared with any other service. The OCS can then instruct the PCRF to return to the original setting by denying credit for this second Charging Key. +- The PCRF needs to apply a second QoS authorization after it gets informed about the "out of credit" event. +- The OCS needs to store the spending limits for the service specific Charging Key when the credit management interaction for the service is terminated. + +- The OCS needs to reset the spending limit for the service specific Charging Key after the corresponding time interval has been passed. + +Editor's note: Configuration efforts (e.g. increased number of Charging Keys) and potential functionality enhancements (e.g. accounting of packets when applying the termination action) needs to be further analyzed. + +If the PCRF and the OCS are configured appropriately, the QoS control based on spending limits proceeds in the following way: + +- The PCRF applies a service specific Charging Key A for the service (that is not shared with any other service of the UE in this PDN connection) together with the QoS that is intended to be used before the spending limit is reached. In addition, the PCRF sets the "out of credit" event trigger. +- The OCS receives the Charging Key A during the credit management interaction and starts (or continues) to measure the parameter that is subject to the spending limit control (i.e. time, volume and/or event) in addition to the normal charging functionality. +- Once the OCS detects that the spending limit is reached, it denies any further credit to the PCEF. In addition, the OCS may set the Termination Action to "Allowing the packets to pass through" to enable the continuation of the service. +- The PCEF reports the "out of credit" event to the PCRF together with the corresponding PCC rule. +- The PCRF can now react and modify the PCC rule according to the operator configuration. The PCRF would select a different Charging Key B and the QoS that has to be applied after reaching the spending limit. +- The PCEF enforces the modifications for the PCC rule and may need to modify the bearer or even bind the PCC rule to a different bearer. In addition, the new Charging Key B is used for the credit management. +- The OCS receives the new Charging Key B and continues to grant credits for this service. +- If the OCS wants the service to return to the original QoS (e.g. after the time interval that is relevant for the spending limit has been passed), the OCS may apply the very same mechanism (i.e. denying credit, setting Termination Action). The PCRF would get informed about it in the very same way and modify the PCC rule back to the original QoS and the Charging Key A. + +#### 4.3.2.2 New reference point (Sy) between PCRF and OCS + +##### 4.3.2.2.1 General + +A solution is to define a new reference point Sy between the PCRF and the OCS to enable transport of indications about charging related events from the OCS to the PCRF. + +![Overall PCC architecture (non-roaming) including the Sy reference point diagram](21ad58fee90f2be50708ff541d225507_img.jpg) + +The diagram illustrates the overall PCC architecture (non-roaming) including the Sy reference point. It shows the following components and interfaces: + +- Subscription Profile Repository (SPR)**: Connected to the PCRF via the **Sp** reference point. +- AF (Application Function)**: Connected to the PCRF via the **Rx** reference point. +- Policy and Charging Rules Function (PCRF)**: The central element, connected to: + - SPR via **Sp** + - AF via **Rx** + - BBERF via **Gxx** + - Gateway (PCEF) via **Gx** + - Online Charging System (OCS) via the new **Sy** reference point (highlighted in red) +- BBERF (Bearer Binding and Event Reporting Function)**: Connected to the PCRF via **Gxx**. +- Gateway (containing PCEF)**: Connected to the PCRF via **Gx**. It also has interfaces: + - Gy** to the Service Data Flow Based Credit Control (part of the OCS) + - Gz** to the Offline Charging System (OFCS) +- Online Charging System (OCS)**: Enclosed in a dashed box, containing the **Service Data Flow Based Credit Control**. It connects to the PCRF via **Sy** and to the Gateway via **Gy**. +- Offline Charging System (OFCS)**: Connected to the Gateway via **Gz**. + +Overall PCC architecture (non-roaming) including the Sy reference point diagram + +Figure 4.3.2.2.1-1: Overall PCC architecture (non-roaming) including the Sy reference point + +![Figure 4.3.2.2.1-2: Overall PCC architecture including the Sy reference point roaming with PCEF in visited network (local breakout).](4356776ca004ecba5d599667a155d7d4_img.jpg) + +The diagram illustrates the Overall PCC architecture for a roaming scenario with local breakout. It shows the following components and interfaces: + +- SPR (Subscription Profile Repository):** Located in the HPLMN, it connects to the H-PCRF via the **Sp** reference point. +- H-PCRF (Policy and Charging Rules Function):** Located in the HPLMN, it connects to the SPR via **Sp**, to an AF via **Rx**, to the V-PCRF via **S9**, and to the OCS via the **Sy** reference point. +- AF (Application Function):** Located in the HPLMN, it connects to the H-PCRF via **Rx**. +- OCS (Online Charging System):** Located in the HPLMN, it contains a **Service Data Flow Based Credit Control** function. It connects to the H-PCRF via **Sy** and to the PCEF via **Gy**. +- V-PCRF (Policy and Charging Rules Function):** Located in the VPLMN, it connects to the H-PCRF via **S9**, to an AF via **Rx**, to the BBERF via **Gxx**, and to the PCEF via **Gx**. +- AF:** Located in the VPLMN, it connects to the V-PCRF via **Rx**. +- BBERF (Bearer Binding and Event Reporting Function):** Located in the VPLMN, it connects to the V-PCRF via **Gxx**. +- Gateway:** Located in the VPLMN, it contains a **PCEF (PDN Connection Entitlement Function)**. The PCEF connects to the V-PCRF via **Gx**, to the OCS via **Gy**, and to the OFCS via **Gz**. +- OFCS (Offline Charging System):** Located in the HPLMN, it connects to the PCEF via **Gz**. + +Figure 4.3.2.2.1-2: Overall PCC architecture including the Sy reference point roaming with PCEF in visited network (local breakout). + +**Figure 4.3.2.2.1-2: Overall PCC architecture including the Sy reference point roaming with PCEF in visited network (local breakout)** + +##### 4.3.2.2.2 PCRF contacting the OCS (PCRF-Centric approach) + +###### 4.3.2.2.2.1 Session scope + +For efficient communication and to be able to support multiple PDN-connections of a user the scope of the Sy connection should be organised on a per subscriber ID and PDN identifier basis, i.e. (at least) all PDN-connections of a UE to the same APN are bound to the same Sy session. This is possible since multiple PDN-connections to the same APN are always controlled by the same PCRF since PCC Rel-8. + +###### 4.3.2.2.2.2 Session initiation + +At IP-CAN session establishment, according to TS 23.203 [3], Gx interactions take place prior to Gy interactions. For the PCRF to be able to provide correct policies at IP-CAN session establishment it is necessary for the PCRF to interact with the OCS prior to sending acknowledge of IP-CAN session establishment to the PCEF. Additionally it is the PCRF that is aware of if the policies of an IP-CAN session are dependent on charging related information. Sy Session Establishment should therefore be initiated by the PCRF. + +The Sy reference point allows the PCRF to request and subscribe to indications about charging related events that affect session and service policies of PDN connections for different users and PDNs. + +The OCS shall support to bind a Sy session with associated Gy sessions and shall notify the PCRF over the Sy interface whenever there is charging related event occurring that the PCRF has subscribed to. + +###### 4.3.2.2.2.3 Information exchange + +The Sy reference point shall support to provide the following indications: + +- Provisioning of indication based on credit balance (e.g. when OCS decides that a prepaid subscriber has reached a balance limit) +- Provisioning of indication per rating group or per IP-CAN session based on previously consumed volume or spending limits (e.g. when OCS decides that a previously consumed volume or spending limit per period has reached a certain value). + +###### 4.3.2.2.2.3.1 Charging Status Reports + +Provisioning of Charging Status Reports is based on the assumption that that the OCS maintains the necessary counter(s) used to track spending between sessions. + +The OCS maintains pre-configured counter(s) with an associated threshold, which it resets according to a known time schedule. Counters could be applicable either per subscriber, per subscriber and active PDN or for a group of services for a certain subscriber. + +The identities of the counters that are relevant for a policy decision are stored in the PCRF or in the SPR. The PCRF is configured with the actions associated with the counter status that is received from OCS. + +The request and provisioning of Charging Status Reports may be used for: + +The initial request for counter state at IP-CAN session establishment. + +The notification from the OCS to the PCRF of threshold reached by OCS. When counters that are applicable either for a single service or for a group of services are referenced over the Sy interface a new identifier called Policy-Counter-Id shall be used. All services that are mapped to the same Policy-Counter-Id will share the same counter state and applicable threshold values in the OCS. + +NOTE: The relation between a Policy-Counter-Id and the Charging Key could be 1-1. However it could also be assumed that services that share the same Charging Key may be associated with different Policy-Counters i.e. although they are rated in the same way they are subject to different actions regarding (e.g. QoS and gating) and are therefore counted separately. + +When a certain threshold has been reached (e.g. daily spending limit of 2\$ reached) in the OCS and/or when a certain threshold has been increased or the accumulated usage is reset the OCS shall provide the new Policy Counter Status to the PCRF for the associated Policy Counter or for the associated UE and active PDN. + +The PCRF shall based on the counter status apply operator defined actions, e.g. downgrade the QoS, for affected IP-CAN Sessions and/or PCC-rules and provide this as policy decisions to the PCEF and to the BBERF (if applicable). + +###### 4.3.2.2.2.4 Roaming + +The Sy reference point should support scenarios where a UE is located in a HPLMN (figure 4.2.2.2-1), roaming with home routed or roaming with visited access (figure 4.3.2.2.1-2). For roaming with visited access the Sy reference point is defined between the H-PCRF and the OCS in the HPLMN. With this approach Sy will be a PLMN internal reference point regardless of if the user is roaming or accessing via the HPLMN. + +##### 4.3.2.2.2.5 Signalling flows + +###### 4.3.2.2.2.5.1 General + +This clause contains signalling flows to demonstrate the PCC interaction to request charging status reports and to provide charging status reports over the Sy reference point. The Sy reference point supports the following functions: + +- Request from PCRF to OCS on the initial Policy Counter Status for a certain subscriber or for a certain subscriber and PDN connection.; +- Reports from the OCS to the PCRF on the Policy Counter Status for a certain subscriber or for a certain subscriber and PDN connection. + +###### 4.3.2.2.2.5.2 + +###### Changes to the IP-CAN Session establishment procedure + +![Sequence diagram for IP-CAN Session establishment procedure. Lifelines: GW (BBERF), GW (PCEF), V-PCRF, H-PCRF, SPR, OCS. The diagram shows 14 steps, with steps 1-5 grouped in a dashed box labeled 'Gateway Control Session Establishment (case 2a and 2b)'. Steps 6 and 7 are red dashed lines. Steps 8-14 are solid lines. A grey shaded area covers the V-PCRF lifeline.](3da1a07cb87051bf616c9876db958cf0_img.jpg) + +Roaming Scenarios + +``` + +sequenceDiagram + participant GW_BBERF as GW (BBERF) + participant GW_PCEF as GW (PCEF) + participant V_PCRF as V-PCRF + participant H_PCRF as H-PCRF + participant SPR as SPR + participant OCS as OCS + + Note right of V_PCRF: Roaming Scenarios + + Note over GW_BBERF, H_PCRF: 1. Gateway Control Session Establishment (case 2a and 2b) + + GW_BBERF->>GW_PCEF: 2. Establish IP-CAN Bearer Request + GW_PCEF->>H_PCRF: 3. Indication of IP_CAN Session Establishment + H_PCRF-->>SPR: 4. Profile Request + SPR-->>H_PCRF: 5. Profile Response + H_PCRF-->>OCS: 6. Initial Charging Status Request + OCS-->>H_PCRF: 7. Initial Charging Status Report + H_PCRF->>GW_PCEF: 8. Policy Decision + GW_PCEF->>GW_BBERF: 9. Acknowledge IP CAN Session Establishment + GW_PCEF-->>OCS: 10. Credit Request + OCS-->>GW_PCEF: 11. Credit Response + GW_PCEF->>GW_BBERF: 12. Establish IP-CAN Bearer Response + GW_BBERF-->>GW_PCEF: 13. IP CAN Bearer Signaling + GW_PCEF-->>H_PCRF: 14. IP CAN Session Establishment Acknowledge + +``` + +Sequence diagram for IP-CAN Session establishment procedure. Lifelines: GW (BBERF), GW (PCEF), V-PCRF, H-PCRF, SPR, OCS. The diagram shows 14 steps, with steps 1-5 grouped in a dashed box labeled 'Gateway Control Session Establishment (case 2a and 2b)'. Steps 6 and 7 are red dashed lines. Steps 8-14 are solid lines. A grey shaded area covers the V-PCRF lifeline. + +Figure 4.3.2.2.2.5.2-1 + +1-5. IP-CAN Session Establishment as per TS 23.203 [3], clause 7.2. + +6. If the subscription data received from the SPR indicated that policy decisions are dependent on charging related information and if this is the first IP-CAN session for this subscriber then PCRF sends an Initial Charging Status Request towards the OCS. The PCRF includes the UE identifier and the Policy-Counter-Id(s) for which status is requested. The PCRF may optionally include PDN-id (e.g. APN), the UE IP address and subscribers to changes in the status of the Policy Counters in the OCS. + +**Editor's note:** The possibility for the OCS to report all the Policy-Counter-Status or only those relevant for a policy decision is FFS. + +- The OCS acknowledges the request by sending a Charging Policy Session Acknowledge and may notify whether threshold(s) have already been reached. + +8-11. Continued IP-CAN Session Establishment as per TS 23.203 [3], clause 7.2 + +###### 4.3.2.2.2.5.3 Changes to the IP CAN Session termination procedures + +![Sequence diagram illustrating the changes to the IP CAN Session termination procedures. The diagram shows interactions between GW(BBERF), GW(PCEF), V-PCRF, (H-)PCRF, AF, OCS, and SPR. The process is divided into initial steps (1), a main sequence (2-9), and concluding steps (10).](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg) + +``` + +sequenceDiagram + participant GW(BBERF) + participant GW(PCEF) + participant V-PCRF + participant (H-)PCRF + participant AF + participant OCS + participant SPR + + Note left of GW(BBERF): 1. Initial steps as described TS 23.203 clause 7.3.1 or 7.3.2 + Note right of (H-)PCRF: 3. Identify what Policy and Charging Rules are affected. + Note left of GW(PCEF): 4. Remove all Policy and Charging Rules + + Note over V-PCRF: 2. Indication of IP-CAN Session Termination + (H-)PCRF->>AF: 5. Notify loss of transmission. + AF-->>(H-)PCRF: 6. Notification response. + (H-)PCRF-->>OCS: 7. Final Charging Status Request + OCS-->>(H-)PCRF: 8. Final Charging Status Report + Note over V-PCRF: 9. Acknowledge IP-CAN Session Termination + Note left of GW(BBERF): 10. Concluding steps as described TS 23.203 clause 7.3.1 or 7.3.2 + +``` + +Sequence diagram illustrating the changes to the IP CAN Session termination procedures. The diagram shows interactions between GW(BBERF), GW(PCEF), V-PCRF, (H-)PCRF, AF, OCS, and SPR. The process is divided into initial steps (1), a main sequence (2-9), and concluding steps (10). + +Figure 4.3.2.2.2.5.3-1 + +1-6. IP-CAN Session Termination as per TS 23.203 [3] clause 7.3.1 or 7.3.2. + +- If this is the last IP-CAN session of a subscriber for the PDN-id the PCRF sends a Final Charging Status Request to cancel the subscription to changes in the status of the Policy Counters in the OCS. + +- The OCS acknowledges to the PCRF that the subscription is cancelled. + +9-10 Continued IP-CAN Session Termination as per TS 23.203 [3] clause 7.3.1 or 7.3.2. + +##### 4.3.2.2.2.6 + +###### Provisioning of notifications from OCS to PCRF + +![Sequence diagram for Provisioning of notifications from OCS to PCRF. Lifelines: GW(PCEF), V-PCRF, (H-)PCRF, OCS, AF. The sequence starts with OCS detecting a threshold (1), sending a Charging Status Report to (H-)PCRF (2), which then sends another Charging Status Report to V-PCRF (3). Finally, a PCRF initiated IP-CAN session modification procedure is triggered (4).](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg) + +``` + +sequenceDiagram + participant GW(PCEF) + participant V-PCRF + participant (H-)PCRF + participant OCS + participant AF + Note right of OCS: 1. Detection of threshold has been passed + OCS->>(H-)PCRF: 2. Charging Status Report + (H-)PCRF->>V-PCRF: 3. Charging Status Report + Note over GW(PCEF), V-PCRF: 4. PCRF initiated IP-CAN session modification procedure + +``` + +Sequence diagram for Provisioning of notifications from OCS to PCRF. Lifelines: GW(PCEF), V-PCRF, (H-)PCRF, OCS, AF. The sequence starts with OCS detecting a threshold (1), sending a Charging Status Report to (H-)PCRF (2), which then sends another Charging Status Report to V-PCRF (3). Finally, a PCRF initiated IP-CAN session modification procedure is triggered (4). + +Figure 4.3.2.2.2.6-1 + +1. The OCS detects that the status of a Policy-Counter-Id(s) has changed and the PCRF requested notifications of changes in the status of the policy counters. +2. The OCS sends a Charging Status Report to the PCRF. The OCS sends the Policy-Counter-Status(s) per each Policy-Counter-Id(s) that has changed. The Policy-Counter-Status received from the OCS overrides the Policy-Counter-Status stored for a certain Policy-Counter-Id in the PCRF. +3. The PCRF acknowledges the Charging Policy Report. +4. A PCRF initiated IP-CAN Session modification procedure may occur as a result from the received report. + +###### 4.3.2.2.2.7 + +###### Intermediate Charging Status Request + +![Sequence diagram for Intermediate Charging Status Request. Lifelines: GW(PCEF), V-PCRF, (H-)PCRF, OCS, AF. The sequence starts with a decision for a charging policy request (1), followed by an Intermediate Charging Status Request from (H-)PCRF to OCS (2), and an Intermediate Charging Status Report from OCS to (H-)PCRF (3). This leads to a policy decision (4), which then triggers a PCRF initiated IP-CAN session modification procedure (5).](04dc3838022e96d8d5548bb1b777b38c_img.jpg) + +``` + +sequenceDiagram + participant GW(PCEF) + participant V-PCRF + participant (H-)PCRF + participant OCS + participant AF + Note right of (H-)PCRF: 1. Decision for Charging Policy Request + (H-)PCRF->>OCS: 2. Intermediate Charging Status Request + OCS->>(H-)PCRF: 3. Intermediate Charging Status Report + Note right of (H-)PCRF: 4. Policy Decision + Note over GW(PCEF), V-PCRF: 5. PCRF initiated IP-CAN session modification procedure or concluding steps of PCEF initiated IP-CAN Session modification + +``` + +Sequence diagram for Intermediate Charging Status Request. Lifelines: GW(PCEF), V-PCRF, (H-)PCRF, OCS, AF. The sequence starts with a decision for a charging policy request (1), followed by an Intermediate Charging Status Request from (H-)PCRF to OCS (2), and an Intermediate Charging Status Report from OCS to (H-)PCRF (3). This leads to a policy decision (4), which then triggers a PCRF initiated IP-CAN session modification procedure (5). + +Figure 4.3.2.2.2.7-1 + +1. The PCRF decides based on interaction with the SPR, AF, BBERF (if applicable) or the PCEF that the need for Charging Status Reports of a user has changed. +2. The PCRF sends an Intermediate Charging Status Request to the OCS, including the applicable Policy-Counter-Id(s). + +Editor's note: The possibility for the OCS to report all the Policy-Counter-Status or only those relevant for a policy decision is FFS. + +3. The OCS acknowledges the Intermediate Charging Status Request that includes the Policy-Counter-Status per Policy-Counter-Id provided by the PCRF in the Intermediate Charging Status Request. +4. The PCRF makes an updated policy decision based on the received report from the OCS. The Policy-Counter-Status received from the OCS overrides the Policy-Counter-Status stored for a certain Policy-Counter-Id in the PCRF. +5. In case the procedure was triggered by an indication of IP-CAN Session Modification procedure the PCRF concludes this procedure as per TS 23.203 [3], clause 7.4.1 steps 10-18. + +##### 4.3.2.2.3 OCS contacting the PCRF (OCS-Centric approach) + +#### 4.3.2.3 Alternative solution 3 - enhancing Gy and Gx + +A QoS control based on spending limits can be realized by enhancing the Gy and Gx procedures with additional functionality and parameters. + +The solution relies on the following procedures: + +##### **A. OCS threshold/s reached notification on IP-CAN session establishment** + +Gy: Credit Request procedure + +The Credit Request procedure is initiated by the PCEF in accordance with the TS 23.203 [3] IP CAN session establishment procedure Session + +The OCS includes in the Credit Request Response message and indication that the value of counter/s associated with spending limits has reached a threshold. + +Gx: IP CAN Session Modification Procedure + +When the PCEF receives an indication from the OCS that a threshold/s has been reached it initiates the IP CAN session Modification request to request PPC rules re-authorization due to spending threshold/s reached. + +The PCC determines the new/modified PCC rules and responds to the PCRF. + +Gy: The PCEF may initiate the Credit Request procedure with the OCS + +##### **B. OCS thresholds reached notification in mid-session** + +Gy: (Credit) Re-Authorization- Request procedure + +The OCS initiates the Re-Authorization- Request procedure (according to TS 32.299 [8]) when threshold/s has been reached + +Gx: IP CAN Session Modification Procedure + +When the PCEF receives an indication from the OCS that a threshold/s has been reached it initiates the IP CAN session Modification request to request PPC rules re-authorization due to spending threshold/s reached. + +The PCC determines the new/modified PCC rules and responds to the PCRF. + +Gy: (Credit) Re-Authorization- Request Response + +The PCEF sends the new/modified PCC rules to the OCS + +NOTE: The Session between the PCEF and the OCS is not impacted by this solution and it is terminated as part of the TS 23.203 [3] IP CAN Session termination procedure. + +### 4.3.3 Conclusion + +Alternative 2 has the advantage of causing no increase in signalling load at the PCEF, along with the fact that it allows H-PCRF and H-OCS to communicate directly in the LBO roaming scenario, simplifying interworking in that case. + +The impact of adding the new Sy reference point is therefore seen as lower than that of the other alternative solutions, both in terms of complexity and network signalling overhead. + +The Sy based solution where PCRF initiates Sy interaction (alternative 2) shall be used to achieve the aims of the key issue. + +NOTE 1: The behaviour of the OCS and PCRF on Sy failure shall be studied during the resulting normative work. + +NOTE 2: No modification to the Gx and Gy reference points is required to resolve key issue #3 or due to the introduction of the Sy reference point. + +## 4.4 Key issue 4: Service Awareness and Privacy Policies + +### 4.4.1 Description + +The network may have policies related to specific services but currently it may not always become aware of usage of these services. The service unawareness can occur when there is no explicit service level signalling and hence no interaction between the Application Function and PCRF or when filters related to a service has not been installed in the PCEF. The user experience can be enhanced if the network becomes service aware and the network is able to apply service specific policies. Service traffic detection mechanisms helps achieve service awareness. Traffic detection functionality can be implemented by a standalone entity as well as be collocated with PCEF. Use of service traffic detection mechanism however may require user consent and for this purpose PCC architecture would have to be extended to include user privacy policies. + +### 4.4.2 Actions resulting from service detection + +Existing charging and enforcement actions based on PCC rules performed at the PCEF and defined in TS 23.203 [3] are still performed. Charging and enforcement actions based on PCC rules at the PCEF may be influenced by the detected services. Additionally, the following are examples of actions to be taken on the detected service: + +- Gating of the detected service traffic (either blocking or permitting unrestricted the detected service traffic) +- Traffic shaping of the detected service traffic +- Redirecting of detected service traffic (for services / protocols that permit redirection) + +### 4.4.3 Alternative solutions + +#### 4.4.3.1 Alternative 1 + +At the time of IP-CAN session establishment, the PCEF contacts the PCRF as per existing procedures. User privacy policy settings are received from the SPR together with the other subscriber related information (the management of the user privacy policy settings is out of scope). The PCRF checks the user privacy policy settings to see if usage of service traffic detection mechanism is allowed and for what services. If it is allowed the PCRF can instruct the Traffic Detection Function (TDF) on what services it should detect and if detection notification is required. After detecting a service with a service traffic detection mechanism, the TDF may inform the PCRF about the detected service, if detection notification is required. The PCRF can then react in the desired way with regard to the policy and charging control information for the detected traffic. + +A new mechanism/ parameter for instructing the TDF on what service traffic to detect needs to be defined. While the actual mechanism for the service traffic detection should not be standardized, TDF has to be able to detect the start and the end of the respective service and notify the PCRF correspondingly. + +NOTE 1: The potential mechanisms to enable steering of user traffic either to a particular TDF or to bypass this TDF are FFS. A key aspect of the evaluation will be the ability to ensure a subscriber's downlink traffic can be steered to the same TDF which is handling the uplink traffic. + +For a collocated PCEF/TDF, the existing PCC rule concept can be extended to include the parameters, which form an SDPR rule, that identifies the service to be detected. + +For a standalone TDF, a Service Detection and Policy (SDPR) rule used both to provide the instruction for service detection and the potential enforcement actions to be applied for the detected service need to be defined. + +It is proposed to use Application Identifier known both to PCRF and to TDF as a set of characteristics of the service, required for detection. An Application identifier can be mapped by the TDF to a pre provisioned service related information e.g. application layer protocol e.g. http, sip, P2P, and TCP/UDP port number / ranges to be detected. + +NOTE 2: Application identifier communicated by the PCRF can be mapped to variety of information pre-provisioned into the TDF, that can allow for expansion of TDF role to be used with new protocols and services without having to standardize new parameters across the interface. + +Two scenarios are addressed below: + +- Solicited service reporting: The TDF is instructed on which services to detect, report to the PCRF and the actions to be enforced on a per IP-CAN session basis. +- Unsolicited service reporting: The TDF is pre-configured on which services to detect and report. The enforcement is done in the PCEF. It is assumed that user consent is not required. + +![Figure 4.4.3.1-1: Architecture including TDF. The diagram shows a PCRF at the top connected to three entities below: BBERF, PCEF, and TDF. The PCRF is connected to the BBERF via the Gxx interface, to the PCEF via the Gx interface, and to the TDF via the Gxd interface. The BBERF, PCEF, and TDF are connected in a horizontal line. The PCEF and TDF are enclosed in a dashed box, indicating they are part of the same gateway.](8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg) + +``` + +graph TD + PCRF[PCRF] -- Gxx --> BBERF[BBERF] + PCRF -- Gx --> PCEF[PCEF] + PCRF -- Gxd --> TDF[TDF] + BBERF --- PCEF + PCEF --- TDF + subgraph Gateway + PCEF + TDF + end + +``` + +Figure 4.4.3.1-1: Architecture including TDF. The diagram shows a PCRF at the top connected to three entities below: BBERF, PCEF, and TDF. The PCRF is connected to the BBERF via the Gxx interface, to the PCEF via the Gx interface, and to the TDF via the Gxd interface. The BBERF, PCEF, and TDF are connected in a horizontal line. The PCEF and TDF are enclosed in a dashed box, indicating they are part of the same gateway. + +**Figure 4.4.3.1-1: Architecture including TDF** + +NOTE 3: This architecture option can be applied for a stand-alone TDF and a TDF that is collocated with the PCEF in the same gateway. + +In case of collocated TDF, the Gxd interface doesn't apply. + +A new reference point Gxd between standalone TDF and PCRF that enables gating, shaping and redirection functions in the TDF is defined. + +##### 4.4.3.1.1 Reference Points + +The Gxd reference point enables communication between TDF and PCRF for the purpose of: + +- Reporting of the start and the stop of a detected services and transfer of service data flow descriptions for detected services from the TDF to the PCRF. +- Signalling of Service Detection and Policy Rules from the PCRF for the purpose of traffic detection and enforcement at the TDF to the PCRF. Functions are provided to establish a TDF session, to modify a TDF session from the PCRF and to terminate a TDF session. + +##### 4.4.3.1.2 Functional entities + +The TDF performs service detection and reporting of detected service and its service data flow description to the PCRF. + +For those cases where service data flow description is not possible to be provided by the TDF to the PCRF, the TDF performs gating, redirection and bandwidth limitation for the detected services. The existing PCEF/BBERF functionality remains as defined in TS 23.203 [3]. + +For those cases where service data flow description is provided by the TDF to the PCRF the actions resulting of service detection may be performed by the PCEF as part of the charging and policy enforcement per service data flow and by the BBERF for bearer binding as defined in TS 23.203 [3] or may be performed by the TDF as described above. + +The PCEF may encompass the TDF functionality. + +#### 4.4.3.2 Solicited service detection reporting + +To trigger the interaction with the PCRF, the start and the end of a detected service have to be added as new event triggers. The TDF notifies the PCRF when it detects the start or the end of a detected service, if detection event trigger is provisioned. After detecting a service, the TDF shall also apply the enforcement actions to the detected service, if they were provided by the corresponding PCC/SDPR rule. The TDF may also inform the PCRF via a Gx/Gxd interface, by providing an Identifier corresponding to the detected service (i.e. SD rule identifier), the service start event notification and the detected filter information, when available. The PCRF may then create/modify the PCC/SDPR rule in the desired way with regard to the policy and charging control information. + +NOTE 1: Charging control applies to PCC rules only. + +When the TDF detects the end of the service, it shall notify the PCRF, if subscribed, with the corresponding SD rule identifier and the service stop event trigger. This may trigger the PCRF to modify the PCC rule in the desired way with regard to the policy and charging control information.. + +The following enforcement actions may be applied by standalone TDF to the detected traffic: + +- a. Permit Unrestricted - the detected service/flow is allowed to continue without further policy action +- b. Block - the detected service / application flows are blocked (or the "gate is closed") +- c. Shape - apply some regime of traffic shaping to the detected service / application flows (e.g. to bandwidth limit for P2P file sharing flows) +- d. Redirection - Redirect detected flows to another controlled address (e.g. redirect to a top-up / service provisioning page). This may not be possible for all types of detected flows (e.g. this may only be performed on specific HTTP based flows) + +NOTE 2: Additional PCC functions (i.e. credit management, reporting, policy control, event reporting, binding mechanisms) besides those listed above are always performed by the PCEF as currently described in TS 23.203 [3]. + +In case the standalone TDF is involved in the communication and required to apply enforcement actions, it is PCRF's responsibility to coordinate the PCC rules and QoS rules, if applicable, with SDPR rules in order to ensure consistent service delivery. + +NOTE 3: The following alignments may be done by PCRF in case the standalone TDF is involved in the communication: + +1. Gate/redirection enforcement. There shall be no contradiction between PCC rules gate/redirection status and SDPR rules gate/redirection status. Note: This mean that, for example, when a P2P traffic has to be gated (blocked) at the TDF, the P2P traffic shall not get redirected at the PCEF, and traffic shall not get gated (blocked) at the PCEF but rather let through. +2. The uplink and downlink maximum bit rates for corresponding detected services shall not exceed the Authorized APN-AMBR, for the IP-CAN Session. + +The mechanisms covering the issue of charging interface, when standalone TDF is used, are out of this key issue's scope. + +##### 4.4.3.2.1 Specific functions description + +In order to establish the session between PCRF and standalone TDF, the PCEF may send the IP address of the related standalone TDF to the PCRF in the request message upon the IP-CAN session establishment. + +The PCRF may then establish user related session towards the TDF including the SDPR rules and event triggers, if required. + +For roaming with home routed traffic, PCEF and TDF reside in the HPLMN, while only BBERF, if applicable, reside in the VPLMN. The S9 interface enables the H-PCRF to provide dynamic QoS control policies from the HPLMN, via a V-PCRF, to a BBERF in the VPLMN. The functionality is not affected by the introduction of Service Awareness and Privacy Policies, as all of the involved entities (H-PCRF, PCEF, TDF) reside in the same network (i.e. HPLMN) and S9 is not required to transfer any new parameters. + +For Local Breakout (i.e. roaming with a visited access), V-PCRF, PCEF, TDF and BBERF, if applicable, reside in the VPLMN, while H-PCRF and SPR reside in the HPLMN. One of already defined S9 reference point functionalities in this case is to enable the H-PCRF (via the V-PCRF) to have dynamic PCC control, including both the PCEF and, if applicable, BBERF, in the VPLMN. In order to provide Service Awareness and Privacy Policies functionality, S9 is required additionally: + +- To carry Application Identifier and service detection start/stop detected traffic event triggers report from V-PCRF to H-PCRF, informing on start and stop of service traffic detection. + +NOTE: For local breakout, there may be situations where the TDF is not able to detect the traffic requested by the H-PCRF. Prior agreements could be arranged to ensure that there is a common understanding of the meaning of Application Identifiers transferred between PLMNs. + +- In addition to the existing functionality, the V-PCRF provides functions to extract SDPR rules from PCC rules provided by the H-PCRF over the S9 reference point. The V-PCRF provides updated PCC rules to the PCEF and SDPR rules to the standalone TDF, if appropriate. + +##### 1.4.3.2.2 Signalling Flows + +This clause contains signalling flows for: + +- TDF session establishment and Activation of Service Detection and Policy Rules by the PCRF into the TDF based on user privacy rules at IP-CAN Session Establishment. +- 'Start of Service' detection notification at service start from the TDF to the PCRF. +- 'Stop of Service' detection notification at service stop from the TDF to the PCRF. +- Activation/deactivation/modification of PCC/SDPR Rules by the PCRF into the TDF. + +NOTE: The external trigger does not have to be necessarily limited to SPR. + +- TDF session termination and deactivation of Service Detection and Policy Rules by the PCRF into the TDF at IP-CAN Session termination. + +###### 4.4.3.2.2.1 Changes to IP-CAN session establishment + +This clause includes the changes to IP-CAN session establishment signalling flow to provision of Service Detection and Policy Rules to the TDF, both for TDF collocated with the PCEF and for the standalone TDF. + +![Sequence diagram titled 'Provisioning of Service Detection Rules to the TDF at IP-CAN session establishment'. The diagram shows interactions between GW (BBERF), GW (PCEF), TDF, V-PCRF, H-PCRF, SPR, and OCS. A 'Roaming Scenarios' box groups the PCEF, TDF, V-PCRF, and H-PCRF. The process is divided into '1. Initial steps of IP-CAN session establishment' and '7. Concluding steps of IP-CAN session establishment'. Steps include: 2. Indication of IPCAN Session Establishment (PCEF to H-PCRF), 3. Profile Request (H-PCRF to SPR), 4. Profile Response (SPR to H-PCRF), 5. Policy Decision (H-PCRF to PCEF), 6. Acknowledge IP CAN Session Establishment (PCEF to TDF), 8. TDF Session Establishment request (H-PCRF to TDF), and 9. TDF Session Establishment ACK (TDF to H-PCRF).](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +sequenceDiagram + participant GW_BBERF as GW (BBERF) + subgraph Roaming Scenarios + participant GW_PCEF as GW (PCEF) + participant TDF + participant V_PCRF as V-PCRF + participant H_PCRF as H-PCRF + end + participant SPR + participant OCS + + Note over GW_BBERF, GW_PCEF: 1. Initial steps of IP-CAN session establishment + Note over SPR, OCS: 7. Concluding steps of IP-CAN session establishment + + GW_PCEF->>H_PCRF: 2. Indication of IPCAN Session Establishment + H_PCRF-->>SPR: 3. Profile Request + SPR-->>H_PCRF: 4. Profile Response + H_PCRF->>GW_PCEF: 5. Policy Decision + GW_PCEF->>TDF: 6. Acknowledge IP CAN Session Establishment + H_PCRF-->>TDF: 8. TDF Session Establishment request + TDF-->>H_PCRF: 9. TDF Session Establishment ACK + +``` + +Sequence diagram titled 'Provisioning of Service Detection Rules to the TDF at IP-CAN session establishment'. The diagram shows interactions between GW (BBERF), GW (PCEF), TDF, V-PCRF, H-PCRF, SPR, and OCS. A 'Roaming Scenarios' box groups the PCEF, TDF, V-PCRF, and H-PCRF. The process is divided into '1. Initial steps of IP-CAN session establishment' and '7. Concluding steps of IP-CAN session establishment'. Steps include: 2. Indication of IPCAN Session Establishment (PCEF to H-PCRF), 3. Profile Request (H-PCRF to SPR), 4. Profile Response (SPR to H-PCRF), 5. Policy Decision (H-PCRF to PCEF), 6. Acknowledge IP CAN Session Establishment (PCEF to TDF), 8. TDF Session Establishment request (H-PCRF to TDF), and 9. TDF Session Establishment ACK (TDF to H-PCRF). + +**Figure 4.4.3.2.2.1-1: Provisioning of Service Detection Rules to the TDF at IP-CAN session establishment** + +1. IP-CAN Session Establishment as specified in TS 23.203 [3] clause 7.2 steps 1 to 2. +2. The PCEF determines that the PCC authorization is required, requests the authorization of allowed service(s) and PCC Rules information as specified in TS 23.203 [3] step 3. The PCEF also includes information on whether the TDF is collocated with the PCEF or it is not and standalone TDF IP address, if applicable. The existing Supported Features mechanism (TS 29.212) may be applied by PCEF and TDF to indicate the detection feature support. +3. IP-CAN Session Establishment as specified in TS 23.203 [3] clause 7.2 step 4. +4. IP-CAN Session Establishment as specified in TS 23.203 [3] clause 7.2 step 5, including user privacy policies. +5. IP-CAN Session Establishment as specified in TS 23.203 [3] clause 7.2 step 6. +6. The PCRF sends a decision as specified in TS 23.203 [3] step 7. If the TDF is collocated with the PCEF, PCRF checks user privacy policies to traffic detection mechanisms. If user's privacy policies as indicated by the profile, allow for the use of service traffic detection, the PCRF also sends the PCC rules for the service detection and enforcement to the PCEF and may include subscription to the service detection start/stop event trigger. The PCEF provisions the detection requirements to the TDF. +7. IP-CAN Session Establishment as specified in TS 23.203 [3] clause 7.2 steps 8 to 12. +8. If the TDF is standalone, steps 8 and-9 take place. If user's privacy policies as indicated by the profile, allow for the use of service traffic detection, the PCRF requests the identified TDF to establish the relevant session + +towards PCRF and provides Service Detection and Policy Rules to the TDF and may subscribe to the service detection start and service detection stop event triggers. + +- 9. The TDF acknowledges the request and may indicate policy enforcement actions support in case some of the enforcement actions required by PCRF are not supported. + +NOTE: Steps 8-9 can occur immediately after step 2. + +###### 4.4.3.2.2.2 Service Detection notification + +This clause describes the provisioning of service information from the TDF at the start of a service detected by the TDF for both standalone TDF and collocated TDF. + +![Sequence diagram showing the provisioning of service information from the TDF. Lifelines: GW (BBERF), GW (PCEF), TDF, V-PCRF, H-PCRF. The diagram shows five steps: 1. Detection of service start (TDF), 2. Provision service information (TDF to H-PCRF via V-PCRF), 3. Policy Decision (H-PCRF), 4. Provision service information ACK (H-PCRF to TDF via V-PCRF), 5. Concluding steps of PCRF-Initiated IP-CAN session modification (involving GW (BBERF), GW (PCEF), and TDF).](f2ea0f64a770b22b902820457d262265_img.jpg) + +``` + +sequenceDiagram + participant GW_BBERF as GW (BBERF) + subgraph Collocated_Region [ ] + participant GW_PCEF as GW (PCEF) + participant TDF as TDF + end + participant V_PCRF as V-PCRF + participant H_PCRF as H-PCRF + + Note right of TDF: 1. Detection of service start + TDF->>H_PCRF: 2. Provision service information + Note right of H_PCRF: 3. Policy Decision + H_PCRF->>TDF: 4. Provision service information ACK + Note left of GW_BBERF: 5. Concluding steps of PCRF-Initiated IP-CAN session modification + +``` + +Sequence diagram showing the provisioning of service information from the TDF. Lifelines: GW (BBERF), GW (PCEF), TDF, V-PCRF, H-PCRF. The diagram shows five steps: 1. Detection of service start (TDF), 2. Provision service information (TDF to H-PCRF via V-PCRF), 3. Policy Decision (H-PCRF), 4. Provision service information ACK (H-PCRF to TDF via V-PCRF), 5. Concluding steps of PCRF-Initiated IP-CAN session modification (involving GW (BBERF), GW (PCEF), and TDF). + +Figure4.4.3.2.2.2-1: Provisioning of service information from the TDF + +- 1. The standalone or collocated TDF detects the start of a service flow that matches with one of the activated PCC/SDPR Rules. Then, in case the enforcement actions were provided as a part of SDPR rules, TDF shall apply those actions. + +NOTE 1: the detection procedure is out of the scope of this study. + +- 2. If the service start event trigger request was received, the TDF shall provide service information to the PCRF, including the SD Rule Identifier, service detection start event trigger and the flow descriptions, if available. + +NOTE 2: In case of collocated TDF, the information is provided by TDF through PCEF-PCRF communication. The interface between TDF and PCEF is out of scope. + +- 3. Upon receiving the notification, PCRF may modify the PCC/SDPR rule (and the QoS Rules if they are applicable), based on the received flow descriptions and operator local policies for the detected service, otherwise step 5 is not applicable. +- 4. If step 2) was initiated by the standalone TDF, then the PCRF sends acknowledge to the TDF. +- 5. The PCRF-Initiated session modification take place as per TS 23.203 [3] clause 7.4.2 steps 4-11. + +###### 4.4.3.2.2.3 Notification for stop of service from the TDF + +This clause describes the reporting of the stop of a service detected by the TDF both for standalone TDF and for collocated TDF. + +![Sequence diagram for Notification for stop of service from the TDF](7d2d1d3870cd224c4430d19334557716_img.jpg) + +The diagram is a sequence diagram illustrating the interaction between five network elements: GW (BBERF), GW (PCEF), TDF, V-PCRF, and H-PCRF. The GW (PCEF) and TDF are grouped together in a dashed box. The V-PCRF and H-PCRF are grouped together in a shaded vertical bar. The sequence of messages is as follows: + +- 1. Detection of service stop**: An internal action within the TDF. +- 2. Notification stop of service**: A message sent from the TDF to the H-PCRF, passing through the V-PCRF. +- 3. Policy Decision**: An internal action performed by the H-PCRF. +- 4. ACK for notification**: An acknowledgement message sent from the H-PCRF back to the TDF, passing through the V-PCRF. +- 5. Concluding steps of PCRF-Initiated IP-CAN session modification**: A dashed box spanning across all entities indicating subsequent procedures. + +Sequence diagram for Notification for stop of service from the TDF + +**Figure 4.4.3.2.2.3-1: Notification for stop of service from the TDF** + +1. The standalone or collocated TDF detects the stop of a service flow that matches with one of the activated PCC/SDPR Rules. +2. If the service stop event trigger was subscribed to, the TDF shall send stop of service event trigger to the PCRF. The notification shall include the SDPR Rule Identifier and service detection stop event trigger. It may also include filters associated with the reported service. + +NOTE: In case of collocated TDF, the information is provided by TDF through PCEF-PCRF communication. The interface between TDF and PCEF is out of scope. + +3. Upon receiving the notification, the PCRF may modify the PCC/SDPR rule (and the QoS Rules if they are applicable), as a result of service detection stop. Then, the step 5 is applicable. +4. If step 2) was initiated by a standalone TDF, then the PCRF sends acknowledge to the TDF. +5. The PCRF-Initiated session modification take place as per TS 23.203 [3] clause 7.4.2 steps 4-11. + +###### 4.4.3.2.2.4 + +###### Activation/deactivation of PCC/SDPR Rules in the TDF + +![Sequence diagram showing the activation/deactivation of PCC/SDPR Rules in the TDF. The diagram involves five lifelines: GW (PCEF), TDF, V-PCRF, H-PCRF, and SPR. The sequence starts with SPR sending a 'Notification of user profile change' to H-PCRF. H-PCRF responds with 'User profile change ACK'. H-PCRF then makes a 'Rules decision'. V-PCRF sends a 'TDF session modification' to TDF, which responds with 'TDF session modification ACK'. Finally, a dashed box labeled '6. Concluding steps of PCRF-Initiated IP-CAN session modification' is shown, indicating the next steps in the process.](3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg) + +``` + +sequenceDiagram + participant SPR + participant H-PCRF + participant V-PCRF + participant TDF + participant GW as GW (PCEF) + + Note left of GW: (GW and TDF are in a dashed box) + + SPR->>H-PCRF: 1. Notification of user profile change + H-PCRF-->>SPR: 2. User profile change ACK + Note right of H-PCRF: 3. Rules decision + V-PCRF-->>TDF: 4. TDF session modification + TDF-->>V-PCRF: 5. TDF session modification ACK + Note left of GW: 6. Concluding steps of PCRF-Initiated IP-CAN session modification + +``` + +Sequence diagram showing the activation/deactivation of PCC/SDPR Rules in the TDF. The diagram involves five lifelines: GW (PCEF), TDF, V-PCRF, H-PCRF, and SPR. The sequence starts with SPR sending a 'Notification of user profile change' to H-PCRF. H-PCRF responds with 'User profile change ACK'. H-PCRF then makes a 'Rules decision'. V-PCRF sends a 'TDF session modification' to TDF, which responds with 'TDF session modification ACK'. Finally, a dashed box labeled '6. Concluding steps of PCRF-Initiated IP-CAN session modification' is shown, indicating the next steps in the process. + +**Figure 4.4.3.2.2.4-1: Provisioning/Removal of Service Detection and Policy Rules in the TDF** + +1. The PCRF is notified that the user profile has changed (e.g. by receiving the appropriate request from SPR). +2. The PCRF acknowledges the user profile change to SPR. +3. PCRF decides on PCC/SDPR rules change. + +NOTE: A change of SDPR rules may also happen as a result of internal PCRF logic execution; in such a case steps 1-2 are not required. + +**If the TDF is standalone:** + +4. PCRF activates/deactivates/modifies the SDPR rules in the TDF. +5. TDF acknowledges the SDPR rules' activation/deactivation/modification. + +**If the TDF is collocated with the PCEF, then steps 4 and 5 are omitted and:** + +6. PCRF provisions PCC Rules to the TDF by applying PCRF-Initiated IP-CAN session modification procedure per TS 23.203 [3] clause 7.4.2 step 5 to 11. + +###### 4.4.3.2.2.5 Changes to IP-CAN session termination + +This clause includes the changes to IP-CAN session termination to deactivate SDPR Rules at the TDF. + +![Sequence diagram showing the removal of Service Detection Rules from the TDF at IP-CAN session termination. The diagram involves eight lifelines: GW(BBERF), GW(PCEF), TDF, V-PCRF, (H-)PCRF, AF, OCS, and SPR. The process is divided into three main phases: 1. Initial steps of IP-CAN Session termination (steps 1-4), 2. Indication of IP-CAN Session Termination (steps 5-9), and 3. Concluding steps of IP-CAN session termination (steps 10-12). Key actions include the GW(PCEF) indicating session termination to the V-PCRF, the V-PCRF identifying affected policy and charging rules, notifying the AF, and finally the TDF performing session termination and receiving an ACK.](933ecd14c858bf3fc919222d8e357bc8_img.jpg) + +``` + +sequenceDiagram + participant GW(BBERF) + participant GW(PCEF) + participant TDF + participant V-PCRF + participant (H-)PCRF + participant AF + participant OCS + participant SPR + + Note right of GW(PCEF): 1. Initial steps of IP-CAN Session termination + Note right of V-PCRF: 2. Indication of IP-CAN Session Termination + Note right of (H-)PCRF: 3. Identify what Policy and Charging Rules are affected. + Note right of GW(PCEF): 6. Remove all Policy and Charging Rules + Note right of (H-)PCRF: 4. Notify loss of transmission + Note right of (H-)PCRF: 5. Notification response + Note right of V-PCRF: 7. Acknowledge IP-CAN Session Termination + Note right of TDF: 8. Indication of IP-CAN session termination to TDF + Note right of TDF: 9. Acknowledge of IP-CAN session termination + Note right of GW(PCEF): 10. Concluding steps of IP-CAN session termination + Note right of TDF: 11. TDF Session Termination + Note right of TDF: 12. TDF Session Termination ACK + + Note left of GW(PCEF): 1. Initial steps of IP-CAN Session termination + Note left of V-PCRF: 2. Indication of IP-CAN Session Termination + Note left of (H-)PCRF: 3. Identify what Policy and Charging Rules are affected. + Note left of GW(PCEF): 6. Remove all Policy and Charging Rules + Note left of (H-)PCRF: 4. Notify loss of transmission + Note left of (H-)PCRF: 5. Notification response + Note left of V-PCRF: 7. Acknowledge IP-CAN Session Termination + Note left of TDF: 8. Indication of IP-CAN session termination to TDF + Note left of TDF: 9. Acknowledge of IP-CAN session termination + Note left of GW(PCEF): 10. Concluding steps of IP-CAN session termination + Note left of TDF: 11. TDF Session Termination + Note left of TDF: 12. TDF Session Termination ACK + +``` + +Sequence diagram showing the removal of Service Detection Rules from the TDF at IP-CAN session termination. The diagram involves eight lifelines: GW(BBERF), GW(PCEF), TDF, V-PCRF, (H-)PCRF, AF, OCS, and SPR. The process is divided into three main phases: 1. Initial steps of IP-CAN Session termination (steps 1-4), 2. Indication of IP-CAN Session Termination (steps 5-9), and 3. Concluding steps of IP-CAN session termination (steps 10-12). Key actions include the GW(PCEF) indicating session termination to the V-PCRF, the V-PCRF identifying affected policy and charging rules, notifying the AF, and finally the TDF performing session termination and receiving an ACK. + +**Figure 4.4.3.2.2.5-1: Removal of Service Detection Rules from the TDF at IP-CAN session termination** + +1. IP-CAN Session Termination initial steps as specified in TS 23.203 [3] clause 7.3.1, steps 1- 2 or clause 7.3.2, steps 1-4. +2. The GW (PCEF) indicates that the IP-CAN Session is being removed and provides relevant information to the PCRF. +3. The PCRF finds the PCC Rules that require an AF to be notified and removes PCC Rules for the IP-CAN session. +4. The PCRF notifies the AF that there are no transmission resources for the service if this is requested by the AF. +5. The AF acknowledges the notification of the loss of transmission resources. +6. The GW (PCEF) removes all PCC Rules associated with the IP-CAN session. +7. The PCRF removes the information related to the terminated IP-CAN Session (subscription information etc.), and acknowledges the IP-CAN Session termination. +8. If the TDF is standalone, then steps 8-9 take place. The PCRF informs TDF about IP-CAN session termination. + +9. TDF deactivates all SDPR Rules associated with the IP-CAN session and acknowledges the termination request from the PCRF. +10. IP-CAN Session Termination concluding steps takes place as specified in TS 23.203 [3] clause 7.3.1, steps 9-14 or clause 7.3.2, steps 11-15. +11. TDF terminates the session with the PCRF. +12. PCRF acknowledges the TDF session termination. + +#### 4.4.3.3 Unsolicited service detection reporting + +##### 4.4.3.3.1 Signalling Flows + +This clause contains signalling flows for those cases where the TDF role is service detection and reporting to the PCRF. + +- Provisioning of service information at service start/modification from the TDF. +- Revoke service session information at service stop from the TDF. + +###### 4.4.3.3.1.1 Provision service information from the TDF + +This clause describes the provisioning of service information from the TDF at the start or modification of a service detected by the TDF. The TDF performs service detection and reporting functions only. + +![Sequence diagram illustrating the provisioning of service information from the TDF. The diagram shows five lifelines: GW (BBERF), GW (PCEF), TDF, V-PCRF, and H-PCRF. The sequence of messages is: 1. Detection of service start/modification (TDF internal), 2. Provision service information (TDF to H-PCRF), 3. Policy Decision (H-PCRF internal), 4. Provision service information ACK (H-PCRF to TDF), and 5. Concluding steps of PCRF-Initiated IP-CAN session modification (dashed box covering all lifelines).](94acd33fcad85bb6f207a308f9b63191_img.jpg) + +``` + +sequenceDiagram + participant GW_BBERF as GW (BBERF) + participant GW_PCEF as GW (PCEF) + participant TDF + participant V_PCRF as V-PCRF + participant H_PCRF as H-PCRF + + Note right of TDF: 1. Detection of service start/modification + TDF->>H_PCRF: 2. Provision service information + Note right of H_PCRF: 3. Policy Decision + H_PCRF->>TDF: 4. Provision service information ACK + Note left of GW_BBERF: 5. Concluding steps of PCRF-Initiated IP-CAN session modification + +``` + +Sequence diagram illustrating the provisioning of service information from the TDF. The diagram shows five lifelines: GW (BBERF), GW (PCEF), TDF, V-PCRF, and H-PCRF. The sequence of messages is: 1. Detection of service start/modification (TDF internal), 2. Provision service information (TDF to H-PCRF), 3. Policy Decision (H-PCRF internal), 4. Provision service information ACK (H-PCRF to TDF), and 5. Concluding steps of PCRF-Initiated IP-CAN session modification (dashed box covering all lifelines). + +**Figure 4.4.3.3.1.1-1: Provisioning of service information from the TDF** + +1. The TDF detects the start or the modification of a service flow that matches with one of the SD Rules installed in the TDF, enforces the service control for the detected service.. + +NOTE 1: The detection procedure is out of the scope of this study. + +2. The TDF provide service information to the PCRF, the TDF includes the application identifier and if available the flow descriptions. + +3. If operator policies indicates that PCC/QoS Rules shall be provisioned then the PCRF generates PCC Rules (and the QoS Rules if they are applicable) based on the received flow descriptions and operator local policies for the detected service, otherwise step 5 is not applicable. +4. The PCRF sends a confirmation to the TDF. +5. The PCRF- Initiated IP-CAN session modification takes place as per TS 23.203 [3] clause 7.4.2 steps 4-11. + +NOTE 2: Step 4 may take place at anytime after step 3. + +###### 4.4.3.3.1.2 Revoking service information from the TDF + +This clause describes the reporting of the stop of a service detected by the TDF. The TDF performs service detection functions only. + +![Sequence diagram illustrating the process of revoking service information from the TDF. The diagram shows five lifelines: GW (BBERF), GW (PCEF), TDF, V-PCRF, and H-PCRF. The process starts with the TDF detecting a service stop (Step 1). The TDF then sends a 'Revoke service information' message to the H-PCRF (Step 2). The H-PCRF makes a 'Policy Decision' (Step 3) and sends a 'Revoke service information ACK' back to the TDF (Step 4). Finally, the TDF initiates the concluding steps of the PCRF-Initiated IP-CAN session modification (Step 5), which involves the V-PCRF and the GW (PCEF).](8658cfab6a458b4a80ab2e384c61ff89_img.jpg) + +``` + +sequenceDiagram + participant GW_BBERF as GW (BBERF) + participant GW_PCEF as GW (PCEF) + participant TDF as TDF + participant V_PCRF as V-PCRF + participant H_PCRF as H-PCRF + + Note right of TDF: 1. Detection of service stop + TDF->>H_PCRF: 2. Revoke service information + Note right of H_PCRF: 3. Policy Decision + H_PCRF->>TDF: 4. Revoke service information ACK + Note right of TDF: 5. Concluding steps of PCRF-Initiated IP-CAN session modification + +``` + +Sequence diagram illustrating the process of revoking service information from the TDF. The diagram shows five lifelines: GW (BBERF), GW (PCEF), TDF, V-PCRF, and H-PCRF. The process starts with the TDF detecting a service stop (Step 1). The TDF then sends a 'Revoke service information' message to the H-PCRF (Step 2). The H-PCRF makes a 'Policy Decision' (Step 3) and sends a 'Revoke service information ACK' back to the TDF (Step 4). Finally, the TDF initiates the concluding steps of the PCRF-Initiated IP-CAN session modification (Step 5), which involves the V-PCRF and the GW (PCEF). + +**Figure 4.4.3.3.1.2-1: Revoke service information to the PCRF** + +1. The TDF detects the stop of a service flow that matches with one of the SD Rules installed in the TDF. + +NOTE: The detection procedure is out of the scope of this study. + +2. The TDF revokes service information to the PCRF. + 3. If PCC Rules are installed in the PCEF steps 5 applies. + 4. The PCRF sends a confirmation to the TDF. + 5. The PCRF- Initiated IP-CAN session modification takes place as per TS 23.203 [3] clause 7.4.2 steps 4-11 +- NOTE 2: Step 4 may take place at anytime after step 3. + +#### 4.4.3.4 Service Detection and Policy rules definition and structure + +This clause is relevant only in the case of standalone TDF. + +##### 4.4.3.4.1 General + +The Service Detection and Policy rule (SDPR rule) comprises the information that is required in order to apply the detection and enforcement actions for the specified service traffic. + +Two different types of SDPR rules exist: dynamic rules and predefined rules. The dynamic SDPR rules are provisioned by the PCRF via the Gxd reference point, while the predefined SDPR rules are directly provisioned into the TDF and only referenced by the PCRF. The pre-defined SDPR rules may be used in a non-roaming situation. + +NOTE 1: The procedure for provisioning predefined SDPR rules is out of scope. + +There are defined procedures for activation, modification and deactivation of SDPR rules (as described in clause 4.4.2.3.2.2). The PCRF may activate, modify and deactivate a SDPR rule at any time, over the Gxd reference point. The modification procedure is applicable to dynamic SDPR rules only. + +Upon detecting end of service traffic for the corresponding SDPR rule, the TDF shall notify the PCRF, if originally controlled by the PCRF, of the end of service traffic. + +The operator defines the SDPR rules. + +The following table lists the information contained in a SDPR rule, including the information element name, the description and whether the PCRF may modify this information in a dynamic SDPR rule which is active in the TDF. The Category field indicates if a certain piece of information is mandatory or not for the construction of a SDPR rule, i.e. if it is possible to construct a SDPR rule without it. + +**Table 4.4.3.4.1-1** + +| Information name | Description | Category | PCRF permitted to modify for a dynamic SDPR rule in the TDF | +|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-------------------------------------------------------------| +| SDPR Rule identifier | Uniquely identifies the SDPR rule, within an IP-CAN session.
It is used between PCRF and standalone TDF for referencing SDPR rules. | Mandatory | No | +| Application identifier | References the corresponding application (i.e. service), for which the rule applies. | Mandatory | No | +| Enforcement control | Defines how the standalone TDF shall apply enforcement actions for the detected service traffic. | | | +| Gate status | The gate status indicates whether the service data flow, detected by the service data flow template, may pass (Gate is open) or shall be discarded (Gate is closed) at the TDF. | | Yes | +| UL-maximum bitrate | The uplink maximum bitrate authorized for the service traffic | | Yes | +| DL-maximum bitrate | The downlink maximum bitrate authorized for the service traffic | | Yes | +| Redirect | Redirect detected service traffic to another controlled address | | Yes | + +The *SDPR Rule identifier* shall be unique for a SDPR rule within an IP-CAN session. A dynamically provided SDPR rule that has the same Rule identifier value as a predefined SDPR rule shall replace the predefined rule within the same IP-CAN session. + +The *Application identifier* references the corresponding application (i.e. service), for which the rule applies. + +The *Gate status* indicates whether the TDF shall let a service traffic matching the Application identifier, pass through (gate is open) the TDF or the TDF shall discard (gate is closed) the service traffic. + +The *UL maximum-bitrate* indicates the authorized maximum bitrate for the uplink component of the detected service traffic. + +The *DL maximum-bitrate* indicates the authorized maximum bitrate for the downlink component of the detected service traffic. + +The *Redirect* indicates whether the detected service traffic should be redirected to another controlled address. The target redirect address is included also. + +##### 4.4.3.4.2 Service Detection and Policy rule relevant operations + +Service Detection and Policy rule operations consist of activation, modification and de-activation of SDPR rules. + +Activation of a dynamic SDPR rule: The PCRF provides the SDPR rule information to the TDF via the Gxd reference point. + +Activation of a predefined SDPR rule: The PCRF provides an identifier of the relevant SDPR rule to the TDF via the Gxd reference point. + +An active SDPR rule means that the service traffic, matching the corresponding application (i.e. service), is detected and enforced as per enforcement control actions, if defined within the SDPR rule. + +The PCRF may, at any time, modify an active, dynamic SDPR rule. + +The PCRF may, at any time, deactivate an active SDPR rule in the TDF via the Gxd reference point. At IP-CAN session termination all active SDPR rules are deactivated upon information, received from the PCRF about IP-CAN session termination. + +Upon detecting end of service traffic for the application (i.e. service), TDF shall deactivate the corresponding SDPR rule. + +##### 4.4.3.4.3 PCC rules modifications + +The following additional fields should be added to PCC rules' structure in order to support service awareness functionality: + +- The *Application identifier* references the corresponding application (i.e. service), for which the rule applies. +- The *Redirect* indicates whether the detected service traffic should be redirected to another controlled address. The target redirect address is included also. + +Additionally, Event triggers of start and stop of detected traffic should be added. + +### 4.4.4 Conclusion + +The general AF, as part of the PCC architecture defined in TS 23.203 [3], shall not be enhanced to support enforcement functionality assigned to the PCEF, according to TS 23.203 [3], for the purpose of service detection / this key issue. As a consequence the Rx reference shall not be enhanced to carry QoS enforcement information. + +Both solicited and unsolicited service detection reporting scenarios as described in key issue 4 are valid. Whether the one or other is chosen depends on the actual network deployment. Therefore, it is proposed to cover both of them in the normative standardization. + +## 4.5 Key issue 5: Service Based Traffic Steering + +### 4.5.1 Description + +In a service aware network it is possible to optimally route the traffic. For IP services that get identified using service traffic detection mechanism it may only be possible after the session has been established and the some traffic has already traversed the network. In order to improve service experience it should be possible to steer traffic after its establishment for example from a Home PDN Gateway to a local breakout. + +Editor's Note: Further changes can be done to this key issue description based on SA WG1 feedback. + +### 4.5.2 Conclusion + +No viable solution was presented to resolve this issue during the period of the study. The issue is therefore being closed. + +## 4.6 Key issue 6: Extending Policy Architecture to handle transactional services + +### 4.6.1 Description + +Current 3GPP PCC architecture usage is designed around the handling of IP flows. Many current / legacy (e.g. SMS) and future services (e.g. video rental) are however of transactional nature. In many scenarios it can be beneficial if there is a standardized mechanism for handling policies for such services via the PCC. For transactional services while the PCRF will authorize requests for such services, the service logic and enforcement of PCRF authorized decisions will continue to reside within the service. + +Editor's note: The extent of such interaction and enforcement are subject to 3GPP scope and FFS. + +### 4.6.2 Alternative solutions + +#### 4.6.2.1 Alternative 1 - Use Rx to authorize transactional services + +##### 4.6.2.1.1 General + +The AF acting as Charging Trigger Function, as described in TS 32.229 [x], performs a check balance request for the transactional service using the Ro Interface. If successful the AF can then proceed to authorize the user to receive the service using Rx. + +Video download is an example of a transactional service that is addressed in this alternative solution. + +The PCRF can be used to authorize the user to receive a service based on network and user preferences (e.g. user has or does not have the priority/subscription to receive the service in the current location) that are available at the PCRF. + +The PCRF plays the role of an authorization server that takes into account at least the user profile (stored in the SPR/UDR), the network information (received from the PCEF/BBERF). + +A successful authorization will trigger installation of PCC/QoS Rules as normal PCC procedures defined in TS 23.203 [3] + +##### 4.6.2.1.2 Architecture + +A possible architecture for transactional services is shown in Figure 4.6.2.1.2-1 in the non roaming case. In the roaming case a S9 reference point is present between the H-PCRF and the V-PCRF. + +![Figure 4.6.2.1.2-1: Architecture for transactional services. The diagram shows a UE connected to an ASP, which is connected to an AF. The AF is connected to a PCRF via the Rx interface. The PCRF is connected to a BBERF via the Gxx interface and to a PCEF via the Gx interface. The PCRF is also connected to an OCS via the Ro interface and to an SPR via the Sp interface. The ASP, AF, and PCRF are enclosed in a dashed box.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +``` + +graph TD + UE[UE] --- ASP[ASP] + subgraph DashedBox [ ] + ASP --- AF[AF] + AF --- Rx((Rx)) + Rx --- PCRF[PCRF] + end + AF --- Ro((Ro)) + Ro --- OCS[OCS] + PCRF --- Sp((Sp)) + Sp --- SPR[SPR] + PCRF --- Gxx((Gxx)) + Gxx --- BBERF[BBERF] + PCRF --- Gx((Gx)) + Gx --- PCEF[PCEF] + style DashedBox fill:none,stroke-dasharray: 5 5 + +``` + +Figure 4.6.2.1.2-1: Architecture for transactional services. The diagram shows a UE connected to an ASP, which is connected to an AF. The AF is connected to a PCRF via the Rx interface. The PCRF is connected to a BBERF via the Gxx interface and to a PCEF via the Gx interface. The PCRF is also connected to an OCS via the Ro interface and to an SPR via the Sp interface. The ASP, AF, and PCRF are enclosed in a dashed box. + +**Figure 4.6.2.1.2-1: Architecture for transactional services** + +The ASP receives application level signalling from a UE that request a transactional service, in this example, to download a video. + +The AF receives user authorization requests from the ASP, an AF may receive user authorization request from multiple ASPs. + +NOTE: The AF is assumed to be part of the operator's domain. + +The AF communicates with the OCS over Ro using existing procedures to check the balance for the requested service. + +If credit balance check is successful the AF requests PCRF authorization over Rx using existing procedures and subscribes to notifications of successful and unsuccessful resource reservation. + +The PCRF authorizes the user to receive the service based on network and user preferences that are stored in the SPR/UDR, + +If the service is authorized a successful response is returned over Rx interface to the ASP via the AF and PCC/QoS Rules are installed in the PCEF/BBERF. If the service is not authorized an unsuccessful response is returned over Rx interface to the ASP via the AF. + +If there is enough credit, the service is authorized and the underlying resources are established, the AF responds that there are service can be successful delivery to the user. + +##### 4.6.2.1.3 Reference points + +###### 4.6.2.1.3.1 AF - PCRF reference point (Rx) + +The Rx reference point between the AF and the PCRF is described in TS 23.203 [3]. The Rx reference point enables transport of application level session information from AF to PCRF. + +###### 4.6.2.1.3.2 AF - OCS reference point (Ro) + +The Ro reference point between the AF and the OCS is described in TS 32.299 [8]. The Ro reference point enables the AF (acting as a Charging Trigger Function) to perform a check balance request for the transactional service. + +##### 4.6.2.1.4 PCC Information Flows + +This clause includes PCC information flows to authorize a user to receive a transactional service, including installation of PCC/QoS Rule for the transactional service and to remove PCC/QoS Rules when the user has received the service. + +###### 4.6.2.1.4.1 + +###### Authorization of a user to receive a transactional service + +![Sequence diagram showing the authorization of a user to receive a transactional service. The diagram involves UE, GW (BBERF), GW (PCEF), Roaming Scenarios (V-PCRF, H-PCRF), AF, OCS, and ASP. The process starts with UE connecting to ASP, followed by a request to authorize the user, balance check, and subsequent policy enforcement and bearer signaling.](4ff00a489baaa34a0c01070de1d613db_img.jpg) + +``` + +sequenceDiagram + participant UE + participant GW_BBERF as GW (BBERF) + participant GW_PCEF as GW (PCEF) + subgraph Roaming Scenarios + V-PCRF + H-PCRF + end + participant AF + participant OCS + participant ASP + + Note right of GW_PCEF: 1. UE connects to ASP + AF->>ASP: 2. Request to authorize the user + AF->>OCS: 3 Check balance + OCS-->>AF: 4. (Enough credit/no credit) + AF->>H-PCRF: 5. Application/Service Info + H-PCRF-->>AF: 6. Ack + Note left of GW_PCEF: 7. Gateway Control and QoS Rules Provision (case 2a and 2b) + H-PCRF->>GW_PCEF: 8. Policy and Charging Rules Provision + Note left of GW_BBERF: 9. Policy Enforcement + GW_PCEF->>OCS: 10. Credit Request + OCS-->>GW_PCEF: 11. Credit Response + GW_BBERF->>GW_PCEF: 12 IP CAN Bearer Signaling (case 1) + GW_PCEF->>GW_BBERF: 13. IP CAN Bearer Signaling (case 1) + GW_PCEF-->>H-PCRF: 14. Ack + H-PCRF->>AF: 15. Notification of Bearer Level Event + AF-->>H-PCRF: 16. Ack + Note right of GW_PCEF: 18 UE access the service + AF->>ASP: 17. Service authorization result + +``` + +Sequence diagram showing the authorization of a user to receive a transactional service. The diagram involves UE, GW (BBERF), GW (PCEF), Roaming Scenarios (V-PCRF, H-PCRF), AF, OCS, and ASP. The process starts with UE connecting to ASP, followed by a request to authorize the user, balance check, and subsequent policy enforcement and bearer signaling. + +Figure 4.6.2.1.4.1-1: User authorization to receive the service + +1. The UE connects to the ASP server and requests transactional services, in this example to download a video from the ASP. +2. Triggered by step 2 or alternatively by the ASP deciding to deliver the service to the user (assuming that the UE location is known), the ASP server decides to check if the user is authorized to receive the service. +3. The AF performs a check balance request using the Ro as described in RFC4006 and TS 32.299 [8] +4. The OCS sends a response on whether there is enough credit. +5. If there is enough credit the AF establishes an Rx session toward the PCRF as described in TS 23.203 [3] and provides the user identity (IMSI, MSISDN or UE IP address), the service identifier for the transactional service and the service information including the Flow Descriptions. Furthermore the AF subscribes to the notification to the AF related bearer level events (transmission resources are established/released/lost) +6. The PCRF checks if the user is allowed to receive the service, taking into account the user profile (e.g. gold/silver/bronze) in the SPR (UDR), the user context (e.g. user location). If the user is not authorized to receive the service in step 7 the PCRF sends a response to the AF that the service is not authorized steps 7 to 18 does not take place. + +7. If there is a need to provision QoS rules, the PCRF initiates a Gateway Control and QoS Rules Provision Procedure to request resources for a transactional service and may subscribe to notification of resource reservation as described in TS 23.203 [3]. +8. The PCRF sends the Policy and Charging Rules Provision (PCC Rules, Event Trigger) to the PCEF and may subscribe to notification of resources reservation (successful or unsuccessful) +9. The PCEF enforces the decision. +10. If online charging is applicable, the PCEF may request credit for new charging keys from and/or shall return the remaining credit for charging keys no longer active to the OCS. +11. If OCS was involved, the OCS provides the credit information to the PCEF, and/or acknowledges the credit report +12. Triggered by the installation of PCC Rules, the PCEF sends an IP-CAN Bearer establishment request for the GTP case. +13. The GW (PCEF) receives the response for the IP-CAN Bearer establishment request for the GTP case to confirm if the resources are available for service delivery. +14. The PCEF sends Acknowledge Policy and Charging Rules Provisioning (accept or reject of the PCC rule operation(s)) to the PCRF. +15. Triggered by the response from the PCEF the PCRF notifies the AF related bearer level events (transmission resources are established or released). +16. The AF acknowledges the notification from the PCRF. +17. As there is enough credit, the service is authorized and the underlying resources are established, the AF responds that there are service can be successful delivery to the user. +18. The UE receives the desired service from the ASP. + +###### 4.1.2.1.2.4 Termination of the authorization of the user to receive the service + +When the user has received the service the ASP will request the AF to terminate the Rx session, as specified in TS 23.203 [3]. + +### 4.6.3 Comparison of alternatives + +### 4.6.4 Conclusion + +Alternative 1 enables the PCRF to perform user authorization to access the service for a transactional service. + +The Ro interface is used to perform a check balance request for the transactional service as per RFC 4006 and TS 32.299 [x]. + +The Rx interface is used to request the PCRF to perform user authorization for a transactional service according to user profile and user context. + +Based on this evaluation no impacts on normative work are expected. + +# Annex A: Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|----|-----|------------------------------------------------------------------------------|-------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2011-06 | SP-52 | SP-100355 | - | - | MCC editorial update for presentation to TSG SA for approval | 0.6.0 | 1.0.0 | +| 2011-06 | SP-52 | - | - | - | MCC update to version 11.0.0 after TSG SA approval | 1.0.0 | 11.0.0 | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23849/1c953f32bd34345dfd68fddf8a3736d6_img.jpg b/marked/Rel-11/23_series/23849/1c953f32bd34345dfd68fddf8a3736d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b427cf8b80cddafeb7f1e19cc92fb593472d299 --- /dev/null +++ b/marked/Rel-11/23_series/23849/1c953f32bd34345dfd68fddf8a3736d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20c6288a3e894bfc92aa2b7fa48c563564329edb652f7c641fab99bf5580ad76 +size 54419 diff --git a/marked/Rel-11/23_series/23849/2834bdd6eb8540277e609decbb924003_img.jpg b/marked/Rel-11/23_series/23849/2834bdd6eb8540277e609decbb924003_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b642e160cf9d8a1d0c061c6779907f1822af5659 --- /dev/null +++ b/marked/Rel-11/23_series/23849/2834bdd6eb8540277e609decbb924003_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4045b84d97407cfe02c6503262b944745bec65d87bd08ea7c5367aa8fe03dfa1 +size 21546 diff --git a/marked/Rel-11/23_series/23849/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-11/23_series/23849/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..280ada80675afdf0067e56798cddf638486286a6 --- /dev/null +++ b/marked/Rel-11/23_series/23849/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:902bb77dec3409667a1e62a272160d69bb55372400ca94e07acbe335ba251a71 +size 155789 diff --git a/marked/Rel-11/23_series/23849/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-11/23_series/23849/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8f4836d3093ad70856ba2bffeca0c8b8e1f9773 --- /dev/null +++ b/marked/Rel-11/23_series/23849/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e720b296cbd0ed44ceac231aa5243b54e23ef2f3a9c72716ea7ea68d757fe60 +size 38593 diff --git a/marked/Rel-11/23_series/23849/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-11/23_series/23849/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2e30c8984903ff26209d6454f4f94cac14b867e --- /dev/null +++ b/marked/Rel-11/23_series/23849/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24a6be64f200e9e137ac3b3cd3b22fc240e7ccd92fc55a1be5d34bbfc57f2561 +size 119521 diff --git a/marked/Rel-11/23_series/23849/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-11/23_series/23849/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71c65e4afdc2c1ad83064cb1467b2d039ed4edba --- /dev/null +++ b/marked/Rel-11/23_series/23849/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fad72924e3bde4a1566247cfe208c4d2a2ddc9628287c8a814df259c4d77f02 +size 134118 diff --git a/marked/Rel-11/23_series/23849/a51105b2031bad93b818b82f071c6add_img.jpg b/marked/Rel-11/23_series/23849/a51105b2031bad93b818b82f071c6add_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8ab5ce2d9bff56186faa8b29620faf95d709706 --- /dev/null +++ b/marked/Rel-11/23_series/23849/a51105b2031bad93b818b82f071c6add_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a16a0b16e4036488305f72529a2279dfe342c79940556ed165fe30a001c5b9d6 +size 30522 diff --git a/marked/Rel-11/23_series/23849/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-11/23_series/23849/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56cb83a64d6a380cd37a89f7f86c17df2e755f7b --- /dev/null +++ b/marked/Rel-11/23_series/23849/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3cf3cc8328bd32e2cf2844db9959fb5e74055fdc05a76a2f758e5a4639bee092 +size 104226 diff --git a/marked/Rel-11/23_series/23849/cf4ac1058c52bc3ca37737740afb7f2c_img.jpg b/marked/Rel-11/23_series/23849/cf4ac1058c52bc3ca37737740afb7f2c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e967d639fd8068514ee73ad686c25d85e17b550 --- /dev/null +++ b/marked/Rel-11/23_series/23849/cf4ac1058c52bc3ca37737740afb7f2c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec80fe73ed108a631ec932af2c0ddf6ef0eda6d61c2515a5f884e9c4f7ccca2c +size 84311 diff --git a/marked/Rel-11/23_series/23849/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-11/23_series/23849/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc67f08f8f22a313c1205021fe1f0314131fcca9 --- /dev/null +++ b/marked/Rel-11/23_series/23849/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5f39d6161966d41c9a2f52c9d12fd7a2491b173c3a6e29a7f32dab39ed27ecf +size 125135 diff --git a/marked/Rel-11/23_series/23849/raw.md b/marked/Rel-11/23_series/23849/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..53d683de13fa985c2be63dbdf90cc068a01b4e79 --- /dev/null +++ b/marked/Rel-11/23_series/23849/raw.md @@ -0,0 +1,769 @@ + + + + + + +# --- Contents + +| | | +|-----------------------------------------------------------------|----| +| Foreword ..... | 4 | +| Introduction ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 5 | +| 4 Assumptions, architectural requirements, and use cases ..... | 6 | +| 4.1 Assumptions..... | 6 | +| 4.2 Architectural Requirements..... | 6 | +| 5 Solution Alternatives..... | 7 | +| 5.1 Solution Alternatives for Allocation of Resources ..... | 7 | +| 5.1.1 Introduction ..... | 7 | +| 5.1.2 Tones/Announcements insertion in the VPLMN ..... | 7 | +| 5.1.3 Conferencing ..... | 10 | +| 5.1.4 Transcoding at Network Edge ..... | 12 | +| 5.1.5 Transcoding in IMS core network..... | 14 | +| 5.1.5.1 Proactive transcoding using MRF in visited network..... | 14 | +| 5.1.5.2 Reactive transcoding using MRF in visited network..... | 16 | +| 5.1.6 Transcoder placement alternative..... | 18 | +| 5.1.7 IBCF interactions..... | 19 | +| 5.1.7.1 General..... | 19 | +| 5.1.7.2 Impact on IMS NNI ..... | 19 | +| 5.1.7.3 Optimal Media Routing ..... | 19 | +| 5.1.8 Optimal MRF placement for RAVEL scenarios ..... | 19 | +| 5.2 Solution Alternatives for MRF/MRB discovery ..... | 20 | +| 5.2.1 MRF/MRB Selection at Registration ..... | 20 | +| 5.2.2 MRF/MRB Selection at Session initiation ..... | 20 | +| 5.2.3 AS is configured with VPLMN MRF address ..... | 21 | +| 5.2.4 AS uses MRB in Query Mode..... | 21 | +| 5.2.5 AS uses MRB in In-Line Mode..... | 21 | +| 6 Assessment..... | 23 | +| 7 Conclusion ..... | 25 | +| Annex A: Change history..... | 27 | + +# --- 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 capability to allow media to be routed in an optimal manner between IMS operators when the subscriber is roaming was introduced in Rel-10. However, certain features may require that the media is controlled by the home network. These features include conferencing, transcoding, tones insertion and announcement insertion. + +In these cases, the media plane is typically re-directed back to the home network to perform these functions. For transcoding, the media would have to stay routed through the home network for the duration of the call. However, for tone and announcement insertion, there is the possibility to temporarily re-direct the media plane through the home network only for the duration of the tone/announcement. Unfortunately, neither of these solutions is ideal from a subscriber's perspective as it potentially introduces delay between the call parties. In addition, the subscriber will also experience a cut-out of media whilst the re-direction is performed (if redirected mid-call e.g. for tone/announcement insertion). This increases the risk of the call being cut-off (e.g. if the redirect fails for some reason). + +# --- 1 Scope + +The present document provides a study into the new (Rel-11) requirements identified by SA WG1 to allow a home network to control a visited network to perform the following IMS functions for its subscribers: + +- conferencing (network hosted); +- transcoding; +- tone insertion; and +- announcement insertion. + +# --- 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 TR 21.801: "Specification drafting rules". +- [3] 3GPP TS 23.218: "IP Multimedia (IM) Session Handling; IM call model; Stage 2". +- [4] 3GPP TS 23.228: " IP multimedia subsystem; Stage 2". +- [5] 3GPP TS 24.229: "IP multimedia call control protocol based on SIP and SDP; stage 3". +- [6] 3GPP TR 23.850: "Study on Roaming Architecture for Voice over IMS with Local Breakout". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] apply. + +## 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]. + +| | | +|-------|-----------------------------------------| +| AS | Application Server | +| B2BUA | Back to back user agent | +| CS | Circuit Switched | +| CSCF | Call Session Control Function | +| HPLMN | Home Public Land Mobile Network | +| IBCF | Interconnection Border Control Function | +| MGCF | Media Gateway Control Function | +| MRB | Media Resource Broker | +| MRF | Media Resource Function | +| MRFC | Media Resource Function Controller | + +| | | +|--------|------------------------------------| +| MRFP | Media Resource Function Processor | +| I-CSCF | Interrogating CSCF | +| P-CSCF | Proxy CSCF | +| S-CSCF | Serving CSCF | +| SDP | Session Description Protocol | +| SIP | Session Initiation Protocol | +| TCP | Transmission Control Protocol | +| TrGW | Translation Gateway | +| UDP | User Datagram Protocol | +| UE | User Equipment | +| VPLMN | Visited Public Land Mobile Network | + +# --- 4 Assumptions, architectural requirements, and use cases + +## 4.1 Assumptions + +The following assumptions need to be borne in mind for the chosen solution, and add clarity to the architectural requirements that follow in the next sub-clause: + +- The subscribers involved in the solution are assumed to be inbound roaming subscribers from another PLMN operator. However, there should be nothing preventing a PLMN using it for its own subscribers, if it so wishes. +- Any Private and Public Identity selection that is preconfigured in the VPLMN is statically configured and agreed by the HPLMN through usual inter-PLMN commercial roaming agreements. + +## 4.2 Architectural Requirements + +The chosen solution shall fulfil the following architectural requirements: + +- Can avoid the need to route the IMS media plane via the HPLMN for the IMS functions as listed in the Scope section of the present document. +- Shall have minimal impact on the existing IMS architecture and shall reuse or enhance existing interfaces/reference points wherever possible. +- Can be invoked selectively by the VPLMN as follows: + - On a per subscriber basis such as: + - static configuration in the VPLMN; and + - subscriber profile flag conveyed by the HPLMN. + - On a per IMS function (as listed in the Scope section of the present document) such as: + - static configuration in the VPLMN; and + - subscriber profile flag conveyed by the HPLMN. +- The VPLMN can deny all or a sub-set of the IMS functions (as listed in the Scope section of the present document) to all or a defined sub-set of subscribers at any session establishment (e.g. due to a lack of capacity/availability). +- Architecture alternatives shall avoid disclosing the hierarchy of operator's resources network and the operator's selected deployments of AS/MRF, MRFC/MRFP and/or MRB/MRFC. + +NOTE: The language used in all of the above bullets is in compliance with TR 21.801 [2], Annex E. As such, the term "can" is used in place of the phrase "shall be able to" (the latter of which is commonly used in other TRs). + +# 5 Solution Alternatives + +## 5.1 Solution Alternatives for Allocation of Resources + +### 5.1.1 Introduction + +Currently, the MRF is limited to HPLMN, which results in media having to be home-routed either temporarily or permanently, in order to place the MRF in its path, resulting in a simplified architecture as follows: + +![Figure 5.1.1-1: Simplified architecture diagram showing media routing between two User Equipment (UE) devices across different PLMNs (VPLMN A, HPLMN A, VPLMN B, HPLMN B) via various network functions (P-CSCF, I/S-CSCF, MRFC, MRFP).](1c953f32bd34345dfd68fddf8a3736d6_img.jpg) + +The diagram illustrates a simplified architecture for media routing. It consists of four main network areas: VPLMN A (top left), HPLMN A (top right), VPLMN B (bottom left), and HPLMN B (bottom right). In VPLMN A, a UE is connected to a P-CSCF. In HPLMN A, an I/S-CSCF is connected to the P-CSCF from VPLMN A, and an MRF (containing MRFC and MRFP) is connected to the I/S-CSCF. In VPLMN B, another UE is connected to a P-CSCF, which is connected to an I/S-CSCF in HPLMN B. A red line represents the signaling path, connecting the UE in VPLMN A to the UE in VPLMN B via the P-CSCF in VPLMN B. A blue line represents the media path, connecting the UE in VPLMN A to the MRF in HPLMN A, and then from the MRF to the UE in VPLMN B via the I/S-CSCF in HPLMN B and the P-CSCF in VPLMN B. + +Figure 5.1.1-1: Simplified architecture diagram showing media routing between two User Equipment (UE) devices across different PLMNs (VPLMN A, HPLMN A, VPLMN B, HPLMN B) via various network functions (P-CSCF, I/S-CSCF, MRFC, MRFP). + +Figure 5.1.1-1 + +This was identified as one of the reasons why operators could not fully realize Optimal Media Routing, when transcoding, conferencing, tone or announcements insertion is needed. + +NOTE: Although other scenarios are commonly used for allocation of resources, e.g. AS interfacing MRFC or using MRB in query and/or in-line mode, for the sake of simplicity, just the one involving the S-CSCF in the signalling path has been shown. + +The following sub-clauses discuss solutions for allocating and provisioning of certain resources (as specified in clause 4 of the present document) to inbound roaming IMS subscribers. All architecture solutions shall follow the constraints specified in clause 4. + +### 5.1.2 Tones/Announcements insertion in the VPLMN + +Announcement/tone insertion is not that commonly used for calls once those have commenced. Some common cases for insertion of tones/announcements relate to conference calls, with optimizations discussed in chapter 5.2.3, and pre-paid calls in which the user is indicated limit of credit by means of tones. + +For cases other than conferencing, the sequence of playing announcements/tones for a UE-originating IMS session is depicted in the figure below. An AS (acting as B2BUA) performs third party call control with the MRF, where the S-CSCF is in the signalling path. + +The AS interacts with the UE as usual to establish the dialog. + +Upon detecting tone/announcement needs to be played and the UE is located in the VPLMN, the AS may perform two different actions, depending on whether a MRB (in query mode) exists or just the MRF needs to be contacted: + +- 1 An MRB is interrogated to assign an MRF fitting the characteristics demanded by the service. The MRB will return the address of the relevant MRF in the VPLMN and the AS will simply initiate a dialogue towards that MRF for playing the announcement. + +2. An MRB is invoked to select an MRF fitting the characteristics demanded by the service. The MRB should then contact directly the relevant MRF in the VPLMN, inserting itself in the dialogue path between the AS and the MRF. + +This becomes an alternative of the existing MRB in In-line mode in which the MRB returns the MRF address to the AS which in turn initiates session towards the S-CSCF and MRFC in the normal offer/answer model. + +3. In the absence of MRB, the AS will select relevant MRF in the VPLMN and the normal offer/answer model will be used in the negotiation between the AS/S-CSCF, in the HPLMN, and the MRFC in the VPLMN. + +The discovery of the MRB/MRF in the VPLMN by the AS may be done by configuration agreed between VPLMN and HPLMN or by provisioning at registration or session establishment. + +If the MRB is located in the HPLMN, it may be configured to have a list of the MRFs in the VPLMN fitting the characteristics of the service demanded. + +NOTE 1: Standardization of announcements across the interfaces is not intended. + +NOTE 2: Charging records are generated by the entities in both VPLMN and HPLMN. Charging of services in the VPLMN will be a matter of agreements between both operators. + +![Sequence diagram illustrating Tones/Announcements insertion in VPLMN. The diagram shows interactions between MRF, AS, S-CSCF, and MRB across Visited and Home Networks.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +``` + +sequenceDiagram + box Visited Network + participant MRF + end + box Home Network + participant AS + participant S-CSCF + end + participant MRB + + Note over S-CSCF: 1. Session Initiation [1] + S-CSCF->>AS: + AS->>S-CSCF: 2. Session Initiation [1] + Note over AS: 3. Service Logic + rect rgb(255, 255, 255) + Note over AS,S-CSCF: 4. Session Initiation [2] + AS->>S-CSCF: + end + Note over S-CSCF,AS: 5. Session Failure + S-CSCF->>AS: + rect rgb(255, 255, 255) + Note over S-CSCF,AS: 6. Session Failure [2] + S-CSCF->>AS: + end + Note over AS: 7. Service Logic + Note over AS: 8. MRB / MRF Service Discovery +- Provisioning from VPLMN at registration or session Initiation +- Configuration in HPLMN + Note over AS,MRB: 9a. Invoke MRF via MRB (new leg) + AS->>MRB: + Note over AS,S-CSCF: 9b. Session Initiation to MRF via S-CSCF, MRF selects media resources (new leg) + AS->>S-CSCF: + Note over MRF,S-CSCF: 10. Dialogue 1 is handled normally using the information from MRF +11. QoS and resources are reserved + Note over MRF,AS: 12. Play Tone/Announcement + +``` + +Sequence diagram illustrating Tones/Announcements insertion in VPLMN. The diagram shows interactions between MRF, AS, S-CSCF, and MRB across Visited and Home Networks. + +**Figure 5.1.2-1: Tones/Announcements insertion in VPLMN** + +- 1) A session initiation request is received at the S-CSCF (Call 1). +- 2) The session request is forwarded to an AS, based on the filter criteria. +- 3) The AS service logic determines to proceed with the call. +- 4) New session initiation request is sent towards destination, via the S-CSCF, to establish a new leg (Call 2). +- 5) A failure is detected; call cannot proceed. +- 6) Session failure returned to the AS. +- 7) The AS service logic determines to play an announcement/tone to the calling party. +- 8) The AS determines which MRB/MRF to address and depending on the presence of MRB, its mode of operation or simply MRF, different flows exist. +- 9a) For MRB in In-line mode, the session initiation is sent to the MRB, which in turn establishes the session towards the MRF. Sufficient information is included to specify the details for the announcement/tone (Call 3). + +9b) For MRB in Query mode, or for MRF either provisioned by VPLMN or configured at HPLMN, the dialogue is established via the S-CSCF. + +10-12) The MRF allocates the requested resource and indicates selected media. The AS manages the dialog for Call 1 as normal, with the info provided by the MRF. MRF plays the announcement as instructed. + +### 5.1.3 Conferencing + +Conferencing is realised by routing all the media via a focus (same as a bridge in CS terms) so where the focus entity is based becomes irrelevant to the UE; UE just need to be able to address the focus in order to route the traffic to it. + +There are, however, several cases with conferencing: + +- Ad-hoc conferencing. +- Network based conferencing (AS/MRF hosted service). + +Routing optimizations are mainly relevant to the cases in which the roaming user is in charge of the conferencing control, e.g. creating, managing or terminating a conference by means of a conference URI. Joining or leaving network hosted conferences servers may observe different optimizations. + +The figure below shows a sequence of a roaming user establishing a multiparty call service. The Application Server, in control of the conference, operates as B2BUA performing 3rd party control towards the VPLMN-MRF by either: + +- interrogating an MRB (either in the VPLMN or HPLMN) to retrieve the VPLMN-MRF address fitting the capabilities demanded by the conference, or +- being already aware of the VPLMN-MRF capabilities (by VPLMN provisioning or configuration at the HPLMN). + +In order to optimize the routing and control of the conferencing resources, the AS shall determine whether break-out can be performed in the VPLMN or in HPLMN, after analyzing the availability of resources and the parties involved in the call. i.e. at session initiation, AS receives the Ad-hoc conference indication from the roaming UE, for the existing sessions with UE2 and UE3 (as shown in the following figure), being able to determine, on a per operator policy, whether the breakout shall take place in the VPLMN where user1 is roaming, in the HPLMN, or in the PLMNs where user2 and user3 are camping. + +In case the AS decides that breakout shall occur in a PLMN different than the VPLMN1, it will not execute discovery of the VPLMN1 MRF; instead it shall: + +- either allocate an MRF belonging to the HPLMN network or, +- execute MRF service discovery in the UE2 and/or UE3 PLMNs. + +NOTE: OMR is required to optimize the media flows in these conferencing scenarios, when other PLMN's are involved. + +![Sequence diagram for Conferencing with MRF in VPLMN showing interactions between MRF, AS, S-CSCF, and MRB across network boundaries.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` + +sequenceDiagram + participant MRF + participant MRB + participant AS + participant S-CSCF + + Note over MRF, MRB: Home/Visited Network + Note over AS, S-CSCF: Home Network + + Note left of S-CSCF: 1. Session Initiation (ad-hoc conf) [1] + S-CSCF->>AS: 2. Session Init (ad-hoc conf) [1] + Note over AS: 3. Service Logic + Note over AS: 4. MRB/MRF Service Discovery: +- Provisioning from VPLMN at registration or session initiation +- Configuration in HPLMN + AS->>MRB: 5a. Establish session via MRB (new leg 2) + MRB->>AS: + AS->>S-CSCF: 5b. Session Initiation to MRF via S-CSCF, MRF selects media resources (new leg 2) + S-CSCF->>MRF: + AS->>S-CSCF: 6. Session Init. (UE2) [3] + S-CSCF->>AS: 7. Session Init. (UE2) [3] + Note over MRF, S-CSCF: 8. Establish path between UE2 and MRF + Note over MRF, S-CSCF: 9. Repeat steps 5-11 for UE3 [4], [5] + AS->>S-CSCF: 10. Session Init (UE1) [6] + S-CSCF->>MRF: 11. Session Initiation(UE1) [6] + MRF->>S-CSCF: 12. 200OK(UE1) [6] + S-CSCF->>AS: 13. 200 OK (UE1) [6] + AS->>S-CSCF: 14. 200 OK (UE1) [1] + S-CSCF->>MRF: 15. 200 OK(UE1) [1] + Note over MRF, S-CSCF: 16. Establish path between UE1 and MRF + +``` + +Sequence diagram for Conferencing with MRF in VPLMN showing interactions between MRF, AS, S-CSCF, and MRB across network boundaries. + +**Figure 5.1.3-1: Conferencing with MRF in VPLMN** + +- 1) Session initiation received at S-CSCF from UE1 to start ad hoc conference (Call 1) for existing sessions with UE2 and UE-3. +- 2) Session request forwarded to AS. +- 3) AS performs service logic starts ad hoc conference. The availability of resources and the location of UE1, UE2 and UE3 is determined in order to decide breakout in the VPLMN or HPLMN. +- 4) The AS determines which MRB/MRF to address and depending on the presence of MRB, its mode of operation or simply MRF, different flows exist. +- 5a) For MRB in In-line mode, the session initiation is sent to the MRB, which in turn establishes the session towards the MRF. Sufficient information is included to specify the details for the announcement/tone (Call 2). If AS has + +determined that break-out would occur at the VPLMN where UE1 resides, the MRF addressed is also located in the VPLMN. Otherwise, the MRF addressed in these steps is located in the HPLMN or in a VPLMN where UE2 and UE3 are located. + +5b) For MRB in Query mode, or for MRF either provisioned by VPLMN or configured at HPLMN, the dialogue is established via the S-CSCF (call 2). + +If AS has determined that break-out will occur at the VPLMN where UE1 resides, the MRF addressed is also located in the VPLMN. Otherwise, the MRF addressed in these steps is located in the HPLMN or in a VPLMN where UE2 and UE3 are located. + +6-7) Establish dialog between AS and UE2 (Call 3). + +8) Path established between MRF and UE2. + +9) New session request towards MRF for UE3 (Call 4); establish dialog with UE3 (Call 5) and path between MRF and UE3. + +10-15) New session request sent to MRF for UE1 (Call 6); response returned to the ad-hoc conference request (Call 1). + +16) The session is established. + +### 5.1.4 Transcoding at Network Edge + +Although transcoding is done in the MRF in the existing specifications, a clear optimization for roaming subscribers is to make use of the IBCF/TrGW transcoding capabilities since they are ideally located at the edge of the NNI for such purpose. + +The usage of IBCF/TrGW for transcoding can be done based on static policies and commercial agreements between the PLMN and HPLMN. + +The following flow shows the reactive transcoding scenario depicted in TS 23.228 [4] where IBCF/TrGW performs the transcoding function after a failure to establish a session due to lack of common codec. This usage is already today provided upon agreement between IM CN subsystems. + +![Sequence diagram showing transcoding at network edge between Visited Network (IBCF, TrGW) and Home Network. Steps include Session Initiation, Session response, Codec mismatch detected, Initiation procedures, Codec negotiation, Codec negotiation response, Update transcoding device, and final Session response (cont.).](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +The diagram illustrates a sequence of messages between a Visited Network and a Home Network. The Visited Network contains two main components: IBCF and TrGW. The sequence of events is as follows: + +- 1. Session Initiation:** An external entity sends a session initiation request to the IBCF. The IBCF then forwards this request (labeled '1.') to the TrGW. +- 2. Session response:** The TrGW sends a session response back to the IBCF. +- 3. Codec mismatch detected:** The IBCF detects a codec mismatch. This step is highlighted with a dashed box. +- 4. Initiation procedures:** The IBCF and TrGW perform internal initiation procedures. +- 5. Codec negotiation:** The TrGW sends a codec negotiation message to an external entity. +- 6. Codec negotiation response:** The external entity sends a codec negotiation response back to the TrGW. +- 7. Update transcoding device:** The TrGW sends an update message to the IBCF to configure the transcoding device. +- 8. Session response (cont.):** Finally, the IBCF sends a continued session response to the external entity. + +The final state is indicated by a dashed box at the bottom: **Call established via transcoding device**. + +Sequence diagram showing transcoding at network edge between Visited Network (IBCF, TrGW) and Home Network. Steps include Session Initiation, Session response, Codec mismatch detected, Initiation procedures, Codec negotiation, Codec negotiation response, Update transcoding device, and final Session response (cont.). + +**Figure 5.1.4-1: Transcoding at Network Edge** + +1. Roaming UE (A) initiates an IMS session towards User B, and the session is analysed at the IBCF. The SDP offer is forwarded towards User B. + +2. A subsequent entity in the signalling path determines that it does not support any codec in the SDP offer and answers with an appropriate error response. This response may include a list of supported Codecs. +3. Based on the response, the IBCF detects the need for reactive transcoding invocation. +4. The IBCF instructs the TrGW to allocate media processing resources for the session, allocate appropriate transcoding resources for the session and bridge the media flows between the calling and called party endpoints. +5. Based on the response from the TrGW, the IBCF creates a new SDP offer that contains the codec and transport address information received from the TrGW. +6. UE (B) selects a codec and acknowledges the SDP offer with an SDP answer. +7. Upon receipt of the SDP answer, the IBCF updates the TrGW with the information from the SDP answer. +8. The IBCF prepares an answer to the offer in step 1, including the selected codec and transport address information for the originating side of the TrGW. The session between the end-points is now established with the media flow traversing the transcoding device. + +At session release, the codec transcoding resource will be released. + +### 5.1.5 Transcoding in IMS core network + +#### 5.1.5.1 Proactive transcoding using MRF in visited network + +This scenario shows how transcoding is performed using the MRF in the visited network. The discovery of MRF in the visited network is as per MRF discovery in clauses 5.2.1, 5.2.2 and 5.2.3. In this case, transcoding is performed prior to sending the session establishment request to the called party. The following information flow in figure 5.1.5.1-1 is an extension of the requirements in TS 23.228 [4], clause 5.14.4 and Annex P. + +![Sequence diagram showing proactive transcoding using an MRF in the visited network. The diagram is divided into two dashed boxes: 'Visited network' (containing MRF) and 'Home network' (containing AS and S-CSCF). The sequence of messages is: 1. Session initiation request from Visited network to S-CSCF; 2. Session initiation request from S-CSCF to AS; 3. Service logic (internal AS); 4. Need for transcoding detected (internal AS); 5. MRF discovery (internal AS); 6. Invoke MRF (AS to MRF); 7. Session initiation request from AS to S-CSCF; 8. Session initiation request from S-CSCF to Visited network; 9. Session response from Visited network to S-CSCF; 10. Session response from S-CSCF to AS; 11. Update MRF (AS to MRF); 12. Session response from AS to S-CSCF; 13. Session response from S-CSCF to Visited network; 14. Establish session (spanning across all components).](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` +sequenceDiagram + participant Visited network + participant MRF + participant AS + participant S-CSCF + Note right of AS: 3. Service logic + Note right of AS: 4. Need for transcoding detected + Note right of AS: 5. MRF discovery + + Visited network->>S-CSCF: 1. Session initiation request + S-CSCF->>AS: 2. Session initiation request + AS->>AS: 3. Service logic + AS->>AS: 4. Need for transcoding detected + AS->>AS: 5. MRF discovery + AS->>MRF: 6. Invoke MRF + AS->>S-CSCF: 7. Session initiation request + S-CSCF->>Visited network: 8. Session initiation request + Visited network->>S-CSCF: 9. Session response + S-CSCF->>AS: 10. Session response + AS->>MRF: 11. Update MRF + AS->>S-CSCF: 12. Session response + S-CSCF->>Visited network: 13. Session response + Visited network->>AS: 14. Establish session +``` + +Sequence diagram showing proactive transcoding using an MRF in the visited network. The diagram is divided into two dashed boxes: 'Visited network' (containing MRF) and 'Home network' (containing AS and S-CSCF). The sequence of messages is: 1. Session initiation request from Visited network to S-CSCF; 2. Session initiation request from S-CSCF to AS; 3. Service logic (internal AS); 4. Need for transcoding detected (internal AS); 5. MRF discovery (internal AS); 6. Invoke MRF (AS to MRF); 7. Session initiation request from AS to S-CSCF; 8. Session initiation request from S-CSCF to Visited network; 9. Session response from Visited network to S-CSCF; 10. Session response from S-CSCF to AS; 11. Update MRF (AS to MRF); 12. Session response from AS to S-CSCF; 13. Session response from S-CSCF to Visited network; 14. Establish session (spanning across all components). + +**Figure 5.1.5.1-1: Proactive transcoding using an MRF in the visited network** + +- 1) A calling party UE sends session establishment request to a called party UE, including an SDP offer with media components, supported Codecs, IP address and port number at which the UE wishes to receive media. +- 2) As a result of filter criteria evaluation, the request is forwarded to an AS. + +- 3) AS service logic determines to proceed with the call and may apply originating services to the call. +- 4) The need for proactive transcoding invocation is detected by the AS. If the SDP offer does not include any codec known to be supported by the called party UE, then the AS is triggered to set up a SIP session with the MRFC, providing Codecs and transport parameters to initiate a transcoding session. +- 5) The AS discovers an MRF in the visited network either through an pre-configured MRF address for an MRF in the visited network which can be used for transcoding purposes, or by querying an MRB, either in the visited network or in the home network, which returns the address of an MRF in the visited network which can be used for transcoding purposes. As an alternative, MRB in In-line mode can initiate itself the request to the MRF, placing itself this way in the session path between the AS and the MRF. +- 6) The AS instructs the MRFC to: + - allocate media processing resources from an MRFP entity under the MRFC's control, configured with the address and port at which the calling UE wishes to receive media, using a codec (say, codec-A) previously included by the calling party UE in the SDP offer and hence known to be supported; + - allocate media processing resources from the same MRFP entity to the called party UE, using a codec (say, codec-B) known to be supported by the called party UE; and + - cause the MRFP entity to bridge those two media flows, such that media received on one will be converted to the format of and transmitted on the other. + +The MRFC accepts the transcoding request and contacts an MRFP to allocate the requested resources. The MRFP responds with the IP address and port number associated with each requested codec. The MRFC returns this information to the AS. + +- 7-8) The AS updates the SIP request received in step 2 by appending codec-B to the list of Codecs in the SDP offer (after all Codecs that were previously in the offer), and altering the transport address and port information to indicate the addresses associated by the MRFP with its resources of type codec-B. The session establishment request is then routed towards the called party UE. +- 9-10) The called party UE acknowledges the SDP offer and makes a codec selection, providing in the SDP answer the IP address and TCP or UDP port at which it wants to receive media. +- 11) Upon receipt of the answer from the called party UE, the AS updates the session with the MRFC (providing the codec selected and the address /port information from the SDP answer). The MRFC processes the received information to configure the transcoding unit with the codec, the destination address and port towards the called party UE. +- 12-13) The AS modifies the SDP answer received from the called party UE such that it refers to codec-A and the MRFP address and port number associated with it in step 10, and sends this message to the calling party UE. +- 14) The session between the end points is now established with the media flow traversing the transcoding device. + +#### 5.1.5.2 Reactive transcoding using MRF in visited network + +This scenario shows how reactive transcoding is performed using the MRF in the visited network. The discovery of MRF in the visited network is as per MRF discovery in clauses 5.2.1, 5.2.2 and 5.2.3. In this case, transcoding is performed after receiving an error response from the called party indicating that the Codecs offered in the session establishment request are not supported. The following information flow in figure 5.1.5.2-1 is an extension of the requirements in TS 23.228 [4], clause 5.14.4 and Annex P. + +![Sequence diagram for proactive transcoding using an MRF in the visited network. The diagram shows interactions between MRF, AS, and S-CSCF across Visited and Home networks.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` +sequenceDiagram + participant UE as User Equipment + participant MRF as MRF + participant AS as AS + participant S-CSCF as S-CSCF + + Note left of MRF: Visited network + Note right of S-CSCF: Home network + + UE->>S-CSCF: 1. Session initiation request + S-CSCF->>AS: 2. Session initiation request + AS->>AS: 3. Service logic + AS->>S-CSCF: 4. Session initiation request + S-CSCF->>UE: 5. Session initiation request + UE->>S-CSCF: 6. Session response + S-CSCF->>AS: 7. Session response + AS->>AS: 8. Codec mismatch detected + AS->>AS: 9. MRF discovery + AS->>MRF: 10. Invoke MRF + AS->>S-CSCF: 11. Session initiation request + S-CSCF->>UE: 12. Session initiation request + UE->>S-CSCF: 13. Session response + S-CSCF->>AS: 14. Session response + AS->>MRF: 15. Update MRF + AS->>S-CSCF: 16. Session response + S-CSCF->>UE: 17. Session response + Note right of S-CSCF: 18. Establish session +``` + +The sequence diagram illustrates the interaction for proactive transcoding. It begins with a 'Session initiation request' (1) from the UE to the S-CSCF. The S-CSCF forwards this to the AS (2). The AS performs 'Service logic' (3) and then sends another 'Session initiation request' (4) to the S-CSCF. The S-CSCF sends this to the UE (5). The UE responds with a 'Session response' (6), which is passed back to the AS (7). The AS detects a 'Codec mismatch' (8) and initiates 'MRF discovery' (9). It then sends an 'Invoke MRF' message (10) to the MRF. The AS sends a 'Session initiation request' (11) to the S-CSCF, which in turn sends it to the UE (12). The UE sends a 'Session response' (13) to the S-CSCF, which passes it to the AS (14). The AS sends an 'Update MRF' message (15) to the MRF and a 'Session response' (16) to the S-CSCF. Finally, the S-CSCF sends a 'Session response' (17) to the UE, and the session is established (18). + +Sequence diagram for proactive transcoding using an MRF in the visited network. The diagram shows interactions between MRF, AS, and S-CSCF across Visited and Home networks. + +**Figure 5.1.5.2-1: Proactive transcoding using an MRF in the visited network** + +- 1) A calling party UE sends session establishment request to a called party UE, including an SDP offer with media components, supported Codecs, IP address and port number at which the UE wishes to receive media. +- 2) As a result of filter criteria evaluation, the request is forwarded to an AS + +- 3) AS service logic determines to proceed with the call and may apply originating services to the call. In this case proactive transcoding is not executed since the need for transcoding may not yet be known. + - 4-5) The session establishment request is routed towards the called party UE. + - 6-7) The called party UE or a terminating network entity (such as MGCF) determines that it does not support any codec in the SDP offer and answers with an appropriate error response. This response can include a list of Codecs that the called party UE can support. + - 8) The AS detects the codec mismatch as a result of receiving the error response from the called party UE. AS service logic determines that transcoding is necessary and proceeds to determine a suitable MRF to carry out transcoding for this session. + - 9) The AS discovers an MRF in the visited network either through an pre-configured MRF address for an MRF in the visited network which can be used for transcoding purposes, or by querying an MRB, either in the visited network or in the home network, which returns the address of an MRF in the visited network which can be used for transcoding purposes. As an alternative, MRB in In-line mode can initiate itself the request to the MRF, placing itself this way in the session path between the AS and the MRF. + - 10) The AS instructs the MRFC to: + - allocate media processing resources from an MRFP entity under the MRFC's control, configured with the address and port at which the calling UE wishes to receive media, using a codec (say, codec-A) previously included by calling party UE in the SDP offer hence known to be supported by calling UE; + - allocate media processing resources from the same MRFP entity to called party UE, using a codec (say, codec-B) known to be supported by called party UE; and + - cause the MRFP entity to bridge those two media flows, such that media received on one will be converted to the format of and transmitted on the other. +- The MRFC accepts the transcoding request and contacts an MRFP to allocate the requested resources. The MRFP responds with the IP address and port number associated with each requested codec. The MRFC returns this information to the AS. +- 11-12) Based on the information received from the MRFC, the AS creates a new SDP offer that contains the information provided by the MRFC (codec and transport addresses). If no information about supported Codecs was available from the error response, the invoking function offers all Codecs supported by the transcoding device. It sends this offer to the called party UE. + - 13-14) The called party UE acknowledges the SDP offer and makes a codec selection, providing in the SDP answer the IP address and TCP or UDP port at which it wants to receive media. + - 15) Upon receipt of the answer from the called party UE, the AS updates the session with the MRFC (providing the codec selected and the address /port information from the SDP answer). The MRFC processes the received information to configure the transcoding unit with the codec, the destination address and port towards the called party UE. + - 16-17) The AS modifies the SDP answer received from the called party UE such that it refers to codec-A and the MRFP address and port number associated with it in step 10, and sends this message to the calling party UE. + - 18) The session between the end points is now established with the media flow traversing the transcoding device. + +### 5.1.6 Transcoder placement alternative + +In this alternative the session transcoding function is co-located with the AGW in the VPLMN under control of the P-CSCF, using the same procedures currently described for the IBCF in TS 23.228 [4]. + +Since transcoding is also a capability required of the ATGW for eSRVCC scenarios, it is reasonable to consider use of the same transcoding element for transcoding between mismatched UA Codecs as well as for eSRVCC. + +The ATCF is generally expected to be co-located with an existing functional element in the IMS architecture, such as the P-CSCF, IBCF or MSC server. The most likely candidate for ATCF co-location is the P-CSCF, since it is already in the path of all UE signalling with IMS. The IBCF is only in the path for a session when the UE is roaming, and the + +MSC server is only involved in a session during and after SRVCC. Thus the IBCF and MSC server are less attractive candidates for co-location with the ATCF. + +### 5.1.7 IBCF interactions + +#### 5.1.7.1 General + +The signalling between an AS and an MRF located in a VPLMN can traverse two IBCFs at the network borders. The following clauses describes some implications of invoking IBCFs on the signalling path between AS and remote MRF. + +#### 5.1.7.2 Impact on IMS NNI + +Signalling associated with the Cr, Mr and Mr' reference points for interaction with the MRF are not currently within the scope of the IMS NNI and related impacts shall be studied and addressed by stage 3 work. + +#### 5.1.7.3 Optimal Media Routing + +In the typical case, an IBCF handling MRF signalling between networks will allocate a TrGW for bearer isolation unless it supports Optimal Media Routing (OMR) to avoid any unnecessary anchoring of the media. + +Figure 5.1.7.3-1 shows an example of the impact of OMR when an AS controls a remote MRF in the VPLMN. + +NOTE: Intermediate IPX networks and IPX proxies can be inserted in the paths between the PLMNs but are not shown in the figure and do not change the flow. + +![Figure 5.1.7.3-1: Impact of OMR on media routing with remote MRF. The diagram compares two network architectures: 'Without OMR' and 'With OMR'. Both show H-PLMN A and V-PLMN A. In 'Without OMR', media flows from the user equipment (UE) through the P-CSCF, then through a series of IBCF+TrGW nodes in the V-PLMN A, then through another IBCF+TrGW node at the border, and finally to the MRF in the H-PLMN A. In 'With OMR', the media flows from the UE through the P-CSCF, then through the IBCF+TrGW nodes in the V-PLMN A, and then directly to the MRF in the H-PLMN A, bypassing the border IBCF+TrGW node.](cf4ac1058c52bc3ca37737740afb7f2c_img.jpg) + +Figure 5.1.7.3-1: Impact of OMR on media routing with remote MRF. The diagram compares two network architectures: 'Without OMR' and 'With OMR'. Both show H-PLMN A and V-PLMN A. In 'Without OMR', media flows from the user equipment (UE) through the P-CSCF, then through a series of IBCF+TrGW nodes in the V-PLMN A, then through another IBCF+TrGW node at the border, and finally to the MRF in the H-PLMN A. In 'With OMR', the media flows from the UE through the P-CSCF, then through the IBCF+TrGW nodes in the V-PLMN A, and then directly to the MRF in the H-PLMN A, bypassing the border IBCF+TrGW node. + +Figure 5.1.7.3-1: Impact of OMR on media routing with remote MRF + +### 5.1.8 Optimal MRF placement for RAVEL scenarios + +The Study on Roaming Architecture for Voice over IMS with Local Breakout (RAVEL) TR 23.850 [6] describes options for the home routing scenario and loopback. + +In the RAVEL home routing scenario, the signalling and media both flow to the HPLMN. In this scenario, there is little point in forcing placement of a media resource under AS control within the VPLMN, ostensibly to create a more efficient media path, when the media flows through the HPLMN anyway. Leaving the MRF in the HPLMN has the added advantage of simplifying the MRF signalling flow (which no longer needs to flow between the HPLMN and VPLMN), while having no detrimental effect on the efficiency of the media path. + +The HPLMN is in general the appropriate network since the media and signalling both flow to the HPLMN. However there may be some scenarios where the resources can be allocated in the VPLMN, or other network. This is subject to local policies. + +The usage of OSCAR optimizes the resource allocation in the VPLMN for the services studied in this report. RAVEL home routing/loopback scenarios may benefit from this optimization and considerations on that will be recorded as part of RAVEL conclusions. + +## 5.2 Solution Alternatives for MRF/MRB discovery + +### 5.2.1 MRF/MRB Selection at Registration + +This option allows the MRF/MRB address to be provided to the home network from the visited network for a specific subscriber during the time of Registration. + +This option requires that the AS that may invoke the MRF/MRB receives 3-party register events from the S-CSCF. + +![Sequence diagram illustrating MRF/MRB Selection at Registration. The diagram shows three entities: P-CSCF (Visited Network), AS (Home Network), and S-CSCF (Home Network). The sequence of messages is: 1. Register (from UE to P-CSCF), 2. Register (MRF/MRB address) (from P-CSCF to S-CSCF), and 3. Register (MRF/MRB address) (from S-CSCF to AS).](a51105b2031bad93b818b82f071c6add_img.jpg) + +``` +sequenceDiagram + participant UE + participant P-CSCF + participant AS + participant S-CSCF + Note left of P-CSCF: Visited Network + Note right of S-CSCF: Home Network + UE->>P-CSCF: 1. Register + P-CSCF->>S-CSCF: 2. Register (MRF/MRB address) + S-CSCF->>AS: 3. Register (MRF/MRB address) +``` + +Sequence diagram illustrating MRF/MRB Selection at Registration. The diagram shows three entities: P-CSCF (Visited Network), AS (Home Network), and S-CSCF (Home Network). The sequence of messages is: 1. Register (from UE to P-CSCF), 2. Register (MRF/MRB address) (from P-CSCF to S-CSCF), and 3. Register (MRF/MRB address) (from S-CSCF to AS). + +**Figure 5.2.1-1: MRF/MRB Selection at Registration** + +1. UE registers to the visited network. +2. P-CSCF in visited network has a set of MRF addresses or MRB address allocated to it that can be used for the roaming users. P-CSCF adds the address to the Register request before forwarding the Register request to the S-CSCF in the home network. +3. The S-CSCF includes the provided address in the 3-party register to the AS. + +### 5.2.2 MRF/MRB Selection at Session initiation + +This option allows the MRF/MRB address to be provided to the home network from the visited network for a specific subscriber when the user originates a call. + +This option cannot be used for terminating calls, but only originating calls. + +![Sequence diagram illustrating MRF/MRB Selection at Session initiation. The diagram shows four main entities: P-CSCF, MRF, AS, and S-CSCF. The P-CSCF and MRF are located in the Visited Network, while the AS and S-CSCF are in the Home Network. The sequence of messages is: 1. Session Initiation from the UE to the P-CSCF; 2. Session Initiation (MRF/MRB address) from the P-CSCF to the S-CSCF; 3. Session Initiation (MRF/MRB address) from the S-CSCF to the AS; 4. MRF invocation from the AS to the MRF.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +``` + +sequenceDiagram + participant UE + participant P-CSCF + participant MRF + participant AS + participant S-CSCF + + Note left of P-CSCF: Visited Network + Note right of S-CSCF: Home Network + + UE->>P-CSCF: 1. Session Initiation + P-CSCF->>S-CSCF: 2. Session Initiation (MRF/MRB address) + S-CSCF->>AS: 3. Session Initiation (MRF/MRB address) + AS->>MRF: 4. MRF invocation + +``` + +Sequence diagram illustrating MRF/MRB Selection at Session initiation. The diagram shows four main entities: P-CSCF, MRF, AS, and S-CSCF. The P-CSCF and MRF are located in the Visited Network, while the AS and S-CSCF are in the Home Network. The sequence of messages is: 1. Session Initiation from the UE to the P-CSCF; 2. Session Initiation (MRF/MRB address) from the P-CSCF to the S-CSCF; 3. Session Initiation (MRF/MRB address) from the S-CSCF to the AS; 4. MRF invocation from the AS to the MRF. + +**Figure 5.2.2-1: MRF/MRB Selection at Session initiation** + +1. UE initiates the session. +2. P-CSCF in visited network has a set of MRF addresses or MRB address allocated to it that can be used for the roaming users. P-CSCF adds the selected address to the Session initiation request before forwarding the request to the S-CSCF in the home network. +3. The S-CSCF forwards the message to the AS. +4. The AS uses the MRF or MRB address to invoke the MRF (according to procedures of previous clauses). + +### 5.2.3 AS is configured with VPLMN MRF address + +In the case where an MRB is not used to determine which MRF is to be used for media resources located in the VPLMN, the AS serving the roaming user shall be provisioned with the address of one or more MRFs located in the VPLMN as per operator policy and roaming agreements. + +Upon receiving a request from a served user, that requires invocation of media resources, the AS first checks if the user is roaming and in which VPLMN the UE is currently located. The AS then selects the most appropriate MRF address from the available MRFs it is aware of. The AS sends a request to the selected MRF to initiate media resource reservation and to retrieve MRF capabilities, Codecs and port numbers for the requested media resources. + +### 5.2.4 AS uses MRB in Query Mode + +In the case where the AS serving the roaming user consults an MRB in Query Mode, the MRB may be located in the home network or in the visited network. In the case where the MRB is in the VPLMN, the AS is provisioned with the address of the MRB in the VPLMN as per operator policy and roaming agreements, or it may become aware of the MRB address at registration or session initiation (according to clauses 5.2.1 and 5.2.2). The query is sent over an inter-operator Rc Interface. + +The AS may include in the query information about the media resources required, including the network domain in which the served user is roaming. The MRB returns the address of an appropriate MRF, to which the AS sends a request to initiate media resource reservation and to retrieve MRF capabilities, Codecs and port numbers for the requested media resources. + +In case the MRB is located in the HPLMN, no major impact is expected in the existing procedures; however, the MRB at the HPLMN needs to know the complete topology of resources in the VPLMN for each service invoked. + +In case the MRB is located in the VPLMN, the topology of the VPLMN is hidden and the HPLMN just needs to know the address of the MRB in the VPLMN. No major impacts foreseen for the actual resource allocation during traffic, except for securing the Cr/Mr/Mr interface crossing inter-operator domain. + +### 5.2.5 AS uses MRB in In-Line Mode + +In the case where the AS serving the roaming user sends a request to invoke media resources, an MRB operating in In-Line Mode may be located in the home network or in the visited network. In the case where the MRB is in the VPLMN, the AS is provisioned with the address of the MRB in the VPLMN as per operator policy and roaming agreements, or it + +may become aware of the MRB address at registration or session initiation (according to clauses 5.2.1 and 5.2.2). The query is sent over an In-Line inter-operator Rc Interface, carrying information about requested media resources. + +The MRB may receive such a request and based upon the information provided in the received request, decide upon which MRF to forward the request towards. . The AS may include in the request information about the media resources required, including the network domain in which the served user is roaming. Upon determining that an MRF in the visited network is available to provide media resources for the roaming user, the request is sent to the selected MRF to initiate media resource reservation and to retrieve MRF capabilities, Codecs and port numbers for the requested media resources. + +The usage of MRB in In-Line Mode is described in TS 23.218 [3]. + +NOTE: Relevant security requirements will be addressed in the stage 3 phase of Rc and, Mr' if these are inter-operator interfaces. Mr is already an inter-operator interface. + +#### MRB in the HPLMN: + +In case the MRB is located in the HPLMN, no major impact is expected in the existing procedures; however, the MRB at the HPLMN needs to know the complete topology of resources in the VPLMN for each service invoked. No additional security would be needed for securing the Mr interface, as it has been an inter-operator interface since Rel5. + +#### MRB in the VPLMN: + +In case the MRB in In-Line mode is located in the VPLMN, the topology of the VPLMN is hidden and the HPLMN just needs to know the address of the MRB in the VPLMN. + +![Diagram illustrating inter-operator traffic when MRB in In-Line mode is located in VPLMN. The diagram shows four main entities: MRB (top left), AS HPLMN (top right), S-CSCF HPLMN (middle right), and MRFC VPLMN (bottom left). The MRB is connected to the AS HPLMN via a horizontal line labeled '1'. The AS HPLMN is connected to the S-CSCF HPLMN via a vertical line. The S-CSCF HPLMN is connected to the MRFC VPLMN via a horizontal line labeled '3'. The MRB is also connected to the MRFC VPLMN via a vertical line labeled '4'. A diagonal line labeled '2' connects the AS HPLMN to the MRFC VPLMN. All connections are marked with a small circle and a cross, indicating they are inter-operator interfaces.](2834bdd6eb8540277e609decbb924003_img.jpg) + +Diagram illustrating inter-operator traffic when MRB in In-Line mode is located in VPLMN. The diagram shows four main entities: MRB (top left), AS HPLMN (top right), S-CSCF HPLMN (middle right), and MRFC VPLMN (bottom left). The MRB is connected to the AS HPLMN via a horizontal line labeled '1'. The AS HPLMN is connected to the S-CSCF HPLMN via a vertical line. The S-CSCF HPLMN is connected to the MRFC VPLMN via a horizontal line labeled '3'. The MRB is also connected to the MRFC VPLMN via a vertical line labeled '4'. A diagonal line labeled '2' connects the AS HPLMN to the MRFC VPLMN. All connections are marked with a small circle and a cross, indicating they are inter-operator interfaces. + +**Figure 5.2.5-1: Inter-operator traffic when MRB in In-Line mode is located in VPLMN** + +Referring to Figure 5.2.5-1, the following interfaces are considered to be inter-operator interfaces under the following conditions: + +1. The interface between AS and MRB traverses network boundaries if MRB is located in the visited network. This is applicable for both MRB Query Mode and MRB In-Line Mode. +2. The interface between AS and visited network MRFC traverses network boundaries. In such configuration, it is assumed that AS has prior knowledge of visited network MRFC address that can service the request for media resources. This can be through configuration, at session registration/initiation or through interacting with an MRB in query mode. +3. The interface between S-CSCF and visited network MRFC traverses network boundaries. In such configuration, it is assumed that AS has prior knowledge of visited network MRFC address that can service the request for media resources. This can be through configuration, at session registration/initiation or through interacting with an MRB in query mode. The S-CSCF proxies such requests for invoking media resources from the AS to the visited network MRFC. + +4. If the MRB is located in the home network, then the interface between the MRB and visited network MRFC traverses network boundaries. This assumes the MRB in the HPLMN has knowledge of the resource network topology of the VPLMN. + +NOTE 1: Mr interface has been an inter-operator interface since Release 5. + +NOTE 2: For the case that MRB is located in the visited network and is deployed in In-Line Mode, the most efficient configuration to contact the desired MRFC in the visited network is via Mr' interface between MRB and MRFC, instead of traversing back to the home network to route signalling via the S-CSCF over Mr interface to the MRFC. + +# --- 6 Assessment + +The current study has investigated two areas regarding the allocation of resources in the VPLMN for IMS services: + +- VPLMN MRB/MRF discovery, where three different alternatives have been discussed, and +- MRB placement in the HPLMN or VPLMN. + +Assessing the feasibility of the different alternatives for discovery, will imply making an analysis of whether each alternative facilitates the fulfilment of the architectural requirements for each of the IMS services. That is depicted in the chart below. + +In addition, placement of MRB in the HPLMN or VPLMN shall be assessed with regards to the same fulfilment of requirements and is included in the chart as well. + +Other alternatives might also be considered in subsequent stage 2 work. + +**Table 6-1: Assessment** + +| | Avoids routing the IMS media plane via the HPLMN | Minimal impact on the existing IMS architecture and reuses or enhances existing interfaces | Can be invoked selectively by the VPLMN | VPLMN can deny all or a sub-set of the IMS functions to all or a defined sub-set of subscribers | VPLMN can "hide" its detailed internal architecture | +|-----------------------------------------------------------------------------------|------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------| +| a) MRF/MRB selection: MRF/MRB Selection at Registration | Yes, with the restriction placed by RAVEL home routing scenario. | No impact on procedures. No major impacts on resource allocation during traffic, except for securing the Cr/Mr'/Mr interface crossing inter-operator domain | Partially, since selection of MRB/MRF may be only done on a per subscriber basis | Yes. Restriction may be enabled based on e.g. network condition | Yes. It selects appropriate MRB/MRF | +| b) MRF/MRB selection: MRF/MRB Selection at Session initiation | Yes, with the restriction placed by RAVEL home routing scenario. | No impact on procedures. No major impacts on resource allocation during traffic, except for securing the Cr/Mr'/Mr interface crossing inter-operator domain | Yes, since selection of MRB/MRF is done on a per subscriber and service basis (see NOTE) | Yes. Restriction may be enabled based on e.g. network condition | Yes. It selects appropriate MRB/MRF | +| c) Allocation of MRF in VPLMN: AS is configured with VPLMN MRB/MRF address | Yes, with the restriction placed by RAVEL home routing scenario. | No impact on procedures. No major impacts on resource allocation during traffic, except for securing the Cr/Mr'/Mr interface crossing inter-operator domain | No. All subscribers would be allocated the same MRB/MRF and all decisions on service invocation would be taken by HPLMN. | VPLMN can only deny allocation of resources after request from HPLMN | No, the AS in the HPLMN would need to know the complete topology of the VPLMN's resources on a per service basis. | +| d) MRB located in HPLMN | Yes, with the restriction placed by RAVEL home routing scenario. | No impact for the case of MRB playing in Query mode. For existing In-line mode, no impact on procedures or allocation of resources during traffic. In the new alternative for In-line mode, proposed interface between MRB and MRFC will need to be secured. | No. All subscribers would be allocated the same MRB and relevant MRF would be simply selected based on service invocation decision taken by HPLMN. | VPLMN can only deny resources when being queried by HPLMN (provisioning of MRB/MRF address from the VPLMN is not applicable) | No, MRB in HPLMN would need to know the complete topology of the VPLMN's resources on a per service basis. | +| e) MRB located in VPLMN | Yes, with the restriction placed by RAVEL home routing scenario. | For the case of MRB playing in Query mode. No impact on procedures beyond securing the Rc interface. For existing In-line mode, no impact on allocation of resources during traffic but expected major signalling crossing interoperator boundaries (due to S-CSCF in the path between MRB and MRFC). Such signalling would need additional security. In the new alternative for In-line mode, No impact on procedures beyond securing the Rc interface and developing the new Mr' between MRB and MRFC. | Partially if MRB address is signalled during registration.

Yes, if MRB address is signalled during session setup (see NOTE).

No, if MRB address is configured in the HPLMN-AS | Yes. Restriction may be enabled based on e.g. network condition if MRB address signalled from the VPLMN.

If MRB address is configured in the AS, VPLMN can only deny allocation of resources after request from HPLMN | Yes. It selects appropriate MRB/MRF | + +NOTE: The provisioning of MRB/MRF address during session initiation can be done on a per IMS service basis, without anticipating whether tones/announcements or conferencing are to be invoked. For that reason, this requirement is fulfilled as long as the VPLMN can signal the MRB address or list of MRF addresses that can support potential tones/announcements or conferencing services being invoked during mid-call. If the MRF announced at initiation, does not match the criteria for the service being invoked at mid-call, a rediscovery procedure may need to be invoked. + +# 7 Conclusion + +As observed from the different chapters in this document, the functionality missing to be able to allocate resources in the visited network are: + +- MRB/MRF discovery, and +- Direct interface between an MRB and MRFC, when MRB is in In-line mode. + +MRB/MRF discovery must be achieved without the visited network needing to reveal the topology of its resources in its network, i.e. the actual allocation and/or denial of resources is decided by the visited network as per its own subscribers and simply announced to the home network in case there is a need or advantage to execute a breakout for optimal routing. + +The actual decision on break-out is taken by the home network and based also on agreements between home and visited networks. However, the most restrictive condition is imposed by the lack of resources in the VPLMN. Relation exists with the work being developed in RAVEL (TR 23.850 [6]) and conclusion on that is depicted below. + +The alternative described in clause 5.2.5 for MRB-to-MRFC interface, when MRB is placed in In-line mode is being specified in the normative phase in CT WG1, as well as the security requirements implied by such alternatives, for each of the services concluded below. + +For some services, additionally, there is no need to allocate any additional resource in order to execute local breakout, i.e. transcoding at the edge. As opposed to that, any service that might demand allocation of MRF for transcoding in the visited network, requires missing alternatives for MRB/MRF placement in the VPLMN to be depicted. These alternatives are assumed to be studied by CT WG1 but are not considered optimal from allocation of resources and signalling points of view in case of transcoding. + +The following list details the main impacts derived from this study. + +## 1. Transcoding + +No impact at all is foreseen for transcoding at the edge, based on P-CSCF or IBCF/TrGW functionality, and thus those are optimal options from impacts and reusability points of view. This is in addition widely deployed solution on a per inter-operator agreement. + +This study does not recommend allocating MRF/MRB in the VPLMN to control transcoding options, due to complexity in resources allocation and signalling exchange. However, further releases might consider that option as a potential alternative after mode of MRB operation and placement of MRF in VPLMN has concluded all alternatives. + +## 2. Tones/announcements + +Even if announcement/tone insertion are not that commonly used for calls once those have commenced, it would be beneficial to harmonize the way the MRB/MRF is discovered in all cases. The following conclusions are agreed as the basis for normative work: + +- a) MRB/MRF discovery for OSCAR scenarios may be based on information provided from the visited network to the home network at registration or session establishment (as in clauses 5.2.1 and 5.2.2). The home network can, based on local policy, take this information into account when invoking the MRB or MRF. Other mechanisms for discovery might exist, and non-OSCAR use cases might require other discovery mechanisms. It is left to CT WG1 to investigate additional discovery mechanisms, as required. + +While the AS is described in this TR as the home network entity that discovers MRB or MRF, the decision regarding which entity does this is left for CT WG1 to determine. + +NOTE: Use of information provided at registration or session establishment might not provide optimal resource management in deployment scenarios where multiple alternative MRFs are available, since the resource availability may change by the time of resource allocation. + +- b) For MRB placement and mode of operation, both In-line mode and Query mode shall be addressed for MRB located in the VPLMN. This study shall be conducted by CT WG1 as part of interoperator scenarios in the current WID for Media Resource Broker (C1-113712). + +Any additional security requirement for MRB and MRF interfaces shall be addressed in that work. + +Additionally, any impact on the NNI profile due to placement of MRF resources in the VPLMN shall be addressed by CT WG3 working group. + +## 3. Conferencing + +In the conferencing case, routing optimizations are mainly achieved for the cases in which the roaming user is in charge of the control, management and termination of the conferencing. + +- a) MRB/MRF discovery for conferencing scenarios may be based on information provided from the visited network to the home network at registration or session establishment (as in clauses 5.2.1 and 5.2.2). The home network can, based on local policy, take this information into account when invoking the MRB or MRF. Other mechanisms for discovery might exist, and non-OSCAR use cases might require other discovery mechanisms. It is left to CT WG1 to investigate additional discovery mechanisms, as required. + +While the AS is described in this TR as the home network entity that discovers MRB or MRF, the decision regarding which entity does this is left for CT WG1 to determine. + +NOTE: Use of information provided at registration or session establishment might not provide optimal resource management in deployment scenarios where multiple alternative MRFs are available, since the resource availability may change by the time of resource allocation. + +- b) For Conferencing service, both In-line mode and Query mode shall be addressed for MRB located in the VPLMN. This study shall be conducted by CT WG1 as part of interoperator scenarios in the current WID for Media Resource Broker (C1-113712). + +Any additional security requirement for MRB and MRF interfaces shall be addressed in that work. + +Additionally, any impact on the NNI profile due to placement of MRF resources in the VPLMN shall be addressed by CT WG3 working group. + +According to clause 5.1.3, the AS may decide to select an MRF for conferencing in a different network that the visited or the home. This decision may be based on policies or on determining the location of the users involved in the conferencing session. However, such scenario is not in the scope of OSCAR improvements and thus shall be addressed separately, and if CT WG1 determines so, from OSCAR work. + +## 4. RAVEL dependencies + +The home network is in general the appropriate network since the media and signalling both flow to the home. However there may be some scenarios where the resources can be allocated in the visited or other network. This is subject to local policies. + +The usage of OSCAR optimizes the resource allocation in the VPLMN for the services studied in this report and RAVEL loopback scenarios may benefit from this optimization. + +# --- Annex A: Change history + +| Change history | | | | | | | | +|----------------|-------|-----------|----|-----|--------------------------------------------------------------------------------------------|-------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2011-12 | SP-54 | SP-110756 | - | - | MCC Update to version 1.0.1 to correct for presentation to TSG SA for information . | 1.0.0 | 1.0.1 | +| 2012-02 | SP-55 | SP-120094 | - | - | MCC Update to version 2.0.0 for presentation to TSG SA for Approval . | 1.1.0 | 2.0.0 | +| 2012-03 | SP-55 | - | - | - | MCC Update to version 11.0.0 after TSG SA Approval (Release 11) | 2.0.0 | 11.0.0 | \ No newline at end of file diff --git a/marked/Rel-11/23_series/23885/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-11/23_series/23885/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e71815fa2940b3ed649867d099531b218ec804b --- /dev/null +++ b/marked/Rel-11/23_series/23885/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0dab25b3d7bd98e50e22881462062ec8bd59eb4e68db9b4da8fbded831c812b3 +size 33673 diff --git a/marked/Rel-11/23_series/23885/04f7b8f64493f6d83188232f10f86fe2_img.jpg b/marked/Rel-11/23_series/23885/04f7b8f64493f6d83188232f10f86fe2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72d12fd83adbe809667258de3ec88bd50c84aa46 --- /dev/null +++ b/marked/Rel-11/23_series/23885/04f7b8f64493f6d83188232f10f86fe2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64125257dbcfb2157e76788b3b69f776df245812cb1564cf22e6e0fba8e8bf3e +size 105626 diff --git a/marked/Rel-11/23_series/23885/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-11/23_series/23885/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d34dbc68bd55ec3d370d59729460e5fed8ffacb --- /dev/null +++ b/marked/Rel-11/23_series/23885/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32fd0e7232e3c55095b7cba183098b60b1d52452f5ebfef8770127ab72f93021 +size 188589 diff --git a/marked/Rel-11/23_series/23885/1316d63eca7b84e13c27f55f0027b7b5_img.jpg b/marked/Rel-11/23_series/23885/1316d63eca7b84e13c27f55f0027b7b5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77cd6cc7534ac518e2d113c9bdc0fa1b47638e8a --- /dev/null +++ b/marked/Rel-11/23_series/23885/1316d63eca7b84e13c27f55f0027b7b5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b6f65117649d6447cb56eb20a302600cd99f01bd55558eccc36cade3213c8f6 +size 37977 diff --git a/marked/Rel-11/23_series/23885/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-11/23_series/23885/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed2a5704858f40ddcf47245bcabbf523e21e9608 --- /dev/null +++ b/marked/Rel-11/23_series/23885/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16d52549f96dc203db6736c6d4b5113451462e2f0dbb3563b03bb57e3d4487f1 +size 60119 diff --git a/marked/Rel-11/23_series/23885/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg b/marked/Rel-11/23_series/23885/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29f7f723e00a0bd551319921dcefbb2e78db7496 --- /dev/null +++ b/marked/Rel-11/23_series/23885/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8158be15e7164ef6adda1e29b1c1ebddb62bfc391799fa7c9e5bb0c3a050d955 +size 46023 diff --git a/marked/Rel-11/23_series/23885/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg b/marked/Rel-11/23_series/23885/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61d48ec0615e2ff89655698c16e8494c5283a5f1 --- /dev/null +++ b/marked/Rel-11/23_series/23885/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df215ce4a3235b0fda960a2b402d83563f7cdac37547b3c1ca62af36c9c74835 +size 84016 diff --git a/marked/Rel-11/23_series/23885/256e8716b024671206b023fab056678e_img.jpg b/marked/Rel-11/23_series/23885/256e8716b024671206b023fab056678e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89edeaa02904b16de2fef66975915b59596047a6 --- /dev/null +++ b/marked/Rel-11/23_series/23885/256e8716b024671206b023fab056678e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7ffff174fc6cedc20dee25a1417d8f736140fa3ab2cb73b229f630fe889d6ec +size 96905 diff --git a/marked/Rel-11/23_series/23885/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-11/23_series/23885/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c51750a48b9f7e18c87a61caec26d59e73a03a69 --- /dev/null +++ b/marked/Rel-11/23_series/23885/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bc7c44507a021d1631e419263cbe667b7186814d3f657ade5bced1a2b0ad31c +size 47075 diff --git a/marked/Rel-11/23_series/23885/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-11/23_series/23885/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a3be65e9a529dc0a31bf0ed84d791c4d705368f --- /dev/null +++ b/marked/Rel-11/23_series/23885/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e30db9447e59961e5215e2e86271b61900cd4ae8e4d7af20863b8f2ac5c028cf +size 106411 diff --git a/marked/Rel-11/23_series/23885/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-11/23_series/23885/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b7deae9589b07596b8549440d9587e9db82863e --- /dev/null +++ b/marked/Rel-11/23_series/23885/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:489183a539c6700c26f8c09a33b810bae581eccd02359f48ffb1251614f32f5d +size 76097 diff --git a/marked/Rel-11/23_series/23885/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-11/23_series/23885/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d98496d971c0d04496917d7ed8feec19560808a --- /dev/null +++ b/marked/Rel-11/23_series/23885/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5252569abd29b601be1625c21a6a709327290a8452a6b6955c39d8f36d40be65 +size 150233 diff --git a/marked/Rel-11/23_series/23885/382a9c9e4816bd229191ab4591424dd8_img.jpg b/marked/Rel-11/23_series/23885/382a9c9e4816bd229191ab4591424dd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc4b7648d580076633dba77fee20b07149dfbf74 --- /dev/null +++ b/marked/Rel-11/23_series/23885/382a9c9e4816bd229191ab4591424dd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:533fea50a0427ba77f3314d006a696af63cb7306faad1d7be672ecc296cba935 +size 79336 diff --git a/marked/Rel-11/23_series/23885/3e20f0289a1945c7c3894f51383d8e37_img.jpg b/marked/Rel-11/23_series/23885/3e20f0289a1945c7c3894f51383d8e37_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf0d9cddf849cae3fb292f7f8030eeeba4278867 --- /dev/null +++ b/marked/Rel-11/23_series/23885/3e20f0289a1945c7c3894f51383d8e37_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ade9a33bf7cc13487ebf1611f7e7dde7dd68f77f46911832c3323028a711779e +size 67011 diff --git a/marked/Rel-11/23_series/23885/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-11/23_series/23885/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1e5a8a0a8d617cd65b0a3e84282dee461e51aae --- /dev/null +++ b/marked/Rel-11/23_series/23885/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:defc06e9b23a75b9a9903446ce13ca53bc5c6c0ff79ed5778d75c5dd16f0631b +size 17012 diff --git a/marked/Rel-11/23_series/23885/4260aa4a7ece77c411597094c9d197bd_img.jpg b/marked/Rel-11/23_series/23885/4260aa4a7ece77c411597094c9d197bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cce259b26da98724534e1028e67d2bbf9ec114c --- /dev/null +++ b/marked/Rel-11/23_series/23885/4260aa4a7ece77c411597094c9d197bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:947c0862a392f9e525648b8340152ab4d4f281208e4fe2b424e1d91fa80c137c +size 131694 diff --git a/marked/Rel-11/23_series/23885/43979979715bb3304389a0cb18f34444_img.jpg b/marked/Rel-11/23_series/23885/43979979715bb3304389a0cb18f34444_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65963d0610b122f0cfd1a36be04e866982accce8 --- /dev/null +++ b/marked/Rel-11/23_series/23885/43979979715bb3304389a0cb18f34444_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84919086499453e0653433089844ec9ef7d74212a4b4db0ec9b6be07fcaca0c6 +size 100195 diff --git a/marked/Rel-11/23_series/23885/4b87467ad9642943235f48f7d4b59449_img.jpg b/marked/Rel-11/23_series/23885/4b87467ad9642943235f48f7d4b59449_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2122c40626cb33b98843db5568afd01c20ac8adf --- /dev/null +++ b/marked/Rel-11/23_series/23885/4b87467ad9642943235f48f7d4b59449_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea6ee1d2e4cef221a2e1d98ee0b65de9d9cb1020b1d7bdb77a05008ae0b08ec2 +size 116012 diff --git a/marked/Rel-11/23_series/23885/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg b/marked/Rel-11/23_series/23885/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..434e9a1bb1963bc880aa5c7a6d2fe664c5ca25b3 --- /dev/null +++ b/marked/Rel-11/23_series/23885/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af80d7c3554c6a27b52dcc72f972a628f8c1d328599458be6cae74642720a8b1 +size 60928 diff --git a/marked/Rel-11/23_series/23885/6031b46d356ee24f96bfe37ee2cb7616_img.jpg b/marked/Rel-11/23_series/23885/6031b46d356ee24f96bfe37ee2cb7616_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c4bb00e85a610cc61b8d3d5045df42d591a3b5f --- /dev/null +++ b/marked/Rel-11/23_series/23885/6031b46d356ee24f96bfe37ee2cb7616_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb56c7528d69ee417a892c4a820fc7d04fcc7dfa40eb16c7570181651141cb53 +size 62757 diff --git a/marked/Rel-11/23_series/23885/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-11/23_series/23885/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15c4fa0ad753a8e9720dfc51fbb5f0995a51019b --- /dev/null +++ b/marked/Rel-11/23_series/23885/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0709a423a40c265a6cc6c043aef8d4c6b5a5ed24144282fba64545330ba862a0 +size 78184 diff --git a/marked/Rel-11/23_series/23885/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-11/23_series/23885/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f92797a955aa5f4c055ed8b8e092a5163d0a9eac --- /dev/null +++ b/marked/Rel-11/23_series/23885/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65681a685a6896f9384c640639e2fae53449dc2c18c31b5b07f32b3e173a9a9b +size 59954 diff --git a/marked/Rel-11/23_series/23885/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-11/23_series/23885/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c85912c5e9a1423869cebb2e25d1e139667e8b1 --- /dev/null +++ b/marked/Rel-11/23_series/23885/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a0645b9428d27ead31eec2ca995f7c3166b4ce414df3c082cc8a5e0baacf688 +size 148595 diff --git a/marked/Rel-11/23_series/23885/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-11/23_series/23885/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f62f2121591517bce467cb038fa5b39ef998644 --- /dev/null +++ b/marked/Rel-11/23_series/23885/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9dd91819d86cfa35fccebd7ed07f30c7a4056df2c4f002f8f8146bc87de7183b +size 85285 diff --git a/marked/Rel-11/23_series/23885/8658cfab6a458b4a80ab2e384c61ff89_img.jpg b/marked/Rel-11/23_series/23885/8658cfab6a458b4a80ab2e384c61ff89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5603d73e0b1eacc97c61dc551987a1c8a3cb6303 --- /dev/null +++ b/marked/Rel-11/23_series/23885/8658cfab6a458b4a80ab2e384c61ff89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:346c47d936465f633c50fcfcf0a3b9ffb4da008aadb39782d5ecf508b4dcf334 +size 73102 diff --git a/marked/Rel-11/23_series/23885/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/Rel-11/23_series/23885/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12e5d96668d079c84176c07b23d35ed0082c17bd --- /dev/null +++ b/marked/Rel-11/23_series/23885/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f26d2bac5f5a3ac2cbed35fb359e519180e7f09b1528e0f34b7c57997785399c +size 119147 diff --git a/marked/Rel-11/23_series/23885/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-11/23_series/23885/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f99efe172b5fa427be6ed8f651eb6020cb6f7211 --- /dev/null +++ b/marked/Rel-11/23_series/23885/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf88ba555f0e6be61dfd2ff44cd871daa2d879a0fc1b89db95d4ad9217ca0fe0 +size 56123 diff --git a/marked/Rel-11/23_series/23885/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-11/23_series/23885/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2425fdfb2335d9fa9d5c6fe5a106d6bb5cf05920 --- /dev/null +++ b/marked/Rel-11/23_series/23885/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c994f793dcd3aeff146e3606957b217a795eea91c2bb7bcd3dce5c2e0b783ef +size 44809 diff --git a/marked/Rel-11/23_series/23885/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg b/marked/Rel-11/23_series/23885/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8033bfa623a316f86787d19ecbb763420e1bcdba --- /dev/null +++ b/marked/Rel-11/23_series/23885/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19d2f2e29bf281c6c476a023cfe34eebd2b57e0745f5c28b755682261d41750c +size 48964 diff --git a/marked/Rel-11/23_series/23885/9cd90f495b95ad2116ff780248c26d95_img.jpg b/marked/Rel-11/23_series/23885/9cd90f495b95ad2116ff780248c26d95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..520aa4bf37fcc51976e03bdd3e761d98ad804ed8 --- /dev/null +++ b/marked/Rel-11/23_series/23885/9cd90f495b95ad2116ff780248c26d95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee28aaee02e6e353c5a81706135c7895e5332201346df4b6bbff5acfc5d99e0f +size 83898 diff --git a/marked/Rel-11/23_series/23885/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/Rel-11/23_series/23885/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6d7e9665a979f8916c1eaed3f0c91700534705f --- /dev/null +++ b/marked/Rel-11/23_series/23885/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eed21bb28b95705ce7b6a6498a366d64a3aed323b84e62460cbb8ea5c70bb406 +size 119375 diff --git a/marked/Rel-11/23_series/23885/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/marked/Rel-11/23_series/23885/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..acd6d13745d835f58d8fb363ef7f3c7356789582 --- /dev/null +++ b/marked/Rel-11/23_series/23885/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ecc176765ed16668173713a9ccd8cf770b8df929a754cf156a524cf9321c238a +size 73791 diff --git a/marked/Rel-11/23_series/23885/ae375ead8aa673286b534e079e9a8533_img.jpg b/marked/Rel-11/23_series/23885/ae375ead8aa673286b534e079e9a8533_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb03f21c49dcb89fedd58fe3355dbf6f0046d448 --- /dev/null +++ b/marked/Rel-11/23_series/23885/ae375ead8aa673286b534e079e9a8533_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52270f8fa18f5760faeb8313dae41b8b4f6349f639e2a69d076a7bddf2411737 +size 39229 diff --git a/marked/Rel-11/23_series/23885/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-11/23_series/23885/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30d90d3703637f05c25ec46e518e4efae446c55c --- /dev/null +++ b/marked/Rel-11/23_series/23885/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e2d52fe33286d619e508919f67eddd0814897272c49c893d61e32022931caff +size 79037 diff --git a/marked/Rel-11/23_series/23885/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-11/23_series/23885/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c924240001d3b85c540a07bb04556ac6e3cac304 --- /dev/null +++ b/marked/Rel-11/23_series/23885/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14cb1e2d8ab80263fd6626f55b520325c8f25165a6bd4c306b466ff117f51d4e +size 58574 diff --git a/marked/Rel-11/23_series/23885/b63f41ca262d8ce9ef8affb62607f32b_img.jpg b/marked/Rel-11/23_series/23885/b63f41ca262d8ce9ef8affb62607f32b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7fda65736af8840809c65366c16644fb4ba7275 --- /dev/null +++ b/marked/Rel-11/23_series/23885/b63f41ca262d8ce9ef8affb62607f32b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17a3ed5fb73d4038f13639bd09331940752aa13ce8ea77d9918a161796ded0e8 +size 93326 diff --git a/marked/Rel-11/23_series/23885/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg b/marked/Rel-11/23_series/23885/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..779400fb76c89d9ac353a9922988b445dd163293 --- /dev/null +++ b/marked/Rel-11/23_series/23885/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee2e286ec23be24533a8fb6583fb72e3ff1fe3e8382bbc7d72b868668285dd87 +size 106049 diff --git a/marked/Rel-11/23_series/23885/c1278da91cbcabe32628e589ebc47418_img.jpg b/marked/Rel-11/23_series/23885/c1278da91cbcabe32628e589ebc47418_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6da972155e5a28b96b81fa10dfbad5a1e4c4ba9 --- /dev/null +++ b/marked/Rel-11/23_series/23885/c1278da91cbcabe32628e589ebc47418_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5932a409a4111c3e7d02159af2c556a3d62731e42fb01ef28d61d37fbcbec27e +size 92763 diff --git a/marked/Rel-11/23_series/23885/c5a20f7bae219fc4c31f7376b7eb11e1_img.jpg b/marked/Rel-11/23_series/23885/c5a20f7bae219fc4c31f7376b7eb11e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..783afb28a9a40855a94810ae23516ac780921e4f --- /dev/null +++ b/marked/Rel-11/23_series/23885/c5a20f7bae219fc4c31f7376b7eb11e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b0bb9646511e95c0eacde45a607b52907f8730f373201a6c48787b134e2138c +size 89581 diff --git a/marked/Rel-11/23_series/23885/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg b/marked/Rel-11/23_series/23885/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52b60a39069c3d51722a0c9492280795e471929f --- /dev/null +++ b/marked/Rel-11/23_series/23885/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdb18e759d75956119857048fbc3334076c8b186cc31efde24d4101e9f114e40 +size 39753 diff --git a/marked/Rel-11/23_series/23885/cc542843836eecb036b99cb270b54a1e_img.jpg b/marked/Rel-11/23_series/23885/cc542843836eecb036b99cb270b54a1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d5755b471b130089c9d07744ecda09982736fbc --- /dev/null +++ b/marked/Rel-11/23_series/23885/cc542843836eecb036b99cb270b54a1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6dd1ddc7b67c81509a21d72b122fd3b064e0d7775bc46f2db8c76c1ae6d1f731 +size 84286 diff --git a/marked/Rel-11/23_series/23885/dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg b/marked/Rel-11/23_series/23885/dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1d9b8d5f7f6c2083cc8015e1d83fd8549c26525 --- /dev/null +++ b/marked/Rel-11/23_series/23885/dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe13c2f3fdc049c35f70f7fcd80824502ef08e5ddbdceaa4e10790d637c7d6c0 +size 45059 diff --git a/marked/Rel-11/23_series/23885/dfaa8b98082261913dac00eae86b2889_img.jpg b/marked/Rel-11/23_series/23885/dfaa8b98082261913dac00eae86b2889_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6355dc6c125129b778bbccfc87c04a88cfb45199 --- /dev/null +++ b/marked/Rel-11/23_series/23885/dfaa8b98082261913dac00eae86b2889_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3ce7437a3c761b4a8e159a4eff7cdbbf6ce084d5a6b89ef4f2921aac943165a +size 77573 diff --git a/marked/Rel-11/23_series/23885/f97535cdaa4fe017f4659512f4f78028_img.jpg b/marked/Rel-11/23_series/23885/f97535cdaa4fe017f4659512f4f78028_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c60f13e78e3c3d298be4fa1be78049f2509f0a9a --- /dev/null +++ b/marked/Rel-11/23_series/23885/f97535cdaa4fe017f4659512f4f78028_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d3814fa6e02d7ff9fa6eca7d6e7d13d48e5c2afdb350dd00b00f7dece7c4e4c +size 113762 diff --git a/marked/Rel-11/23_series/23885/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Rel-11/23_series/23885/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26abeb7622a735b7144e31ab3258ecc0659e8792 --- /dev/null +++ b/marked/Rel-11/23_series/23885/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9cb35a2fc6c5ce43fe8f1754867646acaae10d2cd315d23dde44a707b7470527 +size 69660 diff --git a/marked/Rel-11/23_series/23885/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg b/marked/Rel-11/23_series/23885/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f7e56c93e43ad406c5ce021487bbe628889bfb8 --- /dev/null +++ b/marked/Rel-11/23_series/23885/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:305b63c518a7e9b142c9a67aa042eec12473bc9b89fdceca7e5b03537e2532a1 +size 75114 diff --git a/marked/Rel-11/23_series/23885/raw.md b/marked/Rel-11/23_series/23885/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..dd27efc80fb605fbacba8ac6075cb8dbaea16cf3 --- /dev/null +++ b/marked/Rel-11/23_series/23885/raw.md @@ -0,0 +1,2979 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 8 | +| 4 Requirements and Assumptions..... | 8 | +| 4.1 Assumptions..... | 8 | +| 4.2 Architectural requirements..... | 8 | +| 4.3 Performance requirements..... | 9 | +| 4.4 Reverse SRVCC deployment scenarios..... | 10 | +| 5 Architecture model and reference points ..... | 10 | +| 5.1 General ..... | 10 | +| 5.2 Reference architecture..... | 11 | +| 5.2.1 3GPP UTRAN/GERAN and E-UTRAN SRVCC architecture..... | 11 | +| 5.2.2 3GPP UTRAN/GERAN and UTRAN (HSPA) SRVCC architecture..... | 11 | +| 5.3 Functional Entities..... | 12 | +| 5.3.1 MSC Server enhanced for SRVCC ..... | 12 | +| 5.4 Reference points..... | 12 | +| 6 Solutions..... | 12 | +| 6.1 Solution 1: Session transfer initiated on E-UTRAN/HSPA..... | 12 | +| 6.1.1 Functional Description ..... | 12 | +| 6.1.2 Information flows ..... | 13 | +| 6.1.2.1 GERAN/UTRAN Attach procedure ..... | 13 | +| 6.1.2.2 E-UTRAN attach procedure ..... | 13 | +| 6.1.2.3 Call establishment procedure in GERAN/UTRAN..... | 13 | +| 6.1.2.4 SRVCC from E-UTRAN/HSPA to GERAN/UTRAN..... | 14 | +| 6.1.2.5 Handover procedure in GERAN/UTRAN..... | 14 | +| 6.1.2.6 Call flows for SRVCC from UTRAN/GERAN to E-UTRAN..... | 14 | +| 6.1.2.6.1 SRVCC handover from GERAN without DTM support to E-UTRAN..... | 14 | +| 6.1.2.6.2 SRVCC handover from UTRAN or GERAN with PS handover support to E-UTRAN ..... | 16 | +| 6.1.2.7 Call flows for SRVCC from UTRAN/GERAN to HSPA ..... | 18 | +| 6.1.2.7.1 SRVCC handover from GERAN without DTM support to HSPA ..... | 18 | +| 6.1.2.7.2 SRVCC handover from UTRAN or GERAN with PS handover support to HSPA ..... | 19 | +| 6.2 Solution 2: Session transfer initiated on E-UTRAN/HSPA..... | 20 | +| 6.2.0 General ..... | 20 | +| 6.2.1 Functional Description ..... | 21 | +| 6.2.2 Information flows ..... | 21 | +| 6.2.2.1 GERAN/UTRAN Attach procedure ..... | 21 | +| 6.2.2.2 E-UTRAN attach procedure ..... | 21 | +| 6.2.2.3 Call establishment procedure in GERAN/UTRAN..... | 21 | +| 6.2.2.4 SRVCC from E-UTRAN/HSPA to GERAN/UTRAN..... | 22 | +| 6.2.2.5 Handover procedure in GERAN/UTRAN..... | 22 | +| 6.2.2.6 Call flows for SRVCC from UTRAN/GERAN to E-UTRAN..... | 23 | +| 6.2.2.6.1 SRVCC handover from GERAN without DTM support to E-UTRAN..... | 23 | +| 6.2.2.6.2 SRVCC handover from UTRAN or GERAN with PS handover support to E-UTRAN ..... | 24 | +| 6.3 Solution 3+5: Media anchoring in serving network with Access Transfer Control Functionality ..... | 25 | +| 6.3.1 Architecture Reference Model..... | 25 | +| 6.3.2 Functional Entities ..... | 26 | +| 6.3.2.1 ATCF ..... | 26 | +| 6.3.2.2 SCC AS..... | 27 | +| 6.3.2.3 P-CSCF ..... | 27 | +| 6.3.2.4 MSC Server enhanced for reverse SRVCC ..... | 27 | +| 6.3.2.5 SGSN enhanced for rSRVCC ..... | 27 | +| 6.3.2.6 UE enhanced for rSRVCC..... | 27 | + +| | | | +|-----------|-------------------------------------------------------------------------------|----| +| 6.3.2.7 | HSS ..... | 28 | +| 6.3.2.8 | MME/SGSN enhanced for rSRVCC ..... | 28 | +| 6.3.3 | Message Flows ..... | 28 | +| 6.3.3.1 | General principles ..... | 28 | +| 6.3.3.2 | GERAN/UTRAN Attach procedure ..... | 29 | +| 6.3.3.3 | E-UTRAN attach procedure ..... | 29 | +| 6.3.3.3a | Informing the source RAN about the possibility to perform rSRVCC..... | 29 | +| 6.3.3.4 | Codec and transport address related procedure ..... | 30 | +| 6.3.3.4.1 | General ..... | 30 | +| 6.3.3.4.2 | Information in IMS registration and handover procedure..... | 30 | +| 6.3.3.5 | Establish a session over CS ..... | 30 | +| 6.3.3.5.1 | STN-SR allocated by the ATCF and Transfer Info sent to ATCF ..... | 30 | +| 6.3.3.5.2 | Registration when ATCF involved ..... | 31 | +| 6.3.3.5.3 | Origination procedures when ATCF involved..... | 31 | +| 6.3.3.5.4 | Termination procedures when ATCF involved..... | 32 | +| 6.3.3.6 | CS – PS Access Transfer Overview ..... | 33 | +| 6.3.3.6.1 | Anchored in ATGW ..... | 33 | +| 6.3.3.6.2 | Not Anchored in ATGW ..... | 34 | +| 6.3.3.7 | Access Transfer Preparation ..... | 34 | +| 6.3.3.7.1 | Access Transfer Preparation Alternative 1 ..... | 34 | +| 6.3.3.7.2 | Access Transfer Preparation Alternative 2 ..... | 36 | +| 6.3.3.7.3 | Access Transfer Preparation Alternative 3 ..... | 38 | +| 6.3.3.7.4 | Access Transfer Preparation Alternative 4 ..... | 40 | +| 6.3.3.7.5 | Access Transfer Preparation Alternative 5 (the combination) ..... | 43 | +| 6.3.3.8 | IMS Session Continuity procedure ..... | 45 | +| 6.3.3.8.0 | General ..... | 45 | +| 6.3.3.8.1 | Anchored in ATGW ..... | 46 | +| 6.3.3.8.2 | Not Anchored in ATGW ..... | 47 | +| 6.3.3.9 | Identification of serving PS node..... | 48 | +| 6.3.3.9.1 | Alternative 1: CN nodes based..... | 48 | +| 6.3.3.9.2 | Alternative 2: UE and/or RAN provided information..... | 48 | +| 6.3.3.9.3 | Alternative 3: RAN provided information ..... | 49 | +| 6.3.4 | IMS registration Considerations ..... | 50 | +| 6.3.4.1 | General ..... | 50 | +| 6.3.4.2 | ATCF controlled registration..... | 50 | +| 6.3.4.3 | SCC AS controlled registration ..... | 51 | +| 6.3.4.4 | rSRVCC HO Cancellation in case of UE loss of IMS registration ..... | 52 | +| 6.4 | Solution 4: Session transfer by local anchoring with Indirect Forwarding..... | 53 | +| 6.4.1 | Functional Description ..... | 53 | +| 6.4.2 | Architecture Reference Model..... | 54 | +| 6.4.2 | Information flows ..... | 54 | +| 6.4.2.1 | Initial ATTACH / TA update procedure..... | 54 | +| 6.4.2.2 | Call origination procedure in GERAN/UTRAN ..... | 54 | +| 6.4.2.3 | Call termination procedure in GERAN/UTRAN..... | 56 | +| 6.4.2.4 | SRVCC handover from UTRAN or GERAN to LTE ..... | 57 | +| 6.5 | Solution 5: IMS procedure is initiated by MSC Server to ATCF ..... | 59 | +| 6.5.1 | Architecture Reference Model..... | 59 | +| 6.5.1.1 | General ..... | 59 | +| 6.5.1.2 | Concepts of reverse SRVCC..... | 60 | +| 6.5.2 | Functional Entities ..... | 61 | +| 6.5.2.1 | ATCF ..... | 61 | +| 6.5.2.2 | SCC AS..... | 61 | +| 6.5.2.3 | S-CSCF ..... | 62 | +| 6.5.2.4 | MSC Server enhanced for reverse SRVCC ..... | 62 | +| 6.5.2.5 | MME..... | 62 | +| 6.5.2.6 | UE enhanced for reverse SRVCC..... | 62 | +| 6.5.2.7 | UTRAN/GERAN..... | 62 | +| 6.5.3 | Message Flows ..... | 63 | +| 6.5.3.1 | Home control rSRVCC..... | 63 | +| 6.5.3.2 | RAU/LAU/TAU procedure ..... | 63 | +| 6.5.3.3 | GERAN/UTRAN performs handover procedure ..... | 63 | +| 6.5.3.4 | Maintaining IMS Registration ..... | 63 | + +| | | | +|-----------------|----------------------------------------------------------------------------------------------------------------------|-----------| +| 6.5.3.5 | Preparation of media transfer..... | 63 | +| 6.5.3.6 | Selection of the ATCF ..... | 64 | +| 6.5.3.7 | Originating sessions in CS..... | 65 | +| 6.5.3.7.1 | Serving MSC Server is not enhanced for ICS..... | 65 | +| 6.5.3.7.2 | Serving MSC Server is enhanced for ICS..... | 66 | +| 6.5.3.7.3 | Serving MSC Server is enhanced for rSRVCC..... | 66 | +| 6.5.3.7.4 | UE is enhanced for ICS..... | 67 | +| 6.5.3.8 | Terminating sessions in CS..... | 68 | +| 6.5.3.8.1 | UE is not enhanced for ICS..... | 68 | +| 6.5.3.8.2 | UE is enhanced for ICS..... | 69 | +| 6.5.3.9 | CS - PS Access Transfer..... | 70 | +| 6.5.3.9.0 | Introduction ..... | 70 | +| 6.5.3.9.1 | IMS Session Continuity procedure ..... | 70 | +| 6.5.3.9.2 | CS to PS handover procedure..... | 71 | +| 6.5.3.9 | Failure to complete CS-PS Access Transfer..... | 72 | +| 7 | Assessment of the solutions ..... | 73 | +| 7.1 | Assessment Criteria..... | 73 | +| 7.2 | Assessment of the solution 3+5 access transfer preparation alternatives..... | 74 | +| 8 | Conclusion ..... | 77 | +| 8.1 | General ..... | 77 | +| 8.2 | Access Transfer preparation / How to reserve bearer for VoIP ..... | 77 | +| 8.3 | Source SGSN selection by MSC Server ..... | 77 | +| 8.4 | Maintaining IMS registration over PS access during the CS session ..... | 77 | +| 8.5 | Summary ..... | 77 | +| Annex A: | Mechanisms to re-enable E-UTRAN capability ..... | 78 | +| A.1 | Functional description..... | 78 | +| A.2 | Information flows..... | 79 | +| A.2.1 | Proposed signalling flow for Alternative A to re-enable E-UTRAN capabilities using broadcast indicator..... | 79 | +| A.2.2 | Proposed signalling flow for Alternative B to re-enable E-UTRAN capabilities using NAS indicator..... | 80 | +| A.2.3 | Proposed signalling flow for Alternative C to re-enable E-UTRAN capabilities using change in RFSP/RAC of the UE..... | 81 | +| Annex B: | Mechanisms for GERAN/UTRAN sending Handover/Relocation Required message ..... | 82 | +| Annex C: | Change history..... | 83 | + +# --- 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 the feasibility study is to investigate a solution for supporting Single Radio Voice Call Continuity (SRVCC) from 3GPP UTRAN/GERAN CS access to 3GPP E-UTRAN/HSPA access, for voice call initiated in LTE/HSPA access and previously handed over to UTRAN/GERAN CS access, as well as for the voice call directly initiated in UTRAN/GERAN CS access. + +This Technical Report investigates solutions for SRVCC for voice calls that are anchored in the IMS. + +Coordination between the SRVCC for voice call and the handover of non-voice PS bearers is also covered. + +# --- 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.278: "Service requirements for the Evolved Packet System (EPS)". +- [3] 3GPP TS 23.292: "IP Multimedia System (IMS) centralized services; Stage 2". +- [4] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2". +- [5] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [6] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [7] 3GPP TS 23.216: " Single Radio Voice Call Continuity (SRVCC): Stage 2". +- [8] 3GPP TR 23.856: "Feasibility study of SR-VCC enhancements". +- [9] 3GPP TS 23.221: "Architectural requirements (Release 9)". +- [10] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". +- [11] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [12] 3GPP TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling". +- [13] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol". +- [14] 3GPP TS 29.280: "Evolved Packet System (EPS); 3GPP Sv interface (MME to MSC, and SGSN to MSC) for SRVCC". + +# --- 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]. + +**Reverse Single Radio Voice Call Continuity:** Voice call continuity from UTRAN/GERAN access to IMS over E-UTRAN/HSPA access for calls that are anchored in IMS when the UE is capable of transmitting/receiving on only one of those access networks at a given time. This is also referred to as Single Radio Voice Call Continuity from E-UTRAN/HSPA to UTRAN/GERAN in this technical report. + +**Single Radio Voice Call Continuity:** Voice call continuity from IMS over E-UTRAN/HSPA access to UTRAN/GERAN access for calls that are anchored in IMS when the UE is capable of transmitting/receiving on only one of those access networks at a given time. This is also referred to as Single Radio Voice Call Continuity from UTRAN/GERAN to E-UTRAN/HSPA in this technical report. + +**Service Continuity:** see TS 22.278 [2]. + +## 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]. + +| | | +|--------|--------------------------------------------| +| rSRVCC | Reverse Single Radio Voice Call Continuity | +| SRVCC | Single Radio Voice Call Continuity | + +# --- 4 Requirements and Assumptions + +## 4.1 Assumptions + +For SRVCC from 3GPP UTRAN/GERAN CS access to 3GPP E-UTRAN/HSPA access shall re-use existing functions defined for SRVCC from E-UTRAN/HSPA to UTRAN/GERAN in TS 23.216 [7] as much as possible. The solution shall minimize impacts to Rel-8 SRVCC mechanisms. The results of the study on performance enhancements in TR 23.856 [8] shall be taken into account in this study. The following scenarios shall be studied: + +- SRVCC from GERAN without DTM support to E-UTRAN. +- SRVCC from UTRAN/GERAN with PS HO support to E-UTRAN. +- SRVCC from GERAN without DTM support to UTRAN (HSPA). +- SRVCC from UTRAN/GERAN with PS HO support to UTRAN (HSPA). + +It is assumed that the support of IMS voice over PS Session is homogeneous in the E-UTRAN network. + +## 4.2 Architectural requirements + +- The rSRVCC solution shall not require UE with multiple RATs capability to simultaneously signal on two different RATs. +- Impact on user service quality experience, e.g. QoS, call drop, interruption time, should be minimized. +- Overall duration of the 3GPP UTRAN/GERAN CS access to 3GPP E-UTRAN/HSPA access handover procedure shall be minimized. +- RAT/domain selection change shall be network initiated and under network control. + +- In case where the UE has disabled its E-UTRAN capability due to mismatch with the voice capabilities of the network, it shall be able for the UE to re-enable its E-UTRAN capability. +- It shall be possible to restrict RAT/domain selection change to specific access systems and specific subscribers, depending on operator policies (for example restrict handover of voice calls from UTRAN/GERAN CS access to PS domain) and capabilities of the network and the UE, and these shall be network initiated and under network control . +- In roaming cases, the VPLMN shall be able to control the RAT/domain selection change while taking into account any related HPLMN policies. In particular, the HPLMN shall be able to restrict handover to PS domain for a given VPLMN. +- E-UTRAN shall not be required to convert any CS specific RAB information for rSRVCC operation. +- Handovers from UTRAN/GERAN CS access to E-UTRAN/HSPA for voice call initiated in LTE and previously handed over to UTRAN/GERAN CS access as well as for voice calls directly initiated in UTRAN/GERAN CS access shall be supported, provided that the calls have been anchored in IMS at the time of their establishment (for example in the case of voice calls directly initiated in UTRAN/GERAN CS access the MSC Server has been enhanced for ICS). +- The signalling to the HPLMN for inter-domain handover in the VPLMN should be minimized. +- Impacts to Rel-10 SRVCC mechanisms shall be minimized. +- For calls that have been handed over from PS via SRVCC, provided that the UE and the network support rSRVCC procedures, rSRVCC should be possible no matter which SRVCC Release 10 procedure applied: + - ATCF with media anchored in the ATGW + - ATCF without media anchored in the ATGW + - ATCF not included at registration or no ATCF (i.e. SRVCC Release 9 architecture) + +NOTE 1: In some of the aforementioned scenarios, the performance requirements might not always be possible to fulfill. + +- In case of active PS bearer(s) on UTRAN/GERAN, PS bearer handover to E-UTRAN/HSPA shall be handled as specified in TS 23.401 [5] in conjunction with SRVCC to E-UTRAN/HSPA as specified in TS 23.216 [7]. The rSRVCC solution shall not impact the PS bearer handover. +- The solution shall be applicable to networks where UTRAN/GERAN PS domain cannot provide IMS voice service. +- After transfer from UTRAN/GERAN CS domain to E-UTRAN/HSPA PS-domain, it shall support moving the session back to UTRAN/GERAN CS domain.. +- The solution shall support the MSC to initiate reverse SRVCC due to traffic reasons (e.g., for capacity reason, re-enabling high speed broadband access when LTE is available) +- The solution shall support the UE to return to the source BSS/RAN when HO failed and shall not cause any audible disruption on the voice call. + +## 4.3 Performance requirements + +The RAT change procedure executed to enable **Service Continuity** for an established voice call shall target an interruption time not higher than 300 ms. + +## 4.4 Reverse SRVCC deployment scenarios + +This section details the most likely reasons that can lead operators to deploy rSRVCC, and the handover scenarios which are most important in the different cases: + +- 1) Providing users better service: + +As packet services are better provided over E-UTRAN/HSPA, the operator deploys rSRVCC to make sure that users get service on E-UTRAN/HSPA as soon as E-UTRAN/HSPA becomes available (i.e. typically when the E-UTRAN/HSPA cell quality is better than a given threshold). + +### 2) Optimizing network usage: + +The operator wants to minimize the CS core network usage and to optimize the radio network usage, so it chooses to handover calls to PS as soon as E-UTRAN/HSPA becomes available. (i.e. typically when the E-UTRAN/HSPA cell quality is better than a given threshold) + +### 3) Enhancing coverage: + +The operator wants to enhance its radio coverage by adding the possibility to handover calls to E-UTRAN where GERAN/UTRAN coverage is getting weak. + +It could either be that the E-UTRAN cell quality is getting better than the GERAN/UTRAN cell quality, or that the GERAN/UTRAN cell quality gets worse than a given threshold, while the E-UTRAN cell quality is better than another one. + +It is expected that scenarios 1) and 2) will be the most common, and consequently, that even if coverage triggered rSRVCC handovers are expected to occur, they should not be the most frequent. + +# --- 5 Architecture model and reference points + +## 5.1 General + +The architecture for SRVCC from UTRAN/GERAN to E-UTRAN/HSPA reuses the architecture model as defined in TS 23.216 [7]. + +The overall model and impacts to the various elements is provided in the following clauses. + +## 5.2 Reference architecture + +### 5.2.1 3GPP UTRAN/GERAN and E-UTRAN SRVCC architecture + +![Figure 5.2.1-1: SRVCC architecture for UTRAN/GERAN to E-UTRAN](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +The diagram shows the network architecture for SRVCC from UTRAN/GERAN to E-UTRAN. It features two UE states: an initial state connected to UTRAN/GERAN and a target state connected to E-UTRAN. + +- Source Path:** UE → (Um/Uu) → UTRAN/GERAN → (Iu-cs/A) → MSC Server → IMS. Also, UTRAN/GERAN → (Iu-ps/Gb) → SGSN → (Gn/S3) → MME. +- Target Path:** UE → (E-UTRAN Uu) → Target E-UTRAN → (S1-MME) → MME → (S11) → Serving/PDN GW → (SGi) → IMS. +- Common Elements:** MME connects to HSS via S6a. Target E-UTRAN connects to Serving/PDN GW via S1-U. +- Legend:** + - Solid thick line: Bearer path before HO + - Dashed thick line: Bearer path after HO + - Dashed thin line: SIP signaling path before HO + +Figure 5.2.1-1: SRVCC architecture for UTRAN/GERAN to E-UTRAN + +NOTE 1: The following figure only shows the necessary components related to MSC Server enhanced with SRVCC. + +NOTE 2: MSC Server shown in the figure is enhanced for SRVCC. + +NOTE 3: This architecture also applies to roaming scenario (i.e. S8, S6a are not impacted due to SRVCC). + +NOTE 4: Both Gn-SGSN and S4-SGSN are supported. + +**Figure 5.2.1-1: SRVCC architecture for UTRAN/GERAN to E-UTRAN** + +### 5.2.2 3GPP UTRAN/GERAN and UTRAN (HSPA) SRVCC architecture + +![Figure 5.2.2-1: SRVCC architecture for UTRAN/GERAN to UTRAN (HSPA) with Gn based SGSN](ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg) + +This diagram illustrates the SRVCC architecture for UTRAN/GERAN to UTRAN (HSPA) using a Gn-based SGSN. + +- Source Path:** UE → (Um/Uu) → UTRAN/GERAN → (Iu-cs/A) → MSC Server → IMS. Also, UTRAN/GERAN → (Iu-ps/Gb) → SGSN → (Gn) → Target SGSN. +- Target Path:** UE → (Uu) → Target UTRAN(HSPA) → (Iu-ps) → SGSN → (Gn) → GGSN → (Gi) → IMS. +- Common Elements:** The target SGSN connects to HSS via Gr. +- Visual Flow:** An arrow indicates the UE moving from the top source configuration to the bottom target configuration. + +Figure 5.2.2-1: SRVCC architecture for UTRAN/GERAN to UTRAN (HSPA) with Gn based SGSN + +**Figure 5.2.2-1: SRVCC architecture for UTRAN/GERAN to UTRAN (HSPA) with Gn based SGSN** + +![Diagram of SRVCC architecture for UTRAN/GERAN to UTRAN (HSPA) with S4 based SGSN. The diagram shows two states: the initial state (top) and the state after SRVCC (bottom). In the initial state, a UE is connected to UTRAN/GERAN via Um/Uu. UTRAN/GERAN is connected to an MSC Server via lu-cs/A and to an SGSN via lu-ps/Gb. The MSC Server is connected to the IMS. The SGSN is connected to another SGSN via S16. This second SGSN is connected to an HSS via Gr and to a Serving/PDN GW via S4. The Serving/PDN GW is connected to the IMS via SGi. In the state after SRVCC, the UE is connected to Target UTRAN (HSPA) via Uu. Target UTRAN (HSPA) is connected to the Serving/PDN GW via S12. The Serving/PDN GW is connected to the IMS via SGi. A downward arrow indicates the transition from the initial state to the state after SRVCC.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Diagram of SRVCC architecture for UTRAN/GERAN to UTRAN (HSPA) with S4 based SGSN. The diagram shows two states: the initial state (top) and the state after SRVCC (bottom). In the initial state, a UE is connected to UTRAN/GERAN via Um/Uu. UTRAN/GERAN is connected to an MSC Server via lu-cs/A and to an SGSN via lu-ps/Gb. The MSC Server is connected to the IMS. The SGSN is connected to another SGSN via S16. This second SGSN is connected to an HSS via Gr and to a Serving/PDN GW via S4. The Serving/PDN GW is connected to the IMS via SGi. In the state after SRVCC, the UE is connected to Target UTRAN (HSPA) via Uu. Target UTRAN (HSPA) is connected to the Serving/PDN GW via S12. The Serving/PDN GW is connected to the IMS via SGi. A downward arrow indicates the transition from the initial state to the state after SRVCC. + +NOTE 1: The above figures only show the necessary components related to MSC Server enhanced with SRVCC. + +NOTE 2: MSC Server shown in the above figures are enhanced for SRVCC. + +NOTE 3: This architecture also applies to roaming scenario. + +**Figure 5.2.2-2: SRVCC architecture for UTRAN/GERAN to UTRAN (HSPA) with S4 based SGSN** + +## 5.3 Functional Entities + +NOTE: IMS components are not described here. Please refer to TS 23.237 [4] and TS 23.292 [3]. + +### 5.3.1 MSC Server enhanced for SRVCC + +In addition to the standard MSC Server behaviour defined in TS 23.216 [7], an MSC Server which has been enhanced for SRVCC from UTRAN/GERAN to E-UTRAN/HSPA provides the following functions: + +- Handling the Relocation Preparation procedure requested for the voice component from BSC/RSC via Sv reference point; + +## 5.4 Reference points + +No reference point is introduced for the purpose of SRVCC from UTRAN/GERAN CS access to E-UTRAN/HSPA access. + +# 6 Solutions + +## 6.1 Solution 1: Session transfer initiated on E-UTRAN/HSPA + +### 6.1.1 Functional Description + +A prerequisite for calls to be possible to handover from UTRAN/GERAN to E-UTRAN/HSPA is that they have been anchored in IMS at the time of their establishment. For calls established on the UTRAN/GERAN side with no voice over IMS support implies the existence of ICS capabilities in the network or in the UE. + +**Editor's Note: The functional description of the MSC enhanced for rSRVCC and of the UE enhanced for rSRVCC need to be added to this section.** + +### 6.1.2 Information flows + +#### 6.1.2.1 GERAN/UTRAN Attach procedure + +The UTRAN/GERAN Attach procedure for an SRVCC from UTRAN/GERAN to E-UTRAN capable UE is performed as defined in clause 6.5 of TS 23.060 [6] with the following additions: + +- 1) The UE indicates to the network its capability to perform SRVCC from UTRAN/GERAN to E-UTRAN as follows: + +- a) In case of a network of Network Mode of Operation type I: + - The " rSRVCC capability indication" is sent by the UE in the Attach Request message sent to the SGSN at combined GPRS/IMSI Attach, and in the Routing Area Update Request message at combined RA/LA Update. + - If received by the SGSN, the " rSRVCC capability indication" is transmitted by the SGSN to the MSC in the Location Updating procedure. + - b) In case of a network of Network Mode of Operation types II or III: + - The " rSRVCC capability indication" is sent by the UE in the Location Updating Request it sends to the network. +- 2) If the subscriber is allowed to have rSRVCC in the VPLMN, the HSS shall include the "rSRVCC allowed" indication in the Insert Subscriber Data sent to the MSC at Attach or at Location Area Update. + - 3) The MSC enhanced for rSRVCC shall subscribe to the registration event package at Attach or Location Area Update. This will be used for it to monitor the IMS registration status of the UE. + +**Editor's Note:** Whether this is possible in case the MSC does not register the user on behalf of the UE (as an MSC enhanced for ICS does) is FFS. + +**Editor's Note:** Whether the MSC can correlate the registration status received from the SCC AS with the identity used by the UE in the ongoing session is FFS. + +#### 6.1.2.2 E-UTRAN attach procedure + +The E-UTRAN attach procedure for 3GPP rSRVCC UE is performed as defined in clause 6.3.1 of TS 23.216 [7] with the following additions: + +- 1) rSRVCC UE includes the "rSRVCC capability indication" as part of the "MS Network Capability" in the Attach Request message and in Tracking Area Updates. +- 2) If the subscriber is allowed to have rSRVCC in the VPLMN, the HSS shall include the "rSRVCC allowed" indication as part of the subscription data sent to the MME. + +#### 6.1.2.3 Call establishment procedure in GERAN/UTRAN + +If the MSC server enhanced for rSRVCC determines that rSRVCC is allowed for a given call, it shall include an "rSRVCC possible indication" to the RNS/BSS at call set up to/from an rSRVCC capable UE in: + +- 1) The RAB Assignment Message sent over the Iu-CS interface for a network in Iu mode. +- 2) The Assignment Request sent over the A interface for a network in A/Gb mode. + +The setting of the "rSRVCC possible indication" by the MSC shall at least take into account the following elements: + +- 1) rSRVCC capability of the UE + +The "rSRVCC capability indication" is received from the GERAN/UTRAN to E-UTRAN SRVCC capable UE at Attach or Location Area Update, see clause 6.1.2.1. + +- 2) Authorization of the user for rSRVCC + +The "rSRVCC allowed" information is received from the GERAN/UTRAN to E-UTRAN SRVCC capable UE at Attach or Location Area Update, see clause 6.1.2.1. + +- 3) Prior anchoring of a voice call in the SCC AS + +At call establishment, the rSRVCC capable MSC server shall consider the call as anchored in the SCC AS in the two following cases: + +- a) The voice calls was initiated by the UE on UTRAN/GERAN using CS domain procedures and the MSC has itself anchored using ICS procedures (which can only be the case if the MSC is enhanced for ICS). + +- b) The voice call was initiated on GERAN/UTRAN by a UE enhanced for ICS, using the Gm or the I1 interface for service control purposes. + +To enable the MSC enhanced for rSRVCC to distinguish such calls, rSRVCC capable UEs which are also ICS capable (as defined in TS 23.292 [3]) shall include an "IMS anchoring performed" indicator in a CS CALL SETUP message corresponding to bearer control signalling for a call established using Gm or I1. The presence of that indicator shall be understood by the MSC enhanced for rSRVCC as the fact that the UE has anchored the call in IMS using ICS capabilities. + +##### 4) IMS registration status of the UE + +Additionally, operator policies or local policies could be used for the MSC enhanced for rSRVCC in setting the "rSRVCC possible indication" sent towards the RNS/BSS at call establishment. + +The BSS/RNS shall use that indication to decide for which cells the UE shall report measurements, as a basis for triggering a SRVCC handover from GERAN/UTRAN to E-UTRAN/HSPA. + +#### 6.1.2.4 SRVCC from E-UTRAN/HSPA to GERAN/UTRAN + +The procedures defined in 6.2 and 6.3 of TS 23.216 [7] apply with the following additions: + +If received from the UE and the HSS respectively, the MME/SGSN shall include the "rSRVCC capability indication" as well as the "rSRVCC allowed" in the SRVCC PS to CS Request it sends to the target MSC (via the MSC enhanced for SRVCC). + +In case the MSC server enhanced for rSRVCC determines that rSRVCC is allowed for a given call, it shall include an "rSRVCC possible indication" to the RNS/BSS in the Handover Request/Iu Relocation Request it sends towards the BSS/RNS. + +Once the SRVCC handover procedure is over, the MSC enhanced for rSRVCC shall subscribe to the registration event package at Attach or Location Area Update. This will be used for it to monitor the IMS registration status of the UE. + +**Editor's Note:** Whether this is possible in case the MSC does not register the user on behalf of the UE (as an MSC enhanced for ICS does) is FFS. + +**Editor's Note:** Whether the MSC can correlate the registration status received from the SCC AS with the identity used by the UE in the ongoing session is FFS. + +#### 6.1.2.5 Handover procedure in GERAN/UTRAN + +If the CS domain call is subject to radio-level handover (e.g. intra-RAT, inter-RAT, intra-MSC, inter-MSC, etc) while remaining in the CS domain, the "rSRVCC possible indication" needs to be forwarded to the target radio access (RNS/BSS) provided that it still applies. + +**Editor's Note:** The way this information is conveyed needs to be further detailed. + +#### 6.1.2.6 Call flows for SRVCC from UTRAN/GERAN to E-UTRAN + +##### 6.1.2.6.1 SRVCC handover from GERAN without DTM support to E-UTRAN + +Depicted in Figure 6.1.2.6.1-1 is a call flow for SRVCC handover from GERAN without DTM support to E-UTRAN. + +![Sequence diagram of SRVCC handover from GERAN without DTM support to E-UTRAN. The diagram shows the interaction between UE, Target E-UTRAN, Target MME, MSC server/MGW, Source MSC, Source SGSN, Source BSS, SGW, and IMS (SCC AS). The process starts with the UE having an ongoing CS call and suspended PS bearers. It proceeds through measurement reports, HO decision, HO required/ack, HO Command, TAU procedure, STI, dedicated bearer activation, and resource release.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Target E-UTRAN + participant Target MME + participant MSC server/MGW + participant Source MSC + participant Source SGSN + participant Source BSS + participant SGW + participant IMS (SCC AS) + + Note left of UE: UE has an ongoing CS call and all PS bearers are suspended + UE->>Source BSS: 1-Measurement Reports + Note right of Source BSS: Decision for HO + Source BSS->>Source MSC: 2-HO required + Source MSC->>Source SGSN: 3-Prep HO Req/Resp + Source MSC->>Source BSS: 4-HO required ack + Source BSS->>UE: 5-HO Command + Note left of UE: UE tunes to E-UTRAN + Note over UE, Target MME: 6 – TAU procedure (if needed) + UE->>IMS (SCC AS): 7-Initiation of Session Transfer (STI) + Note right of IMS (SCC AS): Update remote end + Note over UE, Target MME: 8 – NW-initiated dedicated bearer activation for the voice component + Note right of IMS (SCC AS): Release of CS access leg + Note over MSC server/MGW, Source MSC: 9 – Release Resources in MSC server after release from the IMS + +``` + +Sequence diagram of SRVCC handover from GERAN without DTM support to E-UTRAN. The diagram shows the interaction between UE, Target E-UTRAN, Target MME, MSC server/MGW, Source MSC, Source SGSN, Source BSS, SGW, and IMS (SCC AS). The process starts with the UE having an ongoing CS call and suspended PS bearers. It proceeds through measurement reports, HO decision, HO required/ack, HO Command, TAU procedure, STI, dedicated bearer activation, and resource release. + +**Figure 6.1.2.6.1-1: SRVCC handover from GERAN without DTM support to E-UTRAN** + +At the beginning of the call flow, all PS bearers are suspended. The source system is configured to know that the target MME/TA where the UE is moving support IMS VoIP. + +1. Based on UE measurement reports the source BSS decides to trigger a handover to E-UTRAN. +2. Source BSS sends a Handover Required (Source to Target Transparent Container) message to the source MSC. +3. Source MSC executes the inter-MSC handover procedure by exchanging Prepare HO Request/ Response messages with the MSC Server. The MSC server checks whether the IMS registration of the user on the UE is still valid or not. In case it is not, it rejects the handover request, indicating in the cause value that rSRVCC is not possible any longer. That should trigger the RAN to reconfigure the cells the UE shall measure. If the IMS registration is still valid, the MSC Server signals successful CS handover without allocating any E-UTRAN resources. +4. Source MSC sends a Handover Required Acknowledge message to the source BSS. +5. Source BSS sends a Handover Command to the UE instructing it to perform a CS to PS handover to E-UTRAN. Note that this message does not contain any transparent container information. +6. UE re-tunes to E-UTRAN radio and performs a TAU procedure as specified in TS 23.401 [5]. UE uses the Active flag in the TAU Request to MME to resume the suspended SIP signalling bearer and any other suspended non-voice bearers. The MME requests the context from the source SGSN. The MME will inform S-GW and PDN-GW(s) to resume the suspended bearers +7. Subsequently UE initiates the Session Transfer procedure e.g. by sending a SIP INVITE (STI) message to the SCC AS. Standard IMS Service Continuity procedures are applied for execution of the Session Transfer, see TS 23.237 [4]. As part of this procedure the remote end is updated with the SDP of the IMS access leg. The downlink flow of VoIP packets is switched towards the PDN GW at this point. +8. The IMS triggers a network-initiated dedicated bearer activation for the voice component. +9. The IMS releases the CS access leg which result in release of resources in the MSC Server. + +##### 6.1.2.6.2 SRVCC handover from UTRAN or GERAN with PS handover support to E-UTRAN + +Depicted in Figure 6.1.2.6.2-1 is a call flow for SRVCC handover from UTRAN or GERAN with PS handover support to E-UTRAN, including the handling of the non-voice component. E-UTRAN neighbouring cells have to be configured in UTRAN/GERAN for the purpose of measurements. The source system is configured to know that the target MME/TA where the UE is moving support IMS VoIP. + +![Sequence diagram for SRVCC handover from UTRAN or GERAN with PS handover support to E-UTRAN. The diagram shows the interaction between UE, Target eNode B, Target MME, MSC server/MGW, Source MSC, Source SGSN, Source RNS/BSS, SGW, and IMS (SCC AS). The process involves measurement reports, decision for HO, PS relocation steps (2a-6b), CS relocation steps (3a-6b), HO command, UE tuning, HO complete, session transfer, bearer activation, and resource release.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Target eNode B + participant Target MME + participant MSC server/MGW + participant Source MSC + participant Source SGSN + participant Source RNS/BSS + participant SGW + participant IMS (SCC AS) + + Note right of Source RNS/BSS: Decision for HO + UE->>Source RNS/BSS: 1-Measurement Reports + Source RNS/BSS->>Source SGSN: 2a-Reloc Required + Source SGSN->>Target MME: 2b-Fw Reloc Req + Source RNS/BSS->>Source MSC: 3a-Reloc Required + Source MSC->>MSC server/MGW: 3b-Prep HO Req + Target MME->>Source MME: 3c-Fw Reloc Req + Target MME->>Target eNode B: 4-HO Req/Ack + Target MME->>MSC server/MGW: 5a-Fw Reloc Req + MSC server/MGW->>Source MSC: 5b-Prep HO Resp + Source MSC->>Source SGSN: 5c-Reloc Req Ack + Target MME->>Source SGSN: 6a-Fw Reloc Ack + Source SGSN->>Source RNS/BSS: 6b-Fw Reloc Ack + Target MME->>UE: 7-HO Command + Note left of UE: UE tunes to E-UTRAN + UE->>Target eNode B: 8-HO to E-UTRAN complete + Target eNode B->>Target MME: 9-HO notify + Target MME->>MSC server/MGW: 10a-Fwd Reloc Complete/Ack + MSC server/MGW->>Source MSC: 10b-SES (HO Complete) + Target MME->>Source SGSN: 11a-Fwd Reloc Complete/Ack + Note right of Target MME: 11b - Update Bearer Procedure + Note left of Target MME: 12 - TAU Procedure if needed + Target MME->>IMS (SCC AS): 13-Initiation of Session Transfer (STI) + Note right of IMS (SCC AS): Session Transfer + Note right of IMS (SCC AS): Update remote end + Note right of Target MME: 14 - NW initated dedicated bearer activation for the voice component + Note right of Source MSC: 15 - Release resource in MSC server after release from the IMS + +``` + +Sequence diagram for SRVCC handover from UTRAN or GERAN with PS handover support to E-UTRAN. The diagram shows the interaction between UE, Target eNode B, Target MME, MSC server/MGW, Source MSC, Source SGSN, Source RNS/BSS, SGW, and IMS (SCC AS). The process involves measurement reports, decision for HO, PS relocation steps (2a-6b), CS relocation steps (3a-6b), HO command, UE tuning, HO complete, session transfer, bearer activation, and resource release. + +**Figure 6.1.2.6.2-1: SRVCC handover from UTRAN or GERAN with PS handover support to E-UTRAN** + +1. Based on UE measurement reports the RNS/BSS decides to trigger a handover to E-UTRAN. +2. Source RNS initiates PS relocation. The following steps are performed: + - a) Source RNS/BSS sends a Relocation Required (Source to Target Transparent Container) message to source SGSN. + - b) Source SGSN sends a Forward Relocation Request message to the target MME including information about the non-voice component only. +3. In parallel to the previous step, the source RNS/BSS initiates CS relocation. The following steps are performed: + - a) Source RNS/BSS sends a Relocation Required (Source to Target Transparent Container) message to the source MSC. + - b) Source MSC sends a Prepare HO Request to the MSC Server. + - c) The MSC server checks whether the IMS registration of the user on the UE is still valid or not. In case it is not, it shall reject the handover request, indicating in the cause value that rSRVCC is not possible any longer. That should trigger the RAN to cancel the relocation procedure that was started towards the SGSN and to + +reconfigure the cells the UE shall measure. In case the IMS registration is still valid, the MSC Server sends a Forward Relocation Request (Source to Target Transparent Container) message to the target MME. + +4. Target MME synchronises the two Forward Relocation Request messages and requests resource allocation for the non-voice component only by exchanging Handover Request/Acknowledge messages with the target E-UTRAN. +5. Target MME acknowledges the prepared CS relocation towards the source access. The following steps are performed: + - a) Target MME sends a Forward Relocation Response (Target to Source Transparent Container) message to the MSC Server. + - b) MSC Server sends a Prepare HO Response to the source MSC. + - c) Source MSC sends a Relocation Required Acknowledge (Target to Source Transparent Container) message to source RNS/BSS. +6. In parallel to the previous step, the target MME acknowledges the prepared PS relocation towards the source access. The following steps are performed: + - a) Target MME sends a Forward Relocation Response (Target to Source Transparent Container) message to the source SGSN. + - b) Source SGSN sends a Relocation Required Acknowledge (Target to Source Transparent Container) message to the source RNS/BSS. +7. Source RNS/BSS synchronises the two Relocation Required Acknowledge messages and sends a HO Command message to the UE instructing it to perform a handover to E-UTRAN, including the relocation of the voice bearer to the PS domain. +8. UE re-tunes to E-UTRAN radio and sends a Handover to E-UTRAN Complete message to the E-UTRAN. +9. Target E-UTRAN informs the target MME by sending a Handover Notify message. +10. Target MME completes the CS relocation. The following steps are performed: + - a) Target MME sends a Forward Relocation Complete message to the MSC Server. MSC Server acknowledges the information by sending a Forward Relocation Complete Acknowledge message to the source MME. + - b) MSC Server sends a Handover Complete message to the source MSC. +11. In parallel to the previous step the target MME completes the PS relocation. The following steps are performed: + - a) Target MME exchanges Forward Relocation Complete / Acknowledge messages with the source SGSN. + - b) Target MME performs the Update bearer procedure with the Serving GW and the PDN GW. At this point the relocation of all non-voice PS bearers is completed and the user data are flowing across E-UTRAN access in both directions. +12. UE performs a TAU procedure if required (e.g. due to UE mobility under CS coverage). +13. UE initiates the Session Transfer procedure e.g. by sending a SIP INVITE (STI) message to the SCC AS. Standard IMS Service Continuity procedures are applied for execution of the Session Transfer, see TS 23.292 [3] and TS 23.237 [4]. As part of this procedure the remote end is updated with the SDP of the IMS access leg. The downlink flow of VoIP packets is switched towards the PDN GW at this point. This step can occur in parallel with step 12. +14. The IMS triggers a network-initiated dedicated bearer for the voice component. +15. The IMS releases the CS access leg which result in release of resources in the MSC Server. + +#### 6.1.2.7 Call flows for SRVCC from UTRAN/GERAN to HSPA + +##### 6.1.2.7.1 SRVCC handover from GERAN without DTM support to HSPA + +![Sequence diagram for SRVCC handover from GERAN without DTM support to HSPA. The diagram shows the interaction between UE, Target E-UTRAN, Target MME, MSC server/MGW, Source MSC, Source SGSN, Source BSS, SGW, and IMS (SCC AS). The process starts with the UE having an ongoing CS call and all PS bearers suspended. The UE sends measurement reports to the Source BSS, which makes a decision for HO. The Source BSS sends a HO required message to the Source MSC, which then sends a Prep HO Req/Resp to the MSC server/MGW. The Source MSC sends a HO required ack to the Source BSS, which then sends a HO Command to the UE. The UE tunes to UTRAN and performs a RAU procedure. The UE then initiates the Session Transfer (ST) procedure to the IMS (SCC AS), which updates the remote end. The IMS triggers network-initiated dedicated bearer activation for the voice component. Finally, the IMS releases the CS access leg, resulting in the release of resources in the MSC Server.](9cd90f495b95ad2116ff780248c26d95_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Target E-UTRAN + participant Target MME + participant MSC server/MGW + participant Source MSC + participant Source SGSN + participant Source BSS + participant SGW + participant IMS (SCC AS) + + Note left of UE: UE has an ongoing CS call and all PS bearers are suspended + UE->>Source BSS: 1-Measurement Reports + Note right of Source BSS: Decision for HO + Source BSS->>Source MSC: 2-HO required + Source MSC->>MSC server/MGW: 3-Prep HO Req/Resp + MSC server/MGW->>Source MSC: 4-HO required ack + Source MSC->>Source BSS: 5-HO Command + UE->>Target E-UTRAN: UE tunes to UTRAN + Note over UE, Target E-UTRAN, Target MME, MSC server/MGW, Source MSC, Source SGSN, Source BSS, SGW: 6 - RAU procedure + UE->>IMS (SCC AS): 7-Initiation of Session Transfer (ST) + Note right of IMS (SCC AS): Update remote end + Note over UE, Target E-UTRAN, Target MME, MSC server/MGW, Source MSC, Source SGSN, Source BSS, SGW: 8 - NW-initiated dedicated bearer activation for the voice component + Note over MSC server/MGW, Source MSC, Source SGSN, Source BSS, SGW: 9 - Release Resources in MSC server after release from the IMS + +``` + +Sequence diagram for SRVCC handover from GERAN without DTM support to HSPA. The diagram shows the interaction between UE, Target E-UTRAN, Target MME, MSC server/MGW, Source MSC, Source SGSN, Source BSS, SGW, and IMS (SCC AS). The process starts with the UE having an ongoing CS call and all PS bearers suspended. The UE sends measurement reports to the Source BSS, which makes a decision for HO. The Source BSS sends a HO required message to the Source MSC, which then sends a Prep HO Req/Resp to the MSC server/MGW. The Source MSC sends a HO required ack to the Source BSS, which then sends a HO Command to the UE. The UE tunes to UTRAN and performs a RAU procedure. The UE then initiates the Session Transfer (ST) procedure to the IMS (SCC AS), which updates the remote end. The IMS triggers network-initiated dedicated bearer activation for the voice component. Finally, the IMS releases the CS access leg, resulting in the release of resources in the MSC Server. + +**Figure 6.1.2.7.1-1: SRVCC handover from GERAN without DTM support to HSPA** + +At the beginning of the call flow all PS bearers are suspended. The source system is configured to know that the target MME/TA where the UE is moving support IMS VoIP. + +1. The UE reports that a UTRAN has now good quality by sending a Measurement Report to the BSS. Based on that input, the BSS decides to trigger SRVCC to UTRAN/HSPA. +2. Source BSS sends a Handover Required (Source to Target Transparent Container) message to the source MSC. +3. Source MSC executes the inter- MSC handover procedure by exchanging Prepare HO Request/ Response messages with the MSC Server. The MSC server checks whether the IMS registration of the user on the UE is still valid or not. In case it is not, it shall reject the handover request, indicating in the cause value that rSRVCC is not possible any longer. That should trigger the RAN to reconfigure the cells the UE shall measure. In case the IMS registration is still valid, the MSC Server signals successful CS handover without allocating any E-UTRAN resources. +4. Source MSC sends a Handover Required Acknowledge message to the source BSS. +5. Source BSS sends a Handover Command to the UE. The Handover Command includes an indication that this is a CS to PS handover. +6. UE re-tunes to UTRAN radio and performs a RAU procedure to resume the suspended SIP signalling bearer and any other suspended non-voice bearers. +7. Subsequently UE initiates the Session Transfer procedure e.g. by sending a SIP INVITE (STI) message to the SCC AS. Standard IMS Service Continuity procedures are applied for execution of the Session Transfer, see TS 23.292 [3] and TS 23.237 [4]. As part of this procedure the remote end is updated with the SDP of the IMS access leg. The downlink flow of VoIP packets is switched towards the PDN GW at this point. +8. The IMS triggers network-initiated dedicated bearer activation for the voice component. +9. The IMS releases the CS access leg which result in release of resources in the MSC Server. + +##### 6.1.2.7.2 SRVCC handover from UTRAN or GERAN with PS handover support to HSPA + +Depicted in Figure 6.1.2.3.2-1 is a call flow for SRVCC handover from UTRAN or GERAN with PS handover support to HSPA, including the handling of the non-voice component. The source system is configured to know that the target MME/TA where the UE is moving support IMS VoIP. + +![Sequence diagram for SRVCC handover from UTRAN or GERAN with PS handover support to HSPA. The diagram shows the interaction between UE, Target RNS, Target SGSN, MSC server/MGW, Source MSC, Source SGSN, Source RNS/BSS, SGW, and IMS (SCC AS). The process involves measurement reports, decision making, preparation of target and source systems, execution of the handover, and subsequent session transfer and resource management.](898fb89a50d9ec1dfb4e425c816976a7_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Target RNS + participant Target SGSN + participant MSC server/MGW + participant Source MSC + participant Source SGSN + participant Source RNS/BSS + participant SGW + participant IMS (SCC AS) + + Note left of UE: UE tunes to UTRAN cell + UE->>Source RNS/BSS: 1-Measurement Report + Note right of Source RNS/BSS: Decision for HO + Source RNS/BSS->>Source SGSN: 2a-Reloc Required + Source SGSN->>Target SGSN: 2b-Fw Reloc Req + Source RNS/BSS->>Source MSC: 3a-Reloc Required + Source MSC->>MSC server/MGW: 3b-Prep HO Req + Target SGSN->>Target RNS: 3c-Fw Reloc Req + Target RNS->>UE: 4-Reloc Req/Ack + Target SGSN->>MSC server/MGW: 5a-Fw Reloc Resp + MSC server/MGW->>Source MSC: 5b-Prep HO Resp + Source MSC->>Source SGSN: 5c-Reloc Req Ack + Source SGSN->>Target SGSN: 6a-Fw Reloc Ack + Source RNS/BSS->>Source SGSN: 6b-Reloc Req Ack + Target SGSN->>UE: 7-HO Command + Note left of UE: 8 - HO detection + UE->>Target RNS: 9-Reloc complete + Target RNS->>Target SGSN: 10a-Fwd Reloc Complete/Ack + Target SGSN->>Source MSC: 10b-SES (HO Complete) + Target SGSN->>Source SGSN: 11a-Fwd Reloc Complete/Ack + Note right of Target SGSN: 11b - Update Bearer Procedure + Note left of Target SGSN: 12 - RAU Procedure if needed + Target SGSN->>IMS (SCC AS): 13-Initiation of Session Transfer (STT) + Note right of IMS (SCC AS): Session Transfer + Note right of IMS (SCC AS): Update remote end + Note right of Target SGSN: 14 - NW initiated dedicated bearer activation for the voice component + Note right of Source MSC: 15 - Release resource in MSC server after release from the IMS + +``` + +Sequence diagram for SRVCC handover from UTRAN or GERAN with PS handover support to HSPA. The diagram shows the interaction between UE, Target RNS, Target SGSN, MSC server/MGW, Source MSC, Source SGSN, Source RNS/BSS, SGW, and IMS (SCC AS). The process involves measurement reports, decision making, preparation of target and source systems, execution of the handover, and subsequent session transfer and resource management. + +**Figure 6.1.2.7.2-1: SRVCC handover from UTRAN or GERAN with PS handover support to HSPA** + +- Based on UE measurement reports the RNS decides to trigger a handover to UTRAN/HSPA. +- Source RNS initiates PS relocation. The following steps are performed: + - Source RNS sends a Relocation Required (Source to Target Transparent Container) message to source SGSN. + - Source SGSN sends a Forward Relocation Request message to the target SGSN including information about the non-voice component only. +- In parallel to the previous step, the source RNS initiates CS relocation. The following steps are performed: + - Source RNS sends a Relocation Required (Source to Target Transparent Container) message to the source MSC. + - Source MSC sends a Prepare HO Request to the MSC Server. + - The MSC server checks whether the IMS registration of the user on the UE is still valid or not. In case it is not, it shall reject the handover request, indicating in the cause value that rSRVCC is not possible any longer. That should trigger the RAN to cancel the relocation procedure that was started towards the SGSN and to reconfigure the cells the UE shall measure. In case the IMS registration is still valid, the MSC Server sends a Forward Relocation Request (Source to Target Transparent Container) message to the target SGSN. + +4. Target SGSN synchronises the two Forward Relocation Request messages and requests resource allocation for the non-voice component only by exchanging Handover Request/Acknowledge messages with the target E-UTRAN. +5. Target SGSN acknowledges the prepared CS relocation towards the source access. The following steps are performed: + - a) Target SGSN sends a Forward Relocation Response (Target to Source Transparent Container) message to the MSC Server. + - b) MSC Server sends a Prepare HO Response to the source MSC. + - c) Source MSC sends a Relocation Required Acknowledge (Target to Source Transparent Container) message to source RNS. +6. In parallel to the previous step, the target SGSN acknowledges the prepared PS relocation towards the source access. The following steps are performed: + - a) Target SGSN sends a Forward Relocation Response (Target to Source Transparent Container) message to the source SGSN. + - b) Source SGSN sends a Relocation Required Acknowledge (Target to Source Transparent Container) message to the source RNS. +7. Source RNS synchronises the two Relocation Required Acknowledge messages and sends a HO Command message to the UE instructing it to move to UTRAN/HSPA for VoIMS. +8. Handover Detection at the target RNS. The UE sends an RRC message indicating the successful handover of the PS bearers to UTRAN/HSPA. +9. The Target RNS sends a Relocation Complete message to the Target SGSN. +10. Target SGSN completes the CS relocation. The following steps are performed: + - a) Target SGSN sends a Forward Relocation Complete message to the MSC Server. MSC Server acknowledges the information by sending a Forward Relocation Complete Acknowledge message to the source SGSN. + - b) MSC Server sends a Handover Complete message to the source MSC. +11. In parallel to the previous step the target SGSN completes the PS relocation. The following steps are performed: + - a) Target SGSN exchanges Forward Relocation Complete / Acknowledge messages with the source SGSN. + - b) Target SGSN performs the Update bearer procedure with the Serving GW and the PDN GW. At this point the relocation of all non-voice PS bearers is completed and the user data are flowing across UTRAN access in both directions. +12. UE performs a RAU procedure if required (e.g. due to UE mobility under CS coverage). +13. UE initiates the Session Transfer procedure e.g. by sending a SIP INVITE (STI) message to the SCC AS. Standard IMS Service Continuity procedures are applied for execution of the Session Transfer, see TS 23.292 [3] and TS 23.237 [4]. As part of this procedure the remote end is updated with the SDP of the IMS access leg. The downlink flow of VoIP packets is switched towards the PDN GW at this point. This step can occur in parallel with step 12. +14. The IMS triggers a network-initiated dedicated bearer for the voice component. +15. The IMS releases the CS access leg which result in release of resources in the MSC Server. + +## 6.2 Solution 2: Session transfer initiated on E-UTRAN/HSPA + +### 6.2.0 General + +This solution reuses the proposal from Solution 1 with simplification to CS HO procedure. + +### 6.2.1 Functional Description + +A prerequisite for calls to be possible to handover from UTRAN/GERAN to E-UTRAN/HSPA is that they have been anchored in IMS at the time of their establishment. For calls established on the UTRAN/GERAN side with no Voice over IMS support, that implies some ICS capabilities in the network or in the UE. + +**Editor's Note:** The functional description of the MSC enhanced for rSRVCC and of the UE enhanced for rSRVCC need to be added to this section. + +### 6.2.2 Information flows + +#### 6.2.2.1 GERAN/UTRAN Attach procedure + +The UTRAN/GERAN Attach procedure for an SRVCC from UTRAN/GERAN to E-UTRAN capable UE is performed as defined in TS 23.060 [6] with the following additions: + +- 1) The UE indicates to the network its capability to perform SRVCC from UTRAN/GERAN to E-UTRAN as follows: + - a) In case of a network of Network Mode of Operation type I: + - The "rSRVCC capability indication" is sent by the UE in the Attach Request message sent to the SGSN at combined GPRS/IMSI Attach, and in the Routing Area Update Request message at combined RA/LA Update. + - If received by the SGSN, the "rSRVCC capability indication" is transmitted by the SGSN to the MSC in the Location Updating Procedure. + - b) In case of a network of Network Mode of Operation types II or III: + - The "rSRVCC capability indication" is sent by the UE in the Location Updating Request it sends to the network. +- 2) If the subscriber is allowed to have rSRVCC in the VPLMN, the HSS shall include the "rSRVCC allowed" indication in the Insert Subscriber Data sent to the MSC at Attach or at Location Area Update. + +**Editor's Note:** Whether a new "rSRVCC allowed" indication is required remains to be confirmed. If the information elements already defined for SRVCC are enough the parts related to that indication in this chapter and in the following ones need to be revisited. + +#### 6.2.2.2 E-UTRAN attach procedure + +The E-UTRAN attach procedure for 3GPP rSRVCC UE is performed as defined in TS 23.216 [7] with the following additions: + +- 1) rSRVCC UE includes the "rSRVCC capability indication" as part of the "MS Network Capability" in the Attach Request message and in Tracking Area Updates. +- 2) If the subscriber is allowed to have rSRVCC in the VPLMN, the HSS shall include the "rSRVCC allowed" indication as part of the subscription data sent to the MME. + +#### 6.2.2.3 Call establishment procedure in GERAN/UTRAN + +In case the MSC server enhanced for rSRVCC determines that rSRVCC is allowed for a given call, it shall include an "rSRVCC possible indication" to the RNS/BSS at call set up to/from an rSRVCC capable UE in: + +- 1) The RAB Assignment Message sent over the Iu-CS interface for a network in Iu mode. +- 2) The Assignment Request sent over the A interface for a network in A/Gb mode. + +The setting of the "rSRVCC possible indication" by the MSC shall at least take into account the following elements: + +- 1) rSRVCC capability of the UE + +The "rSRVCC capability indication" is received from the GERAN/UTRAN to E-UTRAN SRVCC capable UE at Attach or Location Area Update, see clause 6.1.2.1. + +##### 2) Authorization of the user for rSRVCC + +The "rSRVCC allowed" information is received from the GERAN/UTRAN to E-UTRAN SRVCC capable UE at Attach or Location Area Update, see clause 6.1.2.1. + +##### 3) Prior anchoring of a voice call in the SCC AS + +At call establishment, the rSRVCC capable MSC server shall consider the call as anchored in the SCC AS in the two following cases: + +- The voice call was initiated by the UE on UTRAN/GERAN using CS domain procedures and the MSC has itself anchored using ICS procedures (which can only be the case if the MSC is enhanced for ICS). +- The voice call was initiated on GERAN/UTRAN by a UE enhanced for ICS, using the Gm or the I1 interface for service control purposes. + +To enable the MSC enhanced for rSRVCC to distinguish such calls, rSRVCC capable UEs which are also ICS capable (as defined in TS 23.292 [3]) shall include an "IMS anchoring performed" indicator in a CS CALL SETUP message corresponding to bearer control signalling for a call established using Gm or I1. The presence of that indicator shall be understood by the MSC enhanced for rSRVCC as the fact that the UE has anchored the call in IMS using ICS capabilities. + +##### 4) IMS registration status of the UE + +**Editor's Note:** The IMS registration of the UE is implicitly signalled by the ICS UE enhanced for rSRVCC through the "IMS anchoring performed" indication included in the CS call setup message. How the MSC enhanced for ICS gets the IMS registration status of the UE is FFS. + +**Editor's Note:** How to handle IMS registration expiration during a call is FFS. + +Additionally, operator policies or local policies could be used for the MSC enhanced for rSRVCC in setting the "rSRVCC possible indication" sent towards the RNS/BSS at call establishment. + +The BSS/RNS shall use that indication to decide for which cells the UE shall report measurements, as a basis for triggering a SRVCC handover from GERAN/UTRAN to E-UTRAN/HSPA. + +#### 6.2.2.4 SRVCC from E-UTRAN/HSPA to GERAN/UTRAN + +The procedures defined in clauses 6.2 and 6.3 of TS 23.216 [7] apply with the following additions: + +If received from the UE and the HSS respectively, the MME/SGSN shall include the "rSRVCC capability indication" as well as the "rSRVCC allowed" in the SRVCC PS to CS Request it sends to the target MSC (via the MSC enhanced for SRVCC). + +In case the MSC server enhanced for rSRVCC determines that rSRVCC is allowed for a given call, it shall include an "rSRVCC possible indication" to the RNS/BSS in the Handover Request/Iu Relocation Request it sends towards the BSS/RNS. + +#### 6.2.2.5 Handover procedure in GERAN/UTRAN + +If the CS domain call is subject to radio-level handover (e.g. intra-RAT, inter-RAT, intra-MSC, inter-MSC, etc) while remaining in the CS domain, the "rSRVCC possible indication" needs to be forwarded to the target radio access (RNS/BSS) provided that it still applies. + +**Editor's Note:** The way this information is conveyed needs to be further detailed. + +#### 6.2.2.6 Call flows for SRVCC from UTRAN/GERAN to E-UTRAN + +##### 6.2.2.6.1 SRVCC handover from GERAN without DTM support to E-UTRAN + +Depicted in Figure 6.2.2.6.1-1 is a call flow for SRVCC handover from GERAN without DTM support to E-UTRAN. + +![Sequence diagram for SRVCC handover from GERAN without DTM support to E-UTRAN. The diagram shows the interaction between UE, Target E-UTRAN, Target MME, MSC Server/MGW, Source MSC, Source SGSN, Source BSS, SGW, and IMS (SCC AS). The process starts with the UE sending measurement reports to the Source BSS. The Source BSS makes a decision to move the UE to LTE and sends an RRC Connection Release with redirection to LTE to the UE. The UE tunes to E-UTRAN and performs a TAU Procedure. The Target MME initiates a Session Transfer (STI) to the IMS. The IMS performs session transfer, updates the remote end, and releases the CS access leg. Finally, the MSC Server releases resources after release from the IMS.](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Target E-UTRAN + participant Target MME + participant MSC Server/MGW + participant Source MSC + participant Source SGSN + participant Source BSS + participant SGW + participant IMS (SCC AS) + + Note left of UE: UE is IMS registered over a SUSPENDED PS bearer and has an ongoing 2G CS call + UE->>Source BSS: 1. Measurement reports + Note right of Source BSS: Decision for moving the UE to LTE + Source BSS->>UE: 2. RRC Connection Release with redirection to LTE + Note left of UE: 3. UE tunes to EUTRAN + UE->>Target MME: 4. TAU Procedure + Note right of Target MME: 5. Initiation of Session Transfer (STI) + Target MME->>IMS: 5. Initiation of Session Transfer (STI) + Note right of IMS: Session transfer + Note right of IMS: Update remote end + Note right of IMS: Release of CS access leg + IMS->>MSC Server/MGW: 7. Release Resources in MSC Server after release from the IMS + +``` + +Sequence diagram for SRVCC handover from GERAN without DTM support to E-UTRAN. The diagram shows the interaction between UE, Target E-UTRAN, Target MME, MSC Server/MGW, Source MSC, Source SGSN, Source BSS, SGW, and IMS (SCC AS). The process starts with the UE sending measurement reports to the Source BSS. The Source BSS makes a decision to move the UE to LTE and sends an RRC Connection Release with redirection to LTE to the UE. The UE tunes to E-UTRAN and performs a TAU Procedure. The Target MME initiates a Session Transfer (STI) to the IMS. The IMS performs session transfer, updates the remote end, and releases the CS access leg. Finally, the MSC Server releases resources after release from the IMS. + +**Figure 6.2.2.6.1-1: SRVCC handover from GERAN without DTM support to E-UTRAN** + +At the beginning of the call flow the UE is IMS registered and all PS bearers are suspended. The source system is configured to know that the target MME/TA where the UE is moving support IMS VoIP. + +1. Based on UE measurement reports the source BSS decides to move this UE to E-UTRAN. + +**Editor's Note: How BSS determine this UE can be redirected to E-UTRAN is FFS!** + +2. Source BSS triggers RRC connection release with redirection to E-UTRAN for rSRVCC + +- 3-4. UE re-tunes to E-UTRAN radio and performs a TAU procedure as specified in TS 23.401 [5]. UE uses the Active flag in the TAU Request to MME to resume the suspended SIP signalling bearer and any other suspended non-voice bearers. The MME requests the context from the source SGSN. The MME will inform S-GW and PDN-GW(s) to resume the suspended bearers + +5. Subsequently UE initiates the Session Transfer procedure e.g. by sending a SIP INVITE (STI) message to the SCC AS. Standard IMS Service Continuity procedures are applied for execution of the Session Transfer, see TS 23.237 [4]. As part of this procedure the remote end is updated with the SDP of the IMS access leg. The downlink flow of VoIP packets is switched towards the PDN GW at this point. + +6. The IMS triggers a network-initiated dedicated bearer activation for the voice component. + +7. The IMS releases the CS access leg which result in release of resources in the MSC Server. + +##### 6.2.2.6.2 SRVCC handover from UTRAN or GERAN with PS handover support to E-UTRAN + +Depicted in Figure 6.2.2.6.2-1 is a call flow for SRVCC handover from UTRAN or GERAN with PS handover support to E-UTRAN, including the handling of the non-voice component. E-UTRAN neighbouring cells have to be configured + +in UTRAN/GERAN for the purpose of measurements. The source system is configured to know that the target MME/TA where the UE is moving support IMS VoIP. + +![Sequence diagram of SRVCC handover from UTRAN or GERAN with PS handover support to E-UTRAN. The diagram shows the interaction between UE, Target eNode B, Target MME, MSC server/MGW, Source MSC, Source SGSN, Source RNS/BSS, SGW, and IMS (SCC AS).](4b87467ad9642943235f48f7d4b59449_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Target eNode B + participant Target MME + participant MSC server/MGW + participant Source MSC + participant Source SGSN + participant Source RNS/BSS + participant SGW + participant IMS (SCC AS) + + Note left of UE: UE tunes to E-UTRAN + UE->>Source RNS/BSS: 1a-Measurement Reports + Note right of Source RNS/BSS: Decision for SRVCC with PS-HO + Source RNS/BSS->>UE: 1b-rSRVCC Session continuity trigger + UE->>IMS (SCC AS): 1c-Initiation of Session Transfer (STI) + Note right of IMS (SCC AS): Session Transfer + Source RNS/BSS->>Source SGSN: 2a-Reloc Required + Source SGSN->>Target MME: 2b-Fw Reloc Req + Target MME->>Target eNode B: 3-HO Req/Ack + Target MME->>Source SGSN: 4a-Fw Reloc Ack + Source SGSN->>Source RNS/BSS: 4b-Fw Reloc Ack + Source RNS/BSS->>UE: 5-HO Command + Note left of UE: UE tunes to E-UTRAN + UE->>Target eNode B: 6-HO to E-UTRAN complete + Target eNode B->>Target MME: 7-HO notify + Target MME->>MSC server/MGW: 8a-Fwd Reloc Complete/Ack + Note right of MSC server/MGW: 8b - Update Bearer Procedure + Note left of UE: 9 - TAU Procedure if needed + UE->>IMS (SCC AS): 10. continuing Session Continuity procedure with IMS + Note right of IMS (SCC AS): Update remote end + Note right of IMS (SCC AS): 11 - NW initiated dedicated bearer activation for the voice component + Note right of Source MSC: 12 - Release resource in MSC server after release from the IMS + +``` + +Sequence diagram of SRVCC handover from UTRAN or GERAN with PS handover support to E-UTRAN. The diagram shows the interaction between UE, Target eNode B, Target MME, MSC server/MGW, Source MSC, Source SGSN, Source RNS/BSS, SGW, and IMS (SCC AS). + +**Figure 6.2.2.6.2-1: SRVCC handover from UTRAN or GERAN with PS handover support to E-UTRAN** + +**Editor's Note: How to ensure the voice bearer switching only occur after the UE has gone to the target side is FFS.** + +1a. Based on UE measurement reports the RNS/BSS decides to trigger a SRVCC and PS handover to E-UTRAN. + +1b. Since PS bearer is active; BSS/RNS sends an indication to UE to start session transfer procedure. + +1c. UE starts the session transfer procedure with STI to IMS + +2. Source RNS initiates PS relocation. The following steps are performed: + +a) Source RNS/BSS sends a Relocation Required (Source to Target Transparent Container) message to source SGSN. + +b) Source SGSN sends a Forward Relocation Request message to the target MME including information about the non-voice component only. + +3. Target MME handles the Forward Relocation Request messages and requests resource allocation for the non-voice component only by exchanging Handover Request/Acknowledge messages with the target E-UTRAN. + +4. The target MME acknowledges the prepared PS relocation towards the source access. The following steps are performed: + +a) Target MME sends a Forward Relocation Response (Target to Source Transparent Container) message to the source SGSN. + +- b) Source SGSN sends a Relocation Required Acknowledge (Target to Source Transparent Container) message to the source RNS/BSS. +5. Source RNS/BSS receives the Relocation Required Acknowledge message for the PS HO and sends a HO Command message to the UE instructing it to perform a handover to E-UTRAN. + 6. UE re-tunes to E-UTRAN radio and sends a Handover to E-UTRAN Complete message to the E-UTRAN. + 7. Target E-UTRAN informs the target MME by sending a Handover Notify message. + 8. The target MME completes the PS relocation. The following steps are performed: + - a) Target MME exchanges Forward Relocation Complete / Acknowledge messages with the source SGSN. + - b) Target MME performs the Update bearer procedure with the Serving GW and the PDN GW. At this point the relocation of all non-voice PS bearers is completed and the user data are flowing across E-UTRAN access in both directions. + 9. UE performs a TAU procedure if required (e.g. due to UE mobility under CS coverage). + 10. UE continues the Session Transfer procedure which was started at the source side with SCC AS. As part of this procedure the remote end is updated with the SDP of the IMS access leg. The downlink flow of VoIP packets is switched towards the PDN GW at this point. This step can occur in parallel with step 9. + 11. The IMS triggers a network-initiated dedicated bearer for the voice component. + 12. The IMS releases the CS access leg which result in release of resources in the MSC Server. + +## 6.3 Solution 3+5: Media anchoring in serving network with Access Transfer Control Functionality + +### 6.3.1 Architecture Reference Model + +The architecture is in accordance to SRVCC using ATCF enhancements as specified in TS 23.237 [4]. The source MSC Server is assumed to be enhanced for rSRVCC. + +Figure 6.3.1-1 provides a further clarification of the reference architecture for rSRVCC. The figure only depicts the specific reference points for reverse SRVCC. + +![Figure 6.3.1-1: Reference Architecture for reverse SRVCC. The diagram shows a vertical stack of network elements: SCC AS at the top, connected to I/S-CSCF via ISC. I/S-CSCF is connected to ATCF* via Mw/Mx. ATCF* is connected to ATGW* via I2. Below ATCF* is MSC Server, connected via Sv. MSC Server is connected to SGSN/MME** via Sv. On the left, UE is connected to P-CSCF via Gm, and P-CSCF is connected to ATCF* via Mw/Mx. UE is also connected to CS Access, which is connected to MSC Server.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +graph TD + SCC_AS[SCC AS] -- ISC --> I_S_CSCF[I/S-CSCF] + I_S_CSCF -- Mw/Mx --> ATCF_star[ATCF*] + ATCF_star -- I2 --> ATGW_star[ATGW*] + ATCF_star -- Sv --> MSC_Server[MSC Server] + MSC_Server -- Sv --> SGSN_MME_double_star[SGSN/MME**] + UE[UE] -- Gm --> P_CSCF[P-CSCF] + P_CSCF -- Mw/Mx --> ATCF_star + UE --> CS_Access[CS Access] + CS_Access --> MSC_Server + +``` + +\*: Location of functionality depends on deployment and collocation scenario + +\*\*: Which entity has the Sv interface depends on the solution of Access Transfer Preparation + +Figure 6.3.1-1: Reference Architecture for reverse SRVCC. The diagram shows a vertical stack of network elements: SCC AS at the top, connected to I/S-CSCF via ISC. I/S-CSCF is connected to ATCF\* via Mw/Mx. ATCF\* is connected to ATGW\* via I2. Below ATCF\* is MSC Server, connected via Sv. MSC Server is connected to SGSN/MME\*\* via Sv. On the left, UE is connected to P-CSCF via Gm, and P-CSCF is connected to ATCF\* via Mw/Mx. UE is also connected to CS Access, which is connected to MSC Server. + +**Figure 6.3.1-1: Reference Architecture for reverse SRVCC.** + +NOTE 1: MSC Server and SGSN/MME shown in the figure are enhanced for reverse SRVCC. Whether SGSN, or MME, or both are enhanced depends on sub-alternatives. + +Depending on the alternative chosen for the access transfer preparation, some of the elements shown in the figure might not be impacted, see clause 6.3.2. + +No matter which alternative is chosen for the access transfer preparation, the solution proposed here does not require all MSCs in the operator's network to be upgraded for rSRVCC. Only the ones controlling location areas close to E-UTRAN/HSPA tracking / routing areas with VoIMS support would need to be upgraded. + +NOTE 2: CS calls started in location areas that are controlled by an MSC not supporting rSRVCC can not be transferred to E-UTRAN. + +For access transfer preparation alternatives 1 and 2, only the source SGSNs covering cells close to E-UTRAN/HSPA cells with VoIMS support would need to be upgraded. + +For access transfer preparation alternative 3, all source SGSNs in the operator's network would need to be upgraded. + +### 6.3.2 Functional Entities + +#### 6.3.2.1 ATCF + +The ATCF shall be based on the functionality specified in TS 23.237 [4], with the following enhancements: + +- At registration from MSC Server enhanced for rSRVCC, the ATCF includes itself to the path for future session establishments over CS and correlates the registration with the related PS registration. +- Make media anchoring decision with additional criteria of UE's reverse SRVCC capability for session setups initiated from/destined to the MSC Server enhanced for rSRVCC; +- Correlate the Session Transfer procedures initiated by the UE and the MSC Server enhanced for rSRVCC. +- If media anchoring has been made at session establishment, perform the Access Transfer and update the ATGW with the new media path for the new (PS) access leg, without requiring updating the remote leg; +- If media anchoring has not been made at session establishment, + +- Optionally anchor the call in the ATGW as part of the rSRVCC procedure by establishing the new media path between MGW and ATGW for the new (PS) access leg, +- And updating the remote leg once the UE is on the target access and performs the service continuity procedure; + +**Editor's Note 2: If the call (voice media) is not anchored in the ATGW, executing the remote leg update procedure following rSRVCC handover is required, and whether or not the performance of rSRVCC will then be acceptable is FFS.** + +#### 6.3.2.2 SCC AS + +The SCC AS shall be based on the functionality specified in TS 23.237 [4], with the following enhancements: + +- If indicated from the MSC Server enhanced for rSRVCC, the SCC AS shall notify the MSC Server enhanced for rSRVCC of the STN-SR of the ATCF when changes to this occur (i.e., during an initial IMS registration from the UE over PS access). + +#### 6.3.2.3 P-CSCF + +- If access transfer preparation alternatives 1 and 3: The P-CSCF may interact with PCRF for the preparation of the Access Transfer if informed by the ATCF. + +#### 6.3.2.4 MSC Server enhanced for reverse SRVCC + +The MSC Server enhanced for reverse SRVCC shall be based on the functionality specified in TS 23.216 [7], TS 23.292 [3], and TS 23.237 [4], with the following enhancements: + +- If an ATCF was allocated at IMS registration from the UE and decided to remain in the session paths: + - Discover the ATCF address if not already available. + - Using the ATCF as outgoing proxy when performing IMS registration. +- If access transfer preparation alternative 1: Initiate the session transfer procedure from CS to IMS; +- Initiating the CS to PS handover procedure for handover of the voice component to the target cell via the Sv interface. + +It is assumed the MSC Server supports the I2 reference point, and is capable of registering on behalf of the user to the IMS as specified in TS 23.292 [3]. + +#### 6.3.2.5 SGSN enhanced for rSRVCC + +The source SGSN shall: + +- If access transfer preparation alternatives 1 and 2: Handle the Relocation Preparation procedure requested from MSC Server enhanced for rSRVCC via Sv reference point; +- If access transfer preparation alternative 2: Perform the bearer reservation procedure for voice media in target access; +- If access transfer preparation alternative 3: Establish voice bearer without allocating radio resources for it; +- If access transfer preparation alternatives 1 and 2: Coordinating PS handover and CS to PS handover procedures when both procedures are performed. + +#### 6.3.2.6 UE enhanced for rSRVCC + +The rSRVCC UE shall: + +- Indicate to the access network and IMS that the UE is rSRVCC capable. +- Pre-allocate ports to be used for voice after an rSRVCC handover and inform the network about them OR use pre-defined ports after such a handover + +- Inform the network about supported Codecs that could be used for voice after rSRVCC handover OR use a pre-defined codec for voice after such a handover. +- If access transfer preparation alternatives 1 and 2: receive information about the voice bearer as part of the handover procedure and start using it as soon as going over to the target access. +- If access transfer preparation alternative 3: Trigger the establishment of a voice bearer to be used after rSRVCC handover after performing IMS registration. +- Re-establish the session control of the media after handover to the target access. + +#### 6.3.2.7 HSS + +The HSS shall be based on the functionality specified in TS 23.237 [4], with the following enhancements: + +- Include a rSRVCC allowed indication as part of the subscriber data. + +#### 6.3.2.8 MME/SGSN enhanced for rSRVCC + +- If handover preparation alternative 4: Handle the Relocation Preparation procedure requested from MSC Server enhanced for rSRVCC via Sv reference point; +- If handover preparation alternative 4: Retrieve PDP context related information from the source SGSN if PS-PS handover is not performed at the same time as a rSRVCC handover. +- If handover preparation alternative 4: Perform the bearer reservation procedure for voice media in target access; + +### 6.3.3 Message Flows + +#### 6.3.3.1 General principles + +This solution has the following characteristics: + +- It is assumed the MSC Server is enhanced for ICS and has an I2 interface to be able to register on behalf of the UE. +- The source RAN is capable of including E-UTRAN cells with VoIP capability into the neighbour cell list. +- The architecture reuses the eSRVCC architecture, i.e. SRVCC with ATCF enhancements. +- It is assumed that the MSC Server obtains the address of the ATCF prior registration through the ATCF. +- rSRVCC will be used for a UE if the UE is rSRVCC capable, the rSRVCC allowed indication was part of the subscriber data received from HSS, and the UE is IMS registered. +- When registering to IMS on behalf of the UE, the MSC Server will register through the ATCF if rSRVCC can be used for the UE (i.e., UE is rSRVCC capable and the subscriber has the rSRVCC allowed indication set) and if an ATCF was allocated and decided to remain in the session paths of the UE when it registered over IMS. +- If rSRVCC can be used for the UE, originating and terminating calls established over CS are routed through the ATCF as per existing IMS procedures if an ATCF was involved at registration time. The ATCF then decides whether to anchor the media or not in the ATGW. +- At a high level, the rSRVCC handover procedure is based on the following steps: + - 1) The PS bearer for the active voice session is established in the PS core network before sending the UE to the target access. + - 2) The media plane for the active voice call is switched to the target access while the UE is instructed to move to the target access, so the UE is able to receive/transmit voice as soon as it has tuned to the target access. + - 3) The control plane and the media for the held calls are switched by the UE after tuning to the target access. + +A prerequisite for the flows is that the user is registered in IMS and has at least one PS bearer (used for SIP signalling). + +#### 6.3.3.2 GERAN/UTRAN Attach procedure + +The UTRAN/GERAN Attach procedure for an rSRVCC capable UE is performed as defined in TS 23.060 [6] with the following additions: + +- The UE indicates to the network its capability to perform rSRVCC as follows: + - In case of a network of Network Mode of Operation type I: + - The "rSRVCC capability indication" is sent by the UE in the Attach Request message to the SGSN at combined GPRS/IMSI Attach, and in the Routing Area Update Request message at combined RA/LA Update. + - If received by the SGSN, the "rSRVCC capability indication" is sent to the MSC in the Location Updating Procedure. + - In case of a network of Network Mode of Operation types II or III: + - The "rSRVCC capability indication" is sent by the UE in the Attach Request message sent to the MSC. +- If the subscriber is allowed to have rSRVCC in the VPLMN, the HSS shall include the "rSRVCC allowed" indication in the Insert Subscriber Data sent to the MSC Server. + +#### 6.3.3.3 E-UTRAN attach procedure + +The E-UTRAN attach procedure for 3GPP rSRVCC UE is performed as defined in TS 23.216 [7] with the following addition: + +- rSRVCC UE includes the "rSRVCC capability indication" as part of the "MS Network Capability" in the Attach Request message and in Tracking Area Updates. +- If the subscriber is allowed to have rSRVCC in the VPLMN, the HSS shall include the "rSRVCC allowed" indication as part of the subscription data sent to the MME. + +#### 6.3.3.3a Informing the source RAN about the possibility to perform rSRVCC + +The MSC Server determines the possibility of performing rSRVCC based on: + +- The rSRVCC capability of the UE. +- The presence of the rSRVCC allowed indication in the subscription data of the user. +- The IMS registration status of the UE (i.e., if the MSC Server has registered through the ATCF). +- For access transfer preparation alternatives 1 and 2: the rSRVCC capability of the SGSN the UE is currently registered. + +The MSC Server informs the RAN about the possibility to perform rSRVCC by sending an "rSRVCC operation possible" to the RNC/BSC: + +- in the case of the Iu-CS interface: the Common ID message when the Iu Connection is setup between the MSC Server and the RNC/BSC at Attach Request, Location Area Update, at SRNS relocation, at inter-RAT handover from GERAN, +- in the case of the A interface: in the appropriate message(s) to be defined at stage 3 at attach request, location area update, at intra and inter-MSC handover, at inter-RAT handover from UTRAN. + +In case of inter-MSC handover, the rSRVCC operation possible indication shall be conveyed in the prepare HO required message sent from the anchor MSC to the target MSC. + +The RAN shall use that information for deciding the cells for which the UE shall report measurements that lead to handover request to the core network. + +#### 6.3.3.4 Codec and transport address related procedure + +##### 6.3.3.4.1 General + +For rSRVCC to work, the network needs to know the following information about the UE: + +- the IP address and port number used by the UE for receiving voice media on PS access, +- identifier of the new SGSN / old MME. + +The UE needs to reserve a port for rSRVCC. The UE needs to know the IP address, port number and codec for sending media to the ATGW (in case of media anchoring) or the remote end (in case no media anchoring took place). + +NOTE: Depending on the alternative for access transfer preparation, different network elements that need to have that information: the ATCF (alternative 1), the MSC (alternative 2), the source SGSN / old MME (alternative 3), and the target MME (alternative 4). + +##### 6.3.3.4.2 Information in IMS registration and handover procedure + +For access transfer preparation alternatives 1 and 2: The IP address of the UE is assigned by the network. When registering in the IMS, the UE can indicate its IP address, port and default codec (or list of supported codecs) it will receive media on when a transfer is performed. The MSC Server or ATCF can learn this information and if needed the address of the P-CSCF from the IMS (e.g. during IMS registration or using an event package). + +For access transfer preparation alternative 3 and 4: the codec, IP address and ports are sent from the UE to the network in the post registration IMS signaling used to pre-establish a PS voice bearer. + +#### 6.3.3.5 Establish a session over CS + +##### 6.3.3.5.1 STN-SR allocated by the ATCF and Transfer Info sent to ATCF + +When the UE performs IMS registration, the request is routed through the ATCF, since it is assumed that that ATCF is co-located with a node processing the IMS registration in the serving network, roaming if not home. The ATCF may decide to be involved in the session establishments made over IMS or not at that point, as described in TS 23.216 [7]. In case it does, and if the MSC Server (according to TS 23.292 [3], clause 7.2.1) registered the user in the IMS based on the CS attach before the UE has performed IMS registration, the MSC Server will not have the address of the ATCF when the IMS registration is performed. Therefore it is proposed to proceed as follows: + +- 1) The MSC Server performs IMS Registration according to TS 23.292 [3], clause 7.2.1 and indicates to the SCC AS that it wishes to be informed about STN-SR allocated by the ATCF in case of user registration over PS. +- 2) The UE performs IMS registration via Gm. ATCF is allocated and SCC AS is informed if the ATCF wishes to remain in the path of future session establishments (which is the case assumed in the following steps). +- 3) The SCC AS, when receiving 3rd party registration from the UE including dynamically allocated STN-SR from the ATCF and having received the indication of interest in the STN-SR by the MSC Server informs MSC Server about allocated ATCF. In the case of access transfer preparation alternative #2, the SCC AS also indicates to the MSC the IP address of the UE, the ports allocated by it, and the codecs it supports. +- 4) When receiving a new STN-SR from the SCC AS, the MSC Server performs re-registration towards the allocated ATCF (see clause 6.3.3.5.2). + +If the ATCF involves in the session made over IMS, the procedure of SCC AS providing C-MSISDN and ATU-STI to ATCF as specified in clause 6.3.1.7 of TS 23.237 [4] shall be applied. + +The dynamic STI-rSR shall be provided to the UE from the ATCF. It is left for stage 3 to decide on appropriate mean to provide the dynamic STI-rSR to the UE. + +##### 6.3.3.5.2 Registration when ATCF involved + +The CS registration is done according to TS 23.292 [3] clause 7.2.1, with the difference that the registration is routed through the ATCF. + +The scenario where the ATCF is involved in the registration path, and decides to include itself for the duration of the registration is shown in figure 6.3.3.5.2-1 below. + +![Sequence diagram for Figure 6.3.3.5.2-1: Registration from CS through ATCF. Lifelines: MSC Server, ATCF, SN | HN, SCC AS/ S-CSCF. Steps: 1. Decision to register (internal to MSC Server); 2. REGISTER from MSC Server to ATCF; 3. Decision to include ATCF in the path for rSRVCC procedures (internal to ATCF); 4. REGISTER from ATCF to SCC AS/ S-CSCF; 5. Completion of IMS registration (horizontal bar across all lifelines).](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +Sequence diagram for Figure 6.3.3.5.2-1: Registration from CS through ATCF. Lifelines: MSC Server, ATCF, SN | HN, SCC AS/ S-CSCF. Steps: 1. Decision to register (internal to MSC Server); 2. REGISTER from MSC Server to ATCF; 3. Decision to include ATCF in the path for rSRVCC procedures (internal to ATCF); 4. REGISTER from ATCF to SCC AS/ S-CSCF; 5. Completion of IMS registration (horizontal bar across all lifelines). + +**Figure 6.3.3.5.2-1: Registration from CS through ATCF** + +1. The MSC Server decides to register the UE through CS according to TS 23.292 [3]. +2. If rSRVCC can be used for the UE and if an ATCF has decided to remain in the path of session establishments when the UE registered over IMS, the MSC Server sends the REGISTER to the IMS through the ATCF (using the STN-SR that identifies the ATCF). +3. The ATCF detects that the Register is received from the MSC Server and decides to include itself for the session by adding itself in the route path. +4. The Register is forwarded towards the registrar according to TS 23.292 [3]. +5. The registration process is completed. + +When the ATCF involves in the session made over IMS, the procedure of SCC AS providing C-MSISDN and ATU-STI to ATCF as specified in clause 6.3.1.7 of TS 23.237 [4] shall be applied also for the MSC Server registration. + +##### 6.3.3.5.3 Origination procedures when ATCF involved + +The CS origination is done according to TS 23.292 [3], clause 7.3, with the difference that the call is routed through the ATCF (that was added to the call path during registration according to clause 6.3.3.5.2). + +NOTE: The call may also have been transferred to CS by an SRVCC PS to CS access transfer procedure. + +The scenario where the ATCF is involved in the call set up, and decides to anchor the media in the ATGW is shown in figure 6.3.3.5.3-1 below. + +Once the session is established, the ATCF will act as the access transfer function in the call. + +![Sequence diagram for Figure 6.3.3.5.3-1: Originating call setup over CS through ATCF. Lifelines: UE-1, MME / SGSN, MSC Server, CS-MGW, ATCF, ATGW, SN | HN, SCC AS/ S-CSCF, UE-2. Steps: 1. SETUP from UE-1 to MSC Server; 2. INVITE from MSC Server to ATCF; 3. Decide to anchor and allocate ATGW resources (dashed box between ATCF and ATGW); 4. INVITE from ATCF to SCC AS/ S-CSCF; 5. INVITE from SCC AS/ S-CSCF to UE-2; 6. Completion of originating session setup and optional anchor decision (horizontal bar across all lifelines).](dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg) + +Sequence diagram for Figure 6.3.3.5.3-1: Originating call setup over CS through ATCF. Lifelines: UE-1, MME / SGSN, MSC Server, CS-MGW, ATCF, ATGW, SN | HN, SCC AS/ S-CSCF, UE-2. Steps: 1. SETUP from UE-1 to MSC Server; 2. INVITE from MSC Server to ATCF; 3. Decide to anchor and allocate ATGW resources (dashed box between ATCF and ATGW); 4. INVITE from ATCF to SCC AS/ S-CSCF; 5. INVITE from SCC AS/ S-CSCF to UE-2; 6. Completion of originating session setup and optional anchor decision (horizontal bar across all lifelines). + +**Figure 6.3.3.5.3-1: Originating call setup over CS through ATCF** + +1. The MSC Server receives the CS setup message. +2. The MSC Server initiates an INVITE origination according to TS 23.292 [3] clause 7.3. As the ATCF is in the route, the MSC server, forwards the INVITE to the ATCF. + +3. The ATCF may decide whether to anchor the media session and allocate if needed ATGW resources to it. Anchoring criteria used could be same as for eSRVCC (see TS 23.237 [4]). +- 4-5. The call setup proceeds and is routed to the remote UE-2. +6. The call setup is completed. + +##### 6.3.3.5.4 Termination procedures when ATCF involved + +The CS termination is done according to TS 23.292 [3] clause 7.4, with the difference that the call is routed through the ATCF (that was added to the call path during registration according to clause 6.3.3.5.2). + +NOTE: The call may also have ended up in CS by an SRVCC PS to CS access transfer procedure. + +The scenario where the ATCF is involved in the call set up, and decides to anchor the media in the ATGW is shown in figure 6.3.3.5.4-1 below. + +Once the session is established, the ATCF will act as the access transfer function in the call. + +![Sequence diagram for terminating call setup over CS through ATCF. The diagram shows the interaction between UE-1, MME/SGSN, MSC Server, CS-MGW, ATCF, ATGW, SN, HN, SCC AS/S-CSCF, and UE-2. The sequence of messages is: 1. INVITE from UE-2 to SCC AS/S-CSCF; 2. INVITE from SCC AS/S-CSCF to ATCF; 3. ATCF decides to anchor and allocate ATGW resources (dashed box); 4. INVITE from ATCF to MSC Server; 5. SETUP from MSC Server to UE-1; 6. Completion of terminating session setup and optional anchor decision (spanning across all entities).](1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg) + +Sequence diagram for terminating call setup over CS through ATCF. The diagram shows the interaction between UE-1, MME/SGSN, MSC Server, CS-MGW, ATCF, ATGW, SN, HN, SCC AS/S-CSCF, and UE-2. The sequence of messages is: 1. INVITE from UE-2 to SCC AS/S-CSCF; 2. INVITE from SCC AS/S-CSCF to ATCF; 3. ATCF decides to anchor and allocate ATGW resources (dashed box); 4. INVITE from ATCF to MSC Server; 5. SETUP from MSC Server to UE-1; 6. Completion of terminating session setup and optional anchor decision (spanning across all entities). + +**Figure 6.3.3.5.4-1: Terminating call setup over CS through ATCF** + +- 1-2. UE-2 sends an INVITE towards UE-2. The call is routed towards UE-1 via ATCF as the ATCF was added in the route during registration. +3. The ATCF may decide whether to anchor the media session and allocate if needed ATGW resources to it. Anchoring criteria used could be same as for eSRVCC (see TS 23.237 [4]). +- 4-5. The call setup proceeds and is routed toward UE-1 according to TS 23.292 [3]. +6. The call setup is completed. + +#### 6.3.3.6 CS – PS Access Transfer Overview + +##### 6.3.3.6.1 Anchored in ATGW + +This clause describes the main steps of the rSRVCC procedure when using ATCF enhancements. + +The following flow assumes that the UE has indicated to both MSC and SGSN that it is rSRVCC capable. + +![Sequence diagram for CS-PS Access Transfer with media anchored in ATGW. The diagram shows the interaction between UE-1, MSC/MGW, SGSN, P-CSCF, PCRF, ATCF, ATGW, SN|HN, S-CSCF, SCC AS, and Remote end. The media path is anchored in the ATGW. The sequence of events is: 1. Trigger, 2. Access Transfer preparation, 3. UE Tunes to target, 4. IMS Session Continuity procedure.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +The diagram illustrates the sequence of operations for a CS-PS Access Transfer where media is anchored in the ATGW. The lifelines involved are UE-1, MSC/MGW, SGSN, P-CSCF, PCRF, ATCF, ATGW, SN|HN, S-CSCF, SCC AS, and Remote end. +Initially, media is split: CS-Media between UE-1 and MSC/MGW, and PS-Media from MSC/MGW through ATGW to the Remote end. +1. A 'Trigger' message is sent from the MSC/MGW to the ATCF. +2. An 'Access Transfer preparation' block involves signaling between the UE-1 and ATCF. +3. A 'UE Tunes to target' block shows the UE-1 switching to the target radio access. +After tuning, PS-Media flows from UE-1 through SGSN, P-CSCF to ATGW, and then to the Remote end. +4. An 'IMS Session Continuity procedure' block shows the transfer of session control across all entities from UE-1 to SCC AS. The media path remains anchored at the ATGW throughout the process. + +Sequence diagram for CS-PS Access Transfer with media anchored in ATGW. The diagram shows the interaction between UE-1, MSC/MGW, SGSN, P-CSCF, PCRF, ATCF, ATGW, SN|HN, S-CSCF, SCC AS, and Remote end. The media path is anchored in the ATGW. The sequence of events is: 1. Trigger, 2. Access Transfer preparation, 3. UE Tunes to target, 4. IMS Session Continuity procedure. + +**Figure 6.3.3.6.1-1: CS-PS Access Transfer – with media anchored in ATGW** + +The media paths shown in the figure assume that the media has been anchored in the ATGW at call set up. + +1. The MSC Server receives the trigger to initiate the access transfer. +2. Access Transfer preparation: This step is further detailed below in clause 6.3.3.7. +3. UE tunes to target radio access. UE sends and receives voice media over PS. +4. The access transfer is completed by moving the session control to the PS access leg. This step is further detailed below in clause 6.3.3.8. + +NOTE: After step 4, the media path is between the UE via EPC to the ATGW. + +##### 6.3.3.6.2 Not Anchored in ATGW + +![Sequence diagram for CS-PS Access Transfer without media anchored in ATGW. The diagram shows the interaction between UE-1, MSC/MGW, SGSN, P-CSCF, PCRF, ATCF, ATGW, SN|HN, S-CSCF, SCC AS, and Remote end. The media path is not anchored in the ATGW. The sequence of events is: 1. Trigger, 2. Access Transfer preparation, 3. UE Tunes to target, 4. IMS Session Continuity procedure.](dfaa8b98082261913dac00eae86b2889_img.jpg) + +This diagram illustrates the sequence of operations for a CS-PS Access Transfer where media is not anchored in the ATGW. The lifelines are the same as in the previous diagram. +Initially, CS-Media exists between UE-1 and MSC/MGW, and PS-Media flows from MSC/MGW directly to the Remote end, bypassing ATGW. +1. A 'Trigger' message is sent from the MSC/MGW to the ATCF. +2. An 'Access Transfer preparation' block involves signaling between UE-1 and ATCF. +3. A 'UE Tunes to target' block shows the UE-1 switching to the target radio access. During this phase, the media path is rerouted: PS-Media flows from UE-1 through SGSN and P-CSCF to the MSC/MGW, which then forwards it to the Remote end. +4. An 'IMS Session Continuity procedure' block shows the final transfer of session control. After this, PS-Media flows from UE-1 through SGSN, P-CSCF, and ATGW to the Remote end. + +Sequence diagram for CS-PS Access Transfer without media anchored in ATGW. The diagram shows the interaction between UE-1, MSC/MGW, SGSN, P-CSCF, PCRF, ATCF, ATGW, SN|HN, S-CSCF, SCC AS, and Remote end. The media path is not anchored in the ATGW. The sequence of events is: 1. Trigger, 2. Access Transfer preparation, 3. UE Tunes to target, 4. IMS Session Continuity procedure. + +**Figure 6.3.3.6.2-1: CS-PS Access Transfer –without media anchored in ATGW** + +The media paths shown in the figure assume that the media has not been anchored in the ATGW at call set up. + +1. The MSC Server receives the trigger to initiate the access transfer. +2. Access Transfer preparation: This step is further detailed below in clause 6.3.3.7. + +3. UE tunes to target radio access. UE sends and receives voice media over PS. +4. The access transfer is completed by moving the session control to the PS access leg. This step is further detailed below in clause 6.3.3.8. + +#### 6.3.3.7 Access Transfer Preparation + +##### 6.3.3.7.1 Access Transfer Preparation Alternative 1 + +The more detailed procedures of the Access Transfer Preparation step are shown in the following figure. In this alternative, the source MSC Server together with the ATCF interacts with the P-CSCF to initiate the voice bearer setup. The address of the P-CSCF is known to the ATCF from the IMS registration of the UE, and the ATCF address is known to the MSC Server from the STN-SR. It is also assumed that PCC is used. + +![Sequence diagram for Access Transfer Preparation Alternative 1. The diagram shows the interaction between UE-1, BSC/RNC, NB/eNB, MSC Server, Source SGSN, SGW/PGW, PCRF, ATCF, P-CSCF, and Target MME. The sequence of messages is: 1. HO required (BSC/RNC to MSC Server); 2. CS to PS HO request (MSC Server to Source SGSN); 3. Access Transfer Notification (MSC Server to ATCF); 4. ATN (ATCF to P-CSCF); 5. Resource allocation (P-CSCF to ATCF); 6. Bearer setup (ATCF to Source SGSN); 7. Relocation request (Source SGSN to Target MME); 8. Allocate resources (Target MME to NB/eNB); 9. Relocation response (Target MME to Source SGSN); 10. CS to PS HO response (Source SGSN to MSC Server); 11. CS to PS HO command (MSC Server to UE-1); 12. Access Transfer Preparation request (MSC Server to ATCF).](8658cfab6a458b4a80ab2e384c61ff89_img.jpg) + +``` + +sequenceDiagram + participant UE-1 + participant BSC/RNC + participant NB/eNB + participant MSC Server + participant Source SGSN + participant SGW/PGW + participant PCRF + participant ATCF + participant P-CSCF + participant Target MME + + Note right of Source SGSN: 6. Bearer setup + + BSC/RNC->>MSC Server: 1. HO required + MSC Server->>Source SGSN: 2. CS to PS HO request + MSC Server->>ATCF: 3. Access Transfer Notification + ATCF->>P-CSCF: 4. ATN + P-CSCF->>ATCF: 5. Resource allocation + ATCF->>Source SGSN: 6. Bearer setup + Source SGSN->>Target MME: 7. Relocation request + Target MME->>NB/eNB: 8. Allocate resources + Target MME->>Source SGSN: 9. Relocation response + Source SGSN->>MSC Server: 10. CS to PS HO response + MSC Server->>UE-1: 11. CS to PS HO command + MSC Server->>ATCF: 12. Access Transfer Preparation request + +``` + +Sequence diagram for Access Transfer Preparation Alternative 1. The diagram shows the interaction between UE-1, BSC/RNC, NB/eNB, MSC Server, Source SGSN, SGW/PGW, PCRF, ATCF, P-CSCF, and Target MME. The sequence of messages is: 1. HO required (BSC/RNC to MSC Server); 2. CS to PS HO request (MSC Server to Source SGSN); 3. Access Transfer Notification (MSC Server to ATCF); 4. ATN (ATCF to P-CSCF); 5. Resource allocation (P-CSCF to ATCF); 6. Bearer setup (ATCF to Source SGSN); 7. Relocation request (Source SGSN to Target MME); 8. Allocate resources (Target MME to NB/eNB); 9. Relocation response (Target MME to Source SGSN); 10. CS to PS HO response (Source SGSN to MSC Server); 11. CS to PS HO command (MSC Server to UE-1); 12. Access Transfer Preparation request (MSC Server to ATCF). + +**Figure 6.3.3.7.1-1: Access Transfer Preparation Alternative 1** + +1. The RNC/BSC sends a HO required to the MSC Server including an indication this HO is for SRVCC. If the MSC Server is the target MSC, it forwards the HO required to the anchor MSC Server. + +NOTE 1: If the UE is active in PS domain, the RNC/BSC sends also a Relocation Required message to source SGSN. If the Relocation Required message for PS HO arrives first and the message indicates CS to PS HO is initiated, the source SGSN waits for the CS to PS HO request before performing inter-RAT handover procedure. + +2. The MSC Server sends a SRVCC CS to PS HO command to the Source SGSN / old MME. The IMSI should be included in the message to allow the source SGSN/MME to identify UE. +3. The MSC Server sends an Access Transfer Notification to the ATCF, e.g. a SIP re-INVITE or INVITE message, which indicates the ATCF that it should prepare for the transfer of media to PS. +4. The ATCF retrieves the ports/codecs received from the UE in its IMS registration (The MSC is able to correlate the IMS registration made by the UE and the one made by the MSC on behalf of the UE for instance based on the C-MSISDN or on the IMEI derived instance-id used by both those registrations). The ATCF allocates media ports on the ATGW, then forwards the Transfer Preparation Request to the P-CSCF after including in that message the IP address/ports the UE intends to use after rSRVCC, as well as the IP address/ports the ATGW is sending voice media to (i.e. the SDP for both UE and ATGW will be included in the message). +5. The P-CSCF interacts with the PCRF to establish a voice bearer for the session being transferred using the information received from the ATCF in the Transfer Preparation Request message. The PCC indicates that this bearer establishment is due to rSRVCC. + +NOTE 2: The Transfer Preparation Request message could e.g., be implemented using a INVITE or other appropriate message. It is left for stage 3 to decide on appropriate message. + +6. The PCRF initiates the bearer setup towards P-GW and indicates that this bearer establishment is due to rSRVCC. Once the bearer setup reaches source SGSN / old MME, the SGSN / MME associates the new bearer with the HO CS to PS request that was received previously. The source SGSN / old MME will handle the bearer setup locally, without requiring a full reservation at the source side of the voice bearer. + +NOTE 3: If ISR is activated and the Serving GW does not have a downlink S1-U, the Serving GW sends Downlink Data Notification to the MME and the SGSN before sending the Update Bearer Request message with an indication that this is due to rSRVCC. The serving PS node that received the CS to PS HO request from the MSC will then answer to it with a Modify Bearer Request, without paging the UE. The SGW will answer that message without propagating it to the PGW. + +7. Source SGSN / old MME sends a relocation request to the target SGSN/MME. +8. Target SGSN/MME allocates resources in UTRAN/E-UTRAN. +9. A relocation response is returned to the Source SGSN/ old MME. +10. A SRVCC CS to PS HO response is returned from the Source SGSN/ old MME to the MSC Server. The SGSN also includes in that message the EPS bearer information. +11. MSC Server sends HO required Ack to the RAN, possibly via the target MSC, and the RAN send HO command to UE, indicating CS to PS handover. The MSC Server also includes in that message the EPS bearer information as well as the IP address/ports and selected codec for the ATGW, for the MGW or for the remote end depending on the situation. +12. In case of ATCF with media anchored in ATGW, the MSC Server sends an Access Transfer Preparation Request, e.g. a SIP re-INVITE or PRACK message, to the ATCF to trigger the ATCF/ATGW to have the media path switched to the IP address/port of the UE on the target access. + +In case of without media anchored in ATGW, MSC Server sends an Access Transfer Preparation Request to ATCF and the media path between ATCF/ATGW and the MSC Server/MGW is to be established. + +Editor's Note 1: The responsibility to release the voice bearer in error cases during this procedure are FFS. + +Editor's Note 2: It is FFS how to resume suspended PS bearers after UE tunes to target access, e.g. UE handover from GERAN not supporting DTM. + +##### 6.3.3.7.2 Access Transfer Preparation Alternative 2 + +The more detailed procedures of the Access Transfer Preparation step are shown in the following figure. In this alternative, the source SGSN initiates the voice bearer setup. + +Editor's Note 1: The role of the target MSC in this solution is FFS. + +![Sequence diagram for Access Transfer Preparation – Alternative 2. Lifelines: UE, Source RNS/BSS, MSC server/MGW, Source SGSN, SGW, PGW, Target MME/SGSN, Target eNB/Node B. The sequence shows the preparation for an rSRVCC handover, including bearer resource commands, PCC interaction, and access transfer preparation requests.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source RNS/BSS + participant MSC server/MGW + participant Source SGSN + participant SGW + participant PGW + participant Target MME/SGSN + participant Target eNB/Node B + + Note left of UE: Error! No + Note right of UE: Error! No text of specified style in + + Source RNS/BSS->>MSC server/MGW: 1- Relocation Request/HO required + MSC server/MGW->>Source SGSN: 2- CS to PS HO Request + Source SGSN->>SGW: 3a- Bearer Resource Command + SGW->>PGW: 3b- Bearer Resource Command + Note right of PGW: 3c- PCC interaction + PGW->>SGW: 3d- Create Bearer Request + SGW->>Source SGSN: 3e- Create Bearer Request + Source SGSN->>PGW: 3f- Create Bearer Response + PGW->>SGW: 3g- Create Bearer Response + Source SGSN->>Target MME/SGSN: 4- Fwd Relocation Request + Target MME/SGSN->>Target eNB/Node B: 5- HO Request + Target eNB/Node B->>Target MME/SGSN: 6- HO Ack + Target MME/SGSN->>Source SGSN: 7- Fwd Relocation Resp. + Source SGSN->>MSC server/MGW: 8a- CS to PS HO Resp + MSC server/MGW->>Target eNB/Node B: 8b- Access Transfer Preparation request + MSC server/MGW->>Source RNS/BSS: 8c- Reloc. Cmd/HO req. Ack + Source RNS/BSS->>UE: 9- HO Command + Target eNB/Node B->>UE: 10- HO complete + Target eNB/Node B->>Target MME/SGSN: 11- HO Notify + Note right of PGW: 12- Bearer Modification + +``` + +Sequence diagram for Access Transfer Preparation – Alternative 2. Lifelines: UE, Source RNS/BSS, MSC server/MGW, Source SGSN, SGW, PGW, Target MME/SGSN, Target eNB/Node B. The sequence shows the preparation for an rSRVCC handover, including bearer resource commands, PCC interaction, and access transfer preparation requests. + +**Figure 6.3.3.7.2-1: Access Transfer Preparation – Alternative 2** + +1. The RNS/BSS decides that an rSRVCC handover should take place. It therefore sends a Relocation Required (case of the Iu interface), or a Handover Required (in the case of the A interface) to the MSC. That message includes an indication that an rSRVCC handover is requested. +2. The MSC Server forwards the rSRVCC request to the source SGSN or the source MME according to what it stored as "serving PS node" for the UE, in a CS to PS HO Request. That message includes the transport address provided by the UE (see also clause 6.3.3.4), as well as the address it is sending voice media to (e.g. the transport address of the ATGW or of the remote end). It also includes information related to the pre-agreed codec for voice. In addition, the IMSI should be also included to allow the source SGSN/MME to identify UE. +- 3a. When receiving that message, the SGSN/MME sends a Bearer Resource Command to the SGW, to trigger the set up the PS voice bearer. The Traffic Aggregate Description (TAD) includes transport address information for both ends of the future packet voice access leg i.e. information provided by both UE and MGW. The requested QoS corresponds to the QoS of a packet voice bearer and may take into account the codec information. +- 3b. The SGW forwards the Bearer Resource Command to the PGW. +- 3c. The PGW interacts with the PCRF in case dynamic PCC is deployed. + +- 3d. The PGW initiates (either based on the response of the PCRF in case of dynamic PCC, or as its own decision) the creation of the bearer, by sending a Create Bearer Request to the SGW. The message includes the essential EPS bearer information i.e. the TFT (compiled from TAD information) and the QoS of the future EPS bearer supporting packet voice on E-UTRAN side, with the exception of the EPS Bearer ID/NSAPI, which is assigned later. The message may also include the IP address assigned to the UE in order to cope with some cases when the SGSN/MME is not aware of it. + - 3e. The SGW forwards the Create Bearer Request to the Source SGSN / Source MME. The message includes the essential EPS bearer information, with the exception of the EPS Bearer ID/NSAPI, which is assigned later. The message may also include the IP address assigned to the UE in order to cope with some cases when the SGSN is not aware of it. + - 3f. The source SGSN / source MME assigns the EPS Bearer ID/NSAPI for the future packet voice bearer, and replies with a Create Bearer Response to the SGW. It does not request the RNS/BSS to allocate any radio resources for that bearer. + - 3g. The SGW sends a Create Bearer Response to the PGW, which finalizes the voice bearer creation. + 4. When step 3f has occurred, the Source SGSN / source MME sends a Forward Relocation Request to the Target MME/SGSN. The message includes bearer context for all bearers, including the future packet voice bearer. + - 5-6. The Target MME/SGSN requests the Target eNodeB/NodeB to allocate resources for all bearers (including the voice bearer). The Target eNode B/Node B answers, including the transparent container destined to the UE. + 7. The Target MME/SGSN answers to the Source SGSN / source MME, indicating that the resources have been allocated in the Target eNodeB/Node B. + - 8a. The source SGSN / source MME answers to MSC Server in a CS to PS HO Response indicating the success of the procedure. The essential EPS bearer information the UE will use for voice after rSRVCC handover and UE's IP address is included in that message. + - 8b. When receiving that message, in case of ATCF with media anchored in ATGW, the MSC Server sends an Access Transfer Preparation Request, e.g. a SIP re-INVITE or INVITE message, to the ATCF to have the media path switched to the transport address of the UE on the target access. That step could also occur anytime after step 2. +- In case of without media anchored in ATGW, MSC Server sends an Access Transfer Preparation Request to ATCF and the media path between ATCF / ATGW and the MSC Server / MGW is to be established. +- 8c. The MSC Server sends a Relocation Command to the Source RNS/BSS. This message also includes the EPS bearer information as well as the IP address/ports and selected codec for the ATGW, for the MGW or for the remote end depending on the situation. + 9. When receiving the Relocation Command from the MSC Server, the source BSS/RNS sends a HO Command to the UE. This message also includes the EPS bearer information as well as the IP address/ports and selected codec for the ATGW, for the MGW or for the remote end depending on the situation. + 10. The UE returns to the target access (E-UTRAN/HSPA). The UE sets up locally a PS voice bearer using the NAS information received from the network in the HO Command of step 9. As a result of that message, the UE also resumes the other existing PS bearers in case those were suspended. The UE sends a HO Complete message to the Target eNB/Node B. It starts sending and receiving voice using the PS voice bearer. + 11. When receiving that message from the UE, the target eNode B/Node B sends a Handover Notify to the target MME/SGSN. + 12. The target MME/SGSN performs the bearer modification procedure towards the SGW/PGW, effectively completing the EPS-level handover procedure. Note that in case the PS bearers were suspended, they are resumed in the SGW/PGW as an implicit result of the bearer modification procedure. + +##### 6.3.3.7.3 Access Transfer Preparation Alternative 3 + +The more detailed procedures of the Access Transfer Preparation step are shown in the following figure. This alternative is based on the Alternative 1, the difference is the UE and ATCF negotiate the codec by standard SDP offer/answer procedure prior to the CS call, e.g. immediately after the IMS registration. At the same time, also the voice media bearer (QCI=1) is reserved from the source RAT, but the media flow is not activated. For this reason, unlike in + +Alternative 1, the transfer preparation for the voice media bearer is not needed between MSC Server – ATCF – P-CSCF – PCRF, which makes the transfer phase less complex and speeds up the procedure. On the downside, this alternative requires more resources from the VPLMN; besides to the SIP and media resources from ATCF, also suspended QCI=1 bearer is reserved for all UEs with rSRVCC capability. + +Only the differences to the Alternative 1 are highlighted below. + +![Sequence diagram for Access Transfer Preparation Alternative 3. The diagram shows interactions between UE-1, BSC/RNC, NB/eNB, MSC Server, Source SGSN/Source MME, SGW/PGW, PCRF, ATCF, P-CSCF, and Target MME. The process starts with '1. codec negotiation and bearer reservation' between UE-1 and P-CSCF. Then '2. Resource allocation' from P-CSCF to PCRF. '3. HO required' from NB/eNB to MSC Server. '4. CS to PS HO request' from MSC Server to Source SGSN/Source MME. '5. Relocation request' from Source SGSN/Source MME to Target MME. '6. Allocate resources' from Target MME to SGW/PGW. '7. Relocation response' from SGW/PGW to Source SGSN/Source MME. '8. CS to PS HO response' from Source SGSN/Source MME to MSC Server. '9. CS to PS HO command' from MSC Server to NB/eNB. '10. re-INVITE (update media path)' from Source SGSN/Source MME to ATCF. '11. TPR' from ATCF to P-CSCF. '12. Handover Complete' from NB/eNB to UE-1. '13. Handover Notify' from SGW/PGW to Target MME. Finally, '14. bearer modification' between Target MME and SGW/PGW.](382a9c9e4816bd229191ab4591424dd8_img.jpg) + +Sequence diagram for Access Transfer Preparation Alternative 3. The diagram shows interactions between UE-1, BSC/RNC, NB/eNB, MSC Server, Source SGSN/Source MME, SGW/PGW, PCRF, ATCF, P-CSCF, and Target MME. The process starts with '1. codec negotiation and bearer reservation' between UE-1 and P-CSCF. Then '2. Resource allocation' from P-CSCF to PCRF. '3. HO required' from NB/eNB to MSC Server. '4. CS to PS HO request' from MSC Server to Source SGSN/Source MME. '5. Relocation request' from Source SGSN/Source MME to Target MME. '6. Allocate resources' from Target MME to SGW/PGW. '7. Relocation response' from SGW/PGW to Source SGSN/Source MME. '8. CS to PS HO response' from Source SGSN/Source MME to MSC Server. '9. CS to PS HO command' from MSC Server to NB/eNB. '10. re-INVITE (update media path)' from Source SGSN/Source MME to ATCF. '11. TPR' from ATCF to P-CSCF. '12. Handover Complete' from NB/eNB to UE-1. '13. Handover Notify' from SGW/PGW to Target MME. Finally, '14. bearer modification' between Target MME and SGW/PGW. + +**Figure 6.3.3.7.3-1: Access Transfer Preparation Alternative 3** + +**Editor's Note: The role of the target MSC in this solution is FFS.** + +1. After the IMS registration or after successful rSRVCC handover, the UE negotiates the voice codec with the ATCF (via P-CSCF) using the standard SDP offer / answer procedure. Also the IP address and port number for the RTP voice media is negotiated at the same time. UE may use e.g. a preconfigured PSI to send the SDP offer in INVITE to the ATCF. Or alternatively, the UE may learn the PSI during the IMS registration. A special indicator may be set by UE or ATCF to indicate that this media reservation is only for the rSRVCC preparation. Note that only the IP address and port allocated by the local UE for voice after rSRVCC are used for establishing the pre-establishing the voice bearer in the network. + +NOTE 1: when SRVCC takes place, the source MME/SGSN does not split the suspended QCI=1 bearer from the other PS bearers, but hands it over together with the other PS bearers. The non suspended QCI=1 bearers are released as per the current SRVCC procedures. + +2. P-CSCF reserves the bearer for voice media (QCI=1) using the standard PCC procedures. A special media authorization rules can be used to authorize the QCI=1 bearer at PCRF even though the source RAT does not support GBR bearers, or there is no sufficient bandwidth available. The media flow is not activated at this point and the QCI=1 bearer is marked as suspended. +3. CS call is established as described elsewhere in this solution. + +When the rSRVCC occurs, the RNC/BSC sends a HO required to the MSC Server including an indication this HO is for rSRVCC. Since the PS bearers are suspended, no HO required is send by RAN to the source SGSN. + +4. The MSC Server sends a SRVCC CS to PS HO command to the Source SGSN or the source MME according to what it stored as "serving PS node" for the UE. +5. Source SGSN / source MME sends a relocation request to the target SGSN/MME. That message includes an indicator that the pre-established voice bearer status shall become active. + +6. Target SGSN/MME allocates resources in UTRAN/E-UTRAN. +7. A relocation response is returned to the Source SGSN / source MME. +8. A SRVCC CS to PS HO response is returned from the Source SGSN / source MME to the MSC Server. +9. MSC sends HO required Ack to the RAN and the RAN send HO command to UE, indicating CS to PS handover. There is no need to add the coded information to the HO command, as the codec was negotiated prior to the SRVCC. The HO Command message includes the EPS bearer information related to the pre-established PS voice bearer, as well as the transport address of either the ATGW or the remote end. +10. In case of ATCF with media anchored in ATGW, the MSC Server sends a re-INVITE to the ATCF to trigger the ATCF/ATGW to have the media path switched to the IP address/port of the UE on the target access. + +In case of without media anchored in ATGW, MSC Server sends a re-INVITE or INVITE to ATCF and the media path between ATCF/ATGW and the MSC Server/MGW is to be established. + +11. ATCF is aware of the voice codec, IP address and port number which were negotiated with the UE prior to the SRVCC. Depending on the selected voice codec and the codec used in the ongoing session between ATCF and remote end, the ATCF/ATGW may begin to perform transcoding. + +**Editor's Note: The responsibility to release the voice bearer in error cases during this procedure are FFS.** + +NOTE 2: The MGW can for a certain period of time send media both on the source access leg and the new target access leg to minimize the interruption delay further. + +12. The UE sends a Handover Complete message on the target RAN when it has successfully performed the handover. +13. The target RAN notifies the target MME/SGSN of the successful handover. +14. The target MME/SGSN initiates the Modify Bearer procedure, including an indicator that the suspended voice bearer now needs to be activated. + +**NOTE 3: when the IMS session continuity procedure takes place, the TFT of the PS voice bearer will be modified to take into account the transport address used by the ATGW or by the remote end.** + +##### 6.3.3.7.4 Access Transfer Preparation Alternative 4 + +This alternative is similar with the Alternative 3 that UE and ATCF negotiate the codec, IP address, and port number for the RTP media by standard IMS session setup procedure prior to rSRVCC, e.g. sending an INVITE request immediately after the IMS registration. The major difference is that, in this alternative, MSC Server sends CS to PS handover request to target MME/SGSN instead of serving PS node. + +The SDP offer in the INVITE request indicates to reserve a non-GBR voice media bearer (e.g. QCI=7) from the source RAT, e.g. by using "b=AS:0" line. The radio resource of the non-GBR voice media bearer will be released by source RAN in seconds. + +After triggered to perform rSRVCC procedure, the MSC Server sends CS to PS handover request to target MME/SGSN via Sv interface, the target MME/SGSN may query PDP contexts/connections from source SGSN / old MME before performing standard PS-PS handover procedure. + +The target MME/SGSN shall synchronize PS HO and CS to PS HO based on the IMSI and the rSRVCC HO indication sent from RNC/BSS to MSC Server/SGSN. The rSRVCC HO indication shows whether CS to PS HO is triggered or CS+PS to PS HO is triggered. + +After UE tunes to target access network, UE can transfer voice media data using the non-GBR voice bearer temporarily. After UE complete the IMS Session Continuity procedure as described in clause 6.3.3.8, UE can transfer voice media data using new created GBR voice bearer (QCI=1) bearer. + +Figure 6.3.3.7.4-1 shows an example of the solution when ATCF is involved in the IMS registration made by UE: + +![Sequence diagram for Access Transfer Preparation Alternative 4. The diagram shows interactions between UE-1, BSC/RNC, NB/eNB, MSC Server, Source SGSN/Source MME, SGW/PGW, PCRF, ATCF, P-CSCF, and Target MME. It is divided into 'Procedures prior to rSRVCC' and 'Procedures for Access Transfer Preparation'. Step 1 involves IMS session setup negotiation. Step 2 involves resource allocation and non-GBR bearer activation. Step 3 is a measurement report. Step 4 is an HO/Reloc required message. Step 5 is a CS to PS HO request. Step 6 is a sync between PS and CS HO. Step 7 is resource allocation. Step 8 is a CS to PS HO response. Step 9 is an access transfer preparation request. Step 10 is an HO/Reloc command. Step 11 is a CS to PS HO command. Step 12 is an HO complete and notify sequence.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +Sequence diagram for Access Transfer Preparation Alternative 4. The diagram shows interactions between UE-1, BSC/RNC, NB/eNB, MSC Server, Source SGSN/Source MME, SGW/PGW, PCRF, ATCF, P-CSCF, and Target MME. It is divided into 'Procedures prior to rSRVCC' and 'Procedures for Access Transfer Preparation'. Step 1 involves IMS session setup negotiation. Step 2 involves resource allocation and non-GBR bearer activation. Step 3 is a measurement report. Step 4 is an HO/Reloc required message. Step 5 is a CS to PS HO request. Step 6 is a sync between PS and CS HO. Step 7 is resource allocation. Step 8 is a CS to PS HO response. Step 9 is an access transfer preparation request. Step 10 is an HO/Reloc command. Step 11 is a CS to PS HO command. Step 12 is an HO complete and notify sequence. + +**Figure 6.3.3.7.4-1: Access Transfer Preparation Alternative 4** + +Following step 1 and 2 are procedures prior to rSRVCC: + +- After the IMS registration, UE negotiates the voice codec, IP address, and port number for the RTP voice media with the ATCF (via P-CSCF) using the standard IMS session setup procedure, e.g. sending an SIP INVITE request. UE uses STI-rSR to send the SDP offer in a SIP INVITE request to the SCC AS via the ATCF, and uses "b=AS:0" in SDP offer to indicate the bearer reservation and session setup for rSRVCC. As bandwidth is zero, the ATGW will not handle the uplink traffic if sent by UE fraudulently. The ATCF forwards it to SCC AS immediately. When ATCF and SCC AS receives a SDP offer in a SIP INVITE with valid zero bandwidth voice media, then, if the SIP INVITE is destined to the STI-rSR, it responses with "b=AS:0" in the SDP answer, otherwise reject it. +- P-CSCF reserves the bearer for voice media using the standard PCC procedures. Knowing from the zero bandwidth for voice media, the PCRF reserves a non-GBR voice media bearer (e.g. QCI=7). + +Following steps are procedures for Access Transfer Preparation: + +- UE sends Measurement Report message. +- Source RNC/BSS knows that UE is able to perform rSRVCC as described in clause 6.3.3.3a, and determines to trigger rSRVCC procedure. The following steps are performed: + - If UE is active in PS domain, and UTRAN supports PS HO or GERAN support DTM HO, source RNC/BSS sends Handover/Relocation Required message with rSRVCC HO indication to source SGSN. The rSRVCC + +HO indication can use e.g. new defined values of "CS to PS relocation triggered" and "CS+PS to PS relocation triggered" for Cause IE. The Cause IE is transparent to source SGSN for Inter-RAT handover. + +- b) In parallel with step a), source RNC/BSS sends Handover/Relocation Required (rSRVCC HO) message to anchor MSC Server. +5. Target MME/SGSN handles handover request from PS domain and CS domain as follows: +- a) Receives the CS to PS handover request (rSRVCC HO, serving PS node info, IMSI) from MSC Server enhanced for rSRVCC. The "serving PS node info" is obtained according to clause 6.3.3.9. + - b) If PS HO is not triggered, sends Context Request to source SGSN / old MME and receives the response. + - c) If PS HO is triggered, wait for receiving the Forward Relocation Request (rSRVCC HO, IMSI) from source SGSN. The rSRVCC HO is received from source RNC/BSS and transparently forwarded by the source SGSN. +6. Target MME/SGSN synchronizes PS handover and CS to PS handover based on the rSRVCC HO indication and IMSI. The rSRVCC HO also indicates whether PS HO is triggered or not. +7. Target MME/SGSN allocates resources from target eNB/RNC. +8. If resource allocation is done, target MME/SGSN finishes the handover preparation procedure. The following steps are performed: +- a) Target MME/SGSN sends CS to PS handover response to MSC Server enhanced for rSRVCC. When resource allocation fails, the target MME/SGSN shall send a reject indication to the MSC Server. + - b) In parallel with step a), if PS handover is triggered, target MME/SGSN sends Forward Relocation Response to source SGSN. +9. MSC Server enhanced for rSRVCC handles the CS to PS handover response as follows: +- a) Sends Access Transfer Preparation request (C-MSISDN, STN-SR) to the ATCF, e.g. by using SIP INVITE request. In case of media path anchored in ATGW, if transcoding is needed, the media path between ATCF/ATGW and the MSC Server/MGW may be established by ATCF to make the MSC Server/MGW performing transcoding. + +The ATCF interacts with ATGW to reserve the resources, have the media path switched, and start voice data transfer for the session established at step 1. + +- b) In parallel with step a), sends Handover/Relocation Command to source RNC/BSS. +10. If PS HO is triggered, after step 8c, source SGSN sends Handover/Relocation Command message to source RNC/BSS. +11. Source RNC/BSS sends Handover from UTRAN/GERAN Command message to UE, indicating CS to PS handover, e.g. by including RAB info to remove IE that contains the CS RAB information. There is no need to add the codec and NAS information (e.g. TFT, EPS bearer ID, etc) to the HO from UTRAN/GERAN Command, as the codec and NAS information was negotiated prior to the rSRVCC. + +NOTE: After UE tunes to E-UTRAN, to minimize the interruption delay, it can use the non-GBR voice media bearer to continue to transfer voice data until a GBR voice media bearer (QCI=1) for the session has been created. + +12. UE tunes to LTE/HSPA, and following steps are performed: + +- a) UE sends Handover complete message to target eNB/RNC, the UE also resumes the existing PS bearers in case those were suspended. +- b) Target eNB/RNC sends Handover Notify message to target MME/SGSN. +- c) If PS HO is not triggered, target MME/SGSN sends Context Acknowledge to source SGSN / old MME. When resource allocation fails or UE fails to camp on E-UTRAN/HSPA, the target MME/SGSN shall send a reject indication to the source SGSN / old MME, e.g. by using "no resource available" or "system failure" cause value. + +- d) Target MME/SGSN performs bearer modification procedure towards the SGW/PGW, effectively completing the EPS-level handover procedure. Note that in case the PS bearers were suspended, they are resumed in the SGW/PGW as an implicit result of the bearer modification procedure. + +Editor's note: It is FFS what if UE fails to establish QCI=1 bearer after tunes to target access, e.g. due to lack of radio resources. + +##### 6.3.3.7.5 Access Transfer Preparation Alternative 5 (the combination) + +The more detailed procedures of the Access Transfer Preparation steps are shown in the following figure. + +![Sequence diagram for Access Transfer Preparation Alternative 5, non-DTM case. The diagram shows the interaction between UE-1, BSC/RNC, NB/eNB, MSC Server, Source SGSN, SGW/PGW, PCRF, ATCF, P-CSCF, and Target MME. The sequence starts with the BSC/RNC sending an 'HO required' message to the MSC Server. The MSC Server then sends a 'CS to PS HO request' to the Target MME. The Target MME sends an 'Access Transfer Notification' to the ATCF. The ATCF sends a 'Context Request' to the Source SGSN, which responds with a 'Context Response'. The Target MME then sends an 'Allocate resources' message to the MSC Server. The MSC Server sends a 'CS to PS HO response' to the Target MME. The Target MME sends a 'CS to PS HO command' to the BSC/RNC, which in turn sends a 'CS to PS HO command' to the NB/eNB. The NB/eNB sends a 'CS to PS HO confirmation' to the BSC/RNC, which then sends it to the UE-1. The MSC Server sends an 'Access Transfer Preparation request' to the ATCF. The ATCF sends a 'Handover Notify' to the Target MME. The Target MME sends a 'Modify bearers' message to the SGW/PGW. The SGW/PGW sends a 'Context Request ACK' to the Source SGSN. The Source SGSN sends a 'Voice over default bearer user plane' message to the UE-1. The UE-1 then performs a 'Session continuity procedure (clause 6.3.3.8)'. The UE-1 then performs a 'Bearer setup'. Finally, the UE-1 sends a 'Voice over dedicated bearer user plane' message to the SGW/PGW.](43979979715bb3304389a0cb18f34444_img.jpg) + +Sequence diagram for Access Transfer Preparation Alternative 5, non-DTM case. The diagram shows the interaction between UE-1, BSC/RNC, NB/eNB, MSC Server, Source SGSN, SGW/PGW, PCRF, ATCF, P-CSCF, and Target MME. The sequence starts with the BSC/RNC sending an 'HO required' message to the MSC Server. The MSC Server then sends a 'CS to PS HO request' to the Target MME. The Target MME sends an 'Access Transfer Notification' to the ATCF. The ATCF sends a 'Context Request' to the Source SGSN, which responds with a 'Context Response'. The Target MME then sends an 'Allocate resources' message to the MSC Server. The MSC Server sends a 'CS to PS HO response' to the Target MME. The Target MME sends a 'CS to PS HO command' to the BSC/RNC, which in turn sends a 'CS to PS HO command' to the NB/eNB. The NB/eNB sends a 'CS to PS HO confirmation' to the BSC/RNC, which then sends it to the UE-1. The MSC Server sends an 'Access Transfer Preparation request' to the ATCF. The ATCF sends a 'Handover Notify' to the Target MME. The Target MME sends a 'Modify bearers' message to the SGW/PGW. The SGW/PGW sends a 'Context Request ACK' to the Source SGSN. The Source SGSN sends a 'Voice over default bearer user plane' message to the UE-1. The UE-1 then performs a 'Session continuity procedure (clause 6.3.3.8)'. The UE-1 then performs a 'Bearer setup'. Finally, the UE-1 sends a 'Voice over dedicated bearer user plane' message to the SGW/PGW. + +Figure 6.3.3.7.5-1: Access Transfer Preparation Alternative 5, non-DTM case + +- The RNC/BSC sends a HO required to the MSC Server including an indication this HO is for rSRVCC. If the MSC Server is the target MSC, it forwards the HO required to the anchor MSC Server. +- The MSC Server sends a SRVCC CS to PS HO request to the Target MME. If required, the IMSI is provided for identifying the UE. +- The MSC Server sends an Access Transfer Notification to the ATCF, e.g. a SIP re-INVITE or INVITE message, which indicates the ATCF that it should prepare for the transfer of media to PS. The ATCF allocates media ports on the ATGW. The media ports and codecs allocated by the ATCF are provided to the MSC Server in the response message. This step is independent of step 2. + +NOTE 1: The ATCF retrieves the ports/codecs received from the UE in its IMS registration. The ATCF is able to correlate the IMS registration made by the UE and the one made by the MSC Server on behalf of the UE for instance based on the C-MSISDN or on the IMEI derived instance-id used by both those registrations. + +NOTE 2: The Access Transfer Notification message could e.g., be implemented using an INVITE or other appropriate message. It is left for stage 3 to decide on appropriate message. + +- If the MME has no UE context it sends Context Request using P-TMSI and RAI to find the old SGSN. +- The SGSN responds with Context Response message including all UE contexts. +- Target MME allocates resources in E-UTRAN. +- A SRVCC CS to PS HO response is returned from the target MME to the MSC Server. + +8. MSC Server sends HO required Ack to the RAN, possibly via the target MSC, and the RAN send HO command to UE, indicating CS to PS handover. The MSC Server also includes in that message the IP address/ports and selected codec for the ATGW. +9. In case of ATCF with media anchored in ATGW, the MSC Server sends an Access Transfer Preparation Request, e.g. a SIP re-INVITE or PRACK message, to the ATCF to trigger the ATCF/ATGW to have the media path switched to the IP address/port of the UE on the target access. + +In case of ATCF without media anchored in ATGW, MSC Server sends an Access Transfer Preparation Request to ATCF and the media path between ATCF/ATGW and the MSC Server/MGW is to be established. + +10. The UEs send Handover confirmation to the eNB. +11. The eNB send Handover Notify to the MME. +12. The MME sends Modify Bearer Request to the SGW, which is forwarded to the PGW to update PS bearer contexts. +13. The MME sends the Acknowledgment to the Context Response to the SGSN. +14. The voice media is started directly. + +NOTE 3: During a short period of time prior the RAT has been changed and the new bearer has been established, the media will be sent over the default bearer. + +15. The UE initiates the session continuity procedures according to clause 6.3.3.8 towards the ATCF. +16. As a result of the session continuity procedures, the bearer setup is performed (initiated by the P-CSCF). +17. The voice media is sent in the dedicated bearer. + +![Sequence diagram for Access Transfer Preparation Alternative 5, DTM case. It shows message flows between UE-1, BSC/RNC, NB/eNB, MSC Server, Source SGSN, SGW/PGW, PCRF, ATCF, P-CSCF, and Target MME. Key steps include HO required, CS to PS HO request, Relocation Request, Allocate resources, HO command, Access Transfer Preparation, and bearer setup.](bc9d0c0b02cbe628b1b6548cc1107734_img.jpg) + +``` + +sequenceDiagram + participant UE as UE-1 + participant RAN as BSC/RNC NB/eNB + participant MSC as MSC Server + participant SGSN as Source SGSN + participant SGW as SGW/PGW + participant PCRF + participant ATCF + participant PCSCF as P-CSCF + participant MME as Target MME + + RAN->>MSC: 1. HO required + MSC->>MME: 2. CS to PS HO request + MSC->>ATCF: 3. Access Transfer Notification + RAN->>SGSN: 1a. HO required + SGSN->>MME: 4. Relocation Request + MME->>SGSN: 5. Allocate resources + SGSN->>MME: 6a. Relocation Response + MME->>MSC: 7. CS to PS HO response + MSC->>RAN: 8a. CS to PS HO command + RAN->>MSC: 6b. HO required Ack + RAN->>UE: 8b. CS to PS HO command + MSC->>ATCF: 9. Access Transfer Preparation request + UE->>RAN: 10. CS to PS HO confirmation + RAN->>MME: 11. Handover Notify + MME->>SGSN: 12. Forward Relocation complete + MME->>SGW: 13. Modify Bearers + Note over UE, SGW: 14. Voice over default bearer user plane + rect rgb(240, 240, 240) + Note over UE, ATCF: 15. Session continuity procedure (clause 6.3.3.8) + end + rect rgb(240, 240, 240) + Note over UE, PCSCF: 16. Bearer setup + end + Note over UE, SGW: 17. Voice over dedicated bearer user plane + +``` + +Sequence diagram for Access Transfer Preparation Alternative 5, DTM case. It shows message flows between UE-1, BSC/RNC, NB/eNB, MSC Server, Source SGSN, SGW/PGW, PCRF, ATCF, P-CSCF, and Target MME. Key steps include HO required, CS to PS HO request, Relocation Request, Allocate resources, HO command, Access Transfer Preparation, and bearer setup. + +**Figure 6.3.3.7.5-2: Access Transfer Preparation Alternative 5, DTM case** + +1. The RNC/BSC sends a HO required to the MSC Server including an indication this HO is for rSRVCC. If the MSC Server is the target MSC, it forwards the HO required to the anchor MSC Server. +- 1a. In the DTM case the UE is active in PS domain, the RNC/BSC sends also a Relocation Required message to source SGSN. + +2. The MSC Server sends a SRVCC CS to PS HO request to the Target MME. If required, the IMSI is provided for identifying the UE. +3. The MSC Server sends an Access Transfer Notification to the ATCF, e.g. a SIP re-INVITE or INVITE message, which indicates the ATCF that it should prepare for the transfer of media to PS. The ATCF allocates media ports on the ATGW. The media ports and codecs allocated by the ATCF are provided to the MSC Server in the response message. This step is independent of step 2. + +NOTE 4: The ATCF retrieves the ports/codecs received from the UE in its IMS registration. The ATCF is able to correlate the IMS registration made by the UE and the one made by the MSC Server on behalf of the UE for instance based on the C-MSISDN or on the IMEI derived instance-id used by both those registrations. + +NOTE 5: The Access Transfer Notification message could e.g., be implemented using an INVITE or other appropriate message. It is left for stage 3 to decide on appropriate message. + +4. Source SGSN sends Relocation Request to the target MME. +5. Target MME allocates resources in E-UTRAN. +- 6a. A relocation response is returned to the Source SGSN. +- 6b. Source SGSN sends HO Required Ack to RAN. +7. A SRVCC CS to PS HO response is returned from the target MME to the MSC Server. +8. MSC Server sends HO required Ack to the RAN, possibly via the target MSC, and the RAN send HO command to UE, indicating CS to PS handover. The MSC Server also includes in that message the IP address/ports and selected codec for the ATGW. +9. In case of ATCF with media anchored in ATGW, the MSC Server sends an Access Transfer Preparation Request, e.g. a SIP re-INVITE or PRACK message, to the ATCF to trigger the ATCF/ATGW to have the media path switched to the IP address/port of the UE on the target access. + +In case of ATCF without media anchored in ATGW, MSC Server sends an Access Transfer Preparation Request to ATCF and the media path between ATCF/ATGW and the MSC Server/MGW is to be established. + +10. The UEs send Handover confirmation to the eNB. +11. The eNB send Handover Notify to the MME. +12. The MME sends Forward relocation Complete to the old SGSN. +13. The MME sends Modify Bearer Request to the SGW which is forwarded to the PGW to update PS bearer contexts. +14. The voice media is started directly. + +NOTE 6: During a short period of time prior the RAT has been changed and the new bearer has been established, the media will be sent over the default bearer. + +15. The UE initiates the session continuity procedures according to clause 6.3.3.8 towards the ATCF. +16. As a result of the session continuity procedures, the bearer setup is performed (initiated by the P-CSCF). +17. The voice media is sent in the dedicated bearer. + +#### 6.3.3.8 IMS Session Continuity procedure + +##### 6.3.3.8.0 General + +IMS Session Continuity procedure can be accomplished by sending an Access Transfer Complete request to IMS, e.g. by using a SIP INVITE. If the ATCF was involved in the IMS registration made by UE, the P-CSCF routes the Access Transfer Complete request to the ATCF. The Access Transfer Complete request to IMS is addressed using a dynamically provided STI-rSR (Session Transfer Identifier for rSRVCC). + +If the ATCF was involved and receives an Access Transfer Complete request, it notifies the SCC AS about the fact the UE has now moved to the target access. The SCC AS then releases the source access leg as described in 3GPP TS 23.237 [4]. + +If MSC Server receives the release of the original dialog, it shall release the dialog between the MSC Server and the allocated ATCF. + +##### 6.3.3.8.1 Anchored in ATGW + +Following figure 6.3.3.8.1-1 shows an example that ATCF is involved in the IMS registration made by UE and ATGW anchors the media. + +![Sequence diagram of IMS Session Continuity procedure with media anchored in ATGW. The diagram shows the interaction between UE-1, MSC Server / MGW, P-CSCF, ATCF, ATGW, SCC AS, and Remote side. The process starts with the MSC Server sending an '0. Access Transfer Preparation' to the ATCF. The ATCF then sends a '1. Switch media path' to the ATGW. The UE-1 sends a '2. Access Transfer Complete (STI-rSR)' to the P-CSCF, which is forwarded to the ATCF. The ATCF then sends a '3. ATC (STI-rSR)' to the P-CSCF. The P-CSCF then sends a '4. Control transferred' to the ATCF. The ATCF then sends a '5. Access Transfer Update' to the SCC AS, which responds with a '6. Access Transfer response'. Finally, a '7. Transfer of additional active/held session' is indicated by a horizontal bar across the bottom of the diagram.](ff5f89b660edddb67971d7d3d4ce87ef_img.jpg) + +Sequence diagram of IMS Session Continuity procedure with media anchored in ATGW. The diagram shows the interaction between UE-1, MSC Server / MGW, P-CSCF, ATCF, ATGW, SCC AS, and Remote side. The process starts with the MSC Server sending an '0. Access Transfer Preparation' to the ATCF. The ATCF then sends a '1. Switch media path' to the ATGW. The UE-1 sends a '2. Access Transfer Complete (STI-rSR)' to the P-CSCF, which is forwarded to the ATCF. The ATCF then sends a '3. ATC (STI-rSR)' to the P-CSCF. The P-CSCF then sends a '4. Control transferred' to the ATCF. The ATCF then sends a '5. Access Transfer Update' to the SCC AS, which responds with a '6. Access Transfer response'. Finally, a '7. Transfer of additional active/held session' is indicated by a horizontal bar across the bottom of the diagram. + +**Figure 6.3.3.8.1-1: IMS Session Continuity procedure – with media anchored in ATGW** + +0. The IMS Session Continuity procedure starts when the media path switching is requested from the MSC server during the Access transfer preparation phase (see Step 12 in clause 6.3.3.7.1, Step 8b in clause 6.3.3.7.2, Step 10 in clause 6.3.3.7.3, and Step 9a in clause 6.3.3.7.4 respectively). +1. When receiving the Access Transfer Preparation request from the MSC Server, the ATCF updates the ATGW to switch the media path to the PS access leg. For alternative 3 and 4, the access media leg is switched to the access media leg of the pre-established session. +2. When the UE has moved to PS, it can receive media on the pre-decided ports. It will re-establish the session control of the media by sending an Access Transfer Complete request with the provided STI-rSR, e.g. by using a SIP INVITE request. For alternative 1, 2 and 3, it shall use the media information it already uses. + +For alternative 4, if a new QCI=1 bearer has been created, UE uses it for voice media data transfer. + +3. The Access Transfer Complete request is forwarded to the ATCF. +4. The ATCF correlates the Access Transfer Complete request with the Access Transfer Preparation request and the ongoing sessions, and moves the session control of the session to the new access leg. For alternative 4, the ATCF informs the UE to use the codec that original session used if possible. +5. After receiving the Access Transfer Complete request, the ATCF re-establishes the communication with the SCC AS and updates the SCC AS that the transfer has taken place by sending an Access Transfer Update message to the SCC AS. As there is no update in the session description, no remote end update will be sent by the SCC AS. +6. The SCC AS sends confirmation response to the ATCF. + +- The UE may initiate transfer of any additional active/held session. + +##### 6.3.3.8.2 Not Anchored in ATGW + +Following figure 6.3.3.8.2-1 shows an example that ATCF is involved in the IMS registration made by UE and not involved in the IMS registration made by MSC Server. + +![Sequence diagram of IMS Session Continuity procedure - without media anchored in ATGW. The diagram shows interactions between UE-1, MSC Server / MGW, P-CSCF, ATCF, ATGW, SCC AS, and Remote side. The process involves steps 0 through 8, including Access Transfer Preparation, Create media path, Access Transfer Complete (STI-rSR), ATC (STI-rSR), Control transferred, Access Transfer Update, update media path of Remote side, Access Transfer response, and Transfer of additional active/held session. Media paths are shown switching from CS to PS access legs.](c1278da91cbcabe32628e589ebc47418_img.jpg) + +``` + +sequenceDiagram + participant UE-1 + participant MSC Server / MGW + participant P-CSCF + participant ATCF + participant ATGW + participant SCC AS + participant Remote side + + Note left of UE-1: Media path, access leg (CS) + UE-1->>MSC Server / MGW: 0. Access Transfer Preparation + MSC Server / MGW->>ATCF: 1. Create media path + Note right of ATCF: Media path, access leg + Note left of UE-1: PS-Media + UE-1->>MSC Server / MGW: Media path, access leg(PS) + UE-1->>P-CSCF: 2. Access Transfer Complete (STI-rSR) + P-CSCF->>ATCF: 3. ATC (STI-rSR) + ATCF->>ATCF: 4. Control transferred + ATCF->>SCC AS: 5. Access Transfer Update + SCC AS->>ATGW: 6. update media path of Remote side + ATGW->>ATCF: 7. Access Transfer response + Note left of UE-1: Media path, access leg (PS) + Note right of Remote side: Media path, remote leg + Note bottom: 8. Transfer of additional active/held session + +``` + +Sequence diagram of IMS Session Continuity procedure - without media anchored in ATGW. The diagram shows interactions between UE-1, MSC Server / MGW, P-CSCF, ATCF, ATGW, SCC AS, and Remote side. The process involves steps 0 through 8, including Access Transfer Preparation, Create media path, Access Transfer Complete (STI-rSR), ATC (STI-rSR), Control transferred, Access Transfer Update, update media path of Remote side, Access Transfer response, and Transfer of additional active/held session. Media paths are shown switching from CS to PS access legs. + +**Figure 6.3.3.8.2-1: IMS Session Continuity procedure - without media anchored in ATGW** + +- The IMS Session Continuity procedure starts when the media path switching is requested from the MSC server during the Access transfer preparation phase (see Step 12 in clause 6.3.3.7.1, Step 8b in clause 6.3.3.7.2, Step 10 in clause 6.3.3.7.3, and Step 9a in clause 6.3.3.7.4 respectively). +- When receiving the Access Transfer Preparation request from the MSC Server, the ATCF reserves ATGW resources for the media path connected to MSC Server/MGW. +- When the UE has moved to PS, it can receive media on the pre-decided ports. It will re-establish the session control of the media by sending an Access Transfer Complete request with the provided STI-rSR, e.g. by using a SIP INVITE request. For alternative 1, 2 and 3, it shall use the media information it already uses. + +For alternative 4, if a new QCI=1 bearer has been created, UE uses it for voice media data transfer. + +- The Access Transfer Complete request is forwarded to the ATCF. If ATCF was not involved in the IMS registration procedure made by UE, the Access Transfer Complete request is forwarded to the SCC AS. + +Following steps 4, 5 and 7 is for ATCF involved in the IMS registration made by UE. + +- The ATCF correlates the Access Transfer Complete request with the Access Transfer Preparation request, and moves the session control of the session to the new access leg. For alternative 4, the ATCF informs the UE to use the codec that original session used if possible. +- After receiving the Access Transfer Complete request, the ATCF re-establishes the communication with the SCC AS and updates the SCC AS that the transfer has taken place by sending an Access Transfer Update request to the SCC AS. The ATCF updates the ATGW to switch the media path to the PS access leg. For alternative 1 and 2, the access media leg is switched to the access media leg pre-negotiated during IMS registration procedure made by UE. For alternative 3 and 4, the access media leg is switched to the access media leg of the pre-established session. + +6. After receiving the Access Transfer Update/Access Transfer Complete request, the SCC AS may send remote end update. +7. The SCC AS sends confirmation response to the ATCF. +8. The UE may initiate transfer of any additional active/held session. + +#### 6.3.3.9 Identification of serving PS node + +##### 6.3.3.9.1 Alternative 1: CN nodes based + +Provision of the SGSN identity to the MSC via HSS Insert Subscriber Data and via SGSN notifications + +1. SGSN functionality: + - At Attach and at Inter-SGSN routing area update, the new SGSN gets the address of the MSC serving the UE in the Insert Subscriber Data which it receives from the HSS as part of the existing procedure. + - The SGSN then notifies the MSC (serving or anchor) that it has become the serving SGSN for the user if the UE is rSRVCC capable, and if the MSC is rSRVCC capable. +2. Additional MSC functionality: + - At IMSI Attach and at Inter- MSC Location Area Update, if an SGSN is serving the UE, the MSC stores as "serving PS CN node" the address of the serving SGSN it receives from the HSS in the Insert Subscriber Data as part of the Location Area Update. + - When getting notified by an SGSN, the MSC stores as "serving PS CN node" the identity of the SGSN that issued the notification. + - At SRVCC, the MSC initializes the "serving PS CN node" to the identity of the MME that issued the PS to CS request. +3. Additional HSS functionality: + - The HSS needs to include the serving MSC identity in the Insert Subscriber Data it sends to the SGSN. +4. Additional UE functionality: + - The UE signals its rSRVCC capability to the SGSN at Attach and at Routing Area Update. +At SRVCC handover combined with PS handover, the UE needs to slightly delay the sending of the Routing Area Update it sends once getting on the target access. (This would be required to make sure the MSC has performed the Location Updating towards the HSS, and that the SGSN will therefore be able to get the identity of the MSC it needs to notify). + +##### 6.3.3.9.2 Alternative 2: UE and/or RAN provided information + +UE packs one of the following information into rSRVCC IE, which can be used by the MSC to locate source SGSN / old MME: + +- a. RAI, P-TMSI, and P-TMSI signature if serving PS node is in UTRAN network. +- b. RAI and TLLI if serving PS node is in GERAN network. +- c. GUTTI if serving PS node is in E-UTRAN network. + +UE reports rSRVCC IE to RNC/BSC when it is involved in CS call establishment (including CS MO/MT, CS handover, and SRVCC cases). + +Examples of methods that could be used to report the rSRVCC IE to the RNC/BSC: + +- RRC message: examples are the ASSIGNMENT COMPLETE message and HANDOVER COMPLETE messages (the "RRC Measurement Report" message shall not be used). The inclusion of rSRVCC IE shall be according to clause 10.1.1.1.2 of TS 25.331 for non-critical extension of a RRC message with additional information elements (currently RAN2 does not recommend modifying RRC messages to include rSRVCC Info IE) or clause 8.6.1 of TS 44.018 [13]. + +- Suspend procedure in case of non-DTM capable GERAN network +- Additional RAU procedure or assignment procedure for UE in dedicated mode. +- For UE in dedicated mode, in case of normal CS HO but without RA change (e.g. inter RNC HO without RA change), following methods can be used: + - a. the UE reports rSRVCC IE to RNC/BSC using handover complete procedure. + - b. the source RNC/BSC sends the rSRVCC IE to target RNC/BSC by including it in the Transparent Container. + +NOTE: Which method is used needs to be decided by RAN groups / stage 3. + +RNC/BSC includes the rSRVCC Info IE in Handover/Relocation Required message for CS to PS handover, e.g. by including the rSRVCC Info IE into GERAN Classmark. + +The following figure shows an example call flow. + +![Sequence diagram showing the call flow for rSRVCC. The diagram involves three entities: UE, GERAN/UTRAN, and MSC Server. The sequence of messages is: 1a. Proceed CS call for MO/MT (UE to GERAN/UTRAN), 1b. Provide rSRVCC IE (UE to GERAN/UTRAN), 2a. CS handover or SRVCC to target (GERAN/UTRAN to MSC Server), 2b. Provide rSRVCC IE (GERAN/UTRAN to MSC Server), 3a. rSRVCC triggered (GERAN/UTRAN to MSC Server), 3b. Reloc Required/MAP_HO_Prep (rSRVCC) (MSC Server to GERAN/UTRAN), and 3c. Initiate rSRVCC (MSC Server to GERAN/UTRAN).](1316d63eca7b84e13c27f55f0027b7b5_img.jpg) + +``` + +sequenceDiagram + participant UE + participant GERAN/UTRAN + participant MSC Server + Note right of GERAN/UTRAN: 1a. Proceed CS call for MO/MT + UE->>GERAN/UTRAN: 1b. Provide rSRVCC IE + Note right of GERAN/UTRAN: 2a. CS handover or SRVCC to target + GERAN/UTRAN->>MSC Server: 2b. Provide rSRVCC IE + Note right of GERAN/UTRAN: 3a. rSRVCC triggered + MSC Server->>GERAN/UTRAN: 3b. Reloc Required/MAP_HO_Prep (rSRVCC) + Note right of MSC Server: 3c. Initiate rSRVCC + +``` + +Sequence diagram showing the call flow for rSRVCC. The diagram involves three entities: UE, GERAN/UTRAN, and MSC Server. The sequence of messages is: 1a. Proceed CS call for MO/MT (UE to GERAN/UTRAN), 1b. Provide rSRVCC IE (UE to GERAN/UTRAN), 2a. CS handover or SRVCC to target (GERAN/UTRAN to MSC Server), 2b. Provide rSRVCC IE (GERAN/UTRAN to MSC Server), 3a. rSRVCC triggered (GERAN/UTRAN to MSC Server), 3b. Reloc Required/MAP\_HO\_Prep (rSRVCC) (MSC Server to GERAN/UTRAN), and 3c. Initiate rSRVCC (MSC Server to GERAN/UTRAN). + +Figure 6.3.3.9.2-1 + +1. UE involves in CS session by proceeding CS MO/MT procedure. UE packs the serving PS node information into rSRVCC IE and reports the rSRVCC IE to RNC/BSC. In case the used message contains already the serving PS node information, then there is no need to include the rSRVCC IE additionally and the RNC/BSC can construct the rSRVCC IE on its own. +2. UE involves in CS session by performing SRVCC procedure. UE packs the serving PS node information into rSRVCC IE and reports the rSRVCC IE to RNC/BSC. In case the used message contains already the serving PS node information, then there is no need to include the rSRVCC IE and the RNC/BSC can construct the rSRVCC IE on its own. In case of inter-SGSN change or intra SGSN with RAI change and the BSC/RNC has generated P-TMSI/LLLI+target RAI the RNC/BSC can replace the P-TMSI/LLLI+RAI received from the UE with the RNC/BSC generated P-TMSI/LLLI+target RAI pointing to the target SGSN. +3. When the RNC/BSC supporting rSRVCC triggers the rSRVCC procedure, it sends Relocation Required/Handover Required message with received rSRVCC IE content to anchor MSC Server. The anchor MSC Server sends MAP-Handover-Preparation request with the received rSRVCC IE content to target MSC Server. + +##### 6.3.3.9.3 Alternative 3: RAN provided information + +###### According to 6.3.3.9.2: + +###### Regarding bullet a and bullet b where GERAN is DTM capable: + +In case of UTRAN or DTM capable GERAN network, during attachment procedure or RAU procedure, the RNC/BSC has the information pointed to the serving SGSN, which can be stored in RNC/BSC in case of active CS session. When RNC/BSC needs to start rSRVCC HO, it includes this serving SGSN address as part of the HO signalling toward the MSC enhanced for rSRVCC. + +As RNC/BSC have no UE context for the UE in PS idle mode, the UE should initiate additional RAU to provide the RNC or BSC with the RAI/P-TMSI/P-TMSI signature or RAI/TLLI respectively when initiating CS call. + +In case of normal CS HO without RA change for PS idle mode UE, there seem two alternative solutions as described below: + +- 1) The serving SGSN information is to be transferred as BSC-to-BSC / RNC-to-RNC information in Handover / Relocation Required and Handover / Relocation Request messages and the target RNC/BSC stores the related information for future rSRVCC HO procedure. +- 2) In normal CS HO procedure, the source RNC/BSC reuses the rSRVCC Info IE to include the serving SGSN information in Handover / Relocation Required message and the anchor MSC Server stores the related information for future rSRVCC HO procedure. + +###### **Regarding bullet b where GERAN is Non-DTM capable:** + +In case of Non-DTM capable GERAN network, according to clause 16.2.1.1.1 of TS 23.060 [6], it seems the suspend procedure can be reused to transfer RAI and TLLI to BSC. + +In this case, when UE has been involved in active CS call, the UE sends RR Suspend (TLLI, RAI) message to the BSC and BSC stores the related information. If the MS performs an inter-BSC handover while suspended, the TLLI and RAI should be transferred as BSC-to-BSC information in the Handover Required and Handover Request messages. + +Please note that MSC Server only uses RAI/TLLI to resolve the address of the serving MME and IMSI still needs to be transferred to MME for UE identification. + +###### **Regarding bullet c:** + +This applies to the scenario of CS voice call established during SRVCC from E-UTRAN to GERAN without DTM support where the UE will be in GPRS PS suspend state in GERAN. + +In this case, the UE will send RR Suspend with TLLI/RAI to BSC that is mapped from GUTI pointed to old serving MME and the following procedure is similar with the bullet b. + +Alternatively, SRVCC MSC Server is the anchor MSC Server and can store the information of serving MME node. Assuming SRVCC MSC Server can also act as rSRVCC MSC Server, the stored MME information can be used by the anchor MSC Server to find the correct MME. + +NOTE: The SRVCC MSC Server is able to find the source MME based on the received information during SRVCC PS to CS procedure according to TS 29.280 [14]. + +During rSRVCC procedure, RNC/BSC includes the rSRVCC Info IE with serving SGSN/MME information in Handover/Relocation Required message for CS to PS handover, which is used by MSC Server to find the serving SGSN/MME correctly. + +### **6.3.4 IMS registration Considerations** + +#### **6.3.4.1 General** + +As a prerequisite for rSRVCC, the UE is IMS registered over PS. + +#### **6.3.4.2 ATCF controlled registration** + +To avoid that the IMS registration expires during an ongoing voice call over GERAN / UTRAN without DTM support, the ATCF instructs the P-CSCF as follows: + +- While the voice call is ongoing on the CS access leg (to/from the ATCF), the P-CSCF shall update the local registration timer of the PS access leg such that it does not expire during the ongoing call. +- If needed, the P-CSCF will also further instruct the S-CSCF to update its registration timer for the PS access leg such that it does not expire during the ongoing call. + +After releasing the voice call(s), and if needed, the UE itself updates the IMS registration, i.e. in case the original IMS registration timer on the UE has already expired, the UE will immediately perform re-registration. + +NOTE: If the UE's IMS registration timer expires locally during the ongoing call, the UE ignores this until the call is completed and is able to perform a re-registration. + +Following figure shows an example of the solution: + +![Sequence diagram for ATCF controlled registration. Lifelines: UE, P-CSCF, ATCF, SCC AS/S-CSCF. The sequence starts with '1. UE has CS session' on the ATCF lifeline. ATCF sends '2. Instruct (stop timer)' to P-CSCF and '3. Instruct (stop timer)' to SCC AS/S-CSCF. UE sends '4. All CS sessions are released' to P-CSCF. UE sends '5. REGISTER' to P-CSCF. P-CSCF sends '6. REGISTER' to ATCF. ATCF sends '7. REGISTER' to SCC AS/S-CSCF. A horizontal bar at the bottom indicates '8. Completion of IMS re-registration'.](9cbc1ebd80813fc36e499f7d70ed6881_img.jpg) + +``` + +sequenceDiagram + participant UE + participant P-CSCF + participant ATCF + participant SCC AS/S-CSCF + + Note right of ATCF: 1. UE has CS session + ATCF->>P-CSCF: 2. Instruct (stop timer) + ATCF->>SCC AS/S-CSCF: 3. Instruct (stop timer) + Note left of UE: 4. All CS sessions are released + UE->>P-CSCF: 5. REGISTER + P-CSCF->>ATCF: 6. REGISTER + ATCF->>SCC AS/S-CSCF: 7. REGISTER + Note over UE, P-CSCF, ATCF, SCC AS/S-CSCF: 8. Completion of IMS re-registration + +``` + +Sequence diagram for ATCF controlled registration. Lifelines: UE, P-CSCF, ATCF, SCC AS/S-CSCF. The sequence starts with '1. UE has CS session' on the ATCF lifeline. ATCF sends '2. Instruct (stop timer)' to P-CSCF and '3. Instruct (stop timer)' to SCC AS/S-CSCF. UE sends '4. All CS sessions are released' to P-CSCF. UE sends '5. REGISTER' to P-CSCF. P-CSCF sends '6. REGISTER' to ATCF. ATCF sends '7. REGISTER' to SCC AS/S-CSCF. A horizontal bar at the bottom indicates '8. Completion of IMS re-registration'. + +**Figure 6.3.4.2-1: ATCF controlled registration** + +**Editor's Note:** It is FFS that whether a resume timer is needed and what if CS session is not anchored on ATCF. + +#### 6.3.4.3 SCC AS controlled registration + +During the IMS (re-)registration procedure, The UE shall send a SIP REGISTER request with an additional time interval $T_{maintain}$ to IMS to maintain IMS registration when UE is involved in CS session. The time interval for IMS re-registration is called $T_{Registration}$ . In order not to impact P-CSCF, the $T_{maintain}$ shall be included in the Expires header field of the SIP REGISTER request and the response. + +The S-CSCF shall not reduce the $T_{maintain}$ if the 3rd party registration needs to be performed to a SCC AS. The S-CSCF may reduce the $T_{Registration}$ according to local policy. The S-CSCF shall forward the $T_{Registration}$ to the SCC AS via 3rd party registration procedure and forward the $T_{Registration}$ to the UE, e.g. by including the $T_{Registration}$ in the response to the SIP REGISTER request. + +The SCC AS may hold a time interval $T_{Transfer}$ corresponding to the approximate transfer time of the SIP REGISTER request. The SCC AS shall reset the time interval for monitoring IMS re-registration to ( $T_{Registration} + T_{Transfer}$ ) when all CS sessions of the UE has been released or the UE re-registration has been informed, and stop monitoring the IMS re-registration when CS session of the UE can be detected. If the time expired, the SCC AS shall inform the HSS to de-register the UE. + +Following figure shows an example of the solution: + +![Sequence diagram for SCC AS controlled registration. Lifelines: UE, P-CSCF, S-CSCF, HSS, SCC AS. The sequence shows registration steps 1-3 from UE to SCC AS via P-CSCF and S-CSCF. A bar labeled '4. Completion of IMS registration' spans across. Below this, step 5 shows UE performing re-registration. Step 6 shows UE not having a CS session and Tregistration expires. Steps 7-9 show De-Reg messages from SCC AS to HSS, then S-CSCF, then P-CSCF.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +``` + +sequenceDiagram + participant UE + participant P-CSCF + participant S-CSCF + participant HSS + participant SCC AS + UE->>P-CSCF: 1. REGISTER Tmaintain, Tregistration + P-CSCF->>S-CSCF: 2. REGISTER Tmaintain, Tregistration + S-CSCF->>SCC AS: 3. REGISTER Tregistration + Note over UE, SCC AS: 4. Completion of IMS registration + Note left of UE: 5. UE performs IMS re- +registration according +to Tregistration + Note right of HSS: 6. UE does not have +CS session and +Tregistration expires + SCC AS->>HSS: 7. De-Reg + HSS->>S-CSCF: 8. De-Reg + S-CSCF->>P-CSCF: 9. De-Reg + +``` + +Sequence diagram for SCC AS controlled registration. Lifelines: UE, P-CSCF, S-CSCF, HSS, SCC AS. The sequence shows registration steps 1-3 from UE to SCC AS via P-CSCF and S-CSCF. A bar labeled '4. Completion of IMS registration' spans across. Below this, step 5 shows UE performing re-registration. Step 6 shows UE not having a CS session and Tregistration expires. Steps 7-9 show De-Reg messages from SCC AS to HSS, then S-CSCF, then P-CSCF. + +**Figure 6.3.4.3-1: SCC AS controlled registration** + +#### 6.3.4.4 rSRVCC HO Cancellation in case of UE loss of IMS registration + +The clause handles the case the IMS registration from the UE expires during an ongoing call. + +Two steps are performed to handle the IMS registration expiration. + +1. MSC Server subscribes to the UE's IMS registration status. + +NOTE 1: This does not imply the use of Subscribe at stage 3. + +2. The MSC Server uses the IMS registration status to ensure that full rSRVCC procedures are not performed, when the session may be lost due to de-registration. + +Figure 6.3.4.4-1 provides the procedures of how the MSC server subscribes to the UE's IMS registration status and is notified with changes. + +![Sequence diagram for subscription to UE's IMS registration status. Lifelines: MSC Server, ATCF, CSCF, SCC AS. Step 1 is a subscription from MSC Server to SCC AS. Step 2 is a registration change notification from SCC AS to CSCF. Step 3 is a registration change notification from CSCF to ATCF. Step 4 is a registration change notification from ATCF to MSC Server.](ae375ead8aa673286b534e079e9a8533_img.jpg) + +``` + +sequenceDiagram + participant MSC Server + participant ATCF + participant CSCF + participant SCC AS + Note over MSC Server, SCC AS: 1. MSC Subscribe to registration change for UE + SCC AS->>CSCF: 2. Registration change notification + CSCF->>ATCF: 3. Registration change notification + ATCF->>MSC Server: 4. Registration change notification + +``` + +Sequence diagram for subscription to UE's IMS registration status. Lifelines: MSC Server, ATCF, CSCF, SCC AS. Step 1 is a subscription from MSC Server to SCC AS. Step 2 is a registration change notification from SCC AS to CSCF. Step 3 is a registration change notification from CSCF to ATCF. Step 4 is a registration change notification from ATCF to MSC Server. + +**Figure 6.3.4.4-1: Subscription to UE's IMS registration status** + +1. MSC Server subscribes to the UE's IMS registration status. + +- 2-4. If the UE's IMS registration status changes, the MSC Server is notified by the IMS network. + +Figure 6.3.4.4-2 provides the procedures of how the MSC server handles errors when HO Required is received. + +![Sequence diagram illustrating error handling during handover (HO). The diagram shows two main entities: BSC/RNC and MSC Server. The sequence of messages is: 1. HO Required (from BSC/RNC to MSC Server), 2. Detect rSRVCC not possible (from MSC Server to BSC/RNC), and 3. HO Cancellation (from MSC Server to BSC/RNC).](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +``` + +sequenceDiagram + participant BSC/RNC + participant MSC Server + Note right of MSC Server: 2. Detect rSRVCC not possible + BSC/RNC->>MSC Server: 1. HO Required + MSC Server-->>BSC/RNC: 2. Detect rSRVCC not possible + MSC Server-->>BSC/RNC: 3. HO Cancellation + +``` + +Sequence diagram illustrating error handling during handover (HO). The diagram shows two main entities: BSC/RNC and MSC Server. The sequence of messages is: 1. HO Required (from BSC/RNC to MSC Server), 2. Detect rSRVCC not possible (from MSC Server to BSC/RNC), and 3. HO Cancellation (from MSC Server to BSC/RNC). + +**Figure 6.3.4.4-2: Error handling during HO.** + +1. The RNC/BSC sends a HO required to the MSC Server including an indication this HO is for SRVCC. +2. The MSC Server checks if HO is possible, e.g., that the UE is still registered in IMS (additional checks may be performed, such as if MSC server have a registration through ATCF). In this flow, the MSC Server detects that rSRVCC cannot be performed. +3. MSC Server cancels the HO. + +NOTE 2: After receiving the HO cancellation due to rSRVCC, the RNC/BSC will not perform further HO attempts for rSRVCC. + +## 6.4 Solution 4: Session transfer by local anchoring with Indirect Forwarding + +### 6.4.1 Functional Description + +This solution is a counter part of the alternative 12 in the TR 23.856 [8] such as enhancement of the SRVCC currently studied in SA2. This alternative aims to provide high performance in handover between CS domain voice service and LTE/HSPA IMS based voice media service by anchoring in local network. + +This solution is provided by the following components. + +- New routing number for the MSC Server/MGW enhanced for SRVCC is adapted in this solution in order to establish the CS domain connection between UE and the MSC Server/MGW enhanced for SRVCC. + +**Editor's Note:** How UE gets new routing number is FFS. It is also possible to route to the MSC Server/MGW enhanced for SRVCC by adding prefix information in front of called number. In this case, added prefix is translated in the MSC. If the MSC Server/MGW enhanced for SRVCC is collocated to every MSC in the VPLMN, new routing number is not needed at all. + +- The call control is mainly performed in IMS infrastructure coordinated with the CS domain call control, PCC architecture and EPC session control. +- The PCC and EPC are enhanced for exchanging session related information between the SCC AS and the MSC Server/MGW enhanced for SRVCC. +- Once the MSC Server/MGW enhanced for SRVCC receives a call establishment request from the UE, the MSC Server/MGW enhanced for SRVCC contacts to the SCC AS to inform an IP address of the its MGW. This IP address is conveyed to SGSN via P-CSCF, PCRF, PGW and SGW. Then SGSN use this IP address to contact to the MGW to establish the EPC bearer between SGW and MGW for VoIP media. +- The EPC is enhanced to establish Y shape connection anchored by the SGW. The Y shape is structured by one leg between PGW and UE as normal EPC bearer for packet domain, and the other one leg between PGW and the MSC Server/MGW enhanced for SRVCC for rSRVCC specific EPC bearer. Both legs are anchored by the SGW. The high HO performance can be achieved by this connection model since this model utilizes the inter RAT HO and no "session transfer" is required if PS HO is supported, i.e. SIP signalling session is kept both before and after HO. + +- For both origination and termination, the SIP level call control and CS domain call control can be executed parallel in order to minimize call setup time. + +Editor's Note: It is FFS how to support non-DTM support case. + +Editor's Note: It is FFS how to handle the case where inter-MSC handover happens in this solution. + +### 6.4.2 Architecture Reference Model + +The Figure 6.4.2-1 shows the architecture reference model of this solution. + +![Figure 6.4.2-1: rSRVCC solution using local anchoring. The diagram illustrates the network architecture for rSRVCC, showing the flow of bearers and signaling paths between a UE (User Equipment), Target UTRAN/GERAN, MSC Server/MGW, HSS, SGSN, MME, SGW, PGW, and the IMS domain (SCC AS, S-CSCF, P-CSCF, S/P-CSCF).](c5a20f7bae219fc4c31f7376b7eb11e1_img.jpg) + +The diagram shows the architecture reference model for rSRVCC using local anchoring. It depicts the network components and the paths for bearers and signaling during a handover from a Target UTRAN/GERAN to an E-UTRAN. + +- UE1** (User Equipment) is connected to **Target UTRAN/GERAN** and **E-UTRAN**. +- Target UTRAN/GERAN** is connected to **MSC Server/MGW** and **SGSN**. +- MSC Server/MGW** is connected to **HSS** and **MME**. +- HSS** is connected to **SGSN** and **MME**. +- SGSN** is connected to **MME**. +- MME** is connected to **SGW**. +- SGW** is connected to **PGW**. +- PGW** is connected to **UE2** and the **IMS domain**. +- The **IMS domain** contains **SCC AS**, **S-CSCF**, **P-CSCF**, and **S/P-CSCF**. + +**Legend:** + +- Common Bear path before and after HO (solid black line) +- Bear path after HO (solid blue line) +- Bear path before HO (dashed blue line) +- SIP signaling path after HO (solid red line) +- SIP signaling path before HO (in case of PS HO) (dashed red line) +- SIP signaling before HO (in case of IMS VoIP is not supported in 2G/3G) (dashed purple line) +- CS bearer (before HO) (dashed green line) + +Figure 6.4.2-1: rSRVCC solution using local anchoring. The diagram illustrates the network architecture for rSRVCC, showing the flow of bearers and signaling paths between a UE (User Equipment), Target UTRAN/GERAN, MSC Server/MGW, HSS, SGSN, MME, SGW, PGW, and the IMS domain (SCC AS, S-CSCF, P-CSCF, S/P-CSCF). + +Figure 6.4.2-1: rSRVCC solution using local anchoring + +Editor's Note: The architecture figure will include the PCRF. + +### 6.4.2 Information flows + +#### 6.4.2.1 Initial ATTACH / TA update procedure + +The E-UTRAN attach procedure for 3GPP rSRVCC UE is performed as defined in TS 23.216 [7] with the following additions: + +- 1) rSRVCC UE includes the "rSRVCC capability indication" as part of the "MS Network Capability" in the Attach Request message and in Tracking Area Updates. +- 2) If the subscriber is allowed to have rSRVCC in the VPLMN, the HSS shall include the "rSRVCC allowed" indication as part of the subscription data sent to the MME. + +#### 6.4.2.2 Call origination procedure in GERAN/UTRAN + +In case rSRVCC capable UE determines to establish rSRVCC call, the following procedure takes place. + +![Sequence diagram of call origination procedure in GERAN/UTRAN. The diagram shows interactions between UE, RNS, eNB, MSC, SGSN, MSC for SRVCC, SGW, PGW, PCRF, SCC AS (IMS), and Remote end. The process is divided into three phases: A, B, and C. Phase A involves SIP INVITE and 183 Session Progress. Phase B involves Setup, IAM, ANS, and Connect messages, with a note that eMSC assigns and sends the Public User Identity. Phase C involves PS session information, Application level request, IP CAN Session Request, Create Bearer Request, and Create CS session Request/Response. A note indicates that SGSN checked QCI and MGW IP address information. Another note indicates that a Tanscoder in MGW converts Voice media format if needed. The diagram also shows the establishment of CS and PS bearers.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +The diagram illustrates the call origination procedure in GERAN/UTRAN, showing the sequence of messages between various network elements. The participants are: UE, RNS, eNB, MSC, SGSN, MSC for SRVCC, SGW, PGW, PCRF, SCC AS (IMS), and Remote end. + +**Sequence of Messages:** + +- UE sends 1. SIP (INVITE, M=AMR, rSRVCC flag) over the default bearer to Remote end. +- Remote end sends 2. 183 Session Progress to SCC AS (IMS). +- UE sends 3. Setup (Called #, SRVCC MSC #) to MSC. +- MSC sends 4. IAM (Called # = SRVCC MSC #) to MSC for SRVCC. +- MSC for SRVCC sends 5. ANS to MSC. +- MSC sends 6. Connect to UE. +- MSC for SRVCC sends 7. PS session information (MGW IP address, Public User Identity) to SCC AS (IMS). *Note: eMSC assigns and sends the Public User Identity in order to correlate CS bearer and PS bearer when eMSC receives message #13.* +- SCC AS (IMS) sends 8. Application level request (SDP related information, MGW IP address, Public User Identity) to PGW. +- PGW sends 9. IP CAN Session Request (SDP related information, MGW IP address, Public User Identity) to PCRF. +- PCRF sends 10. Create Bearer Request (QCI=1, SDP related information, MGW IP address, Public User Identity) to SGW. +- SGW sends 11. Create Bearer Request (QCI=1, SDP related information, MGW IP address, Public User Identity, SGW IP address, TEID for VoIP media) to MSC for SRVCC. *Note: SGSN checked QCI and MGW IP address information.* +- MSC for SRVCC sends 12. Create CS session Request (QCI=1, SDP related information, Public User Identity, SGW IP address, TEID for VoIP media) to MSC. +- MSC sends 13. Create CS session Response (MGW IP address, TEID for VoIP media) to MSC for SRVCC. +- MSC for SRVCC sends 14. Create Bearer Response (MGW IP address, TEID for VoIP media) to SGW. +- SGW sends 15. Create Bearer Response (SGW IP address, TEID for VoIP media) to PGW. +- PGW sends 16. Ack. to SCC AS (IMS). +- SCC AS (IMS) sends 17. Ack. to Remote end. +- Remote end sends 18. UPDATE to SCC AS (IMS). +- SCC AS (IMS) sends 19. 200 OK to Remote end. + +**Bearers:** + +- CS Bearer:** Established between UE and MSC for SRVCC. +- PS Bearer:** Established between UE and PGW. + +**Notes:** + +- eMSC assigns and sends the Public User Identity in order to correlate CS bearer and PS bearer when eMSC receives message #13.* +- SGSN checked QCI and MGW IP address information.* +- Tanscoder in MGW converts Voice media format if needed.* + +Sequence diagram of call origination procedure in GERAN/UTRAN. The diagram shows interactions between UE, RNS, eNB, MSC, SGSN, MSC for SRVCC, SGW, PGW, PCRF, SCC AS (IMS), and Remote end. The process is divided into three phases: A, B, and C. Phase A involves SIP INVITE and 183 Session Progress. Phase B involves Setup, IAM, ANS, and Connect messages, with a note that eMSC assigns and sends the Public User Identity. Phase C involves PS session information, Application level request, IP CAN Session Request, Create Bearer Request, and Create CS session Request/Response. A note indicates that SGSN checked QCI and MGW IP address information. Another note indicates that a Tanscoder in MGW converts Voice media format if needed. The diagram also shows the establishment of CS and PS bearers. + +**Figure 6.4.2.2-1: Call origination procedure in GERAN/UTRAN** + +NOTE: Steps in A and B can be performed in parallel. Steps in C is triggered by SCC AS after completing both steps A and B. + +- UE sends the INVITE message with the rSRVCC flag in SIP header if UE wishes to perform HO to IMS in case it would be necessary during a call. +- When SCC AS receives the 183 Session Progress message from peer end, SCC AS checks the rSRVCC flag. If eSRVCC flag is active, then SCC AS waits for the step 7 to arrive and initiate step 8. +- UE sends the setup message over the NAS signal. This message triggers the establishment of the CS bearer from UE to MSC for SRVCC via MSC. This setup message has the SRVCC MSC number in order to reach to the MSC Server/MGW enhanced for SRVCC. Alternatively, called number with prefix could also route to the MSC Server/MGW enhanced for SRVCC. This step can be initiated parallel with the step 1. +- MSC sends the IMS message to the MSC Server/MGW enhanced for SRVCC. +- The MSC Server/MGW enhanced for SRVCC sends ANSWER message to MSC. +- The MSC sends connect message to UE. The voice path in the CS domain is established at this point. The MGW waits the Create CS Session Request message (Step 10) to come if the MGW has not received the Create CS Session Request message. + +7. The MSC Server/MGW enhanced for SRVCC sends the PS session information to the SCC AS. This message contains the MGW IP address information and the Public User Identity. The MGW IP address is used in SGSN to contact to the right MGW that terminates the voice path in CS domain. The MSC Server/MGW enhanced for SRVCC assigns the SRVCC specific Public User Identity as the similar way as the ICS enhanced MSC server as described in the 3GPP TS 23.292 [3]. +8. Once SCC AS receives the 183 Session Progress message, SCC AS send Application level request to the PCRF in order to reserves the network resources for VoIP communication. This message carries the SDP related information, the MGW IP address information and the Public User Identity. +9. The PCRF sends the IP CAN Session request message to the PGW in order to enforce a PCC rule. This message carries the SDP related information, the MGW IP address information and the Public User Identity. +10. The PGW sends the Create Bearer Request message to the SGW. This message carries the SDP related information, the MGW IP address information and the Public User Identity. +11. The SGW sends the Create Bearer Request message to the SGSN. In addition to the SDP related information, the MGW IP address information and the Public User Identity, SGW adds the IP address and TEID for VoIP communication. +12. If the MGW IP address is included in the Create Bearer Request message, the SGSN sends the Create CS Session Request message to the MGW using the MGW IP address received in the step 11. This message carries the SGW IP address, TEID, SDP related information and the Public User Identity. The MGW correlates with the CS voice path that is made by stem 3 to 6 by using the Public User Identity. The SDP related information includes codec related information, routing information to the remote end, etc. The codec related information is used when MGW performs a voice media transcoding. +13. The MGW sends the Create CS session response to the SGSN. This message carries the MGW IP address and TEID to be used for VoIP communication. +14. The SGSN sends the Create bearer response to the SGW. This message carries the MGW IP address and TEID to be used for VoIP communication between the MGW and the SGW. +15. The SGW sends the Create bearer response to the PGW. +16. The PGW sends the acknowledge message to the PCRF. +17. The PCRF sends the acknowledge message to the SPCC AS +18. Once SCC AS receives the Acknowledge message in step 15. The SCC AS sends the UPDATE message to the remote end to inform that all necessary resources has been allocated. +19. The remote end send 200 OK for reply to the message in step 16. + +#### 6.4.2.3 Call termination procedure in GERAN/UTRAN + +In case rSRVCC capable UE determines to establish rSRVCC call, the following procedure takes place. + +![Sequence diagram for call termination procedure in GERAN/UTRAN. Lifelines: UE, RNS, eNB, MSC, SGSN, MSC for SRVCC, SGW, PGW, PCRF, SCC AS (IMS), Remote end. The diagram shows steps 1 through 7, followed by a box indicating the continuation of the C part from Figure 6.4.2.2-1.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNS + participant eNB + participant MSC + participant SGSN + participant MSC for SRVCC + participant SGW + participant PGW + participant PCRF + participant SCC AS (IMS) + participant Remote end + + Note left of UE: C part in Figure 6.4.2.2-1 continues + + UE->>Remote end: 1. SIP (INVITE, M=AMR over the default bearer) + Remote end-->>UE: 2. 183 Session Progress (rSRVCC flag) + UE->>MSC: 3. Setup (Called #, SRVCC MSC #) + MSC->>MSC for SRVCC: 4. IAM (Called # = SRVCC MSC #) + MSC for SRVCC-->>MSC: 5. ANSWER + MSC->>UE: 6. Connect + MSC for SRVCC->>SCC AS (IMS): 7. PS session information (MGW IP address, Public User Identity) + +``` + +Sequence diagram for call termination procedure in GERAN/UTRAN. Lifelines: UE, RNS, eNB, MSC, SGSN, MSC for SRVCC, SGW, PGW, PCRF, SCC AS (IMS), Remote end. The diagram shows steps 1 through 7, followed by a box indicating the continuation of the C part from Figure 6.4.2.2-1. + +**Figure 6.4.2.3-1: Call termination procedure in GERAN/UTRAN** + +1. UE receives the INVITE message. +2. If UE wishes to perform HO to IMS in case it would be necessary during a call, UE sends the 183 Session Progress message with the rSRVCC flag in SIP header. When SCC AS receives the 183 Session Progress message from UE, SCC AS checks the rSRVCC flag. If rSRVCC flag is active, then SCC AS initiates step 8 in the Figure 6.4.2.2-1 after waiting for step 7 arrived. +3. UE sends the setup message over the NAS signal. This setup message has the SRVCC MSC number in order to reach to the MSC Server/MGW enhanced for SRVCC. Alternatively, called number with prefix could also route to the MSC Server/MGW enhanced for SRVCC. This step can be initiated parallel with the step 1. +4. MSC sends the IMS message to the MSC Server/MGW enhanced for SRVCC. +5. The MSC Server/MGW enhanced for SRVCC sends ANSWER message to MSC. +6. The MSC sends connect message to UE. The voice path in the CS domain is established at this point. The MGW waits the Create CS Session Request message (Step 10) to come if the MGW has not received the Create CS Session Request message. +7. The MSC Server/MGW enhanced for SRVCC sends the PS session information to the SCC AS. This message contains the MGW IP address information. The MGW IP address is used in SGSN to contact to the right MGW that terminates the voice path in CS domain. + +After step 7, The C part in the Figure 6.4.2.2-1 continues. + +#### 6.4.2.4 SRVCC handover from UTRAN or GERAN to LTE + +This procedure is basically same as the UTRAN to E-UTRAN Inter RAT HO procedure as described in TS 23.401 [5]. The deltas are indicated in RED font in the Figure 6.4.2.4-1. + +![Sequence diagram for SRVCC handover from UTRAN or GERAN to LTE. The diagram shows the interaction between UE, RNS, eNB, MME, SGSN, MSC for SRVCC, SGW, PGW, PCRF, SCC AS (IMS), and Remote end. It details the steps for handover preparation, execution, and completion, including bearer management (CS and PS) and indirect data forwarding tunnel creation/deletion.](7ed5d5770331f31ade15439a21c31425_img.jpg) + +The sequence diagram illustrates the SRVCC handover process from UTRAN or GERAN to LTE. The participants involved are UE, RNS, eNB, MME, SGSN, MSC for SRVCC, SGW, PGW, PCRF, SCC AS (IMS), and Remote end. The process begins with the RNS sending a 'Handover Required' message to the SGSN. The SGSN then sends a 'Forward Relocation Request (CS indication)' to the MME. The MME sends a 'Handover Request' to the eNB, which includes the addition of a VoIP bearer. The eNB responds with a 'Handover Request Ack.' to the MME. The MME sends a 'Forward Relocation Response' to the SGSN. The SGSN then sends a 'Create Indirect Data Forwarding Tunnel Request' to the SGW, which does not include VoIP media. The SGW responds with a 'Create Indirect Data Forwarding Tunnel Response' to the SGSN. The SGSN sends a 'Relocation command' to the RNS, indicating that no VoIP media is included for indirect data forwarding. The RNS sends a 'HO command' to the UE. The UE moves to LTE and sends an 'HO to E-UTRAN complete' message to the eNB. The eNB sends an 'HO notify' message to the MME. The MME sends a 'Forward Relocation Complete Notification' to the SGSN. The SGSN responds with a 'Forward Relocation Complete Ack.' to the MME. The MME sends a 'Modify Bearer Request' to the SGW, which includes the VoIP bearer. The SGW responds with a 'Modify Bearer Response' to the MME. The MME then sends a 'Delete Indirect Data Forwarding Tunnel Request' to the SGW, which does not include VoIP media. The SGW responds with a 'Delete Indirect Data Forwarding Tunnel Request' to the MME. + +Sequence diagram for SRVCC handover from UTRAN or GERAN to LTE. The diagram shows the interaction between UE, RNS, eNB, MME, SGSN, MSC for SRVCC, SGW, PGW, PCRF, SCC AS (IMS), and Remote end. It details the steps for handover preparation, execution, and completion, including bearer management (CS and PS) and indirect data forwarding tunnel creation/deletion. + +**Figure 6.4.2.4-1: SRVCC handover from UTRAN or GERAN to LTE** + +1. Depending on the radio condition, RNS sends the Handover Required message to SGSN. Note that RNS does send the Handover Required message to MSC since there is no CS domain available in the LTE. + +**Editor's Note: How RNS decides to send Handover Required message to SGSN is FFS.** + +2. SGSN sends the Forward Relocation Request message to the MME with the CS indication. The CS indication indicates that the Voice media exists in CS domain and needs to be handed over the LTE. + +3. MME sends the Handover Request message to eNB. eNB reserves all necessary bearer resources including a bearer resources for the VoIP media. + +**Editor's Note: Voice bearer is created by the separate bearer establishment procedure and the detail is FFS.** + +4. eNB sends the Handover Request Ack message to the MME. + +5. MME sends the Forward Relocation Response message to the SGSN. This message contains the eNB IP address and TEID for VoIP media. + +6. MME sends the Create Indirect Data Forwarding Tunnel Request message to the SGW. This message does not create the indirect data tunnel for VoIP media since indirect data forwarding is not performed for VoIP media. + +7. SGW sends the Create Indirect Data Forwarding Tunnel Response message to the MME. + +8. SGSN sends the Relocation command message to the RNS to command hand over to the LTE. +9. RNS sends HO command to the UE. +10. SGSN sends the Redirect request to the MSC Server/MGW enhanced for SRVCC. This message contains the eNB IP address and TEID that to be used for VoIP media. This message can be sent after the SGSN receives the Forward Relocation Response message from MME. When the MSC Server/MGW enhanced for SRVCC receives this message, the MSC Server/MGW enhanced for SRVCC starts sending DL voice data to the eNB. The MSC Server/MGW enhanced for SRVCC may optionally bi-cast DL voice to both MSC and eNB. + +The MSC Server/MGW enhanced for SRVCC starts the release procedure toward the CS domain after a configurable time has passed. This process is not shown in this flow. + +11. After UE tunes to the LTE, UE sends the HO to E-UTAN complete message to the eNB. +12. eNB sends HO notify to the MME. +13. MME sends the Forward Relocation Complete Notification message to the SGSN. +14. SGSN sends the Forward Relocation Complete Ack message to MME. +15. MME sends the Modify Bearer Request to the SGW. This message includes the eNB TEID for VoIP media. + +NOTE: eNB TEID information is already available at step 4. + +16. SGW sends the Modify Bearer Response to the MME. +17. SGSN sends the Delete Indirect Data Forwarding Tunnel Request to the SGW. This message does not include the bearer information for VoIP media. +18. SGW sends the Delete Indirect Data Forwarding Tunnel Response to the SGSN. + +## 6.5 Solution 5: IMS procedure is initiated by MSC Server to ATCF + +### 6.5.1 Architecture Reference Model + +#### 6.5.1.1 General + +Figure 6.5.1.1-1 provides the reference architecture for reverse SRVCC. The figure only depicts the specific reference points for reverse SRVCC. + +![Reference Architecture for reverse SRVCC diagram](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +``` + +graph TD + SCC_AS[SCC AS] -- ISC --> IS_CSCF[I/S-CSCF] + IS_CSCF -- Mw/Mx --> ATCF[ATCF*] + ATCF -- Mw/Mx --> PCSCF[P-CSCF] + ATCF -- I2 --> MSC_Server[MSC Server] + ATCF --- ATGW[ATGW*] + PCSCF -- Gm --> UE[UE] + UE --- CS_Access[CS Access] + CS_Access --- MSC_Server + MSC_Server -- Sv --> MME[MME] + MSC_Server -- Gn/S4 --> SGSN[SGSN] + +``` + +The diagram illustrates the reference architecture for reverse SRVCC. At the top, the SCC AS (Service Centralization and Continuity Application Server) is connected to the I/S-CSCF (Interrogating/Serving CSCF) via the ISC interface. The I/S-CSCF is connected to the ATCF\* (Access Transfer Control Function) via the Mw/Mx interface. The ATCF\* is connected to the P-CSCF (Proxy-CSCF) via the Mw/Mx interface and to the ATGW\* (Access Transfer Gateway) via a direct connection. The P-CSCF is connected to the UE (User Equipment) via the Gm interface. The UE is also connected to the CS Access (Circuit Switched Access). The CS Access is connected to the MSC Server (Mobile Switching Center Server). The MSC Server is connected to the ATCF\* via the I2 interface and to the SGSN (Serving GPRS Support Node) via the Gn/S4 interface. The MSC Server is also connected to the MME (Mobility Management Entity) via the Sv interface. A note below the diagram states: "\*: Location of functionality depends on deployment and collocation scenario". + +Reference Architecture for reverse SRVCC diagram + +\*: Location of functionality depends on deployment and collocation scenario + +NOTE 1: MSC Server shown in the figure is enhanced for reverse SRVCC + +NOTE 2: The MSC server enhanced for reverse SRVCC may not be the source MSC which connects to the source cell. + +**Figure 6.5.1.1-1: Reference Architecture for reverse SRVCC.** + +#### 6.5.1.2 Concepts of reverse SRVCC + +For facilitating session transfer (reverse SRVCC) of the voice component to the PS domain, the IMS multimedia telephony sessions needs to be anchored in the IMS (ATCF). + +For reverse SRVCC from UTRAN/GERAN to E-UTRAN/UTRAN (HSPA), MSC Server enhanced for reverse SRVCC receives the CS handover request of UTRAN/GERAN with the indication that whether PS handover is initiated and this is for reverse SRVCC handling. If PS handover is initiated, the Source SGSN sends PS handover request to the MSC Server enhanced for reverse SRVCC. MSC Server enhanced for reverse SRVCC synchronises the CS and PS handover requests and triggers the CS to PS Handover procedure with the target MME via the Sv reference point. MSC Server enhanced for reverse SRVCC then initiates the session transfer procedure to IMS (ATCF) and coordinates it with the CS to PS Handover SRVCC procedure. Target MME then sends CS to PS handover Response to MSC Server enhanced for reverse SRVCC, which includes all the components information including voice for the UE to access the E-UTRAN/UTRAN (HSPA). After UE tunes to the target access, it initiates the session transfer procedure to IMS (ATCF), and ATCF coordinates the two session transfer procedures. + +![Sequence diagram illustrating the overall high level concepts for reverse SRVCC. The diagram shows the interaction between UE, UTRAN/GERAN, SGSN, MSC Server, C2PHF, Target E-UTRAN/UTRAN(HSPA), and IMS (ATCF). The process starts with Measurement Reports from UE to UTRAN/GERAN. UTRAN/GERAN sends 'Handover CS to target required' to SGSN. SGSN sends 'Handles PS-PS HO for non-voice if needed, and sends Forward Relocation request to MSC Server' to MSC Server. MSC Server sends 'Initiates CS to PS handover for all component(s)' to C2PHF. C2PHF sends 'IMS Service Continuity Procedure' to Target E-UTRAN/UTRAN(HSPA). Target E-UTRAN/UTRAN(HSPA) sends 'PS handover preparation for voice and non-voice if needed' to MSC Server. MSC Server sends 'PS HO response to MSC Server (PS resources)' to C2PHF. C2PHF sends 'To UTRAN/GERAN' to SGSN. SGSN sends 'Handover CMD' to UE. UE performs 'Handover execution'. Finally, IMS Service Continuity Procedure is shown as a long-duration interaction between IMS (ATCF) and Target E-UTRAN/UTRAN(HSPA).](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +Sequence diagram illustrating the overall high level concepts for reverse SRVCC. The diagram shows the interaction between UE, UTRAN/GERAN, SGSN, MSC Server, C2PHF, Target E-UTRAN/UTRAN(HSPA), and IMS (ATCF). The process starts with Measurement Reports from UE to UTRAN/GERAN. UTRAN/GERAN sends 'Handover CS to target required' to SGSN. SGSN sends 'Handles PS-PS HO for non-voice if needed, and sends Forward Relocation request to MSC Server' to MSC Server. MSC Server sends 'Initiates CS to PS handover for all component(s)' to C2PHF. C2PHF sends 'IMS Service Continuity Procedure' to Target E-UTRAN/UTRAN(HSPA). Target E-UTRAN/UTRAN(HSPA) sends 'PS handover preparation for voice and non-voice if needed' to MSC Server. MSC Server sends 'PS HO response to MSC Server (PS resources)' to C2PHF. C2PHF sends 'To UTRAN/GERAN' to SGSN. SGSN sends 'Handover CMD' to UE. UE performs 'Handover execution'. Finally, IMS Service Continuity Procedure is shown as a long-duration interaction between IMS (ATCF) and Target E-UTRAN/UTRAN(HSPA). + +**Figure 6.5.1.2-1: Overall high level concepts for reverse SRVCC** + +### 6.5.2 Functional Entities + +#### 6.5.2.1 ATCF + +The ATCF shall be based on the functionality specified in TS 23.237 [4], with the following enhancements: + +NOTE 1: For transferring emergency session, the ATCF can be co-located with E-SCC AS. + +- Based on operator policy, decide to + - allocate a STN-rSR; +- Perform the Access Transfer and update the ATGW with the new media path for the new (PS) access leg, without requiring updating the remote leg; +- Make anchoring decision with additional criteria of UE's reverse SRVCC capability; +- Forward the originating call destined to an IMRN pointing to the ATCF; +- Forward the terminating call to CS domain if CS identity is received for the call; +- Inform the MSC Server enhanced for rSRVCC that the Access Transfer is success after response to the Session Transfer message sent by UE; +- Correlate the Session Transfer procedures initiated by the UE and the MSC server enhanced for rSRVCC. + +#### 6.5.2.2 SCC AS + +The SCC AS shall be based on the functionality specified in TS 23.237 [4], with the following enhancements: + +- Clear any existing STN-rSR that has been set to the HSS if a third-party register without a STN-rSR is received; +- Provide the STN-rSR received in a third-party register to the HSS; +- When an ATCF is used, provide during session establishment the PUI registered by the UE to the ATCF; +- If the session is originated from CS domain, instruct the serving network to redirect the call to an number point to the ATCF or instruct the serving network to resend the call via the ATCF, which allocates the STN-rSR; +- Route the call to the ATCF during terminating session establishment if T-ADS selects CS domain. + +- Monitor the IMS re-registration of the UE as described in clause 6.5.3.4 and inform the HSS to de-register the UE if needed. + +#### 6.5.2.3 S-CSCF + +The S-CSCF shall perform IMS Registration procedure for the rSRVCC UE as described in clause 6.5.3.6. + +#### 6.5.2.4 MSC Server enhanced for reverse SRVCC + +The MSC Server enhance for reverse SRVCC shall be based on the functionality specified in TS 23.216 [7] and TS 23.292 [3], with the following enhancements: + +- Perform the session transfer procedure or emergency session transfer procedure from CS to IMS as described in clause 6.5.3.9.1; +- Initiating the CS to PS handover procedure for handover of the voice component to the target cell via the Sv interface and including an emergency indication if this is an emergency session. This procedure is only triggered once regardless of the number of CS sessions those are in use by the UE. +- Coordinating the CS to PS handover and session transfer procedures; +- Not perform MAP\_Update\_Location procedure for CS to PS handover procedure; +- Synchronize PS handover and CS handover procedures when both procedures are performed. + +#### 6.5.2.5 MME + +The MME shall be based on the functionality specified in TS 23.401 [5], with the following enhancements: + +- Handling the Relocation Preparation procedure requested from MSC Server enhanced for rSRVCC via Sv reference point; +- Perform the bearer reservation procedure for voice media in target access as described in clause 6.5.3.9.2; + +#### 6.5.2.6 UE enhanced for reverse SRVCC + +The rSRVCC UE shall: + +- Indicate to the IMS that the UE is rSRVCC capable when being configured for using IMS speech service supported by the home operator, e.g. the IMS Multimedia Telephony Service for bi-directional speech and the operator policy on the rSRVCC UE as specified in TS 23.237 [4] does not restrict the session transfer. +- Initiate RAU/LAU procedure to indicate the GERAN/UTRAN that the user is allowed to use rSRVCC. +- Initiate a Session Transfer procedure as described in TS 23.237 [4] after handover to the target access is completed. +- Perform IMS Registration procedure as described in clause 6.5.3.6. + +#### 6.5.2.7 UTRAN/GERAN + +When UTRAN/GERAN selects a target VoIP-capable cell for CS to PS handover, it needs to send an indication to SGSN that this handover procedure requires rSRVCC. + +UTRAN/GERAN may be capable of determining the neighbour cell list based on the allowance of rSRVCC and/or presence of CS sessions for a specific UE as described in clause 6.5.3.2. + +### 6.5.3 Message Flows + +#### 6.5.3.1 Home control rSRVCC + +When the S-CSCF receives IMS registration from a rSRVCC UE, it shall send the rSRVCC subscription information of the user to the UE if it exists. After receiving the rSRVCC subscription information, the UE shall perform RAU/LAU/TAU procedure depends on where it attaches to send an "rSRVCC allowed" indication to the NB/eNB. + +#### 6.5.3.2 RAU/LAU/TAU procedure + +RAU/LAU/TAU procedure for 3GPP rSRVCC UE is performed as defined in TS 23.060 [6] or TS 23.401 [5] with the following additions: + +- NB/eNB receives "rSRVCC allowed" indication as part of the "UE Radio Access Capability". NB/eNB stores this information for rSRVCC operation. + +NOTE 1: If the indication is populated by core network, considering not all MSC Server/SGSN need to be enhanced for rSRVCC, if UE initiates CS session with that MSC Server and performs CS handover, this indication will be lost in target NB. + +When UE attaches to GERAN/UTRAN, if the "rSRVCC allowed" indication is set to "true" and/or the UE is involved in CS session, then VoIP-capable cells may be included as candidate target cells in the NCL. + +NOTE 2: The UE will receive the "rSRVCC allowed" indication via IMS registration procedure. + +#### 6.5.3.3 GERAN/UTRAN performs handover procedure + +If the GERAN/UTRAN decides to handover the UE with CS session to a VoIP-capable cell, it shall include an rSRVCC indication in the Handover/Relocation Required message for CS handover, and for PS handover if happened, and destine the Handover/Relocation Required message for CS handover to a MSC Server enhanced for rSRVCC. + +Annex Y shows an example of how the GERAN/UTRAN packs the rSRVCC indication. + +#### 6.5.3.4 Maintaining IMS Registration + +During the IMS (re-)registration procedure, The UE shall send a SIP REGISTER request with an additional time interval $T_{\text{maintain}}$ to IMS to maintain IMS registration when UE is involved in CS session. The time interval for IMS re-registration is called $T_{\text{Registration}}$ . In order not to impact P-CSCF, the $T_{\text{maintain}}$ shall be included in the Expires header field of the SIP REGISTER request and the response. + +The S-CSCF shall not reduce the $T_{\text{maintain}}$ if the 3rd party registration needs to be performed to a SCC AS. The S-CSCF may reduce the $T_{\text{Registration}}$ according to local policy. The S-CSCF shall forward the $T_{\text{Registration}}$ to the SCC AS via 3rd party registration procedure and forward the $T_{\text{Registration}}$ to the UE, e.g. by including the $T_{\text{Registration}}$ in the response to the SIP REGISTER request. + +The SCC AS may hold a time interval $T_{\text{Transfer}}$ corresponding to the approximate transfer time of the SIP REGISTER request. The SCC AS shall reset the time interval for monitoring IMS re-registration to ( $T_{\text{Registration}} + T_{\text{Transfer}}$ ) when all CS sessions of the UE has been released or the UE re-registration has been informed, and stop monitoring the IMS re-registration when CS session of the UE can be detected. If the time expired, the SCC AS shall inform the HSS to de-register the UE. + +#### 6.5.3.5 Preparation of media transfer + +UE need to transfer VoIP media right after CS to PS handover procedure described in clause 6.5.3.9.2 is finished. The ATCF and/or MSC Server enhanced for rSRVCC needs to know the IP address and port number used by the UE for receiving media on PS access during CS-PS access transfer. The UE needs to know the IP address, port number and codec for sending media to the ATGW during CS-PS access transfer. + +The IP address of the UE is assigned by the network and used for IMS registration procedure. When registering in the IMS, the UE indicates its port number and default codec (or list of codecs) it will receive media on when a transfer is performed. The ATCF can learn this information during IMS registration procedure, and therefore forward the information, as well as the IP address/port of the ATGW for receiving voice media, to the MSC Server enhanced for rSRVCC during CS-PS access transfer as described in clause 6.5.3.9. + +#### 6.5.3.6 Selection of the ATCF + +In order to ensure that the MSC Server selects the ATCF during rSRVCC procedure, who may anchor the session, a STPN-rSR (Session Transfer Number for rSRVCC) that can be used by the MSC Server to find the ATCF shall be provided to the serving MSC Server before rSRVCC procedure is triggered. + +The ATCF shall allocate the STPN-rSR when the user registers in the IMS. The STN-rSR shall be provided through IMS and via third-party registration to the SCC AS. The SCC AS shall further provide the modified C-MSISDN with prefix of STN-rSR to the HSS, which in turn shall update the serving MSC Server. + +NOTE 1: The STN-rSR is not a routable number, and maybe part of the STN-SR. If the SCC AS receives a third-party register without a STPN-rSR, it will remove any prefix of the C-MSISDN. + +The following figure shows an example of IMS registration flow where the ATCF provides the STN-rSR to the home network. Existing IMS Registration procedures described in TS 23.228 [11] are used to register the user in IMS. + +![Sequence diagram of IMS Registration flow. Lifelines: UE, MSC, ATCF, SN/HN (dashed line), I/S-CSCF, HSS, SCC AS. The sequence starts with UE sending a Registration (rSRVCC capability) to ATCF. ATCF sends a Decision to be included to MSC. ATCF then sends a Registration (STN-rSR) to I/S-CSCF. I/S-CSCF sends a Registration (STN-rSR) to SCC AS. SCC AS sends a Sh-update (C-MSISDN) to HSS. HSS sends an Insert Subscription Data (C-MSISDN) to MSC. Finally, MSC sends a Registration to I/S-CSCF, which in turn sends a Registration to SCC AS.](4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MSC + participant ATCF + participant SN_HN as SN | HN + participant I_S_CSCF as I/S-CSCF + participant HSS + participant SCC_AS as SCC AS + + Note right of ATCF: 2. Decision to be included + + UE->>ATCF: 1. Registration (rSRVCC capability) + ATCF->>MSC: 2. Decision to be included + ATCF->>I_S_CSCF: 3. Registration (STN-rSR) + I_S_CSCF->>SCC_AS: 4. Registration (STN-rSR) + SCC_AS->>HSS: 5. Sh-update (C-MSISDN) + HSS->>MSC: 6. Insert Subscription Data (C-MSISDN) + MSC->>I_S_CSCF: 7. Registration + I_S_CSCF->>SCC_AS: 8. Registration + +``` + +Sequence diagram of IMS Registration flow. Lifelines: UE, MSC, ATCF, SN/HN (dashed line), I/S-CSCF, HSS, SCC AS. The sequence starts with UE sending a Registration (rSRVCC capability) to ATCF. ATCF sends a Decision to be included to MSC. ATCF then sends a Registration (STN-rSR) to I/S-CSCF. I/S-CSCF sends a Registration (STN-rSR) to SCC AS. SCC AS sends a Sh-update (C-MSISDN) to HSS. HSS sends an Insert Subscription Data (C-MSISDN) to MSC. Finally, MSC sends a Registration to I/S-CSCF, which in turn sends a Registration to SCC AS. + +**Figure 6.5.3.6-1: IMS Registration** + +1. UE sends an initial SIP REGISTER request with rSRVCC capability indication to home network via ATCF (P-CSCF not shown in flow). The rSRVCC capability indication is the additional time interval, reserved port, and default codec (or list of codecs). + +2. ATCF decides, based on operator policy and in case the home network supports rSRVCC, to allocate a STPN-rSR. + +3. The ATCF includes the STN-rSR in the request forwarded to the I/S-CSCF. + +NOTE 2: Service level agreements are used to understand whether the home network supports rSRVCC. + +4. The I/S-CSCF sends the SIP REGISTER request to the SCC AS according to the third-party registration procedure. The S-CSCF shall forward the rSRVCC subscription information to the UE, e.g. by including this information in the response to the SIP REGISTER request. If the UE receives the information, it shall trigger RAU/LAU/TAU immediately to set the rSRVCC allowed indication to "true". + +NOTE 3: In case of multiple registrations from the UE from multiple accesses, the SCC AS will only receive and use a STPN-rSR from an ATCF in the mobile network. + +5. SCC AS uses the STN-rSR as the prefix of C-MSISDN and provides the modified C-MSISDN into the HSS. + +NOTE 4: If an ATCF does not exist, the SCC AS will remove the prefix of C-MSISDN and provide the modified C-MSISDN in the HSS. + +6. If the UE attached in GERAN/UTRAN, HSS provides the STN-rSR as prefix of C-MSISDN to the serving MSC Server because of the change of the subscription data. + +7-8. If MSC Server is enhanced for ICS, the MSC Server will perform IMS registration for the UE too, and if the MSC Server also is enhanced for rSRVCC, the SIP REGISTER request may go through the ATCF determined by the STN-rSR. + +#### 6.5.3.7 Originating sessions in CS + +##### 6.5.3.7.1 Serving MSC Server is not enhanced for ICS + +Figure 6.5.3.7.1-1 shows an originating session when the ATCF has previously been included in the signalling path (see clause 6.5.3.6) and serving MSC Server is not enhanced for ICS. If the ATCF was not included in the signalling path then existing Mobile Origination procedures described in TS 23.228 [11] are used. + +![Sequence diagram for Figure 6.5.3.7.1-1: Originating session that uses only CS media (MSC Server not supporting ICS).](cc542843836eecb036b99cb270b54a1e_img.jpg) + +The diagram illustrates the signaling sequence for an originating session. The participants are UE-1, MSC Server, ATCF, ATGW, SN | HN, I/S-CSCF, SCC AS, and UE-2. The sequence of messages is as follows: + +- UE-1 sends a **1. SETUP** message to the MSC Server. +- The MSC Server sends a message to fetch the IMRN from the HPLMN. The HPLMN returns an IMRN pointing to the ATCF according to the STN-rSR. +- The MSC Server sends a **2. IAM/INVITE** message to the ATCF. +- The ATCF **Decides to anchor and allocate ATGW resources**. +- The ATCF sends a **3. INVITE (IMRN)** message to the I/S-CSCF. +- The I/S-CSCF sends a **4. INVITE (IMRN)** message to the SCC AS. +- The SCC AS sends a **5. INVITE** message to the I/S-CSCF. +- The I/S-CSCF sends a **6. INVITE** message to UE-2. +- The SCC AS sends **7. Transfer Info (ATU-STI, UE PUI, C-MSISDN)** to the ATCF. +- The ATCF sends **8. Transfer Info (ATU-STI, UE PUI, C-MSISDN)** to the MSC Server. +- The final step is the **9. Completion of originating session setup**. + +Below the sequence, the media path is shown as: **CS media** (UE-1 to MSC Server), **Remote media path** (MSC Server to ATCF), and **PS media** (ATCF to UE-2). + +Sequence diagram for Figure 6.5.3.7.1-1: Originating session that uses only CS media (MSC Server not supporting ICS). + +**Figure 6.5.3.7.1-1: Originating session that uses only CS media (MSC Server not supporting ICS)** + +- UE-1 sends a SETUP message in CS domain to initiate a CS call to UE-2. +- MSC Server not supporting ICS fetches IMRN from UE-1's home network with terminating number in order to forward the session establishment message to IMS. SCC AS derives an IMRN pointing to the ATCF based on the STN-rSR and roaming agreement. The MSC Server sends an ISUP IAM or SIP INVITE message to the ATCF using the IMRN via a local MGCF. +- 3~4. The ATCF decides to anchor based on local policy and allocates ATGW resources and forwards the SIP INVITE message to the I/S-CSCF of the UE-1's home network. The S-CSCF will forward the SIP INVITE message to the SCC AS according to the originating iFC. +- 5~6. SCC AS changes the request URI of the SIP INVITE request to the terminating number and forwards the SIP INVITE request to the remote UE. +- 7~8. SCC AS sends Access Transfer Info with a dynamic/static ATU-STI, the UE PUI registered by the UE, and the C-MSISDN. The ATCF shall store the Access Transfer Info. + +NOTE 1: The Access Transfer Info (step 7 and 8) can be sent as part of the existing session response (step 9) to the INVITE. + +NOTE 2: The ATU-STI is a routable address pointing to the SCC AS. It could either be dynamically allocated (for each session) or statically allocated (for the SCC AS). + +- Completion of originating session setup. + +##### 6.5.3.7.2 Serving MSC Server is enhanced for ICS + +Figure 6.5.3.7.2-1 shows an originating session when the ATCF has previously been included in the signalling path (see clause 6.5.3.6) and serving MSC Server is enhanced for ICS. If the ATCF was not included in the signalling path then existing Mobile Origination procedures described in TS 23.228 [11] are used. + +![Sequence diagram for originating session setup using only CS media with MSC Server supporting ICS. The diagram shows interactions between UE-1, MSC Server, ATCF, ATGW, SN/HN, I/S-CSCF, SCC AS, and UE-2. The process involves SETUP, INVITE, and Transfer Info messages, leading to the completion of session setup and the establishment of CS, Remote, and PS media paths.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +``` + +sequenceDiagram + participant UE-1 + participant MSC Server + participant ATCF + participant ATGW + participant SN/HN + participant I/S-CSCF + participant SCC AS + participant UE-2 + + Note right of ATCF: Decides to anchor and allocate ATGW resources + + UE-1->>MSC Server: 1. SETUP + MSC Server->>I/S-CSCF: 2. INVITE + I/S-CSCF->>SCC AS: 3. INVITE + SCC AS->>ATCF: 4. Use proxy of ATCF + ATCF->>MSC Server: 5. Use proxy of ATCF + MSC Server->>ATCF: 6. INVITE + Note right of ATCF: Decides to anchor and allocate ATGW resources + ATCF->>I/S-CSCF: 7. INVITE + I/S-CSCF->>SCC AS: 8. INVITE + SCC AS->>I/S-CSCF: 9. INVITE + I/S-CSCF->>UE-2: 10. INVITE + SCC AS->>I/S-CSCF: 11. Transfer Info (ATU-STI, UE PUI, C-MSISDN) + I/S-CSCF->>ATCF: 12. Transfer Info (ATU-STI, UE PUI, C-MSISDN) + Note over all: 13. Completion of originating session setup + + Note left of MSC Server: CS media + Note right of ATCF: Remote media path + Note right of I/S-CSCF: PS media + +``` + +Sequence diagram for originating session setup using only CS media with MSC Server supporting ICS. The diagram shows interactions between UE-1, MSC Server, ATCF, ATGW, SN/HN, I/S-CSCF, SCC AS, and UE-2. The process involves SETUP, INVITE, and Transfer Info messages, leading to the completion of session setup and the establishment of CS, Remote, and PS media paths. + +**Figure 6.5.3.7.2-1: Originating session that uses only CS media (MSC Server supporting ICS)** + +1. UE-1 sends a SETUP message in CS domain to initiate a CS call to UE-2. +- 2~3. MSC Server supporting ICS sends a SIP INVITE request to the I/S-CSCF of UE-1's home network, the S-CSCF will forward the SIP INVITE request to the SCC AS according to the originating iFC. +- 4~5. SCC AS determines the ATCF that UE-1 used for IMS registration based on the STN-rSR and roaming agreement. The SIP INVITE does not go through the ATCF, SCC AS informs the MSC Server to re-send the call via the ATCF. +6. The MSC Server re-sends the SIP INVITE request via the ATCF. +- 7~10. The ATCF decides to anchor based on local policy and allocates ATGW resources and forwards the SIP INVITE request to UE-2. +- 11~13. Same as described in step 7~9 of clause 6.5.3.7.1. + +##### 6.5.3.7.3 Serving MSC Server is enhanced for rSRVCC + +Figure 6.5.3.7.3-1 shows an originating session when the ATCF has previously been included in the signalling path (see clause 6.5.3.6) and serving MSC Server is enhanced for rSRVCC. If the ATCF was not included in the signalling path then existing Mobile Origination procedures described in TS 23.228 [11] are used. + +![Sequence diagram for Figure 6.5.3.7.3-1: Originating session that uses only CS media (MSC Server supporting rSRVCC).](fcc757566216206ceddbd6c775e8db02_img.jpg) + +``` + + UE-1 MSC Server ATCF ATGW SN | HN I/S-CSCF SCC AS UE-2 + | | | | | | | | + |--1. SETUP>| | | | | | | + | |--2. INVITE->| | | | | | + | | |Decides to anchor and| | | | + | | |allocate ATGW resources | | | + | | |---------| | | | | + | | | |--3. INVITE---------->| | | + | | | | | |--4. INVITE->| | + | | | | | |<-5. INVITE--| | + | | | | | |--6. INVITE------------>| + | | |<--8. Transfer Info-------------| | | + | | | (ATU-STI, UE PUI, | |--7. Transfer Info----->| | + | | | C-MSISDN) | |(ATU-STI, UE PUI, C-MSISDN) | + | | | | | | | | + | | |9. Completion of originating session setup | | + |<----------|-------------|---------|----------|-----------|------------|---------->| + | | | | | | | | + |<--CS media-->|<--Remote media path-->| |<----------PS media---------------->| + +``` + +Sequence diagram for Figure 6.5.3.7.3-1: Originating session that uses only CS media (MSC Server supporting rSRVCC). + +**Figure 6.5.3.7.3-1: Originating session that uses only CS media (MSC Server supporting rSRVCC)** + +1. UE-1 sends a SETUP message in CS domain to initiate a CS call to UE-2. +2. MSC Server supporting rSRVCC sends an SIP INVITE request to UE-2 via the ATCF. +- 3~6. The ATCF decides to anchor based on local policy and allocates ATGW resources and forwards the SIP INVITE request to UE-2. +- 7~9. Same as described in step 7~9 of clause 6.5.3.7.1. + +##### 6.5.3.7.4 UE is enhanced for ICS + +Figure 6.5.3.7.4-1 shows an originating session when the ATCF has previously been included in the signalling path (see clause 6.5.3.6) and UE is enhanced for ICS. If the ATCF was not included in the signalling path then existing Mobile Origination procedures described in TS 23.228 [11] are used. + +![Sequence diagram for Figure 6.5.3.7.4-1: Originating session that uses only CS media (UE supporting ICS).](2438c4dd81a8b76ec881d47d87b11fc3_img.jpg) + +``` + + UE-1 MSC Server ATCF ATGW SN | HN I/S-CSCF SCC AS UE-2 + | | | | | | | | + |--1. INVITE------------->| | | | | | + | | |--2. INVITE-------->| |--3. INVITE->| | + |<-6. Response (STNATCF)--|<-5. Response (STNATCF)-|<-4. Response (STNATCF)-| | + |--7. SETUP-| | | | | | | + | (STNATCF) |-8. IAM/INVITE->| | | | | | + | | |Decides to anchor and| | | | + | | |allocate ATGW resources | | | + | | |---------| | | | | + | | |--9. INVITE (STNATCF)---------->|--10. INVITE (STNATCF)->| | + | | | | | |<-11. INVITE-| | + | | | | | |--12. INVITE----------->| + | | |<--14. Transfer Info------------| | | + | | | (ATU-STI, UE PUI, | |--13. Transfer Info---->| | + | | | C-MSISDN) | |(ATU-STI, UE PUI, C-MSISDN) | + | | | | | | | | + | | |15. Completion of originating session setup | | + |<----------|-------------|---------|----------|-----------|------------|---------->| + | | | | | | | | + |<--CS media-->|<--Remote media path-->| |<----------PS media---------------->| + +``` + +Sequence diagram for Figure 6.5.3.7.4-1: Originating session that uses only CS media (UE supporting ICS). + +**Figure 6.5.3.7.4-1: Originating session that uses only CS media (UE supporting ICS)** + +- 1~3. UE-1 sends a SIP INVITE message via Gm/I1 interface in PS/CS domain to initiate a call to UE-2. If the SIP INVITE is sent via Gm interface, the SIP INVITE goes through ATCF. +- 4~6. SCC AS determines the ATCF that UE-1 used for IMS registration based on the STN-rSR and roaming agreement. SCC AS derives a dynamic STN pointing to the ATCF and responses to the SIP INVITE request with the dynamic STN to UE-1. +7. UE-1 sends a SETUP message in CS domain destined to the dynamic STN. +8. The MSC Server sends an ISUP IAM or SIP INVITE message to the ATCF using the dynamic STN. If the MSC Server is not enhanced for ICS, the message will be sent to the ATCF via a local MGCF. +- 9~10. The ATCF decides to anchor based on local policy and allocates ATGW resources and forwards the SIP INVITE message to the I/S-CSCF of the UE-1's home network. The S-CSCF will forward the SIP INVITE message to the SCC AS according to the originating iFC. +- 11~15. Same as described in step 5~9 of clause 6.5.3.7.1. + +#### 6.5.3.8 Terminating sessions in CS + +##### 6.5.3.8.1 UE is not enhanced for ICS + +Figure 6.5.3.8.1-1 shows a terminating session when the ATCF has previously been included in the signalling path (see clause 6.5.3.6) and UE is not enhanced for ICS. If the ATCF was not included in the signalling path then existing Mobile Termination procedures described in TS 23.228 [11] are used. + +![Sequence diagram for Figure 6.5.3.8.1-1: Terminating session that uses only CS media (UE not supporting ICS). The diagram shows the interaction between UE-1, MSC Server, ATCF, ATGW, SN/HN, I/S-CSCF, SCC AS, and UE-2. The sequence of messages is: 1. INVITE from UE-2 to I/S-CSCF; 2. INVITE from I/S-CSCF to SCC AS; 3. INVITE / Transfer Info (ATU-STI, UE PUI, CS identity) from SCC AS to ATCF; 4. INVITE / Transfer Info (ATU-STI, UE PUI, CS identity) from ATCF to MSC Server; 5. IAM/INVITE from MSC Server to UE-1; 6. SETUP from UE-1 to MSC Server; 7. Completion of originating session setup. Below the sequence, a thick double-headed arrow indicates the 'Access Media Path' between UE-1 and ATGW, and another thick double-headed arrow indicates the 'Remote Media Path' between ATGW and UE-2.](3e20f0289a1945c7c3894f51383d8e37_img.jpg) + +Sequence diagram for Figure 6.5.3.8.1-1: Terminating session that uses only CS media (UE not supporting ICS). The diagram shows the interaction between UE-1, MSC Server, ATCF, ATGW, SN/HN, I/S-CSCF, SCC AS, and UE-2. The sequence of messages is: 1. INVITE from UE-2 to I/S-CSCF; 2. INVITE from I/S-CSCF to SCC AS; 3. INVITE / Transfer Info (ATU-STI, UE PUI, CS identity) from SCC AS to ATCF; 4. INVITE / Transfer Info (ATU-STI, UE PUI, CS identity) from ATCF to MSC Server; 5. IAM/INVITE from MSC Server to UE-1; 6. SETUP from UE-1 to MSC Server; 7. Completion of originating session setup. Below the sequence, a thick double-headed arrow indicates the 'Access Media Path' between UE-1 and ATGW, and another thick double-headed arrow indicates the 'Remote Media Path' between ATGW and UE-2. + +**Figure 6.5.3.8.1-1: Terminating session that uses only CS media (UE not supporting ICS)** + +- 1-2. A Terminating session is sent towards the UE-1 from UE-2. The initial SIP INVITE request is routed via the I/S-CSCF to the SCC AS. +3. The SCC AS performs necessary T-ADS procedures according to TS 23.237 [4]. If the SCC AS knows the ATCF will be in the message path and T-ADS selects CS domain, the SCC AS routes the request towards the UE-1 via PS domain, e.g. destined to the UE PUI registered by the UE-1 itself. The SCC AS sends Access Transfer Info to the ATCF with a dynamic/static ATU-STI, UE PUI, and the CS identity of UE-1. The CS identity of UE-1 includes C-MSISDN, and if the serving MSC Server is enhanced for ICS, the CS identity also may include SIP PUI registered by the MSC Server for the UE-1 and information of serving MSC Server, e.g. contact of the MSC Server. + +NOTE 1: The Access Transfer Info can be sent as part of the existing INVITE. If the T-ADS selects PS domain and UE-1 does not support ICS, the Access Transfer Info includes ATU-STI, UE PUI, and C-MSISDN. + +4. The INVITE is routed towards the ATCF (P-CSCF not shown in flow). When receiving the SIP INVITE request and CS identity, the ATCF decides to anchor based on local policy, allocates ATGW resources for voice media, anchors the voice media in the ATGW. The ATCF shall store the ATU-STI, the UE PUI, and the C-MSISDN. The ATCF removes the ATU-STI and CS identity from the INVITE. +5. The ATCF forwards the SIP INVITE request to the UE-1 via CS domain using the CS identity. The forwarded SIP INVITE request will go through a local MGCF near the ATCF if C-MSISDN in the CS identity is used. +6. The MSC Server sends a SETUP message to the UE-1. +7. Session setup is completed. + +##### 6.5.3.8.2 UE is enhanced for ICS + +Figure 6.5.3.8.2-1 shows a terminating session when the ATCF has previously been included in the signalling path (see clause 6.5.3.6) and UE is enhanced for ICS. If the ATCF was not included in the signalling path then existing Mobile Termination procedures described in TS 23.228 [11] are used. + +![Sequence diagram for a terminating session using only CS media (UE supporting ICS). The diagram shows the interaction between UE-1, MSC Server, ATCF, ATGW, SN | HN, I/S-CSCF, SCC AS, and UE-2. The sequence of messages is: 1. INVITE from UE-2 to I/S-CSCF; 2. INVITE from I/S-CSCF to SCC AS; 3. INVITE (STN_ATCF) from SCC AS to I/S-CSCF; 4. INVITE (STN_ATCF) from I/S-CSCF to ATCF; 5. INVITE (STN_ATCF) from ATCF to UE-1; 6. SETUP (STN_ATCF) from UE-1 to MSC Server. A horizontal bar labeled '7. Completion of the CS originating session setup and PS terminating session setup' spans across the bottom. Below this, a thick double-headed arrow indicates the 'Access Media Path' between UE-1 and ATGW, and another thick double-headed arrow indicates the 'Remote Media Path' between ATGW and UE-2.](6031b46d356ee24f96bfe37ee2cb7616_img.jpg) + +Sequence diagram for a terminating session using only CS media (UE supporting ICS). The diagram shows the interaction between UE-1, MSC Server, ATCF, ATGW, SN | HN, I/S-CSCF, SCC AS, and UE-2. The sequence of messages is: 1. INVITE from UE-2 to I/S-CSCF; 2. INVITE from I/S-CSCF to SCC AS; 3. INVITE (STN\_ATCF) from SCC AS to I/S-CSCF; 4. INVITE (STN\_ATCF) from I/S-CSCF to ATCF; 5. INVITE (STN\_ATCF) from ATCF to UE-1; 6. SETUP (STN\_ATCF) from UE-1 to MSC Server. A horizontal bar labeled '7. Completion of the CS originating session setup and PS terminating session setup' spans across the bottom. Below this, a thick double-headed arrow indicates the 'Access Media Path' between UE-1 and ATGW, and another thick double-headed arrow indicates the 'Remote Media Path' between ATGW and UE-2. + +**Figure 6.5.3.8.2-1: Terminating session that uses only CS media (UE supporting ICS)** + +1~2. A Terminating session is sent towards the UE-1 from UE-2. The initial SIP INVITE request is routed via the I/S-CSCF to the SCC AS. + +3~4. The SCC AS determines the ATCF that UE-1 used for IMS registration based on the STN-rSR and roaming agreement. SCC AS derives a dynamic STN pointing to the ATCF and forwards the SIP INVITE request with the dynamic STN to UE-1 as described in TS 23.237 [4]. + +NOTE 1: The Access Transfer Info can be sent as part of the existing INVITE. + +5. The ATCF forwards the SIP INVITE request to the UE-1 without the Access Transfer Info. + +6. UE-1 sends a SETUP message in CS domain destined to the dynamic STN. + +7. Completion of the CS originating session setup that is same as described in setup 8~15 of clause 6.5.3.9.4, and completion of the PS terminating session setup as described in TS 23.237 [4]. + +#### 6.5.3.9 CS - PS Access Transfer + +##### 6.5.3.9.0 Introduction + +This clause describes the main steps of the rSRVCC procedure of the alternative. There are two parallel procedures in the flow: GERAN/UTRAN to E-UTRAN handover procedure and, IMS Service Continuity procedure initiated by MSC + +Server. The IMS Service Continuity procedure initiated by MSC Server is triggered by HO message of the GERAN/UTRAN to E-UTRAN handover procedure. + +##### 6.5.3.9.1 IMS Session Continuity procedure + +This clause describes the detail flow of IMS Session Continuity procedure for the CS-PS access transfer. + +![Sequence diagram of IMS Session Continuity procedure of rSRVCC. The diagram shows the interaction between UE, Source GERAN/UTRAN, Source MSC, MSC Server enhanced for rSRVCC, ATCF, ATGW, IMS (SCC AS), and Remote end. It details the flow of messages for handover and session transfer, including media path anchoring options.](4260aa4a7ece77c411597094c9d197bd_img.jpg) + +The diagram illustrates the IMS Session Continuity procedure for rSRVCC. It features two media path options at the top: 'Media path anchored in ATGW' and 'Media path not anchored in ATGW'. The sequence of events is as follows: + +- UE is IMS registered**: Initial state. +- 1. GERAN/UTRAN handover CS to target**: Triggered by Source GERAN/UTRAN. +- 1a. HO Required**: Message from Source GERAN/UTRAN to Source MSC. +- 1b. Prep\_HO Request**: Message from Source MSC to MSC Server enhanced for rSRVCC. +- 2. Access Transfer Notification(C-MSISDN)**: Message from MSC Server enhanced for rSRVCC to ATCF. +- 3. Configure ATGW**: Message from ATCF to ATGW. +- 4. Response**: Message from ATGW to ATCF. +- 5. Progressing**: Message from ATCF to MSC Server enhanced for rSRVCC. +- 6. Access Transfer Update (ATU-STI, C-MSISDN, SDPATGW-remote)**: Message from ATCF to IMS (SCC AS). +- Session transfer and remote update**: Internal process in IMS (SCC AS). +- 7. Response**: Message from IMS (SCC AS) to ATCF. +- 8. Session Transfer (UE PUI, STI-rSR, SDPUE)**: Message from ATCF to Source MSC. +- 9. Configure ATGW**: Message from ATCF to ATGW. +- 10. Response**: Message from ATGW to ATCF. +- Release of source access leg**: Internal process in IMS (SCC AS). +- 11. 200 OK (SDPATGW)**: Message from ATCF to UE. +- 12. Success**: Message from ATCF to MSC Server enhanced for rSRVCC. +- 13. Transfer of additional held/active session**: Final step involving PS-Media of access leg (via E-UTRAN) and PS-Media of remote leg. +- UE is available in target access**: Final state. + +Sequence diagram of IMS Session Continuity procedure of rSRVCC. The diagram shows the interaction between UE, Source GERAN/UTRAN, Source MSC, MSC Server enhanced for rSRVCC, ATCF, ATGW, IMS (SCC AS), and Remote end. It details the flow of messages for handover and session transfer, including media path anchoring options. + +**Figure 6.5.3.9.1-1: IMS Session Continuity procedure of rSRVCC** + +- Source GERAN/UTRAN determines to perform handover to VoIP-capable cell based on the measurement report and acts as described in clause 6.5.3.3, which will result in the MSC Server enhanced for rSRVCC receiving a handover request from CS domain. If the MSC Server enhanced for rSRVCC is not the Source MSC Server, then the Source MSC Server will send a Prep\_HO\_Request message to the MSC Server enhanced for rSRVCC. + +If the C-MSISDN is not received or does not contain a STN-rSR, the MSC Server enhanced for rSRVCC shall reject the CS handover. + +- The MSC Server initiates Access Transfer Notification message with C-MSISDN to the ATCF that determined by the STPN-rSR in the C-MSISDN, e.g. by sending a SIP INVITE (C-MSISDN) request to the ATCF. + +- If the voice media of the transferred session has not been anchored in ATGW, the ATCF sends Configure ATGW message to ATGW and gets response from the ATGW to reserve the resource for voice media. + +- The ATCF correlates the Access Transfer Notification message with the transferred session using the C-MSISDN, and informs the MSC Server enhanced for rSRVCC that the access transfer is in progressing, e.g. by sending a SIP "183 Session Progress" response. + +The ATCF sends the IP address/port of UE for receiving voice media, the IP address/port of ATGW for receiving voice media, and the codec used to the MSC Server enhanced for rSRVCC in this step. + +- The ATCF sends Access Transfer Update message with C-MSISDN to the SCC AS using the static ATU-STI. The SCC AS correlates the incoming Access Transfer Update message with the transferred session using the C-MSISDN, and if the Session Description (SDPATGW-remote) has changed, a remote end update is initiated according to existing procedures. + +- The SCC AS response to the Access Transfer Update message and releases the source access leg after a while. + +8. When UE-1 handover to the target access, the RRC connection has been ready for data transfer, it sends Session Transfer message to IMS using pre-configured STI-rSR, e.g. by sending a SIP INVITE (UE PUI, STI-rSR) to the IMS. + +9~10. The Session Transfer message arrives at the ATCF, the ATCF knows that the Session Transfer message is for rSRVCC according to the STI-rSR and correlates the Session Transfer message with the transferred session using the UE PUI. The ATCF sends Configure ATGW message to ATGW and gets response from the ATGW to reserve the resource for voice media and correlates it with the resource reserved in step 3 and 4. + +11. The ATCF response to the UE. + +NOTE 1: This may cause bearer modification procedure due to the change of QoS and/or TFT for the voice bearer. + +12. The ATCF informs the MSC Server enhanced for rSRVCC that the access transfer is successful, e.g. by sending a SIP "200 OK" response. + +NOTE 2: After the CS-PS access transfer, the MSC Server enhanced for rSRVCC may release the CS resources immediately instead of waiting for the terminating of access leg. + +13. The UE may initiate transfer of any additional held/active session. + +##### 6.5.3.9.2 CS to PS handover procedure + +This clause describes the detail flow of CS to PS handover procedure for the CS-PS access transfer. The bearer information, Connection Info of ATGW, and Codec are included in Target to Source Transparent Container, e.g. using a NAS message format. + +![Sequence diagram of CS to PS handover procedure. Lifelines: UE, Target E-UTRAN/UTRAN (HSPA), Target MME/SGS, MSC Server enhanced for rSRVCC, Source MSC, Source SGSN, Source GERAN/UTRAN, SGW/PGW, ATCF. The diagram shows 11 steps: 1. HO/Reloc Required (Source GERAN/UTRAN to Source SGSN); 2. Forward Reloc Req (Source SGSN to MSC Server); 3. HO/Reloc Required (Source GERAN/UTRAN to Source MSC); 4. Prep HO Req (Source MSC to MSC Server); 5. CS to PS HO Req (MSC Server to Target MME/SGS); 6. Retrieve PDP Context if needed (Target MME/SGS to Source SGSN); 7. Bearer Resource Command (Target MME/SGS to SGW/PGW); 7a. Bearer Setup (SGW/PGW to Target MME/SGS); 8. Allocate Resources (Target MME/SGS to Target E-UTRAN/UTRAN); 9. CS to PS HO Resp (Target E-UTRAN/UTRAN to MSC Server); 10. Handover Required Acknowledgement (MSC Server to Source MSC); 11. CS to PS HO Command (MSC Server to UE).](256e8716b024671206b023fab056678e_img.jpg) + +Sequence diagram of CS to PS handover procedure. Lifelines: UE, Target E-UTRAN/UTRAN (HSPA), Target MME/SGS, MSC Server enhanced for rSRVCC, Source MSC, Source SGSN, Source GERAN/UTRAN, SGW/PGW, ATCF. The diagram shows 11 steps: 1. HO/Reloc Required (Source GERAN/UTRAN to Source SGSN); 2. Forward Reloc Req (Source SGSN to MSC Server); 3. HO/Reloc Required (Source GERAN/UTRAN to Source MSC); 4. Prep HO Req (Source MSC to MSC Server); 5. CS to PS HO Req (MSC Server to Target MME/SGS); 6. Retrieve PDP Context if needed (Target MME/SGS to Source SGSN); 7. Bearer Resource Command (Target MME/SGS to SGW/PGW); 7a. Bearer Setup (SGW/PGW to Target MME/SGS); 8. Allocate Resources (Target MME/SGS to Target E-UTRAN/UTRAN); 9. CS to PS HO Resp (Target E-UTRAN/UTRAN to MSC Server); 10. Handover Required Acknowledgement (MSC Server to Source MSC); 11. CS to PS HO Command (MSC Server to UE). + +**Figure 6.5.3.9.2.1-1: Target MME/SGSN initiate resources reservation** + +1-2. If the UE is active in PS domain, source GERAN/UTRAN acts as described in clause 6.5.3.3 and sends a Handover/Relocation Required (target ID, rSRVCC indication, Source to Target transparent container) message to source SGSN, and source SGSN sends Forward Relocation Request (target ID, rSRVCC indication, Source to Target transparent container) message to MSC Server enhanced for rSRVCC according to the target ID. + +3-4. Source GERAN/UTRAN acts as described in clause 6.5.3.3 and sends a Handover/Relocation Required (target ID, rSRVCC indication, index of source SGSN, Emergency Indication, Source to Target transparent container) message to source MSC, and if the source MSC is not the target MSC, source MSC performs inter-MSC handover procedure e.g. sends Prepare HO Request (target ID, rSRVCC indication, index of source SGSN, + +Emergency Indication, C-MSISDN, Source to Target transparent container) message to MSC Server enhanced for rSRVCC according to the target ID. + +The index of source SGSN IE shall be included when PS HO is not performed. Otherwise, it shall not be included. + +5. MSC Server enhanced for rSRVCC synchronizes the PS and CS handover procedure, i.e. if Forward Relocation Request arrives first, then MSC Server enhanced for rSRVCC waits for the message for CS handover, if the message for CS handover arrives first, then MSC Server enhanced for rSRVCC waits for the Forward Relocation Request message if index of source SGSN IE is not included. MSC Server enhanced for rSRVCC sends CS to PS HO Request (IMSI, source SGSN Info, Connection Info of UE, Connection Info of remote, Codec, Non-voice Bearers Context, target ID, Source to Target transparent container, Emergency Indication) message to target MME/SGSN. + +The Non-voice Bearers Context IE is included only when PS-PS HO is performed. The Source SGSN Info IE shall be included when PS-PS HO is not performed. The target ID is understandable by target access network. The Codec can be used by the target MME/SGSN to determine the QoS of the voice bearer. + +6. If PS-PS HO is not performed, the target MME/SGSN retrieves PDP context from Source SGSN as described in TS 23.401 [5]. +7. Target MME/SGSN sends Bearer Resource Command to initiate the bearer setup procedure. +8. Target MME/SGSN allocates resources in UTRAN/E-UTRAN. +9. Target MME/SGSN sends CS to PS HO Response message to the MSC Server enhanced for rSRVCC. +10. The MSC Server enhanced for rSRVCC complete the handover preparation procedures. + +NOTE 2: The ATGW can for a certain period of time send media both on the source access leg and the new target access leg to minimize the interruption delay further. + +11. Source GERAN/UTRAN sends Handover Command message to UE, indicating CS to PS handover. This may include additional information such as the IP address/port the UE shall send the media to, and codec used. + +NOTE 3: After completion of CS to PS handover, the UE can start sending and receiving voice using the PS voice bearer. + +#### 6.5.3.9 Failure to complete CS-PS Access Transfer + +In case of failure before MSC Server initiates IMS Service Continuity procedure, there is no difference to TS 23.060 [6]. + +In case of failure after UE receives HO command or in case of handover cancellation, the MSC Server enhanced for rSRVCC will receive information from source access, the MSC Server enhanced for rSRVCC shall send an Access Transfer Cancel message to the ATCF, e.g. by sending a SIP CANCEL request. If the ATCF has sent an Access Transfer Update, the ATCF shall re-establish the source media path, e.g. using 3PCC procedure, and send an Access Transfer Failure message to the SCC AS, e.g. by sending a SIP BYE request with indication that the access transfer is fail. After receiving the Access Transfer Failure message, the SCC AS shall not release the source access leg. + +# --- 7 Assessment of the solutions + +## 7.1 Assessment Criteria + +The criteria include: + +- Voice interruption not exceeding 300ms, in roaming and non-roaming scenarios; +- Minimal impacts on the networks; +- Additional network resource consumption in UE/IMS; +- Call set up delay due to rSRVCC. + +## 7.2 Assessment of the solution 3+5 access transfer preparation alternatives + +The following table summarizes the impacts on the different nodes of the existing alternatives for the access transfer preparation in solution 3+5 ("Media anchoring in serving network with Access Transfer Control Functionality"). + +Error! No + +73 + +Error! No text of specified style in + +| | Node impacts of the voice bearer establishment procedure | UE | MSC | SGSN / MME | ATCF / P-CSCF | SGW / PGW | PCRF | +|---------------|----------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Alternative 1 | |
  • 1- Indicate the preallocated ports and codecs in the Registration procedure.
  • 2- Receive the voice bearer info and the codec info in the Handover command from the MSC, and set up the PS bearer as a result of that message.
  • 3- Start using the voice bearer right after the rSRVCC handover.
  • 4- Trigger service continuity procedure once on E-UTRAN.
|
  • 1- Receive rSRVCC HO request.
  • 2- Send rSRVCC HO request to source SGSN/MME.
  • 3- Send voice bearer setup request to ATCF.
  • 4- Receive HO response from source SGSN/MME.
  • 5- Send HO Command including the voice bearer/selected codec to UE.
  • 6- Send switch media indication to ATCF.
|
  • 1- Receive rSRVCC HO request from MSC (and possibly from RAN).
  • 2- Wait for Create Bearer Request or Downlink Data Notification with rSRVCC indication from SGW.
  • 3- Trigger relocation.
  • 4- Send rSRVCC HO response to MSC, including voice bearer information.
| ATCF:
  • 1- Store UE ports & codec info.
  • 2- Receive message from MSC and relay it to P-CSCF indicating that this is for rSRVCC.
If P-CSCF not collocated with ATCF:
  • 1- Receive message from ATCF and trigger voice bearer setup towards PCRF indicating that this is for rSRVCC.
|
  • 1- SGW / PGW: pass the rSRVCC indication through.
  • 2- SGW impact for ISR: if no S1-U exists when the SGW receives the Create Bearer Request for rSRVCC, send a Downlink Data Notification indicating this is for rSRVCC.
|
  • 1- Trigger voice bearer establishment, including indication that this is for rSRVCC.
  • 2- Correlate the service continuity request from the UE with the voice bearer already established.
| +| Alternative 2 | |
  • 1- Indicate the preallocated ports and codecs in the Registration procedure.
  • 2- Receive the voice bearer info and the codec info in the Handover command from the MSC, and set up the PS bearer as a result of that message.
  • 3- Start using the voice bearer right after the rSRVCC handover.
  • 4- Trigger service continuity procedure once on E-UTRAN.
|
  • 1- Store UE ports and codec info.
  • 2- Receive rSRVCC HO request.
  • 3- Send rSRVCC HO request to SGSN/MME including info regarding the local & remote ports/codec to be used.
  • 4- Receive HO response from SGSN/MME.
  • 5- Send HO Command including the voice bearer/selected codec to the UE.
  • 6- Send switch media indication to ATCF.
|
  • 1- Receive rSRVCC HO request from MSC (and possibly from RAN).
  • 2- Trigger Voice bearer setup towards SGW based on the local & remote ports/codec received from MSC.
  • 3- Trigger relocation.
  • 4- Send rSRVCC HO response to MSC, including voice bearer information
| - | - |
  • 1- Correlate the service continuity request from the UE with the voice bearer already established.
| + +Error! No + +74 + +Error! No text of specified style in + +Based on that summary, the following benefits/drawbacks of the different solutions can be listed: + +| | Alternative #1 | Alternative #2 | Alternative #3 | Alternative #4 | +|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Benefits |
  • - Does not require resource allocation prior to an rSRVCC handover.
  • - Only the SGSNs (and MMEs in case of GERAN with no DTM support) in areas where rSRVCC can take place need to be enhanced.
  • - Avoids the need for transcoding after rSRVCC.
|
  • - Does not require resource allocation prior to an rSRVCC handover.
  • - Only the SGSNs (and MMEs in case of GERAN with no DTM support) in areas where rSRVCC can take place need to be enhanced.
  • - Avoids the need for transcoding after rSRVCC.
|
  • - Does not prolong the handover procedure.
|
  • - Only MME in areas where rSRVCC can take place need to be enhanced.
  • - Does not prolong the handover procedure.
| +| Drawbacks |
  • - Prolongs the handover procedure.
  • - Has ATCF/P-CSCF impacts.
  • - Has SGW impact.
|
  • - Prolongs the handover procedure.
  • - SGSN impact: the SGSN needs to decide how to map the codec/port information received from the MSC to TAD and requested QoS.
|
  • - Requires resource allocation for each rSRVCC capable UE even in the case when no rSRVCC will ever take place.
  • - Requires that all MME/SGSN be enhanced to support the pre-establishment of the voice bearer without allocating radio resources for it.
  • - Has ATCF/P-CSCF impacts.
  • - PGW/SGW impact: requires from the PGW/SGW that they are able to deal with one suspended bearer while other non-suspended bearers exist.
  • - Has an impact on the existing mobility procedures (including SRVCC): requires from the MME/SGSN that they are able to deal with the suspended bearer in the mobility procedures.
  • - As the codec is selected long before the rSRVCC handover, the likelihood that transcoding is required (at least temporarily) after rSRVCC handover is high.
|
  • - Requires resource allocation for each rSRVCC capable UE even in the case when no rSRVCC will ever take place.
  • - As the codec is selected long before the rSRVCC handover, the likelihood that transcoding is required (at least temporarily) after rSRVCC handover is high.
  • - Unclear how much improvement the use of a non GBR bearer for transporting voice together with transcoding (in most cases) will bring compared to a voice break.
  • - MME impact: requires that the MME coordinates the PS handover request from source SGSN or with CS to PS handover request from MSC
| + +# --- 8 Conclusion + +## 8.1 General + +As an intermediate conclusion, it was agreed at SA WG2#81, to pursue a combination of the current solutions 3 and 5 as a way forward (see clause 6.3). + +All MSC Servers where rSRVCC is supported need to be enhanced for rSRVCC. + +## 8.2 Access Transfer preparation / How to reserve bearer for VoIP + +As an intermediate conclusion, it was agreed at SA WG2#84, to pursue alternatives 1 and 2 (clauses 6.3.3.7.1 and 6.3.3.7.2), that minimize resource consumption in the network compared to solutions 3 and 4 (clauses 6.3.3.7.3 and 6.3.3.7.4) which minimize handover preparation time. + +As a final conclusion, it was agreed at SA WG2#86, to select Alternative 5 ( clause 6.3.3.7.5) as the recommended solution for Access Transfer preparation. + +## 8.3 Source SGSN selection by MSC Server + +The Alternative 1 "CN nodes based" documented in clause 6.3.3.9.1 is not further considered. + +The Alternative 2 "UE and/or RAN provided information" documented in clause 6.3.3.9.2 is selected. + +## 8.4 Maintaining IMS registration over PS access during the CS session + +Solution 1 ("ATCF controlled registration") and solution 2 ("SCC AS controlled registration") permit to always allow for rSRVCC to take place while the UE is under GERAN without DTM support but have quite large impacts on the network/the UE. + +Due to the fact that the situation in which the IMS registration would expire during the CS session is expected to occur pretty rarely, it was decided at SA2 #84 to rather pursue a solution that does not maintain IMS registration but allows to handle gracefully the situations in which the IMS registration has expired. + +## 8.5 Summary + +The combination of clause 5 and of the following sub-clauses represents a full solution for Single Radio Voice Call Continuity (SRVCC) from UTRAN/GERAN to E-UTRAN/HSPA, which is recommended for standardization: + +- Architecture Reference Model: clause 6.3.1; +- Functional Entities: clause 6.3.2; +- Message flows: + - clauses 6.3.3.1 to 6.3.3.6, + - clause 6.3.3.7.5, +- clause 6.3.3.8, +- clause 6.3.3.9.2; +- IMS registration Considerations: clauses 6.3.4.1 and 6.3.4.4. + +# --- Annex A: Mechanisms to re-enable E-UTRAN capability + +## A.1 Functional description + +In Rel-8 and Rel-9 the UE disables its E-UTRAN capability as a result of voice domain selection when the UE selects 2G/3G as defined in TS 23.221 [9] and TS 24.301 [10], for example when it passes between TAs that do not support the appropriate voice mechanism i.e. when the UE is IMS VoIP capable and some TAs in E-UTRAN do not support IMS VoIP. + +If the UE has disabled its E-UTRAN capability and the SGSN has not informed the UE to re-enable its E-UTRAN capability, then the UTRAN/GERAN does not provide E-UTRAN neighbour cell list to the UE, hence it is impossible for this UE to perform reverse SRVCC handover if it is needed. + +Therefore a mechanism is required by the SGSN to signal to the UE to re-enable its E-UTRAN capability when there are adjacent TAs that may provide the appropriate voice mechanism for the UE (in this case IMS VoIP) for the reverse SRVCC mechanism to function. + +Three possible mechanisms are envisaged as part of this study: + +- Alt. A) broadcast bit in the UTRAN/GERAN network to indicate that there are adjacent E-UTRAN cells that would drive the UE to re-enable its E-UTRAN capability and signal this to the network with a RAU +- Alt. B) indicator in the RAU-Accept message to indicate to the UE to re-enable its E-UTRAN capability if there are adjacent E-UTRAN TAs that support IMS VoIP. +- Alt. C) the UE that supports rSRVCC does not need to disable its E-UTRAN capability even when it passes from TAs that do not support IMS VoIP. The SGSN is statically configured to manipulate the RFSP or the UEs Radio Access Capability (RAC) of the UE based on statically configured information regarding the support of IMS VoIP of the adjacent MME TAs. + +## A.2 Information flows + +### A.2.1 Proposed signalling flow for Alternative A to re-enable E-UTRAN capabilities using broadcast indicator + +![Diagram illustrating the proposed signalling flow for Alternative A to re-enable E-UTRAN capabilities using a broadcast indicator. The diagram shows a User Equipment (UE) moving between two Tracking Areas (TA1 and TA2) and two Radio Access Networks (RAN1 and RAN2). The UE performs a TAU in TA1, receives an indicator that voice is not supported, and disables its E-UTRAN capability. It then reselects to GERAN/UTRAN. While in GERAN/UTRAN, it reads system information and identifies adjacent E-UTRAN cells. When the UE moves to a cell in RAN1 that indicates adjacent E-UTRAN cells support IMS VoIP, it re-enables its E-UTRAN capability. Finally, the UE camps on an E-UTRAN cell in TA2 and performs a TAU to MME2, which supports IMS VoIP.](b63f41ca262d8ce9ef8affb62607f32b_img.jpg) + +The diagram illustrates the following steps: + +- The UE performs a TAU in TA1 (MME1). The network responds with an indicator that voice is not supported. The UE disables its E-UTRAN capability. +- The UE reselects to GERAN/UTRAN (RAN1) and disables its E-UTRAN capability. +- The UE continues to be attached to GERAN/UTRAN, reading system information while performing mobility in GPRS. +- The UE reads system information in GERAN/UTRAN and identifies from the indicator that there are adjacent E-UTRAN cells. +- When the UE moves to a cell in RAN1 that indicates adjacent E-UTRAN cells support IMS VoIP, it re-enables its E-UTRAN capability. +- The UE has enabled its E-UTRAN capability and can camp on E-UTRAN cells, hence can see TA2. +- The UE performs a TAU in TA2 (MME2). The network responds with an indicator that voice is supported. The UE enables its E-UTRAN capability. + +Diagram illustrating the proposed signalling flow for Alternative A to re-enable E-UTRAN capabilities using a broadcast indicator. The diagram shows a User Equipment (UE) moving between two Tracking Areas (TA1 and TA2) and two Radio Access Networks (RAN1 and RAN2). The UE performs a TAU in TA1, receives an indicator that voice is not supported, and disables its E-UTRAN capability. It then reselects to GERAN/UTRAN. While in GERAN/UTRAN, it reads system information and identifies adjacent E-UTRAN cells. When the UE moves to a cell in RAN1 that indicates adjacent E-UTRAN cells support IMS VoIP, it re-enables its E-UTRAN capability. Finally, the UE camps on an E-UTRAN cell in TA2 and performs a TAU to MME2, which supports IMS VoIP. + +**Figure A-1: Alternative A to re-enable E-UTRAN capabilities using Broadcast indicator in GERAN/UTRAN** + +- The UE while performing TAU receives "IMS Voice over PS supported Indicator" indicating that voice is not supported in the TA, the UE following procedures described in TS 23.221 [9] and TS 24.301 [10] disables its E-UTRAN capability, +- The UE reselects to GERAN/UTRAN and disables its E-UTRAN capability. +- The UE continues to be attached to GERAN/UTRAN reading system information as per the normal procedures while performing mobility in GPRS. +- 4-5. When the UE moves to cell that indicates that there are adjacent E-UTRAN cells that support IMS VoIP triggers the UE to re-enable its E-UTRAN capability. At this stage even if the UE goes to active mode and initiate a CS voice call in GERAN/UTRAN given that the UE has signalled its E-UTRAN capability and is able to see adjacent E-UTRAN, the RNC/BSC is able to handover the UE to E-UTRAN using reverse SRVCC procedures. +- Given that the UE is able to see E-UTRAN cells, following the normal procedures the UE is able to camp to E-UTRAN cell and performs TAU to the MME that supports IMS VoIP, hence initiate IMS VoIP calls. + +### A.2.2 Proposed signalling flow for Alternative B to re-enable E-UTRAN capabilities using NAS indicator + +![Diagram illustrating the proposed signalling flow for Alternative B to re-enable E-UTRAN capabilities using NAS indicator. The diagram shows a User Equipment (UE) moving between two Tracking Areas (TA1 and TA2) and two Radio Areas (RA1 and RA2). The UE initially performs a TAU in TA1, receiving an indicator that voice is not supported. It then reselects to GERAN/UTRAN and disables its E-UTRAN capability. When the UE moves to TA2, it performs another TAU. The SGSN1, which knows the capabilities of adjacent MMEs and the UE's capability, signals the UE to re-enable its E-UTRAN capability. The UE then enables its E-UTRAN capability and can camp on E-UTRAN cells, hence can see TA2. The diagram also shows MME1 and MME2, and indicates that TA1 does not support IMS VoIP while TA2 does.](04f7b8f64493f6d83188232f10f86fe2_img.jpg) + +The diagram illustrates the following components and flow: + +- UE:** User Equipment, shown as a car icon. +- MME1:** Mobility Management Entity 1, located in TA1 (TA without IMS VoIP support). +- MME2:** Mobility Management Entity 2, located in TA2 (TA with IMS VoIP support). +- SGSN1:** Serving GPRS Support Node, located in RA1. +- TA1:** Tracking Area 1, associated with MME1. +- TA2:** Tracking Area 2, associated with MME2. +- RA1:** Radio Area 1, associated with SGSN1. + +The flow steps are numbered as follows: + +1. TAU, no voice support (UE to MME1) +2. UE reselects to GERAN/UTRAN, disabling E-UTRAN capability (UE internal action) +3. UE moves (UE from GERAN/UTRAN to TA2) +4. SGSN knows the capabilities of the adjacent MMEs and the UE capability and Requests the UE to enable E-UTRAN (SGSN1 to UE) +5. RAU, enable E-UTRAN cap (UE to SGSN1) +6. UE has enabled its E-UTRAN capability and can camp on E-UTRAN cells, hence can see TA2 (UE internal action) +7. TAU, voice support (UE to MME2) + +Diagram illustrating the proposed signalling flow for Alternative B to re-enable E-UTRAN capabilities using NAS indicator. The diagram shows a User Equipment (UE) moving between two Tracking Areas (TA1 and TA2) and two Radio Areas (RA1 and RA2). The UE initially performs a TAU in TA1, receiving an indicator that voice is not supported. It then reselects to GERAN/UTRAN and disables its E-UTRAN capability. When the UE moves to TA2, it performs another TAU. The SGSN1, which knows the capabilities of adjacent MMEs and the UE's capability, signals the UE to re-enable its E-UTRAN capability. The UE then enables its E-UTRAN capability and can camp on E-UTRAN cells, hence can see TA2. The diagram also shows MME1 and MME2, and indicates that TA1 does not support IMS VoIP while TA2 does. + +**Figure A-2: Alternative B to re-enable E-UTRAN capabilities using NAS indicator** + +1. The UE while performing TAU receives "IMS Voice over PS supported Indicator" indicating that voice is not supported in the TA, the UE following procedures described in TS 23.221 [9] and TS 24.301 [10] disables its E-UTRAN capability, +2. The UE reselects to GERAN/UTRAN and disables its E-UTRAN capability. +3. The UE continues be attached to GERAN/UTRAN and perform mobility in GPRS. +- 4-5. When the UE moves to an SGSN that knows that the MME serving TAs adjacent to the RA where the UE is currently attached supports IMS VoIP it signals to the UE to re-enable its E-UTRAN capability. At this stage even if the UE goes to active mode and initiate a CS voice call in GERAN/UTRAN given that the UE has signalled its E-UTRAN capability and is able to see adjacent E-UTRAN, the RNC/BSC is able to handover the UE to E-UTRAN using reverse SRVCC procedures. +6. Given that the UE is able to see E-UTRAN cells, following the normal procedures the UE is able to camp to E-UTRAN cell and performs TAU to the MME that supports IMS VoIP, hence initiate IMS VoIP calls. + +### A.2.3 Proposed signalling flow for Alternative C to re-enable E-UTRAN capabilities using change in RFSP/RAC of the UE + +![Diagram illustrating the proposed signalling flow for Alternative C to re-enable E-UTRAN capabilities using change in RFSP/RAC of the UE. The diagram shows a UE moving between different network areas (TAI1, TAI2, RAI1) and interacting with MME1, MME2, and SGSN1.](f97535cdaa4fe017f4659512f4f78028_img.jpg) + +The diagram shows the following components and steps: + +- TAI1 (TA without IMS VoIP support):** Contains MME1. Step 1: "1. TAU, no voice support, change RFSP/RAC to eNB". +- Step 2:** A text box above the UE icon states: "2. UE reselects to GERAN/UTRAN, but does not disable its E-UTRAN capability". +- Step 3:** Arrow labeled "3. UE moves" showing movement from TAI1 towards RAI1. +- RAI1:** Contains SGSN1. Step 5: "5. RAU, change RFSP/RAC to NodeB". +- Step 4:** A text box connected to SGSN1 states: "4. SGSN knows the capabilities of the adjacent MMEs and the UE capability and Requests the UE to enable E-UTRAN". +- TAI2 (TA with IMS VoIP support):** Contains MME2. Step 7: "7. TAU, change RFSP/RAC". +- Step 6:** A text box connected to MME2 states: "6. The SGSN has changed the RFSP/RAC of the UE and a new idle mode mobility priority is passed to the UE, the UE is able to see E-UTRAN cells". + +Diagram illustrating the proposed signalling flow for Alternative C to re-enable E-UTRAN capabilities using change in RFSP/RAC of the UE. The diagram shows a UE moving between different network areas (TAI1, TAI2, RAI1) and interacting with MME1, MME2, and SGSN1. + +**Figure A-3: Alternative B to re-enable E-UTRAN capabilities using changes in RFSP/RAC of the UE** + +1. The UE while performing TAU receives "IMS Voice over PS supported Indicator" indicating that voice is not supported in the TA, the UE given is rSRVCC capable does not follow procedures described in TS 23.221 [9] and TS 24.301 [10] does not disable its E-UTRAN capability. Rather the MME changes the RFSP or manipulates the RAC of the UE making the eNodeB to change the idle mode priority list, prioritising GERAN/UTRAN instead of E-UTRAN. +2. The UE reselects to GERAN/UTRAN. +3. The UE continues to be attached to GERAN/UTRAN and perform mobility in GPRS. +- 4-5. When the UE moves to an SGSN that knows that the MME serving TAs adjacent to the RA where the UE is currently attached supports IMS VoIP it signals to the NodeB/BSC a new RFSP or changes the RAC of the UE in order to change the idle mode priority list of the UE. At this stage even if the UE goes to active mode and initiate a CS voice call in GERAN/UTRAN is able to see adjacent E-UTRAN, the RNC/BSC is able to handover the UE to E-UTRAN using reverse SRVCC procedures. +6. Given that the UE is able to see E-UTRAN cells, following the normal procedures the UE is able to camp to E-UTRAN cell and performs TAU to the MME that supports IMS VoIP, hence initiate IMS VoIP calls. + +# --- Annex B:Mechanisms for GERAN/UTRAN sending Handover/Relocation Required message + +When GERAN/UTRAN decides to initiate handover procedure for the rSRVCC capable UE with CS session(s) to a VoIP-capable cell, it shall use a target ID in the Handover/Relocation Required message for CS handover that the message will be forwarded to a MSC Server enhanced for rSRVCC by intermediate node of the source access network. The target ID for CS handover and PS handover shall contain, but does not need to be the same: + +- LAI or RAI. The LAI/RAI shall identify the target MME/SGSN (HSPA) and the LAI/RAI in routing table of CS core network points to a MSC Server enhanced for rSRVCC; + +NOTE 1: The LAI/RAI can be treated as the rSRVCC indication. + +- Index of eNB ID or RNC ID. The index of eNB ID or RNC ID in the target ID maybe related to the target MME/SGSN (HSPA); +- Index of selected TAI if target access is E-UTRAN. The index of selected TAI maybe related to the target eNB. + +NOTE 2: Considering only the border cell need to be configured as this way, the table of mapping the target ID to a real target ID understandable in target access network will not be a big table. + +The GERAN/UTRAN shall use a target ID in the Relocation Required message for PS handover that messages for both CS handover and PS handover will be forwarded to the same MSC Server enhanced for rSRVCC by intermediate node of the source access network. The target ID for CS handover shall also contain index of source SGSN that related to the source MSC if PS-PS HO is not performed. + +An example format of the target ID according to TS 25.413 [12] is LAI + RAC (8 bits) + Extended RNC-ID (16 bits), and the most significant 4 bits of the Extended RNC-ID is the index of source SGSN, the rest 20 bits contains index of eNB ID, and index of selected TAI. + +# --- Annex C: Change history + +| Change history | | | | | | | | | +|----------------|-------|-----------|----|-----|-------------------------------------------------------------------------------|-------|--------|--| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | | +| 2011-08 | SP-53 | SP-110477 | - | - | MCC Editorial update to version 2.0.0 for presentation to TSG SA for Approval | 1.4.0 | 2.0.0 | | +| 2011-09 | SP-53 | - | - | - | MCC update to version 11.0.0 after TSG SA#53 approval | 2.0.0 | 11.0.0 | | \ No newline at end of file diff --git a/marked/Rel-11/27_series/27001/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/marked/Rel-11/27_series/27001/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2a03125f5626ca6ee2188abf24cacc364653882 --- /dev/null +++ b/marked/Rel-11/27_series/27001/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8226685629d54ac8c28cc424bea85dfc490865197275af29146fec4abc828f8f +size 14928 diff --git a/marked/Rel-11/27_series/27001/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-11/27_series/27001/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18f5d11e8a683c4aee34abd7fdac3aa0d793400e --- /dev/null +++ b/marked/Rel-11/27_series/27001/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbd328e47a248cb730ac7de874b3b52bf8fc750f51a0d0f58d376912fec7dc67 +size 39302 diff --git a/marked/Rel-11/27_series/27001/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-11/27_series/27001/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37896f5ded6cc9f9d43ab68aa08795a0265eed67 --- /dev/null +++ b/marked/Rel-11/27_series/27001/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71091e5543b955c83ebba3e24bce91fff48e3021f8dac51a2e287e7ee5c2b125 +size 31173 diff --git a/marked/Rel-11/27_series/27001/fbfa653853daf5541118a9ddecb92284_img.jpg b/marked/Rel-11/27_series/27001/fbfa653853daf5541118a9ddecb92284_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b432086f639888568cc73e3be3b42f759c123c1c --- /dev/null +++ b/marked/Rel-11/27_series/27001/fbfa653853daf5541118a9ddecb92284_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f093f3b5bba355d63512e0d7d20af768c96098af5d60022bd14eb9f27f80e6d +size 44192 diff --git a/marked/Rel-11/27_series/27001/raw.md b/marked/Rel-11/27_series/27001/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8b3e7eab9e086feb28b5652b26276e5c63b8d6bd --- /dev/null +++ b/marked/Rel-11/27_series/27001/raw.md @@ -0,0 +1,2740 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 11 | +| 3.1 Definitions..... | 11 | +| 3.2 Abbreviations ..... | 11 | +| 4 Access reference configuration..... | 12 | +| 5 Functions to support data services ..... | 13 | +| 6 Support of non transparent Bearer Services..... | 13 | +| 6.1 Functions of the Layer 2 Relay ..... | 13 | +| 6.1.1 Layer 2 Relay in Frame Tunneling Mode ..... | 14 | +| 6.2 Radio Link Services Used..... | 15 | +| 6.3 Flow Control - General Description..... | 15 | +| 6.3.1 End to End Flow Control..... | 15 | +| 6.3.2 Back Pressure ..... | 15 | +| 6.3.3 Receive not Ready..... | 15 | +| 6.4 User initiated service level up and down grading (applies to A/Gb and GERAN Iu mode only) ..... | 15 | +| 6.5 Asymmetry preference indication (applies to A/Gb and GERAN Iu mode only) ..... | 16 | +| 7 Structure of the 3GPP TS 27-series of Specifications ..... | 16 | +| 8 Functions common to all interfaces ..... | 17 | +| 8.1 Synchronization of the Traffic Channel..... | 17 | +| 8.1.1 Transparent services ..... | 17 | +| 8.1.1.1 Initial procedure for traffic channel types TCH/F4.8 and TCH/F9.6 ..... | 17 | +| 8.1.1.2 Initial procedure for traffic channel types TCH/F14.4 and TCH/F28.8 ..... | 18 | +| 8.1.1.3 Subsequent procedures for traffic channel types TCH/F4.8, TCH/F9.6, TCH/F14.4, and TCH/F28.8 ..... | 18 | +| 8.1.1.3.1 V-series interface..... | 18 | +| 8.1.1.3.2 X-series interface..... | 18 | +| 8.1.1.3.3 S interface (I.420)..... | 18 | +| 8.1.1.4 Procedures for RLC..... | 18 | +| 8.1.1.4.1 V-series interface..... | 18 | +| 8.1.2 Non-transparent services ..... | 19 | +| 8.1.2.1 V-series interface ..... | 19 | +| 8.1.2.2 X-series interface ..... | 19 | +| 8.1.2.3 S interface (I.420) (does not apply to UTRAN Iu mode) ..... | 19 | +| 8.1.3 Action on loss of synchronization ..... | 19 | +| 8.1.3.1 Loss at the TAF-radio interface ..... | 19 | +| 8.1.3.2 Loss at the TAF-terminal interface..... | 19 | +| 8.2 Filtering of Channel Control Information (A/Gb or GERAN Iu mode transparent mode only) ..... | 19 | +| 8.2.1 General ..... | 19 | +| 8.2.2 Filtering process to be applied..... | 20 | +| 8.2.2.1 V-series interface ..... | 20 | +| 8.2.2.2 X-series interface ..... | 20 | +| 8.2.2.3 Filtering mechanism ..... | 21 | +| 8.2.2.3.1 Traffic channel types TCH/F4.8 and TCH/F9.6 ..... | 21 | +| 8.2.2.3.2 Traffic channel type TCH/F14.4 ..... | 21 | +| 8.3 Terminal Compatibility Decision..... | 21 | +| 8.3.1 Compatibility Check..... | 21 | +| 8.3.2 Selection of Appropriate Terminal Function..... | 21 | +| 8.3.3 Indication of Compatibility Requirements to the PLMN ..... | 21 | +| 8.3.3.1 Indication in case of Mobile terminating calls..... | 21 | +| 8.3.3.2 Indication in case of Mobile originating calls ..... | 24 | +| 8.3.3.3 Differences in validity of BC parameter values in A/Gb mode, GERAN Iu mode and UTRAN Iu mode..... | 26 | + +| | | | +|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| 8.4 | Test Loops..... | 26 | +| 8.5 | Alternate speech/facsimile group 3 ..... | 26 | +| 8.5.1 | In case of A/Gb mode..... | 26 | +| 8.5.2 | In case of UTRAN Iu mode..... | 26 | +| 8.6 | Multislot configuration split/combine function..... | 27 | +| 8.6.1 | Non-transparent data ..... | 27 | +| 8.6.2 | Transparent data ..... | 27 | +| 8.7 | EDGE multiplexing function ..... | 27 | +| 8.8 | Seamless data rate change..... | 27 | +| Annex A (informative): | List of Bearer Capability Elements ..... | 28 | +| Annex B (normative): | Setting of Bearer Capability, Low Layer Compatibility and High Layer Compatibility Information Element for PLMN Bearer Services and PLMN TeleServices ..... | 35 | +| B.0 | Scope..... | 35 | +| B.1 | Bearer Capability Information Element..... | 35 | +| B.1.1 | Introduction ..... | 35 | +| B.1.1.1 | General Consideration ..... | 35 | +| B.1.1.2 | Interpretation of the Diagrams..... | 36 | +| B.1.2 | Bearer Service 20, Data Circuit Duplex Asynchronous..... | 48 | +| B.1.2.1 | Unrestricted / restricted digital information transfer capability ..... | 48 | +| B.1.2.2 | 3,1 kHz audio ex-PLMN information transfer capability..... | 50 | +| B.1.2.3 | Frame Tunnelling Mode ..... | 52 | +| B.1.2.4 | PIAFS ..... | 53 | +| B.1.3 | Bearer Service 30, Data Circuit Duplex Synchronous..... | 54 | +| B.1.3.1 | Unrestricted/restricted digital information transfer capability ..... | 54 | +| B.1.3.1.1 | Transparent FNUR <= 48 kbit/s (TCH/F4.8, TCH/F9.6, TCH/14.4, TCH/F28.8) ..... | 54 | +| B.1.3.1.2 | X.32 Case..... | 55 | +| B.1.3.1.3 | Transparent FNUR=56 kbit/s, including 3G-H.324/M, (TCH/F9.6, TCH/F32.0, UTRAN Iu mode) ..... | 56 | +| B.1.3.1.4 | Transparent FNUR = 56kbit/s, including 3G-H.324/M (TCH/F14.4)..... | 58 | +| B.1.3.1.5 | Transparent FNUR = 64kbit/s, including 3G-H.324/M (TCH/F9.6, TCH/F14.4, TCH/F32.0, UTRAN Iu mode))..... | 59 | +| B.1.3.1.6 | 3G-H.324/M, FNUR=32.0 kbit/s (TCH/F32.0, UTRAN Iu mode)..... | 61 | +| B.1.3.1.7 | Synchronous transparent 56 kbit/s (RDI) and 64kbit/s (UDI) (UTRAN Iu mode) ..... | 63 | +| B.1.3.2 | 3,1 kHz audio ex-PLMN information transfer capability..... | 64 | +| B.1.3.2.1 | Non-X.32 Cases ..... | 64 | +| B.1.3.2.2 | X.32 Case..... | 65 | +| B.1.3.2.3 | 3G-H.324/M Case..... | 66 | +| B.1.4 | Bearer Service 40 ... 46, PAD Access Asynchronous..... | 67 | +| B.1.5 | Bearer Service 50 ... 53 ,Data Packet Duplex Synchronous, Unrestricted digital information transfer capability ..... | 67 | +| B.1.6 | Bearer Service 61, Alternate Speech/Data ..... | 67 | +| B.1.7 | Bearer Service 81, Speech followed by Data..... | 67 | +| B.1.8 | Teleservice 11 ... 12, Speech..... | 68 | +| B.1.9 | Teleservice 21 ... 23, Short Message..... | 69 | +| B.1.10 | Teleservice 61, Alternate Speech and Facsimile group 3 ..... | 69 | +| B.1.10.1 | Teleservice 61, Speech ..... | 69 | +| B.1.10.2 | Teleservice 61, Facsimile group 3 in A/Gb mode..... | 70 | +| B.1.10.3 | Teleservice 61, Facsimile group 3 in UTRAN Iu mode..... | 71 | +| B.1.11 | Teleservice 62, Automatic Facsimile group 3..... | 72 | +| B.1.12 | Valid combinations of FNUR, WAIUR, ACC, mTCH..... | 72 | +| B.1.12.1 | Transparent Services ..... | 72 | +| B.1.12.2 | Non-transparent services ..... | 74 | +| B.1.13 | Assignment of radio access bearer parameters depending on FNUR and WAIUR..... | 75 | +| B.1.13.1 | Transparent Services ..... | 75 | +| B.1.13.2 | Non-transparent services for UTRAN Iu mode..... | 76 | +| B.1.13.3 | Non-transparent services for GERAN Iu mode..... | 76 | + +| | | | +|------------------------|-------------------------------------------------------------------------|----| +| B.2 | Low Layer/High Layer Compatibility Information Element ..... | 78 | +| B.2.1 | Introduction ..... | 78 | +| B.2.1.1 | General Consideration ..... | 78 | +| B.2.1.2 | Interpretation of the Tables..... | 79 | +| B.2.2 | LLC Bearer Service 20..... | 79 | +| B.2.2.1 | Unrestricted / restricted digital information transfer capability ..... | 79 | +| B.2.2.2 | 3,1 kHz audio ex-PLMN information transfer capability..... | 79 | +| B.2.3 | LLC Bearer Service 30..... | 80 | +| B.2.3.1 | Unrestricted / restricted digital information transfer capability ..... | 80 | +| B.2.3.2 | 3,1 kHz audio ex-PLMN information transfer capability..... | 80 | +| B.2.4 | LLC Bearer Services 41 ... 46 ..... | 81 | +| B.2.5 | LLC Bearer Services 51 ... 53 ..... | 81 | +| B.2.6 | LLC Bearer Service 61 ..... | 81 | +| B.2.7 | LLC Bearer Service 81 ..... | 81 | +| B.2.8 | HLC Teleservices 11 ... 12..... | 81 | +| B.2.9 | HLC Teleservices 21 ... 23..... | 81 | +| B.2.10 | HLC Teleservice 61 ..... | 81 | +| B.2.11 | HLC Teleservice 62 ..... | 82 | +| Annex C (informative): | Change history..... | 83 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document specifies the functions needed for terminal adaptation 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 is based on the principles of terminal adaptor functions presented in the ITU-T I-series of Recommendations (I.460 to I.463). + +The PLMN supports a wide range of voice and non-voice services in the same network. In order to enable non-voice traffic in the PLMN there is a need to connect various kinds of terminal equipment to the Mobile Termination (MT). The target of the present document is to outline the functions needed for the terminal adaptation. + +The bearer services are described in 3GPP TS 22.002 and the general network configuration is described in 3GPP TS 23.002. The PLMN access reference configuration is defined in 3GPP TS 24.002. The various connection types used in the A/Gb mode or GERAN Iu mode PLMN are presented in 3GPP TS 43.010. Terminology used in the present document is presented in 3GPP TR 21.905 and 3GPP TS 29.990. For support of data services between a PLMN and other networks see 3GPP TS 29.007. + +The present document is valid for a 2nd generation PLMN (A/Gb mode) as well as for a 3rd generation PLMN (Iu mode). If text applies only for one of these systems it is explicitly mentioned by using the terms "A/Gb mode" and "UTRAN Iu mode". If text applies to both of the systems, but a distinction between the ISDN/PSTN and the PLMN is necessary, the term "PLMN" is used. + +NOTE 1: From R99 onwards the following services are no longer required by a PLMN: + +- the dual Bearer Services "alternate speech/data" and "speech followed by data"; +- the dedicated services for PAD and Packet access; +- BS 21 ... 26 and BS 31 ... 34. + +From REL-4 onwards the following service is no longer required by a PLMN: + +- the synchronous Bearer Service non-transparent (BS 30 NT). +- Non-transparent facsimile (TS 61/62 NT) for the A/Gb mode and GERAN Iu mode. + +The support of these services is still optional. The specification of these services is not within the scope of the present document. For that, the reader is referred to former releases. + +NOTE2 : Please note that the Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used. + +# --- 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] Void. +- [2] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)". +- [3] 3GPP TS 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)". +- [4] 3GPP TS 23.002: "Network architecture". +- [5] 3GPP TS 43.010: "GSM Public Land Mobile Network (PLMN) connection types". + +- [6] 3GPP TS 24.002: "GSM - UMTS Public Land Mobile Network (PLMN) access reference configuration". +- [7] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core network protocols -Stage 3". +- [8] 3GPP TS 44.021: "Rate adaption on the Mobile Station - Base Station System (MS - BSS) interface". +- [9] 3GPP TS 24.022: "Radio Link Protocol (RLP) for circuit switched bearer and teleservices". +- [10] 3GPP TS 45.005: "Radio transmission and reception". +- [11] 3GPP TS 27.002: "Terminal Adaptation Functions (TAF) for services using Asynchronous bearer capabilities". +- [12] 3GPP TS 27.003: "Terminal Adaptation Functions (TAF) for services using Synchronous bearer capabilities". +- [13] Void. +- [14] Void. +- [15] Void. +- [16] Void. +- [17] Void. +- [18] Void. +- [19] Void. +- [20] Void. +- [21] 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)". +- [22] Void. +- [23] Void. +- [24] Void. +- [25] Void. +- [26] ITU-T V-series Recommendations: "Data communication over the telephone network". +- [27] Void. +- [28] ITU-T X-series Recommendations: "Data networks and open system communication". +- [29] Void +- [30] ITU-T Recommendation X.150 (11/88): "Data Communication Networks: Transmission, Signalling and Switching, Network Aspects, Maintenance and Administrative Arrangements". +- [31] Void. +- [32] ITU-T Recommendation V.250 (05/99): "Serial asynchronous automatic dialling and control". +- [33] ITU-T Recommendation V.54 (11/88): "Loop test devices for modems". +- [34] ITU-T Recommendation V.110 (10/96): "Support by an ISDN of data terminal equipments with V-Series type interfaces". + +- [35] ITU-T Recommendation I.460 (02/99), ITU-T Recommendation I.461 (also published as ITU-T Recommendation X.30 [70] ), ITU-T Recommendation I.462 (also published as ITU-T Recommendation X.31 (11/95)), ITU-T Recommendation I.463 (also published as ITU-T Recommendation V.110 [34]): "ISDN Overall Network Aspects and Functions, User Network Interfaces". +- [36] ITU-T Recommendation Q.931 (1998): "ISDN user network interface layer 3 specification for basic call control". +- [37] ETSI ETR 018 ed.4 (1995-11): "Integrated Services Digital Network (ISDN), Application of the Bearer Capability (BC), High Layer Compatibility (HLC) and Low Layer Compatibility (LLC) information elements by terminals supporting ISDN services". +- [38] ISO/IEC 6429: 1992: "Information technology - Control functions for coded character sets". +- [39] Void. +- [40] Void. +- [41] Void. +- [42] ITU-T Recommendation V.120 (10/96): "Support by an ISDN of data terminal equipment with V-Series type interfaces with provision for statistical multiplexing". +- [43] 3GPP TS 23.034: "High Speed Circuit Switched Data (HSCSD) - Stage 2". +- [44] ISO/IEC 13239 (1997) Information Technology: "Telecommunications and information exchange between systems - High-level data link control (HDLC) procedures" +- [45] Void. +- [46] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [47] 3GPP TR 25.990: "Vocabulary for UTRAN". +- [48] 3GPP TS 25.322: "Radio Link Control (RLC) protocol specification". +- [49] Void. +- [50] Mobile Internet Access Forum: "PIAFS Specification Ver. 1.1, 2.1". +- [51] ITU-T Recommendation V.80 (08/96): "In-band DCE control and synchronous data modes for asynchronous DTE". +- [52] 3GPP TS 43.045: "Technical realization of facsimile group 3 service - transparent". +- [53] 3GPP TS 45.001: "Physical layer on the radio path; General description". +- [54] 3GPP TS 22.034: "High Speed Circuit Switched Data (HSCSD); Stage 1". +- [55] 3GPP TS 23.107: "Quality of Service QoS concept and architecture". +- [56] 3GPP TS 48.020: "Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". +- [57] 3GPP TS 22.001: "Principles of circuit telecommunication services supported by a Public Land Mobile Network (PLMN)". +- [58] ITU-T Recommendation I.440 (also published as ITU-T Recommendation Q.920 [71]). +- [59] ITU-T Recommendation I.450 (also published as ITU-T Recommendation Q.930 [72]). +- [60] ITU-T Recommendation H.223 (07/01): "Multiplexing protocol for low bit rate multimedia communication". +- [61] ITU-T Recommendation H.245: "Control protocol for multimedia communication". + +- [62] ITU-T Recommendation V.21 (11/88): "300 bits per second duplex modem standardized for use in the general switched telephone network". +- [63] ITU-T Recommendation V.22 (11/88): "1200 bits per second duplex modem standardized for use in the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [64] ITU-T Recommendation V.22bis (11/88): "2400 bits per second duplex modem using the frequency division technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits ". +- [65] ITU-T Recommendation V.26ter (11/88): "2400 bits per second duplex modem using the echo cancellation technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [66] ITU-T Recommendation V.31 (11/88): "Electrical characteristics for single-current interchange circuits using optocouplers". +- [67] ITU-T Recommendation V.32 (03/93): "A family of 2-wire, duplex modems operating at data signalling rates of up to 9600 bit/s for use on the general switched telephone network and on leased telephone-type circuits". +- [68] ITU-T Recommendation V.34 (02/98): "A modem operating at data signalling rates of up to 33 600 bit/s for use on the general switched telephone network and on leased point-to-point 2-wire telephone-type circuits". +- [69] ITU-T Recommendation V.42 (03/02): "Error-correcting procedures for DCEs using asynchronous-to-synchronous conversion". +- [70] ITU-T Recommendation X.30 (03/93): "Support of X.21, X.21 bis and X.20 bis based Data Terminal Equipments (DTEs) by an Integrated Services Digital Network (ISDN) ". +- [71] ITU-T Recommendation Q.920 (03/93): "ISDN user-network interface data link layer - General aspects". +- [72] ITU-T Recommendation Q.930 (03/93): "ISDN user-network interface layer 3 - General aspects". +- [74] 3GPP TS 23.146: "Technical realisation of facsimile Group 3 service - non-transparent". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +The term 'Mobile Station' ( MS ) in the present document is synonymous with the term 'User Equipment' ( UE ) as defined in 3GPP TR 21.905. + +The term 'TE2' in the present document is synonymous with the term 'TE' as defined in 3GPP TR 21.905. + +The term 'MT2' in the present document is synonymous with the term 'MT' as defined in 3GPP TR 21.905. + +For the purposes of the present document the following terms and definitions given in 3GPP TS 21.905 and the following apply: + +**A/Gb mode:** indicates that the text applies only to a system or sub-system which operate in A/Gb mode of operation, i.e. with a functional division that is in accordance with the use of an A or a Gb interface between the radio access network and the core network + +**Iu mode:** indicates that the text applies only to a system or a sub-system which operates in Iu mode of operation, i.e. with a functional division that is in accordance with the use of an Iu-CS or Iu-PS interface between the radio access network and the core network + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 and 3GPP TR 25.990 and the following apply: + +| | | +|--------------|----------------------------------------------------------------------------------------------------------| +| CALL PROC | CALL PROCEEDING | +| CALL CONF | CALL CONFIRMED | +| CONNACK | CONNECT ACKNOWLEDGEMENT | +| EDGE channel | A general term referring to channels based on 8PSK modulation; i.e. TCH/F28.8, TCH/F32.0, and TCH/F43.2. | +| FTM | Frame Tunnelling Mode | +| PIAFS | PHS Internet Access Forum Standard | +| PHS | Personal Handyphone System | + +# 4 Access reference configuration + +Figure 1 presents the reference configuration for access to an A/Gb mode PLMN and GERAN Iu mode (see 3GPP TS 24.002). + +![Figure 1: PLMN Access Reference Configuration (in A/Gb mode and GERAN Iu mode). The diagram shows a Mobile Station (MS) containing MT0 and MT2. MT0 is connected to a BSS/MSC. MT2 contains a TA and is connected to a TE2 via the R reference point and to a BSS/MSC via the Um reference point. A legend defines the symbols: reference point (cross), TE2 (V-type terminal), TA (Terminal Adaptor), GERAN (GSM/EDGE Radio Access Network), and CN (Core Network).](7f17c430b9598e4d748a8041457810b3_img.jpg) + +Figure 1: PLMN Access Reference Configuration (in A/Gb mode and GERAN Iu mode). The diagram shows a Mobile Station (MS) containing MT0 and MT2. MT0 is connected to a BSS/MSC. MT2 contains a TA and is connected to a TE2 via the R reference point and to a BSS/MSC via the Um reference point. A legend defines the symbols: reference point (cross), TE2 (V-type terminal), TA (Terminal Adaptor), GERAN (GSM/EDGE Radio Access Network), and CN (Core Network). + +**Figure 1: PLMN Access Reference Configuration (in A/Gb mode and GERAN Iu mode)** + +Within the scope of the present document the Mobile Termination MT0 means a fully integrated MS including data terminal and its adaptation functions. MT2 includes ITU-T V-series terminal adaptation functions among other MT functions. + +Figure 2 presents the access reference configuration for UTRAN Iu mode. There is no reference point identified for the TAF. The TAF is considered as a part of the Mobile Termination. + +![Figure 2: UTRAN Iu mode PLMN Access Reference Configuration. The diagram shows a User Equipment (UE) containing a Mobile Equipment (ME) and a USIM. The ME contains a Terminal Equipment (TE) connected to a Mobile Termination (MT) via the R reference point. The MT contains a Terminal Adaptor Function (TAF). The ME is connected to the USIM via the Cu reference point. The MT is connected to an Access Network via the Uu reference point.](fbfa653853daf5541118a9ddecb92284_img.jpg) + +Figure 2: UTRAN Iu mode PLMN Access Reference Configuration. The diagram shows a User Equipment (UE) containing a Mobile Equipment (ME) and a USIM. The ME contains a Terminal Equipment (TE) connected to a Mobile Termination (MT) via the R reference point. The MT contains a Terminal Adaptor Function (TAF). The ME is connected to the USIM via the Cu reference point. The MT is connected to an Access Network via the Uu reference point. + +**Figure 2: UTRAN Iu mode PLMN Access Reference Configuration** + +# --- 5 Functions to support data services + +The main functions of the MT to support data services are: + +- functions to ensure conformity of terminal service requests to network capability; +- physical connection of the R reference point; +- flow control of signalling and mapping of user signalling to/from the PLMN access signalling; +- rate adaptation of user data (see 3GPP TS 44.021) and data formatting for the transmission SAP (3GPP TS 25.322); +- flow control of non-transparent user data and mapping of flow control for asynchronous data services; +- support of data integrity between the MS and the interworking function in the PLMN; +- end-to-end synchronization between terminals; +- filtering of status information; +- functions to support non-transparent bearer services e.g. termination of the Radio Link Protocol (RLP) and the Layer 2 Relay function (L2R) including optional data compression function (where applicable); +- terminal compatibility checking; +- optional support of local test loops. + +In addition, functions to support autocalling and autoanswering are optionally specified in accordance with ITU-T Recommendation V.250 (although the use of other autocalling/auto-answering procedures are not prohibited provided that mapping in a functionally equivalent way to 3GPP TS 24.008 call control is also provided). + +Other functional entities may be envisaged apart from the TAF. One of the physical interface to all these functions is the DTE/DCE interface to the MT. Normally, this DTE/DCE interface is associated with the TAF, if available. Therefore the access to any of these other functional entities, if implemented, via the DCE/DTE interface, are triggered by appropriate command sequences which are described in the applicable specifications (although the use of other procedures is not prohibited provided that mapping in a functionally equivalent way is also provided). These command sequences shall be issued by the DTE only when the MT is in the appropriate command status and there is no data connection pending. They are interpreted by an MT internal control function and result in an association of the DTE/DCE interface with the addressed function, if available. + +# --- 6 Support of non transparent Bearer Services + +In order to support asynchronous non transparent bearer services a Layer 2 Relay (L2R) function is included in the mobile termination. The details of the particular L2R function for the different asynchronous non transparent bearer services are contained in the appropriate 3GPP 27-series Specification. This clause describes the general aspects of the L2R function. + +The Layer 2 Relay (L2R) function provides for the reliable transportation of known, i.e. asynchronous non transparent, user protocols across the radio interface of a PLMN. The L2R functions are located in the Mobile Termination (MT) and the Interworking Function (IWF) associated with a Mobile Switching Centre (MSC). The L2R uses the services provided by the Radio Link Protocol (RLP) to transport the asynchronous non transparent protocol information between the MS and the IWF. + +## 6.1 Functions of the Layer 2 Relay + +The complete protocol reference models for data and telematic services are described in 3GPP TS 43.010. The subset of those protocol reference models relating to the L2R function is reproduced in figure 2A. + +![Figure 2A: Protocol stack diagram showing MS and IWF entities. The MS side has NTP and IFP protocols connected to an L2R block. The IWF side has an L2R block connected to the Radio Link Protocol, which is connected to the NTP and IFP protocols. A transparent higher layer protocol is shown above the L2R blocks. A legend defines NTP as Non Transparent Protocol and IFP as Interface Protocol.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +MS IWF + +Transparent higher layer protocol + +L2R L2R Protocol Radio Link Protocol + +NTP IFP NTP IFP + +NTP Non Transparent Protocol +IFP Interface Protocol + +Figure 2A: Protocol stack diagram showing MS and IWF entities. The MS side has NTP and IFP protocols connected to an L2R block. The IWF side has an L2R block connected to the Radio Link Protocol, which is connected to the NTP and IFP protocols. A transparent higher layer protocol is shown above the L2R blocks. A legend defines NTP as Non Transparent Protocol and IFP as Interface Protocol. + +Figure 2A + +The Non Transparent Protocol (NTP) is normally a layer 2 protocol for OSI conformant protocols or an equivalent in the case of non OSI protocols. The Interface Protocol (IFP) is normally a layer 1 protocol for OSI conformant systems or equivalent for non OSI systems. + +The L2R can be considered to consist of 3 sub-functions, see figure 3. + +![Figure 3: Diagram of the L2R sub-functions. A large box labeled 'Relay Entity' contains three sub-entities: 'NTP Entity', 'L2RP Entity', and 'RLP Entity'. The NTP Entity is on the left, the L2RP Entity is on the top right, and the RLP Entity is on the bottom right. Lines connect the NTP Entity to the L2RP Entity and the RLP Entity, and the L2RP Entity to the RLP Entity.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg) + +Relay Entity + +NTP Entity L2RP Entity + +RLP Entity + +Figure 3: Diagram of the L2R sub-functions. A large box labeled 'Relay Entity' contains three sub-entities: 'NTP Entity', 'L2RP Entity', and 'RLP Entity'. The NTP Entity is on the left, the L2RP Entity is on the top right, and the RLP Entity is on the bottom right. Lines connect the NTP Entity to the L2RP Entity and the RLP Entity, and the L2RP Entity to the RLP Entity. + +Figure 3 + +The 3 sub-functions are: + +- a Non Transparent Protocol Entity; +- a L2R Protocol Entity; +- a Relay Entity. + +The NTP-entity interfaces the L2R to the IFP-entity and provides an interface to the particular NTP. + +The L2RP-entity interfaces the L2R to the RLP-entity and provides an interface to the appropriate L2R protocol. + +The Relay-entity provides the mapping between the NTP-entity and the L2R-entity. If applicable, it contains the data compression function. The negotiable parameters are exchanged with the remote Relay-entity by means of the RLP XID frame. + +It should be noted that the inter-layer interfaces within the MS and the IWF and within the L2R is not specified by 3GPP. The description given is for explanatory purposes only and is not intended to indicate a method of implementation. Therefore, the specification of the L2R is in terms of the peer-peer protocols. Generally, the non transparent and interface protocols are specified elsewhere, e.g. ITU-T Recommendations V.110 or V.120. Thus the main specification for the L2R consists of the L2R peer-peer protocols. + +### 6.1.1 Layer 2 Relay in Frame Tunneling Mode + +L2R is used in FTM to transport asynchronous HDLC (see [44]) frames between the MS and the IWF. In this case there is no NTP entity on the IWF side. Instead, the L2R entity interfaces a conversion function that performs a mapping between asynchronous and synchronous HDLC frames, which are transported on a UDI or RDI bearer with X.31 flag stuffing as rate adaptation. Consequently there is no error correction or flow control on the fixed network leg. (The HDLC FCS is used by the higher layer protocol, and error correction and flow control are performed end-to-end between the two DTEs.) + +## 6.2 Radio Link Services Used + +The L2R function uses services defined in 3GPP TS 24.022. + +## 6.3 Flow Control - General Description + +A flow control active condition may take place under a number of circumstances: + +- end-to-end flow control (DTE to DTE matter); +- backpressure (buffers filling); +- receive not ready (RLP condition). + +It is possible that there may be an interaction between flow control active and inactive conditions in each circumstance. + +### 6.3.1 End to End Flow Control + +A DTE may wish to send a flow control active condition to another DTE. + +Provisions exist in the L2R entity to transfer a flow control active condition (sent by its associated DTE) to the other L2R entity as soon as possible. This mechanism in the L2R entities allows such a flow control condition to be put ahead of any queuing which exists in the L2R entities. + +Such a mechanism avoids undesirable build up of data buffers. + +The L2R entity, receiving a flow control active condition from its associated DTE, stops sending data to that associated DTE immediately. + +### 6.3.2 Back Pressure + +The L2R and RLP entities have buffers which may become full to a predetermined threshold for a number of reasons, e.g. severe radio fading, failure or slowness of DTE to react to end to end flow control, certain RNR conditions. When this predetermined threshold is reached, a flow control active condition is sent to the associated DTE which is then prevented from sending any data. Subsequently, the flow control inactive condition is sent to the associated DTE when the L2R or RLP entities have indicated that there is sufficient free capacity in their buffers for data flow from the associated DTE to proceed. + +The corresponding peer-layer procedure to assess the respective buffer conditions is a layer management matter and is not dealt with here. It is also considered an implementation matter to ensure that such procedure do not result in loss of data or considerable reduction in throughput. + +In FTM, back pressure is not applicable towards the DTE on the fixed network side, because there is no flow control mechanism on the fixed network leg. Consequently buffer overflow may occur leading to loss of data, which is left to the higher layer protocol to handle. + +### 6.3.3 Receive not Ready + +When the RNR condition arises, an RLP indication is sent to the other RLP entity which in turn shall send a flow control active condition to its associated L2R entity. That L2R entity shall then send a flow control active condition to its associated DTE. + +An RNR condition may result in the Execution of "back pressure" as mentioned under subclause 6.3.2. + +## 6.4 User initiated service level up and down grading (applies to A/Gb and GERAN Iu mode only) + +When the value of the negotiated UIMI parameter is greater than 0, the MS may at any time during the call, control, to some extent, the number of traffic channels to be used. This is done by signalling a higher or lower value for the Wanted Air Interface User Rate (WAIUR) and maximum number of traffic channels (mTCH). The network may assign an AIUR matching the WAIUR using up to mTCH traffic channels, provided that the resources are available (3GPP TS 22.034, 3GPP TS 23.034 and 3GPP TS 24.008). + +If the value of the RLP optional feature 'Up signalling' is negotiated to 1, the MS may receive a suggestion from the network to initiate an upgrading. This occurs when the following condition holds: + +The IWF: + +- 1) is receiving user data from the fixed network side at a higher rate than the current AIUR; or +- 2) in symmetrical calls only, can send user data towards the fixed network side at a higher rate than the current AIUR. + +The MS can detect the condition stated in 1) and 2) above by examining the value of the UP bit in the received RLP S and I+S frames. When the condition does not hold, the value of the UP bit is continuously 0. If the condition does hold, the number of 1s between two consecutive 0s indicates the number of traffic channels to upgrade by. There is no need to repeat this indication since the FCS protects it. For instance, if the UP bit sequence is ...01100... and the current number of assigned traffic channels is 2, then an upgrading 4 traffic channels is suggested. + +NOTE: From MSC/IWF's perspective a TCH/F28.8 or TCH/F43.2 EDGE configuration is identical to a multislot 2×TCH/F14.4 or 3×TCH/F14.4 configuration. Therefore, a factor of 1/2 or 1/3 has to be applied to the suggested increase when the assigned up link channel is TCH/F28.8 or TCH/F43.2 respectively. + +The MS may use the information signalled in the UP bit to find out when a service level upgrading may increase the data throughput. In order to initiate a service level upgrading, the value of UIMI shall be greater than the number of currently assigned channels. + +In order to determine when to downgrade, the MS may compare the rate of received and sent information in the RLP frames to the AIUR. If the rate of received and sent information is less than the current AIUR the MS may initiate a downgrading. + +User initiated service level up and down grading mechanism may also be used to modify the asymmetry preference, see subclause 6.5. This is achieved by sending a new value of the asymmetry preference in the BC-IE. + +## 6.5 Asymmetry preference indication (applies to A/Gb and GERAN Iu mode only) + +The MS's classmark may restrict the possible number of channels or modulation that may be assigned by the network in one of the directions. This may result in an asymmetric transmission, i.e., different numbers of channels or modulations are assigned in each direction. + +Asymmetric transmission may also result from a preference indication. At call set up, the MS may send an asymmetry preference indication in the BC-IE (see 3GPP TS 24.008). There are three options: + +- 1) no preference; +- 2) up link biased asymmetry preferred; +- 3) down link biased asymmetry preferred. + +If down or up link asymmetry preference is indicated, the network shall not assign EDGE channels on the unbiased link. If the network assigns EDGE channels on the biased link, it shall assign TCH/F14.4 on the unbiased link. The WAIUR shall then apply to the biased link. + +# --- 7 Structure of the 3GPP TS 27-series of Specifications + +The structure of the Specifications is as follows: + +3GPP TS 27.001 General on Terminal Adaptation Functions for Mobile Stations. + +3GPP TS 27.002 Terminal Adaptation Functions for Services using Asynchronous Bearer Capabilities. + +This document defines the interfaces and terminal adaption functions integral to a MT which enable the attachment of Asynchronous Terminals to a MT. + +3GPP TS 27.003 Terminal Adaptation Functions for Services using Synchronous Bearer Capabilities. + +This document defines the interfaces and terminal adaptation functions integral to a MT which enable the attachment of Synchronous Terminals to a MT. + +# 8 Functions common to all interfaces + +## 8.1 Synchronization of the Traffic Channel + +As long as there is no connection between the traffic channel and the interface to the TE this interface shall be terminated in the appropriate way. + +Prior to exposing the traffic channel of a PLMN connection to transmission of user data, the controlling entities of the connection shall assure the availability of the traffic channel(s). This is done by the so called synchronization process: + +- starting on the indication of "physical connection established" resulting from the PLMN inherent outband signalling procedure. This indication is given: + - for MO calls: on reception of the CONNECT message; + - for MT calls: on reception of the CONNECT ACKNOWLEDGE message; + - for mobile initiated in-call modification: on reception of the MODIFY COMPLETE message; and + - for network initiated in-call modification: on sending the RR/RRC message confirming the reconfiguration of the traffic channel (in A/Gb mode: ASSIGNMENT COMPLETE, HANDOVER COMPLETE, or CHANNEL MODE MODIFY ACKNOWLEDGE; in Iu mode: RADIO BEARER RECONFIGURATION COMPLETE, TRANSPORT CHANNEL RECONFIGURATION COMPLETE, or PHYSICAL CHANNEL RECONFIGURATION COMPLETE); +- ending by indicating the successful execution of this process to the controlling entity, which then takes care of the further use of the inband information (data, status). + +During the call control phases (set-up and clear), the procedures at the V.-series DTE interfaces may be mapped completely to the out-of-band signalling procedure. The state of the S-bits and X-bits during the call control phases are in this case irrelevant to the DTE interface procedures. However, the "ready for data" condition (i.e. CTs 106 and 109) is derived from the status bits received by the TAF once synchronization is complete. Since half duplex operation is not supported by a PLMN, status bit SB is not needed to signal the turn around of the connection. + +### 8.1.1 Transparent services + +#### 8.1.1.1 Initial procedure for traffic channel types TCH/F4.8 and TCH/F9.6 + +With respect to the TAF, for the transparent bearer capability support the synchronization procedure with the channel codings 2.4 kbit/s, 4.8 kbit/s and 9.6 kbit/s is as follows: + +- sending of synchronization pattern 1/OFF (all data bits "1" / all status bits "OFF", all E-bits "1") to the IWF. In multislot transparent operation, the synchronisation pattern sent is 1/OFF with the exception of the bit positions S1, first X, S3, and S4 which contain the substream number and multiframe alignment pattern (see 3GPP TS 44.021); +- searching for detection of the synchronization pattern received from the IWF, and in multislot operation, also searching for the multiframe alignment pattern "0000 1001 0110 0111 1100 0110 1110 101" (see 3GPP TS 44.021) in bit position S4 and substream numbers in bit positions S1, first X, and S3. The value of the bits E4-E7 shall not be checked. + +#### 8.1.1.2 Initial procedure for traffic channel types TCH/F14.4 and TCH/F28.8 + +With respect to the TAF, for the transparent bearer capability support, the procedure with the TCH/F14.4 or TCH/F28.8 is as follows: + +- sending of synchronization pattern 1/OFF (all data bits "1" / status bits in M2 "OFF") to the network in the multiframe structure with the multiframe alignment pattern "0000 1001 0110 0111 1100 0110 1110 101" in the M1 (see 3GPP TS 44.021) and, in a multislot or TCH/F28.8 case, sending substream numbers in the bit M2; +- searching for the detection of the multiframe alignment pattern "0000 1001 0110 0111 1100 0110 1110 101" (see 3GPP TS 44.021) in the bit M1 originating from the network, and, in a multislot or TCH/F28.8 case, searching for substream numbers in the bit M2. (Any 5 bits sequence in the multiframe alignment pattern is unique, i.e. the multiframe alignment can take place by the recognition of five successive S1 bits). + +#### 8.1.1.3 Subsequent procedures for traffic channel types TCH/F4.8, TCH/F9.6, TCH/F14.4, and TCH/F28.8 + +When the synchronisation pattern and, in case of multislot, TCH/F14.4 or TCH/F28.8 operation the multiframe alignment pattern from the IWF have been recognized as a steady state (see note) the TAF continues sending the synchronization patterns to the IWF until a timer T (= 500 ms) expires. + +NOTE: An idle frame sent by the BSS and received by the MS has the same pattern as the synchronization pattern 1/OFF. + +At the moment when the message CONNECT (MO) or CONNACK (MT) is received at the MS, it is guaranteed that this pattern is received from the MSC/IWF with the exception of a loss of frame synchronization on the Abis interface. + +The handling of frame stealing in case of 2400 bit/s full rate data channels is implementation dependent. + +##### 8.1.1.3.1 V.-series interface + +During the synchronization process described above, i.e. while the synchronization pattern is being sent by the MT, CT106, 107 and 109 remain in the OFF condition. + +After the expiration of the timer T of each allocated traffic channel for the call, the X and SB bits received from the IWF are mapped on to CT 106 and CT 109, respectively, at the MT/DTE interface according to the filtering process described in subclause 8.2. The received SA bit, if available, is ignored. The condition on CT107 is changed from "OFF" to "ON", the data bits received from the IWF are mapped to CT104, and CT103 is mapped to the data bits sent towards the IWF. The transmitted SA (if available), SB and X bits shall be set to "ON". + +##### 8.1.1.3.2 X.-series interface + +Void. + +##### 8.1.1.3.3 S interface (I.420) + +Void. + +#### 8.1.1.4 Procedures for RLC + +With respect to the TAF for T bearer support, the procedure is as follows: + +- no access stratum SDUs are transmitted until an access stratum SDU is received. + +##### 8.1.1.4.1 V.-series interface + +Until the first access stratum SDU is received at the transmission SAP, CT 106, 107 and 109 remain in the OFF condition. At the reception of the first SDU, CT 106, CT 107 and CT 109 are changed from OFF to ON at the DCE/DTE (TE/TAF) interface. The data received in each SDU are mapped to CT 104 and data on CT 103 are mapped to SDUs sent toward the RNC. + +### 8.1.2 Non-transparent services + +With respect to the TAF, for non-transparent bearer capability support, the synchronization procedure in A/Gb and GERAN Iu mode is as follows: + +- firstly, receiving frames on all allocated traffic channels for the call; +- secondly, initiating the RLP link establishment by sending a RLP-SABM across the radio interface. + +In UTRAN Iu mode, the TAF shall initiate the RLP after the physical connection has been established. + +#### 8.1.2.1 V.-series interface + +During the synchronization process described above, i.e. while the synchronization pattern is being sent by the MT, CT106, 107 and 109 remain in the OFF condition. + +When the RLP link has been established, CT107 shall be changed from "OFF" to "ON". From this time the information from/to the RLP, including status changes, shall be mapped by the L2R entity applicable to the particular bearer capability (3GPP TS 27.002 "L2R functionality"). + +#### 8.1.2.2 X.-series interface + +Void. + +#### 8.1.2.3 S interface (I.420) (does not apply to UTRAN Iu mode) + +Void. + +### 8.1.3 Action on loss of synchronization + +#### 8.1.3.1 Loss at the TAF-radio interface + +In A/Gb and GERAN Iu mode, if the TAF detects a loss of synchronisation on one or more channels, it initiates the re-synchronisation process. The TAF searches for the data frame structure in those channels in which the synchronisation has been lost according to the initial procedures described in subclauses 8.1.1 and 8.1.2. The information received from the channels shall continue to be processed as if the synchronisation had not been lost, i.e. corrupted data is forwarded towards RLP entity or TE during the re-synchronisation process. No action shall be taken on the frames being transmitted towards the MSC, other than to continue sending them normally. + +In UTRAN Iu mode, no action shall be taken. + +#### 8.1.3.2 Loss at the TAF-terminal interface + +Void. + +## 8.2 Filtering of Channel Control Information (A/Gb or GERAN Iu mode transparent mode only) + +### 8.2.1 General + +The DTEs used at the MS side of the PLMN conforms to ITU-T's DTE/DCE interface specifications, which assume basically an error-free environment, i.e.: + +- limited distance, point-to-point local interconnection of the interface circuits for data and status; +- steady state signalling. + +The envisaged use of these DTEs in the PLMN environment leads to the exposure of these "interconnections" to the PLMN radio channel. To assure proper operation even under these conditions appropriate measures have to be taken. In the non transparent case the RLP satisfies the requirement for both data and status lines. + +In the transparent case the: + +- data line aspects have to be dealt with end-to-end by the users; while +- status line aspects are of concern to the network, and are dealt with in the following. + +### 8.2.2 Filtering process to be applied + +Filtering of channel control information is relevant only at the MS side and in the transparent mode of operation. By applying filtering measures the condition of a DTE/DCE control interchange circuit, for which the DTE constitutes the + +information sink, is preserved until another condition is signalled for an "integration time" period by the channel control information (status bits) of the rate adaptation scheme. + +The filtering mechanism is understood to reside between the rate adaptation function (information source) and the DTE (information sink). It receives the unfiltered condition of the respective control interchange circuit set according to the actual sequential appearance of the individual associated status bits and forwards the filtered condition to the DTE. + +The filtering process starts when the traffic channel synchronization ends with the expiry of timer T. + +#### 8.2.2.1 V.-series interface + +##### CT 106 + +In the transparent mode the remote inband control of this circuit is needed to support a modem retrain procedure. + +OFF-ON transition at the MS authorizes the DTE to send data; if wrongly set, loss of data may occur. + +ON-OFF transition at the MS causes the DTE to cease transmitting data; set wrongly may impair the performance in connection usage. + +##### CT 109 + +In the transparent mode the remote inband control of this circuit is needed to: + +- trigger the interpretation of received data; +- indicate to the DTE the state of the connection. + +OFF-ON transition at the MS authorizes the DTE to rely on the condition of the received data interchange circuit, set wrongly may cause receipt of wrong data, while setting late may cause loss of data. + +ON-OFF transition at the MS: + +- causes the DTE to cease receiving data; +- may initiate release of the connection during a data phase by the DTE giving an ON-OFF transition on circuit 108/2. + +Setting this condition wrongly may cause loss of data and potentially release the connection. + +#### 8.2.2.2 X.-series interface + +Void. + +#### 8.2.2.3 Filtering mechanism + +##### 8.2.2.3.1 Traffic channel types TCH/F4.8 and TCH/F9.6 + +A filtering mechanism shall be provided by an integration process on those SB and X bits carrying status information in the V.110 frame or in the multiframe structure. The integration periods applied are: + +| V-series | Transition | Integration period | Status stream | +|----------|------------|--------------------|---------------| +| CT 106 | Off-On | 1 s | X | +| CT 106 | On-Off | 1 s | X | +| CT 109 | Off-On | 200 ms | SB | +| CT 109 | On-Off | 5 s | SB | + +The integration process shall ensure that the interchange circuits do not change state in response to spurious transitions of the status bits during the integration period. + +The integration process shall operate reliably with error characteristics as specified in 3GPP TS 45.005. + +##### 8.2.2.3.2 Traffic channel type TCH/F14.4 + +To change the state of CT 109 or CT 106, it is required that at least two consecutive SB-bits or X-bits, respectively, carry the same value. + +## 8.3 Terminal Compatibility Decision + +The establishment of a mobile terminated connection depends on a positive decision on the terminal compatibility. The Mobile Station (MS) contributes to this process by performing (depending on the individual call set-up condition): + +- a compatibility check; +- the selection of the appropriate terminal function; and +- the indication of compatibility requirements to the PLMN; + +initiated by a call set-up request from the PLMN. The aforementioned functions shall be carried out as follows. + +### 8.3.1 Compatibility Check + +Annex B of 3GPP TS 24.008 applies, particularly clause B.3, subclauses B.3.1 and B.3.2. As regards the therein mentioned user-to-user compatibility checking the following applies: + +When the calling user requests a service with user-to-user compatibility significance indicated by the presence of HLC and LLC information element in the call set-up request, the MS shall check that the service supported by the called user matches concerning the contents of the HLC/LLC information element. If a mismatch is detected, then the MS shall reject the offered call using the cause No.88 "Incompatible Destination". + +### 8.3.2 Selection of Appropriate Terminal Function + +The MS shall select the appropriate terminal functions following a positive result of the compatibility check and/or forwarding the indication of compatibility requirements to the PLMN. + +### 8.3.3 Indication of Compatibility Requirements to the PLMN + +#### 8.3.3.1 Indication in case of Mobile terminating calls + +In support of: + +- PSTN originated calls; and +- ISDN originated calls using 3,1 kHz audio Bearer Capability (BC); as well as +- ISDN originated calls using unrestricted digital Bearer Capability but not specifying all parameters for deducing a Bearer Service. + +Mobile specific requirements to be dealt with in the Bearer Capability information element the call confirmed message has been introduced in the call control protocol (3GPP TS 24.008). This also allows for re-negotiation of specific parameters at the beginning of the connection set-up process. The specific parameters are: + +- a) mobile specific requirements: + - Connection element (transparent/non transparent); + - Structure (note 1); + - Synchronous/Asynchronous (note 8); + - Rate adaptation/other rate adaptation (note 9); + - User information layer 2 protocol (note 1); + - Intermediate rate (note 2), (note 3); + - Modem Type (note 1), (note 3); + +- User Rate (note 3); +- Compression , +- Fixed network user rate, (note 3) (note 4); +- Other modem type, (note 3) (note 4); +- User initiated modification indication (note 4). + +The following parameters are indicated by the MS to the network, only: + +- Radio Channel Requirement; +- Acceptable channel codings (note 5); +- Maximum number of traffic channels, (note 5); +- Wanted air interface user rate (note 6) (note 7); +- Asymmetry preference indication (note 7). + +NOTE 1: This parameter is correlated with the value of the parameter connection element. + +NOTE 2: For non-transparent services this parameter is correlated with the value of the parameter negotiation of intermediate rate requested. + +NOTE 3: Modification of these parameters may be proposed by the MS. The Network may accept it or not. + +NOTE 4: This parameter shall be included by the MS only if it was received from the network. + +NOTE 5: This parameter shall be included only if the parameter 'fixed network user rate' is included. + +NOTE 6: This parameter shall be included only for non-transparent services and if the parameter 'fixed network user rate' is included. + +NOTE 7: This parameter has to be included if EDGE channel coding(s) are included in Acceptable channel codings. In cases where this parameter would not otherwise be included, the value is set to 'Air interface user rate not applicable' or 'User initiated modification not requested' or "No preference". + +NOTE 8: For FTM and PIAFS, this parameter may be negotiated as in table B.4e. How the subscription for BS20 is assured, is an operator matter. + +NOTE 9: For FTM, PIAFS or Multimedia, this parameter may be negotiated as in table B.4f. + +b) requirements with effects at the partner terminal: + +- Number of data bits; +- Number of stop bits; +- Parity. + +The MS indicates the radio channel requirement in the call confirmed message. If the MS indicates the support of "dual" (HR and FR channels) the final decision, which radio channel is chosen, is done by the network in an RR message. The radio channel requirement is ignored in UTRAN Iu mode, see table B.5a in Annex B. + +If the network proposes optional support of both transparent and non transparent connection elements, but does not indicate a user information layer 2 protocol, the MS shall set the appropriate value, if choosing non transparent in the call confirmed message and out-band flow control is not requested, see B.1.1.2. + +Additionally the values of the parameters structure, modem type and intermediate rate have to be set in conformance with the values of the parameters radio channel requirements, negotiation of intermediate rate requested and connection element. + +Subclause B.1.1.2 and table B.1 in the annex B describe the negotiation procedure. Annex B table B.4 describes the selection of the modem type and the dependence on the value of the parameter connection element. Annex B table B.4 + +describes the selection of the intermediate rate and user rate and their dependence upon the value of the NIRR parameter and the equipment capabilities. + +The following MT cases can be deduced from the individual call set-up request conditions: + +- a) If the set-up does not contain a BC information element, the MS in the call confirmed message shall include any BC information (single or multiple BC-IE). The MS may use the information provided in the BACKUP BC information element (see 3GPP TS 29.007 and 3GPP TS 24.008) to deduce the requested service. Note, that the presence of the BACKUP BC-IE does not change the condition of "no BC-IE received", that means in particular that the MS shall include any BC-IE (as mentioned before) and shall not negotiate parameter values where the MSC has to offer a value in the BC-IE first, as e.g., for the parameter "compression". If multiple BC-IEs are present, one BC-IE shall indicate the information transfer capability "speech". A 3,1 kHz multimedia BC-IE together with a speech BC-IE indicates the support of a fallback to speech. A UDI/RDI multimedia BC-IE together with a speech BC-IE indicates the support of service change and fallback (see 3GPP TS 29.007 and 3GPP TS 24.008). +- b) If the set-up message contains a single BC-IE, the MS in the call confirmed message shall use either a single BC-IE, if it wants to negotiate mobile specific parameter values or, unless otherwise specified, no BC-IE, if it agrees with the requested ones. +- c) If the set-up contains a multiple BC-IE, the MS in the call confirmed message shall use either a multiple BC-IE, if it wants to negotiate mobile specific parameter values or, unless otherwise specified, no BC-IE, if it agrees with the requested ones. + - For a 3,1kHz multimedia setup the MS may either accept the possibility of a fallback to speech by responding with two BC-IEs, or turn the call to a speech call by sending only a speech BC-IE in the call confirmed message or turn the call to a multimedia only call (i.e. no fallback to speech allowed) by sending only a multimedia BC-IE, in the call confirmed message. + - For a UDI/RDI multimedia setup, the MS may either accept the possibility of service change by responding with two BC-IEs , or turn the call to a speech call by sending only a speech BC-IE in the call confirmed message, or turn the call to a multimedia call by sending only a multimedia BC-IE in the call confirmed message. + - For facsimile, a single BC-IE, containing fax group 3 only, shall be used if a multiple BC-IE requesting speech alternate fax group 3 is received and the MS is not able to support the speech capability. Annex B, table B.7, describes the negotiation rules. + +If the BC-IE contains 3,1 kHz ex PLMN, the MS is allowed to negotiate all mobile specific parameter values listed above. If the BC-IE contains facsimile group 3, the MS is not allowed to negotiate any mobile specific parameter value. In any case, if the set-up message requests a "single service", the MS shall not answer in the call confirmed message requesting a "dual service". + +However, for dual services with repeat indicator set to "circular (alternate)" or to "service change and fallback" the MS may change the sequence of dual BC-IEs within the call confirmed message (preceded by the same value of the repeat indicator), if it wants to start with a different Bearer Capability than proposed by the network as the initial one. + +In addition, the MS may propose to the network to modify User Rate, Modem Type and Intermediate Rate in the CALL CONFIRMED message. The network may accept or release the call. + +If the BC-IE received from the network contains the parameters 'fixed network user rate', 'other modem type' and possibly the 'user initiated modification', the MS shall either: + +- a) include no BC-IE or a BC-IE without these parameters in the call confirmed message, i.e. the MS discards these parameters (only allowed in A/Gb mode); or +- b) include the possibly modified values for the 'fixed network user rate' and 'other modem type' in the BC-IE of the call confirmed message. The network might accept or reject the modified values. In this case the MS shall also include the parameters 'maximum number of traffic channels' and 'acceptable channel codings'. Additionally for non-transparent services, the MS shall also include the parameters 'wanted air interface user rate' and the 'user initiated modification indication'. The parameters 'acceptable channel codings extended' and 'asymmetry indication' may also be included. + +In case a), the MS shall use the fall-back bearer service indicated by the remaining parameters of the BC-IE on a single slot configuration (reference 3GPP TS 44.021). + +In case b), the MS shall use in A/Gb or GERAN Iu mode a singleslot or multislot configuration according to the rules defined in 3GPP TS 44.021, 3GPP TS 48.020 and 3GPP TS 24.022. + +If the 'acceptable channel codings' is indicated by the MS, the decision which channel coding is used is done by the network and indicated to the mobile station with a RR message. This RR message may also assign an asymmetric channel coding. The 'acceptable channel codings' parameter takes precedence over the 'negotiation of intermediate rate requested' parameter for non-transparent services. Also the intermediate rate and user rate per traffic channel in a multislot configuration are not indicated by the 'intermediate rate' and 'user rate' parameters of the BC-IE, but depend on the chosen channel coding only. + +If no BC-IE is received in the SETUP message, the MS may include the parameters 'fixed network user rate', 'other modem type' etc. (i.e. octets 6d, 6e, 6f, and 6g, see 3GPP TS 24.008) in the BC-IE of the CALL CONFIRMED message. However, in this case, the network may release the call if it does not support these parameters. + +If FNUR = 33.6 kbit/s is agreed on in the setup of a 3.1 kHz multimedia call, the modems may handshake to 31.2 kbit/s or 28.8 kbit/s. In this case the MS receives a MODIFY message from the MSC to indicate the new data rate, and shall respond with a MODIFY COMPLETE message (see 3GPP TS 24.008), if it supports the requested modification. If the MS does not support the requested modification, it shall respond with a MODIFY REJECT message. The MT shall indicate the new data rate to the TE (e.g. using the ITU-T Recommendation V.80 inband signalling) in order to cause the TE to use stuffing to adapt the 31.2 or 28.8 kbit/s data rate to the 33.6 kbit/s traffic channel between the TE and IWF. + +#### 8.3.3.2 Indication in case of Mobile originating calls + +In support of mobile originating calls the values of BC-IE parameters are requested in the set-up message from the MS. If the MS indicates the support of both transparent and non transparent connection elements the network shall return its choice in the call proceeding message. The MS is not allowed to indicate support of both transparent and non transparent, if the MS also requests out-band flow control, i.e. it does not indicate a layer 2 protocol. + +Additionally the value of the parameter modem type has to be set depending on the value of the parameter connection element as described in annex B, table B.4a. + +The set-up message contains a single or multiple BC-IE. If multiple BC-IEs are present, one BC-IE shall indicate the information transfer capability "speech". + +For a 3,1 kHz multimedia call, the setup message contains either a multimedia BC-IE indicating a multimedia only call request (i.e. no fallback to speech allowed) or both a 3,1 kHz multimedia BC-IE and a speech BC-IE to indicate the support of a fallback to speech (see 3GPP TS 29.007 and 3GPP TS 24.008). + +For a UDI/RDI multimedia call, the setup message contains either a multimedia BC-IE indicating a multimedia only call request, or both a multimedia BC-IE and a speech BC-IE (in any order) to indicate the support of service change and fallback (see 3GPP TS 29.007 and 3GPP TS 24.008). The latter is not applicable to multimedia calls with FNUR=32.0 kbit/s. + +If the set-up message requests a "single service", the network shall not answer in the call proceeding message requesting a "dual service". Alternatively the network shall answer with a single BC-IE containing fax group 3 if a multiple BC-IE requesting speech alternate fax group 3 is received but the network does not allow the use of this alternate service. Annex B, table B.7, describes the negotiation rules. + +If the MS requests a "dual service" the network is not allowed to change the sequence of the service, a change may however occur due to the called user and this may then be relayed back to the originating MS by the network. + +If the setup message requests a 3.1 kHz multimedia service with fallback, the network may return both BC-IEs in the same order to accept the request, or a single BC-IE if fallback or one of the requested services are not allowed. + +If the setup message requests a UDI/RDI multimedia service with fallback, the network may return both BC-IEs in the same order to accept the request, both BC-IEs in the reverse order (relayed from terminating User), or a single BC-IE if fallback, service change or one of the requested services are not allowed. + +If the set-up message indicates that negotiation of intermediate rate is requested then the network shall behave as described in annex B, table B.4b. + +Unless otherwise specified, if no BC-IE parameter needs negotiation it is up to the network if it sends a CALL PROCEEDING message (with or without a BC-IE) towards the MS or not. + +For MS to network direction, octet 6e shall be included whenever octet 6d is included (see 3GPP TS 24.008). + +For multislot, TCH/F14.4, and EDGE operations and in Iu mode the MS shall include an appropriate set of the parameters 'fixed network user rate', 'other modem type', 'maximum number of TCH' and 'acceptable channel codings' in the BC-IE of the SETUP message. If EDGE channel coding(s) are included in ACC for transparent calls, the 'Wanted air interface user rate'-parameter shall be set to 'Air interface user rate not applicable' and the 'User initiated modification indication'-parameter to 'User initiated modification not requested'. In a non-transparent multislot operation, the MS shall also include the parameters 'wanted air interface user rate' and 'user initiated modification indication' in the BC-IE of the SETUP message. In a non-transparent TCH/F14.4 or EDGE operation or in Iu mode the MS shall also include the parameter 'wanted air interface user rate'. In non-transparent EDGE operation the MS shall also include the parameter 'asymmetry preference indication'. It shall also set the other parameters of the BC-IE (i.e. 'user rate') to values identifying fall-back values. Depending on the network two situations can be distinguished: + +- a) The network supports the requested operation: + - in this case the network shall include the parameter 'fixed network user rate', 'other modem type' and possibly 'user initiated modification' in the BC-IE(s) of the CALL PROCEEDING message, irrespective whether or not they contain modified values or just a copy of the received ones; + - the 'acceptable channel codings' indicated by the MS in the SETUP message takes precedence over the 'negotiation of intermediate rate requested' parameter for non-transparent services. The intermediate rate per traffic channel and the user rate per traffic channel is dependent on the chosen channel coding only. The chosen channel coding is indicated to the mobile station by the network with an RR message. +- b) The network does not support the requested operation: + - in this case, in A/Gb mode, the BC-IE of the CALL PROCEEDING message does not contain the parameters 'fixed network user rate' and 'other modem type' or no BC-IE is included in the CALL PROCEEDING message at all. The mobile station shall then discard the parameters 'fixed network user rate', 'other modem type', 'maximum number of TCH', 'acceptable channel codings', 'wanted air interface user rate' and 'user initiated modification indication' sent with the SETUP message and apply the fall-back bearer service; + - in Iu mode the network shall release the call. + +In case a), the MS shall use in A/Gb and GERAN Iu mode a singleslot or multislot configuration according to the rules defined in 3GPP TS 44.021, 3GPP TS 48.020 and 3GPP TS 24.022. + +In case b), the MS shall use in A/Gb mode the fall-back bearer service indicated by the remaining parameters of the BC-IE on a single slot configuration (reference 3GPP TS 44.021). + +If FNUR = 33.6 kbit/s is agreed on in the setup of a 3.1 kHz multimedia call, the modems may handshake to 31.2 kbit/s or 28.8 kbit/s. In this case the MS receives a MODIFY message from the MSC to indicate the new data rate, and shall respond with a MODIFY COMPLETE message (see 3GPP TS 24.008), if it supports the requested modification. If the MS does not support the requested modification, it shall respond with a MODIFY REJECT message. The MT shall indicate the new data rate to the TE (e.g. using the ITU-T Recommendation V.80 inband signalling) in order to cause the TE to use stuffing to adapt the 31.2 kbit/s or 28.8 kbit/s data rate to the 33.6 kbit/s traffic channel between the TE and IWF. + +#### 8.3.3.3 Differences in validity of BC parameter values in A/Gb mode, GERAN Iu mode and UTRAN Iu mode + +The validity of a BC parameter value, either in the SETUP or CALL CONFIRMED message, may differ from A/Gb mode to GERAN Iu mode and to UTRAN Iu mode. Certain parameters are irrelevant in UTRAN or GERAN Iu mode and any value given is valid and ignored. These parameters may be available in the BC IE. For those parameters that are relevant in UTRAN Iu mode, GERAN Iu mode and A/Gb mode, certain values may be invalid in one of the systems. Invalid parameter values may cause rejection of the BC and subsequent release of the call. + +Parameters that are ignored in UTRAN or GERAN Iu mode may be set to default values, or to specific values in view of an eventual handover to A/Gb mode. They may also be set to values that make call setup in current system + +impossible. This indicates the need for a handover to another radio access technology. Parameter values that are invalid in one system may also result in unsuccessful handover from the other system. + +Table B.5a in annex B lists parameters that are ignored in UTRAN or GERAN Iu mode and parameter values which validity is different in A/Gb mode, GERAN Iu mode and UTRAN Iu mode. + +## 8.4 Test Loops + +In principle, both V -series and X -series interfaces allow for an activation of local or remote test loops by the terminal (see ITU-T Recommendations V.54/X.150). A comprehensive solution of such test loops in a PLMN system has to consider the special conditions of the interface between the terminal (part of the MS) and the transmission equipment (part of the modem pool of a particular IWF within the MSC). In addition, the impact of the radiolink is to be taken into account with respect to the test objectives. Due to those special conditions a PLMN system is not capable to support remote test loops. It is an implementation choice to what extent the activation of local test loops by the terminal is supported in the MT. + +## 8.5 Alternate speech/facsimile group 3 + +### 8.5.1 In case of A/Gb mode + +This alternate service may be initiated by a manual procedure where CT106, CT107, CT108.2 and CT109 are set in the OFF condition. + +Selection of the data phase (from the speech phase) may be by manual intervention via the MS causing ICM by means of CT108.2 going to ON condition, refer to 3GPP TS 03.45. The ensuing data phase shall follow all the operational procedures as described in 3GPP 27-series. + +Selection of the speech phase (from the data phase) may be by manual intervention via the MS causing ICM (phone off-hook condition at the MT and data call end condition at the TE). + +During the ensuing speech phases, CT107, CT106 and CT109 shall be maintained in the OFF condition. + +Subsequent re-selection of the data phase may be by manual intervention via the MS causing CT108.2 going to ON condition initiating ICM. At this point, re-synchronization shall take place as described in subclause 8.1. + +### 8.5.2 In case of UTRAN Iu mode + +Refer to subclauses 9.2.1.1 and 9.2.2.1 in 3GPP TS 23.146. + +## 8.6 Multislot configuration split/combine function + +In multislot configurations using multiple parallel channels the data flow is split into substreams between the Split/Combine-function in the TAF and the network. + +### 8.6.1 Non-transparent data + +In non-transparent data operations the N(S)-numbering in the RLP-header is used for controlling the order of the data in the substreams (reference 3GPP TS 24.022). + +### 8.6.2 Transparent data + +In transparent multislot configurations (TCH/F9.6 or TCH/F4.8) status bits S1, S3 and the X-bit between the D12 and D13 are used for transferring substream numbering information. This S4-bit is used for frame synchronization between the parallel substreams (reference 3GPP TS 44.021). + +In case of a transparent multislot configuration using TCH/F14.4 channel coding, bit M1 in the 290-bit radio interface block is used for frame synchronization between the parallel substreams, whereas bit M2 carries status information, NIC codes and substream numbering as described in 3GPP TS 44.021. + +In transparent TCH/F28.8 channels, bits M1 and M2 are used as described above for transparent TCH/F14.4 channels. + +## 8.7 EDGE multiplexing function + +In EDGE configurations the number of channels across the air interface and that of substreams between BTS and MSC do not necessarily match. In such cases a multiplexing function is included at MS and BTS (3GPP TS 44.021 and 3GPP TS 48.020). These functions distribute data between the substreams and radio channels. + +## 8.8 Seamless data rate change + +If the modems change the data rate during an ongoing multimedia call (using the ITU-T Recommendation V.34 seamless data rate change mechanism), the MSC initiates a MODIFY message (see 3GPP TS 24.008) to indicate the new data rate to the MS. The MT shall indicate the new data rate to the TE (e.g. using the ITU-T Recommendation V.80 inband signaling) in order to cause the TE to use stuffing to adapt the 31.2 kbit/s or 28.8 kbit/s data rate to the 33.6 kbit/s traffic channel between the TE and IWF. + +# --- Annex A (informative): List of Bearer Capability Elements + +This annex lists the PLMN Bearer Capability Elements which need to be provided to support Terminal adaptation function to Interworking control procedures. Some parameters are ignored in GERAN or UTRAN Iu mode although present in the BC-IE. The validity of parameter values may also differ from A/Gb mode to GERAN Iu mode and to UTRAN Iu mode. The ignored parameters and the difference of parameter value validity in A/Gb mode, GERAN Iu mode and UTRAN Iu mode are listed in table B.5a in annex B. + +## Elements and their Values: + +### Information Transfer Capability: + +This element is relevant between the IWF and the fixed network. + +Values: + +- Speech: +- Unrestricted Digital: +- Group 3 Facsimile (note 1): +- 3,1 kHz Ex PLMN (note 2): +- Restricted Digital (note 3): + +NOTE 1: Used for facsimile transmission, unrestricted digital between MT and IWF and 3,1 kHz audio from IWF towards the fixed network. + +NOTE 2: Unrestricted digital between MT and IWF and 3,1 kHz audio from IWF towards the fixed network. + +NOTE 3: Unrestricted digital between MT and IWF and restricted digital information from IWF towards the fixed network; this value is signalled in the "Other ITC" element, due to a lack of further code points in the "ITC" element. + +### Transfer Mode: + +This element is relevant between MT and IWF + +Values: - Circuit + +### Structure: + +This element is relevant between MT and IWF. + +Values: - Service Data Unit Integrity (note 4) +- Unstructured (note 5) + +NOTE 4: Applicable for connection element "non transparent". + +NOTE 5: Applicable for connection element "transparent". + +### Configuration: + +This element is relevant for a PLMN connection. + +Values: - Point to point + +### Establishment: + +This element is relevant for a PLMN connection. + +Values: - Demand + +### **Sync/Async:** + +This element is relevant between TE/TA and MT and between IWF and the fixed network. + +Values: + +- Synchronous +- Asynchronous + +### **Negotiation:** + +This element is relevant between MT and IWF. + +Values: + +- In band negotiation not possible + +### **User Rate:** + +This element is relevant between TE/TA and MT and between IWF and the fixed network, except in case the parameter FNUR is present. + +Values: + +- 0.3 kbit/s +- 1.2 kbit/s +- 2.4 kbit/s +- 4.8 kbit/s +- 9.6 kbit/s +- 19.2 kbit/s (see note 6) + +NOTE 6: This value cannot be signalled between MT and IWF, but it can be used according to the rules in 3GPP TS 29.007 (tables 7A and 7B) for such connections. + +### **Intermediate Rate:** + +This element is relevant between MT and BSS and BSS and IWF + +Values: + +- 8 kbit/s +- 16 kbit/s + +#### **Network Independent Clock on Tx:** + +This element is relevant between TE/TA and MT in the transmit direction. + +Values: + +- Not required +- Required + +#### **Network Independent Clock on Rx:** + +This element is relevant between TE/TA and MT in the receive direction. + +Values: + +- Not accepted +- accepted + +#### **Number of Stop Bits:** + +This element is relevant between the TE/TA and MT and between IWF and fixed network in case of asynchronous transmission. + +Values: + +- 1 bit +- 2 bit + +#### **Number of Data Bits Excluding Parity If Present:** + +This element is relevant between TE/TA and MT and between IWF and the fixed network in case of a character oriented mode of transmission. + +Values: + +- 7 bit +- 8 bit + +### **Parity Information:** + +This element is relevant between TE/TA and MT and between IWF and the fixed network for a character oriented mode of transmission. + +Values: + +- Odd +- Even +- None +- Forced to 0 +- Forced to 1 + +### **Duplex Mode:** + +This element is relevant between MT and IWF. + +Values: + +- Full Duplex + +### **Modem Type:** + +This element is relevant between the IWF and the fixed network in case of 3,1 kHz audio ex-PLMN information transfer capability. + +Values: + +- V.21 +- V.22 +- V.22 bis +- V.26 ter +- V.32 +- autobauding type 1 +- none + +### **Radio Channel Requirement:** + +This element is relevant between MT and BSS + +Values: + +- Full Rate support only Mobile Station +- Dual Rate support Mobile Station/Half Rate preferred +- Dual Rate support Mobile Station/Full Rate preferred + +### **Connection Element:** + +This element is relevant between MT and IWF + +Values: + +- Transparent +- Non Transparent +- both, Transparent preferred +- both, Non transparent preferred + +### **User Information Layer 2 Protocol:** + +This element is relevant between TE/TA and MT and between IWF and the fixed network. + +Values: + +- ISO/IEC 6429 +- Character oriented Protocol with no Flow Control mechanism + +### **Signalling Access Protocol:** + +This element is relevant between TE/TA and MT. + +Values: - I.440/450 + +#### **Rate Adaptation:** + +This element is relevant between IWF and the fixed network. + +Values: - V.110/X.30 +- X.31 flagstuffing +- no rate adaptation +- V.120 (note 7) +- PIAFS (note 7) +- H.223 and H.245 (note 7) + +NOTE 7: This value is signalled in the "Other Rate Adaption" element, due to a lack of further code points in the "Rate Adaption" element. + +#### **Coding Standard:** + +This element refers to the structure of the BC-IE defined in 3GPP TS 24.008. + +Values: - GSM + +### **User Information Layer 1 Protocol:** + +This element characterizes the layer 1 protocol to be used between MT and BSS (Um interface) according to 3GPP TS 45.001, or between the MT and the RNC (Uu interface). + +Values: - default + +#### **Negotiation of Intermediate Rate requested:** + +This element is relevant between MT and BSS and BSS and IWF. + +Values: - no meaning associated +- 6 kbit/s radio interface is requested for a full rate channel with a user rate up to and including 4,8 kbit/s, non transparent service + +#### **Compression:** + +This element is relevant between MT and IWF. + +Values: - compression possible/allowed +- compression not possible/allowed + +#### **Rate adaption header / no header:** + +This element is relevant between IWF and the fixed network. It is only applicable for ITU-T V.120 rate adaptation. + +Values: - Rate adaption header not included +- Rate adaption header included + +#### **Multiple frame establishment support in data link:** + +This element is relevant between IWF and the fixed network. It is only applicable for ITU-T V.120 rate adaptation. + +Values: - Multiple frame establishment not supported. Only UI frames allowed. +- Multiple frame establishment supported. + +#### **Mode of operation:** + +This element is relevant between IWF and the fixed network. It is only applicable for ITU-T V.120 rate adaptation. + +Values: - Bit transparent mode of operation +- Protocol sensitive mode of operation + +#### **Logical link identifier negotiation:** + +This element is relevant between IWF and the fixed network. It is only applicable for ITU-T V.120 rate adaptation. + +Values: + +- Default, LLI=256 only +- Full protocol negotiation (note 8) + +NOTE 8: A connection over which protocol negotiation is executed as indicated in the "In-band / out-band negotiation" parameter. + +#### **Assignor / assignee:** + +This element is relevant between IWF and the fixed network. It is only applicable for ITU-T V.120 rate adaptation. + +Values: + +- Message originator is „default assignee" +- Message originator is „assignor only" + +#### **In-band / out-band negotiation:** + +This element is relevant between IWF and the fixed network. It is only applicable for ITU-T Recommendation V.120 rate adaptation. + +Values: + +- Negotiation is done with USER INFORMATION messages on a temporary signalling connection +- Negotiation is done in-band using logical link zero. + +#### **Fixed network user rate, FNUR (note 12)** + +This element is relevant between the IWF and the fixed network. + +Values + +- Fixed network user rate not applicable (note 9) +- 9,6 kbit/s +- 14,4 kbit/s +- 19,2 kbit/s +- 28,8 kbit/s +- 32,0 kbit/s +- 38,4 kbit/s +- 48,0 kbit/s +- 56,0 kbit/s +- 64,0 kbit/s + +NOTE 9: Not used by currently specified services. + +#### **Wanted air interface user rate, WAIUR (note 12)** + +This element is relevant between the MT and the IWF + +Values + +- Air interface user rate not applicable +- 9,6 kbit/s +- 14,4 kbit/s +- 19,2 kbit/s +- 28,8 kbit/s +- 38,4 kbit/s +- 43,2 kbit/s +- 57,6 kbit/s +- interpreted by the network as 38,4 kbit/s (note 10) + +NOTE 10: Certain code points, if used, are interpreted by the network as 38.4 kbit/s in this version of the protocol, ref 3GPP TS 24.008. + +#### **Acceptable channel codings, ACC (note 12)** + +This element is relevant between the MT and the IWF. + +Value: + +- TCH/F4.8 acceptable +- TCH/F9.6 acceptable +- TCH/F14.4 acceptable +- TCH/F28.8 acceptable +- TCH/F32.0 acceptable (Applicable to multimedia 32 kbit/s, 56 kbit/s and 64 kbit/s and synchronous transparent 56 kbit/s and 64 kbit/s services only) +- TCH/F43.2 acceptable (Applicable to non-transparent services only.) +- none (note 10a) + +NOTE10a: No channel coding (defined by selecting none of the above). + +#### **Maximum number of traffic channels, MaxNumTCH (note 12)** + +This element is relevant between the MT and the IWF. + +Value: + +- 1 TCH +- 2 TCH +- 3 TCH +- 4 TCH +- 5 TCH +- 6 TCH +- 7 TCH (note 11) +- 8 TCH (note 11) + +NOTE11: Not used by currently specified services. + +#### **Other modem type, OMT (Note 12)** + +This element is relevant between the IWF and the fixed network in case of 3,1 kHz audio ex-PLMN + +Values: + +- no other modem type specified in this field +- V.34 + +### **User initiated modification indication, UIMI (Note 12)** + +This element is relevant between the MT and the IWF. + +Values: + +- user initiated modification not requested +- user initiated modification upto 1 TCH requested +- user initiated modification upto 2 TCH requested +- user initiated modification upto 3 TCH requested +- user initiated modification upto 4 TCH requested + +### **Asymmetry preference indication (note 12)** + +This element is relevant between the MT and the BSS. + +Value: + +- no preference +- up link biased asymmetry preference +- down link biased asymmetry preference + +NOTE 12:These GBS-related parameters are optional. + +For a configuration with data rates 9.6kbit/s or higher, the following applies to the parameters contained in the BC-IE: + +- Half rate channels are not supported. The MS shall code the radio channel requirement as "Full rate support only MS" or "Dual rate support MS, full rate preferred". In the second case, the network shall assign full rate channel(s) only. +- The 'fixed network user rate' and 'other modem type' takes precedence over the 'user rate' and 'modem type', unless the 'modem type' indicates "autobauding". +- The ACC indicates which channel coding is acceptable and supported by the MS. In case of CE:NT the TCH/F4.8 and TCH/F9.6 acceptable is equivalent to the support of NIRR. If TCH/F4.8 acceptable only or + +TCH/F9.6 acceptable only or TCH/F14.4 acceptable only is indicated, the assigned channel type which can be chosen by the network is TCH/F4.8 or TCH/F9.6 or TCH/F14.4, respectively. + +- The 'intermediate rate' parameter is overridden. The intermediate rate used per each TCH/F is derived from the chosen channel type: + +| channel type | IR per TCH/F | +|---------------------|------------------------------------| +| TCH/F4.8 | 8 kbit/s | +| TCH/F9.6 | 16 kbit/s | +| TCH/F14.4 | intermediate rate is to be defined | + +- The user rate per TCH is derived from the chosen channel type: + +| channel type | user rate per TCH | +|---------------------|--------------------------| +| TCH/F4.8 | 4.8 kbit/s | +| TCH/F9.6 | 9.6 kbit/s | + +For CE:T, the padding procedure described in 3GPP TS 44.021 can be applied. + +# --- Annex B (normative): Setting of Bearer Capability, Low Layer Compatibility and High Layer Compatibility Information Element for PLMN Bearer Services and PLMN TeleServices + +## B.0 Scope + +This annex describes the relationship between the various parameters of the PLMN Bearer Capability Information Element (BC-IE), their validity and the possible settings with reference to each PLMN Bearer service/Teleservice defined in 3GPP TS 22.002 and 3GPP TS 22.003 and various occurrences during the connection control (clause B.1). Furthermore, the contents of the Low Layer (LLC) and the High Layer (HLC) Compatibility Information Elements are described (clause B.2). + +## --- B.1 Bearer Capability Information Element + +### B.1.1 Introduction + +#### B.1.1.1 General Consideration + +In general, the purpose of the Bearer Capability Information Element (BC-IE) is to request a particular bearer service to be provided by the network. This indication is carried by certain connection control messages which for the subject matter of the present document may be categorized into those messages: + +- related to the call set-up phase; and +- those used during the established connection. + +During the call set-up phase the PLMN BC-IE (single or multiple) is included in: + +- the SETUP message generated by the requesting entity (either MS or MSC) to establish a mobile-originated or mobile-terminated call, respectively, and in + - the CALL CONFIRMED or CALL PROCEEDING messages, respectively, generated by the responding entity (either MS or MSC) in order to negotiate certain parameter values. If no BC-IE is contained in the SETUP message (a mobile terminated call with the single-numbering scheme) the CALL CONFIRMED message indicates the complete applicable BC-IE. The network may release the call if it does not support the service indicated by the BC-IE. Also, if the service does not match with the service requested from the fixed network terminal the MSC/IWF may release the call. + +NOTE: In the latter case also the fixed network terminal may release the call. + +During the established connection the PLMN BC-IE is included in the MODIFY, MODIFY COMPLETE, and MODIFY REJECT messages in order to change the service (bearer capability) or to change the maximum number of traffic channels and/or wanted air interface user rate when a non-transparent multislot data service is in use. + +If the maximum number of traffic channels and/or wanted air interface user rate is to be changed, the BC-IE included in the MODIFY message shall not indicate a different bearer service than the one used at this stage of the connection - the values of the parameters 'maximum number of traffic channels' and/or 'wanted air interface user rate' may be changed, only. + +The subsequent tables and subclauses of clause B.1 deal with the representation of the individual contents of the PLMN BC-IE during the call set-up phase. For the use during the established connection refer to 3GPP TS 24.008. + +With respect to the individual parameter settings at the MS the following cases may be distinguished (see 3GPP TS 27.002 and 3GPP TS 27.003): + +- Mobile-originated call set up by a MS: + +- The setting results from respective MMI actions and/or MT internal settings. +- Mobile-terminated call set up to a MS: + - The BC related part of the compatibility check is carried out according to the knowledge of the MT concerning its implemented functions (i.e. answering the call). The requested field values of the non-negotiable parameters and the selected field values of the negotiable parameters determine the selection of the terminal function to be used for the intended connection. + +#### B.1.1.2 Interpretation of the Diagrams + +The purpose of the subsequent diagrams is to achieve unambiguous representation of the individual contents of the PLMN BC-IE for the various occurrences during the call set-up phase, covering all bearer services and teleservices according to 3GPP TS 22.002 and 3GPP TS 22.003. + +The basic principle adopted is a graphic scheme, or mask, wherein the ordinate designates the individual parameters of the PLMN BC-IE and the abscissa gives the possible field values of these parameters. The abbreviations used in these sections are defined in table B.5. The allowed content of any PLMN BC-IE is represented by a number of graphs connecting parameter values (abscissa points) of all parameters (ordinate points). Each graphic scheme is subdivided into two independent parts: + +- "Layer/Protocol related" part; and +- "Radio Channel related" part. + +The generation of all PLMN BC-IEs in all call set-up messages shall be in accordance with these graphs. + +Subclauses B.1.2 through B.1.11 show individual sets of graphs for each service group (BS/TS) and for each type of applicable Information Transfer Capability. + +In addition, the following rules apply: + +- Those parameters which have only one possible field value for all recognized services are shown in table B.5, where they are marked accordingly in the column "common setting of field values". They are not represented in the graphic scheme. +- Not all parameters of the PLMN BC-IE are relevant for each service (BS/TS). This is represented by specific abscissa points with a value of "NA" (Not Applicable) allocated to these parameters. The graphs pass through these points for each such parameter. The actual field value to be used in the PLMN BC-IE is marked in the column "default setting of field values (NA)" of table B.5. An abscissa point with a value of "NAV" (Not Available) indicates that the entire octet carrying this parameter (see table B.2 "General Structure of the PLMN BC-Information Element") shall be omitted. +- Unless FTM is applied, there is a particular dependency of the parameters "User Information Layer 2 Protocol (UIL2P)" and "Connection Element (CE)": + - If the MS sends a PLMN BC-IE with a CE value other than "Transparent (T)", the parameter UIL2P is essential. Its field value must be set as indicated in the applicable graph. + - If the MSC sends a PLMN BC-IE in the SETUP message, the parameter UIL2P may also be absent in the case of the CE parameter value being other than "Transparent (T)". +- In case FTM is applied, the PLMN BC-IE shows a CE value "non-transparent", SA value "asynchronous", and RA value X.31 flag stuffing. The UIL2P is not available. +- Certain parameters of the PLMN BC-IE may be negotiated during the connection establishment phase. Table B.1 shows these parameters and the relations of their values in the SETUP message and in the CALL CONFIRMED/CALL PROCEEDING message, respectively, both for the mobile-originated and mobile-terminated case. A parameter may indicate a field value of one of the following types: + - "requested value" indicating a request which cannot be changed by the responding entity; + - "offered value" indicating a proposal which may be changed by the responding entity; + - a particular choice value leaving it up to the responding entity which value ultimately applies; + - "as requested" indicating that the requested value applies and is confirmed (by returning it); + +- "selected value" indicating that a particular value applies either out of the offered set or as a free choice out of the defined set of values; +- "supported value" indicating a value supported by the responding entity. + +**Table B.1: BC-Parameters subject to negotiation procedure** + +Mobile Originated Call: + +| BC-parameter | Message | | +|--------------|---------------------------------------------------------------------------------------|---------------------------------------| +| | SETUP | CALL PROC | +| NDB | Requested value | as requested | +| NPB | Requested value | as requested | +| NSB | Requested value | as requested | +| CE | Requested value (T/NT)
"both" with the preferred value indicated
(e.g. both NT) | as requested
selected value (T/NT) | +| UIL2P | Requested value 9) or NAV 1) | as requested or NAV 4) | +| User Rate | Requested value | as requested | +| DC | Requested value 2) | as requested or "NO" 7) | +| FNUR | Requested value | supported value | +| Other MT | Requested value | supported value | +| UIMI | Requested value | supported value | + +Mobile Terminated Call: + +| BC-parameter | Message | | +|---------------------------------------|----------------------------------------------------------|-------------------------------------------------------------------| +| | SETUP | CALL CONF | +| NDB | Offered value | selected value (free choice) | +| NPB | offered value | selected value (free choice) | +| NSB | offered value | selected value (free choice) | +| CE | requested value (T/NT) | as requested or selected value (T/NT) (free choice) 3) | +| | "both" with the preferred value indicated (e.g. both NT) | selected value (T/NT) | +| Sync/Asynchronous | requested value | as requested or selected value 10) | +| Rate adaptation/Other rate adaptation | requested value | as requested or selected value 11) | +| UIL2P | offered value 2) or NAV 4) | selected or NAV 1) | +| User Rate | offered value | selected value 5) | +| DC | requested value 2) | as requested or "NO" 7) | +| FNUR | offered value | selected value 6) | +| Other MT | offered value | selected value 6) | +| UIMI | offered value | selected value 8) | + +- 1) For CE:T only, out-band flow control, or RA:X.31 flag stuffing requested by the MS. +- 2) Not for CE:T. +- 3) When the SETUP message contains no BC-IE (single numbering scheme). +- 4) "NAV" shall not be interpreted as an out-band flow control request by the MS. +- 5) The modification of User Rate shall be in conjunction with Modem Type and Intermediate Rate. +- 6) The modification of the Fixed Network User Rate shall be in conjunction with the Modem Type and/or Other Modem Type. +- 7) In case of a Mobile Terminated Call, if the SETUP message does not contain a BC-IE, the MS shall behave as if the DC is set to "data compression not possible". +If a sending entity, based on an earlier version of the protocol, sends a SETUP message containing "DC.. compression possible/ allowed" instead of the default value "NO.. compression not possible/allowed" as defined in Table B.5 then the receiving MS or the receiving network may ignore the DC value and may return either "NO.. compression not possible/allowed" or "DC.. compression possible/allowed" in the CALL CONF/CALL PROC message. +In case of a MO CALL or a MT CALL where no BC-IE is included in the CALL PROCEEDING or CALL CONFIRMED message, respectively, the MS or the network shall behave as if the DC was set to "data compression not possible" or "data compression not allowed", respectively. +- 8) Less or equal to the offered value. +- 9) Not for CT:T or FTM (i.e., CE:NT, SA:A, RA:X.31 flag stuffing). +- 10) For FTM and PIAFS, this parameter may be negotiated. See Table B.4e for details. +- 11) For FTM, PIAFS and Multimedia, this parameter may be negotiated. See Table B.4f for details. + +**Table B.2: General Structure of the BC-Information Element** + +| OCTET | INFORMATION ELEMENT FIELD | +|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3 | Radio channel requirements
Coding standard
Transfer mode
Information Transfer Capability | +| 4 | Structure 2)
Duplex mode
Configuration
Establishment
Negotiation of Intermediate Rate Requested
Compression | +| 5 | Rate adaption 2)
Signalling access protocol | +| 5a | Other ITC 2) 7)
Other rate adaption | +| 5b | Rate adaption header / no header 2) 3)
Multiple frame establishment support in data link
Mode of operation
Logical link identifier negotiation
Assignor / assignee
In-band / out-band negotiation | +| 6 | User information layer 1 protocol 2)
Synchronous / asynchronous | +| 6a | Number of stop bits 2)
Negotiation
Number of data bits
User rate | +| 6b | Intermediate rate 2)
NIC on transmission
NIC on reception
Parity information | +| 6c | Connection element 2)
Modem type | +| 6d | Fixed network user rate 4)
Other modem type | +| 6e | Maximum number of traffic channels 4)
Acceptable channel codings | +| 6f | Wanted air interface user rate 4)
User initiated modification indication | +| 6g | Acceptable Channel codings 5)
Asymmetry preference indication 6) | +| 7 | User information layer 2 protocol 1) 2) | +| 1) | Octets optional. | +| 2) | Octets only available if the parameter "Information Transfer Capability" does not indicate "Speech". | +| 3) | For ITU-T V.120 rate adaption only. | +| 4) | Optional octets available only if the parameter "Information Transfer Capability" does not indicate "Speech". | +| 5) | Extension of the 'Acceptable channel codings' field in octet 6e in case EDGE channel codings are supported. | +| 6) | Only used if EDGE channels are among the 'Acceptable channel codings'. The value shall be set to 'no preference' in case the connection element is T. | +| 7) | For ITC=RDI or UIL1P=V.120, PIAFS, and 'H.223 and H.245' only. | + +**Table B.3a: Selection of flow control method (for CE:NT with SA:A only)** + +| information element | flow control method | | | +|-----------------------------------|---------------------|--------------|---------------| +| | in-band | out-band (3) | none | +| number of data bits | 7 or 8 | 7 or 8 | 7 or 8 | +| user information layer 2 protocol | ISO 6429 (1) | NAV | COPnoFICt (2) | + +1) ISO6429 stands for "ISO 6429, codeset 0, DC1/DC3" and is applicable for 7 and 8 bit codes. + +2) COPnoFICt stands for a character oriented protocol with no flow control mechanism (no reserved characters for flow control). + +3) "out-band" flow control requires ITU-T V.42 in case of PSTN or ITU-T V.110 in case of ISDN. +If the ITU-T V.110 flow control mechanism is not supported, where required, the call pending shall be terminated. +If the ITU-T V.42 functionality is not supported by the modem in the IWF or in the fixed network, the call shall be supported with a fallback to the non- ITU-T V.42 mode. In this case the IWF shall release the call if due to temporary throughput problems on the radio interface or initiation of flow control by the MS and the inability to flow control the fixed network modem an overflow of the L2R buffers occurs. +Note that a phase 1 network may release the call, if the ITU-T V.42 functionality is not provided by the IWF or the fixed network modem. As ITU-T V.42 does not apply to ITU-T V.21 modems, outband flow control can not be supported for these modem types. + +**Table B.4a: Modem Type subject to negotiation procedure** + +Mobile Originated Call: + +| BC-parameter CE | BC-parameter MT and OMT 6) | | +|--------------------|----------------------------|----------------------------------------| +| | Message SETUP | Message CALL PROC | +| T | V-series | V-series | +| NT | V-series | V-series | +| | autobauding type 1 | autobauding type 1 or
V-series 1) | +| bothT or
bothNT | V-series | V-series | +| | autobauding type 1 | autobauding type 1 or
V-series 1)2) | + +Mobile Terminated Call: + +| BC-parameter CE | BC-parameter MT and OMT 6) | | +|--------------------|----------------------------|----------------------------------------------| +| | Message SETUP | Message CALL CONF | +| T | V-series | V-series | +| NT | V-series | V-series or autobauding type 1 3) | +| | autobauding type 1 | autobauding type 1 or
V-series 4) | +| bothT or
bothNT | V-series | V-series | +| | autobauding type 1 | autobauding type 1 or
V-series 4)5) | + +- 1) No autobauding capability in the IWF:MSC. +- 2) CE:T selected by IWF/MSC. +- 3) Free choice if the SETUP contains no BC-IE (single numbering scheme). +If the IWF/MSC has no autobauding capability, a V-series modem type is used. +- 4) When the MS does not allow the use of autobauding capability. +- 5) CE:T selected by the MS. +- 6) When the MT indicates "autobauding" , "modem for undefined interface" or "none", the OMT shall be set to "no other modem type". Any other values of the MT is overridden by the OMT value. + +**Table B.4b: Intermediate Rate negotiation procedure** + +If the user rate is 9.6 kbit/s the intermediate rate negotiation procedure is not applicable and NIRR shall be set to "No meaning". + +Recipient of SETUP supports full rate, non transparent, 6 kbit/s radio interface rate and the user rate is up to/equal 4,8 kbit/s: + +| BC-parameter | Message SETUP | Message CALL CONF or CALL PROC | +|--------------|------------------------|--------------------------------| +| NIRR | 6 kbit/s | 6 kbit/s | +| IR | 16 kbit/s | 8 kbit/s | +| User Rate | up to/equal 4,8 kbit/s | as requested | + +NOTE 1: In case of a Mobile Terminated Call, if the SETUP message does not contain a BC-IE, the MS shall behave as if NIRR set to "No meaning". + +In case of a MO CALL or a MT CALL where no BC-IE is included in the CALL PROCEEDING or CALL CONFIRMED message, respectively, the MS or the network shall behave as if the NIRR was set to "No meaning". + +Recipient of SETUP does support full rate, non transparent, but not in connection with 6 kbit/s radio interface rate: + +| BC-parameter | Message SETUP | Message CALL CONF or CALL PROC | +|--------------|------------------------|--------------------------------| +| NIRR | 6 kbit/s | No meaning | +| IR | 16 kbit/s | 16 kbit/s | +| User Rate | up to/equal 4,8 kbit/s | as requested | + +NOTE 2: If no other parameter needs negotiation, the CALL CONF/PROC message need not contain any BC-IE. + +In case of a MO CALL or a MT CALL where no BC-IE is included in the CALL PROCEEDING or CALL CONFIRMED message, respectively, the MS or the network shall behave as if the NIRR was set to "No meaning". + +NOTE 3: In case a GBS-operation is requested and acknowledged, the MS indicates the acceptable channel codings. The indicated acceptance of TCH/F4.8 is equivalent to the support of 6 kbit/s radio interface rate per TCH/F and therefore overrides the NIRR parameter. + +**Table B.4c Negotiation of fixed network user rate** + +| BC-parameter | Message SETUP | Message CALL PROC/CONFIRMED | +|--------------|-----------------|-----------------------------------------| +| FNUR | requested value | equal or lower than the requested value | + +The network might accept the modified value or reject the call. + +**Table B.4d Negotiation of user initiated modification indication** + +| BC-parameter | Message SETUP | Message CALL PROC/CONFIRMED | +|--------------|---------------|--------------------------------------------------------------------------------------------------------------| +| UIMI | offered value | equal to or a value indicating a request for modification to a lower number of traffic channels than offered | + +**Table B.4e: Negotiation of Synchronous/Asynchronous** + +Mobile Terminated Call: + +| | BC-parameter Synchronous/Asynchronous | | +|---------------------|---------------------------------------|-------------------| +| Bearer type | Message SETUP | Message CALL CONF | +| FTM 1) | Synchronous | Asynchronous | +| PIAFS 2) | Synchronous | Asynchronous | + +- 1) This negotiation is possible, only if ITC=UDI or RDI, FNUR=64 or 56 kbit/s and CE=NT or "both" is signalled in the SETUP message. The MS shall signal FTM as specified in B.1.2.3 . +- 2) This negotiation is possible, only if ITC=UDI, FNUR=32 kbit/s and CE= "both" is signalled in the SETUP message. The UE shall signal PIAFS as specified in B.1.2.4 + +**Table B.4f: Negotiation of Rate adaptation/Other rate adaptation** + +Mobile Terminated Call: + +| | BC-parameter Rate adaptation/Other rate adaptation | | +|---------------------|----------------------------------------------------|--------------------| +| Bearer type | Message SETUP | Message CALL CONF | +| FTM 1) | V.110, I.460 and X.30 | X.31 flag stuffing | +| PIAFS 2) | V.110, I.460 and X.30 | PIAFS | +| Multimedia | V.110, I.460 and X.30 3) | H.223 and H.245 | +| | No rate adaptation 5) 6) | H.223 and H.245 | + +- 1) This negotiation is possible, only if ITC=UDI or RDI, FNUR=64 or 56 kbit/s and CE=NT or "both" is signalled in the SETUP message. The MS shall signal FTM as specified in B.1.2.3. +- 2) This negotiation is possible, only if ITC=UDI, FNUR=32 kbit/s and CE= "both" is signalled in the SETUP message. The UE shall signal PIAFS as specified in B.1.2.4. + +- 3) This negotiation is possible, only if ITC=UDI or RDI, FNUR=32 or 56 kbit/s and CE=T or "both" is signalled in the SETUP message. The MS shall signal 3G-H.324/M as specified in B.1.3.1.3, B.1.3.1.4 and B.1.3.1.6. +- 4) Void. +- 5) This negotiation is possible, if ITC=3,1 kHz, FNUR=28.8 kbit/s, MT=V.34 and CE=T or "both" is signalled in the SETUP message. The MS shall signal 3G-H.324/M as specified in B.1.3.2.3. +- 6) This negotiation is possible, if ITC=UDI or RDI, FNUR=64 or 56 kbit/s and CE=T is signalled in the SETUP message. The MS shall signal 3G-H.324/M as specified in B.1.3.1.3, B.1.3.1.4, and B.1.3.1.5 + +**Table B.5: BC parameter setting (part 1)** + +| Abbreviations for Parameters and Values: | common setting of field values | | +|--------------------------------------------------------|--------------------------------------|---| +| | default setting of field values (NA) | | +| ITC...Information Transfer Capability: | | | +| - Speech | | | +| - UDI..Unrestricted Digital | | | +| - FAX3..Group 3 Facsimile | | | +| - 3,1 kHz..3,1 kHz Ex PLMN | | | +| - RDI..Restricted Digital | | | +| TM....Transfer Mode: | | | +| - ci..Circuit | X | X | +| S.....Structure: | | | +| - SDU..Service Data Unit Integrity | | | +| - Unstructured | X | | +| C.....Configuration: | | | +| - pp..Point to point | X | X | +| E.....Establishment: | | | +| - de..Demand | X | X | +| SA....Sync/Async: | | | +| - S..Synchronous | | | +| - A..Asynchronous | | | +| N.....Negotiation | | | +| - ibn..in band negotiation not possible | X | X | +| UR....User Rate: | | | +| - 0.3..0.3 kbit/s | | | +| - 1.2..1.2 kbit/s | | | +| - 2.4..2.4 kbit/s | | | +| - 4.8..4.8 kbit/s | | | +| - 9.6..9.6 kbit/s | X | | +| IR....Intermediate Rate: | | | +| - 8.. 8 kbit/s | | | +| - 16.. 16 kbit/s | X | | +| NICT..Network Independent Clock on Tx: | | | +| - not_required.. Not required | X | X | +| - required | | | +| NICR..Network Independent Clock on Rx: | | | +| - not_accepted..not accepted | X | X | +| - accepted | | | +| NSB...Number of Stop Bits: | | | +| - 1..1 bit | X | | +| - 2..2 bit | | | +| NDB...Number of Data Bits Excluding Parity If Present: | | | +| - 7.. 7 bit | | | +| - 8.. 8 bit | X | | +| NPB...Parity Information: | | | +| - Odd | | | +| - Even | | | +| - None | X | | +| - 0.. Forced to 0 | | | +| - 1.. Forced to 1 | | | +| UIL1P.User Information Layer 1 Protocol | | | +| - def..default layer 1 protocol | X | X | + +**Table B.5: BC parameter setting (part 2)** + +| Abbreviations for Parameters and Values | | common setting of field values | | +|------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|---| +| | | default setting of field values (NA) | | +| | | v | v | +| DM....Duplex Mode: | -
- fd.. Full Duplex | X | X | +| MT....Modem Type: | - V.21
- V.22
- V.22 bis
- V.26 ter
- V.32
- autol.. autobauding type 1
- none | X | | +| RCR...Radio Channel Requirement: | - FR Full Rate support only Mobile Station
- dual HR Dual Rate support Mobile Station/
Half Rate preferred
- dual FR Dual Rate support Mobile Station/
Full Rate preferred | | | +| CE....Connection Element: | - T.. Transparent
- NT.. Non Transparent
- bothT both transparent preferred
- bothNT both non Transparent preferred | | | +| UIL2P.User Information Layer 2
Protocol: | - ISO6429..ISO6429,codeset 0,DC1/DC3

- COPnoFlCt..Character oriented protocol with
no flow control mechanism | | | +| SAP...Signalling Access Protocol: | - I.440.. I.440/450 | X | | +| RA....Rate Adaptation: | - V.110.. V.110/X.30
- X.31Flag.. X.31 flagstuffing
- NO.. no rate adaptation
- V.120
- PIAFS
- H.223 and H.245 | X | | +| CS....Coding Standard: | - GSM | X | X | +| NIRR..Negotiation of Intermediate
Rate Requested: | NM..No Meaning associated with this value
6kbit/s..6kbit/s radio interface rate requested | X | | +| DC....Data Compression | - DC.. compression possible/allowed
- NO.. compression not possible/allowed | X | | + +**Table B.5: BC parameter setting (part 3)** + +| Abbreviations for Parameters and Values | | common setting of field values | | +|------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|--| +| | | default setting of field values (NA) | | +| FNUR...Fixed Network User Rate |
  • - FNUR not applicable
  • - 9.6.. 9.6 kbit/s
  • - 14.4.. 14.4 kbit/s
  • - 19.2.. 19.2 kbit/s
  • - 28.8.. 28.8 kbit/s
  • - 32.0.. 32.0 kbit/s
  • - 33.6.. 33.6 kbit/s
  • - 38.4.. 38.4 kbit/s
  • - 48.0.. 48.0 kbit/s
  • - 56.0.. 56.0 kbit/s
  • - 64.0.. 64.0 kbit/s
| | | +| WAIUR...Wanted Air Interface User Rate |
  • - WAIUR not applicable
  • - 9.6.. 9.6 kbit/s
  • - 14.4.. 14.4 kbit/s
  • - 19.2.. 19.2 kbit/s
  • - 28.8.. 28.8 kbit/s
  • - 38.4.. 38.4 kbit/s
  • - 43.2.. 43.2 kbit/s
  • - 57.6.. 57.6 kbit/s
  • - int 38.4.. interpreted by the network as 38.4 kbit/s
| X | | +| ACC.....Acceptable channel codings |
  • - 4.8.. TCH/F4.8 acceptable
  • - 9.6.. TCH/F9.6 acceptable
  • - 14.4..TCH/F14.4 acceptable
  • - 28.8..TCH/F28.8 acceptable
  • - 32.0..TCH/F32.0 acceptable
  • - 43.2..TCH/F43.2 acceptable
  • - none..No channel coding (defined by selecting none of the above)
| | | +| MaxNumTCH...Maximum Number of Traffic Channels |
  • - 1.. 1 TCH
  • - 2.. 2 TCH
  • - 3.. 3 TCH
  • - 4.. 4 TCH
  • - 5.. 5 TCH
  • - 6.. 6 TCH
  • - 7.. 7 TCH
  • - 8.. 8 TCH
| | | +| OMT...Other modem type |
  • - no other MT.. no other modem type
  • - V.34.. V.34
| | | +| User initiated modification indication |
  • - not req.. user initiated modification not required
  • - upto 1 TCH.. user initiated modification upto 1 TCH may be requested
  • - upto 2 TCH.. user initiated modification upto 2 TCH may be requested
  • - upto 3 TCH.. user initiated modification upto 3 TCH may be requested
  • - upto 4 TCH.. user initiated modification upto 4 TCH may be requested
| X | | +| Asymmetry preference indication |
  • - 00 no preference
  • - 01 up link biased asymmetry preferred
  • - 10 down link biased asymmetry preferred
| | | + +**Table B.5a: Differences in parameter value validity in A/Gb mode and UTRAN Iu mode** + +| Parameter / value | A/Gb mode | GERAN Iu mode | UTRAN Iu mode | +|-----------------------------------------------------|---------------------|-----------------------------------------|-----------------------------------------| +| Radio Channel Requirements / any | valid | valid | ignored | +| User rate / any | valid | ignored | ignored | +| Intermediate Rate / any | valid | valid | ignored | +| NIC on transmission / any | valid | ignored | ignored | +| NIC on reception / any | valid | ignored | ignored | +| Negotiation of IR requested / any | valid | ignored | ignored | +| Acceptable Channel Codings / any | valid (note 2) | valid (note 2) | ignored | +| Maximum number of traffic channels / any | valid (note 2) | valid (note 2) | ignored (Note 1) | +| User initiated modification indication / any | valid | valid | ignored (Note 1) | +| Asymmetry preference indication/ any | valid | valid | ignored | +| Modem type / | | | | +| V.21, V.22, V.22bis, V.26ter | valid | invalid | invalid | +| V.32 | valid | valid | invalid for CE=T | +| Fixed Network User Rate / | | | | +| 32 kbit/s | Invalid for CE = NT | Invalid for CE = NT | valid | +| 33.6 kbit/s | invalid | invalid | valid | +| 9.6, 14.4, 19.2, 38.4, 48.0 | valid | invalid for CE=T | invalid for CE=T | +| 28.8 | valid | invalid for CE=T in the case of ITC=UDI | invalid for CE=T in the case of ITC=UDI | +| Other Rate adaptation / | | | | +| PIAFS | invalid | invalid | valid | + +NOTE: Although a parameter value is marked as "valid", the validity may be restricted by rules given elsewhere in the present document. + +NOTE 1: This parameter is relevant in UTRAN Iu mode for NT calls, in conjunction with WAIUR, for deciding which RLP version to negotiate in order to avoid renegotiation of RLP version in case of handover, see 3GPP TS 24.022 [9]. It is otherwise irrelevant for specifying the UTRAN Iu mode radio access bearer. + +NOTE 2: The MS can indicate that the requested service is not supported in A/Gb or GERAN Iu mode by setting all Acceptable Channel Codings to "none" (all zeros) and the Maximum Number of Traffic Channels parameter to the value "one TCH" (zero). The network will interpret these values as an indication that a handover to another mode (e.g. UTRAN Iu mode) is needed before the call setup can proceed. Similarly, while in another mode, the MS can inform the network that the MS does not support the requested service in A/Gb or GERAN Iu mode. + +**Table B.6: Channel combinations** + +Single Bearer and Teleservices + +| MS indication
BC | Network selection CT
CT | +|---------------------|----------------------------| +| FR | FR | +| dual FR | FR or HR | +| dual HR | HR or FR | + +Alternate services + +| MS indication | | Network selection | | | | | +|---------------|-----------|-------------------|-------|----|-------|-------| +| BC(1) | BC(2) | CT(1) | CT(2) | Or | CT(1) | CT(2) | +| FR | FR | FR | FR | | | | +| FR | dual Rate | FR | FR | | | | +| dual Rate | dual Rate | FR | FR | Or | HR | HR | +| dual Rate | FR | FR | FR | | | | + +Followed-by services + +| MS indication | | Network selection | | | | | | | | +|---------------|-----------|-------------------|-------|----|-------|-------|----|-------|-------| +| BC(1) | BC(2) | CT(1) | CT(2) | or | CT(1) | CT(2) | or | CT(1) | CT(2) | +| FR | FR | FR | FR | | | | | | | +| FR | dual Rate | FR | FR | | | | | | | +| dual Rate | dual Rate | FR | FR | or | HR | HR | or | FR | HR | +| dual Rate | FR | FR | FR | | | | | | | + +BC Bearer Capability + +CT Channel Type + +dual Rate {dual FR | dual HR} + +**Table B.7: TS61/TS62 Negotiation rules** + +Mobile Originating Call + +| Subscription | SETUP | CALL PROCEED | +|--------------|----------|------------------| +| TS61 | TS61 s/f | TS61 s/f or TS62 | +| | TS61 f/s | TS61 f/s or TS62 | +| | TS62 | TS62 | +| TS62 | TS61 s/f | TS62 | +| | TS61 f/s | TS62 | +| | TS62 | TS62 | + +Mobile Terminating Call + +| Subscription | SETUP | CALL CONFIRMED | +|--------------|----------|------------------------------| +| TS61 | TS61 s/f | TS61 s/f or TS61 f/s or TS62 | +| | TS61 f/s | TS61 s/f or TS61 f/s or TS62 | +| | TS62 | TS62 | +| | no BC | TS61 s/f or TS61 f/s or TS62 | +| TS62 | TS62 | TS62 | +| | no BC | TS62 (note) | + +s/f = speech then fax + +f/s = fax then speech + +NOTE: TS61 is also accepted if the VMSC supports TS61 and does not perform subscription checking on a CALL CONFIRMED message (see 3GPP TS 22.001 and 3GPP TS 29.007). + +### B.1.2 Bearer Service 20, Data Circuit Duplex Asynchronous + +#### B.1.2.1 Unrestricted / restricted digital information transfer capability + +| | | | | | | | | | | | | +|------------------------|--------------|-------------|----------|---------------------|------------------|-------------------------|-------------------|-----------|--------------------|----|-----| +| ITC | Oct.
3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +| Layer/protocol related | | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 7) | V.110 | H.223 & H.245 | X.31 Flag | No | | | | +| SA | 6 | | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlct 5) | NAV 4) | | | | | +| DC | 4 | NA | | | DC 1) | | NO 1) | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| Radio channel related | | | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| UR 8) | 6a | NA | | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | +| IR 8) | 6b | NA | | 8 | | 16 | | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR | 6d | | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | 48 | NAV | +| ACC 9) | 6e | none | | 4.8 | | 9.6 | | 14.4 | | | NAV | +| MaxNumTCH | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | NAV | +| WAIUR 1) | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI 1) | 6f | NA | not req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV | +| ACC ext. 9) | 6g | | | | | 28.8 | 32.0 | | 43.2 1) | | NAV | +| ASYM 1) | 6g | no. pref. | | | | u1 biased | | d1 biased | | | NAV | + +1) for CE:NT or "both"; + +2) for CE:T only or CE:NT and NIRR:6kb/s (not for the SETUP message); + +3) Void; + +4) for MT CALLS in the SETUP message or MO/MT CALLS with "out-band" flow control requested; + +5) for MO/MT CALLS with no flow control requested; + +6) Void; + +- 7) the V.120 relevant BC parameters (octet 5b) shall be set according to the LLC (see clause B.2); +- 8) IR and UR are overridden by FNUR, ACC and MaxNumTCH; +- 9) ACC may have several values simultaneously (bit map coding). + +#### B.1.2.2 3,1 kHz audio ex-PLMN information transfer capability + +| Oct. | 3/5a | UDI | 3.1 kHz | FAX3 | Speech | RDI | | | | | +|------------------------|------|-------------|----------|------------------|-------------------------|-------------------|-----------|-----------|--------------------|-----| +| Layer/protocol related | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | +| SA | 6 | | | A | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | +| S | 4 | NA | | SDU | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | COPnoFlct 5) | NAV 4) | | | | | +| DC | 4 | NA | | DC 1) | | NO 1) | | | | | +| NDB | 6a | NA | | 7 | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | +| Radio channel related | | | | | | | | | | | +| RCR | 3 | dualHR | | dualFR | | FR | | | | | +| UR 7) | 6a | NA | | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | +| IR 7) | 6b | NA | | 8 2) | | 16 | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | auto 1 | | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | NAV | +| FNUR 9) | 6d | | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | NAV | +| ACC 8) | 6e | none | | 4.8 | | 9.6 | | 14.4 | | NAV | +| MaxNumTCH | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | NAV | +| WAIUR 1) | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | NAV | +| UIMI 1) | 6f | NA | not.req. | upto 1 | upto 2 | | upto 3 | | upto 4 | NAV | +| ACC ext. 8) | 6g | | | | | 28.8 | 32.0 | | 43.2 1) | NAV | +| ASYM 1) | 6g | no. pref. | | | | u1 biased | | d1 biased | | NAV | + +1) for CE:NT or "both"; + +2) for CE:T only or CE:NT and NIRR:6kb/s (not for the SETUP message); + +3) Void; + +4) for MT CALLS in the SETUP message or MO/MT CALLS with "out-band" flow control requested (not for V.21 modem type); + +- 5) for MO/MT CALLS with no flow control requested; +- 6) Void; +- 7) IR and UR are overridden by FNUR, ACC and MaxNumTCH. +- 8) ACC may have several values simultaneously (bit map coding). +- 9) in case of MT = auto1 the value of FNUR has no meaning. + +#### B.1.2.3 Frame Tunnelling Mode + +| | | | | | | | | | | | | +|------------------------|--------------|------------------------|----------|---------|---------|---------------|--------------|-----------|--------|----|-----| +| ITC | Oct.
3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +| | | Layer/protocol related | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | | +| SA | 6 | | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlct | NAV | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| | | Radio channel related | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| UR | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | | +| IR | 6b | NA | 8 | | | 16 | | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR | 6d | | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | 48 | NAV | +| ACC 1) | 6e | none | | 4.8 | | 9.6 | | | 14.4 | | NAV | +| MaxNumTCH | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | NAV | +| WAIUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI | 6f | NA | not req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV | +| ACC ext. 1) | 6g | | | | | 28.8 | 32.0 | | 43.2 | | NAV | +| ASYM | 6g | no. pref. | | | | ul biased | | dl biased | | | NAV | + +1) ACC may have several values simultaneously (bit map coding). + +#### B.1.2.4 PIAFS + +| | | | | | | | | | | | | +|-----------|------|------------------------|-----------|---------|---------|---------------|--------------|-----------|--------|----|--------| +| | Oct. | | | | | | | | | | | +| ITC | 3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +| | | Layer/protocol related | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | | +| SA | 6 | | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlet | NAV | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| | | Radio channel related | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| UR | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | | +| IR | 6b | NA | 8 | | | 16 | | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR | 6d | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | 48 | 56 | 64 NAV | +| ACC | 6e | none | | 4.8 | | 9.6 | | 14.4 | | | NAV | +| MaxNumTCH | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | NAV | +| WAIUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV | +| ACC ext. | 6g | | | | | 28.8 | 32.0 | | 43.2 | | NAV | +| ASYM | 6g | no. pref. | | | | u1 biased | | d1 biased | | | NAV | + +### B.1.3 Bearer Service 30, Data Circuit Duplex Synchronous + +#### B.1.3.1 Unrestricted/restricted digital information transfer capability + +##### B.1.3.1.1 Transparent FNUR <= 48 kbit/s (TCH/F4.8, TCH/F9.6, TCH/14.4, TCH/F28.8) + +Applies to A/Gb mode only. No HO to/from UTRAN Iu mode. + +| ITC | Oct.
3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +|--------------------------|--------------|-------------|-----------|---------|---------|---------------|--------------|-----------|--------|---------|-----------| +| Layer/protocol related | | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | | +| SA | 6 | | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlet | NAV | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| Radio channel related | | | | | | | | | | | | +| RCR | 3 | dualHR | | | | dualFR | FR | | | | | +| UR 1) | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | | +| IR 1) | 6b | NA | 8 | | | 16 | | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR 1) | 6d | | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | 48 | 56 64 NAV | +| ACC 1,2) | 6e | none | | 4.8 | | 9.6 | | | 14.4 | | NAV | +| MaxNumTCH 1) | 6e | | | 1 | 2 | 3 | 4 | 5 | 6 | 7 8 NAV | | +| WAIUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV | +| ACC ext. 1,2) | 6g | | | | | 28.8 | 32.0 | | 43.2 | | NAV | +| ASYM 1) | 6g | no. pref. | | | | u1 biased | | d1 biased | | | NAV | + +1) IR and UR are overridden by FNUR, ACC and MaxNumTCH. + +2) ACC may have several values simultaneously (bit map coding). + +##### B.1.3.1.2 X.32 Case + +Void. + +##### **B.1.3.1.3 Transparent FNUR=56 kbit/s, including 3G-H.324/M, (TCH/F9.6, TCH/F32.0, UTRAN Iu mode)** + +| | | | | | | | | | | | | | +|-----------------------------|------|------------------------|-----------|---------|---------------------|-----------------------------|--------------|--------------------|--------|----|----|-------------------| +| | Oct. | | | | | | | | | | | | +| ITC | 3/5a | UDI 3) | 3.1 kHz | | FAX3 | Speech | | | | | | RDI 3) | +| | | Layer/protocol related | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | | +| RA 3) | 5/5a | NA | PIAFS | V.120 | V.110 3) | H.223 & H.245 3) | X.31 Flag | No 3) | | | | | +| SA | 6 | | | A | | S | | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlct | NAV | | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | | +| | | Radio channel related | | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | | +| UR 1) | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | | | +| IR 1) | 6b | NA | 8 | | | 16 | | | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | | NAV | +| OMT 5) | 6d | no other MT | | | | V.34 | | | | | | NAV | +| FNUR 1,5) | 6d | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | 48 | 56 | 64 | NAV | +| ACC 1,2,4,6) | 6e | none | | 4.8 | | 9.6 | | | 14.4 | | | NAV | +| MaxNumTCH 1,4,6) | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | | NAV | +| WAIUR 1) | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 1) | 57.6 | | | NAV | +| UIMI 1,4) | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | | NAV | +| ACC ext. 1,2,4) | 6g | | | | | 28.8 | 32.0 | | 43.2 | | | NAV | + +- 1) IR and UR are overridden by FNUR, ACC and MaxNumTCH. IR and UR are not applicable to UTRAN Iu mode. +- 2) ACC may have several values simultaneously (bit map coding). However, handover to/from UTRAN is not possible if the network assigns other traffic channels than TCH/F9.6 or TCH/F32.0. +- 3) In case ITC=UDI, RA shall be set to V.110. In case ITC=RDI, RA shall be set to H.223 & H.245 or No. + +- 4) An MS not supporting GERAN A/Gb and GERAN Iu mode sets ACC to "none" and MaxNumTCH is set to "1 TCH". An MS not supporting GERAN A/Gb and GERAN Iu mode also sets ACCext (i.e. the extension bits of ACC parameter, see 3GPP TS 24.008 for its definition and values) and UIMI to zero if they are included in the PLMN BC-IE, i.e. UIMI is set to "NA" and the ACC parameter (including the ACCext bits) is set to the value "none" (all zeros). +- 5) The parameters FNUR and OMT are mandatory for this service. +- 6) If the call setup is started in A/Gb or GERAN Iu mode, the MS can set all ACC fields to "none" (all zeros) and MaxNumTCH parameter to the value "one TCH" (zero) and the network will interpret these values as an indication that a handover to another mode (e.g. UTRAN Iu mode) is needed. Similarly, while in another mode, the MS can inform the network that the MS does not support the requested service in A/Gb or GERAN Iu mode. + +##### B.1.3.1.4 Transparent FNUR = 56kbit/s, including 3G-H.324/M (TCH/F14.4) + +Applies to A/Gb mode only, no HO to/from UTRAN Iu mode + +| | | | | | | | | | | | | +|---------------------------|------------------------|-------------------|-----------|---------|---------------------|-----------------------------|--------------|-------------------|--------|----|--------| +| | Oct. | | | | | | | | | | | +| ITC | 3/5a | UDI 3) | 3.1 kHz | | FAX3 | Speech | | RDI 3) | | | | +| | Layer/protocol related | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA 3) | 5/5a | NA | PIAFS | V.120 | V.110 3) | H.223 & H.245 3) | X.31 Flag | No 3) | | | | +| SA | 6 | | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlct | NAV | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| | Radio channel related | | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| UR 1) | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | | +| IR 1) | 6b | NA | 8 | | | 16 | | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | NAV | +| OMT 4) | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR 1,4) | 6d | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | 48 | 56 | 64 NAV | +| ACC 1,2,4) | 6e | none | | 4.8 | | 9.6 | | 14.4 | | | NAV | +| MaxNumTCH 1,4) | 6e | | 1 | 2 | 3 | 4 1) | 5 | 6 | 7 | 8 | NAV | +| WAIUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV | +| ACC ext. | 6g | | | | | 28.8 | 32.0 | | 43.2 | | NAV | +| ASYM | 6g | no. pref. | | | | u1 biased | | d1 biased | | | NAV | + +1) IR and UR are overridden by FNUR, ACC and MaxNumTCH. + +2) ACC may have several values simultaneously (bit map coding). + +3) In case ITC=UDI, RA shall be set to V.110. In case ITC=RDI, RA shall be set to H.223 & H.245 or No. + +4) The parameters FNUR, OMT, ACC and MaxNumTCH are mandatory for this service. + +##### **B.1.3.1.5 Transparent FNUR = 64kbit/s, including 3G-H.324/M (TCH/F9.6, TCH/F14.4, TCH/F32.0, UTRAN Iu mode))** + +| | | | | | | | | | | | | +|-----------------------------|------|-------------|-----------|---------|---------|---------------|--------------|-----------|--------|----|-----| +| | Oct. | | | | | | | | | | | +| ITC | 3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +| Layer/protocol related | | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | | +| SA | 6 | | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlet | NAV | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| Radio channel related | | | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| UR 1) | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | | +| IR 1) | 6b | NA | 8 | | | 16 | | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | NAV | +| OMT 4) | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR 1,4) | 6d | | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | 48 | 56 | +| ACC 1,2,3,5) | 6e | none | | 4.8 | | 9.6 | | | 14.4 | | NAV | +| MaxNumTCH 1,3,5) | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | NAV | +| WAIUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI 3) | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV | +| ACC ext. 1,2,3) | 6g | | | | | 28.8 | 32.0 | | 43.2 | | NAV | +| ASYM | 6g | no. pref. | | | | u1 biased | | d1 biased | | | NAV | + +- 1) IR and UR are overridden by FNUR, ACC and MaxNumTCH. IR and UR are not applicable to UTRAN Iu mode. +- 2) ACC may have several values simultaneously (bit map coding). + +- 3) An MS not supporting GERAN A/Gb and GERAN Iu mode sets ACC to "none" and MaxNumTCH is set to "1 TCH". An MS not supporting GERAN A/Gb and GERAN Iu mode also sets ACCext (i.e. the extension bits of ACC parameter, see 3GPP TS 24.008 for its definition and values) and UIMI to zero if they are included in the PLMN BC-IE, i.e. UIMI is set to "NA" and the ACC parameter (including the ACCext bits) is set to the value "none" (all zeros). +- 4) The parameters FNUR and OMT are mandatory for this service. +- 5) If the call setup is started in A/Gb or GERAN Iu mode, the MS can set all ACC fields to "none" (all zeros) and MaxNumTCH parameter to the value "one TCH" (zero). The network will interpret these values as an indication that a handover to another mode (e.g. UTRAN Iu mode) is needed. Similarly, while in another mode, the MS can inform the network that the MS does not support the requested service in A/Gb or GERAN Iu mode. + +##### B.1.3.1.6 3G-H.324/M, FNUR=32.0 kbit/s (TCH/F32.0, UTRAN Iu mode) + +| | | | | | | | | | | | | +|---------------------------|------|-------------|-----------|---------|---------|---------------|--------------|------|--------|----|-------------------| +| | Oct. | | | | | | | | | | | +| ITC | 3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +| Layer/protocol related | | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | | +| SA | 6 | | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlet | NAV | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| Radio channel related | | | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| UR 3) | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | | +| IR 3) | 6b | NA | 8 | | | 16 | | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR | 6d | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | 48 | 56 | 64 NAV | +| ACC 1,2,4) | 6e | none | | 4.8 | | 9.6 | | | 14.4 | | NAV 2) | +| MaxNumTCH 2,4) | 6e | NA | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | NAV 2) | +| WAIUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI 2) | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV 2) | +| ACC ext. 1,2) | 6g | not accept. | | | | 28.8 | 32.0 | | 43.2 | | NAV 2) | + +- 1) ACC may have several values simultaneously (bit map coding). +- 2) If ACC, UIMI, MaxNumTCH and ASYM are not available operation is restricted to UTRAN. +- 3) IR and UR are overridden by FNUR, ACC and MaxNumTCH. IR and UR are not applicable to UTRAN Iu mode. + +- 4) If the call setup is started in A/Gb or GERAN Iu mode, the MS can set all ACC fields to “none” (all zeros) and MaxNumTCH parameter to the value “one TCH” (zero). The network will interpret these values as an indication that a handover to another mode (e.g. UTRAN Iu mode) is needed. Similarly, while in another mode, the MS can inform the network that the MS does not support the requested service in A/Gb or GERAN Iu mode. + +##### **B.1.3.1.7 Synchronous transparent 56 kbit/s (RDI) and 64kbit/s (UDI) (UTRAN Iu mode)** + +See B.1.3.1.3 and B.1.3.1.5. + +#### B.1.3.2 3,1 kHz audio ex-PLMN information transfer capability + +##### B.1.3.2.1 Non-X.32 Cases + +| Oct. | 3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +|------------------------|------|-------------------|--------------------|--------------------|--------------------|---------------|--------------|-----------|--------|----|-----| +| Layer/protocol related | | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | | +| SA | 6 | NA | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlet | NAV | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| Radio channel related | | | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| UR | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | | +| IR | 6b | NA | 8 | | | 16 | | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | auto 1 | | | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR | 6d | 9.6 2) | 14.4 2) | 19.2 2) | 28.8 2) | 32 | 33.6 | 38.4 | 48 | 56 | NAV | +| ACC 1) | 6e | none | | 4.8 | | 9.6 | | 14.4 | | | NAV | +| MaxNumTCH | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | NAV | +| WAIUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV | +| ACC ext. 1) | 6g | | | | | 28.8 | 32.0 | | 43.2 | | NAV | +| ASYM | 6g | no. pref. | | | | u1 biased | | d1 biased | | | NAV | + +1) ACC may have several values simultaneously (bit map coding). + +##### B.1.3.2.2 X.32 Case + +Void. + +##### B.1.3.2.3 3G-H.324/M Case + +| | | | | | | | | | | | | +|-------------------------|------|-------------|-----------|---------|--------|---------------|--------------|------|--------|--------|--------| +| | Oct. | | | | | | | | | | | +| ITC | 3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +| Layer/protocol related | | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | | +| SA | 6 | NA | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlct | NAV | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| Radio channel related | | | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| UR | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | | +| IR | 6b | NA | 8 | | | 16 | | | | | | +| MT | 6c | NA | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR | 6d | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | 48 | 56 | 64 NAV | +| ACC 1,3) | 6e | none | | 4.8 | | 9.6 | | 14.4 | | | NAV | +| MaxNumTCH 3) | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | NAV | +| WAIUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV | +| ACC ext. 1) | 6g | | | | | 28.8 | 32.0 | | 43.2 | | NAV | + +- 1) ACC may have several values simultaneously (bit map coding). +- 2) FNUR 33.6 kbit/s applies to UTRAN Iu mode only. +- 3) If the call setup is started in A/Gb or GERAN Iu mode, the MS can set all ACC fields to "none" (all zeros) and MaxNumTCH parameter to the value "one TCH" (zero). The network will interpret these values as an indication that a handover to another mode (e.g. UTRAN Iu mode) is needed. Similarly, while in another mode, the MS can inform the network that the MS does not support the requested service in A/Gb or GERAN Iu mode. + +### B.1.4 Bearer Service 40 ... 46, PAD Access Asynchronous + +Void. + +### B.1.5 Bearer Service 50 ... 53 ,Data Packet Duplex Synchronous, Unrestricted digital information transfer capability + +Void. + +### B.1.6 Bearer Service 61, Alternate Speech/Data + +Void. + +### B.1.7 Bearer Service 81, Speech followed by Data + +Void. + +### B.1.8 Teleservice 11 ... 12, Speech + +| | Oct. | | | | | | | | | | | +|------------------------|------|-------------|-----------|---------|---------|---------------|--------------|-----------|--------|----|-----| +| ITC | 3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +| Layer/protocol related | | | | | | | | | | | | +| SAP | 5 | NA | | 1.440 | | | | | | | NAV | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | NAV | +| SA | 6 | NA | | A | | S | | | | | NAV | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | NAV | +| S | 4 | NA | | SDU | | | unstructured | | | | NAV | +| U1L2P | 7 | | | ISO6429 | | COPnoFlct | | | | | NAV | +| DC | 4 | NA | | | DC | | NO | | | | NAV | +| NDB | 6a | NA | | 7 | | | 8 | | | | NAV | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | NAV | +| NSB | 6a | NA | | 1 | | 2 | | | | | NAV | +| Radio channel related | | | | | | | | | | | | +| | | | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| | | | | | | | | | | | | +| UR | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | NAV | +| IR | 6b | NA | 8 | | | 16 | | | | | NAV | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR | 6d | 9.6 | 14.4 | 19.2 | 28.8 | 32 33.6 | 38.4 | 48 | 56 | 64 | NAV | +| ACC | 6e | none | | 4.8 | | 9.6 | | 14.4 | | | NAV | +| MaxNumTCH | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | NAV | +| WAIUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV | +| ACC ext. | 6g | | | | | 28.8 | 32.0 | | 43.2 | | NAV | +| ASYM | 6g | no. pref. | | | | u1 biased | | d1 biased | | | NAV | + +### **B.1.9 Teleservice 21 ... 23, Short Message** + +Not applicable. + +### **B.1.10 Teleservice 61, Alternate Speech and Facsimile group 3** + +The information element of the "repeat indicator" is set to the value "circular for successive selection (alternate)". + +#### **B.1.10.1 Teleservice 61, Speech** + +See subclause B.1.8. + +#### B.1.10.2 Teleservice 61, Facsimile group 3 in A/Gb mode + +| ITC | Oct.
3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +|------------------------|--------------|-------------|-----------|---------|---------|---------------|--------------|-----------|--------|----|-----| +| Layer/protocol related | | | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | | +| SA | 6 | NA | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlct | NAV | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| Radio channel related | | | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| UR | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | | +| IR | 6b | NA | 8 | | | 16 | | | | | | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR | 6d | | 9.6 | 14.4 | 19.2 | 28.8 | 32 | 33.6 | 38.4 | 48 | NAV | +| ACC 1) | 6e | none | | 4.8 | | 9.6 | | 14.4 | | | NAV | +| MaxNumTCH | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | NAV | +| WAUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV | +| ACC ext. | 6g | | | | | 28.8 | 32.0 | | 43.2 | | NAV | +| ASYM | 6g | no. pref. | | | | u1 biased | | d1 biased | | | NAV | + +1) ACC may have several values simultaneously (bit map coding). + +#### B.1.10.3 Teleservice 61, Facsimile group 3 in UTRAN Iu mode + +| | | | | | | | | | | | | +|-----------|------|------------------------|-----------|---------|---------|-------------------------|--------------|-----------|--------|----|-----| +| | Oct. | | | | | | | | | | | +| ITC | 3/5a | UDI | 3.1 kHz | | FAX3 | Speech | | RDI | | | | +| | | Layer/protocol related | | | | | | | | | | +| SAP | 5 | NA | | I.440 | | | | | | | | +| RA | 5/5a | NA | PIAFS | V.120 | V.110 | H.223 & H.245 | X.31 Flag | No | | | | +| SA | 6 | NA | | A | | S | | | | | | +| CE | 6c | NA | | NT | bothNT | bothT | T | | | | | +| S | 4 | NA | | SDU | | | unstructured | | | | | +| U1L2P | 7 | | | ISO6429 | | COPnoFlet 3) | NAV | | | | | +| DC | 4 | NA | | | DC | | NO | | | | | +| NDB | 6a | NA | | 7 | | | 8 | | | | | +| NPB | 6b | NA | odd | even | 0 | 1 | none | | | | | +| NSB | 6a | NA | | 1 | | 2 | | | | | | +| | | Radio channel related | | | | | | | | | | +| RCR | 3 | dualHR | | | dualFR | | FR | | | | | +| UR | 6a | NA | 0.3 | 1.2 | 2.4 | 4.8 | 9.6 | | | | NAV | +| IR | 6b | NA | 8 | | | 16 | | | | | NAV | +| MT | 6c | none | V.21 | V.22 | V.22bis | V.26ter | V.32 | | auto 1 | | NAV | +| OMT | 6d | no other MT | | | | V.34 | | | | | NAV | +| FNUR | 6d | 9.6 | 14.4 | 19.2 | 28.8 | 32 33.6 | 38.4 | 48 | 56 | 64 | NAV | +| ACC | 6e | none | | 4.8 | | 9.6 | | 14.4 | | | NAV | +| MaxNumTCH | 6e | | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | NAV | +| WAIUR | 6f | NA | 9.6 | 14.4 | 19.2 | 28.8 | 38.4 | 43.2 | 57.6 | | NAV | +| UIMI | 6f | NA | not. req. | upto 1 | upto 2 | | upto 3 | | upto 4 | | NAV | +| ACC ext. | 6g | | | | | 28.8 | 32.0 | | 43.2 | | NAV | +| ASYM | 6g | no. pref. | | | | u1 biased | | d1 biased | | | NAV | + +### B.1.11 Teleservice 62, Automatic Facsimile group 3 + +Ref. subclause B.1.10, the information element "repeat indicator" is not available/valid. + +### B.1.12 Valid combinations of FNUR, WAIUR, ACC, mTCH + +#### B.1.12.1 Transparent Services + +The MS is allowed to signal any combination of FNUR, ACC and mTCH compliant to the following table. The network is allowed to assign any Channel Mode compliant to the following table. + +| FNUR | mTCH (Note 7, 9) | ACC (Note 1,6,9) | | | | | Channel Mode (Note 4,5) | | | | | +|-------------|------------------|------------------|----------|-----------|-----------|-----------|-------------------------|----------|-----------|-----------|-----------| +| | | TCH/F4.8 | TCH/F9.6 | TCH/F14.4 | TCH/F28.8 | TCH/F32.0 | TCH/F4.8 | TCH/F9.6 | TCH/F14.4 | TCH/F28.8 | TCH/F32.0 | +| 9.6 kbit/s | 1 | * | + | * | * | * | - | 1 | - | - | - | +| | 2 | + | * | * | * | * | 2 | 1 | - | - | - | +| 14.4 kbit/s | 1 | * | * | + | * | * | - | - | 1 | - | - | +| | 2 | * | + | * | * | * | - | 2 (N2) | 1 | - | - | +| | 3 | + | * | * | * | * | 3 | 2 (N2) | 1 | - | - | +| 19.2 kbit/s | 2 | * | + | * | * | * | - | 2 | - | - | - | +| | 4 | + | * | * | * | * | 4 | 2 | - | - | - | +| 28.8 kbit/s | 1 | * | * | * | + | * | - | - | - | 1 | - | +| | 2 | * | * | + | * | * | - | - | 2 | 1 | - | +| | 3 | * | + | * | * | * | - | 3 | 2 | 1 | - | +| 32.0 kbit/s | 1 | * | * | * | * | + | - | - | - | - | 1 | +| 38.4 kbit/s | 3 | * | * | + | * | * | - | - | 3 (N2) | - | - | +| | 4 | * | + | * | * | * | - | 4 | 3 (N2) | - | - | +| 48.0 kbit/s | 4 | * | * | + | * | * | - | - | 4 (N2) | - | - | +| | 5 | * | + | * | * | * | - | 5 | 4 (N2) | - | - | +| 56.0 kbit/s | 2 | * | * | * | * | + | - | - | - | - | 2(N8) | +| | 4 | * | * | + | * | * | - | - | 4 (N2) | - | 2(N8) | +| | 5 | * | + | * | * | * | - | 5 (N3) | 4 (N2) | - | 2(N8) | +| 64.0 kbit/s | 2 | * | * | * | * | + | - | - | - | - | 2(N8) | +| | 5 | * | * | + | * | * | - | - | 5 (N2) | - | 2(N8) | +| | 6 | * | + | * | * | * | - | 6 (N2,3) | 5 (N2) | - | 2(N8) | + +**NB: N in the table stands for NOTE.** + +NOTE 1: A '+' indicates that a certain channel coding shall be included in the ACC and a '\*' indicates that it may or may not be included. + +NOTE 2: Padding Required, ref 3GPP TS 44.021. + +NOTE 3: Air interface user rate 11,2 kbit/s, ref. 3GPP TS 44.021. + +NOTE 4: A '-' indicates that this channel coding cannot be assigned for this FNUR. + +NOTE 5: A certain channel coding may only be assigned if indicated as acceptable in the ACC. + +NOTE 6: In case the MS signals an ACC containing TCH/F4.8 only and the network does not support TCH/F4.8 channel coding, then the network may act as if TCH/F9.6 were included in the ACC. + +NOTE 7: The MS is allowed to signal higher values for mTCH than indicated in the table for the signalled FNUR and ACC. Before initiating the assignment procedure, the MSC, if necessary, shall lower the value of the mTCH to the highest value applicable for the signalled FNUR and ACC. + +NOTE 8: Can only be used for bit transparent 56 (RDI) and 64 (UDI) kbit/s connections in 56 kbit/s and 64 kbit/s environments, respectively. + +NOTE 9: The MS can request a transparent data call by setting all ACC bits to "none" (all zeros) and MaxNumTCH parameter to the value "one TCH" (zero). The MSC will interpret these values as an indication that an intersystem handover from A/Gb or GERAN Iu mode to another (e.g. UTRAN Iu) mode is required before the call setup is completed. Similarly, while in another mode, the MS can inform the network that the MS does not support the requested service in A/Gb or GERAN Iu mode. + +The final decision about the radio interface configuration is taken by the BSS during the Assignment procedure subject to the restrictions that the number of assigned TCH/F may not exceed the mTCH, that the channel coding is among the ACC and that the AIUR equals the FNUR. + +The radio interface configuration may be changed by the BSS during the call as long as the channel coding used is among the ACC, the mTCH is not exceeded and the AIUR is kept constant (ref. 3GPP TS 22.034). + +#### B.1.12.2 Non-transparent services + +The MS is allowed to signal any combination of WAIUR, ACC and mTCH compliant to the following table. A combination is compliant to the table, if there exists at least one row that it is compliant to. A combination is compliant to a row if each parameter value meets the conditions given in that row. When a WAIUR, ACC, mTCH combination is compliant to a row, the network is allowed to assign any Channel Mode compliant to that row. The notes of the table provide further details on the compliance conditions. + +| WAIUR (Note 7) | mTCH (Note 5) | ACC (Note 1,4) | | | | | Channel Mode (Note 2,3,6) | | | | | +|----------------|---------------|----------------|----------|-----------|-----------|-----------|---------------------------|----------|-----------|-----------|-----------| +| | | TCH/F4.8 | TCH/F9.6 | TCH/F14.4 | TCH/F28.8 | TCH/F43.2 | TCH/F4.8 | TCH/F9.6 | TCH/F14.4 | TCH/F28.8 | TCH/F43.2 | +| 9.6 kbit/s | 1 | * | + | * | * | * | 1 | 1 | - | - | - | +| | 2 | + | * | * | * | * | 1 - 2 | 1 | - | - | - | +| 14.4 kbit/s | 1 | * | * | + | * | * | 1 | 1 | 1 | - | - | +| | 3 | + | * | * | * | * | 1 - 3 | 1 - 2 | 1 | - | - | +| 19.2 kbit/s | 2 | * | + | * | * | * | 1 - 2 | 1 - 2 | 1 | 1 | - | +| | 4 | + | * | * | * | * | 1 - 4 | 1 - 2 | 1 | 1 | - | +| 28.8 kbit/s | 1 | * | * | * | + | * | 1 | 1 | 1 | 1 | - | +| | 2 | * | * | + | * | * | 1 - 2 | 1 - 2 | 1 - 2 | 1 | - | +| | 3 | * | + | * | * | * | 1 - 3 | 1 - 3 | 1 - 2 | 1 | - | +| 38.4 kbit/s | 4 | * | + | * | * | * | 1 - 4 | 1 - 4 | 1 - 3 | 1 - 2 | 1 | +| 43.2 kbit/s | 1 | * | * | * | * | + | 1 | 1 | 1 | 1 | 1 | +| | 3 | * | * | + | * | * | 1 - 3 | 1 - 3 | 1 - 3 | 1 - 2 | 1 | +| 57.6 kbit/s | 2 | * | * | * | + | * | 1 - 2 | 1 - 2 | 1 - 2 | 1 - 2 | 1 | +| | 4 | * | * | + | * | * | 1 - 4 | 1 - 4 | 1 - 4 | 1 - 2 | 1 | + +NOTE 1: A '+' indicates that a certain channel coding shall be included in the ACC and a '\*' indicates that it may or may not be included. + +NOTE 2: A '-' indicates that this channel coding cannot be used for this WAIUR. + +NOTE 3: A certain channel coding may only be assigned if indicated as acceptable in the ACC. + +NOTE 4: In case the MS signals an ACC containing TCH/F4.8 only and the network does not support TCH/F4.8 channel coding, then the network may act as if TCH/F9.6 were included in the ACC. + +NOTE 5: The MS is allowed to signal higher values for mTCH than indicated in the table for the signalled WAIUR and ACC. Before initiating the assignment procedure, the MSC, if necessary, shall lower the value of the mTCH to the highest value applicable for the signalled WAIUR and ACC. + +NOTE 6: Unless an EDGE channel is assigned in one direction at least, the same channel coding is assigned in both directions, and an equal or lesser number of channels is assigned in the up link direction than in the down link direction. If an EDGE channel is assigned in one direction, TCH/F14.4 or an EDGE channel is assigned in the other direction. If the user has indicated up or down link biased asymmetry preference, TCH/F14.4 is assigned in the unbiased direction. The number of channels assigned is the same in each direction unless restricted by the mobile classmark, and is always within the limits given in the corresponding column. + +NOTE 7: The MS is allowed to signal higher values for WAIUR than indicated in the table for the signalled mTCH and ACC. Before initiating the assignment procedure, the MSC, if necessary, shall lower the value of the WAIUR to the highest value applicable for the signalled mTCH and ACC. + +The final decision about the radio interface configuration is taken by the BSS during the Assignment procedure. The BSS may assign any number of TCH/F ranging from 1 to mTCH and use any of the channel codings among the ACC. The BSS shall try to reach the WAIUR if the resource situation allows it. The maximum possible AIUR shall not exceed the WAIUR unless the higher AIUR can be reached with a smaller number of TCH/F (ref. 3GPP TS 22.034). + +The radio interface configuration may be changed by the BSS during the call as long as the channel coding used is among the ACC and the mTCH is not exceeded. + +### B.1.13 Assignment of radio access bearer parameters depending on FNUR and WAIUR + +#### B.1.13.1 Transparent Services + +Depending on the FNUR negotiated between the network and the MS, the network is allowed to assign any radio resources with a radio access bearer parameter indicating a Quality of Service specifying + +| QoS Parameter | Value | Comments | +|-------------------------------------|---------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | +| Traffic Class | Conversational | Subject to operator tuning (Note 2) | +| RAB Asymmetry Indicator | Symmetric | | +| Maximum bit rate | = guaranteed bit rate | | +| Guaranteed bit rate | FNUR = 64 .. 28,8 kbit/s | GBR for FNUR=56 kbit/s is 64 kbit/s (Note 1) | +| Delivery Order | Yes | | +| Maximum SDU size | 640bits for FNUR = 32, 56 and 64 kbit/s
576 bits for FNUR = 28.8 kbit/s
672 bits for FNUR = 33.6 kbit/s | | +| Transfer Delay | < 200 ms | Subject to operator tuning | +| Traffic Handling Priority | - | Not applicable for the conversational traffic class | +| Source statistics descriptor | Unknown | | +| SDU Parameters | | | +| SDU error ratio | - | Not applicable | +| Residual bit error ratio | $10^{-4}$ | Subject to operator tuning according to 3GPP TS 23.107.
Operator may also choose different value for Multimedia and other transparent data services. | +| Delivery of erroneous SDUs | - | No error detection in the core network | + +NOTE 1: In case the FNUR = 56 kbit/s, the GBR is set to 64 kbit/s. Last bit in each data octet is set to 1 + +NOTE 2: Only traffic Classes "Streaming" and "Conversational" shall be used for Cs data service RABs. The operator tuning is restricted to a choice between them. + +The final decision about the radio interface configuration is taken by the RNC during the Assignment procedure. + +#### B.1.13.2 Non-transparent services for UTRAN Iu mode + +Depending on the WAIUR signalled by the MS, the network is allowed to assign any radio resources with a radio access bearer parameter indicating a Quality of Service specifying + +| QoS Parameter | | Value | Comments | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|----------------------------------|----------------------------------------------------------------------------------| +| | | | | +| Traffic Class | | Streaming | Subject to operator tuning (Note 3) | +| RAB Asymmetry Indicator | | Symmetric | | +| Maximum bit rate | | 14.4, 28.8, 57.6 kbit/s | Maximum bit rate is set to the highest value $\leq$ WAIUR (Note 1) | +| Guaranteed bit rate | | 14.4, 28.8, 57.6 kbit/s | Operator may choose any of the possible values less or equal to WAIUR. (Note 1). | +| Delivery Order | | Yes | | +| Maximum SDU size | | 576 bits | | +| Transfer Delay | | 250 ms | Subject to operator tuning | +| Traffic Handling Priority | | - | Not applicable to the streaming traffic class | +| Source statistics descriptor | | Unknown | | +| SDU Parameters | | | | +| | Residual bit error ratio | $10^{-3}$ | Subject to operator tuning. | +| | Delivery of erroneous SDUs | No error detection consideration | | +| SDU format information | | | | +| | RAB Subflow Combination bit rate | 57.6 kbit/s | (Note 2) | +| | RAB Subflow Combination bit rate | 28.8 kbit/s | (Note 2) | +| | RAB Subflow Combination bit rate | 14.4 kbit/s | | +| | RAB Subflow Combination bit rate | 0 kbit/s | indicates DTX, RFCI is not assigned | +|

NOTE 1: If WAIUR is less or equal to 14.4 kbit/s then GBR and MBR shall be set to 14.4 kbit/s.

NOTE 2: Only RAB subflow combination bit rates \leq maximum bit rate shall be specified.

NOTE 3: Only traffic Classes "Streaming" and "Conversational" shall be used for Cs data service RABs. The operator tuning is restricted to a choice between them.

| | | | + +The final decision about the radio interface configuration is taken by the RNC during the Assignment procedure. + +#### B.1.13.3 Non-transparent services for GERAN Iu mode + +Depending on the WAIUR signalled by the MS, the network is allowed to assign any radio resources with a radio access bearer parameter indicating a Quality of Service specifying + +| QoS Parameter | Value | Comments | +|----------------------------------|---------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------| +| Traffic Class | Streaming | Subject to operator tuning (Note 8) | +| RAB Asymmetry Indicator | Symmetric | | +| Maximum bit rate | 12 kbit/s, 14,4 kbit/s, 24 kbit/s, 28,8 kbit/s, 36 kbit/s, 43,2 kbit/s, 48 kbit/s, 57.6 kbit/s | Maximum bit rate is set to the highest value $\leq$ WAIUR (Note 1, 3, 4, 5 and 6) | +| Guaranteed bit rate | 12 kbit/s, 14,4 kbit/s, 24 kbit/s, 28,8 kbit/s, 36 kbit/s, 43,2 kbit/s, 48 kbit/s, 57.6 kbit/s | Operator may choose any of the possible values less or equal to WAIUR. (Note 1) | +| Delivery Order | Yes | | +| Maximum SDU size | 480 bits if only RAB Subflow
Combination bit rates of multiples of 12 kbit/s are possible, 576 bits in all other cases | | +| Transfer Delay | 230 ms if only RAB Subflow
Combination bit rates of multiples of 12 kbit/s are possible, 250 ms in all other cases | Subject to operator tuning | +| Traffic Handling Priority | - | Not applicable to the streaming traffic class | +| Source statistics descriptor | Unknown | | +| SDU Parameters | | | +| Residual bit error ratio | $10^{-3}$ | Subject to operator tuning. | +| Delivery of erroneous SDUs | No error detection consideration | | +| SDU format information | | | +| Subflow SDU size | 576 bit | (Note 7) | +| RAB Subflow Combination bit rate | 57,6 kbit/s | (Note 2) | +| Subflow SDU size | 480 bit | (Note 7) | +| RAB Subflow Combination bit rate | 48 kbit/s | (Note 2 and 3) | +| Subflow SDU size | 576 bit | (Note 7) | +| RAB Subflow Combination bit rate | 43,2 kbit/s | (Note 2) | +| Subflow SDU size | 480 bit | (Note 7) | +| RAB Subflow Combination bit rate | 36 kbit/s | (Note 2 and 4) | +| Subflow SDU size | 576 bit | (Note 7) | +| RAB Subflow Combination bit rate | 28,8 kbit/s | (Note 2) | +| Subflow SDU size | 480 bit | (Note 7) | +| RAB Subflow Combination bit rate | 24 kbit/s | (Note 2 and 5) | +| Subflow SDU size | 576 bit | (Note 7) | +| RAB Subflow Combination bit rate | 14,4 kbit/s | (Note 2) | +| Subflow SDU size | 480 bit | (Note 7) | +| RAB Subflow Combination bit rate | 12 kbit/s | (Note 2 and 6) | +| RAB Subflow Combination bit rate | 0 kbit/s | indicates DTX, RFCI is not assigned | + +- NOTE 1: If WAIUR is less or equal to 14.4 kbit/s then GBR and MBR shall be set to 14.4 kbit/s for TCH/F14.4. If WAIUR is less or equal to 9.6 kbit/s then GBR and MBR shall be set to 12 kbit/s for TCH/F9.6. The maximum values for GBR and MBR shall not exceed the WAIUR unless the higher GBR and MBR can be reached with a smaller number of TCH/F (ref. subclause B.1.12.2). This means, that e.g., a GBR and MBR of 24 kbit/s (2 x TCH/F9.6) can be selected for a WAIUR of 19,2 kbit/s. +- NOTE 2: Only RAB subflow combination bit rates $\leq$ maximum bit rate shall be specified. +- NOTE 3: If the WAIUR is 38,4 kbit/s, a GBR and MBR of 48 kbit/s is possible for 4 x TCH/F9.6. +- NOTE 4: If the WAIUR is 28,8 kbit/s, a GBR and MBR of 36 kbit/s is possible for 3 x TCH/F9.6. +- NOTE 5: If the WAIUR is 19,2 kbit/s, a GBR and MBR of 24 kbit/s is possible for 2 x TCH/F9.6. +- NOTE 6: If the WAIUR is 9,6 kbit/s, a GBR and MBR of 12 kbit/s is possible for 1 x TCH/F9.6. +- NOTE 7: The Subflow SDU size should only be present when the individual Subflows have different sizes. +- NOTE 8: Only traffic Classes "Streaming" and "Conversational" shall be used for Cs data service RABs. The operator tuning is restricted to a choice between them. + +The final decision about the radio interface configuration is taken by the BSS during the Assignment procedure. + +## --- B.2 Low Layer/High Layer Compatibility Information Element + +### B.2.1 Introduction + +#### B.2.1.1 General Consideration + +The purpose of the Low Layer/High Layer Compatibility Information Element (LLC/HLC-IE) is to provide a means for additional end-to-end compatibility checking by an addressed entity (e.g. a remote user, an interworking unit or a high layer function network node). The LLC/HLC-IE may be manipulated by the PLMN to maintain consistency with the setup parameter negotiation between the mobile station and the network (ref. to 3GPP TS 29.007). The LLC/HLC-IE is transferred transparently by the ISDN between the call originating PLMN and the addressed entity. + +With respect to the individual parameter settings at the MS the following cases may be distinguished (see 3GPP TS 27.002 and 3GPP TS 27.003): + +- Mobile-originated call set up by a MS consisting of a MT with R interface: + - The setting results from respective MMI actions and/or MT internal settings. +- Mobile-terminated call set up to a MS consisting of a MT with R interface: + - The LLC/HLC related part of the compatibility check is carried out according to the knowledge of the MT concerning its implemented functions (i.e. answering the call). The offered field values determine the selection of the terminal function for the intended connection. + +Where applicable, the same settings and rules concerning LLC and/or HLC apply as for ISDN use (ref. ITU-T Recommendation Q.931 and ETR 018). However, considering that PLMN data transmission is based on ITU-T V.110 rate adaptation, the MS shall provide the LLC-IE for mobile-originated calls when using unrestricted or restricted digital information transfer capability. This is to assure the conveyance of the e.g. "ITU-T V.110" indication towards the called entity, as the comparable indication in the ISDN BC-IE may be lost. It shall also be possible to choose whether or not the LLC-IE is provided for the case of an information transfer capability "3,1 kHz audio ex PLMN". + +There shall be no contradiction of the information between the BC-IE and LLC-IE at the originating side. However, as some parts of the bearer capability may be modified during the transport of the call, there should be minimum duplication of this information between the BC-IE and the LLC-IE. + +If as a result of duplication, a contradiction occurs between the BC-IE and the LLC-IE at the terminating side, the receiving entity shall ignore the conflicting information in the LLC-IE. + +#### B.2.1.2 Interpretation of the Tables + +The individual contents of the LLC/HLC-IE are represented in the following tables. The indication of the applicable service group defines the link between the PLMN BC-IE and its associated LLC/HLC-IEs. + +If the appropriate message includes multiple BC-IEs and if LLC and/or HLC information is available, multiple LLCs and HLCs shall be included in the message. The LLC/HLC associated with the BC-IE indicating speech shall be marked as "not applicable" (3GPP TS 24.008). + +Legend:                    { xxxx | yyyy }            choice of values +                               ----                            not relevant for this service (set to appropriate value) +                               [ zzzz ]                        optional + +### B.2.2 LLC Bearer Service 20 + +#### B.2.2.1 Unrestricted / restricted digital information transfer capability + +Low layer compatibility information element: + +| Octet | Information element field | field value | +|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| 3 | Coding standard
Information transfer capability | ITU-T
{ unrestricted digital restricted digital } | +| 4 | Transfer mode
Information transfer rate | circuit mode
64 kbit/s | +| 5 | User information layer 1 protocol | { V.110/X.30 V.120 } | +| 5a | Synchronous / asynchronous
Negotiation
User rate | asynchronous
in-band not possible
{ 0.3 1.2 2.4 4.8 9.6
14.4 19.2 28.8 38.4 48 56 } kbit/s | +| 5b
2) | Intermediate rate
NIC on Tx
NIC on Rx
Flow control on Tx
Flow control on Rx | { 8 16 } kbit/s
-----
{ not required 1) required }
{ not accepted 1) accepted } | +| 5b
3) | Rate adaption header / no header
Multiple frame establishment support
Mode of operation
Assignor / assignee
In-band / out-band negotiation | Rate adaption header included
Multiple frame establishment supported
Protocol sensitive mode of operation
----- | +| 5c | Number of stop bits
Number of data bits
Parity | { 1 2 } bits
{ 7 8 } bits
{ odd even none forced to 0 forced to 1 } | +| 5d | Duplex mode
Modem type | á[ duplex ]
----- | + +- 1) only these values are applicable to Mobile Originated Calls. +- 2) octet 5b for V.110/X.30. +- 3) octet 5b for V.120. + +#### B.2.2.2 3,1 kHz audio ex-PLMN information transfer capability + +Low layer compatibility information element: + +| Octet | Information element field | field value | +|-------|-----------------------------------------------------------------------------------------|--------------------------------------------------------------------| +| 3 | Coding standard
Information transfer capability | ITU-T
3.1kHz audio | +| 4 | Transfer mode
Information transfer rate | circuit mode
64 kbit/s | +| 5 | User information layer 1 protocol | {G.711 A-law G.711 u-law (PCS-1900)} | +| 5a | Synchronous / asynchronous
Negotiation
User rate | (may be set depending on user's requirement) | +| 5b | Intermediate rate
NIC on Tx
NIC on Rx
Flow control on Tx
Flow control on Rx | not relevant
but cannot be omitted
in order to have octet 5d | +| 5c | Number of stop bits
Number of data bits
Parity | (may be set depending on the user's requirement) | +| 5d | Duplex mode
Modem type | [ duplex ]
[{V.21 V.22 V.22bis V.26ter V.32 V.34}] | + +NOTE: If octet 5d is not specified, the whole LLC is not required. + +### B.2.3 LLC Bearer Service 30 + +#### B.2.3.1 Unrestricted / restricted digital information transfer capability + +Low layer compatibility information element: + +| Octet | Information element field | field value | +|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------| +| 3 | Coding standard
Information transfer capability | ITU-T
{ digital unrestricted restricted digital } | +| 4 | Transfer mode
Information transfer rate | circuit mode
64 kbit/s | +| 5 | User information layer 1 protocol | { V.110/X.30 X.31 flag stuffing V.120 H.223 and H.245 } | +| 5a | Synchronous / asynchronous
Negotiation
User rate | synchronous
in-band not possible
{ 0.3 1.2 2.4 4.8 9.6 1.2/0.075 14.4 19.2 28.8 32.0 38.4 48 56 } kbit/s | +| 5b
2) | Intermediate rate
NIC on Tx
NIC on Rx
Flow control on Tx
Flow control on Rx | { 8 16 } kbit/s
{ not required required }
{ not accepted accepted }
----- | +| 5b
3) | Rate adaption header / no header
Multiple frame establishment support
Mode of operation
Assignor / assignee
In-band / out-band negotiation | Rate adaption header included
Multiple frame establishment supported
Protocol sensitive mode of operation
----- | +| 5c
1) | Number of stop bits
Number of data bits
Parity | not relevant
but cannot be omitted
in order to have octet 5d | +| 5d
1) | Duplex mode
Modem type | [ duplex ]
----- | + +- 1) If octet 5d is not specified, octet 5c may be omitted. +- 2) octet 5b for V.110/X.30. +- 3) octet 5b for V.120. + +#### B.2.3.2 3,1 kHz audio ex-PLMN information transfer capability + +Low layer compatibility information element: + +| Octet | Information element field | field value | +|-------|-----------------------------------------------------------------------------------------|--------------------------------------------------------------------| +| 3 | Coding standard
Information transfer capability | ITU-T
3.1kHz audio | +| 4 | Transfer mode
Information transfer rate | circuit mode
64 kbit/s | +| 5 | User information layer 1 protocol | {G.711 A-law G.711 u-law (PCS-1900)} | +| 5a | Synchronous / asynchronous
Negotiation
User rate | (may be set depending on the user's requirement) | +| 5b | Intermediate rate
NIC on Tx
NIC on Rx
Flow control on Tx
Flow control on Rx | not relevant
but cannot be omitted
in order to have octet 5d | +| 5c | Number of stop bits
Number of data bits
Parity | (may be set depending on the user's requirement) | +| 5d | Duplex mode
Modem type | [ duplex ]
[ { V.22 V.22bis V.26ter V.32 V.34 } ] | + +NOTE: If octet 5d is not specified, octets 5a..5d may be omitted. + +### B.2.4 LLC Bearer Services 41 ... 46 + +Void. + +### B.2.5 LLC Bearer Services 51 ... 53 + +Void. + +### B.2.6 LLC Bearer Service 61 + +Void. + +### B.2.7 LLC Bearer Service 81 + +Void. + +### B.2.8 HLC Teleservices 11 ... 12 + +High layer compatibility information element: + +| Octet | Information element field | Field value | +|-------|------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------| +| 3 | Coding standard
Interpretation
Presentation method of protocol profile | ITU-T
first high layer characteristic identification to be used in the call
high layer protocol profile | +| 4 | High layer characteristics identific. | Telephony | + +### B.2.9 HLC Teleservices 21 ... 23 + +Not applicable. + +### B.2.10 HLC Teleservice 61 + +High layer compatibility information element: + +| Octet | Information element field | Field value | +|-------|------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------| +| 3 | Coding standard
Interpretation
Presentation method of protocol profile | ITU-T
first high layer characteristic identification to be used in the call
high layer protocol profile | +| 4 | High layer characteristics identific. | Facsimile G2/G3 | + +### B.2.11 HLC Teleservice 62 + +High layer compatibility information element: + +| Octet | Information element field | Field value | +|-------|----------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------| +| 3 | Coding standard
Interpretation

Presentation method of protocol profile | ITU-T
first high layer characteristic identification to be used in the call
high layer protocol profile | +| 4 | High layer characteristics identific. | Facsimile G2/G3 | + +# Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|----------|----------|-----|-----|--------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| | Apr 1999 | | | | Transferred to 3GPP CN1 | 7.1.0 | | +| 03-1999 | CN#03 | | | | Approved at CN#03 | | 3.0.0 | +| 06-1999 | CN#04 | | 001 | | Introduction of EDGE channel codings into the specifications | 3.0.0 | 3.1.0 | +| 09-1999 | CN#05 | | 002 | | Asymmetry in EDGE | 3.1.0 | 3.2.0 | +| 09-1999 | CN#05 | | 003 | | EDGE related correction | 3.1.0 | 3.2.0 | +| 12-1999 | CN#06 | | 004 | | Introduction of FTM | 3.2.0 | 3.3.0 | +| 12-1999 | CN#06 | | 005 | | Introduction of UMTS | 3.2.0 | 3.3.0 | +| 12-1999 | CN#06 | | 006 | | Introduction of PIAFS and enhancement of processing at mobile terminated call | 3.2.0 | 3.3.0 | +| 12-1999 | CN#06 | | 007 | | Introduction of multi media | 3.2.0 | 3.3.0 | +| 12-1999 | CN#06 | | 008 | | Service clean-up for Release 99 | 3.2.0 | 3.3.0 | +| 12-1999 | CN#06 | | 009 | | BC-IE setting for Real-time non-transparent FAX | 3.2.0 | 3.3.0 | +| 03-2000 | CN#07 | | 010 | | FALLBACK TO SPEECH IN A CS MULTIMEDIA CALL SETUP | 3.3.0 | 3.4.0 | +| 03-2000 | CN#07 | | 011 | | Bit transparent services RDI and UDI | 3.3.0 | 3.4.0 | +| 03-2000 | CN#07 | | 012 | | FTM corrections | 3.3.0 | 3.4.0 | +| 03-2000 | CN#07 | | 013 | | Alignment to RANAP and other clarifications | 3.3.0 | 3.4.0 | +| 03-2000 | CN#07 | | 014 | | Corrections related to MULTIMEDIA | 3.3.0 | 3.4.0 | +| 06-2000 | CN#08 | | 015 | | Missing Asymmetry preference indication in Table B. 5.a | 3.4.0 | 3.5.0 | +| 06-2000 | CN#08 | | 016 | | Residual bit error ratio in Transparent Data | 3.4.0 | 3.5.0 | +| 06-2000 | CN#08 | | 017 | | Adding the value of GBR of NT services | 3.4.0 | 3.5.0 | +| 06-2000 | CN#08 | | 018 | | Application of multi media in GSM | 3.4.0 | 3.5.0 | +| 06-2000 | CN#08 | | 019 | | Removal of packet access service | 3.4.0 | 3.5.0 | +| 06-2000 | CN#08 | | 020 | | WAIUR in case of HO between UMTS and GSM | 3.4.0 | 3.5.0 | +| 06-2000 | CN#08 | | 021 | | Adaptations for UMTS | 3.4.0 | 3.5.0 | +| 06-2000 | CN#08 | | 022 | | Indication of discontinuous transfer for NT data | 3.4.0 | 3.5.0 | +| 06-2000 | CN#08 | | 022 | | Indication of discontinuous transfer for NT data | 3.4.0 | 3.5.0 | +| 06-2000 | CN#08 | | 023 | 1 | Indication of WAIUR 14.4kbit/s in case of UMTS FAX | 3.4.0 | 4.0.0 | +| 09-2000 | CN#09 | | 024 | 1 | UMTS clean-up | 4.0.0 | 4.1.0 | +| 09-2000 | CN#09 | | 027 | | Cleanup of RAB parameter setting | 4.0.0 | 4.1.0 | +| 09-2000 | CN#09 | | 028 | | Relevance of GSM specific BC-IE parameters for negotiating RLP version in UMTS | 4.0.0 | 4.1.0 | +| 09-2000 | CN#09 | | 032 | | 32 kbit/s UDI/RDI multimedia in GSM | 4.0.0 | 4.1.0 | +| 09-2000 | CN#09 | | 034 | | 3.1 kHz multimedia calls at 33.6 kbit/s data rate | 4.0.0 | 4.1.0 | +| 09-2000 | CN#09 | | 036 | | RCR is not indicated from the network to the MS | 4.0.0 | 4.1.0 | +| 09-2000 | CN#09 | | 038 | | Modification from V.25bis to V.250 | 4.0.0 | 4.1.0 | +| 09-2000 | CN#09 | | 040 | | Delivery of erroneous SDUs parameter value | 4.0.0 | 4.1.0 | +| 12-2000 | CN#10 | | 042 | | Correction for 32 kbit/s UDI/RDI | 4.1.0 | 4.2.0 | +| 12-2000 | CN#10 | | 043 | | Removal of Bearer Service 30 Non-transparent | 4.1.0 | 4.2.0 | + +| | | | | | | | | +|---------|-------|-----------|-----|---|----------------------------------------------------------------------------------------------------------|-------|-------| +| 12-2000 | CN#10 | | 044 | | Handover for 56 kbit/s | 4.1.0 | 4.2.0 | +| 03-2001 | CN#11 | NP-010042 | 047 | 1 | Removal of blocking of higher modem speeds | 4.2.0 | 4.3.0 | +| 03-2001 | CN#11 | NP-010046 | 048 | 1 | Deletion of NT Fax in GSM from Release 4. | 4.2.0 | 4.3.0 | +| 03-2001 | CN#11 | NP-010042 | 050 | | RAB- assignment request (RAB parameter) | 4.2.0 | 4.3.0 | +| 03-2001 | CN#11 | NP-010042 | 052 | | Handover for 56 kbit/s [Removal of flow diagram B.1.3.1.7] | 4.2.0 | 4.3.0 | +| 03-2001 | CN#11 | NP-010047 | 053 | | Editorial modifications of flow diagrams | 4.2.0 | 4.3.0 | +| 03-2001 | CN#11 | NP-010043 | 055 | | Correction of service's scope | 4.2.0 | 4.3.0 | +| 03-2001 | CN#11 | NP-010202 | 057 | 2 | Corrections for a mobile terminated call using the single numbering scheme | 4.2.0 | 4.3.0 | +| 03-2001 | CN#11 | NP-010047 | 058 | | Clarification of allowed combinations of FNUR and ACC values for the V.34 modem based 3G-H.324/M service | 4.2.0 | 4.3.0 | +| 06-2001 | CN#12 | NP-010255 | 060 | | Corrections of PLMN BC attributes | 4.3.0 | 4.4.0 | +| 09-2001 | CN#13 | NP-010438 | 062 | 1 | Removal of erroneous IR value | 4.4.0 | 4.5.0 | +| 09-2001 | CN#13 | NP-010438 | 063 | 1 | Removal of erroneous information in B.1.3.1.6. | 4.4.0 | 4.5.0 | +| 09-2001 | CN#13 | NP-010438 | 066 | 1 | Negotiation of Rate adaptation/Other rate adaptation | 4.4.0 | 4.5.0 | +| 12-2001 | CN#14 | NP-010574 | 069 | | SDU size for transparent data at 33.6 kbit/s | 4.5.0 | 4.6.0 | +| 12-2001 | CN#14 | NP-010604 | 070 | 3 | Terminology clarifications as requested by TSG GERAN | 4.6.0 | 5.0.0 | +| 03-2002 | CN#15 | NP-020081 | 074 | 1 | Negotiation of parameter values for facsimile | 5.0.0 | 5.1.0 | +| 03-2002 | CN#15 | NP-020084 | 075 | 1 | Mobile terminated call with single numbering scheme | 5.0.0 | 5.1.0 | +| 06-2002 | CN#16 | NP-020169 | 071 | 7 | Service change and fallback for UDI/RDI multimedia calls | 5.1.0 | 5.2.0 | +| 06-2002 | CN#16 | NP-020172 | 077 | 1 | Multislot clarification | 5.1.0 | 5.2.0 | +| 09-2002 | CN#17 | NP-020404 | 080 | - | Removal of SDU error ratio for NT services | 5.2.0 | 5.3.0 | +| 12-2002 | CN#18 | NP-020617 | 081 | 1 | CS Data Services (including HSCSD and EDGE) for GERAN lu mode | 5.3.0 | 5.4.0 | +| 12-2002 | CN#18 | NP-020619 | 082 | 4 | Mobile originating BC handling for SCUDIF calls | 5.3.0 | 5.4.0 | +| 03-2003 | CN#19 | NP-030075 | 084 | 1 | Removal of S reference point within the MS and introduction of GERAN lu mode | 5.4.0 | 5.5.0 | +| 06-2003 | CN#20 | NP-030201 | 088 | | Negotiation of fixed network user rate (FNUR) | 5.5.0 | 5.6.0 | +| 06-2003 | CN#20 | NP-030202 | 091 | 1 | Removal of S interface in the MS | 5.5.0 | 5.6.0 | +| 06-2003 | CN#20 | NP-030260 | 096 | 1 | BC-IE alignment with 24.008. | 5.5.0 | 5.6.0 | +| 06-2003 | CN#20 | NP-030201 | 099 | 1 | Use of single or multislot configurations | 5.5.0 | 5.6.0 | +| 09-2003 | CN#21 | NP-030327 | 100 | 3 | Interpretation of "no BC-IE in CALL PROC/CONF messages" | 5.6.0 | 5.7.0 | +| 06-2004 | CN#24 | NP-040239 | 107 | 1 | Interpretation of "no BC-IE in CALL PROC/CONF messages" | 5.7.0 | 5.8.0 | +| 12-2004 | CN#26 | | | | Upgraded to v6.0.0 | 5.8.0 | 6.0.0 | +| 06-2005 | CP#28 | CP-050209 | 110 | 4 | Transparent data call request in dual mode case | 6.0.0 | 6.1.0 | +| 06-2005 | CP#28 | CP-050243 | 114 | 3 | Alignment to R99 correction of NA value for Data Compression | 6.0.0 | 6.1.0 | +| 09-2005 | CP#29 | CP-050379 | 115 | | Removal of "S" reference point within MS | 6.1.0 | 6.2.0 | +| 12-2006 | CT#34 | CP-060618 | 118 | | RAB traffic class | 6.2.0 | 6.3.0 | +| 06-2007 | CT#36 | | | | Upgraded to v7.0.0 | 6.3.0 | 7.0.0 | +| 12-2008 | CT#42 | | | | Upgraded to v8.0.0 due to simple upgrade without no technical change | 7.0.0 | 8.0.0 | +| 12-2009 | CT#46 | | | | Automatic upgrade from previous Release | 8.0.0 | 9.0.0 | + +| | | | | | | | | +|---------|-------|-----------|-----|---|--------------------------------------------------------|--------|--------| +| 12-2010 | CT#50 | CP-100779 | 120 | 1 | Correcting non-specific external references | 9.0.0 | 9.1.0 | +| 03-2011 | CT#51 | | | | Automatic upgrade from previous Release version 9.1.0 | 9.1.0 | 10.0.0 | +| 09-2012 | CT#57 | | | | Automatic upgrade from previous Release version 10.0.0 | 10.0.0 | 11.0.0 | \ No newline at end of file diff --git a/marked/Rel-11/27_series/27002/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/Rel-11/27_series/27002/21ad58fee90f2be50708ff541d225507_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e2b7665ac98b13dbf9b106d118c902c3bbb8f32 --- /dev/null +++ b/marked/Rel-11/27_series/27002/21ad58fee90f2be50708ff541d225507_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca1da277cec0529c768f86e93b53c6f15f924a128bbf8e1ee7d268641f493973 +size 22454 diff --git a/marked/Rel-11/27_series/27002/raw.md b/marked/Rel-11/27_series/27002/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ebc44ab51cf539656bcc5451f018f9ab54b0ae29 --- /dev/null +++ b/marked/Rel-11/27_series/27002/raw.md @@ -0,0 +1,780 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 1.1 References ..... | 6 | +| 1.2 Abbreviations ..... | 8 | +| 1.3 Definitions..... | 8 | +| 2 Reference Configuration..... | 8 | +| 2.1 Customer Access Configuration..... | 8 | +| 2.2 Terminal Adaptation Function (TAF)..... | 8 | +| 3 Terminal Adaptation Functions for transparent services ..... | 9 | +| 3.1 Rate Adaptation in A/Gb mode..... | 9 | +| 3.1.1 Rate Adaptation - R interface..... | 9 | +| 3.1.2 Rate Adaptation - S Interface (ITU-T I.420 [14]) ..... | 9 | +| 3.2 Interchange Circuit Signalling Mapping - ITU-T V-series interface..... | 9 | +| 3.2.1 Mapping of V.24 [19] circuits to status bits ..... | 9 | +| 3.2.2 Single slot configurations (TCH/F9.6 or TCH/F4.8) ..... | 10 | +| 3.2.3 Multislot configurations (TCH/F9.6 or TCH/F4.8)..... | 10 | +| 3.2.4 Channel codings TCH/F14.4, TCH/F28.8..... | 10 | +| 3.3 Interface Signal Levels - R interface..... | 10 | +| 3.4 Call Establishment and Clearing Signalling Mapping ..... | 11 | +| 3.4.1 V-series interface Autocalling/answering ..... | 11 | +| 3.4.2 S Interface (I.420) Signalling Mapping..... | 11 | +| 3.4.3 Call Establishment Manual Operation - Utilizing the Unrestricted Digital Capability..... | 11 | +| 3.4.4 V-series interface Call Clearing ..... | 11 | +| 4 Terminal Adaptation Functions for non-transparent services..... | 11 | +| 4.1 Data Structure..... | 11 | +| 4.1.1 Data Structure on S Interface..... | 11 | +| 4.1.2 Data Structure on R Interface ..... | 12 | +| 4.1.3 Data Structure Provided by the L2R Function to the RLP Function..... | 12 | +| 4.2 Signalling Mapping ..... | 12 | +| 4.2.1 Interchange Circuit Signalling Mapping - ITU-T V-series interface ..... | 12 | +| 4.2.2 Call Establishment and Clearing Signalling Mapping ..... | 13 | +| 4.3 Flow Control ..... | 13 | +| 4.3.1 Conditions Requiring Flow Control towards the Network..... | 13 | +| 4.3.2 Conditions Requiring Flow Control towards TE2..... | 13 | +| 4.3.3 Local Flow Control..... | 13 | +| 4.3.4 Character Orientated Protocol with No Flow Control..... | 14 | +| 4.4 Buffers..... | 14 | +| 4.4.1 TX Buffers..... | 14 | +| 4.4.2 RX Buffers..... | 14 | +| 4.5 Bit Transparency ..... | 14 | +| 4.6 Transportation of "BREAK" condition ..... | 14 | +| 4.7 Data Compression ..... | 14 | +| 5 Terminal interfacing to 3GPP TS 24.008 [8] Mapping ..... | 15 | +| 5.1 Mobile Originated Calls..... | 16 | +| 5.2 Mobile Terminated Calls..... | 16 | +| 5.3 Call Clearing ..... | 17 | +| 5.3.1 Mobile initiated ..... | 17 | +| 5.3.2 Network initiated..... | 17 | +| Annex A (normative): L2R Functionality ..... | 18 | +| A.1 Introduction..... | 18 | +| A.2 The L2RCOP..... | 18 | +| A.3 Use of the L2RCOP ..... | 21 | +| A.3.1 Radio Link Connection Control ..... | 21 | + +A.3.2 Data Transfer.....21 +A.3.3 Status Transfer.....21 +A.3.4 Flow Control .....21 +A.3.5 Break .....21 +A.3.5.1 Normal Realization.....21 +A.3.5.2 Realization in case of Data Compression is used.....22 +**Annex B (informative): Use of a 9 pin connector as an MT2 type interface .....23** +**Annex C (informative): General mapping of ITU-T V.24 [19] circuits to channel status bits 24** +Annex D (informative): Change history.....25 + +# --- 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 interfaces and Terminal Adaptation Functions (TAF) integral to a Mobile Termination (MT) which enable the use of asynchronous bearer services in the PLMN and the attachment of asynchronous terminals to a MT (see 3GPP TS 24.002 [3] and 3GPP TS 23.101 [6]). + +The general aspects of Terminal Adaptation Functions are contained in 3GPP TS 27.001 [10]. + +The present document covers support of these services for the following interfaces and procedures: + +- (i) ITU-T V.14 [16] procedures. +- (ii) ITU-T V.21 [17] DTE/DCE interface. +- (iii) ITU-T V.22bis [18] DTE/DCE interface. +- (iv) ITU-T V.32 [24] DTE/DCE procedures. +- (v) ITU-T I.420 [14] S interface. +- (vi) ITU-T V.250 [22] signalling procedures. + +The asynchronous data rates between the MT and the IWF are defined in 3GPP TS 22.002 [5]. + +NOTE: From GSM R99 onwards the following services are no longer required in a PLMN: + +- the dual Bearer Services "alternate speech/data" and "speech followed by data"; +- the dedicated services for PAD and Packet access; +- the BS 21 ... 26 and BS 31 ... 34. + +The support of these services is still optional. The specification of these services is not within the scope of the present document. For that, the reader is referred to GSM Release 98. + +NOTE: Please note that the Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used. GERAN Iu mode is for further study. + +## 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. + +- [1] Void. +- [2] 3GPP TS 43.010: "GSM Public Land Mobile Network (PLMN) connection types". +- [3] 3GPP TS 24.002: "GSM-UMTS Public Land Mobile Network (PLMN) access reference configuration". +- [4] 3GPP TS 44.021: "Rate adaption on the Mobile Station - Base Station System (MS - BSS) interface". +- [5] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)". +- [6] 3GPP TS 23.101: "General UMTS Architecture". +- [7] 3GPP TR 23.910: "Circuit Switched Data Bearer Services". +- [8] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols-Stage 3". + +- [9] 3GPP TS 24.022: "Radio Link Protocol (RLP) for Circuit Switched Bearer and Teleservices". +- [10] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". +- [11] 3GPP TS 27.007: "AT command set for 3G User Equipment (UE)". +- [12] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [13] 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)". +- [14] ITU-T Recommendation I.420 (1998):"Basic user-network interface". +- [15] ITU-T Recommendation V.4 (1988): "General structure of signals of international alphabet No.5 code for character oriented data transmission over public telephone networks". +- [16] ITU-T Recommendation V.14 (1993): "Transmission of start-stop characters over synchronous bearer channels". +- [17] ITU-T Recommendation V.21 (1988): "300 bits per second duplex modem standardized for use in the general switched telephone network". +- [18] ITU-T Recommendation V.22bis (1988): "2400 bits per second duplex modem using the frequency division technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [19] ITU-T Recommendation V.24 (1996): "List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE)". +- [20] ITU-T Recommendation V.25 (1996): "Automatic answering equipment and general procedures for automatic calling equipment on the general switched telephone network including procedures for disabling of echo control devices for both manually and automatically established calls". +- [21] Void. +- [22] ITU-T Recommendation V.250 (1999): "Serial asynchronous automatic dialling and control". +- [23] ITU-T Recommendation V.28 (1993): "Electrical characteristics for unbalanced double-current interchange circuits". +- [24] ITU-T Recommendation V.32 (1993): "A family of 2-wire, duplex modems operating at data signalling rates of up to 9600 bit/s for use in the general switched telephone network and on leased telephone-type circuits". +- [25] ITU-T Recommendation V.42 (1996): "Error-correcting procedures for DCEs using asynchronous-to-synchronous conversion". +- [26] ITU-T Recommendation V.42 bis (1990): "Data compression procedures for data circuit-terminating equipment (DCE) using error correction procedures". +- [27] ITU-T Recommendation V.110 (1996): "Support of data terminal equipments with V-Series interfaces by an integrated services digital network". +- [28] ITU-T Recommendation X.28 (1997): "DTE/DCE interface for a start-stop mode Data Terminal Equipment accessing the Packet Assembly/Disassembly facility (PAD) in a public data network situated in the same country". +- [29] Personal Computer Memory Card Association: "PCMCIA 2.1 or PC-Card 3.0 electrical specification or later revisions". + +- [30] Infrared Data Association IrDA "IrPHY Physical layer signalling standard". +- [31] ISO 2110 (1989): "Data communication - 25-pole DTE/DCE interface connector and contact number assignments". +- [32] ITU-T Recommendation Q.931 (1998): "ISDN user-network interface layer 3 specification for basic call control". + +## 1.2 Abbreviations + +In addition to the abbreviations used in the present document that are listed in TR 21.905 [12] the following internal abbreviations are used: + +| | | +|-------|----------------------------------------------| +| CFI | Call Failure Indication | +| CRN | Call Request with Number | +| DIC | Disregard Incoming Call | +| IA5 | International Alphabet no. 5 | +| INC | INcoming Call | +| INV | INVALID | +| ITU-T | ITU-Telecommunication Standardization Sector | +| VAL | VALID | + +## 1.3 Definitions + +The term 'mobile station' (MS) in the present document is synonymous with the term 'user equipment' (UE) as defined in 3GPP TR 21.905 [12]. + +The term 'TE2' in the present document is synonymous with the term 'TE' as defined in 3GPP TR 21.905 [12]. + +The term 'MT2' in the present document is synonymous with the term 'MT' as defined in 3GPP TR 21.905 [12]. + +In addition to the definitions used in the present document that are listed in TR 21.905 [12] the following internal definitions are used: + +**A/Gb mode:** indicates that the text applies only to a system or sub-system which operate in A/Gb mode of operation, i.e. with a functional division that is in accordance with the use of an A or a Gb interface between the radio access network and the core network + +**Iu mode:** indicates that the text applies only to a system or a sub-system which operates in Iu mode of operation, i.e. with a functional division that is in accordance with the use of an Iu-CS or Iu-PS interface between the radio access network and the core network + +# --- 2 Reference Configuration + +3GPP TS 27.001 [10], 3GPP TS 23.101 [6] and 3GPP TS 24.002 [3] describe the basic reference configurations. + +## 2.1 Customer Access Configuration + +This configuration is as shown in figure 1 of 3GPP TS 24.002 [3]. The present document specifically refers to the Mobile Terminations (MTs) which support terminals of the type TE1 and TE2 with asynchronous capabilities. The TAF is functionally a part of an MT1, MT2 or MT0 with an integral asynchronous data capability. + +## 2.2 Terminal Adaptation Function (TAF) + +The TAF provides facilities to allow manual or automatic call control functions associated with circuit switched services. The following functions are also included: + +- Conversion of electrical, mechanical, functional and procedural characteristics of the ITU-T V series and ISDN type interfaces to those required by the PLMN. +- Bit rate adaptation of the ITU-T V series data signalling rates and the ISDN 64 kbit/s to that provided in the PLMN. + +- The mapping functions necessary to convert automatic calling and/or automatic answering procedures of the ITU-T recommendation V.250 [22] and parameters for asynchronous operation. +- The mapping functions necessary to convert S interface signalling to the PLMN Dm channel signalling. +- Flow control (in some cases resulting in non-transparency of data as described in 4.3). +- Layer 2 Relaying (see annex A). +- In-call modification function. +- Synchronization procedure, which means the task of synchronizing the entry to and the exit from the data transfer phase between two user terminals. This is described in 3GPP TS 27.001 [10]. +- Filtering of channel control information as described in 3GPP TS 27.001 [10]. +- Terminal compatibility checking. +- Splitting and combining of the data flow in case of multiple substream data configurations. + +# --- 3 Terminal Adaptation Functions for transparent services + +3GPP TS 43.010 [2] defines connection types for the support of transparent services in A/Gb mode whilst 3GPP TR 23.910 [7] defines connection types for transparent services in UTRAN Iu mode. + +## 3.1 Rate Adaptation in A/Gb mode + +3GPP TS 44.021 [4] describes the rate adaptation scheme to be utilized over the Base Station (BS) to Mobile Station (MS) link. 3GPP TS 43.010 [2] refers to the rate adaptation elements to be provided in the MS. + +### 3.1.1 Rate Adaptation - R interface + +This is provided as indicated in 3GPP TS 44.021 [4]. + +### 3.1.2 Rate Adaptation - S Interface (ITU-T I.420 [14]) + +VOID + +## 3.2 Interchange Circuit Signalling Mapping - ITU-T V-series interface + +The interchange circuit signalling at the interface between the TE2 and the MT shall conform to ITU-T Recommendation V.24 [19]. The signals required at this interface are shown in table 3. + +The mapping of these signals to the pins of a 25 pin D-type connector is given in ISO 2110 [31]. The mapping for a commonly used 9 pin connector is given in annex B. + +### 3.2.1 Mapping of V.24 [19] circuits to status bits + +Status bits SA, SB and X are used to convey channel control information associated with the data bits in the data transfer state. Table 1 shows the mapping scheme between the ITU-T V.24 [19] circuit numbers and the status bits for the transparent mode. It also shows how the unused status bits should be handled. It is derived from the general mapping scheme described in annex C. A binary 0 corresponds to the ON condition, a binary 1 to the OFF condition. + +The transport of these status bits by the various channel codings is described in subsequent sections. + +**Table 1: Mapping scheme at the MT for the transparent mode** + +| Signal at TE2/MT interface or condition within the MT | Mapping direction: MT to IWF | Mapping direction: IWF to MT | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------------------| +| CT 105 | not mapped (note 1) | | +| CT 106 | | from status bit X (note 7) | +| CT 107 | | not mapped (note 5) | +| CT 108/2 | not mapped (note 6) | | +| CT 109 | | from status bit SB (note 7) | +| CT 133 | not mapped (note 2) | | +| always ON | to status bit SA (note 3) | | +| always ON | to status bit SB (note 1) | | +| always ON | to status bit X (note 4) | | +| ignored by MT | | from status bit SA (note 3) | +| NOTE 1: The SB bit towards the IWF, according to the General Mapping (annex C), could be used to carry CT 105. However, CT 105 should always be ON in the data transfer state since only duplex operation is supported. Also, many DTEs use the connector pin assigned to CT 105 for CT 133. No interchange circuit shall be mapped to the SB bit, which shall always be set to ON in the data transfer state. | | | +| NOTE 2: CT 133 is not mapped since there is no flow control in transparent mode. | | | +| NOTE 3: The SA bits in both directions are available only with certain channel codings. Therefore, for maximum compatibility, they should not be mapped. | | | +| NOTE 4: The X bit towards the IWF is not mapped and shall always be set to ON in the data transfer state since there is no flow control in transparent mode. | | | +| NOTE 5: CT 107 is controlled by the channel synchronisation process (07.01). | | | +| NOTE 6: CT 108/2 may be used in the call setup and answering processes. | | | +| NOTE 7: The status bits are filtered before being mapped to the ITU-T V.24 [19] circuits (3GPP TS 27.001 [10]). | | | + +### 3.2.2 Single slot configurations (TCH/F9.6 or TCH/F4.8) + +3GPP TS 44.021 [4] refers to the frame structure and identifies the use of the status bits for the carriage of signalling information in transparent mode. The S bits are put into two groups. SA is carried by bits S1, S3, S6, S8 and SB by bits S4, S9 in the ITU-T Recommendation V.110 [27] 80-bit intermediate rate frame. + +### 3.2.3 Multislot configurations (TCH/F9.6 or TCH/F4.8) + +In transparent multislot configurations, status bits S1, S3 and the X-bit between the D12 and D13 - in the ITU-T Recommendation V.110 [27] 80-bit intermediate rate frame - are used for transferring substream numbering information. The S4-bit is used for frame synchronization between the parallel substreams (reference 3GPP TS 44.021 [4]). The remaining S bits are put into two groups. SA is carried by bits S6, S8 and SB by bit S9. The remaining X bits can be used as described in subclause 3.2.1. + +### 3.2.4 Channel codings TCH/F14.4, TCH/F28.8 + +For information on the mapping of the interchange circuit signalling bits in the 14,5 kbit/s multiframe structure, refer to 3GPP TS 44.021 [4]. There is no SA bit in this channel coding. Only the SB and X bits are carried. + +## 3.3 Interface Signal Levels - R interface + +The signal levels at the interface between the TE2 and the MT shall conform to ITU-T V.28 [23], or to IrDA IrPHY physical signalling standard specification [30], or to PCMCIA 2.1 [29], or to PC-Card 3.0 [29] electrical specification or to later revisions. + +## 3.4 Call Establishment and Clearing Signalling Mapping + +### 3.4.1 V-series interface Autocalling/answering + +- These procedures are provided according to ITU-T Recommendation V.250 [22] and 3GPP TS 27.007 [11]. +- For autocalling, during the call establishment phase, i.e. after signalling, calling tone according to ITU-T Recommendation V.25 [20] shall be generated in the IWF (3GPP TS 29.007 [13]). + +During the call establishment phase: + +- the states of the ITU-T Recommendation V.24 [19] interchange circuits shall be according to 3GPP TS 27.001 [10]; +- the data and status bits from the IWF shall not be mapped; +- the data and status bits towards the IWF shall be according to 3GPP TS 27.001 [10]. + +### 3.4.2 S Interface (I.420) Signalling Mapping + +Void. + +### 3.4.3 Call Establishment Manual Operation - Utilizing the Unrestricted Digital Capability + +In this case the user shall not hear network supervisory tones or answer tone. The data transfer phase shall be entered automatically. + +### 3.4.4 V-series interface Call Clearing + +This procedure is provided according to ITU-T Recommendation V.250 [22] and 3GPP TS 27.007 [11]. + +During the call clearing phase: + +- the states of the ITU-T Recommendation V.24 [19] interchange circuits shall be according to ITU-T Recommendation V.24 [19]; +- the data and status bits from the IWF shall not be mapped or used by the MT in any way; +- the data and status bits towards the IWF have no significance and may be set to 1 and OFF respectively. + +# --- 4 Terminal Adaptation Functions for non-transparent services + +3GPP TS 43.010 [2] defines connection types for the support of non-transparent services in A/Gb mode whilst 3GPP TR 23.910 [7] defines connection types for non-transparent services in UTRAN Iu mode. + +## 4.1 Data Structure + +### 4.1.1 Data Structure on S Interface + +Void. + +### 4.1.2 Data Structure on R Interface + +The protocol models for this are described in 3GPP TS 43.010 [2]. The data consists of 7 or 8 bit characters with additional start and stop elements. The 7 bit data can additionally have an associated parity bit, 8 bit data cannot have an additional parity bit. + +The interchange circuit signalling at the interface between the TE2 and the MT shall conform to ITU-T Recommendation V.24 [19]. The signals required at this interface are shown in table 3. + +The interface shall provide inband (XON/XOFF) and out of band (CT106) flow control. The use of CT133 for out of band flow control shall be implemented according to ITU-T Recommendation V.42 [25]. + +### 4.1.3 Data Structure Provided by the L2R Function to the RLP Function + +See annex A. + +## 4.2 Signalling Mapping + +### 4.2.1 Interchange Circuit Signalling Mapping - ITU-T V-series interface + +Status bits SA, SB and X are used to convey channel control information associated with the data bits in the data transfer state. Table 2 shows the mapping scheme between the ITU-T Recommendation V.24 [19] circuit numbers and the status bits for the non-transparent mode. It also shows how the unused status bits should be handled. It is derived from the general mapping scheme described in annex C. A binary 0 corresponds to the ON condition, a binary 1 to the OFF condition. + +The transport of the status bits by the L2RCOP is described in annex A. + +**Table 2: Mapping scheme at the MT for the non-transparent mode** + +| Signal at TE2/MT interface or condition within the MT | Mapping direction: MT to IWF | Mapping direction: IWF to MT | +|-------------------------------------------------------|------------------------------|------------------------------| +| CT 105 | not mapped (note 1) | | +| CT 106 (note 4) | | from status bit X (note 7) | +| CT 107 | | not mapped (note 5) | +| CT 108/2 | not mapped (note 6) | | +| CT 109 | | from status bit SB | +| CT 133 (note 8) | to status bit X (notes 3,8) | | +| always ON | to status bit SA (note 2) | | +| always ON | to status bit SB (note 1) | | +| ignored by MT | | from status bit SA (note 2) | + +NOTE 1: The SB bit towards the IWF, according to the General Mapping (annex C), could be used to carry CT 105. However, CT 105 should always be ON in the data transfer state since only duplex operation is supported. Also, many DTEs use the connector pin assigned to CT 105 for CT 133. No interchange circuit shall be mapped to the SB bit which shall always be set to ON in the data transfer state. + +NOTE 2: The SA bits (both directions) are not mapped since CTs 107 and 108/2 are handled locally (notes 5 and 6). + +NOTE 3: The condition of status bit X towards the IWF may also be affected by the state of the receive buffer in the MT. + +NOTE 4: The state of CT 106 (or other local flow control mechanism) may also be affected by the state of the transmit buffer in the MT and the state of the RLP (RR/RNR). + +NOTE 5: CT 107 is controlled by the channel synchronisation process (3GPP TS 27.001 [10]). + +NOTE 6: CT 108/2 may be used in the call setup and answering processes. + +NOTE 7: For inband local flow control, changes in the condition of the status bit X from the IWF also result in the sending of XON or XOFF to the DTE. + +NOTE 8: For inband local flow control, CT 133 is not mapped and the status bit X towards the IWF is controlled by the reception of XON and XOFF characters from the DTE. + +### 4.2.2 Call Establishment and Clearing Signalling Mapping + +This is identical to the transparent case with the exception of the transparent/non-transparent element, see clause 5. + +In addition, the L2R/RLP shall give an explicit indication when the link into the connected network is established. If the link fails, an explicit "link lost" indication shall be given. + +## 4.3 Flow Control + +The passage of flow control information between L2Rs is described in annex A. subclauses 4.3.1, 4.3.2 and 4.3.3 describe the operation of the flow control mechanisms. These mechanisms apply for all the non-transparent services covered by the present document, with the exception of Character Orientated Protocol with No Flow Control which is treated in subclause 4.3.4. + +### 4.3.1 Conditions Requiring Flow Control towards the Network + +The L2R function shall send immediately a "flow control active" indication in the following circumstances: + +- (i) If the receive buffer from the radio side reaches a preset threshold (BACKPRESSURE). + +- (ii) If local flow control is initiated by the TE2 (see 4.3.3 a) or c)). On receipt of this flow control indication transmission of data from the receive buffer towards the TE2 is halted. + +On removal of the buffer congestion or local flow control the L2R shall send a "flow control inactive" indication. + +In addition, for the local flow control condition, transmission of data from the receive buffers shall be restarted. + +### 4.3.2 Conditions Requiring Flow Control towards TE2 + +The L2R functions shall immediately activate local flow control (see 4.3.3 b) or d)) under the following circumstances: + +- (i) The transmit buffer reaches a pre-set threshold (BACKPRESSURE). +- (ii) The L2R receives a "flow control active" indication. + +On removal of buffer congestion or receipt of L2R/RLP "flow control inactive" the local flow control shall be removed. + +### 4.3.3 Local Flow Control + +Two methods of local flow control are allowed: + +Outband: + +- a) From TE2: CT133 shall be turned OFF to indicate flow control active, and ON to indicate flow control inactive. +- b) From TAF: CT106 shall be turned OFF to indicate flow control active, and ON to indicate flow control inactive. + +Inband: + +- c) From TE2: XOFF (DC3) is sent to indicate flow control active. XON (DC1) is sent to indicate flow control inactive. The XON/XOFF characters received from the TE2 are extracted by the L2R from the data stream and are not sent across the radio interface. Where XON/XOFF is utilized then the TAF shall generate flow control active/inactive immediately, i.e. the XON/XOFF characters do not enter the transmit buffer. +- d) From TAF: As from TE2. + +If the outband method is used, the L2R shall pass the DC1/DC3 characters as data, i.e. no flow control indications shall be generated on receipt of DC1/DC3. + +### 4.3.4 Character Orientated Protocol with No Flow Control + +If the users layer 2 indicates Character Orientated Protocol with no flow control then no flow control is used, i.e. the X-bit is not set to OFF and DC1/DC3 characters are passed through as data. + +## 4.4 Buffers + +### 4.4.1 TX Buffers + +Data received on CT103 from the TE2 shall be buffered such that if the MT is unable to transfer the data over the radio path then data is not lost. + +The buffer shall be capable of holding the data. Its size is up to the implementers. + +When the buffer is half full, TE2 shall be flow controlled as per 4.3.2, unless Character Orientated Protocol with No Flow Control is being used (see 4.3.4). + +### 4.4.2 RX Buffers + +Data for transfer to the TE2 on CT104 shall be buffered such that if the TE2 is unable to accept data then data transferred from the MT is not lost. + +The buffer size should be up to the implementers. + +When the buffer becomes half full, the L2R shall send a "flow control active" indication, unless Character Orientated Protocol with No Flow Control is being used. + +## 4.5 Bit Transparency + +Void. + +## 4.6 Transportation of "BREAK" condition + +The "BREAK" condition must be recognized by the L2R function and passed immediately to the IWF. The L2R shall generate a "BREAK" condition to the TE2 on receipt of a "BREAK" indication from the IWF. + +Annex A describes how the L2R shall transport the "BREAK" indication. + +## 4.7 Data Compression + +L2R optionally includes a data compression function according to ITU-T V.42bis [26] that spans from the MS to the IWF in the MSC. The error correction function is provided by RLP instead of ITU-T Recommendation V.42 [25]. RLP XID is used to negotiate compression parameters. L2R includes the ITU-T V.42bis [26] control function especially for reinitializing in case of break recognition or RLP reset and error indication by the data compression function respectively. + +**Table 3: Minimum set of Interchange Circuits** + +| Circuit Number | Circuit Name | Ground | Data | | Control | | +|----------------|--------------------------------------------|--------|--------|----------|---------|----------| +| | | | To TE2 | From TE2 | To TE2 | From TE2 | +| CT102 | Common return | x | | | | | +| CT103 | Transmitted data | | | x | | | +| CT104 | Received data return | | x | | | | +| CT105 | Request to send (note 2) | | | | | x | +| CT106 | Ready for sending | | | | x | | +| CT107 | Data set ready | | | | x | | +| CT108/2 | Data terminal ready | | | | | x | +| CT109 | Data channel received line signal detector | | | | x | | +| CT125 | Calling indicator (note 1) | | | | x | | +| CT133 | Ready for Receiving (note 2) | | | | | x | + +NOTE 1: CT125 is used with the automatic answering function of the TAF. + +NOTE 2: CT105 and CT133 are assigned to the same connector pin on both the standard 25 pin connector (ISO 2110) and the commonly used 9 pin connector (annex B). When this pin is used for CT133 then on the DCE (MT) side of the interface CT 105 is treated as being always in the ON condition. Similarly, when this pin is being used for CT105 then on the DCE (MT) side of the interface CT 133 is treated as being always in the ON condition. As circuit 133 is used only in duplex operation and circuit 105 is used only in half duplex operation (which is not supported by GSM or UMTS) there should be no conflict. + +# 5 Terminal interfacing to 3GPP TS 24.008 [8] Mapping + +Only those elements/messages that are of particular relevance are considered. + +Interface procedures not directly mappable to 3GPP TS 24.008 [8] are not considered. Mobile management procedures of 3GPP TS 24.008 [8] are not considered applicable. + +Mapping of other call establishment or clearing messages to the S interface e.g. "Call proceeding" etc. has not been included. It is assumed these can be mapped directly and as such are of no relevance to the manual interfaces. + +For the Alternate speech/group 3 facsimile service the TAF shall be able to generate a "Modify" message according to the defined procedure in 3GPP TS 24.008 [8]. + +## 5.1 Mobile Originated Calls + +Call establishment is initiated by the keypad or DTE action: + +a) Setup + +| Element | Derived from | +|--------------------|------------------------------------------------------| +| | MMI | +| Called Address | Keypad | +| Called Sub Address | Keypad | +| HLC | Derived from internal settings or MMI information. | +| LLC | Same as HLC | +| BC | Same as HLC 3GPP TS 27.001 [10] gives allowed values | + +b) Release Complete + +| Element | Derived from | +|---------|--------------------| +| | MMI | +| Cause | Display (optional) | + +## 5.2 Mobile Terminated Calls + +Call establishment is initiated by receipt of Setup at the MS: + +a) Setup + +| Element | Mapped on to | +|--------------------|--------------------| +| | MMI | +| Called Address | Display (optional) | +| Called Sub Address | Display (optional) | +| HLC | Display (optional) | +| LLC | Display (optional) | +| BC | Display (optional) | + +### b) Call Confirm + +Information for the BC element in the call confirm shall be derived from e.g. MMI or by internal settings. + +### c) Connect + +Connect is sent in response to connect from MMI. + +## 5.3 Call Clearing + +### 5.3.1 Mobile initiated + +Call clearing is initiated by the keypad or DTE action: + +Disconnect + +| Element | Derived from | | +|---------|--------------|-------------------| +| | MMI | ITU-T V.250 [22] | +| Cause | Keypad | See section 3.4.4 | + +### 5.3.2 Network initiated + +Call clearing is initiated by receipt of Disconnect at the MS: + +Disconnect + +| Element | Mapped on to | | +|---------|--------------------|--------------------------| +| | MMI | ITU-T V.250 [22] | +| Cause | Display (optional) | Unsolicited result codes | + +# Annex A (normative): L2R Functionality + +## A.1 Introduction + +This annex describes the L2R functionality for non-transparent character oriented protocols. The general aspects of L2Rs are described in 3GPP TS 27.001 [10]. Figure 1 shows the 3 sub-functions of a character oriented L2R. + +![Figure 1: Diagram of a Character Oriented Relay Entity (CORE) showing its internal sub-functions: CONTP Entity, CORE, and L2RCOP Entity.](21ad58fee90f2be50708ff541d225507_img.jpg) + +The diagram illustrates the internal structure of a Character Oriented Relay Entity (CORE). It is represented by a large rectangle divided into three main sections. On the left, a section labeled 'CONTPT' at the top and 'CONTPT Entity' at the bottom, separated by a diagonal line. In the center, a section labeled 'CORE'. On the right, a section labeled 'L2RCOP' at the top and 'L2RCOP Entity' at the bottom, also separated by a diagonal line. Horizontal lines extend from the left and right sides of the CORE rectangle, representing input and output connections. + +Figure 1: Diagram of a Character Oriented Relay Entity (CORE) showing its internal sub-functions: CONTP Entity, CORE, and L2RCOP Entity. + +CONTPT Character Oriented Non-Transparent Protocol. +CORE Character Oriented Relay Entity. +L2RCOP L2R Character Oriented Protocol. + +**Figure 1** + +Section 2 describes the L2R Character Oriented Protocol (L2RCOP) and section 3 the use of the L2RCOP. + +## A.2 The L2RCOP + +Information is transferred between L2Rs in fixed length n octet Protocol Data Units (PDUs). This corresponds to the fixed length of the RLP frame information field. The octets within the L2RCOP-PDU are numbered 0 to n-1; octet 0 is transmitted first. The value of n depends on the negotiated RLP version and frame type ( 3GPP TS 24.022[9]). The bits within the octets are numbered 1 to 8; bit 1 is transmitted first. + +The RLP version value 2 indicates RLP multi-link operation. The RLP version value 0 or 1 indicates RLP single-link operation. + +- Each octet contains a status octet, an information octet or fill. + +Octet 0 contains either a status octet or a user information octet. + +- Octet 0 shall always contain a status octet in case at least one status octet is transported in the L2RCOP PDU. In RLP-versions 0 and 1 a PDU always carries at least one status octet. In RLP version 2 a PDU carries status octet(s) only if actual status change(s) has taken place within the period represented by the PDU. Here the L2R status flag in the RLP version 2 header is set to 1 when status octet(s) is carried in the PDU. +- Status octets contain 3 status bits and 5 address bits. In cases where two status octets within the PDU are separated by more than 23 octets, the first status octet in octet m is followed by a pointer octet in octet m+1 forming a two-octet status field. The pointer octet contains one reserved bit and seven address bits indicating the number of characters between the status field and the second status octet. +- The 3 status bits correspond to SA, SB and X in ITU-T Recommendation V.110 [27]. The SA, SB and X bits use bit positions 8, 7 and 6 in the status octets. When a status bit changes the current state of all three bits shall be transmitted. +- Information octets are character octets or encoded character octets. +- Character octets are coded in the following way: + +- The first bit of the character received/transmitted corresponds to bit position 1 in the octet and the seventh bit corresponds to bit 7. For order of transmission of IA5 characters see ITU-T Recommendation V.4 [15]. +- 7 bit characters are padded with a 0 in bit position 8. Received parity (if used) is inserted in bit position 8, if parity is not used bit 8 is set to 0. +- Any start/stop bits are removed by the L2R. +- Encoded character octets are provided by the compression function. They are encoded according to ITU-T Recommendation V.42bis [26]. +- Information octets are inserted into L2RCOP-PDUs in order of transmission in octets 1 to n-1 for RLP single-link operation, in octets 1 to n-1 for RLP multi-link operation with status octet transportation, and in octets 0 to n-1 for multi-link operation with no status octet transportation. +- The address field in the status octets indicates the position of next status octet within the L2RCOP-PDU. This indicates the number of characters between status octets. Thus if two status octets are inserted into L2RCOP-PDU at offsets l and m the address value shall be defined by m-l-1. Address bit $2^0$ corresponds to bit 1 in the status octets. Address bit $2^1$ to bit 2 etc. +- Status octets are inserted in the character stream whenever a status change needs to be transmitted. +- Only address values 1 to n-2 ( $n-2 \leq 23$ ) in the address field of status octets are used for addressing purposes. The implication of not allowing address value 0 to be used for addressing is that two status octets cannot be sent after each other. The remaining codes are used to indicate: + - Last status change, remainder of L2RCOP-PDU empty. Address field value 31. + - Last status change, remainder of L2RCOP-PDU full of characters. Address field value 30. + - Destructive break signal, remainder of L2RCOP-PDU empty. Address field value 29. + - Destructive break acknowledge, remainder of L2RCOP-PDU empty. Address field value 28. + - L2RCOP-PDU contains at least two status octets which are separated by more than 23 characters; the address-field value in the first octet of the two-octet status field is 27 and the address bits in the pointer octet of the status field indicate the number of characters between the two-octet status field and the next status octet. + - Address field values from n-1 to 26 are reserved. In case of a PDU more than 25 octets in length, address field values from 24 to 26 are reserved. +- When it is necessary to insert a status octet into the character stream when no status change has occurred, e.g. to indicate that the remainder of a L2RCOP-PDU is empty or to indicate a break signal, the current status shall be repeated. +- In case when 64 data octets are carried by a 66-octet PDU, a status octet is carried in octet 0 and another status octet within the first 24 data octets. (The first status octet gives the address of the second status octet, which carries value 30 in its address field). + +Three examples of an L2RCOP PDU are shown in figure 2. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----|----|----|---|---|---|---|---|---|-----------------------------------------| +| 0 | SA | SB | x | 0 | 0 | 0 | 1 | 1 | | +| 1 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | IA5 "G" (odd parity) | +| 2 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | IA5 "S" (odd parity) | +| 3 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | IA5 "M" (odd parity) | +| 4 | SA | SB | x | 1 | 1 | 1 | 1 | 1 | (last status change, rest of PDU empty) | +| . | | | | | | | | | | +| . | | | | | | | | | | +| . | | | | | | | | | | +| n-1 | | | | | | | | | | + +Figure 2a: Single-link RLP and multi-link RLP with status octet transfer in PDU + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----|---|---|---|---|---|---|---|---|----------------------| +| 0 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | IA5 "S" (odd parity) | +| 1 | 1 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | IA5 "G" (odd parity) | +| 2 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 1 | IA5 "S" (odd parity) | +| 3 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | IA5 "M" (odd parity) | +| 4 | | | | | | | | | | +| . | | | | | | | | | | +| . | | | | | | | | | | +| . | | | | | | | | | | +| n-1 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | IA5 "M" (odd parity) | + +Figure 2b: Multi-link RLP L2RCOP PDU with no status octet transfer + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----|----|----|---|---|---|---|---|---|----------------------| +| 0 | SA | SB | X | 0 | 0 | 0 | 1 | 1 | | +| 1 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | IA5 "M" (odd parity) | +| 2 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | IA5 "A" (odd parity) | +| 3 | 1 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | IA5 "R" (odd parity) | +| 4 | SA | SB | X | 1 | 1 | 0 | 1 | 1 | | +| 5 | R | 0 | 1 | 0 | 0 | 0 | 1 | 1 | | +| . | | | | | | | | | | +| . | | | | | | | | | | +| 41 | SA | SB | X | 0 | 0 | 0 | 0 | 1 | | +| 42 | 1 | 1 | 0 | 0 | 1 | 1 | 0 | 1 | IA5 "K" (odd parity) | +| 43 | SA | SB | X | 1 | 1 | 1 | 1 | 0 | | +| . | | | | | | | | | | +| . | | | | | | | | | | +| . | | | | | | | | | | +| 65 | 1 | 1 | 0 | 0 | 1 | 1 | 1 | 1 | IA5 "O" (odd parity) | + +Figure 2c: A 66-octet RLP L2RCOP PDU with status octets separated by more than 23 octets + +## A.3 Use of the L2RCOP + +The CORE relays status changes, break conditions and characters in both directions between the CONTP entity and the L2RCOP entity. + +The L2RCOP entity performs the following functions. + +### A.3.1 Radio Link Connection Control + +Given appropriate indications from the signalling mechanisms the L2RCOP entity uses the services of the radio link to establish and release the connection to its peer L2RCOP entity in the IWF. + +### A.3.2 Data Transfer + +The L2RCOP entity shall assemble and disassemble L2RCOP-PDUs. Data characters are assembled into L2RCOP-PDUs until either: + +- the PDU is full; +- the Radio Link service can accept another Radio Link service Data Unit. + +L2RCOP-PDUs are transferred to the peer L2RCOP entity using the data transfer services of the radio link. + +### A.3.3 Status Transfer + +The L2RCOP entity transfers interface status information between L2Rs using bits SA, SB and X in the status octets in L2RCOP-PDUs. Status changes are inserted in the L2RCOP-PDU in the position corresponding to the position in the character stream that the interface status change occurred. When the RLP is established or reset a L2RCOP-PDU with the current status values shall be sent. + +The general mapping between ITU-T V.24 [19] interface circuit numbers and status bits is described in annex C. A binary 0 corresponds to the ON condition, a binary 1 to the OFF condition. The specific mapping at the MT for the non-transparent bearer service is given in subclause 4.2.1. The mapping schemes used at the IWF are given in 3GPP TS 29.007 [13]. + +### A.3.4 Flow Control + +Flow control information is transferred between L2Rs in 2 ways, these are: + +- back pressure caused by L2R buffer conditions. +- use of the X-bit in status octets: + - flow control active, X-bit = ONE. + - flow control inactive, X-bit = ZERO. + +### A.3.5 Break + +The transfer of break conditions between L2Rs is via the status octets with appropriate coding of the address field. Where the "Break Signal" is generated it shall conform to the definition shown in ITU-T Recommendation X.28 [28]. + +#### A.3.5.1 Normal Realization + +The L2RCOP-PDU contains the mandatory status octet coded as the Destructive Break. + +Upon the receipt of the "Break Signal", the L2R shall destroy any existing data in front of the Break Signal in the same direction, and all the buffered data in the other direction. The L2R shall then pass the Break Signal immediately on. + +The termination of a break condition is indicated by sending an L2RCOP-PDU containing characters. + +#### A.3.5.2 Realization in case of Data Compression is used + +If the data compression function is used L2RCOP has to ensure the synchronization of the encoder and decoder according to ITU-T Recommendation V.42bis [26]. + +Upon receipt of a L2RCOP-PDU containing a status octet that signals a Destructive Break L2R destroys all data in the TX and RX buffer and re-initializes the compression function. Then L2R shall transmit an L2RCOP-PDU that contains the mandatory status octet coded as the Destructive Break Acknowledge. After that L2R shall restart the data transfer. + +Upon an receipt of the "Break Signal" by the CONTP, the L2R destroys any existing data in the TX and RX buffer and shall then pass the Break Signal immediately by using L2RCOP-PDU containing a status octet coded as the Destructive Break. L2R shall wait for a L2RCOP-PDU containing a mandatory status octet coded as Destructive Break Acknowledge. Following data received by the CONTP shall be stored in the TX buffer. Data received in L2RCOP-PDUs shall be discarded. After reception of the L2RCOP-PDU containing a mandatory status octet coded as Destructive Break Acknowledge L2R shall re-initialize the data compression function and restart the data transfer. + +# Annex B (informative): Use of a 9 pin connector as an MT2 type interface + +For asynchronous data communications many of the physical pins on a standard 25 pin D-type connector (ISO 2110 [31]) are not used. As a result many communication devices have only a 9 pin connector to allow them to be made smaller. This interface is a MT2 type providing the correct ITU-T Recommendation V.24 [19] signals are supported. + +Table B1 gives the pin assignments for a 9 pin connector. Two variants are permitted: + +## 1. Outband flow control + +When outband (CT 133) flow control is required, pin number 7 carries CT 133 (Ready for Receiving). In this case CT 105 is not mapped to any physical pin. On the MT2 side of the interface, CT 105 is treated as being always in the ON condition. + +## 2. No outband flow control + +When no outband (CT 133) flow control is required, pin number 7 may carry CT 105 (Request to Send). In this case CT 133 is not mapped to any physical pin. On the MT2 side of the interface, CT 133 is treated as being always in the ON condition. + +**Table B1: Interchange circuit mappings** + +| ITU-T V.24 [19] Circuit Number | Circuit Name | Pin Number | +|-------------------------------------------------------------|---------------|------------| +| CT 102 | Common ground | 5 | +| CT 103 | TxD | 3 | +| CT 104 | RxD | 2 | +| CT 105 | RTS | 7 (note) | +| CT 106 | RFS (CTS) | 8 | +| CT 107 | DSR | 6 | +| CT 108/2 | DTR | 4 | +| CT 109 | DCD | 1 | +| CT 125 | CI | 9 | +| CT 133 | RFR | 7 (note) | +| NOTE: Only one of these mappings may exist at any one time. | | | + +# Annex C (informative): General mapping of ITU-T V.24 [19] circuits to channel status bits + +In the data transfer state, status bits SA, SB and X can be used to convey channel control information associated with the data bits. Table C1 shows the general mapping scheme between the ITU-T V.24 [19] circuit numbers and the status bits. A binary 0 corresponds to the ON condition, a binary 1 to the OFF condition. The specific mappings for the various PLMN bearer types are given elsewhere in the present document. + +**Table C1: General mapping scheme at the MT** + +| Signal at TE2/MT interface | Status bit direction: MT to IWF | Status bit direction: IWF to MT | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|---------------------------------| +| CT 105 (note 3) | SB | | +| CT 106 (note 1) | | X | +| CT 107 | | SA | +| CT 108/2 | SA | | +| CT 109 | | SB | +| CT 133 (note 3) | X (note 2) | | +| NOTE 1: The condition of CT 106 may also be affected by the state of any transmit buffer in the MT. | | | +| NOTE 2: The condition of Status bit X towards the IWF may also be affected by the state of any receive buffer in the MT. | | | +| NOTE 3: CT105 and CT133 are assigned to the same connector pin on both the standard 25 pin connector (ISO 2110) and the commonly used 9 pin connector (annex B). When this pin is used for CT133 then on the MT side of the interface CT 105 is treated as being always in the ON condition. SB towards the IWF shall therefore also always be ON. Similarly, when this pin is being used for CT105 then on the MT side of the interface CT 133 is treated as being always in the ON condition. X towards the IWF shall therefore also always be ON. As circuit 133 is used only in duplex operation and circuit 105 is used only in half duplex operation (which is not supported by GSM or UMTS) there should be no conflict. | | | + +# Annex D (informative): Change history + +| Change history | | | | | | | | +|----------------|----------|-----------|-----|-----|--------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| | Apr 1999 | | | | Transferred to 3GPP CN1 | 7.0.0 | | +| | CN#03 | | | | Approved at CN#03 | | 3.0.0 | +| | CN#04 | | 001 | | Introduction of EDGE channel codings into the specifications [E-mail approval] | 3.0.0 | 3.1.0 | +| | CN#06 | | 002 | | Service clean-up for Release 99 | 3.1.0 | 3.2.0 | +| | CN#07 | | 003 | | UMTS Clean Up | 3.2.0 | 3.3.0 | +| | CN#08 | | 004 | | Adaptations for UMTS | 3.3.0 | 3.4.0 | +| | CN#09 | | 007 | | Modification from V.25bis to V.250 | 3.4.0 | 4.0.0 | +| 12-2001 | CN#14 | NP-010604 | 008 | 3 | Terminology Clarifications requested by TSG GERAN | 4.0.0 | 5.0.0 | +| 12-2004 | CN#26 | | | | Upgraded to v6.0.0 | 5.0.0 | 6.0.0 | +| 06-2007 | CT#36 | | | | Upgraded to v7.0.0 | 6.0.0 | 7.0.0 | +| 12-2008 | CT#42 | | | | Upgraded to v8.0.0 due to simple upgrade without no technical change | 7.0.0 | 8.0.0 | +| 12-2009 | CT#46 | | | | Automatic upgrade from previous Release | 8.0.0 | 9.0.0 | +| 12-2010 | CT#50 | CP-100779 | 010 | 1 | Correcting non-specific external references | 9.0.0 | 9.1.0 | +| 03-2011 | CT#51 | | | | Automatic upgrade from previous Release version 9.1.0 | 9.1.0 | 10.0.0 | +| 03-2011 | CT#51 | | | | Correction of heading and numbering made by MCC | 10.0.0 | 10.0.1 | +| 09-2012 | CT#57 | | | | Automatic upgrade from previous Release version 10.0.1 | 10.0.1 | 11.0.0 | \ No newline at end of file diff --git a/marked/Rel-11/27_series/27003/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/Rel-11/27_series/27003/dbe553cf16dd14073b89a8263a428664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bca5829ccc624190bc7c68aaf0840a2281f5004 --- /dev/null +++ b/marked/Rel-11/27_series/27003/dbe553cf16dd14073b89a8263a428664_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:448243cb504871ece913ceaf19c0ba43a9dee8306797e0cba776dfa5cbe10782 +size 15399 diff --git a/marked/Rel-11/27_series/27003/e1a0d046fbe7f28f5e93a47091851747_img.jpg b/marked/Rel-11/27_series/27003/e1a0d046fbe7f28f5e93a47091851747_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f992b36bdfe05e150f64671fa0c58c40dd5a6fd8 --- /dev/null +++ b/marked/Rel-11/27_series/27003/e1a0d046fbe7f28f5e93a47091851747_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06f5e35ab3375760e7267e9d7cb0d4196e18259daf91be12ce60673f76477497 +size 26819 diff --git a/marked/Rel-11/27_series/27003/raw.md b/marked/Rel-11/27_series/27003/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1449203a8765c0b4a682818608b56ab5b0e32693 --- /dev/null +++ b/marked/Rel-11/27_series/27003/raw.md @@ -0,0 +1,489 @@ + + + + + + +# Contents + +| | | +|----------------------------------------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 2.1 Abbreviations ..... | 7 | +| 2.2 Definitions..... | 7 | +| 3 General..... | 7 | +| 3.1 Customer access configuration..... | 7 | +| 3.2 Terminal Adaptation Function ..... | 8 | +| 3.3 TAF Interfacing to other MT functions..... | 8 | +| 4 Terminal Adaptation Functions for synchronous transparent services..... | 8 | +| 4.1 Rate Adaptation in A/Gb mode..... | 9 | +| 4.1.1 Rate adaptation - ITU-T V-series ..... | 9 | +| 4.1.2 Rate adaptation - ITU-T X.21 ..... | 9 | +| 4.1.3 Rate adaptation - ITU-T S-interface..... | 9 | +| 4.2 Interchange Circuit Signalling Mapping ..... | 9 | +| 4.2.1 ITU-T V-series interchange circuit mapping..... | 9 | +| 4.2.1.1 Multislot configurations (Channel coding TCH/F9.6 or TCH/F4.8 kbit/s)..... | 11 | +| 4.2.1.2 Channel coding TCH/F14.4 and TCH/F28.8 ..... | 12 | +| 4.2.2 ITU-T X.21 [23] Interchange circuit mapping ..... | 12 | +| 4.2.3 Case of ITU-T S-interface ..... | 12 | +| 4.3 Call establishment signalling mapping at TE/MT interface..... | 12 | +| 4.3.1 ITU-T V-series interfaces..... | 12 | +| 4.3.1.1 Call establishment manual operation - utilizing Alternate Speech/Data or Speech followed by Data Capabilities..... | 12 | +| 4.3.1.2 Call establishment manual operation - utilizing the Unrestricted Digital Capability ..... | 12 | +| 4.3.1.3 ITU-T V.25bis [18] auto call/auto answer..... | 12 | +| 4.3.2 ITU-T X-series interfaces..... | 13 | +| 4.3.3 ITU-T S-interface (ITU-T I.420 [11]) signalling mapping ..... | 13 | +| 4.3.4 X.25 Procedures Mapping..... | 13 | +| 5 Terminal Adaptation Functions for synchronous non-transparent services..... | 13 | +| 6 V-series interface procedures to 3GPP TS 24.008 [7] mapping ..... | 14 | +| 6.1 Mobile Originated calls..... | 14 | +| 6.2 Mobile Terminated calls..... | 14 | +| 7 ITU-T X.21 [23] interface procedures to 3GPP TS 24.008 [7] mapping ..... | 15 | +| 8 Support for packet service..... | 15 | +| Annex A (normative): L2R Functionality ..... | 16 | +| Annex B (informative): Change history..... | 17 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document defines the interfaces and Terminal Adaptation Functions (TAF) integral to a Mobile Termination (MT) which enables the attachment of synchronous terminals to a MT 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 defines Terminal Adaptation Functions (TAF) which are integrated in a Mobile Termination (MT) and which enable the use of synchronous bearer services in the PLMN and the attachment of Synchronous terminals to an MT (see 3GPP TS 24.002 [3]). For the case where asynchronous terminals are attached to the TAF when using synchronous bearer services in the PLMN, the reader is referred to 3GPP TS 27.002 [36] for the asynchronous MT-TAF interface specifics and to the present document for synchronous bearer service specifics on the TAF-IWF interface. The general aspects of Terminal Adaptation Functions are contained in specification 3GPP TS 27.001 [9]. The present document covers support of synchronous data services (see 3GPP TS 22.002 [6]) for the following interfaces and procedures: + +- V.22 [15] DTE/DCE Interface; +- V.22 bis [16] DTE/DCE Interface; +- V.26 ter [19] DTE/DCE Interface; +- X.21 bis [24] DTE/DCE Interface; +- X.32 [30] Procedure; +- V.25 bis [18] Procedure; + +NOTE: From R99 onwards the support of the following services are no longer required by a PLMN: + +- the dual Bearer Services "alternate speech/data" and "speech followed by data"; +- the dedicated services for PAD and Packet access; +- BS 21 ... 26 and BS 31 ... 34. + +From REL-4 onwards the support of the following service is no longer required by a PLMN: + +- the synchronous Bearer Service non-transparent (BS 30 NT). +- the Teleservice Facsimile non-transparent (TS 61/62 NT) for A/Gb mode. + +The support of these services is still optional. The specification of these services is not within the scope of the present document. For that, the reader is referred to GSM R98 or R99 respectively. + +NOTE: Please note that the Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used. GERAN Iu mode is for further study. + +# --- 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] Void +- [2] 3GPP TS 43.010: "GSM Public Land Mobile Network (PLMN) connection types". +- [3] 3GPP TS 24.002: "GSM - UMTS Public Land Mobile Network (PLMN) access reference configuration " + +- [4] 3GPP TS 44.021: "Rate adaption on the Mobile Station - Base Station System (MS - BSS) interface". +- [5] 3GPP TS 08.20: "Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". +- [6] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by Public Land Mobile Network (PLMN)". +- [7] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols-Stage 3". +- [8] Void. +- [9] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". +- [10] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications ". +- [11] ITU-T Recommendation I.420 (1998): "Basic user-network interface". +- [12] Void. +- [13] Void. +- [14] Void. +- [15] ITU-T Recommendation V.22 (1988): "1200 bits per second duplex modem standardized for use in the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [16] ITU-T Recommendation V.22 bis (1988): "2400 bits per second duplex modem using the frequency division technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [17] ITU-T Recommendation V.24 (1996):"List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE)". +- [18] ITU-T Recommendation V.25 bis (1996): "Synchronous and asynchronous automatic dialling procedures on switched networks". +- [19] ITU-T Recommendation V.26 ter (1988): "2400 bits per second duplex modem using the echo cancellation technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits". +- [20] ITU-T Recommendation V.28 (1993): "Electrical characteristics for unbalanced double-current interchange circuits". +- [21] Void. +- [22] ITU-T Recommendation V.110 (1996): "Support of data terminal equipments with V-Series interfaces by an integrated services digital network". +- [23] Void. +- [24] Void. +- [25] Void. +- [26] Void. +- [27] Void. +- [28] Void. +- [29] Void. + +- [30] ITU-T Recommendation X.32 (1996): "Interface between Data terminal Equipment (DTE) and Data Circuit-terminating Equipment (DCE) for terminals operating in packet mode and accessing a Packet-Switched Public Data Network through a public switched telephone network or an Integrated Services Digital Network or a Circuit-Switched Public Data Network". +- [31] Void. +- [32] Void. +- [33] Personal Computer Memory Card Association: "PCMCIA 2.1 or PC-Card 3.0 electrical specification or later revisions". +- [34] Infrared Data Association IrDA: "IrPHY Physical layer signalling standard". +- [35] Void. +- [36] 3GPP TS 27.002: "Terminal adaptation functions (TAF) for services using asynchronous bearer capabilities". + +## 2.1 Abbreviations + +In addition to the abbreviations listed below, the present document also uses terms listed in 3GPP TR 21.905 [10]. + +| | | +|-------|----------------------------------------------| +| IrDA | Infrared Data Association | +| IrPHY | Infrared Physical layer | +| ITU-T | ITU-Telecommunication Standardization Sector | +| MUX | Multiplexer | + +## 2.2 Definitions + +The term 'mobile station' (MS) in the present document is synonymous with the term 'user equipment' (UE) as defined in 3GPP TR 21.905[10]. + +The term 'TE2' in the present document is synonymous with the term 'TE' as defined in 3GPP TR 21.905[10]. + +The term 'MT2' in the present document is synonymous with the term 'MT' as defined in 3GPP TR 21.905[10]. + +For the purposes of the present document the following internal definitions apply in addition to those given in 3GPP TS 21.905[10]. + +**A/Gb mode:** indicates that the text applies only to a system or sub-system which operate in A/Gb mode of operation, i.e. with a functional division that is in accordance with the use of an A or a Gb interface between the radio access network and the core network + +**Iu mode:** indicates that the text applies only to a system or a sub-system which operates in Iu mode of operation, i.e. with a functional division that is in accordance with the use of an Iu-CS or Iu-PS interface between the radio access network and the core network + +# --- 3 General + +## 3.1 Customer access configuration + +The PLMN access reference configuration is described in figure 1 of 3GPP TS 24.002 [3] and 3GPP TS 27.001 [9]. The present document specifically refers to the MTs which support terminal equipments (TE1 or TE2) that use synchronous bearer capabilities. + +## 3.2 Terminal Adaptation Function + +The TAF is functionally part of an MT0, MT1 or MT2 (see 3GPP TS 24.002 [3]). The terminal adaptation provides facilities to allow manual or automatic call control functions associated with circuit switched data services, in case of ITU-T V series interfaces. The following functions are included: + +- conversion of electrical, mechanical, functional and procedural characteristics of the ITU-T V-series, type interfaces to those required by a PLMN; +- bit rate adaptation of ITU-T V-series and ITU-T X-series data signalling rates and the ISDN 64 kbit/s to that provided in an A/Gb mode PLMN; +- the mapping of ITU-T V.25 bis [18] AUTO CALL/AUTO ANSWER procedures to the PLMN Layer 3 signalling; +- the mapping functions necessary to convert ITU-T S-interface signalling to PLMN Layer 3 signalling; +- synchronization procedure, which means the task of synchronizing the entry to and the exit from the data transfer phase between two subscriber terminals. This is described in the specification 3GPP TS 27.001 [9]; +- filtering of channel control information. This is described in the specification 3GPP TS 27.001 [9]; +- compatibility checking (see 3GPP TS 27.001 [9]); +- flow control; +- in Call Modification function (see clause 4); +- splitting and combining of the data flow in case of multi substream data configurations. + +## 3.3 TAF Interfacing to other MT functions + +TAF interfacing is shown in figure 1. + +![Diagram showing TAF interfacing to other MT functions. The central TAF block is connected to Mobility Management, RR Management, and Channel Codec (with FEC) on the right, and to MMI and Call Control on the bottom.](e1a0d046fbe7f28f5e93a47091851747_img.jpg) + +``` + +graph LR + TAF[TAF] --- MM[Mobility Management] + TAF --- RR[RR Management] + TAF --- CC[Channel Codec] + CC --- FEC[FEC] + TAF --- MMI[MMI] + TAF --- CallControl[Call Control] + +``` + +Diagram showing TAF interfacing to other MT functions. The central TAF block is connected to Mobility Management, RR Management, and Channel Codec (with FEC) on the right, and to MMI and Call Control on the bottom. + +**Figure 1: TAF interfacing to other MT functions** + +# 4 Terminal Adaptation Functions for synchronous transparent services + +Specification 3GPP TS 43.010 [2] refers to the models for connection types supporting synchronous transparent services. + +## 4.1 Rate Adaptation in A/Gb mode + +Rate adaptation on the MS-BS interface is described in 3GPP TS 44.021[4]. The synchronous data services make use of the following rate adaptation functions: RA1, RA2, RA1/RA1', RA1' and in case of TCH/F28.8 usage, EDGE-MUX. See also figures 6, 7 and 8 in 3GPP TS 43.010 [2]. The D-bits of the rate adaptation frames are used to convey user data. The S- and X-bits are used to convey channel status information associated with the data bits in the data transfer + +state, or to carry substream numbering between the Split/Combine functions in case of mult substream operation. For the S- and X-bits, a ZERO corresponds to the ON condition, a ONE to the OFF condition. + +### 4.1.1 Rate adaptation - ITU-T V-series + +This is provided as indicated in specification 3GPP TS 44.021 [4]. The functions applied in this case are shown in figure 2 (see model 2b in figures 6, 7 and 8 of 3GPP TS 43.010 [2]). + +![Diagram showing the connection between TE2 V-series and MT2 via interface circuits at reference point R.](dbe553cf16dd14073b89a8263a428664_img.jpg) + +``` + ++-------------+ +-----------------+ +| TE2 | Interface circuits | MT2 | +| V-series | (data and control) | +---------+ | ++------+------+----------------------+---| RA1' | | + | | +---------+ | + | R +-----------------+ + +--------------+--------------+ + +``` + +Diagram showing the connection between TE2 V-series and MT2 via interface circuits at reference point R. + +**Figure 2: Rate adaptation for V-series terminals** + +### 4.1.2 Rate adaptation - ITU-T X.21 + +Void. + +### 4.1.3 Rate adaptation - ITU-T S-interface + +Void. + +## 4.2 Interchange Circuit Signalling Mapping + +### 4.2.1 ITU-T V-series interchange circuit mapping + +The interchange circuit signalling mapping at the interface between the TE2 and the MT shall conform to ITU-T recommendation V.24 [17]. The signal levels at the interface shall conform either to ITU-T recommendation V.28 [20], or to IrDA IrPHY Physical signalling standard specification [34], or to PCMCIA 2.1 [33], or to PC-Card 3.0 [33] electrical specifications or to later revisions. + +The signals required at this interface are shown in table 2. + +- Specification 3GPP TS 44.021 [4] refers to the frame structure and identifies the use of status bits for the carriage of signalling information. + +Status bits SA, SB and X are used to convey channel control information associated with the data bits in the data transfer state. Table 1 shows the mapping scheme between the ITU-T V.24 [17] circuit numbers and the status bits for the transparent mode. It also shows how the unused status bits should be handled. It is derived from the general mapping scheme described in annex C. A binary 0 corresponds to the ON condition, a binary 1 to the OFF condition. + +The transport of these status bits by the various channel codings is described in subsequent sections. + +**Table 1: Mapping scheme at the MT for the transparent mode** + +| Signal at TE2/MT interface or condition within the MT | Mapping direction: MT to IWF | Mapping direction: IWF to MT | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------------------| +| CT 105 | not mapped (note 1) | | +| CT 106 | | from status bit X (note 7) | +| CT 107 | | not mapped (note 5) | +| CT 108/2 | not mapped (note 6) | | +| CT 109 | | from status bit SB (note 7) | +| CT 133 | not mapped (note 2) | | +| always ON | to status bit SA (note 3) | | +| always ON | to status bit SB (note 1) | | +| always ON | to status bit X (note 4) | | +| ignored by MT | | from status bit SA (note 3) | +| NOTE 1: The SB bit towards the IWF, according to the General Mapping (3GPP TS 27.002, annex C), could be used to carry CT 105. However, CT 105 should always be ON in the data transfer state since only duplex operation is supported. Also, many DTEs use the connector pin assigned to CT 105 for CT 133. No interchange circuit shall be mapped to the SB bit which shall always be set to ON in the data transfer state. | | | +| NOTE 2: CT 133 is not mapped since there is no flow control in transparent mode. | | | +| NOTE 3: The SA bits in both directions are available only with certain channel codings. Therefore, for maximum compatibility, they should not be mapped. | | | +| NOTE 4: The X bit towards the IWF is not mapped and shall always be set to ON in the data transfer state since there is no flow control in transparent mode. | | | +| NOTE 5: CT 107 is controlled by the channel synchronization process (3GPP TS 27.001 [9]). | | | +| NOTE 6: CT 108/2 may be used in the call setup and answering processes. | | | +| NOTE 7: The status bits are filtered before being mapped to the ITU-T V.24 [17] circuits (3GPP TS 27.001 [9]). | | | + +**Table 2: Minimum set of V-series interchange circuits** + +| Circuit Number | Circuit Name | Ground | Data | | Control | | +|---------------------------------------------------------------|--------------------------------------------|--------|--------|----------|---------|----------| +| | | | to TE2 | from TE2 | to TE2 | from TE2 | +| CT102 | Common Return | X | | | | | +| CT103 | Transmitted data | | | X | | | +| CT104 | Received data | | X | | | | +| CT105 | Request to send | | | | | X | +| CT106 | Ready for sending | | | | X | | +| CT107 | Data set ready | | | | X | | +| CT108.2 | Data terminal ready | | | | | X | +| CT109 | Data channel received line signal detector | | | | X | | +| CT114 | Transmitter signal element timing | | | | X | | +| CT115 | Receiver signal element timing | | | | X | | +| CT125 | Calling indicator (note) | | | | X | | +| NOTE: CT125 is used with the AUTO ANSWER function of the TAF. | | | | | | | + +#### Use of Network Independent Clocking (applicable to A/Gb mode PLMN only): + +Network Independent Clocking is only applicable to calls using ITC value "3.1 kHz audio ex PLMN". + +Within the **A/Gb mode PLMN** the coding of the values for bits associated with NIC is specified in 3GPP TS 44.021 [4] and 3GPP TS 08.20 [5]. In the forward (transmitting) direction the multiframes shall be coded in exact accordance with that specified in those specifications. Bit E6 is set to "1" in alternate modified ITU-T V.110 [22] frames at the transmitter. However, the use of this bit at the receiver for monitoring frame Synchronization, or any other purpose, is not specified and is left to the discretion of the implementor. + +A "perfect linear block Code" is used in C1-C5, whose error correction properties may be utilized in the receiver, in order to ensure reliable operation of NIC. + +The NIC sending function has to recognize when the difference between the applicable clock speed of the **A/Gb mode PLMN** and the interface speed generates a positive or negative whole bit requirement. When this positive or negative condition occurs, the NIC codewords specified in specification 3GPP TS 44.021 [4] are used to transport this condition to the receiving NIC function. Transmission of the codeword shall clear the positive or negative condition related to that codeword at the sending function. The sending function shall not send more than one positive or negative compensation within a contiguous period of time corresponding to 10 000 user data bits minus the number of user data bits necessary to make up an even number of ITU-T V.110 [22] frames. Between compensations (NIC compensation is coded in two ITU-T V.110 [22] frames). This results from the requirements to compensate for maximum clock differences of $\pm 100$ parts per million. If the receiving function receives NIC compensations more often than a contiguous period of time corresponding to 10 000 user data bits, there is no guarantee that data will not be lost. + +The NIC receiving function has to provide the capability to support the compensation requirements of the sending function. This compensation is managed by manipulating the clock speed of the interface, within the standard constraints of that interface. + +Overall, the compensation functions have to be capable of managing clock tolerances of $\pm 100$ parts per million. + +The NIC function has to recognize and manage the conversion of the NIC information received incoming from an ISDN terminal Interface. The conversion has to be made to the NIC format used within the **A/Gb mode PLMN** System as defined in specifications 3GPP TS 44.021 [4] and 3GPP TS 08.20 [5]). The NIC function has to manage the conversion of the PLMN NIC format into that used within the ISDN in the traffic direction towards the ISDN terminal interface. + +Due to the incompatibility between the ISDN and the **A/Gb mode PLMN** requirements NIC interworking is nor provided between these two formats. as such no NIC function is required in providing interworking to the ISDN for unrestricted digital. + +#### Action on loss of synchronization: + +If five consecutive NIC multiframes have incorrect framing bit values in E7, the receiver shall stop applying clocking compensation to the received data. Resynchronization shall be attempted and compensation shall resume when synchronization is achieved. + +#### Signal element timing: + +Receiver signal element timing (CT115) is generated by MT2. In the **A/Gb mode PLMN** transparent case, this shall be synchronized to the output of RA1' function. In the UTRAN Iu mode transparent case, this shall be synchronized to output of the RLC. A transition from ON to OFF condition shall nominally indicate the centre of each signal element on CT104. + +Transmitter signal element timing is generated by MT2 (CT114), this may be synchronized to CT115. + +In the case of alternate Speech/Group 3 Facsimile, there may be a Channel Mode Modify during the course of the facsimile portion of the call. If this occurs, the user data rate changes and this is reflected to the ITU-T V.24 [17] interface as a change in the clock speed on CT 114 and CT 115. + +#### 4.2.1.1 Multislot configurations (Channel coding TCH/F9.6 or TCH/F4.8 kbit/s) + +In transparent multislot configurations status bits S1, S3 and the X-bit between the D12 and D13 in the ITU-T V.110 [22] 80-bit intermediate rate frame - are used for transferring substream numbering information. The S4-bit is used for frame synchronization between the parallel substreams (ref 3GPP TS 44.021[4]). + +#### 4.2.1.2 Channel coding TCH/F14.4 and TCH/F28.8 + +For information on the mapping of the interchange circuit signalling bits in the 14,5 multiframe structure, refer to 3GPP TS 44.021 [4]. + +### 4.2.2 ITU-T X.21 [23] Interchange circuit mapping + +Void. + +### 4.2.3 Case of ITU-T S-interface + +Void. + +## 4.3 Call establishment signalling mapping at TE/MT interface + +### 4.3.1 ITU-T V-series interfaces + +#### 4.3.1.1 Call establishment manual operation - utilizing Alternate Speech/Data or Speech followed by Data Capabilities + +Void. + +#### 4.3.1.2 Call establishment manual operation - utilizing the Unrestricted Digital Capability + +In this case the user shall not hear network supervisory tones or answer tone. The data transfer phase shall be entered automatically. + +#### 4.3.1.3 ITU-T V.25bis [18] auto call/auto answer + +The mapping of the ITU-T V.25bis [18] procedures to the messages of the PLMN Layer 3 signalling (3GPP TS 24.008 [7]) is defined in clause 4. + +##### **Auto Call:** + +This procedure is provided according to ITU-T V.25bis [18] using only circuit 108/2. A subset of ITU-T V.25bis [18] is shown in table 4. This subset gives minimum level of control and indication. + +During the call establishment phase, i.e. after signalling, call tone according to ITU-T V.25 bis [18] shall be generated in the IWF, where appropriate. + +##### **Auto Answer:** + +This procedure is provided according to ITU-T V.25bis [18]. + +**Table 4: Minimum set of ITU-T V.25bis [18] Call Set-up Commands and Indications** + +| | Description | IA5Characters | +|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------| +| Commands from TE2 | Call R equest with N umber provided 0,1..9,*,#,A,B,C,D
Disregard I ncoming C all
Connect I ncoming C all | CRN
DIC
CIC | +| Indications to TE2 | Call F ailure I ndication
XX = CB,AB,NT,FC (Note)
I ncoming C all
V ALid
I NVal i id | CFI XX
INC
VAL
INV | + +NOTE to table 4: CB = Local MT busy +AB = Abort call +NT = No answer +FC = Forbidden call (\*) + +(\*) Forbidden call indication results from contravention of rules for repeat call attempts as defined by the appropriate national approval administration. It is recommended that this is the responsibility of the MT, not the TE2. + +### 4.3.2 ITU-T X-series interfaces + +Void. + +### 4.3.3 ITU-T S-interface (ITU-T I.420 [11]) signalling mapping + +Void. + +### 4.3.4 X.25 Procedures Mapping + +Void. + +# --- 5 Terminal Adaptation Functions for synchronous non-transparent services. + +Void. + +# 6 V-series interface procedures to 3GPP TS 24.008 [7] mapping + +Interface procedures not directly mappable to 3GPP TS 24.008 [7] (ie. ITU-T V.25 bis [18] VAL/INV) are not considered. Mobile management procedures of 3GPP TS 24.008 [7] are not considered applicable. + +Mapping of other call establishment or clearing messages to the S interface e.g. "Call proceeding", etc. have not been included. It is assumed that these may be mapped directly and thus are of no relevance to the ITU-T V.25 bis [18] or manual interface. + +## 6.1 Mobile Originated calls + +a) SET-UP. + +| Element | Derived from | | +|----------------|--------------------------------------------------------|-----------------------------| +| | MMI | ITU-T V.25 bis [18] message | +| Called Address | Keypad | CRN/CRI/CRS | +| Called | Keypad | CRI | +| Sub Address | | | +| HLC | Derived from internal settings or MMI information. | | +| LLC | Same as HLC | | +| BC | Same as HSC
3GPP TS 27.001 [9] gives allowed values | | + +b) RELEASE COMPLETE. + +| Element | Derived from | | +|---------|--------------------|-----------------------------| +| | MMI | ITU-T V.25 bis [18] message | +| Cause | Display (optional) | CFI | + +## 6.2 Mobile Terminated calls + +Call establishment is initiated by receipt of Setup at the MS: + +a) SET-UP. + +| Element | Mapped on to | | +|----------------|--------------------|-----------------------------| +| | MMI | ITU-T V.25 bis [18] message | +| Called Address | Display (optional) | INC | +| Called | Display (optional) | Not applicable | +| Sub Address | | | +| HLC | Display (optional) | Not applicable | +| LLC | Display (optional) | Not applicable | +| BC | Display (optional) | Not applicable | + +b) CALL CONFIRM. + +Information for the BC element in the call confirm is derived from e.g. MMI or by internal settings. + +c) CONNECT. + +Connect is sent in response, CIC from ITU-T V.25 bis [18] or in response from MMI. + +# 7 ITU-T X.21 [23] interface procedures to 3GPP TS 24.008 [7] mapping + +Void. + +# --- 8 Support for packet service + +Void. + +# --- Annex A (normative): L2R Functionality + +Void + +# Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|-----|-----|--------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 04-1999 | | | | | Transferred to 3GPP CN1 | 6.0.0 | | +| | CN#03 | | | | Approved at CN#03 | | 3.0.0 | +| | CN#04 | | 001 | | Introduction of EDGE | 3.0.0 | 3.1.0 | +| | CN#06 | | 002 | | Introduction of Asynchronous interface for Real-time non-transparent FAX | 3.1.0 | 3.2.0 | +| | CN#06 | | 003 | | R99 service clean-up (also subclause 8.3 removed) | 3.1.0 | 3.2.0 | +| | CN#07 | | 004 | | UMTS clean up | 3.2.0 | 3.3.0 | +| | CN#08 | | 005 | | Adaptations for UMTS | 3.3.0 | 3.4.0 | +| | CN#09 | | 006 | | Modification from V.25bis to V.250 | 3.4.0 | 3.5.0 | +| | CN#10 | | 007 | | Removal of BS 30 NT | 3.5.0 | 4.0.0 | +| 03-2001 | TSG#11 | NP-010046 | 008 | | Removal of Fax NT in GSM from Rel-4 | 4.0.0 | 4.1.0 | +| 12-2001 | TSG#14 | NP-010604 | 009 | | Terminology clarifications as requested by TSG GERAN | 4.1.0 | 5.0.0 | +| 12-2004 | CN#26 | | | | Upgraded to v6.0.0 | 5.0.0 | 6.0.0 | +| 06-2007 | CT#36 | | | | Upgraded to v7.0.0 | 6.0.0 | 7.0.0 | +| 12-2008 | CT#42 | | | | Upgraded to v8.0.0 due to simple upgrade without no technical change | 7.0.0 | 8.0.0 | +| 12-2009 | CT#46 | | | | Automatic upgrade from previous Release | 8.0.0 | 9.0.0 | +| 03-2011 | CT#51 | | | | Automatic upgrade from previous Release version 9.0.0 | 9.0.0 | 10.0.0 | +| 03-2011 | CT#51 | | | | Correction of heading and numbering made by MCC | 10.0.0 | 10.0.1 | +| 09-2012 | CT#57 | | | | Automatic upgrade from previous Release version 10.0.1 | 10.0.1 | 11.0.0 | \ No newline at end of file diff --git a/marked/Rel-11/27_series/27005/21d8ca19de468e733e521605b1890767_img.jpg b/marked/Rel-11/27_series/27005/21d8ca19de468e733e521605b1890767_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad3cafbb39efbc34a2a3b9ac015d63a682a2d961 --- /dev/null +++ b/marked/Rel-11/27_series/27005/21d8ca19de468e733e521605b1890767_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15024723c047d48b0da2624d6c38dcb1f414eecc53fa26152e2ced84aa7b51fe +size 38439 diff --git a/marked/Rel-11/27_series/27005/34f788b0e5bc8af774fa5561c22e6d01_img.jpg b/marked/Rel-11/27_series/27005/34f788b0e5bc8af774fa5561c22e6d01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa12a3fdfcfb4a68fce485363ca4b6d7af703f7d --- /dev/null +++ b/marked/Rel-11/27_series/27005/34f788b0e5bc8af774fa5561c22e6d01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:263a79b648175ec22c105f9718f0bc3bbeeba88628eeafb58a5c8e69931ac997 +size 28713 diff --git a/marked/Rel-11/27_series/27005/376f80eb8a41369e87da63a0210d173e_img.jpg b/marked/Rel-11/27_series/27005/376f80eb8a41369e87da63a0210d173e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..776f3c9ff90d484120573e252ff69866da85441b --- /dev/null +++ b/marked/Rel-11/27_series/27005/376f80eb8a41369e87da63a0210d173e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:546f4b1462f3e98864b8e1dea92046b7265e6b61b2d9edda0a2b8f69d7b0700d +size 139793 diff --git a/marked/Rel-11/27_series/27005/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-11/27_series/27005/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d373f53f95ae7322d0e721a8a8f5f5bb083db900 --- /dev/null +++ b/marked/Rel-11/27_series/27005/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93964ae4fa79430c171ef8e8dd5e595a7d612e1649158c0fddc26754b35611a2 +size 54521 diff --git a/marked/Rel-11/27_series/27005/4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg b/marked/Rel-11/27_series/27005/4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bd486711e618f37b5616725c23dbeedfeb69621 --- /dev/null +++ b/marked/Rel-11/27_series/27005/4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f67b5b8d13a845224f955bbb914693f9d1d5d6bd0fad5eae958849bd3364260 +size 51146 diff --git a/marked/Rel-11/27_series/27005/536951b2bbd94325ae266d8d1363df8f_img.jpg b/marked/Rel-11/27_series/27005/536951b2bbd94325ae266d8d1363df8f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1d67745b2bcc1946a3e35dac97b27a862737f8a --- /dev/null +++ b/marked/Rel-11/27_series/27005/536951b2bbd94325ae266d8d1363df8f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48af61929bf7f2b34c48b427eac07edb7d582833742b1acc2b3f83763fe2c78c +size 17092 diff --git a/marked/Rel-11/27_series/27005/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-11/27_series/27005/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..460ecf9308967d2fa7b635ff417288c73a33c255 --- /dev/null +++ b/marked/Rel-11/27_series/27005/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2677f7be014a751372a0211b68352163170e807bd740a8043e61d63f97b3f6e8 +size 104832 diff --git a/marked/Rel-11/27_series/27005/583e14835ddabad1d8b92a07b82fc31b_img.jpg b/marked/Rel-11/27_series/27005/583e14835ddabad1d8b92a07b82fc31b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55686aa33a49fbaf67d3a8874a32cc0b4ab9b920 --- /dev/null +++ b/marked/Rel-11/27_series/27005/583e14835ddabad1d8b92a07b82fc31b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4901014fcf68b3b8c37f44c5fc999a01904c595d51a8998b838d89dc86160373 +size 60845 diff --git a/marked/Rel-11/27_series/27005/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/marked/Rel-11/27_series/27005/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e88f3d65655bd5a8756163eedacbf19dc947bc4 --- /dev/null +++ b/marked/Rel-11/27_series/27005/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b033ed9ed9f08bf65f1e4b6286a173ecd31b324eaffcaa43e06c9cd3c132107 +size 6809 diff --git a/marked/Rel-11/27_series/27005/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-11/27_series/27005/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..460ecf9308967d2fa7b635ff417288c73a33c255 --- /dev/null +++ b/marked/Rel-11/27_series/27005/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2677f7be014a751372a0211b68352163170e807bd740a8043e61d63f97b3f6e8 +size 104832 diff --git a/marked/Rel-11/27_series/27005/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg b/marked/Rel-11/27_series/27005/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ffe9d60f7d2c9169d4459a3703bc49a51471bf91 --- /dev/null +++ b/marked/Rel-11/27_series/27005/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0b5012131c5f6467b8785cd16a006da107d07ba92ac5e8b551bd9069ed48454 +size 26888 diff --git a/marked/Rel-11/27_series/27005/6a555cff11e140861ce08db72b01a6a2_img.jpg b/marked/Rel-11/27_series/27005/6a555cff11e140861ce08db72b01a6a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b37231c9515cb1b8c3019fe53f5ffd566260d11 --- /dev/null +++ b/marked/Rel-11/27_series/27005/6a555cff11e140861ce08db72b01a6a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b0dbd9d7e60cc7c7d4c468f90878cec25a567b3748f7f980f6462b1104b8f54 +size 17322 diff --git a/marked/Rel-11/27_series/27005/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg b/marked/Rel-11/27_series/27005/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8be7bebcd10373e43fc50678917036e0acb71de --- /dev/null +++ b/marked/Rel-11/27_series/27005/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46b95a4675accf931929a7f9c96d98056b72daa75dda92cb786f730419e9dc95 +size 138007 diff --git a/marked/Rel-11/27_series/27005/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/Rel-11/27_series/27005/7a0db9703b68b3d06cdaeefc084c0006_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61ecf614b4d528476d11be969146e99011a2b183 --- /dev/null +++ b/marked/Rel-11/27_series/27005/7a0db9703b68b3d06cdaeefc084c0006_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c97decbb6a5c44ae8b889b155a8367f345b29fa83817e2a5a83fa85e1c442c30 +size 19767 diff --git a/marked/Rel-11/27_series/27005/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-11/27_series/27005/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7a8c695a79b9e1e2cf372696bda3e2c4e336fce --- /dev/null +++ b/marked/Rel-11/27_series/27005/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94b6fc06230af663b14443fa328dd866546fb4d7682c932d0793d0b4fd6ed7d9 +size 23454 diff --git a/marked/Rel-11/27_series/27005/965aaf7a8b454893b05799d266de6a69_img.jpg b/marked/Rel-11/27_series/27005/965aaf7a8b454893b05799d266de6a69_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4f5ddc22a560656c8cc0660b105a4936714b3aa --- /dev/null +++ b/marked/Rel-11/27_series/27005/965aaf7a8b454893b05799d266de6a69_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a8798b408815156b8644a6949295df88eef0fce33c08498fb3452f8bdea54fe +size 16641 diff --git a/marked/Rel-11/27_series/27005/977811d1c73b74f801be9f4c376694ca_img.jpg b/marked/Rel-11/27_series/27005/977811d1c73b74f801be9f4c376694ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd526e1e8e1d87573e0aea40cc712cc64cfc21d4 --- /dev/null +++ b/marked/Rel-11/27_series/27005/977811d1c73b74f801be9f4c376694ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b5fca6055f92e9dab7776cd31b285f7c0336a1094c505af042deea5364ff146 +size 26888 diff --git a/marked/Rel-11/27_series/27005/a3083eec2a883ee8327b3c24174df6a9_img.jpg b/marked/Rel-11/27_series/27005/a3083eec2a883ee8327b3c24174df6a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed49762d6cf27fbd1fe3f904504fd8079db6c0da --- /dev/null +++ b/marked/Rel-11/27_series/27005/a3083eec2a883ee8327b3c24174df6a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d1147c6c0ee744a5208b667e9391f3f3dbcfd25fda18af7e42e7a5286f81428 +size 76826 diff --git a/marked/Rel-11/27_series/27005/ad555483986d7170a46ce72d164b5bc8_img.jpg b/marked/Rel-11/27_series/27005/ad555483986d7170a46ce72d164b5bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c62948aff431db484eb50d5689c876acb146c934 --- /dev/null +++ b/marked/Rel-11/27_series/27005/ad555483986d7170a46ce72d164b5bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0a19aab9b64df9a7b3b2cf27a2c84a0b5c71143f4320d00b4579299cc7df527 +size 49647 diff --git a/marked/Rel-11/27_series/27005/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/marked/Rel-11/27_series/27005/b2ea162a0f53d5e0504b7d28346e0754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..100a80f770140f0f1cd393e2dbbb4e837477bff4 --- /dev/null +++ b/marked/Rel-11/27_series/27005/b2ea162a0f53d5e0504b7d28346e0754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29a93410142c5ec208f22b50b4b5fa39558805d489ece92f4e9783cb6e4f0abc +size 18272 diff --git a/marked/Rel-11/27_series/27005/e05122559f56af5699789b7118d8fe87_img.jpg b/marked/Rel-11/27_series/27005/e05122559f56af5699789b7118d8fe87_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..949f3967b5cb3fa73c7b807463059b700f9323c6 --- /dev/null +++ b/marked/Rel-11/27_series/27005/e05122559f56af5699789b7118d8fe87_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bddf6e3b8ee1dbf35b501770e8dd0eb8efa3d4f5771bca2bc7cef1540767555 +size 34756 diff --git a/marked/Rel-11/27_series/27005/raw.md b/marked/Rel-11/27_series/27005/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..df25ce0da752f075f1c9125c0c5deaf3605cd3ab --- /dev/null +++ b/marked/Rel-11/27_series/27005/raw.md @@ -0,0 +1,2859 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 0 Scope..... | 7 | +| 0.1 References ..... | 8 | +| 0.2 Abbreviations ..... | 8 | +| 1 Reference configuration..... | 9 | +| 1.1 V.24 Interface Circuits ..... | 9 | +| 1.1.1 Circuit definitions for the SMS Block mode ..... | 9 | +| 1.1.2 Circuit definitions for the SMS Text and PDU modes..... | 10 | +| 2 SMS Block Mode..... | 10 | +| 2.1 Beginning and ending of SMS/CBS Block Mode..... | 10 | +| 2.1.1 Beginning SMS/CBS Block Mode..... | 10 | +| 2.1.2 Returning from SMS/CBS Block Mode To Default Mode ..... | 11 | +| 2.2 Protocol description..... | 11 | +| 2.3 Requesting messages already held in the Mobile Termination..... | 12 | +| 2.3.1 Requesting List Of Messages ..... | 13 | +| 2.3.2 Requesting Transfer Of Messages..... | 13 | +| 2.3.2.1 Requesting Transfer Of A Specific Message..... | 13 | +| 2.3.2.2 Requesting Transfer Of All Messages ..... | 13 | +| 2.3.3 Requesting Diversion Of Incoming Messages ..... | 14 | +| 2.3.3.1 Requesting SMS Messages..... | 14 | +| 2.3.3.2 Requesting CBS Messages ..... | 14 | +| 2.3.3.3 Requesting indication of message arrival ..... | 14 | +| 2.3.4 Requesting Transfer Into Mobile Termination..... | 15 | +| 2.3.5 Requesting Deletion Of Messages..... | 15 | +| 2.4 Message functional definitions and contents ..... | 16 | +| 2.4.1 Commands Issued By The Terminal Equipment..... | 16 | +| 2.4.1.1 List Request ..... | 17 | +| 2.4.1.2 Get Message..... | 17 | +| 2.4.1.3 Get First Message ..... | 17 | +| 2.4.1.4 Get Next Message..... | 17 | +| 2.4.1.5 Transfer Inc SMS..... | 17 | +| 2.4.1.6 Indicate Inc SMS ..... | 17 | +| 2.4.1.7 Transfer Inc CBS ..... | 18 | +| 2.4.1.8 Insert SMS ..... | 18 | +| 2.4.1.9 Delete message ..... | 18 | +| 2.4.1.10 Unable to process..... | 18 | +| 2.4.1.11 End SMS Mode..... | 18 | +| 2.4.1.12 Acknowledge Message ..... | 19 | +| 2.4.2 Responses/Indications Issued By The MT ..... | 19 | +| 2.4.2.1 Message List ..... | 19 | +| 2.4.2.2 Message ..... | 19 | +| 2.4.2.3 Get Message Failure ..... | 20 | +| 2.4.2.4 Inc Message ..... | 20 | +| 2.4.2.5 Message Arrived..... | 20 | +| 2.4.2.6 Insert SMS Complete..... | 20 | +| 2.4.2.7 Insert SMS Failure ..... | 20 | +| 2.4.2.8 Delete Message Complete ..... | 21 | +| 2.4.2.9 Delete Message Failure..... | 21 | +| 2.4.2.10 Unable To Process ..... | 21 | +| 2.4.2.11 End SMS Mode..... | 21 | +| 2.4.2.12 Request Confirmed ..... | 21 | +| 2.5 General message format and information elements coding ..... | 21 | +| 2.5.1 Message Type..... | 21 | +| 2.5.2 Other Information Elements ..... | 22 | +| 2.5.2.1 Short Message Reference..... | 22 | +| 2.5.2.2 SMS Transfer Type..... | 23 | +| 2.5.2.3 Indication Type..... | 23 | + +| | | | +|-------------------------------|---------------------------------------------------------|-----------| +| 2.5.2.4 | Insert Type ..... | 24 | +| 2.5.2.5 | Short Message Index..... | 25 | +| 2.5.2.6 | Short Message Data ..... | 26 | +| 2.5.2.7 | Cause..... | 28 | +| 2.5.2.8 | Index Count..... | 29 | +| 2.5.2.9 | CBS Transfer Type ..... | 29 | +| 2.5.2.10 | Page Index..... | 29 | +| 2.5.2.11 | Last Short Message..... | 30 | +| 2.5.2.12 | Confirm Type..... | 30 | +| 2.5.2.13 | TP-Failure Cause ..... | 31 | +| 2.5.2.14 | SM-Deliver-Ack ..... | 31 | +| 2.5.2.15 | SM-Submit-Ack..... | 32 | +| 3 | Text Mode..... | 32 | +| 3.1 | Parameter Definitions..... | 32 | +| 3.2 | General Configuration Commands..... | 35 | +| 3.2.1 | Select Message Service +CSMS ..... | 35 | +| 3.2.2 | Preferred Message Storage +CPMS ..... | 36 | +| 3.2.3 | Message Format +CMGF ..... | 36 | +| 3.2.4 | Enter SMS Block Mode Protocol +CESP ..... | 37 | +| 3.2.5 | Message Service Failure Result Code +CMS ERROR ..... | 37 | +| 3.2.6 | Informative Examples ..... | 38 | +| 3.3 | Message Configuration Commands ..... | 38 | +| 3.3.1 | Service Centre Address +CSCA..... | 38 | +| 3.3.2 | Set Text Mode Parameters +CSMP..... | 38 | +| 3.3.3 | Show Text Mode Parameters +CSDH..... | 39 | +| 3.3.4 | Select Cell Broadcast Message Types +CSCB ..... | 39 | +| 3.3.5 | Save Settings +CSAS ..... | 40 | +| 3.3.6 | Restore Settings +CRES..... | 40 | +| 3.3.7 | Informative Examples ..... | 41 | +| 3.4 | Message Receiving and Reading Commands ..... | 41 | +| 3.4.1 | New Message Indications to TE +CNMI ..... | 41 | +| 3.4.2 | List Messages +CMGL..... | 46 | +| 3.4.3 | Read Message +CMGR..... | 47 | +| 3.4.4 | New Message Acknowledgement to ME/TA +CNMA..... | 47 | +| 3.4.5 | Informative Examples ..... | 48 | +| 3.5 | Message Sending and Writing Commands ..... | 49 | +| 3.5.1 | Send Message +CMGS..... | 49 | +| 3.5.2 | Send Message from Storage +CMSS ..... | 50 | +| 3.5.3 | Write Message to Memory +CMGW ..... | 50 | +| 3.5.4 | Delete Message +CMGD ..... | 51 | +| 3.5.5 | Send Command +CMGC ..... | 52 | +| 3.5.6 | More Messages to Send +CMMS..... | 52 | +| 3.5.7 | Informative Examples ..... | 53 | +| 4 | PDU Mode ..... | 53 | +| 4.0 | General ..... | 53 | +| 4.1 | List Messages +CMGL ..... | 54 | +| 4.2 | Read Message +CMGR..... | 54 | +| 4.3 | Send Message +CMGS ..... | 54 | +| 4.4 | Write Message to Memory +CMGW..... | 55 | +| 4.5 | Send Command +CMGC ..... | 56 | +| 4.6 | New Message Acknowledgement to ME/TA +CNMA ..... | 56 | +| 4.7 | Send Message from Storage +CMSS..... | 57 | +| Annex A (normative): | Character Set Conversions for SMS Text Mode..... | 58 | +| Annex B (informative): | Example of processing a data block..... | 61 | +| B.1 | Example state diagrams for the block receiver ..... | 61 | +| B.2 | Example of coding and decoding a data block ..... | 61 | + +Annex C (informative):        Change History..................................................................................................68 + +# --- 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 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 defines three interface protocols for control of SMS functions within a GSM/UMTS mobile telephone from a remote terminal via an asynchronous interface. + +Clause 2 defines a binary protocol ("Block Mode"). The protocol includes error protection and is suitable for use where the link may not be completely reliable. It will be of particular use where control of remote devices is required. Efficient transfer of binary encoded user data is possible. + +Clause 3 defines a character-based interface based on "AT" commands ("Text Mode"). This mode is suitable for unintelligent terminals or terminal emulators, and for application software built on command structures like those defined in V.25ter. Some of the commands defined in clause 3 will also be useful for implementations of clause 2 and/or clause 4, for example enabling an indication of incoming SMS messages. + +Clause 4 defines a character-based interface with hex-encoded binary transfer of message blocks ("PDU Mode"). This mode is suitable for software drivers based on AT command structures which do not understand the content of the message blocks and can only pass them between the MT and "upper level" software resident in the TE. + +In all three modes, the terminal is considered to be in control for SMS/CBS transactions. + +The present document considers the mobile termination to be a single entity. Other 3GPP/GSM Technical Specifications describe the split of functionality between the mobile equipment and (U)SIM. + +The three "modes" referred to above, are represented in figure 0.1. + +The "Block mode" is a self contained mode in its own right, and when entered, control will remain within that mode until the procedures to exit the mode are executed, after which control is returned to the V.25ter "command" state or "on-line command" state. + +The "Text" and "PDU" modes are not in themselves V.25ter states but are simply sets of commands which will operate in either the V.25ter "command" state or "on-line command" state. The "Text" and "PDU" modes are transitory states and after each operation, control is automatically returned to the V.25ter "command" state or "on-line command" state. Whilst in the V.25ter command state, the MS is available to handle incoming and outgoing calls such as Data or Facsimile. + +![Diagram illustrating the relationship between V.25ter states and SMS modes. A large circle represents the 'V.25ter "command" state and "on-line command" state'. Inside this circle are two smaller circles labeled 'SMS Text Mode' and 'SMS PDU Mode'. Below the large circle, a rectangle labeled 'SMS Block Mode' is connected to the bottom of the circle by a vertical line.](34f788b0e5bc8af774fa5561c22e6d01_img.jpg) + +``` +graph TD + subgraph V25ter [V.25ter "command" state and "on-line command" state] + TextMode((SMS Text Mode)) + PDUMode((SMS PDU Mode)) + end + BlockMode[SMS Block Mode] +``` + +Diagram illustrating the relationship between V.25ter states and SMS modes. A large circle represents the 'V.25ter "command" state and "on-line command" state'. Inside this circle are two smaller circles labeled 'SMS Text Mode' and 'SMS PDU Mode'. Below the large circle, a rectangle labeled 'SMS Block Mode' is connected to the bottom of the circle by a vertical line. + +**Figure 0.1: Block, Text and PDU modes** + +In the "Block mode" and "PDU" mode a mobile is not permitted to modify any component of an SMS/CBS message received from the air interface or an SMS message received from a TE, before passing it on, except where 3GPP TS 23.040 [3] or 3GPP TS 23.041 [4] defines a "component modification facility" and where this "component modification facility" is supported by the mobile. In the Text Mode the mobile may be unable to display characters coded in particular coding schemes. In this case, the mobile shall behave as described in 3GPP TS 23.038 [2] and assume the coding scheme to be the GSM 7 bit default alphabet. + +## 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] Void. +- [2] 3GPP TS 23.038: "Alphabets and language-specific information". +- [3] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS) ". +- [4] 3GPP TS 23.041: "Technical realization of the Cell Broadcast Service (CBS)". +- [5] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3". +- [6] 3GPP TS 24.011: "Short Message Service (SMS) support on mobile radio interface". +- [7] 3GPP TS 24.012: "Cell Broadcast Service (CBS) support on the mobile radio interface". +- [8] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". +- [9] 3GPP TS 27.007: "AT command set for User Equipment (UE)". +- [10] 3GPP TS 51.011: "Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface". +- [11] ITU-T Recommendation V.25ter: "Serial asynchronous automatic dialling and control". +- [12] ITU-T Recommendation V.24: "List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE)". +- [13] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". +- [14] ITU-T Recommendation E.163: "Numbering plan for the international telephone service". +- [15] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [16] 3GPP TS 31.102: "Characteristics of the USIM application". + +## 0.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [15] and the following apply. + +| | | +|------|---------------------------------| +| EVPF | Enhanced Validity Period Format | +|------|---------------------------------| + +# 1 Reference configuration + +![Figure 1: Reference configuration diagram. A large rectangle labeled 'UE' contains two main components: a 'USIM' block on the left and a 'ME' block on the right. The 'ME' block contains two sub-blocks: 'MT' (Mobile Terminal) on top and 'TE' (Terminal Equipment) on the bottom.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) + +Figure 1: Reference configuration diagram. A large rectangle labeled 'UE' contains two main components: a 'USIM' block on the left and a 'ME' block on the right. The 'ME' block contains two sub-blocks: 'MT' (Mobile Terminal) on top and 'TE' (Terminal Equipment) on the bottom. + +**Figure 1: Reference configuration** + +The User Equipment (UE) consists of the mobile equipment (ME) and the (U)SIM. Messages may be stored in either, but the present document does not distinguish between messages stored in the (U)SIM or in the ME. The management of message storage in the two parts of the UE is a matter for the UE implementation. + +## 1.1 V.24 Interface Circuits + +The operation of the ITU-T Recommendation V.24 blue book interface circuits for SMS is shown in table 1.1. + +**Table 1.1: Use of V.24 interface circuits** + +| V.24 CIRCUIT | DESCRIPTION | TE to MT | MT to TE | +|--------------|---------------|----------|----------| +| CT102 | signal ground | x | x | +| CT103 | TXD | x | | +| CT104 | RXD | | x | +| CT105 | RTS | x | | +| CT106 | CTS | | x | +| CT107 | DSR | | x | +| CT108.2 | DTR | x | | +| CT109 | DCD | | x | + +NOTE: CT105 at the TE is connected to CT133 at the MT. + +### 1.1.1 Circuit definitions for the SMS Block mode + +#### CT103 + +All commands from the TE to the MT are transferred across this circuit. Inband flow control is not permitted during Block Mode. + +#### CT104 + +All responses/indications from the MT to the TE are transferred across this circuit. Inband flow control is not permitted during Block Mode. + +#### CT105 + +This circuit allows the TE to flow control the MT when in the Block Mode and at other times if hardware flow control is enabled. + +#### CT106 + +This circuit allows the MT to flow control the TE when in the Block Mode and at other times if hardware flow control is enabled. + +#### CT107 + +This circuit shall be set to the ON condition before entry into the Block Mode, and shall remain in the ON condition during Block Mode. If the TE detects that this circuit returns to the OFF condition during the block mode then the TE shall return CT108.2 to the OFF condition and exit the Block Mode. + +#### CT108.2 + +This circuit shall be set in the ON condition before the AT+CESP command is sent from the TE to begin the Block Mode, and shall be maintained in the ON condition during the Block Mode. It shall be returned to the OFF condition after the command 'END SMS MODE' has been accepted and acknowledged by the MT. If the MT detects that this circuit returns to the OFF condition during the Block Mode then the MT shall exit the Block Mode. + +#### CT109 + +This circuit shall be set to the ON condition before entry into the Block Mode and remain in the ON condition during the Block Mode. If the TE detects that this circuit returns to the OFF condition during the Block Mode then the TE shall return CT108.2 to the OFF condition and shall exit the Block Mode. + +### 1.1.2 Circuit definitions for the SMS Text and PDU modes + +Only circuits CT102, CT103 and CT104 are mandatory for the Text and PDU modes. The functionality and operation of other circuits shall be in accordance with V.25ter. + +# --- 2 SMS Block Mode + +## 2.1 Beginning and ending of SMS/CBS Block Mode + +### 2.1.1 Beginning SMS/CBS Block Mode + +As described in 3GPP TS 27.001 [8], the DTE/DCE interface is normally associated with the terminal adaptation function (TAF), if such a function is available. When no data connection is in progress, and the terminal equipment wishes to enter SMS/CBS mode, the command 'AT+CESP' shall be issued by the TE through the DTE/DCE interface requesting that the Block mode protocol described in the present document is to be used. The syntax of this command is further described in clause 3.2.4 later. The syntax for these commands is derived from ITU-T Recommendation V.25ter, i.e. the command is encoded as an IA5 character string together with delimiters as described in ITU-T Recommendation V.25ter. + +Upon receipt of this command, the mobile termination shall respond as follows: + +- If the mobile termination supports SMS/CBS block mode commands, responses and indications as described in the present document, it shall respond with 'OK' (or 0) and enter the SMS/CBS mode. +- If the mobile termination does not support SMS/CBS block mode commands, responses and indications as described in the present document, it shall respond with 'ERROR' (or 4) and remain in the current mode. +- Terminal software shall wait a short time (e.g. 5 seconds) for the 'OK' (0) or 'ERROR' (4) response. If neither response is received before the timeout then the terminal software shall assume that the block mode has been entered. The terminal software may then submit its first block mode command. If no response is received to this command then the terminal software shall proceed as described below in clause 2.2 (i.e. repeat the command 3 times and then exit the block mode). + +If the SMS/CBS block mode command is accepted by the mobile termination, then all further commands, responses and indications shall be as defined in clause 2 of the present document. These SMS/CBS mode commands, responses and indications use 8-bit encoded data and not IA5 characters. + +### 2.1.2 Returning from SMS/CBS Block Mode To Default Mode + +When the terminal equipment wishes to return to default mode from SMS/CBS mode, it shall issue the command 'END SMS MODE', described in clause 2.4.1.11. The mobile termination shall respond with 'OK' (or 0) to indicate that the DTE/DCE interface has returned to default mode. The TE shall change back to default mode whether or not such a response is received. + +The TE may also indicate that it has exit from the SMS/CBS mode through the use of CT 108/2 (see clause 1.1) + +If an incoming data call arrives while the DTE/DCE interface is set to SMS/CBS mode, then the mobile termination may autonomously issue the 'END SMS MODE' indication (clause 2.4.2.11) and revert to default mode in order to connect the data call through the TAF. + +The MT may exit from SMS/CBS mode autonomously if the power to the MT is switched off and then on again. In addition, the MT manufacturer may provide MMI to change the mode back to the default mode. In the latter case, the MT shall issue the 'END SMS MODE' indication (clause 2.4.2.11) and exit the SMS/CBS mode immediately. + +The MT may also indicate that it has exit from the SMS/CBS mode through the use of CT 107 and CT 109 (see clause 1.1). + +A BREAK condition in either direction at the DTE/DCE interface shall cause the TE and the MT to exit from the SMS/CBS block mode and return to the default mode. + +In the event where the TE or the MT find themselves unable to recover from a protocol error then either entity may exit the SMS/CBS mode using any of the mechanisms described above. Confirmation of default mode operation will be achieved through the use of AT commands and responses. + +## 2.2 Protocol description + +The communication path between the MT and the TE across the DTE/DCE interface should be quite reliable if it uses a short wire link. However, to ensure that the low error rate does not cause malfunction, the following error protection scheme is provided. + +Each message sent from the MT to the TE or vice-versa consists of a data block (DATA) and block check sum (BCS, see figure 2.2.1). In the following description the notation DLE, STX, NUL and ETX refer to control characters having the values 10 02 00 and 03 hexadecimal respectively. + +![](536951b2bbd94325ae266d8d1363df8f_img.jpg) + +<-----DATA-----> <- BCS -> + +| | | | | | | | +|------------|------------|-----------------|------------|------------|------------|------------| +| DLE
10H | STX
02H | Message content | DLE
10H | ETX
03H | BCS
MSB | BCS
LSB | +|------------|------------|-----------------|------------|------------|------------|------------| + +**Figure 2.2.1: Format of DTE/DCE interface messages** + +The data block consists of a start transmission sequence, set to 00010000 00000010 (10 02 hex), the message content as defined below and an end transmission sequence, set to 00010000 00000011 (10 03 hex). The least significant bit of each octet is always transmitted first. + +The block check sum is calculated at the transmitter by adding all of the octets in the message content modulo 65536. Each bit of the 16-bit result is then inverted, and 1 is added to the answer. + +During transmission of the message content and the BCS octets, any occurrence of the value 10 hex (DLE) shall result in an additional 'stuffing' octet of value 00 hex (NUL) being transmitted immediately following the octet containing 10 hex. This is to ensure that the start and end markers are unambiguous. The receiver shall remove stuffing octets by discarding any octet of value 00 hex (NUL) which immediately follows an octet of value 10 hex (DLE). + +After removal of any stuffing octets, the receiver can check the BCS by adding all of the octets in the message content and the 16-bit BCS modulo 65536. The correct result is 0000 hex. If any message is received with an incorrect BCS, then the message is discarded. No response is sent over the DTE/DCE interface, but an indication may be provided to higher layers within the receiving entity. + +The transmitter shall only send DLE when it is followed by STX, NUL or ETX. Therefore, if the receiver sees a DLE followed by anything else then the receiver shall assume that some data has been lost, and shall start to search for the + +start marker. An unexpected end marker at the receiver shall also result in a search for a start marker. A start marker shall always be treated as the start of a new block, regardless of which state the receiver is in. + +Examples of state diagrams for a block receiver to implement this procedure are given in Annex B, together with an example of coding and decoding a message. + +Only one Command/Response transaction shall be permitted at any one time from any sending or receiving entity. It shall however be possible for a Command/Response transaction from one entity to be initiated even if there is a Command/Response transaction in progress from the other entity. + +If an immediate response is expected to a message sent over the DTE/DCE interface, then the sending entity shall wait 10 s. If no response is received within this time, the sending entity shall repeat the message. The message shall be repeated a maximum of 3 times, after which the sending entity shall exit from the SMS/CBS mode and provide an error indication to the user. + +If a message cannot be understood by the receiving entity even though it has a correct BCS, then it shall return an UNABLE TO PROCESS message with cause value 'Command not understood'. The receipt of an UNABLE TO PROCESS message should not in itself initiate re-transmission although re-transmission may take place due to the timeout mechanism described earlier since an UNABLE TO PROCESS is deemed to be an invalid response. The 'Cause' may however be referred to a higher layer. An UNABLE TO PROCESS shall not be sent as the result of an incorrect BCS. + +## 2.3 Requesting messages already held in the Mobile Termination + +The TE may request the MT to provide SMS or CBS messages already stored. The TE will either request all messages, or request a list of messages and subsequently ask for specific messages. + +At the start of the SMS/CBS mode session, the MT shall number all messages contiguously, starting with message number 1. These "Short Message References" are only valid for a single SMS/CBS MODE session and should not be confused with the 3GPP TS 23.040 [3] TP-Message-Reference. Each message retains its Short Message Reference for the duration of the SMS/CBS mode session. New messages will normally be given the lowest previously-unused Short Message Reference. However, if all Short Message References have been used then the MT may reallocate Short Message References previously allocated to now-deleted messages. + +Short Message Reference 0 signifies that there are no messages in the MT. The value of 0 is used under the following conditions: + +- When an INSERT SMS command is used to transfer an SM over the air interface and not store it in the MT then the MT will return a Short Message Reference of 0 in the REQUEST CONFIRMED response and the ensuing INSERT SMS COMPLETE / INSERT SMS FAILURE indications. +- For Class 0 SM's which are not stored in the MT. +- For TE specific SM's which are not stored in the MT. + +If Message number 0 is requested by the TE, the MT will always return an error cause, but will also include the highest valid Short Message Reference (see clause 2.3.2.1). + +### 2.3.1 Requesting List Of Messages + +The TE may request the MT to provide a list of SMS and CBS messages currently stored in the mobile termination. This is achieved by the LIST REQUEST command (clause 2.4.1.1). The MT divides the messages stored into groups of 5 (called pages) and transfers the first 5 in a MESSAGE LIST response (clause 2.4.2.1) containing message references allocated by the MT, plus the relevant header information described in 3GPP TS 23.040 [3] and 3GPP TS 24.011 [6] and 3GPP TS 23.041 [4] and 3GPP TS 24.012 [7]. + +If there are no messages stored in the MT, then the MESSAGE LIST response shall be empty. + +The TE may then request further groups of up to 5 messages by repeating the LIST REQUEST command for pages 2, 3, and so on. The MT will indicate that there are no more pages by responding with an empty MESSAGE LIST response. + +### 2.3.2 Requesting Transfer Of Messages + +The TE may request the transfer of one or more messages by means of the commands described below. The MT does not delete messages which have been transferred. Messages can only be deleted by the DELETE MESSAGE command (clause 2.4.1.9). + +#### 2.3.2.1 Requesting Transfer Of A Specific Message + +The TE may request the MT to transfer a specific message by sending the GET MESSAGE command (clause 2.4.1.2), including the appropriate message reference. The MT will provide the full message including header in a MESSAGE response (clause 2.4.2.2). If the message reference is unallocated, then the GET MESSAGE FAILURE response is returned with cause 'No such message' and the highest valid Message Reference (clause 2.4.2.3). + +#### 2.3.2.2 Requesting Transfer Of All Messages + +The TE may request the MT to transfer all messages by sending the GET FIRST MESSAGE command (clause 2.4.1.3), followed by the appropriate number of GET NEXT MESSAGE commands (clause 2.4.1.4). + +The MT shall be able to transfer all messages one-by-one, starting with the 'first' and continuing with the 'next'. The precise ordering of the messages is left to the MT implementation. + +If the MT exits from SMS/CBS mode for any reason, then this information need not be retained. + +On receipt of the GET FIRST MESSAGE command, the MT shall set a pointer to the first message, and transfer this message using the MESSAGE response as described in clause 2.3.2.1. + +On receipt of the GET NEXT MESSAGE command, the MT shall move the pointer to the first available message after the last message transferred (using either GET FIRST MESSAGE, GET MESSAGE or GET NEXT MESSAGE), and transfer this message using the MESSAGE response as described in clause 2.3.2.1. + +If the MT receives a GET NEXT MESSAGE command when all messages have been transferred to the TE, or there are no messages stored in the MT, then the GET MESSAGE FAILURE response shall be provided with the cause 'No such message' (see clause 2.4.2.3). + +If the TE receives an out of sequence message then it shall attempt to transfer the missing message using the GET MESSAGE command before continuing with GET NEXT MESSAGE. If this attempt fails with the cause 'no such message', it means that the message has been deleted, or it has been lost due to a failure at the MT. + +The MT includes a LAST SHORT MESSAGE REFERENCE in the GET MESSAGE FAILURE response. This is so that the TE can detect whether or not the last short message was received in error. + +If the MT receives a GET NEXT MESSAGE command prior to receiving a GET FIRST MESSAGE or GET MESSAGE command, then it shall continue as if the command had been GET FIRST MESSAGE (i.e. provide the 'first' message and continue with the 'next' on receipt of the subsequent GET NEXT MESSAGE command). + +### 2.3.3 Requesting Diversion Of Incoming Messages + +The TE may request the MT to transfer SMS or CBS messages directly from the air interface to the DTE/DCE interface, by the following procedures. If messages are diverted then they are not stored in the MT. If messages are diverted and there is no communication path to the TE (e.g. because it has been disconnected), the diversion shall be cancelled. + +#### 2.3.3.1 Requesting SMS Messages + +The TE may request an indication of arrival of incoming SMS messages, or the direct transfer of incoming SMS messages. + +The TE requests new SMS messages by the TRANSFER INC SMS command (clause 2.4.1.5). This command will be sent with parameters indicating whether all incoming SMS messages are to be transferred, or only those indicated as being for the TE. + +The MT shall confirm receipt of this command with a REQUEST CONFIRMED message provided there is memory available to store SM's in the ME or the (U)SIM. If there is no memory available, the MT shall respond with 'unable to process' with a cause value No memory. + +The MT shall transfer incoming messages by the INC MESSAGE indication (clause 2.4.2.4). + +For an INC MESSAGE which contains a Short Message (SMS) info element id, the TE shall acknowledge receipt of the INC MESSAGE with an ACKNOWLEDGE MESSAGE (clause 2.4.1.12). The MT should not send another INC MESSAGE which contains a Short Message (SMS) info element id to the TE whilst it is waiting for an ACKNOWLEDGE MESSAGE. + +In the event of the MT not receiving an ACKNOWLEDGE MESSAGE within a time specified by the MT manufacturer the MT shall exit the SMS mode automatically after 'n' attempts to send the INC MESSAGE (where n is a number specified by the MT manufacturer). The MT should attempt to store the unacknowledged SM or Status Report (contained in the INC MESSAGE) in the MT or on the (U)SIM as appropriate. + +The ACKNOWLEDGE MESSAGE sent from the TE to the MT must not delay the MT sending the RP-ACK defined in 3GPP TS 23.040 [3] (to the SC) for longer than the RP-ACK timeout specified in 3GPP TS 24.011 [6]. + +The TE requests the cessation of incoming message transfer by the same command, indicating no incoming messages. The transfer of messages will automatically cease on exit of the SMS/CBS mode. Transfer shall not recommence until a new request is issued by the TE. + +#### 2.3.3.2 Requesting CBS Messages + +The TE may request the transfer of all cell broadcast messages directly from the air interface to the DTE/DCE interface. This is achieved by the use of the TRANSFER INC CBS message (clause 2.4.1.7). + +The MT shall confirm receipt of this command with a REQUEST CONFIRMED message. + +After receipt of this command, the MT shall transfer all CBS pages as they arrive on the air interface, using the INC MESSAGE indication (clause 2.4.2.4). + +While the CBS pages are being transferred, any other indication or response required to be sent to the TE will take precedence over the CBS pages. However, the MT shall not interrupt the transfer of a page to send other information within the SMS/CBS mode (ie. the MT shall wait until a page boundary). + +The transfer of messages will automatically cease on exit of the SMS/CBS mode. Transfer shall not recommence until a new request is issued by the TE. + +#### 2.3.3.3 Requesting indication of message arrival + +If the TE requires an indication of incoming message arrival, the INDICATE INC SMS command (clause 2.4.1.6) shall be used. + +The MT shall confirm receipt of this command with a REQUEST CONFIRMED message. + +After receipt of this command, the MT shall indicate all incoming messages in the specified categories (unless they are directly transferred) with the MESSAGE ARRIVED indication (clause 2.4.2.5). This indication shall be of the same format as the MESSAGE LIST response described in clause 2.3.1. + +The TE shall acknowledge receipt of the MESSAGE ARRIVED with an ACKNOWLEDGE MESSAGE. (clause 2.4.1.12). The MT should not send another MESSAGE ARRIVED to the TE whilst it is waiting for an ACKNOWLEDGE MESSAGE. + +In the event of the MT not receiving an ACKNOWLEDGE MESSAGE within a time specified by the MT manufacturer the MT shall exit the SMS mode automatically after 'n' attempts to send the MESSAGE ARRIVED (where n is a number specified by the MT manufacturer). The MT should attempt to store the unacknowledged SM or Status Report in the MT or on the (U)SIM as appropriate. + +The ACKNOWLEDGE MESSAGE sent from the TE to the MT must not delay the MT sending the RP-ACK defined in 3GPP TS 23.040 [3] (to the SC) for longer than the RP-ACK timeout specified in the 3GPP TS 24.011 [6]. + +The TE requests the cessation of incoming message indication by the INDICATE INC SMS command, with the 'no incoming messages' parameter. + +### 2.3.4 Requesting Transfer Into Mobile Termination + +The TE may request transfer of SMS messages into the mobile termination. Cell broadcast messages cannot be transferred in this direction. + +The TE shall use the INSERT SMS command (clause 2.4.1.8) to transfer the message. This command shall indicate whether the message is to be stored in the MT, sent over the air interface or both. The command shall include the full SMS message and header as described in 3GPP TS 23.040 [3], except for the message reference and message type indication (which are allocated by the MT). + +Only one INSERT SMS command may be outstanding at any given instant. An INSERT SMS is deemed complete when an INSERT SMS COMPLETE or an INSERT SMS FAILURE indication has been received irrespective of whether an intermediate REQUEST CONFIRMED has been received. + +Upon receipt of an INSERT SMS command, the MT shall act in the following way: + +If the TE requested the MT to store the message, the MT shall attempt to store the message. If the attempt is successful, the MT shall return an INSERT SMS COMPLETE indication (clause 2.4.2.6), including the message reference allocated by the MT. If the attempt fails (eg. due to lack of memory), the MT shall return an INSERT SMS FAILURE indication (clause 2.4.2.7), providing a cause for the failure. + +If the TE requested the MT to send the message, the MT shall respond immediately with a REQUEST CONFIRMED message, and attempt to send the message. If the send attempt subsequently succeeds, the MT shall send an INSERT SMS COMPLETE indication, including the message references allocated by the MT. If the send attempt subsequently fails, the MT shall return an INSERT SMS FAILURE indication, providing a cause for the failure. + +If the TE requested the MT to store and send the message, the MT shall first attempt to store the message. If no storage is available, the MT shall return an INSERT SMS FAILURE indication (clause 2.4.2.7) and shall not attempt to send the message. If storage is available, the MT shall store the message and then respond with a REQUEST CONFIRMED message. If the send attempt is successful, the MT shall return an INSERT SMS COMPLETE indication (clause 2.4.2.6), including the message references allocated by the MT. If the transmission of the message fails, then the MT shall return an INSERT SMS FAILURE indication (clause 2.4.2.7). This will show that the send attempt failed and provide a cause. After that the MT shall delete the stored message. + +### 2.3.5 Requesting Deletion Of Messages + +The TE may request deletion of SMS or CBS messages from the store in the MT. This is achieved by the DELETE MESSAGE command (clause 2.4.1.9). The command will include a message reference, as defined by the MT and provided in the message list. + +Upon receipt of this command, the MT shall attempt to delete the message. If successful, the MT shall return a DELETE MESSAGE COMPLETE indication (clause 2.4.2.8). If not successful, the MT shall return a DELETE MESSAGE FAILURE indication (clause 2.4.2.9). + +On successful deletion of an SM or CBS message the Page Index (see clause 2.5.2.10) and the Index Count (see clause 2.5.2.8) shall be re-assigned so that their values are contiguous (i.e. there are no gaps in either parameter). The original short message Reference values remain unchanged. + +## 2.4 Message functional definitions and contents + +This clause provides an overview of the message structure to be used over the DTE/DCE interface in SMS/CBS block mode. Each message definition includes a brief description of the use of the message, and a table showing all the information elements which may be included in the message. If an entity receives a message containing more information elements than expected then the receiving entity shall ignore the additional information elements. For each information element the following data are provided. + +Reference - this indicates where the detailed description of each element can be found. + +### **Presence:** + +| | | | +|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| M | Mandatory | must always be present
receiver: If not present, consider message erroneous | +| C | Conditional | presence depending on e.g.
a) value of other element
b) presence of optional element
receiver: If not present when condition met, consider message erroneous | +| O | Optional | presence is a choice of the sender
receiver: present or not, accept message | + +### **Format:** + +| | | +|-----|----------------------------------------------------------------------------------| +| T | Type only, fixed length, only IEI | +| V | Value only, fixed length, no IEI included | +| TV | Type and value, fixed length, IEI included | +| LV | Length and value, variable length, no IEI included and Length indicator included | +| TLV | Type, Length and Value, variable length, IEI and length indicator included | + +Length - this indicates the length of the information element in octets. + +### 2.4.1 Commands Issued By The Terminal Equipment + +Table 2.4.1 summarises the commands which may be issued by the TE. + +**Table 2.4.1: Commands which may be issued by the TE** + +| | Reference | +|---------------------|-----------| +| LIST REQUEST | 2.4.1.1 | +| GET MESSAGE | 2.4.1.2 | +| GET FIRST MESSAGE | 2.4.1.3 | +| GET NEXT MESSAGE | 2.4.1.4 | +| TRANSFER INC SMS | 2.4.1.5 | +| INDICATE INC SMS | 2.4.1.6 | +| TRANSFER INC CBS | 2.4.1.7 | +| INSERT SMS | 2.4.1.8 | +| DELETE MESSAGE | 2.4.1.9 | +| UNABLE TO PROCESS | 2.4.1.10 | +| END SMS MODE | 2.4.1.11 | +| ACKNOWLEDGE MESSAGE | 2.4.1.12 | + +#### 2.4.1.1 List Request + +This message is sent by the TE to the MT to request a list of messages stored in the MT. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Page Index | 2.5.2.10 | M | V | 1 | + +#### 2.4.1.2 Get Message + +This message is sent by the TE to the MT to request transfer of a specific SMS or CBS message stored in the MT. + +| Information element | Reference | Presence | Format | Length | +|-------------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Short Message Reference | 2.5.2.1 | M | V | 1 | + +#### 2.4.1.3 Get First Message + +This message is sent by the TE to the MT to request transfer of the first available SMS or CBS message stored in the MT. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | + +#### 2.4.1.4 Get Next Message + +This message is sent by the TE to the MT to request transfer of the next available SMS or CBS message stored in the MT. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | + +#### 2.4.1.5 Transfer Inc SMS + +This message is sent by the TE to the MT to request the direct transfer of incoming messages from the air interface to the TE. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| SMS Transfer Type | 2.5.2.2 | M | V | 1 | + +#### 2.4.1.6 Indicate Inc SMS + +This message is sent by the TE to the MT to request that the MT indicates when an incoming message arrives. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Indication Type | 2.5.2.3 | M | V | 1 | + +#### 2.4.1.7 Transfer Inc CBS + +This message is sent by the TE to the MT to request transfer of all cell broadcast messages directly from the air interface to the DTE/DCE interface. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| CBS Transfer Type | 2.5.2.9 | M | V | 1 | + +#### 2.4.1.8 Insert SMS + +This message is sent by the TE to the MT to request the transfer of an SMS TPU to the MT memory or across the air interface. The TPDU is formatted in exactly the same way as described in 3GPP TS 23.040 [3]. Where the TPDU includes a TP-Message-Reference which is to be incremented by the MT for every outgoing message, the TP-Message-Reference provided by the TE will be overwritten by the MT before transmission of the message. The value provided by the TE is discarded by the MT and has no significance. + +| Information element | Reference | Presence | Format | Length | +|------------------------|-------------------------------------------------------------------------------------------------------------------------------------|----------|--------|---------| +| Message Type | 2.5.1 | M | V | 1 | +| Insert Type | 2.5.2.4 | M | V | 1 | +| RP-Destination-Address | 3GPP TS 24.011 [6] | M | LV | 1-12 a) | +| SMS-TPDU | 3GPP TS 23.040 [3] | M | V | max 164 | +| a) | If no RP-Destination-Address is to be transferred then the length is set to 0. In this case, the MT inserts the default SC address. | | | | + +#### 2.4.1.9 Delete message + +This message is sent from the TE to the MT to request deletion of a specific SMS or CBS message held in the MT. + +| Information element | Reference | Presence | Format | Length | +|-------------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Short Message Reference | 2.5.2.1 | M | V | 1 | + +#### 2.4.1.10 Unable to process + +This response is sent from the TE to the MT to indicate that the MT's message could not be processed. + +| Information element | Preference | Presence | Format | Length | +|---------------------|------------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Cause | 2.5.2.7 | M | V | 1 | + +#### 2.4.1.11 End SMS Mode + +This message is sent from the TE to the MT to terminate the SMS/CBS mode of the DTE/DCE interface. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | + +#### 2.4.1.12 Acknowledge Message + +This message is sent from the TE to the MT to acknowledge receipt of a INC MESSAGE or MESSAGE ARRIVED which contains a Short Message (SMS) info element id, (e.g. a Short Message or a Status Report but not a CBS message). + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|----------| +| Message Type | 2.5.1 | M | V | 1 | +| SM-Deliver-Ack | 2.5.2.14 | O | TLV | 2 to 160 | + +### 2.4.2 Responses/Indications Issued By The MT + +Table 2.4.2 summarises the responses/indications which may be issued by the MT. + +**Table 2.4.2: Responses/Indications which may be issued by the MT** + +| | Reference | +|-------------------------|-----------| +| MESSAGE LIST | 2.4.2.1 | +| MESSAGE | 2.4.2.2 | +| GET MESSAGE FAILURE | 2.4.2.3 | +| INC MESSAGE | 2.4.2.4 | +| MESSAGE ARRIVED | 2.4.2.5 | +| INSERT SMS COMPLETE | 2.4.2.6 | +| INSERT SMS FAILURE | 2.4.2.7 | +| DELETE MESSAGE COMPLETE | 2.4.2.8 | +| DELETE MESSAGE FAILURE | 2.4.2.9 | +| UNABLE TO PROCESS | 2.4.2.10 | +| END SMS MODE | 2.4.2.11 | +| REQUEST CONFIRMED | 2.4.2.12 | + +#### 2.4.2.1 Message List + +This response is sent from the MT to the TE on receipt of a LIST REQUEST from the TE. + +| Information element | Reference | Presence | Format | Length | +|-------------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Page Index | 2.5.2.10 | M | V | 1 | +| Index Count | 2.5.2.8 | M | V | 1 | +| Short Message Index (1) | 2.5.2.5 | O | TLV | 8-48 | +| Short Message Index (2) | 2.5.2.5 | O | TLV | 8-48 | +| : | : | : | : | : | +| Short Message Index (n) | 2.5.2.5 | O | TLV | 8-48 | + +The number of Short Message Indices included in the message may be 0, 1, 2, 3, 4 or 5. + +#### 2.4.2.2 Message + +This response is sent from the MT to the TE when a short message has been requested. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Short Message Data | 2.5.2.6 | M | TLV | 28-181 | + +#### 2.4.2.3 Get Message Failure + +This response is sent from the MT to the TE when a request for a short message cannot be fulfilled. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Last Short Message | 2.5.2.11 | M | V | 1 | +| Cause | 2.5.2.7 | M | V | 1 | + +#### 2.4.2.4 Inc Message + +This indication is sent from the MT to the TE after the MT has been requested to transfer messages of certain categories immediately upon receipt. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Short Message Data | 2.5.2.6 | M | TLV | 28-181 | + +#### 2.4.2.5 Message Arrived + +This indication is sent from the MT to the TE after the MT has been requested to provide an indication of the receipt of certain categories of incoming message. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Short Message Index | 2.5.2.5 | M | TLV | 8-48 | + +#### 2.4.2.6 Insert SMS Complete + +This response is sent by the MT to the TE to indicate that the TE's request to insert a message has been completed. + +| Information element | Reference | Presence | Format | Length | +|--------------------------------------------------------------------------------------------------------------------------|--------------------|----------|--------|----------| +| Message Type | 2.5.1 | M | V | 1 | +| Short Message Reference | 2.5.2.1 | M | V | 1 | +| TP-Message Reference | 3GPP TS 23.040 [3] | C a) | V | 1 | +| SM-Submit-Ack | 2.5.2.15 | O | TLV | 2 to 160 | +| a) The TP-Message Reference is only included if the message had been requested to be transferred over the air interface. | | | | | + +#### 2.4.2.7 Insert SMS Failure + +This response is sent from the MT to the TE to indicate that the attempt to insert an SMS message failed. + +| Information element | Reference | Presence | Format | Length | +|-------------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Cause | 2.5.2.7 | M | V | 1-2 | +| TP-Failure Cause | 2.5.2.13 | O | TLV | 4 | +| Short Message Reference | 2.5.2.1 | O | TV | 2 | + +#### 2.4.2.8 Delete Message Complete + +This response is sent from the MT to the TE to indicate that the request to delete a message from the MT store has been completed. + +| Information element | Reference | Presence | Format | Length | +|-------------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Short Message Reference | 2.5.2.1 | M | V | 1 | + +#### 2.4.2.9 Delete Message Failure + +This response is sent from the MT to the TE to indicate that the request to delete a message from the MT store failed. + +| Information element | Reference | Presence | Format | Length | +|-------------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Short Message Reference | 2.5.2.1 | M | V | 1 | +| Cause | 2.5.2.7 | M | V | 1 | + +#### 2.4.2.10 Unable To Process + +This response is sent from the MT to the TE to indicate that the TE's request could not be processed. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Cause | 2.5.2.7 | M | V | 1 | + +#### 2.4.2.11 End SMS Mode + +This indication is sent from the MT to the TE when the MT autonomously exits from SMS/CBS mode. + +| Information element | Reference | Presence | Format | Length | +|---------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Cause | 2.5.2.7 | M | V | 1 | + +#### 2.4.2.12 Request Confirmed + +This indication is sent from the MT to the TE to indicate that the MT has received the request from the TE and will perform the requested function. + +| Information element | Reference | Presence | Format | Length | +|-------------------------|-----------|----------|--------|--------| +| Message Type | 2.5.1 | M | V | 1 | +| Confirm Type | 2.5.2.12 | M | V | 1 | +| Short Message Reference | 2.5.2.1 | O | TV | 2 | + +## 2.5 General message format and information elements coding + +This clause describes the content of messages for the SMS/CBS mode of the DTE/DCE interface. Within the figures in this clause, the bit designated "bit 1" is transmitted first, followed by bits 2, 3, 4, etc. Similarly, the octet shown at the top of each figure is sent first. + +### 2.5.1 Message Type + +The purpose of the message type is to identify the function of the message being sent. The message type is coded as shown in figure 2.5.1 and table 2.5.1. + +Bit 8 is reserved for possible future use as an extension bit. + +![](608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg) + +| | | | | | | | | | +|---|--------------|---|---|---|---|---|---|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 0 | Message Type | | | | | | | octet 1 | + +**Figure 2.5.1: Message Type** + +**Table 2.5.1: Message Types** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|---|---|---|---|---|------------------------------------| +| 0 | 0 | 0 | - | - | - | - | - | Commands/ Responses issued by TE | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | LIST REQUEST | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | GET MESSAGE | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | GET FIRST MESSAGE | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | GET NEXT MESSAGE | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | TRANSFER INC SMS | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | INDICATE INC SMS | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | TRANSFER INC CBS | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | INSERT SMS | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | DELETE MESSAGE | +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | UNABLE TO PROCESS | +| 0 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | END SMS MODE | +| 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 | ACKNOWLEDGE MESSAGE | +| 0 | 0 | 1 | - | - | - | - | - | Responses/Indications issued by MT | +| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | MESSAGE LIST | +| 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | MESSAGE | +| 0 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | GET MESSAGE FAILURE | +| 0 | 0 | 1 | 0 | 0 | 0 | 1 | 1 | INC MESSAGE | +| 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | MESSAGE ARRIVED | +| 0 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | INSERT SMS COMPLETE | +| 0 | 0 | 1 | 0 | 0 | 1 | 1 | 0 | INSERT SMS FAILURE | +| 0 | 0 | 1 | 0 | 0 | 1 | 1 | 1 | DELETE MESSAGE COMPLETE | +| 0 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | DELETE MESSAGE FAILURE | +| 0 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | UNABLE TO PROCESS | +| 0 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | REQUEST CONFIRMED | +| 0 | 0 | 1 | 1 | 1 | 1 | 1 | 1 | END SMS MODE | + +All other values are reserved. If a reserved Message Type is received then the receiving entity shall return "Unable to Process" with Cause "Command not understood". + +### 2.5.2 Other Information Elements + +Other information elements follow the general coding principles specified in 3GPP TS 24.008 [5], and are described in the following clauses. + +#### 2.5.2.1 Short Message Reference + +The Short Message Reference uniquely identifies a short message stored in the MT. It is an 8 bit number and is allocated by the MT. + +The Short Message Reference information element is coded as shown in figure 2.5.2 and table 2.5.2. + +![](b2ea162a0f53d5e0504b7d28346e0754_img.jpg) + +| | | | | | | | | | | +|--|-----------------------------------------|----------|----------|----------|----------|----------|----------|----------|---------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | octet 1 | +| | Short Message Reference info element id | | | | | | | | | +| | Short Message Reference value | | | | | | | | octet 2 | + +**Figure 2.5.2: Short Message Reference information element** + +**Table 2.5.2: Short Message Reference information element** + +| | +|--------------------------------------------------------------------------------------------------------------------------------------------| +| Short Message Reference value (octet 2). | +| In the Short Message Reference value field bit 8 of octet 2 is the most significant bit and bit 1 of octet 2 is the least significant bit. | +| Short Message Reference values are allocated by the MT. | + +#### 2.5.2.2 SMS Transfer Type + +The SMS Transfer Type indicates to the MT which SMS messages are required to be transferred to the TE. + +The SMS Transfer Type information element is coded as shown in figure 2.5.3 and table 2.5.3. + +![](965aaf7a8b454893b05799d266de6a69_img.jpg) + +| | | | | | | | | | | +|--|--------------------------------------|----------|----------|----------|----------|------------|----------|----------|---------| +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | octet 1 | +| | SMS Transfer Type info element ident | | | | | | | | | +| | 0 | 0 | 0 | 0 | 0 | SMS Txfr | | | octet 2 | +| | Reserved | | | | | Type value | | | | + +**Figure 2.5.3: SMS Transfer Type information element** + +**Table 2.5.3: SMS Transfer Type information element** + +SMS Txfr Type value (octet 2). + +The SMS txfr type is coded as follows: + +| bit 2 | bit 1 | | +|-------|-------|------------------------------------------------| +| 0 | 0 | Transfer no SMS messages | +| 0 | 1 | Transfer SMS messages marked as
TE-specific | +| 1 | 0 | Reserved | +| 1 | 1 | Transfer all SMS messages | + +Bit 3 shows whether to transfer SMS-STATUS-REPORTS + +| Bit 3 | | +|-------|------------------------------------| +| 0 | Do not transfer SMS-STATUS-REPORTS | +| 1 | Transfer SMS-STATUS-REPORTS | + +A receiving entity shall ignore the setting of bits 8-4. If bit 2 is set to 1 and bit 1 is set to 0 then the receiving entity shall return "Unable to Process" with cause "Command Not Understood" + +#### 2.5.2.3 Indication Type + +The Indication Type tells the MT when to notify the TE that an incoming message has been received. + +The Indication Type information element is coded as shown in figure 2.5.4 and table 2.5.4. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------|---|---|---|-----------------------|---|---|---|---------| +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | octet 1 | +| Indication Type info element identifier | | | | | | | | | +| 0 | 0 | 0 | 0 | Indication Type value | | | | octet 2 | +| Reserved | | | | | | | | | + +**Figure 2.5.4: Indication Type information element** + +**Table 2.5.4: Indication Type information element** + +Indication Type value (octet 2). + +The indication type is coded as follows: + +| bit 3 | bit 2 | bit 1 | | +|-------|-------|-------|--------------------------------------------------------| +| 0 | 0 | 0 | Indicate no messages | +| 0 | 0 | 1 | Reserved | +| 0 | 1 | 0 | Indicate all SMS messages | +| 0 | 1 | 1 | Indicate SMS messages marked as
TE-specific | +| 1 | 0 | 0 | Indicate all CBS messages | +| 1 | 0 | 1 | Indicate CBS messages marked as
TE-specific | +| 1 | 1 | 0 | Indicate all CBS and SMS messages | +| 1 | 1 | 1 | Indicate SMS and CBS messages marked
as TE-specific | + +Bit 4 shows whether or not to indicate SMS reports: + +| bit 4 | | +|-------|-----------------------------| +| 0 | Do not indicate SMS reports | +| 1 | Indicate SMS reports | + +A receiving entity shall ignore the setting of bits 8-5. If bits 3 and 2 are set to 0 and bit 1 is set to 1 then the receiving entity shall return "Unable to Process" with cause "Command Not Understood". + +#### 2.5.2.4 Insert Type + +The Insert Type tells the MT what to do with the short message arriving from the TE. + +The Insert Type information element is coded as shown in figure 2.5.5 and table 2.5.5 + +![](6a555cff11e140861ce08db72b01a6a2_img.jpg) + +| | | | | | | | | | +|-------------------------------------|----------|----------|----------|----------|----------|----------------------|----------|---------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | octet 1 | +| Insert Type info element identifier | | | | | | | | | +| 0 | 0 | 0 | 0 | 0 | 0 | Insert
Type value | | octet 2 | +| Reserved | | | | | | | | | + +**Figure 2.5.5: Insert Type information element****Table 2.5.5: Insert Type information element** + +Insert Type value (octet 2). + +The insert type is coded as follows: + +| bit 2 | bit 1 | | +|-------|-------|------------------------------------------------------------| +| 0 | 0 | Reserved | +| 0 | 1 | Store the short message in the MT | +| 1 | 0 | Send the short message over the air | +| 1 | 1 | Store the short message in the MT and send it over the air | + +A receiving entity shall ignore the setting of bits 8-3. If bits 2 and 1 are set to 0 then the receiving entity shall return "Unable to Process" with cause "Command Not Understood" + +#### 2.5.2.5 Short Message Index + +The Short Message Index provides information about each individual short message currently stored in the MT. Two types of Short Message index are provided; one for SMS and one for CBS. + +The Short Message Index (SMS) information element is coded as shown in figure 2.5.6 and table 2.5.6. A Short Message Index may be an SMS-SUBMIT, an SMS-DELIVER or an SMS-STATUS-REPORT. + +The Short Message Index (CBS) information element is coded as shown in figure 2.5.7 and table 2.5.7. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------------|---|---|---|---|---|---|---|----------------------| +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | octet 1 | +| Short Message Index (SMS) info element id | | | | | | | | | +| Length of Short Message Index | | | | | | | | octet 2 | +| Short Message Reference value | | | | | | | | octet 3 | +| Short Message Status | | | | | | | | octet 4 | +| Service Centre Address | | | | | | | | octets
5-n | +| Short Message Header (SMS) | | | | | | | | octets
n+1 - n+31 | + +**Figure 2.5.6: Short Message Index (SMS) information element** + +NOTE: n can take a value between 5 and 18 (inclusive). + +**Table 2.5.6: Short Message Index (SMS) information element** + +Short Message Reference value (octet 3). + +The Short Message Reference value is coded as specified in table 2.5.2. + +Short Message Status (octet 4). + +The Short Message Status is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|---|---|---|---|---|-------------------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | Not read/not sent | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | Read/Sent | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | Not Read | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | Read | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | Not Sent | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | Sent | + +All other values are reserved. + +The receiving entity shall ignore the setting of bits 8-4. + +In addition, if bit 3 is set to 0 then a receiving entity shall ignore the setting of bit 2. Where bit 3 is set to 0, if the message is mobile originated then bit 1 indicates whether the message has been sent to the network. If the message is mobile terminated then bit 1 indicates whether the message has been read. + +Service Centre Address (Octets 5-n). + +The Service Centre Address is coded as the RP-Origination or RP-Destination address specified in 3 TS 24.011 [6]. If the short message is mobile originated, the address will be the RP-Destination address. If the short message is mobile terminated, the address will be the RP-Origination address. The address is of variable length, 1-12 octets. + +Short Message Header (SMS) (Octets n+1 - n+31). + +The Short Message Header (SMS) is coded as a TPDU as described in 3GPP TS 23.040 [3]. In the case of SMS-DELIVER or SMS-SUBMIT, the TP-User-Data is not included, but the TP-User-Data-Length is included. The Short Message Header is of variable length, 6-31 octets. + +![](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------------------|---|---|---|---|---|---|---|------------| +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | octet 1 | +| Short Message Index (CBS) info element id | | | | | | | | | +| Short Message Reference value | | | | | | | | octet 2 | +| Short Message Header (CBS) | | | | | | | | octets 3-8 | + +**Figure 2.5.7: Short Message Index (CBS) information element** + +**Table 2.5.7: Short Message Index (CBS) information element** + +Short Message Reference value (octet 2). + +The Short Message Reference value is coded as specified in table 2.5.2. + +Short Message Header (CBS) (Octets 3-8). + +The Short Message Header (CBS) is coded as described in 3GPP TS 23.041. [4], including SEQUENCE NUMBER, MESSAGE IDENTIFIER, ALPHABET IDENTIFIER and PAGE PARAMETER, but excluding the characters of the message. + +#### 2.5.2.6 Short Message Data + +The Short Message Data information element is a copy of a short message currently stored in the MT. Two types of Short Message Data information element are provided; one for SMS and one for CBS. + +The Short Message Data (SMS) information element is coded as shown in figure 2.5.8 and table 2.5.8. Short Message Data may be an SMS-SUBMIT, an SMS-DELIVER or an SMS-STATUS-REPORT. + +The Short Message Data (CBS) information element is coded as shown in figure 2.5.9 and table 2.5.9. + +![](21d8ca19de468e733e521605b1890767_img.jpg) + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------------|---|---|---|---|---|---|---|------------------| +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | octet 1 | +| Short Message Data (SMS) info element id | | | | | | | | | +| Length of Short Message Data | | | | | | | | octet 2 | +| Short Message Reference value | | | | | | | | octet 3 | +| Short Message Status | | | | | | | | octet 4 | +| Service Centre Address | | | | | | | | octets 5-n | +| Short Message (SMS) | | | | | | | | octets n+1-n+164 | + +**Figure 2.5.8: Short Message Data (SMS) information element** + +NOTE: n can take a value between 5 and 18 (inclusive). + +**Table 2.5.8: Short Message (SMS) information element** + +Short Message Reference value (octet 3). + +The Short Message Reference value is coded as specified in table 2.5.2. + +Short Message Status (octet 4). + +The Short Message Status is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|---|---|---|---|---|-------------------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | Not read/not sent | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | Read/Sent | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | Not Read | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | Read | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | Not Sent | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | Sent | + +All other values are reserved. + +The receiving entity shall ignore the setting of bits 8-4. + +In addition, if bit 3 is set to 0 then a receiving entity shall ignore the setting of bit 2. + +Where bit 3 is set to 0, if the message is mobile originated then bit 1 indicates whether the message has been sent to the network. If the message is mobile terminated then bit 1 indicates whether the message has been read. + +Service Centre Address (Octets 5-n). + +The Service Centre Address is coded as the RP-Origination-Address or RP-Destination Address specified in 3GPP TS 23.040 [3]. + +If the short message is mobile originated, the address will be the RP-Destination address. If the short message is mobile terminated, the address will be the RP-Origination Address. The address is of variable length, 1-12 octets. + +Short Message (SMS) (Octets n+1 - n+164). + +The Short Message (SMS) is coded as a TPDU as described in 3GPP TS 23.040 [3]. + +The Short Message is of variable length, 6-164 octets. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|------------------------------------------|---|---|---|---|---|---|---|---------| +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | octet 1 | +| Short Message Data (CBS) info element id | | | | | | | | octet 2 | +| Short Message Reference value | | | | | | | | octets | +| Short Message (CBS) | | | | | | | | 3-90 | + +**Figure 2.5.9: Short Message Data (CBS) information element****Table 2.5.9: Short Message Data (CBS) information element** + +Short Message Reference value (octet 2). + +The Short Message Reference value is coded as specified in table 2.5.2. + +Short Message (CBS) (Octets 3-90). + +The Short Message (CBS) is coded as described in 3GPP TS 23.041 [4], including SEQUENCE NUMBER, MESSAGE IDENTIFIER, ALPHABET IDENTIFIER, PAGE PARAMETER and CHARACTERS OF THE MESSAGE. + +#### 2.5.2.7 Cause + +The Cause information element provides more detail as to why an error has occurred. The Cause information element is coded as shown in figure 2.5.10 and table 2.5.10. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------|-------------|---|---|---|---|---|---|---------| +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | octet 1 | +| Cause information element identifier | | | | | | | | octet 2 | +| 0
ext | Cause value | | | | | | | octet 3 | +| 3GPP TS 24.011 [6] RP-Cause value | | | | | | | | | + +**Figure 2.5.10: Cause information element** + +**Table 2.5.10: Cause information element** + +Cause value (octet 2). + +The cause is coded as follows: + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|---|---|---|---|---|--------------------------------------------------------------------------------------------------------------------------| +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | No such message | +| | | | | | | | - | - no short message exists with the provided shortmessage reference | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | No memory | +| | | | | | | | - | - the short message cannot be stored due to lack of memory | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | No air interface | +| | | | | | | | - | - submission of the short message cannot be attempted because the mobile is out of coverage | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | Receiving entity busy | +| | | | | | | | - | - the request was not fulfilled because the Receiving entity is busy on another task | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | Command not understood | +| | | | | | | | - | - error in the coding of the command, or command belongs to higher version of protocol of protocol than that implemented | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | Incoming data call | +| | | | | | | | - | - Incoming data call forces MT to exit from SMS mode | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | User-invoked exit | +| | | | | | | | - | - User has taken MT out of SMS by MMI | +| 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | Other error | +| | | | | | | | - | - Any other error not covered here | +| 1 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | Message Transfer failed | +| | | | | | | | - | - The SMS transfer to the SC failed and the 3GPP TS 24.011 [6] error cause is provided in octet 3 | + +All other values are reserved. + +A receiving entity shall treat any reserved codings as "other error". + +3GPP TS 24.011 [6] RP-Cause value (octet 3) + +If this element is included then bit 8 of octet 2 is set to '1'. The error cause included in the RP-Cause over the air interface is directly mapped into this element. This element is only included if the MT attempts to send a short message to the network and that send attempt fails. + +#### 2.5.2.8 Index Count + +The Index Count identifies the number of short message indices contained in a MESSAGE LIST response from the MT to the TE. It is an 8 bit number. + +The Index Count information element is coded as shown in figure 2.5.11 and table 2.5.11. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------|---|---|---|---|---|---|---|---------| +| 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | octet 1 | +| Index Count information element ident | | | | | | | | octet 2 | + +**Figure 2.5.11: Index Count information element** + +**Table 2.5.11: Index Count information element** + +Index Count value (octet 2). + +In the Index Count field bit 8 of octet 2 is the most significant bit and bit 1 of octet 2 is the least significant bit. + +#### 2.5.2.9 CBS Transfer Type + +The CBS Transfer Type indicates to the MT which CBS messages are required to be transferred to the TE. + +The CBS Transfer Type information element is coded as shown in figure 2.5.12 and table 2.5.12. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------|---|---|---|---|---|----------|------------|---------| +| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | octet 1 | +| CBS Transfer Type info element ident | | | | | | | | octet 2 | +| 0 | 0 | 0 | 0 | 0 | 0 | CBS Txfr | Type value | | +| Reserved | | | | | | | | | + +**Figure 2.5.12: CBS Transfer Type information element** + +**Table 2.5.12: CBS Transfer Type information element** + +CBS Txfr Type value (octet 2). + +The CBS txfr type is coded as follows: + +bit 2 bit 1 + +| | | | +|---|---|---------------------------------------------| +| 0 | 0 | Transfer no CBS messages | +| 0 | 1 | Transfer CBS messages marked as TE-specific | +| 1 | 0 | Reserved | +| 1 | 1 | Transfer all CBS messages | + +A receiving entity shall ignore the setting of bits 8-3. If bit 2 is set to 1 and bit 1 is set to 0 then the receiving entity shall return "Unable to Process" with cause "Command Not Understood" + +#### 2.5.2.10 Page Index + +The Page Index indicates to the MT which Page of SMS Indices is required to be transferred. It also indicates to the TE which Page of SMS Indices is being transferred. + +The Page Index information element is coded as shown in figure 2.5.13 and table 2.5.13. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-------------------------------|---|------------------|---|---|---|---|---|---------| +| 0 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | octet 1 | +| Page Index info element ident | | | | | | | | | +| 0 | 0 | Page Index value | | | | | | octet 2 | +| Reserved | | | | | | | | | + +Figure 2.5.13: Page Index information element + +Table 2.5.13: Page Index information element + +Page Index value (octet 2). + +In the Page Index field bit 6 of octet 2 is the most significant bit and bit 1 of octet 2 is the least significant bit. The Page Index can have a value from 1 to 51. + +A receiving entity shall ignore the setting of bits 8 and 7. If the Page Index field has a value of 0 or a value greater than 51 then the receiving entity shall return "Unable to Process" with cause "Command Not Understood" + +#### 2.5.2.11 Last Short Message + +The Last Short Message field indicates to the TE the highest value of Short Message Reference which points to a valid message stored in the MT. The value 0 signifies that there are no short messages stored in the MT. + +The Last Short Message information element is coded as shown in figure 2.5.14 and table 2.5.14. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------------|---|--------------------------|---|---|---|---|---|---------| +| 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | octet 1 | +| Last Short Message info element ident | | | | | | | | | +| | | Last Short Message value | | | | | | octet 2 | + +Figure 2.5.14: Last Short Message information element + +Table 2.5.14: Last Short Message information element + +Last Short Message value (octet 2). + +In the Last Short Message field bit 8 of octet 2 is the most significant bit and bit 1 of octet 2 is the least significant bit. The Last Short Message can have a value from 0 to 255. + +#### 2.5.2.12 Confirm Type + +The Confirm Type field indicates the message to which the REQUEST CONFIRM is a response. + +The Confirm Type information element is coded as shown in figure 2.5.15 and table 2.5.15. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---------------------------------|---|--------------------|---|---|---|---|---|---------| +| 0 | 0 | 0 | 0 | 1 | 1 | 0 | 1 | octet 1 | +| Confirm Type info element ident | | | | | | | | | +| | | Confirm Type value | | | | | | octet 2 | + +Figure 2.5.15: Confirm Type information element + +**Table 2.5.15: Confirm Type information element** + +| | | | | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---|---------------------------------------------------------------------------------------------------| +| Confirm Type value (octet 2). | | | | | | | | | +| The Confirm Type is coded as follows: | | | | | | | | | +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | Reserved | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | Confirm request to transfer incoming SMS messages | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | Confirm request to transfer incoming CBS messages | +| 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | Confirm request to indicate arrival of messages in MT | +| 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | Confirm request to attempt to send short message (actual send is confirmed later; see clause 3.3) | +| All other values are reserved. If any reserved value is received then the receiving entity shall return "Unable to Process" with cause value "Command Not Understood". | | | | | | | | | + +#### 2.5.2.13 TP-Failure Cause + +This optional field is present if provided by the Relay Layer. The TP-Failure Cause is provided from the Service Centre and indicates to the TE the reason why the delivery of the message was unsuccessful. The TP-Failure cause information element is coded as shown in figure 2.5.16 and table 2.5.16. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|--------------------------------------|---|---|---|---|---|---|---|------------| +| 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | octet 1 | +| Cause information element identifier | | | | | | | | | +| Length of Failure cause field | | | | | | | | octet 2 | +| Failure cause | | | | | | | | octets 3-4 | + +**Figure 2.5.16: TP-Failure Cause information element****Table 2.5.16: TP-Failure Cause information element** + +| | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Failure cause (octet 3-4) | +| The failure cause contained in this field is directly mapped from the TP-Failure Cause (TP-FCS) field of the SMS-SUBMIT-REPORT message defined in 3GPP TS 23.040 [3]. | + +#### 2.5.2.14 SM-Deliver-Ack + +This optional field is sent from the TE to the MT to convey the information to be inserted into the SMS-DELIVER-REPORT RP-ACK TPDU sent by the MT to the SC as defined in 3GPP TS 23.040 [3]. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|-----------------------------------------------|---|---|---|---|---|---|---|--------------| +| 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | octet 1 | +| SM-DELIVER-ACK information element identifier | | | | | | | | | +| Length of SMS-DELIVER-REPORT RP-ACK Field | | | | | | | | octet 2 | +| 03.40 SMS-DELIVER-REPORT RP-ACK | | | | | | | | octets 3-166 | + +#### 2.5.2.15 SM-Submit-Ack + +This optional field is sent from the MT to the TE to convey the information to be inserted into the SMS-SUBMIT-REPORT RP-ACK TPDU sent by the SC to the MT as defined in 3GPP TS 23.040 [3]. + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------|---|---|---|---|---|---|--------------|---------| +| 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | octet 1 | +| SM-SUBMIT-ACK information element identifier | | | | | | | octet 2 | | +| Length of SMS-SUBMIT-REPORT RP-ACK Field | | | | | | | octets 3-166 | | + +# 3 Text Mode + +## 3.1 Parameter Definitions + +The following parameters are used in the subsequent clauses which describe all commands. The formats of integer and string types referenced here are defined in V.25ter. The default values are for command parameters, not for result code parameters. + +### Message Storage Parameters + + integer type; value in the range of location numbers supported by the associated memory + + string type; memory from which messages are read and deleted (commands List Messages +CMGL, Read Message +CMGR and Delete Message +CMGD); defined values (others are manufacturer specific): + +"BM" broadcast message storage + +"ME" ME message storage + +"MT" any of the storages associated with ME + +"SM" (U)SIM message storage + +"TA" TA message storage + +"SR" status report storage + + string type; memory to which writing and sending operations are made (commands Send Message from Storage +CMSS and Write Message to Memory +CMGW ); refer for defined values + + string type; memory to which received SMs are preferred to be stored (unless forwarded directly to TE; refer command New Message Indications +CNMI); refer for defined values; received CBMs are always stored in "BM" (or some manufacturer specific storage) unless directly forwarded to TE; received status reports are always stored in "SR" (or some manufacturer specific storage) unless directly forwarded to TE + + integer type in PDU mode (default 0), or string type in text mode (default "REC UNREAD"); indicates the status of message in memory; defined values: + +0 "REC UNREAD" received unread message (i.e. new message) + +1 "REC READ" received read message + +2 "STO UNSENT" stored unsent message (only applicable to SMs) + +3 "STO SENT" stored sent message (only applicable to SMs) + +4 "ALL" all messages (only applicable to +CMGL command) + + integer type; total number of message locations in + + integer type; total number of message locations in + + integer type; total number of message locations in + + integer type; number of messages currently in + + integer type; number of messages currently in + + integer type; number of messages currently in + +### Message Data Parameters + + 3GPP TS 23.040 [3] RP-User-Data element of RP-ACK PDU; format is same as for in case of SMS, but without 3GPP TS 24.011 [6] SC address field and parameter shall be bounded by double quote characters like a normal string type parameter + + string type alphanumeric representation of or corresponding to the entry found in MT phonebook; implementation of this feature is manufacturer specific; used character set should be the one selected with command Select TE Character Set +CSCS (see definition of this command in 3GPP TS 27.007 [9]) + + 3GPP TS 23.040 [3] TP-Command-Data in text mode responses; ME/TA converts each 8-bit octet into two IRA character long hexadecimal number (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65)) + + 3GPP TS 23.040 [3] TP-Command-Type in integer format (default 0) + + 3GPP TS 23.040 [3] TP-Destination-Address Address-Value field in string format; BCD numbers (or GSM 7 bit default alphabet characters) are converted to characters of the currently selected TE character set (refer command +CSCS in 3GPP TS 27.007 [9]); type of address given by + + In the case of SMS: 3GPP TS 23.040 [3] TP-User-Data in text mode responses; format: + +- if indicates that 3GPP TS 23.038 [2] GSM 7 bit default alphabet is used and indicates that 3GPP TS 23.040 [3] TP-User-Data-Header-Indication is not set: + - if TE character set other than "HEX" (refer command Select TE Character Set +CSCS in 3GPP TS 27.007 [9]): ME/TA converts GSM alphabet into current TE character set according to rules of Annex A + - if TE character set is "HEX": ME/TA converts each 7-bit character of GSM 7 bit default alphabet into two IRA character long hexadecimal number (e.g. character Ψ (GSM 7 bit default alphabet decimal 23) is presented as 17 (IRA 49 and 55)) +- if indicates that 8-bit or UCS2 data coding scheme is used, or indicates that 3GPP TS 23.040 [3] TP-User-Data-Header-Indication is set: ME/TA converts each 8-bit octet into two IRA character long hexadecimal number (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65)) + +In the case of CBS: 3GPP TS 23.041 [4] CBM Content of Message in text mode responses; format: + +- if indicates that 3GPP TS 23.038 [2] GSM 7 bit default alphabet is used: + - if TE character set other than "HEX" (refer command +CSCS in 3GPP TS 27.007 [9]): ME/TA converts GSM alphabet into current TE character set according to rules of Annex A + - if TE character set is "HEX": ME/TA converts each 7-bit character of the GSM 7 bit default alphabet into two IRA character long hexadecimal number +- if indicates that 8-bit or UCS2 data coding scheme is used: ME/TA converts each 8-bit octet into two IRA character long hexadecimal number + + depending on the command or result code: 3GPP TS 23.038 [2] SMS Data Coding Scheme (default 0), or Cell Broadcast Data Coding Scheme in integer format + +-
3GPP TS 23.040 [3] TP-Discharge-Time in time-string format: "yy/MM/dd,hh:mm:ss±zz", where characters indicate year (two last digits), month, day, hour, minutes, seconds and time zone. E.g. 6th of May 1994, 22:10:00 GMT+2 hours equals to "94/05/06,22:10:00+08" +- depending on the command or result code: first octet of 3GPP TS 23.040 [3] SMS-DELIVER, SMS-SUBMIT (default 17), SMS-STATUS-REPORT, or SMS-COMMAND (default 2) in integer format +- integer type value indicating in the text mode (+CMGF=1) the length of the message body (or ) in characters; or in PDU mode (+CMGF=0), the length of the actual TP data unit in octets (i.e. the RP layer SMSC address octets are not counted in the length) +- 3GPP TS 23.041 [4] CBM Message Identifier in integer format +- 3GPP TS 23.040 [3] TP-Message-Number in integer format +- 3GPP TS 23.040 [3] TP-Message-Reference in integer format +- 3GPP TS 23.040 [3] TP-Originating-Address Address-Value field in string format; BCD numbers (or GSM 7 bit default alphabet characters) are converted to characters of the currently selected TE character set (refer command +CSCS in TS 07.07); type of address given by +- 3GPP TS 23.041 [4] CBM Page Parameter bits 4-7 in integer format +- 3GPP TS 23.041 [4] CBM Page Parameter bits 0-3 in integer format +- In the case of SMS: 3GPP TS 24.011 [6] SC address followed by 3GPP TS 23.040 [3] TPDU in hexadecimal format: ME/TA converts each octet of TP data unit into two IRA character long hexadecimal number (e.g. octet with integer value 42 is presented to TE as two characters 2A (IRA 50 and 65)) +- In the case of CBS: 3GPP TS 23.041 [4] TPDU in hexadecimal format +- 3GPP TS 23.040 [3] TP-Protocol-Identifier in integer format (default 0) +- 3GPP TS 23.040 [3] TP-Recipient-Address Address-Value field in string format; BCD numbers (or GSM 7 bit default alphabet characters) are converted to characters of the currently selected TE character set (refer command +CSCS in 3GPP TS 27.007 [9]); type of address given by +- 3GPP TS 24.011 [6] RP SC address Address-Value field in string format; BCD numbers (or GSM 7 bit default alphabet characters) are converted to characters of the currently selected TE character set (refer command +CSCS in 3GPP TS 27.007 [9]); type of address given by +- 3GPP TS 23.040 [3] TP-Service-Centre-Time-Stamp in time-string format (refer
) +- 3GPP TS 23.041 [4] CBM Serial Number in integer format +- 3GPP TS 23.040 [3] TP-Status in integer format +- 3GPP TS 24.011 [6] TP-Destination-Address Type-of-Address octet in integer format (when first character of is + (IRA 43) default is 145, otherwise default is 129) +- 3GPP TS 24.011 [6] TP-Originating-Address Type-of-Address octet in integer format (default refer ) +- 3GPP TS 24.011 [6] TP-Recipient-Address Type-of-Address octet in integer format (default refer ) +- 3GPP TS 24.011 [6] RP SC address Type-of-Address octet in integer format (default refer ) +- depending on SMS-SUBMIT setting: 3GPP TS 23.040 [3] TP-Validity-Period either in integer format (default 167) or in time-string format (refer
) +- depending on SMS-SUBMIT setting: 3GPP TS 23.040 [3] TP-Validity-Period either in integer format (default 167), in time-string format (refer
), or if EVPF is supported, in enhanced format (hexadecimal coded string with double quotes) + +## 3.2 General Configuration Commands + +### 3.2.1 Select Message Service +CSMS + +**Table 3.2.1-1: +CSMS Parameter Command Syntax** + +| Command | Possible response(s) | +|-----------------|----------------------------------------------| +| +CSMS= | +CSMS: , ,
+CMS ERROR: | +| +CSMS? | +CSMS: , , , | +| +CSMS=? | +CSMS: (list of supported s) | + +#### Description + +Set command selects messaging service . It returns the types of messages supported by the ME: for mobile terminated messages, for mobile originated messages and for broadcast type messages. If chosen service is not supported by the ME (but is supported by the TA), final result code +CMS ERROR: shall be returned. See chapter Message Service Failure Result Code for a list of values. + +Also read command returns supported message types along the current service setting. + +Test command returns a list of all services supported by the TA. + +#### Defined Values + +: integer type + +- 0 3GPP TS 23.040 [3] and 3GPP TS 23.041 [4] +- 1 3GPP TS 23.040 [3] and 3GPP TS 23.041 [4] (the requirement of setting 1 is mentioned under corresponding command descriptions) +- 2...127 reserved +- 128... manufacturer specific + +, , : integer type + +- 0 type not supported +- 1 type supported + +#### Implementation + +Mandatory if SMS is supported. + +### 3.2.2 Preferred Message Storage +CPMS + +**Table 3.2.2-1: +CPMS Parameter Command Syntax** + +| Command | Possible response(s) | +|----------------------------------|-------------------------------------------------------------------------------------------------------------| +| +CPMS=[, [, ]] | +CPMS: , , , , ,
+CMS ERROR: | +| +CPMS? | +CPMS: , , , , , , , ,
+CMS ERROR: | +| +CPMS=? | +CPMS: (list of supported s) , (list of supported s) ,
(list of supported s) | + +#### Description + +Set command selects memory storages , and to be used for reading, writing, etc. If chosen storage is not appropriate for the ME (but is supported by the TA), final result code +CMS ERROR: shall be returned. See chapter Message Service Failure Result Code for a list of possible values. + +Test command returns lists of memory storages supported by the TA. + +#### Implementation + +Mandatory if SMS is supported. + +### 3.2.3 Message Format +CMGF + +**Table 3.2.3-1: +CMGF Parameter Command Syntax** + +| Command | Possible response(s) | +|-----------------|------------------------------------| +| +CMGF= [] | | +| +CMGF? | +CMGF: | +| +CMGF=? | +CMGF: (list of supported s) | + +#### Description + +Set command tells the TA, which input and output format of messages to use. indicates the format of messages used with send, list, read and write commands and unsolicited result codes resulting from received messages. Mode can be either PDU mode (entire TP data units used) or text mode (headers and body of the messages given as separate parameters). Text mode uses the value of parameter specified by command Select TE Character Set +CSCS to inform the character set to be used in the message body in the TA-TE interface. + +Test command returns supported modes as a compound value. + +#### Defined Values + +: integer type + +0 PDU mode + +1 text mode + +#### Implementation + +Mandatory if SMS is supported also when only one mode implemented. + +### 3.2.4 Enter SMS Block Mode Protocol +CESP + +**Table 3.2.4-1: +CESP Action Command Syntax** + +| Command | Possible response(s) | +|---------|----------------------| +| +CESP | | +| +CESP=? | | + +#### Description + +Execution command sets the TA in SMS block protocol mode. The TA shall return OK (or 0) to confirm acceptance of the command prior to entering the block mode (see clause 2.1.1). The final result code OK (or 0) shall be returned when the block mode is exited. + +NOTE: Commands following +CESP in the AT command line must not be processed by the TA. + +#### Implementation + +Mandatory when block mode implemented. + +### 3.2.5 Message Service Failure Result Code +CMS ERROR + +Final result code +CMS ERROR: indicates an error related to mobile equipment or network. The operation is similar to ERROR final result code. None of the following commands in the same command line is executed. Neither ERROR nor OK final result code shall be returned. ERROR is returned normally when error is related to syntax or invalid parameters. + +#### Defined Values + + values used by common messaging commands: + +| | | +|-----------|----------------------------------------------| +| 0...127 | 3GPP TS 24.011 [6] clause E.2 values | +| 128...255 | 3GPP TS 23.040 [3] clause 9.2.3.22 values. | +| 300 | ME failure | +| 301 | SMS service of ME reserved | +| 302 | operation not allowed | +| 303 | operation not supported | +| 304 | invalid PDU mode parameter | +| 305 | invalid text mode parameter | +| 310 | (U)SIM not inserted | +| 311 | (U)SIM PIN required | +| 312 | PH-(U)SIM PIN required | +| 313 | (U)SIM failure | +| 314 | (U)SIM busy | +| 315 | (U)SIM wrong | +| 316 | (U)SIM PUK required | +| 317 | (U)SIM PIN2 required | +| 318 | (U)SIM PUK2 required | +| 320 | memory failure | +| 321 | invalid memory index | +| 322 | memory full | +| 330 | SMSC address unknown | +| 331 | no network service | +| 332 | network timeout | +| 340 | no +CNMA acknowledgement expected | +| 500 | unknown error | +| ...511 | other values in range 256...511 are reserved | +| 512... | manufacturer specific | + +#### Implementation + +Mandatory if SMS is supported. + +### 3.2.6 Informative Examples + +Setting up a TA supporting SMS: + +``` + +AT+CSMS=? (inquiry of available services in TA) ++CSMS: (0) +OK +AT+CSMS=0;+CPMS=? (set SMS; query available memories) ++CSMS: 1,1,1 (all MT, MO and CBM supported) ++CPMS: ("BM","ME","SM"), ("ME","SM"), ("ME","SM") (CBM, ME and (U)SIM memories for reading,) +OK ME and (U)SIM memories for writing) +AT+CPMS="ME","ME","ME";+CMGF=? (set ME memory; query available message formats) ++CPMS: "ME",5,99,"ME",5,99,"ME",5,99 (five messages in ME, 99 total space) ++CMGF: (0,1) (both text and PDU mode implemented) +OK +AT+CMGF=1;+CSCS=? (select text mode; query available TE character sets) ++CSCS: ("IRA","PCCP437","8859-1") +OK +AT+CSCS="PCCP437" (select PC code page 437) +OK + +``` + +## 3.3 Message Configuration Commands + +### 3.3.1 Service Centre Address +CSCA + +**Table 3.3.1-1: +CSCA Parameter Command Syntax** + +| Command | Possible response(s) | +|------------------------|-----------------------| +| +CSCA=[, ] | | +| +CSCA? | +CSCA: , | +| +CSCA=? | | + +#### Description + +Set command updates the SMSC address, through which mobile originated SMs are transmitted. In text mode, setting is used by send and write commands. In PDU mode, setting is used by the same commands, but only when the length of the SMSC address coded into parameter equals zero. + +#### Implementation + +Mandatory if SMS is supported. + +### 3.3.2 Set Text Mode Parameters +CSMP + +**Table 3.3.2-1: +CSMP Parameter Command Syntax** + +| Command | Possible response(s) | +|----------------------------------------|---------------------------------| +| +CSMP=[[, [, [, ]]]] | | +| +CSMP? | +CSMP: , , , | +| +CSMP=? | | + +#### Description + +Set command is used to select values for additional parameters needed when SM is sent to the network or placed in a storage when text format message mode is selected. It is possible to set the validity period starting from when the SM is received by the SMSC ( is in range 0... 255) or define the absolute time of the validity period termination ( is a string). The format of is given by . If TA supports the EVPF, see 3GPP TS 23.040 [3], it shall be given as a hexadecimal coded string (refer e.g. ) with double quotes. + +NOTE: When storing a SMS-DELIVER from the TE to the preferred memory storage in text mode (refer command Write Message to Memory +CMGW), field can be used for . + +#### Implementation + +Mandatory when text mode implemented. + +### 3.3.3 Show Text Mode Parameters +CSDH + +**Table 3.3.3-1: +CSDH Parameter Command Syntax** + +| Command | Possible response(s) | +|----------------|------------------------------------| +| +CSDH=[] | | +| +CSDH? | +CSDH: | +| +CSDH=? | +CSDH: (list of supported s) | + +#### Description + +Set command controls whether detailed header information is shown in text mode result codes. + +Test command returns supported values as a compound value. + +#### Defined Values + +: integer type + +- 0 do not show header values defined in commands +CSCA and +CSMP (, , , , and ) nor , or in +CMT, +CMGL, +CMGR result codes for SMS-DELIVERs and SMS-SUBMITs in text mode; for SMS-COMMANDs in +CMGR result code, do not show , , , , or +- 1 show the values in result codes + +#### Implementation + +Mandatory when text mode implemented. + +### 3.3.4 Select Cell Broadcast Message Types +CSCB + +**Table 3.3.4-1: +CSCB Parameter Command Syntax** + +| Command | Possible response(s) | +|------------------------------------|------------------------------------| +| +CSCB=[[, [, ]]] | | +| +CSCB? | +CSCB: , , | +| +CSCB=? | +CSCB: (list of supported s) | + +#### Description + +Set command selects which types of CBMs are to be received by the ME. + +Test command returns supported modes as a compound value. + +#### Defined Values + +: integer type + +- 0 message types specified in and are accepted +- 1 message types specified in and are not accepted + +: string type; all different possible combinations of CBM message identifiers (refer ) (default is empty string); e.g. "0,1,5,320-478,922" + +: string type; all different possible combinations of CBM data coding schemes (refer ) (default is empty string); e.g. "0-3,5" + +#### Implementation + +Optional. + +### 3.3.5 Save Settings +CSAS + +**Table 3.3.5-1: +CSAS Action Command Syntax** + +| Command | Possible response(s) | +|-------------------|---------------------------------------| +| +CSAS[=] | +CMS ERROR: | +| +CSAS=? | +CSAS: (list of supported s) | + +#### Description + +Execution command saves active message service settings to a non-volatile memory. A TA can contain several profiles of settings. Settings specified in commands Service Centre Address +CSCA, Set Message Parameters +CSMP and Select Cell Broadcast Message Types +CSCB (if implemented) are saved. Certain settings may not be supported by the storage (e.g. (U)SIM SMS parameters) and therefore can not be saved. See chapter Message Service Failure Result Code for values. + +Test command shall display the supported profile numbers for reading and writing of settings. + +#### Defined Values + +: integer type + +0..255 manufacturer specific profile number where settings are to be stored + +#### Implementation + +Optional. + +### 3.3.6 Restore Settings +CRES + +Table 3.3.6-1: +CRES Action Command Syntax + +| Command | Possible response(s) | +|-------------------|---------------------------------------| +| +CRES[=] | +CMS ERROR: | +| +CRES=? | +CRES: (list of supported s) | + +#### Description + +Execution command restores message service settings from non-volatile memory to active memory. A TA can contain several profiles of settings. Settings specified in commands Service Centre Address +CSCA, Set Message Parameters +CSMP and Select Cell Broadcast Message Types +CSCB (if implemented) are restored. Certain settings may not be supported by the storage (e.g. (U)SIM SMS parameters) and therefore can not be restored. See chapter Message Service Failure Result Code for values. + +#### Defined Values + +: integer type + +0..255 manufacturer specific profile number from where settings are to be restored + +#### Implementation + +Optional. + +### 3.3.7 Informative Examples + +Figure 3.3.7-1 illustrates an example setup of a TE-TA-ME system for SMS. Location of volatile and non-volatile parameter memories, and the operations to change the parameter values are shown. +CSMP is used to set the text mode header values of SMS-SUBMIT (or SMS-DELIVER when received message is written from TE to a storage). The volatile memory may as well be in the ME, or when no volatile memory is used, +CSMP, +CSCA and +CSCB settings are stored directly to non-volatile memory of ME. + +![Diagram illustrating message service parameter procedures between ME, TA, and TE. The diagram shows three main components: ME (Mobile Equipment), TA (Terminal Adapter), and TE (Terminal Equipment). The ME contains 'SMI STORAGES' (text mode parameters for send and write, SMSC address; non-volatile memory) and 'CBM STORAGES' (cell broadcast types to be stored; non-volatile and volatile memories). The TA contains 'text mode parameters for send and write, SMSC address; volatile memory'. The TE sends commands to the TA: 'set SMSC address +CSCA and set text mode parameters +CSMP', 'save +CSAS and restore +CRES', and 'select cell broadcast message types +CSCB'. The TA sends commands to the ME: 'save +CSAS', 'power-up and restore +CRES', and 'save to non-volatile or restore to volatile'.](583e14835ddabad1d8b92a07b82fc31b_img.jpg) + +``` + +graph LR + subgraph ME + subgraph SMI_STORAGES [SMI STORAGES] + SM[text mode parameters for send and write, SMSC address; non-volatile memory] + end + subgraph CBM_STORAGES [CBM STORAGES] + CB[cell broadcast types to be stored; non-volatile and volatile memories] + end + end + subgraph TA + TV[text mode parameters for send and write, SMSC address; volatile memory] + end + subgraph TE + end + + TE -- "set SMSC address +CSCA and set text mode parameters +CSMP" --> TA + TE -- "save +CSAS and restore +CRES" --> TA + TE -- "select cell broadcast message types +CSCB" --> TA + TA -- "save +CSAS" --> SM + TA -- "power-up and restore +CRES" --> SM + TA -- "save to non-volatile or restore to volatile" --> CB + +``` + +Diagram illustrating message service parameter procedures between ME, TA, and TE. The diagram shows three main components: ME (Mobile Equipment), TA (Terminal Adapter), and TE (Terminal Equipment). The ME contains 'SMI STORAGES' (text mode parameters for send and write, SMSC address; non-volatile memory) and 'CBM STORAGES' (cell broadcast types to be stored; non-volatile and volatile memories). The TA contains 'text mode parameters for send and write, SMSC address; volatile memory'. The TE sends commands to the TA: 'set SMSC address +CSCA and set text mode parameters +CSMP', 'save +CSAS and restore +CRES', and 'select cell broadcast message types +CSCB'. The TA sends commands to the ME: 'save +CSAS', 'power-up and restore +CRES', and 'save to non-volatile or restore to volatile'. + +Figure 3.3.7-1: Message service parameter procedures + +In this example, the volatile parameter settings of TA are used to construct messages in text mode. SMSC address setting is used also in PDU mode. The next example illustrates a session to restore the message parameters from the ME to the TA, and to set up the CBM identifiers (and languages) which are wanted to be received: + +``` +AT+CRES (restore settings from non-volatile memory to volatile memory) +OK +AT+CSMP?;+CSCA? (query SM parameters) ++CSMP: 17,167,0,0 (default values for SMS-SUBMIT) ++CSCA: "+358501234567",145 (SMSC address) +OK +AT+CSDH=1 (show all headers in text mode) +OK +AT+CSCB=1 (all CBMs are accepted) +OK +``` + +## 3.4 Message Receiving and Reading Commands + +### 3.4.1 New Message Indications to TE +CNMI + +**Table 3.4.1-1: +CNMI Parameter Command Syntax** + +| Command | Possible response(s) | +|-------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| +CNMI=[[, [, [, [, ]]]]] | +CMS ERROR: | +| +CNMI? | +CNMI: , , , , | +| +CNMI=? | +CNMI: (list of supported s) , (list of supported s) , (list of supported s) , (list of supported s) , (list of supported s) | + +#### Description + +Set command selects the procedure, how receiving of new messages from the network is indicated to the TE when TE is active, e.g. DTR signal is ON. If TE is inactive (e.g. DTR signal is OFF), message receiving should be done as specified in 3GPP TS 23.038 [2]. + +NOTE 1: When DTR signal is not available or the state of the signal is ignored (V.25ter command &D0), reliable message transfer can be assured by using +CNMA acknowledgement procedure. + + controls the processing of unsolicited result codes specified within this command, sets the result code indication routing for SMS-DELIVERs, for CBMs and for SMS-STATUS-REPORTs. defines the handling method for buffered result codes when 1, 2 or 3 is enabled. If ME does not support requested item (although TA does), final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. + +Test command gives the settings supported by the TA as compound values. + +NOTE 2: Command Select Message Service +CSMS should be used to detect ME support of mobile terminated SMs and CBMs, and to define whether a message routed directly to TE should be acknowledged or not (refer command +CNMA). + +#### Defined Values + +: integer type (refer figure 3.4.1-1) + +NOTE 3: The buffering mechanism may as well be located in the ME; the setting affects only to unsolicited result codes specified within this command): + +- 0 Buffer unsolicited result codes in the TA. If TA result code buffer is full, indications can be buffered in some other place or the oldest indications may be discarded and replaced with the new received indications. +- 1 Discard indication and reject new received message unsolicited result codes when TA-TE link is reserved (e.g. in on-line data mode). Otherwise forward them directly to the TE. + +- 2 Buffer unsolicited result codes in the TA when TA-TE link is reserved (e.g. in on-line data mode) and flush them to the TE after reservation. Otherwise forward them directly to the TE. +- 3 Forward unsolicited result codes directly to the TE. TA-TE link specific inband technique used to embed result codes and data when TA is in on-line data mode. + +NOTE 4: It is possible that ME/TA result code buffer is in volatile memory. In this case messages may get lost if the power of ME/TA is switched off before codes are sent to TE. Thus, it is not recommended to use direct message routing (=2 or 3, =2 or 3, or =1) with value 0 or 2. + +![Diagram illustrating the parameter for message routing between ME, TA, and TE. The diagram shows the flow of messages and indications from the ME through the TA to the TE, categorized by values 0, 1, 2, and 3. For mode 0, all messages go through a buffer. For mode 1, CLASS 0 messages go through the buffer while others go directly to the TE. For mode 2, CLASS 0 messages go to the buffer and CLASS 1-3 messages go directly to the TE. For mode 3, all messages go directly to the TE.](e05122559f56af5699789b7118d8fe87_img.jpg) + +The diagram shows the following components and flows: + +- ME (Mobile Equipment):** Sends "received messages and indications" to the TA. +- TA (Terminal Adapter):** Contains sub-components **COMMAND MODE** and **DATA MODE**. It has a **Buffer** and a **TA** label. It routes messages to the TE based on the ** value**. +- TE (Terminal Equipment):** Receives messages and indications from the TA. +- values:** + - 0:** All messages from COMMAND MODE and DATA MODE pass through the Buffer to the TE. + - 1:** CLASS 0 messages from COMMAND MODE pass through the Buffer; other messages from COMMAND MODE and all from DATA MODE go directly to the TE. + - 2:** CLASS 0 messages from COMMAND MODE pass through the Buffer; CLASS 1, 2, and 3 messages from COMMAND MODE and all from DATA MODE go directly to the TE. + - 3:** All messages from both COMMAND MODE and DATA MODE go directly to the TE, bypassing the Buffer. +- Unsolicited result codes:** Indicated by arrows from the Buffer and DATA MODE directly to the TE, labeled with **+CMTI, +CMT, +CBMI, +CBM, +CDSI, +CDS**. + +Diagram illustrating the parameter for message routing between ME, TA, and TE. The diagram shows the flow of messages and indications from the ME through the TA to the TE, categorized by values 0, 1, 2, and 3. For mode 0, all messages go through a buffer. For mode 1, CLASS 0 messages go through the buffer while others go directly to the TE. For mode 2, CLASS 0 messages go to the buffer and CLASS 1-3 messages go directly to the TE. For mode 3, all messages go directly to the TE. + +Figure 3.4.1-1: parameter + +: integer type (the rules for storing received SMs depend on its data coding scheme (refer 3GPP TS 23.038 [2]), preferred memory storage (+CPMS) setting and this value; refer table 3.4.1-2; + +NOTE 5: If AT command interface is acting as the only display device, the ME must support storing of class 0 messages and messages in the message waiting indication group (discard message); refer table 3.4.1-3): + +- 0 No SMS-DELIVER indications are routed to the TE. +- 1 If SMS-DELIVER is stored into ME/TA, indication of the memory location is routed to the TE using unsolicited result code: + ++CMTI: , + +- 2 SMS-DELIVERs (except class 2 messages and messages in the message waiting indication group (store message)) are routed directly to the TE using unsolicited result code: + ++CMT: [], (PDU mode enabled); or + ++CMT: , [], , , , , , , , (text mode enabled; about parameters in italics, refer command Show Text Mode Parameters +CSDH) + +If ME has its own display device then class 0 messages and messages in the message waiting indication group (discard message) may be copied to both ME display and to TE. In this case, ME shall send the acknowledgement to the network (refer table 2). + +Class 2 messages and messages in the message waiting indication group (store message) result in indication as defined in =1. + +- 3 Class 3 SMS-DELIVERs are routed directly to TE using unsolicited result codes defined in =2. Messages of other data coding schemes result in indication as defined in =1. + +**Table 3.4.1-2: parameter** + +| | Receiving procedure for different message data coding schemes (refer 3GPP TS 23.038 [2]) | +|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | no class: as in 3GPP TS 23.038 [2], but use as preferred memory
class 0: as in 3GPP TS 23.038 [2], but use as preferred memory if message is tried to be stored
class 1: as in 3GPP TS 23.038 [2], but use as preferred memory
class 2: as in 3GPP TS 23.038 [2]
class 3: as in 3GPP TS 23.038 [2], but use as preferred memory
message waiting indication group (discard message): as in 3GPP TS 23.038 [2], but use as preferred memory if message is tried to be stored
message waiting indication group (store message): as in 3GPP TS 23.038 [2], but use as preferred memory | +| 1 | as =0 but send indication if message stored successfully | +| 2 | no class: route message to TE
class 0: as in 3GPP TS 23.038 [2], but also route message to TE and do not try to store it in memory
class 1: route message to TE
class 2: as =1
class 3: route message to TE
message waiting indication group (discard message): as in 3GPP TS 23.038 [2], but also route message to TE and do not try to store it in memory
message waiting indication group (store message): as =1 | +| 3 | class 3: route message to TE
others: as =1 | + +**Table 3.4.1-3: SMS-DELIVER result code and acknowledgement summary** + +| | no class or class 1 | class 0 or message waiting indication group (discard) | class 2 or message waiting indication group (store) | class 3 | +|------|---------------------------|-------------------------------------------------------|-----------------------------------------------------|---------------------------| +| 1 | +CMTI | [+CMTI 1 ] | +CMTI | +CMTI | +| 2 | +CMT & +CNMA 3 | +CMT [& +CNMA 2 ] | +CMTI | +CMT & +CNMA 3 | +| 3 | +CMTI | [+CMTI 1 ] | +CMTI | +CMT & +CNMA 3 | + +1) result code is sent when ME does not have other display device than AT interface. +2) acknowledgement command must be sent when +CSMS value equals 1 and ME does not have other display device than AT interface. +3) acknowledgement command must be sent when +CSMS value equals 1. + + integer type (the rules for storing received CBMs depend on its data coding scheme (refer 3GPP TS 23.038 [2]), the setting of Select CBM Types (+CSCB) and this value; refer table 3.4.1-4): + +0 No CBM indications are routed to the TE. + +1 If CBM is stored into ME/TA, indication of the memory location is routed to the TE using unsolicited result code: + ++CBMI: , + +2 New CBMs are routed directly to the TE using unsolicited result code: + ++CBM: (PDU mode enabled); or + ++CBM: , , , , (text mode enabled) + +If ME supports data coding groups which define special routing also for messages other than class 3 (e.g. (U)SIM specific messages), ME may choose not to route messages of such data coding schemes into TE (indication of a stored CBM may be given as defined in =1). + +3 Class 3 CBMs are routed directly to TE using unsolicited result codes defined in =2. If CBM storage is supported, messages of other classes result in indication as defined in =1. + +**Table 3.4.1-4: parameter** + +| | | +|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Receiving procedure for different message data coding schemes (refer 3GPP TS 23.038 [2]) | +| 0 | all schemes: as in 3GPP TS 23.038 [2]; if CBM storage is supported, store message to "BM" (or some manufacturer or data coding scheme specific memory) | +| 1 | all schemes: as =0 but send indication if message stored successfully | +| 2 | all schemes: route message to TE unless ME has detected a special routing to somewhere else (e.g. to (U)SIM; an indication may be sent if message stored successfully) | +| 3 | class 3: route message to TE
others: as =1 (if CBM memory storage is supported) | + +: integer type + +- 0 No SMS-STATUS-REPORTs are routed to the TE. +- 1 SMS-STATUS-REPORTs are routed to the TE using unsolicited result code: + - +CDS: (PDU mode enabled); or + - +CDS: ,,[],[],[,
, (text mode enabled) +- 2 If SMS-STATUS-REPORT is stored into ME/TA, indication of the memory location is routed to the TE using unsolicited result code: + - +CDSI: , + +**Table 3.4.1-5: SMS-STATUS-REPORT result code and acknowledgement summary** + +| | result codes and commands | +|------|--------------------------------------------------------------------------| +| 1 | +CDS & +CNMA 1) | +| 2 | +CDSI | +| 1) | acknowledgement command must be sent when +CSMS value equals 1 | + +: integer type + +- 0 TA buffer of unsolicited result codes defined within this command is flushed to the TE when 1...3 is entered (OK response shall be given before flushing the codes). +- 1 TA buffer of unsolicited result codes defined within this command is cleared when 1...3 is entered. + +#### Implementation + +Mandatory when any of the new message indications implemented. + +### 3.4.2 List Messages +CMGL + +**Table 3.4.2-1: +CMGL Action Command Syntax** + +| Command | Possible response(s) | +|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CMGL[=] | if text mode (+CMGF=1), command successful and SMS-SUBMITs and/or SMS-DELIVERs:
+CMGL: , , , [], [] [, , ][
+CMGL: , , , [], [] [, , ][...]
if text mode (+CMGF=1), command successful and SMS-STATUS-REPORTs:
+CMGL: , , , , [], [], ,
, [
+CMGL: , , , , [], [], ,
, [...]
if text mode (+CMGF=1), command successful and SMS-COMMANDs:
+CMGL: , , , [
+CMGL: , , , [...]
if text mode (+CMGF=1), command successful and CBM storage:
+CMGL: , , , , , [
+CMGL: , , , , , [...]
otherwise:
+CMS ERROR: | +| +CMGL=? | +CMGL: (list of supported s) | + +#### Description + +Execution command returns messages with status value from message storage to the TE. About text mode parameters in italics, refer command Show Text Mode Parameters +CSDH. If status of the message is 'received unread', status in the storage changes to 'received read'. If listing fails, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for values. + +NOTE: If the selected can contain different types of SMs (e.g. SMS-DELIVERs, SMS-SUBMITs, SMS-STATUS-REPORTs and SMS-COMMANDs), the response may be a mix of the responses of different SM types. TE application can recognize the response format by examining the third response parameter. + +Test command shall give a list of all status values supported by the TA. + +#### Implementation + +Optional. + +### 3.4.3 Read Message +CMGR + +**Table 3.4.3-1: +CMGR Action Command Syntax** + +| Command | Possible response(s) | +|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CMGR= | if text mode (+CMGF=1), command successful and SMS-DELIVER:
+CMGR: , , [], [[/, , , , , , ]]
if text mode (+CMGF=1), command successful and SMS-SUBMIT:
+CMGR: , , [] [, , , , , [, , , ]]
if text mode (+CMGF=1), command successful and SMS-STATUS-REPORT:
+CMGR: , , , [], [], [,
, ]]
if text mode (+CMGF=1), command successful and SMS-COMMAND:
+CMGR: , , [, , [], [], [], ]]]
if text mode (+CMGF=1), command successful and CBM storage:
+CMGR: , , , , ,
otherwise:
+CMS ERROR: | +| +CMGR=? | | + +#### Description + +Execution command returns message with location value from message storage to the TE. About text mode parameters in italics, refer command Show Text Mode Parameters +CSDH. If status of the message is 'received unread', status in the storage changes to 'received read'. If reading fails, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for values. + +#### Implementation + +Optional. + +### 3.4.4 New Message Acknowledgement to ME/TA +CNMA + +**Table 3.4.4-1: +CNMA Action Command Syntax** + +| Command | Possible response(s) | +|-----------------------------------------|----------------------| +| if text mode (+CMGF=1):
+CNMA | +CMS ERROR: | +| +CNMA=? | | + +#### Description + +Execution command confirms correct reception of a new message (SMS-DELIVER or SMS-STATUS-REPORT) which is routed directly to the TE (refer command +CNMI table 3.4.1-3 and table 3.4.1-5). This acknowledgement command (causing ME to send RP-ACK to the network) shall be used when +CSMS parameter equals 1. TA shall not send another +CMT or +CDS result code to TE before previous one is acknowledged. + +If ME does not get acknowledgement within required time (network timeout), ME should respond as specified in 3GPP TS 24.011 [6] to the network. ME/TA shall automatically disable routing to TE by setting both and values of +CNMI to zero. + +If command is executed, but no acknowledgement is expected, or some other ME related error occurs, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. + +NOTE: In case that a directly routed message must be buffered in ME/TA (possible when +CNMI parameter equals 0 or 2) or AT interpreter remains too long in a state where result codes cannot be sent to TE (e.g. user is entering a message using +CMGS), acknowledgement (RP-ACK) must be sent to the network without waiting +CNMA command from TE. Later, when buffered result codes are flushed to TE, TE must send +CNMA acknowledgement for each result code. In this way, ME/TA can determine if message should be placed in non-volatile memory and routing to TE disabled (+CNMA not received). Refer command +CNMI for more details how to use parameter reliably. + +#### Implementation + +Mandatory when value 1 of command Select Message Service +CSMS is supported. + +### 3.4.5 Informative Examples + +Message forwarding is done as illustrated in figure 3.4.5-1. Optional +CNMA acknowledgement procedure is not presented. In this example, there is no TA memory for messages and result code buffer is situated in TA. The routing of message waiting indication group (discard message) SMS-DELIVERs equal to class 0 messages, and the routing of message waiting indication group (store message) SMS-DELIVERs equal to class 2 messages. + +![Figure 3.4.5-1: Message receiving procedures. A sequence diagram showing the interaction between ME (Mobile Equipment), TA (Terminal Adapter), and TE (Terminal Equipment). The diagram illustrates the flow of messages and indications based on specific conditions for parameters like , , , and . Messages are either stored in SM or CBM storages within the ME, buffered in the TA, or sent as indications to the TE.](a3083eec2a883ee8327b3c24174df6a9_img.jpg) + +The diagram illustrates the message receiving procedures between ME, TA, and TE. The ME contains 'SM STORAGES' and 'CBM STORAGES'. The TA contains a 'BUFFER'. The TE receives various indications. + +- SM STORAGES:** + - Condition: =2 → Indication: new status report indication +CDSI + - Condition: =1 or =2 (class 2) or =3 (class not 3) → Indication: new MT SM indication +CMTI + - Condition: =2 (class not 2) or =3 (class 3) → Buffer +- SMS-DELIVER:** + - Condition: =0 or =1 or =2 (class 2) or =3 (class not 3) → SM STORAGES + - Condition: =2 (class not 2) or =3 (class 3) → Buffer +- SMS-STATUS-REPORT:** + - Condition: =0 or =2 → Buffer + - Condition: =1 → Indication: status report +CDS +- CBM with allowed message identifier and data coding scheme (refer +CSCB):** + - Condition: =2 or =3 (class 3) → Buffer + - Condition: =1 or =3 (class not 3) → Indication: new CBM indication +CBM +- CBM STORAGES:** + - Condition: =0 or =1 or =3 (class not 3) → CBM STORAGES + +Figure 3.4.5-1: Message receiving procedures. A sequence diagram showing the interaction between ME (Mobile Equipment), TA (Terminal Adapter), and TE (Terminal Equipment). The diagram illustrates the flow of messages and indications based on specific conditions for parameters like , , , and . Messages are either stored in SM or CBM storages within the ME, buffered in the TA, or sent as indications to the TE. + +Figure 3.4.5-1: Message receiving procedures + +Setting new message indications: + +``` +AT+CNMI=? (query new message unsolicited result code modes) ++CNMI: (0-2), (0-3), (0-3), (0,1), (0,1) +OK +AT+CNMI=2,1,0,1,0 (send SM and status report indications to TE when TA in command mode, otherwise buffer) +OK +``` + +In this example, the TA is set so that it should send an unsolicited result code +CMTI: , to the TE when a new SMS-DELIVER is received from the network and stored successfully to storage , and an unsolicited result code +CDS: . . . when a SMS-STATUS-REPORT is received. These result codes are routed to the TE when TA is in command mode, but buffered when in on-line data mode. Now, if new SM is received, it can be read as follows (text mode with no detailed header information; GSM 7 bit default alphabet used in message body): + +``` ++CMTI: "ME", 2 (new message received in index 2) +AT+CMGR=2 (read the message) ++CMGR: "REC UNREAD", "+358507654321", "Mr. Jones", "95/07/03, 17:38:15+04" +This is the Mr. Jones testing +OK +``` + +In the next example all messages of storage are listed (text mode with no detailed header information; GSM 7 bit default alphabet used in message bodies): + +``` + +AT+CMGL="ALL" (read all SMs) ++CMGL: 1,"REC READ","+358501234567","Mr. Smith","95/07/03,17:45:03+04" +This is the body of the message. ++CMGL: 2,"STO UNSENT","+358501234567","Mr. Smith", +This is the body of the reply. +OK + +``` + +The next example shows a method to read new CBMs received from the network (text mode; GSM 7 bit default alphabet used in message bodies): + +``` + +AT+CNMI=2,,2,,0 (CBMs will be sent to the TE) +OK +AT+CPMS="BM";+CMGL (select CBM memory for reading; list all unread CBMs) ++CMGL: 1,"REC UNREAD",100,40,1,3 (first page of three page weather information) +Weather in Finland 3rd of July 1995 ++CMGL: 2,"REC UNREAD",100,40,2,3 (second page of three page weather information) +Helsinki: cloudy, snow storms, -20 degrees Celsius, wind -14 m/s NE ++CMGL: 3,"REC UNREAD",100,40,3,3 (third page of three page weather information) +Tampere: sunny, 40 degrees Celsius, wind 1 m/s SW +OK + +``` + +## 3.5 Message Sending and Writing Commands + +### 3.5.1 Send Message +CMGS + +**Table 3.5.1-1: +CMGS Action Command Syntax** + +| Command | Possible response(s) | +|---------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| if text mode (+CMGF=1):
+CMGS=[, ]
text is entered | if text mode (+CMGF=1) and sending successful:
+CMGS: [, ]
if sending fails:
+CMS ERROR: | +| +CMGS=? | | + +#### Description + +Execution command sends message from a TE to the network (SMS-SUBMIT). Message reference value is returned to the TE on successful message delivery. Optionally (when +CSMS value is 1 and network supports) is returned. Values can be used to identify message upon unsolicited delivery status report result code. If sending fails in a network or an ME error, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. This command should be abortable. + +#### Description + +Execution command sends message from a TE to the network (SMS-SUBMIT). Message reference value is returned to the TE on successful message delivery. Value can be used to identify message upon unsolicited delivery status report result code. If sending fails in a network or an ME error, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. This command should be abortable. + +- entered text (3GPP TS 23.040 [3] TP-Data-Unit) is sent to address and all current settings (refer Set Text Mode Parameters +CSMP and Service Centre Address +CSCA) are used to construct the actual PDU in ME/TA. +- the TA shall send a four character sequence (IRA 13, 10, 62, 32) after command line is terminated with ; after that text can be entered from TE to ME/TA. +- the DCD signal shall be in ON state while text is entered. +- the echoing of entered characters back from the TA is controlled by V.25ter echo command E. +- the entered text should be formatted as follows: + - if (set with +CSMP) indicates that 3GPP TS 23.038 [2] GSM 7 bit default alphabet is used and indicates that 3GPP TS 23.040 [3] TP-User-Data-Header-Indication is not set: + +- if TE character set other than "HEX" (refer command Select TE Character Set +CSCS in 3GPP TS 27.007 [9]): ME/TA converts the entered text into the GSM 7 bit default alphabet according to rules of Annex A; backspace can be used to delete last character and carriage returns can be used (previously mentioned four character sequence shall be sent to the TE after every carriage return entered by the user); +- if TE character set is "HEX": the entered text should consist of two IRA character long hexadecimal numbers which ME/TA converts into the GSM 7 bit default alphabet characters. (e.g. 17 (IRA 49 and 55) will be converted to character II (GSM 7 bit default alphabet 23)). +- if indicates that 8-bit or UCS2 data coding scheme is used or indicates that 3GPP TS 23.040 [3] TP-User-Data-Header-Indication is set: the entered text should consist of two IRA character long hexadecimal numbers which ME/TA converts into 8-bit octet (e.g. two characters 2A (IRA 50 and 65) will be converted to an octet with integer value 42). +- sending can be cancelled by giving character (IRA 27). +- (IRA 26) must be used to indicate the ending of the message body. + +#### Implementation + +Optional. + +### 3.5.2 Send Message from Storage +CMSS + +**Table 3.5.2-1: +CMSS Action Command Syntax** + +| Command | Possible response(s) | +|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| +CMSS=[, [, ]] | if text mode (+CMGF=1) and sending successful:
+CMSS: [, ]
if sending fails:
+CMS ERROR: | +| +CMSS=? | | + +#### Description + +Execution command sends message with location value from preferred message storage to the network (SMS-SUBMIT or SMS-COMMAND). If new recipient address is given for SMS-SUBMIT, it shall be used instead of the one stored with the message. Reference value is returned to the TE on successful message delivery. Optionally (when +CSMS value is 1 and network supports) is returned. Values can be used to identify message upon unsolicited delivery status report result code. If sending fails in a network or an ME error, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. This command should be abortable. + +#### Implementation + +Optional. + +### 3.5.3 Write Message to Memory +CMGW + +**Table 3.5.3-1: +CMGW Action Command Syntax** + +| Command | Possible response(s) | +|-----------------------------------------------------------------------------------------------------------------------|-------------------------------------| +| if text mode (+CMGF=1):
+CMGW[=[, [, ]]]
text is entered | +CMGW:
+CMS ERROR: | +| +CMGW=? | | + +#### Description + +Execution command stores message (either SMS-DELIVER or SMS-SUBMIT) to memory storage . Memory location of the stored message is returned. By default message status will be set to 'stored unsent', but parameter allows also other status values to be given. The entering of text is done similarly as specified in command Send Message +CMGS. If writing fails, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for values. + +NOTE: SMS-COMMANDs and SMS-STATUS-REPORTs can not be stored in text mode. + +#### Implementation + +Optional. + +### 3.5.4 Delete Message +CMGD + +**Table 3.5.4-1: +CMGD Action Command Syntax** + +| Command | Possible response(s) | +|--------------------------------|-------------------------------------------------------------------------------| +| +CMGD=
[, ] | +CMS ERROR: | +| +CMGD=? | +CMGD: (list of supported
s) [, (list of
supported s) ] | + +#### Description + +Execution command deletes message from preferred message storage location . If is present and not set to 0 then the ME shall ignore and follow the rules for shown below. If deleting fails, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for values. + +Test command shows the valid memory locations and optionally the supported values of . + +: integer type, indicating multiple message deletion request as follows: + +- 0 Delete the message specified in +- 1 Delete all read messages from preferred message storage, leaving unread messages and stored mobile originated messages (whether sent or not) untouched +- 2 Delete all read messages from preferred message storage and sent mobile originated messages, leaving unread messages and unsent mobile originated messages untouched +- 3 Delete all read messages from preferred message storage, sent and unsent mobile originated messages leaving unread messages untouched. +- 4 Delete all messages from preferred message storage including unread messages. + +#### Implementation + +Optional. + +### 3.5.5 Send Command +CMGC + +**Table 3.5.5-1: +CMGC Action Command Syntax** + +| Command | Possible response(s) | +|------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| if text mode (+CMGF=1):
+CMGC=, [, [, [, [, ] ] ] ]
text is entered | if text mode (+CMGF=1) and
sending successful:
+CMGC: [, ]
if sending fails:
+CMS ERROR: | + +| | | +|---------|--| +| +CMGC=? | | +|---------|--| + +#### Description + +Execution command sends a command message from a TE to the network (SMS-COMMAND). The entering of text (3GPP TS 23.040 [3] TP-Command-Data) is done similarly as specified in command Send Message +CMGS, but the format is fixed to be a sequence of two IRA character long hexadecimal numbers which ME/TA converts into 8-bit octets (refer +CMGS). Message reference value is returned to the TE on successful message delivery. Optionally (when +CSMS value is 1 and network supports) is returned. Values can be used to identify message upon unsolicited delivery status report result code. If sending fails in a network or an ME error, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. This command should be abortable. + +#### Implementation + +Optional. + +### 3.5.6 More Messages to Send +CMMS + +**Table 3.5.6-1: +CMMS Parameter Command Syntax** + +| Command | Possible response(s) | +|-------------|---------------------------------| +| +CMMS=[] | | +| +CMMS? | +CMMS: | +| +CMMS=? | +CMMS: (list of supported s) | + +#### Description + +Set command controls the continuity of SMS relay protocol link. When feature is enabled (and supported by network) multiple messages can be sent much faster as link is kept open. + +Test command returns supported values as a compound value. + +#### Defined Values + +: integer type + +- 0 disable +- 1 keep enabled until the time between the response of the latest message send command (+CMGS, +CMSS, etc.) and the next send command exceeds 1-5 seconds (the exact value is up to ME implementation), then ME shall close the link and TA switches automatically back to 0 +- 2 enable (if the time between the response of the latest message send command and the next send command exceeds 1-5 seconds (the exact value is up to ME implementation), ME shall close the link but TA shall not switch automatically back to =0) + +#### Implementation + +Optional. + +### 3.5.7 Informative Examples + +Figure 3.5.7-1 is an example of a TE-TA-ME setup when messages are sent to network or stored to ME. The volatile memory may as well be in the ME, or a non-volatile memory may be used instead when constructing messages. + +![Sequence diagram illustrating Message service send and write procedures between ME, TA, and TE. The diagram shows four message types: SMS-SUBMIT, SMS-SUBMIT, SMS-SUBMIT, and SMS-COMMAND. The ME (Mobile Equipment) contains an SM STORAGES box. The TA (Terminal Adapter) contains a volatile memory box. The TE (Terminal Equipment) is on the right. Arrows show the flow of messages and write operations between these components.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +``` + +sequenceDiagram + participant ME + participant TA + participant TE + Note left of ME: SM STORAGES + Note right of TA: volatile memory + ME->>TE: SMS-SUBMIT + ME->>TA: write +CMGW + TA->>TE: send from storage +CMSS + ME->>TE: SMS-SUBMIT + ME->>TA: write +CMGW + TA->>TE: text mode send +CMGS and write +CMGW + ME->>TE: SMS-SUBMIT + ME->>TA: write +CMGW + TA->>TE: PDU mode send +CMGS and write +CMGW + ME->>TE: SMS-COMMAND + TA->>TE: in text mode, add SMSC address (optional in PDU mode) + TA->>TE: send command +CMGC + +``` + +Sequence diagram illustrating Message service send and write procedures between ME, TA, and TE. The diagram shows four message types: SMS-SUBMIT, SMS-SUBMIT, SMS-SUBMIT, and SMS-COMMAND. The ME (Mobile Equipment) contains an SM STORAGES box. The TA (Terminal Adapter) contains a volatile memory box. The TE (Terminal Equipment) is on the right. Arrows show the flow of messages and write operations between these components. + +Figure 3.5.7-1: Message service send and write procedures + +An example of sending a GSM 7 bit default alphabet message in text mode and a SMS-STATUS-REPORT is wanted: + +``` + +AT+CNMI? (check that status reports are routed to TE) ++CNMI: 2,1,0,1,0 +OK +AT+CSMP=49,167,0,0 (status report wanted; otherwise default settings) +OK +AT+CMGS="+358501234567" (start editing a message) +> This the first line. (edit first line and press carriage return) +> This is the last line.^Z (edit second line and send message by pressing control-Z) ++CMGS: 10 (success: message reference 10 returned from SMSC) +OK ++CDS: 2,10,"+358501234567",145,"95/07/04/13:12:14+04", +"95/07/04/13:12:20+04",0 (status report of successful message delivery received) + +``` + +Storing an unsent message in memory, sending it from there, and deleting it: + +``` + +AT+CPMS? (check memory settings) ++CPMS: "ME",4,10,"ME",4,10,"ME",4,10 +OK +AT+CMGW="9501231234" (write message) +> This is the message body^Z ++CMGW: 7 (index number in storage returned) +OK +AT+CMSS=7 (send from storage) ++CMSS: 12 (success: reference value 12 sent from SC) +OK +AT+CMGD=7 (delete message) +OK + +``` + +# 4 PDU Mode + +## 4.0 General + +The PDU mode uses the same commands and responses as the Text Mode described in clause 3. However, the following commands and responses have a different format. In the PDU mode, a complete SMS Message including all header information is passed as a binary string. This binary string is composed of hexadecimal IA5 characters as defined in clause 3 above under "Message Data Parameters". + +## 4.1 List Messages +CMGL + +Table 4.1-1: +CMGL Action Command Syntax + +| Command | Possible response(s) | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CMGL [] | if PDU mode (+CMGF=0) and command successful:
+CMGL: , , [],
[+CMGL: , , [],
[...]]
otherwise:
+CMS ERROR: | +| +CMGL=? | +CMGL: (list of supported s) | + +### Description + +Execution command returns messages with status value from preferred message storage to the TE. Entire data units are returned. If status of the message is 'received unread', status in the storage changes to 'received read'. If listing fails, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for values. + +Test command shall give a list of all status values supported by the TA. + +### Implementation + +Optional. + +## 4.2 Read Message +CMGR + +Table 4.2-1: +CMGR Action Command Syntax + +| Command | Possible response(s) | +|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| +CMGR= | if PDU mode (+CMGF=0) and command successful:
+CMGR: , [],
otherwise:
+CMS ERROR: | +| +CMGR=? | | + +### Description + +Execution command returns message with location value from preferred message storage to the TE. Status of the message and entire message data unit is returned. If status of the message is 'received unread', status in the storage changes to 'received read'. If reading fails, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for values. + +### Implementation + +Optional. + +## 4.3 Send Message +CMGS + +Table 4.3-1: +CMGS Action Command Syntax + +| Command | Possible response(s) | +|-----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| if PDU mode (+CMGF=0):
+CMGS=
PDU is given | if PDU mode (+CMGF=0) and sending successful:
+CMGS: [, ]
if sending fails:
+CMS ERROR: | +| +CMGS=? | | + +### Description + +Execution command sends message from a TE to the network (SMS-SUBMIT). Message reference value is returned to the TE on successful message delivery. Optionally (when +CSMS value is 1 and network supports) is returned. Values can be used to identify message upon unsolicited delivery status report result code. If sending fails in a network or an ME error, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. This command should be abortable. + +- must indicate the number of octets coded in the TP layer data unit to be given (i.e. SMSC address octets are excluded). +- the TA shall send a four character sequence (IRA 13, 10, 62, 32) after command line is terminated with ; after that PDU can be given from TE to ME/TA. +- the DCD signal shall be in ON state while PDU is given. +- the echoing of given characters back from the TA is controlled by V.25ter echo command E. +- the PDU shall be hexadecimal format (similarly as specified for ) and given in one line; ME/TA converts this coding into the actual octets of PDU. +- when the length octet of the SMSC address (given in the PDU) equals zero, the SMSC address set with command Service Centre Address +CSCA is used; in this case the SMSC Type-of-Address octet shall not be present in the PDU, i.e. TPDU starts right after SMSC length octet. +- sending can be cancelled by giving character (IRA 27). +- (IRA 26) must be used to indicate the ending of PDU. + +### Implementation + +Optional. + +## 4.4 Write Message to Memory +CMGW + +Table 4.4-1: +CMGW Action Command Syntax + +| Command | Possible response(s) | +|------------------------------------------------------------------------------------------------|-------------------------------------| +| if PDU mode (+CMGF=0):
+CMGW=[, ] PDU is given | +CMGW:
+CMS ERROR: | +| +CMGW=? | | + +### Description + +Execution command stores a message to memory storage . Memory location of the stored message is returned. By default message status will be set to 'stored unsent', but parameter allows also other status values to be given. (ME/TA manufacturer may choose to use different default values for different message types.) The entering of PDU is done similarly as specified in command Send Message +CMGS. If writing fails, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for values. + +### Implementation + +Optional. + +## 4.5 Send Command +CMGC + +Table 4.5-1: +CMGC Action Command Syntax + +| Command | Possible response(s) | +|-----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| if PDU mode (+CMGF=0):
+CMGC=
PDU is given | if PDU mode (+CMGF=0) and sending successful:
+CMGC: [, ]
if sending fails:
+CMS ERROR: | +| +CMGC=? | | + +### Description + +Execution command sends a command message from a TE to the network (SMS-COMMAND). The entering of PDU is done similarly as specified in command Send Message +CMGS. Message reference value is returned to the TE on successful message delivery. Optionally (when +CSMS value is 1 and network supports) is returned. Values can be used to identify message upon unsolicited delivery status report result code. If sending fails in a network or an ME error, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. This command should be abortable. + +### Implementation + +Optional. + +## 4.6 New Message Acknowledgement to ME/TA +CNMA + +**Table 4.6-1: +CNMA Action Command Syntax** + +| Command | Possible response(s) | +|-----------------------------------------------------------------------------------------------------|------------------------------------------------------------------| +| if PDU mode (+CMGF=0):
+CNMA[=[, [
PDU is given ]]] | +CMS ERROR: | +| +CNMA=? | if PDU mode (+CMGF=0):
+CNMA: (list of supported s) | + +### Description + +Execution command confirms reception of a new message (SMS-DELIVER or SMS-STATUS-REPORT) which is routed directly to the TE (refer command +CNMI table 3.4.1-3 and table 3.4.1-5). This acknowledgement command shall be used when +CSMS parameter equals 1. In PDU mode, it is possible to send either positive (RP-ACK) or negative (RP-ERROR) acknowledgement to the network. Parameter defines which one will be sent. Optionally (when is greater than zero) an acknowledgement TPDU (SMS-DELIVER-REPORT for RP-ACK or RP-ERROR) may be sent to the network. The entering of PDU is done similarly as specified in command Send Message +CMGS, except that the format of is used instead of (i.e. SMSC address field is not present). PDU shall not be bounded by double quotes. TA shall not send another +CMT or +CDS result code to TE before previous one is acknowledged. + +If ME does not get acknowledgement within required time (network timeout), ME should respond as specified in 3GPP TS 24.011 [6] to the network. ME/TA shall automatically disable routing to TE by setting both and values of +CNMI to zero. + +If command is executed, but no acknowledgement is expected, or some other ME related error occurs, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. + +**NOTE:** In case that a directly routed message must be buffered in ME/TA (possible when +CNMI parameter equals 0 or 2) or AT interpreter remains too long in a state where result codes cannot be sent to TE (e.g. user is entering a message using +CMGS), acknowledgement (RP-ACK) must be sent to the network without waiting +CNMA command from TE. Later, when buffered result codes are flushed to TE, TE must send +CNMA [=0] acknowledgement for each result code. In this way, ME/TA can determine if message should be placed in non-volatile memory and routing to TE disabled (+CNMA [=0] not received). Refer command +CNMI for more details how to use parameter reliably. + +Test command returns a list of supported values. If the only value supported is 0, the device does not support sending of TPDU. + +### Defined Values + +: integer type + +0 command operates similarly as defined for the text mode + +- 1 send RP-ACK (or buffered result code received correctly) +- 2 send RP-ERROR (if PDU is not given, ME/TA shall send SMS-DELIVER-REPORT with 3GPP TS 23.040 [3] TP-FCS value set to 'FF' (unspecified error cause)) + +### Implementation + +Mandatory when value 1 of command Select Message Service +CSMS is supported. + +## 4.7 Send Message from Storage +CMSS + +**Table 4.7-1: +CMSS Action Command Syntax** + +| Command | Possible response(s) | +|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| +CMSS=[, [, ]] | if PDU mode (+CMGF=0) and sending successful:
+CMSS: [, ]
if sending fails:
+CMS ERROR: | +| +CMSS=? | | + +### Description + +Execution command sends message with location value from message storage to the network (SMS-SUBMIT or SMS-COMMAND). If new recipient address is given for SMS-SUBMIT, it shall be used instead of the one stored with the message. Reference value is returned to the TE on successful message delivery. Optionally (when +CSMS value is 1 and network supports) is returned. Values can be used to identify message upon unsolicited delivery status report result code. If sending fails in a network or an ME error, final result code +CMS ERROR: is returned. See chapter Message Service Failure Result Code for a list of values. This command should be abortable. + +### Implementation + +Optional. + +# Annex A (normative): Character Set Conversions for SMS Text Mode + +The following conversions to and from 3GPP TS 23.038 [2] GSM 7 bit default alphabet are defined: + +| TE char set | bits/char | Commands | +|----------------------------|-----------|-------------------------| +| PC Code Page 437 | 8 | +CMGF=1;+CSCS="PCCP437" | +| PC Danish/Norwegian | 8 | +CMGF=1;+CSCS="PCDN" | +| ISO 8859 Latin 1 | 8 | +CMGF=1;+CSCS="8859-1" | +| IRA | 7 | +CMGF=1;+CSCS="IRA" | +| GSM 7 bit default alphabet | 7 | +CMGF=1;+CSCS="GSM" | + +The tables below show which GSM 7 bit default alphabet value corresponds to the 7 or 8 bit value of external character set. The TE character set value is computed by adding column value, 00H through F0H (70H for 7 bits/char), with the row value (00H through 0FH). All values are in hexadecimal, but the H suffix is not used. When text mode is implemented, it is mandatory for a TA to have at least one conversion which include the conversion table of IRA (e.g. PC Code Page 437 does). Additional conversions can be defined by manufacturers. It is manufacturer specific if the TE set is actually converted to GSM 7 bit default alphabet set in the TA or in the ME, and if the TE set is converted to a ME specific set in the TA before converting it to GSM 7 bit default alphabet set when message is sent to the network. It is recommended that characters which cannot be converted to GSM 7 bit default alphabet set are deleted. + +Conversion from IRA to GSM 7 bit default alphabet: + +| | 00 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | +|----|-----|----|----|----|----|----|----|----| +| 00 | - | - | 20 | 30 | 00 | 50 | - | 70 | +| 01 | - | - | 21 | 31 | 41 | 51 | 61 | 71 | +| 02 | - | - | 22 | 32 | 42 | 52 | 62 | 72 | +| 03 | - | - | 23 | 33 | 43 | 53 | 63 | 73 | +| 04 | - | - | 02 | 34 | 44 | 54 | 64 | 74 | +| 05 | - | - | 25 | 35 | 45 | 55 | 65 | 75 | +| 06 | - | - | 26 | 36 | 46 | 56 | 66 | 76 | +| 07 | - | - | 27 | 37 | 47 | 57 | 67 | 77 | +| 08 | - | - | 28 | 38 | 48 | 58 | 68 | 78 | +| 09 | - | - | 29 | 39 | 49 | 59 | 69 | 79 | +| 0A | LF | - | 2A | 3A | 4A | 5A | 6A | 7A | +| 0B | - | - | 2B | 3B | 4B | - | 6B | - | +| 0C | - | - | 2C | 3C | 4C | - | 6C | - | +| 0D | CR- | - | 2D | 3D | 4D | - | 6D | - | +| 0E | - | - | 2E | 3E | 4E | - | 6E | - | +| 0F | - | - | 2F | 3F | 4F | 11 | 6F | - | + +Conversion from PCCP437 (PC-8 Code Page 437) to GSM 7 bit default alphabet: + +| | 00 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | A0 | B0 | C0 | D0 | E0 | F0 | +|----|----|----|----|----|----|----|----|----|-----------------|-----------------|------------------|----|----|----|----|----| +| 00 | - | - | 20 | 30 | 00 | 50 | - | 70 | 09 | 1F | 61 10 | - | - | - | - | - | +| 01 | - | - | 21 | 31 | 41 | 51 | 61 | 71 | 7E | 1D | 69 11 | - | - | - | 1E | - | +| 02 | - | - | 22 | 32 | 42 | 52 | 62 | 72 | 05 | 1C | 6F 12 | - | - | - | 13 | - | +| 03 | - | - | 23 | 33 | 43 | 53 | 63 | 73 | 61 1 | 6F 7 | 75 13 | - | - | - | - | - | +| 04 | - | - | 02 | 34 | 44 | 54 | 64 | 74 | 7B | 7C | 7D | - | - | - | 18 | - | +| 05 | - | 5F | 25 | 35 | 45 | 55 | 65 | 75 | 7F | 08 | 5D | - | - | - | - | - | +| 06 | - | - | 26 | 36 | 46 | 56 | 66 | 76 | 0F | 75 8 | - | - | - | - | - | - | +| 07 | - | - | 27 | 37 | 47 | 57 | 67 | 77 | 09 2 | 06 | - | - | - | - | - | - | +| 08 | - | - | 28 | 38 | 48 | 58 | 68 | 78 | 65 3 | 79 9 | 60 | - | - | - | 12 | - | +| 09 | - | - | 29 | 39 | 49 | 59 | 69 | 79 | 65 4 | 5C | - | - | - | - | 19 | - | +| 0A | LF | - | 2A | 3A | 4A | 5A | 6A | 7A | 04 | 5E | - | - | - | - | 15 | - | +| 0B | - | - | 2B | 3B | 4B | - | 6B | - | 69 5 | - | - | - | - | - | - | - | +| 0C | - | - | 2C | 3C | 4C | - | 6C | - | 69 6 | 01 | - | - | - | - | - | - | +| 0D | CR | - | 2D | 3D | 4D | - | 6D | - | 07 | 03 | 40 | - | - | - | - | - | +| 0E | - | - | 2E | 3E | 4E | - | 6E | - | 5B | - | - | - | - | - | - | - | +| 0F | - | - | 2F | 3F | 4F | 11 | 6F | - | 0E | - | - | - | - | - | - | - | + +1 : â ⇒ a    2 : ç ⇒ Ç    3 : ê ⇒ e    4 : ë ⇒ e    5 : ï ⇒ i +6 : î ⇒ i    7 : ô ⇒ o    8 : û ⇒ u    9 : ÿ ⇒ y    10 : á ⇒ a +11 : í ⇒ i    12 : ó ⇒ o    13 : ú ⇒ u + +Conversion from PCDN (PC-8 Danish/ Norwegian) to GSM 7 bit default alphabet: + +| | 00 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | A0 | B0 | C0 | D0 | E0 | F0 | +|----|----|----|----|----|----|----|----|----|-----------------|-----------------|------------------|----|----|----|----|----| +| 00 | - | - | 20 | 30 | 00 | 50 | - | 70 | 09 | 1F | 61 10 | - | - | - | - | - | +| 01 | - | - | 21 | 31 | 41 | 51 | 61 | 71 | 7E | 1D | 69 11 | - | - | - | 1E | - | +| 02 | - | - | 22 | 32 | 42 | 52 | 62 | 72 | 05 | 1C | 6F 12 | - | - | - | 13 | - | +| 03 | - | - | 23 | 33 | 43 | 53 | 63 | 73 | 61 1 | 6F 7 | 75 13 | - | - | - | - | - | +| 04 | - | - | 02 | 34 | 44 | 54 | 64 | 74 | 7B | 7C | 7D | - | - | - | 18 | - | +| 05 | - | 5F | 25 | 35 | 45 | 55 | 65 | 75 | 7F | 08 | 5D | - | - | - | - | - | +| 06 | - | - | 26 | 36 | 46 | 56 | 66 | 76 | 0F | 75 8 | - | - | - | - | - | - | +| 07 | - | - | 27 | 37 | 47 | 57 | 67 | 77 | 09 2 | 06 | - | - | - | - | - | - | +| 08 | - | - | 28 | 38 | 48 | 58 | 68 | 78 | 65 3 | 79 9 | 60 | - | - | - | 12 | - | +| 09 | - | - | 29 | 39 | 49 | 59 | 69 | 79 | 65 4 | 5C | - | - | - | - | 19 | - | +| 0A | LF | - | 2A | 3A | 4A | 5A | 6A | 7A | 04 | 5E | - | - | - | - | 15 | - | +| 0B | - | - | 2B | 3B | 4B | - | 6B | - | 69 5 | 0C | - | - | - | - | - | - | +| 0C | - | - | 2C | 3C | 4C | - | 6C | - | 69 6 | 01 | - | - | - | - | - | - | +| 0D | CR | - | 2D | 3D | 4D | - | 6D | - | 07 | 0B | 40 | - | - | - | - | - | +| 0E | - | - | 2E | 3E | 4E | - | 6E | - | 5B | - | - | - | - | - | - | - | +| 0F | - | - | 2F | 3F | 4F | 11 | 6F | - | 0E | - | - | - | - | - | - | - | + +1 : â ⇒ a    2 : ç ⇒ Ç    3 : ê ⇒ e    4 : ë ⇒ e    5 : ï ⇒ i +6 : î ⇒ i    7 : ô ⇒ o    8 : û ⇒ u    9 : ÿ ⇒ y    10 : á ⇒ a +11 : í ⇒ i    12 : ó ⇒ o    13 : ú ⇒ u + +Conversion from 8859-1 (ISO 8859 Latin 1) to GSM 7 bit default alphabet: + +| | 00 | 10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | A0 | B0 | C0 | D0 | E0 | F0 | +|----|----|----|----|----|----|----|----|----|----|----|----|----|------------------|------------------|------------------|------------------| +| 00 | - | - | 20 | 30 | 00 | 50 | - | 70 | - | - | - | - | 41 1 | - | 7F | - | +| 01 | - | - | 21 | 31 | 41 | 51 | 61 | 71 | - | - | 40 | - | 41 2 | 5D | 61 20 | 7D | +| 02 | - | - | 22 | 32 | 42 | 52 | 62 | 72 | - | - | - | - | 41 3 | 4F 12 | 61 21 | 08 | +| 03 | - | - | 23 | 33 | 43 | 53 | 63 | 73 | - | - | 01 | - | 41 4 | 4F 13 | 61 22 | 6F 29 | +| 04 | - | - | 02 | 34 | 44 | 54 | 64 | 74 | - | - | 24 | - | 5B | 4F 14 | 7B | 6F 30 | +| 05 | - | - | 25 | 35 | 45 | 55 | 65 | 75 | - | - | 03 | - | 0E | 4F 15 | 0F | 6F 31 | +| 06 | - | - | 26 | 36 | 46 | 56 | 66 | 76 | - | - | - | - | 1C | 5C | 1D | 7C | +| 07 | - | - | 27 | 37 | 47 | 57 | 67 | 77 | - | - | 5F | - | 09 | - | 09 23 | - | +| 08 | - | - | 28 | 38 | 48 | 58 | 68 | 78 | - | - | - | - | 45 5 | 0B | 04 | 0C | +| 09 | - | - | 29 | 39 | 49 | 59 | 69 | 79 | - | - | - | - | 1F | 55 16 | 05 | 06 | +| 0A | LF | - | 2A | 3A | 4A | 5A | 6A | 7A | - | - | - | - | 45 6 | 55 17 | 65 24 | 75 32 | +| 0B | - | - | 2B | 3B | 4B | - | 6B | - | - | - | - | - | 45 7 | 55 18 | 65 25 | 75 33 | +| 0C | - | - | 2C | 3C | 4C | - | 6C | - | - | - | - | - | 49 8 | 5E | 07 | 7E | +| 0D | CR | - | 2D | 3D | 4D | - | 6D | - | - | - | - | - | 49 9 | 59 19 | 69 26 | 79 34 | +| 0E | - | - | 2E | 3E | 4E | - | 6E | - | - | - | - | - | 49 10 | - | 69 27 | - | +| 0F | - | - | 2F | 3F | 4F | 11 | 6F | - | - | - | - | 60 | 49 11 | 1E | 69 28 | 79 35 | + +1 : À ⇒ A    2 : Á ⇒ A    3 : Â ⇒ A    4 : Ã ⇒ A    5 : È ⇒ E +6 : Ê ⇒ E    7 : Ë ⇒ E    8 : Ì ⇒ I    9 : Í ⇒ I    10 : Î ⇒ I +11 : Ï ⇒ I    12 : Ò ⇒ O    13 : Ó ⇒ O    14 : Ô ⇒ O    15 : Õ ⇒ O +16 : Ù ⇒ U    17 : Ú ⇒ U    18 : Û ⇒ U    19 : Ý ⇒ Y    20 : á ⇒ a +21 : â ⇒ a    22 : ã ⇒ a    23 : ç ⇒ Ç    24 : ê ⇒ e    25 : ë ⇒ e +26 : í ⇒ i    27 : î ⇒ i    28 : ï ⇒ i    29 : ó ⇒ o    30 : ô ⇒ o +31 : õ ⇒ o    32 : ú ⇒ u    33 : û ⇒ u    34 : ý ⇒ y    35 : ÿ ⇒ y + +Conversions from GSM 7 bit default alphabet to above character sets are otherwise straightforward, but no conversions of the characters listed below tables are applied. + +Character conversion when a national language locking shift table as defined in 3GPP TS 23.038 [2] is used, is outside the scope of this specification. + +# --- Annex B (informative): Example of processing a data block + +## B.1 Example state diagrams for the block receiver + +The state diagrams on the following two pages show how the receiver component at the block level could work. In this example the received octets are processed in two stages. + +Stage 1 is a low level function which detects the unique start and end markers, and removes any stuffing octets. The results of this stage are passed to stage 2. Any unexpected octet value after a DLE will be indicated as 'abort'. + +Stage 2 assembles the message content and the BCS octets, using octets passed from stage 1 and the 'start' and 'end' indications. A 'start' will always reset the process to state 1 from any state. An 'abort' will always cause a return to state 0 where a 'start' will be awaited. When an 'end' is received in state 1, the following two octets are checked as the BCS. If the BCS is correct, the message content is passed to another stage of the receiver for processing of the message content. + +## --- B.2 Example of coding and decoding a data block + +The last page of this annex shows the coding of an example message at a transmitter, and the decoding stages at a receiver which has the two stages of processing as described above. + +In this example, the message content and the BCS both contain an octet with a value of 10 hex. Therefore the message as transmitted over the interface has additional stuffing octets (00 hex) inserted after these octets. The receiver first detects the start and end markers, and removes the stuffing octets. Finally the BCS is checked. + +### EXAMPLE STATE DIAGRAMS FOR THE BLOCK RECEIVER + +The block receiver can be considered as two stages. Stage 1 detects start and end markers, and removes stuffing characters. Stage 2 assembles the received message and checks the BCS. + +![Block diagram showing the flow from Octets from the DTE/DCE interface through STAGE 1 and STAGE 2 to produce Message blocks.](68a5a1a1a761c652b4b4c56da7cf9914_img.jpg) + +The diagram shows a linear process flow. On the left, an arrow labeled "Octets from the DTE/DCE interface" points into a rectangular box labeled "STAGE 1". An arrow labeled "Octets, with separate Start, End and Abort indications." points from "STAGE 1" to another rectangular box labeled "STAGE 2". Finally, an arrow labeled "Message blocks" points out from "STAGE 2" to the right. + +Block diagram showing the flow from Octets from the DTE/DCE interface through STAGE 1 and STAGE 2 to produce Message blocks. + +### STATE TRANSITIONS IN STAGE 1 + +![State transition diagram for Stage 1 with two states: 0 Idle and 1 Wait for STX, ETX or NUL.](ad555483986d7170a46ce72d164b5bc8_img.jpg) + +The state transition diagram for Stage 1 consists of two states and several transitions. State "0 Idle" is an oval at the top. A vertical downward arrow labeled "DLE" leads to state "1 Wait for STX, ETX or NUL", which is also an oval. From state "0 Idle", a diagonal downward-right arrow labeled "any other octet n" leads to a hexagonal action box "octet = n", which then points to a terminal oval "0". From state "1", four diagonal arrows point downwards to different action boxes: "STX" leads to "'Start'", "NUL" leads to "octet = DLE", "ETX" leads to "'End'", and "any other octet" leads to "'Abort'". Each of these four action boxes points to its own terminal oval "0". Additionally, a self-loop arrow labeled "DLE" is shown on state "1". + +State transition diagram for Stage 1 with two states: 0 Idle and 1 Wait for STX, ETX or NUL. + +Figure B.1 + +![A complex flowchart diagram with multiple decision nodes and process steps, heavily obscured by black redaction bars. The diagram appears to be a state transition or process flow diagram with circular nodes for states and rectangular boxes for transitions or actions.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +The diagram is a complex flowchart that has been almost entirely redacted with black bars. The visible structure includes: + +- A top oval node containing a 'C' and 'H'. +- A rectangular process box below it. +- A circular decision node labeled '1' with 'del' and 'del' labels. +- Transitions leading to rectangular boxes containing 'del' and 'del'. +- Another circular decision node labeled '2' with 'del' and 'del' labels. +- Transitions leading to rectangular boxes containing 'del' and 'del'. +- A third circular decision node labeled '3' with 'del' and 'del' labels. +- Transitions leading to rectangular boxes containing 'del' and 'del'. +- A diamond-shaped decision node containing 'del' and 'del'. +- A final rectangular process box at the bottom containing 'del' and 'del'. +- Terminal circular nodes at the ends of various paths. + +A complex flowchart diagram with multiple decision nodes and process steps, heavily obscured by black redaction bars. The diagram appears to be a state transition or process flow diagram with circular nodes for states and rectangular boxes for transitions or actions. + +Figure B.2 + +### **Example of coding / decoding a message at the DTE/DCE interface** + +![](376f80eb8a41369e87da63a0210d173e_img.jpg) + +Example message to be sent + +| | | | | | | +|-----|-----|-----|-----|-----|-----| +| 00H | 10H | 20H | 30H | 40H | 50H | +|-----|-----|-----|-----|-----|-----| + +↓ +Calculate BCS + +BCS prepared + +| | | | | | | +|-----|-----|-----|-----|-----|-----| +| 00H | 10H | 20H | 30H | 40H | 50H | +|-----|-----|-----|-----|-----|-----| + +| | | +|------------|-----| +| BCS
MSB | LSB | +| FFH | 10H | + +↓ +Insert stuffing octets, and add start & end markers + +Message as transmitted + +| | | | | | | | | | | | | | | +|--------------|------------|-------------------|-----|------------|-----|-----|-----|-----|------------|------------|-----|-----|------------| +| start marker | | message content * | | | | | | | end marker | | BCS | | * | +| DLE
10H | STX
02H | 00H | 10H | NUL
00H | 20H | 30H | 40H | 50H | DLE
10H | ETX
03H | FFH | 10H | NUL
00H | + +↓ +Message transferred over DTE/DCE interface + +\* = stuffing octet + +Message as received (no errors) + +| | | | | | | | | | | | | | | +|--------------|------------|-------------------|-----|------------|-----|-----|-----|-----|------------|------------|-----|-----|------------| +| start marker | | message content * | | | | | | | end marker | | BCS | | * | +| DLE
10H | STX
02H | 00H | 10H | NUL
00H | 20H | 30H | 40H | 50H | DLE
10H | ETX
03H | FFH | 10H | NUL
00H | + +↓ +Detect start & end markers, and remove stuffing octets + +Output from receiver stage 1 + +| | | | | | | | | +|---------|-----|-----|-----|-----|-----|-----|-------| +| 'Start' | 00H | 10H | 20H | 30H | 40H | 50H | 'End' | +|---------|-----|-----|-----|-----|-----|-----|-------| + +| | | +|------------|-----| +| BCS
MSB | LSB | +| FFH | 10H | + +↓ +Check BCS + +Output from receiver stage 2 + +| | | | | | | +|-----|-----|-----|-----|-----|-----| +| 00H | 10H | 20H | 30H | 40H | 50H | +|-----|-----|-----|-----|-----|-----| + +**Figure B.3** + +### EXAMPLE STATE DIAGRAMS FOR THE BLOCK RECEIVER + +The block receiver can be considered as two stages. Stage 1 detects start and end markers, and removes stuffing characters. Stage 2 assembles the received message and checks the BCS. + +![Block diagram of the block receiver stages.](977811d1c73b74f801be9f4c376694ca_img.jpg) + +A block diagram showing the flow of data through two stages. An arrow labeled "Octets from the DTE/DCE interface" points to a box labeled "STAGE 1". An arrow labeled "Octets, with separate Start, End and Abort indications." points from "STAGE 1" to a box labeled "STAGE 2". An arrow labeled "Message blocks" points out from "STAGE 2". + +Block diagram of the block receiver stages. + +#### STATE TRANSITIONS IN STAGE 1 + +![State transition diagram for Stage 1 of the block receiver.](4ca4ef49a4f79d5621932651f7ae3f5e_img.jpg) + +A state transition diagram for Stage 1. It starts with an initial state "0 Idle" (oval). A transition labeled "DLE" leads to state "1 Wait for STX, ETX or NUL" (oval). From state 1, a transition labeled "any other octet n" leads to a decision box "octet = n", which then leads to state "0" (oval). From state 1, a transition labeled "STX" leads to a decision box "'Start'", which leads to state "0" (oval). From state 1, a transition labeled "NUL" leads to a decision box "octet = DLE", which leads to state "0" (oval). From state 1, a transition labeled "ETX" leads to a decision box "'End'", which leads to state "0" (oval). From state 1, a transition labeled "'Abort'" leads to a decision box "'Abort'", which leads to state "0" (oval). There is also a self-loop transition labeled "DLE" on state 1. + +State transition diagram for Stage 1 of the block receiver. + +Figure B.4 + +![A complex flowchart diagram with multiple decision nodes and process steps, heavily obscured by black redaction bars. The diagram includes oval start/end nodes, rectangular process nodes, and diamond decision nodes connected by arrows.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +The diagram is a flowchart that has been almost entirely redacted with black bars. The visible structure is as follows: + +- Start Node:** An oval at the top containing a 'C' and 'H'. +- Process Node:** A rectangle below the start node, containing two redacted lines of text. +- Decision Node 1:** An oval below the first process node, containing a '1' and 'AND' (partially redacted). It has three outgoing arrows: + - Left: To a rectangle with two redacted lines, which then leads to a circle with a redacted symbol. + - Down: To Decision Node 2. + - Right: To a rectangle with two redacted lines, which leads to another rectangle with two redacted lines, which then leads to a circle with a redacted symbol. +- Decision Node 2:** An oval below Decision Node 1, containing a '2' and 'AND' (partially redacted). It has three outgoing arrows: + - Left: To a rectangle with two redacted lines, which then leads to a circle with a redacted symbol. + - Down: To a rectangle with two redacted lines. + - Right: To a circle with a redacted symbol. +- Decision Node 3:** An oval below the process node following Decision Node 2, containing a '3' and 'AND' (partially redacted). It has three outgoing arrows: + - Left: To a rectangle with two redacted lines, which then leads to a circle with a redacted symbol. + - Down: To a rectangle with two redacted lines. + - Right: To a circle with a redacted symbol. +- Decision Node 4:** A diamond shape below the process node following Decision Node 3, containing 'AND' (partially redacted). It has two outgoing arrows: + - Right: To a circle with a redacted symbol. + - Down: To a chevron-shaped process node with two redacted lines. +- End Node:** A circle at the bottom of the flow, containing a redacted symbol. + +A complex flowchart diagram with multiple decision nodes and process steps, heavily obscured by black redaction bars. The diagram includes oval start/end nodes, rectangular process nodes, and diamond decision nodes connected by arrows. + +Figure B.5 + +### **Example of coding / decoding a message at the DTE/DCE interface** + +![](74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg) + +Example message to be sent + +| | | | | | | +|-----|-----|-----|-----|-----|-----| +| 00H | 10H | 20H | 30H | 40H | 50H | +|-----|-----|-----|-----|-----|-----| + +↓ +Calculate BCS + +BCS prepared + +| | | | | | | +|-----|-----|-----|-----|-----|-----| +| 00H | 10H | 20H | 30H | 40H | 50H | +|-----|-----|-----|-----|-----|-----| + +| | | +|-----|-----| +| BCS | | +| MSB | LSB | +| FFH | 10H | + +↓ +Insert stuffing octets, and add start & end markers + +Message as transmitted + +| | | | | | | | | | | | | | | +|--------------|-----|-------------------|-----|-----|-----|-----|-----|-----|------------|-----|-----|-----|-----| +| start marker | | message content * | | | | | | | end marker | | BCS | | * | +| DLE | STX | 00H | 10H | NUL | 20H | 30H | 40H | 50H | DLE | ETX | FFH | 10H | NUL | +| 10H | 02H | | | 00H | | | | | 10H | 03H | | | 00H | + +↓ +Message transferred over DTE/DCE interface + +\* = stuffing octet + +Message as received (no errors) + +| | | | | | | | | | | | | | | +|--------------|-----|-------------------|-----|-----|-----|-----|-----|-----|------------|-----|-----|-----|-----| +| start marker | | message content * | | | | | | | end marker | | BCS | | * | +| DLE | STX | 00H | 10H | NUL | 20H | 30H | 40H | 50H | DLE | ETX | FFH | 10H | NUL | +| 10H | 02H | | | 00H | | | | | 10H | 03H | | | 00H | + +↓ +Detect start & end markers, and remove stuffing octets + +Output from receiver stage 1 + +| | | | | | | | | +|---------|-----|-----|-----|-----|-----|-----|-------| +| 'Start' | 00H | 10H | 20H | 30H | 40H | 50H | 'End' | +|---------|-----|-----|-----|-----|-----|-----|-------| + +| | | +|-----|-----| +| BCS | | +| MSB | LSB | +| FFH | 10H | + +↓ +Check BCS + +Output from receiver stage 2 + +| | | | | | | +|-----|-----|-----|-----|-----|-----| +| 00H | 10H | 20H | 30H | 40H | 50H | +|-----|-----|-----|-----|-----|-----| + +**Figure B.6** + +# Annex C (informative): Change History + +| TSG-T# | TDoc | VER | CR | REV | REL | CAT | WORKITEM | SUBJECT | NEW_VER | +|--------|-----------|--------|------|-----|--------|-----|----------|--------------------------------------------------------------------|---------| +| T#3 | | | New | | | | | Creation of 3GPP 27.005 v1.0.0 out of GSM 07.05 v7.0.0 | 3.0.0 | +| T#6 | TP-99237 | 3.0.0 | 001 | | R99 | F | TEI | Adaptations for UMTS | 3.1.0 | +| T#11 | - | 3.1.0 | - | | Rel-4 | | | Upgrade to Rel-4 | 4.0.0 | +| T#13 | TP-010221 | 4.0.0 | 002 | | Rel-4 | F | TEI4 | Conversion of GSM to 3GPP references | 4.1.0 | +| T#16 | TP-020103 | 4.1.0 | 004 | | Rel-4 | F | TI-ATC | Correction in description of +CNMA | 4.2.0 | +| T#16 | - | 4.2.0 | - | | Rel-5 | | | Upgrade to Rel-5 | 5.0.0 | +| T#26 | - | 5.0.0 | - | | Rel-6 | | | Upgrade to Rel-6 | 6.0.0 | +| | | 6.0.0 | | | | | | Make figure 0.1 visible | 6.0.1 | +| CT#31 | CP-060126 | 6.0.1 | 005 | | Rel-7 | F | TEI7 | Correction to and in examples | 7.0.0 | +| CT#39 | CP-080137 | 7.0.0 | 006 | | Rel-8 | | TEI8 | Language specific extension of GSM7 alphabet | 8.0.0 | +| CT#46 | | 8.0.0 | | | Rel-9 | | | Upgrade to Rel-9 | 9.0.0 | +| CT#51 | CP-110197 | 9.0.0 | 0007 | | Rel-10 | F | TEI10 | Conditions for supporting SMS related AT commands | 10.0.0 | +| | | 10.0.0 | | | Rel-10 | | | Make invisible figures visible | 10.0.1 | +| CT#54 | CP-110882 | 10.0.1 | 0008 | | Rel-11 | F | TEI11 | Specification of integer type definitions of AT-command parameters | 11.0.0 | \ No newline at end of file diff --git a/marked/Rel-11/27_series/27007/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg b/marked/Rel-11/27_series/27007/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72238577b35936e3de84d5e650374e1285d72535 --- /dev/null +++ b/marked/Rel-11/27_series/27007/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b725328604a4feb4d4ace4c590e31f5f702e74cc04457d7f7d7ff16ec40e739 +size 53122 diff --git a/marked/Rel-11/27_series/27007/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg b/marked/Rel-11/27_series/27007/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c466b6aa364eaa7b5392b179d2c758dc239bf333 --- /dev/null +++ b/marked/Rel-11/27_series/27007/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4426f39d123b1a9818d8390855ee875f2bffcd0dd620f84a03a1afa66abd0328 +size 65333 diff --git a/marked/Rel-11/27_series/27007/3afc450f57bb02851ab66705657a9b74_img.jpg b/marked/Rel-11/27_series/27007/3afc450f57bb02851ab66705657a9b74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2b5cd36cc257205931e69275d56d9d1b3cad5d5 --- /dev/null +++ b/marked/Rel-11/27_series/27007/3afc450f57bb02851ab66705657a9b74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d2b0092ce55d9a2d1e995e0044aae439c854b07e65c02c13bc2b943b71fd270 +size 183727 diff --git a/marked/Rel-11/27_series/27007/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg b/marked/Rel-11/27_series/27007/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c997de1246c361f0f56f2611e9eafa76db58ea4f --- /dev/null +++ b/marked/Rel-11/27_series/27007/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6c5b1f1fca99eca29248d513f190fad287b1fca319a88e183f89cb64950313c +size 29755 diff --git a/marked/Rel-11/27_series/27007/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-11/27_series/27007/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70529e37066c0950d39e2d33d5ad8f52c0b743fb --- /dev/null +++ b/marked/Rel-11/27_series/27007/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca43d5d1bd792c4e9608278c89ff677b977ffd65e8e3ad3ee0fcbe29145167eb +size 37733 diff --git a/marked/Rel-11/27_series/27007/507613acfd7f6ef6af724a2005f24024_img.jpg b/marked/Rel-11/27_series/27007/507613acfd7f6ef6af724a2005f24024_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4161a28f9a5e52a2ce8febd91b687bbebefc3fd8 --- /dev/null +++ b/marked/Rel-11/27_series/27007/507613acfd7f6ef6af724a2005f24024_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2058598214fa1603c2352122a57c6ef4fbea2eef426a5109927beb1f9f77df7b +size 137376 diff --git a/marked/Rel-11/27_series/27007/57d06c23c0581d12a25fc6b00d707834_img.jpg b/marked/Rel-11/27_series/27007/57d06c23c0581d12a25fc6b00d707834_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef5c6b42a0fa80c2d6b98dede803d6a39883f1d6 --- /dev/null +++ b/marked/Rel-11/27_series/27007/57d06c23c0581d12a25fc6b00d707834_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd6420db6552ec7cb34339a53ca7e165a808bb634e8f5467272c233359d5bee3 +size 115169 diff --git a/marked/Rel-11/27_series/27007/80f17085454be1e2afdf63635f2fca3f_img.jpg b/marked/Rel-11/27_series/27007/80f17085454be1e2afdf63635f2fca3f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..079ceedfb6922d274281eb52c58ef504d79213e9 --- /dev/null +++ b/marked/Rel-11/27_series/27007/80f17085454be1e2afdf63635f2fca3f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:062192910c89093b2e2cdee104640d14aebb602a268035e6a6fd26e57a7b1b8a +size 28957 diff --git a/marked/Rel-11/27_series/27007/933ecd14c858bf3fc919222d8e357bc8_img.jpg b/marked/Rel-11/27_series/27007/933ecd14c858bf3fc919222d8e357bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0d233947fd01e3ef03e3b7d4250ab70023c26f9 --- /dev/null +++ b/marked/Rel-11/27_series/27007/933ecd14c858bf3fc919222d8e357bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2de081f61dcee64968611cde15013ad47efa2907dda05c2cfa499ea4574c046a +size 39568 diff --git a/marked/Rel-11/27_series/27007/9a95030b736214bb8620597c97e17358_img.jpg b/marked/Rel-11/27_series/27007/9a95030b736214bb8620597c97e17358_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0932657ac03079c6902d147f5587f083bf3ed78 --- /dev/null +++ b/marked/Rel-11/27_series/27007/9a95030b736214bb8620597c97e17358_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74c150cff9390fec8bec42f7863bc46fc45a7bc9618663e80fe8b564d1a5b0c9 +size 38655 diff --git a/marked/Rel-11/27_series/27007/d337002e2fdea9a701abca00b7e56539_img.jpg b/marked/Rel-11/27_series/27007/d337002e2fdea9a701abca00b7e56539_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82b61e06074c094adb0c3c5e8b81134a50abf397 --- /dev/null +++ b/marked/Rel-11/27_series/27007/d337002e2fdea9a701abca00b7e56539_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b982507a6adcd9a21e1ff5479a51ebdb49743855e958a04c0843e8d8982152ba +size 5601 diff --git a/marked/Rel-11/27_series/27007/dbbc0baac7341cda76cc4f8355dce23f_img.jpg b/marked/Rel-11/27_series/27007/dbbc0baac7341cda76cc4f8355dce23f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c1a79b5bcf946cc1b4cab1535fcd4293a339042 --- /dev/null +++ b/marked/Rel-11/27_series/27007/dbbc0baac7341cda76cc4f8355dce23f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8f91ce62d0578fa9291013c52b96b2b1d4e10a1aecc206b3641e94aa74b5105 +size 53273 diff --git a/marked/Rel-11/27_series/27007/e0ca65b56cefdde601aaff41ce7cdb93_img.jpg b/marked/Rel-11/27_series/27007/e0ca65b56cefdde601aaff41ce7cdb93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9387d8f17826389d1165b1ffef2298279445f71f --- /dev/null +++ b/marked/Rel-11/27_series/27007/e0ca65b56cefdde601aaff41ce7cdb93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ee7135d558b8f4a167eea35eb0a71a97554917d2fe99e7586f093ec4a05bc6e +size 39100 diff --git a/marked/Rel-11/27_series/27007/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-11/27_series/27007/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81af23a95413ba0062d3b911cf2160403601039e --- /dev/null +++ b/marked/Rel-11/27_series/27007/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f981f7c9013d9a49b3343702e5eb4ec36ccb189f8eca69ab836b94b1eff98ba6 +size 21024 diff --git a/marked/Rel-11/27_series/27007/f0a296eb755122511ad4e49b7650b867_img.jpg b/marked/Rel-11/27_series/27007/f0a296eb755122511ad4e49b7650b867_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f614ece2c94245963b848ff513b33850f627cdcf --- /dev/null +++ b/marked/Rel-11/27_series/27007/f0a296eb755122511ad4e49b7650b867_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f031893a26f4778f2701f481a427fc8e28c2813e314a0fb51cfbed435c597f3 +size 5073 diff --git a/marked/Rel-11/27_series/27007/raw.md b/marked/Rel-11/27_series/27007/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6a78c0ef3a5255bcc53da2ed73ca58d924915ae7 --- /dev/null +++ b/marked/Rel-11/27_series/27007/raw.md @@ -0,0 +1,13510 @@ + + + + + + +# Contents + +| | | +|----------------------------------------------------------------------|----| +| Foreword..... | 9 | +| 1 Scope..... | 9 | +| 2 References..... | 10 | +| 3 Definitions and abbreviations..... | 16 | +| 3.1 Definitions..... | 16 | +| 3.2 Abbreviations..... | 16 | +| 4 AT command syntax..... | 17 | +| 4.0 General..... | 17 | +| 4.1 Command line..... | 17 | +| 4.2 Information responses and result codes..... | 18 | +| 4.3 ITU-T Recommendation V.250 [14] TE-TA interface commands..... | 18 | +| 5 General commands..... | 19 | +| 5.0 General..... | 19 | +| 5.1 Request manufacturer identification +CGMI..... | 19 | +| 5.2 Request model identification +CGMM..... | 20 | +| 5.3 Request revision identification +CGMR..... | 20 | +| 5.4 Request product serial number identification +CGSN..... | 21 | +| 5.5 Select TE character set +CSCS..... | 21 | +| 5.6 Request international mobile subscriber identity +CIMI..... | 22 | +| 5.7 Multiplexing mode +CMUX..... | 23 | +| 5.8 ITU-T Recommendation V.250 [14] generic TA control commands..... | 25 | +| 5.9 PCCA STD-101 [17] select wireless network +WS46..... | 25 | +| 5.10 Informative examples..... | 26 | +| 6 Call control commands and methods..... | 27 | +| 6.0 General..... | 27 | +| 6.1 Select type of address +CSTA..... | 27 | +| 6.2 ITU-T Recommendation V.250 [14] dial command D..... | 28 | +| 6.3 Direct dialling from phonebooks..... | 28 | +| 6.4 Call mode +CMOD..... | 30 | +| 6.4A Voice call mode +CVMOD..... | 30 | +| 6.5 Hangup call +CHUP..... | 31 | +| 6.6 Alternating mode call control method..... | 31 | +| 6.7 Select bearer service type +CBST..... | 33 | +| 6.8 Radio link protocol +CRLP..... | 35 | +| 6.9 Service reporting control +CR..... | 36 | +| 6.10 Extended error report +CEER..... | 37 | +| 6.11 Cellular result codes +CRC..... | 38 | +| 6.12 HSCSD device parameters +CHSD..... | 39 | +| 6.13 HSCSD transparent call configuration +CHST..... | 40 | +| 6.14 HSCSD non-transparent call configuration +CHSN..... | 41 | +| 6.15 HSCSD current call parameters +CHSC..... | 41 | +| 6.16 HSCSD parameters report +CHSR..... | 42 | +| 6.17 HSCSD automatic user initiated upgrading +CHSU..... | 43 | +| 6.18 HSCSD non-transparent asymmetry configuration +CHSA..... | 43 | +| 6.19 Single numbering scheme +CSNS..... | 44 | +| 6.20 Voice hangup control +CVHU..... | 45 | +| 6.21 CCITT V.120 [36] rate adaption protocol +CV120..... | 45 | +| 6.22 Settings date format +CSDF..... | 46 | +| 6.23 Silence command +CSIL..... | 47 | +| 6.24 Settings time format +CSTF..... | 48 | +| 6.25 ITU-T Recommendation V.250 [14] call control commands..... | 49 | +| 6.26 ITU-T Recommendation V.250 [14] data compression commands..... | 49 | +| 6.27 Initiate eCall +CECALL..... | 49 | +| 6.28 Informative examples..... | 50 | + +| | | | +|------|-----------------------------------------------------------------------------|-----| +| 7 | Network service related commands..... | 51 | +| 7.0 | General..... | 51 | +| 7.1 | Subscriber number +CNUM..... | 51 | +| 7.2 | Network registration +CREG..... | 52 | +| 7.3 | PLMN selection +COPS..... | 54 | +| 7.4 | Facility lock +CLCK..... | 56 | +| 7.5 | Change password +CPWD..... | 58 | +| 7.6 | Calling line identification presentation +CLIP..... | 58 | +| 7.7 | Calling line identification restriction +CLIR..... | 60 | +| 7.8 | Connected line identification presentation +COLP..... | 61 | +| 7.9 | Called line identification presentation +CDIP..... | 62 | +| 7.10 | Closed user group +CCUG..... | 63 | +| 7.11 | Call forwarding number and conditions +CCFC..... | 64 | +| 7.12 | Call waiting +CCWA..... | 65 | +| 7.13 | Call related supplementary services +CHLD..... | 67 | +| 7.14 | Call deflection +CTFR..... | 68 | +| 7.15 | Unstructured supplementary service data +CUSD..... | 68 | +| 7.16 | Advice of charge +CAOC..... | 70 | +| 7.17 | Supplementary service notifications +CSSN..... | 71 | +| 7.18 | List current calls +CLCC..... | 72 | +| 7.19 | Preferred PLMN list +CPOL..... | 74 | +| 7.20 | Selection of preferred PLMN list +CPLS..... | 76 | +| 7.21 | Read operator names +COPN..... | 76 | +| 7.22 | eMLPP priority registration and interrogation +CAEMLPP..... | 77 | +| 7.23 | eMLPP subscriptions +CPPS..... | 77 | +| 7.24 | Fast call setup conditions +CFCS..... | 78 | +| 7.25 | Automatic answer for eMLPP service +CAAP..... | 78 | +| 7.26 | User to user signalling service 1 +CUUS1..... | 79 | +| 7.27 | Preferred network indication +CPNET..... | 81 | +| 7.28 | Preferred network status +CPNSTAT..... | 81 | +| 7.29 | Current packet switched bearer +CPSB..... | 82 | +| 7.30 | Calling name identification presentation +CNAP..... | 83 | +| 7.31 | Connected line identification restriction status +COLR..... | 84 | +| 7.32 | Service specific access control restriction status +CSSAC..... | 85 | +| 7.33 | Network emergency bearer services support +CNEM..... | 87 | +| 7.34 | Enhanced closed user group +CECUG..... | 88 | +| 7.35 | Communication forwarding number and conditions with URI support +CCFCU..... | 90 | +| 7.36 | Informative examples..... | 92 | +| 8 | Mobile termination control and status commands..... | 93 | +| 8.0 | General..... | 93 | +| 8.1 | Phone activity status +CPAS..... | 94 | +| 8.2 | Set phone functionality +CFUN..... | 95 | +| 8.3 | Enter PIN +CPIN..... | 96 | +| 8.4 | Battery charge +CBC..... | 97 | +| 8.5 | Signal quality +CSQ..... | 98 | +| 8.6 | Mobile termination control mode +CMEC..... | 99 | +| 8.7 | Keypad control +CKPD..... | 100 | +| 8.8 | Display control +CDIS..... | 101 | +| 8.9 | Indicator control +CIND..... | 102 | +| 8.10 | Mobile termination event reporting +CMER..... | 103 | +| 8.11 | Select phonebook memory storage +CPBS..... | 105 | +| 8.12 | Read phonebook entries +CPBR..... | 107 | +| 8.13 | Find phonebook entries +CPBF..... | 108 | +| 8.14 | Write phonebook entry +CPBW..... | 110 | +| 8.15 | Clock +CCLK..... | 111 | +| 8.16 | Alarm +CALA..... | 112 | +| 8.17 | Generic SIM access +CSIM..... | 113 | +| 8.18 | Restricted SIM access +CRSM..... | 114 | +| 8.19 | Secure control command +CSCC..... | 115 | +| 8.20 | Alert sound mode +CALM..... | 116 | +| 8.21 | Ringer sound level +CRSL..... | 116 | + +| | | | +|-------|----------------------------------------------------------------------|-----| +| 8.22 | Vibrator mode +CVIB..... | 117 | +| 8.23 | Loudspeaker volume level +CLVL..... | 117 | +| 8.24 | Mute control +CMUT..... | 118 | +| 8.25 | Accumulated call meter +CACM..... | 119 | +| 8.26 | Accumulated call meter maximum +CAMM..... | 119 | +| 8.27 | Price per unit and currency table +CPUC..... | 120 | +| 8.28 | Call meter maximum event +CCWE..... | 120 | +| 8.29 | Power class +CPWC..... | 121 | +| 8.30 | Set language +CLAN..... | 122 | +| 8.31 | Language event +CLAE..... | 123 | +| 8.32 | Set greeting text +CSGT..... | 123 | +| 8.33 | Set voice mail number +CSVM..... | 124 | +| 8.34 | Ring melody control +CRMC..... | 125 | +| 8.35 | Ring melody playback +CRMP..... | 126 | +| 8.36 | Master reset +CMAR..... | 126 | +| 8.37 | List all available AT commands +CLAC..... | 127 | +| 8.38 | Delete alarm +CALD..... | 127 | +| 8.39 | Postpone or dismiss an alarm +CAPD..... | 128 | +| 8.40 | Automatic time zone update +CTZU..... | 128 | +| 8.41 | Time zone reporting +CTZR..... | 129 | +| 8.42 | Enter protocol mode+CPROT..... | 130 | +| 8.43 | Generic UICC logical channel access +CGLA..... | 131 | +| 8.44 | Restricted UICC logical channel access +CRLA..... | 132 | +| 8.45 | Open logical channel +CCHO..... | 133 | +| 8.46 | Close logical channel +CCHC..... | 134 | +| 8.47 | EAP authentication +CEAP..... | 134 | +| 8.48 | EAP retrieve parameters +CERP..... | 136 | +| 8.49 | UICC application discovery +CUAD..... | 136 | +| 8.50 | Mobile originated location request +CMOLR..... | 137 | +| 8.51 | Backlight +CBKLT..... | 141 | +| 8.52 | Command touch screen action +CTSA..... | 142 | +| 8.53 | Command screen orientation +CSO..... | 144 | +| 8.54 | Command screen size +CSS..... | 146 | +| 8.54A | Command display screen boundary +CDSB..... | 147 | +| 8.55 | Positioning control +CPOS..... | 147 | +| 8.56 | Positioning reporting +CPOSR..... | 163 | +| 8.57 | Mobile terminated location request notification +CMTLR..... | 165 | +| 8.58 | Mobile terminated location request disclosure allowance +CMTLRA..... | 166 | +| 8.59 | Battery capacity +CBCAP..... | 166 | +| 8.60 | Battery connection status +CBCON..... | 167 | +| 8.61 | Battery charger status +CBCHG..... | 168 | +| 8.62 | Printing IP address format +CGPIAF..... | 169 | +| 8.63 | IMS single radio voice call continuity +CISRVCC..... | 170 | +| 8.64 | IMS network reporting +CIREP..... | 171 | +| 8.65 | Remaining PIN retries +CPINR..... | 172 | +| 8.66 | Set card slot +CSUS..... | 173 | +| 8.67 | Emergency numbers +CEN..... | 173 | +| 8.68 | Availability for voice calls with IMS +CAVIMS..... | 174 | +| 8.69 | Extended signal quality +CESQ..... | 175 | +| 8.70 | Primary notification event reporting +CPNER..... | 177 | +| 8.71 | IMS registration information +CIREG..... | 178 | +| 8.72 | Availability for SMS using IMS +CASIMS..... | 179 | +| 8.73 | Monitor of current calls +CMCCS..... | 179 | +| 8.74 | List of current calls +CLCCS..... | 185 | +| 8.75 | Informative examples..... | 188 | +| 9 | Mobile termination errors..... | 192 | +| 9.1 | Report mobile termination error +CMEE..... | 192 | +| 9.1a | Report mobile originated location request error +CMOLRE..... | 192 | +| 9.2 | Mobile termination error result code +CME ERROR..... | 193 | +| 9.2.0 | General..... | 193 | +| 9.2.1 | General errors..... | 193 | + +| | | | +|----------|---------------------------------------------------------------------------------|-----| +| 9.2.2 | GPRS and EPS-related errors..... | 194 | +| 9.2.2.1 | Errors related to a failure to perform an attach..... | 194 | +| 9.2.2.2 | Errors related to a failure to activate a context..... | 195 | +| 9.2.2.3 | Errors related to a failure to disconnect a PDN..... | 195 | +| 9.2.2.4 | Other GPRS errors..... | 195 | +| 9.2.3 | VBS, VGCS and eMLPP-related errors..... | 195 | +| 9.3 | Mobile termination error result code +CMOLRE..... | 196 | +| 9.3.1 | General..... | 196 | +| 9.3.2 | Errors..... | 196 | +| 9.4 | Informative examples..... | 196 | +| 10 | Commands for packet domain..... | 197 | +| 10.0 | General..... | 197 | +| 10.1 | Commands specific to MTs supporting the packet domain..... | 197 | +| 10.1.0 | General remark about EPS bearer contexts and PDP contexts..... | 197 | +| 10.1.1 | Define PDP context +CGDCONT..... | 199 | +| 10.1.2 | Define secondary PDP context +CGDSCONT..... | 201 | +| 10.1.3 | Traffic flow template +CGTFT..... | 203 | +| 10.1.4 | Quality of service profile (requested) +CGQREQ..... | 205 | +| 10.1.5 | Quality of service profile (minimum acceptable) +CGQMIN..... | 207 | +| 10.1.6 | 3G quality of service profile (requested) +CGEQREQ..... | 208 | +| 10.1.7 | 3G quality of service profile (minimum acceptable) +CGEQMIN..... | 211 | +| 10.1.8 | 3G quality of service profile (negotiated) +CGEQNEG..... | 215 | +| 10.1.9 | PS attach or detach +CGATT..... | 217 | +| 10.1.10 | PDP context activate or deactivate +CGACT..... | 217 | +| 10.1.11 | PDP context modify +CGCMOD..... | 218 | +| 10.1.12 | Enter data state +CGDATA..... | 219 | +| 10.1.13 | Configure local octet stream PAD parameters +CGCLOSP (Obsolete)..... | 221 | +| 10.1.14 | Show PDP address(es) +CGPADDR..... | 221 | +| 10.1.15 | Automatic response to a network request for PDP context activation +CGAUTO..... | 222 | +| 10.1.16 | Manual response to a network request for PDP context activation +CGANS..... | 223 | +| 10.1.17 | GPRS mobile station class +CGCLASS..... | 224 | +| 10.1.18 | Configure local triple-X PAD parameters +CGCLPAD (GPRS only) (Obsolete)..... | 225 | +| 10.1.19 | Packet domain event reporting +CGEREPP..... | 225 | +| 10.1.20 | GPRS network registration status +CGREG..... | 229 | +| 10.1.21 | Select service for MO SMS messages +CGSMS..... | 231 | +| 10.1.22 | EPS network registration status +CEREG..... | 231 | +| 10.1.23 | PDP context read dynamic parameters +CGCONTRDP..... | 233 | +| 10.1.24 | Secondary PDP context read dynamic parameters +CGSCONTRDP..... | 235 | +| 10.1.25 | Traffic flow template read dynamic parameters +CGTFTRDP..... | 236 | +| 10.1.26 | Define EPS quality of service +CGEQOS..... | 237 | +| 10.1.27 | EPS quality of service read dynamic parameters +CGEQOSRDP..... | 238 | +| 10.1.28 | UE modes of operation for EPS +CEMODE..... | 239 | +| 10.1.29 | Delete non-active PDP contexts +CGDEL..... | 240 | +| 10.1.30 | Signalling connection status +CSCON..... | 241 | +| 10.1.31 | Define PDP context authentication parameters +CGAUTH..... | 242 | +| 10.1.32 | Initial PDP context activation +CIPCA..... | 243 | +| 10.1.33 | No more PS data +CNMPSD..... | 243 | +| 10.1.34 | UE's usage setting for EPS +CEUS..... | 244 | +| 10.1.35 | UE's Voice Domain Preference E-UTRAN +CEVDP..... | 244 | +| 10.1.36 | UE's Voice Domain Preference UTRAN +CVDP..... | 245 | +| 10.1.37 | UE's Mobility Management IMS Voice Termination +CMMIVT..... | 246 | +| 10.1.38 | Power Preference Indication for EPS +CEPPI..... | 246 | +| 10.2 | Modem compatibility commands..... | 247 | +| 10.2.0 | General..... | 247 | +| 10.2.1 | MT originated PDP context activation..... | 247 | +| 10.2.1.0 | General..... | 247 | +| 10.2.1.1 | Request packet domain service 'D'..... | 247 | +| 10.2.1.2 | Request packet domain IP service 'D'..... | 248 | +| 10.2.2 | Network requested PDP context activation..... | 249 | +| 10.2.2.0 | General..... | 249 | +| 10.2.2.1 | Automatic response to a network request for PDP context activation 'S0'..... | 249 | + +| | | | +|-------------------------------|------------------------------------------------------------------------------|------------| +| 10.2.2.2 | Manual acceptance of a network request for PDP context activation 'A'..... | 250 | +| 10.2.2.3 | Manual rejection of a network request for PDP context activation 'H'..... | 250 | +| 11 | Commands for VGCS and VBS..... | 250 | +| 11.0 | General..... | 250 | +| 11.1 | Commands specific to MTs supporting the VGCS and VBS..... | 250 | +| 11.1.1 | Accept an incoming voice group or voice broadcast call +CAJOIN..... | 250 | +| 11.1.2 | Reject an incoming voice group or voice broadcast call +CAREJ..... | 251 | +| 11.1.3 | Leave an ongoing voice group or voice broadcast call +CAHLD..... | 251 | +| 11.1.4 | Talker access for voice group call +CAPTT..... | 252 | +| 11.1.5 | Voice group call uplink status presentation +CAULEV..... | 253 | +| 11.1.6 | List current voice group and voice broadcast calls +CALCC..... | 253 | +| 11.1.7 | Voice group or voice broadcast call state attribute presentation +CACSP..... | 254 | +| 11.1.8 | NCH support indication +CANCHEV..... | 255 | +| 11.1.9 | Originator to dispatcher information +COTDI..... | 256 | +| 11.1.10 | Short data transmission during ongoing VGCS +CEPTT..... | 257 | +| 11.1.11 | Group Id prefixes capability +CGIPC..... | 258 | +| 11.2 | Modem compatibility commands..... | 258 | +| 11.2.0 | General..... | 258 | +| 11.2.1 | Request VGCS or VBS service 'D'..... | 258 | +| 11.2.2 | Termination of an voice group or voice broadcast call 'H'..... | 259 | +| 11.3 | SIM commands supporting the VGCS and VBS..... | 259 | +| 11.3.1 | VGCS subscriptions and GId status +CGCS..... | 259 | +| 11.3.2 | VBS subscriptions and GId status +CBCS..... | 260 | +| 11.4 | Informative examples..... | 261 | +| 12 | Commands for USIM application toolkit..... | 261 | +| 12.1 | General..... | 261 | +| 12.2 | Commands specific to MTs supporting USAT..... | 262 | +| 12.2.1 | Read USAT profile +CUSATR..... | 262 | +| 12.2.2 | Write USAT profile +CUSATW..... | 262 | +| 12.2.3 | Profile download upon start-up +CUSATD..... | 263 | +| 12.2.4 | Activate USAT profile +CUSATA..... | 264 | +| 12.2.5 | Send USAT terminal response +CUSATT..... | 266 | +| 12.2.6 | Send USAT envelope command +CUSATE..... | 266 | +| 12.3 | Informative examples..... | 267 | +| 13 | Commands for enhanced support of dialling..... | 268 | +| 13.1 | General..... | 268 | +| 13.2 | Commands for dialling..... | 268 | +| 13.2.1 | Dial URI +CDU..... | 268 | +| 13.2.2 | Dial URI from phonebook +CDUP..... | 271 | +| 13.2.3 | Hangup of current calls +CHCCS..... | 272 | +| 13.2.4 | Define media profile +CDEFMP..... | 273 | +| 13.2.5 | Control and modify media description +CCMMD..... | 274 | +| 13.3 | Informative examples..... | 275 | +| Annex A (normative): | Summary of commands from other standards..... | 279 | +| Annex B (normative): | Summary of result codes..... | 281 | +| Annex C (informative): | Commands from TTA IS-101..... | 283 | +| C.1 | Introduction..... | 283 | +| C.2 | Commands..... | 284 | +| C.2.1 | Select mode +FCLASS..... | 284 | +| C.2.2 | Buffer threshold setting +VBT..... | 284 | +| C.2.3 | Calling number ID presentation +VCID..... | 285 | +| C.2.4 | Receive gain selection +VGR..... | 285 | +| C.2.5 | Transmit gain selection +VGT..... | 285 | +| C.2.6 | Initialise voice parameters +VIP..... | 286 | +| C.2.7 | Inactivity timer +VIT..... | 286 | +| C.2.8 | Line selection +VLS..... | 286 | + +| | | | +|-------------------------------|-------------------------------------------------------------------|------------| +| C.2.9 | Receive data state +VRX..... | 288 | +| C.2.10 | Select compression method +VSM..... | 288 | +| C.2.11 | DTMF and tone generation +VTS..... | 289 | +| C.2.12 | Tone duration +VTD..... | 289 | +| C.2.13 | Transmit data state +VTX..... | 290 | +| Annex D (informative): | Bibliography..... | 291 | +| Annex E (informative): | Mobile originated alternating voice/data call example..... | 292 | +| Annex F (informative): | Mobile terminated voice followed by data call example..... | 293 | +| Annex G (informative): | Voice call example..... | 294 | +| Annex H (informative): | Change history..... | 295 | + +--- + +## 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 a profile of AT commands and recommends that this profile be used for controlling Mobile Termination (MT) functions and GSM/UMTS network services from a Terminal Equipment (TE) through Terminal Adaptor (TA). The command prefix +C is reserved for Digital Cellular in ITU-T Recommendation V.250 [14]. The present document has also the syntax details used to construct these extended GSM/UMTS commands. Commands from ITU-T Recommendation V.250 [14] and existing digital cellular standards (TIA IS-99 [15] and TIA IS-135 [16]) are used whenever applicable. Some of the new commands are defined such way that they can be easily applied to MT of networks other than GSM/UMTS. ITU-T Recommendation T.31 [11] and ITU-T Recommendation T.32 [12] fax AT commands may be used for GSM/UMTS fax transmission from TE. GSM/UMTS Short Message Service AT commands are defined in 3GPP TS 27.005 [24]. AT commands for GPRS and EPC are defined in clause 10 of this specification. The present document assumes an abstract architecture comprising a TE (e.g. a computer) and a MT interfaced by a TA (see figure 1). The span of control of the defined commands should allow handling of any physical implementation that this abstract architecture may lead to: + +- TA, MT and TE as three separate entities; +- TA integrated under the MT cover, and the TE implemented as a separate entity; +- TA integrated under the TE cover, and the MT implemented as a separate entity; and +- TA and MT integrated under the TE cover as a single entity. + +The commands described in the present document may be observed on the link between the TE and the TA. However, most of the commands retrieve information about the MT, not about the TA. + +![Figure 1: Setup diagram showing the interaction between TE, TA, and MT blocks. TE is connected to USER & APPLICATIONS. TA is connected to MT. MT is connected to NETWORK. Arrows show data flow: AT cmds from TE to TA, responses from TA to TE, MT control from TA to MT, MT status from MT to TA, and network messages between MT and NETWORK.](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` + +graph LR + TE[TE] <--> UA[USER & APPLICATIONS] + TE -- "AT cmds" --> TA[TA] + TA -- "responses" --> TE + TA -- "MT control" --> MT[MT] + MT -- "MT status" --> TA + MT <--> N[NETWORK] + N -- "network messages" --> MT + +``` + +Figure 1: Setup diagram showing the interaction between TE, TA, and MT blocks. TE is connected to USER & APPLICATIONS. TA is connected to MT. MT is connected to NETWORK. Arrows show data flow: AT cmds from TE to TA, responses from TA to TE, MT control from TA to MT, MT status from MT to TA, and network messages between MT and NETWORK. + +**Figure 1: Setup** + +Interface between TE and TA is intended to operate over existing serial (ITU-T Recommendation V.24) cables, infrared link, and all link types with similar behaviour. For correct operation many of the defined commands require eight bit data and therefore it is recommended that TE-TA link is set to eight bits/ byte mode. (For infrared operation implementation, refer informative references IrDA. For embedding AT commands and data during on-line data state, refer TIA-617/ITU-T V.80.) Interface between TA and MT is dependent on the interface in the MT. + +The functional blocks shown in figure 1, using AT commands, shall follow the principles described in the interactions handling framework 3GPP TS 23.227 [63]. + +## 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.002: "Bearer Services (BS) supported by a GSM Public Land Mobile Network (PLMN)". +- [2] 3GPP TS 22.003: "Teleservices supported by a GSM Public Land Mobile Network (PLMN)". +- [3] 3GPP TS 22.081: "Line identification supplementary services - Stage 1". +- [4] 3GPP TS 22.082: "Call Forwarding (CF) supplementary services - Stage 1". +- [5] 3GPP TS 22.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 1". +- [6] 3GPP TS 22.088: "Call Barring (CB) supplementary services - Stage 1". +- [7] 3GPP TS 23.003: "Numbering, addressing and identification". +- [8] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols-Stage 3". +- [9] GSM MoU SE.13, GSM MoU Permanent Reference Document SE.13: "GSM Mobile Network Codes and Names". +- [10] ITU-T Recommendation E.212: "Identification plan for land mobile stations". +- [11] ITU-T Recommendation T.31: "Asynchronous facsimile DCE control, service class 1". +- [12] ITU-T Recommendation T.32: "Asynchronous facsimile DCE control, service class 2". + +- [13] ITU-T Recommendation T.50: "International Reference Alphabet (IRA) (Formerly International Alphabet No. 5 or IA5) - Information technology - 7-bit coded character set for information exchange". +- [14] ITU-T Recommendation V.250: "Serial asynchronous automatic dialling and control". +- [15] TTA IS-99: "Data Services Option Standard for Wideband Spread Spectrum Digital Cellular System". +- [16] TTA IS-135: "800 MHz Cellular Systems, TDMA Services, Async Data and Fax". +- [17] PCCA STD-101 Data Transmission Systems and Equipment: "Serial Asynchronous Automatic Dialling and Control for Character Mode DCE on Wireless Data Services". +- [18] 3GPP TS 24.022: "Radio Link Protocol (RLP) for data and telematic services on the Mobile Station - Base Station System (MS - BSS) interface and the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". +- [19] 3GPP TS 22.030: "Man Machine Interface (MMI) of the Mobile Station (MS)". +- [20] 3GPP TS 45.008: "Radio subsystem link control". +- [21] 3GPP TS 22.085: "Closed User Group (CUG) supplementary services - Stage 1". +- [22] 3GPP TS 22.084: "MultiParty (MPTY) supplementary services - Stage 1". +- [23] 3GPP TS 22.090: "Unstructured Supplementary Service Data (USSD) - Stage 1". +- [24] 3GPP TS 27.005: "Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)". +- [25] 3GPP TS 23.038: "Alphabet and language specific information". +- [26] 3GPP TS 22.024: "Description of Charge Advice Information (CAI)". +- [27] 3GPP TS 22.086: "Advice of Charge (AoC) supplementary services - Stage 1". +- [28] 3GPP TS 51.011: "Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface". +- [29] 3GPP TS 22.034: "High Speed Circuit Switched Data (HSCSD) - Stage 1". +- [30] 3GPP TS 22.091: "Explicit Call Transfer (ECT) supplementary service - Stage 1". +- [31] 3GPP TS 22.072: "Call Deflection (CD) supplementary service - Stage 1". +- [32] ISO/IEC 10646: "Universal Multiple-Octet Coded Character Set (UCS)"; UCS2, 16 bit coding. +- [33] 3GPP TS 22.022: "Personalization of GSM Mobile Equipment (ME) Mobile functionality specification". +- [34] 3GPP TS 27.060: "General requirements on Mobile Stations (MS) supporting General Packet Radio Bearer Service (GPRS)". +- [35] Void. +- [36] CCITT Recommendation V.120: "Support by an ISDN of data terminal equipment with V-Series type interfaces with provision for statistical multiplexing". +- [37] Void. +- [38] 3GPP TS 45.005: "Radio transmission and reception". +- [39] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting GPRS and Packet Data Networks (PDN)". +- [40] 3GPP TS 23.081: "Line identification supplementary services - Stage 2". + +- [41] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". +- [42] 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)". +- [43] Infrared Data Association; Specification of Ir Mobile Communications (IrMC). +- [44] IrDA Object Exchange Protocol. +- [45] 3GPP TS 27.010: "Terminal Equipment to User Equipment (TE-UE) multiplexer protocol User Equipment (UE)". +- [46] 3GPP TS 23.107: "Quality of Service, Concept and Architecture". +- [47] 3GPP TS 23.060: "General Packet Radio Service (GPRS) Service description; Stage 2". +- [48] Void. +- [49] 3GPP TS 43.068: "Voice Group Call service (VGCS) - Stage 2". +- [50] 3GPP TS 43.069: "Voice Broadcast Service (VBS) - Stage 2". +- [51] Void. +- [52] 3GPP TS 44.068: "Voice Group Call service (VGCS) - Stage 3". +- [53] 3GPP TS 44.069: "Voice Broadcast Service (VBS) - Stage 3". +- [54] 3GPP TS 22.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP) - Stage 1". +- [55] 3GPP TS 42.068: "Voice Group Call service (VGCS) - Stage 1". +- [56] 3GPP TS 42.069: "Voice Broadcast Service (VBS) - Stage 1". +- [57] Void. +- [58] 3GPP TS 22.087: "User-to-User Signalling (UUS) - Stage 1". +- [59] 3GPP TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM) Application". +- [60] ETSI TS 102 221 "Smart Cards; UICC-Terminal interface; Physical and logical characteristics (Release 1999)". +- [61] 3GPP TS 44.065: "Mobile Station (MS) – Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDPCP)". +- [62] 3GPP TS 25.323: "Packet Data Convergence Protocol (PDCP)". +- [63] 3GPP TS 23.227 "Applications and User interaction in the UE-Principles and specific requirements". +- [64] Void. +- [65] 3GPP TS 31.101: "UICC-Terminal Interface; Physical and Logical Characteristics." +- [66] ETSI TS 102 310: "Smart Cards; Extensible Authentication Protocol support in the UICC". +- [67] Void. +- [68] RFC 3748: "Extensible Authentication Protocol (EAP)". +- [69] RFC 3629: "UTF-8, a transformation format of ISO 10646". +- [70] 3GPP TS 44.318: "Generic Access (GA) to the A/Gb interface; Mobile GA interface layer 3 specification". + +- [71] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol". +- [72] 3GPP TS 25.308: "High Speed Downlink Packet Access (HSDPA): Overall Description; Stage 2". +- [73] 3GPP TS 25.319: "Enhanced Uplink; Overall Description; Stage 2". +- [74] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification". +- [75] 3GPP TS 24.216: "Communication Continuity Management Object (MO)". +- [76] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". +- [77] 3GPP TS 25.305 "User Equipment (UE) positioning in Universal Terrestrial Radio Access Network (UTRAN); Stage 2". +- [78] IEC 61162: "Maritime navigation and radio communication equipment and systems – Digital interfaces". +- [79] 3GPP TS 44.031: "Location Services (LCS); Mobile Station (MS) - Serving Mobile Location Centre (SMLC), Radio Resource LCS Protocol (RRLP)". +- [80] 3GPP TS 49.031: "Base Station System Application Part, LCS Extension (BSSAP-LE)". +- [81] Void. +- [82] 3GPP TS 23.401: "GPRS enhancements for E-UTRAN access". +- [83] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS)". +- [84] Void. +- [85] 3GPP TS 23.203: "Policy and charging control architecture". +- [86] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [87] 3GPP TS 24.173: "IMS multimedia telephony communication service and supplementary services; Stage 3". +- [88] RFC 4291: "IP Version 6 Addressing Architecture". +- [89] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)". +- [90] 3GPP TS 23.221: "Architectural requirements". +- [91] 3GPP TS 24.237: "IP Multimedia Subsystem (IMS) Service Continuity". +- [92] 3GPP TS 31.111: "Universal Subscriber Identity Module (USIM) Application Toolkit (USAT)". +- [93] 3GPP TS 22.096: "Name identification supplementary services - Stage 1". +- [94] 3GPP TS 23.096: "Name identification supplementary services - Stage 2". +- [95] 3GPP TS 25.133: "Requirements for support of radio resource management (FDD)". +- [96] 3GPP TS 25.123: "Requirements for support of radio resource management (TDD)". +- [97] 3GPP TS 36.133: "Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management". +- [98] 3GPP TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM) application". +- [99] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)". +- [100] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". + +- [101] 3GPP TS 24.341: "Support of SMS over IP networks". +- [102] 3GPP TS 24.167: "3GPP IMS Management Object (MO); Stage 3". +- [103] IETF STD 5: "Internet Protocol". +- [104] IETF STD 51: "The Point-to-Point Protocol (PPP)". +- [105] RFC 1144: "Compressing TCP/IP Headers for Low-Speed Serial Links". +- [106] RFC 2460: "Internet Protocol, Version 6 (IPv6) Specification". +- [107] RFC 2507: "IP Header Compression". +- [108] RFC 3095: "RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed". +- [109] 3GPP TS 24.080: "Mobile radio interface Layer 3 supplementary service specification; Formats and coding". +- [110] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [111] RFC 3261: "SIP: Session Initiation Protocol". +- [112] RFC 3966: "The tel URI for Telephone Numbers". +- [113] RFC 3969: "The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP)". +- [114] RFC 5341: "The Internet Assigned Number Authority (IANA) tel Uniform Resource Identifier (URI) Parameter Registry". +- [115] 3GPP TS 36.355: "Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Positioning Protocol (LPP)". +- [116] RFC 2141: "URN Syntax". +- [117] RFC 3406: "Uniform Resource Names (URN) Namespace Definition Mechanisms". +- [118] RFC 5031: "A Uniform Resource Name (URN) for Emergency and Other Well-Known Services". +- [119] 3GPP TS 24.607: "Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [120] 3GPP TS 24.608: "Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [121] 3GPP TS 24.654: "Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol Specification". +- [122] RFC 4715: "The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI". +- [123] 3GPP TS 22.093: "Completion of Calls to Busy Subscriber (CCBS); Service description, Stage 1". +- [124] 3GPP TS 22.094: "Follow Me service description; Stage 1". +- [125] 3GPP TS 22.097: "Multiple Subscriber Profile (MSP) Phase 2; Service description; Stage 1". +- [126] 3GPP TS 22.135: "Multicall; Service description; Stage 1". +- [127] 3GPP TS 24.182: "IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT); Protocol specification". + +- [128] 3GPP TS 24.183: "IP Multimedia Subsystem (IMS) Customized Ringing Signal (CRS); Protocol specification". +- [129] 3GPP TS 24.239: "Flexible Alerting (FA) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [130] 3GPP TS 24.259: "Personal Network Management (PNM)". +- [131] 3GPP TS 24.390: "Unstructured Supplementary Service Data (USSD) using IP Multimedia (IM) Core Network (CN) subsystem IMS". +- [132] 3GPP TS 24.604: "Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [133] 3GPP TS 24.605: "Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [134] 3GPP TS 24.606: "Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [135] 3GPP TS 24.610: "Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [136] 3GPP TS 24.611: "Anonymous Communication Rejection (ACR) and Communication Barring (CB) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [137] 3GPP TS 24.615: "Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specification". +- [138] 3GPP TS 24.616: "Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [139] 3GPP TS 24.629: "Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [140] 3GPP TS 24.642: "Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [141] 3GPP TS 24.647: "Advice Of Charge (AOC) using IP Multimedia (IM) Core Network (CN) subsystem". +- [142] 3GPP TS 36.509: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC); Special conformance testing functions for User Equipment (UE)". + +## 3 Definitions and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the following syntactical definitions apply (refer also clause 4): + +| | | +|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Carriage return character, which value is specified with command S3. | +| | Linefeed character, which value is specified with command S4. | +| <...> | Name enclosed in angle brackets is a syntactical element. Brackets themselves do not appear in the command line. | +| [...] | Optional subparameter of a command or an optional part of TA information response is enclosed in square brackets. Brackets themselves do not appear in the command line. When subparameter is not given in parameter type commands, new value equals to its previous value. In action type commands, action should be done on the basis of the recommended default setting of the subparameter. | +| underline | Underlined defined subparameter value is the recommended default setting of this subparameter. In parameter type commands, this value should be used in factory settings which are configured by ITU-T Recommendation V.250 [14] command &F0. In action type commands, this value should be used when subparameter is not given. | + +### 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|------------------------------------------------------------------------------------------------------------| +| AT | ATtention; this two-character abbreviation is always used to start a command line to be sent from TE to TA | +| ASCI | Advanced Speech Call Items, including VGCS, VBS and eMLPP | +| BCD | Binary Coded Decimal | +| eMLPP | Enhanced Multi-Level Precedence and Pre-emption Service | +| ETSI | European Telecommunications Standards Institute | +| FTM | Frame Tunnelling Mode (refer 3GPP TS 27.001 [41] and 3GPP TS 29.007 [42]) | +| HSCSD | High Speed Circuit Switched Data | +| IMEI | International Mobile station Equipment Identity | +| IRA | International Reference Alphabet (ITU-T Recommendation T.50 [13]) | +| IrDA | Infrared Data Association | +| ISO | International Standards Organization | +| ITU-T | International Telecommunication Union - Telecommunications Standardization Sector | +| ME | Mobile Equipment | +| MoU | Memorandum of Understanding (GSM operator joint) | +| MT | Mobile Termination | +| PCCA | Portable Computer and Communications Association | +| PTT | Push to Talk | +| RDI | Restricted Digital Information | +| RLP | Radio Link Protocol | +| SIM | Subscriber Identity Module | +| TA | Terminal Adaptor, e.g. a GSM data card (equal to DCE; Data Circuit terminating Equipment) | +| TE | Terminal Equipment, e.g. a computer (equal to DTE; Data Terminal Equipment) | +| TIA | Telecommunications Industry Association | +| UDI | Unrestricted Digital Information | +| UE | User Equipment | +| UICC | Universal Integrated Circuit Card | +| USAT | USIM Application Toolkit | +| USIM | Universal Subscriber Identity Module | +| VBS | Voice Broadcast Service | +| VGCS | Voice Group Call Service | + +## 4 AT command syntax + +### 4.0 General + +This clause summarizes general aspects on AT commands and issues related to them. + +TE software implementors must take account that future versions of this specification may include additional parameters beyond what is expected in any response to an AT Set Command, Read Command, Test Command, or unsolicited result code. Implementations must therefore analyse all parameters provided from the TA and discard (ignore) any parameters received following the parameters expected by the TE software. + +For further information refer ITU-T Recommendation V.250 [14]. + +In the tables for the commands syntaxes, the possible response(s) are outlined as follows: + +- the responses from ITU-T Recommendation V.250 [14] ( like *OK* and *ERROR*) are normally not shown; and +- the final response *+CME ERROR* is shown when a final result code in subclause 9.2 can be provided. + +In certain implementations, AT commands are used as an internal interface within the physical handset, e.g. between the application and the radio interface layer 3 stack implemented on different processors. Certain AT commands transfer information in the clear that can be regarded as sensitive with regards to security or privacy. Care must be exercised in AT commands that: + +- transfer passwords (e.g. *+CLICK*, *+CPWD* or *+CPBS*); +- transfer identities (e.g. *IMSI*) or details of a call (e.g. *+COLP*); +- transfer the current location of the phone (e.g. *+CMOLR*); +- reveal the IMEI (e.g. *+CGSN*); +- allow the TE to take unintentionally control over the SIM-MT interface (e.g. *+CSIM*); +- enable/disable access to commands protected by security mechanism (e.g. *+CSCC*); or +- exchange security related parameters and keys with the UICC (e.g. *+CEAP* and *+CERP*). + +The above mentioned AT commands and parameters are examples to illustrate the concerns and is not meant to be a comprehensive list. + +### 4.1 Command line + +See figure 2 for general structure of a command line. Standardized *basic* commands are found only in ITU-T Recommendation V.250 [14]. GSM/UMTS commands use syntax rules of *extended* commands. Every extended command has a *test command* (trailing *=?*) to test the existence of the command and to give information about the type of its subparameters. *Parameter type* commands also have a *read command* (trailing *?*) to check the current values of subparameters. *Action type* commands do not store the values of any of their possible subparameters, and therefore do not have a read command. + +![Figure 2: Basic structure of a command line. The diagram shows a command line: ATCMD1 CMD2=12; +CMD1; +CMD2=,15; +CMD2?; +CMD2=?. Annotations with arrows point to various parts: 'command line prefix' points to 'AT', 'subparameter' points to 'CMD2', 'extended commands are delimited with semicolon' points to the semicolons, 'read command for checking current subparameter values' points to '+CMD2?', 'command line termination character' points to '', 'basic command (no + prefix)' points to 'CMD1', 'extended command (prefixed with +)' points to '+CMD1', 'subparameters may be omitted' points to the empty subparameter in '+CMD2=', and 'test command for checking possible subparameter values' points to '+CMD2=?'.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +Figure 2: Basic structure of a command line. The diagram shows a command line: ATCMD1 CMD2=12; +CMD1; +CMD2=,15; +CMD2?; +CMD2=?. Annotations with arrows point to various parts: 'command line prefix' points to 'AT', 'subparameter' points to 'CMD2', 'extended commands are delimited with semicolon' points to the semicolons, 'read command for checking current subparameter values' points to '+CMD2?', 'command line termination character' points to '', 'basic command (no + prefix)' points to 'CMD1', 'extended command (prefixed with +)' points to '+CMD1', 'subparameters may be omitted' points to the empty subparameter in '+CMD2=', and 'test command for checking possible subparameter values' points to '+CMD2=?'. + +**Figure 2: Basic structure of a command line** + +If verbose responses are enabled with command V1 and all commands in a command line has been performed successfully, result code OK is sent from the TA to the TE. If numeric responses are enabled with command V0, result code 0 is sent instead. + +If verbose responses are enabled with command V1 and subparameter values of a command are not accepted by the TA (or command itself is invalid, or command cannot be performed for some reason), result code ERROR is sent to the TE and no subsequent commands in the command line are processed. If numeric responses are enabled with command V0, result code 4 is sent instead. ERROR (or 4) response may be replaced by +CME ERROR: (refer clause 9) when command was not processed due to an error related to MT operation. + +## 4.2 Information responses and result codes + +The TA response for the example command line of figure 2 could be as shown in figure 3. Here, verbose response format is enabled with command V1. If numeric format V0 would have been used, headers of *information responses* would have been left out and *final result code* changed to 0. + +![Figure 3: Response to a command line. The diagram shows the response to the command line in Figure 2: +CMD2: 3,0,15,\](3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg) + +Figure 3: Response to a command line. The diagram shows the response to the command line in Figure 2: +CMD2: 3,0,15,\ + +**Figure 3: Response to a command line** + +So called *intermediate result codes* inform about progress of TA operation (e.g. connection establishment CONNECT), and so called *unsolicited result codes* indicate occurrence of an event not directly associated with issuance of a command from TE (e.g. ring indication RING). + +## 4.3 ITU-T Recommendation V.250 [14] TE-TA interface commands + +Table 1 summarizes ITU-T Recommendation V.250 [14] commands relating to command line and response formatting, and TA-TE interface operation. All are applicable to GSM/UMTS terminals. + +**Table 1: V.250 commands relating to TE-TA interface** + +| Command | Subclause | Impl. | Use in GSM/UMTS | +|--------------------------------|-----------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| S3=[] | 6.2.1 | mand. | command line termination character (mandatory default setting IRA 13) | +| S4=[] | 6.2.2 | mand. | response formatting character (recommended default IRA 10) | +| S5=[] | 6.2.3 | mand. | command line editing character (recommended default IRA 8) | +| E[] | 6.2.4 | mand. | command echo (recommended default 1 i.e. TA echoes commands back) | +| Q[] | 6.2.5 | mand. | result code suppression (recommended default 0 i.e. TA transmits result codes) | +| V[] | 6.2.6 | mand. | TA response format (recommended default 1 i.e. verbose format) | +| X[] | 6.2.7 | mand. | defines CONNECT result code format; values manufacturer specific | +| &C[] | 6.2.8 | mand. | determines how ITU-T V.24 circuit 109 (or equivalent) relates to the detection of received line signal from remote end (recommended default 1 i.e. 109 operation relates to detection of received signal) | +| &D[] | 6.2.9 | mand. | determines how TA responds when ITU-T V.24 circuit 108/2 (or equivalent) is changed from ON to OFF condition during online data state | +| +IPR=[] | 6.2.10 | opt. | fixed TE data rate (recommended default 0 i.e. automatic detection) | +| +ICF=[[
,]] | 6.2.11 | opt. | TE-TA character framing (recommended default 3,3 i.e. eight data bits, no parity, 1 stop bit) | +| +IFC=[ [
,]] | 6.2.12 | opt. | TE-TA local flow control (recommended default 2,2 i.e. TE uses ITU-T V.24 circuit 133 (or equivalent), and TA circuit 106 (or equivalent)) | +| +ILRR=[] | 6.2.13 | opt. | determines whether the used local TE-TA data rate is informed using intermediate result code +ILRR: before going online data state after call answering or originating | + +## 5 General commands + +### 5.0 General + +ITU-T Recommendation V.250 [14] includes "Generic DCE Control" commands with the prefix +G. These commands are for the identification of the TA. Four of those commands are adapted here to be the identification commands of the MT. Syntax is otherwise similar but the prefix is +CG. TTA IS-99 [15] uses same commands for base station identification. + +### 5.1 Request manufacturer identification +CGMI + +**Table 2: +CGMI action command syntax** + +| Command | Possible response(s) | +|---------|-----------------------------------------| +| +CGMI |

+CME ERROR: | +| +CGMI=? | | + +#### Description + +Execution command causes the TA to return one or more lines of information text , determined by the MT manufacturer, which is intended to permit the user of the TA to identify the manufacturer of the MT to which it is connected to. Typically, the text will consist of a single line containing the name of the manufacturer, but manufacturers may choose to provide more information if desired. Refer subclause 9.2 for possible values. + +#### Defined values + +: the total number of characters, including line terminators, in the information text shall not exceed 2048 characters. + +Text shall not contain the sequence 0 or OK + +#### Implementation + +Optional. + +## 5.2 Request model identification +CGMM + +**Table 3: +CGMM action command syntax** + +| Command | Possible response(s) | +|---------|-----------------------------------------------| +| +CGMM |

+CME ERROR: <err> | +| +CGMM=? | | + +#### Description + +Execution command causes the TA to return one or more lines of information text , determined by the MT manufacturer, which is intended to permit the user of the TA to identify the specific model of the MT to which it is connected to. Typically, the text will consist of a single line containing the name of the product, but manufacturers may choose to provide more information if desired. Refer subclause 9.2 for possible values. + +#### Defined values + +: the total number of characters, including line terminators, in the information text shall not exceed 2048 characters. + +Text shall not contain the sequence 0 or OK + +#### Implementation + +Optional. + +## 5.3 Request revision identification +CGMR + +**Table 4: +CGMR action command syntax** + +| Command | Possible response(s) | +|---------|--------------------------------------------------| +| +CGMR |

+CME ERROR: <err> | +| +CGMR=? | | + +#### Description + +Execution command causes the TA to return one or more lines of information text , determined by the MT manufacturer, which is intended to permit the user of the TA to identify the version, revision level or date, or other pertinent information of the MT to which it is connected to. Typically, the text will consist of a single line containing the version of the product, but manufacturers may choose to provide more information if desired. Refer subclause 9.2 for possible values. + +#### Defined values + +: the total number of characters, including line terminators, in the information text shall not exceed 2048 characters. + +Text shall not contain the sequence 0 or OK + +## Implementation + +Optional. + +## 5.4 Request product serial number identification +CGSN + +**Table 5: +CGSN action command syntax** + +| Command | Possible response(s) | +|---------|-------------------------------| +| +CGSN |

+CME ERROR: | +| +CGSN=? | | + +### Description + +Execution command causes the TA to return one or more lines of information text , determined by the MT manufacturer, which is intended to permit the user of the TA to identify the individual MT to which it is connected to. Typically, the text will consist of a single line containing the IMEI (International Mobile station Equipment Identity; refer 3GPP TS 23.003 [7]) number of the MT, but manufacturers may choose to provide more information if desired. Refer subclause 9.2 for possible values. + +### Defined values + +: the total number of characters, including line terminators, in the information text shall not exceed 2048 characters. + +Text shall not contain the sequence 0 or OK + +## Implementation + +Optional. + +## 5.5 Select TE character set +CSCS + +**Table 6: +CSCS parameter command syntax** + +| Command | Possible response(s) | +|-----------------|-------------------------------------| +| +CSCS=[] | | +| +CSCS? | +CSCS: | +| +CSCS=? | +CSCS: (list of supported s) | + +### Description + +Set command informs TA which character set is used by the TE. TA is then able to convert character strings correctly between TE and MT character sets. + +When TA-TE interface is set to 8-bit operation and used TE alphabet is 7-bit, the highest bit shall be set to zero. + +NOTE: It is manufacturer specific how the internal alphabet of MT is converted to/from the TE alphabet. + +Read command shows current setting and test command displays conversion schemes implemented in the TA. + +### Defined values + +: character set as a string type (conversion schemes not listed here can be defined by manufacturers) + +- "GSM" GSM 7 bit default alphabet (3GPP TS 23.038 [25]); this setting causes easily software flow control (XON/XOFF) problems. + +- "HEX" Character strings consist only of hexadecimal numbers from 00 to FF; e.g. "032FE6" equals three 8-bit characters with decimal values 3, 47 and 230; no conversions to the original MT character set shall be done. + +If MT is using GSM 7 bit default alphabet, its characters shall be padded with 8th bit (zero) before converting them to hexadecimal numbers (i.e. no SMS-style packing of 7-bit alphabet). + +- "IRA" International reference alphabet (see ITU-T Recommendation T.50 [13]). +- "PCCPxxx" PC character set Code Page xxx +- "PCDN" PC Danish/Norwegian character set +- "UCS2" 16-bit universal multiple-octet coded character set (see ISO/IEC10646 [32]); UCS2 character strings are converted to hexadecimal numbers from 0000 to FFFF; e.g. "004100620063" equals three 16-bit characters with decimal values 65, 98 and 99. +- "UTF-8" Octet (8-bit) lossless encoding of UCS characters (see RFC 3629 [69]); UTF-8 encodes each UCS character as a variable number of octets, where the number of octets depends on the integer value assigned to the UCS character. The input format shall be a stream of octets. It shall not be converted to hexadecimal numbers as in "HEX" or "UCS2". This character set requires an 8-bit TA – TE interface. +- "8859-n" ISO 8859 Latin n (1-6) character set +- "8859-C" ISO 8859 Latin/Cyrillic character set +- "8859-A" ISO 8859 Latin/Arabic character set +- "8859-G" ISO 8859 Latin/Greek character set +- "8859-H" ISO 8859 Latin/Hebrew character set + +#### Implementation + +Mandatory when a command using the setting of this command is implemented. + +## 5.6 Request international mobile subscriber identity +CIMI + +**Table 7: +CIMI action command syntax** + +| Command | Possible response(s) | +|---------|---------------------------------| +| +CIMI |

+CME ERROR: | +| +CIMI=? | | + +#### Description + +Execution command causes the TA to return , which is intended to permit the TE to identify the individual SIM card or active application in the UICC (GSM or USIM) which is attached to MT. Refer subclause 9.2 for possible values. + +#### Defined values + +: International Mobile Subscriber Identity (string without double quotes) + +#### Implementation + +Optional. + +## 5.7 Multiplexing mode +CMUX + +Table 8: +CMUX parameter command syntax + +| Command | Possible response(s) | +|------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CMUX=[, [, [, [, [, [, [, [, ]]]]]]] | +CME ERROR: | +| +CMUX? | +CMUX: , [], , , , , , , []

+CME ERROR: | +| +CMUX=? | +CMUX: (list of supported s) , (list of supported s) , (list of supported s) , (list of supported s) , (list of supported s) , (list of supported s) , (list of supported s) , (list of supported s) , (list of supported s) | + +### Description + +This command is used to enable/disable the 3GPP TS 27.010 [45] multiplexing protocol control channel. Refer subclause 9.2 for possible values. The AT command sets parameters for the Control Channel. If the parameters are left out, the default value is used. + +Read command returns the current settings. + +Test command returns the supported parameters. + +It is recommended that the MT/TA/TE should autobaud to the +CMUX command up to and including an interface speed of 9600 bits/s. + +The OK or +CME ERROR: response is returned at the speed of the +CMUX command prior to entering . + +It is recommended that whenever the multiplexer control channel is released the MT/TA/TE should assume an interface rate of up to and including 9600 bits/s for auto bauding purposes irrespective of any previous higher speed having been selected. + +If a +CMUX command is issued whilst in any multiplexer mode then that +CMUX command shall be ignored and the MT/TA shall return a +CME ERROR: response. + +### Defined values + +: integer type (multiplexer Transparency Mechanism) + +- 0 Basic option +- 1 Advanced option + +: integer type. This parameter defines the way in which the multiplexer **control channel** is set up. A virtual channel may subsequently be set up differently but in the absence of any negotiation for the settings of a virtual channel, the virtual channel shall be set up according to the control channel setting. + +- 0 UIH frames used only +- 1 UI frames used only +- 2 I frames used only + + integer type (transmission rate) + +- 1 9 600 bit/s +- 2 19 200 bit/s +- 3 38 400 bit/s +- 4 57 600 bit/s +- 5 115 200 bit/s +- 6 230 400 bits/s + +: integer type (maximum frame size) + +- 1- 32768, where the 31 is default for Basic option and 64 is default for Advanced option (see ) + +: integer type (acknowledgement timer in units of ten milliseconds) + +- 1-255, where 10 is default (100 ms) + +: integer type (maximum number of re-transmissions) + +- 0-100, where 3 is default + +: integer type (response timer for the multiplexer control channel in units of ten milliseconds) + +- 2-255, where 30 is default (300 ms) + +NOTE: T2 must be longer than T1. + +: integer type (wake up response timer in seconds) + +- 1-255, where 10 is default + +: integer type (window size, for Advanced option with Error-Recovery Mode) + +- 1-7, where 2 is default + +## Implementation + +Mandatory, if 3GPP TS 27.010 [45] supported in the MT/TA. + +## 5.8 ITU-T Recommendation V.250 [14] generic TA control commands + +**Table 9: V.250 generic TA control commands** + +| Command | Subclause | Impl. | Use in GSM/UMTS | +|--------------|-----------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Z [] | 6.1.1 | mand. | TA sets all parameters to their defaults as specified by a user memory profile or by the manufacturer, and resets TA | +| &F [] | 6.1.2 | mand. | TA sets all parameters to their defaults as specified by the manufacturer | +| I [] | 6.1.3 | opt. | request manufacturer specific information about the TA (software cannot use this command to determine the capabilities of a TA) | +| +GMI | 6.1.4 | mand. | request TA manufacturer identification (may equal to +CGMI) | +| +GMM | 6.1.5 | mand. | request TA model identification (may equal to +CGMM) | +| +GMR | 6.1.6 | mand. | request TA revision identification (may equal to +CGMR) | +| +GSN | 6.1.7 | opt. | request TA serial number identification (may equal to +CGSN) | +| +GOI | 6.1.8 | opt. | request ISO system global object identification of the TA (general format defined in ITU-T Recommendation X.208; encoding rules in ITU-T Recommendation X.209) | +| +GCAP | 6.1.9 | mand. | request overall capabilities of TA; the response code for a TA building on this document shall be +CGSM | +| +GCI= | 6.1.10 | opt. | selects the country of installation for the TA using ITU-T Recommendation T.35 Annex A country codes | + +## 5.9 PCCA STD-101 [17] select wireless network +WS46 + +PCCA STD-101 [17] includes a command to select the cellular network (Wireless Data Service; WDS) to operate with the TA. PCCA calls this WDS-Side Stack Selection. This command may be used when TA is asked to indicate the networks in which it can operate. + +**Table 10: +WS46 parameter command syntax** + +| Command | Possible response(s) | +|-------------|--------------------------| +| +WS46=[] | | +| +WS46? | | +| +WS46=? | (list of supported s) | + +### Description + +Set command selects the WDS side stack to be used by the TA. Read command shows current setting and test command displays side stacks implemented in the TA. + +### Defined values for Query + +: integer type + +- 12 GSM Digital Cellular Systems (GERAN only) +- 22 UTRAN only +- 25 3GPP Systems (GERAN, UTRAN and E-UTRAN) +- 28 E-UTRAN only +- 29 GERAN and UTRAN +- 30 GERAN and E-UTRAN +- 31 UTRAN and E-UTRAN + +The values in for Query are mutually exclusive. If one value (e.g. "25") is returned, other values shall not be returned. + +#### Defined values for Set + +: integer type + +- 12 3GPP System +- 22 Not used. If received, the value shall be treated as if 12 had been received or an ERROR shall be returned. +- 25 Not used. If received, the value shall be treated as if 12 had been received or an ERROR shall be returned. +- 28 Not used. If received, the value shall be treated as if 12 had been received or an ERROR shall be returned. +- 29 Not used. If received, the value shall be treated as if 12 had been received or an ERROR shall be returned. +- 30 Not used. If received, the value shall be treated as if 12 had been received or an ERROR shall be returned. +- 31 Not used. If received, the value shall be treated as if 12 had been received or an ERROR shall be returned. +- refer PCCA STD-101 [17] for other values. + +#### Implementation + +Mandatory in PCCA STD-101 [17], but optional for GSM/UMTS/EPS. + +## 5.10 Informative examples + +When beginning to build a communication link, a general TE application controlling a TA needs to determine the TA and the MT to which it is connected. ITU-T Recommendation V.250 [14] has seven commands for TA identification from which four are mandatory to be implemented in a TA. An example of this command sequence requesting manufacturer (+GMI), model (+GMM), revision (+GMR) and serial number (+GSN) information would be: + +``` +AT+GMI +Manufacturer ABC +OK +AT+GMM +GSM Ultimate Data Device +OK +AT+GMR +1.00 +OK +AT+GSN +987612345-123 +OK +``` + +The maximum lengths of the information responses are defined to be 2048 characters, but it is recommended that they are kept as simple as in the example. The serial number command is defined as optional. Another optional command is Global Object Identification command (+GOI) which should return the object identifiers of ITU-T Recommendation X.208 as numeric strings delimited by periods. The Complete Capabilities List command (+GCAP) should indicate the major capability areas of the TA. The support of different areas is presented in the response of +GCAP command. Each area may be presented by the selection command name of a specific capability area (e.g. +FCLASS for fax support) or some other predefined response. For instance, a GSM TA with fax capabilities could respond as follows: + +``` +AT+GCAP ++GCAP: +CGSM, +FCLASS, +W +OK +``` + +The first supported area in the response is presented with +CGSM. It is the response text to show that some or all GSM commands of the present document are supported. Second response text (+FCLASS) informs that some fax or voice capabilities are present, and the third text (+W) about the presence of wireless commands as specified by PCCA STD-101 [17]. Command +FCLASS=? (refer e.g. ITU-T Recommendation T.31 [11] and ITU-T Recommendation T.32 [12]) should be used to query the supported fax capabilities and +WS46=? to query the wireless data services available: + +``` +AT+FCLASS=?;+WS46=? +0,1,2,2.0 +(12) +OK +``` + +The TA of this example supports GSM data services, and fax service class 1 (TIA-578-A), 2 (manufacturer specific) and 2.0 (ITU-T Recommendation T.32 [12] / TIA-592). + +The present document defines commands for MT identification which are similar to those for TA identification in ITU-T Recommendation V.250 [14], for an example: + +``` +AT+CGMI +Mobile Manufacturer XYZ +OK +AT+CGMM +GSM Phone 1234 +OK +AT+CGMR +1.00 +OK +AT+CGSN +123456121234561 +OK +``` + +Manufacturer, model and version commands work similarly as for TA, except that the serial number query returns the International Mobile Station Equipment Identity (IMEI) number. IMEI is fifteen digits long and consists of a type approval code, a final assembly code, a serial number and a spare digit (refer 3GPP TS 23.003 [7]). When the TA is implemented inside MT, the responses for both TA and MT queries will most likely follow the responses of MT identification. + +## 6 Call control commands and methods + +### 6.0 General + +This clause describes the control of calls. Normal data and fax call control is done as in ITU-T Recommendation V.250 [14], ITU-T Recommendation T.31 [11] and ITU-T Recommendation T.32 [12]. For voice call originating, refer subclause "ITU-T Recommendation V.250 dial command D" and clause "Commands for enhanced support of dialling". + +### 6.1 Select type of address +CSTA + +**Table 11: +CSTA parameter command syntax** + +| Command | Possible response(s) | +|--------------|------------------------------------| +| +CSTA= | | +| +CSTA? | +CSTA: | +| +CSTA=? | +CSTA: (list of supported s) | + +#### Description + +Set command selects the type of number for further dialling commands (D) according to GSM/UMTS specifications. Test command returns values supported a compound value. + +#### Defined values + +: type of address octet in integer format (refer 3GPP TS 24.008 [8] subclause 10.5.4.7); default 145 when dialling string includes international access code character "+", otherwise 129 + +### Implementation + +Mandatory when other than default value allowed. + +## 6.2 ITU-T Recommendation V.250 [14] dial command D + +ITU-T Recommendation V.250 [14] dial command D lists characters that may be used in a dialling string for making a call or controlling supplementary services in accordance with 3GPP TS 22.030 [19]. Their use in GSM/UMTS is listed in this subclause, as well as new dial modifiers applicable only to GSM/UMTS are introduced. For a MT supporting AT commands only, it is mandatory to support the control of supplementary services in accordance with 3GPP TS 22.030 [19] through the dial command or through the specific supplementary service commands (+CCFC, +CLCK, etc.), where 3GPP TS 22.030 [19] identifies the supplementary services as mandatory. + +### V.250 dialling digits + +1 2 3 4 5 6 7 8 9 0 \* # + A B C (implementation of these characters is mandatory for GSM/UMTS) + +D (implementation of this character is optional for GSM/UMTS, and it is ignored) + +### V.250 modifier characters + +, (implementation of this character is mandatory for GSM/UMTS, but it may be ignored) + +T P (implementation of these characters is mandatory for GSM/UMTS, but they are ignored) + +! W @ (implementation of these characters is optional for GSM/UMTS, and they are ignored) + +### V.250 semicolon character + +In GSM/UMTS, when semicolon character is given after dialling digits (or modifiers), a voice call originated to the given address. TA returns to command state immediately (or after possible +COLP result code; refer subclause "Connected line identification presentation +COLP"). Refer Annex G for a detailed example. + +### GSM/UMTS modifier characters + +> (refer subclause "Direct dialling from phonebooks") + +I or i (override the CLIR supplementary service subscription default value for this call; I = invocation (restrict CLI presentation) and i = suppression (allow CLI presentation); refer subclause "Calling line identification restriction +CLIR") + +G or g (control the CUG supplementary service information for this call; uses index and info values set with command +CCUG or +CECUG; refer subclause "Closed user group +CCUG" and subclause "Enhanced closed user group +CECUG") + +## 6.3 Direct dialling from phonebooks + +GSM/UMTS MT and SIM/UICC can contain phonebooks which have a phone number and an alphanumeric field for each phonebook entry location. The use of ITU-T Recommendation V.250 [14] dialling command ensures that direct dialling from MT and SIM/UICC phonebook is possible through ordinary communications software which just gives the phone number field to be filled and then use the D command to originate the call. Available memories may be queried with Select Phonebook Storage test command +CPBS=?, and location range for example with Read Phonebook Entries test command +CPBR=?. + +### Execute commands + +1. D>[I][G][;] originate call to phone number which corresponding alphanumeric field is (if possible, all available memories should be searched for the correct entry). +2. D>mem[I][G][;] originate call to phone number in memory *mem* entry location (available memories may be queried with Select Phonebook Storage test command +CPBS=?; *mem* could be e.g. ME). +3. D>[I][G][;] originate call to phone number in entry location (it is manufacturer specific which memory storage of MT, SIM/UICC in the currently selected card slot and TA is used; command Select Phonebook Memory Storage +CPBS setting is recommended to be used). + +Semicolon character shall be added when voice call is originated. CLIR and CUG per call base modifiers may also be present. + +### Responses + +Possible error responses include +CME ERROR: when error is related to MT functionality. Refer subclause 9.2 for possible error values. Otherwise TA responses can have values defined by ITU-T Recommendation V.250 [14] and commands Service Reporting Control +CR and Connected Line Identification Presentation +COLP. Detailed error report of an unsuccessful originated call failed in a GSM/UMTS network error can be obtained with command Extended Error Report +CEER (if implemented). + +### Defined values + +: string type value, which should equal to an alphanumeric field in at least one phonebook entry in the searched memories; used character set should be the one selected with Select TE Character Set +CSCS + +: integer type memory location should be in the range of locations available in the memory used + +### Implementation + +Mandatory when direct dialling is implemented. Also phonebook commands implementation is required. + +## 6.4 Call mode +CMOD + +**Table 12: +CMOD parameter command syntax** + +| Command | Possible response(s) | +|-----------------|------------------------------------| +| +CMOD= [] | | +| +CMOD? | +CMOD: | +| +CMOD=? | +CMOD: (list of supported s) | + +### Description + +Set command selects the call mode of further dialling commands (D) or for next answering command (A). Mode can be either single or alternating (in the present document, terms "alternating mode" and "alternating call" refer to all GSM/UMTS bearer and teleservices that incorporate more than one basic service (voice, data, fax) within one call). When single mode is selected the call originating and hangup procedures are similar to procedures specified in ITU-T Recommendations V.250 [14], T.31 [11] and T.32 [12]. In GSM/UMTS there can be voice followed by data (refer 3GPP TS 22.002 [1]), alternating voice/data (refer 3GPP TS 22.002 [1]) and alternating voice/fax calls (refer 3GPP TS 22.003 [2]). Refer next two subclauses for alternating call control methods. + +Test command returns values supported as a compound value. + +NOTE: +CMOD shall be set to zero after a successfully completed alternating mode call. It shall be set to zero also after a failed answering. The power-up, factory (&F) and user resets (Z) shall also set the value to zero. This reduces the possibility that alternating mode calls are originated or answered accidentally. + +### Defined values + +: integer type + +- 0 single mode +- 1 alternating voice/fax (teleservice 61) +- 2 alternating voice/data (bearer service 61) +- 3 voice followed by data (bearer service 81) +- all other values below 128 are reserved by the present document + +### Implementation + +Mandatory when alternating mode calls are implemented in the TA. + +## 6.4A Voice call mode +CVMOD + +**Table 13: +CVMOD parameter command syntax** + +| Command | Possible response(s) | +|-----------------------|-------------------------------------------| +| +CVMOD=[] | | +| +CVMOD? | +CVMOD: | +| +CVMOD=? | +CVMOD: (list of supported s) | + +### Description + +Set command selects the voice call mode for making a Mobile Originated voice call from the UE. The voice call mode can be CS\_ONLY, VOIP\_ONLY, CS\_PREFERRED or VOIP\_PREFERRED. Type of VoIP session preferred (e.g. SIP VoIP, IMS VoIP) is manufacturer specific issue. + +NOTE 1: If the Call Mode is set to CS\_ONLY, then the ATD command will make a call in CS mode. + +If the Call Mode is set to VOIP\_ONLY, then the ATD command will make a call in VoIP mode. + +If the Call Mode is set to CS\_PREFERRED, then the ATD command gives preference for CS based voice call. + +If the Call Mode is set to VOIP\_PREFERRED, then the ATD command gives preference for VoIP based voice call + +NOTE 2: The preferences are not applicable for the emergency call. + +NOTE 3: The preferences are not applicable if operator has set preferences for UE originated calls/sessions, 3GPP TS 24.216 [75] subclause 5.6. + +Read command returns the current value of . + +Test command returns the values supported by the UE. + +#### Defined values + +: integer type + +- 0 CS\_ONLY +- 1 VOIP\_ONLY +- 2 CS\_PREFERRED +- 3 VOIP\_PREFERRED + +#### Implementation + +Optional. + +## 6.5 Hangup call +CHUP + +**Table 13a: +CHUP action command syntax** + +| Command | Possible response(s) | +|---------|----------------------| +| +CHUP | | +| +CHUP=? | | + +#### Description + +Execution command causes the TA to hangup the current GSM/UMTS call of the MT. + +NOTE: The purpose of this command is not to replace the ITU-T Recommendation V.250 [14] command H, but to give an assured procedure to terminate an alternating mode call. Refer next subclause. + +#### Implementation + +Mandatory when alternating mode calls implemented in the TA. + +## 6.6 Alternating mode call control method + +This subclause describes the procedure to handle alternating mode calls with AT commands. Procedures are mandatory when alternating mode calls are implemented in the TA. + +NOTE 1: ATH and drop DTR will not necessarily cause a hangup from voice mode. If the +CVHU is implemented the behaviour shall be controlled by its setting. + +### Voice followed by data call (bearer service 81) + +Figure 4 shows commands to start the call, to switch from voice to data (In-Call Modification) and to hang up the call. +CMOD and +FCLASS commands indicate the current settings before dialling or answering command, not that they shall be given just before D or A command. Refer subclause "Cellular result codes +CRC" for possible +CRING result code values. Refer Annex F for a detailed example. + +![Figure 4: Voice followed by data call state transition diagram](933ecd14c858bf3fc919222d8e357bc8_img.jpg) + +``` + +stateDiagram-v2 + direction TB + MO: MO +AT+CMOD=3 +AT+FCLASS=0 + MT: MT ++CRING: VOICE/XXX +AT+CMOD=3;+FCLASS=0 + + MO --> VOICE : ATDxxx; + MT --> VOICE : ATA + VOICE --> DATA : ATD or ATA or +remote initiated + VOICE --> HANGUP : AT+CHUP or +remote initiated hangup +(or ATH +or drop DTR) + DATA --> HANGUP : ATH or +drop DTR or +AT+CHUP or +remote initiated hangup + HANGUP: HANGUP +TA sets +CMOD=0 + +``` + +The diagram illustrates the state transitions for a voice call followed by a data call (bearer service 81). It starts with two initial states: MO (Mobile Originated) and MT (Mobile Terminated). Both states lead to the VOICE state. The MO state is initialized with AT+CMOD=3 and AT+FCLASS=0, and the MT state with +CRING: VOICE/XXX and AT+CMOD=3;+FCLASS=0. Transitions from VOICE to DATA are initiated by ATD or ATA or remote initiated commands. Transitions from VOICE to HANGUP are initiated by AT+CHUP or remote initiated hangup (or ATH or drop DTR) commands. Transitions from DATA to HANGUP are initiated by ATH or drop DTR or AT+CHUP or remote initiated hangup commands. The HANGUP state is initialized with TA sets +CMOD=0. + +Figure 4: Voice followed by data call state transition diagram + +**Figure 4: Voice followed by data call** + +### Voice/ data call (bearer service number 61) + +Figure 5 shows the commands to start the call, to switch between modes (In-Call Modification) and to hang up the call. +CMOD and +FCLASS commands indicate the current settings before dialling or answering command, not that they shall be given just before D or A command. Refer subclause "Cellular result codes +CRC" for possible +CRING result code values. Refer Annex E for a detailed example. + +![Figure 5: Alternating voice and data call state transition diagram](1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg) + +``` + +stateDiagram-v2 + direction TB + MT_V: MT voice first ++CRING: ALT VOICE/XXX +AT+CMOD=2;+FCLASS=0 + MO: MO +AT+CMOD=2 +AT+FCLASS=0 + MT_D: MT data first ++CRING: ALT XXX/VOICE +AT+CMOD=2;+FCLASS=0 + + MT_V --> VOICE : ATA + MO --> VOICE : ATDxxx; + MO --> DATA : ATDxxx + MT_D --> DATA : ATA + + VOICE --> DATA : ATD or ATA or +remote initiated + DATA --> VOICE : ATH or drop DTR or +remote initiated + + VOICE --> HANGUP : AT+CHUP or +remote initiated hangup +(or ATH +or drop DTR) + DATA --> HANGUP : AT+CHUP or +remote initiated hangup + + HANGUP: HANGUP +TA sets +CMOD=0 + +``` + +The diagram illustrates the state transitions for alternating voice and data calls (bearer service number 61). It starts with three initial states: MT voice first, MO, and MT data first. MT voice first and MO lead to the VOICE state, while MT data first and MO lead to the DATA state. The MT voice first state is initialized with +CRING: ALT VOICE/XXX and AT+CMOD=2;+FCLASS=0. The MO state is initialized with AT+CMOD=2 and AT+FCLASS=0. The MT data first state is initialized with +CRING: ALT XXX/VOICE and AT+CMOD=2;+FCLASS=0. Transitions from VOICE to DATA are initiated by ATD or ATA or remote initiated commands. Transitions from DATA to VOICE are initiated by ATH or drop DTR or remote initiated commands. Transitions from VOICE to HANGUP are initiated by AT+CHUP or remote initiated hangup (or ATH or drop DTR) commands. Transitions from DATA to HANGUP are initiated by AT+CHUP or remote initiated hangup commands. The HANGUP state is initialized with TA sets +CMOD=0. + +Figure 5: Alternating voice and data call state transition diagram + +**Figure 5: Alternating voice and data call** + +### Voice/ fax call (teleservice number 61) + +Figure 6 shows the commands to start the call, to switch between modes (In-Call Modification) and to hang up the call. +CMOD and +FCLASS commands indicate the current settings before dialling or answering command, not that they shall be given just before D or A command. The parameter "x" of +FCLASS command can be 1, 1.0, 2 or 2.0. + +NOTE 2: The transition from fax mode to voice mode is for further study. + +![Figure 6: Alternating voice and fax call flowchart. The diagram shows three initial states: 'MT voice first', 'MO', and 'MT fax first'. 'MT voice first' and 'MO' lead to 'VOICE' state via 'ATA' and 'ATDxxx;' commands respectively. 'MT fax first' and 'MO' lead to 'FAX' state via 'ATA' and 'ATDxxx' commands respectively. A transition from 'VOICE' to 'FAX' is labeled 'ATD or remote initiated'. Both 'VOICE' and 'FAX' states lead to 'HANGUP' state via 'AT+CHUP or remote initiated hangup (or ATH or drop DTR)' and 'refer ITU-T T.31 [11] and T.32 [12] for different hangup possibilities (also AT+CHUP shall hangup)' commands respectively. The 'HANGUP' state is labeled 'TA sets +CMOD=0'.](dbbc0baac7341cda76cc4f8355dce23f_img.jpg) + +``` + +graph TD + subgraph MT_voice_first [MT voice first] + M1["+CRING: ALT VOICE/FAX +AT+CMOD=1;+FCLASS=x"] + end + subgraph MO [MO] + M2["AT+CMOD=1 +AT+FCLASS=x"] + end + subgraph MT_fax_first [MT fax first] + M3["+CRING: ALT FAX/VOICE +AT+CMOD=1;+FCLASS=x"] + end + M1 -- ATA --> VOICE + M2 -- ATDxxx; --> VOICE + M2 -- ATDxxx --> FAX + M3 -- ATA --> FAX + VOICE -- "ATD or remote initiated" --> FAX + VOICE -- "AT+CHUP or remote initiated hangup +(or ATH or drop DTR)" --> HANGUP + FAX -- "refer ITU-T T.31 [11] and T.32 [12] +for different hangup possibilities +(also AT+CHUP shall hangup)" --> HANGUP + HANGUP -- "TA sets +CMOD=0" --> HANGUP + +``` + +Figure 6: Alternating voice and fax call flowchart. The diagram shows three initial states: 'MT voice first', 'MO', and 'MT fax first'. 'MT voice first' and 'MO' lead to 'VOICE' state via 'ATA' and 'ATDxxx;' commands respectively. 'MT fax first' and 'MO' lead to 'FAX' state via 'ATA' and 'ATDxxx' commands respectively. A transition from 'VOICE' to 'FAX' is labeled 'ATD or remote initiated'. Both 'VOICE' and 'FAX' states lead to 'HANGUP' state via 'AT+CHUP or remote initiated hangup (or ATH or drop DTR)' and 'refer ITU-T T.31 [11] and T.32 [12] for different hangup possibilities (also AT+CHUP shall hangup)' commands respectively. The 'HANGUP' state is labeled 'TA sets +CMOD=0'. + +Figure 6: Alternating voice and fax call + +## 6.7 Select bearer service type +CBST + +Table 14: +CBST parameter command syntax + +| Command | Possible response(s) | +|-----------------------------------|-----------------------------------------------------------------------------------------------| +| +CBST=[[, [, ]]] | | +| +CBST? | +CBST: , , | +| +CBST=? | +CBST: (list of supported s) , (list of supported s) , (list of supported s) | + +### Description + +Set command selects the bearer service with data rate , and the connection element to be used when data calls are originated (refer 3GPP TS 22.002 [1]). Values may also be used during mobile terminated data call setup, especially in case of single numbering scheme calls (refer +CSNS). + +Test command returns values supported as compound values. + +### Defined values + +NOTE: The default values of the subparameters are manufacturer specific since they depend on the purpose of the device and data services provided by it. Not all combinations of these subparameters are supported by GSM/UMTS (refer 3GPP TS 22.002 [1]). + +: integer type + +- 0 autobauding (automatic selection of the speed; this setting is possible in case of 3.1 kHz modem and non-transparent service) +- 1 300 bps (V.21) +- 2 1200 bps (V.22) + +- 3 1200/75 bps (V.23) +- 4 2400 bps (V.22bis) +- 5 2400 bps (V.26ter) +- 6 4800 bps (V.32) +- 7 9600 bps (V.32) +- 12 9600 bps (V.34) +- 14 14400 bps (V.34) +- 15 19200 bps (V.34) +- 16 28800 bps (V.34) +- 17 33600 bps (V.34) +- 34 1200 bps (V.120) +- 36 2400 bps (V.120) +- 38 4800 bps (V.120) +- 39 9600 bps (V.120) +- 43 14400 bps (V.120) +- 47 19200 bps (V.120) +- 48 28800 bps (V.120) +- 49 38400 bps (V.120) +- 50 48000 bps (V.120) +- 51 56000 bps (V.120) +- 65 300 bps (V.110) +- 66 1200 bps (V.110) +- 68 2400 bps (V.110 or X.31 flag stuffing) +- 70 4800 bps (V.110 or X.31 flag stuffing) +- 71 9600 bps (V.110 or X.31 flag stuffing) +- 75 14400 bps (V.110 or X.31 flag stuffing) +- 79 19200 bps (V.110 or X.31 flag stuffing) +- 80 28800 bps (V.110 or X.31 flag stuffing) +- 81 38400 bps (V.110 or X.31 flag stuffing) +- 82 48000 bps (V.110 or X.31 flag stuffing) +- 83 56000 bps (V.110 or X.31 flag stuffing; this setting can be used in conjunction with asynchronous non-transparent UDI or RDI service in order to get FTM) +- 84 64000 bps (X.31 flag stuffing; this setting can be used in conjunction with asynchronous non-transparent UDI service in order to get FTM) +- 115 56000 bps (bit transparent) +- 116 64000 bps (bit transparent) + +- 120 32000 bps (PIAFS32k) +- 121 64000 bps (PIAFS64k) +- 130 28800 bps (multimedia) +- 131 32000 bps (multimedia) +- 132 33600 bps (multimedia) +- 133 56000 bps (multimedia) +- 134 64000 bps (multimedia) +- all other values below 128 are reserved by the present document. + +: integer type + +- 0 data circuit asynchronous (UDI or 3.1 kHz modem) +- 1 data circuit synchronous (UDI or 3.1 kHz modem) +- 2 PAD Access (asynchronous) (UDI) +- 3 Packet Access (synchronous) (UDI) +- 4 data circuit asynchronous (RDI) +- 5 data circuit synchronous (RDI) +- 6 PAD Access (asynchronous) (RDI) +- 7 Packet Access (synchronous) (RDI) +- all other values below 128 are reserved by the present document. + +: integer type + +- 0 transparent +- 1 non-transparent +- 2 both, transparent preferred +- 3 both, non-transparent preferred + +## Implementation + +Mandatory when data calls implemented. + +## 6.8 Radio link protocol +CRLP + +**Table 15: +CRLP parameter command syntax** + +| Command | Possible response(s) | +|---------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| +CRLP=[[, [, [, [, [, ]]]]]] | | +| +CRLP? | +CRLP: , , , [, [, ]]
[+CRLP: , , , [, [, ]]
[...]] | + +| | | +|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CRLP=? | + CRLP: (list of supported s) , (list of supported s) ,
(list of supported s) , (list of supported s) [,
[, (list of supported s) ] ]

[+ CRLP: (list of supported s) , (list of supported
s) , (list of supported s) , (list of supported s)
[, [, (list of supported s) ] ]

[ . . . ] ] | +|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## Description + +Radio link protocol (RLP) parameters used when non-transparent data calls are originated may be altered with set command. Available command subparameters depend on the RLP versions implemented by the device (e.g. may not be available if device supports only versions 0 and 1). + +NOTE 1: If radio link protocol is not used, but some other error correcting protocol (for transparent data calls), ITU-T Recommendation V.250 [14] Error Control Selection test command +ES=? may be used to indicate the presence of the protocol. + +Read command returns current settings for each supported RLP version . Only RLP parameters applicable to the corresponding are returned. + +Test command returns values supported as a compound value. If MT/TA supports several RLP versions , the RLP parameter value ranges for each are returned in a separate line. + +## Defined values + +, : RLP version number in integer format; when version indication is not present it shall equal 0 + +NOTE 2: Versions 0 and 1 share the same parameter set. Read and test commands shall return only one line for this set (where is not present). + +, , , , : IWF to MS window size, MS to IWF window size, acknowledgement timer T1, retransmission attempts N2, re-sequencing period T4 in integer format (default values and value ranges depend on RLP version; refer 3GPP TS 24.022 [18]): T1 and T4 are in units of 10 ms. + +## Implementation + +Mandatory when RLP implemented. + +# 6.9 Service reporting control +CR + +**Table 16: +CR parameter command syntax** + +| Command | Possible response(s) | +|---------------|----------------------------------| +| +CR= [] | | +| +CR? | +CR: | +| +CR=? | +CR: (list of supported s) | + +## Description + +Set command controls whether or not intermediate result code +CR: is returned from the TA to the TE. If enabled, the intermediate result code is transmitted at the point during connect negotiation at which the TA has determined which speed and quality of service will be used, before any error control or data compression reports are transmitted, and before the intermediate result code CONNECT is transmitted. + +NOTE: This command replaces ITU-T Recommendation V.250 [14] command Modulation Reporting Control +MR, which is not appropriate for use in the GSM/UMTS network. Possible error control (other than radio link protocol) and data compression reporting can be enabled with V.250 commands Error Control Reporting +ER and Data Compression Reporting +DR. + +Test command returns values supported as a compound value. + +#### Defined values + +: integer type + +- 0 disables reporting +- 1 enables reporting + +: + +- ASYNC asynchronous transparent +- SYNC synchronous transparent +- REL ASYNC asynchronous non-transparent +- REL SYNC synchronous non-transparent +- GPRS [] GPRS + + proposes a layer 2 protocol to use between the MT and the TE. It is defined in the Enter GPRS Data Mode (+CGDATA) command. + +#### Implementation + +Mandatory when data calls implemented. + +## 6.10 Extended error report +CEER + +**Table 17: +CEER action command syntax** + +| Command | Possible response(s) | +|---------|----------------------| +| +CEER | +CEER: | +| +CEER=? | | + +#### Description + +Execution command causes the TA to return one or more lines of information text , determined by the MT manufacturer, which should offer the user of the TA an extended report of the reason for + +- the failure in the last unsuccessful call setup (originating or answering) or in-call modification; +- the last call release; +- the last unsuccessful GPRS attach or unsuccessful PDP context activation; +- the last GPRS detach or PDP context deactivation. + +Typically, the text will consist of a single line containing the cause information given by GSM/UMTS network in textual format. + +#### Defined values + +: the total number of characters, including line terminators, in the information text shall not exceed 2041 characters. + +Text shall not contain the sequence 0 or OK. + +#### Implementation + +Optional. + +## 6.11 Cellular result codes +CRC + +**Table 18: +CRC parameter command syntax** + +| Command | Possible response(s) | +|---------------|-----------------------------------| +| +CRC=[] | | +| +CRC? | +CRC: | +| +CRC=? | +CRC: (list of supported s) | + +### Description + +Set command controls whether or not the extended format of incoming call indication or GPRS network request for PDP context activation or notification for VBS/VGCS calls is used. When enabled, an incoming call is indicated to the TE with unsolicited result code +CRING: instead of the normal RING. + +Test command returns values supported as a compound value. + +NOTE 1: Similar command may be found in TTA IS-99 [15] and TTA IS-135 [16]. + +### Defined values + +: integer type + +- 0 disables extended format +- 1 enables extended format + +: + +- ASYNC [, [, , ]] asynchronous transparent +- SYNC [, [, , ]] synchronous transparent +- REL ASYNC [, [, , ]] +non-transparent asynchronous +- REL SYNC [, [, , ]] +non-transparent synchronous +- FAX [, [, , ]] facsimile (TS 62) +- VOICE [, [, , ]] +normal voice (TS 11) (see NOTE 2) +- VOICE/VIDEO [, [, [, , ]]] +voice or video call (see NOTE 2) +- VOICE/XXX [, [, , ]] +voice followed by data (BS 81) (XXX is ASYNC, SYNC, REL ASYNC or REL SYNC) +- ALT VOICE/XXX [, [, , ]] +alternating voice/data, voice first (BS 61) + +- ALT XXX/VOICE [, [, , ]] alternating voice/data, data first (BS 61) +- ALT VOICE/FAX [, [, , ]] alternating voice/fax, voice first (TS 61) +- ALT FAX/VOICE [, [, , ]] alternating voice/fax, fax first (TS 61) +- GPRS , [, [, ]] GPRS network request for PDP context activation +- VGC , , [, ] voice group call (TS 91) +- VBC , , [, ] voice broadcast call (TS 92) + +NOTE 2: The =VOICE/VIDEO is used for voice and/or video calls. It is implementation specific whether this type will replace the =VOICE or if both the types =VOICE/VIDEO and =VOICE are supported. + + indicates the eMLPP priority level of the incoming call by paging, notification or setup message. The priority level values are as defined in eMLPP specification 3GPP TS 22.067 [54]. + +: string type subaddress of format specified by + +: type of subaddress octet in integer format (refer 3GPP TS 24.008 [8] subclause 10.5.4.8) or RFC 4715 [122] appendix A. + +: integer type. Call identification number, see +CLCCS. + +, and are as defined in the Define PDP Context (+CGDCONT) command. proposes a layer 2 protocol to use between the MT and the TE. It is defined in the Enter GPRS Data Mode (+CGDATA) command. If the MT is unable to announce to the TE the network's request (for example it is in V.250 online data state) the MT shall reject the request. No corresponding unsolicited result code shall be issued when the MT returns to a command state. + + is a part of the group call reference as specified in 3GPP TS 23.003 [7] and indicates group call area. See the commands +CAJOIN, +CAREJ and +CALCC. + + is a part of the group call reference as specified in 3GPP TS 23.003 [7] and indicates group call identification. See the commands +CAJOIN, +CAREJ and +CALCC. + +: proposes that a predefined confirmation procedure is to be used after the call is ended. The value 1 indicates that a predefined confirmation procedure is to be used after the call is ended. The value 0 indicates that no confirmation procedure is required. See the parameter of command +CALCC. + +## Implementation + +Mandatory when data or fax circuit mode calls are implemented, or for an MT supporting AT commands only and eMLPP or VGCS or VBS is implemented. + +## 6.12 HSCSD device parameters +CHSD + +Table 19: +CHSD action command syntax + +| Command | Possible response(s) | +|---------|--------------------------------------------------------------------------| +| +CHSD | +CHSD: ,,,,

+CME ERROR: | +| +CHSD=? | | + +### Description + +Execution command returns information about HSCSD features (refer 3GPP TS 22.034 [29]) supported by the MT/TA. Refer subclause 9.2 for possible values. + +The return information is only applicable in GERAN. + +### Defined values + +: integer type; multislot class + +: integer type; maximum number of receive timeslots that MT can use + +: integer type; maximum number of transmit timeslots that MT can use + +: integer type; total number of receive and transmit timeslots that MT can use at the same time (per TDMA frame). The following applies in a HSCSD call: $1 \leq (\text{receive slots}) + (\text{transmit slots}) \leq \text{}$ + + is a sum of integers each representing a supported channel coding (e.g. value 5 indicates that 4,8k and 9,6k channel codings are supported): + +- 1 4,8k full rate data traffic channel +- 4 9,6k full rate data traffic channel +- 8 14,4k full rate data traffic channel +- 16 28,8k full rate data traffic channel (only possible when 14.4k is supported) +- 32 32,0k full rate data traffic channel (only possible in a two-timeslot configuration) +- 64 43,2k full rate data traffic channel (only possible when 14.4k is supported) + +### Implementation + +Mandatory when HSCSD implemented. + +This command is not applicable to UTRAN or E-UTRAN UEs. + +## 6.13 HSCSD transparent call configuration +CHST + +Table 20: +CHST parameter command syntax + +| Command | Possible response(s) | +|---------------------------|------------------------| +| +CHST=[[,]] | | +| +CHST? | +CHST: , | +| +CHST=? | | + +### Description + +Set command controls parameters for transparent HSCSD calls in GERAN. Changing them during a call does not affect the current call. + +NOTE: In UTRAN or E-UTRAN, values set with this command are not needed. The only applicable parameter is , which is set with +CBST command. + +#### Defined values + +: integer type; wanted amount of receive timeslots. Default value 0 indicates that TA shall calculate a proper value from currently selected fixed network user rate ( subparameter from +CBST command) and + +: a sum of integers each representing a channel coding that is accepted for transparent HSCSD calls. Default value 0 indicates that all supported codings are accepted (refer +CHSD command for other values) + +#### Implementation + +Mandatory when transparent HSCSD implemented. + +This command is not applicable to UTRAN or E-UTRAN UEs. + +## 6.14 HSCSD non-transparent call configuration +CHSN + +**Table 21: +CHSN parameter command syntax** + +| Command | Possible response(s) | +|--------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| +CHSN=[[, [, [, ]]]] | | +| +CHSN? | +CHSN: , , , | +| +CHSN=? | +CHSN: (list of supported s) , (list of supported s) , (list of supported s) , (list of supported s) | + +#### Description + +Set command controls parameters for originating non-transparent HSCSD calls. Values may also be used during mobile terminated data call setup. In GERAN, changing or value during a call does not affect the current call. In GERAN, changing of or affects the current call only if was non-zero when call was established. + +#### Defined values + +: integer type; wanted air interface user rate. Default value 0 indicates that TA shall calculate a proper value from currently selected fixed network user rate ( subparameter from +CBST command), , and (or from +CHSD command if =0). Other values: + +- 1 9600 bps +- 2 14400 bps +- 3 19200 bps +- 4 28800 bps +- 5 38400 bps +- 6 43200 bps +- 7 57600 bps + +: integer type; wanted amount of receive timeslots. Default value 0 indicates that TA shall calculate a proper value from currently selected and . This parameter is not applicable to UTRAN or E-UTRAN UEs. + +: integer type; top value for that user is going to request during the next established non-transparent HSCSD call. Default value 0 indicates that user is not going to change / during the next call. This parameter is not applicable to UTRAN or E-UTRAN UEs. + +: a sum of integers each representing a channel coding that is accepted for non-transparent HSCSD calls. Default value 0 indicates that all supported codings are accepted (refer +CHSD command for other values). This parameter is not applicable to UTRAN or E-UTRAN UEs. + +#### Implementation + +Mandatory when non-transparent HSCSD implemented. + +### 6.15 HSCSD current call parameters +CHSC + +Table 22: +CHSC action command syntax + +| Command | Possible response(s) | +|---------|-------------------------------------| +| +CHSC | +CHSC: , , , | +| +CHSC=? | | + +#### Description + +Execution command returns information about current HSCSD call. If no HSCSD call is active, all parameters returned shall equal zero. If HSCSD call is active in UTRAN or E-UTRAN, all non-applicable parameters returned shall be equal to zero. (It is manufacturer specific whether non-zero information is returned in case of an active normal single-slot data call.) + +#### Defined values + +: integer type; number of receive timeslots currently in use. This parameter is not applicable in UTRAN or E-UTRAN. + +: integer type; number of transmit timeslots currently in use. This parameter is not applicable in UTRAN or E-UTRAN. + +: integer type; current air interface user rate (in case of transparent service this equals fixed network user rate) (refer +CHSN command for possible values). For the two-timeslot ECSD bit transparent configuration the following additional values apply: + +- 8 56000 bps +- 9 64000 bps + +: current channel coding (refer +CHSD command for possible values). This parameter is not applicable in UTRAN or E-UTRAN. + +#### Implementation + +Optional. + +### 6.16 HSCSD parameters report +CHSR + +Table 23: +CHSR parameter command syntax + +| Command | Possible response(s) | +|-------------------|------------------------------------| +| +CHSR= [ ] | | +| +CHSR? | +CHSR: | +| +CHSR=? | +CHSR: (list of supported s) | + +## Description + +Enabled command returns intermediate result code +CHSR: from the TA to the TE when an HSCSD call is being set up. The result code represents the current (negotiated or renegotiated) HSCSD parameters. If enabled, the intermediate result code is transmitted at the point of the call setup negotiation where the TA has determined what type of an HSCSD connection will be used. Result code transmission is done after possible service (+CR), error control (+ER), and/or compression (+DR) reporting but before possible TE-TA rate (+ILRR) reporting and before the intermediate result code CONNECT is transmitted. The format of the intermediate result code is: + ++CHSR: , , , + +For the value definitions, refer to +CHSN and +CHSC commands. For instance, for a non-transparent HSCSD call, result code '+CHSR: 2, 2, 4, 8' means that the call has two timeslots in both up- and downlink, the air interface user rate is 28800 bps, and the used channel coding TCH/F14.4. + +In UTRAN or E-UTRAN, all non-applicable parameters returned shall be equal to zero. + +Read command returns the current value of . + +Test command returns the values supported by the UE. + +## Defined values + +: integer type + +- 0 disables reporting +- 1 enables reporting + +## Implementation + +Mandatory when HSCSD implemented + +# 6.17 HSCSD automatic user initiated upgrading +CHSU + +**Table 24: +CHSU parameter command syntax** + +| Command | Possible response(s) | +|--------------|------------------------------------| +| +CHSU= | | +| +CHSU? | +CHSU: | +| +CHSU=? | +CHSU: (list of supported s) | + +## Description + +Set command controls whether or not automatic user initiated service level upgrading shall be used for non-transparent HSCSD calls. "Automatic" means that, if enabled, the ME/TA shall use the UP bit in the received RLP frames to determine when to initiate user initiated service level upgrading (i.e. when to modify the +CHSN parameters and/or for the current call). Refer to 3GPP TS 27.001 [41] for details on the interpretation of the UP bit(s). + +NOTE 1: The validity of the UP bit in the RLP frames depends on the result of the RLP negotiations. The UP bit shall only be used if the result of the RLP negotiations were successful with respect to the UP bit. + +NOTE 2: This command is only applicable in GERAN. + +## Defined values + +: integer type + +- 0 disables use of UP bit for upgrading +- 1 enables use of UP bit for upgrading + +## Implementation + +Optional + +This command is not applicable to UTRAN or E-UTRAN UEs. + +## 6.18 HSCSD non-transparent asymmetry configuration +CHSA + +**Table 25: +CHSA parameter command syntax** + +| Command | Possible response(s) | +|--------------|------------------------------------| +| +CHSA= | | +| +CHSA? | +CHSA: | +| +CHSA=? | +CHSA: (list of supported s) | + +### Description + +Set command controls the preferred asymmetry bias for non-transparent ECSD calls. Downlink biased asymmetry means that 8-PSK modulation is preferred downlink and GMSK modulation uplink. Uplink based asymmetry means that 8-PSK modulation is preferred uplink and GMSK downlink. Changing of affects the current call only if (refer +CHSN) was non-zero when call was established. + +Test command returns values supported by the MT/TA as compound values. The subparameter range indirectly indicates the UE Type; range (0-1) indicates UE Type A and range (0-2) indicates UE Type B. + +NOTE 1: ECSD is also controlled by +CHSD, +CHSN and +CHST. + +NOTE 2: This command is only applicable in GERAN. + +### Defined values + +: integer type + +- 0 No preference +- 1 Downlink biased asymmetry +- 2 Uplink biased asymmetry + +### Implementation + +Mandatory when non-transparent ECSD is implemented. + +This command is not applicable to UTRAN or E-UTRAN UEs. + +## 6.19 Single numbering scheme +CSNS + +**Table 26: +CSNS parameter command syntax** + +| Command | Possible response(s) | +|----------------|------------------------------------| +| +CSNS=[] | | +| +CSNS? | +CSNS: | +| +CSNS=? | +CSNS: (list of supported s) | + +### Description + +Set command selects the bearer or teleservice to be used when mobile terminated single numbering scheme call is established. Parameter values set with +CBST command shall be used when equals to a data service. + +Test command returns values supported as compound values. + +### Defined values + +: integer type + +- 0 voice +- 1 alternating voice/fax, voice first (TS 61) +- 2 fax (TS 62) +- 3 alternating voice/data, voice first (BS 61) +- 4 data +- 5 alternating voice/fax, fax first (TS 61) +- 6 alternating voice/data, data first (BS 61) +- 7 voice followed by data (BS 81) + +#### Implementation + +Optional. + +## 6.20 Voice hangup control +CVHU + +Table 27: +CVHU parameter command syntax + +| Command | Possible response(s) | +|--------------|------------------------------------| +| +CVHU= | | +| +CVHU? | +CVHU: | +| +CVHU=? | +CVHU: (list of supported s) | + +#### Description + +Set command selects whether ATH or "drop DTR" shall cause a voice connection to be disconnected or not. By voice connection is also meant alternating mode calls that are currently in voice mode. (See subclause 6.6). + +NOTE: When = 2, this command must be seen in conjunction with the ITU-T Recommendation V.250 [14] command &D. Else &D shall be ignored. + +#### Defined values + +: integer type + +- 0 "Drop DTR" ignored but OK response given. ATH disconnects. +- 1 "Drop DTR" and ATH ignored but OK response given. +- 2 "Drop DTR" behaviour according to &D setting. ATH disconnects. + +#### Implementation + +Optional + +## 6.21 CCITT V.120 [36] rate adaption protocol +CV120 + +Table 28: +CV120 parameter command syntax + +| Command | Possible response(s) | +|-----------------------------------------------------------------------|-------------------------------------------------------------| +| +CV120=[[, [, [, [, [, ]]]]] | | +| +CV120? | +CV120: , , , , , | + +| | | +|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| +CV120=? | +CV120: (list of supported s) , (list of supported s) , (list of supported s) , (list of supported s) , (list of supported s) , (list of supported s) | +|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## Description + +Set command sets the values of the V.120 protocol parameters (defined in CCITT Recommendation V.120 [36]) that are carried in the GSM BC and/or LLC information elements. + +Read command returns current settings for the V.120 parameters. + +Test command returns values supported as a compound value. + +## Defined values + +: integer type + +- 0 rate adaption header not included +- 1 rate adaption header included (mandatory for protocol sensitive modes). + +: integer type + +- 0 multiple frame establishment not supported, only UI frames allowed +- 1 multiple frame establishment supported, both I and UI frames allowed. + +: integer type + +- 0 bit transparent mode of operation +- 1 protocol sensitive mode of operation. + +: integer type + +- 0 no negotiation, LLI = 256 only +- 1 negotiation allowed. + +NOTE: indicates the connection over which the negotiation is performed. + +: integer type + +- 0 message originator is "default assignee" +- 1 message originator is "assignor only". + +: integer type + +- 0 negotiation is done using logical link zero +- 1 negotiation is done with USER INFORMATION messages on a temporary signalling connection. + +GSM/UMTS does not support all the possible modes of V.120 operation. However, in order to accommodate possible future additions, the complete set of parameters is included in the command. + +The permitted values are: 1, 1 or 0, 1, 0, 0, 0. + +A recommended set of default values is: 1, 1, 1, 0, 0, 0. + +## Implementation + +Mandatory, if the MT supports V.120 interworking. + +## 6.22 Settings date format +CSDF + +Table 29: +CSDF parameter command syntax + +| Command | Possible response(s) | +|----------------------------------|------------------------------------------------------------------------------------------------| +| +CSDF=[ [] [, ] ] | +CME ERROR: | +| +CSDF? | +CSDF: [, ]
+CME ERROR: | +| +CSDF=? | +CSDF: (list of supported s)
[, (list of supported s) ]
+CME ERROR: | + +### Description + +This command sets the date format via MMI of the date information presented to the user, which is specified by use of the parameter. The affects the date format on the phone display and doesn't affect the date format of the AT command serial interface. The command also sets the date format of the TE-TA interface, which is specified by use of the parameter (e.g. the affects the