gsmSRF in IP connected to gsmSSF in MSC or GMSC via ISUP and accessed by gsmSCF through direct Signalling System No.7 Connection | See Note 1 | See Note 2 | - | See Notes 3 and 6.
For gsmSRF in VPLMN see Note 4; For gsmSRF in HPLMN see note 5 | - | +| Scenario 2a
assisting gsmSSF in MSC or GMSC connected to gsmSSF in MSC or GMSC via ISUP. Assisting gsmSSF is accessed by gsmSCF through direct Signalling System No.7 Connection.
gsmSRF is co-located with assisting gsmSSF and accessed (by gsmSCF) by relay via assisting gsmSSF over an internal nodal interface | See Note 1
For gsmSRF in VPLMN see Notes 4 and 6; For gsmSRF in HPLMN see note 5 and 6 | - | See Note 2 | - | See Note 3 | +| Scenario 2b
assisting gsmSSF in MSC or GMSC connected to gsmSSF in MSC or GMSC via ISUP. Assisting gsmSSF is accessed by gsmSCF through direct Signalling System No.7 Connection
gsmSRF is in IP connected to assisting gsmSSF and accessed (by gsmSCF) by relay through ISUP or DSS1 via assisting gsmSSF | See Note 1
See Notes 4 and 6 | See Notes 4 and 6 | See Note 2 | - | See Note 3 | +| Scenario 3
gsmSRF is co-located with a gsmSSF in an MSC or GMSC and accessed by relay via gsmSSF over an internal nodal interface | For gsmSRF in VPLMN see Notes 4; For gsmSRF in HPLMN see notes 5 and 6 | - | - | - | - | +| Scenario 4
gsmSRF in IP connected to gsmSSF and accessed by gsmSCF by relay through ISUP or DSS1 via gsmSSF | See Notes 4 and 6 | See Notes 4 and 6 | - | - | - | + +NOTE 1: Basic for establishment of interface when CorrelationID and SCFiD are transferred in the AssistingSSPIPRoutingAddress. Bilateral when CorrelationID and SCFiD are transferred by other means than in the AssistingSSPIPRoutingAddress. + +NOTE 2: Basic for establishment of interface when CorrelationID and SCFiD are transferred in the Called Party Number. Bilateral when CorrelationID and SCFiD are transferred by other means than in the Called Party Number. + +NOTE 3: Basic when the full Called Party Number received in VPLMN or HPLMN is transferred on its own in the AssistRequestInstructions operation CorrelationID parameter to a gsmSCF in HPLMN. + +Bilateral when CorrelationID is extracted from Called Party Number in HPLMN or VPLMN and transferred on its own in AssistRequestInstructions CorrelationID field to a gsmSCF in HPLMN. + +NOTE 4: Bilateral for the playing of announcements via elementaryMessageIDs and variableMessages, playing of tones and the collection of DTMF digits. + +NOTE 5: Basic for the playing of announcements via elementaryMessageIDs and variableMessages, playing of tones and the collection of DTMF digits. + +NOTE 6: Bilateral for the playing of announcements via text to speech translation, translation of DTMF digits via speech to caller and the translation of voice to digits. + +#### 4.1.3 CAP protocol architecture + +Many of the terms used in the present subclause are based on the OSI application layer structure as defined in ISO 9545 (1989) [81]. + +The CAP protocol architecture is illustrated in figure 4-2. + +A Physical Entity (PE) has either single interactions (case a) or multiple co-ordinated interactions (case b) with another PE. + +In case (a), SACF provides a co-ordination function in using Application Service Elements (ASEs), which includes the ordering of operations supported by ASE(s), in the order of received primitives. The Single Association Object (SAO) represents the SACF plus a set of ASEs to be used over a single interaction between a pair of PEs. + +In case (b), MACF provides a co-ordinating function among several SAO's, each of which interacts with an SAO in a remote PE. + +Each ASE supports one or more operations. Description of each operation is tied with the action of corresponding Functional Entity (FE) modelling. For FE modelling, refer to ITU-T Recommendation Q.1224 [50] and clause 11 of the present document. Each operation is specified using the OPERATION macro described in figure 4-3. + + + +The diagram illustrates the CAP protocol architecture for two cases: + +- Multiple coordinated interactions case b:** + - An **Application process** is connected to a **MACF** block. + - The **MACF** block is connected to two **SAO** (Single Association Object) blocks. + - Each **SAO** block contains a table with two columns: **S A C F** and **A S E's**. The **A S E's** column is further divided into **TCAP**. + - Both **SAO** blocks are connected to a common **SCCP** block. + - The **SCCP** block is connected to an **MTP** block. +- Single interaction case a:** + - An **Application process** is connected to a **SAO** block. + - The **SAO** block contains a table with two columns: **S A C F** and **A S E's**. The **A S E's** column is further divided into **TCAP**. + - The **SAO** block is connected to a common **SCCP** block. + - The **SCCP** block is connected to an **MTP** block. + +Diagram illustrating the CAP protocol architecture for two cases: Multiple coordinated interactions (case b) and Single interaction (case a). + +NOTE: CAP is the collection of all specifications in ASEs. + +**Figure 4-2: CAP protocol architecture** + + + +The diagram illustrates the operation description for CAP, showing the interaction between INAP User ASEs and TCAP ASE. + +**INAP User ASEs** (top box) contains the following elements: + +- xyz OPERATION +- ARGUMENT {Parameter1, Parameter2,...} +- RESULT {Parameter1, Parameter2,...} +- LINKED {operation3, operation4,...} +- ERRORS {error1, error2....} +- error1 ERROR +- PARAMETER {Parameter6, Parameter7,...} +- etc + +An arrow labeled "to peer" points from the INAP User ASEs box to a list of elements: **Operations**, **Results**, and **Errors**. + +**TCAP ASE** (bottom box) contains two sub-layers: + +- COMPONENT SUB-LAYER** +- TRANSACTION SUB-LAYER** + +Arrows labeled "to peer" point from each sub-layer to a list of elements: + +- From **COMPONENT SUB-LAYER**: **INVOKE**, **RETURN RESULT**, **RETURN ERROR**, **REJECT** +- From **TRANSACTION SUB-LAYER**: **BEGIN**, **CONTINUE**, **END**, **ABORT**, **UNIDIRECTIONAL** + +A double-headed arrow points from the **TCAP ASE** box down to **CONNECTIONLESS SCCP**. + +Diagram of Operation description showing INAP User ASEs and TCAP ASE layers and their interactions. + +**Figure 4-3: Operation description** + +#### 4.1.4 Compatibility mechanisms used for CAP + +##### 4.1.4.1 Introduction + +The present subclause specifies the compatibility mechanisms that shall be used for CAP. + +Two major categories of compatibility are handled by these mechanisms: + +- compatibility with the ITU-T Recommendation Q.1228 [51] version of CS2 INAP and the specification EN 301 140-1 version of CS2 INAP [26]; +- compatibility with future versions of CAP. + +The second category has three subcategories of compatibility dealt with within the present subclause: + +- **Minor changes to CAP in future versions of CAP:** +A minor change can be defined as a change of a functionality which is not essential for the requested IN service. Where it is a modification of an existing function, it is acceptable that the addressed function is executed in either the older or the modified variant. If the change is purely additional, then it is acceptable that it is not executed at all and that the peer Application Entity (AE) need not know about the effects of the change. For minor changes, a new Application Context is not required. +- **Major changes to CAP in future versions of CAP:** +A major change can be defined as a change of a functionality which is essential for the requested IN service. Where it is a modification of an existing function, both application entities shall have a shared knowledge about the addressed functional variant. If the change is purely additional and one of the application entities does not support the additional functionality, then the requested IN service will not be provided. For major changes, a new Application Context is required. + +- Network-specific changes to CAP: + +These additions may be of either the major or minor type for a service. No new Application Context is expected to be defined for this type of change. At the time of definition of these network-specific changes to CAP, the additions would not be expected to be included in identical form in future versions of CAP. + +#### 4.1.4.2 Definition of CAP compatibility mechanisms + +##### 4.1.4.2.1 Compatibility mechanism for interworking of CAP with ETSI CS2 Core INAP and ITU-T Q.1228 INAP + +On receipt of an operation according to ITU-T Recommendation Q.1228 [51] or an operation according to ETSI EN 301 140-1 [26], which is not part of the CAP or is part of the CAP but which contains parameters which are not part of the CAP: + +- the gsmSSF, gsmSCF, assisting gsmSSF and gsmSRF shall apply the normal error handling for unknown operations or parameters, i.e. the normal error handling procedures as specified in clause 10 shall be followed. + +Tagging of CAP additions to ITU-T Recommendation Q.1228 [51] and ETSI EN 301 140-1 [26] are specified from 50 to 59. + +##### 4.1.4.2.2 Procedures for major additions to CAP + +In order to support the introduction of major functional changes, the protocol allows a synchronisation between the two applications with regard to which functionality is to be performed. This synchronisation takes place before the new function is invoked in either application entity, in order to avoid complicated fall-back procedures. + +##### 4.1.4.2.3 Procedures for minor additions to CAP + +The extension mechanism marker shall be used for future standardised minor additions to CAP. This mechanism implements extensions by including an "extensions marker" in the type definition. The extensions are expressed by optional fields that are placed after the marker. When an entity receives unrecognised parameters that occur after the extension marker, they are ignored. Refer to ITU-T Recommendation X.680 [53] for further details on the extension mechanism. + +##### 4.1.4.2.4 Procedures for inclusion of network specific additions to CAP + +This mechanism is based on the ability to explicitly declare fields of any type via the Macro facility in ASN.1 at the outermost level of a type definition. It works by defining an "ExtensionField" that is placed within the type definition. This extension field is defined as a set of extensions, where an extension can contain any type. Each extension is associated with an identification that unambiguously identifies the extension. Refer to ITU-T Recommendation Q.1400 [52] for a definition of this mechanism. + +#### 4.1.5 Definition and usage of LegID + +##### 4.1.5.1 Definition of LegID + +In CAP V4, two types of LegID may be exchanged between the gsmSCF and the gsmSSF. These are: + +- Sending Side LegID; and +- Receiving Side LegID. + +Sending Side LegID is always used in operations sent from the gsmSCF to the gsmSSF, and Receiving Side LegID is always used in operations sent from the gsmSSF to the gsmSCF. + +##### 4.1.5.2 Allocation of LegID + +For all operations containing a LegID: + +- LegID = 1 shall always refer to the Calling Party, more specifically that party in the call present when InitialDP is sent to the gsmSCF; +- LegID = 2 shall always refer to a Called Party, more specifically a party in the call created as a result of the InitialDP operation, followed by the Connect, Continue or ContinueWithArgument operation. + +- LegID > 2 shall always refer to a Called Party, more specifically a party in the call created as a result of the InitiateCallAttempt operation, followed by the ContinueWithArgument operation. + +## 4.2 SACF/MACF rules + +### 4.2.1 Reflection of TC AC + +TC AC negotiation rules require that the proposed AC, if acceptable, is reflected in the first backwards message. + +NOTE: If the gsmSSF, gprsSSF or smsSSF provides an AC which is not acceptable to the gsmSCF, then an alternate AC shall not be returned. If the AC presented to the gsmSCF is not acceptable, then this is most probably due to an error in subscriber data provisioning or an error at the gsmSSF, gprsSSF or smsSSF. + +### 4.2.2 Sequential/parallel execution of operations + +In some cases it may be necessary to distinguish whether operations should be performed sequentially or in parallel (synchronised). Operations which may be synchronised are: + +- charging operations; may be synchronised with any other operation(s). + +The method of indicating to the receiving entity that operations should be synchronised is to transmit these operations in a single TC message. If one of the operations identified above shall not be executed until the execution of another operation has progressed to a certain extent or has finished, then the sending PE shall control this by sending the operations in two separate TC messages. + +This method does not imply that all operations sent in a single TC message shall be executed simultaneously, but that where it could make sense to do so (in the situations identified above) the operations should be synchronised. + +In the case of inconsistency between the above-mentioned generic rules and the FE-specific rules, as specified in clause 9, the FE-specific rules take precedence over the generic rules. + +## 5 Common CAP Types + +### 5.1 Data types + +``` +CAP-datatypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) +modules(3) cap-datatypes(52) version8(7)} +``` + +``` +DEFINITIONS IMPLICIT TAGS ::= BEGIN +``` + +``` +IMPORTS +``` + +``` +Duration, +Integer4, +Interval, +LegID, +ServiceKey +``` + +``` +FROM CS1-DataTypes {itu-t(0) identified-organization(4) etsi(0) inDomain(1) in-network(1) +modules(0) cs1-datatypes(2) version1(0)} +``` + +``` +BothwayThroughConnectionInd, +CriticalityType, +MiscCallInfo +``` + +``` +FROM CS2-datatypes {itu-t(0) identified-organization(4) etsi(0) inDomain(1) in-network(1) +cs2(20) modules(0) in-cs2-datatypes(0) version1(0)} +``` + +``` +AddressString, +CellGlobalIdOrServiceAreaIdFixedLength, +Ext-BasicServiceCode, +IMSI, +ISDN-AddressString, +LAIFixedLength, +NAEA-CIC +``` + +``` +FROM MAP-CommonDataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0)} +``` + +``` + +gsm-Network(1) modules(3) map-CommonDataTypes(18) version12(12)} + + Ext-QoS-Subscribed, + Ext2-QoS-Subscribed, + Ext3-QoS-Subscribed, + GeographicalInformation, + GSN-Address, + LocationInformation, + LSAIdentity, + QoS-Subscribed, + RAIdentity, + SubscriberState, + GPRSChargingID +FROM MAP-MS-DataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-MS-DataTypes(11) version12(12)} + + CallReferenceNumber, + SuppressionOfAnnouncement +FROM MAP-CH-DataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-CH-DataTypes(13) version12(12)} + + tc-Messages, + classes +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} + + EXTENSION, + PARAMETERS-BOUND, + SupportedExtensions +FROM CAP-classes classes + + ExtensionContainer +FROM MAP-ExtensionDataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-ExtensionDataTypes(21) version12(12)} + +; + +AccessPointName {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minAccessPointNameLength .. bound.&maxAccessPointNameLength)) +-- Indicates the AccessPointName, refer to 3GPP TS 24.008 [9] for the encoding. +-- It shall be coded as in the value part defined in 3GPP TS 24.008, +-- i.e. the 3GPP TS 24.008 IEI and 3GPP TS 24.008 octet length indicator +-- shall not be included. + +AChBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE + (bound.&minAChBillingChargingLength .. bound.&maxAChBillingChargingLength)) + (CONSTRAINED BY {-- shall be the result of the BER-encoded value of the type -- + CAMEL-AChBillingChargingCharacteristics {bound}}) +-- The AChBillingChargingCharacteristics parameter specifies the charging related information +-- to be provided by the gsmSSF and the conditions on which this information has to be reported +-- back to the gsmSCF with the ApplyChargingReport operation. The value of the +-- AChBillingChargingCharacteristics of type OCTET STRING carries a value of the ASN.1 data type: +-- CAMEL-AChBillingChargingCharacteristics. The normal encoding rules are used to encode this +-- value. +-- The violation of the UserDefinedConstraint shall be handled as an ASN.1 syntax error. + +AChChargingAddress {PARAMETERS-BOUND : bound} ::= CHOICE { + legID [2] LegID, + srfConnection [50] CallSegmentID {bound} +} + +AdditionalCallingPartyNumber {PARAMETERS-BOUND : bound} ::= Digits {bound} +-- Indicates the Additional Calling Party Number. + +AlertingPattern ::= OCTET STRING (SIZE(3)) +-- Indicates a specific pattern that is used to alert a subscriber +-- (e.g. distinctive ringing, tones, etc.). + +``` + +- The encoding of the last octet of this parameter is as defined in 3GPP TS 29.002 [11]. +- Only the trailing OCTET is used, the remaining OCTETS shall be sent as NULL (zero) +- The receiving side shall ignore the leading two OCTETS. + +``` +AOCBeforeAnswer ::= SEQUENCE { + aOCInitial [0] CAI-GSM0224, + aOCSubsequent [1] AOCSubsequent OPTIONAL +} +``` + +``` +AOCGPRS ::= SEQUENCE { + aOCInitial [0] CAI-GSM0224, + aOCSubsequent [1] AOCSubsequent OPTIONAL +} +``` + +``` +AOCSubsequent ::= SEQUENCE { + cAI-GSM0224 [0] CAI-GSM0224 , + tariffSwitchInterval [1] INTEGER (1..86400) OPTIONAL +} +``` + +– tariffSwitchInterval is measured in 1 second units + +``` +AppendFreeFormatData ::= ENUMERATED { + overwrite(0), + append (1) +} +``` + +ApplicationTimer ::= INTEGER (0..2047) + +– Used by the gsmSCF to set a timer in the gsmSSF. The timer is in seconds. + +AssistingSSIPRoutingAddress {PARAMETERS-BOUND : bound} ::= Digits {bound} + +– Indicates the destination address of the gsmSRF for the assist procedure. + +``` +AudibleIndicator ::= CHOICE { + tone BOOLEAN, + burstList [1] BurstList +} +``` + +``` +BackwardServiceInteractionInd ::= SEQUENCE { + conferenceTreatmentIndicator [1] OCTET STRING (SIZE(1)) OPTIONAL, + -- acceptConferenceRequest 'xxxx xx01'B + -- rejectConferenceRequest 'xxxx xx10'B + -- if absent from Connect or ContinueWithArgument, + -- then CAMEL service does not affect conference treatment + callCompletionTreatmentIndicator [2] OCTET STRING (SIZE(1)) OPTIONAL, + -- acceptCallCompletionServiceRequest 'xxxx xx01'B, + -- rejectCallCompletionServiceRequest 'xxxx xx10'B + -- if absent from Connect or ContinueWithArgument, + -- then CAMEL service does not affect call completion treatment + ... +} +``` + +``` +BasicGapCriteria {PARAMETERS-BOUND : bound} ::= CHOICE { + calledAddressValue [0] Digits {bound}, + gapOnService [2] GapOnService, + calledAddressAndService [29] SEQUENCE { + calledAddressValue [0] Digits {bound}, + serviceKey [1] ServiceKey, + ... + }, + callingAddressAndService [30] SEQUENCE { + callingAddressValue [0] Digits {bound}, + serviceKey [1] ServiceKey, + ... + } +} +``` + +- Both calledAddressValue and callingAddressValue can be +- incomplete numbers, in the sense that a limited amount of digits can be given. + +- For the handling of numbers starting with the same digit string refer to the detailed procedure of the CallGap operation + +``` +BCSMEvent{PARAMETERS-BOUND : bound} ::= SEQUENCE { + eventTypeBCSM [0] EventTypeBCSM, + monitorMode [1] MonitorMode, + legID [2] LegID OPTIONAL, + dpSpecificCriteria [30] DpSpecificCriteria {bound} OPTIONAL, + automaticRearm [50] NULL OPTIONAL, + ... +} +``` + +- Indicates the BCSM Event information for monitoring. + +``` +BCSM-Failure {PARAMETERS-BOUND : bound} ::= SEQUENCE { + legID [0] LegID OPTIONAL, + cause [2] Cause {bound} OPTIONAL, + ... +} +``` + +``` +BearerCapability {PARAMETERS-BOUND : bound} ::= CHOICE { + bearerCap [0] OCTET STRING (SIZE(2..bound.&maxBearerCapabilityLength)) +} +``` + +- Indicates the type of bearer capability connection to the user. For bearerCap, the ISUP User +- Service Information, ETSI EN 300 356-1 [23] +- encoding shall be used. + +``` +Burst ::= SEQUENCE { + numberOfBursts [0] INTEGER (1..3) DEFAULT 1, + burstInterval [1] INTEGER (1..1200) DEFAULT 2, + numberOfTonesInBurst [2] INTEGER (1..3) DEFAULT 3, + toneDuration [3] INTEGER (1..20) DEFAULT 2, + toneInterval [4] INTEGER (1..20) DEFAULT 2, + ... +} +``` + +- burstInterval, toneDuration and toneInterval are measured in 100 millisecond units + +``` +BurstList ::= SEQUENCE { + warningPeriod [0] INTEGER (1..1200) DEFAULT 30, + bursts [1] Burst, + ... +} +``` + +- warningPeriod is measured in 1 second units. + +``` +CAI-GSM0224 ::= SEQUENCE { + e1 [0] INTEGER (0..8191) OPTIONAL, + e2 [1] INTEGER (0..8191) OPTIONAL, + e3 [2] INTEGER (0..8191) OPTIONAL, + e4 [3] INTEGER (0..8191) OPTIONAL, + e5 [4] INTEGER (0..8191) OPTIONAL, + e6 [5] INTEGER (0..8191) OPTIONAL, + e7 [6] INTEGER (0..8191) OPTIONAL +} +``` + +- Indicates Charge Advice Information to the Mobile Station. For information regarding +- parameter usage, refer to 3GPP TS 22.024 [2]. + +``` +CalledPartyBCDNumber {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minCalledPartyBCDNumberLength .. bound.&maxCalledPartyBCDNumberLength)) +``` + +- Indicates the Called Party Number, including service selection information. +- Refer to 3GPP TS 24.008 [9] for encoding. +- This data type carries only the 'type of number', 'numbering plan +- identification' and 'number digit' fields defined in 3GPP TS 24.008 [9]; +- it does not carry the 'called party BCD number IEI' or 'length of called +- party BCD number contents'. +- In the context of the DestinationSubscriberNumber field in ConnectSMSArg or +- InitialDPSMSArg, a CalledPartyBCDNumber may also contain an alphanumeric +- character string. In this case, type-of-number '101'B is used, in accordance +- with 3GPP TS 23.040 [6]. The address is coded in accordance with the +- GSM 7-bit default alphabet definition and the SMS packing rules + +-- as specified in 3GPP TS 23.038 [15] in this case. + +``` +CalledPartyNumber {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minCalledPartyNumberLength .. bound.&maxCalledPartyNumberLength)) +-- Indicates the Called Party Number. Refer to ETS EN 300 356-1 [23] for encoding. +``` + +-- A CalledPartyNumber may contain national-specific values of the *Nature Of Address indicator*. The filling-in of the national-specific *Nature Of Address indicator* values shall be done in accordance with the national ISUP of the gsmSSF country, e.g. + -- ANSI T1.113-1995 [92]. + -- In terms of ETS EN 300 356-1 [23], the *Destination Address Field* is not present if the *destination address length* is set to zero. This is the case e.g. when the ANSI ISUP *Nature Of Address indicator* indicates *no number present, operator requested* (1110100) or *no number present, cut-through call to carrier* (1110101). + -- See also see 3GPP TS 23.078 [7]. + +``` +CallingPartyNumber {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minCallingPartyNumberLength .. bound.&maxCallingPartyNumberLength)) +-- Indicates the Calling Party Number. Refer to ETS EN 300 356-1 [23] for encoding. +``` + +``` +CallResult {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minCallResultLength .. bound.&maxCallResultLength)) + (CONSTRAINED BY {-- shall be the result of the BER-encoded value of type - + CAMEL-CallResult {bound}}) +-- The violation of the UserDefinedConstraint shall be handled as an ASN.1 syntax error. +``` + +-- This parameter provides the gsmSCF with the charging related information previously requested + -- using the ApplyCharging operation. This shall include the partyToCharge parameter as + -- received in the related ApplyCharging operation to correlate the result to the request + +``` +CallSegmentFailure {PARAMETERS-BOUND : bound} ::= SEQUENCE { + callSegmentID [0] CallSegmentID {bound} OPTIONAL, + cause [2] Cause {bound} OPTIONAL, + ... + } +``` + +CallSegmentID {PARAMETERS-BOUND : bound} ::= INTEGER (1..bound.&numOfCSs) + +``` +CallSegmentToCancel {PARAMETERS-BOUND : bound} ::= SEQUENCE { + invokeID [0] InvokeID OPTIONAL, + callSegmentID [1] CallSegmentID {bound} OPTIONAL, + ... + } +``` + +``` +CAMEL-AChBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= CHOICE { + timeDurationCharging [0] SEQUENCE { + maxCallPeriodDuration [0] INTEGER (1..864000), + releaseIfDurationExceeded [1] BOOLEAN DEFAULT FALSE, + tariffSwitchInterval [2] INTEGER (1..86400) OPTIONAL, + audibleIndicator [3] AudibleIndicator DEFAULT tone: FALSE, + extensions [4] Extensions {bound} OPTIONAL, + ... + } + } +``` + +-- tariffSwitchInterval is measured in 1 second units. + -- maxCallPeriodDuration is measured in 100 millisecond units + +``` +CAMEL-CallResult {PARAMETERS-BOUND : bound} ::= CHOICE { + timeDurationChargingResult [0] SEQUENCE { + partyToCharge [0] ReceivingSideID, + timeInformation [1] TimeInformation, + legActive [2] BOOLEAN DEFAULT TRUE, + callLegReleasedAtTcpExpiry [3] NULL OPTIONAL, + extensions [4] Extensions {bound} OPTIONAL, + aChChargingAddress [5] AChChargingAddress {bound} + DEFAULT legID:receivingSideID:leg1, + ... + } + } +``` + +``` +... +} +} +``` + +``` +CAMEL-FCIBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= CHOICE{ + fCIBCCCAMELsequence1 [0] SEQUENCE { + freeFormatData [0] OCTET STRING (SIZE( + bound.&minFCIBillingChargingDataLength .. bound.&maxFCIBillingChargingDataLength)), + partyToCharge [1] SendingSideID DEFAULT sendingSideID: leg1, + appendFreeFormatData [2] AppendFreeFormatData DEFAULT overwrite, + } + ... +} +``` + +``` +CAMEL-FCIGPRSBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= SEQUENCE{ + fCIBCCCAMELsequence1 [0] SEQUENCE { + freeFormatData [0] OCTET STRING (SIZE( + bound.&minFCIBillingChargingDataLength .. bound.&maxFCIBillingChargingDataLength)), + pDPID [1] PDPID OPTIONAL, + appendFreeFormatData [2] AppendFreeFormatData DEFAULT overwrite, + } + ... +} +``` + +``` +CAMEL-FCISMSBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= CHOICE{ + fCIBCCCAMELsequence1 [0] SEQUENCE { + freeFormatData [0] OCTET STRING (SIZE( + bound.&minFCIBillingChargingDataLength .. bound.&maxFCIBillingChargingDataLength)), + appendFreeFormatData [1] AppendFreeFormatData DEFAULT overwrite + } +} +``` + +``` +CAMEL-SCIBillingChargingCharacteristics ::= CHOICE { + aOCBeforeAnswer [0] AOCBeforeAnswer, + aOCAfterAnswer [1] AOCS subsequent, + aOC-extension [2] CAMEL-SCIBillingChargingCharacteristicsAlt +} +``` + +``` +CAMEL-SCIBillingChargingCharacteristicsAlt ::= SEQUENCE { + ... +} +-- This datatype is for extension in future releases. +``` + +``` +CAMEL-SCIGPRSBillingChargingCharacteristics ::= SEQUENCE { + aOCGPRS [0] AOCGPRS, + pDPID [1] PDPID OPTIONAL, + ... +} +``` + +``` +Carrier {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minCarrierLength .. bound.&maxCarrierLength)) +-- This parameter is used for North America (na) only. +-- It contains the carrier selection field (first octet) followed by Carrier ID +-- information (North America (na)). +``` + +``` +-- The Carrier selection is one octet and is encoded as: +-- 00000000 No indication +-- 00000001 Selected carrier identification code (CIC) pre subscribed and not +-- input by calling party +-- 00000010 Selected carrier identification code (CIC) pre subscribed and input by +-- calling party +-- 00000011 Selected carrier identification code (CIC) pre subscribed, no +-- indication of whether input by calling party (undetermined) +-- 00000100 Selected carrier identification code (CIC) not pre subscribed and +-- input by calling party +``` + +- 00000101 +- to Spare +- 11111110 +- 11111111 Reserved + +- Refer to ANSI T1.113-1995 [92] for encoding of na carrier ID information (3 octets). + +Cause {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minCauseLength .. bound.&maxCauseLength)) + +- Indicates the cause for interface related information. +- Refer to ETSI EN 300 356-1 [23] Cause parameter for encoding. +- For the use of cause and location values refer to ITU-T Recommendation Q.850 [47] +- Shall always include the cause value and shall also include the diagnostics field, +- if available. + +CGEncountered ::= ENUMERATED { + noCGencountered (0), + manualCGencountered (1), + scpOverload (2) + } + +- Indicates the type of automatic call gapping encountered, if any. + +ChangeOfPositionControlInfo {PARAMETERS-BOUND : bound} ::= SEQUENCE SIZE + (1..bound.&numOfChangeOfPositionControlInfo) OF ChangeOfLocation {bound} + +ChangeOfLocation {PARAMETERS-BOUND : bound} ::= CHOICE { + cellGlobalId [0] CellGlobalIdOrServiceAreaIdFixedLength, + serviceAreaId [1] CellGlobalIdOrServiceAreaIdFixedLength, + locationAreaId [2] LAIFixedLength, + inter-SystemHandOver [3] NULL, + inter-PLMNHandOver [4] NULL, + inter-MSCHandOver [5] NULL, + changeOfLocationAlt [6] ChangeOfLocationAlt {bound} + } + +- The cellGlobalId shall contain a Cell Global Identification. + +- The serviceAreaId shall contain a Service Area Identification. + +ChangeOfLocationAlt {PARAMETERS-BOUND : bound} ::= SEQUENCE { + ... + } + +ChargeIndicator ::= OCTET STRING (SIZE (1)) + +- As specified in ITU-T Recommendation Q.763 as follows: +- no indication 'xxxx xx00'B +- no charge 'xxxx xx01'B +- charge 'xxxx xx10'B +- spare 'xxxx xx11'B +- Sending entity shall fill the upper six bits with '0's. +- Receiving entity shall ignore the upper six bits. + +ChargeNumber {PARAMETERS-BOUND : bound} ::= LocationNumber {bound} + +- Information sent in either direction indicating the chargeable number for the call and +- consisting of the odd/even indicator, nature of address indicator, numbering plan indicator, +- and address signals. + +- Uses the LocationNumber format which is based on the Location Number format as defined +- in ITU-T Recommendation Q.763 [45]. +- For example, the ChargeNumber may be a third party number to which a call is billed for +- the 3rd party billing service. In this case, the calling party may request operator assistance +- to charge the call to, for example, their home number. + +- For NA, this parameter uniquely identifies the chargeable number for a call sent into a North +- American long distance carrier. It transports the ChargeNumber Parameter Field as defined in +- ANSI T1.113-1995 [92]. This provides +- - 1 octet for the nature of address indicator field, plus + +- - 1 octet for a numbering plan field, plus +- - up to 5 octets for the address signal (up to 10 digits) +- The Charge Number in ANSI T1.113-1995 [92] normally contains a 10 digit national number within +- the North American Numbering Plan (NANP); longer (e.g. international) charge numbers are not +- supported in ANSI T1.113-1995 [92]. + +``` +ChargingCharacteristics ::= CHOICE { + maxTransferredVolume [0] INTEGER (1..4294967295), + maxElapsedTime [1] INTEGER (1..86400) +} +``` + +- maxTransferredVolume is measured in number of bytes +- maxElapsedTime is measured in seconds + +``` +ChargingResult ::= CHOICE { + transferredVolume [0] TransferredVolume, + elapsedTime [1] ElapsedTime +} +``` + +``` +ChargingRollOver ::= CHOICE { + transferredVolumeRollOver [0] TransferredVolumeRollOver, + elapsedTimeRollOver [1] ElapsedTimeRollOver +} +``` + +- *transferredVolumeRollOver* shall be reported if ApplyChargingReportGPRS reports volume and +- a roll-over has occurred in one or more volume counters. Otherwise, it shall be absent. +- *elapsedTimeRollOver* shall be reported if ApplyChargingReportGPRS reports duration and +- a roll-over has occurred in one or more duration counters. Otherwise, it shall be absent. + +``` +CollectedDigits ::= SEQUENCE { + minimumNbOfDigits [0] INTEGER (1..30) DEFAULT 1, + maximumNbOfDigits [1] INTEGER (1..30), + endOfReplyDigit [2] OCTET STRING (SIZE (1..2)) OPTIONAL, + cancelDigit [3] OCTET STRING (SIZE (1..2)) OPTIONAL, + startDigit [4] OCTET STRING (SIZE (1..2)) OPTIONAL, + firstDigitTimeOut [5] INTEGER (1..127) OPTIONAL, + interDigitTimeOut [6] INTEGER (1..127) OPTIONAL, + errorTreatment [7] ErrorTreatment DEFAULT stdErrorAndInfo, + interruptableAnnInd [8] BOOLEAN DEFAULT TRUE, + voiceInformation [9] BOOLEAN DEFAULT FALSE, + voiceBack [10] BOOLEAN DEFAULT FALSE +} +``` + +- The use of voiceBack and the support of voice recognition via voiceInformation +- is network operator specific. +- The endOfReplyDigit, cancelDigit, and startDigit parameters have been +- designated as OCTET STRING, and are to be encoded as BCD, one digit per octet +- only, contained in the four least significant bits of each OCTET. The following encoding shall +- be applied for the non-decimal characters: +- 1011 (\*), 1100 (#). +- The usage is service dependent. +- firstDigitTimeOut and interDigitTimeOut are measured in seconds. + +``` +CollectedInfo ::= CHOICE { + collectedDigits [0] CollectedDigits +} +``` + +``` +ConnectedNumberTreatmentInd ::= ENUMERATED { + noINImpact (0), + presentationRestricted (1), + presentCalledINNumber (2), + presentCallINNumberRestricted (3) +} +``` + +- This parameter is used to suppress or to display the connected number. + +``` +ControlType ::= ENUMERATED { + sCPOverloaded (0), +} +``` + +``` + +manuallyInitiated (1) +} + +``` + +``` + +CompoundCriteria {PARAMETERS-BOUND : bound} ::= SEQUENCE { + basicGapCriteria [0] BasicGapCriteria {bound}, + scfID [1] ScfID {bound} OPTIONAL +} + +``` + +CorrelationID {PARAMETERS-BOUND : bound} ::= Digits {bound} +– used by gsmSCF for correlation with a previous operation. + +DateAndTime ::= OCTET STRING (SIZE(7)) +– DateAndTime is BCD encoded. The year digit indicating millenium occupies bits +– 0-3 of the first octet, and the year digit indicating century occupies bits +– 4-7 of the first octet. +– The year digit indicating decade occupies bits 0-3 of the second octet, +– whilst the digit indicating the year within the decade occupies bits 4-7 of +– the second octet. +– The most significant month digit occupies bits 0-3 of the third octet, +– and the least significant month digit occupies bits 4-7 of the third octet. +– The most significant day digit occupies bits 0-3 of the fourth octet, +– and the least significant day digit occupies bits 4-7 of the fourth octet. +– The most significant hours digit occupies bits 0-3 of the fifth octet, +– and the least significant digit occupies bits 4-7 of the fifth octet. +– The most significant minutes digit occupies bits 0-3 of the sixth octet, +– and the least significant digit occupies bits 4-7 of the sixth octet. +– The most significant seconds digit occupies bits 0-3 of the seventh octet, +– and the least seconds significant digit occupies bits 4-7 of the seventh octet. +– For the encoding of digits in an octet, refer to the timeAndtimezone parameter. + +DestinationRoutingAddress {PARAMETERS-BOUND : bound} ::= SEQUENCE SIZE(1) OF +CalledPartyNumber {bound} +– Indicates the Called Party Number. + +Digits {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( +bound.&minDigitsLength .. bound.&maxDigitsLength)) +– Indicates the address signalling digits. +– Refer to ETSI EN 300 356-1 [23] Generic Number & Generic Digits parameters for encoding. +– The coding of the subfields 'NumberQualifier' in Generic Number and 'TypeOfDigits' in +– Generic Digits are irrelevant to the CAP; +– the ASN.1 tags are sufficient to identify the parameter. +– The ISUP format does not allow to exclude these subfields, +– therefore the value is network operator specific. +– +– The following parameters shall use Generic Number: +– - AdditionalCallingPartyNumber for InitialDP +– - AssistingSSPIPRoutingAddress for EstablishTemporaryConnection +– - CorrelationID for AssistRequestInstructions +– - CalledAddressValue for all occurrences, CallingAddressValue for all occurrences. +– +– The following parameters shall use Generic Digits: +– - CorrelationID in EstablishTemporaryConnection +– - number in VariablePart +– - digitsResponse in ReceivedInformationArg +– - midCallEvents in oMidCallSpecificInfo and tMidCallSpecificInfo +– +– In the digitsResponse and midCalEvents, the digits may also include the '\*', '#', +– a, b, c and d digits by using the IA5 character encoding scheme. If the BCD even or +– BCD odd encoding scheme is used, then the following encoding shall be applied for the +– non-decimal characters: 1011 (\*), 1100 (#). +– +– AssistingSSPIPRoutingAddress in EstablishTemporaryConnection and CorrelationID in +– AssistRequestInstructions may contain a Hex B digit as address signal. Refer to +– Annex A.6 for the usage of the Hex B digit. +– + +- Note that when CorrelationID is transported in Generic Digits, then the digits shall +- always be BCD encoded. + +``` + +DpSpecificCriteria { PARAMETERS-BOUND : bound } ::= CHOICE { + applicationTimer [1] ApplicationTimer, + midCallControlInfo [2] MidCallControlInfo, + dpSpecificCriteriaAlt [3] DpSpecificCriteriaAlt {bound} +} +-- Exception handling: reception of DpSpecificCriteriaAlt shall be treated like +-- reception of no DpSpecificCriteria. +-- The gsmSCF may set a timer in the gsmSSF for the No_Answer event. +-- If the user does not answer the call within the allotted time, +-- then the gsmSSF reports the event to the gsmSCF. +-- The gsmSCF may define a criterion for the detection of DTMF digits during a call. +-- The gsmSCF may define other criteria in the dpSpecificCriteriaAlt alternative +-- in future releases. + +``` + +``` + +DpSpecificCriteriaAlt { PARAMETERS-BOUND : bound } ::= SEQUENCE { + ... + changeOfPositionControlInfo [0] ChangeOfPositionControlInfo {bound} + numberOfDigits [1] NumberOfDigits OPTIONAL, + interDigitTimeout [2] INTEGER (1..127) OPTIONAL +} +-- interDigitTimeout duration in seconds. + +``` + +``` + +DpSpecificInfoAlt { PARAMETERS-BOUND : bound } ::= SEQUENCE { + ... + oServiceChangeSpecificInfo [0] SEQUENCE { + ext-basicServiceCode [0] Ext-BasicServiceCode OPTIONAL, + ... + initiatorOfServiceChange [1] InitiatorOfServiceChange OPTIONAL, + natureOfServiceChange [2] NatureOfServiceChange OPTIONAL + } + tServiceChangeSpecificInfo [1] SEQUENCE { + ext-basicServiceCode [0] Ext-BasicServiceCode OPTIONAL, + ... + initiatorOfServiceChange [1] InitiatorOfServiceChange OPTIONAL, + natureOfServiceChange [2] NatureOfServiceChange OPTIONAL + } + collectedInfoSpecificInfo [2] SEQUENCE { + calledPartyNumber [0] CalledPartyNumber OPTIONAL, + ... + } +} +-- This datatype is for extension in future releases. + +``` + +``` + +ElapsedTime ::= CHOICE { + timeGPRSIfNoTariffSwitch [0] INTEGER (0..86400), + timeGPRSIfTariffSwitch [1] SEQUENCE { + timeGPRSSinceLastTariffSwitch [0] INTEGER (0..86400), + timeGPRSTariffSwitchInterval [1] INTEGER (0..86400) OPTIONAL + } +} +-- timeGPRSIfNoTariffSwitch is measured in seconds +-- timeGPRSSinceLastTariffSwitch and timeGPRSTariffSwitchInterval are measured in seconds + +``` + +``` + +ElapsedTimeRollOver ::= CHOICE { + rO-TimeGPRSIfNoTariffSwitch [0] INTEGER (0..255), + rO-TimeGPRSIfTariffSwitch [1] SEQUENCE { + rO-TimeGPRSSinceLastTariffSwitch [0] INTEGER (0..255) OPTIONAL, + rO-TimeGPRSTariffSwitchInterval [1] INTEGER (0..255) OPTIONAL + } +} +-- rO-TimeGPRSIfNoTariffSwitch, rO-TimeGPRSSinceLastTariffSwitch and +-- rO-TimeGPRSTariffSwitchInterval +-- present counters indicating the number of parameter range rollovers. + +``` + +``` + +EndUserAddress {PARAMETERS-BOUND: bound} ::= SEQUENCE { + pDPTypeOrganization [0] OCTET STRING (SIZE(1)), + pDPTypeNumber [1] OCTET STRING (SIZE(1)), + pDPAddress [2] OCTET STRING (SIZE( + bound.&minPDPAddressLength .. bound.&maxPDPAddressLength)) OPTIONAL +} + +``` + +- Indicates the EndUserAddress, refer to 3GPP TS 29.060 [12] for the encoding. +- The pDPTypeOrganization shall use the least significant 4 bits of the octet encoded. +- The sender of this parameter shall set the most significant 4 bits of the octet to 1. +- The receiver of this parameter shall ignore the most significant 4 bits of this octet. + +``` + +ErrorTreatment ::= ENUMERATED { + stdErrorAndInfo (0), + help (1), + repeatPrompt (2) +} + +``` + +- stdErrorAndInfo means returning the 'ImproperCallerResponse' error in the event of an error +- condition during collection of user info. + +``` + +EventSpecificInformationBCSM {PARAMETERS-BOUND : bound} ::= CHOICE { + routeSelectFailureSpecificInfo[2] SEQUENCE { + failureCause [0] Cause {bound} OPTIONAL, + ... + }, + oCalledPartyBusySpecificInfo [3] SEQUENCE { + busyCause [0] Cause {bound} OPTIONAL, + ... + }, + oNoAnswerSpecificInfo [4] SEQUENCE { + -- no specific info defined -- + ... + }, + oAnswerSpecificInfo [5] SEQUENCE { + destinationAddress [50] CalledPartyNumber {bound} OPTIONAL, + or-Call [51] NULL OPTIONAL, + forwardedCall [52] NULL OPTIONAL, + chargeIndicator [53] ChargeIndicator OPTIONAL, + ext-basicServiceCode [54] Ext-BasicServiceCode OPTIONAL, + ext-basicServiceCode2 [55] Ext-BasicServiceCode OPTIONAL, + ... + }, + oMidCallSpecificInfo [6] SEQUENCE { + midCallEvents [1] CHOICE { + dTMFDigitsCompleted [3] Digits {bound}, + dTMFDigitsTimeOut [4] Digits {bound} + } OPTIONAL, + ... + }, + oDisconnectSpecificInfo [7] SEQUENCE { + releaseCause [0] Cause {bound} OPTIONAL, + ... + }, + tBusySpecificInfo [8] SEQUENCE { + busyCause [0] Cause {bound} OPTIONAL, + callForwarded [50] NULL OPTIONAL, + routeNotPermitted [51] NULL OPTIONAL, + forwardingDestinationNumber [52] CalledPartyNumber {bound} OPTIONAL, + ... + }, + tNoAnswerSpecificInfo [9] SEQUENCE { + callForwarded [50] NULL OPTIONAL, + forwardingDestinationNumber [52] CalledPartyNumber {bound} OPTIONAL, + ... + }, + tAnswerSpecificInfo [10] SEQUENCE { + destinationAddress [50] CalledPartyNumber {bound} OPTIONAL, + +``` + +``` + +or-Call [51] NULL OPTIONAL, +forwardedCall [52] NULL OPTIONAL, +chargeIndicator [53] ChargeIndicator OPTIONAL, +ext-basicServiceCode [54] Ext-BasicServiceCode OPTIONAL, +ext-basicServiceCode2 [55] Ext-BasicServiceCode OPTIONAL, +... +}, +tMidCallSpecificInfo [11] SEQUENCE { + midCallEvents [1] CHOICE { + dTMFDigitsCompleted [3] Digits {bound}, + dTMFDigitsTimeOut [4] Digits {bound} + } OPTIONAL, + ... +}, +tDisconnectSpecificInfo [12] SEQUENCE { + releaseCause [0] Cause {bound} OPTIONAL, + ... +}, +oTermSeizedSpecificInfo [13] SEQUENCE { + locationInformation [50] LocationInformation OPTIONAL, + ... +}, +callAcceptedSpecificInfo [20] SEQUENCE { + locationInformation [50] LocationInformation OPTIONAL, + ... +}, +oAbandonSpecificInfo [21] SEQUENCE { + routeNotPermitted [50] NULL OPTIONAL, + ... +}, +oChangeOfPositionSpecificInfo [50] SEQUENCE { + locationInformation [50] LocationInformation OPTIONAL, + ..., + metDPCriteriaList [51] MetDPCriteriaList {bound} OPTIONAL +}, +tChangeOfPositionSpecificInfo [51] SEQUENCE { + locationInformation [50] LocationInformation OPTIONAL, + ..., + metDPCriteriaList [51] MetDPCriteriaList {bound} OPTIONAL +}, +dpSpecificInfoAlt [52] DpSpecificInfoAlt {bound} +} + +``` + +-- Indicates the call related information specific to the event. + +``` + +EventSpecificInformationSMS ::= CHOICE { + o-smsFailureSpecificInfo [0] SEQUENCE { + failureCause [0] MO-SMSCause OPTIONAL, + ... + }, + o-smsSubmissionSpecificInfo [1] SEQUENCE { + -- no specific info defined-- + ... + }, + t-smsFailureSpecificInfo [2] SEQUENCE { + failureCause [0] MT-SMSCause OPTIONAL, + ... + }, + t-smsDeliverySpecificInfo [3] SEQUENCE { + -- no specific info defined-- + ... + } +} + +``` + +``` + +EventTypeBCSM ::= ENUMERATED { + collectedInfo (2), + analyzedInformation (3), + routeSelectFailure (4), + oCalledPartyBusy (5), + ... +} + +``` + +``` + + oNoAnswer (6), + oAnswer (7), + oMidCall (8), + oDisconnect (9), + oAbandon (10), + termAttemptAuthorized (12), + tBusy (13), + tNoAnswer (14), + tAnswer (15), + tMidCall (16), + tDisconnect (17), + tAbandon (18), + oTermSeized (19), + callAccepted (27), + oChangeOfPosition (50), + tChangeOfPosition (51), + ..., + oServiceChange (52), + tServiceChange (53) + } + +``` + +- Indicates the BCSM detection point event. +- Values analyzedInformation and termAttemptAuthorized may be used +- for TDPs only. +- Exception handling: reception of an unrecognized value shall be treated +- like reception of no detection point. + +``` + +EventTypeSMS ::= ENUMERATED { + sms-CollectedInfo (1), + o-smsFailure (2), + o-smsSubmission (3), + sms-DeliveryRequested (11), + t-smsFailure (12), + t-smsDelivery (13) +} + +``` + +- Values sms-CollectedInfo and sms-DeliveryRequested may be used for TDPs only. + +``` + +Extensions {PARAMETERS-BOUND : bound} ::= SEQUENCE SIZE (1..bound.&numOfExtensions) OF ExtensionField +ExtensionField ::= SEQUENCE { + +``` + +``` + + type EXTENSION.&id ({SupportedExtensions}), + -- shall identify the value of an EXTENSION type + criticality CriticalityType DEFAULT ignore, + value [1] EXTENSION.&ExtensionType ({SupportedExtensions}{@type}), + ... +} + +``` + +- This parameter indicates an extension of an argument data type. +- Its content is network operator specific + +``` + +FCIBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minFCIBillingChargingLength .. bound.&maxFCIBillingChargingLength)) + (CONSTRAINED BY {-- shall be the result of the BER-encoded value of type -- + CAMEL-FCIBillingChargingCharacteristics {bound}}) + +``` + +- This parameter indicates the billing and/or charging characteristics. +- The violation of the UserDefinedConstraint shall be handled as an ASN.1 syntax error. + +``` + +FCIGPRSBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minFCIBillingChargingLength .. bound.&maxFCIBillingChargingLength)) + (CONSTRAINED BY {-- shall be the result of the BER-encoded value of type - + CAMEL-FCIGPRSBillingChargingCharacteristics {bound}}) + +``` + +- This parameter indicates the GPRS billing and/or charging characteristics. +- The violation of the UserDefinedConstraint shall be handled as an ASN.1 syntax error. + +``` + +FCISMSBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minFCIBillingChargingLength .. bound.&maxFCIBillingChargingLength)) + (CONSTRAINED BY {-- shall be the result of the BER-encoded value of type - + CAMEL-FCISMSBillingChargingCharacteristics {bound}}) + +``` + +- This parameter indicates the SMS billing and/or charging characteristics. +- The violation of the UserDefinedConstraint shall be handled as an ASN.1 syntax error. + +``` + +ForwardServiceInteractionInd ::= SEQUENCE { + conferenceTreatmentIndicator [1] OCTET STRING (SIZE(1)) OPTIONAL, + -- acceptConferenceRequest 'xxxx xx01'B + -- rejectConferenceRequest 'xxxx xx10'B + -- if absent from Connect or ContinueWithArgument, + -- then CAMEL service does not affect conference treatment + callDiversionTreatmentIndicator [2] OCTET STRING (SIZE(1)) OPTIONAL, + -- callDiversionAllowed 'xxxx xx01'B + -- callDiversionNotAllowed 'xxxx xx10'B + -- if absent from Connect or ContinueWithArgument, + -- then CAMEL service does not affect call diversion treatment + callingPartyRestrictionIndicator [4] OCTET STRING (SIZE(1)) OPTIONAL, + -- noINImpact 'xxxx xx01'B + -- presentationRestricted 'xxxx xx10'B + -- if absent from Connect or ContinueWithArgument, + -- then CAMEL service does not affect calling party restriction treatment + ... +} + +``` + +``` + +GapCriteria {PARAMETERS-BOUND : bound} ::= CHOICE { + basicGapCriteria BasicGapCriteria {bound}, + compoundGapCriteria CompoundCriteria {bound} +} + +``` + +``` + +GapIndicators ::= SEQUENCE { + duration [0] Duration, + gapInterval [1] Interval, + ... +} + +``` + +- Indicates the call gapping characteristics. +- No call gapping when gapInterval equals 0. + +``` + +GapOnService ::= SEQUENCE { + serviceKey [0] ServiceKey, + ... +} + +``` + +``` + +GapTreatment {PARAMETERS-BOUND : bound} ::= CHOICE { + informationToSend [0] InformationToSend {bound}, + releaseCause [1] Cause {bound} +} + +``` + +- The default value for Cause is the same as in ISUP. + +``` + +GenericNumber {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minGenericNumberLength .. bound.&maxGenericNumberLength)) + +``` + +- Indicates a generic number. Refer to ETSI EN 300 356-1 [23] Generic number for encoding. + +``` + +GenericNumbers {PARAMETERS-BOUND : bound} ::= SET SIZE(1..bound.&numOfGenericNumbers) OF GenericNumber {bound} + +``` + +``` + +GPRS-QoS ::= CHOICE { + short-QoS-format [0] QoS-Subscribed, + long-QoS-format [1] Ext-QoS-Subscribed +} + +``` + +- Short-QoS-format shall be sent for QoS in pre GSM release 99 format. +- Long-QoS-format shall be sent for QoS in GSM release 99 (and beyond) format. +- Which of the two QoS formats shall be sent is determined by which QoS format is available in the SGSN at the time of sending. +- Refer to 3GPP TS 29.002 [11] for encoding details of QoS-Subscribed and Ext-QoS-Subscribed. + +``` + +GPRS-QoS-Extension ::= SEQUENCE { + supplement-to-long-QoS-format [0] Ext2-QoS-Subscribed, + ... +} + +``` + +``` + +additionalSupplement [1] Ext3-QoS-Subscribed OPTIONAL +} + +``` + +GPRSCause {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE + (bound.&minGPRSCauseLength .. bound.&maxGPRSCauseLength)) + – Shall only include the cause value. + +- 00000000 Unspecified +- All other values shall be interpreted as 'Unspecified'. +- +- This parameter indicates the cause for CAP interface related information. +- The GPRSCause mapping to/from GTP cause values specified in the 3GPP TS 29.060 [12] and +- to/from 3GPP TS 24.008 [9] GMM cause and SM cause values are outside scope of this document. + +``` + +GPRSEvent ::= SEQUENCE { + gPRSEEventType [0] GPRSEventType, + monitorMode [1] MonitorMode +} + +``` + +- Indicates the GPRS event information for monitoring. + +GPRSEventSpecificInformation {PARAMETERS-BOUND : bound} ::= CHOICE { + +``` + +attachChangeOfPositionSpecificInformation + [0] SEQUENCE { + locationInformationGPRS [0] LocationInformationGPRS OPTIONAL, + ... + }, + +``` + +``` + +pdp-ContextchangeOfPositionSpecificInformation + [1] SEQUENCE { + accessPointName [0] AccessPointName {bound} OPTIONAL, + chargingID [1] GPRSChargingID OPTIONAL, + locationInformationGPRS [2] LocationInformationGPRS OPTIONAL, + endUserAddress [3] EndUserAddress {bound} OPTIONAL, + qualityOfService [4] QualityOfService OPTIONAL, + timeAndTimeZone [5] TimeAndTimezone {bound} OPTIONAL, + ..., + gGSNAddress [6] GSN-Address OPTIONAL + }, + +``` + +``` + +detachSpecificInformation [2] SEQUENCE { + initiatingEntity [0] InitiatingEntity OPTIONAL, + ..., + routeingAreaUpdate [1] NULL OPTIONAL +}, + +``` + +``` + +disconnectSpecificInformation [3] SEQUENCE { + initiatingEntity [0] InitiatingEntity OPTIONAL, + ..., + routeingAreaUpdate [1] NULL OPTIONAL +}, + +``` + +``` + +pDPContextEstablishmentSpecificInformation + [4] SEQUENCE { + accessPointName [0] AccessPointName {bound} OPTIONAL, + endUserAddress [1] EndUserAddress {bound} OPTIONAL, + qualityOfService [2] QualityOfService OPTIONAL, + locationInformationGPRS [3] LocationInformationGPRS OPTIONAL, + timeAndTimeZone [4] TimeAndTimezone {bound} OPTIONAL, + pDPInitiationType [5] PDPInitiationType OPTIONAL, + ..., + secondaryPDP-context [6] NULL OPTIONAL + }, + +``` + +``` + +pDPContextEstablishmentAcknowledgementSpecificInformation + [5] SEQUENCE { + +``` + +``` + + accessPointName [0] AccessPointName {bound} OPTIONAL, + chargingID [1] GPRSChargingID OPTIONAL, + endUserAddress [2] EndUserAddress {bound} OPTIONAL, + qualityOfService [3] QualityOfService OPTIONAL, + locationInformationGPRS [4] LocationInformationGPRS OPTIONAL, + timeAndTimeZone [5] TimeAndTimezone {bound} OPTIONAL, + ..., + gGSNAddress [6] GSN-Address OPTIONAL + } +} + +``` + +``` + +GPRSEventType ::= ENUMERATED { + attach (1), + attachChangeOfPosition (2), + detached (3), + pdp-ContextEstablishment (11), + pdp-ContextEstablishmentAcknowledgement (12), + disconnect (13), + pdp-ContextChangeOfPosition (14) +} + +``` + +``` + +InbandInfo {PARAMETERS-BOUND : bound} ::= SEQUENCE { + messageID [0] MessageID {bound}, + numberOfRepetitions [1] INTEGER (1..127) OPTIONAL, + duration [2] INTEGER (0..32767) OPTIONAL, + interval [3] INTEGER (0..32767) OPTIONAL, + ... +} + +``` + +- Interval is the time in seconds between each repeated announcement. Duration is the total +- amount of time in seconds, including repetitions and intervals. +- The end of announcement is either the end of duration or numberOfRepetitions, +- whatever comes first. +- duration with value 0 indicates infinite duration + +``` + +InformationToSend {PARAMETERS-BOUND : bound} ::= CHOICE { + inbandInfo [0] InbandInfo {bound}, + tone [1] Tone +} + +``` + +``` + +InitiatingEntity ::= ENUMERATED { + mobileStation (0), + sgsn (1), + hlr (2), + ggsn (3) +} + +``` + +``` + +InitiatorOfServiceChange ::= ENUMERATED { + a-side (0), + b-side (1) +} + +``` + +``` + +InvokeID ::= INTEGER (-128..127) + +``` + +``` + +IPRoutingAddress {PARAMETERS-BOUND : bound} ::= CalledPartyNumber {bound} +– Indicates the routing address for the IP. + +``` + +``` + +IPSSPCapabilities {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minIPSSPCapabilitiesLength .. bound.&maxIPSSPCapabilitiesLength)) +– Indicates the gsmSRF resources available. The parameter has two parts, a standard and a +– bilateral part. The standard part indicates capabilities defined as optional in CAP +– that shall be recognised (but not necessarily supported) by a gsmSCF. The bilateral +– part contains further information that is not specified in this standard, but which is set +– according to bilateral agreements between network operators and/or equipment vendors. +– The last octet of the standard part is indicated by bit 7 being set to 0, otherwise Bit 7 of +– a standard part octet is set to 1 indicating that the standard part continues in the following + +``` + +– octet. Coding is as follows: + +| | | | +|-----------------|------------------------------------------------------------|-----------------------------------------------------------| +| – Octet 1 | Standard Part for CAP | | +| – Bit | Value | Meaning | +| – 0 | 0 | IPRoutingAddress not supported | +| – | 1 | IPRoutingAddress supported | +| – 1 | 0 | VoiceBack not supported | +| – | 1 | VoiceBack supported | +| – 2 | 0 | VoiceInformation not supported, via speech recognition | +| – | 1 | VoiceInformation supported, via speech recognition | +| – 3 | 0 | VoiceInformation not supported, via voice recognition | +| – | 1 | VoiceInformation supported, via voice recognition | +| – 4 | 0 | Generation of voice announcements from Text not supported | +| – | 1 | Generation of voice announcements from Text supported | +| – 5 | - | Reserved | +| – 6 | - | Reserved | +| – 7 | 0 | End of standard part | +| – | 1 | This value is reserved in CAP | +| – | | | +| – Octets 2 to 4 | Bilateral Part: Network operator/equipment vendor specific | | + +``` +LegOrCallSegment {PARAMETERS-BOUND : bound} ::= CHOICE { + callSegmentID [0] CallSegmentID {bound}, + legID [1] LegID +} +``` + +LegType ::= OCTET STRING (SIZE(1)) + +leg1 LegType ::= '01'H + +leg2 LegType ::= '02'H + +``` +LocationInformationGPRS ::= SEQUENCE { + cellGlobalIdOrServiceAreaIdOrLAI [0] OCTET STRING (SIZE(5..7)) OPTIONAL, + routeingAreaIdentity [1] RAIdentity OPTIONAL, + geographicalInformation [2] GeographicalInformation OPTIONAL, + sgsn-Number [3] ISDN-AddressString OPTIONAL, + selectedLSAIdentity [4] LSAIdentity OPTIONAL, + extensionContainer [5] ExtensionContainer OPTIONAL, + ..., + sai-Present [6] NULL OPTIONAL, + userCSGInformation [7] UserCSGInformation OPTIONAL +} +``` + +– cellGlobalIdOrServiceAreaIdOrLAI shall contain the value part of the + +– CellGlobalIdOrServiceAreaIdFixedLength type or the LAIFixedLength type (i.e. excluding tags + +– and lengths) as defined in 3GPP TS 29.002 [13]. + +– sai-Present indicates that the cellGlobalIdOrServiceAreaIdOrLAI parameter contains + +– a Service Area Identity. + +– UserCSGInformation contains the CSG ID, Access mode, and the CSG Membership Indication in the + +-- case the Access mode is Hybrid Mode, as defined in 3GPP TS 23.060 [93]. + +``` +LocationNumber {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE ( + bound.&minLocationNumberLength .. bound.&maxLocationNumberLength)) +``` + +– Indicates the Location Number for the calling party. + +– Refer to ETSI EN 300 356-1 [23] for encoding. + +``` +LowLayerCompatibility {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE ( + bound.&minLowLayerCompatibilityLength .. bound.&maxLowLayerCompatibilityLength)) +``` + +– indicates the LowLayerCompatibility for the calling party. + +– Refer to 3GPP TS 24.008 [9] for encoding. + +– It shall be coded as in the value part defined in 3GPP TS 24.008. + +-- i.e. the 3GPP TS 24.008 IEI and 3GPP TS 24.008 octet length indicator + +-- shall not be included. + +``` +MessageID {PARAMETERS-BOUND : bound} ::= CHOICE { + elementaryMessageID [0] Integer4, + text [1] SEQUENCE { + messageContent [0] IA5String (SIZE( + bound.&minMessageContentLength .. bound.&maxMessageContentLength)), +``` + +``` + +attributes [1] OCTET STRING (SIZE( + bound.&minAttributesLength .. bound.&maxAttributesLength)) OPTIONAL +}, +elementaryMessageIDs [29] SEQUENCE SIZE (1.. bound.&numOfMessageIDs) OF Integer4, +variableMessage [30] SEQUENCE { + elementaryMessageID [0] Integer4, + variableParts [1] SEQUENCE SIZE (1..5) OF VariablePart {bound} +} +} + +``` + +– Use of the text parameter is network operator/equipment vendor specific. + +MetDPCriteriaList {PARAMETERS-BOUND : bound} ::= SEQUENCE SIZE (1..bound.&numOfChangeOfPositionControlInfo) OF MetDPCriterion {bound} + +``` + +MetDPCriterion {PARAMETERS-BOUND : bound} ::= CHOICE { + enteringCellGlobalId [0] CellGlobalIdOrServiceAreaIdFixedLength, + leavingCellGlobalId [1] CellGlobalIdOrServiceAreaIdFixedLength, + enteringServiceAreaId [2] CellGlobalIdOrServiceAreaIdFixedLength, + leavingServiceAreaId [3] CellGlobalIdOrServiceAreaIdFixedLength, + enteringLocationAreaId [4] LAIFixedLength, + leavingLocationAreaId [5] LAIFixedLength, + inter-SystemHandOverToUMTS [6] NULL, + inter-SystemHandOverToGSM [7] NULL, + inter-PLMNHandOver [8] NULL, + inter-MSCHandOver [9] NULL, + metDPCriterionAlt [10] MetDPCriterionAlt {bound} +} + +``` + +– The enteringCellGlobalId and leavingCellGlobalId shall contain a Cell Global Identification. + +– The enteringServiceAreaId and leavingServiceAreaId shall contain a Service Area Identification. + +MetDPCriterionAlt {PARAMETERS-BOUND : bound} ::= SEQUENCE { + +``` + +... +} + +``` + +``` + +MidCallControlInfo ::= SEQUENCE { + minimumNumberOfDigits [0] INTEGER (1..30) DEFAULT 1, + maximumNumberOfDigits [1] INTEGER (1..30) DEFAULT 30, + endOfReplyDigit [2] OCTET STRING (SIZE (1..2)) OPTIONAL, + cancelDigit [3] OCTET STRING (SIZE (1..2)) OPTIONAL, + startDigit [4] OCTET STRING (SIZE (1..2)) OPTIONAL, + interDigitTimeout [6] INTEGER (1..127) DEFAULT 10, + ... +} + +``` + +``` + +-- +-- - minimumNumberOfDigits specifies the minimum number of digits that shall be collected +-- - maximumNumberOfDigits specifies the maximum number of digits that shall be collected +-- - endOfReplyDigit specifies the digit string that denotes the end of the digits +-- to be collected. +-- - cancelDigit specifies the digit string that indicates that the input shall +-- be erased and digit collection shall start afresh. +-- - startDigit specifies the digit string that denotes the start of the digits +-- to be collected. +-- - interDigitTimeout specifies the maximum duration in seconds between successive +-- digits. +-- +-- endOfReplyDigit, cancelDigit and startDigit shall contain digits in the range 0..9, '*' and '#' +-- only. The collected digits string, reported to the gsmSCF, shall include the endOfReplyDigit and +-- the startDigit, if present. +-- +-- endOfReplyDigit, cancelDigit and startDigit shall be encoded as BCD digits. Each octet shall +-- contain one BCD digit, in the 4 least significant bits of each octet. +-- The following encoding shall be used for the over-decadic digits: 1011 (*), 1100 (#). + +``` + +``` + +MonitorMode ::= ENUMERATED { + interrupted (0), + notifyAndContinue (1), + transparent (2) +} + +``` + +– Indicates the event is relayed and/or processed by the SSP. + +– Transparent means that the gsmSSF or gprsSSF does not notify the gsmSCF of the event. + +-- For the use of this parameter refer to the procedure descriptions in clause 11. + +-- For the RequestNotificationCharging operation, 'interrupted' shall not be used in MonitorMode. + +``` +MO-SMSCause ::= ENUMERATED { + systemFailure (0), + unexpectedDataValue (1), + facilityNotSupported (2), + sM-DeliveryFailure (3), + releaseFromRadioInterface (4) +} +``` + +-- MO SMS error values which are reported to gsmSCF. + +-- Most of these values are received from the SMSC as a response to + +-- MO-ForwardSM operation. + +``` +MT-SMSCause ::= OCTET STRING (SIZE (1)) +``` + +-- This variable is sent to the gsmSCF for a Short Message delivery failure + +-- notification. + +-- If the delivery failure is due to RP-ERROR RPDU received from the MS, + +-- then MT-SMSCause shall be set to the RP-Cause component in the RP-ERROR RPDU. + +-- Refer to 3GPP TS 24.011 [10] for the encoding of RP-Cause values. + +-- Otherwise, if the delivery failure is due to internal failure in the MSC or SGSN + +-- or time-out from the MS, then MT-SMSCause shall be set to 'Protocol error, + +-- unspecified', as defined in 3GPP TS 24.011 [10]. + +``` +NAOliInfo ::= OCTET STRING (SIZE (1)) +``` + +-- NA Oli information takes the same value as defined in ANSI T1.113-1995 [92] + +-- e.g. '3D'H - Decimal value 61 - Cellular Service (Type 1) + +-- '3E'H - Decimal value 62 - Cellular Service (Type 2) + +-- '3F'H - Decimal value 63 - Cellular Service (roaming) + +``` +NatureOfServiceChange ::= ENUMERATED { + userInitiated (0), + networkInitiated (1) +} +``` + +``` +NumberOfDigits ::= INTEGER (1..255) +``` + +-- Indicates the number of digits to be collected. + +``` +OCSIAplicable ::= NULL +``` + +-- Indicates that the Originating CAMEL Subscription Information, if present, shall be + +-- applied on the outgoing call leg created with a Connect operation. For the use of this + +-- parameter see 3GPP TS 23.078 [7]. + +``` +OriginalCalledPartyID {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( +``` + +``` + bound.&minOriginalCalledPartyIDLength .. bound.&maxOriginalCalledPartyIDLength)) +``` + +-- Indicates the original called number. Refer to ETSI EN 300 356-1 [23] Original Called Number + +-- for encoding. + +``` +PDPID ::= OCTET STRING (SIZE (1)) +``` + +-- PDP Identifier is a counter used to identify a specific PDP Context within a control + +-- relationship between gprsSSF and gsmSCF. + +``` +PDPInitiationType ::= ENUMERATED { + mSInitiated (0), + networkInitiated (1) +} +``` + +``` +QualityOfService ::= SEQUENCE { +``` + +``` + requested-QoS [0] GPRS-QoS OPTIONAL, + subscribed-QoS [1] GPRS-QoS OPTIONAL, + negotiated-QoS [2] GPRS-QoS OPTIONAL, +``` + +``` + ..., +``` + +``` + requested-QoS-Extension [3] GPRS-QoS-Extension OPTIONAL, + subscribed-QoS-Extension [4] GPRS-QoS-Extension OPTIONAL, + negotiated-QoS-Extension [5] GPRS-QoS-Extension OPTIONAL +``` + +``` +} +``` + +``` +ReceivingSideID ::= CHOICE { +``` + +``` + receivingSideID [1] LegType +``` + +} + +– used to identify LegID in operations sent from gsmSSF to gsmSCF + +RedirectingPartyID {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE ( + bound.&minRedirectingPartyIDLength .. bound.&maxRedirectingPartyIDLength)) + +– Indicates redirecting number. + +– Refer to ETSI EN 300 356-1 [23] Redirecting number for encoding. + +RequestedInformationList {PARAMETERS-BOUND : bound} ::= SEQUENCE SIZE (1.. numOfInfoItems) OF RequestedInformation {bound} + +RequestedInformationTypeList ::= SEQUENCE SIZE (1.. numOfInfoItems) OF RequestedInformationType + +RequestedInformation {PARAMETERS-BOUND : bound} ::= SEQUENCE { + requestedInformationType [0] RequestedInformationType, + requestedInformationValue [1] RequestedInformationValue {bound}, + ... + } + +RequestedInformationType ::= ENUMERATED { + callAttemptElapsedTime (0), + callStopTime (1), + callConnectedElapsedTime (2), + releaseCause (30) + } + +RequestedInformationValue {PARAMETERS-BOUND : bound} ::= CHOICE { + callAttemptElapsedTimeValue [0] INTEGER (0..255), + callStopTimeValue [1] DateAndTime, + callConnectedElapsedTimeValue [2] Integer4, + releaseCauseValue [30] Cause {bound} + } + +– The callAttemptElapsedTimeValue is specified in seconds. The unit for the + +– callConnectedElapsedTimeValue is 100 milliseconds + +RPCause ::= OCTET STRING (SIZE (1)) + +– RP cause according to 3GPP TS 24.011 [10] or 3GPP TS 29.002 [11]. + +– GsmSCF shall send this cause in the ReleaseSMS operation. + +-- For a MO-SMS service, the MSC or SGSN shall send the RP Cause to the originating MS. + +-- It shall be used to overwrite the RP-Cause element in the RP-ERROR RPDU. + +-- For a MT-SMS service, the MSC or SGSN shall send the RP Cause to the sending SMS-GMSC. + +-- It shall be used to overwrite the RP-Cause element in the RP-ERROR RPDU. + +ScfID {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minScfIDLength .. bound.&maxScfIDLength)) + +– format and length of ScfID is defined by the network operator. + +– Indicates the gsmSCF identity. + +SCIBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE ( + bound.&minSCIBillingChargingLength .. bound.&maxSCIBillingChargingLength)) + (CONSTRAINED BY {– shall be the result of the BER-encoded value of type – + CAMEL-SCIBillingChargingCharacteristics}) + +– Indicates AOC information to be sent to a Mobile Station + +– The violation of the UserDefinedConstraint shall be handled as an ASN.1 syntax error. + +SCIGPRSBillingChargingCharacteristics {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE ( + bound.&minSCIBillingChargingLength .. bound.&maxSCIBillingChargingLength)) + (CONSTRAINED BY {– shall be the result of the BER-encoded value of type – + CAMEL-SCIGPRSBillingChargingCharacteristics}) + +– Indicates AOC information to be sent to a Mobile Station + +– The violation of the UserDefinedConstraint shall be handled as an ASN.1 syntax error. + +SendingSideID ::= CHOICE {sendingSideID [0] LegType} + +– used to identify LegID in operations sent from gsmSCF to gsmSSF + +ServiceInteractionIndicatorsTwo ::= SEQUENCE { + +``` + +forwardServiceInteractionInd[0] ForwardServiceInteractionInd OPTIONAL, +-- applicable to operations InitialDP, Connect and ContinueWithArgument. +backwardServiceInteractionInd [1] BackwardServiceInteractionInd OPTIONAL, +-- applicable to operations Connect and ContinueWithArgument. +bothwayThroughConnectionInd [2] BothwayThroughConnectionInd OPTIONAL, +-- applicable to ConnectToResource and EstablishTemporaryConnection +connectedNumberTreatmentInd [4] ConnectedNumberTreatmentInd OPTIONAL, +-- applicable to Connect and ContinueWithArgument +nonCUGCall [13] NULL OPTIONAL, +-- applicable to Connect and ContinueWithArgument +-- indicates that no parameters for CUG shall be used for the call (i.e. the call shall +-- be a non-CUG call). +-- If not present, it indicates one of three things: +-- a) continue with modified CUG information (when one or more of either CUG Interlock Code +-- and Outgoing Access Indicator are present), or +-- b) continue with original CUG information (when neither CUG Interlock Code or Outgoing +-- Access Indicator are present), i.e. no IN impact. +-- c) continue with the original non-CUG call. +holdTreatmentIndicator [50] OCTET STRING (SIZE(1)) OPTIONAL, +-- applicable to InitialDP, Connect and ContinueWithArgument +-- acceptHoldRequest 'xxxx xx01'B +-- rejectHoldRequest 'xxxx xx10'B +-- if absent from Connect or ContinueWithArgument, +-- then CAMEL service does not affect call hold treatment +cwTreatmentIndicator [51] OCTET STRING (SIZE(1)) OPTIONAL, +-- applicable to InitialDP, Connect and ContinueWithArgument +-- acceptCw 'xxxx xx01'B +-- rejectCw 'xxxx xx10'B +-- if absent from Connect or ContinueWithArgument, +-- then CAMEL service does not affect call waiting treatment +ectTreatmentIndicator [52] OCTET STRING (SIZE(1)) OPTIONAL, +-- applicable to InitialDP, Connect and ContinueWithArgument +-- acceptEctRequest 'xxxx xx01'B +-- rejectEctRequest 'xxxx xx10'B +-- if absent from Connect or ContinueWithArgument, +-- then CAMEL service does not affect explicit call transfer treatment +... +} + +``` + +SGSNCapabilities ::= OCTET STRING (SIZE (1)) + +-- Indicates the SGSN capabilities. The coding of the parameter is as follows: + +| Bit | Value | Meaning | +|-----|-------|---------------------------------| +| 0 | 0 | AoC not supported by SGSN | +| | 1 | AoC supported by SGSN | +| 1 | - | This bit is reserved in CAP V.3 | +| 2 | - | This bit is reserved in CAP V.3 | +| 3 | - | This bit is reserved in CAP V.3 | +| 4 | - | This bit is reserved in CAP V.3 | +| 5 | - | This bit is reserved in CAP V.3 | +| 6 | - | This bit is reserved in CAP V.3 | +| 7 | - | This bit is reserved in CAP V.3 | + +SMS-AddressString ::= AddressString (SIZE (1 .. maxSMS-AddressStringLength)) + +-- This data type is used to transport CallingPartyNumber for MT-SMS. + +-- If this data type is used for MO-SMS, then the maximum number of digits shall be 16. + +-- An SMS-AddressString may contain an alphanumeric character string. In this + +-- case, a nature of address indicator '101'B is used, in accordance with + +-- 3GPP TS 23.040 [6]. The address is coded in accordance with the GSM 7-bit + +-- default alphabet definition and the SMS packing rules as specified in + +-- 3GPP TS 23.038 [15] in this case. + +maxSMS-AddressStringLength INTEGER ::= 11 + +``` + +SMSEvent ::= SEQUENCE { + eventTypeSMS [0] EventTypeSMS, + +``` + +``` + + monitorMode [1] MonitorMode + } + +``` + +``` + +TariffSwitchInterval ::= INTEGER (1 .. 86400) +-- TariffSwitchInterval is measured in 1 second units + +``` + +``` + +TimeAndTimezone {PARAMETERS-BOUND : bound} ::= OCTET STRING (SIZE( + bound.&minTimeAndTimezoneLength .. bound.&maxTimeAndTimezoneLength)) +-- Indicates the time and timezone, relative to GMT. This parameter is BCD encoded. +-- The year digit indicating millenium occupies bits 0-3 of the first octet, and the year +-- digit indicating century occupies bits 4-7 of the first octet. +-- The year digit indicating decade occupies bits 0-3 of the second octet, whilst the digit +-- indicating the year within the decade occupies bits 4-7 of the second octet. +-- The most significant month digit occupies bits 0-3 of the third octet, and the least +-- significant month digit occupies bits 4-7 of the third octet. +-- The most significant day digit occupies bits 0-3 of the fourth octet, and the least +-- significant day digit occupies bits 4-7 of the fourth octet. +-- The most significant hours digit occupies bits 0-3 of the fifth octet, and the least +-- significant hours digit occupies bits 4-7 of the fifth octet. +-- The most significant minutes digit occupies bits 0-3 of the sixth octet, and the least +-- significant minutes digit occupies bits 4-7 of the sixth octet. +-- The most significant seconds digit occupies bits 0-3 of the seventh octet, and the least +-- significant seconds digit occupies bits 4-7 of the seventh octet. +-- +-- The timezone information occupies the eighth octet. For the encoding of Timezone refer to +-- 3GPP TS 23.040 [6]. +-- +-- The BCD digits are packed and encoded as follows: +-- +-- Bit 7 6 5 4 | 3 2 1 0 +-- -- 2nd digit | 1st digit Octet 1 +-- -- 3rd digit | 4th digit Octet 2 +-- -- .. | .. Octet m +-- +-- 0000 digit 0 +-- 0001 digit 1 +-- 0010 digit 2 +-- 0011 digit 3 +-- 0100 digit 4 +-- 0101 digit 5 +-- 0110 digit 6 +-- 0111 digit 7 +-- 1000 digit 8 +-- 1001 digit 9 +-- 1010 spare +-- 1011 spare +-- 1100 spare +-- 1101 spare +-- 1110 spare +-- 1101 spare +-- +-- where the leftmost bit of the digit is either bit 7 or bit 3 of the octet. + +``` + +``` + +TimeIfNoTariffSwitch ::= INTEGER(0..864000) +-- TimeIfNoTariffSwitch is measured in 100 millisecond intervals + +``` + +``` + +TimeIfTariffSwitch ::= SEQUENCE { + timeSinceTariffSwitch [0] INTEGER(0..864000), + tariffSwitchInterval [1] INTEGER(1..864000) OPTIONAL +} +-- timeSinceTariffSwitch and tariffSwitchInterval are measured in 100 millisecond intervals + +``` + +``` + +TimeInformation ::= CHOICE { + timeIfNoTariffSwitch [0] TimeIfNoTariffSwitch, + +``` + +``` + +timeIfTariffSwitch [1] TimeIfTariffSwitch +} + +``` + +– Indicates call duration information + +``` + +TimerID ::= ENUMERATED { + tssf (0) +} + +``` + +– Indicates the timer to be reset. + +``` + +TimerValue ::= Integer4 + +``` + +– Indicates the timer value (in seconds). + +``` + +Tone ::= SEQUENCE { + toneID [0] Integer4, + duration [1] Integer4 OPTIONAL, + ... +} + +``` + +– The duration specifies the length of the tone in seconds, value 0 indicates infinite duration. + +``` + +TPDataCodingScheme ::= OCTET STRING (SIZE (1)) + +``` + +– TP Data Coding Scheme according to 3GPP TS 23.040 [6] + +``` + +TPProtocolIdentifier ::= OCTET STRING (SIZE (1)) + +``` + +– indicates the protocol used above the SM-Transfer Layer as specified in 3GPP TS 23.040 [6]. + +``` + +TPShortMessageSpecificInfo ::= OCTET STRING (SIZE (1)) + +``` + +– contains the 1st octet of the applicable TPDU or the SMS-COMMAND TPDU as specified in 3GPP TS 23.040 [6]. + +``` + +TPValidityPeriod ::= OCTET STRING (SIZE (1..7)) + +``` + +– indicates the length of the validity period or the absolute time of the validity + +– period termination as specified in 3GPP TS 23.040 [6]. + +– the length of ValidityPeriod is either 1 octet or 7 octets + +``` + +TransferredVolume ::= CHOICE { + volumeIfNoTariffSwitch [0] INTEGER (0..4294967295), + volumeIfTariffSwitch [1] SEQUENCE { + volumeSinceLastTariffSwitch [0] INTEGER (0..4294967295), + volumeTariffSwitchInterval [1] INTEGER (0..4294967295) OPTIONAL + } +} + +``` + +– volumeIfNoTariffSwitch, volumeSinceLastTariffSwitch and volumeTariffSwitchInterval + +– are measured in bytes. + +``` + +TransferredVolumeRollOver ::= CHOICE { + rO-VolumeIfNoTariffSwitch [0] INTEGER (0..255), + rO-VolumeIfTariffSwitch [1] SEQUENCE { + rO-VolumeSinceLastTariffSwitch [0] INTEGER (0..255) OPTIONAL, + rO-VolumeTariffSwitchInterval [1] INTEGER (0..255) OPTIONAL + } +} + +``` + +– rO-VolumeIfNoTariffSwitch, rO-VolumeSinceLastTariffSwitch and rO-VolumeTariffSwitchInterval + +– present counters indicating the number of parameter range rollovers. + +``` + +UnavailableNetworkResource ::= ENUMERATED { + unavailableResources (0), + componentFailure (1), + basicCallProcessingException (2), + resourceStatusFailure (3), + endUserFailure (4) +} + +``` + +– Indicates the network resource that failed. + +``` + +VariablePart {PARAMETERS-BOUND : bound} ::= CHOICE { + integer [0] Integer4, + +``` + +``` + +number [1] Digits {bound}, -- Generic digits +time [2] OCTET STRING (SIZE(2)), -- HH: MM, BCD coded +date [3] OCTET STRING (SIZE(4)), -- YYYYMMDD, BCD coded +price [4] OCTET STRING (SIZE(4)) +} + +``` + +- Indicates the variable part of the message. Time is BCD encoded. +- The most significant hours digit occupies bits 0-3 of the first octet, and the least +- significant digit occupies bits 4-7 of the first octet. The most significant minutes digit +- occupies bits 0-3 of the second octet, and the least significant digit occupies bits 4-7 +- of the second octet. +- +- Date is BCD encoded. The year digit indicating millennium occupies bits 0-3 of the first octet, +- and the year digit indicating century occupies bits 4-7 of the first octet. The year digit +- indicating decade occupies bits 0-3 of the second octet, whilst the digit indicating the year +- within the decade occupies bits 4-7 of the second octet. +- The most significant month digit occupies bits 0-3 of the third octet, and the least +- significant month digit occupies bits 4-7 of the third octet. The most significant day digit +- occupies bits 0-3 of the fourth octet, and the least significant day digit occupies bits 4-7 +- of the fourth octet. +- Price is BCD encoded. The digit indicating hundreds of thousands occupies bits 0-3 of the +- first octet, and the digit indicating tens of thousands occupies bits 4-7 of the first octet. +- The digit indicating thousands occupies bits 0-3 of the second octet, whilst the digit +- indicating hundreds occupies bits 4-7 of the second octet. The digit indicating tens occupies +- bits 0-3 of the third octet, and the digit indicating 0 to 9 occupies bits 4-7 of the third +- octet. The tenths digit occupies bits 0-3 of the fourth octet, and the hundredths digit +- occupies bits 4-7 of the fourth octet. +- +- For the encoding of digits in an octet, refer to the timeAndtimezone parameter + +-- The Definition of range of constants follows + numOfInfoItems INTEGER ::= 4 + +END + +## 5.2 Error types + +``` +CAP-errorTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) +modules(3) cap-errorTypes(51) version8(7)} +``` + +- This module contains the type definitions for the CAP Error Types. +- Where a parameter of type CHOICE is tagged with a specific tag value, the tag is automatically +- replaced with an EXPLICIT tag of the same value. + +``` +DEFINITIONS IMPLICIT TAGS ::= BEGIN +``` + +``` +IMPORTS +``` + +``` + ros-InformationObjects, + datatypes, + errorcodes +``` + +``` +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} +``` + +``` + ERROR +``` + +``` +FROM Remote-Operations-Information-Objects ros-InformationObjects +``` + +``` + InvokeID, + UnavailableNetworkResource +FROM CAP-datatypes datatypes +``` + +``` + errcode-canceled, + errcode-cancelFailed, + errcode-eTCFailed, + errcode-improperCallerResponse, + errcode-missingCustomerRecord, + errcode-missingParameter, + errcode-parameterOutOfRange, + errcode-requestedInfoError, + errcode-systemFailure, +``` + +``` + errcode-taskRefused, + errcode-unavailableResource, + errcode-unexpectedComponentSequence, + errcode-unexpectedDataValue, + errcode-unexpectedParameter, + errcode-unknownLegID, + errcode-unknownCSID, + errcode-unknownPDPID +FROM CAP-errorcodes errorcodes + +; + +-- TYPE DEFINITION FOR CAP ERROR TYPES FOLLOWS + +canceled ERROR ::= { + CODE errcode-canceled +} +-- The operation has been canceled. + +cancelFailed ERROR ::= { + PARAMETER SEQUENCE { + problem [0] ENUMERATED { + unknownOperation (0), + tooLate (1), + operationNotCancellable (2) + }, + operation [1] InvokeID, + ... + } + CODE errcode-cancelFailed +} +-- The operation failed to be canceled. + +eTCFailed ERROR ::= { + CODE errcode-eTCFailed +} +-- The establish temporary connection failed. + +improperCallerResponse ERROR ::= { + CODE errcode-improperCallerResponse +} +-- The caller response was not as expected. + +missingCustomerRecord ERROR ::= { + CODE errcode-missingCustomerRecord +} +-- The Service Logic Program could not be found in the gsmSCF. + +missingParameter ERROR ::= { + CODE errcode-missingParameter +} +-- An expected optional parameter was not received. + +parameterOutOfRange ERROR ::= { + CODE errcode-parameterOutOfRange +} +-- The parameter was not as expected (e.g. missing or out of range). + +requestedInfoError ERROR ::= { + PARAMETER ENUMERATED { + unknownRequestedInfo (1), + requestedInfoNotAvailable (2) + } + CODE errcode-requestedInfoError +} +-- The requested information cannot be found. + +systemFailure ERROR ::= { + PARAMETER UnavailableNetworkResource + CODE errcode-systemFailure +} +-- The operation could not be completed due to a system failure at the serving physical entity. + +taskRefused ERROR ::= { + PARAMETER ENUMERATED { + generic (0), + unobtainable (1), + congestion (2) + } +} +``` + +``` + + } + CODE errcode-taskRefused + } + -- An entity normally capable of the task requested cannot or chooses not to perform the task at + -- this time. This includes error situations like congestion and unobtainable address as used in + -- e.g. the connect operation.) + + unavailableResource ERROR ::= { + CODE errcode-unavailableResource + } + -- A requested resource is not available at the serving entity. + + unexpectedComponentSequence ERROR ::= { + CODE errcode-unexpectedComponentSequence + } + -- An incorrect sequence of Components was received (e.g. 'DisconnectForwardConnection' + -- followed by 'PlayAnnouncement'). + + unexpectedDataValue ERROR ::= { + CODE errcode-unexpectedDataValue + } + -- The data value was not as expected (e.g. route number expected but billing number received) + + unexpectedParameter ERROR ::= { + CODE errcode-unexpectedParameter + } + -- A parameter received was not expected. + + unknownLegID ERROR ::= { + CODE errcode-unknownLegID + } + -- Leg not known to the gsmSSF. + + unknownCSID ERROR ::= { + CODE errcode-unknownCSID + } + -- Call Segment not known to the gsmSSF. + + unknownPDPID ERROR ::= { + CODE errcode-unknownPDPID + } + -- PDPID not known by the receiving entity. + +END + +``` + +## 5.3 Operation codes + +CAP-operationcodes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) cap-operationcodes(53) version8(7)} + +DEFINITIONS ::= BEGIN + +IMPORTS + +ros-InformationObjects + FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} + +Code + FROM Remote-Operations-Information-Objects ros-InformationObjects + +; + +-- the operations are grouped by the identified operation packages. + +``` + +-- gsmSCF activation Package + opcode-initialDP Code ::= local: 0 +-- gsmSCF/gsmSRF activation of assist Package + opcode-assistRequestInstructions Code ::= local: 16 +-- Assist connection establishment Package + opcode-establishTemporaryConnection Code ::= local: 17 +-- Generic disconnect resource Package + opcode-disconnectForwardConnection Code ::= local: 18 + opcode-dFCWithArgument Code ::= local: 86 +-- Non-assisted connection establishment Package + +``` + +``` + + opcode-connectToResource Code ::= local: 19 +-- Connect Package (elementary gsmSSF function) + opcode-connect Code ::= local: 20 +-- Call handling Package (elementary gsmSSF function) + opcode-releaseCall Code ::= local: 22 +-- BCSM Event handling Package + opcode-requestReportBCSMEVENT Code ::= local: 23 + opcode-eventReportBCSM Code ::= local: 24 +-- gsmSSF call processing Package + opcode-collectInformation Code ::= local: 27 + opcode-continue Code ::= local: 31 +-- gsmSCF call initiation Package + opcode-initiateCallAttempt Code ::= local: 32 +-- Timer Package + opcode-resetTimer Code ::= local: 33 +-- Billing Package + opcode-furnishChargingInformation Code ::= local: 34 +-- Charging Package + opcode-applyCharging Code ::= local: 35 + opcode-applyChargingReport Code ::= local: 36 +-- Traffic management Package + opcode-callGap Code ::= local: 41 +-- Call report Package + opcode-callInformationReport Code ::= local: 44 + opcode-callInformationRequest Code ::= local: 45 +-- Signalling control Package + opcode-sendChargingInformation Code ::= local: 46 +-- Specialized resource control Package + opcode-playAnnouncement Code ::= local: 47 + opcode-promptAndCollectUserInfo Code ::= local: 48 + opcode-specializedResourceReport Code ::= local: 49 +-- Cancel Package + opcode-cancel Code ::= local: 53 +-- Activity Test Package + opcode-activityTest Code ::= local: 55 +-- CPH Response Package + opcode-continueWithArgument Code ::= local: 88 + opcode-disconnectLeg Code ::= local: 90 + opcode-moveLeg Code ::= local: 93 + opcode-splitLeg Code ::= local: 95 +-- Exception Inform Package + opcode-entityReleased Code ::= local: 96 +-- Play Tone Package + opcode-playTone Code ::= local: 97 + +-- Sms Activation Package + opcode-initialDPSMS Code ::= local: 60 +-- Sms Billing Package + opcode-furnishChargingInformationSMS Code ::= local: 61 +-- Sms Connect Package + opcode-connectSMS Code ::= local: 62 +-- Sms Event Handling Package + opcode-requestReportSMSEVENT Code ::= local: 63 + opcode-eventReportSMS Code ::= local: 64 +-- Sms Processing Package + opcode-continueSMS Code ::= local: 65 +-- Sms Release Package + opcode-releaseSMS Code ::= local: 66 +-- Sms Timer Package + opcode-resetTimerSMS Code ::= local: 67 + +-- Gprs Activity Test Package + opcode-activityTestGPRS Code ::= local: 70 +-- Gprs Charging Package + opcode-applyChargingGPRS Code ::= local: 71 + opcode-applyChargingReportGPRS Code ::= local: 72 +-- Gprs Cancel Package + opcode-cancelGPRS Code ::= local: 73 +-- Gprs Connect Package + opcode-connectGPRS Code ::= local: 74 +-- Gprs Processing Package + opcode-continueGPRS Code ::= local: 75 +-- Gprs Exception Information Package + opcode-entityReleasedGPRS Code ::= local: 76 +-- Gprs Billing Package + opcode-furnishChargingInformationGPRS Code ::= local: 77 +-- Gprs Scf Activation Package + opcode-initialDPGPRS Code ::= local: 78 + +``` + +``` + +-- Gprs Release Package + opcode-releaseGPRS Code ::= local: 79 +-- Gprs Event Handling Package + opcode-eventReportGPRS Code ::= local: 80 + opcode-requestReportGPRSEvent Code ::= local: 81 +-- Gprs Timer Package + opcode-resetTimerGPRS Code ::= local: 82 +-- Gprs Charge Advice Package + opcode-sendChargingInformationGPRS Code ::= local: 83 + +END + +``` + +## 5.4 Error codes + +``` + +CAP-errorcodes { itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) +modules(3) cap-errorcodes(57) version8(7) } + +``` + +``` + +DEFINITIONS ::= BEGIN + +``` + +``` + +IMPORTS + +``` + +``` + + ros-InformationObjects +FROM CAP-object-identifiers { itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7) } + +``` + +``` + + Code +FROM Remote-Operations-Information-Objects ros-InformationObjects + +; + +``` + +``` + +errcode-canceled Code ::= local: 0 +errcode-cancelFailed Code ::= local: 1 +errcode-eTCFailed Code ::= local: 3 +errcode-improperCallerResponse Code ::= local: 4 +errcode-missingCustomerRecord Code ::= local: 6 +errcode-missingParameter Code ::= local: 7 +errcode-parameterOutOfRange Code ::= local: 8 +errcode-requestedInfoError Code ::= local: 10 +errcode-systemFailure Code ::= local: 11 +errcode-taskRefused Code ::= local: 12 +errcode-unavailableResource Code ::= local: 13 +errcode-unexpectedComponentSequence Code ::= local: 14 +errcode-unexpectedDataValue Code ::= local: 15 +errcode-unexpectedParameter Code ::= local: 16 +errcode-unknownLegID Code ::= local: 17 +errcode-unknownPDPID Code ::= local: 50 +errcode-unknownCSID Code ::= local: 51 + +``` + +``` + +END + +``` + +## 5.5 Classes + +``` + +CAP-classes { itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) +modules(3) cap-classes(54) version8(7) } + +``` + +``` + +DEFINITIONS ::= BEGIN + +``` + +``` + +IMPORTS + +``` + +``` + + ROS-OBJECT-CLASS, + Code +FROM Remote-Operations-Information-Objects ros-InformationObjects + +``` + +``` + + id-rosObject-gprsSSF, + id-rosObject-gsmSRF, + id-rosObject-gsmSSF, + id-rosObject-smsSSF-V3, + id-rosObject-smsSSF-V4, + ros-InformationObjects, + gsmSSF-gsmSCF-Protocol, + gsmSCF-gsmSRF-Protocol, + smsSSF-gsmSCF-Protocol, + gprsSSF-gsmSCF-Protocol + +``` + +``` + +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} + + capSsfToScfGeneric, + capAssistHandoffssfToScf, + capScfToSsfGeneric +FROM CAP-gsmSSF-gsmSCF-pkgs-contracts-acss gsmSSF-gsmSCF-Protocol + + gsmSRF-gsmSCF-contract +FROM CAP-gsmSCF-gsmSRF-pkgs-contracts-acss gsmSCF-gsmSRF-Protocol + + cap3SMS, + cap4SMS +FROM CAP-smsSSF-gsmSCF-pkgs-contracts-acss smsSSF-gsmSCF-Protocol + + capGprsSsfToScf, + capGsmScfToGprsSsf +FROM CAP-gprsSSF-gsmSCF-pkgs-contracts-acss gprsSSF-gsmSCF-Protocol + + CriticalityType +FROM CS2-datatypes {itu-t(0) identified-organization(4) etsi(0) inDomain(1) in-network(1) cs2(20) +modules(0) in-cs2-datatypes(0) version1(0)} + +; + +gsmSSF ROS-OBJECT-CLASS ::= { + INITIATES {capSsfToScfGeneric| + capAssistHandoffssfToScf} + RESPONDS {capScfToSsfGeneric} + ID id-rosObject-gsmSSF} +-- The Rel-6 'gsmSSF' definition uses the Rel-6 capSsfToScfGeneric, capAssistHandoffssfToScf +-- and capScfToSsfGeneric CONTRACT definitions. + +gsmSRF ROS-OBJECT-CLASS ::= { + INITIATES {gsmSRF-gsmSCF-contract} + ID id-rosObject-gsmSRF} +-- The Rel-6 'gsmSRF' definition uses the Rel-6 gsmSRF-gsmSCF-contract CONTRACT definition. + +smsSSF-V3 ROS-OBJECT-CLASS ::= { + INITIATES {cap3SMS} + ID id-rosObject-smsSSF-V3} +-- The Rel-6 'smsSSF-V3' definition uses the Rel-6 cap3SMS CONTRACT definition. The smsSSF-V3 +-- ROS-OBJECT-CLASS is used for MO SMS control. + +smsSSF-V4 ROS-OBJECT-CLASS ::= { + INITIATES {cap4SMS} + ID id-rosObject-smsSSF-V4} +-- The Rel-6 'smsSSF-V4' definition uses the Rel-6 cap4SMS CONTRACT definition. The smsSSF-V4 +-- ROS-OBJECT-CLASS is used for MT SMS control. + +gprsSSF ROS-OBJECT-CLASS ::= { + INITIATES {capGprsSsfToScf} + RESPONDS {capGsmScfToGprsSsf} + ID id-rosObject-gprsSSF} +-- The Rel-6 'gprsSSF' definition uses the Rel-6 capGprsSsfToGsmScf and capGsmScfToGprsSsf +-- CONTRACT definitions. + +EXTENSION ::= CLASS { + &ExtensionType, + &criticality CriticalityType DEFAULT ignore, + &id Code} + +WITH SYNTAX { + EXTENSION-SYNTAX &ExtensionType + CRITICALITY &criticality + IDENTIFIED BY &id +} +-- Only value Global OBJECT IDENTIFIER is used for &id; +-- Only the value ignore (0) is used for &criticality. + +-- Example of addition of an extension named 'Some Network Specific Indicator' of type +-- BOOLEAN, with criticality 'ignore' and identified by global Object Identifier. +-- +-- Example of definition using the above information object class: +-- +-- SomeNetworkSpecificIndicator EXTENSION ::= { + +``` + +``` + +- EXTENSION-SYNTAX BOOLEAN +- CRITICALITY ignore +- IDENTIFIED BY global:{itu-t(0) identified-organization(4) organisation(0) gsm(1) +-- capextension(2)} +- } + +-- Example of transfer syntax, using the ExtensionField datatype as specified in clause 5. +-- Assuming the value of the extension is set to TRUE, the extensions parameter becomes +-- a Sequence of type {itu-t(0) identified-organization(4) organisation(0) gsm(1) +-- capextension(2)}, criticality ENUMERATED ::= ignore(0) and value [1] EXPLICIT BOOLEAN +-- ::= TRUE. +-- +-- Use of ITU-T Recommendation Q.1400 [52] defined Extension is for further study. +-- In addition the extension mechanism marker is used to identify the future minor additions +-- to CAP. + +firstExtension EXTENSION ::= { + EXTENSION-SYNTAX NULL + CRITICALITY ignore + IDENTIFIED BY global : {itu-t(0) identified-organization(4) organisation(0) gsm(1) + capextension(2)} +} +-- firstExtension is just an example. + +SupportedExtensions EXTENSION ::= {firstExtension, ... +-- full set of network operator extensions -- +} +-- SupportedExtension is the full set of the network operator extensions. + +PARAMETERS-BOUND ::= CLASS { + &minAccessPointNameLength INTEGER, + &maxAccessPointNameLength INTEGER, + &minACHBillingChargingLength INTEGER, + &maxACHBillingChargingLength INTEGER, + &minAttributesLength INTEGER, + &maxAttributesLength INTEGER, + &maxBearerCapabilityLength INTEGER, + &minCalledPartyBCDNumberLength INTEGER, + &maxCalledPartyBCDNumberLength INTEGER, + &minCalledPartyNumberLength INTEGER, + &maxCalledPartyNumberLength INTEGER, + &minCallingPartyNumberLength INTEGER, + &maxCallingPartyNumberLength INTEGER, + &minCallResultLength INTEGER, + &maxCallResultLength INTEGER, + &minCarrierLength INTEGER, + &maxCarrierLength INTEGER, + &minCauseLength INTEGER, + &maxCauseLength INTEGER, + &minDigitsLength INTEGER, + &maxDigitsLength INTEGER, + &minFCIBillingChargingDataLength INTEGER, + &maxFCIBillingChargingDataLength INTEGER, + &minFCIBillingChargingLength INTEGER, + &maxFCIBillingChargingLength INTEGER, + &minGenericNumberLength INTEGER, + &maxGenericNumberLength INTEGER, + &minGPRSCauseLength INTEGER, + &maxGPRSCauseLength INTEGER, + &minIPSSPCapabilitiesLength INTEGER, + &maxIPSSPCapabilitiesLength INTEGER, + &minLocationNumberLength INTEGER, + &maxLocationNumberLength INTEGER, + &minLowLayerCompatibilityLength INTEGER, + &maxLowLayerCompatibilityLength INTEGER, + &minMessageContentLength INTEGER, + &maxMessageContentLength INTEGER, + &minOriginalCalledPartyIDLength INTEGER, + &maxOriginalCalledPartyIDLength INTEGER, + &minPDPAddressLength INTEGER, + &maxPDPAddressLength INTEGER, + &minRedirectingPartyIDLength INTEGER, + &maxRedirectingPartyIDLength INTEGER, + &minScfIDLength INTEGER, + &maxScfIDLength INTEGER, + &minSCIBillingChargingLength INTEGER, +} + +``` + +``` + + &maxSCIBillingChargingLength INTEGER, + &minTimeAndTimezoneLength INTEGER, + &maxTimeAndTimezoneLength INTEGER, + &numOfBCSMEvents INTEGER, + &numOfChangeOfPositionControlInfo INTEGER, + &numOfCSSs INTEGER, + &numOfSMSEvents INTEGER, + &numOfGPRSEvents INTEGER, + &numOfExtensions INTEGER, + &numOfGenericNumbers INTEGER, + &numOfMessageIDs INTEGER} + +WITH SYNTAX { + MINIMUM-FOR-ACCESS-POINT-NAME &minAccessPointNameLength + MAXIMUM-FOR-ACCESS-POINT-NAME &maxAccessPointNameLength + MINIMUM-FOR-ACH-BILLING-CHARGING &minAchBillingChargingLength + MAXIMUM-FOR-ACH-BILLING-CHARGING &maxAchBillingChargingLength + MINIMUM-FOR-ATTRIBUTES &minAttributesLength + MAXIMUM-FOR-ATTRIBUTES &maxAttributesLength + MAXIMUM-FOR-BEARER-CAPABILITY &maxBearerCapabilityLength + MINIMUM-FOR-CALLED-PARTY-BCD-NUMBER &minCalledPartyBCDNumberLength + MAXIMUM-FOR-CALLED-PARTY-BCD-NUMBER &maxCalledPartyBCDNumberLength + MINIMUM-FOR-CALLED-PARTY-NUMBER &minCalledPartyNumberLength + MAXIMUM-FOR-CALLED-PARTY-NUMBER &maxCalledPartyNumberLength + MINIMUM-FOR-CALLING-PARTY-NUMBER &minCallingPartyNumberLength + MAXIMUM-FOR-CALLING-PARTY-NUMBER &maxCallingPartyNumberLength + MINIMUM-FOR-CALL-RESULT &minCallResultLength + MAXIMUM-FOR-CALL-RESULT &maxCallResultLength + MINIMUM-FOR-CARRIER &minCarrierLength + MAXIMUM-FOR-CARRIER &maxCarrierLength + MINIMUM-FOR-CAUSE &minCauseLength + MAXIMUM-FOR-CAUSE &maxCauseLength + MINIMUM-FOR-DIGITS &minDigitsLength + MAXIMUM-FOR-DIGITS &maxDigitsLength + MINIMUM-FOR-FCI-BILLING-CHARGING-DATA &minFCIBillingChargingDataLength + MAXIMUM-FOR-FCI-BILLING-CHARGING-DATA &maxFCIBillingChargingDataLength + MINIMUM-FOR-FCI-BILLING-CHARGING &minFCIBillingChargingLength + MAXIMUM-FOR-FCI-BILLING-CHARGING &maxFCIBillingChargingLength + MINIMUM-FOR-GENERIC-NUMBER &minGenericNumberLength + MAXIMUM-FOR-GENERIC-NUMBER &maxGenericNumberLength + MINIMUM-FOR-GPRS-CAUSE-LENGTH &minGPRSCauseLength + MAXIMUM-FOR-GPRS-CAUSE-LENGTH &maxGPRSCauseLength + MINIMUM-FOR-IP-SSP-CAPABILITIES &minIPSSPCapabilitiesLength + MAXIMUM-FOR-IP-SSP-CAPABILITIES &maxIPSSPCapabilitiesLength + MINIMUM-FOR-LOCATION-NUMBER &minLocationNumberLength + MAXIMUM-FOR-LOCATION-NUMBER &maxLocationNumberLength + MINIMUM-FOR-LOW-LAYER-COMPATIBILITY &minLowLayerCompatibilityLength + MAXIMUM-FOR-LOW-LAYER-COMPATIBILITY &maxLowLayerCompatibilityLength + MINIMUM-FOR-MESSAGE-CONTENT &minMessageContentLength + MAXIMUM-FOR-MESSAGE-CONTENT &maxMessageContentLength + MINIMUM-FOR-ORIGINAL-CALLED-PARTY-ID &minOriginalCalledPartyIDLength + MAXIMUM-FOR-ORIGINAL-CALLED-PARTY-ID &maxOriginalCalledPartyIDLength + MINIMUM-FOR-PDP-ADDRESS-LENGTH &minPDPAddressLength + MAXIMUM-FOR-PDP-ADDRESS-LENGTH &maxPDPAddressLength + MINIMUM-FOR-REDIRECTING-ID &minRedirectingPartyIDLength + MAXIMUM-FOR-REDIRECTING-ID &maxRedirectingPartyIDLength + MINIMUM-FOR-GSMSCF-ID &minScfIDLength + MAXIMUM-FOR-GSMSCF-ID &maxScfIDLength + MINIMUM-FOR-SCI-BILLING-CHARGING &minSCIBillingChargingLength + MAXIMUM-FOR-SCI-BILLING-CHARGING &maxSCIBillingChargingLength + MINIMUM-FOR-TIME-AND-TIMEZONE &minTimeAndTimezoneLength + MAXIMUM-FOR-TIME-AND-TIMEZONE &maxTimeAndTimezoneLength + NUM-OF-BCSM-EVENT &numOfBCSMEvents + NUM-OF-CHANGE-OF-POSITION-CONTROL-INFO &numOfChangeOfPositionControlInfo + NUM-OF-CSS &numOfCSSs + NUM-OF-SMS-EVENTS &numOfSMSEvents + NUM-OF-GPRS-EVENTS &numOfGPRSEvents + NUM-OF-EXTENSIONS &numOfExtensions + NUM-OF-GENERIC-NUMBERS &numOfGenericNumbers + NUM-OF-MESSAGE-IDS &numOfMessageIDs} + +cAPSpecificBoundSet PARAMETERS-BOUND ::= { + MINIMUM-FOR-ACCESS-POINT-NAME 1 + MAXIMUM-FOR-ACCESS-POINT-NAME 100 + MINIMUM-FOR-ACH-BILLING-CHARGING 5 + MAXIMUM-FOR-ACH-BILLING-CHARGING 177 + MINIMUM-FOR-ATTRIBUTES 2 +} + +``` + +``` + +MAXIMUM-FOR-ATTRIBUTES 10 +MAXIMUM-FOR-BEARER-CAPABILITY 11 +MINIMUM-FOR-CALLED-PARTY-BCD-NUMBER 1 +MAXIMUM-FOR-CALLED-PARTY-BCD-NUMBER 41 +MINIMUM-FOR-CALLED-PARTY-NUMBER 2 +MAXIMUM-FOR-CALLED-PARTY-NUMBER 18 +MINIMUM-FOR-CALLING-PARTY-NUMBER 2 +MAXIMUM-FOR-CALLING-PARTY-NUMBER 10 +MINIMUM-FOR-CALL-RESULT 12 +MAXIMUM-FOR-CALL-RESULT 193 +MINIMUM-FOR-CARRIER 4 +MAXIMUM-FOR-CARRIER 4 +MINIMUM-FOR-CAUSE 2 +MAXIMUM-FOR-CAUSE 32 +MINIMUM-FOR-DIGITS 2 +MAXIMUM-FOR-DIGITS 16 +MINIMUM-FOR-FCI-BILLING-CHARGING-DATA 1 +MAXIMUM-FOR-FCI-BILLING-CHARGING-DATA 160 +MINIMUM-FOR-FCI-BILLING-CHARGING 5 +MAXIMUM-FOR-FCI-BILLING-CHARGING 225 +MINIMUM-FOR-GENERIC-NUMBER 3 +MAXIMUM-FOR-GENERIC-NUMBER 11 +MINIMUM-FOR-GPRS-CAUSE-LENGTH 1 +MAXIMUM-FOR-GPRS-CAUSE-LENGTH 1 +MINIMUM-FOR-IP-SSP-CAPABILITIES 1 +MAXIMUM-FOR-IP-SSP-CAPABILITIES 4 +MINIMUM-FOR-LOCATION-NUMBER 2 +MAXIMUM-FOR-LOCATION-NUMBER 10 +MINIMUM-FOR-LOW-LAYER-COMPATIBILITY 1 +MAXIMUM-FOR-LOW-LAYER-COMPATIBILITY 16 +MINIMUM-FOR-MESSAGE-CONTENT 1 +MAXIMUM-FOR-MESSAGE-CONTENT 127 +MINIMUM-FOR-ORIGINAL-CALLED-PARTY-ID 2 +MAXIMUM-FOR-ORIGINAL-CALLED-PARTY-ID 10 +MINIMUM-FOR-PDP-ADDRESS-LENGTH 1 +MAXIMUM-FOR-PDP-ADDRESS-LENGTH 63 +MINIMUM-FOR-REDIRECTING-ID 2 +MAXIMUM-FOR-REDIRECTING-ID 10 +MINIMUM-FOR-GSMSCF-ID 2 +MAXIMUM-FOR-GSMSCF-ID 25 +-- maximum length of the ScfID shall be 10 unless the operator defined format +-- of the ScfID requires a higher maximum length +MINIMUM-FOR-SCI-BILLING-CHARGING 4 +MAXIMUM-FOR-SCI-BILLING-CHARGING 225 +MINIMUM-FOR-TIME-AND-TIMEZONE 8 +MAXIMUM-FOR-TIME-AND-TIMEZONE 8 +NUM-OF-BCSM-EVENT 30 +NUM-OF-CHANGE-OF-POSITION-CONTROL-INFO 10 +NUM-OF-CSS 127 +NUM-OF-SMS-EVENTS 10 +NUM-OF-GPRS-EVENTS 10 +NUM-OF-EXTENSIONS 10 +NUM-OF-GENERIC-NUMBERS 5 +NUM-OF-MESSAGE-IDS 16} + +``` + +END + +## 5.6 Object Identifiers (IDs) + +``` + +CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} + +``` + +``` + +DEFINITIONS ::= BEGIN + +``` + +``` + +-- This module assigns object identifiers for Modules, Packages, Contracts and ACs +-- used by CAP + +``` + +``` + +-- For Modules from TC, ROS, +tc-Messages OBJECT IDENTIFIER ::= +{itu-t recommendation q 773 modules(2) messages(1) version3(3)} + +``` + +``` + +tc-NotationExtensions OBJECT IDENTIFIER ::= +{itu-t recommendation q 775 modules(2) notation-extension (4) version1(1)} + +``` + +``` +ros-InformationObjects OBJECT IDENTIFIER ::= + {joint-iso-itu-t remote-operations(4) informationObjects(5) version1(0)} + +-- For CAP Modules +datatypes OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-datatypes(52) version8(7)} + +errortypes OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-errortypes(51) version8(7)} + +operationcodes OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-operationcodes(53) version8(7)} + +errorcodes OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-errorcodes(57) version8(7)} + +classes OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-classes(54) version8(7)} + +gsmSSF-gsmSCF-Operations OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-gsmSSF-gsmSCF-ops-args(101) version8(7)} +-- The Object Identifier 'gsmSSF-gsmSCF-Operations' is updated to version8(7) in Rel-6, so +-- other modules can IMPORT Rel-6 Operation definitions related to call control. + +gsmSSF-gsmSCF-Protocol OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-gsmSSF-gsmSCF-pkgs-contracts-ac(102) version8(7)} +-- The Object Identifier 'gsmSSF-gsmSCF-Protocol' is updated to version8(7) in Rel-6, so +-- other modules can IMPORT Rel-6 Protocol definitions related to call control. + +gsmSCF-gsmSRF-Operations OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-gsmSCF-gsmSRF-ops-args(103) version8(7)} +-- The Object Identifier 'gsmSCF-gsmSRF-Operations' is updated to version8(7) in Rel-6, so +-- other modules can IMPORT Rel-6 Operation definitions related to gsmSRF control. + +gsmSCF-gsmSRF-Protocol OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-gsmSCF-gsmSRF-pkgs-contracts-ac(104) version8(7)} +-- The Object Identifier 'gsmSCF-gsmSRF-Protocol' is updated to version8(7) in Rel-6, so +-- other modules can IMPORT Rel-6 Protocol definitions related to gsmSRF control. + +sms-Operations OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-SMS-ops-args(105) version8(7)} +-- The Object Identifier 'sms-Operations' is updated to version8(7) in Rel-6, so other +-- modules can IMPORT Rel-6 Operation definitions related to SMS control. + +smsSSF-gsmSCF-Protocol OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-smsSSF-gsmSCF-pkgs-contracts-ac(106) version8(7)} +-- The Object Identifier 'smsSSF-gsmSCF-Protocol' is updated to version8(7) in Rel-6, so +-- other modules can IMPORT Rel-6 Protocol definitions related to SMS control. + +gprsSSF-gsmSCF-Operations OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-GPRS-ops-args(107) version8(7)} +-- The Object Identifier 'gprsSSF-gsmSCF-Operations' is updated to version8(7) in Rel-6, so +-- other modules can IMPORT Rel-6 Operation definitions related to GPRS control. + +gprsSSF-gsmSCF-Protocol OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) + cap-gprsSSF-gsmSCF-pkgs-contracts-ac(108) version8(7)} +-- The Object Identifier 'gprsSSF-gsmSCF-Protocol' is updated to version8(7) in Rel-6, so +-- other modules can IMPORT Rel-6 Protocol definitions related to GPRS control. + +id-CAP OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) + umts-network(1) cap4(22)} +``` + +``` + +id-CAP3 OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) + umts-network(1) cap3(20)} + +id-CAPOE OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) + umts-network(1) cap4OE(23)} + +id-CAP3OE OBJECT IDENTIFIER ::= + {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) + umts-network(1) cap3OE(21)} + +id-ac OBJECT IDENTIFIER ::= {id-CAP ac(3)} +id-acE OBJECT IDENTIFIER ::= {id-CAPOE ac(3)} +id-ac3E OBJECT IDENTIFIER ::= {id-CAP3OEac(3)} +id-as OBJECT IDENTIFIER ::= {id-CAP as(5)} +id-asE OBJECT IDENTIFIER ::= {id-CAPOE as(5)} +id-rosObject OBJECT IDENTIFIER ::= {id-CAP rosObject(25)} +id-contract OBJECT IDENTIFIER ::= {id-CAP contract(26)} +id-contract3 OBJECT IDENTIFIER ::= {id-CAP3 contract(26)} +id-contractE OBJECT IDENTIFIER ::= {id-CAPOE contract(26)} +id-package OBJECT IDENTIFIER ::= {id-CAP package(27)} +id-packageE OBJECT IDENTIFIER ::= {id-CAPOE package(27)} + +-- for ac, as, rosObject, contract and package, the values are identical to ITU-T Recommendation +-- Q.1218 [49] + +-- ROS Objects + +id-rosObject-gsmSCF OBJECT IDENTIFIER ::= {id-rosObject 4} +id-rosObject-gsmSSF OBJECT IDENTIFIER ::= {id-rosObject 5} +id-rosObject-gsmSRF OBJECT IDENTIFIER ::= {id-rosObject 6} +id-rosObject-gprsSSF OBJECT IDENTIFIER ::= {id-rosObject 7} +id-rosObject-smsSSF-V3 OBJECT IDENTIFIER ::= {id-rosObject 8} +id-rosObject-smsSSF-V4 OBJECT IDENTIFIER ::= {id-rosObject 9} + +-- Application Contexts + +-- gsmSSF/gsmSCF AC +id-ac-CAP-gsmSSF-scfGenericAC OBJECT IDENTIFIER ::= {id-acE 4} +id-ac-CAP-gsmSSF-scfAssistHandoffAC OBJECT IDENTIFIER ::= {id-acE 6} +id-ac-CAP-scf-gsmSSFGenericAC OBJECT IDENTIFIER ::= {id-acE 8} + +-- gsmSRF/gsmSCF AC +id-ac-gsmSRF-gsmSCF OBJECT IDENTIFIER ::= {id-ac 14} + +-- gprsSSF/gsmSCF AC +id-ac-CAP-gprsSSF-gsmSCF-AC OBJECT IDENTIFIER ::= {id-ac3E 50} +id-ac-CAP-gsmSCF-gprsSSF-AC OBJECT IDENTIFIER ::= {id-ac3E 51} + +-- gprsSSF/gsmSCF or gsmSSF/gsmSCF AC +id-ac-cap3-sms-AC OBJECT IDENTIFIER ::= {id-ac3E 61} +id-ac-cap4-sms-AC OBJECT IDENTIFIER ::= {id-acE 61} + +-- Contracts + +-- gsmSSF/gsmSCF Contracts +id-CAPSSfToScfGeneric OBJECT IDENTIFIER ::= {id-contractE 3} +id-CAPAssistHandoffssfToScf OBJECT IDENTIFIER ::= {id-contractE 5} +id-CAPScfToSsfGeneric OBJECT IDENTIFIER ::= {id-contractE 6} + +-- gsmSRF/gsmSCF Contracts +id-contract-gsmSRF-gsmSCF OBJECT IDENTIFIER ::= {id-contract 13} + +-- gprsSSF/gsmSCF Contracts +id-capGprsSsfToGsmScf OBJECT IDENTIFIER ::= {id-contract 14} +id-capGsmScfToGprsSsf OBJECT IDENTIFIER ::= {id-contract 15} + +-- gprsSSF/gsmSCF or gsmSSF/gsmSCF Contracts +id-cap3SmsSsfToGsmScf OBJECT IDENTIFIER ::= {id-contract3 16} +id-cap4SmsSsfToGsmScf OBJECT IDENTIFIER ::= {id-contract 16} + +``` + +``` + +-- Operation Packages + +-- gsmSSF/gsmSCF Operation Packages +id-package-scfActivation OBJECT IDENTIFIER ::= {id-package 11} +id-package-gsmSRF-scfActivationOfAssist OBJECT IDENTIFIER ::= {id-package 15} +id-package-assistConnectionEstablishment OBJECT IDENTIFIER ::= {id-package 16} +id-package-genericDisconnectResource OBJECT IDENTIFIER ::= {id-package 17} +id-package-nonAssistedConnectionEstablishment OBJECT IDENTIFIER ::= {id-package 18} +id-package-connect OBJECT IDENTIFIER ::= {id-package 19} +id-package-callHandling OBJECT IDENTIFIER ::= {id-packageE 20} +id-package-bcsmEventHandling OBJECT IDENTIFIER ::= {id-package 21} +id-package-ssfCallProcessing OBJECT IDENTIFIER ::= {id-packageE 24} +id-package-scfCallInitiation OBJECT IDENTIFIER ::= {id-package 25} +id-package-timer OBJECT IDENTIFIER ::= {id-package 26} +id-package-billing OBJECT IDENTIFIER ::= {id-package 27} +id-package-charging OBJECT IDENTIFIER ::= {id-package 28} +id-package-trafficManagement OBJECT IDENTIFIER ::= {id-package 29} +id-package-callReport OBJECT IDENTIFIER ::= {id-package 32} +id-package-signallingControl OBJECT IDENTIFIER ::= {id-package 33} +id-package-activityTest OBJECT IDENTIFIER ::= {id-package 34} +id-package-cancel OBJECT IDENTIFIER ::= {id-packageE 36} +id-package-cphResponse OBJECT IDENTIFIER ::= {id-package 37} +id-package-exceptionInform OBJECT IDENTIFIER ::= {id-package 38} +id-package-playTone OBJECT IDENTIFIER ::= {id-package 39} + +-- gsmSRF/gsmSCF Operation Packages +id-package-specializedResourceControl OBJECT IDENTIFIER ::= {id-package 42} +id-package-gsmSRF-scfCancel OBJECT IDENTIFIER ::= {id-package 43} + +-- gprsSSF/gsmSCF Operation Packages +id-package-gprsContinue OBJECT IDENTIFIER ::= {id-package 49} +id-package-gprsExceptionInformation OBJECT IDENTIFIER ::= {id-package 50} +id-package-gprsScfActivation OBJECT IDENTIFIER ::= {id-package 51} +id-package-gprsConnect OBJECT IDENTIFIER ::= {id-package 52} +id-package-gprsRelease OBJECT IDENTIFIER ::= {id-package 53} +id-package-gprsEventHandling OBJECT IDENTIFIER ::= {id-package 54} +id-package-gprsTimer OBJECT IDENTIFIER ::= {id-package 55} +id-package-gprsBilling OBJECT IDENTIFIER ::= {id-package 56} +id-package-gprsCharging OBJECT IDENTIFIER ::= {id-package 57} +id-package-gprsActivityTest OBJECT IDENTIFIER ::= {id-package 58} +id-package-gprsCancel OBJECT IDENTIFIER ::= {id-package 59} +id-package-gprsChargeAdvice OBJECT IDENTIFIER ::= {id-package 60} + +-- gprsSSF/gsmSCF or gsmSSF/gsmSCF Operation Packages +id-package-smsActivation OBJECT IDENTIFIER ::= {id-package 61} +id-package-smsConnect OBJECT IDENTIFIER ::= {id-package 62} +id-package-smsContinue OBJECT IDENTIFIER ::= {id-package 63} +id-package-smsRelease OBJECT IDENTIFIER ::= {id-package 64} +id-package-smsEventHandling OBJECT IDENTIFIER ::= {id-package 65} +id-package-smsBilling OBJECT IDENTIFIER ::= {id-package 66} +id-package-smsTimer OBJECT IDENTIFIER ::= {id-package 67} + +-- Abstract Syntaxes + +-- gsmSSF/gsmSCF Abstract Syntaxes +id-as-gsmSSF-scfGenericAS OBJECT IDENTIFIER ::= {id-asE 4} +id-as-assistHandoff-gsmSSF-scfAS OBJECT IDENTIFIER ::= {id-asE 6} +id-as-scf-gsmSSFGenericAS OBJECT IDENTIFIER ::= {id-asE 7} + +-- gsmSRF/gsmSCF Abstract Syntaxes +id-as-basic-gsmSRF-gsmSCF OBJECT IDENTIFIER ::= {id-as 14} + +-- gprsSSF/gsmSCF Abstract Syntaxes +id-as-gprsSSF-gsmSCF-AS OBJECT IDENTIFIER ::= {id-as 50} +id-as-gsmSCF-gprsSSF-AS OBJECT IDENTIFIER ::= {id-as 51} + +-- gprsSSF/gsmSCF or gsmSSF/gsmSCF Abstract Syntaxes +id-as-smsSSF-gsmSCF-AS OBJECT IDENTIFIER ::= {id-as 61} + +END + +``` + +## 5.7 User Abort Data + +CAP-U-ABORT-Data {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) cap-u-abort-data(110) version8(7)} + +DEFINITIONS ::= BEGIN + +id-CAP-U-ABORT-Reason OBJECT IDENTIFIER ::= {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-Network(1) as(1) cap-u-abort-reason(2) version3(2)} + +cap-U-ABORT-Reason-Abstract-Syntax ABSTRACT-SYNTAX ::= {CAP-U-ABORT-REASON IDENTIFIED BY id-CAP-U-ABORT-Reason} + +CAP-U-ABORT-REASON ::= ENUMERATED { + +no-reason-given (1), + application-timer-expired (2), + not-allowed-procedures (3), + abnormal-processing (4), + congestion (5), + invalid-reference (6), + missing-reference (7), + overlapping-dialogue (8) +} + +-- application-timer-expired shall be set when application timer (e.g. Tssf) is expired. + -- not-allowed-procedures shall be set when received signal is not allowed in CAP procedures. + -- For example, when a class 4 operation is received from the gsmSCF and the operation is not allowed in gsmSSF FSM. (gsmSSF FSM cannot continue state transition). (e.g. ReleaseCall operation received in Waiting for End of Temporary Connection state.) + -- abnormal-processing shall be set when abnormal procedures occur at entity action. + -- congestion shall be set when requested resource is unavailable due to congestion at TC user (CAP) level. + -- invalid-reference shall be set if the received destinationReference is unknown or for a known destination Reference the received originationReference does not match with the stored originationReference. + -- This abort reason is used for CAP defined GPRS-ReferenceNumber. + -- missing-reference shall be set when the destinationReference or the originationReference is absent in the received message but is required to be present according to the procedures in subclause 14.1.7. + -- This abort reason is used for CAP defined GPRS-ReferenceNumber. + -- overlapping-dialogue shall be used by the gprsSSF to indicate to the gsmSCF that a specific instance already has a TC dialogue open. This error cause is typically obtained when both the gsmSCF and gprsSSF open a new dialogue at the same time. + -- no-reason-given shall be set when any other reasons above do not apply + END -- of CAP-U-ABORT-Data + +## 6 Circuit Switched Call Control + +### 6.1 gsmSSF/CCF - gsmSCF Interface + +#### 6.1.1 Operations and arguments + +cap-gsmSSF-gsmSCF-ops-args {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) cap-gsmSSF-gsmSCF-ops-args(101) version8(7)} + +DEFINITIONS IMPLICIT TAGS ::= BEGIN + +-- This module contains the operations and operation arguments used for the + -- gsmSSF - gsmSCF interface, for the control of circuit switched calls. + -- The table in subclause 2.1 lists the specifications that contain the modules + -- that are used by CAP. + +IMPORTS + +``` +errortypes, +datatypes, +operationcodes, +classes, +tc-Messages, +ros-InformationObjects +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} + +OPERATION +FROM Remote-Operations-Information-Objects ros-InformationObjects + +CallingPartysCategory, +HighLayerCompatibility, +LegID, +RedirectionInformation, +ServiceKey +FROM CS1-DataTypes {itu-t(0) identified-organization(4) etsi(0) inDomain(1) in-network(1) +modules(0) cs1-datatypes(2) version1(0)} + +MiscCallInfo +FROM CS2-datatypes {itu-t(0) identified-organization(4) etsi(0) inDomain(1) in-network(1) +cs2(20) modules(0) in-cs2-datatypes(0) version1(0)} + +Ext-BasicServiceCode, +IMEI, +IMSI, +ISDN-AddressString +FROM MAP-CommonDataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-CommonDataTypes(18) version12(12)} + +CUG-Index, +CUG-Interlock, +CUG-Info, +LocationInformation, +MS-Classmark2, +SubscriberState, +SupportedCamelPhases, +OfferedCamel4Functionalities +FROM MAP-MS-DataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-MS-DataTypes(11) version12(12)} + +CallReferenceNumber, +SuppressionOfAnnouncement, +UU-Data +FROM MAP-CH-DataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-CH-DataTypes(13) version12(12)} + +PARAMETERS-BOUND +FROM CAP-classes classes + +opcode-activityTest, +opcode-applyCharging, +opcode-applyChargingReport, +opcode-assistRequestInstructions, +opcode-callGap, +opcode-callInformationReport, +opcode-callInformationRequest, +opcode-cancel, +opcode-collectInformation, +opcode-connect, +opcode-connectToResource, +opcode-continue, +opcode-continueWithArgument, +opcode-disconnectForwardConnection, +opcode-dFCWithArgument, +opcode-disconnectLeg, +opcode-entityReleased, +opcode-establishTemporaryConnection, +opcode-eventReportBCSM, +opcode-furnishChargingInformation, +opcode-initialDP, +opcode-initiateCallAttempt, +opcode-moveLeg, +opcode-playTone, +opcode-releaseCall, +opcode-requestReportBCSMEVENT, +``` + +``` +opcode-resetTimer, +opcode-sendChargingInformation, +opcode-splitLeg +FROM CAP-operationcodes operationcodes +-- The CAP Operation identifiers for CAP V4 in Rel-6 are the same as the CAP Operation +-- identifiers for CAP V4 in Rel-5. + +AChBillingChargingCharacteristics {}, +AdditionalCallingPartyNumber {}, +AlertingPattern, +AChChargingAddress {}, +AssistingSSPIPRoutingAddress {}, +BCSMEVENT {}, +BCSM-Failure, +BearerCapability {}, +Burst, +CalledPartyNumber {}, +CalledPartyBCDNumber {}, +CallingPartyNumber {}, +CallResult {}, +CallSegmentID {}, +CallSegmentToCancel {}, +CallSegmentFailure {}, +Carrier, +Cause {}, +CGEncountered, +ChargeNumber {}, +ControlType, +CorrelationID {}, +DestinationRoutingAddress {}, +EventSpecificInformationBCSM {}, +EventTypeBCSM, +Extensions {}, +FCIBillingChargingCharacteristics {}, +GapCriteria {}, +GapIndicators, +GapTreatment, +GenericNumbers {}, +InvokeID, +IPRoutingAddress {}, +IPSSPCapabilities {}, +leg1, +leg2, +LegOrCallSegment {}, +LocationNumber {}, +LowLayerCompatibility {}, +MonitorMode, +NAOLiInfo, +OCSIApplicable, +OriginalCalledPartyID {}, +ReceivingSideID, +RedirectingPartyID {}, +RequestedInformationList {}, +RequestedInformationTypeList, +ScfID {}, +SCIBillingChargingCharacteristics {}, +SendingSideID, +ServiceInteractionIndicatorsTwo, +TimeAndTimezone {}, +TimerID, +TimerValue +FROM CAP-datatypes datatypes +-- For Rel-6, the CAP-datatypes module is updated to version8(7); Object Identifier 'datatypes' +-- is also updated to version8(7). As a result, the present module uses Rel-6 data type definitions. + +cancelFailed, +eTCFailed, +missingCustomerRecord, +missingParameter, +parameterOutOfRange, +requestedInfoError, +systemFailure, +taskRefused, +unexpectedComponentSequence, +unexpectedDataValue, +unexpectedParameter, +unknownLegID, +unknownCSID +``` + +``` + +FROM CAP-errortypes errortypes +-- For Rel-6, the CAP-errortypes module is updated to version8(7); Object Identifier +-- 'errortypes' is also updated to version8(7). As a result, the present module uses Rel-6 +-- error type definitions. + +; + +activityTest OPERATION ::= { + RETURN RESULT TRUE + CODE opcode-activityTest} +-- Direction: gsmSCF -> gsmSSF, Timer: Tat +-- This operation is used to check for the continued existence of a relationship +-- between the gsmSCF and gsmSSF, assist gsmSSF or gsmSRF. If the relationship is +-- still in existence, then the gsmSSF will respond. If no reply is received, +-- then the gsmSCF will assume that the gsmSSF, assist gsmSSF or gsmSRF has failed +-- in some way. + +applyCharging {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT ApplyChargingArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + unexpectedComponentSequence | + unexpectedParameter | + unexpectedDataValue | + parameterOutOfRange | + systemFailure | + taskRefused | + unknownLegID | + unknownCSID} + CODE opcode-applyCharging} +-- Direction: gsmSCF -> gsmSSF, Timer: Tac +-- This operation is used for interacting from the gsmSCF with the gsmSSF charging mechanisms. +-- The ApplyChargingReport operation provides the feedback from the gsmSSF to the gsmSCF. + +ApplyChargingArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + aChBillingChargingCharacteristics [0] AChBillingChargingCharacteristics {bound}, + partyToCharge [2] SendingSideID DEFAULT sendingSideID : leg1, + extensions [3] Extensions {bound} OPTIONAL, + aChChargingAddress [50] AChChargingAddress {bound} + DEFAULT legID:sendingSideID:leg1, + ... +} + +-- The partyToCharge parameter indicates the party in the call to which the ApplyCharging operation +-- shall be applied. + +applyChargingReport {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT ApplyChargingReportArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + unexpectedComponentSequence | + unexpectedParameter | + unexpectedDataValue | + unknownCSID | + unknownLegID | + parameterOutOfRange | + systemFailure | + taskRefused} + CODE opcode-applyChargingReport} +-- Direction: gsmSSF -> gsmSCF, Timer: Tacr +-- This operation is used by the gsmSSF to report to the gsmSCF the occurrence of a +-- specific charging event as requested by the gsmSCF using the ApplyCharging operation. + +ApplyChargingReportArg {PARAMETERS-BOUND : bound} ::= CallResult {bound} + +assistRequestInstructions {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT AssistRequestInstructionsArg {bound} + RETURN RESULT FALSE + ERRORS {missingCustomerRecord | + missingParameter | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter} + CODE opcode-assistRequestInstructions} +-- Direction: gsmSSF -> gsmSCF or gsmSRF -> gsmSCF, Timer: Tari + +``` + +``` + +-- This operation is used when there is an assist procedure and may be +-- sent by the gsmSSF or gsmSRF to the gsmSCF. This operation is sent by the +-- assisting gsmSSF to gsmSCF, when the initiating gsmSSF has set up a connection to +-- the gsmSRF or to the assisting gsmSSF as a result of receiving an +-- EstablishTemporaryConnection from +-- the gsmSCF. +-- Refer to clause 11 for a description of the procedures associated with this operation. + +AssistRequestInstructionsArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + correlationID [0] CorrelationID {bound}, + iPSSPCapabilities [2] IPSSPCapabilities {bound}, + extensions [3] Extensions {bound} OPTIONAL, + ... +} + +-- OPTIONAL denotes network operator specific use. The value of the correlationID may be the +-- Called Party Number supplied by the initiating gsmSSF. + +callGap {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT CallGapArg {bound} + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE opcode-callGap} +-- Direction: gsmSCF -> gsmSSF, Timer: Tcg +-- This operation is used to request the gsmSSF to reduce the rate at which specific service +-- requests are sent to the gsmSCF. + +CallGapArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + gapCriteria [0] GapCriteria {bound}, + gapIndicators [1] GapIndicators, + controlType [2] ControlType OPTIONAL, + gapTreatment [3] GapTreatment {bound} OPTIONAL, + extensions [4] Extensions {bound} OPTIONAL, + ... +} + +-- OPTIONAL denotes network operator optional. If gapTreatment is not present, then the gsmSSF will +-- use a default treatment depending on network operator implementation. + +callInformationReport {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT CallInformationReportArg {bound} + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE opcode-callInformationReport} +-- Direction: gsmSSF -> gsmSCF, Timer: Tcirp +-- This operation is used to send specific call information for a single call party to the gsmSCF as +-- requested by the gsmSCF in a previous CallInformationRequest. + +CallInformationReportArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + requestedInformationList [0] RequestedInformationList {bound}, + extensions [2] Extensions {bound} OPTIONAL, + legID [3] ReceivingSideID DEFAULT receivingSideID:leg2, + ... +} + +callInformationRequest {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT CallInformationRequestArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + requestedInfoError | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownLegID} + CODE opcode-callInformationRequest} +-- Direction: gsmSCF -> gsmSSF, Timer: Tcirq +-- This operation is used to request the gsmSSF to record specific information about a single +-- call party and report it to the gsmSCF (with a CallInformationReport operation). + +CallInformationRequestArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + requestedInformationTypeList [0] RequestedInformationTypeList, + extensions [2] Extensions {bound} OPTIONAL, + legID [3] SendingSideID DEFAULT sendingSideID:leg2, + ... +} + +-- OPTIONAL denotes network operator optional. + +``` + +``` + +cancel {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT CancelArg {bound} + RETURN RESULT FALSE + ERRORS {cancelFailed | + missingParameter | + taskRefused | + unknownCSID} + CODE opcode-cancel} +-- Direction: gsmSCF -> gsmSSF, or gsmSCF -> gsmSRF, Timer: Tcan +-- This operation cancels the correlated previous operation or all previous requests. The following +-- operations can be canceled: PlayAnnouncement, PromptAndCollectUserInformation. + +CancelArg {PARAMETERS-BOUND : bound} ::= CHOICE { + invokeID [0] InvokeID, + allRequests [1] NULL, + callSegmentToCancel [2] CallSegmentToCancel {bound} +} +-- The InvokeID has the same value as that which was used for the operation to be cancelled. + +collectInformation {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT CollectInformationArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + SystemFailure | + TaskRefused | + UnexpectedComponentSequence | + UnexpectedDataValue | + UnexpectedParameter} + CODE opcode-collectInformation} +-- Direction: gsmSCF-> gsmSSF, Timer: Tci +-- This operation is used to request the gsmSSF to perform the call +-- processing actions to prompt a calling party for additional digits. + +CollectInformationArg {PARAMETERS-BOUND : bound} ::= SEQUENCE{ + extensions [0] Extensions {bound} OPTIONAL, + ... +} + +connect {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT ConnectArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownLegID} + CODE opcode-connect} +-- Direction: gsmSCF-> gsmSSF, Timer: Tcon +-- This operation is used to request the gsmSSF to perform the call processing actions +-- to route or forward a call to a specified destination. + +ConnectArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + destinationRoutingAddress [0] DestinationRoutingAddress {bound}, + alertingPattern [1] AlertingPattern OPTIONAL, + originalCalledPartyID [6] OriginalCalledPartyID {bound} OPTIONAL, + extensions [10] Extensions {bound} OPTIONAL, + carrier [11] Carrier {bound} OPTIONAL, + callingPartysCategory [28] CallingPartysCategory OPTIONAL, + redirectingPartyID [29] RedirectingPartyID {bound} OPTIONAL, + redirectionInformation [30] RedirectionInformation OPTIONAL, + genericNumbers [14] GenericNumbers {bound} OPTIONAL, + serviceInteractionIndicatorsTwo [15] ServiceInteractionIndicatorsTwo OPTIONAL, + chargeNumber [19] ChargeNumber {bound} OPTIONAL, + legToBeConnected [21] LegID OPTIONAL, + cug-Interlock [31] CUG-Interlock OPTIONAL, + cug-OutgoingAccess [32] NULL OPTIONAL, + suppressionOfAnnouncement [55] SuppressionOfAnnouncement OPTIONAL, + oCSIApplicable [56] OCSIApplicable OPTIONAL, + naOliInfo [57] NAOLIInfo OPTIONAL, + bor-InterrogationRequested [58] NULL OPTIONAL, + ... / + suppress-N-CSI [59] NULL OPTIONAL +} +-- na-Info is included at the discretion of the gsmSCF operator. + +``` + +``` + +connectToResource {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT ConnectToResourceArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownCSID} + CODE opcode-connectToResource} +-- Direction: gsmSCF -> gsmSSF, Timer: Tctr +-- This operation is used to connect a call segment from the gsmSSF to the +-- gsmSRF. + +ConnectToResourceArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + resourceAddress CHOICE { + ipRoutingAddress [0] IPRoutingAddress {bound}, + none [3] NULL + }, + extensions [4] Extensions {bound} OPTIONAL, + serviceInteractionIndicatorsTwo [7] ServiceInteractionIndicatorsTwo OPTIONAL, + callSegmentID [50] CallSegmentID {bound} OPTIONAL, + ... +} + +continue OPERATION ::= { + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE opcode-continue} +-- Direction: gsmSCF -> gsmSSF, Timer: Tcue +-- This operation is used to request the gsmSSF to proceed with call processing at the +-- DP at which it previously suspended call processing to await gsmSCF instructions +-- (i.e. proceed to the next point in call in the BCSM). The gsmSSF continues call +-- processing without substituting new data from gsmSCF. + +continueWithArgument {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT ContinueWithArgumentArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownLegID | + unknownCSID} + CODE opcode-continueWithArgument} +-- Direction: gsmSCF -> gsmSSF, Timer: Tcwa +-- This operation is used to request the gsmSSF to proceed with call processing at the +-- DP at which it previously suspended call processing to await gsmSCF instructions +-- (i.e. proceed to the next point in call in the BCSM). The gsmSSF continues call +-- processing with the modified call setup information as received from the gsmSCF. + +ContinueWithArgumentArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + alertingPattern [1] AlertingPattern OPTIONAL, + extensions [6] Extensions {bound} OPTIONAL, + serviceInteractionIndicatorsTwo [7] ServiceInteractionIndicatorsTwo OPTIONAL, + callingPartysCategory [12] CallingPartysCategory OPTIONAL, + genericNumbers [16] GenericNumbers {bound} OPTIONAL, + cug-Interlock [17] CUG-Interlock OPTIONAL, + cug-OutgoingAccess [18] NULL OPTIONAL, + chargeNumber [50] ChargeNumber {bound} OPTIONAL, + carrier [52] Carrier {bound} OPTIONAL, + suppressionOfAnnouncement [55] SuppressionOfAnnouncement OPTIONAL, + naOliInfo [56] NAOLIInfo OPTIONAL, + bor-InterrogationRequested [57] NULL OPTIONAL, + suppress-O-CSI [58] NULL OPTIONAL, + continueWithArgumentArgExtension [59] ContinueWithArgumentArgExtension {bound} OPTIONAL, + ... +} + +ContinueWithArgumentArgExtension {PARAMETERS-BOUND : bound} ::= SEQUENCE { + suppress-D-CSI [0] NULL OPTIONAL, + suppress-N-CSI [1] NULL OPTIONAL, + suppressOutgoingCallBarring [2] NULL OPTIONAL, + legOrCallSegment [3] LegOrCallSegment {bound} OPTIONAL, + ... +} + +``` + +``` + + } + + disconnectForwardConnection OPERATION ::= { + RETURN RESULT FALSE + ERRORS {systemFailure | + taskRefused | + unexpectedComponentSequence} + CODE opcode-disconnectForwardConnection} + -- Direction: gsmSCF -> gsmSSF, Timer: Tdfc + -- This operation is used to disconnect a forward temporary connection or a connection to a + -- resource. Refer to clause 11 for a description of the procedures associated with this operation. + + disconnectForwardConnectionWithArgument {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT DisconnectForwardConnectionWithArgumentArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownCSID} + CODE opcode-dFCWithArgument} + -- Direction gsmSCF -> gsmSSF, Timer Tdfcwa + -- This operation is used to disconnect a forward temporary connection or a connection to a + -- resource. Refer to clause 11 for a description of the procedures associated with this operation. + + DisconnectForwardConnectionWithArgumentArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + callSegmentID [1] CallSegmentID {bound} OPTIONAL, + extensions [2] Extensions {bound} OPTIONAL, + ... + } + + disconnectLeg {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT DisconnectLegArg {bound} + RETURN RESULT TRUE + ERRORS {missingParameter | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownLegID} + CODE opcode-disconnectLeg} + -- Direction: gsmSCF -> gsmSSF, Timer Tdl + -- This operation is used by the gsmSCF to release a specific leg associated with the call and + -- retain any other legs not specified in the DisconnectLeg. Refer to clause 11 for a description + -- of the procedures associated with this operation. + + DisconnectLegArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + legToBeReleased [0] LegID, + releaseCause [1] Cause {bound} OPTIONAL, + extensions [2] Extensions {bound} OPTIONAL, + ... + } + + entityReleased {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT EntityReleasedArg {bound} + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE opcode-entityReleased} + -- Direction: gsmSSF -> gsmSCF, Timer: Ter + -- This operation is used by the gsmSSF to inform the gsmSCF of an error or exception + + EntityReleasedArg {PARAMETERS-BOUND : bound} ::= CHOICE { + callSegmentFailure [0] CallSegmentFailure {bound}, + bCSM-Failure [1] BCSM-Failure {bound} + } + + establishTemporaryConnection {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT EstablishTemporaryConnectionArg {bound} + RETURN RESULT FALSE + ERRORS {eTCFailed | + missingParameter | + systemFailure | + taskRefused | + unexpectedComponentSequence | + +``` + +``` + + unexpectedDataValue | + unexpectedParameter | + unknownCSID} + CODE + opcode-establishTemporaryConnection} +-- Direction: gsmSCF -> gsmSSF, Timer: Tetc +-- This operation is used to create a connection to a resource for a limited period +-- of time (e.g. to play an announcement, to collect user information); it implies +-- the use of the assist procedure. Refer to clause 11 for a description of the +-- procedures associated with this operation. + +EstablishTemporaryConnectionArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + assistingSSPIRoutingAddress [0] AssistingSSPIRoutingAddress {bound}, + correlationID [1] CorrelationID {bound} OPTIONAL, + scfID [3] ScfID {bound} OPTIONAL, + extensions [4] Extensions {bound} OPTIONAL, + carrier [5] Carrier {bound} OPTIONAL, + serviceInteractionIndicatorsTwo [6] ServiceInteractionIndicatorsTwo OPTIONAL, + callSegmentID [7] CallSegmentID {bound} OPTIONAL, + naOliInfo [50] NAOLiInfo OPTIONAL, + chargeNumber [51] ChargeNumber {bound} OPTIONAL, + ... + originalCalledPartyID [52] OriginalCalledPartyID {bound} OPTIONAL, + callingPartyNumber [53] CallingPartyNumber {bound} OPTIONAL +} + +eventReportBCSM {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT EventReportBCSMArg {bound} + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE + opcode-eventReportBCSM} +-- Direction: gsmSSF -> gsmSCF, Timer: Terb +-- This operation is used to notify the gsmSCF of a call-related event (e.g. BCSM +-- events such as O_Busy or O_No_Answer) previously requested by the gsmSCF in a +-- RequestReportBCSMEVENT operation. + +EventReportBCSMArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + eventTypeBCSM [0] EventTypeBCSM, + eventSpecificInformationBCSM [2] EventSpecificInformationBCSM {bound} OPTIONAL, + legID [3] ReceivingSideID OPTIONAL, + miscCallInfo [4] MiscCallInfo DEFAULT {messageType request}, + extensions [5] Extensions {bound} OPTIONAL, + ... +} + +furnishChargingInformation {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT FurnishChargingInformationArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownLegID} + CODE + opcode-furnishChargingInformation} +-- Direction: gsmSCF -> gsmSSF, Timer: Tfci +-- This operation is used to request the gsmSSF to generate, register a call record +-- or to include some information in the default call record. +-- The registered call record is intended for off line charging of the call. + +FurnishChargingInformationArg {PARAMETERS-BOUND : bound} ::= + FCIBillingChargingCharacteristics{bound} + +initialDP {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT InitialDPArg {bound} + RETURN RESULT FALSE + ERRORS {missingCustomerRecord | + missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter} + CODE + opcode-initialDP} +-- Direction: gsmSSF -> gsmSCF, Timer: Tidp +-- This operation is used after a TDP to indicate request for service. + +``` + +``` + +InitialDPArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + serviceKey [0] ServiceKey , + calledPartyNumber [2] CalledPartyNumber {bound} OPTIONAL, + callingPartyNumber [3] CallingPartyNumber {bound} OPTIONAL, + callingPartysCategory [5] CallingPartysCategory OPTIONAL, + cGEncountered [7] CGEncountered OPTIONAL, + iPSSPCapabilities [8] IPSSPCapabilities {bound} OPTIONAL, + locationNumber [10] LocationNumber {bound} OPTIONAL, + originalCalledPartyID [12] OriginalCalledPartyID {bound} OPTIONAL, + extensions [15] Extensions {bound} OPTIONAL, + highLayerCompatibility [23] HighLayerCompatibility OPTIONAL, + additionalCallingPartyNumber [25] AdditionalCallingPartyNumber {bound} OPTIONAL, + bearerCapability [27] BearerCapability {bound} OPTIONAL, + eventTypeBCSM [28] EventTypeBCSM OPTIONAL, + redirectingPartyID [29] RedirectingPartyID {bound} OPTIONAL, + redirectionInformation [30] RedirectionInformation OPTIONAL, + cause [17] Cause {bound} OPTIONAL, + serviceInteractionIndicatorsTwo [32] ServiceInteractionIndicatorsTwo OPTIONAL, + carrier [37] Carrier {bound} OPTIONAL, + cug-Index [45] CUG-Index OPTIONAL, + cug-Interlock [46] CUG-Interlock OPTIONAL, + cug-OutgoingAccess [47] NULL OPTIONAL, + IMSI [50] IMSI OPTIONAL, + subscriberState [51] SubscriberState OPTIONAL, + locationInformation [52] LocationInformation OPTIONAL, + ext-basicServiceCode [53] Ext-BasicServiceCode OPTIONAL, + callReferenceNumber [54] CallReferenceNumber OPTIONAL, + mscAddress [55] ISDN-AddressString OPTIONAL, + calledPartyBCDNumber [56] CalledPartyBCDNumber {bound} OPTIONAL, + timeAndTimezone [57] TimeAndTimezone {bound} OPTIONAL, + callForwardingSS-Pending [58] NULL OPTIONAL, + initialDPArgExtension [59] InitialDPArgExtension {bound} OPTIONAL, + ... +} + +InitialDPArgExtension {PARAMETERS-BOUND : bound} ::= SEQUENCE { + gmscAddress [0] ISDN-AddressString OPTIONAL, + forwardingDestinationNumber [1] CalledPartyNumber {bound} OPTIONAL, + ms-Classmark2 [2] MS-Classmark2 OPTIONAL, + iMEI [3] IMEI OPTIONAL, + supportedCamelPhases [4] SupportedCamelPhases OPTIONAL, + offeredCamel4Functionalities [5] OfferedCamel4Functionalities OPTIONAL, + bearerCapability2 [6] BearerCapability {bound} OPTIONAL, + ext-basicServiceCode2 [7] Ext-BasicServiceCode OPTIONAL, + highLayerCompatibility2 [8] HighLayerCompatibility OPTIONAL, + lowLayerCompatibility [9] LowLayerCompatibility {bound} OPTIONAL, + lowLayerCompatibility2 [10] LowLayerCompatibility {bound} OPTIONAL, + .... + enhancedDialledServicesAllowed [11] NULL OPTIONAL, + uu-Data [12] UU-Data OPTIONAL, + collectInformationAllowed [13] NULL OPTIONAL, + releaseCallArgExtensionAllowed [14] NULL OPTIONAL +} + +-- If iPSSPCapabilities is not present then this denotes that a colocated gsmSRF is not +-- supported by the gsmSSF. If present, then the gsmSSF supports a colocated gsmSRF capable +-- of playing announcements via elementaryMessageIDs and variableMessages, the playing of +-- tones and the collection of DTMF digits. Other supported capabilities are explicitly +-- detailed in the IPSSPCapabilities parameter itself. +-- Carrier is included at the discretion of the gsmSSF operator. +-- The UserCSGInformation is conveyed in the LocationInformation. The encoding of the parameter is +-- as defined in 3GPP TS 29.002 [11]. + +initiateCallAttempt {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT InitiateCallAttemptArg {bound} + RESULT InitiateCallAttemptRes {bound} + ERRORS {missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter + } + CODE opcode-initiateCallAttempt} +-- Direction: gsmSCF -> gsmSSF, Timer T_ica +-- This operation is used to instruct the gsmSSF to create a new call to a call party using the +-- address information provided by the gsmSCF. + +``` + +``` + +InitiateCallAttemptArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + destinationRoutingAddress [0] DestinationRoutingAddress {bound}, + extensions [4] Extensions {bound} OPTIONAL, + legToBeCreated [5] LegID OPTIONAL, + newCallSegment [6] CallSegmentID {bound} OPTIONAL, + callingPartyNumber [30] CallingPartyNumber {bound} OPTIONAL, + callReferenceNumber [51] CallReferenceNumber OPTIONAL, + gsmSCFAddress [52] ISDN-AddressString OPTIONAL, + suppress-T-CSI [53] NULL OPTIONAL, + ... +} + +InitiateCallAttemptRes {PARAMETERS-BOUND : bound} ::= SEQUENCE { + supportedCamelPhases [0] SupportedCamelPhases OPTIONAL, + offeredCamel4Functionalities [1] OfferedCamel4Functionalities OPTIONAL, + extensions [2] Extensions {bound} OPTIONAL, + ..., + releaseCallArgExtensionAllowed [3] NULL OPTIONAL +} + +moveLeg {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT MoveLegArg {bound} + RETURN RESULT TRUE + ERRORS {missingParameter | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownLegID} + CODE opcode-moveLeg +-- Direction: gsmSCF -> gsmSSF, Timer: Tml +-- This operation is used by the gsmSCF to move a leg from one call segment to another call segment +-- within the same call segment association. + +MoveLegArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + legIDToMove [0] LegID, + extensions [2] Extensions {bound} OPTIONAL, + ... +} + +playTone {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT PlayToneArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + systemFailure | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownLegID | + unknownCSID} + CODE opcode-playTone +-- Direction: gsmSCF -> gsmSSF, Timer: Tpt +-- This operation is used to play tones to either a leg or a call segment using +-- the MSC's tone generator. + +PlayToneArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + legOrCallSegment [0] LegOrCallSegment {bound}, + bursts [1] Burst, + extensions [2] Extensions {bound} OPTIONAL, + ... +} + +releaseCall {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT ReleaseCallArg {bound} + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE opcode-releaseCall +-- Direction: gsmSCF -> gsmSSF, Timer: Trc +-- This operation is used to tear down an existing call at any phase of the call for all parties +-- involved in the call. + +ReleaseCallArg {PARAMETERS-BOUND : bound} ::= CHOICE { + allCallSegments AllCallSegments, + allCallSegmentsWithExtension [2] AllCallSegmentsWithExtension +} + +``` + +``` + + } + +AllCallSegments ::= Cause {bound} +-- A default value of decimal 31 (normal unspecified) shall be given. + +AllCallSegmentsWithExtension ::= SEQUENCE { + allCallSegments [0] AllCallSegments, + extensions [1] Extensions {bound} OPTIONAL +} + +requestReportBCSMEvent {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT RequestReportBCSMEventArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownLegID} + CODE opcode-requestReportBCSMEvent} +-- Direction: gsmSCF -> gsmSSF, Timer: Trrb +-- This operation is used to request the gsmSSF to monitor for a call-related event +-- (e.g. BCSM events such as O_Busy or O_No_Answer) and to send a notification +-- to the gsmSCF when the event is detected. +-- +-- NOTE: +-- Every EDP must be explicitly armed by the gsmSCF via a RequestReportBCSMEvent operation. +-- No implicit arming of EDPs at the gsmSSF after reception of any operation (different +-- from RequestReportBCSMEvent) from the gsmSCF is allowed. + +RequestReportBCSMEventArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + bcsmEvents [0] SEQUENCE SIZE(1..bound.&numOfBCSMEvents) OF + BCSMEvent {bound}, + extensions [2] Extensions {bound} OPTIONAL, + ... +} +-- Indicates the BCSM related events for notification. + +resetTimer {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT ResetTimerArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownCSID} + CODE opcode-resetTimer} +-- Direction: gsmSCF -> gsmSSF, Timer: Ttr +-- This operation is used to request the gsmSSF to refresh an application timer in the gsmSSF. + +ResetTimerArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + timerID [0] TimerID DEFAULT tssf, + timerValue [1] TimerValue, + extensions [2] Extensions {bound} OPTIONAL, + callSegmentID [3] CallSegmentID {bound} OPTIONAL, + ... +} + +sendChargingInformation {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT SendChargingInformationArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + unexpectedComponentSequence | + unexpectedParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedDataValue | + unknownLegID} + CODE opcode-sendChargingInformation} +-- Direction: gsmSCF -> gsmSSF, Timer: Tsci +-- This operation is used to instruct the gsmSSF on the charging information to send by the gsmSSF. +-- The charging information can either be sent back by means of signalling or internal +-- if the gsmSSF is located in the local exchange. In the local exchange + +``` + +-- this information may be used to update the charge meter or to create a standard call record. + +``` +SendChargingInformationArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + SCIBillingChargingCharacteristics [0] SCIBillingChargingCharacteristics {bound}, + partyToCharge [1] SendingSideID, + extensions [2] Extensions {bound} OPTIONAL, + ... +} +``` + +``` +splitLeg {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT SplitLegArg {bound} + RETURN RESULT TRUE + ERRORS {missingParameter | + unexpectedComponentSequence | + unexpectedParameter | + unexpectedDataValue | + systemFailure | + taskRefused | + unknownLegID} + CODE opcode-splitLeg} +``` + +-- Direction: gsmSCF -> gsmSSF, Timer Tsl + +-- This operation is used by the gsmSCF to separate a leg from its source call segment and +-- place it in a new call segment within the same call segment association. + +``` +SplitLegArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + legToBeSplit [0] LegID, + newCallSegment [1] CallSegmentID {bound} OPTIONAL, + extensions [2] Extensions {bound} OPTIONAL, + ... +} +``` + +END + +The following value ranges apply for operation specific timers in CAP: + +| | | +|---------|------------------| +| short: | 1 s - 10 s | +| medium: | 1 s - 60 s | +| long: | 1 s - 30 minutes | + +Table 6-1 lists all operation timers and the value range for each timer. The definitive value for each operation timer may be network specific and has to be defined by the network operator. + +**Table 6-1: Timer value ranges** + +| Operation Name | Timer | value range | +|-----------------------------------------|--------------------|-------------| +| ActivityTest | T at | Short | +| ApplyCharging | T ac | Short | +| ApplyChargingReport | T acr | Short | +| AssistRequestInstructions | T ari | Short | +| CollectInformation | T ci | Short | +| CallInformationReport | T cirp | Short | +| CallInformationRequest | T cirq | Short | +| Cancel | T can | Short | +| CallGap | T cg | Short | +| Connect | T con | Short | +| ConnectToResource | T ctr | Short | +| Continue | T cue | Short | +| ContinueWithArgument | T cwa | Short | +| DisconnectForwardConnectionWithArgument | T dfcwa | Short | +| DisconnectLeg | T dl | Short | +| EntityReleased | T er | Short | +| DisconnectForwardConnection | T dfc | Short | +| EstablishTemporaryConnection | T etc | Medium | +| EventReportBCSM | T erb | Short | +| FurnishChargingInformation | T fci | Short | +| InitialDP | T idp | Short | +| InitiateCallAttempt | T ica | Short | +| MoveLeg | T ml | Short | +| PlayTone | T pt | Short | +| ReleaseCall | T rc | Short | +| RequestReportBCSMEVENT | T rrb | Short | +| ResetTimer | T rt | Short | +| SendChargingInformation | T sci | Short | +| SplitLeg | T sl | Short | + +## 6.1.2 gsmSSF/gsmSCF packages, contracts and ACs + +### 6.1.2.1 gsmSSF/gsmSCF ASN.1 module + +``` +CAP-gsmSSF-gsmSCF-pkgs-contracts-ac { itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-gsmSSF-gsmSCF-pkgs-contracts-ac(102) version8(7) } +``` + +``` +DEFINITIONS ::= BEGIN +``` + +``` +-- This module specifies the Operation Packages, Contracts, Application Contexts +-- and Abstract Syntaxes used for the gsmSSF - gsmSCF interface, for the control of +-- circuit switched calls. +``` + +``` +-- The table in subclause 2.1 lists the specifications that contain the modules +-- that are used by CAP. +``` + +``` +IMPORTS +``` + +``` + PARAMETERS-BOUND, + cAPSpecificBoundSet +FROM CAP-classes classes +-- Elements that exist in cAPSpecificBoundSet in Rel-5 are not changed in Rel-6. As a +-- result, the value range of data type definitions in Rel-5 are not changed in Rel-6. +``` + +``` +CONTRACT, +``` + +``` + + OPERATION-PACKAGE, + OPERATION +FROM Remote-Operations-Information-Objects ros-InformationObjects + + TCMessage {} +FROM TCAPMessages tc-Messages + + APPLICATION-CONTEXT, + dialogue-abstract-syntax +FROM TC-Notation-Extensions tc-NotationExtensions + + activityTest, + applyCharging {}, + applyChargingReport {}, + assistRequestInstructions {}, + callGap {}, + callInformationReport {}, + callInformationRequest {}, + cancel {}, + collectInformation {}, + connect {}, + connectToResource {}, + continue, + continueWithArgument {}, + disconnectForwardConnection, + disconnectForwardConnectionWithArgument {}, + disconnectLeg {}, + entityReleased {}, + establishTemporaryConnection {}, + eventReportBCSM {}, + furnishChargingInformation {}, + initialDP {}, + initiateCallAttempt {}, + moveLeg {}, + playTone {}, + releaseCall {}, + requestReportBCSMEVENT {}, + resetTimer {}, + sendChargingInformation {}, + splitLeg {} +FROM CAP-gsmSSF-gsmSCF-ops-args gsmSSF-gsmSCF-Operations +-- Object Identifier 'gsmSSF-gsmSCF-Operations' is updated to version8(7) in Rel-6. As +-- a result, the present module, 'CAP-gsmSSF-gsmSCF-pkgs-contracts-ac', IMPORTS CAP +-- Operation definitions from CAP-gsmSSF-gsmSCF-ops-args version8(7). Operation +-- definitions are used in the ABSTRACT SYNTAX definitions and in the OPERATION PACKAGE +-- definitions. + playAnnouncement {}, + promptAndCollectUserInformation {}, + specializedResourceReport +FROM CAP-gsmSCF-gsmSRF-ops-args gsmSCF-gsmSRF-Operations-- Object Identifier 'gsmSCF-gsmSRF- +Operations' is updated to version8(7) in Rel-6. AS +-- a result, the present module, 'CAP-gsmSSF-gsmSCF-pkgs-contracts-ac', IMPORTS CAP +-- Operation definitions from CAP-gsmSCF-gsmSRF-ops-args version8(7). Operation +-- definitions are used in the ABSTRACT SYNTAX definitions and in the OPERATION PACKAGE +-- definitions. + + specializedResourceControlPackage {} +FROM CAP-gsmSCF-gsmSRF-pkgs-contracts-ac gsmSCF-gsmSRF-Protocol +-- Object Identifier 'gsmSCF-gsmSRF-Protocol' is updated to version8(7) in Rel-6. As a +-- result, the present module, 'CAP-gsmSSF-gsmSCF-pkgs-contracts-ac', IMPORTS CAP Operation +-- Package definitions from CAP-gsmSCF-gsmSRF-pkgs-contracts-ac version8(7). Operation +-- Package definitions are used in the CONTRACT definitions. + + id-ac-CAP-gsmSSF-scfGenericAC, + id-ac-CAP-gsmSSF-scfAssistHandoffAC, + id-ac-CAP-scf-gsmSSFGenericAC, +-- The APPLICATION-CONTEXT Identifiers for CAP V4 in Rel-6 are the same as for CAP V4 in Rel-5. + + id-CAPssnToScfGeneric, + id-CAPAssistHandoffssnToScf, + id-CAPScfToSsfGeneric, +-- The CONTRACT Identifiers for CAP V4 in Rel-6 are the same as for CAP V4 in Rel-5. + + id-as-gsmSSF-scfGenericAS, + id-as-scf-gsmSSFGenericAS, + id-as-assistHandoff-gsmSSF-scfAS, +-- The ABSTRACT-SYNTAX Identifiers for CAP V4 in Rel-6 are the same as for CAP V4 in Rel-5. + +``` + +``` + +id-package-scfActivation, +id-package-gsmSRF-scfActivationOfAssist, +id-package-assistConnectionEstablishment, +id-package-genericDisconnectResource, +id-package-nonAssistedConnectionEstablishment, +id-package-connect, +id-package-callHandling, +id-package-bcsmEventHandling, +id-package-ssfCallProcessing, +id-package-scfCallInitiation, +id-package-timer, +id-package-billing, +id-package-charging, +id-package-trafficManagement, +id-package-callReport, +id-package-signallingControl, +id-package-activityTest, +id-package-cancel, +id-package-cphResponse, +id-package-exceptionInform, +id-package-playTone, +-- The OPERATION-PACKAGE Identifiers for CAP V4 in Rel-6 are the same as for CAP V4 in Rel-5. + +classes, +ros-InformationObjects, +tc-Messages, +tc-NotationExtensions, + +gsmSSF-gsmSCF-Operations, +gsmSCF-gsmSRF-Operations, +-- Object Identifiers gsmSSF-gsmSCF-Operations and gsmSCF-gsmSRF-Operations are updated +-- to version8(7) in Rel-6. As a result, the present module, 'CAP-gsmSSF-gsmSCF-pkgs- +-- contracts-ac', IMPORTS Rel-6 versions of the CAP Operation definitions. + +gsmSCF-gsmSRF-Protocol +-- Object Identifier gsmSCF-gsmSRF-Protocol is updated to version8(7) in Rel-6. As a result, +-- the present module IMPORTS Rel-6 versions of the CAP Operation Package definitions. + +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)}; + +-- Application Contexts + +-- CAP V4 Rel-5 and CAP V4 Rel-6 use the same Application Context version. The CONTRACT +-- and ABSTRACT SYNTAXES for the call control related Application Contexts, however, are +-- defined in Rel-6. This is needed to use parameter definitions that are defined in Rel-6. + +-- Refer to ITU-T Recommendation Q.775 for the formal definition of APPLICATION-CONTEXT. +-- The structured DIALOGUE MODE is defined in ITU-T Recommendation Q.771; the +-- dialogue-abstract-syntax ABSTRACT SYNTAX is defined in ITU-T Recommendation Q.775. + +capsf-scfGenericAC APPLICATION-CONTEXT ::= { + CONTRACT capSsfToScfGeneric + DIALOGUE MODE structured + ABSTRACT SYNTAXES {dialogue-abstract-syntax | + gsmSSF-scfGenericAbstractSyntax} + APPLICATION CONTEXT NAME id-ac-CAP-gsmSSF-scfGenericAC} +-- 'capSsfToScfGeneric' and 'gsmSSF-scfGenericAbstractSyntax' are defined in the present +-- module. + +capsf-scfAssistHandoffAC APPLICATION-CONTEXT ::= { + CONTRACT capAssistHandoffssfToScf + DIALOGUE MODE structured + ABSTRACT SYNTAXES {dialogue-abstract-syntax | + assistHandoff-gsmSSF-scfAbstractSyntax} + APPLICATION CONTEXT NAME id-ac-CAP-gsmSSF-scfAssistHandoffAC} +-- 'capAssistHandoffssfToScf' and 'assistHandoff-gsmSSF-scfAbstractSyntax' are defined in +-- the present module. + +capsf-ssfGenericAC APPLICATION-CONTEXT ::= { + CONTRACT capScfToSsfGeneric + DIALOGUE MODE structured + ABSTRACT SYNTAXES {dialogue-abstract-syntax | + scf-gsmSSFGenericAbstractSyntax} + APPLICATION CONTEXT NAME id-ac-CAP-scf-gsmSSFGenericAC} +-- 'capScfToSsfGeneric' and 'scf-gsmSSFGenericAbstractSyntax' are defined in the present +-- module. + +``` + +``` + +-- Contracts +-- The CONTRACT definitions are updated for Rel-6, due to the fact that the individual +-- OPERATION-PACKAGE definitions are updated in Rel-6. + +capSsfToScfGeneric CONTRACT ::= { +-- dialogue initiated by gsmSSF with InitialDP Operation + INITIATOR CONSUMER OF {exceptionInformPackage {CAPSpecificBoundSet} | + scfActivationPackage {CAPSpecificBoundSet}} + RESPONDER CONSUMER OF {activityTestPackage | + assistConnectionEstablishmentPackage {CAPSpecificBoundSet} | + bcsmEventHandlingPackage {CAPSpecificBoundSet} | + billingPackage {CAPSpecificBoundSet} | + callHandlingPackage {CAPSpecificBoundSet} | + callReportPackage {CAPSpecificBoundSet} | + cancelPackage {CAPSpecificBoundSet} | + chargingPackage {CAPSpecificBoundSet} | + connectPackage {CAPSpecificBoundSet} | + cphResponsePackage {CAPSpecificBoundSet} | + genericDisconnectResourcePackage {CAPSpecificBoundSet} | + nonAssistedConnectionEstablishmentPackage {CAPSpecificBoundSet} | + playTonePackage {CAPSpecificBoundSet} | + signallingControlPackage {CAPSpecificBoundSet} | + specializedResourceControlPackage {CAPSpecificBoundSet} | + ssfCallProcessingPackage {CAPSpecificBoundSet} | + timerPackage {CAPSpecificBoundSet} | + trafficManagementPackage {CAPSpecificBoundSet} | + scfCallInitiationPackage {CAPSpecificBoundSet}} + ID + id-CAPSsfToScfGeneric +-- The OPERATION-PACKAGES are defined in the present module, except for +-- specializedResourceControlPackage, which is defined in CAP-gsmSCF-gsmSRF-pkgs-contracts-ac. + +capAssistHandoffssnToScf CONTRACT ::= { +-- dialogue initiated by gsmSSF with AssistRequestInstructions + INITIATOR CONSUMER OF {gsmSRF-scfActivationOfAssistPackage {CAPSpecificBoundSet}} + RESPONDER CONSUMER OF {activityTestPackage | + cancelPackage {CAPSpecificBoundSet} | + genericDisconnectResourcePackage {CAPSpecificBoundSet} | + nonAssistedConnectionEstablishmentPackage {CAPSpecificBoundSet} | + specializedResourceControlPackage {CAPSpecificBoundSet} | + timerPackage {CAPSpecificBoundSet}} + ID + id-CAPAssistHandoffssnToScf +-- The OPERATION-PACKAGES are defined in the present module, except for +-- specializedResourceControlPackage, which is defined in CAP-gsmSCF-gsmSRF-pkgs-contracts-ac. + +capScfToSsfGeneric CONTRACT ::= { +-- dialogue initiated by gsmSCF with InitiateCallAttempt, Generic Case + INITIATOR CONSUMER OF {activityTestPackage | + assistConnectionEstablishmentPackage {CAPSpecificBoundSet} | + bcsmEventHandlingPackage {CAPSpecificBoundSet} | + billingPackage {CAPSpecificBoundSet} | + callHandlingPackage {CAPSpecificBoundSet} | + callReportPackage {CAPSpecificBoundSet} | + cancelPackage {CAPSpecificBoundSet} | + chargingPackage {CAPSpecificBoundSet} | + connectPackage {CAPSpecificBoundSet} | + cphResponsePackage {CAPSpecificBoundSet} | + genericDisconnectResourcePackage {CAPSpecificBoundSet} | + nonAssistedConnectionEstablishmentPackage {CAPSpecificBoundSet} | + playTonePackage {CAPSpecificBoundSet} | + scfCallInitiationPackage {CAPSpecificBoundSet} | + specializedResourceControlPackage {CAPSpecificBoundSet} | + ssfCallProcessingPackage {CAPSpecificBoundSet} | + timerPackage {CAPSpecificBoundSet}} + RESPONDER CONSUMER OF {exceptionInformPackage {CAPSpecificBoundSet}} + ID + id-CAPScfToSsfGeneric +-- The OPERATION-PACKAGES are defined in the present module, except for +-- specializedResourceControlPackage, which is defined in CAP-gsmSCF-gsmSRF-pkgs-contracts-ac. + +-- Operation Packages +-- The OPERATION-PACKAGE definitions are updated for Rel-6, due to the fact that the individual +-- OPERATION definitions are updated in Rel-6. The OPERATION definitions are IMPORTED from +-- CAP-gsmSSF-gsmSCF-ops-args and from CAP-gsmSCF-gsmSRF-ops-args. + +scfActivationPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {initialDP {bound}} + ID + id-package-scfActivation} + +``` + +``` +gsmSRF-scfActivationOfAssistPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {assistRequestInstructions {bound}} + ID id-package-gsmSRF-scfActivationOfAssist} + +assistConnectionEstablishmentPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {establishTemporaryConnection {bound}} + ID id-package-assistConnectionEstablishment} + +genericDisconnectResourcePackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {disconnectForwardConnection | + disconnectForwardConnectionWithArgument {bound}} + ID id-package-genericDisconnectResource} + +nonAssistedConnectionEstablishmentPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {connectToResource {bound}} + ID id-package-nonAssistedConnectionEstablishment} + +connectPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {connect {bound}} + ID id-package-connect} + +callHandlingPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {releaseCall {bound}} + ID id-package-callHandling} + +bcsmEventHandlingPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {requestReportBCSMEVENT {bound}} + SUPPLIER INVOKES {eventReportBCSM {bound}} + ID id-package-bcsmEventHandling} + +ssfCallProcessingPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {collectInformation | continueWithArgument {bound} | continue} + ID id-package-ssfCallProcessing} + +scfCallInitiationPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {initiateCallAttempt {bound}} + ID id-package-scfCallInitiation} + +timerPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {resetTimer {bound}} + ID id-package-timer} + +billingPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {furnishChargingInformation {bound}} + ID id-package-billing} + +chargingPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {applyCharging {bound}} + SUPPLIER INVOKES {applyChargingReport {bound}} + ID id-package-charging} + +trafficManagementPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {callGap {bound}} + ID id-package-trafficManagement} + +callReportPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {callInformationRequest {bound}} + SUPPLIER INVOKES {callInformationReport {bound}} + ID id-package-callReport} + +signallingControlPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {sendChargingInformation {bound}} + ID id-package-signallingControl} + +activityTestPackage OPERATION-PACKAGE ::= { + CONSUMER INVOKES {activityTest} + ID id-package-activityTest} + +cancelPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {cancel {bound}} + ID id-package-cancel} + +cphResponsePackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {continueWithArgument {bound} | + disconnectLeg {bound} | + moveLeg {bound} | + splitLeg {bound}} + ID id-package-cphResponse} +``` + +``` + +exceptionInformPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {entityReleased {bound}} + ID id-package-exceptionInform} + +playTonePackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {playTone {bound}} + ID id-package-playTone} + +-- Abstract Syntaxes + +-- SsfToScfGenericInvokable and SsfToScfGenericReturnable use OPERATION definitions with +-- version8(7). As a result, GenericSSF-gsmSCF-PDUs uses version8(7) OPERATION definitions. +-- As a subsequent result, gsmSSF-scfGenericAbstractSyntax uses version8(7) OPERATION +-- definitions. That ABSTRACT-SYNTAX is used in the capssf-scfGenericAC APPLICATION-CONTEXT +-- definition (CAP from gsmSSF to gsmSCF). + +gsmSSF-scfGenericAbstractSyntax ABSTRACT-SYNTAX ::= { + GenericSSF-gsmSCF-PDUs + IDENTIFIED BY id-as-gsmSSF-scfGenericAS} +-- 'GenericSSF-gsmSCF-PDUs' is defined in the present module. + +GenericSSF-gsmSCF-PDUs ::= TCMessage {{SsfToScfGenericInvokable}, + {SsfToScfGenericReturnable}} +-- 'SsfToScfGenericInvokable' and 'SsfToScfGenericReturnable' are defined in the present module. + +SsfToScfGenericInvokable OPERATION ::= { + activityTest | + applyCharging {cAPSpecificBoundSet} | + applyChargingReport {cAPSpecificBoundSet} | + callInformationReport {cAPSpecificBoundSet} | + callInformationRequest {cAPSpecificBoundSet} | + cancel {cAPSpecificBoundSet} | + connect {cAPSpecificBoundSet} | + continueWithArgument {cAPSpecificBoundSet} | + connectToResource {cAPSpecificBoundSet} | + collectInformation | + disconnectForwardConnection | + disconnectForwardConnectionWithArgument {cAPSpecificBoundSet} | + disconnectLeg {cAPSpecificBoundSet} | + entityReleased {cAPSpecificBoundSet} | + establishTemporaryConnection {cAPSpecificBoundSet} | + eventReportBCSM {cAPSpecificBoundSet} | + furnishChargingInformation {cAPSpecificBoundSet} | + initialDP {cAPSpecificBoundSet} | + initiateCallAttempt {cAPSpecificBoundSet} | + moveLeg {cAPSpecificBoundSet} | + releaseCall {cAPSpecificBoundSet} | + requestReportBCSMEVENT {cAPSpecificBoundSet} | + resetTimer {cAPSpecificBoundSet} | + sendChargingInformation {cAPSpecificBoundSet} | + splitLeg {cAPSpecificBoundSet} | + playAnnouncement {cAPSpecificBoundSet} | + playTone {cAPSpecificBoundSet} | + promptAndCollectUserInfo {cAPSpecificBoundSet} | + specializedResourceReport +} +-- The OPERATION definitions are IMPORTED from CAP-gsmSSF-gsmSCF-ops-args and from +-- CAP-gsmSCF-gsmSRF-ops-args. + +SsfToScfGenericReturnable OPERATION ::= { + activityTest | + applyCharging {cAPSpecificBoundSet} | + applyChargingReport {cAPSpecificBoundSet} | + callGap {cAPSpecificBoundSet} | + callInformationRequest {cAPSpecificBoundSet} | + cancel {cAPSpecificBoundSet} | + connect {cAPSpecificBoundSet} | + connectToResource {cAPSpecificBoundSet} | + collectInformation | + continue | + continueWithArgument {cAPSpecificBoundSet} | + disconnectForwardConnection | + disconnectForwardConnectionWithArgument {cAPSpecificBoundSet} | + disconnectLeg {cAPSpecificBoundSet} | + entityReleased {cAPSpecificBoundSet} | + establishTemporaryConnection {cAPSpecificBoundSet} | +} + +``` + +``` + furnishChargingInformation {cAPSSpecificBoundSet} | + initialDP {cAPSSpecificBoundSet} | + initiateCallAttempt {cAPSSpecificBoundSet} | + moveLeg {cAPSSpecificBoundSet} | + releaseCall {cAPSSpecificBoundSet} | + requestReportBCSMEVENT {cAPSSpecificBoundSet} | + resetTimer {cAPSSpecificBoundSet} | + sendChargingInformation {cAPSSpecificBoundSet} | + splitLeg {cAPSSpecificBoundSet} | + playAnnouncement {cAPSSpecificBoundSet} | + playTone {cAPSSpecificBoundSet} | + promptAndCollectUserInfo {cAPSSpecificBoundSet} + } +-- The OPERATION definitions are IMPORTED from CAP-gsmSSF-gsmSCF-ops-args and from +-- CAP-gsmSCF-gsmSRF-ops-args. + +-- AssistHandoffssfToScfInvokable and AssistHandoffssfToScfReturnable use OPERATION definitions +-- with version8(7). As a result, AssistHandoffssf-gsmSCF-PDUs uses version8(7) OPERATION +-- definitions. As a subsequent result, assistHandoff-gsmSSF-scfAbstractSyntax uses version8(7) +-- OPERATION definitions. That ABSTRACT-SYNTAX is used in the capssf-scfAssistHandoffAC +-- APPLICATION-CONTEXT definition (CAP from assist gsmSSF to gsmSCF). + +assistHandoff-gsmSSF-scfAbstractSyntax ABSTRACT-SYNTAX ::= { + AssistHandoffssf-gsmSCF-PDUs + IDENTIFIED BY id-as-assistHandoff-gsmSSF-scfAS} +-- 'AssistHandoffssf-gsmSCF-PDUs' is defined in the present module. + +AssistHandoffssf-gsmSCF-PDUs ::= TCMessage {{AssistHandoffssfToScfInvokable}, + {AssistHandoffssfToScfReturnable}} +-- 'AssistHandoffssfToScfInvokable' and 'AssistHandoffssfToScfReturnable' are defined in the +-- present module. + +AssistHandoffssfToScfInvokable OPERATION ::= { + activityTest | + assistRequestInstructions {cAPSSpecificBoundSet} | + cancel {cAPSSpecificBoundSet} | + connectToResource {cAPSSpecificBoundSet} | + disconnectForwardConnection | + playAnnouncement {cAPSSpecificBoundSet} | + promptAndCollectUserInfo {cAPSSpecificBoundSet} | + resetTimer {cAPSSpecificBoundSet} | + specializedResourceReport +} +-- The OPERATION definitions are IMPORTED from CAP-gsmSSF-gsmSCF-ops-args and from +-- CAP-gsmSCF-gsmSRF-ops-args. + +AssistHandoffssfToScfReturnable OPERATION ::= { + activityTest | + assistRequestInstructions {cAPSSpecificBoundSet} | + cancel {cAPSSpecificBoundSet} | + connectToResource {cAPSSpecificBoundSet} | + disconnectForwardConnection | + playAnnouncement {cAPSSpecificBoundSet} | + promptAndCollectUserInfo {cAPSSpecificBoundSet} | + resetTimer {cAPSSpecificBoundSet} +} +-- The OPERATION definitions are IMPORTED from CAP-gsmSSF-gsmSCF-ops-args and from +-- CAP-gsmSCF-gsmSRF-ops-args. + +-- ScfToSsfGenericInvokable and ScfToSsfGenericReturnable use OPERATION definitions +-- with version8(7). As a result, GenericSCF-gsmSSF-PDUs uses version8(7) OPERATION +-- definitions. As a subsequent result, scf-gsmSSFGenericAbstractSyntax uses version8(7) +-- OPERATION definitions. That ABSTRACT-SYNTAX is used in the capscf-ssfGenericAC +-- APPLICATION-CONTEXT definition (CAP from gsmSCF to gsmSSF). +scf-gsmSSFGenericAbstractSyntax ABSTRACT-SYNTAX ::= { + GenericSCF-gsmSSF-PDUs + IDENTIFIED BY id-as-scf-gsmSSFGenericAS} +-- 'GenericSCF-gsmSSF-PDUs' is defined in the present module. + +GenericSCF-gsmSSF-PDUs ::= TCMessage {{ScfToSsfGenericInvokable}, + {ScfToSsfGenericReturnable}} +-- 'ScfToSsfGenericInvokable' and 'ScfToSsfGenericReturnable' are defined in the +-- present module. + +ScfToSsfGenericInvokable OPERATION ::= { + activityTest | + applyCharging {cAPSSpecificBoundSet} | +``` + +``` + + applyChargingReport {cAPSpecificBoundSet} | + callInformationRequest {cAPSpecificBoundSet} | + cancel {cAPSpecificBoundSet} | + collectInformation | + connect {cAPSpecificBoundSet} | + connectToResource {cAPSpecificBoundSet} | + continue | + continueWithArgument {cAPSpecificBoundSet} | + disconnectForwardConnection | + disconnectForwardConnectionWithArgument {cAPSpecificBoundSet} | + disconnectLeg {cAPSpecificBoundSet} | + establishTemporaryConnection {cAPSpecificBoundSet} | + furnishChargingInformation {cAPSpecificBoundSet} | + initiateCallAttempt {cAPSpecificBoundSet} | + moveLeg {cAPSpecificBoundSet} | + playTone {cAPSpecificBoundSet} | + releaseCall {cAPSpecificBoundSet} | + requestReportBCSMEVENT {cAPSpecificBoundSet} | + resetTimer {cAPSpecificBoundSet} | + sendChargingInformation {cAPSpecificBoundSet} | + splitLeg {cAPSpecificBoundSet} | + playAnnouncement {cAPSpecificBoundSet} | + promptAndCollectUserInfo {cAPSpecificBoundSet} + } + -- The OPERATION definitions are IMPORTED from CAP-gsmSSF-gsmSCF-ops-args and from + -- CAP-gsmSCF-gsmSRF-ops-args. + + ScfToSsfGenericReturnable OPERATION ::= { + activityTest | + applyCharging {cAPSpecificBoundSet} | + applyChargingReport {cAPSpecificBoundSet} | + callInformationReport {cAPSpecificBoundSet} | + callInformationRequest {cAPSpecificBoundSet} | + cancel {cAPSpecificBoundSet} | + connect {cAPSpecificBoundSet} | + connectToResource {cAPSpecificBoundSet} | + disconnectForwardConnection | + disconnectForwardConnectionWithArgument {cAPSpecificBoundSet} | + disconnectLeg {cAPSpecificBoundSet} | + entityReleased {cAPSpecificBoundSet} | + establishTemporaryConnection {cAPSpecificBoundSet} | + eventReportBCSM {cAPSpecificBoundSet} | + furnishChargingInformation {cAPSpecificBoundSet} | + initiateCallAttempt {cAPSpecificBoundSet} | + moveLeg {cAPSpecificBoundSet} | + requestReportBCSMEVENT {cAPSpecificBoundSet} | + resetTimer {cAPSpecificBoundSet} | + sendChargingInformation {cAPSpecificBoundSet} | + splitLeg {cAPSpecificBoundSet} | + playAnnouncement {cAPSpecificBoundSet} | + playTone {cAPSpecificBoundSet} | + promptAndCollectUserInfo {cAPSpecificBoundSet} | + specializedResourceReport + } + -- The OPERATION definitions are IMPORTED from CAP-gsmSSF-gsmSCF-ops-args and from + -- CAP-gsmSCF-gsmSRF-ops-args. + +END + +``` + +## 6.2 gsmSCF/gsmSRF interface + +### 6.2.1 gsmSCF/gsmSRF operations and arguments + +``` + +CAP-gsmSCF-gsmSRF-ops-args {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-gsmSCF-gsmSRF-ops-args(103) version8(7)} + +``` + +``` + +DEFINITIONS IMPLICIT TAGS ::= BEGIN + +``` + +``` + + -- This module contains the operations and operation arguments used for the + -- gsmSRF - gsmSCF interface, for the control of circuit switched calls. + + -- The table in subclause 2.1 lists the specifications that contain the modules + -- that are used by CAP. + +``` + +``` + +IMPORTS + +``` + +``` + +OPERATION +FROM Remote-Operations-Information-Objects ros-InformationObjects + + opcode-playAnnouncement, + opcode-promptAndCollectUserInfo, + opcode-specializedResourceReport +FROM CAP-operationcodes operationcodes +-- The CAP Operation identifiers for CAP V4 in Rel-6 are the same as the CAP Operation +-- identifiers for CAP V4 in Rel-5. + + CallSegmentID {}, + CollectedInfo, + Digits {}, + Extensions {}, + InformationToSend {} +FROM CAP-datatypes datatypes +-- For Rel-6, the CAP-datatypes module is updated to version8(7); Object Identifier 'datatypes' +-- is also updated to version8(7). As a result, the present module uses Rel-6 data type definitions. + + canceled, + improperCallerResponse, + missingParameter, + parameterOutOfRange, + systemFailure, + taskRefused, + unavailableResource, + unexpectedComponentSequence, + unexpectedDataValue, + unexpectedParameter, + unknownCSID +FROM CAP-errortypes errortypes +-- For Rel-6, the CAP-errortypes module is updated to version8(7); Object Identifier +-- 'errortypes' is also updated to version8(7). As a result, the present module uses Rel-6 +-- error type definitions. + +PARAMETERS-BOUND +FROM CAP-classes classes + + ros-InformationObjects, + operationcodes, + datatypes, + errortypes, + classes +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} + +; + +playAnnouncement {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT PlayAnnouncementArg {bound} + RETURN RESULT FALSE + ERRORS {canceled | + missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unavailableResource | + unknownCSID} + LINKED {specializedResourceReport} + CODE opcode-playAnnouncement} +-- Direction: gsmSCF -> gsmSRF, Timer: Tpa +-- This operation is to be used after Establish Temporary Connection (assist procedure +-- with a second gsmSSF) or a Connect to Resource (no assist) operation. It may be used +-- for inband interaction with a mobile station, or for interaction with an ISDN user. +-- In the former case, the gsmSRF is usually collocated with the gsmSSF for standard +-- tones (congestion tone...) or standard announcements. +-- In the latter case, the gsmSRF is always collocated with the gsmSSF in the switch. +-- Any error is returned to the gsmSCF. The timer associated with this operation must +-- be of a sufficient duration to allow its linked operation to be correctly correlated. + +PlayAnnouncementArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + informationToSend [0] InformationToSend {bound}, + disconnectFromIPForbidden [1] BOOLEAN DEFAULT TRUE, + requestAnnouncementCompleteNotification [2] BOOLEAN DEFAULT TRUE, +} + +``` + +``` + + extensions [3] Extensions {bound} OPTIONAL, + callSegmentID [5] CallSegmentID {bound} OPTIONAL, + requestAnnouncementStartedNotification [51] BOOLEAN DEFAULT FALSE, + ... + } + +promptAndCollectUserInformation {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT PromptAndCollectUserInformationArg {bound} + RESULT ReceivedInformationArg {bound} + ERRORS {canceled | + improperCallerResponse | + missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unavailableResource | + unexpectedDataValue | + unexpectedParameter | + unknownCSID} + LINKED {specializedResourceReport} + CODE opcode-promptAndCollectUserInformation} + -- Direction: gsmSCF -> gsmSRF, Timer: Tpc + -- This operation is used to interact with a user to collect information. + + PromptAndCollectUserInformationArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + collectedInfo [0] CollectedInfo, + disconnectFromIPForbidden [1] BOOLEAN DEFAULT TRUE, + informationToSend [2] InformationToSend {bound} OPTIONAL, + extensions [3] Extensions {bound} OPTIONAL, + callSegmentID [4] CallSegmentID {bound} OPTIONAL, + requestAnnouncementStartedNotification [51] BOOLEAN DEFAULT FALSE, + ... + } + + ReceivedInformationArg {PARAMETERS-BOUND : bound} ::= CHOICE { + digitsResponse [0] Digits {bound} + } + + specializedResourceReport OPERATION ::= { + ARGUMENT SpecializedResourceReportArg + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE opcode-specializedResourceReport} + -- Direction: gsmSRF -> gsmSCF, Timer: Tsrr + -- This operation is used as the response to a PlayAnnouncement operation when the announcement + -- completed report indication is set. + + SpecializedResourceReportArg ::= CHOICE { + allAnnouncementsComplete [50] NULL, + firstAnnouncementStarted [51] NULL + } + +END + +``` + +The following value ranges apply for operation specific timers in CAP: + +| | | +|---------|------------------| +| short: | 1 s - 10 s | +| medium: | 1 s - 60 s | +| long: | 1 s - 30 minutes | + +Table 6-2 lists all operation timers and the value range for each timer. The definitive value for each operation timer may be network specific and has to be defined by the network operator. + +**Table 6-2: Operation timers and their value range** + +| Operation Name | Timer | Value range | +|---------------------------------|------------------|-------------| +| PlayAnnouncement | T pa | Long | +| PromptAndCollectUserInformation | T pc | Long | +| SpecializedResourceReport | T srr | Short | + +## 6.2.2 gsmSRF/gsmSCF contracts, packages and ACs + +### 6.2.2.1 gsmSRF/gsmSCF ASN.1 modules + +CAP-gsmSCF-gsmSRF-pkgs-contracts-ac {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) modules(3) cap-gsmSCF-gsmSRF-pkgs-contracts-ac(104) version8(7)} + +DEFINITIONS ::= BEGIN + +- This module specifies the Operation Packages, Contracts, Application Contexts +- and Abstract Syntaxes used for the gsmSRF – gsmSCF interface, for the control of +- circuit switched calls. + +- The table in subclause 2.1 lists the specifications that contain the modules +- that are used by CAP. + +IMPORTS + +PARAMETERS-BOUND, +cAPSpecificBoundSet + +FROM CAP-classes classes + +- Elements that exist in cAPSpecificBoundSet in Rel-5 are not changed in Rel-6. As a +- result, the value range of data type definitions in Rel-5 are not changed in Rel-6. + +CONTRACT, +OPERATION-PACKAGE, +OPERATION + +FROM Remote-Operations-Information-Objects ros-InformationObjects + +TCMessage {} + +FROM TCAPMessages tc-Messages + +APPLICATION-CONTEXT, +dialogue-abstract-syntax + +FROM TC-Notation-Extensions tc-NotationExtensions + +playAnnouncement {}, +promptAndCollectUserInfo {}, +specializedResourceReport + +FROM CAP-gsmSCF-gsmSRF-ops-args gsmSCF-gsmSRF-Operations-- Object Identifier 'gsmSCF-gsmSRF-Operations' is updated to version8(7) in Rel-6. As + +- a result, the present module, 'CAP-gsmSCF-gsmSRF-pkgs-contracts-ac', IMPORTS CAP +- Operation definitions from CAP-gsmSCF-gsmSRF-ops-args version8(7). Operation +- definitions are used in the ABSTRACT SYNTAX definitions and in the OPERATION PACKAGE +- definitions. + +activityTest, +cancel {}, +assistRequestInstructions {} + +FROM CAP-gsmSSF-gsmSCF-ops-args gsmSSF-gsmSCF-Operations + +- Object Identifier 'gsmSSF-gsmSCF-Operations' is updated to version8(7) in Rel-6. AS +- a result, the present module, 'CAP-gsmSCF-gsmSRF-pkgs-contracts-ac', IMPORTS CAP +- Operation definitions from CAP-gsmSSF-gsmSCF-ops-args version8(7). Operation +- definitions are used in the ABSTRACT SYNTAX definitions and in the OPERATION PACKAGE +- definitions. + +gsmSRF-scfActivationOfAssistPackage {} + +FROM CAP-gsmSSF-gsmSCF-pkgs-contracts-ac gsmSSF-gsmSCF-Protocol + +- Object Identifier 'gsmSSF-gsmSCF-Protocol' is updated to version8(7) in Rel-6. As a +- result, the present module, 'CAP-gsmSCF-gsmSRF-pkgs-contracts-ac', IMPORTS CAP Operation +- Package definitions from CAP-gsmSSF-gsmSCF-pkgs-contracts-ac version8(7). Operation +- Package definitions are used in the CONTRACT definitions. + +id-package-specializedResourceControl, +id-package-activityTest, +id-package-gsmSRF-scfCancel, + +``` + +-- The OPERATION-PACKAGE Identifiers for CAP V4 in Rel-6 are the same as for CAP V4 in Rel-5. + + id-ac-gsmSRF-gsmSCF, +-- The APPLICATION-CONTEXT Identifiers for CAP V4 in Rel-6 are the same as for CAP V4 in Rel-5. + + id-contract-gsmSRF-gsmSCF, +-- The CONTRACT Identifiers for CAP V4 in Rel-6 are the same as for CAP V4 in Rel-5. + + id-as-basic-gsmSRF-gsmSCF, +-- The ABSTRACT-SYNTAX Identifiers for CAP V4 in Rel-6 are the same as for CAP V4 in Rel-5. + + classes, + ros-InformationObjects, + tc-Messages, + tc-NotationExtensions, + + gsmSCF-gsmSRF-Operations, + gsmSSF-gsmSCF-Operations, +-- Object Identifiers gsmSSF-gsmSCF-Operations and gsmSCF-gsmSRF-Operations are updated +-- to version8(7) in Rel-6. As a result, the present module, 'CAP-gsmSCF-gsmSRF-pkgs- +-- contracts-ac', IMPORTS Rel-6 versions of the CAP Operation definitions. + + gsmSSF-gsmSCF-Protocol +-- Object Identifier gsmSSF-gsmSCF-Protocol is updated to version8(7) in Rel-6. As a result, +-- the present module IMPORTS Rel-6 versions of the CAP Operation Package definitions. + +``` + +``` + +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)}; + +``` + +#### -- Application Contexts + +``` + +-- CAP V4 Rel-5 and CAP V4 Rel-6 use the same Application Context version. The CONTRACT +-- and ABSTRACT SYNTAXES for the call control related Application Contexts, however, are +-- defined in Rel-6. This is needed to use parameter definitions that are defined in Rel-6. + +-- Refer to ITU-T Recommendation Q.775 for the formal definition of APPLICATION-CONTEXT. +-- The structured DIALOGUE MODE is defined in ITU-T Recommendation Q.771; the +-- dialogue-abstract-syntax ABSTRACT SYNTAX is defined in ITU-T Recommendation Q.775. + +``` + +``` + +gsmSRF-gsmSCF-ac APPLICATION-CONTEXT ::= { + +``` + +``` + + CONTRACT gsmSRF-gsmSCF-contract + DIALOGUE MODE structured + TERMINATION basic + ABSTRACT SYNTAXES {dialogue-abstract-syntax | + gsmSRF-gsmSCF-abstract-syntax} + APPLICATION CONTEXT NAME id-ac-gsmSRF-gsmSCF} + +``` + +``` + +-- 'gsmSRF-gsmSCF-contract' and 'gsmSRF-gsmSCF-abstract-syntax' are defined in the present +-- module. + +``` + +#### -- Contracts + +``` + +-- The CONTRACT definitions are updated for Rel-6, due to the fact that the individual +-- OPERATION-PACKAGE definitions are updated in Rel-6. + +``` + +``` + +gsmSRF-gsmSCF-contract CONTRACT ::= { + +``` + +``` + + INITIATOR CONSUMER OF {gsmSRF-scfActivationOfAssistPackage {cAPSpecificBoundSet}} + RESPONDER CONSUMER OF {specializedResourceControlPackage {cAPSpecificBoundSet} | + activityTestPackage | + gsmSRF-scfCancelPackage {cAPSpecificBoundSet} } + +``` + +``` + + ID id-contract-gsmSRF-gsmSCF} + +``` + +``` + +-- The OPERATION-PACKAGES are defined in the present module, except for +-- gsmSRF-scfActivationOfAssistPackage, which is defined in CAP-gsmSSF-gsmSCF-pkgs-contracts-ac. + +``` + +#### -- Operation Packages + +``` + +-- The OPERATION-PACKAGE definitions are updated for Rel-6, due to the fact that the individual +-- OPERATION definitions are updated in Rel-6. The OPERATION definitions are IMPORTED from +-- CAP-gsmSSF-gsmSCF-ops-args and from CAP-gsmSCF-gsmSRF-ops-args. + +``` + +``` + +specializedResourceControlPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + +``` + +``` + + CONSUMER INVOKE {playAnnouncement {bound} | + +``` + +``` + + promptAndCollectUserInformation {bound}} + SUPPLIER INVOKES {specializedResourceReport} + ID id-package-specializedResourceControl} + +gsmSRF-scfCancelPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {cancel {bound}} + ID id-package-gsmSRF-scfCancel} + +activityTestPackage OPERATION-PACKAGE ::= { + CONSUMER INVOKES {activityTest} + ID id-package-activityTest} + +-- Abstract Syntaxes + +-- GsmSRFgsmSCFInvokable and GsmSRFgsmSCFReturnable use OPERATION definitions with +-- version8(7). As a result, BASIC-gsmSRF-gsmSCF-PDUs uses version8(7) OPERATION definitions. +-- As a subsequent result, gsmSRF-gsmSCF-abstract-syntax uses version8(7) OPERATION +-- definitions. That ABSTRACT-SYNTAX is used in the gsmSRF-gsmSCF-ac APPLICATION-CONTEXT +-- definition (CAP from gsmSRF to gsmSCF). + +gsmSRF-gsmSCF-abstract-syntax ABSTRACT-SYNTAX ::= { + BASIC-gsmSRF-gsmSCF-PDUs + IDENTIFIED BY id-as-basic-gsmSRF-gsmSCF} +-- 'BASIC-gsmSRF-gsmSCF-PDUs' is defined in the present module. + +BASIC-gsmSRF-gsmSCF-PDUs ::= TCMessage {{GsmSRFgsmSCFInvokable}, + {GsmSRFgsmSCFReturnable}} +-- 'GsmSRFgsmSCFInvokable' and 'GsmSRFgsmSCFReturnable' are defined in the present module. + +GsmSRFgsmSCFInvokable OPERATION ::= { + activityTest | + assistRequestInstructions {CAPSpecificBoundSet} | + cancel {CAPSpecificBoundSet} | + playAnnouncement {CAPSpecificBoundSet} | + promptAndCollectUserInformation {CAPSpecificBoundSet} | + specializedResourceReport +} +-- The OPERATION definitions are IMPORTED from CAP-gsmSSF-gsmSCF-ops-args and from +-- CAP-gsmSCF-gsmSRF-ops-args. + +GsmSRFgsmSCFReturnable OPERATION ::= { + activityTest | + assistRequestInstructions {CAPSpecificBoundSet} | + cancel {CAPSpecificBoundSet} | + playAnnouncement {CAPSpecificBoundSet} | + promptAndCollectUserInformation {CAPSpecificBoundSet} +} +-- The OPERATION definitions are IMPORTED from CAP-gsmSSF-gsmSCF-ops-args and from +-- CAP-gsmSCF-gsmSRF-ops-args. + +END + +``` + +## 7 SMS Control + +This clause defines the protocol used for CAMEL control of MO SMS and MT SMS. CAMEL control of MO SMS uses version 3 of the application context, and CAMEL control of MT SMS uses version 4 of the application context. + +### 7.1 SMS operations and arguments + +``` + +CAP-SMS-ops-args {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) +modules(3) cap-SMS-ops-args(105) version8(7)} +-- The module CAP-SMS-ops-args is updated to version8(7) for Rel-6. The OPERATION definitions +-- are not modified. + +``` + +``` +DEFINITIONS IMPLICIT TAGS::= BEGIN + +-- This module contains the operations and operation arguments used for the +-- smsSSSF- gsmSCF interface, for the control of MO-SMS and MT-SMS. + +-- The table in subclause 2.1 lists the specifications that contain the modules +-- that are used by CAP. + +IMPORTS + + errortypes, + datatypes, + operationcodes, + classes, + ros-InformationObjects, + tc-Messages +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} + + OPERATION +FROM Remote-Operations-Information-Objects ros-InformationObjects + + ServiceKey +FROM CS1-DataTypes {itu-t(0) identified-organization(4) etsi(0) inDomain(1) in-network(1) +modules(0) cs1-datatypes(2) version1(0)} + + MiscCallInfo +FROM CS2-datatypes {itu-t(0) identified-organization(4) etsi(0) inDomain(1) in-network(1) +cs2(20) modules(0) in-cs2-datatypes (0) version1(0)} + + IMEI, + IMSI, + ISDN-AddressString +FROM MAP-CommonDataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-CommonDataTypes(18) version12(12)} + + GPRSMSClass, + LocationInformation, + MS-Classmark2 +FROM MAP-MS-DataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-MS-DataTypes(11) version12(12)} + + PARAMETERS-BOUND +FROM CAP-classes classes + + opcode-connectSMS, + opcode-continueSMS, + opcode-eventReportSMS, + opcode-furnishChargingInformationSMS, + opcode-initialDPSMS, + opcode-releaseSMS, + opcode-requestReportSMSEvent, + opcode-resetTimerSMS +FROM CAP-operationcodes operationcodes +-- The CAP Operation identifiers for CAP V3 and CAP V4 for SMS in Rel-6 are the same as in Rel-5. + + CalledPartyBCDNumber {}, + EventSpecificInformationSMS, + EventTypeSMS, + Extensions {}, + FCISMSBillingChargingCharacteristics, + LocationInformationGPRS, + RPCause, + SMS-AddressString, + SMSEvent, + TimeAndTimezone {}, + TimerID, + TimerValue, + TPDataCodingScheme, + TPProtocolIdentifier, + TPShortMessageSpecificInfo, + TPValidityPeriod +FROM CAP-datatypes datatypes +-- For Rel-6, the CAP-datatypes module is updated to version8(7); Object Identifier 'datatypes' +-- is also updated to version8(7). As a result, the present module uses Rel-6 data type definitions. + + missingCustomerRecord, + missingParameter, +``` + +``` + +parameterOutOfRange, +systemFailure, +taskRefused, +unexpectedComponentSequence, +unexpectedDataValue, +unexpectedParameter +FROM CAP-errorTypes errorTypes +-- For Rel-6, the CAP-errorTypes module is updated to version8(7); Object Identifier +-- 'errorTypes' is also updated to version8(7). As a result, the present module uses Rel-6 +-- error type definitions. + +CallReferenceNumber +FROM MAP-CH-DataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-CH-DataTypes(13) version12(12)} + +; + +connectSMS {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT ConnectSMSArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter} + CODE opcode-connectSMS} +-- Direction: gsmSCF -> gsmSSF or gprsSSF, Timer: Tconsms +-- This operation is used to request the smsSSF to perform the SMS processing +-- actions to route or forward a short message to a specified destination. + +ConnectSMSArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + callingPartyNumber [0] SMS-AddressString OPTIONAL, + destinationSubscriberNumber [1] CalledPartyBCDNumber {bound} OPTIONAL, + smSCAddress [2] ISDN-AddressString OPTIONAL, + extensions [10] Extensions {bound} OPTIONAL, + ... +} + +continueSMS OPERATION ::= { + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE opcode-continueSMS} +-- Direction: gsmSCF -> smsSSF, Timer: Tcuesms +-- This operation is used to request the smsSSF to proceed with +-- Short Message processing at the DP at which it previously suspended +-- Short Message processing to await gsmSCF instructions (i.e. proceed +-- to the next Point in Association in the SMS FSM). The smsSSF +-- continues SMS processing without substituting new data from the gsmSCF. + +eventReportSMS {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT EventReportSMSArg {bound} + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE opcode-eventReportSMS} +-- Direction: gsmSSF or gprsSSF -> gsmSCF, Timer: Terbsms +-- This operation is used to notify the gsmSCF of a Short Message related event (FSM events +-- such as submission, delivery or failure) previously requested by the gsmSCF in a +-- RequestReportSMSEvent operation. + +EventReportSMSArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + eventTypeSMS [0] EventTypeSMS, + eventSpecificInformationSMS [1] EventSpecificInformationSMS OPTIONAL, + miscCallInfo [2] MiscCallInfo DEFAULT {messageType request}, + extensions [10] Extensions {bound} OPTIONAL, + ... +} + +furnishChargingInformationSMS {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT FurnishChargingInformationSMSArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter} + +``` + +``` + + CODE opcode-furnishChargingInformationSMS} +-- Direction: gsmSCF -> gsmSSF or gprsSSF, Timer: Tfcisms +-- This operation is used to request the smsSSF to generate, register a charging record +-- or to include some information in the default SM record. The registered charging record is +-- intended for off line charging of the Short Message. + +``` + +``` + +FurnishChargingInformationSMSArg {PARAMETERS-BOUND : bound} ::= + FCISMSBillingChargingCharacteristics {bound} + +``` + +``` + +initialDPSMS {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT InitialDPSMSArg {bound} + RETURN RESULT FALSE + ERRORS {missingCustomerRecord | + missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter} + CODE opcode-initialDPSMS} +-- Direction: gsmSSF or gprsSSF -> gsmSCF, Timer: Tidpsms +-- This operation is used after a TDP to indicate request for service. + +``` + +``` + +InitialDPSMSArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + serviceKey [0] ServiceKey, + destinationSubscriberNumber [1] CalledPartyBCDNumber {bound} OPTIONAL, + callingPartyNumber [2] SMS-AddressString OPTIONAL, + eventTypeSMS [3] EventTypeSMS OPTIONAL, + iMSI [4] IMSI OPTIONAL, + locationInformationMSC [5] LocationInformation OPTIONAL, + locationInformationGPRS [6] LocationInformationGPRS OPTIONAL, + sMSCAddress [7] ISDN-AddressString OPTIONAL, + timeAndTimezone [8] TimeAndTimezone {bound} OPTIONAL, + tpShortMessageSpecificInfo [9] TPShortMessageSpecificInfo OPTIONAL, + tpProtocolIdentifier [10] TPProtocolIdentifier OPTIONAL, + tpDataCodingScheme [11] TPDataCodingScheme OPTIONAL, + tpValidityPeriod [12] TPValidityPeriod OPTIONAL, + extensions [13] Extensions {bound} OPTIONAL, + ..., + smsReferenceNumber [14] CallReferenceNumber OPTIONAL, + mscAddress [15] ISDN-AddressString OPTIONAL, + sgsn-Number [16] ISDN-AddressString OPTIONAL, + ms-Classmark2 [17] MS-Classmark2 OPTIONAL, + gPRSMSClass [18] GPRSMSClass OPTIONAL, + iMEI [19] IMEI OPTIONAL, + calledPartyNumber [20] ISDN-AddressString OPTIONAL +} + +``` + +-- The UserCSGInformation is conveyed in the LocationInformation for CS and LocationInformationGPRS + -- for GPRS. The encoding of the parameter is as defined in 3GPP TS 29.002 [11]. + +``` + +releaseSMS OPERATION ::= { + ARGUMENT ReleaseSMSArg + RETURN RESULT FALSE + ALWAYS RESPONDS FALSE + CODE opcode-releaseSMS} +-- Direction: gsmSCF -> gsmSSF or gprsSSF, Timer: Trelsms +-- This operation is used to prevent an attempt to submit or deliver a short message. + +``` + +``` +ReleaseSMSArg ::= RPCause +``` + +``` + +requestReportSMSEvent {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT RequestReportSMSEventArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter} + CODE opcode-requestReportSMSEvent} +-- Direction: gsmSCF -> gsmSSF or gprsSSF, Timer: Trrbsms +-- This operation is used to request the gsmSSF or gprsSSF to monitor for a +-- Short Message related event (FSM events such as submission, delivery or failure) +-- and to send a notification to the gsmSCF when the event is detected. + +``` + +``` + +RequestReportSMSEventArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + smSEvents [0] SEQUENCE SIZE (1..bound.&numOfSMSEvents) OF SMSEvent, + extensions [10] Extensions {bound} OPTIONAL, + ... +} + +-- Indicates the Short Message related events(s) for notification. + +resetTimerSMS {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT ResetTimerSMSArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter} + CODE opcode-resetTimerSMS} + +-- Direction: gsmSCF -> smsSSF, Timer: Trtsms +-- This operation is used to request the smsSSF to refresh an application +-- timer in the smsSSF. + +ResetTimerSMSArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + timerID [0] TimerID DEFAULT tssf, + timervalue [1] TimerValue, + extensions [2] Extensions {bound} OPTIONAL, + ... +} + +END + +``` + +### 7.1.1 Operation timers + +The following value ranges apply for operation specific timers in CAP: + +| | | +|---------|-------------------------| +| short: | 1 to 20 seconds; | +| medium: | 1 to 60 seconds; | +| long: | 1 second to 30 minutes. | + +Table 7-1 lists all operation timers and the value range for each timer. The definitive value for each operation timer may be network specific and has to be defined by the network operator. + +**Table 7-1: Operation timers and their value range** + +| Operation Name | Timer | Value range | +|-------------------------------|---------------------|-------------| +| ConnectSMS | T consms | Short | +| ContinueSMS | T cuesms | Short | +| EventReportSMS | T erbsms | Short | +| FurnishChargingInformationSMS | T fcisms | Short | +| InitialDPSMS | T idpsms | Short | +| ReleaseSMS | T relsms | Short | +| RequestReportSMSEvent | T rrbsms | Short | +| ResetTimerSMS | T rtsms | Short | + +## 7.2 SMS contracts, packages and ACs + +### 7.2.1 smsSSF/gsmSCF ASN.1 module + +``` + +CAP-smsSSF-gsmSCF-pkgs-contracts-ac {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-smsSSF-gsmSCF-pkgs-contracts-ac(106) version8(7)} + +``` + +``` + +DEFINITIONS ::= BEGIN + +``` + +``` + +-- This module specifies the Operation Packages, Contracts, Application Contexts +-- and Abstract Syntaxes used for the smsSSF - gsmSCF interface, for the + +``` + +``` + +-- control of MO-SMS and MT-SMS. + +-- The table in subclause 2.1 lists the specifications that contain the modules +-- that are used by CAP. + +IMPORTS + + PARAMETERS-BOUND, + cAPSpecificBoundSet +FROM CAP-classes classes +-- Elements that exist in cAPSpecificBoundSet in Rel-5 are not changed in Rel-6. As a +-- result, the value range of data type definitions in Rel-5 are not changed in Rel-6. + + CONTRACT, + OPERATION-PACKAGE, + OPERATION +FROM Remote-Operations-Information-Objects ros-InformationObjects + + TCMessage {} +FROM TCAPMessages tc-Messages + + APPLICATION-CONTEXT, + dialogue-abstract-syntax +FROM TC-Notation-Extensions tc-NotationExtensions + + connectSMS{}, + continueSMS, + eventReportSMS{}, + furnishChargingInformationSMS{}, + initialDPSMS{}, + releaseSMS, + requestReportSMSEvent{}, + resetTimerSMS{} +FROM CAP-SMS-ops-args sms-Operations +-- Object Identifier 'sms-Operations' is updated to version8(7) in Rel-6. As a result, +-- the present module, 'CAP-smsSSF-gsmSCF-pkgs-contracts-ac', IMPORTS CAP Operation +-- definitions from CAP-SMS-ops-args version8(7). Operation definitions are used in the +-- ABSTRACT SYNTAX definitions and in the OPERATION PACKAGE definitions. + + id-ac-cap3-sms-AC, + id-ac-cap4-sms-AC, +-- The APPLICATION-CONTEXT Identifiers for CAP V3 and CAP V4 for SMS in Rel-6 are the same as +-- in Rel-5. + + id-cap3SmsSsfTogsmScf, + id-cap4SmsSsfTogsmScf, +-- The CONTRACT Identifiers for CAP V3 and CAP V4 for SMS in Rel-6 are the same as in Rel-5. + + id-package-smsActivation, + id-package-smsConnect, + id-package-smsContinue, + id-package-smsRelease, + id-package-smsEventHandling, + id-package-smsBilling, + id-package-smsTimer, +-- The OPERATION-PACKAGE Identifiers for CAP V3 and CAP V4 for SMS in Rel-6 are the same as +-- in Rel-5. + + sms-Operations, +-- Object Identifier sms-Operations is updated to version8(7) in Rel-6. As a result, the present +-- module, 'CAP-smsSSF-gsmSCF-pkgs-contracts-ac', IMPORTS Rel-6 versions of the CAP Operation +-- definitions. + + tc-NotationExtensions, + tc-Messages, + ros-InformationObjects, + classes, + + id-as-smsSSF-gsmSCF-AS +-- The ABSTRACT-SYNTAX Identifiers for CAP V3 and CAP V4 for SMS in Rel-6 are the same as +-- in Rel-5. + +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} + +; + +-- Application Contexts +``` + +``` +-- Rel-6 uses the same Application Context versions for SMS as Rel-5. The CONTRACT and ABSTRACT +-- SYNTAXES for SMS are defined in Rel-6. +``` + +``` +-- Refer to ITU-T Recommendation Q.775 for the formal definition of APPLICATION-CONTEXT. +-- The structured DIALOGUE MODE is defined in ITU-T Recommendation Q.771; the +-- dialogue-abstract-syntax ABSTRACT SYNTAX is defined in ITU-T Recommendation Q.775. +``` + +``` +cap3-sms-AC APPLICATION-CONTEXT ::= { +``` + +``` + CONTRACT cap3SMS + DIALOGUE MODE structured + ABSTRACT SYNTAXES {dialogue-abstract-syntax | + sms-AbstractSyntax} + APPLICATION CONTEXT NAME id-ac-cap3-sms-AC} +``` + +``` +-- This application context shall be used for CAMEL support of MO-SMS. +``` + +``` +-- 'cap3SMS' and 'sms-AbstractSyntax' are defined in the present module. +``` + +``` +cap4-sms-AC APPLICATION-CONTEXT ::= { +``` + +``` + CONTRACT cap4SMS + DIALOGUE MODE structured + ABSTRACT SYNTAXES {dialogue-abstract-syntax | + sms-AbstractSyntax} + APPLICATION CONTEXT NAME id-ac-cap4-sms-AC} +``` + +``` +-- This application context shall be used for CAMEL support of MT-SMS. +``` + +``` +-- 'cap4SMS' and 'sms-AbstractSyntax' are defined in the present module. +``` + +``` +-- Contracts +``` + +``` +-- The CONTRACT definitions for SMS in Rel-6 use OPERATION-PACKAGE definitions which are +``` + +``` +-- defined in Rel-6. +``` + +``` +cap3SMS CONTRACT ::= { +``` + +``` +-- dialogue initiated by gprsSSF or gsmSSF with InitialDPSMS Operation +``` + +``` + INITIATOR CONSUMER OF {smsActivationPackage {CAPSpecificBoundSet}} + RESPONDER CONSUMER OF {smsConnectPackage {CAPSpecificBoundSet} | + smsReleasePackage | + smsEventHandlingPackage {CAPSpecificBoundSet} | + smsTimerPackage {CAPSpecificBoundSet} | + smsBillingPackage {CAPSpecificBoundSet} | + smsProcessingPackage} +``` + +``` + ID id-cap3SmsSsfTogsmScf} +``` + +``` +-- The OPERATION-PACKAGES are defined in the present module. +``` + +``` +cap4SMS CONTRACT ::= { +``` + +``` +-- dialogue initiated by gprsSSF or gsmSSF with InitialDPSMS Operation +``` + +``` + INITIATOR CONSUMER OF {smsActivationPackage {CAPSpecificBoundSet}} + RESPONDER CONSUMER OF {smsConnectPackage {CAPSpecificBoundSet} | + smsReleasePackage | + smsEventHandlingPackage {CAPSpecificBoundSet} | + smsTimerPackage {CAPSpecificBoundSet} | + smsBillingPackage {CAPSpecificBoundSet} | + smsProcessingPackage } +``` + +``` + ID id-cap4SmsSsfTogsmScf} +``` + +``` +-- The OPERATION-PACKAGES are defined in the present module. +``` + +``` +-- Operation Packages +``` + +``` +-- The OPERATION-PACKAGE definitions for SMS in Rel-6 use Operation definitions from Rel-6. The +``` + +``` +-- OPERATION definitions are IMPORTED from CAP-SMS-ops-args. +``` + +``` +smsActivationPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { +``` + +``` + CONSUMER INVOKE {initialDPSMS {bound}} + ID id-package-smsActivation} +``` + +``` +smsConnectPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { +``` + +``` + CONSUMER INVOKE {connectSMS {bound}} + ID id-package-smsConnect} +``` + +``` +smsProcessingPackage OPERATION-PACKAGE ::= { +``` + +``` + CONSUMER INVOKE {continueSMS} + ID id-package-smsContinue} +``` + +``` +smsReleasePackage OPERATION-PACKAGE ::= { +``` + +``` + CONSUMER INVOKE {releaseSMS} +``` + +``` + +ID id-package-smsRelease} + +smsEventHandlingPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {requestReportSMSEvent {bound}} + SUPPLIER INVOKES {eventReportSMS {bound}} + ID id-package-smsEventHandling} + +smsBillingPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {furnishChargingInformationSMS {bound}} + ID id-package-smsBilling} + +smsTimerPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {resetTimerSMS {bound}} + ID id-package-smsTimer} + +-- Abstract Syntaxes + +-- SmsInvokable and SmsReturnable use OPERATION definitions with version8(7). As a result, +-- Generic-sms-PDUs uses version8(7) OPERATION definitions. As a subsequent result, +-- sms-AbstractSyntax uses version8(7) OPERATION definitions. That ABSTRACT-SYNTAX is used +-- in the cap3-sms-AC APPLICATION-CONTEXT definition and in the and cap4-sms-AC APPLICATION- +-- CONTEXT definition (CAP from smsSSF to gsmSCF). + +sms-AbstractSyntax ABSTRACT-SYNTAX ::= { + Generic-sms-PDUs + IDENTIFIED BY id-as-smsSSF-gsmSCF-AS } +-- 'Generic-sms-PDUs' is defined in the present module. + +Generic-sms-PDUs ::= TCMessage {{SmsInvokable}, + {SmsReturnable}} +-- 'SmsInvokable' and 'SmsReturnable' are defined in the present module. + +SmsInvokable OPERATION ::= { + connectSMS {cAPSpecificBoundSet} | + eventReportSMS {cAPSpecificBoundSet} | + furnishChargingInformationSMS {cAPSpecificBoundSet} | + initialDPSMS {cAPSpecificBoundSet} | + requestReportSMSEvent {cAPSpecificBoundSet} | + resetTimerSMS {cAPSpecificBoundSet}} +-- The OPERATION definitions are IMPORTED from CAP-SMS-ops-args version8(7). + +SmsReturnable OPERATION ::= { + connectSMS {cAPSpecificBoundSet} | + continueSMS | + furnishChargingInformationSMS {cAPSpecificBoundSet} | + initialDPSMS {cAPSpecificBoundSet} | + releaseSMS | + requestReportSMSEvent {cAPSpecificBoundSet} | + resetTimerSMS {cAPSpecificBoundSet}} +-- The OPERATION definitions are IMPORTED from CAP-SMS-ops-args version8(7). + +END + +``` + +## 8 GPRS Control + +### 8.1 gsmSCF/gprsSSF operations and arguments + +``` + +CAP-gprsSSF-gsmSCF-ops-args {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) + umts-network(1) modules(3) cap-GPRS-ops-args(107) version8(7)} +-- Module CAP-gprsSSF-gsmSCF-ops-args is updated to version8(7) for Rel-6. The OPERATION +-- definitions in this module are not modified, compared to Rel-5. + +``` + +``` +DEFINITIONS IMPLICIT TAGS ::= BEGIN +``` + +``` + +-- This module contains the operations and operation arguments used for the +-- gprsSSF - gsmSCF interface, for the control of GPRS. + +-- The table in subclause 2.1 lists the specifications that contain the modules +-- that are used by CAP. + +``` + +``` +IMPORTS +``` + +``` + errortypes, +``` + +``` + datatypes, + operationcodes, + classes, + ros-InformationObjects +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} + + OPERATION +FROM Remote-Operations-Information-Objects ros-InformationObjects + + ServiceKey +FROM CS1-DataTypes {itu-t(0) identified-organization(4) etsi(0) inDomain(1) in-network(1) +modules(0) cs1-datatypes(2) version1(0)} + + MiscCallInfo +FROM CS2-datatypes {itu-t(0) identified-organization(4) etsi(0) inDomain(1) in-network(1) +cs2(20) modules(0) in-cs2-datatypes(0) version1(0)} + + IMEI, + IMSI, + ISDN-AddressString +FROM MAP-CommonDataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-CommonDataTypes(18) version12(12)} + + GPRSChargingID, + GPRSMSClass, + GSN-Address, + RAIdentity +FROM MAP-MS-DataTypes {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +gsm-Network(1) modules(3) map-MS-DataTypes(11) version12(12)} + + PARAMETERS-BOUND +FROM CAP-classes classes + + opcode-activityTestGPRS, + opcode-applyChargingGPRS, + opcode-applyChargingReportGPRS, + opcode-cancelGPRS, + opcode-connectGPRS, + opcode-continueGPRS, + opcode-entityReleasedGPRS, + opcode-eventReportGPRS, + opcode-furnishChargingInformationGPRS, + opcode-initialDPGPRS, + opcode-releaseGPRS, + opcode-requestReportGPRSEvent, + opcode-resetTimerGPRS, + opcode-sendChargingInformationGPRS +FROM CAP-operationcodes operationcodes +-- The CAP Operation identifiers for CAP V3 for GPRS in Rel-6 are the same as the CAP Operation +-- identifiers for CAP V3 for GPRS in Rel-5. + + AccessPointName {}, + GPRSCause {}, + ChargingCharacteristics, + ChargingResult, + ChargingRollOver, + EndUserAddress, + Extensions, + FCIGPRSBillingChargingCharacteristics, + GPRSEventSpecificInformation {}, + GPRSEvent, + GPRSEventType, + LocationInformationGPRS, + PDPID, + PDPInitiationType, + QualityOfService, + SCIGPRSBillingChargingCharacteristics {}, + SGSNCapabilities, + TimeAndTimezone {}, + TimerID, + TimerValue +FROM CAP-datatypes datatypes +-- For Rel-6, the CAP-datatypes module is updated to version8(7); Object Identifier 'datatypes' +-- is also updated to version8(7). As a result, the present module uses Rel-6 data type definitions. + + missingCustomerRecord, + missingParameter, +``` + +``` + +parameterOutOfRange, +systemFailure, +taskRefused, +unexpectedComponentSequence, +unexpectedDataValue, +unexpectedParameter, +unknownPDPID +FROM CAP-errortypes errortypes +-- For Rel-6, the CAP-errortypes module is updated to version8(7); Object Identifier +-- 'errortypes' is also updated to version8(7). As a result, the present module uses Rel-6 +-- error type definitions. + +; + +activityTestGPRS OPERATION ::= { + RETURN RESULT TRUE + CODE opcode-activityTestGPRS} +-- Direction: gsmSCF -> gprsSSF, Timer: Tatg +-- This operation is used to check for the continued existence of a relationship between the gsmSCF +-- and gprsSSF. If the relationship is still in existence, then the gprsSSF will respond. If no +-- reply is received, then the gsmSCF will assume that the gprsSSF has failed in some way +-- and will take the appropriate action. + +applyChargingGPRS OPERATION ::= { + ARGUMENT ApplyChargingGPRSArg + RETURN RESULT FALSE + ERRORS {missingParameter | + unexpectedComponentSequence | + unexpectedParameter | + unexpectedDataValue | + parameterOutOfRange | + systemFailure | + taskRefused | + unknownPDPID} + CODE opcode-applyChargingGPRS} +-- Direction gsmSCF -> gprsSSF, Timer Tacg +-- This operation is used for interacting from the gsmSCF with the gprsSSF CSE-controlled +-- GPRS session or PDP Context charging mechanism. + +ApplyChargingGPRSArg ::= SEQUENCE { + chargingCharacteristics [0] ChargingCharacteristics, + tariffSwitchInterval [1] INTEGER (1..86400) OPTIONAL, + pDPID [2] PDPID OPTIONAL, + ... +} +-- tariffSwitchInterval is measured in 1 second units. + +applyChargingReportGPRS OPERATION ::= { + ARGUMENT ApplyChargingReportGPRSArg + RETURN RESULT TRUE + ERRORS {missingParameter | + unexpectedComponentSequence | + unexpectedParameter | + unexpectedDataValue | + parameterOutOfRange | + systemFailure | + taskRefused | + unknownPDPID} + CODE opcode-applyChargingReportGPRS} +-- Direction gprsSSF -> gsmSCF, Timer Tacrg +-- The ApplyChargingReportGPRS operation provides the feedback from the gprsSSF to the gsmSCF +-- CSE-controlled GPRS session charging mechanism. + +ApplyChargingReportGPRSArg ::= SEQUENCE { + chargingResult [0] ChargingResult, + qualityOfService [1] QualityOfService OPTIONAL, + active [2] BOOLEAN DEFAULT TRUE, + pDPID [3] PDPID OPTIONAL, + ..., + chargingRollOver [4] ChargingRollOver OPTIONAL +} + +cancelGPRS OPERATION ::= { + ARGUMENT CancelGPRSArg + RETURN RESULT FALSE + ERRORS {missingParameter | + taskRefused | + +``` + +``` + + unknownPDPID} + CODE opcode-cancelGPRS} +-- Direction: gsmSCF -> gprsSSF, Timer: Tcag +-- This generic operation cancels all previous requests, +-- i.e. all EDPs and reports can be cancelled by the gsmSCF. + +CancelGPRSArg ::= SEQUENCE { + pDPID [0] PDPID OPTIONAL, + ... +} + +connectGPRS {PARAMETERS-BOUND: bound} OPERATION ::= { + ARGUMENT ConnectGPRSArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + unknownPDPID | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter} + CODE opcode-connectGPRS} +-- Direction: gsmSCF -> gprsSSF, Timer: Tcong +-- This operation is used to modify the Access Point Name used when establishing a PDP Context. + +ConnectGPRSArg {PARAMETERS-BOUND: bound} ::= SEQUENCE { + accessPointName [0] AccessPointName {bound}, + pDPID [1] PDPID OPTIONAL, + ... +} + +continueGPRS OPERATION ::= { + ARGUMENT ContinueGPRSArg + RETURN RESULT FALSE + ERRORS {missingParameter | + unknownPDPID | + unexpectedDataValue} + CODE opcode-continueGPRS} +-- Direction: gsmSCF -> gprsSSF, Timer: Tcueg +-- This operation is used to request the gprsSSF to proceed with processing at the DP at +-- which it previously suspended processing to await gsmSCF instructions (i.e., proceed to +-- the next point in processing in the Attach/Detach state model or PDP Context +-- state model) substituting new data from the gsmSCF. + +ContinueGPRSArg ::= SEQUENCE { + pDPID [0] PDPID OPTIONAL, + ... +} + +entityReleasedGPRS {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT EntityReleasedGPRSArg {bound} + RETURN RESULT TRUE + ERRORS {missingParameter | + taskRefused | + unknownPDPID} + CODE opcode-entityReleasedGPRS} +-- Direction: gprsSSF -> gsmSCF, Timer: Terg +-- This operation is used when the GPRS Session is detached or a PDP Context is disconnected and +-- the associated event is not armed for reporting. +-- The usage of this operation is independent of the functional entity that initiates the Detach +-- or PDP Context Disconnection and is independent of the cause of the Detach or PDP Context +-- Disconnect. + +EntityReleasedGPRSArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + gPRSCause [0] GPRSCause {bound}, + pDPID [1] PDPID OPTIONAL, + ... +} + +eventReportGPRS {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT EventReportGPRSArg {bound} + RETURN RESULT TRUE + ERRORS {unknownPDPID} + CODE opcode-eventReportGPRS} +-- Direction gprsSSF -> gsmSCF, Timer Tereg +-- This operation is used to notify the gsmSCF of a GPRS session or PDP context related + +``` + +``` + +-- events (e.g. PDP context activation) previously requested by the gsmSCF in a +-- RequestReportGPRSEventoperation. + +EventReportGPRSArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + gPRSEventType [0] GPRSEventType, + miscGPRSInfo [1] MiscCallInfo DEFAULT {messageType request}, + gPRSEventSpecificInformation [2] GPRSEventSpecificInformation {bound} OPTIONAL, + pDPID [3] PDPID OPTIONAL, + ... +} + +furnishChargingInformationGPRS {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT FurnishChargingInformationGPRSArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownPDPID} + CODE opcode-furnishChargingInformationGPRS} +-- Direction: gsmSCF -> gprsSSF, Timer: Tfcig +-- This operation is used to request the gprsSSF to generate, register a logical record or to +-- include some information in the default logical GPRS record. +-- The registered logical record is intended for off line charging of the GPRS session +-- or PDP Context. + +FurnishChargingInformationGPRSArg {PARAMETERS-BOUND : bound} ::= + FCIGPRSBillingChargingCharacteristics{bound} + +initialDPGPRS {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT InitialDPGPRSArg {bound} + RETURN RESULT FALSE + ERRORS {missingCustomerRecord | + missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter} + CODE opcode-initialDPGPRS} +-- Direction gprsSSF -> gsmSCF, Timer Tidpg +-- This operation is used by the gprsSSF when a trigger is detected at a DP in the GPRS state +-- machines to request instructions from the gsmSCF + +InitialDPGPRSArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + serviceKey [0] ServiceKey, + gPRSEventType [1] GPRSEventType, + mSISDN [2] ISDN-AddressString, + iMSI [3] IMSI, + timeAndTimeZone [4] TimeAndTimezone {bound}, + gPRSMSClass [5] GPRSMSClass OPTIONAL, + endUserAddress [6] EndUserAddress {bound} OPTIONAL, + qualityOfService [7] QualityOfService OPTIONAL, + accessPointName [8] AccessPointName{bound} OPTIONAL, + routeingAreaIdentity [9] RAIdentity OPTIONAL, + chargingID [10] GPRSChargingID OPTIONAL, + sGSNCapabilities [11] SGSNCapabilities OPTIONAL, + locationInformationGPRS [12] LocationInformationGPRS OPTIONAL, + pDPInitiationType [13] PDPInitiationType OPTIONAL, + extensions [14] Extensions {bound} OPTIONAL, + ... + gGSNAddress [15] GSN-Address OPTIONAL, + secondaryPDP-context [16] NULL OPTIONAL, + iMEI [17] IMEI OPTIONAL +} +-- The RouteingAreaIdentity parameter is not used. +-- The receiving entity shall ignore RouteingAreaIdentity if received. +-- The RouteingAreaIdentity is conveyed in the LocationInformationGPRS parameter. +-- The CSGInformation is conveyed in the LocationInformationGPRS parameter. The encoding of the +-- parameter is as defined in 3GPP TS 29.002 [11]. + +releaseGPRS {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT ReleaseGPRSArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + taskRefused | + +``` + +``` + + unknownPDPID} + CODE opcode-releaseGPRS} +-- Direction: gsmSCF -> gprsSSF, Timer: Trg +-- This operation is used to tear down an existing GPRS session or PDP Context at any phase. + +ReleaseGPRSArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + gprsCause [0] GPRSCause {bound}, + pDPID [1] PDPID OPTIONAL, + ... +} + +requestReportGPRSEvent {PARAMETERS-BOUND : bound} OPERATION ::= { + ARGUMENT RequestReportGPRSEventArg {bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownPDPID} + CODE opcode-requestReportGPRSEvent} +-- Direction: gsmSCF -> gprsSSF, Timer: Trrqe +-- This operation is used to request the gprsSSF to monitor for an event (e.g., GPRS events +-- such as attach or PDP Context activation), then send a notification back to the +-- gsmSCF when the event is detected. + +RequestReportGPRSEventArg {PARAMETERS-BOUND : bound} ::= SEQUENCE { + gPRSEvent [0] SEQUENCE SIZE (1..bound.&numOfGPRSEvents) OF GPRSEvent, + pDPID [1] PDPID OPTIONAL, + ... +} +-- Indicates the GPRS related events for notification. + +resetTimerGPRS OPERATION ::= { + ARGUMENT ResetTimerGPRSArg + RETURN RESULT FALSE + ERRORS {missingParameter | + parameterOutOfRange | + taskRefused | + unexpectedComponentSequence | + unexpectedDataValue | + unexpectedParameter | + unknownPDPID} + CODE opcode-resetTimerGPRS} +-- Direction: gsmSCF -> gprsSSF, Timer: Trtg +-- This operation is used to request the gprsSSF to refresh an application timer in the gprsSSF. + +ResetTimerGPRSArg ::= SEQUENCE { + timerID [0] TimerID DEFAULT tssf, + timervalue [1] TimerValue, + ... +} + +sendChargingInformationGPRS {PARAMETERS-BOUND: bound} OPERATION ::= { + ARGUMENT SendChargingInformationGPRSArg { bound} + RETURN RESULT FALSE + ERRORS {missingParameter | + unexpectedComponentSequence | + unexpectedParameter | + parameterOutOfRange | + systemFailure | + taskRefused | + unexpectedDataValue | + unknownPDPID} + CODE opcode-sendChargingInformationGPRS} +-- Direction: gsmSCF -> gprsSSF, Timer: Tscig +-- This operation is used to instruct the gprsSSF on the charging information which the +-- gprsSSF shall send to the Mobile Station by means of GSM access signalling. + +SendChargingInformationGPRSArg {PARAMETERS-BOUND: bound} ::= SEQUENCE { + scIGPRSBillingChargingCharacteristics [0] SCIGPRSBillingChargingCharacteristics {bound}, + ... +} + +END + +``` + +### 8.1.1 GPRS Reference Number + +``` + +CAP-GPRS-ReferenceNumber {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-dialogueInformation(111) version8(7)} +-- Module CAP-GPRS-ReferenceNumber is updated to version8(7) for Rel-6. The definitions +-- in this module are not modified, compared to Rel-5. + +DEFINITIONS ::= BEGIN + +EXPORTS + id-CAP-GPRS-ReferenceNumber, + cAP-GPRS-ReferenceNumber-Abstract-Syntax; + +IMPORTS + + Integer4 +FROM CS1-DataTypes {itu-t(0) identified-organization(4) etsi(0) inDomain(1) in-network(1) +modules(0) cs1-datatypes(2) version1(0)} +; + +id-CAP-GPRS-ReferenceNumber OBJECT IDENTIFIER ::= {itu-t(0) identified-organization(4) etsi(0) +mobileDomain(0) umts-network(1) as(1) cap-GPRS-ReferenceNumber(5) version3(2)} + +CAP-GPRS-ReferenceNumber-Abstract-Syntax ABSTRACT-SYNTAX ::= {CAP-GPRS-ReferenceNumber IDENTIFIED BY +id-CAP-GPRS-ReferenceNumber} + +CAP-GPRS-ReferenceNumber ::= SEQUENCE { + destinationReference [0] Integer4 OPTIONAL, + originationReference [1] Integer4 OPTIONAL +} +-- This parameter is used to identify the relationship between SGSN and the gsmSCF. + +END -- of CAP-GPRS-ReferenceNumber + +``` + +### 8.1.2 Operation timers + +The following value ranges apply for operation specific timers in CAP: + +| | | +|---------|------------------------| +| short: | 1 to 20 seconds; | +| medium: | 1 to 60 seconds; | +| long: | 1 second to 30 minutes | + +Table 8-1 lists all operation timers and the value range for each timer. The definitive value for each operation timer may be network specific and has to be defined by the network operator. + +**Table 8-1: Operation timers and their value range** + +| Operation Name | Timer | value | +|--------------------------------|-------------------|-------| +| ActivityTestGPRST | T atg | Short | +| ApplyChargingGPRS | T acg | Short | +| ApplyChargingReportGPRS | T acrg | Short | +| CancelGPRS | T cag | Short | +| ConnectGPRS | T cong | Short | +| ContinueGPRS | T cueg | Short | +| EntityReleasedGPRS | T erg | Short | +| EventReportGPRS | T ereg | Short | +| FurnishChargingInformationGPRS | T fcig | Short | +| InitialDPGPRS | T idpg | Short | +| ReleaseGPRS | T trg | Short | +| RequestReportGPRSEvent | T rrqe | Short | +| ResetTimerGPRS | T rtg | Short | +| SendChargingInformationGPRS | T scig | Short | + +## 8.2 gsmSCF/gprsSSF contracts, packages and ACs + +### 8.2.1 gprsSSF/gsmSCF ASN.1 module + +``` + +CAP-gprsSSF-gsmSCF-pkgs-contracts-ac { itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-gprsSSF-gsmSCF-pkgs-contracts-ac(108) version8(7) } +DEFINITIONS ::= BEGIN + +-- This module specifies the Operation Packages, Contracts, Application Contexts +-- and Abstract Syntaxes used for the gprsSSF - gsmSCF interface, for the +-- control of GPRS. + +-- The table in subclause 2.1 lists the specifications that contain the modules +-- that are used by CAP. + +IMPORTS + + PARAMETERS-BOUND, + cAPSpecificBoundSet +FROM CAP-classes classes +-- Elements that exist in cAPSpecificBoundSet in Rel-5 are not changed in Rel-6. As a +-- result, the value range of data type definitions in Rel-5 are not changed in Rel-6. + + CONTRACT, + OPERATION-PACKAGE, + OPERATION +FROM Remote-Operations-Information-Objects ros-InformationObjects + + TCMessage { } +FROM TCAPMessages tc-Messages + + APPLICATION-CONTEXT, + dialogue-abstract-syntax +FROM TC-Notation-Extensions tc-NotationExtensions + + activityTestGPRS, + applyChargingGPRS, + applyChargingReportGPRS, + cancelGPRS, + connectGPRS {}, + continueGPRS, + entityReleasedGPRS {}, + furnishChargingInformationGPRS {}, + initialDPGPRS {}, + releaseGPRS {}, + eventReportGPRS {}, + requestReportGPRSEvent {}, + +``` + +``` + + resetTimerGPRS, + sendChargingInformationGPRS {} +FROM CAP-gprsSSF-gsmSCF-ops-args gprsSSF-gsmSCF-Operations + + id-ac-CAP-gprsSSF-gsmSCF-AC, + id-ac-CAP-gsmSCF-gprsSSF-AC, +-- The APPLICATION-CONTEXT Object Identifiers for CAP V3 for GPRS in Rel-6 are the same as for +-- CAP V3 for GPRS in Rel-5. + + id-capGprsSsfToGsmScf, + id-capGsmScfToGprsSsf, +-- The CONTRACT Object Identifiers for CAP V3 for GPRS are updated in Rel-6. + + id-as-gprsSSF-gsmSCF-AS, + id-as-gsmSCF-gprsSSF-AS, +-- The ABSTRACT-SYNTAX Object Identifiers for CAP V3 for GPRS are updated in Rel-6. + + id-package-gprsScfActivation, + id-package-gprsConnect, + id-package-gprsContinue, + id-package-gprsRelease, + id-package-gprsEventHandling, + id-package-gprsExceptionInformation, + id-package-gprsTimer, + id-package-gprsBilling, + id-package-gprsCharging, + id-package-gprsChargeAdvice, + id-package-gprsActivityTest, + id-package-gprsCancel, +-- The OPERATION-PACKAGE Object Identifiers for CAP V3 for GPRS are updated in Rel-6. + + classes, + ros-InformationObjects, + tc-Messages, + tc-NotationExtensions, + + gprsSSF-gsmSCF-Operations +-- Object Identifier 'gprsSSF-gsmSCF-Operations' is updated for Rel-6. + +FROM CAP-object-identifiers {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) +umts-network(1) modules(3) cap-object-identifiers(100) version8(7)} + +; + +-- Application Contexts + +-- The APPLICATION-CONTEXT definitions for CAP V3 for GPRS are updated in Rel-6. +-- However, the APPLICATION-CONTEXT definitions for CAP V3 for GPRS in Rel-6 use the same +-- Object Identifier for APPLICATION CONTEXT NAME as CAP V3 for GPRS in Rel-5. + +-- Refer to ITU-T Recommendation Q.775 for the formal definition of APPLICATION-CONTEXT. +-- The structured DIALOGUE MODE is defined in ITU-T Recommendation Q.771; the +-- dialogue-abstract-syntax ABSTRACT SYNTAX is defined in ITU-T Recommendation Q.775. + +cap-gprssf-scfAC APPLICATION-CONTEXT ::= { + CONTRACT capGprsSsfToScf + DIALOGUE MODE structured + ABSTRACT SYNTAXES {dialogue-abstract-syntax | + gprsSSF-gsmSCFAbstractSyntax} + APPLICATION CONTEXT NAME id-ac-CAP-gprsSSF-gsmSCF-AC} +-- 'capGprsSsfToScf' and 'gprsSSF-gsmSCFAbstractSyntax' are defined in the present +-- module. + +cap-gsmscf-gprssfAC APPLICATION-CONTEXT ::= { + CONTRACT capGsmScfToGprsSsf + DIALOGUE MODE structured + ABSTRACT SYNTAXES {dialogue-abstract-syntax | + gsmSCF-gprsSSFAbstractSyntax} + APPLICATION CONTEXT NAME id-ac-CAP-gsmSCF-gprsSSF-AC} +-- 'capGsmScfToGprsSsf' and 'gsmSCF-gprsSSFAbstractSyntax' are defined in the present +-- module. + +-- Contracts +-- The CONTRACT definitions for CAP V3 for GPRS are updated in Rel-6. + +capGprsSsfToScf CONTRACT ::= { +-- dialogue initiated by gprsSSF with InitialDPGPRS, ApplyChargingReportGPRS, +``` + +``` +-- EntityReleasedGPRS and EventReportGPRS Operations +INITIATOR CONSUMER OF {gprsScfActivationPackage {CAPSSpecificBoundSet}} | + gprsEventHandlingPackage {CAPSSpecificBoundSet} | + gprsChargingPackage | + gprsExceptionInformationPackage {CAPSSpecificBoundSet}} +RESPONDER CONSUMER OF {gprsConnectPackage {CAPSSpecificBoundSet}} | + gprsProcessingPackage | + gprsReleasePackage {CAPSSpecificBoundSet} | + gprsEventHandlingPackage {CAPSSpecificBoundSet} | + gprsTimerPackage | + gprsBillingPackage {CAPSSpecificBoundSet} | + gprsChargingPackage | + gprsCancelPackage | + gprsChargeAdvicePackage {CAPSSpecificBoundSet}} +ID + id-capGprsSsfToGsmScf +-- The OPERATION-PACKAGES are defined in the present module. + +capGsmScfToGprsSsf CONTRACT ::= { +-- dialogue initiated by gsmSCF with ApplyChargingGPRS, ActivityTestGPRS, +-- CancelGPRS, FurnishChargingInformationGPRS, ReleaseGPRS, +-- RequestReportGPRSEvent and SendChargingInformationGPRS Operations +INITIATOR CONSUMER OF {gprsReleasePackage {CAPSSpecificBoundSet}} | + gprsEventHandlingPackage {CAPSSpecificBoundSet} | + gprsBillingPackage {CAPSSpecificBoundSet} | + gprsChargingPackage | + gprsActivityTestPackage | + gprsCancelPackage | + gprsChargeAdvicePackage {CAPSSpecificBoundSet}} +ID + id-capGsmScfToGprsSsf +-- The OPERATION-PACKAGES are defined in the present module. + +-- Operation Packages + +-- The OPERATION-PACKAGE definitions for CAP V3 for GPRS are updated in Rel-6. + +gprsScfActivationPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {initialDPGPRS {bound}} + ID id-package-gprsScfActivation} + +gprsConnectPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {connectGPRS {bound}} + ID id-package-gprsConnect} + +gprsProcessingPackage OPERATION-PACKAGE ::= { + CONSUMER INVOKES {continueGPRS } + ID id-package-gprsContinue} + +gprsReleasePackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {releaseGPRS {bound}} + ID id-package-gprsRelease} + +gprsEventHandlingPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {requestReportGPRSEvent {bound}} + SUPPLIER INVOKES {eventReportGPRS {bound}} + ID id-package-gprsEventHandling} + +gprsExceptionInformationPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {entityReleasedGPRS {bound}} + ID id-package-gprsExceptionInformation} + +gprsTimerPackage OPERATION-PACKAGE ::= { + CONSUMER INVOKES {resetTimerGPRS } + ID id-package-gprsTimer} + +gprsBillingPackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {furnishChargingInformationGPRS {bound}} + ID id-package-gprsBilling} + +gprsChargingPackage OPERATION-PACKAGE ::= { + CONSUMER INVOKES {applyChargingGPRS} + SUPPLIER INVOKES {applyChargingReportGPRS} + ID id-package-gprsCharging} + +gprsChargeAdvicePackage {PARAMETERS-BOUND : bound} OPERATION-PACKAGE ::= { + CONSUMER INVOKES {sendChargingInformationGPRS {bound}} + ID id-package-gprsChargeAdvice} +``` + +``` +gprsActivityTestPackage OPERATION-PACKAGE ::= { + CONSUMER INVOKES {activityTestGPRS} + ID id-package-gprsActivityTest} + +gprsCancelPackage OPERATION-PACKAGE ::= { + CONSUMER INVOKES {cancelGPRS } + ID id-package-gprsCancel} + +-- Abstract Syntaxes + +-- The ABSTRACT-SYNTAX definitions for CAP V3 for GPRS are updated in Rel-6. + +gprsSSF-gsmSCFAbstractSyntax ABSTRACT-SYNTAX ::= { + GenericGprsSSF-gsmSCF-PDUs + IDENTIFIED BY id-as-gprsSSF-gsmSCF-AS} +-- 'GenericGprsSSF-gsmSCF-PDUs' is defined in the present module. + +GenericGprsSSF-gsmSCF-PDUs ::= TCMessage {{GprsSsfToGsmScfInvokable}, + {GprsSsfToGsmScfReturnable}} +-- 'GprsSsfToGsmScfInvokable' and 'GprsSsfToGsmScfReturnable' are defined in the present module. + +GprsSsfToGsmScfInvokable OPERATION ::= { + activityTestGPRS | + applyChargingGPRS | + applyChargingReportGPRS | + cancelGPRS | + connectGPRS {CAPSpecificBoundSet} | + entityReleasedGPRS {CAPSpecificBoundSet} | + eventReportGPRS {CAPSpecificBoundSet} | + furnishChargingInformationGPRS {CAPSpecificBoundSet} | + initialDPGPRS {CAPSpecificBoundSet} | + releaseGPRS {CAPSpecificBoundSet} | + requestReportGPRSEvent {CAPSpecificBoundSet} | + resetTimerGPRS | + sendChargingInformationGPRS {CAPSpecificBoundSet}} + +GprsSsfToGsmScfReturnable OPERATION ::= { + activityTestGPRS | + applyChargingGPRS | + applyChargingReportGPRS | + cancelGPRS | + connectGPRS {CAPSpecificBoundSet} | + continueGPRS | + entityReleasedGPRS {CAPSpecificBoundSet} | + furnishChargingInformationGPRS {CAPSpecificBoundSet} | + initialDPGPRS {CAPSpecificBoundSet} | + releaseGPRS {CAPSpecificBoundSet} | + requestReportGPRSEvent {CAPSpecificBoundSet} | + resetTimerGPRS | + sendChargingInformationGPRS {CAPSpecificBoundSet}} + +gsmSCF-gprsSSFAbstractSyntax ABSTRACT-SYNTAX ::= { + GenericGsmSCF-gprsSSF-PDUs + IDENTIFIED BY id-as-gsmSCF-gprsSSF-AS} +-- 'GenericGsmSCF-gprsSSF-PDUs' is defined in the present module. + +GenericGsmSCF-gprsSSF-PDUs ::= TCMessage {{GsmScfToGprsSsfInvokable}, + {GsmScfToGprsSsfReturnable}} +-- 'GsmScfToGprsSsfInvokable' and 'GsmScfToGprsSsfReturnable' are defined in the present module. + +GsmScfToGprsSsfInvokable OPERATION ::= { + activityTestGPRS | + applyChargingGPRS | + cancelGPRS | + furnishChargingInformationGPRS {CAPSpecificBoundSet} | + releaseGPRS {CAPSpecificBoundSet} | + requestReportGPRSEvent {CAPSpecificBoundSet} | + sendChargingInformationGPRS {CAPSpecificBoundSet}} + +GsmScfToGprsSsfReturnable OPERATION ::= { + activityTestGPRS | + applyChargingGPRS | + cancelGPRS | + furnishChargingInformationGPRS {CAPSpecificBoundSet} | + releaseGPRS {CAPSpecificBoundSet} | + requestReportGPRSEvent {CAPSpecificBoundSet} | +``` + +``` +sendChargingInformationGPRS {cAPSpecificBoundSet} +``` + +``` +END +``` + +--- + +## 9 Application Entity procedures + +The description of the application entity procedures for CAMEL Phase 3 can be found in 3GPP TS 23.078 [7]. + +--- + +## 10 Error procedures + +The present clause specifies the generic error procedures for CAP. The error procedure descriptions are divided in two subclauses, subclause 10.1 listing the errors related to CAP Operations and subclause 10.2 listing the errors related to error conditions in the different FEs which are not directly related to the CAP Operations. + +The gsmSSF FSM states, smsSSF FSM states and gprsSSF FSM states which are referred to in the present clause are described in 3GPP TS 23.078 [7]. The CAP Operations PlayAnnouncement, PromptAndCollectUserInfo and SpecializedResourceReport refer to states in the gsmSRF SRSM which are described in ETSI ETS 300 374-1 [24] as well as to states in 3GPP TS 23.078 [7]. + +### 10.1 Operation related error procedures + +The following subclauses specify the generic error handling for the CAP Operation related errors. The errors are defined as Operation Errors in clauses 6, 7 and 8. Errors which have a specific procedure for a CAP Operation are described in clause 11 with the detailed procedure of the related CAP Operation. + +The TC services which are used for reporting CAP Operation Errors are described in subclause 14.1. All Errors which can be detected by the ASN.1 decoder, already may have been detected during the decoding of the TC message and indicated by the TC error indication "MistypedParameter" in the TC-U-Reject. + +#### 10.1.1 Canceled + +##### 10.1.1.1 General Description + +###### 10.1.1.1.1 Error description + +The gsmSRF uses this Error to indicate" to the gsmSCF that the cancellation of a specific CAP Operation, as requested by the gsmSCF, has been successful. The only CAP Operations which may be cancelled are PlayAnnouncement and PromptAndCollectUserInfo. + +##### 10.1.1.2 Operations gsmSCF & gsmSRF + +###### Procedures at responding entity (gsmSRF) + +###### A) Receiving Cancel + +Precondition: SRSM FSM state "User Interaction". + +Postcondition: SRSM FSM state "User Interaction". + +If execution of the indicated CAP Operation has not yet started, then the indicated CAP Operation shall be removed from the buffer. If execution of the indicated CAP Operation is in progress, then the execution of that CAP Operation shall be terminated. If the indicated CAP Operation was already executed, then then this causes a failure ("CancelFailed"). + +###### B) Sending Error "Canceled" + +Precondition: SRSM FSM state "User Interaction". + +Postcondition: SRSM FSM state "User Interaction". + +After returning the Error "Canceled", the gsmSRF FSM remains in the same state. The execution of the indicated PlayAnnouncement or PromptAndCollectUserInfo CAP Operation is aborted. The gsmSRF shall remain + +connected and the next PlayAnnouncement or PromptAndCollectUserInfo CAP Operation, if available, shall be executed. + +## 10.1.2 CancelFailed + +### 10.1.2.1 General description + +#### 10.1.2.1.1 Error description + +The gsmSRF uses this Error to indicate to the gsmSCF that the cancellation of a specific CAP Operation, as requested by the gsmSCF, was not successful. Possible failure reasons are: + +- 0 "unknownOperation", when the InvokeID of the CAP Operation to cancel is not known to the gsmSRF (this may also happen when the CAP Operation has already been completed); +- 1 "tooLate", when the invokeID is known but the execution of the CAP Operation is in a state in which it cannot be canceled anymore. For instance the announcement is finished but the SpecializedResourceReport has not been sent to the gsmSCF yet. The conditions for the occurrence of failure reason "tooLate" are implementation dependent; +- 2 "operationNotCancellable", when the invokeID points to a CAP Operation that the gsmSCF is not allowed to cancel. + +### 10.1.2.2 Operations gsmSCF $\leftarrow$ gsmSRF + +#### **Procedures at responding entity (gsmSRF)** + +A) Receiving Cancel. However, the indicated CAP Operation is not known, or has already been executed or may not be cancelled. This causes a failure, "CancelFailed". + +**Precondition:** SRSM FSM state "User Interaction". + +**Postcondition:** SRSM FSM state "User Interaction" or + SRSM FSM state "Idle". + +B) Sending Error "CancelFailed" + +**Precondition:** SRSM FSM state "User Interaction" or + SRSM FSM state "Idle". + +**Postcondition:** SRSM FSM state "User Interaction" or + SRSM FSM state "Idle". + +After returning the Error "CancelFailed" the gsmSRF FSM remains in the same state. + +## 10.1.3 ETFailed + +### 10.1.3.1 General description + +#### 10.1.3.1.1 Error description + +The gsmSSF uses this Error to indicate to the gsmSCF that the establishment of a temporary connection to an assisting gsmSSF or gsmSRF was not successful (e.g., receiving a "Backwards Release" after sending an ISUP IAM). + +### 10.1.3.2 Operations gsmSCF $\leftarrow$ gsmSSF + +#### **Procedures at responding entity (gsmSSF)** + +A gsmSSF receives EstablishTemporaryConnection from a gsmSCF but the establishment of the connection fails, which results in returning the Error "ETFailed" to the gsmSCF. + +**Precondition:** gsmSSF FSM state "Waiting\_for\_Instructions". + +**Postcondition:** gsmSSF FSM state "Waiting\_for\_Instructions". + +No further error treatment. + +## 10.1.4 ImproperCallerResponse + +### 10.1.4.1 General description + +#### 10.1.4.1.1 Error description + +The gsmSRF uses this Error to indicate to the gsmSCF that the format of the user input has been checked by the gsmSRF, but does not correspond to the required format as it was defined in the initiating CAP Operation. + +### 10.1.4.2 Operations gsmSCF $\leftarrow$ gsmSRF + +#### Procedures at responding entity (gsmSRF) + +A) gsmSRF receives PromptAndCollectUserInformation + +Precondition: SRSM FSM state "Connected"; or +SRSM FSM state "User Interaction". + +Postcondition: SRSM FSM state "User Interaction". + +B) format of the user input is not correct, gsmSRF returns ImproperCallerResponse to gsmSCF + +Precondition: SRSM FSM state "User Interaction". + +Postcondition: SRSM FSM state "User Interaction". + +The gsmSRF shall wait for a new CAP Operation from the gsmSCF. This may be a new PromptAndCollectUserInformation or a PlayAnnouncement. + +## 10.1.5 MissingCustomerRecord + +### 10.1.5.1 General description + +#### 10.1.5.1.1 Error description + +The gsmSCF uses this Error to indicate to the gsmSSF, gprsSSF, smsSSF or gsmSRF, that the SLP could not be found in the gsmSCF, because the required customer record does not exist, or the requested SLPI, indicated by the correlationID in "AssistRequestInstructions" does not exist anymore. + +### 10.1.5.2 Operations gsmSSF $\leftarrow$ gsmSCF + +#### Procedures at invoking entity (gsmSSF) + +A) Sending CAP Operation + +Precondition: gsmSSF FSM state "Trigger processing" or +gsmSSF FSM state "Waiting\_for\_Instructions"; in the assisting gsmSSF case. + +Postcondition: gsmSSF FSM state "Waiting\_for\_Instructions". +gsmSSF FSM state "Waiting\_for\_Instructions"; in the assisting gsmSSF case. + +B) gsmSSF receives Error "MissingCustomerRecord" + +Precondition: gsmSSF FSM state "Waiting\_for\_Instructions" or +gsmSSF FSM state "Waiting\_for\_Instructions"; in the assisting gsmSSF case. + +Postcondition: gsmSSF FSM state "Idle" or +gsmSSF FSM state "Idle"; in the assisting gsmSSF case. + +The GMSC or VMSC shall handle the call in accordance with the Default Call Handling parameter of the valid CSI. + +### 10.1.5.3 Operations gsmSRF $\leftarrow$ gsmSCF + +#### Procedures at invoking entity (gsmSRF) + +A) Sending CAP Operation + +Precondition: SRSM FSM state "Connected". + +Postcondition: SRSM FSM state "Connected". + +B) gsmSRF receives Error "MissingCustomerRecord" + +Precondition: SRSM FSM state "Connected". + +Postcondition: SRSM FSM state "Idle". + +The gsmSRF shall initiate a Disconnect. + +### 10.1.5.4 Operations smsSSF $\leftarrow$ gsmSCF + +#### Procedures at invoking entity (smsSSF) + +A) Sending CAP Operation + +Precondition: smsSSF FSM state "Waiting\_for\_Instructions". + +Postcondition: smsSSF FSM state "Waiting\_for\_Instructions". + +B) smsSSF receives Error "MissingCustomerRecord" + +Precondition: smsSSF FSM state "Waiting\_for\_Instructions". + +Postcondition: smsSSF FSM state "Idle". + +The VMSC or SGSN shall handle the Short Message in accordance with the Default SMS Handling parameter of the valid CSI. + +### 10.1.5.5 Operations gprsSSF $\leftarrow$ gsmSCF + +#### Procedures at invoking entity (gprsSSF) + +A) Sending CAP Operation + +Precondition: gprsSSF FSM state "Waiting\_for\_Instructions". + +Postcondition: gprsSSF FSM state "Waiting\_for\_Instructions". + +B) gprsSSF receives Error "MissingCustomerRecord" + +Precondition: gprsSSF FSM state "Waiting\_for\_Instructions". + +Postcondition: gprsSSF FSM state "Idle". + +The SGSN shall handle the GPRS Session or PDP Context in accordance with the Default GPRS Handling parameter of the valid CSI. + +## 10.1.6 MissingParameter + +### 10.1.6.1 General description + +#### 10.1.6.1.1 Error description + +The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this Error to indicate that there is an error in the received CAP Operation argument. The responding entity cannot start the execution of the requested CAP Operation because the argument is incorrect: an expected optional parameter which is essential for the application is not included in the CAP Operation argument. + +### 10.1.6.2 Operations gsmSCF $\leftarrow$ gsmSSF + +#### Procedures at responding entity (gsmSSF) + +Precondition: (1) gsmSSF FSM appropriate state + (2) gsmSSF FSM Call associated CAP Operation received, appropriate event occurred + (3) gsmSSME FSM appropriate state + (4) gsmSSME FSM Non call associated CAP Operation received, appropriate event + +Postcondition: (1) No gsmSSF FSM transition + (2) gsmSSME FSM transition to the initial state (i.e., before receiving the erroneous CAP Operation) + +The gsmSSF detects the error in the received CAP Operation. The Error parameter "MissingParameter" is returned to inform the gsmSCF of this situation. + +### 10.1.6.3 Operations gsmSSF $\leftarrow$ gsmSCF + +#### Procedures at invoking entity (gsmSSF) + +A) Sending CAP Operation + +Precondition: gsmSSF FSM appropriate state + +Postcondition: gsmSSF FSM appropriate state as result of the transfer of the CAP Operation + +B) gsmSSF receives Error "MissingParameter" + +Precondition: gsmSSF FSM appropriate state as result of the transfer of any of the CAP Operation + +Postcondition: gsmSSF FSM state "Idle" + +After receiving this Error, the gsmSSF FSM shall return to the state "Idle". The GMSC or VMSC shall handle the call in accordance with the Default Call Handling parameter, valid for this CAMEL dialogue. In the case of an assisting gsmSSF, the temporary connection shall be released by the assisting gsmSSF. + +### 10.1.6.4 Operations gsmSCF $\leftarrow$ gsmSRF + +#### Procedures at responding entity (gsmSRF) + +Precondition: SRSM FSM state "Connected"; or + SRSM FSM state "User Interaction". + +Postcondition: SRSM FSM state "User Interaction". + +The SRSM detects that a required parameter is not present in the CAP Operation argument. The Error parameter "MissingParameter" is returned to inform the gsmSCF of this situation. + +### 10.1.6.5 Operations gsmSRF $\leftarrow$ gsmSCF + +#### Procedures at invoking entity (gsmSRF) + +A) Sending CAP Operation + +Precondition: SRSM FSM state "Connected". + +Postcondition: SRSM FSM state "Connected". + +B) Receiving Error + +Precondition: SRSM FSM state "Connected". + +Postcondition: SRSM FSM state "Idle". + +The gsmSCF detects the error in the received CAP Operation. The Error parameter "MissingParameter" is used to inform the gsmSRF of this situation. The SL and maintenance functions are informed. The gsmSCF might try another gsmSRF, route the call or release the call (SL dependent). + +### 10.1.6.6 Operations smsSSF $\leftarrow$ gsmSCF + +#### Procedures at invoking entity (smsSSF) + +##### A) Sending CAP Operation + +Precondition: smsSSF FSM state "WaitingForInstructions". + +Postcondition: smsSSF FSM state "WaitingForInstructions". + +##### B) Receiving Error + +Precondition: smsSSF FSM state "WaitingForInstructions". + +Postcondition: smsSSF FSM state "Idle". + +After receiving this error, the smsSSF FSM shall transit to the state "Idle". The SGSN or VMSC shall handle the Short Message in accordance with the Default SMS Handling parameter of the valid CSI. + +### 10.1.6.7 Operations gsmSCF $\leftarrow$ smsSSF + +#### Procedures at responding entity (smsSSF) + +precondition: + +- (1) smsSSF appropriate state. +- (2) smsSSF SMS associated CAP Operation received, appropriate event occurred. + +postcondition: + +- (1) smsSSF transition to the same state. + +The smsSSF detects the error in the received CAP Operation. The Error parameter "MissingParameter" is returned to inform the gsmSCF of this situation. + +### 10.1.6.8 Operations gprsSSF $\leftarrow$ gsmSCF + +#### Procedures at invoking entity (gprsSSF) + +##### A) Sending CAP Operation + +Precondition: gprsSSF FSM state "Waiting\_for\_Instructions". + +Postcondition: gprsSSF FSM state "Waiting\_for\_Instructions". + +##### B) Receiving Error + +Precondition: gprsSSF FSM state "Waiting\_for\_Instructions". + +Postcondition: gprsSSF FSM state "Idle". + +After receiving this error, the gprsSSF FSM shall transits to the state "Idle". The SGSN shall handle the GPRS Session or PDP Context in accordance with the Default GPRS Handling parameter of the valid CSI. + +### 10.1.6.9 Operations gsmSCF $\leftarrow$ gprsSSF + +#### Procedures at responding entity (gprsSSF) + +precondition: + +- (1) gprsSSF appropriate state. +- (2) gprsSSF CAP Operation received, appropriate event occurred. + +postcondition: + +(1) gprsSSF transition to the same state. + +The gprsSSF detects the error in the received CAP Operation. The Error parameter "MissingParameter" is returned to inform the gsmSCF of this situation. + +## 10.1.7 ParameterOutOfRange + +### 10.1.7.1 General description + +#### 10.1.7.1.1 Error description + +The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this Error to indicate that it cannot start the execution of the requested CAP Operation because an error in a parameter of the CAP Operation argument is detected: a parameter value is out of range. + +#### 10.1.7.2 Operations gsmSCF $\leftarrow$ gsmSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.7.3 Operations gsmSSF $\leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.7.4 Operations gsmSCF $\leftarrow$ gsmSRF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.7.5 Operations smsSSF $\leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.7.6 Operations gsmSCF $\leftarrow$ smsSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.7.7 Operations gprsSSF $\leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.7.8 Operations gsmSCF $\leftarrow$ gprsSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +## 10.1.8 RequestedInfoError + +### 10.1.8.1 General description + +#### 10.1.8.1.1 Error description + +The gsmSSF uses this Error to indicate to the gsmSCF that the information requested in the CallInformationRequest CAP Operation is not known to the gsmSSF or is not available. + +#### 10.1.8.2 Operations gsmSCF $\leftarrow$ gsmSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +## 10.1.9 SystemFailure + +### 10.1.9.1 General description + +#### 10.1.9.1.1 Error description + +The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this error to indicate that it is not able to execute a specific task as requested by a CAP Operation, and recovery is not expected to be completed within the current call instance. + +#### 10.1.9.2 Operations gsmSCF $\mathcal{C}$ gsmSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.9.3 Operations gsmSSF $\mathcal{C}$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.9.4 Operations gsmSCF $\mathcal{C}$ gsmSRF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.9.5 Operations gsmSRF $\mathcal{C}$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.9.6 Operations smsSSF $\mathcal{C}$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.9.7 Operations gsmSCF $\mathcal{C}$ smsSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.9.8 Operations gprsSSF $\mathcal{C}$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.9.9 Operations gsmSCF $\mathcal{C}$ gprsSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +## 10.1.10 TaskRefused + +### 10.1.10.1 General description + +#### 10.1.10.1.1 Error description + +The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this Error to indicate that it is not able to execute a specific task as requested by a CAP Operation, and recovery is expected to be completed within the current call instance. + +If the gsmSSF requests MoveLeg or SplitLeg operations in the gsmSSF while user interaction is in progress in an affected Call Segment, then CAP\_Error (task refused) is returned. + +#### 10.1.10.2 Operations gsmSCF $\mathcal{C}$ gsmSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.10.3 Operations gsmSSF $\mathcal{C}$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.10.4 Operations gsmSCF $\leftarrow$ gsmSRF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.10.5 Operations gsmSRF $\leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.10.6 Operations smsSSF $\leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.10.7 Operations gsmSCF $\leftarrow$ smsSSF + +##### SMS Related + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.10.8 Operations gprsSSF $\leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.10.9 Operations gsmSCF $\leftarrow$ gprsSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.11 UnavailableResource + +#### 10.1.11.1 General description + +##### 10.1.11.1.1 Error description + +The gsmSRF uses this Error to indicate to the gsmSCF that it is not able to perform its function (i.e., play a certain announcement and/or collect specific user information), and cannot be replaced. A reattempt is not possible. + +#### 10.1.11.2 Operations gsmSCF $\leftarrow$ gsmSRF + +##### Procedures at responding entity (gsmSRF) + +A) gsmSRF receiving PlayAnnouncement or PromptAndCollectUserInformation + +Precondition: SRSM FSM state "Connected"; if initial PlayAnnouncement or PromptAndCollectUserInformation; or SRSM FSM state "User Interaction"; if not initial PlayAnnouncement or PromptAndCollectUserInformation. + +B) gsmSRF is not able to perform its function (and cannot be replaced). The gsmSRF sends the Error "UnavailableResource". + +Precondition: SRSM FSM state "User Interaction". + +Postcondition: SRSM FSM state "User Interaction". + +### 10.1.12 UnexpectedComponentSequence + +#### 10.1.12.1 General description + +##### 10.1.12.1.1 Error description + +The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this Error to indicate that it cannot start the execution of the requested CAP Operation because a SACF or MACF rule is violated, or the CAP Operation cannot be executed in the current state of the FSM. + +### 10.1.12.2 Operations gsmSCF $\leftarrow$ gsmSSF + +In this case the gsmSSF detects the erroneous situation, sends the Error "UnexpectedComponentSequence" and remains in the same state. + +### 10.1.12.3 Operations gsmSSF $\leftarrow$ gsmSCF + +If the CAP Operation is sent by an "initiating" gsmSSF in the context of an existing relationship, then the gsmSCF returns the Error parameter. On receiving the error the gsmSSF FSM shall transit to the state "Idle". The VMSC or GMSC shall handle the call in accordance with the Default Call Handling parameter, valid for this CAMEL dialogue. + +### 10.1.12.4 Operations gsmSCF $\leftarrow$ gsmSRF (applicable for direct gsmSCF-gsmSRF case only) + +In this case the gsmSRF detects the erroneous situation, sends the Error "UnexpectedComponentSequence" and remains in the same state. + +### 10.1.12.5 Operations gsmSRF $\leftarrow$ gsmSCF + +In this case, an error occurs if the gsmSRF has already an established relationship with the gsmSCF and sends the CAP Operation AssistRequestInstructions. The gsmSCF detects the erroneous situation, informs SL and maintenance functions and returns the error parameter. On receiving the Error parameter, the gsmSRF FSM shall transit to the state "Idle" and releases the temporary connection. + +### 10.1.12.6 Operations smsSSF $\leftarrow$ gsmSCF + +If the CAP Operation is sent by the smsSSF in the context of an existing relationship, then the gsmSCF returns the Error parameter. On receiving the error, the smsSSF FSM shall transit to the state "Idle". The SGSN or VMSC shall handle the Short Message in accordance with the Default SMS Handling parameter of the valid CSI. + +### 10.1.12.7 Operations gsmSCF $\leftarrow$ smsSSF + +In this case the smsSSF detects the erroneous situation, sends the Error "UnexpectedComponentSequence" and remains in the same state. + +### 10.1.12.8 Operations gprsSSF $\leftarrow$ gsmSCF + +If the CAP Operation is sent by the gprsSSF in the context of an existing relationship, then the gsmSCF returns the Error parameter. On receiving the error, the gprsSSF FSM shall transit to the state "Idle". The SGSN shall handle the GPRS Session or PDP Context in accordance with the Default GPRS Handling parameter of the valid CSI. + +### 10.1.12.9 Operations gsmSCF $\leftarrow$ gprsSSF + +In this case the gprsSSF detects the erroneous situation, sends the Error "UnexpectedComponentSequence" and remains in the same state. + +## 10.1.13 UnexpectedDataValue + +### 10.1.13.1 General description + +#### 10.1.13.1.1 Error description + +The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this Error to indicate that it cannot execute the requested CAP Operation because a parameter has an unexpected data value. + +Note that this error does not overlap with "ParameterOutOfRange". + +EXAMPLE: startTime DateAndTime ::= -- value indicating January 32 1993, 12: 15: 01 + +The responding entity does not expect this value and responds with Error "UnexpectedDataValue". + +### 10.1.13.2 Operations gsmSCF $\leftarrow$ gsmSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.13.3 Operations gsmSSF $\leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.13.4 Operations gsmSCF $\leftarrow$ gsmSRF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.13.5 Operations gsmSRF $\leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.13.6 Operations smsSSF $\leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.13.7 Operations gsmSCF $\leftarrow$ smsSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.13.8 Operations gprsSSF $\leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.13.9 Operations gsmSCF $\leftarrow$ gprsSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +## 10.1.14 UnexpectedParameter + +### 10.1.14.1 General description + +#### 10.1.14.1.1 Error description + +The gsmSCF, gsmSSF, gsmSRF, smsSSF or gprsSSF uses this Error to indicate that there is an error in the received CAP Operation argument. A valid but unexpected parameter was present in the CAP Operation argument. The presence of this parameter is not consistent with the presence of the other parameters. The responding entity cannot start the execution of the CAP Operation. + +### 10.1.14.2 Operations gsmSCF $\leftarrow$ gsmSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.14.3 Operations gsmSSF $\leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.14.4 Operations gsmSCF $\leftarrow$ gsmSRF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.14.5 Operations gsmSRF $\leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.14.6 Operations smsSSF $\leftarrow$ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.14.7 Operations gsmSCF ⌚ smsSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.14.8 Operations gprsSSF ⌚ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.14.9 Operations gsmSCF ⌚ gprsSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.15 UnknownLegID + +#### 10.1.15.1 General description + +##### 10.1.15.1.1 Error description + +The gsmSSF uses this error to indicate to the gsmSCF that a specific leg, indicated by the LegID parameter value in the CAP Operation, is unknown to the gsmSSF. + +#### 10.1.15.2 Operations gsmSCF ⌚ gsmSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.16 UnknownCSID + +#### 10.1.16.1 General description + +##### 10.1.16.1.1 Error description + +The gsmSSF uses this error to indicate to the gsmSCF that a specific Call Segment, indicated by the callSegmentID parameter value in the CAP Operation, is unknown to the gsmSSF. + +#### 10.1.16.2 Operations gsmSCF ⌚ gsmSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +### 10.1.17 UnknownPDPIID + +#### 10.1.17.1 General description + +##### 10.1.17.1.1 Error description + +The gsmSCF or gprsSSF uses this error to indicate that a specific PDP Context, indicated by the PDPIID parameter value in the CAP Operation argument, is unknown to the receiving entity. + +#### 10.1.17.2 Operations gprsSSF ⌚ gsmSCF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +#### 10.1.17.3 Operations gsmSCF ⌚ gprsSSF + +Refer to subclause 10.1.6 MissingParameter for the appropriate error procedures. + +## 10.2 Entity related error procedures + +The following subclauses specify the error handling procedures for the Functional Entity related errors. Since the error situations are not originated by the reception of a CAP Operation, the invoking entity is denoted here as the entity at which the error situation is detected. The responding entity is the entity which receives the error report. + +The TC services used for reporting errors are described in clause 14. + +## 10.2.1 Expiration of Tssf + +### 10.2.1.1 General description + +#### 10.2.1.1.1 Error description + +A timeout has occurred in the gsmSSF, gprsSSF, smsSSF or assisting gsmSSF on the response from the gsmSCF. + +#### 10.2.1.2 Procedures gsmSSF $\leftarrow$ gsmSCF + +##### Procedure at the invoking entity (gsmSSF or assisting gsmSSF) + +Timeout occurs in gsmSSF on Tssf. + +Precondition: gsmSSF FSM state "Waiting\_for\_Instructions"; or +gsmSSF FSM state "Waiting\_for\_end\_of\_User\_Interaction"; or +gsmSSF FSM state "Waiting\_for\_end\_of\_Temporary\_Connection". + +Postcondition: gsmSSF FSM state "Idle". + +The gsmSSF shall abort the TC dialogue and shall transit to the state "Idle". The GMSC or VMSC shall handle the call in accordance with the Default Call Handling parameter, valid for this CAMEL dialogue. For CAMEL dialogues that are established as a result of a CSI, the Default Call Handling parameter is obtained from the CSI. For gsmSCF initiated CAMEL dialogues, the Default Call Handling parameter shall be "ReleaseCall". + +The assisting gsmSSF shall abort the TC dialogue and shall transit to the state "Idle". The assisting gsmSSF shall release the temporary connection. + +#### 10.2.1.3 Procedures gprsSSF $\leftarrow$ gsmSCF + +##### Procedure at the invoking entity (gprsSSF) + +Timeout occurs in gprsSSF on Tssf. + +Precondition: gprsSSF FSM state "Waiting\_for\_Instructions". + +Postcondition: gprsSSF FSM state "Idle". + +The gprsSSF shall abort the TC dialogue and and the GPRS dialogue and shall transit to the state "Idle". The SGSN shall handle the PDP Context in accordance with the Default GPRS Handling parameter of the valid CSI. + +#### 10.2.1.4 Procedures smsSSF $\leftarrow$ gsmSCF + +##### Procedure at the invoking entity (smsSSF) + +Timeout occurs in smsSSF on Tssf. + +Precondition: smsSSF FSM state "Waiting\_for\_Instructions". + +Postcondition: smsSSF FSM state "Idle". + +The smsSSF shall abort the TC dialogue and shall transit to the state "Idle". The MSC or SGSN shall handle the Short Message in accordance with the Default SMS Handling parameter of the valid CSI. + +## 10.2.2 Expiration of Tsrf + +### 10.2.2.1 General Description + +#### 10.2.2.1.1 Error description + +A timeout has occurred in the gsmSRF on the response from the gsmSCF. The procedures for handling this error are described in ETSI ETS 300 374-1 [24]. + +## 10.2.2.2 Procedures description + +The procedures for handling this error are described in ETSI ETS 300 374-1 [24]. + +--- + +# 11 Detailed operation procedures for circuit switched call control + +NOTE: The detailed operation procedures in the present clause which cross reference the gsmSCF FSMs for the pre- and postconditions are for information only. + +NOTE: Where a parameter for a circuit switched call control Operation is marked OPTIONAL in ASN.1, the reader is referred to the conditions for presence for this parameter, specified in the respective Information Flow in 3GPP TS 23.078 [7]. + +## 11.1 ActivityTest procedure + +### 11.1.1 General description + +The gsmSCF uses this operation to check for the continued existence of a relationship between the gsmSCF and the gsmSSF, between the gsmSCF and the gsmSRF or between the gsmSCF and the assist gsmSSF. If the relationship is still in existence, then the receiving entity will respond If the ActivityTest operation timer expires, then the gsmSCF will assume that the receiving entity has failed in some way and will take appropriate action. + +#### 11.1.1.1 Parameters + +None. + +### 11.1.2 Responding entity (gsmSSF, gsmSRF or assist gsmSSF) + +#### 11.1.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A relationship exists between the gsmSCF and the gsmSSF. +- (2) The gsmSSME FSM is in the state "Idle Management" or in the state "Non-call Associated Treatment". + +gsmSRF or assist gsmSSF preconditions: + +- (1) A relationship exists between the gsmSCF and the gsmSRF or assist gsmSSF. +- (2) The gsmSSME FSM is in the state "Idle Management". + +gsmSSF postconditions: + +- (1) The gsmSSME FSM stays in, or transits to the state "Non-call Associated Treatment". +- (2) If the TC Dialogue ID is active and there is a gsmSSF using the dialogue, then the gsmSSME FSM shall send a Return Result "ActivityTest" to the gsmSCF. If there are no other management activities (e.g. Call Gapping), then the gsmSSME FSM shall transit to the state "Idle Management". Otherwise, the gsmSSME FSM remains in the state "Non-call Associated Treatment". + +If the TC Dialogue ID is not active, then the TC in the gsmSSF will issue a P-Abort. The gsmSSME FSM will in that case not receive the "ActivityTest" indication and thus will not be able to reply. + +gsmSRF or assist gsmSSF postconditions: + +- (1) The gsmSSME FSM transits to the state "Non-call Associated Treatment". +- (2) If the TC Dialogue ID is active and there is a gsmSRF or assist gsmSSF using the dialogue, then the gsmSSME FSM shall send a Return Result "ActivityTest" to the gsmSCF. The gsmSSME FSM then returns to the state "Idle Management". + +If the TC Dialogue ID is not active, then the TC in the gsmSRF or assist gsmSSF will issue a P-Abort. The gsmSSME FSM will in that case not receive the ActivityTest indication and thus will not be able to reply. + +### 11.1.2.2 Error handling + +Operation related error handling is not applicable, due to class 3 operation. + +## 11.2 ApplyCharging procedure + +### 11.2.1 General description + +The gsmSCF uses this operation for interacting with the gsmSSF function: "CSE control of call duration". The ApplyChargingReport operation provides the feedback from the gsmSSF to the gsmSCF. + +The charging scenarios supported by this operation are those given in 3GPP TS 22.078 [3] for "CSE control of call duration". + +#### 11.2.1.1 Parameters + +- aChBillingChargingCharacteristics: + +This parameter specifies a list of parameters required for "CSE control of call duration": + +The list may contain the following parameters: + +- timeDurationCharging: + +This list contains the following parameters: + +- maxCallPeriodDuration: +This parameter specifies the period of time for which a call may progress before an ApplyChargingReport shall be sent to the gsmSCF. +- releaseIfDurationExceeded: +This parameter specifies the action to be taken at the gsmSSF when the duration specified above has been reached. +- audibleIndicator: +This parameter indicates to the gsmSSF that an audible indicator may be played to the served subscriber. This audible indicator may either be a predefined sequence of tones or a sequence defined by the gsmSCF. This parameter shall consist of either tone or burstlist as described below: + - tone: +This parameter indicates that a warning tone shall be played when the pre-defined warning tone timer expires. + - burstlist: +This parameter indicates that a variable sequence of tones shall be played when the gsmSCF-defined warning tone timer expires. This parameter may consist of the following parameters: + - c) - burst: +This parameter indicates the number of bursts that form the burstlist. + - d) - burstInterval: +This parameter indicates the time interval between the successive burst in the burstlist. + - e) - toneInBurst: +This parameter indicates the number of tones to be played in each burst. + - f) - toneDuration: +This parameter indicates the time duration that the tone shall be played for. + +g) - toneInterval: + +This parameter indicates the time interval between successive tones in a burst + +- tariffSwitchInterval (for the CSE control of call duration): + +This parameter indicates the time duration until the next tariff switch for the CSE control of call duration. The measurement of the elapsed tariff switch period shall start immediately after successful execution of this operation. + +- partyToCharge: + +This parameter indicates the party in the call. + +- aChChargingAddress: + +This parameter identifies the call party to which the ApplyCharging operation applies. That is the leg or srfConnection. + +This parameter is a choice of one of the following parameters: + +- legID: + +This parameter indicates that the "CSE control of call duration" is associated to the specified leg. + +or + +- srfConnection: + +This parameter indicates that the "CSE control of call duration" is associated to the Temporary Connection or to the connection to a gsmSRF. + +## 11.2.2 Responding entity (gsmSSF) + +### 11.2.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A control relationship exists between the gsmSCF and the gsmSSF. +- (2) The gsmSSF FSM is in one of the following states: + +"Waiting\_for\_Instructions"; or +"Waiting\_for\_end\_of\_User\_Interaction"; or +"Waiting\_for\_end\_of\_Temporary\_Connection"; or +"Monitoring". + +gsmSSF postconditions: + +- (1) No gsmSSF FSM state transition. + +On receipt of this operation, the gsmSSF sets the charging data using the information elements included in the operation and acts accordingly. + +If the aChChargingAddress indicates a legID, then: + +The "CSE control of call duration" is associated to the specified leg. If Answer has not already been received on the incoming or outgoing connection (leg) to the Call Party, then the gsmSSF shall start monitoring for the Answer event upon receipt of the ApplyCharging operation. Upon subsequent detection of the Answer event on the outgoing connection charging is started. If the Answer event has occurred on the incoming or outgoing connection already when the ApplyCharging operation is received, then charging starts immediately. + +A precautionary started DELTA measurement shall be taken into account when charging is started. + +For a change in the connection configuration of the legs - on CPH - the particular point in time when the new connection configuration is established shall be taken as Answer time. + +Upon release of the incoming or outgoing connection to the Call Party any indication of Answer event occurred on the incoming or outgoing connection shall be cleared, i.e. set to "Answer event not occurred". + +If the aChChargingAddress indicates a srfConnection, then: + +The "CSE control of call duration" is associated to the Temporary Connection or to the connection to a gsmSRF. If Answer has not already been received on the Temporary Connection, then the gsmSSF will start monitoring for the Answer event upon receipt of the ApplyCharging operation; or, if the gsmSRF is not yet connected, then the gsmSSF will start monitoring for a connection to a gsmSRF. Upon subsequent detection of the Answer event on the Temporary Connection or the subsequent connection to a gsmSRF, charging shall be started. If the Answer event has been received from a Temporary Connection already or if the gsmSRF is already connected when the ApplyCharging operation is received, then charging shall start immediately. + +Upon release of the Temporary Connection any indication of Answer event receipt on the outgoing connection shall be cleared i.e. set to "Answer event not received". Upon end of the connection to a gsmSRF, any indication of the connection to the gsmSRF shall be cleared. + +### 11.2.2.2 Error handling + +"TaskRefused": In addition to the generic error handling noted below, this error shall be indicated when: + +- a previously received call period duration is pending for this leg or srfConnection; +- a tariffSwitchInterval for the "CSE control of call duration" is indicated when a previously received tariffSwitchInterval for the "CSE control of call duration" is pending for the Called Party, the Temporary Connection or the connection to a gsmSRF. + +Generic error handling for the operation related errors is described in clause 10 and the TC services used for reporting operation errors are described in clause 14. + +## 11.3 ApplyChargingReport procedure + +### 11.3.1 General description + +The gsmSSF uses this operation to report charging related information to the gsmSCF as requested by the gsmSCF using the "ApplyCharging" operation. + +For a change in a connection configuration of the legs – on CPH – this operation shall be sent as an indication towards the gsmSCF that the supervision of that part of the connection is finished; i.e. + +- (i) the gsmSCF shall settle the account using the reported duration and +- (ii) the durations reported for subsequent AC/ACR cycles will not be accumulated to the reported duration. + +If Answer is detected by the gsmSSF, then timing of duration shall be started as requested by the ApplyCharging operation. It shall be started independently for a connection to a Called Party, a Temporary Connection and a gsmSRF connection. + +The charging report shall be generated as specified in the 3GPP TS 23.078 [7]. + +The tariff switch mentioned in the following subclause is the tariff switch for "CSE control of call duration" for the connection to which the ApplyChargingReport procedure applies. + +#### 11.3.1.1 Parameters + +- callResult: +This parameter provides the gsmSCF with the charging related information previously requested using the ApplyCharging operation. The "CallResult" is a list and may contain the following parameters: + - timeDurationChargingResult: +This parameter is a list, and can contain the following parameters: + - timeInformation: +This parameter is a choice of the following parameters: + - timeIfNoTariffSwitch: +This parameter shall be present if no tariff switch has occurred since the reception of the first ApplyCharging operation for the connection to the Called Party, Temporary Connection or gsmSRF connection, otherwise it shall be absent. +If Answer was detected for the connection to the Called Party, the Temporary Connection or the gsmSRF connection, then the elapsed time since detection of Answer shall be reported. If answer was + +not detected, then it shall be set to "0". + +For a change in the connection configuration of the legs - on CPH - the particular point in time when the new connection configuration is established shall be taken as Answer time. + +- timeIfTariffSwitch: + +This parameter shall be present if a tariff switch has occurred since the reception of the first ApplyCharging operation for the connection to the Called Party, Temporary Connection or gsmSRF connection, otherwise it shall be absent. + +The parameter may contain the following information: + +h) - timeSinceLastTariffSwitch: + +If Answer was detected for the connection to the Called Party, the Temporary Connection or the gsmSRF connection, then the elapsed time since detection of Answer or the last tariff switch (whichever of these events was last detected) shall be reported. If Answer was not detected, then it shall be set to "0". + +For a change in the connection configuration of the legs - on CPH - the particular point in time when the new connection configuration is established shall be taken as Answer time. + +i) - TariffSwitchInterval (for the "CSE control of call duration"): + +This parameter is present only if a tariff switch has occurred since the detection of Answer for the connection to the Called Party, the temporary connection or the gsmSRF connection in the reported call period. + +The time interval between either the detection of the Answer event or the previous tariff switch (whichever of these events was last detected) and the last tariff switch is reported. + +For a change in the connection configuration of the legs - on CPH - the particular point in time when the new connection configuration is established shall be taken as Answer time. + +- partyToCharge: + +The "partyToCharge" parameter as received in the related ApplyCharging operation or deduced from the default value. This parameter is used by the gsmSCF, to correlate the result to the request. + +- aChChargingAddress: + +The "aChChargingAddress" parameter as received in the related ApplyCharging operation or deduced from the default value. This parameter is used by the gsmSCF, to correlate the result to the request. + +- legActive: + +This parameter indicates whether the leg, the Temporary Connection or the connection to a gsmSRF is still active or has been released. + +- callLegReleasedAtTcpExpiry: + +This parameter indicates that the gsmSSF has released the call leg or the Temporary Connection or SRF connection + +## 11.3.2 Invoking entity (gsmSSF) + +### 11.3.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A relationship exists between the gsmSSF and the gsmSCF. +- (2) A charging event has been detected that was requested by the gsmSCF via an ApplyCharging operation or a Called Party, Temporary Connection or gsmSRF disconnection event has occurred. + +gsmSSF postconditions: + +- (1) If release of the call has occurred because the allowed call duration has been reached, then: + - All armed EDPs shall be disarmed; + - ApplyChargingReport shall be sent to gsmSCF followed by any pending CallInformationReports; + - The gsmSSF FSM shall transit to the state "Idle". +- (2) If release of the call has occurred but not because the allowed call duration has been reached, then: + +- If there are any armed EDPs or pending reports, then the gsmSSF FSM shall remain in the same state, else; + - The gsmSSF FSM shall transit to the state "Idle". +- (3) else: +- no gsmSSF FSM state transition. + +### 11.3.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services used for reporting operation errors are described in clause 14. + +## 11.4 AssistRequestInstructions procedure + +### 11.4.1 General description + +This operation may be used by an assist gsmSSF or by a gsmSRF. The operation is sent to the gsmSCF when the assisting gsmSSF or gsmSRF receives an indication from an initiating gsmSSF indicating an assist procedure. + +#### 11.4.1.1 Parameters + +- correlationID: +This parameter is used by the gsmSCF to associate the "AssistRequestInstructions" from the assisting gsmSSF or by a gsmSRF with the request from the initiating gsmSSF. The value of the "correlationID" may be extracted from the digits received from the initiating gsmSSF. +- iPSSPCapabilities: +Indicates which gsmSRF resources are attached, available and supported within: + - the MSC where the assisting gsmSSF resides; or + - the IP where the gsmSRF resides. + +### 11.4.2 Invoking entity (gsmSSF/gsmSRF) + +#### 11.4.2.1 Normal procedure + +assisting gsmSSF or gsmSRF preconditions: + +- (1) An assist indication is detected by the assisting gsmSSF or gsmSRF. + +assisting gsmSSF or gsmSRF postconditions: + +- (1) The assisting gsmSSF FSM is in the state "Waiting\_for\_Instructions" or the gsmSRF FSM is in the state "Connected". + +On receipt of an assist indication from the initiating gsmSSF, the assisting gsmSSF or gsmSRF shall ensure that the required resources are available to invoke an "AssistRequestInstructions" operation in the assist gsmSSF or gsmSRF and shall indicate to the initiating gsmSSF that the call is accepted. The "AssistRequestInstructions" operation is invoked by the assist gsmSSF or gsmSRF after the call, which initiated the assist indication, is accepted. + +#### 11.4.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.5 CallGap procedure + +### 11.5.1 General description + +The gsmSCF uses this operation to request the gsmSSF to reduce the rate at which specific service requests are sent to the gsmSCF. This operation may be sent only within a dialogue that has been opened by the gsmSSF by an InitialDP operation. + +### 11.5.1.1 Parameters + +- gapCriteria: +This parameter identifies the criteria for a call to be subject to call gapping. It is a choice of the following parameters: "basicGapCriteria" or "compoundGapCriteria": + - basicGapCriteria: +This parameter consists of the following parameters: + - calledAddressValue: +This parameter indicates that call gapping shall be applied when the leading digits of the dialled number of a call attempt match those specified in "calledAddressValue". The called address is the one received from the current call control. + - gapOnService: +This parameter indicates that call gapping shall be applied when the Service Key of a Service initiation attempt matches the Service Key specified in "gapOnService". + - calledAddressAndService: +This parameter indicates that call gapping shall be applied when the Service Key of a Service initiation attempt matches the Service Key defined in "calledAddressAndService" and the leading digits of the dialled number of a that call attempt match the dialled digits defined in "calledAddressAndService". The called address is the one received from the current call control. + - callingAddressAndService: +This parameter indicates that call gapping shall be applied when the Service Key of a Service initiation attempt matches the Service Key defined in "callingAddressAndService" and the leading digits of the calling party number of that call attempt match the calling party number defined in "callingAddressAndService". In the case of call forwarding the calling address to be gapped shall the redirecting number which is placed in the Initial DP operation. + - compoundGapCriteria: +This parameter consists of the following parameters: + - basicGapCriteria: +This parameter is as described above. + - scfID: +This parameter identifies a gsmSCF. The scfID shall convey the necessary gsmSCF address information (e.g. Global Title) in the network to the requesting gsmSSF. Refer to ITU-T Recommendation Q.713 [42] "calling party address" parameter. The network operator shall decide about the actual mapping of this parameter on the used signalling system. +This parameter indicates the address of the gsmSCF which requests the call gapping. +If scfID is used in an operation that crosses an inter-network boundary, then its encoding must be understood in both networks and if the length is extended beyond 10 bytes this must be supported by both entities; this requires bilateral agreement on the encoding. If this parameter is not available, then the call gapping is not dedicated to a specific gsmSCF. +This parameter is restricted to include a fixed GT address string. + +NOTE: In the case where the GT addresses more than one SCP (e.g. a mated pair), then if one of these physical SCPs enters an overload conditions and issues a CallGap instruction, then the CallGap is applied to all these SCPs. + +- gapIndicators: +This parameter indicates the call gapping characteristics. +- duration: +This parameter specifies the total time interval during which call gapping for the specified gap criteria will be active. + +A duration of 0 indicates that call gapping shall be removed. + +A duration of -2 indicates a network specific duration. + +Other values indicate duration in seconds. A duration of -1 shall not be used. + +- gapInterval: +This parameter specifies the minimum time between calls being allowed through. + +An interval of 0 indicates that calls meeting the gap criteria shall not be rejected. + +An interval of -1 indicates that all calls meeting the gap criteria shall be rejected. + +Other values indicate the gap interval in milliseconds. + +- controlType: +This parameter indicates the reason for activating call gapping. + +The "controlType" value "sCPOverloaded" indicates that an automatic congestion detection and control mechanism in the SCP has detected a congestion situation. + +The "controlType" value "manuallyInitiated" indicates that the service, the network management centre or service management centre, or both has detected a congestion situation, or any other situation that requires manually initiated controls. + +NOTE: The controlType "manuallyInitiated" shall have priority over "sCPOverloaded" call gap. Also non-CAMEL controlled traffic control mechanism may apply to an exchange with the gsmSSF functionality. The non-CAMEL controlled traffic control may also have some influence to the CAMEL call. It is therefore recommended to take measures to co-ordinate several traffic control mechanisms. The non-CAMEL controlled traffic control and co-ordination of several traffic control mechanisms are out of the scope of CAP. + +- gapTreatment: +This parameter indicates how calls that were stopped by the call gapping mechanism shall be treated. + +- informationToSend: + +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. + +- inbandInfo: +This parameter specifies the inband information to be sent. + +- messageID: +This parameter indicates the message(s) to be sent, it can be one of the following: + +- j) - elementaryMessageID: +This parameter indicates a single announcement. + +- duration: +This parameter indicates the maximum time duration in seconds that the message shall be played or repeated. A value of "0" indicates endless repetition. + +- tone: +This parameter specifies a tone to be sent to the end-user. + +- toneID: +This parameter indicates the tone to be sent. + +- k) - duration: +This parameter indicates the time duration in seconds of the tone. A value of "0" indicates infinite duration. + +- releaseCause: +If the call shall be released, then this parameter indicates a specific cause value to be sent in the release message. See ETSI EN 300 356-1 [23]. + +## 11.5.2 Responding entity (gsmSSF) + +### 11.5.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) Call gapping for gapCriteria is not active; or +Call gapping for gapCriteria is active. +- (2) The gsmSSF FSM is in any state except "Idle" and except "Wait\_For\_Request". + +gsmSSF postconditions: + +- (1) The gsmSSME FSM is in the state "Active". +- (2) Call gapping for gapCriteria is activated; or +Call gapping for gapCriteria is renewed; or +Call gapping for gapCriteria is removed. +- (3) No gsmSSF FSM state transition. + +If there is not already an existing gsmSSME FSM for the gap criteria and gsmSCFAddress provided, then a new gsmSSME FSM shall be created. If no gsmSCFAddress is provided, then this refers in general to the gsmSSME FSM without a gsmSCFAddress. This gsmSSME FSM enters the state "Active" and initialises call gapping for the specified CAMEL calls. The parameters "gapIndicators", "controlType", "gapTreatment" and "gsmSCFAddress" for the indicated gap criteria shall be set as provided by the "CallGap" operation. + +In the case that both "manuallyInitiated" and "sCPOverloaded" call gapping are active for the same "gapCriteria", the manuallyInitiated call gapping shall prevail over the "sCPOverloaded" call gapping. More specifically, the following rules shall be applied in the gsmSSF to manage the priority of different control Types associated with the same "gapCriteria": + +- If a gsmSSME FSM already exists for the "gapCriteria" and the gsmSCFAddress provided, then: + - (1) If the (new) "controlType" equals an existing "controlType", then the new parameters (i.e., "gapIndicators" and "gapTreatment") shall overwrite the existing parameters. + - (2) If the (new) "controlType" is different from the existing "controlType", then the new parameters (i.e., "controlType", "gapIndicators" and "gapTreatment") shall be appended to the appropriate gsmSSME FSM (in addition to the existing parameters). The gsmSSME FSM remains in the state "Active". + +If the gsmSSF meets a TDP, then it shall check if call gapping was initiated for the same gsmSCF as the one currently assigned to this TDP or if call gapping exists with no provided gsmSCFAddress. If neither call gapping was initiated nor exists, then an "InitialDP" operation may be sent. + +The gsmSSF shall check if call gapping was initiated either for the "serviceKey" or for the "calledAddressValue" assigned to this TDP. If this is not the case, then an "InitialDP" operation may be sent. If call gapping was initiated for "calledAddressAndService" or "callingAddressAndService" and the "serviceKey" matches, then a check on the "calledAddressValue" and "callingAddressValue" for active call gapping shall be performed. Otherwise, an "InitialDP" operation may be sent. + +If a call to a controlled number matches one "gapCriteria" only, then the corresponding control is applied. If both "manuallyInitiated" call gapping and "sCPOverload" call gapping controls are active, then only the "manuallyInitiated" call gapping shall be applied. + +If a call matches several active "basicGapCriteria", then the treatment as specified in the CallGap associated with the gapCriteria with the highest priority shall be applied, with the priority being from high to low: + +1. calledAddressAndService or calledAddressValue; +2. callingAddressAndService; +3. gapOnService. + +For example, a call with called number 123456 and ServiceKey = NP matches two CallGaps, one with gapCriteria "CalledAdressValue=123" and another one with gapCriteria "gapOnService=NP". Then the call shall be subject to the control of the service request CallGap with "CalledAdressValue=123". + +In the case that multiple call gapping procedures are active with the same gap criteria, the "manuallyInitiated" call gapping shall prevail over the "sCPOverloaded" call gapping. + +If a call to a controlled called number or from a controlled calling number matches several active "basicGapCriteria " of the same type (in this context "calledAddressAndService" and "calledAddressValue" are seen as one type), then only the "gapCriteria" associated with the longest called party number shall be used, and the corresponding control shall be applied. For example, the codes 1234 and 12345 are under control. Then the call with 123456 is subject to the control on 12345. + +If a call to a controlled called number matches calledAddressAndService and calledAddressValue with the same number length, then calledAddressAndService has priority. Furthermore, if both "manuallyInitiated" and "sCPOverloaded" "controlTypes" are active for this "gapCriteria", then the "manuallyInitiated" control shall be applied. + +If call gapping is performed on a call for a particular service and triggering of this service is allowed, then no other gap criteria shall be applied this service instance. + +Active GapCriteria with assigned scfID shall have higher priority than the other GapCriteria. In the case that an entry with scfID matching the current call exists, all other criteria without scfID shall not be evaluated. + +The matching entries with scfID shall be evaluated in accordance with the priority rules for the basic criteria listed above. + +If call gapping shall be applied and there is no gap interval active, then an "InitialDP" operation may be sent including the "cGEncountered" parameter in accordance with the specified controlType. A new gap interval shall be initiated as indicated by "gapInterval". + +If a gap interval is active, then no "InitialDP" operation shall be sent and the call shall be treated as defined by Default Call Handling of the valid CSI and "gapTreatment". + +If the indicated duration equals "0", then the call gap process shall be stopped. + +If call gapping proceeds, then the gsmSSME FSM remains in the state "Active". Otherwise, the gsmSSME FSM transits to the state "idle". + +## 11.5.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +# 11.6 CallInformationReport procedure + +## 11.6.1 General description + +The gsmSSF uses this operation to send specific call information for a single call party to the gsmSCF as requested by the gsmSCF in previous "CallInformationRequest" operation. The report shall be sent at the end of a call party connection which is indicated by one of the events specified below. + +### 11.6.1.1 Parameters + +- requestedInformationList: +The gsmSSF sends the appropriate types and values to the gsmSCF in accordance with the requested information. +- legID: +This parameter indicates the party in the call for which the information has been collected. + +## 11.6.2 Invoking entity (gsmSSF) + +### 11.6.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) The indicated or default party is released from the call or call setup towards the indicated or default party is terminated prematurely. +- (2) Requested call information has been collected. +- (3) "CallInformationReport" is pending due to a previously received "CallInformationRequest" operation. +- (4) A control or a monitor relationship exists between the gsmSCF and the gsmSSF. + +gsmSSF postconditions: + +- (1) If there are no armed EDPs or pending reports, then the gsmSSF FSM shall transit to the state "Idle"; otherwise, the gsmSSF FSM shall remain in the same state. + +If the gsmSSF FSM executes a state transition caused by one of the following events: + +- release for the indicated or default leg; +- abandon for the indicated or default leg; +- Called party Busy or Not Reachable for the indicated or default leg; +- gsmSSF No\_Answer timer expiration for the indicated or default leg; +- route select failure for the indicated or default leg; +- release of call initiated by the gsmSCF (ReleaseCall), + +and "CallInformationRequest" is pending for the indicated or default leg, then one "CallInformationReport" operation shall be sent to the gsmSCF, containing all information requested for that leg. + +If a "CallInformationReport" has been sent to the gsmSCF, then no "CallInformationReport" is pending on that leg, i.e. if a further "CallInformationReport" on that leg is required, for example in the case of follow-on call, then this has to be explicitly requested by the gsmSCF. + +### 11.6.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +## 11.7 CallInformationRequest procedure + +### 11.7.1 General description + +The gsmSCF uses this operation to request the gsmSSF to record specific information about a single call party and report it to the gsmSCF using the "CallInformationReport" operation. + +#### 11.7.1.1 Parameters + +- requestedInformationTypeList: +This parameter specifies a list of specific items of information which is requested. The list may contain the following parameters: + - callAttemptElapsedTime: +This parameter indicates the duration between the end of CAP processing of operations initiating call setup ("Connect", "Continue" or "ContinueWithArgument") and the received answer indication from the called party. If the callAttemptElapsedTime is requested for the calling party, then a value of "0" shall be reported by the gsmSSF. + +In the case of unsuccessful call setup, the network event indicating the unsuccessful call setup stops the measurement of "callAttemptElapsedTime". + +- callStopTime: +This parameter indicates the time stamp when the connection is released. +- callConnectedElapsedTime: +This parameter indicates the duration between the received answer indication from the called party and the release of that connection. For the calling party it indicates the duration between the sending of InitialDP and the release of that party. +- releaseCause: +This parameter indicates the release cause for the call. +- legID: +This parameter indicates the party in the call for which the information shall be collected. + +## 11.7.2 Responding entity (gsmSSF) + +### 11.7.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A control relationship exists between gsmSSF and gsmSCF. +- (2) The gsmSSF FSM is in the state "Waiting\_for\_Instructions". + +gsmSSF postconditions: + +- (1) Requested call information is retained by the gsmSSF. +- (2) No gsmSSF FSM state transition. + +The gsmSSF allocates a record for the indicated or default party and stores the requested information if already available and prepares the recording of information items, that will become available later like for example "callStopTimeValue". + +Call information may be requested for any call party (identified by a legID). + +### 11.7.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.8 Cancel procedure + +### 11.8.1 General description + +The gsmSCF uses this operation to request the gsmSRF or gsmSSF to cancel a correlated previous operation. + +The Cancel operation may be used for the following purposes: + +- (1) Cancel may be sent to the gsmSRF to cancel the "PlayAnnouncement" or the "PromptAndCollectUserInfo" operation. The cancellation of the operation is indicated via a respective error indication, "Canceled", to the invoking entity of the cancelled "PlayAnnouncement" or "PromptAndCollectUserInfo" operation. +- (2) Cancel may be sent to the gsmSSF to disarm all armed EDPs and cancel all pending reports. This enables the gsmSSF FSM to transit to the state "Idle". If Cancel is used for this purpose, then the Cancel operation does not specify any specific operation to be cancelled. + +### 11.8.1.1 Parameters + +- invokeID: +This parameter specifies which operation invocation shall be cancelled, i.e. PromptAndCollectUserInformation or PlayAnnouncement. +- callSegmentID: +This parameter specifies the Call Segment to which the cancellation of the user interaction operation shall apply. +- allRequests: +This parameter indicates that all armed EDP shall be disarmed and that any pending "ApplyChargingReport" and "CallInformationReport" shall be cancelled. + +## 11.8.2 Responding entity (gsmSRF) + +In the case of Cancel(invokeID), the gsmSRF is the responding entity. In this case, the Cancel operation may also contain the callSegmentID parameter. + +### 11.8.2.1 Normal procedure + +gsmSRF preconditions: + +- (1) A PlayAnnouncement or PromptAndCollectUserInformation operation has been received and the gsmSRF FSM is in the state "User Interaction". + +gsmSRF postconditions: + +- (1) The execution of the PlayAnnouncement or PromptAndCollectUserInformation operation has been aborted and the gsmSRF remains in the state "User Interaction". + +### 11.8.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.8.3 Responding entity (gsmSSF) + +In the case of Cancel(allRequests), the gsmSSF is the responding entity. + +### 11.8.3.1 Normal procedure + +gsmSSF preconditions: + +- (1) The gsmSSF FSM is in the state "Waiting\_for\_Instructions" or in the state "Monitoring". + +gsmSSF postconditions: + +- (1) All armed EDPs are disarmed and all pending reports are cancelled. +- (2) If the gsmSSF FSM was in the state "Monitoring", then it shall transit to the state "Idle"; or +If the gsmSSF FSM was in the state "Waiting\_for\_Instructions", then it shall remain in that state. +A subsequent call-processing operation will result in a gsmSSF FSM state transition to the state "Idle". If the call is in the active state, then the gsmSSF shall treat it autonomously as a normal (non-CAMEL) call. + +### 11.8.3.2 Error handling + +Sending of return error on cancel is not applicable in the cancel "allRequests" case. Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.8A CollectInformation Procedure + +### 11.8A.1 General description + +The gsmSCF uses this operation to request the gsmSSF to perform the call processing actions to collect additional digits from the calling party and report it to the gsmSCF. The CollectInformation operation may be used for TO calls in the gsmSSF. The gsmSCF shall arm the Collected\_Info DP as EDP-R before sending this operation. + +#### 11.8A.1.1 Parameters + +None + +Note: An operation argument is supported for future extensibility. + +### 11.8A.2 Responding entity (gsmSSF) + +#### 11.8A.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A control relationship exists between the gsmSCF and the gsmSSF; +- (2) Basic call processing has been suspended at CollectedInfo DP or AnalysedInfo DP; +- (3) CollectedInfo DP has been armed as EDP-R; +- (4) The gsmSSF FSM is in the state "Waiting\_for\_Instructions". + +gsmSSF postconditions: + +- (1) The gsmSSF performs the call processing actions to collect additional dialled digits from the calling party; +- (2) The gsmSSF FSM transits to the state "Monitoring"; +- (3) In the O-BCSM, call processing resumes at PIC Collect\_Info or PIC Analyze\_Information. + +#### 11.8A.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.9 Connect procedure + +### 11.9.1 General description + +The gsmSCF uses this operation to request the gsmSSF to perform the call processing actions to route a call to a specific destination. + +In general all parameters which are provided in a Connect operation to the gsmSSF shall replace the corresponding signalling parameter in the CCF in O-BCSM, in accordance with ETSI ES 201 296 [21] and shall be used for subsequent call processing. The CCF of the T-BCSM shall send corresponding signalling parameters to new call leg without using them in subsequent call processing. Parameters which are not provided by the Connect operation shall retain their value (if already assigned) in the CCF for subsequent call processing. + +#### 11.9.1.1 Parameters + +- destinationRoutingAddress: +This parameter contains the called party numbers towards which the call shall be routed. +- alertingPattern: +This parameter indicates the type of alerting to be applied. It is defined in 3GPP TS 29.002 [11]. + +- serviceInteractionIndicatorsTwo: +This parameter contains indicators to resolve interactions between CAMEL based services and network based services. +- callingPartyCategory: +This parameter indicates the type of calling party (e.g., operator, pay phone, ordinary subscriber). +- originalCalledPartyID: +If the call is forwarded by the gsmSCF, then this parameter carries the dialled digits. +- redirectingPartyID: +This parameter indicates the last directory number the call was redirected from. +- redirectionInformation: +This parameter contains forwarding related information, such as redirecting counter. +- genericNumbers: +This parameter allows the gsmSCF to set the Generic Number parameter used in the network. It is used for transfer of Additional Calling Party Number. +- suppressionOfAnnouncement: +This parameter indicates that announcements and tones which are played in the exchange at non-successful call set-up attempts shall be suppressed. +- oCSIApplicable: +This parameter indicates to the GMSC/gsmSSF or VMSC/gsmSSF that the Originating CAMEL Subscription Information, if present, shall be applied on the outgoing call leg created with the Connect operation. For the use of this parameter see 3GPP TS 23.078 [7]. +- Carrier: +This parameter indicates carrier information. It consists of the carrier selection field followed by the Carrier ID information to be used by gsmSSF for routeing a call to a carrier. + +It contains the following embedded parameters: + +- carrierSelectionField: +This parameter indicates how the selected carrier is provided (e.g. pre-subscribed). +- carrierID: +This parameter indicates the carrier to use for the call. It contains the digits of the carrier identification code. +- naOliInfo: +This parameter contains originating line information which identifies the charged party number type to the carrier. +- ChargeNumber: +This parameter contains the number that identifies the entity to be charged for the call. It identifies the chargeable number for the usage of a carrier (applicable on a call sent into a North American long distance carrier). For a definition of this parameter refer to ANSI T1.113-1995 [92]. +- cug-Interlock: +This parameter uniquely identifies a CUG within a network. +- cug-OutgoingAccess: +This parameter indicates if the calling user has subscribed to the outgoing access inter-CUG accessibility subscription option. +- bor-InterrogationRequested: +This parameter indicates that Basic Optimal Routeing is requested for the call. +- legToBeConnected: +This parameter indicates the leg to be connected. +- suppress-N-CSI: +This parameter indicates that N-CSI shall be suppressed + +## 11.9.2 Responding entity (gsmSSF) + +### 11.9.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A control relationship exists between the gsmSSF and the gsmSCF. +- (2) Basic call processing has been suspended at a DP. +- (3) The gsmSSF FSM is in the state "Waiting\_for\_Instructions". + +gsmSSF postconditions: + +- (1) The gsmSSF performs the call processing actions to route the call to the specified destination. +- (2) In the O-BCSM, call processing resumes at PIC Analyze\_Information. + +On receipt of this operation, the gsmSSF performs the following actions: + +- If no EDPs have been armed and neither a CallInformationReport nor an ApplyChargingReport has been requested, then the gsmSSF FSM transits to the state "Idle". Otherwise, the gsmSSF FSM transits to the state "Monitoring". + +The gsmSSF shall not perform any implicit arming or disarming of DPs. + +Statistic counter(s) are not affected. + +### 11.9.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.10 ConnectToResource procedure + +### 11.10.1 General description + +The gsmSCF uses this operation to connect a call segment from the gsmSSF to a specialized resource. After successful connection to the gsmSRF, the interaction with the parties in the call segment can take place. The gsmSSF relays all operations for the gsmSRF and all responses from the gsmSRF. + +#### 11.10.1.1 Parameters + +- resourceAddress: +This parameter identifies the physical location of the gsmSRF. It may be one of the following parameters. + - iPRoutingAddress: +This parameter indicates the routeing address to set up a connection towards the gsmSRF. + - none: +This parameter indicates that the call segment shall be connected to a predefined gsmSRF. +- serviceInteractionIndicatorsTwo: +This parameter contains an indicator that is used for the control of the through connection to the Calling Party. + +NOTE The call segment to which the ConnectToResource applies does not have to contain a leg to the calling party. + +The assisting gsmSSF shall always assume that Bothway Throughconnection is required, and hence will ignore this parameter if received. + +- callSegmentId: +This parameter indicates the call segment to which the Connect To Resource procedure applies. + +## 11.10.2 Responding entity (gsmSSF) + +### 11.10.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A control relationship exists between the gsmSCF and the gsmSSF. +- (2) The gsmSSF FSM is in the state "Waiting\_for\_Instructions". + +gsmSSF postconditions: + +- (1) The call segment is connected to the gsmSRF. +- (2) A control relationship between the gsmSCF and the gsmSRF is established. +- (3) The gsmSSF FSM transits to the state "Waiting\_for\_end\_of\_User\_Interaction". + +NOTE: The successful connection to the gsmSRF causes a gsmSRF FSM state transition from the state "Idle" to the state "Connected". + +### 11.10.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.11 Continue procedure + +### 11.11.1 General description + +The gsmSCF uses this operation to request the gsmSSF to proceed with call processing at the DP at which it previously suspended call processing to await gsmSCF instructions. The gsmSSF continues call processing without substituting new data from the gsmSCF. + +#### 11.11.1.1 Parameters + +None. + +## 11.11.2 Responding entity (gsmSSF) + +### 11.11.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A control relationship exists between the gsmSSF and the gsmSCF. +- (2) Basic call processing has been suspended at any DP. +- (3) The gsmSSF FSM is in the state "Waiting\_for\_Instructions". + +gsmSSF postconditions: + +- (1) BCSM: If the Call Segment has received all the required resumptions then basic call processing continues. +- (2) The gsmSSF FSM remains in the same state unless all resumptions have been received. + +If all resumptions have been received, then: + +- If there are armed EDPs or pending reports and no user interaction is ongoing, then the gsmSSF FSM transits to the state "Monitoring"; or +- If there are no armed EDPs neither pending reports, then the gsmSSF FSM transits to the state "Idle". + +### 11.11.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +## 11.12 ContinueWithArgument Procedure + +### 11.12.1 General description + +The gsmSCF uses this operation to request the gsmSSF to proceed with call processing at the DP at which it previously suspended call processing to await gsmSCF instructions. It is also used to provide additional service related information to a User (Called Party or Calling Party) whilst the call processing proceeds. + +In general all parameters which are provided in a ContinueWithArgument operation to the gsmSSF shall replace the corresponding signalling parameter in the CCF, in accordance with ETSI ES 201 296 [21], and shall be used for subsequent call processing. Parameters which are not provided by the ContinueWithArgument operation shall retain their value (if already assigned) in the CCF for subsequent call processing. + +#### 11.12.1.1 Parameters + +- legOrCallSegment: +This parameter indicates the leg or Call Segment to which the ContinueWithArgument operation shall apply. +- alertingPattern: +This parameter indicates the type of alerting to be applied. It is defined in 3GPP TS 29.002 [11]. +- serviceInteractionIndicatorsTwo: +This parameter contains indicators that are used to resolve interactions between CAMEL based services and network based services. +- callingPartysCategory: +This parameter indicates the type of calling party (e.g., operator, pay phone, ordinary subscriber). +- genericNumbers: +This parameter allows the gsmSCF to set the Generic Number parameter used in the network. It is used for transfer of Additional Calling Party Number. +- suppressionOfAnnouncement: +This parameter indicates that announcements and tones which are played in the exchange at non-successful call set-up attempts shall be suppressed. +- carrier: +This parameter indicates carrier information. It consists of the carrier selection field followed by the Carrier ID information to be used by gsmSSF for routing a call to a carrier. + +It contains the following embedded parameter: + +- carrierSelectionField: +This parameter indicates how the selected carrier is provided (e.g. pre-subscribed). +- carrierID: +This parameter indicates the carrier to use for the call. It contains the digits of the carrier identification code. +- naOliInfo: +This parameter contains originating line information which identifies the charged party number type to the carrier. +- chargeNumber: +This parameter contains the number that identifies the entity to be charged for the call. It identifies the chargeable number for the usage of a carrier (applicable on a call sent into a North American long distance carrier). For a definition of this parameter refer to ANSI T1.113-1995 [92]. +- cug-Interlock: +This parameter uniquely identifies a CUG within a network. + +- cug-OutgoingAccess: +This parameter indicates if the calling user has subscribed to the outgoing access inter-CUG accessibility subscription option. +- bor-InterrogationRequested: +This parameter indicates that Basic Optimal Routeing is requested for the call. +- suppress-O-CSI: +This parameter indicates that O-CSI shall be suppressed for the forwarding leg or deflecting leg. +- suppress-D-CSI: +This parameter indicates that D-CSI shall be suppressed for the leg. +- suppress-N-CSI: +This parameter indicates that N-CSI shall be suppressed for the leg or trunk originated call. +- suppressOutgoingCallBarring: +This parameter indicates that outgoing call barrings shall be suppressed for the leg. + +## 11.12.2 Responding entity (gsmSSF) + +### 11.12.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A control relationship exists between the gsmSSF and the gsmSCF. +- (2) Basic call processing has been suspended at a DP. +- (3) The gsmSSF FSM is in the state "Waiting\_for\_Instructions". + +gsmSSF postconditions: + +- (1) BCSM: If the Call Segment has received all the required resumptions then basic call processing continues with modified information, +- (2) The gsmSSF FSM remains in the same state unless all resumptions have been received. + +If all resumptions have been received, then: + +- If there are armed EDPs or pending reports and no user interaction is ongoing, then the gsmSSF FSM transits to the state "Monitoring"; or +- If there are no armed EDPs neither pending reports, then the gsmSSF FSM transits to the state "Idle". + +### 11.12.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.13 DisconnectForwardConnection procedure + +### 11.13.1 General Description + +The gsmSCF uses this operation for the following two purposes: + +- (1) To clear a connection to a gsmSRF: + +The operation is used to explicitly disconnect a connection to a resource (gsmSRF) established previously with a "ConnectToResource" or an "EstablishTemporaryConnection" operation. It is used for a forward disconnection from the gsmSSF. + +An alternative solution is the backward disconnect from the gsmSRF, controlled by the "DisconnectFromIPForbidden" parameter in the "PlayAnnouncement" and "PromptAndCollectUserInformation" operations. + +- (2) To clear a connection to an assisting gsmSSF: + +The operation is sent to the non-assisting gsmSSF of a pair of gsmSSFs involved in an assist procedure. It is used to disconnect the temporary connection between the initiating gsmSSF and the assisting gsmSSF and the connection between the assisting gsmSSF and its associated gsmSRF. + +The DisconnectForwardConnection operation shall not be used when the CallSegmentID is required. + +#### 11.13.1.1 Parameters + +None. + +### 11.13.2 Responding entity (gsmSSF) + +#### 11.13.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) The basic call processing has been suspended at a DP. The gsmSSF FSM in the initiating gsmSSF is in the state "Waiting\_for\_end\_of\_User\_Interaction" or in the state "Waiting\_for\_end\_of\_Temporary\_Connection". + +gsmSSF postconditions: + +- (1) The connection to the gsmSRF or assisting gsmSSF is released. +- (2) The gsmSSF FSM is in the state "Waiting\_for\_Instructions". + +The receipt of "DisconnectForwardConnection" results in a disconnection of the assisting gsmSSF or the PE containing the gsmSRF from the call. It does not result in a release of the connection between the gsmSSF and the end-user. + +On receipt of this operation, the gsmSSF shall perform the following actions: + +- The initiating gsmSSF releases the connection to the assisting gsmSSF or the gsmSRF. +- The gsmSSF FSM transits to the state "Waiting\_for\_Instructions". + +NOTE: The successful disconnection to the gsmSRF causes a gsmSRF FSM state transition to the state "Idle". A current order (e.g. "PlayAnnouncement" or "PromptAndCollectUserInfo") is cancelled and any queued order (e.g. "PlayAnnouncement" or "PromptAndCollectUserInfo") is discarded. + +#### 11.13.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +### 11.14 DisconnectForwardConnectionWithArgument procedure + +#### 11.14.1 General Description + +The gsmSCF uses this operation to disconnect a connection to a resource (gsmSRF) established previously with a "ConnectToResource" or an "EstablishTemporaryConnection" operation. + +#### 11.14.1.1 Parameters + +- callSegmentID: +This parameter indicates the Call Segment to be disconnected from the resource. + +### 11.14.2 Responding entity (gsmSSF) + +#### 11.14.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) The basic call processing has been suspended at a DP. The CS\_gsmSSF FSM in the initiating gsmSSF is in the state "Waiting\_for\_end\_of\_User\_Interaction" or in the state "Waiting\_for\_end\_of\_Temporary\_Connection". + +gsmSSF postconditions: + +- (1) The connection to the gsmSRF or assisting gsmSSF is released. +- (2) The CS\_gsmSSF FSM transits to the state "Waiting\_for\_Instructions". + +The receipt of "DisconnectForwardConnectionWithArgument" results in disconnecting the PE containing the gsmSRF from the specified Call Segment. It does not result in a release of the connection between the gsmSSF and the end-user. + +On receipt of this operation, the gsmSSF shall perform the following actions: + +- The gsmSSF releases the connection to the assisting gsmSSF or the gsmSRF. +- The gsmSSF FSM transits to the state "Waiting\_for\_Instructions". + +NOTE: The successful disconnection from the gsmSRF causes the gsmSRF to transit to the state "Idle". A current order (e.g. "PlayAnnouncement" or "PromptAndCollectUserInfo") is cancelled and any queued order (e.g. "PlayAnnouncement" or "PromptAndCollectUserInfo") is discarded. + +## 11.14.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +# 11.15 DisconnectLeg procedure + +## 11.15.1 General Description + +The gsmSCF uses this operation to request the gsmSSF to release a specific leg associated with the call. Any other leg(s) not specified in the Disconnect Leg operation are retained. + +### 11.15.1.1 Parameters + +- legToBeReleased: +This parameter indicates the call leg to be released. +- releaseCause: +This parameter may be used by the MSC for generating specific tones to the party to be released or to fill in the "cause" parameter in the release message. + +## 11.15.2 Responding entity (gsmSSF) + +### 11.15.2.1 Normal procedure + +gsmSSF preconditions: + +- 1) A control relationship exists between the gsmSCF and the gsmSSF; +- 2) User interaction is not in progress in the Call Segment containing the leg to be disconnected. + +gsmSSF postconditions: + +- 1) The gsmSSF performs the call processing actions to release the indicated party. +- 2) Any armed EDPs on that leg shall be disarmed; any pending reports for that leg shall be sent to the gsmSCF. +- 3) If the released leg was the last leg within the Call Segment, then the CS\_gsmSSF FSM for that Call Segment returns to the state "Idle". +- 4) If the leg was the last leg within the call, then the CSA\_gsmSSF FSM returns to the state "Idle". + +- 5) If the CS\_gsmSSF FSM for the Call Segment concerned has not returned to the state "Idle", then it transits to the state "Waiting\_for\_Instructions". The remaining BCSM instances within the Call Segment shall transit to the O\_Mid\_Call DP or to the T\_Mid\_Call DP, unless already suspended at a DP. The Mid\_Call EDP shall not be reported for this case. +- 6) A Return Result shall be sent to the gsmSCF immediately after successful execution of this operation. + +## 11.15.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10, and the TC services which are used for reporting operation errors are described in clause 14. + +# 11.16 EntityReleased procedure + +## 11.16.1 General Description + +The CSA uses this operation to inform the gsmSCF about the release of a logical entity (Call Segment or BCSM) caused by exception or errors. The CSA shall use this operation if this information can not be conveyed in a TC\_ABORT or TC\_END TC message because the TC dialogue has to be maintained for other logical entities (Call Segment or BCSM) in this CSA which are not affected by this error or exception. The CSA shall not use this operation if the last Call Segment in the CSA was released. + +### 11.16.1.1 Parameters + +This operation consists of a choice of the following parameters: + +- CSFailure: +Indicates that a Call Segment was released. It contains of the following parameters: + - callSegmentID: +This parameter identifies the released Call Segment. + - cause: +This parameter indicates the cause for releasing this Call Segment. The cause may be used by the gsmSCF to decide the further handling of the call. +- BCSMFailure: +This parameter indicates that a leg was released. It consists of the following parameters: + - legID: +This parameter identifies the released leg. + - cause: +This parameter indicates the cause for releasing this BCSM. The cause may be used by the gsmSCF to decide the further handling of the call. + +## 11.16.2 Invoking entity (gsmSSF) + +### 11.16.2.1 Normal procedure + +CSA\_gsmSSF preconditions: + +- (1) Any CSA\_gsmSSF FSM state except "Idle". + +CSA\_gsmSSF postconditions: + +- + +gsmSSF postconditions: + +- (1) If the released entity was a BCSM (leg), then only the appropriate resources are released. If the released entity was a Call Segment, then the related CS\_gsmSSF FSM returns to the state "Idle". + +### 11.16.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10, and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.17 EstablishTemporaryConnection procedure + +### 11.17.1 General Description + +The gsmSCF uses this operation to create a connection between an initiating gsmSSF and an assisting gsmSSF as part of a service assist procedure. It can also be used to create a connection between a gsmSSF and a gsmSRF, for the case where the gsmSRF exists in a separately addressable PE. + +The assistingSSPIRoutingAddress shall contain routeing digits, a correlationID and a scfID when a temporary connection shall be established between PLMNs and no bilateral agreement exists between the involved network operators to transfer correlationID and SCFiD as separate parameters. + +#### 11.17.1.1 Parameters + +- assistingSSPIRoutingAddress: +This parameter indicates the destination address of the gsmSRF for assist procedure. The "assistingSSPIRoutingAddress" may contain embedded within it, a "correlationID" and "scfID", but only if "correlationID" and "scfID" are not specified separately. +- correlationID: +This parameter is used by the gsmSCF to associate the "AssistRequestInstructions" from the assisting gsmSSF (or the gsmSRF) with the Request from the initiating gsmSSF. The "correlationID" shall be used only if the correlation id is not embedded in the "assistingSSPIRoutingAddress". The network operator has to decide about the actual mapping of this parameter on the used signalling system. +- scfID: +This parameter contains the gsmSCF identifier and enables the assisting gsmSSF to identify which gsmSCF the AssistRequestInstructions shall be sent to. +The "scfID" shall be used only if the gsmSCF id is not embedded in the "assistingSSPIRoutingAddress". The network operator has to decide about the actual mapping of this parameter on the used signalling system. +When ScfID is used in an operation which crosses an internetwork boundary, its encoding must be understood in both networks and if the length is extended beyond 10 bytes this must be supported by both entities; this requires bilateral agreement on the encoding. +- serviceInteractionIndicatorsTwo: +This parameter contains an indicator that is used for the control of the through connection to the Calling Party. +- Carrier: +This parameter contains carrier information. It consists of the carrier selection field followed by the Carrier ID information to be used by gsmSSF for routeing a call to a carrier. + +It contains the following embedded parameter: + +- carrierSelectionField: +This parameter indicates how the selected carrier is provided (e.g. pre-subscribed). +- carrierID: +This parameter indicates the carrier to use for the call. It contains the digits of the carrier identification code. +- naOliInfo: +This parameter contains originating line information which identifies the charged party number type to the carrier. +- chargeNumber: +This parameter contains the number that identifies the entity to be charged for the call. It identifies the chargeable number for the usage of a carrier (applicable on a call sent into a North American long distance carrier). For a definition of this parameter refer to ANSI T1.113-1995 [92]. + +- callSegmentID: +This parameter indicates the Call Segment to which the temporary connection shall be established. +- originalCalledPartyID: +This parameter identifies the original called party. +- callingPartyNumber: +This parameter identifies the calling party. + +## 11.17.2 Responding entity (gsmSSF) + +### 11.17.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) The gsmSSF FSM is in the state "Waiting\_for\_Instructions". +- (2) The gsmSSF is not an assisting gsmSSF. + +gsmSSF postconditions: + +- (1) The gsmSSF performs the call processing actions to route the call to the assisting gsmSSF or gsmSRF in accordance with the "assistingSSPIPRoutingAddress" requested by the gsmSCF. +- (2) The gsmSSF FSM transits to the state "Waiting\_for\_end\_of\_Temporary\_Connection". + +On receipt of this operation, the gsmSSF shall perform the following actions: + +- Route the call to assisting gsmSSF or gsmSRF using "assistingSSPIPRoutingAddress"; + +### 11.17.2.2 Error handling + +Until the connection setup has been accepted (refer to ITU-T Recommendation Q.71 [41]) by the assisting gsmSSF or the gsmSRF, all received failure indications from the network on the ETC establishment shall be reported to the gsmSCF as EstablishTemporaryConnection error ETCFailed (e.g., busy, congestion). + +NOTE The operation timer for EstablishTemporaryConnection shall be longer than the maximum allowed time for the signalling procedures to accept the connection. + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.18 EventReportBCSM procedure + +### 11.18.1 General description + +The gsmSSF uses this operation to notify the gsmSCF of a call related event previously requested by the gsmSCF in a "RequestReportBCSMEVENT" operation. + +#### 11.18.1.1 Parameters + +- eventTypeBCSM: +This parameter specifies the type of event that is reported. +- eventSpecificInformationBCSM: +This parameter indicates the call related information specific to the event. + +For Collected\_Info it shall contain the CalledPartyNumber parameter. + +For Route\_Select\_Failure it shall contain the "FailureCause", if available. + +For O\_Busy it shall contain the "BusyCause", if available. + +- If the busy event is triggered by an ISUP release message, then the BusyCause is a copy of the ISUP release cause, for example: Subscriber absent, 20 or User busy, 17. + +- If the busy event is triggered by a MAP error, for example: Absent subscriber, received from the HLR, then the MAP cause is mapped to the corresponding ISUP release cause. + +NOTE 1: If no BusyCause is received, then the gsmSCF shall assume busy. + +For T\_Busy it may contain the following parameters, if available. + +- CallForwarded: +This parameter indicates that the busy event is triggered by call forwarding at the GMSC or VMSC. +- ForwardingDestinationNumber: +This parameter indicates the forwarding destination. +- RouteNotPermitted: +This parameter indicates that the busy event is triggered because call forwarding was not invoked in this GMSC due to the rules of Basic Optimal Routeing. +- BusyCause: + - If the busy event is triggered by an ISUP release message, then the BusyCause is a copy of the ISUP release cause, for example: Subscriber absent, 20 or User busy, 17. + - If the busy event is triggered by a MAP error, for example: Absent subscriber, received from the HLR, then the MAP cause is mapped to the corresponding ISUP release cause. + - If the busy event is triggered by call forwarding or call deflection invocation in the GMSC or VMSC, then the BusyCause will refer to the release cause in accordance with the mapping table in 3GPP TS 23.078 [7]. + - If the busy event is triggered by call forwarding at the GMSC, then the BusyCause reflects the forwarding reason (Subscriber Absent, 20 or User busy, 17). The eventSpecificInformationBCSM shall in that case also contain the CallForwarded indication. + +NOTE 2: If no BusyCause is received, then the gsmSCF shall assume busy. + +For O\_No\_Answer it shall be empty. + +For T\_No\_Answer it may contain the CallForwarded indication and the ForwardingDestinationNumber. + +- If the No\_Answer event is triggered by an ISUP release message or expiry of the CAMEL timer TNRY, then the eventSpecificInformationBCSM shall be empty. +- If the No\_Answer event is triggered by call forwarding at the GMSC or VMSC, then the eventSpecificInformationBCSM shall contain the CallForwarded indication and the ForwardingDestinationNumber. + +For O\_Answer or T\_Answer it shall contain the following information, if available: + +- The destination address for the call; +- The OR indicator, in the case that the call was subject to Basic Optimal Routeing, as specified in 3GPP TS 23.079 [8]; +- The forwarding indicator, in the case that the Call Forwarding Supplementary Service was invoked; +- The charge indicator; +- The Extended Basic Service Code, for SCUDIF calls (see 3GPP TS 23.172 [16]); +- The Extended Basic Service Code 2, for SCUDIF calls (see 3GPP TS 23.172 [16]). + +For O\_Mid\_Call and T\_Mid\_Call it shall contain the detected digit string, in accordance with the criterion defined in the RequestReportBCSMEVENT operation. + +For Call\_Accepted, O\_Term\_Seized, O\_Change\_Of\_Position and T\_Change\_Of\_Position it shall contain the following information: + +- locationInformation: +This parameter indicates the location of the MS. + +For O\_Disconnect and T\_Disconnect it shall contain the "releaseCause", if available. + +For O\_Abandon" it may contain the following parameter, if available. + +- routeNotPermitted: +This parameter indicates that the O-Abandon event is triggered because call set up shall not be invoked in this MSC due to the rules of Basic Optimal Routeing. + +For O\_Service\_Change or T\_Service\_Change it may contain the following information: + +- The Extended Basic Service Code, for SCUDIF calls (see 3GPP TS 23.172 [16]) ; + - The initiator of the Service Change; + - The nature of Service Change. +- legID: +This parameter indicates the party in the call for which the event is reported. The gsmSSF shall use the option "receivingSideID" only. + - receivingSideID: +If not included, then the default values for LegID are assumed according to the tables 11-1 and 11-2. +- The "legID" parameter shall always be included for the events O\_Disconnect and T\_Disconnect. +- miscCallInfo: +This parameter indicates Detection Point (DP) related information. + - messageType: +This parameter indicates whether the message is a request, i.e. resulting from a "RequestReportBCSMEVENT" with monitorMode = interrupted, or a notification, i.e. resulting from a "RequestReportBCSMEVENT" with "monitorMode" = "notifyAndContinue". + +## 11.18.2 Invoking entity (gsmSSF) + +### 11.18.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A control relationship or a monitoring relationship exists between the gsmSSF and the gsmSCF. +- (2) For the O\_Abandon DP and T\_Abandon DP, the gsmSSF FSM is in any state, except "Idle". For other DPs, refer to 3GPP TS 23.078 [7]. +- (3) The BCSM proceeds to an EDP that is armed. + +gsmSSF postconditions: + +- (1) If the message type was notification and there are still armed EDPs or pending reports, then the gsmSSF FSM stays in the state "Monitoring". +- (2) If the message type was notification and there are neither any armed EDPs nor pending reports, then the gsmSSF FSM transits to the state "Idle". +- (3) If the message type was request, then the gsmSSF FSM transits to the state "Waiting\_for\_Instructions". Call processing is interrupted. + +### 11.18.2.2 Error handling + +If the message type is "request" and the Tssf timer expires, then the gsmSSF shall abort the TC dialogue and shall instruct the MSC to treat the call in accordance with the Default Call Handling, valid for this CAMEL dialogue. + +Operation related error handling is not applicable, due to class 4 operation. + +## 11.19 FurnishChargingInformation procedure + +### 11.19.1 General description + +The gsmSCF uses this operation to send charging related information to a logical call record. This logical call record is CAMEL specific. The first FurnishChargingInformation operation of a call leg leads to the generation of a logical call record. The handling of subsequent FurnishChargingInformation operations for a call leg depends on the presence and value of the append free format data parameter in the FurnishChargingInformation operation. For details see 3GPP TS 23.078 [7]. + +If a FurnishChargingInformation operation is received for the called party when the gsmSSF FSM is in the state "Monitoring", or is suspended in one of the following DPs, then the charging information shall be included in the logical call record for the leg that has been or is to be established: + +- Collected\_Info; +- Analysed\_Information; +- O\_Answer; +- Terminating\_Attempt\_Authorised; or +- T\_Answer. + +If a FurnishChargingInformation operation is received for the called party when the gsmSSF is suspended in any other DP, then the charging information shall be included in the logical call record created for the last failed or disconnected called party. + +### 11.19.1.1 Parameters + +- fCIBillingChargingCharacteristics: +This parameter contains the following parameters; +- fCIBCCCAMELsequence1: +This parameter contains the following parameters; +- freeFormatData: +This parameter contains free-format billing and/or charging characteristics; +- partyToCharge: +This parameter indicates the party to bill and/or charge; +- appendFreeFormatData: +This parameter indicates whether previous FurnishChargingInformation free format data is appended or overwritten. Refer to 3GPP TS 23.078 [7] for details on the usage of this parameter. + +## 11.19.2 Responding entity (gsmSSF) + +### 11.19.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) The gsmSSF FSM is in the state +"Waiting\_for\_Instructions"; or +"Waiting\_for\_end\_of\_User\_Interaction"; or +"Waiting\_for\_end\_of\_Temporary\_Connection"; or +"Monitoring". + +gsmSSF postconditions: + +- (1) No gsmSSF FSM state transition. + +On receipt of this operation the gsmSSF performs actions to create the Logical call record if necessary, and writes the free-format information carried in the operation into the Logical call record. A FurnishChargingInformation operation + +will create a Logical Call Data Record (CDR) if such a record does not already exist for the indicated leg. Refer to sect. 11.26.1 for the handling in the case of successive FurnishChargingInformation operations for a call leg. + +The Logical CDRs will be associated for a given call into one or more physical CDRs, as specified in 3GPP TS 32.250 [13]. + +A logical call record is output to a physical CDR when a disconnection event is propagated to the call leg associated with it, or when a Connect operation to create a connection to a Follow-on Called Party is received. Successive FurnishChargingInformation operations indicating the calling leg (leg1) may overwrite data from previously received FurnishChargingInformation operation(s) indicating that leg during the entire call or call attempt. Successive FurnishChargingInformation operations indicating a called leg (leg2 or higher) may overwrite any previously received data from FurnishChargingInformation operation(s) indicating that called leg until the called leg representing that particular called party number is released from the call. When a new called party is created as a result of a follow-on call, and a FurnishChargingInformation operation indicating the called leg is received, then a new Logical call record shall be created for that call leg, for that portion of the call. From then on, any subsequent FurnishChargingInformation operations for that called party may overwrite the data from any previous FurnishChargingInformation operation(s) for the called leg presenting that particular called party number. Logical call records that have been output already are not affected. + +No Logical call record is output at the end of a user interaction. + +## 11.19.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +# 11.20 InitialDP procedure + +## 11.20.1 General description + +The gsmSSF uses this operation after detection of a TDP-R in the BCSM, to request the gsmSCF for instructions to complete the call. + +### 11.20.1.1 Parameters + +- **serviceKey:** +This parameter indicates to the gsmSCF the requested IN service. It is used to address the required application/SLP within the gsmSCF; this parameter is not for SCP addressing. +- **calledPartyNumber:** +This parameter contains the number used to identify the called party in the forward direction, i.e. see ETSI EN 300 356-1 [23]. This parameter shall be sent only in the Mobile Terminating, Mobile Forwarding, mobile originating on unsuccessful TDP and trunk originating cases. For the trunk originating case the end of pulsing signal (ST) is included in the calledPartyNumber address signals if it has been received or the MSC has determined that the called number information is complete. +- **callingPartyNumber:** +This parameter carries the calling party number to identify the calling party or the origin of the call. See ETSI EN 300 356-1 [23] Calling Party Number signalling information. +- **callingPartysCategory:** +Indicates the type of calling party (e.g. operator, pay phone, ordinary subscriber). See ETSI EN 300 356-1 [23] Calling Party Category signalling information. +- **locationNumber:** +This parameter is used to convey the geographical area address for mobility services, see ITU-T Recommendation Q.762 [44]. It is used when "callingPartyNumber" does not contain any information about the geographical location of the calling party (e.g., origin dependent routeing when the calling party is a mobile subscriber). +- **originalCalledPartyID:** +If the call has met call forwarding on the route to the gsmSSF, then this parameter carries the dialled digits. Refer to EN 300 356-1[23] Original Called Number signalling information. + +- **highLayerCompatibility:** +This parameter indicates the type of the high layer compatibility, which will be used to determine the ISDN - teleservice of a connected ISDN terminal. The highlayerCompatibility can also be transported by ISUP (e.g. within the ATP (see ITU-T Recommendation Q.763 [45]) parameter). +- **additionalCallingPartyNumber:** +The calling party number provided by the access signalling system of the calling user, e.g. provided by a PBX. +- **bearerCapability:** +This parameter indicates the type of the bearer capability connection or the transmission medium requirements to the user. It is a network option to select which of the two parameters to be used: + - **bearerCap:** +This parameter contains the value of the ISUP User Service Information parameter. + +The parameter "bearerCapability" shall be included in the "InitialDP" operation only in the case the ISUP User Service Information parameter is available at the gsmSSF. + +If User Service Information and User Service Information Prime are available at the gsmSSF, then the "bearerCap" shall contain the value of the User Service Information Prime parameter. +- **eventTypeBCSM:** +This parameter indicates the armed BCSM DP event, resulting in the "InitialDP" operation. +- **redirectingPartyID:** +This parameter indicates the last directory number the call was redirected from. +- **redirectionInformation:** +This parameter contains forwarding related information, such as redirecting counter. +See ITU-T Recommendation Q.763 [45] Redirection Information signalling information. +- **iPSSPCapabilities:** +This parameter indicates which gsmSRF resources supported within the VMSC or GMSC the gsmSSF resides in are attached and available. +- **serviceInteractionIndicatorsTwo:** +This parameter contains indicators that are used to resolve interactions between CAMEL based services and network based services. +- **iMSI:** +This parameter contains the IMSI of the mobile subscriber for which the service is invoked. +- **subscriberState:** +This parameter indicates the state of the mobile subscriber for which the service is invoked. The possible states are "busy", "idle" and "not reachable". +- **locationInformation:** +This parameter indicates the location of the MS and the age of the information defining the location. +- **ext-BasicServiceCode:** +This parameter indicates the Basic Service Code. +- **callReferenceNumber:** +This parameter contains the call reference number assigned to the call by the CCF. +- **mscAddress:** +This parameter contains the mscId assigned to the MSC. +- **gmscAddress:** +This parameter contains the gmscId assigned to the GMSC. +- **calledPartyBCDNumber:** +This parameter contains the number used to identify the called party in the forward direction. It may also include service selection information, including \* and # characters. + +- time&Timezone: +This parameter contains the time that the gsmSSF was triggered, and the time zone that the invoking gsmSSF resides in. +- callForwardingSS-Pending: +This parameter indicates that a forwarded-to-number was received and that the call will be forwarded due to the Call Forwarding supplementary service in the GMSC or in the VMSC, unless otherwise instructed by the gsmSCF. +- carrier: +This parameter contains carrier information. It consists of the carrier selection field followed by the Carrier ID information associated with the calling subscriber of a mobile originating call or trunk originating call, the called subscriber of a mobile terminating call or the forwarding subscriber of a mobile forwarded call. + +It contains the following embedded parameter: + +- carrierSelectionField: +This parameter indicates how the selected carrier is provided (e.g. pre-subscribed). +- carrierID: +This parameter indicates the carrier to use for the call. It contains the digits of the carrier identification code. +- cug-Index: +This parameter is used to select a CUG for an outgoing call at the user, or to indicate an incoming CUG call to the user. +- cug-Interlock: +This parameter uniquely identifies a CUG within a network. +- cug-OutgoingAccess: +This parameter indicates if the calling user has subscribed to the outgoing access inter-CUG accessibility subscription option. +- cGEncountered: +This parameter indicates the type of call gapping the related call has been subjected to, if any. +- cause: +This parameter indicates the release cause which triggered the event: + +For Route\_Select\_Failure" it shall contain the "FailureCause", if available. + +For T\_Busy it may contain the following parameters, if available. + +- If the busy event is triggered by an ISUP release message, then the BusyCause shall a copy of the ISUP release cause, for example: Subscriber absent, 20 or User busy, 17. +- If the busy event is triggered by a MAP error, for example: Absent subscriber, received from the HLR, then the MAP cause is mapped to the corresponding ISUP release cause. +- If the busy event is triggered by call forwarding invocation in the GMSC or VMSC, then the BusyCause shall refer to the type of the call forwarding service in accordance with the mapping table in 3GPP TS 23.078 [7]. +- forwardingDestinationNumber: +This parameter contains the forwarding destination. +- ms-Classmark2: +This parameter contains the MS Classmark 2 of the mobile subscriber for which the service is invoked. +- iMEI: +This parameter contains the IMEI (with software version) of the mobile subscriber for which the service is invoked. +- supportedCamelPhases: +This parameter indicates the CAMEL Phases supported in the GMSC or VMSC which sends this operation. +- offeredCamel4Functionalities: +This parameter contains the offered CAMEL phase 4 functionalities. + +- bearerCapability2: +This parameter indicates the type of the bearer capability connection or the transmission medium requirements to the user. +- ext-BasicServiceCode2: +This parameter indicates the Basic Service Code2. +- highLayerCompatibility2: +This parameter indicates the high layer compatibility2 for a SCUDIF call. +- lowLayerCompatibility: +This parameter indicates the low layer compatibility. +- lowLayerCompatibility2: +This parameter indicates the low layer compatibility2 for a SCUDIF call. +- enhancedDialledServicesAllowed: +This parameter indicates that the gsmSCF may use the Enhanced Dialled Services (EDS) for this call. +- UU-Data: +This parameter contains user-to-user signalling service related information. +- collectInformationAllowed: +This parameter indicates that the gsmSCF may use Collect Information for this call. +- releaseCallArgExtensionAllowed: +This parameter indicates that the gsmSCF may use Extensions in Release Call operation for this call. + +## 11.20.2 Invoking entity (gsmSSF) + +### 11.20.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) An event fulfilling the criteria for the DP being executed has been detected. +- (2) Call gapping and SS7 overload are not in effect for the call. + +gsmSSF postconditions: + +- (1) If the DP was armed as a TDP-R and trigger conditions, if present, are fulfilled, then a control relationship between the gsmSCF and the gsmSSF is established. The gsmSSF FSM transits to the state "Waiting\_for\_Instructions". + +The address of the gsmSCF shall be fetched from the valid CSI. The gsmSSF shall provide all available parameters to the gsmSCF. + +If no triggering takes place, because trigger conditions were not fulfilled, then the gsmSSF shall proceed with call handling without CAMEL Service. + +The gsmSSF application timer Tssf is loaded and started when the gsmSSF sends "InitialDP" for requesting instructions from the gsmSCF. It is used to prevent excessive call suspension time. + +### 11.20.2.2 Error handling + +If the gsmSCF is not accessible, then the call proceeds in accordance with the Default Call Handling parameter in the CSI. + +When Tssf expires, then the gsmSSF shall abort the interaction with the gsmSCF by means of an abort to TC and shall call continue the call in accordance with the Default Call Handling parameter in the valid CSI. + +If the calling party abandons after the sending of "InitialDP" and before the TC dialogue is established, then the gsmSSF shall abort the interaction with the gsmSCF by means of an abort to TC. + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.21 InitiateCallAttempt procedure + +### 11.21.1 General Description + +The gsmSCF uses this operation to request the gsmSSF to create a new call leg to one call party using the address information provided by the gsmSCF (e.g. wake-up call). InitiateCallAttempt can also be used to create an additional call party in a new Call Segment within an existing Call Segment Association. In both use cases the gsmSCF shall subsequently arm O\_Answer as an EDP-R and the call failure events (Route\_Select\_Failure, O\_Busy and O\_No\_Answer) as EDP-Rs and/or EDP-Ns, in order to enable the gsmSCF to treat this call appropriately when any of these events is encountered. + +#### 11.21.1.1 Parameters + +##### 11.21.1.1.1 Argument Parameters + +- destinationRouteingAddress: +This parameter contains the called party number towards which the call shall be routed. +- callingPartyNumber: +This parameter identifies which number shall be regarded as the calling party for the created call. +- legToBeCreated: +This parameter indicates the LegID to be assigned to the newly created party. +- newCallSegment: +This parameter indicates the Call Segment ID to be assigned to the newly created Call Segment. +- callReferenceNumber: +This parameter contains the call reference number assigned to the call by the gsmSCF. +- gsmSCFAddress: +This parameter indicates the address of the gsmSCF initiating the operation. +- suppress-T-CSI: +This parameter indicates that the T-CSI for the served subscriber shall be suppressed for this call leg. + +##### 11.21.1.1.2 Result Parameters + +- supportedCamelPhases: +This parameter indicates the CAMEL Phases supported in the gsmSSF which receives this operation. +- offeredCamel4Functionalities: +This parameter contains the offered CAMEL phase 4 functionalities. +- releaseCallArgExtensionAllowed: +This parameter indicates that the gsmSCF may use Extensions in Release Call operation for this call. + +### 11.21.2 Responding entity (gsmSSF) + +#### 11.21.2.1 Normal procedure + +gsmSSF preconditions: + +None. + +gsmSSF postconditions: + +- 1) A new O-BCSM has been created; call processing is suspended. +- 2) A Return Result is sent to the gsmSCF. +- 3) The CS\_gsmSSF FSM transits from the state "Idle" to the state "Waiting\_for\_Instructions". + +All subsequent operations are treated in accordance with their normal procedures. + +### 11.21.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10, and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.22 MoveLeg procedure + +### 11.22.1 General Description + +The gsmSCF uses this operation to request the gsmSSF to move the leg from its current Call Segment to CSID1. + +#### 11.22.1.1 Parameters + +- legIDToMove: +This parameter indicates the leg that shall be moved. + +### 11.22.2 Responding entity (gsmSSF) + +#### 11.22.2.1 Normal procedure + +gsmSSF preconditions: + +- 1) A control relationship exists between the gsmSCF and the gsmSSF. +- 2) The source BCSM is in the alerting phase or in the active phase. +- 3) The target Call Segment fulfills the following preconditions: + - At least one leg in the target Call Segment has reached the active phase, or + - The original BCSM in the target Call Segment is at Terminating\_Attempt\_Authorised, Analysed\_Information (for EDS only) or Collected\_Info detection point, and the outgoing leg of that BCSM has been disconnected by the gsmSCF, or + - The call was created by the gsmSCF. +- 4) The CS\_gsmSSF FSM for each Call Segment involved is in the state "Waiting\_for\_Instructions" or in the state "Monitoring". +- 5) User Interaction is not in progress in either Call Segment. + +gsmSSF postconditions: + +- 1) The gsmSSF performs the appropriate call processing actions. +- 2) The CS\_gsmSSF FSM for CSID1 transits to the state "Waiting\_for\_Instructions". The BCSM instances within CSID1 transit to the O\_Mid\_Call DP or to the T\_Mid\_Call DP, if not already suspended. The Mid\_Call EDP shall not be reported for this case. +- 3) The CS\_gsmSSF process for the source Call Segment is terminated. +- 4) A Return Result is sent to the gsmSCF immediately after successful execution of this operation. +- 5) A Pending ApplyChargingReport for the source call segment shall be sent to the gsmSCF. + +#### 11.22.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10, and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.23 PlayAnnouncement procedure + +### 11.23.1 General description + +The gsmSCF uses this operation for inband interaction with a CS user. + +#### 11.23.1.1 Parameters + +- informationToSend: +This parameter indicates an announcement a tone to be sent to the end-user by the gsmSRF. + - inbandInfo: +This parameter specifies the inband information to be sent. + - messageID: +This parameter indicates the message(s) to be sent; this may be one of the following: + - elementaryMessageID: +This parameter indicates a single announcement. + - text: +This parameter indicates a text to be sent. The text shall be transformed to inband information (speech) by the gsmSRF. This parameter consists of two parameters; messageContent and attributes. The attributes of the text parameter may consist of items such as language. + - elementaryMessageIDs: +This parameter specifies a sequence of announcements. + - variableMessage: +This parameter specifies an announcement with one or more variable parts. + - numberOfRepetitions: +This parameter indicates the maximum number of times the message shall be sent to the end-user. + - duration: +This parameter indicates the maximum time duration in seconds that the message shall be played or repeated. A value of "0" indicates endless repetition. + - interval: +This parameter indicates the time interval in seconds between successive messages, i.e. the time between the end of the announcement and the start of the repetition of this announcement. This parameter may be used only when "numberOfRepetitions" is > 1. +- tone: +This parameter specifies a tone to be sent to the end-user. + - toneID: +This parameter indicates the tone to be sent. + - duration: +This parameter indicates the time duration in seconds of the tone to be sent. A value of "0" indicates infinite duration. +- disconnectFromIPForbidden: +This parameter indicates whether the gsmSRF may initiate a disconnection from the gsmSSF after the interaction has been completed. + +If this parameter is TRUE, then the gsmSRF shall not initiate a disconnection. If this parameter is FALSE, then the gsmSRF may initiate a disconnection. +- requestAnnouncementCompleteNotification: +This parameter indicates whether or not a "SpecializedResourceReport" shall be sent to the gsmSCF when all information has been sent. + +- requestAnnouncementStartedNotification: +This parameter indicates whether or not a "SpecializedResourceReport" shall be sent to the gsmSCF when the first announcement or tone has started. +- callSegmentID: +This parameter indicates the Call Segment to which the user interaction shall apply. + +## 11.23.2 Responding entity (gsmSRF) + +### 11.23.2.1 Normal procedure + +gsmSRF preconditions: + +- (1) The SRSM-FSM is in the state "Connected"; if the gsmSRF received previously an operation from the gsmSCF, then the SRSM-FSM is in the state "User Interaction". +- (2) When the first announcement or tone has started and "RequestAnnouncementStartedNotification" is TRUE, then the SRSM shall send a "SpecializedResourceReport" operation, containing the "FirstAnnouncementStarted" parameter, to the gsmSCF. + +gsmSRF postconditions: + +- (1) The gsmSRF sends the information to the user as indicated by "informationToSend". +- (2) The SRSM-FSM transits to the state "User Interaction", or remains in the same state. +- (3) If all information has been sent and "RequestAnnouncementCompleteNotification" is TRUE, then the SRSM shall send a "SpecializedResourceReport" operation, containing the "AllAnnouncementsComplete" parameter, to the gsmSCF. +- (4) If all information has been sent and "disconnectFromIPForbidden" is FALSE, then the SRSM disconnects the gsmSRF from the user. + +The announcement sent to the end-user is ended in the following conditions: + +- if neither "duration" nor "numberOfRepetitions" is specified, then the network specific announcement ending conditions shall apply; or +- if "numberOfRepetitions" is specified, when all repetitions have been sent; or +- if duration is specified, when the duration has expired. The announcement is repeated until this condition is met; or +- if "duration" and "numberOfRepetitions" is specified, when one of both conditions is satisfied (whichever comes first). + +### 11.23.2.2 Error handling + +If a Cancel operation is received before or during the processing of the operation, then that operation shall be cancelled immediately and the error "Canceled" shall be reported to the gsmSCF. + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.24 PlayTone procedure + +### 11.24.1 General description + +The gsmSCF uses this operation to instruct the gsmSSF to play tones to a leg or a Call Segment using the MSC's tone generator. + +If a Call Segment is indicated, then the tones shall be played to all active legs in that Call Segment. If a leg is indicated, then the tones shall be played to that leg only. + +### 11.24.1.1 Parameters + +- legOrCallSegment: +This parameter indicates the leg or Call Segment to which the PlayTone operation shall apply. +- bursts: +This parameter indicates the variable sequence of tones to be played and consists of the following parameters: + - numberOfBursts: +This parameter indicates the number of bursts that form the burstlist. + - burstInterval: +This parameter indicates the time interval between successive bursts in a sequence of bursts. + - numberOfTonesInBurst: +This parameter indicates the number of tones to be played in each burst. + - toneDuration: +This parameter indicates the time duration of a single tone in a burst. + - toneInterval: +This parameter indicates the time interval between successive tones in a burst. + +## 11.24.2 Responding entity (gsmSSF) + +### 11.24.2.1 Normal procedure + +gsmSSF preconditions: + +The gsmSSF FSM is in one of the following states: + +"Monitoring"; or +"Waiting\_for\_Instructions". + +If a Call Segment is indicated, then at least one of the legs in that Call Segment is in the active phase. + +gsmSSF postconditions: + +- (1) No gsmSSF FSM state transition. + +### 11.24.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services used for reporting operation errors are described in clause 14. + +## 11.25 PromptAndCollectUserInfo procedure + +### 11.25.1 General description + +The gsmSCF uses this operation to interact with a call party in order to collect information. + +#### 11.25.1.1 Parameters + +- collectedInfo: + - collectedDigits: + +- minimumNbOfDigits: +This parameter specifies the minimum number of valid digits to be collected. +- maximumNbOfDigits: +This parameter specifies the maximum number of valid digits to be collected. The following applies: +"maximumNbOfDigits" $\geq$ "minimumNbOfDigits". +- endOfReplyDigit: +This parameter indicates the digit string used to signal the end of input. + +In the case that the "maximumNbOfDigits" > "minimumNbOfDigits" the following applies: + +If "endOfReplyDigit" is not present, then the end of input is indicated: + +- l) - when the inter-digit timer expires; or +- m) - when the number of valid digits received equals the "maximumNbOfDigits". + +If "endOfReplyDigit" is present, then the end of input is indicated: + +- n) - when the inter-digit timer expires; or +- o) - when the end of reply digit is received; or +- p) - when the number of valid digits received equals the "maximumNbOfDigits". + +When the end of input is reached, the collected digits are sent from gsmSRF to the gsmSCF, including the "endOfReplyDigit" if received by the gsmSRF. In the case the number of valid digits received is less than the "minimumNbOfDigits" when the inter-digit timer expires or when the end of reply digit is received, the input is considered to be erroneous. + +- cancelDigit: +This parameter indicates the cancel digit string that may be entered by the user to request a retry. All digits already received by the gsmSRF are discarded and the PromptAndCollectUserInformation procedure is performed again, thus e.g. the same announcement to request user information is given to the user and information is collected. If this parameter is not present, then the user is not able to request a retry. +- startDigit: +This parameter indicates the start digit string that indicates the start of the valid digits to be collected. The digits that are received by the gsmSRF before this start digit is received, are discarded and are not considered to be valid. The start digit string itself is considered to be valid digits. + +If this parameter is not present, then all received digits are considered to be valid. + +When the end of input is reached, the collected digits are sent from gsmSRF to the gsmSCF, including the "startDigit" if received by the gsmSRF. + +- firstDigitTimeout: +If this parameter is present, then the first digit shall be received by the gsmSRF before first-digit timer expiration. If the first digit is not received before first-digit timer expiration, then the input is considered to be erroneous. + +If this parameter is not present, then the gsmSRF shall use a default value for the first-digit timer. + +If "startDigit" is present, then the first-digit timer shall be stopped after the start digit is received. If "startDigit" is not present, then the first-digit timer shall be stopped when any digit is received, except when the digit matches the "cancelDigit", if present. + +- interDigitTimeout: + +If this parameter is present, then any subsequent valid or invalid digit shall be received by the gsmSRF before the inter-digit timer expires. As a result of receiving a digit, the inter-digit timer is reset and restarted. + +If a subsequent valid or invalid digit is not received before the inter-digit timer expires and the number of received valid digits is less than "minimumNbOfDigits", then the input is considered to be unsuccessful. + +If a subsequent valid or invalid digit is not received before the inter-digit timer expires and the number of received valid digits is greater than "minimumNbOfDigits" and smaller than or equal to "maximumNbOfDigits", then the input is considered to be successful. + +If the "interDigitTimeout" is not present, then the gsmSRF shall use a default value for the inter-digit timer. + +- errorTreatment: + +This parameter defines what specific action shall be taken by the gsmSRF in the event of error conditions occurring. + +- interruptableAnnInd: + +If this parameter is TRUE, then the announcement shall interrupted after the first valid or invalid digit is received by the gsmSRF. If the announcement is interrupted, then a first-digit timer shall not apply anymore. However, if the announcement has not been interrupted, then the first-digit timer shall be started after the announcement has been finished. + +If this parameter is FALSE, then the announcement shall not be interrupted after the first digit is received by the gsmSRF. The received digits during the announcement are discarded and considered to be invalid. All other specified parameters ("minimumNbOfDigits", "maximumNbOfDigits", "endOfReplyDigit", etc.) do not apply before the announcement has been finished. The first-digit timer shall be started after the announcement has been finished. + +- voiceInformation: + +If this parameter is FALSE, then all valid or invalid digits shall be entered by DTMF. + +If this parameter is TRUE, then the calling user is required to provide all valid or invalid information by speech. The gsmSRF shall perform voice recognition and shall translate the provided information into digits. The end of reply digit(s), if required, shall be provided by speech. + +- voiceBack: + +If this parameter is FALSE, then no voice back information shall be given by the gsmSRF. + +If this parameter is TRUE, then the valid input digits received by the gsmSRF shall be announced back to the calling user immediately after the end of input is received. The invalid input digits will not be announced back to the calling user. The end of reply digit(s) shall not be voiced back to the calling user. + +- disconnectFromIPForbidden: + +This parameter indicates whether the gsmSRF may initiate a disconnection from the gsmSSF after the interaction has been completed. + +If this parameter is TRUE, then the gsmSRF shall not initiate a disconnection. If this parameter is FALSE, then the gsmSRF may initiate a disconnection. + +- informationToSend: + +This parameter indicates an announcement or tone to be sent to the end-user by the gsmSRF. + +- inbandInfo: +This parameter specifies the inband information to be sent. +- messageID: +This parameter indicates the message(s) to be sent,, this may be one of the following: + - elementaryMessageID: +This parameter indicates a single announcement. + - text: +This parameter indicates a text to be sent. The text shall be transformed to inband information (speech) by the gsmSRF. The attributes of text may consist of items such as language. + - elementaryMessageIDs: +This parameter specifies a sequence of announcements. + - variableMessage: +This parameter specifies an announcement with one or more variable parts. +- numberOfRepetitions: +This parameter indicates the maximum number of times the message shall be sent to the end-user. +- duration: +This parameter indicates the maximum time duration in seconds that the message shall be played or repeated. A value of "0" indicates endless repetition. +- interval: +This parameter indicates the time interval between successive messages, i.e. the time between the end of the announcement and the start of the repetition of this announcement. This parameter may be used only when "numberOfRepetitions " > 1. +- tone: +This parameter specifies a tone to be sent to the end-user. + - toneID: +This parameter indicates the tone to be sent. + - duration: +This parameter indicates the time duration in seconds of the tone. A value of "0" indicates infinite duration. +- requestAnnouncementStartedNotification: +This parameter indicate whether or not a "SpecializedResourceReport" shall be sent to the gsmSCF when the first announcement or tone has started. +- callSegmentID: +This parameter indicates the Call Segment to which the user interaction shall apply. + +#### Result Parameter: + +- digitsResponse: +This parameter contains the information collected from the end-user. + +## 11.25.2 Responding entity (gsmSRF) + +### 11.25.2.1 Normal procedure + +#### gsmSRF preconditions: + +- (1) The SRSM-FSM is in the state "Connected"; if the gsmSRF received previously an operation from the gsmSCF, then the SRSM-FSM is in the state "User Interaction". +- (2) If the first announcement or tone has started and "RequestAnnouncementStartedNotification" is TRUE, then the SRSM sends a "SpecializedResourceReport" operation, containing the "FirstAnnouncementStarted" parameter, to the gsmSCF. + +gsmSRF postconditions: + +- (1) The gsmSRF has sent the information to the end-user as indicated by "informationToSend". +- (2) The collected information from the end-user is sent to the gsmSCF as RETURN RESULT of the "PromptAndCollectUserInfoInformation". +- (3) If the "disconnectFromIPForbidden" is FALSE, then the gsmSRF initiates a bearer channel disconnect to the gsmSSF and the SRSM FSM transits to the state "Idle". +- (4) Otherwise, the SRSM FSM transits to the state "User Interaction" or remains in the same state. + +The announcement sent to the end-user is ended in the following conditions: + +- if neither "duration" nor "numberOfRepetitions" is specified, then the network specific announcement ending conditions shall apply; or +- if "numberOfRepetitions" is specified, when all repetitions have been sent; or +- if duration is specified, when the duration has expired. The announcement is repeated until this condition is met; or +- if "duration" and "numberOfRepetitions" is specified, when one of both conditions is satisfied (whichever comes first). + +If the parameter "interruptableAnnInd" is not FALSE and the end-user has responded with a digit during the sending of the announcement, then the above conditions are overruled. In that case, the announcement shall be ended immediately. + +The parameter "errorTreatment" specifies how the gsmSRF shall treat an error. The value "reportErrorToSCF" means that the error shall be reported to the gsmSCF by means of Return Error with "ImproperCallerResponse". The value "help" indicates that no error shall be reported to gsmSCF but assistance shall be given to the end-user in the form of a network dependent default announcement (which may be dependent on the context, i.e. the sent message). The value "repeatPrompt" indicates that no error shall be reported to the gsmSCF but the prompt shall be repeated to the end-user. The error handling procedures related to "help" and "repeatPrompt" shall be done only once per "PromptAndCollectUserInfoInformation" operation. + +**NOTE** Note on processing "endOfInput" + +The receipt of any "endOfInput" condition (e.g endOfReplyDigit, cancelDigit, firstDigitTimeout, interDigitTimeout) terminates immediately the ongoing input. In other words when e.g an endOfReplyDigit is received, then the receipt of a subsequent cancelDigit will not be processed anymore. + +## 11.25.2.2 Error handling + +If a Cancel operation is received before or during the processing of the operation, then the operation shall be cancelled immediately and the error "Canceled" shall be reported to the gsmSCF. + +Generic error handling for the operation related errors are described in clause 10, the TC services which are used for reporting operation errors are described in clause 14. + +If any of the parameter restrictions are violated (e.g. "minimumNbOfDigits" > "maximumNbOfDigits"), then an operation error has occurred. + +## 11.26 ReleaseCall procedure + +### 11.26.1 General description + +The gsmSCF uses this operation to tear down a call at any phase. + +#### 11.26.1.1 Parameters + +- allCallSegments: +This parameter gives an indication to the gsmSSF about the reason of releasing this specific call. This may be used by gsmSSF for generating specific tones to the different parties in the call or to fill in the "cause" in the release message. +- allCallSegmentsWithExtension: +This parameter gives an indication to the gsmSSF about the reason of releasing this specific call. This may be used by gsmSSF for generating specific tones to the different parties in the call or to fill in the "cause" in the release message. It additionally allows for the sending of the extensions parameter to the gsmSSF. + +### 11.26.2 Responding entity (gsmSSF) + +#### 11.26.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A control relationship exists between gsmSCF and gsmSSF. +- (2) The gsmSSF FSM is in the state "Waiting\_for\_Instructions" or in the state "Monitoring". + +gsmSSF postconditions: + +- (1) The gsmSSF FSM transits to the state "Idle" after sending any pending "CallInformationReport" or "ApplyChargingReport". All armed EDPs shall be disarmed. All connections and resources related to the call shall be released. + +#### 11.26.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +## 11.27 RequestReportBCSMEVENT procedure + +### 11.27.1 General description + +The gsmSCF uses this operation to request the gsmSSF to monitor for a call-related event (e.g., BCSM events such as O\_Busy or O\_No\_Answer) and to send a notification to the gsmSCF when the event is detected. + +The monitoring of more than one event may be requested with a single "RequestReportBCSMEVENT" operation, but each of these requested events will be reported in a separate "EventReportBCSM" operation. + +NOTE: If the RequestReportBCSMEVENT requests arming of the current DP from which the call processing was suspended, then the next occurrence of the DP encountered during BCSM processing will be detected (i.e. not the current one from which the call was suspended). + +The DP arming principle is as follows: + +- The DPs O\_Disconnect and T\_Disconnect can be armed for any or all legs depending on the direction for which events have to be captured. As an example, the O\_Disconnect DP can be armed for leg1 and leg2; in this case, if a release request is received from the A-party, then it will be detected by the O\_Disconnect DP armed for leg1, while a release request from the B-party will be detected by the O\_Disconnect DP armed for leg2. +- The O\_Abandon DP can be armed only for leg1 in the O-BCSM and the T\_Abandon DP can be armed only for leg1 in the T-BCSM. + +- The Collected\_Info DP can be armed only for leg1 in the O-BCSM for TO calls. + +**Table 11-1: DP Arming Table for O-BCSM:** + +| O-BCSM | leg1 | Not leg 1 | Default leg_ID | +|-------------------------|------|-----------|----------------| +| O_Term_Seized DP | - | X | 2 | +| Route_Select_Failure DP | - | X | 2 | +| O_Busy DP | - | X | 2 | +| O_No_Answer DP | - | X | 2 | +| O_Answer DP | - | X | 2 | +| O_Disconnect DP | X | X | -(note 1) | +| O_Abandon DP | X | - | 1 | +| O_Mid_Call | X | - | 1 | +| O_Change_Of_Position | X | - | 1 | +| O_Service_Change | X | - | 1 | +| Collected_Info DP | X | - | 1 | + +Note 1: The "legID" parameter shall be included +Nomenclature: X = Arming Applicable +- = Arming not Applicable + +**Table 11-2: DP Arming Table for T-BCSM:** + +| T-BCSM | leg2 | leg1 | Default Leg ID | +|----------------------|------|------------|----------------| +| Call_Accepted DP | X | - | 2 | +| T_Busy DP | X | - | 2 | +| T_No_Answer DP | X | - | 2 | +| T_Answer DP | X | - | 2 | +| T_Disconnect DP | X | X | -(note 1) | +| T_Abandon DP | - | X (note 2) | 1 | +| T_Mid_Call | X | - | 2 | +| T_Change_Of_Position | X | - | 2 | +| T_Service_Change | X | - | 2 | + +Note 1: The "legID" parameter shall be included +Note 2: T\_Abandon can be armed for leg1 only. +Nomenclature: X = Arming Applicable +- = Arming not Applicable + +### 11.27.1.1 Parameters + +- bcsmevents: +This parameter specifies the event or events of which a report is requested. + - eventTypeBCSM: +This parameter specifies the type of event of which a report is requested. + - monitorMode: +This parameter indicates how the event shall be reported. If the "monitorMode" is "interrupted", then the event shall be reported as a request; if the "monitorMode" is "notifyAndContinue", then the event shall be reported as a notification; if the "monitorMode" is "transparent", then the event shall not be reported. + - legID: +This parameter indicates the party in the call for which the event shall be reported. The gsmSCF shall use the option "sendingSideID" only. + - sendingSideID: + +If not included, then the default values for LegID are assumed according to the tables 11-1 and 11-2. + +The "legID" parameter shall always be included for the events O\_Disconnect and T\_Disconnect. + +- dPSSpecificCriteria: +This parameter contains information specific to the EDP that shall be armed. + +- **numberOfDigits:** +This parameter indicates the number of digits requested for the CollectedInfo event. +- **interDigitTimeout:** +This parameter indicates the inter-digit timer value for the CollectedInfo event. +- **applicationTimer:** +This parameter indicates the No\_Answer timer value for the No\_Answer event. If the called party does not answer the call within the allotted time, then the gsmSSF shall report the event to the gsmSCF. This timer shall be shorter than the network No\_Answer timer. +- **midCallControlInfo:** +This parameter defines the criterion for the detection and reporting of mid-call digits. If this parameter is absent, then the first digit entered shall be reported. +- **changeOfPositionControlInfo:** +This parameter defines the criterion for the reporting of change of location. If this parameter is absent, then any change of position shall be reported. +- **automaticRearm:** +This parameter indicates that the gsmSSF shall rearm the DP whenever it is encountered. + +## 11.27.2 Responding entity (gsmSSF) + +### 11.27.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) A control relationship exists between the gsmSSF and the gsmSCF. +- (2) The gsmSSF FSM is in the state "Waiting\_for\_Instructions" or in the state "Monitoring". + +NOTE: In the state "monitoring" only requests to disarm detection points (with MonitorMode set to "Transparent") or to send notifications of events (with MonitorMode set to "NotifyAndContinue") shall be accepted by the gsmSSF. + +gsmSSF postconditions: + +- (1) The requested EDPs are armed or disarmed as indicated. +- (2) Previously requested events are monitored until ended by a transparent monitor mode, until the end of the call, until the EDPs are detected or until the corresponding leg is released. +- (3) The gsmSSF FSM remains in the same state, unless all EDPs have been disarmed and no CallInformationReport or ApplyChargingReport has been requested; in the latter case, the gsmSSF FSM transits to the state "Idle". + +### 11.27.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.28 ResetTimer procedure + +### 11.28.1 General description + +The gsmSCF uses this operation to refresh the Tssf application timer, in order to avoid the Tssf time-out at the gsmSSF. + +#### 11.28.1.1 Parameters + +- **timerID:** +This parameter indicates which timer shall be reset. The only permissible value of this parameter is "tssf". +- **timerValue:** +This parameter specifies the value to which the timer shall be set. + +- callSegmentID: + +This parameter indicates the Call Segment in the gsmSSF for which the timer shall be reset. + +## 11.28.2 Responding entity (gsmSSF) + +### 11.28.2.1 Normal procedure + +gsmSSF preconditions: + +- (1) Basic call processing has been suspended at a DP. +- (2) The gsmSSF FSM is in the state "Waiting\_for\_Instructions", the state "Waiting\_for\_end\_of\_User\_Interaction" or in the state "Waiting\_for\_end\_of\_Temporary\_Connection". + +gsmSSF postconditions: + +- (1) The Tssf timer is loaded with the value received from the gsmSCF and is restarted. +- (2) No gsmSSF FSM state transition. + +### 11.28.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.29 SendChargingInformation procedure + +### 11.29.1 General description + +The gsmSCF uses this operation to instruct the gsmSSF on the Advice of Charge information to be sent by the gsmSSF. The SendChargingInformation operation may be invoked on multiple occasions. + +The SendChargingInformation operation may be used for MO and MT calls in the VMSC. In the case of an MT call, the CSE provided e-parameters are not used by Mobile Station if a call forwarding or follow-on call occurs. + +#### 11.29.1.1 Parameters + +- sCIBillingChargingCharacteristics: +This parameter is a choice between two lists of information. + +The first list shall be sent only if there is neither an active call leg, nor a Temporary Connection, nor a connection to a gsmSRF. It contains the following parameters: + +- aOCBeforeAnswer: +This is a list of the following information: + - aOCInitial: +This is a set of Charge Advice Information (CAI) elements, as defined in 3GPP TS 22.024 [2]. These CAI elements shall be sent by the gsmSSF to the MS when Answer is detected and a tariff switch for the "CSE control of e-parameters" has not yet occurred. + - aOCSubsequent: +This list may contain the following information: + - cAIElements: +This is a set of Charge Advice Information (CAI) elements, as defined in 3GPP TS 22.024 [2]. These CAI elements shall be sent to the MS when Answer is detected and a tariff switch for the "CSE control of e-parameters" has occurred previously, or when Answer has previously been detected and a tariff switch for the "CSE control of e-parameters" occurs. + - tariffSwitchInterval (for the "CSE control of e-parameters"): +This parameter indicates the time duration until the next tariff switch for the "CSE control of e-parameters". The measurement of the elapsed tariff switch period shall start immediately after successful execution of this operation. + +The second list in the choice shall be sent only if there is an active call leg or a Temporary Connection or a connection to a gsmSRF. It contains the following parameters: + +-aOCAfterAnswer: + +This list may contain the following information: + +- cAIElements: + +This is a set of Charge Advice Information (CAI) elements, as defined in 3GPP TS 22.024 [2]. These CAI elements shall be sent to the MS by the gsmSSF when Answer is detected and a tariff switch for the "CSE control of e-parameters" has occurred previously, or when Answer has previously been detected and a tariff switch for the "CSE control of e-parameters" occurs. + +- tariffSwitchInterval (for the "CSE control of e-parameters"): + +This parameter indicates the time duration until the next tariff switch for the "CSE control of e-parameters". The measurement of the elapsed tariff switch period shall start immediately after successful execution of this operation. + +- legID: + +This parameter indicates where the charging information shall be sent. For Mobile Originated calls, only leg 1 shall be used. For Mobile Terminated calls in the VMSC, only the leg of the CAMEL subscriber shall be used. + +## 11.29.2 Responding entity (gsmSSF) + +### 11.29.2.1 Normal procedure + +gsmSSF preconditions: + +(1) The gsmSSF FSM is in one of the following states: + +"Waiting\_for\_Instructions"; or +"Waiting\_for\_end\_of\_User\_Interaction"; or +"Waiting\_for\_end\_of\_Temporary\_Connection"; or +"Monitoring". + +gsmSSF postconditions: + +(1) No gsmSSF FSM state transition. + +On receipt of this operation the gsmSSF performs actions to send the Advice of Charge information to the indicated Call Partys MS. + +If Advice of Charge shall be provided to a MS in conjunction with "CSE control of call duration", then the following sequence of operations may be sent by the gsmSCF to the gsmSSF in the following order, in the same TC-CONTINUE TC message: + +one or more ApplyCharging operations; SendChargingInformation operation. + +These operations shall be processed sequentially by the gsmSSF, in the order that they are sent by the gsmSCF. In this case, the parameters TariffSwitchInterval (for the "CSE control of call duration") may be present in any of the ApplyCharging operations and the parameter TariffSwitchInterval (for the "CSE control of e-parameters") may be present in the SendChargingInformation operation. + +The TariffSwitchInterval information received with the ApplyCharging operation shall set or overwrite the tariff switch timer for the "CSE control of call duration" in the gsmSSF and this duration timer shall run from the time of successful operation execution. + +The TariffSwitchInterval information received in the SendChargingInformation operation shall set or overwrite the tariff switch timer for the "CSE control of e-parameters" in the gsmSSF and this duration timer shall run from the time of successful operation execution. + +### 11.29.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 11.30 SpecializedResourceReport procedure + +### 11.30.1 General description + +The gsmSRF uses this operation as a response to a "PlayAnnouncement" operation or a "PromptAndCollectUserInformation" operation. This operation shall be used only when the "requestAnnouncementCompleteNotification" parameter is TRUE or the "requestAnnouncementStartedNotification" parameter is TRUE in the "PlayAnnouncement" operation or the "PromptAndCollectUserInformation" operation. + +#### 11.30.1.1 Parameters + +- allAnnouncementsComplete: +This parameter indicates that all the announcements and tones are complete. +- firstAnnouncementStarted: +This parameter indicates that the first announcement or tone has started. + +### 11.30.2 Invoking entity (gsmSRF) + +#### 11.30.2.1 Normal procedure + +gsmSRF preconditions: + +- (1) The gsmSRF FSM is in the state "User\_Interaction". +- (2) Either: + - (i) The sending of announcements and tones as defined in the "PlayAnnouncement" operation or the "PromptAndCollectUserInformation" operation has started and the parameter "RequestAnnouncementStartedNotification" in the "PlayAnnouncement" or "PromptAndCollectUserInformation" operation is TRUE; or + - (ii) A "PlayAnnouncement" operation has been executed, all announcements and tones have been sent and the parameter "RequestAnnouncementCompleteNotification" in the "PlayAnnouncement" operation is TRUE. + +gsmSRF postconditions: + +- (1) No gsmSRF FSM state transition. +- (2) If the "DisconnectFromIPForbidden" parameter is FALSE, then the gsmSRF initiates a bearer channel disconnect sequence to the gsmSSF using the applicable bearer channel signalling system after sending the "SpecializedResourceReport" operation to the gsmSCF. The gsmSRF transits to the state "Idle". + +#### 11.30.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +## 11.31 SplitLeg Procedure + +### 11.31.1 General Description + +The gsmSCF uses this operation to request the gsmSSF to separate one party from the source Call Segment and place it in a new target Call Segment. + +#### 11.31.1.1 Parameters + +- legToBeSplit: +This parameter indicates the party in the call to be split from the source Call Segment. +- newCallSegment: +This parameter indicates the CSID to be assigned to the newly-created Call Segment. + +## 11.31.2 Responding entity (gsmSSF) + +### 11.31.2.1 Normal procedure + +gsmSSF preconditions: + +- 1) A control relationship exists between the gsmSCF and the gsmSSF. +- 2) The CSID1 is either the source Call Segment or the target Call Segment. +- 3) When SplitLeg is used to move a leg into CSID1 (when CSID1 does not exist), then the BCSM for the leg to be split shall be in the alerting phase or in the active phase. + +When SplitLeg is used to split a leg off from CSID1 into a new Call Segment, then the BCSM for the leg to be split shall be in the active phase. + +- 4) User interaction is not in progress in the source Call Segment. + +gsmSSF postconditions: + +- 1) The gsmSSF performs the necessary actions to separate the specified leg from its original Call Segment and place it in a new target Call Segment. +- 2) The CS\_gsmSSF FSM for the new Call Segment transits to the state "Waiting\_for\_Instructions". +- 3) The CS\_gsmSSF FSM for the source Call Segment transits to the state "Waiting\_for\_Instructions". +- 4) The remaining BCSM instances within the source Call Segment transit to the O\_Mid\_Call DP or to the T\_Mid\_Call DP, unless already suspended at a DP. The Mid\_Call EDP shall not be reported for this case. +- 5) A Return Result shall be sent to the gsmSCF immediately after successful execution of this operation. +- 6) A pending ApplyChargingReport for the source call segment shall be sent to the gsmSCF. + +### 11.31.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10, and the TC services which are used for reporting operation errors are described in clause 14. + +--- + +## 12 Detailed operation procedures for SMS control + +- NOTE: For Short Message processing in a Circuit Switched network, the CAMEL interaction with SMS is done through the MSC/smsSSF. +For Short Message processing in a Packet Switched network, the CAMEL interaction with SMS is done through the SGSN/smsSSF. + +Any reference to the smsSSF applies to both the smsSSF co-located with the MSC and the smsSSF co-located with the SGSN. + +- NOTE Where a parameter for an SMS control Operation is marked OPTIONAL in ASN.1, the reader is referred to the conditions for presence for this parameter, specified in the respective Information Flow in 3GPP TS 23.078 [7]. + +## 12.1 ConnectSMS procedure + +### 12.1.1 General description + +The gsmSCF uses this operation to request the smsSSF to continue Short Message processing, such as routeing a Short Message to a specific destination or delivering a Short Message to the served subscriber, with modified information. + +### 12.1.1.1 Parameters + +- callingPartyNumber: +This parameter allows the gsmSCF to set the Calling Party Number parameter used in the network. It is used for showing the sending party's id (i.e. the originating address) to the receiving party. +- destinationSubscriberNumber: +This parameter contains the destination address to which the Short Message shall be routed by the SMSC. +- smscAddress: +This parameter contains the Short Message Service Centre address towards which the Short Message shall be routed. + +## 12.1.2 Responding entity (smsSSF) + +### 12.1.2.1 Normal procedure + +smsSSF preconditions: + +- (1) Mobile originating Short Message submission or Mobile terminating Short Message delivery attempt has been initiated. +- (2) Short Message processing has been suspended at the DP SMS\_Collected\_Info or at DP SMS\_Delivery\_Requested. +- (3) The smsSSF FSM is in the state "Waiting\_for\_Instructions". + +smsSSF postconditions: + +- (1) The smsSSF performs the Short Message processing actions to route the Short Message to the specified destination or to deliver the Short Message to the served subscriber. + +On receipt of this operation, the smsSSF performs the following actions: + +- if the callingPartyNumber, destinationSubscriberNumber or smscAddress are supplied, then these values shall be used for subsequent processing; +- if no EDPs have been armed, then the smsSSF FSM transits to the state "Idle". Otherwise, the smsSSF FSM transits to the state "Monitoring". + +The smsSSF shall not perform any implicit arming or disarming of DPs. + +Statistic counter(s) are not affected. + +### 12.1.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 12.2 ContinueSMS procedure + +### 12.2.1 General description + +The gsmSCF uses this operation to request the smsSSF to proceed with processing at the DP at which it previously suspended processing to await gsmSCF instructions. The smsSSF continues processing without substituting new data from the gsmSCF. + +### 12.2.1.1 Parameters + +None. + +## 12.2.2 Responding entity (smsSSF) + +### 12.2.2.1 Normal procedure + +smsSSF preconditions: + +- (1) processing has been suspended at any DP. +- (2) The smsSSF FSM is in the state "Waiting\_for\_Instructions". + +smsSSF postconditions: + +- (1) processing continues. +- (2) The smsSSF FSM is in one of the following states: + - State "Monitoring" because at least one EDP was armed; or + - State "Idle" because no EDPs were armed. + +### 12.2.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +## 12.3 EventReportSMS procedure + +### 12.3.1 General description + +The smsSSF uses this operation to notify the gsmSCF of a short message related event previously requested by the gsmSCF in a RequestReportSMSEvent operation. + +#### 12.3.1.1 Parameters + +- eventTypeSMS: +This parameter identifies the type of event that is reported. +- eventSpecificInformationSMS: +This parameter contains the Short Message related information specific to the event. + - For O\_SMS\_Failure it shall contain the O-SMSCause, if available. + - For T\_SMS\_Failure it shall contain the T-SMSCause, if available. + - For O\_SMS\_Submitted and for T\_SMS\_Delivery it shall be empty. +- miscCallInfo: +This parameter contains DP related information. + - messageType: +This parameter indicates whether the message is a request, i.e. resulting from a RequestReportSMSEvent with "monitorMode" = "interrupted", or a notification, i.e. resulting from a RequestReportSMSEvent with "monitorMode" = "notifyAndContinue". + +### 12.3.2 Invoking entity (smsSSF) + +#### 12.3.2.1 Normal procedure + +smsSSF preconditions: + +- (1) The smsSSF FSM is in the state "Monitoring"; +- (2) The smsSSF FSM proceeds to an EDP that is armed. + +smsSSF postconditions: + +- (1) The smsSSF has applied implicit disarming of EDPs. +- (2) If message type was notification and there are no more EDPs armed, then the smsSSF FSM transits to the state "Idle". Otherwise, the smsSSF FSM transits to the state "Waiting\_for\_Instructions". + +### 12.3.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +## 12.4 FurnishChargingInformationSMS procedure + +### 12.4.1 General description + +The gsmSCF uses this operation to send charging related information to a Logical SMS record. This Logical SMS record is CAMEL specific. The first FurnishChargingInformationSMS operation leads to the generation of a Logical SMS record. Receipt of subsequent FurnishChargingInformationSMS operations shall overwrite or append the contents of the Logical SMS record. + +#### 12.4.1.1 Parameters + +- fCISMSBillingChargingCharacteristics: +This parameter contains the following parameters; +- fCIBCCCAMELsequence1: +This parameter contains the following parameters; +- freeFormatData: +This parameter contains free-format billing and/or charging characteristics. +- appendFreeFormatData: +This parameter indicates whether previous free-format data shall be appended or overwritten. See 3GPP TS 23.078 [7] for details. + +### 12.4.2 Responding entity (smsSSF) + +#### 12.4.2.1 Normal procedure + +smsSSF preconditions: + +- (1) The smsSSF FSM is in the state "Waiting\_for\_Instructions". + +smsSSF postconditions: + +- (1) No smsSSF FSM state transition. + +On receipt of this operation, the smsSSF performs actions to create the Logical SMS record, if a Logical SMS record does not already exist, and writes the free-format information carried in the operation into the Logical SMS record. Subsequent FurnishChargingInformationSMS operations received, by default, will overwrite the free-format data previously written in the Logical SMS record, as specified in 3GPP TS 23.078 [7]. It is also possible to append free format data with subsequent FurnishChargingInformationSMS operations. + +The Logical SMS records will be associated for a given Short Message submission or Short Message delivery with one or more physical CDRs, as specified in 3GPP TS 32.250 [13], 3GPP TS 32.251 [14] and 3GPP TS 22.115 [4]. + +#### 12.4.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 12.5 InitialDPSMS procedure + +### 12.5.1 General description + +The smsSSF uses this operation after detection of a TDP-R in the smsSF FSM, to request the gsmSCF for instructions to complete the Short Message submission to the SMSC or the Short Message delivery to the served subscriber. + +#### 12.5.1.1 Parameters + +- destinationSubscriberNumber: +This parameter carries the ISDN number of the entity receiving the short message or the destination address of the destination subscriber, in an MO-SMS procedure. +- callingPartyNumber: +In an MO-SMS procedure, this parameter carries the MSISDN of the subscriber. In an MT-SMS procedure, this parameter carries the address of the submitter of the short message (i.e. the originating address). +- eventType: +This parameter indicates the armed smSSF FSM DP, resulting in the InitialDPSMS operation. +- iMSI: +IMSI of the mobile subscriber for whom the CAMEL service is invoked. +- locationInformationInMSC: +This parameter indicates the location of the MSC of the served subscriber. This parameter shall be included only if the InitialDP operation is sent from the MSC. +- locationInformationInSGSN: +This parameter indicates the location of the SGSN of the served subscriber. This parameter shall be included only if the InitialDPSMS operation is sent from the SGSN. +- serviceKey: +This parameter indicates to the gsmSCF the requested IN service. It is used to address the required application/SLP within the gsmSCF; it is not for gsmSCF addressing. +- timeAndTimeZone: +This parameter contains the time that the smsSSF was triggered, and the time zone that the invoking smsSSF resides in. +- tPDataCodingScheme: +This parameter indicates the data coding scheme of the TP-User-Data element within the TPDU. It may indicate a message class. The message class may indicate e.g. the originator of the Short Message. +- tPShortMessageSpecificInfo: +This parameter contains the 1st octet of the TPDU. Refer to 3GPP TS 23.040 [6] for a description of the various TPUDUs. +- tPProtocolIdentifier: +This parameter indicates the protocol used above the SM-Transfer Layer. +- tPValidityPeriod: +This parameter indicates the length of the validity period or the absolute time of the validity period termination. +- sMSCAddress: +This parameter defines the address of the SMSC to which the Short Message is intended to be submitted. +- smsReferenceNumber: +This parameter contains the SMS Reference Number assigned to the Short Message by the MSC or SGSN. +- mscAddress: +This parameter contains the E.164 address of the MSC. It shall be present if the SMS processing takes place in the MSC; otherwise shall be absent. + +- **sgsn-Number:** +This parameter contains the Global Title of the SGSN. It shall be present if the SMS processing takes place in the SGSN; otherwise it shall be absent. +- **ms-Classmark2:** +This parameter contains the MS Classmark 2 of the mobile subscriber for which the service is invoked. +- **gPRSMSCClass:** +This parameter contains the GPRS MS capabilities of the mobile subscriber for which the CAMEL service is invoked. +- **iMEI:** +This parameter contains the IMEI (with software version) of the mobile subscriber for which the service is invoked. +- **calledPartyNumber:** +This parameter indicates the served subscriber in an MT-SMS procedure. + +## 12.5.2 Invoking entity (smsSSF) + +### 12.5.2.1 Normal procedure + +smsSSF preconditions: + +- (1) A Short Message submission attempt or a Short Message delivery attempt has been initiated. +- (2) An event has been detected at a DP. +- (3) For MT-SMS, the event fulfilled the criteria for the DP being executed. + +smsSSF postconditions: + +- (1) A control relationship has been established and the smsSSF waits for instructions from the gsmSCF. + +The address of the gsmSCF the InitialDPSMS operation shall be sent to, shall be fetched from the MO-SMS-CSI or the MT-SMS-CSI. The smsSSF shall provide all available parameters to the gsmSCF. + +A control relationship is established with the gsmSCF. The smsSSF application timer Tssf is laded with the deafult value and is started. It is used to prevent excessive Short Message submission or delivery suspension time. + +### 12.5.2.2 Error handling + +If the gsmSCF is not accessible, then the smsSSF instructs the MSC or SGSN to proceed with the Short Message processing in accordance with the Default SMS Handling parameter of the MO-SMS-CSI or MT-SMS-CSI. + +If Tssf expires, then the smsSSF aborts the interaction with the gsmSCF by means of an abort to TC and shall instruct the MSC or SGSN to proceed with the Short Message processing in accordance with the Default SMS Handling parameter of the MO-SMS-CSI CSI or MT-SMS-CSI. + +In the case of an MO-SMS Service, if the sending mobile party abandons after the sending of InitialDPSMS and before the TC dialogue is established, then the smsSSF shall abort the interaction with the gsmSCF by means of an abort to TC. + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 12.6 ReleaseSMS procedure + +### 12.6.1 General description + +The gsmSCF uses this operation to tear down a Short Message submission attempt or Short Message delivery attempt. The operation may be sent within a control relationship only; it is not allowed in a monitor relationship. + +#### 12.6.1.1 Parameters + +- rPCause: +This parameter gives an indication to the smsSSF about the reason of releasing this specific Short Message. For a MO-SMS Service, the rPCause shall be sent to the served subscriber in the RP-ERROR RPDU. For a MT-SMS Service, the rPCause shall be sent to the SMS-GMSC in the RP-ERROR RPDU. + +### 12.6.2 Responding entity (smsSSF) + +#### 12.6.2.1 Normal procedure + +smsSSF preconditions: + +- (1) The smsSSF FSM is in the state "Waiting\_for\_Instructions". +- (2) The FSM is in DP SMS\_Collected\_Info or in DP SMS\_Delivery\_Requested. + +smsSSF postconditions: + +- (1) The smsSSF FSM transits to the state "Idle". All armed EDPs shall be disarmed. All resources in the MSC or SGSN related to the Short Message shall be released. + +#### 12.6.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +## 12.7 RequestReportSMSEvent procedure + +### 12.7.1 General description + +The gsmSCF uses this operation to request the smsSSF to monitor for a Short Message related event (FSM events such as failure, delivery or submission) and to send a notification to the gsmSCF when the event is detected. + +The monitoring of more than one event may be requested with a single RequestReportSMSEvent operation, but each of these requested events will be reported in a separate EventReportSMS operation. + +#### 12.7.1.1 Parameters + +- smsEvents: +This parameter indicates the event or events of which a report is requested. + - eventTypeSMS: +This parameter indicates the type of event of which a report is requested. Values SMSCollectedInfo and SMSDeliveryRequested are not valid for the RequestReportSMSEvent operation. + - monitorMode: +This parameter indicates how the event shall be reported. When the "monitorMode" is "interrupted", the event shall be reported as a request, if the "monitorMode" is "notifyAndContinue", the event shall be reported as a notification, if the "monitorMode" is "transparent", then the event shall not be reported. + +### 12.7.2 Responding entity (smsSSF) + +#### 12.7.2.1 Normal procedure + +smsSSF preconditions: + +- (1) A control relationship exists between the smsSSF and the gsmSCF. +- (2) The smsSSF FSM is in the state "Waiting\_for\_Instructions". + +smsSSF postconditions: + +- (1) The requested EDPs have been armed or disarmed as indicated. +- (2) Armed events are monitored until ended by a transparent monitor mode, until the occurrence of the event or until the implicit disarming of the event. +- (3) No smsSSF FSM state transition. + +### 12.7.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 12.8 ResetTimerSMS procedure + +### 12.8.1 General description + +The gsmSCF uses this operation to refresh the Tssf application timer, in order to prevent Tssf expiry at the smsSSF. + +#### 12.8.1.1 Parameters + +- timerID: +This parameter indicates which timer shall be reset. The only permissible value of this parameter is "tssf". +- timerValue: +This parameter defines the value to which the timer shall be set. + +### 12.8.2 Responding entity (smsSSF) + +#### 12.8.2.1 Normal procedure + +smsSSF preconditions: + +- (1) Short Message processing has been suspended at a DP. +- (2) The smsSSF FSM is in the state "Waiting\_for\_Instructions". + +smsSSF postconditions: + +- (1) The Tssf timer is loaded with the value received from the gsmSCF and is restarted. +- (2) No smsSSF FSM state transition. + +#### 12.8.2.2 Error handling + +Generic error handling for the operation related errors are described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +--- + +## 13 Detailed operation procedures for GPRS control + +NOTE Where a parameter for a GPRS control Operation is marked OPTIONAL in ASN.1, the reader is referred to the conditions for presence for this parameter, specified in the respective Information Flow in 3GPP TS 23.078 [7]. + +## 13.1 ActivityTestGPRS procedure + +### 13.1.1 General description + +The gsmSCF uses this operation to check for the continued existence of a relationship between the gsmSCF and the gprsSSF. If the relationship is still in existence, then the identified instance of gprsSSF will respond. If the ActivityTestGPRS operation timer expires, then the gsmSCF will assume that the receiving entity has failed in some way and will take appropriate action. This operation opens a new SS7 dialogue between gsmSCF and gprsSSF. + +#### 13.1.1.1 Parameters + +None. + +### 13.1.2 Responding entity (gprsSSF) + +#### 13.1.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) A relationship exists between the gsmSCF and the gprsSSF. +- (2) The gprsSSME FSM is in the state "Idle Management". +- (3) No active TC dialogue exists at the moment of receiving ActivityTestGPRS. + +gprsSSF postconditions: + +- (1) The gprsSSME FSM transits to the state "Non-call Associated Treatment". +- (2) If there is a gprsSSF using the GPRS-Reference Number, then the gprsSSME FSM sends a Return Result "ActivityTestGPRS" to the gsmSCF. The gprsSSME FSM then returns to the state "Idle Management". + +If there is no gprsSSF using the GPRS-ReferenceNumber, then the gprsSSME FSM will issue a U-Abort. The gprsSSME FSM then returns to the state "Idle Management". + +- (3) The temporary TC dialogue is closed. + +If at the time of receiving ActivityTestGPRS there is an active TC dialogue for this GPRS Dialogue, then the gprsSSME FSM issues a U-Abort with Abort reason "overlapping-dialogue". + +#### 13.1.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services used for reporting operation errors are described in clause 14. + +## 13.2 ApplyChargingGPRS procedure + +### 13.2.1 General description + +The gsmSCF uses this operation for interacting with the gprsSSF function "CSE control of GPRS session or PDP Context duration and volume". The ApplyChargingGPRSReport operation provides the feedback from the gprsSSF to the gsmSCF. The charging scenarios supported by this operation are those given in 3GPP TS 22.078 [3] for "CSE control of GPRS session and PDP Context duration and volume". + +If this procedure is used within a PDP Context dialogue, then the charging instruction shall pertain to the PDP Context only. Data volume threshold and duration threshold may be defined separately. + +If this procedure is used within a GPRS Session dialogue, then the charging instruction may pertain to the GPRS Session or to a single PDP Context. Charging for a PDP Context may be on duration and/or volume. Charging for a GPRS Session may be on duration only. + +NOTE: Charging for a PDP Context on duration and volume requires two ApplyChargingGPRS operations. + +### 13.2.1.1 Parameters + +- **chargingCharacteristics:** +This parameter is a choice between parameters required for "CSE control of a GPRS session or a PDP Context duration or volume": + - **maxTransferredVolume:** +This parameter specifies the maximum volume that may be transferred before a ApplyChargingReportGPRS shall be sent to the gsmSCF. + - **maxElapsedTime:** +This parameter specifies the maximum period of time before a ApplyChargingReportGPRS shall be sent to the gsmSCF. +- **tariffSwitchInterval:** +This parameter indicates the time duration until the next tariff switch. The measurement of the elapsed tariff switch period shall start immediately after successful execution of this operation. +- **pDPID:** +This parameter identifies the PDP Context, within the GPRS Session dialogue, to which the charging instruction applies. + +## 13.2.2 Responding entity (gprsSSF) + +### 13.2.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) A control relationship exists between the gsmSCF and the GPRS Session or PDP Context to which the operation applies. +- (2) The gprsSSF FSM is in one of the following states: "Waiting\_for\_Instructions" or "Monitoring". + +gprsSSF postconditions: + +- (1) No gprsSSF FSM state transition. + +On receipt of this operation, the gprsSSF shall set the charging data using the information elements included in the operation. + +### 13.2.2.2 Error handling + +"TaskRefused": In addition to the generic error handling noted below, this error shall be indicated when: + +- a previously received GPRS Session or PDP Context period or volume duration is pending; +- a tariffSwitchInterval is indicated when a previously received tariffSwitchInterval is pending; +- the gprsSSF has received an ApplyChargingGPRS operation for a PDP Context that is already disconnected; +- the gprsSSF has received an ApplyChargingGPRS operation for the GPRS Session when the subscriber is already detached. + +Generic error handling for the operation related errors is described in clause 10 and the TC services used for reporting operation errors are described in clause 14. + +## 13.3 ApplyChargingReportGPRS procedure + +### 13.3.1 General description + +The gprsSSF uses this operation to report charging related information to the gsmSCF as requested by the gsmSCF using the ApplyChargingGPRS operation. + +Timing of duration and measuring of transferred data (if applicable) shall be started when either an Attach, PDP Context Establishment Acknowledgement or an Inter SGSN Routeing Area Update acceptance is detected by the gprsSSF. + +A report shall be made when a PDP Context Disconnect, a Detach or a Change in QoS is detected by the gprsSSF or when the gprsSSF detects that the transferred volume or elapsed time duration indicated in the parameter "transferredVolume" or "elapsedTime" (received in ApplyChargingGPRS operation) has been reached. ApplyChargingReportGPRS shall be sent only on chargeable QoS changes. + +### 13.3.1.1 Parameters + +- **chargingResult:** + +This parameter provides the gsmSCF with the charging related information previously requested using the ApplyChargingGPRS operation. The "ChargingResult" is a choice, and can contain either of the following parameters: + +- **transferredVolume:** + +This is a choice of the following parameters: + +- **volumeIfNoTariffSwitch:** + +This parameter shall be present if no tariff switch has occurred for the PDP Context, otherwise it shall be absent. If present, then the volume transferred since the detection of the event that triggered volume count shall be reported. + +- **volumeIfTariffSwitch:** + +This parameter shall be present if a tariff switch has occurred for the PDP Context, otherwise it shall be absent. This parameter may contain the following information: + +- **volumeSinceLastTariffSwitch:** + +The volume since the detection of the event that triggered volume count or the last tariffSwitch (whichever of these events was last detected) shall be reported. + +- **VolumeTariffSwitchInterval:** + +This parameter shall be present only if a tariff switch was detected after the event that triggered volume count for the PDP Context in the current volume count period. If present, the volume between either the detection the event that triggered volume count or the previous tariff switch (whichever of these events was last detected) and the last tariff switch shall be reported. + +- **elapsedTime:** + +This parameter is a choice of the following parameters: + +- **timeGPRSIfNoTariffSwitch:** + +This parameter shall be present if no tariff switch has occurred for the GPRS Session or the PDP Context, otherwise it shall be absent. If present, then the elapsed time since the detection of the event that triggered time count shall be reported. + +- **timeGPRSIfTariffSwitch:** + +This parameter shall be present if a tariff switch has occurred for the GPRS Session or the PDP Context, otherwise it shall be absent. This parameter may contain the following information: + +- **timeGPRSSinceLastTariffSwitch:** + +The time since the event that triggered time count or the last tariffSwitch shall be reported. + +- **timeGPRSTariffSwitchInterval:** + +This parameter shall be present only if a tariff switch was detected after the event that triggered time count for the GPRS Session or PDP Context in the current time count period. If present, then the time between either the detection the event that triggered time count or the previous tariff switch (whichever of these events was last detected) and the last tariff switch shall be reported. + +- **qualityOfService:** + +This parameter identifies the QoS which was negotiated between the user, the SGSN and the GGSN. + +This parameter shall be present only if the sending of the ApplyChargingReportGPRS operation was triggered by a change in Quality of Service. The "negotiated-QoS-Extension" may be present as a supplement to the "negotiated-QoS". + +- active: +This parameter indicates whether the GPRS Session or PDP Context is still active +- pDPID: +This parameter identifies the PDP Context, within the GPRS Session dialogue, for which the charging report is valid. +- chargingRollOver: +This parameter indicates possible rollovers of the "ChargingResult" parameter due to the limited value ranges of the associated charging parameters. The "chargingRollOver" parameter is a choice and may contain either of the following parameters: + - transferredVolumeRollOver: +This parameter is a choice of the following parameters: + - rO-VolumeIfNoTariffSwitch: +This parameter indicates how many times the volumeIfNoTariffSwitch parameter of the chargingResult has rolled over. If no rollover has happened, then rO-VolumeIfNoTariffSwitch may be absent. + - rO-VolumeIfTariffSwitch: +This parameter is present if at least one of the parameters below is present. It may contain the following information: + - rO-VolumeSinceLastTariffSwitch: +This parameter indicates how many times the volumeSinceLastTariffSwitch parameter of the chargingResult has rolled over. If no rollover has happened, then rO-VolumeSinceLastTariffSwitch may be absent. + - rO-VolumeTariffSwitchInterval: +This parameter indicates how many times the VolumeTariffSwitchInterval parameter of the chargingResult has rolled over. If no rollover has happened, then rO-VolumeTariffSwitchInterval may be absent. + - elapsedTimeRollOver: +This parameter is a choice of the following parameters: + - rO-TimeGPRSIfNoTariffSwitch: +This parameter indicates how many times the timeGPRSIfNoTariffSwitch parameter of the chargingResult has rolled over. If no rollover has happened, then rO-TimeGPRSIfNoTariffSwitch may be absent. + - rO-TimeGPRSIfTariffSwitch: +This parameter shall be present if at least one of the parameters below is present. If It may contain the following information: + - rO-TimeGPRSSinceLastTariffSwitch: +This parameter indicates how many times the timeGPRSSinceLastTariffSwitch parameter of the chargingResult has rolled over. If no rollover has happened, then rO-TimeGPRSSinceLastTariffSwitch may be absent. + - rO-TimeGPRSTariffSwitchInterval: +This parameter indicates how many times the timeGPRSTariffSwitchInterval parameter of the chargingResult has rolled over. If no rollover has happened, then rO-TimeGPRSTariffSwitchInterval may be absent. + +## 13.3.2 Invoking entity (gprsSSF) + +### 13.3.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) A relationship exists between the gsmSCF and the GPRS Session or PDP Context. +- (2) A charging event has been detected that was requested by the gsmSCF via an ApplyChargingGPRS operation. + +gprsSSF postconditions: + +- (1) If termination of the GPRS Session or a PDP Context has occurred, then: + - If the sending of ApplyChargingReportGPRS is directly followed by the reporting of an EDP-R, then the gprsSSF FSM shall transit to the state "Waiting\_for\_Instructions"; else + - If there are any armed EDPs or pending reports, then the gprsSSF FSM shall remain in the same state; else + - If there are no armed EDPs or pending reports, then the gprsSSF FSM shall transit to the state "Idle". +- (2) If the sending of ApplyChargingReportGPRS is due to a timer or counter expiry, then: + - If there are any armed EDPs or pending reports, then the gprsSSF FSM shall remain in the same state; else + - If there are no armed EDPs or pending reports, then the gprsSSF FSM shall transit to the state "Idle". +- (3) If the sending of ApplyChargingReportGPRS is due to a change in QoS of a PDP Context, then: + - The gprsSSF FSM shall remain in the same state. + +### 13.3.2.2 Error handling + +If the operation timer expires, then the gprsSSF shall abort the TC dialogue, terminate the GPRS dialogue and instruct the SGSN to handle the GPRS session or PDP context in accordance with the default GPRS handling parameter of the valid CSI. + +Generic error handling for the operation related errors is described in clause 10 and the TC services used for reporting operation errors are described in clause 14. + +## 13.4 CancelGPRS procedure + +### 13.4.1 General description + +The gsmSCF uses this operation to request the gprsSSF to disarm all pending EDPs and to cancel all pending reports for a GPRS Session or for a specific PDP Context. This enables the gprsSSF FSM to transit to the state "Idle". This procedure can not be used to cancel a previous operation. + +#### 13.4.1.1 Parameters + +- pDPID: +This parameter identifies the PDP Context, within the GPRS Session dialogue, for which the armed EDPs shall be disarmed and the pending reports shall be cancelled. + +### 13.4.2 Responding entity (gprsSSF) + +#### 13.4.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) The gprsSSF FSM is in the state "Waiting\_for\_Instructions" or in the state "Monitoring". + +gprsSSF postconditions: + +- (1) All pending ApplyChargingReportGPRS are cancelled and all pending EDPs are disarmed. If a PDPID is included in the operation, then the cancelling of the pending reports and the disarming of the armed events applies to the indicated PDP Context only. +- (2) If the gprsSSF FSM was in the state "Monitoring" and there are no more armed EDPs or pending ApplyChargingReportsGPRS, then the gprsSSF FSM shall transit to the state "Idle". + +If the gprsSSF FSM was in the state "Waiting\_for\_Instructions", it shall remain in that state. If there are no more armed EDPs or pendingApplyChargingReportsGPRS, then subsequent GPRS Session or PDP Context processing operation will result in the gprsSSF FSM to transit the state "Idle". + +The GPRS Session or PDP Context to which the CancelGPRS operation applies, if in active state, shall further be treated by the gprsSSF autonomously as a normal (non-CAMEL) GPRS Session or PDP Context. + +### 13.4.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 13.5 ConnectGPRS procedure + +### 13.5.1 General description + +The gsmSCF uses this operation to provide an APN to the gprsSSF, to be used for establishing a PDP Context. + +#### 13.5.1.1 Parameters + +- accessPointName: +This parameter contains the Access Point Name towards which the PDP Context shall be established. Refer to 3GPP TS 29.060 [12] for details on the Access Point Name. +- pDPID: +This parameter identifies the PDP Context, within the GPRS Session dialogue, for which the Access Point Name shall be used. + +### 13.5.2 Responding entity (gprsSSF) + +#### 13.5.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) A control relationship exists between the gsmSCF and the PDP Context. +- (2) The GPRS PDP Context FSM is suspended at DP PDP\_Context\_Establishment. +- (3) The gprsSSF FSM is in the state "Waiting\_for\_Instructions". + +gprsSSF postconditions: + +- (1) The gprsSSF performs the actions to establish the PDP Context using the given Access Point Name. +- (2) The gprsSSF stops Tssf. +- (3) If no EDPs are armed, then the gprsSSF FSM transits to the state "Idle". Otherwise the gprsSSF FSM transits to the state "Monitoring". + +The gsmSSF shall not perform any implicit arming or disarming of DPs. + +#### 13.5.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 13.6 ContinueGPRS procedure + +### 13.6.1 General description + +The gsmSCF uses this operation to request the gprsSSF to proceed with GPRS Session or PDP Context processing at the DP at which it previously suspended processing to await gsmSCF instructions. The gprsSSF continues processing without substituting new data from the gsmSCF. + +### 13.6.1.1 Parameters + +- pDPID: +This parameter identifies the PDP Context within the control relationship for which the processing shall continue. + +## 13.6.2 Responding entity (gprsSSF) + +### 13.6.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) A control relationship exists between the gsmSCF and the GPRS Session or PDP Context. +- (2) The GPRS Session or PDP Context processing has been suspended at any DP. +- (3) The gprsSSF FSM is in the state "Waiting\_for\_Instructions". + +gsmSSF postconditions: + +- (1) GPRS Session or PDP Context processing continues. +- (2) The gprsSSF FSM is in one of the following states: + - "Monitoring" because at least one EDP was armed or an ApplyChargingReportGPRS was requested; or + - "Idle" because no EDPs were armed and no ApplyChargingReportGPRS was requested. + +### 13.6.2.2 Error handling + +Operation related error handling is not applicable, due to class 4 operation. + +## 13.7 EntityReleasedGPRS procedure + +### 13.7.1 General description + +The gprsSSF uses this operation to inform the gsmSCF that the GPRS Session is detached or a PDP Context is disconnected. It shall be used only when the associated event detection point (ie. for GPRS Session Detach: DP "Detach" and for PDP Context Disconnect: DP "PDP Context Disconnection") is at that moment not armed for reporting. + +This operation shall be used irrespectively of the functional entity that initiated the Detach or PDP Context Disconnect and irrespectively of the cause for the Detach or PDP Context Disconnect. + +When a PDP Context is terminated, then the gprsSSF shall send all pending reports of that PDP Context to the gsmSCF. When a GPRS Session is terminated, then the gprsSSF shall send all outstanding reports of the GPRS Session to the gsmSCF. + +### 13.7.1.1 Parameters + +- gPRSCause: +This parameter gives an indication to the gsmSCF about the reason for discontinuing the PDP Context or GPRS Session. This may be used by gsmSCF if a FurnishChargingInformationGPRS operation needs to be sent to the gprsSSF. +- pDPID: +This parameter identifies the PDP Context within the GPRS Session dialogue, which has terminated. + +### 13.7.2 Invoking entity (gprsSSF) + +### 13.7.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) The gprsSSF FSM is in the state "Waiting\_for\_Instructions" or in the state "Monitoring". + +gprsSSF postconditions: + +- (1) All armed EDPs for the indicated PDP Context or GPRS Session shall be disarmed. All connections and resources related to the indicated PDP Context or GPRS Session shall be released. +If there are no more armed EDPs or pending reports, then the gprsSSF FSM transits to the state "Idle"; otherwise the gprsSSF FSM remains in the same state. + +### 13.7.2.2 Error handling + +If the operation timer expires, then the gprsSSF shall abort the TC dialogue, terminate the GPRS dialogue and instruct the SGSN to handle the GPRS session or PDP context in accordance with the default GPRS handling parameter of the valid CSI. + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 13.8 EventReportGPRS procedure + +### 13.8.1 General description + +The gprsSSF uses this operation to notify the gsmSCF of a GPRS Session or PDP Context event previously requested by the gsmSCF in a RequestReportGPRSEvent operation. + +#### 13.8.1.1 Parameters + +- gPRSEventType: +This parameter specifies the type of event that is reported. +- gPRSEventSpecificInformation: +This parameter indicates the GPRS Session or PDP Context related information specific to the event. + +For Change of Position GPRS Session it shall contain the "locationInformationGPRS", if available. + +For Change of Position PDP Context it shall contain the "accessPointName", "chargingID", "locationInformationGPRS", "endUserAddress", Quality of Service, "timeAndTimeZone" and "gGSNAddress" and "secondaryPDP-context", if available. + +For Detach and PDP Context Disconnect it shall contain the "initiatingEntity" and, conditionally, "routeingAreaUpdate". The "initiatingEntity" indicates the entity that initiated the Detach or PDP Context Disconnect. The "routeingAreaUpdate" indicates that the Detach or PDP Context Disconnect is due to inter-SGSN routeing area update. + +In the case of inter-SGSN routeing area update, the gsmSCF may ignore the "initiatingEntity". + +For PDP Context Establishment it shall contain the "accessPointName", "endUserAddress", "pDPInitiationType", Quality of Service, "locationInformationGPRS", "timeAndTimeZone" and "secondaryPDP-context", if available. + +The Quality of Service shall contain the Requested QoS and the Subscribed QoS. The "requested-QoS-Extension" and the "subscribed-QoS-Extension" may be present as supplements to the "requested-QoS" and the "subscribed-QoS" respectively. + +For PDP Context Establishment Acknowledgement it shall contain the "accessPointName", "chargingID", "endUserAddress", Quality of Service, "locationInformationGPRS", "timeAndTimeZone" and "gGSNAddress", if available. + +The Quality of Service shall contain the Requested QoS, the Subscribed QoS and the Negotiated QoS. The "requested-QoS-Extension", the "subscribed-QoS-Extension" and the "negotiated-QoS-Extension" may be present as supplements to the "requested-QoS", the "subscribed-QoS" and the "negotiated-QoS" respectively. + +All optional gPRSEventSpecificInformation parameters shall be sent in accordance with 3GPP TS 23.078 [7] subclause 6.6.1.4 and 3GPP TS 22.078 [3] annex "GPRS Information provided to the CSE". + +- miscGPRSInfo: +This parameter contains DP related information. + +- messageType: +This parameter indicates whether the message is a request, i.e. resulting from a RequestReportGPRSEvent with "monitorMode" = "interrupted", or a notification, i.e. resulting from a RequestReportGPRSEvent with "monitorMode" = "notifyAndContinue". +- pDPID: +This parameter identifies the PDP Context, within the GPRS Session dialogue, for which the event is reported. + +## 13.8.2 Invoking entity (gprsSSF) + +### 13.8.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) The gprsSSF FSM is in the state "Monitoring" or in the state "WaitingForInstructions". +- (2) The GPRS Session or PDP Context FSM proceeds to an EDP that is armed. + +gprsSSF postconditions: + +- (1) If the message type was notification and there are still armed EDPs that can be met or there are any pending reports, then the gprsSSF FSM shall remain in the state "Monitoring". +- (2) If the message type was notification and there are no more EDPs armed that can be met and there are no pending reports, then the gprsSSF FSM shall transit to the state "Idle". +- (3) If the message type was request, then the gprsSSF FSM shall transit to the state "Waiting\_for\_Instructions". +GPRS Session or PDP Context processing is interrupted. + +If an EDP-R is met that causes the release of a GPRS Session or PDP Context, then all EDPs related to the GPRS Session or PDP Context shall be disarmed. + +### 13.8.2.2 Error handling + +If the operation timer expires, then the gprsSSF shall abort the TC dialogue, terminate the GPRS dialogue and instruct the SGSN to handle the GPRS session or PDP context in accordance with the default GPRS handling parameter of the valid CSI. + +If the message type is "request" and the Tssf timer expires, then the gprsSSF shall abort the TC dialogue and shall instruct the SGSN to treat the GPRS Session or PDP Context in accordance with the default GPRS handling of the valid CSI. + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 13.9 FurnishChargingInformationGPRS procedure + +### 13.9.1 General description + +The gsmSCF uses this operation to send charging related information to a Logical GPRS record. This Logical GPRS record is CAMEL specific. The first FurnishChargingInformationGPRS operation results in the generation of a Logical GPRS record. Receipt of subsequent FurnishChargingInformationGPRS operations shall overwrite or append the contents of the Logical GPRS record. + +#### 13.9.1.1 Parameters + +- fCIGPRSBillingChargingCharacteristics: +This parameter contains the following parameters; +- fCIBCCCAMELsequence1: +This parameter contains the following parameters; +- freeFormatData: +This parameter contains free-format billing and/or charging characteristics. + +- appendFreeFormatData: +This parameter indicates whether previous FCI free format data is appended or overwritten. Refer to 3GPP TS 23.078 [7] for details of this mechanism. +- pDPID: +This parameter indicates the PDP Context's Logical GPRS record to which the free format data belongs. + +## 13.9.2 Responding entity (gprsSSF) + +### 13.9.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) The gprsSSF FSM is in the state "Waiting\_for\_Instructions" or in the state "Monitoring". + +gprsSSF postconditions: + +- (1) No gprsSSF FSM state transition. + +On receipt of this operation the gprsSSF performs actions to create the Logical GPRS record, if necessary, and writes the free-format information carried in the operation into the GPRS record. A FurnishChargingInformationGPRS operation will create a Logical GPRS Data Record (CDR) if such a record does not already exist. Subsequent FurnishChargingInformationGPRS operations received, will either overwrite or append the data previously written in the free-format CDR field depending on the presence and value of the parameter "appendFreeFormatData". + +The Logical GPRS records will be associated for a given GPRS Session or PDP Context with one or more physical CDRs, as specified in 3GPP TS 32.250 [14] and 3GPP TS 22.115 [4]. + +### 13.9.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 13.10 InitialDPGPRS procedure + +### 13.10.1 General description + +The gprsSSF uses this operation after detection of a TDP-R in the GPRS Session or PDP Context state machine, to request the gsmSCF for instructions to complete the GPRS Session or PDP Context. + +For a GPRS Session, the "Attach" and "Change of Position Session" TDPs may result in the InitialDPGPRS Procedure. + +For a PDP Context, the "PDP Context Establishment", the "PDP Context Establishment Acknowledgement" and the "Change of Position Context" TDPs may result in the InitialDPGPRS Procedure. + +If a PDP Context related TDP is met and there is at that moment a GPRS dialogue for the GPRS Session, then the gprsSSF shall not initiate the InitialDPGPRS Procedure for that PDP Context. + +If the "PDP Context Establishment Acknowledgement" event occurs and this event is armed as a TDP, and there is at that moment a GPRS dialogue for the PDP Context, then the gprsSSF shall not initiate a new InitialDPGPRS Procedure for that PDP Context. + +#### 13.10.1.1 Parameters + +- serviceKey: +This parameter indicates to the gsmSCF the requested IN service. It is used to address the required application/SLP within the gsmSCF; it is not used for SCP addressing. +- gPRSEventType: +This parameter indicates the armed GPRS Attach/Detach FSM or PDP Context FSM DP event, resulting in the InitialDPGPRS operation. +- mSISDN: +This parameter contains the MSISDN of the mobile subscriber for which the CAMEL service is invoked. + +- iMSI: +This parameter contains the IMSI of the mobile subscriber for which the CAMEL service is invoked. +- timeAndTimezone: +This parameter contains the time that the gprsSSF is triggered, and the time zone that the invoking gprsSSF resides in. +- gPRSMSCClass: +This parameter contains the MS capabilities of the mobile subscriber for which the CAMEL service is invoked. +- endUserAddress: +This parameter identifies the PDP type, PDP type organisation and the actual PDP address. +- qualityOfService: +This parameter contains the Quality of Service. +If the InitialDPGPRS operation is sent as a result of the "PDP Context Establishment" TDP, then the Quality of Service parameter shall contain the Requested QoS and the Subscribed QoS. The "requested-QoS-Extension" and the "subscribed-QoS-Extension" may be present as supplements to the "requested-QoS" and the "subscribed-QoS" respectively. +If the InitialDPGPRS operation is sent as a result of the "PDP Context Establishment Acknowledgement" TDP or the Change of Position Context TDP, then the Quality of Service parameter shall contain the Requested QoS, the Subscribed QoS and the Negotiated QoS. The "requested-QoS-Extension", the "subscribed-QoS-Extension" and the "negotiated-QoS-Extension" may be present as supplements to the "requested-QoS", the "subscribed-QoS" and the "negotiated-QoS" respectively. +- accessPointName: +This parameter contains the requested address that the MS for which the CAMEL service is invoked for wants to connect to. +- routeingAreaIdentity: +This parameter contains the location information of the MS for which the CAMEL service is invoked. +- chargingID: +This parameter contains the charging ID that, together with the gGSNAddress, uniquely identifies the PDP Context for the MS for which the CAMEL service is invoked. +- sGSNcapabilities: +This parameter specifies the capabilities which the SGSN node can provide for the CAMEL service control. +- locationInformationInSGSN: +This parameter indicates the location of the sending MS. +- pDPInitiationType: +This parameter indicates whether a PDP Context was established as a result of a network-initiated request or as a result of a subscriber request. +- gGSNAddress: +This parameter refers to the IP address of the GGSN where the PDP Context terminates. It is used together with the chargingID for uniquely identification of the PDP Context for which the CAMEL service is invoked from. +- secondaryPDP-context: +This parameter indicates that the PDP Context is requested as a secondary PDP Context. +- iMEI: +This parameter contains the IMEI (with software version) of the mobile subscriber for which the service is invoked. + +## 13.10.2 Invoking entity (gprsSSF) + +### 13.10.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) An event has been met that is armed as TDP. +- (2) There is no GPRS dialogue active for that PDP Context or for the GPRS Session. + +gprsSSF postconditions: + +- (1) A control relationship is established between the gsmSCF and the GPRS Session or the PDP Context. +- (2) The gprsSSF FSM is in the state "Waiting\_for\_Instructions". + +The address of the gsmSCF that the InitialDPGPRS operation shall be sent to, shall be fetched from the valid CSI. The gprsSSF shall provide all available parameters to the gsmSCF. + +The gprsSSF application timer Tssf shall be loaded and started when the gprsSSF sends InitialDPGPRS for requesting instructions from the gsmSCF. It is used to prevent excessive GPRS Session or PDP Context duration or volume usage. + +### 13.10.2.2 Error handling + +If the gsmSCF is not accessible, then the gprsSSF instructs the SGSN to handle the GPRS Session or PDP Context in accordance with the Default GPRS Handling parameter of the valid CSI. + +If Tssf expires, then the gprsSSF shall abort the interaction with the gsmSCF by means of an abort to TC and shall instruct the SGSN to handle the GPRS Session or PDP Context in accordance with the Default GPRS Handling parameter of the valid CSI. + +If the MS abandons the establishment of a GPRS Session or PDP Context after the sending of InitialDPGPRS and before the TC dialogue is established, then the gprsSSF shall abort the interaction with the gsmSCF by means of an abort to TC. + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 13.11 ReleaseGPRS procedure + +### 13.11.1 General description + +The gsmSCF uses this operation to tear down by the gsmSCF an existing GPRS Session or PDP Context at any phase. + +#### 13.11.1.1 Parameters + +- gPRSCause: +This parameter gives an indication to the gprsSSF about the reason of releasing the GPRS Session or a specific PDP Context. This may be used by gprsSSF for generating specific indications to the MS or to fill in the "cause" in the release message. +- pDPID: +This parameter identifies the PDP Context, within the GPRS Session dialogue, which shall be released. + +### 13.11.2 Responding entity (gprsSSF) + +#### 13.11.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) A control relationship exists between gsmSCF and the GPRS Session or PDP Context. More specifically, in order to tear down an individual PDP Context, an EDP-R must be armed for that PDP Context. In order to make a SCP controlled detach an EDP-R must be armed for the GPRS Session. +- (2) The gprsSSF FSM is in the state "Waiting\_for\_Instructions" or in the state "Monitoring". + +gprsSSF postconditions: + +- (1) All pending reports for the GPRS Session or the PDP Context shall be reported to the gsmSCF. +- (2) All connections and resources related to the GPRS Session or the PDP Context shall be released. +- (3) All armed EDPs for the GPRS Session or the PDP Context shall be disarmed. + +- (4) If there are no more pending reports or armed events, then the gprsSSF FSM transits to the state "Idle". + +If there are any pending reports or armed events, then the gprsSSF FSM remains in the same state. + +### 13.11.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 13.12 RequestReportGPRSEvent procedure + +### 13.12.1 General description + +The gsmSCF uses this operation to request the gprsSSF to monitor for a GPRS Session or PDP Context related event (e.g., events such as PDP Context establishment or detach) and to send a notification to the gsmSCF when the event is detected. + +The monitoring of more than one event may be requested with a single RequestReportGPRSEvent operation, but each of these requested events will be reported in a separate EventReportGPRS operation. + +#### 13.12.1.1 Parameters + +- gPRSEvent: +This parameter specifies the event or events of which a report is requested. +- gPRSEventType: +This parameter specifies the type of event of which a report is requested. +- monitorMode: +This parameter indicates how the event shall be reported. If the "monitorMode" is "interrupted", then the event shall be reported as a request; if the "monitorMode" is "notifyAndContinue", then the event shall be reported as a notification; if the "monitorMode" is "transparent", then the event shall not be reported. +- pDPID: +This parameter identifies the PDP Context, within the GPRS Session dialogue, for which the event reporting is requested + +### 13.12.2 Responding entity (gprsSSF) + +#### 13.12.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) A control relationship exists between the gsmSCF and the GPRS Session or PDP Context. +- (2) The gprsSSF FSM is in the state "Waiting\_for\_Instructions" or the state "Monitoring". + +In the state "monitoring" only requests to disarm detection points (with MonitorMode set to "Transparent") or send notifications of events (with MonitorMode set to "NotifyAndContinue") shall be accepted. + +gprsSSF postconditions: + +- (1) The requested EDPs have been armed or disarmed as indicated. +- (2) Previously requested events are monitored until ended by a transparent monitor mode, until the end of the GPRS Session or PDP Context or until the EDPs are detected. +- (3) If there are no armed events or pending reports, then the gsmSSF FSM shall transit to the state "Idle". Otherwise it shall remain in the same state. + +#### 13.12.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 13.13 ResetTimerGPRS procedure + +### 13.13.1 General description + +The gsmSCF uses this operation to refresh the Tssf application timer, in order to avoid the Tssf time-out at the gprsSSF. + +#### 13.13.1.1 Parameters + +- timerID: +This parameter indicates which timer shall be reset. The only permissible value for this parameter is "Tssf". +- timerValue: +This parameter specifies the value to which the timer shall be set. + +### 13.13.2 Responding entity (gprsSSF) + +#### 13.13.2.1 Normal procedure + +gprsSSF preconditions: + +- (1) GPRS Session or PDP Context processing has been suspended at a DP. +- (2) The gprsSSF FSM is in the state "Waiting\_for\_Instructions". + +gprsSSF postconditions: + +- (1) The Tssf timer is loaded with the value received from the gsmSCF and is restarted. +- (2) No gprsSSF FSM state transition. + +#### 13.13.2.2 Error handling + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 13.14 SendChargingInformationGPRS Procedure + +### 13.14.1 General description + +The gsmSCF uses this operation to instruct the gprsSSF on the Advice of Charge information to be sent to the MS, provided that the SGSN supports Advice of Charge. The operation may be invoked on multiple occasions. + +#### 13.14.1.1 Parameters + +- sCIGPRSBBillingChargingCharacteristics: +This parameter contains the Advice of Charge information: + - aOCGPRS: +This parameter specifies the Advice of Charge information that shall be sent to the MS. It may contain one or more of the following parameters: + - aOCInitial: +This is a set of Charge Advice Information elements, as defined in 3GPP TS 22.024 [2]. These CAI elements shall be sent by the gprsSSF to the MS when an Activate PDP Context Accept or Attach Accept is sent to MS and a tariff switch has not yet occurred. It may also be sent at any other time e.g. upon change of QoS or RAI. + - aOCSubsequent: +This parameter may contain the following information: + - cAIElements: +This is a set of Charge Advice Information (CAI) elements, as defined in 3GPP TS 22.024 [2]. These CAI elements shall be sent to the MS when an Activate PDP Context Accept or Attach Accept is + +detected and a tariff switch has occurred previously, or when Activate PDP Context Accept or Attach Accept has previously been detected and a tariff switch occurs. + +- **tariffSwitchInterval:** +This parameter indicates to the gprsSSF the time duration until the next tariff switch. The measurement of the elapsed tariff switch period shall start immediately after successful execution of this operation. +- **pDPID:** +This parameter identifies the PDP Context, within the GPRS Session dialogue, for which the Advice-of-Charge instruction applies. + +## 13.14.2 Responding Entity (gprsSSF) + +### 13.14.2.1 Normal Procedure + +gprsSSF preconditions: + +- (1) A relationship exists between the gsmSCF and the GPRS Session or PDP Context. +- (2) The gprsSSF FSM is in the state "Waiting\_for\_Instructions" or in the state "Monitoring". + +gprsSSF postconditions: + +- (1) No gprsSSF FSM state transition. + +On receipt of this operation, the gprsSSF performs actions to send the Advice of Charge information to the MS, provided that the SGSN supports Advice of Charge. + +If Advice of Charge is to be provided to an MS in conjunction with "CSE control of GPRS Session or PDP Context duration or volume", then the following sequence of operations shall be sent from the gsmSCF to the gprsSSF in the following order and in the same TC TC-CONTINUE or TC-BEGIN component: + +ApplyChargingGPRS; SendChargingInformationGPRS. + +These operations shall be processed sequentially by the gprsSSF, in the order that they are sent by the gsmSCF. In this, case parameter **TariffSwitchInterval** may be present either in the **ApplyChargingGPRS** operation or in the **SendChargingInformationGPRS** operation, but not in both operations. It is recommended that this parameter be transported in the **ApplyGPRSCharging** operation. + +The **TariffSwitchInterval** information received with either one of these operations shall set the same tariff switch timer in the gprsSSF. This duration timer shall run from the time of successful operation execution. + +### 13.14.2.2 Error handling + +"TaskRefused": In addition to the generic error handling noted below, this error shall be indicated when: + +- a **tariffSwitchInterval** is indicated when a previously received **tariffSwitchInterval** is pending. + +Generic error handling for the operation related errors is described in clause 10 and the TC services which are used for reporting operation errors are described in clause 14. + +## 14 Services assumed from lower layers + +### 14.1 Services assumed from TC + +The SS7 application layer protocol defined in this 3GPP TS, is a protocol to provide communication between a pair of application processes. In the SS7 environment this is represented as communication between a pair of application-entities (AEs) using the TC. The function of an AE is provided by a set of application-service-elements (ASEs). The interaction between AEs is described in terms of their use of the services provided by the ASEs. + +If AC are to be used for FE differentiation within a physical node, then the version of TC used must support the dialogue portion of TC (i.e. ETSI ETS 300 287-1 [22]). + +This requirement applies to all interfaces, not just those used for internetworking. + +Table 14-1 defines which versions of TC are the minimum versions required to support the defined CAP interfaces: + +**Table 14-1: Minimum TC requirements for CAP interfaces** + +| Interface | CAP | +|------------------------|------------| +| gsmSSF - gsmSCF | White Book | +| gsmSRF - gsmSCF | White Book | +| assist gsmSSF - gsmSCF | White Book | +| smsSSF - gsmSCF | White Book | +| gprsSSF - gsmSCF | White Book | + +## 14.1.1 Common procedures + +The present subclause defines the procedures and mapping which apply between CAP and TC to be used in the absence of specific procedures and mapping instructions for the specific CAP interfaces as defined in subsequent subclauses. + +### 14.1.1.1 Normal procedures + +The present subclause describes the procedures and TC primitives that shall be used for transmitting messages between AEs under normal operation. + +The CAP, as TC-user, uses only the structured dialogue facility provided by TC. The following situations can occur when a message is sent between two PE: + +- a dialogue shall be established: the TC-user issues a TC-BEGIN request primitive. +- a dialogue shall be maintained: the TC-user issues a TC-CONTINUE request primitive. +- a dialogue shall no longer be maintained: the TC-user issues a TC-END request primitive with either basic end or with pre-arranged end depending on the following conditions: + - Basic End + - In the case the dialogue is established, operations, leading to a termination of the relationship, can be transmitted by the FE with a TC-END request primitive (basic) in the case the FE is not interested in the reception of any ERROR or REJECT components for these sent operations. Once the FE dialogue resources have been released, any ERROR or REJECT components received for these operations will be discarded by TC as described in ETSI ETS 300 287-1 [22]. + - In the case that the dialogue is established and the FE has received an operation, leading to the termination of the relationship, does not wish to continue dialogue and there is no operation to be sent, a TC-END request primitive (basic) with zero components can be sent from the FE. + - Pre-arranged End + - Where an entity is interested in possible ERROR or REJECT messages on response to sent operations leading to a termination of the relationship, the dialogue is ended with a TC-END request primitive (pre-arranged end) after the last associated operation timer expires. The receiving entity can end the dialogue with a TC-END request primitive (pre-arranged end) after successful processing of these operations (i.e. the relationship is terminated). + - in general, the use of prearranged end shall be limited to the case for both communicating entities clearly recognizable that peer entity applies prearranged end. In all other cases, basic end shall be used. + +### 14.1.1.2 Abnormal procedures + +The present subclause describes the procedures and TC primitives that shall be used for reporting abnormal situations between AEs. The error cases are defined in clause 10. + +The following primitives shall be used to report abnormal situations: + +- operation errors, as defined in the CAP, are reported with TC-U-ERROR request primitive. + +- rejection of a TC component by the TC-user shall be reported with TC-U-REJECT request primitive. +- when the FE detecting error or rejecting operation decides the termination of TC dialogue, TC-END request primitive (basic) with error or reject can be used for the termination of TC dialogue. +- when the gsmSSF or the gsmSRF detecting error or rejecting operation recognizes the possibility to continue dialogue, TC-CONTINUE request primitive with error or reject can be used for the continuation of TC dialogue. +- a dialogue shall be aborted by the TC-user with a TC-U-ABORT request primitive. +- on expiration of application timer Tssf or Tsrf, dialogue shall be terminated by means of by TC-U-ABORT primitive with an Abort reason, regardless of TC dialogue is established or not. + +For abnormal situations detected by TC the same rules shall apply for reception of TC-R-REJECT indication as for transmission of TC-U-REJECT request and for transmission of TC-P-ABORT indication as for transmission of TC-U-ABORT request primitive. + +The following rules shall be applied to terminate the TC dialogue under abnormal situations: + +- in the case that abort condition is detected and TC dialogue is established, TC dialogue is terminated by TC-U-ABORT primitive with an Abort reason. +- in the case that abort condition is detected and TC dialogue is not established, TC dialogue is locally terminated by TC-U-ABORT primitive. (in the case such as application time out). + +In error situations prearranged end shall not be used to terminate the TC dialogue. In the case any AE encounters an error situation the peer entity shall be explicitly notified of the error, if possible. If from any entity's point of view the error encountered requires the relationship to be ended, then it shall close the dialogue via a TC-END request primitive with basic end or via a TC-U-ABORT request primitive, depending on whether any pending ERROR or REJECT component is to be sent or not. + +In the case an entity receives a TC-END indication primitive and after all components have been considered, the FSM is not in a state to terminate the relationship, an appropriate internal error should be provided. + +In cases when a dialogue needs to be closed by the initiating entity before its establishment has been completed (before the first TC indication primitive to the TC-BEGIN request primitive has been received from the responding entity), the TC-user shall issue a TC-END request primitive with prearranged end or a TC-U-ABORT request primitive. The result of these primitives will be only local, any subsequent TC indication received for this dialogue will be handled in accordance with the abnormal procedures as specified in ETSI ETS 300 287-1 [22]. + +When the gsmSSF, gprsSSF or smsSSF receives multiple Operation components in a single TC Message and there is an error in the processing of one of these Operations, then the gsmSSF FSM, gprsSSF FSM or smsSSF FSM shall process the error and shall discard all Operation components in that TC Message of which the processing has not yet started. + +### 14.1.1.3 Dialogue handling + +#### 14.1.1.3.1 Dialogue establishment + +The establishment of a CAP dialogue involves two application processes as described in clause 1, one that is the dialogue-initiator and one that is the dialogue-responder. + +This procedure is driven by the following signals: + +- A TC-BEGIN request primitive from the dialogue-initiator. +- A TC-BEGIN indication primitive occurring at the responding side +- The first TC-CONTINUE indication primitive occurring at the initiating side or under specific conditions: + - A TC-END indication primitive occurring at the initiating side + - A TC-U-ABORT indication primitive occurring at the initiating side + - A TC-P-ABORT indication primitive occurring at the initiating side + +*Sending of a TC-BEGIN request* + +Before issuing a TC-BEGIN request primitive, TC-USER shall store the AC-name and if present the user-information parameter. + +TC-USER shall request the invocation of the associated operations using the TC-INVOKE service. See subclause 14.1.1.4.1 for a description of the invocation procedure. + +After processing of the last invocation request, TC-USER shall issue a TC-BEGIN request primitive. + +The initiator TC-USER then waits for a TC indication primitive and will not issue any other requests, except a TC-U-ABORT request or a TC-END request with the release method parameter set to "pre-arranged release". + +*Receipt of a TC-BEGIN indication* + +On receipt of a TC-BEGIN indication primitive, responder TC-USER shall: + +- Analyse the application-context-name included in the primitive. If it is supported, then process any other indication primitives received from TC as described in subclause 14.1.1.4.1. +- If the application-context-name included in the primitive is not supported, then issue a TC-U-ABORT request primitive. + +*Receipt of the first TC-CONTINUE indication* + +On receipt of the first TC-CONTINUE indication primitive for a dialogue, TC-USER shall check the value of the application-context-name parameter. If this value matches the one used in the TC-BEGIN request primitive, then TC-USER shall process the following TC component handling indication primitives as described in subclause 14.1.1.4.1, otherwise it shall issue a TC-U-ABORT request primitive. + +*Receipt of a TC-END indication* + +On receipt of a TC-END indication primitive in the dialogue initiated state, TC-USER shall check the value of the application-context-name parameter. If this value match the one used in the TC-BEGIN request primitive, then the TC-USER shall process the following TC component handling indication primitives as described in subclause 14.1.1.4.1. + +*Receipt of a TC-U-ABORT indication* + +Receipt of a TC-U-ABORT indication primitive is described as part of user abort procedure (see 14.1.1.3.4.). + +*Receipt of a TC-P-ABORT indication* + +Receipt of a TC-P-ABORT indication primitive is described as part of provider abort procedure (see 14.1.1.3.5.). + +#### 14.1.1.3.2 Dialogue continuation + +Once established the dialogue is said to be in a continuation phase. + +Both application processes can request the transfer of CAP APDUs until one of them requests the termination of the dialogue. + +*Sending entity* + +TC-USER shall process any component handling request primitives as described in subclause 14.1.1.4.1. + +After processing the last component handling request primitive, TC-USER shall issue a TC-CONTINUE request primitive. + +*Receiving entity* + +On receipt of a TC-CONTINUE indication primitive TC-USER shall accept zero, one or several TC component handling indication primitives and process them as described in subclause 14.1.1.4.1. + +### 14.1.1.3.3 Dialogue termination + +Both the dialogue-initiator and the dialogue-responder have the ability to request the termination of a dialogue after it has been established when no dialogue is to be established or when a dialogue is no longer to be maintained according to the rules as stated in subclauses 14.1.2.1.1 and 14.1.2.1.2. + +The dialogue termination procedure is driven by the following events: + +- A TC-END request primitive +- A TC-END indication primitive + +#### *Sending of TC-END request* + +When the dialogue shall no longer be maintained, TC-USER shall process any component handling request primitives as described in subclause 14.1.1.4.1 + +After processing the last component handling request primitive (if any), TC-USER shall issue a TC-END request primitive with the release method parameter set to "basic end" or "prearranged release", in accordance with the rules as stated in subclauses 14.1.2.1.1 and 14.1.2.1.2. + +When no dialogue is to be established, refer to subclauses 14.1.1.3.1. + +#### *Receipt of a TC-END indication* + +On receipt of a TC-END indication primitive, the TC-USER shall accept any component handling indication primitives and process them as described in subclause 14.1.1.4.1. + +After processing the last component handling primitive all dialogue related resources are released. + +### 14.1.1.3.4 User abort + +Both the dialogue-initiator and the dialogue-responder have the ability to abort a dialogue at any time. + +The user abort procedure is driven by one of the following events: + +- A TC-U-ABORT request primitive +- A TC-U-ABORT indication primitive + +#### *Sending of TC-U-ABORT request* + +After issuing a TC-U-ABORT request primitive, all dialogue related resources are released. + +#### *Receipt of a TC-U-ABORT indication* + +On receipt of a TC-U-ABORT indication all dialogue related resources are released. + +### 14.1.1.3.5 Provider abort + +TC has the ability to abort a dialogue at both the dialogue-initiator side and the dialogue-responder side. + +The provider abort procedure is driven by the following event: + +- A TC-P-ABORT indication primitive + +#### *Receipt of a TC-P-ABORT indication* + +On receipt of a TC-P-ABORT indication, all dialogue related resources are released. + +#### 14.1.1.3.6 Mapping to TC dialogue primitives + +The TC-UNI service is not used by CAP. + +The mapping of parameters onto the TC Dialogue services is as follows: + +The use of parameters of the TC-BEGIN service is as defined in subclause 14.1.1.3.7 with the following qualifications: + +- The Destination Address parameter of the TC-BEGIN service shall be set to the CAP address of the AE which is to respond to the TC-BEGIN service. +NOTE 1: The address used in this parameter may be mapped by SCCP address translation to one of a number of alternative AEs. +- The AC Name parameter of the TC-BEGIN service shall be set according to the specific interface being used between the initiating AE and the responding AE. +- The Originating Address parameter of the TC-BEGIN service shall be set to the unambiguous CAP address of the AE initiating the TC-BEGIN service. + +The use of parameters of the TC-CONTINUE service is as defined in subclause 14.1.1.3.7 with the following qualifications: + +- The AC Name parameter of the TC-CONTINUE service shall be set to the value of the AC Name parameter of the TC-BEGIN service for the same TC Dialogue ID parameter value. +- If present, the Originating Address parameter of the TC-CONTINUE service shall be set to the unambiguous CAP address of the AE initiating the TC-CONTINUE service. This parameter is present only in the first TC-CONTINUE service after a TC-BEGIN service with the same TC Dialogue ID parameter value. + +The use of parameters of the TC-END service is as defined in subclause 14.1.1.3.7 with the following qualifications: + +- The AC Name parameter of the TC-END service shall be set to the value of the AC Name parameter of the TC-BEGIN service for the same TC Dialogue ID parameter value. This parameter is present only if the TC-END service is used immediately after the TC-BEGIN service. + +The use of parameters of the TC-U-ABORT service is as defined in subclause 14.1.1.3.7 with the following qualifications: + +- The Abort Reason parameter of the TC-U-ABORT service shall be used as specified in ETSI ETS 300 287-1 [22]. +- The AC Name parameter of the TC-U-ABORT service shall be set to the value used in the TC-BEGIN service. +NOTE 2: This parameter is present only if the TC-U-ABORT is the immediate response to a TC-BEGIN indication. + +The use of parameters of the TC-P-ABORT service is as defined in subclause 14.1.1.3.7 with the following qualifications: + +- The P-Abort parameter of the TC-P-ABORT service is set by TC to indicate the reason why TC aborted the dialogue. It shall take the values as defined in ETSI ETS 300 287-1 [22]. + +#### 14.1.1.3.7 Default mapping to TC dialogue parameters + +##### *Dialogue Id* + +The value of this parameter is associated with the CAP invocation in an implementation dependent manner. This parameter uniquely identifies a specific TC dialogue to a remote CAP AE for a CAP AE. + +*Application-context-name* + +The application-context-name parameter is set in accordance with the set of Operations which need to be supported by the TC dialogue. The defined AC Names can be found in clauses 6 to 8. + +*User information* + +This parameter may be used by both initiating and responding application processes. This parameter shall be used for the CAP-GPRS-ReferenceNumber as defined in 14.1.7. For interfaces other than the gprsSSF-gsmSCF interface and for SMS related messages (as in subclauses 14.1.3, 14.1.4 and 14.1.5) the receiving side may ignore this parameter if received. The User Information parameter shall be encoded in accordance with the definition provided in ITU-T Recommendation Q.773 [46], subclause 3.2, and the definition of EXTERNAL type provided in ITU-T Recommendation X.690 [57], with the restriction that: + +- a size (1..10) constraint of SEQUENCE OF EXTERNAL; +- an Object Identifier shall always be present to identify the user information and the entity which sent it; +- a single-ASN-1-type is used for encoding. + +For the use of CAP defined TC-U-Abort reason, see the ASN.1 notation in the subclause 5.7. + +For the use of CAP defined CAP-GPRS-ReferenceNumber, see subclause 14.1.7. For the abstract syntax of CAP defined CAP-GPRS-ReferenceNumber, see the ASN.1 notation in the subclause 8.1. + +*Component present* + +This parameter is used by TC-USER as described in ETSI ETS 300 287-1 [22]. + +*Termination* + +The value of the release method parameter of the TC-END request primitive is set by TC-USER according to the rules as stated in subclauses 14.1.2.1.1 and 14.1.2.1.2. + +*Quality of service* + +The quality of service of TC request primitives is set by the TC-USER to the following value: + +- Sequencing requested; +- return option, this parameter is set by TC-USER in an implementation dependent manner. + +#### 14.1.1.4 Component handling + +##### 14.1.1.4.1 Procedures for CAP Operations + +The present subclause describes the procedures for CAP Operations. + +*Operation invocation* + +TC-USER shall build an operation argument from the parameters received and request the invocation of the associated operation using the TC-INVOKE procedure. If a linked ID parameter is inserted in the primitive, then this indicates a child operation and implies that the operation is linked to a parent operation. + +*Operation invocation receipt* + +On receipt of a TC-INVOKE indication primitive, TC-USER shall: + +- If the operation code does not correspond to an operation supported by the application-context, then request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (unrecognized operation); +- If a linked ID is included, then perform the following checks: If the operation referred to by the linked ID does not allow linked operations or if the operation code does not correspond to a permitted linked operation, or if the parent operation invocation is not active, then request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (linked response unexpected or unexpected linked operation); + +- If a linked ID is not included, but a Linked ID is needed to correlate the indication primitive with a parent operation invocation, then request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter); +- If the type of the argument is not the one defined for the operation, then request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter); +- If the operation cannot be invoked because the CAP related dialogue is about to be released, then request the transfer of a reject component using the TC-U-REJECT request primitive with the problem code (Initiating Release); +- If sufficient CAP related resources are not available to perform the requested operation, then request the transfer of a reject component using the TC-U-REJECT request primitive with the problem code (Resource Limitation); +- Otherwise, accept the TC-INVOKED indication primitive. If the operation is to be user confirmed, then TC-USER waits for the corresponding response. + +#### *Operation Response* + +For user confirmed operations, TC-USER shall: + +- If no error indication is included in the response to a class 1 or 3 operation, then construct a result information element from the parameters received and request its transfer using the TC-RESULT-L service. +- If an error indication is included in the response to a class 1 or 2 operation, then construct an error parameter from the parameters received and request its transfer using the TC-U-ERROR request primitive. + +#### *Receipt of a response* + +On receipt of a TC-RESULT-NL indication, TC-USER shall: + +- Request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter). + +On receipt of a TC-RESULT-L indication, TC-USER shall: + +- If the type of the result parameter is not the one defined for the result of this operation, request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter); +- Otherwise, accept the TC-RESULT-L indication primitive. + +On receipt of a TC-U-ERROR indication, TC-USER shall: + +- If the error code is not defined for the TC-USER or is not one associated with the operation referred to by the invoke ID, request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (unrecognized error or unexpected error); +- If the type of the error parameter is not the one defined for this error, request the transfer of a reject component using the TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter); +- Otherwise, accept the TC-U-ERROR indication primitive. + +On receipt of a TC-U-REJECT indication primitive which affects a pending operation, TC-USER shall: + +- accept the TC-U-REJECT indication primitive. + +On receipt of a TC-L-REJECT indicating "return result problem, return error unexpected", TC-USER shall inform the application process. + +On receipt of a TC-L-REJECT indicating "return error problem, return error unexpected", TC-USER shall inform the application process. + +This event occurs when the local TC detects a protocol error in an incoming component which affects an operation. + +When the problem code indicates a general problem, it is considered that the event cannot be related to an active operation even if the invoke Id is provided by TC. This is because it is unclear whether the invoke Id refers to a local or remote invocation. The behaviour of TC-USER in such a case is described in the subclause headed "other events". + +On receipt of a TC-L-CANCEL indication, the TC-USER shall: + +- If the associated operation is a class 1 operation, inform the application process; +- If the associated operation is a class 2 operation and no linked operations are defined for this operation, ignore the primitive; +- If the associated operation is a class 2 operation and has linked operations but none of them has been invoked, inform the application process; +- If the associated operation is a class 2 operation and a linked operation invocation has already been received in response to this operation, ignore the primitive; +- If the associated operation is a class 3 operation, inform the application process; +- If the associated operation is a class 4 operation, ignore the primitive; + +#### *Other events* + +This subclause describes the behaviour of TC-USER on receipt of a component handling indication primitive which cannot be related to any operation or which does not affect a pending one. + +On receipt of a TC-U-REJECT indication primitive which does not affect an active operation (i.e. indicating a return result or return error problem), it is up to the application process to abort, continue or terminate the dialogue, if not already terminated by the sending application process according to the rules as stated in subclause 14.1.2.1.2. This is also applicable for invoke problems related to a class 4 linked operation. + +On receipt of a TC-R-REJECT indication (i.e. when a protocol error has been detected by the peer TC entity) which does not affect an active operation, it is up to the application process to abort, continue or terminate the dialogue, if not already terminated by the sending application process according to the rules as stated in subclause 14.1.2.1.2. + +On receipt of a TC-L-REJECT indication primitive (i.e. when a protocol error has been detected by the local TC entity) which cannot be related to an active operation, it is up to the application process to continue, or to terminate the dialogue and implicitly trigger the transmission of the reject component or to abort the dialogue. + +On receipt of a TC-NOTICE indication primitive, which informs the TC-USER that a message cannot be delivered by the Network Layer, it is for the application process to decide whether to terminate the dialogue or retry. + +This primitive can occur only if the Return Option has been set (see subclause 14.1.1.3.6). + +#### 14.1.1.4.2 Mapping to TC component primitives + +The mapping of parameters onto the TC Component services is as follows: + +The TC-U-CANCEL service is not used. + +The TC-RESULT-NL service is not used. + +The use of parameters of the TC-INVOKE service is as defined in subclause 14.1.1.4.3 with the following qualifications: + +- The Operation parameter of the TC-INVOKE service shall contain the *operation.&operationCode* value of the CAP Operation to be invoked. The operation must be one of the valid operations supported by the AC for the TC dialogue and must be invokable by the local AE. +- The Parameters parameter of the TC-INVOKE service shall contain a value of the *operation.&ArgumentType* value for the operation being invoked, as specified by the Operation parameter. + +The use of parameters of the TC-RESULT-L service is as defined in subclause 14.1.1.4.3 with the following qualifications: + +- The Invoke Id parameter of the TC-RESULT-L service shall be set to the value of the Invoke Id parameter of the TC-INVOKE service from the remote AE to which a result is being sent. +- The Operation parameter of the TC-RESULT-L service be set to the value of the Operation parameter of the TC-INVOKE service from the remote AE which contains the same Invoke Id Parameter value. +- The Parameters parameter of the TC-RESULT-L service shall contain the *operation.&ResultType* value for the operation result, as specified by the Operation parameter. + +The use of parameters of the TC-U-ERROR service is as defined in subclause 14.1.1.4.3 with the following qualifications: + +- The Invoke Id parameter of the TC-U-ERROR service shall be set to the value of the Invoke Id parameter of the TC-INVOKE service from the remote AE to which an error is being sent. +- The Error parameter of the TC-U-ERROR service shall be set to the value of the *error.&errorCode* of the error to be sent. It must be one of the errors which is expected for the invoked operation as defined in the *operation.&Errors* specification. +- The Parameters parameter of the TC-U-ERROR service shall be set to the value of the *error.&ParameterType* of the error to be sent, as identified by the Error parameter. + +The use of parameters of the TC-U-REJECT service is as defined in subclause 14.1.1.4.3 with the following qualifications: + +- The Invoke Id parameter of the TC-U-REJECT service shall be set to the Invoke Id Parameter of the TC component service from the remote AE which is being rejected. + +The use of parameters of the TC-L-CANCEL service is as defined in subclause 14.1.1.4.3. + +#### 14.1.1.4.3 Default mapping to TC component parameters + +##### *Invoke Id* + +This parameter is set by the sending application process. It represents the unique identity of an instance of an operation which is invoked by an AE within a specific TC dialogue. The TC dialogue is identified by the Dialogue Id parameter. + +##### *Linked Id* + +This parameter is set by the sending application process. It represents the Invoke Id of an operation which was received from the remote AE for a specific TC dialogue to which the operation being invoked by the local AE is to be linked. This parameter is present only if the original operation invoked by the remote AE is defined as having linked operations. The type of local operation invoked must be the same type as one of the operations defined as being linked. + +##### *Dialogue Id* + +The value of this parameter is associated with the CAP invocation in an implementation dependent manner. It represents the identity of the established TC dialogue which will carry the component services between the local AE and the remote AE. + +##### *Class* + +The value of this parameter is set according to the type of the operation to be invoked according to the operation definitions in clauses 6 through 8. + +##### *Time out* + +The value of this parameter is set according to the type of operation invoked. + +##### *Last component* + +This parameter is used as described in ETSI ETS 300 287-1 [22]. + +##### *Problem code* + +This parameter is used as described in subclause 14.1.1.4.1. + +*Abort reason* + +This parameter is used by TC-USER, and attributes and coding are specified by network operator. + +## 14.1.2 gsmSSF-gsmSCF interfaces + +### 14.1.2.1 Normal procedures + +#### 14.1.2.1.1 gsmSSF-to-gsmSCF messages + +The present subclause defines the normal procedures for TC messages from the gsmSSF to the gsmSCF. + +*gsmSSF FSM related messages* + +A dialogue shall be established when the gsmSSF FSM transits from the state "Idle" to the state "Waiting\_for\_Instructions". + +The CAP Operation InitialDP shall be sent with a TC-BEGIN request primitive. + +When the dialogue was opened with InitialDP or InitiateCallAttempt operation then the gsmSSF shall maintain the dialogue when sending the SpecializedResourceReport operation indicating the announcement complete for PlayAnnouncement regardless of the fact whether the disconnectFromIPForbidden parameter was set to true or false. + +For all other operations sent from the gsmSSF FSM, the dialogue shall be maintained except for the following cases. + +When the gsmSSF FSM executes a non-error case state transition to the state "Idle" and there is one or more pending operation and TC dialogue is established, TC dialogue can be terminated by TC-END primitive with component(s). When the gsmSSF sends the last EventReportBCSM, ApplyChargingReport or CallInformationReport the dialogue may be ended from the gsmSSF by a TC-END request primitive with basic end. + +In the case that there is no pending operation and TC dialogue is established, TC dialogue can be terminated by TC-END primitive with zero component or prearranged end. When the gsmSSF FSM makes a non-error case state transition to the state "Idle" and there is no operation to be sent, the dialogue is ended by means of a TC-END request primitive (basic) with zero components, or the dialogue is locally ended by means of a TC-END request primitive with prearranged end. + +In the case where a call release is initiated by any other entity than a gsmSCF, the gsmSSF can end a dialogue with a TC-END request primitive with zero component or prearranged end if a TC dialogue is established and the gsmSSF has no pending call information requests (or pending requests which should be treated in the same way, see subclause 14.1.1.1) nor any armed EDP. + +When the gsmSSF has sent the last EventReportBCSM, ApplyChargingReport or CallInformationReport the dialogue may be ended from the gsmSCF by a TC-END request primitive with basic end. + +*Assisting gsmSSF FSM related messages* + +A dialogue shall be established when the assisting gsmSSF FSM transits from the state "Idle" to the state "Waiting\_for\_Instructions". The AssistRequestInstructions operation shall be transmitted with a TC-BEGIN request primitive. + +For all other operations sent from the assisting gsmSSF FSM, the dialogue shall be maintained except for the following cases. + +When the assisting gsmSSF FSM makes a non-error case state transition to the state "Idle" and there is one or more pending operation and TC dialogue is established, TC dialogue can be terminated by TC-END primitive with component(s). + +In the assisting gsmSSF case the same rules apply as for the gsmSCF as specified for the SpecializedResourceReport operation in subclause 14.1.3.1.1. + +In the case that there is no pending operation and TC dialogue is established, TC dialogue can be terminated by TC-END primitive with zero component or prearranged end. When the assisting gsmSSF FSM makes a non-error case state transition to the state "Idle" and there is no operation to be sent, the dialogue is ended by means of a TC-END request primitive (basic) with zero components, or the dialogue is locally ended by means of a TC-END request primitive with prearranged end. + +*gsmSSME FSM related messages* + +The following procedures shall be followed: + +- The dialogue shall be maintained when the ActivityTest Return Result is sent. + +#### 14.1.2.1.2 gsmSCF-to-gsmSSF messages + +The present subclause defines the normal procedures for TC messages from the gsmSCF to the gsmSSF. + +*SCSM-FSM related messages* + +A dialogue shall be established when the SCSM-FSM receives an InitialDP operation for TDP-R or an AssistRequestInstructions operation, or sends an InitiateCallAttempt operation. + +For subsequent operations sent from the SCSM-FSM, the dialogue shall be maintained except for the following cases; + +The dialogue shall no longer be maintained when the prearranged end condition is met in the gsmSCF. When the gsmSCF does not expect any messages other than possibly REJECT or ERROR messages for the operations sent and when the last associated operation timer expires, the dialogue is locally ended by means of a TC-END request primitive with prearranged end. + +Alternatively, the sending of operations, leading to the termination of the relationship, by means of a TC-END request primitive (basic end) is possible. + +*SCME-FSM related messages* + +The operations sent from the SCME-FSM shall be issued according to the following procedures: + +- The dialogue shall be maintained when the ActivityTest operation is sent. +- For sending one or more CallGap operations, the SCME FSM shall use an existing SCSM FSM associated dialogue which was initiated by a gsmSSF FSM (i.e. established for the transmission of the InitialDP operation). The dialogue shall be maintained. + +#### 14.1.2.1.3 smsSSF -to-gsmSCF SMS related messages + +A dialogue shall be established when the smsSSF has finalised trigger processing and transits to the state "Waiting\_for\_Instructions". The relevant CAP Operation, which can be the InitialDPSMS operation only, shall be transmitted in the same message. + +For all other operations sent from the smsSSF, the dialogue shall be maintained. + +The dialogue shall no longer be maintained when the prearranged end condition is met in the smsSSF. When the smsSSF makes a state transition to the state "Idle", the dialogue is locally ended by means of a TC-END request primitive with prearranged end. + +When the smsSSF FSM transits to the state "Idle", but no event was reported to the gsmSCF, then the smsSSF shall send TC-END with zero components to the gsmSCF. + +When the smsSSF has sent the last EventReportSMS operation the dialogue may be ended from the gsmSCF by a TC-END request primitive with basic end. If the smsSSF decides to apply basic end, then it shall send TC-END with zero components. + +#### 14.1.2.1.4 gsmSCF-to-smsSSF SMS related messages + +All operations are sent after a dialogue was established from the smsSSF (the gsmSCF has previously received a TC-BEGIN indication primitive with an InitialSMSEvent operation). + +The dialogue shall no longer be maintained when the prearranged end condition is met in the gsmSCF. When the gsmSCF does not expect any messages other than possibly REJECT or ERROR messages for the operations sent and when the last associated operation timer expires, the dialogue is locally ended by means of a TC-END request primitive with prearranged end. + +Alternatively, the sending of operations, leading to the termination of the control relationship, by means of a TC-END request primitive (basic end) is possible. + +#### 14.1.2.1.5 Use of dialogue handling services + +Dialogue handling services are used to trigger the sending of the APDUs associated with the operations involved in the CAP packages. + +Component grouping is performed under the control of the application-process through an appropriate usage of the TC-BEGIN, TC-CONTINUE and TC-END service. + +#### 14.1.2.2 Abnormal procedures + +The following procedures also apply to the gsmSCF-gsmSRF interfaces. + +##### 14.1.2.2.1 gsmSCF-to-gsmSSF/gsmSRF messages + +Considering that gsmSSF and gsmSRF do not have the logic to recover from error cases detected on the gsmSCF-gsmSSF/gsmSRF interface, the following shall apply: + +- Operation errors and rejection of TC components shall be transmitted to the gsmSSF and, respectively, the gsmSRF with a TC-END request primitive, basic end. + +If, in violation of the above procedure, an ERROR or REJECT component is received with a TC-CONTINUE indication primitive, then the gsmSSF and, respectively, the gsmSRF shall abort the dialogue with a TC-U-ABORT request primitive. + +##### 14.1.2.2.2 gsmSSF/gsmSRF/ -to-gsmSCF messages + +Operation errors and rejection of TC components shall be transmitted to the gsmSCF according to the following rules: + +- The dialogue shall be maintained when the preceding message, which contained the erroneous component, indicated that the dialogue shall be maintained. I.e. the error or reject shall be transmitted with a TC-CONTINUE request primitive if the erroneous component was received with a TC-CONTINUE indication primitive. +On receipt of an ERROR or REJECT component the gsmSCF decides on further processing. It may either continue, explicitly end or abort the dialogue. +- When the gsmSSF has received and processed InitiateCallAttempt and has acknowledged InitiateCallAttempt with InitiateCallAttempt-RESULT, then a User Error resulting from an erroneous component that is contained in the same TC\_Begin message as InitiateCallAttempt, shall be transmitted with a TC-CONTINUE indication primitive. +- In all other situations the dialogue shall no longer be maintained. I.e. the error or reject shall be transmitted with a TC-END request primitive, basic end, if the erroneous component was received with a TC-BEGIN indication primitive. +- on expiration of application timer Tssf or Tsrf, dialogue shall be terminated by means of by TC-U-ABORT primitive with an Abort reason, regardless of TC dialogue is established or not. + +If the error processing in the gsmSSF or gsmSRF leads to the case where the gsmSSF or gsmSRF is not able to process further gsmSCF operations while the dialogue is to be maintained, then the gsmSSF or gsmSRF aborts the dialogue with a TC-END request primitive with basic end or a TC-U-ABORT request primitive, depending on whether any pending ERROR or REJECT component is to be sent or not. + +The gsmSSF can end a dialogue with a TC-U-ABORT request primitive in the case that call release is initiated by any other entity then the gsmSCF and the gsmSSF has no pending call information requests (or pending requests which should be treated in the same way, i.e., ApplyCharging nor any armed EDP to notify the gsmSCF of the call release (for alternative way, see subclause 14.1.2.1.1). + +##### 14.1.2.2.3 gsmSCF-to-smsSSF SMS related messages + +Considering that the smsSSF does not have the logic to recover from error cases detected on the gsmSCF-smsSSF interface, the following shall apply: + +- operation errors and rejection of TC components shall be transmitted to the smsSSF with a TC-END request primitive, basic end. + +If, in violation of the above procedure, an ERROR or REJECT component is received with a TC-CONTINUE indication primitive, then the smsSSF shall abort the dialogue with a TC-U-ABORT request primitive. + +#### 14.1.2.2.4 smsSSF-to-gsmSCF SMS related messages + +Operation errors and rejection of TC components shall be transmitted to the gsmSCF according to the following rules: + +- the dialogue shall be maintained when the preceding message, which contained the erroneous component, indicated that the dialogue shall be maintained. I.e. the error or reject shall be transmitted with a TC-CONTINUE request primitive if the erroneous component was received with a TC-CONTINUE indication primitive; +- on receipt of an ERROR or REJECT component the gsmSCF decides on further processing. It may either continue, explicitly end or abort the dialogue; + +If the error processing in the smsSSF leads to the case where the smsSSF is not able to process further gsmSCF operations while the dialogue is to be maintained, then the smsSSF aborts the dialogue with a TC-U-ABORT request primitive. + +The smsSSF aborts a dialogue with a TC-U-ABORT request primitive if release is initiated by any other entity than the gsmSCF and the smsSSF has no armed EDPs to notify the gsmSCF. + +#### 14.1.2.2.5 Use of dialogue handling services + +On receipt of a TC-U-REJECT.ind in the FE, this primitive should be ignored. It is up to the application process to abort, continue or terminate the dialogue, if not already terminated by the sending application process according to the rules as stated in subclause 14.1.1.2. This is also applicable for invoke problems related to a class 4 linked operation. + +A TC-U-REJECT.req should be sent followed by a TC-CONTINUE.req. + +On receipt of a TC-R-REJECT.ind in the FE, this primitive should be ignored. It is up to the application process to abort, continue or terminate the dialogue, if not already terminated by the sending application process according to the rules as stated in subclause 14.1.1.2. This is also applicable for invoke problems related to a class 4 linked operation. + +On receipt of a TC-L-REJECT indication primitive (i.e. when a protocol error has been detected by the local TC entity) which cannot be related to an active operation, it is up to the application process to continue or to terminate the dialogue and implicitly trigger the transmission of the reject component or to abort the dialogue. + +On receipt of a TC-NOTICE indication the TC-USER is informed that a message cannot be delivered by the Network Layer. It occurs if the Return Option has been set (see subclause 14.1.1.3.7). It is for the application process to decide whether to terminate the dialogue or retry. + +The application-process is the sole user of the TC-P-ABORT service and TC-NOTICE service. + +The receipt of a TC-U-ABORT-Ind or TC-P-ABORT-Ind on a dialogue terminates all request processing. + +#### 14.1.2.3 Dialogue handling + +##### 14.1.2.3.1 Dialogue establishment + +##### 14.1.2.3.2 Dialogue continuation + +##### 14.1.2.3.3 Dialogue termination + +##### 14.1.2.3.4 User abort + +##### 14.1.2.3.5 Provider abort + +##### 14.1.2.3.6 Mapping to TC dialogue primitives + +The gsmSSF-gsmSCF IN services can be mapped onto TC services. The present subclause defines the mapping of the gsmSSF-gsmSCF IN services onto the services of the TC dialogue handling services defined in ETSI ETS 300 287-1 [22]. + +- a) The TC-BEGIN service is used to invoke the operations of the gsmSCF-gsmSSF connection packages as defined in clause 6. +- b) The TC-CONTINUE service is used to report the success of the operations invoked in a TC-BEGIN service and to invoke or respond to any other operations. +- c) The TC-U-ABORT service is used to report the failure of operations of the connection packages as defined in clause 6. + +The mapping of the parameters onto the TC-BEGIN primitive is defined in subclause 14.1.1.3.6 with the following qualifications: + +- The AC Name parameter shall take the value of the application-context-name field of the cap3-sms-AC object if the initiating AE is a gsmSSF. + +The mapping of the parameters onto the TC-CONTINUE primitive is defined in subclause 14.1.1.3.6. + +The mapping of the parameters onto the TC-U-ABORT primitive is defined in subclause 14.1.1.3.6 with the following qualifications: + +- The Application-Context-Name parameter shall be used as specified in ETSI ETS 300 287-1 [22]. When the responding AE refuses a dialogue because the application-context-name it receives is not supported, this parameter shall have the value of the application-context-name field of the cap3-sms-AC object if the responding AE is a gsmSCF. + +The use of the parameters of the TC-END service is defined in subclause 14.1.1.3.6. + +## 14.1.2.4 Component Handling + +### 14.1.2.4.1 Procedures for CAP Operations + +The CAP ASEs are users of the TC component handling services except for the TC-L-REJECT and TC-L-CANCEL services which are used by the application-process. Receipt of a TC-L-REJECT-Ind leads the application-process to abandon the dialogue (i.e. it issues a TC-U-ABORT-Request primitive). + +The TC-U-CANCEL service is never used. + +### 14.1.2.4.2 Mapping to TC component parameters + +The gsmSSF-gsmSCF IN ASE services are mapped onto the TC component handling services. The mapping of operations and errors onto TC services is defined in subclause 14.1.1.4.2 with the following qualifications: + +The timeout parameter of the TC-INVOKEReq primitives is set according to clause 6. + +## 14.1.3 gsmSCF-gsmSRF interface + +### 14.1.3.1 Normal procedures + +#### 14.1.3.1.1 gsmSCF-to/from-gsmSRF messages + +A dialogue is established when the gsmSRF sends an AssistRequestInstructions operation to the gsmSCF. For all other operations sent to/from the gsmSRF, the dialogue shall be maintained. + +In the case that there is no pending operation and TC dialogue is established, TC dialogue can be terminated by TC-END primitive with zero component. When the SCSM makes a non-error case state transition to end-user interaction and there is no operation to be sent, the dialogue is ended by means of a TC-END request primitive (basic) with zero components. + +When the dialogue is opened with the AssistRequestInstructions operation then the gsmSRF shall no longer maintain the dialogue when sending the SpecializedResourceReport operation indicating announcement complete for PlayAnnouncement with disconnectFromIPForbidden parameter was set to false or Return Result of the PromptAndCollectUserInfo with disconnectFromIPForbidden parameter was set to false. The dialogue is ended by means of a TC-END request primitive with basic end, and the SpecializedResourceReport operation is transmitted with the same request. + +Regardless of whether pending operation exists or not, when the SRSM-FSM is informed of the disconnection of bearer connection (in the case of gsmSCF initiated disconnection or call abandon from call party) and dialogue is established, the dialogue is ended by means of a TC-END request primitive (basic) with zero components or TC-END request primitive (prearranged end). + +The dialogue shall no longer be maintained when the prearranged end condition is met in the gsmSRF. When the SRSM-FSM is informed the disconnection of bearer connection and TC dialogue is not established, TC dialogue is locally terminated by TC-END primitive with prearranged end. + +When the gsmSCF does not expect any messages other than possibly REJECT or ERROR messages for the operations sent and when the last associated operation timer expires, the dialogue is locally ended by means of a TC-END request primitive with prearranged end. Alternatively, the sending of operations, leading to the termination of the relationship, by means of a TC-END request primitive (basic end) is possible. + +In the relay case, the gsmSRF-gsmSCF relationship uses the gsmSSF-gsmSCF TC dialogue. This is possible, because begin and end of the gsmSRF-gsmSCF relationship are embedded in the gsmSSF-gsmSCF relationship. gsmSRF-gsmSCF information shall be exchanged with TC-CONTINUE request primitives. + +#### 14.1.3.1.2 Abnormal procedures + +##### 14.1.3.1.3 Dialogue handling + +###### 14.1.3.1.3.1 Dialogue establishment + +###### 14.1.3.1.3.2 Dialogue continuation + +###### 14.1.3.1.3.3 Dialogue termination + +###### 14.1.3.1.3.4 User abort + +###### 14.1.3.1.3.5 Provider abort + +###### 14.1.3.1.3.6 Mapping to TC dialogue primitives + +The gsmSCF-gsmSRF IN services can be mapped onto TC services. The present subclause defines the mapping of the gsmSCF-gsmSRF IN services onto the services of the TC dialogue handling services defined in ETSI ETS 300 287-1 [22]. + +- a) The TC-BEGIN service is used to invoke the operations of the gsmSRF-gsmSCF connection packages as defined in clause 6. +- b) The TC-CONTINUE service is used to report the success of the operations invoked in a TC-BEGIN service and to invoke or respond to any other operations. +- c) The TC-U-ABORT service is used to report the failure of operation of the gsmSCF-gsmSRF operations packages as defined in clause 6. + +The mapping of parameters onto the TC Dialogue services is as defined in subclause 14.1.1.3.6 with the following qualifications: + +The mapping of the parameters onto the TC-BEGIN primitive is defined in subclause 14.1.1.3.6 with the following qualifications: + +- The AC Name parameter shall take the value of the application-context-name field of the gsmSRF-gsmSCF-ac object. + +#### 14.1.3.2 Component handling + +##### 14.1.3.2.1 Procedures for CAP Operations + +##### 14.1.3.2.2 Mapping to TC component parameters + +The mapping of parameters for the TC component services is defined in subclause 14.1.1.4.2 with the following qualifications. + +The Timeout Parameter of the TC-INVOKE service is set according to clauses 6. + +## 14.1.4 gprsSSF-gsmSCF interface + +### 14.1.4.1 Normal procedures + +#### 14.1.4.1.1 TC-dialogues and relationships + +The GPRS dialogue can consist of multiple consecutive TC-dialogues. A GPRS dialogue is identified by a GPRS-ReferenceNumber consisting of the originationReference and the destinationReference. One GPRS-Reference is assigned by the SGSN and shall be unique within this SGSN. The other GPRS-Reference is assigned by the gsmSCF and shall be unique within this gsmSCF. + +The *TC*-dialogues are closed and (re)opened whenever necessary. + +#### 14.1.4.1.2 Use of the GPRS Reference + +For the use of CAP defined GPRS-ReferenceNumber, see also the ASN.1 notation in the subclause 8.1. + +When the gprsSSF sends the first operation for a new GPRS dialogue (InitialDPGPRS), the gprsSSF shall include a GPRS Reference Number in the TC message. This GPRS Reference Number shall consist of the *SGSN Process Id* as originationReference, which is internally allocated by the gprsSSF. This number is used by the gprsSSF to associate an incoming TC message with an internal GPRS Process. + +When the gsmSCF has received the InitialDPGPRS operation, it shall store the SGSN Process ID and allocate an *SCF Process Id* which is used by the gsmSCF to associate an incoming TC message with an internal gsmSCF Process. + +The gsmSCF shall include the GPRS Reference Number in the first TC-CONTINUE message, *SGSN Process Id* in destinationReference and *SCF Process Id* in originationReference, returned to the gprsSSF. + +When the gprsSSF receives the first TC message from the gsmSCF for this GPRS dialogue, the gprsSSF shall store the gsmSCF Process Id together with the SGSN Process Id. + +From here onwards all the TC messages that open a new TC dialogue shall include the GPRS Reference Number consisting of the originationReference and the destinationReference to associate the internal process in the origination entity and the destination entity, respectively, until the end of the relationship between these processes. + +For any TC-CONTINUE in the existing TC dialogue, transporting the GPRS Reference Number is not needed except for the first response after the InitialDPGPRS operation. + +#### 14.1.4.1.3 gprsSSF-to-gsmSCF messages + +The present subclause defines the normal procedures for TC messages from the gprsSSF to the gsmSCF. + +##### *gprsSSF FSM related messages* + +A GPRS dialogue and a TC dialogue shall be established when the gprsSSF FSM transits from the state "Idle" to the state "Waiting\_for\_Instructions". The InitialDPGPRS operation shall be transmitted in the same TC message, i.e. TC-BEGIN. It shall contain the GPRS-Reference as assigned by the SGSN in the originationReference. The gprsSSF may initiate the subsequent TC dialogues for this GPRS dialogue with the following operations: + +- ApplyChargingReportGPRS +- EntityReleasedGPRS +- EventReportGPRS + +For the establishment of a new TC dialogue within the context of the current GPRS dialogue, the gprsSSF may apply one of the following mechanisms: + +- (1) the gprsSSF shall memorise the gsmSCF address used in the first response message to the InitialDPGPRS and use it to open the new TC dialogue; +- (2) the gprsSSF shall use the gsmSCF address from GPRS-CSI to open the new TC dialogue. + +The gsmSCF shall memorise the gprsSSF address received along with the InitialDPGPRS and use it for the opening of new TC dialogues within the context of the current GPRS dialogue. + +The gsmSCF may open subsequent TC dialogues with the following CAP Operations: + +- ActivityTestGPRS; +- ApplyChargingGPRS; +- CancelGPRS; +- FurnishChargingInformationGPRS; +- ReleaseGPRS; +- RequestReportGPRSEvent; +- SendChargingInformationGPRS. + +The CAP Operation that opens a TC dialogue shall be sent with a TC-BEGIN request primitive. This message shall contain the GPRS-ReferenceNumber assigned by the sender of this message in the originationReference. If the operation opens a subsequent TC dialogue, then this message shall contain also the previously received destinationReference. If an operation opens a GPRS dialogue, then the TC message reply shall contain the originationReference as assigned by the sender, i.e. the gsmSCF. + +The TC dialogue shall be closed for the idle periods, i.e. when the gprsSSF FSM transits from the state "Waiting\_for\_Instructions" to the state "Idle", if the gprsSSF FSM is in the state "Monitoring" and has received all replies or time-outs for the operations sent, after standalone operations of the gsmSCF in Monitoring state if gprsSSF FSM does not transit to the state "Idle" (ActivityTestGPRS, ApplyChargingGPRS, CancelGPRS, FurnishChargingInformationGPRS, RequestReportGPRSEvent, SendChargingInformationGPRS), or at the end of a GPRS dialogue. + +Each TC dialogue shall be terminated by the gprsSSF using TC-END (basic end). The following operations can cause the end of the GPRS dialogue: + +- ContinueGPRS; +- ConnectGPRS; +- ApplyChargingReportGPRS result; +- EntityReleasedGPRS result; +- EventReportGPRS (EDP-N) result; +- CancelGPRS; +- ReleaseGPRS; +- RequestReportGPRSEvent (disarming of DPs). + +When the gprsSSF FSM makes a non-error case state transition to the state "Idle" and there is one or more pending operation and TC dialogue is established, TC dialogue may be terminated by TC-END primitive with zero component(s) after all pending operations have been sent. When the gprsSSF sends the last EventReportGPRS, EntityreleasedGPRS or ApplyChargingReportGPRS, then after reception of the result or error, the GPRS dialogue may be ended from the gprsSSF by a TC-END request primitive with basic end. + +In the case that there is no pending operation, result nor error, and TC dialogue is established, TC dialogue shall be terminated by a TC-END primitive with zero component. + +In the case where a PDP Context release or detach is initiated by any other entity than a gsmSCF, the gprsSSF shall end a GPRS dialogue with the EntityReleasedGPRS operation if the gprsSSF has no armed DP to report nor pending ApplyChargingReportGPRS which should reported. + +In the case of overlapping dialogues for the same GPRS dialogue the gsmSCF opened TC dialogue is aborted by the gprsSSF with the abort reason overlapping-dialogue as specified in subclause 5.7. This abort reason is used to indicate to the gsmSCF that a specific instance already has a TC dialogue open. It is typically obtained when both the gsmSCF and gprsSSF open a new dialogue at the same time. While the gprsSSF waits for a response to an operation sent in TC-BEGIN it may receive an operation from the gsmSCF in TC-BEGIN. In such cases the dialogue opened by the gprsSSF is maintained and the dialogue opened by the gsmSCF is aborted with this abort reason. + +#### *gprsSSME FSM related messages* + +The following procedures shall be followed: + +- The TC dialogue shall be terminated by a TC-END primitive with zero components after the ActivityTestGPRS Return Result is sent. + +#### 14.1.4.1.4 gsmSCF-to-gprsSSF messages + +The present subclause defines the normal procedures for TC messages from the gsmSCF to the gprsSSF. + +In the case of overlapping dialogues for the same relationship the gsmSCF opened dialogue is closed by the gprsSSF as specified in subclause 5.7. The gsmSCF shall first respond normally to the operations sent by the gprsSSF, and then decide on the further actions. + +#### *SCME-FSM related messages* + +The operations sent from the SCME-FSM shall be issued according to the following procedures: + +- A new subsequent TC dialogue is established when the ActivityTestGPRS operation is sent. + +#### 14.1.4.2 Abnormal procedures + +##### 14.1.4.2.1 gsmSCF-to-gprsSSF messages + +The present subclause defines the abnormal procedures for TC messages from the gsmSCF to the gprsSSF. + +Considering that the gprsSSF does not have the logic to recover from error cases detected on the gsmSCF-gprsSSF interface, the following shall apply: + +- Operation errors and rejection of TC components shall be transmitted to the gprsSSF with a TC-END request primitive, basic end. +- The GPRS dialogue shall be closed. +- The gprsSSF shall apply Default GPRS Handling from the valid CSI to the PDP Context or GPRS Session. + +If, in violation of the above procedure, an ERROR or REJECT component is received with a TC-CONTINUE indication primitive, then the gprsSSF shall abort the dialogue with a TC-U-ABORT request primitive and shall apply Default GPRS Handling from the valid CSI to the PDP Context or GPRS Session. + +##### 14.1.4.2.2 gprsSSF-to-gsmSCF messages + +The present subclause defines the abnormal procedures for TC messages from the gprsSSF to the gsmSCF. + +Operation errors and rejection of TC components shall be transmitted to the gsmSCF according to the following rules: + +- The TC dialogue shall be maintained when the preceding message, which contained the erroneous component, indicated that the dialogue shall be maintained. I.e. the error or reject shall be transmitted with a TC-CONTINUE request primitive. +On receipt of an ERROR or REJECT component the gsmSCF decides on further processing. It may either continue, explicitly end or abort the TC dialogue. If the TC dialogue is closed due to such error, then the GPRS dialogue shall also be closed. +- on expiration of application timer Tssf, the TC dialogue shall be terminated by means of by TC-U-ABORT primitive with an Abort reason. The GPRS dialogue shall be closed. + +If the error processing in the gprsSSF leads to the case where the gprsSSF is not able to process further gsmSCF operations while the TC dialogue is to be maintained, then the gprsSSF aborts the TC dialogue with a TC-END request + +primitive with basic end or a TC-U-ABORT request primitive, depending on whether any pending ERROR or REJECT component is to be sent or not. + +The gprsSSF can end a TC dialogue with a TC-U-ABORT request primitive in the following case: + +- Any entity other than the gsmSCF initiates closure of the GPRS dialogue, and +- The gprsSSF has no pending reports, and +- The gprsSSF has no armed EDP to notify the gsmSCF that the GPRS dialogue has been closed. + +For an alternative method, see subclause 14.1.7.1.1. + +#### 14.1.4.2.3 Default GPRS Handling + +If a TC dialogue is closed due to unrecoverable TC/protocol error (does not apply to the overlapping TC dialogues), or aborted by the gsmSCF, or at the Tssf expiry, then the gprsSSF shall check the applicable Default GPRS Handling parameter of the GPRS-CSI. In this context the applicable Default GPRS Handling is the one that corresponds the TDP that opened the GPRS dialogue. The same default handling shall apply to all state models that are controlled by the particular GPRS dialogue. + +## 14.2 Services assumed from SCCP + +The present subclause describes the services required from the SCCP that may be used by the CAMEL applications for the CAMEL Application Part (CAP) used between the gsmSSF, assisting gsmSSF, gsmSRF, gprsSSF, and gsmSCF. + +The following SCCP revisions are supported by CAP: + +- Signalling Connection Control Part, Signalling System no. 7 CCITT ("Blue Book SCCP") +- Signalling Connection Control Part, Signalling System no. 7 ITU-T Recommendation Q.711 to Q.716 ("White Book SCCP") + +NOTE: Support of White Book SCCP at the receiving side shall be mandated from 00:01hrs, 1st July 2002(UTC). + +- ANSI T1.112-1996 [91]: "American National Standards for Telecommunications– Signalling System Number 7 (SS7) – Signalling Connection Control Part (SCCP)". + +When CAP uses White Book SCCP to send a message, and SCCP segments the message into one or more XUDT messages, then the transmission of this message may fail. + +Failure will occur when the destination SCCP, or any intermediate SCCP, does not support White Book SCCP. + +Support of ANSI T1.112-1996 [91] SCCP applies to PLMNs in North America only. Interworking between a PLMN in North America and a PLMN outside North America will involve a STP to translate between ANSI SCCP and ITU-T/CCITT SCCP. + +### 14.2.1 Normal procedures + +The SCCP forms the link between the TC and the MTP and provides (in conjunction with the MTP) the network services for the CAMEL applications. The network services provided allow the signalling messages sent by the application to the lower layers to be successfully delivered to the peer application. + +### 14.2.2 Service functions from SCCP + +#### 14.2.2.1 SCCP connectionless services + +The services described are those given in the SCCP ITU-T recommendations Q.711 to Q.716 should be consulted to identify possible interworking and compatibility issues between the different SCCP versions. + +The following Connection-less services are expected from the SCCP: + +- a) Network Addressing to enable signalling connections between SCCP users; + +- b) Sequence Control to enable the SCCP users to invoke "sequence guaranteed" or "sequence not guaranteed" options for a given stream of messages to the same destination; +- c) Segmentation/reassembly of large user messages (for "White Book SCCP" only); +- d) Return Option to enable the SCCP users to invoke "discard message on error" or "return message on error" for a given message not able to be delivered by the SCCP to the destination SCCP user, due to routeing or segmentation/re-assembly failure; +- e) Congestion control. + +The primitives used for the above services are given below. + +The N-UNITDATA request and N-UNITDATA indication primitives are used to send and receive data. The parameters of these primitives include the Called and Calling Addresses, Sequence Control, Return Option and User Data with the addressing parameters always mandatory. + +The N-NOTICE indication primitive is used to return undelivered data if return option is set and a routeing/segmentation error occurs. + +#### 14.2.2.1.1 Sub-System Number (SSN) + +The use of SSN is a network operator option and values for intra-PLMN usage are network specific. A CAP SSN has been reserved for inter-PLMN use, as defined in 3GPP TS 23.003 [5]. + +#### 14.2.2.1.2 Addressing + +The addressing elements consist of information contained within the Calling and the Called Party Addresses which are sent by the application to the lower layers. + +The application expects the SCCP to route messages by either (a) the use of the Destination Point Code (DPC) plus the Subsystem Number (SSN), or (b) the use of the GT plus optionally the SSN. The application also specifies to the lower layer whether to route the message on the DPC or the GT. + +Method (a) above may be used when the application is aware of the destination point code and the destination SSN located at that point code to which the message is to be delivered. Within a national network different SSNs, according to ITU-T Recommendation Q.713 [42], may be allocated for the different network specific applications, e.g. a SSN may be allocated for a gsmSCF functionality. + +Method (b) above may be used when a message is to be delivered to a SCCP-user which can be identified by the combination of the elements within the GT. An example of the use of this method is when messages have to be delivered between different networks. This method may be used since the originating network is unaware of the point code and SSN's allocations within the destination network. The network that determines the end-node to which the message is to be delivered has to perform a GT Translation to derive the destination Point Code and the SSN. If optionally the original address contained the SSN, then this may be used as the destination SSN, or the translation may, if required, provide an appropriate new SSN. + +When GT is used for addressing, the CAMEL application expects that the SCCP supports the following elements as defined in ITU-T Recommendation Q.713 [42]: + +##### *Address Indicator:* + +The application will set this indicator to indicate one or any combination of the elements "signalling point code, GT, subsystem number" in the address information octets. + +##### *GT Indicator:* + +This indicator specifies the method employed for the formatting of the address information. There are four values (1 to 4), for example, the value 4 indicates that the format includes the numbering plan, the nature of the address indicator and the translation type. The format with the indicator value 4 is always used for internetwork connections. + +##### *Translation Type:* + +The Translation Types are defined within ITU-T Recommendation Q.713 [42]. + +*Numbering Plan:* + +- 1) The *proposed* "generic numbering plan" is described within the ITU-T Recommendation Q.713 [42]. This numbering plan identifies the SCCP nodes or SCCP subsystems unambiguously such that messages may be efficiently routed within one or more networks, and is particularly useful when used in the Calling Address for the sending of a response message back to the originating node. This is achieved by having an international and a national part in the generic numbering plan. For response messages the responding node analyses the international part of the generic numbering plan to determine the gateway node to which the response is to be routed. Having routed to the gateway node, the national part (which was populated within the originating network) is analysed to determine the originating node within the originating network. +- 2) A numbering plan which would define particular nodes based specifically on services is outside the scope of CAMEL. +- 3) The SCCP caters for a number of other numbering plans (e.g. ISDN, Mobile etc. numbering plans). The whole range catered for is shown in [?]. These may be used by CAMEL applications if deemed suitable. + +*Encoding Scheme:* + +This identifies the encoding scheme employed by the application and is generally BCD encoded with odd or even number of digits. + +*GT Address Information:* + +These are the actual address digits supplied by the application and may be BCD digits or encoded as indicated by the encoding scheme. + +The network provider must ensure that any change of GT value during translation preserves any CAP specific information contained in the initial GT value. + +This requirement applies to all interfaces, not just those used for internetworking. + +If *route on SSN* is to be supported from the originating node, then an ITU-T non-zero internationally standardised SSN is required for international internetworking. + +In the absence of a ITU-T standardised non-zero SSN for CAP services, the use of *route on GT* is mandatory from the origin node to the network containing the destination node. + +When the SCCP of CCITT Signalling System No. 7 is used, the format and coding of address parameters carried by the SCCP for that purpose shall comply with ITU-T Recommendation Q.713 [42] with the following restrictions: + +- 1) Intra-PLMN addressing + +For communication between entities within the same PLMN, the use of SCCP addressing is network specific, and method (a) and (b) are both applicable. + +- 2) Inter-PLMN addressing + +method (b) with the mandatory SSN is applicable only with the following format: + +- i) Called Party Address + +- SSN indicator = a standardised SSN shall be used. The SSN used shall be that specified for CAP in 3GPP TS 23.003 [5]; +- Point Code indicator = 0; +- Global title indicator = 0100 (Global title includes translation type, numbering plan, encoding scheme and nature of address indicator); +- Translation type = 0 (Not used); +- Routing indicator = 0 (Routing on global title); + +The format is also described in the table 14-2 below (for NP=1, NAI=4): + +**Table 14-2: Called Party Address format** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------------------|-------------------------------------------------|----------------|---|-----------------------------------|---|----------|---------|----------| +| 0 | RI = 0 | GTI = 4 (0100) | | | | SSNI = 1 | PCI = 0 | Octet 1 | +| SSN = a value for CAP as specified in 3GPP TS 23.003 [5] | | | | | | | | Octet 2 | +| Translation type = 0 | | | | | | | | Octet 3 | +| Numbering plan = 1 (E.164) | | | | Encoding scheme = 1 or 2 | | | | Octet 4 | +| 0 | Nature of address indicator = 4 (International) | | | | | | | Octet 5 | +| Country code digit 2 (if present) | | | | Country code digit 1 | | | | Octet 6 | +| National Destination Code (NDC) Digit 1 | | | | Country code digit 3 (if present) | | | | Octet 7 | +| NDC digit 3 (if present) | | | | NDC digit 2 (if present) | | | | Octet 8 | +| NDC digit 5 (if present) | | | | NDC digit 4 (if present) | | | | Octet 9 | +| Equipment identification digit 2 | | | | Equipment identification digit 1 | | | | Octet 10 | +| ... | | | | ... | | | | ... | +| filler = 0 (if needed) | | | | Equipment identification digit m | | | | Octet n | + +Note Country code, National Destination Code, and SN(equipment id) are provided as example, so each digit may differ for each Inter-PLMN addressing case. (e.g., there is a case where only CC digit 1 shall be used). See ITU-T Recommendation Q.713 [42] for translation rules. + +## ii) Calling Party Address + +- SSN indicator = a standardised SSN shall be used. The SSN used shall be that specified for CAP in 3GPP TS 23.003 [5]; +- Point code indicator = 0; +- Global title indicator = 0100 (Global title includes translation type, numbering plan, encoding scheme and nature of address indicator); +- Translation type = 0 (Not used); +- Routing indicator = 0 (Routeing on Global Title). + +The format is also described in the table 14-3 below (for NP=1, NAI=4): + +**Table 14-3: Calling Party Address format** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|----------------------------------------------------------|-------------------------------------------------|---------|---|-----------------------------------|---|----------|---------|----------| +| 0 | RI = 0 | GTI = 4 | | | | SSNI = 1 | PCI = 0 | Octet 1 | +| SSN = a value for CAP as specified in 3GPP TS 23.003 [5] | | | | | | | | Octet 2 | +| Translation type = 0 | | | | | | | | Octet 3 | +| Numbering plan = 1 (E.164) | | | | Encoding scheme = 1 or 2 | | | | Octet 4 | +| 0 | Nature of address indicator = 4 (International) | | | | | | | Octet 5 | +| Country code digit 2 (if present) | | | | Country code digit 1 | | | | Octet 6 | +| National Destination Code (NDC) Digit 1 | | | | Country code digit 3 (if present) | | | | Octet 7 | +| NDC digit 3 (if present) | | | | NDC digit 2 (if present) | | | | Octet 8 | +| NDC digit 5 (if present) | | | | NDC digit 4 (if present) | | | | Octet 9 | +| Equipment identification digit 2 | | | | Equipment identification digit 1 | | | | Octet 10 | +| ... | | | | ... | | | | ... | +| Filler = 0 (if needed) | | | | Equipment identification digit m | | | | Octet n | + +Note Country code, National Destination Code, and SN(equipment id) are provided as example, so each digit may differ for each Inter-PLMN addressing case. (e.g., there is a case where only CC digit 1 shall be used). See ITU-T Recommendation Q.713 [42] for translation rules. + +When the SCCP of ANSI Signalling System No. 7 is used, the format and coding of address parameters carried by the SCCP for the purpose of signalling transfer shall comply with ANSI Recommendation T1.112-1996 [91] with the following restrictions: + +## 1) Intra-PLMN addressing + +For communication between entities within the same PLMN, the use of SCCP addressing is network specific. + +## 2) Inter-PLMN addressing + +### a) Called Party Address + +- SSN indicator = a standardised SSN shall be used. The SSN used shall be that specified for CAP in 3GPP TS 23.003 [5]; +- Point Code indicator = 0; +- Global title indicator = 0010 (Global title includes translation type); +- the Translation Type (TT) field shall be coded according to the content of the address information as follows: + - TT = 9 (decimal), if IMSI is included; or + - TT = 14 (decimal), if MSISDN is included; or + - TT = 10 (decimal), if a Network Element address is included. (If TT=10, then Number Portability is not applicable, if TT=14, then Number Portability is applicable) +- Routing indicator = 0 (Routeing on global title); + +### b) Calling Party Address + +- SSN indicator = a standardised SSN shall be used. The SSN used shall be that specified for CAP in 3GPP TS 23.003 [5]; +- Point code indicator = 0; +- Global title indicator = 0010 (Global title includes translation type); +- the Translation Type (TT) field shall be coded according to the content of the address information as follows: + - TT = 9 (decimal), if IMSI is included; or + - TT = 14 (decimal), if MSISDN is included; or + - TT = 10 (decimal), if a Network Element address is included. (If TT=10, then Number Portability is not applicable, if TT=14, then Number Portability is applicable) +- Routing indicator = 0 (Routeing on Global Title). + +### 14.2.2.1.3 Sequence control + +The application will specify whether SCCP protocol class 0 or 1 is required. Class 0 provides a basic connection-less service where the sequence of message delivery is not guaranteed. Class 1 connection-less service provides a guaranteed sequence delivery of messages (with the same called address) for a given stream of messages. Class 1 shall be requested by any application that can send more than 1 TC message to its peer (consecutive TR-CONTINUE) before receiving a response from its peer (TR-CONTINUE or TR-END). + +On receipt of a TC-RESULT-NL indication, the TC-USER shall request the transfer of a reject component using TC-U-REJECT request primitive, with the appropriate problem code (mistyped parameter). + +The return option may be used if requested by the application (Network Operator to determine). + +### 14.2.2.1.4 Return on error + +Return on Error mechanism may be required by the CAMEL applications such that the application is aware of messages that have not been delivered to the destination by the SCCP. The return option allows the return of the message that was not delivered due to routeing or segmentation/re-assembly failure back to the issuing user. This return option may be required in all segments of a long message or only in the first segment by the CAMEL applications. + +If the return option is invoked by the application and the message is not delivered, then the SCCP specifies the "return reason" as specified in ITU-T Recommendation Q.713 [42]. The N-NOTICE primitive is used to return the undelivered message to the originating user. + +#### 14.2.2.1.5 Segmentation / reassembly + +The application expects that since the SCCP can send up to 260 octets of user data (including the address information and TC-message) in a UDT message (248 octets in a XUDT message performing segmentation and congestion control), segmentation is available for long user messages. + +Also the SCCP is expected to perform the reassembly function on received segmented messages and deliver the reassembled message to the user. + +However, it should be noted that even though the theoretical maximum size of SCCP-user data and addresses that can be segmented by the SCCP is 3 968 octets, the SCCP-user would limit the length to about 2 560 octets to allow for the largest known addresses. Note that the application must also allow for the octets used for the TC-message in the 2 560 octets. + +The CAMEL application does not expect the SCCP to segment the long message into more than 16 segments. + +#### 14.2.2.1.6 Congestion control + +To help control of possible congestion that might occur in the lower layers the application may assign a value to indicate the importance of the message. The use of this parameter requires the use of SCCP (1997) ITU-T Recommendations. + +Also there exist other congestion control mechanisms as indicated below in SCCP Management. + +These congestion control methods are network operator option in the case of intra-PLMN network signalling, and shall not be used in the case of inter-PLMN network signalling. + +#### 14.2.2.2 SCCP connection oriented services + +The use by CAMEL applications for the Connection-oriented services is outside the scope of CAMEL. + +#### 14.2.2.3 SCCP management + +The subsystems used within the CAMEL application expect the SCCP to provide management procedures to maintain network performance by re-routeing in the event of failure of a subsystem, and in the case of network congestion by use of the congestion handling procedure. These procedures have appropriate interactions with the SCCP user as described in ITU-T Recommendations Q.713 [42] and ITU-T Recommendation Q.714 [43]. + +To achieve the above the SCCP is expected to perform the following procedures: + +- Signalling point status management (which include the signalling point prohibited, signalling point allowed, signalling point congested, and local MTP availability sub procedures). +- Subsystem status management (which include the subsystem prohibited, subsystem allowed, and subsystem status test sub procedures). +- Co-ordinated state change (a procedure which allows a duplicated subsystem to be withdrawn from service without affecting the performance of the network). + +These SCCP management procedures are network operator option in the case of intra-PLMN network signalling, and shall not be used in the case of inter-PLMN network signalling. + +## Annex A (normative): Mapping between CAP and ISUP + +### A.1 InitialDP operation + +Table A.1 + +| ISUP message
IAM (Note 1) | CAP Operation
InitialDP | +|-----------------------------------------------------------------------------------------------|---------------------------------------------------------------------| +| Called party number (note 6) | CalledPartyNumber | +| Calling party number | CallingPartyNumber | +| Calling party's category | CallingPartysCategory | +| Location number | LocationNumber | +| Original called number | OriginalCalledPartyID | +| User teleservice information (1 st priority) | HighLayerCompatibility | +| High layer compatibility IE contained in access transport (2 nd priority) (Note 2) | | +| High layer compatibility IE contained in access transport (Note 2) | HighLayerCompatibility2 | +| Low Layer compatibility IE contained in access transport (note 4) | LowLayerCompatibility | +| Low Layer compatibility IE contained in access transport (note 4) | LowLayerCompatibility2 | +| Generic number "additional calling party number" | AdditionalCallingPartyNumber | +| User service information prime (1 st priority) | BearerCapability | +| User service information (2 nd priority) (Note 3) | | +| User service information (Note 3) | BearerCapability2 | +| Redirecting number | RedirectingPartyID | +| Redirection information | RedirectionInformation | +| Call diversion treatment indicators | ServiceInteractionIndicatorsTwo.Call diversion treatment indicators | +| Conference treatment indicators | ServiceInteractionIndicatorsTwo.Conference treatment indicators | +| User-to-user indicators (Note 5) | UU-Data.UUIndicator | +| User-to-user information (Note 5) | UU-Data.UUI | + +NOTE 1: Optional parameters may be absent, i.e. they are only mapped only if these parameters are available at the DP. + +NOTE 2: If two high layer compatibility information elements are contained in the access transport parameter, then the second information element, carrying the preferred HLC, is mapped to the CAP highLayerCompatibility parameter, and the first information element, carrying the less preferred HLC, is mapped to the CAP highLayerCompatibility2 parameter. + +NOTE 3: If User service information prime and User service information are present, then one of the following two mapping rules shall be applied. The principles for the choice of mapping rule are specified in 3GPP TS 23.078 [7]. + +- One of User service information prime or User service information is mapped to Bearer Capability. +- User service information prime is mapped to BearerCapability and User service information is mapped to Bearer Capability2. + +NOTE 4: If two low layer compatibility information elements are contained in the access transport parameter, then the first information element, carrying the preferred LLC, is mapped to the CAP lowLayerCompatibility parameter, and the second information element, carrying the less preferred LLC, is mapped to the CAP lowLayerCompatibility2 parameter. + +NOTE 5: If present in ISUP IAM, user-to-user indicators and user-to-user information may optionally be mapped into the InitialDP Operation. + +NOTE 6: For trunk originating calls using overlap signalling, the called party number may contain partial address digits. + +## A.1.1 EventReportBCSM Operation + +Table A.1.1 + +| ISUP message
SAMs (Note 1) | CAP Operation
EventReportBCSM | +|-------------------------------|----------------------------------| +| Subsequent number | CalledPartyNumber | + +NOTE 1: For trunk originating calls using overlap signalling, subsequent address digits may be reported to the gsmSCF in EventReportBCSM, if requested by the gsmSCF with the 'Collect Information' operation. + +## A.2 ContinueWithArgument operation + +Table A.2 illustrates the mapping of parameters received in the ContinueWithArgument operation to parameters sent in the ISUP IAM to the succeeding exchange. All parameters which were received in the ISUP IAM and which are not replaced by parameters mapped from the ContinueWithArgument operation, shall be treated (and propagated to the succeeding exchange) according to the normal procedures. Propagation of ISUP parameters and mapping of parameters according to Table A.2 applies also for CWA when used to set up a new party leg in an existing call, except when the existing call is a NC call, in which case only mapping of parameters according to Table A.2 applies. The rule of copying ISUP parameters received from incoming leg to NP leg is valid also when the incoming leg no longer exists. + +For trunk originating calls using overlap signalling, the called party number in ISUP IAM may contain partial address digits. Any address digits received in SAMs, before the ISUP IAM is sent out, may also be included in the called party number parameter. Any address digits received in SAMs, after the ISUP IAM is sent out and before an ISUP ACM is received, shall be passed on to the succeeding exchange as received. + +On sending of the ISUP IAM the awaiting address complete timer is started. If the timer expires, then the call is released in both directions and an appropriate indication is returned to the calling subscriber. + +Table A.2 + +| CAP Operation ContinueWithArgument (Note 1) | ISUP message IAM | +|---------------------------------------------|-------------------------------------------| +| callingPartysCategory | Calling party's category | +| genericNumbers | Generic number (Note 2) | +| serviceInteractionIndicatorTwo | See Table A.4 | +| cug-Interlock | Closed user group interlock code | +| cug-OutgoingAccess | Optional forward call indicators (Note 3) | + +NOTE 1: Optional parameters may be absent, i.e. they are mapped only if received. + +NOTE 2: The set of generic numbers received in the genericNumbers parameter is mapped to the appropriate number of Generic Number parameters in the ISUP IAM. This shall be performed irrespective of the value of the screening indicator in the ISUP calling party number. + +NOTE 3: The cug-OutgoingAccess is mapped to the Closed User Group indicator which is carried in bits A & B of the Optional forward call indicators. + +## A.3 Connect operation + +On receipt of a Connect operation from the gsmSCF the called party number used for routing is derived from the destinationRoutingAddress (see Table A.3). If the triggering of the CAMEL service was made for a mobile terminating call in the GMSC or VMSC or for a mobile forwarded call, then an ISUP ACM shall be sent to the preceding exchange. The encoding of the backward call indicators in the ISUP ACM is specified in 3GPP TS 09.12 [1]. + +On receipt of a Connect operation from the gsmSCF for a trunk originating call, the called party number used for routing is derived from the destinationRoutingAddress (see Table A.3) and an ISUP ACM is sent to the preceding exchange (in an overlap signalling scenario this will prevent any further SAMs being sent by the preceding exchange). + +Table A.3 illustrates the mapping of parameters received in the Connect operation to parameters sent in the ISUP IAM to the succeeding exchange. Parameters which were received in the ISUP IAM and are not replaced by parameters of the Connect operation are treated according to the normal procedures. + +On sending of the ISUP IAM the awaiting address complete timer is started. If the timer expires, then the call is released in both directions and an appropriate indication is returned to the calling subscriber. + +**Table A.3** + +| CAP Operation
Connect (Note 1) | ISUP message
IAM | +|-----------------------------------|-------------------------------------------| +| DestinationRoutingAddress | Called party number | +| OriginalCalledPartyID | Original called number | +| callingPartysCategory | Calling party's category | +| redirectingPartyID | Redirecting number | +| redirectionInformation | Redirection information | +| GenericNumbers | Generic number (Note 2) | +| ServiceInteractionIndicatorTwo | See Table A.4 | +| Cug-Interlock | Closed user group interlock code | +| cug-OutgoingAccess | Optional forward call indicators (Note 3) | + +NOTE 1: Optional parameters may be absent, i.e. they are mapped only if received. + +NOTE 2: The set of generic numbers received in the genericNumbers parameter is mapped to the appropriate number of Generic Number parameters in the ISUP IAM. This shall be performed irrespective of the value of the screening indicator in the ISUP calling party number. + +NOTE 3: The cug-OutgoingAccess is mapped to the Closed User Group indicator which is carried in bits A & B of the Optional forward call indicators. + +Table A.4 – Mapping of the CAP Connect and ContinueWithArgument operation serviceInteractionIndicatorsTwo to ISUP. + +Table A.4 + +| CAP
ServiceInteractionIndicators | ISUP parameter in | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | ACM/CPG/CON/ANM/REL | IAM | +| Call to be diverted indicator
– call diversion allowed
– call diversion not allowed | --- | Call diversion treatment indicators parameter
Call to be diverted indicator
– no indication
– call diversion allowed
– call diversion not allowed | +| Conference at DLE accept. ind.
– accept conference request
– reject conference request | --- | Conference treatment indicators parameter
Conference acceptance ind.
– no indication
– accept conference request
– reject conference request | +| Calling party restriction indicator
– no IN impact
– presentation restricted | --- | Calling party number address presentation restricted indicator
– no impact
– presentation restricted | +| Conference at OLE accept. ind.
– accept conference request
– reject conference request | ACM/CPG/CON/ANM: Conference treatment indicators parameter
Conference acceptance ind.
– no indication
– accept conference request
– reject conference request | --- | +| Call completion treatment indicator
– accept CCBS service request
– reject CCBS service request | REL, busy cause
Diagnostig field
– CCBS possible
– CCBS not possible | --- | +| Connected number treatment indicator
– no IN impact
– presentation restricted
– present called IN number
– present called IN number restricted | Note 3 | | + +## NOTE 3: + +If "no IN impact" was received for Connected number treatment indicator in the serviceInteractionIndicatorsTwo, then a connected number parameter and a generic number parameter "additional connected number" are passed on unchanged. + +If "presentation restricted" was received for Connected number treatment indicator in the serviceInteractionIndicatorsTwo, then: + +- If a connected number parameter has been received in the ISUP ANM or ISUP CON, then the address presentation restricted indicator is set to "presentation restricted". +- If a generic number parameter "additional connected number" has been received in the ISUP ANM or ISUP CON, then the address presentation restricted indicator is set to "presentation restricted". +- If a redirection number parameter has been received, then a redirection number restriction parameter is sent in the ISUP ANM with bits AB set to "presentation restricted". + +If "present called IN number" was received for Connected number treatment indicator in the serviceInteractionIndicatorsTwo, then: + +- If a connected number parameter has been received in the ISUP ANM or ISUP CON, then the connected number parameter is modified as follows: + +nature of address indicator and numbering plan indicator are encoded as received in the called party number of the ISUP IAM, + +address presentation restricted indicator: 00 (presentation allowed), + +address signals:as received in the called party number and possible subsequent number parameters, until the ISUP ACM was sent. + +- b) A generic number parameter "additional connected number" is deleted from the message, if applicable, +- c) A redirection number parameter is deleted from the relevant messages, if applicable. + +If "present called IN number restricted" was received for Connected number treatment indicator in the serviceInteractionIndicatorsTwo, then: + +- a) If a connected number parameter has been received in the ISUP ANM or ISUP CON, then the connected number parameter is modified as follows: + +nature of address indicator and numbering plan indicator are encoded as received in the called party number of the ISUP IAM, + +address presentation restricted indicator: 01 (presentation restricted), + +address signals:as received in the called party number and possible subsequent number parameters, until the ISUP ACM was sent. + +- b) A generic number parameter "additional connected number" is deleted from the message, if applicable, +- c) A redirection number parameter is deleted from the relevant messages, if applicable. + +--- + +## A.4 AssistRequestInstructions operation + +If an ISUP IAM is received at an assisting SSP containing an assisting gsmSSF or at an IP containing a gsmSRF, then an AssistRequestInstructions operation is sent to the gsmSCF. The correlationID parameter in the AssistRequestInstructions operation can contain: + +- a) the CorrelationID digits extracted from the ISUP IAM Called Party Number, +- b) the whole Called Party Number received in the ISUP IAM (CorrelationID digits extracted at gsmSCF), +- c) the contents of the ISUP IAM CorrelationID parameter. + +In the case where the gsmSCF and the assisting gsmSSF are both in the HPLMN and ISUP 97 is supported then any of these mechanisms may be used. + +In the case where the gsmSCF and the assisting gsmSSF are both in the HPLMN and ISUP 97 is not supported then mechanisms a) and b) may be used. + +In the case where the gsmSCF is in the HPLMN and the assisting gsmSSF is in the VPLMN then only mechanism b) may be used when an all-ISUP 97 signalling path cannot be guaranteed. Mechanism a) may be used if bilateral agreements on the format of the information transferred in the ISUP IAM Called Party Number are defined between the HPLMN and the VPLMN. + +In the case where the gsmSCF is in the HPLMN and the assisting gsmSSF is in the VPLMN then mechanism c) may only be used if an all-ISUP 97 signalling path can be guaranteed between the HPLMN and the VPLMN. + +--- + +## A.5 ConnectToResource operation + +On receipt of a ConnectToResource operation from the gsmSCF, the gsmSRF is connected to the call, to facilitate User Interactive dialogue with the user. + +If the User Interactive dialogue is to be performed at a forwarding MSC or at a terminating MSC (GMSC or VMSC), then an ISUP ACM shall be sent to the preceding exchange. The encoding of the backward call indicators in the ISUP ACM is specified in 3GPP TS 09.12 [1], with the Optional Backward Call Indicators indicating "in-band information or an appropriate pattern is now available". + +If the User Interactive dialogue is to be performed at a forwarding MSC or at a terminating MSC (GMSC or VMSC), then when the gsmSRF indicates through-connection and the ConnectToResource operation indicates that a bothway + +throughconnection is required, an ISUP ANM shall be sent to the preceding exchange if answer has not previously been sent. As a network operator/equipment vendor option an ISUP CPG message may be sent if ISUP ANM has already been sent. + +## A.6 EstablishTemporaryConnection operation + +On receipt of an EstablishTemporaryConnection operation from the gsmSCF then if the triggering of the CAMEL service was made for a mobile terminating call in the GMSC or VMSC or for a forwarded call, then an ISUP ACM shall be sent to the preceding exchange. The encoding of the backward call indicators in the ISUP ACM is specified in 3GPP TS 09.12 [1]. In addition, an ISUP IAM shall be sent to the succeeding exchange. + +Table A.5 illustrates the mapping of parameters received in the EstablishTemporaryConnection operation to parameters sent in the ISUP IAM to the succeeding exchange. On sending of the ISUP IAM the awaiting address complete timer is started. If the timer expires, then the call is released in both directions and an appropriate indication is returned to the calling subscriber. + +**Table A.5** + +| CAP Operation
EstablishTemporaryConnection | ISUP message
IAM | +|-----------------------------------------------|---------------------------------| +| AssistingSSPIPRoutingAddress (note 1) | Called party number | +| CorrelationID | Correlation id (note 2) | +| ScfId | GsmSCF id (note 2) | +| OriginalCalledPartyID | Original called number (note 3) | +| CallingPartyNumber | Calling party number (note 3) | + +NOTE 1: The AssistingSSPIPRoutingAddress parameter may also include a Hex B digit, in order to delineate the boundary between digits used for routing and digits forming part of the SCFiD and/or CorrelationID. + +NOTE 2: These optional parameters may be absent, i.e. they are mapped only if received. If they are received and cannot be mapped, then an error is sent to the gsmSCF as detailed in clause 11. + +NOTE 3: These optional parameters may be absent, i.e. they are mapped only if received. + +Except for the Called Party Number the remaining mandatory ISUP IAM parameters are set as follows: + +a) Nature of connection indicators + +Satellite indicator: set as in an Originating MSC, + +Continuity check indicator: set as in Originating MSC, + +Echo control device indicator: set as in Originating MSC + +b) Forward Call Indicators + +National/international call indicator: set as in Originating MSC, + +End-to-end method indicator: 00 (no end-to-end method available), + +Interworking indicator: 0 (no interworking encountered), + +End-to-end information indicator: 0 (no end-to-end information available), + +ISDN User Part indicator: 1 (ISDN User Part used all the way), + +ISDN User Part preference indicator: 00 (ISDN User Part preferred all the way), + +ISDN access indicator: 0 (originating access non-ISDN), + +SCCP method indicator: 00 (no indication) + +c) Calling Party's Category + +00001010 (ordinary subscriber) + +d) Transmission Medium Requirement + +00000011 (3.1 kHz audio) + +The ISUP IAM optional parameter Propagation Delay Counter is set as in an Originating MSC. + +## A.7 ReleaseCall operation + +Upon receipt of the ReleaseCall operation, the GMSC/gsmSSF (VMSC/gsmSSF) sends REL messages in both directions. The cause indicators parameter contains the releaseCallArg parameter of the ReleaseCall operation. + +## A.8 InitiateCallAttempt operation + +On receipt of an InitiateCallAttempt operation, the GMSC/gsmSSF or VMSC/gsmSSF prepares to set up a new call leg in an existing call configuration, or to set up a new call, to the destination defined by the DestinationRoutingAddress parameter. The GMSC/gsmSSF or VMSC/gsmSSF does not send the ISUP IAM until it has received a ContinueWithArgument operation, which contains additional information needed to populate the parameters of the ISUP IAM. + +For a new call leg in an existing call, except a NC call, all parameters which were received in the ISUP IAM and which were not replaced by parameters mapped from the InitiateCallAttempt or ContinueWithArgument operation, shall be treated (and propagated to the succeeding exchange) according to the normal procedures. The rule of copying ISUP parameters received from incoming leg to NP leg is valid also when the incoming leg no longer exists. + +Table A.6 illustrates the mapping of parameters received in the InitiateCallAttempt operation to parameters sent in the ISUP IAM to the succeeding exchange. + +**Table A.6** + +| CAP Operation
InitiateCallAttempt (Note 1) | ISUP message
IAM | +|-----------------------------------------------|---------------------------------------------------| +| DestinationRoutingAddress | Called party number | +| CallingPartyNumber | Calling party number | +| | Transmission medium requirement (Note 2) (Note 4) | +| | Access transport (Note 3) (Note 4) | + +NOTE 1: Optional parameters may be absent, i.e. they are mapped only if received. + +NOTE 2: The transmission medium requirement parameter field shall be set to "speech". + +NOTE 3: The "Bearer capability" and "High layer compatibility information" elements shall be filled in accordance with ETSI EN 300 403-1 [25] for speech call. + +NOTE 4: Only the minimum set of parameters indicating the fact that the call is a speech call is described here. + +--- + +## Annex B (normative): Mapping between CAP and MAP and mapping between CAP and SM-CP + +The Short Message signalling between the SMS-GMSC and the MSC or SGSN, for the transport of SM RP-DUs, is specified in 3GPP TS 29.002 [11]. The Short Message signalling between the MSC or SGSN and the MS, for the transport of SM RP-DUs, is specified in 3GPP TS 24.011 [10]. + +--- + +### B.1 Mapping between CAP and MAP + +#### B.1.1 MO-SMS + +##### B.1.1.1 ConnectSMS operation + +The Short Message TPDU is carried by a Short Message RPDU. The RPDU between the MSC or SGSN and the SMS-IWMSC is conveyed in the MAP MO-ForwardSM OPERATION. The MSC or SGSN shall obtain information from CAP OPERATION ConnectSMS and place it in MAP OPERATION MO-ForwardSM. + +**Table B.1** + +| CAP ConnectSMS | MAP MO-ForwardSM ARGUMENT | +|-----------------------------|------------------------------------------------| +| CallingPartysNumber | sm-RP-OA; CHOICE set to msisdn | +| DestinationSubscriberNumber | sm-RP-UI; TP-Destination-Address | +| SMSCAddress | sm-RP-DA; CHOICE set to serviceCentreAddressDA | + +NOTE The encoding of "SignalInfo" in MO-ForwardSM is specified in 3GPP TS 23.040 [6]. + +##### B.1.1.2 EventReportSMS operation + +The MSC or SGSN may receive error information from the SMS-IWMSC, via the MAP OPERATION MO-ForwardSM ERROR. The MSC or SGSN shall obtain the error information from MAP OPERATION MO-ForwardSM and place it in the CAP OPERATION EventReportSMS. + +**Table B.2** + +| CAP EventReportSMS | MAP MO-ForwardSM ERROR | +|--------------------|--------------------------------------------------------------------------------| +| MO_SMS Cause | SM-DeliveryFailure; SM-DeliveryFailureCause; SM-EnumeratedDeliveryFailureCause | + +## B.1.2 MT-SMS + +### B.1.2.1 InitialDPSMS operation (MT-SMS) + +The Short Message TPDU is carried by a Short Message RPDUs. The RPDUs between the SMS-GMSC and the MSC or SGSN is conveyed in the MAP MT-ForwardSM OPERATION ARGUMENT. The MSC or SGSN shall obtain information from the MT-ForwardSM MAP Message and place it in CAP InitialDPSMS. + +Table B.3 + +| CAP InitialDPSMS | MAP MT-ForwardSM ARGUMENT | +|----------------------------|------------------------------------------------------------------------------------------| +| CallingPartysNumber | TP-Originating-Address from SMS-Deliver-TPDU. SMS-Deliver-TPDU is contained in sm-RP-UI. | +| SMSCAddress | sm-RP-OA | +| TPShortMessageSpecificInfo | First OCTET of the TPDU. The TPDU is contained in sm-RP-UI. | +| TPProtocolIdentifier | TP-Protocol-Identifier of the TPDU. The TPDU is contained in sm-RP-UI. | +| TPDataCodingScheme | TP-Data-Coding-Scheme of the TPDU. The TPDU is contained in sm-RP-UI. | +| TPValidityPeriod | TP-Validity-Period of the TPDU. The TPDU is contained in sm-RP-UI. | + +NOTE The encoding of "SignalInfo" in MT-ForwardSM is specified in 3GPP TS 23.040 [6]. + +### B.1.2.2 ReleaseSMS operation (MT-SMS) + +When the MSC or SGSN receives the CAP ReleaseSMS operation, it shall return a RP-ERROR RPDUs to the SMS-GMSC. The RP-ERROR RPDUs between the MSC or SGSN and the SMS-GMSC is conveyed in the MAP MT-ForwardSM OPERATION ERROR. + +Table B.4 + +| CAP ReleaseSMS | MAP MT-ForwardSM ERROR | +|----------------|--------------------------------------------------------------------------------| +| RPCause | SM-DeliveryFailure; sm-DeliveryFailureCause; sm-EnumeratedDeliveryFailureCause | + +## B.2 Mapping between CAP and SM-CP + +### B.2.1 MO-SMS + +#### B.2.1.1 InitialDPSMS operation + +The Short Message TPDU is carried by a Short Message RPDUs. The RPDUs between the MS and the MSC or SGSN is conveyed in the RP-DATA Relay Message. The MSC or SGSN shall obtain information from the RP-DATA Message and place it in CAP InitialDP OPERATION. + +Table B.5 + +| CAP InitialDPSMS ARGUMENT | SM-CP RP-DATA Message | +|-----------------------------|-----------------------------------------------| +| DestinationSubscriberNumber | RP-User Data; TPDU; TP-Destination-Address | +| SMSCAddress | RP-User Data; RP-Destination Address | +| TPShortMessageSpecificInfo | RP-User Data; TPDU; 1 st octet | +| TPProtocolIdentifier | RP-User Data; TPDU; TP-Protocol-Identifier | +| TPDataCodingScheme | RP-User Data; TPDU; TP-Data-Coding-Scheme | +| TPValidityPeriod | RP-User Data; TPDU; TP-Validity-Period-Format | + +## B.2.1.2 ReleaseSMS operation + +When the MSC or SGSN receives the CAP ReleaseSMS operation, it shall return a RP-ERROR RPDUs to the MS. The RP-ERROR RPDUs between the MSC or SGSN and the MS is conveyed in the RP-ERROR Relay Message. The MSC or SGSN shall obtain the RPCause from the CAP ReleaseSMS OPERATION and place it in the RP-ERROR Message. + +**Table B.6** + +| CAP ReleaseSMS ARGUMENT | SM-CP RP-ERROR Message | +|-------------------------|------------------------| +| RPCause | RP-Cause | + +## B.2.2 MT-SMS + +### B.2.2.1 ConnectSMS operation + +When the MSC or SGSN receives the ConnectSMS operation, it shall use the received information to replace data in the Short Message SMS-DELIVER TPDU. The SMS-DELIVER TPDU is carried in a RP-MT-DATA RPDUs. The RP-MT-DATA RPDUs between the MSC or SGSN and the MS is conveyed by the SM-CP CP-Data Message. + +**Table B.7** + +| CAP ConnectSMS | SM-CP RP-DATA Message | +|---------------------|--------------------------------------------| +| CallingPartysNumber | RP-User Data; TPDU; TP-Originating-Address | + +### B.2.2.2 EntReportSMS operation + +When the MSC or SGSN receives the RP-ERROR RPDUs from the MS, it shall send the RP-Cause to the gsmSCF. The RP-ERROR RPDUs between the MS and the MSC or SGSN is conveyed in the RP-ERROR Relay Message. The MSC or SGSN shall obtain the RPCause from the RP-ERROR Message and place it in CAP EventReportSMS. + +**Table B.8** + +| CAP EventReportSMS | SM-CP RP-ERROR Message | +|--------------------------|------------------------| +| EventSpecificInformation | RP-Cause | + +--- + +## Annex C (informative): Change history + +### Comments on CAMEL Phase 4 Rel-6 + +- For Release Rel-6, the version of module CAP-U-ABORT-Data is aligned with the other CAP modules; the module version is increased to version8(7). The increase of module version number does not affect the data type definitions contained within the module. +- CAP Operation "SpecialisedResourceReport" is spelled with a "z" (American spelling) in ASN.1. Therefore, TS 29.078 shall write in the text SpecializedResourceReport with a "z" consistently. +- For consistency purposes, module CAP-GPRS-ReferenceNumber is placed in a separate section. All CAP Modules (starting with BEGIN and ending with END) are specified in a separate section. +- The Rel-5 history overview ("How CAMEL Phase 4 Rel-5 Version 5.0.0 was created") is removed from the Rel-6 version of the present specification. + +| Date | TSG # | TSG Doc. | CR | Re
v | Subject/Comment | New | +|---------|-------|-----------|------|---------|--------------------------------------------------------------------------------------------------|--------| +| 2003-12 | CN#22 | NP-030527 | 332 | 1 | Collective CR for Rel-6 Enhanced Dialled Services | 6.0.0 | +| 2003-12 | CN#22 | NP-030528 | 343 | 1 | Change of position armed with criteria | 6.0.0 | +| 2004-03 | CN#23 | NP-040138 | 350 | 2 | Enhancement of Event Specific Information for DP 'Change of Position' | 6.1.0 | +| 2004-03 | CN#23 | NP-040095 | 352 | 1 | CAMEL4 SCUDIF notification during active call for prepay | 6.1.0 | +| 2004-03 | CN#23 | NP-040096 | 356 | 1 | LLC passes on the gsmSSF - gsmSCF interface | 6.1.0 | +| 2004-03 | CN#23 | NP-040136 | 360 | | Correction to description of Service Interaction Indicators Two parameter | 6.1.0 | +| 2004-03 | CN#23 | NP-040136 | 361 | | Correction to temporary connection establishment | 6.1.0 | +| 2004-03 | CN#23 | NP-040137 | 362 | | Correction to SplitLeg and MoveLeg preconditions | 6.1.0 | +| 2004-03 | CN#23 | NP-040138 | 363 | | Correction to Disconnect Leg preconditions | 6.1.0 | +| 2004-03 | CN#23 | NP-040138 | 364 | | Correction to GPRS protocol definition | 6.1.0 | +| 2004-06 | CN#24 | NP-040249 | 366 | 1 | Enhancement to User Interaction | 6.2.0 | +| 2004-06 | CN#24 | NP-040249 | 367 | 1 | Adding missing ROS Object Identifier | 6.2.0 | +| 2004-06 | CN#24 | NP-040207 | 370 | 1 | Mapping between ICA and IAM | 6.2.0 | +| 2004-06 | CN#24 | NP-040207 | 371 | | Correction to Tssf timer | 6.2.0 | +| 2004-06 | CN#24 | NP-040207 | 372 | | Correction to ERB pre-condition for gsmSSF FSM state | 6.2.0 | +| 2004-06 | CN#24 | NP-040207 | 374 | 2 | Correction to Move Leg pre-condition | 6.2.0 | +| 2004-06 | CN#24 | NP-040249 | 375 | | Correction to First Digit Timer for Prompt&Collect | 6.2.0 | +| 2004-09 | CN#25 | NP-040405 | 380 | | Support of User-to-User Information (UUI) in CAMEL InitialDP operation | 6.3.0 | +| 2004-09 | CN#25 | NP-040397 | 382 | 2 | Clarification on the handling of operation invocation when LinkedID is missing although expected | 6.3.0 | +| 2004-09 | CN#25 | NP-040406 | 383 | | Correction to usage of ACM for CAP ETC and CAP CTR | 6.3.0 | +| 2004-09 | CN#25 | NP-040406 | 384 | | Correction to Cancel procedure description | 6.3.0 | +| 2004-09 | CN#25 | NP-040406 | 385 | | Correction to SplitLeg ASN.1 description | 6.3.0 | +| 2004-09 | CN#25 | NP-040406 | 386 | | Correction to Apply Charging Report procedure | 6.3.0 | +| 2004-09 | CN#25 | NP-040406 | 387 | | Correction to Assist Request Instructions procedure | 6.3.0 | +| 2004-09 | CN#25 | NP-040406 | 388 | | Correction to Call Information Request and Report | 6.3.0 | +| 2004-09 | CN#25 | NP-040406 | 389 | | Correction to Tssf timer setting for SMS control | 6.3.0 | +| 2004-12 | CN#26 | NP-040544 | 390 | | Correction of wrong TS numbers in references | 6.4.0 | +| 2005-06 | CT#28 | CP-050103 | 392 | 1 | Additions to CAP for trunk originated services | 7.0.0 | +| 2005-09 | CT#29 | CP-050312 | 393 | 1 | Additions and clarifications to CAP for trunk originated services | 7.1.0 | +| 2005-12 | CT#30 | CP-050626 | 0396 | 1 | Support of an Operation Arg and Errors for CollectInformation | 7.2.0 | +| 2006-06 | CT#32 | CP-060311 | 0397 | 1 | Addition of information related to service change | 7.3.0 | +| 2007-09 | CT#37 | CP-070540 | 0399 | 2 | AC/ACR Handling | 7.4.0 | +| 2007-09 | CT#37 | CP-070540 | 0400 | | QoS Extension | 7.4.0 | +| 2008-12 | CT#42 | | | | Upgraded unchanged from Rel-7 | 8.0.0 | +| 2009-09 | CT#45 | CP-090523 | 0407 | | Correction to InvokeID syntax definition | 8.1.0 | +| 2009-12 | CT#46 | | | | Upgraded unchanged from Rel-8 | 9.0.0 | +| 2010-03 | CT#47 | CP-100029 | 0409 | 1 | User CSG Information for CAMEL | 9.1.0 | +| 2010-04 | | | | | Figures 4-1/4, 4-1/6 and 4-1/8 were not visible. Release corrected on cover page. | 9.1.1 | +| 2010-06 | CT#48 | CP-100261 | 0413 | | ASN.1 Module Version Update | 9.2.0 | +| 2011-03 | CT#51 | | | | Update to Rel-10 version (MCC) | 10.0.0 | +| 2011-09 | CT#53 | CP-110733 | 0414 | 2 | Extension parameter for Release Call | 11.0.0 | +| 2011-12 | CT#53 | CP-110813 | 0415 | 2 | Extension of ScfID parameter length | 11.1.0 | +| 2012-12 | CT#58 | CP-120749 | 0416 | 1 | CWA Correction and CWA and ICA Clarification | 11.2.0 | +| 2014-09 | - | - | - | - | Update to Rel-12 version (MCC) | 12.0.0 | +| 2015-12 | CT#70 | - | - | - | Update to Rel-13 version (MCC) | 13.0.0 | +| 2017-03 | CT#75 | - | - | - | Update to Rel-14 version (MCC) | 14.0.0 | +| 2018-06 | CT#80 | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-07 | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/29_series/29079/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-16/29_series/29079/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32aaf1a7220fc0c7e7f5114a8ae9ebee3124e514 --- /dev/null +++ b/marked/Rel-16/29_series/29079/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d136df3a5c80ec2f879cf8b6eaf8965a00fe8ab4c3544045a8255d6fd08177a +size 107138 diff --git a/marked/Rel-16/29_series/29079/4af57aad638888edf2062306f8a54a6c_img.jpg b/marked/Rel-16/29_series/29079/4af57aad638888edf2062306f8a54a6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f7818146309c8295a4ce35cf3949168d3bfe0f0 --- /dev/null +++ b/marked/Rel-16/29_series/29079/4af57aad638888edf2062306f8a54a6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb8c6633b220cee30ca6cac3866510150c13272001ffd4f12c3cc13e243e4d45 +size 79156 diff --git a/marked/Rel-16/29_series/29079/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-16/29_series/29079/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7c8a462207ad4ae12c98ac8da21d737ce38848f --- /dev/null +++ b/marked/Rel-16/29_series/29079/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:820b8027d118efe1efc00c961b58c144b5b86eb7f02468f1d4f444988c4654a4 +size 230446 diff --git a/marked/Rel-16/29_series/29079/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg b/marked/Rel-16/29_series/29079/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5352e691e1ec089486f9bbc84759b23605c6c9e9 --- /dev/null +++ b/marked/Rel-16/29_series/29079/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d26610e742bb6b3752e83f532205c964390c34b5658d55d47e6e09cb8dfdd0eb +size 78562 diff --git a/marked/Rel-16/29_series/29079/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg b/marked/Rel-16/29_series/29079/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f82004bf01cf70f79b31803e713666e6ba1197f --- /dev/null +++ b/marked/Rel-16/29_series/29079/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c35879b612acde1006a2e21c4704e40542a28aa951e4b136fe5dcd63754de3ae +size 164965 diff --git a/marked/Rel-16/29_series/29079/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/29_series/29079/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ceca180e76bbe61ea437ccde7e406139aa415b66 --- /dev/null +++ b/marked/Rel-16/29_series/29079/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:870636269d5033ad37a5d5a5e0add42948ac82103c1d95834222df22c0241c53 +size 221956 diff --git a/marked/Rel-16/29_series/29079/e05122559f56af5699789b7118d8fe87_img.jpg b/marked/Rel-16/29_series/29079/e05122559f56af5699789b7118d8fe87_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c24b42218fe26dd0823ba7d39e301914bb841dc --- /dev/null +++ b/marked/Rel-16/29_series/29079/e05122559f56af5699789b7118d8fe87_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fce5c4bfe61e21d7b2a1bd0303770733fa41196a6ddbe139e25b8f529aaf951c +size 243680 diff --git a/marked/Rel-16/29_series/29079/e94cbc0895c6914a2bb53f150ab7495e_img.jpg b/marked/Rel-16/29_series/29079/e94cbc0895c6914a2bb53f150ab7495e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7e81fbc9c1a47df2c723f1a72f3cdee2c337583 --- /dev/null +++ b/marked/Rel-16/29_series/29079/e94cbc0895c6914a2bb53f150ab7495e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d802f6861b152cc4df0d6cd9b736ca9f0c8193d6226659756339be56238402d8 +size 80363 diff --git a/marked/Rel-16/29_series/29079/raw.md b/marked/Rel-16/29_series/29079/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9f2361bfc363b96ad0077b99cdfa8d9a7ba3f5d4 --- /dev/null +++ b/marked/Rel-16/29_series/29079/raw.md @@ -0,0 +1,4157 @@ + + + + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +| | | +|------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations..... | 7 | +| 3.1 Definitions ..... | 7 | +| 3.2 Symbols..... | 8 | +| 3.3 Abbreviations ..... | 8 | +| 4 General..... | 8 | +| 5 Common SDP Procedures..... | 9 | +| 5.1 General ..... | 9 | +| 5.2 Encapsulation of previous SDP information..... | 9 | +| 5.2.1 Media level information ..... | 9 | +| 5.2.2 Session level information ..... | 9 | +| 5.3 Determination of codec related SDP information associated to a previous realm instance..... | 10 | +| 5.4 Modifying codec related information..... | 11 | +| 5.4.1 Modifying the format list..... | 11 | +| 5.4.2 Modifying preferred configurations ..... | 11 | +| 5.5 Additional handling for SDP answer with actual configuration ..... | 12 | +| 5.6 Procedures specific to OMR attributes..... | 12 | +| 5.6.1 General ..... | 12 | +| 5.6.2 instance-number ..... | 12 | +| 5.6.3 Session and media checksum calculation..... | 13 | +| 5.7 Roaming architecture for voice over IMS with local breakout..... | 13 | +| 5.8 II-NNI traversal scenario..... | 13 | +| 6 IMS-ALG procedures ..... | 13 | +| 6.1 IMS-ALG handling of initial SDP offer ..... | 13 | +| 6.1.1 General ..... | 13 | +| 6.1.2 Validating the received SDP offer..... | 14 | +| 6.1.3 Deciding whether to allocate a primary local MR and if any previous MR can be bypassed..... | 14 | +| 6.1.4 Bypassing previous MRs..... | 16 | +| 6.1.5 Bypassing no previous MRs..... | 16 | +| 6.1.6 Allocating a primary local MR..... | 16 | +| 6.1.7 Allocating no primary local MR..... | 17 | +| 6.1.8 Allocating secondary local MRs ..... | 17 | +| 6.1.9 Forwarding SDP offer ..... | 18 | +| 6.2 IMS-ALG handling of initial SDP answer..... | 18 | +| 6.2.1 General ..... | 18 | +| 6.2.2 IMS-ALG bypasses an allocated transcoding MR ..... | 18 | +| 6.2.3 IMS-ALG allocates a local transcoding MR when performing proactive transcoding without resource reservation..... | 19 | +| 6.2.4 IMS-ALG determines steps required to complete the handling of the SDP answer ..... | 20 | +| 6.2.5 Receiving an unspecified connection address and a visited-realm instance ..... | 20 | +| 6.2.6 Receiving an unspecified connection address and a secondary-realm instance..... | 21 | +| 6.2.7 Other handling when no primary local MR allocated ..... | 21 | +| 6.2.8 Retaining a primary or secondary local MR..... | 21 | +| 6.2.9 Forwarding the SDP answer..... | 22 | +| 6.3 IMS-ALG OMR media resource operations ..... | 23 | +| 6.3.1 General ..... | 23 | +| 6.3.2 IMS-ALG operations..... | 23 | +| 6.4 Handling of connected IP realms ..... | 23 | +| 7 UA Procedures ..... | 24 | +| 7.1 UA sending an initial SDP offer ..... | 24 | +| 7.2 UA receiving an initial SDP offer ..... | 24 | +| 7.2.1 General ..... | 24 | +| 7.2.2 Validating the incoming SDP offer ..... | 24 | + +- 7.2.3 UA may choose an alternate realm instance to bypass an upstream MR..... 25 +- 7.3 UA receiving an initial SDP answer ..... 25 + - 7.3.1 General ..... 25 + - 7.3.2 Receiving SDP answer with an unspecified connection address ..... 25 + - 7.3.3 Receiving SDP answer with a valid connection address..... 25 +- 7.4 UA OMR media resource operations..... 26 + - 7.4.1 General ..... 26 + - 7.4.2 UA operations..... 26 +- 7.5 Handling of connected IP realms ..... 26 +- 8 Subsequent SDP offer/answer transactions..... 26 + - 8.1 General ..... 26 + - 8.2 IMS-ALG and UA subsequent SDP offer procedures ..... 27 + - 8.3 IMS-ALG and UA subsequent SDP answer procedures..... 27 + - 8.4 Handling media resources during a subsequent SDP offer/answer transaction ..... 28 +- Annex A (informative): Signalling flows..... 29** + - A.1 Scope of signalling flows..... 29 + - A.2 Introduction..... 29 + - A.3 Media bypassing all IMS-ALGs ..... 30 + - A.3.1 General ..... 30 + - A.3.2 Message flow..... 30 + - A.4 IMS-ALG allocates a local transcoding MR when performing proactive transcoding without resource reservation ..... 42 + - A.4.1 General ..... 42 + - A.4.2 Message flow..... 42 + - A.5 IMS-ALG bypasses an allocated transcoding MR..... 62 + - A.5.1 General ..... 62 + - A.5.2 Message flow..... 62 + - A.6 Loopback routeing via an intermediate network..... 75 + - A.6.1 General ..... 75 + - A.6.2 Message flow..... 76 +- Annex B (informative): Change history..... 90** + +# --- 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 optional Optimal Media Routeing (OMR) procedures that can be applied by entities in the IP Multimedia Subsystem (IMS) that control media resources and are capable of manipulating the Session Description Protocol (SDP) as defined by IETF RFC 4566 [6]. + +The OMR procedures in the present specification relate to the handling of OMR-specific SDP attributes that are documented in TS 24.229 [4]. The OMR procedures use SDP offer/answer related procedures in IETF RFC 3264 [5] and in 3GPP TS 24.229 [4] in a backward-compatible manner. + +The 3GPP network architecture, including the configuration and network entities of the IMS, is defined in 3GPP TS 23.002 [2]. The Stage 2 of the IMS is defined 3GPP TS 23.228 [3]. Annex Q of 3GPP TS 23.228 [3] documents the architecture and call flows for OMR. + +The OMR procedures in this document are applicable to the following IMS entities that perform as an IMS-ALG or UA according to 3GPP TS 24.229 [4] and that control media resources: + +- an IBCF acting as an IMS-ALG; +- a P-CSCF acting as IMS-ALG; +- an AS acting as B2BUA and adapting IMS-ALG procedures to control an MRF; +- an AS acting as B2BUA and adapting UA procedures to control an MRF; and +- an MGCF acting as UA. + +NOTE 1: An AS acting as B2BUA to perform application functions such as conferencing or announcements will normally perform separate originating and terminating UA procedures, treating the media resource as an endpoint. An AS acting as B2BUA offering transcoding options will typically follow IMS-ALG procedures. + +NOTE 2: The controlled media resource can be a TrGW, IMS-AGW, MRF, or a media function of the entity performing OMR. + +The OMR procedures are not applicable for an UE. + +# --- 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.002: "Network architecture". +- [3] 3GPP TS 23.228: "IP multimedia subsystem; Stage 2". +- [4] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3". +- [5] IETF RFC 3264: "An Offer/Answer Model with Session Description Protocol (SDP)". +- [6] IETF RFC 4566: "SDP: Session Description Protocol". + +- [7] IETF RFC 2617: "HTTP Authentication: Basic and Digest Access Authentication". +- [8] IETF RFC 3605: "Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)". +- [9] 3GPP TS 29.238: "Interconnection Border Control Functions (IBCF) – Transition Gateway (TrGW) interface, Ix Interface; Stage 3". +- [10] 3GPP TS 29.334: "IMS Application Level Gateway (IMS-ALG) – IMS Access Gateway (IMS-AGW); Iq Interface; Stage 3". +- [11] IETF RFC 4240: "Basic Network Media Services with SIP". +- [12] IETF RFC 3260: "Media Control Channel Framework". +- [13] IETF RFC 6505: "A Mixer Control Package for the media Control Channel Framework". +- [14] 3GPP TS 29.332: "Media Gateway Control Function (MGCF) – IM Media Gateway Mn Interface". +- [15] 3GPP TS 23.334: "IP Multimedia Subsystem (IMS) Application Level Gateway (IMS-ALG) – IMS Access Gateway (IMS-AGW) interface: Procedures descriptions". +- [16] 3GPP TS 29.162: "Interworking between the IM CN subsystem and IP networks". +- [17] 3GPP TS 29.163: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks". +- [18] IETF RFC 5552: "SIP Interface to VoiceXML Media Services". +- [19] IETF RFC 4117: "Transcoding Services Invocation in the Session Initiation Protocol (SIP) Using Third Party Call Control (3pcc)". +- [20] IETF RFC 5939: "Session Description Protocol (SDP) Capability Negotiation". +- [21] IETF RFC 2234: "Augmented BNF for Syntax Specification: ABNF". +- [22] IETF RFC 7549: 3GPP SIP URI Inter Operator Traffic Leg parameter". + +# --- 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]. + +**Codec:** A media configuration for a media line in SDP that is specified by one or more formats in the format list of the m-line, by one or more preferred configurations (pcfg) associated with the media line, or by a combination of both. + +**Codec Change:** Any modification to the media configurations for the media line in the format list or the list of preferred configurations. + +**Codec List:** Either the format list of the m-line, or a combination of all the preferred configurations and the format list for the media line. + +**Connected IP realm:** Compared to a reference IP realm, a connected IP realm is one identified with a different unique name where all IP endpoints in the two IP realms are mutually reachable (accessible) by means of IP routing without address translation. Interconnection between the IP realms may be via direct link, via IP tunnel through other networks, via IP routing through intermediate networks, or via any other method of internetworking as long as their IP endpoints are mutually reachable. The property of connectedness is symmetric but not necessarily transitive. In particular, two IP realms connected to a reference IP realm are not necessarily themselves connected. + +**Incoming termination:** The termination at an MR in the direction from where an incoming SDP offer is being received at the IMS-ALG that is controlling the MR. + +**IP realm:** A collection of IP endpoints identified by a unique name, where all IP endpoints are mutually reachable by means of IP routing without address translation. + +**Media resource:** An IMS Network entity that provides resources to process media streams and is controlled by an entity applying OMR procedures. A TrGW, BGW, MRF, or a function internal to the entity performing OMR can be a media resource. + +**Loopback routing:** A method of routing a SIP request back to the visited network for local breakout according to the Roaming Architecture for Voice over IMS with Local Breakout as specified in TS 24.229 [4]. + +**Outgoing termination:** The termination at an MR in the direction towards where an outgoing SDP offer is being sent at the IMS-ALG that is controlling the MR. + +**Second SDP offer/answer:** An SDP offer/answer transaction initiated by any of the involved IMS-ALGs during session establishment towards the initial SDP answerer upon reception of the initial SDP answer and MR resources are required (e.g. when an intermediate IMS-ALG performs proactive transcoding without resource reservation) or not required (e.g. when MR resources are reserved for the purpose of transcoding and transcoding is not required). The second SDP offer is not an end-to-end negotiation and is handled as the initial SDP offer. + +**Subsequent SDP offer/answer:** An end-to-end SDP offer/answer transaction initiated after a completed initial or second SDP offer/answer transaction. The subsequent SDP offer contains no OMR specific attributes. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----|---------------------------------------------------------------| +| Ix | Reference Point between IBCF and TrGW | +| Iq | Reference Point between the P-CSCF and the IMS Access Gateway | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1], in TS 23.228 [3] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1] or in TS 23.228 [3]. + +| | | +|-------|----------------------------------------| +| ALG | Application Level Gateway | +| B2BUA | Back-to-Back User Agent | +| IC | Interconnection | +| ICE | Interactive Connectivity Establishment | +| MR | Media Resource | +| OMR | Optimal Media Routing | +| TRF | Transit and Roaming Function | +| UA | User Agent | + +# 4 General + +The procedures in clause 5, clause 6, clause 7 and clause 8 shall apply separately to each media line with non-zero port value in each SDP message, and shall apply separately to each SDP offer/answer transaction. In the presence of forking of a SIP INVITE request that includes an SDP offer, the OMR procedures for handling of the SDP offer apply once for all forked dialogs, and the OMR procedures for handling of the corresponding SDP answer apply independently to each dialog. Entities supporting OMR use the OMR-specific SDP extension attributes defined in TS 24.229 [4]. + +OMR builds on the ALG NAT traversal model and is not consistent with ICE. + +OMR does not modify the SIP signalling route path and usually does not modify the flow of SIP messages except in some cases when transcoding options are offered. + +# 5 Common SDP Procedures + +## 5.1 General + +The IMS-ALG or UA using the OMR procedures in clause 6 or clause 7, respectively, shall additionally use the procedures in this clause when manipulating SDP. + +## 5.2 Encapsulation of previous SDP information + +### 5.2.1 Media level information + +If an IMS-ALG forwards an SDP offer and for a given media line: + +- adds or removes offered format(s); +- modifies the transport protocol; +- adds or removes other corresponding media level SDP attribute(s) than "visited-realm", "secondary-realm", "omr-codecs", "omr-m-att", "omr-s-att", "omr-m-bw", "omr-s-bw", "omr-s-cksum" or "omr-m-cksum" attributes; +- modifies the value of other corresponding media level SDP attribute(s) than "visited-realm", "secondary-realm", "omr-codecs", "omr-m-att", "omr-s-att", "omr-m-bw", "omr-s-bw", "omr-s-cksum" or "omr-m-cksum" attributes; +- adds or removes corresponding media level SDP bandwidth line(s); or +- modifies the value of corresponding media level SDP bandwidth line(s), + +then the IMS-ALG shall apply the procedures below to encapsulate all media level information of the corresponding media line. + +The IMS ALG shall encapsulate the received transport protocol and format list of the corresponding media line within an "omr-codecs" attribute and add this attribute as a media level attribute for the corresponding media line. + +The IMS ALG shall encapsulate each received attribute of the corresponding media line within an "omr-m-att" attribute and add this attribute as a media level attribute for the corresponding media line. + +The IMS ALG shall encapsulate each received bandwidth line of the corresponding media line within an "omr-m-bw" attribute and add this attribute as media level attribute for the corresponding media line. + +If the IMS-ALG received any visited-realm instances in the SDP offer, the IMS-ALG shall supply the instance number one above the highest instance number in the received SDP offer as instance number within the "omr-codecs", the "omr-m-att" and "omr-m-bw" attribute(s). Otherwise the IMS-ALG shall supply the instance number 2. + +### 5.2.2 Session level information + +If an IMS-ALG forwards an SDP offer and: + +- encapsulated any media level information according to the conditions in clause 5.2.1; +- adds or removes any session level SDP attribute(s); +- modifies the value of any session level SDP attribute(s); +- adds or removes session level SDP bandwidth line(s); or +- modifies the value of session level SDP bandwidth line(s), + +then the IMS-ALG shall apply the procedures below to encapsulate all session level information. + +The IMS ALG shall encapsulate each received session-level attribute within an "omr-s-att" attribute and add this attribute as a media level attribute for every media line. + +The IMS ALG shall encapsulate each received session-level bandwidth line within an "omr-s-bw" attribute and add this attribute as a media level attribute for every media line. + +If the IMS-ALG received any visited-realm instances in the SDP offer, the IMS-ALG shall supply the instance number one above the highest instance number in the received SDP offer as instance number within the "omr-s-att" and "omr-s-bw" attribute(s). Otherwise the IMS-ALG shall supply the instance number 2. + +NOTE 1: The instance number 1 is reserved for the incoming SDP offer when it contains no visited-realm instance. + +NOTE 2: The remaining SDP session level attributes (e.g., the "o" line) are not modified by the OMR procedures. + +## 5.3 Determination of codec related SDP information associated to a previous realm instance + +When deciding to bypass some previous MR, an IMS-ALG needs to determine the SDP information which is applicable together with the visited-realm instance or secondary-realm instance that the IMS selects for the bypass (see clause 6.1). The IMS-ALG will include that SDP information in a forwarded SDP offer or perform additional modifications on top of it, e.g., to offer transcoding at its own MR. + +To determine the codec related SDP information associated to that previous realm instance for the media line, the IMS-ALG shall use the procedures below. + +1) If any "omr-codecs", "omr-m-att", or "omr-m-bw" attributes with a higher instance number than the previous visited-realm instance or secondary-realm instance exist for a media line, the IMS-ALG shall consider the information within the set of attributes with the lowest instance number among those as follows: + +- the IMS-ALG shall replace the transport format and media formats in the media line with the transport format and media formats from the "omr-codecs" attribute with this instance number; +- the IMS-ALG shall retain all the "visited-realm", "secondary-realm", "omr-s-cksum", "omr-m-cksum", "omr-codecs", "omr-m-att", "omr-s-att", "omr-m-bw" and "omr-s-bw" attributes for the media line and replace all other SDP a-line(s) for the media line with the attributes extracted from the "omr-m-att" attribute(s) with this instance number; and + +NOTE 1: This procedure only describes update to codec related SDP information. Clauses 6 and 7 describe the corresponding modifications to the OMR related attributes. + +- the IMS-ALG shall replace the SDP b-line(s) for the media line with the b-line(s) extracted from the "omr-m-bw" attributes with this instance number. + +Otherwise, the IMS-ALG shall use the SDP a-lines, b-lines, transport format and list of media formats of the corresponding media line. + +2) If any "omr-s-att" or "omr-s-bw" attributes with a higher instance number than the previous visited-realm instance or secondary-realm instance exist, the IMS-ALG shall consider the information within the set of attributes with the lowest instance number among those as follows: + +- If the same attributes are provided for each media line, the IMS ALG shall replace all session-level SDP a-lines and b-lines with the encapsulated attributes and bandwidth within the "omr-s-att" attributes and "omr-s-bw" attributes of one media line as session level attributes and bandwidth, and may apply attribute or bandwidth modifier specific logic to verify and possibly adjust the session-level information from "omr-s-att" and "omr-s-bw" attributes and media level information determined as described above; + +NOTE 2: Verification helps in the possible event of splitting media lines by intermediate entities. + +- otherwise the IMS-ALG shall apply attribute or bandwidth modifier specific logic to derive appropriate session-level information from "omr-s-att" and "omr-s-bw" attributes and media level information determined as described above, or delete all those encapsulated attributes and all session-level SDP a-lines and b-lines. + +NOTE 3: In the possible event of merging of media lines by intermediate entities, there may be inconsistencies in the encapsulated session level a-lines and/or b-lines. + +3) Otherwise, the IMS-ALG shall use the session-level SDP a-lines and b-lines. + +For an SDP offer with several media lines, an IMS-ALG applies the OMR algorithm separately for each media line and can select different optimised paths. In such a case, the session-level attributes and bandwidth information determined + +by the above algorithm can differ for different optimised paths, depending on the selected visited-realm instance or secondary-realm instance for each media line. The IMS-ALG may then apply attribute or bandwidth modifier specific logic to determine the appropriate session-level information or discard conflicting information. An IMS-ALG may also apply a policy not to choose different optimised paths for different media to avoid such conflicts. + +NOTE 4: Upon receiving an SDP offer and validating the OMR attributes in the SDP offer, but before making any codec changes to the SDP offer, the IMS-ALG supporting OMR can delete any unsupported attributes from the SDP offer, e.g., attributes associated with capability negotiation. The IMS-ALG supporting OMR can also delete any ignored attributes, e.g., due to lack of support of a required extension to capability negotiation, as determined by the *creq* attribute defined in IETF RFC 5939 [20]. + +## 5.4 Modifying codec related information + +### 5.4.1 Modifying the format list + +When forwarding an SDP offer, the IMS-ALG should not make changes to the attributes associated with a format remaining in the format list of the m-line that require the allocation of an MR to translate the media payload between the format described by the received SDP offer and the format described by the forwarded SDP offer. + +NOTE 1: Examples include changing between AMR octet-aligned and bandwidth-efficient modes, and incompatible AMR mode-sets. + +To add a codec to the format list of the m-line in the SDP offer to be forwarded, the IMS-ALG shall either: + +- add a media format to the format list on the media line that is different from any format in the "omr-codecs" attributes for the media line, along with any necessary media attributes, or +- re-insert a format from an "omr-codecs" attribute for the media line that is not in the current format list, along with the corresponding attributes for the format with the same instance number in "omr-m-att" attributes. + +NOTE 2: This procedure avoids the potential need to retain a media resource to perform format mapping when performing proactive transcoding, if the bypass decision is based on the SDP answer. + +### 5.4.2 Modifying preferred configurations + +When forwarding an SDP offer, the IMS-ALG supporting SDP capability negotiation shall only make a change to a preferred configuration in the incoming SDP offer without changing the configuration number if the change is backward compatible. A backward compatible change is one that, if it is selected as the actual configuration, does not require the allocation of an MR to translate the media payload between the format described by the received SDP offer and the format described by the forwarded SDP offer, and does not require modification of the actual configuration number when forwarding the SDP answer. This applies to the preferred configuration (*pcfg*) itself and any capabilities referenced in the *pcfg*. + +NOTE 1: It is recommended that an IMS-ALG not make any codec list changes to an SDP offer that includes any mandatory session capabilities unless it also deletes all attributes associated with capability negotiation as if capability negotiation were not supported. + +To make any of the following changes to a preferred configuration in the SDP offer: + +- to change the priority of the preferred configuration with respect to others; +- to allow insertion of a new preferred configurations with higher priority; +- to allow reassignment of another preferred configuration to a higher priority; or +- to make any other changes to a preferred configuration that are not backward compatible and cannot be realized by inserting a new preferred configuration, + +the IMS-ALG shall reassign the configuration number to one unused in the SDP offer or in any of the encapsulated information for the media line in the SDP offer and add any necessary capability attributes. + +NOTE 2: Changing the priority of a codec or preferred configuration increases the possibility of introducing a transcoding function that is not otherwise needed. Normally new or changed preferred configurations are assigned with higher configuration numbers (of lower priority) than existing preferred configurations. + +When forwarding an SDP offer, the IMS-ALG supporting SDP capability negotiation shall not change any existing SDP capneg capability attributes, but may insert additional capability attributes. + +The IMS-ALG may delete a preferred configuration from the SDP offer. However, the IMS-ALG shall not delete any unreferenced capability attributes. + +If the IMS-ALG desires to add a preferred configuration, it should search for an equivalent or backward compatible preferred configuration within the encapsulated codec related information. If it finds such a suitable preferred configuration, the IMS-ALG should reuse the configuration number from the encapsulated preferred configuration if the resulting priority with respect to other preferred configurations is acceptable. + +To add a new preferred configuration to the media line of the SDP offer that is different from and not backward compatible with any pcfg attribute in encapsulated codec information for the media line, the IMS-ALG shall allocate a new configuration number for the new preferred configuration with a configuration number unused by any other preferred configuration within the SDP offer or within the encapsulated codec related information. + +## 5.5 Additional handling for SDP answer with actual configuration + +In clause 6.2.2 and clause 6.2.8 step 4), if the media line in the initial or second SDP answer includes an actual configuration, the IMS-ALG should perform the following procedure to determine if the codecs in the initial or second SDP answer are supported by a previous version of the received initial or second SDP offer: + +The IMS-ALG should compare the actual configuration with SDP capneg preferred configurations in encapsulated codec related information to determine if previous realm instances are associated with matching codec related information. The actual configuration matches a preferred configuration: + +- if the preferred configuration has the same configuration number as the actual configuration; or +- if the capabilities listed in the actual configuration match the capabilities available in the preferred configuration in the initial or second SDP offer. + +NOTE: An IMS-ALG can choose not to compare the SDP capneg actual configuration with encapsulated preferred configurations, or only to compare configuration numbers, but this may lead to a failure to find opportunities to bypass previous realm instances. However, SDP capneg procedures recommend that the offerer performs a second offer/answer transaction where the actual configuration is offered in normal SDP. Missed opportunities to bypass previous realm instances could still be found during this second offer/answer transaction. + +If the IMS-ALG selected a preferred configuration with a different configuration number than the actual configuration for bypassing a previous realm, the IMS-ALG shall change the capability number of the actual configuration to equal the capability number of the matching preferred configuration before forwarding the initial or second SDP answer. + +## 5.6 Procedures specific to OMR attributes + +### 5.6.1 General + +This clause describes additional procedures specific to SDP attributes associated with OMR specified in TS 24.229 [4], clause 7.5.3. + +### 5.6.2 instance-number + +When creating a new visited-realm instance for a media line in an SDP offer, the IMS-ALG shall assign an instance-number value for the instance that is "1" higher than the highest existing instance-number value for any visited-realm attribute for any media line in the received SDP offer, starting with the value "1" if there are no such attributes in the SDP offer. If the IMS-ALG adds visited-realm instances for several media lines, the IMS-ALG shall use the same instance-number. If the IMS-ALG adds a "secondary-realm" SDP attribute for a media line in the SDP offer the IMS-ALG shall assign the same instance-number value as assigned to the "visited-realm" SDP attribute. + +A UA creating a visited-realm instance for a media line in an SDP offer shall assign an instance-number value "1" for the instance. If the UA adds a "secondary-realm" SDP attribute for a media line in the SDP offer the UA shall assign the instance-number value "1" for a secondary-realm instance. + +### 5.6.3 Session and media checksum calculation + +An IMS ALG or a UA supporting OMR shall determine a session level checksum and a media level checksum for each media line containing a "visited-realm" SDP attribute or a "secondary-realm" SDP attribute in an SDP offer. + +NOTE: A session level checksum and a media level checksum calculation is not performed for an SDP answer containing media line with a "visited-realm" SDP attribute or a "secondary-realm" SDP attribute. + +The session level checksum shall be calculated by summing all the hex values of the individual ASCII characters (excluding all white space) of the "b" and "a" session level lines. The media level checksum shall be calculated by summing all the hex values of the individual ASCII characters (excluding all white space) of the "m", "b", and "a" media level lines including attributes specific to OMR but excluding the session and media level checksum attribute lines themselves. + +When there are no "b" or "a" session level lines to calculate the session level checksum, the session level checksum is set to "0". + +## 5.7 Roaming architecture for voice over IMS with local breakout + +In a network supporting the roaming architecture for voice over IMS with local breakout OMR related policies may depend on the identification of a roaming architecture for voice over IMS with local breakout session. + +An IBCF acting as an IMS-ALG can identify a session to be a roaming architecture for voice over IMS with local breakout session as specified in TS 24.229 [4], clause 5.10.9. + +## 5.8 II-NNI traversal scenario + +OMR related policies can depend on the II-NNI traversal scenario type. + +An IBCF acting as an IMS-ALG can identify the II-NNI traversal scenario type as specified in TS 24.229 [4]. + +# --- 6 IMS-ALG procedures + +## 6.1 IMS-ALG handling of initial SDP offer + +### 6.1.1 General + +Upon receiving an initial SDP offer, the IMS-ALG supporting OMR shall apply the procedures in the following clauses for each media line with non-zero port value. + +Upon receiving a second SDP offer that includes OMR attributes for some media lines, the IMS-ALG supporting OMR shall apply the procedures in the following clauses for each media line with non-zero port value and OMR attributes. + +NOTE: An example of a second SDP offer/answer transaction is when any of the IMS-ALGs performs proactive transcoding without resource reservation or removes media resources when transcoding is no longer required. See clauses 6.2.2 and 6.2.3. + +After the completion of an initial SDP offer/answer transaction and when receiving an SDP offer without OMR attributes for a media line, the IMS-ALG supporting OMR shall apply the procedures for subsequent SDP offer/answer transaction in clause 8 for that media line. + +### 6.1.2 Validating the received SDP offer + +If any of the following conditions are true: + +- 1) the received SDP offer includes any OMR attributes for the media line, but no visited-realm instance; +- 2) the connection-address and port information in the visited-realm instance with the highest value of instance-number for the media line does not match the connection address and port information for the media line; or +- 3) one of the following conditions are true: + +- the "omr-m-cksum" attribute does not match the checksum value computed for the media line as described in clause 5.6.3; or +- based on local policy, if the "omr-m-cksum" attribute matches the computed media line checksum, but the "omr-s-cksum" attribute does not match the checksum value computed for the session level lines as described in clause 5.6.3, + +then the IMS-ALG shall remove all OMR attributes associated with the media line from the received SDP offer and use the modified SDP offer as the received SDP offer in the procedures in the following clauses. + +### 6.1.3 Deciding whether to allocate a primary local MR and if any previous MR can be bypassed + +The IMS-ALG considers information in the received SDP offer and applies local policy to decide whether to allocate a primary local MR and if it is to bypass any previous MRs. + +**NOTE:** An IMS-ALG can revise these decisions when receiving the SDP answer, applying procedures in clause 6.2. + +The IMS-ALG shall perform the following steps: + +- 0) If the connection address for the media line in the received SDP offer is the unspecified address, then the IMS-ALG should: + - a) select to not allocate a primary local MR (regardless of local policy), and to not bypass any previous MRs; + - b) convert the unspecified address in the connection address for the media line in the received SDP offer to the addrtype of the outgoing IP realm, if necessary; + - c) if subsequently choosing to perform proactive transcoding in clause 6.1.7, then select to perform proactive transcoding without resource reservation (regardless of local policy); + - d) select to not add secondary-realm instances to the modified SDP offer when performing the procedure in clause 6.1.8 (regardless of local policy); and + - e) skip to step 6), +- 1) If all of the following conditions apply: + - a) local policy does not require the allocation of an MR for any non-OMR related reason (e.g. for hosted NAPT traversal on the incoming signalling path, or for legal interception; and + - b) the IP realm, nettype and addrtype for the outgoing signalling path is the same as the IP realm, nettype and addrtype associated with a visited-realm or secondary-realm instance for the media line + - such that the instance has an instance-number value $i$ that is less than the highest instance-number value $n$ associated with the media line in the received SDP offer; and + - such that the instance $i$ is associated with a codec list, determined using the procedures in clause 5.3, which includes all codecs required by local policy, unless the IMS-ALG has a policy to offer the missing codecs proactively without reserving an MR, + +then the IMS-ALG shall store an indication that the allocation of a primary local MR is not required and shall store the realm instances with instance-number greater than $i$ , which are associated with MRs that can be bypassed without allocating a primary local MR. + +- 2) If the following condition applies: + - a) the IMS-ALG controls an MR with access to an IP realm or connected IP realm, nettype and addrtype associated with a visited-realm or secondary-realm instance for the media line + - such that the instance has an instance-number value $j$ that is less than the highest instance-number value $n$ associated with the media line in the received SDP offer; and + +- such that the instance $j$ is associated with a codec list, determined using the procedures in clause 5.3, which includes all codecs required by local policy, unless such codecs are provided at a local MR via transcoding, + +then the IMS-ALG shall store the realm instances with instance-number greater than $j$ , which are associated with MRs that can be bypassed when allocating a primary local MR. + +3) If all of the following conditions apply: + +- the condition in step 1) does not apply; +- the IP realm, nettype and addrtype for the outgoing signalling path is the same as the IP realm, nettype and addrtype for the incoming signalling path; +- the codec list in the received SDP offer, determined from the SDP m-line and associated non-OMR attribute lines, includes all codecs required by local policy, unless the IMS-ALG has a policy to offer the missing codecs proactively without reserving an MR; and +- local policy does not require the allocation of an MR for any non-OMR related reason (e.g. for hosted NAPT traversal on the incoming signalling path, or for legal interception), + +then the IMS-ALG shall store an indication that the allocation of a primary local MR is not required and that no MRs can be bypassed when no primary local MR is allocated. + +4) If an indication that the allocation of a primary local MR is not required has been stored in steps 1) or 3), + +- then the IMS-ALG shall compare the realm instances (and MRs) that can be bypassed with or without allocation of a primary local MR, as determined in steps 1), 2) and 3), and shall use local policy to select whether to allocate a primary local MR, +- else the IMS-ALG shall select to allocate a primary local MR, + +NOTE: Usually the decision is made based on which choice retains the smallest total number of MRs in the media path, but local policy may apply other criteria. + +5) If the IMS-ALG selected in step 4) to allocate a primary local MR, then the IMS-ALG shall: + +- if one or more realm instances can be bypassed when allocating a primary local MR, then store instance-number value $k=j$ and apply the procedures in clause 6.1.4 to bypass previous MRs, else apply the procedures in clause 6.1.5 to not bypass previous MRs; and +- apply the procedures in clause 6.1.6 to allocate a primary local MR. + +6) If the IMS-ALG selected in step 4) to not allocate a primary local MR, then the IMS-ALG shall: + +- if one or more realm instances can be bypassed when not allocating a primary local MR, then store instance-number value $k=i$ and apply the procedures in clause 6.1.4 to bypass previous MRs, else apply the procedures in clause 6.1.5 to not bypass previous MRs; and +- apply the procedures in clause 6.1.7 to not allocate a primary local MR. + +### 6.1.4 Bypassing previous MRs + +If the IMS-ALG decides (applying the criteria in clauses 6.1.3, 6.2.2, 6.2.3 or 6.2.8) to bypass a previous MR, the IMS-ALG shall: + +- 1) use the connection address and port information from the selected instance $k$ for the media line in the received SDP offer as incoming connection address and incoming port information for the media line in the subsequent steps; +- 2) reconstruct the associated codec information for the media line in the received SDP offer from the selected instance $k$ as described in clause 5.3, and use that codec information as incoming codec information in the subsequent steps; and +- 3) delete every OMR attribute for the media line with instance-number value higher than $k$ . + +### 6.1.5 Bypassing no previous MRs + +If the IMS-ALG decides (applying the criteria in clauses 6.1.3, 6.2.2 or 6.2.3) not to bypass any previous MR, the IMS-ALG shall: + +- 1) use the connection-address from the SDP c-line in the received SDP offer as incoming connection-address in subsequent steps; +- 2) use the port information from the SDP m-line in the received SDP offer as incoming port information in subsequent steps; and +- 3) use the codec information from the SDP m-line and associated non-OMR attribute lines in the received SDP offer as incoming codec information in the subsequent steps. + +### 6.1.6 Allocating a primary local MR + +If the IMS-ALG decides (applying the criteria in clauses 6.1.3 or 6.2.3) to allocate a local MR, the IMS-ALG shall: + +- 1) if no MR context has been allocated due to a previous SDP offer-answer exchange, allocate an MR context with access to the IP realms, nettypes and addrtypes associated with the incoming connection address and port information determined in clause 6.1.4 or 6.1.5, and the outgoing signalling path, respectively applying procedures as described in clause 6.3; +- 2) if the IMS-ALG is not performing hosted NAPT traversal on the incoming side, then insert the incoming connection address and incoming port information for the media line, as determined in clause 6.1.4 or 6.1.5, into the remote connection address and port information for the incoming termination on the MR; +- 3) if the IMS-ALG is performing hosted NAPT traversal on the incoming side, then discover the remote connection address and port information for the incoming termination on the MR using latching or other unspecified technique; +- 4) if codec information is to be provided to the allocated MR on the incoming termination, provide to the MR the incoming codec information as determined in clause 6.1.4 or 6.1.5; + +NOTE: The IMS-ALG can defer the allocation of an MR termination at the incoming side and the related procedures in steps 1) to 4) until it processes the SDP answer. + +- 5) if the IMS-ALG requires according to local policy that its MR remain in the media path for reasons unrelated to OMR, remove all OMR specific attributes from the modified SDP offer; +- 6) if there is no visited-realm instance associated with the connection address and port information for the media line in the received (and possibly modified) SDP offer, and there is no local policy prohibiting removal of the allocated MR, then construct and add this visited-realm instance to the modified SDP offer; +- 7) replace the connection address and port information for the media line in the modified SDP offer with the connection address and port information from the MR termination on the outgoing side; +- 8) make any codec changes to incoming codec information, as determined in clause 6.1.4 or 6.1.5, according to local policy, taking into account the procedures in clause 5.4, and insert the changed codec information into the SDP m-line and associated attribute lines of the modified SDP offer; +- 9) if codec information is to be provided to the allocated MR for the outgoing termination, provide to the MR the modified codec information derived in step 8); and +- 10) add to the modified SDP offer a visited-realm instance for the IP realm associated with the connection address and port information for the media line in the modified SDP offer, including the incoming codec information encoded according to clause 5.2 if any codec changes were inserted in step 8). + +### 6.1.7 Allocating no primary local MR + +If the IMS-ALG decides (applying the criteria in clauses 6.1.3 or 6.2.2) not to allocate a primary local MR, the IMS-ALG shall: + +- 1) decide according to local policy if the IMS-ALG performs any codec changes to the incoming codec information, as determined in clause 6.1.4 or 6.1.5, without allocating an MR (i.e., for proactive transcoding without resource reservation); + +NOTE: The IMS-ALG can only make codec changes if the available SIP signalling allows the IMS-ALG to initiate a 2nd SDP offer/answer transaction if necessary to allocate a transcoding MR after receipt of the SDP answer, as described in clause 6.2.3. + +- 2) if the IMS-ALG decided in step 1) to perform any codec changes, then + - a) if there is no visited-realm instance associated with the connection address and port information for the media line in the received SDP offer, then construct and add this visited-realm instance; + - b) make the codec changes to incoming codec information according to local policy, taking into account the procedures in clause 5.4, and insert the changed codec information into the SDP m-line and associated attribute lines of the modified SDP offer; and + - c) add to the modified SDP offer a visited-realm instance with the same IP realm, connection address and port information as the previous visited-realm instance (after a possible execution of step 3 in clause 6.1.4 for the media line, including the incoming codec information encoded according to clause 5.2), +- 3) if the IMS-ALG decided in step 1) not to perform any codec changes, then + - a) insert the incoming codec information, determined in clause 6.1.4 or 6.1.5 into the SDP m-line and associated attribute lines of the modified SDP offer. +- 4) use the incoming connection address, determined in clause 6.1.4 or 6.1.5, as the connection address in the SDP c-line of the modified SDP offer; and +- 5) use the incoming port information as determined in previous steps as port information in the SDP m-line of the modified SDP offer. + +### 6.1.8 Allocating secondary local MRs + +According to local policy, the IMS-ALG may allocate a secondary MR for each combination of IP realm, nettype and addrtype on the outgoing side for which the IMS-ALG can allocate an MR context. However, if the IMS-ALG does not require a local MR for non-OMR reasons, the IMS ALG should only allocate a secondary MR for a combination of IP realm, nettype and addrtype if the IP realm, nettype and addrtype are not represented by a visited-realm or secondary-realm instance for the media line in the SDP offer. To allocate a secondary MR, the IMS-ALG shall: + +- 1) if no MR context has been allocated due to a previous SDP offer-answer exchange, allocate an MR context for the IP realm, nettype and addrtype on the outgoing side, using the incoming connection address and incoming port information for the media line, determined in clause 6.1.4 or 6.1.5, as the remote connection address and port information for the incoming termination; + - 2) if codec information is to be provided to the allocated MR for the incoming termination, provide to the MR the incoming codec information, as determined in clause 6.1.4 or 6.1.5; +- NOTE: The IMS-ALG can defer the allocation of an MR termination at the incoming side and the related procedures in steps 1) and 2) until it processes the SDP answer. +- 3) if any codec information is to be provided to the allocated MR for the outgoing termination, provide to the MR the codec information from the SDP m-line and associated attribute lines of the modified SDP offer; + - 4) if the IMS-ALG did not yet add a visited-realm instance for the outgoing side (the IMS-ALG did not allocate a primary MR and did not perform any codec changes, see clause 6.1.7); then + - a) if there is no visited-realm instance associated with the connection address and port information for the media line in the received SDP offer, then construct and add this visited-realm instance; and + - b) add to the SDP offer a visited-realm instance with the same IP realm, connection address and port information as the previous visited-realm instance (after a possible execution of step 3 in clause 6.1.4 for the media line), + - 5) add to the modified SDP offer a secondary-realm instance for the context allocated in step 1). + +### 6.1.9 Forwarding SDP offer + +The IMS-ALG shall: + +- 1) if local policy forbids sending of OMR related attributes to the outgoing IP realm, the IMS-ALG shall delete all OMR related attributes from the modified SDP offer; and +- 2) if the IMS-ALG has made any modifications to the received SDP offer before forwarding and the modified SDP offer includes OMR related attributes, the IMS-ALG shall compute checksum values as described in clause 5.6.3 and replace or add the "omr-s-cksum" and "omr-m-cksum" attributes for the media line. + +The IMS-ALG forwards the SDP offer according to TS 24.229 [4]. + +## 6.2 IMS-ALG handling of initial SDP answer + +### 6.2.1 General + +Upon receiving the initial or second SDP answer corresponding to the initial or second SDP offer sent in clause 6.1, the IMS-ALG supporting OMR shall perform the procedures in the following clauses for each media line in the initial or second SDP answer. + +### 6.2.2 IMS-ALG bypasses an allocated transcoding MR + +The IMS-ALG uses the following conditions to determine that a previously allocated primary local MR or upstream MR is to be bypassed and that a second SDP offer/answer transaction is needed to update the connection information on the outgoing side. Two examples of this procedure are given in Annex Q of TS 23.228 [3]: steps 5) and 6) of Figure Q.5, and steps 7) and 8) of Figure Q.7. + +If the following conditions are true: + +- 1) the received initial SDP answer includes connection address information for the media line that is a valid IP address other than the unspecified address (i.e., IPv4: "0.0.0.0", IPv6: "invalid.invalid"); and +- 2) it is possible to immediately initiate a second SDP offer/answer transaction towards the initial SDP answerer with the available SIP signalling, + +then the IMS-ALG should re-evaluate the conditions in clause 6.1.3, steps 1) to 4), taking into account the information from the originally received initial SDP offer, as well as the codecs received in the initial SDP answer as additional information (using the procedure in clause 5.5 if the initial SDP answer includes an actual configuration), to select again whether to allocate a primary local MR and to recompute how many realm instances can be bypassed. The IMS-ALG should select to modify the previous decision if a higher number of realm instances can be bypassed. + +If the IMS-ALG selected in the previous step to modify the previous decision and + +- to not allocate a primary local MR that has previously been allocated; or +- to not allocate a primary local MR and to bypass other previous realm instances than decided when previously evaluating clause 6.1.3, + +then the IMS-ALG shall: + +- 1) apply the procedures in clause 6.1.4 to bypass previous MRs or the procedures in clause 6.1.5 to not bypass previous MRs (using information from the originally received initial SDP offer), depending on its corresponding decision; +- 2) apply the procedures in clause 6.1.7 to not allocate a primary local MR without making any codec changes; +- 3) after clauses 6.2.2 and 6.2.3 are completed as applicable for all media lines, apply the procedures in clause 6.1.9 for each media line to send a second SDP offer within available SIP signalling, initiating a new second SDP offer/answer transaction towards the initial SDP answerer; and +- 4) upon receipt of the second SDP answer, continue handling of the second SDP answer as if it were the initial SDP answer, and reference the most recent data associated with the forwarding of the (modified) second SDP offer (i.e., incoming SDP information, allocated MRs and modified second SDP offer) as if it occurred the first time. + +### 6.2.3 IMS-ALG allocates a local transcoding MR when performing proactive transcoding without resource reservation + +The IMS-ALG uses the procedures in this clause if it receives an initial SDP answer without a realm instance, performed proactive transcoding without resource reservation when forwarding the initial SDP offer, as in step 2) of clause 6.1.7, and then determines that it needs to allocate an MR for proactive transcoding. + +If all the following conditions are true: + +- 1) the received initial SDP answer includes connection address information for the media line that is a valid IP address other than the unspecified address (i.e., IPv4: "0.0.0.0", IPv6: "invalid.invalid"); +- 2) the IMS-ALG performed proactive transcoding without resource reservation when previously forwarding the initial SDP offer, as in step 2) of clause 6.1.7; +- 3) the selected codec in the received initial SDP answer is not supported by the incoming media path and incoming codec information, as previously determined in clause 6.1.4 or 6.1.5 (using information from the originally received initial SDP offer), indicating that an MR must be allocated to provide transcoding; and +- 4) it is possible to immediately initiate a second SDP offer/answer transaction towards the SDP answerer with the available SIP signalling, + +NOTE: If a second SDP offer/answer transaction cannot be initiated with available SIP signalling, the OMR algorithm will fail to allocate a functioning end-to-end media path. + +then the IMS-ALG shall: + +- 1) if when previously handling the initial SDP offer it was determined in step 2) of clause 6.1.3 that one or more realm instances can be bypassed when allocating a primary local MR (using information from the originally received initial SDP offer), then store instance-number value $k=j$ and apply the procedures in clause 6.1.4 to bypass previous MRs, else apply the procedures in clause 6.1.5 to not bypass previous MRs (using information from the originally received initial SDP offer); +- 2) apply the procedures in clause 6.1.6 to allocate a primary local MR; +- 3) apply the procedures in clause 6.1.8 to update allocation of any secondary MRs, if necessary; +- 4) after clauses 6.2.2 and 6.2.3 are completed as applicable for all media lines, apply the procedures in clause 6.1.9 for each media line, to send a second SDP offer within available SIP signalling, and to initiate a new SDP offer/answer transaction towards the initial SDP answerer; and +- 5) upon receipt of the second SDP answer, continue handling of the second SDP answer as if it were the initial SDP answer, and reference the most recent data associated with the forwarding of the (modified) second SDP offer (i.e., incoming information, allocated MRs and modified second SDP offer) as if it occurred the first time. + +### 6.2.4 IMS-ALG determines steps required to complete the handling of the SDP answer + +The IMS-ALG performs the following steps to determine the disposition of any allocated MRs and to complete the handling of the SDP answer: + +- 1) if the received SDP answer for the media line includes a connection address with unspecified address and a visited-realm instance, then the IMS-ALG shall apply the procedures in clause 6.2.5; +- 2) if the received SDP answer for the media line includes a connection address with unspecified address and a secondary-realm instance, then the IMS-ALG shall apply the procedures in clause 6.2.6; +- 2a) If the received SDP answer for the media line includes a connection address with unspecified address and no visited-realm or secondary-realm instance, then the IMS-ALG shall: + - a) if necessary, update the unspecified connection address information in the SDP answer with the unspecified address of the appropriate type for the network into which the SDP answer will be sent (i.e., IPv4: "0.0.0.0", IPv6: "invalid.invalid"); + +- 3) if all the following conditions are true: + - a) the connection address for the media line in the received SDP answer is a valid (not unspecified) address; and + - b) the IMS-ALG did not allocate a primary local MR (i.e., executed clause 6.1.7) when forwarding the SDP offer,then the IMS-ALG shall apply the procedures in clause 6.2.7, and +- 4) if all the following conditions are true: + - a) the connection address for the media line in the received SDP answer is a valid (not unspecified) address; and + - b) the IMS-ALG allocated a primary local MR (i.e., executed clause 6.1.6) when forwarding the SDP offer,then the IMS-ALG shall apply the procedures in clause 6.2.8 to retain a primary local MR. + +### 6.2.5 Receiving an unspecified connection address and a visited-realm instance + +If the IMS-ALG receives a connection address with unspecified address and a visited-realm instance, then the IMS-ALG shall: + +- 1) If the visited-realm instance for the media line in the SDP answer has an instance-number that matches the visited-realm instance associated with the incoming SDP offer information, + +NOTE 1: The visited-realm instance associated with the incoming SDP offer information is either the one in the received SDP offer with highest instance-number (before any bypass decision is made), if one is present, or the one added in clause 6.1.6 step 6) or in clause 6.1.7 step 2a). + +NOTE 2: The IP realms in the two visited-realm instances either have the same name or are connected. + +then the IMS-ALG shall: + +- replace the connection address and port information for the media line in the SDP answer with the connection address and port information from the visited-realm instance in the received SDP answer, and + - retain the visited-realm instance in the SDP answer, +- 2) else the IMS-ALG shall: + - if necessary, update the unspecified connection address information in the SDP answer with the unspecified address of the appropriate type for the network into which the SDP answer will be sent (i.e., IPv4: "0.0.0.0", IPv6: "invalid.invalid"). + +### 6.2.6 Receiving an unspecified connection address and a secondary-realm instance + +If the IMS-ALG receives a connection address with unspecified address and a secondary-realm instance, then the IMS-ALG shall: + +- 1) if the secondary-realm instance for the media line in the SDP answer has an instance-number that matches a secondary-realm instance added by the IMS-ALG when applying procedures in clause 6.1.8 then the IMS-ALG shall apply the procedures in clause 6.2.8 to retain a secondary local MR, + +NOTE: The IP realms in the two secondary-realm instances either have the same name or are connected. + +- 2) else the IMS-ALG shall: + +- if necessary, update the unspecified connection address information in the SDP answer with the unspecified address of the appropriate type for the network into which the SDP answer will be sent (i.e., IPv4: "0.0.0.0", IPv6: "invalid.invalid"). + +### 6.2.7 Other handling when no primary local MR allocated + +If the IMS-ALG receives (as determined in clause 6.2.4) an SDP answer with a valid connection address after forwarding an SDP offer without allocating a primary local MR, then the IMS-ALG shall: + +- 1) If the IMS-ALG applied clause 6.1.4 to bypass previous MRs when handling the forwarding of the SDP offer, then the IMS-ALG shall: + - a) copy into the media line of the SDP answer the visited-realm or secondary-realm instance from the media line of the received SDP offer that was used to populate the connection address and port information in the forwarded SDP offer, replacing the connection-address and port information in the instance with the connection address and port information from the received SDP answer, and if the IP realm in the instance is a connected IP realm, replacing the IP realm name with the corresponding local IP realm name; and + - b) replace the connection address information in the SDP answer with the unspecified address of the appropriate type for the network into which the SDP answer will be sent (*i.e.*, IPv4: "0.0.0.0", IPv6: "invalid.invalid"), +- 2) else the IMS-ALG did not bypass previous MRs when forwarding the SDP offer and the IMS-ALG shall not modify the SDP answer. + +NOTE: In step 1) the received SDP answer never includes a realm instance. In step 2) the SDP answer can but does not necessarily include a realm instance. + +### 6.2.8 Retaining a primary or secondary local MR + +If the IMS-ALG decides (applying the criteria in clause 6.2.4 and clause 6.2.6) to retain a primary or secondary local MR, the IMS-ALG shall: + +- 1) if the IMS-ALG received an SDP answer with no secondary-realm instance for the media line, then the IMS-ALG shall: + + +NOTE: The IMS-ALG retains a primary local MR in this case. The IMS-ALG can but does not necessarily receive a visited-realm instance in an SDP answer when retaining a primary local MR. If present, the visited-realm instance can be used to identify the connected IP realm for the outgoing termination, if different from the IP realm of the outgoing termination. + + - a) update the remote connection address and port information for the outgoing termination on the selected primary local MR context with the connection address and port information for the media line in the received SDP answer, + - b) delete the visited-realm instance from the SDP answer, if present, +- 2) if the IMS-ALG received an SDP answer with a secondary-realm instance for the media line, then the IMS-ALG shall: + - a) update the remote connection address and port information for the outgoing termination on the selected secondary local MR context with the connection-address and port information from the secondary-realm instance in the received SDP answer; and + - b) delete the secondary-realm instance from the SDP answer, +- 3) if the selected codecs in the SDP answer are not in the set of codecs associated with the incoming SDP offer information, as determined in clause 6.1.4 or 6.1.5 when handling the SDP offer, then modify the SDP answer to include the codecs selected for the incoming termination of the selected local MR; +- 4) if the selected MR has access to an IP realm or connected IP realm, nettype and addrtype associated with a visited-realm or secondary-realm instance for the media line + - such that the instance has an instance-number value $k$ that is less than the highest instance-number value $n$ associated with the media line in the incoming SDP offer information, previously determined in clause 6.1.4 or 6.1.5; and + +- such that the instance $k$ is associated with a codec list, determined using the procedures in clause 5.3, which includes the codecs selected for the incoming termination of the selected local MR in step 3) (using the procedure in clause 5.5 if the SDP answer includes an actual configuration), + +then the IMS-ALG shall: + +- a) store the realm instances with instance-number greater than $k$ , which are associated with additional MRs that can be bypassed after selecting a codec for the incoming media path when allocating a primary local MR; + - b) apply the procedures in clause 6.1.4 to bypass additional previous MRs (using information from the originally received SDP offer); + - c) insert the incoming connection address and incoming port information for the media line, as determined in step b), as the remote connection address and port information for the selected IP realm on the incoming termination of the selected MR; + - d) if necessary, modify the selected codec information in the SDP answer to be a valid response to the incoming SDP offer codec information determined in step b); + - e) if codec information is to be provided to the allocated MR on the incoming termination, provide to the MR the incoming codec information as determined in step d); +- 5) If the IMS-ALG applied clause 6.1.4 to bypass previous MRs when forwarding the SDP offer or in step 4b), then the IMS-ALG shall: +- a) copy into the media line of the SDP answer the visited-realm or secondary-realm instance from the media line of the received SDP offer that was used for the remote connection address and port information for the incoming termination on the MR, replacing the connection-address and port information in the instance with the local connection address and port information for the incoming termination on the selected MR, and if the IP realm in the instance is a connected IP realm, replacing the IP realm name with the corresponding local IP realm name; and + - b) replace the connection address information in the SDP answer with the unspecified address of the appropriate type for the network into which the SDP answer will be sent (i.e., IPv4: "0.0.0.0", IPv6: "invalid.invalid"), +- 6) If the IMS-ALG applied clause 6.1.5 to not bypass previous MRs when forwarding the SDP offer, and did not bypass previous MRs in step 4b), then the IMS-ALG shall: +- a) replace the connection address and port information for the media line in the SDP answer with the local connection address and port information for the incoming termination on the selected MR. + +### 6.2.9 Forwarding the SDP answer + +The IMS-ALG forwards the SDP answer according to TS 24.229 [4]. + +The IMS-ALG shall release each MR for the media line, when it is no longer potentially needed for this and any other forked dialog. + +## 6.3 IMS-ALG OMR media resource operations + +### 6.3.1 General + +The IMS-ALG OMR procedures as specified by clauses 6.1 and 6.2 refer to generic MR allocation operation. When no MR was previously allocated, e.g. during the initial SDP offer/answer exchange, this allocation will result in the allocation of one or more local media termination point pairs (ingress and egress) – one for the primary IP realm and possible additional terminations points for secondary IP realms. + +Subsequent SDP offer/answer exchanges may result in the decision that a local MR is needed. If a local MR was not previously allocated, then one will now be allocated. If a local MR was previously allocated that matches the resource information needed, then the previously allocated resource will be used. If the previously allocated local MR does not match the resource information needed, then the local MR will be modified to meet the current need. + +If it is determined that local MR may be by-passed or no longer needed, then any previously allocated local MRs will be deallocated. + +### 6.3.2 IMS-ALG operations + +The OMR MR procedures in this document are applicable to the following IMS entities that perform as IMS-ALG using the media resource interface operations as indicated. + +- An IBCF acting as an IMS-ALG controlling a TrGW using the Ix interface as defined by TS 29.162 [16] and TS 29.238 [9]: + - Reserve TrGW Connection Point; + - Configure TrGW Connection Point, + - Reserve and Configure TrGW Connection Point; and + - Release TrGW Connection Point. +- A P-CSCF acting as IMS-ALG controlling an IMS-AGW using the Iq interface as defined by TS 23.334 [15] and TS 29.334 [10]: + - Reserve AGW Connection Point; + - Configure AGW Connection Point; + - Reserve and Configure AGW Connection Point; and + - Release AGW Connection Point. +- An AS acting as B2BUA and adapting IMS-ALG procedures to control an MRF shall use one or more of the following: + - IETF RFC 4240 [11] conference service; + - IETF RFC 4117 [19]; and + - IETF RFC 3260 [12] and IETF RFC 6505 [13]. + +## 6.4 Handling of connected IP realms + +For each IP realm to which a controlled MR has direct access, the IMS-ALG supporting OMR may be provisioned with a list of the names of connected IP realms, if any. The IMS-ALG shall determine if an IP realm is connected to a local IP realm based only on provisioning. + +NOTE 1: The OMR algorithm assumes that a first IMS-ALG or UA sending an SDP offer that offers connectivity via a local IP realm will accept from a second IMS-ALG or UA an SDP answer with an address in a connected IP realm, even if the first IMS-ALG or UA does not have provisioned information about the connected IP realm. + +NOTE 2: Connected IP realm lists only need to be provisioned at certain OMR-capable nodes. For example, it is preferred that an IBCF whose TrGW has connectivity to multiple peer networks via bilateral interconnect be provisioned with connected IP realm information. + +# --- 7 UA Procedures + +## 7.1 UA sending an initial SDP offer + +Upon preparing an initial SDP offer for sending to begin an initial SDP offer/answer transaction, a UA supporting OMR shall additionally: + +- 1) add to the initial SDP offer a visited-realm instance for the IP realm associated with the connection address and port information for the media line in the initial SDP offer; +- 2) for each combination of IP realm, nettype and addrtype on the outgoing side for which the UA can allocate an MR termination according to local policy, if the IP realm, nettype and addrtype are not associated with the media + +line in the initial SDP offer, allocate an MR termination for the IP realm, nettype and addrtype on the outgoing side, using the same codecs associated with the media line; + +- 3) add to the initial SDP offer a secondary-realm instance for each termination allocated in step 2); and +- 4) compute a checksum values as described in clause 5.6.3 and add the "omr-s-cksum" and "omr-m-cksum" attributes for the media line. + +The UA then sends the initial SDP offer according to TS 24.229 [4]. + +NOTE: A subsequent SDP offer is sent according to procedures in clause 8. + +## 7.2 UA receiving an initial SDP offer + +### 7.2.1 General + +Upon receiving an SDP offer that includes OMR attributes and selecting a codec for the media line, a UA supporting OMR shall perform the procedures specified in clauses 7.2.2 and 7.2.3, and then send the initial or second SDP answer according to TS 24.229 [4]. + +### 7.2.2 Validating the incoming SDP offer + +If any of the following conditions are true: + +- 1) the SDP offer includes any OMR attributes for the media line, but no visited-realm instance; +- 2) the connection-address and port information in the visited-realm instance with the highest value of instance-number for the media line does not match the connection address and port information for the media line; or +- 3) one of the following checksum comparison failures are true: + - the "omr-m-cksum" attribute does not match the checksum value computed for the media line as described in clause 5.6.3; or + - based on local policy, if the "omr-m-cksum" attribute matches the computed media line checksum, but the "omr-s-cksum" attribute does not match the checksum value computed for the session level lines as described in clause 5.6.3, + +then the UA shall remove all OMR related attributes associated with the media line. + +### 7.2.3 UA may choose an alternate realm instance to bypass an upstream MR + +If all the following conditions are true: + +- 1) the UA can make available a media termination in an IP realm, nettype and addrtype such that this IP realm or a connected IP realm, nettype and addrtype match the IP realm, nettype and addrtype of a visited-realm or secondary-realm instance for the media line in the SDP offer; +- 2) the instance does not match the connection address and port information in the SDP offer; and +- 3) the instance supports the codec selected by the UA, + +then the UA shall: + +- 1) select the visited-realm or secondary-realm instance with the lowest value of instance-number such that the UA can make available a media termination in the IP realm or connected IP realm, nettype and addrtype that matches the IP realm, nettype and addrtype of the instance and the instance supports the codec selected by the UA; +- 2) allocate a media termination in the selected IP realm, nettype and addrtype; +- 3) copy into the media line of the SDP answer the selected visited-realm or secondary-realm instance from the media line of the received SDP offer, replacing the connection-address and port information in the instance with the local connection address and port information for the allocated termination, and if the IP realm in the instance is a connected IP realm, replacing the IP realm name with the corresponding local IP realm name; and + +- 4) replace the connection address information in the SDP answer with the unspecified address of the appropriate type for the network into which the SDP answer will be sent (i.e., IPv4: "0.0.0.0", IPv6: "invalid.invalid"). + +## 7.3 UA receiving an initial SDP answer + +### 7.3.1 General + +Upon receiving the initial SDP answer corresponding to the initial SDP offer sent in clause 7.1, the UA supporting OMR shall perform the procedures specified in either clause 7.3.2 if the initial SDP answer included a realm instance or clause 7.3.3 if the initial SDP answer did not include a realm instance. + +### 7.3.2 Receiving SDP answer with an unspecified connection address + +If the received SDP answer for the media line includes an unspecified connection address (i.e., IPv4: "0.0.0.0", IPv6: "invalid.invalid") and a visited-realm or a secondary-realm instance with an instance-number that matches a visited-realm or secondary-realm instance for the media line from the SDP offer, then the UA shall: + +NOTE: The IP realms in the two realm instances either have the same name or are connected. + +- 1) update the remote connection address and port information for the selected outgoing termination with the connection-address and port information from the visited-realm or secondary-realm instance in the received SDP answer; and +- 2) release any other MR apart from the selected MR allocated for the media line, when it is no longer potentially needed for any other forked dialog. + +### 7.3.3 Receiving SDP answer with a valid connection address + +If the received SDP answer includes a valid (not unspecified) connection address for the media line, then the UA shall: + +- 1) update the remote connection address and port information for the primary outgoing termination with the connection address and port information from the received SDP answer; and +- 2) release any secondary MR allocated for the media line, when it is no longer potentially needed for any other forked dialog. + +## 7.4 UA OMR media resource operations + +### 7.4.1 General + +The UA OMR procedures as specified by clauses 7.1, 7.2, and 7.3 refer to generic MR allocation operation. This allocation will result in the allocation of a local media termination associated with the selected IP realm. + +Subsequent SDP offer/answer exchanges may result in either the exact same local MR being allocated or possibly a different local MR. If the UA is able to determine that the same resource information is being requested, the existing allocated local MR will be used. If the previously allocated local MR does not match the resource information needed, then the local MR will be modified to meet the current need. + +### 7.4.2 UA operations + +The OMR MR procedures in this document are applicable to the following IMS entities that perform as UA using the media resource interface operations as indicated. + +- An AS acting as B2BUA and adapting UA procedures to control an MRF shall use one or more of the following: + - IETF RFC 4240 [11] conference service and tone/announcement service; + - IETF RFC 5552 [18]; and + - IETF RFC 3260 [12] and IETF RFC 6505 [13]. +- An MGCF acting as an UA controlling an IM-MGW using the Mn interface as defined by TS 29.163 [17] and TS 29.332 [14]: + +- Reserve IMS Connection Point; +- Configure IMS Connection Point; +- Reserve and Configure IMS Connection Point; and +- Release IMS Connection Point. + +## 7.5 Handling of connected IP realms + +For each IP realm to which a controlled MR has direct access, the UA supporting OMR may be provisioned with a list of the names of connected IP realms, if any. The UA shall determine if an IP realm is connected to a local IP realm based only on provisioning. + +NOTE 1: The OMR algorithm assumes that a first IMS-ALG or UA sending an SDP offer that offers connectivity via a local IP realm will accept from a second IMS-ALG or UA an SDP answer with an address in a connected IP realm, even if the first IMS-ALG or UA does not have provisioned information about the connected IP realm. + +NOTE 2: Connected IP realm lists only need to be provisioned at certain OMR-capable nodes. For example, it is preferred that an IBCF whose TrGW has connectivity to multiple peer networks via bilateral interconnect be provisioned with connected IP realm information. + +# --- 8 Subsequent SDP offer/answer transactions + +## 8.1 General + +Any UA or IMS-ALG controlling a media stream may initiate a subsequent SDP offer/answer transaction at any time after first establishing the media flow, in order to modify characteristics of the media flow. + +NOTE: For example, a media endpoint (IP address) can change, the preferred codec can change, or a server can select to insert a media function such as a tone generator or conference focus. + +An IMS-ALG or UA shall handle a received SDP offer as a subsequent SDP offer as specified in clause 8.2 if an initial or second SDP offer/answer transaction has been completed and a received SDP offer contains no OMR specific SDP attributes. + +## 8.2 IMS-ALG and UA subsequent SDP offer procedures + +When a IMS-ALG determines according to clause 8.1 that a received SDP offer shall be handled as a subsequent SDP offer, the IMS-ALG with or without a local primary or secondary MR allocated shall perform the following steps: + +- 1) determine if the local primary or secondary MR can be inserted or removed from the media path as specified in clause 8.4; +- 2) if the IMS-ALG keeps an allocated MR or allocates a new MR and continues with an MR inserted in the media path, the IMS-ALG shall: + - if necessary (e.g. due to a codec change or allocation of a new MR) interact with the MR; + - update the connection address for the media line in the outgoing subsequent SDP offer; and + - forward the modified SDP offer as specified in 3GPP TS 24.229 [4]. +- 3) if the IMS-ALG does not allocate a new MR or deallocated an MR allocated in the initial or second SDP offer / answer transaction in clause 6 and continues without a MR inserted in the media path, forward the incoming subsequent SDP offer as received. + +When a UA (e.g. a conference application treating the media resource as an endpoint or an MGCF) determines according to clause 8.1 that a SDP offer shall be sent as a subsequent SDP offer , the UA shall not apply OMR + +procedures in clause 7 when sending the subsequent SDP offer. If the conditions in clause 8.4 for reallocating a MR are fulfilled, the UA may reallocate a MR. + +## 8.3 IMS-ALG and UA subsequent SDP answer procedures + +When an IMS-ALG receives a subsequent SDP answer as the result of a subsequent SDP offer generated according to clauses 8.2, the IMS-ALG with or without a local primary or secondary MR allocated shall perform the following steps: + +- 1) if the IMS-ALG has a local MR allocated: + +NOTE: The local MR can have been allocated during the initial or second SDP offer / answer transaction as described in clause 6 or as the result of the subsequent SDP offer generated in clause 8.2. + +- a) if necessary interact with the MR as described in clauses 6.3; and +- b) update connection address in the outgoing subsequent SDP answer for the media line with the MR connection information; +- c) forward the modified SDP answer as specified in 3GPP TS 24.229 [4]; and + +- 2) if the IMS-ALG has no local MR allocated: + +- a) if the local MR was allocated when the subsequent SDP offer was received, release MR resources; and +- b) forward the subsequent SDP answer as received. + +When a UA not acting as a B2BUA (e.g. a conference application treating the media resource as an endpoint or the MGCF) receives a subsequent SDP answer, the UA shall not apply OMR procedures specified in clause 7. + +## 8.4 Handling media resources during a subsequent SDP offer/answer transaction + +An IMS-ALG, an AS acting as B2BUA and adapting IMS-ALG procedures to control an MRF or a UA not acting as a B2BUA (e.g. a conference application treating the media resource as an endpoint or the MGCF) shall not allocate, deallocate or reallocate a MR during the subsequent SDP offer/answer transaction unless any of the following exceptions apply: + +- an IMS-ALG may allocate an MR resource if the downstream and upstream media anchoring points are within the same realm and in the same operator network as the IMS-ALG; +- an IMS-ALG may deallocate an MR resource if the downstream and upstream media anchoring points are within the same realm and in the same operator network as the IMS-ALG; or +- an UA may reallocate an MR resource if the downstream and upstream media anchoring point is within the same realm and in the same operator network as the UA. + +If an IMS-ALG or UA decides to allocate or reallocate a MR, the IMS-ALG or UA shall interact with the MR as described in clause 6.3 or 7.4. + +If a IMS-ALG decides to deallocate a MR, the IMS-ALG shall release the MR resource when receiving the subsequent SDP answer. + +# Annex A (informative): Signalling flows + +## A.1 Scope of signalling flows + +This annex gives examples of signalling flows for Optimized Media Routeing (OMR) based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP). The OMR specific SDP syntax is described in TS 24.229 [4]. + +## A.2 Introduction + +The signalling flows in this annex are based on IP realm and IP structure in Figure A.2-1. + + + +The diagram illustrates the IP realm and IP structure across three network domains: + +- Home IMS network H:** Realm Ha.operatorH.net. It contains an S-CSCF/BGCF connected to two parallel paths. Each path consists of an IBCF (IBCF-2 and IBCF-3) and a TrGW. IP addresses shown are 190.1.15.2 (Ha), Xa4 179.14.1.2, and Xa4 179.14.1.3. +- IPX network X:** Realm Xa.operatorX.net. It connects to the Home network via two parallel paths. Each path consists of an IC (IC-1 and IC-2) and an MGW. IP addresses shown are 179.14.1.1 (Xa2), 179.14.1.4 (Xa2), Xa2 178.15.1.2, and Xa2 178.15.1.3. +- Visited network V:** Realm Va.operatorV.net. It contains a UE-A (Va 192.0.2.1) connected to a P-CSCF-A, which is connected to a PCRF and a PDN. The PDN is connected to a TrGW (IBCF-1) with IP address 192.0.2.2. Another TrGW (IBCF-4) with IP address 192.0.2.3 is connected to a TRF, which is connected to another TrGW (IBCF-5) with IP address Va 192.0.2.4. + +**Legend:** + +- Solid line with double arrow: Control signalling path +- Dashed line with single arrow: Media path after OMR + +Diagram of IP realm and IP structure showing Home IMS network H, IPX network X, and Visited network V with various network elements like S-CSCF, IBCF, TrGW, IC, MGW, P-CSCF, PCRF, PDN, TRF, and UEs. + +Figure A.2-1: IP realm and IP structure + +Operator X and operator Y have an agreement to allow roaming users and to use OMR as much as possible. + +UE-A and UE-B are mobile users roaming into the visited network X. IP addresses etc. are obtained as described in TS 24.229 [4]. + +The operator X implements the IBCF policy to allow OMR optimization of anchoring if originating UE is a visiting/roaming user respectively if terminating UE is a visiting/roaming user. + +The operator Y implements the IBCF policy to allow OMR optimization of anchoring if home UE is visiting/roaming in another network. + +## --- A.3 Media bypassing all IMS-ALGs + +### A.3.1 General + +This clause provides an example of a call where the media is bypassing all IMS-ALG and sent directly between the UEs. + +### A.3.2 Message flow + +This clause describes the scenario when two mobile user A and B roams into a visited network X and both users belongs to the same operator Y. + +Preconditions: + +- Both user A and B are registered to the Home IMS network Y via the visited operator X network; +- the visited operator X and the operator of user A and B IMS home network Y have an agreement to allow media to be bypassed using OMR; +- both user A and B are connected to IP realm Xa of the visited operator network X; +- the AMR codec is allowed and accepted by all involved entities; and +- no B2BUA manipulating SDP is connected in the intermediate IM CN subsystem. + +Figure A.3.2-1 shows the message flow for the scenario. + + + +The diagram illustrates the signalling flow for media bypassing all IMS ALGs. It shows the interaction between UE-A, P-CSCF A, IBCF-1, IBCF-2, Intermediate IM CN subsystem entities X, IBCF-3, IBCF-4, P-CSCF B, and UE-B. The flow includes INVITE, 183, PRACK, 200 OK (PRACK), UPDATE, 200 OK (UPDATE), 180, 200 OK (INVITE), and ACK messages. The audio media path is established between UE-A and UE-B via the Intermediate IM CN subsystem entities X. + +**Visited network X** (Realms: Xa.operatorX.net, X.operatorX.net, X.operatorY.net) + +**Home IMS network Y (of user A and B)** (Realms: Yb.operatorY.net, X.operatorY.net) + +**Visited network X** (Realms: Xa.operatorX.net, X.operatorX.net, X.operatorY.net) + +**Entities:** UE-A (192.0.2.1), P-CSCF A (192.0.2.2), IBCF-1 (13.24.1.1), IBCF-2 (13.24.1.2), Intermediate IM CN subsystem entities X (190.1.15.2), IBCF-3 (190.1.15.3), IBCF-4 (13.24.1.4), P-CSCF B (192.0.2.3), UE-B (192.0.2.4) + +**Signalling Flow:** + +1. INVITE [AMR, c=192.0.2.1] from UE-A to P-CSCF A +2. INVITE [AMR, c=192.0.2.1] from P-CSCF A to IBCF-1 +3. INVITE [AMR, c=13.24.1.1, visited-realm:1 Xa 192.0.2.1, visited-realm:2 X-Y 13.24.1.1] from IBCF-1 to IBCF-2 +4. INVITE [AMR, c=190.1.15.2, visited-realm:1 Xa 192.0.2.1, visited-realm:2 X-Y 13.24.1.1, visited-realm:3 Yb 190.1.15.2] from IBCF-2 to Intermediate IM CN subsystem entities X +5. INVITE [AMR, c=190.1.15.2, visited-realm:1 Xa 192.0.2.1, visited-realm:2 X-Y 13.24.1.1, visited-realm:3 Yb 190.1.15.2] from Intermediate IM CN subsystem entities X to IBCF-3 +6. INVITE [AMR, c=13.24.1.1, visited-realm:1 Xa 192.0.2.1, visited-realm:2 X-Y 13.24.1.1] from IBCF-3 to IBCF-4 +7. INVITE [AMR, c=192.0.2.1, visited-realm:1 Xa 192.0.2.1] from IBCF-4 to P-CSCF B +8. INVITE [c=192.0.2.1] from P-CSCF B to UE-B +9. 183 [c=192.0.2.4] from UE-B to P-CSCF B +10. 183 [AMR, c=192.0.2.4] from P-CSCF B to IBCF-4 +11. 183 [AMR, c=0.0.0.0, visited-realm:1 Xa 192.0.2.4] from IBCF-4 to IBCF-3 +12. 183 [AMR, c=0.0.0.0, visited-realm:1 Xa 192.0.2.4] from IBCF-3 to Intermediate IM CN subsystem entities X +13. 183 [AMR, c=0.0.0.0, visited-realm:1 Xa 192.0.2.4] from Intermediate IM CN subsystem entities X to IBCF-2 +14. 183 [AMR, c=0.0.0.0, visited-realm:1 Xa 192.0.2.4] from IBCF-2 to IBCF-1 +15. 183 [AMR, c=192.0.2.4] from IBCF-1 to P-CSCF A +16. 183 [AMR, c=192.0.2.4] from P-CSCF A to UE-A +17. PRACK from UE-A to P-CSCF A +18. PRACK from P-CSCF A to IBCF-1 +19. PRACK from IBCF-1 to IBCF-2 +20. PRACK from IBCF-2 to Intermediate IM CN subsystem entities X +21. PRACK from Intermediate IM CN subsystem entities X to IBCF-3 +22. PRACK from IBCF-3 to IBCF-4 +23. PRACK from IBCF-4 to P-CSCF B +24. PRACK from P-CSCF B to UE-B +25. 200 OK (PRACK) from UE-B to P-CSCF B +26. 200 OK (PRACK) from P-CSCF B to IBCF-4 +27. 200 OK (PRACK) from IBCF-4 to IBCF-3 +28. 200 OK (PRACK) from IBCF-3 to Intermediate IM CN subsystem entities X +29. 200 OK (PRACK) from Intermediate IM CN subsystem entities X to IBCF-2 +30. 200 OK (PRACK) from IBCF-2 to IBCF-1 +31. 200 OK (PRACK) from IBCF-1 to P-CSCF A +32. 200 OK (PRACK) from P-CSCF A to UE-A +33. UPDATE [AMR, c=192.0.2.1] from UE-A to P-CSCF A +34. UPDATE [AMR, c=192.0.2.1] from P-CSCF A to IBCF-1 +35. UPDATE [AMR, c=192.0.2.1] from IBCF-1 to IBCF-2 +36. UPDATE [AMR, c=192.0.2.1] from IBCF-2 to Intermediate IM CN subsystem entities X +37. UPDATE [AMR, c=192.0.2.1] from Intermediate IM CN subsystem entities X to IBCF-3 +38. UPDATE [AMR, c=192.0.2.1] from IBCF-3 to IBCF-4 +39. UPDATE [AMR, c=192.0.2.1] from IBCF-4 to P-CSCF B +40. UPDATE [AMR, c=192.0.2.1] from P-CSCF B to UE-B +41. 200 OK (UPDATE) [c=192.0.2.4] from UE-B to P-CSCF B +42. 200 OK (UPDATE) [AMR, c=192.0.2.4] from P-CSCF B to IBCF-4 +43. 200 OK (UPDATE) [AMR, c=192.0.2.4] from IBCF-4 to IBCF-3 +44. 200 OK (UPDATE) [AMR, c=192.0.2.4] from IBCF-3 to Intermediate IM CN subsystem entities X +45. 200 OK (UPDATE) [AMR, c=192.0.2.4] from Intermediate IM CN subsystem entities X to IBCF-2 +46. 200 OK (UPDATE) [AMR, c=192.0.2.4] from IBCF-2 to IBCF-1 +47. 200 OK (UPDATE) [AMR, c=192.0.2.4] from IBCF-1 to P-CSCF A +48. 200 OK (UPDATE) [AMR, c=192.0.2.4] from P-CSCF A to UE-A +49. 180 from UE-B to P-CSCF B +50. 180 from P-CSCF B to IBCF-4 +51. 180 from IBCF-4 to IBCF-3 +52. 180 from IBCF-3 to Intermediate IM CN subsystem entities X +53. 180 from Intermediate IM CN subsystem entities X to IBCF-2 +54. 180 from IBCF-2 to IBCF-1 +55. 180 from IBCF-1 to P-CSCF A +56. 180 from P-CSCF A to UE-A +57. 200 OK (INVITE) [c=192.0.2.4] from UE-B to P-CSCF B +58. 200 OK (INVITE) [AMR, c=192.0.2.4] from P-CSCF B to IBCF-4 +59. 200 OK (INVITE) [AMR, c=192.0.2.4] from IBCF-4 to IBCF-3 +60. 200 OK (INVITE) [AMR, c=192.0.2.4] from IBCF-3 to Intermediate IM CN subsystem entities X +61. 200 OK (INVITE) [AMR, c=192.0.2.4] from Intermediate IM CN subsystem entities X to IBCF-2 +62. 200 OK (INVITE) [AMR, c=192.0.2.4] from IBCF-2 to IBCF-1 +63. 200 OK (INVITE) [AMR, c=192.0.2.4] from IBCF-1 to P-CSCF A +64. 200 OK (INVITE) [AMR, c=192.0.2.4] from P-CSCF A to UE-A +65. ACK from UE-A to P-CSCF A +66. ACK from P-CSCF A to IBCF-1 +67. ACK from IBCF-1 to IBCF-2 +68. ACK from IBCF-2 to Intermediate IM CN subsystem entities X +69. ACK from Intermediate IM CN subsystem entities X to IBCF-3 +70. ACK from IBCF-3 to IBCF-4 +71. ACK from IBCF-4 to P-CSCF B +72. ACK from P-CSCF B to UE-B + +**audio media** (established between UE-A and UE-B via Intermediate IM CN subsystem entities X) + +Sequence diagram showing the signalling flow for media bypassing all IMS ALGs. The diagram illustrates the interaction between UE-A, P-CSCF A, IBCF-1, IBCF-2, Intermediate IM CN subsystem entities X, IBCF-3, IBCF-4, P-CSCF B, and UE-B. The flow includes INVITE, 183, PRACK, 200 OK (PRACK), UPDATE, 200 OK (UPDATE), 180, 200 OK (INVITE), and ACK messages. The audio media path is established between UE-A and UE-B via the Intermediate IM CN subsystem entities X. + +NOTE: For clarity, the SIP 100 (Trying) messages are not shown in the signalling flow. + +**Figure A.3.2-1: Signalling flow for media bypassing all IMS ALGs** + +The steps of the flow are as follows: + +#### **1. INVITE request (UE-A to P-CSCF-A) - see example in table A.3.2-1.** + +The UE-A sends a SIP INVITE request including an initial SDP offer according to TS 24.229 [4]. + +**Table A.3.2-1: SIP INVITE request (UE-A to P-CSCF-A)** + +``` + +INVITE SIP: user_B@operator_Y.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o= 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 192.0.2.1 +m=audio 49170 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 + +``` + +#### 2. INVITE request (P-CSCF-A to IBCF-1) - see example in table A.3.2-1. + +The P-CSCF-A uses the procedures in clauses 6.1.5, 6.1.7 and 6.1.9 since no MR could be bypassed and no MR is allocated. + +The P-CSCF-A: + +- uses the connection-address from the SDP c-line as incoming connection-address in subsequent steps; +- uses the port information from the SDP m-line as incoming port information in subsequent steps; +- uses the codec information from the SDP m-line in subsequent steps; +- inserts the incoming codec information into the SDP m-line and associated attribute lines of the modified initial SDP offer; +- uses the incoming connection address as the connection address in the SDP c-line of the forwarded initial SDP offer, and +- use the incoming port information as port information in the SDP m-line of the modified initial SDP offer. + +The P-CSCF-A then selects an IBCF, IBCF-1, in the IP realm "Xa.operatorX.net" and forwards the INVITE request with the initial SDP offer to the IBCF-1 according to TS 24.229 [4]. + +#### 3. INVITE request (IBCF-1 to IBCF-2) - see example in table A.3.2-3 + +The IBCF-1 uses the procedures in clauses 6.1.5, 6.1.6 and 6.1.9 since no previous realm instance offers an opportunity to bypass a previous MR and a local MR is required for IP realm matching. + +The IBCF-1: + +- uses the connection-address from the SDP c-line as incoming connection-address in subsequent steps; +- uses the port information from the SDP m-line as incoming port information in subsequent steps; +- uses the codec information from the SDP m-line in subsequent steps; +- allocates an MR context with access to the IP realms and addrtypes associated with the incoming and outgoing signalling paths; +- inserts the incoming connection address and incoming port information for the media line into the remote connection address and port information for the incoming termination on the MR; +- provides to the MR the incoming codec information; + +- replaces the connection address and port information for the media line in the initial SDP offer with the connection address and port information from the MR termination on the outgoing side; +- constructs and adds a visited-realm instance for the media line in the received initial SDP offer to the modified initial SDP offer; +- adds to the modified initial SDP offer a visited-realm instance for the IP realm associated with the connection address and port information for the media line in the modified initial SDP offer, including the incoming codec; and +- computes a checksum value for the media line as described in clause 5.6.3 and adds the "omr-m-cksum" and "omr-s-cksum" attributes for the media line. The "omr-s-cksum" is set to "0" since there are no session attributes to compute the checksum on. + +The IBCF-1 then selects an IBCF, IBCF-2, in the IP realm "X-Y.operatorX.net" and forwards the INVITE request with the initial SDP offer to the IBCF-2 according to TS 24.229 [4]. + +**Table A.3.2-3: SIP INVITE request (IBCF-1 to IBCF-2)** + +``` +INVITE SIP: user_B@operator_Y.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 13.24.1.1 +m=audio 62111 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 +a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.1 49170 +a=visited-realm:2 X-Y.operator.netX IN IP4 13.24.1.1 62111 +a=omr-m-cksum:(..) +a=omr-s-cksum:0 +``` + +#### 4-5. INVITE request (IBCF-2 to IBCF-3 via intermediate IMS CN subsystem entities) - see example in table A.3.2-4. + +The IBCF-2 uses the procedure in clauses 6.1.5, 6.1.6 and 6.1.9 since no realm instance offers an opportunity to bypass a previous MR and a local MR is required for IP realm matching. + +The IBCF-2: + +- uses the connection-address from the SDP c-line as incoming connection-address in subsequent steps; +- uses the port information from the SDP m-line as incoming port information in subsequent steps; +- uses the codec information from the SDP m-line and associated non-OMR attribute lines as incoming codec information in subsequent steps; +- allocates an MR context with access to the IP realms, nettypes and addrtypes associated with the incoming and outgoing signalling paths, respectively, applying procedures as described in clause 6.3, +- insert the incoming connection address and incoming port information for the media line into the remote connection address and port information for the incoming termination on the MR; +- provides to the MR the incoming codec information; +- replaces the connection address and port information for the media line in the initial SDP offer with the connection address and port information from the MR termination on the outgoing side; + +- adds to the modified initial SDP offer a visited-realm instance for the IP realm associated with the connection address and port information for the media line in the modified SDP offer, including the incoming codec; and +- computes a checksum value for the media line as described in clause 5.3.4 and adds the "omr-m-cksum" and "omr-s-cksum" attributes for the media line The "omr-s-cksum" attribute is set to "0" since there are no session attributes to compute the checksum on.. + +The IBCF-2 forwards the INVITE request to the intermediate IMS CN subsystem entities in IP realm "Yb.operatorY.net" according to TS 24.229 [4]. + +None of the intermediate IMS CN subsystem entities manipulated with the initial SDP offer but the identity of [user\\_B@operator\\_Y.net](#) in the Request-URI is change to the contact address, i.e. UE-B@operatorX.net. + +The intermediate IMS CN subsystem entities select an IBCF, IBCF-3, and forward the INVITE request with the initial SDP offer to the IBCF-3 according to TS 24.229 [4]. + +**Table A.3.2-4: SIP INVITE request (IBCF-2 to IBCF-3 via intermediate IMS CN subsystem entities)** + +``` +INVITE SIP: sip:UE-B@operatorX.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 190.1.15.2 +m=audio 11324 RTP/AVP 96 07 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 +a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.1 49170 +a=visited-realm:2 X-Y.operator.netX IN IP4 13.24.1.1 62111 +a=visited-realm:3 Yb.operatorY.net IN IP4 190.1.15.2 11324 +a=omr-m-cksum:(..) +a=omr-s-cksum:0 +``` + +#### 6. INVITE request (IBCF-3 to IBCF-4) - see example in table A.3.2-6. + +The IBCF-3 uses the procedures in clauses 6.1.4, 6.1.7 and 6.1.9 since a previous realm instance exists that can be used to bypass a previous MR, IBCF-2, and bypass is allowed according to operator X and operator Y agreements, and the previous realm instance match the outgoing IP realm so that no local MR is required. + +The IBCF-3: + +- uses the connection address and port information for the media line in the initial SDP offer with the connection-address and port information from the selected instance 2 as incoming connection address and incoming port information for the media line; +- deletes the visited-realm instance 3; +- inserts the incoming codec information into the SDP m-line and associated attribute lines of the modified initial SDP offer; +- uses the incoming connection address as the connection address in the SDP c-line of the forwarded initial SDP offer; +- uses the incoming port information as port information in the SDP m-line of the modified initial SDP offer; and + +- computes a checksum value for the media line as described in clause 5.3.4 and adds the "omr-m-cksum" and "omr-s-cksum" attributes for the media line. The "omr-s-cksum" attribute is set to "0" since there are no session attributes to compute the checksum on. + +The IBCF-3 then selects an IBCF, IBCF-4, in the IP realm "X.operatorX.net, Y.operatorY.net" and forwards the initial SDP offer according to TS 24.229 [4] to IBCF-4. + +**Table A.3.2-6: SIP INVITE request (IBCF-3 to IBCF-4)** + +``` +INVITE SIP: sip:UE-B@operatorX.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 13.24.1.1 +m=audio 62111 RTP/AVP 96 07 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 +a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.1 49170 +a=visited-realm:2 X-Y.operator.netIN IP4 13.24.1.1 62111 +a=omr-m-cksum: (...) +a=omr-s-cksum:0 +``` + +#### 7. INVITE request (IBCF-4 to P-CSCF B) - see example in table A.3.2-7. + +The IBCF-4 uses the procedures in clauses 6.1.4, 6.1.7 and 6.1.9 since a previous realm instance exists that can be used to bypass a previous MR, IBCF-1, and the previous realm instance match the outgoing IP realm so that no local MR is required. + +The IBCF-4: + +- uses the connection address and port information for the media line in the initial SDP offer with the connection-address and port information from the selected instance 1 as incoming connection address and incoming port information for the media line; +- deletes the visited-realm instance 2; +- inserts the incoming codec information into the SDP m-line and associated attribute lines of the modified initial SDP offer; +- uses the incoming connection address as the connection address in the SDP c-line of the forwarded initial SDP offer; +- uses the incoming port information as port information in the SDP m-line of the modified initial SDP offer; and +- computes a checksum value for the media line as described in clause 5.3.4 and adds the "omr-m-cksum" and "omr-s-cksum" attributes for the media line. The "omr-s-cksum" attribute is set to "0" since there are no session attributes to compute the checksum on. + +The IBCF-4 forwards the INVITE request with the initial SDP offer to the P-CSCF-B, in the IP realm "X.operatorX.net" according to TS 24.229 [4]. + +**Table A.3.2-7: SIP INVITE request (IBCF-4 to P-CSCF B)** + +``` + +INVITE SIP: sip:UE-B@operatorX.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 192.0.2.1 +m=audio 49170 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 +a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.1 49170 +a=omr-m-cksum:(..) +a=omr-s-cksum:0 + +``` + +#### **8. INVITE request (P-CSCF to UE- B) - see example in table A.3.2-8.** + +The P-CSCF-B uses the procedures in clauses 6.1.5, 6.1.7 and 6.1.9 since no previous realm instance offers an opportunity to bypass an MR and no local MR is required to match the incoming realm to the outgoing realm. + +- uses the connection-address from the SDP c-line as incoming connection-address; +- uses the port information from the SDP m-line as incoming port information; +- uses the codec information from the SDP m-line and associated non-OMR attribute lines as incoming codec information; and +- according to the local policy, deletes the visited-realm "visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.1 49170", the "omr-m-cksum:(...)" and the "omr-s-cksum=:0" attributes from the SDP offer. + +The P-CSCF-B forwards the INVITE request with the initial SDP offer to the UE-B according to TS 24.229 [4]. + +**Table A.3.2-8: SIP INVITE request (P-CSCF to UE-B)** + +``` + +INVITE SIP: sip:UE-B@operatorX.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s= +t=0 0 +c=IN IP4 192.0.2.1 +m=audio 49170 RTP/AVP 96 97 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:97 AMR +a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:96 telephone-event +a=maxptime:20 + +``` + +#### **9. 183 (Session Progress) response (UE-B to P-CSCF-B) - see example in table A.3.2-9.** + +The UE accepts the codec and sends a 183 (Session Progress) response with an initial SDP answer indicating that resources are not yet available to P-CSCF-B according to TS 24.229 [4]. + +**Table A.3.2-9: 183 (Session Progress) response (UE-B to P-CSCF-B)** + +``` + +SIP/2.0 183 Session Progress + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s=- +c=IN IP4 192.0.2.4 +t=0 0 +m=audio 16511 RTP/AVP 97 98 +a=curr:qos local none +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:98 AMR +a=fmtp:98 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:97 telephone-event +a=maxptime:20 + +``` + +#### **10. 183 (Session Progress) response (P-CSCF-B to IBCF-4) - see example in table A.3.2-9** + +The P-CSCF-B uses the procedures in clauses 6.2.7 and 6.2.9 since the connection address is valid and no primary local MR was allocated. + +The P-CSCF-B:- does not modify the initial SDP answer and forwards the 183 (Session Progress) response with the initial SDP answer to IBCF-4 according to TS 24.229 [4]. + +#### **11. 183 (Session Progress) response (IBCF-4 to IBCF-3) - see example in table A.3.2-11** + +The IBCF-4 uses the procedures in clauses 6.2.7 and 6.2.9 since the connection address is valid and no primary local MR was allocated. + +The IBCF-4: + +- copies into the media line of the initial SDP answer the visited-realm instance 1 from the media line of the received initial SDP offer that was used to populate the connection address and port information in the forwarded initial SDP offer, replacing the connection-address and port information in the instance with the connection address and port information from the received initial SDP answer; and +- replaces the connection address information in the initial SDP answer with the unspecified IPv4 address. + +The IBCF-4 forwards the 183 (Session Progress) response with the initial SDP answer to IBCF-3 according to TS 24.229 [4]. + +**Table A.3.2-11 183 (Session Progress) response (IBCF-4 to IBCF-3)** + +``` + +SIP/2.0 183 Session Progress +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s=- +c=IN IP4 0.0.0.0 +t=0 0 +m=audio 16511 RTP/AVP 97 98 +a=curr:qos local none +a=curr:qos remote sendrecv +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:98 AMR +a=fmtp:98 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:97 telephone-event +a=maxptime:20 +a=visited-realm:1 Xa.operatorX.net IN IP4 192.0.2.4 16511 + +``` + +#### **12-13. 183 (Session Progress) response (IBCF-3 to IBCF-2 via intermediate IMS CN subsystem entities) - see example in table A.3.2-11** + +The IBCF-3 uses the procedures in clauses 6.2.5 and 6.2.9 since the initial SDP answer contained an unspecified connection address and a realm instance matching one in the received initial SDP offer and since no primary local MR was allocated. + +The IBCF-3 does not modify the initial SDP answer since the visited-realm instance does not match the information in the initial SDP offer. + +The IBCF-3 then forwards the 183 (Session Progress) response with the initial SDP answer to intermediate IMS CN subsystem entities according to TS 24.229 [4]. + +The intermediate IMS CN subsystem entities do not modify the initial SDP answer and forwards the 183 (Session Progress) response with the initial SDP answer to IBCF-2 according to TS 24.229 [4]. + +#### **14. 183 (Session Progress) response (IBCF-2 to IBCF-1) - see example in table A.3.2-11** + +The IBCF-2 uses the procedures in clauses 6.2.5 and 6.2.9 since the initial SDP answer contained an unspecified connection address and a realm instance matching one in the received initial SDP offer and the local MR allocated in step 4 can be bypassed. + +The IBCF does not modify the initial SDP answer since the visited-realm instance does not match the information in the initial SDP offer. + +The IBCF-2 forwards the 183 (Session Progress) response with initial SDP answer to IBCF-1 according to TS 24.229 [4]. + +The IBCF-2 retains the primary local MR allocated in step 4, until it is no longer potentially needed for this and any other forked dialog. + +#### **15. 183 (Session Progress) response (IBCF-1 to P-CSCF-A) - see example in table A.3.2-15** + +The IBCF-1 uses the procedures in clauses 6.2.5 and 6.2.8 since the initial SDP answer contained an unspecified connection address and a realm instance matching one in the received initial SDP offer and the local MR allocated in step 3 can be bypassed. + +The IMS-ALG: + +- replaces the connection address and port information for the media line in the initial SDP answer with the connection address and port information from the visited-realm instance in the received initial SDP answer. + +The IBCF-1 forwards the 183 (Session Progress) response with the initial SDP answer to P-CSCF-A according to TS 24.229 [4]. + +The IBCF-1 retains the primary local MR allocated in step 3, until it is no longer potentially needed for this and any other forked dialog. + +**Table A.3.2-15: 183 (Session Progress) response (IBCF-1 - P-CSCF-A)** + +``` +SIP/2.0 183 Session Progress + +SIP headers according to 3GPP TS 24.229 [4] + +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933615 IN IP4 192.0.2.1 +s=- +c=IN IP4 192.0.2.4 +t=0 0 +m=audio 16511 RTP/AVP 97 98 +a=curr:qos local none +a=curr:qos remote sendrecv +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:98 AMR +a=fmtp:98 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:97 telephone-event +a=maxptime:20 +``` + +#### **16. 183 (Session Progress) response (P-CSCF-A to UE-A) - see example in table A.3.2-15** + +The P-CSCF-A: + +- forwards the 183 (Session Progress) with the initial SDP answer to the UE-A according to TS 24.229 [4]; and +- deletes the visited-realm instance according to local policy. + +#### **17-24. PRACK request (UE-A to UE-B via P-CSCF-A, IBCF-1, IBCF-2, intermediate IMS CN subsystem entities, IBCF-3, IBCF-4 and P-CSCF-B).** + +The UE-A acknowledge the reception of the initial SDP answer and the 183 (Session Progress) response by means of a PRACK request. + +#### **25-32. 200 (OK) response to the PRACK request (UE-B to UE-A via P-CSCF-B, IBCF-4, IBCF-3, intermediate IMS CN subsystem entities, IBCF-2, IBCF-1 and P-CSCF-A).** + +The UE-B acknowledges the reception of the PRACK request by means of a 200 (OK) response. + +#### **33. UPDATE request (UE-A to P-CSCF-A) - see example in table A.3.2-33.** + +When the UE-A has got resources reserved the UE-A sends an UPDATE request. + +The subsequent SDP offer in the UPDATE the request is the same as the initial SDP offer in the INVITE request in the step 1 with the only exception that "a=curr:qos local none" is now changed to "a=curr:qos local sendrecv". + +**Table A.3.2-33: UPDATE request (UE-A to P-CSCF-A)** + +``` + +UPDATE SIP: sip:UE-A@operatorX.net; SIP/2.0 + +SIP headers according to 3GPP TS 24.229 [4] +Content-Type: application/sdp +Content-Length: (...) + +v=0 +o=- 2987933615 2987933616 IN IP4 192.0.2.4 +s=- +c=IN IP4 192.0.2.1 +t=0 0 +m=audio 16511 RTP/AVP 97 98 +a=curr:qos local sendrecv +a=curr:qos remote none +a=des:qos mandatory local sendrecv +a=des:qos none remote sendrecv +a=rtpmap:98 AMR +a=fmtp:98 mode-set=0,2,5,7; mode-change-period=2 +a=rtpmap:97 telephone-event +a=maxptime:20 + +``` + +#### **34-40. UPDATE request (P-CSCF-A to UE-B via IBCF-1, IBCF-2, intermediate IMS CN subsystem entities, IBCF-3, IBCF-4 and P-CSCF-B).** + +- 34) When the P-CSCF-A receives the UPDATE request, the P-CSCF-A forwards the UPDATE request without modifying the subsequent SDP offer. +- 35) When the IBCF-1 receives the UPDATE request, the IBCF-1 forwards the UPDATE request without modifying the subsequent SDP offer. +- 36) When the IBCF-2 receives the UPDATE request, the IBCF-2 forwards the UPDATE request without modifying the subsequent SDP offer. +- 37) Intermediate IMS CN subsystem entities do not manipulate the SDP offer. +- 38) When the IBCF-3 receives the UPDATE request, the IBCF-3 forwards the UPDATE request without modifying the subsequent SDP offer. +- 39) When the IBCF-4 receives the UPDATE request, the IBCF-4 forwards the UPDATE request without modifying the subsequent SDP offer. +- 40) When the P-CSCF-B receives the UPDATE request, the P-CSCF-B forwards the UPDATE request without modifying the subsequent SDP offer. + +#### **41. 200 (OK) response to the UPDATE request (UE-B to P-CSCF-B) - see example in table A.3.2-41.** + +The UE-B acknowledges the reception of the UPDATE request by means of a 200 (OK) response containing a subsequent SDP answer. + +**Table A.3.2-41: 200 (OK) response to the UPDATE request (UE-B to P-CSCF-B).** + +``` + +SIP/2.0 200 OK +Via: +To:
C3-110028, C3-110030, C3-110031, C3-110032, C3-110033, C3-110034, C3-110233, C3-110234, C3-110235, C3-110238, C3-110374, C3-110375, C3-110376 | 1.0.0 | 1.1.0 | +| 02.28.11 | | | | | Version 1.2.0 created by rapporteur based on PCRs
C3-110472, C3-110579, C3-110580, C3-110582, C3-110601, C3-110603, C3-110604, C3-110605, C3-110650, C3-110651, C3-110696, C3-110699, C3-110723, C3-110755 | 1.1.0 | 1.2.0 | +| 03/2011 | TSG#51 | | | | 3GPP TS 29.079 2.0.0 have been approved in TSG#51 | 2.0.0 | 10.0.0 | +| 06/2011 | TSG#52 | CP-110408 | 0001 | 2 | Adding session checksum in the simple example flow | 10.0.0 | 10.1.0 | +| 06/2011 | TSG#52 | CP-110408 | 0002 | 2 | Update of proactive transcoder without resource reservation FLOW | 10.0.0 | 10.1.0 | +| 06/2011 | TSG#52 | CP-110408 | 0003 | 3 | Clarifying checksum calculation | 10.0.0 | 10.1.0 | +| 06/2011 | TSG#52 | CP-110408 | 0004 | 3 | Receiving and modified SDP offer clarification | 10.0.0 | 10.1.0 | +| 06/2011 | TSG#52 | CP-110408 | 0005 | 2 | IMS-ALG bypasses an allocated transcoding MR - FLOW | 10.0.0 | 10.1.0 | +| 06/2011 | TSG#52 | CP-110408 | 0006 | 2 | Enhanced IP realm definition | 10.0.0 | 10.1.0 | +| 06/2011 | TSG#52 | CP-110408 | 0007 | 2 | Making connected IP realm information available | 10.0.0 | 10.1.0 | +| 09/2011 | TSG#53 | | | | Editorial Improvement by MCC | 10.1.0 | 10.1.1 | +| 12/2011 | TSG#54 | CP-110834 | 0008 | | Updated references - Media Control Channel Framework | 10.1.1 | 10.2.0 | +| 06/2012 | TSG#56 | CP-120355 | 0009 | 3 | RAVEL Loop-back routeing example updates | 10.2.0 | 11.0.0 | +| 06/2012 | TSG#56 | CP-120357 | 0010 | | Incorrect IP address in example | 10.2.0 | 11.0.0 | +| 09/2012 | TSG#57 | CP-120535 | 0013 | | OMR modification | 11.0.0 | 11.1.0 | +| 09/2012 | TSG#57 | CP-120535 | 0014 | 1 | Naming of transit network | 11.0.0 | 11.1.0 | +| 12/2012 | TSG#58 | CP-120840 | 0015 | 1 | Updating loopback example | 11.1.0 | 11.2.0 | +| 12/2012 | TSG#58 | CP-120827 | 0018 | | Reference update of draft-ietf-mediactrl-mixer-control-package | 11.1.0 | 11.2.0 | +| 12/2012 | TSG#58 | CP-120827 | 0020 | 2 | OMR Signalling Flows | 11.1.0 | 11.2.0 | +| 03/2013 | TSG#59 | CP-130079 | 0016 | 4 | Identifying an RAVEL session | 11.2.0 | 11.3.0 | +| 03/2013 | TSG#59 | CP-130079 | 0021 | | Removing all editors notes in the loopback flow | 11.2.0 | 11.3.0 | +| 06-2014 | TSG#64 | CP-140362 | 0024 | 2 | Correcting IP addresses on OMR call flow examples | 11.3.0 | 11.4.0 | +| 06-2014 | TSG#64 | CP-140382 | 0022 | 1 | II-NNI traversal scenario identification | 11.3.0 | 12.0.0 | +| 09-2014 | CT-65 | CP-140528 | 0028 | - | Correcting references | 12.0.0 | 12.1.0 | +| 09-2014 | CT-65 | CP-140528 | 0032 | 1 | Message flow correction for media bypassing all IMS-ALGs | 12.0.0 | 12.1.0 | +| 09-2014 | CT-65 | CP-140536 | 0026 | 1 | Adding the "iotl" SIP URI parameter in the loopback message flow | 12.0.0 | 12.1.0 | +| 09-2014 | CT-65 | CP-140553 | 0025 | - | Removal of a non-existing feature-capability | 12.0.0 | 12.1.0 | +| 09-2014 | CT-65 | CP-140553 | 0029 | 2 | Adding missing home network identity in g.3gpp.loopback feature-capability indicator | 12.0.0 | 12.1.0 | +| 03-2015 | CT-67 | CP-150100 | 0036 | | Instance-number value for secondary-realm | 12.1.0 | 12.2.0 | +| 03-2015 | CT-67 | CP-150100 | 0039 | | Checksum calculation | 12.1.0 | 12.2.0 | +| 03-2015 | CT-67 | CP-150100 | 0042 | | Correcting UA procedure | 12.1.0 | 12.2.0 | +| 03-2015 | CT-67 | CP-150109 | 0046 | | Reference update: draft-holmberg-dispatch-iotl | 12.1.0 | 12.2.0 | +| 06-2015 | CT-68 | CP-150340 | 0049 | 2 | Procedures for avoiding changes in the OMR algorithm outcome on subsequent SDP offer/answer transactions | 12.2.0 | 12.3.0 | +| 06-2015 | CT-68 | CP-150347 | 0050 | - | draft-holmberg-dispatch-iotl-parameter-04 updated to RFC 7549 | 12.2.0 | 12.3.0 | +| 12-2015 | | | | | Automatic upgrade from previous Release | 12.3.0 | 13.0.0 | +| Change history | | | | | | | | +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +| 03-2017 | CT#75 | | | | | Automatic upgrade from previous Release | 14.0.0 | +| 2018-06 | SA-80 | - | - | - | | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-06 | SA#88e | - | - | - | | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/29_series/29108/raw.md b/marked/Rel-16/29_series/29108/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..46437b4462d5ed19af7bbdf89cb19e3fae550ce8 --- /dev/null +++ b/marked/Rel-16/29_series/29108/raw.md @@ -0,0 +1,413 @@ + + + + + + +# --- Contents + +| | | +|------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Abbreviations ..... | 5 | +| 4 Principles for the use of RANAP on the E-interface ..... | 6 | +| 4.1 General ..... | 6 | +| 4.2 Transfer of RANAP layer 3 messages on the E-interface..... | 6 | +| 4.3 Roles of 3G_MSC-A, 3G_MSC-I and 3G_MSC-T ..... | 6 | +| 5 Use of the RANAP on the E-interface ..... | 7 | +| 5.1 RAB Assignment..... | 7 | +| 5.2 RAB Release Request ..... | 7 | +| 5.3 Iu Release Request ..... | 8 | +| 5.4 Relocation Resource Allocation..... | 8 | +| 5.5 Relocation Cancel ..... | 8 | +| 5.6 Relocation Detect and Relocation Complete ..... | 8 | +| 5.7 CN Trace invocation ..... | 9 | +| 5.8 Security mode control ..... | 9 | +| 5.9 Location Reporting Control ..... | 9 | +| 5.10 Location Report..... | 9 | +| 5.11 Direct Transfer ..... | 9 | +| 5.12 Error Indication ..... | 10 | +| 5.13 CN Deactivate Trace..... | 10 | +| 5.14 Common ID..... | 10 | +| 5.15 Location Related Data..... | 10 | +| 5.16 UE Specific Information ..... | 10 | +| 5.17 RAB Modification Request..... | 10 | +| 6 RANAP messages transferred on the E-interface ..... | 11 | +| 7 Exceptions for RANAP message contents and information element coding when transferred on the E-interface ..... | 12 | +| 7.1 Message Contents..... | 12 | +| 8 RANAP message error handling when transferred on the E-interface ..... | 12 | +| Annex A (informative): Change history..... | 13 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document describes the subset of Radio Access Network Application Part (RANAP) messages and procedures, defined in 3GPP TS 25.413 [4], which is used on the E-interface. A general description can be found in 3GPP TS 23.002 [7] and 3GPP TS 23.009 [2]. + +For the initiation and execution of relocation of SRNS (relocation for short, throughout the whole document) between MSCs a subset of RANAP procedures are used. For the subsequent control of resources allocated to the User Equipment (UE) RANAP procedures are used. The Direct Transfer Elementary Procedure (EP) of RANAP, is used for the transfer of connection management and mobility management messages between the UE and the controlling 3G\_MSC. + +# --- 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". +- [2] 3GPP TS 23.009: "Handover procedures". +- [3] Void +- [4] 3GPP TS 25.413: "UTRAN Iu Interface Radio Access Network Application Part (RANAP) signalling". +- [5] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [6] 3GPP TS 29.010: "Information element mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC); Signalling procedures and the Mobile Application Part (MAP)". +- [7] 3GPP TS 23.002: "Network architecture". +- [8] Void + +# --- 3 Abbreviations + +For the purposes of the present document, the abbreviations defined in TR 21.905 [1] and the following apply: + +| | | +|-----------|------------------------------------------------------------------------------------------------------------------------| +| 3G_MSC | A third generation Mobile services Switching Centre that supports the Iu interface (and possibly also the A-interface) | +| 3G_MSC-A | The controlling 3G_MSC on which the call was originally established | +| 3G_MSC-B | The 3G_MSC to which the UE is handed over in a Basic Handover | +| 3G_MSC-B' | The 3G_MSC to which the UE is handed over in a Subsequent Handover | +| 3G_MSC-I | Interworking 3G_MSC | +| 3G_MSC-T | Target 3G_MSC | +| EP | Elementary Procedure | +| NNSF | NAS Node Selection Function | +| RNC | Radio Network Controller | + +# 4 Principles for the use of RANAP on the E-interface + +## 4.1 General + +The mechanism for the transfer of the RANAP messages on the E-interface is defined in TS 29.002 [5]. The operation of the relocation procedures between 3G\_MSCs and the use of the RANAP messages for those procedures is described in TS 23.009 [2] and TS 29.010 [6]. + +RANAP is defined to connect the RNS to both, the cs and ps domain of an UMTS CN. Procedures, messages and IEs, only defined for communication between the RNS and the ps domain of an UMTS CN will, of course, never appear on the E-interface. + +In the same way as a the connection oriented service of SCCP is used for the messages relating to one UE on the 3G\_MSC-RNS interface a TCAP dialogue is used on the E-interface for messages relating to one UE. As no correspondence to the connectionless service on the 3G\_MSC-RNS interface is used on the E-interface none of the global procedures are applicable. + +The management of the terrestrial circuits between the 3G\_MSCs is outside the scope of the E-interface (see TS 23.009 [2]), therefore all procedures, messages and information elements relating to terrestrial circuits are also excluded from the RANAP procedures and messages used on the E-interface. + +## 4.2 Transfer of RANAP layer 3 messages on the E-interface + +The RANAP data which on the 3G\_MSC-RNS interface is contained in the user data field of the exchanged SCCP frames is on the E-interface transferred as the contents of the access network signalling info in the AN-APDU parameter as described in TS 29.002 [5], indicating the access network protocol identification "ts3G-25413". + +## 4.3 Roles of 3G\_MSC-A, 3G\_MSC-I and 3G\_MSC-T + +For the description in the present document, the 3G\_MSC's functionality related to the relocation between 3G\_MSCs has been split into three logical parts, 3G\_MSC-A, 3G\_MSC-T and 3G\_MSC-I. The different roles need not necessarily be performed by different 3G\_MSCs. + +3G\_MSC-A is the call/connection controlling part of the 3G\_MSC where the call/connection was originally established and the switching point for relocation between 3G\_MSCs. (This corresponds to 3G\_MSC-A as defined in TS 23.009 [2] and TS 29.002 [5]). The 3G\_MSC that is the 3G\_MSC-A will not be changed during the duration of a call/connection. + +3G\_MSC-T is the part relating to the transitory state during the relocation for the 3G\_MSC controlling the RNS the serving RNS functionality is relocated to, when basic relocation or subsequent relocation (see TS 23.009) take place. (This corresponds, depending on the type of relocation to 3G\_MSC-A, 3G\_MSC-B or 3G\_MSC-B' in TS 23.009 [2] and TS 29.002 [5]). + +3G\_MSC-I is the part of a 3G\_MSC through which the 3G\_MSC-A, via an E-interface (or an internal interface) is in contact with the UE. (This corresponds, depending on the type of relocation to 3G\_MSC-A, 3G\_MSC-B or 3G\_MSC-B' in TS 23.009 [2] and TS 29.002 [5]). + +The 3G\_MSC that is the 3G\_MSC-A can also have the role of either the 3G\_MSC-I or the 3G\_MSC-T during a period of the call/connection. + +The following is applicable for the involved 3G\_MSCs concerning the exchange of RANAP data on an E-interface before and after a successful inter 3G\_MSC relocation: + +- 1) At basic relocation, two 3G\_MSCs are involved, one 3G\_MSC being 3G\_MSC-A and one being 3G\_MSC-T. When this relocation has been performed, the two 3G\_MSCs interworking on the E-interface have the roles of 3G\_MSC-A and 3G\_MSC-I respectively, i.e. the 3G\_MSC that is the 3G\_MSC-T during the relocation is now the 3G\_MSC-I. +- 2) At subsequent relocation back to 3G\_MSC-A, two 3G\_MSCs are involved. The 3G\_MSC having the role of 3G\_MSC-A has also the role of 3G\_MSC-T. The other 3G\_MSC involved has the role of 3G\_MSC-I. When this relocation has been completed, there is no exchange of RANAP data on the E-interface, i.e. the 3G\_MSC being the 3G\_MSC-I before and during the relocation is now no longer taking part. + +- 3) At subsequent relocation of SRNS to an 3G\_MSC not being 3G\_MSC-A, three 3G\_MSCs are involved. The roles of these 3G\_MSCs are 3G\_MSC-A, 3G\_MSC-I, and 3G\_MSC-T respectively. When this relocation has been performed, the two 3G\_MSCs interworking on an E-interface have the roles of 3G\_MSC-A and 3G\_MSC-I respectively, i.e. the 3G\_MSC that is the 3G\_MSC-T during the relocation is now the 3G\_MSC-I and the 3G\_MSC being 3G\_MSC-I during the relocation is now no longer taking part. + +# --- 5 Use of the RANAP on the E-interface + +The dedicated RANAP procedures used on the E-interface to some extent are: + +- RAB assignment; +- RAB Release Request; +- Iu Release Request; +- Relocation resource allocation; +- Relocation Detect; +- Relocation Complete; +- Relocation Cancel; +- CN Invoke Trace; +- Security mode control; +- Location Reporting Control; +- Location Report; +- Direct Transfer; +- Error Indication; +- Common ID; +- Location Related Data; +- UE Specific Information; +- RAB Modification Request. + +## 5.1 RAB Assignment + +The RAB Assignment procedure (TS 25.413 [4] subclause 8.2) is applied on the E-interface with following conditions: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +The handling of terrestrial resources is not applicable, i.e. the RANAP IEs *Transport Layer Address* and *Iu Transport Association* will be assigned by the 3G\_MSC-I. + +## 5.2 RAB Release Request + +For the RAB Release Request procedure (TS 25.413 [4] subclauses 8.3) the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-I acts as the RNS; +- the 3G\_MSC-A acts as the 3G\_MSC. + +## 5.3 Iu Release Request + +For the Iu Release Request procedure (TS 25.413 [4] subclause 8.4) the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-I acts as the RNS; +- the 3G\_MSC-A acts as the 3G\_MSC. + +Additionally, at basic Inter-3G\_MSC relocation and at subsequent Inter-3G\_MSC relocation (TS 23.009 [2]), if the 3G\_MSC that is the 3G\_MSC-A is not also the 3G\_MSC-T, the Iu Release Request procedure (TS 25.413 [4] subclause 8.4) is applied on the E-interface with the following conditions: + +- the 3G\_MSC-T acts as the RNS; +- the 3G\_MSC-A acts as the 3G\_MSC. + +## 5.4 Relocation Resource Allocation + +At basic Inter-3G\_MSC relocation (TS 23.009 [2]) the Relocation Resource Allocation procedure (TS 25.413 [4] subclause 8.7) is applied on the E-interface with the following conditions: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-T acts as the target RNS. + +At subsequent Inter-3G\_MSC relocation the Relocation Resource Allocation procedure is applied on the E-interface with the following conditions: + +- the 3G\_MSC-I acts as the 3G\_MSC; +- the 3G\_MSC-T acts as the target RNS; +- if the 3G\_MSC that is the 3G\_MSC-A is not also the 3G\_MSC-T, then this 3G\_MSC shall act as the target RNS towards the 3G\_MSC-I and as the 3G\_MSC towards the 3G\_MSC-T. + +The handling of terrestrial resources is not applicable, i.e. the RANAP IEs *Transport Layer Address* and *Iu Transport Association* will be assigned by the 3G\_MSC-T. + +In case NNSF is active, the *Iu Signalling Connection Identifier* IE and the *Global CN ID* IE shall be set by the 3G\_MSC-T towards Target RNC. + +## 5.5 Relocation Cancel + +For subsequent Inter-3G\_MSC relocation the Relocation Cancel procedure (TS 25.413 [4] subclause 8.10) is applied on the E-interface with the following conditions. + +- the 3G\_MSC-A, acts as the 3G\_MSC; +- the 3G\_MSC-I, acts as the serving RNS. + +## 5.6 Relocation Detect and Relocation Complete + +For the Relocation Detect and Relocation Complete procedure (TS 25.413 [4] subclauses 8.8 and 8.9) the applicable parts on the E-interface are the transfer of RELOCATION DETECT, RELOCATION COMPLETE messages at inter 3G\_MSC relocation. For those parts, the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-T acts as the target RNS. + +## 5.7 CN Trace invocation + +For the CN Trace invocation procedure (TS 25.413 [4], subclause 8.17), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +Additionally, at basic Inter-3G\_MSC relocation and at subsequent Inter-3G\_MSC relocation (TS 23.009 [2]), if the 3G\_MSC that is the 3G\_MSC-A is not also the 3G\_MSC-T, the CN Trace invocation procedure (TS 25.413 [4], subclause 8.17) is applied on the E-interface with the following conditions: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-T acts as the RNS. + +## 5.8 Security mode control + +For the Security mode control procedure (TS 25.413 [4], subclause 8.18), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.9 Location Reporting Control + +For the Location Reporting Control procedure (TS 25.413 [4], subclause 8.19), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +Additionally, at basic Inter-3G\_MSC relocation and at subsequent Inter-3G\_MSC relocation (3GPP TS 23.009 [2]), if the 3G\_MSC that is the 3G\_MSC-A is not also the 3G\_MSC-T, the Location Reporting Control procedure (TS 25.413 [4] subclause 8.19) is applied on the E-interface with the following conditions: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-T acts as the RNS. + +## 5.10 Location Report + +For the Location Report procedure (TS 25.413 [4], subclause 8.20), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.11 Direct Transfer + +For the Direct Transfer procedure (TS 25.413 [4], subclause 8.23), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.12 Error Indication + +For the Error Indication procedure (TS 25.413 [4], subclause 8.27), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.13 CN Deactivate Trace + +For the CN Deactivate Trace procedure procedure (TS 25.413 [4], subclause 8.28), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.14 Common ID + +For the Common ID procedure (TS 25.413 [4], subclause 8.16), the involved 3G MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.15 Location Related Data + +For the Location Related Data procedure (TS 25.413 [4], subclause 8.31), the involved 3G\_MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.16 UE Specific Information + +For the UE Specific Information procedure (TS 25.413 [4], subclause 8.33), the involved 3G MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +## 5.17 RAB Modification Request + +For the RAB Modification Request procedure (TS 25.413 [4], subclause 8.30), the involved 3G MSCs shall act according to the following: + +- the 3G\_MSC-A acts as the 3G\_MSC; +- the 3G\_MSC-I acts as the RNS. + +# --- 6 RANAP messages transferred on the E-interface + +The list given below shows the RANAP messages, defined in TS 25.413 [4] subclause 9.1(tabular format) and 9.3 (ASN.1 notation) that are transferred on the E-interface. + +| | | +|-------------------------|------------------------| +| RAB ASSIGNMENT REQUEST | (3G_MSC-A -> 3G_MSC-I) | +| RAB ASSIGNMENT RESPONSE | (3G_MSC-I -> 3G_MSC-A) | + +| | | +|------------------------------------|-------------------------------------------------| +| RAB RELEASE REQUEST | (3G_MSC-I -> 3G_MSC-A) | +| IU RELEASE REQUEST | (3G_MSC-I -> 3G_MSC-A and 3G_MSC-T -> 3G_MSC-A) | +| * RELOCATION REQUEST | (3G_MSC-A -> 3G_MSC-T and 3G_MSC-I -> 3G_MSC-A) | +| * RELOCATION REQUEST ACKNOWLEDGE | (3G_MSC-T -> 3G_MSC-A and 3G_MSC-A -> 3G_MSC-I) | +| * RELOCATION DETECT | (3G_MSC-T -> 3G_MSC-A) | +| * RELOCATION COMPLETE | (3G_MSC-T -> 3G_MSC-A) | +| * RELOCATION FAILURE | (3G_MSC-T -> 3G_MSC-A and 3G_MSC-A -> 3G_MSC-I) | +| * RELOCATION CANCEL | (3G_MSC-I -> 3G_MSC-A) | +| * RELOCATION CANCEL ACKNOWLEDGE | (3G_MSC-A -> 3G_MSC-I) | +| # CN INVOKE TRACE | (3G_MSC-A -> 3G_MSC-I and 3G_MSC-A -> 3G_MSC-T) | +| SECURITY MODE COMMAND | (3G_MSC-A -> 3G_MSC-I) | +| SECURITY MODE COMPLETE | (3G_MSC-I -> 3G_MSC-A) | +| SECURITY MODE REJECT | (3G_MSC-I -> 3G_MSC-A) | +| LOCATION REPORTING CONTROL | (3G_MSC-A -> 3G_MSC-I and 3G_MSC-A -> 3G_MSC-T) | +| LOCATION REPORT | (3G_MSC-I -> 3G_MSC-A) | +| DIRECT TRANSFER | (3G_MSC-A -> 3G_MSC-I and 3G_MSC-I -> 3G_MSC-A) | +| ERROR INDICATION | (3G_MSC-A -> 3G_MSC-I and 3G_MSC-I -> 3G_MSC-A) | +| # CN DEACTIVATE TRACE | (3G_MSC-A -> 3G_MSC-I) | +| COMMON ID | (3G_MSC-A -> 3G_MSC-I) | +| LOCATION RELATED DATA REQUEST | (3G_MSC-A -> 3G_MSC-I) | +| LOCATION RELATED DATA RESPONSE | (3G_MSC-I -> 3G_MSC-A) | +| LOCATION RELATED DATA FAILURE | (3G_MSC-I -> 3G_MSC-A) | +| UE SPECIFIC INFORMATION INDICATION | (3G_MSC-A -> 3G_MSC-I) | +| RAB MODIFY REQUEST | (3G_MSC-I -> 3G_MSC-A) | + +All other RANAP messages shall be considered as non-existent on the E-interface. + +Some of the messages above are qualified by \* or #. This indicates whether the message, when sent on the E interface, is considered as: + +- relocation related message (\*); or +- trace related message (#). + +# --- 7 Exceptions for RANAP message contents and information element coding when transferred on the E-interface + +## 7.1 Message Contents + +For the applicable RANAP messages transferred on the E-interface the following exceptions to the descriptions in TS 25.413 [4] are valid: + +### RAB ASSIGNMENT REQUEST message + +- Transport Layer Address IE: + - if received, this IE shall be ignored; +- Iu Transport Association IE: + - if received, this IE shall be ignored; +- UP Mode Versions IE: + - the information given within this IE is only useful in case of TrFO. + +### RELOCATION REQUEST message + +- Transport Layer Address IE: + - if received, this IE shall be ignored; +- Iu Transport Association IE: + - if received, this IE shall be ignored; +- UP Mode Versions IE: + - the information given within this IE is only useful in case of TrFO; +- Iu Signalling Connection Identifier IE: + - if received, this IE shall be ignored; +- Global CN ID IE: + - if received, this IE shall be ignored. + +# --- 8 RANAP message error handling when transferred on the E-interface + +The RANAP error handling (TS 25.413 [4], clause 10) is applicable. The handling of faults concerning the use of SCCP is not applicable. + +The RANAP error messages sent on the E-interface shall only be sent as response to RANAP messages received on the same interface. + +# Annex A (informative): Change history + +| Change history | | | | | | +|----------------|---------|------------|-----------|-------------|--------------------------------------------------------| +| TSG RAN# | Version | CR | Tdoc RAN | New Version | Subject/Comment | +| RAN_08 | 2.0.0 | - | RP-000258 | 3.0.0 | Approved at TSG RAN #8 and placed under Change Control | +| RAN_10 | 3.0.0 | 001
002 | RP-000634 | 3.1.0 | Approved at TSG RAN #10 | + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|--------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 03/2001 | 11 | - | - | - | Approved at TSG RAN #11 and placed under Change Control | - | 4.0.0 | +| 09/2001 | 13 | RP-010590 | 004 | - | Iu Signalling Connection identifier on E-i/f | 4.0.0 | 4.1.0 | +| 03/2002 | 15 | - | - | - | Approved at TSG RAN #15 and placed under Change Control | 4.1.0 | 5.0.0 | +| 06/2002 | 16 | RP-020416 | 007 | - | Location Related Data procedure missing | 5.0.0 | 5.1.0 | +| 12/2002 | 18 | RP-020755 | 010 | 1 | Explicit indication of relocation related messages | 5.1.0 | 5.2.0 | +| 03/2003 | 19 | RP-030079 | 013 | 1 | Corrections to the list of RANAP messages transferred on the E-interface | 5.2.0 | 5.3.0 | +| 12/2003 | 22 | - | - | - | Introduction of Release 6 specification | 5.3.0 | 6.0.0 | +| 06/2004 | 24 | RP-040177 | 015 | - | PUESBINE support over E-interface | 6.0.0 | 6.1.0 | +| 03/2005 | 27 | RP-050120 | 017 | - | Full RANAP support of network initiated SCUDIF | 6.1.0 | 6.2.0 | +| 03/2006 | 31 | - | - | - | Introduction of Release 7 specification | 6.2.0 | 7.0.0 | +| 06/2003 | 32 | RP-060278 | 019 | - | Iu-Flex for Inter-3G MSC Relocation | 7.0.0 | 7.1.0 | +| 12/2008 | 42 | - | - | - | Upgrade to Release 8 without technical change | 7.1.0 | 8.0.0 | +| 12/2009 | - | - | - | - | Upgrade to Release 9 without technical change | 8.0.0 | 9.0.0 | +| 03/2011 | - | - | - | - | Upgrade to Release 10 without technical change | 9.0.0 | 10.0.0 | +| 06/2011 | 52 | RP-110684 | 020 | - | Corrections of References | 10.0.0 | 10.1.0 | +| 09/2012 | - | - | - | - | Update to Rel-11 version (MCC) | 10.1.0 | 11.0.0 | +| 09/2014 | - | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 12/2015 | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | SA#75 | - | - | - | - | Promotion to Release 14 without technical change | 14.0.0 | +| 2018-07 | SA#80 | - | - | - | - | Promotion to Release 15 without technical change | 15.0.0 | +| 2020-07 | SA#88-e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/29_series/29109/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/Rel-16/29_series/29109/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f414631d7167c3c7c7ee53a4bafce7b467a8454 --- /dev/null +++ b/marked/Rel-16/29_series/29109/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d867cd64906959ed2c6733982edcb7f53b6ae56d726b89c8b25e3340c91cacf0 +size 96610 diff --git a/marked/Rel-16/29_series/29109/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Rel-16/29_series/29109/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39266067bb1c70f64c646ebd61e4633ce680b410 --- /dev/null +++ b/marked/Rel-16/29_series/29109/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc0058da931c418e043ec176678177a9b93ddea13bbedfb3fb118d42eaac3580 +size 11134 diff --git a/marked/Rel-16/29_series/29109/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/marked/Rel-16/29_series/29109/5793a44ffdadd039928e2f9fe6daae06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46fd1d4f886cf335c4020107db7facd80be7917f --- /dev/null +++ b/marked/Rel-16/29_series/29109/5793a44ffdadd039928e2f9fe6daae06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d457b6f318177606e532248ad5f4ab0d8f4322672a44f10ea31299da605e21b8 +size 34713 diff --git a/marked/Rel-16/29_series/29109/5dfc130b129ace4df375839020a5700d_img.jpg b/marked/Rel-16/29_series/29109/5dfc130b129ace4df375839020a5700d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc3b05162e62879aa64e3dd50d478aad8b95717d --- /dev/null +++ b/marked/Rel-16/29_series/29109/5dfc130b129ace4df375839020a5700d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87ceffa3a558289c81dbf9df571b964f9f10c291963c35f6cb3cbb276387bb98 +size 38807 diff --git a/marked/Rel-16/29_series/29109/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/marked/Rel-16/29_series/29109/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b06f04a27c07547b37c3393306a35294db48fc8e --- /dev/null +++ b/marked/Rel-16/29_series/29109/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24b6aaecd9ac3945efb46e8c2cb9f3770b51dd2f964a7f40dca77e9edff81b73 +size 9062 diff --git a/marked/Rel-16/29_series/29109/6f31cdb576d2f15c35c3f266e5f59211_img.jpg b/marked/Rel-16/29_series/29109/6f31cdb576d2f15c35c3f266e5f59211_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ca6a80abb06ed6e199a88f396d4e0f85777db97 --- /dev/null +++ b/marked/Rel-16/29_series/29109/6f31cdb576d2f15c35c3f266e5f59211_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b64bf46816b524e86fef7ff52b1a6d905b85d048b82a3be5aaf5b11692351b5 +size 120866 diff --git a/marked/Rel-16/29_series/29109/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/29_series/29109/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2337bdb1900264c2fef20489e5ae81ff73abb7a8 --- /dev/null +++ b/marked/Rel-16/29_series/29109/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9519fffd6f241e3e0356e1070fba08f4a32e3d73387c83338bf0a0a75d21661f +size 86996 diff --git a/marked/Rel-16/29_series/29109/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/29_series/29109/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d67b58404280a0282e98d9c8b01ab2957f1518f --- /dev/null +++ b/marked/Rel-16/29_series/29109/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3322f4d4dd28c1c05ac5fb0006889f561a4777c65b661e681621346e811156e5 +size 106352 diff --git a/marked/Rel-16/29_series/29109/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-16/29_series/29109/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07bd57b69731f791c63c99f1864ecf4c7717d2e0 --- /dev/null +++ b/marked/Rel-16/29_series/29109/997233d405f0d4b89ddeb7683e047f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f185e4c6976da69a1d72e5774a3eb89cf8f969edd45366129e20f6ba0f9d11b +size 95883 diff --git a/marked/Rel-16/29_series/29109/9a159e2112eac7be06bdb97e84a0c49a_img.jpg b/marked/Rel-16/29_series/29109/9a159e2112eac7be06bdb97e84a0c49a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f31f06cc66716ea4094180f9e200256930becdb --- /dev/null +++ b/marked/Rel-16/29_series/29109/9a159e2112eac7be06bdb97e84a0c49a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00c13d3886a761c57ba7d60aeb220bdab02df1b113212911eecc96d5530f202d +size 75327 diff --git a/marked/Rel-16/29_series/29109/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/29_series/29109/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05060b672c98558dd4c0c6c2c5ba3f7bc5160876 --- /dev/null +++ b/marked/Rel-16/29_series/29109/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad3b11a788b52090d6cf81e59a9cfe3a98ddfc59aa4adc615c4e7dbf6436223a +size 90937 diff --git a/marked/Rel-16/29_series/29109/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/Rel-16/29_series/29109/ddc7460821484f1ae2835c67955c554c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02be253defa71671afa5a0de8f1d108172b603c2 --- /dev/null +++ b/marked/Rel-16/29_series/29109/ddc7460821484f1ae2835c67955c554c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:871b19d7d4fa0a7bc71faf4689119c1cf751184337400752d4d895056bd0351c +size 11115 diff --git a/marked/Rel-16/29_series/29109/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/29_series/29109/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f64c7fedb874935338ae9b3b4baf3b3265182d7 --- /dev/null +++ b/marked/Rel-16/29_series/29109/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3857a4a734d71f27aaa728ccab908e6fa36594a2765112a096cb08bc504154b6 +size 77131 diff --git a/marked/Rel-16/29_series/29109/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/29_series/29109/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e5777e66166b558175f96c5a4141f11e71421cf --- /dev/null +++ b/marked/Rel-16/29_series/29109/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94bbea7990a2d001f82bc26a5bb470907440b424f2cf8049b1826ec435976afc +size 41508 diff --git a/marked/Rel-16/29_series/29109/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/marked/Rel-16/29_series/29109/e9d825d87c5f85c8dba0664eace96ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2d4eb163ecbf288df59298dde3913c63a5d5654 --- /dev/null +++ b/marked/Rel-16/29_series/29109/e9d825d87c5f85c8dba0664eace96ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63126b2daa9cf3a22242393d3b1e2785b1fa6b7c7382817b8b101d57250e43e3 +size 14677 diff --git a/marked/Rel-16/29_series/29109/f6d72d7c790e7f585532140f3971639a_img.jpg b/marked/Rel-16/29_series/29109/f6d72d7c790e7f585532140f3971639a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..801ef061164b5b66fef37b9fd2ecf33075712929 --- /dev/null +++ b/marked/Rel-16/29_series/29109/f6d72d7c790e7f585532140f3971639a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a55e7ff7d11d1cad5f9caec530cbb31ecf7efa5d49947fb6d6823cc6aa848178 +size 61681 diff --git a/marked/Rel-16/29_series/29109/raw.md b/marked/Rel-16/29_series/29109/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0fb250087e05498b6d10261520645fcfc438a9d9 --- /dev/null +++ b/marked/Rel-16/29_series/29109/raw.md @@ -0,0 +1,3517 @@ + + + + + + +# Contents + +| | | | +|----------|-------------------------------------------------------------------------|----| +| 1 | Scope..... | 5 | +| 2 | References..... | 9 | +| 3 | Definitions, symbols and abbreviations ..... | 11 | +| 3.1 | Definitions ..... | 11 | +| 3.2 | Symbols..... | 11 | +| 3.3 | Abbreviations ..... | 12 | +| 4 | GBA Bootstrapping Zh interface and Zh' interface ..... | 13 | +| 4.1 | Generic bootstrapping network architecture ..... | 13 | +| 4.2 | Protocol Zh between BSF and HSS ..... | 13 | +| 4.3 | Protocol Zh' between BSF and HLR..... | 18 | +| 4.3.1 | Public to Private Identity Resolution over Zh between BSF and HLR ..... | 19 | +| 5 | GAA Application Zn and Zpn interfaces..... | 21 | +| 5.1 | Applications' network architecture ..... | 21 | +| 5.2 | Protocol Zn between NAF and BSF based on Diameter..... | 22 | +| 5.3 | Protocol Zn between NAF and BSF based on Web Services ..... | 25 | +| 5.4 | Protocol Zpn between NAF and BSF based on Diameter..... | 28 | +| 5.5 | Protocol Zpn between NAF and BSF based on Web Services ..... | 32 | +| 6 | Diameter application for Zh, Zn and Zpn interfaces..... | 35 | +| 6.0 | Introduction ..... | 35 | +| 6.1 | Command-Code values ..... | 35 | +| 6.2 | Result-Code AVP values..... | 35 | +| 6.2.1 | Success ..... | 35 | +| 6.2.2 | Permanent failures ..... | 35 | +| 6.2.2.1 | DIAMETER_ERROR_IDENTITY_UNKNOWN (5401) ..... | 35 | +| 6.2.2.2 | DIAMETER_ERROR_NOT_AUTHORIZED (5402)..... | 36 | +| 6.2.2.3 | DIAMETER_ERROR_TRANSACTION_IDENTIFIER_INVALID (5403) ..... | 36 | +| 6.2.2.4 | Void ..... | 36 | +| 6.2.2.5 | Void ..... | 36 | +| 6.2.2.6 | Void ..... | 36 | +| 6.2.2.7 | Void ..... | 36 | +| 6.3 | AVPs ..... | 37 | +| 6.3.1 | Common AVPs..... | 38 | +| 6.3.1.1 | GBA-UserSecSettings AVP ..... | 38 | +| 6.3.1.2 | Transaction-Identifier AVP ..... | 38 | +| 6.3.1.3 | NAF-Id..... | 38 | +| 6.3.1.4 | GAA-Service-Identifier AVP ..... | 38 | +| 6.3.1.5 | Key-ExpiryTime AVP..... | 38 | +| 6.3.1.6 | ME-Key-Material AVP..... | 38 | +| 6.3.1.7 | UICC-Key-Material AVP ..... | 38 | +| 6.3.1.8 | GBA_U-Awareness-Indicator ..... | 38 | +| 6.3.1.9 | BootstrapInfoCreationTime AVP ..... | 39 | +| 6.3.1.10 | GUSS-Timestamp AVP..... | 39 | +| 6.3.1.11 | GBA-Type ..... | 39 | +| 6.3.1.12 | UE-Id ..... | 39 | +| 6.3.1.13 | UE-Id-Type ..... | 39 | +| 6.3.1.14 | UICC-App-Label ..... | 39 | +| 6.3.1.15 | UICC-ME..... | 39 | +| 6.3.1.16 | Requested-Key-Lifetime..... | 40 | +| 6.3.1.17 | Private-Identity-Request ..... | 40 | +| 6.3.1.18 | GBA-Push-Info ..... | 40 | +| 6.3.1.19 | NAF-SA-Identifier ..... | 40 | +| 6.3.1.20 | Security-Feature-Request..... | 40 | +| 6.3.1.21 | Security-Feature-Response ..... | 40 | +| 6.4 | User identity to HSS resolution..... | 40 | + +| | | | +|-------------------------------|-----------------------------------------------------------------|-----------| +| 7 | Use of namespaces..... | 42 | +| 7.1 | AVP codes..... | 42 | +| 7.2 | Experimental-Result-Code AVP values..... | 42 | +| 7.3 | Command Code values..... | 42 | +| Annex A (normative): | GBA-UserSecSettings XML definition..... | 43 | +| Annex B (normative): | GAA Service Type Codes ..... | 48 | +| Annex C (normative): | GAA Authorization flag codes ..... | 48 | +| Annex D (normative): | Web Services Definition for Zn interface..... | 49 | +| Annex E (informative): | Liberty authentication context definitions for GBA ..... | 50 | +| E.1 | Introduction..... | 50 | +| E.2 | GBA Authentication context statement data model..... | 50 | +| E.3 | GBA authentication context statement schema ..... | 51 | +| E.4 | GBA authentication context classes..... | 52 | +| E.4.1 | GBAOneFactorUnregistered..... | 52 | +| E.4.1.1 | Associated 3GPP URI ..... | 52 | +| E.4.1.2 | Class schema ..... | 53 | +| E.4.2 | GBATwoFactorUnregistered ..... | 53 | +| E.4.2.1 | Associated 3GPP URI ..... | 53 | +| E.4.2.2 | Class schema ..... | 53 | +| E.4.3 | GBAOneFactorContract..... | 54 | +| E.4.3.1 | Associated 3GPP URI ..... | 54 | +| E.4.3.2 | Class schema ..... | 54 | +| E.4.4 | GBATwoFactorContract..... | 55 | +| E.4.4.1 | Associated 3GPP URI ..... | 55 | +| E.4.4.2 | Class schema ..... | 55 | +| Annex F (informative): | SAML authentication context definitions for GBA ..... | 56 | +| F.1 | Introduction..... | 56 | +| F.2 | GBA authentication context declaration data model ..... | 56 | +| F.3 | GBA authentication context declaration types..... | 57 | +| F.4 | GBA authentication context declaration classes..... | 58 | +| F.4.1 | GBAOneFactorUnregistered..... | 58 | +| F.4.1.1 | Associated 3GPP URI ..... | 58 | +| F.4.1.2 | Class schema ..... | 58 | +| F.4.2 | GBATwoFactorUnregistered ..... | 61 | +| F.4.2.1 | Associated 3GPP URI ..... | 61 | +| F.4.2.2 | Class schema ..... | 61 | +| F.4.3 | GBAOneFactorContract..... | 63 | +| F.4.3.1 | Associated 3GPP URI ..... | 63 | +| F.4.3.2 | Class schema ..... | 63 | +| F.4.4 | GBATwoFactorContract..... | 65 | +| F.4.4.1 | Associated 3GPP URI ..... | 65 | +| F.4.4.2 | Class schema ..... | 65 | +| Annex G (normative): | Web Services Definition for Zpn interface ..... | 68 | +| Annex H (informative): | Change history..... | 69 | + +# --- 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 stage 3 specification defines the Diameter based implementation for bootstrapping Zh interface (BSF-HSS) and Dz interface (BSF-SLF) for HSS resolution for the BSF, the MAP based implementation for bootstrapping Zh' interface (BSF-HLR) and GAA Application Zn interface (BSF-NAF) in Generic Authentication Architecture (GAA). This specification also defines the Web Services based implementation for GAA Application Zn reference point (BSF-NAF). The definition contains procedures, message contents and coding. The procedures for bootstrapping and usage of bootstrapped security association are defined in 3GPP TS 33.220 [5]. + +The present document also specifies the Diameter and Web Services based implementation for the GAA Application Push Function Zpn reference point (BSF-NAF). The procedures for bootstrapping are defined in 3GPP TS 33.223 [23]. + +This specification is a part of the Generic Authentication Architecture (GAA) specification series. + +The diameter based implementation for the Zh interface is based on re-usage of Cx interface Multimedia-Auth-Request/Answer messages originally between CSCF and HSS. These messages are defined in 3GPP TS 29.229 [3]. The 3GPP IMS mobility management uses the same definitions between CSCF and HSS. The present document defines how the defined messages are used with the bootstrapping and GAA application procedures (e.g. subscriber certificates) and the application logic that is needed in GAA network elements (BSF, HSS, and NAF). + +Figure 1.1 depicts the relationships of these specifications to the other specifications for the Diameter based implementations. + + + +| | | | | +|----------------|--------------------------------------------------|---------|------------------| +| 3GPP | GAA System Description TR 33.919 | Stage 2 | IMS TS 23.228 | +| | GAA GBA TS 33.220
GBA Push Function TS 33.223 | | IMS MM TS 29.228 | +| | GAA Zh, Zn and Zpn TS 29.109 | Stage 3 | | +| IETF with 3GPP | IMS Cx Diameter message definitions TS 29.229 | | | +| IETF | Diameter Base Protocol RFC 3588 | | | +| | SCTP | | | +| | IP | | | + +Diagram showing the relationships between various specifications for Diameter-based implementations, categorized by 3GPP and IETF standards. + +**Figure 1.1: Relationships to other specifications** + +Figure 1.2 provides an informal overall quick introduction to the whole signalling procedures in GAA system. The important identifiers are marked **bold** and optional data items are *italicised*. The Ub and Ua interfaces, not defined in this TS, are simplified. + +NOTE: The Zh' interface (BSF-HLR) is not represented in this figure. + + + +The diagram illustrates the signalling procedure in the GAA system, organized into two domains: the GAA Security Domain (top) and the GAA Application Domain (bottom). The entities involved are the UE (User Equipment), BSF (Bootstrap Function), SLF (SLF Function), HSS (Home Subscriber Server), and NAF (Network Application Function), which contains an Auth.Proxy and Appl.Spec. Servers. + +The procedure consists of the following steps: + +- (1) The UE sends an **IMPI** to the BSF via the **Ub** interface. +- (2) The BSF sends an **IMPI** to the SLF via the **Dz** interface. +- (3) The SLF sends an **AV**, **IMPI**, and **GUSS(USS\*(UID\*))** to the BSF via the **Zh** interface. +- (4) The BSF sends a **B-TID** and **Key-Lifetime** to the UE via the **Ub** interface. +- (5) The UE sends a **B-TID** and **UID** to the NAF via the **Ua** interface. +- (6) The NAF sends a **B-TID**, **GSID\***, and **NAF-Id** to the BSF via the **Zn** interface. +- (7) The BSF sends **USS\*(UID\*)**, **Ks\_(ext)\_NAF**, **Key-Expirytime**, **BootstrapInfoCreationTime**, **Ks\_int\_NAF**, and **IMPI** to the HSS via the **Zn** interface. +- (8) The NAF sends a response to the UE via the **Ua** interface. +- (9) if needed: **Sh**, **GUP**, etc. are sent from the HSS to the NAF via the **Ua** interface. + +**Bold**=Important Identity. *Italic*=optional items. Ub and Ua interfaces are simplified. + +Diagram of the whole signalling procedure in GAA system. The diagram is divided into two domains: GAA Security Domain (top, green background) and GAA Application Domain (bottom, blue background). Entities involved are SLF, BSF, UE, HSS, and NAF (containing Auth.Proxy and Appl.Spec. Servers). The procedure consists of 9 steps: (1) UE sends IMPI to BSF via Ub; (2) BSF sends IMPI to SLF via Dz; (3) SLF sends AV, IMPI, and GUSS(USS\*(UID\*)) to BSF via Zh; (4) BSF sends B-TID and Key-Lifetime to UE via Ub; (5) UE sends B-TID and UID to NAF via Ua; (6) NAF sends B-TID, GSID\*, and NAF-Id to BSF via Zn; (7) BSF sends USS\*(UID\*), Ks\_(ext)\_NAF, Key-Expirytime, BootstrapInfoCreationTime, Ks\_int\_NAF, and IMPI to HSS via Zn; (8) NAF sends a response to UE via Ua; (9) HSS sends Sh, GUP, etc. to NAF if needed via Ua. + +**Figure 1.2: The whole signalling procedure in GAA system** + +Figure 1.3 provides an informal overall quick introduction to the whole signalling procedures in GAA Push Function. The important identifiers are marked bold and optional data items are italicised. The Ua and Upa interfaces, not defined in this TS, are simplified. + + + +The diagram illustrates the signalling procedure for GAA Bootstrapping Push Function across two domains: **GAA Security Domain** (top, green background) and **GAA Application Domain** (bottom, light blue background). + +**Entities:** + +- UE (User Equipment):** Located in the GAA Application Domain. +- SLF (Subscription Locator Function):** Located in the GAA Security Domain. +- BSF (Bootstrap Function):** Located in the GAA Security Domain. +- HSS (Home Subscriber Server):** Located in the GAA Security Domain. +- NAF (Network Application Function):** Located in the GAA Application Domain, connected to **Appl.Spec. Servers**. + +**Signalling Steps and Interfaces:** + +- (1)** UE to NAF: **UE-Id (Type)**, **P-TID**, **GSID\***, **NAF-Id**. +- (2)** BSF to HSS: **IMPI/IMPU**. +- (3)** HSS to BSF: **Zh** interface, carrying *AV, IMPI*, *GUSS(USS\*(UID\*))*. +- (4)** BSF to NAF: **Zpn** interface, carrying **GPI**, *USS\*(UID\*)*, **Ks\_(ext)\_NAF**, Key-Expirytime, BootstrapInfoCreationTime, *Ks\_int\_NAF*, **IMPI**. +- (5)** NAF to UE: **Upa** interface, carrying **GPI**. + +**Other Interfaces:** + +- Dz**: Interface between SLF and BSF, carrying **IMPI/IMPU**. + +Signalling procedure in GAA Bootstrapping Push Function diagram showing interactions between UE, SLF, BSF, HSS, and NAF across GAA Security and Application domains. + +**Bold**=Important Identity. *Italic*=optional items. Ub and Ua interfaces are simplified. + +**Figure 1.3: Signalling procedure in GAA Bootstrapping Push Function** + +# 2 References + +The following documents contain provisions that, 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 29.228: "IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents". +- [3] 3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol". +- [4] 3GPP TR 33.919 "Generic Authentication Architecture (GAA); System Description". +- [5] 3GPP TS 33.220 "Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture". +- [6] 3GPP TS 33.221 "Generic Authentication Architecture (GAA); Support for Subscriber Certificates". +- [7] 3GPP TS 24.109: "Bootstrapping interface (Ub) and Network application function interface (Ua);Protocol details". +- [8] 3GPP TS 29.230: "Diameter applications; 3GPP specific codes and identifiers" +- [9] IETF RFC 3589: "Diameter Command Codes for Third Generation Partnership Project (3GPP)". +- [10] 3GPP TS 23.008: "Organisation of subscriber data" +- [11] 3GPP TS 33.222: "Generic Authentication Architecture (GAA); Access to network application functions using secure hypertext transfer protocol (HTTPS)". +- [12] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2" +- [13] W3C: "Web Services Activity",
BSF is hosted in a network element under the control of an MNO. | +| B-TID | Bootstrapping Transaction Identifier | +| CA | Certificate Authority | +| CK | Confidential Key | +| FQDN | Full Qualified Domain Name in URI (e.g. http://FQDN:80 ) | +| GAA | Generic Authentication Architecture | +| GBA | Generic Bootstrapping Architecture | +| GPI | GBA Push Information | +| GSID | GAA Service Identifier | +| GUSS | GBA User Security Settings | +| HSS | Home Subscriber System | +| IK | Integrity Key | +| IMPI | IP Multimedia Private Identity | +| IMPU | IP Multimedia Public Identity | +| Ks | Key Material | +| Ks_ext_NAF | MEbased key for a specific NAF | +| Ks_int_NAF | UICC based key for a specific NAF | +| ME | Mobile Equipment | +| MNO | Mobile network operator | +| NAF | Operator-controlled network application function functionality.
NAF is hosted in a network element under the control of an MNO. | +| P-TID | Push Temporary Identifier | +| RAND | Random challenge in authentication | +| REQ | In Diameter header indicates that the message is a Request. | +| SCTP | Stream Control Transmission Protocol | +| SLF | Subscription Location Function | +| SSC | Subscriber Certificate Procedure | +| Ua | UE-NAF interface for GAA applications | +| Ub | UE-BSF interface for bootstrapping | +| UE | User Equipment | +| USS | User Security Settings (a part of GUSS) | +| XRES | Expected response in authentication | +| Zh | BSF-HSS interface for bootstrapping procedure | +| Zh' | BSF-HLR interface for bootstrapping procedure | +| Zn | BSF-NAF interface for GAA applications | +| Zpn | BSF-NAF interface for GBA push. | + +# 4 GBA Bootstrapping Zh interface and Zh' interface + +## 4.1 Generic bootstrapping network architecture + +The network architecture of the Diameter based implementation for Bootstrapping procedure is presented in Figure 4.1-1. The interface Ub (bootstrapping) is defined in 3GPP TS 24.109 [7] and the interface Zh in this specification. + + + +``` + +graph LR + UE[UE] -- Ub --> BSF[BSF] + BSF -- Zh --> HSS[HSS] + +``` + +Figure 4.1-1: Network architecture of bootstrapping procedure. A diagram showing three entities: UE, BSF, and HSS. UE is connected to BSF via the Ub interface. BSF is connected to HSS via the Zh interface. + +**Figure 4.1-1: Network architecture of bootstrapping procedure** + +The generic bootstrapping network architecture for Bootstrapping Push procedures is presented in Figure 4.1-2. The interface Zpn is also defined in this specification. + + + +``` + +graph LR + UE[UE] -- Upa --> NAF[NAF] + NAF -- Zpn --> BSF[BSF] + BSF -- Zh --> HSS[HSS] + +``` + +Figure 4.1-2: Network architecture of bootstrapping push procedure. A diagram showing four entities: UE, NAF, BSF, and HSS. UE is connected to NAF via the Upa interface. NAF is connected to BSF via the Zpn interface. BSF is connected to HSS via the Zh interface. + +**Figure 4.1-2: Network architecture of bootstrapping push procedure** + +The protocol stack of the Zh interface in Bootstrapping procedure is presented in Figure 4.2. The Diameter Base protocol is defined in IETF RFC 6733 [33] and the Diameter application in 3GPP TS 29.229 [3]. The requirements for Zh interface are defined in 3GPP TS 33.220 [5] and 3GPP TS 33.223 [23]. + + + +| BSF | HSS | +|-----------------------------|-----------------------------| +| Zh application logic in BSF | Zh application logic in HSS | +| Diameter application | Diameter application | +| Diameter Base Protocol | Diameter Base Protocol | +| SCTP | SCTP | +| IP | IP | + +The two IP layers are connected by the Zh interface. + +Figure 4.2: Protocol stack of Zh interface. A diagram showing the protocol stacks for BSF and HSS. Both stacks consist of Zh application logic, Diameter application, Diameter Base Protocol, SCTP, and IP. The stacks are connected by the Zh interface. + +**Figure 4.2: Protocol stack of Zh interface** + +The MAP based Bootstrapping Zh' interface is defined in the section 4.3. + +## 4.2 Protocol Zh between BSF and HSS + +The requirements for Zh interface are defined in 3GPP TS 33.220 [5] and 3GPP TS 33.223 [23]. + +The Bootstrapping Zh interface performs the retrieval of an authentication vector and possibly GBA User Security Settings from the HSS. + +The overall Bootstrapping procedure is depicted in Figure 4.3. The basic procedure is: + +- A UE starts the bootstrapping procedure by protocol Ub with a BSF giving the IMPI of the user (see 3GPP TS 24.109 [7]). +- The BSF starts protocol Zh with user's HSS + +- The BSF requests user's authentication vector and GBA User Security Settings (GUSS) corresponding to the IMPI. If the authentication scheme is to use SIP Digest credentials, the BSF shall indicate this in the request. +- The HSS supplies to the BSF the requested authentication vector and GUSS (if applicable, cf. 3GPP TS 33.220 [5]). The HSS supplies the requested authentication vector relating to SIP Digest only if explicitly indicated in the request. + +NOTE 1: If there is more than one HSS deployed within the network, the BSF may have to contact the SLF using the Dz interface prior to sending the request for information to the HSS (see section 6.4). + +C) The BSF continues the protocol Ub with the UE (see 3GPP TS 24.109 [7]). + + + +``` + +sequenceDiagram + participant UE + participant BSF + participant HSS + + Note over UE, BSF: Ub + Note over BSF, HSS: Zh + + Note left of UE: If non-IMS subriber, +generates IMPI from IMSI + UE->>BSF: Bootstrapping-Request (IMPI) + BSF->>HSS: 1. Multimedia-Auth-Request ( IMPI ) + Note right of HSS: 2. HSS derives +Authentication data and +fetches GUSS for IMPI. + HSS->>BSF: 3. Multimedia-Auth-Answer +(Authentication data, +GAA-UserSecSettings) + Note left of BSF: 4. BSF stores bootstrapping +information tuple for IMPI. + BSF->>UE: Bootstrapping-Answer +(realm,nonce,algorithm) + Note over UE, BSF: The rest of the Boostrapping procedure + +``` + +The diagram illustrates the GBA bootstrapping procedure involving three main entities: UE (User Equipment), BSF (Bootstrap Server), and HSS (Home Subscriber Server). The sequence of messages is as follows: + + +- The UE sends a **Bootstrapping-Request (IMPI)** to the BSF over the **Ub** interface. A note indicates that if the UE is a non-IMS subriber, it generates the IMPI from the IMSI. +- The BSF sends a **1. Multimedia-Auth-Request ( IMPI )** to the HSS over the **Zh** interface. +- The HSS performs an internal step: **2. HSS derives Authentication data and fetches GUSS for IMPI.** +- The HSS sends a **3. Multimedia-Auth-Answer (Authentication data, GAA-UserSecSettings)** back to the BSF over the **Zh** interface. +- The BSF performs an internal step: **4. BSF stores bootstrapping information tuple for IMPI.** +- The BSF sends a **Bootstrapping-Answer (realm,nonce,algorithm)** back to the UE over the **Ub** interface. +- A final note indicates: **The rest of the Boostrapping procedure**. + +Sequence diagram of the GBA bootstrapping procedure between UE, BSF, and HSS. + +Figure 4.3: The GBA bootstrapping procedure + +The overall Bootstrapping Push procedure is depicted in Figure 4.4. The Push procedure shall not apply with an authentication scheme using SIP Digest credentials. The Push procedure is: + +A) A NAF sends a bootstrapping push request to the BSF via Zpn interface including the IMPI or IMPU of the user (see section 5). + +B) The BSF starts protocol Zh with user's HSS + +- The BSF requests user's authentication vector and GBA User Security Settings (GUSS) corresponding to the IMPI or IMPU. +- The HSS supplies to the BSF the requested authentication vector and GUSS (if any). + +NOTE 2: If there is more than one HSS deployed within the network, the BSF may have to contact the SLF using the Dz interface prior to sending the request for information to the HSS (see section 6.4). + +C) The BSF continues the protocol Zpn with the NAF (see section 5). + +D) The NAF starts protocol Upa with the UE, as specified in 3GPP TS 24.109 [7]. + + + +``` + +sequenceDiagram + participant UE + participant NAF + participant BSF + participant HSS + Note right of NAF: Generate GPI Request + NAF->>BSF: GPI-Request (IMPI or IMPU, NAF-Id) + BSF->>HSS: 1. Multimedia-Auth-Request (IMPI or IMPU) + HSS->>BSF: 2. HSS generates AV and fetches GUSS for IMPI. + BSF->>HSS: 3. Multimedia-Auth-Answer (RAND, AUTN, XRES, CK, IK, GAA-UserSecSettings) + BSF->>NAF: 4. BSF generates GPI + NAF->>BSF: GPI-Response (GPI) + BSF->>UE: GPI Push + +``` + +Sequence diagram of the GBA bootstrapping Push procedure. Lifelines: UE, NAF, BSF, HSS. The process starts with NAF sending a 'Generate GPI Request' to BSF. BSF sends a 'GPI-Request (IMPI or IMPU, NAF-Id)' to HSS. HSS sends '1. Multimedia-Auth-Request (IMPI or IMPU)' to BSF. BSF sends '2. HSS generates AV and fetches GUSS for IMPI.' to HSS. HSS sends '3. Multimedia-Auth-Answer (RAND, AUTN, XRES, CK, IK, GAA-UserSecSettings)' to BSF. BSF sends '4. BSF generates GPI' to NAF. NAF sends 'GPI-Response (GPI)' to BSF. BSF sends 'GPI Push' to UE. + +**Figure 4.4: The GBA bootstrapping Push procedure** + +The steps of the bootstrapping procedure over Zh reference point in Figure 4.3 and Figure 4.4 are: + +### Step 1 + +The BSF shall send the following Bootstrapping-Request to the HSS in the format of Multimedia-Auth-Request (MAR) message. The content of the message is given below in the same format as in 3GPP TS 29.229 [3]. The curly brackets indicate mandatory AVPs. The square brackets indicate optional AVPs. The "address of" refers to the Fully Qualified Host Name (FQDN). + +``` + +
or
/xmb/v1.0/reports/{report-res-id} | +| | | Notification | /xmb/v1.0/notifications?query
or
/xmb/v1.0/notifications/{notification-res-id} | +| PUT | Replace | Service | /xmb/v1.0/services/{service-res-id} | +| | | Session | /xmb/v1.0/services/{service-res-id}/sessions/{session-res-id} | +| PATCH | Modify | Service | /xmb/v1.0/services/{service-res-id} | +| | | Session | /xmb/v1.0/services/{service-res-id}/sessions/{session-res-id} | +| DELETE | Delete | Service | /xmb/v1.0/services/{service-res-id} | +| | | Session | /xmb/v1.0/services/{service-res-id}/sessions/{session-res-id} | + +### 5.1.2 Error Handling + +The xMB API shall use the HTTP status codes to indicate any errors that might occur in the processing of operations on xMB resources. Unless defined otherwise, the HTTP status codes shall be interpreted as specified in IETF RFC 7231 [6]. API operations that are not successfully handled shall not leave the resource at an undefined state. The response should provide sufficient information for a human operator to understand and locate the error. + +API operations that do not follow the security procedures defined in section 7 shall be rejected without any impact on the resources. + +Errors may also happen during the content ingestion and shall be notified to the Content Provider in a timely manner depending on the severity of the error. + +### 5.1.3 xMB Entry Point Discovery + +The Content Provider shall be able to discover the entry point to the xMB interface by one of the following methods: + +- It is provided with the URL that serves as the entry point for the xMB-C interface; +- It acquires that entry point URL from DNS resolution of the following Fully Qualified Domain Name (FQDN): + +
Enumeration of Service Announcement Mode.
Additional service announcement modes may be added in the future.
- - "SACH": BM-SC performs the service announcement for the current service using the SACH channel (cf. Annex L.2, L3 of 3GPP TS 26.346 [3]).
- - "Content Provider": BM-SC provides the necessary service access information used by the Content Provider to create the service announcement information.
The Content Provider wishes to collect consumption reports for the service.
Reporting start and end time: The reporting period with start and end time.
Reporting interval: The interval for which the BM-SC is aggregate the statistics in seconds. (Data type: number; default value: 3600)
| | + +| | | | | | | | +|---------------------------------|--------|--|------|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | | | |Sample percentage: Percentage of users to collect reports from (Data type: number; default value: 10)
The presence of this object indicates the enabling of consumption reporting; if not present, it indicates the disabling of the consumption reporting.
| | +| push-notification-url | string | | None | “” |The Content Provider provides Notification URL over which it will receive notifications "pushed" by the BM-SC. The Notification procedure is described in subclause 5.3.6. of 3GPP TS 26.348 [33]
| | +| push-notification-configuration | string | | None | All |If the Content Provider enables push delivery of notifications, then the Content Provider may provide notification filters
This parameter contains a comma separated list of Classes it wishes to receive among the following options: Critical, Warning, Information, Service, Session, or All to get all types of notification.
The notification message shall be sent immediately to the Content Provider upon its availability.
| | + +NOTE: Properties marked with a supported feature are applicable as described in subclause 9. + +The service instance resource with the properties defined above can be found in Annex B. + +#### 5.2.1.2 API Operations + +##### 5.2.1.2.1 Introduction + +Services can be created, updated, or deleted at the BM-SC by the Content Provider, or the properties of a previously created service at the BM-SC may be obtained by the Content Provider, by invoking HTTP methods on the "service" instance resource or the "services" collection resource. + +##### 5.2.1.2.2 Service Creation + +POST /xmb/v1.0/services + +To create a service, the Content Provider shall use the HTTP POST method on the "services" collection resource as follows: + +- the request URI with the "path" part is set to: "/xmb/v1.0/services". +- the Host field is set to the address of the BM-SC + +The Content Provider shall follow the procedures defined in subclause 9 to advertise support of any feature. + +The content body of the POST request shall be empty. Upon receipt of the HTTP POST request from the Content Provider to create a service, the BM-SC will check whether the Content Provider is authenticated and authorized to create services as described in clause 7. If the authorization fails, the BM-SC shall send a 401 message as described in Table 5.2.1.2.2-1. If the authorization is successful, the BM-SC shall create a service with default service property values as described in subclause 5.2.1.1. Upon successful creation of a service, the BM-SC shall respond to the Content Provider with a 201 message indicating that the service is successfully created along with the service resource identifier of the service resource. The service resource identifier is the identifier that uniquely identifies the service. When the Content Provider receives the service resource identifier, it shall use this identifier in subsequent requests to the BM-SC + +to refer to this service. Alternatively, if the creation of service failed, the BM-SC shall send a 403 message to the Content Provider. + +Both the Content Provider and BM-SC shall remember the negotiated features for the lifetime of the service. + +The possible response messages from the BM-SC, depending on whether the POST request is successful or unsuccessful, are shown in Table 5.2.1.2.2-1. + +**Table 5.2.1.2.2-1: Response status code, message, and contents for service creation** + +| Status Code | Message | Contents | +|-------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------| +| 201 Created | Service created successfully | The BM-SC shall send the service resource identifier of the created service. | +| 401 Unauthorized | Request requires user authentication | In accordance to conditions as described in IETF RFC 7231 [6] and IETF RFC 7235 [8] | +| 403 Forbidden | Request cannot be fulfilled | The BM-SC may include optional text to indicate why the request could not be fulfilled | +| 412 Precondition Failed | Request cannot be fulfilled | The precondition given in one or more of the request-header fields evaluated to false when it was tested on the recipient. | +| Note: In addition to the above response codes, the BM-SC can also send appropriate response codes described in IETF RFC 7231 [6] as applicable. | | | + +##### 5.2.1.2.3 Service Modification + +###### 5.2.1.2.3.1 Partial Modification of Service Properties + +PATCH /xmb/v1.0/services/{service-res-id} + +Assuming that a service has been created using the service creation method described in subclause 5.2.1.2.2, partial updating of its properties can be performed by the Content Provider using the HTTP PATCH method on the "service" instance resource as follows: + +- the request URI with the "path" part is set to: "/xmb/v1.0/services/{service-res-id}" +- the Host field is set to the address of the BM-SC +- the Content-Type header field is set to "application/json" +- the body of the message is encoded in JSON format + +The {service-res-id} in the request URI is the service resource identifier of the service as allocated by the BM-SC during service creation. + +The content body of the service modification request shall contain updated partial representation of the service resource. The representation of the service is based on the JSON schema of the service resource as described in subclause 5.2.1.1. Further, one or more properties of the service listed in Table 5.2.1.1-1, with the exception that the value of the properties "id", "service-id", "pull-notification-url" and "receive-only-mode" cannot be modified. + +Upon receipt of the HTTP PATCH request from the Content Provider to update a service, the BM-SC will check whether the Content Provider is authenticated and authorized to update services as described in clause 7. If the authorization fails, the BM-SC shall send a 401 message. If the authorization is successful, the BM-SC shall update the requested service. Upon successful updating of the requested service, the BM-SC shall respond to the Content Provider with a 200 OK message indicating that the service is successfully updated along with the updated service resource. If the service was not found, the BM-SC shall send a 404 Not Found message. If the service cannot be updated, the BM-SC shall send a 403 Forbidden message to the Content Provider. + +The possible response messages from the BM-SC, depending on whether the PATCH request is successful or unsuccessful, are shown in Table 5.2.1.2.3.1-1. + +**Table 5.2.1.2.3.1-1: Response status code, message, and contents for service modification using HTTP PATCH** + +| Status Code | Message | Contents | +|-------------|---------------------------|------------------------------------------------------------| +| 200 OK | The request has succeeded | The BM-SC shall send the service resource that is modified | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|-------------------------------------------------------------------------------------| +| 204 No Content | The request has succeeded | None | +| 401 Unauthorized | Request requires user authentication | In accordance to conditions as described in IETF RFC 7231 [6] and IETF RFC 7235 [8] | +| 403 Forbidden | Request cannot be fulfilled | The BM-SC may include optional text to indicate why the request could not fulfilled | +| 404 Not Found | Requested resource not found | None | +| Note: In addition to the above response codes, the BM-SC can also send appropriate response codes described in IETF RFC 7231 [6] as applicable. | | | + +###### 5.2.1.2.3.2 Full Modification of Service Properties + +PUT /xmb/v1.0/services/{service-res-id} + +Assuming that a service has been created using the service creation method described in sub clause 5.2.1.2.2, full modification of its properties can be performed by the Content Provider using the HTTP PUT method on the "service" instance resource as follows: + +- the request URI with the "path" part is set to: "/xmb/v1.0/services/{service-res-id}". +- the Host field is set to the address of the BM-SC +- the Content-Type header field is set to "application/json" +- the body of the message is encoded in JSON format + +The {service-res-id} in the request URI is the service resource identifier of the service as allocated by the BM-SC during service creation. + +The content body of the service update request shall contain the updated representation of the service resource. The representation of the service is based on the JSON schema of the service resource as described in subclause 5.2.1.1. Furthermore, when HTTP PUT method is used for updating the service, the Content Provider shall specify the updated values of all the service properties with the exception that the value of the properties "id", "service-id", "pull-notification-url" and "receive-only-mode" cannot be modified. + +Upon receipt of the HTTP PUT request from the Content Provider to update a service, the BM-SC will check whether the Content Provider is authenticated and authorized to update services as described in clause 7. If the authorization fails, the BM-SC shall send a 401 message as described in Table 5.2.1.2.3.2-1. If the authorization is successful, the BM-SC update the requested service. While updating the service representation, the BM-SC shall overwrite the values of all properties of the service being updated with the values provided in the update request. Upon successful update of the requested service, the BM-SC shall respond to the Content Provider with a 200 OK success message indicating that the service is successfully updated along with the updated service resource. If the service was not found, the BM-SC shall send a 404 Not Found message. If the service cannot be updated, the BM-SC shall send a 403 Forbidden message to the Content Provider. + +The possible response messages from the BM-SC, depending on whether the PUT request is successful or unsuccessful, are shown in Table 5.2.1.2.3.2-1. + +**Table 5.2.1.2.3.2-1: Response status code, message, and contents for service modification using HTTP PUT** + +| Status Code | Message | Contents | +|------------------|--------------------------------------|-------------------------------------------------------------------------------------| +| 200 OK | The request has succeeded | The BM-SC shall send the service resource that is modified | +| 204 No Content | The request has succeeded | None | +| 401 Unauthorized | Request requires user authentication | In accordance to conditions as described in IETF RFC 7231 [6] and IETF RFC 7235 [8] | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|----------------------------------------------------------------------------------------| +| 403Forbidden | Request cannot be fulfilled | The BM-SC may include optional text to indicate why the request could not be fulfilled | +| 404 Not
Found | Requested resource not found | None | +| Note: In addition to the above response codes, the BM-SC can also send appropriate response codes described in IETF RFC 7231 [6] as applicable. | | | + +##### 5.2.1.2.4 Service Deletion + +DELETE /xmb/v1.0/services/{service-res-id} + +To delete a service, the Content Provider shall use the HTTP DELETE method on the "service" instance resource as follows: + +- the request URI with the "path" part is set to: "/xmb/v1.0/services/{service-res-id}" +- the Host field is set to the address of the BM-SC +- the Content-Type header field is set to "application/json" +- the body of the message is encoded in JSON format + +The {service-res-id} in the request URI is the service resource identifier of the service as allocated by the BM-SC during service creation. + +Upon receipt of the HTTP DELETE request from the Content Provider to delete a service, the BM-SC will check whether the Content Provider is authenticated and authorized to delete services as described in clause 7. If the authorization fails, the BM-SC shall send a 401 message as described in Table 5.2.1.2.4-1. If the authorization is successful, the BM-SC shall delete the requested service. Upon successful deletion of requested service, the BM-SC shall respond to the Content Provider with a 200 OK success message indicating that the service is successfully deleted along with the service resource identifier of the service that is deleted. If the service was not found, the BM-SC shall send a 404 Not Found message. If the service cannot be deleted, the BM-SC shall send 403 Forbidden message to the Content Provider. + +The possible response messages from the BM-SC, depending on whether the DELETE request is successful or unsuccessful, are shown in Table 5.2.1.2.4-1. + +**Table 5.2.1.2.4-1: Response status code, message, and contents for service deletion** + +| Status Code | Message | Contents | +|-------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|----------------------------------------------------------------------------------------| +| 200 OK | The request has succeeded | The BM-SC shall send the service resource identifier of the service that is deleted | +| 204 No Content | The request has succeeded | None | +| 401 Unauthorized | Request requires user authentication | In accordance to conditions as described in IETF RFC 7231 [6] and IETF RFC 7235 [8] | +| 403 Forbidden | Request cannot be fulfilled | The BM-SC may include optional text to indicate why the request could not be fulfilled | +| 404 Not Found | Requested resource not found | None | +| Note: In addition to the above response codes, the BM-SC can also send appropriate response codes described in IETF RFC 7231 [6] as applicable. | | | + +##### 5.2.1.2.5 Service Retrieval + +Services can be read when the Content Provider wishes to know the latest representation of the service resource at the BM-SC. + +Retrieval of a specific Service + +###### GET /xmb/v1.0/services/{service-res-id} + +The retrieval of a service shall be performed by the Content Provider using the HTTP GET method on the "service" instance resource as follows: + +- the request URI with the "path" part is set to: "/xmb/v1.0/services/{service-res-id}" +- the Host field is set to the address of the BM-SC + +The {service-res-id} in the request URI is the service resource identifier of the service as allocated by the BM-SC during service creation. + +Upon receipt of the HTTP GET request from the Content Provider, the BM-SC will check whether the Content Provider is authenticated and authorized to read services as described in clause 7. If the authorization fails, the BM-SC shall send a 401 message as described in table 5.2.1.2.5-1. If the authorization is successful, the BM-SC shall respond to the Content Provider with a 200 OK message along with the service information. The response from the BM-SC to the Content Provider shall contain the following: + +- the Content-Type header field is set to "application/json" +- the body of the message is encoded in JSON format + +The content body of this response message shall be the representation of the requested service based on the JSON schema of service resource as described in subclause 5.2.1.1. The properties "service-id", "service-class", and "service-announcement-mode" shall be included in the response to the Content Provider. All other properties of the service instance are optional to be returned to the Content Provider. + +Alternatively, if the service was not found, the BM-SC shall send a 404 Not Found message. If the request cannot be fulfilled, the BM-SC shall send a 403 Forbidden message to the Content Provider. + +The possible response messages from the BM-SC, depending on whether the GET request is successful or unsuccessful, are shown in Table 5.2.1.2.5-1. + +**Table 5.2.1.2.5-1: Response status code, message, and contents for service modification using HTTP GET** + +| Status Code | Message | Contents | +|---------------------|--------------------------------------|-------------------------------------------------------------------------------------------------| +| 200 OK | The request has succeeded | The BM-SC shall send the service representation of the service resource to the Content Provider | +| 401
Unauthorized | Request requires user authentication | In accordance to conditions as described in IETF RFC 7231 [6] and IETF RFC 7235 [8] | +| 403
Forbidden | Request cannot be fulfilled | The BM-SC may include optional text to indicate why the request could not be fulfilled | +| 404 Not
Found | Requested resource not found | None | + +Note: In addition to the above response codes, the BM-SC can also send appropriate response codes described in IETF RFC 7231 [6] as applicable. + +###### Retrieval of all Services + +###### GET /xmb/v1.0/services + +The retrieval of all services shall be performed by the Content Provider using the HTTP GET method on the "services" instance resource as follows: + +- the request URI with the "path" part is set to: "/xmb/v1.0/services" +- the Host field is set to the address of the BM-SC + +Upon receipt of the HTTP GET request from the Content Provider, the BM-SC will check whether the Content Provider is authenticated and authorized to read services as described in clause 7. If the authorization fails, the BM-SC shall send a 401 message as described in table 5.2.1.2.5-2. If the authorization is successful, the BM-SC shall respond to the Content Provider with a 200 OK message along with information of all services configured at the BM-SC. The response from the BM-SC to the Content Provider shall contain the following: + +- the Content-Type header field set to "application/json" +- the body of the message encoded in JSON format + +The content body of this response message shall be the representation of the list of all services configured at the BM-SC where each service representation is based on the JSON schema of service resource as described in subclause 5.2.1.1. The properties "service-id", "service-class", and "service-announcement-mode" shall be included for each service representation in the response to the Content Provider. All other properties of the service instance are optional to be returned to the Content Provider. + +Alternatively, if there are no services configured at the BM-SC, the BM-SC shall send message content in the 200 OK message indicating to the Content Provider that there are no services configured at the BM-SC. If the request cannot be fulfilled, the BM-SC shall send a 403 Forbidden message to the Content Provider. + +The possible response messages from the BM-SC, depending on whether the GET request is successful or unsuccessful, are shown in Table 5.2.1.2.5-2. + +**Table 5.2.1.2.5-2: Response status code, message, and contents for service modification using HTTP GET** + +| Status Code | Message | Contents | +|------------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 200 OK | The request has succeeded | If there are services configured at the BM-SC, the BM-SC shall send the representations of all the configured services to the Content Provider. If there are no services configured at the BM-SC, the BM-SC shall send message content in this message that there are no services configured at the BM-SC | +| 401 Unauthorized | Request requires user authentication | In accordance to conditions as described in IETF RFC 7231 [6] and IETF RFC 7235 [8] | +| 403 Forbidden | Request cannot be fulfilled | The BM-SC may include optional text to indicate why the request could not be fulfilled | + +Note: In addition to the above response codes, the BM-SC can also send appropriate response codes described in IETF RFC 7231 [6] as applicable. + +### 5.2.2 Sessions + +The Content Provider shall configure sessions at the BM-SC using the RESTful API methods over two resources managed at the BM-SC. + +Table 5.2.2-1 summarizes different resources for provisioning and managing sessions at the BM-SC. + +**Table 5.2.2-1: Resources for managing sessions at BM-SC** + +| Resource Name | Resource Type | Description | +|---------------|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Session | Instance resource | Represents a single session resource. The Content Provider can provision or modify a single session at the BM-SC by invoking REST API requests to this session resource at the BM-SC. | +| Sessions | Collection Resource | Represents a collection of session resources. | + +Since sessions are configured for each service, the session instance resource or the sessions collection resource are referenced through a particular service. + +#### 5.2.2.1 Properties + +Each session resource described in Table 5.2.2-1 has the set of properties described in Table 5.2.2.1-1. The Content Provider shall modify one or more of the properties of the session resource using the API operations described in subclause 5.2.2.2 + +Table 5.2.2.1-1 summarizes the different properties of a session resource. + +**Table 5.2.2.1-1: Properties of session resource** + +| Property Token | JSON Value Type | Defaults | | Parameter Description | Applicability (NOTE) | +|--------------------------------|---------------------|--------------------------------------------|----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| | | | | | | +| session-start | number | UTC Date timestamp (with second precision) | Session creation date + 1h | Time at which the MBMS Bearer become active. | | +| session-stop | number | UTC Date timestamp (with second precision) | Session start date + 1h | Time at which the MBMS bearer becomes inactive. | | +| max-ingest-bitrate | number | kbps | 0 | This requested bitrate by the Content Provider for content ingestion at the BM-SC, which excludes FEC overhead and transport overhead. The BM-SC calculates the MBMS Bearer bitrate from its value, considering overhead like FEC and other transport overheads. The session bitrate is always larger than or equal to the payload bitrate | | +| max-delay | number | ms | -1 | Specifies the maximum delay the MBMS System should add, i.e. from the time a packet is received by the BM-SC to the time when the packet should be received by the MBMS client. | | +| session-state | string | None | Idle | The BM-SC may automatically change the state of the session.
Possible states: "Session Idle", "Session Announced", "Session Active". | | +| service-announcement-starttime | number | UTC Date timestamp (with second precision) | None | When present, the wall-clock time at which the BM-SC shall start service announcement. If absent, the BM-SC may automatically start service announcement when it has all the data needed to perform such service announcement. | | +| geographical-area |
> string | None | Empty list | Geographical area to which the service is to be provided, via either unicast or MBMS bearers. The BM-SC derives the MBMS service area and the SAI list corresponding to the geographical area as provided by the Content Provider.
The Geographical Area contains list of string.
If the mc-extension property is present and the MCExtension feature is | | + +| | | | | | | +|-----------------------------|--------|------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | | |
supported, the content of each string follows the format specified by subclause 5.4.7 of 3GPP TS 26.348 [33].
Else, the content of each string item is left to the business agreement between the Content Provider and the Operator.
| | +| qoe-reporting-configuration | object | | |The Content Provider wishes to collect QoE reports for the session. The Content Provider can supply a list of QoE metric configurations where each metric configuration shall contain:
Metric name: Name of QoE metric
Metric type: Type of metric
Reporting interval: The interval at which the BM-SC should periodically aggregate and report the statistics to the Content Provider.
Sample percentage: Percentage of users to collect reports from
Start time: Start time of report collection
End time: End time of report collection
If this configuration is included, the QoE reporting configuration shall be applied only for this session., and the Content Provider is requesting override of service level configuration for this session by this configuration.
Note: SA4 should define the list of parameters for qoe-reporting-configuration. SA4 shall also indicate if service level qoe-reporting configuration can be applied.
| | +| session-type | string | None | Files |The Session Type represents the method used by the Content Provider in providing content to the BM-SC (via xMB-U). The BM-SC shall select the appropriate delivery method from the Session Type.
Valid values: "Streaming", "Files", "Application", "Transport-Mode"
When the Session Type is set to "Streaming", the BM-SC expects a Streaming type input (RTP), and the format shall compliant to MBMS streaming (as defined in 3GPP TS 26.346 [3]).
| | + +| | | | | | | +|--------------------|---------------------|------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| +| | | | |When the Session Type is set to "Files", the BM-SC expects generic files as input. The files can be provided either by on-request pull interactions or continuous push ingest.
When the Session Type is set to "Application", then the ingest method depends on the application service description.
When the Application Service Description corresponds to DASH, the BM-SC expects an MPD and optionally one or more Initialization Segments. The content is assumed to be 3GP-DASH compliant (as defined by 3GPP TS 26.247 [18]). The BM-SC may either pull the Media Segments from the Content Provider or the Content Provider will continuously push Media Segments to the BM-SC.
When the Session Type is set to "Transport-Mode", the BM-SC provides transport of data/TV content in a transparent manner. The Content Provider may provide some properties for the MBMS distribution.
The Session Type shall be extensible to include other session types.
| | +| max-cid | integer | none | none |integer indicating the MAX_CID parameter for the compressor (see IETF RFC 5795 [27]). The value for the LARGE_CID parameter (usage of short CID representation or large CID representation) shall be deducted from MAX_CID as follows:
If MAX_CID > 15 then
LARGE_CIDS = TRUE else
LARGE_CIDS = FALSE.
When header compression applies, the "max-cid" property shall be provided together with "header-compression" property.
| ROHC | +| header-compression |> object | none | none |
Requests the BM-SC to enable ROHC (see IETF RFC 5795 [27] and IETF RFC 3095 [28]) on the input flow. The object consists of:
- - "ipv4addr": String identifying an IPv4 address formatted in the "dotted decimal" notation as defined in IETF RFC 1166 [31].
- - "ipv6addr": String identifying an IPv6 address formatted according to clause 4 of IETF RFC 5952 [32]. The mixed
IPv4 IPv6 notation according to clause 5 of IETF RFC 5952 shall not be used.
- "port": integer between 0 and 65535 identifying a UDP or TCP port
- "periodicity": a number denoting the target periodicity for ROHC full header packets in units of seconds
- "profile": integer denoting the applicable ROHC profile (see IETF RFC 5795 [27]). The value is restricted to the 0x0001 RTP/UDP/IP profile or the 0x0002 UDP/IP profile, 0x0001 profile applies if omitted.
Either "ipv4addr" or "ipv6addr" shall be included and "port" and "periodicity" may be included.
The BM-SC shall:
- 1. apply the procedures in IETF RFC 5795 [27] and in IETF RFC 3095 [28] to provide header compression to downlink IP packets and possibly higher protocol layers within the user plane data;
- 2. use the ROHC profile requested in the "profile" property for downlink packet which belongs to any of the flows listed in this property;
- 3. use the 0x0000 uncompressed profile for any downlink packet which does not belong to any of the flows listed in this property; and
- 4. use the ROHC unidirectional mode (see IETF RFC 3095 [28]) without ROHC segmentation (see IETF RFC 5795 [27]).
Requests the BM-SC to perform FEC (see IETF RFC 6363 [29]) protection of the input flow when transmitting over the MBMS channel. The string shall include an SDP description of FEC framework configuration information (see subclause 5.5 of IETF RFC 6363 [29]) formatted according to subclause 8A.5 of 3GPP TS 26.346 [3].
| FEC | +| resource-sharing-ind | boolean | none | false |The resource sharing indication.
When present and set to "true", it implies the current transmission resources can be shared with other sessions.
| ResourceSharing | + +| | | | | | | +|------------------------------------------|--------|----------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| +| | | | | Note that other sessions will use the same Max Bitrate, Geographical Area and (in case of MC Services) QoS-Information. | | +| resource-sharing-url | string | none | none |The resource sharing id.
When present in the session modification request, the value of the field identifies an existing xMB session resource URL (as specified in table 5.1.1-1) to share the transmission, where Max Bitrate, Geographical Area and (in case of MC Services) QoS-Information are re-used.
Note that the Max Bitrate, Geographical Area and (in case of MC Services) QoS-Information cannot be changed since the values from the original session will be used.
| ResourceSharing | +| session-announcement-mode | string | – None – | Other |Represents the session announcement mode. The session announcement mode is either "Content Provider" or "SACH", with the following behavior:
"Content Provider": The BMSC generates the session parameters and provides those to the Content Provider.
"SACH": In this case, the session announcement is done by the MBMS system through the SACH. (see Annex L.2, L.3 of 3GPP TS 26.346 [3]).
Additional modes may be added in future releases.
Only applicable if the Session Type is set to "Transport-Mode"
| Transport | +| userplane-session-description-parameters | object | | |This property provides information to the BM-SC on where and how to access the user plane content from the content provider, and comprises one or more of the following components:
Type: the type of the content associated with the target resource, for example the Internet Media Type of the resource as identified by an HTTP/S URL. An "embedded" type is defined, which indicates that the xMB-U user plane parameters are embedded in the User Plane Parameters object described below.
Access URL: A URL that enables the access to and possibly control of the ingest session. The URL may, for example, be an RTSP URL, a reference to an SDP that
| Transport | + +| | | | | | | +|--|--|--|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | | |describes a multicast stream, or an HTTP/S URL to retrieve an already-packaged MPEG2-TS stream.
User Plane Parameters: When the Type is set to "embedded", the Content Provider shall provide an object to the BM-SC which contains the session description.
If this property is set to Forward-only, the object may contain a ready-made Session Description and the indication of a single xMB-U reception UDP port. When a Session Description is present, the BM-SC shall use it for Service Announcement.
If this property is set to Proxy, the object shall contain a Session Description template and a list of the transmitted UDP flows to be forwarded on the established MBMS bearer for the session. For each list entry, the content provider shall indicate whether a) this UDP flow is directly associated with a media description entry in the Session Description Template – i.e., an "m=" line is present in the template and which contains a port field, or b) this UDP flow is related to a media description entry – e.g., it corresponds to an RTCP flow affiliated with the RTP flow as described by the RTP/AVP profile). If the flow is directly associated with a media description entry, then the BM-SC shall modify the port field of the media description entry in the Session Description Template. If the flow is related to a media description entry, then the BM-SC shall simply forward the flow onto a port whose value is equal to the port of the related media session plus an offset.
Note the BM-SC may get input on session properties from the content provider, e.g. bitrate, depending on the ingest session.
| | +|--|--|--|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| + +| | | | | | | +|-----------------------------------------|--------|----------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------| +| userplane-delivery-mode-configuration | string | – None – | Forward-only |This property defines how the session needs to be delivered to the application, i.e. it basically establishes the delivery mode.
Mode Enumeration: Specifies the delivery mode.
Forward-only: The BM-SC receives complete IP Multicast packets for to be forwarded. The Content Provider will create the IP multicast packets.
Proxy: The BM-SC proxies the incoming UDP payloads to the outgoing UDP payloads. The BM-SC will create the IP multicast packets.
Only applicable if the Session Type is set to "Transport-Mode".
| Transport | +| delivery-session-description-parameters | string | | |The contents of this property depend on the setting of the Session Announcement Mode property. If Session Announcement Mode is set to "Content Provider", then at minimum the following session parameters shall be provided by the BM-SC:
TMGI of the MBMS Bearer
For Receive Only Mode service, the TMGI shall be allocated from the range specified in 3GPP TS 24.116 [25]. Note that additional session parameters may be provided, based on the configuration options of the delivery method set to "Transport-Mode".
Only applicable if the Session Type is set to "Transport-Mode".
| Transport | +| sdp-url | string | – None – | "" |A URL to the SDP that describes the streaming session between the Content Provider and the BM-SC, which will be used for BM-SC ingestion of the streaming session via xMB-U. The SDP shall include the RTSP links for every media session as part of the "a=control" attribute to enable RTSP control of the session. The SDP shall also contain the required bitrate for each of the media sessions.
The content shall conform to the constraints of this specification.
Only applicable if the Session Type is set to "Streaming".
| RTPStreaming | + +| | | | | | | +|---------------------|--------|-----------|----------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------| +| time-shifting | number | second | 0 | Indicates if and for how long time shifting access to the content (using unicast) may be provided for this session.If not set (so defaulted to 0), there shall be no time shifting access.
Only applicable if the Session Type is set to "Streaming". | RTPStreaming | +| application-service | string | MIME type | application/dash+xml | Internet Media Type of the Application Service
Only applicable if the Session Type is set to "Application". | ApplicationPush, ApplicationPull | +| ingest-mode | string | None | "Push" when Session Type is set to "Application"
"Pull" when Session Type is set to "Files" | The ingest mode enumerates how resources are ingested into the BM-SC via xMB-U.
When the Session Type is set to "Application":
Pull: The BM-SC pulls the resources as described by the application entry point document.
Push: The Content Provider pushes resources. The BM-SC needs to provide a push URL.
In case of DASH, resources are Media Segments:
Pull: The BM-SC pulls the Media Segments as described by the Segment availability start time from a DASH MPD.
Push: The Content Provider pushes Media Segments, so that the Media Segment is available on the BM-SC according to Segment availability start time. The BM-SC needs to provide a push URL.
When the Session Type is set to "Files":
Push: The Content Provider shall push the file to the BM-SC that will immediately process and deliver as soon as it is ready. The BM-SC may be configured to ignore all files that are pushed before session active time, or store them. In case of Push mode, the BM-SC shall provide back to the Content Provider the URL the Content Provider shall use to push the files. | ApplicationPush, ApplicationPull, FilePush, FilePull | + +| | | | | | | +|--------------------------------|---------|------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| | | | | Pull: In this case, the Content Provider provides the resource location from which the BM-SC will fetch the file. The Content Provider may tell the BM-SC when to start fetching the file. | | +| application-
entrypoint-url | string | None | "" |
The application entry point refers to an MPD when Application Service Description pertains to DASH.
When the Ingest Mode is set to Push, the MPD URL refers to a DASH MPD which should be fetched, optionally conditioned, and then inserted into Service Announcement.
When the Ingest Mode is set to Pull, then the BM-SC will fetch the Segments using unicast.
Note that if not set to a valid URL, the session will not be started.
| ApplicationPush,ApplicationPull, | +| push-url | string | None | "" |
When the Session Type is set to "Application":
A resource locator for ingesting Media Segments using HTTP via xMB-U. The Content Provider may create additional sub-resources using WebDAV procedures.
This is a read-only property managed by the BM-SC and only present when Ingest Mode is set to Push
This property is mandatory if the Session type is set to "Application" and Ingest Mode is set to Push.
When the Session Type is set to Files:
A resource locator for ingesting content using HTTP via xMB-U.
This is a read-only property managed by the BM-SC and only present when Ingest Mode is set to Push.
| ApplicationPush,FilePush | +| unicast-
delivery | boolean | None | False |
Indicator whether the content is also available for unicast retrieval.
Only applicable if the Session Type is set to "Application".
| ApplicationPush,ApplicationPull, | +| Components | array | None | Empty list | List of components of the application, which are recommended to be made available on MBMS Bearers. | ApplicationPush,
ApplicationPull, | + +| | | | | | | +|-----------|-------|--|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| | | | | In case of DASH, each component is identified by a representation identifier.
Only applicable if the Session Type is set to "Application". | | +| file-list | array | | |
List of files to be sent.
In the Push mode, the file list is not used since the BM-SC will monitor its push folder and send the files it receives on a first-come first-served basis.
In Pull mode, the file list contains the following information per file entry:
file URL: the URL to the file the BM-SC will use to fetch the content
file display URL: The URL to the file as seen by the UE
byte-range (optional): If present and set to "true", indicates that the HTTP(S) URL given in the file display URL parameter can be used for Byte-Range-Based file repair (subclause 9.3 of 3GPP TS 26.346 [3]) otherwise file display URL parameter should not be used for Byte-Range-Based file repair
e-tag (optional): represents the value of the ETag as defined in IETF RFC 7232 [38] which may also serve as the version identifier for the file in the Byte-Range-Based file repair requests. The ETag should only be supplied by the 3rd party content provider if it is expected that it is different from the one provided over xMB-U when fetching the file.
file earliest fetch time: The BM-SC shall fetch the file no sooner than this UTC timestamp. If absent, then the file shall be present on the Content Provider server and the BM-SC may fetch it at a time of its choosing.
file latest fetch time: The BM-SC shall fetch the file no later than this UTC timestamp. If absent, then the file shall be present on the Content Provider server and
| FilePull,FileRepair (NOTE 2) | + +| | | | | | | +|--|--|--|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | | |
the BM-SC may fetch it at a time of its choosing.
file size (optional): The Content Provider may provide the precise or a file size estimate as input. The BM-SC may update the file size once it has started to fetch the file.
file status: Enumeration stating the state of the file. Possible values are pending, fetched, prepared, transmitting, sent.
Target reception completion time (on the MBMS Client): hint on the deadline by which target time the file should be completely received by the UE. The BM-SC should schedule and order the transmission accordingly.
Keep Updated Interval: The BM-SC checks the file resources with the given interval for changes.
Unicast availability: Indication that the file is also available for unicast retrieval by the application at a Content Provider server whose location is given by the HTTP(S) URL corresponding to the value of "file display URL".
File repetition: The number of times the file shall be sent on the session (a value of 1 means the file shall be sent only once). This counter shall be decreased by one each time the file has been transmitted. When the counter reaches zero the file will cease to be delivered. The BM-SC may send FEC instead of source information.
Note that the expected behavior is that the BM-SC will first send all files in the order of the File List, then decrement the file repetition counter for each file, and subsequently retransmit the list again (only files with counter > 0 are transmitted). This is repeated until all repetitions are completed, or the session stop time has elapsed, whichever event occurring first.
Periodic update interval: When present, it is an indication that
| | +|--|--|--|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| + +| | | | | | | +|---------------------------------|--------|------|----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | | | | this file of the list of files is expected to be periodically updated, and the value of this parameter represents the nominally expected time interval between successive updates of this file. This parameter is a signal to the BM-SC to deliver the file and its updates as a Datacasting service. From its value, the BM-SC will choose the delivery mode ('scheduled-and-periodic' or 'back-to-back'), and set the associated interval and @mode values in controlling the transmission of the Datacasting service. | | +| file-delivery-manifest-url | string | None | "" | Alternative to the file list for describing file properties and delivery requirements. The resource may additionally describe scheduling information for the file.Only applicable if the Session Type is set to Files. | FilePush, FilePull | +| display-base-url | string | None | "" | When ingest mode is set to Push, the Base URL as seen by the UE. | FilePush | +| sa-file-url | string | None | "" | When the service announcement mode is set to "Content provider", the BM-SC returns the URL of the SA file announcing the session. The BM-SC shall follow the profile 1c (Annex L.3 of 3GPP TS 26.346 [3]) | SaProfile | +| local-mbms-delivery-information | object | | | The Content Provider may request the BM-SC to activate an MBMS bearer for local MBMS based MBMS data delivery. If so, the Content Provider shall provide:
MBMS eNB IPv4 multicast address:
Contains the M1 (transport) plane IPv4 destination multicast address used by MBMS-GW for IP multicast encapsulation of application IP multicast datagrams.
MBMS eNB IPv6 multicast address:
Contains the M1 (transport) plane IPv6 prefix of destination multicast address used by MBMS-GW for IP multicast encapsulation of application IP multicast datagrams.
MBMS GW IPv4 SSM address:
Contains the value of MBMS- | LocalMBMS | + +| | | | | | | +|--------------|--------|------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| +| | | | |
GW's IPv4 address for Source Specific Multicasting.
MBMS GW IPv6 SSM address: Contains the value of MBMS-GW's IPv6 address for Source Specific Multicasting.
Common Tunnel Endpoint Identifier: Indicates the common tunnel endpoint identifier of MBMS GW for user plane.
BM-SC IPv4 address: Indicates the destination IPv4 address of the BM-SC for the reception of user plane data via the xMB-U interface.
BM-SC IPv6 address: Indicates the destination IPv6 address of the BM-SC for the reception of user plane data via the xMB-U interface.
BM-SC port: Indicates the destination UDP port of the BM-SC for the reception of user plane data via the xMB-U interface.
| | +| group-ids | array | None | Empty list |This parameter contains a list of group identifiers, applicable if the service-announcement-mode is set to "SACH".
It is used by the BM-SC in the service announcement for identifying UE belonging to a group.
| GroupContentDelivery | +| mc-extension | object | | |If the MCExtension feature is supported, the Content Provider may request the BM-SC to activate an MBMS bearer with a specific QoS. If so, the Content Provider shall provide the following QoS properties in the session modification operation, to be used by the BM-SC within the QoS-Information AVP during the MBMS Session start procedure (3GPP TS 29.061 [20]):
gbr: Guaranteed bitrate for the MBMS session in unit kbps. The BM-SC shall use this value for the Guaranteed-Bitrate-DL AVP. The difference between the max-ingest-bitrate and gbr can be used by the BM-SC as a budget for FEC.
qci: QoS Class identifier. The BM-SC shall use this value for the QoS-Class-Identifier AVP.
| MCExtension | + +| | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|--|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | | |arp-priority-level: the BM-SC shall use this value for the Priority-Level AVP within the Allocation-Retention-Priority AVP.
arp-pre-emption-capability: the BM-SC shall use this value for the Pre-emption-Capability AVP within the Allocation-Retention-Priority AVP.
arp-pre-emption-vulnerability: the BM-SC shall use this value for the Pre-emption-Vulnerability AVP within the Allocation-Retention-Priority AVP.
If the Content Provider includes the mc-extension property during the session modification operation, the BM-SC shall return the following property in the session retrieval operation:
tmgi: the TMGI of the MBMS session, as returned by the MBMS Session start procedure in 3GPP TS 29.061 [20], the encoding of TMGI is specified in 3GPP TS 24.008 [37], from octet 3 to 8.
| | +|NOTE 1: Properties marked with a supported feature are applicable as described in subclause 9.
NOTE 2: FileRepair feature is only applicable for byte-range and e-tag properties.
Forbidden | Request cannot be fulfilled | The BM-SC may include optional text to indicate why the request could not be fulfilled | +| 404 Not
Found | Requested resource not found | None | +| Note: In addition to the above response codes, the BM-SC can also send appropriate response codes described in IETF RFC 7231 [6] as applicable. | | | + +##### 5.2.2.2.5 Session Retrieval + +Sessions can be read when the Content Provider wishes to know the latest representation of the session resources at the BM-SC. + +Retrieval of a specific Session of a specific Service + +GET /xmb/v1.0/services/{service-res-id}/sessions/{session-res-id} + +The retrieval of a session shall be performed by the Content Provider using the HTTP GET method on the "session" instance resource as follows: + +- the request URI with the "path" part is set to: /xmb/v1.0/services/{service-res-id}/sessions/{session-res-id} +- the Host field is set to the address of the BM-SC + +The {service-res-id} in the request URI is the service resource identifier of the service as allocated by the BM-SC during service creation. + +The {session-res-id} in the request URI is the session resource identifier of the session that is being retrieved. + +Upon receipt of the HTTP GET request from the Content Provider, the BM-SC will check whether the Content Provider is authenticated and authorized to read services and sessions as described in clause 7. If the authorization fails, the BM-SC shall send a 401 message as described in table 5.2.2.2.5-1. If the authorization is successful, the BM-SC shall respond to the Content Provider with a 200 OK message and shall include the session resource representation of the session corresponding to the given service to the Content Provider. The response from the BM-SC to the Content Provider shall contain the following: + +- the Content-Type header field set to "application/json" +- the body of the message encoded in JSON format + +The content body of this response message shall be the representation of the session configured at the BM-SC for the given service where the session representation is based on the JSON schema of session resource as described in subclause 5.2.2.1. The properties "session-start", "session-stop", "max-ingest-bitrate", "session-state", "geographical-area", "session-type", "session-announcement-mode", "session-type", "userplane-delivery-mode-configuration", "sdp-url", "application-service-description", "ingest-mode", "application-entrypoint-url", and "unicast-delivery" shall be included in the response to the Content Provider. All other properties of the session instance are optional to be returned to the Content Provider. + +Alternatively, if the service was not found or if the session was not found, the BM-SC shall send a 404 Not Found message. If the request cannot be fulfilled, the BM-SC shall send 403 Forbidden message to the Content Provider. + +The possible response messages from the BM-SC, depending on whether the GET request is successful or unsuccessful, are shown in Table 5.2.2.2.5-1. + +**Table 5.2.2.2.5-1: Response status code, message, and contents for service modification using HTTP GET** + +| Status Code | Message | Contents | +|---------------------|--------------------------------------|-------------------------------------------------------------------------------------------------| +| 200 OK | The request has succeeded | The BM-SC shall send the session representation of the session resource to the Content Provider | +| 401
Unauthorized | Request requires user authentication | In accordance to conditions as described in IETF RFC 7231 [6] and IETF RFC 7235 [8] | +| 403
Forbidden | Request cannot be fulfilled | The BM-SC may include optional text to indicate why the request could not be fulfilled | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------| +| 404 Not Found | Requested resource not found | None | +| Note: In addition to the above response codes, the BM-SC can also send appropriate response codes described in IETF RFC 7231 [6] as applicable. | | | + +###### Retrieval of all Sessions of a Service + +###### GET /xmb/v1.0/services/{service-res-id}/sessions + +The retrieval of all sessions of a service shall be performed by the Content Provider using the HTTP GET method on the "sessions" instance resource as follows: + +- the request URI with the "path" part is set to: /xmb/v1.0/services/{service-res-id}/sessions +- the Host field is set to the address of the BM-SC + +The {service-res-id} in the request URI is the service resource identifier of the service as allocated by the BM-SC during service creation. + +Upon receipt of the HTTP GET request from the Content Provider, the BM-SC will check whether the Content Provider is authenticated and authorized to read services and sessions as described in clause 7. If the authorization fails, the BM-SC shall send a 401 message as described in table 5.2.2.2.5-2. If the authorization is successful, the BM-SC shall respond to the Content Provider with a 200 OK message. If there are sessions configured at the BM-SC for the corresponding service, the BM-SC shall send the representation of the list of all session resources configured at the BM-SC for that service along with the 200 OK message. If there are no sessions configured at the BM-SC for that service, the BM-SC shall send message content in the 200 OK message indicating to the Content Provider that there are no sessions configured at the BM-SC for that service. + +The response from the BM-SC to the Content Provider shall contain the following: + +- the Content-Type header field set to "application/json" +- the body of the message encoded in JSON format + +The content body of this response message shall be the representation of list of sessions configured at the BM-SC for the given service where each session representation is based on the JSON schema of session resource as described in subclause 5.2.2.1. The properties "session-start", "session-stop", "max-ingest-bitrate", "session-state", "geographical-area", "session-type", "session-announcement-mode", "session-type", "userplane-delivery-mode-configuration", "sdp-url", "application-service-description", "ingest-mode", "application-entrypoint-url", and "unicast-delivery" shall be included for each session representation in the response to the Content Provider. All other properties of the session instance are optional to be returned to the Content Provider. + +Alternatively, if the request cannot be fulfilled, the BM-SC shall send 403 Forbidden message to the Content Provider. If the service was not found, the BM-SC shall send a 404 Not Found message + +The possible response messages from the BM-SC, depending on whether the GET request is successful or unsuccessful, are shown in Table 5.2.2.2.5-2. + +**Table 5.2.2.2.5-2: Response status code, message, and contents for service modification using HTTP GET** + +| Status Code | Message | Contents | +|------------------|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 200 OK | The request has succeeded | If there are sessions configured at the BM-SC for that service, the BM-SC shall send the representations of all the configured sessions for that service to the Content Provider. If there are no sessions configured at the BM-SC for that service, the BM-SC shall send message content in this message indicating to the Content Provider that there are no sessions configured at the BM-SC for this service | +| 401 Unauthorized | Request requires user authentication | In accordance to conditions as described in IETF RFC 7231 [6] and IETF RFC 7235 [8] | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|----------------------------------------------------------------------------------------| +| 403
Forbidden | Request cannot be fulfilled | The BM-SC may include optional text to indicate why the request could not be fulfilled | +| 404 Not
Found | Requested resource not found | None | +| Note: In addition to the above response codes, the BM-SC can also send appropriate response codes described in IETF RFC 7231 [6] as applicable. | | | + +### 5.2.3 Reports + +The BM-SC shall send reports to the Content Provider upon request by the Content Provider. Table 5.2.3-1 summarizes different report resources that the BM-SC manages for sending reports to the Content Provider. + +**Table 5.2.3-1: Resources for managing reports at BM-SC** + +| Resource Name | Resource Type | Description | +|---------------|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| Report | Instance resource | Represents a single report resource. The BM-SC can send an individual report to the Content Provider using the report instance resource | +| Reports | Collection Resource | Represents a collection of report resources. | + +Reports can be generated separately for each service or for a session belonging to a particular service. Therefore, a report can be referenced with a given service resource identifier or for a combination of service resource identifier and session resource identifier. + +#### 5.2.3.1 Properties + +Each report resource described in Table 5.2.3-1 has the set of properties described in Table 5.2.3.1-1. The BM-SC shall deliver the reports as indicated by this structure using the API operations described in subclause 5.2.3.2 + +Table 5.2.3.1-1 summarizes different service properties of a service resource. + +**Table 5.2.3.1-1: Resources for managing services at BM-SC** + +| Property Token | JSON Value Type | Parameter Description | +|-----------------------------------------------------------------------------------------------------------------------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| report-res-id | string | Report resource identifier | +| report-starttime | string | Report collection start time | +| report-endtime | string | Report collection end time | +| report-type | string | Type of report. Three types of reports can be generated by the BM-SC to send to the Content Provider:
Consumption report: Report that provides service consumption information
QoE report: Report that provides detailed QoE information of the content received
File reception report: Report that provides detailed reception information for each file | +| report-url | string | Location of the report from where the Content Provider can retrieve the detailed report. | +| Report | string | Detailed report. This may not be included if report-url is included | +| Note: SA4 to clarify the report types and detail structure of a report that can be sent from BM-SC to the Content Provider. | | | + +The report instance resource with the properties defined above for each report can be found in Annex B. + +#### 5.2.3.2 API Operations + +##### 5.2.3.2.1 Introduction + +The Content Provider can request reports from the BM-SC for a given service or a session belonging to a given service. + +##### 5.2.3.2.2 Report Retrieval + +Reports can be retrieved by the Content Provider for a service or for a session of a given service using HTTP GET method. + +###### Report Retrieval for a Service + +GET /xmb/v1.0/services/{service-res-id}/reports + +The retrieval of reports of a service shall be performed by the Content Provider using the HTTP GET method on the "reports" collection resource as follows: + +- the request URI with the "path" part set to: "/xmb/v1.0/services/{service-res-id}/reports" +- the Host field is set to the address of the BM-SC + +QoE reports however are only available on session level. The {service-res-id} in the request URI is the service resource identifier of the service as allocated by the BM-SC during service creation. + +Upon receipt of a HTTP GET request from the Content Provider to retrieve all the reports of a service, the BM-SC will check whether the Content Provider is authenticated and authorized to request reports for services and sessions configured at the BM-SC as described in clause 7. If the authorization fails, the BM-SC shall send a 401 message as described in Table 5.2.3.2.2-1. If the authorization is successful, the BM-SC shall verify that the service with the given service resource identifier exists at the BM-SC. If the service exists at the BM-SC, the BM-SC shall respond to the Content Provider with a 200 success message along with the service resource identifier and the list of all reports for that service. The response from the BM-SC to the Content Provider shall contain the following: + +- the Content-Type header field set to "application/json" +- the body of the message encoded in JSON format + +The content body of this response message shall be the list of report for that service. Each report in this list shall be based on the JSON schema of report resource as described in subclause 5.2.3.1. + +Alternatively, if the report retrieval request cannot be fulfilled, the BM-SC shall send a 403 message to the Content Provider. If the service for which the report is sought could not be found, the BM-SC shall send a 404 message to the Content Provider. + +The possible response messages from the BM-SC, depending on whether the GET request is successful or unsuccessful, are shown in Table 5.2.3.2.2-1. + +**Table 5.2.3.2.2-1: Response status code, message, and contents for retrieval of all service reports** + +| Status Code | Message | Contents | +|------------------|--------------------------------------|------------------------------------------------------------------------------------------| +| 200 OK | The request has succeeded | The BM-SC shall send the service resource identifier and all the reports for the service | +| 401 Unauthorized | Request requires user authentication | In accordance to conditions as described in IETF RFC 7231 [6] and IETF RFC 7235 [8] | +| 403 Forbidden | Request cannot be fulfilled | The BM-SC may include optional text to indicate why the request could not be fulfilled | +| 404 Not Found | Requested resource not found | None | + +Note: In addition to the above response codes, the BM-SC can also send appropriate response codes described in IETF RFC 7231 [6] as applicable. + +###### GET /xmb/v1.0/services/{service-res-id}/reports/{report-res-id} + +The Content Provider can request individual reports of a service if it is aware of the report resource identifiers of that service. A specific report for a service can be retrieved by the Content Provider using the HTTP GET method on the "report" instance resource as follows. + +- the request URI with the "path" part set to: "/xmb/v1.0/services/{service-res-id}/reports/{report-res-id}" +- the Host field is set to the address of the BM-SC + +The {service-res-id} in the request URI is the service resource identifier of the service whose reports are being sought. + +The {report-res-id} in the request URI is the report resource identifier of that service. + +It should be noted that QoE reports are only available on session level. Upon receipt of a HTTP GET request from the Content Provider to retrieve a specific report of a service with report resource identifier, the BM-SC will check whether the Content Provider is authenticated and authorized to request reports for services and sessions configured at the BM-SC as described in clause 7. If the authorization fails, the BM-SC shall send a 401 message as described in Table 5.2.3.2.2-2. If the authorization is successful, the BM-SC shall verify that the service with the given service resource identifier and a report with given report resource identifier exists for that service at the BM-SC. If such report exists at the BM-SC, the BM-SC shall respond to the Content Provider with a 200 success message along with the service resource identifier and the report to the Content Provider. The response from the BM-SC to the Content Provider shall contain the following: + +- the Content-Type header field set to "application/json" +- the body of the message encoded in JSON format + +The content body of this response message shall be the requested report resource for that service whose representation is based on the JSON schema of report resource as described in subclause 5.2.3.1. + +Alternatively, if the report retrieval request cannot be fulfilled, the BM-SC shall send a 403 message to the Content Provider. If the service for which the report is sought could not be found, the BM-SC shall send a 404 message to the Content Provider. + +The possible response messages from the BM-SC, depending on whether the GET request is successful or unsuccessful, are shown in Table 5.2.3.2.2-2. + +**Table 5.2.3.2.2-2: Response status code, message, and contents for retrieval of a specific report of a service** + +| Status Code | Message | Contents | +|------------------|--------------------------------------|----------------------------------------------------------------------------------------------| +| 200 OK | The request has succeeded | The BM-SC shall send the service resource identifier and the requested report of the service | +| 401 Unauthorized | Request requires user authentication | In accordance to conditions as described in IETF RFC 7231 [6] and IETF RFC 7235 [8] | +| 403 Forbidden | Request cannot be fulfilled | The BM-SC may include optional text to indicate why the request could not be fulfilled | +| 404 Not Found | Requested resource not found | None | + +Note: In addition to the above response codes, the BM-SC can also send appropriate response codes described in IETF RFC 7231 [6] as applicable. + +###### Report Retrieval for a Session of a given Service + +###### GET /xmb/v1.0/services/{service-res-id}/sessions/{session-res-id}/reports + +The retrieval of all the reports of a session for a given service shall be performed by the Content Provider using the HTTP GET method on the "reports" collection resource as follows: + +- the request URI with the "path" part is set to: "/xmb/v1.0/services/{service-res-id}/sessions/{session-res-id}/reports" +- the Host field is set to the address of the BM-SC + +The {service-res-id} in the request URI is the service resource identifier of the service as allocated by the BM-SC during service creation. + +The {session-res-id} in the request URI is the session resource identifier of the session whose reports are being sought. + +Upon receipt of a HTTP GET request from the Content Provider to retrieve all the reports of a session of given service, the BM-SC will check whether the Content Provider is authenticated and authorized to request reports for services and sessions configured at the BM-SC as described in clause 7. If the authorization fails, the BM-SC shall send a 401 message as described in Table 5.2.3.2.2-3. If the authorization is successful, BM-SC shall verify that the service with the given service resource identifier and a corresponding session with the given session identifier exists at the BM-SC. If such a session exists at the BM-SC, the BM-SC shall respond to the Content Provider with a 200 success message along with the list of all reports for that session. If there are no reports for that session at the BM-SC, the BM-SC shall send a 200 OK message with message content indicating that there are no reports for the session at the BM-SC. The response from the BM-SC to the Content Provider shall contain the following: + +- the Content-Type header field set to "application/json" +- the body of the message encoded in JSON format + +The content body of this response message shall be the list of all reports for that session. Each report in this list of reports sent shall be based on the JSON schema of report resource as described in subclause 5.2.3.1. + +Alternatively, if the report retrieval request cannot be fulfilled, the BM-SC shall send a 403 message to the Content Provider. If the session for which the report is sought could not be found, or if the service corresponding to that session could not be found, the BM-SC shall send a 404 message to the Content Provider. + +The possible response messages from the BM-SC, depending on whether the GET request is successful or unsuccessful, are shown in Table 5.2.3.2.2-3. + +**Table 5.2.3.2.2-3: Response status code, message, and contents for retrieval of all reports for a session** + +| Status Code | Message | Contents | +|------------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 200 OK | The request has succeeded | The BM-SC shall send the service resource identifier, session resource identifier, and all the reports of that session. If there are no reports for that session at the BM-SC, the BM-SC shall include message content indicating that there are no reports for the requested session at the BM-SC. | +| 401 Unauthorized | Request requires user authentication | In accordance to conditions as described in IETF RFC 7231 [6] and IETF RFC 7235 [8] | +| 403 Forbidden | Request cannot be fulfilled | The BM-SC may include optional text to indicate why the request could not be fulfilled | +| 404 Not Found | Requested resource not found | None | + +Note: In addition to the above response codes, the BM-SC can also send appropriate response codes described in IETF RFC 7231 [6] as applicable. + +**GET /xmb/v1.0/services/{service-res-id}/sessions/{session-res-id}/reports/{report-res-id}** + +The Content Provider can request individual reports of a given session of a service if it is aware of the report resource identifiers of that session for that service. A specific report for a session can be retrieved by the Content Provider using the HTTP GET method on the "report" instance resource as follows. + +- the request URI with the "path" part is set to: "/xmb/v1.0/services/{service-res-id}/sessions/{session-res-id}/reports/{report-res-id}" +- the Host field is set to the address of the BM-SC + +The {service-res-id} in the request URI is the service resource identifier of the service as allocated by the BM-SC during service creation. + +The {session-res-id} in the request URI is the session resource identifier of the session whose report is being sought. + +The {report-res-id} in the request URI is the report resource identifier that is being sought. + +Upon receipt of a HTTP GET request from the Content Provider to retrieve a specific report for a session of a service, the BM-SC will check whether the Content Provider is authenticated and authorized to request reports for services and sessions configured at the BM-SC as described in clause 7. If the authorization fails, the BM-SC shall send a 401 message as described in Table 5.2.3.2.2-4. If the authorization is successful, the BM-SC shall verify that a report with report resource identifier exists for a session with given session resource identifier whose service identifier is the given service resource identifier at the BM-SC. If such a report exists at the BM-SC, the BM-SC shall respond to the Content Provider with a 200 success message along with the requested report to the Content Provider. The response from the BM-SC to the Content Provider shall contain the following: + +- the Content-Type header field set to "application/json" +- the body of the message encoded in JSON format + +The content body of this response message shall be the requested report resource for that session for the given service and whose representation is based on the JSON schema of report resource as described in subclause 5.2.3.1. + +Alternatively, if the report retrieval request cannot be fulfilled, the BM-SC shall send a 403 message to the Content Provider. If the session for which the report is sought could not be found, or if the service corresponding to that session could not be found, or if the report is not found, the BM-SC shall send a 404 message to the Content Provider. + +The possible response messages from the BM-SC, depending on whether the GET request is successful or unsuccessful, are shown in Table 5.2.3.2.2-4. + +**Table 5.2.3.2.2-4: Response status code, message, and contents for retrieval of a specific report of a session** + +| Status Code | Message | Contents | +|------------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------| +| 200 OK | The request has succeeded | The BM-SC shall send the service resource identifier, session resource identifier, and the requested report for the service | +| 401 Unauthorized | Request requires user authentication | In accordance to conditions as described in IETF RFC 7231 [6] and IETF RFC 7235 [8] | +| 403 Forbidden | Request cannot be fulfilled | The BM-SC may include optional text to indicate why the request could not be fulfilled | +| 404 Not Found | Requested resource not found | None | + +Note: In addition to the above response codes, the BM-SC can also send appropriate response codes described in IETF RFC 7231 [6] as applicable. + +### 5.2.4 Notifications + +Notifications can be exchanged via two alternative methods. In the first method, the Content Provider can "pull" the notifications from the BM-SC using HTTP GET method if and when the Content Provider wishes to acquire notification information as described in this subclause. The second method is that the notifications can be "pushed" from the BM-SC to the Content Provider via the push-notification-url as documented in clause 8. + +Table 5.2.4-1 summarizes different notification resources that the BM-SC manages for sending notifications to the Content Provider. + +**Table 5.2.4-1: Resources for managing services at BM-SC** + +| Resource Name | Resource Type | Description | +|---------------|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Notification | Instance resource | Represents a single notification resource. The BM-SC can send an individual notification to the Content Provider using the notification instance resource | +| Notifications | Collection Resource | Represents a collection of notification resources. | + +#### 5.2.4.1 Properties + +Each notification resource described in Table 5.2.4-1 has the set of properties described in Table 5.2.4.1-1. The BM-SC shall deliver the notifications as indicated by this structure using the API operations described in sub clause 5.2.4.2. + +Table 5.2.4.1-1 summarizes different properties of a notification resource. + +**Table 5.2.4.1-1: Resources for managing services at BM-SC** + +| Property Token | JSON Value Type | Parameter Description | +|---------------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| notification-res-id | string | Notification resource identifier | +| message-class | string |
Enumeration with the following values (may be expanded in the future):
Critical, Warning, Information, Service, Session. The message classes bear the following meaning:
Critical: When some event drastically prevent the proper delivery of content
Warning: When the service can be partially delivered but quality is reduced
Information: When the service is properly delivered but some interesting event occurred
Session/Service: Information about Service/Session related parameters
Table 5.2.4.1-x shows the information that can be notified for each of the message classes.
| +| message-name | string |Unique identifier of the message. Provides information about the message pertaining to the message-class of the notification
Table 5.2.4.1-2 shows the information that can be notified for each of the message classes and message names.
| +| Message-information | object |A dictionary of key values containing informations linked to the notification.
Every message-information dictionary shall include the following two keys:
date: The value of this key contains the UTC timestamp (in ms) of the date of the event
source: The value of this key is hierarchical colon separated format of services and sessions with the format "service-resource-identifier session-resource-identifier". If the notification is for a service, only the service-resource-identifier shall be included in this value. An empty value for this key shall represent a system wide notification.
Table 5.2.4.1-x shows the additional key value pairs that can be included in the message-information for each of the message-class and message-name.
| + +Table 5.2.4.1-2 shows the notification details that can be sent for each of the message classes. + +**Table 5.2.4.1-2: Notification Details for different message classes** + +| Message Class | Possible Message Name | Additional Key Value Pairs in message-information dictionary | +|----------------------|------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Critical | network-is-down | None | +| | service-badly-configured | bad-or-missing-parameters: [to-state:
where the from state and to state have one of the values in the enumeration:
Session Idle
Session Announced
Session Active
Session Terminated | +| | file-ready-for-transmission | file-url:
file-size:
transmission-size:
http-error-code:
Forbidden | Request cannot be fulfilled | The Content Provider may include optional text to indicate why the request could not be fulfilled | +| 404 Not
Found | Requested resource not found | None | +| Note: If "file-delivery-manifest-url" is used, and if there is any error code in response to the request to get the manifest from the provided URL, the session is not started. | | | + +## 6.3 Application Session + +### 6.3.1 General + +Application mode, including DASH service delivery shall use one of the two options in the following subclauses. + +### 6.3.2 Push Mode + +WebDAV as described in IETF RFC 4918 [9] or HTTP v1.1 shall be used over TLS. The Content Provider shall use PUT method with the resource (Application Session) or the Media Segment (DASH) in the message body, to place it at the push-url. The Content Provider shall ensure that each Segment is available at the BM-SC prior to its prescribed Segment availability start time in the MPD, or if that parameter is not provided, prior to the session start. Potential response codes and their interpretation is provided in Table 6.2.2-1. + +**Table 6.3.2-1: Response status code, message, and contents of Application (including DASH) Push mode** + +| Status Code | Message | Contents | +|------------------|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| 201 Created | File pushed successfully | None | +| 401 Unauthorized | Request requires user authorization | In accordance to conditions as described in IETF RFC 7231 [6] and IETF RFC 7235 [8] | +| 403 Forbidden | Request cannot be fulfilled | The Content Provider may include optional text to indicate why the request could not be fulfilled, e.g. incorrect URL was used | + +### 6.3.3 Pull Mode + +HTTP v1.1 shall be used over TLS in Pull mode. For DASH service, the BM-SC shall use the application-entry-point-url to retrieve the MPD. The BM-SC shall use GET method to request the resource, or for DASH, each Media Segment as defined by the MPD. Upon a successful GET, the Content Provider shall provide the requested resource or DASH Segment, respectively, in the response body. Potential response codes and their interpretation is provided in Table 6.2.3-1. + +**Table 6.3.3-1: Response status code, message, and contents of Application (including DASH) Pull mode** + +| Status Code | Message | Contents | +|------------------|--------------------------------------|---------------------------------------------------------------------------------------------------| +| 200 OK | The request has succeeded | The Content Provider shall send the requested resource or DASH Segment in the response body. | +| 401 Unauthorized | Request requires user authentication | In accordance to conditions as described in IETF RFC 7231 [6] and IETF RFC 7235 [8] | +| 403 Forbidden | Request cannot be fulfilled | The Content Provider may include optional text to indicate why the request could not be fulfilled | +| 404 Not Found | Requested resource not found | None | + +The BM-SC shall ensure that each DASH Media Segment is fully received prior to its prescribed availability start time, or if not provided, prior to the session start. + +Note: If "application-entry-point-url" is used, and if there is any error code in response to the request to get the MPD from the provided URL, the session shall not be started. + +## 6.4 RTP Streaming + +The Content Provider shall support PSS server functionality according to PSS as described in clause 5.3 of 3GPP TS 26.234 [5]. The streaming session shall be accessible prior to the start of the session. A URL to the SDP file that describes the streaming session between the Content Provider and the BM-SC is provided via the sdp-url, which shall be used for ingesting the streaming session. The SDP shall include the RTSP links for every media session as part of the "a=control" attribute to enable RTSP control of the session. The SDP shall also contain the required bitrate for each of the media sessions. + +When the user plane data is provided via UDP, then SRTP over DTLS as described in 3GPP TS 33.246 [24] shall be used for user plane protection. Establishment of TCP based user plane sessions with PSS is not supported. + +If there is any error retrieving the SDP, the session shall not be started. + +## 6.5 Transport + +For Transport sessions, the BM-SC shall activate the receivers on the indicated IP address and port numbers and shall ensure that firewall and NAT traversal is enabled on these IP addresses and port numbers as defined in the SDP retrieved from the sdp-url. If there is any error retrieving the SDP, the session shall not be started. All traffic shall use DTLS as specified in 3GPP TS 33.246 [24] where both client and server certificates are verified. + +# --- 7 Security + +## 7.1 Overview + +All xMB-C and xMB-U traffic shall only be sent over secured transport channels that are established after successful authentication and authorization as described in subclauses 4.4.2, 4.4.3 and 7.2. + +## 7.2 Authentication & Authorization + +(D)TLS as defined in 3GPP TS 33.246 [24] shall be used to authenticate both ends of the connection. + +The BM-SC shall support at least one of the two following modes for authorization of the Content Provider: *domain-based* or *user-based*, as defined in 3GPP TS 26.348 [33]. Authorization shall be performed after the successful completion of (D)TLS authentication. Domain-based authorization, as defined in Annex O.2 of 3GPP TS 33.246 [24], corresponds to the granting of access rights for service and/or session resource management at a coarse-grained level of the Content Provider, as identified by its administrative domain name in the subject field of the Content Provider certificate. User-based authorization, as defined in Annex O.2 of 3GPP TS 33.246 [24], corresponds to the granting of access rights for service/session resource management at a finer-grain level of an individual representative of the Content Provider. User-based authorization, if performed, shall occur after successful domain based authorization, and is based on HTTP Digest authentication of username and password as specified in IETF RFC 2617 [26]. Detailed specification of the authorization procedure and affiliated mechanisms (for example, pre-establishment of agreement between the Content Provider and mobile operator on domain- and user-based access rights, management of username and password credentials, etc.) are outside the scope of this specification, in order to allow flexibility of implementations which conform to the mechanism described herein. + +Authorization of the BM-SC by the Content Provider shall be based on the same mechanisms as described above for BM-SC authorization of the Content Provider. + +## 7.3 Void + +# 8 Notification Push to the Content Provider + +## 8.1 Introduction + +The Content Provider configures the BM-SC with a push-notification-url and push-notification-configuration property as documented in subclause 5.2.1.1, where the BM-SC can post the notifications to the Content Provider. + +## 8.2 Notification Post + +To send a notification to the Content Provider, the BM-SC shall use HTTP POST as follows: + +- the request URI with the "path" part is set to: {push-notification-url} HTTP/1.1 +- the Host field is set to the address of the Content Provider +- the Content-Type header field is set to "application/json" +- the body of the message is encoded in JSON format + +The {push-notification-url} in the URI above is the push notification URL configured by the Content Provider when the Content Provider configures the service using procedures described in subclause 5.2.1.2. The URL shall be an HTTPS URL. + +The content body of the above POST request shall contain the notification that the BM-SC intends to send to the Content Provider. The representation of the notification is based on the JSON schema of notification resource as described in subclause 5.2.4.1. + +Upon receipt of HTTP POST from the BM-SC to notify the Content Provider about a notification, the Content Provider shall check whether the BM-SC is authenticated and authorized to send notifications to the Content Provider. If the authorization fails, the Content Provider shall send a 401 message to the BM-SC. If the authorization is successful, the Content Provider shall accept the notification request and respond to the BM-SC with a 200 OK message indicating that it has received the notification from the BM-SC. If the request cannot be fulfilled, the Content Provider shall send a 403 Forbidden message to the BM-SC. + +The possible response messages from the Content Provider, depending on whether the notification request is accepted or not, are shown in Table 8.2-1. + +**Table 8.2-1: Response status code, message, and contents for notification request using HTTP POST** + +| Status Code | Message | Contents | +|------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|------------------------------------------------------------------------------------------------| +| 200 OK | The request has succeeded | None | +| 401
Unauthorized | Request requires user authentication | In accordance to conditions as described in IETF RFC 7231 [6] and IETF RFC 7235 [8] | +| 403
Forbidden | Request cannot be fulfilled | The Content Provider may include optional text to indicate why the request could not fulfilled | +| Note: In addition to the above response codes, the Content Provider can also send appropriate response codes described in IETF RFC 7231 [6] as applicable. | | | + +# 9 Feature negotiation + +## 9.1 General + +The xMB API needs to provide a mechanism to advertise required and optional features supported by both the Content Provider and BM-SC for interoperability reasons as the functionality of the xMB interface is augmented. + +Feature negotiation shall take place during service creation procedure and applies for a given instance of service and its related session(s), and any optionally associated reports and/or notifications associated with that service until the service is terminated. The Content Provider shall include in the HTTP POST the set of supported features as follows: + +- if a feature is required for the proper operation of the service, its associated session management, and reporting and/or notification functionality, if applicable, it shall be included within the 3gpp-Required-Features header; +- if a feature is optional for the proper operation of the service, its associated session management, and reporting and/or notification functionality, if applicable, it shall be included within the 3gpp-Optional-Features header. + +The BM-SC shall include, within the 3gpp-Accepted-Features header in the response to the HTTP POST, the set of features it supports in common with the Content Provider. + +If the BM-SC does not support any of the required features advertised by the Content-Provider within the 3gpp-Required-Features header, the BM-SC shall reject the HTTP POST with an HTTP 412 Precondition Failed status code and shall include the commonly supported features with the Content Provider within the 3gpp-Accepted-Features. + +If the BM-SC requires certain features to be supported that are not advertised by the Content Provider, the BM-SC shall reject the HTTP POST with an HTTP 412 Precondition Failed status code and shall include the commonly supported features with the Content Provider within the 3gpp-Accepted-Features and the required features in the 3gpp-required-features. + +If the BM-SC and Content Provider successfully negotiate supported features, the list of commonly supported features shall be applicable for the created service, related session(s) and any optionally associated reports and/or notifications, until it is deleted. Features that are not advertised as supported shall not be used for that service. + +The sender may send information that is related to the supported features. Any unrecognized/supported information shall be ignored by the receiver. + +The table below defines the features applicable to the xMB interface. + +**Table 9.1-1: Features used in xMB Interface** + +| Feature | M/O | Description | +|----------------------|--------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| LocalMBMS | O | The feature indicates the support of Local MBMS data delivery. | +| FilePush | O | The feature indicates the support of File Session Push Mode user plane procedures as specified in subclause 6.2.2 | +| FilePull | O | The feature indicates the support of File Session Pull Mode user plane procedures as specified in subclause 6.2.3 | +| ApplicationPush | O | The feature indicates the support of Application Push Mode user plane procedures as specified in subclause 6.3.2 | +| ApplicationPull | O | The feature indicates the support of Application Pull Mode user plane procedures as specified in subclause 6.3.3 | +| RTPStreaming | O | The feature indicates the support of RTPStreaming user plane procedures as specified in subclause 6.4 | +| Transport | O | The feature indicates the support of Transport user plane procedures as specified in subclause 6.5 | +| FEC | O | This feature indicates the support of applying FEC (see IETF RFC 6363 [29]) to downlink packet streams at the BM-SC. | +| ROHC | O | This feature indicates the support of applying ROHC (see IETF RFC 5795 [27] and IETF RFC 3095 [28]) to downlink packet streams at the BM-SC. | +| GroupContentDelivery | O | This feature indicates the support of delivering contents to a group of UEs. | +| MCExtension | O | This feature indicates the support of the xMB mission critical extension as specified in subclause 4.3.2 and subclause 5.2.2.1. | +| ResourceSharing | O | This feature indicates the support of sharing transmission resource for different MBMS services. | +| SaProfile | O | This feature indicates the support of BM-SC supplied Service Announcement profile. | +| FileRepair | O | This feature indicates the support of content provider supplied file repair function. | +| Feature: | A short name for the feature to which the M/O and description pertain. | | +| M/O: | Indication on whether the implementation of the feature is mandatory ("M") or optional ("O") in this 3GPP Release. | | +| Description: | Textual description of the feature. | | + +NOTE: The base functionality for the xMB interface is defined in the Release-14 version of this specification and a feature is an extension of that functionality. The negotiation of supported features allows interworking between the endpoints of the xMB interface whereby each entity may support all, some, or none of the features that the xMB application can support defined in this specification. Features are defined so that they are independent of each other. Any introduced feature is explicitly defined in this specification. + +## 9.2 HTTP custom headers + +This subclause defines any new HTTP custom headers introduced by this specification. + +### 9.2.1 3gpp-Optional-Features + +This header is used by the Content Provider to advertise the optional features that are supported by the Content Provider. + +The encoding of the header follows the ABNF as defined in IETF RFC 7231 [6]. + +`3gpp-Optional-Features = "3gpp-Optional-Features" ":" 1#token` + +n example is: `3gpp-Optional-Features: feature1, feature2` + +### 9.2.2 3gpp-Required-Features + +This header is used by the Content Provider to announce the mandatory features that must be supported in BM-SC. + +This header is also used by the BM-SC to indicate the missing features that must be supported in Content Provider. + +The encoding of the header follows the ABNF as defined in IETF RFC 7231 [6]. + +`3gpp-Required-Features = "3gpp-Required-Features" ":" 1#token` + +An example is: `3gpp-Required-Features: feature1, feature2` + +### 9.2.3 3gpp-Accepted-Features + +The header is used by the BM-SC to confirm the commonly supported set of features with the Content Provider. + +The encoding of the header follows the ABNF as defined in IETF RFC 7231 [6]. + +`3gpp-Accepted-Features = "3gpp-Accepted-Features" ":" 1#token` + +An example is: `3gpp-Accepted-Features: feature1, feature2` + +# --- 10 Using Common API Framework + +## 10.1 General + +When CAPIF is used with BM-SC, BM-SC shall support the following as defined in 3GPP TS 29.222 [40]: + +- the API exposing function and related APIs over CAPIF-2/2e and CAPIF-3 reference points; +- the API publishing function and related APIs over CAPIF-4 reference point; +- the API management function and related APIs over CAPIF-5 reference point; and +- at least one of the the security methods for authentication and authorization, and related security mechanisms. + +In a centralized deployment as defined in 3GPP TS 23.222 [39], where the CAPIF core function and API provider domain functions are co-located, the interactions between the CAPIF core function and API provider domain functions may be independent of CAPIF-3, CAPIF-4 and CAPIF-5 reference points. + +## 10.2 Security + +When CAPIF is used for external exposure, before invoking the API exposed by the BM-SC, the Content Provider as API invoker shall negotiate the security method (PKI, TLS-PSK or OAuth 2.0) with CAPIF core function and ensure the BM-SC has enough credential to authenticate the Content Provider (see 3GPP TS 29.222 [40], subclause 5.6.2.2 and subclause 6.2.2.2). + +If PKI or TLS-PSK is used as the selected security method between the Content Provider and the BM-SC, upon API invocation, the BM-SC shall retrieve the authorization information from the CAPIF core function as described in 3GPP TS 29.222 [40], subclause 5.6.2.4. + +As indicated in 3GPP TS 33.122 [41], the access to the xMB API may be authorized by means of the OAuth 2.0 protocol (see IETF RFC 6749 [42]), using the "Client Credentials" authorization grant, where the CAPIF core function (see 3GPP TS 29.222 [40]) plays the role of the authorization server. + +NOTE 1: In this release, only "Client Credentials" authorization grant is supported. + +If OAuth 2.0 is used as the selected security method between the Content Provider and the BM-SC, the Content Provider, prior to consuming services offered by the xMB API, shall obtain a "access token" from the authorization server, by invoking the Obtain\_Authorization service, as described in 3GPP TS 29.222 [40], subclause 5.6.2.3.2. + +The xMB API do not define any scopes for OAuth 2.0 authorization. It is the BM-SC responsibility to check whether the Content Provider is authorized to use an API based on the "token". Once the BM-SC verifies the "token", it shall check whether the BM-SC identifier in the "token" matches its own published identifier, and whether the API name in the "token" matches its own published API name. If those checks are passed, the Content Provider has full authority to access any resource or operation for the invoked API. + +NOTE 2: For aforementioned security methods, the BM-SC needs to apply admission control according to access control policies after performing the authorization checks. + +# --- Annex A (informative): Call Flows + +## A.1 Introduction + +The xMB-C procedures are used to create and control MBMS User Services from external sources. An MBMS User Service spans from the BM-SC to the UE and can contain one or more MBMS delivery methods. The provisioning procedure offer functions to create one or more delivery sessions (such as a MBMS Download Delivery session) and allows association of the delivery sessions to MBMS Bearer Services. As part of the xMB-C procedures for MBMS User Services, content ingestion for the user-plane data (i.e. xMB-U) are negotiated. As a result of the xMB-C procedures, the BM-SC can start service announcement and activates MBMS bearer services. + +The Content Provider can query its entitlements, for instance the list of broadcast areas it is authorized to use. + +The Content Provider can query the status of delivery sessions. + +The Content Provider can request reception statistics. + +## --- A.2 xMB Procedure example for Live DASH services (MBMS Broadcast only) + +This procedure example describes the xMB procedures for the delivery of a DASH Live service (see clause 11 of 3GPP TS 26.247 [18] for the specification of DASH Live services), to a single broadcast area. A push interface like WebDAV is used here as the ingestion method for the user-plane data (xMB-U). The push interface is identified by a unique URI. The source of the user plane data (CP Source) are the DASH Media Segments as produced by a Live Encoder / Segmenter and the source pushes each new Segment when it becomes available. The Media Presentation Description (MPD) URL and Initialization Segment (IS) for the Live DASH session is provided to BM-SC during Session creation or in a subsequent update request to the BM-SC. + + + +``` + +sequenceDiagram + participant UE + participant MBMS-GW + participant BM-SC + participant CP Control + participant CP Source + + Note over BM-SC: 2: BM-SC admin applies agreed ranges to BM-SC + Note over BM-SC: Provisioning a Live DASH Session + + Note over BM-SC: Creating a Service + BM-SC->>CP Control: 4: HTTP POST + CP Control-->>BM-SC: 5: HTTP 201 CREATED + BM-SC->>CP Control: 6: HTTP GET + CP Control-->>BM-SC: HTTP 200 OK + BM-SC->>CP Control: 7: HTTP PUT/PATCH + CP Control-->>BM-SC: HTTP 200 OK + + Note over BM-SC: Creating a Session + BM-SC->>CP Control: 8: HTTP POST + CP Control-->>BM-SC: 9: HTTP 201 CREATED + BM-SC->>CP Control: 10: HTTP GET + CP Control-->>BM-SC: HTTP 200 OK + BM-SC->>CP Control: 11: HTTP PUT/PATCH + CP Control-->>BM-SC: HTTP 200 OK + + BM-SC->>UE: 12: Do service announcement + Note right of MBMS-GW: (when all data present) + + Note over MBMS-GW: MBMS Bearer is activated + MBMS-GW->>BM-SC: 13: MBMS Session Start + BM-SC-->>MBMS-GW: Ok + BM-SC->>CP Control: 14: Notification + + Note over MBMS-GW: User Plane Data (DASH Segments) + MBMS-GW->>UE: 15: User Plane Data (DASH Segments) + + Note over MBMS-GW: MBMS Bearer is deactivated + MBMS-GW->>BM-SC: 16: MBMS Session Stop + BM-SC-->>MBMS-GW: Ok + BM-SC->>CP Control: 17: Notification + +``` + +Sequence diagram showing xMB-C and xMB-U procedures for a Live DASH Service. Lifelines: UE, MBMS-GW, BM-SC, CP Control, CP Source. The diagram includes steps for Service Level Agreement, session provisioning, service creation, session creation, service announcement, bearer activation, data delivery, bearer deactivation, and session stop. + +
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | + +### 8.2 SGsAP-ALERT-REJECT message + +This message is sent from the MME to the VLR to indicate that the MME could not identify the IMSI indicated in the SGsAP-ALERT-REQUEST message. Table 8.2.1 shows the content of the SGsAP-ALERT-REJECT message. + +**Table 8.2.1: SGsAP-ALERT-REJECT message content** + +| Information element | Type/Reference | Presence | Format | Length | +|---------------------|---------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | +| SGs Cause | SGs cause
9.4.18 | M | TLV | 3 | + +### 8.3 SGsAP-ALERT-REQUEST message + +This message is sent by the VLR to the MME to request an indication when the next activity of a UE is detected. Table 8.3.1 shows the content of the SGsAP-ALERT-REQUEST message. + +**Table 8.3.1: SGsAP-ALERT-REQUEST message content** + +| Information element | Type/Reference | Presence | Format | Length | +|---------------------|---------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | + +### 8.4 SGsAP-DOWNLINK-UNITDATA message + +This message is sent from the VLR to the MME to transparently relay a NAS message, from the VLR, to the UE. Table 8.4.1 shows the content of the SGsAP-DOWNLINK-UNITDATA message. + +**Table 8.4.1: SGsAP-DOWNLINK-UNITDATA message content** + +| Information element | Type/Reference | Presence | Format | Length | +|-----------------------|---------------------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | +| NAS message container | NAS message container
9.4.15 | M | TLV | 4-253 | + +## 8.5 SGsAP-EPS-DETACH-ACK message + +This message is sent by the VLR to the MME to acknowledge a previous SGsAP-EPS-DETACH-INDICATION message. Table 8.5.1 shows the content of the SGsAP-EPS-DETACH-ACK message. + +**Table 8.5.1: SGsAP-EPS-DETACH-ACK message content** + +| Information element | Type/Reference | Presence | Format | Length | +|---------------------|---------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | + +## 8.6 SGsAP-EPS-DETACH-INDICATION message + +This message is sent by the MME to the VLR to indicate an EPS detach performed from the UE or the MME. The type of detach is indicated in the IMSI detach from EPS service type information element. Table 8.6.1 shows the content of the SGsAP-EPS-DETACH-INDICATION message. + +**Table 8.6.1: SGsAP-EPS-DETACH-INDICATION message content** + +| Information element | Type/Reference | Presence | Format | Length | +|-----------------------------------|--------------------------------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | +| MME name | MME name
9.4.13 | M | TLV | 57 | +| IMSI detach from EPS service type | IMSI detach from EPS service type
9.4.7 | M | TLV | 3 | + +## 8.7 SGsAP-IMSI-DETACH-ACK message + +This message is sent by the VLR to the MME to acknowledge a previous SGsAP-IMSI-DETACH-INDICATION message. Table 8.7.1 shows the content of the SGsAP-IMSI-DETACH-ACK message. + +**Table 8.7.1: SGsAP-IMSI-DETACH-ACK message content** + +| Information element | Type/Reference | Presence | Format | Length | +|---------------------|---------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | + +## 8.8 SGsAP-IMSI-DETACH-INDICATION message + +This message is sent by the MME to the VLR to indicate an IMSI detach performed from the UE or the MME. The type of detach is indicated in the IMSI detach from non-EPS service type information element. Table 8.8.1 shows the content of the SGsAP-IMSI-DETACH-INDICATION message. + +**Table 8.8.1: SGsAP-IMSI-DETACH-INDICATION message content** + +| Information element | Type/Reference | Presence | Format | Length | +|---------------------------------------|------------------------------------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | +| MME name | MME name
9.4.13 | M | TLV | 57 | +| IMSI Detach from non-EPS service type | IMSI detach from non-EPS service type
9.4.8 | M | TLV | 3 | + +## 8.9 SGsAP-LOCATION-UPDATE-ACCEPT message + +### 8.9.1 Message definition + +This message is sent by the VLR to the MME to indicate that update or IMSI attach in the VLR has been completed. Table 8.9.1.1 shows the content of the SGsAP-LOCATION-UPDATE-ACCEPT message. + +**Table 8.9.1.1: SGsAP-LOCATION-UPDATE-ACCEPT message content** + +| Information element | Type/Reference | Presence | Format | Length | +|--------------------------|------------------------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | +| Location area identifier | Location area identifier
9.4.11 | M | TLV | 7 | +| New TMSI, or IMSI | Mobile identity
9.4.14 | O | TLV | 6-10 | + +### 8.9.2 New TMSI, or IMSI + +This information element represents the identity to be used for (and then by) the UE. + +If this information element is an IMSI, then the UE is not allocated any TMSI (and deletes any TMSI accordingly). If this information element is a TMSI, then the UE will use this TMSI as the new temporary identity (the UE deletes its old TMSI if available, and stores the new TMSI). If neither a TMSI nor an IMSI are included in this information element, the old TMSI, if any available, will be kept. + +## 8.10 SGsAP-LOCATION-UPDATE-REJECT message + +### 8.10.1 Message definition + +This message is sent by the VLR to the MME to indicate that location update or IMSI attach has failed. Table 8.10.1 shows the content of the SGsAP-LOCATION-UPDATE-REJECT message. + +**Table 8.10.1: SGsAP-LOCATION-UPDATE-REJECT message content** + +| Information element | Type/Reference | Presence | Format | Length | +|--------------------------|------------------------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | +| Reject cause | Reject cause
9.4.16 | M | TLV | 3 | +| Location area identifier | Location area identifier
9.4.11 | O | TLV | 7 | + +## 8.10.2 Location area identifier + +The VLR shall include this information element. + +# 8.11 SGsAP-LOCATION-UPDATE-REQUEST message + +## 8.11.1 Message definition + +This message is sent by the MME to the VLR either to request update of its location file (normal update) or to request IMSI attach. Table 8.11.1.1 shows the content of the SGsAP-LOCATION-UPDATE-REQUEST message. + +**Table 8.11.1.1: SGsAP-LOCATION-UPDATE-REQUEST message content** + +| Information element | Type/Reference | Presence | Format | Length | +|------------------------------|----------------------------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | +| MME name | MME name
9.4.13 | M | TLV | 57 | +| EPS location update type | EPS location update type
9.4.2 | M | TLV | 3 | +| New location area identifier | Location area identifier
9.4.11 | M | TLV | 7 | +| Old location area identifier | Location area identifier
9.4.11 | O | TLV | 7 | +| TMSI status | TMSI status
9.4.21 | O | TLV | 3 | +| IMEISV | IMEISV
9.4.5 | O | TLV | 10 | +| TAI | Tracking Area Identity
9.4.21a | O | TLV | 7 | +| E-CGI | E-UTRAN Cell Global Identity
9.4.3a | O | TLV | 9 | +| TMSI based NRI container | TMSI based NRI container
9.4.26 | O | TLV | 4 | +| Selected CS domain operator | Selected CS domain operator
9.4.27 | O | TLV | 5 | + +## 8.11.2 Old location area identifier + +The MME shall include this information element if the UE included the old location area information in the ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message. + +## 8.11.3 TMSI status + +The MME shall include this information element if the TMSI status received in the ATTACH REQUEST or TRACKING AREA UPDATING REQUEST message from the UE indicates that no valid TMSI is available in the UE. + +## 8.11.4 IMEISV + +The MME shall include this information element if the IMEISV is available in the MME. + +## 8.11.5 TAI + +If the TAI is available in the MME, the MME shall include this information element. + +## 8.11.6 E-CGI + +If the E-CGI is available in the MME, the MME shall include this information element. + +### 8.11.7 TMSI based NRI container + +This information element shall be included if the TMSI based NRI container has been received in the ATTACH REQUEST or TRACKING AREA UPDATING REQUEST message from the UE. + +### 8.11.8 Selected CS domain operator + +This information element shall be included if the network is configured to support gateway core network (GWCN) for CS domain, the preferred RAT of the selected PLMN for CS fallback is GERAN, and the UE does not support GERAN network sharing. + +## 8.12 SGsAP-MM-INFORMATION-REQUEST + +This message is sent by the VLR to the MME to provide the UE with subscriber specific information. Table 8.12.1 shows the content of the SGsAP-MM-INFORMATION-REQUEST message. + +**Table 8.12.1: SGsAP-MM-INFORMATION-REQUEST message content** + +| Information element | Type/Reference | Presence | Format | Length | +|---------------------|--------------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | +| MM information | MM information
9.4.12 | M | TLV | 3-n | + +## 8.13 SGsAP-PAGING-REJECT message + +This message is sent from the MME to the VLR to indicate that the delivery of a previous SGsAP-PAGING-REQUEST message has failed. Table 8.13.1 shows the content of the SGsAP-PAGING-REJECT message. + +**Table 8.13.1: SGsAP-PAGING-REJECT message content** + +| Information element | Type/Reference | Presence | Format | Length | +|---------------------|---------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | +| SGs Cause | SGs Cause
9.4.18 | M | TLV | 3 | + +## 8.14 SGsAP-PAGING-REQUEST message + +### 8.14.1 Message definition + +This message is sent from the VLR to the MME and contains sufficient information to allow the paging message to be transmitted by the correct cells at the correct time. Table 8.14.1.1 shows the content of the SGsAP-PAGING-REQUEST message. + +**Table 8.14.1.1: SGsAP-PAGING-REQUEST message content** + +| Information element | Type/Reference | Presence | Format | Length | +|------------------------------|----------------------------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | +| VLR name | VLR name
9.4.22 | M | TLV | 3-n | +| Service indicator | Service indicator
9.4.17 | M | TLV | 3 | +| TMSI | TMSI
9.4.20 | O | TLV | 6 | +| CLI | CLI
9.4.1 | O | TLV | 3-14 | +| Location area identifier | Location area identifier
9.4.11 | O | TLV | 7 | +| Global CN-Id | Global CN-Id
9.4.4 | O | TLV | 7 | +| SS code | SS code
9.4.19 | O | TLV | 3 | +| LCS indicator | LCS indicator
9.4.10 | O | TLV | 3 | +| LCS client identity | LCS client identity
9.4.9 | O | TLV | 3-n | +| Channel needed | Channel needed
9.4.23 | O | TLV | 3 | +| eMLPP Priority | eMLPP Priority
9.4.24 | O | TLV | 3 | +| Additional paging indicators | Additional paging indicators
9.4.25 | O | TLV | 3 | +| SM Delivery Timer | SM Delivery Timer
9.4.29 | O | TLV | 4 | +| SM Delivery Start Time | SM Delivery Start Time
9.4.30 | O | TLV | 6 | +| Maximum Retransmission Time | Maximum Retransmission Time
9.4.32 | O | TLV | 6 | + +## 8.14.2 TMSI + +This element is omitted in the exceptional case where paging with IMSI is performed. + +## 8.14.3 CLI + +If the Calling Line Identification is available in the VLR, the VLR shall include this information element. + +## 8.14.4 Location area identifier + +The VLR shall include this information element if the "Confirmed by Radio Contact" restoration indicator is set to "true". + +## 8.14.5 Global CN-Id + +If the network supports the Intra Domain Connection of RAN Nodes to multiple CN Nodes functionality, the VLR shall include this information element when the VLR initiates paging by IMSI, via the SGs interface. + +## 8.14.6 SS code + +The VLR shall include this information element if paging is due to a NW-initiated Call Independent SS procedure (see 3GPP TS 24.010 [9]). + +## 8.14.7 LCS indicator + +The VLR shall include this information element if the paging is due to a Mobile Terminated Location Request (see 3GPP TS 24.030 [11]). + +## 8.14.8 LCS client identity + +The VLR may include this information element if the paging is due to a Mobile Terminated Location Request (see 3GPP TS 24.030 [11]). If the paging is due to emergency positioning, then VLR should include this information element. + +## 8.14.9 Channel needed + +This information element shall be included if the VLR intends to indicate which channel the UE should use. + +## 8.14.10 eMLPP priority + +This information element shall be included if the VLR supports CSFB priority call handling and the call was received with eMLPP priority level indication. + +The eMLPP priority IE may be used to determine the required priority of a SCTP association for the associated SGsAP message. + +## 8.14.11 Additional paging indicators + +This information element shall be included if additional paging information e.g. CS restoration indicator needs to be passed to the MME. + +## 8.14.12 SM Delivery Timer + +For Deployment Option 2 (see subclause 8.2.4a.1 of 3GPP TS 23.272 [7]), this information element may be included if the Service Indicator IE indicates "SMS indicator" and the SM Delivery Timer and SM Delivery Start Time IEs were received from the SMS-GMSC as defined in 3GPP TS 24.010 [9]. + +## 8.14.13 SM Delivery Start Time + +For Deployment Option 2 (see subclause 8.2.4a.1 of 3GPP TS 23.272 [7]), this information element may be included if the Service Indicator IE indicates "SMS indicator" and the SM Delivery Timer and SM Delivery Start Time IEs were received from the SMS-GMSC as defined in 3GPP TS 24.010 [9]. + +## 8.14.4 Maximum Retransmission Time + +For Deployment Option 2 (see subclause 8.2.4a.1 of 3GPP TS 23.272 [7]), this information element may be included if the Service Indicator IE indicates "SMS indicator" and if the Maximum Retransmission Time IE was received from the SMS-GMSC as defined in 3GPP TS 29.002 [15]. + +# 8.15 SGsAP-RESET-ACK message + +## 8.15.1 Message definition + +This message is sent from the MME or the VLR to acknowledge a previous SGsAP-RESET-INDICATION message. This message indicates that all the SGs associations to the VLR or the MME have been marked as invalid. + +The sending entity (either the MME or the VLR) includes its identity in the form of a name in the SGsAP-RESET-ACK message. Table 8.15.1.1 shows the content of the SGsAP-RESET-ACK message. + +**Table 8.15.1.1: SGsAP-RESET-ACK message content** + +| Information element | Type/Reference | Presence | Format | Length | +|---------------------|---------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| MME name | MME name
9.4.13 | C | TLV | 57 | +| VLR name | VLR name
9.4.22 | C | TLV | 3-n | + +## 8.15.2 MME name + +If the MME is the sending entity, then the MME shall indicate its identity by including its MME name information element. Otherwise (i.e. if the VLR is the sending entity), then the VLR shall not include the MME name information element. + +## 8.15.3 VLR name + +If the VLR is the sending entity, then the VLR shall indicate its identity by including its VLR name information element. Otherwise (i.e. if the MME is the sending entity), then MME shall not include the VLR name information element. + +# 8.16 SGsAP-RESET-INDICATION message + +## 8.16.1 Message definition + +This message is sent from the VLR to the MME to indicate that a failure in the VLR has occurred and all the SGs associations to the VLR are to be marked as invalid. + +This message is also sent from the MME to the VLR to indicate that a failure in the MME has occurred and all the SGs associations to the MME are to be marked as invalid. + +The sending entity (either the MME or the VLR) includes its identity in the SGsAP-RESET-INDICATION message. Table 8.16.1.1 shows the content of the SGsAP-RESET-INDICATION message. + +**Table 8.16.1.1: SGsAP-RESET-INDICATION message content** + +| Information element | Type/Reference | Presence | Format | Length | +|---------------------|---------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| MME name | MME name
9.4.13 | C | TLV | 57 | +| VLR name | VLR name
9.4.22 | C | TLV | 3-n | + +## 8.16.2 MME name + +If the MME is the sending entity, then the MME shall indicate its identity by including its MME name information element. Otherwise (i.e. if the VLR is the sending entity), then the VLR shall not include the MME name information element. + +## 8.16.3 VLR name + +If the VLR is the sending entity, then the VLR shall indicate its identity by including its VLR name information element. Otherwise (i.e. if the MME is the sending entity), then the MME shall not include the VLR name information element. + +## 8.17 SGsAP-SERVICE-REQUEST message + +### 8.17.1 Message definition + +This message is sent from the MME to the VLR as a response to a previously received SGsAP-PAGING-REQUEST message to indicate the existence of a NAS signalling connection between the UE and the MME or to indicate to the VLR that the NAS signalling connection has been established after the paging procedure. Table 8.17.1 shows the content of the SGsAP-SERVICE-REQUEST message. + +**Table 8.17.1: SGsAP-SERVICE-REQUEST message content** + +| Information element | Type/Reference | Presence | Format | Length | +|----------------------------|----------------------------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | +| Service indicator | Service indicator
9.4.17 | M | TLV | 3 | +| IMEISV | IMEISV
9.4.5 | O | TLV | 10 | +| UE Time Zone | UE Time Zone
9.4.21b | O | TLV | 3 | +| Mobile Station Classmark 2 | Mobile Station Classmark 2
9.4.14a | O | TLV | 5 | +| TAI | Tracking Area Identity
9.4.21a | O | TLV | 7 | +| E-CGI | E-UTRAN Cell Global Identity
9.4.3a | O | TLV | 9 | +| UE EMM Mode | UE EMM mode
9.4.21c | O | TLV | 3 | + +### 8.17.2 IMEISV + +If the IMEISV is available in the MME, the MME shall include this information element. + +### 8.17.3 UE Time Zone + +If the UE Time Zone is available in the MME, the MME shall include this information element. + +### 8.17.4 Mobile Station Classmark 2 + +If the Mobile Station Classmark 2 is available in the MME, the MME shall include this information element. + +### 8.17.5 TAI + +If the TAI is available in the MME, the MME shall include this information element. + +### 8.17.6 E-CGI + +If the E-CGI is available in the MME, the MME shall include this information element. + +### 8.17.7 UE EMM Mode + +The MME shall include this information element. This information element indicates the EMM mode of the UE when the SGsAP-PAGING-REQUEST message was received by the MME. + +## 8.18 SGsAP-STATUS message + +### 8.18.1 Message definition + +This message is sent by both the VLR and the MME to indicate an error. The contents of SGsAP-STATUS message are shown in table 8.18.1.1. + +**Table 8.18.1.1: SGsAP-STATUS message content** + +| Information element | Type/Reference | Presence | Format | Length | +|---------------------|----------------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | O | TLV | 6-10 | +| SGs cause | SGs cause
9.4.18 | M | TLV | 3 | +| Erroneous message | Erroneous message
9.4.3 | M | TLV | 3-n | + +## 8.18.2 IMSI + +The MME shall include this information element if the IMSI is present in the erroneous message. + +## 8.19 SGsAP-TMSI-REALLOCATION-COMPLETE message + +This message is sent by the MME to the VLR to indicate that TMSI reallocation on the UE has been successfully completed. Table 8.19.1 shows the content of the SGsAP-TMSI-REALLOCATION-COMPLETE message. + +**Table 8.19.1: SGsAP-TMSI-REALLOCATION-COMPLETE message content** + +| Information element | Type/Reference | Presence | Format | Length | +|---------------------|---------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | + +## 8.20 SGsAP-UE-ACTIVITY-INDICATION message + +This message is sent by the MME to the VLR to indicate that activity from a UE has been detected. Table 8.20.1 shows the content of the SGsAP-UE-ACTIVITY-INDICATION message. + +**Table 8.20.1: SGsAP-UE-ACTIVITY-INDICATION message content** + +| Information element | Type/Reference | Presence | Format | Length | +|------------------------------|----------------------------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | +| Maximum UE Availability Time | Maximum UE Availability Time
9.4.28 | O | TLV | 6 | + +### 8.20.1 Maximum UE Availability Time + +For Deployment Option 2 (see subclause 8.2.4a.1 of 3GPP TS 23.272 [7]), the MME may include this information element to indicate the time until the UE is available. + +## 8.21 SGsAP-UE-UNREACHABLE message + +This message is sent from the MME to the VLR to indicate that, for example, paging could not be performed because the UE is marked as unreachable at the MME. Table 8.21.1 shows the content of the SGsAP-UE-UNREACHABLE message. + +**Table 8.21.1: SGsAP-UE-UNREACHABLE message content** + +| Information element | Type/Reference | Presence | Format | Length | +|--------------------------------------|------------------------------------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | +| SGs cause | SGs cause
9.4.18 | M | TLV | 3 | +| Requested Retransmission Time | Requested Retransmission Time
9.4.33 | O | TLV | 6 | +| Additional UE Unreachable indicators | Additional UE Unreachable indicators
9.4.31 | O | TLV | 3 | + +### 8.21.1 Requested Retransmission Time + +For Deployment Option 2 (see subclause 8.2.4a.1 of 3GPP TS 23.272 [7]), this information element may be included if the SGsAP-PAGING-REQUEST message included the Maximum Retransmission Time IE. + +### 8.21.2 Additional UE Unreachable indicators + +For Deployment Option 2 (see subclause 8.2.4a.1 of 3GPP TS 23.272 [7]), this information element may be included if the SGsAP-PAGING-REQUEST message includes the SM Delivery Timer and SM Delivery Start Time IEs and the UE is expected to be reachable before the time indicated by the SM Delivery Timer and SM Delivery Start Time IEs received in the SGsAP-PAGING-REQUEST message. + +## 8.22 SGsAP-UPLINK-UNITDATA message + +### 8.22.1 Message definition + +This message is sent from the MME to the VLR to transparently convey a NAS message, from the UE, to the VLR. Table 8.22.1 shows the content of the SGsAP-UPLINK-UNITDATA message. + +**Table 8.22.1: SGsAP-UPLINK-UNITDATA message content** + +| Information element | Type/Reference | Presence | Format | Length | +|----------------------------|----------------------------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | +| NAS message container | NAS message container
9.4.15 | M | TLV | 4-253 | +| IMEISV | IMEISV
9.4.5 | O | TLV | 10 | +| UE Time Zone | UE Time Zone
9.4.21b | O | TLV | 3 | +| Mobile Station Classmark 2 | Mobile Station Classmark 2
9.4.14a | O | TLV | 5 | +| TAI | Tracking Area Identity
9.4.21a | O | TLV | 7 | +| E-CGI | E-UTRAN Cell Global Identity
9.4.3a | O | TLV | 9 | + +### 8.22.2 IMEISV + +If the IMEISV is available in the MME, the MME shall include this information element. + +### 8.22.3 UE Time Zone + +If the UE Time Zone is available in the MME, the MME shall include this information element. + +## 8.22.4 Mobile Station Classmark 2 + +If the Mobile Station Classmark 2 is available in the MME, the MME shall include this information element. + +## 8.22.5 TAI + +If the TAI is available in the MME, the MME shall include this information element. + +## 8.22.6 E-CGI + +If the E-CGI is available in the MME, the MME shall include this information element. + +# 8.23 SGsAP-RELEASE-REQUEST message + +## 8.23.1 Message definition + +This message is sent by the VLR to the MME when the VLR determines that there are no more NAS messages to be exchanged between the VLR and the UE, or when a further exchange of NAS messages for the specified UE is not possible due to an error. Table 8.23.1 shows the content of the SGsAP-RELEASE-REQUEST message. + +**Table 8.23.1: SGsAP-RELEASE-REQUEST message content** + +| Information element | Type/Reference | Presence | Format | Length | +|---------------------|---------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | +| SGs cause | SGs cause
9.4.18 | O | TLV | 3 | + +## 8.23.2 SGs Cause + +The VLR shall include the SGs Cause to indicate an error. + +# 8.24 SGsAP-SERVICE-ABORT-REQUEST message + +## 8.24.1 Message definition + +This message is sent from the VLR to the MME to abort a mobile terminating CS fallback call during call establishment. Table 8.24.1.1 shows the content of the SGsAP-SERVICE-ABORT-REQUEST message. + +**Table 8.24.1.1: SGsAP-SERVICE-ABORT-REQUEST message content** + +| Information element | Type/Reference | Presence | Format | Length | +|---------------------|---------------------|----------|--------|--------| +| Message type | Message type
9.2 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | + +# 8.25 SGsAP-MO-CSFB-INDICATION message + +## 8.25.1 Message definition + +If the network is configured to support the return to the last used E-UTRAN PLMN after CS fallback, this message is sent from the MME to the VLR to indicate to the VLR that the UE initiated a service request for MO CS fallback. Table 8.25.1 shows the content of the SGsAP-MO-CSFB-INDICATION message. + +**Table 8.25.1: SGsAP-MO-CSFB-INDICATION message content** + +| Information element | Type/Reference | Presence | Format | Length | +|---------------------|----------------------------------------|----------|--------|--------| +| Message type | Message type
9.1 | M | V | 1 | +| IMSI | IMSI
9.4.6 | M | TLV | 6-10 | +| TAI | Tracking Area Identity
9.4.21a | O | TLV | 7 | +| E-CGI | E-UTRAN Cell Global Identity
9.4.3a | O | TLV | 9 | + +## 8.25.2 TAI + +If the TAI is available in the MME, the MME shall include this information element. + +## 8.25.3 E-CGI + +If the E-CGI is available in the MME, the MME shall include this information element. + +# 9 Information element coding + +## 9.1 Overview + +This clause specifies the coding of the information elements used in by the SGsAP protocol. + +The spare bits in the coding of an information element shall be set to zero by the sender and shall be ignored by the receiver. + +All unassigned codes (whether omitted or explicitly *Unassigned* in the text) shall be treated as unknown (see clause 7). + +## 9.2 Message type + +Message type uniquely identifies the message being sent. It is a single octet information element, mandatory in all messages. Table 9.2.1 defines the value part of the Message type information element. + +**Table 9.2.1: Message type information element** + +| 8 7 6 5 4 3 2 1 | Message type | Reference | +|------------------------------------------|------------------------------------------------|------------------| +| 0 0 0 0 0 0 0 0 | Unassigned: treated as an unknown Message type | 7 | +| 0 0 0 0 0 0 0 1 | SGsAP-PAGING-REQUEST | 8.14 | +| 0 0 0 0 0 0 1 0 | SGsAP-PAGING-REJECT | 8.13 | +| 0 0 0 0 0 0 1 1
to
0 0 0 0 0 1 0 1 | Unassigned: treated as an unknown Message type | 7 | +| 0 0 0 0 0 1 1 0 | SGsAP-SERVICE-REQUEST | 8.17 | +| 0 0 0 0 0 1 1 1 | SGsAP-DOWNLINK-UNITDATA | 8.4 | +| 0 0 0 0 1 0 0 0 | SGsAP-UPLINK-UNITDATA | 8.22 | +| 0 0 0 0 1 0 0 1 | SGsAP-LOCATION-UPDATE-REQUEST | 8.11 | +| 0 0 0 0 1 0 1 0 | SGsAP-LOCATION-UPDATE-ACCEPT | 8.9 | +| 0 0 0 0 1 0 1 1 | SGsAP-LOCATION-UPDATE-REJECT | 8.10 | +| 0 0 0 0 1 1 0 0 | SGsAP-TMSI-REALLOCATION-COMPLETE | 8.19 | +| 0 0 0 0 1 1 0 1 | SGsAP-ALERT-REQUEST | 8.3 | +| 0 0 0 0 1 1 1 0 | SGsAP-ALERT-ACK | 8.1 | +| 0 0 0 0 1 1 1 1 | SGsAP-ALERT-REJECT | 8.2 | +| 0 0 0 1 0 0 0 0 | SGsAP-UE-ACTIVITY-INDICATION | 8.20 | +| 0 0 0 1 0 0 0 1 | SGsAP-EPS-DETACH-INDICATION | 8.6 | +| 0 0 0 1 0 0 1 0 | SGsAP-EPS-DETACH-ACK | 8.5 | +| 0 0 0 1 0 0 1 1 | SGsAP-IMSI-DETACH-INDICATION | 8.8 | +| 0 0 0 1 0 1 0 0 | SGsAP-IMSI-DETACH-ACK | 8.7 | +| 0 0 0 1 0 1 0 1 | SGsAP-RESET-INDICATION | 8.16 | +| 0 0 0 1 0 1 1 0 | SGsAP-RESET-ACK | 8.15 | +| 0 0 0 1 0 1 1 1 | SGsAP-SERVICE-ABORT-REQUEST | 8.24 | +| 0 0 0 1 1 0 0 0 | SGsAP-MO-CSFB-INDICATION | 8.25 | +| 0 0 0 1 1 0 0 1
to
0 0 0 1 1 0 0 1 | Unassigned: treated as an unknown Message type | 7 | +| 0 0 0 1 1 0 1 0 | SGsAP-MM-INFORMATION-REQUEST | 8.12 | +| 0 0 0 1 1 0 1 1 | SGsAP-RELEASE-REQUEST | 8.23 | +| 0 0 0 1 1 1 0 0 | Unassigned: treated as an unknown Message type | 7 | +| 0 0 0 1 1 1 0 1 | SGsAP-STATUS | 8.18 | +| 0 0 0 1 1 1 1 0 | Unassigned: treated as an unknown Message type | 7 | +| 0 0 0 1 1 1 1 1 | SGsAP-UE-UNREACHABLE | 8.21 | + +## 9.3 Information element identifiers + +The next list shows the coding of the information element identifiers used in the present document. Table 9.3.1 shows the values assigned for the information element identifiers. + +**Table 9.3.1: Information element identifier coding** + +| 8 7 6 5 4 3 2 1 | Information element | Reference | +|-----------------|---------------------------------------|-----------| +| 0 0 0 0 0 0 0 1 | IMSI | 9.4.6 | +| 0 0 0 0 0 0 1 0 | VLR name | 9.4.22 | +| 0 0 0 0 0 0 1 1 | TMSI | 9.4.20 | +| 0 0 0 0 0 1 0 0 | Location area identifier | 9.4.11 | +| 0 0 0 0 0 1 0 1 | Channel Needed | 9.4.23 | +| 0 0 0 0 0 1 1 0 | eMLPP Priority | 9.4.24 | +| 0 0 0 0 0 1 1 1 | TMSI status | 9.4.21 | +| 0 0 0 0 1 0 0 0 | SGs cause | 9.4.18 | +| 0 0 0 0 1 0 0 1 | MME name | 9.4.13 | +| 0 0 0 0 1 0 1 0 | EPS location update type | 9.4.2 | +| 0 0 0 0 1 0 1 1 | Global CN-Id | 9.4.4 | +| 0 0 0 0 1 1 1 0 | Mobile identity | 9.4.14 | +| 0 0 0 0 1 1 1 1 | Reject cause | 9.4.16 | +| 0 0 0 1 0 0 0 0 | IMSI detach from EPS service type | 9.4.7 | +| 0 0 0 1 0 0 0 1 | IMSI detach from non-EPS service type | 9.4.8 | +| 0 0 0 1 0 1 0 1 | IMEISV | 9.4.5 | +| 0 0 0 1 0 1 1 0 | NAS message container | 9.4.15 | +| 0 0 0 1 0 1 1 1 | MM information | 9.4.12 | +| 0 0 0 1 1 0 1 1 | Erroneous message | 9.4.3 | +| 0 0 0 1 1 1 0 0 | CLI | 9.4.1 | +| 0 0 0 1 1 1 0 1 | LCS client identity | 9.4.9 | +| 0 0 0 1 1 1 1 0 | LCS indicator | 9.4.10 | +| 0 0 0 1 1 1 1 1 | SS code | 9.4.19 | +| 0 0 1 0 0 0 0 0 | Service indicator | 9.4.17 | +| 0 0 1 0 0 0 0 1 | UE Time Zone | 9.4.21b | +| 0 0 1 0 0 0 1 0 | Mobile Station Classmark 2 | 9.4.14a | +| 0 0 1 0 0 0 1 1 | Tracking Area Identity | 9.4.21a | +| 0 0 1 0 0 1 0 0 | E-UTRAN Cell Global Identity | 9.4.3a | +| 0 0 1 0 0 1 0 1 | UE EMM mode | 9.4.21c | +| 0 0 1 0 0 1 1 0 | Additional paging indicators | 9.4.25 | +| 0 0 1 0 0 1 1 1 | TMSI based NRI container | 9.4.26 | +| 0 0 1 0 1 0 0 0 | Selected CS domain operator | 9.4.27 | +| 0 0 1 0 1 0 0 1 | Maximum UE Availability Time | 9.4.28 | +| 0 0 1 0 1 0 1 0 | SM Delivery Timer | 9.4.29 | +| 0 0 1 0 1 0 1 1 | SM Delivery Start Time | 9.4.30 | +| 0 0 1 0 1 1 0 0 | Additional UE Unreachable indicators | 9.4.31 | +| 0 0 1 0 1 1 0 1 | Maximum Retransmission Time | 9.4.32 | +| 0 0 1 0 1 1 1 0 | Requested Retransmission Time | 9.4.33 | + +### 9.3a Length indicator + +The length indicator of the information elements consists of one octet and contains the binary encoding of the number of octets of the value part in the information elements. + +## 9.4 Information elements + +### 9.4.1 CLI + +This information element is used to represent calling line identification for the terminating call received in the CS domain. The CLI information element is coded as shown in figure 9.4.1.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3
To
Octet 14 | Octets 3 to 14 contain the value part of the Calling party BCD number information element defined in subclause 10.5.4.9 of 3GPP TS 24.008 [8] (octets 3 to 14, i.e. not including 3GPP TS 24.008 IEI and 3GPP TS 24.008 length indicator) | | | | | | | | + +Figure 9.4.1.1: Calling Line Identification information element + +## 9.4.2 EPS location update type + +The purpose of the EPS location update type information element is to indicate to the VLR whether an IMSI attach or a normal location update has been performed by the UE. The EPS location update type information element is coded as shown in figure 9.4.2.1 and table 9.4.2.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|--------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | EPS location update type value | | | | | | | | + +Figure 9.4.2.1: EPS location update type information element + +Table 9.4.2.1: EPS location update type information element value part + +| EPS location update type value (octet 3) | | +|------------------------------------------|-------------------------------------------------------------------------------------------------| +| Bits | | +| 8 7 6 5 4 3 2 1 | | +| 0 0 0 0 0 0 0 0 | Shall not be sent in this version of the protocol. If received, shall be treated as '000000010' | +| 0 0 0 0 0 0 0 1 | IMSI attach | +| 0 0 0 0 0 0 1 0 | Normal location update | +| 0 0 0 0 0 0 1 1 | to | +| 1 1 1 1 1 1 1 1 | | +| | Shall not be sent in this version of the protocol. If received, shall be treated as '000000010' | + +## 9.4.3 Erroneous message + +See subclause 18.4.5 in 3GPP TS 29.018 [16]. + +### 9.4.3a E-UTRAN Cell Global Identity + +The E-UTRAN Cell Global Identity information element indicates the UE's current E-UTRAN Cell Global Identity. The E-UTRAN Cell Global Identity information element is coded as shown in figure 9.4.3a.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3
- | The coding of the E-UTRAN Cell Global Identity value is according to ECGI field information element as specified in subclause 8.21.5 of 3GPP TS 29.274 [17A] | | | | | | | | +| Octet 9 | | | | | | | | | + +Figure 9.4.3a.1: E-UTRAN Cell Global Identity information element + +## 9.4.4 Global CN-Id + +See subclause 18.4.27 in 3GPP TS 29.018 [16]. + +## 9.4.5 IMEISV + +See subclause 18.4.9 in 3GPP TS 29.018 [16]. + +## 9.4.6 IMSI + +See subclause 18.4.10 in 3GPP TS 29.018 [16]. + +## 9.4.7 IMSI detach from EPS service type + +The IMSI detach from EPS service type information element indicates from MME to VLR the particular type of IMSI detach from EPS. The IMSI detach from EPS service type information element is coded as shown in figure 9.4.7.1 and table 9.4.7.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|-----------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | IMSI detach from EPS service type value | | | | | | | | + +Figure 9.4.7.1: IMSI detach from EPS service type information element + +Table 9.4.7.1: IMSI detach from EPS service type information element value + +| IMSI detach from EPS service type value (octet 3) | | | +|---------------------------------------------------|---|-----------------------------------------------------------------------| +| Bits | | | +| 8 | 7 | 6 5 4 3 2 1 | +| 0 | 0 | 0 0 0 0 0 0 0 Interpreted as reserved in this version of the protocol | +| 0 | 0 | 0 0 0 0 0 0 1 Network initiated IMSI detach from EPS services | +| 0 | 0 | 0 0 0 0 0 1 0 UE initiated IMSI detach from EPS services | +| 0 | 0 | 0 0 0 0 0 1 1 EPS services not allowed | +| 0 | 0 | 0 0 0 0 1 0 0 | +| to | | Interpreted as reserved in this version of the protocol | +| 1 | 1 | 1 1 1 1 1 1 1 | + +## 9.4.8 IMSI detach from non-EPS service type + +The IMSI detach from non-EPS service type information element indicates from MME to VLR the particular type of IMSI detach from non-EPS. The IMSI detach from non-EPS service type information element is coded as shown in figure 9.4.8.1 and table 9.4.8.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|---------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | IMSI detach from non-EPS service type value | | | | | | | | + +Figure 9.4.8.1: IMSI detach from non-EPS service type information element + +**Table 9.4.8.1: IMSI detach from non-EPS service type information element value** + +| IMSI detach from non-EPS service type value (octet 3) | | +|-------------------------------------------------------|----------------------------------------------------------------------| +| Bits | | +| 8 7 6 5 4 3 2 1 | | +| 0 0 0 0 0 0 0 0 | Interpreted as reserved in this version of the protocol | +| 0 0 0 0 0 0 0 1 | Explicit UE initiated IMSI detach from non-EPS services | +| 0 0 0 0 0 1 0 | Combined UE initiated IMSI detach from EPS and non-EPS services | +| 0 0 0 0 0 1 1 | Implicit network initiated IMSI detach from EPS and non-EPS services | +| 0 0 0 0 1 0 0 | to | +| to | | +| 1 1 1 1 1 1 1 | Interpreted as reserved in this version of the protocol | + +## 9.4.9 LCS client identity + +The LCS client identity information element is a compound parameter and comprises information related to the client of a LCS request. The LCS client identity information element is coded as shown in figure 9.4.9.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3
to
Octet n | The coding of the LCS client identity value is according to LCS-ClientID as specified in subclause 17.7.13 of 3GPP TS 29.002 [15] | | | | | | | | + +**Figure 9.4.9.1: LCS client identity information element** + +## 9.4.10 LCS indicator + +The LCS indicator information element indicates that the origin of the message is due to a LCS request and the type of this request. The LCS indicator information element is coded as shown in figure 9.4.10.1 and table 9.4.10.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|---------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | LCS indicator value | | | | | | | | + +**Figure 9.4.10.1: LCS indicator information element****Table 9.4.10.1: LCS indicator value** + +| LCS indicator | | +|-----------------|------------------------------------------------------| +| Bits | | +| 8 7 6 5 4 3 2 1 | | +| 0 0 0 0 0 0 0 0 | Normal, unspecified in this version of the protocol. | +| 0 0 0 0 0 0 0 1 | MT-LR | +| 0 0 0 0 0 1 0 | to | +| to | | +| 1 1 1 1 1 1 1 | Normal, unspecified in this version of the protocol | + +## 9.4.11 Location area identifier + +This element uniquely identifies one Location Area. The Location area identifier information element is coded as shown in figure 9.4.11.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3
-
Octet 7 | Octets 3 to 7 contain the value part of the Location area identification information element defined in 3GPP TS 24.008 [8] (starting with octet 2, i.e. not including 3GPP TS 24.008 IEI) | | | | | | | | + +Figure 9.4.11.1: Location area identifier information element + +## 9.4.12 MM information + +The MM information information element is a TLV information element that encapsulates the user information that the MME forwards to the UE. For the coding see subclause 18.4.16 in 3GPP TS 29.018 [16]. + +## 9.4.13 MME name + +The MME name information element specifies the MME name and is coded as shown in figure 9.4.13.1. Octets 3 through 57 contain MME node FQDN as specified in subclause 19.4.2.4 of 3GPP TS 23.003 [3]. The contents of octets 3 through 57 shall be coded as a fully qualified domain name (FQDN) as specified in subclause 19.4.2.1 of 3GPP TS 23.003 [3]. The value part of the MME name information element (not including IEI and length indicator) shall have a length of 55 octets. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-----------|-------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3 | Length field of the 1st label of the MME Name | | | | | | | | +| Octet 4 | Leftmost character of the 1st label of the MME name | | | | | | | | +| Octet 5 | - | | | | | | | | +| Octet m | Length field of the i-th label of the MME Name | | | | | | | | +| Octet m+1 | Leftmost character of the i-th label of the MME name | | | | | | | | +| Octet m+2 | - | | | | | | | | +| - | | | | | | | | | +| Octet 57 | Rightmost character of the last label of the MME Name | | | | | | | | + +Figure 9.4.13.1: MME name information element + +## 9.4.14 Mobile identity + +See subclause 18.4.17 in 3GPP TS 29.018 [16]. + +### 9.4.14a Mobile Station Classmark 2 + +With the exception of the IEI, the contents are specified in subclause 10.5.1.6 in 3GPP TS 24.008 [8]. + +## 9.4.15 NAS message container + +This information element is used to encapsulate the SMS messages transferred between the VLR and the MME. The NAS message container information element is coded as shown in figure 9.4.15.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------------------|-------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3
to
Octet 253 | Octets 3 to 253 contain the SMS message (i.e. CP-DATA, CP-ACK or CP-ERROR) as defined in subclause 7.2 of 3GPP TS 24.011 [10] | | | | | | | | + +Figure 9.4.15.1: NAS message container information element + +## 9.4.16 Reject cause + +See subclause 18.4.21 in 3GPP TS 29.018 [16]. + +## 9.4.17 Service indicator + +This information element indicates the type of the CS service (e.g. voice call, Short Message Service). The Service indicator information element is coded as shown in figure 9.4.17.1 and table 9.4.17.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|-------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | Service indicator value | | | | | | | | + +Figure 9.4.17.1: Service indicator information element + +Table 9.4.17.1: Service indicator value + +| Service indicator | | +|-------------------|------------------------------------------------------------------------------------------------| +| Bits | | +| 8 7 6 5 4 3 2 1 | | +| 0 0 0 0 0 0 0 0 | Shall not be sent in this version of the protocol. If received, shall be treated as '00000001' | +| 0 0 0 0 0 0 0 1 | CS call indicator | +| 0 0 0 0 0 0 1 0 | SMS indicator | +| 0 0 0 0 0 0 1 1 | to | +| 1 1 1 1 1 1 1 1 | | +| | Shall not be sent in this version of the protocol. If received, shall be treated as '00000001' | + +## 9.4.18 SGs cause + +The purpose of the SGs cause information element is to indicate an error to the receiving entity. This could be a protocol data error, to indicate to the VLR the reason why a paging procedure could not be performed or to indicate to the VLR that the mobile terminating CS fallback call has been rejected by the user. The SGs cause information element is coded as shown in figure 9.4.18.1 and table 9.4.18.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | SGs cause value | | | | | | | | + +Figure 9.4.18.1: SGs cause information element + +**Table 9.4.18.1: SGs cause information element value part** + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|----------------------------------------------------------| +| SGs cause value (octet 3) | | | +| Bits | | | +| 8 7 6 5 4 3 2 1 | | | +| 0 0 0 0 0 0 0 0 | | Normal, unspecified in this version of the protocol. | +| 0 0 0 0 0 0 0 1 | | IMSI detached for EPS services | +| 0 0 0 0 0 0 1 0 | | IMSI detached for EPS and non-EPS services | +| 0 0 0 0 0 0 1 1 | | IMSI unknown | +| 0 0 0 0 0 1 0 0 | | IMSI detached for non-EPS services | +| 0 0 0 0 0 1 0 1 | | IMSI implicitly detached for non-EPS services | +| 0 0 0 0 0 1 1 0 | | UE unreachable | +| 0 0 0 0 0 1 1 1 | | Message not compatible with the protocol state | +| 0 0 0 0 1 0 0 0 | | Missing mandatory information element | +| 0 0 0 0 1 0 0 1 | | Invalid mandatory information | +| 0 0 0 0 1 0 1 0 | | Conditional information element error | +| 0 0 0 0 1 0 1 1 | | Semantically incorrect message | +| 0 0 0 0 1 1 0 0 | | Message unknown | +| 0 0 0 0 1 1 0 1 | | Mobile terminating CS fallback call rejected by the user | +| 0 0 0 0 1 1 1 0 | | UE temporarily unreachable | +| 0 0 0 0 1 1 1 1 | to | Normal, unspecified in this version of the protocol | +| 1 1 1 1 1 1 1 1 | | | +| NOTE: "Normal, unspecified" has the same meaning than in 3GPP TS 24.008 [8], informative Annex H (UMTS specific cause values for call control). It is used to report a normal event, and should not be interpreted as syntactically incorrect nor unknown if received. | | | + +## 9.4.19 SS code + +The SS code information element is used to represent the code identifying a single supplementary service, a group of supplementary services, or all supplementary services. The SS code information element is coded as shown in figure 9.4.19.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|-----------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | The coding of the SS code value is according to SS-Code as specified in subclause 17.7.5 of 3GPP TS 29.002 [15] | | | | | | | | + +**Figure 9.4.19.1: SS code information element** + +## 9.4.20 TMSI + +See subclause 18.4.23 in 3GPP TS 29.018 [16]. + +## 9.4.21 TMSI status + +See subclause 18.4.24 in 3GPP TS 29.018 [16]. + +## 9.4.21a Tracking Area Identity + +This element uniquely identifies one Tracking Area. The Tracking Area Identity information element is coded as shown in figure 9.4.21a.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | Octets 3 to 7 contain the value part of the Tracking Area Identity information element defined in 3GPP TS 24.301 [14] (starting with octet 2, i.e. not including 3GPP TS 24.301 IEI) | | | | | | | | +| Octet 7 | | | | | | | | | + +**Figure 9.4.21a.1: Tracking Area Identity information element** + +## 9.4.21b UE Time Zone + +This element identifies the offset between universal time and local time in steps of 15 minutes. The UE Time Zone information element is coded as shown in figure 9.4.21b.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | E | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | The coding of the UE Time Zone value is according to value part of the Time Zone information element as specified in subclause 10.5.3.8 of 3GPP TS 24.008 [8] (i.e. not including 3GPP TS 24.008 E ) | | | | | | | | + +**Figure 9.4.21b.1: UE Time Zone information element** + +## 9.4.21c UE EMM mode + +The UE EMM mode information element is used by MME to indicate to the VLR the EMM mode of the UE upon reception of the SGsAP-PAGING-REQUEST message. The UE EMM mode information element is coded as shown in figure 9.4.21c.1 and table 9.4.21c.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|-------------------|---|---|---|---|---|---|---| +| Octet 1 | E | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | UE EMM mode value | | | | | | | | + +**Figure 9.4.21c.1: UE EMM mode information element****Table 9.4.21c.1: UE EMM mode value** + +| | | | +|-----------------------------|---|---------------------------------------------------------| +| UE EMM mode value (octet 3) | | | +| Bits | | | +| 8 | 7 | 6 5 4 3 2 1 | +| 0 | 0 | 0 0 0 0 0 0 0 EMM-IDLE | +| 0 | 0 | 0 0 0 0 0 0 1 EMM-CONNECTED | +| 0 | 0 | 0 0 0 0 0 1 0 | +| to | | Interpreted as reserved in this version of the protocol | +| 1 | 1 | 1 1 1 1 1 1 1 | + +## 9.4.22 VLR name + +The VLR name information element specifies the VLR name and is coded as shown in figure 9.4.22.1. The contents of octets 3 through n shall be coded as a fully qualified domain name (FQDN) as specified in 3GPP TS 23.003 [3]. + +NOTE: In earlier releases of this specification, the coding of VLR Name was not clear. Implementations based on earlier releases that encode VLR Name as a string with labels separated by dot can exist. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-----------|-------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length Indicator | | | | | | | | +| Octet 3 | Length field of the 1st label of the VLR Name | | | | | | | | +| Octet 4 | Leftmost character of the 1st label of the VLR name | | | | | | | | +| Octet 5 | - | | | | | | | | +| Octet m | Length field of the i-th label of the VLR Name | | | | | | | | +| Octet m+1 | Leftmost character of the i-th label of the VLR name | | | | | | | | +| Octet m+2 | - | | | | | | | | +| - | | | | | | | | | +| Octet n | Rightmost character of the last label of the VLR Name | | | | | | | | + +Figure 9.4.22.1: VLR name information element + +## 9.4.23 Channel needed + +See subclause 18.4.2 in 3GPP TS 29.018 [16]. + +## 9.4.24 eMLPP priority + +See subclause 18.4.4 in 3GPP TS 29.018 [16]. + +## 9.4.25 Additional paging indicators + +The Additional paging indicators information element provides additional information during the paging procedure. The Additional paging indicators information element is coded as shown in figure 9.4.25.1 and table 9.4.25.1. + +The Additional paging indicators is a type 4 information element with a length of 3 octets. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------|------------------|---|---|---|---|---|---|------| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | CSRI | +| | Spare | | | | | | | | + +Figure 9.4.25.1: Additional paging indicators information element + +Table 9.4.25.1: Additional paging indicators value + +| | +|------------------------------------------------------------------| +| Additional paging indicators value (octet 3, bit 1) | +| Bits | +| 1 | +| 0 CS restoration indicator (CSRI) is not set | +| 1 CS restoration indicator (CSRI) is set | +| Bits 8 to 2 of octet 3 are spare and shall be all coded as zero. | + +## 9.4.26 TMSI based NRI container + +See subclause 18.4.28 in 3GPP TS 29.018 [16]. + +## 9.4.27 Selected CS domain operator + +The selected CS domain operator information element indicates the CS domain operator selected by the MME when CS domain is configured for gateway core network (GWCN), the preferred RAT of the selected PLMN for CS fallback is GERAN, and the UE does not support GERAN network sharing. The selected CS domain operator information element is coded as shown in figure 9.4.27.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|---------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3
-
Octet 5 | Coded as octets 2 to 4 of the Location Area Identification IE, defined in 3GPP TS 24.008 [8] (not including 3GPP TS 24.008 IEI and LAC). | | | | | | | | + +Figure 9.4.27.1: Selected CS domain operator information element + +## 9.4.28 Maximum UE Availability Time + +For Deployment Option 2 (see subclause 8.2.4a.1 of 3GPP TS 23.272 [7]), the Maximum UE Availability Time IE indicates the (UTC) time until which a UE using eDRX is expected to be reachable. The Maximum UE Availability Time IE is coded as shown in figure 9.4.28.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3
to
Octet 6 | Maximum UE Availability Time value, encoded as the Maximum UE Availability Time IE in subclause 12.4.2 of 3GPP TS 29.002 [15]. | | | | | | | | + +Figure 9.4.28.1: Maximum UE Availability Time information element + +## 9.4.29 SM Delivery Timer + +For Deployment Option 2 (see subclause 8.2.4a.1 of 3GPP TS 23.272 [7]), this IE identifies, together with the SM Delivery Start Time, the time until which the VLR buffers the Short Message. The SM Delivery Timer IE is coded as shown in figure 9.4.29.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------------------------------|----------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3
to
Octet 4 | SM Delivery Timer value, encoded as the SM Delivery Timer IE in subclause 12.9.2 of 3GPP TS 29.002 [15]. | | | | | | | | + +Figure 9.4.29.1: SM Delivery Timer information element + +## 9.4.30 SM Delivery Start Time + +For Deployment Option 2 (see subclause 8.2.4a.1 of 3GPP TS 23.272 [7]), this IE identifies, together with the SM Delivery Timer, the time until which the VLR buffers the Short Message. The SM Delivery Start Time IE is coded as shown in figure 9.4.30.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------------------------------|--------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3
to
Octet 6 | SM Delivery Start Time value, encoded as the SM Delivery Start Time IE in subclause 12.9.2 of 3GPP TS 29.002 [15]. | | | | | | | | + +Figure 9.4.30.1: SM Delivery Start Time information element + +### 9.4.31 Additional UE Unreachable indicators + +For Deployment Option 2 (see subclause 8.2.4a.1 of 3GPP TS 23.272 [7]), the Additional UE Unreachable indicators information element provides additional information during the paging for non-EPS services procedure. The Additional UE Unreachable indicators information element is coded as shown in figure 9.4.31.1 and table 9.4.31.1. + +The Additional UE Unreachable indicators is a type 4 information element with a length of 3 octets. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|----------------|------------------|---|---|---|---|---|---|-------| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | SMBRI | +| | Spare | | | | | | | | + +**Figure 9.4.31.1: Additional UE Unreachable indicators information element** + +**Table 9.4.31.1: Additional UE Unreachable indicators value** + +| | +|------------------------------------------------------------------| +| Additional paging indicators value (octet 3, bit 1) | +| Bits | +| 1 | +| 0 SM Buffer Request Indicator (SMBRI) is not set | +| 1 SM Buffer Request Indicator (SMBRI) is set | +| Bits 8 to 2 of octet 3 are spare and shall be all coded as zero. | + +### 9.4.32 Maximum Retransmission Time + +For Deployment Option 2 (see subclause 8.2.4a.1 of 3GPP TS 23.272 [7]), the Maximum Retransmission Time IE indicates the time until which the SMS-GMSC is capable to retransmit the Short Message. The Maximum Retransmission Time IE is coded as shown in figure 9.4.32.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3
to
Octet 6 | Maximum Retransmission Time value, encoded as the Maximum Retransmission Time IE in subclause 12.9.2 of 3GPP TS 29.002 [15]. | | | | | | | | + +**Figure 9.4.32.1: Maximum Retransmission Time information element** + +### 9.4.33 Requested Retransmission Time + +For Deployment Option 2 (see subclause 8.2.4a.1 of 3GPP TS 23.272 [7]), the Requested Retransmission Time IE indicates the time at which the MME requests the SMS-GMSC to retransmit the Short Message. The Requested Retransmission Time IE is coded as shown in figure 9.4.33.1. + +| | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | +|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------|---|---|---|---|---|---|---| +| Octet 1 | IEI | | | | | | | | +| Octet 2 | Length indicator | | | | | | | | +| Octet 3
to
Octet 6 | Requested Retransmission Time value, encoded as the Requested Retransmission Time IE in subclause 12.9.2 of 3GPP TS 29.002 [15]. | | | | | | | | + +**Figure 9.4.33.1: Requested Retransmission Time information element** + +## 10 List of system variables + +### 10.1 Timers + +This subclause lists the management timers specified for the operation of the SGsAP protocol. All the implementation shall support the range of values specified in table 10.1.1 or table 10.1.2 as appropriate. The specific value of the timers is under the control of the operator. + +**Table 10.1.1: Management timers – MME side** + +| Timer name | Default value | Timer range | Granularity | Notes | Relation to other timers | +|------------|---------------|----------------|-------------|------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Ts6-1 | - | 10 s to 90 s | 1 s | Guards the Location Update procedure. | It is expected to take a value greater than 2 times the maximum transmission time in the SGs interface, plus the supervision timer of the Update Location procedure (as defined in 3GPP TS 29.002 [15]) | +| Ts8 | 4 s | 1s to 30 s | 1 s | Guards the Explicit IMSI detach from EPS services procedure. | None. | +| Ts9 | 4 s | 1-30 s | 1 s | Guards the Explicit IMSI detach from non-EPS services procedure. | None. | +| Ts10 | 4 s | 1-30 s | 1 s | Guards the Implicit IMSI detach from non-EPS services procedure. | None. | +| Ts12-1 | - | 8 - 60x384+8 s | 1 min | Controls the resetting of the 'MME-Reset' variable. | It is expected to take a value greater than the longest periodic tracking area update timer running on the MME, plus the transmission delay on the radio interface. | +| Ts12-2 | 4 s | 1-120 s | 1 s | Guards the MME reset procedure. There is one Ts12-2 timer per VLR for which the MME has a SGs association. | None. | +| Ts13 | 4 s | 1-30 s | 1 s | Guards the Implicit IMSI detach from EPS services procedure. | None. | + +NOTE: The Default value is the recommended value. + +**Table 10.1.2: Management timers – VLR side** + +| Timer name | Default value | Timer range | Granularity | Notes | Relation to other timers | +|------------|---------------|----------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Ts5 | - | 2 s to 20 s | 100 ms | Guards the Paging procedure at the VLR. | Value is correlated to paging cycle. The default is set according to maximum paging cycle supported by the MME (operator choice) as defined in 3GPP TS 36.331 [19]. | +| Ts6-2 | 40 s | 5 s to 60 s | 1 s | Guards the TMSI reallocation procedure. | It is expected to take a value greater than 2 times the maximum transmission time in the SGs interface, plus 4 times T3450 (as defined in 3GPP TS 24.301 [14]). The T3450 value to use in the calculation is the value for cases without coverage enhancement. | +| Ts7 | 4 s | 1 s to 30 s | 1 s | Guards the Non-EPS alert procedure. | None. | +| Ts11 | 4 s | 1-120 s | 1 s | Guards the VLR reset procedure. There is one Ts11 timer per MME for which the VLR has a SGs association. | None. | +| Ts14 | - | 5 s to 20 s (NOTE 2) | 1 s | Guards the MT UE fallback procedure to UTRAN/GERAN | It is expected to take a value greater than T3417ext-mt. Otherwise, the UE can attempt to select GERAN/UTRAN although the call is already released. | +| Ts15 | - | 1 s to 20 s (NOTE 2) | 1 s | Guards the MO UE fallback procedure to UTRAN/GERAN when the network is configured to support the return to the last used E-UTRAN PLMN after CS fallback | None. | + +NOTE 1: The Default value is the recommended value. +NOTE 2: If a too small value is configured, the timer can expire before a successful fallback to UTRAN/GERAN occurs. + +## 10.2 Retry counters + +This subclause lists the management retry counters specified for the operation of the SGsAP protocol. The values in table 10.2.1 and table 10.2.2 are recommended values. + +**Table 10.2.1: Management retry counters – VLR side** + +| Retry counter name | Retry value | +|--------------------|-------------| +| Ns7 | 2 | +| Ns11 | 2 | + +**Table 10.2.2: Management retry counters – MME side** + +| Retry counter name | Retry value | +|--------------------|-------------| +| Ns8 | 2 | +| Ns9 | 2 | +| Ns10 | 2 | +| Ns12 | 2 | + +## Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|---------------|-----------|------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | R
e
v | Subject/Comment | Old | New | +| 2008-06 | | | | | Draft skeleton provided by rapporteur. | - | 0.0.0 | +| 2008-06 | CT1#54 | | | | Includes the following contributions agreed by CT1:
C1-082435, C1-082710 | 0.0.0 | 0.1.0 | +| 2008-08 | CT1#55 | | | | Includes the following contributions agreed by CT1:
C1-083518, C1-083519, C1-083520, C1-083521, C1-083523, C1-083586 | 0.1.0 | 0.2.0 | +| 2008-09 | e-mail review | | | | Added newly assigned TS number and updated title and scope for correct definition of VLR acronym. | 0.2.0 | 0.2.1 | +| 2008-10 | CT1#55 bis | | | | Includes the following contributions agreed by CT1:
C1-083821, C1-083822, C1-083824, C1-084195, C1-084199, C1-084300, C1-084301, C1-084302, C1-084303, C1-084304, C1-084305, C1-084306, C1-084307, C1-084312, C1-084314, C1-084483, C1-084485, C1-084486, C1-084487, C1-084488 | 0.2.1 | 0.3.0 | +| 2008-11 | CT1#56 | | | | Includes the following contributions agreed by CT1:
C1-084709, C1-084719, C1-084722, C1-085182, C1-085194, C1-085195, C1-085196, C1-085197, C1-085301, C1-085302, C1-085303, C1-085311, C1-085522
Changes by the rapporteur:
- correction of title for 3GPP TS 22.101 and 3GPP TS 32.422 in references subclause
- information element identifiers for LCS client identity, LCS indicator, MM information and SS code added to table 9.3.1
- details for coding of LCS client identity moved to figure 9.4.9.1 and details for coding of SS code moved to figure 9.4.19.1
- editorial corrections to align with drafting rules | 0.3.0 | 0.4.0 | +| 2008-11 | | | | | Version 1.0.0 created for presentation to CT#42 for information and approval | 0.4.0 | 1.0.0 | +| 2008-12 | CT#42 | | | | Version 8.0.0 created after approval in CT#42 | 1.0.0 | 8.0.0 | +| 2009-03 | CT#43 | CP-090154 | 0001 | 2 | Handle of CSFB paging procedure when UE is in connected mode | 8.0.0 | 8.1.0 | +| 2009-03 | CT#43 | CP-090154 | 0002 | | SGs paging with access control in E-UTRAN | 8.0.0 | 8.1.0 | +| 2009-03 | CT#43 | CP-090154 | 0003 | 2 | Clarifications of paging procedure in MME | 8.0.0 | 8.1.0 | +| 2009-03 | CT#43 | CP-090154 | 0004 | 1 | Consistent usage of HSS | 8.0.0 | 8.1.0 | +| 2009-03 | CT#43 | CP-090154 | 0005 | | Location update for non-EPS services procedure: failure and abnormal cases | 8.0.0 | 8.1.0 | +| 2009-03 | CT#43 | CP-090154 | 0006 | 1 | Clarifications for MM information procedure | 8.0.0 | 8.1.0 | +| 2009-03 | CT#43 | CP-090154 | 0007 | 1 | VLR number derivation | 8.0.0 | 8.1.0 | +| 2009-03 | CT#43 | CP-090154 | 0008 | 3 | Abnormal conditions for UL and DL Unitdata procedures | 8.0.0 | 8.1.0 | +| 2009-03 | CT#43 | CP-090154 | 0009 | 1 | MME behaviour when receiving paging for SMS | 8.0.0 | 8.1.0 | +| 2009-03 | CT#43 | CP-090154 | 0010 | 1 | Adding IE details | 8.0.0 | 8.1.0 | +| 2009-03 | CT#43 | CP-090154 | 0011 | 2 | Corrections in state models for VLR/MME | 8.0.0 | 8.1.0 | +| 2009-03 | CT#43 | CP-090154 | 0012 | 2 | SS handling details in VLR | 8.0.0 | 8.1.0 | +| 2009-03 | CT#43 | CP-090154 | 0013 | 2 | IE of paging request | 8.0.0 | 8.1.0 | +| 2009-03 | CT#43 | CP-090154 | 0014 | 1 | Corrections and additions for procedures for SMS delivery over SGs | 8.0.0 | 8.1.0 | +| 2009-06 | CT#44 | CP-090421 | 0017 | | Removing Editor's note on EPS location update type | 8.1.0 | 8.2.0 | +| 2009-06 | CT#44 | CP-090421 | 0019 | 1 | Correction of the location update initiation | 8.1.0 | 8.2.0 | +| 2009-06 | CT#44 | CP-090421 | 0021 | 1 | Paging Procedure when MME restarts | 8.1.0 | 8.2.0 | +| 2009-06 | CT#44 | CP-090421 | 0022 | | Forward of CS paging to the SGSN when ISR is activated | 8.1.0 | 8.2.0 | +| 2009-09 | CT#45 | CP-090674 | 0023 | | Correction to the Location update for non-EPS services procedure in the MME | 8.2.0 | 8.3.0 | +| 2009-09 | CT#45 | CP-090674 | 0024 | 1 | Support multiple SCTP associations | 8.2.0 | 8.3.0 | +| 2009-09 | CT#45 | CP-090674 | 0025 | | Port number and payload protocol identifier for SGsAP | 8.2.0 | 8.3.0 | +| 2009-09 | CT#45 | CP-090674 | 0026 | | The usage of timer Ns12 | 8.2.0 | 8.3.0 | +| 2009-09 | CT#45 | CP-090674 | 0027 | | Corrections for the length of IE | 8.2.0 | 8.3.0 | +| 2009-09 | CT#45 | CP-090674 | 0028 | 2 | Clarification of Location Update | 8.2.0 | 8.3.0 | +| 2009-09 | CT#45 | CP-090675 | 0029 | 2 | Update for 'SMS-only' behaviour | 8.2.0 | 8.3.0 | +| 2009-09 | CT#45 | CP-090674 | 0031 | 2 | Clarify the condition for starting the location update for non-EPS services procedure | 8.2.0 | 8.3.0 | +| 2009-09 | CT#45 | CP-090675 | 0033 | 1 | SMS over SGs charging and authority enquiry parameters | 8.2.0 | 8.3.0 | +| 2009-09 | CT#46 | CP-090916 | 0036 | 1 | Paging procedure in MME for supporting SMS only | 8.3.0 | 8.4.0 | +| 2009-09 | CT#46 | CP-090916 | 0037 | 1 | Location update initiation for SMS over SGs only | 8.3.0 | 8.4.0 | +| 2009-09 | CT#46 | CP-090915 | 0038 | 6 | Corrections for SGs Service Request | 8.3.0 | 8.4.0 | +| 2009-09 | CT#46 | CP-090916 | 0039 | 2 | Correction for Online and offline charging parameters | 8.3.0 | 8.4.0 | +| 2009-09 | CT#46 | CP-090915 | 0040 | 1 | Correction of definition of MME name | 8.3.0 | 8.4.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|--------------------------------------------------------------------------------------------------------------|--------|--------| +| 2009-09 | CT#46 | CP-090915 | 0041 | 1 | Implicit detach procedure in VLR correction | 8.3.0 | 8.4.0 | +| 2009-09 | CT#46 | CP-090916 | 0042 | | Remove use case of UE not supporting combined attach for 'SMS only' | 8.3.0 | 8.4.0 | +| 2009-09 | CT#46 | CP-090915 | 0043 | 1 | Handling of EPS detach indication | 8.3.0 | 8.4.0 | +| 2009-09 | CT#46 | CP-090915 | 0044 | | Correction of reference to TS 23.195 | 8.3.0 | 8.4.0 | +| 2009-09 | CT#46 | CP-090915 | 0046 | | MME executing the HSS location updating procedure and location update procedure for non-EPS services | 8.3.0 | 8.4.0 | +| 2009-09 | CT#46 | CP-090915 | 0047 | 1 | Correction of values of IMSI detach from EPS service type IE and IMSI detach from non-EPS service type IE | 8.3.0 | 8.4.0 | +| 2009-09 | CT#46 | CP-090922 | 0034 | 1 | Paging signalling optimization after MME failure | 8.4.0 | 9.0.0 | +| 2009-09 | CT#46 | CP-090922 | 0035 | 2 | Paging clarifications | 8.4.0 | 9.0.0 | +| 2009-09 | CT#46 | CP-090922 | 0048 | 1 | Add UE EMM Mode IE in SGsAP-SERVICE-REQUEST message | 8.4.0 | 9.0.0 | +| 2010-03 | CT#47 | CP-100126 | 0049 | 2 | MME Name octet length correction | 9.0.0 | 9.1.0 | +| 2010-03 | CT#47 | CP-100126 | 0052 | | Alignment term "CSFB and SMS over SGs" with TS23.401 (Part III) | 9.0.0 | 9.1.0 | +| 2010-03 | CT#47 | CP-100134 | 0053 | 2 | Modification of the paging procedure | 9.0.0 | 9.1.0 | +| 2010-03 | CT#47 | CP-100126 | 0056 | | Clarification of paging procedure for SMS | 9.0.0 | 9.1.0 | +| 2010-03 | CT#47 | CP-100126 | 0058 | 1 | Paging for SMS on S3 and no paging retransmission in the MME | 9.0.0 | 9.1.0 | +| 2010-06 | CT#48 | CP-100348 | 0065 | 2 | Alert MME Notification / UE Activity Notification procedure on S3 interface | 9.1.0 | 9.2.0 | +| 2010-06 | CT#48 | CP-100348 | 0069 | 3 | Paging Procedures in the MME for SMS Service Type | 9.1.0 | 9.2.0 | +| 2010-06 | CT#48 | CP-100348 | 0072 | | Removal of reference to TS 23.195 | 9.1.0 | 9.2.0 | +| 2010-06 | CT#48 | CP-100354 | 0074 | 1 | New LAI derivation at MME | 9.1.0 | 9.2.0 | +| 2010-06 | CT#48 | CP-100370 | 0066 | 2 | Message Name and Miscellaneous Editorial changes | 9.2.0 | 10.0.0 | +| 2010-06 | CT#48 | CP-100370 | 0073 | | Update to service request procedure | 9.2.0 | 10.0.0 | +| 2010-09 | CT#49 | CP-100518 | 0076 | 1 | Location Update Retry on LAIs of other RATs | 10.0.0 | 10.1.0 | +| 2010-09 | CT#49 | CP-100520 | 0081 | 4 | Add Timezone IE in Location Update Request | 10.0.0 | 10.1.0 | +| 2010-09 | CT#49 | CP-100518 | 0083 | 1 | MME Name | 10.0.0 | 10.1.0 | +| 2010-09 | CT#49 | CP-100501 | 0086 | 2 | Correction to LAI derivation for default SGs scenario | 10.0.0 | 10.1.0 | +| 2010-09 | CT#49 | CP-100518 | 0088 | 3 | Call cancellation for CSFB MT | 10.0.0 | 10.1.0 | +| 2010-09 | CT#49 | CP-100495 | 0091 | 1 | IMSI detach from EPS and Non-EPS services | 10.0.0 | 10.1.0 | +| 2010-09 | CT#49 | CP-100518 | 0098 | 2 | MME State Diagram Correction | 10.0.0 | 10.1.0 | +| 2010-09 | CT#49 | CP-100518 | 0102 | 2 | VLR Abnormal Case Handling for SMS-MO Call | 10.0.0 | 10.1.0 | +| 2010-09 | CT#49 | CP-100518 | 0103 | 2 | Data Restoration and SGs Association Recovery | 10.0.0 | 10.1.0 | +| 2010-09 | CT#49 | CP-100518 | 0105 | | Where to page for the UE for a mobile terminated CS call when no NAS signalling connection exists | 10.0.0 | 10.1.0 | +| 2010-09 | CT#49 | CP-100518 | 0106 | | SGsAP-SERVICE-REQUEST message is not sent when UE is in EMM-IDLE mode | 10.0.0 | 10.1.0 | +| 2010-09 | CT#49 | CP-100518 | 0111 | | Behavior of the recipient upon receipt of an erroneous SGsAP-Status message | 10.0.0 | 10.1.0 | +| 2010-09 | CT#49 | CP-100518 | 0112 | | Corrections related to use of location area identifier IE at MME upon receiving SGsAP-PAGING-REQUEST message | 10.0.0 | 10.1.0 | +| 2010-12 | CT#50 | CP-100763 | 0099 | 2 | VLR Failure Handling | 10.1.0 | 10.2.0 | +| 2010-12 | CT#50 | CP-100763 | 0100 | 2 | MME Failure Handling | 10.1.0 | 10.2.0 | +| 2010-12 | CT#50 | CP-100763 | 0107 | 2 | VLR name is not configured locally in the MME for SGsAP-Paging-Request | 10.1.0 | 10.2.0 | +| 2010-12 | CT#50 | CP-100763 | 0112 | 1 | Correction of use of release procedure | 10.1.0 | 10.2.0 | +| 2010-12 | CT#50 | CP-100763 | 0114 | 3 | CS PLMN determination for CSFB | 10.1.0 | 10.2.0 | +| 2010-12 | CT#50 | CP-100763 | 0117 | 1 | CS domain access rights check in CSFB | 10.1.0 | 10.2.0 | +| 2010-12 | CT#50 | CP-100740 | 0122 | 1 | Paging failure on SGs | 10.1.0 | 10.2.0 | +| 2010-12 | CT#50 | CP-100763 | 0123 | | Length indicator in SGsAP information elements | 10.1.0 | 10.2.0 | +| 2010-12 | CT#50 | CP-100763 | 0124 | 2 | Adding location area identity to SGs location update reject message | 10.1.0 | 10.2.0 | +| 2010-12 | CT#50 | CP-100763 | 0127 | 3 | DST, Universal time and local time zone handling at the MME | 10.1.0 | 10.2.0 | +| 2010-12 | CT#50 | CP-100763 | 0128 | 1 | Call Forwarding on No Reply Triggering in EMM-CONNECTED Mode | 10.1.0 | 10.2.0 | +| 2010-12 | CT#50 | CP-100740 | 0136 | | Removal of VLR number derivation by the MME | 10.1.0 | 10.2.0 | +| 2010-12 | CT#50 | CP-100763 | 0137 | 1 | Additional MME Abnormal Cases | 10.1.0 | 10.2.0 | +| 2010-12 | CT#50 | CP-100763 | 0142 | 1 | Removing unused stored parameters in the VLR | 10.1.0 | 10.2.0 | +| 2011-03 | CT#51 | CP-110197 | 0143 | | Requirement for inclusion of LCS client identity IE in SGsAP-PAGING-REQUEST message | 10.2.0 | 10.3.0 | +| 2011-03 | CT#51 | CP-110197 | 0144 | | Correction of handling of call forwarding | 10.2.0 | 10.3.0 | +| 2011-03 | CT#51 | CP-110197 | 0145 | 3 | Implicit detach handling for EPS and non-EPS services | 10.2.0 | 10.3.0 | +| 2011-03 | CT#51 | CP-110197 | 0148 | 1 | Explicit IMSI detach from EPS services triggered by PTAU reject | 10.2.0 | 10.3.0 | +| 2011-03 | CT#51 | CP-110197 | 0149 | 2 | Discarding LSA identity in MM INFORMATION REQUEST message | 10.2.0 | 10.3.0 | +| 2011-03 | CT#51 | CP-110189 | 0150 | 2 | Clarification about usage of eMLPP priority IE in SGsAP-PAGING-REQUEST | 10.2.0 | 10.3.0 | +| 2011-03 | CT#51 | CP-110197 | 0151 | 1 | Implicit detach procedure in VLR when MME goes detached | 10.2.0 | 10.3.0 | +| 2011-03 | CT#51 | CP-110197 | 0153 | | Timer handling in detach response | 10.2.0 | 10.3.0 | +| 2011-03 | CT#51 | CP-110197 | 0154 | 1 | Location update trigger correction in SGs-ASSOCIATED state | 10.2.0 | 10.3.0 | +| 2011-03 | CT#51 | CP-110197 | 0155 | 1 | Paging accept in SGs NULL state at MME | 10.2.0 | 10.3.0 | +| 2011-03 | CT#51 | CP-110197 | 0156 | 2 | VLR behavior in SGs NULL state | 10.2.0 | 10.3.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|----------------------------------------------------------------------------------------------------------------------|--------|--------| +| 2011-06 | CT#52 | CP-110464 | 0158 | 2 | Correction on SGs UE unreachable handling | 10.3.0 | 10.4.0 | +| 2011-06 | CT#52 | CP-110464 | 0159 | 1 | UE Paging Initiation after SGs association has been established | 10.3.0 | 10.4.0 | +| 2011-06 | CT#52 | CP-110464 | 0160 | 1 | Detach handling for Implicit IMSI detach from non-EPS services | 10.3.0 | 10.4.0 | +| 2011-06 | CT#52 | CP-110457 | 0162 | 1 | Removal of CS PLMN reselection requirement for CSFB | 10.3.0 | 10.4.0 | +| 2011-06 | CT#52 | CP-110464 | 0163 | 1 | New Location Update Request during TMSI reallocation procedure | 10.3.0 | 10.4.0 | +| 2011-06 | CT#52 | CP-110464 | 0165 | 1 | Updating IMSI detach flag during explicit IMSI detach for non-EPS services | 10.3.0 | 10.4.0 | +| 2011-06 | CT#52 | CP-110464 | 0167 | 1 | SMS paging at MME failure | 10.3.0 | 10.4.0 | +| 2011-06 | CT#52 | CP-110464 | 0171 | | MME state diagram corrections | 10.3.0 | 10.4.0 | +| 2011-09 | CT#53 | CP-110682 | 0174 | 2 | MO SMS over SGs handling at VLR failure | 10.4.0 | 10.5.0 | +| 2011-09 | CT#53 | CP-110684 | 0175 | 2 | MT SMS over SGs handling at VLR failure | 10.4.0 | 10.5.0 | +| 2011-09 | CT#53 | CP-110682 | 0176 | 1 | Correction on detach in SGs-NULL state for non-EPS service | 10.4.0 | 10.5.0 | +| 2011-09 | CT#53 | CP-110694 | 0169 | 3 | Abnormal case for SGs location update procedure | 10.5.0 | 11.0.0 | +| 2011-09 | CT#53 | CP-110691 | 0179 | 1 | Inclusion of SS Code in SGs Paging for Network initiated CISS Procedure | 10.5.0 | 11.0.0 | +| 2011-09 | CT#53 | CP-110691 | 0182 | 2 | Overlapping with TS 24.301 scope | 10.5.0 | 11.0.0 | +| 2011-12 | CT#54 | CP-110886 | 0177 | 6 | Restoration of CS Services during long MME failure | 11.0.0 | 11.1.0 | +| 2011-12 | CT#54 | CP-110882 | 0180 | 4 | Asynchronous display of network name in CSFB deployment | 11.0.0 | 11.1.0 | +| 2011-12 | CT#54 | CP-110882 | 0181 | 1 | Correction to references | 11.0.0 | 11.1.0 | +| 2011-12 | CT#54 | CP-110888 | 0184 | 1 | Editorial corrections | 11.0.0 | 11.1.0 | +| 2011-12 | CT#54 | CP-110858 | 0193 | 1 | Inclusion of E-UTRAN location in SGs Location Update message | 11.0.0 | 11.1.0 | +| 2011-12 | CT#54 | CP-110874 | 0194 | 1 | Correction on trigger of EPS detach indication at the MME | 11.0.0 | 11.1.0 | +| 2011-12 | CT#54 | CP-110888 | 0198 | 2 | Correct the behaviors of the VLR during the implicit IMSI detach procedure | 11.0.0 | 11.1.0 | +| 2011-12 | CT#54 | CP-110942 | 0183 | 6 | Provide Subscriber Information handling for UE under LTE | 11.0.0 | 11.1.0 | +| 2012-03 | CT#55 | CP-120113 | 0186 | 6 | SGs paging handling in the VLR and the MME failure cases | 11.1.0 | 11.2.0 | +| 2012-06 | CT#56 | CP-120318 | 0203 | 3 | MME paging handling for "SMS Indicator" case | 11.2.0 | 11.3.0 | +| 2012-06 | CT#56 | CP-120293 | 0207 | 2 | Change to the detach message for implicit detach at MME | 11.2.0 | 11.3.0 | +| 2012-06 | CT#56 | CP-120293 | 0211 | 2 | Clarification of MME behaviour in receiving CS Paging when MRT has expired but IDT is running while ISR is activated | 11.2.0 | 11.3.0 | +| 2012-06 | CT#56 | CP-120309 | 0213 | 2 | SGs Support for MSC in Pool to avoid dual VLR registration | 11.2.0 | 11.3.0 | +| 2012-06 | CT#56 | CP-120318 | 0219 | 3 | Support of MAP signalling in the MME (via IWF) | 11.2.0 | 11.3.0 | +| 2012-06 | CT#56 | CP-120315 | 0201 | 6 | Support of SMS in MME for PS-only subscription | 11.2.0 | 11.3.0 | +| 2012-09 | CT#57 | CP-120572 | 0221 | 2 | Partial VLR failure or VLR restart with CSFB while ISR is activated | 11.3.0 | 11.4.0 | +| 2012-09 | CT#57 | CP-120594 | 0225 | 1 | Clarification of MME Name and VLR Name format | 11.3.0 | 11.4.0 | +| 2012-09 | CT#57 | CP-120594 | 0227 | 1 | Transitioning to SGs-NULL upon Attach | 11.3.0 | 11.4.0 | +| 2012-09 | CT#57 | CP-120584 | 0228 | 1 | Avoiding dual VLR registration for legacy UEs | 11.3.0 | 11.4.0 | +| 2012-09 | CT#57 | CP-120589 | 0222 | 2 | Additional condition for skipping VLR SGs registration | 11.3.0 | 11.4.0 | +| 2012-12 | CT#58 | CP-120807 | 0232 | 3 | Handling of VLR failure without restart | 11.4.0 | 11.5.0 | +| 2012-12 | CT#58 | CP-120803 | 0233 | 5 | SMS in MME registration indication from the HSS | 11.4.0 | 11.5.0 | +| 2012-12 | CT#58 | CP-120807 | 0234 | 2 | Configurations with multiple SCTP endpoints per MME/VLR pair | 11.4.0 | 11.5.0 | +| 2012-12 | CT#58 | CP-120807 | 0239 | 5 | FQDN coding in VLR name and MME name | 11.4.0 | 11.5.0 | +| 2012-12 | CT#58 | CP-120898 | 0230 | 7 | Selected PLMN in network sharing for CSFB | 11.4.0 | 11.5.0 | +| 2013-03 | CT#59 | CP-130108 | 0242 | | SGs Interface applicability in case of SMS in MME | 11.5.0 | 11.6.0 | +| 2013-03 | CT#59 | CP-130123 | 0246 | 2 | CS domain operator selection in GWCN | 11.5.0 | 11.6.0 | +| 2013-03 | CT#59 | CP-130134 | 0241 | 6 | MME handling of VLR Failure without restart | 11.6.0 | 12.0.0 | +| 2013-03 | CT#59 | CP-130125 | 0243 | 2 | Editorial change on reset indication | 11.6.0 | 12.0.0 | +| 2013-06 | CT#60 | CP-130255 | 0249 | 1 | Correction to Selected CS Domain Operator IE definition | 12.0.0 | 12.1.0 | +| 2013-06 | CT#60 | CP-130258 | 0256 | 1 | Clarification on the SGs-implicit IMSI detach | 12.0.0 | 12.1.0 | +| 2013-06 | CT#60 | CP-130239 | 0259 | 2 | Explicit IMSI detach trigger by the rejection of TAU procedure | 12.0.0 | 12.1.0 | +| 2013-06 | CT#60 | CP-130264 | 0264 | 3 | State transition in the MME without SGs signaling | 12.0.0 | 12.1.0 | +| 2013-06 | CT#60 | CP-130258 | 0265 | 3 | Paging response from GERAN/UTRAN during CSFB | 12.0.0 | 12.1.0 | +| 2013-06 | CT#60 | CP-130386 | 0266 | 3 | Implicit detach timer and implicit IMSI detach | 12.0.0 | 12.1.0 | +| 2013-06 | CT#60 | CP-130258 | 0267 | | Stop the timer Ts13 | 12.0.0 | 12.1.0 | +| 2013-06 | CT#60 | CP-130258 | 0268 | | Change VLR number to VLR name | 12.0.0 | 12.1.0 | +| 2013-06 | CT#60 | CP-130264 | 0269 | 4 | Cause Value Mapping Method for Contact without 2G/3G Roaming Agreement | 12.0.0 | 12.1.0 | +| 2013-06 | CT#60 | CP-130258 | 0270 | 3 | VLR handling when CSFB UE failing to access to UTRAN/GERAN | 12.0.0 | 12.1.0 | +| 2013-09 | CT#61 | CP-130505 | 0276 | | General description for UE fallback supervision procedure | 12.1.0 | 12.2.0 | +| 2013-09 | CT#61 | CP-130505 | 0277 | 2 | Re-paging for MT CSFB call at VLR | 12.1.0 | 12.2.0 | +| 2013-09 | CT#61 | CP-130505 | 0278 | 1 | MME handling when receiving paging at the SGs-NULL | 12.1.0 | 12.2.0 | +| 2013-09 | CT#61 | CP-130505 | 0279 | 2 | Handling the collision of call services | 12.1.0 | 12.2.0 | +| 2013-09 | CT#61 | CP-130505 | 0283 | 2 | CSFB supervision via timer Ts5/Ts14 and CFNRy/CRNRc handling | 12.1.0 | 12.2.0 | +| 2013-09 | CT#61 | CP-130510 | 0284 | 2 | Implicit IMSI detach triggering criteria | 12.1.0 | 12.2.0 | +| 2013-09 | CT#61 | CP-130498 | 0292 | 1 | Clarification on SS code used in the Paging message | 12.1.0 | 12.2.0 | +| 2013-09 | CT#61 | CP-130525 | 0296 | 2 | State of SGs association in the MME for emergency CSFB | 12.1.0 | 12.2.0 | +| 2013-09 | CT#61 | CP-130573 | 0290 | 4 | Handling of VLR failure without restart during MO-SMS procedure | 12.1.0 | 12.2.0 | +| 2013-12 | CT#62 | CP-130762 | 0301 | | Correction on reference of message type IE | 12.2.0 | 12.3.0 | +| 2013-12 | CT#62 | CP-130742 | 0303 | 5 | Addition of MO CSFB indication for return to last LTE PLMN | 12.2.0 | 12.3.0 | +| 2013-12 | CT#62 | CP-130754 | 0304 | 1 | Cleanup of SGs paging without LAI case | 12.2.0 | 12.3.0 | +| 2013-12 | CT#62 | CP-130745 | 0306 | 6 | UE paging after TMSI reallocation procedure abort | 12.2.0 | 12.3.0 | +| 2013-12 | CT#62 | CP-130739 | 0313 | 1 | Modification for paging with IMSI in MME for CSFB | 12.2.0 | 12.3.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|--------------------------------------------------------------------------------------------|--------|--------| +| 2013-12 | CT#62 | CP-130754 | 0315 | 2 | Paging identity usage after new Location Update Request during TMSI reallocation procedure | 12.2.0 | 12.3.0 | +| 2013-12 | CT#62 | CP-130754 | 0316 | | Trigger of the SGs service request procedure | 12.2.0 | 12.3.0 | +| 2014-03 | CT#63 | CP-140144 | 0314 | 3 | Collision of tracking area update and the MME initiated IMSI detach procedures | 12.3.0 | 12.4.0 | +| 2014-03 | CT#63 | CP-140141 | 0320 | | Clarification on Ts14 minimum value | 12.3.0 | 12.4.0 | +| 2014-03 | CT#63 | CP-140130 | 0326 | 1 | Response to SGs paging | 12.3.0 | 12.4.0 | +| 2014-06 | CT#64 | CP-140301 | 0329 | 1 | CSFB priority call handling in a network supporting Multimedia Priority Service | 12.4.0 | 12.5.0 | +| 2014-06 | CT#64 | CP-140309 | 0331 | | Return to last LTE PLMN indication for emergency calls | 12.4.0 | 12.5.0 | +| 2014-06 | CT#64 | CP-140331 | 0332 | 1 | Available old TMSI | 12.4.0 | 12.5.0 | +| 2014-06 | CT#64 | CP-140328 | 0336 | 2 | Release of SGs association in case of SRVCC | 12.4.0 | 12.5.0 | +| 2014-06 | CT#64 | CP-140304 | 0338 | 3 | Handling paging request for USSD when VoLTE call is ongoing | 12.4.0 | 12.5.0 | +| 2014-09 | CT#65 | CP-140661 | 0341 | 1 | Clarification on SCTP multi-homing support for SGsAP transport | 12.5.0 | 12.6.0 | +| 2014-12 | CT#66 | CP-140832 | 0343 | 3 | Service request in idle mode. | 12.6.0 | 12.7.0 | +| 2014-12 | CT#66 | CP-140832 | 0346 | 2 | SGs paging when NAS signalling connection is present | 12.6.0 | 12.7.0 | +| 2014-12 | CT#66 | CP-140832 | 0347 | | Removal of duplicated references TS 23.216 | 12.6.0 | 12.7.0 | +| 2014-12 | CT#66 | CP-140862 | 0342 | | Correction of faulty interface reference | 12.7.0 | 13.0.0 | +| 2014-12 | CT#66 | CP-140862 | 0344 | 1 | Correct MME's behaviour in VLR fails without restart | 12.7.0 | 13.0.0 | +| 2014-12 | CT#66 | CP-140858 | 0345 | 1 | Collision during paging procedure in A/lu mode | 12.7.0 | 13.0.0 | +| 2015-06 | CT#68 | CP-150329 | 0354 | | Correction on background color of text | 13.0.0 | 13.1.0 | +| 2015-09 | CT#69 | CP-150529 | 0355 | 3 | SGs state change without SGsAP signalling at the MME during PS HO | 13.1.0 | 13.2.0 | +| 2015-09 | CT#69 | CP-150529 | 0356 | | IMSI format correction | 13.1.0 | 13.2.0 | +| 2016-03 | CT#71 | CP-160072 | 0357 | 8 | UE temporarily unreachable due to eDRX | 13.2.0 | 13.3.0 | +| 2016-03 | CT#71 | CP-160082 | 0358 | | Alignment of paging for MT-SMS in case of ISR activated and VLR failure | 13.2.0 | 13.3.0 | + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-09 | CT#73 | CP-160492 | 0359 | 6 | B | Prioritized SM retransmission by the SMS SC when the UE becomes reachable | 13.4.0 | +| 2016-09 | CT#73 | CP-160492 | 0360 | 5 | B | MT SM transmission to a UE in eDRX within the SM-Delivery-Start-Time/Timer | 13.4.0 | +| 2016-09 | CT#73 | CP-160492 | 0361 | 5 | B | MT SM retransmission by the SMS GMSC to a UE in eDRX at the time requested in the Delivery Report | 13.4.0 | +| 2016-09 | CT#73 | CP-160492 | 0362 | 1 | F | Improve the MT SMS over SGs procedure in eDRX | 13.4.0 | +| 2016-12 | CT#74 | CP-160722 | 0363 | 3 | F | Enabling SMS over SGs for NB-IoT only UEs | 13.5.0 | +| 2017-03 | CT#75 | CP-170110 | 0365 | 3 | F | Failure case handling of SMS over SGs for NB-IoT only UEs | 13.6.0 | +| 2017-03 | CT#75 | CP-170111 | 0367 | | F | Correction on CR implementation for eDRX | 13.6.0 | +| 2017-03 | SA#75 | | | | | Upgrade to Rel-14 | 14.0.0 | +| 2017-06 | CT#76 | CP-171073 | 0369 | | F | MS Classmark 2 IE not provided at normal procedures | 14.1.0 | +| 2017-06 | CT#76 | CP-171073 | 0370 | 1 | F | Specification of TMSI handling in the MME at SMS via SGs using normal procedures | 14.1.0 | +| 2017-06 | CT#76 | CP-171073 | 0371 | | F | Extended NAS timer impact on TMSI reallocation supervision timer | 14.1.0 | +| 2017-09 | CT#77 | CP-172120 | 0372 | | C | Handling of timer expiry during extended service request procedure for MT CSFB | 15.0.0 | +| 2017-12 | CT#78 | CP-173054 | 0376 | | A | Missing IE Identifier coding assignments for eDRX | 15.1.0 | +| 2017-12 | CT#78 | CP-173079 | 0377 | 1 | B | Setting of priority transport value for priority services on the SGs Interface | 15.1.0 | +| 2018-03 | CT#79 | CP-180088 | 0378 | | F | IMEISV inclusion criteria correction for ICS | 15.2.0 | +| 2020-07 | SA#88e | - | - | - | | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/29_series/29119/47e8c2042061e08a14e012472e9fdbaa_img.jpg b/marked/Rel-16/29_series/29119/47e8c2042061e08a14e012472e9fdbaa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc783b25113d3ab38b0c7cdbe94bcdd08cf862d4 --- /dev/null +++ b/marked/Rel-16/29_series/29119/47e8c2042061e08a14e012472e9fdbaa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:492b70eeb32c679e1e255391a3e7339c2c8c37c7c448f547ce44e251aea19a16 +size 49790 diff --git a/marked/Rel-16/29_series/29119/e1a0d046fbe7f28f5e93a47091851747_img.jpg b/marked/Rel-16/29_series/29119/e1a0d046fbe7f28f5e93a47091851747_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a676c3be84c279e591dfc0f5dd11f9b5eefc2d3 --- /dev/null +++ b/marked/Rel-16/29_series/29119/e1a0d046fbe7f28f5e93a47091851747_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd52192e2533189edc1569ccf9de7db5ddc11207f3a82d9a783e382d32b0142b +size 42293 diff --git a/marked/Rel-16/29_series/29119/raw.md b/marked/Rel-16/29_series/29119/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d782174952606a5007dfa8d48b93e15253a2756a --- /dev/null +++ b/marked/Rel-16/29_series/29119/raw.md @@ -0,0 +1,312 @@ + + + + + + +# Contents + +Foreword .....4 + +1 Scope.....5 + +1.1 References .....5 + +2 Definitions and abbreviations .....5 + +2.1 Definitions.....5 + +2.2 Abbreviations .....6 + +3 General.....6 + +4 Transmission order and bit definitions.....7 + +5 GTP header .....7 + +6 GTP Message and Message Formats .....7 + +6.1 Signalling Message Formats .....7 + +6.2 Path Management messages.....8 + +6.3 Tunnel Management messages.....8 + +6.4 Location Management message .....9 + +6.5 Mobility Management messages.....9 + +6.6 Reliable delivery of signalling messages .....9 + +6.7 Information element .....10 + +7 Signalling Plane (GTP-C) .....10 + +8 GTP-U .....10 + +9 Path Protocol .....10 + +10 Error handling .....10 + +11 Inter-PLMN GTP communication over the Gp Interface .....10 + +12 IP, the networking technology used by GTP .....10 + +13 GTP parameters.....10 + +Annex A (informative): Change history.....11 + +# --- Foreword + +The present document has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document describes the signalling requirements and procedures used at network elements related to the GLR for GTP within the 3GPP system at the application level. + +The present document gives the description of the systems needed only in the network utilising GLR as the delta document against 3GPP TS 29.060. + +## 1.1 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. + - For a specific reference, subsequent revisions do not apply. + - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document *in the same Release as the present document*. +- [1] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description Stage2". +- [2] 3GPP TS 23.119: "Gateway Location Register (GLR) – stage2". +- [3] 3GPP TS 24.008: "Mobile radio interface layer 3 specification, Core Network Protocols – Stage 3". +- [4] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [5] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface". + +# --- 2 Definitions and abbreviations + +## 2.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**Gateway Location Register:** this entity handles location management of roaming subscriber in visited network without involving HLR + +**Intermediate GSN:** this entity is used as serving GSN towards home network and relay some PDU notification messages between serving GSN and Gateway GSN + +**MM context:** information sets held in MS and GSNs for a GPRS subscriber related to mobility management (MM) + +**MM Context ID:** IMSI or equivalent for use in conjunction with Anonymous Access (please refer to section GTP Header) + +**Path:** UDP/IP path and TCP/IP path are examples of paths that may be used to multiplex GTP tunnels + +**Path Protocol:** path Protocol is the protocol(s) used as a bearer of GTP between GSNs + +**PDP:** packet Data Protocol (PDP) is a network protocol used by an external packet data network interfacing to GPRS + +**PDP Context:** information sets held in MS and GSNs for a PDP address + +- Signalling message:** GTP signalling messages are exchanged between GSN pairs in a path. The signalling messages are used to transfer GSN capability information between GSN pairs and to create, update and delete GTP tunnels +- T-PDU:** original packet, for example an IP datagram, from an MS or a network node in an external packet data network. A T-PDU is the payload that is tunnelled in the GTP tunnel +- Tunnel Endpoint Identifier (TEID):** this field unambiguously identifies a tunnel endpoint in the receiving GTP-U or GTP-C protocol entity. The receiving end side of a GTP tunnel locally assigns the TEID value the transmitting side has to use. The TEID values are exchanged between tunnel endpoints using GTP-C messages + +## 2.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|------------------------------| +| GGSN | Gateway GPRS support node | +| GLR | Gateway Location Register | +| GPRS | General Packet Radio Service | +| GTP | GPRS Tunnelling Protocol | +| IM_GSN | Intermediate GSN | +| IP | Internet Protocol | +| GLR | Gateway Location Register | +| SGSN | Serving GPRS support node | +| TEID | Tunnel Endpoint Identifier | +| UDP | User Datagram Protocol | + +# 3 General + +The present document defines the GPRS Tunnelling Protocol (GTP) specific to the network with the GLR, i.e. the protocol between IM\_GSN and other nodes (i.e. GGSN, SGSN and GTP-MAP protocol converting GSN). It includes only the GTP signalling but not data transfer procedures. + +The interface between IM\_GSN and GGSN is either intra-PLMN interface or inter-PLMN interface. + + + +``` + +graph TD + GLR[GLR] -.-> HLR[HLR] + GLR -.-> GTPMAP1[GTP-MAP Protocol Converting GSN] + GLR -.-> IM_GSN[IM_GSN] + HLR -.-> GTPMAP2[GTP-MAP Protocol Converting GSN] + HLR -.-> GGSN[GGSN] + GTPMAP1 -.-> IM_GSN + GTPMAP2 -.-> GGSN + IM_GSN --- SGSN[SGSN] + IM_GSN --- GGSN + SGSN --- GGSN + +``` + +Legend: + +- ..... Signalling Interface +- \_\_\_\_\_ Signalling and Data Transfer Interface + +Figure 1: Logical Architecture for PS domain in the network with GLR. The diagram shows a network architecture with GLR, HLR, GTP-MAP Protocol Converting GSN, IM\_GSN, SGSN, and GGSN. Solid lines represent Signalling and Data Transfer Interfaces, while dotted lines represent Signalling Interfaces. + +Figure 1: Logical Architecture for PS domain in the network with GLR + +The GTP protocol is implemented only by IM\_GSNs, SGSNs and GGSNs. No other systems need to be aware of GTP. GPRS MSs are connected to a SGSN without being aware of GTP. + +It is assumed that there will be a many-to-many relationship between IM\_GSNs, SGSNs and GGSNs. An IM\_GSN may provide service to many GGSNs. A SGSN may provide service to many IM\_GSNs and GGSNs. + +# 4 Transmission order and bit definitions + +Transmission order and bit definitions on the interface between the IM\_GSN and other nodes in the network with GLR are the same as that used in the network without the GLR, see 3GPP TS 29.060. + +# 5 GTP header + +The GTP header used on interface between the IM\_GSN and other nodes in the network with GLR is the same as that used in the network without the GLR, see 3GPP TS 29.060. + +# 6 GTP Message and Message Formats + +The only signalling plane exists between the IM\_GSN and other nodes (i.e. GGSN, SGSN and GTP-MAP protocol converting GSN). + +## 6.1 Signalling Message Formats + +GTP defines a set of signalling messages between two associated GSNs. The signalling messages to be used between the IM\_GSN and other nodes are defined in the table below. For the GTP signalling messages to be used on other interfaces see 3GPP TS 29.060. + +**Table 1: Signalling messages** + +| Message Type value (Decimal) | Signalling message | Reference | +|------------------------------|---------------------------------------------|--------------------------| +| 3 | Version Not Supported | 7.4.3 in 3GPP TS 29.060 | +| 27 | PDU Notification Request | 7.5.12 in 3GPP TS 29.060 | +| 28 | PDU Notification Response | 7.5.13 in 3GPP TS 29.060 | +| 29 | PDU Notification Reject Request | 7.5.14 in 3GPP TS 29.060 | +| 30 | PDU Notification Reject Response | 7.5.15 in 3GPP TS 29.060 | +| 32 | Send Routeing Information for GPRS Request | 7.6.1 in 3GPP TS 29.060 | +| 33 | Send Routeing Information for GPRS Response | 7.6.2 in 3GPP TS 29.060 | +| 34 | Failure Report Request | 7.6.3 in 3GPP TS 29.060 | +| 35 | Failure Report Response | 7.6.4 in 3GPP TS 29.060 | + +## 6.2 Path Management messages + +The messages, which are listed in following table, are used on the interface between the IM\_GSN and other nodes. For the definitions of these messages and other messages used on the other interfaces refer to the corresponding sections in 3GPP TS 29.060. + +| Messages | Sending node | Receiving node | +|-----------------------|--------------|----------------| +| Version Not Supported | IM_GSN | GGSN, SGSN | +| | GGSN, SGSN | IM_GSN | + +## 6.3 Tunnel Management messages + +In following table, only the messages used between the IM\_GSN and GGSN and between the IM\_GSN and SGSN are listed. For the definitions of these messages and other messages used on the other interfaces refer to the corresponding sections in 3GPP TS 29.060. + +| Messages | Sending node | Receiving node | +|----------------------------------|--------------|----------------| +| PDU Notification Request | GGSN | IM_GSN | +| | IM_GSN | SGSN | +| PDU Notification Response | SGSN | IM_GSN | +| | IM_GSN | GGSN | +| PDU Notification Reject Request | SGSN | IM_GSN | +| | IM_GSN | GGSN | +| PDU Notification Reject Response | GGSN | IM_GSN | +| | IM_GSN | SGSN | + +## 6.4 Location Management message + +In the network with the GLR, The optional Location Management messages are defined to support the case when Network-Requested PDP Context Activation procedures are used and an IM\_GSN does not have a SS7 MAP interface. GTP is then used to transfer signalling messages between the IM\_GSN and a GTP-MAP protocol-converting GSN in the GPRS backbone network. The GTP-MAP protocol-converting GSN converts the signalling messages described in this section between GTP and MAP. The MAP messages are sent to and received from the GLR. The GTP-MAP protocol-converting function is described in 3GPP TS 23.060. The MAP protocol describing the corresponding procedures and messages is described in 3GPP TS 29.002. This alternative method is illustrated in Figure 2. + + + +The diagram illustrates the protocol stacks for IM\_GSN, GSN, and GLR. The IM\_GSN stack consists of GTP, UDP, IP, L2, and L1. The GSN is shown with two stacks: a GTP stack (GTP, UDP, IP, L2, L1) and a MAP stack (MAP, TCAP, SCCP, MTP3, MTP2, L1). The GLR stack consists of MAP, TCAP, SCCP, MTP3, MTP2, and L1. Arrows indicate the flow of signalling messages from the IM\_GSN through the GSN's GTP stack to its MAP stack, and then through the GLR's MAP stack. The GSN is labeled as 'GTP-MAP Interworking'. + +Diagram illustrating IM\_GSN - GLR Signalling via a GTP-MAP protocol-converter in a GSN. The diagram shows three main entities: IM\_GSN, GSN (with GTP-MAP Interworking), and GLR. The IM\_GSN has a protocol stack of GTP, UDP, IP, L2, and L1. The GSN has two stacks: one for GTP (GTP, UDP, IP, L2, L1) and one for MAP (MAP, TCAP, SCCP, MTP3, MTP2, L1). The GLR has a protocol stack of MAP, TCAP, SCCP, MTP3, MTP2, and L1. Arrows show the flow of messages from the IM\_GSN through the GSN's GTP stack to its MAP stack, and then through the GLR's MAP stack. + +Figure 2: IM\_GSN - GLR Signalling via a GTP-MAP protocol-converter in a GSN + +In following table, only the messages used between the IM\_GSN and The GTP-MAP protocol-converting GSN are listed. For the definitions of these messages and other messages used on the other interfaces refer to the corresponding sections in 3GPP TS 29.060. + +| Messages | Sending node | Receiving node | +|---------------------------------------------|-----------------------------|-----------------------------| +| Send Routeing Information for GPRS Request | IM_GSN | GTP-MAP protocol-converting | +| Send Routeing Information for GPRS Response | GTP-MAP protocol-converting | IM_GSN | +| Failure Report Request | IM_GSN | GTP-MAP protocol-converting | +| Failure Report Response | GTP-MAP protocol-converting | IM_GSN | + +## 6.5 Mobility Management messages + +The messages belonging to the mobility management messages are not used on the interface between the IM\_GSN and other nodes in the network with the GLR. + +## 6.6 Reliable delivery of signalling messages + +For the Reliability mechanism in the IM\_GSN, see section 7.8 in 3GPP TS 29.060. + +## 6.7 Information element + +The format of information elements in the message used on the interface between the IM\_GSN and other nodes in the network with GLR is the same as that in the network without the GLR. See 3GPP TS 29.060. + +# 7 Signalling Plane (GTP-C) + +The definition of signalling plane used in the network with the GLR is the same as that used in the network without the GLR, see in 3GPP TS 29.060. + +# 8 GTP-U + +GTP-U is not used on the interface between the IM\_GSN and other nodes. For the definition of GTP-U on the other interfaces, see in 3GPP TS 29.060. + +# 9 Path Protocol + +The Path Protocol on the interface between the IM\_GSN and other nodes in the network with the GLR is the same as that used in the network without the GLR. See 3GPP TS 29.060. + +# 10 Error handling + +The error handling on the interface between the IM\_GSN and other nodes is the same as that in the network without the GLR. See 3GPP TS 29.060. One exception is that the IM\_GSN doesn't have a Restart Counter because the IM\_GSN stores no PDP and MM context and therefore the synchronisation of the status of these with other GSNs is not needed. + +# --- 11 Inter-PLMN GTP communication over the Gp Interface + +Refer to the corresponding section in 3GPP TS 29.060. + +# --- 12 IP, the networking technology used by GTP + +Refer to the corresponding section in 3GPP TS 29.060. + +# --- 13 GTP parameters + +The definitions and directions for use of the parameters in GTP (inc. timer values or counter values and so on) on the interface between the IM\_GSN and other nodes is the same as that used in the network without the GLR. See 3GPP TS 29.060. + +# Annex A (informative): Change history + +| Document history | | | +|-------------------------|-----------|---------------------------------------------------------------------------------------------------------------------| +| V0.0.1 | Oct 1999 | The GTP protocol part is separated from MAP protocol part, and new specification related to GTP issue is generated. | +| V0.1.0 | Nov 1999 | For approval by N2#8 | +| V1.0.0 | Dec 1999 | For information and approval by TSG CN#6. | +| V1.0.1 | Jan 2000 | Only editorial modifications including some alignment with 29.060 | +| V2.0.0 | Mar 2000 | Submitted for approval to TSG CN#07 | +| V3.0.0 | Mar 2000 | Approved by TSG CN#07 | +| V4.0.0 | Mar 2001 | Approved by TSG CN#11 | +| V5.0.0 | Jun 2002 | Rel-5 created after CN#16 | +| V6.0.0 | Dec 2004 | Rel-6 created after CN#26 | +| V7.0.0 | June 2007 | Upgraded unchanged from Rel-6 after CT#36 | +| V8.0.0 | Dec 2008 | Upgraded unchanged from Rel-7 after CT#42 | +| V9.0.0 | Dec 2009 | Update to Rel-9 version (MCC) | +| V10.0.0 | Mar 2011 | Update to Rel-10 version (MCC) | +| V11.0.0 | Sep 2012 | Update to Rel-11 version (MCC) | +| V12.0.0 | Sep 2014 | Update to Rel-12 version (MCC) | +| V13.0.0 | Dec 2015 | Update to Rel-13 version (MCC) | +| V14.0.0 | Mar 2017 | Update to Rel-14 version (MCC) | +| V15.0.0 | Jun 2018 | Update to Rel-15 version (MCC) | +| V16.0.0 | July 2020 | Update to Rel-16 version (MCC) | \ No newline at end of file diff --git a/marked/Rel-16/29_series/29120/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/29_series/29120/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9eebdb4a0ab2a9364b5dc2b06ad1eb9eb081568f --- /dev/null +++ b/marked/Rel-16/29_series/29120/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4d7aed76c36e837e8a50eefdae7afeda569cf032c2158e0efe46e1e9d43279e +size 130135 diff --git a/marked/Rel-16/29_series/29120/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg b/marked/Rel-16/29_series/29120/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae91fcce65531bba43c42d57eb33ba0e4f943b55 --- /dev/null +++ b/marked/Rel-16/29_series/29120/036c200da9b64c3eb5aae2d67bb53e1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a915ae7ff5cc14385aae7af3d2717a34137afea42d25ad9a7f880e78f6ade067 +size 112096 diff --git a/marked/Rel-16/29_series/29120/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/29_series/29120/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3027e6d88153b83ffe7847d325f6f1f921d7c57d --- /dev/null +++ b/marked/Rel-16/29_series/29120/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34baa9d10f52b97fa104d519801378bfea7fab8459f55d39da51a052eb561b91 +size 146654 diff --git a/marked/Rel-16/29_series/29120/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-16/29_series/29120/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4f79431ee2472bcafedd6bd7a62b2af0c1bfa6b --- /dev/null +++ b/marked/Rel-16/29_series/29120/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d8fc6ce78e0838018b38987b873e31782061bc433a7be27f189bc38bbc95b70 +size 164897 diff --git a/marked/Rel-16/29_series/29120/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-16/29_series/29120/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..027329e2d20f5300844f66a5a0562e2f8016cf25 --- /dev/null +++ b/marked/Rel-16/29_series/29120/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58f078ed0bb7771b2e9ecdff84e5eb1eeaa48e53e23fa0e005eb78ee41f8f3b4 +size 93354 diff --git a/marked/Rel-16/29_series/29120/0b998e3ad8f9d104768642612605cb35_img.jpg b/marked/Rel-16/29_series/29120/0b998e3ad8f9d104768642612605cb35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75ec750d5e661384cfcd28cfffb96619f9e352e0 --- /dev/null +++ b/marked/Rel-16/29_series/29120/0b998e3ad8f9d104768642612605cb35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:134bd6984118e9ade6a1493db3be10f0e2e81006b9ec10ef7689ead4657b6f73 +size 129259 diff --git a/marked/Rel-16/29_series/29120/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-16/29_series/29120/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d364c9a46aab3f9db6689bf623348fa6b4d2c86f --- /dev/null +++ b/marked/Rel-16/29_series/29120/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:869d0b1ca2dc7185dfdcf71bf6b31eb21e72e7cf998adf4b0b241ec5537f4823 +size 119975 diff --git a/marked/Rel-16/29_series/29120/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/Rel-16/29_series/29120/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..414e913dec8cb19cc1a0e5725ad7b2e761a37bf2 --- /dev/null +++ b/marked/Rel-16/29_series/29120/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a95df66e18800adfd4fbb74f37519bf3aefa407933bada69dadfb50918a68723 +size 125487 diff --git a/marked/Rel-16/29_series/29120/17431d8b59408f09df7552d8bdbaa015_img.jpg b/marked/Rel-16/29_series/29120/17431d8b59408f09df7552d8bdbaa015_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69c49aae82b59eb2faa9fe3a6d78662315da50e8 --- /dev/null +++ b/marked/Rel-16/29_series/29120/17431d8b59408f09df7552d8bdbaa015_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0fb4a358ca7807811147fbc248782ff091c2ac0753b644299c89fdef2127405 +size 125596 diff --git a/marked/Rel-16/29_series/29120/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/marked/Rel-16/29_series/29120/18003425d0e8638dde4acc9c5c468c5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64be219d4d75090b63a05098a8589768b2d2e86b --- /dev/null +++ b/marked/Rel-16/29_series/29120/18003425d0e8638dde4acc9c5c468c5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4dcea52cedf73dea7cef82e266b9de93e74e3a3682e2739007d8f673997caf4 +size 130088 diff --git a/marked/Rel-16/29_series/29120/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg b/marked/Rel-16/29_series/29120/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbe19ac1e62044d52eedb6e25f475197213c045b --- /dev/null +++ b/marked/Rel-16/29_series/29120/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2020cfd5279fe3a7efd4cd3ed14ccd724368a4838123a6ccce1e371c0af47b8c +size 51377 diff --git a/marked/Rel-16/29_series/29120/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg b/marked/Rel-16/29_series/29120/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f7e453f79b7dc956acd78c37bf956088839b771 --- /dev/null +++ b/marked/Rel-16/29_series/29120/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80cc65e99d570833671ddd365365ef69b4ca9a8121877501f6fe855388dae4fc +size 128874 diff --git a/marked/Rel-16/29_series/29120/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg b/marked/Rel-16/29_series/29120/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c9476050db5fe5476637dc9f2604fcd074d82cd --- /dev/null +++ b/marked/Rel-16/29_series/29120/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e68f6819ad731d9c7b7d994ed00871cc289776a2d3b9c8e6a5a8b3a55b9698bc +size 41673 diff --git a/marked/Rel-16/29_series/29120/223792b3652794024244c277cc46394b_img.jpg b/marked/Rel-16/29_series/29120/223792b3652794024244c277cc46394b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d3a3aeef6ff62a9c924259dcb5a236682f2c9be --- /dev/null +++ b/marked/Rel-16/29_series/29120/223792b3652794024244c277cc46394b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d166f2bc5b25493d460dad3c0b58488b6dbfea7cdbe76217a1770b7eceb2025c +size 124724 diff --git a/marked/Rel-16/29_series/29120/245166735676c675f98f535bc4c6f0a1_img.jpg b/marked/Rel-16/29_series/29120/245166735676c675f98f535bc4c6f0a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff45a68d5ce3abe5a3ccab9f856946b1f5901d19 --- /dev/null +++ b/marked/Rel-16/29_series/29120/245166735676c675f98f535bc4c6f0a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32cbe9f0bc8ac54f40c724eb0b3cf1d21cb3dfc7cb0bea479d128191a38b5545 +size 157226 diff --git a/marked/Rel-16/29_series/29120/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg b/marked/Rel-16/29_series/29120/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..834d2c80adb21d383fd7e8d9eeab3b414ba569eb --- /dev/null +++ b/marked/Rel-16/29_series/29120/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a0bfcd0e972f73bbeb91eac8d267954f16091a731b59a110802ccf4e253d307 +size 136861 diff --git a/marked/Rel-16/29_series/29120/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/29_series/29120/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d845c106c45fe5d5a7385fc088832be92aba681e --- /dev/null +++ b/marked/Rel-16/29_series/29120/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c6f1a599d6f959448442f7001008ea534ff4afb28ad5badb9639d7cfbcbab33 +size 109279 diff --git a/marked/Rel-16/29_series/29120/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-16/29_series/29120/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5ff22befae5c2d7cd0e3d9f8ff0258eca6e9038 --- /dev/null +++ b/marked/Rel-16/29_series/29120/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ac7bbce4f46d9f6049ad231de208d4ddee311471c0dcecc692fb1110e5f1b5f +size 160571 diff --git a/marked/Rel-16/29_series/29120/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/29_series/29120/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38d280a98c3f3e580eb4c9a327788e9e1d9a77ae --- /dev/null +++ b/marked/Rel-16/29_series/29120/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc3171d7f94a711cb0bb8a290733f6078ffb7b2572ede752b84c942efe52b850 +size 140901 diff --git a/marked/Rel-16/29_series/29120/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/29_series/29120/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5518f8291018a88c3fba643068374d4c5dadd66a --- /dev/null +++ b/marked/Rel-16/29_series/29120/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b82b208d860a81156ce3cd399570bc070c89bb94f9aedc0ff7c948d0a2ab6abc +size 137306 diff --git a/marked/Rel-16/29_series/29120/3334fcca5dac808f4fd3840aba35bc2e_img.jpg b/marked/Rel-16/29_series/29120/3334fcca5dac808f4fd3840aba35bc2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee17eb434a9fce700719ce65e29b5a1972cbce5d --- /dev/null +++ b/marked/Rel-16/29_series/29120/3334fcca5dac808f4fd3840aba35bc2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c4931bc5459221a9200f252608855aa6f3f1adc80e94ef9ce6c56346905a7ce +size 94326 diff --git a/marked/Rel-16/29_series/29120/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-16/29_series/29120/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..602527144f9bb48728df4291530908c7edf7e916 --- /dev/null +++ b/marked/Rel-16/29_series/29120/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:200e7573d0acf2722b1ecb5b1b1c309ba74b4d2eb91f9ce07797ef96b7074f17 +size 107750 diff --git a/marked/Rel-16/29_series/29120/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/marked/Rel-16/29_series/29120/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9dca1253e1486a62177f0e1395aab58926ac4c9 --- /dev/null +++ b/marked/Rel-16/29_series/29120/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c8eb24056e31ec43cc6beff9c764ea73abc1a0e4902761476908959de1db717 +size 116491 diff --git a/marked/Rel-16/29_series/29120/36fd537a1e39baa2471ecfaaf869751a_img.jpg b/marked/Rel-16/29_series/29120/36fd537a1e39baa2471ecfaaf869751a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8a73bd773173286d2547124cc3355fa0f3d30ba --- /dev/null +++ b/marked/Rel-16/29_series/29120/36fd537a1e39baa2471ecfaaf869751a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cced0ff9e2e8caf5698c49b7a643b2c5a17635a4cf44e4fbb3a72d248e0abc19 +size 27778 diff --git a/marked/Rel-16/29_series/29120/3750b0149a6380885998ab3ca6a8787c_img.jpg b/marked/Rel-16/29_series/29120/3750b0149a6380885998ab3ca6a8787c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f31e599155610cebee644b5faf65010a228a7cc --- /dev/null +++ b/marked/Rel-16/29_series/29120/3750b0149a6380885998ab3ca6a8787c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c1f9949c66ffd95c5be63bc37444a7104270a487f9835bea0f7cdb21339d968 +size 39262 diff --git a/marked/Rel-16/29_series/29120/38d82ffe820e339811b396206f40a201_img.jpg b/marked/Rel-16/29_series/29120/38d82ffe820e339811b396206f40a201_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca5d40641d6d95f6623ad422e82a1c2b03d350a3 --- /dev/null +++ b/marked/Rel-16/29_series/29120/38d82ffe820e339811b396206f40a201_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c11f5836acb3b1d29da401ecda008b53b61a6124bade14b4a8738f25413f8d2e +size 137097 diff --git a/marked/Rel-16/29_series/29120/3ec35c497a0765a1a885c85f214b1bef_img.jpg b/marked/Rel-16/29_series/29120/3ec35c497a0765a1a885c85f214b1bef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c8378d70ae24bf1abd8c0ff2b567d568b71f5b1 --- /dev/null +++ b/marked/Rel-16/29_series/29120/3ec35c497a0765a1a885c85f214b1bef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3467aec236fed04dc5a21e4cf84da8ea3d603f77230c3fd0ff6a3c2a866410f +size 157412 diff --git a/marked/Rel-16/29_series/29120/40b80ef077f6151a9fbb593b8ad4864d_img.jpg b/marked/Rel-16/29_series/29120/40b80ef077f6151a9fbb593b8ad4864d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e344837a74915bae0b6b9361a7d0403e06c8c546 --- /dev/null +++ b/marked/Rel-16/29_series/29120/40b80ef077f6151a9fbb593b8ad4864d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3200ae06fba05d4890f28c84e93ebe43eae2e580668e38443912d15e75f20b6 +size 136640 diff --git a/marked/Rel-16/29_series/29120/4806f9f95fff13a30d6523bd6ffeac63_img.jpg b/marked/Rel-16/29_series/29120/4806f9f95fff13a30d6523bd6ffeac63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38bb5a789b34cc5eea364bea868d65865c16df9b --- /dev/null +++ b/marked/Rel-16/29_series/29120/4806f9f95fff13a30d6523bd6ffeac63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e6e49a06a2a26808ed80f34681c0b07cd57d8ecaba2bd789b51f917d47860e3 +size 132567 diff --git a/marked/Rel-16/29_series/29120/4847c98185bc52e8786b78738bc52b45_img.jpg b/marked/Rel-16/29_series/29120/4847c98185bc52e8786b78738bc52b45_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04abdf142d6cefd3b2ba7a82d1a31f3d0d8c4ade --- /dev/null +++ b/marked/Rel-16/29_series/29120/4847c98185bc52e8786b78738bc52b45_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64676a93de5a55a29afcc2759c980d78db715931783efde4d2827ac6e6d1b527 +size 99119 diff --git a/marked/Rel-16/29_series/29120/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/marked/Rel-16/29_series/29120/49fe8fe978c0f7e73112d231feb377eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d82c4ee2b074ab3d3769a8416e5324f3dbfc14c --- /dev/null +++ b/marked/Rel-16/29_series/29120/49fe8fe978c0f7e73112d231feb377eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f75ea68133b3066a741d7c6bf943312739be25e5a0240af632a443ab78e3512 +size 129869 diff --git a/marked/Rel-16/29_series/29120/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-16/29_series/29120/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c71460dfab62454eee64b96c598cad4b096b95d --- /dev/null +++ b/marked/Rel-16/29_series/29120/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af6969a629b209cd3e22b3446bbc8adbc6d25d8c15bf37872eb27fdada0448a2 +size 151597 diff --git a/marked/Rel-16/29_series/29120/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg b/marked/Rel-16/29_series/29120/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07492c3d82bc28992297da2006815c341486d287 --- /dev/null +++ b/marked/Rel-16/29_series/29120/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3eac8d8a916d55ad40e991377f173f5b22b14f5f96b347ece0f23c546843b563 +size 42491 diff --git a/marked/Rel-16/29_series/29120/4ff00a489baaa34a0c01070de1d613db_img.jpg b/marked/Rel-16/29_series/29120/4ff00a489baaa34a0c01070de1d613db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be019540d4e0b99f356d2e9e545bcc2e5019a8c2 --- /dev/null +++ b/marked/Rel-16/29_series/29120/4ff00a489baaa34a0c01070de1d613db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6907b5806658552b5e200d7e07306a379cef2cb3fbe5d99184c9a5c8b08c6335 +size 106712 diff --git a/marked/Rel-16/29_series/29120/50214d232017279410e9c9db8eb75119_img.jpg b/marked/Rel-16/29_series/29120/50214d232017279410e9c9db8eb75119_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b1c0ffc9030dc42e9049db5649217cd6e8bafe6 --- /dev/null +++ b/marked/Rel-16/29_series/29120/50214d232017279410e9c9db8eb75119_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac73305f409c1c13ce80542fddee862bad73ecf3429cbc94cbd887aa058400ed +size 42206 diff --git a/marked/Rel-16/29_series/29120/5478f70a6cef3e5672b2b22d28830cfb_img.jpg b/marked/Rel-16/29_series/29120/5478f70a6cef3e5672b2b22d28830cfb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf12c9e47ae588f9414bc7b94db5864b23b12370 --- /dev/null +++ b/marked/Rel-16/29_series/29120/5478f70a6cef3e5672b2b22d28830cfb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f51055e743a705a54414038d1c7933f9b0012f33e91f6bd3adb000b2462096e +size 106426 diff --git a/marked/Rel-16/29_series/29120/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-16/29_series/29120/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b72c95ea5aae5a7102bc9a58dc5f7294880079b8 --- /dev/null +++ b/marked/Rel-16/29_series/29120/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d17097c3cf319611a951aef964b2f5883152b828f6b7c785e03af64b8c0d1e7 +size 133338 diff --git a/marked/Rel-16/29_series/29120/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-16/29_series/29120/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1265ec396bfc717c23dda8be2603ef33398df6d1 --- /dev/null +++ b/marked/Rel-16/29_series/29120/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea677e84e38b915de0bab9d6bf624d0f591b36b9e49dc3eda86bf2ced05998eb +size 115712 diff --git a/marked/Rel-16/29_series/29120/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/marked/Rel-16/29_series/29120/5cf80bac69830ea773ac17c87e0ae24d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b989561d95d8bac5112e806e86852f03fa1ed4b1 --- /dev/null +++ b/marked/Rel-16/29_series/29120/5cf80bac69830ea773ac17c87e0ae24d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e9ea1783c156742c064c7130392ef8a6ae5f18c780067b88bba7864e401f172 +size 42160 diff --git a/marked/Rel-16/29_series/29120/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-16/29_series/29120/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16cab59b17b918d6c691e5bf56b2c34a40bf4a09 --- /dev/null +++ b/marked/Rel-16/29_series/29120/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a1d34d319f935be3e73df6545344d603454395bf55b5123526cb3522dd3dfc9 +size 130879 diff --git a/marked/Rel-16/29_series/29120/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-16/29_series/29120/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..955a7b77cdbb0c67db75d6339d03df84d48967df --- /dev/null +++ b/marked/Rel-16/29_series/29120/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3097d74c6928eb066310aae3798fe19e140c67f1e3c72f0f9bf826b9f5d7bd6c +size 23493 diff --git a/marked/Rel-16/29_series/29120/61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg b/marked/Rel-16/29_series/29120/61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..327a097734e309e0b63a245b4247fc538d994bf4 --- /dev/null +++ b/marked/Rel-16/29_series/29120/61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b22a9be417c4c83d83a1f16c5ad67f156b395855197cecddb3e37c68357737e3 +size 115713 diff --git a/marked/Rel-16/29_series/29120/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-16/29_series/29120/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d04575888db6c8bb7bea093820c5732b0b9b1e1 --- /dev/null +++ b/marked/Rel-16/29_series/29120/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03bb68d922f9ac71ae7de302ffb6b2f7a4d40f66195f9c034584549e667fb8d3 +size 96479 diff --git a/marked/Rel-16/29_series/29120/67d03c9e89620d73e3786c869e559752_img.jpg b/marked/Rel-16/29_series/29120/67d03c9e89620d73e3786c869e559752_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b4f2aa78711f94eef39737ad4daed709e806bf6 --- /dev/null +++ b/marked/Rel-16/29_series/29120/67d03c9e89620d73e3786c869e559752_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:deb614029f9e8cf45260631cfbfeb0b7c220a89c03ca59af8653da3be885ae90 +size 127169 diff --git a/marked/Rel-16/29_series/29120/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg b/marked/Rel-16/29_series/29120/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afbfd705067e211119caac60ab4171f3be6b77e5 --- /dev/null +++ b/marked/Rel-16/29_series/29120/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:921ab083ed28475145a1d58c971543db0d583b8122ba9a825317b7f8cc9e9280 +size 147127 diff --git a/marked/Rel-16/29_series/29120/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg b/marked/Rel-16/29_series/29120/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a2fbe0aa9243464c72ba692184a741718b6077d --- /dev/null +++ b/marked/Rel-16/29_series/29120/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6648608f6848787a3826bd0776f267e1371e67c7708be523d06efa435224bb7 +size 102651 diff --git a/marked/Rel-16/29_series/29120/694df81535f89c7bfb9ef0df6f130dc0_img.jpg b/marked/Rel-16/29_series/29120/694df81535f89c7bfb9ef0df6f130dc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9d20eeaabf908fa5301e5a209297291c748dfd1 --- /dev/null +++ b/marked/Rel-16/29_series/29120/694df81535f89c7bfb9ef0df6f130dc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ff79f4d85a95324f07d6b6d14f2ba37894a5f465ff8e505710224c3e57502a6 +size 118115 diff --git a/marked/Rel-16/29_series/29120/69e5f1993021af230d08c08aac97d9df_img.jpg b/marked/Rel-16/29_series/29120/69e5f1993021af230d08c08aac97d9df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3857de3a61ee31bab963a15122575f2f9405af7c --- /dev/null +++ b/marked/Rel-16/29_series/29120/69e5f1993021af230d08c08aac97d9df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4927e8ef4aedb36367e073f4e6cbcf2d5f7fb0c07276829ce7c06f48bf9d0b94 +size 127352 diff --git a/marked/Rel-16/29_series/29120/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/marked/Rel-16/29_series/29120/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84bd2185178f155b925e09874497c3f9721e1180 --- /dev/null +++ b/marked/Rel-16/29_series/29120/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5866c98cf2808cc38c348beccea6f9e6335ecba943010e76a1f006357be617b +size 121554 diff --git a/marked/Rel-16/29_series/29120/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/29_series/29120/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e2e708622cce796530b6eac4d363a7e863f69c2 --- /dev/null +++ b/marked/Rel-16/29_series/29120/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2ad8066fcf416b2ebe082348ce199bb1074cae3cc2c970f8060cdcd1d67f3a0 +size 172087 diff --git a/marked/Rel-16/29_series/29120/6e9d059430baba0c363e33749f68b107_img.jpg b/marked/Rel-16/29_series/29120/6e9d059430baba0c363e33749f68b107_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f10f630b0676eda6b41f1da3d13b20fa55ec0ae4 --- /dev/null +++ b/marked/Rel-16/29_series/29120/6e9d059430baba0c363e33749f68b107_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8645c3508eea86677644e43ece5c0d89018ed07b692e1086dd43d726a6a35a44 +size 136730 diff --git a/marked/Rel-16/29_series/29120/710ff83dc4a77abbe489fbf1a462845a_img.jpg b/marked/Rel-16/29_series/29120/710ff83dc4a77abbe489fbf1a462845a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8635ba95e19f55098fd03376a1cb840317410b8 --- /dev/null +++ b/marked/Rel-16/29_series/29120/710ff83dc4a77abbe489fbf1a462845a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:531d0a6c6f6ccbd8f4dcb4df1c22cdb9b80c9c9bf3ce037caa8e8fc08c5f1252 +size 119298 diff --git a/marked/Rel-16/29_series/29120/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-16/29_series/29120/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3078bebfa5f82bf2044fad667d5cba537cc9e51e --- /dev/null +++ b/marked/Rel-16/29_series/29120/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3207684bd10a9aff09e9bdd0eae7df4b93fe2bfb5306ce923e38f6ca52491257 +size 122593 diff --git a/marked/Rel-16/29_series/29120/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/marked/Rel-16/29_series/29120/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ca71bed87db08d95aa4f29a1e29283d0ce4ce5c --- /dev/null +++ b/marked/Rel-16/29_series/29120/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7b480c8cd636120a61c0570f109c9b6e67d9d5da2b1947cc71cc1e07e9dbc07 +size 137411 diff --git a/marked/Rel-16/29_series/29120/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/29_series/29120/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c208c5d8e9a378f54c0b3ffaeefe8251e1559e94 --- /dev/null +++ b/marked/Rel-16/29_series/29120/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:917f998ea3ed44df72db2b3581f182ef720cc8360cbeedc21ec9b697530cb2de +size 133379 diff --git a/marked/Rel-16/29_series/29120/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg b/marked/Rel-16/29_series/29120/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..501360128c726a7cddb568dc3a193626caa18162 --- /dev/null +++ b/marked/Rel-16/29_series/29120/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:774cb31ec925e13a3030e7783ac0ce20e5ef95528e2d200db6126fece170c517 +size 135774 diff --git a/marked/Rel-16/29_series/29120/7f16ae750ce9a533b0bd301dd986355e_img.jpg b/marked/Rel-16/29_series/29120/7f16ae750ce9a533b0bd301dd986355e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b6140a1e8766cfd909d2e1cd341dec1b2eeab62 --- /dev/null +++ b/marked/Rel-16/29_series/29120/7f16ae750ce9a533b0bd301dd986355e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0be6dd91dba71b100937217e770bdc3daa77a83f5dc188750c99a2b258839642 +size 132542 diff --git a/marked/Rel-16/29_series/29120/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-16/29_series/29120/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..beabd49443c1fa0e57045a0ed3551ad5c045e71d --- /dev/null +++ b/marked/Rel-16/29_series/29120/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1322bd4f79f0db50ad822f44e1930bc034f3b350053352cc69bd51d52207cc53 +size 34835 diff --git a/marked/Rel-16/29_series/29120/85680f3dcbe15424dd54fa3fd9e1c90d_img.jpg b/marked/Rel-16/29_series/29120/85680f3dcbe15424dd54fa3fd9e1c90d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f3a32e26f6c22cdedc66af46a412c58379838a2 --- /dev/null +++ b/marked/Rel-16/29_series/29120/85680f3dcbe15424dd54fa3fd9e1c90d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14a735c929804329a6d13261daeb62fca6ad0532be64499023729bfd6909b433 +size 79140 diff --git a/marked/Rel-16/29_series/29120/884c44b6cb9fbe15347e0562a6085df2_img.jpg b/marked/Rel-16/29_series/29120/884c44b6cb9fbe15347e0562a6085df2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..718e2eb8296079b8f65bb9d51acbc932fd0b0e2e --- /dev/null +++ b/marked/Rel-16/29_series/29120/884c44b6cb9fbe15347e0562a6085df2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ab5f6365703730244c30a773fb4cae36e84324a1cfb65b35ba2890b6d190c10 +size 122709 diff --git a/marked/Rel-16/29_series/29120/8aafdc3df2af4882f3c1b5e1e7e8dc8a_img.jpg b/marked/Rel-16/29_series/29120/8aafdc3df2af4882f3c1b5e1e7e8dc8a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0eb3e425431f54dda9eeda3cc5dee3f5b688ecb4 --- /dev/null +++ b/marked/Rel-16/29_series/29120/8aafdc3df2af4882f3c1b5e1e7e8dc8a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e14c21e0cd6336442ff01edfae12be7970ed93c01005cced296e0ee27c502449 +size 68980 diff --git a/marked/Rel-16/29_series/29120/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-16/29_series/29120/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9b74f2ab9dcaca81116c01b7d151ab6fd9e6229 --- /dev/null +++ b/marked/Rel-16/29_series/29120/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a82a4ab59072f0a717b2001dfd00c6af1edd974e431626e25e4719fe79e2de60 +size 114472 diff --git a/marked/Rel-16/29_series/29120/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg b/marked/Rel-16/29_series/29120/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cc4d91782e2e334244a345ed9060fba645e1a50 --- /dev/null +++ b/marked/Rel-16/29_series/29120/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:059683ade1bcb33cc92e14ca23d4cc76d9fb2e2561e3d3377e211b5b1b7a54c0 +size 134657 diff --git a/marked/Rel-16/29_series/29120/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg b/marked/Rel-16/29_series/29120/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a052d177f5543cb00b9d6445f8d645809f37ba0 --- /dev/null +++ b/marked/Rel-16/29_series/29120/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa73a13435de89f70d4e90be28ff514d43d92d881925fab476a7fd0ef30d9010 +size 81450 diff --git a/marked/Rel-16/29_series/29120/92724c769da9d46b730fde1a6dccb023_img.jpg b/marked/Rel-16/29_series/29120/92724c769da9d46b730fde1a6dccb023_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d70b8bebf7da5f31708a6544c0d9ecca9f8d09c --- /dev/null +++ b/marked/Rel-16/29_series/29120/92724c769da9d46b730fde1a6dccb023_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1458ce16612c1c674401b67c1221051197f69d6cfe163a1edaafdd35acf319b +size 136516 diff --git a/marked/Rel-16/29_series/29120/93699fb71e95b4df5a3871fdcf818982_img.jpg b/marked/Rel-16/29_series/29120/93699fb71e95b4df5a3871fdcf818982_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06a138ace49719580279af743ae63544c9e0305d --- /dev/null +++ b/marked/Rel-16/29_series/29120/93699fb71e95b4df5a3871fdcf818982_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b450e26f25223b4d4923a5615208143e206d45e2a896f599ea553bd1034e30d +size 79537 diff --git a/marked/Rel-16/29_series/29120/93bd00a00fa28558486f0664550699b1_img.jpg b/marked/Rel-16/29_series/29120/93bd00a00fa28558486f0664550699b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7be711bb83acb325fdeedcf481997b7f15b7f5e --- /dev/null +++ b/marked/Rel-16/29_series/29120/93bd00a00fa28558486f0664550699b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:088f4a4a73381652678626b31eebf484c79e3bc0456dc4ca51f5cde8a83f6a1e +size 125406 diff --git a/marked/Rel-16/29_series/29120/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-16/29_series/29120/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eccc50207d9c1ee2fa35ce4a7dc57cc2f67b7ed8 --- /dev/null +++ b/marked/Rel-16/29_series/29120/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a44621ff251102929402b80e18a4aa76043f1b6a62ec9df879bb73b6539e7d66 +size 130896 diff --git a/marked/Rel-16/29_series/29120/9c45844d796e85ae05505870a54e4eb4_img.jpg b/marked/Rel-16/29_series/29120/9c45844d796e85ae05505870a54e4eb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d229272dc0ae54294eab021f5b08836f4ca3f29b --- /dev/null +++ b/marked/Rel-16/29_series/29120/9c45844d796e85ae05505870a54e4eb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc69901c4b9a8af72b588e3ff82f20c336371e33876873fbf942e71c1f617e5f +size 139260 diff --git a/marked/Rel-16/29_series/29120/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg b/marked/Rel-16/29_series/29120/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f6cfa28eb3baf63333012cac323b4808d16b471 --- /dev/null +++ b/marked/Rel-16/29_series/29120/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:694b3cd81d6db739ccd52b13ab915c80994de4fe63c1b5828160976aa8c3892c +size 116761 diff --git a/marked/Rel-16/29_series/29120/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/marked/Rel-16/29_series/29120/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d990f88c6d0919686c83ed4b061adb32a7986cde --- /dev/null +++ b/marked/Rel-16/29_series/29120/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef3f68d9c545781f86939fd3b9d2e0c855b8e0aadcd9ee123861864827c71ab2 +size 138095 diff --git a/marked/Rel-16/29_series/29120/a1b35c85c93d7a2e30d1feea2faac2e6_img.jpg b/marked/Rel-16/29_series/29120/a1b35c85c93d7a2e30d1feea2faac2e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c925ec61c773c98da7e1400358bbef67325302b1 --- /dev/null +++ b/marked/Rel-16/29_series/29120/a1b35c85c93d7a2e30d1feea2faac2e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f2a57f73f5ac86eb58ae6ee46b5c9c095661a7fe6fff347049064017c967c2a +size 138186 diff --git a/marked/Rel-16/29_series/29120/a5404b7275b06497eecf9b5883604753_img.jpg b/marked/Rel-16/29_series/29120/a5404b7275b06497eecf9b5883604753_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9105ce6b7f71dbacaf69b78e7d05fd3f5c2bb41 --- /dev/null +++ b/marked/Rel-16/29_series/29120/a5404b7275b06497eecf9b5883604753_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a89a8e420b2d5a3776358f5a7b52593359614a2db3e7b38bc40f3ed97e219d3 +size 158860 diff --git a/marked/Rel-16/29_series/29120/a7450c80e88ad3f6ca1427ad84020998_img.jpg b/marked/Rel-16/29_series/29120/a7450c80e88ad3f6ca1427ad84020998_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..261102a3e6c95dcbf593306ead18411cdf5f0ef9 --- /dev/null +++ b/marked/Rel-16/29_series/29120/a7450c80e88ad3f6ca1427ad84020998_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7664f20442b63c9a5c304de7da90210421c614fc04061aa21f28f4d97da8ca8 +size 111582 diff --git a/marked/Rel-16/29_series/29120/a963ca41bde1669b18a4b783616f228b_img.jpg b/marked/Rel-16/29_series/29120/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30493bff0f6ddbaec1c2ef7a8a970035128d9740 --- /dev/null +++ b/marked/Rel-16/29_series/29120/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbab43ac7e8885155d790ac8aa0b9fcf0d53b8c3a9fac38712983d6d53c64566 +size 113115 diff --git a/marked/Rel-16/29_series/29120/ac42de838505beb048fb1267c46de428_img.jpg b/marked/Rel-16/29_series/29120/ac42de838505beb048fb1267c46de428_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79c96766ba84b22f115be1343bd8cfbbe688082d --- /dev/null +++ b/marked/Rel-16/29_series/29120/ac42de838505beb048fb1267c46de428_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59e1e2bd82fef86eb604fea6d731f9a97a7b2468cb15f3cc146f515d5de86fb2 +size 33093 diff --git a/marked/Rel-16/29_series/29120/aeb2a26a07219661191294dba528067a_img.jpg b/marked/Rel-16/29_series/29120/aeb2a26a07219661191294dba528067a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d32ff30acebe670705cab68cfb5e26c16604ba2b --- /dev/null +++ b/marked/Rel-16/29_series/29120/aeb2a26a07219661191294dba528067a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:366be45c5a7234111dea379c39af44fe95b71653c99da5a4391fdfe3acff2683 +size 133080 diff --git a/marked/Rel-16/29_series/29120/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg b/marked/Rel-16/29_series/29120/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6248d5c6acb92829038702b6f7056dec09225438 --- /dev/null +++ b/marked/Rel-16/29_series/29120/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0d1b5eda40e281c700470cb03ba5146dd2f58f0db39d61da441f3ea178bb117 +size 138391 diff --git a/marked/Rel-16/29_series/29120/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-16/29_series/29120/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35a0809dd993164d58b0d22c62c0940fd2508e89 --- /dev/null +++ b/marked/Rel-16/29_series/29120/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c27072f6f7d1ea2a90703784498568a506450af75772fa16c093eb728177d37 +size 97893 diff --git a/marked/Rel-16/29_series/29120/b55cd9b5721bd8aabc979c85316924e4_img.jpg b/marked/Rel-16/29_series/29120/b55cd9b5721bd8aabc979c85316924e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac573a68665029f974fb55cd359f8e9b8d76b89b --- /dev/null +++ b/marked/Rel-16/29_series/29120/b55cd9b5721bd8aabc979c85316924e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3972362a903fb0073a4be6587f3092f586081d3ae9692c00fc2926b8f8c8539 +size 129653 diff --git a/marked/Rel-16/29_series/29120/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg b/marked/Rel-16/29_series/29120/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a238b7823da163d6166e1bf572e5480de9a85705 --- /dev/null +++ b/marked/Rel-16/29_series/29120/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d97aad669c5a61311d9d11fcf667e83d54e3495c46fb84d91218a039148e945d +size 136172 diff --git a/marked/Rel-16/29_series/29120/bdd96f20e71f079cad85240efb3d3f24_img.jpg b/marked/Rel-16/29_series/29120/bdd96f20e71f079cad85240efb3d3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63f1bb14b2e8ff9b8c806da5925cc2ddad4ca116 --- /dev/null +++ b/marked/Rel-16/29_series/29120/bdd96f20e71f079cad85240efb3d3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d10af3a5cac9c8e4cfe10b66af34fe9de9b1f274f075893f31c510930fc7b2ae +size 20549 diff --git a/marked/Rel-16/29_series/29120/c21bad844b5cb6026c067a1f43ce67c3_img.jpg b/marked/Rel-16/29_series/29120/c21bad844b5cb6026c067a1f43ce67c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97c8493b34ac6f8eaa63251d16a948a614abe754 --- /dev/null +++ b/marked/Rel-16/29_series/29120/c21bad844b5cb6026c067a1f43ce67c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a78ed0df13a595f351d91a2392608d0e128b7f4af2a6058bebc837838802552a +size 120272 diff --git a/marked/Rel-16/29_series/29120/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg b/marked/Rel-16/29_series/29120/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ffe955fc8d4c768a55814e1f8d1fa135b5e4620 --- /dev/null +++ b/marked/Rel-16/29_series/29120/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16832c1389b248d4380f6e3d6c0a81c87a6e54d8f1c54aee565dadf159752216 +size 86184 diff --git a/marked/Rel-16/29_series/29120/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-16/29_series/29120/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..090e4353412ad0e96f975e8858e0068ed8668ea2 --- /dev/null +++ b/marked/Rel-16/29_series/29120/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5be62c1ff78000cac3c12703575bcc481312a49c6a8f0f349fbba58de770864 +size 164622 diff --git a/marked/Rel-16/29_series/29120/ca9fd3bd2fe73a46244dd1d017ffa3b5_img.jpg b/marked/Rel-16/29_series/29120/ca9fd3bd2fe73a46244dd1d017ffa3b5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20fb1779a31e6bbe27adcb2a9bfccd9d85e96c86 --- /dev/null +++ b/marked/Rel-16/29_series/29120/ca9fd3bd2fe73a46244dd1d017ffa3b5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce019bb11af30671a3fcd3bd1ae468e3e8b1779e6b4c6c6994c6d640de8836af +size 36737 diff --git a/marked/Rel-16/29_series/29120/d2417b04116c354deccb25d98a84a0fb_img.jpg b/marked/Rel-16/29_series/29120/d2417b04116c354deccb25d98a84a0fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38f425574a3ee8743ff340ab85116071a7939b8c --- /dev/null +++ b/marked/Rel-16/29_series/29120/d2417b04116c354deccb25d98a84a0fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d54d0bd6dbf30279f7b6c3dbf632b29aa2432795e7386e7bf2a8da554ce26d4f +size 137649 diff --git a/marked/Rel-16/29_series/29120/da85343976fdbb19f866d9ddbdad0eae_img.jpg b/marked/Rel-16/29_series/29120/da85343976fdbb19f866d9ddbdad0eae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26117177e9ab72fe3f28e2d029d9b01e40b76a48 --- /dev/null +++ b/marked/Rel-16/29_series/29120/da85343976fdbb19f866d9ddbdad0eae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e6bd214df6b6846d329ec1fdcbcab5c5e6cb9482eafd3700916c38106af2e60 +size 116747 diff --git a/marked/Rel-16/29_series/29120/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-16/29_series/29120/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..904e39321f34670cf00184182fff4868f98a26e2 --- /dev/null +++ b/marked/Rel-16/29_series/29120/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9a8ccc9a71f5363eb3fd31ff755b54a177d1de2681c663d8460a942bacd0d80 +size 130199 diff --git a/marked/Rel-16/29_series/29120/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/marked/Rel-16/29_series/29120/dbd4bab54b57e8d1abf80e3de6471130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3fc555372699e1d29ffd5563b097bea37ca849e --- /dev/null +++ b/marked/Rel-16/29_series/29120/dbd4bab54b57e8d1abf80e3de6471130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fb56f9a07b90e7c909e57a127e6b596041a0746ee09b94722fd420f7145a03f +size 140183 diff --git a/marked/Rel-16/29_series/29120/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/29_series/29120/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e0a3110039c1ab0e5e7046246349fa14c9c4fe0 --- /dev/null +++ b/marked/Rel-16/29_series/29120/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c002ddbeaf84eef1240b7366b7d3bb8fa4395028c92b743cf4f7ac22a821e3a +size 128447 diff --git a/marked/Rel-16/29_series/29120/dd6c544ab685b25dd17f59456efcfbfc_img.jpg b/marked/Rel-16/29_series/29120/dd6c544ab685b25dd17f59456efcfbfc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50d4d31cd8bc9ca06dc64b9833e025d5aa8287e3 --- /dev/null +++ b/marked/Rel-16/29_series/29120/dd6c544ab685b25dd17f59456efcfbfc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4e61c1b02ceafb1fb848921b998ac1c97b84e589674f177d3d7452c274df6a7 +size 23918 diff --git a/marked/Rel-16/29_series/29120/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/29_series/29120/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf96e7048d63e42a3138886d8e1254f324be737b --- /dev/null +++ b/marked/Rel-16/29_series/29120/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d900d38d8dfd41ded634213131e1f6f0b77ad2eb74a95faab1145a845d183cd1 +size 99545 diff --git a/marked/Rel-16/29_series/29120/e16bfa31d748f4d99ec4ae3d16656926_img.jpg b/marked/Rel-16/29_series/29120/e16bfa31d748f4d99ec4ae3d16656926_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5add40279febe4374c6fb5d72e458520be675c1d --- /dev/null +++ b/marked/Rel-16/29_series/29120/e16bfa31d748f4d99ec4ae3d16656926_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c4afadf38dc4f20a5d3963e1840de611ce3bbcfbed8b17adf70e4d89adedb61 +size 158723 diff --git a/marked/Rel-16/29_series/29120/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/29_series/29120/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7053734bde3829535ea620ad9332024f6e39ddd2 --- /dev/null +++ b/marked/Rel-16/29_series/29120/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4afee64f3ab93691030890b236908b51bd2d05ef1c1f0aa528cfe5dd9af953d +size 167778 diff --git a/marked/Rel-16/29_series/29120/e18841eb4a995df8354a793459e12fd0_img.jpg b/marked/Rel-16/29_series/29120/e18841eb4a995df8354a793459e12fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e51d6ebe2da2fdc26af4bd252377d1f005a78f1b --- /dev/null +++ b/marked/Rel-16/29_series/29120/e18841eb4a995df8354a793459e12fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e20a58f37f0b3c1d7d074482df6591c8aefd94542d29cbb835b02b1f73d094d +size 118874 diff --git a/marked/Rel-16/29_series/29120/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-16/29_series/29120/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..421ce86b4f7bceebba52311a60d208eded907ef3 --- /dev/null +++ b/marked/Rel-16/29_series/29120/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da809e34ce647b4ed60334e9c1ae306e22c0795d914380f46206fb59bfbdd3df +size 150660 diff --git a/marked/Rel-16/29_series/29120/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Rel-16/29_series/29120/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f741fb40fd41aaaef8e7da470d2dd0346eb796c4 --- /dev/null +++ b/marked/Rel-16/29_series/29120/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1d91bf8dd1cacd17140d31eb25d417fd7b35550464691836533f8ac01c76dc3 +size 88325 diff --git a/marked/Rel-16/29_series/29120/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/Rel-16/29_series/29120/e90987faabad6a6665cd8ed1151dc474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..946c694c3719b3bcb2fdedc64e0bcafdf2c1be77 --- /dev/null +++ b/marked/Rel-16/29_series/29120/e90987faabad6a6665cd8ed1151dc474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:798977f7c4f3a43a08e78e28a466c19c2bc30001b5378d7b820b588f5f4eb389 +size 141151 diff --git a/marked/Rel-16/29_series/29120/eabcb2f8b9acedb194571d5bc734b463_img.jpg b/marked/Rel-16/29_series/29120/eabcb2f8b9acedb194571d5bc734b463_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9266e4e51c3785cfa47edcd5522e89b018da510c --- /dev/null +++ b/marked/Rel-16/29_series/29120/eabcb2f8b9acedb194571d5bc734b463_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52898721f2e188e73a4aa9c4cd2df4eccf05355a94c5cddf6e6f7fdfd23b0dcd +size 112550 diff --git a/marked/Rel-16/29_series/29120/eefcb3f73fb33cce57cd04109c81506f_img.jpg b/marked/Rel-16/29_series/29120/eefcb3f73fb33cce57cd04109c81506f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f16a2f60dd4648263c0c1ebafe7fbafe4cf60c93 --- /dev/null +++ b/marked/Rel-16/29_series/29120/eefcb3f73fb33cce57cd04109c81506f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1abeeeacf0a657044f8f70b889236eb9f7281c2a30d78826aaeb688d229c3dc8 +size 69136 diff --git a/marked/Rel-16/29_series/29120/ef45b00396c293be0b18d32b97118bf4_img.jpg b/marked/Rel-16/29_series/29120/ef45b00396c293be0b18d32b97118bf4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67478a1fbd461e01c045edc841aad98a98d809b9 --- /dev/null +++ b/marked/Rel-16/29_series/29120/ef45b00396c293be0b18d32b97118bf4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8c708a347d4c9df98c97d4b6cfdbd23f4a1af21ef8892d233cd424d043c084f +size 118901 diff --git a/marked/Rel-16/29_series/29120/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg b/marked/Rel-16/29_series/29120/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3573d24c8d70383403718e8c8acaab0c12e28e7b --- /dev/null +++ b/marked/Rel-16/29_series/29120/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6117f9c60fc3c9534bbf16c7e16726700eab25107980654497890d2c14c5abc6 +size 129897 diff --git a/marked/Rel-16/29_series/29120/f61d0925551545b5938b3a4d1bbf63c3_img.jpg b/marked/Rel-16/29_series/29120/f61d0925551545b5938b3a4d1bbf63c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bb20bb2917ed50ade4021e7de0b45dc28a77a5c --- /dev/null +++ b/marked/Rel-16/29_series/29120/f61d0925551545b5938b3a4d1bbf63c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27852569af244cd842745d3487d91e525819d377d8aa3bf87a6fcf07534b1117 +size 126634 diff --git a/marked/Rel-16/29_series/29120/fc3e2b49a9f850951570e502393b697f_img.jpg b/marked/Rel-16/29_series/29120/fc3e2b49a9f850951570e502393b697f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07614b3cc5899142309e03e55b532203a0a7f154 --- /dev/null +++ b/marked/Rel-16/29_series/29120/fc3e2b49a9f850951570e502393b697f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21b19312d045aa3584cba5aa4ad60ff93f01107f23d5f401965dc5c122cf23c8 +size 116276 diff --git a/marked/Rel-16/29_series/29120/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-16/29_series/29120/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc5f5528e59cb1de4a40e7d2c1b578319a1d4d38 --- /dev/null +++ b/marked/Rel-16/29_series/29120/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5dac9d1bbc6f4d94a77d21c64c179871bc79e60ec490d783c979c25df41b6f47 +size 156081 diff --git a/marked/Rel-16/29_series/29120/fe7304192caf64cda93b580c5e7e5c06_img.jpg b/marked/Rel-16/29_series/29120/fe7304192caf64cda93b580c5e7e5c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f814b8ddbec50a4ce5ddad7ec49d5c071bb6a9a --- /dev/null +++ b/marked/Rel-16/29_series/29120/fe7304192caf64cda93b580c5e7e5c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:745a461cae1d3f935a39c775787a6d433bdd0feac262758d468290cf0534db48 +size 85136 diff --git a/marked/Rel-16/29_series/29120/ffb6acd27b8e3a54392840948a75869f_img.jpg b/marked/Rel-16/29_series/29120/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2346c506f8885e5437741855ad33f3b03d650e3d --- /dev/null +++ b/marked/Rel-16/29_series/29120/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cd9be571746fba6174e7c02960df18656db130c0db03d031f0d1566e6242d9a +size 21010 diff --git a/marked/Rel-16/29_series/29120/raw.md b/marked/Rel-16/29_series/29120/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..812f2f5a726c40fa7a3686fa7c29879318f34b95 --- /dev/null +++ b/marked/Rel-16/29_series/29120/raw.md @@ -0,0 +1,5796 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Abbreviations ..... | 8 | +| 4 The entities and interfaces within the mobile network utilising the GLR ..... | 9 | +| 4.1 The entities of the mobile system..... | 9 | +| 4.2 The Interfaces within the mobile services..... | 9 | +| 5 Overload and compatibility overview..... | 9 | +| 5.1 Overload control for MAP entities..... | 9 | +| 5.2 Compatibility..... | 9 | +| 6 Requirements concerning the use of SCCP and TC ..... | 10 | +| 6.1 Use of SCCP..... | 10 | +| 6.1.1 SCCP Class..... | 10 | +| 6.1.2 Sub-System Number (SSN)..... | 10 | +| 6.1.3 SCCP addressing ..... | 10 | +| 6.1.3.1 Introduction..... | 10 | +| 6.1.3.2 The Gateway Location Register (GLR) ..... | 10 | +| 6.1.3.2.1 Addressed by the VLR..... | 10 | +| 6.1.3.2.2 Addressed by the HLR..... | 10 | +| 6.1.3.2.3 Addressed by the GMSC..... | 11 | +| 6.1.3.2.4 Addressed by the IM-GSN..... | 11 | +| 6.1.3.3 The Intermediate MSC (IM_MSC)..... | 11 | +| 6.1.3.3.1 Addressed by the GMSC..... | 11 | +| 6.1.3.3.2 Addressed by the GMLC..... | 11 | +| 6.1.3.4 The Intermediate GSN (IM_GSN) ..... | 11 | +| 6.1.3.5 Summary table ..... | 11 | +| 6.2 Use of TC ..... | 12 | +| 7 General on MAP services ..... | 13 | +| 7.1 Common MAP services ..... | 13 | +| 7.1.1 MAP-U-ABORT service..... | 13 | +| 8 Mobility services..... | 14 | +| 8.1 General ..... | 14 | +| 8.2 Location Management services..... | 15 | +| 8.3 Authentication Management services ..... | 15 | +| 8.4 Subscriber management services ..... | 15 | +| 8.5 Fault recovery services..... | 16 | +| 8.6 Subscriber Information services..... | 16 | +| 9 Operation and maintenance services..... | 16 | +| 9.1 General ..... | 16 | +| 9.2 MAP_SEND_IMSI service ..... | 16 | +| 10 Call handling services ..... | 17 | +| 10.1 General ..... | 17 | +| 10.2 MAP_PROVIDE_ROAMING_NUMBER service ..... | 17 | +| 10.3 MAP_SET_REPORTING_STATE service..... | 17 | +| 10.4 MAP_STATUS_REPORT service ..... | 17 | +| 10.5 MAP_REMOTE_USER_FREE service ..... | 17 | +| 11 Supplementary services related services..... | 18 | +| 11.1 General ..... | 18 | +| 11.2 MAP_REGISTER_SS service ..... | 18 | +| 11.3 MAP_ERASE_SS service..... | 18 | +| 11.4 MAP_ACTIVATE_SS service ..... | 18 | +| 11.5 MAP_DEACTIVATE_SS service..... | 18 | + +| | | | +|----------|--------------------------------------------------------------|----| +| 11.6 | MAP_INTERROGATE_SS service ..... | 19 | +| 11.7 | MAP_REGISTER_PASSWORD service ..... | 19 | +| 11.8 | MAP_GET_PASSWORD service ..... | 19 | +| 11.9 | MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service ..... | 19 | +| 11.10 | MAP_UNSTRUCTURED_SS_REQUEST service ..... | 20 | +| 11.11 | MAP_UNSTRUCTURED_SS_NOTIFY service ..... | 20 | +| 11.12 | MAP_REGISTER_CC_ENTRY service ..... | 20 | +| 11.13 | MAP_ERASE_CC_ENTRY service ..... | 20 | +| 12 | Short message service management services ..... | 20 | +| 12.1 | General ..... | 20 | +| 12.2 | MAP-READY-FOR-SM service ..... | 21 | +| 12.3 | MAP-MT-FORWARD-SHORT-MESSAGE service ..... | 21 | +| 13 | Network-Requested PDP Context Activation services ..... | 21 | +| 13.1 | General ..... | 21 | +| 13.2 | MAP_SEND_ROUTING_INFO_FOR_GPRS service ..... | 21 | +| 13.3 | MAP_FAILURE_REPORT service ..... | 22 | +| 14 | Void ..... | 22 | +| 15 | Element of procedure ..... | 22 | +| 15.1 | SDL descriptions ..... | 22 | +| 16 | Mapping onto TC services ..... | 23 | +| 17 | Abstract syntax of the MAP protocol ..... | 24 | +| 17.1 | General ..... | 24 | +| 17.2 | Packages specifications ..... | 24 | +| 17.3 | Application contexts ..... | 25 | +| 18 | General on MAP user procedure ..... | 26 | +| 19 | Mobility procedures ..... | 27 | +| 19.1 | Location management Procedures ..... | 27 | +| 19.1.1 | Location updating ..... | 29 | +| 19.1.1.1 | General ..... | 29 | +| 19.1.1.2 | Detailed procedure in the GLR ..... | 30 | +| 19.1.2 | Location Cancellation ..... | 43 | +| 19.1.2.1 | General ..... | 43 | +| 19.1.2.2 | Detailed procedure in the GLR ..... | 44 | +| 19.1.3 | Purge MS ..... | 49 | +| 19.1.3.1 | General ..... | 49 | +| 19.1.3.2 | Detailed procedure in GLR ..... | 49 | +| 19.2 | Fault recovery procedures ..... | 54 | +| 19.2.1 | RESET procedure ..... | 54 | +| 19.2.1.1 | HLR failure case ..... | 54 | +| 19.2.1.2 | GLR failure case ..... | 54 | +| 19.2.1.3 | Detailed procedure in GLR ..... | 54 | +| 19.2.2 | VLR restoration: the restore data procedure in the GLR ..... | 58 | +| 19.2.2.1 | General ..... | 58 | +| 19.2.2.2 | Detailed procedure in GLR ..... | 58 | +| 20 | Operations and maintenance procedures ..... | 65 | +| 20.1 | General ..... | 65 | +| 20.2 | Subscriber data management procedures ..... | 65 | +| 20.2.1 | General ..... | 65 | +| 20.2.2 | Procedures in the GLR ..... | 67 | +| 20.2.2.1 | Subscriber deletion procedure ..... | 67 | +| 20.2.2.2 | Subscriber data modification procedure ..... | 67 | +| 20.3 | Subscriber Identity procedure ..... | 77 | +| 20.3.1 | Subscriber identity procedure in the GLR ..... | 78 | +| 21 | Call handling procedures ..... | 81 | +| 21.1 | General ..... | 81 | + +| | | | +|---------|--------------------------------------------------------------------------|-----| +| 21.2 | Retrieval of routing information ..... | 82 | +| 21.2.1 | General ..... | 82 | +| 21.2.2 | Process in the GLR to provide a roaming number ..... | 83 | +| 21.2.3 | Process in the GLR to provide subscriber information ..... | 86 | +| 21.3 | Setting of Reporting State ..... | 89 | +| 21.3.1 | General ..... | 89 | +| 21.3.2 | Process in the GLR to set the reporting state ..... | 89 | +| 21.4 | Status Reporting ..... | 92 | +| 21.4.1 | General ..... | 92 | +| 21.4.2 | Process in the GLR for Status Reporting ..... | 92 | +| 21.5 | Remote User Free..... | 94 | +| 21.5.1 | General ..... | 94 | +| 21.5.2 | Process in the GLR for Remote User Free ..... | 95 | +| 22 | Supplementary services procedures..... | 98 | +| 22.1 | Functional supplementary service processes..... | 98 | +| 22.1.1 | Functional supplementary service process co-ordinator for GLR..... | 98 | +| 22.1.2 | Call completion supplementary service process co-ordinator for GLR ..... | 100 | +| 22.2 | Registration procedure ..... | 102 | +| 22.2.1 | General ..... | 102 | +| 22.2.2 | Procedures in the GLR ..... | 103 | +| 22.3 | Erasure procedure..... | 105 | +| 22.3.1 | General ..... | 105 | +| 22.3.2 | Procedures in the GLR ..... | 106 | +| 22.4 | Activation procedure..... | 106 | +| 22.4.1 | General ..... | 106 | +| 22.4.2 | Procedures in the GLR ..... | 106 | +| 22.5 | Deactivation procedure ..... | 108 | +| 22.5.1 | General ..... | 108 | +| 22.5.2 | Procedures in the GLR ..... | 109 | +| 22.6 | Interrogation procedure..... | 109 | +| 22.6.1 | General ..... | 109 | +| 22.6.2 | Procedures in the GLR ..... | 109 | +| 22.7 | Password registration procedure ..... | 109 | +| 22.7.1 | General ..... | 109 | +| 22.7.2 | Procedures in the GLR ..... | 109 | +| 22.8 | Mobile Initiated USSD procedure..... | 109 | +| 22.8.1 | Procedures in the GLR ..... | 109 | +| 22.9 | Network initiated USSD procedure..... | 112 | +| 22.9.1 | Procedure in the GLR..... | 112 | +| 22.10 | Common macros for clause 22..... | 116 | +| 22.10.1 | SS Password handling macros..... | 116 | +| 22.11 | Activation of a CCBS request..... | 118 | +| 22.11.1 | General ..... | 118 | +| 22.11.2 | Procedure in the GLR ..... | 118 | +| 22.12 | Deactivation of a CCBS request..... | 120 | +| 22.12.1 | General ..... | 120 | +| 22.12.2 | Procedure in the GLR..... | 121 | +| 23 | Short message service procedures..... | 124 | +| 23.1 | General ..... | 124 | +| 23.2 | The mobile terminated short message transfer procedure..... | 124 | +| 23.2.1 | Procedure in the Intermediate MSC ..... | 124 | +| 23.2.2 | Procedure in the GLR..... | 130 | +| 23.3 | The Short Message Alert procedure..... | 136 | +| 23.3.1 | Procedures in the GLR ..... | 137 | +| 24 | GPRS process description..... | 139 | +| 24.1 | General ..... | 139 | +| 24.2 | Send Routing Information procedure..... | 139 | +| 24.2.1 | Process in the GLR for Send Routing Information for GPRS..... | 139 | +| 24.2.2 | Process in the IM-GSN for Send Routing Information for GPRS ..... | 140 | +| 24.3 | Failure Report procedure..... | 143 | + +| | | | +|------------------------|----------------------------------------------------------------------------|-----| +| 24.3.1 | Process in the GLR for Failure Report ..... | 143 | +| 24.3.2 | Process in the IM-GSN for Failure Report..... | 144 | +| 25 | General macro description ..... | 147 | +| 25.1 | MAP open macros..... | 147 | +| 25.2 | Macros to check the content of indication and confirmation primitives..... | 147 | +| 25.3 | Authentication processes..... | 147 | +| 25.3.1 | Process Obtain_Authentication_Sets_GLR..... | 147 | +| 25.3.2 | Process Authentication_Failure_Report_GLR ..... | 149 | +| 25.4 | Short Message Alert procedures ..... | 151 | +| 25.4.1 | Subscriber_Present_GLR_AS_VLR process ..... | 151 | +| 25.4.2 | The Mobile Subscriber is present..... | 154 | +| Annex A (informative): | Change history..... | 156 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document specifies the signalling requirements and procedures used at network elements related to the Gateway Location Register (GLR) for Mobile Application Part (MAP) within the 3GPP system. (i.e. the present document specifies the delta against 3GPP TS 29.002.) + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The present document describes the signalling requirements and procedures used at network elements related to the GLR for MAP within the 3GPP system at the application level. + +The present document gives the description of the systems needed only in the network utilising GLR as the delta document against 3GPP TS 29.002. + +# --- 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. +- [1] 3GPP TS 23.003: "Numbering, addressing and identification". +- [2] 3GPP TS 23.007: "Restoration procedures". +- [3] 3GPP TS 23.012: "Location registration procedures". +- [4] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS) Point to Point (PP)". +- [5] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [6] 3GPP TS 23.119: "Gateway Location Register (GLR) - stage2". + +# --- 3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|---------------------------------------| +| CCBS | Completion of Call to Busy Subscriber | +| GLR | Gateway Location Register | +| GPRS | General Packet Radio Service | +| IM_GSN | Intermediate GSN | +| IM_MSC | Intermediate MSC | +| SGSN | Serving GPRS support node | +| GGSN | Gateway GPRS support node | + +# --- 4 The entities and interfaces within the mobile network utilising the GLR + +## 4.1 The entities of the mobile system + +The functional entities related to the GLR are described below. The description of each entity is detailed in 3GPP TS 23.119 (GLR stage2 specification). The other functional entities described in the present document (e.g. MSC, VLR, and HLR) are specified in 3GPP TS 29.002. + +- The Gateway location Register (GLR). +- The Intermediate MSC (IM-MSC). +- The Intermediate GSN (IM-GSN). + +## 4.2 The Interfaces within the mobile services + +The Interfaces related to the GLR are described below. The description of each interface is detailed in 3GPP TS 23.119 (GLR stage2 specification). + +- Interface between the HLR and the GLR. +- Interface between the VLR and the GLR. +- Interface between the MSC and the IM\_MSC. +- Interface between the SGSN and the GLR. +- Interface between the MSC and the GLR. +- Interface between the GLR and the IM\_GSN. + +# --- 5 Overload and compatibility overview + +## 5.1 Overload control for MAP entities + +The VLR and SGSN see the GLR as an HLR, and the HLR sees the GLR as a VLR or a SGSN. Therefore the GLR shall behave like mobile entity as which the GLR is regarded. If overload of the GLR is detected, the responder may ignore requests for certain MAP operations (see tables 5.1/1, 5.1/2 and 5.1/3 in 3GPP TS 29.002). The decision as to which MAP Operations may be ignored is made by the MAP service provider and is based upon the priority of the application context. + +## 5.2 Compatibility + +A version negotiation mechanism based on the use of an application-context-name is used to negotiate the protocol version used between two entities for supporting a MAP-user signalling procedure. The description of the version negotiation mechanism is detailed in 3GPP TS 29.002. + +# --- 6 Requirements concerning the use of SCCP and TC + +## 6.1 Use of SCCP + +The Mobile Application Part makes use of the services offered by the Signalling Connection Control Part of signalling System No. 7. CCITT Blue Book or ITU-T (03/93) Recommendations Q.711 to Q.716 should be consulted for the full specification of SCCP. In North America (World Zone 1) the national version of SCCP is used as specified in ANSI T1.112. + +### 6.1.1 SCCP Class + +MAP will only make use of the connectionless classes (0 or 1) of the SCCP. + +### 6.1.2 Sub-System Number (SSN) + +The Application Entities (AEs) defined for MAP consist of several Application Service Elements (ASEs) and are addressed by sub-system numbers (SSNs). The SSN for MAP are specified in 3GPP TS 23.003 [1]. The specific SSN is not needed for the GLR, IM\_MSC, and IM\_GSN. + +### 6.1.3 SCCP addressing + +#### 6.1.3.1 Introduction + +The format and coding of address parameters carried by SCCP are detailed in 3GPP TS 29.002. + +The following subclauses describe the method of SCCP addressing appropriate for each entity both for the simple intra-PLMN case and where an inter-PLMN communication is required. The following entities are considered for the GLR additionally: + +- the Gateway location Register (GLR); +- the Intermediate Mobile-services Switching Centre (IM\_MSC); +- the Intermediate GPRS Support Node (IM\_GSN). + +#### 6.1.3.2 The Gateway Location Register (GLR) + +##### 6.1.3.2.1 Addressed by the VLR + +In the network utilising the GLR, when an MS that belongs to other PLMN registers in a VLR/SGSN, the VLR/SGSN sees the GLR as the MS's HLR. When initiating the update location dialogues, the VLR is able to address the GLR based on the SPC of the GLR because of intra-PLMN signalling. And the VLR can address the GLR based on an E.214 Mobile Global Title originally derived by the VLR from the IMSI (when CCITT or ITU-T SCCP is used), or an E.212 number originally derived from IMSI (when ANSI SCCP is used, an IMSI). When answering with Global Title to the VLR, the GLR shall insert its E.164 address in the Calling Party Address of the SCCP message containing the first responding CONTINUE message. After that, the VLR can address the GLR based on an E.164 GLR address. + +##### 6.1.3.2.2 Addressed by the HLR + +When a location updating dialogue initiated by a GLR has been successfully completed, the HLR sees the GLR as the VLR. When initiating dialogues towards the VLR, the routing information used by the HLR is derived from the E.164 VLR number received as a parameter of the MAP message initiating the update location dialogue, but in reality the HLR addresses the GLR using the VLR number. + +##### 6.1.3.2.3 Addressed by the GMSC + +In the case that the MS is served by the SGSN in the network utilising the GLR, the GMSC sees the GLR as the SGSN. When the GMSC initiates dialogues towards the SGSN the SGSN (MAP) SSN (See 3GPP TS 23.003) shall be included in the called party address. The routing information used by the GMSC is derived from the E.164 SGSN number received as a parameter of the MAP message initiating the forward short message procedure. But in reality the GMSC addresses the GLR using the SGSN number. + +##### 6.1.3.2.4 Addressed by the IM-GSN + +In the network utilising the GLR, the IM-GSN initiates the GPRS location information retrieval to the GLR. The IM-GSN must have the value of the GLR address beforehand. + +#### 6.1.3.3 The Intermediate MSC (IM\_MSC) + +##### 6.1.3.3.1 Addressed by the GMSC + +When a short message for CS has to be routed to an MS, the GMSC addresses the MSC by an MSC identity received from the HLR that complies with E.164 rules. But in reality the GMSC addresses the IM-MSC in the network utilising the GLR. + +##### 6.1.3.3.2 Addressed by the GMLC + +When a location request for a particular MS needs to be sent to the MS's VMSC, the GMLC addresses the MSC using an E.164 address received from the MS's HLR. But in reality the GMLC addresses the IM-MSC in the network utilising the GLR. + +#### 6.1.3.4 The Intermediate GSN (IM\_GSN) + +The IM-GSN provides routing of the Network-Requested PDP Context activation. If a Network-Requested PDP Context activation fails, the GLR will alert the IM-GSN when the subscriber becomes reachable. The GLR will use the E.164 IM-GSN number received as parameter of the MAP message reporting the failure. + +#### 6.1.3.5 Summary table + +The following table summarises the SCCP address used for invoke operations. As a principle, within a PLMN either an SPC or a GT may be used (network operation option), whereas when addressing an entity outside the PLMN the GT must be used. The address type mentioned in the table (e.g. MSISDN) is used as GT or to derive the SPC. + +For a response, the originating address passed in the invoke message is used as SCCP Called Party Address. For extra-PLMN addressing the own E.164 entity address is used as SCCP Calling Party Address; for intra-PLMN addressing an SPC derived from the entity number may be used instead. When using an SPC, the SPC may be taken directly from MTP. + +Table 6.1.3/1 + +| to
from | fixed
net
work | HLR | VLR | MSC | SGSN | GGSN | GLR | IM-MSC | IM-
GSN | +|--------------------------------------------|----------------------|-----------------------------------------------------------------------------------------------|-------------------------------------|-----------------------------|--------------------------------------|-------|---------------------------------------------------------------------------------------------------------|-------------------------------------|------------| +| fixed
network | | | | | | | | | | +| home
location
register | | | | | | | I:SPC/GT
E:GT
T:VLR NUMBER | | | +| visitor
location
register | | | | | | | I:SPC/GT
E:GT
T:MGT
(outside World Zone
1)/MSISDN
(World Zone 1)/HLR
NUMBER
(note) | | | +| mobile-
services
switching
centre | | | | | | | E:GT
T:SGSN NUMBER | I:SPC/GT
E:GT
T:MSC
NUMBER | | +| Serving
GPRS
Support
Node | | | | | | | I:SPC/GT
T:MGT/MSISDN/HL
R NUMBER | | | +| Gateway
GPRS
Support
Node | | | | | | Note1 | | | | +| Gateway
Location
register | --- | E:GT
T:MGT
(outside
World
Zone1)/MSISDN(
World Zone1/)
HLR NUMBER
(note) | I:SPC/G
T
T:VLR
NUMBE
R | --- | I:SPC/G
T
T:SGSN
NUMBE
R | | | | | +| Intermedia
te-
MSC | --- | | | I:SPC/GT
T:MSC
NUMBER | | | | | | +| Intermedia
te-
GSN | --- | | | | | | I:SPC/GT
T:HLR
NUMBER | | | + +I: Intra-PLMN E: Extra (Inter)-PLMN T: Address Type + GT: Global Title MGT: E.214 Mobile Global Title SPC: Signalling Point Code + +NOTE 0: For initiating the location updating procedure and an authentication information retrieval from the HLR preceding it, the VLR has to derive the HLR address from the IMSI of the MS. The result can be an SPC or an E.214 Mobile Global Title if CCITT or ITU-T SCCP is used, or IMSI itself if ANSI SCCP is used (ANSI SCCP is used in World Zone 1). When continuing the established update location dialogue (as with any other dialogue) the VLR must derive the routing information towards the HLR from the Calling Party Address received with the first responding CONTINUE message until the dialogue terminating message is received. + +For transactions invoked by the VLR after update location completion, the VLR may derive the information for addressing the HLR from addresses received in the course of the update location procedure (MSISDN or HLR number) or from the IMSI. + +When invoking the Restore Data procedure and an authentication information retrieval from the HLR preceding it, the VLR must derive the information for addressing the HLR from the address information received in association with the roaming number request. This may be either the IMSI received as a parameter of the MAP message requesting the Roaming Number or the Calling Party Address associated with the MAP message requesting the Roaming Number. + +From VLR in, GLR as for T (address type) only HLR Number is used. VLR and HLR are because only the thing that is belonging to same PLMN is thought. + +NOTE1: The hatching part is the same part of 3GPP TS29.002. + +## 6.2 Use of TC + +Refer to the corresponding section in 3GPP TS 29.002. + +# 7 General on MAP services + +Refer to the corresponding section in 3GPP TS 29.002 with the exceptions described below. + +## 7.1 Common MAP services + +The following common services are used: + +- MAP-OPEN service; +- MAP-CLOSE service; +- MAP-DELIMITER service; +- MAP-U-ABORT service; +- MAP-P-ABORT service; +- MAP-NOTICE service; +- MAP-SECURE-TRANSPORT-CLASS-1 service; +- MAP-SECURE-TRANSPORT-CLASS-2 service; +- MAP-SECURE-TRANSPORT-CLASS-3 service; +- MAP-SECURE-TRANSPORT-CLASS-4 service. + +Replace the MAP-U-ABORT service as follows. + +### 7.1.1 MAP-U-ABORT service + +This service enables the service-user to request the MAP dialogue to be aborted. The service is an unconfirmed service with service-primitives as shown in table 7.1/1. MAP service-user in the GLR may set "application context not supported" as user reason. + +**Table 7.1/1: Service-primitives for the MAP-U-ABORT service** + +| Parameters | Request | Indication | +|------------------------|---------|------------| +| User reason | M | M(=) | +| Diagnostic information | U | C(=) | +| Specific information | U | C(=) | + +#### User reason: + +This parameter can take the following values: + +- resource limitation (congestion); +the requested user resource is unavailable due to congestion; +- resource unavailable; +the requested user resource is unavailable for reasons other than congestion; +- application procedure cancellation; +the procedure is cancelled for reason detailed in the diagnostic information parameter; +- application context not supported; +the requested application context is not supported; + +- procedure error; + +processing of the procedure is terminated for procedural reasons. + +#### Diagnostic information: + +This parameter may be used to give additional information for some of the values of the user-reason parameter: + +**Table 7.1/2: User reason and diagnostic information** + +| User reason | Diagnostic information | +|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Resource limitation (congestion) | - | +| Resource unavailable | Short term/long term problem | +| Application procedure cancellation | Handover cancellation/
Radio Channel release/
Network path release/
Call release/
Associated procedure failure/
Tandem dialogue released/
Remote operations failure | +| Application context not supported | - | +| Procedure error | - | + +#### Specific information: + +This parameter may be used for passing any user specific information. Establishment and processing of the Specific information is not specified by GSM and shall be performed according to operator specific requirements. + +# 8 Mobility services + +## 8.1 General + +Regarding definition of each service, only the interval for adoption shall be considered for the GLR introduction. The interval for adoption for the GLR specification is described below. Service primitives and parameter definitions are as in 3GPP TS 29.002. + +## 8.2 Location Management services + +| Services | Interval for adoption | +|--------------------------|-----------------------| +| MAP_UPDATE_LOCATION | VLR – GLR | +| | GLR – HLR | +| MAP_CANCEL_LOCATION | HLR – GLR | +| | GLR – VLR | +| | GLR – SGSN | +| MAP_PURGE_MS | VLR – GLR | +| | SGSN – GLR | +| | GLR – HLR | +| MAP_UPDATE_GPRS_LOCATION | SGSN – GLR | +| | GLR – HLR | + +**Figure 8.2 /1** + +## 8.3 Authentication Management services + +| Services | Interval for adoption | +|---------------------------------------|-----------------------| +| MAP_SEND_AUTHENTICATION_IN
FO | VLR – GLR | +| | SGSN – GLR | +| | GLR – HLR | +| MAP_AUTHENTICATION_FAILURE
_REPORT | VLR – GLR | +| | SGSN – GLR | +| | GLR – HLR | + +Figure 8.3/1 + +## 8.4 Subscriber management services + +| Services | Interval for adoption | +|----------------------------|-----------------------| +| MAP_INSERT-SUBSCRIBER-DATA | HLR – GLR | +| | GLR – VLR | +| | GLR – SGSN | +| MAP-DELETE-SUBSCRIBER-DATA | HLR – GLR | +| | GLR – VLR | +| | GLR – SGSN | + +Figure 8.4/1 + +## 8.5 Fault recovery services + +| Services | Interval for adoption | +|-------------------------------------|-----------------------| +| MAP_RESET | HLR – GLR | +| | GLR – VLR | +| | GLR – SGSN | +| MAP_FORWARD_CHECK_SS_INDICA
TION | HLR – GLR | +| | GLR – VLR | +| MAP_RESTORE_DATA | VLR – GLR | + +Figure 8.5/1 + +## 8.6 Subscriber Information services + +| Services | Interval for adoption | +|-----------------------------|-----------------------| +| MAP-PROVIDE-SUBSCRIBER-Info | VLR – GLR | +| | GLR – HLR | + +Figure 8.6/1 + +# --- 9 Operation and maintenance services + +## 9.1 General + +Regarding definition of each service, only the interval for adoption shall be considered for the GLR introduction. The intervals for adoption for the GLR specification are described below. Service primitives and parameter definitions are as in 3GPP TS 29.002. + +## 9.2 MAP\_SEND\_IMSI service + +| Services | Interval for adoption | +|---------------|-----------------------| +| MAP_SEND_IMSI | HLR – GLR | +| | GLR – VLR | + +Figure 9.2/1 + +# --- 10 Call handling services + +## 10.1 General + +Regarding definition of each service, only the interval for adoption shall be considered for the GLR introduction. The intervals for adoption for the GLR specification are described below. Service primitives and parameter definitions are as in 3GPP TS 29.002. + +## 10.2 MAP\_PROVIDE\_ROAMING\_NUMBER service + +| Services | Interval for adoption | +|----------------------------|-----------------------| +| MAP_PROVIDE_ROAMING_NUMBER | HLR – GLR | +| | GLR – VLR | + +Figure 10.2/1 + +## 10.3 MAP\_SET\_REPORTING\_STATE service + +| Services | Interval for adoption | +|-------------------------|-----------------------| +| MAP_SET_REPORTING_STATE | HLR – GLR | +| | GLR – VLR | + +Figure 10.3/1 + +## 10.4 MAP\_STATUS\_REPORT service + +| Services | Interval for adoption | +|-------------------|-----------------------| +| MAP_STATUS_REPORT | VLR – GLR | +| | GLR – HLR | + +Figure 10.4/1 + +## 10.5 MAP\_REMOTE\_USER\_FREE service + +| Services | Interval for adoption | +|----------------------|-----------------------| +| MAP_REMOTE_USER_FREE | VLR – GLR | +| | GLR – HLR | + +Figure 10.5/1 + +# --- 11 Supplementary services related services + +## 11.1 General + +Regarding definition of each service, only the interval for adoption shall be considered for the GLR introduction. The intervals for adoption for the GLR specification are described below. Service primitives and parameter definitions are as in 3GPP TS 29.002. + +## 11.2 MAP\_REGISTER\_SS service + +| Services | Interval for adoption | +|-----------------|-----------------------| +| MAP_REGISTER_SS | VLR – GLR | +| | GLR – HLR | + +Figure 11.2/1 + +## 11.3 MAP\_ERASE\_SS service + +| Services | Interval for adoption | +|--------------|-----------------------| +| MAP_ERASE_SS | VLR – GLR | +| | GLR – HLR | + +Figure 11.3/1 + +## 11.4 MAP\_ACTIVATE\_SS service + +| Services | interval for adoption | +|-----------------|-----------------------| +| MAP_ACTIVATE_SS | VLR – GLR | +| | GLR – HLR | + +Figure 11.4/1 + +## 11.5 MAP\_DEACTIVATE\_SS service + +| Services | Interval for adoption | +|-------------------|-----------------------| +| MAP_DEACTIVATE_SS | VLR – GLR | +| | GLR – HLR | + +Figure 11.5/1 + +## 11.6 MAP\_INTERROGATE\_SS service + +| Services | Interval for adoption | +|--------------------|-----------------------| +| MAP_INTERROGATE_SS | VLR – GLR | +| | GLR – HLR | + +Figure 11.6/1 + +## 11.7 MAP\_REGISTER\_PASSWORD service + +| Services | Interval for adoption | +|-----------------------|-----------------------| +| MAP_REGISTER_PASSWORD | VLR – GLR | +| | GLR – HLR | + +Figure 11.7/1 + +## 11.8 MAP\_GET\_PASSWORD service + +| Services | Interval for adoption | +|------------------|-----------------------| +| MAP_GET_PASSWORD | HLR – GLR | +| | GLR – VLR | + +Figure 11.8/1 + +## 11.9 MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST service + +| Services | Interval for adoption | +|-------------------------------------|-----------------------| +| MAP_PROCESS_UNSTRUCTURED_SS_REQUEST | VLR – GLR | +| | GLR – HLR | + +Figure 11.9/1 + +## 11.10 MAP\_UNSTRUCTURED\_SS\_REQUEST service + +| Services | Interval for adoption | +|-----------------------------|-----------------------| +| MAP_UNSTRUCTURED_SS_REQUEST | HLR – GLR | +| | GLR – VLR | + +Figure 11.10/1 + +## 11.11 MAP\_UNSTRUCTURED\_SS\_NOTIFY service + +| Services | Interval for adoption | +|----------------------------|-----------------------| +| MAP_UNSTRUCTURED_SS_NOTIFY | HLR – GLR | +| | GLR – VLR | + +Figure 11.11/1 + +## 11.12 MAP\_REGISTER\_CC\_ENTRY service + +| Services | Interval for adoption | +|----------------------------|-----------------------| +| MAP_UNSTRUCTURED_SS_NOTIFY | VLR – GLR | +| | GLR – HLR | + +Figure 11.12/1 + +## 11.13 MAP\_ERASE\_CC\_ENTRY service + +| Services | Interval for adoption | +|---------------------|-----------------------| +| MAP_ERASE_CC_NOTIFY | VLR – GLR | +| | GLR – HLR | + +Figure 11.13/1 + +# --- 12 Short message service management services + +## 12.1 General + +Regarding definition of each service, only the interval for adoption shall be considered for the GLR introduction. The intervals for adoption for the GLR specification are described below. Service primitives and parameter definitions are as in 3GPP TS 29.002. + +## 12.2 MAP-READY-FOR-SM service + +| Services | interval for adoption | +|------------------|-----------------------| +| MAP-READY-FOR-SM | VLR – GLR | +| | SGSN – GLR | +| | GLR – HLR | + +Figure 12.2/1 + +## 12.3 MAP-MT-FORWARD-SHORT-MESSAGE service + +| Services | interval for adoption | +|------------------------------|-----------------------| +| MAP_MT_FORWARD_SHORT_MESSAGE | SMS-GMSC – IM-MSC | +| | IM-MSC – MSC | +| | SMS-GMSC – GLR | +| | GLR – SGSN | + +Figure 12.3/1 + +# --- 13 Network-Requested PDP Context Activation services + +## 13.1 General + +Regarding definition of each service, only the interval for adoption shall be considered for the GLR introduction. The intervals for adoption for the GLR specification are described below. Service primitives and parameter definitions are as in 3GPP TS 29.002. + +## 13.2 MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS service + +| Services | Interval for adoption | +|--------------------------------|-----------------------| +| MAP_SEND_ROUTING_INFO_FOR_GPRS | IM-GSN – GLR | + +Figure 13.2/1 + +## 13.3 MAP\_FAILURE\_REPORT service + +| Services | Interval for adoption | +|--------------------|-----------------------| +| MAP_FAILURE_REPORT | IM-GSN – GLR | + +Figure 13.3/1 + +# --- 14 Void + +# 15 Element of procedure + +The elements of procedures for the MAP protocol are referred to the corresponding section in 3GPP TS 29.002002 with the exceptions described below. + +## 15.1 SDL descriptions + +Replace the corresponding part of Process Secure\_MAP\_DSM as figure 15.1/1. + + + +Process Secure\_MAP\_DSM\_GLR 15.1.1(1) + +Process to manage a MAP dialogue + +``` + +stateDiagram-v2 + [*] --> DIALOGUE_ACCEPTED + DIALOGUE_ACCEPTED --> MAP_REQ + DIALOGUE_ACCEPTED --> MAP_rsp + DIALOGUE_ACCEPTED --> MAP_DELIMITER_req + MAP_REQ --> Secure_Transport_required + Secure_Transport_required --> Requesting_MAP_SSM : (TRUE) + Secure_Transport_required --> Service_Invoked_VIA_Intern2 : (FALSE) + Requesting_MAP_SSM --> Service_Invoked_VIA_Intern2 + Service_Invoked_VIA_Intern2 --> DIALOGUE_ESTABLISHED + MAP_rsp --> Secure_Transport_required + Secure_Transport_required --> Response_Issued_VIA_Intern1 : (TRUE) + Secure_Transport_required --> Response_Issued_VIA_Intern3 : (FALSE) + Response_Issued_VIA_Intern1 --> DIALOGUE_ACCEPTED + Response_Issued_VIA_Intern3 --> DIALOGUE_ACCEPTED + MAP_DELIMITER_req --> TC_CONTINUE_req_VIA_TC1 + TC_CONTINUE_req_VIA_TC1 --> DIALOGUE_ESTABLISHED + DIALOGUE_ESTABLISHED --> MAP_CLOSE_req + DIALOGUE_ESTABLISHED --> MAP_U_ABORT_req + MAP_CLOSE_req --> TC_END_req_VIA_TC1 + TC_END_req_VIA_TC1 --> Secure_Transport_required + Secure_Transport_required --> Terminated_VIA_Intern1 : (FALSE) + Secure_Transport_required --> Terminated_VIA_Intern2 : (TRUE) + Terminated_VIA_Intern1 --> To_all_active_PSSMs + Terminated_VIA_Intern2 --> To_all_active_RSSMs + To_all_active_PSSMs --> IDLE + To_all_active_RSSMs --> IDLE + MAP_U_ABORT_req --> User_reason=AC-not-supported + User_reason=AC-not-supported --> Abort_reason := User-specific + User_reason=AC-not-supported --> Abort_reason := AC-not-supported + Abort_reason := User-specific --> User_info := MAP_UserAbortInfo + User_info := MAP_UserAbortInfo --> TC_U_ABORT_req_VIA_TC1 + Abort_reason := AC-not-supported --> TC_U_ABORT_req_VIA_TC1 + TC_U_ABORT_req_VIA_TC1 --> Secure_Transport_required + Secure_Transport_required --> Terminated_VIA_Intern3 : (FALSE) + Secure_Transport_required --> Terminated_VIA_Intern4 : (TRUE) + Terminated_VIA_Intern3 --> To_all_active_SPSSMs + Terminated_VIA_Intern4 --> To_all_active_SRSSMs + To_all_active_SPSSMs --> IDLE + To_all_active_SRSSMs --> IDLE + +``` + +State transition diagram for Process Secure\_MAP\_DSM\_GLR. The diagram shows transitions between states DIALOGUE\_ACCEPTED, DIALOGUE\_ESTABLISHED, and IDLE based on various MAP primitives and transport requirements. + +Figure 15.1/1: Process Secure\_MAP\_DSM\_GLR + +# 16 Mapping onto TC services + +Dialogue control, Service specific procedures and SDL descriptions are referred to the corresponding section in 3GPP TS 29.002. + +# 17 Abstract syntax of the MAP protocol + +## 17.1 General + +Refer to the corresponding section in 3GPP TS 29.002 except Packages specifications and Application contexts. + +Regarding the operations which are initiated by the VLR or SGSN toward HLR via GLR, the timer value used in the operations should be configured enough long to guarantee the GLR specific fallback mechanism. + +## 17.2 Packages specifications + +Regarding Packages specifications, only the supplier and consumer definition shall be considered for the GLR introduction. The supplier and consumer definition for the GLR specification are derived Table 17.2/1. For the other definitions of the package specifications are as in 3GPP TS 29.002. + +**Table 17.2/1: supplier and consumer definition** + +| Operation Package | supplier | consumer | +|----------------------------------------|-------------|----------| +| LocationUpdatingPackage-v3 | HLR | GLR | +| | GLR | VLR | +| LocationCancellationPackage-v3 | VLR or SGSN | GLR | +| | GLR | HLR | +| RoamingNumberEnquiryPackage-v3 | VLR | GLR | +| | GLR | HLR | +| InfoRetrievalPackage-v2 | HLR | GLR | +| | GLR | VLR | +| | GLR | SGSN | +| InfoRetrievalPackage-v1 | HLR | GLR | +| | GLR | VLR | +| | GLR | SGSN | +| IMSIRetrievalPackage-v2 | HLR | GLR | +| | GLR | VLR | +| SubscriberDataMngtStandAlonePackage-v3 | VLR or SGSN | GLR | +| | GLR | HLR | +| SubscriberDataMngtPackage-v3 | VLR or SGSN | GLR | +| | GLR | HLR | +| ResetPackage-v2 | VLR or SGSN | GLR | +| | GLR | HLR | +| FunctionalSsPackage-v2 | HLR | GLR | +| | GLR | HLR | +| BindingPackage-v1 | HLR | GLR | +| | GLR | VLR | +| UnstructuredSsPackage-v2 | HLR | GLR | +| | GLR | VLR | +| UnstructuredSsPackage-v1 | HLR | GLR | +| | GLR | VLR | +| MTShortMsgRelayPackage-v3 | IM-MSC or | GMSC | +| | GLR | | +| | MSC | IM-MSC | +| | SGSN | GLR | +| MwdMngtPackage-v3 | HLR | GLR | +| | GLR | SGSN | +| | GLR | VLR | +| MwdMngtPackage-v1 | HLR | GLR | +| | GLR | VLR | +| DataRestorationPackage-v3 | GLR | VLR | +| PurgingPackage-v3 | HLR | GLR | +| | GLR | VLR | +| | GLR | SGSN | +| SubscriberInformationEnquiryPackage-v3 | VLR | GLR | +| | GLR | HLR | + +| Operation Package | supplier | consumer | +|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------|-----------------| +| GprsLocationUpdatingPackage-v3 | HLR | GLR | +| | GLR | SGSN | +| FailureReportingPackage-v3 | GLR | IM-GSN | +| SetReportingStatePackage-v3 | VLR | GLR | +| | GLR | HLR | +| StatusReportPackage-v3 | HLR | GLR | +| | GLR | VLR | +| RemoteUserFreePackage-v3 | VLR | GLR | +| | GLR | HLR | +| CallCompletionPackage-v3 | HLR | GLR | +| | GLR | VLR | +| AuthenticationFailureReportPackage-v3 | HLR | GLR | +| | GLR | VLR | +| | GLR | SGSN | +| SecureTransportHandlingPackage-v3 | This operation package includes the operations required for the secure transport of MAP messages between any MAP entities. | | + +## 17.3 Application contexts + +Regarding Application contexts specifications, only the responder and initiator definition shall be considered for the GLR introduction. The responder and initiator definition for the GLR specification are derived Table 17.3/1. For the other definitions of the package specifications are as in 3GPP TS 29.002. + +**Table 17.3/1: supplier and consumer definition** + +| Application Context | Version | Initiator | Responder | +|------------------------------------|---------|-----------------------------------------------------------------------------------------------------|---------------| +| locationCancellationContext | v3 | HLR | GLR | +| | | GLR | VLR or SGSN | +| imsiRetrievalContext | v2 | VLR | GLR | +| | | GLR | HLR | +| infoRetrievalContext | v2 | VLR or SGSN | GLR | +| | | GLR | HLR | +| mwdMngtContext | v3 | VLR or SGSN | GLR | +| | | GLR | HLR | +| msPurgingContext | v3 | VLR or SGSN | GLR | +| | | GLR | HLR | +| resetContext | v2 | HLR | GLR | +| | | GLR | VLR or SGSN | +| networkUnstructuredSsContext | v2 | VLR | GLR | +| | | GLR | HLR | +| | | HLR | GLR | +| | | GLR | VLR | +| networkFunctionalSsContext | v2 | VLR | GLR | +| | | GLR | HLR | +| shortMsgMT-RelayContext | v3 | MSC | IM-MSC or GLR | +| | | IM-MSC | MSC | +| | | GLR | SGSN | +| networkLocUpContext | v3 | VLR | GLR | +| | | GLR | HLR | +| gprsLocationUpdateContext | v3 | SGSN | GLR | +| | | GLR | HLR | +| subscriberDataMngtContext | v3 | HLR | GLR | +| | | GLR | VLR or SGSN | +| roamingNumberEnquiryContext | v3 | HLR | GLR | +| | | GLR | VLR | +| gprsLocationInfoRetrievalContext | v3 | IM-GSN | GLR | +| failureReportContext | v3 | IM-GSN | GLR | +| subscriberInfoEnquiryContext | v3 | HLR | GLR | +| | | GLR | VLR | +| reportingContext | v3 | VLR | GLR | +| | | GLR | HLR | +| | | HLR | GLR | +| | | GLR | VLR | +| callCompletionContext | v3 | VLR | GLR | +| | | GLR | HLR | +| authenticationFailureReportContext | v3 | VLR or SGSN | GLR | +| | | GLR | HLR | +| SecureTransportHandlingContext | v3 | This application context is used for the secure transport of MAP messages between any MAP entities. | | + +# 18 General on MAP user procedure + +Refer to 3GPP TS 29.002 for general matters for procedure description such as notation convention, version handling at dialogue establishment and interaction between MAP provider and MAP users. + +# 19 Mobility procedures + +## 19.1 Location management Procedures + +For non-GPRS subscribers, this subclause comprises a number of processes to handle the mobile nature of the subscriber. The processes will be addressed by SCCP SSN (VLR or HLR) and the Application Context. The processes in the GLR interact with the processes in the VLR or HLR defined in 29.002. The followings show the relations between the protocol processes in the GLR and the processes in the other node. + +Process Update Location (VLR-GLR): + +- Initiator: Update\_Location\_Area\_VLR or Update\_Location\_HLR; +- Responder: Update\_Location\_GLR. + +Process Update Location (GLR-HLR): + +- Initiator: GLR\_Update\_Location\_HLR; +- Responder: Update\_Location\_HLR. + +Process Cancel Location (VLR-GLR): + +- Initiator: GLR\_Cancel\_Location\_VLR; +- Responder: Cancel\_Location\_VLR. + +Process Cancel Location (GLR-HLR): + +- Initiator: Cancel\_Location\_HLR; +- Responder: Cancel\_Location\_GLR. + +Process Purge MS (VLR-GLR): + +- Initiator: Purge\_MS\_VLR; +- Responder: Purge\_MS\_GLR. + +Process Purge MS (GLR-HLR): + +- Initiator: GLR\_Purge\_MS\_HLR; +- Responder: Purge\_MS\_HLR. + +A Location Management Co-ordinator in the GLR co-ordinates the two protocol processes "Update\_Location\_GLR" (subclause 19.1.2) and "RESTORE\_DATA\_GLR" (subclause 19.2) that are addressed by the same application context. + +On receipt of a dialogue request for the Location Management Application Context, the location Management\_Coordinator\_GLR will: + +- Terminate the process in case of parameter problems; or +- Revert to MAP version Vr protocol if the VLR requests version Vr protocol; or +- Continue as described in the following, if the dialogue is accepted. + +The protocol process is created depending on the first primitive received from the MAP service provider within this dialogue: + +- Update\_Location\_GLR if the primitive is a MAP\_UPDATE\_LOCATION indication. +- RESTORE\_DATA\_GLR if the primitive is a MAP\_RESTORE\_DATA indication. + +If a MAP\_NOTICE indication is received instead, the dialogue towards the VLR is terminated and the process returns to idle state. + +After creation of the protocol process the service primitive received from the MAP service-provider is passed to the protocol process. Henceforth, the co-ordinator will relay all service primitives from MAP service-provider to the MAP service-user and vice versa, until a request or indication for dialogue termination is received. This last primitive will be relayed, too, before the Co-ordinator process returns to idle state. + + + +**Process Location\_Management\_Coordinator\_GLR** 19.1.1.1(1) + +Location management coordination process in the GLR + +``` + +graph TD + Start([ ]) --> NULL1([NULL]) + NULL1 --> OpenInd[Receive_Open_Ind] + OpenInd --- Section251[Section 25.1] + OpenInd --> OK[OK] + OpenInd --> Vr[Vr] + OpenInd --> Error[Error] + OK --> WaitForServicePrimitive([WAIT_FOR_SERVICE_PRIMITIVE]) + Vr --> PerformVrDialogue[Perform_MAP_Vr_Dialogue] + PerformVrDialogue --> NULL2([NULL]) + Error --> NULL3([NULL]) + WaitForServicePrimitive --> UpdateInd[MAP_UPDATE_LOCATION_Ind] + WaitForServicePrimitive --> RestoreInd[MAP_RESTORE_DATA_Ind] + WaitForServicePrimitive --> NoticeInd[MAP_NOTICE_Ind] + UpdateInd --> UpdateGlr[Update_Location_GLR] + RestoreInd --> RestoreGlr[RESTORE_DATA_GLR] + NoticeInd --> CloseReq[MAP-CLOSE_Req] + UpdateGlr --> UpdateOut[MAP_UPDATE_LOCATION_Ind] + RestoreGlr --> RestoreOut[MAP_RESTORE_DATA_Ind] + CloseReq --> NULL4([NULL]) + UpdateOut --> RelayInfo1([RELAY_INFO]) + RestoreOut --> RelayInfo2([RELAY_INFO]) + RelayInfo1 --> FromProvider[from Provider] + RelayInfo2 --> FromOffspring[from OFFSPRING] + FromProvider --> ToOffspring1[to OFFSPRING] + ToOffspring1 --> RelayInfo3([RELAY_INFO]) + FromOffspring --> ToProvider1[to Provider] + ToProvider1 --> RelayInfo4([RELAY_INFO]) + FromOffspring --> AbortReq[MAP-U-ABORT_Req, MAP-CLOSE_Req from OFFSPRING] + AbortReq --> ToProvider2[to Provider] + ToProvider2 --> NULL5([NULL]) + FromOffspring --> AbortInd[MAP-P-ABORT_Ind, MAP-U-ABORT_Ind, MAP-CLOSE_Ind] + AbortInd --> ToOffspring2[to OFFSPRING] + ToOffspring2 --> NULL6([NULL]) + +``` + +Flowchart of Process Location\_Management\_Coordinator\_GLR. The process starts with an oval, leading to a 'NULL' state. It then receives an 'Open\_Ind' primitive (Section 25.1). From here, three paths emerge: 'OK' leads to 'WAIT\_FOR\_SERVICE\_PRIMITIVE'; 'Vr' leads to 'Perform\_MAP\_Vr\_Dialogue' which ends in 'NULL'; 'Error' leads directly to 'NULL'. 'WAIT\_FOR\_SERVICE\_PRIMITIVE' leads to three parallel processing paths: 1) 'MAP\_UPDATE\_LOCATION\_Ind' -> 'Update\_Location\_GLR' -> 'MAP\_UPDATE\_LOCATION\_Ind' (outward) -> 'RELAY\_INFO'; 2) 'MAP\_RESTORE\_DATA\_Ind' -> 'RESTORE\_DATA\_GLR' -> 'MAP\_RESTORE\_DATA\_Ind' (outward) -> 'RELAY\_INFO'; 3) 'MAP\_NOTICE\_Ind' -> 'MAP-CLOSE\_Req' -> 'NULL'. All three 'RELAY\_INFO' outputs converge to a central 'RELAY\_INFO' block. From this block, four paths emerge: 1) 'from Provider' -> 'to OFFSPRING' -> 'RELAY\_INFO'; 2) 'from OFFSPRING' -> 'to Provider' -> 'RELAY\_INFO'; 3) 'MAP-U-ABORT\_Req, MAP-CLOSE\_Req from OFFSPRING' -> 'to Provider' -> 'NULL'; 4) 'MAP-P-ABORT\_Ind, MAP-U-ABORT\_Ind, MAP-CLOSE\_Ind' -> 'to OFFSPRING' -> 'NULL'. + +**Figure 19.1.1/1: Process Location\_Management\_Coordinator\_GLR** + +For GPRS subscribers, this subclause comprises a number of other processes to handle the mobile nature of the subscriber. The processes will be addressed by SCCP Sub-System Number (SGSN or HLR) and the Application + +Context. The processes in the GLR interact with the processes in the VLR, SGSN or HLR defined in 29.002. The followings show the relations between the processes in the GLR and the processes in the other node: + +Process GPRS Update Location (VLR or SGSN-GLR): + +Initiator: GPRS\_Update\_Location\_Area\_VLR, or SGSN\_Update\_HLR. + +Responder: Update\_GPRS\_Location\_GLR. + +Process GPRS Update Location (GLR-HLR): + +Initiator: GLR\_Update\_GPRS\_Location\_HLR. + +Responder: Update\_GPRS\_Location\_HLR. + +Process Cancel Location (SGSN-GLR): + +Initiator: GLR\_Cancel\_Location\_SGSN. + +Responder: Cancel\_Location\_SGSN. + +Process Cancel Location (GLR-HLR): + +Initiator: Cancel\_GPRS\_Location\_HLR. + +Responder: Cancel\_GPRS\_Location\_GLR. + +Process Purge MS (SGSN-GLR): + +Initiator: Purge\_MS\_SGSN. + +Responder: Purge\_MS\_GLR\_for\_GPRS. + +Process Purge MS (GLR-HLR): + +Initiator: GLR\_Purge\_MS\_HLR\_for\_GPRS. + +Responder: Purge\_MS\_HLR. + +### 19.1.1 Location updating + +#### 19.1.1.1 General + +This location updating procedure is used to update the location information held in the network. + +If the GLR is located between the VLR and the HLR, the MAP\_UPDATE\_LOCATION service is invoked towards the GLR whose identity is contained in the VLR table. When the GLR receives a MAP\_UPDATE\_LOCATION indication, it determines whether it invokes the MAP\_UPDATE\_LOCATION service towards the HLR, and invokes it if necessary. + +If the GLR is located between the SGSN and the HLR, the MAP\_UPDATE\_GPRS\_LOCATION service is invoked towards the GLR whose identity is contained in the SGSN table. When the GLR receives a MAP\_UPDATE\_GPRS\_LOCATION indication, it determines whether it invokes the MAP\_UPDATE\_GPRS\_LOCATION service towards the HLR, and invokes it if necessary. + + + +``` + +sequenceDiagram + participant VLR_SGSN as VLR/SGSN + participant GLR + participant HLR + participant PGLR_PVLR_PSGSN as PGLR/PVLR/PSGSN + + VLR_SGSN->>GLR: MAP UPDATE_LOCATION +or MAP UPDATE GPRS LOCATION + GLR->>HLR: MAP UPDATE_LOCATION +or MAP UPDATE GPRS LOCATION + HLR->>PGLR_PVLR_PSGSN: MAP_CANCEL_LOCATION + PGLR_PVLR_PSGSN-->>HLR: MAP_CANCEL_LOCATION ack + + HLR-->>GLR: MAP INSERT SUBSCRIBER DATA + GLR-->>VLR_SGSN: MAP INSERT SUBSCRIBER DATA + VLR_SGSN->>GLR: MAP INSERT SUBSCRIBER DATA ack + GLR->>HLR: MAP INSERT SUBSCRIBER DATA ack + + HLR-->>GLR: MAP CHECK SS INDICATION + GLR-->>VLR_SGSN: MAP CHECK SS INDICATION + + HLR-->>GLR: MAP UPDATE_LOCATION ack +or MAP UPDATE GPRS LOCATION ack + GLR-->>VLR_SGSN: MAP UPDATE_LOCATION ack +or MAP UPDATE GPRS LOCATION ack + +``` + +Sequence diagram showing network interfaces and services for location updating between VLR/SGSN, GLR, HLR, and PGLR/PVLR/PSGSN. + +**Figure 19.1.2/1: Interface and services for Location updating** + +#### 19.1.1.2 Detailed procedure in the GLR + +Figure 19.1.2/2 shows the Process Update\_Location\_GLR. This process is a GLR MAP protocol machine handling location updating and is a responder to the VLR. + + + +### Process Update\_Location\_GLR + +19.1.2.2\_1(3) + +GLR MAP protocol machine handling location updating and interfacing with VLR MAP protocol machine + +Left to VLR +Right to GLR application + +``` +stateDiagram-v2 + [*] --> WAIT_FOR_SERVICE_PRIMITIVE + WAIT_FOR_SERVICE_PRIMITIVE --> MAP_Update_Location_ind + MAP_Update_Location_ind --> Update Location + Update Location --> WAIT_FOR_APPLICATION_RESPONSE + WAIT_FOR_APPLICATION_RESPONSE --> Update Location Ack + WAIT_FOR_APPLICATION_RESPONSE --> Update Location Negative Response + WAIT_FOR_APPLICATION_RESPONSE --> Insert Subscriber Data + WAIT_FOR_APPLICATION_RESPONSE --> Forward check SS indication + WAIT_FOR_APPLICATION_RESPONSE --> Abort + + Update Location Ack --> Set result + Set result --> MAP_UPDATE_LOCATION_Rsp.MAP_CLOSE_Req + MAP_UPDATE_LOCATION_Rsp.MAP_CLOSE_Req --> [*] + + Update Location Negative Response --> Set Error + Set Error --> MAP_UPDATE_LOCATION_Rsp.MAP_CLOSE_Req + MAP_UPDATE_LOCATION_Rsp.MAP_CLOSE_Req --> [*] + + Insert Subscriber Data --> 1 + 1 --> [*] + + Forward check SS indication --> WAIT_FOR_APPLICATION_RESPONSE + WAIT_FOR_APPLICATION_RESPONSE --> MAP_FORWARD_CHECK_SS_INDICATION_req.MAP_DELIMITER_req + MAP_FORWARD_CHECK_SS_INDICATION_req.MAP_DELIMITER_req --> [*] + + Abort --> MAP_U_ABORT_req + MAP_U_ABORT_req --> [*] +``` + +State transition diagram for Process Update\_Location\_GLR. The diagram shows a sequence of states and transitions starting from an initial state, through WAIT\_FOR\_SERVICE\_PRIMITIVE, MAP\_Update\_Location\_ind, Update Location, and WAIT\_FOR\_APPLICATION\_RESPONSE. From the final wait state, five transitions are possible: Update Location Ack, Update Location Negative Response, Insert Subscriber Data, Forward check SS indication, and Abort. Each transition leads to a specific action and output message set. Transitions 1, 2, and 3 lead to terminal states (marked with X). Transitions 4 and 5 lead to intermediate states with their own output message sets. + +Figure 19.1.2/2 (sheet 1 of 3): Process Update\_Location\_GLR + + + +### Process Update\_Location\_GLR + +19.1.2.2\_2(3) + +``` +stateDiagram-v2 + [*] --> 1 + 1 --> WAIT_FOR_ISD_Cnf_WAIT_FOR_SUBSEQUENT_APPLICATION_RESPONSE + WAIT_FOR_ISD_Cnf_WAIT_FOR_SUBSEQUENT_APPLICATION_RESPONSE --> MAP_INSERT_SUBSCRIBER_CNF: MAP_Insert_Subscriber_Cnf + WAIT_FOR_ISD_Cnf_WAIT_FOR_SUBSEQUENT_APPLICATION_RESPONSE --> MAP_U_ABORT_IND_MAP_P_ABORT_IND_MAP_CLOSE_IND: MAP_U_ABORT_Ind, MAP_P_ABORT_Ind, MAP_CLOSE_Ind + WAIT_FOR_ISD_Cnf_WAIT_FOR_SUBSEQUENT_APPLICATION_RESPONSE --> MAP_NOTICE_IND: MAP_NOTICE_Ind + MAP_INSERT_SUBSCRIBER_CNF --> CHECK_CONFIRMATION: Check Confirmation + CHECK_CONFIRMATION --> INSERT_SUBSCRIBER_CNF: OK + CHECK_CONFIRMATION --> SET_NEGATIVE_RESPONSE_SYSTEM_FAILURE: Provider error, Data error + CHECK_CONFIRMATION --> MAP_USER_ERROR_TO_NEGATIVE_RESPONSE: User error + MAP_U_ABORT_IND_MAP_P_ABORT_IND_MAP_CLOSE_IND --> ABORT: Abort + ABORT --> [*] + MAP_NOTICE_IND --> SET_NEGATIVE_RESULT_SYSTEM_FAILURE: Set Negative Result System Failure + SET_NEGATIVE_RESULT_SYSTEM_FAILURE --> ISD_NEGATIVE_RESPONSE_1: ISD Negative Response + ISD_NEGATIVE_RESPONSE_1 --> 2 + INSERT_SUBSCRIBER_CNF --> 2 + SET_NEGATIVE_RESPONSE_SYSTEM_FAILURE --> ISD_NEGATIVE_RESPONSE_2: ISD Negative Response + MAP_USER_ERROR_TO_NEGATIVE_RESPONSE --> ISD_NEGATIVE_RESPONSE_2 + ISD_NEGATIVE_RESPONSE_2 --> 2 +``` + +GLR MAP protocol machine handling location updating and interfacing with VLR MAP protocol machine + +Left to VLR +Right to GLR application + +MAP\_Insert\_Subscriber\_Data\_Req +MAP\_Delimiter\_Req + +WAIT\_FOR\_ISD\_Cnf +WAIT\_FOR\_SUBSEQUENT\_APPLICATION\_RESPONSE + +MAP\_Insert\_Subscriber\_Cnf + +MAP\_U\_ABORT\_Ind +MAP\_P\_ABORT\_Ind +MAP\_CLOSE\_Ind + +Abort + +MAP\_NOTICE\_Ind + +Set Negative Result System Failure + +ISD Negative Response + +2 + +Check Confirmation + +Section 25.2 + +OK + +Provider error +Data error + +User error + +Insert\_Subscriber\_Cnf + +Set Negative Response System Failure + +MAP User Error to Negative Response + +ISD Negative Response + +2 + +State transition diagram for Process Update\_Location\_GLR. The process starts at state 1, receives MAP\_Insert\_Subscriber\_Data\_Req and MAP\_Delimiter\_Req, enters a wait state, then branches based on MAP\_Insert\_Subscriber\_Cnf, MAP\_U\_ABORT\_Ind/MAP\_P\_ABORT\_Ind/MAP\_CLOSE\_Ind, or MAP\_NOTICE\_Ind. The diagram includes callouts for GLR MAP protocol machine handling and VLR/GLR application interactions, and references to Section 25.2. + +Figure 19.1.2/2 (sheet 2 of 3): Process Update\_Location\_GLR + + + +### Process Update\_Location\_GLR + +19.1.2.2\_3(3) + +GLR MAP protocol machine handling location updating and interfaceing with VLR MAP protocol machine + +Left to VLR +Right to GLR application + +``` + +stateDiagram-v2 + state "WAIT_FOR_ISD_Cnf +WAIT_FOR_SUBSEQUENT_APPLICATION_RESPONSE" as WAIT + + [*] --> WAIT + + WAIT --> UpdateLocationAck : Update Location Ack + WAIT --> UpdateLocationNeg : Update Location Negative Response + WAIT --> InsertSubData : Insert Subscriber Data + WAIT --> Abort : Abort + + UpdateLocationAck --> SetResult : Set result + UpdateLocationNeg --> SetError : Set Error + + SetResult --> Output1 + SetError --> Output1 + + state "MAP_UPDATE_LOCATION_Rsp. +MAP_CLOSE_Req." as Output1 + Output1 --> [*] + + InsertSubData --> Connector1 : 1 + + Abort --> MAP_U_ABORT_Req : MAP_U_ABORT_Req. + MAP_U_ABORT_Req --> [*] + +``` + +SDL diagram for Process Update\_Location\_GLR showing state transitions from WAIT\_FOR\_ISD\_Cnf and WAIT\_FOR\_SUBSEQUENT\_APPLICATION\_RESPONSE based on various inputs like Update Location Ack, Negative Response, Insert Subscriber Data, and Abort. + +Figure 19.1.2/2 (sheet 3 of 3): Process Update\_Location\_GLR + +Figure 19.1.2/3 shows the Process GLR\_Update\_Location\_HLR. This process is a GLR MAP protocol machine handling location updating and is an initiator to the HLR. + +Sheet 1: If the Macro Open\_Receive\_Cnf results Vr, the process requests to perform MAP Vr. It causes a request for sending an abort message to Process Update\_Location\_GLR. + + + +### Process GLR\_Update\_Location\_HLR + +19.1.2.3\_1(3) + +GLR MAP protocol machine handling Location Management and interfacing to HLR MAP protocol machine, handling Location Management. + +Signals to/from the left are to/from the GLR application. +Signals to/from the right are to/from the HLR MAP protocol machine. + +``` +graph TD; Start([ ]) --> IDLE([IDLE]); IDLE --> UpdateLocation{Update Location}; UpdateLocation --> Decision{ }; Decision --> Req["MAP_OPEN_Req
MAP_UPDATE_LOCATION_Req
MAP_DELIMITER_Req"]; Req --> ReceiveOpenCnf[Receive Open Cnf]; ReceiveOpenCnf --- Section251[Section 25.1]; ReceiveOpenCnf -- OK --> WaitForHLR[Wait_For_HLR_Response]; ReceiveOpenCnf -- Vr --> PerformMAPVr{Perform MAP Vr}; ReceiveOpenCnf -- Error --> SetError[Set error]; SetError --> UpdateLocationNeg[Update Location Negative Response]; PerformMAPVr --> End1[ ]; UpdateLocationNeg --> End2[ ] +``` + +Flowchart for Process GLR\_Update\_Location\_HLR. The process starts at an oval, goes to an IDLE state (oval), then an Update Location transition (chevron). It then enters a loop: a decision diamond (left side) leads to a box with MAP\_OPEN\_Req, MAP\_UPDATE\_LOCATION\_Req, and MAP\_DELIMITER\_Req; this leads to a Receive Open Cnf state (double rectangle, linked to Section 25.1). From Receive Open Cnf, three paths emerge: OK leads to Wait\_For\_HLR\_Response (oval); Vr leads to Perform MAP Vr (diamond); Error leads to Set error (rectangle) then Update Location Negative Response (chevron). Both Perform MAP Vr and Update Location Negative Response lead to end symbols (crossed lines). + +Figure 19.1.2/3 (Sheet 1 of 3): Process GLR\_Update\_Location\_HLR + + + +### Process GLR\_Update\_Location\_HLR + +19.1.2.3\_2(3) + +GLR MAP protocol machine handling Location Management and interfacing to HLR MAP protocol machine, handling Location Management. + +Signals to/from the left are to/from the GLR application. +Signals to/from the right are to/from the HLR MAP protocol machine. + +``` + +stateDiagram-v2 + state "Wait_For_HLR_Response" as WaitHLR + state "Wait_For_HLR_or_Application_Response" as WaitHLRApp + state "Idle" as Idle + + [*] --> WaitHLR + + WaitHLR --> MAP_FORWARD_Check_SS_ind + MAP_FORWARD_Check_SS_ind --> Forward_Check_SS_Indication + Forward_Check_SS_Indication --> WaitHLR + + WaitHLR --> MAP_INSERT_SUBSCRIBER_DATA_ind + MAP_INSERT_SUBSCRIBER_DATA_ind --> Insert_Subscriber_data + Insert_Subscriber_data --> WaitHLRApp + + WaitHLRApp --> MAP_Update_Location_cnf + MAP_Update_Location_cnf --> Check_Confirmation + state Check_Confirmation <> + Check_Confirmation --> Update_Location_ack : OK + Check_Confirmation --> Set_negative_response_1 : Provider Error, User Error, Data Error + Update_Location_ack --> Idle + Set_negative_response_1 --> Update_Location_negative_response_1 + Update_Location_negative_response_1 --> Idle + + WaitHLR --> MAP_Notice_Indication + MAP_Notice_Indication --> MAP_Close_request + MAP_Close_request --> Set_negative_response_2 + Set_negative_response_2 --> Update_Location_negative_response_2 + Update_Location_negative_response_2 --> Idle + + WaitHLR --> MAP_Abort_Signals + state "MAP_U_Abort_ind\nMAP_P_Abort_ind\nMAP_Close_ind" as MAP_Abort_Signals + MAP_Abort_Signals --> Abort + Abort --> Idle + +``` + +Section 25.2 + +SDL Diagram for Process GLR\_Update\_Location\_HLR showing state transitions from Wait\_For\_HLR\_Response based on various MAP signals leading to Idle or further wait states. + +**Figure 19.1.2/3 (Sheet 2 of 3): Process GLR\_Update\_Location\_HLR** + + + +### Process GLR\_Update\_Location\_HLR + +19.1.2.3\_3(3) + +GLR MAP protocol machine handling Location Management and interfacing to HLR MAP protocol machine, handling Location Management. + +Signals to/from the left are to/from the GLR application. +Signals to/from the right are to/from the HLR MAP protocol machine. + +``` +stateDiagram-v2 + [*] --> Wait_For_HLR_or_Application_Response_1 : Wait_For_HLR_or_Application_Response + state "Wait_For_HLR_or_Application_Response" as Wait_For_HLR_or_Application_Response_1 + state "MAP_FORWARD_Check_SS_ind" as MAP_FORWARD_Check_SS_ind + state "MAP_INSERT_SUBSCRIBER_DATA_ind" as MAP_INSERT_SUBSCRIBER_DATA_ind + state "Forward Check SS Indication" as Forward_Check_SS_Indication + state "Insert Subscriber data" as Insert_Subscriber_data + state "Insert Subscriber Data ack" as Insert_Subscriber_Data_ack + state "Insert Subscriber Data negative response" as Insert_Subscriber_Data_negative_response + state "Set user error" as Set_user_error + state "MAP_Insert Subscriber Data response" as MAP_Insert_Subscriber_Data_response + state "MAP_Update_Location_cnf" as MAP_Update_Location_cnf + state "Check Confirmation" as Check_Confirmation + state "Update Location ack" as Update_Location_ack + state "Set negative response" as Set_negative_response_1 + state "Update Location negative response" as Update_Location_negative_response_1 + state "Abort" as Abort_1 + state "Map_U_Abort request" as Map_U_Abort_request + state "MAP_Notify_Indication" as MAP_Notify_Indication + state "MAP_Close_request" as MAP_Close_request + state "MAP_U_Abort_ind" as MAP_U_Abort_ind + state "MAP_P_Abort_ind" as MAP_P_Abort_ind + state "MAP_Close_ind" as MAP_Close_ind + state "Idle" as Idle_1 + state "Idle" as Idle_2 + + Wait_For_HLR_or_Application_Response_1 --> MAP_FORWARD_Check_SS_ind + Wait_For_HLR_or_Application_Response_1 --> MAP_INSERT_SUBSCRIBER_DATA_ind + MAP_FORWARD_Check_SS_ind --> Forward_Check_SS_Indication + Forward_Check_SS_Indication --> [*] + MAP_INSERT_SUBSCRIBER_DATA_ind --> Insert_Subscriber_data + Insert_Subscriber_data --> Insert_Subscriber_Data_ack + Insert_Subscriber_Data_ack --> [*] + Insert_Subscriber_Data_ack --> Insert_Subscriber_Data_negative_response + Insert_Subscriber_Data_negative_response --> Set_user_error + Set_user_error --> [*] + Insert_Subscriber_Data_ack --> MAP_Insert_Subscriber_Data_response + MAP_Insert_Subscriber_Data_response --> [*] + + [*] --> Wait_For_HLR_or_Application_Response_2 : Wait_For_HLR_or_Application_Response + state "Wait_For_HLR_or_Application_Response" as Wait_For_HLR_or_Application_Response_2 + Wait_For_HLR_or_Application_Response_2 --> MAP_Update_Location_cnf + Wait_For_HLR_or_Application_Response_2 --> Abort_1 + Wait_For_HLR_or_Application_Response_2 --> MAP_Notify_Indication + Wait_For_HLR_or_Application_Response_2 --> MAP_U_Abort_ind + Wait_For_HLR_or_Application_Response_2 --> MAP_P_Abort_ind + Wait_For_HLR_or_Application_Response_2 --> MAP_Close_ind + + MAP_Update_Location_cnf --> Check_Confirmation + Check_Confirmation --> Update_Location_ack : OK + Check_Confirmation --> Set_negative_response_1 : Provider Error, User Error, Data Error + Update_Location_ack --> Idle_1 + Set_negative_response_1 --> Update_Location_negative_response_1 + Update_Location_negative_response_1 --> Idle_1 + + Abort_1 --> Map_U_Abort_request + Map_U_Abort_request --> [*] + + MAP_Notify_Indication --> MAP_Close_request + MAP_Close_request --> Set_negative_response_2 : Set negative response + Set_negative_response_2 --> Update_Location_negative_response_2 : Update Location negative response + Update_Location_negative_response_2 --> Idle_2 + + MAP_U_Abort_ind --> Abort_2 : Abort + MAP_P_Abort_ind --> Abort_2 + MAP_Close_ind --> Abort_2 + Abort_2 --> Idle_2 +``` + +State transition diagram for Process GLR\_Update\_Location\_HLR. The diagram shows two main sections. The top section handles 'MAP\_INSERT\_SUBSCRIBER\_DATA\_ind' from the application, leading to 'Insert Subscriber data' (GLR internal), then 'Insert Subscriber Data ack' (to HLR), and finally 'MAP\_Insert Subscriber Data response' (to HLR). The bottom section handles 'MAP\_Update\_Location\_cnf' from the HLR, leading to 'Check Confirmation' (GLR internal), then 'Update Location ack' (to application) or 'Set negative response' (to application), ending in 'Idle'. Other states include 'MAP\_FORWARD\_Check\_SS\_ind', 'MAP\_U\_Abort\_ind', 'MAP\_P\_Abort\_ind', and 'MAP\_Close\_ind' leading to 'Abort' and 'Idle'. + +Figure 19.1.2/3 (Sheet 3 of 3): Process GLR\_Update\_Location\_HLR + +Figure 19.1.2/4 shows the Process Update\_GPRS\_Location\_GLR. This process is a GLR MAP protocol machine handling location updating and is a responder to the SGSN. + + + +### Process Update\_GPRS\_Location\_GLR + +19.1.2.4\_1(3) + +``` +stateDiagram-v2 + [*] --> NULL1[NULL] + NULL1 --> Receive_Open_Ind[Receive Open Ind.] + Receive_Open_Ind --> WAIT_FOR_SERVICE_PRIMITIVE[WAIT_FOR_SERVICE_PRIMITIVE] + WAIT_FOR_SERVICE_PRIMITIVE --> MAP_Update_GPRS_Location_ind{MAP_Update_GPRS_Location_ind} + MAP_Update_GPRS_Location_ind --> Update_GPRS_Location[Update GPRS Location] + Update_GPRS_Location --> 2((2)) + 2 --> WAIT_FOR_APPLICATION_RESPONSE[WAIT_FOR APPLICATION RESPONSE] + WAIT_FOR_APPLICATION_RESPONSE --> Update_GPRS_Location_Ack[Update GPRS Location Ack] + WAIT_FOR_APPLICATION_RESPONSE --> Update_GPRS_Location_Negative_Response[Update GPRS Location Negative Response] + WAIT_FOR_APPLICATION_RESPONSE --> Insert_Subscriber_Data[Insert Subscriber Data] + WAIT_FOR_APPLICATION_RESPONSE --> Abort[Abort] + Update_GPRS_Location_Ack --> Set_result[Set result] + Set_result --> MAP_UPDATE_GPRS_LOCATION_Rsp_1{MAP_UPDATE_GPRS_LOCATION_Rsp. MAP_CLOSE_Req.} + Update_GPRS_Location_Negative_Response --> Set_error[Set error] + Set_error --> MAP_UPDATE_GPRS_LOCATION_Rsp_2{MAP_UPDATE_GPRS_LOCATION_Rsp. MAP_CLOSE_Req.} + Insert_Subscriber_Data --> 1((1)) + Abort --> MAP_U_ABORT_req{MAP_U_ABORT_req.} +``` + +GLR MAP protocol machine handling location updating and interfacing with SGSN MAP protocol machine + +Left to SGSN +Right to GLR application + +OK + +V2 + +V1 Error + +NULL + +NULL + +Perform\_MAP\_Vr\_Dialogue + +Receive Open Ind. + +WAIT\_FOR\_SERVICE\_PRIMITIVE + +MAP\_Update\_GPRS\_Location\_ind + +Update GPRS Location + +2 + +WAIT\_FOR\_APPLICATION\_RESPONSE + +Update GPRS Location Ack + +Set result + +MAP\_UPDATE\_GPRS\_LOCATION\_Rsp. MAP\_CLOSE\_Req. + +Update GPRS Location Negative Response + +Set error + +MAP\_UPDATE\_GPRS\_LOCATION\_Rsp. MAP\_CLOSE\_Req. + +Insert Subscriber Data + +1 + +Abort + +MAP\_U\_ABORT\_req. + +State transition diagram for Process Update\_GPRS\_Location\_GLR. The process starts at an initial state, goes to NULL, then receives an Open Indication. From there, it branches based on version: V2 leads to Perform\_MAP\_Vr\_Dialogue and then NULL; V1 Error leads to NULL; OK leads to WAIT\_FOR\_SERVICE\_PRIMITIVE. From WAIT\_FOR\_SERVICE\_PRIMITIVE, it sends a MAP\_Update\_GPRS\_Location\_ind to the application. The application responds with Update GPRS Location, which leads to connector 2. From connector 2, it goes to WAIT\_FOR\_APPLICATION\_RESPONSE. From this wait state, it handles three possible responses: Update GPRS Location Ack (leading to Set result and then MAP\_UPDATE\_GPRS\_LOCATION\_Rsp. MAP\_CLOSE\_Req.), Update GPRS Location Negative Response (leading to Set error and then MAP\_UPDATE\_GPRS\_LOCATION\_Rsp. MAP\_CLOSE\_Req.), or Insert Subscriber Data (leading to connector 1). An Abort response leads to MAP\_U\_ABORT\_req. Callouts indicate the process is a GLR MAP protocol machine interfacing with SGSN MAP and that messages go left to SGSN and right to GLR application. + +Figure 19.1.2/4 (sheet 1 of 3): Process Update\_GPRS\_Location\_GLR + + + +### Process Update\_GPRS\_Location\_GLR + +19.1.2.4\_2(3) + +GLR MAP protocol machine handling location updating and interfacing with SGSN MAP protocol machine + +``` +stateDiagram-v2 + [*] --> 1 + 1 --> 3 + 3 --> Request + state "MAP_Insert_Subscriber_Data_Req
MAP_Delimiter_Req" as Request + Request --> WAIT + state "WAIT_FOR_ISD_Cnf
WAIT_FOR_SUBSEQUENT_APPLICATION_RESPONSE" as WAIT + WAIT --> Insert_Cnf + state "MAP_Insert_Subscriber_Cnf" as Insert_Cnf + WAIT --> Abort + state "MAP_U_ABORT_Ind
MAP_P_ABORT_Ind
MAP_CLOSE_Ind" as Abort + WAIT --> Notice_Ind + state "MAP_NOTICE_Ind" as Notice_Ind + Insert_Cnf --> Check + state "Check Confirmation" as Check + Check --> OK + Check --> Provider_Error + Check --> User_Error + OK --> Insert_Data_Cnf + state "Insert_Subscriber_Data_Cnf" as Insert_Data_Cnf + Insert_Data_Cnf --> 2 + Provider_Error --> Set_Neg_Resp + state "Set Negative Response System Failure" as Set_Neg_Resp + User_Error --> MAP_User_Error + state "MAP User Error to Negative Response" as MAP_User_Error + Set_Neg_Resp --> ISD_Neg_Resp_2 + state "ISD Negative Response" as ISD_Neg_Resp_2 + ISD_Neg_Resp_2 --> 2 + Notice_Ind --> Set_Neg_Resp_3 + state "Set Negative Result System Failure" as Set_Neg_Resp_3 + Set_Neg_Resp_3 --> ISD_Neg_Resp_3 + state "ISD Negative Response" as ISD_Neg_Resp_3 + ISD_Neg_Resp_3 --> 3 +``` + +Left to SGSN +Right to GLR application + +Section 25.2 + +State transition diagram for Process Update\_GPRS\_Location\_GLR. The process starts at connector 1, moves to connector 3, and sends MAP\_Insert\_Subscriber\_Data\_Req and MAP\_Delimiter\_Req. It then enters a WAIT state. From WAIT, it can receive MAP\_Insert\_Subscriber\_Cnf (leading to Check Confirmation), MAP\_U\_ABORT\_Ind/MAP\_P\_ABORT\_Ind/MAP\_CLOSE\_Ind (leading to Abort), or MAP\_NOTICE\_Ind (leading to Set Negative Result System Failure). Check Confirmation leads to OK (Insert\_Subscriber\_Data\_Cnf to connector 2), Provider error Data error (Set Negative Response System Failure), or User error (MAP User Error to Negative Response). Both Set Negative Response System Failure and MAP User Error to Negative Response lead to ISD Negative Response to connector 2. MAP\_NOTICE\_Ind also leads to ISD Negative Response to connector 3. + +Figure 19.1.2/4 (sheet 2 of 3): Process Update\_GPRS\_Location\_GLR + + + +### Process Update\_GPRS\_Location\_GLR + +19.1.2.4\_3(3) + +GLR MAP protocol machine handling location updating and interfacing with SGSN MAP protocol machine + +Left to SGSN +Right to GLR application + +``` + +stateDiagram-v2 + state "WAIT_FOR_ISD_Cnf\nWAIT_FOR_SUBSEQUENT_\nAPPLICATION_RESPONSE" as MainState + + MainState --> Update_Location_Ack + MainState --> Update_GPRS_Location_Negative_Response + MainState --> Insert_Subscriber_Data + MainState --> Abort + + Update_Location_Ack --> Set_result + Set_result --> MAP_UPDATE_LOCATION_Rsp + MAP_UPDATE_LOCATION_Rsp --> [*] + + Update_GPRS_Location_Negative_Response --> Set_Error + Set_Error --> MAP_UPDATE_LOCATION_Rsp + + Insert_Subscriber_Data --> Connector_1 : 1 + + Abort --> MAP_U_ABORT_req + MAP_U_ABORT_req --> [*] + +``` + +SDL Diagram for Process Update\_GPRS\_Location\_GLR showing transitions from WAIT\_FOR\_ISD\_Cnf and WAIT\_FOR\_SUBSEQUENT\_APPLICATION\_RESPONSE states based on inputs like Update Location Ack, Update GPRS Location Negative Response, Insert Subscriber Data, and Abort. + +**Figure 19.1.2/4 (sheet 3 of 3): Process Update\_GPRS\_Location\_GLR** + +Figure 19.1.2/5 shows the Process GLR\_Update\_GPRS\_Location\_HLR. This process is a GLR MAP protocol machine handling location updating and is an initiator to the HLR. + +Sheet 1: If the Macro Open\_Receive\_Cnf results Vr, the process requests to perform MAP Vr. It causes a request for sending an abort message to Process Update\_GPRS\_Location\_GLR. + + + +### Process GLR\_Update\_GPRS\_Location\_HLR 19.1.2.5\_1(3) + +GLR MAP protocol machine handling Location Management and interfacing to HLR MAP protocol machine, handling Location Management. + +Signals to/from the left are to/from the GLR application. +Signals to/from the right are to/from the HLR MAP protocol machine. + +``` + +stateDiagram-v2 + [*] --> IDLE + IDLE --> Update_GPRS_Location : Update GPRS Location + state Update_GPRS_Location { + direction LR + MAP_OPEN_Req + MAP_UPDATE_GPRS_LOCATION_Req + MAP_DELIMITER_Req + } + Update_GPRS_Location --> Receive_Open_Cnf + state "Receive Open Cnf. (Section 25.1)" as Receive_Open_Cnf + Receive_Open_Cnf --> Wait_For_HLR_Response : OK + Receive_Open_Cnf --> Perform_MAP_Vr : Vr + Receive_Open_Cnf --> Set_error : Error + + state "Wait_For_HLR_Response" as Wait_For_HLR_Response + + state Perform_MAP_Vr { + Perform_MAP_Vr_Signal : Perform MAP Vr + } + Perform_MAP_Vr --> [*] + + state Set_error { + Set_error_Task : Set error + Negative_Response : Update GPRS Location Negative Response + } + Set_error --> [*] + +``` + +SDL diagram for Process GLR\_Update\_GPRS\_Location\_HLR. The flow starts at IDLE, receives 'Update GPRS Location', sends MAP requests, calls 'Receive Open Cnf.', and branches into OK (Wait\_For\_HLR\_Response), Vr (Perform MAP Vr), or Error (Set error and Negative Response). + +Figure 19.1.2/5 (Sheet 1 of 3): Process GLR\_Update\_GPRS\_Location\_HLR + + + +### Process GLR\_Update\_GPRS\_Location\_HLR + +19.1.2.5\_2(3) + +GLR MAP protocol machine handling Location Management and interfacing to HLR MAP protocol machine, handling Location Management. + +Signals to/from the left are to/from the GLR application. +Signals to/from the right are to/from the HLR MAP protocol machine. + +``` +stateDiagram-v2 + [*] --> Wait_For_HLR_Response + state "Wait_For_HLR_Response" as Wait_For_HLR_Response + state "MAP_Update_GPRS_Location_cnf" as MAP_Update_GPRS_Location_cnf + state "MAP_INSERT_SUBSCRIBER_DATA_ind" as MAP_INSERT_SUBSCRIBER_DATA_ind + state "MAP_Notice_Indication" as MAP_Notice_Indication + state "MAP_U_Abort_ind, MAP_P_Abort_ind, MAP_Close_ind" as MAP_U_Abort_ind_MAP_P_Abort_ind_MAP_Close_ind + state "Check Confirmation" as CheckConfirmation["Check Confirmation (Section 25.2)"] + state "Insert Subscriber Data" as InsertSubscriberData + state "MAP_Close_request" as MAP_Close_request + state "Abort" as Abort + state "Update GPRS Location ack" as UpdateGPRSLocationAck + state "Set negative response" as SetNegativeResponse1[Set negative response] + state "Wait_For_HLR_or_Application_Response" as Wait_For_HLR_or_Application_Response + state "Set negative response" as SetNegativeResponse2[Set negative response] + state "Update GPRS Location negative response" as UpdateGPRSLocationNegativeResponse + state "Idle" as Idle + + Wait_For_HLR_Response --> MAP_Update_GPRS_Location_cnf + Wait_For_HLR_Response --> MAP_INSERT_SUBSCRIBER_DATA_ind + Wait_For_HLR_Response --> MAP_Notice_Indication + Wait_For_HLR_Response --> MAP_U_Abort_ind_MAP_P_Abort_ind_MAP_Close_ind + + MAP_Update_GPRS_Location_cnf --> CheckConfirmation + CheckConfirmation --> UpdateGPRSLocationAck : OK + CheckConfirmation --> SetNegativeResponse1 : Provider Error, User Error, Data Error + UpdateGPRSLocationAck --> Idle + SetNegativeResponse1 --> UpdateGPRSLocationNegativeResponse + UpdateGPRSLocationNegativeResponse --> Idle + + MAP_INSERT_SUBSCRIBER_DATA_ind --> InsertSubscriberData + InsertSubscriberData --> Wait_For_HLR_or_Application_Response + + MAP_Notice_Indication --> MAP_Close_request + MAP_Close_request --> SetNegativeResponse2 + SetNegativeResponse2 --> UpdateGPRSLocationNegativeResponse + UpdateGPRSLocationNegativeResponse --> Idle + + MAP_U_Abort_ind_MAP_P_Abort_ind_MAP_Close_ind --> Abort + Abort --> Idle +``` + +State transition diagram for Process GLR\_Update\_GPRS\_Location\_HLR. The diagram shows four main entry points from 'Wait\_For\_HLR\_Response': 1) MAP\_Update\_GPRS\_Location\_cnf leads to 'Check Confirmation' (Section 25.2), which results in 'Update GPRS Location ack' (OK) or 'Set negative response' (Provider Error, User Error, Data Error), both leading to 'Idle'. 2) MAP\_INSERT\_SUBSCRIBER\_DATA\_ind leads to 'Insert Subscriber Data', which leads to 'Wait\_For\_HLR\_or\_Application\_Response'. 3) MAP\_Notice\_Indication leads to 'MAP\_Close\_request', which leads to 'Set negative response', then 'Update GPRS Location negative response', and finally 'Idle'. 4) MAP\_U\_Abort\_ind, MAP\_P\_Abort\_ind, and MAP\_Close\_ind all lead to 'Abort', which leads to 'Idle'. + +Figure 19.1.2/5 (Sheet 2 of 3): Process GLR\_Update\_GPRS\_Location\_HLR + + + +**Process GLR\_Update\_GPRS\_Location\_HLR** 19.1.2.5\_3(3) + +GLR MAP protocol machine handling Location Management and interfacing to HLR MAP protocol machine, handling Location Management. + +Signals to/from the left are to/from the GLR application. + + Signals to/from the right are to/from the HLR MAP protocol machine. + +``` + + stateDiagram-v2 + state "Wait_For_HLR_or_Application_Response" as Wait1 + state "Wait_For_HLR_or_Application_Response" as Wait2 + state "Idle" as Idle1 + state "Idle" as Idle2 + + Wait1 --> MAP_INSERT_SUBSCRIBER_DATA_ind + MAP_INSERT_SUBSCRIBER_DATA_ind --> Insert_Subscriber_Data_Decision + + Insert_Subscriber_Data_Decision --> Insert_Subscriber_Data_ack + Insert_Subscriber_Data_Decision --> Insert_Subscriber_Data_negative_response + + Insert_Subscriber_Data_ack --> MAP_Insert_Subscriber_Data_response + Insert_Subscriber_Data_negative_response --> Set_user_error + Set_user_error --> MAP_Insert_Subscriber_Data_response + + MAP_Insert_Subscriber_Data_response --> Wait2 + + Wait2 --> MAP_Update_GPRS_Location_cnf + Wait2 --> Abort_Input + Wait2 --> MAP_Notice_Indication + Wait2 --> MAP_Abort_Ind_Group + + MAP_Update_GPRS_Location_cnf --> Check_Confirmation + Check_Confirmation --> OK_Path + Check_Confirmation --> Error_Path + + OK_Path --> Update_GPRS_Location_ack + Update_GPRS_Location_ack --> Idle1 + + Error_Path --> Set_negative_response_1 + Set_negative_response_1 --> Update_GPRS_Location_negative_response_1 + Update_GPRS_Location_negative_response_1 --> Idle1 + + Abort_Input --> Map_U_Abort_request + Map_U_Abort_request --> Idle2 + + MAP_Notice_Indication --> MAP_Close_request + MAP_Close_request --> Set_negative_response_2 + Set_negative_response_2 --> Update_GPRS_Location_negative_response_2 + Update_GPRS_Location_negative_response_2 --> Idle2 + + MAP_Abort_Ind_Group --> Abort_Task + Abort_Task --> Idle2 + +``` + +SDL Process Diagram for GLR\_Update\_GPRS\_Location\_HLR. The diagram illustrates the state transitions and signal handling for GPRS location updates. It includes states like 'Wait\_For\_HLR\_or\_Application\_Response' and 'Idle', inputs like 'MAP\_INSERT\_SUBSCRIBER\_DATA\_ind', and various decision points and tasks leading to either successful acknowledgement or error handling and abortion of the process. + +**Figure 19.1.2/5 (Sheet 3 of 3): Process GLR\_Update\_GPRS\_Location\_HLR** + +### 19.1.2 Location Cancellation + +#### 19.1.2.1 General + +The purpose of this process is to delete a subscriber's record from a previous GLR/VLR/SGSN after she has registered with a new GLR/VLR/SGSN. The procedure may also be used if the subscriber's record is to be deleted for other operator determined purposes. Location cancellation can be used to enforce location updating including updating of subscriber data in the VLR or in the SGSN at the next subscriber access. + +In all cases, the process is performed independently of the invoking process (e.g. Location Updating). + +If GLR is located between the VLR or the SGSN and the HLR, the MAP\_CANCEL\_LOCATION service is invoked towards the GLR whose identity is contained in the HLR table. + + + +Sequence diagram for Figure 19.1.3/1: Interface and services for Location Cancellation. The diagram shows four entities: VLR/GLR, HLR, PGLR, and PVLR. The HLR is connected to each of the other three entities by dashed lines labeled 'D'. The sequence of messages is: 1. VLR/GLR sends a solid line 'MAP\_UPDATE\_LOCATION' to HLR. 2. HLR sends a dotted line 'MAP\_CANCEL\_LOCATION' to PGLR. 3. PGLR sends a dotted line 'MAP\_CANCEL\_LOCATION' to PVLR. 4. PGLR sends a solid line 'MAP\_CANCEL\_LOCATION' back to HLR. 5. HLR sends a solid line 'ack' back to PGLR. 6. PVLR sends a solid line 'MAP\_CANCEL\_LOCATION' back to PGLR. 7. PGLR sends a solid line 'ack' back to PVLR. + +NOTE: The service shown in dotted lines indicates the trigger provided by other MAP signalling. + +**Figure 19.1.3/1: Interface and services for Location Cancellation** + + + +Sequence diagram for Figure 19.1.3/2: Interface and services for Location Cancellation in GPRS. The diagram shows four entities: SGSN/GLR, HLR, PGLR, and PSGSN. The HLR is connected to each of the other three entities by dashed lines labeled 'D'. The sequence of messages is: 1. SGSN/GLR sends a solid line 'MAP\_UPDATE\_GPRS\_LOCATION' to HLR. 2. HLR sends a dotted line 'MAP\_CANCEL\_LOCATION' to PGLR. 3. PGLR sends a dotted line 'MAP\_CANCEL\_LOCATION' to PSGSN. 4. PGLR sends a solid line 'MAP\_CANCEL\_LOCATION' back to HLR. 5. HLR sends a solid line 'ack' back to PGLR. 6. PSGSN sends a solid line 'MAP\_CANCEL\_LOCATION' back to PGLR. 7. PGLR sends a solid line 'ack' back to PSGSN. + +NOTE: The service shown in dotted lines indicates the trigger provided by other MAP signalling. + +**Figure 19.1.3/2: Interface and services for Location Cancellation in GPRS** + +Additionally, The MAP\_CANCEL\_LOCATION service is invoked when the GLR that stores the subscriber's record receives a MAP\_UPDATE\_LOCATION indication from a VLR other than that stored in its table for this subscriber. Also the MAP\_CANCEL\_LOCATION service is invoked when the GLR that stores the subscriber's record a MAP\_UPDATE\_GPRS\_LOCATION indication from a SGSN other than stored in its table for this subscriber. The MAP\_CANCEL\_LOCATION service is in any case invoked towards the VLR or the SGSN whose identity is contained in the HLR table. + + + +The diagram illustrates a sequence of messages between three entities: VLR/SGSN, GLR, and PVL/PSGSN. The entities are represented by boxes with dashed borders. The first entity (VLR/SGSN) sends a 'MAP\_UPDATE\_LOCATION or MAP\_UPDATE\_GPRS\_LOCATION' message to the second entity (GLR). The second entity (GLR) then sends a 'MAP\_CANCEL\_LOCATION' message to the third entity (PVL/PSGSN). Finally, the third entity (PVL/PSGSN) sends a 'MAP\_CANCEL\_LOCATION' message back to the second entity (GLR), which responds with an 'ack' (acknowledgment) message. + +``` +sequenceDiagram + participant VLR/SGSN + participant GLR + participant PVL/PSGSN + Note over VLR/SGSN, GLR: D + Note over GLR, PVL/PSGSN: D + VLR/SGSN->>GLR: MAP_UPDATE_LOCATION or MAP_UPDATE_GPRS_LOCATION + GLR->>PVL/PSGSN: MAP_CANCEL_LOCATION + PVL/PSGSN->>GLR: MAP_CANCEL_LOCATION + GLR-->>PVL/PSGSN: ack +``` + +Sequence diagram showing MAP UPDATE LOCATION, MAP\_CANCEL\_LOCATION, and MAP\_CANCEL\_LOCATION messages between VLR/SGSN, GLR, and PVL/PSGSN entities. + +**Figure 19.1.3/4: Interface and services for Location Cancellation in case that the GLR stores the subscriber's record** + +#### 19.1.2.2 Detailed procedure in the GLR + +Figure 19.1.3/5 shows the Process Cancel\_Location\_GLR. This process is a GLR MAP protocol machine handling location cancellation and is a responder to the HLR. + + + +### Process Cancel\_Location\_GLR + +19.1.3.5(1) + +GLR MAP protocol machine handling Location cancelation and interfacing to HLR MAP protocol machine, handling Location Cancelation. + +Signals to/from the left are to/from the GLR Location cancellation application. + +Signals to/from the right are to/from the HLR MAP protocol machine, handling Location Cancellation. + +``` +stateDiagram-v2 + [*] --> NULL1[NULL] + NULL1 --> ReceiveOpenInd[Receive Open Ind.] + ReceiveOpenInd --> WAIT_FOR_SERVICE_PRIMITIVE[WAIT_FOR_SERVICE_PRIMITIVE] : OK + ReceiveOpenInd --> Perform_MAP_Vr_Dialogue[Perform_MAP_Vr_Dialogue] : V2 + ReceiveOpenInd --> NULL2[NULL] : V1 Error + WAIT_FOR_SERVICE_PRIMITIVE --> MAP_CANCEL_LOCATION_ind[MAP_CANCEL_LOCATION_ind] + WAIT_FOR_SERVICE_PRIMITIVE --> MAP_NOTICE_ind[MAP_NOTICE_ind] + MAP_NOTICE_ind --> MAP_CLOSE_req[MAP_CLOSE_req] + MAP_CLOSE_req --> NULL3[NULL] + MAP_CANCEL_LOCATION_ind --> CancelLocation{Cancel Location} + CancelLocation --> WAIT_FOR_APPLICATION_RESPONSE[WAIT_FOR_APPLICATION_RESPONSE] + WAIT_FOR_APPLICATION_RESPONSE --> CancelLocationAck{Cancel Location Ack} + WAIT_FOR_APPLICATION_RESPONSE --> CancelLocationNegativeResponse{Cancel Location Negative response} + WAIT_FOR_APPLICATION_RESPONSE --> Abort{Abort} + CancelLocationAck --> MAP_CANCEL_LOCATION_Rsp_MAP_CLOSE_Req[MAP_CANCEL_LOCATION_Rsp. MAP_CLOSE_Req.] + CancelLocationNegativeResponse --> MAP_CANCEL_LOCATION_Rsp_MAP_CLOSE_Req + MAP_CANCEL_LOCATION_Rsp_MAP_CLOSE_Req --> NULL4[NULL] + Abort --> MAP_U_ABORT_req[MAP_U_ABORT_req] + MAP_U_ABORT_req --> NULL5[NULL] +``` + +State transition diagram for Process Cancel\_Location\_GLR. It starts with an initial state leading to NULL, then Receive Open Ind. From there, it branches into WAIT\_FOR\_SERVICE\_PRIMITIVE (OK), Perform\_MAP\_Vr\_Dialogue (V2), and NULL (V1 Error). The main path goes through MAP\_CANCEL\_LOCATION\_ind, Cancel Location, and WAIT\_FOR\_APPLICATION\_RESPONSE to reach final NULL states via MAP\_CANCEL\_LOCATION\_Rsp.MAP\_CLOSE\_Req. or MAP\_U\_ABORT\_req. + +Figure 19.1.3/5: Process Cancel\_Location\_GLR + +Figure 19.1.3/6 shows the Process GLR\_Cancel\_Location\_VLR. This process is a GLR MAP protocol machine handling location cancellation and is an initiator to the VLR. + +Sheet 1: If the Macro Open\_Receive\_Cnf results Vr, the process requests to perform MAP Vr. It causes a request for sending an abort message to Process Cancel\_Location\_GLR. + + + +**Process GLR\_Cancel\_Location\_VLR** 19.1.3.6(1) + +``` +graph TD; Start([ ]) --> IDLE[/IDLE/]; IDLE --> CL{Cancel Location}; CL --> ROCnf{Receive Open Cnf.}; ROCnf -- OK --> WFA[/WAIT_FOR_ACK/]; ROCnf -- Vr --> PMVr[/Perform MAP_Vr/]; ROCnf -- Error --> CLNR1[/Cancel Location Negative Response/]; WFA --> MCLCnf{MAP_CANCEL_LOCATION_Cnf}; MCLCnf --> CC[Check Confirmation]; CC -- OK --> CLA[/Cancel Location Ack/]; CC -- Error --> CLNR2[/Cancel Location Negative Response/]; PMVr --> X1((X)); CLNR1 --> X2((X)); MCLCnf --> MPAINd{MAP_P_ABORT_Ind}; MPAINd --> CLNR3[/Cancel Location Negative Response/]; CLNR3 --> X3((X)); MCLCnf --> MNInd{MAP_NOTICE_Ind}; MNInd --> MCReq{MAP_CLOSE_Req}; MCReq --> CLNR4[/Cancel Location Negative Response/]; CLNR4 --> X4((X)); +``` + +Notes: + +- GLR MAP protocol machine handling cancel location and interfacing with VLR MAP protocol machine +- VLR to the Left +GLR Application to the Right + +State transition diagram for Process GLR\_Cancel\_Location\_VLR. The process starts at an initial state leading to IDLE. From IDLE, a 'Cancel Location' request is sent. The next state is a decision point for 'Receive Open Cnf.' with three possible outcomes: 'OK' leading to 'WAIT\_FOR\_ACK', 'Vr' leading to 'Perform MAP\_Vr', and 'Error' leading to 'Cancel Location Negative Response'. 'WAIT\_FOR\_ACK' leads to 'MAP\_CANCEL\_LOCATION\_Cnf', which leads to 'Check Confirmation'. 'Check Confirmation' has two outcomes: 'OK' leading to 'Cancel Location Ack', and 'Error' leading to 'Cancel Location Negative Response'. 'Perform MAP\_Vr' and 'Cancel Location Negative Response' both lead to terminal states (crossed out). 'MAP\_CANCEL\_LOCATION\_Cnf' also leads to 'MAP\_P\_ABORT\_Ind' and 'MAP\_NOTICE\_Ind'. 'MAP\_P\_ABORT\_Ind' leads to 'Cancel Location Negative Response' (terminal). 'MAP\_NOTICE\_Ind' leads to 'MAP\_CLOSE\_Req', which leads to 'Cancel Location Negative Response' (terminal). + +Figure 19.1.3/6: Process GLR\_Cancel\_Location\_VLR + +Figure 19.1.3/7 shows the Process Cancel\_GPRS\_Location\_GLR. This process is a GLR MAP protocol machine handling location cancellation and is a responder to the HLR. + + + +### Process Cancel\_GPRS\_Location\_GLR + +19.1.3.7(1) + +GLR MAP protocol machine handling Location cancellation and interfacing to HLR MAP protocol machine, handling Location Cancellation. + +Signals to/from the right are to/from the GLR Location cancellation application. + +Signals to/from the left are to/from the HLR MAP protocol machine, handling Location Cancellation. + +``` +stateDiagram-v2 + [*] --> NULL1[NULL] + NULL1 --> Receive_Open_Ind[Receive Open Ind.] + Receive_Open_Ind --> OK + Receive_Open_Ind --> V2 + Receive_Open_Ind --> V1_Error[V1 Error] + OK --> WAIT_FOR_SERVICE_PRIMITIVE + V2 --> Perform_MAP_Vr_Dialogue + V1_Error --> NULL2[NULL] + Perform_MAP_Vr_Dialogue --> NULL3[NULL] + WAIT_FOR_SERVICE_PRIMITIVE --> MAP_CANCEL_LOCATION_ind + WAIT_FOR_SERVICE_PRIMITIVE --> MAP_NOTICE_ind + MAP_CANCEL_LOCATION_ind --> Cancel_Location + MAP_NOTICE_ind --> MAP_CLOSE_req + Cancel_Location --> WAIT_FOR_APPLICATION_RESPONSE + MAP_CLOSE_req --> NULL4[NULL] + WAIT_FOR_APPLICATION_RESPONSE --> Cancel_Location_Ack + WAIT_FOR_APPLICATION_RESPONSE --> Cancel_Location_Negative_Response + WAIT_FOR_APPLICATION_RESPONSE --> Abort + Cancel_Location_Ack --> MAP_CANCEL_LOCATION_Rsp_MAP_CLOSE_Req + Cancel_Location_Negative_Response --> NULL5[NULL] + Abort --> MAP_U_ABORT_req + MAP_CANCEL_LOCATION_Rsp_MAP_CLOSE_Req --> NULL6[NULL] + MAP_U_ABORT_req --> NULL7[NULL] +``` + +State transition diagram for Process Cancel\_GPRS\_Location\_GLR. The process starts at an initial state leading to NULL, then receives an Open Indication. It then branches based on the response: OK leads to WAIT\_FOR\_SERVICE\_PRIMITIVE; V2 leads to Perform\_MAP\_Vr\_Dialogue; V1 Error leads to NULL. From WAIT\_FOR\_SERVICE\_PRIMITIVE, it branches to MAP\_CANCEL\_LOCATION\_ind (leading to Cancel Location) or MAP\_NOTICE\_ind (leading to MAP\_CLOSE\_req). Both lead to NULL. From Cancel Location, it goes to WAIT\_FOR\_APPLICATION\_RESPONSE, which then branches to Cancel Location Ack (leading to MAP\_CANCEL\_LOCATION\_Rsp. MAP\_CLOSE\_Req.) or Cancel Location Negative Response (leading to NULL). From Abort, it goes to MAP\_U\_ABORT\_req. Both lead to NULL. + +Figure 19.1.3/7: Process Cancel\_GPRS\_Location\_GLR + +Figure 19.1.3/8 shows the Process GLR\_Cancel\_Location\_SGSN. This process is a GLR MAP protocol machine handling location cancellation and is an initiator to the SGSN. + +Sheet 1: If the Macro Open\_Receive\_Cnf results Vr, the process requests to perform MAP Vr. It causes a request for sending an abort message to Process Cancel\_GPRS\_Location\_GLR. + + + +**Process GLR\_Cancel\_Location\_SGSN** 19.1.3.8(1) + +GLR MAP protocol machine handling cancel location and interfacing with SGSN MAP protocol machine + +SGSN to the Left +GLR Application to the Right + +``` + +stateDiagram-v2 + [*] --> IDLE + IDLE --> Cancel_Location : Input from Right + Cancel_Location --> Send_Reqs + state Send_Reqs <
WAIT_FOR_SUBSEQUENT_APPLICATION_RESPONSE" as WAIT_FOR_ISD_Cnf + WAIT_FOR_ISD_Cnf --> Restore_Data_Ack : Restore_Data_Ack + WAIT_FOR_ISD_Cnf --> Restore_Data_Negative_Response : Restore_Data_Negative_Response + WAIT_FOR_ISD_Cnf --> Insert_Subscriber_Data : Insert_Subscriber_Data + WAIT_FOR_ISD_Cnf --> Abort : Abort + Restore_Data_Ack --> Set_result : Set result + Restore_Data_Negative_Response --> Set_Error : Set Error + Insert_Subscriber_Data --> 1 : 1 + Abort --> MAP_U_ABORT_req : MAP_U_ABORT_req + Set_result --> MergePoint + Set_Error --> MergePoint + MergePoint --> MAP_RESTORE_DATA_Rsp_MAP_CLOSE_Req : MAP_RESTORE_DATA_Rsp.
MAP_CLOSE_Req. + MAP_RESTORE_DATA_Rsp_MAP_CLOSE_Req --> [*] : X + MAP_U_ABORT_req --> [*] : X +``` + +State transition diagram for Process RESTORE\_DATA\_GLR. The diagram shows four main paths originating from a central state labeled 'WAIT\_FOR\_ISD\_Cnf' and 'WAIT\_FOR\_SUBSEQUENT\_APPLICATION\_RESPONSE'. Path 1: 'Restore\_Data\_Ack' (glide) leads to 'Set result' (action), which then leads to a merge point for 'MAP\_RESTORE\_DATA\_Rsp.' and 'MAP\_CLOSE\_Req.' (glide), ending at a state exit (X). Path 2: 'Restore\_Data\_Negative\_Response' (glide) leads to 'Set Error' (action), which also leads to the same merge point. Path 3: 'Insert\_Subscriber\_Data' (glide) leads to a connector circle labeled '1'. Path 4: 'Abort' (glide) leads to 'MAP\_U\_ABORT\_req' (action), which ends at a state exit (X). + +Figure 19.2.2/1 (Sheet 3 of 3): Process RESTORE\_DATA\_GLR + +Figure 19.2.2/2 shows the Process GLR\_RESTORE\_DATA\_HLR. This process is a GLR MAP protocol machine handling VLR restoration and is an initiator to the HLR. + +Sheet 1: If the Macro Open\_Receive\_Cnf results Vr, the process requests to perform MAP Vr. It causes a request for sending an abort message to Process RESTORE\_DATA\_GLR. + + + +### Process GLR\_RESTORE\_DATA\_HLR 19.2.2.2\_1(3) + +GLR MAP protocol machine handling restore data and interfacing to HLR MAP protocol machine, handling restore data. + +Signals to/from the left are to/from the GLR application. +Signals to/from the right are to/from the HLR MAP protocol machine. + +``` +graph TD; Start([ ]) --> IDLE([IDLE]); IDLE --> RD[/restore data/]; RD --> Decision{ }; Decision -- "MAP_OPEN_Req +MAP_RESTORE_DATA_Req +MAP_DELIMITER_Req" --> Right1[ ]; Decision --> ROCnf[Receive Open Cnf]; ROCnf --- S251[Section 25.1]; ROCnf -- OK --> WFR[Wait_For_HLR_Response]; ROCnf -- Vr --> PMVr{Perform MAP Vr}; ROCnf -- Error --> SetError[Set error]; SetError --> RNR[/Restore data Negative Response/]; PMVr --> X1[X]; RNR --> X2[X]; +``` + +Flowchart for Process GLR\_RESTORE\_DATA\_HLR. It starts with an oval, followed by an IDLE state. A 'restore data' input leads to a decision diamond. From the diamond, three outputs go to the right: MAP\_OPEN\_Req, MAP\_RESTORE\_DATA\_Req, and MAP\_DELIMITER\_Req. The main path goes down to 'Receive Open Cnf', which is linked to 'Section 25.1'. From 'Receive Open Cnf', three paths emerge: 'OK' leads to 'Wait\_For\_HLR\_Response'; 'Vr' leads to 'Perform MAP Vr'; 'Error' leads to 'Set error' and then 'Restore data Negative Response'. Both 'Perform MAP Vr' and 'Restore data Negative Response' lead to an 'X' symbol. + +Figure 19.2.2/2 (Sheet 1 of 3): Process GLR\_RESTORE\_DATA\_HLR + + + +### Process GLR\_RESTORE\_DATA\_HLR + +19.2.2.2\_2(3) + +GLR MAP protocol machine handling restore data and interfacing to HLR MAP protocol machine, handling restore data. + +Signals to/from the left are to/from the GLR application. +Signals to/from the right are to/from the HLR MAP protocol machine. + +``` +stateDiagram-v2 + [*] --> Wait_For_HLR_Response + state "Wait_For_HLR_Response" as Wait_For_HLR_Response + state "MAP_RESTORE_DATA_cnf" as MAP_RESTORE_DATA_cnf + state "MAP_INSERT_SUBSCRIBER_DATA_ind" as MAP_INSERT_SUBSCRIBER_DATA_ind + state "MAP_Notice_Indication" as MAP_Notice_Indication + state "MAP_U_Abort_ind, MAP_P_Abort_ind, MAP_Close_ind" as MAP_U_Abort_ind, MAP_P_Abort_ind, MAP_Close_ind + + Wait_For_HLR_Response --> MAP_RESTORE_DATA_cnf + Wait_For_HLR_Response --> MAP_INSERT_SUBSCRIBER_DATA_ind + Wait_For_HLR_Response --> MAP_Notice_Indication + Wait_For_HLR_Response --> MAP_U_Abort_ind, MAP_P_Abort_ind, MAP_Close_ind + + state "Check Confirmation" as Check Confirmation + state "OK" as OK + state "Provider Error, User Error, Data Error" as Provider Error, User Error, Data Error + state "Restore data ack" as Restore data ack + state "Set negative response" as Set negative response + state "Restore data negative response" as Restore data negative response + state "Idle" as Idle + + MAP_RESTORE_DATA_cnf --> Check Confirmation + Check Confirmation --> OK + Check Confirmation --> Provider Error, User Error, Data Error + OK --> Restore data ack + Provider Error, User Error, Data Error --> Set negative response + Restore data ack --> Idle + Set negative response --> Restore data negative response + Restore data negative response --> Idle + + state "Insert Subscriber data" as Insert Subscriber data + state "Wait_For_HLR or Application_Response" as Wait_For_HLR or Application_Response + + MAP_INSERT_SUBSCRIBER_DATA_ind --> Insert Subscriber data + Insert Subscriber data --> Wait_For_HLR or Application_Response + + state "MAP_Close_request" as MAP_Close_request + state "Set negative response" as Set negative response + state "Restore data negative response" as Restore data negative response + state "Idle" as Idle + + MAP_Notice_Indication --> MAP_Close_request + MAP_Close_request --> Set negative response + Set negative response --> Restore data negative response + Restore data negative response --> Idle + + state "Abort" as Abort + state "Idle" as Idle + + MAP_U_Abort_ind, MAP_P_Abort_ind, MAP_Close_ind --> Abort + Abort --> Idle +``` + +State transition diagram for Process GLR\_RESTORE\_DATA\_HLR. The diagram shows four main paths starting from a 'Wait\_For\_HLR\_Response' state. Path 1: MAP\_RESTORE\_DATA\_cnf -> Check Confirmation (Section 25.2) -> OK leads to Restore data ack -> Idle; Provider Error, User Error, Data Error leads to Set negative response -> Restore data negative response -> Idle. Path 2: MAP\_INSERT\_SUBSCRIBER\_DATA\_ind -> Insert Subscriber data -> Wait\_For\_HLR or Application\_Response. Path 3: MAP\_Notice\_Indication -> MAP\_Close\_request -> Set negative response -> Restore data negative response -> Idle. Path 4: MAP\_U\_Abort\_ind, MAP\_P\_Abort\_ind, MAP\_Close\_ind -> Abort -> Idle. + +Figure 19.2.2/2 (Sheet 2 of 3): Process GLR\_RESTORE\_DATA\_HLR + + + +**Process GLR\_RESTORE\_DATA\_HLR** 19.2.2.2\_3(3) + +GLR MAP protocol machine handling restore data and interfacing to HLR MAP protocol machine, handling restore data. + +Signals to/from the left are to/from the GLR application. + Signals to/from the right are to/from the HLR MAP protocol machine. + +``` + +stateDiagram-v2 + [*] --> Wait_For_HLR_or_Application_Response + state "Wait_For_HLR_or_Application_Response" as Wait_For_HLR_or_Application_Response + state "MAP_RESTORE_DATA_cnf" as MAP_RESTORE_DATA_cnf + state "Check Confirmation" as Check Confirmation + state "Restore data ack" as Restore data ack + state "Set negative response" as Set negative response + state "Restore data negative response" as Restore data negative response + state "Idle" as Idle + state "MAP_INSERT_SUBSCRIBER_DATA_ind" as MAP_INSERT_SUBSCRIBER_DATA_ind + state "Insert Subscriber data" as Insert Subscriber data + state "Insert Subscriber Data ack" as Insert Subscriber Data ack + state "Insert Subscriber Data negative response" as Insert Subscriber Data negative response + state "Set user error" as Set user error + state "MAP_Insert Subscriber Data_response" as MAP_Insert Subscriber Data_response + state "Abort" as Abort + state "MAP_Notice_Indication" as MAP_Notice_Indication + state "MAP_U_Abort_ind / MAP_P_Abort_ind / MAP_Close_ind" as MAP_U_Abort_ind / MAP_P_Abort_ind / MAP_Close_ind + state "Map_U_Abort_request" as Map_U_Abort_request + state "MAP_Close_request" as MAP_Close_request + state "Set negative response" as Set negative_response + state "Update Location negative response" as Update Location negative response + + Wait_For_HLR_or_Application_Response --> MAP_RESTORE_DATA_cnf + MAP_RESTORE_DATA_cnf --> Check Confirmation + Check Confirmation --> Restore data ack : OK + Check Confirmation --> Set negative_response : Provider Error, User Error, Data Error + Restore data ack --> Idle + Set negative_response --> Restore data negative_response + Restore data negative_response --> Idle + + Wait_For_HLR_or_Application_Response --> MAP_INSERT_SUBSCRIBER_DATA_ind + MAP_INSERT_SUBSCRIBER_DATA_ind --> Insert Subscriber data + Insert Subscriber data --> Insert Subscriber Data ack + Insert Subscriber data --> Insert Subscriber Data negative_response + Insert Subscriber Data negative_response --> Set user error + Set user error --> MAP_Insert Subscriber Data_response + MAP_Insert Subscriber Data_response --> Wait_For_HLR_or_Application_Response + + Wait_For_HLR_or_Application_Response --> Abort + Wait_For_HLR_or_Application_Response --> MAP_Notice_Indication + Wait_For_HLR_or_Application_Response --> MAP_U_Abort_ind / MAP_P_Abort_ind / MAP_Close_ind + + Abort --> Map_U_Abort_request + Map_U_Abort_request --> Idle + + MAP_Notice_Indication --> MAP_Close_request + MAP_Close_request --> Set negative_response + Set negative_response --> Update Location negative_response + Update Location negative_response --> Idle + + MAP_U_Abort_ind / MAP_P_Abort_ind / MAP_Close_ind --> Abort + Abort --> Idle + +``` + +State transition diagram for Process GLR\_RESTORE\_DATA\_HLR. The diagram shows two main paths starting from 'Wait\_For\_HLR\_or\_Application\_Response'. The left path handles 'MAP\_RESTORE\_DATA\_cnf' with a 'Check Confirmation' (Section 25.2), leading to 'Restore data ack' (OK) or 'Set negative response' (Provider Error, User Error, Data Error), both ending at 'Idle'. The right path handles 'MAP\_INSERT\_SUBSCRIBER\_DATA\_ind', leading to 'Insert Subscriber data', 'Insert Subscriber Data ack', or 'Insert Subscriber Data negative response'. The negative response leads to 'Set user error' and then 'MAP\_Insert Subscriber Data\_response', which loops back to 'Wait\_For\_HLR\_or\_Application\_Response'. The 'Insert Subscriber data' path leads to another 'Wait\_For\_HLR\_or\_Application\_Response' state, which then branches into 'Abort' (leading to 'Map\_U\_Abort\_request'), 'MAP\_Notice\_Indication' (leading to 'MAP\_Close\_request' -> 'Set negative response' -> 'Update Location negative response'), or 'MAP\_U\_Abort\_ind / MAP\_P\_Abort\_ind / MAP\_Close\_ind' (leading to 'Abort'). All three branches from the second wait state lead to 'Idle'. + +Figure 19.2.2/2 (Sheet 3 of 3): Process GLR\_RESTORE\_DATA\_HLR + +# 20 Operations and maintenance procedures + +## 20.1 General + +The Operations and Maintenance procedures are needed for operating and maintaining the UMTS PLMN network. + +The following procedures exist for operation and maintenance purposes: + +- i) Tracing procedures; +- ii) Subscriber Data Management procedures; +- iii) Subscriber Identity procedures. + +The following application contexts refer to complex MAP Users consisting of several processes: + +- subscriberDataManagementContext; +- tracingContext. + +These two application contexts need a co-ordinating process in the VLR or in the SGSN. Refer to the 3GPP TS 29.002 for detail procedures. + +The Subscriber Data Management procedures are only procedures that impact to the GLR. The following subclause describes the Subscriber Identity procedures in the GLR. + +## 20.2 Subscriber data management procedures + +### 20.2.1 General + +Two types of subscriber data management procedures exist in the Mobile Application Part + +- i) Subscriber Deletion; +- ii) Subscriber Data Modification. + +No requirements have been identified for the Subscriber creation and subscriber data interrogation procedures. + +The subscriber deletion and subscriber data modification procedures are initiated by the OMC (see figures 20.2.1/1, 20.2.1/2, 20.2.1/3 and 20.2.1/4). + + + +``` +sequenceDiagram + participant VLR + participant GLR + participant HLR + participant OMC + Note over OMC,HLR: 1. Delete Subscriber + OMC->>HLR: + Note over HLR,GLR: 2. MAP_CANCEL_LOCATION + HLR->>GLR: + Note over GLR,VLR: 2. MAP_CANCEL_LOCATION + GLR->>VLR: + Note over VLR,GLR: 3. MAP_CANCEL_LOCATION_ACK + VLR-->>GLR: + Note over GLR,HLR: 3. MAP_CANCEL_LOCATION_ACK + GLR-->>HLR: + Note over HLR,OMC: 4. Subscriber Deleted + HLR-->>OMC: +``` + +- 1) Delete Subscriber. +- 2) MAP\_CANCEL\_LOCATION. +- 3) MAP\_CANCEL\_LOCATION\_ACK. +- 4) Subscriber Deleted. + +Sequence diagram of the subscriber deletion procedure showing interactions between VLR, GLR, HLR, and OMC. 1. OMC to HLR: Delete Subscriber. 2. HLR to GLR and GLR to VLR: MAP\_CANCEL\_LOCATION. 3. VLR to GLR and GLR to HLR: MAP\_CANCEL\_LOCATION\_ACK. 4. HLR to OMC: Subscriber Deleted. + +**Figure 20.2.1/1: Subscriber deletion procedure** + +In the subscriber deletion procedure the subscriber data should be removed from the VLR and from the HLR. The HLR uses the MAP\_CANCEL\_LOCATION service. + + + +``` + +sequenceDiagram + participant SGSN + participant GLR + participant HLR + participant OMC + Note right of HLR: 1. + HLR-->>OMC: + Note left of GLR: 2. + SGSN-->>GLR: + Note right of GLR: 3. + GLR-->>HLR: + Note right of OMC: 4. + OMC-->>HLR: + +``` + +Sequence diagram for Figure 20.2.1/2: Subscriber deletion procedure for GPRS. Lifelines: SGSN, GLR, HLR, OMC. The sequence is: 1. HLR sends a message to OMC; 2. SGSN sends a message to GLR; 3. GLR sends a message to HLR; 4. OMC sends a message to HLR. + +- 1) Delete GPRS Subscriber. +- 2) MAP\_CANCEL\_LOCATION. +- 3) MAP\_CANCEL\_LOCATION\_ACK. +- 4) GPRS Subscriber Deleted. + +**Figure 20.2.1/2: Subscriber deletion procedure for GPRS** + +In the subscriber deletion procedure the subscriber data should be removed from the SGSN and from the HLR. The HLR uses the MAP\_CANCEL\_LOCATION service. + + + +``` + +sequenceDiagram + participant VLR + participant GLR + participant HLR + participant OMC + Note right of HLR: 1. + HLR-->>OMC: + Note left of GLR: 2. + VLR-->>GLR: + Note right of GLR: 3. + GLR-->>HLR: + Note right of OMC: 4. + OMC-->>HLR: + +``` + +Sequence diagram for Figure 20.2.1/3: Subscriber data modification procedure. Lifelines: VLR, GLR, HLR, OMC. The sequence is: 1. HLR sends a message to OMC; 2. VLR sends a message to GLR; 3. GLR sends a message to HLR; 4. OMC sends a message to HLR. + +- 1) Modify Subscriber Data. +- 2) MAP\_CANCEL\_LOCATION, MAP\_INSERT\_SUBSCRIBER\_DATA or +MAP\_DELETE\_SUBSCRIBER\_DATA. +- 3) MAP\_CANCEL\_LOCATION\_ACK, MAP\_INSERT\_SUBSCRIBER\_DATA\_ACK or +MAP\_DELETE\_SUBSCRIBER\_DATA\_ACK. +- 4) Subscriber Data Modified. + +**Figure 20.2.1/3: Subscriber data modification procedure** + + + +``` + +sequenceDiagram + participant SGSN + participant GLR + participant HLR + participant OMC + Note right of HLR: 1. + HLR-->>OMC: + Note left of GLR: 2. + SGSN-->>GLR: + Note right of GLR: 3. + GLR-->>HLR: + Note right of OMC: 4. + OMC-->>HLR: + +``` + +Sequence diagram for Figure 20.2.1/4: Subscriber data modification procedure for GPRS. Lifelines: SGSN, GLR, HLR, OMC. The sequence is: 1. HLR sends a message to OMC; 2. SGSN sends a message to GLR; 3. GLR sends a message to HLR; 4. OMC sends a message to HLR. + +- 1) Modify Subscriber Data. +- 2) MAP\_CANCEL\_LOCATION, MAP\_INSERT\_SUBSCRIBER\_DATA or +MAP\_DELETE\_SUBSCRIBER\_DATA. +- 3) MAP\_CANCEL\_LOCATION\_ACK, MAP\_INSERT\_SUBSCRIBER\_DATA\_ACK or +MAP\_DELETE\_SUBSCRIBER\_DATA\_ACK. +- 4) Subscriber Data Modified. + +**Figure 20.2.1/4: Subscriber data modification procedure for GPRS** + +In the subscriber data modification procedure the subscriber data is modified in the HLR and when necessary also in the VLR or in the SGSN. The HLR initiates either the MAP\_INSERT\_SUBSCRIBER\_DATA, MAP\_DELETE\_SUBSCRIBER\_DATA or MAP\_CANCEL\_LOCATION service depending on the modified data. + +### 20.2.2 Procedures in the GLR + +#### 20.2.2.1 Subscriber deletion procedure + +The subscriber deletion procedure in the GLR is described in the subclause 19. + +#### 20.2.2.2 Subscriber data modification procedure + +When receiving either the MAP\_INSERT\_SUBSCRIBER\_DATA indication or the MAP\_DELETE\_SUBSCRIBER\_DATA indication, the GLR checks the parameters and data in the primitive. Data errors are reported as an unexpected data value error or a data missing error depending on the nature of the error. + +After receiving the first MAP\_INSERT\_SUBSCRIBER\_DATA indication, the GLR will check the IMSI that is included in the primitive. If the IMSI is unknown, the error "Unidentified subscriber" is returned. + +If the GLR does not support received basic or supplementary services or the network feature Operator Determined Barring, or there is a problem with Regional Subscription Data then this is reported to the HLR. + +If the entire MSC area that covered the VLR wherein the subscriber is registered is restricted due to regional subscription, this is reported to the HLR. + +If the updating of the subscriber data is not possible, the GLR will initiate the MAP\_U\_ABORT request primitive. + +If the updating is successful in the GLR, the GLR will initiate the MAP\_INSERT\_SUBSCRIBER\_DATA request or the MAP\_DELETE\_SUBSCRIBER\_DATA request to the VLR or to the SGSN wherein the subscriber is registered. + +The subscriber data modification procedure in the GLR is shown in the figures 20.2.2.2/1, 20.2.2.2/2, 20.2.2.2/3, 20.2.2.2/4, 20.2.2.2/5 and 20.2.2.2/6. + + + +### Process INS\_SUBS\_DATA\_GLR + +20.2.2.2.1\_1(3) + +Figure 20.2.2.2/1: The insert subscriber data process in the GLR + +Arrows to left are to VLR +Arrows to right are to HLR + +``` +graph TD; NULL1(NULL) --> Receive[Receive Open Ind]; Receive -- OK --> Wait[Wait_For_indication]; Receive -- "'V' 'Error'" --> NULL2(NULL); Wait --> MAP_INSERT[MAP_INSERT_SUBSCRIBER_DATA_ind]; Wait --> MAP_NOTICE[MAP_NOTICE_ind]; Wait --> MAP_ABORT[MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind]; MAP_NOTICE --> MAP_CLOSE_req[MAP_CLOSE_req]; MAP_INSERT --> Check[Check_Indication]; MAP_CLOSE_req --> X1((X)); Check -- Ok --> ParamOK{Parameter OK}; ParamOK -- Error --> SetUE1[Set UE= Unexpected Data value]; ParamOK -- No --> SetUE1; ParamOK -- Yes --> IMSIKnown{IMSI Known}; IMSIKnown -- No --> SetUE2[Set UE= Unidentified Subscriber]; IMSIKnown -- Yes --> 1((1)); SetUE1 --> Response[MAP_INSERT_SUBSCRIBER_DATA_rsp, MAP_CLOSE_Req]; SetUE2 --> Response; Response --> X2((X)); +``` + +Flowchart for Process INS\_SUBS\_DATA\_GLR. It starts with NULL, receives an Open Indication, and then branches based on OK status. The main path involves waiting for indications (MAP\_INSERT\_SUBSCRIBER\_DATA\_ind, MAP\_NOTICE\_ind, MAP\_CLOSE\_req), checking parameters, and then checking if the IMSI is known. Depending on these checks, it either proceeds to the next step (1), sets the UE as unidentified, or sets an unexpected data value, both leading to a response message. + +Figure 20.2.2.2/1 (Sheet 1 of 3): Process INS\_SUBS\_DATA\_GLR + + + +### Process INS\_SUBS\_DATA\_GLR + +20.2.2.2.1\_2(3) + +Figure 20.2.2.2/1: The insert subscriber data process in the GLR + +Arrows to left are to VLR +Arrows to right are to HLR + +``` +graph TD + 1((1)) --> D{MAP_OPEN_Req +MAP_INSERT_SUBSCRIBER_DATA_Req +MAP_DELIMITER} + D --> R[Receive Open Cnf] + R -- OK --> W((WF PRIMITIVE_OR_CLOSE)) + R -- Vr, Error --> UA1{MAP U ABORT_req} + UA1 --> X1((X)) + W --> MC1{MAP_CLOSE_ind.} + W --> MN1{MAP_NOTICE_ind} + W --> MU1{MAP_U_ABORT_ind. +MAP_P_ABORT_ind} + MC1 --> MCReq1{MAP_CLOSE_req} + MCReq1 --> X2((X)) + MN1 --> MCReq2{MAP_CLOSE_req} + MCReq2 --> MUInd1{MAP_U_ABORT_ind} + MUInd1 --> SNC1[Set Not Confirmed by HLR] + SNC1 --> X3((X)) + MU1 --> MUInd2{MAP_U_ABORT_ind} + MUInd2 --> SNC2[Set Not Confirmed by HLR] + SNC2 --> MUReq1{MAP U ABORT req} + MUReq1 --> X4((X)) + W --> MC2{MAP_CLOSE_ind.} + W --> MN2{MAP_NOTICE_ind} + W --> MU2{MAP_U_ABORT_ind. +MAP_P_ABORT_ind} + MC2 --> MCReq3{MAP_CLOSE_req} + MCReq3 --> X5((X)) + MN2 --> MCReq4{MAP_CLOSE_req} + MCReq4 --> SNC3[Set Not Confirmed by HLR] + SNC3 --> MUReq2{MAP U ABORT req} + MUReq2 --> X6((X)) + MU2 --> SNC4[Set Not Confirmed by HLR] + SNC4 --> MUReq3{MAP U ABORT req} + MUReq3 --> X7((X)) +``` + +Flowchart of Process INS\_SUBS\_DATA\_GLR. It starts with a connector '1', followed by a decision diamond with MAP\_OPEN\_Req, MAP\_INSERT\_SUBSCRIBER\_DATA\_Req, and MAP\_DELIMITER. A 'Receive Open Cnf' block follows. From there, an 'OK' path leads to a 'WF PRIMITIVE\_OR\_CLOSE' block, while a 'Vr, Error' path leads to a 'MAP U ABORT\_req' block which ends in a cross. The 'WF PRIMITIVE\_OR\_CLOSE' block branches into three parallel paths. The first path has 'MAP\_CLOSE\_ind.' leading to 'MAP\_CLOSE\_req' (crossed out). The second path has 'MAP\_NOTICE\_ind' leading to 'MAP\_CLOSE\_req' leading to 'MAP\_U\_ABORT\_ind' leading to 'Set Not Confirmed by HLR' (crossed out). The third path has 'MAP\_U\_ABORT\_ind. MAP\_P\_ABORT\_ind' leading to 'MAP\_U\_ABORT\_ind' leading to 'Set Not Confirmed by HLR' leading to 'MAP U ABORT req' (crossed out). A second parallel set of paths follows, starting with 'MAP\_CLOSE\_ind.' leading to 'MAP\_CLOSE\_req' (crossed out). The next path has 'MAP\_NOTICE\_ind' leading to 'MAP\_CLOSE\_req' leading to 'Set Not Confirmed by HLR' leading to 'MAP U ABORT req' (crossed out). The final path has 'MAP\_U\_ABORT\_ind. MAP\_P\_ABORT\_ind' leading to 'Set Not Confirmed by HLR' leading to 'MAP U ABORT req' (crossed out). + +Figure 20.2.2.2/1 (Sheet 2 of 3): Process INS\_SUBS\_DATA\_GLR + + + +**Process INS\_SUBS\_DATA\_GLR** 20.2.2.2.1\_3(3) + +Figure 20.2.2.2/1: The insert subscriber data process in the GLR + +Arrows to left are to VLR +Arrows to right are to HLR + +``` + +graph TD + Start((WF PRIMITIVE_OR_CLOSE)) --> Ind{MAP_INSERT_SUBSCRIBER_DATA_ind} + Ind --> Params{Parameters OK} + Params -- Yes --> Req1[MAP_INSERT_SUBSCRIBER_DATA_req +MAP_DELIMITER_req] + Req1 --> Rsp1[MAP_INSERT_SUBSCRIBER_DATA_rsp +MAP_DELIMITER_req] + Rsp1 --> End((WF PRIMITIVE_OR_CLOSE)) + Params -- No --> UE[Set UE= Unexpected Data Value] + UE --> CNF{MAP_INSERT_SUBSCRIBER_DATA_cnf} + CNF --> Check[Check Confirmation] + Check -- OK --> Service{Service unsupported in VLR?} + Service -- Yes --> Action1[GLR internal action] + Service -- No --> Roaming{Roaming restriction due to unsupported feature or MSC are restricted received} + Roaming -- Yes --> Action2[GLR internal action] + Roaming -- No --> Req2[MAP_INSERT_SUBSCRIBER_DATA_rsp +MAP_DELIMITER_req] + Req2 --> Save[Save subscriber data] + Save --> End + Check -- "User error, Data error" --> Abort1{MAP_U_ABORT_req} + Abort1 --> HLR + Check -- "Provider error" --> Abort2{MAP_U_ABORT_req} + Abort2 --> HLR + +``` + +Flowchart of Process INS\_SUBS\_DATA\_GLR. The process starts with a 'WF PRIMITIVE\_OR\_CLOSE' primitive, followed by 'MAP\_INSERT\_SUBSCRIBER\_DATA\_ind'. A decision 'Parameters OK' follows. If 'Yes', it sends 'MAP\_INSERT\_SUBSCRIBER\_DATA\_req' and 'MAP\_DELIMITER\_req' to the VLR, then receives 'MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp' and 'MAP\_DELIMITER\_req' from the VLR, and finally calls 'WF PRIMITIVE\_OR\_CLOSE'. If 'No', it sends 'Set UE= Unexpected Data Value' to the HLR. The process then receives 'MAP\_INSERT\_SUBSCRIBER\_DATA\_cnf' from the HLR and performs 'Check Confirmation'. If 'OK', it checks 'Service unsupported in VLR?'. If 'Yes', it performs 'GLR internal action'. If 'No', it checks 'Roaming restriction due to unsupported feature or MSC are restricted received'. If 'Yes', it performs 'GLR internal action'. If 'No', it sends 'MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp' and 'MAP\_DELIMITER\_req' to the VLR, saves subscriber data, and calls 'WF PRIMITIVE\_OR\_CLOSE'. If 'User error, Data error' or 'Provider error' occurs during 'Check Confirmation', it sends 'MAP\_U\_ABORT\_req' to the HLR. + +Figure 20.2.2.2/1 (Sheet 3 of 3): Process INS\_SUBS\_DATA\_GLR + + + +### Process INS\_GPRS\_SUBS\_DATA\_GLR + +20.2.2.2.2\_1(3) + +Figure 20.2.2.2/2: The insert subscriber data +process in the GLR + +Arrows to left are to SGSN +Arrows to right are to HLR + +``` + +graph TD + Start([NULL]) --> RecvInd[Receive +Open Ind] + RecvInd -- OK --> WaitInd[Wait_For_ +indication] + RecvInd -- "'Vr' 'Error'" --> NullEnd([NULL]) + + WaitInd --> MapInsInd[/MAP_INSET_ +SUBSCRIBER_ +DATA ind/] + WaitInd --> MapNotInd[/MAP_ +NOTICE_ind/] + WaitInd --> MapAbortInd[/MAP_U_ABORT_ind. +MAP_P_ABORT_ind +MAP_CLOSE_ind/] + WaitInd --> CheckInd[Check_ +Indication] + + MapNotInd --> MapCloseReq[\MAP_CLOSE_ +req\] + MapCloseReq --> Term1((X)) + + CheckInd -- OK --> ParamOK{Parameter OK} + ParamOK -- Yes --> IMSIKnown{IMSI Known} + ParamOK -- Error --> SetUEUnexpected[Set UE= +Unexpected +Data value] + ParamOK -- No --> SetUEUnexpected + + IMSIKnown -- Yes --> Conn1((1)) + IMSIKnown -- No --> SetUEUnidentified[Set UE= +Unidentified +Subscriber] + + SetUEUnidentified --> MapResp[\MAP_INSERT_SUBSCRIBER_DATA_rsp +MAP_CLOSE_req\] + SetUEUnexpected --> MapResp + MapResp --> Term2((X)) + +``` + +SDL Flowchart for Process INS\_GPRS\_SUBS\_DATA\_GLR. The process starts at a NULL state, receives an Open Indication, and transitions through various states like Wait\_For\_indication. It handles MAP messages (INSERT\_SUBSCRIBER\_DATA, NOTICE, ABORT, CLOSE) and includes decision points for Parameter OK and IMSI Known. Error paths lead to setting UE status to Unidentified Subscriber or Unexpected Data value before closing the MAP connection. + +Figure 20.2.2.2/2 (Sheet 1 of 3): Process INS\_GPRS\_SUBS\_DATA\_GLR + + + +### Process INS\_GPRS\_SUBS\_DATA\_GLR + +20.2.2.2.2\_2(3) + +Figure 20.2.2.2/2: The insert subscriber data process in the GLR + +Arrows to left are to SGSN +Arrows to right are to HLR + +``` +sequenceDiagram + participant GLR + participant HLR + Note left of GLR: 1 + GLR->>HLR: MAP_OPEN_Req, MAP_INSERT_SUBSCRIBER_DATA_Req, MAP_DELIMITER + HLR-->>GLR: Recieve Open conf + Note right of GLR: OK + Note right of GLR: Vr, Error + GLR->>HLR: WF PRIMITIVE_OR_CLOSE + Note left of GLR: MAP_CLOSE_ind. + Note left of GLR: MAP_NOTICE + Note left of GLR: MAP_U_ABORT_ind., MAP_P_ABORT_ind. + Note right of GLR: MAP_CLOSE_ind. + Note right of GLR: MAP_NOTICE ind. + Note right of GLR: MAP_U_ABORT_ind., MAP_P_ABORT_ind. + Note left of GLR: MAP_CLOSE_req. + Note left of GLR: MAP_CLOSE_req. + Note left of GLR: MAP_U_ABORT_ind. + Note right of GLR: MAP_CLOSE_req. + Note right of GLR: MAP_CLOSE_req. + Note right of GLR: MAP_U_ABORT_ind. + Note left of GLR: Set Not Confirmed by HLR + Note right of GLR: Set Not Confirmed by HLR + Note right of GLR: MAP_U_ABORT_req. + Note left of GLR: X + Note left of GLR: X + Note left of GLR: X + Note right of GLR: X + Note right of GLR: X + Note right of GLR: X +``` + +Sequence diagram for Process INS\_GPRS\_SUBS\_DATA\_GLR. The diagram shows the interaction between a GLR and an HLR. It starts with a circle labeled '1'. The GLR sends MAP\_OPEN\_Req, MAP\_INSERT\_SUBSCRIBER\_DATA\_Req, and MAP\_DELIMITER to the HLR. The HLR responds with 'Recieve Open conf'. From this point, two paths emerge: 'OK' and 'Vr, Error'. The 'OK' path leads to a 'WF PRIMITIVE\_OR\_CLOSE' block, which then branches into three parallel paths: 1) MAP\_CLOSE\_ind. to SGSN, followed by MAP\_CLOSE\_req. to HLR, ending with an 'X'. 2) MAP\_NOTICE to SGSN, followed by MAP\_CLOSE\_req. to HLR, then MAP\_U\_ABORT\_ind. to SGSN, then 'Set Not Confirmed by HLR', ending with an 'X'. 3) MAP\_U\_ABORT\_ind. and MAP\_P\_ABORT\_ind. to SGSN, followed by MAP\_U\_ABORT\_ind. to HLR, then 'Set Not Confirmed by HLR', ending with an 'X'. The 'Vr, Error' path from 'Recieve Open conf' leads to MAP\_U\_ABORT\_req. to HLR, ending with an 'X'. The 'WF PRIMITIVE\_OR\_CLOSE' block also has a rightward branch leading to another set of three parallel paths: 1) MAP\_CLOSE\_ind. to SGSN, followed by MAP\_CLOSE\_req. to HLR, ending with an 'X'. 2) MAP\_NOTICE ind. to SGSN, followed by MAP\_CLOSE\_req. to HLR, then MAP\_U\_ABORT\_ind. to SGSN, then 'Set Not Confirmed by HLR', ending with an 'X'. 3) MAP\_U\_ABORT\_ind. and MAP\_P\_ABORT\_ind. to SGSN, followed by 'Set Not Confirmed by HLR', then MAP\_U\_ABORT\_req. to HLR, ending with an 'X'. + +Figure 20.2.2.2/2 (Sheet 2 of 3): Process INS\_GPRS\_SUBS\_DATA\_GLR + + + +**Process INS\_GPRS\_SUBS\_DATA\_GLR** 20.2.2.2.2\_3(3) + +Figure 20.2.2.2/2: The insert subscriber data process in the GLR + +Arrows to left are to SGSN +Arrows to right are to HLR + +``` + +graph TD + Start((WF PRIMITIVE_OR_CLOSE)) --> Ind{MAP_INSERT_SUBSCRIBER_DATA_ind} + Ind --> Params{Parameters OK} + Params -- No --> SetUE[Set UE= Unexpected Data Value] + Params -- Yes --> Req1[MAP_INSERT_SUBSCRIBER_DATA_req +MAP_DELIMITER_req] + SetUE --> Conn1{ } + Req1 --> Conn2{ } + Conn1 --> Roaming{Roaming_restriction_due_to_unsupported_feature_or_MSC_are_restricted_received} + Conn2 --> Roaming + Roaming -- Yes --> GLR1[GLR internal action] + Roaming -- No --> Conn3{ } + Conn3 --> Rsp1[MAP_INSERTt_SUBSCRIBER_DATA_rsp +MAP_DELIMITER_req] + Rsp1 --> Save[Save subscriber data] + Save --> Cnf{MAP_INSERT_SUBSCRIBER_DATA_cnf} + Cnf --> Check[Check Confirmation] + Check -- OK --> Service{Service unsupported in VLR?} + Service -- Yes --> GLR2[GLR internal action] + Service -- No --> Conn3 + Check -- "User error, Data error" --> Abort1{MAP_U_ABORT_req} + Check -- "Provider error" --> Abort2{MAP_U_ABORT_req} + Abort1 --> X1((X)) + Abort2 --> X2((X)) + Conn3 --> End((WF PRIMITIVE_OR_CLOSE)) + +``` + +Flowchart of Process INS\_GPRS\_SUBS\_DATA\_GLR. The process starts with a 'WF PRIMITIVE\_OR\_CLOSE' connector, leading to 'MAP\_INSERT\_SUBSCRIBER\_DATA\_ind'. A decision 'Parameters OK' follows. If 'No', it goes to 'Set UE= Unexpected Data Value' and then to an unlabeled connector. If 'Yes', it goes to 'MAP\_INSERT\_SUBSCRIBER\_DATA\_req' (with 'MAP\_DELIMITER\_req'), then to another unlabeled connector, then to 'MAP\_INSERT\_SUBSCRIBER\_DATA\_rsp' (with 'MAP\_DELIMITER\_req'). Both unlabeled connectors lead to a 'Roaming\_restriction\_due\_to\_unsupported\_feature\_or\_MSC\_are\_restricted\_received' decision. If 'Yes', it goes to 'GLR internal action'. If 'No', it goes to an unlabeled connector, then to 'MAP\_INSERTt\_SUBSCRIBER\_DATA\_rsp' (with 'MAP\_DELIMITER\_req'), then to 'Save subscriber data'. From 'Save subscriber data', the flow goes to 'MAP\_INSERT\_SUBSCRIBER\_DATA\_cnf', then to 'Check Confirmation'. From 'Check Confirmation', 'OK' leads to a 'Service unsupported in VLR?' decision. If 'Yes', it goes to 'GLR internal action'. If 'No', it leads to the unlabeled connector before 'Roaming\_restriction...'. From 'Service unsupported in VLR?', 'User error, Data error' leads to 'MAP\_U\_ABORT\_req' (to SGSN) and 'Provider error' leads to 'MAP\_U\_ABORT\_req' (to HLR). Both 'MAP\_U\_ABORT\_req' paths end at an 'X' symbol. The process ends at a 'WF PRIMITIVE\_OR\_CLOSE' connector. + +Figure 20.2.2.2/2 (Sheet 3 of 3): Process INS\_GPRS\_SUBS\_DATA\_GLR + + + +### Process Delete\_Subscriber\_Data\_GLR + +20.2.2.2.3(1) + +Figure 20.2.2.2/3: The delete subscriber data process in the GLR + +Arrows to left are to VLR +Arrows to right are to HLR + +``` +graph TD; NULL1(NULL) --> Rec[Receive Open Ind]; Rec -- OK --> Wait[Wait_For indication]; Rec -- "'Vr' 'Error'" --> NULL2(NULL); Wait --> MAP_DEL[MAP_DELETE_SUBSCRIBER_DATA ind]; MAP_DEL --> Check[Check Indication]; Check --> Know{Subscriber Know}; Know -- No --> SetUE[Set UE= Unidentified Subscriber]; Know -- Yes --> Services{Services registered in a GLR}; Services -- No --> SetNotConf[Set Not Confirmed by HLR]; Services -- Yes --> Delete[Delete Subs Data GLR]; Delete -- "Figure 20.2.2.2/5" --> DeleteSub[Delete Subscriber Data in the GLR]; DeleteSub -- OK --> NULL3(NULL); DeleteSub -- Error --> NULL4(NULL); SetUE --> Join(( )); SetNotConf --> Join; Join --> MAP_RSP[MAP_DELETE_SUBSCRIBER_DATA_rsp MAP_CLOSE_req]; MAP_RSP --> NULL5(NULL); +``` + +Flowchart for Process Delete\_Subscriber\_Data\_GLR. The process starts with NULL, receives an Open Indication, and checks if the subscriber is known. If not known, it sets the UE as an unidentified subscriber. If known, it checks if services are registered in a GLR. If not registered, it sets the subscriber as not confirmed by the HLR. If registered, it proceeds to delete subscriber data. The process ends with a response message to the HLR or NULL. + +Figure 20.2.2.2/3: Process Delete\_Subscriber\_Data\_GLR + + + +### Process Delete\_GPRS\_Subscriber\_Data\_GLR + +20.2.2.2.4(1) + +Figure 20.2.2.2/4: The delete subscriber data process in the GLR + +Arrows to left are to SGSN +Arrows to right are to HLR + +``` +graph TD; NULL1([NULL]) --> RecInd[Receive Open Ind]; RecInd -- OK --> WaitFor[Wait_For indication]; RecInd -- "'Vr' 'Error'" --> NULL2([NULL]); WaitFor --> MAPDel[MAP_DELETE_SUBSCRIBER_DATA ind]; MAPDel --> CheckInd[Check Indication]; CheckInd --> SubKnow{Subscriber Know}; SubKnow -- Yes --> ServicesReg{Services registered in a GLR}; SubKnow -- No --> SetUE[Set UE= Unidentified Subscriber]; SubKnow -- Error --> SetNotConf[Set Not Confirmed by HLR]; ServicesReg -- Yes --> DeleteData[Delete GPRS Subs Data GLR]; ServicesReg -- No --> Join1(( )); SetUE --> Join1; SetNotConf --> Join1; DeleteData -- "OK" --> DeleteSubData[Delete Subscriber Data in the GLR]; DeleteData -- Error --> Join2(( )); DeleteSubData --> Join2; Join1 --> MAPRsp[MAP_DELETE_SUBSCRIBER_DATA_rsp MAP_CLOSE_req]; Join2 --> MAPRsp; MAPRsp --> Join3(( )); Join3 --> End1(( )); Join3 --> End2(( )); Join3 --> End3(( )); +``` + +Flowchart for Process Delete\_GPRS\_Subscriber\_Data\_GLR. The process starts with NULL, receives an Open Indication, and checks if the subscriber is known. If not known, it sets the UE as an unidentified subscriber. If known, it checks if services are registered in a GLR. If not registered, it sets the subscriber as not confirmed by HLR. If registered, it deletes GPRS subscriber data and sends a response. Arrows pointing left are to SGSN, and arrows pointing right are to HLR. + +Figure 20.2.2.2/4: Process Delete\_GPRS\_Subscriber\_Data\_GLR + + + +### Macrodefinition Delete\_Subs\_Data\_GLR 20.2.2.2.5(1) + +Figure 20.2.2.2/5: The delete subscriber data macro in the GLR + +Arrows to left are to VLR +Arrows to right are to HLR + +``` +graph TD + Start([ ]) --> Init["MAP_OPEN_req +MAP_DELETE_SUBSCRIBER_DATA_req +MAP_DELIMITER"] + Init --> RecvOpen["Receive Open cnf"] + RecvOpen -- Ok --> WaitForConfirm{Wait_For_Confirm} + WaitForConfirm --> Branch1[ ] + subgraph Branch1 + direction TB + B1[MAP_CLOSE_ind.] + B2[MAP_NOTICE_ind] + B3[MAP_U_ABORT_ind +MAP_P_ABORT_ind] + B4[MAP_DELETE_SUBSCRIBER_DATA.cnf] + B5[MAP_NOTICE_ind] + B6[MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind] + end + B1 --> MAP_CLOSE_req1[MAP_CLOSE_req] + MAP_CLOSE_req1 --> MAP_CLOSE Req[MAP_CLOSE Req] + MAP_CLOSE Req --> Error1((Error)) + B2 --> MAP_CLOSE_req2[MAP_CLOSE_req] + MAP_CLOSE_req2 --> MAP_U_ABORT_ind2[MAP_U_ABORT_ind] + MAP_U_ABORT_ind2 --> Error2((Error)) + B3 --> Error3((Error)) + B4 --> Decision1{MSC_Area_Restricted_received or "Roaming_Restricted_Due_To_Unsupported_Feature"} + Decision1 -- Yes --> MAP_U_ABORT req[MAP_U_ABORT req] + MAP_U_ABORT req --> Error4((Error)) + Decision1 -- No --> Decision2{MSC_Area_Restricted_Flag} + Decision2 -- "not Restricted" --> MAP_DELETE_SUBSCRIBER_DATA_Cnf1[MAP_DELETE_SUBSCRIBER_DATA_Cnf] + MAP_DELETE_SUBSCRIBER_DATA_Cnf1 --> Error5((Error)) + Decision2 -- "Restricted" --> MAP_DELETE_SUBSCRIBER_DATA_Cnf2[MAP_DELETE_SUBSCRIBER_DATA_Cnf] + MAP_DELETE_SUBSCRIBER_DATA_Cnf2 --> OK((OK)) + B5 --> MAP_CLOSE_req3[MAP_CLOSE_req] + MAP_CLOSE_req3 --> WaitForConfirm + B6 --> VrError[Vr,Error] +``` + +Flowchart for Macro Delete\_Subs\_Data\_GLR. The process starts with an entry point, followed by sending MAP\_OPEN\_req, MAP\_DELETE\_SUBSCRIBER\_DATA\_req, and MAP\_DELIMITER. It then receives an 'Open cnf' and enters a 'Wait\_For\_Confirm' state. From there, it branches based on received indications: MAP\_CLOSE\_ind., MAP\_NOTICE\_ind, MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_DELETE\_SUBSCRIBER\_DATA.cnf, and another MAP\_NOTICE\_ind. The first three lead to MAP\_CLOSE\_req and then either MAP\_CLOSE Req or MAP\_U\_ABORT\_ind, both ending in Error. The fourth leads to an Error state. The fifth leads to a decision diamond 'MSC\_Area\_Restricted\_received or Roaming\_Restricted\_Due\_To\_Unsupported\_Feature'. If 'Yes', it sends MAP\_U\_ABORT req and ends in Error. If 'No', it checks 'MSC\_Area\_Restricted\_Flag'. If 'not Restricted', it sends MAP\_DELETE\_SUBSCRIBER\_DATA\_Cnf and ends in Error. If 'Restricted', it sends MAP\_DELETE\_SUBSCRIBER\_DATA\_Cnf and ends in OK. The sixth indication leads to MAP\_CLOSE\_req and then to the right side of the Wait\_For\_Confirm loop. The seventh leads to the right side of the Wait\_For\_Confirm loop and ends in Vr,Error. + +Figure 20.2.2.2/5: Macro Delete\_Subs\_Data\_GLR + + + +**Macrodefinition Delete\_GPRS\_Subs\_Data\_GLR** 20.2.2.2.6(1) + +Figure 20.2.2.2/6: The delete subscriber data macro in the GLR + +Arrows to left are to SGSN + Arrows to right are to HLR + + + +``` + + graph TD + Start([ ]) --> Out1[/ /] + Out1 --> Req1[MAP_OPEN_req +MAP_DELETE_SUBSCRIBER_DATA_req +MAP_DELIMITER] + Req1 --> In1[/Receive +Open Cnf/] + In1 -- Ok --> Wait[Wait_For_ +Confirm] + + Wait --> Ind1{MAP_CLOSE_ +ind.} + Wait --> Ind2{MAP_NOTICE +ind} + Wait --> Ind3{MAP_U_ABORT_ind +MAP_P_ABORT_ind} + Wait --> Ind4{MAP_DELETE_ +SUBSCRIBER_ +DATA Cnf} + Wait --> Ind5{MAP_NOTICE +ind} + Wait --> Ind6{MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind} + Wait -- Vr,Error --> Exit1(( )) + + Ind1 --> CloseReq1[MAP_CLOSE_ +Req] + CloseReq1 --> Error1((Error)) + + Ind2 --> CloseReq2[MAP_CLOSE_req] + CloseReq2 --> UAbortInd[MAP_U_ABORT_ind.] + UAbortInd --> Error2((Error)) + + Ind3 --> Error2 + + Ind4 --> ErrorDec{Error} + ErrorDec -- Yes --> Error2 + ErrorDec -- No --> AreaDec{SGSN_Area_Restricted_received or +"Roaming_Restricted_Due_ +To_Unsupported_Feature"} + + AreaDec -- Yes --> AreaRestricted[SGSN_Area_ +Restricted_Flag +=Restricted] + AreaDec -- No --> AreaNotRestricted[SGSN_Area_ +Restricted_Flag +not Restricted] + + AreaRestricted --> DelCnf1[MAP_DELETE_ +SUBSCRIBER_ +DATA_Cnf] + AreaNotRestricted --> DelCnf2[MAP_DELETE_ +SUBSCRIBER_ +DATA_Cnf] + + DelCnf1 --> Error3((Error)) + DelCnf2 --> OK1((OK)) + + Ind5 --> CloseReq3[MAP_CLOSE_ +req] + CloseReq3 --> Exit1 + + Ind6 --> UAbortReq[MAP U ABORT req] + UAbortReq --> Error4((Error)) + +``` + +SDL Diagram for Macro Delete\_GPRS\_Subs\_Data\_GLR showing the flow from initiation, sending requests to HLR, waiting for confirmation, handling various MAP indications, and reaching either an OK or Error state based on decision logic regarding SGSN Area Restricted flags. + +Figure 20.2.2.2/6: Macro Delete\_GPRS\_Subs\_Data\_GLR + +## 20.3 Subscriber Identity procedure + +In the subscriber identity procedure the IMSI of the subscriber is retrieved from the HLR. The procedure is shown in figure 20.3/1. + + + +``` +sequenceDiagram + participant OMC + participant VLR + participant GLR + participant HLR + Note left of OMC: 1) Identity request. + OMC->>VLR: 1. + Note right of VLR: 2) MAP_SEND_IMSI. + VLR->>GLR: 2. + VLR->>HLR: 2. + Note right of GLR: 3) MAP_SEND_IMSI_ACK. + GLR->>VLR: 3. + HLR->>VLR: 3. + Note left of VLR: 4) Identity confirm. + VLR->>OMC: 4. +``` + +Sequence diagram showing the subscriber identity procedure between OMC, VLR, GLR, and HLR. The sequence is: 1) Identity request from OMC to VLR; 2) MAP\_SEND\_IMSI from VLR to GLR and HLR; 3) MAP\_SEND\_IMSI\_ACK from GLR and HLR to VLR; 4) Identity confirm from VLR to OMC. + +- 1) Identity request. +- 2) MAP\_SEND\_IMSI. +- 3) MAP\_SEND\_IMSI\_ACK. +- 4) Identity confirm. + +**Figure 20.3/1: The subscriber identity procedure** + +### 20.3.1 Subscriber identity procedure in the GLR + +The subscriber identity procedure in the GLR is shown in figure 20.3/2. + + + +### Process Send\_IMSI\_GLR + +20.3.2\_1(2) + +Figure 20.3/2: The send IMSI process in the GLR + +Arrows to left are to VLR +Arrows to right are to HLR + +``` +graph TD; Idle1([Idle]) --> RecOpen[Receive Open_ind]; RecOpen --> WaitForResponse([Wait For Response]); WaitForResponse --> MAP_NOTICE_ind{MAP_NOTICE_ind}; WaitForResponse --> MAP_SEND_IMSI_ind{MAP_SEND_IMSI_ind}; WaitForResponse --> Vr[Perform Vr Dialogue]; WaitForResponse --> Error1[Error]; MAP_NOTICE_ind --> MAP_CLOSE_req{MAP_CLOSE_req}; MAP_CLOSE_req --> Idle2([Idle]); MAP_SEND_IMSI_ind --> CheckIndication[Check Indication]; CheckIndication --> SubKnown{OK Subscriber Known}; SubKnown -- Yes --> MAP_OPEN_req[MAP_OPEN_req +MAP_SEND_IMSI_req +MAP_SWLIMITER_req]; SubKnown -- No --> SetUE[Set UE= Unknown Subscriber]; SetUE --> MAP_SEND_IMSI_rsp[MAP_SEND_IMSI_rsp +MAP_CLOSE_req]; MAP_SEND_IMSI_rsp --> Idle3([Idle]); MAP_OPEN_req --> RecOpenCnf[Receive Open_Cnf]; RecOpenCnf -- Ok --> WF_IDENTITY_RESULT{WF_IDENTITY RESULT}; RecOpenCnf -- "Vr, Error" --> MAP_U_ABORT_req{MAP_U_ABORT_req}; WF_IDENTITY_RESULT --> Idle4([Idle]); MAP_U_ABORT_req --> Idle5([Idle]); +``` + +Flowchart of the Send\_IMSI\_GLR process. It starts at 'Idle', receives an 'Open\_ind', and enters 'Wait For Response'. From there, it can send 'MAP\_NOTICE\_ind' or 'MAP\_SEND\_IMSI\_ind' to the VLR (left), perform a 'Vr Dialogue' with the HLR (right), or encounter an 'Error'. The 'MAP\_NOTICE\_ind' path leads to 'MAP\_CLOSE\_req' and back to 'Idle'. The 'MAP\_SEND\_IMSI\_ind' path leads to 'Check Indication', which checks if the 'Subscriber Known'. If 'Yes', it sends 'MAP\_OPEN\_req', 'MAP\_SEND\_IMSI\_req', and 'MAP\_SWLIMITER\_req' to the HLR, receives 'Open\_Cnf', and outputs 'WF\_IDENTITY\_RESULT' to the VLR. If 'No', it sets 'UE= Unknown Subscriber', receives 'MAP\_SEND\_IMSI\_rsp' and 'MAP\_CLOSE\_req' from the HLR, and returns to 'Idle'. The 'Vr Dialogue' path leads to 'Idle' or an 'Error'. The 'Error' path from 'Wait For Response' also leads to 'Idle'. Finally, 'WF\_IDENTITY\_RESULT' leads to 'MAP\_U\_ABORT\_req' (on 'Vr, Error') or back to 'Idle' (on 'Ok'). + +Figure 20.3/2 (Sheet 1 of 2): Process Send\_IMSI\_GLR + +#### Process Send\_IMSI\_GLR + +20.3.2\_2(2) + +Figure 20.3/2: The send IMSI process in the GLR + +Arrows to left are to VLR +Arrows to right are to HLR + + + +``` +graph TD; Start([WF_IDENTITY_RESULT]) --> VLR[MAP_SEND_IMSI_cnf]; VLR --> Confirm[Check Confirmation]; Confirm -- OK --> End1([Idle]); Confirm -- Error --> SetError[Set error]; SetError --> End1; SetError --> VLR_rsp[MAP_SEND_IMSI_rsp +MAP_CLOSE_req]; VLR_rsp --> End1; Start --> HLR[MAP_NOTICE_ind]; HLR --> CloseReq[MAP_CLOSE_req]; CloseReq --> AbortReq{MAP_U_ABORT_req}; AbortReq --> End2([Idle]); AbortReq --> Indications[MAP_CLOSE_ind +MAP_U_ABORT_ind +MAP_P_ABORT_ind]; +``` + +The flowchart illustrates the 'Process Send\_IMSI\_GLR'. It begins with an entry point 'WF\_IDENTITY\_RESULT'. From here, a message 'MAP\_SEND\_IMSI\_cnf' is sent to the VLR (indicated by an arrow pointing left). The VLR performs a 'Check Confirmation'. If the result is 'OK', the process ends at an 'Idle' state. If the result is 'Error', it proceeds to 'Set error'. From 'Set error', the process can end at 'Idle' or send 'MAP\_SEND\_IMSI\_rsp' and 'MAP\_CLOSE\_req' back to the HLR (indicated by an arrow pointing right) before ending at 'Idle'. Another path from 'WF\_IDENTITY\_RESULT' sends 'MAP\_NOTICE\_ind' to the HLR. The HLR responds with 'MAP\_CLOSE\_req' to the VLR. The VLR then sends a 'MAP\_U\_ABORT\_req' (indicated by a diamond-shaped decision node). This request leads to an 'Idle' state and also triggers a set of indications: 'MAP\_CLOSE\_ind', 'MAP\_U\_ABORT\_ind', and 'MAP\_P\_ABORT\_ind'. + +Flowchart of Process Send\_IMSI\_GLR showing interactions between VLR and HLR. + +Figure 20.3/2 (Sheet 2 of 2): Process Send\_IMSI\_GLR + +# --- 21 Call handling procedures + +## 21.1 General + +The MAP call handling procedures are used: + +1. to retrieve routing information to handle a mobile terminating call; +2. to transfer control of a call back to the GMSC if the call is to be forwarded; +3. to retrieve and transfer information between anchor MSC and relay MSC for inter MSC group calls / broadcast calls; +4. to allocate resources in an SIWFS; +5. to handle the reporting of MS status for call completion services; +6. to handle the notification of remote user free for CCBS. + +Items 1, 5 and 6 are only procedures that have impact to the GLR. The following subclause describes the function of the GLR related to these procedures. + +## 21.2 Retrieval of routing information + +### 21.2.1 General + +The message flows for successful retrieval of routeing information for a mobile terminating call are shown in figure 21.2.1/1 (mobile terminating call which has not been optimally routed) and 21.2.1/2 (mobile-to-mobile call which has been optimally routed). + + + +``` + +sequenceDiagram + participant Network + participant Gateway as Gateway MSC + participant HLR + participant GLR + participant VLR + + Network->>Gateway: I_IAM (note2) + Gateway->>HLR: MAP_SEND_ROUTING_INFO + Note right of HLR: (note 1) + HLR->>GLR: MAP_PROVIDE_SUBSCRIBER_INFO + GLR->>VLR: MAP_PROVIDE_SUBSCRIBER_INFO + VLR->>GLR: MAP_PROVIDE_SUBSCRIBER_INFO ack + GLR->>HLR: MAP_PROVIDE_SUBSCRIBER_INFO ack + HLR->>Gateway: MAP_SEND_ROUTING_INFO ack + Gateway->>HLR: MAP_SEND_ROUTING_INFO + HLR->>GLR: MAP_PROVIDE_ROAMING_NUMBER + GLR->>VLR: MAP_PROVIDE_ROAMING_NUMBER + VLR->>GLR: MAP_PROVIDE_ROAMING_NUMBER ack + GLR->>HLR: MAP_PROVIDE_ROAMING_NUMBER ack + HLR->>Gateway: MAP_SEND_ROUTING_INFO ack + Gateway->>Network: I_IAM + +``` + +The diagram illustrates the message flow for a non-optimally routed mobile terminating call. It involves five entities: Network, Gateway (MSC), HLR, GLR, and VLR. The process starts with the Network sending an I\_IAM message to the Gateway MSC. The Gateway then sends a MAP\_SEND\_ROUTING\_INFO message to the HLR. The HLR sends a MAP\_PROVIDE\_SUBSCRIBER\_INFO message to the GLR, which in turn sends it to the VLR. The VLR returns a MAP\_PROVIDE\_SUBSCRIBER\_INFO ack to the GLR, which returns it to the HLR. The HLR then sends a MAP\_SEND\_ROUTING\_INFO ack to the Gateway. The Gateway sends another MAP\_SEND\_ROUTING\_INFO message to the HLR. The HLR sends a MAP\_PROVIDE\_ROAMING\_NUMBER message to the GLR, which sends it to the VLR. The VLR returns a MAP\_PROVIDE\_ROAMING\_NUMBER ack to the GLR, which returns it to the HLR. The HLR then sends a MAP\_SEND\_ROUTING\_INFO ack to the Gateway. Finally, the Gateway sends an I\_IAM message back to the Network. + +Sequence diagram showing message flow for retrieval of routing information (non-optimally routed call). + +Notes: + +xxx = *Optional Procedure* + +NOTE 1: This service may also be used by an ISDN exchange for obtaining routing information from the HLR. + +NOTE 2: TUP or ISUP may be used in signalling between MSCs, depending on the network type between the MSCs. For further details on the TUP and ISUP procedures refer to the following ITU-T Recommendations and ETSI specification: + +Q.721-725 - Telephone User Part (TUP); + +ETS 300 356-1 - Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 2 for the international interface; Part 1: Basic services. + +NOTE 3: As a network operator option, the HLR sends MAP\_PROVIDE\_SUBSCRIBER\_INFORMATION to the VLR. For further details on the CAMEL procedures refer to GSM 3GPP TS 03.78. + +**Figure 21.2.1/1: Message flow for retrieval of routeing information (non-optimally routed call)** + + + +``` + +sequenceDiagram + participant Network + participant Gateway as Gateway + participant HLR + participant GLR + participant VLR + + Note left of Network: I_IAM (note) + Network->>Gateway: MAP_SEND_ROUTING +INFO + Gateway->>HLR: MAP_PROVIDE_SUB- +SCRIBER_INFO + HLR->>GLR: MAP_PROVIDE_SUB- +SCRIBER_INFO + GLR->>VLR: MAP_PROVIDE_SUB- +SCRIBER_INFO + VLR->>GLR: MAP_PROVIDE_SUB- +SCRIBER_INFO ack + GLR->>HLR: MAP_PROVIDE_SUB- +SCRIBER_INFO ack + Note right of GLR: OR + HLR->>GLR: MAP_PROVIDE_ROAMING +NUMBER + GLR->>VLR: MAP_PROVIDE_ROAMING +NUMBER + VLR->>GLR: MAP_PROVIDE_ROAMING +NUMBER ack + GLR->>HLR: MAP_PROVIDE_ROAMING +NUMBER ack + HLR->>Gateway: MAP_SEND_ROUTING +INFO ack + Gateway->>Network: I_IAM + +``` + +Sequence diagram showing message flow for retrieval of routing information (optimally routed call). + +**Figure 21.2.1/2: Message flow for retrieval of routing information (optimally routed call)** + +#### **Notes:** + +xxx = *Optional Procedure.* + +For Optimal Routing phase 1, only one of the information flows for Provide Subscriber Info and Provide Roaming Number is used. For later phases of Optimal Routing, the HLR may return a MAP\_SEND\_ROUTING\_INFORMATION ack after the Provide Subscriber Info information flow, and the GMSC may send a second MAP\_SEND\_ROUTING\_INFORMATION, which will trigger the Provide Roaming Number information flow. + +TUP or ISUP may be used in signalling between MSCs, depending on the network type between the MSCs. For further details on the TUP and ISUP procedures refer to the following CCITT. + +Recommendations & ETSI specification: + +Q.721-725 - Telephone User Part (TUP); + +ETS 300 356-1 - Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 2 for the international interface; Part 1: Basic services. + +### 21.2.2 Process in the GLR to provide a roaming number + +The MAP process in the GLR to provide a roaming number for a mobile terminating call is shown in figure 21.2.2/1 (Process PRN\_Receive\_GLR) and figure 21.2.2/2 (Process PRN\_Send\_GLR). The MAP process invokes a macro not defined in this subclause; the definition of this macro can be found as follows: + +- Receive\_Open\_Ind see subclause 25.1. +- Receive\_Open\_Cnf see subclause 25.1. +- Check\_Confirmation see subclause 25.2. + + + +### Process PRN\_Receive\_GLR + +21.2.2.1(1) + +Figure 21.2.2/1: Process in the GLR to respond to a request routeing information + +Signals to/from the left are to/from the HLR; +signals to/from the right are to/from the GLR Call process + +``` + +graph TD + Start([ ]) --> Idle1([Idle]) + Idle1 --> RecOpen[Receive Open Ind] + RecOpen -- Vr --> PerfMAP[Perform MAP Vr Dialogue] + RecOpen -- OK --> WaitServ[Wait For Service Indication] + RecOpen -- Error --> IdleErr([Idle]) + + PerfMAP --> IdleVr([Idle]) + + WaitServ --> MAP_P_ABORT_ind{{MAP_P_ABORT_ind.}} + MAP_P_ABORT_ind --> IdleAbort([Idle]) + + WaitServ --> MAP_PRN_ind{{MAP_PROVIDE_ROAMING_NUMBER_ind.}} + MAP_PRN_ind --> ProvRoam[Provide Roaming Number To GLR Call process] + ProvRoam --> WaitResp([Wait For Response]) + + WaitServ --> MAP_NOT_ind{{MAP_NOTICE_ind.}} + MAP_NOT_ind --> MAP_CLOSE_req>MAP_CLOSE_req< + MAP_CLOSE_req --> IdleNot([Idle]) + + WaitResp --> PRN_ack{{Provide Roaming Number ack}} + WaitResp --> PRN_neg{{Provide Roaming Number negative response}} + WaitResp --> Abort{{Abort}} + + PRN_ack --> SetRes[Set result] + PRN_neg --> SetErr[Set error] + Abort --> MAP_U_ABORT_req>MAP_U_ABORT_req< + MAP_U_ABORT_req --> IdleUAbort([Idle]) + + SetRes --> MAP_PRN_rsp>MAP_PROVIDE_ROAMING_NUMBER_rsp.< + SetErr --> MAP_PRN_rsp + MAP_PRN_rsp --> IdleFinal([Idle]) + +``` + +SDL Diagram for Process PRN\_Receive\_GLR showing state transitions and signal handling between HLR and GLR Call process. + +**Figure 21.2.2/1: Process PRN\_Receive\_GLR** + + + +### Process PRN\_Send\_GLR 21.2.2.2(1) + +Figure 21.2.2/2: Process in the GLR to respond to a request routing information + +Signals to/from the left are to/from the GLR Call; process signals to/from the right are to/from the VLR + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> ProvideRoamingNumber: Provide Roaming Number + state " " as Outbound + ProvideRoamingNumber --> Outbound + Outbound --> ReceiveOpenCnf: MAP_Open_req, MAP_PROVIDE_ROAMING_NUMBER_req, MAP_DELIMITER_req + ReceiveOpenCnf --> WaitForResponse: Open cnf + state "Wait For Response" as WaitForResponse + WaitForResponse --> CheckConfirmation: MAP_PROVIDE_ROAMING_NUMBER_cnf (OK) + WaitForResponse --> PerformMAPVr: MAP_U_ABORT_ind, MAP_P_ABORT_ind (Vr) + WaitForResponse --> MAP_NOTICE_ind: MAP_NOTICE_ind (Error) + PerformMAPVr --> [*] + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Abort + Abort --> [*] + CheckConfirmation --> ProvideRoamingNumberAck: OK + CheckConfirmation --> ProvideRoamingNumberNegativeResponse: Error + ProvideRoamingNumberAck --> [*] + ProvideRoamingNumberNegativeResponse --> [*] +``` + +State transition diagram for Process PRN\_Send\_GLR. The process starts at 'Idle', transitions to 'Provide Roaming Number', then to a state where it sends MAP\_Open\_req, MAP\_PROVIDE\_ROAMING\_NUMBER\_req, and MAP\_DELIMITER\_req. It then receives an 'Open cnf' and enters 'Wait For Response'. From there, it can receive 'MAP\_PROVIDE\_ROAMING\_NUMBER\_cnf' (OK), 'MAP\_U\_ABORT\_ind'/'MAP\_P\_ABORT\_ind' (Vr), or 'MAP\_NOTICE\_ind' (Error). The first leads to 'Check Confirmation' and then either 'Provide Roaming Number ack' (OK) or 'Provide Roaming Number negative response' (Error). The second and third lead to 'Abort'. + +Figure 21.2.2/2: Process PRN\_Send\_GLR + +### 21.2.3 Process in the GLR to provide subscriber information + +The MAP process in the GLR to provide subscriber information for a mobile terminating call is shown in figure 21.2.3/1 (Process PSI Receive\_GLR) and figure 21.2.3/2 (Process PSI Send\_GLR). The MAP process invokes a macro not defined in this subclause; the definition of this macro can be found as follows: + +| | | +|--------------------|---------------------| +| Receive_Open_Ind | see subclause 25.1. | +| Receive_Open_Cnf | see subclause 25.1. | +| Check_Confirmation | see subclause 25.2. | + + + +### Process PSI\_Receive\_GLR + +21.2.3.1(1) + +Figure 21.2.3/1: Process in the GLR to respond to a request routing information + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the GLR Call process + +``` +graph TD; Start([Idle]) --> OpenInd[Receive Open Ind]; OpenInd --> Vr{Vr}; Vr -- OK --> WaitForService([Wait For Service Indication]); Vr -- Error --> Idle1([Idle]); Vr -- Vr --> PerformMAP[Perform MAP Vr Dialogue]; PerformMAP --> Idle2([Idle]); WaitForService --> MAP_P_ABORT_ind{MAP_P_ABORT_ind}; WaitForService --> MAP_PROVIDE_SUBSCRIBER_INFO_ind[MAP_PROVIDE_SUBSCRIBER_INFO_ind]; WaitForService --> MAP_NOTICE_ind{MAP_NOTICE_ind}; MAP_P_ABORT_ind --> Idle3([Idle]); MAP_PROVIDE_SUBSCRIBER_INFO_ind --> ProvideSubscriberInfo[Provide Subscriber Info To GLR Call process]; ProvideSubscriberInfo --> WaitForResponse([Wait For Response]); MAP_NOTICE_ind --> MAP_CLOSE_req{MAP_CLOSE_req}; MAP_CLOSE_req --> Idle4([Idle]); WaitForResponse --> ProvideSubscriberInfoAck{Provide Subscriber Info ack}; WaitForResponse --> ProvideSubscriberInfoNegativeResponse{Provide Subscriber Info negative response}; WaitForResponse --> Abort{Abort}; ProvideSubscriberInfoAck --> SetResult[Set result]; ProvideSubscriberInfoNegativeResponse --> SetError[Set error]; Abort --> MAP_U_ABORT_req[MAP_U_ABORT_req]; SetResult --> MAP_PROVIDE_SUBSCRIBER_INFO_rsp[MAP_PROVIDE_SUBSCRIBER_INFO_rsp]; SetError --> MAP_PROVIDE_SUBSCRIBER_INFO_rsp; MAP_PROVIDE_SUBSCRIBER_INFO_rsp --> Idle5([Idle]); +``` + +Flowchart for Process PSI\_Receive\_GLR. It starts at an Idle state, receives an Open Indication, and then branches based on OK, Error, or Vr signals. The main path involves waiting for a service indication, sending a MAP\_PROVIDE\_SUBSCRIBER\_INFO\_ind, waiting for a response, and then handling ack, negative response, or abort signals to either set a result, set an error, or send a MAP\_U\_ABORT\_req before returning to Idle. + +Figure 21.2.3/1 : Process PSI\_Receive\_GLR + + + +**Process PSI\_Send\_GLR** 21.2.3.2(1) + +Figure 21.2.3/2: Process in the GLR to respond to a request routing information + +Signals to/from the left are to/from the GLR Call; process signals to/from the right are to/from the VLR + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> ProvideSubscriberInfo: Provide Subscriber Info + ProvideSubscriberInfo --> Out: MAP_Open_req, MAP_PROVIDE_SUBSCRIBER_INFO_req, MAP_DELIMITER_req + Out --> ReceiveOpenCnf: Receive Open cnf + ReceiveOpenCnf --> WaitForResponse: OK + ReceiveOpenCnf --> PerformMAPVr: Vr + ReceiveOpenCnf --> ProvideSubscriberInfoNegativeResponse: Error + PerformMAPVr --> [*]: + ProvideSubscriberInfoNegativeResponse --> [*]: + WaitForResponse --> In: MAP_PROVIDE_SUBSCRIBER_INFO_cnf + WaitForResponse --> Abort1: MAP_U_ABORT_ind, MAP_P_ABORT_ind + WaitForResponse --> In2: MAP_NOTICE_ind + In --> CheckConfirmation: Check Confirmation + CheckConfirmation --> ProvideSubscriberInfoAck: OK + CheckConfirmation --> ProvideSubscriberInfoNegativeResponse2: Error + ProvideSubscriberInfoAck --> [*]: + ProvideSubscriberInfoNegativeResponse2 --> [*]: + Abort1 --> [*]: + In2 --> MAP_CLOSE_req: MAP_CLOSE_req + MAP_CLOSE_req --> Abort2: Abort + Abort2 --> [*]: + +``` + +State transition diagram for Process PSI\_Send\_GLR. The process starts at an initial state, goes to Idle, then Provide Subscriber Info. It sends MAP\_Open\_req, MAP\_PROVIDE\_SUBSCRIBER\_INFO\_req, and MAP\_DELIMITER\_req. It then receives an Open cnf. From there, it branches based on the response: OK leads to Wait For Response; Vr leads to Perform MAP Vr (which leads to an error state); Error leads to Provide Subscriber Info negative response (which also leads to an error state). From Wait For Response, it branches into three possible indications: MAP\_PROVIDE\_SUBSCRIBER\_INFO\_cnf, MAP\_U\_ABORT\_ind/MAP\_P\_ABORT\_ind, or MAP\_NOTICE\_ind. The first leads to Check Confirmation, which then branches into Provide Subscriber Info ack (OK) or Provide Subscriber Info negative response (Error), both leading to error states. The second and third lead directly to Abort, which also leads to an error state. + +Figure 21.2.3/2 : Process PSI\_Send\_GLR + +## 21.3 Setting of Reporting State + +### 21.3.1 General + +In case the HLR received the CCBS request message from the other HLR for CCSB monitoring, the message flow for setting the reporting state is shown in figure 21.3.1/1. The message flow shown in figure 21.3.1/1 shall also be applied in case for stop monitoring. The stage2 specification for the interaction with CCBS in a GLR is in 3GPP TS 23.119. + + + +``` +sequenceDiagram + participant VLR + participant GLR + participant HLR + Note right of VLR: MAP_SET_REPORTING_STATE + VLR->>GLR: MAP_SET_REPORTING_STATE + Note left of GLR: MAP_SET_REPORTING_STATE + GLR->>HLR: MAP_SET_REPORTING_STATE + Note right of HLR: MAP_SET_REPORTING_STATE ack + HLR-->>GLR: MAP_SET_REPORTING_STATE ack + Note left of GLR: MAP_SET_REPORTING_STATE ack + GLR-->>VLR: MAP_SET_REPORTING_STATE ack +``` + +The diagram illustrates the message flow for setting the reporting state across three network elements: VLR, GLR, and HLR. The sequence begins with the VLR sending a **MAP\_SET\_REPORTING\_STATE** message to the GLR. Upon receiving this, the GLR sends a **MAP\_SET\_REPORTING\_STATE** message to the HLR. The HLR responds with a **MAP\_SET\_REPORTING\_STATE ack** message back to the GLR. Finally, the GLR sends its own **MAP\_SET\_REPORTING\_STATE ack** message back to the VLR. All messages are represented by dashed arrows indicating the direction of flow. + +Sequence diagram showing message flow for setting the reporting state between VLR, GLR, and HLR. + +**Figure 21.3.1/1: Message Flow for Setting the Reporting State** + +### 21.3.2 Process in the GLR to set the reporting state + +The MAP process in the GLR to set the reporting state is shown in figures 21.3.2/1 and 21.3.2/2. The MAP process invokes a macro not define in this subclause; the definition of this macro can be found as follows: + +| | | +|--------------------|---------------------| +| Receive_Open_Ind | see subclause 25.1. | +| Receive_Open_Cnf | see subclause 25.1. | +| Check_Confirmation | see subclause 25.2. | + +#### Set the reporting state + +When receiving the **MAP\_SET\_REPORTING\_STATE** indication, the MAP user in the GLR transfers the information to the VLR in the **MAP\_SET\_REPORTING\_STATE** request. + +The GLR then awaits the receipt of the **MAP\_SET\_REPORTING\_STATE** confirm from the VLR. The MAP user in the GLR shall transfer the information contained in this primitive to the HLR in the **MAP\_SET\_REPORTING\_STATE** response without checking its contents. + + + +**Process Reporting\_State\_Receive\_GLR** 21.3.2.1(1) + +Figure 21.3.2/1: Process in the GLR to respond to a request reporting state + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the GLR Call process + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> Receive_Open_Ind : Open Ind + state "Receive Open Ind" as Receive_Open_Ind + Receive_Open_Ind --> Idle : Error + Receive_Open_Ind --> Wait_For_Service_Indication : OK + state "Wait For Service Indication" as Wait_For_Service_Indication + Receive_Open_Ind --> Perform_MAP_Vr_Dialogue : Vr + state "Perform MAP Vr Dialogue" as Perform_MAP_Vr_Dialogue + Perform_MAP_Vr_Dialogue --> Idle + Wait_For_Service_Indication --> MAP_P_ABORT_ind : MAP_P_ABORT_ind + state "MAP_P_ABORT_ind" as MAP_P_ABORT_ind + MAP_P_ABORT_ind --> Idle + Wait_For_Service_Indication --> MAP_SET_REPORTING_ind : MAP_SET_REPORTING_ind + state "MAP_SET_REPORTING_ind" as MAP_SET_REPORTING_ind + MAP_SET_REPORTING_ind --> Set_Reporting_To_GLR_Call_process : Set Reporting To GLR Call process + state "Set Reporting To GLR Call process" as Set_Reporting_To_GLR_Call_process + Set_Reporting_To_GLR_Call_process --> Wait_For_Response + state "Wait For Response" as Wait_For_Response + Wait_For_Response --> Set_Reporting_ack : Set Reporting ack + state "Set Reporting ack" as Set_Reporting_ack + Set_Reporting_ack --> Set_result : Set result + state "Set result" as Set_result + Set_result --> MAP_SET_REPORTING_rsp : MAP_SET_REPORTING_rsp + state "MAP_SET_REPORTING_rsp" as MAP_SET_REPORTING_rsp + MAP_SET_REPORTING_rsp --> Idle + Wait_For_Response --> Set_Reporting_negative_response : Set Reporting negative response + state "Set Reporting negative response" as Set_Reporting_negative_response + Set_Reporting_negative_response --> Set_error : Set error + state "Set error" as Set_error + Set_error --> Idle + Wait_For_Response --> Abort : Abort + state "Abort" as Abort + Abort --> MAP_U_ABORT_req : MAP_U_ABORT_req + state "MAP_U_ABORT_req" as MAP_U_ABORT_req + MAP_U_ABORT_req --> Idle + Wait_For_Service_Indication --> MAP_NOTICE_ind : MAP_NOTICE_ind + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + MAP_NOTICE_ind --> MAP_CLOSE_req : MAP_CLOSE_req + state "MAP_CLOSE_req" as MAP_CLOSE_req + MAP_CLOSE_req --> Idle +``` + +State transition diagram for Process Reporting\_State\_Receive\_GLR. The process starts at Idle, receives an Open Indication, and then branches based on the response (OK, Error, or Vr). The OK path leads to waiting for a service indication, then either a MAP\_P\_ABORT\_ind (returning to Idle), a MAP\_SET\_REPORTING\_ind (leading to Set Reporting To GLR Call process and then Wait For Response), or a MAP\_NOTICE\_ind (leading to MAP\_CLOSE\_req and Idle). The Wait For Response path leads to Set Reporting ack (Set result, then MAP\_SET\_REPORTING\_rsp, then Idle), Set Reporting negative response (Set error, then Idle), or Abort (MAP\_U\_ABORT\_req, then Idle). The Error path returns to Idle. The Vr path leads to Perform MAP Vr Dialogue and then Idle. + +**Figure 21.3.2/1: Process Reporting\_State\_Receive\_GLR** + + + +**Process Reporting\_State\_Send\_GLR** 21.3.2.2(1) + +Figure 21.3.2/2: Process in the GLR to respond to a request reporting state + +Signals to/from the left are to/from the GLR Call; process signals to/from the right are to/from the VLR + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Set_Reporting: Set Reporting + Set_Reporting --> Open_cnf: MAP_Open_req, MAP_SET_REPORTING_req, MAP_DELIMITER_req + Open_cnf --> Wait_For_Response: OK + Open_cnf --> Perform_MAP_Vr: Vr + Open_cnf --> Set_Reporting_negative_response_1: Error + Wait_For_Response --> Set_Reporting_ack: MAP_SET_REPORTING_cnf + Wait_For_Response --> Abort_1: MAP_U_ABORT_ind, MAP_P_ABORT_ind + Wait_For_Response --> Abort_2: MAP_NOTICE_ind + Set_Reporting_ack --> Check_Confirmation: Check Confirmation + Check_Confirmation --> Set_Reporting_ack: OK + Check_Confirmation --> Set_Reporting_negative_response_2: Error + Perform_MAP_Vr --> [*] + Set_Reporting_negative_response_1 --> [*] + Abort_1 --> [*] + Abort_2 --> [*] + Set_Reporting_ack --> [*] + Set_Reporting_negative_response_2 --> [*] + +``` + +State transition diagram for Process Reporting\_State\_Send\_GLR. The process starts at Idle, transitions to Set Reporting, then receives an Open confirmation. It then branches based on the response: OK leads to Wait For Response, which then branches into three paths: MAP\_SET\_REPORTING\_cnf (leading to Check Confirmation and then Set Reporting ack or negative response), MAP\_U\_ABORT\_ind/MAP\_P\_ABORT\_ind (leading to Abort), and MAP\_NOTICE\_ind (leading to MAP\_CLOSE\_req and then Abort). The initial Set Reporting step also sends MAP\_Open\_req, MAP\_SET\_REPORTING\_req, and MAP\_DELIMITER\_req. The Wait For Response state also has transitions for Vr (Perform MAP Vr) and Error (Set Reporting negative response), both leading to terminal states. + +Figure 21.3.2/2: Process Reporting\_State\_Send\_GLR + +## 21.4 Status Reporting + +### 21.4.1 General + +In case that the monitored subscriber becomes to the idle state, the message flow for reporting subscriber's state to the HLR is shown in figure 21.4.1/1. The stage2 specification for the interaction with CCBS in a GLR is in 3GPP TS 23.119. + + + +``` +sequenceDiagram + participant VLR + participant GLR + participant HLR + Note right of VLR: MAP_STATUS_REPORT + VLR->>GLR: MAP_STATUS_REPORT + Note right of GLR: MAP_STATUS_REPORT ack + GLR-->>VLR: MAP_STATUS_REPORT ack + Note right of GLR: MAP_STATUS_REPORT + GLR->>HLR: MAP_STATUS_REPORT + Note right of HLR: MAP_STATUS_REPORT ack + HLR-->>GLR: MAP_STATUS_REPORT ack +``` + +Sequence diagram showing message flow between VLR, GLR, and HLR for status reporting. The VLR sends a MAP\_STATUS\_REPORT to the GLR, which receives an acknowledgment. The GLR then sends a MAP\_STATUS\_REPORT to the HLR, which also receives an acknowledgment. + +Figure 21.4.1/1: Message Flow for Status Reporting + +### 21.4.2 Process in the GLR for Status Reporting + +The MAP process in the GLR to send the status report to the HLR is shown in figures 21.4.1/1 and 21.4.2/2. + +#### Send Status report + +When receiving the MAP\_STATUS\_REPORT indication, the MAP user in the GLR transfers the information to the HLR in the MAP\_STATUS\_REPORT request. + +The GLR then awaits the receipt of the MAP\_STATUS\_REPORT confirm from the HLR. The MAP user in the GLR shall transfer the information contained in this primitive to the VLR in the MAP\_STATUS\_REPORT response without checking its contents. + + + +### Process Status\_Report\_Receive\_GLR + +21.4.2.1(1) + +Figure 21.4.2/1: Process in the GLR to respond to a request status report + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the GLR Call process + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> Receive_Open_Ind : Open Ind + Receive_Open_Ind --> Wait_For_Service_Indication : OK + Receive_Open_Ind --> Idle : Error + Receive_Open_Ind --> Perform_MAP_Vr_Dialogue : Vr + Wait_For_Service_Indication --> MAP_P_ABORT_ind + Wait_For_Service_Indication --> MAP_STATUS_REPORT_ind + Wait_For_Service_Indication --> MAP_NOTICE_ind + MAP_P_ABORT_ind --> Idle + MAP_STATUS_REPORT_ind --> Status_Report_To_GLR_Call_process : Status Report To GLR Call process + Status_Report_To_GLR_Call_process --> Wait_For_Response + Wait_For_Response --> Status_Report_ack + Wait_For_Response --> Status_Report_negative_response + Wait_For_Response --> Abort + Status_Report_ack --> Set_result + Status_Report_negative_response --> Set_error + Set_result --> MAP_STATUS_REPORT_rsp + Set_error --> MAP_U_ABORT_req + MAP_STATUS_REPORT_rsp --> Idle + MAP_U_ABORT_req --> Idle + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle +``` + +State transition diagram for Process Status\_Report\_Receive\_GLR. The process starts at Idle, receives an Open Indication, and then branches based on OK, Error, or Vr signals. The OK path leads to Wait For Service Indication, then to MAP\_STATUS\_REPORT\_ind, Status Report To GLR Call process, Wait For Response, and finally to Idle via MAP\_STATUS\_REPORT\_rsp. The Error path leads to Idle via MAP\_NOTICE\_ind and MAP\_CLOSE\_req. The Vr path leads to Perform MAP Vr Dialogue and then to Idle. Negative responses lead to Set error and then to Idle via MAP\_U\_ABORT\_req. + +Figure 21.4.2/1: Process Status\_Report\_Receive\_GLR + + + +### Process Status\_Report\_Send\_GLR 21.4.2.2(1) + +Figure 21.4.2/2: Process in the GLR to respond to a request status report + +Signals to/from the left are to/from the GLR Call; process signals to/from the right are to/from the HLR + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> Status_Report + Status_Report --> Open_Req + Open_Req --> Open_Cnf + Open_Cnf --> Wait_For_Response + state "Wait For Response" as Wait_For_Response + state "Status Report" as Status_Report + state "Open cnf" as Open_Cnf + state "Check Confirmation" as Check_Confirmation + state "Status Report ack" as Status_Report_ack + state "Status Report negative response" as Status_Report_negative_response + state "Abort" as Abort + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_CLOSE_req" as MAP_CLOSE_req + + Note right of Open_Req: MAP_Open_req +MAP_STATUS_REPORT_req +MAP_DELIMITER_req + Note left of Open_Cnf: Open cnf + Note right of MAP_NOTICE_ind: MAP_CLOSE_req + Note right of Check_Confirmation: OK / Error + + Wait_For_Response --> Status_Report_ack + Wait_For_Response --> Abort + Wait_For_Response --> MAP_NOTICE_ind + Status_Report --> Abort : Vr + Status_Report --> Status_Report_negative_response : Error + + Status_Report_ack --> [*] + Status_Report_negative_response --> [*] + Abort --> [*] + MAP_CLOSE_req --> Abort + Abort --> [*] +``` + +State transition diagram for Process Status\_Report\_Send\_GLR. The process starts at 'Idle', receives a 'Status Report', sends 'MAP\_Open\_req', 'MAP\_STATUS\_REPORT\_req', and 'MAP\_DELIMITER\_req', receives 'Open cnf', and then enters 'Wait For Response'. From 'Wait For Response', it can receive 'MAP\_STATUS\_REPORT\_cnf' (leading to 'Check Confirmation' and then 'Status Report ack' or 'Status Report negative response'), 'MAP\_U\_ABORT\_ind'/'MAP\_P\_ABORT\_ind' (leading to 'Abort'), or 'MAP\_NOTICE\_ind' (leading to 'MAP\_CLOSE\_req' and then 'Abort'). Transitions to 'Abort' and 'Status Report negative response' from 'Wait For Response' are also labeled 'Vr' and 'Error'. + +Figure 21.4.2/2: Process Status\_Report\_Send\_GLR + +## 21.5 Remote User Free + +### 21.5.1 General + +The message flow for handling remote user free is shown in figure 21.5.1/1. + + + +``` +sequenceDiagram + participant VLR + participant GLR + participant HLR + Note right of GLR: MAP_REMOTE_USER_FREE + GLR-->>VLR: MAP_REMOTE_USER_FREE + Note left of VLR: MAP_REMOTE_USER_FREE ack + VLR-->>GLR: MAP_REMOTE_USER_FREE ack + Note right of HLR: MAP_REMOTE_USER_FREE + HLR-->>GLR: MAP_REMOTE_USER_FREE + Note right of GLR: -- + Note right of GLR: MAP_REMOTE_USER_FREE ack + GLR-->>HLR: MAP_REMOTE_USER_FREE ack + Note right of GLR: -> +``` + +Sequence diagram showing message flow between VLR, GLR, and HLR for Remote User Free. The diagram shows three vertical lifelines: VLR, GLR, and HLR. The sequence of messages is: 1. GLR sends MAP\_REMOTE\_USER\_FREE to VLR (dashed arrow). 2. VLR sends MAP\_REMOTE\_USER\_FREE ack to GLR (dashed arrow). 3. HLR sends MAP\_REMOTE\_USER\_FREE to GLR (dashed arrow). 4. GLR sends a return message to HLR (dashed arrow with '->'). + +Figure 21.5.1/1: Message Flow for Remote User Free + +### 21.5.2 Process in the GLR for Remote User Free + +The MAP process in the GLR to handling Remote User Free is shown in figures 21.5.2/1 and 21.5.2/2. + +#### Remote User Free + +When receiving the MAP\_REMOTE\_USER\_FREE indication, the MAP user in the GLR transfers the information to the VLR in the MAP\_REMOTE\_USER\_FREE request. + +The GLR then awaits the receipt of the MAP\_REMOTE\_USER\_FREE confirm from the VLR. The MAP user in the GLR shall transfer the information contained in this primitive to the HLR in the MAP\_REMOTE\_USER\_FREE response without checking its contents. + + + +### Process Remote\_User\_Free\_Receive\_GLR + +21.5.2.1(1) + +Figure 21.5.2/1: Process in the GLR to respond to a request remote user free + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the GLR Call process + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> Receive_Open_Ind + Receive_Open_Ind --> OK + OK --> Wait_For_Service_Indication + Wait_For_Service_Indication --> MAP_REMOTE_USER_FREE_ind + MAP_REMOTE_USER_FREE_ind --> Remote_User_Free_To_GLR_Call_process + Remote_User_Free_To_GLR_Call_process --> Wait_For_Response + Wait_For_Response --> Remote_User_Free_ack + Wait_For_Response --> Remote_User_Free_negative_response + Wait_For_Response --> Abort + Remote_User_Free_ack --> Set_result + Remote_User_Free_negative_response --> Set_error + Set_result --> MAP_REMOTE_USER_FREE_rsp + Set_error --> MAP_REMOTE_USER_FREE_rsp + MAP_REMOTE_USER_FREE_rsp --> Idle + Abort --> MAP_U_ABORT_req + MAP_U_ABORT_req --> Idle + Receive_Open_Ind --> Vr + Vr --> Perform_MAP_Vr_Dialogue + Perform_MAP_Vr_Dialogue --> Idle + Receive_Open_Ind --> Error + Error --> Idle + Wait_For_Service_Indication --> MAP_P_ABORT_ind + MAP_P_ABORT_ind --> Idle + Wait_For_Service_Indication --> MAP_NOTICE_ind + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Idle +``` + +State transition diagram for Process Remote\_User\_Free\_Receive\_GLR. It starts at Idle, receives an Open Indication, and then branches based on OK, Vr, or Error signals. The OK path leads to waiting for a service indication, then sending a MAP\_REMOTE\_USER\_FREE\_ind to the GLR Call process, waiting for a response, and finally sending a MAP\_REMOTE\_USER\_FREE\_rsp. The Vr path leads to performing a MAP Vr Dialogue. The Error path leads to Idle. Other branches include MAP\_P\_ABORT\_ind, MAP\_NOTICE\_ind, and MAP\_CLOSE\_req, all leading to Idle states. + +Figure 21.5.2/1: Process Remote\_User\_Free\_Receive\_GLR + + + +### Process Remote\_User\_Free\_Send\_GLR 21.5.2.2(1) + +Figure 21.5.2/2: Process in the GLR to respond to a request remote user free + +Signals to/from the left are to/from the GLR Call; process signals to/from the right are to/from the VLR + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> Remote_User_Free + Remote_User_Free --> Send_Requests + state "Send_Requests" as Send_Requests + Send_Requests --> Receive_Open_cnf + Receive_Open_cnf --> Wait_For_Response : OK + Receive_Open_cnf --> Perform_MAP_Vr : Vr + Receive_Open_cnf --> Remote_User_Free_negative_response_1 : Error + Perform_MAP_Vr --> [*] + Remote_User_Free_negative_response_1 --> [*] + Wait_For_Response --> Check_Confirmation : MAP_REMOTE_USER_FREE_cnf + Wait_For_Response --> Abort_1 : MAP_U_ABORT_ind / MAP_P_ABORT_ind + Wait_For_Response --> MAP_NOTICE_ind + Check_Confirmation --> Remote_User_Free_ack : OK + Check_Confirmation --> Remote_User_Free_negative_response_2 : Error + Remote_User_Free_ack --> [*] + Remote_User_Free_negative_response_2 --> [*] + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> Abort_2 + Abort_1 --> [*] + Abort_2 --> [*] +``` + +State transition diagram for Process Remote\_User\_Free\_Send\_GLR. The process starts at 'Idle', receives 'Remote User Free', sends 'MAP\_Open\_req', 'MAP\_REMOTE\_USER\_FREE\_req', and 'MAP\_DELIMITER\_req', then receives 'Open cnf'. From 'Receive Open cnf', an 'OK' path leads to 'Wait For Response', while 'Vr' and 'Error' paths lead to 'Perform MAP Vr' and 'Remote User Free negative response' respectively, both of which are terminated. From 'Wait For Response', three paths emerge: 'MAP\_REMOTE\_USER\_FREE\_cnf' leads to 'Check Confirmation', 'MAP\_U\_ABORT\_ind' / 'MAP\_P\_ABORT\_ind' leads to 'Abort', and 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_req' and then 'Abort'. From 'Check Confirmation', 'OK' leads to 'Remote User Free ack' and 'Error' leads to 'Remote User Free negative response', both terminated. All terminal states are marked with an 'X'. + +Figure 21.5.2/2: Process Remote\_User\_Free\_Send\_GLR + +# 22 Supplementary services procedures + +## 22.1 Functional supplementary service processes + +### 22.1.1 Functional supplementary service process co-ordinator for GLR + +Any functional SS process in the GLR starts by the GLR receiving a MAP-OPEN service indication. If that service is successful, the GLR can handle supplementary service indications from the VLR. Table 21.1/1 shows the co-ordinating process' reaction on receipt of specific SS service indications from the VLR. After the relevant process is invoked, the received service indication is sent to that process, and the co-ordinating process terminates. + +**Table 21.1/1: Relationship between received service indication and invoked process in the GLR** + +| Service indication received | Process invoked | +|------------------------------------|------------------------| +| MAP_REGISTER_SS_ind | REGISTER_SS_GLR | +| MAP_ERASE_SS_ind | ERASE_SS_GLR | +| MAP_ACTIVATE_SS_ind | ACTIVATE_SS_GLR | +| MAP_DEACTIVATE_SS_ind | DEACTIVATE_SS_GLR | +| MAP_INTERROGATE_SS_ind | INTERROGATE_SS_GLR | +| MAP_REGISTER_PASSWORD | REGISTER_PASSWORD_GLR | + +Figure 22.1/1 shows the co-ordinating process in the GLR. + +#### Process SS\_Coordinator\_GLR + +22.1.1\_1(2) + +Figure 22.1/1: Supplementary Service Coordination process in the GLR, to identify which functional supplementary service process be invoked. + + + +``` +graph TD; Start([ ]) --> NULL1(NULL); NULL1 --> Receive_Open_ind[Receive_Open_ind]; Receive_Open_ind --> Wait_for_service_ind((Wait_for_service_ind)); Receive_Open_ind -- Error --> Perform_MAP_V1_Dialogue[Perform_MAP_V1_Dialogue]; Perform_MAP_V1_Dialogue --> NULL2(NULL); Wait_for_service_ind --> MAP_REGISTER_ind{MAP_REGISTER_
SS_ind}; Wait_for_service_ind --> MAP_ERASE_ind{MAP_ERASE_
SS_ind}; Wait_for_service_ind --> MAP_ACTIVATE_ind{MAP_ACTIVATE_
SS_ind}; Wait_for_service_ind --> MAP_DEACTIVATE_ind{MAP_DEACTIVATE_
SS_ind}; Wait_for_service_ind --> MAP_INTERROGATE_ind{MAP_INTERROGATE_
SS_ind}; Wait_for_service_ind --> MAP_REGISTER_PASSWORD_ind{MAP_REGISTER_
PASSWORD_
SS_ind}; MAP_REGISTER_ind --> Register_SS_GLR[Register_
SS_GLR]; Register_SS_GLR --> MAP_REGISTER_ind_return{MAP_REGISTER_
SS_ind}; MAP_ERASE_ind --> Erase_SS_GLR[Erase_
SS_GLR]; Erase_SS_GLR --> MAP_ERASE_ind_return{MAP_ERASE_
SS_ind}; MAP_ACTIVATE_ind --> Activate_SS_GLR[Activate_
SS_GLR]; Activate_SS_GLR --> MAP_ACTIVATE_ind_return{MAP_ACTIVATE_
SS_ind}; MAP_DEACTIVATE_ind --> Deactivate_SS_GLR[Deactivate_
SS_GLR]; Deactivate_SS_GLR --> MAP_DEACTIVATE_ind_return{MAP_DEACTIVATE_
SS_ind}; MAP_INTERROGATE_ind --> Interrogate_SS_GLR[Interrogate_
SS_GLR]; Interrogate_SS_GLR --> MAP_INTERROGATE_ind_return{MAP_INTERROGATE_
SS_ind}; MAP_REGISTER_PASSWORD_ind --> Register_Password_SS_GLR[Register_
Password_
SS_GLR]; Register_Password_SS_GLR --> MAP_REGISTER_PASSWORD_ind_return{MAP_REGISTER_
PASSWORD_
SS_ind}; MAP_REGISTER_ind_return --> Relay_Info((Relay_Info)); MAP_ERASE_ind_return --> Relay_Info; MAP_ACTIVATE_ind_return --> Relay_Info; MAP_DEACTIVATE_ind_return --> Relay_Info; MAP_INTERROGATE_ind_return --> Relay_Info; MAP_REGISTER_PASSWORD_ind_return --> Relay_Info; Relay_Info --> MAP_NOTICE_ind{MAP_NOTICE_
ind}; MAP_NOTICE_ind --> MAP_CLOSE_ind{MAP_CLOSE_
ind}; MAP_CLOSE_ind --> NULL3(NULL); +``` + +Signals to/from the left are to/from the VLR via the MAP provider; signals to/from the right are to/from the child process + +Flowchart for Process SS\_Coordinator\_GLR. It starts with an oval, followed by a NULL terminal, then a 'Receive\_Open\_ind' block. An 'Error' path leads to 'Perform\_MAP\_V1\_Dialogue' and another NULL terminal. The main path goes to 'Wait\_for\_service\_ind', which then branches into six parallel MAP service paths: REGISTER, ERASE, ACTIVATE, DEACTIVATE, INTERROGATE, and REGISTER PASSWORD. Each path has a corresponding GLR process block and a return signal block. All six return signals converge to a 'Relay\_Info' block. From 'Relay\_Info', the flow goes to 'MAP\_NOTICE\_ind', then 'MAP\_CLOSE\_ind', and finally a NULL terminal. A note on the right explains signal directions: 'Signals to/from the left are to/from the VLR via the MAP provider; signals to/from the right are to/from the child process'. + +Figure 22.1/1 (sheet 1 of 2): Process SS\_Coordinator\_GLR + + + +**Process SS\_Coordinator\_GLR** 22.1.1\_2(2) + +Figure 22.1/1: Supplementary Service Coordination process in the GLR, to identify which functional supplementary service process be invoked. + +Signals to/from the left are to/from the VLR via the MAP provider; signals to/from the right are to/from the child process + +``` + +stateDiagram-v2 + [*] --> Relay_Info + state "Relay_Info" as Relay_Info + state "*FROM PROVIDER" as FROM_PROVIDER + state "*FROM OFFSPRING" as FROM_OFFSPRING + state "*TO OFFSPRING" as TO_OFFSPRING + state "*TO PROVIDER" as TO_PROVIDER + state "NULL" as NULL + + FROM_PROVIDER --> TO_OFFSPRING + FROM_OFFSPRING --> TO_PROVIDER + + TO_OFFSPRING --> Relay_Info + TO_OFFSPRING --> NULL + + TO_PROVIDER --> Relay_Info + TO_PROVIDER --> NULL + + FROM_PROVIDER --> MAP_U_ABORT_ind + FROM_PROVIDER --> MAP_P_ABORT_ind + FROM_PROVIDER --> MAP_CLOSE_ind + + FROM_OFFSPRING --> MAP_U_ABORT_ind + FROM_OFFSPRING --> MAP_CLOSE_ind + +``` + +State transition diagram for Process SS\_Coordinator\_GLR. The diagram shows four main paths originating from a central 'Relay\_Info' state. Path 1: \*FROM PROVIDER -> \*TO OFFSPRING -> Relay\_Info. Path 2: \*FROM PROVIDER -> \*TO OFFSPRING -> NULL. Path 3: \*FROM OFFSPRING -> \*TO PROVIDER -> Relay\_Info. Path 4: \*FROM OFFSPRING -> \*TO PROVIDER -> NULL. Transitions from PROVIDER and OFFSPRING include specific MAP indications: MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind for the left side, and MAP\_U\_ABORT\_ind, MAP\_CLOSE\_ind for the right side. + +**Figure 22.1/1 (sheet 2 of 2): Process SS\_Coordinator\_GLR** + +### 22.1.2 Call completion supplementary service process co-ordinator for GLR + +The MAP co-ordinating process in the GLR to handle a dialogue opened with the call Completion application context is shown in figure 22.1/2. The MAP process invokes a macro not defined in this subclause; the definition of this macro can be found as follows: + +Receive\_Open\_Ind see subclause 25.1. + +Any call completion SS process in the GLR starts by the GLR receiving a MAP-OPEN service indication. If that service is successful, the GLR can handle call completion supplementary service indications from the VLR. Table 22.1/2 shows the co-ordinating process' reaction on receipt of specific call completion SS service indications from the VLR. After the relevant process is invoked, the received service indication is sent to that process. + +**Table 22.1/2: Relationship between received service indication and invoked process in the GLR** + +| Service indication received | Process invoked | +|------------------------------------|------------------------| +| MAP_REGISTER_CC_ENTRY_ind | REGISTER_CC_ENTRY_GLR | +| MAP_ERASE_CC_ENTRY_ind | ERASE_CC_ENTRY_GLR | + +After creation of the user process the Co-ordinator relays the messages between the MAP\_PM and the invoked process until a request or an indication for dialogue termination is received. + +The Call\_Completion Co-ordinator is shown in figure 22.1/2. + + + +**Process CC\_Coord\_GLR** 22.1.2(1) + +Figure 22.1/2: Coordinating process in the GLR to handle dialogue opened with the AC Call Completion Context + +Signals to/from the left are to/from the VLR via the MAP provider; signals to/from the right are to/from the child process + +``` + +graph TD + Start([ ]) --> Idle1([Idle]) + Idle1 -- "Receive_Open_ind" --> Wait[Wait_for_service_ind] + Wait -- OK --> Wait + Wait -- "Vr, Error" --> Idle2([Idle]) + Wait --> MR[MAP_REGISTER_CC_ENTRY_ind] + Wait --> ME[MAP_ERASE_CC_ENTRY_ind] + Wait --> MN[MAP_NOTICE_ind] + MR --> RCN[Register_CC_RNTRY_GLR] + RCN --> MR + ME --> ECN[Erase_CC_ENTRY_GLR] + ECN --> ME + MN --> MC[MAP_CLOSE_ind] + MC --> Idle3([Idle]) + MR --> RI1([Relay_Info]) + ME --> RI1 + RI1 --> FP[FROM PROVIDER] + RI1 --> FO[FROM OFFSPRING] + FP --> TOOFF1[TO OFFSPRING] + TOOFF1 --> RI2([Relay_Info]) + FO --> TOP1[TO PROVIDER] + TOP1 --> RI3([Relay_Info]) + FP --> NULL1([NULL]) + FO --> NULL2([NULL]) + FP --- MAPU[MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind] + FO --- MAPU2[MAP_U_ABORT_ind +MAP_CLOSE_ind] + +``` + +Flowchart for Process CC\_Coord\_GLR. The process starts at an oval, goes to an 'Idle' state (oval). It receives an 'Open\_ind' (rectangle) from the left, labeled 'Section 25.1'. From 'Open\_ind', an 'OK' path leads to 'Wait\_for\_service\_ind' (oval) and a 'Vr, Error' path leads to another 'Idle' state (oval). From 'Wait\_for\_service\_ind', three paths lead to 'MAP\_REGISTER\_CC\_ENTRY\_ind' (parallelogram), 'MAP\_ERASE\_CC\_ENTRY\_ind' (parallelogram), and 'MAP\_NOTICE\_ind' (parallelogram). 'MAP\_REGISTER\_CC\_ENTRY\_ind' leads to 'Register\_CC\_RNTRY\_GLR' (rectangle), which leads to 'MAP\_REGISTER\_CC\_ENTRY\_ind' (parallelogram). 'MAP\_ERASE\_CC\_ENTRY\_ind' leads to 'Erase\_CC\_ENTRY\_GLR' (rectangle), which leads to 'MAP\_ERASE\_CC\_ENTRY\_ind' (parallelogram). 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_ind' (diamond), which leads to an 'Idle' state (oval). Both 'MAP\_REGISTER\_CC\_ENTRY\_ind' and 'MAP\_ERASE\_CC\_ENTRY\_ind' lead to 'Relay\_Info' (oval). From 'Relay\_Info', the flow splits into two main branches. The left branch has a 'FROM PROVIDER' parallelogram leading to a 'TO OFFSPRING' parallelogram, which leads to 'Relay\_Info' (oval). The right branch has a 'FROM OFFSPRING' parallelogram leading to a 'TO PROVIDER' parallelogram, which leads to 'Relay\_Info' (oval). There are also 'NULL' states (oval) and 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', 'MAP\_CLOSE\_ind' (rectangle) associated with these branches. + +Figure 22.1/2: Process\_CC\_Coord\_GLR + +## 22.2 Registration procedure + +### 22.2.1 General + +The registration procedure is used to register data related to a supplementary service in the HLR. The registration procedure is a fully transparent communication between the MS and the HLR. + +### 22.2.2 Procedures in the GLR + +#### Supplementary service registration + +When receiving the MAP\_REGISTER\_SS indication from VLR, the MAP user in the GLR transfers the information to the HLR in the MAP\_REGISTER\_SS request without checking the contents of the service indication. + +The GLR then awaits the receipt of the MAP\_REGISTER\_SS confirm from the HLR. The MAP user in the GLR shall transfer the information contained in this primitive to the VLR in the MAP\_REGISTER\_SS response without checking its contents. + +#### Error handling + +If at any time during this procedure a MAP\_P\_ABORT, MAP\_U\_ABORT, MAP\_NOTICE or unexpected MAP\_CLOSE indication is received from the VLR concerning the process, a MAP\_U\_ABORT request indicating application procedure cancellation is sent to the HLR (if a connection exists). If a MAP\_NOTICE indication was received from the VLR, that dialogue must be closed by sending a MAP\_CLOSE request towards the VLR. The process is terminated. + +If a MAP\_P\_ABORT, MAP\_U\_ABORT or MAP\_CLOSE indication is received from the HLR, a MAP\_U\_ABORT request shall be sent to the VLR terminating the process. If a MAP\_NOTICE indication was received from the HLR, that dialogue must be closed by sending a MAP\_CLOSE request towards the HLR. The process terminates. + +The registration procedure in the GLR is shown in figure 22.2/1. + + + +### Process SS\_REGISTER\_GLR + +22.2.1\_1(2) + +Figure 22.2/1: Mobile Initiated registration of supplementary service in the GLR + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` +sequenceDiagram + participant MS as Mobile Station + participant VLR as VLR + participant HLR as HLR + + Note left of MS: NULL + MS->>VLR: MAP_REGISTER_SS_ind + VLR->>HLR: MAP_OPEN_req + Note right of MAP_OPEN_req: Including +- Destination reference = subscriber's IMSI +- Originating reference = GLR number + VLR->>MS: MAP_REGISTER_req + VLR->>MS: MAP_DELIMITER_req + MS->>VLR: Receive_Open_Confirm + Note right of Receive_Open_Confirm: Section 25.1 + MS->>VLR: OK + VLR->>MS: Wait_for_ss_cnf + MS->>VLR: Vr, Error + VLR->>MS: MAP_U_ABORT_req + Note right of VLR: MAP_NOTICE_ind + VLR->>HLR: MAP_CLOSE_req + Note right of MAP_CLOSE_req: [Crossed out] + Note right of HLR: MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind + Note right of MS: 1 +``` + +Sequence diagram for Process SS\_REGISTER\_GLR showing the interaction between a mobile station and the network (VLR/HLR). The process starts with NULL, followed by MAP\_REGISTER\_SS\_ind, MAP\_OPEN\_req (with Destination reference = subscriber's IMSI and Originating reference = GLR number), MAP\_REGISTER\_req, MAP\_DELIMITER\_req, and Receive\_Open\_Confirm (Section 25.1). From Receive\_Open\_Confirm, an 'OK' path leads to Wait\_for\_ss\_cnf and a 'Vr, Error' path leads to MAP\_U\_ABORT\_req. There is also a MAP\_NOTICE\_ind and MAP\_CLOSE\_req sequence with a cross-out. A box on the right lists MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, and MAP\_CLOSE\_ind. A connector '1' is shown. + +Figure 22.2/1 (sheet 1 of 2): Procedure SS\_Register\_GLR + + + +Process SS\_REGISTER\_GLR 22.2.1\_2(2) + +Figure 22.2/1: Mobile Initiated registration of supplementary service in the GLR + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` + +graph TD + Start([Wait_for_ss_cnf]) --> Input1[/MAP_REGISTER_ss_cnf/] + Input1 --> Decision1{MAP_P_ERROR} + Decision1 --|yes| Conn1((1)) + Decision1 --|no| Output1[/MAP_REGISTER_ss_rsp/] + Output1 --> Output2[/MAP_CLOSE_req/] + Output2 --> End1(X) + + Input1 --> Input2[\MAP_U_ABORT_ind +MAP_P_ABORT_ind/] + Input2 --> Output3[/MAP_CLOSE_req/] + Output3 --> Output4[/MAP_U_ABORT_req/] + Output4 --> End2(X) + + Input1 --> Input3[\MAP_NOTICE_ind/] + Input3 --> Output5[/MAP_CLOSE_req/] + Output5 --> Output6[/MAP_U_ABORT_req/] + Output6 --> End3(X) + + Input1 --> Input4[\MAP_NOTICE_ind/] + Input4 --> Output7[/MAP_CLOSE_req/] + Output7 --> Output8[/MAP_U_ABORT_req/] + Output8 --> End4(X) + + Input1 --> Input5[\MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind/] + Input5 --> End5(X) + +``` + +The SDL diagram depicts the 'Wait\_for\_ss\_cnf' state. Upon receiving 'MAP\_REGISTER\_ss\_cnf', several paths are possible. One path checks for 'MAP\_P\_ERROR'; if yes, it goes to connector 1; if no, it sends 'MAP\_REGISTER\_ss\_rsp' and 'MAP\_CLOSE\_req' to the VLR. Other paths handle abort and notice indications from the HLR ('MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', 'MAP\_NOTICE\_ind', 'MAP\_CLOSE\_ind'), resulting in 'MAP\_CLOSE\_req' and 'MAP\_U\_ABORT\_req' being sent to the VLR or HLR as appropriate, followed by process termination (X). + +SDL diagram for Process SS\_REGISTER\_GLR showing state transitions and signal exchanges between VLR, GLR, and HLR. + +**Figure 22.2/1 (sheet 2 of 2): Procedure SS\_Register\_GLR** + +## 22.3 Erasure procedure + +### 22.3.1 General + +The erasure procedure is used to erase data related to a supplementary service in the HLR. The erasure procedure is a fully transparent communication between the MS and the HLR. + +### 22.3.2 Procedures in the GLR + +The GLR procedures for erasure are identical to those specified for registration in subclause 22.2. The text and diagrams in subclause 22.2 apply with all references to registration changed to erasure. + +## 22.4 Activation procedure + +### 22.4.1 General + +The activation procedure is used to activate a supplementary service in the HLR. The activation procedure is a fully transparent communication between the MS and the HLR. + +### 22.4.2 Procedures in the GLR + +#### Supplementary service activation + +When receiving the MAP\_ACTIVATE\_SS indication, the MAP user in the GLR transfers the information to the HLR in the MAP\_ACTIVATE\_SS request without checking the contents of the service indication. + +The GLR may then receive the MAP\_GET\_PASSWORD indication. This information is transferred to the VLR in the MAP\_GET\_PASSWORD request. If a MAP\_GET\_PASSWORD confirm primitive is received from the VLR, the VLR initiates the MAP\_GET\_PASSWORD response towards the HLR. + +The GLR will receive the MAP\_ACTIVATE\_SS confirm from the HLR. The MAP user in the GLR shall transfer the information contained in this primitive to the VLR in the MAP\_ACTIVATE\_SS response without checking its contents. + +#### Error handling + +The handling of MAP\_P\_ABORT, MAP\_U\_ABORT, MAP\_NOTICE and unexpected MAP\_CLOSE in this procedure is identical to the handling in the Registration procedure in the GLR, see subclause 22.2 of the present document. + +The activation procedure in the GLR is shown in figure 22.4/1. + + + +### Process SS\_ACTIVATE\_GLR + +22.4.1\_1(2) + +Figure 22.4/1: Activation of supplementary service procedure in the GLR + +Signals to/from the left are to/from the VLR via the MAP provider; signals to/from the right are to/from the child process + +``` +graph TD; Start([ ]) --> NULL[NULL]; NULL --> MAP_ACTIVATE_SS_ind{MAP_ACTIVATE_SS_ind}; MAP_ACTIVATE_SS_ind --> MAP_OPEN_req{MAP_OPEN_req}; MAP_OPEN_req --> To_HLR["To HLR, Including
- Destination reference = subscriber's IMSI
- Originating reference = GLR number"]; To_HLR --> MAP_ACTIVATE_req{MAP_ACTIVATE_req}; MAP_ACTIVATE_req --> MAP_DELIMITER_req{MAP_DELIMITER_req}; MAP_DELIMITER_req --> Receive_Open_Confirm[Receive_Open_Confirm]; Receive_Open_Confirm --> Section_25_1[Section 25.1]; Receive_Open_Confirm -- OK --> Wait_for_ss_cnf[Wait_for_ss_cnf]; Receive_Open_Confirm -- Vr,Error --> Circle_1((1)); Circle_1 --> MAP_U_ABORT_req{MAP_U_ABORT_req}; MAP_U_ABORT_req --> End_X1[ ]; MAP_ACTIVATE_SS_ind --> MAP_NOTICE_ind{MAP_NOTICE_ind}; MAP_NOTICE_ind --> MAP_CLOSE_req{MAP_CLOSE_req}; MAP_CLOSE_req --> End_X2[ ]; MAP_NOTICE_ind --> MAP_U_ABORT_ind["MAP_U_ABORT_ind
MAP_P_ABORT_ind
MAP_CLOSE_ind"]; +``` + +Flowchart for Process SS\_ACTIVATE\_GLR. The process starts with an oval, followed by a 'NULL' block. It then branches into two parallel paths. The left path consists of 'MAP\_ACTIVATE\_SS\_ind', 'MAP\_OPEN\_req' (with a note: To HLR, Including - Destination reference = subscriber's IMSI, - Originating reference = GLR number), 'MAP\_ACTIVATE\_req', 'MAP\_DELIMITER\_req', and 'Receive\_Open\_Confirm' (linked to Section 25.1). From 'Receive\_Open\_Confirm', an 'OK' path leads to 'Wait\_for\_ss\_cnf' and a 'Vr,Error' path leads to a circle labeled '1'. The circle '1' leads to 'MAP\_U\_ABORT\_req', which ends with a crossed-out line. The right path consists of 'MAP\_NOTICE\_ind', 'MAP\_CLOSE\_req', and a box containing 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind'. 'MAP\_CLOSE\_req' also ends with a crossed-out line. + +Figure 22.4/1 (sheet 1 of 2): Procedure Activate\_SS\_GLR + + + +**Process SS\_ACTIVATE\_GLR** 22.4.1\_2(2) + +Figure 22.4/1: Activation of supplementary service procedure in the GLR + +Signals to/from the left are to/from the VLR via the MAP provider; signals to/from the right are to/from the child process + +``` + +graph TD + Start([Wait_for_ss_cnf]) --> RegisterLeft[MAP_REGISTER_SS_cnf] + RegisterLeft --> PError{MAP_P_ERROR} + PError -- yes --> Connector1((1)) + PError -- no --> RegisterRight[MAP_REGISTER_SS_rsp] + RegisterRight --> CloseLeft[MAP_CLOSE_req] + CloseLeft --> EndLeft[✗] + Connector1 --> AbortInd[MAP_U_ABORT_ind +MAP_P_ABORT_ind] + AbortInd --> NoticeRight[MAP_NOTICE_ind] + NoticeRight --> CloseRight[MAP_CLOSE_req] + CloseRight --> EndRight[✗] + AbortInd --> GetPassword[GET_PASSWORD_GLR] + GetPassword --> Section22_10[Section 22.10] + GetPassword -- OK --> WaitRight([Wait_for_ss_cnf]) + GetPassword -- NULL --> EndRight2[✗] + +``` + +Flowchart for Process SS\_ACTIVATE\_GLR. The process starts with 'Wait\_for\_ss\_cnf'. It then sends 'MAP\_REGISTER\_SS\_cnf' to the left. A decision 'MAP\_P\_ERROR' follows. If 'yes', it goes to connector '1'. If 'no', it receives 'MAP\_REGISTER\_SS\_rsp' from the left, then sends 'MAP\_CLOSE\_req' to the left, which ends with a crossed-out symbol. If 'MAP\_P\_ERROR' is 'no', it also receives 'MAP\_NOTICE\_ind' from the right, then sends 'MAP\_CLOSE\_req' to the right, which ends with a crossed-out symbol. A return path from connector '1' leads to a box with 'MAP\_U\_ABORT\_ind' and 'MAP\_P\_ABORT\_ind'. From this box, the flow goes to 'MAP\_NOTICE\_ind' on the right, then 'MAP\_CLOSE\_req' on the right, which ends with a crossed-out symbol. Another path from the box leads to 'GET\_PASSWORD\_GLR' on the right, which is linked to 'Section 22.10'. 'GET\_PASSWORD\_GLR' has two outputs: 'OK' leads to 'Wait\_for\_ss\_cnf', and 'NULL' ends with a crossed-out symbol. + +Figure 22.4/1 (sheet 2 of 2): Procedure SS\_Activate\_GLR + +## 22.5 Deactivation procedure + +### 22.5.1 General + +The deactivation procedure is used to deactivate a supplementary service in the HLR. The deactivation procedure is a fully transparent communication between the MS and the HLR. + +### 22.5.2 Procedures in the GLR + +The GLR procedures for deactivation are identical to those specified for activation in subclause 22.4. The text and diagrams in subclause 22.4 apply with all references to activation changed to deactivation. + +## 22.6 Interrogation procedure + +### 22.6.1 General + +The interrogation procedure is used to retrieve information related to a supplementary service from the VLR or the HLR. The interrogation procedure in the GLR is a fully transparent communication between the VLR and the HLR. + +### 22.6.2 Procedures in the GLR + +The GLR procedures for interrogation are identical to those specified for registration in subclause 22.2. The text and diagrams in subclause 22.2 apply with all references to registration changed to interrogation. + +## 22.7 Password registration procedure + +### 22.7.1 General + +The password registration procedure is used to register a password in the HLR. The password registration procedure is a fully transparent communication between the MS and the HLR. + +### 22.7.2 Procedures in the GLR + +The password registration procedure in the GLR is identical to that for activation specified in subclause 22.4. All the text and diagrams in subclause 22.4 apply with all references to activation changed to password registration. + +## 22.8 Mobile Initiated USSD procedure + +### 22.8.1 Procedures in the GLR + +The initiation of the process is shown in subclause 22.1. + +In the case that a GLR is located between the VLR and the HLR, the Mobile Initiated USSD procedure in the GLR is a fully transparent communication between the VLR and the HLR. + +When receiving the MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST indication from VLR, the MAP user in the GLR transfers the information to the HLR in the MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST request without checking the contents of the service indication. + +The GLR may subsequently receive one or more MAP\_UNSTRUCTURED\_SS\_REQUEST or MAP\_UNSTRUCTURED\_SS\_NOTIFY indications from the HLR. These shall be sent transparently to the VLR. When a confirmation is received from the VLR this shall be returned to the HLR. + +When the GLR receives a MAP\_PROCESS\_UNSTRUCTURED\_SS\_REQUEST confirmation from the HLR then it shall pass this to the VLR and closes the MAP provider service. + +#### Error Handling + +Both the VLR and the HLR may initiate release of the MAP service at any time. This is handled as shown in the diagrams. + +The procedure in the HLR is shown in figure 22.8/1. + + + +### Process MS\_INIT\_USSD\_GLR + +22.8.1\_1(2) + +Figure 22.8/1: Handling of mobile initiated USSD at GLR. + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` +graph TD; NULL1(NULL) --> RO1[Receive_Open_ind]; RO1 --- S25_1_1[Section25.1]; RO1 -- OK --> WS[Wait_for_service_ind]; RO1 -- "Vr, Error" --> NULL2(NULL); WS --> MPRI{MAP_PROCESS_UNSTD_SS_REQUEST_ind}; MPRI --> MR{MAP_NOTICE_ind}; MR --> MC{MAP_CLOSE_ind}; MC --> MA[MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind]; MPRI --> MO{MAP_OPEN_req}; MO --- MO_info["-Destination reference = subscriber's IMSI +-Originating reference = GLR number"]; MO --> MPQR{MAP_PROCESS_UNSTD_SS_REQUEST_req}; MPQR --> MD{MAP_DELIMITER_req}; MD --> RO2[Receive_Open_cnf]; RO2 --- S25_1_2[Section25.1]; RO2 -- OK --> WP[Wait_for_pussd_cnf]; RO2 -- Vr --> MUAR{MAP_U_ABORT_req}; RO2 -- Error --> SU["Set UE= System Failure"]; SU --> MPRESP{MAP_PROCESS_UNSTD_SS_REQUEST_rsp}; MPRESP --> NULL3(NULL); +``` + +Flowchart for Process MS\_INIT\_USSD\_GLR. The process starts with NULL, followed by Receive\_Open\_ind (Section25.1). It then branches based on OK (Wait\_for\_service\_ind) or Vr, Error (NULL). The main path involves MAP\_PROCESS\_UNSTD\_SS\_REQUEST\_ind, MAP\_OPEN\_req (with Destination reference = subscriber's IMSI and Originating reference = GLR number), MAP\_PROCESS\_UNSTD\_SS\_REQUEST\_req, MAP\_DELIMITER\_req, and Receive\_Open\_cnf (Section25.1). From Receive\_Open\_cnf, it branches based on OK (Wait\_for\_pussd\_cnf), Vr (MAP\_U\_ABORT\_req), or Error (Set UE= System Failure). The Error path leads to MAP\_PROCESS\_UNSTD\_SS\_REQUEST\_rsp and NULL. There is also a branch for MAP\_NOTICE\_ind, MAP\_CLOSE\_ind, and signals MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, and MAP\_CLOSE\_ind. + +Figure 22.8/1 (sheet 1 of 2): Procedure MI\_USSD\_GLR + + + +**Process MS\_INIT\_USSD\_GLR** 22.8.1\_2(2) + +Figure 22.8/1: Handling of mobile initiated USSD at GLR. + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` + +graph TD + Start([Wait_for_pussd_cnf]) --> P1[MAP_PROCESS_UNSTD_SS_REQUEST_cnf] + Start --> P2[MAP_UNSTD_SS_NOTIFY_ind] + Start --> P3[MAP_UNSTD_SS_REQUEST_ind] + Start --> P4[MS_Receive_Error_at_GLR] + + P1 --> D1{MAP_P_ERROR} + D1 -- no --> P1R[MAP_PROCESS_UNSTD_SS_REQUEST_rsp] + D1 -- yes --> U1[MAP_U_ABORT_req] + P1R --> C1[MAP_CLOSE_req] + U1 --> U2[MAP_U_ABORT_req] + C1 --> NULL1([NULL]) + + P2 --> D2{MAP_UNSTD_SS_NOTIFY_req} + D2 --> DEL2[MAP_DELIMITER_req] + DEL2 --> W2([Wait_for_ussdn_cnf]) + W2 --> N2[MAP_UNSTD_SS_NOTIFY_cnf] + N2 --> R2[MAP_UNSTD_SS_NOTIFY_rsp] + R2 --> DEL3[MAP_DELIMITER_req] + DEL3 --> W3([Wait_for_pussd_cnf]) + + P3 --> D3{MAP_UNSTD_SS_REQUEST_req} + D3 --> DEL4[MAP_DELIMITER_req] + DEL4 --> W4([Wait_for_ussdn_cnf]) + W4 --> N3[MAP_UNSTD_SS_REQUEST_cnf] + N3 --> R3[MAP_UNSTD_SS_REQUEST_rsp] + R3 --> DEL5[MAP_DELIMITER_req] + DEL5 --> W5([Wait_for_pussd_cnf]) + + P4 --> NULL2([NULL]) + +``` + +Flowchart for Process MS\_INIT\_USSD\_GLR showing four main signal paths: MAP\_PROCESS\_UNSTD\_SS\_REQUEST\_cnf, MAP\_UNSTD\_SS\_NOTIFY\_ind, MAP\_UNSTD\_SS\_REQUEST\_ind, and MS\_Receive\_Error\_at\_GLR. Each path leads to various processing steps including error handling, delimiter processing, and waiting for confirmations. + +Figure 22.8/1 (sheet 2 of 2): Procedure MI\_USSD\_GLR + + + +### Macrodefinition MS\_Receive\_Error\_at\_GLR + +22.8.2(1) + +Figure 22.8/2: Handling of error at GLR for MS initiated USSD + +Signals to/from the left +are to/from the VLR +signals to/from the right +are to/from the HLR +unless otherwise stated + +``` + +stateDiagram-v2 + [*] --> Wait_for_cnf + state "Wait_for_cnf" as Wait_for_cnf + + %% Path 1: MAP_CLOSE_ind from HLR + Wait_for_cnf --> MAP_CLOSE_ind_HLR : MAP_CLOSE_ind (from right) + state "MAP_CLOSE_ind" as MAP_CLOSE_ind_HLR + MAP_CLOSE_ind_HLR --> MAP_CLOSE_req_VLR : MAP_CLOSE_req (to left) + state "MAP_CLOSE_req" as MAP_CLOSE_req_VLR + MAP_CLOSE_req_VLR --> End1 + state " " as End1 + + %% Path 2: Abort from HLR + Wait_for_cnf --> Abort_HLR : MAP_U_ABORT_ind / MAP_P_ABORT_ind (from right) + state "MAP_U_ABORT_ind\nMAP_P_ABORT_ind" as Abort_HLR + Abort_HLR --> MAP_NOTICE_ind_VLR : MAP_NOTICE_ind (to left) + state "MAP_NOTICE_ind" as MAP_NOTICE_ind_VLR + MAP_NOTICE_ind_VLR --> MAP_CLOSE_req_HLR : MAP_CLOSE_req (to right) + state "MAP_CLOSE_req" as MAP_CLOSE_req_HLR + MAP_CLOSE_req_HLR --> MAP_U_ABORT_req_VLR : MAP_U_ABORT_req (to left) + state "MAP_U_ABORT_req" as MAP_U_ABORT_req_VLR + MAP_U_ABORT_req_VLR --> End2 + state " " as End2 + + %% Path 3: MAP_NOTICE_ind from HLR + Wait_for_cnf --> MAP_NOTICE_ind_HLR : MAP_NOTICE_ind (from right) + state "MAP_NOTICE_ind" as MAP_NOTICE_ind_HLR + MAP_NOTICE_ind_HLR --> MAP_CLOSE_req_HLR2 : MAP_CLOSE_req (to right) + state "MAP_CLOSE_req" as MAP_CLOSE_req_HLR2 + MAP_CLOSE_req_HLR2 --> MAP_U_ABORT_req_VLR2 : MAP_U_ABORT_req (to left) + state "MAP_U_ABORT_req" as MAP_U_ABORT_req_VLR2 + MAP_U_ABORT_req_VLR2 --> End3 + state " " as End3 + + %% Path 4: Signals from VLR + Wait_for_cnf --> Signals_VLR : MAP_U_ABORT_ind / MAP_P_ABORT_ind / MAP_CLOSE_ind (from left) + state "MAP_U_ABORT_ind\nMAP_P_ABORT_ind\nMAP_CLOSE_ind\nFrom VLR" as Signals_VLR + Signals_VLR --> End4 + state " " as End4 + +``` + +SDL diagram for Macro MS\_Receive\_Error\_at\_GLR showing signal handling between VLR and HLR. + +**Figure 22.8/2: Macro MS\_Receive\_ERROR\_at\_GLR** + +## 22.9 Network initiated USSD procedure + +### 22.9.1 Procedure in the GLR + +In the case that a GLR is located between the VLR and the HLR, the Network initiated USSD procedure in the GLR is a fully transparent communication between the VLR and the HLR. + +The procedure may be invoked by the HLR. It may start by using either the MAP\_UNSTRUCTURED\_SS\_REQUEST or MAP\_UNSTRUCTURED\_SS\_NOTIFY service. + +The GLR may subsequently receive one or more MAP\_UNSTRUCTURED\_SS\_REQUEST\_ind or MAP\_UNSTRUCTURED\_SS\_NOTIFY\_ind indications from the VLR. These shall be sent transparently to the HLR. When a confirmation is received from the HLR this shall be returned to the VLR. + +When the GLR receives a MAP\_CLOSE\_ind from the HLR then it shall pass this to the VLR and close the MAP dialogue. + +#### **Error Handling** + +Both the VLR and the HLR may initiate release of the MAP service at any time. This is handled as shown in the diagrams. + +The Network initiated USSD procedure in the GLR is shown in figure 22.9/1. + + + +### Process NW\_INIT\_USSD\_GLR + +22.9.1\_1(2) + +Figure 22.9/1: Handling of network initiated USSD at GLR. + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` +graph TD + NULL1(NULL) --> Receive_Open_ind[Receive_Open_ind] + Receive_Open_ind --- Section25_1_1[Section 25.1] + Receive_Open_ind --> Wait_for_service_ind((Wait_for_service_ind)) + Wait_for_service_ind -- OK --> MAP_UNSTD_SS_NOTIFY_req{MAP_UNSTD_SS_NOTIFY_req} + Wait_for_service_ind -- Vr, Error --> NULL2(NULL) + MAP_UNSTD_SS_NOTIFY_req --> MAP_OPEN_req1{MAP_OPEN_req} + MAP_UNSTD_SS_NOTIFY_req --> MAP_UNSTD_SS_REQUEST_ind{MAP_UNSTD_SS_REQUEST_ind} + MAP_UNSTD_SS_REQUEST_ind --> MAP_OPEN_req2{MAP_OPEN_req} + MAP_OPEN_req1 --> MAP_UNSTD_SS_NOTIFY_req + MAP_OPEN_req2 --> MAP_UNSTD_SS_REQUEST_req{MAP_UNSTD_SS_REQUEST_req} + MAP_UNSTD_SS_REQUEST_req --> Junction(( )) + Junction --> MAP_CLOSE_req{MAP_CLOSE_req} + Junction --> AbortCloseBox[MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind] + MAP_CLOSE_req --> NULL3(NULL) + MAP_CLOSE_req --> Junction + MAP_UNSTD_SS_NOTIFY_req --> MAP_DELIMITER_req{MAP_DELIMITER_req} + MAP_DELIMITER_req --> Receive_Open_cnf[Receive_Open_cnf] + Receive_Open_cnf --- Section25_1_2[Section 25.1] + Receive_Open_cnf -- OK --> Wait_for_ussdn_cnf((Wait_for_ussdn_cnf)) + Receive_Open_cnf -- Vr, Error --> MAP_U_ABORT_req{MAP_U_ABORT_req} + Wait_for_ussdn_cnf --> NULL4(NULL) + MAP_U_ABORT_req --> NULL4 +``` + +Flowchart for Process NW\_INIT\_USSD\_GLR. The process starts with NULL, followed by Receive\_Open\_ind (Section 25.1). It then enters a Wait\_for\_service\_ind state. From there, it branches based on OK (leading to MAP\_UNSTD\_SS\_NOTIFY\_req) or Vr, Error (leading to NULL). The MAP\_UNSTD\_SS\_NOTIFY\_req leads to MAP\_OPEN\_req, which leads to MAP\_UNSTD\_SS\_NOTIFY\_req. The MAP\_UNSTD\_SS\_NOTIFY\_req leads to MAP\_DELIMITER\_req, which leads to Receive\_Open\_cnf (Section 25.1). From Receive\_Open\_cnf, it branches based on OK (leading to Wait\_for\_ussdn\_cnf) or Vr, Error (leading to MAP\_U\_ABORT\_req). Both Wait\_for\_ussdn\_cnf and MAP\_U\_ABORT\_req lead to NULL. There is also a branch from Wait\_for\_service\_ind to MAP\_UNSTD\_SS\_REQUEST\_ind, which leads to MAP\_OPEN\_req, which leads to MAP\_UNSTD\_SS\_REQUEST\_req. The MAP\_UNSTD\_SS\_REQUEST\_req leads to a junction point. From this junction point, it branches to MAP\_CLOSE\_req (which leads to NULL) and to a box containing MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, and MAP\_CLOSE\_ind. The MAP\_CLOSE\_req also leads to the junction point. + +Figure 22.9/1 (sheet 1 of 2): Procedure NI\_USSD\_GLR + + + +### Process NW\_INIT\_USSD\_GLR + +22.9.1\_2(2) + +Figure 22.9/1: Handling of network initiated USSD at GLR. + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` +graph TD; Start([Wait_for_pussd_cnf]) --> Ind1{MAP_UNSTD_SS_NOTIFY_ind}; Start --> Ind2{MAP_UNSTD_SS_REQUEST_ind}; Start --> Error1[NW_Receive_Error_at_GLR]; Ind1 --> Req1{MAP_UNSTD_SS_NOTIFY_req}; Req1 --> Delim1{MAP_DELIMITER_req}; Delim1 --> Wait1([Wait_for_ussdn_cnf]); Wait1 --> Cnf1{MAP_UNSTD_SS_NOTIFY_cnf}; Cnf1 --> Rsp1{MAP_UNSTD_SS_NOTIFY_rsp}; Rsp1 --> Delim2{MAP_DELIMITER_req}; Delim2 --> Wait2([Wait_for_pussd_cnf]); Ind2 --> Req2{MAP_UNSTD_SS_REQUEST_req}; Req2 --> Delim3{MAP_DELIMITER_req}; Delim3 --> Wait3([Wait_for_ussdn_cnf]); Wait3 --> Cnf2{MAP_UNSTD_SS_REQUEST_cnf}; Cnf2 --> Rsp2{MAP_UNSTD_SS_REQUEST_rsp}; Rsp2 --> Delim4{MAP_DELIMITER_req}; Delim4 --> Wait4([Wait_for_pussd_cnf]); Error1 --> NULL1([NULL]); Cnf1 --> Error2[NW_Receive_Error_at_GLR]; Error2 --> NULL2([NULL]); Cnf2 --> Error3[NW_Receive_Error_at_GLR]; Error3 --> NULL3([NULL]); +``` + +Flowchart for Process NW\_INIT\_USSD\_GLR. It starts with 'Wait\_for\_pussd\_cnf' and branches into three main paths based on incoming signals: MAP\_UNSTD\_SS\_NOTIFY\_ind, MAP\_UNSTD\_SS\_REQUEST\_ind, and NW\_Receive\_Error\_at\_GLR. The first path involves MAP\_UNSTD\_SS\_NOTIFY\_req, MAP\_DELIMITER\_req, and Wait\_for\_ussdn\_cnf, leading to a decision on MAP\_UNSTD\_SS\_NOTIFY\_cnf. The second path involves MAP\_UNSTD\_SS\_REQUEST\_req, MAP\_DELIMITER\_req, and Wait\_for\_ussdn\_cnf, leading to a decision on MAP\_UNSTD\_SS\_REQUEST\_cnf. The third path leads to NULL. Both decision points have 'NULL' error paths. + +Figure 22.9/1 (sheet 2 of 2): Procedure NI\_USSD\_GLR + + + +### Macrodefinition NW\_Receive\_Error\_at\_GLR + +22.9.2(1) + +Figure 22.9/2: Handling of error at GLR for NW initiated USSD + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` +stateDiagram-v2 + [*] --> Wait_for_cnf + state "Wait_for_cnf" as Wait_for_cnf + state "MAP_CLOSE_ind" as MAP_CLOSE_ind + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "MAP_U_ABORT_ind" as MAP_U_ABORT_ind + state "MAP_P_ABORT_ind" as MAP_P_ABORT_ind + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "MAP_U_ABORT_req" as MAP_U_ABORT_req + state "MAP_NOTICE_ind (From VLR)" as MAP_NOTICE_ind + state "MAP_U_ABORT_ind (From VLR)" as MAP_U_ABORT_ind + state "MAP_P_ABORT_ind (From VLR)" as MAP_P_ABORT_ind + state "MAP_CLOSE_ind (From VLR)" as MAP_CLOSE_ind + state "MAP_CLOSE_req (From VLR)" as MAP_CLOSE_req + state "MAP_U_ABORT_req (From VLR)" as MAP_U_ABORT_req + + Wait_for_cnf --> MAP_CLOSE_ind + MAP_CLOSE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> [*] + + Wait_for_cnf --> Merge1 + state "Merge1" as Merge1 + Merge1 --> MAP_U_ABORT_ind + Merge1 --> MAP_P_ABORT_ind + MAP_U_ABORT_ind --> MAP_NOTICE_ind + MAP_P_ABORT_ind --> MAP_NOTICE_ind + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> MAP_U_ABORT_req + MAP_U_ABORT_req --> [*] + + Merge2 --> MAP_NOTICE_ind + state "Merge2" as Merge2 + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> MAP_U_ABORT_req + MAP_U_ABORT_req --> [*] + + Note right of MAP_U_ABORT_ind: MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind +From VLR +``` + +State transition diagram for Macrodefinition NW\_Receive\_Error\_at\_GLR. The diagram shows two main paths. The left path starts with a start symbol, followed by 'Wait\_for\_cnf', then 'MAP\_CLOSE\_ind', 'MAP\_CLOSE\_req', and an end symbol. The right path starts from the 'Wait\_for\_cnf' state, goes through a merge point, then 'MAP\_U\_ABORT\_ind' and 'MAP\_P\_ABORT\_ind' (from the right), then 'MAP\_NOTICE\_ind', 'MAP\_CLOSE\_req', 'MAP\_U\_ABORT\_req', and an end symbol. A second part of the diagram shows 'MAP\_NOTICE\_ind' (from the right), a merge point, 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind' (all from the VLR), then 'MAP\_CLOSE\_req', 'MAP\_U\_ABORT\_req', and an end symbol. + +Figure 22.9/2: Marco NW\_Receive\_Rrror\_at\_GLR + +## 22.10 Common macros for clause 22 + +### 22.10.1 SS Password handling macros + +Macro Get\_Password\_GLR + +This macro is used by the GLR to relay a request for password from the HLR to the VLR, and to relay a response from the VLR back to the HLR. The macro is described in figure 22.10/1. + + + +**Macrodefinition GET\_PASSWORD\_GLR** 22.10.1(1) + +Figure 22.10/1: Macro which relay a GET Password request from the HLR to the VLR and relay a GET Password response from the VLR to the HLR + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` + +graph TD + Start([ ]) --> MAP_GET_PASSWORD_ind[MAP_GET_PASSWORD_ind] + MAP_GET_PASSWORD_ind --> MAP_GET_PASSWORD_req{MAP_GET_PASSWORD_req} + MAP_GET_PASSWORD_req --> MAP_DELIMITER_req1{MAP_DELIMITER_req} + MAP_DELIMITER_req1 --> Wait[Wait_for_password] + Wait --> Entry(( )) + Entry --> MAP_GET_PASSWORD_cnf[MAP_GET_PASSWORD_cnf] + Entry --> AbortInd[MAP_U_ABORT_ind +MAP_P_ABORT_ind] + Entry --> NoticeInd[MAP_NOTICE_ind] + MAP_GET_PASSWORD_cnf --> MAP_GET_PASSWORD_rsp[MAP_GET_PASSWORD_rsp] + MAP_GET_PASSWORD_rsp --> MAP_DELIMITER_req2{MAP_DELIMITER_req} + MAP_DELIMITER_req2 --> OK([OK]) + AbortInd --> NULL1((NULL)) + NoticeInd --> MAP_CLOSE_req1{MAP_CLOSE_req} + MAP_CLOSE_req1 --> MAP_U_ABORT_req1{MAP_U_ABORT_req} + MAP_U_ABORT_req1 --> NULL2((NULL)) + NULL2 --> FinalInd[MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind] + FinalInd --> NoticeInd2[MAP_NOTICE_ind] + NoticeInd2 --> MAP_CLOSE_req2{MAP_CLOSE_req} + MAP_CLOSE_req2 --> MAP_U_ABORT_req2{MAP_U_ABORT_req} + MAP_U_ABORT_req2 --> NULL3((NULL)) + +``` + +Flowchart for Macro GET\_PASSWORD\_GLR. The process starts with an oval connector, followed by MAP\_GET\_PASSWORD\_ind (VLR to GLR), MAP\_GET\_PASSWORD\_req (GLR to VLR), and MAP\_DELIMITER\_req (GLR to VLR). A 'Wait\_for\_password' state follows. A loop then begins: MAP\_GET\_PASSWORD\_cnf (VLR to GLR) leads to MAP\_GET\_PASSWORD\_rsp (GLR to VLR), which leads to MAP\_DELIMITER\_req (GLR to VLR), ending at an 'OK' connector. From the loop entry point, two other paths exist: one leading to a box with MAP\_U\_ABORT\_ind and MAP\_P\_ABORT\_ind, which then leads to a 'NULL' connector; the other leading to MAP\_NOTICE\_ind (VLR to GLR), then MAP\_CLOSE\_req (GLR to VLR), then MAP\_U\_ABORT\_req (GLR to VLR), ending at a 'NULL' connector. From the 'NULL' connector, a path leads to a box with MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, and MAP\_CLOSE\_ind, which then leads to MAP\_NOTICE\_ind (VLR to GLR), then MAP\_CLOSE\_req (GLR to VLR), then MAP\_U\_ABORT\_req (GLR to VLR), ending at another 'NULL' connector. + +Figure 22.10/1: Macro Get\_PW\_GLR + +## 22.11 Activation of a CCBS request + +### 22.11.1 General + +The Activation of a CCBS request procedure in the GLR is a fully transparent communication between the VLR and the HLR. + +### 22.11.2 Procedure in the GLR + +When receiving the MAP\_REGISTER\_CC\_ENTRY indication from VLR, the MAP user in the GLR transfers the information to the HLR in the MAP\_REGISTER\_CC\_ENTRY request without checking the contents of the service indication. + +When the GLR receives a MAP\_REGISTER\_CC\_ENTRY confirmation from the HLR then it shall pass this to the VLR and closes the MAP provider service. + +The activation of a CCBS request procedure in the GLR is shown in figure 22.11/1. + + + +### Process Register\_CC\_Entry\_GLR + +22.11.1\_1(2) + +Figure 22.11/1: Handling of Register\_CC\_Entry at GLR + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` +sequenceDiagram + participant Start(( )) + participant NULL[NULL] + participant MAP_REGISTER_CC_ENTRY_ind{MAP REGISTER_CC_ENTRY_ind} + participant MAP_OPEN_req{MAP OPEN_req} + participant HLR[HLR] + participant MAP_REGISTER_CC_ENTRY_req{MAP REGISTER_CC_ENTRY_req} + participant MAP_DELIMITER_req{MAP DELIMITER_req} + participant Receive_Open_Confirm[Receive_Open_Confirm] + participant Wait_for_cnf{Wait_for_cnf} + participant MAP_U_ABORT_req{MAP U_ABORT_req} + participant End(( )) + Note right of HLR: To HLR, Including +- Destination reference = subscriber's IMSI +- Originating reference = GLR number + Note right of Receive_Open_Confirm: Section 25.1 + Note right of Wait_for_cnf: 1 + + Start->>NULL: + NULL->>MAP_REGISTER_CC_ENTRY_ind: + MAP_REGISTER_CC_ENTRY_ind->>MAP_OPEN_req: + MAP_OPEN_req->>HLR: + HLR-->>MAP_REGISTER_CC_ENTRY_req: + MAP_REGISTER_CC_ENTRY_req->>MAP_DELIMITER_req: + MAP_DELIMITER_req->>Receive_Open_Confirm: + Receive_Open_Confirm-->>Wait_for_cnf: OK + Note right of Wait_for_cnf: 1 + Note right of Wait_for_cnf: Vr, Error + Wait_for_cnf->>MAP_U_ABORT_req: + MAP_U_ABORT_req->>End: +``` + +The sequence diagram illustrates the interaction for processing a Register\_CC\_Entry at the GLR. It begins with an initial node leading to a NULL state. The process then enters a loop waiting for a MAP\_REGISTER\_CC\_ENTRY\_ind signal. Upon receiving it, a MAP\_OPEN\_req is sent to the HLR, which includes the destination reference (subscriber's IMSI) and the originating reference (GLR number). The HLR responds with a MAP\_REGISTER\_CC\_ENTRY\_req, which is followed by a MAP\_DELIMITER\_req. The GLR then receives a confirmation (Receive\_Open\_Confirm) from the HLR. If the response is 'OK', the process moves to a 'Wait\_for\_cnf' state. If the response is 'Vr, Error', the process moves to a 'MAP\_U\_ABORT\_req' state. A callout 'Section 25.1' is associated with the 'Receive\_Open\_Confirm' step. A callout '1' is associated with the 'Wait\_for\_cnf' state. A callout box on the right indicates that signals to/from the left are to/from the VLR, and signals to/from the right are to/from the HLR, unless otherwise stated. A list of possible signals (MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, MAP\_CLOSE\_ind) is shown on the right side of the diagram. + +Sequence diagram for Process Register\_CC\_Entry\_GLR + +Figure 22.11/1 (sheet 1 of 2): Process Register\_CC\_Entry\_GLR + + + +**Process Register\_CC\_Entry\_GLR** 22.11.1\_2(2) + +Figure 22.11/1: Handling of Register\_CC\_Entry at GLR + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` + +sequenceDiagram + participant VLR + participant GLR + Note left of GLR: Wait_for_cnf + GLR->>VLR: MAP_REGISTER_CC_ENTRY_cnf + VLR-->>GLR: MAP_P_ERROR + alt yes: Connector 1 + alt no: + GLR->>VLR: MAP_REGISTER_CC_ENTRY_rsp + GLR->>VLR: MAP_CLOSE_req + Note right of GLR: HLR signals + HLR->>GLR: MAP_U_ABORT_ind + HLR->>GLR: MAP_P_ABORT_ind + GLR->>VLR: MAP_NOTICE_ind + GLR->>VLR: MAP_CLOSE_req + Note right of GLR: HLR signals + HLR->>GLR: MAP_U_ABORT_ind + HLR->>GLR: MAP_P_ABORT_ind + HLR->>GLR: MAP_CLOSE_ind + GLR->>VLR: MAP_NOTICE_ind + GLR->>VLR: MAP_CLOSE_req + GLR->>VLR: MAP_U_ABORT_req + Note right of GLR: End + +``` + +Sequence diagram for Process Register\_CC\_Entry\_GLR. The process starts with 'Wait\_for\_cnf' and sends 'MAP\_REGISTER\_CC\_ENTRY\_cnf' to the VLR. The VLR responds with 'MAP\_P\_ERROR' (yes leads to connector 1, no leads to 'MAP\_REGISTER\_CC\_ENTRY\_rsp'). The GLR then sends 'MAP\_CLOSE\_req' to the VLR. Simultaneously, the HLR sends 'MAP\_U\_ABORT\_ind' and 'MAP\_P\_ABORT\_ind' to the GLR. The GLR then sends 'MAP\_NOTICE\_ind' and 'MAP\_CLOSE\_req' to the VLR. Finally, the HLR sends 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind' to the GLR, which then sends 'MAP\_NOTICE\_ind', 'MAP\_CLOSE\_req', and 'MAP\_U\_ABORT\_req' to the VLR. The process ends with an 'X' mark. + +Figure 22.11/1 (sheet 2 of 2): Process Register\_CC\_Entry\_GLR + +## 22.12 Deactivation of a CCBS request + +### 22.12.1 General + +The Deactivation of a CCBS request procedure in the GLR is a fully transparent communication between the VLR and the HLR. + +### 22.12.2 Procedure in the GLR + +When receiving the MAP\_ERASE\_CC\_ENTRY indication from VLR, the MAP user in the GLR transfers the information to the HLR in the MAP\_ERASE\_CC\_ENTRY request without checking the contents of the service indication. + +When the GLR receives a MAP\_ERASE\_CC\_ENTRY confirmation from the HLR then it shall pass this to the VLR and closes the MAP provider service. + +The deactivation of a CCBS request procedure in the GLR is shown in figure 22.12/1. + + + +### Process Erase\_CC\_Entry\_GLR + +22.12.1\_1(2) + +Figure 22.12/1: Handling of Erase\_CC\_Entry at GLR + +Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + +``` +sequenceDiagram + participant NULL + participant GLR + participant VLR + participant HLR + + Note right of HLR: Signals to/from the left are to/from the VLR +signals to/from the right are to/from the HLR +unless otherwise stated + + NULL-->>GLR: NULL + GLR->>VLR: MAP_ERASE_CC_ENTRY_ind + GLR->>HLR: MAP_OPEN_req + Note right of HLR: Including +- Destination reference = subscriber's IMSI +- Originating reference = GLR number + GLR->>VLR: MAP_ERASE_CC_ENTRY_req + GLR->>VLR: MAP_DELIMITER_req + GLR->>GLR: Receive_Open_Confirm + Note right of GLR: Section 25.1 + GLR-->>VLR: OK + GLR-->>GLR: Wait_for_cnf + GLR-->>VLR: Vr, Error + Note right of VLR: 1 + GLR->>HLR: MAP_NOTICE_ind + GLR->>GLR: MAP_CLOSE_req + Note right of GLR: X + Note right of HLR: MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind +``` + +Sequence diagram for Process Erase\_CC\_Entry\_GLR. The process starts with NULL, followed by MAP\_ERASE\_CC\_ENTRY\_ind. It then sends MAP\_OPEN\_req (with Destination reference = subscriber's IMSI and Originating reference = GLR number), MAP\_ERASE\_CC\_ENTRY\_req, and MAP\_DELIMITER\_req. It receives a Confirm (Section 25.1). From the Confirm, an OK path leads to Wait\_for\_cnf, and a Vr, Error path leads to MAP\_U\_ABORT\_req (marked with an X). The MAP\_ERASE\_CC\_ENTRY\_ind also leads to MAP\_NOTICE\_ind, which leads to MAP\_CLOSE\_req (marked with an X). A box on the right lists MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, and MAP\_CLOSE\_ind. A connector '1' is shown near the error path. + +Figure 22.12/1 (sheet 1 of 2): Process Erase\_CC\_Entry\_GLR + + + +Process Erase\_CC\_Entry\_GLR + +22.12.1\_2(2) + +Figure 22.12/1: Handling of Erase\_CC\_Entry at GLR + +Signals to/from the left +are to/from the VLR +signals to/from the right +are to/from the HLR +unless otherwise stated + +``` + +graph TD + Start([Wait_for_cnf]) --> Input1[MAP_REGISTER_CC_ENTRY_cnf] + Input1 --> Decision1{MAP_P_ERROR} + Decision1 -- yes --> Connector1((1)) + Decision1 -- no --> Output1[MAP_REGISTER_CC_ENTRY_rsp] + Output1 --> Output2[MAP_CLOSE_req] + Output2 --> End1[X] + + Start --> Input2[MAP_U_ABORT_ind +MAP_P_ABORT_ind] + Input2 --> Output3[MAP_CLOSE_req] + Output3 --> Output4[MAP_U_ABORT_req] + Output4 --> End2[X] + + Start --> Input3[MAP_NOTICE_ind] + Input3 --> Output3 + + Start --> Input4[MAP_NOTICE_ind] + Input4 --> Output5[MAP_CLOSE_req] + Output5 --> Output6[MAP_U_ABORT_req] + Output6 --> End3[X] + + Start --> Input5[MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind] + Input5 --> End3 + +``` + +SDL Diagram for Process Erase\_CC\_Entry\_GLR + +Figure 22.12/1 (sheet 2 of 2): Process Erase\_CC\_Entry\_GLR + +# 23 Short message service procedures + +## 23.1 General + +The short message service procedures are used to control both mobile originated and mobile terminated short message transfer. + +Four procedures exist for short message services (see 29.002) but only the following two procedures are involved in the GLR and the IM-MSC: + +- mobile terminated short message service transfer; +- short message alert procedure. + +## 23.2 The mobile terminated short message transfer procedure + +The mobile terminated short message transfer procedure is used for forwarding a short message or several short messages from a Service Centre to a mobile subscriber. This subclause includes the description of the procedures in the IM-MSC and the GLR. The procedures in the other existing entities are entirely the same as in the network without the GLR and are described in 29.002. + +### 23.2.1 Procedure in the Intermediate MSC + +When initiating the dialogue with the IM-MSC, the SMS Gateway MSC must provide the IMSI of the subscriber to whom the short message is directed. + +The IMSI can be included either in the Destination Reference of the MAP\_OPEN indication received from the SMS Gateway MSC or in the sm-RP-DA information field of the MAP\_MT\_FORWARD\_SHORT\_MESSAGE indication. + +When receiving a MAP\_OPEN indication primitive that is not associated with any MAP service indication primitive and if the dialogue is accepted, the MAP service-user in the IM-MSC issues a MAP\_DELIMITER request primitive in order to trigger the local MAP service-provider to confirm the dialogue. + +When receiving the first MAP\_MT\_FORWARD\_SHORT\_MESSAGE indication from the gateway MSC, the IM-MSC retrieves the E.164 Number of the servicing MSC from the GLR if the MAP service primitive is accepted. + +The MAP\_MT\_FORWARD\_SHORT\_MESSAGE indication primitive is checked by the macro "Check\_Indication". If the received MAP service primitive contains errors, the service is aborted and an unexpected data value error or data missing error is returned to the GMSC. + +The subscriber identity information that may be included in the MAP\_OPEN indication primitive and in the MAP service indication primitive is checked by the macro "Check\_Subscr\_Identity\_For\_MT\_SMS" as follows. + +If a Destination Reference has been received in the MAP\_OPEN indication, an LMSI must be present in the sm-RP-DA information field of the MAP\_MT\_FORWARD\_SHORT\_MESSAGE indication. The LMSI shall be key information for retrieving the MSC Number in the GLR. + +Otherwise, if the IMSI is included in the sm-RP-DA information field of the MAP\_MT\_FORWARD\_SHORT\_MESSAGE indication, it is used to retrieve the MSC Number in the GLR. + +If: + +a Destination Reference has been received in the IM-MSC and the sm-RP-DA information field of the MAP\_MT\_FORWARD\_SHORT\_MESSAGE indication does not include an LMSI, or + +no Destination Reference has been received and the sm-RP-DA information field does not cover an IMSI; + +the service is aborted in the IM-MSC and the error "Unexpected Data Value" is returned to the SMS GMSC. + +The interaction between the IM- MSC and the GLR for the MSC Number retrieval is described in 3GPP TS 23.119 GLR-stage2. + +If the IM- MSC is successfully retrieves the MSC Number it initiates the forward short message procedure to the servicing MSC. The presence of the Destination Reference in the MAP\_OPEN request and the LMSI or IMSI in the first MAP\_MT\_FORWARD\_SHORT\_MESSAGE request follows the message received from the GMSC. The More Messages To Send flag is set to TRUE or FALSE depending on the information received from the GMSC. + +If the grouping of MAP\_OPEN request and MAP\_MT\_FORWARD\_SHORT\_MESSAGE request together would need segmenting, these primitives must not be grouped together. The MAP\_OPEN request primitive is sent first without any associated MAP service request primitive and the dialogue confirmation must be received before the MAP\_MT\_FORWARD\_SHORT\_MESSAGE request is sent. + +As a response to the procedure, the IM- MSC will receive the MAP\_MT\_FORWARD\_SHORT\_MESSAGE confirmation indicating: + +- a successful forwarding of the short message. This indication is passed to the GMSC; +- unsuccessful forwarding of the short message. This indication is passed to the GMSC. + +The IM- MSC informs the delivery failure to the GLR, if an absent subscriber\_SM, an unidentified subscriber or SM delivery failure with error cause MS memory capacity exceeded indication is received from the servicing MSC. That enables the GLR set the MNRF. The interaction between the IM- MSC and the GLR regarding the procedure is described in 3GPP TS 23.119 GLR-stage2. + +Unexpected data value, system failure errors and other errors are simply passed to the GMSC. + +If the More Messages To Send flag was TRUE in the MAP\_MT\_FORWARD\_SHORT\_MESSAGE request and the previous short message transfer succeeded, then the IM- MSC awaits the next short message. + +When receiving the next short message from the GMSC, the IM- MSC sets the More Messages To Send flag according to the information received and starts the service MAP\_MT\_FORWARD\_SHORT\_MESSAGE again. + +If the More Messages To Send flag was FALSE or the service MAP\_MT\_FORWARD\_SHORT\_MESSAGE ends unsuccessfully, the transaction to the gateway MSC is terminated. + +The mobile terminated short message transfer procedure in the IM- MSC is shown in figure 23.2/1 and 23.2/2. + + + +### Process MT\_SM\_Transfer\_IMMSC + +23.2.1\_1(3) + +Figure 23.2/1: The mobile terminated short message service in the IM-MSC + +Signals to/from the left are to/from the SMS-GMSC; signals to/from the right are to/from the MSC + +``` +graph TD; Start([ ]) --> NULL1(NULL); NULL1 --> Receive_Open_ind[Receive_Open_ind]; Receive_Open_ind --- Section_25_1[Section 25.1]; Receive_Open_ind -- OK --> Dest_Ref_received{Dest_Ref_received}; Dest_Ref_received -- no --> NULL2(NULL); Dest_Ref_received -- yes --> Store_Destination_Reference[Store_Destination_Reference]; Store_Destination_Reference --> WAIT_FOR_SERVICE_PRIMITIVE1(WAIT_FOR_SERVICE_PRIMITIVE); Dest_Ref_received -- Error --> NULL3(NULL); WAIT_FOR_SERVICE_PRIMITIVE1 --> MAP_DELIMITER_ind1[MAP_DELIMITER_ind]; WAIT_FOR_SERVICE_PRIMITIVE1 --> MAP_MT_FORWARD_SHORT_MESSAGE_ind[MAP_MT_FORWARD_SHORT_MESSAGE_ind]; WAIT_FOR_SERVICE_PRIMITIVE1 --> MAP_U_ABORT_ind[MAP_U_ABORT_ind]; WAIT_FOR_SERVICE_PRIMITIVE1 --> MAP_P_ABORT_ind[MAP_P_ABORT_ind]; WAIT_FOR_SERVICE_PRIMITIVE1 --> MAP_CLOSE_ind[MAP_CLOSE_ind]; WAIT_FOR_SERVICE_PRIMITIVE1 --> MAP_NOTICE_ind[MAP_NOTICE_ind]; MAP_DELIMITER_ind1 --> MAP_DELIMITER_req[MAP_DELIMITER_req]; MAP_DELIMITER_req --> WAIT_FOR_SERVICE_PRIMITIVE2(WAIT_FOR_SERVICE_PRIMITIVE); MAP_MT_FORWARD_SHORT_MESSAGE_ind --> Check_Indication[Check_Indication]; Check_Indication --- Section_25_2[Section 25.2]; Check_Indication -- ok --> MT_SM_IM-MSC[MT_SM_IM-MSC]; MT_SM_IM-MSC --- Figure_23_2_2[Figure 23.2/2]; MT_SM_IM-MSC -- error --> UnlabeledBox1[ ]; MT_SM_IM-MSC -- ok --> More_msg_to_sent{More_msg_to_sent}; More_msg_to_sent -- yes --> UnlabeledBox2[ ]; More_msg_to_sent -- no --> UnlabeledBox3[ ]; More_msg_to_sent -- error --> UnlabeledBox1; UnlabeledBox2 --> MAP_MT_FORWARD_SHORT_MESSAGE_rsp1[MAP_MT_FORWARD_SHORT_MESSAGE_rsp]; UnlabeledBox2 --> MAP_DELIMITER_req2[MAP_DELIMITER_req]; MAP_DELIMITER_req2 --> WAIT_FOR_MORE_MESSAGES(WAIT_FOR_MORE_MESSAGES); UnlabeledBox3 --> MAP_MT_FORWARD_SHORT_MESSAGE_rsp2[MAP_MT_FORWARD_SHORT_MESSAGE_rsp]; UnlabeledBox3 --> MAP_CLOSE_req[MAP_CLOSE_req]; MAP_CLOSE_req --> NULL4(NULL); MAP_U_ABORT_ind --> NULL5(NULL); MAP_P_ABORT_ind --> NULL5; MAP_CLOSE_ind --> NULL5; MAP_NOTICE_ind --> MAP_CLOSE_ind2[MAP_CLOSE_ind]; MAP_CLOSE_ind2 --> NULL6(NULL); +``` + +Flowchart for Process MT\_SM\_Transfer\_IMMSC. The process starts with an oval, leading to a 'NULL' state, then 'Receive\_Open\_ind' (linked to Section 25.1). A decision 'Dest\_Ref\_received' follows: 'OK' leads to 'Store\_Destination\_Reference' then 'WAIT\_FOR\_SERVICE\_PRIMITIVE'; 'no' leads to 'NULL'; 'Error' leads to 'NULL'. From 'WAIT\_FOR\_SERVICE\_PRIMITIVE', four paths emerge: 1) 'MAP\_DELIMITER\_ind' -> 'MAP\_DELIMITER\_req' -> 'WAIT\_FOR\_SERVICE\_PRIMITIVE'; 2) 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ind' -> 'Check\_Indication' (linked to Section 25.2) -> 'MT\_SM\_IM-MSC' (linked to Figure 23.2/2) -> 'More\_msg\_to\_sent' decision; 3) A group of 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind' -> 'NULL'; 4) 'MAP\_NOTICE\_ind' -> 'MAP\_CLOSE\_ind' -> 'NULL'. From 'More\_msg\_to\_sent': 'yes' leads to an unlabeled box -> 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' / 'MAP\_DELIMITER\_req' -> 'WAIT\_FOR\_MORE\_MESSAGES'; 'no' leads to an unlabeled box -> 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' / 'MAP\_CLOSE\_req' -> 'NULL'. 'error' paths from 'MT\_SM\_IM-MSC' and 'More\_msg\_to\_sent' lead to the unlabeled box before the final 'NULL' state. + +Figure 23.2/1 (sheet1 of 3): Procedure\_MT\_SM\_Transfer\_IM-MSC + + + +### Process MT\_SM\_Transfer\_IMMSC + +23.2.1\_2(3) + +Figure 23.2/1: The mobile terminated short message service in the IM-MSC + +``` +graph TD; Start([WAIT_FOR_MORE_MESSAGES]) --> Ind{MAP_MT_FORWARD_SHORT_MESSAGE_ind}; Ind --> CheckInd[Check Indication]; CheckInd -- Section 25.2; CheckInd -- ok --> Req[MAP_MT_FORWARD_SHORT_MESSAGE_req
MAP_DELIMITER_req]; Req --> WaitConfirm([WAIT_FOR_MT_SMS_CONFIRM]); WaitConfirm --> Cnf{MAP_MT_FORWARD_SHORT_MESSAGE_cnf}; Cnf --> CheckCnf[Check Confirmation]; CheckCnf -- Section 25.2; CheckCnf -- ok --> MoreMsg{More msg to_sent}; MoreMsg -- yes --> Start; MoreMsg -- no --> Rsp1[MAP_MT_FORWARD_SHORT_MESSAGE_rsp
MAP_DELIMITER_req]; CheckCnf -- Data error --> Failure{Inform SM Delivery Failure}; CheckCnf -- User error --> Absent{Absent Subscriber?}; Absent -- yes --> Failure; Failure -- to GLR Application Process in TS23.119; Failure --> Rsp2[MAP_MT_FORWARD_SHORT_MESSAGE_rsp
MAP_CLOSE_req]; Rsp1 --> End([NULL]); Rsp2 --> End; +``` + +Flowchart for Process MT\_SM\_Transfer\_IMMSC. The process starts with 'WAIT\_FOR\_MORE\_MESSAGES', followed by 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ind'. It then checks the indication (Section 25.2). If 'ok', it sends 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_req' and 'MAP\_DELIMITER\_req', then waits for 'MT\_SMS\_CONFIRM'. Upon receiving 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_cnf', it checks the confirmation (Section 25.2). From the confirmation check, if 'ok', it checks 'More msg to\_sent'. If 'yes', it loops back to 'WAIT\_FOR\_MORE\_MESSAGES'. If 'no', it sends 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' and 'MAP\_DELIMITER\_req'. If 'Data error' or 'User error' (specifically 'Absent Subscriber?'), it sends 'Inform SM Delivery Failure' to the GLR Application Process in TS23.119. Finally, it sends 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' and 'MAP\_CLOSE\_req' to reach a 'NULL' state. + +Figure 23.2/1 (sheet 2 of 3): Procedure MT\_SM\_Transfer\_IM-MSC + +#### Process MT\_SM\_Transfer\_IMMSC + +23.2.1\_3(3) + +Figure 23.2/1: The mobile terminated short message service in the IM-MSC + + + +The sequence diagram illustrates the 'Process MT\_SM\_Transfer\_IMMSC' procedure. It begins with an initial state (oval) leading to a wait state containing 'WAIT\_FOR\_MORE\_MESSAGES' and 'WAIT\_FOR\_MT\_SMS\_CONFIRM'. The process then enters a loop. First, it checks for incoming messages from the SMS-GMSC. If 'MAP\_U\_ABORT\_ind' or 'MAP\_P\_ABORT\_ind' is received, it sends a 'MAP\_U\_ABORT\_req' to the VMSC and ends (cross). If 'MAP\_NOTICE\_ind' is received from the SMS-GMSC, it sends a 'MAP\_CLOSE\_req' to the SMS-GMSC. The diagram then shows a transition to interactions with the VMSC. It receives 'MAP\_NOTICE\_ind' from the VMSC and sends a 'MAP\_CLOSE\_req' to the VMSC. Simultaneously, it receives 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'fMAP\_CLOSE\_ind' from the VMSC. Finally, it sends a 'MAP\_U\_ABORT\_req' to the SMS-GMSC and ends (cross). + +``` +sequenceDiagram + participant IM-MSC + participant SMS-GMSC + participant VMSC + + Note right of IM-MSC: WAIT_FOR_MORE_MESSAGES +WAIT_FOR_MT_SMS_CONFIRM + Note left of IM-MSC: MAP_U_ABORT_ind +MAP_P_ABORT_ind +from SMS-GMSC + Note right of IM-MSC: MAP_NOTICE_ind +from SMS-GMSC + Note right of IM-MSC: MAP_CLOSE_req +to SMS-GMSC + Note right of IM-MSC: MAP_U_ABORT_req +to VMSC + Note left of IM-MSC: MAP_NOTICE_ind +from VMSC + Note right of IM-MSC: MAP_CLOSE_req +to VMSC + Note right of IM-MSC: MAP_U_ABORT_ind +MAP_P_ABORT_ind +fMAP_CLOSE_ind +from VMSC + Note right of IM-MSC: MAP_U_ABORT_req +to SMS-GMSC +``` + +Sequence diagram for Process MT\_SM\_Transfer\_IMMSC showing interactions between IM-MSC, SMS-GMSC, and VMSC. + +Figure 23.2/1 (sheet 3 of 3): Procedure MT\_SM\_Transfer\_IM-MSC + + + +### Macrodefinition MT\_SM\_IMMSC + +23.2.2\_1(2) + +Figure 23.2/2: Macro which transfer short message PDUs to VMSC in the IM-MSC + +Signals to/from the right are to/from the MSC + +``` +graph TD; Start([ ]) --> Obtain[Obtain MSC Number]; Obtain --> GLR[to GLR Application Process in TS23.119]; Obtain --> Wait[WAIT_FOR_RESPONSE]; Wait --> Response[RESPONSE]; Response --> GLR_R[from GLR Application Process in TS23.119]; Response --> Obtained{MSC Number Obtained?}; Obtained -- no --> UserError[User Error = Unidentified User]; UserError --> ERR1((ERR OR)); Obtained -- yes --> Segmenting{Message segmenting needed?}; Segmenting -- no --> Merge1(( )); Merge1 --> OpenReq1[MAP_OPEN_req +MAP_MT_FORWARD_SHORT_MESSAGE_req +MAP_DELIMITER_req]; OpenReq1 --> OpenCnf1[Receive_Open_Cnf]; OpenCnf1 -- ok --> WaitConfirm1[WAIT_FOR_MT_SMS_CONFIRM]; OpenCnf1 -- error --> SystemFailure[Error = System Failure]; SystemFailure --> ERR2((ERR OR)); Segmenting -- yes --> OpenReq2[MAP_OPEN_req +MAP_DELIMITER_req]; OpenReq2 --> OpenCnf2[Receive_Open_Cnf]; OpenCnf2 -- ok --> Merge2(( )); OpenCnf2 -- error --> SystemFailure; Merge2 --> OpenReq3[MAP_MT_FORWARD_SHORT_MESSAGE_req +MAP_DELIMITER_req]; OpenReq3 --> WaitConfirm2[WAIT_FOR_MT_SMS_CONFIRM]; WaitConfirm1 --> Merge3(( )); WaitConfirm2 --> Merge3; Merge3 --> Cnf[MAP_MT_FORWARD_SHORT_MESSAGE_Cnf]; Cnf --> Page2((1 page2)); +``` + +Flowchart for Macro MT\_SM\_IMMSC. The process starts with a connector, followed by 'Obtain MSC Number' (to GLR Application Process in TS23.119), 'WAIT\_FOR\_RESPONSE', and 'RESPONSE' (from GLR Application Process in TS23.119). A decision 'MSC Number Obtained?' follows. If 'no', it goes to 'User Error = Unidentified User' and then 'ERR OR'. If 'yes', it goes to 'Message segmenting needed?'. If 'no', it goes to a merge point and then 'MAP\_OPEN\_req', 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_req', 'MAP\_DELIMITER\_req', 'Receive\_Open\_Cnf', and 'WAIT\_FOR\_MT\_SMS\_CONFIRM'. If 'yes', it goes to 'MAP\_OPEN\_req', 'MAP\_DELIMITER\_req', 'Receive\_Open\_Cnf', a merge point, 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_req', 'MAP\_DELIMITER\_req', 'WAIT\_FOR\_MT\_SMS\_CONFIRM'. Both 'WAIT\_FOR\_MT\_SMS\_CONFIRM' paths lead to a merge point, then 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_Cnf', and finally '1 page2'. + +Figure 23.2/2 (sheet1 of 2): Macro MT\_SM\_IM-MSC + + + +**Macrodefinition MT\_SM\_IMMSC** **23.2.2\_2(2)** + +Figure 23.2/2: Macro which transfer short message PDUs to VMSC in the IM-MSC + +``` +graph TD; Start((1 page1)) --> Check[Check Confirmation]; Check --- Section[Section 25.2]; Check -- ok --> OK((OK)); Check -- User Error --> Absent{Absent Subscriber?}; Check -- "Provider Error Data Error" --> ERR[ERR OR]; Absent -- yes --> Inform[Inform SM Delivery Failure]; Inform --- GLR[to GLR Application Process in TS 23.119]; Inform --> ERR; Absent -- no --> ERR; +``` + +Flowchart for Macro MT\_SM\_IMMSC. It starts at connector '1 page1', goes to 'Check Confirmation' (linked to Section 25.2). From there, three paths emerge: 'ok' leads to 'OK' connector; 'User Error' leads to 'Absent Subscriber?' decision; 'Provider Error Data Error' leads to 'ERR OR' connector. From 'Absent Subscriber?', 'yes' leads to 'Inform SM Delivery Failure' (linked to 'to GLR Application Process in TS 23.119'), which then leads to 'ERR OR'; 'no' leads directly to 'ERR OR'. + +**Figure 23.2/2 (sheet2 of 2): Macro MT\_SM\_IM-MSC** + +### 23.2.2 Procedure in the GLR + +When initiating the dialogue with the GLR, the SMS Gateway MSC must provide the IMSI of the subscriber to whom the short message is directed. + +The IMSI is included in the sm-RP-DA information field of the MAP\_MT\_FORWARD\_SHORT\_MESSAGE indication. + +When receiving a MAP\_OPEN indication primitive that is not associated with any MAP service indication primitive and if the dialogue is accepted, the MAP service-user in the GLR issues a MAP\_DELIMITER request primitive in order to trigger the local MAP service-provider to confirm the dialogue. + +When receiving the first MAP\_MT\_FORWARD\_SHORT\_MESSAGE indication from the gateway MSC, the GLR performs some subscriber data checks, if the MAP service primitive is accepted. + +The MAP\_MT\_FORWARD\_SHORT\_MESSAGE indication primitive is checked by the macro "Check\_Indication". If the received MAP service primitive contains errors, the service is aborted and an unexpected data value error or data missing error is returned to the GMSC. + +The subscriber identity information that is included in the MAP service indication primitive is checked by the macro "Check\_Subscr\_Identity\_For\_MT\_SMS" as follows: + +If the IMSI is included in the sm-RP-DA information field of the MAP\_MT\_FORWARD\_SHORT\_MESSAGE indication, the MAP\_OPEN indication received from the gateway MSC shall not include a Destination Reference. + +If no Destination Reference has been received and the sm-RP-DA information field does not cover an IMSI the service is aborted in the GLR and the error "Unexpected Data Value" is returned to the GMSC. + +The following outcomes from the subscriber data checks can occur in GLR: + +- if the mobile subscriber is unknown, the unidentified subscriber error is forwarded to the GMSC; +- if the "Confirmed by HLR" indicator is set to "Not Confirmed", the unidentified subscriber error is forwarded to the GMSC. + +If the mobile subscriber is known and "Confirmed by HLR" indicator is set to "Confirmed", the GLR shall successfully retrieves the SGSN Number. + +If the GLR is successfully retrieves the SGSN Number it initiates the forward short message procedure to the SGSN. The IMSI is included in the sm-RP-DA information field of the MAP\_MT\_FORWARD\_SHORT\_MESSAGE request. More Messages To Send flag is set to TRUE or FALSE depending on the information received from the GMSC. + +If the grouping of MAP\_OPEN request and MAP\_MT\_FORWARD\_SHORT\_MESSAGE request together would need segmenting, these primitives must not be grouped together. The MAP\_OPEN request primitive is sent first without any associated MAP service request primitive and the dialogue confirmation must be received before the MAP\_MT\_FORWARD\_SHORT\_MESSAGE request is sent. + +As a response to the procedure, the GLR will receive the MAP\_MT\_FORWARD\_SHORT\_MESSAGE confirmation indicating: + +- a successful forwarding of the short message. This indication is passed to the GMSC; +- unsuccessful forwarding of the short message. This indication is passed to the GMSC. + +The GLR sets MNRG, if an absent subscriber\_SM (except for the case that absent subscriber reason is PurgedMS), an unidentified subscriber or SM delivery failure with error cause MS memory capacity exceeded indication is received from the SGSN. + +If the GLR receives an absent subscriber\_SM and absent subscriber reason is PurgedMS, the GLR deletes the subscriber data for the user. + +Unexpected data value, system failure errors and other errors are simply passed to the GMSC. + +If the More Messages To Send flag was TRUE in the MAP\_MT\_FORWARD\_SHORT\_MESSAGE request and the previous short message transfer succeeded, then the GLR awaits the next short message. + +When receiving the next short message from the GMSC, the GLR sets the More Messages To Send flag according to the information received and starts the service MAP\_MT\_FORWARD\_SHORT\_MESSAGE again. + +If the More Messages To Send flag was FALSE or the service MAP\_MT\_FORWARD\_SHORT\_MESSAGE ends unsuccessfully, the transaction to the gateway MSC is terminated. + +The mobile terminated short message transfer procedure in the GLR is shown in figure 23.2/3 and 23.2/4. + + + +### Process MT\_SM\_Transfer\_GLR + +23.2.3\_1(3) + +Figure 23.2/3: The mobile terminated short message service in the GLR + +Signals to/from the left are to/from the SMS-GMSC; +signals to/from the right are to/from the SGSN + +Flowchart for Process MT\_SM\_Transfer\_GLR. The process starts with an oval, leading to a 'NULL' state. It then enters a 'Receive\_Open\_ind' block (Section 25.1). From here, an 'Error' path leads to another 'NULL' state. An 'OK' path leads to a 'Dest\_Ref\_received' decision. If 'no', it goes to 'NULL'. If 'yes', it goes to 'Store\_Destination\_Reference', then 'WAIT\_FOR\_SERVICE\_PRIMITIVE'. From 'WAIT\_FOR\_SERVICE\_PRIMITIVE', four paths emerge: 1) 'MAP\_DELIMITER\_ind' leads to 'MAP\_DELIMITER\_req' then 'WAIT\_FOR\_SERVICE\_PRIMITIVE'. 2) 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ind' leads to 'Check\_Indication' (Section 25.2). From 'Check\_Indication', an 'ok' path leads to 'MT\_SM\_GLR' (Figure 23.2/4), and an 'error' path leads to a junction. 3) A junction receives 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'MAP\_CLOSE\_ind'. 4) 'MAP\_NOTICE\_ind' leads to 'MAP\_CLOSE\_ind'. From 'MAP\_CLOSE\_ind', the path leads to 'NULL'. From the junction, an 'error' path leads to 'NULL', and a 'no' path leads to a junction. From this junction, two paths emerge: 1) 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' and 'MAP\_DELIMITER\_req' lead to 'WAIT\_FOR\_MORE\_MESSAGES'. 2) 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' and 'MAP\_CLOSE\_req' lead to 'NULL'. A 'More\_msg\_to\_sent' decision follows 'MT\_SM\_GLR'. If 'yes', it leads to a junction. If 'ok', it leads to the junction. If 'no', it leads to the junction. The junction also receives an 'error' path from 'MT\_SM\_GLR'. + +Figure 23.2/3 (sheet 1 of 3): Procedure MT\_SM\_Transfer\_GLR + + + +### Process MT\_SM\_Transfer\_GLR + +23.2.3\_2(3) + +Figure 23.2/3: The mobile terminated short message service in the GLR + +``` +graph TD; Start([WAIT FOR MORE MESSAGES]) --> Ind{MAP_MT_FORWARD_SHORT_MESSAGE_ind}; Ind --> CheckInd[Check Indication]; CheckInd -- Section 25.2; CheckInd -- ok --> Req[MAP_MT_FORWARD_SHORT_MESSAGE_req]; Req -- MAP_DELIMITER_req --> Confirm([WAIT_FOR_MT_SMS_CONFIRM]); Confirm --> Cnf{MAP_MT_FORWARD_SHORT_MESSAGE_cnf}; Cnf --> CheckConf[Check Confirmation]; CheckConf -- Section 25.2; CheckConf -- ok --> MoreMsg{More msg to_sent}; CheckConf -- "User error" --> Absent{Absent Subscriber?}; Absent -- yes --> setMNRG[set MNRG]; setMNRG --> CheckAbsent[Check Absent SubscriberSM In_GLR]; CheckAbsent -- See TS 23.119; Absent -- no --> Rsp1[MAP_MT_FORWARD_SHORT_MESSAGE_rsp]; Rsp1 -- MAP_CLOSE_req --> NULL1([NULL]); MoreMsg -- yes --> MoreMsgWait([WAIT FOR MORE MESSAGES]); MoreMsg -- no --> Rsp2[MAP_MT_FORWARD_SHORT_MESSAGE_rsp]; Rsp2 -- MAP_DELIMITER_req --> NULL2([NULL]); NULL1 --> NULL2; NULL2 --> NULL3([NULL]); +``` + +Flowchart for Process MT\_SM\_Transfer\_GLR. It starts with 'WAIT FOR MORE MESSAGES', followed by 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_ind', 'Check Indication' (Section 25.2), 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_req', 'MAP\_DELIMITER\_req', 'WAIT\_FOR\_MT\_SMS\_CONFIRM', 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_cnf', 'Check Confirmation' (Section 25.2). A decision diamond 'Absent Subscriber?' has 'yes' leading to 'set MNRG' then 'Check Absent SubscriberSM In\_GLR' (See TS 23.119), and 'no' leading to 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' and 'MAP\_CLOSE\_req'. Another decision diamond 'More msg to\_sent' has 'yes' leading to 'WAIT FOR MORE MESSAGES' and 'no' leading to 'MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_rsp' and 'MAP\_DELIMITER\_req'. Both paths lead to 'NULL'. + +Figure 23.2/3 (sheet 2 of 3): Procedure MT\_SM\_Transfer\_GLR + +#### Process MT\_SM\_Transfer\_GLR + +23.2.3\_3(3) + +Figure 23.2/3: The mobile terminated short message service in the GLR + + + +The sequence diagram illustrates the 'Process MT\_SM\_Transfer\_GLR' procedure. It begins with an initial state labeled 'WAIT\_FOR\_MORE\_MESSAGES' and 'WAIT\_FOR\_MT\_SMS\_CONFIRM'. The process then enters a loop. In the first part of the loop, the GLR receives 'MAP\_U\_ABORT\_ind' and 'MAP\_P\_ABORT\_ind' from the SMS-GMSC, sends a 'MAP\_NOTICE\_ind' to the SMS-GMSC, a 'MAP\_CLOSE\_req' to the SMS-GMSC, and a 'MAP\_U\_ABORT\_req' to the SGSN. This part of the loop ends with an 'X' mark. The second part of the loop involves the GLR receiving a 'MAP\_NOTICE\_ind' from the SGSN, sending a 'MAP\_CLOSE\_req' to the SGSN, and then sending 'MAP\_U\_ABORT\_ind', 'MAP\_P\_ABORT\_ind', and 'fMAP\_CLOSE\_ind' to the SGSN. This is followed by a 'MAP\_U\_ABORT\_req' to the SMS-GMSC, which also ends with an 'X' mark. The diagram uses standard UML notation: ovals for initial states, rectangles for message exchanges, diamonds for decision points, and 'X' marks for loop exits. + +Sequence diagram for Process MT\_SM\_Transfer\_GLR showing interactions between a GLR and an SGSN. + +Figure 23.2/3 (sheet 3 of 3): Procedure MT\_SM\_Transfer\_GLR + + + +### Macrodefinition MT\_SM\_GLR + +23.2.4\_1(2) + +Figure 23.2/4: Macro which transfer short message PDUs to SGSN in the GLR + +Signals to/from the right are to/from the SGSN + +``` +graph TD; Start([ ]) --> Sub{Subscriber known?}; Sub -- no --> UE[User Error = Unidentified User]; UE --> ERR1((ERR OR)); Sub -- yes --> Conf{Confirmed by HLR?}; Conf -- no --> Right(( )); Conf -- yes --> SGSN[Retrieve and set SGSN Number]; SGSN --> Seg{Message segmenting needed?}; Seg -- no --> P1[MAP_OPEN_req
MAP_MT_FORWARD_SHORT_MESSAGE_req
MAP_DELIMITER_req]; P1 --> ROCnf1[Receive_Open_Cnf]; ROCnf1 -- ok --> W1((WAIT_FOR_MT_SMS_CONFIRM)); ROCnf1 -- error --> SF[Error = System Failure]; SF --> ERR2((ERR OR)); Seg -- yes --> P2[MAP_OPEN_req
MAP_DELIMITER_req]; P2 --> ROCnf2[Receive_Open_Cnf]; ROCnf2 -- ok --> P3[MAP_MT_FORWARD_SHORT_MESSAGE_req
MAP_DELIMITER_req]; P3 --> W2((WAIT_FOR_MT_SMS_CONFIRM)); W1 -- ok --> CNF[MAP_MT_FORWARD_SHORT_MESSAGE_Cnf]; W2 -- ok --> CNF; CNF --> End((1 page2)); +``` + +Flowchart for Macro MT\_SM\_GLR. It starts with an oval connector, followed by 'Subscriber known?' (yes/no). 'no' leads to 'User Error = Unidentified User' and an 'ERR OR' circle. 'yes' leads to 'Confirmed by HLR?' (yes/no). 'no' leads to an arrow pointing right. 'yes' leads to 'Retrieve and set SGSN Number'. Then 'Message segmenting needed?' (yes/no). 'no' leads to a process block with MAP\_OPEN\_req, MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_req, and MAP\_DELIMITER\_req, then 'Receive\_Open\_Cnf', then 'WAIT\_FOR\_MT\_SMS\_CONFIRM' (ok/error). 'error' leads to 'Error = System Failure' and 'ERR OR'. 'ok' leads to a process block with MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_req and MAP\_DELIMITER\_req, then 'WAIT\_FOR\_MT\_SMS\_CONFIRM' (ok/error). Both 'ok' paths lead to a process block with MAP\_MT\_FORWARD\_SHORT\_MESSAGE\_Cnf, which then leads to a circle labeled '1 page2'. + +Figure 23.2/4 (sheet1 of 2): Macro MT\_SM\_GLR + +##### Macrodefinition MT\_SM\_GLR + +23.2.4\_2(2) + +Figure 23.2/4: Macro which transfer short message PDUs to SGSN in the GLR + + + +Flowchart for Macro MT\_SM\_GLR. It starts with '1 page1', followed by 'Check Confirmation' (linked to Section 25.2). A decision diamond 'Absent Subscriber?' follows. 'yes' leads to 'set MNRG' then 'Check\_Absent SubscriberSM\_in\_GLR' (linked to See TS 23.119). 'no' leads to 'ERR OR'. 'ok' from 'Check Confirmation' leads to 'OK'. 'User Error' from 'Check Confirmation' leads to 'ERR OR'. 'Provider Error Data Error' from 'set MNRG' leads to 'ERR OR'. + +Figure 23.2/4 (sheet2 of 2): Macro MT\_SM\_GLR + +## 23.3 The Short Message Alert procedure + +The Short Message Alert procedure is used for alerting the Service Centre when the mobile subscriber is active after a short message transfer has failed because the mobile subscriber is not reachable or when the MS has indicated that it has memory capacity to accept a short message. + +### 23.3.1 Procedures in the GLR + +When the GLR receives MAP\_READY\_FOR\_SM indication from the VLR or the SGSN and it has MNRF or MNRG, it sends MAP\_READY\_FOR\_SM request to the HLR. + +If the outcome is successful, the MNRF or MNRG is cleared. + +The short message alert procedure in the GLR is shown in figure 23.3/1. + + + +**Process SM\_Alert\_GLR** 23.3.1\_1(2) + +Figure 23.3/1: The short message alert process in the GLR + +Signals to/from the left are to/from the VLR/SGSN; signals to/from the right are to/from the HLR + +``` + +graph TD + Start([NULL]) --> RecOpen[Receive_Open_ind] + RecOpen --- Sec25_1_1[Section 25.1] + RecOpen -- ok --> WaitService((WAIT_FOR_SERVICE_PRIMITIVE_)) + RecOpen -- Error --> NULL1([NULL]) + WaitService --> MapReadyInd{MAP_READY_FOR_SM_ind} + MapReadyInd --- Sec25_2[Section 25.2] + MapReadyInd -- ok --> SubKnown{Subscriber known?} + SubKnown -- yes --> SendOpenReq[MAP_OPEN_req +MAP_READY_FOR_SM_req +MAP_DELIMITER_req] + SubKnown -- no --> SetUnknown[SET UE = UNKNOWN SUBSCRIBWR] + SubKnown -- error --> NULL2([NULL]) + SendOpenReq --> RecOpenCnf[Receive_Open_Cnf] + RecOpenCnf --- Sec25_1_2[Section 25.1] + RecOpenCnf -- ok --> SetFailure[SET UE = system failure] + RecOpenCnf -- error --> NULL3([NULL]) + SetFailure --> End1((1 page 2)) + SetUnknown --> NULL4([NULL]) + MapNoticeInd{MAP_NOTICE_ind} --> MapCloseReq[MAP_CLOSE_req] + MapCloseReq --> NULL5([NULL]) + MapUAbortInd[MAP_U_ABORT_ind +MAP_P_ABORT_ind +MAP_CLOSE_ind] --> NULL6([NULL]) + +``` + +Flowchart of Process SM\_Alert\_GLR. The process starts with NULL, then receives an Open indication (Section 25.1). If ok, it enters WAIT\_FOR\_SERVICE\_PRIMITIVE. From there, it checks for MAP\_READY\_FOR\_SM\_ind (Section 25.2). If ok, it checks if the subscriber is known. If yes, it sends MAP\_OPEN\_req, MAP\_READY\_FOR\_SM\_req, and MAP\_DELIMITER\_req to the HLR, receives an Open Confirmation (Section 25.1), and if ok, sets UE to system failure and ends at 1 page 2. If no, it sets UE to UNKNOWN SUBSCRIBWR and ends at NULL. If error, it ends at NULL. If MAP\_NOTICE\_ind is received, it sends a MAP\_CLOSE\_req to the HLR and ends at NULL. If MAP\_U\_ABORT\_ind, MAP\_P\_ABORT\_ind, or MAP\_CLOSE\_ind is received, it ends at NULL. + +Figure 23.3/1 (sheet 1 of 2): Process SM\_Alert\_GLR + + + +**Process SM\_Alert\_GLR** 23.3.1\_2(2) + +Figure 23.3/1: The short message alert process in the GLR + +``` +graph TD; Start((1 page1)) --> WF_RESULT([WF_RESULT]); WF_RESULT --> MAP_READY_FOR_SM_Cnf[MAP_READY_FOR_SM_Cnf]; MAP_READY_FOR_SM_Cnf --> CheckConfirmation[Check Confirmation]; CheckConfirmation --> MNRF_MNRG_Set{MNRF or MNRG set?}; CheckConfirmation -- error --> SET_USER_ERROR[SET USER ERROR]; MNRF_MNRG_Set -- ok --> REASON{REASON}; REASON -- no --> NULL[NULL]; REASON -- yes --> REASON_SUB{ }; REASON_SUB -- non-GPRS --> ClearMNRF[Clear MNRF]; REASON_SUB -- GPRS --> ClearMNRG[Clear MNRG]; ClearMNRF --> NULL; ClearMNRG --> NULL; SET_USER_ERROR --> NULL; +``` + +The flowchart illustrates the short message alert process in the GLR. It begins with a connector '1 page1', leading to a 'WF\_RESULT' symbol, followed by a 'MAP\_READY\_FOR\_SM\_Cnf' symbol. A 'Check Confirmation' block follows, with a reference to 'Section 25.2'. A decision diamond 'MNRF or MNRG set?' evaluates the confirmation. If 'ok', it proceeds to a 'REASON' decision diamond. If 'error', it goes to 'SET USER ERROR'. From 'REASON', if 'no', it ends at 'NULL'. If 'yes', it branches based on 'non-GPRS' (leading to 'Clear MNRF') or 'GPRS' (leading to 'Clear MNRG'). Both 'Clear MNRF' and 'Clear MNRG' lead to a merge point before the final output symbols 'MAP\_READY\_FOR\_SM\_rsp' and 'MAP\_CLOSE\_req', which then lead to the 'NULL' end symbol. + +Flowchart of Process SM\_Alert\_GLR + +Figure 23.3/1 (sheet 2 of 2): Process SM\_Alert\_GLR + +# 24 GPRS process description + +## 24.1 General + +The MAP GPRS procedures are used for the Network Requested PDP-Context Activation procedures. + +The stage 2 specification for Packet Switched Service involving GLR is in 3GPP TS 23.119. + +## 24.2 Send Routing Information procedure + +### 24.2.1 Process in the GLR for Send Routing Information for GPRS + +The MAP process in the GLR to provide routing information for a network-requested PDP context activation is shown in figure 24.2/1. The MAP process invokes a macro not defined in this subclause; the definition of this macro can be found as follows: + +- Receive\_Open\_Ind see subclause 25.1; +- Check\_Indication see subclause 25.2. + +#### Successful outcome + +When the MAP process receives a MAP\_OPEN indication with the application context gprsLocationInfoRetrieval, it checks it by invoking the macro Receive\_Open\_Ind. + +If the macro takes the OK exit, the MAP process waits for a service indication. + +If a MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS service indication is received, the GLR sends a Send Routing Info For Gprs request to the GPRS application process in the GLR, and wait for a response. The Send Routing Info For Gprs request contains the parameter received in the MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS service indication. + +If the GPRS application process in the GLR returns a positive response containing the routing information, the MAP process constructs a MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS service response containing the routing info, constructs a MAP\_CLOSE service request, sends them to the IM-GSN and returns to the idle state. + +#### Negative response from GLR GPRS application process + +If the GPRS application process in the GLR returns a negative response, the MAP process constructs a MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS service response containing the appropriate error, constructs a MAP\_CLOSE service request, sends them to the IM-GSN and returns to the idle state. + +#### Failure of dialogue opening with the IM-GSN + +If the macro Receive\_Open\_Ind takes the Vr exit or the Error exit, the MAP process returns to the idle state. + +If the MAP provider sends a MAP\_P\_ABORT while the MAP process is waiting for a service indication, the MAP process returns to the idle state. + +If the MAP provider sends a MAP\_NOTICE while the MAP process is waiting for a service indication, the MAP process sends a MAP\_CLOSE request to terminate the dialogue and returns to the idle state. + + + +### Process Send\_Routing\_Info\_For\_Gprs\_GLR + +24.2.1(1) + +Figure 24.2/1: The Send Routing Info For Gprs process in the GLR + +Signals to/from the right are to/from the GPRS application process + + + +``` + + graph TD + Start([ ]) --> Idle1([Idle]) + Idle1 --> RecOpen[/Receive Open_Ind/] + RecOpen --- Sec251[Section 25.1] + RecOpen -- OK --> WaitSvc([Wait_For_Service_Indication]) + RecOpen -- "Vr, Error" --> Idle2([Idle]) + + WaitSvc --> AbortInd[/MAP_P_ABORT_ind/] + WaitSvc --> SendRInfoInd[/MAP_SEND_ROUTING_INFO_FOR_GPRS_ind/] + WaitSvc --> NoticeInd[/MAP_NOTICE_ind/] + WaitSvc --> SendRInfoInt{{Send Routing Info For Gprs}} + + AbortInd --> Idle3([Idle]) + + SendRInfoInt --> WaitRInfo([Wait For Routing Info]) + + NoticeInd --> CloseReq1[MAP_CLOSE_req] + CloseReq1 --> Idle4([Idle]) + + WaitRInfo --> NegResp[/Send Routing Info For Gprs negative response/] + WaitRInfo --> Ack[/Send Routing Info For Gprs ack/] + + NegResp --> SetUE[Set UE] + Ack --> SetRInfo[Set Routing Info] + SendRInfoInd --> SetRInfo + + SetUE --> FinalMerge{ } + SetRInfo --> FinalMerge + + FinalMerge --> Rsp[MAP_SEND_ROUTING_INFO_FOR_GPRS_rsp] + FinalMerge --> CloseReq2[MAP_CLOSE_req] + Rsp --> Idle5([Idle]) + CloseReq2 --> Idle5 + +``` + +SDL Diagram for Process Send\_Routing\_Info\_For\_Gprs\_GLR. The flow starts at an entry point leading to an Idle state. From Idle, it receives Open\_Ind (referencing Section 25.1). If OK, it moves to Wait\_For\_Service\_Indication. If Vr, Error, it returns to Idle. From Wait\_For\_Service\_Indication, four branches exist: 1) MAP\_P\_ABORT\_ind leads to Idle. 2) MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS\_ind leads to Set Routing Info. 3) MAP\_NOTICE\_ind leads to MAP\_CLOSE\_req and then Idle. 4) An internal signal 'Send Routing Info For Gprs' leads to Wait For Routing Info. From Wait For Routing Info, two responses are possible: a negative response (Set UE) or an ack (Set Routing Info). Both lead to a final state where MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS\_rsp and MAP\_CLOSE\_req are sent before returning to Idle. + +**Figure 24.2/1: Process Send Routing Info For Gprs\_GLR** + +### 24.2.2 Process in the IM-GSN for Send Routing Information for GPRS + +Successful Outcome + +When the MAP process receives a Send Routing Info For Gprs request from the GPRS application process in the IM-GSN, it: + +- requests a dialogue with the GLR whose identity is contained in the Send Routing Info For Gprs request by sending a MAP\_OPEN service request; +- requests routing information using a MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS service request, and +- invokes the macro Receive\_Open\_Cnf to wait for the response to the dialogue opening request. + +If the dialogue opening is successful, the MAP process waits for a response from the GLR. + +If the MAP process receives a MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS service confirm from the GLR, the MAP process invokes the macro Check\_Confirmation to check the content of the confirmation. + +If the macro Check\_Confirmation takes the OK exit, the MAP process sends a Send Routing Info For Gprs ack containing the routing information received from the GLR to the GPRS application process in the IM-GSN and returns to the idle state. + +#### **Failure of dialogue opening with the GLR** + +If the macro Receive\_Open\_Cnf takes the Vr exit or the Error exit, the MAP process sends a negative response to the GPRS application process in the IM-GSN and returns to the idle state. + +#### **Error in MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS confirm** + +If the MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS service confirm contains a user error or a provider error, or the macro Check\_Confirmation indicates that there is a data error, the MAP process sends a Send Routing Info For Gprs negative response to the GPRS application process in the IM-GSN and returns to the idle state. + +#### **Abort of GLR dialogue** + +After the dialogue with the GLR has been established, the MAP service provider may abort the dialogue by issuing a MAP\_P\_ABORT or a MAP\_U\_ABORT indication. In this case, the MAP process sends a Send Routing Info For Gprs negative response to the GPRS application process in the IM-GSN and returns to the idle state. + +If the MAP provider indicates a protocol problem by sending a MAP\_NOTICE indication, the MAP process closes the dialogue with the GLR, sends a Send Routing Info For Gprs negative response indicating system failure to the GPRS application process in the IM-GSN and returns to the idle state. + + + +### Process Send\_Routing\_Info\_For\_Gprs\_IMGSN 24.2.2(1) + +Figure 24.2/2: The Send Routing Info For Gprs process in the IMGSN + +Signals to/from the right are to/from the GPRS application process + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> Send_Routing_Info_For_Gprs + Send_Routing_Info_For_Gprs --> Wait_For_Open + state "MAP_OPEN_req
MAP_SEND_ROUTING_INFO_FOR_GPRS_req
MAP_DELIMITER_req" as Wait_For_Open + Wait_For_Open --> Receive_Open_cnf + Receive_Open_cnf --> Wait_For_Ack : OK + Receive_Open_cnf --> Send_Routing_Info_For_Gprs_negative_response : Vr, Error + Send_Routing_Info_For_Gprs_negative_response --> Idle + Wait_For_Ack --> Check_Confirmation : MAP_SEND_ROUTING_INFO_FOR_GPRS_cnf + Check_Confirmation --> Send_Routing_Info_For_Gprs_ack : OK + Send_Routing_Info_For_Gprs_ack --> Idle + Wait_For_Ack --> Send_Routing_Info_For_Gprs_negative_response : MAP_P_ABORT_ind / MAP_U_ABORT_ind + Send_Routing_Info_For_Gprs_negative_response --> Idle + Wait_For_Ack --> MAP_NOTICE_ind + MAP_NOTICE_ind --> MAP_CLOSE_req + Note right of Check_Confirmation : Section 25.2 + Note right of Receive_Open_cnf : Section 25.1 +``` + +State transition diagram for Process Send\_Routing\_Info\_For\_Gprs\_IMGSN. The process starts at Idle, transitions to Send Routing Info For Gprs, then to a state where it waits for MAP\_OPEN\_req, MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS\_req, or MAP\_DELIMITER\_req. It then receives Open\_cnf (Section 25.1). From Open\_cnf, an OK leads to Wait\_For\_Ack, while Vr, Error leads to Send Routing Info For Gprs negative response and back to Idle. From Wait\_For\_Ack, three paths emerge: MAP\_SEND\_ROUTING\_INFO\_FOR\_GPRS\_cnf (leading to Check\_Confirmation, Section 25.2), MAP\_P\_ABORT\_ind / MAP\_U\_ABORT\_ind, and MAP\_NOTICE\_ind. Check\_Confirmation leads to Send Routing Info For Gprs ack (OK) and back to Idle. The other two paths lead to Send Routing Info For Gprs negative response (Provider User Error, Data Error) and back to Idle. MAP\_NOTICE\_ind also leads to MAP\_CLOSE\_req. + +Figure 24.2/2: Process Send\_Routing\_Info\_For\_Gprs\_IM-GSN + +## 24.3 Failure Report procedure + +### 24.3.1 Process in the GLR for Failure Report + +The MAP process in the GLR to set the MNRG (Mobile station Not Reachable for GPRS) flag for the subscriber is shown in figure 24.3/1. The MAP process invokes a macro not defined in this subclause; the definition of this macro can be found as follows: + +- Receive\_Open\_Ind see subclause 25.1; +- Check Indication see subclause 25.2. + +#### Successful outcome + +When the MAP process receives a MAP\_OPEN indication with the application context failureReport, it checks it by invoking the macro Receive\_Open\_Ind. + +If the macro takes the OK exit, the MAP process waits for a service indication. + +If a MAP\_FAILURE\_REPORT service indication is received, the GLR sends a Failure Report request to the GPRS application process in the GLR, and wait for a response. The Failure Report request contains the parameter received in the MAP\_FAILURE\_REPORT service indication. + +If a positive response is received, the MAP process constructs a MAP\_FAILURE\_REPORT service response, constructs a MAP\_CLOSE service request, sends them to the IM-GSN and returns to the idle state. + +#### Negative response from GLR GPRS application process + +If the GPRS application process in the GLR returns a negative response, the MAP process constructs a MAP\_FAILURE\_REPORT service response containing the appropriate error, constructs a MAP\_CLOSE service request, sends them to the IM-GSN and returns to the idle state. + +#### Failure of dialogue opening with the IM-GSN + +If the macro Receive\_Open\_Ind takes the Vr exit or the Error exit, the MAP process returns to the idle state. + +If the MAP provider sends a MAP\_P\_ABORT while the MAP process is waiting for a service indication, the MAP process returns to the idle state. + +If the MAP provider sends a MAP\_NOTICE while the MAP process is waiting for a service indication, the MAP process sends a MAP\_CLOSE request to terminate the dialogue and returns to the idle state. + + + +### Process Failure\_Report\_GLR + +24.3.1(1) + +Figure 24.3/1: The Failure Report process in the GLR + +Signals to/from the right are to/from the application process + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> RecOpen[Receive Open_Ind]; RecOpen --> WaitFor[Wait_For_Service_Indication]; RecOpen --> VrError[Idle]; VrError --> VrError; WaitFor --> MAP_P_ABORT[MAP_P_ABORT_ind]; WaitFor --> MAP_FAILURE_REPORT[MAP_FAILURE_REPORT_ind]; WaitFor --> MAP_NOTICE[MAP_NOTICE_ind]; MAP_P_ABORT --> Idle2([Idle]); MAP_FAILURE_REPORT --> FailureReport[Failure Report]; FailureReport --> WaitForResponse[Wait For Response]; MAP_NOTICE --> MAP_CLOSE_req1[MAP_CLOSE_req]; MAP_CLOSE_req1 --> Idle3([Idle]); WaitForResponse --> NegResponse[Failure Report negative response]; WaitForResponse --> Ack[Failure Report ack]; NegResponse --> SetUE[Set UE]; Ack --> MAP_FAILURE_REPORT_rsp[MAP_FAILURE_REPORT_rsp]; SetUE --> MAP_FAILURE_REPORT_rsp; MAP_FAILURE_REPORT_rsp --> MAP_CLOSE_req2[MAP_CLOSE_req]; MAP_FAILURE_REPORT_rsp --> Idle4([Idle]); +``` + +The flowchart illustrates the 'Process Failure\_Report\_GLR'. It begins with an initial state leading to an 'Idle' state. Upon receiving an 'Open\_Ind' signal (referenced to Section 25.1), the process enters a 'Wait\_For\_Service\_Indication' state. From here, three outcomes are possible: an 'OK' response leads to another 'Idle' state; a 'Vr, Error' response also leads to an 'Idle' state; and a successful indication leads to three parallel paths. The first path involves 'MAP\_P\_ABORT\_ind', leading to 'Idle'. The second path involves 'MAP\_FAILURE\_REPORT\_ind', leading to a 'Failure Report' state, then 'Wait For Response'. From 'Wait For Response', a 'Failure Report negative response' leads to 'Set UE', and a 'Failure Report ack' leads to the final 'MAP\_FAILURE\_REPORT\_rsp' state. The third path involves 'MAP\_NOTICE\_ind', leading to 'MAP\_CLOSE\_req', which then leads to 'Idle'. Both 'Set UE' and 'MAP\_FAILURE\_REPORT\_rsp' lead to a final 'MAP\_FAILURE\_REPORT\_rsp' state, which also includes a 'MAP\_CLOSE\_req' signal and leads to a final 'Idle' state. A note indicates that signals to/from the right are to/from the application process. + +Flowchart of Process Failure\_Report\_GLR + +Figure 24.3/1: Process Failure\_Report\_GLR + +### 24.3.2 Process in the IM-GSN for Failure Report + +Successful Outcome + +When the MAP process receives a Failure Report request from the GPRS application process in the IM-GSN, it requests a dialogue with the GLR whose identity is contained in the Failure Report request by sending a MAP\_OPEN service request, sending failure information using a MAP\_FAILURE\_REPORT service request and invokes the macro Receive\_Open\_Cnf to wait for the response to the dialogue opening request. If the dialogue opening is successful, the MAP process waits for a response from the GLR. + +If the MAP process receives a MAP\_FAILURE\_REPORT service confirm from the GLR, the MAP process invokes the macro Check\_Confirmation to check the content of the confirmation. + +If the macro Check\_Confirmation takes the OK exit, the MAP process sends a Failure Report ack containing the information received from the GLR to the GPRS application process in the IM-GSN and returns to the idle state. + +#### **Failure of dialogue opening with the GLR** + +If the macro Receive\_Open\_Cnf takes the Vr exit or the Error exit, the MAP process sends a negative response to the GPRS application process in the IM-GSN and returns to the idle state. + +#### **Error in MAP\_FAILURE\_REPORT confirm** + +If the MAP\_FAILURE\_REPORT service confirm contains a user error or a provider error, or the macro Check\_Confirmation indicates that there is a data error, the MAP process sends a Failure Report negative response to the GPRS application process in the IM-GSN and returns to the idle state. + +#### **Abort of GLR dialogue** + +After the dialogue with the GLR has been established, the MAP service provider may abort the dialogue by issuing a MAP\_P\_ABORT or a MAP\_U\_ABORT indication. In this case, the MAP process sends a Failure Report negative response to the GPRS application process in the IM-GSN and returns to the idle state. + +If the MAP provider indicates a protocol problem by sending a MAP\_NOTICE indication, the MAP process closes the dialogue with the GLR, sends a Failure Report negative response indicating system failure to the GPRS application process in the IM-GSN and returns to the idle state. + + + +### Process Failure\_Report\_IMGSN + +24.3.2(1) + +Figure 24.3/2: The Failure Report process in the IMGSN + +Signals to/from the right are to/from the GPRS application process + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> FailureReport[/Failure Report/]; FailureReport --> OpenReq{ }; OpenReq --- OpenReqList["MAP_OPEN_req +MAP_FAILURE_REPORT_req +MAP_DELIMITER_req"]; OpenReq --> ReceiveOpenCnf[Receive Open_cnf]; ReceiveOpenCnf --- Section251[Section 25.1]; ReceiveOpenCnf --> WaitForAck([Wait_For_Ack]); WaitForAck -- OK --> CheckConfirmation[Check Confirmation]; WaitForAck -- "Vr, Error" --> FailureReportNeg[Failure Report negative response]; FailureReportNeg --> Idle2([Idle]); CheckConfirmation --- Section252[Section 25.2]; CheckConfirmation -- OK --> FailureReportAck[/Failure Report ack/]; CheckConfirmation -- "Provider User Error, Data Error" --> FailureReportNeg2[Failure Report negative response]; FailureReportAck --> Idle3([Idle]); FailureReportNeg2 --> Idle3; MAP_FAILURE_REPORT_cnf[MAP_FAILURE_REPORT_cnf] --> CheckConfirmation; MAP_P_ABORT_ind[MAP_P_ABORT_ind +MAP_U_ABORT_ind] --> FailureReportNeg2; MAP_NOTICE_ind[MAP_NOTICE_ind] --> MAP_CLOSE_req{ }; MAP_CLOSE_req --> FailureReportNeg2; +``` + +Flowchart of the Failure Report process in the IMGSN. The process starts at an Idle state, receives a Failure Report, sends MAP\_OPEN\_req, MAP\_FAILURE\_REPORT\_req, and MAP\_DELIMITER\_req, receives an Open confirmation, and then either waits for an acknowledgment or sends a negative response. It then checks for confirmations or notices, and finally sends an acknowledgment or negative response to return to the Idle state. + +Figure 24.3/2: Process Failure\_Report\_IM-GSN + +# --- 25 General macro description + +## 25.1 MAP open macros + +This subclause refers 3GPP TS 29.002. + +## 25.2 Macros to check the content of indication and confirmation primitives + +This subclause refers 3GPP TS 29.002. + +## 25.3 Authentication processes + +### 25.3.1 Process Obtain\_Authentication\_Sets\_GLR + +This process is initiated by the GLR to fetch authentication vectors from a subscriber's HLR to the VLR. The process is described in figure 25.3/1. + + + +### Process Obtain\_Authent\_Sets\_GLR + +25.3.1\_1(2) + +Figure 25.3/1: The Process to obtain authentication sets from the HLR to the VLR via the GLR + +Left from/to VLR +Right from/to HLR + +``` +graph TD; Start([ ]) --> NULL1(NULL); NULL1 --> Receive_Open_ind[Receive_Open_ind]; subgraph Section_25_1_1 [Section 25.1]; Receive_Open_ind; end; Receive_Open_ind -- OK --> Wait_For_Service_Primitive((Wait_For_Service_Primitive)); Receive_Open_ind -- "Vr, Error" --> NULL2(NULL); Wait_For_Service_Primitive --> MAP_P_ABORT_ind[MAP_P_ABORT_ind +MAP_U_ABORT_ind +MAP_CLOSE_ind]; Wait_For_Service_Primitive --> MAP_SEND_AUTHENTICATION_INFO_ind[MAP_SEND_AUTHENTICATION_INFO_ind]; Wait_For_Service_Primitive --> MAP_NOTICE_ind[MAP_NOTICE_ind]; MAP_P_ABORT_ind --> NULL3(NULL); MAP_SEND_AUTHENTICATION_INFO_ind --> Request[MAP_OPEN_req +MAP_SEND_AUTHENTICATION_INFO_req +MAP_DELIMITER_req]; Request --> Receive_Open_cnf[Receive_Open_cnf]; subgraph Section_25_1_2 [Section 25.1]; Receive_Open_cnf; end; Receive_Open_cnf -- OK --> WAIT_FOR_AUTHENTICATION_INFO((WAIT_FOR_AUTHENTICATION_INFO)); Receive_Open_cnf -- "Vr, Error" --> MAP_U_ABORT_req{MAP_U_ABORT_req}; MAP_U_ABORT_req --> NULL4(NULL); MAP_NOTICE_ind --> MAP_CLOSE_req{MAP_CLOSE_req}; MAP_CLOSE_req --> NULL5(NULL); +``` + +Flowchart for Process Obtain\_Authent\_Sets\_GLR. The process starts with an oval connector, leading to a 'NULL' state. It then enters a 'Receive\_Open\_ind' block (Section 25.1). From here, an 'OK' path leads to 'Wait\_For\_Service\_Primitive', which then branches into three parallel paths: one leading to a 'NULL' state via 'MAP\_P\_ABORT\_ind', 'MAP\_U\_ABORT\_ind', and 'MAP\_CLOSE\_ind'; another leading to a request block ('MAP\_OPEN\_req', 'MAP\_SEND\_AUTHENTICATION\_INFO\_req', 'MAP\_DELIMITER\_req') which then leads to 'Receive\_Open\_cnf' (Section 25.1); and a third leading to 'NULL' via 'MAP\_NOTICE\_ind' and 'MAP\_CLOSE\_req'. From 'Receive\_Open\_cnf', an 'OK' path leads to 'WAIT\_FOR\_AUTHENTICATION\_INFO', while a 'Vr, Error' path leads to 'MAP\_U\_ABORT\_req' and then to a 'NULL' state. + +Figure 25.3.1/1 (sheet 1 of 2): Process Obtain\_Authentication\_Sets\_GLR + + + +**Process Obtain\_Authent\_Sets\_GLR** 25.3.1\_2(2) + +Figure 25.3/1: The Process to obtain authentication sets from the HLR to the VLR via the GLR + +Left from/to VLR +Right from/to HLR + +``` + +stateDiagram-v2 + [*] --> WAIT_FOR_AUTHENTICATION_INFO + state "WAIT FOR AUTHENTICATION_INFO" as WAIT_FOR_AUTHENTICATION_INFO + state "MAP SEND AUTHENTICATION_INFO_req" as MAP_SEND_AUTHENTICATION_INFO_req + state "MAP SEND AUTHENTICATION_INFO_ind" as MAP_SEND_AUTHENTICATION_INFO_ind + state "MAP SEND AUTHENTICATION_INFO_cnf" as MAP_SEND_AUTHENTICATION_INFO_cnf + state "MAP CLOSE_ind" as MAP_CLOSE_ind + state "MAP CLOSE_req" as MAP_CLOSE_req + state "NULL" as NULL + state "MAP_NOTICE_ind" as MAP_NOTICE_ind + state "MAP_CLOSE_req" as MAP_CLOSE_req + state "MAP_U_ABORT_req" as MAP_U_ABORT_req + state "MAP_P_ABORT_ind / MAP_U_ABORT_ind" as MAP_P_ABORT_ind_MAP_U_ABORT_ind + + WAIT_FOR_AUTHENTICATION_INFO --> MAP_SEND_AUTHENTICATION_INFO_req + MAP_SEND_AUTHENTICATION_INFO_req --> MAP_SEND_AUTHENTICATION_INFO_ind + MAP_SEND_AUTHENTICATION_INFO_ind --> MAP_SEND_AUTHENTICATION_INFO_cnf + MAP_SEND_AUTHENTICATION_INFO_cnf --> WAIT_FOR_AUTHENTICATION_INFO + MAP_SEND_AUTHENTICATION_INFO_cnf --> MAP_SEND_AUTHENTICATION_INFO_req + MAP_SEND_AUTHENTICATION_INFO_req --> NULL + MAP_CLOSE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> NULL + MAP_CLOSE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> WAIT_FOR_AUTHENTICATION_INFO + + WAIT_FOR_AUTHENTICATION_INFO --> MAP_NOTICE_ind + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> MAP_U_ABORT_req + MAP_U_ABORT_req --> NULL + MAP_NOTICE_ind --> MAP_CLOSE_req + MAP_CLOSE_req --> WAIT_FOR_AUTHENTICATION_INFO + MAP_P_ABORT_ind_MAP_U_ABORT_ind --> MAP_U_ABORT_req + MAP_U_ABORT_req --> NULL + MAP_P_ABORT_ind_MAP_U_ABORT_ind --> MAP_U_ABORT_req + MAP_U_ABORT_req --> WAIT_FOR_AUTHENTICATION_INFO + +``` + +State transition diagram for Process Obtain\_Authent\_Sets\_GLR. The diagram shows two main sections of state transitions. The top section starts with 'WAIT FOR AUTHENTICATION\_INFO' and branches into four paths: 1) MAP SEND AUTHENTICATION\_INFO\_req leads to MAP SEND AUTHENTICATION\_INFO\_ind, which leads to MAP SEND AUTHENTICATION\_INFO\_cnf, which leads to 'WAIT FOR AUTHENTICATION\_INFO'. 2) MAP SEND AUTHENTICATION\_INFO\_cnf leads to MAP SEND AUTHENTICATION\_INFO\_req, which leads to 'NULL'. 3) MAP CLOSE\_ind leads to MAP CLOSE\_req, which leads to 'NULL'. 4) MAP CLOSE\_ind leads to MAP CLOSE\_req, which loops back to 'WAIT FOR AUTHENTICATION\_INFO'. The bottom section starts with 'WAIT FOR AUTHENTICATION\_INFO' and branches into four paths: 1) MAP\_NOTICE\_ind leads to MAP\_CLOSE\_req, which leads to MAP\_U\_ABORT\_req, which leads to 'NULL'. 2) MAP\_NOTICE\_ind leads to MAP\_CLOSE\_req, which loops back to 'WAIT FOR AUTHENTICATION\_INFO'. 3) MAP\_P\_ABORT\_ind / MAP\_U\_ABORT\_ind leads to MAP\_U\_ABORT\_req, which leads to 'NULL'. 4) MAP\_P\_ABORT\_ind / MAP\_U\_ABORT\_ind leads to MAP\_U\_ABORT\_req, which loops back to 'WAIT FOR AUTHENTICATION\_INFO'. + +Figure 25.3.1/2 (sheet 2 of 2): Process Obtain\_Authentication\_Sets\_GLR + +### 25.3.2 Process Authentication\_Failure\_Report\_GLR + +This process is initiated by the GLR to notify a subscriber's HLR about the occurrence of an authentication failure in the VLR or SGSN. The process is described in figure 25.3/2. + + + +### Process Authentication\_Failure\_Report\_GLR + +25.3.2\_1(2) + +Figure 25.3.2/1: The Process to notify authentication failure report from the VLR/SGSN to the HLR via the GLR + +Left from/to VLR or SGSN +Right from/to HLR + +``` +graph TD; Start([ ]) --> NULL1([NULL]); NULL1 --> Receive_Open_ind[Receive_Open_ind]; Receive_Open_ind --- Section25_1_1[Section 25.1]; Receive_Open_ind -- OK --> Wait_For_Service_Primitive([Wait_For_Service_Primitive]); Receive_Open_ind -- "Vr, Error" --> NULL2([NULL]); Wait_For_Service_Primitive --> Decision1{ }; Decision1 -- "MAP_AUTHENTICATION_FAILURE_REPORT_ind" --> MAP_NOTICE_ind[MAP_NOTICE_ind]; MAP_NOTICE_ind --> MAP_CLOSE_req{MAP_CLOSE_req}; MAP_CLOSE_req --> NULL3([NULL]); Decision1 --> MAP_P_ABORT_ind[MAP_P_ABORT_ind +MAP_U_ABORT_ind +MAP_CLOSE_ind]; MAP_P_ABORT_ind --> NULL4([NULL]); Decision1 --> MAP_OPEN_req[MAP_OPEN_req +MAP_AUTHENTICATION_FAILURE_REPORT_req +MAP_DELIMITER_req]; MAP_OPEN_req --> Receive_Open_cnf[Receive_Open_cnf]; Receive_Open_cnf --- Section25_1_2[Section 25.1]; Receive_Open_cnf -- OK --> WAIT_FOR_RESPONSE([WAIT_FOR_RESPONSE]); Receive_Open_cnf -- "Vr, Error" --> MAP_U_ABORT_req{MAP_U_ABORT_req}; MAP_U_ABORT_req --> NULL5([NULL]); +``` + +Flowchart for Process Authentication\_Failure\_Report\_GLR. The process starts with a NULL state, followed by 'Receive\_Open\_ind' (Section 25.1). From here, an 'OK' path leads to 'Wait\_For\_Service\_Primitive', which then leads to a decision point. A 'Vr, Error' path from 'Receive\_Open\_ind' leads to a NULL state. From the decision point, a 'MAP\_AUTHENTICATION\_FAILURE\_REPORT\_ind' leads to 'MAP\_NOTICE\_ind', which then leads to 'MAP\_CLOSE\_req' and a NULL state. Another path from the decision point leads to a box with 'MAP\_P\_ABORT\_ind', 'MAP\_U\_ABORT\_ind', and 'MAP\_CLOSE\_ind', which leads to a NULL state. A third path from the decision point leads to a box with 'MAP\_OPEN\_req', 'MAP\_AUTHENTICATION\_FAILURE\_REPORT\_req', and 'MAP\_DELIMITER\_req', which leads to 'Receive\_Open\_cnf' (Section 25.1). From 'Receive\_Open\_cnf', an 'OK' path leads to 'WAIT\_FOR\_RESPONSE', and a 'Vr, Error' path leads to 'MAP\_U\_ABORT\_req' and a NULL state. + +Figure 25.3.2/1 (sheet 1 of 2): Process Authentication\_Failure\_Report\_GLR + + + +**Process Authentication\_Failure\_Report\_GLR** 25.3.2\_2(2) + +Figure 25.3.2/1: The Process to notify authentication failure report from the VLR/SGSN to the HLR via the GLR + +Left from/to VLR or SGSN +Right from/to HLR + +State transition diagram for Process Authentication\_Failure\_Report\_GLR. The diagram shows two main sections of state transitions. The top section starts with a 'WAIT\_FOR\_RESPONSE' state, leading to a horizontal transition line. Below this line are three boxes: 'MAP\_AUTHENTICATION\_FAILURE\_REPORT\_cnf' (left), 'MAP\_CLOSE\_ind' (middle), and 'MAP\_CLOSE\_ind' (right). Below the left box is a 'MAP\_AUTHENTICATION\_FAILURE\_REPORT\_cnf' state. Below the middle and right boxes are 'MAP\_CLOSE\_req' states. All three states lead to a 'NULL' state. The bottom section starts with a horizontal transition line. Below it are four boxes: 'MAP\_NOTICE\_ind' (leftmost), 'MAP\_NOTICE\_ind' (second from left), 'MAP\_P\_ABORT\_ind / MAP\_U\_ABORT\_ind' (third from left), and 'MAP\_P\_ABORT\_ind / MAP\_U\_ABORT\_ind' (rightmost). Below the leftmost box is a 'MAP\_CLOSE\_req' state, which leads to a 'MAP\_U\_ABORT\_req' state. Below the second box is a 'MAP\_CLOSE\_req' state, which leads to a 'MAP\_U\_ABORT\_req' state. Below the third box is a 'MAP\_U\_ABORT\_req' state. Below the rightmost box is a 'MAP\_U\_ABORT\_req' state. All four 'MAP\_U\_ABORT\_req' states lead to a 'NULL' state. + +**Figure 25.3.2/2 (sheet 2 of 2): Process Authentication\_Failure\_Report\_GLR** + +## 25.4 Short Message Alert procedures + +### 25.4.1 Subscriber\_Present\_GLR\_AS\_VLR process + +The Subscriber\_Present\_GLR\_AS\_VLR process is invoked by the GLR, when GLR receives Update Location from VLR and the MNRF flag is set. The general description of the short message alert procedures is in the subclause 23.3. + +The GLR sends the MAP\_READY\_FOR\_SM request to the HLR and waits for the HLR to answer. When receiving the answer, the GLR will act as follows: + +- the MNRF flag is cleared if the procedure is successful; +- the MNRF flag is not cleared if the procedure is not successful. + +The Subscriber\_Present\_GLR\_AS\_VLR process is shown in the figure 25.4/1. + +#### Process Subscriber\_Present\_GLR\_AS\_VLR + +25.4.1(1) + +Figure 25.4/1: The short message alert process in the GLR for mobile present situation + + + +``` +graph TD; Start([ ]) --> MNRF{MNRF set}; MNRF -- No --> Error1[Error]; MNRF -- Yes --> Req["MAP_OPEN_req
MAP_READY_FOR_SM_req
MAP_DELIMITER_req"]; Req --> OpenCnf["Receive_Open_cnf
Section 25.1"]; OpenCnf --> WF{WF RESPONSE}; WF -- OK --> Rsp["MAP_READY_FOR_SM_rsp"]; Rsp --> Ind["MAP_P_ABORT_ind
MAP_U_ABORT_ind
MAP_CLOSE_ind"]; Ind --> Error2{Error}; Error2 -- Yes --> Error3[Error]; Error2 -- No --> ClearMNRF[Clear MNRF]; ClearMNRF --> V1[V1]; WF -- Error --> Error4[Error]; Error4 -- Yes --> Error5[Error]; Error4 -- No --> ClearMNRF2[Clear MNRF]; ClearMNRF2 --> V2[V1]; +``` + +Flowchart for Process Subscriber\_Present\_GLR\_AS\_VLR. It starts with a decision 'MNRF set'. If 'No', it goes to an 'Error' state. If 'Yes', it sends 'MAP\_OPEN\_req', 'MAP\_READY\_FOR\_SM\_req', and 'MAP\_DELIMITER\_req', then receives 'Open\_cnf' (Section 25.1). It then checks 'WF RESPONSE'. If 'OK', it sends 'MAP\_READY\_FOR\_SM\_rsp' and 'MAP\_P\_ABORT\_ind', 'MAP\_U\_ABORT\_ind', 'MAP\_CLOSE\_ind', then checks for 'Error'. If 'Error' is 'Yes', it goes to 'Error'; if 'No', it 'Clear MNRF' and goes to 'V1'. If 'WF RESPONSE' is 'Error', it goes to 'Error'. If 'Error' is 'Yes', it goes to 'Error'; if 'No', it 'Clear MNRF' and goes to 'V1'. + +Figure 25.4/1: Process Subscriber\_Present\_GLR\_AS\_VLR + +### 25.4.2 The Mobile Subscriber is present + +When GLR receives Update GPRS Location from SGSN, while the MS not reachable for GPRS (MNRG) flag is set, the GLR will send the MAP\_READY\_FOR\_SM request towards the HLR. The Alert Reason is set to indicate that the mobile subscriber is present for GPRS. + +When receiving the answer, the GLR will act as follows: + +- MNRG is cleared if the procedure is successful. +- MNRG is not cleared if the procedure is not successful. + +The Subscriber\_Present\_GLR\_AS\_SGSN process is shown in the figure 25.4/2. + +#### Process Subscriber\_Present\_GLR\_AS\_SGSN + +25.4.2(1) + +Figure 25.4/2: The short message alert process in the GLR for mobile present situation + + + +``` +graph TD; Start([ ]) --> MNRG_set{MNRG set}; MNRG_set -- No --> End1(( )); MNRG_set -- Yes --> SendReq[MAP_OPEN_req +MAP_READY_FOR_SM_req +MAP_DELIMITER_req]; SendReq --> ReceiveOpenCnf[Receive Open_cnf]; ReceiveOpenCnf -- Section 25.1 --> WF_RESPONSE{WF RESPONSE}; WF_RESPONSE -- Error --> End2(( )); WF_RESPONSE -- V1 --> PerformMAPV1[Perform MAP_V1_Dialogue]; PerformMAPV1 --> End3(( )); WF_RESPONSE -- OK --> ReceiveReadyRsp[MAP_READY_FOR_SM_rsp]; ReceiveReadyRsp --> ErrorDecision{Error}; ErrorDecision -- Yes --> End4(( )); ErrorDecision -- No --> ClearMNRG[Clear MNRG]; ClearMNRG --> End5(( )); ClearMNRG --> SendInd[MAP_P_ABORT_ind +MAP_U_ABORT_ind +MAP_CLOSE_ind]; SendInd --> End6(( )); +``` + +Flowchart for Process Subscriber\_Present\_GLR\_AS\_SGSN. It starts with a decision 'MNRG set'. If 'No', it ends. If 'Yes', it sends 'MAP\_OPEN\_req', 'MAP\_READY\_FOR\_SM\_req', and 'MAP\_DELIMITER\_req', then receives 'Open\_cnf' (Section 25.1). It then checks 'WF RESPONSE'. If 'Error', it ends. If 'V1', it performs 'MAP\_V1\_Dialogue' and ends. If 'OK', it receives 'MAP\_READY\_FOR\_SM\_rsp'. It then checks 'Error'. If 'Yes', it ends. If 'No', it performs 'Clear MNRG' and ends. There is also a branch for 'MAP\_P\_ABORT\_ind', 'MAP\_U\_ABORT\_ind', and 'MAP\_CLOSE\_ind'. + +Figure 25.4/2: Process Subscriber\_Present\_GLR\_AS\_SGSN + +# Annex A (informative): Change history + +| TSG CN# | Spec | CR |
(5513) ..... | 37 | +| 6.3.3.4 | DIAMETER_ERROR_CONFIGURATION_EVENT_NON_EXISTANT (5514) ..... | 38 | +| 6.3.3.5 | DIAMETER_ERROR_REQUESTED_LOCATION_NOT_SERVED (5650) ..... | 38 | +| 6.3.3.6 | DIAMETER_ERROR_USER_UNKNOWN (5001) ..... | 38 | +| 6.3.3.7 | DIAMETER_ERROR_OPERATION_NOT_ALLOWED (5101) ..... | 38 | +| 6.3.3.8 | DIAMETER_ERROR_INVALID_EPS_BEARER (5651) ..... | 38 | +| 6.3.3.9 | DIAMETER_ERROR_NIDD_CONFIGURATION_NOT_AVAILABLE (5652) ..... | 38 | +| 6.3.3.10 | DIAMETER_ERROR_SCEF_REFERENCE_ID_UNKNOWN (5515) ..... | 38 | +| 6.3.3.11 | DIAMETER_ERROR_USER_TEMPORARILY_UNREACHABLE (5653) ..... | 38 | +| 6.3.3.12 | DIAMETER_ERROR_UNREACHABLE_USER (4221) ..... | 38 | +| 6.4 | AVPs ..... | 38 | +| 6.4.1 | General ..... | 38 | +| 6.4.2 | Monitoring-Event-Configuration ..... | 42 | +| 6.4.3 | Monitoring-Event-Report ..... | 42 | +| 6.4.4 | Communication-Failure-Information ..... | 43 | +| 6.4.5 | Cause-Type ..... | 43 | +| 6.4.6 | SIAP-Cause ..... | 44 | +| 6.4.7 | RANAP-Cause ..... | 44 | +| 6.4.8 | BSSGP-Cause ..... | 44 | +| 6.4.9 | GMM-Cause ..... | 44 | +| 6.4.10 | SM-Cause ..... | 44 | +| 6.4.11 | Number-Of-UE-Per-Location-Configuration ..... | 44 | +| 6.4.12 | Number-Of-UE-Per-Location-Report ..... | 44 | +| 6.4.13 | UE-Count ..... | 45 | +| 6.4.14 | Feature-List AVP ..... | 45 | +| 6.4.14.1 | Feature-List AVP for the T6a/T6b application ..... | 45 | +| 6.4.15 | DRMP ..... | 45 | +| 6.4.16 | User-Identifier ..... | 46 | +| 6.4.17 | Bearer-Identifier ..... | 46 | +| 6.4.18 | Connection-Action ..... | 46 | + +| | | | +|-------------------------------|--------------------------------------------------|-----------| +| 6.4.19 | Non-IP-Data ..... | 46 | +| 6.4.20 | Service-Selection ..... | 46 | +| 6.4.21 | Serving-PLMN-Rate-Control ..... | 46 | +| 6.4.22 | Downlink-Rate-Limit ..... | 47 | +| 6.4.23 | Uplink-Rate-Limit ..... | 47 | +| 6.4.24 | SCEF-Wait-Time ..... | 47 | +| 6.4.25 | CMR-Flags ..... | 47 | +| 6.4.26 | Extended-PCO ..... | 47 | +| 6.4.27 | RRC-Cause-Counter ..... | 47 | +| 6.4.28 | Counter-Value ..... | 47 | +| 6.4.29 | RRC-Counter-Timestamp ..... | 48 | +| 6.4.30 | Terminal-Information ..... | 48 | +| 6.4.31 | TDA-Flags ..... | 48 | +| 6.4.32 | Idle-Status-Indication ..... | 48 | +| 6.4.33 | Idle-Status-Timestamp ..... | 49 | +| 6.4.34 | Active-Time ..... | 49 | +| 6.4.35 | Reachability-Cause ..... | 49 | +| 6.4.36 | APN-Rate-Control-Status ..... | 50 | +| 6.4.37 | Uplink-Number-Of-Packets-Allowed ..... | 50 | +| 6.4.38 | Number-Of-Additional-Exception-Reports ..... | 50 | +| 6.4.39 | Downlink-Number-Of-Packets-Allowed ..... | 50 | +| 6.4.40 | APN-Rate-Control-Status-Validity-Time ..... | 50 | +| A.1 | T6a/b and T7 interfaces ..... | 50 | +| A.1.1 | General ..... | 50 | +| A.1.2 | SCEF behaviour ..... | 50 | +| A.1.3 | MME/SGSN behaviour ..... | 51 | +| A.1.4 | IWK-SCEF behaviour ..... | 51 | +| Annex B (normative): | Diameter message priority mechanism ..... | 51 | +| B.1 | General ..... | 51 | +| B.2 | T6a, T6ai, T6b, T6bi, T7 interfaces ..... | 51 | +| Annex C (normative): | Diameter load control mechanism ..... | 52 | +| C.1 | General ..... | 52 | +| C.2 | SCEF behaviour ..... | 52 | +| C.3 | MME/SGSN behaviour ..... | 53 | +| C.4 | IWK-SCEF behaviour ..... | 53 | +| Annex D (informative): | Change history ..... | 54 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document describes the Diameter-based interfaces between the SCEF/IWK-SCEF and other network entities such as MME/SGSN for the Architecture enhancements to facilitate communications with packet data networks and applications. + +In particular, this document specifies the T6a interface between the MME and the SCEF, the T6ai interface between the MME and the IWK-SCEF, the T6b interface between the SGSN and the SCEF, the T6bi interface between the SGSN and the SCEF and the T7 interface between the SCEF and the IWK-SCEF. The procedures over those interfaces are defined in 3GPP TS 23.682 [2]. + +# --- 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.682: "Architecture enhancements to facilitate communications with packet data networks and applications ". +- [3] Void. +- [4] 3GPP TS 29.229: "Cx and Dx interfaces based on the Diameter protocol; protocol details ". +- [5] 3GPP TS 29.336: "Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications". +- [6] 3GPP TS 29.228: "IP multimedia (IM) Subsystem Cx Interface; Signalling flows and Message Elements". +- [7] IETF RFC 4960: "Stream Control Transport Protocol". +- [8] IETF RFC 5234: "Augmented BNF for Syntax Specifications: ABNF". +- [9] IETF RFC 7683: "Diameter Overload Indication Conveyance". +- [10] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points". +- [11] 3GPP TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling". + +- [12] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3". +- [13] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)". +- [14] 3GPP TS 48.018: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS protocol (BSSGP)". +- [15] IETF RFC 7944: "Diameter Routing Message Priority". +- [16] 3GPP TS 29.272: "Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol". +- [17] 3GPP TS 29.329: "Sh Interface based on the Diameter protocol; Protocol details". +- [18] Void. +- [19] 3GPP TS 23.007: "Restoration procedures". +- [20] 3GPP TS 32.299: "Telecommunication management; Charging management; Diameter charging applications". +- [21] IETF RFC 5778: "Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction". +- [22] 3GPP TS 32.299: "Telecommunication management; Charging management; Diameter charging applications". +- [23] 3GPP TS 32.253: "Telecommunication management; Charging management; Control Plane (CP) data transfer domain charging". +- [24] 3GPP TS 23.003: "Numbering, addressing and identification". +- [25] 3GPP TS 23.401: "GPRS enhancements for E-UTRAN access". +- [26] 3GPP TS 29.172: "Location Services (LCS); Evolved Packet Core (EPC) LCS Protocol (ELP) between the Gateway Mobile Location Centre (GMLC) and the Mobile Management Entity (MME); SLg interface". +- [27] 3GPP TS 29.338: "Diameter based protocols to support SMS capable MMEs". +- [28] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". +- [29] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)". +- [30] 3GPP TS 32.298: "Telecommunication Management; Charging Management; Charging Data Record (CDR) parameter description". +- [31] IETF RFC 8583: "Diameter Load Information Conveyance". +- [32] IETF RFC 6733: "Diameter Base Protocol". +- [33] 3GPP TS 29.274: " Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C)". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|----------|--------------------------------------| +| DRMP | Diameter Routing Message Priority | +| DSCP | Differentiated Services Code Point | +| SCEF | Service Capability Exposure Function | +| IWK-SCEF | Interworking - SCEF | + +# --- 4 General Description + +## 4.1 Introduction + +The T6a/b reference point between the MME/SGSN and the SCEF, the T6ai/bi reference point between the MME/SGSN in the VPLMN and the IWK-SCEF and the T7 reference point between the IWK-SCEF and the SCEF are defined in the 3GPP TS 23.682 [2]. + +This document describes the Diameter-based T6a/b, T6ai/bi and T7 related procedures, message parameters and protocol specification. + +An excerpt of the 3GPP Architecture for the enhancements to facilitate communications with packet data networks and applications, as defined in 3GPP TS 23.682 [2] is shown in Figure 4.1-1, where the relevant interfaces towards the SCEF/IWK-SCEF are highlighted. + + + +Diagram of 3GPP Architecture for enhancements to facilitate communications with packet data networks and applications. The diagram shows two network domains: HPLMN (Home PLMN) and VPLMN (Visited PLMN), separated by a dashed orange line. In the HPLMN, there is an HSS at the top, an MME/SGSN on the left, and an SCEF on the right. In the VPLMN, there is an MME/SGSN on the left and an IWK-SCEF on the right. Interfaces are labeled: S6a/d (between HSS and MME/SGSN in HPLMN), S6t (between HSS and SCEF in HPLMN), T6a/b (between MME/SGSN and SCEF in HPLMN), T6ai/T6bi (between MME/SGSN in VPLMN and IWK-SCEF in VPLMN), and T7 (between SCEF in HPLMN and IWK-SCEF in VPLMN). + +**Figure 4.1-1: 3GPP Architecture for the enhancements to facilitate communications with packet data networks and applications** + +In this architecture, the T6a/b reference point connects the MME/SGSN with the SCEF. + +The T6a/b interface shall allow the SCEF: + +- to receive reports of the monitoring events from the MME/SGSN configured via an HSS; +- to configure the monitoring events at an MME/SGSN which are not UE related in the non roaming cases; +- to manage a connection between the MME and the SCEF on T6a; +- to send MT data on T6a; +- to receive MO data on T6a. + +The T6ai/bi reference point connects the MME/SGSN with the IWK-SCEF in the visited network, if the IWK-SCEF is deployed. + +The T6ai/bi interface shall allow the IWK-SCEF to: + +- to receive configuration of the monitoring events from the MME or the SGSN and perform a filtering of the services which are allowed for this subscriber in this visited network based on roaming policies; +- to receive reports of the monitoring events from the MME/SGSN that are configured via an HSS, perform a filtering and forward them to the SCEF (in the home network which has configured the event) via the T7 reference point; +- to receive MO data on T6ai/bi and forward them to the SCEF; +- to receive MT data and forward them to the MME on T6ai/bi; +- to manage a connection between MME/SGSN and IWK-SCEF on T6ai/bi and forward connection management commands to the SCEF. + +The T7 reference point connects the IWK-SCEF in the visited network with the SCEF in the home network. + +The T7 interface shall allow the IWK-SCEF to: + +- to forward reports received on T6ai/bi to the SCEF indicated in the event report received on T6ai/T6bi; +- to receive MO data on T6ai/bi and forward them to the SCEF on T7; +- to receive MT data on T7 and forward them to the MME/SGSN; +- to manage connection between the SCEF and the IWK-SCEF on T7 and forward connection management commands to the MME/SGSN. + +# --- 5 Procedures Description + +## 5.1 Introduction + +This clause describes the Diameter-based T6a, T6b, T6ai, T6bi and T7 interface related procedures and the Information elements exchanged between the functional entities. + +In the tables that describe the Information Elements transported by each Diameter command, each Information Element is marked as (M) Mandatory, (C) Conditional or (O) Optional in the "Cat." column. For the correct handling of the Information Element according to the category type, see the description detailed in clause 6 of the 3GPP TS 29.228 [6]. + +## 5.2 Report Procedures + +### 5.2.1 General + +This procedure is used between the MME/SGSN and the SCEF, between the MME/SGSN and the IWK-SCEF and between the IWK-SCEF and the SCEF. + +When the procedure is invoked by the MME or the SGSN, it is used for reporting: + +- UE Loss of Connectivity; +- UE Reachability; +- Location of the UE and change in location of the UE; +- Communication Failure; +- Availability after DNN failure; +- Idle Status Indication; +- PDN Connectivity Status. + +When the procedure is invoked by the IWK-SCEF, it is used for conveying the monitoring event reported by the MME or the SGSN to the SCEF, after applying the roaming policies configured at the IWK-SCEF. + +This procedure is mapped to the commands Reporting-Information-Request/Answer in the Diameter application specified in clause 6. The tables 5.2.1-1 and 5.2.1-2 detail the involved information elements. + +**Table 5.2.1-1: Reporting Information Request** + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------------------------|-------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity
(See 6.4.16) | User-Identifier | C | If present, this information element shall contain the identity of the UE. This is a grouped AVP containing the MSISDN or the External-Identifier. | +| Monitoring Event Report
(see 3GPP TS 29.336 [5] clause 8.4.3) | Monitoring-Event-Report | C | If the Reporting-Information-Request is sent for reporting the monitoring events, the MME/SGSN and the IWK-SCEF shall include the monitoring event(s) reported towards the SCEF. | +| Supported Features
(See 3GPP TS 29.229 [4]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +**Table 5.2.1-2: Reporting Information Answer** + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|-----------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result
(See 6.3) | Result-Code / Experimental-Result | M | Result of the request.
Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
Experimental-Result AVP shall be used for T6a/b errors. This is a grouped AVP, which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| Supported Features
(See 3GPP TS 29.229 [4]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Monitoring Event Report Status | Monitoring-Event-Report-Status | O | If present, this information element shall contain the status of each individual monitoring event report received by the SCEF from the MME/SGSN. | + +### 5.2.2 Detailed Behaviour of the MME/SGSN + +#### 5.2.2.0 General + +The MME/SGSN shall fill the Monitoring-Event-Report AVP according to the event reported as specified below. For all monitoring events, the SCEF-ID, the SCEF-Reference-ID/SCEF-Reference-ID-Ext and the Monitoring-Type AVPs shall be included. In addition, the event specific AVPs as listed below shall be included based on the type of event reported. + +The MME/SGSN shall include the External-Identifier or the MSISDN if present in the subscription data received from the HSS. + +If the MME/SGSN receives an Experimental-Result-Code set to DIAMETER\_ERROR\_SCEF\_REFERENCE\_ID\_UNKNOWN within an RIA command, it shall delete the event stored for the indicated SCEF-ID and SCEF-Reference-ID/SCEF-Reference-ID-Ext (see 3GPP TS 23.007 [19]). + +#### 5.2.2.1 UE Loss of Connectivity + +The following AVPs shall be present within the Monitoring-Event-Report AVP when the UE Loss of Connectivity event is reported: + +- Monitoring-Type set to LOSS\_OF\_CONNECTIVITY (0) + +The following AVPs may be present within the Monitoring-Event-Report AVP when the UE Loss of Connectivity event is reported: + +- Loss-Of-Connectivity-Reason set to one of the values defined in 3GPP TS 29.336 [5] + +#### 5.2.2.2 UE Reachability + +The following AVPs shall be present within the Monitoring-Event-Report AVP when the UE Reachability event is reported: + +- Monitoring-Type set to either UE\_REACHABILITY (1) or UE\_REACHABILITY\_AND\_IDLE\_STATUS\_INDICATION (8), as received in the configuration request. +- Reachability-Information set to REACHABLE\_FOR\_DATA(1) + +The following AVPs may be present within the Monitoring-Event-Report AVP when the UE Reachability event is reported: + +- Maximum-UE-Availability-Time +- Reachability-Cause + +NOTE: When the Monitoring-Type is UE\_REACHABILITY\_AND\_IDLE\_STATUS\_INDICATION (8), absence of the Idle-Status-Indication AVP from the Monitoring-Event-Report AVP indicates that UE reachability is reported. + +#### 5.2.2.3 Location Reporting + +The following AVPs shall be present within the Monitoring-Event-Report AVP when the location event is reported: + +- Monitoring-Type set to LOCATION\_REPORTING (2) +- EPS-Location-Information + +#### 5.2.2.4 Communication Failure + +The following AVPs shall be present within the Monitoring-Event-Report AVP when the Communication Failure event is reported + +- Monitoring-Type set to COMMUNICATION\_FAILURE (5) +- Communication-Failure-Information (see clause 6.4.3) + +#### 5.2.2.5 Availability after DDN failure + +The following AVPs shall be present within the Monitoring-Event-Report AVP when the Availability after DDN failure event is reported: + +- Monitoring-Type set to either AVAILABILITY\_AFTER\_DDN\_FAILURE (6) or AVAILABILITY\_AFTER\_DNN\_FAILURE\_AND\_IDLE\_STATUS\_INDICATION (9), as received in the configuration request. + +NOTE: When the Monitoring-Type is AVAILABILITY\_AFTER\_DNN\_FAILURE\_AND\_IDLE\_STATUS\_INDICATION (9), absence of the Idle-Status-Indication AVP from the Monitoring-Event-Report AVP indicates that Availability after DNN failure is reported. + +#### 5.2.2.6 Idle Status Indication + +The following AVPs shall be present within the Monitoring-Event-Report AVP when the Idle Status Indication event is reported: + +- Monitoring-Type set to UE\_REACHABILITY\_AND\_IDLE\_STATUS\_INDICATION (8) or to AVAILABILITY\_AFTER\_DDN\_FAILURE\_AND\_IDLE\_STATUS\_INDICATION (9), depending on the Monitoring-Type of the corresponding event configuration. + +- Idle-Status-Indication + +#### 5.2.2.7 PDN Connectivity Status + +The following AVPs shall be present within the Monitoring-Event-Report AVP when the PDN Connectivity Status event is reported: + +- Monitoring-Type set to PDN\_CONNECTIVITY\_STATUS (8) +- PDN-Connectivity-Status-Report + +### 5.2.3 Detailed Behaviour of the SCEF + +When the SCEF receives a Reporting Information Request from the MME/SGSN or the IWK-SCEF and at least one of the Monitoring Event Report AVPs has a SCEF-Reference-ID/SCEF-Reference-ID-Ext not known by the SCEF, it shall reply with Experimental-Result-Code set to DIAMETER\_ERROR\_SCEF\_REFERENCE\_ID\_UNKNOWN (see 3GPP TS 23.007 [19]). In that case, if the HSS had included multiple Monitoring Event Reports in the RIR command, the SCEF shall include in the Reporting Information Answer command a list of Monitoring-Event-Report-Status AVPs where the status of multiple monitoring event reports is detailed. In that AVP list, the AVPs corresponding to event reports with a successful status may be omitted by the SCEF, for efficiency. + +Otherwise when the SCEF receives a Reporting-Information-Request command from the MME/SGSN or the IWK-SCEF, the SCEF shall set Result-Code to DIAMETER\_SUCCESS in the Reporting-Information-Answer and shall handle it according to the procedures defined in 3GPP TS 23.682 [2]. + +### 5.2.4 Detailed Behaviour of the IWK-SCEF + +When the IWK-SCEF receives a Reporting-Information-Request command from the MME/SGSN it shall deliver the request to the SCEF after applying the roaming policies configured at the IWK-SCEF, as specified in 3GPP TS 23.682 [2]. + +## 5.3 Event Configuration Procedure + +### 5.3.1 General + +This procedure is used between the SCEF and the MME and between the SCEF and the SGSN to configure the monitoring events directly at the MME/SGSN through the T6a/b interface. + +When the procedure is invoked by the SCEF, it is used for configuring the event(s): + +- the number of UEs at a given geographic location. + +This procedure is mapped to the commands Configuration-Information-Request/Answer in the Diameter application specified in clause 6. The tables 5.3.1-1 and 5.3.1-2 detail the involved information elements. + +**Table 5.3.1-1: Configuration Information Request** + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------------|--------------------------------|------|-------------------------------------------------------------------------------------------------------| +| Monitoring Event Configuration (see clause 6.4.2) | Monitoring-Event-Configuration | C | If present, this Information Element shall contain the details of the Monitoring event(s) configured. | +| Supported Features (See 3GPP TS 29.229 [4]) | Supported-Features | O | If present, this Information Element shall contain the list of features supported by the origin host. | + +**Table 5.3.1-2: Configuration Information Answer** + +| Information Element Name | Mapping to Diameter AVP | Cat | Description | +|---------------------------------------------------------------------------------|--------------------------------------|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result
(See 6.3) | Result-Code /
Experimental-Result | M | Result of the request.
Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
Experimental-Result AVP shall be used for T6a/T6b errors.
This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| Supported Features
(See 3GPP TS 29.229 [4]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Monitoring Event Report
(see 3GPP TS 29.336 [5] clause 8.4.3) | Monitoring-Event-Report | C | If an immediate report is available this information element shall contain the requested data available in the MME/SGSN. | +| Monitoring Event-Configuration Status
(see 3GPP TS 29.336 [5] clause 8.4.24) | Monitoring-Event-Config-Status | O | If present it shall contain the status of each monitoring event configuration identified by an SCEF-Reference-ID/SCEF-Reference-ID-Ext. | + +### 5.3.2 Detailed Behaviour of the MME/SGSN + +Monitoring Events configuration and deletion directly at the MME/SGSN for roaming scenarios is not supported. For the non roaming cases, when the Configuration-Information-Request is received from the SCEF, the MME/SGSN shall, in the following order: + +1. Check whether the requesting SCEF is authorized to request the specified service (e.g: number of UEs at a given geographic location). If not, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_UNAUTHORIZED\_REQUESTING\_ENTITY (5510) in the Configuration-Information-Answer. +2. If the TA / RA / ECGI location requested by the SCEF is not served by the MME/SGSN, then the MME/SGSN shall set the Experimental-Result AVP to DIAMETER\_ERROR\_REQUESTED\_LOCATION\_NOT\_SERVED (5650) in the Configuration-Information-Answer. + +If there is an error in any of the above steps then the MME/SGSN shall stop processing and shall return the error code specified in the respective step. + +If the MME/SGSN cannot fulfil the received request for reasons not stated above, it shall stop processing the request and set Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. + +If CIR message includes multiple SCEF Reference IDs (either in SCEF-Reference-ID or in SCEF-Reference-ID-Ext AVPs) and for a SCEF Reference ID the monitoring events cannot be handled, the MME/SGSN shall report the failed SCEF Reference ID to the SCEF with an appropriate status in the Monitoring-Event-Config-Status AVP. + +For the number of UEs in a geographic location monitoring event, for each SCEF-Reference-ID that the MME/SGSN is able to successfully process, the MME/SGSN shall + +- if filtering is not requested (i.e. IMSI-Group-Id was not present in the request) or not supported: +include in the Configuration-Information-Answer, the exact count of the number of UEs that are known to be at the requested location. +- if filtering is requested and (i.e. IMSI-Group-Id was present in the request) and supported: +include in the Configuration-Information-Answer, the exact count of the number of UEs belonging to the provided IMSI Group that are known to be at the requested location. + +If the requested location type is current location, then the MME/SGSN may activate the paging and RAN location reporting procedures (if required) before providing the response in the Configuration-Information-Answer. + +If the monitoring event configuration is for a continuous monitoring (i.e. Monitoring-Duration and/or Maximum-Number-Of-Reports are set) and the deletion criteria are met (i.e. Monitoring-Duration time expired and/or Maximum-Number-Of-Reports are sent) the MME/SGSN shall locally delete the Monitoring event. + +### 5.3.3 Detailed Behaviour of the IWK-SCEF + +Monitoring Events configuration and deletion directly at the MME/SGSN for roaming scenarios is not supported. Consequently the IWK-SCEF is not impacted for Monitoring Events configuration and deletion directly at the MME/SGSN from the SCEF.5.3.4 Detailed Behaviour of the SCEF + +When the SCEF receives Monitoring Event Report AVP from the MME/SGSN or the IWK-SCEF in the CIA command, it shall handle it according to the procedures defined in 3GPP TS 23.682 [2]. + +When the SCEF receives a Monitoring Event Report AVP from the MME/SGSN with a SCEF-Reference-ID/SCEF-Reference-ID-Ext not known by the SCEF, it should discard the Monitoring Event Report received in CIA command. + +## 5.4 Event Configuration Procedure for Roaming + +### 5.4.1 General + +The MME/SGSN shall send the monitoring event configuration information to the IWK-SCEF in roaming scenarios, when the MME/SGSN receives the monitoring event configuration from the HSS. The monitoring event configuration information shall be locally consumed at the IWK-SCEF and the IWK-SCEF shall not route such requests beyond it. + +This procedure is mapped to the commands Configuration-Information-Request/Answer in the Diameter application specified in clause 6. The tables 5.4.1-1 and 5.4.1-2 detail the involved information elements. + +**Table 5.4.1-1: Configuration-Information-Request** + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|--------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Monitoring Event Configuration (see 8.4.2) | Monitoring-Event-Configuration | C | If present, this Information Element shall contain the details of Monitoring event(s). | +| Monitoring Event Report (see 8.4.3) | Monitoring-Event-Report | C | If an immediate report is available this information element shall contain the event reported by the MME/SGSN. The IWK-SCEF may normalize the event report and return it in the Configuration-Information-Answer. | +| Supported Features (See 3GPP TS 29.229 [7]) | Supported-Features | O | If present, this Information Element shall contain the list of features supported by the origin host. | + +**Table 5.4.1-2: Configuration-Information-Answer** + +| Information Element Name | Mapping to Diameter AVP | Cat | Description | +|-------------------------------------------------------------------------------------|------------------------------------------|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result
(See 6.3) | Result-Code /
Experimental-
Result | M | Result of the request.
Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
Experimental-Result AVP shall be used for T6a/b errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| Supported Features
(See 3GPP TS 29.229 [7]) | Supported-
Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Monitoring Event-
Configuration Status
(see 3GPP TS 29.336 [5] clause 8.4.24) | Monitoring-Event-
Config-Status | O | If present it shall contain the status of each monitoring event configuration identified by an SCEF-Reference-ID/SCEF-Reference-ID-Ext. | + +### 5.4.2 Detailed Behaviour of the IWK-SCEF + +When the Configuration-Information-Request is received from the MME/SGSN, the IWK-SCEF shall, in the following order: + +1. Check whether the requesting SCEF, identified by the SCEF-ID is authorized to request the specified service at the VPLMN. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_UNAUTHORIZED\_REQUESTING\_ENTITY (5510) in the Configuration-Information-Answer. +2. Check whether the chargeable party for the monitoring event is authorized to be charged at the VPLMN. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_UNAUTHORIZED\_REQUESTING\_ENTITY (5510) in the Configuration-Information-Answer. + +If the monitoring event configuration also carries the monitoring event report, the IWK-SCEF checks if the immediate events reported by the MME/SGSN needs to be normalized. If yes, the IWK-SCEF shall normalize the event report as per local policies. The IWK-SCEF shall then send the normalized monitoring event report towards the SCEF as a separate Reporting-Information-Request message. + +If the monitoring event configuration is for a continuous monitoring (i.e. Monitoring-Duration and/or Maximum-Number-Of-Reports are set), then the IWK-SCEF shall temporarily store the monitoring event configuration until the deletion criteria for the monitoring event configuration is met. If the deletion criteria are met, the IWK-SCEF shall delete the Monitoring event locally. The stored monitoring event configuration information shall be used during subsequent monitoring event report procedure, to generate the charging records towards the right chargeable party. + +If the received SCEF Reference ID for Deletion (either in SCEF-Reference-ID-for-Deletion or in SCEF-Reference-ID-for-Deletion-Ext AVPs) does not exist, the IWK-SCEF shall set the Experimental-Result-Code to DIAMETER\_ERROR\_CONFIGURATION\_EVENT\_NON\_EXISTANT (5514). + +If the SCEF Reference ID (either in SCEF-Reference-ID or in SCEF-Reference-ID-Ext) exists and the old configuration data could not be replaced by new Configuration event data, the HSS shall set the Experimental-Result-Code to DIAMETER\_ERROR\_CONFIGURATION\_EVENT\_STORAGE\_NOT\_SUCCESSFUL (5513). + +If the IWK-SCEF cannot fulfil the received request for reasons not stated in the above, it shall stop processing the request and set Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. + +The details how to handle expiring of Monitoring events is described in 3GPP TS 23.682 [2] + +### 5.4.3 Detailed Behaviour of the MME/SGSN + +When the MME/SGSN receives the Configuration-Information-Answer from the IWK-SCEF, it shall handle it as follows: For the monitoring event configurations for which the configuration status have changed since last informed to + +the HSS, the MME/SGSN shall report the status to the HSS through a Notify-Request command as specified in clause 5.2.5 of 3GPP TS 29.272 [16]. + +## 5.5 MO-Data Procedure + +### 5.5.1 General + +This procedure shall be used between the MME/SGSN and the SCEF, between the MME/SGSN and the IWK-SCEF and between the IWK-SCEF and the SCEF. + +When the procedure is invoked by the MME or SGSN, it is used to forward mobile originated Non-IP data of a mobile user from the MME or SGSN to the SCEF. The procedure is also invoked by the MME on reception of RRC cause "MO Exception data". + +This procedure is used according to 3GPP TS 23.682 [2] clause 5.13.4. + +The IWK-SCEF may be in the path between the MME/SGSN and the SCEF for roaming cases when the IWK-SCEF is deployed by the operator of the visited PLMN. + +When the procedure is invoked by the IWK-SCEF, it is used to forward mobile originated Non-IP data received from the MME or SGSN to the SCEF. + +This procedure is mapped to the commands MO-Data-Request/Answer (ODR/ODA) in the Diameter application specified in clause 6. + +The tables 5.5.1-1 and 5.5.1-2 detail the involved information elements. + +**Table 5.5.1-1: MO Data Request** + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|-------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity
(See 6.4.16) | User-Identifier | M | This Information Element shall be present and shall contain the identity of the UE. This is a grouped AVP which shall contain the IMSI. | +| EPS Bearer Identity
(See 6.4.17) | Bearer-Identifier | M | This information element shall be present and shall contain either the identity of the EPS bearer identifying the T6a connection, or the NSAPI of the PDP context identifying the T6b connection, for the Non-IP data delivery. | +| Non IP data
(See 6.4.19) | Non-IP-Data | C | This information element shall contain the Non-IP data to be delivered to the SCEF.
This Information Element shall be present when the request conveys Non-IP data. | +| Supported Features
(See 3GPP TS 29.229 [4]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| MO Exception Data Counter
(see 6.4.27) | RR-Cause-Counter | C | The MME shall include this Information Element when MME needs to send a non-zero counter value for the MO Exception Data Counter. The timestamp in the counter shall be set with the time at which the counter value increased from 0 to 1. | + +**Table 5.5.1-2: MO Data Answer** + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|--------------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result
(See 6.3) | Result-Code /
Experimental-Result | M | Result of the request.
Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
Experimental-Result AVP shall be used for T6a/b errors. This is a grouped AVP, which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| Supported Features
(See 3GPP TS 29.229 [4]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +### 5.5.2 Detailed Behaviour of the MME/SGSN + +The MME shall make use of this procedure over a T6a connection identified by its EPS bearer identity and previously established with the SCEF to forward the Non-IP data received from the UE to the SCEF or to an IWK-SCEF when deployed for a roaming case. + +The SGSN shall make use of this procedure over a T6b connection identified by the NSAPI of the PDP context, and previously established with the SCEF, to forward the Non-IP data received from the UE to the SCEF or to an IWK-SCEF when deployed for a roaming case. + +The MME shall increment the "MO Exception data counter" by one each time the MME has received the RRC cause "MO Exception data". The MME may defer sending a MO Data command message to report a non-zero value for the MO Exception Data Counter based on local configuration. + +If the MME has sent the RRC-Cause-Counter for RRC Cause "MO Exception data" in the MO Data Request command the MME shall reset the RRC-Cause-Counter when receiving MO Data Answer command. + +When receiving a Permanent Failure Result-Code/Experimental-Result, the MME or SGSN shall initiate a PDN disconnection procedure or Detach procedure towards the UE and if the permanent failure is different from DIAMETER\_ERROR\_INVALID\_EPS\_BEARER and different from DIAMETER\_ERROR\_USER\_UNKNOWN, the MME or SGSN shall make use of the "Connection Management by MME/SGSN" Procedure (see clause 5.7) to release the T6a/b connection between the MME/SGSN and the SCEF. + +### 5.5.3 Detailed Behaviour of the SCEF + +When the SCEF receives a MO Data Request from the MME/SGSN or the IWK-SCEF, the SCEF shall, in the following order: + +- Check that the User Identity exists in the SCEF. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN in the MO Data Answer; +- Check if, for this user, a bearer context exists. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_INVALID\_EPS\_BEARER in the MO Data Answer; +- Process the delivery of the data (if available) to the SCS/AS and/or process the RRC Cause Counter (if available). If the processing of either of them is not successful, return an appropriate Diameter error code, otherwise return a Result code set to DIAMETER\_SUCCESS to the MME/SGSN or IWK-SCEF. If the data delivery to the SCS/AS has failed due to there being no NIDD configuration context with an SCS/AS, set the Experimental-Result to DIAMETER\_ERROR\_NIDD\_CONFIGURATION\_NOT\_AVAILABLE in the MO Data Answer. + +NOTE: The Diameter Result-Code / Experimental-Result returned by the SCEF can depend on the error returned by the SCS/AS to the SCEF. The interface between the SCEF and the SCS/AS is out of scope of 3GPP. + +### 5.5.4 Detailed Behaviour of the IWK-SCEF + +When the IWK-SCEF receives a MO Data Request from the MME or SGSN, it shall forward the request to the SCEF. + +When the IWK-SCEF receives a MO Data Answer from the SCEF, it shall forward the answer to the MME or SGSN. + +## 5.6 MT Data Procedure + +### 5.6.1 General + +This procedure shall be used between the SCEF and the MME or SGSN, between the SCEF and the IWK-SCEF and between the IWK-SCEF and the MME or SGSN. + +When the procedure is invoked by the SCEF, it is used to forward mobile terminated Non-IP data of a mobile user from the SCEF to the MME or SGSN. + +This procedure is used according to 3GPP TS 23.682 [2] clause 5.13.3. + +The IWK-SCEF may be in the path between the SCEF and the MME/SGSN for roaming cases when the IWK-SCEF is deployed by the operator of the visited PLMN. + +When the procedure is invoked by the IWK-SCEF, it is used to forward mobile terminated Non-IP data received from the SCEF to the MME or SGSN. + +This procedure is mapped to the commands MT-Data-Request/Answer (TDR/TDA) in the Diameter application specified in clause 6. + +The tables 5.6.1-1 and 5.6.1-2 detail the involved information elements. + +NOTE: The corresponding message name in 3GPP TS 23.682 [2] is "NIDD Submit Request". + +**Table 5.6.1-1: MT Data Request** + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|----------------------------------------------------------|-----------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity
(See 6.4.16) | User-Identifier | M | This Information Element shall be present and shall contain the identity of the UE. This is a grouped AVP which shall contain the IMSI. | +| EPS Bearer Identity
(See 6.4.17) | Bearer-Identifier | M | This information element shall be present and shall contain either the identity of the EPS bearer identifying the T6a connection, or the NSAPI of the PDP context identifying the T6b connection, for the Non-IP data delivery. | +| Non-IP Data
(See 6.4.19) | Non-IP-Data | C | This information element shall contain the Non-IP data to be delivered to the MME or SGSN.
This Information Element shall be present when the request conveys Non-IP data. | +| SCEF Wait Time
(See 6.4.24) | SCEF-Wait-Time | O | This information element, when present, shall indicate the timestamp (in UTC) until which the SCEF expects a response. | +| Maximum Retransmission Time
(See 3GPP TS 29.338 [27]) | Maximum-Retransmission-Time | O | This information element, when present, shall indicate the maximum retransmission time (in UTC) until which the SCEF is capable to retransmit the MT Non-IP Data. | +| Supported Features
(See 3GPP TS 29.229 [4]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +**Table 5.6.1-2: MT Data Answer** + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------------------|--------------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result
(See 6.3) | Result-Code /
Experimental-Result | M | This information element shall contain the Result of the request. The Result-Code AVP shall be used to indicate success or errors as defined in the Diameter Base Protocol. The Experimental-Result AVP shall be used for T6a/b errors. This is a grouped AVP, which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| Requested Retransmission Time
(See 3GPP TS 29.338 [27]) | Requested-Retransmission-Time | O | This information element may be present if the Experimental-Result-Code is set to DIAMETER_ERROR_USER_TEMPORARILY_UNREACHABLE and the Maximum Retransmission Time information element is present in the MT Data Request. It may be included if the UE is using a power saving mechanism (such as extended idle mode DRX) and the UE is currently not reachable.
When present, this shall indicate the retransmission time (in UTC) at which the SCEF is requested to retransmit the MT Non-IP Data. The Requested Retransmission Time shall not exceed the Maximum Retransmission Time received from the SCEF. | +| Supported Features
(See 3GPP TS 29.229 [4]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| TDA Flags
(See 6.4.31) | TDA-Flags | O | This Information Element contains a bit mask. See clause 6.4.31 for the meaning of the bits and the condition for each bit to be set or not. | + +### 5.6.2 Detailed Behaviour of the SCEF + +The SCEF shall make use of this procedure over a T6a connection identified by its EPS Bearer Identity, and previously established with the MME, to forward the Non-IP data received from the SCS/AS to the MME or to an IWK-SCEF when deployed for a roaming case. + +The SCEF shall make use of this procedure over a T6b connection identified by the NSAPI of the PDP context, and previously established with the SGSN, to forward the Non-IP data received from the SCS/AS to the SGSN or to an IWK-SCEF when deployed for a roaming case. + +The SCEF shall check if a bearer context exists for the user before sending the request. + +The SCEF may include the Maximum-Retransmission-Time AVP in the MT Data Request to indicate the maximum retransmission time for when it is capable to retransmit the Non-IP Data. + +If the MT Data Answer includes the Requested-Retransmission-Time AVP, the SCEF shall retransmit the MT Non-IP Data at the requested retransmission time. + +### 5.6.3 Detailed Behaviour of the MME/SGSN + +When the MME or SGSN receives a MT Data Request from the SCEF or the IWK-SCEF, the MME or SGSN shall, in the following order: + +- Check that the User Identity exists in the MME or SGSN. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN in the MT Data Answer; +- Check whether, for this user, a bearer context exists. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_INVALID\_EPS\_BEARER in the MT Data Answer. +- Process the data delivery to the UE and: + +- if it is successful, return a Result code set to DIAMETER\_SUCCESS to the SCEF or IWK-SCEF; in addition, if the successful delivery was acknowledged by the eNodeB, the MME/SGSN shall set the "Success Acknowledged Delivery" bit within the TDA-Flags AVP. +- return an Experimental-Result set to DIAMETER\_ERROR\_USER\_TEMPORARILY\_UNREACHABLE, if the UE is using a power saving function (e.g. extended idle mode DRX or UE Power Saving Mode as defined in 3GPP TS 23.682 [27]) and the UE is expected to not be reachable shortly or, based on MME or SGSN implementation, within the time indicated by the SCEF-Wait-Time; + +The MME or SGSN shall set the Not Reachable for NIDD flag and store the SCEF Host and Realm for which this flag is set; + +If the MT Data Request includes the Maximum-Retransmission-Time AVP, the MME or SGSN may additionally include the Requested-Retransmission-Time AVP requesting the SCEF to retransmit the Non-IP Data at a later time prior to the Maximum Retransmission Time; + +The MME or SGSN shall then update the SCEF, as specified in clause 5.7, when it detects that the UE is reachable or about to become reachable and the Not Reachable for NIDD flag is set. If the MME or SGSN included the Requested-Retransmission-Time AVP in the MT Data Answer, the MME or SGSN shall do so only if the UE becomes reachable before the Requested Retransmission Time, i.e. the MME or SGSN shall reset the Not Reachable for NIDD flag when the Requested-Retransmission-Time expires if the UE has not become reachable beforehand; + +- return an Experimental-Result set to DIAMETER\_ERROR\_UNREACHABLE\_USER, if the UE is not reachable; +- otherwise return an appropriate Diameter error code. + +### 5.6.4 Detailed Behaviour of the IWK-SCEF + +When the IWK-SCEF receives a MT Data Request from the SCEF, it shall forward the request to the MME or SGSN. + +When the IWK-SCEF receives a MT Data Answer from the MME or SGSN, it shall forward the answer to the SCEF. + +## 5.7 Connection Management by MME/SGSN Procedure. + +### 5.7.1 General + +This procedure shall be used between the MME/SGSN and the SCEF, between the MME/SGSN and the IWK-SCEF and between the IWK-SCEF and the SCEF. + +When the procedure is invoked by the MME or SGSN, it is used: + +- to establish a T6a/b connection between the MME/SGSN and the SCEF; +- to update the parameters (e.g. RAT-Type) for a T6a/b connection between the MME/SGSN and the SCEF; +- to update the status of a T6a/b connection between the MME/SGSN and the SCEF, e.g. to indicate to the SCEF that the UE has become or is about to become reachable when MT non-IP data is pending at the SCEF for a UE using a power saving function; + +This procedure is used according to 3GPP TS 23.682 [2] clause 5.13.1 and 5.13.5 and 5.13.6. The IWK-SCEF may be in the path between the MME/SGSN and the SCEF for roaming cases when the IWK-SCEF is deployed by the operator of the visited PLMN. + +When the procedure is invoked by the IWK-SCEF, it is used to forward the Connection Management Request received from the MME or SGSN to the SCEF. + +This procedure is mapped to the commands Connection-Management-Request/Answer (CMR/CMA) in the Diameter application specified in clause 6. + +The tables 5.7.1-1 and 5.7.1-2 detail the involved information elements. + +**Table 5.7.1-1: Connection Management Request** + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------------------|-------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity
(See 6.4.16) | User-Identifier | M | This Information Element shall be present and shall contain the identity of the UE. This is a grouped AVP which shall contain the IMSI. | +| EPS Bearer Identity
(See 6.4.17) | Bearer-Identifier | M | This Information Element shall be present and shall contain either the identity of the EPS bearer identifying the T6a connection, or the NSAPI of the PDP context of the T6b connection, to which the request applies. | +| T6a/b Connection Action
(See 6.4.18) | Connection-Action | M | This Information element shall be present and shall contain a T6a/b connection management action indicating a T6a/b connection establishment or a T6a/b connection release or a T6a/b connection update. | +| APN
(See 6.4.20) | Service-Selection | C | This Information element shall contain the APN the user wants to connect to.
It shall be present if the request is for a T6a/b connection establishment. | +| Serving PLMN Rate Control
(See 6.4.21) | Serving-PLMN-Rate-Control | O | If present, this information element shall contain the Serving PLMN rate control set by the MME. | +| CMR Flags
(See 6.4.25) | CMR-Flags | O | This Information Element contains a bit mask. See clause 6.4.25 for the meaning of the bits and the condition for each bit to be set or not. | +| Maximum UE Availability Time
(See 3GPP TS 29.338 [27]) | Maximum-UE-Availability-Time | O | This information element may be included, if available, if the Connection-Action AVP indicates a T6a/b connection update and the UE-Reachable-Indicator is set in the CMR-Flags AVP.
When present, it shall indicate the timestamp (in UTC) until which a UE using a power saving mechanism (such as extended idle mode DRX) is expected to be reachable for MT Non-IP Data Delivery.
This information may be used by the SCEF to prioritize the retransmission of MT Non-IP Data to UEs using a power saving mechanism. | +| Extended PCO | Extended-PCO | C | This Information Element shall be present, if the MME or SGSN receives Extended PCO information from the UE. | +| 3GPP Charging Characteristics
(See 3GPP TS 32.298 [30]) | 3GPP-Charging-Characteristics | C | This Information element shall contain the PDN Connection Charging Characteristics data for an APN Configuration with SCEF-based NIDD mechanism.
It shall be present if the request is for a T6a/b connection establishment and may be present if the request is for a T6a/b connection update. | +| RAT-Type
(See 3GPP TS 29.212 [10]) | RAT-Type | C | This Information Element shall contain the used RAT Type.
It shall be present if the request is for a T6a/b connection establishment or for a T6a/b connection update. | +| Supported Features
(See 3GPP TS 29.229 [4]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Terminal Information
(See 3GPP TS 29.272 [16]) | Terminal-Information | C | This Information Element shall contain the identity of the UE.
It shall be present if available. | +| Visited PLMN ID
(See 3GPP TS 29.272 [16]) | Visited-PLMN-Id | C | This Information Element shall contain the identity (MCC and MNC) of serving PLMN.
It shall be present if the request is for a T6a/b connection establishment or for a T6a/b connection update. | +| APN Rate Control Status
(see 6.4.36) | APN-Rate-Control-Status | O | May be present if the request is for a T6a/b connection establishment. | + +**Table 5.7.1-2: Connection Management Answer** + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|-------------------------------------------------------|--------------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result
(See 6.3) | Result-Code /
Experimental-Result | M | Result of the request.
Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
Experimental-Result AVP shall be used for T6a/b errors. This is a grouped AVP, which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| NIDD Charging Identifier
(See 3GPP TS 32.299 [22]) | PDN-Connection-Charging-Id | C | This Information element is defined in 3GPP TS 32.253 [23] and shall be present if the answer is for a T6a/b connection establishment. | +| Extended PCO | Extended-PCO | C | This Information Element shall be present, if the SCEF needs to send Extended PCO information to the UE. | +| Supported Features
(See 3GPP TS 29.229 [4]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| APN Rate Control Status (see 6.4.36) | APN-Rate-Control-Status | O | May be present if the response is for a T6a/b connection release. | + +### 5.7.2 Detailed Behaviour of the MME/SGSN + +The MME or SGSN shall make use of this procedure to request one of the following T6a/b connection management actions: + +- for a T6a/b connection establishment, the MME shall: + - include the user's IMSI. + - fill the EPS Bearer Identity information element with either the identity of the EPS bearer that MME allocated to the Non-IP PDN connection, or the NSAPI of the PDP context used by the SGSN for the Non-IP connection, as described in 3GPP TS 23.682 [2]; + - if Serving PLMN Rate Control is configured, the MME shall include the Serving PLMN Rate Control information as described in 3GPP TS 23.401 [25]; +- for a T6a/b connection release, the MME or SGSN shall: + - fill the EPS Bearer Identity information element with the identity of the EPS bearer of the T6a connection, or the NSAPI of the PDP context of the T6b connection, which is released as described in 3GPP TS 23.682 [2]; + - upon getting the Connection Management Answer from the SCEF, delete the T6a/b connection context; +- for a T6a/b connection update, the MME or SGSN shall: + - fill the EPS Bearer Identity information element with the identity of the EPS bearer of the T6a connection, or the NSAPI of the PDP context of the T6b connection, that needs to be updated; + - set the UE-Reachable-Indicator in the CMR-Flags AVP if the UE has become or is about to become reachable. The MME or SGSN may additionally include the Maximum UE Availability Time AVP, if available, to indicate the timestamp (in UTC) until which a UE using a power saving mechanism (such as extended idle mode DRX) is expected to be reachable for MT Non-IP Data Delivery; + - upon getting the Connection Management Answer from the SCEF, reset the Not Reachable for NIDD flag if this flag was set and if the UE-Reachable-Indicator was set in the CMR-Flags AVP in the Connection Management Request; + - if Serving PLMN Rate Control needs to be added or updated, the MME shall include Serving PLMN Rate Control information as described in 3GPP TS 23.401 [25]. + +NOTE: If the UE has several T6a/b connections to the same SCEF, for which Non-IP data is pending, the MME or SGSN initiates a T6a/b connection update for only one of the T6a/b connections towards this SCEF; the UE can have either T6a or T6b connections, but not both simultaneously. + +If the MME or SGSN receives the Extended-PCO AVP in the Connection Management Answer from the SCEF, the MME or SGSN shall forward the Extended-PCO to the UE transparently, as specified in 3GPP TS 24.301 [28]. + +### 5.7.3 Detailed Behaviour of the SCEF + +When the SCEF receives a Connection Management Request from the MME or SGSN the SCEF shall, in the following order: + +- check that the User Identity exists in the SCEF. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN in the Connection Management Answer; +- check that the T6a/b connection action indicates a T6a/b connection establishment, a T6a/b connection release or a T6a/b connection update. If not, the Experimental-Result shall be set to DIAMETER\_ERROR\_OPERATION\_NOT\_ALLOWED in the Connection Management Answer; +- if the T6a/b connection action indicates a T6a/b connection establishment: + - check whether a valid NIDD configuration exists for the UE at the SCEF; + +If not, the SCEF shall: + +- reject the Connection Management Request, with Experimental-Result set to DIAMETER\_ERROR\_NIDD\_CONFIGURATION\_NOT\_AVAILABLE in the Connection Management Answer, or +- accept the Connection Management Request, and initiate a NIDD Configuration procedure with a default SCS/AS configured in the SCEF and the MSISDN or an external ID obtained from the HSS, as specified in 3GPP TS 29.336 [5] clause 7.2.3.2. If such NIDD Configuration procedure fails, the SCEF shall reject the Connection Management Request, with Experimental-Result set to DIAMETER\_ERROR\_NIDD\_CONFIGURATION\_NOT\_AVAILABLE in the Connection Management Answer; +- create an EPS bearer context; +- store the MME or SGSN Identity identified by the Origin-Host AVP of the T6a/b Connection Management Request, and the MME or SGSN realm identified by the Origin-Realm AVP of the T6a/b Connection Management Request in the EPS bearer context; +- include the Extended-PCO AVP in the Connection Management Answer, if the Extended PCO information (e.g. APN Rate Control information) needs to be provided to the UE; +- if Serving PLMN Rate Control is provided by the MME, restrict the number of messages for the downlink to not exceed the values provided in Serving PLMN Rate Control. If it is not provided and Serving PLMN Rate Control is active, then continue using the previously provided values; +- If successful, Result shall be set to DIAMETER\_SUCCESS in the Connection Management Answer; +- if the T6a/b connection action indicates a T6a/b connection release: + - check whether, for this user and the received EPS bearer ID, a T6a connection context exists. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_INVALID\_EPS\_BEARER in the Connection Management Answer; + - include the Extended-PCO AVP in the Connection Management Answer, if the Extended PCO information needs to be provided to the UE; + - delete the T6a/b connection context at the SCEF. If successful, Result code shall be set to DIAMETER\_SUCCESS in the Connection Management Answer; +- if the T6a/b connection action indicates a T6a connection update: + +- check whether, for this user and the received EPS Bearer Identity, a T6a/b connection context exists. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_INVALID\_EPS\_BEARER in the Connection Management Answer; +- if successful: + - if Serving PLMN Rate Control is provided by the MME, restrict the number of messages for the downlink to not exceed the values provided in Serving PLMN Rate Control. If it is not provided and Serving PLMN Rate Control is active, then continue using the previously provided values; + - include the Extended-PCO AVP in the Connection Management Answer, if the Extended PCO information (e.g. APN Rate Control information) needs to be provided to the UE; + - store the MME or SGSN Identity identified by the Origin-Host AVP of the T6a/b Connection Management Request and the MME or SGSN realm identified by the Origin-Realm AVP of the T6a/b Connection Management Request, if the MME or SGSN identity has changed, in the bearer context, and the Result shall be set to DIAMETER\_SUCCESS in the Connection Management Answer; + - if the UE-Reachable-Indicator was set in the CMR-Flags AVP, forward any MT Non-IP data pending for any T6a/b connection for this UE, to the MME or SGSN. + +If the Serving-PLMN-Rate-Control AVP is included in the Connection Management Request message from the MME, the SCEF shall enforce the Serving PLMN Rate Control as specified in 3GPP TS 23.401 [12] clause 4.7.7.2. + +### 5.7.4 Detailed Behaviour of the IWK-SCEF + +When the IWK-SCEF receives a Connection Management Request from the MME or SGSN, it shall forward the request to the SCEF. + +When the IWK-SCEF receives a Connection Management Answer from the SCEF, it shall forward the answer to the MME or SGSN. + +## 5.8 Connection Management by SCEF Procedure + +### 5.8.1 General + +This procedure shall be used between the SCEF and the MME/SGSN, and between the SCEF and the MME/SGSN via the IWK-SCEF acting as a Diameter proxy agent for roaming cases. + +When the procedure is invoked by the SCEF, it is used + +- to update the parameters (e.g. Extended PCO information) associated to a T6a/b connection between the MME/SGSN and the SCEF; +- to release a T6a/b connection between MME/SGSN and SCEF. + +This procedure is used according to 3GPP TS 23.682 [2]. The IWK-SCEF may be in the path between the MME/SGSN and the SCEF for roaming cases when the IWK-SCEF is deployed by the operator of the visited PLMN. + +This procedure is mapped to the commands Connection-Management-Request/Answer (CMR/CMA) in the Diameter application specified in clause 6. + +The tables 5.8.1-1 and 5.8.1-2 detail the involved information elements. + +**Table 5.8.1-1: Connection Management SCEF Request** + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|-------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity
(See 6.4.16) | User-Identifier | M | This Information Element shall be present and shall contain the identity of the UE. This is a grouped AVP containing the IMSI. | +| EPS Bearer Identity
(See 6.4.17) | Bearer-Identifier | M | This Information Element shall be present and shall contain either the identity of the EPS bearer identifying the T6a connection, or the NSAPI of the PDP context identifying the T6b connection, to which the request applies. | +| T6a/b Connection Action
(See 6.4.18) | Connection-Action | M | This Information element shall be present and shall contain a T6a/b connection management action indicating a T6a/b connection update. | +| Extended PCO
(see 6.4.26) | Extended-PCO | C | This Information Element shall be present if the SCEF needs to send updated Extended PCO information (e.g. APN Rate Control information) to the UE. | +| Supported Features
(See 3GPP TS 29.229 [4]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +**Table 5.8.1-2: Connection Management SCEF Answer** + +| Information Element Name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|-----------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result
(See 6.3) | Result-Code / Experimental-Result | M | Result of the request.
Result-Code AVP shall be used for errors defined in the Diameter Base Protocol.
Experimental-Result AVP shall be used for T6a/b errors. This is a grouped AVP, which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| Supported Features
(See 3GPP TS 29.229 [4]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +### 5.8.2 Detailed Behaviour of the SCEF + +The SCEF shall make use of this procedure to send the updated Extended PCO information (e.g. APN Rate Control information) to the UE during T6a/b connection update, if needed. If APN Rate Control information is included in the Extended-PCO AVP within the Connection Management SCEF Request message from the SCEF, the SCEF shall enforce the APN Rate Control as specified in 3GPP TS 23.401 [12] clause 4.7.7.3. + +The SCEF shall make use of this procedure to request the release of the T6a/b connection. + +### 5.8.3 Detailed Behaviour of the MME/SGSN + +When the MME or SGSN receives a Connection Management SCEF Request from the SCEF or the IWK-SCEF, the MME or SGSN shall, in the following order: + +- check that the User Identity exists in the MME or SGSN. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN in the Connection Management SCEF Answer; +- check that the T6a/b connection action indicates a T6a/b connection update or T6a/b connection release. If not, the Experimental-Result shall be set to DIAMETER\_ERROR\_OPERATION\_NOT\_ALLOWED in the Connection Management SCEF Answer; + +- check whether, for this user and the received EPS Bearer Identity, a T6a/b connection context exists. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_INVALID\_EPS\_BEARER in the Connection Management SCEF Answer; +- if the T6a/b connection action indicates a T6a/b connection update: + - if the Extended-PCO AVP is received, forward the Extended-PCO to the UE, as specified in 3GPP TS 24.301[28]. If successful, the Result code shall be set to DIAMETER\_SUCCESS in the Connection Management SCEF Answer. +- if the T6a/b connection action indicates T6a/b connection release, delete the T6a/b connection context at the MME/SGSN. If successful, the Result code shall be set to DIAMETER\_SUCCESS in the Connection Management SCEF Answer. + +### 5.8.4 Detailed Behaviour of the IWK-SCEF + +When the IWK-SCEF receives a Connection Management SCEF Request from the SCEF, it shall forward the request to the MME or SGSN. + +When the IWK-SCEF receives a Connection Management SCEF Answer from the MME or SGSN, it shall forward the answer to the SCEF. + +# --- 6 Protocol Specification and Implementation + +## 6.1 Introduction + +### 6.1.1 Use of Diameter Base Protocol + +The Diameter base protocol as specified in IETF RFC 6733 [32] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and error codes as specified in this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) shall be used unmodified. + +### 6.1.2 Securing Diameter Messages + +For secure transport of Diameter messages, see 3GPP TS 33.210 [4]. + +### 6.1.3 Accounting Functionality + +Accounting functionality (Accounting Session State Machine, related command codes and AVPs) shall not be used on the T6a/T6b interface, T6ai/T6bi interface and the T7 interface. + +### 6.1.4 Use of Sessions + +Diameter sessions shall be implicitly terminated between: + +- the MME/SGSN and the SCEF, for the T6a/T6b interface; +- the MME/SGSN and the IWK-SCEF, for the T6ai/T6bi interface and +- the IWK-SCEF and the SCEF for the T7 interface. + +An implicitly terminated session is one for which the server does not maintain state information. The client shall not send any re-authorization or session termination requests to the server. + +The Diameter base protocol includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions. + +The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value NO\_STATE\_MAINTAINED (1), as described in IETF RFC 6733 [32]. As a consequence, the server shall not maintain any state information about this session and the client shall not send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses. + +### 6.1.5 Transport Protocol + +Diameter messages over the T6a/T6b, T6ai/T6bi and T7 interface shall make use of SCTP IETF RFC 4960 [7] as transport protocol. + +### 6.1.6 Routing Considerations + +#### 6.1.6.1 Routing Considerations for Monitoring Event related Requests + +This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host for Monitoring Event related requests. + +The MME/SGSN shall use the SCEF-ID and the SCEF realm previously received over S6a/b for a monitoring event configuration as the Destination-Host AVP and the Destination-Realm AVP in the Reporting-Information-Request for the monitoring event reports sent over the T6a/T6b or T6ai/bi interface. + +The MME/SGSN shall use the pre-configured IWK-SCEF identify and the pre-configured IWK-SCEF realm as the Destination-Host AVP and the Destination Realm AVP in the Configuration-Information-Request for the monitoring event configuration sent over the T6ai/bi interface. + +The IWK-SCEF behaves as a Diameter Proxy agent according to IETF RFC 6733 [32] for the Reporting-Information-Request received from the MME/SGSN over the T6ai/bi interface and shall forward these requests to the SCEF over the T7 interface by keeping unchanged the Destination Realm and Destination Host AVPs. + +For monitoring events directly configured at the MME/SGSN by the SCEF, if the SCEF knows the address/name of the MME/SGSN, both the Destination-Realm AVP and the Destination-Host AVP shall be present in the request. Otherwise, only the Destination-Realm AVP shall be present and the command shall be routed to the next Diameter node. Consequently, the Destination-Host AVP is declared as optional in the ABNF for all Monitoring Event related requests initiated by the SCEF. + +The Destination-Realm AVP is declared as mandatory in the ABNF for all Monitoring Event related requests. The Destination-Host AVP is declared as optional in the ABNF description of the Reporting-Information-Request and of the Configuration Information-Request. + +#### 6.1.6.2 Routing Considerations for Non-IP Data Related Requests + +This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host for Non-IP Data related requests. + +The MME or SGSN shall use the SCEF-ID and the SCEF realm that it received in the subscribed APN associated to the T6a/b connection at its establishment as the Destination-Host AVP and the Destination realm AVP in the Non-IP data related request commands sent over the T6a/b and T6ai/bi interfaces. + +The Destination-Host AVP is declared as optional and the Destination realm AVP as mandatory in the ABNF description of the Non-IP data related requests initiated by the MME or SGSN. + +NOTE 1: For roaming cases, the routing of MME or SGSN initiated request commands to the IWK-SCEF relies on the Destination Realm AVP as according to the Diameter base protocol. + +NOTE 2: The Diameter implicitly terminated sessions and their Session ID for the Non-IP data related traffic are end to end between the MME/SGSN and the SCEF. + +The IWK-SCEF behaves as a Diameter Proxy agent according to IETF RFC 6733 [32] for the Non-IP related requests received from the MME or SGSN over the T6ai/bi interfaces and shall forward these requests to the SCEF over the T7 interface by keeping unchanged the Destination Realm and Destination Host AVPs. + +The SCEF obtains the Destination-Host AVP and the Destination-Realm AVP to use in the Non-IP data related requests towards an MME or SGSN from the Origin-Host AVP and the Origin-Realm AVP received in previous Non-IP Data related requests from the MME or SGSN. The Origin-Realm AVP in the requests received by the SCEF in roaming cases should contain the domain name of the network to which the MME or SGSN belongs, encoded as specified in clause 19.2 of 3GPP TS 23.003 [24]. + +The Destination-Host AVP is declared as optional and the Destination realm AVP as mandatory in the ABNF for the Non-IP Data related requests initiated by the SCEF. + +The IWK-SCEF behaves as a Diameter Proxy agent according to IETF RFC 3588 [3] for the Non-IP related requests received from the SCEF over the T7 interface and shall forward these requests to the MME or SGSN over the T6ai/bi interfaces by keeping unchanged the Destination Realm and Destination Host AVPs. + +#### 6.1.6.3 Handling of the Vendor-Specific-Application-Id AVP + +If the Vendor-Specific-Application-ID AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node, and it shall not be used for routing purposes. + +### 6.1.7 Advertising Application Support + +The SCEF, MME, SGSN and the IWK-SCEF shall advertise support of the Diameter T6a/T6b Application by including the value of the application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +NOTE: Even though the reference point between the MME/SGSN and the IWK-SCEF is called T6ai/T6bi respectively and the reference point between the IWK-SCEF and the SCEF is called T7, all these reference points use the same Diameter Application ID. + +The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the Diameter node as per IETF RFC 6733 [32]. + +### 6.1.8 Diameter Application Identifier + +The T6a/T6b interface protocol shall be defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP (
Configuration and reporting of monitoring events
This feature is applicable to from an SCEF with CIR/CIA command pair and the reporting of events to the SCEF with RIR/RIA command pair.
If the MME/SGSN does not support this feature, the SCEF shall not send monitoring event configurations to the HSS within CIR.
| +| 1 | NIDD | O |Support of Non-IP Data service over T6a/b
This feature is applicable to CMR/CMA, ODR/ODA and TDR/TDA command pairs.
If the SCEF does not indicate support of this feature in an CMA, the MME or SGSN may store this information and not send any further CMR commands to that SCEF.
| +| 2 | Filtering | O |Filtering Number of UEs present at given location by IMSI-Group
This feature is applicable to the CIR/CIA command pair.
If the MME/SGSN does not support this feature, the SCEF shall interpret the reported number of UEs per location as not being filtered by the provided IMSI-Group-Id.
| +| 3 | Extended Reference IDs | O |Extended Reference IDs
This feature is applicable for the CIR/CIA and RIR/RIA command pairs.
If the SCEF detects that the MME/SGSN does not support this feature, it shall refrain from sending CIR commands containing 64-bit long SCEF Reference IDs.
If the MME/SGSN detects that the SCEF does not support this feature, it shall refrain from sending RIR commands containing 64-bit long SCEF Reference IDs.
| +|Feature bit: The order number of the bit within the Supported-Features AVP, e.g. "1".
Feature: A short name that can be used to refer to the bit and to the feature, e.g. "MONTE".
M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O").
Description: A clear textual description of the feature.
This AVP and all AVPs within this grouped AVP shall have the 'M' bit cleared. | | +| Monitoring-Duration | 3GPP TS 29.336 [7] | It shall contain the number of seconds for which network status reporting shall be performed. | | +| Network-Area-Info-List | 3GPP TS 29.154 [8] | It contains the network area information which is coded as specified in 3GPP TS 29.274 [9] in Presence Reporting Area Action IE, starting from octet 9. | | +| OC-OLR | IETF RFC 7683 [5] | Contains the necessary information to convey an overload report. | | +| OC-Supported-Features | IETF RFC 7683 [5] | Defines the support for the Diameter overload indication conveyance by the sending node. | | +| SCEF-ID | 3GPP TS 29.336 [7] | It shall contain the identity of the SCEF which has requested the network status reporting. | | +| SCEF-Reference-ID | 3GPP TS 29.336 [7] | It contains the identifier provided by the SCEF. | | +| Supported-Features | 3GPP TS 29.229 [6] | If present, this AVP informs the destination host about the features that the origin host requires to successfully complete this command exchange. | | +| NOTE: AVPs marked with a supported feature are applicable as described in subclause 5.4.2. | | | | + +### 5.4.2 Use of the Supported-Features AVP on the Ns reference point + +When new functionality is introduced on the Ns reference point, it should be defined as optional. If backwards incompatible changes cannot be avoided, the new functionality shall be introduced as a new feature and support advertised with the Supported-Features AVP. Unless otherwise stated, the use of the Supported-Features AVP on the Ns reference point shall be compliant to the usage of the Supported-Features AVP on the Cx reference point and consistent with the procedures for the dynamic discovery of supported features as defined in subclause 7.2 of 3GPP TS 29.229 [6]. + +When extending the application by adding new AVPs for a feature, the new AVPs shall have the M bit cleared and the AVP shall not be defined mandatory in the command ABNF. + +As defined in 3GPP TS 29.229 [6], the Supported-Features AVP is of type grouped and contains the Vendor-Id, Feature-List-ID and Feature-List AVPs. On the all reference points as specified in this specification, the Supported-Features AVP is used to identify features that have been defined by 3GPP and hence, for features defined in this document, the Vendor-Id AVP shall contain the vendor ID of 3GPP (10415). If there are multiple feature lists defined for the reference point, the Feature-List-ID AVP shall differentiate those lists from one another. + +The Supported-Features AVP shall be included in every NSR and NSA command if supported by the RCAF and SCEF respectively. + +The Table 5.4.2.1 defines the features applicable to the Ns reference point for the feature list with a Feature-List-ID of 1. + +**Table 5.4.2.1: Features of Feature-List-ID 1 used in Ns** + +| Feature bit | Feature | M/O | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----|-------------| +| Feature bit: The order number of the bit within the Feature-List AVP where the least significant bit is assigned number "0".
Feature: A short name that can be used to refer to the bit and to the feature, e.g. "EPS".
M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O") in this 3GPP Release.
Description: A clear textual description of the feature. | | | | + +NOTE: This table is a placeholder for when any supported features are added to Ns. There are no supported features in this release. + +## 5.5 Ns specific Experimental-Result-Code AVP values + +### 5.5.1 General + +This clause defines result code values that shall be supported by Diameter implementations that conform to this specification. + +### 5.5.2 Success + +Result Codes that fall into the Success category are used to inform a peer that a request has been successfully completed. The Result-Code AVP values defined in Diameter BASE Protocol IETF RFC 6733 [15] are applied. + +### 5.5.3 Permanent Failures + +Errors that fall into the Permanent Failures category shall be used to inform the peer that the request has failed. The Result-Code AVP values defined in Diameter Base Protocol IETF RFC 6733 [15] are applied. + +### 5.5.4 Transient Failures + +Errors that fall within the Transient failures category are used to inform a peer that the request could not be satisfied at the time it was received, but may be able to satisfy the request in the future. + +The Result-Code AVP values defined in Diameter Base Protocol IETF RFC 6733 [15] are applicable. + +## 5.6 Ns messages + +### 5.6.1 Command-Code Values + +This clause defines the Command-Code values for the Ns interface application as allocated by IANA from the vendor-specific namespace defined in IETF RFC 5719 [10]. Every command is defined by means of the ABNF syntax in IETF RFC 2234 [11], and according to the rules in IETF RFC 6733 [15]. + +NOTE: As the commands in the present specification have originally been defined based on the former specification of the Diameter Base Protocol (IETF RFC 3588 [3]), the Vendor-Specific-Application-Id AVP is still assumed as a required AVP (an AVP indicated as {AVP}) in the command code format to avoid backward compatibility issues, even if the use of this AVP has been deprecated in the new specification of the Diameter Base Protocol (IETF RFC 6733 [15]). + +The following Command Codes are defined in this specification: + +**Table 5.6.1: Command-Code values for Ns** + +| Command-Name | Abbreviation | Code | Section | +|------------------------------------------|--------------|---------|---------| +| Network-Status-Request | NSR | 8388724 | 5.6.2 | +| Network-Status-Answer | NSA | 8388724 | 5.6.3 | +| Network-Status-Continuous-Report-Request | NCR | 8388725 | 5.6.4 | +| Network- Status-Continuous-Report-Answer | NCA | 8388725 | 5.6.5 | + +### 5.6.2 Network-Status-Request (NSR) command + +The NSR command, indicated by the Command-Code field set to 8388724 and the 'R' bit set in the Command Flags field, is sent by the SCEF to the RCAF as part of the one time or continuous network status reporting procedure and as part of the cancellation of continuous reporting of network status procedure. + +Message Format: + +``` +
Feature: A short name that can be used to refer to the bit and to the feature, e.g. "EPS".
M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O") in this 3GPP Release.
Description: A clear textual description of the feature. | | | | + +NOTE: This table is a placeholder for when any supported features are added to Nt. There are no supported features in this release. + +## 5.5 Nt specific Experimental-Result-Code AVP values + +### 5.5.1 General + +This subclause defines result code values that shall be supported by Diameter implementations that conform to this specification. + +### 5.5.2 Success + +Result Codes that fall into the Success category are used to inform a peer that a request has been successfully completed. The Result-Code AVP values defined in Diameter base protocol IETF RFC 6733 [15] are applied. + +### 5.5.3 Permanent Failures + +Errors that fall into the Permanent Failures category shall be used to inform the peer that the request has failed, and should not be attempted again. + +The Result-Code AVP values defined in Diameter base protocol IETF RFC 6733 [15] are applied. + +### 5.5.4 Transient Failures + +Errors that fall within the Transient Failures category are used to inform a peer that the request could not be satisfied at the time it was received, but may be able to satisfy the request in the future. + +The Result-Code AVP values defined in Diameter base protocol IETF RFC 6733 [15] are applied. + +## 5.6 Nt messages + +### 5.6.1 Command-Code Values + +This subclause defines the Command-Code values for the Nt application as allocated by IANA from the vendor-specific namespace defined in IETF RFC 5719 [7]. Every command is defined by means of the ABNF syntax in IETF RFC 2234 [8], and according to the rules in IETF RFC 6733 [15]. + +NOTE: As the commands in the present specification have originally been defined based on the former specification of the Diameter Base Protocol (IETF RFC 3588 [3]), the Vendor-Specific-Application-Id AVP is still assumed as a required AVP (an AVP indicated as {AVP}) in the command code format to avoid backward compatibility issues, even if the use of this AVP has been deprecated in the new specification of the Diameter Base Protocol (IETF RFC 6733 [15]). + +The Nt application identifier shall be included in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP contained in the BT-Request/Answer commands. + +The following Command Codes are defined in this specification: + +**Table 5.6.1: Command-Code values for Nt** + +| Command-Name | Abbreviation | Code | Section | +|----------------------------------|--------------|---------|---------| +| Background-Data-Transfer-Request | BTR | 8388723 | 5.6.2 | +| Background-Data-Transfer-Answer | BTA | 8388723 | 5.6.3 | + +### 5.6.2 Background-Data-Transfer-Request (BTR) command + +The BTR command, indicated by the Command-Code field set to 8388723 and the 'R' bit set in the Command Flags field, is sent by the SCEF to the PCRF as part of Negotiation for future background data transfer procedure. + +Message Format: + +``` +
For 3GPP/non-3GPP accesses the MCC and the MNC provided by the serving gateway (SGW, or AGW or TWAG). | | +| 3GPP-User-Location-Info | 3GPP TS 29.061 [18] | Indicates details of where the UE is currently located (e.g. SAI, CGI or eNodeB ID) | | +| DRMP | IETF RFC 7944 [12] | Allows Diameter endpoints to indicate the relative priority of Diameter transactions. | | +| External-Identifier | 3GPP TS 29.336 [17] | External Identifier of the UE | | +| Group-Reporting-Guard-Timer | 3GPP TS 29.336 [17] | It is used by the PCRF to aggregate the reports. | | +| Load | IETF RFC 8583 [14] | The AVP used to convey load information between Diameter nodes. This AVP and all AVPs within this grouped AVP shall have the 'M' bit cleared. | | +| Location-Information-Configuration | 3GPP TS 29.336 [17] | Only MONTE-Location-Type AVP is applicable for the Nta application. | | +| Monitoring-Type | 3GPP TS 29.336 [17] | Only LOCATION_REPORTING (2) is applicable for the Nta application. | | +| MONTE-Location-Type | 3GPP TS 29.336 [17] | Indicates the current location or the last known location. | | +| MSISDN | 3GPP TS 29.329 [16] | MSISDN of the UE | | +| NetLoc-Access-Support | 3GPP TS 29.212 [19] | Indicates the level of support for NetLoc procedures provided by the current access network. | | +| OC-OLR | IETF RFC 7683 [10] | Contains the necessary information to convey an overload report. | | +| OC-Supported-Features | IETF RFC 7683 [10] | Defines the support for the Diameter overload indication conveyance by the sending node. | | +| SCEF-ID | 3GPP TS 29.336 [17] | The diameter identifier provided by the SCEF which has originated the request towards the PCRF. | | +| Supported-Features | 3GPP TS 29.229 [11] | If present, this AVP informs the destination host about the features that the origin host requires to successfully complete this command exchange. | | +| TCP-Source-Port | 3GPP TS 29.212 [19] | TCP source port number | | +| UDP-Source-Port | 3GPP TS 29.212 [19] | UDP source port number | | +| UE-Local-IP-Address | 3GPP TS 29.212 [19] | Contains the UE local IP address. | | +| User-Location-Info-Time | 3GPP TS 29.212 [19] | The time at which the UE was last known to be in the location. | | + +NOTE: AVPs marked with a supported feature are applicable as described in subclause A.6.4.2. + +#### A.6.4.2 Use of the Supported-Features AVP for the Nt application + +When new functionality is introduced for the Nt application, it should be defined as optional. If backwards incompatible changes cannot be avoided, the new functionality shall be introduced as a new feature and support advertised with the Supported-Features AVP. Unless otherwise stated, the use of the Supported-Features AVP for the Nt application shall be compliant to the usage of the Supported-Features AVP on the Cx reference point and consistent with the procedures for the dynamic discovery of supported features as defined in subclause 7.2 of 3GPP TS 29.229 [11]. + +The base functionality for the Nta application is the 3GPP Rel-15 standard and a feature is an extension to that functionality. If the origin host does not support any features beyond the base functionality, the Supported-Features AVP may be absent from the Nta commands. + +As defined in subclause 7.1.1 of 3GPP TS 29.229 [11], when extending the application by adding new AVPs for a feature, the new AVPs shall have the M bit cleared and the AVP shall not be defined mandatory in the command ABNF. + +As defined in 3GPP TS 29.229 [11], the Supported-Features AVP is of type grouped and contains the Vendor-Id, Feature-List-ID and Feature-List AVPs. On the all reference points as specified in this specification, the Supported-Features AVP is used to identify features that have been defined by 3GPP and hence, for features defined in this document, the Vendor-Id AVP shall contain the vendor ID of 3GPP (10415). If there are multiple feature lists defined for the reference point, the Feature-List-ID AVP shall differentiate those lists from one another. + +The Supported-Features AVP shall be included in every ECR and ECA commands if supported by the SCEF and PCRF respectively. + +The table A.6.4.2-1 defines the features applicable to the Nta application for the feature list with a Feature-List-ID of 1. + +**Table A.6.4.2-1: Features of Feature-List-ID 1 used in Nta** + +| Feature bit | Feature | M/O | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----|-------------| +| Feature bit: The order number of the bit within the Feature-List AVP where the least significant bit is assigned number "0".
Feature: A short name that can be used to refer to the bit and to the feature, e.g. "EPS".
M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O") in this 3GPP Release.
Description: A clear textual description of the feature. | | | | + +NOTE: This table is a placeholder for when any supported features are added to Nta. There are no supported features in this release. + +### A.6.5 Nta specific Experimental-Result-Code AVP values + +Subclause 5.5 is applicable for Nta specific Experimental-Result-Code AVP values. + +### A.6.6 Nta messages + +#### A.6.6.1 Command-Code Values + +This subclause defines the Command-Code values for the Nta application as allocated by IANA from the vendor-specific namespace defined in IETF RFC 5719 [7]. Every command is defined by means of the ABNF syntax in IETF RFC 2234 [8], and according to the rules in IETF RFC 6733 [15]. + +The Vendor-Specific-Application-Id AVP shall not be included in any command sent by Diameter nodes supporting applications defined in this specification. If the Vendor-Specific-Application-Id AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node. + +NOTE: The Vendor-Specific-Application-Id is included as an optional AVP in all Command Code Format specifications defined in this specification in order to overcome potential interoperability issues with intermediate Diameter agents non-compliant with the IETF RFC 6733 [15]. + +The following Command Codes are defined in this specification: + +**Table A.6.6-1: Command-Code values for Nta** + +| Command-Name | Abbreviation | Code | Section | +|-----------------------------|---------------------|-------------|----------------| +| Event-Configuration-Request | ECR | 8388735 | A.6.6.2 | +| Event-Configuration-Answer | ECA | 8388735 | A.6.6.3 | +| Event-Reporting-Request | ERR | 8388736 | A.6.6.4 | +| Event-Reporting-Answer | ERA | 8388736 | A.6.6.5 | + +#### A.6.6.2 Event-Configuration-Request (ECR) command + +The ECR command, indicated by the Command-Code field set to 8388735 and the 'R' bit set in the Command Flags field, is sent by the SCEF to the PCRF as part of event monitoring configuration procedure. + +Message Format: + +``` +
a) next header
b) fragment Offset
c) More fragment bit
d) Identification | Copied from IPv4 Protocol field.
Copied from the IPv4 Fragment offset field.
Copied from the value of the more fragment bit in the IPv4 flags field.
The value of this field should be mapped from the triple of the source address, destination address and IPv4 identification field of the incoming packet/fragments to a unique value for the source and destination address of the outgoing IPv6 packet/fragments. | + +#### 9.2.2.2 Abnormal cases + +If IPv4 options are present in the IPv4 packet, they should be ignored i.e., there is no attempt to translate them. However, if an unexpired source route option is present then the packet shall instead be discarded, and an ICMPv4 "destination unreachable/source route failed" Type 3/Code 5 error message shall be returned to the sender as defined in IETF RFC 792 [18]. + +When a translator receives the first fragment of a fragmented UDP IPv4 packet and the checksum field is zero the translator should drop the packet and generate a system management event specifying at least the IP addresses and port numbers in the packet. When the translator receives fragments other than the first it should silently drop the packet since there is no port information to log. + +When a translator receives an unfragmented UDP IPv4 packet and the checksum field is zero the translator shall compute the missing UDP checksum as part of translating the packet. Also, the translator should maintain a counter of how many UDP checksums are generated in this manner. + +#### 9.2.2.3 IPv6 to IPv4 + +When the TrGW receives an IPv6 message the following codings shall be set in the IPv4 headers of the message sent to the IPv4 network. + +- If there is no IPv6 fragment header, the IPv4 header fields shall be set as described in Table 3; +- if there is an IPv6 fragment header, the IPv4 header fields shall be set as described in Table 4. + +**Table 3: Derivation of IPv4 Header from IPv6 Header (no fragmentation)** + +| IPv4 field | Value | +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Version | 4 | +| Internet header length | 5 (No IPv4 options) | +| Type of Service | The default behaviour is that the value of the IPv4 field Type of service field is the value of the IPv6 Traffic class field (all 8 bits are copied). An implementation of a TrGW should also provide the ability to ignore the value of the IPv6 Traffic Class and always set the IPv4 Type of Service field to zero. | +| Total length | The IPv4 Total Length field value is the IPv6 Payload length value plus the size of the IPv4 headers. | +| Identification | All bits are set to zero. | +| Flags | The more fragment flag is set to zero. The Don't fragment flag is set to one. | +| Fragment offset | Set to zero. | +| Time to live (TTL) | The value of the field shall be set to the received IPv6 Hop Limit field value minus 1. | +| Protocol | The IPv4 field Protocol shall be set to the value of IPv6 field The next header value. | +| Header checksum | Computed once the IPv4 header has been created. | +| Source Address | Shall be handled as the addresses of the payload message as described in subclause 9.2.1. | +| Destination Address | Shall be handled as the addresses of the payload message as described in subclause 9.2.1. | + +**Table 4: Derivation of IPv4 Header from IPv6 Header (fragmentation)** + +| IPv4 field | Value | +|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Version | 4 | +| Internet header length | 5 (No IPv4 options) | +| Type of Service and Precedence: | The default behaviour is that the value of the IPv4 field Type of service field is the value of the IPv6 Traffic class field (all 8 bits are copied). An implementation of a TrGW should also provide the ability to ignore the value of the IPv6 Traffic Class and always set the IPv4 Type of Service field to zero. | +| Total length | The IPv4 Total Length field value is the IPv6 Payload length value plus the size of the IPv4 headers minus 8 for the Fragment header. | +| Identification | The value of this field should be mapped from the triple of the source address, destination address and IPv6 fragmentation header field "identification" of the incoming packet/fragments to a unique value for the source and destination address of the outgoing IPv4 packet/fragments. | +| Flags | The IPv4 More Fragments flag is copied from the IPv6 M flag in the IPv6 Fragment header the IPv4. The Don't Fragments flag is set to zero allowing this packet to be fragmented by IPv4 routers. | +| Time to live (TTL) | The value of the field shall be set to the received IPv6 Hop Limit field value minus 1. | +| Protocol | The IPv4 field Protocol shall be set to the value of IPv6 field The next header value. | +| Header checksum | Computed once the IPv4 header has been created. | +| Source Address | Shall be handled as the addresses of the payload message as described in subclause 9.2.1. | +| Destination Address | Shall be handled as the addresses of the payload message as described in subclause 9.2.1. | + +#### 9.2.2.4 Abnormal cases + +If any of an IPv6 hop-by-hop options header, destination options header, or routing header with the Segments Left field equal to zero are present in the IPv6 packet, they are ignored i.e., there is no attempt to translate them. However, the Total Length field and the Protocol field shall be adjusted to "skip" these extension headers. + +If a routing header with a non-zero Segments Left field is present then the packet shall be translated, and an ICMPv6 "parameter problem/ erroneous header field encountered" Type 4/Code 0 error message as defined in IETF RFC 2463 [19], with the Pointer field indicating the first byte of the Segments Left field should be returned to the sender. + +### 9.2.3 Fragmentation + +If the DF flag is not set and the IPv4 packet will result in an IPv6 packet larger than 1280 bytes the TrGW shall prior to transferring it in the IPv6 network: + +- Add the fragment header to the message; and + +- fragment the IPv4 packets so that their length, excluding the IPv4 header, is at most 1232 bytes (1280 minus 40 for the IPv6 header and 8 for the Fragment header). + +### 9.2.4 Abnormal cases + +As a part of decrementing the Time To Live /Hop Limit value and the TrGW discovers that the zero value is reached the TrGW shall send an ICMPv4/ICMPv6 message with the error "time to live exceeded in transit" type 11 code 0 as defined in IETF RFC 792 [18] and "hop limit exceeded in transit" type 3 code 0 as defined in IETF RFC 2463 [19]. + +# 10 IBCF – TrGW Interactions + +## 10.1 Overview + +### 10.1.1 General + +The present specification describes Ix signalling procedures and their interaction with SIP signalling in the control plane, and with user plane procedures. Each scenario or "use case" is described in a separate subclause within subclause 10.2. 3GPP TS 29.238 [25] maps these signalling procedures to H.248 messages and defines the required H.248 profile (which provides details of used packages and parameters). + +### 10.1.2 Network model + +Figure 10.1.2.1 shows the network model. The broken line represents the call control signalling. The dotted line represents the user plane. The IBCF uses one context with two terminations in the TrGW. + + + +The diagram illustrates the network model. At the top, a box labeled 'IBCF' has two internal connection points. A horizontal green dashed line (representing call control signalling) passes through the IBCF. Below the IBCF, a solid blue vertical line connects it to a second box labeled 'TrGW'. The TrGW box contains two internal connection points labeled 'T1' and 'T2', with a switch-like symbol between them. A horizontal red dotted line (representing the user plane) passes through the TrGW, connecting to T1 and T2. + +Figure 10.1.2.1: Network model diagram showing IBCF and TrGW components and their connections. + +Figure 10.1.2.1: Network model + +### 10.1.3 Example Call Flow + +#### 10.1.3.1 Basic Procedures + +##### 10.1.3.1.1 Call Establishment + +Figure 10.1.3.1.1.1 depicts the signalling flow for a call setup either from or toward an external network. + + + +``` + +sequenceDiagram + participant IBCF + participant TrGW + Note right of IBCF: 1. SDP offer (IP2o, P2o) + IBCF->>IBCF: 2. Use case X detected that needs TrGW functionality + IBCF->>TrGW: 3. H.248 ADD req (C= ?, T= ?, LAddr=?, LPort=?) + Note right of TrGW: 4. Create outgoing termination T1 + TrGW->>IBCF: 5. H.248 ADD resp. (C=C1, T=T1, LAddr=IP1o, LPort=P1o) + Note right of IBCF: 6. Modify SDP offer + IBCF->>Network: 7. SDP offer (IP1o, P1o) + Network-->>IBCF: 8. SDP answer (IP1a, P1a) + IBCF->>TrGW: 9. H.248 MOD req (C= C1, T= T1, RAddr=IP1a, RPort=P1a) + Note right of TrGW: 10. Configure Outgoing Termination T1 + TrGW->>IBCF: 11. H.248 MOD Resp (C= C1, T= T1) + IBCF->>TrGW: 12. H.248 ADD req (C= C1, T= ?, LAddr=?, LPort=?, RAddr=IP2o, RPort=P2o) + Note right of TrGW: 13. Create incoming Termination T2 + TrGW->>IBCF: 14. H.248 ADD Resp (C= C1, T= T2, LAddr=IP2a, LPort=P2a, RAddr=IP1a, RPort=P1a) + Note right of IBCF: 15. Modify SDP answer + IBCF->>Network: 16. SDP answer(IP2a, P2a) + +``` + +Reserve TrGW Connection Point (, Change Through-Connection) + +Configure TrGW Connection Point (, Change Through-Connection) + +Reserve And Configure TrGW Connection Point (, Change Through-Connection) + +Sequence diagram showing the interaction between TrGW and IBCF for TrGW functionality detection and resource reservation. The diagram includes 16 steps: 1. IBCF receives SDP offer; 2. Use case X detected; 3. IBCF sends H.248 ADD req to TrGW; 4. TrGW creates outgoing termination T1; 5. TrGW sends H.248 ADD resp; 6. IBCF modifies SDP offer; 7. IBCF sends SDP offer to network; 8. IBCF receives SDP answer; 9. IBCF sends H.248 MOD req to TrGW; 10. TrGW configures outgoing termination T1; 11. TrGW sends H.248 MOD Resp; 12. IBCF sends H.248 ADD req for incoming termination; 13. TrGW creates incoming termination T2; 14. TrGW sends H.248 ADD Resp; 15. IBCF modifies SDP answer; 16. IBCF sends SDP answer to network. Brackets on the right indicate phases for 'Reserve TrGW Connection Point', 'Configure TrGW Connection Point', and 'Reserve And Configure TrGW Connection Point'. + +1. The IBCF receives an SDP offer in SIP signalling. +2. The IBCF detects that one of the CS-TrGW functions is required, e.g. NAPT/NAT. +3. The IBCF sends a H.248 ADD command to create the outgoing termination and to request resources to execute TrGW function. +4. The TrGW creates the outgoing termination. +5. The TrGW replies to IBCF with a H.248 Add reply command and provides the local address and port of the outgoing termination. +6. The IBCF replaces the IP address inside the SDP using the information coming from TrGW. +7. SDP offer is sent to the network at the outgoing side. +8. SDP answer is received by IBCF. + +9. The IBCF sends a H.248 MOD command to configure the outgoing termination with address and port information received in the SDP answer. + 10. The TrGW configures the outgoing termination. + 11. The TrGW replies to IBCF with a H.248 MOD reply command. + 12. The IBCF sends a H.248 ADD command to create the incoming termination and to request resources to execute TrGW function. + 13. The TrGW creates the incoming termination. + 14. The TrGW replies to the IBCF with a H.248 Add reply command and provides the local address and port of the incoming termination. +- NOTE 1: Steps 12 to 14 may also be executed after step 2. +15. The IBCF replaces the IP address inside the SDP using the information coming from TrGW. + 16. SDP answer is sent to the network at the incoming side. + +###### **Figure 10.1.3.1.1.1: IBCF and TrGW interaction at Call establishment.** + +When creating the termination towards the IMS network or towards external networks, the IBCF may also indicate that the IP Interface Type is "MboIP". + +NOTE : Other values may be indicated by a CS-IBCF, as detailed in 3GPP TS 29.235 [29]. + +The IP Interface Type allows the TrGW to collect statistics per interface type associated with the RTP bearer termination. The provision of these statistics is outside of the scope of this specification. + +##### 10.1.3.1.2 Call Release + +Figure 10.1.3.1.2.1 depicts the signalling flow for a call release. + + + +``` + +sequenceDiagram + participant IBCF + participant TrGW + Note right of IBCF: 1. Event causing release + IBCF->>TrGW: 2. H.248 SUB req (C=C1, T=T1) + Note left of TrGW: 3. Destroy outgoing termination T1 + TrGW-->>IBCF: 4. H.248 SUB resp. (C=C1, T=T1) + IBCF->>TrGW: 5. H.248 SUB req (C=C1, T=T2) + Note left of TrGW: 6. Destroy incoming termination T2 + TrGW-->>IBCF: 7. H.248 SUB resp. (C=C1, T=T2) + +``` + +Sequence diagram showing the interaction between TrGW and IBCF for call release. The process starts with an event causing release at the IBCF. The IBCF sends an H.248 SUB request (C=C1, T=T1) to the TrGW. The TrGW destroys the outgoing termination T1 and responds with an H.248 SUB response (C=C1, T=T1). Next, the IBCF sends an H.248 SUB request (C=C1, T=T2) to the TrGW. The TrGW destroys the incoming termination T2 and responds with an H.248 SUB response (C=C1, T=T2). Brackets on the right indicate that steps 2-4 are 'Release TrGW Termination' and steps 5-7 are 'Release TrGW Termination'. + +1. The IBCF identifies that the call is to be release. Typically this will be by the receipt of a SIP BYE request. +2. The IBCF sends a H.248 SUB command to release the outgoing termination. +3. The TrGW destroys the outgoing termination. +4. The TrGW replies to IBCF with a H.248 SUB reply command. +5. The IBCF sends a H.248 SUB command to release the incoming termination. +6. The TrGW destroys the incoming termination. +7. The TrGW replies to IBCF with a H.248 SUB reply command. + +NOTE 1: Steps 5 to 7 may also be executed before steps 2 to 4 or in parallel with steps 2 to 4. + +NOTE 2: Rather than releasing the two terminations separately, the IBCF may request the TrGW to release both terminations in a single request. + +**Figure 10.1.3.1.2.1: IBCF and TrGW interaction at Call release** + +## 10.2 Main Functions supported at the Ix Interface + +## 10.2.0 Introduction + +The following functions shall be supported by the TrGW: + +- Gate Management including: + - Opening/closing of gates; + - Remote source address filtering; and + - Remote source port filtering; + +- QoS packet marking (differentiated services); +- NAPT and IP Version Interworking; +- Bandwidth policing; +- Hanging termination detection; +- IP Realm Indication; +- Media Control; and +- Through-Connection. + +Additionally, the following functions may be supported by the TrGW: + +- Resource allocation per flow; +- Media Inactivity Detection; +- IP Realm Availability; +- Optimal Media Routeing; +- Explicit Congestion Notification support; +- Emergency Call; +- IMS end-to-end media plane security; +- Access Transfer procedures with media anchored in ATGW; +- Multimedia Priority Service; +- RTP Header extension to signal Coordination of Video Orientation; + - Generic image attribute; +- Interactive Connectivity Establishment; +- Video Region of Interest (ROI) ; +- RTP-level pause and resume functionality ; and +- "RTCP Codec Control Commands and Indications" + +### 10.2.1 NAPT and IP version interworking + +NAPT and IP version interworking is documented in clause 9. + +The IP Address and port conversion is configured by the standard Ix interactions at call setup depicted in figure 10.1.3.1.1.1. + +IP address and port conversion is mandatory every time a TrGW is inserted into the path for any reason to guarantee that all IP packets are routed through this entity. + +### 10.2.2 Gate Management + +The procedures in subclause A.7.1.2.2.3 of 3GPP TS 29.235 [29] are applicable. + +### 10.2.3 RTCP Handling + +The procedures in subclause A.7.1.2.2.7 of 3GPP TS 29.235 [29] are applicable. + +### 10.2.4 IP Realm Indication + +Whenever requesting a new IP media-path (i.e. creation of IP bearer terminations), the TrGW may indicate the correspondent IP realm/domain to the TrGW. The TrGW shall assign the IP termination in the IP realm indicated. The same IP realm shall be applied to all media streams associated with the termination. The IP realm identifier shall not be changed after the initial assignment. + +A default IP realm may be configured such that if the TrGW has not received the IP realm identifier and the TrGW supports multiple IP realms then the default IP realm shall be used. + +### 10.2.5 Media Control + +#### 10.2.5.1 General + +The transcoding functionality, where the TrGW processes and possibly converts application / media data (like e.g. RTP payload) is optional for the TrGW and IBCF to support. + +The IBCF shall determine the TrGW transcoding capability through provisioning and MGW selection, outside the scope of this specification. + +IBCF procedures to offer transcoding in SIP/SDP signalling are described in 3GPP TS 23.228 [8] and in 3GPP TS 24.229 [1]. The IBCF shall only apply those transcoding procedures if an attached TrGW supports transcoding. For media with "RTP/SAVP" (see IETF RFC 3711 [34]) or "RTP/SAVPF" (see IETF RFC 5124 [35]) as transport protocol, the IBCF shall not offer or apply transcoding. + +If the IBCF and available TrGW support transcoding, the IBCF may add codecs to a SDP offer within a SIP request. + +If the IBCF and available TrGW do not support transcoding, or if the IBCF chooses not to offer transcoding, the IBCF shall pass SDP offers without adding codecs to the SDP offer and the IBCF shall pass SDP answers without modification to the contained codecs. + +If the IBCF does not offer or apply transcoding procedures (as described above) but inserts the TrGW for any other reason, the IBCF shall either not signal media related information to the TrGW, or it shall signal the same media related information for all interconnected terminations (i.e. identical media configurations for the two connected H.248 stream endpoints). + +If the IBCF does not offer or apply transcoding but signals media attributes to a TrGW that does not support transcoding without having seized the peer termination (see figure 10.2.5.3, Step 3) the TrGW shall accept this request even though it cannot reserve any transcoding resources related to this media. When the peer termination is seized and configured it shall be configured with the same media related sub-fields in the media descriptor as for the first termination. If the selected codec is not the same as the codec configured at the first termination then this termination shall be modified before the peer termination is seized. + +NOTE 1: The signalling of such codec related information by an IBCF to a TrGW not supporting transcoding is an implementation decision. + +NOTE 2: A TrGW not supporting transcoding can use such codec related information to learn that RTCP ports need to be reserved, and to derive information about packet size and frequency useful for internal resource reservation. + +If the IBCF and available TrGW support transcoding and the IBCF includes in a SDP offer additional codecs, the following procedures apply: + +- The IBCF may seize a termination towards the terminating user, using the "Reserve TrGW Connection Point" procedure before sending an SDP offer with added codecs to the terminating user. The IBCF may signal media related information to the TrGW or omit media when adding the IP termination at this stage. + +NOTE 3: The signalling of media related information to a MGW requires that it reserve the indicated resources before returning a positive response to the H.248 command, by omitting media related information the TrGW does not need to reserve any associated resources at this stage. + +- When the IBCF receives the SDP answer from the terminating user, the IBCF shall check if any of the codecs offered by the originating side are contained in the answer. + +- If only the codecs inserted by the IBCF are contained in the answer, the IBCF shall configure the TrGW to transcode. If it previously performed a "Reserve TrGW Connection Point" procedure it shall configure the TrGW using the "Configure TrGW Connection Point" procedure towards the termination on the terminating user side by supplying the media returned in the answer from the terminating user, otherwise it shall perform a "Reserve and Configure TrGW Connection Point" procedure. Within those procedures, the IBCF shall supply the media returned in the answer from the terminating user. If the IBCF seized the termination only at this point in time, it shall send the IP address and port information received from the TrGW in the acknowledgment to the "Reserve and Configure TrGW Connection Point" procedure towards the terminating user in a new SDP offer. The IBCF shall perform the "Reserve and Configure TrGW Connection Point" procedure towards the termination on the originating user side, supplying the preferred media offered by the originating side. +- If the returned SDP contains media offered by the originating user no transcoding at the TrGW is required. If the IBCF previously performed the "Reserve TrGW Connection Point" procedure the IBCF shall configure the TrGW accordingly by either either supplying the same media related information for all interconnected terminations or by omitting the media related information. + +Some basic use cases are depicted in figures 10.2.5.1, 10.2.5.2, and 10.2.5.3. + + + +``` + +sequenceDiagram + participant IBCF + participant TrGW + + Note right of IBCF: 1. SDP offer (IP2o, P2o, codec1, codec2) + Note right of IBCF: 2. IBCF supports transcoding and supports additional codecs, the IBCF inserts additional codecs in the SDP offer + IBCF->>TrGW: 3. H.248 ADD req (C= ?, T= ?, LAddr=?, LPort=?, Local Resources="-" or codec1 or codec 2 or codec3) + Note right of TrGW: Reserve TrGW Connection Point + TrGW->>TrGW: 4. Create outgoing termination T1 + TrGW->>IBCF: 5. H.248 ADD resp. (C=C1, T=T1, LAddr=IP1o, LPort=P1o) + Note right of IBCF: 6. Modify SDP offer + IBCF->>TrGW: SDP offer (IP1o, P1o, codec 1, codec2, codec3) + TrGW->>IBCF: 8. SDP answer (IP1a, P1a, codec 1) + Note right of IBCF: Configure TrGW Connection Point + IBCF->>TrGW: 9. H.248 MOD req (C= C1, T= T1, RAddr=IP1a, RPort=P1a, Local Resources="-" or codec1, Remote Resources="-" or codec1) + TrGW->>TrGW: 10. Configure Outgoing Termination T1 + TrGW->>IBCF: 11. H.248 MOD Resp (C= C1, T= T1) + Note right of IBCF: Reserve And Configure TrGW Connection Point + IBCF->>TrGW: 12. H.248 ADD req (C= C1, T= ?, LAddr=?, LPort=?, RAddr=IP2o, RPort=P2o, Local Resources="-" or codec1, Remote Resources="-" or codec1) + TrGW->>TrGW: 13. Create incoming Termination T2 + TrGW->>IBCF: 14. H.248 ADD Resp (C= C1, T= T2, LAddr=IP2a, LPort=P2a, RAddr=IP2o, RPort=P2o) + Note right of IBCF: 15. Modify SDP answer + IBCF->>TrGW: 16. SDP answer(IP2a, P2a, codec 1) + +``` + +Sequence diagram showing the interaction between TrGW and IBCF for media resource reservation and configuration. + +1. The IBCF receives an SDP offer in SIP signalling. +2. The IBCF adds additional codecs to the subsequent SDP offer, giving priority to those offered by the preceding node/network. +3. In this example the IBCF seizes a TrGW prior to sending the new SDP offer; as this scenario is preparing for a possible transcoding in the TrGW then a TrGW supporting media shall be seized. The IBCF sends a H.248 ADD request command to create the outgoing termination and to request IP resources to execute TrGW function. As no media transcoding is yet known to be needed this may be indicated by omitting media related sub-fields in the media descriptor (i.e. signalling "-"). Alternatively the preferred codec (e.g. codec 1) may be signalled in order to reserve this resource in the event that transcoding was required. +4. The TrGW creates the outgoing termination. + +5. The TrGW replies to IBCF with a H.248 ADD reply command and provides the local address and port of the outgoing termination. +6. The IBCF replaces the IP address inside the SDP offer using the information coming from TrGW +7. The IBCF forwards the new SDP offer to the succeeding node. +8. The SDP answer is received by IBCF. In this example the codec1 received in the original SDP offer in step1 has been selected by the succeeding network/terminating UE and the IBCF determines that transcoding is not required. +9. The IBCF sends a H.248 MOD request command to configure the outgoing termination with address and port information received in the SDP answer. As no media transcoding is needed this may be indicated by omitting media related sub-fields in the media descriptor (i.e. signalling "-"). Alternatively the selected codec (codec 1) may be signalled. +10. The TrGW configures the outgoing termination. +11. The TrGW replies to IBCF with a H.248 MOD reply command. +12. The IBCF sends a H.248 ADD request command to create the incoming termination to configure this termination with remote address and port information and to request resources to execute TrGW function. As no media transcoding is needed this may be indicated by omitting media related sub-fields in the media descriptor (i.e. signalling "-"). Alternatively the selected codec received in step 8 (Codec 1) may be signalled. +13. The TrGW creates the incoming termination. +14. The TrGW replies to the IBCF with a H.248 ADD reply command and provides the local address and port of the incoming termination. +15. The IBCF replaces the IP address inside the SDP using the information coming from TrGW. +16. The SDP answer is sent to the network at the incoming side. + +**Figure 10.2.5.1: IBCF and TrGW interaction when the IBCF offers additional codecs but no transcoding is required, and the TrGW is seized in advance.** + + + +``` + +sequenceDiagram + participant External + participant IBCF + participant TrGW + + External-->>IBCF: 1. SDP offer (IP2o, P2o, codec1, codec2) + Note over IBCF: 2. IBCF supports transcoding +and supports additional +codecs + Note right of IBCF: Reserve TrGW Connection Point + IBCF->>TrGW: 3. H.248 ADD req +(C= ?, T= ?, LAddr=?, LPort=?, +Local Resources="-" or codec1 or codec 2 or codec 3) + Note left of TrGW: 4. Create outgoing termination T1 + TrGW-->>IBCF: 5. H.248 ADD resp. +(C=C1, T=T1, +LAddr=IP1o, LPort=P1o) + Note over IBCF: 6. Modify SDP offer + IBCF->>External: 7. SDP offer (IP1o, P1o, codec 1, codec 2, codec 3) + External-->>IBCF: 8. SDP answer (IP1a, P1a, codec 3) + Note right of IBCF: Configure TrGW Connection Point + IBCF->>TrGW: 9. H.248 MOD req +(C= C1, T= T1, +RAddr=IP1a, RPort=P1a, +Local Resources= codec3 +Remote Resources= codec3) + Note left of TrGW: 10. Configure Outgoing Termination T1 + TrGW-->>IBCF: 11. H.248 MOD Resp +(C= C1, T= T1) + Note right of IBCF: Reserve And Configure TrGW Connection Point + IBCF->>TrGW: 12. H.248 ADD req +(C= C1, T= ?, LAddr=?, LPort=?, +RAddr=IP2o, RPort=P2o, +Local Resources=codec1 or codec2, +Remote Resources=codec1 or codec2) + Note left of TrGW: 13. Create incoming Termination T2 + TrGW-->>IBCF: 14. H.248 ADD Resp +(C= C1, T= T2, +LAddr=IP2a, LPort=P2a, +RAddr=IP2o, RPort=P2o) + Note over IBCF: 15. Modify SDP answer + IBCF->>External: 16. SDP answer(Ip2a, P2a, +codec1 or codec2) + +``` + +Sequence diagram showing the interaction between TrGW and IBCF for media resource reservation and configuration. The diagram consists of 16 steps. 1. IBCF receives an SDP offer from an external source. 2. IBCF adds supported codecs to the offer. 3. IBCF sends an H.248 ADD request to TrGW to reserve resources and create an outgoing termination T1. 4. TrGW creates the outgoing termination. 5. TrGW sends an H.248 ADD response. 6. IBCF modifies the SDP offer. 7. IBCF sends the modified SDP offer to the external source. 8. External source sends an SDP answer. 9. IBCF sends an H.248 MOD request to TrGW to configure the outgoing termination. 10. TrGW configures the outgoing termination. 11. TrGW sends an H.248 MOD response. 12. IBCF sends an H.248 ADD request to TrGW to reserve and configure an incoming termination T2. 13. TrGW creates the incoming termination. 14. TrGW sends an H.248 ADD response. 15. IBCF modifies the SDP answer. 16. IBCF sends the final SDP answer to the external source. Brackets on the right indicate phases: 'Reserve TrGW Connection Point' (steps 3-5), 'Configure TrGW Connection Point' (steps 9-11), and 'Reserve And Configure TrGW Connection Point' (steps 12-14). + +1. The IBCF receives an SDP offer in SIP signalling. +2. The IBCF adds additional codecs to the subsequent SDP offer, giving priority to those offered by the preceding node/network. +3. In this example the IBCF seizes a TrGW prior to sending the new SDP offer; as this scenario is preparing for a possible transcoding in the TrGW then a TrGW supporting media shall be seized. The IBCF sends a H.248 ADD request command to create the outgoing termination and to request IP resources to execute TrGW function. As no media transcoding is yet known to be needed this may be indicated by omitting media related sub-fields in the media descriptor (i.e. signalling "-"). Alternatively the preferred codec (e.g. Codec 1) may be signalled in order to reserve this resource in the event that transcoding was required. +4. The TrGW creates the outgoing termination. + +5. The TrGW replies to IBCF with a H.248 ADD reply command and provides the local address and port of the outgoing termination. +6. The IBCF replaces the IP address inside the SDP offer using the information coming from TrGW. +7. The IBCF forwards the new SDP offer to the succeeding node. +8. The SDP answer is received by IBCF. In this example the codec 3 added by the IBCF to the SDP offer has been selected. Transcoding is therefore required. +9. The IBCF sends a H.248 MOD request command to configure the outgoing termination with address and port information received in the SDP answer and the selected media attributes (codec 3). +10. The TrGW configures the outgoing termination. +11. The TrGW replies to IBCF with a H.248 MOD reply command. +12. The IBCF sends a H.248 ADD request command to create the incoming termination to configure this termination with remote address and port information and to request resources to execute TrGW function. As media transcoding is required it indicates this explicitly with a codec selected by the IBCF for the incoming termination from the offered codec(s) received in step1. +13. The TrGW creates the incoming termination. +14. The TrGW replies to the IBCF with a H.248 ADD reply command and provides the local address and port of the incoming termination. +15. The IBCF replaces the IP address inside the SDP using the information coming from TrGW and replaces the codec with the codec it selected for the incoming termination. +16. The SDP answer is sent to the network at the incoming side. + +**Figure 10.2.5.2: IBCF and TrGW interaction when IBCF offers additional codecs and transcoding is required, and the TrGW is seized in advance.** + + + +``` + +sequenceDiagram + participant TrGW + participant IBCF + Note right of IBCF: 1. SDP offer (IP2o, P2o, codec1, codec2) + Note right of IBCF: 2. Use case X detected that needs TrGW functionality + IBCF->>TrGW: 3. H.248 ADD req (C= ?, T= ?, LAddr=?, LPort=?, Local Resources="-" or codec1 or codec2) + Note left of TrGW: 4. Create outgoing termination T1 + TrGW->>IBCF: 5. H.248 ADD resp. (C=C1, T=T1, LAddr=IP1o, LPort=P1o) + Note right of IBCF: 6. Modify SDP offer + IBCF-->>External: 7. SDP offer (IP1o, P1o, codec1, codec2) + External-->>IBCF: 8. SDP answer (IP1a, P1a, codec1) + IBCF->>TrGW: 9. H.248 MOD req (C= C1, T= T1, RAddr=IP1a, RPort=P1a, Local Resources="-" or codec1, Remote Resources="-" or codec1) + Note left of TrGW: 10. Configure Outgoing Termination T1 + TrGW->>IBCF: 11. H.248 MOD Resp (C= C1, T= T1) + IBCF->>TrGW: 12. H.248 ADD req (C= C1, T= ?, LAddr=?, LPort=?, RAddr=IP2o, RPort=P2o, Local Resources="-" or codec1, Remote Resources="-" or codec1) + Note left of TrGW: 13. Create incoming Termination T2 + TrGW->>IBCF: 14. H.248 ADD Resp (C= C1, T= T2, LAddr=IP2a, LPort=P2a, RAddr=IP2o, RPort=P2o) + Note right of IBCF: 15. Modify SDP answer + IBCF-->>External: 16. SDP answer (IP2a, P2a, codec 1) + +``` + +Reserve +TrGW +Connection +Point + +Configure +TrGW +Connection +Point + +Reserve +And +Configure +TrGW +Connection +Point + +Sequence diagram showing the interaction between TrGW and IBCF for resource reservation and configuration. The diagram consists of 16 steps. 1. IBCF receives an SDP offer. 2. IBCF detects a use case needing TrGW. 3. IBCF sends an H.248 ADD req to TrGW. 4. TrGW creates an outgoing termination T1. 5. TrGW sends an H.248 ADD resp. 6. IBCF modifies the SDP offer. 7. IBCF sends the SDP offer to the caller. 8. IBCF receives the SDP answer. 9. IBCF sends an H.248 MOD req to TrGW. 10. TrGW configures the outgoing termination T1. 11. TrGW sends an H.248 MOD Resp. 12. IBCF sends an H.248 ADD req to TrGW. 13. TrGW creates an incoming termination T2. 14. TrGW sends an H.248 ADD Resp. 15. IBCF modifies the SDP answer. 16. IBCF sends the SDP answer to the caller. Brackets on the right indicate phases: 'Reserve TrGW Connection Point' (steps 3-5), 'Configure TrGW Connection Point' (steps 9-11), and 'Reserve And Configure TrGW Connection Point' (steps 12-14). + +1. The IBCF receives an SDP offer in SIP signalling. +2. The IBCF requires a TrGW for another use case but does not offer transcoding. +3. The IBCF sends a H.248 ADD request command to create the outgoing termination and to request IP resources to execute TrGW function. As no media transcoding is required this may be indicated by signalling "-". Alternatively any codec (e.g. codec 1) can be signalled. If the IBCF selects a TrGW that does not support transcoding, the IBCF may signal media related sub-fields in the media descriptor to the TrGW if the TrGW supports media encoding. The TrGW shall accept the ADD request even though it cannot reserve any transcoding resources for the indicated media. +4. The TrGW creates the outgoing termination. + +5. The TrGW replies to IBCF with a H.248 ADD reply command and provides the local address and port of the outgoing termination. +6. The IBCF replaces the IP address inside the SDP using the information coming from TrGW. +7. The IBCF forwards the new offer to the succeeding node. +8. The SDP answer is received by IBCF. In this example the codec 1 received in the original SDP offer in step 1 has been selected. +9. The IBCF sends a H.248 MOD request command to configure the outgoing termination with address and port information. As no media transcoding is needed this may be indicated by signalling "-" .Alternatively the selected codec (codec 1) can be signalled. +10. The TrGW configures the outgoing termination. +11. The TrGW replies to IBCF with a H.248 MOD reply command. +12. The IBCF sends a H.248 ADD command to create the incoming termination to configure this termination with remote address and port information and to request resources to execute TrGW function. As no media transcoding is needed this may be indicated by signalling "-" .Alternatively media related sub-fields in the media descriptor for the codec indicated to the incoming termination may be signalled (e.g. the selected codec received in step 8 (codec 1)). +13. The TrGW creates the incoming termination. +14. The TrGW replies to the IBCF with a H.248 ADD reply command and provides the local address and port of the incoming termination. +15. The IBCF replaces the IP address inside the SDP answer using the information coming from TrGW. +16. The SDP answer is sent to the network at the incoming side. + +**Figure 10.2.5.3: IBCF and TrGW interaction when IBCF does not offer transcoding** + +#### 10.2.5.2 Handling of common codec parameters + +The requirements as described in subclause 5.13.2 of 3GPP TS 23.334 [43] for the IMS-ALG and the IMS-AGW, apply to the IBCF and the TrGW. + +#### 10.2.5.3 EVS speech codec parameters handling + +The Enhanced Voice Services (EVS) speech codec is defined in 3GPP TS 26.441 [52]. Its RTP payload type is defined in 3GPP TS 26.445 [53], and procedures for its usage as IMS Multimedia Telephony speech codec are defined in 3GPP TS 26.114 [36]. + +The IBCF and the TrGW may support transcoding to and from the EVS speech codec. If they do so, the requirements as described in subclause 5.13.3 of 3GPP TS 23.334 [43] for the IMS-ALG and the IMS-AGW, apply to the IBCF and the TrGW. + +#### 10.2.5.4 Rate adaptation for media endpoints + +If the IBCF and the TrGW support rate adaptation for media endpoints using the enhanced bandwidth negotiation mechanism defined in 3GPP TS 26.114 [36] the requirements and procedures in the present subclause apply. + +If the IBCF receives an SDP offer and if the IBCF and the TrGW apply the transcoding procedure, defined in subclause 10.2.5.1, then the following additional actions may be performed: + +- if the received SDP offer (figure 10.2.5.2, step 1) contained the SDP "a=bw-info" attribute(s), defined in clause 19 of 3GPP TS 26.114 [36] for payload type(s) that the IBCF retains in the forwarded SDP offer, the IBCF: + - a) if the IP version interworking is required and the received "a=bw-info" SDP attribute lines do not contain bandwidth properties for both IPv4 and IPv6, should adjust the bandwidth properties in accordance with subclause 9.1.5; or + - b) otherwise (if the IP version interworking is not required or the received "a=bw-info" SDP attribute lines contain bandwidth properties for both IPv4 and IPv6), should forward the SDP offer with unmodified related SDP "a=bw-info" attribute(s); and + +NOTE 1: The IBCF can modify the related SDP "a=bw-info" attribute(s) according to operator policies as specified in 3GPP TS 26.114 [36]. + +- for the each added codec in the SDP offer (figure 10.2.5.2, step 6) the IBCF shall include appropriate bandwidth information in new or existing "a=bw-info" attribute lines(s). + +If the IBCF then receives an SDP answer (figure 10.2.5.2, step 8) and if only the codecs inserted by the IBCF with the corresponding SDP "a=bw-info" attribute(s) are contained in the SDP answer the IBCF: + +- when requesting the TrGW to configure resources towards the succeeding node (figure 10.2.5.2, step 9), shall include for the selected codec the "Additional Bandwidth Properties" information element containing "a=bw-info" SDP attribute(s) providing information for the selected codec in the remote descriptor about bandwidths that will be used for the selected codec in the sending direction towards the succeeding node; + +NOTE 2: The included information corresponds to "a=bw-info" SDP attribute(s) from the received SDP answer for the "recv" or "sendrecv" direction. + +- shall select a codec from the ones in the previously received SDP offer from the preceding node; +- if the received SDP offer contained the SDP "a=bw-info" attribute(s) for the selected codec: + - a) shall construct appropriate SDP "a=bw-info" attribute(s) for the selected codec according to the rules in 3GPP TS 26.114 [36]; and + +NOTE 3: The offer/answer negotiation is performed for each "a=bw-info" SDP attribute line, payload type, direction and bandwidth property individually. + +- b) shall include the "Additional Bandwidth Properties" information element containing "a=bw-info" SDP attribute(s) in the remote descriptor describing bandwidths that will be used for the selected codec in the sending direction towards the preceding node when requesting the TrGW to reserve resources towards the preceding node (figure 10.2.5.2, step 12); and + +NOTE 4: The included information corresponds to "a=bw-info" SDP attribute(s) in the sent SDP answer for the "send" or "sendrecv" direction. + +- include the selected codec with the corresponding SDP "a=bw-info" attribute(s) in the modified SDP answer (figure 10.2.5.2, step 15) that will be sent towards the preceding node. + +If the received SDP answer contains codecs received in the SDP offer no transcoding at the TrGW is required and the IBCF shall: + +- not include the "Additional Bandwidth Properties" information element containing the "a=bw-info" SDP attribute(s) when requesting the TrGW to configure resources towards the succeeding node (figure 10.2.5.2, step 9); +- not include the "Additional Bandwidth Properties" information element containing the "a=bw-info" SDP attribute(s) when requesting the TrGW to configure resources towards the preceding node (figure 10.2.5.2, step 12); and +- if the received SDP answer (figure 10.2.5.2, step 8) contained the SDP "a=bw-info" attribute(s), the IBCF shall check: + - a) if the IP version interworking is required and the received "a=bw-info" SDP attribute lines do not contain bandwidth properties for both IPv4 and IPv6, the IBCF may adjust the bandwidth properties in accordance with subclause 9.1.5; + - b) otherwise (if the IP version interworking is not required or the received "a=bw-info" SDP attribute lines contain bandwidth properties for both IPv4 and IPv6), the IBCF shall forward the SDP answer with unmodified SDP "a=bw-info" attribute(s). + +The TrGW may use the "Additional Bandwidth Properties" information element indicating media bandwidth range for rate adaption (i.e. to select an appropriate encoding and redundancy) when transcoding media streams. + +### 10.2.6 Media Inactivity Detection + +The procedures in subclause A.7.1.2.2.6 of 3GPP TS 29.235 [29] are applicable. + +### 10.2.7 QoS Packet Marking (differentiated services) + +The procedures in subclause A.7.1.2.2.4 of 3GPP TS 29.235 [29] are applicable. + +Those procedures relate to Diffserv code point marking as described in IETF RFC 2474 [31] + +### 10.2.8 Hanging Termination Detection + +The procedures in subclause A.7.1.2.2.2 of 3GPP TS 29.235 [29] are applicable. + +### 10.2.9 Bandwidth Policing + +The procedures in subclause A.7.1.2.2.8 of 3GPP TS 29.235 [29] are applicable. + +NOTE 1: In order to support services that generate media with variable bitrate (e.g. video), the policing function needs to provide sufficient buffer space. The derivation of the correspondent token bucket size can be based on the estimated traffic volume over the expected maximum burst length (supposed time interval of the burst). For example, for MTSI media, 3GPP TS 26.114 [36] subclause 7.5.5 recommends a default period of 2 seconds for the derivation of average bitrates and provides further considerations regarding suitable time periods for speech and video. + +NOTE 2: The IBCF can derive the sustainable data rate from bandwidth parameters if it receives them within an SDP media description. The IBCF can: + +- use the "b=AS" bandwidth modifier if received within an SDP body; or +- if the IBCF supports the enhanced bandwidth negotiation mechanism, use the "maximum supported bandwidth for the receiving direction" property value from the "a=bw-info" SDP attribute received within an SDP answer. + +If the value of the "maximum supported bandwidth for the receiving direction" for the selected RTP payload type differs from the value of the "b=AS" bandwidth modifier, then the IBCF can use "maximum supported bandwidth for the receiving direction" property value from the "a=bw-info" SDP attribute to determine the sustainable data rate for the selected RTP payload. + +### 10.2.10 IMS end-to-end media plane security + +#### 10.2.10.1 End-to-end security for RTP based media + +An IBCF and a TrGW may support the end-to-end IMS media plane security for RTP based media as specified in 3GPP TS 33.328 [32]. If supported, the IBCF shall use the following procedures. + +If the IBCF receives SDP containing media lines with "RTP/SAVP" (see IETF RFC 3711 [34]) or "RTP/SAVPF" (see IETF RFC 5124 [35]) as transport protocol, the IBCF shall: + +- forward the SDP with unmodified transport protocol for those media lines; +- apply the procedures to not offer or apply transcoding defined in subclause 10.2.5; and +- provide "RTP/SAVP" or "RTP/SAVPF", as received in the SDP, to the TrGW as transport protocol for all related terminations, and not provide media related information to these terminations, to configure the TrGW to pass media and possibly associated RTCP control flows and not to reserve any resources. + +NOTE: RTP/SAVP or SAVPF are provided to the TrGW even though it does not reserve any resources for this as such, but this is needed in order to allocate dual ports to support RTCP flows. These are also controlled as described in subclause 10.2.3. For "RTP/SAVP" or "RTP/SAVPF", RTCP will be encrypted and can not be interpreted by the TrGW. Media information is also meaningless as encryption will modify the properties of the media streams. + +If the IBCF receives SDP containing SDES SDP attribute(s) according to IETF RFC 4568 [33], IBCF shall forward the SDP with unmodified SDES SDP attribute(s), but shall not provide the SDES SDP attribute(s) to the TrGW. + +#### 10.2.10.2 End-to-end security for TCP based media using TLS + +An IBCF may support the end-to-end IMS media plane security for TCP based media using TLS as specified in 3GPP TS 33.328 [32]. If supported, the IBCF shall use the following procedures. + +NOTE: End-to-end IMS media plane security for TCP based media using TLS does not impact the TrGW. + +End-to-end protection of MSRP (used in IMS session-based messaging) and BFCP (used in IMS conferencing) media is based on TLS, according to the TLS profile specified in Annex M of 3GPP TS 33.328 [32]. + +If the IBCF receives SDP containing media lines with "TCP/TLS/MSRP" (see IETF RFC 4975 [47]) and IETF RFC 6714 [48]) and/or "TCP/TLS/BFCP" (see IETF RFC 4583 [49]) as transport protocol, the IBCF shall: + +- forward the SDP with unmodified transport protocol for those media lines and unmodified TLS related SDP attribute(s); and +- indicate "TCP" to the TrGW as transport protocol for all related terminations, and provide no media related information to these terminations, to configure the TrGW to pass media transparently. + +### 10.2.11 Through-Connection + +#### 10.2.11.1 General + +The procedures in subclause A.7.1.2.2.9 of 3GPP TS 29.235 [29] are applicable. + +In addition, prior to the completion of the SIP session set-up, i.e. until a 2xx response to the initial INVITE request is received, the IBCF may enable or disable media stream(s), thus allowing or forbidding early media in forward and/or backward direction. + +If there is: + +- 1) no SIP early dialog and the IBCF receives an 18x provisional response including an SDP answer; or +- 2) only one SIP early dialog, and the IBCF receives a SIP message with an SDP answer on that SIP early dialog, + +then; + +- 1) the IBCF shall save the received SDP answer; and +- 2) based on the operator policy, the IBCF may: + - set the value of the Through-Connection information element based on the value of the direction attribute in the received SDP answer; or + - set the value of the Through-Connection information element considering the em-param(s) of the P-Early-Media header field (defined in IETF RFC 5009 [58]) according to subclause 10.2.11.2; or + - set the value of the Through-Connection information element based on the value of the direction attribute in the received SDP answer downgraded according to the configuration provisioned in the IBCF. + +Upon reception of the 2xx response to the initial INVITE request, the IBCF shall enable the media stream by setting the value of the Through-Connection information element based on the value of the direction attribute in the last received SDP answer on the established SIP dialog, if the IBCF has not already set the value of the Through-Connection information element based on the same value of the direction attribute in the last received SDP answer on the corresponding SIP early dialog. + +NOTE: The setting of StreamMode property by through-connection control does not impact a "control flow" component (i.e. an RTCP control component) as described in ITU-T Recommendation H.248.1 [26]. + +After the session establishment (i.e. after the 2xx response to the INVITE request is received and media session is established), if the IBCF receives an SDP answer indicating a different media stream direction than the current setting of the StreamMode property of the termination(s), the IBCF shall set the value of the Through-Connection information element based on the received SDP answer. + +#### 10.2.11.2 Through-connect control procedures considering the P-Early-Media header field + +If the IBCF uses the em-param(s) of the P-Early-Media header field for the through-connect control of early media, the IBCF shall perform the procedures described in this subclause. + +When a SIP 18x provisional response to an initial INVITE request with the P-Early-Media header field is received from the functional entity within the trust domain, then: + +- the IBCF may decide not to perform the through-connect control of early media if the P-Early-Media header field includes the "gated" parameter and the IBCF shall not block early media in both directions on both terminations; and + - if the P-Early-Media header field includes the "gated" parameter and the IBCF decides to perform the through-connection control, or if the P-Early-Media header field does not include the "gated" parameter then the IBCF shall perform the procedures in the subsequent bullet 1), or the procedures in the subsequent bullet 2), or both of those procedures. If the IBCF does not perform the procedures in the bullets 1) or 2), the IBCF shall not block early media in both directions on the termination for which the IBCF does not perform the procedures in the bullet 1) or 2). +- 1) For the termination which resides on the side receiving the 18x provisional response: + - a) if the received em-param(s) in the P-Early-Media header field is set to "sendrecv", the IBCF shall set the Through-Connection information element to "sendrecv"; + - b) if the received em-param(s) in the P-Early-Media header field is set to "recvonly", the IBCF shall set the Through-Connection information element to "sendonly"; + - c) if the received em-param(s) in the P-Early-Media header field is set to "sendonly", the IBCF shall set the Through-Connection information element to "recvonly"; and + - d) if the received em-param(s) in the P-Early-Media header field is set to "inactive", the IBCF shall set the Through-Connection information element to "inactive". + - 2) For the termination which resides on the side forwarding the 18x provisional response: + - a) if the received em-param(s) in the P-Early-Media header field is set to "sendrecv", the IBCF shall set the Through-Connection information element to "sendrecv"; + - b) if the received em-param(s) in the P-Early-Media header field is set to "sendonly", the IBCF shall set the Through-Connection information element to "sendonly"; + - c) if the received em-param(s) in the P-Early-Media header field is set to "recvonly", the IBCF shall set the Through-Connection information element to "recvonly"; and + - d) if the received em-param(s) in the P-Early-Media header field is set to "inactive", the IBCF shall set the Through-Connection information element to "inactive". + +NOTE 1: According to IETF RFC 5009 [58], the non-direction parameter "gated" can be included after the direction parameter (e.g. "sendrecv") in the parameter list. The proxy performing gating of early media can add the parameter before forwarding the response. + +NOTE 2: It is regarded as an error case if the direction authorized by the P-Early-Media header field is not enabled in the received SDP direction attribute. As indicated in IETF RFC 5009 [58] the applicable preconditions need to be met in order to allow early media in a particular direction, but the related handling is left to the implementation. + +When an 18x provisional response to an initial INVITE request without the P-Early-Media header field is received from the functional entity within the trust domain and no previous 18x provisional response to the initial INVITE request with the P-Early-Media header field has been received, then the IBCF may: + +- 1) set the Through-Connection information element to "inactive"; or +- 2) set the Through-Connection information element to the value of the direction attribute in the last received SDP answer (received in the 18x provisional response or in a previous SIP message); or +- 3) set the value of the Through-Connection information element based on the value of the direction attribute in the received SDP answer (received in the 18x provisional response or in a previous SIP message) downgraded according to the configuration provisioned in the IBCF. + +When an 18x provisional response to an initial INVITE request with the P-Early-Media header field is received from the functional entity other than the functional entity within the trust domain, then the IBCF shall not use the received em-param(s) in the P-Early-Media header field and the IBCF shall: + +- 1) set the Through-Connection information element to "inactive"; or + +- 2) set the Through-Connection information element based on the value of the direction attribute in the last received SDP answer(received in the 18x provisional response or in a previous SIP message); or +- 3) set the value of the Through-Connection information element based on the value of the direction attribute in the received SDP answer (received in the 18x provisional response or in a previous SIP message) downgraded according to the configuration provisioned in the IBCF. + +NOTE 3: The IBCF will remove or modify the P-Early-Media header field in the above case. + +### 10.2.12 Emergency Call + +The procedures in subclause A.7.1.2.2.10 of 3GPP TS 29.235 [29] are applicable. + +### 10.2.13 Explicit Congestion Notification support + +#### 10.2.13.1 General + +An IBCF and TrGW may support Multimedia Telephony using Explicit Congestion Notification (ECN) according to IETF RFC 3168 [37], and may act as an ECN endpoint to enable ECN with a local ECN-capable terminal within a local network that properly handles ECN-marked packets. + +#### 10.2.13.2 Incoming SDP offer with ECN + +If the IBCF receives an SDP offer containing the "a=ecn-capable-rtp" attribute (see IETF RFC 6679 [38]), then if all of the following statements are true: + +- a) the IBCF supports ECN according to 3GPP TS 26.114 [36]; +- b) the TrGW supports ECN according to 3GPP TS 26.114 [36]; +- c) the IBCF knows (via configuration) that the succeeding network supports ECN according to 3GPP TS 26.114 [36]; and +- d) the IBCF does not insert any transcoding; + +then the IBCF shall: + +- if the "ecn-capable-rtp" attribute includes both the "ice" initiation method and other initiation methods, remove the "ice" initiation method from the "ecn-capable-rtp" attribute and forward the attribute with this modification in the outgoing SDP offer; +- if the "ecn-capable-rtp" attribute only includes the "ice" initiation method, remove the "ecn-capable-rtp" attribute, any "rtcp-fb" attribute with the "nack" feedback parameter and the "ecn" feedback parameter value, and any "ecn-sum" parameter within a "rtcp-xr" attribute from the outgoing SDP offer; +- if the "ecn-capable-rtp" attribute did not include the "ice" initialisation method, forward the unmodified "ecn-capable-rtp" attribute within the outgoing SDP offer; and +- if the IBCF includes the "ecn-capable-rtp" attribute within the outgoing SDP offer, forward the SDP offer containing ECN parameters to the succeeding network. + +Otherwise the IBCF shall remove the "ecn-capable-rtp" attribute, any "rtcp-fb" attribute with the "nack" feedback parameter and the "ecn" feedback parameter value, and any "ecn-sum" parameter within an "rtcp-xr" attribute from the outgoing SDP offer. + +If the IBCF forwarded the SDP offer containing the "a=ecn-capable-rtp" attribute and receives an SDP answer also containing the "a=ecn-capable-rtp" attribute (the reception of the attribute indicates a successful ECN negotiation) then the IBCF shall forward the SDP answer to its preceding node and shall indicate to the TrGW that it shall transfer ECN bits in IP header transparently. + +If the IBCF forwarded the SDP offer containing the "a=ecn-capable-rtp" attribute and receives an SDP answer without the "a=ecn-capable-rtp" attribute and the TrGW supports at least some of the initialisation methods within the "a=ecn-capable-rtp" attribute in the previously received SDP offer, + +NOTE 1: Only the "leap" initialisation method is supported over the Ix interface in this release. + +the IBCF shall: + +- act as an end point for ECN; +- select an initialisation method supported by the TrGW; +- determine if application specific feedback or ECN feedback messages shall be used, taking into account whether the TrGW supports ECN feedback messages, and the negotiation procedures in 3GPP TS 26.114 [36]; +- determine if ECN XR summary reports can be used, taking into account whether they are supported at the TrGW, and the negotiation procedures in 3GPP TS 26.114 [36]; +- send the SDP answer according to 3GPP TS 26.114 [36] and the capabilities of the TrGW, containing the ECN attribute "a=ecn-capable-rtp"; and +- indicate to the TrGW that it shall apply the ECN procedures (according to 3GPP TS 26.114 [36]) and act as an ECT endpoint. + +If the IBCF receives an SDP offer containing the "a=ecn-capable-rtp" attribute and bullets a) and b) above are satisfied but if bullet c) or d) or both are not met then the IBCF shall remove ECN related attributes before forwarding the SDP offer. If the TrGW supports at least some of the initialisation methods offered within the "a=ecn-capable-rtp" attribute, + +NOTE 2: Only the "leap" initialisation method is supported over the Ix interface in this release. + +the IBCF shall: + +- act as an end point for ECN; +- select an initialisation method supported by the TrGW; +- determine if application specific feedback or ECN feedback messages shall be used, taking into account whether the TrGW supports ECN feedback messages, and the negotiation procedures in 3GPP TS 26.114 [36]; +- determine if ECN XR summary reports can be used, taking into account whether they are supported at the TrGW and the negotiation procedures in 3GPP TS 26.114 [36]; +- send an SDP answer according to 3GPP TS 26.114 [36] and the capabilities of the TrGW, containing the "a=ecn-capable-rtp" attribute; and +- indicate to the TrGW that it shall apply the ECN procedures (according to 3GPP TS 26.114 [36]) and act as an ECT endpoint. + +The TrGW should not send RTCP XR ECN summary reports. + +#### 10.2.13.3 Incoming SDP offer without ECN + +If the IBCF receives an SDP offer without the "a=ecn-capable-rtp" attribute then if all of the following statements are true: + +- a) the IBCF supports ECN according to 3GPP TS 26.114 [36]; +- b) the TrGW supports ECN according to 3GPP TS 26.114 [36]; and +- c) the IBCF knows (via configuration) that the succeeding network supports ECN according to 3GPP TS 26.114 [36]; + +the IBCF may include the "a=ecn-capable-rtp" attribute in the SDP offer it forwards towards the succeeding node, indicating the related capabilities of the TrGW. + +NOTE: ECN XR summary reports and RTCP AVPF ECN feedback message are not supported in this release towards IMS terminations. + +If the IBCF inserted ECN attributes in the SDP offer and receives an SDP answer containing the "a=ecn-capable-rtp" attribute the IBCF shall act as an endpoint and shall return the SDP answer to the preceding node removing the "a=ecn-capable-rtp" attribute, any "rtcp-fb" attribute with the "nack" feedback parameter and the "ecn" feedback parameter value, and any "ecn-sum" parameter within a "rtcp-xr" attribute, and shall indicate to the TrGW that it shall apply the + +ECN procedures according to 3GPP TS 26.114 [36] and act as an ECT endpoint. The TrGW should not send RTCP XR ECN summary reports. + +If the IBCF inserted the "a=ecn-capable-rtp" attribute in the SDP offer and receives an SDP answer without the "a=ecn-capable-rtp" attribute the IBCF shall continue the call without any ECN active. + +#### 10.2.13.3a Detection of ECN failures by TrGW + +If the TrGW acts as ECN endpoint and detects an ECN-related error case, for example non-ECT in the received packets when ECT(0) was expected or detecting a very high packet loss rate when ECN is used, the TrGW shall notify the IBCF. The IBCF should then initiate a session re-negotiation to disable ECN. + +#### 10.2.13.4 Interworking with non-3GPP ECN IP terminal + +##### 10.2.13.4.1 Support for additional ECN parameters + +An IBCF and TrGW may support additional ECN parameter settings than defined in subclause 10.2.13.2. The following sub-clauses describe the optional behaviour if the IBCF and TrGW support these additional values. + +##### 10.2.13.4.2 Incoming SDP offer from external IP network with ECN + +If the IBCF receives an incoming SDP offer from the external IP network containing values in the incoming SDP offer not supported by MTSI then it shall configure the SDP offer as defined in subclause 10.2.13.2 when forwarding the SDP offer to the IMS. + +When receiving the SDP answer from the IMS the IBCF may configure the SDP answer to the external IP network with alternative settings depending on what is received from the IMS and what was offered by the external IP network. The permitted alternatives are listed in table 10.2.13.4.1; the supported alternatives are implementation options which need to be derived through configuration or package auditing. + +##### 10.2.13.4.3 Incoming SDP offer from the IMS with ECN + +If the IBCF receives an incoming SDP offer from the IMS and it supports additional ECN parameter settings than those defined in subclause 10.2.13.2 the IBCF may add these to the SDP offer forwarded to the external IP network. + +When receiving an SDP answer from the external IP network the IBCF shall respond to the IMS in accordance with subclause 10.2.13.2. If the IBCF modifies any ECN-related parameters in the forwarded SDP answer compared to the received SDP answer, the IBCF shall configure its TrGW as an ECN endpoint. The permitted alternatives are listed in table 10.2.13.4.1; the supported alternatives are implementation options which need to be derived through configuration or package auditing. + +**Table 10.2.13.4.1: Possible configurations when interworking with non-3GPP ECN IP terminal** + +| ECN SDP Attribute and required TrGW Action | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMS side | External IP Network | TrGW Action | +| Initiation | | | +| "leap" | "rtp"
NOTE 3 | Act as an Endpoint and trigger explicit initiation using RTP and RTCP as described in IETF RFC 6679 [38] toward the external IP network. When initial ECT marked packets are received from the external IP network these are forwarded to the IMS (all packets shall be marked) and early feedback and XR Summary reports are sent back to the external IP network. If ECT marked packets are received from the IMS before any initiation is completed with the external IP network then ECT marking should be removed and only a fraction of the packets should be marked until feedback is received from the external IP network. | +| | "ice" | This initiation method is not supported in the present release. | +| Mode | | | +| "setread" | "readonly" | Act as ECN transparent unless required to act as an Endpoint for other reasons but mark packets toward the IMS with ECT(0). If ECN-CE is received from the IMS then this shall be handled by the IMS termination as currently specified for the non-interworking case and not forwarded to the external IP network. | +| | "setonly" | Act as ECN transparent (unless required to act as ECN Endpoint for other reasons) - ECN-CE marked packets will not be received from external IP network, ECN-CE marked packets from the IMS will be passed to the external IP network. | +| ECT | | | +| "ect(0)" | "ect(1)" | Act as ECN transparent unless required to act as an Endpoint for other reasons but mark packets toward the IMS with ECT(0) and mark packets toward external network with ECT(1). | +| | "random" | Act as ECN transparent unless required to act as an Endpoint for other reasons but mark packets toward IMS with ECT(0). Packets received from the IMS are left as ECT(0). | +| RTCP feedback | | | +| no "rtcp-fb:* nack ecn"
(received driven congestion control) | "rtcp-fb:* nack ecn" (sender driven congestion control) | For AMR, the handling of an AVPF feedback message received from the external IP the handling is not defined.
For video related AVFP feedback messages received from the external IP network the TrGW shall generate the appropriate TMBR request towards the IMS. If a TMBR request is received from the IMS the TrGW shall generate an appropriate AVPF feedback message to the external IP network. | +| "rtcp-fb:* nack ecn"
(sender driven congestion control) | "rtcp-fb:* nack ecn" (sender driven congestion control) | An AVPF feedback message received from the external IP network shall be forwarded via the IMS termination. | +| RTCP XR ECN summary report | | | +| - | "rtcp-xr:ecn-sum" | RTCP XR is not bi-directions and each end-point indicates whatever XR feedback it supports. Hence, if the SDP offer does not contain rtcp-xr with "ecn-sum" then it can still be added in the SDP answer.
The TrGW shall include XR ECN Summary reports towards the external IP network and receive reports from the external IP network. (NOTE 4) | +| NOTE 1: The settings for IMS side may be supported on the External IP Network side in which case no interworking is specified. | | | +| NOTE 2: Each parameter is described separately as each parameter may or may not need to be interworked. Unless stated otherwise the assumption is that each parameter can be treated independently. | | | +| NOTE 3: RTCP feedback messages need to be supported and negotiated for the "rtp" initialisation method. | | | +| NOTE 4: The contents of the XR reports will be limited to data received from the external IP network. | | | + +#### 10.2.13.5 Message sequence chart + +##### 10.2.13.5.1 ECN support requested (ECN endpoint) + +Figure 10.2.13.5.1.1 shows the message sequence chart example for requesting ECN. + +![Sequence diagram for Figure 10.2.13.5.1.1: Procedure to Request ECN. The diagram shows two lifelines: IBCF and TrGW. The IBCF sends a Context(Cx) message to the TrGW containing an H.248:ADD.req with Termination X, Transport = RTP/AVPF, ECN_enable=True, and {Notify_ECN_Error}. The TrGW responds with a Context(Cx) message containing an H.248:ADD.resp[Termination X]. The TrGW also performs internal actions: Reserve IMS Connection Point and Configure Remote Resources.](030c758fd425016b03290c8f11bef69d_img.jpg) + +``` +sequenceDiagram + participant IBCF + participant TrGW + Note right of TrGW: Reserve IMS Connection Point and Configure Remote Resources + IBCF->>TrGW: Context(Cx) [H.248:ADD.req[ Termination X, Transport = RTP/AVPF, ECN_enable=True, {Notify_ECN_Error}]] + TrGW-->>IBCF: Context(Cx) [H.248:ADD.resp[Termination X]] +``` + +Sequence diagram for Figure 10.2.13.5.1.1: Procedure to Request ECN. The diagram shows two lifelines: IBCF and TrGW. The IBCF sends a Context(Cx) message to the TrGW containing an H.248:ADD.req with Termination X, Transport = RTP/AVPF, ECN\_enable=True, and {Notify\_ECN\_Error}. The TrGW responds with a Context(Cx) message containing an H.248:ADD.resp[Termination X]. The TrGW also performs internal actions: Reserve IMS Connection Point and Configure Remote Resources. + +**Figure 10.2.13.5.1.1: Procedure to Request ECN** + +Upon receipt of a request to apply ECN the TrGW shall set the ECN field of the IP header in accordance with 3GPP TS 26.114 [36] when sending any data packets. + +Upon receipt of any IP headers indicating ECN Congestion Experienced (ECN-CE) the TrGW shall trigger rate adaptation in accordance with 3GPP TS 26.114 [36]. + +NOTE: ECN requires the IBCF to configure the TrGW with all media attributes to allow rate adaptation even if no transcoding is required/supported in the TrGW. + +##### 10.2.13.5.2 ECN Active Indicated (ECN transparent) + +Figure 10.2.13.5.2.1 shows the message sequence chart example for indicating ECN transparent. + +![Sequence diagram for Figure 10.2.13.5.2.1: Procedure to indicate ECN transparent negotiated. The diagram shows two lifelines: IBCF and TrGW. The IBCF sends a Context(Cx) message to the TrGW containing an H.248:ADD.req with Termination X, Transport = RTP/AVPF, ECN_enable = True, and Initialisation_Method = Inactive. The TrGW responds with a Context(Cx) message containing an H.248:ADD.resp[Termination X]. The TrGW also performs internal actions: Reserve IMS Connection Point and Configure Remote Resources.](5879500ca01e1a2521654beff6c289a4_img.jpg) + +``` +sequenceDiagram + participant IBCF + participant TrGW + Note right of TrGW: Reserve IMS Connection Point and Configure Remote Resources + IBCF->>TrGW: Context(Cx) [H.248:ADD.req[ Termination X, Transport = RTP/AVPF, ECN_enable = True, Initialisation_Method = Inactive]] + TrGW-->>IBCF: Context(Cx) [H.248:ADD.resp[Termination X]] +``` + +Sequence diagram for Figure 10.2.13.5.2.1: Procedure to indicate ECN transparent negotiated. The diagram shows two lifelines: IBCF and TrGW. The IBCF sends a Context(Cx) message to the TrGW containing an H.248:ADD.req with Termination X, Transport = RTP/AVPF, ECN\_enable = True, and Initialisation\_Method = Inactive. The TrGW responds with a Context(Cx) message containing an H.248:ADD.resp[Termination X]. The TrGW also performs internal actions: Reserve IMS Connection Point and Configure Remote Resources. + +**Figure 10.2.13.5.2.1: Procedure to indicate ECN transparent negotiated** + +Upon receipt of the indication that ECN transparent has been negotiated the TrGW shall forward IP packets with ECN bits set unmodified. + +##### 10.2.13.5.3 ECN Failure Indication (ECN endpoint) + +Figure 10.2.13.5.3.1 shows the message sequence chart example for an ECN Failure Event. + + + +``` + +sequenceDiagram + participant IBCF + participant TrGW + Note left of IBCF: Context(Cx) + IBCF->>TrGW: H.248:NOTIFY.req(ECN Failure) +[Termination =x, cause=ecn_cause] + TrGW-->>IBCF: H.248:NOTIFY.resp(ECN Failure) +[Termination x] + Note right of TrGW: Report ECN Failure + Note left of IBCF: Context(Cx) + +``` + +Sequence diagram showing the procedure to report ECN failure between IBCF and TrGW. The IBCF sends an H.248:NOTIFY.req(ECN Failure) message to the TrGW. The TrGW responds with an H.248:NOTIFY.resp(ECN Failure) message. The IBCF then reports the ECN failure to the Context(Cx). + +**Figure 10.2.13.5.3.1: Procedure to Report ECN Failure** + +When the IBCF receives a Notification indicating that a failure has occurred, the MGCF may trigger a new SDP offer to disable ECN. + +### 10.2.14 Optimal Media Routeing + +An IBCF may support optimal media routeing (OMR) procedures, as defined in 3GPP TS 29.079 [39]. + +3GPP TS 29.079 [39] specifies that "secondary media resources" may be allocated in addition to "primary media resources". If controlled by an IBCF, such primary or secondary media resources are TrGWs controlled over the Ix interface with procedures specified in the present specification. + +If the IBCF applies OMR procedures, the following modifications to the procedures within the present specification are applicable: + +- Under conditions specified in 3GPP TS 29.079 [39], the IBCF uses information from OMR related SDP attributes as remote connection and port information that is provided towards the TrGW within the call establishment procedures in subclause 10.1.3.1.1. +- Under conditions specified in 3GPP TS 29.079 [39], the IBCF encapsulates local address and port information, as received from the TrGW within the call establishment procedures in subclause 10.1.3.1.1, in OMR related SDP attributes. +- Under conditions specified in 3GPP TS 29.079 [39], the IBCF uses information from OMR related SDP attributes as codec information that is provided towards the TrGW within the media control procedures in clause 10.2.5. +- 3GPP TS 29.079 [39] specifies OMR-specific events that trigger the call release procedures in subclause 10.1.3.1.2. + +### 10.2.15 IP Realm Availability + +The procedures in subclause A.7.1.2.2.5 of 3GPP TS 29.235 [29] are applicable. + +### 10.2.16 Access Transfer procedures with media anchored in ATGW + +The procedures in the present clause are optional to be supported for both IBCF and TrGW when supporting the ATCF and ATGW functionality (see subclause 6.1.4). + +The procedures in subclause 6.2.14 of 3GPP TS 23.334 [43] are applicable, except that where the Iq interface is mentioned in those procedures, the Ix interface is applicable. + +### 10.2.17 Multimedia Priority Service (MPS) Support + +#### 10.2.17.1 General + +The Multimedia Priority Service (MPS) is specified in 3GPP TS 22.153 [44]. The IBCF/TrGW may support the priority treatment of a call/session identified as an MPS call/session. If MPS is supported then upon receipt of the MPS priority information in the call control signalling: + +- The IBCF shall recognise the call/session as having priority. +- The IBCF shall send the Priority information for a context to the TrGW to enable the priority treatment described below related to the TrGW. +- The IBCF shall apply priority handling to H.248 transactions related to priority calls/sessions when network resources are congested, e.g., preferential treatment in any queues or buffers. +- The IBCF may send the updated priority information and, if DiffServ is used, provision a suitable DSCP marking for the updated MPS priority level to the TrGW if it needs to change the priority information previously communicated to the TrGW for an MPS call/session. +- If the H.248 control association utilises a transport with the possibility for prioritisation, the IBCF may apply priority using the appropriate prioritisation procedures. +- If the MPS Priority service requires a specific MPS DSCP setting, the IBCF shall configure the TrGW to apply a specific MPS DSCP marking to the user data transport packets to indicate that the packets are of a higher priority than those for normal calls. +- If the TrGW receives an indication to apply a specific MPS DSCP marking to the user data transport packets, it shall apply this DSCP marking to the IP headers. + +NOTE 1: Support of Diffserv procedures by the TrGW assumes an operator uses Diffserv for prioritising user plane traffic related to an MPS call/session. + +- When the IBCF marks a Context with Priority information, the TrGW may use the Priority information for selecting resources for the media and signaling transport with priority. The following actions may be taken by the TrGW if it has reached a congested state: + - i) seize priority reserved resources; or + - ii) if resources are completely congested, indicate that in a Command Response error code. + +NOTE 2: The Priority information can be used to derive Layer 2 QoS marking and trigger priority identification and priority treatment for other QoS technologies than Diffserv. + +This clause describes the Ix signalling procedures and their interactions with SIP signalling in the control plane and with user plane procedures to support the requirements for MPS. These Ix signalling procedures may or may not apply depending on the network configuration (e.g. whether the TrGW is shared by multiple IBCFs or whether the IBCF controls multiple TrGWs for a given route – Media Gateway Group). + +The IBCF can receive a SIP INVITE with MPS priority information (see 3GPP TS 23.228 [8], subclause 5.21). + +#### 10.2.17.2 TrGW Resource Congestion in ADD response, request is queued + +If the IBCF requests a resource via the Reserve and Configure TrGW Connection Point procedure or Reserve TrGW Connection Point procedure and receives an error indicating that the requested resource could not be seized (e.g. H.248 error code #510 "insufficient resources") and the IBCF does not have an alternative TrGW through which it can route the call/session, the IBCF queues the priority call/session and gives it priority over any further Reserve and Configure TrGW Connection Point or Reserve TrGW Connection Point procedures for lower priority calls/sessions towards this TrGW until the requested resource for this queued call/session is successfully seized. The example sequence is shown in Figure 10.2.17.2.1. + +![Sequence diagram showing the request to reserve MPS priority call resources when TrGW is congested. The diagram involves two main entities: IBCF and TrGW. The sequence starts with an INVITE [MPS priority indication] to the IBCF. The IBCF then sends an H.248 ADD Req to the TrGW. The TrGW responds with an H.248 ADD Reject [Error = #510] due to congestion. The IBCF then queues the MPS request. After some time, the IBCF sends another H.248 ADD Req to the TrGW, which now successfully seizes the required resources and responds with an H.248 ADD Resp.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +``` + +sequenceDiagram + participant IBCF + participant TrGW + Note left of IBCF: 1. INVITE [MPS priority indication] + Note left of IBCF: Reserve TrGW Connection Point + IBCF->>TrGW: 2. H.248 ADD Req [C=?, T=?, Laddr=?, Lport=?, Local Resources, Priority] + TrGW-->>IBCF: 3. H.248 ADD Reject [Error = #510] + Note right of TrGW: TrGW is congested + Note left of IBCF: 4. IBCF queues MPS request + Note left of IBCF: Reserve TrGW Connection Point + IBCF->>TrGW: 5. H.248 ADD Req [C=?, T=?, Laddr=?, Lport=?, Local Resources, Priority] + TrGW-->>IBCF: 6. H.248 ADD Resp [C=C1, T=T2, Laddr=IP2o, LPort=P2o] + Note right of TrGW: TrGW successfully seizes required resources + +``` + +Sequence diagram showing the request to reserve MPS priority call resources when TrGW is congested. The diagram involves two main entities: IBCF and TrGW. The sequence starts with an INVITE [MPS priority indication] to the IBCF. The IBCF then sends an H.248 ADD Req to the TrGW. The TrGW responds with an H.248 ADD Reject [Error = #510] due to congestion. The IBCF then queues the MPS request. After some time, the IBCF sends another H.248 ADD Req to the TrGW, which now successfully seizes the required resources and responds with an H.248 ADD Resp. + +**Figure 10.2.17.2.1: Request to Reserve MPS priority call resources when TrGW is congested** + +#### 10.2.17.3 TrGW Resource Congestion in ADD response, IBCF seizes new TrGW + +If the IBCF requests a resource via the Reserve and Configure TrGW Connection Point procedure or Reserve TrGW Connection Point procedure and receives an error indicating that the requested resources could not be seized due to congestion (e.g. H.248 error code #510 "insufficient resources") and Media Gateway Groups are implemented the IBCF seizes a new TrGW from the same Media Gateway Group before resorting to any queuing of the priority call/session (as described in subclause 10.2.17.2) to enable the MPS call/session to proceed as early as possible. + +#### 10.2.17.4 TrGW Priority Resource Allocation + +If the TrGW supports the Priority information (e.g. determined through provisioning or package profile), the IBCF requests a resource via the Reserve and Configure TrGW Connection Point procedure or Reserve TrGW Connection Point procedure and includes the Priority information. The TrGW may then provide priority allocation of resources once a congestion threshold is reached. The example sequence is shown in figure 10.2.17.4.1. If the TrGW is completely congested it shall indicate this to the IBCF as described in subclause 10.2.17.2. + +![Sequence diagram showing the request to reserve MPS priority call resources when TrGW is congested, but priority resources are allocated. The diagram involves two main entities: IBCF and TrGW. The sequence starts with an INVITE [MPS priority indication] to the IBCF. The IBCF then sends an H.248 ADD Req to the TrGW. The TrGW responds with an H.248 ADD Resp [C=C1, T=T2, Laddr=IP2o, LPort=P2o] because it is in a congested state but allocates priority resources to this call.](9dc9f41d7d76c1add4b190d348cb1533_img.jpg) + +``` + +sequenceDiagram + participant IBCF + participant TrGW + Note left of IBCF: 1. INVITE [MPS priority indication] + Note left of IBCF: Reserve TrGW Connection Point + IBCF->>TrGW: 2. H.248 ADD Req [C=?, T=?, Laddr=?, Lport=?, Local Resources, Priority] + TrGW-->>IBCF: 3. H.248 ADD Resp [C=C1, T=T2, Laddr=IP2o, LPort=P2o] + Note right of TrGW: TrGW is in a congested state but allocates priority resources to this call. + +``` + +Sequence diagram showing the request to reserve MPS priority call resources when TrGW is congested, but priority resources are allocated. The diagram involves two main entities: IBCF and TrGW. The sequence starts with an INVITE [MPS priority indication] to the IBCF. The IBCF then sends an H.248 ADD Req to the TrGW. The TrGW responds with an H.248 ADD Resp [C=C1, T=T2, Laddr=IP2o, LPort=P2o] because it is in a congested state but allocates priority resources to this call. + +**Figure 10.2.17.4.1: Request to reserve MPS priority call resources when TrGW is congested, priority resources are allocated** + +The TrGW may also provide priority allocation for resources requested via a subsequent Configure TrGW Connection Point procedure not including Priority information if the related context has been marked with priority information during the Reserve TrGW Connection Point or Reserve and Configure TrGW Connection Point procedure. + +#### 10.2.17.5 TrGW Priority User Data marking + +The IBCF may request the streams associated to an MPS call/session to be marked with certain priority code point as described in subclause 10.2.7. The TrGW shall then mark each IP packet header accordingly. The example sequence is shown in figure 10.2.17.5.1. + + + +``` + +sequenceDiagram + participant Ext as External + participant IBCF + participant TrGW + Ext->>IBCF: 1. INVITE [MPS priority indication] + Note over IBCF, TrGW: Reserve TrGW Connection Point + IBCF->>TrGW: 2. H.248 ADD Req [C=?, T= ?, Laddr = ?, Lport = ?, Local Resources, Diffserv Mark = DSCP1, Priority] + Note right of TrGW: TrGW is requested to apply DSCP value in IP header of user data packets. + TrGW-->>IBCF: 3. H.248 ADD Resp [C=C1, T=T2, Laddr=IP2o, LPort=P2o] + +``` + +The diagram illustrates a sequence of messages between an IBCF and a TrGW. It starts with an external INVITE message (1) with an MPS priority indication entering the IBCF. A bracket on the IBCF side labeled 'Reserve TrGW Connection Point' encompasses the subsequent H.248 messages. The IBCF sends a request (2) 'H.248 ADD Req [C=?, T= ?, Laddr = ?, Lport = ?, Local Resources, Diffserv Mark = DSCP1, Priority]' to the TrGW. A note on the TrGW side indicates that it is requested to apply the DSCP value in the IP header of user data packets. The TrGW responds (3) with 'H.248 ADD Resp [C=C1, T=T2, Laddr=IP2o, LPort=P2o]'. + +Sequence diagram showing the request to reserve IMS resources and apply DSCP marking for MPS between IBCF and TrGW. + +**Figure 10.2.17.5.1: Request to reserve IMS resources and apply DSCP marking for MPS** + +#### 10.2.17.6 TrGW Priority Modification + +If the IBCF seized an IP termination for a priority call/session with a default priority and subsequently needs to modify the priority information previously communicated to the TrGW (e.g. subject to subsequent authorisation by an authorisation point, see 3GPP TS 24.229 [1] subclause 4.11), the IBCF may modify the existing IP termination for the MPS call/session with the actual priority and, if DiffServ is used, provision a suitable DSCP marking for the updated MPS priority level to the TrGW via the Configure TrGW Connection Point Procedure. + +NOTE: The specific Ix related call sequence which details the handling to support the requirements defined in 3GPP TS 24.229 [1] subclause 4.11 and 3GPP TS 23.228 [8], subclause 5.21 is not specified and therefore implementations might exist which fulfil these requirements but do not require modification of the priority information across the Ix interface. + +### 10.2.18 Coordination of Video Orientation + +#### 10.2.18.1 General + +The IBCF and the TrGW may support the Coordination of Video Orientation (CVO) as defined in 3GPP TS 26.114 [36]. + +If the IBCF receives an SDP body containing the RTP header extension attribute(s) "a=extmap", as defined in IETF RFC 5285 [45], and if "a=extmap" attribute indicates a CVO URN(s) (i.e. the CVO URN for a 2 bit granularity of rotation and/or the CVO URN for a higher granularity of rotation) as defined in 3GPP TS 26.114 [36], then: + +- a) if the IBCF and the TrGW support the CVO feature: + - the IBCF shall include an "extended RTP header for CVO" information element when seizing resources in the TrGW to indicate to the TrGW that it shall allow the RTP header extension for CVO to pass; and + - the IBCF shall forward within SIP signalling the SDP body received from the preceding node to the succeeding node with unmodified "a=extmap" attribute(s); or +- b) if the TrGW does not support the CVO feature the IBCF shall forward within SIP signalling, the SDP body received from the preceding node to the succeeding node without any "a=extmap" attributes. + +If the TrGW supports the CVO feature and has been instructed as described above to pass on the extended RTP header for CVO for both incoming and outgoing terminations then: + +- if the TrGW does not apply video transcoding, it shall pass any received RTP CVO header extension to succeeding RTP streams; or + +- if the TrGW applies video transcoding, it shall keep the video orientation unchanged during the transcoding and copy the received RTP CVO header extension to the succeeding outgoing RTP stream(s) after transcoding the associated group of packets. + +NOTE 1: IETF RFC 5285 [45] provides a framework for header extensions and can also be used for non-CVO related purposes. It is an implementation decision of the TrGW if it only passes CVO related RTP header extensions, or if it passes any RTP header extension when being instructed with the "extended RTP header for CVO" information element. + +NOTE 2: The behaviour of the TrGW when being instructed with the "extended RTP header for CVO" information element only at one termination is an implementation decision. + +#### 10.2.18.2 Message sequence chart + +Figure 10.2.18.2.1 shows the message sequence chart example for indicating extended RTP header for Coordination of Video Orientation. + + + +``` +sequenceDiagram + participant IBCF + participant TrGW + Note left of IBCF: INVITE with SDP offer ["a=extmap: URN=CVO"] + IBCF->>TrGW: H.248: ADD req. [C=?, T= ?, Laddr = ?, Lport = ?, Local Resources, Extended RTP header(CVO)] + Note right of TrGW: Reserve TrGW Connection Point + TrGW-->>IBCF: H.248: ADD resp. [Termination T2...] + Note left of IBCF: INVITE with SDP offer ["a=extmap: URN=CVO"] + IBCF->>TrGW: SIP msg with SDP answer ["a=extmap: URN=CVO"] + Note left of IBCF: H.248: ADD req. [C=C, T= ?, Laddr = ?, Lport = ?, Local Resources, Extended RTP header(CVO)] + Note right of TrGW: Reserve and Configure TrW Connection Point + TrGW-->>IBCF: H.248: ADD resp. [Termination T1...] + Note left of IBCF: SIP msg with SDP answer ["a=extmap: URN=CVO"] + IBCF-->>TrGW: +``` + +The sequence diagram illustrates the interaction between an IBCF (Initiating Border Controller Function) and a TrGW (Traffic Gateway) to indicate the use of an extended RTP header for CVO (Coordination of Video Orientation). The process begins with an external INVITE with SDP offer containing the 'a=extmap: URN=CVO' attribute. The IBCF sends an H.248: ADD request to the TrGW, specifying the CVO header extension. The TrGW reserves a connection point and responds with H.248: ADD resp. [Termination T2...]. The IBCF then sends another INVITE with SDP offer with the CVO attribute and a SIP msg with SDP answer. The IBCF sends a second H.248: ADD request to the TrGW, this time with 'C=C' (indicating it is the selected connection). The TrGW reserves and configures the connection point and responds with H.248: ADD resp. [Termination T1...]. Finally, the IBCF sends a SIP msg with SDP answer with the CVO attribute. + +Sequence diagram showing the procedure to indicate RTP extension header for CVO between IBCF and TrGW. + +**Figure 10.2.18.2.1: Procedure to indicate RTP extension header for CVO** + +The IBCF shall send the "extended RTP header for CVO" information element only with supported CVO URN(s) to the TrGW. If the TrGW does not support the CVO feature, the IBCF shall not send the "extended RTP header for CVO" information element to the TrGW. + +NOTE: If the IBCF receives an SDP answer which includes the "a=extmap" attribute with a CVO URN with a granularity that the TrGW has not included in its response, or if the SDP answer does not include any "a=extmap" CVO related attribute, it is not necessary to modify the TrGW for this reason alone. Doing that would only add unnecessary signalling without requiring any action or changes in the TrGW. However if the IBCF needs to modify the media attributes for other purposes, in particular due to transcoding then the TrGW is updated in accordance with the received SDP answer, that is, either with the "extended RTP header for CVO" information element containing the received CVO URN if the CVO related "a=extmap" attribute has been included in the received SDP answer or without the "extended RTP header for CVO" information element if the CVO related "a=extmap" attribute has not been included in the received SDP answer (thus removing the requirement for sending the received RTP header extension with CVO bits for the transcoded stream). + +### 10.2.19 Generic image attributes + +#### 10.2.19.1 General + +The IBCF and TrGW may support a media-level SDP image attribute "a=imageattr" defined in IETF RFC 6236 [46] to negotiate the image size for sending and receiving video as required by 3GPP TS 26.114 [36]. + +NOTE 1: The image attribute may be used within the SDP capability negotiation framework and its use is then specified using the "a=acap" parameter. + +If the IBCF: + +- supports the negotiation of the image size; +- receives an SDP body containing the image attribute(s) "imageattr" defined in IETF RFC 6236 [46]; and +- does not offer or does not apply transcoding procedures defined in subclause 10.2.5; + +the IBCF shall forward the SDP body with unmodified image attribute(s). + +If the IBCF applies transcoding procedures defined in subclause 10.2.5 then the following additional actions may be performed if the negotiation of the image size is supported by the IBCF and the TrGW. + +- a) Upon receipt of an SDP offer containing the image attribute(s) from the preceding node (figure 10.2.5.2, step 1) and if the received image sizes are supported by the TrGW: + - 1) if the IBCF seizes an outgoing IP termination with the media related information before sending the SDP offer the IBCF may send the generic image attribute parameter to the TrGW (figure 10.2.5.2, step 3). + - 2) the IBCF shall include the SDP image attribute(s) "a=imageattr" indicating the supported image sizes in the modified SDP offer (figure 10.2.5.2, step 6). +- b) Upon receipt of an SDP answer from the succeeding node (figure 10.2.5.2, step 8) and if the returned SDP answer: + - 1) does not contain the image attribute(s) and contains media offered by the preceding node (i.e. no transcoding at the TrGW is required) then the IBCF shall send to the preceding node the SDP answer without image attribute; + - 2) does not contain the image attribute(s) and if the IBCF is an endpoint for the video stream (transcoding) then the IBCF: + - may send the generic image attribute parameter to the TrGW when seizing or modifying resources (figure 10.2.5.2, step 12); and + - shall include the SDP image attribute(s) "a=imageattr" indicating the supported image sizes in the modified SDP answer (figure 10.2.5.2, step 15); + - 3) contains the image attribute(s) and the media offered by the preceding node (i.e. no transcoding at the TrGW is required) then the IBCF shall send to the preceding node the SDP answer containing the received image attribute(s); or + +- 4) contains the image attribute(s) and if the IBCF is an endpoint for the video stream (transcoding) and if the received image sizes are supported by the TrGW then the IBCF: + - may send the generic image attribute parameters for the send and receive directions to the TrGW when seizing or modifying resources (figure 10.2.5.2, step 9 and step 12); and + - shall include the SDP image attribute(s) "a=imageattr" indicating the supported image sizes in the modified SDP answer (figure 10.2.5.2, step 15) + +NOTE 2: The IBCF not supporting the negotiation of generic image attributes will ignore the SDP image attribute received in the SDP offer and will return the SDP answer without any associated SDP image attribute. + +When sending the SDP body with image attribute(s) on the Mx interface the IBCF shall include in the "a=imageattr": + +- "recv" keyword and corresponding image sizes which the TrGW supports in the receiving direction; and +- "send" keyword and corresponding image sizes which the TrGW supports in the sending direction. + +If the TrGW is configured with different image sizes on the receive direction of one termination and the send direction of another interconnected termination, then it shall adjust the frame sizes accordingly when forwarding video media streams and use the image size as described in 3GPP TS 26.114 [36] when sending media. + +NOTE 3: The relation between the negotiated image sizes and CVO are specified in 3GPP TS 26.114 [36]. + +NOTE 4: The generic image attribute includes information related to the send and receive capabilities of a single termination, and the adjustment of image sizes is typically based on the setting of two connected terminations in a single context. + +#### 10.2.19.2 Indication of generic image attributes + +The IBCF may include the generic image attributes to the TrGW. The example sequence is shown in figure 10.2.19.2.1. + +The list of image sizes per payload type supported by the TrGW shall be preconfigured in the IBCF. If the image sizes received within an SDP body on the Mx interface are not all supported by the TrGW then the IBCF shall only send the list of corresponding TrGW supported image sizes to the TrGW. If no image size is supported by the TrGW, the IBCF shall not send the generic image attribute parameter to the TrGW. + + + +``` + +sequenceDiagram + participant External + participant IBCF + participant TrGW + Note right of IBCF: NOTE + External->>IBCF: SIP msg with SDP offer1 ["imageattr: ..."] + IBCF->>TrGW: SIP msg with SDP offer2 ["imageattr: ..."] + TrGW-->>IBCF: SIP msg with SDP answer2 ["imageattr: ..."] + IBCF->>TrGW: Reserve and Configure TrGW connection point + Note right of TrGW: TrGW receives generic image attribute to be used when transcoding video. + IBCF->>TrGW: H.248: ADD Req [C=?, T=?, Laddr = ?, Lport = ?, Local Resources, Generic Image Attribute] + TrGW-->>IBCF: H.248: ADD Resp [Termination X ...] + IBCF->>External: SIP msg with SDP answer1 ["imageattr: ..."] + +``` + +Sequence diagram showing the request to reserve TrGW connection point with generic image attribute. The diagram involves two main entities: IBCF and TrGW. The sequence starts with an external SIP msg with SDP offer1 (containing 'imageattr: ...') sent to the IBCF. The IBCF then sends an internal SIP msg with SDP offer2 (containing 'imageattr: ...') to the TrGW. The TrGW responds with a SIP msg with SDP answer2 (containing 'imageattr: ...'). A NOTE is present between the SIP messages. The IBCF then sends a 'Reserve and Configure TrGW connection point' message to the TrGW. The TrGW receives a generic image attribute for transcoding video. Finally, the IBCF sends an H.248: ADD Req (with various parameters like C=?, T=?, Laddr = ?, Lport = ?, Local Resources, Generic Image Attribute) to the TrGW, and the TrGW responds with an H.248: ADD Resp (Termination X ...). The IBCF then sends a SIP msg with SDP answer1 (containing 'imageattr: ...') back to the external source. + +NOTE: shown sequence applies to the creation of the incoming termination T2 from the figure 10.2.5.2 and when both, the IBCF and the TrGW support the generic image attribute. The outgoing termination T1 may be created in advance (i.e. before sending SDP offer2) as shown in the figure 10.2.5.2 or upon receipt of the SDP answer2. Even if the IBCF reserves the resources in advance the media information may be omitted at this stage (as described in subclause 10.2.5) and thus the generic image attribute will not be sent to the TrGW if the media information is omitted. + +**Figure 10.2.19.2.1: Request to reserve TrGW connection point with generic image attribute** + +### 10.2.20 Interactive Connectivity Establishment (ICE) + +The IBCF and the TrGW may support ICE functionality as specified in IETF RFC 5245 [50] and 3GPP TS 24.229 [1] to support a UE residing behind a remote NAT. + +Support of full ICE functionality is optional, but if ICE is supported, the IBCF and the TrGW shall at least support ICE lite as specified in IETF RFC 5245 [50]. + +The requirements for the IMS-ALG and the IMS-AGW as specified in subclause 5.17 of 3GPP TS 23.334 [43], apply to the IBCF and the TrGW when the ICE procedures are supported. + +### 10.2.21 MSRP handling + +The IBCF and TrGW may support the handling of the Message Session Relay Protocol (MSRP), IETF RFC 4975 [47]. If they support MSRP handling, they shall apply the procedures as specified in the subclause 5.19 and subclause 6.2.19 of 3GPP TS 23.334 [43]. + +### 10.2.22 Alternative connection (ALTC) addresses management + +An IBCF may support the ALTC functionality as specified in IETF RFC 6947 [51] and 3GPP TS 24.229 [1] to advertise alternative IP addresses (IPv4 and IPv6 address types) to the terminating side. + +The requirements for the IMS-ALG as specified in subclause 5.21 of 3GPP TS 23.334 [43], apply to the IBCF when the procedures related to ALTC are supported. + +The ALTC procedures as described specified in subclause 6.2.20 of 3GPP TS 23.334 [43] are then applicable, except that where the Iq interface is mentioned in those procedures, the Ix interface is applicable. + +### 10.2.23 Video Region-of-Interest (ROI) + +#### 10.2.23.1 General + +The IBCF and the TrGW may support the video Region-of-Interest (ROI) as defined in 3GPP TS 26.114 [36]. Three modes are specified for supporting ROI, including "Far End Camera Control (FECC)", "Arbitrary ROI" and "Pre-defined ROI". The IBCF and the TrGW may independently support any of these modes. + +#### 10.2.23.2 "Far End Camera Control" mode + +##### 10.2.23.2.1 General + +The procedures in subclause 5.22.2 of 3GPP TS 23.334 [43] are applicable. + +##### 10.2.23.2.2 Message sequence chart + +Figure 10.2.23.2.2.1 shows the message sequence chart example for indicating Video Region-of-Interest (ROI) using FECC. + + + +``` + +sequenceDiagram + participant External + participant IBCF + participant TrGW + + Note left of IBCF: INVITE with SDP offer +["m=application port RTP/AVP x" +"a=rtpmap:x h224/4800" +"a=sendrecv"] + External->>IBCF: INVITE with SDP offer + IBCF->>TrGW: H.248:ADD.req[C=?, T= ?, Laddr = ?, Lport = ?, Local Resources] + Note right of TrGW: Reserve TrGW Connection Point + TrGW-->>IBCF: H.248:ADD.resp[Termination T2...] + Note right of IBCF: INVITE with SDP offer +["m=application port RTP/AVP x" +"a=rtpmap:x h224/4800" "a=sendrecv"] + IBCF->>TrGW: INVITE with SDP offer + Note right of TrGW: SDP answer +["m=application port RTP/AVP x" +"a=rtpmap:x h224/4800" "a=sendrecv"] + TrGW-->>IBCF: SDP answer + Note right of IBCF: H.248:ADD.req[C=C, T= ?, Laddr = ?, Lport = ?] + IBCF->>TrGW: H.248:ADD.req + Note right of TrGW: Reserve and Configure TrGW Connection Point + TrGW-->>IBCF: H.248:ADD.resp[Termination T1...] + Note left of IBCF: SDP answer +["m=application port RTP/AVP x" +"a=rtpmap:x h224/4800" +"a=sendrecv"] + IBCF-->>External: SDP answer + +``` + +The sequence diagram illustrates the interaction between an IBCF and a TrGW to indicate Video ROI using FECC. The process begins with an external INVITE with SDP offer to the IBCF. The IBCF sends an H.248:ADD.req to the TrGW, which reserves a connection point and responds. The IBCF then sends another INVITE with SDP offer to the TrGW, which provides an SDP answer. Finally, the IBCF sends a second H.248:ADD.req to the TrGW, which reserves and configures the connection point and responds. The IBCF then sends the final SDP answer back to the external entity. + +Sequence diagram showing the procedure to indicate Video ROI using FECC between an IBCF and a TrGW. + +Figure 10.2.23.2.2.1: Procedure to indicate Video ROI using FECC + +#### 10.2.23.3 "Predefined ROI" mode + +##### 10.2.23.3.1 General + +The procedures in subclause 5.22.3 of 3GPP TS 23.334 [43] are applicable. + +##### 10.2.23.3.2 Message sequence chart + +Figure 10.2.23.3.2.1 shows the message sequence chart example for indicating Predefined ROI mode. + + + +``` + +sequenceDiagram + participant IBCF + participant TrGW + Note left of IBCF: INVITE with SDP offer +["a=rtcp-fb: 3gpp-roi-predefined" +"a=extmap: URN=Predefined +ROI" "a=predefined_ROI"] + IBCF->>TrGW: H.248:ADD.req[C=?, T= ?, Laddr = ?, Lport = ?, +Local Resources, RTCP Feedback(Predefined +ROI), Extended RTP header(Predefined ROI)] + Note right of TrGW: Reserve TrGW +Connection Point + TrGW-->>IBCF: H.248:ADD.resp[Termination T2...] + Note left of IBCF: INVITE with SDP offer +["a=rtcp-fb:3gpp-roi-predefined" "a=extmap: +URN=Predefined ROI" "a=predefined_ROI"] + IBCF->>TrGW: SDP answer +["a=rtcp-fb:3gpp-roi-predefined" "a=extmap: +URN=Predefined ROI" "a=predefined_ROI"] + Note right of TrGW: Reserve and +Configure TrGW +Connection Point + TrGW-->>IBCF: H.248:ADD.resp[Termination T1...] + Note left of IBCF: SDP answer +["a=rtcp-fb:3gpp-roi- +predefined" "a=extmap: +URN=Predefined ROI" +"a=predefined_ROI"] + +``` + +The sequence diagram illustrates the interaction between an IBCF (Initiation Border Control Function) and a TrGW (Traffic Gateway) for Predefined ROI mode. The process starts with an external INVITE with SDP offer to the IBCF. The IBCF sends an H.248:ADD.req message to the TrGW, which reserves a connection point. The TrGW responds with H.248:ADD.resp. The IBCF then sends another INVITE with SDP offer to the TrGW, which reserves and configures the connection point. The TrGW responds with H.248:ADD.resp. Finally, the IBCF sends an SDP answer back to the external caller. + +Sequence diagram for Predefined ROI mode between IBCF and TrGW. + +**Figure 10.2.23.3.2.1: Procedure to indicate Predefined ROI mode** + +According to this procedure, the IBCF shall send to the TrGW the information element on the RTCP feedback message capability for "Predefined ROI" type expressed by the parameter "3gpp-roi-predefined" as described in 3GPP TS 26.114 [36], and the RTP Header Extension capability for carriage of predefined ROI information as defined in IETF RFC 5285 [45] and 3GPP TS 26.114 [36]. In addition, the IBCF shall send to the TrGW the media-level SDP predefined ROI attribute "a=predefined\_ROI" defined in 3GPP TS 26.114 [36]. + +#### 10.2.23.4 "Arbitrary ROI" mode + +##### 10.2.23.4.1 General + +The procedures in subclause 5.22.4 of 3GPP TS 23.334 [43] are applicable. + +##### 10.2.23.4.2 Message sequence chart + +Figure 10.2.23.4.2.1 shows the message sequence chart example for indicating Arbitrary ROI mode. + + + +``` + +sequenceDiagram + participant IBCF + participant TrGW + Note left of IBCF: INVITE with SDP offer +["a=rtcp-fb: 3gpp-roi-arbitrary" +"a=extmap: URN=Arbitrary +ROI"] + IBCF->>TrGW: H.248:ADD.req[C=?, T= ?, Laddr = ?, Lport = ?, +Local Resources, RTCP Feedback(Arbitrary ROI), +Extended RTP header(Arbitrary ROI)] + Note right of TrGW: Reserve TrGW +Connection Point + TrGW-->>IBCF: H.248:ADD.resp[Termination T2...] + Note left of IBCF: INVITE with SDP offer +["a=rtcp-fb: 3gpp-roi-arbitrary" +"a=extmap: URN=Arbitrary ROI"] + IBCF->>TrGW: SDP answer +["a=rtcp-fb: 3gpp-roi-arbitrary" +"a=extmap: URN=Arbitrary ROI"] + Note right of TrGW: Reserve and +Configure TrGW +Connection Point + TrGW-->>IBCF: H.248:ADD.req[C=C, T= ?, Laddr = ?, Lport = ?, +Local Resources, RTCP Feedback(Arbitrary ROI), +Extended RTP header(Arbitrary ROI)] + TrGW-->>IBCF: H.248:ADD.resp[Termination T1...] + Note left of IBCF: SDP answer +["a=rtcp-fb: 3gpp-roi-arbitrary" +"a=extmap: URN=Arbitrary +ROI"] + IBCF-->>TrGW: + +``` + +The diagram illustrates the interaction between an IBCF (Initiation Border Control Function) and a TrGW (Traffic Gateway) to indicate Arbitrary ROI mode. The sequence starts with an INVITE with SDP offer from an external source to the IBCF. The IBCF then sends an H.248:ADD.req message to the TrGW, which reserves a connection point. The TrGW responds with H.248:ADD.resp. The IBCF then sends another INVITE with SDP offer to the TrGW, which reserves and configures the connection point. The TrGW responds with H.248:ADD.req, and the IBCF sends an SDP answer back to the external source. + +Sequence diagram showing the procedure to indicate Arbitrary ROI mode between IBCF and TrGW. + +**Figure 10.2.23.4.2.1: Procedure to indicate Arbitrary ROI mode** + +According to this procedure, the IBCF shall send to the TrGW the information element on the RTCP feedback message capability for "Arbitrary ROI" type expressed by the parameter "3gpp-roi-arbitrary" as described in 3GPP TS 26.114 [36], and the RTP Header Extension capability for carriage of arbitrary ROI information as defined in IETF RFC 5285 [45] and 3GPP TS 26.114 [36]. + +### 10.2.24 SDP Capability Negotiation (SDPCapNeg) + +#### 10.2.24.1 General + +The SDP Capability Negotiation (SDPCapNeg) as specified in IETF RFC 5939 [57] is adopted as an optional functionality to negotiate capabilities and the associated configurations according to 3GPP TS 24.229 [1]. + +Upon receipt of an incoming SDP offer containing the attributes of SDP capability negotiation, e.g. offer AVPF and AVP together for the RTP profile negotiation using the "a=tcap", "a=pcfg" and "a=acfg" attributes, the IBCF shall: + +- request the TrGW to reserve resources only for the default configuration without SDPCapNeg, and make the decision on support of the alternative configurations based on the IBCF/TrGW capability as provisioned before forwarding the SDP offer, i.e. handling SDPCapNeg at the controller level; or +- request the TrGW to reserve resources for all of these configurations by signalling SDPCapNeg to the TrGW, and update the SDP offer based on the response from the TrGW before forwarding. + +NOTE: The additional benefit of signalling SDPCapNeg between the IBCF and the TrGW is to check the resource availability for the corresponding configurations and to avoid the further session failure in case of inadequate resources for the configuration changes in the final confirmation. However, due to the extra resources reserved only during the call establishment phase, there is increased risk of call establishment failures. + +In case the IBCF decides to request the TrGW to reserve resources for all of those configurations, the IBCF shall: + +- use legacy SDP attributes as specified in IETF RFC 4566 [53] to do the mapping of actual and potential configurations with the H.248 ReserveGroup concept; or +- use SDP extensions for SDP capability negotiation as specified in IETF RFC 5939 [57], if supported by the TrGW. + +Before using SDP extensions for SDP capability negotiation as specified in IETF RFC 5939 [57] towards the TrGW, the IBCF shall perform the necessary checks (i.e. through auditing or via prior provisioning) to ensure that the TrGW supports the syntax and capabilities requested. For an auditing the procedure in subclause 6.1.8.1 is used with the "SDPCapNeg Supported Capabilities" as the object. + +When receiving a request from the IBCF with information element "SDPCapNeg configuration" indicating the potential use of multiple configurations, the TrGW shall reserve resources for all of those configurations that it supports and shall send indicate the configurations for which it reserved resources in an "SDPCapNeg configuration" information element in the response. The IBCF shall update the SDP offer with SDPCapNeg configurations in the response from the TrGW and shall forward the SDP offer to the next hop. + +The IBCF may also provide SDP configurations to the TrGW with no dependency on the incoming SDP offer, e.g. the IBCF may wildcard the supported configurations in order to construct or update an SDP offer with the addition of alternative configurations via SDPCapNeg attributes. + +On receipt of an SDP answer with SDPCapNeg, the IBCF shall request the TrGW to configure the resources for the selected configuration. If the TrGW previously reserved any temporary resources for configurations that were not selected, the IBCF shall also request the TrGW to release those resources. + +#### 10.2.24.2 Message sequence chart + +##### 10.2.24.2.1 Audit SDPCapNeg Supported Capabilities + +The IBCF may request the TrGW to report the current values assigned to distinct objects, here as the "SDPCapNeg Supported Capabilities" in the TrGW. This procedure may be used when the IBCF is unsure of the applicability for SDPCapNeg of the TrGW. + +Figure 10.2.24.2.1.1 shows the message sequence chart example for the auditing. + + + +``` +sequenceDiagram + participant IBCF + participant TrGW + Note left of IBCF: IBCF + Note right of TrGW: TrGW + IBCF->>TrGW: Audit Value (Object(s)) + TrGW-->>IBCF: Audit Value Ack (values per requested object) +``` + +Sequence diagram showing the Audit Value of the TrGW. The IBCF sends an 'Audit Value (Object(s))' message to the TrGW, and the TrGW responds with an 'Audit Value Ack (values per requested object)' message. + +Figure 10.2.24.2.1.1: Audit Value of the TrGW + +### 10.2.25 WebRTC Media Plane Optimization + +#### 10.2.25.1 General + +The IBCF and the TrGW may support the WebRTC media plane optimization as defined in 3GPP TS 23.228 [8], annex U.2.4, and 3GPP TS 24.229 [1], subclause 6.7.1.5. + +The purpose of WebRTC media plane optimization procedures is to convey media between WebRTC clients without bearer level protocol conversion. When both ends are WebRTC IMS clients (WIC), the TrGW remain allocated but media plane interworking is disabled. + +The SDP attributes associated with WebRTC media plane optimization procedures "tra-contact", "tra-m-line", "tra-att", "tra-SCTP-association", "tra-media-line-number" and "tra-bw" are defined in 3GPP TS 24.229 [1], subclause 7.5.4. + +#### 10.2.25.2 SDP offer handling + +If the IBCF receives an SDP offer that contains any "tra-contact" SDP attribute, and the IBCF decides to include a TrGW in the media path, the IBCF shall: + +- 1) reserve resources at the TrGW that are suitable for the media described in the SDP offer outside the "tra-m-line", "tra-att" and "tra-bw" SDP attributes. +- 2) include the address information as received from the TrGW in that contact line and also encapsulate the address information into each received "tra-contact" attribute, replacing previous information; and +- 3) transparently pass (in the forwarded SDP offer) all received "tra-m-line", "tra-att", "tra-SCTP-association", "tra-media-line-number" and "tra-bw" SDP attributes. + +#### 10.2.25.3 SDP answer handling + +If the IBCF receives an SDP answer and the SDP answer includes "tra-m-line" media level SDP attributes, the IBCF shall: + +- 1) configure the TrGW to transparently pass the media described in the received "tra-m-line", "tra-att", "tra-SCTP-association", and "tra-bw" SDP attributes; and +- 2) transparently pass all received "tra-m-line", "tra-att", "tra-SCTP-association" and "tra-bw" SDP attributes. + +NOTE: If interconnected H.248 Stream endpoints or terminations at the TrGW are configured with transport "UDP", they will pass the payload within UDP without modifications, known as UDP transparent forwarding. For WebRTC media plane optimization, the UDP payload will be either DTLS encapsulating SCTP and data channel(s), DTLS-SRTP encapsulating key management information, or SRTP encapsulating audio or video media. + +### 10.2.26 RTP-level pause and resume + +The IBCF and the TrGW may support the "RTP-level pause and resume" signalling as defined in 3GPP TS 26.114 [36] and IETF RFC 7728 [59]. + +If the IBCF and the TrGW support the "RTP-level pause and resume" signalling, they shall apply the requirements and procedures specified in 3GPP TS 23.334 [43] subclause 5.2.4 and subclause 6.2.23. + +### 10.2.27 RTCP Codec Control Commands and Indications + +The IBCF and the TrGW may support signalling of "RTCP Codec Control Commands and Indications", as defined in 3GPP TS 26.114 [36] and IETF RFC 5104 [60]. + +NOTE 1: 3GPP TS 26.114 [36] specifies support of the following RTCP feedback codec control messages (CCM): "Full Intra Request (FIR)", "Temporary Maximum Media Stream Bit Rate Request (TMMBR)" and "Temporary Maximum Media Stream Bit Rate Notification (TMMBN)". + +The RTCP feedback FIR message can be used both by point-to-point video calls, and by conference participants supporting Multi-stream Multiparty Conferencing Media Handling feature, as specified in 3GPP TS 26.114 [36] annex S, to request the media sender to send a decoder refresh point. + +The RTCP TMMBR and TMMBN feedback messages can also be used in reaction to the Explicit Congestion Notification, as specified in subclause 10.2.13. + +Usage of the RTCP feedback "CCM" messages is negotiated via SDP offer/answer exchange through an extension (defined in IETF RFC 5104 [60]) of the RTCP feedback capability attribute "a=rtcp-fb" (defined in IETF RFC 4585 [61]). + +NOTE 2: The SDP offer/answer negotiation is performed with a separate "a=rtcp-fb" attribute line for each CCM message type. + +If the IBCF and the TrGW support the "RTCP Codec Control Commands and Indications" signalling, they shall apply the requirements and procedures specified in 3GPP TS 23.334 [43] subclause 5.25 and subclause 6.2.24. + +### 10.2.28 Delay Budget Information (DBI) + +The IBCF and the TrGW may support the "DBI" signalling as defined in 3GPP TS 26.114 [36]. + +RTCP feedback messages to report or request additional delay budget for voice and video media streams (as defined in 3GPP TS 26.114 [36] subclause 7.3.8) can be used both by participants in a point-to-point MTSI session, and by conference participants. + +Usage of the RTCP feedback messages for "DBI" signalling is negotiated via SDP offer/answer exchange through an extension defined in 3GPP TS 26.114 [36] of the RTCP feedback capability attribute "a=rtcp-fb" as defined in IETF RFC 4585 [61]. + +If the IBCF and the TrGW support the "DBI" signalling, they shall apply the requirements and procedures specified in 3GPP TS 23.334 [43] subclause 5.26 and subclause 6.2.25. + +## 10.3 Void + +## 10.4 Procedures + +### 10.4.1 Call related Procedures + +#### 10.4.1.1 Reserve TrGW Connection Point + +This procedure is used to reserve an termination at the TrGW. + +###### **Table 10.4.1.1.1: Reserve TrGW Connection Point Procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------|-----------|----------------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserve TrGW Connection Point | IBCF | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Emergency Call Indicator | O | This information element identifies the call as emergency call that requires a preferential handling. | +| | | Priority information | O | This information element requests the TrGW to apply priority treatment for the terminations and bearer connections in the specified context. | +| | | Termination Request | M | This information element requests a new termination for the bearer to be established. | +| | | IP Interface | O | This information element specifies the type of external interface to be used for the IP termination (e.g. MbolfP). | +| | | Local IP Resources | O | This information element indicates the resource(s) (e.g. codec, auxiliary payload types) for which the TrGW shall be prepared to receive user data. May be excluded (i.e. "-" is used in SDP m-line) if no transcoding or other media related functions are required. | +| | | ReserveValue | C | This information element indicates if multiple local resources are to be reserved.
This information element shall be included if a speech codec and auxiliary payload types are configured. | +| | | Local Connection Address Request | M | This information element requests an IP address and port number on the TrGW that the remote end can send user plane data to. | +| | | Remote Source Address Filtering | O | This information element indicates that remote source address filtering is required. | +| | | Remote Source Address Mask | C | This information element provides information on the valid remote source addresses. This may be included if remote source address filtering is included. It shall not be included if remote source address filtering is not included. | +| | | Remote Source Port Filtering | O | This information element indicates that remote source port filtering is required. | +| | | Remote Source Port | C | This information element identifies the valid remote source port. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| | | Remote Source Port Range | C | This information element identifies a range of valid remote source ports. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| | | RTCP handling | O | Indicates whether or not the TrGW shall reserve a port for an RTCP flow. | +| | | Notify termination heartbeat | M | This information element requests termination heartbeat indications. | +| | | Notify Released Bearer | O | This information element requests a notification of a released bearer. | + +| | | | | +|--|-------------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | DiffServ Code Point | O | This information element indicates a specific DiffServ code point to be used in the IP header in packets sent on the IP termination. | +| | DiffServ Tagging Behaviour | O | This information element indicates whether the Diffserv code point in the IP header in packets sent on the IP termination should be copied from the received value or set to a specific value. | +| | IP Realm Identifier | O | This information element indicates the IP realm of the IP termination. | +| | Traffic Policing Required | O | This information element indicates that policing of the media flow is required. | +| | Peak Data Rate | O | This information element may be present if Policing is required and specifies the permissible peak data rate for a media stream. (NOTE 2) | +| | Sustainable Data Rate | O | This information element may be present if Policing is required and specifies the permissible sustainable data rate for a media stream. (NOTE 2) | +| | Delay Variation Tolerance | O | This information element may be present if Policing on Peak Data Rate is required and specifies the maximum expected delay variation tolerance for the corresponding media stream. | +| | Maximum Burst Size | C | This information element shall be present if Policing on Sustainable Data Rate is required and specifies the maximum expected burst size for the corresponding media stream. | +| | Media Inactivity Detection Required | O | This information element indicates that detection of inactive media flows is required. | +| | Inactivity Detection Time | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection time. | +| | Inactivity Detection Direction | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection direction. | +| | ECN Enable | O | This information element requests the TrGW to apply ECN procedures | +| | ECN Initiation Method | C | This information element specifies the ECN Initiation method and requests the TrGW to perform IP header settings as an ECN endpoint, or indicates that ECN bits shall be passed transparently. It may be included only if ECN is enabled. | +| | Congestion Response Method | C | This information element specifies the ECN Congestion Response Method; receiver driven or sender driven. The default is "received driven congestion control". It may be included only if ECN is enabled and the TrGW acts as ECN endpoint. (NOTE 3) | +| | ECN ECT Marking | C | This information element specifies the ECN ECT Marking. It may be included only if ECN is enabled and the TrGW acts as ECN endpoint. (NOTE 3) | +| | ECN Mode | C | This information element specifies the ECN Mode. It may be included only if ECN is enabled and the TrGW acts as ECN endpoint. (NOTE 3) | +| | RTCP Feedback | C | This information element specifies the RTCP Feedback support. (NOTE 3) | + +| | | | | | +|-----------------------------------|------|---------------------------------------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | XR Summary Report | C | This information element specifies the support of XR Summary Reporting. | +| | | Notify ECN Failure Event | C | This information element requests a notification if a ECN failure occurs. It may only be supplied if ECN is enabled and the TrGW acts as ECN endpoint. | +| | | Extended RTP Header for CVO | O | This information element requests the TrGW to pass on the CVO extended RTP header as defined by IETF RFC 5285 [45]. | +| | | Generic Image Attributes | O | This information element indicates image attributes (e.g. image size) as defined by IETF RFC 6236 [46]. | +| | | ICE password request | O | This information element is present if IBCF requests an ICE password. | +| | | ICE Ufrag request | O | This information element is present if IBCF requests an ICE ufrag. | +| | | ICE host candidate request | O | This information element is present if IBCF requests an ICE host candidate. | +| | | STUN server request | O | This information element is present if IBCF requests the TrGW to answer STUN connectivity checks for ICE. | +| | | Application-aware MSRP interworking request | O | This information element is present if IBCF requests the TrGW to perform application-aware MSRP Interworking. | +| | | Extended RTP Header for Sent ROI | O | This information element requests the TrGW to pass on the ROI extended RTP header for carriage of predefined and/or arbitrary ROI information as defined by IETF RFC 5285 [45] and 3GPP TS 26.114 [36]. | +| | | Predefined ROI | O | This information element requests the TrGW to support the RTCP feedback message capability for "Predefined ROI" type expressed by the parameter "3gpp-roi-predefined", as described in 3GPP TS 26.114 [36]. | +| | | Arbitrary ROI | O | This information element requests the TrGW to support the RTCP feedback message capability for "Arbitrary ROI" type expressed by the parameter "3gpp-roi-arbitrary", as described in 3GPP TS 26.114 [36]. | +| | | SDPCapNeg configuration | O | This information element provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. | +| Reserve TrGW Connection Point Ack | TrGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | +| | | Local IP Resources | C | This information element indicates the resources that the TrGW has reserved to receive the user plane data from the remote peer. This information element shall be present if it was contained in the request. If the information element was not contained in the request, it may be present in the reply. | +| | | Local Connection Address | M | This information element indicates the IP address and port on the TrGW that shall receive user plane data from the remote peer. | + +| | | | | | +|-----------------------------------------------------------------------------------------------|--|-------------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | ICE password | C | This information element shall be present only if it was contained in the request. It indicates the ICE password assigned by the TrGW. | +| | | ICE Ufrag | C | This information element shall be present only if it was contained in the request. It indicates the ICE Ufrag assigned by the TrGW. | +| | | ICE host candidate | C | This information element shall be present only if it was contained in the request. It indicates the ICE host candidate assigned by the TrGW. | +| | | ICE lite indication | C | This information element shall be present only if an ICE host candidate request was contained in the request, and the IBCF supports ICE lite, but not full ICE. It indicates that the TrGW only supports ICE lite. | +| | | SDPCapNeg configuration | C | This information element shall be present only if it was contained in the request. It provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. | +| NOTE 1: Remote Source Port and Remote Source Port Range are mutually exclusive. | | | | | +| NOTE 2: At least one of these information elementshall be present when policing is required. | | | | | +| NOTE 3: This parameter does not need to be signalled if support is for 3GPP defined ECN only. | | | | | + +#### 10.4.1.2 Configure TrGW Connection Point + +This procedure is used to configure or reconfigure an termination at the TrGW. + +###### **Table 10.4.1.2.1: Configure TrGW Connection Point Procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------------|-----------|---------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Configure TrGW Connection Point | IBCF | Context | M | This information element indicates the existing context. | +| | | Priority information | O | This information element shall be present if the priority information needs to be modified, it may be present otherwise. | +| | | Termination | M | This information element indicates the existing bearer termination. | +| | | IP Interface | O | This information element specifies the type of external interface to be used for the IP termination (e.g. MboIP). | +| | | Local IP Resources | O | This information element indicates the resources (e.g. codec, auxiliary payload types) that the TrGW may use on the reception of user plane data.
If Local Connection Address is supplied may be excluded (i.e. "-" is used in SDP m-line) if no transcoding or other media related functions are required. | +| | | Remote IP Resources | O | This information element indicates the resources (e.g. codec, auxiliary payload types) that the TrGW may send user plane data to.
If Remote Connection Address is supplied may be excluded (i.e. "-" is used in SDP m-line) if no transcoding or other media related functions are required. | +| | | Local Connection Address | O | This information element indicates the IP address and port on the TrGW that the remote peer can send user plane data to. | +| | | Remote Connection Address | O | This information element indicates the IP address and port that the TrGW can send user plane data to. | +| | | Reserve Value | C | This information element indicates if multiple resources are to be reserved. This information element shall be included if a speech codec and auxiliary payload types are configured. | +| | | Remote Source Address Filtering | O | This information element indicates that remote source address filtering is required. | +| | | Remote Source Address Mask | C | This information element provides information on the valid remote source addresses. This may be included if remote source address filtering is included. It shall not be included if remote source address filtering is not included. | +| | | Remote Source Port Filtering | O | This information element indicates that remote source port filtering is required. | +| | | Remote Source Port | C | This information element identifies the valid remote source port. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| | | Remote Source Port Range | C | This information element identifies a range of valid remote source ports. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| | | RTCP handling | O | Indicates whether or not the TrGW shall reserve a port for an RTCP flow | + +| | | | +|-------------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Traffic Policing Required | O | This information element indicates that policing of the media flow is required. | +| Peak Data Rate | O | This information element may be present if Policing is required and specifies the permissible peak data rate for a media stream. (NOTE 2) | +| Sustainable Data Rate | O | This information element may be present if Policing is required and specifies the permissible sustainable data rate for a media stream. (NOTE 2) | +| Delay Variation Tolerance | O | This information element may be present if Policing on Peak Data Rate is required and specifies the maximum expected delay variation tolerance for the corresponding media stream. | +| Maximum Burst Size | C | This information element shall be present if Policing on Sustainable Data Rate is required and specifies the maximum expected burst size for the corresponding media stream. | +| DiffServ Code Point | O | This information element indicates a specific DiffServ code point to be used in the IP header in packets sent on the IP termination. | +| DiffServ Tagging Behaviour | O | This information element indicates whether the Diffserv code point in the IP header in packets sent on the IP termination should be copied from the received value or set to a specific value. | +| Media Inactivity Detection Required | O | This information element indicates that detection of inactive media flows is required. | +| Inactivity Detection Time | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection time. | +| Inactivity Detection Direction | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection direction. | +| ECN Enable | O | This information element requests the TrGW to apply ECN procedures. | +| ECN Initiation Method | C | This information element specifies the ECN Initiation method and requests the TrGW to perform IP header settings as an ECN endpoint, or indicates that ECN bits shall be passed transparently. It may be included only if ECN is enabled. | +| Congestion Response Method | C | This information element specifies the ECN Congestion Response Method; receiver driven or sender driven. The default is "received driven congestion control". It may be included only if ECN is enabled and the TrGW acts as ECN endpoint. (NOTE 3) | +| ECN ECT Marking | C | This information element specifies the ECN ECT Marking. It may be included only if ECN is enabled and the TrGW acts as ECN endpoint. (NOTE 3) | +| ECN Mode | C | This information element specifies the ECN Mode. It may be included only if ECN is enabled and the TrGW acts as ECN endpoint. (NOTE 3) | +| RTCP Feedback | C | This information element specifies the RTCP Feedback support. (NOTE 3) | +| XR Summary Report | C | This information element specifies the support of XR Summary Reporting. | + +| | | | | +|--|--------------------------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Notify ECN Failure Event | C | This information element requests a notification if a ECN failure occurs. It may only be supplied if ECN is enabled and the TrGW acts as ECN endpoint. | +| | Extended RTP Header for CVO | O | This information element requests the TrGW to pass on the CVO extended RTP header as defined by IETF RFC 5285 [45]. | +| | Generic Image Attributes | O | This information element indicates image attributes (e.g. image size) as defined by IETF RFC 6236 [46]. | +| | ICE Connectivity Check | C | This information element requests the TrGW to perform ICE connectivity check as defined by IETF RFC 5245 [50]. It is only applicable for full ICE. | +| | Notify ICE Connectivity Check Result | C | This information element requests a notification of ICE connectivity check result. It is only applicable for full ICE. | +| | Notify New Peer Reflexive Candidate | C | This information element requests a notification of new peer reflexive candidate was discovered during a connectivity check. It is only applicable for full ICE. | +| | Additional ICE Connectivity Check | C | This information element requests the TrGW to perform additional ICE connectivity check as defined by IETF RFC 5245 [50]. It is only applicable for full ICE. | +| | ICE received candidate | O | This information element is present if IBCF indicates a received candidate for ICE. | +| | ICE received password | O | This information element is present if IBCF indicates a received password for ICE. | +| | ICE received Ufrag | O | This information element is present if IBCF indicates a received Ufrag for ICE. | +| | MSRP Path | O | This information element is present for application-aware MSRP Interworking. It provides the path information that the TrGW shall insert in the MSRP layer "To-Path" Information element. | +| | Allowed RTCP APP message types | O | This information element is present if the IBCF allows the TrGW to send RTCP APP packets of the indicated types. The TrGW shall not send other RTCP APP packets. If the parameter is not supplied, the TrGW shall not send any RTCP APP packets. | +| | Extended RTP Header for Sent ROI | O | This information element requests the TrGW to pass on the ROI extended RTP header for carriage of predefined and/or arbitrary ROI information as defined by IETF RFC 5285 [45] and 3GPP TS 26.114 [36]. | +| | Predefined ROI | O | This information element requests the TrGW to support the RTCP feedback message capability for "Predefined ROI" type expressed by the parameter "3gpp-roi-predefined", as described in 3GPP TS 26.114 [36]. | +| | Arbitrary ROI | O | This information element requests the TrGW to support the RTCP feedback message capability for "Arbitrary ROI" type expressed by the parameter "3gpp-roi-arbitrary", as described in 3GPP TS 26.114 [36]. | + +| | | | | | +|-------------------------------------|------|---------------------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | SDPCapNeg configuration | O | This information element provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. | +| | | Additional Bandwidth Properties | O | This information element indicates additional bandwidth properties using "a=bw-info" SDP attribute(s) as defined by 3GPP TS 26.114 [36]. | +| | | CCM BASE | O | This information element indicates that the TrGW shall be prepared to receive and is allowed to send, respectively, the RTCP feedback "CCM FIR" and/or "CCM TMMBR" messages (defined in IETF RFC 5104 [60]). | +| | | CCM pause-resume | O | This information element indicates to the TrGW that RTCP feedback "CCM PAUSE-RESUME" messages shall be passed transparently. | +| | | DBI | O | This information element indicates to the TrGW that RTCP feedback messages for "DBI" signalling (as defined in 3GPP TS 26.114 [36] subclause 7.3.8) shall be passed transparently. | +| Configure TrGW Connection Point Ack | TrGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | +| | | Local IP Resources | O | This information element indicates the resources that the TrGW has reserved to receive the user plane data from the far end. | +| | | Remote IP Resources | O | This information element indicates the resource (i.e. codec) that the TrGW shall use to send user data to. May be present only if corresponding information element is present in the request. | +| | | Local Connection Address | O | This information element indicates the IP address and port on the TrGW that the remote end can send user plane data to. | +| | | Remote Connection Address | O | This information element indicates the IP address and port that the TrGW can send user plane data to. May be present only if corresponding information element is present in the request. | + +NOTE 1: Remote Source Port and Remote Source Port Range are mutually exclusive. + +NOTE 2: At least one of these information elements shall be present when policing is required. + +NOTE 3: This parameter does not need to be signalled if support is for 3GPP defined ECN only. + +#### 10.4.1.3 Reserve and Configure TrGW Connection Point + +This procedure is used to reserve and configure multimedia-processing resources for a termination at the TrGW. + +###### **Table 10.4.1.3.1: Reserve and Configure TrGW Connection Point Procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------------------------|-----------|----------------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserve and Configure TrGW Connection Point | IBCF | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Emergency Call Indicator | O | This information element identifies the call as emergency call that requires a preferential handling. | +| | | Priority information | O | This information element requests the TrGW to apply priority treatment for the terminations and bearer connections in the specified context. | +| | | Termination/ Termination Request | M | This information element indicates the existing bearer termination or requests a new termination for the bearer to be established. | +| | | IP Interface | O | This information element specifies the used interface type for the IP termination (e.g. MboIP). | +| | | Local IP Resources | C | This information element indicates the resource(s) (e.g. codec, auxiliary payload types) for which the TrGW shall be prepared to receive user data. May be excluded (i.e. "-" is used in SDP m-line) if no transcoding or other media related functions are required. | +| | | Remote IP Resources | C | This information element indicates the resources (e.g. codec, auxiliary payload types) that the TrGW shall use to send user data. May be excluded (i.e. "-" is used in SDP m-line) if no transcoding or other media related functions are required. | +| | | Reserve Value | C | This information element indicates if multiple IP resources are to be reserved. This information element shall be included if a speech codec and auxiliary payload types are configured. | +| | | Local Connection Address request | M | This information element requests an IP address and a port number on the TrGW that the remote end can send user plane data to. | +| | | Remote Connection Address | M | This information element indicates the IP address and ports of the remote party that the TrGW can send user plane data to. | +| | | Remote Source Address Filtering | O | This information element indicates that remote source address filtering is required. | +| | | Remote Source Address Mask | C | This information element provides information on the valid remote source addresses. This may be included if remote source address filtering is included. It shall not be included if remote source address filtering is not included. | +| | | Remote Source Port Filtering | O | This information element indicates that remote source port filtering is required. | +| | | Remote Source Port | C | This information element identifies the valid remote source port. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| | | Remote Source Port Range | C | This information element identifies a range of valid remote source ports. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | + +| | | | | +|--|-------------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | RTCP handling | O | This information element indicates whether or not the TrGW shall reserve a port for an RTCP flow. | +| | Notify termination heartbeat | M | This information element requests termination heartbeat indications. | +| | Notify Released Bearer | O | This information element requests a notification of a released bearer. | +| | IP Realm Identifier | O | This information element indicates the IP realm of the IP termination. | +| | Traffic Policing Required | O | This information element indicates that policing of the media flow is required. | +| | Peak Data Rate | O | This information element may be present if Policing is required and specifies the permissible peak data rate for a media stream. (NOTE 2) | +| | Sustainable Data Rate | O | This information element may be present if Policing is required and specifies the permissible sustainable data rate for a media stream. (NOTE 2) | +| | Delay Variation Tolerance | O | This information element may be present if Policing on Peak Data Rate is required and specifies the maximum expected delay variation tolerance for the corresponding media stream. | +| | Maximum Burst Size | C | This information element shall be present if Policing on Sustainable Data Rate is required and specifies the maximum expected burst size for the corresponding media stream. | +| | DiffServ Code Point | O | This information element indicates a specific DiffServ code point to be used in the IP header in packets sent on the IP termination. | +| | DiffServ Tagging Behaviour | O | This information element indicates whether the Diffserv code point in the IP header in packets sent on the IP termination should be copied from the received value or set to a specific value. | +| | Media Inactivity Detection Required | O | This information element indicates that detection of inactive media flows is required. | +| | Inactivity Detection Time | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection time. | +| | Inactivity Detection Direction | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection direction. | +| | ECN Enable | O | This information element requests the TrGW to apply ECN procedures. | +| | ECN Initiation Method | C | This information element specifies the ECN Initiation method and requests the TrGW to perform IP header settings as an ECN endpoint, or indicates that ECN bits shall be passed transparently. It may be included only if ECN is enabled. | +| | Congestion Response Method | C | This information element specifies the ECN Congestion Response Method; receiver driven or sender driven. The default is "received driven congestion control". It may be included only if ECN is enabled and the TrGW acts as ECN endpoint. (NOTE 3) | +| | ECN ECT Marking | C | This information element specifies the ECN ECT Marking. It may be included only if ECN is enabled and the TrGW acts as ECN endpoint. (NOTE 3) | + +| | | | | | +|--|--|---------------------------------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | ECN Mode | C | This information element specifies the ECN Mode. It may be included only if ECN is enabled and the TrGW acts as ECN endpoint. (NOTE 3) | +| | | RTCP Feedback | C | This information element specifies the RTCP Feedback support. (NOTE 3) | +| | | XR Summary Report | C | This information element specifies the support of XR Summary Reporting. | +| | | Notify ECN FailureEvent | C | This information element requests a notification if a ECN failure occurs due to ECN. It may only be supplied if ECN is enabled and the TrGW acts as ECN endpoint. | +| | | Extended RTP Header for CVO | O | This information element requests the TrGW to pass on the CVO extended RTP header as defined by IETF RFC 5285 [45]. | +| | | Generic Image Attributes | O | This information element indicates image attributes (e.g. image size) as defined by IETF RFC 6236 [46]. | +| | | STUN server request | O | This information element is present if IBCF requests the TrGW to answer STUN connectivity checks for ICE. | +| | | ICE Connectivity Check | C | This information element requests the TrGW to perform ICE connectivity check as defined by IETF RFC 5245 [50]. It is only applicable for full ICE. | +| | | Notify ICE Connectivity Check Result | C | This information element requests a notification of ICE connectivity check result. It is only applicable for full ICE. | +| | | Notify New Peer Reflexive Candidate | C | This information element requests a notification of new peer reflexive candidate was discovered during a connectivity check. It is only applicable for full ICE. | +| | | ICE password request | O | This information element is present if IBCF requests an ICE password. | +| | | ICE Ufrag request | O | This information element is present if IBCF requests an ICE ufrag. | +| | | ICE host candidate request | O | This information element is present if IBCF requests an ICE host candidate. | +| | | ICE received candidate | O | This information element is present if IBCF indicates a received candidate for ICE. | +| | | ICE received password | O | This information element is present if IBCF indicates a received password for ICE. | +| | | ICE received Ufrag | O | This information element is present if IBCF indicates a received Ufrag for ICE. | +| | | MSRP Path | O | This information element is present for application-aware MSRP Interworking. It provides the path information that the TrGW shall insert in the MSRP layer "To-Path" Information element. | +| | | Application-aware MSRP interworking request | O | This information element is present if IBCF requests the TrGW to perform application-aware MSRP Interworking. | +| | | Allowed RTCP APP message types | O | This information element is present if the IBCF allows the TrGW to send RTCP APP packets of the indicated types. The TrGW shall not send other RTCP APP packets. If the parameter is not supplied, the TrGW shall not send any RTCP APP packets. | +| | | Extended RTP Header for Sent ROI | O | This information element requests the TrGW to pass on the ROI extended RTP header for carriage of predefined and/or arbitrary ROI information as defined by IETF RFC 5285 [45] and 3GPP TS 26.114 [36]. | + +| | | | | | +|-------------------------------------------------|------|---------------------------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Predefined ROI | O | This information element requests the TrGW to support the RTCP feedback message capability for "Predefined ROI" type expressed by the parameter "3gpp-roI-predefined", as described in 3GPP TS 26.114 [36]. | +| | | Arbitrary ROI | O | This information element requests the TrGW to support the RTCP feedback message capability for "Arbitrary ROI" type expressed by the parameter "3gpp-roI-arbitrary", as described in 3GPP TS 26.114 [36]. | +| | | SDPCapNeg configuration | O | This information element provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. | +| | | Additional Bandwidth Properties | O | This information element indicates additional bandwidth properties using "a=bw-info" SDP attribute(s) as defined by 3GPP TS 26.114 [36]. | +| | | CCM BASE | O | This information element indicates that the TrGW shall be prepared to receive and is allowed to send, respectively, the RTCP feedback "CCM FIR" and/or "CCM TMMBR" messages (defined in IETF RFC 5104 [60]). | +| | | CCM pause-resume | O | This information element indicates to the TrGW that RTCP feedback "CCM PAUSE-RESUME" messages shall be passed transparently. | +| | | DBI | O | This information element indicates to the TrGW that RTCP feedback messages for "DBI" signalling (as defined in 3GPP TS 26.114 [36] subclause 7.3.8) shall be passed transparently. | +| Reserve and Configure TrGW Connection Point Ack | TrGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | +| | | Local IP Resources | C | This information element indicates the resources that the TrGW has reserved to receive the user plane data from the remote side. This information element shall be present if it was contained in the request. If the information element was not contained in the request, it may be present in the reply. | +| | | Remote IP Resources | O | This information element indicates the resource (i.e. codec) that the TrGW shall use to send user data. | +| | | Local Connection Addresses | M | This information element indicates the IP address and port on the TrGW that shall receive user plane data. | +| | | Remote Connection Address | O | This information element indicates the IP address and port that the TrGW can send user plane data to. | +| | | ICE password | C | This information element shall be present only if it was contained in the request. It indicates the ICE password assigned by the TrGW. | +| | | ICE Ufrag | C | This information element shall be present only if it was contained in the request. It indicates the ICE Ufrag assigned by the TrGW. | +| | | ICE host candidate | C | This information element shall be present only if it was contained in the request. It indicates the ICE host candidate assigned by the TrGW. | + +| | | | | | | +|------------------------------------------------------------------------------------------------|--|-------------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | ICE lite indication | C | This information element shall be present only if an ICE host candidate request was contained in the request, and the TrGW supports ICE lite, but not full ICE. It indicates that the TrGW only supports ICE lite. | | +| | | SDPCapNeg configuration | C | This information element shall be present only if it was contained in the request. It provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. | | +| NOTE 1: Remote Source Port and Remote Source Port Range are mutually exclusive. | | | | | | +| NOTE 2: At least one of these information elements shall be present when policing is required. | | | | | | +| NOTE 3: This parameter does not need to be signalled if support is for 3GPP defined ECN only. | | | | | | + +#### 10.4.1.4 Release TrGW Termination + +This procedure is used to release multimedia-processing resources for a termination at the TrGW. + +**Table 10.4.1.4.1: Release TrGW Termination** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------| +| Release TrGW Termination | IBCF | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the existing bearer termination to be released. | +| Release TrGW Termination Ack | TrGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | + +NOTE: No requirement for statistics in the Release TrGW Termination Ack has been justified by a use case. + +#### 10.4.1.5 IP Bearer Released + +**Table 10.4.1.5.1: IP Bearer Released** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------|-----------|--------------------------|------------------------------|-----------------------------------------------------------------------------------------------| +| IP Bearer Released | TrGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Termination | M | This information element indicates the bearer termination where the bearer was released. | +| | | Bearer Released | M | This information element notifies a bearer release. | +| | | Release Cause | M | This information element indicates the cause of a bearer release. | +| IP Bearer Released Ack | IBCF | Context | M | This information element indicates all context are where the command was executed. | +| | | Termination | M | This information element indicates that Bearer termination is where the command was executed. | + +#### 10.4.1.6 Media Inactivity Detection + +This command is used to notify the IBCF of media inactivity on the TrGW. + +**Table 10.4.1.6.1: Media Inactivity Notification** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------| +| Media Inactivity Notification | TrGW | Context | M | This information element indicates the existing context for the bearer termination. | +| | | Termination | M | This information element indicates that bearer termination is where the media inactivity detection was activated. | +| | | Media Inactivity | M | This information element notifies the IBCF of Media inactivity detection on the bearer termination. | +| Media Inactivity Notification Ack | IBCF | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the bearer termination where the command was executed. | + +#### 10.4.1.7 Termination heartbeat indication + +This command is used by the TrGW to periodically notify the IBCF of a termination heartbeat. + +**Table 10.4.1.7.1: Termination heartbeat indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------------------------------| +| Termination heartbeat indication | TrGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the termination heartbeat is reported. | +| | | Termination heartbeat | M | Hanging Termination event. | +| Termination heartbeat indication Ack | IBCF | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +#### 10.4.1.8 Change Through-Connection + +This procedure is used to change the Through-connection in the bearer termination. + +**Table 10.4.1.8.1: Change Through-Connection** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------|-----------|-----------------------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| Change Through-Connection | IBCF | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Bearer Termination/Bearer Termination Request | M | This information element indicates the existing bearer termination or requests a new Bearer termination where the through connection is changed. | +| | | Through-Connection | M | This information element indicates the through-connection of the bearer termination. | +| Change Through-Connection Ack | TrGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +NOTE: This procedure may be combined with Reserve and Configure TrGW Connection Point, Reserve TrGW Connection Point or Configure TrGW Connection Point procedure. This list of procedures is not exhaustive. + +#### 10.4.1.9 ECN Failure Indication + +This procedure is used to report ECN related failures (see clause 10.2.13.3a). + +**Table 10.4.1.9.1: Procedures toward the IM Subsystem: ECN Failure Indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------|-----------|--------------------------|------------------------------|--------------------------------------------------------------------------------------------------| +| ECN Error Indication | TrGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the ECN failure is reported. | +| | | ECN Error Indication | M | This information element indicates an ECN failure event. | +| ECN Error Indication Ack | IBCF | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +#### 10.4.1.10 Change Flow Direction + +This procedure may be used to change the flow direction between bearer terminations within a context for access transfer procedures (see subclause 10.2.15). + +**Table 10.4.1.10.1: Procedures toward the IM Subsystem: Change Flow Direction** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------|------------|----------------------------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| Change Flow Direction | IBCF(ATCF) | Context/Context Request | M | This information element indicates the existing context or a new context where the flow direction is changed. | +| | | Bearer Termination 1/ Bearer Termination 1 Request | M | This information element indicates the existing bearer termination or a new bearer termination from where the new flow direction is applied. | +| | | Bearer Termination 2/ Bearer Termination 2 Request | M | This information element indicates the existing bearer termination where the new flow direction is applied. | +| | | Flow Direction | M | This information element indicates the flow direction from the bearer termination 1 to bearer termination 2 within the context. | +| Change Flow Direction Ack | TrGW(ATGW) | Context | M | This information element indicates the context where the command was executed. | + +#### 10.4.1.11 ICE Connectivity Check Result Notification + +This procedure is used to report ICE connectivity check result for Full ICE. + +**Table 10.4.1.11.1: Procedures toward the IM Subsystem: ICE Connectivity Check Result Notification** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------------------------------|-----------|------------------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------| +| ICE Connectivity Check Result Notification | TrGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the ICE Connectivity Check Result is reported. | +| | | ICE Connectivity Check Result Indication | M | This information element indicates an ICE Connectivity Check Result event. | +| ICE Connectivity Check Result Notification Ack | IBCF | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +#### 10.4.1.12 ICE New Peer Reflexive Candidate Notification + +This procedure is used to report ICE New Peer Reflexive Candidate for Full ICE. + +**Table 10.4.1.12.1: Procedures toward the IM Subsystem: ICE New Peer Reflexive Candidate Notification** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------------------------------|-----------|---------------------------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------| +| ICE New Peer Reflexive Candidate Notification | TrGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the ICE New Peer Reflexive Candidate is reported. | +| | | ICE New Peer Reflexive Candidate Indication | M | This information element indicates an ICE New Peer Reflexive Candidate event. | +| ICE New Peer Reflexive Candidate Notification Ack | IBCF | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 10.4.2 Non Call related Procedures + +The procedures in table 10.4.2.1 shall be applied between the IBCF and TrGW. + +**Table 10.4.2.1: Non-call related procedures** + +| Stage 3 Procedure (for information) defined in 3GPP TS 29.238 [25] | Corresponding Stage 2 Procedure defined in 3GPP TS 23.205 [28] | Remarks | +|--------------------------------------------------------------------|----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| TrGW Out of service | MGW Out of Service | | +| TrGW Communication Up | MGW Communication Up | | +| TrGW Restoration | MGW Restoration | | +| TrGW Register | MGW Register | | +| TrGW Re-register | MGW Re-register | | +| CS-IBCF Ordered Re-register | (G)MSC Server Ordered Re-register | | +| CS-IBCF Restoration | (G)MSC Server Restoration | | +| CS-IBCF Out of Service | (G)MSC Server Out of Service | | +| Termination Out-of-Service | Termination Out-of-Service | The "Termination Out-of-Service procedure" is also used as a call-related H.248 command | +| Audit Value | Audit Value | The "Audit Value" procedure may be used to determine the support of SDPCapNeg in response to non-call-related H.248 commands. | +| Command Rejected | Command Rejected | The "Command Rejected" procedure may be used in response both to call-related and non-call-related H.248 commands. | +| TrGW Capability Change | Capability Update | | +| TrGW Resource Congestion Handling – Activate | MGW Resource Congestion Handling – Activate | | +| TrGW Resource Congestion Handling – Indication | MGW Resource Congestion Handling – Indication | | +| Inactivity timeout activation | Inactivity timeout activation | | +| Inactivity timeout indication | Inactivity timeout indication | | +| Realm Availability Change Activation | | See 3GPP TS 29.235 [29] subclause A.7.2 | + +| | | | +|--------------------------------------|--|-----------------------------------------| +| Realm Availability Change Indication | | See 3GPP TS 29.235 [29] subclause A.7.2 | +|--------------------------------------|--|-----------------------------------------| + +--- + +Annex A (informative): +Void. + +# Annex B (informative): Change history + +| Change history | | | | | | | | | +|-----------------------|--------------|-----------------|-----------|------------|------------|-----------------------------------------------------------------------------------------------------|------------|------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | Old | New | +| 06-2015 | CT-68 | CP-150351 | 0139 | - | | Bearer Termination in Acknowledgements | 12.6.0 | 12.7.0 | +| 09-2015 | CT-69 | CP-150483 | 0141 | 2 | B | Support for Video Enhancements by Region-of-Interest Information Signalling | 12.7.0 | 13.0.0 | +| 12-2015 | CT-70 | CP-150667 | 0142 | 11 | B | Support of SDP capability negotiation | 13.0.0 | 13.1.0 | +| 12-2015 | CT-70 | CP-150665 | 0144 | 4 | B | Support for Video Enhancements by Region-of-Interest Information Signalling | 13.0.0 | 13.1.0 | +| Change history | | | | | | | | | +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | | +| 03-2016 | CT#71 | CP-160105 | 0149 | - | F | Bandwidth adjustment for EVS codec | 13.2.0 | | +| 03-2016 | CT#71 | CP-160102 | 0150 | 2 | B | Support of enhanced bandwidth negotiation mechanism for MTSI sessions | 13.2.0 | | +| 03-2016 | CT#71 | CP-160105 | 0151 | - | F | Removal of references to TS 26.235 | 13.2.0 | | +| 03-2016 | CT#71 | CP-160097 | 0152 | 4 | B | WebRTC media plane optimization procedure | 13.2.0 | | +| 06-2016 | CT#72 | CP-160269 | 0153 | - | F | Clarifications related to the enhanced bandwidth negotiation mechanism | 13.3.0 | | +| 09-2016 | CT#73 | CP-160451 | 0154 | 3 | B | Clarification of the gate control procedure between SIP and H.248 for early media over Ix interface | 14.0.0 | | +| 12-2016 | CT#74 | CP-160625 | 0155 | 1 | B | Support of RTP-level pause and resume functionality | 14.1.0 | | +| 03-2017 | CT#75 | CP-170082 | 0156 | - | F | Correcting references for "RTP-level pause and resume" signalling | 14.2.0 | | +| 03-2017 | CT#75 | CP-170082 | 0157 | 1 | B | RTCP Codec Control Commands and Indications | 14.2.0 | | +| 09-2018 | CT#81 | | | | | Automatic upgrade to Rel-15 | 15.0.0 | | +| 06-2019 | CT#84 | CP-191107 | 0159 | 3 | B | Update IBCF and TrGW interworking requirements for DBI support | 16.0.0 | | \ No newline at end of file diff --git a/marked/Rel-16/29_series/29163/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/29_series/29163/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..287df08b65d52f9ef64b431831124ee29b2784ef --- /dev/null +++ b/marked/Rel-16/29_series/29163/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a117820fbfa474a2f010a37f1ab9203b972ef6d290c773b462f0a4a8b5c84f6d +size 68146 diff --git a/marked/Rel-16/29_series/29163/01465752f3ac36c403672804f406a676_img.jpg b/marked/Rel-16/29_series/29163/01465752f3ac36c403672804f406a676_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7212599750d6f0d8c2620698963225306c4e4b92 --- /dev/null +++ b/marked/Rel-16/29_series/29163/01465752f3ac36c403672804f406a676_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56f69d7704d5960ce754e610eb5714c3539b32caf6bce00901a2f8e48e1611c6 +size 43311 diff --git a/marked/Rel-16/29_series/29163/02e16c8e8e61c2706b5c0129674884a8_img.jpg b/marked/Rel-16/29_series/29163/02e16c8e8e61c2706b5c0129674884a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fc996e5a4da650fed9b90d2f8daac2333236a63 --- /dev/null +++ b/marked/Rel-16/29_series/29163/02e16c8e8e61c2706b5c0129674884a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5308a96b2aacd8e4c5e7375109a303151a2556a5c749e7724faf52d9161de1e +size 21586 diff --git a/marked/Rel-16/29_series/29163/04dc3838022e96d8d5548bb1b777b38c_img.jpg b/marked/Rel-16/29_series/29163/04dc3838022e96d8d5548bb1b777b38c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25c8fa47291ee71a0f9e14ad5babe53cee88de60 --- /dev/null +++ b/marked/Rel-16/29_series/29163/04dc3838022e96d8d5548bb1b777b38c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c19525bcb871f0d1145f363bd24c25ba460c5f79ca9ef9df81b300a6d19fa2ba +size 46415 diff --git a/marked/Rel-16/29_series/29163/0726a03ffb4e106eb90cd4f9283a6347_img.jpg b/marked/Rel-16/29_series/29163/0726a03ffb4e106eb90cd4f9283a6347_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26e04ab262f9c867bf040479bc4058d4e935b2b1 --- /dev/null +++ b/marked/Rel-16/29_series/29163/0726a03ffb4e106eb90cd4f9283a6347_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be2f99a647ecf78aee322de008a0c5ab8bd7013c6120a975fdb3f98d71eaaae1 +size 14284 diff --git a/marked/Rel-16/29_series/29163/09036266c6dba47efb2613ceaebe2b19_img.jpg b/marked/Rel-16/29_series/29163/09036266c6dba47efb2613ceaebe2b19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b57b44e95b00feb38b444d4adf44b0ee69554631 --- /dev/null +++ b/marked/Rel-16/29_series/29163/09036266c6dba47efb2613ceaebe2b19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2754ce8f8983b02f21a6bc79e8c3f07b610a9594c99b1d5e6a92405f66665b6 +size 13944 diff --git a/marked/Rel-16/29_series/29163/0943af69f1915094819054eb36d77807_img.jpg b/marked/Rel-16/29_series/29163/0943af69f1915094819054eb36d77807_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca6aa8c17cfdcc878f934d594708eeba134496ee --- /dev/null +++ b/marked/Rel-16/29_series/29163/0943af69f1915094819054eb36d77807_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ade94ef3cdab2dee517edf8e581418370f6acd4c88d3dbf6227c4ad4d3d2fae5 +size 12630 diff --git a/marked/Rel-16/29_series/29163/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/marked/Rel-16/29_series/29163/09955ff8214ffb6947951fc0f60eb6ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48a6a063cd1f249bc8eedaf4b4da9466db783845 --- /dev/null +++ b/marked/Rel-16/29_series/29163/09955ff8214ffb6947951fc0f60eb6ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:542e8e4fb74627f60d9f96efcab153fa3633284021ab4928f62ad7b6f3884213 +size 29614 diff --git a/marked/Rel-16/29_series/29163/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg b/marked/Rel-16/29_series/29163/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..175141123b95ccf9dce88031042278515cb8cced --- /dev/null +++ b/marked/Rel-16/29_series/29163/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f43eeab55323250ddad3a3799a3d3ee05e42f486522fc9119d2af5d2562352f4 +size 57808 diff --git a/marked/Rel-16/29_series/29163/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Rel-16/29_series/29163/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77fbf8365f0030e3a6a14c73e783660253974f12 --- /dev/null +++ b/marked/Rel-16/29_series/29163/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9f54cfb4afff5dff2620c0bc9a25a276db50dc6524bdc74c495730cc0b0a963 +size 27697 diff --git a/marked/Rel-16/29_series/29163/0db3cccd1279034258e5ad5b6fdcff01_img.jpg b/marked/Rel-16/29_series/29163/0db3cccd1279034258e5ad5b6fdcff01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af49e3d608cd619b21fb8382154e529265f46dc3 --- /dev/null +++ b/marked/Rel-16/29_series/29163/0db3cccd1279034258e5ad5b6fdcff01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ca3a13a623ff5eae30d06ca4faceec6e70657091f2ceac0cb0876c05283093b +size 7334 diff --git a/marked/Rel-16/29_series/29163/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/marked/Rel-16/29_series/29163/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a4328270474b1be1025100f7430aa56df36e689 --- /dev/null +++ b/marked/Rel-16/29_series/29163/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e262dcc585159cdb2c1397926a5f2499e0b4ec01a464ec85466ea2d3b4c0b1d1 +size 15702 diff --git a/marked/Rel-16/29_series/29163/1381593e48739f603c81fa60e6b98a6c_img.jpg b/marked/Rel-16/29_series/29163/1381593e48739f603c81fa60e6b98a6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7fad50cea452542bfa025a0913b876486168109 --- /dev/null +++ b/marked/Rel-16/29_series/29163/1381593e48739f603c81fa60e6b98a6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:964423023d6ebff15edbf3d04ac1e3497d6cc099c8d20f06db362e4cb5ca6684 +size 37741 diff --git a/marked/Rel-16/29_series/29163/1399c76ef88f22b70d05ed3f781d3c48_img.jpg b/marked/Rel-16/29_series/29163/1399c76ef88f22b70d05ed3f781d3c48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f57fc78d559f78fcbc791a60fc44d60e331bdaf --- /dev/null +++ b/marked/Rel-16/29_series/29163/1399c76ef88f22b70d05ed3f781d3c48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43eae90c9c6a063413e8320371f82fc42e858bddc49c722c11c23f7f6a611ed4 +size 11845 diff --git a/marked/Rel-16/29_series/29163/17431d8b59408f09df7552d8bdbaa015_img.jpg b/marked/Rel-16/29_series/29163/17431d8b59408f09df7552d8bdbaa015_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7504cb6e58814d7ac9fa9a7884a1d712e9edecb --- /dev/null +++ b/marked/Rel-16/29_series/29163/17431d8b59408f09df7552d8bdbaa015_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38ac5255e1ef460222b28e011d0e814989b873b7ffc61492544af4aa5af890fc +size 51620 diff --git a/marked/Rel-16/29_series/29163/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-16/29_series/29163/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1745d8c90b5c4cc44a80d5633a546685b332168 --- /dev/null +++ b/marked/Rel-16/29_series/29163/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8ea6a2eba0e2fc3bc1c3fac5f343bb18846be3572285e548042c9340720611b +size 126681 diff --git a/marked/Rel-16/29_series/29163/19499072f755b22d0a231123f75fa477_img.jpg b/marked/Rel-16/29_series/29163/19499072f755b22d0a231123f75fa477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8eb89d8c0d1c0c03a8271f0cbf36c17b54dab3ff --- /dev/null +++ b/marked/Rel-16/29_series/29163/19499072f755b22d0a231123f75fa477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8248318c31a22c2008016aebfc66693abcb1da729b56bc3121b53a7300d5e5f +size 11493 diff --git a/marked/Rel-16/29_series/29163/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/29_series/29163/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6457bbc7b7478e7b9b9f9476d47c8e6d2a7439e --- /dev/null +++ b/marked/Rel-16/29_series/29163/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b62d1e9cbad1d78c4a64a667847559bf21828ce16d5aeedb9872628523616cef +size 45706 diff --git a/marked/Rel-16/29_series/29163/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg b/marked/Rel-16/29_series/29163/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1c6906bb842a3fc0a73ac5bdb3e3fc73225a9b4 --- /dev/null +++ b/marked/Rel-16/29_series/29163/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:602e4fde66722d07b3c53941953b3be4261e96cee058772cbf10c9835eeb14c2 +size 84283 diff --git a/marked/Rel-16/29_series/29163/20e1585db1a707a774877194c689de82_img.jpg b/marked/Rel-16/29_series/29163/20e1585db1a707a774877194c689de82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad070f1568d5119b092dc00d92f680007bbbc1d0 --- /dev/null +++ b/marked/Rel-16/29_series/29163/20e1585db1a707a774877194c689de82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79db3c2efc3756f28179f55ace107eeae1746e0b55fd1c4454f31ae47ea72bea +size 23461 diff --git a/marked/Rel-16/29_series/29163/257c8341b41f1f4a287f27d33227974c_img.jpg b/marked/Rel-16/29_series/29163/257c8341b41f1f4a287f27d33227974c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb71238c2fa0ecae6cb060615c4986fdf9e2993b --- /dev/null +++ b/marked/Rel-16/29_series/29163/257c8341b41f1f4a287f27d33227974c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7cbf467b73ce54093578fb08b1153b4129c46fc915528a7120761ea4552f99e9 +size 61818 diff --git a/marked/Rel-16/29_series/29163/28085f681b9fff76a53c5b8b32338ee1_img.jpg b/marked/Rel-16/29_series/29163/28085f681b9fff76a53c5b8b32338ee1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f02c36ee1174b1d5e02bd2cabeb1e00efdc00ed1 --- /dev/null +++ b/marked/Rel-16/29_series/29163/28085f681b9fff76a53c5b8b32338ee1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1419abafd8a45fa97cb06768fe6def2636ad3e0721986420086985e71c3fedcb +size 93741 diff --git a/marked/Rel-16/29_series/29163/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-16/29_series/29163/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa1451c3f2eb2f33667b9e8c6f9820930da430e9 --- /dev/null +++ b/marked/Rel-16/29_series/29163/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86ee99cd379ac6a30527da380a4bb1d7d7430518d8c53e86d7c2bc65a57f21f5 +size 135866 diff --git a/marked/Rel-16/29_series/29163/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/29_series/29163/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae00e343d6ebc653329a451378a70b46f4b700ed --- /dev/null +++ b/marked/Rel-16/29_series/29163/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6743eee39008385db4b769c1e98821caaabd24ca00404befe7a14fd319c60e0 +size 58243 diff --git a/marked/Rel-16/29_series/29163/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-16/29_series/29163/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d001666e3e0e4e91ec08959eec63d52d861cf44 --- /dev/null +++ b/marked/Rel-16/29_series/29163/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69711a404c50fa494c2b68d3dbc60e55ac24e1e2a92b1baf2f291ee97db58a20 +size 17594 diff --git a/marked/Rel-16/29_series/29163/2e787cedee89518fd6c63f3cce1f913c_img.jpg b/marked/Rel-16/29_series/29163/2e787cedee89518fd6c63f3cce1f913c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..922287904aa87d1a4d2145a2f937f180f3545173 --- /dev/null +++ b/marked/Rel-16/29_series/29163/2e787cedee89518fd6c63f3cce1f913c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7cdbc0a005c4561fc88aac84eb1fe3f271051cd1905403ff1c659f641bb37640 +size 23561 diff --git a/marked/Rel-16/29_series/29163/30fe9e9487585118063341332e802e98_img.jpg b/marked/Rel-16/29_series/29163/30fe9e9487585118063341332e802e98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2132db134eea167ced318841f46b15b61810b819 --- /dev/null +++ b/marked/Rel-16/29_series/29163/30fe9e9487585118063341332e802e98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e61aaabc751573cac0b502eb1db06bd21abd240b28c6d068324dc2d3f7abe8e +size 39985 diff --git a/marked/Rel-16/29_series/29163/31ef15d175af5babdbf4d2fbac884c1b_img.jpg b/marked/Rel-16/29_series/29163/31ef15d175af5babdbf4d2fbac884c1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58f69fc5aa177b73ca86ef1801480aaa0212aee6 --- /dev/null +++ b/marked/Rel-16/29_series/29163/31ef15d175af5babdbf4d2fbac884c1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92067ad12ab18c32528a6b425d81001af5f3eeee4999415ccd3cacf6725d02ce +size 10166 diff --git a/marked/Rel-16/29_series/29163/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/marked/Rel-16/29_series/29163/33a8f3f01dfa8bce75d23017855a13c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b880ea7950ef618038e8b7d947b6647ea160e9a --- /dev/null +++ b/marked/Rel-16/29_series/29163/33a8f3f01dfa8bce75d23017855a13c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f00995c151a7ad005c14c9006f290de4d1f27e6ebd972a471e1a2870991e4e66 +size 24905 diff --git a/marked/Rel-16/29_series/29163/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/29_series/29163/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd9633b97efed910f3e14eb8086a712d8713b65d --- /dev/null +++ b/marked/Rel-16/29_series/29163/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b1d2a35d1d382f59cdb18bc3c838d6122f58241a4c217096c56002e2da652e5 +size 68494 diff --git a/marked/Rel-16/29_series/29163/474a819357587e34949a3e110ff19b30_img.jpg b/marked/Rel-16/29_series/29163/474a819357587e34949a3e110ff19b30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fa03df794effd3191107c67b6a94a8830dbc9de --- /dev/null +++ b/marked/Rel-16/29_series/29163/474a819357587e34949a3e110ff19b30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:faeb9457b9a0bbc97c304328fdb0cfcb2b46c3c12c2f2227c354d0cb530e4fec +size 157808 diff --git a/marked/Rel-16/29_series/29163/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg b/marked/Rel-16/29_series/29163/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4ad5e64f12d05ee34239c4d1b5096b20f24ba35 --- /dev/null +++ b/marked/Rel-16/29_series/29163/4cd9eeaee1deb05bf88a8abf02ff7d7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ce6c17f65017f7803a04767b432f6f23ae44130dd315b6d40291ca72b3f46b2 +size 29726 diff --git a/marked/Rel-16/29_series/29163/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-16/29_series/29163/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..035694abb1e0464939510a26d3297f2adfa35bf4 --- /dev/null +++ b/marked/Rel-16/29_series/29163/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b1d6602c38272ddbfefe7b0647a222a335add9212395ffe32409fc2d942e4b8 +size 100255 diff --git a/marked/Rel-16/29_series/29163/5043b1d06ff3f78c43f3432a4bae436d_img.jpg b/marked/Rel-16/29_series/29163/5043b1d06ff3f78c43f3432a4bae436d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a8dd6d76a012ed29d891113fe2c60df5169ffd2 --- /dev/null +++ b/marked/Rel-16/29_series/29163/5043b1d06ff3f78c43f3432a4bae436d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74d933eb72bdad6ab65f951a1b2afbcebea1337715c5e33c09f897326a3254e5 +size 21458 diff --git a/marked/Rel-16/29_series/29163/53e80f05e45f132bf76a96442a5507e9_img.jpg b/marked/Rel-16/29_series/29163/53e80f05e45f132bf76a96442a5507e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a718ce03e0313265124c6120c50362a94c63420b --- /dev/null +++ b/marked/Rel-16/29_series/29163/53e80f05e45f132bf76a96442a5507e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6efd7059e772e2de3cfd852ef45bbc54b401fee83978fdcfdda06251e2fd7b8 +size 46945 diff --git a/marked/Rel-16/29_series/29163/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg b/marked/Rel-16/29_series/29163/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..087ab4b2affbe449b79ed1a9c36bad29eab98940 --- /dev/null +++ b/marked/Rel-16/29_series/29163/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5c7d3cb70a070f01369c8e6e0ddef69d51fac4b7004fd1556aa224b16fa8099 +size 24723 diff --git a/marked/Rel-16/29_series/29163/55136bc716146672fc680fa05989f1d2_img.jpg b/marked/Rel-16/29_series/29163/55136bc716146672fc680fa05989f1d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7457545e5747238007714da425f1c7a4410d042 --- /dev/null +++ b/marked/Rel-16/29_series/29163/55136bc716146672fc680fa05989f1d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a82574356465d91d4529ae9547c84e32673ba595061fd1a25f3366eb3c31f7d2 +size 38442 diff --git a/marked/Rel-16/29_series/29163/5bba23cc120ad806779f82df1c01bebf_img.jpg b/marked/Rel-16/29_series/29163/5bba23cc120ad806779f82df1c01bebf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e12c83fa8a154aa54ebdf63d5f0e4d31e1ebfba --- /dev/null +++ b/marked/Rel-16/29_series/29163/5bba23cc120ad806779f82df1c01bebf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7331ad2be06a2955d0559c7ba49e7c61e5aae538e9248351994afa4be2a4e503 +size 9992 diff --git a/marked/Rel-16/29_series/29163/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg b/marked/Rel-16/29_series/29163/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..347b5108397acd42cdf94bbcccbba82a4b3f9fca --- /dev/null +++ b/marked/Rel-16/29_series/29163/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16ff6e65353e07a258109defd585f33d7f04ec792253b1bad246ea2f8116d917 +size 80493 diff --git a/marked/Rel-16/29_series/29163/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg b/marked/Rel-16/29_series/29163/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae22e24a99b2655b29b25498f9369295b2b3094b --- /dev/null +++ b/marked/Rel-16/29_series/29163/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfd8bd93e0db07ed2430b49fae1e43b0f4818817fddd4b289a45e7270ac6da80 +size 53121 diff --git a/marked/Rel-16/29_series/29163/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/marked/Rel-16/29_series/29163/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df9d49fd1ac2e557daba021b3b224afa35029637 --- /dev/null +++ b/marked/Rel-16/29_series/29163/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f0d48f638ac5b903c28e7b213ecc034cda49e14bb0ec40846ab2cd76d5dbb93 +size 29808 diff --git a/marked/Rel-16/29_series/29163/61a49f3179b455e4d35242fc3d187a29_img.jpg b/marked/Rel-16/29_series/29163/61a49f3179b455e4d35242fc3d187a29_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..beb51ea38765108798e51cc9e2064306b40b7708 --- /dev/null +++ b/marked/Rel-16/29_series/29163/61a49f3179b455e4d35242fc3d187a29_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afaa805333793d82debb0aa511a4e55116491d5678499b2220c5c4f29f12b113 +size 21804 diff --git a/marked/Rel-16/29_series/29163/61d000f6a2a1ff2f0da0b51fb732fafb_img.jpg b/marked/Rel-16/29_series/29163/61d000f6a2a1ff2f0da0b51fb732fafb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f19af624ea1df4cd46174d1069d75d107eb7f944 --- /dev/null +++ b/marked/Rel-16/29_series/29163/61d000f6a2a1ff2f0da0b51fb732fafb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40943d84741d231ef15930188d4f6f12ee843dd940934e87346199e78ca3b15c +size 16050 diff --git a/marked/Rel-16/29_series/29163/6361dfaef83c9ffc3b147e1627ba76a1_img.jpg b/marked/Rel-16/29_series/29163/6361dfaef83c9ffc3b147e1627ba76a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..404231eadb4c1fdab418acf83744101e190f8d57 --- /dev/null +++ b/marked/Rel-16/29_series/29163/6361dfaef83c9ffc3b147e1627ba76a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c13eed53f90c6b7c76cc5acce325dc8ca6b34fc66efee49ea375eea11c4d072 +size 39371 diff --git a/marked/Rel-16/29_series/29163/68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg b/marked/Rel-16/29_series/29163/68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57077833c515c3e4b35bf215dcdf48399acb8bb1 --- /dev/null +++ b/marked/Rel-16/29_series/29163/68d50e85fb8de4fae0e0eafaf20e63c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a4b50f842d26ba2cfb85b53a8ccbb370005c41c42afc2532215ae99d3f59e69 +size 150295 diff --git a/marked/Rel-16/29_series/29163/69733eeb3ef32197543f66f22a431771_img.jpg b/marked/Rel-16/29_series/29163/69733eeb3ef32197543f66f22a431771_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b5ef1d0736a5dd368fda9fd51598f339cc92d0d --- /dev/null +++ b/marked/Rel-16/29_series/29163/69733eeb3ef32197543f66f22a431771_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b752bbe13575623bcf8fd3517353188e2e37feefa21f6b3ad7a34fec1cf3ed8 +size 29465 diff --git a/marked/Rel-16/29_series/29163/69edc2887e907309499ac95b47ab6905_img.jpg b/marked/Rel-16/29_series/29163/69edc2887e907309499ac95b47ab6905_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b2648a180dbe647c6a1ce4669d35526260a6942 --- /dev/null +++ b/marked/Rel-16/29_series/29163/69edc2887e907309499ac95b47ab6905_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4197191aa48090248ee5f6628e30461230f44e71b5b29633972ed8114e711b35 +size 152187 diff --git a/marked/Rel-16/29_series/29163/6d67eee81b97a14e06a6fe57a95aff36_img.jpg b/marked/Rel-16/29_series/29163/6d67eee81b97a14e06a6fe57a95aff36_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08991a413b8a21d3da31a203b32b2934a3e4b9ff --- /dev/null +++ b/marked/Rel-16/29_series/29163/6d67eee81b97a14e06a6fe57a95aff36_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f750d7fd8fd673a7dfbcd23ac750d914d17af7d7b72cae0dfd4037202b2207a +size 43309 diff --git a/marked/Rel-16/29_series/29163/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/29_series/29163/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a916745daca6928d3e7466a0590fce5ac9b7ab2a --- /dev/null +++ b/marked/Rel-16/29_series/29163/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c71f863aaf7f204c2e04b0faa6ca8ee467d668037eb28599c31b73545324a78a +size 167699 diff --git a/marked/Rel-16/29_series/29163/735e3bc9f8e35ffd7d0a9f37d8da6afb_img.jpg b/marked/Rel-16/29_series/29163/735e3bc9f8e35ffd7d0a9f37d8da6afb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3ab6f33b89d59601935e77ba755576ab53e76f9 --- /dev/null +++ b/marked/Rel-16/29_series/29163/735e3bc9f8e35ffd7d0a9f37d8da6afb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec25eec6fd70be988f8eb7d47f37bd6270da80afb0fe1a729dc565441ac4afb2 +size 804 diff --git a/marked/Rel-16/29_series/29163/74d23510f27b21403a7be84820821863_img.jpg b/marked/Rel-16/29_series/29163/74d23510f27b21403a7be84820821863_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f02c3ad3a4339c7c5f8ab856063093965c737c3b --- /dev/null +++ b/marked/Rel-16/29_series/29163/74d23510f27b21403a7be84820821863_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:183e0b740abedf4057b80ee8b7dd7f8973c49b59cdc9c2bc4e4ebc399700d3f4 +size 155352 diff --git a/marked/Rel-16/29_series/29163/74e409e1548dd2606c4de9bdfe9806e4_img.jpg b/marked/Rel-16/29_series/29163/74e409e1548dd2606c4de9bdfe9806e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c6eb57b7f3c7c55514ef5b51730ee3ef6bed53d --- /dev/null +++ b/marked/Rel-16/29_series/29163/74e409e1548dd2606c4de9bdfe9806e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c39e3fee7fe379aa2e850ddea4d8b1f0dd447d1be44e79e7ebb9526b442563c9 +size 8748 diff --git a/marked/Rel-16/29_series/29163/7913c315e0db8233cb1ac2455e4a0a81_img.jpg b/marked/Rel-16/29_series/29163/7913c315e0db8233cb1ac2455e4a0a81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9da10b03c7af185c7b5079ad5ceda344d0941421 --- /dev/null +++ b/marked/Rel-16/29_series/29163/7913c315e0db8233cb1ac2455e4a0a81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f8f37e790b3e74ed28a0466e681e001c0cb098fab49e8a17e975ab6f8f2a45d +size 14440 diff --git a/marked/Rel-16/29_series/29163/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg b/marked/Rel-16/29_series/29163/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4be5f90225051629fa7b35b5ee193b6c593c10d0 --- /dev/null +++ b/marked/Rel-16/29_series/29163/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8cebbc546c741ae935af589a918b32b2a3cbd3059bf6676147c0566f9e3d4055 +size 42275 diff --git a/marked/Rel-16/29_series/29163/80d994053160f3b1d88b075564af9e57_img.jpg b/marked/Rel-16/29_series/29163/80d994053160f3b1d88b075564af9e57_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac6eb822383effac5b6c99cab3d4f0c4546b3bdb --- /dev/null +++ b/marked/Rel-16/29_series/29163/80d994053160f3b1d88b075564af9e57_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9709174887654604e7b8ca19a574b69f379b055fb5f09d91aa0a0d9907522791 +size 42419 diff --git a/marked/Rel-16/29_series/29163/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/29_series/29163/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..370766f54fadaf29708ebc792baa7b0deb946023 --- /dev/null +++ b/marked/Rel-16/29_series/29163/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11f9e76808b931545e94fb95e8c2d90f1debd09a00a79b32f881e6157b143859 +size 67238 diff --git a/marked/Rel-16/29_series/29163/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-16/29_series/29163/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..527212876ac9175f3f324807c60f4f643ae6def0 --- /dev/null +++ b/marked/Rel-16/29_series/29163/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c1369005187aac1dfbc4f6a87f60495e888b478a7e741a43191ca61d6e7e6e9 +size 92323 diff --git a/marked/Rel-16/29_series/29163/8277ec2f29c84d97cbe70bc413a42cd1_img.jpg b/marked/Rel-16/29_series/29163/8277ec2f29c84d97cbe70bc413a42cd1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cc684fa4aba92b0f7f628fea19b7de3eafd6645 --- /dev/null +++ b/marked/Rel-16/29_series/29163/8277ec2f29c84d97cbe70bc413a42cd1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7ea60a1602c592fb3652943096f8115f523ba27642e251283fbbef609205b73 +size 9099 diff --git a/marked/Rel-16/29_series/29163/848073118eebfdbfdb9a60e3923fe0b3_img.jpg b/marked/Rel-16/29_series/29163/848073118eebfdbfdb9a60e3923fe0b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..939588a61a4efffbd2f9553957d92ff9b804af3d --- /dev/null +++ b/marked/Rel-16/29_series/29163/848073118eebfdbfdb9a60e3923fe0b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f417aa8fe2134995d1a4f777c0d5f4e3c14183cdb1cb6bbb327c0f101c82cbe +size 55903 diff --git a/marked/Rel-16/29_series/29163/88b0f3f4393228e9ea4d6542aef7c399_img.jpg b/marked/Rel-16/29_series/29163/88b0f3f4393228e9ea4d6542aef7c399_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e9357fb89df53046573fb047c8fc8aa3d0f4b10 --- /dev/null +++ b/marked/Rel-16/29_series/29163/88b0f3f4393228e9ea4d6542aef7c399_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41eadb8e9a38dc6c4318b1f2da428f0a05db8dba2a7fd8eeaa54b35ffef2d477 +size 80042 diff --git a/marked/Rel-16/29_series/29163/8edfc370769207831f060f44d2281084_img.jpg b/marked/Rel-16/29_series/29163/8edfc370769207831f060f44d2281084_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78acb2b5baca087b66e64d2d2578dfaf53e7a649 --- /dev/null +++ b/marked/Rel-16/29_series/29163/8edfc370769207831f060f44d2281084_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26a71cae1dccb5a3983a43371a2e60c3a2a95f4fc735cd1e6da086c796a14e28 +size 39908 diff --git a/marked/Rel-16/29_series/29163/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/29_series/29163/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2274d2ee1b11fc1cff40436cb475b837c0232ef6 --- /dev/null +++ b/marked/Rel-16/29_series/29163/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a217979947a8761788be0bdbfc99d9a85bf3f64ef01107bff2b8db85921a646b +size 46750 diff --git a/marked/Rel-16/29_series/29163/8fecf981da2650d0a2832e4b9ac5c934_img.jpg b/marked/Rel-16/29_series/29163/8fecf981da2650d0a2832e4b9ac5c934_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db3b580c58ab06c5af0b7afb20679b9e821bc626 --- /dev/null +++ b/marked/Rel-16/29_series/29163/8fecf981da2650d0a2832e4b9ac5c934_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:942b930ae1ab0c633e98c139e72e013549ae2cc5ac281e981112595725b53755 +size 15206 diff --git a/marked/Rel-16/29_series/29163/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/29_series/29163/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bd7a49d95e11ba0917c9bfb95cc5a244049a827 --- /dev/null +++ b/marked/Rel-16/29_series/29163/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0e75d9a524cca878d32e0bb832370ff891af4ca4308f90aa0506fa573975613 +size 137665 diff --git a/marked/Rel-16/29_series/29163/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-16/29_series/29163/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98241998572b41c174aff8a8f6b59797ef07ceca --- /dev/null +++ b/marked/Rel-16/29_series/29163/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4007de4abbf4f20bf1808c6eeb9fc46a2316350d278dadbf2823620b0466d693 +size 57660 diff --git a/marked/Rel-16/29_series/29163/977811d1c73b74f801be9f4c376694ca_img.jpg b/marked/Rel-16/29_series/29163/977811d1c73b74f801be9f4c376694ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32d795d76d8b492c6f8922fb43f0e635f7c94d67 --- /dev/null +++ b/marked/Rel-16/29_series/29163/977811d1c73b74f801be9f4c376694ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f040ec5a14cfd9430de0f5912b7641d9850e674bebb0b6e359cddc6fd4df625f +size 161800 diff --git a/marked/Rel-16/29_series/29163/9870bf462aa0d916a16d14b5a100c60a_img.jpg b/marked/Rel-16/29_series/29163/9870bf462aa0d916a16d14b5a100c60a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cd2b31629461e3ee248ae983e578c3c3db66505 --- /dev/null +++ b/marked/Rel-16/29_series/29163/9870bf462aa0d916a16d14b5a100c60a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f91f0db38a0e4b687f86444ebe2138e6da7beebd14d6c8f00c17904e271dca2 +size 48189 diff --git a/marked/Rel-16/29_series/29163/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/marked/Rel-16/29_series/29163/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4737e1c7542af17a45c3c8a4740262ac3555746b --- /dev/null +++ b/marked/Rel-16/29_series/29163/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2f9e4f9570a33d0459eed4c5c34e6d5bee5b9320e67fe1ff4b3b7a830d87da9 +size 33142 diff --git a/marked/Rel-16/29_series/29163/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg b/marked/Rel-16/29_series/29163/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5abda095e9de8eda960f77d06e3d63301a87a7a2 --- /dev/null +++ b/marked/Rel-16/29_series/29163/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0044f7765090cac58a959b3a1bffd858fa3f66cbe92152d7fce6ae4d685fea58 +size 13474 diff --git a/marked/Rel-16/29_series/29163/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/29_series/29163/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c035084ce737c4b36dfa844a70c755ad5f00058b --- /dev/null +++ b/marked/Rel-16/29_series/29163/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b85a3917aa21152dce00d34cf46dbc9731e9f0bd84adfb6683893ffd7ecf0139 +size 14499 diff --git a/marked/Rel-16/29_series/29163/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/29_series/29163/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b66158da95e77f3ea9efde4857b70b3214af45a1 --- /dev/null +++ b/marked/Rel-16/29_series/29163/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:feee8b81954592d62a34e0727698130f8877400894bf1452ea6617f6ab6706ef +size 49403 diff --git a/marked/Rel-16/29_series/29163/9f862801bce82634d3b5a1e0a195a799_img.jpg b/marked/Rel-16/29_series/29163/9f862801bce82634d3b5a1e0a195a799_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c60cc9ac8f692fa4d2c187799d7f94d1fa1e34a0 --- /dev/null +++ b/marked/Rel-16/29_series/29163/9f862801bce82634d3b5a1e0a195a799_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e940b7243edc50508f1778cfc4c26d0e671929e52b7d25a4a39c56cba3124d9d +size 78603 diff --git a/marked/Rel-16/29_series/29163/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/29_series/29163/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5162db0e4eb1195d062d29957873a9d071d8d69c --- /dev/null +++ b/marked/Rel-16/29_series/29163/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:44a64e418ab2c336a8d6e0d4ea8d7349ab8e42ce0e1f4f6aa1790a3edbcc7eb0 +size 33020 diff --git a/marked/Rel-16/29_series/29163/a4b868a176f7e0448ee72483727e9f6f_img.jpg b/marked/Rel-16/29_series/29163/a4b868a176f7e0448ee72483727e9f6f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15b3983c5281d3e9cd67d6e83ae007ae91bd2c8d --- /dev/null +++ b/marked/Rel-16/29_series/29163/a4b868a176f7e0448ee72483727e9f6f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b46e0e6e36f72ea6cd00c779b7907f0911d26d6e3111dcf14f414479303ed600 +size 8912 diff --git a/marked/Rel-16/29_series/29163/a5184899f915014fa38608754efcc9c7_img.jpg b/marked/Rel-16/29_series/29163/a5184899f915014fa38608754efcc9c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55fcd9e9b19b04ef321fa1336686995c7825ab0e --- /dev/null +++ b/marked/Rel-16/29_series/29163/a5184899f915014fa38608754efcc9c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f998cf1d816d7261474946a076d0dd783621e30191f95cd3d9012917c05a7d91 +size 113853 diff --git a/marked/Rel-16/29_series/29163/a66383962afcd0f0458f0d45c101fabf_img.jpg b/marked/Rel-16/29_series/29163/a66383962afcd0f0458f0d45c101fabf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e6a3e94b7c23212aa913cf6332f5c015ad2000f --- /dev/null +++ b/marked/Rel-16/29_series/29163/a66383962afcd0f0458f0d45c101fabf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbf15daa87f17a5844c53a389bbfb9de9db24c9979942b52f54d8bc4a786dfa5 +size 9071 diff --git a/marked/Rel-16/29_series/29163/a8f498be9c286684f48a3eb211ce4cea_img.jpg b/marked/Rel-16/29_series/29163/a8f498be9c286684f48a3eb211ce4cea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fd98ab95744388aa873269048a4027c0404c498 --- /dev/null +++ b/marked/Rel-16/29_series/29163/a8f498be9c286684f48a3eb211ce4cea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5f89ef9d151b7bb7292ae8ba62e2b0075ce588c0fb31e3eb1b21edb1263a2072 +size 9749 diff --git a/marked/Rel-16/29_series/29163/aa73c8651865e31f7a2f7b8a9c068461_img.jpg b/marked/Rel-16/29_series/29163/aa73c8651865e31f7a2f7b8a9c068461_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64642cb917ea32b0abebce7e89c95432f120f022 --- /dev/null +++ b/marked/Rel-16/29_series/29163/aa73c8651865e31f7a2f7b8a9c068461_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb537506fbd8f2dc6543572266c341cfe874a25d7e3a755fa6fb5a81e6ab98fa +size 25386 diff --git a/marked/Rel-16/29_series/29163/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/29_series/29163/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08c4c24964c664e6525211ac29ce6bcb0de739a1 --- /dev/null +++ b/marked/Rel-16/29_series/29163/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f814e79623e9bb8d487d6ba4334cbe90474722b8c104847b3cf35192491c07e +size 167685 diff --git a/marked/Rel-16/29_series/29163/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg b/marked/Rel-16/29_series/29163/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef0b5250b6cf2f961d31324fa70315f9b2c54f32 --- /dev/null +++ b/marked/Rel-16/29_series/29163/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a7cb1c58b95d66b9f3a808fd8e1151c2e58118af611de6dae3dcbbb3ce77961 +size 39596 diff --git a/marked/Rel-16/29_series/29163/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-16/29_series/29163/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8f5d0869c422b81f7d07343d47119296ac16676 --- /dev/null +++ b/marked/Rel-16/29_series/29163/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03db1ea3887dd6c0982d0894ee310f638f2320fa7baf3e6da84b3f5053edc325 +size 21181 diff --git a/marked/Rel-16/29_series/29163/b50f38be091844d58b11e3d47bc71e73_img.jpg b/marked/Rel-16/29_series/29163/b50f38be091844d58b11e3d47bc71e73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1706ad5b3bc6654a2e76a5294ad6e3d14e8eae9 --- /dev/null +++ b/marked/Rel-16/29_series/29163/b50f38be091844d58b11e3d47bc71e73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e82e1524f3a6163be067fddd993f9f218c71914d1beeace9a96607528fe0eb7 +size 67414 diff --git a/marked/Rel-16/29_series/29163/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/marked/Rel-16/29_series/29163/b51423b6c049f5b5fcde42e50b58f18b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b79c275fc9dfa58df8cb59f913fee7dfa484d968 --- /dev/null +++ b/marked/Rel-16/29_series/29163/b51423b6c049f5b5fcde42e50b58f18b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3adf0b29f4f3e7d50565f69834ede2bbd2e598c93e8cf108431c91d3ae4f5155 +size 48144 diff --git a/marked/Rel-16/29_series/29163/b5987d63203a5fa601921039922ac520_img.jpg b/marked/Rel-16/29_series/29163/b5987d63203a5fa601921039922ac520_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..955f2a0272c84a394ff9daddb6e1311102b135a4 --- /dev/null +++ b/marked/Rel-16/29_series/29163/b5987d63203a5fa601921039922ac520_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e10578220044c3110221bdb341be5754c075812369a11bb678e9a0f4ec842858 +size 78835 diff --git a/marked/Rel-16/29_series/29163/b8efedb73292a798b3f2050f9335cae6_img.jpg b/marked/Rel-16/29_series/29163/b8efedb73292a798b3f2050f9335cae6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..398229b7e1a90d87bc49fe76b6fd7f7b4b4b12fa --- /dev/null +++ b/marked/Rel-16/29_series/29163/b8efedb73292a798b3f2050f9335cae6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21fa4fb98f59c04c58820718acbd8c455f3d8101a13b29455a9b6bd7a31f3c56 +size 21570 diff --git a/marked/Rel-16/29_series/29163/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-16/29_series/29163/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7721d62cdfcdec29f82c946732aa99c60a31724 --- /dev/null +++ b/marked/Rel-16/29_series/29163/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d67104f9a8268df795decb62e1e7449471cf5c0ac0abfb29554e9efd1109ccde +size 133650 diff --git a/marked/Rel-16/29_series/29163/bf32ff2a1af507083217ccc56c515a50_img.jpg b/marked/Rel-16/29_series/29163/bf32ff2a1af507083217ccc56c515a50_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e68caf545181abafc314079c3a4e01d93de84c1 --- /dev/null +++ b/marked/Rel-16/29_series/29163/bf32ff2a1af507083217ccc56c515a50_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9dbbfb5fa337c0f1ab1be06760598ac1e2ec100f05b31d862153a33137fcc25 +size 8112 diff --git a/marked/Rel-16/29_series/29163/c036e2540a94b31357ceb0002f0cacab_img.jpg b/marked/Rel-16/29_series/29163/c036e2540a94b31357ceb0002f0cacab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6fbf1be70bca0aca67657b077e831a21341c631 --- /dev/null +++ b/marked/Rel-16/29_series/29163/c036e2540a94b31357ceb0002f0cacab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c1b6bb8b8c991ac70e7c39d350fe92ade4849d366ed8c3bb77eff5224ca62b6 +size 38341 diff --git a/marked/Rel-16/29_series/29163/c0ca823603794512478906b302176bca_img.jpg b/marked/Rel-16/29_series/29163/c0ca823603794512478906b302176bca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..908cf0f421f4cb39dc0529a61aa02100cb2eae2f --- /dev/null +++ b/marked/Rel-16/29_series/29163/c0ca823603794512478906b302176bca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f42bcb12d0d9677e089c2c2e59f0b596780a494baf190d358cfb82e585102a3d +size 18693 diff --git a/marked/Rel-16/29_series/29163/c21bad844b5cb6026c067a1f43ce67c3_img.jpg b/marked/Rel-16/29_series/29163/c21bad844b5cb6026c067a1f43ce67c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a737b24b80fd098c8b0f65a8156e3996b5f5334 --- /dev/null +++ b/marked/Rel-16/29_series/29163/c21bad844b5cb6026c067a1f43ce67c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d191e3aa73514a8032d8231d8fe213af319cee06bf6981983d4a636355f902f5 +size 163229 diff --git a/marked/Rel-16/29_series/29163/c6005b2627c6ca10f6b0e94cdb34858d_img.jpg b/marked/Rel-16/29_series/29163/c6005b2627c6ca10f6b0e94cdb34858d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8c2c67f4ae24e22fec792b4c97c2c40ae5dde6d --- /dev/null +++ b/marked/Rel-16/29_series/29163/c6005b2627c6ca10f6b0e94cdb34858d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53e73d57523a4db5d76c95368ad457e8da8d06f95850256218243b798e36f958 +size 24850 diff --git a/marked/Rel-16/29_series/29163/c686c005fef31702c109f5d9dd975413_img.jpg b/marked/Rel-16/29_series/29163/c686c005fef31702c109f5d9dd975413_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfe959ae2d94cc327b6970308257b513520888e9 --- /dev/null +++ b/marked/Rel-16/29_series/29163/c686c005fef31702c109f5d9dd975413_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4963935f02bf81a3cbed66380382100e6ca6d942ba0de9c0ce6b4ffb28ae1996 +size 7410 diff --git a/marked/Rel-16/29_series/29163/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-16/29_series/29163/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25451f761593cc66b2a1be7bd8abfb955689e213 --- /dev/null +++ b/marked/Rel-16/29_series/29163/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b044df14dc12cefeda973662ed5f2ff49bdc442a77994f3a8a4c40456008a0a +size 81755 diff --git a/marked/Rel-16/29_series/29163/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg b/marked/Rel-16/29_series/29163/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b076a93f999702e7ea0cae7a7d24b47f1f130bf --- /dev/null +++ b/marked/Rel-16/29_series/29163/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91fa58838e3f6bb63f1c5089cd7c5f1174ce1cc16c8e438fb180fed965165c87 +size 53014 diff --git a/marked/Rel-16/29_series/29163/cb698d64c91df5a86b05bbddc202c144_img.jpg b/marked/Rel-16/29_series/29163/cb698d64c91df5a86b05bbddc202c144_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..058ff8e1f7dd0b49d990a656a6a23e0b04f55e61 --- /dev/null +++ b/marked/Rel-16/29_series/29163/cb698d64c91df5a86b05bbddc202c144_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:778f5b442baf73bdcfdbb1ee005e27a4bd2134a0583d2b6b8d7bc37b49055695 +size 18951 diff --git a/marked/Rel-16/29_series/29163/ccf6853c7291703cb04568057fef5849_img.jpg b/marked/Rel-16/29_series/29163/ccf6853c7291703cb04568057fef5849_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a2aa1bccd4adcd677491570cf22594760053f95 --- /dev/null +++ b/marked/Rel-16/29_series/29163/ccf6853c7291703cb04568057fef5849_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de3ea810dcc0c462b13c39ca0b450947f90381778dfd47b921b3fc7d90811036 +size 32897 diff --git a/marked/Rel-16/29_series/29163/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/29_series/29163/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76e8ba39ae37aeb2c72c590edc719a1e9c5d74ec --- /dev/null +++ b/marked/Rel-16/29_series/29163/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:614cf72778b04a02655505853d9d71bc73a0e804e415eadccf8423647daab679 +size 61578 diff --git a/marked/Rel-16/29_series/29163/d2517ac00a9e8064ae23cb653e651d1b_img.jpg b/marked/Rel-16/29_series/29163/d2517ac00a9e8064ae23cb653e651d1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d2b4e6e13158ff6bfb40aca90e0434e7496d7a4 --- /dev/null +++ b/marked/Rel-16/29_series/29163/d2517ac00a9e8064ae23cb653e651d1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:523e8185936beebb35d410fd3b273a44e05986e576571a447bf86a5cdb9fd369 +size 905 diff --git a/marked/Rel-16/29_series/29163/d31e6cf9a987586abee2f530b7812041_img.jpg b/marked/Rel-16/29_series/29163/d31e6cf9a987586abee2f530b7812041_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c1af61a7b17567e23c1f7a0d345b8352a3b0e5e --- /dev/null +++ b/marked/Rel-16/29_series/29163/d31e6cf9a987586abee2f530b7812041_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d19f5b05e5e5d570a39d02e4a2bddbd5cdb1a65386e3cf3b601786105cf65bd +size 7350 diff --git a/marked/Rel-16/29_series/29163/dc37a040cf9e2add7488c7c37cbf3687_img.jpg b/marked/Rel-16/29_series/29163/dc37a040cf9e2add7488c7c37cbf3687_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7fbc008f759224b786b04bf78a231098629db945 --- /dev/null +++ b/marked/Rel-16/29_series/29163/dc37a040cf9e2add7488c7c37cbf3687_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3c03f66b2f660e3c2bba2b034ecd6e792fbf4bcea172417a1a51009c8d38c66 +size 16935 diff --git a/marked/Rel-16/29_series/29163/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/29_series/29163/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c57a93662409a5d23116e67d0e894d27316e27c --- /dev/null +++ b/marked/Rel-16/29_series/29163/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60cd6354965b5c99dcb39c9b7fff66a4ae25d647d2af2ebc7a8643d66de51f9f +size 132459 diff --git a/marked/Rel-16/29_series/29163/ddb58f51e65a3ae8ebc5911df26e18e0_img.jpg b/marked/Rel-16/29_series/29163/ddb58f51e65a3ae8ebc5911df26e18e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ce1d3a554e12323eb141a4ac8ebe34ccfb45d63 --- /dev/null +++ b/marked/Rel-16/29_series/29163/ddb58f51e65a3ae8ebc5911df26e18e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fdfb8e04394a304feb9b2080858d7c9bd7728a9381c98b268845e6fa3ed9d24f +size 80449 diff --git a/marked/Rel-16/29_series/29163/e05c1a13b44ab41505609d82b00cf4df_img.jpg b/marked/Rel-16/29_series/29163/e05c1a13b44ab41505609d82b00cf4df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62a4a728d442c079c73cee835200fc2d3f42d9c6 --- /dev/null +++ b/marked/Rel-16/29_series/29163/e05c1a13b44ab41505609d82b00cf4df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54e5c956746688ddd55276fb58794be1a1a27c6c39a24f2e2b3c8a84880591d2 +size 107982 diff --git a/marked/Rel-16/29_series/29163/e16bfa31d748f4d99ec4ae3d16656926_img.jpg b/marked/Rel-16/29_series/29163/e16bfa31d748f4d99ec4ae3d16656926_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d15a33960dca01fbca79e9aa5d097dd21bf2fd3a --- /dev/null +++ b/marked/Rel-16/29_series/29163/e16bfa31d748f4d99ec4ae3d16656926_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e550aee988c3f427dbd7ed08318bafe5342b8b6772d36811d97fb04656860df +size 23022 diff --git a/marked/Rel-16/29_series/29163/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/29_series/29163/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..356be10d14c3814ae533f050558ff19c03a9310a --- /dev/null +++ b/marked/Rel-16/29_series/29163/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:443dc257bb967e6ab2a82e0ec242a89b19ae9da06c7cd6a72b2360055e09e0be +size 125416 diff --git a/marked/Rel-16/29_series/29163/e26bb66586e464339df27951d5c9355e_img.jpg b/marked/Rel-16/29_series/29163/e26bb66586e464339df27951d5c9355e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f46dc1b6ecaea93246f5e80d1edadf048d9d8e24 --- /dev/null +++ b/marked/Rel-16/29_series/29163/e26bb66586e464339df27951d5c9355e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5de98eebe5932b395eeb10d1497edd64d649fbb174500b0e56c281c6358ed2c +size 66861 diff --git a/marked/Rel-16/29_series/29163/e35f25e0b66752d4179a4cb108a3fb5a_img.jpg b/marked/Rel-16/29_series/29163/e35f25e0b66752d4179a4cb108a3fb5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c32f108694b87233a0f313c3f9f725320183d8a --- /dev/null +++ b/marked/Rel-16/29_series/29163/e35f25e0b66752d4179a4cb108a3fb5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b683105e136427f8dca26eadb5f9196051b120e7e599c7020de8deb2665d5163 +size 28590 diff --git a/marked/Rel-16/29_series/29163/e534e903e6dae8a582643bfd9f89254c_img.jpg b/marked/Rel-16/29_series/29163/e534e903e6dae8a582643bfd9f89254c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1b8f6d125e3acfe2aedabaf6b6fd1bb171fb560 --- /dev/null +++ b/marked/Rel-16/29_series/29163/e534e903e6dae8a582643bfd9f89254c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ab9e5c8ad00bd01f327a89a2226f4b53da8d495c83bada2e3fe43cb51f8811e +size 12488 diff --git a/marked/Rel-16/29_series/29163/e64106d52dee350a3439ff0d396d26fc_img.jpg b/marked/Rel-16/29_series/29163/e64106d52dee350a3439ff0d396d26fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15afd6ebab94449ed419d610e4fdbadf277e6399 --- /dev/null +++ b/marked/Rel-16/29_series/29163/e64106d52dee350a3439ff0d396d26fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a030209f091d210d571b0f829a7732944bc733b67e26215f0f9889620c0aa1bf +size 13426 diff --git a/marked/Rel-16/29_series/29163/f5e131a3fffe09aa98db055df84e4378_img.jpg b/marked/Rel-16/29_series/29163/f5e131a3fffe09aa98db055df84e4378_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d4f7c94a01508c8498801c14c3efa0b95aefc7c --- /dev/null +++ b/marked/Rel-16/29_series/29163/f5e131a3fffe09aa98db055df84e4378_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1deffa94f74c4aaa1836455910ea6ab8c5ec17043015eeff9918a6b6d0bc9b64 +size 26599 diff --git a/marked/Rel-16/29_series/29163/fc0cdcafc5389b99674ba116c9787ffd_img.jpg b/marked/Rel-16/29_series/29163/fc0cdcafc5389b99674ba116c9787ffd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..16b7f16aa1db4d051a6f9ee9aa977134f3091f1d --- /dev/null +++ b/marked/Rel-16/29_series/29163/fc0cdcafc5389b99674ba116c9787ffd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9e3cec9f965949c6289c3aeab3f5f544c0af777b238ef4eea1f63cdc7279f70 +size 15741 diff --git a/marked/Rel-16/29_series/29163/fe7304192caf64cda93b580c5e7e5c06_img.jpg b/marked/Rel-16/29_series/29163/fe7304192caf64cda93b580c5e7e5c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a91c8d52cc6966bbc3ab2dbe3bf9c3ee1b1aac41 --- /dev/null +++ b/marked/Rel-16/29_series/29163/fe7304192caf64cda93b580c5e7e5c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:003378b34ac9edf94504ac71dd3227511bc2516a4426b8d9a3c22ced012a996a +size 30975 diff --git a/marked/Rel-16/29_series/29163/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/29_series/29163/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6bcc55018db042a0d8b130c40aea08e8a2e4d6c --- /dev/null +++ b/marked/Rel-16/29_series/29163/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e97d5c172c665357e96083c2368bcf8b9da40c36e7fa7c24c4d659099520c16 +size 66294 diff --git a/marked/Rel-16/29_series/29163/ffefa4f6eab4ce450aa5ecd3d3fd70bb_img.jpg b/marked/Rel-16/29_series/29163/ffefa4f6eab4ce450aa5ecd3d3fd70bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdf1709de556c84cfdf311b3660f20e748733f32 --- /dev/null +++ b/marked/Rel-16/29_series/29163/ffefa4f6eab4ce450aa5ecd3d3fd70bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f30c391e48560259a52deed953a734c05a4b2ddede6e01c4c4adc0abad3b079b +size 27532 diff --git a/marked/Rel-16/29_series/29163/raw.md b/marked/Rel-16/29_series/29163/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2562d218a4e69dcbe17fc4764e4bf3227c6da599 --- /dev/null +++ b/marked/Rel-16/29_series/29163/raw.md @@ -0,0 +1,12585 @@ +Error: + +2 + +Error: Reference source not found + +# Contents + +| | | +|-----------------------------------------------------------------------------------|----| +| Foreword..... | 18 | +| 1 Scope..... | 19 | +| 2 References..... | 19 | +| 3 Definitions and abbreviations..... | 25 | +| 3.1 Definitions..... | 25 | +| 3.2 Abbreviations..... | 26 | +| 4 General..... | 28 | +| 4.1 General interworking overview..... | 28 | +| 5 Network characteristics..... | 28 | +| 5.1 Key characteristics of ISUP/BICC based CS networks..... | 28 | +| 5.2 Key characteristics of IM CN subsystem..... | 29 | +| 6 Interworking with CS networks..... | 29 | +| 6.1 Interworking reference model..... | 29 | +| 6.1.1 Interworking reference points and interfaces..... | 29 | +| 6.1.2 Interworking functional entities..... | 30 | +| 6.1.2.1 Signalling Gateway Function (SGW)..... | 30 | +| 6.1.2.2 Media Gateway Control Function (MGCF)..... | 30 | +| 6.1.2.3 IP Multimedia - Media Gateway Function (IM-MGW)..... | 30 | +| 6.2 Control plane interworking model..... | 30 | +| 6.3 User plane interworking model..... | 30 | +| 7 Control plane interworking..... | 30 | +| 7.1 General..... | 31 | +| 7.2 Interworking between CS networks supporting ISUP and the IM CN subsystem..... | 31 | +| 7.2.1 Services performed by network entities in the control plane..... | 32 | +| 7.2.1.1 Services performed by the SS7 signalling function..... | 32 | +| 7.2.1.2 Services of the SGW..... | 32 | +| 7.2.1.3 Services of the MGCF..... | 32 | +| 7.2.1.4 Services of the SIP signalling function..... | 32 | +| 7.2.2 Signalling interactions between network entities in the control plane..... | 32 | +| 7.2.2.1 Signalling between the SS7 signalling function and MGCF..... | 32 | +| 7.2.2.1.1 Signalling from MGCF to SS7 signalling function..... | 32 | +| 7.2.2.1.2 Signalling from SS7 signalling function to MGCF..... | 33 | +| 7.2.2.1.3 Services offered by SCTP and M3UA..... | 33 | +| 7.2.2.1.3.1 Services offered by SCTP..... | 33 | +| 7.2.2.1.3.2 Services offered by M3UA..... | 33 | +| 7.2.2.2 Signalling between the MGCF and SIP signalling function..... | 33 | +| 7.2.3 SIP-ISUP protocol interworking..... | 33 | +| 7.2.3.1 Incoming call interworking from SIP to ISUP at I-MGCF..... | 33 | +| 7.2.3.1.1 Sending of IAM..... | 33 | +| 7.2.3.1.2 Coding of the IAM..... | 35 | +| 7.2.3.1.2.0 General..... | 35 | +| 7.2.3.1.2.1 Called party number..... | 35 | +| 7.2.3.1.2.2 Nature of connection indicators..... | 36 | +| 7.2.3.1.2.3 Forward call indicators..... | 37 | +| 7.2.3.1.2.4 Calling party's category..... | 38 | +| 7.2.3.1.2.4A Originating Line Information..... | 38 | +| 7.2.3.1.2.5 Transmission medium requirement..... | 38 | +| 7.2.3.1.2.5a Transmission medium requirement prime and USI prime (optional)..... | 40 | +| 7.2.3.1.2.6 Calling party number..... | 42 | +| 7.2.3.1.2.7 Generic number..... | 46 | +| 7.2.3.1.2.8 User service information..... | 46 | +| 7.2.3.1.2.9 Hop Counter (National option)..... | 47 | + +| | | | +|-----------------|------------------------------------------------------------------------------------------|----| +| 7.2.3.1.2.10 | Progress Indicator..... | 47 | +| 7.2.3.1.2.11 | Location Number..... | 47 | +| 7.2.3.1.2.12 | Support of ICS call..... | 49 | +| 7.2.3.1.2.13 | UID capability indicators (National option)..... | 49 | +| 7.2.3.1.2.14 | Called IN number and original called IN number (optional)..... | 50 | +| 7.2.3.1.2.A | Coding of the IAM when Number Portability is supported..... | 50 | +| 7.2.3.1.2.A.1 | Coding of the IAM when a Number Portability Routing Number is available..... | 50 | +| 7.2.3.1.2.A.1.1 | Separate Directory Number Addressing Method..... | 51 | +| 7.2.3.1.2.A.1.2 | Concatenated Addressing Method..... | 52 | +| 7.2.3.1.2.A.1.3 | Separate Network Routing Number Addressing Method..... | 52 | +| 7.2.3.1.2.A.2 | Number Portability Forward Information..... | 53 | +| 7.2.3.1.2.B | Coding of the IAM for Carrier Routeing..... | 53 | +| 7.2.3.1.2.B.1 | Coding of the IAM when a Carrier Identification Code (CIC) is present..... | 53 | +| 7.2.3.1.2.B.2 | Void..... | 53 | +| 7.2.3.1.3 | Sending of COT..... | 53 | +| 7.2.3.1.3.A | Sending of SAM..... | 54 | +| 7.2.3.1.3.A.1 | General..... | 54 | +| 7.2.3.1.3.A.2 | Additional digits received in in-dialog SIP INFO requests..... | 54 | +| 7.2.3.1.3.A.3 | Additional digits received in SIP INVITE requests..... | 54 | +| 7.2.3.1.4 | Sending of 180 ringing..... | 55 | +| 7.2.3.1.4.0 | General..... | 55 | +| 7.2.3.1.4.0a | PSTN XML body..... | 56 | +| 7.2.3.1.4.0b | Fallback by I-MGCF..... | 57 | +| 7.2.3.1.4.1 | Fallback in a succeeding network: Transmission Medium Used parameter (TMU) received..... | 58 | +| 7.2.3.1.4.A | Sending of 183 Session Progress for early media scenarios..... | 58 | +| 7.2.3.1.4.B | Sending of 181Call is being forwarded..... | 61 | +| 7.2.3.1.4.C | Sending of 183 Session Progress for overlap signalling using the in-dialog method..... | 62 | +| 7.2.3.1.4.D | Sending of 183 Session Progress to carry ISUP Cause..... | 62 | +| 7.2.3.1.4.E | Sending of 183 Session Progress for ICS call..... | 62 | +| 7.2.3.1.5 | Sending of the 200 OK (INVITE)..... | 63 | +| 7.2.3.1.6 | Sending of the Release message (REL)..... | 65 | +| 7.2.3.1.7 | Coding of the REL..... | 65 | +| 7.2.3.1.8 | Receipt of the Release Message..... | 67 | +| 7.2.3.1.9 | Receipt of RSC, GRS or CGB (H/W oriented)..... | 70 | +| 7.2.3.1.9a | Receipt of REFER..... | 70 | +| 7.2.3.1.10 | Autonomous Release at I-MGCF..... | 71 | +| 7.2.3.1.11 | Internal through connection of the bearer path..... | 71 | +| 7.2.3.2 | Outgoing Call Interworking from ISUP to SIP at O-MGCF..... | 71 | +| 7.2.3.2.1 | Sending of INVITE..... | 71 | +| 7.2.3.2.1.1 | General..... | 71 | +| 7.2.3.2.1.2 | Interaction with continuity check..... | 72 | +| 7.2.3.2.1.3 | IAM without calling party number..... | 72 | +| 7.2.3.2.1.4 | Terminating overlap signalling at MGCF..... | 73 | +| 7.2.3.2.1.5 | Fallback (optional)..... | 73 | +| 7.2.3.2.1a | Sending of INVITE without determining the end of address signalling..... | 74 | +| 7.2.3.2.1a.1 | General..... | 74 | +| 7.2.3.2.1a.2 | Additional digits sent with in-dialog overlap method..... | 74 | +| 7.2.3.2.1a.3 | Additional digits sent using the multiple INVITEs overlap method..... | 75 | +| 7.2.3.2.2 | Coding of the INVITE..... | 76 | +| 7.2.3.2.2.0 | Overview..... | 76 | +| 7.2.3.2.2.1 | Request-URI and To header field..... | 76 | +| 7.2.3.2.2.2 | SDP Media Description..... | 77 | +| 7.2.3.2.2.3 | P-Asserted-Identity, From and Privacy header fields..... | 80 | +| 7.2.3.2.2.3.A | "cpc" URI Parameter in P-Asserted-Identity Header..... | 85 | +| 7.2.3.2.2.3.B | "oli" URI Parameter in P-Asserted-Identity Header..... | 85 | +| 7.2.3.2.2.4 | Max Forwards header..... | 86 | +| 7.2.3.2.2.5 | IMS Communication Service Identifier..... | 86 | +| 7.2.3.2.2.6 | P-Early-Media header field..... | 86 | + +| | | | +|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 7.2.3.2.2.7 | PSTN XML elements..... | 86 | +| 7.2.3.2.2.8 | Progress indicator..... | 87 | +| 7.2.3.2.2.9 | P-Access-Network-Info..... | 88 | +| 7.2.3.2.2.A | Coding of the INVITE when Number Portability is supported..... | 88 | +| 7.2.3.2.2.A.1 | Request-URI and To header field..... | 88 | +| 7.2.3.2.2.A.1.1 | Separate Directory Number Addressing Method..... | 89 | +| 7.2.3.2.2.A.1.2 | Concatenated Addressing Method..... | 89 | +| 7.2.3.2.2.A.1.3 | Separate Network Routing Number Addressing Method..... | 90 | +| 7.2.3.2.2.B | Coding of the INVITE for Carrier Routeing..... | 90 | +| 7.2.3.2.2.B.1 | Mapping of "cic" in Request-URI..... | 90 | +| 7.2.3.2.2.B.2 | Void..... | 90 | +| 7.2.3.2.2.C | Coding of INVITE with instance-id in form of IMEI URN..... | 90 | +| 7.2.3.2.2.10 | PSAP Call-back indication..... | 91 | +| 7.2.3.2.2.11 | History-Info header field (optional)..... | 91 | +| 7.2.3.2.3 | Receipt of CONTINUITY..... | 91 | +| 7.2.3.2.4 | Sending of ACM and awaiting answer indication..... | 92 | +| 7.2.3.2.5 | Coding of the ACM..... | 94 | +| 7.2.3.2.5.0 | General..... | 94 | +| 7.2.3.2.5.1 | Backward call indicators..... | 95 | +| 7.2.3.2.5.2 | Optional Backward call indicators..... | 96 | +| 7.2.3.2.5.3 | Access Transport Parameter, Transmission medium used parameter..... | 96 | +| 7.2.3.2.5.4 | Progress indicator..... | 97 | +| 7.2.3.2.5.5 | Cause Value..... | 97 | +| 7.2.3.2.6 | Sending of the Call Progress message (CPG)..... | 97 | +| 7.2.3.2.6.0 | General..... | 97 | +| 7.2.3.2.6.1 | Handling of the progress indicator..... | 99 | +| 7.2.3.2.7 | Coding of the CPG..... | 99 | +| 7.2.3.2.7.0 | General..... | 99 | +| 7.2.3.2.7.1 | Event information..... | 100 | +| 7.2.3.2.7.2 | Access Transport Parameter..... | 100 | +| 7.2.3.2.7.3 | Void..... | 100 | +| 7.2.3.2.7.4 | Handling of Backward Call indicators..... | 100 | +| 7.2.3.2.7.5 | Optional Backward call indicators..... | 100 | +| 7.2.3.2.7.6 | Cause Value..... | 100 | +| 7.2.3.2.7.a | Receipt of 200 OK(INVITE)..... | 101 | +| 7.2.3.2.7.b | Internal through connection of the bearer path..... | 101 | +| 7.2.3.2.8 | Sending of the Answer Message (ANM)..... | 101 | +| 7.2.3.2.9 | Coding of the ANM..... | 101 | +| 7.2.3.2.9.1 | Backwards Call Indicators..... | 101 | +| 7.2.3.2.9.2 | Access Transport Parameter..... | 101 | +| 7.2.3.2.9.3 | Transmission Medium Used parameter (TMU)..... | 102 | +| 7.2.3.2.10 | Sending of the Connect message (CON)..... | 103 | +| 7.2.3.2.11 | Coding of the CON..... | 103 | +| 7.2.3.2.11.0 | General..... | 103 | +| 7.2.3.2.11.1 | Backward call indicators..... | 103 | +| 7.2.3.2.11.2 | Access Transport Parameter..... | 103 | +| 7.2.3.2.11.3 | Transmission medium used parameter..... | 103 | +| 7.2.3.2.11.A | Receipt of a reINVITE request..... | 103 | +| 7.2.3.2.12 | Receipt of Status Codes 4xx, 5xx or 6xx..... | 103 | +| 7.2.3.2.12.1 | Special handling of 404 Not Found and 484 Address Incomplete responses after sending of INVITE without determining the end of address signalling..... | 106 | +| 7.2.3.2.13 | Receipt of a BYE..... | 106 | +| 7.2.3.2.14 | Receipt of the Release Message..... | 106 | +| 7.2.3.2.15 | Receipt of RSC, GRS or CGB (H/W oriented)..... | 107 | +| 7.2.3.2.16 | Autonomous Release at O-MGCF..... | 107 | +| 7.2.3.2.17 | Special handling of 580 precondition failure received in response to either an INVITE or UPDATE..... | 107 | +| 7.2.3.2.17.1 | 580 Precondition failure response to an INVITE..... | 107 | +| 7.2.3.2.17.2 | 580 Precondition failure response to an UPDATE within an early dialog..... | 107 | + +| | | | +|--------------|----------------------------------------------------------------------------------------|-----| +| 7.2.3.2.18 | Sending of CANCEL..... | 108 | +| 7.2.3.2.19 | Receipt of SIP redirect (3xx) response..... | 108 | +| 7.2.3.2.20 | Sending of INFO for overlap signalling using the in-dialog method..... | 108 | +| 7.2.3.2.20.1 | General..... | 108 | +| 7.2.3.2.20.2 | Encoding of the INFO..... | 108 | +| 7.2.3.3 | Timers..... | 109 | +| 7.3 | Interworking between CS networks supporting BICC and the IM CN subsystem..... | 109 | +| 7.3.1 | Services performed by network entities in the control plane..... | 110 | +| 7.3.2 | Signalling interactions between network entities in the control plane..... | 110 | +| 7.3.2.1 | Signalling between the SS7 signalling function and MGCF..... | 110 | +| 7.3.2.1.1 | Signalling from MGCF to SS7 signalling function..... | 110 | +| 7.3.2.1.2 | Signalling from SS7 signalling function to MGCF..... | 110 | +| 7.3.2.1.3 | Services offered by STC, SCTP and M3UA..... | 111 | +| 7.3.2.1.3.1 | Services offer by SCTP..... | 111 | +| 7.3.2.1.3.2 | Services offered by M3UA..... | 111 | +| 7.3.2.1.3.3 | Services offered by STC..... | 111 | +| 7.3.2.2 | Signalling between the MGCF and SIP signalling function..... | 111 | +| 7.3.3 | SIP-BICC protocol interworking..... | 111 | +| 7.3.3.1 | Incoming call interworking from SIP to BICC at I-MGCF..... | 111 | +| 7.3.3.1.1 | Sending of IAM..... | 111 | +| 7.3.3.1.2 | Coding of IAM..... | 111 | +| 7.3.3.1.2.1 | Called party number..... | 111 | +| 7.3.3.1.2.2 | Nature of connection indicators..... | 111 | +| 7.3.3.1.2.3 | Forward call indicators..... | 112 | +| 7.3.3.1.2.4 | Calling party's category..... | 112 | +| 7.3.3.1.2.4A | Originating Line Information..... | 112 | +| 7.3.3.1.2.5 | Transmission medium requirement..... | 112 | +| 7.3.3.1.2.6 | Calling party number..... | 112 | +| 7.3.3.1.2.7 | Generic number..... | 112 | +| 7.3.3.1.2.8 | User service information..... | 112 | +| 7.3.3.1.2.9 | Hop counter (National option)..... | 112 | +| 7.3.3.1.2.10 | Location Number..... | 112 | +| 7.3.3.1.2.11 | Support of ICS call..... | 112 | +| 7.3.3.1.2.12 | UID capability indicators (National option)..... | 112 | +| 7.3.3.1.2.A | Coding of the IAM when Number Portability is supported..... | 112 | +| 7.3.3.1.2.B | Coding of the IAM for Carrier Routeing..... | 112 | +| 7.3.3.1.2.13 | Called IN number and original called IN number (optional)..... | 112 | +| 7.3.3.1.3 | Sending of COT..... | 113 | +| 7.3.3.1.3.A | Sending of SAM..... | 113 | +| 7.3.3.1.4 | Sending of 180 Ringing..... | 113 | +| 7.3.3.1.4.A | Sending of 183 Session Progress for early media scenarios..... | 113 | +| 7.3.3.1.4.B | Sending of 181 Call is being forwarded..... | 113 | +| 7.3.3.1.4.C | Sending of 183 Session Progress for overlap signalling using the in-dialog method..... | 113 | +| 7.3.3.1.4.D | Sending of 183 Session Progress to carry ISUP Cause..... | 113 | +| 7.3.3.1.4.E | Sending of 183 Session Progress for ICS call..... | 113 | +| 7.3.3.1.5 | Sending of the 200 OK (INVITE)..... | 114 | +| 7.3.3.1.6 | Sending of the Release message (REL)..... | 114 | +| 7.3.3.1.7 | Coding of the REL..... | 114 | +| 7.3.3.1.8 | Receipt of the Release Message..... | 114 | +| 7.3.3.1.9 | Receipt of RSC, GRS or CGB (H/W oriented)..... | 114 | +| 7.3.3.1.9a | Receipt of REFER..... | 114 | +| 7.3.3.1.9b | Autonomous Release at I-MGCF..... | 114 | +| 7.3.3.1.10 | Internal through connection of the bearer path..... | 114 | +| 7.3.3.1.11 | Out of Band DTMF..... | 114 | +| 7.3.3.2 | Outgoing Call Interworking from BICC to SIP at O-MGCF..... | 114 | +| 7.3.3.2.1 | Sending of INVITE..... | 114 | +| 7.3.3.2.1a | Sending of INVITE without determining the end of address signalling..... | 115 | +| 7.3.3.2.2 | Coding of the INVITE..... | 115 | +| 7.3.3.2.2.1 | Request-URI and To header field..... | 115 | + +| | | | +|--------------|-------------------------------------------------------------------------------------------------------------------------------|-----| +| 7.3.3.2.2.2 | SDP Media Description..... | 115 | +| 7.3.3.2.2.3 | P-Asserted-Identity and privacy header fields..... | 115 | +| 7.3.3.2.2.3A | "cpc" URI Parameter in P-Asserted-Identity Header..... | 115 | +| 7.3.3.2.2.3B | "oli" URI Parameter in P-Asserted-Identity Header..... | 115 | +| 7.3.3.2.2.4 | Max Forwards header..... | 115 | +| 7.3.3.2.2.5 | IMS Communication Service Identifier..... | 116 | +| 7.3.3.2.2.6 | P-Access-Network-Info..... | 116 | +| 7.3.3.2.2.A | Coding of the INVITE when number portability is supported..... | 116 | +| 7.3.3.2.2.B | Coding of the INVITE for Carrier Routeing..... | 116 | +| 7.3.3.2.2.C | Coding of INVITE with instance-id in form of IMEI URN..... | 116 | +| 7.3.3.2.2.7 | PSAP Call-back indication..... | 116 | +| 7.3.3.2.2.8 | History-Info header field (optional)..... | 116 | +| 7.3.3.2.3 | Sending of UPDATE..... | 116 | +| 7.3.3.2.4 | Sending of ACM and Awaiting Answer indication..... | 117 | +| 7.3.3.2.5 | Coding of the ACM..... | 117 | +| 7.3.3.2.5.1 | Backward call indicators..... | 117 | +| 7.3.3.2.6 | Sending of the Call Progress message (CPG)..... | 117 | +| 7.3.3.2.7 | Coding of the CPG..... | 117 | +| 7.3.3.2.7.1 | Event information..... | 117 | +| 7.3.3.2.7.2 | Optional Backward call indicators..... | 117 | +| 7.3.3.2.7a | Receipt of 200 OK (INVITE)..... | 117 | +| 7.3.3.2.7b | Internal through connection of the bearer path..... | 117 | +| 7.3.3.2.8 | Sending of the Answer Message (ANM)..... | 117 | +| 7.3.3.2.9 | Coding of the ANM..... | 117 | +| 7.3.3.2.10 | Sending of the Connect message (CON)..... | 117 | +| 7.3.3.2.11 | Coding of the CON..... | 118 | +| 7.3.3.2.11.1 | Void..... | 118 | +| 7.3.3.2.11A | Receipt of re-INVITE requests..... | 118 | +| 7.3.3.2.12 | Receipt of Status Codes 4xx, 5xx or 6xx..... | 118 | +| 7.3.3.2.13 | Receipt of a BYE..... | 118 | +| 7.3.3.2.14 | Receipt of the Release Message..... | 118 | +| 7.3.3.2.15 | Receipt of RSC, GRS or CGB (H/W oriented)..... | 118 | +| 7.3.3.2.16 | Out of Band DTMF..... | 118 | +| 7.3.3.2.17 | Sending of CANCEL..... | 118 | +| 7.3.3.2.18 | Autonomous Release at O-MGCF..... | 118 | +| 7.3.3.2.19 | Special handling of 580 precondition failure received in response to either an INVITE or UPDATE..... | 118 | +| 7.3.3.2.20 | Receipt of SIP redirect (3xx) response..... | 119 | +| 7.3.3.2.21 | Sending of INFO for overlap signalling using the in-dialog method..... | 119 | +| 7.3.3.3 | Timers..... | 119 | +| 7.4 | Supplementary Services..... | 119 | +| 7.4.1 | Calling line identification presentation/restriction (CLIP/CLIR)..... | 119 | +| 7.4.2 | Connected line presentation and restriction (COLP/COLR)..... | 119 | +| 7.4.2.0 | General..... | 119 | +| 7.4.2.1 | Incoming Call Interworking from SIP to BICC/ISUP at the I-MGCF..... | 119 | +| 7.4.2.1.1 | INVITE to IAM interworking (SIP to ISUP/BICC calls)..... | 119 | +| 7.4.2.1.2 | ANM/CON to 200 OK (INVITE)..... | 120 | +| 7.4.2.2 | Outgoing Call Interworking from BICC/ISUP to SIP at O-MGCF..... | 120 | +| 7.4.2.2.1 | IAM to INVITE interworking (ISUP to SIP calls)..... | 120 | +| 7.4.2.2.2 | 1XX to ANM or CON interworking..... | 121 | +| 7.4.2.2.3 | 200 OK (INVITE) to ANM/CON interworking..... | 121 | +| 7.4.3 | Direct Dialling In (DDI)..... | 122 | +| 7.4.4 | Malicious call identification..... | 122 | +| 7.4.5 | Subaddressing (SUB)..... | 122 | +| 7.4.5.1 | General..... | 122 | +| 7.4.5.2 | Interworking at I-MGCF..... | 123 | +| 7.4.5.3 | Interworking at O-MGCF..... | 124 | +| 7.4.6 | Call Forwarding Busy (CFB)/ Call Forwarding No Reply (CFNR) / Call Forwarding Unconditional (CFU) / Call Deflection (CD)..... | 126 | + +| | | | +|------------|-----------------------------------------------------------------------------------------------------|-----| +| 7.4.6.1 | General..... | 126 | +| 7.4.6.2 | Interworking at the O-MGCF..... | 127 | +| 7.4.6.2.1 | General..... | 127 | +| 7.4.6.2.2 | Interworking SIP to ISUP..... | 127 | +| 7.4.6.2.3 | Interworking ISUP to SIP..... | 131 | +| 7.4.6.3 | Interworking at the I-MGCF..... | 133 | +| 7.4.6.3.1 | General..... | 133 | +| 7.4.6.3.2 | Interworking from SIP to ISUP..... | 134 | +| 7.4.6.3.3 | Interworking from ISUP to SIP..... | 136 | +| 7.4.7 | Void..... | 141 | +| 7.4.8 | Explicit Call Transfer (ECT)..... | 141 | +| 7.4.9 | Call Waiting..... | 141 | +| 7.4.10 | Call Hold..... | 141 | +| 7.4.10.1 | Session hold initiated from the IM CN subsystem side..... | 141 | +| 7.4.10.2 | Session hold initiated from the CS network side..... | 143 | +| 7.4.11 | Call Completion on busy subscriber..... | 145 | +| 7.4.12 | Completion of Calls on No Reply (CCNR)..... | 145 | +| 7.4.13 | Terminal Portability (TP)..... | 145 | +| 7.4.14 | Conference calling (CONF) / Three-Party Service (3PTY)..... | 145 | +| 7.4.15 | Void..... | 146 | +| 7.4.16 | Closed User Group (CUG)..... | 146 | +| 7.4.17 | Multi-Level Precedence and Pre-emption (MLPP)..... | 146 | +| 7.4.18 | Global Virtual Network Service (GVNS)..... | 146 | +| 7.4.19 | International telecommunication charge card (ITCC)..... | 146 | +| 7.4.20 | Reverse charging (REV)..... | 146 | +| 7.4.21 | User-to-User Signalling (UUS)..... | 146 | +| 7.4.21.0 | General..... | 146 | +| 7.4.21.1 | User-to-User Signalling (UUS) service 1 (implicit)..... | 146 | +| 7.4.21.1.0 | General..... | 146 | +| 7.4.21.1.1 | Void..... | 147 | +| 7.4.21.1.2 | User-to-user information Interworking from SIP to ISUP..... | 147 | +| 7.4.21.1.3 | User-to-user information Interworking from ISUP to SIP..... | 147 | +| 7.4.21.2 | User-to-User Signalling (UUS) service 1 (explicit)..... | 147 | +| 7.4.21.3 | User-to-User Signalling (UUS) service 2 (explicit)..... | 147 | +| 7.4.21.4 | User-to-User Signalling (UUS) service 3 (explicit)..... | 147 | +| 7.4.22 | Multiple Subscriber Number (MSN)..... | 148 | +| 7.4.23 | Anonymous Call rejection..... | 148 | +| 7.4.23.0 | General..... | 148 | +| 7.4.23.1 | ISUP-SIP protocol interworking at the I-MGCF..... | 148 | +| 7.4.23.2 | SIP-ISUP protocol interworking at the O-MGCF..... | 148 | +| 7.4.24 | Customized Alerting Tones (CAT) in the 3GPP CS domain..... | 148 | +| 7.5 | IMS Supplementary Services..... | 148 | +| 7.5.1 | Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR)..... | 148 | +| 7.5.2 | Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR)..... | 148 | +| 7.5.2.1 | General..... | 148 | +| 7.5.2.2 | Interworking at the O-MGCF..... | 149 | +| 7.5.2.3 | Interworking at the I-MGCF..... | 150 | +| 7.5.2.4 | Timer..... | 151 | +| 7.5.3 | void..... | 151 | +| 7.5.4 | Communication Diversion (CDIV)..... | 151 | +| 7.5.4.1 | General..... | 151 | +| 7.5.4.2 | Interworking at the O-MGCF..... | 152 | +| 7.5.4.2.1 | General..... | 152 | +| 7.5.4.2.2 | Call Diversion within the ISUP Network appeared..... | 157 | +| 7.5.4.3 | Interworking at the I-MGCF..... | 160 | +| 7.5.5 | Communication Hold (HOLD)..... | 168 | +| 7.5.6 | Conference call (CONF)..... | 168 | +| 7.5.6.1 | General..... | 168 | +| 7.5.6.2 | Subscribing for the conference event package..... | 168 | + +| | | | +|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 7.5.6.3 | Interworking the notification..... | 169 | +| 7.5.7 | Anonymous Communication Rejection (ACR) and Communication Barring (CB)..... | 170 | +| 7.5.8 | Message Waiting Indication (MWI)..... | 170 | +| 7.5.9 | Malicious Communication Identification (MCID)..... | 170 | +| 7.5.9.0 | General..... | 170 | +| 7.5.9.1 | Interworking at the O-MGCF..... | 170 | +| 7.5.9.1.0 | General..... | 170 | +| 7.5.9.1.1 | Interworking of the MCID XML Request schema with the ISUP MCID request indicators..... | 170 | +| 7.5.9.1.2 | Interworking of the ISUP MCID response indicators with the MCID XML Response schema.... | 171 | +| 7.5.9.1.3 | Interworking of the ISUP Calling Party Number in an Identification Response with the
OrigPartyIdentity within the MCID XML Response schema..... | 171 | +| 7.5.9.1.4 | Interworking of the ISUP Generic Number in an Identification Response with the
GenericNumber within the MCID XML Response schema..... | 171 | +| 7.5.9.2 | Interworking at the I-MGCF..... | 172 | +| 7.5.9.2.1 | General..... | 172 | +| 7.5.9.2.2 | Interworking of identification Request..... | 172 | +| 7.5.9.2.3 | Interworking of identification Response..... | 172 | +| 7.5.10 | Closed User Group (CUG)..... | 172 | +| 7.5.10.0 | General..... | 172 | +| 7.5.10.1 | Interworking at the I-MGCF..... | 172 | +| 7.5.10.2 | Interworking at the O-MGCF..... | 173 | +| 7.5.11 | CCBS/CCNR..... | 174 | +| 7.5.11.0 | General..... | 174 | +| 7.5.11.1 | Interworking at the I-MGCF..... | 174 | +| 7.5.11.2 | Interworking at the O-MGCF..... | 177 | +| 7.5.12 | Communication Waiting (CW)..... | 179 | +| 7.5.12.0 | General..... | 179 | +| 7.5.12.1 | Interworking at the I-MGCF..... | 179 | +| 7.5.12.2 | Interworking at the O-MGCF..... | 179 | +| 7.5.13 | Customized Alerting Tones (CAT)..... | 179 | +| 7.5.13.1 | General..... | 179 | +| 7.5.13.2 | Early session model..... | 179 | +| 7.5.13.2.1 | Interworking at the O-MGCF..... | 179 | +| 7.5.13.2.2 | MGCF - IM-MGW Interaction for CAT service..... | 180 | +| 7.5.13.2.2.1 | General..... | 180 | +| 7.5.13.2.2.2 | IM CN subsystem side Early Session establishment..... | 180 | +| 7.5.13.2.2.3 | IM CN subsystem side normal Session establishment..... | 180 | +| 7.5.13.2.2.4 | Called party alerting..... | 181 | +| 7.5.13.2.2.5 | Message sequence chart..... | 181 | +| 7.5.13.3 | Forging model..... | 184 | +| 7.5.13.4 | Gateway model..... | 184 | +| 8 | User plane interworking..... | 184 | +| 8.1 | Interworking between IM CN subsystem and bearer independent CS network..... | 184 | +| 8.1.1 | Transcoder-less Mb to Nb Interworking..... | 185 | +| 8.1.1.1 | Initialisation..... | 185 | +| 8.1.1.2 | Time alignment..... | 185 | +| 8.1.1.3 | Rate control..... | 185 | +| 8.1.1.3.1 | General..... | 185 | +| 8.1.1.3.2 | Rate control for AMR and AMR-WB codecs..... | 185 | +| 8.1.1.3.3 | Rate and Mode control for the EVS codec..... | 186 | +| 8.1.1.3.4 | Interworking of rate control between compatible AMR-WB and EVS codec configurations..... | 187 | +| 8.1.1.3.5 | Interworking between rate control and RTCP-APP-CMR messages for MTSI..... | 187 | +| 8.1.1.4 | Frame quality indication..... | 188 | +| 8.1.1.5 | Framing..... | 188 | +| 8.1.1.6 | Transcoding..... | 188 | +| 8.1.1.7 | Discontinuous transmission..... | 188 | +| 8.1.1.8 | Timing and sequence information..... | 189 | +| 8.2 | Interworking between IM CN subsystem and TDM-based CS network..... | 189 | +| 8.3 | Transcoding requirements..... | 189 | + +| | | | +|------------|---------------------------------------------------|-----| +| 8.4 | Diffserv code point requirements..... | 189 | +| 8.5 | DTMF handling..... | 190 | +| 9 | MGCF - IM-MGW Interaction..... | 190 | +| 9.1 | Overview..... | 190 | +| 9.2 | Mn signalling interactions..... | 190 | +| 9.2.1 | Network model..... | 190 | +| 9.2.2 | Basic IM CN subsystem originated session..... | 191 | +| 9.2.2.1 | BICC forward bearer establishment..... | 191 | +| 9.2.2.1.1 | IM-MGW selection..... | 191 | +| 9.2.2.1.2 | CS network side bearer establishment..... | 191 | +| 9.2.2.1.3 | IM CN subsystem side termination reservation..... | 191 | +| 9.2.2.1.4 | IM CN subsystem side session establishment..... | 192 | +| 9.2.2.1.5 | Through-connection..... | 192 | +| 9.2.2.1.6 | Codec handling..... | 192 | +| 9.2.2.1.7 | Failure handling in MGCF..... | 193 | +| 9.2.2.1.8 | Message sequence chart..... | 193 | +| 9.2.2.2 | BICC backward bearer establishment..... | 194 | +| 9.2.2.2.1 | IM-MGW selection..... | 194 | +| 9.2.2.2.2 | IM CN subsystem side termination reservation..... | 195 | +| 9.2.2.2.3 | IM CN subsystem side session establishment..... | 195 | +| 9.2.2.2.4 | CS network side bearer establishment..... | 195 | +| 9.2.2.2.5 | Through-connection..... | 196 | +| 9.2.2.2.6 | Codec handling..... | 196 | +| 9.2.2.2.7 | Failure handling in MGCF..... | 196 | +| 9.2.2.2.8 | Message sequence chart..... | 196 | +| 9.2.2.3 | ISUP..... | 197 | +| 9.2.2.3.1 | IM-MGW selection..... | 197 | +| 9.2.2.3.2 | IM CN subsystem side termination reservation..... | 197 | +| 9.2.2.3.3 | IM CN subsystem side session establishment..... | 198 | +| 9.2.2.3.4 | CS network side circuit reservation..... | 198 | +| 9.2.2.3.5 | Through-connection..... | 198 | +| 9.2.2.3.6 | Continuity check..... | 199 | +| 9.2.2.3.7 | Codec handling..... | 199 | +| 9.2.2.3.8 | Voice processing function..... | 199 | +| 9.2.2.3.9 | Failure handling in MGCF..... | 199 | +| 9.2.2.3.10 | Message sequence chart..... | 199 | +| 9.2.3 | Basic CS network originated session..... | 201 | +| 9.2.3.1 | BICC forward bearer establishment..... | 201 | +| 9.2.3.1.1 | IM-MGW selection..... | 201 | +| 9.2.3.1.2 | IM CN subsystem side termination reservation..... | 201 | +| 9.2.3.1.3 | IM CN subsystem side session establishment..... | 201 | +| 9.2.3.1.4 | CS network side bearer establishment..... | 201 | +| 9.2.3.1.5 | Called party alerting..... | 202 | +| 9.2.3.1.6 | Called party answer..... | 202 | +| 9.2.3.1.7 | Through-Connection..... | 202 | +| 9.2.3.1.8 | Codec handling..... | 202 | +| 9.2.3.1.9 | Failure handling in MGCF..... | 202 | +| 9.2.3.1.10 | Message sequence chart..... | 202 | +| 9.2.3.2 | BICC Backward bearer establishment..... | 204 | +| 9.2.3.2.1 | IM-MGW selection..... | 204 | +| 9.2.3.2.2 | CS network side bearer establishment..... | 204 | +| 9.2.3.2.3 | IM CN subsystem side termination reservation..... | 204 | +| 9.2.3.2.4 | IM CN subsystem side session establishment..... | 205 | +| 9.2.3.2.5 | Called party alerting..... | 205 | +| 9.2.3.2.6 | Called party answer..... | 205 | +| 9.2.3.2.7 | Through-Connection..... | 205 | +| 9.2.3.2.8 | Codec handling..... | 205 | +| 9.2.3.2.9 | Failure handling in MGCF..... | 206 | +| 9.2.3.2.10 | Message sequence chart..... | 206 | + +| | | | +|------------|----------------------------------------------------------------------------|-----| +| 9.2.3.3 | ISUP..... | 208 | +| 9.2.3.3.1 | IM-MGW selection..... | 208 | +| 9.2.3.3.2 | CS network side circuit reservation..... | 208 | +| 9.2.3.3.3 | IM CN subsystem side termination reservation..... | 208 | +| 9.2.3.3.4 | IM CN subsystem side session establishment..... | 208 | +| 9.2.3.3.5 | Called party alerting..... | 209 | +| 9.2.3.3.6 | Called party answer..... | 209 | +| 9.2.3.3.7 | Through-Connection..... | 209 | +| 9.2.3.3.8 | Continuity Check..... | 209 | +| 9.2.3.3.9 | Codec handling..... | 209 | +| 9.2.3.3.10 | Voice Processing function..... | 210 | +| 9.2.3.3.11 | Failure handling in MGCF..... | 210 | +| 9.2.3.3.12 | Message sequence chart..... | 210 | +| 9.2.3.4 | Handling of Forking..... | 212 | +| 9.2.3.4.1 | Detection of Forking..... | 212 | +| 9.2.3.4.2 | IM CN subsystem side session establishment..... | 212 | +| 9.2.3.4.3 | IM CN subsystem side session establishment completion..... | 214 | +| 9.2.3.4.4 | Message sequence chart..... | 215 | +| 9.2.4 | Session release initiated from IM CN subsystem side..... | 218 | +| 9.2.4.1 | BICC..... | 218 | +| 9.2.4.1.1 | Session release in the IM CN subsystem side..... | 218 | +| 9.2.4.1.2 | Session release in the CS network side..... | 218 | +| 9.2.4.1.3 | Message sequence chart..... | 218 | +| 9.2.4.2 | ISUP..... | 219 | +| 9.2.4.2.1 | Session release in the IM CN subsystem side..... | 219 | +| 9.2.4.2.2 | Session release in the CS network side..... | 219 | +| 9.2.4.2.3 | Message sequence chart..... | 219 | +| 9.2.5 | Session release initiated from CS network side..... | 219 | +| 9.2.5.1 | BICC..... | 219 | +| 9.2.5.1.1 | Session release in the CS network side..... | 219 | +| 9.2.5.1.2 | Session release in the IM CN subsystem side..... | 220 | +| 9.2.5.1.3 | Message sequence chart..... | 220 | +| 9.2.5.2 | ISUP..... | 220 | +| 9.2.5.2.1 | Session release in the CS network side..... | 220 | +| 9.2.5.2.2 | Session release in the IM CN subsystem side..... | 221 | +| 9.2.5.2.3 | Message sequence chart..... | 221 | +| 9.2.6 | Session release initiated by MGCF..... | 221 | +| 9.2.6.1 | BICC..... | 221 | +| 9.2.6.1.1 | Session release in the CS network side..... | 221 | +| 9.2.6.1.2 | Session release in the IM CN subsystem side..... | 221 | +| 9.2.6.1.3 | Message sequence chart..... | 222 | +| 9.2.6.2 | ISUP..... | 222 | +| 9.2.6.2.1 | Session release in the CS network side..... | 222 | +| 9.2.6.2.2 | Session release in the IM CN subsystem side..... | 222 | +| 9.2.6.2.3 | Message sequence chart..... | 222 | +| 9.2.7 | Session release initiated by IM-MGW..... | 223 | +| 9.2.7.1 | BICC..... | 223 | +| 9.2.7.1.1 | Session release in the CS network side..... | 223 | +| 9.2.7.1.2 | Session release in the IM CN subsystem side..... | 223 | +| 9.2.7.1.3 | Message sequence chart..... | 223 | +| 9.2.7.2 | ISUP..... | 224 | +| 9.2.7.2.1 | Session release in the CS network side..... | 224 | +| 9.2.7.2.2 | Session release in the IM CN subsystem side..... | 224 | +| 9.2.7.2.3 | Message sequence chart..... | 225 | +| 9.2.8 | Handling of RTP telephone events..... | 225 | +| 9.2.8.1 | Sending DTMF digits out-of-band to CS CN (BICC)..... | 226 | +| 9.2.8.2 | Sending and receiving DTMF digits inband to/from CS CN (ISUP or BICC)..... | 228 | +| 9.2.8.3 | Receiving DTMF digits out-of-band from CS CN (BICC)..... | 229 | +| 9.2.9 | Session hold initiated from IM CN subsystem..... | 230 | + +| | | | +|------------|---------------------------------------------------------------------------------------|-----| +| 9.2.10 | Session hold initiated from CS network..... | 232 | +| 9.2.11 | Explicit Congestion Notification Support..... | 234 | +| 9.2.11.1 | General..... | 234 | +| 9.2.11.1a | Incoming Call Interworking from SIP to ISUP/BICC at I-MGCF..... | 234 | +| 9.2.11.1b | Outgoing Call Interworking from ISUP/BICC to SIP at O-MGCF..... | 235 | +| 9.2.11.1c | Detection of ECN failures by IM-MGW..... | 235 | +| 9.2.11.2 | Message sequence chart..... | 235 | +| 9.2.12 | Interactive Connectivity Establishment Support..... | 236 | +| 9.2.12.1 | General..... | 236 | +| 9.2.12.2 | ICE lite..... | 236 | +| 9.2.12.3 | Full ICE..... | 237 | +| 9.2.12.4 | Procedures for Interactive Connectivity Establishment (ICE)..... | 239 | +| 9.2.12.4.1 | ICE lite..... | 239 | +| 9.2.12.4.2 | Full ICE..... | 240 | +| 9.2.12.4.3 | Connectivity check result notification (full ICE)..... | 241 | +| 9.2.12.4.4 | New peer reflexive candidate notification (full ICE)..... | 241 | +| 9.2.13 | Codec Parameters Handling..... | 242 | +| 9.2.13.1 | Handling of common codec parameters..... | 242 | +| 9.2.13.2 | Handling of EVS speech codec parameters when interworking with a different codec..... | 243 | +| 9.2.13.3 | Handling of EVS speech codec parameters when the EVS codec is used end-to-end..... | 252 | +| 9.2.14 | SDP Capability Negotiation (SDPCapNeg)..... | 260 | +| 9.2.15 | Rate adaptation for media endpoints..... | 260 | +| 9.3 | Mn Signalling procedures..... | 261 | +| 9.3.1 | Procedures related to terminations towards the IM CN Subsystem..... | 261 | +| 9.3.1.1 | Reserve IMS connection point..... | 262 | +| 9.3.1.2 | Configure IMS resources..... | 264 | +| 9.3.1.3 | Reserve IMS Connection point and configure remote resources..... | 265 | +| 9.3.1.4 | Release IMS termination..... | 267 | +| 9.3.1.5 | Detect IMS RTP Tel event..... | 268 | +| 9.3.1.6 | Notify IMS RTP Tel event..... | 268 | +| 9.3.1.7 | Void..... | 268 | +| 9.3.1.8 | Send IMS RTP Tel event..... | 268 | +| 9.3.1.9 | Stop IMS RTP Tel event..... | 268 | +| 9.3.1.10 | Termination heartbeat indication..... | 269 | +| 9.3.1.11 | IMS Bearer Released..... | 269 | +| 9.3.1.12 | End IMS RTP Tel event..... | 269 | +| 9.3.1.13 | IMS Send Tone..... | 269 | +| 9.3.1.14 | IMS Stop Tone..... | 269 | +| 9.3.1.15 | IMS Tone Completed..... | 269 | +| 9.3.1.16 | ECN Failure Indication..... | 270 | +| 9.3.1.17 | ICE Connectivity Check Result Notification..... | 270 | +| 9.3.1.18 | ICE New Peer Reflexive Candidate Notification..... | 271 | +| 9.3.2 | Procedures related to a termination towards an ISUP network..... | 271 | +| 9.3.2.1 | Reserve TDM circuit..... | 271 | +| 9.3.2.2 | Change TDM through-connection..... | 272 | +| 9.3.2.3 | Activate TDM voice-processing function..... | 272 | +| 9.3.2.4 | Send TDM tone..... | 272 | +| 9.3.2.5 | Stop TDM tone..... | 272 | +| 9.3.2.6 | Play TDM announcement..... | 272 | +| 9.3.2.7 | TDM announcement completed..... | 272 | +| 9.3.2.8 | Stop TDM announcement..... | 272 | +| 9.3.2.9 | Continuity check..... | 272 | +| 9.3.2.10 | Continuity check verify..... | 273 | +| 9.3.2.11 | Continuity check response..... | 273 | +| 9.3.2.12 | Release TDM termination..... | 274 | +| 9.3.2.13 | Termination Out-of-Service..... | 274 | +| 9.3.2.14 | Termination heartbeat indication..... | 274 | +| 9.3.2.15 | Bearer Released..... | 274 | +| 9.3.2.16 | TDM tone completed..... | 274 | + +| | | | +|-------|-------------------------------------------------------------------------|-----| +| 9.3.3 | Procedures related to a termination towards a BICC network..... | 275 | +| 9.3.4 | Non-call related procedures..... | 275 | +| 9.3.5 | Multiple IP Realms..... | 276 | +| 9.4 | Multimedia Priority Service (MPS) Support..... | 277 | +| 9.4.1 | General..... | 277 | +| 9.4.2 | IM-MGW Resource Congestion in ADD response, request is queued..... | 277 | +| 9.4.3 | IM-MGW Resource Congestion in ADD response, MGCF seizes new IM-MGW..... | 278 | +| 9.4.4 | IM-MGW Priority Resource Allocation..... | 278 | +| 9.4.5 | IM-MGW Priority User Data marking..... | 279 | + +| | | | +|-------------------------------|------------------|------------| +| Annex A (informative): | Void..... | 280 | +|-------------------------------|------------------|------------| + +| | | | +|-----------------------------|---------------------------------------------------------------------------------|------------| +| Annex B (normative): | Codec Negotiation between a BICC CS network and the IM CN subsystem..... | 281 | +|-----------------------------|---------------------------------------------------------------------------------|------------| + +| | | | +|------------|----------------------------------------------------------------------------------|-----| +| B.1 | Introduction..... | 281 | +| B.2 | Control plane interworking..... | 281 | +| B.2.1 | Incoming call interworking from SIP to BICC at I-MGCF..... | 281 | +| B.2.1.1 | Sending of IAM..... | 281 | +| B.2.1.2 | Sending of SDP answer..... | 281 | +| B.2.2 | Outgoing call interworking from BICC to SIP at O-MGCF..... | 282 | +| B.2.2.1 | Sending of INVITE..... | 282 | +| B.2.2.2 | Responding to serving node initiating codec negotiation..... | 282 | +| B.2.3 | Mid-call interworking from SIP to BICC at I-MGCF or O-MGCF..... | 282 | +| B.2.3.1 | Receipt of SDP offer..... | 282 | +| B.2.3.2 | Generating SDP answer..... | 283 | +| B.2.4 | Mid-call interworking from BICC to SIP at I-MGCF or O-MGCF..... | 283 | +| B.2.4.1 | Receipt of mid-call codec negotiation request..... | 283 | +| B.2.4.2 | Responding to serving node initiating mid-call codec negotiation..... | 283 | +| B.2.4.3 | Receipt of codec modification request..... | 284 | +| B.2.5 | Codec parameter translation between BICC CS network and the IM CN subsystem..... | 284 | +| B.2.5.1 | Codec parameters for 3GPP AMR-NB codecs..... | 285 | +| B.2.5.2 | Codec parameters for 3GPP AMR-WB codecs..... | 287 | +| B.2.5.3 | Codec parameters for 3GPP non-AMR codecs..... | 288 | +| B.2.5.4 | Codec parameters for ITU-T codecs..... | 288 | +| B.2.5.5 | Codec parameters for 3GPP EVS codec..... | 289 | +| B.3 | MGCF - IM-MGW interaction during interworking of codec negotiation..... | 291 | +| B.3.1 | Basic IM CN subsystem originated session..... | 291 | +| B.3.1.1 | BICC forward bearer establishment..... | 292 | +| B.3.1.1.1 | IM-MGW selection..... | 292 | +| B.3.1.1.2 | CS network side bearer establishment..... | 292 | +| B.3.1.1.3 | IM CN subsystem side session establishment..... | 292 | +| B.3.1.1.4 | Through-connection..... | 292 | +| B.3.1.1.5 | Codec handling..... | 293 | +| B.3.1.1.6 | Failure handling in MGCF..... | 293 | +| B.3.1.1.7 | Message sequence chart..... | 293 | +| B.3.2 | Basic CS network originated session..... | 295 | +| B.3.2.1 | BICC forward bearer establishment..... | 295 | +| B.3.2.1.1 | IM-MGW selection..... | 295 | +| B.3.2.1.2 | IM CN subsystem side termination reservation..... | 295 | +| B.3.2.1.3 | IM CN subsystem side session establishment..... | 295 | +| B.3.2.1.4 | CS network side bearer establishment..... | 295 | +| B.3.2.1.5 | Called party alerting..... | 296 | +| B.3.2.1.6 | Called party answer..... | 296 | +| B.3.2.1.7 | Through-Connection..... | 296 | +| B.3.2.1.8 | Codec handling..... | 296 | +| B.3.2.1.9 | Failure handling in MGCF..... | 296 | +| B.3.2.1.10 | Message sequence chart..... | 296 | +| B.3.3 | CS network initiated mid-call codec negotiation..... | 299 | + +| | | | +|-------------------------------|------------------------------------------------------------------------------------------------------------------------------------|------------| +| B.3.4 | IM CN subsystem initiated mid-call codec negotiation..... | 300 | +| Annex C (normative): | Interworking of CPC parameter..... | 301 | +| C.1 | Interworking SIP to ISUP..... | 301 | +| C.2 | Interworking ISUP to SIP..... | 302 | +| Annex D (informative): | Void..... | 303 | +| Annex E (normative): | Multimedia interworking between the IP Multimedia Core Network (CN) Subsystem (IMS) and Circuit Switched (CS) networks..... | 304 | +| E.1 | Basic Multimedia calls interworking between the IMS and CS Networks scenarios..... | 304 | +| E.2 | Control plane interworking..... | 305 | +| E.2.1 | General..... | 305 | +| E.2.2 | Functionalities required in the MGCF for multimedia calls support..... | 305 | +| E.2.3 | IM CN subsystem originated session..... | 305 | +| E.2.3.1 | Preconditions used at IMS side..... | 305 | +| E.2.3.1.1 | Interactions between H.245 or MONA and SIP/SDP..... | 305 | +| E.2.3.2 | Preconditions not used at IMS side..... | 307 | +| E.2.3.2.1 | Interactions between H.245 or MONA and SIP/SDP..... | 307 | +| E.2.3.3 | Fallback to speech at session establishment..... | 309 | +| E.2.4 | CS network originated session..... | 309 | +| E.2.4.1 | Interactions between SIP/SDP and H.245 or MONA..... | 309 | +| E.2.4.1.1 | Normal Call setup..... | 309 | +| E.2.4.1.2 | Call setup if multimedia call can not be recognized in an unambiguous manner..... | 311 | +| E.2.4.1.3 | Fallback to speech during call setup..... | 311 | +| E.2.4.2 | CS originated - IM CN transit - CS terminated..... | 312 | +| E.2.5 | Service change..... | 313 | +| E.2.5.2.1 | SCUDIF..... | 313 | +| E.2.5.2.1.0 | General..... | 313 | +| E.2.5.2.1.1 | IM CN subsystem originated change..... | 313 | +| E.2.5.2.1.1.1 | Change from multimedia to speech..... | 313 | +| E.2.5.2.1.1.2 | Change from speech to multimedia..... | 314 | +| E.2.5.2.1.2 | CS network originated change..... | 315 | +| E.2.5.2.1.2.1 | Change from multimedia to speech..... | 315 | +| E.2.5.2.1.2.2 | Change from speech to multimedia..... | 316 | +| E.2.5.2.2 | Non-SCUDIF case (ISUP or BICC without SCUDIF)..... | 316 | +| E.2.5.2.2.1 | Change from multimedia to audio..... | 316 | +| E.2.5.2.2.2 | Change from speech to multimedia..... | 317 | +| E.2.6 | Call release..... | 318 | +| E.2.6.1 | Call release initiated from the IM CN subsystem side..... | 318 | +| E.2.6.2 | Call release initiated from the CS network side..... | 319 | +| E.2.6.3 | Call release initiated from the interworking node..... | 319 | +| E.3 | User plane interworking..... | 320 | +| E.3.1 | Functionalities required in the IM-MGW for multimedia calls support..... | 320 | +| E.4 | MGCF and IM-MGW interactions..... | 320 | +| E.4.1 | Introduction..... | 320 | +| E.4.2 | Mn signalling interactions..... | 321 | +| E.4.2.1 | Introduction..... | 321 | +| E.4.2.2 | H.248 Context Model..... | 321 | +| E.4.2.3 | Transport of H.245 messages between the MGCF and IM-MGW..... | 321 | +| E.4.2.3.1 | General..... | 321 | +| E.4.2.3.2 | Transport from MGCF to IM-MGW..... | 322 | +| E.4.2.3.3 | Transport from IM-MGW to MGCF..... | 322 | +| E.4.2.4 | Call establishment procedure..... | 322 | +| E.4.2.5 | Handling of H.245 indication message..... | 325 | +| E.4.2.5.1 | Overview..... | 325 | + +| | | | +|-------------|-----------------------------------------------------------------------------------------------|-----| +| E.4.2.5.2 | Function Not Understood / Function Not Supported message..... | 325 | +| E.4.2.5.3 | User Input Indication message..... | 326 | +| E.4.2.6 | Handling of H.245 Command message..... | 326 | +| E.4.2.6.1 | Overview..... | 326 | +| E.4.2.6.2 | Flow control command..... | 326 | +| E.4.2.6.3 | End Session Command..... | 327 | +| E.4.2.6.4 | videoFastUpdatePicture..... | 327 | +| E.4.2.7 | Mn Signalling Interactions to support the Media Oriented Negotiation Acceleration (MONA)..... | 328 | +| E.4.2.7.1 | Overview..... | 328 | +| E.4.2.7.2 | Mn Interactions for MONA preference messages..... | 330 | +| E.4.2.7.3 | Mn Interactions for MONA MPCs..... | 332 | +| E.4.2.7.4 | Mn Interactions for MONA SPCs..... | 334 | +| E.4.2.7.4.1 | General..... | 334 | +| E.4.2.7.4.2 | Transport from MGCF to IM-MGW..... | 334 | +| E.4.2.7.4.3 | Transport from IM-MGW to MGCF..... | 335 | +| E.4.2.7.4.4 | Termination of SPC procedure..... | 336 | +| E.4.2.7.5 | Mn Interactions for fallback from MONA procedures to standard H.324 setup..... | 337 | +| E.4.2.8 | Interworking between RTCP messages and H.245 messages..... | 338 | +| E.4.2.8.1 | Overview..... | 338 | +| E.4.2.8.2 | IM CN subsystem originated RTCP messages..... | 338 | +| E.4.2.8.3 | CS network originated H.245 messages..... | 339 | +| E.4.3 | Mn Signalling procedures..... | 340 | +| E.4.3.1 | Overview..... | 340 | +| E.4.3.2 | Add Multiplex Termination..... | 341 | +| E.4.3.3 | Configure Multiplex Termination..... | 342 | +| E.4.3.4 | Signal H245 Message..... | 343 | +| E.4.3.5 | Notify H245 Message..... | 343 | +| E.4.3.6 | Notify MONA Preference Reception..... | 344 | +| E.4.3.7 | Notify MONA Preference Completed..... | 344 | +| E.4.3.8 | Signal SPC..... | 345 | +| E.4.3.9 | Notify SPC..... | 345 | +| E.4.3.10 | Notify MPC..... | 346 | +| E.4.3.11 | Notify Detection of Legacy Interworking..... | 346 | +| E.4.3.12 | Request RTCP-Interworking..... | 347 | +| E.4.3.13 | Notify RTCP-Interworking..... | 347 | +| E.4.3.14 | Signal-H.245-Interworking..... | 348 | +| E.4.3.15 | Stop MPC..... | 348 | +| E.4.3.16 | Stop SPC..... | 349 | +| E.4.3.17 | Stop MONA Negotiation..... | 350 | + +| | | | +|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------|------------| +| Annex F (normative): | PSTN XML Scheme..... | 350 | +| F.1 | Scope..... | 350 | +| F.2 | MIME type..... | 351 | +| F.3 | XML Schema definition..... | 351 | +| F.4 | IANA registration template..... | 356 | +| Annex G (informative): | Void..... | 358 | +| Annex H (normative): | Interworking of Originating Line Information (OLI) parameter
(network option)..... | 358 | +| H.1 | Interworking SIP to ISUP..... | 358 | +| H.2 | Interworking ISUP to SIP..... | 358 | +| Annex I (normative): | GTT interworking between the IP Multimedia Core Network (CN)
Subsystem (IMS) and Circuit Switched (CS) networks..... | 359 | +| I.1 | Overview of GTT interworking between the IMS and Circuit Switched (CS) networks..... | 359 | +| I.2 | Control plane interworking..... | 360 | +| I.2.1 | General..... | 360 | +| I.2.2 | Functionalities required in the MGCF for GTT calls support..... | 360 | +| I.2.3 | IM CN subsystem originated session..... | 360 | +| I.2.3.1 | Initial INVITE with an SDP offer including a text media line..... | 360 | +| I.2.4 | CS network originated session..... | 361 | +| I.2.4.1 | General..... | 361 | +| I.2.4.2 | Initial INVITE with an SDP offer including audio only..... | 361 | +| I.2.5 | Subsequent SDP offer/answer exchange adding text to an audio session..... | 362 | +| I.3 | User plane interworking..... | 362 | +| I.3.1 | Functionalities required in the IM-MGW for GTT support..... | 362 | +| I.3.2 | Monitoring of text/modem signals on the CS side..... | 362 | +| I.3.3 | Multiplexing between the CS and IMS streams..... | 363 | +| I.3.4 | Conversion between text/modem and Real-Time Text over RTP..... | 363 | +| I.4 | MGCF and IM-MGW interactions..... | 363 | +| I.4.1 | Introduction..... | 363 | +| I.4.2 | Mn signalling interactions..... | 364 | +| I.4.2.1 | Introduction..... | 364 | +| I.4.2.2 | H.248 Context Model..... | 364 | +| I.4.2.3 | Specific Mn signalling for GTT..... | 364 | +| I.4.2.4 | IM CN subsystem originated session between the MGCF and IM-MGW..... | 365 | +| I.4.2.4.1 | Initial INVITE with an SDP offer including Real-Time Text..... | 365 | +| I.4.2.5 | CS network originated session..... | 367 | +| I.4.2.5.1 | Initial INVITE with an SDP offer only including audio..... | 367 | +| I.4.3 | Mn Signalling procedures..... | 368 | +| I.4.3.1 | Overview..... | 368 | +| Annex J (informative): | Call Flow for Customized Alerting Tone (CAT) interworking
between CS network and IMS..... | 369 | +| J.1 | Introduction..... | 369 | +| J.2 | IMS CAT provided by the terminating IMS user using gateway model towards user served in CS
networks..... | 369 | +| J.2.1 | Callflow without using precondition mechanism..... | 370 | + +**Annex K (normative): T.38 interworking between the IP Multimedia Core Network (CN) Subsystem (IMS) and Circuit Switched (CS) networks.....372** + +K.1 General.....372 + +K.2 Recommend T.38 configuration.....372 + +K.3 Handling T.38 SDP attributes at the I-MGCF.....373 + +K.4 Handling T.38 SDP attributes at the O-MGCF.....374 + +K.5 Applicable T.38 SDP attributes at the Mn Interface.....375 + +**Annex L (normative): Interworking of called IN number and original called IN number parameters.....376** + +L.0 General.....376 + +L.1 Interworking SIP to ISUP.....376 + +L.2 Interworking ISUP to SIP.....377 + +Annex M (informative): Change history.....381 + +--- + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- Y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +--- + +# 1 Scope + +The present document specifies the principles of interworking between the 3GPP IM CN subsystem and BICC/ISUP based legacy CS networks, in order to support IM basic voice, data and multimedia calls. + +The present document addresses the areas of control and user plane interworking between the IM CN subsystem and CS networks through the network functions, which include the MGCF and IM-MGW. For the specification of control plane interworking, areas such as the interworking between SIP and BICC or ISUP are detailed in terms of the processes and protocol mappings required for the support of both IM originated and terminated voice and multimedia calls. + +Other areas addressed encompass the transport protocol and signalling issues for negotiation and mapping of bearer capabilities and QoS information. + +The present document specifies the interworking between 3GPP profile of SIP (as detailed according to 3GPP TS 24.229 [9]) and BICC or ISUP, as specified in ITU-T Recommendations Q.1902.1 to Q.1902.6 [30] and ITU-T Q761 to Q764 [4] respectively. + +The present document also specifies the interworking between circuit switched multimedia telephony service, as described in 3GPP TS 26.110 [78] 3GPP TS 26.111 [79], and ITU-T Recommendation H.324 [81] and packet switched multimedia services, as described in 3GPP TS 26.114 [104], in particular and the interworking between the 3GPP profile of SIP and the inband control protocols for multimedia communication as specified in ITU-T Recommendations H.245 [82] and H.324 Annex K [81]. + +The present document addresses two interworking scenarios with respect to the properties of the CS network: + +- The CS network does not use any 3GPP specific additions. +- The CS network uses 3GPP specific additions. + +--- + +# 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] ITU-T Recommendation G.711 (11/88): "Pulse Code Modulation (PCM) of voice frequencies". +- [2] ITU-T Recommendation H.248.1 (05/02): "Gateway control protocol: Version 2". +- [3] ITU-T Recommendation Q.701 (03/93), Q.702 (11/88), Q.703 (07/96), Q.704 (07/96), Q.705 (03/93), Q.706 (03/93), Q.707 (11/88), Q.708 (03/99), Q.709 (03/93): "Functional description of the message transfer part (MTP) of Signalling System No. 7". +- [4] ITU-T Recommendations Q.761 to Q.764 (12/99): "Specifications of Signalling System No.7 ISDN User Part (ISUP)". +- [5] Void. +- [6] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [7] Void. +- [8] 3GPP TS 24.228: "Signalling flows for the IP multimedia call control based on SIP and SDP". + +- [9] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP". +- [10] 3GPP TS 23.002: "Network Architecture". +- [11] 3GPP TS 22.228: "Service requirements for the IP Multimedia Core Network Subsystem". +- [12] 3GPP TS 23.228: "IP Multimedia subsystem (IMS)". +- [13] Void. +- [14] 3GPP TS 29.205: "Application of Q.1900 series to Bearer Independent CS Network architecture; Stage 3". +- [15] 3GPP TS 29.332: "Media Gateway Control Function (MGCF) - IM-Media Gateway (IM-MGW) interface, Stage 3". +- [16] IETF RFC 791: "Internet Protocol". +- [17] IETF RFC 768: "User Datagram Protocol". +- [18] IETF RFC 2960: "Stream Control Transmission Protocol". +- [19] IETF RFC 3261: "SIP: Session Initiation Protocol". +- [20] 3GPP TS 29.202: "Signalling System No. 7 (SS7) signalling transport in core network; Stage 3". +- [21] IETF RFC 2474: "Definition of the Differentiated Services Field (DS Field) in the Ipv4 and Ipv6 Headers". +- [22] IETF RFC 2475: "An Architecture for Differentiated Services". +- [23] IETF RFC 4867 : "RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs". +- [24] IETF RFC 793: "Transmission Control Protocol". +- [25] 3GPP TS 29.414: "Core network Nb data transport and transport signalling". +- [26] 3GPP TS 29.415: "Core network Nb interface user plane protocols". +- [27] 3GPP TS 23.205: "Bearer-independent circuit-switched core network; Stage 2". +- [28] Void. +- [29] ITU-T Recommendation Q.2150.1: "Signalling transport converter on MTP3 and MTP3b". +- [30] ITU-T Recommendations Q.1902.1 to Q.1902.6 (07/01): "Bearer Independent Call Control". +- [31] Void. +- [32] Void. +- [33] Void. +- [34] Void. +- [35] ITU-T Recommendation Q.765.5: "Signalling system No. 7 - Application transport mechanism: Bearer Independent Call Control (BICC)". +- [36] IETF RFC 3264: "An Offer/Answer Model with the Session Description Protocol (SDP)". +- [37] IETF RFC 3312: "Integration of Resource Management and Session Initiation Protocol (SIP)". +- [38] ITU-T Recommendation Q.850 (05/1998) including Amendment 1 (07/2001): "Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part". + +- [39] IETF RFC 2460: "Internet Protocol, Version 6 (Ipv6) Specification". +- [40] IETF RFC 3323: "A Privacy Mechanism for the Session Initiation Protocol (SIP)". +- [41] IETF RFC 3325: "Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks". +- [42] ITU-T Recommendation Q.730 (12/99), Q.731.1 (07/96), Q.731.3 (03/93), Q.731.4 (03/93), Q.731.5 (03/93), Q.731.6 (03/93), Q.731.7 (06/97), Q.731.8 (02/92), Q.732.2-5 (12/99), Q.732.7 (07/96), Q.733.1 (02/92), Q.733.2 (03/93), Q.733.3 (06/97), Q.733.4 (03/93), Q.733.5 (12/99), Q.734.1 (03/93), Q.734.2 (07/96), Q.735.1 (03/93), Q.735.3 (03/93), Q.735.6 (07/93), Q.736.1 (10/95), Q.736.3 (10/95), Q.737.1 (06/97): "ISDN user part supplementary services". +- [43] ITU-T Recommendation I.363.5 (1996): "B-ISDN ATM Adaptation Layer specification: Type 5 AAL". +- [44] ITU-T Recommendation Q.2110 (1994): "B-ISDN ATM adaptation layer - Service Specific Connection Oriented Protocol (SSCOP)". +- [45] ITU-T Recommendation Q.2140 (1995): "B-ISDN ATM adaptation layer - Service specific coordination function for signalling at the network node interface (SSCF AT NNI)". +- [46] ITU-T Recommendation Q.2210 (1996): "Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140". +- [47] 3GPP TS 23.221: "Architectural requirements". +- [48] ITU-T Recommendation E.164 (05/1997): "The international public telecommunication numbering plan". +- [49] ITU-T Recommendation Q.1912.5 (03/04): "Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control Protocol or ISDN User Part". +- [50] 3GPP TS 26.102: "Adaptive Multi-Rate (AMR) speech codec; Interface to Iu and Uu". +- [51] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications". +- [52] IETF RFC 3551: "RTP Profile for Audio and Video Conferences with Minimal Control". +- [53] IETF RFC 3555: "MIME Type Registration of RTP Payload Formats". +- [54] IETF RFC 3262: "Reliability of provisional responses". +- [55] IETF RFC 3311: "SIP UPDATE method". +- [56] IETF RFC 4566: "SDP: Session Description Protocol". +- [57] 3GPP TS 26.103: "Speech Codec List for GSM and UMTS". +- [58] 3GPP TS 28.062: "Inband Tandem Free Operation (TFO) of speech codecs". +- [59] IETF RFC 3556: "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) bandwidth". +- [60] 3GPP TS 24.604: "Communication Diversion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [61] 3GPP TS 24.605: "Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [62] 3GPP TS 24.606: "Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". + +- [63] 3GPP TS 24.607: "Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [64] 3GPP TS 24.608: "Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [65] 3GPP TS 24.610: "Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [66] Void. +- [67] 3GPP TS 24.611: "Anonymous Communication Rejection (ACR) and Communication Barring (CB) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [68] Void. +- [69] IETF RFC 4040: "RTP Payload Format for a 64 kbit/s Transparent Call". +- [70] ETSI EN 300 356-1 (V4.2.1): "Integrated Services Digital Network (ISDN); Signalling System No.7 (SS7); ISDN User Part (ISUP) version 4 for the international interface; Part 1: Basic services [ITU-T Recommendations Q.761 to Q.764 (1999) modified]". +- [71] ETSI EN 300 356-21 (V4.2.1): "Integrated Services Digital Network (ISDN); Signalling System No.7 (SS7); ISDN User Part (ISUP) version 4 for the international interface; Part 21: Anonymous Call Rejection (ACR) supplementary service". +- [72] ITU-T Recommendation T.38 (09/2010): "Procedures for real-time Group 3 facsimile communication over IP networks". +- [73] IETF RFC 3362: "Real-time Facsimile (T.38) - image/t38 MIME Sub-type Registration". +- [74] 3GPP TS 23.003: "Numbering, addressing and identification". +- [75] IETF RFC 3515: "The Session Initiation Protocol (SIP) REFER method". +- [76] Void. +- [77] IETF RFC 5079: "Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)". +- [78] 3GPP TS 26.110: "Codec for circuit switched multimedia telephony service; General description". +- [79] 3GPP TS 26.111: "Codec for Circuit switched Multimedia Telephony Service; Modifications to H.324". +- [80] Void. +- [81] ITU-T Recommendation H.324 (04/09): "Terminal for low bitrate multimedia communication". +- [82] ITU-T Recommendation H.245: "Control protocol for multimedia communication". +- [83] ITU-T Recommendation H.261 (03/93): "Video codec for audiovisual services at p x 64 kbit/s". +- [84] ITU-T Recommendation H.263 (01/05): "Video coding for low bitrate communication". +- [85] Void. +- [86] Void. +- [87] Void. +- [88] 3GPP TS 24.173: "IMS Multimedia Telephony Communication Service and Supplementary Services, stage 3". + +- [89] IETF RFC 5009: "Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media". +- [90] IETF RFC 2663: "IP Network Address Translator (NAT) Terminology and Considerations". +- [91] IETF RFC 7044: "An extension to the Session Initiation Protocol (SIP) for Request History Information". +- [92] ITU-T Recommendation Q.769.1 (12/99): "Signalling system No. 7 - ISDN user part enhancements for the support of number portability". +- [93] IETF RFC 4694: "Number portability parameters for the "tel" URI". +- [94] Void. +- [95] Void. +- [96] ETSI EN 300 403-1 (V1.3.2): "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control; Part 1: Protocol specification [ITU-T Recommendation Q.931 (1993), modified]". +- [97] IETF RFC 3966: "The tel URI for Telephone Numbers". +- [98] Void. +- [99] IETF RFC 7433: "A Mechanism for Transporting User-to-User Call Control Information in SIP". +- [99A] IETF RFC 7434: "Interworking ISDN Call Control User Information with SIP". +- [100] IETF RFC 4575: "A Session Initiation Protocol (SIP) Event Package for Conference State". +- [101] 3GPP TS 24.654: "Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol Specification". +- [102] 3GPP TS 24.616: "Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [103] 3GPP TS 23.014: "Technical Specification Group Core Network; Support of Dual Tone Multi-Frequency (DTMF) signalling". +- [104] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction". +- [105] IETF RFC 4733: "RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals". +- [106] IETF RFC 6910: "Completion of Calls for the Session Initiation Protocol (SIP)". +- [107] IETF RFC 7462: "URNs for the Alert-Info Header Field of the Session Initiation Protocol (SIP)". +- [108] IETF RFC 4715: "The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI". +- [109] IETF RFC 4585: "Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)". +- [110] IETF RFC 5104: "Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF)". +- [111] 3GPP TS 24.615: "Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem, Protocol Specification". +- [112] 3GPP TS 24.642: "Completion of Communications to Busy Subscriber (CCBS) Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". + +- [113] IETF RFC 4458: "Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR)". +- [114] IETF RFC 5993: "RTP Payload format for Global System for Mobile Communications Half Rate (GSM-HR)". +- [115] IETF RFC 6432: "Carrying Q.850 Codes in Reason Header Fields in SIP (Session Initiation Protocol) Responses". +- [116] IETF RFC 3326: "The Reason Header Field for the Session Initiation Protocol (SIP)". +- [117] ANSI Standard ATIS-1000113.2005(R2010) (07/2005): "Signalling System No. 7 (SS7) - Integrated Services Digital Network (ISDN) User Part". +- [118] 3GPP TS 23.237: "IP Multimedia subsystem (IMS) Service Continuity; Stage 2". +- [119] IETF RFC 5626: "Managing Client Initiated Connections in the Session Initiation Protocol (SIP)". +- [120] IETF RFC 7254: "A Uniform Resource Name Namespace for the Global System for Mobile Communications Association (GSMA) and the International Mobile station Equipment Identity (IMEI)". +- [121] 3GPP TS 23.172: "Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2". +- [122] 3GPP TS 23.226: "Global Text Telephony (GTT); stage 2". +- [123] ITU-T Recommendation T.140 (02/98): "Text conversation presentation protocol". +- [124] IETF RFC 4103: "RTP Payload for Text Conversation". +- [125] ITU-T Recommendation V.18 (11/00): "Operational and interworking requirements for DCEs operating in the text telephone mode" including V.18 (2000) Amendment 1 (11/02): "Harmonization with ANSI TIA/EIA-825 (2000) text phones". +- [126] 3GPP TS 26.226: "Cellular text telephone modem; General description". +- [127] Void. +- [128] Void. +- [129] IETF RFC 3168: "The Addition of Explicit Congestion Notification (ECN) to IP". +- [130] IETF RFC 6679: "Explicit Congestion Notification (ECN) for RTP over UDP". +- [131] IETF RFC 3959: "The Early Session Disposition Type for the Session Initiation Protocol (SIP)". +- [132] 3GPP TS 24.182: "IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT); Protocol specification". +- [133] IETF RFC 6086: "Session Initiation Protocol (SIP) INFO Method and Package Framework". +- [134] 3GPP TS 23.088: "Call Barring (CB) Supplementary Services; Stage 2". +- [135] IETF RFC 3840: "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)". +- [136] 3GPP TS 22.153: "Multimedia Priority Service". +- [137] IETF RFC 3023: "XML Media Types". +- [138] IETF RFC 6665: "SIP-Specific Event Notification". +- [139] IETF RFC 7090: "Public Safety Answering Point (PSAP) Callback". + +- [141] 3GPP TS 24.292: "IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS); Stage 3". +- [142] IETF RFC 6809: "Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)". +- [143] IETF RFC 5245: "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols". +- [144] IETF RFC 5389: "Session Traversal Utilities for NAT (STUN)". +- [145] 3GPP TS 23.334: "IMS Application Level Gateway (IMS-ALG) - IMS Access Gateway (IMS-AGW) interface: Procedures Descriptions". +- [146] 3GPP TS 26.441: "Codec for Enhanced Voice Services (EVS); General Overview". +- [147] 3GPP TS 26.445: "Codec for Enhanced Voice Services (EVS); Detailed Algorithmic Description". +- [148] IETF RFC 8119: "SIP "cause" URI Parameter for Service Number Translation". +- [149] ITU-T Recommendation Q.931 (05/98): "ISDN user-network interface layer 3 specification for basic call control". +- [150] IETF RFC 5939: "Session Description Protocol (SDP) Capability Negotiation". +- [151] 3GPP TS 23.333: "Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface: Procedures Descriptions". +- [152] 3GPP TS 26.453: "Codec for Enhanced Voice Services (EVS); Speech codec frame structure". +- [153] IETF RFC 8224: "Authenticated Identity Management in the Session Initiation Protocol (SIP)". +- [154] IETF RFC 8197: "A SIP Response Code for Unwanted Calls". +- [155] IETF RFC 8606: "ISDN User Part (ISUP) Cause Location Parameter for the SIP Reason Header Field". + +--- + +## 3 Definitions and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [6], ITU-T Recommendation E.164 [48] and the following apply: + +**Carrier textphone mode:** a mode for text communication, where continuous signals (i.e. a carrier tone) are present on the connection irrespective of whether text is being exchanged or not. + +**Carrierless textphone mode:** a mode for text communication, where signals are only present on the connection when text is being exchanged. E.g.: Baudot + +**SS7 signalling function:** function in the CS network, which has the capabilities to transport the SS7 MTP-User parts ISUP and BICC+STCmtp + +**SIP signalling function:** function in the IM CN subsystem, which has the capabilities to transport SIP + +**Incoming or Outgoing:** used in the present document to indicate the direction of a call (not signalling information) with respect to a reference point. + +**Incoming MGCF (I-MGCF):** entity that terminates incoming SIP calls from the IMS side and originates outgoing calls towards the CS side using the BICC or ISUP protocols. + +**Outgoing Interworking Unit (O-MGCF)**: entity that terminates incoming BICC or ISUP calls from the CS side and originates outgoing calls towards the IMS using SIP. + +**Root Termination**: refers to Media Gateway as an entity in itself, rather than a Termination within it. A special TerminationID, "Root" is reserved for this purpose. See ITU-T Recommendation H.248.1. [2] + +**Signalling Transport Converter (STC)**: function that converts the services provided by a particular Signalling Transport to the services required by the Generic Signalling Transport Service. + +**STCmtp**: Signalling Transport Converter on MTP. See ITU-T Recommendation Q.2150.1 [29]. + +**BICC+STCmtp**: this terminology means that BICC signalling always needs to be used on top of STCmtp sublayer. + +**diverting URI**: the URI of the node by which the existing communication was last diverted/forwarded. + +**diverted-to URI**: the URI to which the existing communication is diverted/forwarded to. + +**ICE lite**: The lite implementation of the Interactive Connectivity Establishment (ICE) specified in IETF RFC 5245 [143]. + +**Full ICE**: The full implementation of the Interactive Connectivity Establishment (ICE) specified in IETF RFC 5245 [143]. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations as defined in TR 21.905 [6] and the following apply: + +| | | +|-----------|-------------------------------------------------------------------------------| +| 3PTY | Three Party | +| AAL1 | ATM Adaptation Layer type 1 | +| ACR | Anonymous Call Rejection | +| AMR | Adaptive Multi-Rate | +| AMR-WB | Adaptive Multi-Rate - WideBand | +| AMR-WB IO | Adaptive Multi-Rate - WideBand Inter-operable Mode, included in the EVS codec | +| ANM | Answer Message | +| APM | Application Transport Message | +| APP | APplication-defined RTCP packet | +| APRI | Address Presentation Restriction Indicator | +| ATP | Access Transport Parameter | +| BC | Bearer Capability | +| BCI | Backward Call Indicators | +| BGCF | Breakout Gateway Control Function | +| BICC | Bearer Independent Call Control | +| CAT | Customized Alerting Tones | +| CB | Communication Barring | +| CCNR | Call Completion on No Reply | +| CCSS | Call Completion Service Set-up | +| Cda | Call Deflection Alerting | +| Cdi | Call Deflection Immediate | +| CDIV | Communication Diversion | +| CdPN | Called Party Number | +| CFB | Call Forwarding Busy | +| CFNR | Call Forwarding No Reply | +| CGB | Circuit Group Blocking | +| CgPN | Calling Party Number | +| CIC | Carrier Identification Code | +| CMR | Codec Mode Request | +| CON | Connect | +| CONF | Conference | +| COT | Continuity | +| CPC | Calling Party's Category | +| CPG | Call ProGress message | + +| | | +|-----------|----------------------------------------------------------------------------------| +| CSI | Carrier Selection Information | +| DSCP | DiffServ Code Point | +| DTX | Discontinuous Transmission | +| ECN | Explicit Congestion Notification | +| ECN-CE | ECN Congestion Experienced | +| EVS | Enhanced Voice Services | +| EVS-CMR | Codec Mode Request for EVS | +| FAC | Facility | +| FQC | Frame Quality Classification | +| GN | Generic Number | +| GRS | Group Reset | +| GVNS | Global Virtual Network Service | +| H/W | Hardware | +| ICE | Interactive Connectivity Establishment | +| ICS | IMS Centralized Services | +| IDR | Identification Request | +| IEPS | International Emergency Preference Scheme | +| I-MGCF | Incoming MGCF | +| IM-MGW | IP Multimedia Media Gateway Function | +| INF | Information | +| INR | Information Request | +| IRS | Identification Response | +| ITCC | International Telecommunication Charge Card | +| ITU-T | International Telecommunication Union - Telecommunication Standardization Sector | +| MCID | Malicious Communication Identification | +| M3UA | MTP-L3 User Adaptation layer | +| MLPP | Multi-Level Precedence and Pre-emption | +| MONA | Media Orientation Negotiation Acceleration | +| MPC | Media Preconfigured Channel | +| MPS | Multimedia Priority Service | +| MRFP | Media Resource Function Processor | +| MSN | Multiple Subscriber Number | +| MSU | Message Signalling Unit | +| MWI | Message Waiting Indication | +| NOA | Nature Of Address indicator | +| NPDI | Number Portability Database Dip Indicator | +| OIP | Originating Identification Presentation | +| OIR | Originating Identification Restriction | +| OLI | Originating Line Information | +| O-MGCF | Outgoing MGCF | +| PI | Progress Indicator | +| PIDF | Presence Information Data Format | +| PSAP | Public Safety Answering Point | +| REV | Reverse Charging | +| RLC | Release Complete | +| RSC | Reset Circuit | +| RTCP | RTP Control Protocol | +| RTP | Real-time Transport Protocol | +| SAM | Subsequent Address Message | +| SCTP | Stream Control Transmission Protocol | +| SDPCapNeg | SDP Capability Negotiation | +| SGW | Signalling Gateway | +| SPC | Signalling Preconfigured Channel | +| ST | Sending Terminated | +| STUN | Session Traversal Utilities for NAT | +| TCAP | Transaction Capabilities Application Part | +| TDM | Time Division Multiplex | +| TIP | Terminating Identification Presentation | +| TIR | Terminating Identification Restriction | + +| | | +|--------|-----------------------------------------------------------| +| TMR | Transmission Medium Requirement | +| TMU | Transmission Medium Used | +| TNL | Transport Network Layer | +| TNS | Transit Network Selection | +| TP | Terminal Portability | +| UA | User Agent | +| UAC | User Agent Client | +| UDI | Unrestricted Digital Information | +| UDI-TA | Unrestricted Digital Information with Tones/Announcements | +| UID | User Interactive Dialog | +| URI | Uniform Resource Identifier | +| USI | User Service Information | +| UUS | User-to-User Signalling | +| XML | eXtensible Markup Language | + +--- + +## 4 General + +### 4.1 General interworking overview + +The IM CN subsystem shall interwork with BICC and ISUP based legacy CS networks, e.g. PSTN, ISDN, CS PLMNs, in order to provide the ability to support basic voice calls (see 3GPP TS 22.228 [11]), between a UE located in the IM CN subsystem and user equipment located in a CS network. + +For the ability to support the delivery of basic voice calls between the IM CN subsystem and CS networks, basic protocol interworking between SIP (as specified in 3GPP TS 24.229 [9]) and BICC or ISUP (as specified in ITU-T Recommendations Q.1902.1-6 [30] and ITU-T Recommendations Q.761 to Q.764 [4] respectively) has to occur at a control plane level, in order that call setup, call maintenance and call release procedures can be supported. The MGCF shall provide this protocol mapping functionality within the IM CN subsystem. + +User plane interworking between the IM CN subsystem and CS network bearers (e.g. 64k TDM, ATM/AAL2 circuit or IP bearer) are supported by the functions within the IM-MGW. The IM-MGW resides in the IM CN subsystem and shall provide the bearer channel interconnection. The MGCF shall provide the call control to bearer setup association. + +The IM CN subsystem shall interwork, at the control and user plane, with BICC and ISUP based legacy CS networks. The support of supplementary services shall be as defined in 3GPP TS 22.228 [11]. The MGCF and IM-MGW shall support the interworking of the IM CN subsystem to an external ISUP based CS network. They may also support interworking to a BICC based CS network where no 3GPP specific extension is applied. The MGCF and the IM-MGW may also support interworking to a BICC based CS network where 3GPP specific extensions in accordance with 3GPP TS 29.205 [14] are applied. + +--- + +## 5 Network characteristics + +### 5.1 Key characteristics of ISUP/BICC based CS networks + +This signalling interface to a PSTN is either based on BICC Capability Set 2 as specified in ITU-T Recommendations Q.1902.1 to Q.1902.6 [30], or on ISUP (see ITU-T Recommendations Q.761 to Q.764 [4]). + +The interface towards a CS-PLMN may either be one of the interfaces mentioned in the paragraph above or a signalling interface based on BICC with 3GPP specific extensions, as specified for the 3GPP Nc interface in 3GPP TS 29.205 [14], and the IM-MGW may support the 3GPP Nb interface, as specified in 3GPP TS 29.414 [25] and 3GPP TS 29.415 [26]. If the 3GPP Nc interface is applied as signalling interface, the 3GPP Nb interface is used as user plane interface and the Nb UP Framing protocol is applied. + +### 5.2 Key characteristics of IM CN subsystem + +The IM CN subsystem uses SIP to manage IP multimedia sessions in a 3GPP environment, it also uses Ipv6, as defined in RFC 2460 [39], as the transport mechanism for both SIP session signalling and media transport. The 3GPP profile of + +SIP defining the usage of SIP within the IM CN subsystem is specified in 3GPP TS 24.229 [9]. Example callflows are provided in 3GPP TS 24.228 [8]. + +## 6 Interworking with CS networks + +### 6.1 Interworking reference model + +Figure 1 details the reference model required to support interworking between the 3GPP IM CN subsystem and CS networks for IM basic voice calls. + + + +Figure 1: IM CN subsystem to CS network logical interworking reference model. The diagram shows the logical interworking between the IM CN subsystem and a CS network. On the left, BGCF and CSCF are connected to MGCF via reference points Mj and Mg respectively. MGCF is connected to SGW via BICC/ISUP over SCTP/IP. SGW is connected to the CS network via BICC/ISUP over MTP. MGCF is also connected to IM-MGW via reference point Mn. IM-MGW is connected to the CS network via CS channels (e.g., PCM) and to other network entities (Note 3) via reference point Mb. A legend indicates that solid lines represent the User Plane and dotted lines represent the Control Plane. + +- NOTE 1: The logical split of the signalling and bearer path between the CS network and the IM CN subsystem is as shown, however the signalling and bearer may be logically directly connected to the IM-MGW. +- NOTE 2: The SGW may be implemented as a stand-alone entity or it may be located in another entity either in the CS network or the IM-MGW. The implementation options are not discussed in the present document. +- NOTE 3: The IM-MGW may be connected via the Mb to various network entities, such as a UE (via a GTP Tunnel to a GGSN), an MRFP, or an application server. +- NOTE 4: A SGW function is not required for certain signalling transports, where M3UA+SCTP+IP is used in CS network and IM-MGCF. + +**Figure 1: IM CN subsystem to CS network logical interworking reference model** + +#### 6.1.1 Interworking reference points and interfaces + +The reference points and network interfaces shown in figure 1 are as described: + +Protocol for Mg reference point: The single call control protocol applied across the Mg reference point (i.e. between CSCF and MGCF) will be based on the 3GPP profile of SIP as defined in accordance with 3GPP TS 24.229 [9]. + +Protocol for Mn reference point: The Mn reference point describes the interfaces between the MGCF and IM-MGW, and has the properties as detailed in 3GPP TS 29.332 [15]. + +Protocol for Mj reference point: The single call control protocol applied across the Mj reference point (i.e. between BGCF and MGCF) will be based on the 3GPP profile of SIP as defined in accordance with 3GPP TS 24.229 [9]. + +Protocol for Mb reference point: The Mb reference point is defined in accordance with 3GPP TS 23.002 [10] and is IPv6 based. + +#### 6.1.2 Interworking functional entities + +##### 6.1.2.1 Signalling Gateway Function (SGW) + +This component performs the call related signalling conversion to or from BICC/ISUP based MTP transport networks to BICC/ISUP based SCTP/IP transport networks, and forwards the converted signalling to or from the MGCF. The functionality within SGW shall be in accordance with 3GPP TS 23.002 [10]. + +### 6.1.2.2 Media Gateway Control Function (MGCF) + +This is the component within the IM CN subsystem, which controls the IM-MGW, and also performs SIP to BICC or SIP to ISUP call related signalling interworking. + +The functionality defined within MGCF shall be defined in accordance with 3GPP TS 23.002 [10]. + +### 6.1.2.3 IP Multimedia - Media Gateway Function (IM-MGW) + +This is the component within the IM CN subsystem, which provides the interface between the PS domain and the CS domain, and it shall support the functions as defined in accordance with 3GPP TS 23.002 [10]. + +## 6.2 Control plane interworking model + +Within the IM CN subsystem, the 3GPP profile of SIP is used to originate and terminate IM sessions to and from the UE. + +External CS networks use BICC or ISUP to originate and terminate voice calls to and from the IM CN subsystem. + +Therefore, in order to provide the required interworking to enable inter network session control, the control plane protocols shall be interworked within the IM CN subsystem. This function is performed within the MGCF (see clause 6.1.2). + +## 6.3 User plane interworking model + +Within the IM CN subsystem, IPv6, and framing protocols such as RTP, are used to transport media packets to and from the IM CN subsystem entity like UE or MRFP. + +External legacy CS networks use circuit switched bearer channels like TDM circuits (e.g. 64 kbits PCM), ATM/AAL2 circuit or IP bearers to carry encoded voice frames, to and from the IM CN subsystem. + +Other CN networks use ATM/AAL 1 or AAL 2 or IP as a backbone, with different framing protocols. + +Therefore, in order to provide the required interworking to enable media data exchange, the user plane protocols shall be translated within the IM CN subsystem. This function is performed within the IM-MGW (see clause 6.1.2). + +--- + +# 7 Control plane interworking + +Signalling from CS networks to or from IM CN subsystem, where the associated supported signalling protocols are SS7/M3UA+ SCTP+IP and M3UA+SCTP+IP respectively, requires a level of interworking between the nodes across the Control Plane, i.e. the SS7 signalling function, SGW (if applicable), MGCF and SIP signalling function. This interworking is required in order to provide a seamless support of a user part, i.e. SIP and BICC+STCmtp or SIP and ISUP. + +The transport of SS7 signalling protocol messages of any protocol layer that is identified by MTP level 3, in SS7 terms, as a user part (MTP3-user) shall be accomplished in accordance with the protocol architecture defined in the following clauses. For the present document these protocol layers include, but are not limited to, Bearer Independent Call Control (BICC)+STCmtp and ISDN User Part (ISUP). + +## 7.1 General + +The following clauses define the signalling interworking between the Bearer Independent Call Control (BICC) or ISDN User Part (ISUP) protocols and Session Initiation Protocol (SIP) with its associated Session Description Protocol (SDP) at a MGCF. The MGCF shall act as a Type A exchange (ITU-T Recommendation Q.764 [4]) for the purposes of ISUP and BICC Compatibility procedures. The services that can be supported through the use of the signalling interworking are limited to the services that are supported by BICC or ISUP and SIP based network domains. + +BICC is the call control protocol used between Nodes in a network that incorporates separate call and bearer control. The BICC/ISUP capabilities or signalling information defined for national use is outside the scope of the present document. It does not imply interworking for national-specific capabilities is not feasible. + +The capabilities of SIP and SDP that are interworked with BICC or ISUP are defined in 3GPP TS 24.229 [9]. + +Services that are common in SIP and BICC or ISUP network domains will seamlessly interwork by using the function of the MGCF. The MGCF will originate and/or terminate services or capabilities that do not interwork seamlessly across domains according to the relevant protocol recommendation or specification. + +How to create a SIP component which is not mapped from BICC or ISUP parameter(s) (e.g., the SIP domain name in the SIP URI) is outside the scope of this specification. + +Table 1 lists the services seamlessly interworked and therefore within the scope of the present document. + +**Table 1: Interworking Capabilities between BICC/ISUP and SIP profile for 3GPP** + +| Service | +|------------------------------------------------------------------| +| Speech/3.1 kHz audio | +| CS data Calls (optional) | +| En bloc address signalling | +| Overlap address signalling from the CS side towards the IMS | +| Out of band transport of DTMF tones and information. (BICC only) | +| Inband transport of DTMF tones and information. (BICC and ISUP) | +| Direct-Dialling-In (DDI) | +| Multiple Subscriber Number (MSN) | +| Calling Line Identification Presentation (CLIP) | +| Calling Line Identification Restriction (CLIR) | +| Connected line presentation (COLP) | +| Connected line restriction (COLR) | +| Carrier routeing | + +## 7.2 Interworking between CS networks supporting ISUP and the IM CN subsystem + +The control plane between CS networks supporting ISUP and the IM CN subsystem supporting SIP, where the underlying network is SS7 and IP respectively is as shown in figure 2. + + + +The diagram illustrates the control plane interworking between CS networks and the IM CN subsystem. It consists of four main functional blocks connected in a chain: + +- SS7 signalling function:** Contains layers ISUP, MTP3, MTP2, and L1. It connects to the Signalling gateway function via an SS7 link at the L1 layer. +- Signalling gateway function:** Contains layers MTP3, MTP2, L1, M3UA, SCTP, and IP. It receives SS7 from the SS7 signalling function and forwards ISUP (via M3UA) and IP (via SCTP) to the Media gateway control function. +- Media gateway control function:** Contains layers ISUP, SIP, M3UA, SCTP, and IP. It receives ISUP and IP from the Signalling gateway function and forwards SIP and IP to the SIP signalling function. +- SIP signalling function:** Contains layers SIP, TCP/UDP/SCTP, and IP. It receives SIP and IP from the Media gateway control function. + +Key connections: + +- An **ISUP** signal flows from the SS7 signalling function (ISUP layer) through the Signalling gateway function (M3UA layer) to the Media gateway control function (ISUP layer). +- An **SS7** signal flows from the SS7 signalling function (L1 layer) to the Signalling gateway function (L1 layer). +- An **IP** signal flows from the Signalling gateway function (IP layer) to the Media gateway control function (IP layer). +- A **SIP** signal flows from the Media gateway control function (SIP layer) to the SIP signalling function (SIP layer). +- An **IP** signal flows from the Media gateway control function (IP layer) to the SIP signalling function (IP layer). + +Figure 2: Control plane interworking between CS networks supporting ISUP and the IM CN subsystem. The diagram shows four main components: SS7 signalling function, Signalling gateway function, Media gateway control function, and SIP signalling function. The SS7 signalling function contains ISUP, MTP3, MTP2, and L1 layers. The Signalling gateway function contains MTP3, MTP2, L1, M3UA, SCTP, and IP layers. The Media gateway control function contains ISUP, SIP, M3UA, SCTP, and IP layers. The SIP signalling function contains SIP, TCP/UDP/SCTP, and IP layers. Arrows indicate the flow of ISUP, SS7, IP, and SIP signals between these functions. + +**Figure 2: Control plane interworking between CS networks supporting ISUP and the IM CN subsystem** + +## 7.2.1 Services performed by network entities in the control plane + +### 7.2.1.1 Services performed by the SS7 signalling function + +The SS7 signalling function provides the capabilities to deliver or receive SS7 MTP3-User information (e.g. ISUP or BICC+STCmtp) across the SS7 signalling network. The functional interface of the MTP, the MTP User parts and the signalling network are as detailed in ITU-T Recommendations Q.701 to Q.709 [3]. + +### 7.2.1.2 Services of the SGW + +The SGW shall perform the functions as described in 3GPP TS 23.002 [10]. + +In order to support the seamless operation of the MTP3-User part information between networks incorporating SS7 and IP (either IPv4, see RFC 791 [16], or IPv6, see RFC 2460 [39]), the SGW shall support the services of MTP as well as the services of the M3UA (see 3GPP TS 29.202 [20]) and SCTP (see RFC 2960 [18]). + +### 7.2.1.3 Services of the MGCF + +The session handling and session control of the MGCF shall be as detailed in 3GPP TS 24.229 [9]. + +The MGCF shall provide the interaction, through the use of its interworking function, between the SS7 MTP3-User part information, e.g. ISUP, and SIP. The MGCF interworking function shall also provide the translation between the SS7 MTP3-User part information and SIP, where the interworking of SIP to ISUP and BICC+STCmtp are detailed below. + +### 7.2.1.4 Services of the SIP signalling function + +The SIP signalling function is a logical entity that provides the capabilities to deliver or receive multimedia session information across the IM CN subsystem signalling system. + +## 7.2.2 Signalling interactions between network entities in the control plane + +### 7.2.2.1 Signalling between the SS7 signalling function and MGCF + +The SGW shall enable the signalling interaction between the SS7 signalling function and the MGCF. + +#### 7.2.2.1.1 Signalling from MGCF to SS7 signalling function + +For signalling from the MGCF to the SS7 signalling function, the SGW shall terminate the SCTP and M3UA protocol layers and deliver the MTP3-User protocol messages, e.g. ISUP messages, towards the SS7 signalling function. The SGW transmits and receives SS7 Message Signalling Units (MSUs) to and from the SS7 signalling function over standard SS7 network interfaces, using MTP to provide reliable transport of the messages. + +#### 7.2.2.1.2 Signalling from SS7 signalling function to MGCF + +For signalling from the SS7 signalling function to the MGCF, the SGW shall terminate SS7 MTP2 and MTP3 protocol layers and deliver MTP3-User part information messages, e.g. ISUP, towards the MGCF. In order to direct messages received from the SS7 MTP3 network to the appropriate IP destination, e.g. MGCF, the SGW shall perform a message distribution function using the information received from the MTP3-User message. Message distribution at the SGW shall be performed in accordance with 3GPP TS 29.202 [20]. + +#### 7.2.2.1.3 Services offered by SCTP and M3UA + +The SGW internal protocol mapping and transportation between BICC or ISUP messages and IP encapsulated BICC or ISUP messages respectively is supported by the services of the M3UA adaptation layer and the underlying SCTP layer. The SGW shall allow for the transfer of MTP3-User signalling messages, e.g. BICC or ISUP, to and from an MGCF, where the peer MTP3-User protocol exists. + +##### 7.2.2.1.3.1 Services offered by SCTP + +SCTP offers the ability to reliably transfer the SCTP User applications, e.g. M3UA, between the SCTP User application peers. The initialization procedure used for an association between two SCTP end-to-end peers, and the initialization to the SCTP User applications shall be performed as detailed in RFC 2960 [18]. + +#### 7.2.2.1.3.2 Services offered by M3UA + +When an association between two SCTP peers has been established, the use of M3UA shall provide the transport service in accordance with MTP (see ITU-T Recommendations Q.701 to Q.709 [3]) to the MTP3-User, e.g. ISUP. + +#### 7.2.2.2 Signalling between the MGCF and SIP signalling function + +Signalling between the SIP signalling function and the MGCF uses the services of IP (RFC 2460 [39]), and transport protocol such as TCP (RFC 793 [24]) or UDP (RFC 768 [17]) or SCTP (RFC 2960 [18]) (see 3GPP TS 24.229 [9]), and SIP. + +The naming and addressing concepts between the MGCF and SIP signalling function shall be detailed in accordance with 3GPP TS 23.228 [12]. The issues of general IP address management are discussed in 3GPP TS 23.221 [47]. + +### 7.2.3 SIP-ISUP protocol interworking + +When a coding of a parameter value is omitted it implies that it is not affected by the interworking and the values are assigned by normal protocol procedures. + +#### 7.2.3.1 Incoming call interworking from SIP to ISUP at I-MGCF + +##### 7.2.3.1.1 Sending of IAM + +On reception of a SIP INVITE requesting a session, the I-MGCF shall send an IAM message. The allowed sessions are given in clause 7.2.3.1.2.5. + +An I-MGCF shall support both incoming INVITE requests containing SIP preconditions and 100rel extensions in the SIP Supported or Require header fields, and INVITE requests not containing these extensions, unless the Note below applies. + +NOTE: If the I-MGCF is deployed in an IMS network that by local configuration serves no user requiring preconditions, the MGCF may not support incoming requests requiring preconditions. + +The I-MGCF shall interwork forked INVITE requests with different request URIs. + +If the SIP precondition extension is not included in the Supported or Require header field, the I-MGCF shall send an IAM immediately after the reception of the INVITE, as shown in figure 3. The I-MGCF shall set the continuity indicators to "Continuity check not required". + +If a Continuity Check procedure is supported in the ISUP network and SIP precondition extension are included in the SIP Supported or Require header field, the I-MGCF shall send the IAM immediately after the reception of the INVITE, as shown in figure 3. If the received SDP indicates that precondition is fulfilled the I-MGCF shall set the continuity indicators to "continuity check is not required". If the received SDP indicates that precondition is not fulfilled the I-MGCF shall set the continuity indicators to "continuity check performed on a previous circuit". The procedure in figure 3 applies when the value of the continuity indicator is either set to "continuity check required", "continuity check performed on a previous circuit" or "continuity check not required". If the continuity indicator is set to "continuity check required" the corresponding procedures at the Mn interface described in clause 9.2.2.3 also apply. + + + +``` +graph LR; INVITE[INVITE] --> I-MGCF[I-MGCF]; I-MGCF --> IAM[IAM]; +``` + +Diagram showing the receipt of an INVITE request and the subsequent sending of an IAM message at the I-MGCF. An arrow labeled 'INVITE' points to a vertical line representing the I-MGCF. From the I-MGCF, an arrow labeled 'IAM' points to the right. + +**Figure 3: Receipt of an INVITE request (continuity procedure supported in the ISUP network)** + +If Continuity Check procedure is not supported in the ISUP network, and the SDP in the received INVITE request contains preconditions not met, the I-MGCF shall delay sending the IAM until the SIP preconditions are met and set the continuity indicators in the resulting IAM to "Continuity check not required". + + + +``` + +graph LR + INVITE[INVITE] --> I-MGCF[I-MGCF] + subgraph Box [SDP indicating pre-conditions met] + SDP[SDP indicating pre-conditions met] + end + SDP --> I-MGCF + I-MGCF --> IAM[IAM] + +``` + +Diagram showing the receipt of an INVITE request by an I-MGCF. An INVITE message is received from the left. A box labeled 'SDP indicating pre-conditions met' is shown below the INVITE message, with an arrow pointing from it to the I-MGCF. The I-MGCF then sends an IAM message to the right. + +**Figure 4: Receipt of an INVITE request (continuity procedure not supported in the ISUP network)** + +The I-MGCF shall reject an INVITE request for a session only containing unsupported media types by sending a status code 488 "Not Acceptable Here". If several media streams are contained in a single INVITE request, and if the I-MGCF does not support multimedia interworking according to Annex E, then the I-MGCF shall select one of the supported media streams, reserve the codec(s) for that media stream, and reject the other media streams and unselected codecs in the SDP answer, as detailed in IETF RFC 3264 [36]. If supported audio media stream(s) and supported non-audio media stream(s) are contained in a single INVITE request, an audio stream should be selected. + +The I-MGCF shall include a To tag in the first backward non-100 provisional response, in order to establish an early dialog as described in IETF RFC 3261 [19]. + +If an MGCF discovers an emergency call it shall, depending on national requirements, map that to appropriate indication in ISUP. + +According to IETF RFC 3261 [19] and IETF RFC 3264 [36], if an INVITE message is received without an SDP offer, then the I-MGCF sends an SDP offer in the first reliable non-failure message. + +### 7.2.3.1.2 Coding of the IAM + +#### 7.2.3.1.2.0 General + +The following ISDN user part parameters description can be found in ITU-T Recommendation Q.763 [4]. + +##### 7.2.3.1.2.1 Called party number + +The E.164 address encoded in the Request-URI shall be mapped to the called party number parameter of the IAM message. + +**Table 2: Coding of the called party number** + +| INVITE→ | IAM→ | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| Request-URI | Called Party Number | | | +| E.164 address
(format +CC
NDC SN)
(e.g. as User info
portion of a SIP
URI with
user=phone, or
as tel URI) | Address Signal:
Analyse the information contained in received E.164 address.
If CC is country code of the network in which the next hop terminates, then remove "+CC"
and use the remaining digits to fill the Address signals.
If CC is not the country code of the network in which the next hop terminates, then remove
"+" and use the remaining digits to fill the Address signals.
(NOTE 2) | | | +| | Odd/even indicator: set as required | | | +| | Nature of address indicator:
Analyse the information contained in received E.164 address.
If CC is country code of the network in which the next hop terminates, then set Nature of
Address indicator to "National (significant) number".
If CC is not the country code of the network in which the next hop terminates, then set
Nature of Address indicator to "International number".
(NOTE 1) | | | +| | Internal Network Number Indicator:
1 routing to internal network number not allowed | | | +| | Numbering plan Indicator:
001 ISDN (Telephony) numbering plan (Rec. E.164) | | | +| national operator
option for service
numbers:
Non E.164
numbers
(as a local-
number with a
phone-context in
the User Info
portion in a SIP
URI with
user=phone, or
as a local
number with a
phone-context in
a tel URI) | (NOTE 3) | Address Signal:
use received non E.164 number to fill the Address signals with national
significant number. | | +| | | Odd/even indicator: set as required | | +| | | Nature of address indicator:
"National (significant) number". (NOTE 1) | | +| | | Internal Network Number Indicator:
1 routing to internal network number not allowed | | +| | | Numbering plan Indicator:
001 ISDN (Telephony) numbering plan (Rec. E.164) | | +| (NOTE 3) | | Address Signal:
Use received non E.164 number to fill the Address signals. | | +| | | Odd/even indicator: set as required | | +| | | Nature of address indicator:
set Nature of Address indicator to "network-specific number" or to "reserved
for national use". | | +| | | Internal Network Number Indicator:
1 routing to internal network number not allowed | | +| | | Numbering plan Indicator:
Based on operator policy other numbering plan indicators than "001 ISDN
(Telephony) numbering plan (Rec. E.164)" can be used e.g. depending on
phone context value. | | +| NOTE 1: The usage of "nature of address indicator" value "unknown" is allowed but the mapping is not specified in the present specification. | | | | +| NOTE 2: If PSTN XML and ISUP Sending Terminated (ST) signal are supported as a network option, then the PSTN XML sendingCompleteIndication, if present, is mapped to the sending terminated digit (hexadecimal digit F) in the address signals field of the Called Party Number parameter. | | | | +| NOTE 3: Depending on configuration, network-specific numbers (identified by phone context according to operator policy) should be translated into "ISDN (Telephony) numbering plan numbers (Rec. E.164)" unless such a mapping is not possible and local operator's policy requires keeping them in local format. | | | | + +#### 7.2.3.1.2.2 Nature of connection indicators + +bits BA Satellite indicator + +0 0 *no satellite circuit in the connection* + +bits DC Continuity check indicator + +- 0 0 *continuity check not required*, if the continuity check procedure is not supported in the succeeding network (figure 4). + - 0 1 *continuity check required*, if a continuity check shall be carried out on the succeeding circuit. (figure 3) + - 1 0 *continuity check performed on a previous circuit otherwise*, if the continuity check procedure is supported in the succeeding network, but shall not be carried out on the succeeding circuit otherwise. (figure 3) +- bit E Echo control device indicator +- 1 *outgoing echo control device included*, for speech calls, e.g., TMR is "3.1KHz audio". + - 0 *outgoing echo control device not included*, for known data calls, e.g., TMR "64 kBit/s unrestricted" or HLC "Facsimile Group 2/3". + +#### 7.2.3.1.2.3 Forward call indicators + +- bits CB End-to-end method indicator +- 0 0 *no end-to-end method available (only link-by-link method available)* +- bit D Interworking indicator +- 1 *interworking encountered* + +As a network operator option, the value D = 0 "No interworking encountered" is used if the TMR = 64 kBit/s unrestricted is used. + +NOTE: This avoids sending of a progress indicator with progress information 0 0 0 0 0 0 1 "Call is not end-to-end ISDN; further call progress information may be available in-band", so the call will not be released for that reason by an ISDN terminal. + +- bit E End-to-end information indicator (national use) +- 0 *no end-to-end information available* +- bit F ISDN user part/BICC indicator +- 0 *ISDN user part/BICC not used all the way* + +As a network operator option, the value F = 1 "ISDN user part/BICC used all the way" is used if the TMR = 64 kBit/s unrestricted is used. + +NOTE: This avoids sending of a progress indicator with progress information 0 0 0 0 0 0 1 "Call is not end-to-end ISDN; further call progress information may be available in-band", so the call will not be released for that reason by an ISDN terminal. + +- bits HG ISDN user part/BICC preference indicator +- if any used supplementary service requires ISUP or BICC all the way, depending on operator policy: +- 0 0 *ISDN user part/BICC preferred all the way*, or + - 1 0 *ISDN user part/BICC required all the way*; +- Otherwise: +- 0 1 *ISDN user part/BICC not required all the way* +- bit I ISDN access indicator +- 0 *originating access non-ISDN* + +As a network operator option, the value I = 1 "originating access ISDN" is used if the TMR = 64 kBit/s unrestricted is used. + +NOTE: This avoids sending of a progress indicator with progress information 0 0 0 0 1 1 "Originating access is non-ISDN", so the call will not be released for that reason by an ISDN terminal. + +bits KJ SCCP method indicator + +0 0 *no indication* + +If the PSTN XML is supported as a network option, the Forward Call indicators derived as shown in Table 02a shall take precedence. + +**Table 02a: Mapping of PSTN XML elements to Forward call indicators parameter** + +| INVITE →
PSTN XML | IAM →
Forward call indicators parameter | | +|--------------------------------------------------------------------------------------------------------------|--------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PSTN XML with Progress indicator with Progress Description value 6 (Meaning: originating access ISDN) | bit D
0
bit F
1
bit I
1 | Interworking Indicator
"no interworking encountered (No. 7 signalling all the way)"
ISDN User Part indicator
"ISDN User Part used all the way"
ISDN access indicator
"originating access ISDN" | +| NOTE: Progress Indicator with Progress Description value "6" shall not be included in an ATP within the IAM. | | | + +#### 7.2.3.1.2.4 Calling party's category + +See ANNEX C for the normative interworking of the CPC parameter. + +##### 7.2.3.1.2.4A Originating Line Information + +The ISUP Originating Line Information parameter is defined by ANSI Standard ATIS-1000113 [117], Chapter 3. + +See Annex H for the normative interworking of the OLI parameter as a network option. + +##### 7.2.3.1.2.5 Transmission medium requirement + +The I-MGCF may either transcode the selected codec(s) to the codec on the PSTN side or it may attempt to interwork the media without transcoding. If the I-MGCF transcodes, it shall select the TMR parameter to "3.1 kHz audio". If the I-MGCF does not transcode, it should map the TMR, USI and Access Transport parameters from the selected codec according to Table 2a. However, if the I-MGCF supports the PSTN XML body as a network option, and if a PSTN XML body is received in the INVITE request and the I-MGCF selects media encoded in any of the formats in table 2a (G.711, Clearmode or t38) among the offered media, the I-MGCF shall derive these parameters from the XML body instead, as detailed in table 2b. The I-MGCF should only apply the mapping in table 2b if the TMR and USI values derived from the selected codec according to table 2a are equivalent with the values within the first Bearer Capability element in the PSTN XML, and otherwise the I-MGCF should apply the mapping according to table 2a. + +The support of any of the media listed in table 2a is optional. + +If no SDP is received from the remote peer (as described in clause 7.2.3.1.1), then the TMR parameter should be set to "3.1 kHz audio". Transcoding shall be applied as required. + +**Table 2a: Coding of TMR/USI/HLC from SDP: SIP to ISUP** + +| | m= line | | b= line (NOTE 4) | a= line | TMR parameter | USI parameter (optional) (NOTE 1) | | HLC IE in the ATP parameter (optional) | +|---------|-------------|------------|----------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------------------------------------------|------------------------------------------------|---------------------------------------------|-------------------------------------------| +|
(NOTE 5) | rtpmap:
PCMU/8000 | "3.1KHz audio" | | | (NOTE 3) | +| audio | RTP/AVP | 8 | N/A or AS: up to (64 kbit/s + RTP/UDP/IP overhead) | N/A | "3.1KHz audio" | | | (NOTE 3) | +| audio | RTP/AVP | Dynamic PT | N/A or AS: up to (64 kbit/s + RTP/UDP/IP overhead) | rtpmap:
PCMA/8000 | "3.1KHz audio" | | | (NOTE 3) | +| audio | RTP/AVP | Dynamic PT | AS: (64 kbit/s + RTP/UDP/IP overhead) | rtpmap:
CLEARMODE/8000
(NOTE 2) | "64 kbit/s unrestricted"
or
"64 kbit/s preferred"
(NOTE 7) | "Unrestricted digital information"
(NOTE 6) | | | +| image | Udptl [73] | t38 [73] | N/A or AS: up to (64 kbit/s + UDP/IP overhead) | Based on ITU-T T.38 [72] (NOTE 8) | "3.1 KHz audio" | "3.1 KHz audio" | | "Facsimile Group 2/3" | +| image | tcp | t38 [73] | N/A or AS: up to (64 kbit/s + TCP/IP overhead) | Based on ITU-T T.38 [72] | "3.1 KHz audio" | "3.1 KHz audio" | | "Facsimile Group 2/3" | + +NOTE 1: In this table the codec G.711 is used only as an example. Other codecs are possible. + +NOTE 2: CLEARMODE is specified in RFC4040 [69]. + +NOTE 3: HLC is normally absent in this case. It is possible for HLC to be present with the value "Telephony", although 6.3.1/Q.939 indicates that this would normally be accompanied by a value of "Speech" for the Information Transfer Capability element. + +NOTE 4: The MGCF should return an b:AS bandwidth modifier with a bandwidth of 64kbit/s + RTP/UDP/IP overhead in the SDP answer to request that the peer does not send with a higher bandwidth. If the received b=line indicates a bandwidth greater than 64kbit/s + RTP/UDP/IP overhead, the MGCF should also accept the incoming call. + +NOTE 5:
(InformationTransferCapability)
(NOTE 2) | Speech | TMR | Speech | +| | 3.1 kHz audio | | 3.1 kHz audio | +| | Unrestricted digital information | | 64 kbit/s unrestricted | +| | Unrestricted digital information with tones/announcements | | 64 kbit/s unrestricted | + +NOTE 1: If two high layer compatibility information elements are received, they shall be transferred in the same order as received in the PSTN XML body in the INVITE message. +NOTE 2: If there are two BCs present, see clause 7.2.3.1.2.5a. +NOTE 3: The above mapping assumes that there is only a single BearerCapability present. + +#### 7.2.3.1.2.5a Transmission medium requirement prime and USI prime (optional) + +The procedures to support UDI-TA Fallback mechanism described in the present clause shall only apply if two PSTN XML Bearer Capability elements appear within the INVITE Request and the MGCF supports the PSTN XML body as a network option. + +When all the following conditions apply: + +- The INVITE request includes SDP with one m-line with at least two formats, and with the coding of the first two formats appearing in table 2a; +- the TMR and USI prime values derived from the first format in the m-line according to table 2a are equivalent with the values within the second Bearer Capability element in the PSTN XML; +- the TMR prime and USI values derived from the second format in the m-line according to table 2a are equivalent with the values within the first Bearer Capability element in the PSTN XML; and +- the I-MGCF supports forwarding fallback signalling. + +Then the I-MGCF shall + +- if TMR "64 kBit/s preferred" is supported at the succeeding trunk: + - map the first XML Bearer Capability element into the "USI" within the IAM; + - map the the first PSTN XML BearerCapability (InformationTransferCapability) into the "TMR prime" within the IAM, applying the same mapping rules as specified for the mapping into the "TMR" in table 2b; + - map the second XML Bearer Capability element (InformationTransferCapability) into the USI prime within the IAM; + - set the TMR within the IAM to "64 kBit/s preferred"; + - configure the IM-MGW; and + - store those values; +- if TMR "64 kBit/s preferred" is not supported at the succeeding trunk: + - apply the procedures as described within clause 7.2.3.1.2.5, using the first Bearer Capability element in the PSTN XML and the second format in the m-line; + +discard the second Bearer Capability element in the PSTN XML; + +- select the second format in the m-line within the SDP answer; and +- configure the IM-MGW. + +Otherwise (i.e. if some Bearer Capability element in the PSTN XML did not match the SDP), the I-MGCF shall: + +- discard the XML Bearer Capability elements; +- if the I-MGCF received at least two formats within the m-line, select one of those formats, except for the CLEARMODE codec, within the SDP answer; +- apply the mapping for the selected format according to table 2a; and +- configure the IM-MGW accordingly + +#### 7.2.3.1.2.6 Calling party number + +The SIP "Privacy" header is defined within IETF RFC 3323 [40]. The SIP "P-Asserted-Identity" header is defined in IETF RFC 3325 [41]. + +**Table 3: Mapping of SIP From/P-Asserted-Identity/Privacy headers to CLI parameters** + +| Has a "P-Asserted-Identity" header field (NOTE 2, NOTE 5, NOTE 6) been received? | Has a "From" header field (NOTE 3) containing a URI that encodes an E.164 address been received (NOTE 6)? | Calling Party Number parameter Address signals | Calling Party Number parameter APRI | Generic Number (additional calling party number) address signals | Generic Number parameter APRI | +|----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------| +| No | No | Network option to either include a network provided E.164 number (See table 4) or omit the Address signals. | Network option to set APRI to "presentation restricted" or "presentation allowed" (NOTE 4) (See table 5)
As a network option the APRI "presentation restricted by network" (NOTE 7) can be used instead of the APRI "presentation restricted" | Parameter not included | Not applicable | +| No | Yes | Network option to either include a network provided E.164 number (See table 4) or omit the Address signals. | Network option to set APRI to "presentation restricted" or "presentation allowed" (NOTE 4) (See table 5)
As a network option the APRI "presentation restricted by network" (NOTE 7) can be used instead of the APRI "presentation restricted" | Network option to either omit the parameter (if CgPN has been omitted) or derive from the "From" header (NOTE 1) (See table 6) | APRI = "presentation restricted" or "presentation allowed" depending on SIP Privacy header. (See table 6) | +| Yes | No | Derived from P-Asserted-Identity (See table 5) | APRI = "presentation restricted" or "presentation allowed" depending on SIP Privacy header. (See table 5) | Not included | Not applicable | +| Yes | Yes | Derived from P-Asserted-Identity (See table 5) | APRI = "presentation restricted" or "presentation allowed" depending on SIP Privacy header. (See table 5) | Network option to either omit the parameter or derive from the "From" header (NOTE 1) (See table 6) | APRI = "presentation restricted" or "presentation allowed" depending on SIP Privacy header. (see table 6) | + +| Has a "P-Asserted-Identity" header field (NOTE 2, NOTE 5, NOTE 6) been received? | Has a "From" header field (NOTE 3) containing a URI that encodes an E.164 address been received (NOTE 6)? | Calling Party Number parameter Address signals | Calling Party Number parameter APRI | Generic Number (additional calling party number) address signals | Generic Number parameter APRI | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|------------------------------------------------|-------------------------------------|------------------------------------------------------------------|-------------------------------| +|
NOTE 1: This mapping effectively gives the equivalent of Special Arrangement to all SIP UAC with access to the I-MGCF.
NOTE 2: It is possible that the P-Asserted-Identity header field includes both a tel URI and a SIP URI. In this case, either the tel URI or the SIP URI with user="phone" and a specific host portion, as selected by operator policy, may be used.
NOTE 3: The "From" header may contain an "Anonymous User Identity". An "Anonymous User Identity" includes information that does not point to the calling party. IETF RFC 3261 recommends that the display-name component contain "Anonymous". That the Anonymous User Identity will take the form defined in TS 23.003 [74]. The Anonymous User Identity indicates that the calling party desired anonymity. The From header may also contain an Unavailable User Identity as defined in TS 23.003 [74], that indicates that the calling party is unknown.
NOTE 4: A national option exists to set the APRI to "Address not available".
NOTE 5: TS 24.229 [9] guarantees that the received number is an E.164 number formatted as an international number, with a "+" sign as prefix.
NOTE 6: The E.164 numbers considered within the present document are composed by a Country Code (CC), followed by a National Destination Code (NDC), followed by a Subscriber Number (SN). On the IMS side, the numbers are international public telecommunication numbers ("CC"+"NDC"+"SN") and are prefixed by a "+" sign. On the CS side, it is a network option to omit the CC.
NOTE 7: This is an ETSI specific value described within ETSI EN 300 356-1 [70].
| | | | | | + +**Table 4: Setting of the network-provided BICC/ISUP calling party number parameter with a CLI (network option)** + +| BICC/ISUP CgPN Parameter field | Value | +|------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Screening Indicator | " network provided " | +| Number Incomplete Indicator | " complete " | +| Number Plan Indicator | ISDN/Telephony (E.164) | +| Address Presentation Restricted Indicator | Presentation allowed/restrictedAs a network option the APRI value "presentation restricted by network" (NOTE) can be used instead of the APRI value "presentation restricted" | +| Nature of Address Indicator | If next BICC/ISUP node is located in the same country set to " National (Significant) number " else set to " International number " | +| Address signals | If NOA is " national (significant) number " no country code should be included. If NOA is " international number ", then the country code of the network-provided number should be included. | +| NOTE: This is an ETSI specific value described within ETSI EN 300 356-1 [70] | | + +**Table 5: Mapping of P-Asserted-Identity and privacy headers to the ISUP/BICC calling party number parameter** + +| SIP Component | Value | BICC/ISUP Parameter / field | Value | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| P-Asserted-Identity header field (NOTE 1) | E.164 number | Calling Party Number | | +| | | Number incomplete indicator | "Complete" | +| | | Numbering Plan Indicator | "ISDN/Telephony (E.164)" | +| | | Nature of Address Indicator | If CC encoded in the URI is equal to the CC of the country where MGCF is located AND the next BICC/ISUP node is located in the same country then set to " national (significant) number " else set to " international number " | +| | | Screening indicator (NOTE 2) | Network Provided | +| Addr-spec | "CC" "NDC" "SN" from the URI | Address signal | If NOA is " national (significant) number " then set to "NDC" + "SN"
If NOA is " international number " then set to "CC"+"NDC"+"SN" | +| Privacy header field is not present | | APRI | " presentation allowed " | +| Privacy header field (IETF RFC 3323 [40]) | priv-value | APRI | If the Privacy header field contains the values " id " (see IETF RFC 3325 [41]) and/or " header ", the APRI shall be set to " presentation restricted ". Otherwise, the APRI shall be set to " presentation allowed ". | +| NOTE 1: It is possible that a P-Asserted –Identity header field includes both a tel URI and a SIP URI. In this case, either the tel URI or the SIP URI with user="phone" and a specific host portion, as selected by operator policy, may be used. | | | | +| NOTE 2: As a network option, the MGCF may support "Calling number verification using signature verification and attestation information " feature as described in IETF RFC 8224 [153] and 3GPP TS 24.229 [9]. If the I-MGCF received a "verstat" tel URI parameter (defined in 3GPP TS 24.229 [9] clause 7.2A.20) in the P-Asserted-Identity header filed the I-MGCF may map the "verstat" tel URI parameter to the Screening Indicator field as follows:
- the value "No-TN-Validation" to the value "user provided, not verified";
- the value "TN-Validation-Passed" to the value "user provided, verified and passed"; and
- the value "TN-Validation-Failed" to the value "user provided, verified and failed". | | | | + +## 7.2.3.1.2.7 Generic number + +**Table 6: Mapping of SIP from header field to BICC/ISUP generic number (additional calling party number) parameter (network option)** + +| SIP component | Value | BICC/ISUP parameter / field | Value | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| From header field | name-addr or addr-spec | Generic number
Number Qualifier Indicator | " additional calling party number " | +| | | Nature of Address Indicator | If CC encoded in the URI is equal to the CC of the country where MGCF is located AND the next BICC/ISUP node is located in the same country then set to " national (significant) number " else set to " international number " | +| | | National operator option for local numbers (NOTE 2):
Nature of Address Indicator | Based on the received local number and phone-context set to " subscriber number " or " unknown ". (NOTE 3) | +| | | Number incomplete indicator | " Complete " | +| | | Numbering Plan Indicator | " ISDN/Telephony (E.164) " | +| | | Screening indicator (NOTE 1) | " user provided not verified " | +| Addr-spec | E.164 address (format "+" "CC" "NDC" "SN") from the URI | Address signal | If NOA is "national (significant) number" then set to "NDC" + "SN"
If NOA is "international number" then set to "CC"+"NDC"+"SN" | +| | National operator option for local numbers (NOTE 2):
non E.164 address (NOTE 4) | | Use received non E.164 number to fill the Address signals. | +| Privacy header field is not present | | APRI | " presentation allowed " | +| Privacy header field (IETF RFC 3323 [40]) | priv-value | APRI | If the Privacy header field contains the value "user", the APRI shall be set to " presentation restricted ". Otherwise, the APRI shall be set to " presentation allowed ". | +| NOTE 1: As a network option, the MGCF may support "Calling number verification using signature verification and attestation information" feature as described in IETF RFC 8224 [153] and 3GPP TS 24.229 [9]. If the I-MGCF received a "verstat" tel URI parameter (defined in 3GPP TS 24.229 [9] clause 7.2.A.20) in the From header field the I-MGCF may map the "verstat" tel URI parameter to the Screening Indicator field as follows:
- the value "No-TN-Validation" to the value "user provided, not verified";
- the value "TN-Validation-Passed" to the value "user provided, verified and passed"; and
- the value "TN-Validation-Failed" to the value "user provided, verified and failed". | | | | +| NOTE 2: Local numbers can e.g. be national service numbers, business trunking numbers, or private numbers. | | | | +| NOTE 3: Mapping between phone-context values and "Nature of Address Indicator" values is provisioned in the MGCF. Setting the values of "Nature of Address Indicator" is dependent on local operator's policies. | | | | +| NOTE 4: A non E.164 address can either be present as a local number with a phone-context parameter in the user portion of a SIP URI with "user=phone" or as a local number with a phone-context parameter in a tel URI. | | | | + +## 7.2.3.1.2.8 User service information + +For coding of the USI see 7.2.3.1.2.5. + +#### 7.2.3.1.2.9 Hop Counter (National option) + +The I-MGCF shall perform the following interworking procedure if the Hop Counter procedure is supported in the CS network. + +At the I-MGCF the Max-Forwards SIP header shall be used to derive the Hop Counter parameter if applicable. Due to the different default values (that are based on network demands/provisions) of the SIP Max-Forwards header and the Hop Counter, a factor shall be used to adapt the Max Forwards to the Hop Counter at the I-MGCF. For example, the following guidelines could be applied: + +- 1) Max-Forwards for a given message should be monotone decreasing with each successive visit to a SIP entity, regardless of intervening interworking, and similarly for Hop Counter. +- 2) The initial and successively mapped values of Max-Forwards should be large enough to accommodate the maximum number of hops that may be expected of a validly routed call. + +Table 7 shows the principle of the mapping: + +**Table 7: Max forwards - hop counter** + +| | | | | +|----------------------------------------------------------------------------------------------------|-----|-------------|----------------------------------| +| Max-Forwards | = X | Hop Counter | = INTEGER part of (X /Factor) =Y | +| NOTE: The Mapping of value X to Y should be done with the used (implemented) adaptation mechanism. | | | | + +The Principle of adoption could be implemented on a basis of the network provision, trust domain rules and bilateral agreement. + +#### 7.2.3.1.2.10 Progress Indicator + +If the I-MGCF supports the PSTN XML body as a network option and an INVITE containing a PSTN XML body is received, an available "ProgressIndicator" element in the PSTN XML body shall be mapped into a Progress Indicator in the Access Transport Parameter of the sent IAM as shown in table 7.2.3.1.2.10.1. + +**Table 7.2.3.1.2.10.1: Contents of the Access Transport Parameter** + +| INVITE → | IAM→ | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| +| PSTN XML | Access Transport Parameter | +| Progress indicator | Progress indicator (NOTE) | +| NOTE: A ProgressIndicator with Progress Description value 6 shall not be included into the ISUP ATP, and is mapped instead to Forward call indicators parameter according to table 02a. | | + +#### 7.2.3.1.2.11 Location Number + +Location Number is defined in clause 3.30 of ITU-T Q.763 [4]. + +If the received INVITE message contains: + +- 1) only one P-Access-Network-Info header field and the P-Access-Network-Info header contains only one access network specific component then: + - a) if an access-type field with the value "GSTN" is received: + - i) if an access-info field with the value "gstn-location" is present and the value "operator-specific-GI" is not present, the I-MGCF shall include an ISUP Location Number parameter in the outgoing IAM set as shown in table 7.2.3.1.2.11.1; or + - ii) as a network option: + - if an access-info field with the value "operator-specific-GI" is present and the value "gstn-location" is not present, the I-MGCF shall include an ISUP Location Number parameter in the outgoing IAM set as shown in table 7.2.3.1.2.11.3; or + +- if both values "gstn-location" and "operator-specific-GI" are present, the I-MGCF shall include an ISUP Location Number parameter in the outgoing IAM set as shown in table 7.2.3.1.2.11.1 or table 7.2.3.1.2.11.3, based on local policy; or + - b) as a network option, if an access-type field with a value different from "GSTN" and an access-info field with the value "operator-specific-GI" are received, the I-MGCF shall include an ISUP Location Number parameter in the outgoing IAM as shown in table 7.2.3.1.2.11.3; or +- 2) more P-Access-Network-Info header fields or the P-Access-Network-Info header field contains more access network specific components then the I-MGCF shall select the access network specific component which contains a "network-provided" parameter and shall perform the mapping to an ISUP Location Number parameter as described in bullet 1). + +NOTE 1: According to 3GPP TS 24.229 [9] two P-Access-Network-Info header fields (or one P-Access-Network-Info header field with two access network specific components) can be received but only one access network specific component can contain the "network-provided" parameter. + +NOTE 2: A UE will not create the P-Access-Network-Info header field with the access-type field value "GSTN" and the "gstn-location" parameter, as specified in subclause 7.2A.4.2 of 3GPP TS 24.229 [9]. However the access-type field value "GSTN" without the "network-provided" parameter can be received in interworking cases when the IMS network is used between two CS networks and the P-Access-Network-Info header field was created by the O-MGCF in accordance to subclause 7.2.3.2.2.9. Based on local policy, the I-MGCF can select the P-Access-Network-Info header field with the access-type field value "GSTN" and without the "network-provided" parameter. + +**Table 7.2.3.1.2.11.1: Contents of the location number parameter** + +| INVITE → | IAM→ | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------| +| | Location Number parameter | +| P-Access-Network-Info with access-type="GSTN" and gstn-location parameter | Binary value derived from the gstn-location parameter of the P-Access-Network-Info | +| NOTE: The binary value shall be obtained by removing the quotes and converting each pair of consecutive character strings into an octet that has the equivalent hexadecimal representation | | + +**Table 7.2.3.1.2.11.2: Mapping of P-Access-Network-Info to Location Number** + +| INVITE→ | IAM→ | +|-------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| P-Access-Network-Info | Location Number | +| access type="GSTN"
gstn-location=value | Address Signal:
Copied from octet 3 to n of the binary representation of the gstn-location field
Odd/even indicator:
Copied from bit 8 octet 1 of the binary representation of the gstn-location field
Nature of address indicator:
Copied from bit 7 to 1 of octet 1 of the binary representation of the gstn-location field
Internal Network Number Indicator:
Copied from bit 8 of octet 2 of the binary representation of the gstn-location field
Numbering plan Indicator:
Copied from bit 7 to 5 of octet 2 of the binary representation of the gstn-location field
Address presentation restricted indicator:
If the SIP Privacy header field = header, APRI is set to "01 (presentation restricted)" otherwise APRI is copied from bit 4 and 3 of octet 2 of the binary representation of the gstn-location field
Screening indicator:
If the "network-provided" parameter is present in the P-Access-Network-Info header field, set to "11 (network provided)" otherwise set from bit 2 and 1 of octet 2 of the binary representation of the gstn-location field | + +**Table 7.2.3.1.2.11.3: Mapping of P-Access-Network-Info operator-specific-GI to Location Number** + +| INVITE → | IAM→ | +|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Location Number parameter | +| P-Access-Network-Info with
access-info="operator-specific-GI"
and operator-specific-GI parameter | | +| P-Access-Network-Info | Location Number | +| access-info="operator-specific-GI"
operator-specific-GI=value | Address Signal :
Copy the digits set by 2 digits per byte. In case of an odd number of address signals, the filler code 0000 is inserted after the last address signal.
Odd/even indicator:
Set as required
Nature of address indicator:
Set from an operator-configured value
Internal Network Number Indicator:
1 routing to internal network number not allowed
Numbering plan Indicator:
Set from an operator-configured value
Address presentation restricted indicator:
If the SIP Privacy header field = header, APRI is set to "01 (presentation restricted)"
Screening indicator:
If the "network-provided" parameter is present in the P-Access-Network-Info header field, set to "11 (network provided)" | +| NOTE: This mapping is only possible if the operator-specific-GI field of the P-Access-Network-Info header field contains a sequence of digits. | | + +#### 7.2.3.1.2.12 Support of ICS call + +If the received initial INVITE request contains a Feature Caps header field, defined in IETF RFC 6809 [142] with a "+g.3gpp.ics" header field parameter as specified in clause B.4 of 3GPP TS 24.292 [141] then according to operator policy the I-MGCF may mark a call as an "ICS call". + +For the call marked as the "ICS call" the I-MGCF shall include in the outgoing IAM message a redirection information parameter field set as shown in table 7.2.3.1.2.12.1. + +**Table 7.2.3.1.2.12.1: Contents of the redirection information parameter field** + +| INVITE → | IAM→ | | +|-------------------------------------------------------------------------------------------------|-----------------------------------------|--------------------------------------------------------------------| +| Feature-Caps header field with
g.3gpp.ics feature-capability indicator | Redirection information parameter field | | +| | Redirecting indicator | Call diverted, all redirection info presentation restricted | +| | Original redirection reason | Unknown/not available | +| | Redirecting reason | Unknown/not available | +| | Redirection counter | set to maximum value
(NOTE) | +| NOTE: For instance, in ISUP ITU-T Q.763 [4], the Redirection counter parameter cannot exceed 5. | | | + +#### 7.2.3.1.2.13 UID capability indicators (National option) + +UID capability indicators parameter is defined in ITU-T Recommendation Q.763 [4]. + +When a both-way media path is available, then it is possible to support user interactive dialogs prior to answer through the use of the P-Early-Media header field authorizing both-way media. + +If the received initial INVITE request contains a P-Early-Media header field with the "supported" value and either the SDP in the INVITE request allows a send/receive media path or the INVITE request does not contain an SDP body then the UID capability indicators parameter in the outgoing IAM message may be set as shown in table 7.2.3.1.2.13.1. + +**Table 7.2.3.1.2.13.1: Contents of the UID capability indicators parameter** + +| INVITE → | IAM→ | | +|--------------------------------------------------------------------------------------------------------------|--------------------------------------------|-------------------------------------------------------| +| P-Early-Media with "supported" and either SDP with "sendrecv" (explicit or implied) or no SDP present | UID capability indicators parameter | | +| | Through-connection indicator | 1 " through-connection modification possible " | +| | T9 timer indicator | 0 " no indication " | + +#### 7.2.3.1.2.14 Called IN number and original called IN number (optional) + +See Annex L for the normative interworking of the called IN number and original called IN number parameters. + +#### 7.2.3.1.2A Coding of the IAM when Number Portability is supported + +This clause describes optional coding procedures when Number Portability is supported. + +##### 7.2.3.1.2A.1 Coding of the IAM when a Number Portability Routing Number is available + +ITU-T Q.769.1 [92] describes three possible addressing methods for signalling of the Called Party E.164 address and Number Portability Routing Number (ITU-T Q.769.1 [92] uses the terms directory number and network routing number respectively). The choice of these methods is based on network operator and national requirements. + +The following clauses describe how the IAM is populated, based on these methods, when a Number Portability Routing Number is available in the Request URI in the form of a Tel URI "rn=" parameter. + +When the optional Number Portability Routing Number is available and supported, these procedures take precedence over procedures for coding of the Called Party Number described in clause 7.2.3.1.2.1. + +If the Number Portability Database Dip Indicator is present within the Request-URI the procedures described in clause 7.2.3.1.2A.2 apply. When a Number Portability Routing Number is not available, the Called Party Number parameter is populated as described in clause 7.2.3.1.2.1. + +## 7.2.3.1.2.A.1.1 Separate Directory Number Addressing Method + +**Table 7a.0a: Coding of the called party number and called directory number with Number Portability +Separate Directory Number Addressing Method** + +| INVITE→ | IAM→ | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| Request-URI | Called Party Number | Called Directory Number | +| Called Party E.164 address (format +CC NDC SN) (e.g. as User info in SIP URI with user=phone, or as tel URL) plus Number Portability Routing Number (format +CC NDC SN) (e.g. as Tel URI rn= parameter) plus Number Portability Database Dip Indicator as defined in IETF RFC 4694 [93] (e.g. as Tel URI npdi parameter) | Address Signal:
Analyse the information contained in received Number Portability Routing Number. If the Number Portability Routing number contains an E.164 address, then remove "+CC" and use the remaining digits to fill the Address signal. Otherwise, use the digits of the Number Portability Routing number to fill the Address signal.
(NOTE) | Address Signal:
Remove "+CC" from the Called Party E.164 address and use the remaining digits to fill the Address signals. | +| | Odd/even indicator: set as required | Odd/even indicator: set as required | +| | Nature of address indicator:
Set Nature of Address indicator to "Network routing number in national (significant) number 51isali". "National (significant) number" and "Network routing number in network specific number format" may alternately be chosen as described in ITU-T Q.769.1 [92] | Nature of address indicator:
Set Nature of Address indicator to "National (significant) number". | +| | Internal Network Number Indicator:
1 routing to internal network number not allowed | Internal Network Number Indicator:
1 routing to internal network number not allowed | +| | Numbering plan Indicator:
001 ISDN (Telephony) numbering plan (Rec. E.164) | Numbering plan Indicator:
001 ISDN (Telephony) numbering plan (Rec. E.164) | + +NOTE: If PSTN XML and ISUP Sending Terminated (ST) signal are supported as a network option, then the PSTN XML sendingCompleteIndication, if present, is mapped to the sending terminated digit (hexadecimal digit F) in the address signals field of the Called Party Number parameter. + +## 7.2.3.1.2.A.1.2 Concatenated Addressing Method + +**Table 7a.0b: Coding of the called party number with Number Portability Concatenated Addressing Method** + +| INVITE→ | IAM→ | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Request-URI | Called Party Number | +| Called Party E.164 address (format +CC NDC SN) (e.g. as User info in SIP URI with user=phone, or as tel URL) plus Number Portability Routing Number (format +CC NDC SN) (e.g. as Tel URI rn= parameter) plus Number Portability Database Dip Indicator as defined in IETF RFC 4694 [93] (e.g. as Tel URI npdi parameter) | Address Signal:
Analyse the information contained in received Number Portability Routing Number. If the Number Portability Routing number contains an E.164 address, then remove "+CC" and use the remaining digits to fill the Address signal. Otherwise, use the digits of the Number Portability Routing number to fill the Address signal.
Remove the "+CC" from the Called Party E.164 address and append the remaining digits to the Address signal.
(NOTE) | +| | Odd/even indicator: set as required | +| | Nature of address indicator:
set Nature of Address indicator to "Network routing number concatenated with called directory number" or "National (significant) number" as described in ITU-T Q.769.1 [92] | +| | Internal Network Number Indicator:
1 routing to internal network number not allowed | +| | Numbering plan Indicator:
001 ISDN (Telephony) numbering plan (Rec. E.164) | +| NOTE: If PSTN XML and ISUP Sending Terminated (ST) signal are supported as a network option, then the PSTN XML sendingCompleteIndication, if present, is mapped to the sending terminated digit (hexadecimal digit F) in the address signals field of the Called Party Number parameter. | | + +## 7.2.3.1.2.A.1.3 Separate Network Routing Number Addressing Method + +**Table 7a.0c: Coding of the network routing number and called party number with Number Portability Separate Network Routing Number Addressing Method** + +| INVITE→ | IAM→ | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| Request-URI | Network Routing Number | Called Party Number | +| Called Party E.164 address (format +CC NDC SN) (e.g. as User info in SIP URI with user=phone, or as tel URL) plus Number Portability Routing Number (format +CC NDC SN) (e.g. as Tel URI rn= parameter) plus Number Portability Database Dip Indicator as defined in IETF RFC 4694 [93] (e.g. as Tel URI npdi parameter) | Address Signal:
Analyse the information contained in received Number Portability Routing Number. If the Number Portability Routing number contains an E.164 address, then remove "+CC" and use the remaining digits to fill the Address signal. Otherwise, use the digits of the Number Portability Routing number to fill the Address signal. | Address Signal:
Remove "+CC" from the Called Party E.164 address and use the remaining digits to fill the Address signals.
(NOTE) | +| | Odd/even indicator: set as required | Odd/even indicator: set as required | +| | Nature of address indicator:
Set Nature of Address indicator to "Network routing number in national (significant) number format".
"Network routing number in network specific number format" may alternately be chosen as described in ITU-T Q.769.1 [92] | Nature of address indicator:
Set Nature of Address indicator to "National (significant) number". | +| | Numbering plan Indicator:
001 ISDN (Telephony) numbering plan (Rec. E.164) | Internal Network Number Indicator:
1 routing to internal network number not allowed | +| | | Numbering plan Indicator:
001 ISDN (Telephony) numbering plan (Rec. E.164) | +| NOTE: If PSTN XML and ISUP Sending Terminated (ST) signal are supported as a network option, then the PSTN XML sendingCompleteIndication, if present, is mapped to the sending terminated digit (hexadecimal digit F) in the address signals field of the Called Party Number parameter. | | | + +### 7.2.3.1.2A.2 Number Portability Forward Information + +Network Operator or National policy may allow forward transfer of number portability status information, as described in ITU-T Q.769.1 [92]. In this case, the following coding applies. + +**Table 7a.0d: Coding of the number portability forward information** + +| INVITE→
Request-URI | IAM→
Number Portability Forward Information | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Called Party E.164 address
(format +CC NDC SN)
(e.g. as User info in SIP URI with user=phone, or as tel URL) plus Number Portability Routing Number
(format +CC NDC SN) (e.g. as Tel URI rn= parameter) plus Number Portability Database Dip Indicator as defined in IETF RFC 4694 [93] (e.g. as Tel URI npdi parameter) |
If the Number Portability Database Dip Indicator is present, and there is no Number Portability Routing Number, set to "number portability query done for called number, non-ported called subscriber".
If the Number Portability Database Dip Indicator is present, and a Number Portability Routing Number is present, set to "number portability query done for called number, ported called subscriber".
If there is no Number Portability Database Dip Indicator, set to "number portability query not done for called number"
| + +### 7.2.3.1.2B Coding of the IAM for Carrier Routeing + +This clause describes optional coding procedures for carrier-based routeing. The interworking of the CIC parameter is defined. + +#### 7.2.3.1.2B.1 Coding of the IAM when a Carrier Identification Code (CIC) is present + +The procedures followed in clause 7.2.3.1.2.1 apply with the following addition. + +Based on network configuration, if the tel-URI parameter in a tel-URI or the userinfo part of a SIP URI with user=phone in the Request-URI of an initial INVITE request, contains a "cic=" parameter, as defined in IETF RFC 4694 [93], the I-MGCF may extract the carrier identification code from the "cic=" field for routeing the call. If the outgoing IAM message contains the Transit Network Selection (TNS) parameter, as defined in ITU-T Q.763 [4], based on network configuration the TNS may be populated using the carrier identification code from the "cic=" field. The format of the "cic" parameter (e.g. global-cic and local-cic) shall be compliant to IETF RFC 4694 [93]. + +#### 7.2.3.1.2B.2 Void + +### 7.2.3.1.3 Sending of COT + + + +``` + +sequenceDiagram + participant Client + participant I-MGCF + Note left of Client: SDP indicating preconditions met and/or active media + Client->>I-MGCF: + I-MGCF->>COT: + +``` + +Sequence diagram showing the sending of COT. A box on the left contains 'SDP indicating preconditions met and/or active media'. An arrow points from this box to a vertical line labeled 'I-MGCF'. From the I-MGCF line, an arrow points to a box labeled 'COT'. + +**Figure 5: Sending of COT** + +If the IAM has already been sent, the Continuity message shall be sent indicating "continuity check successful", when all of the following conditions have been met: + +- The requested remote preconditions (if any) in the IMS network have been met. +- The media stream previously set to inactive mode is set to active (as specified in IETF RFC 4566 [56]). + +- Local preconditions have been fulfilled. +- A possible outstanding continuity check procedure is successfully performed on the outgoing circuit. + +### 7.2.3.1.3A Sending of SAM + +#### 7.2.3.1.3A.1 General + +The procedures in the present clause are only applicable if the I-MGCF supports the network option of overlap signalling, using either the in-dialog method or the multiple INVITEs method. Within one IMS only a single of those methods shall be used. + +After the ISUP IAM message has been sent the I-MGCF can receive additional digits. The additional digits may either, as a network option, be received in: + +- in-dialog SIP INFO requests ("legacy" mode of usage of the INFO method as defined in IETF RFC 6086 [133]), in-dialog method as specified in clause 7.2.3.1.3A.2 or +- in additional SIP INVITE requests, multiple INVITEs method as specified in 7.2.3.1.3A.3. + + + +``` + +graph LR + A[SIP message carrying additional digits] --> I-MGCF + I-MGCF --> SAM + SAM --> B[ ] + style B fill:none,stroke:none + +``` + +Diagram illustrating the sending of SAM. A box labeled 'SIP message carrying additional digits' has an arrow pointing to a vertical line representing the I-MGCF. From the I-MGCF, an arrow points to a box labeled 'SAM', which then has an arrow pointing to the right. + +**Figure 5a: Sending of SAM** + +#### 7.2.3.1.3A.2 Additional digits received in in-dialog SIP INFO requests + +If interworking of overlap signalling using the in-dialog method is supported by the I-MGCF, the ISUP IAM message has already been sent, but no ISUP ACM or REL message has been received, and a SIP INFO request carrying additional digits is received, then the I-MGCF shall generate a SAM and pass it to outgoing BICC/ISUP procedures. The SAM shall contain in its Subsequent Number parameter only the additional digits received in this SIP INFO request. + +#### 7.2.3.1.3A.3 Additional digits received in SIP INVITE requests + +If interworking of overlap signalling using the multiple INVITEs method is supported by the I-MGCF, the ISUP IAM message has already been sent, but no ISUP ACM or REL message has been received, and the I-MGCF receives an INVITE with the same Call-ID and From tag as a previous INVITE which was associated with a BICC/ISUP call/bearer control instance currently existing on the BICC/ISUP side, then: + +- If the number of digits in the Request-URI is greater than the number of digits already received for the communication, the I-MGCF shall generate a SAM and pass it to outgoing BICC/ISUP procedures. The SAM shall contain in its Subsequent Number parameter only the additional digits received in this Request-URI compared with the digits already received for the communication. The I-MGCF shall reply to any earlier INVITE with a 484 Address Incomplete response if this has not already been done. +- If the number of digits in the Request-URI is equal or less than the number of digits already received for the communication, then the I-MGCF shall immediately send a 484 Address Incomplete response for this INVITE. In this case, no SAM shall be sent to BICC/ISUP procedures. + + + +Sequence diagram for Figure 5b showing multiple overlapping INVITE messages. A box at the top represents the caller. Below it are three stacked black rectangles representing the callee's processing. Arrows point from the caller to each of the three rectangles, indicating multiple INVITE requests. Arrows also point from each rectangle back towards the caller, representing responses or processing steps. + +**Figure 5b: Receipt of subsequent INVITE for multiple INVITEs method overlap signalling** + +On sending of a 484 Address Incomplete message for an INVITE transaction, the I-MGCF considers any offer/answer exchange initiated by the INVITE to be terminated. The new INVITE initiates a new offer/answer exchange. However, if resources have already been reserved and they can be reused within the new offer/answer exchange, the precondition signalling shall reflect the current status of the affected preconditions. + +**7.2.3.1.4 Sending of 180 ringing** + +**7.2.3.1.4.0 General** + +The I-MGCF shall send the SIP 180 Ringing response when receiving any of the following messages: + +- ACM with Called party's status indicator set to subscriber free. + + + +Sequence diagram for Figure 6 showing the receipt of ACM. A vertical line represents the I-MGCF. An arrow labeled 'ACM (Subscriber Free)' points from the right towards the I-MGCF line. From the I-MGCF line, two arrows point to the left: a solid arrow labeled '180 Ringing' and a dashed arrow labeled 'P-Early-Media (1)'. Below these, another dashed arrow points left, labeled 'Ring tone'. + +**Figure 6: The receipt of ACM** + +**NOTE:** Whether the P-Early-Media header field is included depends on whether the received INVITE contains a P-Early-Media header field with the "supported" parameter as described in IETF RFC 5009 [89] or based on local policy. + +- CPG with Event indicator set to alerting + + + +I-MGCF + +Diagram showing the receipt of CPG (Alerting) by the I-MGCF. A vertical line represents the I-MGCF. To the left, '180 Ringing' and 'P-Early-Media (1)' are shown with a solid arrow pointing left. To the right, 'CPG (Alerting)' is shown with a solid arrow pointing left towards the I-MGCF. Below the I-MGCF line, a dashed line extends to the left, labeled 'Ring tone'. + +NOTE: Whether the P-Early-Media header field is included depends on whether the received INVITE contains a P-Early-Media header field with the "supported" parameter as described in IETF RFC 5009 [89] or based on local policy. + +**Figure 7: Receipt of CPG (Alerting)** + +For a speech call that is not identified as an "ICS call" as specified in clause 7.2.3.1.2.12, if the INVITE request includes the P-Early-Media header field, the I-MGCF shall include in the SIP 180 Ringing response a P-Early-Media header field authorizing backward early media, except when + +- the I-MGCF has already sent a reliable provisional response (see IETF RFC 3262 [54]) including a P-Early-Media header, as defined in IETF RFC 5009 [89], and +- the most recently sent P-Early-Media header field authorized backward early media. + +NOTE: If the I-MGCF signals the P-Early-Media header field authorizing backward early media, then the IMS can expect tones or announcements to the calling party to flow from the CS network via an MGW controlled by the I-MGCF. In particular, once the I-MGCF sends the 180 Ringing response, ringback is expected in media from the CS network. + +If the INVITE request doesn't include the P-Early-Media header field with the "supported" parameter and if the speech call is not identified as the "ICS call" as specified in clause 7.2.3.1.2.12, then as a network option the I-MGCF may include in the SIP 180 Ringing response a P-Early-Media header field authorizing backward early media. + +As a network option, an I-MGCF may generate a Call-Info header field, or an Alert-Info header field according to rules and procedures of IETF RFC 3261 [19] to provide media instead of the in-band media received from the PSTN. + +For the speech call identified as the "ICS call" as specified in clause 7.2.3.1.2.12, if the I-MGCF has received the P-Early-Media header field in the initial INVITE request, the I-MGCF shall include in the SIP 180 Ringing response the P-Early-Media header field indicating the backward early media is not authorised, except when: + +- the I-MGCF has already sent a reliable provisional response (see IETF RFC 3262 [54]) including a P-Early-Media header, as defined in IETF RFC 5009 [89]; and +- the most recently sent P-Early-Media header field did not authorize the backward early media. + +If the P-Early-Media header field with the "supported" parameter was not included in the initial INVITE request, then as a network option the I-MGCF may include in the SIP 180 Ringing response the P-Early-Media header field indicating the backward early media is not authorised for the "ICS call". + +#### 7.2.3.1.4.0a PSTN XML body + +The procedures in the present clause apply only if the I-MGCF supports the PSTN XML body as a network option. The I-MGCF shall map the Access Transport parameter received in the CPG or ACM into PSTN XML elements as shown in table 7a.0f and include this PSTN XML body in the 180 Ringing. + +**Table 7a.0f: Mapping of ISUP ATP Parameter into PSTN XML elements** + +| 18x | CPG or ACM | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|--------------------------| +| PSTN XML | ISUP Parameter | Content | +| ProgressIndicator | Access Transport Parameter | Progress indicator | +| HighLayerCompatibility (NOTE 2) | | High layer compatibility | +| LowLayerCompatibility (NOTE 2) | | Low layer compatibility | +| BearerCapability (NOTE 1, NOTE 2) | | Bearer Capability | +| BearerCapability (NOTE 1, NOTE 2) | Transmission medium used parameter (NOTE 1) | | +| NOTE 1: see clause 7.2.3.1.4.1 Transmission Medium Used parameter (TMU) | | | +| NOTE 2: The I-MGCF shall only provide this IE if it interworks media encoded in any of the formats in table 2a (G.711, Clearmode, or t38) without transcoding. If both TMU and a BC in the ATP have been received, the BC in the ATP shall be mapped. | | | + +The I-MGCF shall map a possibly available "ProgressIndicator" element in the ATP parameter within the ACM or CPG into a Progress Indicator in the PSTN XML body of the 180 Ringing. In addition, the I-MGCF shall map the Backward call indicators parameter and the Optional backward call indicators parameter (if present) within the ACM or CPG into other ProgressIndicator(s) in the PSTN XML body of the 180 Ringing as shown in table 7a.0g. + +NOTE: The order of ProgressIndicators within the same PSTN XML body is irrelevant. + +**Table 7a.0g: Mapping of ISUP BCI and optional BCI parameters into PSTN XML ProgressIndicator** + +| ← 180 Ringing | ←ACM or CPG | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PSTN XML body with ProgressIndicator with "Progress Description" value No (Value of PI) | Backward call indicators parameterOptional backward call indicators parameter | +| No. 1
("Call is not end-to-end ISDN: further call progress information may be available in-band") | Backward call indicators parameter
ISDN User Part indicator
0 "ISDN User Part not used all the way" | +| No. 2
("Destination address is non-ISDN") | Backward call indicators parameter
ISDN User Part indicator
1 "ISDN User Part used all the way"
ISDN access indicator
0 "Terminating access non-ISDN" | +| No. 7
("Terminating access ISDN") | Backward call indicators parameter
ISDN User Part indicator
1 "ISDN User Part used all the way"
ISDN access indicator
1 "Terminating access ISDN" | +| No. 8
("In-band information or an appropriate pattern is now available") | Optional backward call indicators parameter
In-band information indicator
"in-band information or an appropriate pattern is now available" | +| NOTE: The ProgressIndicator "Coding Standard" parameter shall be set to "00 (ITU-T standardized coding)". The default value for the ProgressIndicator "Location" parameter is "0011 (Transit Network)". | | + +#### 7.2.3.1.4.0b Fallback by I-MGCF + +If the I-MGCF supports the PSTN XML body as a network option and the I-MGCF received two PSTN XML Bearer Capability elements within the INVITE Request, but the succeeding trunk does not support TMR "64 kBit/s preferred" (as described in clause 7.2.3.1.2.5a), and if no corresponding elements were received in the Access Transport Parameter (see table 7a.0f), then the I-MGCF shall create a PSTN XML body containing the following elements, and include it in the 18x Response : + +- a BearerCapability element, which shall be copied from the first BearerCapability element received in the PSTN XML in the INVITE; +- if two HighLayerCompatibility elements were present in the PSTN XML body in the INVITE, then a HighLayerCompatibility element, which shall be copied from the first HighLayerCompatibility element received in the PSTN XML in the INVITE; and + +- a ProgressIndicator element with "Progress Description" value 5 ("Interworking has occurred and has resulted in a telecommunication service change"), "Coding Standard" value "00 (ITU-T standardized coding)", and default value "0011 (Transit Network)" for the "Location" parameter. + +#### 7.2.3.1.4.1 Fallback in a succeeding network: Transmission Medium Used parameter (TMU) received + +The procedures in the present clause apply only if the I-MGCF supports the PSTN XML body as a network option and receives a Transmission Medium Used parameter (TMU). + +NOTE: The I-MGCF will only receive a TMU parameter if it has applied the Fallback related procedures in clause 7.2.3.1.2.5a, including both a TMR and TMR Prime in the IAM, and fallback to the bearer capability identified in TMR Prime and USI occurred in a succeeding network. + +If the I-MGCF receives a Transmission Medium Used parameter (TMU) , the I-MGCF shall: + +- If an BC is not available in the ATP in the Address Complete Message (ACM) or Call Progress Message (CPG), map the TMU value (Speech or 3.1 kHz audio) to the PSTN XML BearerCapability; +- If an BC is available in the ATP in the Address Complete Message (ACM) or Call Progress Message (CPG), include the received BC value in the PSTN XML BearerCapability; +- configure the IM-MGW to use the second format in the m-line in the SDP that has been received in the INVITE as codec at the IMS termination; and +- send SDP selecting the second format in the m-line of the SDP that has been received in the INVITE as soon as allowed according to SIP rules. + +**Table 7.2.3.1.4.1.1: Sending of BC fallback indication** + +| ← 180 Ringing or 183 Session Progress | ←ACM/CPG | | +|--------------------------------------------------------------------------------|------------|---------------------------------------------------------------| +| PSTN XML BearerCapability = "Speech" | TMU
ATP | "Speech"
No BC | +| PSTN XML BearerCapability = "3.1 kHz audio" | TMU
ATP | "3.1 kHz audio"
No BC | +| PSTN XML BearerCapability received in the ATP
("speech" or "3.1 kHz audio") | TMU
ATP | "Speech or 3.1 kHz audio"
BC ("speech" or "3.1 kHz audio") | + +#### 7.2.3.1.4A Sending of 183 Session Progress for early media scenarios + +If SIP preconditions are used, the first 183 Session Progress will be sent after the reception of the INVITE request, before any ISUP message has been received from the CS network. The I-MGCF shall not include the P-Early-Media header field in any SIP message before it receives an ISUP ACM. + +For a speech call, which is not identified as an "ICS call" as specified in clause 7.2.3.1.2.12, upon receipt of one of the following messages and if the I-MGCF has received the P-Early-Media header field in the INVITE request, and has not already sent a provisional response including a P-Early-Media header field with parameters indicating authorization of early media with the same directionality as determined by table 7.2.3.1.4A.1 or table 7.2.3.1.4A.2, then the I-MGCF shall send the 183 Session Progress response with a P-Early-Media header field authorizing early media as indicated: + +- ACM with the value of the called party's status indicator "no indication" and one of the options described in table 7.2.3.1.4A.1 If the I-MGCF supports the PSTN XML body as a network option, the I-MGCF shall map parameters within the ACM into the PSTN XML body within the 183 as indicated in table 7.2.3.1.4A.1. Based on local configuration, the I-MGCF may also send a 183 Session Progress response with a P-Early-Media header field authorizing early media if it receives an ACM with other parameters than described in table 7.2.3.1.4A.1. + + + +I-MGCF + +Diagram showing the receipt of an ACM 'No indication' message. A vertical line represents the I-MGCF. To the left, '183 Progress' and 'P-Early-Media' are shown with a solid arrow pointing left. To the right, 'ACM (No indication)' is shown with a solid arrow pointing left towards the I-MGCF. Below the I-MGCF, a dashed arrow points left, labeled 'appropriate announcement'. + +**Figure 7c: Receipt of ACM "No indication"** + +**Table 7.2.3.1.4A.1: ACM Parameters that trigger the 183 Session Progress response** + +| ← 183 Session Progress | ← ACM | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| P-Early-Media header field authorizing backward early media, if not already sent (NOTE 2)
PSTN XML with ProgressIndicator with "Progress Description" value No. 8 ("In-band information or appropriate pattern is now available") (NOTE 1) | Optional backward call indicators parameter
In-band information indicator
1 "In-band info or an appropriate pattern is now available" | +| PSTN XML with ProgressIndicator with "Progress Description" value No. 1 ("Call is not end-to-end ISDN: further call progress information may be available in-band") (NOTE 1) | Backward call indicators parameter
ISDN User Part indicator
0 "ISDN User Part not used all the way" | +| PSTN XML with ProgressIndicator with "Progress Description" value No. 2 ("Destination address is non-ISDN") (NOTE 1) | Backward call indicators parameter
ISDN User Part indicator
1 "ISDN User Part used all the way"
ISDN access indicator
0 "Terminating access non-ISDN" | +| PSTN XML with ProgressIndicator with "Progress Description" value No. 7 ("Terminating access ISDN") (NOTE 1) | Backward call indicators parameter
ISDN User Part indicator
1 "ISDN User Part used all the way"
ISDN access indicator
1 "Terminating access ISDN" | +| P-Early-Media header field authorizing both-way early media, if not already sent (NOTE 2) | UID action indicators parameter
Through-connection instruction indicator
1 "through-connect in both directions" | +| NOTE 1: The ProgressIndicator "Coding Standard" parameter shall be set to "00 (ITU-T standardized coding)". The default value for the ProgressIndicator "Location" parameter is "0011 (Transit Network)". | | +| NOTE 2: Setting of the P-Early-Media header field based on the UID action indicators parameter value of "through-connect in both directions" takes precedence over setting based on the Optional backward call indicators parameter value of "In-band info or an appropriate pattern is now available". | | + +NOTE 1: As a network option the I-MGCF can also map ACM into 183 in other cases than those described in table 7.2.3.1.4A.1. + +- CPG message, when: + +1. Event indicator is set to "in-band information or an appropriate pattern is now available", or +2. Event indicator is set to "Progress" and one of the options described in table 7.2.3.1.4A.2. + + + +I-MGCF + +Diagram showing the receipt of CPG (in-band information available) by the I-MGCF. A solid arrow labeled '183 Progress P-Early-Media' points left from the I-MGCF. A solid arrow labeled 'CPG (in-band information available)' points right towards the I-MGCF. A dashed arrow labeled 'appropriate announcement' points left from the I-MGCF. + +**Figure 7d: Receipt of CPG (in-band information available)** + +**Table 7.2.3.1.4A.2: CPG Parameters that trigger the 183 Session Progress response** + +| ←183 Session Progress | ←CPG | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| P-Early-Media header field authorizing backward early media, if not already sent (NOTE 4)
PSTN XML with ProgressIndicator with "Progress Description" value No. 8 ("In-band information or appropriate pattern is now available") (NOTE 3) | Event indicator
000 0010 (progress)
Optional backward call indicators parameter
In-band information indicator
1 "In-band info or an appropriate pattern is now available" | +| PSTN XML with ProgressIndicator with "Progress Description" value No. 1 (Call is not end-to-end ISDN: further progress information may be available in-band") (NOTE 3) | Event indicator
000 0010 (progress)
Backward call indicators parameter
ISDN User Part indicator
0 "ISDN User Part not used all the way" | +| PSTN XML with ProgressIndicator with "Progress Description" value No. 2 ("Destination address is non-ISDN") (NOTE 3) | Backward call indicators parameter
ISDN User Part indicator
1 "ISDN User Part used all the way"
ISDN access indicator
0 "Terminating access non-ISDN" | +| PSTN XML with ProgressIndicator with "Progress Description" value No. 7 ("Terminating access ISDN") (NOTE 3) | Backward call indicators parameter
ISDN User Part indicator
1 "ISDN User Part used all the way"
ISDN access indicator
1 "Terminating access ISDN" | +| P-Early-Media header field authorizing both-way early media, if not already sent (NOTE 4) | UID action indicators parameter
Through-connection instruction indicator
1 "through-connect in both directions" | + +NOTE 1: The mapping of the contents in the CPG message is only relevant if the information received in the message is different compared to earlier received information, e.g., in the ACM message or a CPG message received prior to this message. + +NOTE 2: 183 Session Progress message including a P-Early-Media header authorizing early media may only be sent for a speech call. + +NOTE 3: The ProgressIndicator "Coding Standard" parameter shall be set to "00 (ITU-T standardized coding)". The default value for the ProgressIndicator "Location" parameter is "0011 (Transit Network)". + +NOTE 4: Setting of the P-Early-Media header field based on the UID action indicators parameter value of "through-connect in both directions" takes precedence over setting based on the Optional backward call indicators parameter value of "In-band info or an appropriate pattern is now available". + +NOTE 2: As a network option the I-MGCF can also map CPG into 183 in other cases than those described in table 7.2.3.1.4A.1. + +If the INVITE request doesn't include the P-Early-Media header field with the "supported" parameter, then as a network option the I-MGCF may include in the SIP 180 Ringing response a P-Early-Media header field authorizing early media. + +If the I-MGCF supports the PSTN XML body as a network option, the I-MGCF shall map the Access Transport Parameter received in the CPG or ACM into PSTN XML elements as shown in table 7a.0f and include this XML body + +in the 183 Session Progress. The I-MGCF shall include both a ProgressIndicator mapped from possibly received Progress indicator element in the Access Transport Parameter and ProgressIndicators derived according to table 7.2.3.1.4A.1 or table 7.2.3.1.4A.2 in the PSTN XML body. + +NOTE 3: The order of ProgressIndicators within the same PSTN XML body is irrelevant. + +If the I-MGCF has applied UDI-TA fallback related procedures in clause 7.2.3.1.2.5a, the I-MGCF shall also apply the procedures in clauses 7.2.3.1.4.0b and 7.2.3.1.4.1, including the PSTN XML body in the 183 Session Progress. + +As a network option, an I-MGCF may generate a Call-Info header field, or an Alert-Info header field according to rules and procedures of IETF RFC 3261 [19] to provide media instead of the in-band media received from the PSTN. + +If the ACM or CPG contains an ISUP Cause, the MGCF may add a Reason header field containing the received Cause Value to the SIP 183 Session Progress provisional response as a network option. The mapping of the Cause Indicators parameter to the Reason header as shown in table 9a shall be applied. IETF RFC 6432 [115] describes the use of the Reason header field in responses. The Reason header field itself is described in IETF RFC 3326 [116]. + +#### 7.2.3.1.4B Sending of 181Call is being forwarded + +The I-MGCF shall send the SIP 181 Call is being forwarded when receiving any of the following messages: + +- ACM with call diversion information not indicating that presentation is not allowed and optional backward call indicators indicate that in-band information is available. + + + +Diagram of Figure 7c: The receipt of ACM (call diversion information). The diagram shows the I-MGCF at the top. On the left, '181 Call is being forwarded' and 'P-Early-Media (1)' are shown. A solid arrow points from the I-MGCF to the left for 'ACM( call diversion information)'. A dashed arrow points from the I-MGCF to the left for 'Audio'. + +NOTE 1: Whether the P-Early-Media header field is included depends on whether the received INVITE contains a P-Early-Media header field with the "supported" parameter as described in IETF RFC 5009 [89] or based on local policy. + +**Figure 7c: The receipt of ACM (call diversion information)** + +- CPG with call diversion information not indicating that presentation is not allowed and optional backward call indicators indicate that in-band information is available. + + + +Diagram of Figure 7d: Receipt of CPG (Call diversion information). The diagram shows the I-MGCF at the top. On the left, '181 Call is being forwarded' and 'P-Early-Media (1)' are shown. A solid arrow points from the I-MGCF to the left for 'CPG(Call diversion information)'. A dashed arrow points from the I-MGCF to the left for 'Audio'. + +NOTE 1: Whether the P-Early-Media header field is included if the received INVITE contains a P-Early-Media header field with the "supported" parameter as described in IETF RFC 5009 [89] or based on local policy. + +**Figure 7d: Receipt of CPG (Call diversion information)** + +For a speech call, and if the INVITE request includes the P-Early-Media header, the I-MGCF shall include in the SIP 181 Call is being forwarded response a P-Early-Media header authorizing early media, except when + +- the I-MGCF has already sent a reliable provisional response including a P-Early-Media header field, as defined in IETF RFC 5009 [89], or a 180 Ringing response; and +- the most recently sent P-Early-Media header field authorized early media. + +NOTE: If the I-MGCF signals the P-Early-Media header field authorizing early media, then the IMS can expect tones or announcements to the calling party to flow from the CS network via an MGW controlled by the I-MGCF. + +If the INVITE request doesn't include the P-Early-Media header field with the "supported" parameter, then as a network option the I-MGCF may include in the SIP 180 Ringing response a P-Early-Media header field authorizing early media. + +#### 7.2.3.1.4C Sending of 183 Session Progress for overlap signalling using the in-dialog method + +If the I-MGCF supports the network option of overlap signalling using the in-dialog method, and the SIP INVITE request contained an indication that the 100rel extension is supported or required, the I-MGCF shall send a reliable 183 (Session Progress) response immediately after the reception of an INVITE request. + +NOTE: If the INVITE request does not contain an indication that the 100rel extension is supported or required, it is assumed that overlap is not used, and that no further digits will be received. + +#### 7.2.3.1.4D Sending of 183 Session Progress to carry ISUP Cause + +If the I-MGCF receives an ACM or CPG message containing an ISUP Cause, and if the I-MGCF does not send any SIP provisional response due to interworking procedures described in clauses 7.2.3.1.4A, for the ACM or CPG message, the I-MGCF may send a SIP 183 Session Progress with a Reason header field containing the received Cause Value as a network option. The mapping of the Cause Indicators parameter to the Reason header as shown in table 9a shall be applied. IETF RFC 6432 [115] describes the use of the Reason header field in responses. The Reason header field itself is described in IETF RFC 3326 [116]. + + + +Diagram illustrating the receipt of ACM or CPG with ISUP Cause. A vertical line represents the I-MGCF. To the right of the line, 'ACM or CPG (Cause=xxx)' is shown. An arrow points from this text, across the line, to the left. To the left of the line, '183 Session Progress (Reason(Cause=xxx))' is shown, indicating the response sent by the I-MGCF. + +**Figure 7.2.3.1.4D.1: The receipt of ACM or CPG with ISUP Cause** + +#### 7.2.3.1.4E Sending of 183 Session Progress for ICS call + +For a speech call identified as an "ICS call" as specified in clause 7.2.3.1.12 if the I-MGCF has received: + +- ACM message with the value of the called party's status indicator "*no indication*" and the optional backward call indicators parameter field with the in-band information indicator set to "*in-band information or an appropriate pattern is now available*"; or +- CPG message with the event indicator of the event information parameter field set to: + - 1 "*in-band information or an appropriate pattern is now available*"; or + - 2 "*progress*" and the optional backward call indicators parameter field with the in-band information indicator set to "*in-band information or an appropriate pattern is now available*"; and +- if the received ACM or CPG message does not contain the cause indicators parameter field then: + - a) if the I-MGCF has received a P-Early-Media header field in the initial INVITE request; and + - b) the I-MGCF has not already sent a provisional response including the P-Early-Media header field with parameters indicating that a backward early media is not authorised; + +the I-MGCF shall send the 183 Session Progress response with the P-Early-Media header field indicating the backward early media is not authorised. If the I-MGCF supports a PSTN XML body as a network option, the I-MGCF shall map parameters within the ACM or CPG message into the PSTN XML body within the 183 Session Progress response as indicated in clause 7.2.3.1.4A; or + +- otherwise if the received ACM or CPG message contains the cause indicators parameter field the I-MGCF shall send a final response to the initial INVITE request according to table 9 in clause 7.2.3.1.8 with a Reason header field containing the received (Q.850) cause value. The mapping of the cause indicators parameter field to the Reason header field as shown in table 9a shall be applied. IETF RFC 6432 [115] describes the use of the Reason header field in responses. The Reason header field itself is described in IETF RFC3326 [116]. + +#### 7.2.3.1.5 Sending of the 200 OK (INVITE) + +The following cases are possible trigger conditions for sending the 200 OK (INVITE): + +- The reception of the ANM. + + + +A sequence diagram illustrating the interaction for Figure 8. A vertical line represents the I-MGCF. An arrow labeled 'ANM' points from the right towards the I-MGCF line. From the I-MGCF line, an arrow labeled '200 OK (INVITE)' points to the left. + +Sequence diagram showing the receipt of ANM by I-MGCF and the subsequent sending of 200 OK (INVITE). + +**Figure 8: Receipt of ANM** + +- The reception of the CON message. + + + +A sequence diagram illustrating the interaction for Figure 9. A vertical line represents the I-MGCF. An arrow labeled 'CON' points from the right towards the I-MGCF line. From the I-MGCF line, an arrow labeled '200 OK (INVITE)' points to the left. + +Sequence diagram showing the receipt of CON by I-MGCF and the subsequent sending of 200 OK (INVITE). + +**Figure 9: Receipt of CON** + +If the I-MGCF supports the PSTN XML body as a network option, the I-MGCF shall map the Access Transport Parameter received in the ANM or CON into PSTN XML elements as shown in table 7.2.3.1.5.1 and include this PSTN XML body in the 200 OK (INVITE). + +On receipt of an ANM/CON message containing the ATP including the Bearer Capability set to "unrestricted digital information with tones/announcement" without TMU parameter the 200 OK message shall contain the PSTN XML Bearer Capability "unrestricted digital information with tones/announcement". + +If the I-MGCF supports the PSTN XML body as a network option, the I-MGCF shall map an available BCI element in the ANM or CON into a ProgressIndicator in the PSTN XML body as shown in table 7.2.3.1.5.2; the I-MGCF shall include both a ProgressIndicator mapped from possibly received Progress indicator element in the Access Transport Parameter and ProgressIndicators derived according to table 7.2.3.1.5.2 in the PSTN XML. + +NOTE 1: The order of ProgressIndicators within the same PSTN XML body is irrelevant. + +**Table 7.2.3.1.5.1: Mapping of ISUP ATP Parameter into PSTN XML elements** + +| 200 OK | ANM or CON | | +|-----------------------------------|---------------------------------------------|--------------------------| +| PSTN XML | ISUP Parameter | Content | +| ProgressIndicator | Access Transport Parameter | Progress indicator | +| HighLayerCompatibility (NOTE 2) | | High layer compatibility | +| LowLayerCompatibility (NOTE 2) | | Low layer compatibility | +| BearerCapability (NOTE 1, NOTE 2) | | Bearer Capability | +| BearerCapability (NOTE 1, NOTE 2) | Transmission medium used parameter (NOTE 1) | | + +NOTE 1: see clause 7.2.3.1.4.1 Transmission Medium Used parameter (TMU) +NOTE 2: The I-MGCF shall only provide this IE if it interworks media encoded in any of the formats in table 2a (G.711, Clearmode, or t38) without transcoding. If both TMU and a BC in the ATP have been received, the BC in the ATP shall be mapped. + +**Table 7.2.3.1.5.2: Mapping of ISUP BCI and optional BCI parameters into PSTN XML +ProgressIndicator** + +| ← 200 OK | ←ANM or CON | +|------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PSTN XML body with ProgressIndicator with "Progress Description" value No (Value of PI) (NOTE) | Content
Backward call indicators parameter
Optional backward call indicators parameter | +| No. 1
("Call is not end-to-end ISDN: further call progress information may be available in-band") | Backward call indicators parameter
ISDN User Part indicator
0 "ISDN User Part not used all the way" | +| No. 2
("Destination address is non-ISDN") | Backward call indicators parameter
ISDN User Part indicator
1 "ISDN User Part used all the way"
ISDN access indicator
0 "Terminating access non-ISDN" | +| No. 7
("Terminating access ISDN") | Backward call indicators parameter
ISDN User Part indicator
1 "ISDN User Part used all the way"
ISDN access indicator
1 "Terminating access ISDN" | +| No. 8
("In-band information or an appropriate pattern is now available") | Optional backward call indicators parameter
In-band information indicator
1 "in-band information or an appropriate pattern is now available" | + +NOTE: The ProgressIndicator "Coding Standard" parameter shall be set to "00 (ITU-T standardized coding)". The default value for the ProgressIndicator "Location" parameter is "0011 (Transit Network)". + +If the I-MGCF supports the PSTN XML body and receives a Transmission Medium Used (TMU) parameter, + +NOTE 2: The I-MGCF will only receive a TMU parameter if it has applied the Fallback related procedures in clause 7.2.3.1.2.5a, including both a USI and TMR Prime parameter in the IAM, and fallback to the bearer capability identified in USI and TMR Prime occurred at the terminating side. + +Then the I-MGCF shall: + +- if a BC is not available in the ATP in the ANM or CON, map the TMU value (Speech or 3.1 kHz audio) to the PSTN XML BearerCapability element; +- if a BC is available in the ATP in the ANM or CON, include the received BC in the PSTN XML BearerCapability element; +- configure the IM-MGW to use the second format in the m-line in the SDP that has been received in the INVITE as codec at the IMS termination; and +- send SDP selecting the second format in the m-line of the SDP that has been received in the INVITE as soon as allowed according to SIP rules. + +If the I-MGCF supports the PSTN XML body, has applied the Fallback related procedures in clause 7.2.3.1.2.5a, including both a TMR and TMR Prime in the IAM, and did not receive TMU in the ANM, CON, or any previous ISUP message, + +NOTE 3: Fallback to the bearer capability identified in TMR did not occur at the terminating side. + +Then the I-MGCF shall: + +- configure the IM-MGW to use the first format in the m-line in the SDP offer that has been received in the INVITE as codec at the IMS termination; and +- send SDP selecting the first format in the m-line in the SDP offer at the first possibility according to SIP rules. + +#### 7.2.3.1.6 Sending of the Release message (REL) + +The following are possible triggers for sending the Release message: + +- Receipt of the BYE method + + + +``` + +graph LR + BYE[BYE] --> I-MGCF[I-MGCF] + I-MGCF --> REL[REL] + +``` + +Diagram illustrating the receipt of the BYE method. An arrow labeled 'BYE' points from the left to a vertical line representing the I-MGCF. From the I-MGCF, an arrow labeled 'REL' points to the right. + +**Figure 10: Receipt of the Bye method** + +- Receipt of the CANCEL method + + + +``` + +graph LR + CANCEL[CANCEL] --> I-MGCF[I-MGCF] + I-MGCF --> REL[REL] + +``` + +Diagram illustrating the receipt of the CANCEL method. An arrow labeled 'CANCEL' points from the left to a vertical line representing the I-MGCF. From the I-MGCF, an arrow labeled 'REL' points to the right. + +**Figure 11: Receipt of Cancel method** + +Additional triggers are contained in table 10. + +#### 7.2.3.1.7 Coding of the REL + +Coding of the REL message depends on the Reason header field (specified in IETF RFC 3326 [116]) contained in the BYE or CANCEL request. + +If the Reason header field is missing or does not contain a cause parameter then the ISUP Cause Value in the REL message shall be coded as shown in table 8. + +If the Reason header field contains a protocol header field parameter set to "Q.850" then the ISUP Cause Value shall be coded as shown in table 8a. + +If the Reason header field contains a protocol header field parameter set to "SIP" then, as a network option, the ISUP Cause Value may be coded as shown in table 8aa. + +The Location Field shall be set to "*network beyond interworking point*". If, as a network option, the I-MGCF supports the location header field parameter as described in IETF RFC 8606 [155], the I-MGCF shall instead derive the ISUP cause location from the location parameter in the SIP Reason header field as shown in table 8c. + +**Table 8: Coding of REL** + +| SIP Message | REL | +|--------------------|-------------------------------------------| +| Request | cause indicators parameter | +| BYE | Cause value No. 16 (Normal call clearing) | +| CANCEL | Cause value No. 16 (Normal call clearing) | + +**Table 8a: Mapping of SIP Reason header field into Cause Indicators parameter – Q.850 protocol case** + +| Component of SIP Reason header field | Component value | BICC/ISUP Parameter field | Value | +|---------------------------------------------|------------------------|----------------------------------|-------------------------------------| +| Protocol | "Q.850" | Cause Indicators parameter | - | +| protocol-cause | "cause = XX" (NOTE 1) | Cause Value | "XX" (NOTE 1) | +| - | - | Location | "network beyond interworking point" | + +NOTE: "XX" is the Cause Value as defined in ITU-T Recommendation Q.850 [38]. + +**Table 8aa: Mapping of SIP Reason header field into Cause Indicators parameter - SIP protocol case** + +| Component of SIP Reason header field | Component value | BICC/ISUP Parameter field | Value (NOTE 2) | +|---------------------------------------------|------------------------|----------------------------------|-------------------------------------| +| Protocol | "SIP" | Cause Indicators parameter | - | +| protocol-cause | "cause = 200" (NOTE 1) | Cause Value | "13" (Call completed elsewhere) | +| - | - | Location | "network beyond interworking point" | + +NOTE 1: The usage of SIP response codes such as "200" is specified in 3GPP TS 24.229 [9]. +NOTE 2: The ISUP Cause Value in the REL message shall be coded as shown in table 8 if the connected CS network is other operator's network, except when a bilateral agreement for use of the cause value(s) exists between the operators. + +NOTE: The mapping of reason headers towards the ISDN can be misused due to possible user creation of the reason header since there is no screening in IMS. + +If the I-MGCF supports this PSTN XML body as a network option and the I-MGCF interworks media encoded in any of the formats in table 2a (G.711, Clearmode or t38) without transcoding, and if a PSTN XML body is received in the BYE or CANCEL request, the I-MGCF shall derive the Access Transport Parameter in the REL message from the PSTN XML body as shown in table 8b. + +**Table 8b: Mapping of PSTN XML elements into ISUP Parameters** + +| BYE or CANCEL | REL | | +|------------------------|----------------------------|--------------------------| +| PSTN XML | ISUP Parameter | Content | +| HighLayerCompatibility | Access Transport Parameter | High layer compatibility | +| LowLayerCompatibility | | Low layer compatibility | + +**Table 8c: Mapping of SIP Reason header field location parameter into Cause Indicator Location parameter** + +| Component of SIP Reason header field | Component value | BICC/ISUP Parameter field | Value | +|--------------------------------------|-----------------|---------------------------|-----------------------------------------| +| location | U | Location | user | +| | LPN | | private network serving the local user | +| | LN | | public network serving the local user | +| | TN | | transit network | +| | RLN | | public network serving the remote user | +| | RPN | | private network serving the remote user | +| | LOC-6 | | network beyond interworking point | +| | INTL | | international network | +| | LOC-8 | | network beyond interworking point | +| | LOC-9 | | network beyond interworking point | +| | BI | | network beyond interworking point | +| | LOC-11 | | network beyond interworking point | +| | LOC-12 | | network beyond interworking point | +| | LOC-13 | | network beyond interworking point | +| | LOC-14 | | network beyond interworking point | +| | LOC-15 | | network beyond interworking point | + +NOTE: The interworking of the location value as described in this table is a network option. + +#### 7.2.3.1.8 Receipt of the Release Message + +If the REL message is received and a final response (i.e. 200 OK (INVITE)) has already been sent, the I-MGCF shall send a BYE message. + +NOTE: According to SIP procedures, in the case that the REL message is received and a final response (e.g. 200 OK (INVITE)) has already been sent (but no ACK request has been received) on the incoming side of the I-MGCF then the I-MGCF does not send a 487 Request terminated response and instead waits until the ACK request is received before sending a BYE message. + +If the REL message is received and the final response (i.e. 200 OK (INVITE)) has not already been sent, the I-MGCF shall send a Status-Code 4xx (Client Error), 5xx (Server Error) or 6xx (Global Failure) response. The Status code to be sent is determined by examining the Cause value received in the REL message. Table 9 specifies the mapping of the cause values, as defined in ITU-T Recommendation Q.850 [38], to SIP response status codes. Cause values not appearing in the table shall have the same mapping as the appropriate class defaults according to ITU-T Recommendation Q.850 [38]. + +**Table 9: Receipt of the Release message (REL)** + +| ← SIP Message | ← REL | +|-------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------| +| Status code | Cause indicators parameter | +| 404 Not Found | Cause value No 1 (Unallocated (unassigned) number) | +| 604 Does not exist anywhere | Cause value No 2 (No route to specified transit network) | +| 604 Does not exist anywhere | Cause value No 3 (No route to destination) | +| 500 Server Internal error | Cause value No 4 (Send special information tone) | +| 404 Not Found | Cause value No 5 (Misdialed trunk prefix) | +| 486 Busy Here | Cause value No 17 (User busy) | +| 408 Request Timeout IF "ICS call"
(NOTE 4)
ELSE 480 Temporarily unavailable | Cause value No 18 (No user responding) | +| 480 Temporarily unavailable | Cause value No 19 (No answer from user (user alerted)) | +| 408 Request Timeout IF "ICS call"
(NOTE 4)
ELSE 480 Temporarily unavailable | Cause value No 20 (Subscriber absent) | +| 603 Decline IF location field is set to user
ELSE 403 Forbidden | Cause value No 21 (Call rejected) | +| 410 Gone | Cause value No 22 (Number changed) | +| 410 Gone | Cause value No 23 (Redirection to new destination) | +| 433 Anonymity Disallowed (NOTE 1) | Cause value No 24 (Call rejected due to feature at the destination) | +| 483 Too Many Hops | Cause value No 25 (Exchange routing error) | +| 480 Temporarily unavailable | Cause value No 26 (Non-selected user clearing) | +| 502 Bad Gateway | Cause value No 27 (Destination out of order) | +| 484 Address Incomplete | Cause value No 28 (Invalid number format (address incomplete)) | +| 501 Not Implemented | Cause value No 29 (Facility rejected) | +| 480 Temporarily unavailable | Cause value No 31 (Normal, unspecified)
(class default) (NOTE 2) | +| 486 Busy here if Diagnostics indicator
includes the (CCBS indicator = CCBS
possible)
else 503 Service Unavailable (NOTE 3) | Cause value No 34 (No circuit/channel available) | +| 500 Server Internal error | Cause value No 38 (Network out of order) | +| 503 Service Unavailable (NOTE 3) | Cause value No 41 (Temporary failure) | +| 503 Service Unavailable (NOTE 3) | Cause value No 42 (Switching equipment congestion) | +| 500 Server Internal error | Cause value No 43 (Access information discarded) | +| 503 Service Unavailable (NOTE 3) | Cause value No 44 (Requested channel not available) | +| 500 Server Internal error | Cause value No 46 (Precedence call blocked) | +| 503 Service Unavailable (NOTE 3) | Cause value No 47 (Resource unavailable, unspecified)
(class default) | +| 488 Not acceptable here | Cause value No 50 (Requested facility not subscribed) | +| 603 Decline | Cause value No 55 (Incoming class barred within Closed User Group
(CUG)) | +| 603 Decline | Cause value No 57 (Bearer capability not authorised) | +| 503 Service Unavailable (NOTE 3) | Cause value No 58 (Bearer capability not presently available) | +| 501 Not Implemented | Cause value No 63 (Service option not available, unspecified)
(class default) | +| 500 Server Internal error | Cause value No 65 (Bearer capability not implemented) | +| 501 Not Implemented | Cause value No 69 (Requested facility not implemented) | +| 501 Not Implemented | Cause value No 70 (Only restricted digital information capability is
available) | +| 501 Not Implemented | Cause value No 79 (Service or option not implemented, unspecified)
(class default) | +| 403 Forbidden | Cause value No 87 (User not member of Closed User Group (CUG)) | +| 606 Not Acceptable | Cause value No 88 (Incompatible destination) | +| 403 Forbidden | Cause value No 90 (Non existing Closed User Group (CUG)) | +| 500 Server Internal error | Cause value No 91 (Invalid transit network selection) | +| 513 Message too large | Cause value No 95 (Invalid message, unspecified)
(class default) | +| 501 Not Implemented | Cause value No 97 (Message type non-existent or not implemented) | +| 501 Not Implemented | Cause value No 98 (Message not compatible with call state or
message type non-existent or not implemented) | +| 501 Not Implemented | Cause value No 99 (Information element/parameter non-existent or
not implemented) | +| 504 Server timeout | Cause value No 102 (Recovery on timer expiry) | + +| ←SIP Message | ← REL | +|---------------------------|---------------------------------------------------------------------------| +| Status code | Cause indicators parameter | +| 501 Not Implemented | Cause value No 103 (Parameter non-existent or not implemented, passed on) | +| 501 Not Implemented | Cause value No 110 (Message with unrecognised parameter, discarded) | +| 400 Bad Request | Cause value No 111 (Protocol error, unspecified) (class default) | +| 500 Server Internal error | Cause value No 127 (Interworking, unspecified) (class default) | + +NOTE 1: Anonymity Disallowed, IETF RFC 5079 [77] refers +NOTE 2: Class 0 and class 1 have the same default value. +NOTE 3: No Retry-After header field shall be included. +NOTE 4: The I-MGCF identifies a call as an "ICS call" as specified in clause 7.2.3.1.2.12. + +A Reason header field containing the received (Q.850) Cause Value of the REL shall be added to the SIP final response or BYE request sent as a result of this subclause. The mapping of the Cause Indicators parameter to the Reason header is shown in table 9a. IETF RFC 6432 [115] describes the use of the Reason header field in responses. The Reason header field itself is described in IETF RFC 3326 [116]. If, as a network option, the I-MGCF supports the location header field parameter as described in IETF RFC 8606 [155], the I-MGCF shall map the ISUP cause location to the location parameter in the SIP Reason header field as shown in table 9a. + +**Table 9a: Mapping of Cause Indicators parameter into SIP Reason header fields** + +| Cause indicators parameter field | Value of parameter field | component of SIP Reason header field | component value | +|----------------------------------|-----------------------------------------|--------------------------------------|--------------------------------------------------------------------------------------------------| +| - | - | protocol | "Q.850" | +| Cause Value | "XX" (NOTE 1) | protocol-cause | "cause = XX" (NOTE 1) | +| - | - | reason-text | Should be filled with the definition text as stated in ITU-T Recommendation Q.850 [38]. (NOTE 2) | +| Location (NOTE 3) | user | location | U | +| | private network serving the local user | | LPN | +| | public network serving the local user | | LN | +| | transit network | | TN | +| | public network serving the remote user | | RLN | +| | private network serving the remote user | | RPN | +| | international network | | INTL | +| | network beyond interworking point | | BI | +| | | | | + +NOTE 1: "XX" is the Cause Value as defined in ITU-T Recommendation Q.850 [38]. +NOTE 2: Due to the fact that the Cause Indicators parameter does not include the definition text as defined in table 1/Q.850 [38], this is based on provisioning in the I-MGCF. +NOTE 3: The mapping of the cause location is a network option. + +As a network option, an I-MGCF may generate an Error-Info header field according to rules and procedures of IETF RFC 3261 [19] to provide media instead of the in-band media received from the PSTN. + +If the I-MGCF supports the PSTN XML body as a network option, the I-MGCF shall map the Access Transport Parameter received in the REL into PSTN XML elements as shown in table 9aa and include this PSTN XML body in the SIP final response or BYE. + +**Table 9aa: Mapping of ISUP Parameters into PSTN XML elements** + +| 4xx,5xx,6xx or BYE | REL | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|--------------------------| +| PSTN XML | ISUP Parameter | Content | +| ProgressIndicator | Access Transport Parameter | Progress indicator | +| HighLayerCompatibility (NOTE) | | High layer compatibility | +| LowLayerCompatibility (NOTE) | | Low layer compatibility | +| NOTE: The I-MGCF shall only provide this IE if it interworks media encoded in any of the formats in table 2a (G.711, Clearmode, or t38) without transcoding, | | | + +### 7.2.3.1.9 Receipt of RSC, GRS or CGB (H/W oriented) + +Upon receipt of a RSC, GRS or CGB (H/W oriented) message the following applies independently for each affected circuit: + +- NOTE: For the RSC message, the circuit identified by the CIC is affected. + For the GRS message, the affected circuits are identified by the CIC and the Range subfield of the Range and Status parameter. + For the CGB message, the affected circuits are identified by the CIC and the Range and Status parameter. + +If an initial address message has been sent for the affected circuit and after at least one backward message relating to that call has been received then: + +- If the final response (i.e. 200 OK (INVITE)) has already been sent, the I-MGCF shall send a BYE message. +- If the final response (i.e. 200 OK (INVITE)) has not already been sent, the I-MGCF shall send a SIP response with Status-Code 480 Temporarily Unavailable. + +A Reason header field containing the (Q.850) Cause Value of the REL message generated by the ISUP procedures shall be added to the SIP message (BYE or 480 response) to be sent by the SIP side of the I-MGCF. + +### 7.2.3.1.9a Receipt of REFER + + + +The diagram shows a vertical line representing a timeline. A horizontal arrow points from the right towards this line. Above the timeline is a black rectangular block with a white horizontal bar at the top, likely representing a SIP message or a call state. + +Diagram illustrating the receipt of REFER method. It shows a vertical timeline with a horizontal arrow pointing left towards it from the right side. Above the timeline is a black rectangular block with a white horizontal bar at the top. + +**Figure 11a: Receipt of REFER method** + +Upon receipt of a REFER request at the MGCF, the default behaviour of the I-MGCF is to reject the REFER request with a 403 Forbidden response. + +NOTE: The I-MGCF may also decide for example to execute the REFER request as specified in IETF RFC 3515 [75] as an operator option, but such handling is outside of the scope of the present document. + +#### 7.2.3.1.10 Autonomous Release at I-MGCF + +Table 10 shows the trigger events at the MGCF and the release initiated by the MGCF when the call is traversing from SIP to ISUP/BICC. + +A Reason header field containing the (Q.850) Cause Value of the REL message sent by the I-MGCF shall be added to the SIP Message (BYE request or final response) sent by the SIP side of the I-MGCF. + +**Table 10: Autonomous Release at I-MGCF** + +| SIP Response | Trigger event | REL cause parameter | +|------------------------------|------------------------------------------------------------------|------------------------------------| +| 484 Address Incomplete | Determination that insufficient digits received. | Not sent. | +| 480 Temporarily Unavailable | Congestion at the MGCF/Call is not routable. | Not sent. | +| BYE | ISUP/BICC procedures result in release after answer | According to ISUP/BICC procedures. | +| BYE | SIP procedures result in release after answer. | 127 (Interworking unspecified) | +| 500 Server Internal error | Call release due to the ISUP/BICC compatibility procedure (NOTE) | According to ISUP/BICC procedures. | +| 484 Address Incomplete | Call release due to expiry of T7 within the ISUP/BICC procedures | According to ISUP/BICC procedures. | +| 480 Temporarily Unavailable | Call release due to expiry of T9 within the BICC/ISUP procedures | According to BICC/ISUP procedures. | +| 480 Temporarily Unavailable. | Other BICC/ISUP procedures result in release before answer. | According to BICC/ISUP procedures. | + +NOTE: MGCF receives unrecognized ISUP or BICC signalling information and determines that the call needs to be released based on the coding of the compatibility indicators, refer to ITU-T Recommendation Q.764 [4] and ITU-T Q.1902.4 [30]. + +#### 7.2.3.1.11 Internal through connection of the bearer path + +The through connection procedure is described in clause 9.2.2.3.5. + +### 7.2.3.2 Outgoing Call Interworking from ISUP to SIP at O-MGCF + +#### 7.2.3.2.1 Sending of INVITE + +##### 7.2.3.2.1.1 General + + + +The diagram illustrates the flow of signaling messages at an O-MGCF. An arrow labeled 'IAM' points from the left towards a vertical line representing the O-MGCF. Above the vertical line is the label 'O-MGCF'. From the right side of the vertical line, an arrow labeled 'INVITE' points to the right. + +Diagram showing the receipt of an IAM message by the O-MGCF and the subsequent sending of an INVITE message. + +**Figure 11b: Receipt of an IAM** + +Upon reception of an IAM message, the O-MGCF shall send a SIP INVITE request, as further detailed in the clauses below. + +An O-MGCF shall support both the SIP preconditions and 100 rel extensions and indicate the support of the SIP preconditions and 100rel extensions in the INVITE request, unless the Note below applies. + +NOTE: If the O-MGCF is deployed in an IMS network that by local configuration serves no user requiring preconditions, it may send the INVITE request without indicating support of preconditions. + +#### 7.2.3.2.1.2 Interaction with continuity check + +If the Continuity Check indicator in the Nature of Connection Indicators parameter in the incoming IAM is set to indicate either "*continuity check required on this circuit*" or "*continuity check performed on previous circuit*", the O-MGCF should defer sending the INVITE request until receiving a COT message. + +NOTE: If the Continuity Check indicator in the Nature of Connection Indicators parameter in the incoming IAM is set to indicate either "*continuity check required on this circuit*" or "*continuity check performed on previous circuit*" and the O-MGCF sends the INVITE request before receiving a COT message, the following considerations apply: If the receiving terminal is not supporting the SIP precondition and the SIP UPDATE method, clipping may occur. Furthermore, if the MGCF sets the SDP "inactive" attribute in the initial INVITE request and the receiving terminal is not supporting the SIP precondition, the interworking procedures within the present specification do not describe all necessary signalling interactions required to set up a call, in particular with respect to the sending of the re-INVITE that may also cause additional delay in the call setup. In addition, the interworking of the ringing indication might not be possible if the peer sends the ringing indication only as response to a re-INVITE. + + + +The diagram shows a sequence of messages received by an O-MGCF. A solid horizontal arrow labeled 'IAM' points to a vertical line representing the O-MGCF. Below it, a dashed horizontal arrow labeled 'COT (NOTE)' also points to the same vertical line. After the COT message is received, a solid horizontal arrow labeled 'INVITE' points away from the O-MGCF to the right. + +Sequence diagram for Figure 12: Receipt of an IAM (Waiting for the COT message). + +NOTE: Waiting for the COT is recommended, if the Continuity Check indicator in the Nature of Connection Indicators parameter in the incoming IAM is set to indicate either "*continuity check required on this circuit*" or "*continuity check performed on previous circuit*" + +**Figure 12: Receipt of an IAM (Waiting for the COT message)** + +#### 7.2.3.2.1.3 IAM without calling party number + +If no calling party number is received in the incoming IAM message, as a network option, the O-MGCF may send an INR message to request the calling party number and not send the INVITE request until receiving an INF message with calling party number. If no calling party number is received in the INF message, O-MGCF may reject or continue the call based on local configuration. + + + +The diagram shows a sequence of messages received by an O-MGCF. A solid horizontal arrow labeled 'IAM' points to a vertical line representing the O-MGCF. From the O-MGCF, a solid horizontal arrow labeled 'INR' points back to the left. A solid horizontal arrow labeled 'INF' points to the O-MGCF from the left. After the INF message is received, a solid horizontal arrow labeled 'INVITE' points away from the O-MGCF to the right. + +Sequence diagram for Figure 12a: Receipt of an IAM (Request for calling party number). + +**Figure 12a: Receipt of an IAM (Request for calling party number)** + +#### 7.2.3.2.1.4 Terminating overlap signalling at MGCF + + + +``` + +sequenceDiagram + participant CS Network + participant O-MGCF + Note right of CS Network: IAM + CS Network->>O-MGCF: IAM + Note right of CS Network: SAM + CS Network->>O-MGCF: SAM + Note left of O-MGCF: INVITE + O-MGCF->>CS Network: INVITE + +``` + +Sequence diagram showing the receipt of IAM and SAM messages by the O-MGCF, followed by the sending of an INVITE message. + +**Figure 13: Receipt of an IAM (Overlap signalling in CS network)** + +After initiating the normal incoming BICC/ISUP call establishment procedures, determining the end of address signalling and selecting to route the call to the IMS domain, the O-MGCF shall send the initial INVITE. + +The end of address signalling shall be determined by the earlier of the following criteria: + +- by receipt of an end-of-pulsing (ST) signal; or +- by receipt of the maximum number of digits used in the national numbering plan; or +- by analysis of the called party number to indicate that a sufficient number of digits has been received to route the call to the called party; or +- by observing that timer Ti/w1 has expired after the receipt of the latest address message and the minimum number of digits required for routing the call have been received. + +If the end of the address signalling is determined in accordance with criteria a) b) or c), the timer Ti/w2 is started when INVITE is sent. Also, if the PSTN XML body is supported as a network option, the O-MGCF shall insert the PSTN XML sendingCompleteIndication. + +#### 7.2.3.2.1.5 Fallback (optional) + +The Fallback mechanism described in the present clause shall only apply if the O-MGCF supports the PSTN XML body as a network option, and propagates UDI-TA fallback signalling into the IMS as a network option. + +NOTE: If the Fallback related signalling is not forwarded according to the procedures in the present subclause by the O-MGCF, the O-MGCF will apply the ISUP Fallback procedures when the IAM includes a TMR and a TMR prime parameter and a USI and USI Prime parameter. + +When the IAM includes a TMR and a TMR prime parameter and a USI and USI Prime parameter then the O-MGCF shall: + +- map the "USI Prime" into the "InformationTransferCapability" of the second BearerCapability element in the PSTN XML body; +- include SDP with one m-line of "audio" media type in the INVITE; +- map the "TMR" and "USI Prime" into a first offerered format in the SDP m-line according to table 10b; +- map the "USI" into the first Bearer Capability element in the PSTN XML body; +- map the "TMR prime" into the "InformationTransferCapability" of the first BearerCapability element in the PSTN XML body; and +- map the TMR prime and USI into a second offerered format in the SDP m-line according to table 10b. + +### 7.2.3.2.1a Sending of INVITE without determining the end of address signalling + +#### 7.2.3.2.1a.1 General + +As a network option, the O-MGCF is not required to determine the end of address signalling. In this case the O-MGCF shall send an initial INVITE when a preconfigured number of digits has been reached. + +When the MGCF receives ISUP SAM messages the additional digits received in the SAMs may either be sent using the in-dialog overlap method as specified in clause 7.2.3.2.1a.2 or using the multiple INVITEs overlap method as specified in 7.2.3.2.1a.3. It depends on the network configuration which of these methods is applied. However, within one IMS only a single method shall be used. + +#### 7.2.3.2.1a.2 Additional digits sent with in-dialog overlap method + + + +``` + +sequenceDiagram + participant External + participant O-MGCF + Note right of O-MGCF: O-MGCF + External->>O-MGCF: IAM + O-MGCF->>External: INVITE + External-->>O-MGCF: 404/484 + External->>O-MGCF: SAM + O-MGCF->>External: INVITE + External-->>O-MGCF: 18x + External->>O-MGCF: SAM + O-MGCF->>External: INFO + External-->>O-MGCF: 200 (INFO) + +``` + +Sequence diagram illustrating overlap signalling using in-dialog INFO messages. The diagram shows the interaction between an external network and the O-MGCF. The sequence is: 1. IAM is received by the O-MGCF. 2. The O-MGCF sends an INVITE. 3. The O-MGCF receives a 404/484 response. 4. A SAM is received by the O-MGCF. 5. The O-MGCF sends another INVITE. 6. The O-MGCF receives an 18x provisional response. 7. Another SAM is received by the O-MGCF. 8. The O-MGCF sends an INFO message. 9. The O-MGCF receives a 200 (INFO) response. + +**Figure 14: Overlap signalling using in-dialog INFOs in CS an IMS network** + +If the O-MGCF sends an initial SIP INVITE request before the end of address signalling is determined, the O-MGCF shall: + +- use the SIP precondition extension within the SIP INVITE request; +- start timer Ti/w2; +- be prepared to process SAM as described below; +- be prepared to handle incoming SIP 18x provisional responses, establishing early dialogs; and +- be prepared to handle incoming SIP 404 or 484 error responses as detailed in clause 7.2.3.2.12.1. + +NOTE 1: A SIP INVITE request with incomplete address information can be rejected with a SIP 404 or 484 error response. + +On receipt of a SAM from the BICC/ISUP side, unless the O-MGCF has received a SIP 180 (Ringing) response for the call, the following O-MGCF procedures apply: + +- The O-MGCF shall stop timer Ti/w3 (if it is running). +- If no response has been received for the previous INVITE request of the same call, the O-MGCF shall wait for the response and then apply the procedures in the next bullets to transfer the digits received in the SAM. If additional SAMs are received while the O-MGCF is waiting for the response for the previous SIP INVITE request, the digits within shall be combined with the digits of the previous SAMs. + +- If an early dialog has not been established, and a SIP 404 or 484 error response has been received for the last previous SIP INVITE request for the same call, the O-MGCF shall send a SIP INVITE request complying to the following: + - The SIP INVITE request shall use the SIP preconditions extension. + - The SIP INVITE request shall include all digits received so far for this call in the Request-URI. + - The SIP INVITE request shall include the same Call-ID and From tag as the previous SIP INVITE request for the call. +- If an early dialog has been established, and a response has been received for any previously sent SIP INFO request ("legacy" mode of usage of the INFO method as defined in IETF RFC 6086 [133]), the O-MGCF shall send an in-dialog SIP INFO request complying the following: + - The SIP INFO request shall only include the digits received since the previous SIP request with digits was sent (see Note). +- If no response has been received for the previous SIP INFO request, the O-MGCF shall wait for the response and then apply the procedures in the previous bullet to transfer digits received in the SAM. If additional SAMs are received while the O-MGCF is waiting for the response for the previous SIP INFO request, the digits within shall be combined with the digits of the previous SAMs. +- Restart Ti/w2. + +If timer Ti/w2 has expired, or the O-MGCF has received a SIP 180 (Ringing) response for the call, the O-MGCF shall ignore subsequent SAMs received. + +NOTE 2: The encoding of the digits within the SIP INFO request is described in clause 7.2.3.2.20.2. + +#### 7.2.3.2.1a.3 Additional digits sent using the multiple INVITEs overlap method + + + +O-MGCF + +``` + +sequenceDiagram + participant CS + participant O-MGCF + participant IMS + Note over O-MGCF: O-MGCF + CS->>O-MGCF: IAM + O-MGCF->>IMS: INVITE + IMS-->>O-MGCF: 404/484 + CS->>O-MGCF: SAM + O-MGCF->>IMS: INVITE + IMS-->>O-MGCF: 404/484 + CS->>O-MGCF: SAM + O-MGCF->>IMS: INVITE + +``` + +Sequence diagram showing overlap signalling using multiple INVITEs in CS and IMS network. The O-MGCF receives IAM and SAM messages from the left and sends INVITE messages to the right. It receives 404/484 responses from the right and sends subsequent INVITE messages as more SAMs are received. + +**Figure 14a: Overlap signalling using multiple INVITEs in CS and IMS network** + +If the O-MGCF sends an SIP INVITE request before the end of address signalling is determined, the O-MGCF shall: + +- use the SIP precondition extension within the SIP INVITE request; +- start timer Ti/w2; and +- be prepared to process SAM as described below; and +- be prepared to handle incoming SIP 404 or 484 error responses as detailed in clause 7.2.3.2.12.1. + +NOTE: An SIP INVITE request with incomplete address information will be rejected with a SIP 404 or 484 error response. + +On receipt of a SAM from the BICC/ISUP side, unless the O-MGCF has received a SIP 180 (Ringing) response for the call, the O-MGCF shall: + +- stop timer Ti/w3 (if it is running); +- send an INVITE request complying to the following: + - The SIP INVITE request shall use the SIP preconditions extension. + - The SIP INVITE request shall include all digits received so far for this call in the Request-URI. + - The SIP INVITE request shall include the same Call-ID and From tag as the previous SIP INVITE request for the call. +- restart Ti/w2; + +If timer Ti/w2 has expired, or the O-MGCF has received a SIP 180 (Ringing) response for the call, the O-MGCF shall ignore subsequent SAMs received. + +### 7.2.3.2.2 Coding of the INVITE + +#### 7.2.3.2.2.0 Overview + +Table 10aa provides a summary of how the header fields within the outgoing INVITE message are populated. + +**Table 10aa: Interworked contents of the INVITE message** + +| IAM→ | INVITE→ | +|-------------------------------------------------------------|------------------------------------------------------------------------------| +| Called Party Number | Request-URI
To
History-Info | +| Calling Party Number | P-Asserted-Identity
Privacy
From
Attestation-Info
Origination-Id | +| Generic Number ( "additional calling party number" ) | From
Privacy
Attestation-Info
Origination-Id | +| Called IN number | History-Info | +| Original called IN number | History-Info | +| Hop Counter | Max-Forwards | +| TMR/USI | Message Body (application/SDP) | +| Location Number | P-Access-Network-Info | + +#### 7.2.3.2.2.1 Request-URI and To header field + +The called party number parameter of the IAM message is used to derive Request-URI of the INVITE request. The Request-URI is a tel URI or SIP URI with "user=phone" and shall contain: + +- an E.164 International public telecommunication number prefixed by a "+" sign (e.g. tel:+4911231234567) , or +- a non E.164 number (national operator option for service numbers), expressed as a local number as per IETF RFC 3966 [97]. + +**Table 10a: Mapping ISUP Called Party Number to SIP Request-URI and To header field** + +| IAM | | INVITE | | +|-----------------------------------------------|----------------------------------------------------------------------------|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| BICC/ISUP Parameter / field | Value | SIP component | Value | +| Called Party Number (NOTE 3) | | Request-URI and To header field | display-name (optional) and addr-spec derived from Called Party Number parameter address signals | +| Nature of Address Indicator (NOTE 2) (NOTE 6) | " national (significant) number " | Tel URI or SIP URI | Insert "+CC" before the Address signals (NOTE 1) | +| | " international number " | | Insert "+" before the Address signals | +| | " Network-specific number " or " reserved for national use " | | according to local policies should either be:
- a global number (+CC), if the called party number may be converted into an E.164 address
OR, depending on operator's requirements may be converted into
- local number (with a phone-context parameter) (NOTE 4) (NOTE 5) | + +NOTE 1: CC = Country Code of the network in which the O-MGCF is located. +NOTE 2: The usage of "Nature of address indicator" value "unknown" is allowed but the mapping is not specified in the present specification. +NOTE 3: If the address signals received in the ISUP Called Party Number contain a sending terminated signal (hexadecimal digit F), then this shall be discarded or if the O-MGCF supports the PSTN XML body as a network option then the PSTN XML sendingCompleteIndication shall be set. +NOTE 4: Mapping between nature of address indicator values and phone-context values is provisioned in the MGCF. Setting of value of phone-context is depending on local operator's policies. +NOTE 5: Network-specific number or reserved for national use shall be translated into E.164 format numbers except if local operator's policy requires keeping in local format (e.g. for national reasons E.164 numbers cannot be used for such purpose). In the later case the mapping shall be done as indicated in the table. +NOTE 6: The values "Network routing number in national (significant) number format", "Network routing number in network specific number format" or "Network routing number concatenated with called directory number" are used when number portability is supported. For the mapping see clause 7.2.3.2.2A. + +#### 7.2.3.2.2.2 SDP Media Description + +If the O-MGCF indicates support of the SIP preconditions in the initial INVITE request and local preconditions have not been met, the SDP media description shall contain precondition information as per 3GPP TS 24.229 [9]. Depending on the coding of the continuity indicators different precondition information (IETF RFC 3312 [37]) is included. If the continuity indicator indicates "continuity performed on a previous circuit" or "continuity required on this circuit", and the INVITE is sent before receiving a COT, message (which is not recommended according to clause 7.2.3.2.1.1), then the O-MGCF shall indicate that the preconditions are not met. Otherwise the O-MGCF shall indicate whether the preconditions are met, dependent on the status of the local resource reservation. + +If the O-MGCF determines that a speech call is incoming, the O-MGCF shall include the AMR codec transported according to IETF RFC 4867 [23] with the options listed in clause 12.3.1 of 3GPP TS 26.114 [104] in the SDP offer, unless the Note below applies. Within the SDP offer, the O-MGCF should also provide SDP RR and RS bandwidth modifiers specified in IETF RFC 3556 [59] as detailed in clause 7.3.1 of 3GPP TS 26.114 [104]. The O-MGCF may include other codecs according to operator policy. + +NOTE: If the O-MGCF is deployed in an IMS network that by local configuration serves no user equipment that implements the AMR codec, then the AMR codec may be excluded from the SDP offer. + +To avoid transcoding or to support non-speech services, the O-MGCF may add media derived from the incoming ISUP information according to table 10b. The support of the media listed in table 10b is optional. If the O-MGCF supports the PSTN XML body as a network option and adds media derived from the incoming ISUP information according to table 10b, the O-MGCF shall also map the media related ISUP information into the XML body as shown in table 7.2.3.2.2.7.1. + +**Table 10b: Coding of SDP media description lines from TMR/USI: ISUP to SIP** + +| TMR parameter | USI parameter (Optional) | | HLC IE in ATP (Optional) | m= line | | | b= line | a= line | +|--------------------------|------------------------------------|---------------------------------------------|-------------------------------------------|----------------|--------------|--------------------------------------------------------|----------------------------------|------------------------------------------------------------------------------------------------------------| +| | | | |
"id" and "header" are not included
(See table 16). | +| Y | "presentation restricted" | N | - | Derived from Calling Party Number parameter address signals (See table 14) | SIP URI with addr-spec of Unavailable User Identity (NOTE 2) (NOTE 6) (NOTE 12) | priv-value =: "id". (See table 16) | +| Y | "presentation restricted" | Y | "presentation allowed" | Derived from Calling Party Number parameter address signals (See table 14) | Derived from Generic Number (AcgPN) address signals (See table 13) (NOTE 6) | priv-value =: "id". | +| Y | "presentation restricted" | Y | "presentation restricted" | Derived from Calling Party Number parameter address signals (See table 14) | SIP URI with addr-spec of Anonymous URI (NOTE 6) (NOTE 7) (NOTE 10) | priv-value =: "id" | +| | | | | | Derived from the Generic Number parameter address signals (see table 13) (NOTE 6) (NOTE 8) | priv-value =: "id", "user".
(See table 16). | +| Y | "presentation restricted by network" (NOTE 4) | N | - | Header field not included. | Addr-spec is set to "unavailable@hostportion" (NOTE 5) (NOTE 6) (NOTE 12) | Privacy header is not included or if included, "id" and "header" are not included (See table 16) | +| Y | "presentation restricted by network" | Y | "presentation allowed" | Header field not included. | Derived from Generic Number (AcgPN) address signals (See table 13) (NOTE 6) | Privacy header is not included or if included, "id", "header" and "user" are not included (See table 16). | +| Y | "presentation restricted by network" | Y | "presentation restricted" | Header field not included. | Addr-spec is set to Anonymous URI (NOTE 6) (NOTE 7) | Privacy header is not included or if included, "id" and "header" are not included (See table 16). | + +| Has a Calling Party Number parameter with complete E.164 number, and with Screening Indicator = UPVP or NP (NOTE 1) been received? | Calling Party Number APRI | Has a Generic Number (AcgPN) with a complete E.164 number and with Screening Indicator = UPNV been received? | Generic Number APRI | P-Asserted-Identity header field | From header field | Privacy header field | +|------------------------------------------------------------------------------------------------------------------------------------|---------------------------|--------------------------------------------------------------------------------------------------------------|---------------------|----------------------------------|--------------------------------------------------------------------------------------------|--------------------------------------------------------------------------| +| | | | | | Derived from the Generic Number parameter address signals (see table 13) (NOTE 6) (NOTE 8) | priv-value =: "user". "id" and "header" are not included (See table 16). | + +NOTE 1: A Network Provided CLI in the CgPN parameter may occur on a call to IMS. Therefore in order to allow the "display" of this Network Provided CLI at a SIP UAS it shall be mapped into the SIP From header. It is also considered suitable to map into the P-Asserted-Identity header since in this context it is a fully authenticated CLI related exclusively to the calling line, and therefore as valid as a User Provided Verified and Passed CLI for this purpose. + +NOTE 2: The "From" header may contain an "Unavailable User Identity". An "Unavailable User Identity" includes information that does not point to the calling party and indicates that the caller's identity is unknown. The encoding of the "Unavailable User Identity" shall be as defined in 3GPP TS 23.003 [74]. + +NOTE 3: This combination of CgPN and AcgPN is an error case but is shown here to ensure consistent mapping across different implementations. + +NOTE 4: This is an ETSI specific value described within ETSI EN 300 356-1 [70]. + +NOTE 5: The setting of the hostportion is according to operator policy. + +NOTE 6: In accordance with IETF RFC 3261 [19] procedures, a tag shall be added to the "From" header. + +NOTE 7: The "From" header may contain an "Anonymous User Identity". An "Anonymous User Identity" includes information that does not point to the calling party and indicates that the caller has withheld their identity. The encoding of the "Anonymous User Identity" shall be as defined in 3GPP TS 23.003 [74]. + +NOTE 8: As a network option, the "From" header may be derived from the Generic Number parameter address signals (see table 13). This option is only recommended to use within a trusted domain where an entity such as a TAS is configured to be inserted into the call path that is able to change the "From" Header content to an anonymous user identity (NOTE 7). + +NOTE 9: As a network option, the "From" header may be derived from the Calling Party Number parameter address signals (see table 15). This option is only recommended to use within a trusted domain where an entity such as a TAS is configured to be inserted into the call path that is able to change the "From" Header content to an anonymous user identity (NOTE 7). + +NOTE 10: Network option. + +NOTE 11: As a network option, the P-Asserted-Identity header field may be included. The URI of the P-Asserted-Identity header field is "Unavailable User Identity" defined in 3GPP TS 23.003 [74]. When populating the P-Asserted-Identity header field containing the "Unavailable User Identity" into a SIP request, the MGCF may populate the Privacy header field set to "id" into the SIP request in order to avoid this identity to be displayed to user. + +NOTE 12: As a network option, for calls where a Generic Number (ACgPN) with the "Nature of Address Indicator" values "subscriber number" or "unknown" is received, the nature of address indicator and address signals may instead be mapped into the SIP From header field as specified in Table 13. + +**Table 13: Mapping of generic number (additional calling party number) to SIP From header field** + +| BICC/ISUP parameter / field | Value | SIP component | Value | +|-------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------| +| Generic Number
Number Qualifier
Indicator | " additional calling party number " | From header field | display-name (optional) and addr-spec | +| Nature of Address
Indicator | " national (significant) number " | Tel URI or SIP URI | Add CC (of the country where the MGCF is located) to GN address signals to construct E.164 number in URI. Prefix number with "+". | +| | " international number " | | Map complete GN address signals to E.164 number in URI. Prefix number with "+". | +| | " subscriber number " or " unknown " (NOTE 1) | | Map complete GN address signals. Add phone-context URI parameter (NOTE 2) | +| Address signal | if NOA is " national (significant) number " then the format of the address signals is:
NDC+ SN
If NOA is " international number " then the format of the address signals is:
CC + NDC + SN | Tel URI or SIP URI | | +| | If NOA is " subscriber number " (NOTE 1), then the format of the address signals is:
SN | | CC+NDC+SN as E.164 number in URI. Prefix number with "+". | +| | If NOA is " unknown " (NOTE 1), then the format of the address signals is determined by the operator. | | Map subscriber number as local number with a phone-context URI parameter (NOTE 2) | +| | | | Map address signals with a phone-context URI parameter (NOTE 2) | +| | | | | +| | If NOA is " subscriber number " (NOTE 1), then the format of the address signals is:
SN | | Map subscriber number as local number with a phone-context URI parameter (NOTE 2) | +| | If NOA is " unknown " (NOTE 1), then the format of the address signals is determined by the operator. | | Map address signals with a phone-context URI parameter (NOTE 2) | + +NOTE 1: The usage and the interworking of the "Nature of Address Indicator" values "subscriber number" and "unknown" is a national operator option. +NOTE 2: Mapping between "Nature of Address Indicator" values and phone-context values is provisioned in the MGCF. Setting the values of phone-context is dependent on local operator's policies. + +**Table 14: Mapping of calling party number parameter to SIP P-Asserted-Identity header fields** + +| BICC/ISUP Parameter / field | Value | SIP component | Value | +|------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| +| Calling Party Number | | P-Asserted-Identity header field | addr-spec and optionally display-name (NOTE 1) | +| Nature of Address Indicator | " national (significant) number " | Tel URI or SIP URI (NOTE 2) | Add CC (of the country where the MGCF is located) to CgPN address signals to construct E.164 number in URI. Prefix number with "+". | +| | " international number " | | Map complete CgPN address signals to E.164 number in URI. Prefix number with "+". | +| Address signal | If NOA is " national (significant) number " then the format of the address signals is:
NDC + SN
If NOA is " international number " then the format of the address signals is:
CC + NDC + SN | Tel URI or SIP URI (NOTE 2) | CC+NDC+SN as E.164 number in URI. Prefix number with "+" | + +NOTE 1: The display-name may be mapped from the corresponding telephone number if possible and allowed by network operator policies. + +NOTE 2: A tel URI or a SIP URI with "user=phone" is used according to operator policy. + +**Table 15: Mapping of BICC/ISUP Calling Party Number parameter to SIP From header field** + +| BICC/ISUP parameter / field | Value | SIP component | Value | +|------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| Calling Party Number | | From header field | | +| Nature of Address Indicator | " national (significant) number " | Tel URI or SIP URI (NOTE) | Add CC (of the country where the MGCF is located) to CgPN address signals then map to construct E.164 number in URI. Prefix number with "+". | +| | " international number " | | Map complete CgPN address signals to construct E.164 number in URI. Prefix number with "+". | +| Address signal | If NOA is " national (significant) number " then the format of the address signals is:
NDC + SN
If NOA is " international number " then the format of the address signals is:
CC + NDC + SN | Tel URI or SIP URI (NOTE) | CC+NDC+SN as E.164 number in URI. Prefix number with "+". | + +NOTE: A tel URI or a SIP URI with "user=phone" is used according to operator policy. + +**Table 16: Mapping of BICC/ISUP APRIs into SIP Privacy header fields** + +| BICC/ISUP parameter / field | Value | SIP component | Value | +|-------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|----------------------|----------------------------------------------------------------------------------------------------| +| Calling Party Number | | Privacy header field | priv-value | +| APRI | " presentation restricted " | Priv-value | "id"
("id" included only if the P-Asserted-Identity header is included in the SIP INVITE) | +| | " presentation allowed " or " presentation restricted by network " | Priv-value | omit Privacy header or Privacy header without "id" and "header" if other privacy service is needed | +| Generic Number (ACgPN) | | Privacy header field | priv-value | +| APRI (NOTE) | " presentation restricted " | Priv-value | "user" | +| | " presentation allowed " | Priv-value | omit Privacy header or Privacy header without "user" if other privacy service is needed | +| NOTE: Mapping of Generic Number APRI is only applicable, if the Generic Number is mapped to the "From" header field (see table 12). | | | | + +If, as a network option, the MGCF supports "Calling number verification using signature verification and attestation information" feature as described in IETF RFC 8224 [153] and 3GPP TS 24.229 [9], the MGCF shall: + +- include in the initial INVITE request: + - a) attestation level in the Attestation-Info header field defined in 3GPP TS 24.229 [9]; and + - b) the origination identifier in the Origination-Id header field defined in 3GPP TS 24.229 [9]; and +- if the MGCF performed mapping of Calling party number parameter to the P-Asserted-Identity header field as defined in table 14 and the MGCF received the Calling party number with the Screening indicator set to value "*user provided, verified and passed*": + - a) set the value of the Attestation-Info header field to "B" (Partial Attestation) as described in 3GPP TS 24.229 [9]; and + - b) use own address or identifier for creation of the Origination-Id header field as described in 3GPP TS 24.229 [9]; or +- otherwise, for all other mapping cases defined in table 12: + - a) set the value of the Attestation-Info header field to "C" (Gateway Attestation) as described in 3GPP TS 24.229 [9]; and + - b) use the received Circuit identification field (i.e. Circuit identification code) for creation of the Origination-Id header field as described in 3GPP TS 24.229 [9]. + +#### 7.2.3.2.2.3A "cpc" URI Parameter in P-Asserted-Identity Header + +See Annex C for normative interworking of a Calling party's category to a "cpc" URI parameter within P-Asserted-Identity header field. + +#### 7.2.3.2.2.3B "oli" URI Parameter in P-Asserted-Identity Header + +See Annex H for normative interworking of the "oli" URI parameter as a network option. + +#### 7.2.3.2.2.4 Max Forwards header + +If the Hop Counter procedure is supported in the CS network, the O-MGCF shall use the Hop Counter parameter to derive the Max-Forwards SIP header. Due to the different default values (that are based on network + +demands/provisions) of the SIP Max-Forwards header and the Hop Counter, an adaptation mechanism shall be used to adopt the Hop Counter to the Max Forwards at the O-MGCF. For example, the following guidelines could be applied. + +- a) Max-Forwards for a given message should be monotone decreasing with each successive visit to a SIP entity, regardless of intervening interworking, and similarly for Hop Counter. +- b) The initial and successively mapped values of Max-Forwards should be large enough to accommodate the maximum number of hops that may be expected of a validly routed call. + +The table 17 shows the principle of the mapping: + +**Table 17: Hop counter-Max forwards** + +| | | | | +|----------------------------------------------------------------------------------------------------|-----|--------------|------------------------------------| +| Hop Counter | = X | Max-Forwards | = Y = Integer part of (X * Factor) | +| NOTE: The Mapping of value X to Y should be done with the used (implemented) adaptation mechanism. | | | | + +The factor used to map from Hop Counter to Max-Forwards for a given call will depend on call origin, and will be provisioned at the O-MGCF based on network topology, trust domain rules, and bilateral agreement. + +The Principle of adaptation could be implemented on a basis of the network provision, trust domain rules and bilateral agreement. + +#### 7.2.3.2.2.5 IMS Communication Service Identifier + +For speech and video calls, the O-MGCF shall insert an IMS Communication Service Identifier, indicating the IMS Multimedia Telephony Communication Service. + +The IMS Communication Service Identifier for the IMS Multimedia Telephony Communication Service is defined in 3GPP TS 24.173 [88]. + +#### 7.2.3.2.2.6 P-Early-Media header field + +For a speech call the O-MGCF may include the P-Early-Media header field with the "supported" parameter as described in IETF RFC 5009 [89] in each outgoing INVITE request. + +NOTE: The P-Early-Media header with the "supported" parameter can be ignored by terminating devices when not supporting the procedures described in IETF RFC 5009 [89]. + +#### 7.2.3.2.2.7 PSTN XML elements + +If the O-MGCF supports the PSTN XML body as a network option, the O-MGCF shall map ISUP information into the XML body as shown in table 7.2.3.2.2.7.1 and 7.2.3.2.2.8.1. + +**Table 7.2.3.2.2.7.1: Mapping of ISUP Parameters with PSTN XML elements** + +| IAM | | INVITE | +|------------------------------|-------------------------------------------------|-------------------------------------------------| +| ISUP Parameter | Content | PSTN XML | +| Access Transport Parameter | High layer compatibility | HighLayerCompatibility (NOTE 1, NOTE 2, NOTE 3) | +| | Low layer compatibility | LowLayerCompatibility (NOTE 3) | +| User Service Information | | Bearer Capability (NOTE 3, NOTE 4) | +| User Teleservice Information | High layer compatibility | HighLayerCompatibility (NOTE 2, NOTE 3) | +| Called Party Number | Sending terminated signal (hexadecimal digit F) | sendingCompleteIndication | + +NOTE 1: If two high layer compatibility information elements are received in the ATP of the IAM, they shall be transferred in the same order as received into the PSTN XML body within the INVITE. + +NOTE 2: In the normal case, the High layer compatibility information in the ATP is equal to the High layer compatibility in the User Teleservice Information parameter. In the PSTN XML body, no two identical High layer compatibility information shall be present. If an HLC is available both in the ATP and in the User Teleservice information, the HLC from the ATP should be mapped. + +NOTE 3: The O-MGCF shall only map this information element if the O-MGCF offers media formats which can be transferred by the IM-MGW without transcoding and are derived from the incoming ISUP information according to table 10b. + +NOTE 4: See clause 7.2.3.2.1.5. + +#### 7.2.3.2.2.8 Progress indicator + +If the O-MGCF supports the PSTN XML body as a network option, the Forward call indicators parameter and an available "Progress indicator" element in the IAM shall be mapped into a ProgressIndicator in the PSTN XML body of the INVITE as shown in table 7.2.3.2.2.8. + +**Table 7.2.3.2.2.8: Coding of PSTN XML ProgressIndicator** + +| IAM→ | | | INVITE → | +|----------------------------------------------|----------------------------------------|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Forward call indicators parameter | | Access transport parameter | PSTN XML body with ProgressIndicator with "Progress Description" value No. (Value of PI) | +| ISDN User Part indicator | ISDN access indicator | | | +| 0
("ISDN User Part not used all the way") | Value non-significant | Value non-significant | No. 1 (NOTE 1) | +| 1
("ISDN User Part used all the way") | 0
("originating access non - ISDN") | Value non-significant | No. 3 (NOTE 1) | +| 1
("ISDN User Part used all the way") | 1
("originating access ISDN") | Progress indicator No. (Value of PI) | ProgressIndicator mapped from Progress indicator received in the ATP (NOTE 2) and additional ProgressIndicator with "Progress Description" value No.6 (NOTE 1, NOTE 3) | +| 1
("ISDN User Part used all the way") | 1
("originating access ISDN") | Not present | No. 6 (NOTE 1) | + +NOTE 1: The ProgressIndicator "Coding Standard" parameter shall be set to "00 (ITU-T standardized coding)". The default value for the ProgressIndicator "Location" parameter is "0011 (Transit Network)". + +NOTE 2: The entire Progress indicator, including the "Progress Description", "Coding Standard" and "Location" parameters shall be copied. + +NOTE 3: The order of ProgressIndicators within PSTN XML body is irrelevant. + +#### 7.2.3.2.2.9 P-Access-Network-Info + +If the IAM message includes a location number ISDN user part parameter, the O-MGCF shall include a P-Access-Network-Info header. The P-Access-Network-Info shall be populated as shown in table 7.2.3.2.2.9.1. + +**Table 7.2.3.2.2.9.1: Coding of the P-Access-Network-Info header fields** + +| BICC/ISUP parameter / field | SIP component | Value | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|-------------------------------------| +| Location Number | access-type | "GSTN" | +| | gstn-location (NOTE) | value of Location Number, in quotes | +| NOTE: Alternatively, as a network option, the value of the Location Number can populate the operator-specific-GI parameter. In this case, the operator-specific-GI is set to the text string between quotes with the sequence of digits found in octet 3 to N (except the filler) starting with the 1 st digit. The access-info parameter is set to "operator-specific-GI" | | | + +**Table 7.2.3.2.2.9.2: Mapping ISUP Location Number to SIP P-Access-Network-Info** + +| IAM | INVITE | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------| +| Location Number | P-Access-Network-Info | +| Parameter name | not mapped | +| Parameter length | not mapped | +| Parameter content | gstn-location set to the hexadecimal representation of the ISUP parameter content, encoded as a text string between quotes | +| NOTE 1: As specified in ITU-T Q.763 [4], the parameter content includes both the header fields (octets 1 and 2) and the address signals. | | +| NOTE 2: The parameter content includes the address presentation restricted indicator. This field is not mapped to the Privacy header field. It is upon network operator responsibility to remove the P-Access-Network-Info header field when leaving the trust domain, as specified in 3GPP TS 24.229 [9]. | | +| NOTE 3: If the screening indicator is set to network provided, a "network-provided" parameter is added to the P-Access-Network-Info header field value. | | + +#### 7.2.3.2.2A Coding of the INVITE when Number Portability is supported + +This clause describes optional coding procedures when Number Portability is supported. + +##### 7.2.3.2.2A.1 Request-URI and To header field + +When Number Portability is supported, the method used for signalling of the Called Party E.164 address and the Number Portability Routing Number determines the parameters of the IAM message used to derive the Request-URI of the INVITE request. + +The number portability information (rn and npdi) shall not be mapped into the To header field. + +ITU-T Q.769.1 [92] describes three possible addressing methods for signalling of the Called Party E.164 address and Number Portability Routing Number (ITU-T Q.769.1 [92] uses the terms directory number and network routing number respectively). The choice of these methods is based on network operator and national requirements. + +The following clauses describe how the Request-URI and To header field are populated, based on these methods, when a Number Portability Routing Number is available in the IAM. + +When the optional Number Portability Routing Number is available and supported, these procedures take precedence over procedures for coding of the Request-URI and To header field described in clause 7.2.3.2.2.1. + +When a Number Portability Routing Number is not available, the Request-URI and To header field are populated as described in clause 7.2.3.2.2.1, with the following addition: If a Number Portability Forward Information parameter is present in the IAM, containing a value of "number portability query done for called number, non-ported called subscriber", a tel URI npdi parameter [93] is added. + +For the following clauses, the Request-URI is a tel URI or SIP URI with "user=phone" and shall contain an E.164 International public telecommunication number prefixed by a "+" sign (e.g.
Nature of address indicator:
"Network routing number in national (significant) number format" or "National (significant) number" or "Network routing number in network specific number format" as described in ITU-T Q.769.1 [92]
(NOTE 2) | Address Signal:
Nature of address indicator:
"National (significant) number". | The "telephone-subscriber" is populated from the Called Directory Number as follows:
Insert "+CC" before the Address signals (NOTE 1)
The Tel URI rn= parameter is populated from the Called Party Number as follows:
Insert "+CC" before the Address signals (NOTE 1) and is added only to the Request-URI.
Use of the local form of the rn= parameter is out of the scope of the present specification.
Tel URI npdi parameter as defined in IETF RFC 4694 [93] is added only to the Request-URI. | + +NOTE 1: CC = Country Code of the network in which the O-MGCF is located. +NOTE 2: If the address signals received in the ISUP Called Party Number contain a sending terminated signal (hexadecimal digit F), then this shall be discarded or if the PSTN XML is supported then the sendingCompleteIndication shall be included. + +## 7.2.3.2.2A.1.2 Concatenated Addressing Method + +**Table 17b: Mapping ISUP to SIP Request-URI and To header field with Number Portability Concatenated Number Addressing Method** + +| IAM→ | | INVITE | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Called Party Number | | Request-URI and To Header Field | +| Address Signal:
Nature of address indicator:
"Network routing number concatenated with called directory number" or "National (significant) number" as described in ITU-T Q.769.1 [92]
(NOTE 2) | | The "telephone-subscriber" is populated from the Called Party Number as follows:
Remove the prefix representing the Number Portability Routing Number
or the prefix prior to the directory number (NOTE3).
Insert "+CC" before the Address signals (NOTE 1).
The Tel URI rn= parameter is populated from the Called Party Number as follows and is added only to the Request-URI:
Use all address digits contained within the Called Party Number or remove the digits that follow the prefix representing the Number Portability Routing Number
Insert "+CC" before the Address signals (NOTE 1)
Use of the local form of the rn= parameter is out of the scope of the present specification.
Tel URI npdi parameter as defined in IETF RFC 4694 [93] is added only to the Request-URI. | + +NOTE 1: CC = Country Code of the network in which the O-MGCF is located. +NOTE 2: If the address signals received in the ISUP Called Party Number contain a sending terminated signal (hexadecimal digit F), then this shall be discarded or if the PSTN XML is supported then the sendingCompleteIndication shall be included. +NOTE 3: Based on national policy the whole Number Portability Routing number includes the Called Party Number and a prefix. In such cases only the Prefix has to be removed. Normally the Nature of address indicator indicates if the Number Portability Routing Number contains a Called Party Number and a prefix. + +### 7.2.3.2.2A.1.3 Separate Network Routing Number Addressing Method + +**Table 17c: Mapping ISUP to SIP Request-URI and To header field with Number Portability Separate Network Routing Number Addressing Method** + +| IAM→ | | INVITE | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Network Routing Number | Called Party Number | Request-URI and To Header Field | +| Address Signal:
Nature of address indicator:
"Network routing number in national (significant) number format" or
"Network routing number in network specific number format" as described in ITU-T Q.769.1 [92]
(NOTE 2) | Address Signal:
Nature of address indicator:
"National (significant) number". | The "telephone-subscriber" is populated from the Called Party Number as follows:
Insert "+CC" before the Address signals (NOTE 1)
The Tel URI rn= parameter is populated from the Network Routing Number as follows and is added only to the Request-URI:
Insert "+CC" before the Address signals (NOTE 1)
Use of the local form of the rn= parameter is out of the scope of the present specification.
Tel URI npdi parameter as defined in IETF RFC 4694 [93] is added only to the Request-URI. | + +NOTE 1: CC = Country Code of the network in which the O-MGCF is located. +NOTE 2: If the address signals received in the ISUP Called Party Number contain a sending terminated signal (hexadecimal digit F), then this shall be discarded or if the PSTN XML is supported then the sendingCompleteIndication shall be included. + +### 7.2.3.2.2B Coding of the INVITE for Carrier Routeing + +This clause describes optional coding procedures for carrier-based routeing. + +#### 7.2.3.2.2B.1 Mapping of "cic" in Request-URI + +The procedures followed in clause 7.2.3.2.2.1 apply with the following addition. + +If the Transit Network Selection parameter, defined according to ITU-T Q.761 [4], is included in the IAM message the O-MGCF, based on network configuration, may send the transit network selection information to the SIP network. In such a case the "cic=" parameter as defined in IETF RFC 4694 [93] is included in the Request-URI and configured according to the table below. + +**Table 17d: Mapping of ISUP "Transit Network Selection" (TNS) to SIP "Carrier Identification Code" (CIC)** + +| ISUP parameter/field | Value | SIP Component | Value | +|---------------------------|--------|--------------------------------------------|--------------------------------------------------------| +| Transit Network Selection | Digits | Carrier id code in Userinfo of Request-URI | "cic=carrier ID code" as defined in IETF RFC 4694 [93] | + +#### 7.2.3.2.2B.2 Void + +### 7.2.3.2.2C Coding of INVITE with instance-id in form of IMEI URN + +An Emergency Access Transfer Function (EATF) that provides IMS-based mechanisms for enabling service continuity of IMS emergency sessions is described in 3GPP TS 23.237 [118]. A correlation of the call legs at the EATF is based on the equipment identifier. + +A Mobile Equipment Identifier (MEI) parameter of the Mobile Service Transport (MST) Application Transport Parameter is defined in 3GPP TS 29.205 [14]. + +An instance-id is a SIP Contact header field parameter defined in IETF RFC 5626 [119]. When an IMEI is available, the instance-id shall take the form of an International Mobile station Equipment Identity (IMEI) URN as specified in IETF RFC 7254 [120]. + +When an O-MGCF receives the Mobile Service Transport (MST) Application Transport Parameter containing the Mobile Equipment Identifier (MEI) parameter within the IAM the O-MGCF shall perform the mapping to the "+sip.instance" Contact header field parameter according to table 7.2.3.2.2C.1. + +**Table 7.2.3.2.2C.1: Mapping of ISUP/BICC to SIP** + +| IAM | | INVITE | | +|-------------------------------------|-------------------------------------|-----------------------------------------------------------------------------|------------------------------------------------------| +| ISUP Parameter | Value | SIP Component | Value | +| MST Application Transport Parameter | Mobile Equipment Identifier: IMEI | Contact header containing "+sip.instance" parameter in the form of IMEI URN | gmsa urn set to "imei" namespace
NOTE 1
NOTE 2 | +| | Mobile Equipment Identifier: IMEISV | | | + +NOTE 1: The gsma-specifier "imei" is generated as: +urn:gsma:imei:tac-snr-spare +where +"tac" represents 8 digits type allocation code (TAC), "snr" represents 4 digits serial number (SNR), and "spare" represents spare decimal digit as specified in TS 23.003 [74]. + +NOTE 2: The Software Version Number is not interworked and thus the "svn" parameter is not included within the gsma urn. + +#### 7.2.3.2.2.10 PSAP Call-back indication + +If the O-MGCF based on the operator policy has determined that the received IAM message is a for the purpose of a PSAP call-back, then the O-MGCF shall include in the initial INVITE request a Priority header field with a "psap-callback" header field value as specified in IETF RFC 7090 [139]. The operator policy decision may be based the PSAP call-back indication in the received IAM message and/or any other information made available at O-MGCF. + +NOTE: The PSAP call-back indication in the received IAM message depends on the national regulatory requirements applicable for the emergency services (e.g. calling party's category parameter indicating priority/emergency call, pre-defined prefix in front of the called party number) and is outside the scope of this specification. + +#### 7.2.3.2.2.11 History-Info header field (optional) + +See Annex L for the normative interworking of the History-Info header field into the called IN number and original called IN number parameters. + +### 7.2.3.2.3 Receipt of CONTINUITY + +This clause only applies if the O-MGCF has sent the INVITE request without waiting for an outstanding COT message (see clause 7.2.3.2.1). + + + +``` + +sequenceDiagram + participant External + participant O-MGCF + Note right of O-MGCF: O-MGCF + External->>O-MGCF: COT(success) + Note right of O-MGCF: SDP indicating pre-conditions met + O-MGCF-->>External: + +``` + +Sequence diagram showing the receipt of COT (success) by the O-MGCF. A horizontal arrow labeled 'COT(success)' points to a vertical line representing the O-MGCF. From the O-MGCF line, another horizontal arrow points to the right, labeled 'SDP indicating pre-conditions met'. + +**Figure 14a: Receipt of COT (success)** + +When the requested local preconditions (if any) have been met and if possible outstanding continuity procedures have successfully been completed (COT with the Continuity Indicators parameter set to "continuity check successful" is received), a SDP offer (e.g. a SIP UPDATE request, as defined in IETF RFC 3311 [55]) shall be sent for each early SIP + +dialogue for which the received provisional response indicated support of preconditions confirming that all the required local preconditions have been met. + +NOTE: This procedure applies regardless of whether the early SIP dialog existed prior to the preconditions being fulfilled or is subsequently created. + +#### 7.2.3.2.4 Sending of ACM and awaiting answer indication + +If the Address Complete Message (ACM) has not yet been sent, the following cases are possible trigger conditions that shall lead to the sending the address complete message (ACM): + +- the detection of end of address signalling by the expiry of Timer T i/w1 or, + + + +Sequence diagram for Figure 15: Sending of ACM T i/w1 elapses. The diagram shows an O-MGCF entity. It receives IAM, then SAM, then another SAM. Brackets on the right indicate that Timer T i/w1 is running after each SAM. When the timer expires after the second SAM, an ACM (no indication) is sent to the left, and an INVITE is sent to the right. + +**Figure 15: Sending of ACM T i/w1 elapses** + +- the reception of the first 180 Ringing. An O-MGCF initiates the sending of an awaiting answer indication only if according to IETF RFC 5009 [89] backward early media is not authorized (the most recently received P-Early-Media header field is received does not authorize the backward early media or the P-Early-Media header field has not yet been received). + + + +Sequence diagram for Figure 16: Sending of ACM (Receipt of first 180 Ringing and backward early media is not authorized). The diagram shows an O-MGCF entity. It receives a 180 Ringing message from the right. In response, it sends an ACM (Subscriber Free) message to the left and a Ring tone (indicated by a dashed line) to the left. + +**Figure 16: Sending of ACM (Receipt of first 180 Ringing and backward early media is not authorized)** + +Based on local knowledge that the call is transited to a PSTN network, the O-MGCF may decide not to generate the awaiting answer indication when receiving the 180 Ringing message and backward early media is not authorized according to IETF RFC 5009 [89]. + + + +Sequence diagram for Figure 16a: Sending of ACM (Receipt of first 180 Ringing and backward early media is authorized). The diagram shows an O-MGCF entity. It receives a 180 Ringing message from the right that includes a P-Early-Media header indicating backward early media is authorized. In response, it sends an ACM (Subscriber Free) message to the left. A Ring tone (indicated by a dashed line) is shown being generated but not sent to the left. + +**Figure 16a: Sending of ACM (Receipt of first 180 Ringing and backward early media is authorized)** + +- the reception of the first 181 Call is Being Forwarded. + + + +This sequence diagram illustrates the interaction at an O-MGCF. A vertical line represents the O-MGCF. An incoming message labeled "181 Call is Being Forwarded" is received from the right. In response, an outgoing message labeled "ACM (Call Diversion information)" is sent to the left. No audio path is established. + +Sequence diagram for Figure 16b showing the O-MGCF sending an ACM message with call diversion information after receiving a 181 Call is Being Forwarded message. No audio is sent. + +**Figure 16b: Sending of ACM (Receipt of first 181 Call is Being Forwarded and backward early media is not authorized)** + + + +This sequence diagram shows the O-MGCF receiving a "181 Call is Being Forwarded" message that includes a "P-Early-Media header: backward early media authorized". The O-MGCF responds with an "ACM (Call Diversion information, OBCI: in-band info available)" message. Following this, an "Audio" path is established, indicated by a dashed line extending to the left. + +Sequence diagram for Figure 16c showing the O-MGCF sending an ACM message with call diversion and OBCI information after receiving a 181 Call is Being Forwarded message that authorizes early media. Audio is then sent. + +**Figure 16c: Sending of ACM (Receipt of first 181 Call is Being Forwarded that includes authorization of early media)** + +- At an O-MGCF once all the following sub-conditions have been met: {1} the reception of the first 183 Session Progress that includes a P-Early-Media header field authorizing backward early media, and {2} SDP preconditions are not used, or applicable SDP preconditions have been met. + + + +This sequence diagram depicts the O-MGCF receiving an "183 Session Progress" message with a "P-Early-Media header: backward early media authorized". The O-MGCF sends back an "ACM (No indication, OBCI: in-band info available)" message. Subsequently, an "Appropriate announcement" is sent, indicated by a dashed line extending to the left. + +Sequence diagram for Figure 16d showing the O-MGCF sending an ACM message with no indication after receiving a 183 Session Progress message that authorizes early media. An appropriate announcement is then sent. + +**Figure 16d: Sending of ACM (Receipt of first 183 Session Progress that includes authorization of early media)** + +- As a network option, reception of 183 containing a SIP reason header with an Q.850 Cause Value. + + + +Sequence diagram showing the sending of ACM (Alerting Call Message) in response to a 183 Session Progress message. The diagram features a vertical line for the O-MGCF. To the left of the line, 'ACM (No indication Cause=xxx)' is shown with an arrow pointing left. To the right of the line, '183 Session Progress (Reason(Cause=xxx))' is shown with an arrow pointing right towards the O-MGCF line. + +**Figure 16e: Sending of ACM (Receipt of 183 Session Progress containing SIP Reason header)** + +- Ti/w 2 expires after the initial INVITE is sent. + + + +Sequence diagram showing the sending of ACM after Ti/w 2 expires. A vertical line represents the O-MGCF. An 'IAM' message is shown with an arrow pointing right towards the O-MGCF. An 'INVITE' message is shown with an arrow pointing right from the O-MGCF. A bracket labeled 'T i/w 2' spans the time between the INVITE and the ACM. The 'ACM (no indication)' message is shown with an arrow pointing left from the O-MGCF. + +**Figure 17: Sending of ACM (Ti/w2 elapses)** + +The sending of an awaiting answer indication is described in clause 9.2.3.3. + +When a 180 (Ringing) response is received with the Alert-Info header field at an O-MGCF supporting capabilities associated with the Alert-Info header field an O-MGCF may instruct the IM-MGW to play out early media available at the associated URL to the PSTN leg of the communication. + +If the O-MGCF receives a 18x response with a P-Early-Media header field that changes the authorization of early media, the O-MGCF terminates the sending of the awaiting answer indication if the header field authorizes backward early media, and initiates the sending of the awaiting answer indication if the header field removes authorization of backward early media and if the O-MGCF has received the 180 Ringing response. + +### 7.2.3.2.5 Coding of the ACM + +#### 7.2.3.2.5.0 General + +The description of the following ISDN user part parameters can be found in ITU-T Recommendation Q.763 [4]. + +##### 7.2.3.2.5.1 Backward call indicators + +| | | | +|------|-----------|--------------------------------------------------------------| +| bits | AB | Charge indicator Contributors | +| | 1 0 | charge | +| bits | DC | Called party's status indicator | +| | 01 | subscriber free if the 180 Ringing has been received. | +| | 00 | no indication otherwise | +| bits | FE | Called party's category indicator | +| | 0 0 | no indication | +| bits | HG | End-to-end method indicator | +| | 0 0 | no end-to-end method available | +| bit | I | Interworking indicator | +| | 1 | interworking encountered | + +As a network operator option, the value I = 0 "no interworking encountered" is used for TMR = 64 kBit/s unrestricted + +NOTE: This avoids sending of a progress indicator with Progress information 0 0 0 0 0 0 1 "Call is not end-to-end ISDN; further call progress information may be available in-band", so the call will not be released for that reason by an ISDN terminal. + +bit J End-to-end information indicator +0 no end-to-end information available +bit K ISDN user part/BICC indicator +0 ISDN user part not used all the way + +As a network operator option, the value K = 1 "ISDN user part/BICC used all the way" is used for TMR = 64 kBit/s unrestricted + +NOTE: This avoids sending of a progress indicator with progress information 0 0 0 0 0 0 1 "Call is not end-to-end ISDN; further call progress information may be available in-band", so the call will not be released for that reason by an ISDN terminal. + +bit L Holding indicator (national use) +0 *holding not requested* +bit M ISDN access indicator +0 *terminating access non-ISDN* + +As a network operator option, the value M = 1 "terminating access ISDN" is used for TMR = 64 kBit/s unrestricted. + +NOTE: This avoids sending of a progress indicator with progress information 0 0 0 0 0 1 0 "Destination access is non-ISDN", so the call will not be released for that reason by an ISDN terminal. + +bit N Echo control device indicator +1 *incoming echo control device included*, for speech calls, e.g., TMR is "3.1KHz audio". +0 *incoming echo control device not included*, for known data calls, e.g., TMR "64 kBit/s unrestricted" or HLC "Facsimile Group 2/3". + +If the PSTN XML body is supported as a network option, the Backward Call indicators parameters derived as shown in table 7.2.3.2.5.1.1 shall take precedence over the above Backward Call indicators parameter setting. + +**Table 7.2.3.2.5.1.1: Derivation of Backward Call Indicators from PSTN XML body** + +| ←ACM | ← 180 Ringing or 183 Session Progress | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Backward call indicators parameter
Optional backward call indicators parameter | PSTN XML body with Progress indicator with "Coding Standard" value "00 (ITU-T standardized coding)" and with "Progress Description" No (Value of PI) | +| Backward call indicators parameter
ISDN User Part indicator
0 "ISDN User Part not used all the way" | No. 1
("Call is not end-to-end ISDN: further call progress information may be available in-band") | +| Backward call indicators parameter
ISDN User Part indicator
1 "ISDN User Part used all the way"
ISDN access indicator
0 "Terminating access non-ISDN" | No. 2
("Destination address is non-ISDN") | +| Backward call indicators parameter
Interworking indicator
0 "no interworking encountered"
ISDN User Part indicator
1 "ISDN User Part used all the way"
ISDN access indicator
1 "Terminating access ISDN" | No. 7
("Terminating user ISDN") | +| Optional backward call indicators parameter
In-band information indicator
1 "in-band information or an appropriate pattern is now available" | No. 8
("In-band information or an appropriate pattern is now available") | + +#### 7.2.3.2.5.2 Optional Backward call indicators + +Bit A 1 "in-band information or an appropriate pattern is now available" shall be set if 183 Session Progress or 181 Call is Being Forwarded response is received and according to IETF RFC 5009 [89] backward early media is authorized. + +**Table 7a0.4: Sending criteria of Optional backward call indicators parameter** + +| ←ACM | ← 183 Session Progress or 181 Call is Being Forwarded | +|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------| +| Optional backward call indicators parameter
In-band information indicator
in-band information or an appropriate pattern is now available | P-Early-Media header authorizing backward early media | + +#### 7.2.3.2.5.3 Access Transport Parameter, Transmission medium used parameter + +If the O-MGCF supports the PSTN XML body as a network option and if a PSTN XML body is received within the 180 ringing or 183 session progress, the O-MGCF shall store the received PSTN XML elements, replacing any previously stored PSTN XML elements on that dialog. + +NOTE: Multiple 18x responses can be received, both within a single dialog and in multiple dialogs. The PSTN XML bodies are stored on a per-dialog basis to be mapped to the ATP/TMU parameters on receipt of the 200 OK (see clause 7.2.3.2.9.2). + +**Table 7.2.3.2.5.3.1: Void** + +#### 7.2.3.2.5.4 Progress indicator + +If the O-MGCF supports the PSTN XML body as a network option and receives it in the 180 or 183, the O-MGCF shall store a "ProgressIndicator" element from the PSTN XML body on a per dialog basis and shall additionally map it into a Progress Indicator in the ACM as shown in table 7.2.3.2.5.4.1. + +**Table 7.2.3.2.5.4.1: Handling of the progress indicator** + +| ←ACM | ←180/183 | +|-----------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Access transport parameter | PSTN XML body with Progress indicator with "Coding Standard" value "00 (ITU-T standardized coding)" and with "Progress Description" No. (Value of PI) | +| Progress indicator (NOTE) | Progress indicator No. 1 / 2 | +| Progress indicator (NOTE) | Progress indicator No. 8 | +| NOTE: The entire Progress Indicator, including the "Progress Description", "Coding Standard" and "Location" parameters shall be copied. | | + +**Table 7.2.3.2.5.4.2: Void** + +#### 7.2.3.2.5.5 Cause Value + +If the O-MGCF sends the ACM upon reception of a SIP 183 provisional response containing a SIP reason header with a Q.850 Cause value, the O-MGCF may include the received Cause value within the ACM as a network option. The mapping of the Cause Indicators parameter to the Reason header as shown in table 8a shall be applied. IETF RFC 6432 [115] describes the use of the Reason header field in responses. The Reason header field itself is described in IETF RFC 3326 [116]. + +If, as a network option, the O-MGCF supports the location header field parameter as described in IETF RFC 8606 [155], the O-MGCF shall derive the ISUP cause location from the location parameter in the SIP Reason header field as shown in table 8c (see subclause 7.2.3.1.7). + +### 7.2.3.2.6 Sending of the Call Progress message (CPG) + +#### 7.2.3.2.6.0 General + +If the Address Complete Message (ACM) has already been sent, the O-MGCF shall send the Call Progress message (CPG) in the following cases: + +- Upon receipt of the SIP 180 Ringing provisional response. An O-MGCF should initiate the sending of an awaiting answer indication only if according to IETF RFC 5009 [89] backward early media is not authorized (the most recently received P-Early-Media header field does not authorize the backward early media or the P-Early-Media header field has not yet been received). + + + +``` + +sequenceDiagram + participant O-MGCF + Note right of O-MGCF: 180 Ringing + O-MGCF->>Left: CPG (Alerting) + Note left of O-MGCF: Ring tone + +``` + +Sequence diagram showing the O-MGCF receiving a 180 Ringing response and sending a CPG (Alerting) message. The diagram shows a vertical line for the O-MGCF. An arrow labeled '180 Ringing' points to the O-MGCF from the right. From the O-MGCF, an arrow labeled 'CPG (Alerting)' points to the left. Below the CPG (Alerting) arrow, a dashed arrow labeled 'Ring tone' also points to the left. + +**Figure 18: Sending of CPG(Alerting) (Receipt of 180 Ringing response and backward early media is not authorized)** + + + +This sequence diagram illustrates the interaction between an O-MGCF and a CPG (Alerting) entity. The O-MGCF receives a '180 Ringing' response containing a 'P-Early-Media header: backward early media authorized'. In response, the O-MGCF sends a 'CPG (Alerting)' message to the CPG entity. The CPG entity then generates a 'Ring tone'. A dashed line at the bottom indicates the continuation of the sequence. + +Sequence diagram for Figure 18a: Sending of CPG(Alerting) (Receipt of 180 Ringing response with authorization of early media). + +**Figure 18a: Sending of CPG(Alerting) (Receipt of 180 Ringing response with authorization of early media)** + +Based on local knowledge that the call is transited to a PSTN network, the O-MGCF may decide not to generate the awaiting answer indication when receiving the 180 Ringing message and backward early media is not authorized according to IETF RFC 5009 [89]. + +- At an O-MGCF upon receipt of a 183 Session Progress that includes the first P-Early-Media header field authorizing backward early media. + + + +This sequence diagram shows the O-MGCF receiving a '183 Session Progress' message with a 'P-Early-Media header: backward early media authorized'. The O-MGCF then sends a 'CPG (In-band information available)' message to the CPG entity. Following this, an 'Appropriate announcement' is generated. A dashed line at the bottom indicates the continuation of the sequence. + +Sequence diagram for Figure 18b: Sending of CPG(in-band information available). + +**Figure 18b: Sending of CPG(in-band information available)** + +- Upon receipt of the 181 Call is Being Forwarded provisional response. + + + +This sequence diagram depicts the O-MGCF receiving a '181 Call is Being Forwarded' provisional response with a 'P-Early-Media header: backward early media authorized'. The O-MGCF sends a 'CPG (Progress, OBCI: in-band info available)' message to the CPG entity. Subsequently, 'Audio' is generated. A dashed line at the bottom indicates the continuation of the sequence. + +Sequence diagram for Figure 18c: Sending of CPG(Progress). + +**Figure 18c: Sending of CPG(Progress)** + +- As a network option, reception of 183 containing a SIP reason header with a Q.850 Cause Value. + + + +The diagram illustrates a message flow between two entities: O-MGCF and CPG (in-band information available Cause=xxx). A horizontal line represents the timeline. On the right, the O-MGCF sends a message labeled "183 Session Progress (Reason(Cause=xxx))". An arrow points from this message to the left, towards the CPG entity. The CPG entity is labeled "CPG (in-band information available Cause=xxx)". + +Diagram showing the sending of CPG (Receipt of 183 Session Progress containing SIP Reason header) from O-MGCF to CPG (in-band information available Cause=xxx). + +**Figure 18d: Sending of CPG (Receipt of 183 Session Progress containing SIP Reason header)** + +If the O-MGCF receives a 18x response with P-Early-Media header that changes the authorization of early media, the O-MGCF terminates the sending of the awaiting answer indication if the header authorizes backward early media and initiates the sending of the awaiting answer indication if the header removes authorization of backward early media and if the O-MGCF has received the 180 Ringing response. + +#### 7.2.3.2.6.1 Handling of the progress indicator + +If the O-MGCF supports the PSTN XML body as a network option and receives it in the 180 or 183, any "ProgressIndicator" element in the PSTN XML body shall be stored on a per-dialog basis as well as mapped as shown in tables 7.2.3.2.6.1.1 and 7.2.3.2.6.1.3. + +**Table 7.2.3.2.6.1.1: Mapping of progress indicator in PSTN XML body into ATP** + +| ←CPG | ←180/183 | +|-------------------------------------------|-----------------------------------------| +| Access transport parameter | PSTN XML body with Progress indicator X | +| Progress indicator (NOTE 1, NOTE 3) | Progress indicator No. 1 / 2 | +| Progress indicator (NOTE 2, NOTE 3) | Progress indicator No. 4 | +| Progress indicator No. 4 (NOTE 2, NOTE 4) | Progress indicator No. 7 | + +NOTE 1: Values 1 ("call is not end-to-end ISDN: further call progress information may be available in-band") or 2 ("destination address is non-ISDN") shall be sent if Value 4 ("Call has returned to the ISDN") has been sent since value 1 or 2 was previously sent or if no value 1 or 2 was previously sent. + +NOTE 2: Value 4 ("Call has returned to the ISDN") shall be sent if value 1 ("call is not end-to-end ISDN: further call progress information may be available in-band") or 2 ("destination address is non-ISDN") was sent previously and no value 4 has been signalled since. + +NOTE 3: The entire Progress Indicator, including the "Progress Description", "Coding Standard" and "Location" parameters shall be copied. + +NOTE 4: The Progress Indicator "Coding Standard" parameter shall be set to "00 (ITU-T standardized coding)". The default value for the Progress Indicator "Location" parameter is "0100 (Public Network serving remote user)". + +**Table 7.2.3.2.6.1.2: Void** + +**Table 7.2.3.2.6.1.3: Mapping of progress indicator in PSTN XML body into Event Indicator** + +| ←CPG | ←180/183 | +|---------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| +| Event indicator | PSTN XML body with Progress indicator with "Coding Standard" value "00 (ITU-T standardized coding)" and with Progress Description" value No. X | +| "In-band information or appropriate pattern is now available" | No. 8
"In-band information or appropriate pattern is now available" | + +#### 7.2.3.2.7 Coding of the CPG + +##### 7.2.3.2.7.0 General + +The description of the following ISDN user part parameters can be found in ITU-T Recommendation Q.763 [4]. + +##### 7.2.3.2.7.1 Event information + +bits G-A Event indicator + +0 0 0 0 0 0 1 *alerting* if 180 Ringing response received + +0 0 0 0 0 1 0 *progress*, if 181 Call is Being Forwarded response received + +0 0 0 0 0 1 1 *in-band information or an appropriate pattern is now available*, if the received 183 Session Progress response and most recently received P-Early-Media header authorizes backward early media + +NOTE: In national networks other values of the Event indicator may be used. + +If the O-MGCF supports the PSTN XML body as a network option and receives in the 180 or 183 a "ProgressIndicator" element in the PSTN XML body with a "Coding Standard" value "00 (ITU-T standardized coding)" and with Progress Description" value No. 8, instead of the mapping above, the O-MGCF shall map this "Progress Indicator" into the "Event Indicator" within the CPG as shown in table 7.2.3.2.6.1.3. + +#### 7.2.3.2.7.2 Access Transport Parameter + +If the O-MGCF supports the PSTN XML body as a network option and if a PSTN XML body is received within the 180 ringing or 183 session progress, the O-MGCF shall store the contained information as described in clause 7.2.3.2.5.3, and additionally shall map this "Progress Indicator" into the ATP within the CPG as shown in table 7.2.3.2.6.1.1. + +NOTE: Multiple 18x responses can be received, both within a single dialog and in multiple dialogs. The PSTN XML bodies are stored on a per-dialog basis to be mapped to the ATP parameter on receipt of the 200 OK (see clause 7.2.3.2.9.2). + +#### 7.2.3.2.7.3 Void + +**Table 17h: Void** + +**Table 17j: Void** + +#### 7.2.3.2.7.4 Handling of Backward Call indicators + +The Backward Call indicator shall be derived as shown in clause 7.2.3.2.5.1. The Backward Call Indicators parameter is optional in the CPG message and shall only be included if any indicators have changed from those previously sent. + +#### 7.2.3.2.7.5 Optional Backward call indicators + +Bit A 1 "in-band information or an appropriate pattern is now available" shall be set if 181 Call is Being Forwarded response is received and according to IETF RFC 5009 [89] the backward early media is authorized. + +**Table 17k: Sending criteria of Optional backward call indicators parameter** + +| ←CPG | ← 181 Call is Being Forwarded | +|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------| +| Optional backward call indicators parameter
In-band information indicator
in-band information or an appropriate pattern is now available | P-Early-Media header authorizing backward early media | + +#### 7.2.3.2.7.6 Cause Value + +If the O-MGCF sends the CPG upon reception of a SIP 183 provisional response containing a SIP reason header with a Q.850 Cause value, the O-MGCF may include the received Cause value within the ACM as a network option. The mapping of the Cause Indicators parameter to the Reason header as shown in table 8a shall be applied. IETF RFC 6432 [115] describes the use of the Reason header field in responses. The Reason header field itself is described in IETF RFC 3326 [116]. + +If, as a network option, the O-MGCF supports the location header field parameter as described in IETF RFC 8606 [155], the O-MGCF shall derive the ISUP cause location from the location parameter in the SIP Reason header field as shown in table 8c (see subclause 7.2.3.1.7). + +#### 7.2.3.2.7a Receipt of 200 OK(INVITE) + +Upon receipt of the first 200 OK (INVITE), the O-MGCF shall send an Answer Message (ANM) or Connect message (CON) as described in clauses 7.2.3.2.8 to 7.2.3.2.11. + +The O-MGCF shall not progress any further early dialogues to established dialogues. Therefore, upon the reception of a subsequent final 200 (OK) response for any further dialogue for an INVITE request (e.g., due to forking), the O-MGCF shall: + +- 1) acknowledge the response with an ACK request; and +- 2) send a BYE request to this dialog in order to terminate it. + +If the received 200 OK (INVITE) response contains a Feature-Caps header field, defined in IETF RFC 6809 [142] with a "+g.3gpp.ics" header field parameter as specified in clause B.4 of 3GPP TS 24.292 [141] then according to operator policy the O-MGCF may mark a call as an "ICS call". + +#### 7.2.3.2.7b Internal through connection of the bearer path + +The through connection procedure is described in clause 9.2.3.3.7. + +#### 7.2.3.2.8 Sending of the Answer Message (ANM) + +Upon receipt of the first 200 OK (INVITE), if the Address Complete Message (ACM) has already been sent, the O-MGCF shall send the Answer Message (ANM) to the preceding exchange. + +NOTE: Through connection and the stop of awaiting answer indication are described in clause 9.2.3.3 + + + +``` +graph LR; subgraph O-MGCF; direction TB; ANM[ANM] --> Left[ ]; Right[ ] --> ANM; end; Right -- "200 OK (INVITE)" --> Right; ANM --> Left; +``` + +Diagram illustrating the sending of the Answer Message (ANM) by the O-MGCF. A vertical line represents the O-MGCF. An arrow labeled '200 OK (INVITE)' points from the right towards the O-MGCF line. An arrow labeled 'ANM' points from the O-MGCF line towards the left. + +**Figure 19: Sending of ANM** + +#### 7.2.3.2.9 Coding of the ANM + +##### 7.2.3.2.9.1 Backwards Call Indicators + +If Backwards Call Indicators are included in the ANM, then the coding of these parameters shall be as described in clause 7.2.3.2.5.1. The Backward Call Indicators parameter is optional in the ANM message and shall only be included if any indicators have changed from those previously sent. + +##### 7.2.3.2.9.2 Access Transport Parameter + +If the O-MGCF supports the PSTN XML body as a network option and if a PSTN XML body is received within the 200 OK(INVITE) or has been previously stored from a 18x message, the O-MGCF shall map the most recently received information for the established dialog (i.e. the dialog for which the first 200 OK has been received) into the ANM as shown in table 7.2.3.2.9.2.1 except Progress Indicator value No. 3 or No. 8. + +**Table 7.2.3.2.9.2.1: Mapping of PSTN XML elements into ISUP Parameters** + +| ANM | | 200 OK / stored information from previous 18x | +|----------------------------|-------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| ISUP Parameter | Content | PSTN XML (NOTE 9) | +| Access Transport Parameter | Progress indicator (NOTE 5, NOTE 8) | ProgressIndicator with "Coding Standard" value "00 (ITU-T standardized coding)" and with "Progress Description" value No. 1 / 2 | +| | Progress indicator with "Progress Description" value No. 4 (NOTE 4, NOTE 6, NOTE 9) | ProgressIndicator with "Coding Standard" value "00 (ITU-T standardized coding)" and with "Progress Description" value No. 7 | +| | Progress indicator (NOTE 6, NOTE 8) | ProgressIndicator with "Coding Standard" value "00 (ITU-T standardized coding)" and with "Progress Description" value No. 4 | +| | Progress indicator (NOTE 7, NOTE 8) | ProgressIndicator with "Coding Standard" value "00 (ITU-T standardized coding)" and with "Progress Description" value No. 5 | +| | High layer compatibility (NOTE 1) | HighLayerCompatibility | +| | Bearer Capability | BearerCapability (NOTE 2) | +| | Bearer Capability ("UDI-TA") | BearerCapability ("UDI-TA") (NOTE 3) | + +NOTE 1: This information element shall only be mapped if the O-MGCF transfers media types listed in table 10b without transcoding. + +NOTE 2: Applicable if the O-MGCF has not propagated UDI fallback signalling according to clause 7.2.3.2.1.5. + +NOTE 3: Applicable if the O-MGCF has propagated UDI fallback signalling according to clause 7.2.3.2.1.5. Only the value "UDI-TA" within the PSTN XML BC shall be mapped. Other values within the PSTN XML BC are mapped to TMU as described in clause 7.2.3.2.9.3. + +NOTE 4: ProgressIndicator No. 7 is not mapped into the ISUP ATP. However, it may be mapped into PI=4. + +NOTE 5: Values 1 ("call is not end-to-end ISDN: further call progress information may be available in-band") or 2 ("destination address is non-ISDN") shall be sent if Value 4 ("Call has returned to the ISDN") has been sent since value 1 or 2 was previously sent or if no value 1 or 2 was previously sent. + +NOTE 6: Value 4 ("Call has returned to the ISDN") shall be sent if value 1 ("call is not end-to-end ISDN: further call progress information may be available in-band") or 2 ("destination address is non-ISDN") was sent previously and no value 4 has been signalled since. + +NOTE 7: This value indicates a bearer service change and is present with an associated BearerCapability and indicates that fallback has occurred (i.e. TMR and TMR Prime present in IAM and the destination ISDN user has accepted the BearerCapability equating to TMR Prime). + +NOTE 8: The entire Progress Indicator, including the "Progress Description", "Coding Standard" and "Location" parameters shall be copied. + +NOTE 9: The Progress Indicator "Coding Standard" parameter shall be set to "00 (ITU-T standardized coding)". The default value for the Progress Indicator "Location" parameter is "0100 (Public Network serving remote user)". + +### 7.2.3.2.9.3 Transmission Medium Used parameter (TMU) + +The procedures in the present clause shall only apply if the O-MGCF supports the PSTN XML body, and has propagated UDI-TA fallback signalling according to clause 7.2.3.2.1.5. + +If a Bearer Capability element within a PSTN XML body is received within the first 200 OK(INVITE) or has been previously stored from a 18x message relating to the now established dialog (i.e. the dialogue for which the first 200 OK has been received), the O-MGCF shall map the most recently received information (if any) into a TMU within the ANM as shown in table 7.2.3.2.9.3.1. If the most recently received PSTN XML BearerCapability is "UDI-TA", it shall be mapped into an ISUP Access Transport Parameter Bearer Capability (see clause 7.2.3.2.9.2). + +NOTE: The TMU is only included if both the TMR and TMR Prime were received in the ISUP IAM and fallback has occurred. + +**Table 7.2.3.2.9.3.1 - Mapping to TMU parameter** + +| ANM | 200 OK / stored information from previous 18x | +|----------------------------------------|-----------------------------------------------| +| TMU | PSTN XML BearerCapability | +| TMU = "Speech" | PSTN XML BearerCapability = "Speech" | +| TMU= "3.1 kHz audio" | PSTN XML BearerCapability = "3.1 kHz audio" | +| No mapping (fallback has not occurred) | PSTN XML BearerCapability = "UDI-TA" | +| TMU = "3.1 kHz audio" | PSTN XML BearerCapability not present | + +### 7.2.3.2.10 Sending of the Connect message (CON) + +Upon receipt of the first 200 OK (INVITE), if the Address Complete Message (ACM) has not yet been sent, the O-MGCF shall send the Connect message (CON) to the preceding exchange. + + + +The diagram illustrates the sequence of messages for sending a Connect message (CON). A vertical line represents the O-MGCF. An arrow labeled "200 OK (INVITE)" points from the right towards the O-MGCF line. From the O-MGCF line, an arrow labeled "CON" points to the left. + +Diagram showing the O-MGCF sending a CON message after receiving a 200 OK (INVITE). + +**Figure 20: Sending of CON** + +### 7.2.3.2.11 Coding of the CON + +#### 7.2.3.2.11.0 General + +The description of the following ISDN user part parameters can be found in ITU-T Recommendation Q.763 [4]. + +#### 7.2.3.2.11.1 Backward call indicators + +The Called Party's status indicator (Bit DC) of BCI parameter shall be set to "no indication". The other BCI indicators shall be set as described in clause 7.2.3.2.5.1 + +#### 7.2.3.2.11.2 Access Transport Parameter + +The O-MGCF shall apply the same procedure as described for the ANM in clause 7.2.3.2.9.2. + +#### 7.2.3.2.11.3 Transmission medium used parameter + +The O-MGCF shall apply the same procedure as described for the ANM in clause 7.2.3.2.9.3. + +### 7.2.3.2.11A Receipt of a reINVITE request + +When a reINVITE request is received from the network containing a Call-Info header field the MGCF may instruct the IM-MGW to send media available at the associated URL to the PSTN leg of the communication. + +### 7.2.3.2.12 Receipt of Status Codes 4xx, 5xx or 6xx + + + +The diagram illustrates the sequence of messages for receiving status codes. A vertical line represents the O-MGCF. A box on the right contains the text "Status Code 4xx, 5xx or 6xx". An arrow points from this box to the O-MGCF line. From the O-MGCF line, an arrow labeled "REL" points to the left. + +Diagram showing the O-MGCF receiving a Status Code (4xx, 5xx or 6xx) and sending a REL message. + +**Figure 21: Receipt of Status codes 4xx, 5xx or 6xx** + +If a Reason header as described in IETF RFC 6432 [115] is included in a 4xx, 5xx, 6xx response, then the Cause Value of the Reason header shall be mapped to the ISUP Cause Value field in the ISUP REL message. The Reason header field itself is described in IETF RFC 3326 [116]. The mapping of the Reason header to the Cause Indicators parameter is shown in table 8a (see clause 7.2.3.1.7). Otherwise coding of the Cause value field in the REL message is derived + +from the SIP Status code received according to table 18. The Cause Indicators Parameter Values are defined in ITU-T Recommendation Q.850 [38]. + +If, as a network option, the O-MGCF supports the location header field parameter as described in IETF RFC 8606 [155], the O-MGCF shall derive the ISUP cause location from the location parameter in the SIP Reason header field as shown in table 8c (see subclause 7.2.3.1.7). + +In all cases where SIP itself specifies additional SIP side behaviour related to the receipt of a particular INVITE response these procedures should be followed in preference to the immediate sending of a REL message to BICC/ISUP. + +If there are no SIP side procedures associated with this response, the REL shall be sent immediately. + +**NOTE** Depending upon the SIP side procedures applied at the O-MGCF it is possible that receipt of certain 4xx/5xx/6xx responses to an INVITE may in some cases not result in any REL message being sent to the BICC/ISUP network. For example, if a 401 Unauthorized response is received and the O-MGCF successfully initiates a new INVITE containing the correct credentials, the call will proceed. + +When the O-MGCF receives a 415 Unsupported Media Type response, as a result from a multipart MIME body in an initial INVITE request not being accepted, and when the handling of all the MIME bodies in the initial INVITE request except for the SDP MIME body are optional (Content-Disposition header parameter "handling" is set to optional), the O-MGCF shall send an ACK request and send a new initial INVITE request with SDP as only MIME body in accordance with clause 8.1.3.5 of IETF RFC 3261 [19]. + +**Table 18: 4xx/5xx/6xx Received on SIP side of O-MGCF** + +| ←REL (cause value) | ←4xx/5xx/6xx SIP Message | +|-----------------------------------------------------------------------------|--------------------------------------| +| Cause value No 111 (Protocol error, unspecified) | 400 Bad Request | +| Cause value No 127 (Interworking, unspecified) | 401 Unauthorized | +| Cause value No 127 (Interworking, unspecified) | 402 Payment Required | +| Cause value No 79 (Service or option not implemented, unspecified) | 403 Forbidden | +| Cause value No 1 (Unallocated (unassigned) number) | 404 Not Found | +| Cause value No 127 (Interworking, unspecified) | 405 Method Not Allowed | +| Cause value No 127 (Interworking, unspecified) | 406 Not Acceptable | +| Cause value No 127 (Interworking, unspecified) | 407 Proxy authentication required | +| Cause value No 102 (Recovery on timer expiry) | 408 Request Timeout | +| Cause value No 22 (Number changed) | 410 Gone | +| Cause value No 127 (Interworking, unspecified) | 413 Request Entity too long | +| Cause value No 111 (Protocol error, unspecified) | 414 Request-URI too long | +| Cause value No 127 (Interworking, unspecified) | 415 Unsupported Media type | +| Cause value No 111 (Protocol error, unspecified) | 416 Unsupported URI scheme | +| Cause value No 79 (Service or option not implemented, unspecified) | 417 Unknown Resource-Priority | +| Cause value No 111 (Protocol error, unspecified) | 420 Bad Extension | +| Cause value No 111 (Protocol error, unspecified) | 421 Extension required | +| Cause value No 31 (Normal, unspecified) | 422 Session Interval Too Small | +| Cause value No 127 (Interworking, unspecified) | 423 Interval Too Brief | +| Cause value No 127 (Interworking, unspecified) | 428 Use Identity Header (NOTE 5) | +| Cause value No 24 (Call rejected due to feature at the destination) | 433 Anonymity Disallowed (NOTE 1) | +| Cause value No 127 (Interworking, unspecified) | 436 Bad Identity Info (NOTE 5) | +| Cause value No 127 (Interworking, unspecified) | 437 Unsupported Credential (NOTE 5) | +| Cause value No 127 (Interworking, unspecified) | 438 Invalid Identity Header (NOTE 5) | +| Cause value No 127 (Interworking, unspecified) | 440 Max-Breadth Exceeded | +| Cause value No 20 (Subscriber absent) | 480 Temporarily Unavailable | +| Cause value No 127 (Interworking, unspecified) | 481 Call/Transaction does not exist | +| Cause value No 127 (Interworking, unspecified) | 482 Loop detected | +| Cause value No 25 (Exchange routing error) | 483 Too many hops | +| Cause value No 28 (Invalid number format (address incomplete)) | 484 Address Incomplete | +| Cause value No 1 (Unallocated (unassigned) number) | 485 Ambiguous | +| Cause value No 17 (User busy) | 486 Busy Here | +| Cause value No 127 (Interworking, unspecified) or not interworked. (NOTE 2) | 487 Request terminated | +| Cause value No 50 (Requested facility not subscribed) | 488 Not acceptable here | +| Cause value No 127 (Interworking, unspecified) | 493 Undecipherable | +| Cause value No 127 (Interworking, unspecified) | 500 Server Internal error | +| Cause value No 79 (Service or option not implemented, unspecified) | 501 Not implemented | +| Cause value No 27 (Destination out of order) | 502 Bad Gateway | +| Cause value No 41 (Temporary failure) | 503 Service Unavailable | +| Cause value No 102 (Recovery on timer expiry) | 504 Server timeout | +| Cause value No 127 (Interworking, unspecified) | 505 Version not supported | +| Cause value No 95 (Invalid message, unspecified) | 513 Message too large | +| Cause value No 127 (Interworking, unspecified) | 580 Precondition failure | +| Cause value No 17 (User busy) | 600 Busy Everywhere | +| Cause value No 21 (Call rejected) | 603 Decline | +| Cause value No 2 (No route to specified transit network) | 604 Does not exist anywhere | +| Cause value No 88 (Incompatible destination) | 606 Not Acceptable | +| Cause value No 21 (Call rejected) | 607 Unwanted (NOTE 4) | + +NOTE 1: Anonymity Disallowed, IETF RFC 5079 [77] refers. +NOTE 2: No interworking if the O-MGCF previously issued a CANCEL request for the INVITE. +NOTE 3: The 4xx/5xx/6xx SIP responses that are not covered in this table are not interworked. +NOTE 4: The "607 Unwanted" SIP response code is defined in IETF RFC 8197 [154]. +NOTE 5: The 428, 436, 437 and 438 SIP response codes are defined in IETF RFC 8224 [153]. + +If the O-MGCF supports the PSTN XML body as a network option and if a PSTN XML body is received within the 4xx/5xx/6xx, the O-MGCF shall map the contained information into the Access Transport Parameter of the REL as shown in clause 7.2.3.2.9.2. + +When a 4xx, 5xx or 6xx SIP response to an INVITE request is received from the network containing an Error-Info header field, the O-MGCF, supporting the capabilities associated with the Error-Info header field, may instruct the IM-MGW to play out media available at the associated URL towards PSTN. + +#### 7.2.3.2.12.1 Special handling of 404 Not Found and 484 Address Incomplete responses after sending of INVITE without determining the end of address signalling + +This clause is only applicable when the network option of Sending of INVITE without determining the end of address signalling is being used (see clause 7.2.3.2.1.a). + +On receipt of a 404 Not Found or 484 Address Incomplete response while Ti/w2 is running, the O-MGCF shall start timer Ti/w3, if there are no other pending INVITE transactions for the corresponding call. + +At the receipt of a SAM, a SIP 1xx provisional response or a SIP 200 OK (INVITE), the O-MGCF shall stop Ti/w2 and Ti/w3. + +The O-MGCF shall send a REL message with Cause Value 28 towards the BICC/ISUP network if Ti/w3 expires. + +#### 7.2.3.2.13 Receipt of a BYE + + + +``` + +graph LR + subgraph O-MGCF + direction TB + BYE[BYE] --> REL[REL] + end + O-MGCF -- REL --> Left[ ] + Right[ ] -- BYE --> O-MGCF + style Left fill:none,stroke:none + style Right fill:none,stroke:none + +``` + +Diagram illustrating the receipt of a BYE method. A vertical line represents the O-MGCF. An arrow labeled 'BYE' points from the right towards the O-MGCF. An arrow labeled 'REL' points from the O-MGCF towards the left. + +**Figure 22: Receipt of BYE method** + +If a Reason header field with Q.850 Cause Value is included in the BYE request, then the Cause Value shall be mapped to the ISUP Cause Value field in the ISUP REL as shown in table 8a (see clause 7.2.3.1.7). Otherwise, the O-MGCF sends a REL message with Cause Code value 16 (Normal Call Clearing). + +If, as a network option, the O-MGCF supports the location header field parameter as described in IETF RFC 8606 [155], the O-MGCF shall derive the ISUP cause location from the location parameter in the SIP Reason header field as shown in table 8c (see subclause 7.2.3.1.7). + +If the O-MGCF supports the PSTN XML body as a network option and if a PSTN XML body is received within the BYE, the O-MGCF shall map the contained information into the Access Transport Parameter of the REL as shown in clause 7.2.3.2.9.2. + +If a Reason header field with SIP status code "607 (Unwanted)" (defined in IETF RFC 8197 [154]) is included in the BYE request, then the O-MGCF shall send a REL message with the Cause Code value "21 (Call rejected)". + +#### 7.2.3.2.14 Receipt of the Release Message + +In the case that the REL message is received and a final response (i.e. 200 OK (INVITE)) has already been received the O-MGCF shall send a BYE request. If the final response (i.e. 200 OK (INVITE)) has not already been received the O-MGCF shall send a CANCEL method. + +A Reason header field containing the received (Q.850) Cause Value of the REL message shall be added to the CANCEL or BYE request. The mapping of the Cause Indicators parameter to the Reason header is shown in table 9a (see clause 7.2.3.1.8). + +If the O-MGCF supports the PSTN XML body as a network option, the O-MGCF shall map the contained information into a PSTN XML body within the BYE or CANCEL as shown in table 9aa. + +#### 7.2.3.2.15 Receipt of RSC, GRS or CGB (H/W oriented) + +Upon receipt of a RSC, GRS or CGB (H/W oriented) message the following applies independently for each affected circuit: + +NOTE: For the RSC message, the circuit identified by the CIC is affected. + For the GRS message, the affected circuits are identified by the CIC and the Range subfield of the Range and Status parameter. + For the CGB message, the affected circuits are identified by the CIC and the Range and Status parameter. + +If a final response (i.e. 200 OK (INVITE)) has already been received, the O-MGCF shall send a BYE method. If a final response (i.e. 200 OK (INVITE)) has not already been received, the O-MGCF shall send a CANCEL method. + +A Reason header field containing the (Q.850) Cause Value of the REL message generated by the ISUP procedures shall be added to the SIP message (BYE or CANCEL request) to be sent by the SIP side of the O-MGCF. + +#### 7.2.3.2.16 Autonomous Release at O-MGCF + +If the O-MGCF determines due to internal procedures that the call shall be released then the MGCF shall send + +- A BYE method if the ACK has been sent. +- A CANCEL method before 200 OK (INVITE) has been received. + +NOTE: The MGCF shall send the ACK method before it sends the BYE, if 200 OK (INVITE) is received. + +A Reason header field containing the (Q.850) Cause Value of the REL message sent by the O-IWU shall be added to the SIP Message (BYE or CANCEL request) to be sent by the SIP side of the O-IWU. + +**Table 18a: Autonomous Release at O-MGCF** + +| REL
Cause parameter | Trigger event |
SIP |
+|---------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|
+| As determined by BICC/ISUP procedure. | COT received with the Continuity Indicators parameter set to " continuity check failed " (ISUP only) or the BICC/ISUP timer T8 expires. | CANCEL or BYE according to the rules described in this subclause. |
+| REL with cause value 47 (resource unavailable, unspecified). | Internal resource reservation unsuccessful | As determined by SIP procedure |
+| As determined by BICC/ISUP procedure. | BICC/ISUP procedures result in generation of autonomous REL on BICC/ISUP side. | CANCEL or BYE according to the rules described in this subclause. |
+| Depending on the SIP release reason. | SIP procedures result in a decision to release the call. | As determined by SIP procedure. |
+
+#### 7.2.3.2.17 Special handling of 580 precondition failure received in response to either an INVITE or UPDATE
+
+A 580 Precondition failure response may be received as a response either to an INVITE or to an UPDATE request.
+
+##### 7.2.3.2.17.1 580 Precondition failure response to an INVITE
+
+Release with cause code as indicated in table 18 is sent immediately to the BICC/ISUP network.
+
+##### 7.2.3.2.17.2 580 Precondition failure response to an UPDATE within an early dialog
+
+A BYE request is sent for the early dialog within which the UPDATE was sent.
+
+If all the early dialogs that were generated from the INVITE request have answered the respective UPDATE request with 580 Precondition failure response then the O-MGCF shall send the Release message with Cause Code '127 Interworking' to the ISUP network.
+
+### 7.2.3.2.18 Sending of CANCEL
+
+
+
+The diagram illustrates the O-MGCF's response to a failure. A horizontal arrow labeled "COT (failure)" points from the left towards a vertical line representing the O-MGCF. From the O-MGCF, a horizontal arrow labeled "CANCEL" points to the right.
+
+Diagram showing the receipt of a COT (failure) message by the O-MGCF and the subsequent sending of a CANCEL message.
+
+**Figure 23: Receipt of COT (failure)**
+
+CANCEL shall be sent if the Continuity message is received with the Continuity Indicators parameter set to "*continuity check failed*" or the ISUP (or BICC) timer T8 expires.
+
+A Reason header field containing the (Q.850) Cause Value 41 Temporary Failure shall be added to the CANCEL request to be sent by the SIP side of the O-MGCF.
+
+### 7.2.3.2.19 Receipt of SIP redirect (3xx) response
+
+
+
+The diagram illustrates the O-MGCF's response to a SIP redirect. A horizontal arrow points from a box labeled "SIP response code 3xx" towards a vertical line representing the O-MGCF. From the O-MGCF, a horizontal arrow labeled "REL (Cause value 127)" points to the left.
+
+Diagram showing the receipt of a SIP response code 3xx by the O-MGCF and the subsequent sending of a REL (Cause value 127) message.
+
+**Figure 24: Receipt of SIP response code 3xx**
+
+When receiving a SIP response with a response code 3xx, the default behaviour of the O-MGCF is to release the call with a cause code value 127 (Interworking unspecified).
+
+NOTE: The O-MGCF may also decide for example to redirect the call towards the URIs in the Contact header field of the response as an operator option, but such handling is outside of the scope of the present document.
+
+### 7.2.3.2.20 Sending of INFO for overlap signalling using the in-dialog method
+
+#### 7.2.3.2.20.1 General
+
+SIP INFO request ("legacy" mode of usage of the INFO method as defined in IETF RFC 6086 [133]) is used to carry additional digits when overlap signalling is sent using the in-dialog method as described in clause 7.2.3.2.1a.2, which is a network option. Clause 7.2.3.2.1a.2 also describes when the O-MGCF sends a SIP INFO request.
+
+#### 7.2.3.2.20.2 Encoding of the INFO
+
+Table 18b provides a summary of how the header fields within the outgoing INFO messages are populated when in-dialog SIP INFO requests are used for overlap dialling.
+
+**Table 18b: Interworked contents of the INFO message**
+
+| SAM→ | INFO→ |
+|--------|-----------------------------------|
+| Digits | See TS 24.229 [9] clause 7.12.1.2 |
+
+### 7.2.3.3 Timers
+
+**Table 19: Timers for interworking**
+
+| Symbol | Time-out value | Cause for initiation | Normal termination | At expiry | Reference |
+|--------|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------|-----------------------------------------|
+| Ti/w1 | 4 s to 6 s(default of 4 s) | When last address message is received and the minimum number of digits required for routing the call have been received. | At the receipt of fresh address information. | Send INVITE, send the address complete message | 7.2.3.2.1
7.2.3.2.4
(NOTE 1) | +| Ti/w2 | 4 s to 20 s
(default of 4 s) | When INVITE is sent unless the ACM has already been sent. | On reception of 180 Ringing , or 183 Session Progress and P-Early-Media header authorizing backward early media, or 181 Call is Being Forwarded, or 404 Not Found or 484 Address Incomplete for an INVITE transaction for which Ti/w3 is running, or 200 OK (INVITE). | Send ACM (no indication) | 7.2.3.2.4
7.2.3.2.1
(NOTE 2) | +| Ti/w3 | 4-6 seconds
(default of 4 seconds) | On receipt of 404 Not Found or 484 Address Incomplete if there are no other pending INVITE transactions for the corresponding call. | At the receipt of SAM | Send REL with Cause Value 28 to the BICC/ISUP side. | 7.2.3.2.1A,
7.2.3.2.12.1
(NOTE 3) | + +NOTE 1: This timer is used when overlap signalling is received from BICC/ISUP network and converted to en-block signalling at the MGCF. + +NOTE 2: This timer is used to send an early ACM if a delay is encountered in receiving a response from the subsequent SIP network. + +NOTE 3: This timer is known as the "SIP dialog protection timer". This timer is only used where the O-MGCF is configured to send INVITE before end of address signalling is determined. + +## 7.3 Interworking between CS networks supporting BICC and the IM CN subsystem + +The control plane between CS networks supporting BICC and the IM CN subsystem supporting SIP, where the underlying network is SS7 and IP respectively is as shown in figures 25, 26 and 27. + + + +Diagram of Control Plane interworking between CS networks supporting BICC over MTP3 and the IM CN subsystem. The diagram shows four main functional blocks: SS7 signalling function, Signalling gateway function, Media gateway control function, and SIP signalling function. The SS7 signalling function contains layers BICC, STC, MTP3, MTP2, and L1. It connects via an SS7 link to the Signalling gateway function, which contains layers MTP3, MTP2, L1, M3UA, SCTP, and IP. The Signalling gateway function connects via an IP link to the Media gateway control function, which contains layers BICC, STC, M3UA, SCTP, IP, SIP, TCP/UDP/SCTP, and IP. The Media gateway control function connects via a SIP link to the SIP signalling function, which contains layers SIP, TCP/UDP/SCTP, and IP. Arrows indicate the flow of signalling: BICC over MTP3 from the SS7 function to the Media gateway control function, and SIP from the Media gateway control function to the SIP signalling function. + +**Figure 25: Control Plane interworking between CS networks supporting BICC over MTP3 and the IM CN subsystem** + + + +Figure 26: Control Plane interworking between CS networks supporting BICC over MTP3B over AAL5 and the IM CN subsystem. The diagram shows four main entities: SS7 signalling function, Signalling gateway function, Media gateway control function, and SIP signalling function. The SS7 signalling function contains layers BICC, STC, MTP3B, SSCF, SSCOP, and AAL5. The Signalling gateway function contains layers MTP3B, M3UA, SSCF, SCTP, SSCOP, IP, and AAL5. The Media gateway control function contains layers BICC, STC, M3UA, SCTP, IP, and SIP. The SIP signalling function contains layers SIP, TCP/UDP/SCTP, and IP. Connections are: BICC between SS7 and MGCF; AAL5 between SS7 and SGW; IP between SGW and MGCF; SIP between MGCF and SIP SF; and IP between MGCF and SIP SF. + +**Figure 26: Control Plane interworking between CS networks supporting BICC over MTP3B over AAL5 and the IM CN subsystem** + + + +Figure 27: Control Plane interworking between CS networks supporting BICC over STC and M3UA and the IM CN subsystem. The diagram shows three main entities: SS7 signalling function, Media gateway control function, and SIP signalling function. The SS7 signalling function contains layers BICC, STCMTP, M3UA, SCTP, and IP. The Media gateway control function contains layers BICC, STCMTP, M3UA, SCTP, IP, and SIP. The SIP signalling function contains layers SIP, TCP/UDP/SCTP, and IP. Connections are: BICC between SS7 and MGCF; IP between SS7 and MGCF; SIP between MGCF and SIP SF; and IP between MGCF and SIP SF. + +**Figure 27: Control Plane interworking between CS networks supporting BICC over STC and M3UA and the IM CN subsystem** + +### 7.3.1 Services performed by network entities in the control plane + +Services offered by the network entities in the control plane are as detailed in clause 7.2.1. + +If ATM transport is applied between the SS7 Signalling function and the Signalling Gateway Function, they shall apply MTP3B (ITU-T Recommendation Q.2210 [46]) over SSCF (ITU-T Recommendation Q.2140 [45]) over SSCOP (ITU-T Recommendation Q.2110 [44]) over AAL5 (ITU-T Recommendation I.363.5 [43]) as depicted in figure 26. + +If IP transport is applied between the SS7 Signalling function and the MGCF, they shall support and apply M3UA, SCTP and IP (either IPv4, see RFC 791 [16], or IPv6, see RFC 2460 [39]), as depicted in figure 27. + +### 7.3.2 Signalling interactions between network entities in the control plane + +#### 7.3.2.1 Signalling between the SS7 signalling function and MGCF + +See clause 7.2.2.1. + +##### 7.3.2.1.1 Signalling from MGCF to SS7 signalling function + +See clause 7.2.2.1.1. + +##### 7.3.2.1.2 Signalling from SS7 signalling function to MGCF + +See clause 7.2.2.1.2. + +### 7.3.2.1.3 Services offered by STC, SCTP and M3UA + +See clause 7.2.2.1.3. + +#### 7.3.2.1.3.1 Services offer by SCTP + +See clause 7.2.2.1.3.1. + +#### 7.3.2.1.3.2 Services offered by M3UA + +See clause 7.2.2.1.3.2. + +#### 7.3.2.1.3.3 Services offered by STC + +STC provides the services for the transparent transfer of STC user information, e.g. BICC, between STC users, i.e. the SS7 signalling function and the MGCF (see 3GPP TS 29.205 [14]). + +STC performs the functions of data transfer service availability reporting and congestion reporting to the STC user and User part availability control. See ITU-T Recommendation Q.2150.1 [29]. + +### 7.3.2.2 Signalling between the MGCF and SIP signalling function + +See clause 7.2.2.2. + +## 7.3.3 SIP-BICC protocol interworking + +### 7.3.3.1 Incoming call interworking from SIP to BICC at I-MGCF + +#### 7.3.3.1.1 Sending of IAM + +Clause 7.2.3.1.1 is applicable with the clarification that the Continuity Check procedure applies. + +#### Figure 28: Void + +#### 7.3.3.1.2 Coding of IAM + +The description of the following ISDN user part parameters can be found in ITU-T Recommendation Q.763 [4]. + +##### 7.3.3.1.2.1 Called party number + +See clause 7.2.3.1.2.1. + +##### 7.3.3.1.2.2 Nature of connection indicators + +| | | | +|------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bits | BA | Satellite indicator | +| | 0 0 | no satellite circuit in the connection | +| bits | DC | Continuity indicator (BICC) | +| | 0 0 | no COT to be expected , if the received SDP does not contain precondition information or indicates that all preconditions are fulfilled, and all local resource reservation is completed. | +| | 1 0 | COT to be expected , if the received SDP indicates that precondition is not fulfilled or any local resource reservation is not completed. | +| Bit | E | Echo control device indicator | +| | 1 | outgoing echo control device included | + +##### 7.3.3.1.2.3 Forward call indicators + +See clause 7.2.3.1.2.3. + +7.3.3.1.2.4 Calling party's category + +See clause 7.2.3.1.2.4. + +7.3.3.1.2.4A Originating Line Information + +See clause 7.2.3.1.2.4A + +7.3.3.1.2.5 Transmission medium requirement + +See clause 7.2.3.1.2.5. + +7.3.3.1.2.6 Calling party number + +See clause 7.2.3.1.2.6. + +7.3.3.1.2.7 Generic number + +See clause 7.2.3.1.2.7. + +7.3.3.1.2.8 User service information + +See clause 7.2.3.1.2.8. + +7.3.3.1.2.9 Hop counter (National option) + +See clause 7.2.3.1.2.9. + +7.3.3.1.2.10 Location Number + +See clause 7.2.3.1.2.11. + +7.3.3.1.2.11 Support of ICS call + +See clause 7.2.3.1.2.12. + +7.3.3.1.2.12 UID capability indicators (National option) + +See clause 7.2.3.1.2.13. + +7.3.3.1.2A Coding of the IAM when Number Portability is supported + +See clause 7.2.3.1.2A. + +7.3.3.1.2B Coding of the IAM for Carrier Routeing + +See clause 7.2.3.1.2B. + +7.3.3.1.2.13 Called IN number and original called IN number (optional) + +See clause 7.2.3.1.2.14. + +7.3.3.1.3 Sending of COT + + + +The diagram illustrates the 'Sending of COT' process. It features a vertical line representing the I-MGCF. On the left, an arrow points towards this line, accompanied by a box containing the text 'SDP indicating preconditions met and/or active media'. On the right, an arrow points away from the I-MGCF line, accompanied by a box containing the text 'COT'. + +Sequence diagram showing the sending of COT from an I-MGCF. An arrow from the left points to a vertical line labeled I-MGCF, with a box above it containing 'SDP indicating preconditions met and/or active media'. From the I-MGCF line, another arrow points to the right with a box above it containing 'COT'. + +Figure 29: Sending of COT + +If the IAM has already been sent, then the Continuity message shall be sent indicating "continuity check successful", when all of the following conditions have been met. + +- When the requested remote preconditions (if any) in the IMS have been met. +- The media stream previously set to inactive mode is set to active (as specified in IETF RFC 4566 [56]). +- Local preconditions have been fulfilled. + +#### 7.3.3.1.3A Sending of SAM + +See clause 7.2.3.1.3A. + +#### 7.3.3.1.4 Sending of 180 Ringing + +See clause 7.2.3.1.4. + +#### 7.3.3.1.4A Sending of 183 Session Progress for early media scenarios + +See clause 7.2.3.1.4A. + +#### 7.3.3.1.4B Sending of 181 Call is being forwarded + +See clause 7.2.3.1.4B. + +#### 7.3.3.1.4C Sending of 183 Session Progress for overlap signalling using the in-dialog method + +See clause 7.2.3.1.4C. + +NOTE: If the network option of overlap signalling using the in-dialog method is applied at the I-MGCF in combination with the optional codec negotiation interworking with BICC in clause B.2., in order to meet the requirement in clause B.2.1 that the I-MGCF suspends the SDP answer procedure until it receives backward codec information from BICC, the 183 session progress response will not contain the SDP answer. + +#### 7.3.3.1.4D Sending of 183 Session Progress to carry ISUP Cause + +See clause 7.2.3.1.4D. + +#### 7.3.3.1.4E Sending of 183 Session Progress for ICS call + +See clause 7.2.3.1.4E. + +#### 7.3.3.1.5 Sending of the 200 OK (INVITE) + +See clause 7.2.3.1.5. + +#### 7.3.3.1.6 Sending of the Release message (REL) + +See clause 7.2.3.1.6. + +#### 7.3.3.1.7 Coding of the REL + +See clause 7.2.3.1.7. + +#### 7.3.3.1.8 Receipt of the Release Message + +See clause 7.2.3.1.8. + +#### 7.3.3.1.9 Receipt of RSC, GRS or CGB (H/W oriented) + +See clause 7.2.3.1.9. + +#### 7.3.3.1.9a Receipt of REFER + +See clause 7.2.3.1.9a. + +#### 7.3.3.1.9b Autonomous Release at I-MGCF + +See clause 7.2.3.1.10. + +#### 7.3.3.1.10 Internal through connection of the bearer path + +The through connection procedure is described in clauses 9.2.2.1.5 and 9.2.2.2.5. + +#### 7.3.3.1.11 Out of Band DTMF + +If a SIP UA sends DTMF tones to the IM-MGW, the IM-MGW may report this information via the Mn interface to the MGCF. The MGCF shall send to the BICC network the APM message with the following values for the different parameters: + +- Action indicator in accordance with the requested DTMF transport function; +- Signal in accordance with which DTMF digit to send; +- Duration in accordance with the required duration of the DTMF digit. + +If the BICC network sends an APM message with DTMF signal, duration and action indicator to the MGCF, the MGCF may send this information to the IM-MGW via the Mn interface. The IM-MGW shall send the corresponding DTMF signal and duration information on the user plane of the IM CN subsystem according to RFC 4733 [105]. + +The interactions with the IM-MGW are shown in clause 9.2.8. + +### 7.3.3.2 Outgoing Call Interworking from BICC to SIP at O-MGCF + +#### 7.3.3.2.1 Sending of INVITE + +The following particularities apply for a BICC IAM received case, with regard to the already specified in clause 7.2.3.2.1. + +The O-MGCF should defer sending the INVITE request until the BICC bearer setup and any local resource reservation is completed. + +- NOTE: If the O-MGCF sends the INVITE request before the BICC bearer setup and any local resource reservation is completed, the following considerations apply: If the receiving terminal is not supporting the SIP precondition, clipping may occur. Furthermore, if the MGCF sets the SDP "inactive" attribute in the initial INVITE request and the receiving terminal is not supporting the SIP precondition and the SIP UPDATE method, the interworking procedures within the present specification do not describe all necessary signalling interactions required to set up a call, in particular with respect to the sending of the re-INVITE that may also cause additional delay in the call setup. In addition, the interworking of the ringing indication might not be possible if the peer sends the ringing indication only as response to a re-INVITE. + +The BICC bearer setup is completed when one of the following conditions is met: + +- The event Bearer Set-up indication - for the forward bearer set-up case where the incoming Connect Type is "notification not required", which indicate successful completion of bearer set-up, is received by the Incoming bearer set-up procedure (ITU-T Recommendation Q.1902.4 [30] clause 7.5); +- Bearer Set-up Connect indication for the backward call set-up case, which indicate successful completion of bearer set-up, is received by the Incoming bearer set-up procedure (ITU-T Recommendation Q.1902.4 [30] clause 7.5); +- BNC set-up success indication for cases using bearer control tunnelling which indicate successful completion of bearer set-up, is received by the Incoming bearer set-up procedure (ITU-T Recommendation Q.1902.4 [30] clause 7.5). + +#### 7.3.3.2.1a Sending of INVITE without determining the end of address signalling + +See clause 7.2.3.2.1a. + +#### 7.3.3.2.2 Coding of the INVITE + +##### 7.3.3.2.2.1 Request-URI and To header field + +See clause 7.2.3.2.2.1 + +##### 7.3.3.2.2.2 SDP Media Description + +If the O-MGCF sends the INVITE request without waiting for the BICC bearer setup and any local resource reservation to complete, (which is not recommended according to clause 7.3.3.2.1) it shall indicate that SIP preconditions are not met when the initial INVITE request indicates support of the SIP preconditions. + +The O-MGCF shall include the AMR codec transported according to IETF RFC 4867 [23] with the options listed in clause 12.3.1 of 3GPP TS 26.114 [104] in the SDP offer. Within the SDP offer, the O-MGCF should also provide SDP RR and RS bandwidth modifiers specified in IETF RFC 3556 [59] as detailed in clause 7.3.1 of 3GPP TS 26.114 [104]. + +##### 7.3.3.2.2.3 P-Asserted-Identity and privacy header fields + +See clause 7.2.3.2.2.3 + +###### 7.3.3.2.2.3A "cpc" URI Parameter in P-Asserted-Identity Header + +See clause 7.2.3.2.2.3A. + +###### 7.3.3.2.2.3B "oli" URI Parameter in P-Asserted-Identity Header + +See clause 7.2.3.2.2.3B. + +##### 7.3.3.2.2.4 Max Forwards header + +See clause 7.2.3.2.2.4 + +##### 7.3.3.2.2.5 IMS Communication Service Identifier + +For speech and video calls, the O-MGCF shall insert an IMS Communication Service Identifier, indicating the IMS Multimedia Telephony Communication Service. + +The IMS Communication Service Identifier for the IMS Multimedia Telephony Communication Service is defined in 3GPP TS 24.173 [88]. + +##### 7.3.3.2.2.6 P-Access-Network-Info + +See clause 7.2.3.2.2.9. + +#### 7.3.3.2.2A Coding of the INVITE when number portability is supported + +See clause 7.2.3.2.2A. + +#### 7.3.3.2.2B Coding of the INVITE for Carrier Routeing + +See clause 7.2.3.2.2B. + +#### 7.3.3.2.2C Coding of INVITE with instance-id in form of IMEI URN + +See clause 7.2.3.2.2C. + +##### 7.3.3.2.2.7 PSAP Call-back indication + +See clause 7.2.3.2.2.10. + +#### 7.3.3.2.2.8 History-Info header field (optional) + +See clause 7.2.3.2.2.11. + +#### 7.3.3.2.3 Sending of UPDATE + +This clause only applies if the O-MGCF sends the INVITE request before SIP preconditions are met (see clause 7.3.3.2.1). + + + +The diagram illustrates a sequence of events for the O-MGCF. A horizontal arrow labeled "COT (success)" points to a vertical line representing the O-MGCF. From this vertical line, another horizontal arrow labeled "UPDATE" points to the right, indicating the sending of the UPDATE message. + +Sequence diagram showing the receipt of COT (success) and the subsequent sending of an UPDATE message by the O-MGCF. + +**Figure 30: Receipt of COT (success)** + +The UPDATE request with a new SDP offer shall be sent for each early SIP dialogue for which the received provisional response indicated support of preconditions confirming that all the required local preconditions have been met when all the following conditions are met. + +1. A Continuity message, with the Continuity Indicators parameter set to "continuity check successful" shall be received. +2. The reservation of requested local resources has been completed. + +In addition, depending on which bearer set-up procedure used for the call one of the following condition shall be met: + +- The event Bearer Set-up indication - for the forward bearer set-up case where the incoming Connect Type is "notification not required", which indicate successful completion of bearer set-up, is received by the Incoming bearer set-up procedure (ITU-T Recommendation Q.1902.4 [30] clause 7.5); +- Bearer Set-up Connect indication for the backward call set-up case, which indicate successful completion of bearer set-up, is received by the Incoming bearer set-up procedure (ITU-T Recommendation Q.1902.4 [30] clause 7.5); +- BNC set-up success indication for cases using bearer control tunnelling which indicate successful completion of bearer set-up, is received by the Incoming bearer set-up procedure, (ITU-T Recommendation Q.1902.4 [30] clause 7.5). + +NOTE: This procedure applies regardless of whether the early SIP dialog existed prior to the preconditions being fulfilled or is subsequently created. + +#### 7.3.3.2.4 Sending of ACM and Awaiting Answer indication + +See clause 7.2.3.2.4 + +The sending of an awaiting answer indication is described in clause 9.2.3.1. and clause 9.2.3.2. + +#### 7.3.3.2.5 Coding of the ACM + +##### 7.3.3.2.5.1 Backward call indicators + +See clause 7.2.3.2.5.1 + +#### 7.3.3.2.6 Sending of the Call Progress message (CPG) + +See clause 7.2.3.2.6. + +### 7.3.3.2.7 Coding of the CPG + +#### 7.3.3.2.7.1 Event information + +See clause 7.2.3.2.7.1. + +#### 7.3.3.2.7.2 Optional Backward call indicators + +See clause 7.2.3.2.7.5. + +#### 7.3.3.2.7a Receipt of 200 OK (INVITE) + +See clause 7.2.3.2.7a. + +#### 7.3.3.2.7b Internal through connection of the bearer path + +The through connection procedure is described in clauses 9.2.3.1.7 and 9.2.3.2.7. + +### 7.3.3.2.8 Sending of the Answer Message (ANM) + +See clause 7.2.3.2.8. + +### 7.3.3.2.9 Coding of the ANM + +See clause 7.2.3.2.9. + +### 7.3.3.2.10 Sending of the Connect message (CON) + +See clause 7.2.3.2.10. + +### 7.3.3.2.11 Coding of the CON + +See clause 7.2.3.2.11. + +#### 7.3.3.2.11.1 Void + +#### 7.3.3.2.11A Receipt of re-INVITE requests + +See clause 7.2.3.2.11A. + +### 7.3.3.2.12 Receipt of Status Codes 4xx, 5xx or 6xx + +See clause 7.2.3.2.12. + +### 7.3.3.2.13 Receipt of a BYE + +See clause 7.2.3.2.13. + +### 7.3.3.2.14 Receipt of the Release Message + +See clause 7.2.3.2.14. + +### 7.3.3.2.15 Receipt of RSC, GRS or CGB (H/W oriented) + +See clause 7.2.3.2.15. + +### 7.3.3.2.16 Out of Band DTMF + +If a SIP UA sends DTMF tones to the IM-MGW, the IM-MGW may report this information via the Mn interface to the MGCF. The MGCF shall send to the BICC network the APM message with the following values for the different parameters: + +- Action indicator in accordance with the requested DTMF transport function; +- Signal in accordance with which DTMF digit to send; + +- Duration in accordance with the required duration of the DTMF digit. + +If the BICC network sends an APM message with DTMF signal, duration and action indicator to the MGCF, the MGCF may send this information to the IM-MGW via the Mn interface. The IM-MGW shall send the corresponding DTMF signal and duration information on the user plane of the IM CN subsystem according to 4733 [105]. + +The interaction with the IM-MGW is shown in clause 9.2.8. + +#### 7.3.3.2.17 Sending of CANCEL + +See clause 7.2.3.2.18. + +#### 7.3.3.2.18 Autonomous Release at O-MGCF + +See clause 7.2.3.2.16. + +#### 7.3.3.2.19 Special handling of 580 precondition failure received in response to either an INVITE or UPDATE + +See clause 7.2.3.2.17. + +#### 7.3.3.2.20 Receipt of SIP redirect (3xx) response + +See clause 7.2.3.2.19. + +#### 7.3.3.2.21 Sending of INFO for overlap signalling using the in-dialog method + +See clause 7.2.3.2.20. + +### 7.3.3.3 Timers + +See clause 7.2.3.3. + +## 7.4 Supplementary Services + +The following clauses describe the MGCF behaviour related to supplementary services as defined in ITU-T Recommendations Q.730 to ITU-T Q.737 [42] when interworking with an IMS which does not use a Multimedia Telephony Application Server (MTAS) providing supplementary services according to 3GPP according to 3GPP TS 24.173 [88]. The support of these supplementary services is optional. If the supplementary services are supported, the procedures described within this clause shall be applied. + +### 7.4.1 Calling line identification presentation/restriction (CLIP/CLIR) + +The inter working between the Calling Party Number parameter and the P-Asserted-ID header and vice versa used for the CLIP-CLIR service is defined in the clauses 7.2.3.1.2.6 and 7.2.3.2.2.3. This inter working is essentially the same as for basic call and differs only in that if the CLIR service is invoked the "Address Presentation Restriction Indicator (APRI)" (in the case of ISUP to SIP calls) or the "priv value" of the "calling" Privacy header field (in the case of SIP to ISUP calls) is set to the appropriate "restriction/privacy" value. + +In the specific case of ISUP originated calls, use of the CLIP service additionally requires the ability to determine whether the number was network provided or provided by the access signalling system. Due to the possible SIP indication of the P-Asserted-Identity the Screening indicator is set to network provided as default. For the CLIP-CLIR service the mapping of the APRI from privacy header at the O-MGCF is described within table 16 in clause 7.2.3.2.2.3. + +At the O-MGCF the presentation restricted indication shall be mapped to the Privacy header field values "id" and "header". This is described in table 12 in clause 7.2.3.2.2.3. + +## 7.4.2 Connected line presentation and restriction (COLP/COLR) + +### 7.4.2.0 General + +The COLP/COLR services are only to be interworked between trusted nodes - that is before passing any COLP/COLR information over the SIP-BICC/ISUP boundary the MGCF shall satisfy itself that the nodes on the BICC/ISUP side to which the information is to be passed are trusted. + +The procedure within clause 7.5.2 for the generic number ("additional connected number") mapping shall apply. + +### 7.4.2.1 Incoming Call Interworking from SIP to BICC/ISUP at the I-MGCF + +#### 7.4.2.1.1 INVITE to IAM interworking (SIP to ISUP/BICC calls) + +In the case of SIP to ISUP/BICC calls the I-MGCF may invoke the COLP service as an operator option by setting the "Connected Line Identity Request indicator" field of the "Optional forward call indicators" parameter of the IAM to "requested". + +NOTE: This implies that all outgoing calls will invoke the COLP service. + +#### 7.4.2.1.2 ANM/CON to 200 OK (INVITE) + +Tables 20 and 21 specify the interworking required in the case when the COLP has been automatically requested on behalf of the originating SIP node. The table also indicates the inter workings required if the COLP service has been invoked and the called party has or has not invoked the COLR service. + +**Table 20: Mapping to P-Asserted-Identity and Privacy Header Fields** + +| SIP Component | Setting | +|---------------------|--------------| +| P-Asserted-Identity | See table 21 | +| Privacy | See table 22 | + +**Table 21: Mapping of connected number parameter to SIP P-Asserted-Identity header fields** + +| BICC/ISUP parameter / field | Value | SIP component | Value | +|----------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| +| Connected Number | | P-Asserted-Identity header field | | +| Nature of Address Indicator | " national (significant) number " | Tel URI or SIP URI (NOTE 1) | Add CC (of the country where the MGCF is located) to Connected PN address signals to construct E.164 number in URI. Prefix number with "+". | +| | " international number " | | Map complete Connected address signals to construct E.164 number in URI. Prefix number with "+". | +| Address signal | If NOA is " national (significant) number " then the format of the address signals is:
NDC + SN
If NOA is " international number " then the format of the address signals is:
CC + NDC + SN | Tel URI or SIP URI (NOTE 1) | CC+NDC+SN as E.164 number in URI. Prefix number with "+". | +| NOTE 1: A tel URI or a SIP URI with "user=phone" is used according to operator policy. | | | | + +**Table 22: Mapping of BICC/ISUP APRIs into SIP privacy header fields** + +| BICC/ISUP parameter / field | Value | SIP component | Value | +|---------------------------------------------------------------|----------------------------------|----------------------|----------------------------------------------------------------------------------------------------| +| Connected Number | | Privacy header field | priv-value | +| APRI
(See to determine which APRI to use for this mapping) | "presentation restricted" | Priv-value | "id"
("id" included only if the P-Asserted-Identity header is included in the SIP INVITE) | +| | "presentation allowed" | Priv-value | omit Privacy header or Privacy header without "id" and "header" if other privacy service is needed | + +## 7.4.2.2 Outgoing Call Interworking from BICC/ISUP to SIP at O-MGCF + +### 7.4.2.2.1 IAM to INVITE interworking (ISUP to SIP calls) + +The O-MGCF determines that the COLP service has been requested by the calling party by parsing the "Optional Forward Call Indicators" field of the incoming IAM. If the "Connected Line Identity Request indicator" is set to "requested" then the BICC/ISUP to SIP interworking node shall ensure that any backwards "connected party" information is interworked to the appropriate parameters of the ISUP ANM or CON message sent backwards to the calling party as detailed within this subclause. + +The O-MGCF has to store the status of the "Connected Line Identity Request indicator". + +### 7.4.2.2.2 1XX to ANM or CON interworking + +If the P-Asserted-Identity header field is included within a 1XX SIP response, the identity shall be stored within the O-MGCF together with information about the SIP dialogue of the 1XX SIP response and shall be included within the ANM or CON message if required by the procedures described in clause 7.4.2.2.3. In accordance with ISUP procedures, a connected number shall not be included within the ACM message. The mapping of the of the P-Asserted-Identity and Privacy header fields is shown in tables 23 and 24. + +### 7.4.2.2.3 200 OK (INVITE) to ANM/CON interworking + +Tables 23 and 24 specify the interworking required in the case when the calling party has invoked the COLP service. The tables also indicate the interworking procedures required if the calling party has invoked the COLP service and the called party has or has not invoked the COLR service. + +If no P-Asserted-Identity header field is provided within the 200 OK (INVITE) message, the stored information previously received in the last provisional 1xx response of the same SIP dialogue shall be used. + +NOTE: Due to forking, other P-Asserted-Identities might have been received in different SIP dialogues. + +If the Calling Party has requested the COLP service (as indicated by the stored request status) but the 200 OK (INVITE) and previous 1XX provisional responses do not include a P-Asserted-Identity header field, the O-MGCF shall set up a network provided Connected Number with an Address not Available indication. + +If the P-Asserted-Identity is available then the Connected number has to be setup with the screening indication network provided. The mapping of the P-Asserted-Identity and Privacy (if available) is shown in table 24. + +**Table 23: Connected number parameter mapping** + +| ANM/CON | 200 OK INVITE | +|-------------------------------------------|----------------------| +| Connected Number (Network Provided) | P-Asserted-ID | +| Address Presentation Restricted Indicator | Privacy Value Field | + +**Table 24: Mapping of P-Asserted-Identity and privacy headers to the ISUP/BICC connected number parameter** + +| SIP component | Value | BICC/ISUP parameter / field | Value | +|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| P-Asserted-Identity header field (NOTE) | E.164 number | Connected Number | | +| | | Number incomplete indicator | "Complete" | +| | | Numbering Plan Indicator | "ISDN/Telephony (E.164)" | +| | | Nature of Address Indicator | If CC encoded in the URI is equal to the CC of the country where MGCF is located AND the next BICC/ISUP node is located in the same country then set to "national (significant) number" else set to "international number" | +| | | Address Presentation Restricted Indicator (APRI) | Depends on priv-value in Privacy header. | +| | | Screening indicator | Network Provided | +| Addr-spec | "CC" "NDC" "SN" from the URI | Address signal | if NOA is "national (significant) number" then set to "NDC" + "SN".
If NOA is "international number" then set to "CC"+"NDC"+"SN". | +| Privacy header field is not present | | APRI | Presentation allowed | +| Privacy header field | priv-value | APRI | "Address Presentation Restricted Indicator" | +| priv-value | "header" | APRI | Presentation restricted | +| | "user" | APRI | Presentation restricted | +| | "none" | APRI | Presentation allowed | +| | "id" | APRI | Presentation restricted | +| NOTE: | It is possible that a P-Asserted-Identity header field includes both a tel URI and a SIP URI. In this case, either the tel URI or the SIP URI with user="phone" and a specific host portion, as selected by operator policy, may be used. | | | + +### 7.4.3 Direct Dialling In (DDI) + +A direct dialling in call is a basic call and no additional treatment is required by the MGCF. + +### 7.4.4 Malicious call identification + +The actions of the MGCF at the ISUP/BICC side are described in ITU-T Recommendation Q.731.7 [42] under the clause "Interactions with other networks". + +### 7.4.5 Subaddressing (SUB) + +#### 7.4.5.1 General + +The ISDN subaddress information in ISUP is transported within the Access Transport Parameter. The coding of the subaddress parameter within the Access Transport Parameter is described within ETSI EN 300 403-1 [96]. The isdn-subaddress parameter "isub" carried within a tel or SIP URI is defined within IETF RFC 3966 [97]. The isdn-subaddress encoding type parameter "isub-encoding" carried within a tel or SIP URI is defined within IETF RFC 4715 [108] and extended within 3GPP TS 24.229 [9]. + +#### 7.4.5.2 Interworking at I-MGCF + +The mapping in table 24ba of the isdn-subaddress parameter received within a tel or SIP URI of the initial INVITE request to the ISUP Access Transport Parameter encapsulating the subaddress information (calling party subaddress and/or called party subaddress information elements) to be sent within the IAM message shall be applied. + +The mapping in table 24bb of the subaddress information (connected subaddress information element) received within an ANM message or a CON message containing the ISUP Access Transport Parameter to the isdn-subaddress parameters "isub" and "isub-encoding" of a tel or SIP URI to be sent within a 200 OK (INVITE) shall be applied. + +**Table 24ba: Mapping of the isdn-subaddress received in an initial INVITE to the subaddress information sent in the IAM** + +| SIP Message INVITE | | | ISUP Message IAM | | | +|----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|----------------------------|----------------------------------|------------------------------------------------------| +| Source SIP header field and component | Source component value | | ISUP Parameter field | Derived value of parameter field | | +| To header field including the isdn-subaddress (NOTE 1) | "isub=" 1*uric
"uric" containing the subaddress digits | isub-encoding not present | Access Transport Parameter | called party subaddress | Type of subaddress = "NSAP" (000) | +| | | "isub-encoding=nsap-ia5" | | | Type of subaddress = "NSAP" (000) | +| | | "isub-encoding=nsap-bcd" | | | Type of subaddress = "NSAP" (000) | +| | | "isub-encoding=nsap" | | | Type of subaddress = "user specified" (010) (NOTE 2) | +| | "isub=" 1*uric ("uric" containing the subaddress digits) and isub-encoding does not contain "nsap-ia5" or "nsap-bcd" or "nsap" or "user-specified" value (NOTE 2) | | No mapping | | | +| P-Asserted-Identity header Field including the isdn-subaddress | ";isub=" 1*uric
"uric" containing the subaddress digits | isub-encoding not present | Access Transport Parameter | calling party subaddress | Type of subaddress = "NSAP" (000) | +| | | "isub-encoding=nsap-ia5" | | | Type of subaddress = "NSAP" (000) | +| | | "isub-encoding=nsap-bcd" | | | Type of subaddress = "NSAP" (000) | +| | | "isub-encoding=nsap" | | | Type of subaddress = "user specified" (010) (NOTE 2) | +| | "isub=" 1*uric ("uric" containing the subaddress digits) and isub-encoding does not contain "nsap-ia5" or "nsap-bcd" or "nsap" or "user-specified" value (NOTE 2) | | No mapping | | | + +NOTE 1: As an operator option, an isdn-subaddress within the Request-URI may also be mapped into the ISUP Access Transport parameter. +NOTE 2: The interworking between "user-specified" encoding-type parameter and "user-specified" type of subaddress is an operator option. + +**Table 24bb: Mapping of the subaddress information received in an ANM or CON to the isdn subaddress sent in the 200 OK (INVITE)** + +| ISUP Message ANM or CON | | SIP Message 200 (OK) | | +|----------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|---------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ISUP Parameter field | Source component value | Source SIP header field and component | Derived value of parameter field | +| Access Transport Parameter | connected subaddress and Type of subaddress = "NSAP" (000) | P-Asserted-Identity including the isdn-subaddress | ";isub=" 1*uric and "isub-encoding=nsap-ia5"
The subaddress digits included into the "uric" shall be derived from the Access Transport Parameter. | +| | connected subaddress and Type of subaddress = "user specified" (010) (NOTE) | | ";isub=" 1*uric and "isub-encoding=user-specified"
The subaddress digits included into the "uric" shall be derived from the Access Transport Parameter. (NOTE) | +| | connected subaddress and Type of subaddress ≠ "NSAP" (000) or "user specified" (010) (NOTE) | No mapping | | +| NOTE: The interworking between "user-specified" encoding-type parameter and "user-specified" type of subaddress is an operator option. | | | | + +### 7.4.5.3 Interworking at O-MGCF + +The mapping in table 24bc of the subaddress information received in the Access Transport Parameter (calling party subaddress and/or called party subaddress information elements) of the IAM message to the isdn-subaddress parameters "isub" and "isub-encoding" of a tel or SIP URI to be sent within the initial INVITE request shall be applied. + +The mapping in table 24bd of the isdn-subaddress information received within a tel or SIP URI of a 200 OK (INVITE) to the subaddress information of the ISUP Access Transport Parameter (connected subaddress information element) to be sent within the ANM or CON message shall be applied. + +**Table 24bc: Mapping of the subaddress information received in an IAM to the isdn-subaddress sent in the INVITE** + +| ISUP IAM Message | | SIP INVITE Message | | +|----------------------------|-------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ISUP Parameter field | Source component value | Source SIP header field and component | Derived value of parameter field | +| Access Transport Parameter | called party subaddress and Type of subaddress = "NSAP" (000) | To header field including the isdn-subaddress, and, as an operator option, Request URI | ";isub=" 1*uric and "isub-encoding=nsap-ia5"
The subaddress digits included into the "uric" shall be derived from the Access Transport Parameter. | +| | called party subaddress and Type of subaddress = "user specified" (010) (NOTE) | | ";isub=" 1*uric and "isub-encoding=user-specified"
The subaddress digits included into the "uric" shall be derived from the Access Transport Parameter. (NOTE) | +| | called party subaddress and Type of subaddress ≠ "NSAP" (000) OR "user specified" (010) (NOTE) | No mapping | | +| | calling party subaddress and Type of subaddress = "NSAP" (000) | P-Asserted-Identity header field including the isdn-subaddress | ";isub=" 1*uric and "isub-encoding=nsap-ia5"
The subaddress digits included into the "uric" shall be derived from the Access Transport Parameter. | +| | calling party subaddress and Type of subaddress = "user specified" (010) (NOTE) | | ";isub=" 1*uric and "isub-encoding=user-specified"
The subaddress digits included into the "uric" shall be derived from the Access Transport Parameter. (NOTE) | +| | calling party Subaddress and Type of Subaddress ≠ "NSAP" (000) or "user specified" (010) (NOTE) | No mapping | | + +NOTE: The interworking between "user-specified" encoding-type parameter and "user-specified" type of subaddress is an operator option. + +**Table 24bd: Mapping of the isdn subaddress received in a 200OK to the subaddress information sent in the ANM or CON** + +| SIP Message 200 (OK) | | | ISUP Message ANM or CON | | | +|----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|----------------------------|----------------------------------|----------------------------------------------------| +| Source SIP header field and component | Source component value | | ISUP Parameter field | Derived value of parameter field | | +| P-Asserted-Identity header Field including the isdn-subaddress | "isub=" 1*uric
"uric" containing the subaddress digits | isub-encoding not present | Access Transport Parameter | connected subaddress | Type of subaddress = "NSAP" (000) | +| | | "isub-encoding=nsap-ia5" | | | Type of subaddress = "NSAP" (000) | +| | | "isub-encoding=nsap-bcd" | | | Type of subaddress = "NSAP" (000) | +| | | "isub-encoding=nsap" | | | Type of subaddress = "user-specified" (010) (NOTE) | +| | "isub=" 1*uric ("uric" containing the subaddress digits) and isub-encoding does not contain "nsap-ia5" or "nsap-bcd" or "nsap" or "user-specified" value (NOTE) | | No mapping | | | + +NOTE: The interworking between "user-specified" encoding-type parameter and "user-specified" type of subaddress is an operator option. + +## 7.4.6 Call Forwarding Busy (CFB)/ Call Forwarding No Reply (CFNR) / Call Forwarding Unconditional (CFU) / Call Deflection (CD) + +### 7.4.6.1 General + +A MGCF within an IMS network applying the Communication Diversion service uses the procedures defined in clause 7.5.4. + +This clause describes additional interworking of call forwarding service information between a PSTN/PLMN network and an IMS network. This can also be used when interworking between SIP networks (e.g., IMS network interworking with enterprise networks making use of the History-Info header field with an escaped Reason header field as described in IETF RFC 7044 [91]). The procedures support the interworking of the diversion reason within the History-Info header field using an escaped Reason header field defined by IETF RFC 3326 [116] as described in IETF RFC 7044 [91] and also support the diversion cause using the "cause" URI parameter as described by IETF RFC 4458 [113]. + +If the MGCF is supporting the interworking of Call Forwarding and also applying the Communication Diversion services as defined by 3GPP TS 24.604 [60], it uses both IETF RFC 7044 [91] and IETF RFC 4458 [113] to signal the diversion reason. An IMS network supporting the interworking of Call Forwarding and not applying the IMS Communication Diversion supplementary service according to 3GPP TS 24.604 [60] uses IETF RFC 7044 [91] and can also use IETF RFC 4458 [113] based on network option. + +When interworking the SIP History-Info header field to ISUP, and both the diversion reason based on IETF RFC 7044 [91] and IETF RFC 4458 [113] are present for the same diversion instance, the MGCF should use the "cause" URI parameter per IETF RFC 4458 [113] for deriving the ISUP. When the "cause" URI parameter per IETF RFC 4458 [113] is used, the corresponding interworking as described in clause 7.5.4 shall be applied for that diversion instance. Otherwise, the interworking as defined in the present clause should be applied. + +When interworking from ISUP to the History-Info header field, to signal the diversion reason the MGCF should use the escaped Reason header field from IETF RFC 7044 [91] and apply the interworking procedures in the present subclause. The MGCF should also apply the interworking procedures described in clause 7.5.4 to use the "cause" URI parameter from IETF RFC 4458 [113] to signal the diversion reason. + +In the event that the interworking procedures described in this clause as well as the interworking procedures in clause 7.5.4 are not applied, the actions of the MGCF at the ISUP/BICC side as described in ITU-T Recommendation Q.732.2-5 [42] under the clause "Interactions with networks not providing any call diversion information" may be applied as a network option. + +## 7.4.6.2 Interworking at the O-MGCF + +### 7.4.6.2.1 General + +This clause describes the optional mapping of Call Forwarding information at the O-MGCF to the protocol-cause specified in IETF RFC 3326 [116]. + +### 7.4.6.2.2 Interworking SIP to ISUP + +**Table 7.4.6.2.2.1: Mapping of SIP messages to ISUP messages** + +| ←Message sent to ISUP | ←Message Received from SIP | | +|-------------------------------------------|----------------------------------------------------------------------------------------------------------------|------------------------| +| ACM indicating call forwarding | 181 (Call Is Being Forwarded) response | See table 7.4.6.2.2.6 | +| CPG indicating call forwarding (see NOTE) | 181 (Call Is Being Forwarded) response | See table 7.4.6.2.2.7 | +| ACM indicating ringing | 180 (Ringing) response | See table 7.4.6.2.2.8 | +| CPG indicating alerting (see NOTE) | 180 (Ringing) response | See table 7.4.6.2.2.9 | +| ANM | 200 (OK) response | See table 7.4.6.2.2.10 | +| CON | 200 (OK) response (Neither a 181 (Call Is Being Forwarded) response nor a 180 (Ringing) response was received) | See table 7.4.6.2.2.10 | + +NOTE: A CPG will be sent if an ACM was already sent. + +**Table 7.4.6.2.2.2: Mapping of History-Info header field to ISUP Redirection number** + +| Source SIP header field and component | Source Component value | Redirection number | Derived value of parameter field | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| hi-targeted-to-uri of the hi-entry following the last hi-entry containing a Reason "headers" component as defined in IETF RFC 7044 [91] with cause value as listed in table 7.4.6.2.2.4. Appropriate global number portion of the hi-targeted-to-uri, assumed to be in form "+" CC + NDC + SN. (NOTE) | CC | Nature of address indicator | If CC is equal to the country code of the country where O-MGCF is located AND the next ISUP node is located in the same country, then set to " national (significant) number " else set to " international number ". | +| | CC, NDC, SN | Address signals | If NOA is " national (significant) number " then set to NDC + SN.
If NOA is " international number " then set to CC + NDC + SN. | +| NOTE: If the SIP URI doesn't contain " user=phone ", mapping to redirection number is impossible, therefore no need to generate Redirection number and Redirection number restriction parameter (per table 7.4.6.2.2.3), Notification subscription options can't be set as " presentation allowed with redirection number ". | | | | + +**Table 7.4.6.2.2.3: Mapping of History-Info header field to ISUP Redirection number restriction** + +| Source SIP header field and component | Source Component value | Redirection number restriction | Derived value of parameter field | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|-----------------------------------|-------------------------------------------| +| Privacy header field, or/and Privacy "headers" component of the hi-entry following the last hi-entry containing a Reason "headers" component as defined in IETF RFC 7044 [91] with cause value as listed in table 7.4.6.2.2.4 | " history " or " session " or " header " | Presentation restricted indicator | " Presentation restricted " | +| | Privacy "headers" component of the hi-targeted-to-uri and Privacy header field absent or " none " | | " Presentation allowed " or absent | + +**Table 7.4.6.2.2.4: Mapping of hi-targeted-to-uri to ISUP Call Diversion Information** + +| Source SIP header field and component | Source Component value | Call Diversion Information | Derived value of parameter field | +|------------------------------------------------------------------------------------------------------|------------------------------|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | | Notification subscription options |
If the priv-value "history" or "session" or "header" is received within the Privacy header field or the priv-value "history" is received within the "headers" component of the hi-targeted-to-uri representing the diverting URI(s) and within the hi-targeted-to-uri representing diverted-to URI then "presentation not allowed" shall be set.
Otherwise, if the priv-value "history" is received only within the "headers" component of the hi-targeted-to-uri representing the diverted-to URI then "presentation allowed without redirection number" shall be set. (NOTE 1, NOTE 2)
Otherwise, "presentation allowed with redirection number" shall be set.
| +| hi-targeted-to-uri; Reason "headers" component as defined in IETF RFC 7044 [91] with cause parameter | Cause parameter value | Redirecting reason | | +| | 302 | | Deflection immediate response | +| | 486 | | User busy | +| | 408 | | No reply | +| | 503 | | Mobile subscriber not reachable | +| | all other cause values | | Unknown | + +NOTE 1: diverting URI corresponds to the hi-targeted-to-uri of the hi-entry containing a hi-index value that match the "mp" header field parameter value of the diverted-to URI. If the diverted-to URI does not contain the "mp" header field parameter, the diverting URI corresponds to the hi-targeted-to-uri of the last hi-entry containing a Reason "headers" component with cause parameter. + +NOTE 2: diverted-to URI corresponds to the hi-targeted-to-uri of the hi-entry following the last hi-entry containing a Reason "headers" component with cause parameter and is mapped to the Redirection number, see table 7.4.6.2.2.2. + +Table 7.4.6.2.2.5: Void + +Table 7.4.6.2.2.6: Mapping of 181 (Call Is Being Forwarded) © ACM when ACM was not previously sent + +| Source SIP header field and component | Source Component value | ISUP Parameter | Derived value of parameter field | +|------------------------------------------------------------------------------------------------------|------------------------|------------------------------------------------------------------------|----------------------------------| +| 181 (Call Is Being Forwarded) | | ACM | | +| | | Generic notification indicatorNotification indicator | Call is diverting | +| History-Info header field | See table 7.4.6.2.2.2 | Redirection number | See table 7.4.6.2.2.2 | +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | See table 7.4.6.2.2.3 | Redirection number restriction | See table 7.4.6.2.2.3 | +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | See table 7.4.6.2.2.4 | Call diversion information
Notification subscription options | See table 7.4.6.2.2.4 | +| hi-targeted-to-uri; Reason "headers" component as defined in IETF RFC 7044 [91] with cause parameter | See table 7.4.6.2.2.4 | Call diversion information
Redirecting reason | See table 7.4.6.2.2.4 | + +Table 7.4.6.2.2.7: Mapping of 181 (Call Is Being Forwarded) © CPG if ACM was already sent + +| Source SIP header field and component | Source Component value | ISUP Parameter | Derived value of parameter field | +|------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------|----------------------------------| +| 181 (Call Is Being Forwarded) response | | CPG | | +| | | Generic notification indicator
Notification indicator | Call is diverting | +| hi-targeted-to-uri; Reason "headers" component as defined in IETF RFC 7044 [91] with cause parameter | 486 | Event information | CFB (national use) | +| | 408 (see NOTE) | Event indicator | CFNR (national use) | +| | all other values, or if appropriate "national use" value (CFB, CFNR or CFU) is not used in a network, or if no hi-targeted-to-uri "cause" URI parameter is contained in the SIP 181 (Call Is Being Forwarded) response. | | Progress | +| History-Info header field | See table 7.4.6.2.2.2 | Redirection number | See table 7.4.6.2.2.2 | +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | See table 7.4.6.2.2.3 | Redirection number restriction | See table 7.4.6.2.2.3 | +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | See table 7.4.6.2.2.4 | Call diversion information
Notification subscription options | See table 7.4.6.2.2.4 | +| hi-targeted-to-uri; Reason "headers" component as defined in IETF RFC 7044 [91] with cause parameter | See table 7.4.6.2.2.4 | Call diversion information
Redirecting reason | See table 7.4.6.2.2.4 | +| NOTE: This appears in the cases of CFNR. | | | | + +**Table 7.4.6.2.2.8: Mapping of 180 (Ringing) $\Leftarrow$ ACM when ACM was not previously sent** + +| Source SIP header field and component | Source Component value | ISUP Parameter | Derived value of parameter field | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------| +| 180 (Ringing) response | | ACM | | +| History-Info header field | If hi-targeted-to-uri of at least one History-Info hi-entry contains a Reason "headers" component as defined in IETF RFC 7044 [91]. | Generic notification indicator
Notification indicator | Call is diverting | +| History-Info header field | See table 7.4.6.2.2.2 | Redirection number (NOTE) | See table 7.4.6.2.2.2 | +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | See table 7.4.6.2.2.3 | Redirection number restriction (NOTE) | See table 7.4.6.2.2.3 | +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | See table 7.4.6.2.2.4 | Call diversion information
Notification subscription options (NOTE) | See table 7.4.6.2.2.4 | +| hi-targeted-to-uri; Reason "headers" component as defined in IETF RFC 7044 [91] with cause parameter | See table 7.4.6.2.2.4 | Call diversion information
Redirecting reason (NOTE) | See table 7.4.6.2.2.4 | +| NOTE: Parameter shall only be supplied if hi-targeted-to-uri contains a Reason "headers" component, as defined in IETF RFC 7044 [91] with cause value as listed in table 7.4.6.2.2.4. | | | | + +The mapping described within table 7.4.6.2.2.8 can only appear if the communication has already undergone a Communications diversion in the IMS and the 180 (Ringing) is the first provisional response sent in backward direction. + +The O-MGCF can indicate the call diversion information in the mapping of 180 (Ringing) provisional response to a CPG message in fact if the response before was a 181 (Call Is Being Forwarded). + +**Table 7.4.6.2.2.9: Mapping of 180 (Ringing) $\Leftarrow$ CPG if ACM was already sent** + +| Source SIP header field and component | Source Component value | ISUP Parameter | Derived value of parameter field | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-------------------------------------------------------------------------------|----------------------------------| +| 180 (Ringing) response | | CPG | | +| | | Generic notification indicator
Notification indicator | Call is diverting | +| History-Info header field | | Event information
Event indicator | ALERTING | +| History-Info header field | See table 7.4.6.2.2.2 | Redirection number (NOTE) | See table 7.4.6.2.2.2 | +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | See table 7.4.6.2.2.3 | Redirection number restriction (NOTE) | See table 7.4.6.2.2.3 | +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | See table 7.4.6.2.2.4 | Call diversion information
Notification subscription options (NOTE) | See table 7.4.6.2.2.4 | +| hi-targeted-to-uri; Reason "headers" component as defined in IETF RFC 7044 [91] with cause parameter | See table 7.4.6.2.2.4 | Call diversion information
Redirecting reason (NOTE) | See table 7.4.6.2.2.4 | +| NOTE: Parameter shall only be supplied if hi-targeted-to-uri contains a Reason "headers" component, as defined in IETF RFC 7044 [91] with cause value as listed in table 7.4.6.2.2.4. | | | | + +The mapping in table 7.4.6.2.2.9 appears when a 181 (Call Is Being Forwarded) provisional response previously was mapped to an ACM. Therefore the state machine of the O-MGCF knows that a CDIV is in progress. + +**Table 7.4.6.2.2.10: Mapping of 200 (OK) response** + +| Source SIP header field and component | Source Component value | ISUP Parameter | Derived value of parameter field | +|-----------------------------------------------------------------------------------------------|------------------------|--------------------------------|----------------------------------| +| 200 (OK) response | | ANM/CON (NOTE) | | +| History-Info header field | See table 7.4.6.2.2.2 | Redirection number | See table 7.4.6.2.2.2 | +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | See table 7.4.6.2.2.3 | Redirection number restriction | See table 7.4.6.2.2.3 | +| NOTE:Redirection number shall only be supplied if 200 (OK) response is mapped to ANM message. | | | | + +### 7.4.6.2.3 Interworking ISUP to SIP + +For the interworking of 180 (Ringing) response and 200 (OK) response (to the INVITE request) to the regarding ISUP messages and parameters no additional procedures beyond the basic call procedures are needed. + +To interwork the redirecting number at the O-MGCF it can be needed to create placeholder History-Info hi-entries. Such a History-Info hi-entry shall contain a hi-targeted-to-uri set to an "Unknown User Identity" (value "sip:unknown@unknown.invalid" as defined in 3GPP TS 23.003 [74]), a Reason "headers" component with a cause parameter, a hi-index and an "mp" header field parameter as described within table 7.4.6.2.3.1. + +**Table 7.4.6.2.3.1: Mapping of IAM to SIP INVITE request** + +| ISUP Parameter or IE | Derived value of parameter field | SIP component | Value | +|------------------------------|------------------------------------------|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IAM | | INVITE request | | +| Redirecting number | | History-Info header field | IF Redirection counter exceeds 1
hi-targeted-to-uri of the penultimate created hi-entry (NOTE 9)
IF Redirecting number is available
set to the value of the Redirecting number
ELSE
set to the Unknown User Identity (NOTE 10)
ELSE
no mapping (NOTE 8) | +| Nature of address indicator: | " national (significant) number " | hi-targeted-to-uri | Add CC (of the country where the MGCF is located) to Redirecting number Address Signals to construct E.164 number in URI. | +| | " international number " | | Map complete Redirecting number Address Signals to E.164 number in URI. | + +| ISUP Parameter or IE | Derived value of parameter field | SIP component | Value | +|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Address Signals | If NOA is " national (significant) number " then the format of the Address Signals is:
NDC + SN
If NOA is " international number " then the format of the Address Signals is:
CC + NDC + SN | hi-targeted-to-uri | Addr-spec
"+" CC NDC SN mapped to userinfo portion of SIP URI.
(NOTE 5)
Add "user=phone". | +| Redirecting number | APRI | Privacy "headers" component of the penultimate hi-targeted-to-uri entry in the History-Info header | Priv-value | +| | " presentation restricted " | | " history " | +| | " presentation allowed " | | Privacy header field absent or " none " (NOTE 3) | +| Redirection Information | Redirecting indicator | Privacy "headers" component of the penultimate hi-targeted-to-uri entry in the History-Info header | Priv-value | +| | Call diverted | | Privacy header field absent or " none " (NOTE 4) | +| | Call diverted, all redirection information presentation restricted | | " history " | +| Redirection Information | Redirection counter
1 | hi-index and "mp" header field parameter (NOTE 7) | Number of diversions is shown to the number of levels in hi-index.
Index for Original called number = 1
Index for Called party number = 1.1 and addition of "mp=1" | +| | 2 | | Index for Original called number = 1
Index for Redirecting number = 1.1 and addition of "mp=1"
Index for Called party number = 1.1.1 and addition of "mp=1.1" | +| | N | | Index for Original called number = 1
Placeholder History-Info hi-entry with Index = 1.1 and addition of "mp=1"
...
Fill up
...
Index for Redirecting number = 1.[[(N-1)* ".1"]] and addition of "mp" set to the hi-index value of the hi-targeted-to-uri that precede.
Index for Called party number = 1.N* ".1" (e.g. N=3 ( 1.1.1.1) and addition of "mp=1.[[(N-1)* ".1"]] | +| Redirection Information | Redirecting Reason and Original Redirection Reason (NOTE 1) | hi-targeted-to-uri; Reason "headers" component as defined in IETF RFC 7044 [91] with cause parameter.
For a placeholder History-Info hi-entry the value "404" shall be taken (NOTE 2). | Cause parameter value | +| | unknown/not available | | 404 | +| | unconditional | | 302 | +| | User Busy | | 486 | +| | No reply | | 408 | +| | Deflection during alerting | | 302 | + +| ISUP Parameter or IE | Derived value of parameter field | SIP component | Value | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | Deflection immediate response | Cause parameter for redirecting reason will be put in the entry of redirecting number, and cause parameter for original redirection reason will be put in the entry of original called number. | 302 | | +| | Mobile subscriber not reachable | | 503 | | +| Called Party Number | See Redirecting number
Nature of address indicator and Address signal | History-Info header field see hi-targeted-to-uri | URI of the last hi-targeted-to-uri entry of History-Info header field (NOTE 6) | | +| Original called number | See Redirecting number
Nature of address indicator and Address signal | History-Info header field see hi-targeted-to-uri | URI of first hi-targeted-to-uri entry of History-Info header field (NOTE 5, NOTE 9)
IF the Original called number is available:
set to the value of the Original called number
ELSE
IF the Redirection counter equals 1 AND the Redirecting number is available,
set to the value of the Redirecting number
ELSE
set to the Unknown User Identity (NOTE 10) | | +| Original called number | APRI | Privacy "headers" component of the first hi-targeted-to-uri entry of History-Info header | Priv-value | | +| | "presentation restricted" | | "history" | | +| | "presentation allowed" | | Privacy header field absent or "none" | | +| NOTE 1: Original Redirection Reason contains only the "unknown/not available" parameter | | | | | +| NOTE 2: For all History-Info hi-entries except the last one a cause parameter in Reason "headers" component as defined in IETF RFC 7044 [91] has to be included. | | | | | +| NOTE 3: If the Redirecting indicator has the value "Call diverted, all redirection information presentation restricted", the privacy value "history" shall be set. | | | | | +| NOTE 4: If the redirecting number APRI has the value "presentation restricted", the privacy value "history" shall be set. | | | | | +| NOTE 5: Used URI scheme shall be SIP URI. The Reason "headers" component with a cause parameter cannot be added if hi-targeted-to-uri is a tel URI. | | | | | +| NOTE 6: The used URI scheme can be tel or SIP since the last hi-targeted-to-uri entry of the History-Info header field does not contain the Reason "headers" component with a cause parameter. | | | | | +| NOTE 7: The hi-target-param defined in IETF RFC 7044 [91] defines the mp-param "mp" as a header field parameter that contains the value of the hi-index in the hi-entry with an hi-targeted-to-uri that reflects the Request-URI that was retargeted, thus identifying the "mapped from" target. Since the hi-entries are created based on the redirection counter to reflect the diverting/diverted-to entries, the hi-target-param "mp" shall be present in each entry except the first one. | | | | | +| NOTE 8: If the Original called number parameter is not available and if the value of the Redirecting counter is equal to one, the Redirecting number parameter is used for the first hi-targeted-to-uri entry of the History-Info header field. | | | | | +| NOTE 9: If a further SIP to ISUP interworking occurs, parameters not present in the original message can then be included. | | | | | +| NOTE 10: The "History-Info" header field may contain an "Unknown User Identity". An "Unknown User Identity" includes information that does not point to the served user and indicates that the user's identity is unknown. The encoding of the "Unknown User Identity" shall be as defined in 3GPP TS 23.003 [74]. | | | | | + +### 7.4.6.3 Interworking at the I-MGCF + +#### 7.4.6.3.1 General + +This clause describes the interworking of the Call Forwarding information at the I-MGCF. + +#### 7.4.6.3.2 Interworking from SIP to ISUP + +**Table 7.4.6.3.2.1: Mapping of SIP to ISUP messages** + +| Message received from SIP | Message send to BICC/ISUP | +|---------------------------|---------------------------| +| INVITE request | IAM | + +**Table 7.4.6.3.2.2: Mapping of History-Info header field to ISUP Redirecting number** + +| Source SIP header field and component | Source Component value | Redirecting number | Derived value of parameter field | +|-----------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| latest History-Info header field entry containing a Reason "headers" component as defined in IETF RFC 7044 [91] with cause parameter (NOTE 1) | | Redirecting number | | +| hi-targeted-to-uri appropriate global number portion of the URI, assumed to be in form "+" CC + NDC + SN | CC | Nature of address indicator | If CC is equal to the country code of the country where MGCF is located AND the next ISUP node is located in the same country, then set to " national (significant) number " else set to " international number " | +| | CC, NDC, SN | Address signals | If NOA is " national (significant) number " then set to NDC + SN.
If NOA is " international number " then set to CC + NDC + SN | +| Privacy header field or/and Privacy "headers" component of the hi-entry in History-Info header field as specified in this table (NOTE 2) | | APRI | If the priv-value " history " or " session " or " header " is received within the Privacy header field or if the priv-value " history " is received within the "headers" component of the hi-targeted-to-uri in the latest hi-entry containing a Reason "headers" component as defined in IETF RFC 7044 [91] with cause parameter, then " presentation restricted " shall be set.
Otherwise, " presentation allowed " shall be set. | + +NOTE 1: If the SIP URI doesn't contain "*user=phone*", mapping to redirecting number is impossible, therefore no need to generate Redirecting number. +NOTE 2: It is possible that an entry of the History-Info header field itself is marked as restricted or the whole History-Info header. + +**Table 7.4.6.3.2.3: Mapping of History-Info header to ISUP Redirection Information** + +| Source SIP header field and component | Source Component value | Redirection Information | Derived value of parameter field | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|-----------------------------|----------------------------------------------------------------------------------------------------------------------| +| Privacy header field, and in History-Info header field in the Privacy "headers" component of the last hi-targeted-to-uri containing a Reason "headers" component as defined in IETF RFC 7044 [91] with cause parameter value as listed in the cause parameter row in this table | "history" or "session" or "header" for the Privacy SIP header or for the hi-targeted-to-uri entry | Redirecting indicator | Call diverted, all redirection information presentation restricted | +| | Privacy header field and the privacy component of the hi-targeted-to-uri entry either absent or set to "none" | | Call diverted | +| | | Original redirection reason | Unknown/not available | +| Cause parameter in the last hi-targeted-to-uri containing a Reason "headers" component as defined in IETF RFC 7044 [91] | Cause parameter value | Redirecting Reason | | +| | 302 | | Deflection immediate response | +| | 486 | | User busy | +| | 408 | | No reply | +| | 503 | | Mobile subscriber not reachable | +| | All other values | | unknown | +| History-Info header field | | Redirection counter | number of History-Info hi-entry(ies) containing a Reason "headers" component with a cause parameter (NOTE 1, NOTE 2) | + +NOTE 1: If the determined number of redirection in SIP exceeds the ISUP maximum parameter value, the MGCF shall set the Redirection counter to its maximum value. For instance, in ISUP ITU-T Q.763 [4], the Redirection counter parameter cannot exceed 5. + +NOTE 2: The Redirection counter value will be incremented regardless of the SIP URI format. + +**Table 7.4.6.3.2.4: Mapping of History-Info header field to ISUP Original Called number** + +| Source SIP header field and component | Source Component value | Original called number | Derived value of parameter field | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Numbering Plan Indicator | "ISDN (Telephony) numbering plan (Recommendation E.164)" | +| hi-targeted-to-uri of 1 st hi-targeted-to-uri containing a Reason "headers" component as defined in IETF RFC 7044 [91] with cause parameter; appropriate global number portion of the URI, assumed to be in form "+" CC + NDC + SN (NOTE 1) | CC | Nature of address indicator | If CC is equal to the country code of the country where MGCF is located AND the next ISUP node is located in the same country, then set to "national (significant) number" else set to "international number" | +| | CC, NDC, SN | Address signals | If NOA is "national (significant) number" then set to NDC + SN.
If NOA is "international number" then set to CC + NDC + SN | +| Privacy "headers" component in History-Info header field of the History-Info header field entry as defined above in this table (NOTE 2) | "history" or "session" or "header" | APRI | "presentation restricted" | +| | Privacy header field absent or "none" | | "presentation allowed" | + +NOTE 1: If it is SIP URI and doesn't contain "user=phone", mapping to Original Called number is impossible, therefore no need to generate Original Called number. + +NOTE 2: It is possible that an entry of the History-Info header field itself is marked as restricted or the whole History-Info header. + +**Table 7.4.6.3.2.5: Mapping of INVITE to IAM** + +| INVITE | | IAM | | +|---------------------------|-----------------------|-------------------------|-----------------------| +| History-Info header field | See table 7.4.6.3.2.2 | Redirecting number | See table 7.4.6.3.2.2 | +| History-Info header field | See table 7.4.6.3.2.3 | Redirection Information | See table 7.4.6.3.2.3 | +| History-Info header field | See table 7.4.6.3.2.4 | Original Called Number | See table 7.4.6.3.2.4 | + +## 7.4.6.3.3 Interworking from ISUP to SIP + +**Table 7.4.6.3.3.1: Mapping of ISUP to SIP Messages** + +| ←Message sent to SIP | ←Message Received from BICC/ISUP | | +|-------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| 181 (Call Is Being Forwarded) | ACM no indication with Redirection number and Call diversion information parameters (CFU, CFB, Cdi) | See table 7.4.6.3.3.3 | +| 180 (Ringing) | ACM indicating ringing, OBCI: "Call diversion may occur" (CFNR, Cda) | See clause 7.2.3.1.4 | +| 181 (Call Is Being Forwarded) | CPG indicating progress or subsequent diversion indicated in the CPG with Redirection number and Call diversion information parameters (CFNR, Cda) | See table 7.4.6.3.3.4 | +| 180 (Ringing) | CPG indicating ringing and Redirection number restriction parameter | See table 7.4.6.3.3.5 | +| 200 (OK) | ANM and Redirection number restriction parameter | See table 7.4.6.3.3.6 | + +**Table 7.4.6.3.3.2: Mapping of ISUP Redirection Number Restriction to History-Info header field** + +| Redirection Number Restriction | Derived value of parameter field | SIP component | Value | +|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------| +| Presentation restricted indicator | " Presentation restricted " | Privacy "headers" component of the hi-targeted-to-uri | " History " | +| | " Presentation allowed " or absent AND a previously received notification subscription options was NOT " presentation not allowed " OR was NOT " presentation allowed without redirection number " | | Privacy header field absent or " none " | + +**Table 7.4.6.3.3.3: Mapping of ACM 181 (Call Is Being Forwarded) response** + +| ISUP Parameter | Derived value of parameter field | SIP component | Value | +|-----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| Generic notification indicator
Notification indicator | Call is diverting | | | +| | | 1 st hi-entry of History-info header having an index = 1 (NOTE 1) | Unknown User Identity (NOTE 4) | +| Redirection number | | 2 nd hi-entry of History-Info header field having an index 1.1 | hi-targeted-to-uri: | +| Nature of address indicator: | " national (significant) number " | hi-targeted-to-uri | Add CC (of the country where the MGCF is located) to Redirection number Address Signals to construct E.164 number in URI. | +| | " international number " | | Map complete Redirection number Address Signals to E.164 number in URI. | +| Address Signals | If NOA is " national (significant) number " then the format of the Address Signals is:
NDC + SN
If NOA is " international number " then the format of the Address Signals is:
CC + NDC + SN | hi-targeted-to-uri | Addr-spec
"+" CC NDC SN mapped to userinfo portion of SIP URI (NOTE 3)
Add "user=phone". | +| Call diversion information | Redirecting Reason | Reason "headers" component as defined in IETF RFC 7044 [91] with cause parameter in the penultimate hi-entry (NOTE 2) | Cause parameter value | +| | Unknown | | 404 | +| | Unconditional | | 302 | +| | User busy | | 486 | +| | No reply | | 408 | +| | Deflection immediate response | | 302 | +| | Deflection during alerting | | 302 | +| | Mobile subscriber not reachable | | 503 | +| | Notification subscription options | Privacy "headers" component associated with Redirection number hi-targeted-to-uri (NOTE 2) | | +| | unknown | | Escaped Privacy value is set according to the rules of TS 24.604 [60] clause 4.5.2.6.4 item c | +| | presentation not allowed | | A 181 (Call Is Being Forwarded) shall not be sent | +| | presentation allowed with redirection number | | Escaped Privacy value is set according to the rules of TS 24.604 [60] clause 4.5.2.6.4 item c | +| | presentation allowed without redirection number | | Escaped Privacy value is set according to the rules of TS 24.604 [60] clause 4.5.2.6.4 item c | + +NOTE 1: It is necessary to create two History-Info header entries to carry both Redirection number and Call diversion information. Since the original called number is not available from the ISUP message a hi-targeted-to-uri set to an "Unknown User Identity" is included in the first entry. Only two entries are provided because the number of diversions is not available. + +NOTE 2: Needs to be stored for a possible inclusion into subsequent messages. + +NOTE 3: Used URI scheme shall be SIP URI. The Reason "headers" component with a cause parameter cannot be added if hi-targeted-to-uri is a tel URI. + +NOTE 4: The "History-Info" header field may contain an "Unknown User Identity". An "Unknown User Identity" includes information that does not point to the served user and indicates that the user's identity is unknown. The encoding of the "Unknown User Identity" shall be as defined in 3GPP TS 23.003 [74]. + +**Table 7.4.6.3.3.4: Mapping of CPG 181 (Call Is Being Forwarded) response** + +| ISUP Parameter | Derived value of parameter field | SIP component | Value | +|-----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| Event information
Event Indicator | Progress | | | +| Generic notification indicator
Notification indicator | Call is diverting | | | +| | | 1 st hi-entry of History-Info header having an index = 1 (NOTE 1) | Unknown User Identity (NOTE 4) | +| Redirection number | | 2 nd hi-entry of History-Info header field having an index = 1.1 | hi-targeted-to-uri: | +| Nature of address indicator | " national (significant) number " | hi-targeted-to-uri | Add CC (of the country where the MGCF is located) to Redirection number Address Signals to construct E.164 number in URI. | +| | " international number " | hi-targeted-to-uri | Map complete Redirection number Address Signals to E.164 number in URI. | +| Address Signals | If NOA is " national (significant) number " then the format of the Address Signals is:
NDC + SN
If NOA is " international number " then the format of the Address Signals is:
CC + NDC + SN | hi-targeted-to-uri | Addr-spec
"+" CC NDC SN mapped to userinfo portion of SIP URI (NOTE 3)
Add "user=phone". | +| Call diversion information | Redirecting Reason | Reason "headers" component as defined in IETF RFC 7044 [91] with cause parameter in the penultimate hi-entry (NOTE 2) | Cause parameter value | +| | Unknown | | 404 | +| | Unconditional | | 302 | +| | User busy | | 486 | +| | No reply | | 408 | +| | Deflection immediate response | | 302 | +| | Deflection during alerting | | 302 | +| | Mobile subscriber not reachable | | 503 | +| | Notification subscription options | Privacy "headers" component associated with Redirection number hi-targeted-to-uri (NOTE 2) | | +| | unknown | | Escaped Privacy value is set according to the rules of TS 24.604 [60] clause 4.5.2.6.4 item c | +| | presentation not allowed | | A 181 Call is Being Forwarded shall not be sent | +| | presentation allowed with redirection number | | Escaped Privacy value is set according to the rules of TS 24.604 [60] clause 4.5.2.6.4 item c | +| | presentation allowed without redirection number | | Escaped Privacy value is set according to the rules of TS 24.604 [60] clause 4.5.2.6.4 item c | + +NOTE 1: It is necessary to create two History-Info header entries to carry both Redirection number and Call diversion information. Since the original called number is not available from the ISUP message a hi-targeted-to-uri set to an "Unknown User Identity" is included in the first entry. Only two entries are provided because the number of diversions is not available. + +NOTE 2: Needs to be stored for a possible inclusion into subsequent messages. + +NOTE 3: Used URI scheme shall be SIP URI. The Reason "headers" component with a cause parameter cannot be added if hi-targeted-to-uri is a tel URI. + +NOTE 4: The "History-Info" header field may contain an "Unknown User Identity". An "Unknown User Identity" includes information that does not point to the served user and indicates that the user's identity is unknown. The + +| | +|-------------------------------------------------------------------------------------| +| encoding of the "Unknown User Identity" shall be as defined in 3GPP TS 23.003 [74]. | +|-------------------------------------------------------------------------------------| + +Table 7.4.6.3.3.5 addresses two separate conditions: the CPG message is received from the diverting exchange in which case the Call diversion information parameter is included; and the CPG message is received from the diverted-to exchange in which case the Call diversion information parameter is not included. Interworking for both conditions is shown. + +**Table 7.4.6.3.3.5: Mapping of CPG 180 (Ringing) response** + +| ISUP Parameter | Derived value of parameter field | SIP component | Value | +|-------------------------------------------------------|--------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| Event information
Event Indicator | Alerting | | | +| | | 1 st hi-entry of History-Info header having an index = 1 (NOTE 1) | Unknown User Identity (NOTE 3) | +| Call diversion information | Redirecting Reason | Reason "headers" component as defined in IETF RFC 7044 [91] with cause parameter in the penultimate hi-entry (NOTE 2) | Cause parameter value | +| | Unknown | | 404 | +| | Unconditional | | 302 | +| | User busy | | 486 | +| | No reply | | 408 | +| | Deflection immediate response | | 302 | +| | Deflection during alerting | | 302 | +| | Mobile subscriber not reachable | | 503 | +| | Notification subscription options | Privacy "headers" component associated with Redirection number hi-targeted-to-uri (NOTE 2) | | +| | unknown | | Escaped Privacy value is set according to the rules of TS 24.604 [60] clause 4.5.2.6.4 item c | +| | presentation not allowed | | The 180 (Ringing) response shall be sent without the the History-Info header field included | +| | presentation allowed with redirection number | | Escaped Privacy value is set according to the rules of TS 24.604 [60] clause 4.5.2.6.4 item c | +| | presentation allowed without redirection number | | Escaped Privacy value is set according to the rules of TS 24.604 [60] clause 4.5.2.6.4 item c | +| Redirection number | | 2 nd hi-entry of History-Info header field having an index = 1.1 | See table 7.4.6.3.3.3 | +| If no Call diversion information parameter is present | | Reason "headers" component as defined in IETF RFC 7044 [91] with cause parameter in the penultimate hi-entry | Value stored from a previous received ACM or CPG. See tables 7.4.6.3.3.3 and 7.4.6.3.3.4 | +| | | Privacy "headers" component associated with Redirection number hi-targeted-to-uri | Value stored from a previous received ACM or CPG. See tables 7.4.6.3.3.3 and 7.4.6.3.3.4 | +| Redirection number restriction | | | See table 7.4.6.3.3.2 | + +NOTE 1: It is necessary to create two History-Info header entries to carry both Redirection number and Redirecting reason. Since the original called number is not available from the ISUP message a hi-targeted-to-uri set to an "Unknown User Identity" is included in the first entry. Only two entries are provided because the number of diversions is not available. + +NOTE 2: Needs to be stored for a possible inclusion into subsequent messages. + +NOTE 3: The "History-Info" header field may contain an "Unknown User Identity". An "Unknown User Identity" includes information that does not point to the served user and indicates that the user's identity is unknown. The encoding of the "Unknown User Identity" shall be as defined in 3GPP TS 23.003 [74]. + +**Table 7.4.6.3.3.6: Mapping of ANM & 200 (OK) response (to INVITE request)** + +| ISUP Parameter | Derived value of parameter field | SIP component | Value | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|--------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------| +| | | 1 st hi-entry of History-Info header having an index = 1 (NOTE 1) | Unknown User Identity (NOTE 2) | +| Redirection number | | 2 nd hi-entry of History-Info header field having an index = 1.1 | See table 7.4.6.3.3.3 | +| | | Reason "headers" component as defined in IETF RFC 7044 [91] with cause parameter in the penultimate hi-entry | Value stored from a previously received ACM or CPG. See tables 7.4.6.3.3.3 and 7.4.6.3.3.4 | +| Redirection number restriction | | | See table 7.4.6.3.3.2 | +| NOTE 1: It is necessary to create two hi-entries of History-Info header field to carry both Redirection number and Redirecting reason. Since the original called number is not available from the ISUP message a hi-targeted-to-uri set to an "Unknown User Identity" is included in the first entry. Only two entries are provided because the number of diversions is not available. | | | | +| NOTE 2: The "History-Info" header field may contain an "Unknown User Identity". An "Unknown User Identity" includes information that does not point to the served user and indicates that the user's identity is unknown. The encoding of the "Unknown User Identity" shall be as defined in 3GPP TS 23.003 [74]. | | | | + +## 7.4.7 Void + +## 7.4.8 Explicit Call Transfer (ECT) + +When the MGCF receives a FAC message with Generic notification indicator coded as "Call transfer active" or "call transfer alerting" and a CPG with Generic notification indicator coded as "Remote hold" was received previously for the current communication, the action described in table 24be applies. In all other cases the actions of the MGCF at the ISUP/BICC side are described in ITU-T Recommendation Q.732.7 [42] under the clause "Interactions with other networks". + +**Table 24be: Mapping between ISUP and SIP for the Explicit Communication Transfer supplementary service** + +| ISUP message | Mapping | +|------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------| +| FAC with a "call transfer, active" or "call transfer, alerting" Generic notification indicator | As described for CPG message with a "remote retrieval" Generic notification indicator in Clause 7.4.10.2 | + +## 7.4.9 Call Waiting + +The actions of the MGCF at the ISUP/BICC side are described in ITU-T Q.733.1 [42] under the clause "Interactions with other networks". + +## 7.4.10 Call Hold + +The service is interworked as indicated in 3GPP TS 23.228 [12]. + +### 7.4.10.1 Session hold initiated from the IM CN subsystem side + +The IMS network makes a hold request by sending an UPDATE or re-INVITE request containing an SDP offer with: + +- an "*a=inactive*" SDP attribute if the stream was a "*recvonly*" media stream; or +- an "*a=sendonly*" SDP attribute if the stream was a "*sendrecv*" media stream. + +Upon receipt of the hold request from the IMS network, the MGCF shall send a CPG message to the CS side with a "remote hold" *Generic notification indicator*. Towards the IMS network the MGCF shall send a 200 OK final response containing an SDP answer with: + +- an "a=*inactive*" SDP attribute if the received SDP offer contained an "a=*inactive*" SDP attribute; or +- an "a=*recvonly*" SDP attribute if the received SDP offer contained an "a=*sendonly*" SDP attribute. + +To resume the session, the IMS network sends an UPDATE or re-INVITE request containing an SDP offer with: + +- an "a=*recvonly*" SDP attribute if the stream was an "*inactive*" media stream; or +- an "a=*sendrecv*" SDP attribute or without any direction SDP attribute ("a=*sendrecv*", "a=*recvonly*", "a=*sendonly*", "a=*inactive*") if the stream was a "*sendonly*" media stream. + +Upon receipt of the resume request from the IMS network, the MGCF shall send a CPG message to the CS side with a "remove retrieval" *Generic notification indicator*. Towards the IMS network the MGCF shall send a 200 OK final response containing an SDP answer with: + +- an "a=*sendonly*" SDP attribute if the received SDP offer contained an "a=*recvonly*" SDP attribute; or +- an "a=*sendrecv*" SDP attribute or without any direction SDP attribute ("a=*sendrecv*", "a=*recvonly*", "a=*sendonly*", "a=*inactive*") if the received SDP offer contained an "a=*sendrecv*" SDP attribute. + +However, the I-MGCF shall not send a CPG message upon reception of SDP offer containing "a=*inactive*" SDP attribute within an initial INVITE request establishing a new SIP dialogue and upon reception of the first subsequent SDP offer activating those media. + +The user plane interworking of the hold/resume request is described in the clause 9.2.9. + + + +``` + +sequenceDiagram + participant IMS as IMS Network + participant MGCF as MGCF + participant CS as CS Network + + Note over IMS, MGCF: Hold Sequence + IMS->>MGCF: 1. SIP: UPDATE [SDP, a=sendonly/inactive] + MGCF->>CS: 2. BICC/ISUP: CPG (Hold) + MGCF->>IMS: 3. SIP: 200 OK [SDP] + + Note over IMS, MGCF: Resume Sequence + IMS->>MGCF: 4. SIP: UPDATE [SDP, a=sendrecv/recvonly] + MGCF->>CS: 5. BICC/ISUP: CPG (Retrieve) + MGCF->>IMS: 6. SIP: 200 OK [SDP] + +``` + +Sequence diagram showing session hold and resume initiated from the IM CN subsystem side. The diagram involves an MGCF and an external network. The hold sequence (steps 1-3) shows an UPDATE request with a=sendonly/inactive, a CPG (Hold) message to the CS side, and a 200 OK response. The resume sequence (steps 4-6) shows an UPDATE request with a=sendrecv/recvonly, a CPG (Retrieve) message to the CS side, and a 200 OK response. + +**Figure 30a: Session hold/resume initiated from the IM CN subsystem side** + +### 7.4.10.2 Session hold initiated from the CS network side + +If an MGCF receives a CPG message with a "remote hold" *Generic notification indicator* and there is no dialog established towards the IMS UE the MGCF shall send, when the first dialog is established, an UPDATE or re-INVITE request containing an SDP offer with: + +- an "*a=sendonly*" SDP attribute if the stream on this dialog was a "*sendrecv*" media stream; or +- an "*a=inactive*" SDP attribute if the stream on this dialog was a "*recvonly*" media stream, + +NOTE 1: If a media stream directionality towards the IMS UE was "*sendonly*" or "*inactive*" a call hold request is not interworked. + +as described in IETF RFC 3264 [36]. For an early dialog an UPDATE request shall be used. + +When an MGCF receives a CPG message with a "*remote hold*" *Generic notification indicator* and the media on the IMS side are "*sendrecv*" or "*recvonly*", the MGCF shall forward the hold request by sending an UPDATE request on the early dialog which was last established containing an SDP offer with: + +- an "*a=sendonly*" SDP attribute if the stream on this dialog was a "*sendrecv*" media stream;" or +- an "*a=inactive*" SDP attribute" if the stream on this dialog was a "*recvonly*" media stream, + +NOTE 2: If a media stream directionality towards the IMS UE was "*sendonly*" or "*inactive*" a call hold request is not interworked. + +as described in IETF RFC 3264 [36]. + +If an additional early dialog is established during the "*remote hold*" condition the MGCF shall send on this new dialog an UPDATE request containing an SDP offer with an "*a=sendonly*" or an "*a=inactive*" SDP attribute, depending on media stream directionality on this dialog, as described above. + +If an UPDATE request with an SDP offer is received on one of the early dialogs for a call in the "*remote hold*" condition the MGCF shall send an appropriate SDP answer. If the MGCF had not invoked a call hold service towards the IMS on that dialog before, the MGCF shall then send a new UPDATE request including an SDP offer with an "*a=sendonly*" or an "*a=inactive*" SDP attribute, depending on media stream directionality on this dialog, as described above. + +If an MGCF receives a 200 OK (INVITE) response on an early dialog for the call in a "*remote hold*" condition and if the MGCF on the dialog where 200 OK (INVITE) response was received had not invoked a call hold service before, the MGCF shall send an UPDATE or re-INVITE request (according to implementation option) containing an SDP offer with an "*a=sendonly*" or an "*a=inactive*" SDP attribute, depending on media stream directionality on this dialog, as described above. If the Contact header field of the received 200 OK (INVITE) response contained an "*isfocus*" media feature tag, defined in IETF RFC 3840 [135], the MGCF shall order the IM-MGW to disconnect the media towards the IMS. + +If the MGCF receives a CPG with *Generic Notification Indicator* "*remote hold*" and there is a confirmed dialog on IMS side then the MGCF shall send a SIP re-INVITE or UPDATE request (according to implementation option) containing an SDP offer with an "*a=sendonly*" or an "*a=inactive*" SDP attribute, depending on media stream directionality on this dialog, as described above. + +If the MGCF receives a CPG with a *Generic Notification Indicator* "*remote retrieval*" and there is an early dialog on IMS side then a SIP UPDATE request containing an SDP offer with: + +- an "*a=recvonly*" SDP attribute if the stream was an "*inactive*" media stream; or +- an "*a=sendrecv*" SDP attribute or without any direction SDP attribute ("*a=sendrecv*", "*a=recvonly*", "*a=sendonly*", "*a=inactive*") if the stream was a "*sendonly*" media stream, + +shall be sent if the call hold service had been invoked on this early dialog before. For each subsequent early dialog for which the MGCF receives an 18x response or an UPDATE request with an SDP offer, the MGCF shall send a SIP UPDATE request with the SDP offer indicating call retrieval (as described above) after a possible SDP answer to the SDP offer, if that dialog had received a call hold indication before. + +If the MGCF receives a CPG with *Generic Notification Indicator* "*remote retrieval*" and there is a confirmed dialog on IMS side then a SIP re-INVITE or UPDATE request (according to implementation option) containing an SDP offer with: + +- an "*a=recvonly*" SDP attribute if the stream was an "*inactive*" media stream; or + +- an "*a=sendrecv*" SDP attribute if the stream was a "*sendonly*" media stream, + +shall be sent for this dialog only if the call hold service had been invoked for this dialog before. + +If link aliveness information is required at the IM-MGW while the media are on hold, and RTCP was previously disabled the MGCF should provide modified SDP RR and RS bandwidth modifiers specified in IETF RFC 3556 [59] within the UPDATE or re-INVITE request holding and retrieving the media to temporarily enable RTCP while the media are on hold, as detailed in clause 7.3.1 of 3GPP TS 26.114 [104]. If no link aliveness information is required at the IM-MGW or RTCP was previously enabled, the MGCF should provide the SDP RR and RS bandwidth modifiers previously used. + +The interworking does not impact the user plane with the following exceptions: + +- the MGCF provides modified SDP RR and RS bandwidth modifiers within the UPDATE or re-INVITE request; +- the Contact header of the IMS remote party contains the "*isfocus*" media feature tag; or +- the MGCF has identified a speech call as an "ICS call" as specified in clause 7.2.3.1.2.12 or in clause 7.2.3.2.7a. + +If the MGCF provides modified SDP RR and RS bandwidth modifiers to the IMS side, the MGCF shall also provide modified SDP RR and RS bandwidths to the IM-MGW, as described in the clause 9.2.10. + +If there is a confirmed dialog on the IMS side for which the MGCF received the Contact header of the IMS remote party (in the initial INVITE request or in the 200 OK (INVITE) response) with the "*isfocus*" media feature tag, defined in IETF RFC 3840 [135], then upon reception of the CPG message with: + +- a "*remote hold*" *Generic notification indicator* the MGCF shall request the IM-MGW to suspend sending media towards the IMS side; or +- a "*remote retrieval*" *Generic notification indicator* the MGCF shall request the IM-MGW to re-establish communication towards the IMS network if the MGCF requested the IM-MGW to suspend sending media on the "*remote hold*" request, + +prior to sending of the UPDATE or re-INVITE request to the IMS side. + +NOTE 3: If a participant of a conference invokes a hold request, it is not desirable to provide an announcement to the conference. + +For a speech call that is identified as the "ICS call", upon reception of the CPG message with: + +- a "*remote hold*" *Generic notification indicator* the MGCF shall request the IM-MGW to suspend sending media towards the IMS side; or +- a "*remote retrieval*" *Generic notification indicator* the MGCF shall request the IM-MGW to re-establish communication towards the IMS network if the MGCF requested the IM-MGW to suspend sending media on the "*remote hold*" request, + +prior to sending of the UPDATE or re-INVITE request to the IMS side. + +![Sequence diagram for Figure 30b: Session hold/resume initiated from the CS network side. The diagram shows two parts: a hold session and a resume session. In the hold session, a BICC/ISUP CPG (Hold) message is received by the MGCF, which then sends a SIP UPDATE [SDP, a=sendonly/inactive] to the remote party, receiving a SIP 200 OK [SDP] in response. In the resume session, a BICC/ISUP CPG (Retrieve) message is received by the MGCF, which then sends a SIP UPDATE [SDP, a=sendrecv/recvonly] to the remote party, receiving a SIP 200 OK [SDP] in response.](b0384c8e0ff826a8116ab2ff67dadc43_img.jpg) + +``` + +sequenceDiagram + participant CS as CS Network Side + participant MGCF + participant Remote + + Note left of MGCF: Hold Session + CS->>MGCF: 1. BICC/ISUP: CPG (Hold) + MGCF->>Remote: 2. SIP: UPDATE [SDP, a=sendonly/inactive] + Remote-->>MGCF: 3. SIP: 200 OK [SDP] + + Note left of MGCF: Resume Session + CS->>MGCF: 4. BICC/ISUP: CPG (Retrieve) + MGCF->>Remote: 5. SIP: UPDATE [SDP, a=sendrecv/recvonly] + Remote-->>MGCF: 6. SIP: 200 OK [SDP] + +``` + +Sequence diagram for Figure 30b: Session hold/resume initiated from the CS network side. The diagram shows two parts: a hold session and a resume session. In the hold session, a BICC/ISUP CPG (Hold) message is received by the MGCF, which then sends a SIP UPDATE [SDP, a=sendonly/inactive] to the remote party, receiving a SIP 200 OK [SDP] in response. In the resume session, a BICC/ISUP CPG (Retrieve) message is received by the MGCF, which then sends a SIP UPDATE [SDP, a=sendrecv/recvonly] to the remote party, receiving a SIP 200 OK [SDP] in response. + +**Figure 30b: Session hold/resume initiated from the CS network side** + +#### 7.4.11 Call Completion on busy subscriber + +The actions of the MGCF at the ISUP/BICC side are described in ITU-T Recommendation Q.733.3 [42] under the clause "Interactions with other networks". + +#### 7.4.12 Completion of Calls on No Reply (CCNR) + +The actions of the MGCF at the ISUP/BICC side are described in ITU-T Recommendation Q.733.5 [42] under the clause "Interactions with other networks". + +#### 7.4.13 Terminal Portability (TP) + +Terminal Portability is defined as an ISUP supplementary service within ITU-T Rec. Q.733.4. [42]. + +A Suspend message containing the Suspend/Resume indicators set to "ISDN subscriber initiated" shall be treated like a CPG with "remote hold" in Clause 7.4.10. Resume message containing the Suspend/Resume indicators set to "ISDN subscriber initiated" shall be treated like a CPG with "remote retrieval" in Clause 7.4.10. + +#### 7.4.14 Conference calling (CONF) / Three-Party Service (3PTY) + +The default behaviour of the MGCF at the ISUP/BICC side is described in ITU-T Recommendation Q.734.1[42] under the clause "Interactions with other networks". In addition, the MGCF may apply the interworking from ISUP to SIP described in Table 24aa. + +Alternatively, the MGCF may apply the interworking to the Conference supplementary service described in clause 7.5.6. + +**Table 24aa: Mapping between ISUP and SIP for the Conference Calling (CONF) and Three-Party Service (3PTY) supplementary service** + +| ISUP message | Mapping | +|---------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------| +| CPG with a "Conference established" Generic notification indicator | As described for CPG message with a "remote retrieval" Generic notification indicator in Clause 7.4.10.2 | +| CPG with a "Conference disconnected" Generic notification indicator | As described for CPG message with a "remote retrieval" Generic notification indicator in Clause 7.4.10.2 | +| CPG with an "isolated" Generic notification indicator | As described for CPG message with a "remote hold" Generic notification indicator in Clause 7.4.10.2 | +| CPG with a "reattached" Generic notification indicator | As described for CPG message with a "remote retrieval" Generic notification indicator in Clause 7.4.10.2 | + +## 7.4.15 Void + +## 7.4.16 Closed User Group (CUG) + +The actions of the MGCF at the ISUP/BICC side are described in ITU-T Recommendation Q.735.1[42] under the clause 1.5.2.4.2 "Exceptional procedures". + +## 7.4.17 Multi-Level Precedence and Pre-emption (MLPP) + +The actions of the MGCF at the ISUP/BICC side are described in ITU-T Recommendation Q.735.3 [42] under the clause "Interactions with other networks". + +## 7.4.18 Global Virtual Network Service (GVNS) + +The actions of the MGCF at the ISUP/BICC side are described in ITU-T Recommendation Q.735.6 [42] under the clause "Interactions with other networks". + +## 7.4.19 International telecommunication charge card (ITCC) + +An International Telecommunication charge card call is a basic call and no additional treatment is required by the MGCF. + +## 7.4.20 Reverse charging (REV) + +The actions of the MGCF at the ISUP/BICC side are described in ITU-T Recommendation Q.736.3 [42] under the clause "Interactions with other networks". + +## 7.4.21 User-to-User Signalling (UUS) + +### 7.4.21.0 General + +Procedures for the ISDN supplementary service "User-to-user signalling" are specified in ITU-T Recommendation Q.737.1 [42]. + +### 7.4.21.1 User-to-User Signalling (UUS) service 1 (implicit) + +#### 7.4.21.1.0 General + +The coding of the User-user information element is described within ITU-T Recommendation Q.931 [149]. The User-user information element is carried within the ISDN user part parameter user-to-user information, as defined in ITU-T Recommendation Q.763 [4]. The User-to-User header field is defined within IETF RFC 7433 [99]. A package for interworking user-to-user information with the ISDN is defined by IETF RFC 7434 [99A]. + +#### 7.4.21.1.1 Void + +#### 7.4.21.1.2 User-to-user information Interworking from SIP to ISUP + +On the receipt of a User-to-User header field with the "*purpose*" header field parameter set to "*isdn-uui*", or a User-to-User header field without a "*purpose*" parameter, with "*encoding*" header field parameter set to "*hex*" or without an "*encoding*" parameter, with "*content*" header field parameter set to "*isdn-uui*" or without a "*content*" parameter, that is valid as defined by IETF RFC 7434 [99A], the MGCF shall map the content of the "*uui-data*" field to the "*protocol discriminator*" and "*user information*" parameters of the User-user information element. + +The "*length of user-user contents*" parameter shall be set by the MGCF according to the normal procedures. + +The MGCF maps the messages transporting the user-to-user information according to the normal interworking procedures (see table 24ab). + +**Table 24ab: Mapping of the User-to-User header field to the ISUP user-to-user information parameter** + +| SIP parameter | | ISUP parameter | | +|------------------|------------------------|---------------------|---------------------------------------------| +| SIP header field | Source component value | ISUP parameter name | ISUP parameter field | +| User-to-User | uui-data | User-to-user | Protocol discriminator and user information | + +#### 7.4.21.1.3 User-to-user information Interworking from ISUP to SIP + +On the receipt of the user-to-user information parameter the MGCF shall map the protocol discriminator and user information parameter fields to the uui-data field of the User-to-User header field (see table 24ac). + +If sent, the "*purpose*", "*content*" and "*encoding*" header field parameters are not mapped and are set in accordance with IETF RFC 7434 [99A] + +The MGCF maps the messages transporting the user-to-user information parameters according to the normal interworking procedures. + +**Table 24ac: Mapping of the ISUP user-to-user information parameter to the User-to-User header field** + +| ISUP parameter | | SIP parameter | | +|--------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|------------------|------------------------| +| ISUP parameter name | ISUP parameter field | SIP header field | Source component value | +| User-to-user | Protocol discriminator and user information | User-to-User | uui-data (NOTE) | +| NOTE: The MGCF shall always send uui-data as a token (see IETF RFC 7433 [99]). The letters used for the hex digits shall always be capital form. | | | | + +#### 7.4.21.2 User-to-User Signalling (UUS) service 1 (explicit) + +The actions of the MGCF at the ISUP/BICC side are described in ITU-T Recommendation Q.737.1 [42] under the clause "Interaction with other networks". + +#### 7.4.21.3 User-to-User Signalling (UUS) service 2 (explicit) + +The actions of the MGCF at the ISUP/BICC side are described in ITU-T Recommendation Q.737.1 [42] under the clause "Interaction with other networks". + +#### 7.4.21.4 User-to-User Signalling (UUS) service 3 (explicit) + +The actions of the MGCF at the ISUP/BICC side are described in ITU-T Recommendation Q.737.1 [42] under the clause "Interaction with other networks". + +### 7.4.22 Multiple Subscriber Number (MSN) + +A MSN call is a basic call and no additional treatment is required by the MGCF. + +## 7.4.23 Anonymous Call rejection + +### 7.4.23.0 General + +The Anonymous Call rejection (ACR) supplementary service in the CS domain is described within 3GPP TS 23.088 [134]. The ETSI ACR service is described within ETSI EN 300 356-21 [71]. + +### 7.4.23.1 ISUP-SIP protocol interworking at the I-MGCF + +If ISUP Cause Value field in the ISUP REL includes Cause Value 24 *"call rejected due to feature at the destination"* the I-MGCF shall map this to a 433 (Anonymity Disallowed) SIP response code as described in RFC 5079 [77]. + +### 7.4.23.2 SIP-ISUP protocol interworking at the O-MGCF + +SIP response code 433 (Anonymity Disallowed) shall be mapped to the ISUP Cause Value field 24 *"call rejected due to feature at the destination"* in the ISUP REL. + +## 7.4.24 Customized Alerting Tones (CAT) in the 3GPP CS domain + +The Customized Alerting Tones (CAT) in the 3GPP CS domain service is described in 3GPP TS 23.205 [27]. + +To pass CAT early media from the CS network towards the IM CN subsystem, no special interworking procedures beyond basic call at the I-MGCF are required. The procedure to supply the "P-Early-Media" header field is described in clause 7.2.3.1.4, clause 7.2.3.1.4A and clause 7.2.3.1.4B. + +## 7.5 IMS Supplementary Services + +The following clauses describe the MGCF behaviour related to supplementary services as defined in ITU-T Recommendations Q.730 to ITU-T Q.737 [42] when interworking with an IMS which uses a Multimedia Telephony Application Server (MTAS) providing supplementary services according to 3GPP TS 24.173 [88]. The support of the related procedures is optional. + +### 7.5.1 Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) + +The mapping of Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR); supplementary service with the CLIP/CLIR PSTN/ISDN Supplementary Service is the same mapping as described in clause 7.4.1. The Service itself is described within 3GPP TS 24.607 [63]. + +### 7.5.2 Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) + +#### 7.5.2.1 General + +The protocol specification of the Terminating Identification Presentation and Terminating Identification Restriction supplementary services is described in 3GPP TS 24.608 [64]. + +The procedures for mapping of the connected number described within clause 7.4.2 shall apply. + +#### 7.5.2.2 Interworking at the O-MGCF + +For the mapping of IAM to the INVITE request: + +If an Optional forward call indicators parameter in the IAM is received where the bit H Connected line identity request indicator is set to "requested", then the option tag "from-change" shall be add to the Supported header field. See table 7.5.2.2.1. + +**Table 7.5.2.2.1: Mapping of ISUP IAM to SIP INVITE request** + +| ISUP Parameter | Derived value of parameter field | Source SIP header field and component | Source Component value | +|---------------------------------|------------------------------------------------------------------------|---------------------------------------|------------------------| +| Optional forward call indicator | Connected line identity request indicator is set to "requested" | Supported | "from-change" | + +NOTE: The presence of "from-change" enables the reception of Generic Number with Number qualifier parameter field set to additional connected, if available. As per 3GPP TS 24.608 [64] the presence of "from-change" tag is not a criterion for TIP service. + +If a provisional or final response including the option tag "from-change" is received, then the O-MGCF shall: + +- if a 200 (OK) response to the INVITE request is received, start timer $T_{TIR1}$ ; and +- store the 200 (OK) response, without interworking it. + +Otherwise the 200 (OK) response (to the INVITE request) shall be mapped as described in clause 7.2.3.2.7a. + +If an UPDATE request is received containing a changed From header field before the timer $T_{TIR1}$ expired, then the O-MGCF shall: + +- stop timer $T_{TIR1}$ ; +- map the From header field received in the UPDATE request to the Generic number in the ANM as shown in table 7.5.2.2.2 and table 7.5.2.2.3; +- if the UPDATE request includes a P-Asserted-Identity header field that is different from the one within the stored 200 (OK) response, the latest received P-Asserted-Identity header field shall be mapped to the connected number as described table 24; and +- map the parameters needed to be mapped of the stored 200 (OK) response to an ANM as described in clause 7.4.2.2.3, modified by the changed mapping steps of the From and P-Asserted-Identity header fields. + +When $T_{TIR1}$ expires, then the stored 200 (OK) response (to the INVITE request) response shall be mapped as described in clause 7.4.2.2.3. + +**Table 7.5.2.2.2: Mapping of SIP UPDATE request to ISUP ANM/CON** + +| ANM/CON | UPDATE | +|----------------|-------------------| +| Generic number | From header field | + +**Table 7.5.2.2.3: Mapping of SIP From header field to ISUP Generic Number ("additional connected number") parameter** + +| Source SIP header field and component | Source component value | Generic Number parameter field | Derived value of parameter field | +|-------------------------------------------------------------------------|-----------------------------|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| - | - | Number Qualifier Indicator | "additional connected number" | +| From, userinfo component of URI assumed to be in form "+" CC + NDC + SN | CC | Nature of Address Indicator | If CC is equal to the country code of the country where I-MGCF is located AND the next ISUP node is located in the same country, then set to "national (significant) number" else set to "international number" | +| - | - | Number Incomplete Indicator | "complete" | +| - | - | Numbering Plan Indicator | "ISDN (Telephony) numbering plan (Recommendation E.164)" | +| Privacy, priv-value component | Privacy header field absent | Address Presentation Restricted Indicator (APRI) | "presentation allowed" | +| | "none" | | "presentation allowed" | +| | "header" | | "presentation allowed" | +| | "user" | | "presentation restricted" | +| | "id" | | "presentation allowed" | +| - | - | Screening Indicator | "user provided, not verified" | +| From, userinfo component assumed to be in form "+" CC + NDC + SN | CC, NDC, SN | Address Signals | If NOA is "national (significant) number" then set to NDC + SN.
If NOA is "international number" then set to CC + NDC + SN | + +### 7.5.2.3 Interworking at the I-MGCF + +For the mapping of INVITE request to IAM: + +- the bit H *Connected line identity request indicator* of the Optional forward call indicators parameter in the IAM shall be set to "requested". + +**Table 7.5.2.3.1: Void** + +If a received ISUP ANM includes an ISUP Generic Number ("additional connected number") parameter, then the I-MGCF shall send a 200 (OK) response (to the INVITE request) including an option tag "from-change" If the initial INVITE was received and the Supported header field contains the "from-change" tag, the 200 (OK) response is followed by an UPDATE request, containing the "additional connected number" copied into the From header field as shown in table 7.5.2.3.2. + +The To header field of the UPDATE request is derived from the P-Asserted-Identity header field received within the initial INVITE request. + +**Table 7.5.2.3.2: Mapping of ANM Generic Number ("additional connected number") to SIP From header field in a SIP UPDATE request** + +| ISUP Parameter/field | Value | SIP component | Value | +|---------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| Generic Number Number Qualifier Indicator | " additional connected number " | From header field | display-name (optional) and addr-spec | +| Nature of Address Indicator | " national (significant) number " | Addr-spec | Add "+" CC (of the country where the IWU is located) to Generic Number Address Signals then map to user portion of URI scheme used | +| | " international number " | | Map complete Generic Number Address Signals used prefixed with a "+" to user portion of URI scheme used | +| Address Presentation restriction indicator (APRI) | " presentation allowed " | | No Privacy header field or not " user " | +| | " presentation restricted " | | " user " | +| Address Signals | if NOA is " national (significant) number " then the format of the address signals is:
NDC + SN
If NOA is " international number " then the format of the address signals is:
CC + NDC + SN | Display-name (optional) | display-name shall be mapped from Address Signals, if network policy allows it | +| | | Addr-spec | "+" CC NDC SN mapped to user portion of URI scheme used | + +A received connected number in an ANM shall be mapped to the P-Asserted-Identity header field as shown in table 21 of the UPDATE request. + +## 7.5.2.4 Timer + +**Table 7.5.2.4.1 TIR timer definition** + +| Symbol | Timeout value | Cause for initiation | Normal termination | At expiry | +|-------------------|----------------------------------------------------|------------------------------------------------------------------------------------|-----------------------------|----------------------------------| +| T TIR1 | 100 - 2000 milliseconds (default 100 milliseconds) | On receipt of provisional or final response including the option tag "from-change" | At the receipt of an UPDATE | map the received 200OK to an ANM | + +## 7.5.3 void + +## 7.5.4 Communication Diversion (CDIV) + +### 7.5.4.1 General + +The protocol specification of the Communication Diversion supplementary service is described in 3GPP TS 24.604 [60]. The mapping of Communication Diversion supplementary service with Call Diversion services PSTN/ISDN supplementary service including the mapping of the optional History-Info header field as defined in IETF RFC 7044 [91] is described. + +The hi-target-param "mp" header field parameter as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed. + +In case of interworking with networks which do not provide any notification of the communication diversion or communication redirection information (e.g. redirection counter) in the signalling system, the communication continues according to the basic call procedures. + +In case of interworking with networks not supporting IETF RFC 7044 [91] the "mp" header field parameter may not appear. + +## 7.5.4.2 Interworking at the O-MGCF + +### 7.5.4.2.1 General + +For the mapping of IAM to the INVITE request no additional procedures beyond the basic call and interworking procedures are needed unless Call Diversion services within the ISUP Network appeared as described in clause 7.5.4.2.2. + +With regard to the backward messages the following mapping is valid. + +**Table 7.5.4.2.1.1: Mapping of SIP messages to ISUP messages** + +| ←Message sent to ISUP | ←Message Received from SIP | | +|-------------------------------------------|----------------------------------------------------------------------------------------------------------------|------------------------| +| ACM indicating call forwarding | 181 (Call Is Being Forwarded) response | See table 7.5.4.2.1.6 | +| CPG indicating call forwarding (see NOTE) | 181 (Call Is Being Forwarded) response | See table 7.5.4.2.1.7 | +| ACM indicating ringing | 180 (Ringing) response | See table 7.5.4.2.1.8 | +| CPG indicating alerting (see NOTE) | 180 (Ringing) response | See table 7.5.4.2.1.9 | +| ANM | 200 (OK) response | See table 7.5.4.2.1.10 | +| CON | 200 (OK) response (Neither a 181 (Call Is Being Forwarded) response nor a 180 (Ringing) response was received) | See table 7.5.4.2.1.10 | + +NOTE: A CPG will be sent if an ACM was already sent. + +**Table 7.5.4.2.1.2: Mapping of History-Info header field to ISUP Redirection number** + +| Source SIP header field and component | Source Component value | Redirection number | Derived value of parameter field | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| hi-targeted-to-uri of the last History-Info hi-entry containing a "cause" URI parameter, as defined in IETF RFC 4458 [113].
(NOTE 2) | CC | Nature of address indicator | If CC is equal to the country code of the country where O-MGCF is located AND the next ISUP node is located in the same country, then set to " national (significant) number " else set to " international number ". | +| The global number portion of the hi-targeted-to-uri is assumed to be in form "+" CC + NDC + SN.
(NOTE 1) | CC, NDC, SN | Address signals | If NOA is " national (significant) number " then set to NDC + SN.
If NOA is " international number " then set to CC + NDC + SN. | +| NOTE 1: If the SIP URI doesn't contain " user=phone ", mapping to redirection number is impossible, therefore no need to generate Redirection number and Redirection number restriction parameter (per table 7.5.4.2.1.3), Notification subscription options can't be set as "presentation allowed with redirection number". | | | | +| NOTE 2: The hi-target-param parameter set to "mp" as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed and appears in this hi-targeted-to-uri. In case of interworking with networks not supporting IETF RFC 7044 [91] the "mp" header field parameter may not appear. | | | | + +**Table 7.5.4.2.1.3: Mapping of History-Info header field to ISUP Redirection number restriction** + +| Source SIP header field and component | Source Component value | Redirection number restriction | Derived value of parameter field | +|-----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|-----------------------------------|-------------------------------------------| +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | " history " or " session " or " header " | Presentation restricted indicator | " Presentation restricted " | +| | Privacy "headers" component of the hi-targeted-to-uri and Privacy header field absent or " none " | | " Presentation allowed " or absent | + +**Table 7.5.4.2.1.4: Mapping of hi-targeted-to-uri to ISUP Call diversion information** + +| Source SIP header field and component | Source Component value | Call diversion information | Derived value of parameter field | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | | Notification subscription options |
If the priv-value "history" or "session" or "header" is received within the Privacy header field or the priv-value "history" is received within the "headers" component of the hi-targeted-to-uri representing the diverting URI(s) and within the hi-targeted-to-uri representing diverted-to URI then "presentation not allowed" shall be set.
Otherwise, if the priv-value "history" is received only within the "headers" component of the hi-targeted-to-uri representing the diverted-to URI then "presentation allowed without redirection number" shall be set. (NOTE 1, NOTE 2)
Otherwise, "presentation allowed with redirection number" shall be set.
| | +| "cause" URI parameter, as defined in IETF RFC 4458 [113] of the last History-Info hi-entry containing hi-targeted-to-uri with "cause" URI parameter. (NOTE 3) | Cause value | Redirecting reason | | | +| | 404 | | Unknown | | +| | 302 | | Unconditional | | +| | 486 | | User busy | | +| | 408 | | No reply | | +| | 480 | | Deflection immediate response | | +| | 503 | | Mobile subscriber not reachable | | +| | 487 | | Deflection during alerting | | +| NOTE 1: diverting URI corresponds to the hi-targeted-to-uri of the hi-entry containing a hi-index value that match the "mp" header field parameter value of the diverted-to URI. If the diverted-to URI does not contain the "mp" header field parameter, the diverting URI corresponds to the hi-targeted-to-uri of the hi-entry before the last hi-entry containing "cause" URI parameter. | | | | | +| NOTE 2: diverted-to URI corresponds to the hi-targeted-to-uri of the last hi-entry containing "cause" URI parameter and is mapped to the Redirection number, see table 7.5.4.2.1.2. | | | | | +| NOTE 3: The hi-target-param parameter set to "mp" as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed and appears in this hi-targeted-to-uri. In case of interworking with networks not supporting IETF RFC 7044 [91] the "mp" header field parameter may not appear. | | | | | + +Table 7.5.4.2.1.5: Void + +Table 7.5.4.2.1.6: Mapping of 181 (Call Is Being Forwarded) $\leftarrow$ ACM if no ACM was sent before + +| Source SIP header field and component | Source Component value | ISUP Parameter | Derived value of parameter field | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|------------------------------------------------------------------------|----------------------------------| +| 181 (Call Is Being Forwarded) | | ACM | | +| | | Generic notification indicatorNotification indicator | Call is diverting | +| History-Info header field | See table 7.5.4.2.1.2 | Redirection number | See table 7.5.4.2.1.2 | +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | See table 7.5.4.2.1.3 | Redirection number restriction | See table 7.5.4.2.1.3 | +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | See table 7.5.4.2.1.4 | Call diversion information
Notification subscription options | See table 7.5.4.2.1.4 | +| hi-targeted-to-uri; "cause" URI parameter as defined in IETF RFC 4458 [113] of the last History-Info hi-entry containing such "cause" URI parameter. (NOTE) | See table 7.5.4.2.1.4 | Call diversion information
Redirecting reason | See table 7.5.4.2.1.4 | +| NOTE: The hi-target-param parameter set to "mp" as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed and appears in this hi-targeted-to-uri. In case of interworking with networks not supporting IETF RFC 7044 [91] the "mp" header field parameter may not appear. | | | | + +**Table 7.5.4.2.1.7: Mapping of 181 (Call Is Being Forwarded) © CPG if ACM was already sent** + +| Source SIP header field and component | Source Component value | ISUP Parameter | Derived value of parameter field | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------|----------------------------------| +| 181 (Call Is Being Forwarded) response | | CPG | | +| | | Generic notification indicator
Notification indicator | Call is diverting | +| "cause" URI parameter, as defined in IETF RFC 4458 [113] of the last History-Info hi-entry containing hi-targeted-to-uri with "cause" URI parameter. (NOTE 2) | 486 | Event information
Event indicator | CFB (national use) | +| | 408 (see NOTE 1) | | CFNR (national use) | +| | 302 | | CFU (national use) | +| | Any other value, or if appropriate "national use" value (CFB, CFNR or CFU) is not used in a network. or if no agreement exists between operators to use these values, or if no hi-targeted-to-uri with "cause" URI parameter is contained in the SIP 181. | | PROGRESS | +| History-Info header field | See table 7.5.4.2.1.2 | Redirection number | See table 7.5.4.2.1.2 | +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | See table 7.5.4.2.1.3 | Redirection number restriction | See table 7.5.4.2.1.3 | +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | See table 7.5.4.2.1.4 | Call diversion information
Notification subscription options | See table 7.5.4.2.1.4 | +| hi-targeted-to-uri; "cause" URI parameter, as defined in IETF RFC 4458 [113] of the last History-Info hi-entry containing such "cause" URI parameter. (NOTE 2) | See table 7.5.4.2.1.4 | Call diversion information
Redirecting reason | See table 7.5.4.2.1.4 | + +NOTE 1: This appears in the cases of CFNR. +NOTE 2: The hi-target-param parameter set to "mp" as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed and appears in this hi-targeted-to-uri. In case of interworking with networks not supporting IETF RFC 7044 [91] the "mp" header field parameter may not appear. + +**Table 7.5.4.2.1.8: Mapping of 180 (Ringing) & ACM if no ACM was sent before** + +| Source SIP header field and component | Source Component value | ISUP Parameter | Derived value of parameter field | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|----------------------------------| +| 180 (Ringing) response | | ACM | | +| History-Info header field | If hi-targeted-to-uri of at least one History-Info hi-entry contains a "cause" URI parameter, as defined in IETF RFC 4458 [113]. | Generic notification indicator
Notification indicator | Call is diverting | +| History-Info header field | See table 7.5.4.2.1.2 | Redirection number
(NOTE 1) | See table 7.5.4.2.1.2 | +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | See table 7.5.4.2.1.3 | Redirection number restriction (NOTE 1) | See table 7.5.4.2.1.3 | +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | See table 7.5.4.2.1.4 | Call diversion information
Notification subscription options (NOTE 1) | See table 7.5.4.2.1.4 | +| hi-targeted-to-uri; "cause" URI parameter, as defined in IETF RFC 4458 [113] of the last History-Info hi-entry containing such "cause" URI parameter. (NOTE 2) | See table 7.5.4.2.1.4 | Call diversion information
Redirecting reason (NOTE 1) | See table 7.5.4.2.1.4 | +| NOTE 1: Parameter shall only be supplied if hi-targeted-to-uri of at least one History-Info hi-entry contains a "cause" URI parameter, as defined in IETF RFC 4458 [113]. | | | | +| NOTE 2: The hi-target-param parameter set to "mp" as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed and appears in this hi-targeted-to-uri. In case of interworking with networks not supporting IETF RFC 7044 [91] the "mp" header field parameter may not appear. | | | | + +The mapping described within table 7.5.4.2.1.8 can only appear if the communication has already undergone a Communications diversion in the IMS and the 180 (Ringing) is the first provisional response sent in backward direction. + +The O-MGCF can indicate the call diversion information in the mapping of the 180 (Ringing) provisional response to a CPG message in fact if the response before was a 181 (Call Is Being Forwarded). + +**Table 7.5.4.2.1.9: Mapping of 180 (Ringing) & CPG if ACM was already sent** + +| Source SIP header field and component | Source Component value | ISUP Parameter | Derived value of parameter field | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|----------------------------------| +| 180 (Ringing) response | | CPG | | +| History-Info header field | If hi-targeted-to-uri of at least one History-Info hi-entry contains a "cause" URI parameter, as defined in IETF RFC 4458 [113]. | Generic notification indicator
Notification indicator | Call is diverting | +| | | Event information
Event indicator | ALERTING | +| History-Info header field | See table 7.5.4.2.1.2 | Redirection number
(NOTE 1) | See table 7.5.4.2.1.2 | +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | See table 7.5.4.2.1.3 | Redirection number restriction (NOTE 1) | See table 7.5.4.2.1.3 | +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | See table 7.5.4.2.1.4 | Call diversion information
Notification subscription options (NOTE 1) | See table 7.5.4.2.1.4 | +| hi-targeted-to-uri; "cause" URI parameter, as defined in IETF RFC 4458 [113] of the last History-Info hi-entry containing such "cause" URI parameter. (NOTE 2) | See table 7.5.4.2.1.4 | Call diversion information
Redirecting reason (NOTE 1) | See table 7.5.4.2.1.4 | +| NOTE 1: Parameter shall only be supplied if hi-targeted-to-uri of at least one History-Info hi-entry contains a "cause" URI parameter, as defined in IETF RFC 4458 [113]. | | | | +| NOTE 2: The hi-target-param parameter set to "mp" as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed and appears in this hi-targeted-to-uri. In case of interworking with networks not supporting IETF RFC 7044 [91] the "mp" header field parameter may not appear. | | | | + +The mapping in table 7.5.4.2.1.9 appears when a 181 (Call Is Being Forwarded) provisional response previously was mapped to an ACM. Therefore the state machine of the O-MGCF knows that a CDIV is in progress. + +**Table 7.5.4.2.1.10: Mapping of 200 (OK) response** + +| Source SIP header field and component | Source Component value | ISUP Parameter | Derived value of parameter field | +|------------------------------------------------------------------------------------------------|------------------------|--------------------------------|----------------------------------| +| 200 (OK) response | | ANM/CON | | +| History-Info header field | See table 7.5.4.2.1.2 | Redirection number(NOTE) | See table 7.5.4.2.1.2 | +| Privacy "headers" component of the hi-targeted-to-uri or/and Privacy header field | See table 7.5.4.2.1.3 | Redirection number restriction | See table 7.5.4.2.1.3 | +| NOTE: Redirection number shall only be supplied if 200 (OK) response is mapped to ANM message. | | | | + +## 7.5.4.2.2 Call Diversion within the ISUP Network appeared + +The following scenario shows if a Call Diversion service appears in the ISUP/PSTN and the diverted-to number is within the SIP network. Table 7.5.4.2.2.1 should be seen as an example. + +For the mapping of 180 (Ringing) response and 200 (OK) response (to the INVITE request) to the regarding ISUP messages and parameters no additional procedures beyond the basic call procedures are needed. + +To interwork the redirecting number at the O-MGCF it can be needed to create placeholder History-Info hi-entries. Such a History-Info hi-entry shall contain a hi-targeted-to-uri set to an "Unknown User Identity" (value "sip:unknown@unknown.invalid" as defined in 3GPP TS 23.003 [74]), a "cause" URI parameter, a hi-index and an "mp" header field parameter as described within table 7.5.4.2.2.1. + +Table 7.5.4.2.2.1: Mapping of IAM to SIP INVITE request + +| ISUP Parameter or IE | Derived value of parameter field | SIP component | Value | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IAM | | INVITE request | | +| Redirecting number | | History-Info header field | IF Redirection counter exceeds 1
hi-targeted-to-uri of the
penultimate created hi-entry
(NOTE 9)
IF Redirecting number is
available
set to the value of the
Redirecting number
ELSE
set to the Unknown User
Identity (NOTE 10)
ELSE
no mapping (NOTE 8) | +| Nature of address indicator | " national (significant) number " | hi-targeted-to-uri | Add CC (of the country where the MGCF is located) to Redirecting number Address Signals to construct E.164 number in URI. | +| | " international number " | | Map complete Redirecting number Address Signals to E.164 number in URI. | +| Address Signals | If NOA is " national (significant) number " then the format of the Address Signals is:
NDC + SN
If NOA is " international number " then the format of the Address Signals is:
CC + NDC + SN | hi-targeted-to-uri | Addr-spec
"+" CC NDC SN mapped to userinfo portion of SIP URI. (NOTE 5)
Add "user=phone". | +| Redirecting number | APRI | Privacy header field that corresponds to the penultimate hi-targeted-to-uri entry in the History-Info header | Priv-value | +| | " presentation restricted " | | " history " | +| | " presentation allowed " | | Privacy header field absent or " none " (NOTE 3) | +| Redirection information | Redirecting indicator | Privacy header field that corresponds to the penultimate hi-targeted-to-uri entry in the History-Info header | Priv-value | +| | Call diverted | | Privacy header field absent or " none " (NOTE 4) | +| | Call diverted, all redirection information presentation restricted | | " history " | +| Redirection information | Redirection counter
1 | hi-index and "mp" header field parameter (NOTE 7) | Number of diversions is shown to the number of levels in hi-index
Index for Original called number = 1
Index for Called party number = 1.1 and addition "mp=1" | +| | 2 | | Index for Original called number = 1
Index for Redirecting number = 1.1 and addition of "mp=1"
Index for Called party number = 1.1.1 and addition of "mp=1.1" | +| | N | | Index for Original called number = 1
Placeholder History entry with Index = 1.1 and addition of "mp=1"
...
Fill up
...
Index for Redirecting number = 1.
[(N-1)* ".1"] and addition of "mp"
header field parameter set to the hi-index value of the hi-targeted-to-uri | + +| ISUP Parameter or IE | Derived value of parameter field | SIP component | Value | +|-------------------------|--------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | that precede.
Index for Called party number = 1.N* ".1" (e.g. N=3 → 1.1.1.1) and addition of mp=1.[(N-1)*].1 | +| Redirection information | Redirecting reason and Original redirection reason (NOTE 1) | hi-targeted-to-uri; "cause" URI parameter, as defined in IETF RFC 4458 [113].
The Redirecting reason shall be mapped to the last hi-targeted-to-uri.
If the redirection counter is 2 or higher, the Original redirection Reason shall be mapped to the second hi-targeted-to-uri.
If the redirection counter is 3 or higher, for each hi-targeted-to-uri following a placeholder History-Info hi-entry the value "404" shall be taken (NOTE 2) | cause value | +| | unknown/not available | | 404 | +| | unconditional | | 302 | +| | User Busy | | 486 | +| | No reply | | 408 | +| | Deflection during alerting | | 487 | +| | Deflection immediate response | | 480 | +| | Mobile subscriber not reachable | | 503 | +| Called party number | See Redirecting number
Nature of address indicator and Address signal | History-Info header field see hi-targeted-to-uri | URI of the last hi-targeted-to-uri entry of History-Info header field | +| Original called number | See Redirecting number
Nature of address indicator and Address signal | History-Info header field see hi-targeted-to-uri | URI of first hi-targeted-to-uri entry of History-Info header field (NOTE 6, NOTE 9)
IF the Original called number is available:
set to the value of the Original called number
ELSE
IF the Redirection counter equals 1 AND the Redirecting number is available,
set to the value of the Redirecting number
ELSE
set to the Unknown User Identity (NOTE 10) | +| Original called number | APRI | Privacy header field of the first hi-targeted-to-uri entry of History-Info header | Priv-value | +| | "presentation restricted" | | "history" | +| | "presentation allowed" | | Privacy header field absent or "none" | + +| ISUP Parameter or IE | Derived value of parameter field | SIP component | Value | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|---------------|-------| +| NOTE 1: Original redirection reason contains only the "unknown/not available" value.
NOTE 2: For all History-Info hi-entries except the first one a "cause" URI parameter as defined in IETF RFC 4458 [113] has to be included.
NOTE 3: If the Redirecting indicator has the value " Call diverted, all redirection information presentation restricted ", the privacy value " history " shall be set.
NOTE 4: If the Redirecting number APRI has the value " presentation restricted ", the privacy value " history " shall be set.
NOTE 5: Used URI scheme shall be SIP URI. The "cause" URI parameter cannot be added if hi-targeted-to-uri is a tel URI.
NOTE 6: The used URI scheme can be tel URI or SIP URI since the first hi-targeted-to-uri entry of the History-Info header field does not contain the "cause" URI parameter.
NOTE 7: The hi-target-param defined in IETF RFC 7044 [91] defines the "mp" as a header field parameter that contains the value of the hi-index in the hi-entry with an hi-targeted-to-uri that reflects the Request-URI that was retargeted, thus identifying the "mapped from" target. Since the hi-entries are created based on the redirection counter to reflect the diverting/diverted-to entries, the hi-target-param "mp" header field parameter shall be present in each entry except the first one.
NOTE 8: If the Original called number parameter is not available and if the value of the Redirecting counter is equal to one, the Redirecting number parameter is used for the first hi-targeted-to-uri entry of the History-Info header field.
NOTE 9: If a further SIP to ISUP interworking occurs, parameters not present in the original message can then be included.
NOTE 10: The "History-Info" header field may contain an "Unknown User Identity". An "Unknown User Identity" includes information that does not point to the served user and indicates that the user's identity is unknown. The encoding of the "Unknown User Identity" shall be as defined in 3GPP TS 23.003 [74]. | | | | + +### 7.5.4.3 Interworking at the I-MGCF + +**Table 7.5.4.3.1: Mapping of SIP to ISUP messages** + +| Message received from SIP | Message send to BICC/ISUP | +|---------------------------|---------------------------| +| INVITE request | IAM | + +**Table 7.5.4.3.2: Mapping of History-Info header field to ISUP Redirecting number** + +| Source SIP header field and component | Source Component value | Redirecting number | Derived value of parameter field | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| In History-Info SIP header field, hi-targeted-to-uri in hi-entry having a hi-index that match the "mp" header field parameter value of the last hi-entry containing an "mp" header field parameter and a "cause" URI parameter, as defined in IETF RFC 4458 [113]. (NOTE 1) (NOTE 3) | | Redirecting number | | +| hi-targeted-to-uri appropriate global number portion of the URI, assumed to be in form "+" CC + NDC + SN | CC | Nature of address indicator | If CC is equal to the country code of the country where MGCF is located AND the next ISUP node is located in the same country, then set to " national (significant) number " else set to " international number " | +| | CC, NDC, SN | Address signals | If NOA is " national (significant) number " then set to NDC + SN.
If NOA is " international number " then set to CC + NDC + SN | +| Privacy header field or/and priv-value component of the hi-entry in History-Info header field (NOTE 2) | | APRI | If the priv-value " history " or " session " or " header " is received within the Privacy header field or if the priv-value " history " is received within the "headers" component of the hi-targeted-to-uri in hi-entry before last hi-entry containing a "cause" URI parameter then " presentation restricted " shall be set.
Otherwise, " presentation allowed " shall be set. | + +NOTE 1: If the SIP URI doesn't contain "*user=phone*", mapping to redirecting number is impossible, therefore no need to generate Redirecting number. + +NOTE 2: It is possible that an entry of the History-Info header field itself is marked as restricted or the whole History-Info header. + +NOTE 3: The hi-target-param parameter set to "mp" as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed and appears in the hi-targeted-to-uri. In case of interworking with networks not supporting IETF RFC 7044 [91] the "mp" header field parameter may not appear. If the "mp" header field parameter is missing in the last hi-entry containing a "cause" URI parameter as defined in IETF RFC 4458 [113], the hi-entry to use is the entry just before. + +**Table 7.5.4.3.3: Mapping of History-Info header to ISUP Redirection information** + +| Source SIP header field and component | Source Component value | Redirection information | Derived value of parameter field | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| Privacy header field and priv-value of hi-entry having a hi-index that match the "mp" header field parameter value of the last hi-entry containing an "mp" header field parameter and a "cause" URI parameter as defined in IETF RFC 4458 [113] of the History-Info header field. (NOTE 3) | "history" or "session" or "header" for the Privacy header field or for the hi-targeted-to-uri entry | Redirecting indicator | Call diverted, all redirection information presentation restricted | +| | Privacy header field and the privacy component of the hi-targeted-to-uri entry either absent or "none" | | Call diverted | +| | | Original redirection reason | Unknown/not available | +| Cause value in the last hi-targeted-to-uri containing a "cause" URI parameter as defined in IETF RFC 4458 [113] (NOTE 3) | Cause parameter value | Redirecting reason | Redirecting reason | +| | 404 | | Unknown/not available | +| | 302 | | Unconditional | +| | 486 | | User busy | +| | 408 | | No reply | +| | 480 | | Deflection immediate response | +| | 487 | | Deflection during alerting | +| | 503 | | Mobile subscriber not reachable | +| History-Info header field | | Redirection counter | number of History-Info hi-entry(ies) containing a "cause" URI parameter with value as listed as cause parameter value in this table (NOTE 1, NOTE 2) | + +NOTE 1: If the determined number of redirection in SIP exceeds the ISUP maximum parameter value, the MGCF shall set the Redirection counter to its maximum value. For instance, in ISUP ITU-T Q.763 [4], the Redirection counter parameter cannot exceed 5. + +NOTE 2: The Redirection counter value will be incremented regardless of the SIP URI format. + +NOTE 3: The hi-target-param parameter set to "mp" as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed and appears in the hi-targeted-to-uri. In case of interworking with networks not supporting IETF RFC 7044 [91] the "mp" header field parameter may not appear. If the "mp" header field parameter is missing in the last hi-entry containing a "cause" URI parameter as defined in IETF RFC 4458 [113], the hi-entry to use is the entry just before. + +**Table 7.5.4.3.4: Mapping of History-Info header field to ISUP Original called number** + +| Source SIP header field and component | Source Component value | Original called number | Derived value of parameter field | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Numbering Plan Indicator | "ISDN (Telephony) numbering plan (Recommendation E.164)" | +| hi-targeted-to-uri of hi-entry having a hi-index that match the "mp" header field parameter value of the first hi-targeted-to-uri containing an "mp" header field parameter and a "cause" URI parameter, as defined in IETF RFC 4458 [113]; the global number portion of the URI, is assumed to be in form "+" CC + NDC + SN (NOTE 1) (NOTE 3) | CC | Nature of address indicator | If CC is equal to the country code of the country where MGCF is located AND the next ISUP node is located in the same country, then set to " national (significant) number " else set to " international number " | +| | CC, NDC, SN | Address signals | If NOA is " national (significant) number " then set to NDC + SN.
If NOA is " international number " then set to CC + NDC + SN | +| priv-value component in History-Info header field of the History-Info header field entry as defined above in this table (NOTE 2) | " history " or " session " or " header " | APRI | " presentation restricted " | +| | Privacy header field absent or " none " | | " presentation allowed " | + +NOTE 1: If it is SIP URI and doesn't contain "*user=phone*", mapping to Original called number is impossible, therefore no need to generate Original called number. + +NOTE 2: It is possible that an entry of the History-Info header field itself is marked as restricted or the whole History-Info header. + +NOTE 3: The hi-target-param parameter set to "*mp*" as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed and appears in the hi-targeted-to-uri. In case of interworking with networks not supporting IETF RFC 7044 [91] the "*mp*" header field parameter may not appear. If the "*mp*" header field parameter is missing in the first hi-entry containing a "*cause*" URI parameter as defined in IETF RFC 4458 [113], the hi-entry to use is the hi-entry preceding the first hi-entry containing the "*cause*" URI parameter. + +**Table 7.5.4.3.5: Mapping of INVITE to IAM** + +| INVITE | | IAM | | +|---------------------------|---------------------|-------------------------|---------------------| +| History-Info header field | See table 7.5.4.3.2 | Redirecting number | See table 7.5.4.3.2 | +| History-Info header field | See table 7.5.4.3.3 | Redirection information | See table 7.5.4.3.3 | +| History-Info header field | See table 7.5.4.3.4 | Original called number | See table 7.5.4.3.4 | + +**Table 7.5.4.3.6: Mapping of ISUP to SIP Messages** + +| ←Message sent to SIP | ←Message Received from BICC/ISUP | | +|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| +| 181 (Being forwarded) | ACM no indication with Redirection number and Call diversion information parameters (CFU, CFB, Cdi) | See table 7.5.4.3.8 | +| 180 (Ringing) | ACM indicating ringing, oBCi: " Call diversion may occur " (CFNR, Cda) | See subclause 7.2.3.1.4 | +| 181 (Being forwarded) | CPG indicating progress or subsequent diversion indicated in the CPG with Redirection number and Call diversion information parameters (CFNR, Cda) | See table 7.5.4.3.9 | +| 180 (Ringing) | CPG indicating ringing and Redirection number restriction parameter | See table 7.5.4.3.10 | +| 200 (OK) | ANM and Redirection number restriction parameter | See table 7.5.4.3.11 | + +**Table 7.5.4.3.7: Mapping of ISUP Redirection number restriction to History-Info header field** + +| Redirection number restriction | Derived value of parameter field | SIP component | Value | +|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|------------------------------------------------| +| Presentation restricted indicator | " Presentation restricted " | privacy "headers" component of the hi-targeted-to-uri | " history " | +| | " presentation allowed " or absent AND any previously received notification subscription options was NOT " presentation not allowed " AND was NOT " presentation allowed without redirection number " | | Privacy header field absent or " none " | + +**Table 7.5.4.3.8: Mapping of ACM (Call Is Being Forwarded) response** + +| ISUP Parameter | Derived value of parameter field | SIP component | Value | +|-----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| Generic notification indicator
Notification indicator | Call is diverting | | | +| Redirection number | | History-Info header field with one hi-entry and the hi-target-param "mp" header field parameter | hi-targeted-to-uri: | +| Nature of address indicator: | " national (significant) number " | hi-targeted-to-uri | Add CC (of the country where the MGCF is located) to Redirection number Address Signals to construct E.164 number in URI. | +| | " international number " | | Map complete Redirection number Address Signals to E.164 number in URI. | +| Address Signals | If NOA is " national (significant) number " then the format of the Address Signals is:
NDC + SN
If NOA is " international number " then the format of the Address Signals is:
CC + NDC + SN | hi-targeted-to-uri | Addr-spec
"+" CC NDC SN mapped to userinfo portion of SIP URI. (NOTE 2)
Add "user=phone". | +| Call diversion information | Redirecting reason | IETF RFC 4458 [113] | cause value | +| | Unknown | "cause" URI parameter in the hi-targeted-to-uri (NOTE 1) | 404 | +| | Unconditional | | 302 | +| | User busy | | 486 | +| | No reply | | 408 | +| | Deflection immediate response | | 480 | +| | Deflection during alerting | | 487 | +| | Mobile subscriber not reachable | | 503 | +| | Notification subscription options | privacy "headers" component of the hi-targeted-to-uri (NOTE 1) | | +| | unknown | | Escaped Privacy value is set according to the rules of 3GPP TS 24.604 [60] subclause 4.5.2.6.4 item c | +| | presentation not allowed | | A 181 Being Forwarded shall not be sent | +| | presentation allowed with redirection number | | Escaped Privacy value is set according to the rules of 3GPP TS 24.604 [60] subclause 4.5.2.6.4 item c | +| | presentation allowed without redirection number | | Escaped Privacy value is set according to the rules of 3GPP TS 24.604 [60] subclause 4.5.2.6.4 item c | + +NOTE 1: Needs to be stored for a possible inclusion into subsequent messages. + +NOTE 2: Used URI scheme shall be SIP URI. The "cause" URI parameter cannot be added if hi-targeted-to-uri is a tel URI. + +Table 7.5.4.3.9: Mapping of CPG & 181 (Call Is Being Forwarded) response + +| ISUP Parameter | Derived value of parameter field | SIP component | Value | +|-----------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| Event information
Event Indicator | PROGRESS | | | +| Generic notification indicator
Notification indicator | Call is diverting | | | +| Redirection number | | History-Info header field with one hi-entry and the hi-target-param "mp" header field parameter | hi-targeted-to-uri: | +| Nature of address indicator | " national (significant) number " | hi-targeted-to-uri | Add CC (of the country where the MGCF is located) to Redirection number Address Signals to construct E.164 number in URI. | +| | " international number " | hi-targeted-to-uri | Map complete Redirection number Address Signals to E.164 number in URI. | +| Address Signals | If NOA is " national (significant) number " then the format of the Address Signals is:
NDC + SN
If NOA is " international number " then the format of the Address Signals is:
CC + NDC + SN | hi-targeted-to-uri | Addr-spec
"+" CC NDC SN mapped to userinfo portion of SIP URI.
(NOTE 2)
Add "user=phone". | +| Call diversion information | Redirecting reason | IETF RFC 4458 [113] | cause value | +| | Unknown | "cause" URI parameter in the hi-targeted-to-uri (NOTE 1) | 404 | +| | Unconditional | | 302 | +| | User busy | | 486 | +| | No reply | | 408 | +| | Deflection immediate response | | 480 | +| | Deflection during alerting | | 487 | +| | Mobile subscriber not reachable | | 503 | +| | Notification subscription options | privacy "headers" component of the hi-targeted-to-uri (NOTE 1) | | +| | unknown | | Escaped Privacy value is set according to the rules of 3GPP TS 24.604 [60] subclause 4.5.2.6.4 items c | +| | presentation not allowed | | A 181 Being Forwarded shall not be sent | +| | presentation allowed with redirection number | | Escaped Privacy value is set according to the rules of 3GPP TS 24.604 [60] subclause 4.5.2.6.4 items c | +| | presentation allowed without redirection number | | Escaped Privacy value is set according to the rules of 3GPP TS 24.604 [60] subclause 4.5.2.6.4 items c | + +NOTE 1: Needs to be stored for a possible inclusion into subsequent messages. + +NOTE 2: Used URI scheme shall be SIP URI. The "cause" URI parameter cannot be added if hi-targeted-to-uri is a tel URI. + +Table 7.5.4.3.10 addresses two separate conditions: the CPG is received from the diverting exchange in which case the Call diversion information parameter is included; and the CPG is received from the diverted-to exchange in which case the Call diversion information parameter is not included. Interworking for both conditions is shown. + +Table 7.5.4.3.10: Mapping of CPG < 180 (Ringing) response + +| ISUP Parameter | Derived value of parameter field | SIP component | Value | +|-------------------------------------------------------|--------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| +| Event information
Event Indicator | ALERTING | | | +| Redirection number | | History-Info header field with one hi-entry and the hi-target-param "mp" header field parameter | See table 7.5.4.3.8 | +| Call diversion information | Redirecting reason | IETF RFC 4458 [113]
"cause" URI parameter in the hi-targeted-to-uri (NOTE 1) | cause value | +| | Unknown | | 404 | +| | Unconditional | | 302 | +| | User busy | | 486 | +| | No reply | | 408 | +| | Deflection immediate response | | 480 | +| | Deflection during alerting | | 487 | +| | Mobile subscriber not reachable | | 503 | +| | Notification subscription options | | | +| | unknown | | Escaped Privacy value is set according to the rules of 3GPP TS 24.604 [60] subclause 4.5.2.6.4 item c | +| | presentation not allowed | privacy "headers" component of the hi-targeted-to-uri (NOTE 1) | The 180 Ringing response shall be sent without the History-Info header field included | +| | presentation allowed with redirection number | | Escaped Privacy value is set according to the rules of 3GPP TS 24.604 [60] subclause 4.5.2.6.4 item c | +| | presentation allowed without redirection number | | Escaped Privacy value is set according to the rules of 3GPP TS 24.604 [60] subclause 4.5.2.6.4 item c | +| If no Call diversion information parameter is present | | IETF RFC 4458 [113]
"cause" URI parameter in the hi-targeted-to-uri | Value stored from a previously received ACM or CPG. See tables 7.5.4.3.8 and 7.5.4.3.9. | +| | | privacy "headers" component of the hi-targeted-to-uri | Value stored from a previously received ACM or CPG. See tables 7.5.4.3.8 and 7.5.4.3.9. | +| Redirection number restriction (NOTE 2) | | | See table 7.5.4.3.7 | + +NOTE 1: Needs to be stored for a possible inclusion into subsequent messages. + +NOTE 2: This parameter may appear without call diversion information parameter and redirection number. In such cases, the O-MGCF shall send the previously sent and stored History-Info header field and set the priv-value in the History-Info header field as described in table 7.5.4.3.7. + +**Table 7.5.4.3.11: Mapping of ANM & 200 (OK) response (to INVITE request)** + +| ISUP Parameter | Derived value of parameter field | SIP component | Value | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------| +| Redirection number | | History-Info header field with one hi-entry and the hi-target-param "mp" header field parameter | See table 7.5.4.3.8 | +| | | IETF RFC 4458 [113] "cause" URI parameter in the hi-targeted-to-uri | Value stored from a previous received ACM or CPG. See tables 7.5.4.3.8 and 7.5.4.3.9. | +| Redirection number restriction (NOTE) | | | See table 7.5.4.3.7 | +| NOTE: This parameter may appear without Call diversion information parameter and Redirection number. In such cases, the O-MGCF shall send the previously sent and stored History-Info header field and set the priv-value in the History-Info header field as described in table 7.5.4.3.7. | | | | + +## 7.5.5 Communication Hold (HOLD) + +The mapping of Communication Hold supplementary service with Call Hold PSTN/ISDN Supplementary Service is the same mapping as described in clause 7.4.10. The Service itself is described within 3GPP TS 24.610 [65]. + +## 7.5.6 Conference call (CONF) + +### 7.5.6.1 General + +The protocol description of the CONF supplementary service is described in 3GPP TS 24.605 [61]. In this clause the interworking from the conference event package in accordance with IETF RFC 4575 [100] to the messages of the PSTN/ISDN CONF supplementary service is described. Note that an interworking from the PSTN/ISDN to the IMS is out of scope. + +### 7.5.6.2 Subscribing for the conference event package + +Based on local policy, the MGCF may subscribe for the conference event package on behalf of the PSTN/ISDN participant after the participant joins or is added to a conference. + +When the conference event package option is implemented, and one of the following events occurs at the MGCF: + +- a 200 (OK) response is received as a response to an initial INVITE request originated by the MGCF, where the Contact header field contains an "isfocus" parameter; or +- an ACK message is received which acknowledges a 200 (OK) response to the initial INVITE request, and the initial INVITE request is originated by the conferencing AS and contains an "isfocus" parameter in the Contact header field; + +then the following steps shall be performed: + +- 1) a SUBSCRIBE request shall be created according to IETF RFC 4575 [100], using the updated procedures from IETF RFC 6665 [138]; +- 2) the Request URI is set to the Contact address of the conferencing AS; +- 3) the P-Asserted-Identity header field, the From header field and the Privacy header field are set with the same value as: + - the P-Asserted-Identity header field, the From header field and the Privacy header field in the initial INVITE request originated by the MGCF; or + - the P-Asserted-Identity header field, the To header field and the Privacy header field in a 1xx or 2xx response sent by the MGCF to the initial INVITE request from the conferencing AS. + +### 7.5.6.3 Interworking the notification + +NOTE: There is a need to differentiate between the procedures of interworking for a full and a partial type of notification. + +When a full type of notification is received a check is made of the content. If the changes with respect a previous version of the notification have not been sent on to the PSTN/ISDN for this session, the MGCF shall perform an ISUP interaction towards the PSTN/ISDN. If the changes with respect a previous version of the notification have been sent to the PSTN/ISDN for this session, the MGCF shall not perform an ISUP interaction towards the PSTN/ISDN. + +When a partial notification is received then it is assumed that a value of a received notification has changed, so the MGCF performs an ISUP interaction towards the PSTN/ISDN, as follows: + +- Conference established: + +Upon the receipt of a conference information document with the
codec 1 | voice
codec 2 | +| RTP | TNL | +| UDP | | +| IP | | +| L2 | | +| L1 | L1 | + +| Mb +IM-MGW +Nb | + +Interworking arrow + +**Figure 31/1: IM CN subsystem to bearer independent CS network user plane protocol stack** + +### 8.1.1 Transcoder-less Mb to Nb Interworking + + + +| | | +|-----------------------------------------|-------| +| Transcoder-less user plane interworking | | +| RTP | Nb FP | +| UDP | | +| IP | L3 | +| L2 | L2 | +| L1 | L1 | + +Mb IM-MGW Nb + +Diagram of the IM CN subsystem to bearer independent CS network user plane protocol stack. The diagram shows a stack of protocols between the Mb and Nb interfaces, with an IM-MGW at the bottom. The stack consists of five layers: L1, L2, IP, UDP, and RTP. The top layer is labeled 'Transcoder-less user plane interworking'. The layers are grouped into two columns: the left column contains RTP, UDP, IP, L2, and L1; the right column contains Nb FP, L3, L2, and L1. The IM-MGW is shown as a box below the L1 layer, connected to both the Mb and Nb interfaces. + +**Figure 31/2: IM CN subsystem to bearer independent CS network user plane protocol stack (optional in the event the codecs on both sides are the same)** + +If no transcoder is inserted, the IM-MGW shall interwork the following procedures between the Nb and Mb interfaces. + +#### 8.1.1.1 Initialisation + +There is no need to interwork initialisation procedures between Nb and Mb interfaces see 3GPP TS 29.415 [26]. + +#### 8.1.1.2 Time alignment + +The purpose of the time alignment procedure on the Nb interface is to minimise the buffer delay in the RNC for downlink transmissions by adjusting the vocoder time reference within the network. No such procedure exists on the Mb interface, so the IM-MGW shall return NACK indication time alignment not supported according to 3GPP TS 29.415 [26]. + +#### 8.1.1.3 Rate control + +##### 8.1.1.3.1 General + +The rate control procedure signals to the peer entity the maximum rate among the currently allowed rates at which it can receive codec frames. Rate control only applies to AMR, AMR-WB and EVS codec configurations with multiple active modes. For the EVS codec, the rate control procedure also signals to the peer entity the maximum mode among the currently allowed modes at which it can receive codec frames. + +##### 8.1.1.3.2 Rate control for AMR and AMR-WB codecs + +For AMR and AMR-WB codecs: + +- On the Nb interface, IuFP provides for rate control via the exchange of RATE CONTROL and RATE CONTROL ACK PDUs +- On the Mb interface, IETF RFC 4867 [23] provides for in-band rate control via the Codec Mode Request (CMR) field of every codec frame (Speech or SID) and CMR-Only frames. +- Interworking of rate control procedures at an IM-MGW between an Mb interface and a corresponding Nb interface only applies when the IM-MGW bridges compatible codec configurations between the interfaces without applying a transcoding function. +- An IM-MGW receiving a CMR from an Mb interface shall initiate the IuFP rate control procedure on the corresponding Nb interface. + +- An IM-MGW receiving a rate control request on an Nb interface shall adjust the CMR field of outgoing speech frames on the corresponding Mb interface. + +##### 8.1.1.3.3 Rate and Mode control for the EVS codec + +For the EVS codec: + +- On the Nb interface, CMR for EVS (EVS-CMR) as specified in 3GPP TS 26.453 [152] subclause 4.5 provides for in-band rate and mode control via the Codec Mode Request (CMR) field of every codec frame (Speech or SID) and CMR-Only frame. +- On the Mb interface, EVS-CMR as specified in 3GPP TS 26.445 [147] subclause A.2.2.1.1 provides for in-band rate and mode control via the Codec Mode Request (CMR) field of the codec frame in RTP. Alternatively RTCP-APP packets may be used with corresponding control commands as specified in 3GPP TS 26.114 [104]. The rate and mode control on the Mb interface depends on the SDP offer/answer procedure. It may also be disabled, in which case transcoding is mandatory. +- Interworking of rate control procedures at an IM-MGW between an Mb interface and a corresponding Nb interface only applies when the IM-MGW bridges compatible codec configurations between the interfaces without applying a transcoding function. +- An IM-MGW receiving an EVS-CMR from an Nb interface may filter and modify the EVS-CMR contents based on configured policies and shall perform one of the following alternatives: + - 1) if CMR in RTP is required in every RTP packets on the Mb interface (cmr=1), include the resulting contents into the EVS-CMR field of the corresponding outgoing frame or CMR-Only frame on the Mb interface; + - 2) if CMR in RTP is enabled "on demand" on the Mb interface (cmr=0 or omitted), include the resulting contents into the EVS-CMR field of the outgoing codec frame or CMR-Only frame on the corresponding Mb interface only if it is different from the previously sent EVS-CMR value, and send the new EVS-CMR value at least 3 times within the next 100 ms to provide a minimum of error robustness, if necessary using also additional CMR-Only frames in speech pauses; + - 3) if CMR in RTP is disabled on the Mb interface (cmr=-1) and if RTCP-APP is enabled on the Mb interface, translate the resulting contents into a corresponding RTCP-APP command and send it at least 3 times within the next 100 ms to provide a minimum of error robustness, if the resulting RTCP-APP command is different from the previously sent RTCP-APP command; or + - 4) if CMR in RTP is disabled on the Mb interface (cmr=-1) and if RTCP-APP is disabled on the Mb interface, applying a transcoding function. In this case the rate and mode control on the Nb interface is terminated in the IM-MGW. +- An IM-MGW receiving an EVS-CMR on an Mb interface may filter and modify the EVS-CMR contents based on configured policies and shall include the resulting contents into the EVS-CMR field of the outgoing codec frame or CMR-Only frame on the corresponding Nb interface. +- The rules by which the IM-MGW may filter and modify the EVS-CMR contents consist of the following: + - 1) The IM-MGW shall not modify the EVS-CMR to increase the maximum bit rate; + - 2) If the IM-MGW observes the incoming stream of speech frames or packets and determines that a lower EVS mode is more appropriate, the IM-MGW may modify the EVS-CMRs sent in the opposite direction of the observed speech flow; + - 3) If the IM-MGW modifies the EVS-CMR to decrease the maximum bit rate and the resulting maximum bit rate no longer support the originally requested maximum audio bandwidth, then the maximum audio bandwidth may be reduced by the IM-MGW to the next lower one that fits to the reduced maximum bit rate; + - 4) The IM-MGW shall not modify the EVS-CMR in a way that results in a change of the major operation mode (EVS primary mode or EVS AMR-WB IO mode); + +NOTE: The IM-MGW can be forced to change the major operation mode of an incoming EVS-CMR when interworking between EVS and AMR-WB, during handover or after handover. + +- 5) When channel-aware mode is used, if the IM-MGW observes the incoming stream of speech frames or packets and determines that other channel-aware mode parameters are more appropriate, the IM-MGW may modify the EVS-CMRs, flowing in the opposite direction of the observed speech flow to change the received channel-aware offset to a bigger one (e.g. from 2 to 3) and the received channel-aware depth to a lower, more robust one; +- 6) When channel-aware mode is used, the IM-MGW shall not reduce the received channel-aware offset or modify the received channel-aware depth a less robust one; +- 7) The IM-MGW should not block the channel-aware mode; +- 8) The IM-MGW may modify the EVS primary mode in the received EVS-CMR to the EVS Variable Bit Rate mode. + +##### 8.1.1.3.4 Interworking of rate control between compatible AMR-WB and EVS codec configurations + +The EVS codec includes the EVS AMR-WB IO major operation mode and is therefore TrFO-compatible to the AMR-WB codec, if the mode-set and mode-change-period parameters are TrFO-compatible. For example, AMR-WB on one IM-MGW termination and EVS on the other IM-MGW termination are TrFO-compatible codecs, if the mode-set parameters are TrFO-compatible and mode-change-period=2 on both sides. + +If the IM-MGW bridges compatible EVS codec configurations and AMR-WB codec configurations: + +- If the codec of the incoming termination is EVS and the codec of the outgoing termination is AMR-WB, then the rate control procedure for AMR-WB shall apply at the outgoing termination, with the maximum rate equal to or lower than the maximum rate received in the EVS-CMR. The IM-MGW shall map received EVS-CMRs to the selected mode-set of the outgoing AMR-WB termination. +- If the codec of the incoming termination is AMR-WB and the codec of the outgoing termination is EVS, then the rate control procedure for AMR-WB shall apply on the incoming termination and shall determine the maximum rate included in the EVS-CMR sent by the IM-MGW. The IM-MGW shall request the EVS AMR-WB IO major operation mode in the outgoing EVS-CMR. +- The IM-MGW may filter and modify the CMR contents according to the following rules: + - 1) The IM-MGW shall not modify the EVS-CMR to increase the maximum bit rate; + - 2) If the IM-MGW observes the incoming stream of speech frames or packets and determines that a lower EVS mode is more appropriate, the IM-MGW may modify the EVS-CMRs sent in the opposite direction of the observed speech flow. + +If the IM-MGW bridges EVS codec configurations and AMR-WB codec configurations which are not compatible, the IM-MGW shall apply transcoding and shall handle the independent rate and mode control procedures towards the incoming and the outgoing networks. + +##### 8.1.1.3.5 Interworking between rate control and RTCP-APP-CMR messages for MTSI + +An IM-MGW may support the MTSI service defined in 3GPP TS 24.173 [88] and may then support codecs according to 3GPP TS 26.114 [104]. + +NOTE 1: Alternative codec specifications for the MTSI service are listed in 3GPP TS 24.173 [88]. + +If the IM-MGW supports the MTSI service with the codecs according to 3GPP TS 26.114 [104] the IM-MGW should support reception of RTCP-APP-CMR messages as specified in the clause 10.2.1 of 3GPP TS 26.114 [104] which can be sent by a MTSI client in the terminal. If the IM-MGW is in TrFO then RTCP-APP-CMR messages should be translated to the appropriate rate control method on the CS side (e.g. IuFP rate control or RTP based CMR) in the same way as for an RTP based CMR, described in the preceding subclauses. + +NOTE 2: When the IM-MGW is transcoding at the Mb interface then any RTCP-APP-CMR requests received from the MTSI client in the terminal when the IM-MGW is transcoding will result in a change to DL codec mode towards the MTSI client terminal. + +#### 8.1.1.4 Frame quality indication + +The Nb interface signals frame quality with the Frame Quality Classification (FQC) field of each speech frame PDU. See 3GPP TS 26.102 [50] and 3GPP TS 29.415 [26] for details. The FQC may have possible values: 0=frame\_good; 1=frame\_bad; 2=frame\_bad\_due\_to\_radio; and 3=spare. The Mb interface signals frame quality with the Q bit (frame quality indicator) field of each speech frame, as defined in IETF RFC 4867 [23]. The Q bit may have values: 1=speech\_good; and 0=speech\_bad or sid\_bad. + +Tables 24a and 24b provide the mapping between Mb and Nb interfaces. + +**Table 24a: Mapping of Mb (Q bit) onto Nb (FQC)** + +| Mb - Qbit | Mb - FT | Nb - FQC | +|-----------|---------|----------| +| 1 | X | 0 | +| 0 | X | 1 | + +**Table 24b: Mapping Nb onto Mb** + +| Nb - FQC | Mb - Qbit | Mb - FT | +|----------|-----------|---------| +| 0 | 1 | NC | +| 1 | 0 | NO DATA | +| 2 | 0 | NC | + +#### 8.1.1.5 Framing + +Even when the IM-MGW bridges compatible codec configurations between the Nb and Mb interfaces, the IM-MGW shall perform translation between the frame formats defined for the two interfaces, since all codec configurations have different framing procedures for the two interfaces. The framing details for Nb are defined in 3GPP TS 26.102 [50] and 3GPP TS 29.415 [26], although they do not describe the framing for ITU-T codecs other than G.711. The framing details for Mb are defined in IETF RFC 4867 [23], IETF RFC 3550 [51], IETF RFC 3551 [52] and IETF RFC 3555 [53]. + +#### 8.1.1.6 Transcoding + +Transcoding at the IM-MGW is avoided when the IM-MGW bridges compatible codec configurations between the Nb and Mb interfaces. Otherwise transcoding is necessary, which eliminates the need to interwork other user plane procedures between the interfaces. + +#### 8.1.1.7 Discontinuous transmission + +When the IM-MGW bridges compatible codec configurations between the Nb and Mb interfaces, the DTX procedures are normally interworked transparently by translating between the framing formats on the interfaces. All the ITU-T, AMR, AMR-WB and EVS codecs have configurations that are compatible between the Mb and Nb interfaces. + +For the AMR, AMR-WB and EVS codecs, DTX is always enabled on the CS radio Interface in the uplink direction and the transport channel for DTX in the downlink is always provided. + +If the IMS side requires interworking without DTX in its media-receive direction, then the IM-MGW shall insert transcoding in this direction. The IMS side may apply in its media-sending direction DTX or not, the CS side is prepared for both alternatives without transcoding. + +#### 8.1.1.8 Timing and sequence information + +The IM-MGW shall always correct out-of-sequence delivery between Nb and Mb interfaces, either by re-ordering frames, or by dropping frames that are out of sequence. + +When the IuFP frame numbers are based on time and if the IM-MGW bridges compatible codec configurations between the Nb and Mb interfaces, it shall either correct jitter before forwarding PDUs or interwork the RTP timestamp (see RFC 3550 [51]) with the IuFP Frame Number (see 3GPP TS 29.415 [26]) so that both the RTP timestamp and IuFP frame number similarly reflect the nominal sampling instant of the user data in the packet. + +NOTE: Correcting jitter may cause additional delay. + +The RTP sequence number (see RFC 3550 [51]) is handled independently on Mb, i.e. it is not interworked with the IuFP Frame Number (see 3GPP TS 29.415 [26]). + +## 8.2 Interworking between IM CN subsystem and TDM-based CS network + +It shall be possible for the IM CN subsystem to interwork with the TDM based CS networks (e.g. PSTN, ISDN or CS domain of a PLMN). Figure 32 describes the user plane protocol stack to provide the particular interworking. + + + +Figure 32: IM CN subsystem to TDM-based CS network user plane protocol stack. The diagram shows a protocol stack for the IM-MGW. On the left side, the stack consists of AMR, RTP, UDP, IP, L2, and L1 layers. On the right side, the stack consists of G.711 PCM Coding, TDM CS Bearer Channel, and L1 layers. A 'Transcoding' label with a double-headed arrow is positioned above the AMR and G.711 PCM Coding layers, indicating the conversion between them. The bottom L1 layer is connected to the Mb interface on the left and the IM-MGW box on the right. + +Figure 32: IM CN subsystem to TDM-based CS network user plane protocol stack + +## 8.3 Transcoding requirements + +The IM CN subsystem supports the AMR codec as the native codec for basic voice services. For IM CN subsystem terminations, the IM MGW shall support the transport of AMR over RTP according to IETF RFC 4867 [23]. The MGCF shall support the options of IETF RFC 4867 [23] listed within subclause 12.3.1 of 3GPP TS 26.114 [104]. + +It shall be possible for the IM CN subsystem to interwork with the CS networks (e.g. PSTN, ISDN or a CS domain of a PLMN) by supporting AMR to G.711 transcoding (see ITU-T Recommendation G.711 [1]) in the IM-MGW. The IM-MGW may also perform transcoding between AMR and other codec types supported by CS networks. + +## 8.4 Diffserv code point requirements + +The IM-MGW shall perform DiffServ Code Point (DSCP) markings (see RFC 2474 [21]) on the IP packets sent towards the IM CN subsystem entity like UE or MRFP across the Mb interface to allow DiffServ compliant routers and GGSNs to schedule the traffic accordingly. + +The IETF Differentiated Services architecture (see RFC 2475 [22]) shall be used to provide QoS for the external bearer service. + +The DSCP shall be operator configurable. + +## 8.5 DTMF handling + +When sending DTMF inband towards the CS network, the MGW shall comply with the encoding requirements in 3GPP TS 23.014 [103]; in particular the requirements for the minimum length of a tone and for the minimum gap between two subsequent tones shall be ensured. + +When detecting DTMF digits arriving from the CS side, the MGW shall comply with 3GPP TS 23.014 [103] (by checking that a valid digit with minimum duration and minimum gap has been received) before initiating an RTP Telephony Event to the IMS interface. + +When sending DTMF towards the IMS side according to the IETF RFC 4733 [105] RTP Payload format, the MGW shall comply with the DTMF encoding requirements of Annex G.2 of 3GPP TS 26.114 [104], in particular the minimum duration of 65ms shall be ensured. It is optional if the RTP Telephony Event is sent as a number of "RTP Events" with interim durations (e.g. every 20ms or 40ms in line with the speech packetisation time) or as a single "RTP Event" with the at least 65ms duration. + +# 9 MGCF - IM-MGW Interaction + +## 9.1 Overview + +The MGCF shall control the functions of the IM-MGW, which are used to provide the connection between media streams of an IP based transport network and bearer channels from a CS network. + +The MGCF shall interact with the IM-MGW across the Mn reference point. The MGCF shall terminate the signalling across the Mn interface towards the IM-MGW and the IM-MGW shall terminate the signalling from the MGCF. + +The signalling interface across the Mn reference point shall be defined in accordance with ITU-T Recommendation H.248.1 [2] and shall conform to 3GPP specific extensions as detailed in 3GPP TS 29.332 [15]. + +The present specification describes Mn signalling procedures and their interaction with BICC/ISUP and SIP signalling in the control plane, and with user plane procedures. 3GPP TS 29.332 [15] maps these signalling procedures to H.248 messages and defines the required packages and parameters. + +## 9.2 Mn signalling interactions + +The following paragraphs describe the Mn interface procedures triggered by SIP and BICC signalling relayed in MGCF. + +The SIP signalling occurring at the MGCF is described in 3GPP TS 24.229 [9]. + +All message sequence charts in this clause are examples. + +### 9.2.1 Network model + +Figure 33 shows the network model, applicable to BICC and ISUP cases. The broken line represents the call control signalling. The dotted line represents the bearer control signalling (if applicable) and the user plane. The MGCF uses one context with two terminations in the IM-MGW. The termination T1 is used towards the IM CN subsystem entity and the bearer termination T2 is used for the bearer towards the succeeding CS network element. + + + +The diagram illustrates the network model. On the left, there are two stacked boxes. The top box is labeled 'MGCF' and contains two curved arrows pointing towards each other. The bottom box is labeled 'IM-MGW' and contains two curved arrows pointing towards each other, with 'T1' and 'T2' labels above them respectively. A solid blue vertical line connects the MGCF box to the IM-MGW box. To the right is a large box labeled 'CS NETWORK'. A green dashed line connects the MGCF box to the CS NETWORK box. A red dotted line connects the IM-MGW box to the CS NETWORK box. The red dotted line passes through the IM-MGW box, specifically through the 'T1' and 'T2' terminations. + +Figure 33: Network model diagram showing MGCF and IM-MGW connected to a CS NETWORK. + +Figure 33: Network model + +### 9.2.2 Basic IM CN subsystem originated session + +#### 9.2.2.1 BICC forward bearer establishment + +##### 9.2.2.1.1 IM-MGW selection + +The MGCF shall select an IM-MGW for the bearer connection before it performs the CS network side bearer establishment. This may happen either before sending the IAM or after receiving the APM message (signal 5 or signal 6 in figure 34). In the latter case, the IM-MGW selection may be based on a possibly received MGW-id from the succeeding node. + +##### 9.2.2.1.2 CS network side bearer establishment + +The MGCF shall either select bearer characteristics or request the IM-MGW to select and provide the bearer characteristics for the CS network side bearer connection before sending the IAM. In the latter case the MGCF shall use the Prepare Bearer procedure, not shown in figure 34, to request the IM-MGW to select the bearer characteristics. After the succeeding node has provided a bearer address and a binding reference in the APM, the MGCF shall use the Establish Bearer procedure to request the IM-MGW to establish a bearer towards the destination CS-MGW. The MGCF shall provide the IM-MGW with the bearer address, the binding reference and the bearer characteristics (signal 7 in figure 34). + +##### 9.2.2.1.3 IM CN subsystem side termination reservation + +On receipt of an initial INVITE (signal 1 in figure 34) the MGCF shall initiate the Reserve IMS Connection Point and Configure Remote Resources procedure (signal 3 and 4 in figure 34). From the received SDP and local configuration data the MGCF: + +- Shall send the appropriate remote codec(s), the remote UDP port and the remote IP address to the IM-MGW. The remote UDP port and IP address refer to the destination of user plane data sent towards the IM CN subsystem. The remote codec(s) are the codec(s) the IM-MGW may select for user plane data sent towards the IM CN subsystem. +- Shall indicate to the IM-MGW the appropriate local codec(s) and request a local IP address and UDP port. The local IP address and UDP port are used by the IM-MGW to receive user plane data from the IM CN subsystem. The local codec(s) are the codec(s) the IM-MGW may select to receive user plane data from the IM CN subsystem. +- If DTMF support together with speech support is required, the reserve value indicator shall be set to "true". +- May indicate that IP interface type is for MboIP. + +The IM-MGW + +- Shall reply to the MGCF with the selected local codec(s) and the selected remote codec(s) and the selected local UDP port and IP address. +- Shall reserve resources for those codec(s). + +The MGCF shall send the local codec(s), UDP port and IP address to the IMS in the Session Progress (signal 9 in figure 34). + +##### 9.2.2.1.4 IM CN subsystem side session establishment + +Dependent on what the MGCF receives in the PRACK message (signal 10 in figure 34), the MGCF may initiate the Configure IMS Resources procedure. If no SDP is received, or if the received SDP does not contain relevant changes compared to the previous SDP sent to the IMS in signal 9 in figure 34, the procedure is not invoked. Otherwise the MGCF shall use the Configure IMS Resources procedure to provide to the IM-MGW: + +- The appropriate remote codec(s), the remote UDP port and the remote IP address. +- Optionally the appropriate local codec(s), UDP port and IP address. +- If DTMF support together with speech support is required, the reserve value indicator shall be set to "true". + +- May indicate that IP interface type is for MboIP. + +The IM-MGW shall: + +- Reply to the MGCF with the selected remote codec(s), +- Reply to the MGCF with the selected local codec(s) if the MGCF supplied local codec(s), +- Update the codec reservation and remote IP address and remote UDP port in accordance with the received information. + +The MGCF shall include the selected codec(s) and UDP port and IP address in a 200 OK (PRACK) (signal 11 in figure 34) sent back to the IMS. + +##### 9.2.2.1.5 Through-connection + +During the Prepare Bearer and Establish Bearer procedures, the MGCF shall either use the Change Through-Connection procedure to request the IM-MGW to backward through-connect the BICC terminations, or the MGCF shall use this procedure to both-way through-connect the BICC termination already on this stage (signal 7 in figure 34). During the Reserve IMS Connection Point procedure: + +- if the MGCF has been identified a call as an "ICS call" as specified in clause 7.3.3.1.2.12 the MGCF shall request the IM MGW to suspend sending media towards the IMS side by setting the through-connection of the IM CN subsystem side termination to "not through-connected" using the Change IMS Through Connection procedure (signal 3 in figure 34); and +- otherwise the MGCF shall use the Change IMS Through-Connection procedure to request the IM-MGW to backward through-connect the IMS termination (signal 3 in figure 34). + +When the MGCF receives a BICC ACM or CPG message with an UID action indicators parameter with the through-connection instruction indicator set to "*through-connect in both directions*" the MGCF shall request the IM-MGW to both-way through-connect the terminations using the Change IMS Through-Connection or Change Through-Connection procedures (signal 18 in figure 34), unless those terminations are already both-way through-connected. + +When the MGCF receives the BICC:ANM answer indication, it shall request the IM-MGW to both-way through-connect the termination using the Change Through-Connection or Change IMS Through-Connection procedures (signal 24 in figure 34), unless those terminations are already both-way through-connected. + +##### 9.2.2.1.6 Codec handling + +The IM-MGW may include a speech transcoder based upon the speech coding information provided to each termination. + +##### 9.2.2.1.7 Failure handling in MGCF + +If any procedure between the MGCF and the IM-MGW is not completed successfully the default action by the MGCF is to release the session, as described in clause 9.2.6. If the MGCF receives a Bearer Released procedure from the IM-MGW the default action by the MGCF is to release the session as described in clause 9.2.7. + +- NOTE: As an implementation option the MGCF may also decide for example to only release the resources in the IM-MGW that caused the failure, possibly select a new IM-MGW for the connection and continue the call establishment using new resources in the selected IM-MGW but such handling is outside of the scope of the present document. + +##### 9.2.2.1.8 Message sequence chart + +Figure 34 shows the message sequence chart for the IM CN subsystem originating session with BICC forward bearer establishment where the selection of IM-MGW is done before the sending of the IAM. In the chart the MGCF requests the seizure of an IM CN subsystem side termination. When the APM is received from the succeeding node, the MGCF requests the seizure of a CS network side bearer termination and the establishment of the bearer. When the MGCF receives an answer indication, it requests the IM-MGW to both-way through-connect the terminations. Dashed lines represent optional or conditional messages. + + + +``` + +sequenceDiagram + participant MGCF + participant IM-MGW + + Note left of MGCF: Reserve IMS Connection Point and Configure Remote Resource, Change IMS Through-Connection = backward + MGCF->>MGCF: 1. SIP: INVITE + MGCF-->>MGCF: 2. SIP: 100 Trying + MGCF->>IM-MGW: 3. H.248: ADD.req [Context ID = ?, Termination ID=?] + IM-MGW-->>MGCF: 4. H.248: ADD.resp [Context ID = C1, Termination ID = T1] + + Note left of MGCF: if SIP 100 rel is used + MGCF-->>MGCF: 9. SIP: 183 Session Progress + MGCF->>IM-MGW: 5. BICC: IAM + IM-MGW-->>MGCF: 6. BICC: APM + + Note left of MGCF: Establish Bearer, Change Through-Connection = both + MGCF->>IM-MGW: 7. H.248: ADD.req [Context ID = C1, Termination ID = ?] + IM-MGW-->>MGCF: 8. H.248: ADD.resp [Context ID = C1, Termination ID = T2] + Note right of IM-MGW: Bearer Establishment + + Note left of MGCF: if SIP 100 rel is used + MGCF-->>MGCF: 10. SIP: PRACK + MGCF-->>MGCF: 11. SIP: 200 OK (PRACK) + MGCF->>IM-MGW: 12. H.248: MOD.req [Context ID = C1, Termination ID = T1] + IM-MGW-->>MGCF: 13. H.248: MOD.resp [Context ID = C1, Termination ID = T1] + Note right of IM-MGW: Configure IMS Resources + + Note left of MGCF: Only if SIP Preconditions are used + MGCF-->>MGCF: 14. SIP: UPDATE + MGCF-->>MGCF: 15. SIP: 200 OK (UPDATE) + MGCF->>IM-MGW: 16. BICC: COT + IM-MGW-->>MGCF: 17. BICC: ACM + Note right of IM-MGW: Only if BICC continuity check and/or SIP Preconditions are used + + Note left of MGCF: Change IMS Through-Connection = both + MGCF->>IM-MGW: 18. H.248: MOD.req [Context ID=C1, Termination ID = T1] + IM-MGW-->>MGCF: 19. H.248: MOD.resp [Context ID = C1, Termination ID = T1] + Note right of IM-MGW: Only if BICC UID action indicates through-connect both directions Optional + + MGCF-->>MGCF: 20. SIP: 180 Ringing + MGCF-->>MGCF: 21. SIP: PRACK + MGCF-->>MGCF: 22. SIP: 200 OK (PRACK) + MGCF->>IM-MGW: 23. BICC: ANM + Note right of IM-MGW: Change IMS Through-Connection = both + MGCF->>IM-MGW: 24. H.248: MOD.req [Context ID=C1, Termination ID = T1] + IM-MGW-->>MGCF: 25. H.248: MOD.resp [Context ID = C1, Termination ID = T1] + + MGCF-->>MGCF: 26. SIP: 200 OK (INVITE) + MGCF->>MGCF: 27. SIP: ACK + + Note right of MGCF: CALL IN ACTIVE STATE + +``` + +Sequence diagram for Basic IM CN Subsystem originating session, BICC forward bearer establishment. Lifelines: MGCF and IM-MGW. The diagram shows the interaction between MGCF and IM-MGW for session establishment, including SIP INVITE, H.248 ADD.req/resp, and BICC IAM/APM messages. Annotations describe conditions like 'if SIP 100 rel is used', 'Only if SIP Preconditions are used', and 'Change IMS Through-Connection = both'. A 'CALL IN ACTIVE STATE' bar is shown at the bottom. + +Figure 34: Basic IM CN Subsystem originating session, BICC forward bearer establishment (message sequence chart) + +#### 9.2.2.2 BICC backward bearer establishment + +##### 9.2.2.2.1 IM-MGW selection + +The MGCF shall select an IM-MGW for the bearer connection before it performs the IM CN subsystem session establishment or the CS network side bearer establishment, and before it sends the IAM (signal 8 in figure 35). + +##### 9.2.2.2.2 IM CN subsystem side termination reservation + +On receipt of an initial INVITE (signal 1 in figure 35) the MGCF shall initiate the Reserve IMS Connection Point and Configure Remote Resources procedure (signal 3 and 4 in figure 35). From the received SDP and local configuration data the MGCF: + +- Shall send the appropriate remote codec(s), the remote UDP port and the remote IP address to the IM-MGW. The remote UDP port and IP address refer to the destination of user plane data sent towards the IM CN subsystem. The remote codec(s) are the codec(s) the IM-MGW may select for user plane data sent towards the IM CN subsystem. +- Shall indicate to the IM-MGW the appropriate local codec(s) and request a local IP address and UDP port. The local UDP port and IP address are used by the IM-MGW to receive user plane data from the IM CN subsystem. The local codec(s) are the codec(s) the IM-MGW may select to receive user plane data from the IM CN subsystem. +- If DTMF support together with speech support is required, the reserve value indicator shall be set to "true". +- May indicate that IP interface type is for MboIP. + +The IM-MGW shall + +- Reply to the MGCF with the selected local codec(s) and the selected remote codec(s) and the selected local UDP port and IP address. +- Reserve resources for those codec(s). + +The MGCF shall send the local codec(s), UDP port and IP address to the IMS in the Session Progress (signal 5 in figure 35). + +##### 9.2.2.2.3 IM CN subsystem side session establishment + +Dependent on what the MGCF receives in the PRACK message (signal 9 in figure 35) the MGCF may initiate the Select Configure IMS Resources procedure (signals 10 and 11 in figure 35). If no SDP is received, or if the received SDP does not contain relevant changes compared to the previous SDP the procedure is not invoked. Otherwise the MGCF shall use the Configure IMS Resources procedure to provide to the IM-MGW: + +- the appropriate remote codec(s), the remote UDP port and the remote IP address. +- optionally if DTMF support together with speech support is required, the reserve value indicator shall be set to "true". +- May indicate that IP interface type is for MboIP. + +The IM-MGW shall: + +- Reply to the MGCF with the selected remote codec(s). +- Reply to the MGCF with the selected local codec(s), if the MGCF supplied local codec(s). +- Update the codec reservation and remote IP address and remote UDP port in accordance with the received information. + +The MGCF shall include the selected codec(s), IP address and UDP port in an 200 OK (PRACK) (signal 12 in figure 35) sent back to the IMS + +##### 9.2.2.2.4 CS network side bearer establishment + +The MGCF shall request the IM-MGW to prepare for the CS network side bearer establishment using the Prepare Bearer procedure before sending the IAM to the succeeding node. Within this procedure, the MGCF shall request the IM-MGW to provide a bearer address and a binding reference, and the MGCF shall either provide the IM-MGW with the preferred bearer characteristics or it shall request the IM-MGW to select and provide the bearer characteristics (signal 6 in figure 35). After the IM-MGW has replied with the bearer address, the binding reference and the bearer characteristics (if requested), the MGCF sends the IAM to the succeeding node (signal 8 in figure 35). + +##### 9.2.2.2.5 Through-connection + +During the Prepare Bearer procedure, the MGCF shall either use the Change Through-Connection procedure to request the IM-MGW to backward through-connect the BICC termination, or the MGCF shall use this procedure to both-way through-connect the BICC termination already on this stage (signal 6 in figure 35). During the Reserve IMS Connection Point procedure: + +- if the MGCF has been identified a call as an "ICS call" as specified in clause 7.3.3.1.2.12 the MGCF shall request the IM-MGW to suspend sending media towards the IMS side by setting the through-connection of the IM CN subsystem side termination to "not through-connected" using the Change IMS Through-Connection procedure (signal 3 in figure 35); and +- otherwise the MGCF shall use the Change IMS Through-Connection procedure to request the IM-MGW to backward through-connect the IMS termination (signal 3 in figure 35). + +When the MGCF receives an BICC ACM or CPG message with an UID action indicators parameter with the through-connection instruction indicator set to "*through-connect in both directions*" the MGCF shall request the IM-MGW to both-way through-connect the terminations using the Change IMS Through-Connection or Change Through-Connection procedures (signal 17 in figure 35), unless those terminations are already both-way through-connected. + +When the MGCF receives the BICC:ANM answer indication, it shall request the IM-MGW to both-way through-connect the terminations using the Change Through-Connection or Change IMS Through-Connection procedures (signal 23 in figure 35), unless those terminations are already both-way through-connected. + +##### 9.2.2.2.6 Codec handling + +The IM-MGW may include a speech transcoder based upon the speech coding information provided to each termination. + +##### 9.2.2.2.7 Failure handling in MGCF + +If any procedure between the MGCF and the IM-MGW is not completed successfully the default action by the MGCF is to release the session as described in clause 9.2.6. If the MGCF receives a Bearer Released procedure from the IM-MGW the default action by the MGCF is to release the session, as described in clause 9.2.7. + +NOTE: As an implementation option the MGCF may also decide for example to only release the resources in the IM-MGW that caused the failure, possibly select a new IM-MGW for the connection and continue the call establishment using new resources in the selected IM-MGW but such handling is outside of the scope of the present document. + +##### 9.2.2.2.8 Message sequence chart + +Figure 35 shows the message sequence chart for the IM CN subsystem originating session with BICC backward bearer establishment. In the chart the MGCF requests the seizure of an IM CN subsystem side termination and a CS network side bearer termination. When the MGCF receives an answer indication, it requests the IM-MGW to both-way through-connect the terminations. Dashed lines represent optional or conditional messages. + + + +The sequence diagram illustrates the message exchange between the MGCF and the IM-MGW for a Basic IM CN Subsystem originating session. The sequence of messages is as follows: + +1. **SIP: INVITE** (MGCF to IM-MGW) +2. **SIP: 100 Trying** (IM-MGW to MGCF) +3. **H.248: ADD.req** [Context ID = ?, Termination ID=?] (MGCF to IM-MGW) - *Reserve IMS Connection Point and Configure Remote Resources, Change IMS Through -Connection = backward* +4. **H.248: ADD.resp** [Context ID = C1, Termination ID = T1] (IM-MGW to MGCF) +5. **SIP: 183 Session Progress** (MGCF to IM-MGW) - *if SIP 100 rel is used* +6. **H.248: ADD.req** [Context ID = C1, Termination ID = ?] (MGCF to IM-MGW) - *Prepare Bearer, Change Through-Connection = both* +7. **H.248: ADD.resp** [Context ID = C1, Termination ID = T2] (IM-MGW to MGCF) +8. **BICC: IAM** (MGCF to IM-MGW) - *Bearer Establishment* +9. **SIP: PRACK** (MGCF to IM-MGW) - *if SIP 100 rel is used* +10. **H.248: MOD.req** [Context ID = C1, Termination ID = T1] (MGCF to IM-MGW) - *Configure IMS Resources* +11. **H.248: MOD.resp** [Context ID = C1, Termination ID = T1] (IM-MGW to MGCF) +12. **SIP: 200 OK (PRACK)** (MGCF to IM-MGW) +13. **SIP: UPDATE** (MGCF to IM-MGW) - *Only if SIP Preconditions are used* +14. **SIP: 200 OK (UPDATE)** (IM-MGW to MGCF) +15. **BICC: COT** (MGCF to IM-MGW) - *Only if BICC continuity check and/or SIP Preconditions are used* +16. **BICC: ACM** (MGCF to IM-MGW) +17. **H.248: MOD.req** [Context ID=C1, Termination ID = T1] (MGCF to IM-MGW) - *Only if BICC UID action indicates through-connection in both direction* +18. **H.248: MOD.resp** [Context ID = C1, Termination ID = T1] (IM-MGW to MGCF) +19. **SIP: 180 Ringing** (MGCF to IM-MGW) - *Change IMS Through-Connection = both* +20. **SIP: PRACK** (MGCF to IM-MGW) +21. **SIP: 200 OK (PRACK)** (MGCF to IM-MGW) +22. **BICC: ANM** (MGCF to IM-MGW) +23. **H.248: MOD.req** [Context ID=C1, Termination ID = T1] (MGCF to IM-MGW) - *Change IMS Through-Connection = both* +24. **H.248: MOD.resp** [Context ID = C1, Termination ID = T1] (IM-MGW to MGCF) +25. **SIP: 200 OK (INVITE)** (MGCF to IM-MGW) +26. **SIP: ACK** (IM-MGW to MGCF) + +At the bottom, a double-headed arrow spans from the MGCF to the IM-MGW, labeled **CALL IN ACTIVE STATE**. + +Sequence diagram for Basic IM CN Subsystem originating session, BICC backward bearer establishment. The diagram shows interactions between MGCF and IM-MGW. The process starts with SIP INVITE and ends with SIP ACK. Key steps include H.248 ADD.req/resp for resource reservation, BICC IAM for bearer establishment, H.248 MOD.req/resp for resource configuration, BICC COT/ACM for continuity check, and H.248 MOD.req/resp for bearer change. The final state is 'CALL IN ACTIVE STATE'. + +**Figure 35: Basic IM CN Subsystem originating session, BICC backward bearer establishment (message sequence chart)** + +#### 9.2.2.3 ISUP + +##### 9.2.2.3.1 IM-MGW selection + +The MGCF shall select an IM-MGW with circuits to the given destination in the CS domain before it performs the IM CN subsystem session establishment and before it sends the IAM (signal 8 in figure 36). + +##### 9.2.2.3.2 IM CN subsystem side termination reservation + +On receipt of an initial INVITE (signal 1 in figure 36) the MGCF shall initiate the Reserve IMS Connection Point and Configure Remote Resources procedure (signal 3 and 4 in figure 36). From the received SDP and local configuration data the MGCF: + +- shall send the appropriate remote codec(s), the remote UDP port and the remote IP address to the IM-MGW. The remote UDP port and IP address refer to the destination of user plane data sent towards the IM CN subsystem. + +The remote codec(s) are the codec(s) the IM-MGW may select for user plane data sent towards the IM CN subsystem. + +- shall indicate to the IM-MGW the appropriate local codec(s) and request a local IP address and UDP port. The local IP address and UDP port are used by the IM-MGW to receive user plane data from the IM CN subsystem. The local codec(s) are the codec(s) the IM-MGW may select to receive user plane data from the IM CN subsystem. +- If DTMF support together with speech support is required, the reserve value indicator shall be set to "true". +- May indicate that IP interface type is for MboIP. + +The IM-MGW shall + +- reply to the MGCF with the selected local codec(s) and the selected remote codec(s) and the selected local UDP port and IP address. +- reserve resources for those codec(s). + +The MGCF shall send selected local codec(s) and the selected remote codec and the selected local UDP port and IP address to the IMS in the Session Progress (signal 5 in figure 36) + +##### 9.2.2.3.3 IM CN subsystem side session establishment + +Dependent on what the MGCF receives in the PRACK message (signal 9 in figure 35) the MGCF may initiate the Configure IMS Resources procedure. If no SDP is received, or if the received SDP does not contain relevant changes compared to the previous SDP, the procedure is not invoked. Otherwise the MGCF shall use the Configure IMS Resources procedure to provide to the IM-MGW: + +- the appropriate remote codec(s), the remote UDP port and the remote IP address. +- optionally the appropriate local codec(s), UDP port and IP address. +- If DTMF support together with speech support is required, the reserve value indicator shall be set to "true". +- May indicate that IP interface type is for MboIP. + +The IM-MGW shall: + +- reply to the MGCF with the selected remote codec. +- reply to the MGCF with the selected local codec(s), if the MGCF supplied local codec(s). +- update the codec reservation and remote IP address and UDP port in accordance with the received information. + +The MGCF shall include the selected codec(s) UDP port and IP address in 200 OK (PRACK) (signal 12 in figure 36) sent back to the IMS. + +##### 9.2.2.3.4 CS network side circuit reservation + +The MGCF shall request the IM-MGW to reserve a circuit using the Reserve TDM Circuit procedure. The MGCF sends the IAM to the succeeding node including the reserved circuit identity. + +##### 9.2.2.3.5 Through-connection + +During the Reserve TDM Circuit and Reserve IMS Connection Point procedures, the MGCF shall either use the Change TDM Through-Connection procedure to request the IM-MGW to backward through-connect the termination, or the MGCF shall use this procedure to both-way through-connect the TDM termination already on this stage (signal 6 in figure 36). During the Reserve IMS connection Point procedure: + +- if the MGCF has been identified a call as an "ICS call" as specified in clause 7.2.3.1.12 the MGCF shall request the IM-MGW to suspend sending media towards the IMS side by setting the through-connection of the IM CN subsystem side termination to "not through-connected" using the Change IMS Through-Connection procedure (signal 3 in figure 36); and + +- otherwise the MGCF shall use the Change IMS through-connection procedure to request the IM-MGW to backward through-connect the IMS termination (signal 3 in figure 36). + +When the MGCF receives an ISUP ACM or CPG message with an UID action indicators parameter with the through-connection instruction indicator set to "*through-connect in both directions*" the MGCF shall request the IM-MGW to both-way through-connect the terminations using the Change IMS Through-Connection or Change TDM Through-Connection procedures (signal 17 in figure 36), unless those terminations are already both-way through-connected. + +When the MGCF receives the ISUP:ANM answer indication, it shall request the IM-MGW to both-way through-connect the terminations using the Change IMS Through-Connection or Change TDM Through-Connection procedures (signal 23 in figure 36), unless those terminations are already both-way through-connected. + +##### 9.2.2.3.6 Continuity check + +The MGCF may request a continuity check on the connection towards the CS network within the IAM message. In this case, the MGCF shall use the Continuity Check procedure towards the IM-MGW to request the generation of a continuity check tone on the TDM termination. The IM-MGW shall then use the Continuity Check Verify procedure to notify the MGCF of an incoming continuity check tone on the corresponding circuit. In addition to other conditions detailed in Clause 7, the MGCF shall wait until receiving this notification before sending the COT. (Not depicted in figure 36) + +##### 9.2.2.3.7 Codec handling + +The IM-MGW may include a speech transcoder based upon the speech coding information provided to each termination. + +##### 9.2.2.3.8 Voice processing function + +A voice processing function located on the IM-MGW may be used to achieve desired acoustic quality on the terminations. If the voice processing function is used, the MGCF shall request the activation of it in the termination towards the CS network using the Activate TDM Voice Processing Function procedure (signal 23 in figure 36). + +##### 9.2.2.3.9 Failure handling in MGCF + +If any procedure between the MGCF and the IM-MGW is not completed successfully session shall be released as described in clause 9.2.6. If the MGCF receives a Bearer Released procedure from the IM-MGW the default action by the MGCF is to release the session as described in clause 9.2.7. + +##### 9.2.2.3.10 Message sequence chart + +Figure 36 shows the message sequence chart for the IM CN subsystem originating session. In the chart the MGCF requests the seizure of an IM CN subsystem side termination and a CS network side bearer termination. When the MGCF receives an answer indication, it requests the IM-MGW to both-way through-connect the terminations. The MGCF requests the possible activation of the voice processing functions for the bearer terminations. Dashed lines represent optional or conditional messages. + + + +``` + +sequenceDiagram + participant User + participant MGCF + participant IM-MGW + + Note left of MGCF: if SIP 100 rel is used + User->>MGCF: 1. SIP: INVITE + MGCF-->>User: 2. SIP: 100 Trying + MGCF->>IM-MGW: 3. H.248: ADD.req [Context ID = ?, Termination ID=?] + IM-MGW-->>MGCF: 4. H.248: ADD.resp [Context ID = C1, Termination ID = T1] + Note right of IM-MGW: Reserve IMS Connection Point, and Configure Remote Resources +Change IMSThrough-Connection = backward + MGCF-->>User: 5. SIP: 183 Session Progress + MGCF->>IM-MGW: 6. H.248: ADD.req [Context ID = C1, Termination ID = T2] + IM-MGW-->>MGCF: 7. H.248: ADD.resp [Context ID = C1, Termination ID = T2] + Note right of IM-MGW: Reserve TDM Circuit, Change TDM Through-Connection= both + MGCF->>IM-MGW: 8. ISUP: IAM + Note left of MGCF: if SIP 100 rel is used + MGCF-->>User: 9. SIP: PRACK + MGCF->>IM-MGW: 10. H.248: MOD.req [Context ID = C1, Termination ID = T1] + IM-MGW-->>MGCF: 11. H.248: MOD.resp [Context ID = C1, Termination ID = T1] + Note right of IM-MGW: Configure IMS Resources + MGCF-->>User: 12. SIP: 200 OK (PRACK) + Note left of MGCF: Only if SIP Preconditions are used + MGCF-->>User: 13. SIP: UPDATE + MGCF-->>User: 14. SIP: 200 OK (UPDATE) + MGCF-->>IM-MGW: 15. ISUP: COT + Note right of IM-MGW: Only if ISUP continuity check and/or SIP Preconditions are used + MGCF-->>IM-MGW: 16. ISUP: ACM + Note left of MGCF: Change IMS Through-Connection = both + MGCF->>IM-MGW: 17. H.248: MOD.req [Context ID=C1, Termination ID = T1] + IM-MGW-->>MGCF: 18. H.248: MOD.resp [Context ID = C1, Termination ID = T1] + Note right of IM-MGW: Only if ISUP UID action indicates through connection in both directions +Optional + MGCF-->>User: 19. SIP: 180 Ringing + MGCF-->>User: 20. SIP: PRACK + MGCF-->>User: 21. SIP: 200 OK (PRACK) + MGCF->>IM-MGW: 22. ISUP: ANM + MGCF->>IM-MGW: 23. H.248: MOD.req [Context ID=C1, Termination ID = T1] + IM-MGW-->>MGCF: 24. H.248: MOD.resp [Context ID = C1, Termination ID = T1] + Note right of IM-MGW: Change IMS Through-Connection = both + MGCF->>IM-MGW: 25. H.248: MOD.req [Context ID=C1, Termination ID = T2] + IM-MGW-->>MGCF: 26. H.248: MOD.resp [Context ID = C1, Termination ID = T2] + Note right of IM-MGW: Activate TDM Voice Processing Function + MGCF-->>User: 27. SIP: 200 OK (INVITE) + MGCF->>User: 28. SIP: ACK + Note bottom: CALL IN ACTIVE STATE + +``` + +Sequence diagram for Basic IM CN Subsystem originating session, ISUP. The diagram shows the interaction between MGCF and IM-MGW. The sequence starts with SIP INVITE and ends with SIP ACK, with a 'CALL IN ACTIVE STATE' indicated at the bottom. Various SIP, H.248, and ISUP messages are exchanged, with conditional blocks for SIP 100 rel, SIP Preconditions, and ISUP actions. + +Figure 36: Basic IM CN Subsystem originating session, ISUP (message sequence chart) + +### 9.2.3 Basic CS network originated session + +#### 9.2.3.1 BICC forward bearer establishment + +##### 9.2.3.1.1 IM-MGW selection + +The MGCF shall select an IM-MGW for the bearer connection before it performs the IM CN subsystem session establishment or the CS network side bearer establishment. + +##### 9.2.3.1.2 IM CN subsystem side termination reservation + +The MGCF shall derive from configuration data one or several appropriate local codec(s) the IM-MGW may use to receive user plane data from the IM CN subsystem. The MGCF shall use the Reserve IMS Connection Point procedure (signals 2 and 3 in figure 37). Within this procedure, the MGCF shall indicate the local codec(s) and request a local IP address and UDP port from the IM-MGW. The local IP address and UDP port are used by the IM-MGW to receive user plane data from the IM CN subsystem. If DTMF support together with speech support is required, or if the resources for multiple speech codecs shall be reserved at this stage, the reserve value indicator shall be set to "true". + +The MGCF may also indicate that the IP interface type is for MboIP. + +The IM-MGW shall reply to the MGCF with the selected local codec(s) and the selected local IP address and UDP port. + +The MGCF shall send this information in the INVITE (signal 4 in figure 37) to the IM CN subsystem. + +##### 9.2.3.1.3 IM CN subsystem side session establishment + +The MGCF shall use the Configure IMS Resources procedure (signals 7 and 8 or 23a and 23b in figure 37) to provide configuration data (derived from SDP received in signal 6 in figure 37 and local configuration data) to the IM-MGW as detailed below: + +- The MGCF shall indicate the remote IP address and UDP port, i.e. the destination IP address and UDP port for data sent in the user plane towards the IM CN subsystem, +- The MGCF shall indicate the remote codec(s), i.e. the speech codec(s) for data sent in the user plane towards the IM CN subsystem. +- The MGCF may indicate the local codec(s) and the local IP address and UDP port. The MGCF shall indicate the local codec(s) if a change is required. +- IF DTMF support together with speech support is required, the reserve value indicator shall be set to "true". +- The MGCF may indicate that IP interface type is for MboIP. + +The IM-MGW shall reply with the selected remote codec(s) and reserve resources for these codec(s). If local codec(s) were received, the IM-MGW shall also reply with the selected local codec(s) and reserve the corresponding resources. + +If the selected local codec(s) differ from the codec(s) received in the SDP of signal 6 in figure 37 (if any), the MGCF shall send the local reserved codec(s), and the local IP address and UDP port in the PRACK (signal 9 in figure 37) to the IMS. + +If the selected local codec(s) differ from the codec(s) received in the SDP of signal 23 in figure 37 (if any), the MGCF shall send the local reserved codec(s), and the local IP address and UDP port in an re-INVITE or UPDATE (not depicted in figure 37) to the IMS. + +##### 9.2.3.1.4 CS network side bearer establishment + +The MGCF shall request the IM-MGW to prepare for the CS network side bearer establishment using the Prepare Bearer procedure (signals 11 and 12 in figure 37). Within this procedure, the MGCF shall request the IM-MGW to provide a bearer address, a binding reference and optionally notify when the bearer is established. The MGCF shall also provide the IM-MGW with the bearer characteristics that was received from the preceding node in the IAM. After the IM-MGW has replied with the bearer address and the binding reference, the MGCF provides the APM message (signals 13 in figure 37) to the preceding node. The MGCF may also provide the IM-MGW-id in the APM message. + +##### 9.2.3.1.5 Called party alerting + +The MGCF shall request the IM-MGW to provide an awaiting answer indication (ringing tone) to the calling party using the Send Tone procedure (signals 20 and 21 in figure 37) , when the following condition is satisfied: + +- the MGCF receives the first 180 Ringing message, unless this message or some previous SIP provisional response contained a P-Early-Media header field that authorizes early media. + +##### 9.2.3.1.6 Called party answer + +When the MGCF receives a 200 OK message (signal 23 in figure 34), it shall request the IM-MGW to stop providing the ringing tone to the calling party using the Stop Tone procedure (signals 26 and 27 in figure 37). + +##### 9.2.3.1.7 Through-Connection + +During the Prepare Bearer procedure, the MGCF shall either use the Change Through-Connection procedure to request the IM-MGW to backward through-connect the BICC termination, or the MGCF shall use this procedure to both-way through-connect the BICC termination already on this stage (signals 11 and 12 in figure 37). During the Reserve IMS Connection Point procedure, the MGCF shall use the Change IMS Through-Connection procedure to request the IM-MGW to backward through-connect the IMS termination (signals 2 and 3 in figure 37). + +When the MGCF receives the SIP 200 OK(INVITE) (signal 23 in figure 37), it requests the IM-MGW to both-way through-connect the terminations using the Change IMS Through-Connection or Change Through-Connection procedures (signals 28 and 29 in figure 37), unless those terminations are already both-way through-connected. + +##### 9.2.3.1.8 Codec handling + +The IM-MGW may include a speech transcoder based upon the speech coding information provided to each termination. + +##### 9.2.3.1.9 Failure handling in MGCF + +If any procedure between the MGCF and the IM-MGW is not completed successfully, the default action by the MGCF is to release the session as described in clause 9.2.6. If the MGCF receives a Bearer Released procedure from the IM-MGW the default action by the MGCF is to release the session, as described in clause 9.2.7. + +- NOTE: As an implementation option the MGCF may also decide for example to only release the resources in the IM-MGW that caused the failure, possibly select a new IM-MGW for the connection and continue the call establishment using new resources in the selected IM-MGW but such handling is outside of the scope of the present document. + +##### 9.2.3.1.10 Message sequence chart + +Figure 37 shows the message sequence chart for the CS network originating session with BICC forward bearer establishment. In the chart the MGCF requests the seizure of the IM CN subsystem side termination and CS network side bearer termination. When the MGCF receives an answer indication, it requests the IM-MGW to both-way through-connect the terminations. Dashed lines represent optional or conditional messages. + + + +The sequence chart illustrates the interaction between IM-MGW and MGCF for a Basic CS Network Originating Session. The process begins with the IM-MGW sending a **1. BICC: IAM** to the MGCF. The MGCF responds with **2. H.248: ADD.req** [Context ID = ?, Termination ID=?], which includes the action: "Reserve IMS Connection Point, Change IMS Through-Connection = backward". The IM-MGW replies with **3. H.248: ADD.resp** [Context ID = C1, Termination ID = T1]. + +Next, the MGCF sends a **4. SIP: INVITE** to the user agent, receiving a **5. SIP: 100 Trying** response. The MGCF then sends a **6. SIP: 183 Session Progress**. The IM-MGW sends a **7. H.248: MOD.req** [Context ID = C1, Termination ID = T1] to the MGCF, with the annotation "Configure IMS Resources". The MGCF responds with **8. H.248: MOD.resp** [Context ID = C1, Termination ID = T1]. + +The MGCF then sends a **9. SIP: PRACK** (if SIP Preconditions and/or 100 rel are used) and a **10. SIP: 200 OK (PRACK)**. The IM-MGW sends a **11. H.248: ADD.req** [Context ID = C1, Termination ID = ?] to the MGCF, with the action: "Prepare Bearer, Change Through-Connection= both". The MGCF responds with **12. H.248: ADD.resp** [Context ID = C1, Termination ID = T2]. + +The IM-MGW then sends a **13. BICC: APM** to the MGCF. A dashed box labeled "Bearer Establishment" encompasses the next steps. The IM-MGW sends a **14. BICC: COT** to the MGCF, with the annotation "if continuity check is used". The MGCF responds with **15. SIP: UPDATE** (if SIP Preconditions and/or 100 rel are used) and **16. SIP: 200 OK (UPDATE)**. + +The MGCF then sends a **17. SIP: 180 Ringing** and an **18. SIP: PRACK** (Optional). The IM-MGW sends a **19. BICC: ACM** to the MGCF. The MGCF sends a **20. H.248: MOD.req** [Context ID = C1, Termination ID = T2] to the IM-MGW, with the annotation "Send Tone". The IM-MGW responds with **21. H.248: MOD.resp** [Context ID = C1, Termination ID = T2]. Finally, the MGCF sends a **22. SIP: 200 OK (PRACK)**. + +Sequence chart showing Basic CS Network Originating Session, Forward Bearer Establishment between IM-MGW and MGCF. The chart includes messages like BICC: IAM, H.248: ADD.req, SIP: INVITE, and H.248: MOD.req. Annotations include 'Configure IMS Resources', 'Bearer Establishment', and 'Send Tone'. + +Figure 37/1: Basic CS Network Originating Session, Forward Bearer Establishment (message sequence chart) + + + +``` + +sequenceDiagram + participant IM-MGW + participant MGCF + Note right of MGCF: 23. SIP: 200 OK (INVITE) + MGCF->>IM-MGW: 23a. H.248: MOD.req [Context ID = C1, Termination ID = T1] + Note right of MGCF: Configure IMS Resources +if SIP Preconditions and 100 rel are not used + IM-MGW-->>MGCF: 23b. H.248: MOD.resp [Context ID = C1, Termination ID = T1] + MGCF->>IM-MGW: 24. H.248: MOD.req [Context ID=C1, Termination ID = T2] + IM-MGW-->>MGCF: 25. H.248: MOD.resp [Context ID = C1, Termination ID = T2] + Note right of MGCF: Stop Tone +if tone was inserted + MGCF->>IM-MGW: 26. H.248: MOD.req [Context ID=C1, Termination ID = T1] + IM-MGW-->>MGCF: 27. H.248: MOD.resp [Context ID = C1, Termination ID = T1] + Note right of MGCF: Change IMS Through-Connection = both + IM-MGW->>IM-MGW: 28. BICC: ANM + MGCF->>MGCF: 29. SIP: ACK + Note bottom: CALL IN ACTIVE STATE + +``` + +Sequence diagram showing the Basic CS Network Originating Session, Forward Bearer Establishment. The diagram involves two main entities: IM-MGW and MGCF. The sequence starts with signal 23. SIP: 200 OK (INVITE) from MGCF to IM-MGW. This is followed by a series of H.248 messages: 23a. MOD.req, 23b. MOD.resp, 24. MOD.req, 25. MOD.resp, 26. MOD.req, and 27. MOD.resp. These are accompanied by annotations: 'Configure IMS Resources' (if SIP Preconditions and 100 rel are not used), 'Stop Tone' (if tone was inserted), and 'Change IMS Through-Connection = both'. Signal 28. BICC: ANM is sent from IM-MGW to the left. Signal 29. SIP: ACK is sent from MGCF to the right. A bracket at the bottom indicates the 'CALL IN ACTIVE STATE'. + +**Figure 37/2: Basic CS Network Originating Session, Forward Bearer Establishment (message sequence chart continue)** + +#### 9.2.3.2 BICC Backward bearer establishment + +##### 9.2.3.2.1 IM-MGW selection + +The MGCF shall select an IM-MGW for the bearer connection before it performs the IM CN subsystem session establishment or the CS network side bearer establishment. + +##### 9.2.3.2.2 CS network side bearer establishment + +The MGCF shall request the IM-MGW to establish a bearer using the Establish Bearer procedure (signals 2 and 3 in figure 38). The MGCF provides the IM-MGW with the bearer address, the binding reference and the bearer characteristics that were received from the preceding node in the IAM (signal 1 in figure 38). + +##### 9.2.3.2.3 IM CN subsystem side termination reservation + +The MGCF shall derive from configuration data one or several appropriate local codec(s) the IM-MGW may use to receive user plane data from the IM CN subsystem. The MGCF shall use the Reserve IMS Connection Point procedure (signals 2 and 3 in figure 38). Within this procedure, the MGCF shall indicate the local codec(s) and request a local IP address and UDP port from the IM-MGW. The local IP address and UDP port are used by the IM-MGW to receive user plane data from the IM CN subsystem. If DTMF support together with speech support is required, or if the resources for multiple speech codecs shall be reserved at this stage, the reserve value indicator shall be set to "true". + +The MGCF may also indicate that the IP interface type is for MboIP. + +The IM-MGW shall reply to the MGCF with the selected local codec(s) and the selected local IP address and UDP port. + +The MGCF shall send this information in the INVITE (signal 6 in figure 38) to the IM CN subsystem. + +##### 9.2.3.2.4 IM CN subsystem side session establishment + +The MGCF shall use the Configure IMS Resources procedure (signals 9 and 10 or 22a and 22b in figure 38) to provide configuration data (derived from SDP received in signal 8 in figure 38 and local configuration data) to the IM-MGW as detailed below: + +- The MGCF shall indicate the remote IP address and UDP port, i.e. the destination IP address and UDP port for data sent in the user plane towards the IM CN subsystem +- The MGCF shall indicate the remote codec(s), i.e. the speech codec(s) for data sent in the user plane towards the IM CN subsystem. +- The MGCF may indicate the local codec(s) and the local IP address and UDP port. The MGCF shall indicate the local codec(s) if a change is required. +- If DTMF support together with speech support is required, the reserve value indicator shall be set to "true". +- The MGCF may indicate that IP interface type is for MboIP. + +The IM-MGW shall reply with the selected remote codec(s) and reserve resources for this codec. If local codec(s) were received, the IM-MGW shall also reply with the selected local codec(s) and reserve the corresponding resources. + +If the selected local codec(s) differ from the codec(s) received in the SDP of signal 8 in figure 38 (if any), the MGCF shall send the reserved speech codec(s), and the local IP address and UDP port in the PRACK (signal 11 in figure 38) to the IMS. + +If the selected local codec(s) differ from the codec(s) received in the SDP of signal 22 in figure 38 (if any), the MGCF shall send the local reserved codec(s), and the local IP address and UDP port in an re-INVITE or UPDATE (not depicted in figure 38) to the IMS. + +##### 9.2.3.2.5 Called party alerting + +The MGCF shall request the IM-MGW to provide an awaiting answer indication (ringing tone) to the calling party using the Send Tone procedure (signals 19 and 20 in figure 38) , when the following conditions is satisfied: + +- the MGCF receives the first 180 Ringing message, unless this message or some previous SIP provisional response contained a P-Early-Media header field that authorizes early media. + +##### 9.2.3.2.6 Called party answer + +When the MGCF receives a 200 OK message (signal 22 in figure 38), it shall request the IM-MGW to stop providing the ringing tone to the calling party using the Stop Tone procedure (signals 23 and 24 in figure 38). + +##### 9.2.3.2.7 Through-Connection + +During the Establish Bearer procedure, the MGCF shall either use the Change Through-Connection procedure to request the IM-MGW to backward through-connect the BICC termination, or the MGCF shall use this procedure to both-way through-connect the BICC termination already on this stage (signals 2 and 3 in figure 38). During the Reserve IMS Connection Point procedure, the MGCF shall use the Change IMS Through-Connection procedure to request the IM-MGW to backward through-connect the IMS termination (signals 4 and 5 in figure 38). + +When the MGCF receives the SIP 200 OK(INVITE) (signal 22 in figure 38), it shall request the IM-MGW to both-way through-connect the bearer using the Change IMS Through-Connection or Change Through-Connection procedure (signals 25 and 26 in figure 38), unless those terminations are already both-way through-connected. + +##### 9.2.3.2.8 Codec handling + +The IM-MGW may include a speech transcoder based upon the speech coding information provided to each termination. + +##### 9.2.3.2.9 Failure handling in MGCF + +If any procedure between the MGCF and the IM-MGW is not completed successfully, the default action by the MGCF is to release the session as described in clause 9.2.6. If the MGCF receives a Bearer Released procedure from the IM-MGW the default action by the MGCF is to release the session as described in clause 9.2.7. + +NOTE: As an implementation option the MGCF may also decide for example to only release the resources in the IM-MGW that caused the failure, possibly select a new IM-MGW for the connection and continue the call establishment using new resources in the selected IM-MGW but such handling is outside of the scope of the present document. + +##### 9.2.3.2.10 Message sequence chart + +Figure 38 shows the message sequence chart for the CS network originating session with BICC backward bearer establishment. In the chart the MGCF requests seizure of the IM CN subsystem side termination and CS network side bearer termination. When the MGCF receives an answer indication, it requests the IM-MGW to both-way through-connect the terminations. Dashed lines represent optional or conditional messages. + + + +``` + +sequenceDiagram + participant IM-MGW + participant MGCF + + Note left of IM-MGW: Bearer Establishment + IM-MGW->>MGCF: 1. BICC: IAM + MGCF-->>IM-MGW: 2. H.248: ADD.req [Context ID = ?, Termination ID = ?] + IM-MGW-->>MGCF: 3. H.248: ADD.resp [Context ID = C1, Termination ID = T2] + Note right of MGCF: Establish Bearer, Change Through-Connection = both + Note left of IM-MGW: Configure IMS Resources + MGCF-->>IM-MGW: 4. H.248: ADD.req [Context ID = C1, Termination ID=?] + IM-MGW-->>MGCF: 5. H.248: ADD.resp [Context ID = C1, Termination ID = T1] + Note right of MGCF: Reserve IMS Connection Point, Change IMSThrough-Connection = backward + MGCF->>IM-MGW: 6. SIP: INVITE + IM-MGW-->>MGCF: 7. SIP: 100 Trying + MGCF-->>IM-MGW: 8. SIP: 183 Session Progress + IM-MGW-->>MGCF: 9. H.248: MOD.req [Context ID = C1, Termination ID = T1] + MGCF-->>IM-MGW: 10. H.248: MOD.resp [Context ID = C1, Termination ID = T1] + Note right of MGCF: if SIP Preconditions and/or 100 rel are used + MGCF->>IM-MGW: 11. SIP: PRACK + IM-MGW-->>MGCF: 12. SIP: 200 OK (PRACK) + Note left of IM-MGW: if continuity check is used + IM-MGW-->>MGCF: 13. BICC: COT + MGCF-->>IM-MGW: 14. SIP: UPDATE + Note right of MGCF: if SIP Preconditions and/or 100 rel are used + MGCF->>IM-MGW: 15. SIP: 200 OK (UPDATE) + IM-MGW-->>MGCF: 16. SIP: 180 Ringing + MGCF-->>IM-MGW: 17. SIP: PRACK + IM-MGW-->>MGCF: 18. BICC: ACM + Note right of MGCF: Optional + MGCF-->>IM-MGW: 19. H.248: MOD.req [Context ID = C1, Termination ID = T2] + IM-MGW-->>MGCF: 20. H.248: MOD.resp [Context ID = C1, Termination ID = T2] + Note right of MGCF: Send Tone + MGCF-->>IM-MGW: 21. SIP: 200 OK (PRACK) + +``` + +Sequence chart for Basic CS Network Originating Session, BICC Backward Bearer Establishment. Lifelines: IM-MGW and MGCF. The process involves BICC IAM, H.248 ADD.req/resp, SIP INVITE/100 Trying/183 Session Progress, H.248 MOD.req/resp, SIP PRACK/200 OK, BICC COT, SIP UPDATE/200 OK/180 Ringing, BICC ACM, and optional H.248 MOD.req/resp and SIP 200 OK. + +Figure 38/1: Basic CS Network Originating Session, BICC Backward Bearer Establishment (message sequence chart) + + + +``` + +sequenceDiagram + participant External + participant MGCF + participant IM-MGW + + Note right of MGCF: if SIP Pre-conditions and 100 rel are not used + Note right of MGCF: Stop Tone If tone was inserted + Note right of MGCF: Change IMS Through-Connection = both + + External->>MGCF: 22. SIP:200 OK (INVITE) + MGCF->>IM-MGW: 22a. H.248: MOD.req [Context ID = C1, Termination ID = T1] + IM-MGW-->>MGCF: 22b. H.248: MOD.resp [Context ID = C1, Termination ID = T1] + MGCF->>IM-MGW: 23. H.248: MOD.req [Context ID = C1, Termination ID = T2] + IM-MGW-->>MGCF: 24. H.248: MOD.resp [Context ID = C1, Termination ID = T2] + MGCF->>IM-MGW: 25. H.248: MOD.req [Context ID = C1, Termination ID = T1] + IM-MGW-->>MGCF: 26. H.248: MOD.resp [Context ID = C1, Termination ID = T1] + MGCF->>IM-MGW: 27. BICC: ANM + MGCF->>External: 28. SIP: ACK + +``` + +Sequence diagram for Basic CS Network Originating Session, BICC Backward Bearer Establishment. The diagram shows interactions between IM-MGW and MGCF. The MGCF sends a SIP:200 OK (INVITE) to an external entity. The MGCF then sends H.248 MOD.req (Context ID = C1, Termination ID = T1) to the IM-MGW. The IM-MGW responds with H.248 MOD.resp (Context ID = C1, Termination ID = T1). The MGCF then sends H.248 MOD.req (Context ID = C1, Termination ID = T2) to the IM-MGW. The IM-MGW responds with H.248 MOD.resp (Context ID = C1, Termination ID = T2). The MGCF then sends H.248 MOD.req (Context ID = C1, Termination ID = T1) to the IM-MGW. The IM-MGW responds with H.248 MOD.resp (Context ID = C1, Termination ID = T1). The MGCF then sends BICC: ANM to the IM-MGW. The MGCF then sends SIP: ACK to the external entity. A bracket at the bottom indicates the 'CALL IN ACTIVE STATE' between the MGCF and the external entity. + +**Figure 38/2: Basic CS Network Originating Session, BICC Backward Bearer Establishment (message sequence chart continue)** + +#### 9.2.3.3 ISUP + +##### 9.2.3.3.1 IM-MGW selection + +The MGCF selects the IM-MGW based on the received circuit identity in the IAM. + +##### 9.2.3.3.2 CS network side circuit reservation + +The MGCF shall request the IM-MGW to reserve a circuit using the Reserve TDM Circuit procedure. + +##### 9.2.3.3.3 IM CN subsystem side termination reservation + +The MGCF shall derive from configuration data one or several appropriate local codec(s) the IM-MGW may use to receive user plane data from the IM CN subsystem. The MGCF shall use the Reserve IMS Connection Point procedure (signals 2 and 3 in figure 39). Within this procedure, the MGCF shall indicate the local codec(s) and request a local IP address and UDP port from the IM-MGW. The local IP address and UDP port are used by the IM-MGW to receive user plane data from the IM CN subsystem. If DTMF support together with speech support is required, or if the resources for multiple speech codecs shall be reserved at this stage, the reserve value indicator shall be set to "true". + +The MGCF may also indicate that the IP interface type is for MboIP. + +The IM-MGW shall reply to the MGCF with the selected local codec(s) and the selected local IP address and UDP port. + +The MGCF shall send this information in the INVITE (signal 6 in figure 39) to the IM CN subsystem. + +##### 9.2.3.3.4 IM CN subsystem side session establishment + +The MGCF shall use the Configure IMS Resources procedure (signals 9 and 10 or 22a and 22b in figure 39) to provide configuration data (derived from SDP received in signal 8 in figure 39 and local configuration data) as detailed below: + +- The MGCF shall indicate the remote IP address and UDP port, i.e. the destination IP address and UDP port for data sent in the user plane towards the IM CN subsystem. + +- The MGCF shall indicate the remote codec(s), i.e. the speech codec(s) for data sent in the user plane towards the IM CN subsystem. +- The MGCF may indicate the local codec(s) and the local IP address and UDP port. The MGCF shall indicate the local codec(s) if a change is required. +- If DTMF support together with speech support is required, the reserve value indicator shall be set to "true". +- The MGCF may indicate that IP interface type is for MboIP. + +The IM-MGW shall reply with the selected remote codec(s) and reserve resources for these codec(s). If local codec(s) were received, the IM-MGW shall also reply with the selected local codec(s) and reserve the corresponding resources. + +If the selected local codec(s) differ from the codec(s) received in the SDP of signal 8 in figure 39 (if any), the MGCF shall send the reserved speech codec(s), and the local IP address and UDP port in the PRACK (signal 11 in figure 39) to the IMS. + +If the selected local codec(s) differ from the codec(s) received in the SDP of signal 22 in figure 39 (if any), the MGCF shall send the local reserved codec(s), and the local IP address and UDP port in an re-INVITE or UPDATE (not depicted in figure 39) to the IMS. + +##### 9.2.3.3.5 Called party alerting + +The MGCF shall request the IM-MGW to provide an awaiting answer indication (ringing tone) to the calling party using the Send TDM Tone procedure (signals 19 and 20 in figure 39), when the following condition is satisfied: + +- the MGCF receives the first 180 Ringing message, unless this message or some previous SIP provisional response contained a P-Early-Media header field that authorizes early media. + +##### 9.2.3.3.6 Called party answer + +When the MGCF receives a 200 OK message (signal 22 in figure 39), it shall request the IM-MGW to stop providing the ringing tone to the calling party using the Stop TDM Tone procedure (signals 23 and 24 in figure 39). + +##### 9.2.3.3.7 Through-Connection + +Within the Reserve TDM Circuit procedure, the MGCF shall either use the Change TDM Through-Connection procedure to request the IM-MGW to backward through-connect the TDM termination, or the MGCF shall use this procedure to both-way through-connect the TDM termination already on this stage (signals 2 and 3 in figure 39). During the Reserve IMS Connection Point procedure, the MGCF shall use the Change IMS Through-Connection procedure to request the IM-MGW to backward through-connect the IMS termination (signals 4 and 5 in figure 39). + +When the MGCF receives the SIP 200 OK(INVITE) message, it shall request the IM-MGW to both-way through-connect the terminations using the Change IMS Through-Connection or Change TDM Through-Connection procedure (signals 25 and 26 in figure 39), unless those terminations are already both-way through-connected. + +##### 9.2.3.3.8 Continuity Check + +If a continuity check on the connection towards the CS network is requested in the IAM message, the MGCF shall use the Continuity Check Response procedure towards the IM-MGW to request loop-back of a received continuity check tone on the TDM circuit. Upon reception of the COT message, the MGCF shall use the Continuity Check Response procedure towards the IM-MGW to request the removal of the loop-back. (Not depicted in figure 39) + +##### 9.2.3.3.9 Codec handling + +The IM-MGW may include a speech transcoder based upon the speech coding information provided to each termination. + +##### 9.2.3.3.10 Voice Processing function + +A voice processing function located on the IM-MGW may be used to achieve desired acoustic quality on the terminations. If the voice processing function is used, the MGCF shall request the activation of it in the termination towards the CS network using the Activate TDM Voice Processing Function procedure (signal 23 in figure 39). + +##### 9.2.3.3.11 Failure handling in MGCF + +If any procedure between the MGCF and the IM-MGW is not completed successfully, the session shall be released as described in clause 9.2.6. If the MGCF receives a Bearer Released procedure from the IM-MGW the default action by the MGCF is to release the session as described in clause 9.2.7. + +##### 9.2.3.3.12 Message sequence chart + +Figure 39 shows the message sequence chart for the CS network originating Session with ISUP. In the chart the MGCF requests seizure of the IM CN subsystem side termination and CS network side bearer termination. When the MGCF receives an answer indication, it requests the IM-MGW to both-way through-connect the terminations. The MGCF may request the possible activation of the voice processing functions for the terminations. Dashed lines represent optional or conditional messages. + + + +``` + +sequenceDiagram + participant IM-MGW + participant MGCF + + Note left of IM-MGW: Configure IMS Resources + IM-MGW->>MGCF: 1. ISUP: IAM + MGCF-->>IM-MGW: 2. H.248: ADD.req [Context ID = ?, Termination ID = ?] + Note right of MGCF: Reserve TDM Circuit, Change Through-Connection = both + MGCF->>IM-MGW: 3. H.248: ADD.resp [Context ID = C1, Termination ID = T2] + MGCF-->>IM-MGW: 4. H.248: ADD.req [Context ID = C1, Termination ID=?] + Note right of MGCF: Reserve IMS Connection Point, Change IMS Through-Connection = backward + MGCF->>IM-MGW: 5. H.248: ADD.resp [Context ID = C1, Termination ID = T1] + MGCF->>IM-MGW: 6. SIP: INVITE + MGCF-->>IM-MGW: 7. SIP: 100 Trying + MGCF-->>IM-MGW: 8. SIP: 183 Session Progress + Note right of MGCF: if SIP Preconditions and/or 100 rel are used + MGCF-->>IM-MGW: 9. H.248: MOD.req [Context ID = C1, Termination ID = T1] + MGCF-->>IM-MGW: 10. H.248: MOD.resp [Context ID = C1, Termination ID = T1] + MGCF->>IM-MGW: 11. SIP: PRACK + MGCF-->>IM-MGW: 12. SIP: 200 OK (PRACK) + Note left of IM-MGW: if continuity check is used + IM-MGW-->>MGCF: 13. ISUP: COT + MGCF->>IM-MGW: 14. SIP: UPDATE + Note right of MGCF: if SIP Preconditions and/or 100 rel are used + MGCF-->>IM-MGW: 15. SIP: 200 OK (UPDATE) + MGCF-->>IM-MGW: 16. SIP: 180 Ringing + MGCF->>IM-MGW: 17. SIP: PRACK + IM-MGW-->>IM-MGW: 18. ISUP: ACM + MGCF-->>IM-MGW: 19. H.248: MOD.req [Context ID = C1, Termination ID = T2] + MGCF->>IM-MGW: 20. H.248: MOD.resp [Context ID = C1, Termination ID = T2] + Note right of MGCF: Send TDM Tone Optional + MGCF-->>IM-MGW: 21. SIP: 200 OK (PRACK) + +``` + +Sequence diagram for Basic CS Network Originating Session, ISUP. Lifelines: IM-MGW and MGCF. The diagram shows the interaction between the IM-MGW and MGCF for session setup, including ISUP IAM, H.248 ADD/MOD messages, and SIP INVITE/UPDATE/ACK messages. Annotations include 'Configure IMS Resources', 'if continuity check is used', and 'Send TDM Tone Optional'. + +Figure 39/1: Basic CS Network Originating Session, ISUP (message sequence chart) + +![Sequence diagram for Basic CS Network Originating Session, ISUP (message sequence chart continue). The diagram shows interactions between IM-MGW and MGCF. The sequence starts with MGCF sending a 22. SIP :200 OK (INVITE) to IM-MGW. IM-MGW responds with 22a. H.248: MOD.req [Context ID = C1, Termination ID = T1]. MGCF replies with 22b. H.248: MOD.resp [Context ID = C1, Termination ID = T1]. IM-MGW then sends 23. H.248: MOD.req [Context ID=C1, Termination ID = T2]. MGCF replies with 24. H.248: MOD.resp [Context ID = C1, Termination ID = T2]. IM-MGW sends 25. H.248: MOD.req [Context ID=C1, Termination ID = T1]. MGCF replies with 26. H.248: MOD.resp [Context ID = C1, Termination ID = T1]. IM-MGW sends 27. ISUP: ANN. MGCF replies with 28. SIP: ACK. A bracket at the bottom indicates the 'CALL IN ACTIVE STATE' from signal 27 onwards. Annotations on the right side of the MGCF lifeline describe the actions taken: 'Configure IMS Resources' (if SIP Preconditions and 100 rel are not used), 'Stop TDM Tone, Activate TDM Voice Processing Function' (if tone was inserted or for voice processing), and 'Change IMS Through-Connection = both'.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +Sequence diagram for Basic CS Network Originating Session, ISUP (message sequence chart continue). The diagram shows interactions between IM-MGW and MGCF. The sequence starts with MGCF sending a 22. SIP :200 OK (INVITE) to IM-MGW. IM-MGW responds with 22a. H.248: MOD.req [Context ID = C1, Termination ID = T1]. MGCF replies with 22b. H.248: MOD.resp [Context ID = C1, Termination ID = T1]. IM-MGW then sends 23. H.248: MOD.req [Context ID=C1, Termination ID = T2]. MGCF replies with 24. H.248: MOD.resp [Context ID = C1, Termination ID = T2]. IM-MGW sends 25. H.248: MOD.req [Context ID=C1, Termination ID = T1]. MGCF replies with 26. H.248: MOD.resp [Context ID = C1, Termination ID = T1]. IM-MGW sends 27. ISUP: ANN. MGCF replies with 28. SIP: ACK. A bracket at the bottom indicates the 'CALL IN ACTIVE STATE' from signal 27 onwards. Annotations on the right side of the MGCF lifeline describe the actions taken: 'Configure IMS Resources' (if SIP Preconditions and 100 rel are not used), 'Stop TDM Tone, Activate TDM Voice Processing Function' (if tone was inserted or for voice processing), and 'Change IMS Through-Connection = both'. + +**Figure 39/2: Basic CS Network Originating Session, ISUP (message sequence chart continue)** + +#### 9.2.3.4 Handling of Forking + +The procedures described in clauses 9.2.3.1 to 9.2.3.3 shall be applied with the following additions. + +##### 9.2.3.4.1 Detection of Forking + +According to SIP procedures, the O-MGCF inspects the tags in the "to" SIP header fields of provisional and final responses to identify the SIP dialogue the response belongs to. If responses belonging to different dialogues are received (signals 8 and 13 in figure 39a), the INVITE request (signal 6 in figure 39a) has been forked. + +##### 9.2.3.4.2 IM CN subsystem side session establishment + +If one or more SIP early dialog exists and: + +- a) if the O-MGCF has not already received a P-Early-Media header field that authorizes backward early media (the received em-param(s) in the P-Early-Media header field includes "sendrecv" or "sendonly") on any of existing SIP early dialog, then upon reception of a provisional 18x response with an SDP answer creating a new early dialog (signal 13 in figure 39a/1) and: + - 1) with the P-Early-Media header field that authorizes backward early media (the received em-param(s) in the P-Early-Media header field includes "sendrecv" or "sendonly"), the O-MGCF shall use the Configure IMS Resources procedure (signals 14 and 15 in figure 39a/1) and shall provide to the IM-MGW: + - the remote IP address and UDP port, and the remote codec selected from the received SDP answer. + +The IM-MGW may be configured to use the remote IP address and port information as source filter for incoming packets to prevent that backward early media from other early SIP dialogs interfere. The O-MGCF may also provide an IP address and port source filter that disallows backward early media from other early dialogs without an early media authorization in order to prevent that such unauthorized backward early media interfere with the authorized backward early media. (NOTE 1); and + - local configuration data, corresponding to the SIP early dialog of the SIP provisional response containing a P-Early-Media header field that authorizes backward early media; or +- 2) without the P-Early-Media header field or with the P-Early-Media header field that does not authorize backward early media (the received em-param(s) in the P-Early-Media header field includes "inactive" or "recvonly"), the O-MGCF may either: + - refrain from reconfiguring the IM-MGW; or + +- use the Configure IMS Resources procedure (signals 14 and 15 in figure 39a/1) as detailed below: + - i) the O-MGCF may compare the selected local codecs of the different dialogs (which the O-MGCF selects due to the received SDP answer and local configuration data). If different local codecs are selected for the different dialogs, the O-MGCF may include all these codecs in the "local IMS resources", and set the "reserve value" to indicate that resources for all these codecs shall be reserved. Alternatively, the O-MGCF may only include the codecs received in the last received SDP in the "local IMS resources"; and + - ii) the O-MGCF may update the "remote IMS resources" with the information received in the latest SDP answer. The MGCF should provide the remote IP address and UDP port, and the remote codec selected from the received SDP answer and local configuration data. (NOTE 2); or +- b) if the O-MGCF has already received a P-Early-Media header field that authorizes backward early media (the received em-param(s) in the P-Early-Media header field includes "sendrecv" or "sendonly") on any of existing early dialog, then upon reception of a provisional 18x response with an SDP answer creating a new early dialog (signal 13 in figure 39a/1) and: + - 1) with the P-Early-Media header field that authorizes backward early media (the received em-param(s) in the P-Early-Media header field includes "sendrecv" or "sendonly"), the O-MGCF may either: + - refrain from reconfiguring the IM-MGW; or + - use the Configure IMS Resources procedure (signals 14 and 15 in figure 39a/1) to provide to the IM-MGW the remote IP address and UDP port, and the remote codec selected from the received SDP answer and local configuration data, corresponding to the SIP early dialog of the SIP provisional response containing the P-Early-Media header field that authorizes backward early media. The IM-MGW may be configured to use the remote IP address and port information as source filter for incoming packets to prevent that backward early media from another early SIP dialog interfere. The O-MGCF may also provide an IP address and port source filter that disallows backward early media from other early dialogs without an early media authorization in order to prevent that such unauthorized backward early media interfere with the authorized backward early media. (NOTE 1, NOTE 2); or + - 2) without the P-Early-Media header field or with the P-Early-Media header field that does not authorize backward early media (the received em-param(s) in the P-Early-Media header field includes "inactive" or "recvonly"), the O-MGCF shall store the received SDP answer and shall refrain from reconfiguring the IM-MGW. + +NOTE 1: The O-MGCF can use the P-Early-Media header field (IETF RFC 5009 [89]) to determine whether the media associated with a forked dialog is authorized and thus eligible for a through connection. In the presence of backward early media for multiple dialogs due to forking, if the IM-MGW is able to identify the media associated with a dialog (i.e., if symmetric RTP is used by the peer and the IM-MGW can use the remote SDP information to determine the source of the media), then the O-MGCF/IM-MGW can selectively establish a through-connection for an authorized backward early media flow. + +NOTE 2: This behaviour is beneficial if forking is applied in a sequential manner. + +If the O-MGCF has not already received a P-Early-Media header field that authorizes backward early media (the received em-param(s) in the P-Early-Media header field includes "sendrecv" or "sendonly") on any of existing SIP early dialog, then: + +- a) upon reception of a SIP message with the P-Early-Media header field that authorizes backward early media (the received em-param(s) in the P-Early-Media header field includes "sendrecv" or "sendonly") on existing early dialog; and + +NOTE 3: For the existing early dialog the P-Early-Media header field can be received within the UPDATE requests, 2xx responses to the PRACK and the UPDATE requests, and in the subsequent 18x provisional responses (as specified in IETF RFC 5009 [89]). Subsequent 18x provisional response is every 18x provisional response except the first 18x provisional response, received within the one early dialog. Reception of the first 18x provisional response which creates a new early dialog is described in at the beginning of this subclause). + +- b) if the O-MGCF has received an SDP body on the early dialog on which the SIP message with the P-Early-Media header field that authorizes backward early media was received, + +the O-MGCF shall provide to the IM-MGW the remote IP address and UDP port, and the remote codec selected from the latest received SDP body corresponding to the early dialog on which the SIP message with the P-Early-Media header field that authorizes backward early media was received. + +Upon reception of: + +- a) a SIP message with the P-Early-Media header field that removes authorization of backward early media (the received em-param(s) in the P-Early-Media header field includes "inactive" or "recvonly") on the early dialog for which: + - 1) the P-Early-Media header field authorizing backward early media was previously received (the received em-param(s) in the P-Early-Media header field includes "sendrecv" or "sendonly"); and + - 2) the O-MGCF provided to the IM-MGW the remote IP address and UDP port, and the remote codec selected from the latest received SDP body corresponding to this early dialog and this remote IP address and UDP port, are the most recently sent the remote IP address and UDP port to the IM-MGW; or +- b) a 199 Early Dialog Terminated provisional response corresponding to the SIP early dialog for which: + - 1) the P-Early-Media header field authorizing backward early media was previously received (the received em-param(s) in the P-Early-Media header field includes "sendrecv" or "sendonly"); and + - 2) the O-MGCF provided to the IM-MGW the remote IP address and UDP port, and the remote codec selected from the latest received SDP body corresponding to this early dialog and this remote IP address and UDP port, are the most recently sent the remote IP address and UDP port to the IM-MGW, + +the O-MGCF shall check if the P-Early-Media header field that authorizes backward early media (the received em-param(s) in the P-Early-Media header field includes "sendrecv" or "sendonly") was received on any other early dialog and that the authorization of backward early media on that early dialog has not changed. If such early dialog: + +- a) exists the O-MGCF shall provide to the IM-MGW using the Configure IMS Resources procedure, the remote IP address and UDP port, and the remote codec selected from the latest received SDP body on that early dialog. If there is more than one such early dialog, the O-MGCF shall select the early dialog where the P-Early-Media header field was most recently received; or +- b) does not exist and if: + - 1) the O-MGCF has already received the 180 Ringing provisional response on any of existing SIP early dialog; or + - 2) the received SIP message is the 180 Ringing provisional response, + +the O-MGCF shall request the IM-MGW to provide an awaiting answer indication (ringing tone) to the calling party using the Send Tone procedure (signals 27 and 28 in figure 39a/2). + +##### 9.2.3.4.3 IM CN subsystem side session establishment completion + +Upon reception of the first final 2xx response (signal 32 in figure 39a), the MGCF shall use the Configure IMS Resources procedure (signals 35 and 36 in figure 39a) as detailed below unless the IM-MGW is already configured accordingly: + +- If the remote IMS resources configured at the IM-MGW do not match the remote resources selected for the established dialogue of the final response, the MGCF shall provide the remote IP address and UDP port from the latest received SDP of this established dialogue, and the remote codec selected from the latest received SDP of this established dialogue and local configuration data within the "remote IMS resources". +- If the local IMS resources configured at the IM-MGW contain more codecs than selected for the established dialogue of the final response, the MGCF should update the "local IMS resources" with the selected local codec derived from the latest SDP of this established dialogue and local configuration data. The "reserve value" may be cleared unless it is required for DTMF. + +- The IM-MGW may be configured to use the remote IP address and port information as source filter for incoming packages to prevent that early media from other early SIP dialogues interfere with the media of the established dialogue. The MGCF may also provide an IP address and port source filter that disallows early media from other early dialogues in order to prevent that such early media interfere with the media of the established dialogue. If the MGCF has provided a source filter selecting media of another SIP early dialogue, it shall remove or update this source filter. + +##### 9.2.3.4.4 Message sequence chart + +Figure 39a shows an example message sequence chart for a CS network originating Session Setup with ISUP, where forking occurs. + + + +``` + +sequenceDiagram + participant IM-MGW + participant MGCF + + Note left of IM-MGW: Reserve TDM Circuit, +Change Through- +Connection = both + IM-MGW->>MGCF: 1. ISUP: IAM + MGCF-->>IM-MGW: 2. H.248: ADD.req [Context ID = ?, Termination ID = ?] + IM-MGW-->>MGCF: 3. H.248: ADD.resp [Context ID = C1, Termination ID = T2] + Note left of IM-MGW: Reserve IMS Connection Point, +Change IMS Through- +Connection = backward + IM-MGW->>MGCF: 4. H.248: ADD.req [Context ID = C1, Termination ID=?] + MGCF-->>IM-MGW: 5. H.248: ADD.resp [Context ID = C1, Termination ID = T1] + MGCF->>X: 6. SIP: INVITE + X-->>MGCF: 7. SIP: 100 Trying + X-->>MGCF: 8. SIP: 183 Session Progress (to:xxx, tagA) + Note left of IM-MGW: Configure IMS Resources + IM-MGW->>MGCF: 9. H.248: MOD.req [Context ID = C1, Termination ID = T1] + MGCF-->>IM-MGW: 10. H.248: MOD.resp [Context ID = C1, Termination ID = T1] + MGCF->>X: 11. SIP: PRACK (to:xxx, tagA) + X-->>MGCF: 12. SIP: 200 OK (PRACK) (to:xxx, tagA) + X-->>MGCF: 13. SIP: 183 Session Progress (to:xxx, tagB) + Note left of IM-MGW: Configure IMS Resources + IM-MGW->>MGCF: 14. H.248: MOD.req [Context ID = C1, Termination ID = T1] + MGCF-->>IM-MGW: 15. H.248: MOD.resp [Context ID = C1, Termination ID = T1] + MGCF->>X: 16. SIP: PRACK (to:xxx, tagB) + X-->>MGCF: 17. SIP: 200 OK (PRACK) (to:xxx, tagB) + IM-MGW->>MGCF: 18. ISUP: COT + MGCF->>X: 19. SIP: UPDATE (to:xxx, tagA) + X-->>MGCF: 20. SIP: UPDATE (to:xxx, tagB) + X-->>MGCF: 21. SIP: 200 OK (UPDATE) (to: xxx, tagA) + X-->>MGCF: 22. SIP: 200 OK (UPDATE) (to: xxx, tagB) + +``` + +Sequence diagram for CS Network Originating Session with forking, ISUP. Lifelines: IM-MGW and MGCF. The diagram shows a series of messages between the two entities, with annotations for actions like 'Reserve TDM Circuit', 'Configure IMS Resources', and 'Reserve IMS Connection Point'. + +Figure 39a/1: CS Network Originating Session with forking, ISUP (message sequence chart) + + + +Sequence diagram illustrating the CS Network Originating Session with forking, ISUP (message sequence chart continue). + +The diagram shows interactions between the IM-MGW and the MGCF. + +External SIP messages received by the MGCF: + +- 23. **SIP** :180 Ringing (to:xxx, tagB) +- 24. **SIP** : PRACK (to:xxx, tagB) +- 25. **SIP** :200 OK (PRACK) (to:xxx, tagB) + +ISUP message sent from the MGCF to the IM-MGW: + +- 26. **ISUP** : ACM + +H.248 messages exchanged between the MGCF and the IM-MGW: + +- 27. **H.248** : MOD.req [Context ID = C1, Termination ID = T2] (MGCF to IM-MGW) +- 28. **H.248** : MOD.resp [Context ID = C1, Termination ID = T2] (IM-MGW to MGCF) +- 33. **H.248** : MOD.req [Context ID=C1, Termination ID = T2] (MGCF to IM-MGW) +- 34. **H.248** : MOD.resp [Context ID = C1, Termination ID = T2] (IM-MGW to MGCF) +- 35. **H.248** : MOD.req [Context ID=C1, Termination ID = T1] (MGCF to IM-MGW) +- 36. **H.248** : MOD.resp [Context ID = C1, Termination ID = T1] (IM-MGW to MGCF) + +Additional SIP messages received by the MGCF: + +- 29. **SIP** :180 Ringing (to:xxx, tagA) +- 30. **SIP** : PRACK (to:xxx, tagA) +- 31. **SIP** :200 OK (PRACK) (to:xxx, tagA) +- 32. **SIP** :200 OK (INVITE) (to:xxx, tagA) + +IM-MGW actions: + +- Send TDM Tone (triggered by message 27) +- Stop TDM Tone , Activate TDM Voice Processing Function (triggered by message 33) +- Configure IMS Resources, Change IMS Through-Connection = both (triggered by message 35) + +ISUP message sent from the MGCF to the IM-MGW: + +- 37. **ISUP** : ANM + +External SIP message sent from the MGCF: + +- 38. **SIP** : ACK + +The period from message 27 to message 37 is labeled as **CALL IN ACTIVE STATE**. + +Sequence diagram for CS Network Originating Session with forking. Lifelines: IM-MGW and MGCF. The diagram shows a series of messages between the MGCF and external entities, and between the MGCF and IM-MGW. The MGCF receives SIP 180 Ringing, PRACK, and 200 OK (PRACK) from an external source. The MGCF then sends ISUP ACM to the IM-MGW. The MGCF sends H.248 MOD.req to the IM-MGW, which responds with H.248 MOD.resp. The MGCF then sends another SIP 180 Ringing, PRACK, and 200 OK (PRACK) to another external source. The MGCF sends H.248 MOD.req to the IM-MGW, which responds with H.248 MOD.resp. The MGCF then sends H.248 MOD.req to the IM-MGW, which responds with H.248 MOD.resp. The MGCF sends ISUP ANM to the IM-MGW. Finally, the MGCF sends SIP ACK to the external source. A bracket at the bottom indicates the 'CALL IN ACTIVE STATE' from the first H.248 MOD.req to the ISUP ANM. + +Figure 39a/2: CS Network Originating Session with forking, ISUP (message sequence chart continue) + +### 9.2.4 Session release initiated from IM CN subsystem side + +#### 9.2.4.1 BICC + +##### 9.2.4.1.1 Session release in the IM CN subsystem side + +When the MGCF has received a BYE message from the IM CN subsystem side, the MGCF shall release resources in the IM-MGW serving the relevant Mb interface connection by using the "Release IMS Termination" procedure (signals 5 and 6 in figure 40). After receiving the BYE message, the MGCF shall also send a 200 OK [BYE] message towards the IM CN subsystem (signal 2 in figure 40). + +##### 9.2.4.1.2 Session release in the CS network side + +When the MGCF has received a BYE message from the IM CN subsystem side, the MGCF shall send a REL message to the succeeding node (signal 3 in figure 40). Once the succeeding node has responded with the RLC message (signal 6 in figure 40), the MGCF shall release the resources for the CS network side in the IM-MGW. If any resources were seized in the IM-MGW, the MGCF shall use the "Release Bearer", "Change Through-Connection" and "Release Termination" procedures (signals 7 to 10 in figure 40) to indicate to the IM-MGW that the CS network side bearer termination shall be removed and the bearer shall be released towards the succeeding MGW. + +##### 9.2.4.1.3 Message sequence chart + +Figure 40 shows the message sequence chart for the session release initiated from the IM CN subsystem side. + +![Figure 40: Session release from IM CN subsystem side for BICC (message sequence chart). The diagram shows a sequence of messages between the MGCF and the IM-MGW. The sequence starts with a SIP: BYE from the IM CN subsystem to the MGCF, followed by a SIP: 200 OK [BYE] from the MGCF back to the IM CN subsystem. Then, the MGCF sends a BICC: REL to the succeeding node, which responds with a BICC: RLC. The MGCF then initiates the 'Release IMS Termination' procedure with H.248: SUB.req and H.248: SUB.resp messages. Next, the 'Release Bearer, Change Through-Connection = backward' procedure is initiated with H.248: MOD.req and H.248: MOD.resp messages. Finally, the 'Release Termination' procedure is initiated with H.248: SUB.req and H.248: SUB.resp messages.](e38206fcefa2045af01d494b2956775a_img.jpg) + +``` + +sequenceDiagram + participant IM_CN as IM CN subsystem + participant MGCF + participant IM_MGW as IM-MGW + Note right of MGCF: Release IMS Termination + Note right of MGCF: Release Bearer, Change Through-Connection = backward + Note right of MGCF: Release Termination + + IM_CN->>MGCF: 1. SIP: BYE + MGCF-->>IM_CN: 2. SIP: 200 OK [BYE] + MGCF->>IM_MGW: 3. BICC: REL + IM_MGW-->>MGCF: 4. BICC: RLC + MGCF->>IM_MGW: 5. H.248: SUB.req [Context ID = C1, Termination ID = T1] + IM_MGW-->>MGCF: 6. H.248: SUB.resp [Context ID = C1, Termination ID = T1] + MGCF->>IM_MGW: 7. H.248: MOD.req [Context ID = C1, Termination ID = T2] + IM_MGW-->>MGCF: 8. H.248: MOD.resp [Context ID = C1, Termination ID = T2] + MGCF->>IM_MGW: 9. H.248: SUB.req [Context ID = C1, Termination ID = T2] + IM_MGW-->>MGCF: 10. H.248: SUB.resp [Context ID = C1, Termination ID = T2] + +``` + +Figure 40: Session release from IM CN subsystem side for BICC (message sequence chart). The diagram shows a sequence of messages between the MGCF and the IM-MGW. The sequence starts with a SIP: BYE from the IM CN subsystem to the MGCF, followed by a SIP: 200 OK [BYE] from the MGCF back to the IM CN subsystem. Then, the MGCF sends a BICC: REL to the succeeding node, which responds with a BICC: RLC. The MGCF then initiates the 'Release IMS Termination' procedure with H.248: SUB.req and H.248: SUB.resp messages. Next, the 'Release Bearer, Change Through-Connection = backward' procedure is initiated with H.248: MOD.req and H.248: MOD.resp messages. Finally, the 'Release Termination' procedure is initiated with H.248: SUB.req and H.248: SUB.resp messages. + +Figure 40: Session release from IM CN subsystem side for BICC (message sequence chart) + +#### 9.2.4.2 ISUP + +##### 9.2.4.2.1 Session release in the IM CN subsystem side + +When the MGCF has received a BYE message from the IM CN subsystem side, the MGCF shall release resources in the IM-MGW serving the relevant Mb interface connection by using the "Release IMS Termination" procedure (signals 4 and 5 in figure 41). After receiving the BYE message, the MGCF shall also send a 200 OK [BYE] message towards the IM CN subsystem (signal 2 in figure 41). + +##### 9.2.4.2.2 Session release in the CS network side + +When the MGCF has received a BYE message from the IM CN subsystem side, the MGCF shall send a REL message to the succeeding node (signal 3 in figure 41). After sending the REL message, the MGCF shall expect a RLC message (signal 8 in figure 41) from the succeeding node. The MGCF shall also release the resources for the CS network side in the IM-MGW. If any resources were seized in the IM-MGW, the MGCF shall use the "Release TDM Termination" procedure (signals 6 to 7 in figure 41) to indicate to the IM-MGW that the CS network side bearer termination can be released. + +##### 9.2.4.2.3 Message sequence chart + +Figure 41 shows the message sequence chart for the session release initiated from the IM CN subsystem side. + +![Figure 41: Session release from IM CN subsystem side for ISUP (message sequence chart). The diagram shows a sequence of messages between the MGCF and the IM-MGW. The sequence starts with a SIP: BYE from the IM CN subsystem to the MGCF. The MGCF responds with a SIP: 200 OK [BYE] to the IM CN subsystem. The MGCF then sends an ISUP: REL message to the IM-MGW. The MGCF then initiates the 'Release IMS Termination' procedure with the IM-MGW via H.248 SUB.req and SUB.resp messages. The MGCF then initiates the 'Release TDM Termination' procedure with the IM-MGW via H.248 SUB.req and SUB.resp messages. Finally, the MGCF receives an ISUP: RLC message from the IM-MGW.](257c8341b41f1f4a287f27d33227974c_img.jpg) + +``` +sequenceDiagram + participant IM_CN as IM CN subsystem + participant MGCF + participant IM-MGW + Note left of MGCF: Release IMS Termination + Note left of MGCF: Release TDM Termination + IM_CN->>MGCF: 1. SIP: BYE + MGCF-->>IM_CN: 2. SIP: 200 OK [BYE] + MGCF->>IM-MGW: 3. ISUP: REL + MGCF->>IM-MGW: 4. H.248: SUB.req [Context ID = C1, Termination ID = T1] + IM-MGW-->>MGCF: 5. H.248: SUB.resp [Context ID = C1, Termination ID = T1] + MGCF->>IM-MGW: 6. H.248: SUB.req [Context ID = C1, Termination ID = T2] + IM-MGW-->>MGCF: 7. H.248: SUB.resp [Context ID = C1, Termination ID = T2] + IM-MGW->>MGCF: 8. ISUP: RLC +``` + +Figure 41: Session release from IM CN subsystem side for ISUP (message sequence chart). The diagram shows a sequence of messages between the MGCF and the IM-MGW. The sequence starts with a SIP: BYE from the IM CN subsystem to the MGCF. The MGCF responds with a SIP: 200 OK [BYE] to the IM CN subsystem. The MGCF then sends an ISUP: REL message to the IM-MGW. The MGCF then initiates the 'Release IMS Termination' procedure with the IM-MGW via H.248 SUB.req and SUB.resp messages. The MGCF then initiates the 'Release TDM Termination' procedure with the IM-MGW via H.248 SUB.req and SUB.resp messages. Finally, the MGCF receives an ISUP: RLC message from the IM-MGW. + +Figure 41: Session release from IM CN subsystem side for ISUP (message sequence chart) + +### 9.2.5 Session release initiated from CS network side + +#### 9.2.5.1 BICC + +##### 9.2.5.1.1 Session release in the CS network side + +When the MGCF receives a REL message from the preceding node (signal 1 in figure 42), the MGCF shall release resources for the CS network side in the IM-MGW. If any resources were seized in the IM-MGW, the MGCF shall use the "Release Bearer", "Change Through-Connection" and "Release Termination" procedures to indicate to the IM-MGW that the CS network side bearer termination shall be removed and the bearer shall be released towards the preceding MGW (signal 3 to 6 in figure 42). After completion of resource release, the MGCF shall send a RLC message towards the preceding node. + +##### 9.2.5.1.2 Session release in the IM CN subsystem side + +When the MGCF receives a REL message from the preceding node (signal 1 in figure 42), the MGCF shall send a BYE message to the IM CN subsystem (signal 2 in figure 42) and the MGCF shall release the resources in the IM-MGW serving the relevant Mb interface connection by using the "Release IMS Termination" procedure (signals 7 and 8 in figure 42). The MGCF shall also expect to receive a 200 OK [BYE] message from the IM CN subsystem side (signal 10 in figure 42). + +##### 9.2.5.1.3 Message sequence chart + +Figure 42 shows the message sequence chart for the session release initiated from the CS network side. + +![Figure 42: Session release from CS network side for BICC (message sequence chart). The diagram shows a sequence of messages between an IM-MGW and an MGCF. The sequence starts with a BICC REL message from the IM-MGW to the MGCF. The MGCF then sends a SIP BYE message to the right. Next, the MGCF sends an H.248 MOD.req message to the IM-MGW, which is labeled 'Release Bearer, Change Through-Connection = backward'. The IM-MGW responds with an H.248 MOD.resp. Then, the MGCF sends an H.248 SUB.req message, labeled 'Release Termination', which the IM-MGW responds to with an H.248 SUB.resp. Next, the MGCF sends another H.248 SUB.req message, labeled 'Release IMS Termination', which the IM-MGW responds to with an H.248 SUB.resp. Finally, the MGCF sends a BICC RLC message to the left, and the IM-MGW responds with a SIP 200 OK [BYE] message to the MGCF.](9f862801bce82634d3b5a1e0a195a799_img.jpg) + +``` + +sequenceDiagram + participant IM-MGW + participant MGCF + Note left of IM-MGW: Release Bearer, Change Through-Connection = backward + IM-MGW->>MGCF: 1. BICC: REL + MGCF->>right: 2. SIP: BYE + MGCF->>IM-MGW: 3. H.248: MOD.req [Context ID = C1, Termination ID = T2] + IM-MGW-->>MGCF: 4. H.248: MOD.resp [Context ID = C1, Termination ID = T2] + Note left of IM-MGW: Release Termination + MGCF->>IM-MGW: 5. H.248: SUB.req [Context ID = C1, Termination ID = T2] + IM-MGW-->>MGCF: 6. H.248: SUB.resp [Context ID = C1, Termination ID = T2] + Note left of IM-MGW: Release IMS Termination + MGCF->>IM-MGW: 7. H.248: SUB.req [Context ID = C1, Termination ID = T1] + IM-MGW-->>MGCF: 8. H.248: SUB.resp [Context ID = C1, Termination ID = T1] + MGCF->>left: 9. BICC: RLC + IM-MGW-->>MGCF: 10. SIP: 200 OK [BYE] + +``` + +Figure 42: Session release from CS network side for BICC (message sequence chart). The diagram shows a sequence of messages between an IM-MGW and an MGCF. The sequence starts with a BICC REL message from the IM-MGW to the MGCF. The MGCF then sends a SIP BYE message to the right. Next, the MGCF sends an H.248 MOD.req message to the IM-MGW, which is labeled 'Release Bearer, Change Through-Connection = backward'. The IM-MGW responds with an H.248 MOD.resp. Then, the MGCF sends an H.248 SUB.req message, labeled 'Release Termination', which the IM-MGW responds to with an H.248 SUB.resp. Next, the MGCF sends another H.248 SUB.req message, labeled 'Release IMS Termination', which the IM-MGW responds to with an H.248 SUB.resp. Finally, the MGCF sends a BICC RLC message to the left, and the IM-MGW responds with a SIP 200 OK [BYE] message to the MGCF. + +Figure 42: Session release from CS network side for BICC (message sequence chart) + +#### 9.2.5.2 ISUP + +##### 9.2.5.2.1 Session release in the CS network side + +When the MGCF receives a REL message from the preceding node (signal 1 in figure 43), the MGCF shall release resources for the CS network side in the IM-MGW. If any resources were seized in the IM-MGW, the MGCF shall use the "Release TDM Termination procedures" to indicate to the IM-MGW that the CS network side bearer termination can be released (signal 3 to 4 in figure 43). After completion of resource release, the MGCF shall send a RLC message towards the preceding node. + +##### 9.2.5.2.2 Session release in the IM CN subsystem side + +When the MGCF receives a REL message from the preceding node (signal 1 in figure 43), the MGCF shall send a BYE message to the IM CN subsystem (signal 2 in figure 43) and the MGCF shall release the resources in the IM-MGW serving the relevant Mb interface connection by using the "Release IMS Termination" procedure (signal 5 to 6 in figure 43). The MGCF shall also expect to receive a 200 OK [BYE] message from the IM CN subsystem side (signal 8 in figure 43). + +##### 9.2.5.2.3 Message sequence chart + +Figure 43 shows the message sequence chart for the session release initiated from the CS network side. + +![Figure 43: Session release from CS network side for ISUP (message sequence chart). The diagram shows a sequence of messages between an IM-MGW and an MGCF. The sequence starts with the IM-MGW sending a 1. ISUP: REL message to the MGCF. The MGCF responds with a 2. SIP: BYE message. The IM-MGW then sends a 3. H.248: SUB.req [Context ID = C1, Termination ID = T2] message to the MGCF. The MGCF responds with a 4. H.248: SUB.resp [Context ID = C1, Termination ID = T2] message. The IM-MGW then sends a 5. H.248: SUB.req [Context ID = C1, Termination ID = T1] message to the MGCF. The MGCF responds with a 6. H.248: SUB.resp [Context ID = C1, Termination ID = T1] message. The IM-MGW then sends a 7. ISUP: RLC message to the MGCF. The MGCF responds with a 8. SIP: 200 OK [BYE] message. The diagram also includes labels for 'Release TDM Termination' and 'Release IMS Termination'.](0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg) + +``` + +sequenceDiagram + participant IM-MGW + participant MGCF + Note left of IM-MGW: Release TDM Termination + IM-MGW->>MGCF: 1. ISUP: REL + MGCF->>External: 2. SIP: BYE + MGCF->>IM-MGW: 3. H.248: SUB.req [Context ID = C1, Termination ID = T2] + IM-MGW->>MGCF: 4. H.248: SUB.resp [Context ID = C1, Termination ID = T2] + Note left of IM-MGW: Release IMS Termination + IM-MGW->>MGCF: 5. H.248: SUB.req [Context ID = C1, Termination ID = T1] + MGCF->>IM-MGW: 6. H.248: SUB.resp [Context ID = C1, Termination ID = T1] + IM-MGW->>External: 7. ISUP: RLC + MGCF->>External: 8. SIP: 200 OK [BYE] + +``` + +Figure 43: Session release from CS network side for ISUP (message sequence chart). The diagram shows a sequence of messages between an IM-MGW and an MGCF. The sequence starts with the IM-MGW sending a 1. ISUP: REL message to the MGCF. The MGCF responds with a 2. SIP: BYE message. The IM-MGW then sends a 3. H.248: SUB.req [Context ID = C1, Termination ID = T2] message to the MGCF. The MGCF responds with a 4. H.248: SUB.resp [Context ID = C1, Termination ID = T2] message. The IM-MGW then sends a 5. H.248: SUB.req [Context ID = C1, Termination ID = T1] message to the MGCF. The MGCF responds with a 6. H.248: SUB.resp [Context ID = C1, Termination ID = T1] message. The IM-MGW then sends a 7. ISUP: RLC message to the MGCF. The MGCF responds with a 8. SIP: 200 OK [BYE] message. The diagram also includes labels for 'Release TDM Termination' and 'Release IMS Termination'. + +Figure 43: Session release from CS network side for ISUP (message sequence chart) + +### 9.2.6 Session release initiated by MGCF + +#### 9.2.6.1 BICC + +##### 9.2.6.1.1 Session release in the CS network side + +The MGCF shall send a REL message to the succeeding node on the CS network side (signal 1 in figure 44). Once the succeeding node has responded with the RLC message (signal 3 in figure 44), the MGCF shall release the resources for the CS network side in the IM-MGW. If any resources were seized in the IM-MGW, the MGCF shall use the "Release Bearer", "Change Through-Connection" and "Release Termination" procedures to indicate to the IM-MGW that the CS network side bearer termination shall be removed and the bearer shall be released towards the succeeding MGW (signal 4 to 7 in figure 44). + +##### 9.2.6.1.2 Session release in the IM CN subsystem side + +The MGCF shall send a BYE message to the IM CN subsystem side (signal 2 in figure 44) and the MGCF shall release the resources in the IM-MGW serving the relevant Mb interface connection by using the "Release IMS Termination" procedure (signals 8 and 9 in figure 44). The MGCF shall also expect to receive a 200 OK [BYE] message is received from the IM CN subsystem side (signal 10 in figure 44). + +##### 9.2.6.1.3 Message sequence chart + +Figure 44 shows the message sequence chart for the session release initiated by the MGCF. + +![Figure 44: Session release initiated by MGCF for BICC (message sequence chart). The diagram shows a sequence of messages between MGCF and IM-MGW. The sequence starts with MGCF sending a BICC: REL message to IM-MGW (1). MGCF then sends a SIP: BYE message to an external entity (2). IM-MGW responds with a BICC: RLC message (3). MGCF then sends a series of H.248 messages to IM-MGW: MOD.req [Context ID = C1, Termination ID = T2] (4), MOD.resp [Context ID = C1, Termination ID = T2] (5), SUB.req [Context ID = C1, Termination ID = T2] (6), SUB.resp [Context ID = C1, Termination ID = T2] (7), SUB.req [Context ID = C1, Termination ID = T1] (8), and SUB.resp [Context ID = C1, Termination ID = T1] (9). Finally, MGCF receives a SIP: 200 OK [BYE] message (10). Annotations on the left indicate 'Release Bearer, Change Through-Connection = backward' for messages 4-5, 'Release Termination' for messages 6-7, and 'Release IMS Termination' for messages 8-9.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +``` + +sequenceDiagram + participant MGCF + participant IM-MGW + Note left of MGCF: Release Bearer, Change Through-Connection = backward + MGCF->>IM-MGW: 1. BICC: REL + MGCF->>External: 2. SIP: BYE + IM-MGW->>MGCF: 3. BICC: RLC + MGCF->>IM-MGW: 4. H.248: MOD.req [Context ID = C1, Termination ID = T2] + IM-MGW->>MGCF: 5. H.248: MOD.resp [Context ID = C1, Termination ID = T2] + Note left of MGCF: Release Termination + MGCF->>IM-MGW: 6. H.248: SUB.req [Context ID = C1, Termination ID = T2] + IM-MGW->>MGCF: 7. H.248: SUB.resp [Context ID = C1, Termination ID = T2] + Note left of MGCF: Release IMS Termination + MGCF->>IM-MGW: 8. H.248: SUB.req [Context ID = C1, Termination ID = T1] + IM-MGW->>MGCF: 9. H.248: SUB.resp [Context ID = C1, Termination ID = T1] + External->>MGCF: 10. SIP: 200 OK [BYE] + +``` + +Figure 44: Session release initiated by MGCF for BICC (message sequence chart). The diagram shows a sequence of messages between MGCF and IM-MGW. The sequence starts with MGCF sending a BICC: REL message to IM-MGW (1). MGCF then sends a SIP: BYE message to an external entity (2). IM-MGW responds with a BICC: RLC message (3). MGCF then sends a series of H.248 messages to IM-MGW: MOD.req [Context ID = C1, Termination ID = T2] (4), MOD.resp [Context ID = C1, Termination ID = T2] (5), SUB.req [Context ID = C1, Termination ID = T2] (6), SUB.resp [Context ID = C1, Termination ID = T2] (7), SUB.req [Context ID = C1, Termination ID = T1] (8), and SUB.resp [Context ID = C1, Termination ID = T1] (9). Finally, MGCF receives a SIP: 200 OK [BYE] message (10). Annotations on the left indicate 'Release Bearer, Change Through-Connection = backward' for messages 4-5, 'Release Termination' for messages 6-7, and 'Release IMS Termination' for messages 8-9. + +Figure 44: Session release initiated by MGCF for BICC (message sequence chart) + +#### 9.2.6.2 ISUP + +##### 9.2.6.2.1 Session release in the CS network side + +The MGCF shall send a REL message to the succeeding node on the CS network side (signal 2 in figure 45) and the MGCF shall release the resources for the CS network side in the IM-MGW. If any resources were seized in the IM-MGW, the MGCF shall use the "Release TDM Termination" procedure to indicate to the IM-MGW that the CS network side termination shall be released (signal 5 to 6 in figure 45). The MGCF shall also expect to receive a RLC message from the succeeding node on the CS network side (signal 7 in figure 45). + +##### 9.2.6.2.2 Session release in the IM CN subsystem side + +The MGCF shall send a BYE message to the IM CN subsystem side (signal 1 in figure 45) and the MGCF shall release the resources in the IM-MGW serving the relevant Mb interface connection by using the "Release IMS Termination" procedure (signal 5 to 6 in figure 45). The MGCF shall also expect to receive a 200 OK [BYE] message from the IM CN subsystem side (signal 8 in figure 45). + +##### 9.2.6.2.3 Message sequence chart + +Figure 45 shows the message sequence chart for the session release initiated by the MGCF. + +![Figure 45: Session release initiated by MGCF for ISUP (message sequence chart). The diagram shows a sequence of messages between an MGCF and an IM-MGW. The sequence starts with the MGCF sending a SIP: BYE message to an external entity. The IM-MGW responds with an ISUP: REL message. The MGCF then sends an H.248: SUB.req message to the IM-MGW, which responds with an H.248: SUB.resp. The MGCF then sends another H.248: SUB.req message to the IM-MGW, which responds with an H.248: SUB.resp. The MGCF then sends an ISUP: RLC message to the IM-MGW. Finally, the MGCF receives a SIP: 200 OK [BYE] message from the external entity. The diagram also includes labels for 'Release IMS Termination' and 'Release TDM Termination'.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +``` + +sequenceDiagram + participant MGCF + participant IM-MGW + Note left of MGCF: Release IMS Termination + MGCF->>External: 1. SIP: BYE + IM-MGW->>External: 2. ISUP: REL + MGCF->>IM-MGW: 3. H.248: SUB.req [Context ID = C1, Termination ID = T1] + IM-MGW-->>MGCF: 4. H.248: SUB.resp [Context ID = C1, Termination ID = T1] + Note left of MGCF: Release TDM Termination + MGCF->>IM-MGW: 5. H.248: SUB.req [Context ID = C1, Termination ID = T2] + IM-MGW-->>MGCF: 6. H.248: SUB.resp [Context ID = C1, Termination ID = T2] + IM-MGW->>External: 7. ISUP: RLC + External->>MGCF: 8. SIP: 200 OK [BYE] + +``` + +Figure 45: Session release initiated by MGCF for ISUP (message sequence chart). The diagram shows a sequence of messages between an MGCF and an IM-MGW. The sequence starts with the MGCF sending a SIP: BYE message to an external entity. The IM-MGW responds with an ISUP: REL message. The MGCF then sends an H.248: SUB.req message to the IM-MGW, which responds with an H.248: SUB.resp. The MGCF then sends another H.248: SUB.req message to the IM-MGW, which responds with an H.248: SUB.resp. The MGCF then sends an ISUP: RLC message to the IM-MGW. Finally, the MGCF receives a SIP: 200 OK [BYE] message from the external entity. The diagram also includes labels for 'Release IMS Termination' and 'Release TDM Termination'. + +Figure 45: Session release initiated by MGCF for ISUP (message sequence chart) + +### 9.2.7 Session release initiated by IM-MGW + +#### 9.2.7.1 BICC + +##### 9.2.7.1.1 Session release in the CS network side + +Upon receiving from the IM-MGW a "Bearer Released" procedure (signal 1a and 2a in figure 46) or "IMS Bearer Released" procedure (signal 1b and 2b in figure 46) or a "MGW Out-of-Service" procedure indicating an immediate release (H248 ServiceChangeMethod="Forced") (not depicted in figure 46), the MGCF shall send a REL message to the succeeding node on the CS network side (signal 3 in figure 46). Once the succeeding node has responded with the RLC message (signal 5 in figure 46), the MGCF shall release the resources for the CS network side in the IM-MGW, unless the "MGW Out-of-Service" procedure was received. If any resources were seized in the IM-MGW, the MGCF shall use the "Release Termination" procedure to indicate to the IM-MGW that the CS network side bearer termination shall be removed (signals 6 and 7 in figure 46). + +NOTE: Other actions related to MGW Out-Of-Service procedure is defined in 3GPP TS 23.205 [27]. + +##### 9.2.7.1.2 Session release in the IM CN subsystem side + +Upon receiving from the IM-MGW a "Bearer Released" procedure (signals 1a and 2a in figure 46) or "IMS Bearer Released" procedure (signal 1b and 2b in figure 46) or a "MGW Out-of-Service" procedure indicating an immediate release (H248 ServiceChangeMethod="Forced") (not depicted in figure 46), the MGCF shall send a BYE/CANCEL message to the IM CN subsystem side (signal 4 in figure 46). Upon receiving from the IM-MGW a "Bearer Released" procedure or "IMS Bearer Released" procedure, the MGCF shall also release the resources in the IM-MGW serving the relevant Mb interface connection by using the "Release IMS Termination" procedure (signals 8 and 9 in figure 46). The MGCF shall also expect to receive a 200 OK [BYE] message from the IM CN subsystem side (signal 10 in figure 46). + +NOTE: Other actions related to MGW-Out-Of-Service procedure is defined in 3GPP TS 23.205 [27] + +##### 9.2.7.1.3 Message sequence chart + +Figure 46 shows the message sequence chart for the session release initiated by the IM-MGW. + +![Figure 46: Session release initiated by the IM-MGW for BICC (message sequence chart). The diagram shows the interaction between MGCF and IM-MGW for session release. It includes two main paths: 'Bearer Released' (signals 1a, 2a, 3, 4, 5) and 'IMS Bearer Released' (signals 1b, 2b, 3, 4, 5). The 'Release Termination' path (signals 6, 7, 8, 9, 10) shows the MGCF sending SUB.req and receiving SUB.resp, followed by a SIP 200 OK [BYE] message.](8269648391c59363ea61243864a2adf7_img.jpg) + +``` + +sequenceDiagram + participant MGCF + participant IM-MGW + Note left of MGCF: Bearer Released + MGCF->>IM-MGW: 1a. H.248: Notify.req [Context ID = C1, Termination ID = T2] + IM-MGW-->>MGCF: 2a. H.248: Notify.resp [Context ID = C1, Termination ID = T2] + Note left of MGCF: or + Note left of MGCF: IMS Bearer Released + MGCF->>IM-MGW: 1b. H.248: Notify.req [Context ID = C1, Termination ID = T1] + IM-MGW-->>MGCF: 2b. H.248: Notify.resp [Context ID = C1, Termination ID = T1] + MGCF->>IM-MGW: 3. BICC: REL + MGCF->>IM-MGW: 4. SIP: BYE + IM-MGW-->>MGCF: 5. BICC: RLC + Note left of MGCF: Release Termination + MGCF->>IM-MGW: 6. H.248: SUB.req [Context ID = C1, Termination ID = T2] + IM-MGW-->>MGCF: 7. H.248: SUB.resp [Context ID = C1, Termination ID = T2] + Note left of MGCF: Release IMS Termination + MGCF->>IM-MGW: 8. H.248: SUB.req [Context ID = C1, Termination ID = T1] + IM-MGW-->>MGCF: 9. H.248: SUB.resp [Context ID = C1, Termination ID = T1] + MGCF->>IM-MGW: 10. SIP: 200 OK [BYE] + +``` + +Figure 46: Session release initiated by the IM-MGW for BICC (message sequence chart). The diagram shows the interaction between MGCF and IM-MGW for session release. It includes two main paths: 'Bearer Released' (signals 1a, 2a, 3, 4, 5) and 'IMS Bearer Released' (signals 1b, 2b, 3, 4, 5). The 'Release Termination' path (signals 6, 7, 8, 9, 10) shows the MGCF sending SUB.req and receiving SUB.resp, followed by a SIP 200 OK [BYE] message. + +Figure 46: Session release initiated by the IM-MGW for BICC (message sequence chart) + +#### 9.2.7.2 ISUP + +##### 9.2.7.2.1 Session release in the CS network side + +Upon receiving from the IM-MGW a "Termination Out-of-Service" procedure indicating an immediate release (signals 1a and 2a in figure 47), a "Bearer Released" procedure (signals 1b and 2b in figure 47), a "IMS Bearer Released" procedure (signals 1c and 2c in figure 47) or a "MGW Out-of-Service procedure" (not depicted in figure 47) indicating an immediate release (H248 ServiceChangeMethod="Forced") the MGCF shall send a REL message to the succeeding node (signal 3 in figure 47). Upon receiving from the IM-MGW a "Termination Out-of-Service" message procedure indicating an immediate release or a "Bearer Released" procedure, the MGCF shall also release the resources for the corresponding CS network side termination(s) in the IM-MGW. If any resources were seized in the IM-MGW, the MGCF shall use the "Release TDM Termination" procedure to indicate to the IM-MGW that the CS network side bearer termination can be removed (signals 7 and 8 in figure 47). The MGCF also expects to receive a RLC message on the CS network side (signal 9 in figure 47) before the circuit is reselectable. + +NOTE: Other actions related to "MGW-Out-Of-Service" procedure are defined in 3GPP TS 23.205 [27]. + +##### 9.2.7.2.2 Session release in the IM CN subsystem side + +Upon receiving from the IM-MGW a "Termination Out-of-Service" procedure indicating an immediate release (signals 1a and 2a in figure 47) on the CS termination in the context, a "Bearer Released" procedure (signals 1b and 2b in figure 47), an "IMS Bearer Released" procedure (signals 1c and 2c in figure 47) or a "MGW Out-of-Service procedure" (not depicted in figure 47) indicating an immediate release, (H248 ServiceChangeMethod="Forced") the MGCF shall send a BYE/CANCEL message to the IM CN subsystem side (signal 4 in figure 47). Upon receiving from the IM-MGW a "Termination Out-of-Service" procedure indicating an immediate release on the CS termination in the context, a "Bearer Released" procedure or an "IMS Bearer Released" procedure, the MGCF shall also release the resources in the IM-MGW for the corresponding terminations towards the IM CN subsystem using the "Release IMS Termination" procedure (signals 5 and 6 in figure 47). The MGCF also expects to receive a 200 OK [BYE] message from the IM CN subsystem side (signal 10 in figure 47). + +NOTE: Other actions related to "MGW-Out-Of-Service" procedure are defined in 3GPP TS 23.205 [27]. + +##### 9.2.7.2.3 Message sequence chart + +Figure 47 shows the message sequence chart for the session release initiated by the IM-MGW. + +![Figure 47: Session release initiated by the IM-MGW for ISUP (message sequence chart). The diagram shows a sequence of messages between MGCF and IM-MGW. The sequence starts with IM-MGW sending a ServiceChange.req to MGCF. MGCF responds with ServiceChange.resp. Then, IM-MGW sends Notify.req to MGCF, which responds with Notify.resp. This is followed by another Notify.req and Notify.resp. Then, IM-MGW sends a REL message to MGCF. MGCF responds with a BYE message. IM-MGW then sends SUB.req to MGCF, which responds with SUB.resp. This is followed by another SUB.req and SUB.resp. Finally, IM-MGW sends a RLC message to MGCF, which responds with a 200 OK [BYE] message.](a5184899f915014fa38608754efcc9c7_img.jpg) + +``` + +sequenceDiagram + participant MGCF + participant IM-MGW + Note left of MGCF: Termination Out-of-Service +or +Bearer Released +or +IMS Bearer Released + IM-MGW->>MGCF: 1a. H.248: ServiceChange.req [Context ID = C1, Termination ID = T2] + MGCF-->>IM-MGW: 2a. H.248: ServiceChange.resp [Context ID = C1, Termination ID = T2] + IM-MGW->>MGCF: 1b. H.248: Notify.req [Context ID = C1, Termination ID = T2] + MGCF-->>IM-MGW: 2b. H.248: Notify.resp [Context ID = C1, Termination ID = T2] + IM-MGW->>MGCF: 1c. H.248: Notify.req [Context ID = C1, Termination ID = T1] + MGCF-->>IM-MGW: 2c. H.248: Notify.resp [Context ID = C1, Termination ID = T1] + IM-MGW->>MGCF: 3. ISUP: REL + MGCF-->>External: 4. SIP: BYE + Note left of MGCF: Release IMS Termination +or +Release TDM Termination + IM-MGW->>MGCF: 5. H.248: SUB.req [Context ID = C1, Termination ID = T1] + MGCF-->>IM-MGW: 6. H.248: SUB.resp [Context ID = C1, Termination ID = T1] + IM-MGW->>MGCF: 7. H.248: SUB.req [Context ID = C1, Termination ID = T2] + MGCF-->>IM-MGW: 8. H.248: SUB.resp [Context ID = C1, Termination ID = T2] + IM-MGW->>MGCF: 9. ISUP: RLC + MGCF-->>External: 10. SIP: 200 OK [BYE] + +``` + +Figure 47: Session release initiated by the IM-MGW for ISUP (message sequence chart). The diagram shows a sequence of messages between MGCF and IM-MGW. The sequence starts with IM-MGW sending a ServiceChange.req to MGCF. MGCF responds with ServiceChange.resp. Then, IM-MGW sends Notify.req to MGCF, which responds with Notify.resp. This is followed by another Notify.req and Notify.resp. Then, IM-MGW sends a REL message to MGCF. MGCF responds with a BYE message. IM-MGW then sends SUB.req to MGCF, which responds with SUB.resp. This is followed by another SUB.req and SUB.resp. Finally, IM-MGW sends a RLC message to MGCF, which responds with a 200 OK [BYE] message. + +Figure 47: Session release initiated by the IM-MGW for ISUP (message sequence chart) + +### 9.2.8 Handling of RTP telephone events + +DTMF digits, telephony tones and signals (telephone events) can be transferred using different mechanisms. For the IM CN Subsystem, 3GPP TS 24.229 [9] defines the usage of the RTP payload format defined for DTMF Digits, Telephony Tones and Telephony Signals in RFC 4733 [105]. When BICC signalling is used in the CS network, telephony signals may be sent either inband or out-of-band as defined in ITU-T Recommendation Q.1902.4 [30] and in ITU-T Recommendation Q.765.5 [35]. If ISUP signalling is used the DTMF tones are sent inband. The following paragraphs describe the Mn interface procedures to transfer DTMF between RTP format defined in RFC 4733 [105] and the CS CN. + +Before the actual usage of the telephony signals can occur the sending/receiving of telephone events need to be agreed with the SDP offer-answer mechanism defined in RFC 3264 [36]. The outcome of the negotiation can be e.g. that no telephone events are sent in RTP payload, telephone events are sent only in one direction or in both directions. If the outcome of the negotiation is that RTP payload telephone-events are sent in both directions, the IM-MGW may nevertheless be configured to interwork only mobile originated telephone-events. + +When the offer-answer mechanism based session parameters negotiation results in an agreement that telephone events are sent in the RTP payload and the needed preconditions are fulfilled, telephone events can be sent in RTP payload. This negotiation can be done at call control signalling phase or during an ongoing call. + +If the MGCF and IM-MGW support the reception and/or transmission of the RTP MIME type "telephone event" (as defined in RFC 4733 [105]) with the IMS, the following applies: + +- For CS Network Originating Sessions, the MGCF shall include the MIME type "telephone events" with default events in the first SDP offer. After the usage of telephone events is agreed in the subsequent offer-answer + +parameter exchanges and the needed preconditions defined in RFC 3312 [37] are fulfilled, telephone events can be sent as RTP payload. + +- In case of IM CN Subsystem Originating Sessions, the MGCF shall accept the MIME type "telephone events" with default events in any SDP answer when it received such an offer. + +#### 9.2.8.1 Sending DTMF digits out-of-band to CS CN (BICC) + +For the IM CN subsystem terminated session, the MGCF shall use the "Configure IMS Resources" procedure as described in clause 9.2.3. For the IM CN subsystem originating session, the MGCF shall use the "Reserve IMS Connection Point and Configure Remote Resources" procedure as described in clause 9.2.2. If DTMF is supported, the MGCF shall include "telephone event" along with the selected speech codecs within the "local IMS resources" Parameter of these procedures. The same termination shall be used to receive and transmit DTMF and speech of the same call. + +Furthermore, the MGCF shall use the "Detect IMS RTP Tel Signal" procedure to request the MGW to detect incoming telephone events from the IMS and notify the MGCF about the detected events. The MGW shall use the "Notify IMS RTP Tel Event" procedure for this notification. The termination used to receive DTMF shall be placed in the same context used for the speech of the same call. The MGCF shall request to be notified when the MGW detects the end of a digit and may also request to be notified when the MGW detects the start of a digit. An IM-MGW not supporting the notification about the detection of the start of a digit may ignore the request to provide this notification. If the IM-MGW received a "Detect IMS RTP Tel Event" procedure for a termination, the IM-MGW shall not forward inband to the CS network any DTMF received at this termination. + +Figure 48 shows an example message sequence chart when a DTMF digit is received from the IM CN subsystem in the RTP payload and the MGCF has requested to be notified only about the detection of the end of a digit. Figure 48a shows an example message sequence chart when a DTMF digit is received from the IM CN subsystem in the RTP payload and the MGCF has requested to be notified about the detection of the start and the end of a digit. + + + +Sequence diagram illustrating the activation of notification of DTMF digits received in RTP and examples of sending the digits out-of-band to CS CN. The diagram shows interactions between IM-MGW and MGCF. + +**IM-MGW** (left lifeline) and **MGCF** (right lifeline). + +**Sequence of messages:** + +- 1. H.248 Add/Mod.req** [Context ID = C1, Termination ID = T1, Codec = "telephone event, AMR", Notify IMS RTP Tel Event ("End tone detected") ] +- 2. H.248 Add/Mod.resp** [Context ID = C1, Termination ID = T1] +- 8. RTP** encoded new DTMF event (tone-event, end=0, duration=x) +- 9. RTP** encoded continued DTMF event (tone-event, end=1, duration= Duration) +- 10. H.248 Notify.ind** [Context ID = C1, Termination ID = T1, Tone-ID, Event="End tone detected", Duration] +- 11. H.248 Notify.resp** [Context ID = C1, Termination ID = T1] +- 12. BICC APM** (ActInd= Start signal notify, signal-type, duration) +- 13. BICC APM** (ActInd=Start signal ack) + +**Notes:** + +- Configure IMS Resources or Reserve IMS Connection Point and configure Remote Resources, Detect\_IMS\_RTP\_Tel\_Event +- Notify\_IMS\_RTP\_Tel\_Event +- A bracket on the right side groups messages 8 and 9 as **1 Digit**. + +Sequence diagram showing the activation of notification of DTMF digits received in RTP and examples of sending the digits out-of-band to CS CN. Lifelines: IM-MGW and MGCF. The diagram includes messages 1, 2, 8, 9, 10, 11, 12, and 13. A bracket on the right side groups messages 8 and 9 as '1 Digit'. + +Figure 48: Activation of notification of DTMF digits received in RTP and examples of sending the digits out-of-band to CS CN, a whole digit received by IM-MGW before sending further (message sequence chart) + + + +Sequence Diagram: Activation of notification of DTMF digits received in RTP + +Participants: IM-MGW, MGCF + +Sequence of messages: + +1. H.248 Add/Mod.req [Context ID = C1, Termination ID = T1, Codec = "telephone event, AMR", Notify IMS RTP Tel Event ("Start tone detected", "End tone detected") ] +2. H.248 Add/Mod.resp [Context ID = C1, Termination ID = T1] +3. RTP encoded new DTMF event (tone-event, end=0, duration=x) +4. H.248 Notify.ind [Context ID = C1, Termination ID = T1, Tone\_ID, Event="Start tone detected"] +5. H.248 Notify.resp [Context ID = C1, Termination ID = T1] +6. BICC APM (ActInd=Start signal notify, signal-type) +7. BICC APM (ActInd=Start signal ack) +8. RTP encoded new DTMF event (tone-event, end=0, duration=y) +9. RTP encoded continued DTMF event (tone-event, end=1, duration=Duration) +10. H.248 Notify.ind [Context ID = C1, Termination ID = T1, Tone-ID, Event="End tone detected", Duration] +11. H.248 Notify.resp [Context ID = C1, Termination ID = T1] +12. BICC APM (ActInd=Stop signal notify) +13. BICC APM (ActInd=Stop signal ack) + +External events and notifications: + +- Configure IMS Resources or Reserve IMS Connection Point and configure Remote Resources, Detect IMS RTP Tel Event (on IM-MGW side) +- Notify IMS RTP Tel Event (on IM-MGW side) +- 1 Digit (grouping RTP events and H.248 notifications) + +Sequence diagram showing the activation of notification of DTMF digits received in RTP. The diagram involves two main participants: IM-MGW and MGCF. The process starts with the MGCF sending an H.248 Add/Mod.req to the IM-MGW. The IM-MGW responds with H.248 Add/Mod.resp. The MGCF then sends an RTP encoded new DTMF event. The IM-MGW detects the event and sends an H.248 Notify.ind to the MGCF. The MGCF responds with H.248 Notify.resp. The IM-MGW then sends BICC APM (ActInd=Start signal notify) and BICC APM (ActInd=Start signal ack) messages. The MGCF sends another RTP encoded new DTMF event. The IM-MGW detects the event and sends an H.248 Notify.ind to the MGCF. The MGCF responds with H.248 Notify.resp. The IM-MGW then sends BICC APM (ActInd=Stop signal notify) and BICC APM (ActInd=Stop signal ack) messages. A bracket on the right side of the diagram groups the RTP events and H.248 notifications as '1 Digit'. + +**Figure 48a: Activation of notification of DTMF digits received in RTP and examples of sending the digits out-of-band to CS CN, IM-MGW starts sending the digit further when the start of the digit is recognized (message sequence chart)** + +#### 9.2.8.2 Sending and receiving DTMF digits inband to/from CS CN (ISUP or BICC) + +For the IM CN subsystem terminated session, the MGCF shall use the "Configure IMS Resources" procedure as described in clause 9.2.3. For the IM CN subsystem originating session, the MGCF shall use the "Reserve IMS Connection Point and Configure Remote Resources" procedure as described in clause 9.2.2. If DTMF is supported and the MGCF wants to configure the IM-MGW to send and receive DTMF to/from the CS network side, the MGCF shall include "telephone event" along with the selected speech codecs within the "local IMS resources" parameter of these procedures to request the MGW to detect incoming telephone events and transform them into speech signals on the CS side and shall not apply the "Detect IMS RTP Tel Event" procedure. When receiving this configuration, an MGW supporting DTMF shall detect DTMF encoded according as RTP Tel Event and transform this into DTMF tones encoded within the speech codec used at the CS CN network and may in addition optionally detect incoming telephone events received inband from the CS CN network and transform them into telephone events on the IMS side. The same termination shall be used to receive and transmit DTMF and speech of the same call. + +Figure 49 shows the message sequence chart to configure the IM-MGW to receive DTMF detection on the IMS side and transfer the DTMF inband on the CS side. When receiving this configuration, the IM-MGW may in addition optionally detect DTMF inband on the CS side and transmit DTMF on the IMS side. + + + +``` +sequenceDiagram + participant IM-MGW + participant MGCF + Note left of IM-MGW: Configure IMS Resources +Or +Reserve IMS Connection Point +and configure Remote Resources + MGCF->>IM-MGW: 1. H.248 Add/Mod.req +[Context ID = C1, Termination ID = T1, +Codec = "telephone event, AMR",] + IM-MGW-->>MGCF: 2. H.248 Add/Mod.resp [Context ID = C1, Termination ID = T1] +``` + +The diagram illustrates a message sequence between the IM-MGW and the MGCF. On the left, a text block indicates the actions to be performed: "Configure IMS Resources Or Reserve IMS Connection Point and configure Remote Resources". The sequence starts with the MGCF sending a message "1. H.248 Add/Mod.req" to the IM-MGW. This message includes parameters: Context ID = C1, Termination ID = T1, and Codec = "telephone event, AMR". The IM-MGW responds with "2. H.248 Add/Mod.resp" containing Context ID = C1 and Termination ID = T1. + +Sequence diagram showing the activation of DTMF processing between IM-MGW and MGCF. + +**Figure 49: Activation of processing of DTMF digits received in RTP for sending the digits inband to CS CN (message sequence chart)** + +#### 9.2.8.3 Receiving DTMF digits out-of-band from CS CN (BICC) + +For the IM CN subsystem terminated session, the MGCF shall use the "Configure IMS Resources" procedure as described in clause 9.2.3. For the IM CN subsystem originating session, the MGCF shall use the "Reserve IMS Connection Point and Configure Remote Resources" procedure as described in clause 9.2.2. If DTMF is supported, the MGCF shall include "telephone event" along with the selected speech codecs within the "local IMS resources" Parameter of these procedures. The same termination shall be used to receive and transmit DTMF and speech of the same call. + +Furthermore, the MGCF shall use the "Send IMS RTP Tel Event" and may use the "Stop IMS RTP Tel Event" procedures to request the MGW to play out DTMF to the IM CN subsystem whenever it receives out-of-band DTMF indications from the BICC network. + +Figure 49a shows an example message sequence chart when DTMF digits are transmitted to the IM CN subsystem in the RTP payload. For the first digit, the received APM message contains all information including the duration and only a single notification is received. For the second digit, the start and the end of the DTMF digit are notified separately. + + + +The sequence diagram illustrates the interaction between the IM-MGW and the MGCF for receiving DTMF digits out-of-band from the CS CN and transmitting them in RTP. The sequence of messages is as follows: + +- Configure IMS Resources or Reserve IMS Connection Point and configure Remote Resources, Detect IMS RTP Tel\_Event**: The IM-MGW sends an **1. H.248 Add/Mod.req** to the MGCF. The message includes Context ID = C1, Termination ID = T1, Codec = "telephone event, AMR", and Notify IMS RTP Tel Event ("Start tone detected", "End tone detected"). +- The MGCF responds with **2. H.248 Add/Mod.resp** [Context ID = C1, Termination ID = T1]. +- The MGCF sends **3. BICC APM** (ActInd=Start signal notify, signal-type, duration) to the IM-MGW. +- The IM-MGW responds with **4. BICC APM** (ActInd=Start signal ack). +- The MGCF sends **5. H.248 Mod.ind** [Context ID = C1, Termination ID = T1, Tone-Id, SignalType=Timeout, Duration] to the IM-MGW. +- The MGCF sends **6. H.248 Mod.resp** [Context ID = C1, Termination ID = T1] to the IM-MGW. +- Send IMS RTP Tel\_Event**: The MGCF sends **7. RTP** encoded new DTMF event (tone-event, end=0, duration=x) to the IM-MGW. This is followed by another **7. RTP** encoded new DTMF event (tone-event, end=1, duration=x) to the IM-MGW. The IM-MGW then sends **8. BICC APM** (ActInd=Start signal notify, signal-type) to the MGCF, which responds with **9. BICC APM** (ActInd=Start signal ack). +- The MGCF sends **10. H.248 Mod.ind** [Context ID = C1, Termination ID = T1, Tone\_ID, SignalType=On/Off] to the IM-MGW. +- Send IMS RTP Tel\_Event**: The MGCF sends **11. H.248 Mod.resp** [Context ID = C1, Termination ID = T1] to the IM-MGW. The IM-MGW then sends **12. RTP** encoded new DTMF event (tone-event, end=0, duration=x) to the MGCF, followed by **13. RTP** encoded new DTMF event (tone-event, end=0, duration=y) to the MGCF. The MGCF then sends **14. BICC APM** (ActInd=Stop signal notify) to the IM-MGW, which responds with **15. BICC APM** (ActInd=Stop signal ack). +- The MGCF sends **16. H.248 Mod.ind** [Context ID = C1, Termination ID = T1] to the IM-MGW. +- Stop IMS RTP Tel\_Event**: The MGCF sends **17. H.248 Mod.resp** [Context ID = C1, Termination ID = T1] to the IM-MGW. The IM-MGW then sends **18. RTP** encoded continued DTMF event (tone-event, end=1, duration) to the MGCF. + +Brackets on the right side of the diagram group the messages for **Digit 1** (steps 3-6) and **Digit 2** (steps 7-17). Ellipses indicate additional messages between the digits. + +Sequence diagram showing the interaction between IM-MGW and MGCF for receiving DTMF digits out-of-band from the CS CN and transmitting them in RTP. The diagram includes two digits, Digit 1 and Digit 2, with various H.248, BICC, and RTP messages exchanged between the entities. + +Figure 49a: Examples of receiving DTMF digits out-of-band from the CS CN and transmitting them in RTP (message sequence chart) + +### 9.2.9 Session hold initiated from IM CN subsystem + +The network model in the clause 9.2.1 shall apply here. + +#### Hold request + +When the IMS network makes a hold request by sending an UPDATE or re-INVITE message (signal 1 of figure 50), the MGCF shall request the IM-MGW to suspend sending media towards the IMS side by changing the through-connection of the IM CN subsystem side termination to "not through-connected" (signal 2 of figure 50). If the IMS side provides modified SDP RR or RS bandwidth modifiers, as specified in IETF RFC 3556 [59], within the hold request, the MGCF shall use the Configure IMS Resources Mn procedure to forward this information to the IM-MGW (not depicted in figure 50, but may be combined with signal 2). The MGCF shall send a CPG (Hold) message to the succeeding CS network node to indicate that the session is on hold (signal 4 of figure 50). Simultaneously a SIP message acknowledging the Hold request is sent to the IMS side (signal 7 of figure 50, acknowledged by signal 7.a if the INVITE method is used). + +If the MGCF has identified a speech call as an "ICS call" as specified in clause 7.2.3.1.2.12 or in clause 7.2.3.2.7a the MGCF shall not apply an announcement to the party on hold. Otherwise, an announcement may be applied to the party on hold, depending on the held party's status, using the Play Announcement procedure (for BICC) or the Play TDM Announcement procedure (for ISUP, signal 5 in figure 50). The hold operation shall not block RTCP flows. + +#### Resume request + +When the IMS network makes a request to retrieve the session on hold by sending an UPDATE or re-INVITE message (signal 8 of figure 50), the MGCF shall request the IM-MGW to re-establish communication towards the IMS network by changing the through-connection of the IM CN subsystem side termination to both-way through-connected (signal 11 of figure 50). If the IMS side provides modified SDP RR or RS bandwidth modifiers, as specified in IETF RFC 3556 [59], within the retrieve request, the MGCF shall use the Configure IMS Resources Mn procedure to forward this information to the IM-MGW (not depicted in figure 50, but may be combined with signal 11). Possible announcements to the party on hold shall be stopped using the Stop Announcement procedure (for BICC) or the Stop TDM Announcement procedure (for ISUP, signal 9 in figure 50). The MGCF shall send a CPG (Retrieve) message to the succeeding CS network node to indicate that the session is retrieved (signal 13 of figure 50). + +#### Message sequence chart + +Figure 50 shows the message sequence chart for the call hold and retrieval procedures. + + + +``` + +sequenceDiagram + participant External + participant MGCF + participant IM-MGW + + Note left of MGCF: Change Through-Connection=Inactive + External->>MGCF: 1. SIP: UPDATE/INVITE [SDP, a=sendonly/inactive] + MGCF->>IM-MGW: 2. H.248: MOD.req [Context ID = C1, Termination ID = T1] + IM-MGW-->>MGCF: 3. H.248: MOD.resp [Context ID = C1, Termination ID = T1] + MGCF->>External: 4. BICC/ISUP: CPG (Hold) + Note left of MGCF: Play TDM Announcement + MGCF->>IM-MGW: 5. H.248: MOD.req [Context ID = C1, Termination ID = T2] + IM-MGW-->>MGCF: 6. H.248: MOD.resp [Context ID = C1, Termination ID = T2] + MGCF-->>External: 7. SIP: 200 OK [SDP] + Note left of MGCF: + External-->>MGCF: 7.a SIP: ACK (if INVITE is used) + Note left of MGCF: Stop TDM Announcement + External->>MGCF: 8. SIP: UPDATE/INVITE [SDP, a=sendrecv/recvonly] + MGCF->>IM-MGW: 9. H.248: MOD.req [Context ID = C1, Termination ID = T2] + IM-MGW-->>MGCF: 10. H.248: MOD.resp [Context ID = C1, Termination ID = T2] + MGCF->>IM-MGW: 11. H.248: MOD.req [Context ID = C1, Termination ID = T1] + IM-MGW-->>MGCF: 12. H.248: MOD.resp [Context ID = C1, Termination ID = T1] + Note left of MGCF: Change Through-Connection=Both + MGCF->>External: 13. BICC/ISUP: CPG (Retrieve) + MGCF-->>External: 14. SIP: 200 OK [SDP] + Note left of MGCF: + External-->>MGCF: 14.a SIP: ACK (if INVITE is used) + +``` + +Sequence diagram showing session hold and resume from IM CN subsystem between MGCF and IM-MGW. + +NOTE: For an "ICS call" signals 5, 6, 9 and 10 will not be sent since the MGCF will not request an announcement from the IM-MGW. + +**Figure 50: Session hold/resume from IM CN subsystem** + +### 9.2.10 Session hold initiated from CS network + +When an MGCF receives a CPG message with a "*remote hold*" Generic notification indicator (signal 1 of figure 51), the MGCF forwards the hold request by sending an UPDATE or re-INVITE message containing SDP with "*sendonly*" or "*inactive*" media (signal 4 of figure 51). + +When an MGCF receives a CPG message with a "*remote retrieval*" Generic notification indicator (signal 6 of figure 51), the MGCF forwards the resume request by sending an UPDATE or re-INVITE message containing SDP with "*sendrecv*" or "*recvonly*" media (signal 9 of figure 51). + +If the MGCF receives a CPG with "*remote hold*" or "*remote retrieval*" before answer, it shall forward the request using an UPDATE message. If the MGCF receives a CPG with "*remote hold*" or "*remote retrieval*" after answer, it should forward the request using re-INVITE but may use UPDATE. + +If link aliveness information is required at the IM-MGW while the media are on hold, and RTCP was previously disabled the MGCF should provide to the modified SDP RR and RS bandwidth modifiers specified in + +IETF RFC 3556 [59] within the SDP offers in the UPDATE or re-INVITE messages holding and retrieving the media as detailed in clause 7.3.1 of 3GPP TS 26.114 [104]. If no link aliveness information is required at the IM-MGW or RTCP was previously enabled, the MGCF should provide the SDP RR and RS bandwidth modifiers previously used. + +The interworking does not impact the user plane, unless the MGCF: + +- provides modified SDP RR and RS bandwidth modifiers in the UPDATE or re-INVITE messages. If the MGCF provides modified SDP RR and RS bandwidth modifiers in the UPDATE or re-INVITE messages, the MGCF shall also provide modified SDP RR and RS bandwidths to the IM-MGW using the Configure IMS Resources procedures (signals 2-3 and 7-8 of figure 51); or +- has identified a speech call as an "ICS call" as specified in clause 7.2.3.1.2.12 or in clause 7.2.3.2.7a. When the MGCF receives from the CS network: + - a) a hold request the MGCF shall request the IM-MGW to suspend sending media towards the IMS side by changing the through-connection of the IM CN subsystem side termination to "not through-connected" (not depicted in figure 51, but may be combined with signal 2) prior to sending of the UPDATE or re-INVITE message containing the SDP offer with "*sendonly*" or "*inactive*" media; + - b) a request to retrieve the session on hold and if the MGCF requested the IM-MGW to suspend sending media on the hold request the MGCF shall request the IM-MGW to re-establish communication towards the IMS network by changing the through-connection of the IM CN subsystem side termination to "both-way through-connected" (not depicted in figure 51, but may be combined with signal 7) prior to sending of the UPDATE or re-INVITE message containing the SDP offer with "*sendrecv*" or "*recvonly*" media; or +- has received for a confirmed dialog towards IMS side the Contact header (in the initial INVITE request or in the 200 OK (INVITE) response) with the "*isfocus*" media feature tag, defined in IETF RFC 3840 [135]. When the MGCF receives from the CS network: + - a) a hold request the MGCF shall request the IM-MGW to suspend sending media towards the IMS side by changing the through-connection of the IM CN subsystem side termination to "not through-connected" (not depicted in figure 51, but may be combined with signal 2) prior to sending of the UPDATE or re-INVITE message containing the SDP offer with "*sendonly*" or "*inactive*" media; or + - b) a request to retrieve the session on hold and if the MGCF requested the IM-MGW to suspend sending media on the hold request the MGCF shall request the IM-MGW to re-establish communication towards the IMS network by changing the through-connection of the IM CN subsystem side termination to "both-way through-connected" (not depicted in figure 51, but may be combined with signal 7) prior to sending of the UPDATE or re-INVITE message containing the SDP offer with "*sendrecv*" or "*recvonly*" media. + +#### Message sequence chart + +Figure 51 shows the message sequence chart for the call hold and retrieval procedures. + + + +``` + +sequenceDiagram + participant External + participant MGCF + participant IM-MGW + + Note left of MGCF: Configure IMS Resources (optional) + External->>MGCF: 1. BICC/ISUP: CPG (Hold) + MGCF->>IM-MGW: 2. H.248: MOD.req [Context ID = C1, Termination ID = T1] + IM-MGW-->>MGCF: 3. H.248: MOD.resp [Context ID = C1, Termination ID = T1] + MGCF->>External: 4. SIP: UPDATE/INVITE [SDP, a=sendonly/inactive] + External-->>MGCF: 5. SIP: 200 OK [SDP] + IM-MGW-->>External: 5.a SIP: ACK (if INVITE is used) + + Note left of MGCF: Configure IMS Resources (optional) + External->>MGCF: 6. BICC/ISUP: CPG (Retrieve) + MGCF->>IM-MGW: 7. H.248: MOD.req [Context ID = C1, Termination ID = T1] + IM-MGW-->>MGCF: 8. H.248: MOD.resp [Context ID = C1, Termination ID = T1] + MGCF->>External: 9. SIP: UPDATE/INVITE [SDP, a=sendrecv/reconly] + External-->>MGCF: 10. SIP: 200 OK [SDP] + IM-MGW-->>External: 10.a SIP: ACK (if INVITE is used) + +``` + +Sequence diagram for Session hold/resume from CS network. The diagram shows interactions between an external source, MGCF, and IM-MGW. The process involves holding a session (steps 1-5) and resuming it (steps 6-10). + +Figure 51: Session hold/resume from CS network + +### 9.2.11 Explicit Congestion Notification Support + +#### 9.2.11.1 General + +A MGCF and IM-MGW may support Multimedia Telephony using Explicit Congestion Notification (see IETF RFC 3168 [129], IETF RFC 6679 [130], and 3GPP TS 26.114 [104]), and may then act as an ECN endpoint to enable ECN with a local ECN-capable terminal within a local network that properly handles ECN-marked packets. + +##### 9.2.11.1a Incoming Call Interworking from SIP to ISUP/BICC at I-MGCF + +If the MGCF receives a SDP Offer containing ECN negotiation, see IETF RFC 6679 [130], and if all of the following statements are true: + +- the MGCF supports ECN according to 3GPP TS 26.114 [104]; +- the IM-MGW supports ECN according to 3GPP TS 26.114 [104]; +- the IM-MGW knows (via configuration) that the preceding (IMS) network supports ECN according to 3GPP TS 26.114 [104]; and +- the IM-MGW supports at least some of the initialisation methods offered within the "a=ecn-capable-rtp", + +NOTE 1: Only the "leap" initialisation method is supported over the Mn interface in this release. + +The MGCF shall: + +- act as an end point for ECN; +- select an initialisation method supported by the IM-MGW; + +- determine if application specific feedback or ECN feedback messages shall be used, taking into account whether the IM-MGW supports ECN feedback messages, and the negotiation procedures in 3GPP TS 26.114 [104]; +- determine if ECN XR summary reports can be used, taking into account whether they are supported at the IM-MGW and the negotiation procedures in 3GPP TS 26.114 [104]; +- return an SDP Answer according to 3GPP TS 26.114 [104] and the capabilities of the IM-MGW, containing the "a=ecn-capable-rtp" attribute; and + +NOTE 2: ECN XR summary reports and RTCP AVPF ECN feedback message are not supported in this release. + +- indicate to the IM-MGW that it shall apply the ECN procedures (according to 3GPP TS 26.114 [104]) and act as an ECT endpoint. + +The IM-MGW should not send RTCP XR ECN summary reports. + +##### 9.2.11.1b Outgoing Call Interworking from ISUP/BICC to SIP at O-MGCF + +When creating the SDP Offer the MGCF may initiate ECN negotiation (in accordance with 3GPP TS 26.114 [104]), indicating the capabilities of the IM-MGW (e.g. supported initialisation methods, support of ECN feedback message, and support of ECN XR summary reports). + +NOTE: ECN XR summary reports and RTCP AVPF ECN feedback message are not supported in this release. + +If the MGCF receives the SDP Answer also containing ECN attributes (indicating successful ECN negotiation) then it shall indicate to the IM-MGW that it shall apply the ECN procedures (according to 3GPP TS 26.114 [104]) and act as an ECT endpoint. + +The IM-MGW should not send RTCP XR ECN summary reports. + +##### 9.2.11.1c Detection of ECN failures by IM-MGW + +If the IM-MGW detects an ECN-related error case, for example non-ECT in the received packets when ECT(0) was expected or detecting a very high packet loss rate when ECN is used, the IM-MGW shall notify the MGCF. The MGCF should then initiate a session re-negotiation to disable ECN. + +#### 9.2.11.2 Message sequence chart + +Figure 9.2.11.2.1 shows the message sequence chart example for requesting Explicit Congestion Notification. + +![Sequence diagram showing the procedure to request ECN between MGCF and IM-MGW. The MGCF sends a Context(Cx) message to the IM-MGW with H.248:ADD.req parameters including Termination X, Transport = RTP/AVPF, ECN_enable=True, and {Notify_ECN_Error}. The IM-MGW responds with Context(Cx) and H.248:ADD.resp[Termination X]. The IM-MGW also performs internal actions: Reserve IMS Connection Point and Configure Remote Resources.](1381593e48739f603c81fa60e6b98a6c_img.jpg) + +``` + +sequenceDiagram + participant MGCF + participant IM-MGW + Note right of IM-MGW: Reserve IMS Connection Point and Configure Remote Resources + MGCF->>IM-MGW: Context(Cx) H.248:ADD.req[ Termination X, Transport = RTP/AVPF, ECN_enable=True, {Notify_ECN_Error} ] + IM-MGW-->>MGCF: Context(Cx) H.248:ADD.resp[Termination X] + +``` + +Sequence diagram showing the procedure to request ECN between MGCF and IM-MGW. The MGCF sends a Context(Cx) message to the IM-MGW with H.248:ADD.req parameters including Termination X, Transport = RTP/AVPF, ECN\_enable=True, and {Notify\_ECN\_Error}. The IM-MGW responds with Context(Cx) and H.248:ADD.resp[Termination X]. The IM-MGW also performs internal actions: Reserve IMS Connection Point and Configure Remote Resources. + +**Figure 9.2.11.2.1: Procedure to Request ECN** + +Upon receipt of a request to apply Explicit Congestion Notification the IM-MGW shall set the ECN field of the IP header in accordance with 3GPP TS 26.114 [104] when sending any data packets. + +Upon receipt of any IP headers indicating ECN Congestion Experienced (ECN-CE) the IM-MGW shall trigger rate adaptation in accordance with 3GPP TS 26.114 [104]. + +Figure 9.2.11.2.2 shows the message sequence chart example for an ECN Failure Event. + + + +``` + +sequenceDiagram + participant MGCF + participant IM-MGW + Note right of IM-MGW: Report ECN Failure + IM-MGW->>MGCF: H.248:NOTIFY.req(ECN Failure) +[Termination =>x, cause=ecn_cause] + Note left of MGCF: Context(Cx) + MGCF->>IM-MGW: H.248:NOTIFY.resp(ECN Failure) +[Termination x] + Note right of IM-MGW: Context(Cx) + +``` + +Sequence diagram showing the procedure to report an ECN failure between an MGCF and an IM-MGW. The MGCF sends an H.248:NOTIFY.req(ECN Failure) message to the IM-MGW. The IM-MGW responds with an H.248:NOTIFY.resp(ECN Failure) message. The MGCF then reports the ECN failure to the IM-MGW. + +**Figure 9.2.11.2.2: Procedure to Report ECN Failure** + +When the MGCF receives a Notification indicating that a failure has occurred, the MGCF may trigger a new SDP offer to 241salig ECN. + +### 9.2.12 Interactive Connectivity Establishment Support + +#### 9.2.12.1 General + +The MGCF and the IM-MGW may support ICE functionality as specified in IETF RFC 5245 [143] and 3GPP TS 24.229 [9] to support a UE residing behind a remote NAT. The present clause describes the requirements for MGCF and IM-MGW when the ICE procedures are supported. + +Support of full ICE functionality is optional, but if ICE is supported, the MGCF and IM-MGW shall at least support ICE lite as specified in IETF RFC 5245 [143]. + +The MGCF and IM-MGW shall only use host candidates as local ICE candidates. + +NOTE 1: MGCF and IM-MGW are not located behind a NAT (from perspective of the ICE deployment model according to Figure 1 in RFC 5245 [143]). + +When the MGCF detects no ICE parameters in the received SDP, it shall not configure the IM-MGW to apply any ICE and STUN related procedures (see IETF RFC 5389 [144]) toward the call leg from where the SDP has been received. + +Any IM-MGW supporting ICE shall advertise its support of incoming STUN continuity check procedures. An IM-MGW supporting full ICE procedures shall in addition advertise its support for originating STUN connectivity check procedures. + +If the IM-MGW does not indicate the support of STUN procedures, or if the MGCF is configured not to apply ICE toward a call leg, the MGCF shall not configure the IM-MGW to apply STUN procedures. + +#### 9.2.12.2 ICE lite + +If the MGCF is configured to use ICE lite, or supports only ICE lite, or controls an IM-MGW that only support ICE lite, the procedures in the present clause apply. + +If the MGCF receives an initial SDP offer with ICE candidate information but no "a=ice-lite" attribute, the MGCF: + +- shall request the IM-MGW for each media line where it decides to use ICE to reserve an ICE host candidate and provide its address information and a related ICE user name fragment and password; + +NOTE 1: Requesting only one host candidate per m-line prevents that the MGCF will receive "a=remote-candidates" SDP attributes in a subsequent SDP. Requesting separate ufrag and password for each media line simplifies H.248 encoding. + +- shall configure the IM-MGW to act as STUN server at the host candidate address, i.e. to answer STUN connectivity checks; +- may provide received remote ICE candidates and the received related ICE user name fragment and password to the IM-MGW; +- shall include the host candidate and related ICE user name fragment and password received from the IM-MGW in the SDP answer it sends; and +- shall include the "a=ice-lite" attribute in the SDP answer it sends. + +If the MGCF receives SDP offer with ICE candidate information and an "a=ice-lite" attribute, the MGCF shall not apply ICE and shall not include any ICE related SDP attributes in the SDP answer. + +NOTE 2: This avoids that the ICE lite peer needs to send extra SDP offers to complete ICE procedures. + +If the MGCF sends an SDP offer and ICE is to be applied, the MGCF: + +- shall request the IM-MGW to reserve a host candidate for each media line where it decides to use ICE and provide its address information, user name fragment and password; +- shall configure the IM-MGW to act as STUN server at the host candidate address, i.e. to answer STUN connectivity checks; +- shall include the host candidate provided by the IM-MGW and related ICE user name fragment and password in the SDP offer it forwards; and +- shall include the "a=ice-lite" attribute in the SDP offer. + +If the MGCF then receives an SDP answer with candidate information from the call leg where ICE is to be applied, the MGCF may provide received remote ICE candidates and the received related ICE user name fragment and password to the IM-MGW. + +After the initial SDP offer-answer exchange, the MGCF can receive a new offer from the peer that includes updated address and port information in the SDP "c=" line, "m=" line, or "a=rtpc" line SDP attributes. If the ICE user name fragment and password in the SDP offer differ from the ones received in the previous SDP (i.e. the peer restarts ICE), the MGCF shall apply the same procedures as for the initial SDP offer. + +When receiving a request for a host candidate for a media line, the IM-MGW shall allocate one host candidate for that media line and send it to the MGCF within the reply. The IP address and port shall be the same as indicated separately as Local IP Resources. The IM-MGW shall also indicate that it supports ICE lite in the reply. + +When receiving a request for an ICE user name fragment and password, the IM-MGW shall generate an ICE user name fragment and password and send it to the MGCF within the reply. The IM-MGW shall store the password and user name fragment to be able to authenticate incoming STUN binding request according to clause 7.2 of IETF RFC 5245 [143]. + +When receiving a request to act as STUN server, the IM-MGW shall be prepared to answer STUN binding request according to clause 7.2 of IETF RFC 5245 [143]. Once a STUN binding request with the "USE-CANDIDATE" flag has been received, the IM-MGW may send media towards the source of the binding request. + +#### 9.2.12.3 Full ICE + +If the MGCF supports and is configured to use full ICE, and controls an IM-MGW that supports full ICE, the procedures in the present clause apply. + +If the MGCF receives an initial SDP offer with ICE candidate information, the MGCF: + +- shall request the IM-MGW for each media line where it decides to use ICE to reserve an ICE host candidate and provide its address information and a related ICE user name fragment and password; + +NOTE 1: Requesting only one host candidate per m-line prevents that the MGCF will receive "a=remote-candidates" SDP attributes in a subsequent SDP. Requesting separate ufrag and password for each media line simplifies H.248 encoding. + +- shall configure the IM-MGW to act as STUN server at the host candidate address, i.e. to answer STUN connectivity checks; +- shall provide received remote ICE candidates and the received related ICE user name fragment and password to the IM-MGW; +- shall include the host candidate and related ICE user name fragment and password received from the IM-MGW in the SDP answer it sends; +- shall determine the role of MGCF in ICE (controlling or controlled) according to clause 5.2 of IETF RFC 5245 [143]; +- shall configure the IM-MGW to perform connectivity checks in accordance with the determined ICE role; +- shall configure the IM-MGW to report connectivity check results; and +- shall configure the IM-MGW to report a new peer reflexive candidate if discovered during the connectivity check. + +If the MGCF sends an SDP offer and ICE is to be applied, the MGCF: + +- shall request the IM-MGW to reserve a host candidate for each media line where it decides to use ICE and provide its address information, ICE user name fragment and password; +- shall configure the IM-MGW to act as STUN server at the host candidate address, i.e. to answer STUN connectivity checks; and +- shall include the host candidate provided by the IM-MGW and related ICE user name fragment and password in the SDP offer it sends. + +If the MGCF then receives an SDP answer with candidate information from the call leg where ICE is to be applied, the MGCF: + +- shall provide received remote ICE candidates and the received related ICE user name fragment and password to the IM-MGW; +- shall determine the role of MGCF in ICE (controlling or controlled) according to clause 5.2 of IETF RFC 5245 [143]; +- shall configure the IM-MGW to perform connectivity checks in accordance with the determined ICE role; +- shall configure the IM-MGW to report connectivity check results; and +- shall configure the IM-MGW to report a new peer reflexive candidate if discovered during the connectivity check. + +When the MGCF is informed by the IM-MGW about new peer reflexive candidate(s) discovered by the connectivity checks, the MGCF shall configure the IM-MGW to perform additional connectivity checks for those candidates, + +When the MGCF is informed by the IM-MGW about successful candidate pairs determined by the connectivity checks, the MGCF shall send a new SDP offer to its peer with contents according to clause 9.2.2.2 of IETF RFC 5245 [143] if it has the controlling role and the highest-priority candidate pair differs from the default candidates in previous SDP. + +After the initial SDP offer-answer exchange, the MGCF can receive a new offer from the peer that includes updated address and port information in the SDP "c=" line, "m=" line, or "a=rtpc" line SDP attributes. If the ICE user name fragment and password in the SDP offer are the same as received in the previous SDP, the MGCF shall then configure the IM-MGW to send media towards the address and port in the SDP "c=" line, "m=" line. If the STUN user name and password in the SDP offer differ from the ones received in the previous SDP (i.e. the peer restarts ICE), the MGCF shall apply the same procedures as for the initial SDP offer. + +When receiving a request for a host candidate for a media line, the IM-MGW shall allocate one host candidate for that media line and send it to the MGCF within the reply. The IP address and port shall be the same as indicated separately as Local IP Resources. + +When receiving a request for an ICE user name fragment and password, the IM-MGW shall generate an ICE user name fragment and password and send it to the MGCF within the reply. The IM-MGW shall store the password and user name fragment to be able to authenticate incoming STUN binding request according to clause 7.2 of IETF RFC 5245 [143]. + +When receiving a request to act as STUN server, the IM-MGW shall be prepared to answer STUN binding request according to clause 7.2 of IETF RFC 5245 [143]. Once a STUN binding request with the "USE-CANDIDATE" flag has been received, the IM-MGW may send media towards the source of the binding request. + +When receiving a request to perform connectivity checks and to report connectivity check results, the IM-MGW: + +- shall compute ICE candidate pairs according to clause 5.7 of IETF RFC 5245 [143]; +- shall schedule checks for the ICE candidate pairs according to clause 5.8 of IETF RFC 5245 [143]; +- shall send STUN connectivity checks for the scheduled checks according to clause 7.1 of IETF RFC 5245 [143]; +- shall inform the MGCF about successful candidate pairs determined by the connectivity checks; +- shall inform the MGCF about new peer reflexive candidate(s) discovered by the connectivity checks; and +- should send media using the highest priority candidate pair for which connectivity checks have been completed. + +#### 9.2.12.4 Procedures for Interactive Connectivity Establishment (ICE) + +##### 9.2.12.4.1 ICE lite + +Figure 9.2.12.4.1.1 shows a message sequence chart example for performing the ICE lite procedure towards the offerer. + + + +``` + +sequenceDiagram + participant External + participant MGCF + participant IM-MGW + + Note left of MGCF: INVITE/SDP offer +["a=candidate rc, +a=ice-pwd rpw, +a=ice-uf rag ruf"] + External->>MGCF: INVITE/SDP offer + MGCF->>IM-MGW: H.248:ADD.req[C=?, T=?, Laddr = ?, Lport = ?, Local Resources] + IM-MGW-->>MGCF: H.248:ADD.resp[C=C1, T=T2] + Note right of IM-MGW: Reserve IMS Connection Point + MGCF->>IM-MGW: INVITE/SDP offer [ ] + IM-MGW-->>MGCF: SDP Answer [ ] + MGCF->>IM-MGW: H.248:MOD.req[C=C1, T=T2] + IM-MGW-->>MGCF: H.248:MOD.resp[C=C1, T=T2] + Note right of IM-MGW: Configure IMS Connection Point + MGCF->>IM-MGW: H.248:ADD.req[C=C1, T=?, STUN server request, Local Resources (Laddr = ?, Lport = ?, ice-pwd=?, ice-uf rag=?; candidate host=?), Remote Resources (candidate rc, ice-pwd rpw, ice-uf rag ruf)] + IM-MGW-->>MGCF: H.248:ADD.req[C=C1, T=T1, Local Resources (Laddr = l1, Lport = p1, ice-pwd=lpw, ice-uf rag=luf; candidate=lc, ice-lite)] + Note right of IM-MGW: Reserve and Configure IMS Connection Point + MGCF->>External: SDP Answer +[a=ice-pwd lpw, +a=ice-uf rag luf, +a=candidate lc, +a=ice-lite] + +``` + +Sequence diagram showing the procedure for interactive connectivity establishment using ICE lite towards the offerer. The diagram involves two main participants: MGCF and IM-MGW. The process starts with an INVITE/SDP offer from an external source to the MGCF. The MGCF sends an H.248:ADD.req to the IM-MGW. The IM-MGW responds with H.248:ADD.resp and reserves an IMS Connection Point. The MGCF then sends an INVITE/SDP offer to the IM-MGW, which responds with an SDP Answer. The MGCF sends an H.248:MOD.req to the IM-MGW, which configures the IMS Connection Point and responds with H.248:MOD.resp. The MGCF then sends an H.248:ADD.req to the IM-MGW, which reserves and configures the IMS Connection Point and responds with H.248:ADD.req. Finally, the MGCF sends an SDP Answer to the external source. + +**Figure 9.2.12.4.1.1: Procedure for interactive connectivity establishment using ICE lite towards the offerer** + +##### 9.2.12.4.2 Full ICE + +Figure 9.2.12.4.2.1 shows a message sequence chart example for performing the full ICE procedure towards the offerer. + + + +``` + +sequenceDiagram + participant External + participant MGCF + participant IM-MGW + + Note right of IM-MGW: Reserve IMS Connection Point + External->>MGCF: INVITE/SDP offer +["a=candidate rc, +a=ice-pwd rpw, +a=ice-uf rag ruf"] + MGCF->>IM-MGW: H.248:ADD.req[C=?, T=?, Laddr=?, Lport=?, Local Resources] + IM-MGW-->>MGCF: H.248:ADD.resp[C=C1, T=T2] + MGCF->>External: INVITE/SDP offer [] + External-->>MGCF: SDP Answer [] + MGCF->>IM-MGW: H.248:MOD.req[C=C1, T=T2] + IM-MGW-->>MGCF: H.248:MOD.resp[C=C1, T=T2] + Note right of IM-MGW: Configure IMS Connection Point + MGCF->>IM-MGW: H.248:ADD.req[C=C1, T=?, STUN server request, ICE connectivity check {Notify connectivity check result, Notify new peer reflexive candidate}, Local Resources (Laddr=?, Lport=?, ice-pwd=?, ice-uf rag=?, candidate host=?), Remote Resources (candidate rc, ice-pwd rpw, ice-uf rag ruf)] + Note right of IM-MGW: Reserve and Configure IMS Connection Point + MGCF->>IM-MGW: H.248:ADD.req[C=C1, T=T1, Local Resources (Laddr=l1, Lport=p1, ice-pwd=lpw, ice-uf rag=luf; candidate=lc)] + IM-MGW-->>MGCF: + MGCF-->>External: SDP Answer +[a=ice-pwd lpw, +a=ice-uf rag luf, +a=candidate lc,] + +``` + +Sequence diagram for Figure 9.2.12.4.2.1: Procedure for interactive connectivity establishment using full ICE towards the offerer. The diagram shows interactions between an external entity, MGCF, and IM-MGW. + +**Figure 9.2.12.4.2.1: Procedure for interactive connectivity establishment using full ICE towards the offerer** + +##### 9.2.12.4.3 Connectivity check result notification (full ICE) + +Figure 9.2.12.4.3.1 shows the message sequence chart example for an ICE connectivity check result Event. + + + +``` + +sequenceDiagram + participant ContextCx1 as Context(Cx) + participant MGCF + participant IM-MGW + participant ContextCx2 as Context(Cx) + + Note right of IM-MGW: ICE Connectivity Check Result Notification + IM-MGW->>ContextCx1: H.248:NOTIFY.Req (ICE connectivity check result) [Termination =x, Candidate/Transport pair] + ContextCx2->>IM-MGW: H.248:NOTIFY.resp (ICE connectivity check result) [Termination x] + +``` + +Sequence diagram for Figure 9.2.12.4.3.1: Procedure to report ICE connectivity check result. The diagram shows interactions between Context(Cx), MGCF, and IM-MGW. + +**Figure 9.2.12.4.3.1: Procedure to report ICE connectivity check result** + +##### 9.2.12.4.4 New peer reflexive candidate notification (full ICE) + +Figure 9.2.12.4.4.1 shows the message sequence chart example for additional connectivity check when new peer reflexive candidate is discovered in full ICE. + + + +``` + +sequenceDiagram + participant MGCF + participant IM-MGW + Note right of IM-MGW: Additional connectivity check based on new peer reflexive candidate notification + IM-MGW->>MGCF: H.248:NOTIFY.Req (New peer reflexive candidate) [C=Cx, T=Tx, Candidate] + MGCF-->>IM-MGW: H.248:NOTIFY.resp (New peer reflexive candidate) [C=Cx, T=Tx] + MGCF->>IM-MGW: H.248:MODIFY.Req [C=Cx, T=Tx, Additional connectivity check] + IM-MGW-->>MGCF: H.248:MODIFY.resp [C=Cx, T=Tx] + +``` + +Sequence diagram showing the procedure to perform additional connectivity check upon the report of new peer reflexive candidate between MGCF and IM-MGW. + +Figure 9.2.12.4.4.1: Procedure to perform additional connectivity check upon the report of new peer reflexive candidate + +### 9.2.13 Codec Parameters Handling + +#### 9.2.13.1 Handling of common codec parameters + +Table 9.2.13.1.1 describes the MGCF handling of codec related parameters applicable to multiple codecs when the MGCF sends an SDP offer. + +Table 9.2.13.1.1: MGCF handling of common codec parameters when the MGCF acts as SDP offerer + +| Parameter | Handling of common codec parameter in the sent SDP offer | Handling of common codec parameter in the received SDP answer | +|-----------------|----------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ptime (NOTE) | The MGCF may add the parameter with a value according to configured preferences to the SDP offer. | If a ptime parameter is included in the received SDP answer, the MGCF shall supply the parameter to the IM-MGW for the termination towards the answerer in the remote descriptor. | +| maxptime (NOTE) | The MGCF may add the parameter with a value according to the IM-MGW capabilities to the SDP offer. | If a maxptime parameter is included in the received SDP answer, the MGCF shall supply the parameter to the IM-MGW for the termination towards the answerer in the remote descriptor. | + +NOTE 2: This SDP attribute is defined in IETF RFC 4566 [56]. It applies to all codecs offered in an SDP media line. + +When receiving an SDP offer, the MGCF shall handle the codec related parameters applicable to multiple codecs as described in table 9.2.13.1.2. + +**Table 9.2.13.1.2: MGCF handling of common codec parameters when the MGCF acts as SDP answerer** + +| Parameter | Handling of common codec parameter in the received SDP offer | Handling of common codec parameter in the sent SDP answer | +|-------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| +| ptime (NOTE) | If a ptime parameter is included in the received SDP offer, the MGCF shall supply the parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | The MGCF may add the parameter with a value according to configured preferences to the SDP answer. | +| maxptime (NOTE) | If a maxptime parameter is included in the received SDP offer, the MGCF shall supply the parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | The MGCF may add the parameter with a value according to the IM-MGW capabilities to the SDP answer. | +| NOTE: This SDP attribute is defined in IETF RFC 4566 [56]. It applies to all codecs offered in an SDP media line. | | | + +IM-MGW handling of codec related parameters applicable to multiple codecs shall follow table 5.13.1.2 in 3GPP TS 23.334 [145]. + +#### 9.2.13.2 Handling of EVS speech codec parameters when interworking with a different codec + +The Enhanced Voice Services (EVS) speech codec is defined in 3GPP TS 26.441 [146]. Its RTP payload type is defined in 3GPP TS 26.445 [147], and procedures for its usage as IMS Multimedia Telephony speech codec are defined in 3GPP TS 26.114 [104]. + +The MGCF and the IM-MGW may support transcoding to and from the EVS speech codec. If they do so, the procedures in the present clause apply. + +Table 9.2.13.2.1 describes the MGCF handling of EVS codec parameters when the MGCF sends an SDP offer for an EVS payload type, and that EVS payload type is selected in the answer. In addition, rules for the parameter handling in 3GPP TS 26.445 [147] shall apply. + +**Table 9.2.13.2.1: MGCF handling of EVS related SDP parameters when the MGCF adds the EVS payload type to the SDP offer it sends out** + +| Parameter | Handling for EVS payload type added to an SDP offer | Handling if offered EVS payload type is accepted in the SDP answer | +|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| evs-mode-switch (NOTE 1) | If the MGCF expects that interworking between AMR-WB and EVS is required, it shall include the evs-mode-switch with value 1. Otherwise the MGCF shall not include the evs-mode-switch. | If an evs-mode-switch parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW for the termination towards the answerer in the remote descriptor. | +| hf-only (NOTE 1) | If the MGCF is configured to negotiate using only the header-full EVS RTP payload format, the MGCF shall include the hf-only parameter with a value 1. | If an hf-only parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| dtx (NOTE 1) | If the usage of DTX is not desired in the sending and receiving direction (e.g. due to DTX capabilities of expected codecs to transcode with), the MGCF shall include the dtx parameter with a value 0. | If a dtx parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| dtx-recv (NOTE 1) | If receiving DTX is not desired and the dtx parameter is not included, the MGCF shall include the dtx-recv parameter with a value 0.
If both the dtx and dtx-recv parameters are included, those parameters shall have the same value; however, inclusion of the dtx-recv parameter is not required if the dtx parameter is included. | If a dtx-recv parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| br (NOTE 1) | If the MGCF desires the same bit rate range for the send and receive direction in EVS primary mode, and wants to restrict the bit rate range to match IM-MGW capabilities and possible configured policies, it shall supply the br parameter in the SDP offer it sends. Otherwise the MGCF shall not include this parameter in the SDP offer.
If the MGCF also supplies the bw, bw-send or bw-recv parameter, the value of the br parameter shall be compatible with the values of those parameters. | If a br parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| br-send (NOTE 1) | If the MGCF desires a different bit rate (range) for the send and receive direction in EVS primary mode, and wants to restrict the bit rate range for the send direction to match IM-MGW capabilities and possible configured policies, it shall supply the br-send parameter in the SDP offer it sends. Otherwise the MGCF shall not include this parameter in the SDP offer.
If the MGCF also supplies the bw or bw-send parameter, the value of the br-send parameter shall be compatible with the values of those parameters. | If a br-send parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| br-recv (NOTE 1) | If the MGCF desires a different bit rate (range) for the send and receive direction in EVS primary mode, and wants to restrict the bit rate range for the receive direction to match IM-MGW capabilities and possible configured policies, it shall supply the br-recv parameter in the SDP offer it sends. Otherwise the MGCF shall not include this parameter in the SDP offer.
If the MGCF also supplies the bw or bw-recv parameter, the value of the br-recv parameter shall be compatible with the values of those parameters. | If a br-recv parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | + +| | | | +|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| bw (NOTE 1) | If the MGCF desires the same sampling bandwidth(s) for the send and receive direction in EVS primary mode, and wants to restrict the sampling bandwidths to match IM-MGW capabilities, sampling bandwidths of expected codecs EVS will be transcoded to, and possible configured policies, it shall supply the bw parameter in the SDP offer it sends. Otherwise the MGCF shall not include this parameter in the SDP offer. | If a bw parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| bw-send (NOTE 1) | If the MGCF desires different sampling bandwidths for the send and receive direction in EVS primary mode, and wants to restrict the sampling bandwidths in the send direction to match IM-MGW capabilities, sampling bandwidths of expected codecs EVS will be transcoded to and possible configured policies, it shall supply the bw-send parameter in the SDP offer it sends. Otherwise the MGCF shall not include this parameter in the SDP offer. | If a bw-send parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| bw-recv (NOTE 1) | If the MGCF desires different sampling bandwidths for the send and receive direction in EVS primary mode, and wants to restrict the sampling bandwidths in the receive direction to match IM-MGW capabilities, sampling bandwidths of expected codecs EVS will be transcoded to, and possible configured policies, it shall supply the bw-recv parameter in the SDP offer it sends. Otherwise the MGCF shall not include this parameter in the SDP offer. | If a bw-recv parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| cmr (NOTE 1) | If the MGCF desires to disable codec mode requests within the RTP payload of the EVS primary mode (due to the IM-MGW capabilities or policies), it shall include the cmr parameter with value -1 in the SDP offer it sends. | If a cmr parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| ch-aw-recv (NOTE 1) | The MGCF shall include the ch-aw-recv parameter in the SDP offer if it desires to control the channel-aware-mode of EVS in the receive direction, e.g. to disable it with value -1. The MGCF shall consider the capabilities of the IM-MGW when it chooses an appropriate value. | If a ch-aw-recv parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| number of channels (NOTE 2) | The MGCF shall only include the "number of channels" parameter in the SDP offer if it desires to send or receive multiple channels. If the desired number of channels in the send and receive direction differs, the MGCF shall include the higher value. The MGCF should consider the number of channels of expected codecs EVS will be transcoded to. | If a "number of channels" parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| ch-send (NOTE 1) | The MGCF shall only include the ch-send parameter in the SDP offer if it desires to send multiple channels, with different numbers of channels in the send and receive direction. The MGCF should consider the number of channels of expected codecs EVS will be interworked with. | If a ch-send parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| ch-recv (NOTE 1) | The MGCF shall only include the ch-recv parameter in the SDP offer if it desires to receive multiple channels, with different numbers of channels in the send and receive direction. The MGCF should consider the number of channels of expected codecs EVS will be interworked with.. | If a ch-recv parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| mode-set (NOTE 4) | The MGCF shall only include the mode-set parameter in the SDP offer if it desires to restrict the mode-set of AMR-WB IO mode. The MGCF should only restrict the mode-set if the expected codec EVS will be interworked with is AMR-WB and has a restricted mode set. | If a mode-set parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| mode-change-period (NOTE 3) | The MGCF shall only include the mode-change-period parameter with value 2 in the SDP offer if it desires to restrict the mode change period of received packets in AMR-WB IO mode. The MGCF should only restrict the mode-change-period if the expected codec EVS will be interworked with is AMR-WB and has such a restriction. | If a mode-change-period parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| mode-change-capability (NOTE 3) | The MGCF shall include the mode-change-capability parameter with value 2 or omit it in the SDP offer. | If a mode-change-capability parameter is contained in the SDP answer, the MGCF may forward this parameter to the IM-MGW in the remote descriptor. | +| mode-change-neighbor (NOTE 3) | The MGCF shall only include the mode-change-neighbor parameter in the SDP offer if it desires to restrict the mode change within received packets of AMR-WB IO mode to neighboring modes. The MGCF should consider the mode-change-neighbor parameter of the expected codec EVS will be interworked with if this is AMR-WB. | If a mode-change-neighbor parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| max-red (NOTE 5) | The MGCF shall only include the max-red parameter in the SDP offer if it desires to restrict the maximum redundancy of received packets. MGCF shall consider the capabilities of the IM-MGW, and should consider a max-red parameter of the expected codec EVS will be interworked with if this is AMR-WB. | If a max-red parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| 3gpp_mtsi_app_adapt (NOTE 4) | If the IM-MGW supports RTCP APP based adaptation messages defined in TS 26.114 [104], and the MGCF has a policy to negotiate the usage of those messages, the MGCF shall include the 3gpp_mtsi_app_adapt SDP attribute indicating the supported APP messages in the SDP offer. | If a 3gpp_mtsi_app_adapt attribute is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| NOTE 1: This MIME parameter of the EVS RTP payload type is defined in TS 26.445 [147]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [56]. | | | +| NOTE 2: This number of channels are encoded as "encoding parameters" of the SDP "a=rtpmap" attribute defined in IETF RFC 4566 [56]. | | | +| NOTE 3: This MIME parameter of the EVS RTP payload type relates to AMR-WB IO mode and is defined in IETF RFC 4867 [23]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [56]. | | | +| NOTE 4: This SDP attribute is defined in TS 26.114 [104]. It applies to all codecs offered in an SDP media line. However, some values are specific to EVS. | | | +| NOTE 5: This MIME parameter of the EVS RTP payload type is defined in IETF RFC 4867 [23]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [56]. | | | + +When receiving an SDP offer that contains an EVS codec payload type, the MGCF shall handle the EVS codec parameters as described in table 9.2.13.2.2. In addition, rules for the parameter handling in 3GPP TS 26.445 [147] shall apply. + +**Table 9.2.13.2.2: MGCF handling of EVS related SDP parameters when the MGCF receives the EVS payload type in an SDP offer** + +| Parameter | Handling of EVS payload type parameter received in the SDP offer | EVS payload type supplied in the SDP answer | +|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| evs-mode-switch (NOTE 1) | If an evs-mode-switch parameter is contained in the SDP offer and the MGCF select the EVS payload type, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | If an evs-mode-switch parameter is contained in the SDP offer, the MGCF shall include the evs-mode-switch parameter with unmodified value in the SDP answer. Otherwise, if the MGCF decides to interwork between AMR-WB and EVS, it shall include the evs-mode-switch with value 1. Otherwise the MGCF shall not include the evs-mode-switch. If the MGCF supplies the evs-mode-switch in the SDP answer, it shall also supply it to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. | +| hf-only (NOTE 1) | If an hf-only parameter is contained in the SDP offer and the MGCF select the EVS payload type, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | If an hf-only parameter is contained in the SDP offer, the MGCF shall include the hf-only parameter with unmodified value in the SDP answer. Otherwise, if the MGCF is configured to negotiate using only the header-full EVS RTP payload format, the MGCF shall include the hf-only parameter with a value 1. If the MGCF supplies the hf-only parameter in the SDP answer, it shall also supply it to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. | +| dtx (NOTE 1) | If a dtx parameter is contained in the SDP offer and the MGCF select the EVS payload type, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | If a dtx parameter is contained in the SDP offer, the MGCF shall include the dtx parameter with unmodified value in the SDP answer. If the dtx parameter is not contained in the SDP offer and if a dtx-recv parameter is contained in the SDP offer, the MGCF may include the dtx parameter in the SDP answer , and the value of the dtx parameter shall then be identical to that of the dtx-recv parameter in the SDP offer (e.g, if that value matches DTX capabilities of expected codecs to transcode with). If the dtx parameter is not contained in the SDP offer and if the dtx-recv parameter is not contained in the SDP offer, and if the usage of DTX is not desired (e.g. due to DTX capabilities of expected codecs to transcode with), the MGCF shall include in the SDP answer the dtx parameter with a value 0. If the MGCF supplies the dtx parameter in the SDP answer, it shall also supply it to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. | + +| | | | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dtx-recv (NOTE 1) |
If a dtx-recv parameter is contained in the SDP offer and the MGCF select the EVS payload type, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor.
|If no dtx parameter is included in the SDP answer and if the reception of DTX is not desired, the MGCF shall include in the SDP answer the dtx-recv parameter with a value 0.
If both the dtx and dtx-recv parameters are included, those parameters shall have the same value; however, inclusion of the dtx-recv parameter is not required if the dtx parameter is included.
If the MGCF supplies the dtx-recv parameter in the SDP answer, it should also supply it to the IM-MGW in the local descriptor for the termination towards the offerer with the same value.
| +| br (NOTE 1) |If a br parameter is contained in the SDP offer, the MGCF shall check if the IM-MGW supports the indicated bit rates, or a subset of them, in EVS primary mode in the send and receive direction. If the indicated bit rates, and even each subset of them, are not supported, the MGCF shall not select the EVS payload type. If the MGCF selects the EVS payload type, it shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor.
|If a br parameter is contained in the SDP offer, the MGCF shall select a bit rate value, which is either the received br value or a subset of it, based on IM-MGW capabilities and possible configured policies, and shall include the br parameter with the selected value that is also supplied towards the IM-MGW in the SDP answer. Otherwise, if the MGCF desires the same bit rate range for the send and receive direction in EVS primary mode, and wants to restrict the bit rate range to match IM-MGW capabilities and possible configured policies, the MGCF shall supply the br parameter in the SDP answer it sends. Otherwise the MGCF shall not include this parameter in the SDP answer.
If the MGCF also supplies the bw, bw-send or bw-recv parameter, the value of the br parameter shall be compatible with the values of those parameters.
If the MGCF supplies the br parameter in the SDP answer, it shall also supply to the IM-MGW the br parameter in the local descriptor for the termination towards the offerer with the same value.
| + +| | | | +|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| br-send (NOTE 1) |If a br-send parameter is contained in the SDP offer, the MGCF shall check if the IM-MGW supports the indicated bit rates, or a subset of them, in EVS primary mode in the receive direction. If the indicated bit rates, and even each subset of them, are not supported, the MGCF shall not select the EVS payload type. If the MGCF selects the EVS payload type, it shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor.
|If a br-recv parameter is contained in the SDP offer, the MGCF shall select a bit rate value, which is either the received br-recv value or a subset of it, based on IM-MGW capabilities and possible configured policies, and the MGCF shall include the br-send parameter with the selected value that is also supplied towards the IM-MGW in the SDP answer.
Otherwise, if the MGCF desires a different bit rate (range) for the send and receive direction in EVS primary mode, and wants to restrict the bit rate range for the send direction to match IM-MGW capabilities and possible configured policies, it shall supply the br-send parameter in the SDP answer it sends.
Otherwise the MGCF shall not include the br-send parameter in the SDP answer.
If the MGCF also supplies the bw or bw-send parameter, the value of the br-send parameter shall be compatible with the values of those parameters.
If the MGCF supplies the br-send parameter in the SDP answer, it shall also supply to the IM-MGW the br-send parameter in the local descriptor for the termination towards the offerer with the same value.
| +| br-recv (NOTE 1) |If a br-recv parameter is contained in the SDP offer, the MGCF shall check if the IM-MGW supports the indicated bit rates, or a subset of them, in EVS primary mode in the send direction. If the indicated bit rates, and even each subset of them, are not supported, the MGCF shall not select the EVS payload type. If the MGCF selects the EVS payload type, it shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor.
|If a br-send parameter is contained in the SDP offer, the MGCF shall select a bit rate value, which is either the received br-send value or a subset of it, based on IM-MGW capabilities and possible configured policies, and the MGCF shall include the br-recv parameter with the selected value that is also supplied towards the IM-MGW in the SDP answer.
Otherwise, if the MGCF desires a different bit rate (range) for the send and receive direction in EVS primary mode, and wants to restrict the bit rate range for the receive direction to match IM-MGW capabilities and possible configured policies, it shall supply the br-recv parameter in the SDP answer it sends.
Otherwise the MGCF shall not include the br-recv parameter in the answer.
If the MGCF also supplies the bw or bw-recv parameter, the value of the br-recv parameter shall be compatible with the values of those parameters.
If the MGCF supplies the br-recv parameter in the SDP answer, it shall also supply to the IM-MGW the br-recv parameter in the local descriptor for the termination towards the offerer with the same value.
| + +| | | | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bw (NOTE 1) |If a bw parameter is contained in the SDP offer, the MGCF shall check if the IM-MGW supports the indicated sampling bandwidth(s), or a subset of them, in EVS primary mode in the send and receive direction. If the indicated sampling bandwidth(s), and even each subset of them, are not supported, the MGCF shall not select the EVS payload type. If the MGCF selects the EVS payload type, it shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor.
|If a bw parameter is contained in the SDP offer, the MGCF shall select a sampling bandwidth value, which is either the received bw value or a subset of it, based on IM-MGW capabilities, possible configured policies, and the bw range of other codecs to transcode with, and the MGCF shall include the bw parameter with the selected value that is also supplied towards the IM-MGW in the SDP answer. Otherwise, if the MGCF desires the same sampling bandwidth(s) for the send and receive direction in EVS primary mode, and wants to restrict the sampling bandwidth(s) to match IM-MGW capabilities, possible configured policies, and the bw range of other codecs to transcode with, the MGCF shall supply the bw parameter in the SDP answer it sends. Otherwise the MGCF shall not include this parameter in the answer. If the MGCF also supplies the br, br-send or br-recv parameter, the value of the bw parameter shall be compatible with the values of those parameters. If the MGCF supplies the bw parameter in the SDP answer, it shall also supply to the IM-MGW the bw parameter in the local descriptor for the termination towards the offerer with the same value.
| +| bw-send (NOTE 1) |If a bw-send parameter is contained in the SDP offer, the MGCF shall check if the IM-MGW supports the indicated sampling bandwidths, or a subset of them, in EVS primary mode in the receive direction. If the indicated sampling bandwidths, and even each subset of them, are not supported, the MGCF shall not select the EVS payload type. If the MGCF selects the EVS payload type, it shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor.
|If a bw-recv parameter is contained in the SDP offer, the MGCF shall select a sampling bandwidths value, which is either the received bw-recv value or a subset of it, based on IM-MGW capabilities, possible configured policies, and the bw range of other codecs to transcode with, and the MGCF shall include the bw-send parameter with the selected value in the SDP answer. Otherwise, if the MGCF desires a different sampling bandwidths for the send and receive direction in EVS primary mode, and wants to restrict the sampling bandwidths for the send direction to match IM-MGW capabilities, possible configured policies, and the bw range of other codecs to transcode with, the MGCF shall supply the bw-send parameter in the SDP answer it sends. Otherwise the MGCF shall not include the br-send parameter in the SDP answer. If the MGCF also supplies the bw or bw-send parameter, the value of the br-send parameter shall be compatible with the values of those parameters. If the MGCF supplies the bw-send parameter in the SDP answer, it shall also supply to the IM-MGW the bw-send parameter in the local descriptor for the termination towards the offerer with the same value.
| + +| | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bw-recv (NOTE 1) |If a br-recv parameter is contained in the SDP offer, the MGCF shall check if the IM-MGW supports the indicated sampling bandwidths, or a subset of them, in EVS primary mode in the send direction. If the indicated sampling bandwidths, and even each subset of them, are not supported, the MGCF shall not select the EVS payload type. If the MGCF selects the EVS payload type, it shall forward the bw-recv parameter to the IM-MGW for the termination towards the offerer in the remote descriptor.
|If a bw-send parameter is contained in the SDP offer, the MGCF shall select a sampling bandwidths value, which is either the received bw-send value or a subset of it, based on IM-MGW capabilities, possible configured policies, and the bw range of other codecs to transcode with, and the MGCF shall include the bw-recv parameter with the selected value in the SDP answer. Otherwise, if the MGCF desires a different sampling bandwidths for the send and receive direction in EVS primary mode, and wants to restrict the sampling bandwidths for the receive direction to match IM-MGW capabilities, possible configured policies, and the bw range of other codecs to transcode with, the MGCF shall supply the bw-recv parameter in the SDP answer it sends. Otherwise the MGCF shall not include the bw-recv parameter in the SDP answer. If the MGCF also supplies the br or br-recv parameter, the value of the bw-recv parameter shall be compatible with the values of those parameters. If the MGCF supplies the bw-send parameter in the SDP answer, it shall also supply it to the IM-MGW in the local descriptor for the termination towards the offerer with the same value.
| +| cmr (NOTE 1) |If a cmr parameter is contained in the SDP offer and the MGCF select the EVS payload type, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor.
|If a cmr parameter is contained in the SDP offer, the MGCF shall include the cmr parameter with unmodified value in the SDP answer. Otherwise, if the IM-MGW desires to disable codec mode requests within the RTP payload of the EVS primary mode (due to the IM-MGW capabilities and possible configured policies), it shall include the cmr parameter with value -1 in the SDP answer it sends. If the MGCF supplies the cmr parameter in the SDP answer, it shall also supply it to the IM-MGW in the local descriptor for the termination towards the offerer with the same value.
| +| ch-aw-recv (NOTE 1) |If a ch-aw-recv parameter is contained in the SDP offer the MGCF shall check if the IM-MGW supports the indicated mode in the send direction. If the indicated mode is not supported, the MGCF shall not select the EVS payload type. If the MGCF selects the EVS payload type, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor.
|If the MGCF it desires to control the channel-aware mode of EVS in the receive direction, e.g. to disable it with value -1, it shall include the ch-aw-recv parameter in the SDP offer and shall also supply the ch-aw-recv parameter to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. The MGCF shall consider the capabilities of the IM-MGW when it chooses an appropriate value.
| + +| | | | +|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| number of channels (NOTE 2) | If a "number of channels" parameter is contained in the SDP offer the MGCF shall check if the IM-MGW supports the indicated number of channels. If the indicated number of channels is not supported, the MGCF shall not select the EVS payload type. If the MGCF selects the EVS payload type, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | If a "number of channels" parameter is contained in the SDP offer, the MGCF shall include the "number of channels" parameter with unmodified value in the SDP answer and shall also supply it to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. | +| ch-send (NOTE 1) | If a ch-send parameter is contained in the SDP offer the MGCF shall check if the IM-MGW supports the indicated number of channels in the receive direction. If the indicated number of channels is not supported, the MGCF shall not select the EVS payload type. If the MGCF selects the EVS payload type, the MGCF shall forward the ch-send parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | If a ch-recv parameter is contained in the SDP offer, the MGCF shall include the ch-send parameter with unmodified value in the SDP answer and shall also supply the ch-send parameter to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. | +| ch-recv (NOTE 1) | If a ch-recv parameter is contained in the SDP offer the MGCF shall check if the IM-MGW supports the indicated number of channels in the send direction. If the indicated number of channels is not supported, the MGCF shall not select the EVS payload type. If the MGCF selects the EVS payload type for transcoding, the MGCF shall forward the ch-recv parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | If a ch-send parameter is contained in the SDP offer, the MGCF shall include the ch-recv parameter with unmodified value in the SDP answer and shall also supply the ch-recv parameter to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. | +| mode-set (NOTE 3) | If a mode-set parameter is contained in the SDP offer and the MGCF select the EVS payload type, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | If a mode-set parameter is contained in the SDP offer, the MGCF shall include the mode-set parameter with unmodified value in the SDP answer.Otherwise, if AMR-WB is used to interwork with, the MGCF should include the mode-set parameter with a value indicating the mode that was negotiated for AMR-WB (or omit it if no restrictions applied before).
If the MGCF supplies the mode-set parameter in the SDP answer, it shall also supply it to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. | +| mode-change-period (NOTE 3) | If a mode-change-period parameter is contained in the SDP offer and the MGCF select the EVS payload type, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | If AMR-WB is used to interwork with, the MGCF should include the mode-change-period parameter with a value indicating the mode that was negotiated for AMR-WB (or omit it if no restrictions applied before) in the SDP answer.
If the MGCF supplies the mode-change-period parameter in the SDP answer, it shall also supply it to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. | +| mode-change-capability (NOTE 3) | If a mode-change-capability (Note 4) parameter is contained in the SDP offer and the MGCF select the EVS payload type, the MGCF may forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | If the MGCF selects the EVS payload type, the MGCF shall include the mode-change-capability parameter with value 2 or omit it in the SDP answer.
If the MGCF supplies the mode-change-capability parameter in the SDP answer, it may also supply it to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. | + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| mode-change-neighbor (NOTE 3) | If a mode-change-neighbor parameter is contained in the SDP offer and the MGCF select the EVS payload type, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | If AMR-WB is used to interwork with, the MGCF should include the mode-change-neighbor parameter with a value indicating the mode that was negotiated for AMR-WB (or omit it if no restrictions applied before) in the SDP answer.
If the MGCF supplies the mode-change-neighbor parameter in the SDP answer, it shall also supply it to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. | +| max-red (NOTE 5) | If a max-red parameter is contained in the SDP offer and the MGCF select the EVS payload type, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | The MGCF shall only include the max-red parameter in the SDP answer if it desires to restrict the maximum redundancy of received packets. When selecting the value of the max-red parameter, the MGCF shall consider the capabilities of the IM-MGW.
If the MGCF supplies the max-red parameter in the SDP answer, it shall also supply it to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. | +| 3gpp_mtsi_app_adapt (NOTE 4) | If a 3gpp_mtsi_app_adapt SDP attribute is contained in the SDP answer, and the MGCF select the EVS payload type, the MGCF shall forward this parameter to the IM-MGW the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | If the IM-MGW supports RTCP APP based adaptation messages defined in TS 26.114 [104], and the MGCF has a policy to negotiate the usage of those messages, the MGCF shall include the 3gpp_mtsi_app_adapt SDP attribute indicating the allowed APP messages in the SDP answer. | +| NOTE 1: This MIME parameter of the EVS RTP payload type is defined in TS 26.445 [147]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [56].
NOTE 2: This number of channels are encoded as "encoding parameters" of the SDP "a=rtpmap" attribute defined in IETF RFC 4566 [56].
NOTE 3: This MIME parameter of the EVS RTP payload type relates to AMR-WB IO mode and is defined in IETF RFC 4867 [23]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [56].
NOTE 4: This SDP attribute is defined in TS 26.114 [104]. It applies to all codecs offered in an SDP media line. However, some values are specific to EVS.
NOTE 5: This MIME parameter of the EVS RTP payload type is defined in IETF RFC 4867 [23]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [56]. | | | + +IM-MGW handling of EVS codec parameters shall follow table 5.13.2.3 in 3GPP TS 23.334 [145]. The IM-MGW should support transcoding of EVS with bandwidths (sampling rates) which are supported by codec the IM-MGW is capable to transcode EVS to/from (e.g. NB for AMR, and WB for AMR-WB). + +#### 9.2.13.3 Handling of EVS speech codec parameters when the EVS codec is used end-to-end + +The procedures in the present clause apply when the EVS speech codec is used in both IMS and the CS domain. + +The four allowed EVS codec configurations for the CS domain are specified in 3GPP TS 26.103 [57]. + +Table 9.2.13.3.1 describes the MGCF handling of EVS codec parameters when the MGCF sends an SDP offer for an EVS payload type, which is supported in the CS network, and that EVS payload type is selected in the SDP answer. In addition, rules for the parameter handling in 3GPP TS 26.445 [147] shall apply. + +**Table 9.2.13.3.1: MGCF handling of EVS related SDP parameters when the MGCF acts as SDP offerer** + +| Parameter | Handling of EVS codec parameter in the sent SDP offer | Handling of EVS codec parameter in the received SDP answer | +|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| evs-mode-switch (NOTE 1) | The MGCF shall not include the evs-mode-switch parameter in the SDP offer. | If an evs-mode-switch parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW for the termination towards the answerer in the remote descriptor. | +| hf-only (NOTE 1) | If the MGCF is configured to negotiate using only the header-full EVS RTP payload format, the MGCF shall include the hf-only parameter with a value of 1 in the SDP offer.
Using only the header-full EVS RTP payload format is recommended. | If an hf-only parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| dtx (NOTE 1) | The MGCF shall include the dtx parameter in the SDP offer and shall set it to 1 i.e. DTX enabled. | If a dtx parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| dtx-recv (NOTE 1) | The MGCF shall include the dtx-recv parameter in the SDP offer and shall set it to 1 i.e. DTX enabled. | If a dtx-recv parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| br (NOTE 1) | The MGCF shall include the br parameter in the SDP offer and shall set it to a range corresponding to the CS configuration received in the Single Codec IE (see subclause B.2.5.5). | If a br parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| br-send (NOTE 1) | The MGCF shall not include the br-send parameter in the SDP Offer. | If a br-send parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| br-recv (NOTE 1) | The MGCF shall not include the br-recv parameter in the SDP Offer. | If a br-recv parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| bw (NOTE 1) | The MGCF shall include the bw parameter in the SDP offer and shall set it to a range corresponding to the CS configuration received in the Single Codec IE (see subclause B.2.5.5). | If a bw parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| bw-send (NOTE 1) | The MGCF shall not include the bw-send parameter in the SDP Offer. | If a bw-send parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| bw-recv (NOTE 1) | The MGCF shall not include the bw-recv parameter in the SDP Offer. | If a bw-recv parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| cmr (NOTE 1) | If the MGCF desires to disable codec mode requests on Mb within the RTP payload of the EVS primary mode (due to the IM-MGW capabilities or policies) and desires to use RTCP-APP instead for codec mode request, then it shall include the cmr parameter with a value of -1 in the SDP offer.
Otherwise, the MGCF shall include the cmr parameter with a value of 1 in the SDP offer in order to request EVS-CMR in every RTP packet.
The use of code mode requests on Mb within the RTP payload of the EVS primary mode is recommended. | If a cmr parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| ch-aw-recv (NOTE 1) | The MGCF shall include the ch-aw-recv parameter in the SDP offer and shall set it to an allowed value for the CS configuration received in the Single Codec IE (see subclause B.2.5.5). | If a ch-aw-recv parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| number of channels (NOTE 2) | The MGCF shall include the number of channels parameter with a value of 1 in the SDP offer. | If a "number of channels" parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| ch-send (NOTE 1) | The MGCF shall not include the ch-send parameter in the SDP offer. | If a ch-send parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| ch-recv (NOTE 1) | The MGCF shall not include the ch-recv parameter in the SDP offer. | If a ch-recv parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| mode-set (NOTE 4) | The MGCF shall include the mode-set parameter in the SDP offer and shall set it as per the received Single Codec IE (see subclause B.2.5.5). | If a mode-set parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| mode-change-period (NOTE 3) | The MGCF shall include the mode-change-period parameter in the SDP offer and shall set it to 2. | If a mode-change-period parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| mode-change-capability (NOTE 3) | The MGCF shall either include the mode-change-capability parameter with a value of 2 or omit it in the SDP offer. | If a mode-change-capability parameter is contained in the SDP answer, the MGCF may forward this parameter to the IM-MGW in the remote descriptor. | +| mode-change-neighbor (NOTE 3) | The MGCF shall include the mode-change-neighbor parameter in the SDP offer and shall set it to 1. | If a mode-change-neighbor parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| max-red (NOTE 5) | The MGCF shall not include the max-red parameter in the SDP offer. | If a max-red parameter is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. (NOTE 6) | +| 3gpp_mtsi_app_adapt (NOTE 4) | If the IM-MGW supports RTCP APP based adaptation messages defined in TS 26.114 [104], and the MGCF has a policy to negotiate the usage of those messages, the MGCF shall include the 3gpp_mtsi_app_adapt SDP attribute indicating the supported APP messages in the SDP offer. | If a 3gpp_mtsi_app_adapt attribute is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | +| NOTE 1: This MIME parameter of the EVS RTP payload type is defined in TS 26.445 [147]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [56]. | | | +| NOTE 2: This number of channels is encoded as "encoding parameters" of the SDP "a=rtpmap" attribute defined in IETF RFC 4566 [56]. | | | +| NOTE 3: This MIME parameter of the EVS RTP payload type relates to the EVS AMR-WB IO major operation mode and is defined in IETF RFC 4867 [23]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [56]. | | | +| NOTE 4: This SDP attribute is defined in TS 26.114 [104]. It applies to all codecs offered in an SDP media line. However, some values are specific to EVS. | | | +| NOTE 5: This MIME parameter of the EVS RTP payload type is defined in IETF RFC 4867 [23]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [56]. | | | +| NOTE 6: RTP redundancy is only applicable on the Mb interface. In such a case, the IM-MGW performs repacking. Transcoding is not required. | | | + +When receiving an SDP offer that contains an EVS codec payload type, the MGCF shall handle the EVS codec parameters as described in table 9.2.13.3.2. In addition, rules for the parameter handling in 3GPP TS 26.445 [147] shall apply. + +**Table 9.2.13.3.2: MGCF handling of EVS codec SDP parameters when the MGCF acts as SDP answerer** + +| Parameter | Handling of EVS codec parameter in the received SDP offer | Handling of EVS codec parameter in the sent SDP answer | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| evs-mode-switch (NOTE 1) | If an evs-mode-switch parameter is contained in the SDP offer and the MGCF select the EVS payload type, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. (NOTE 6) | If an evs-mode-switch parameter is contained in the SDP offer, the MGCF shall include the evs-mode-switch parameter with unmodified value in the SDP answer. Otherwise the MGCF shall not include the evs-mode-switch parameter. | +| hf-only (NOTE 1) | If an hf-only parameter is contained in the SDP offer, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | If an hf-only parameter is contained in the SDP offer, the MGCF shall include the hf-only parameter with unmodified value in the SDP answer. Otherwise, if the hf-only parameter is not contained in the SDP offer and if the MGCF is configured to negotiate using only the header-full EVS RTP payload format, then the MGCF shall include the hf-only parameter with a value of 1. If the MGCF supplies the hf-only parameter in the SDP answer, it shall also supply it to the IM-MGW in the local descriptor for the termination towards the offerer. | +| dtx (NOTE 1) | If a dtx parameter is contained in the SDP offer and the MGCF select the EVS payload type, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | If a dtx parameter is not contained in the SDP offer and a dtx-recv parameter is not contained in the SDP offer, the MGCF shall include the dtx parameter with a value of 1 in the SDP answer. If a dtx parameter is not contained in the SDP offer and a dtx-recv parameter is contained in the SDP offer with a value of 1, the MGCF shall include the dtx parameter in the SDP answer with a value identical to that of the dtx-recv parameter in the SDP offer. If a dtx parameter is contained in the SDP offer, the MGCF shall include the dtx parameter with unmodified value in the SDP answer. The MGCF shall also supply the dtx parameter to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. | +| dtx-recv (NOTE 1) | If a dtx-recv parameter is contained in the SDP offer and the MGCF select the EVS payload type, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | If no dtx parameter is included in the SDP answer, the MGCF may include the dtx-recv parameter with a value of 1 in the SDP answer. The MGCF should also supply the dtx-recv parameter to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. | + +| | | | +|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| br (NOTE 1) |
If a br parameter is contained in the SDP offer, the MGCF shall check if the IM-MGW supports the indicated bit rates, or a subset of them, in EVS primary mode in the send and receive direction. If the indicated bit rates, and even each subset of them, are not supported, the MGCF shall not select the EVS payload type. If the MGCF selects the EVS payload type, it shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor.
|If a br parameter is contained in the SDP offer, the MGCF shall select a bit rate value, which is either the received br value or a subset of it, based on IM-MGW capabilities, possible configured policies and the CS configuration received Single Codec IE (see subclause B.2.5.5), and shall include the br parameter with the selected value that is also supplied towards the IM-MGW in the SDP answer. Otherwise, the MGCF shall include the br parameter in the SDP answer and shall set it to a range corresponding to the CS configuration received in the Single Codec IE (see subclause B.2.5.5). If the MGCF also supplies the bw, bw-send or bw-recv parameter, the value of the br parameter shall be compatible with the values of those parameters. The MGCF shall also supply the br parameter to the IM-MGW in the local descriptor for the termination towards the offerer with the same value.
| +| br-send (NOTE 1) |If a br-send parameter is contained in the SDP offer, the MGCF shall check if the IM-MGW supports the indicated bit rates, or a subset of them, in EVS primary mode in the receive direction. If the indicated bit rates, and even each subset of them, are not supported, the MGCF shall not select the EVS payload type. If the MGCF selects the EVS payload type, it shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor.
|If a br-recv parameter is contained in the SDP offer, the MGCF shall select a bit rate value, which is either the received br-recv value or a subset of it, based on IM-MGW capabilities, possible configured policies and the br parameter value included in the SDP answer, and the MGCF shall include the br-send parameter with the selected value that is also supplied towards the IM-MGW in the SDP answer. Otherwise the MGCF shall not include the br-send parameter in the SDP answer. If the MGCF also supplies the bw or bw-send parameter, the value of the br-send parameter shall be compatible with the values of those parameters.
| +| br-recv (NOTE 1) |If a br-recv parameter is contained in the SDP offer, the MGCF shall check if the IM-MGW supports the indicated bit rates, or a subset of them, in EVS primary mode in the send direction. If the indicated bit rates, and even each subset of them, are not supported, the MGCF shall not select the EVS payload type. If the MGCF selects the EVS payload type, it shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor.
|If a br-send parameter is contained in the SDP offer, the MGCF shall select a bit rate value, which is either the received br-send value or a subset of it, based on IM-MGW capabilities, possible configured policies and the br parameter value included in the SDP answer, and the MGCF shall include the br-recv parameter with the selected value that is also supplied towards the IM-MGW in the SDP answer. Otherwise the MGCF shall not include the br-recv parameter in the answer. If the MGCF also supplies the bw or bw-recv parameter, the value of the br-recv parameter shall be compatible with the values of those parameters. If the MGCF supplies the br-recv parameter in the SDP answer, it shall also supply to the IM-MGW the br-recv parameter in the local descriptor for the termination towards the offerer with the same value.
| + +| | | | +|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| bw (NOTE 1) | If a bw parameter is contained in the SDP offer, the MGCF shall check if the IM-MGW supports the indicated sampling bandwidth(s), or a subset of them, in EVS primary mode in the send and receive direction. If the indicated sampling bandwidth(s), and even each subset of them, are not supported, the MGCF shall not select the EVS payload type. If the MGCF selects the EVS payload type, it shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | If a bw parameter is contained in the SDP offer, the MGCF shall select a sampling bandwidth value, which is either the received bw value or a subset of it, based on IM-MGW capabilities, possible configured policies and the CS configuration received in the Single Codec IE (see subclause B.2.5.5), and the MGCF shall include the bw parameter with the selected value that is also supplied towards the IM-MGW in the SDP answer. Otherwise the MGCF shall include the bw parameter in the SDP answer and shall set it to a range corresponding to the CS configuration received in the Single Codec IE (see subclause B.2.5.5). If the MGCF also supplies the br, br-send or br-recv parameter, the value of the bw parameter shall be compatible with the values of those parameters. The MGCF shall also supply the bw parameter to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. | +| bw-send (NOTE 1) | If a bw-send parameter is contained in the SDP offer, the MGCF shall check if the IM-MGW supports the indicated sampling bandwidths, or a subset of them, in EVS primary mode in the receive direction. If the indicated sampling bandwidths, and even each subset of them, are not supported, the MGCF shall not select the EVS payload type. If the MGCF selects the EVS payload type, it shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | If a bw-recv parameter is contained in the SDP offer, the MGCF shall select a sampling bandwidths value, which is either the received bw-recv value or a subset of it, based on IM-MGW capabilities, possible configured policies and the bw parameter value included in the SDP answer, and the MGCF shall include the bw-send parameter with the selected value in the SDP answer. Otherwise the MGCF shall not include the br-send parameter in the SDP answer. If the MGCF also supplies the bw or bw-send parameter, the value of the br-send parameter shall be compatible with the values of those parameters. If the MGCF supplies the bw-send parameter in the SDP answer, it shall also supply to the IM-MGW the bw-send parameter in the local descriptor for the termination towards the offerer with the same value. | +| bw-recv (NOTE 1) | If a br-recv parameter is contained in the SDP offer, the MGCF shall check if the IM-MGW supports the indicated sampling bandwidths, or a subset of them, in EVS primary mode in the send direction. If the indicated sampling bandwidths, and even each subset of them, are not supported, the MGCF shall not select the EVS payload type. If the MGCF selects the EVS payload type, it shall forward the bw-recv parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | If a bw-send parameter is contained in the SDP offer, the MGCF shall select a sampling bandwidths value, which is either the received bw-send value or a subset of it, based on IM-MGW capabilities, possible configured policies and the bw parameter value included in the SDP answer, and the MGCF shall include the bw-recv parameter with the selected value in the SDP answer. Otherwise the MGCF shall not include the bw-recv parameter in the SDP answer. If the MGCF also supplies the br or br-recv parameter, the value of the bw-recv parameter shall be compatible with the values of those parameters. If the MGCF supplies the bw-send parameter in the SDP answer, it shall also supply it to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. | + +| | | | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| cmr (NOTE 1) | If a cmr parameter is contained in the SDP offer, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. |If a cmr parameter is contained in the SDP offer, the MGCF shall include the cmr parameter with unmodified value in the SDP answer.
Otherwise, if the IM-MGW desires to disable codec mode requests within the RTP payload of the EVS primary mode (due to the IM-MGW capabilities and possible configured policies), it shall include the cmr parameter with value -1 in the SDP answer.
Otherwise the MGCF shall include the cmr parameter with a value of 1 in the SDP answer.
The MGCF shall also supply the cmr parameter to the IM-MGW in the local descriptor for the termination towards the offerer.
| +| ch-aw-recv (NOTE 1) | If a ch-aw-recv parameter is contained in the SDP offer the MGCF shall check if the CS side supports the indicated mode. If the indicated mode is not supported, the MGCF shall set this parameter to -1 and forward it to the IM-MGW for the termination towards the offerer in the remote descriptor. | If the MGCF desires to control the channel-aware mode of EVS in the receive direction, e.g. to disable it with value -1, it shall include the ch-aw-recv parameter in the SDP offer and shall also supply the ch-aw-recv parameter to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. The MGCF shall consider the capabilities of the IM-MGW when it chooses an appropriate value. | +| number of channels (NOTE 2) | If a "number of channels" parameter is contained in the SDP offer the MGCF shall check if the IM-MGW supports the indicated number of channels. If the indicated number of channels is not supported, the MGCF shall not select the EVS payload type. If the MGCF selects the EVS payload type, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | The MGCF shall include the "number of channels" parameter with a value of 1 in the SDP answer and shall also supply it to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. | +| ch-send (NOTE 1) | If a ch-send parameter is contained in the SDP offer the MGCF shall check if the IM-MGW supports the indicated number of channels in the receive direction. If the indicated number of channels is not supported, the MGCF shall not select the EVS payload type. If the MGCF selects the EVS payload type, the MGCF shall forward the ch-send parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | If a ch-recv parameter is contained in the SDP offer, the MGCF shall include the ch-send parameter with a value of 1 in the SDP answer and shall also supply the ch-send parameter to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. | +| ch-recv (NOTE 1) | If a ch-recv parameter is contained in the SDP offer the MGCF shall check if the IM-MGW supports the indicated number of channels in the send direction. If the indicated number of channels is not supported, the MGCF shall not select the EVS payload type. If the MGCF selects the EVS payload type, the MGCF shall forward the ch-recv parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | If a ch-send parameter is contained in the SDP offer, the MGCF shall include the ch-recv parameter with a value of 1 value in the SDP answer and shall also supply the ch-recv parameter to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. | + +| | | | +|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| mode-set (NOTE 3) | If a mode-set parameter is contained in the SDP offer and the mode-set parameter does not include mode set 0, the MGCF shall not select the EVS payload type. Otherwise, if a mode-set parameter is contained in the SDP offer, the mode-set parameter includes mode set 0 and the MGCF select the EVS payload type, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | If a mode-set parameter is contained in the SDP offer, the MGCF shall include the mode-set parameter with a value which is either the received mode-set parameter value or a subset of it, based on the CS configuration received in the Single Codec IE (see subclause B.2.5.5), in the SDP answer. Otherwise, the MGCF shall include the mode-set parameter in the SDP answer and shall set it to the range corresponding to the CS configuration received in the Single Codec IE (see subclause B.2.5.5). The MGCF shall also supply the mode-set parameter to the IM-MGW in the local descriptor for the termination towards the offerer. | +| mode-change-period (NOTE 3) | If a mode-change-period parameter is contained in the SDP offer and the MGCF select the EVS payload type, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | The MGCF shall include the mode-change-period parameter in the SDP answer and shall set it as per the received Single Codec IE (see subclause B.2.5.5). The MGCF shall also supply the mode-change-period parameter to the IM-MGW in the local descriptor for the termination towards the offerer. | +| mode-change-capability (NOTE 3) | If a mode-change-capability (NOTE 4) parameter is contained in the SDP offer and the MGCF select the EVS payload type, the MGCF may forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | The MGCF shall either include the mode-change-capability parameter with a value of 2 or omit it in the SDP answer. The MGCF may also supply the mode-change-capability parameter to the IM-MGW in the local descriptor for the termination towards the offerer. | +| mode-change-neighbor (NOTE 3) | If a mode-change-neighbor parameter is contained in the SDP offer and the MGCF select the EVS payload type, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | The MGCF shall include the mode-change-neighbor parameter in the SDP answer and shall set it as per the received Single Codec IE (see subclause B.2.5.5). The MGCF shall also supply the mode-change-neighbor to the IM-MGW in the local descriptor for the termination towards the offerer. | +| max-red (NOTE 5) | If a max-red parameter is contained in the SDP offer and the MGCF select the EVS payload type, the MGCF shall forward this parameter to the IM-MGW for the termination towards the offerer in the remote descriptor. | The MGCF shall only include the max-red parameter in the SDP answer if it desires to restrict the maximum redundancy of received packets. When selecting the value of the max-red parameter, the MGCF shall consider the capabilities of the IM-MGW. If the MGCF supplies the max-red parameter in the SDP answer, it shall also supply it to the IM-MGW in the local descriptor for the termination towards the offerer with the same value. | +| 3gpp_mtsi_app_adapt (NOTE 4) | If a 3gpp_mtsi_app_adapt SDP attribute is contained in the SDP answer, the MGCF shall forward this parameter to the IM-MGW in the remote descriptor. | If the IM-MGW supports RTCP APP based adaptation messages defined in TS 26.114 [104], and the MGCF has a policy to negotiate the usage of those messages, the MGCF shall include the 3gpp_mtsi_app_adapt SDP attribute indicating the allowed APP messages in the SDP answer. | + +- | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: This MIME parameter of the EVS RTP payload type is defined in TS 26.445 [147]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [56]. | +| NOTE 2: This number of channels are encoded as "encoding parameters" of the SDP "a=rtpmap" attribute defined in IETF RFC 4566 [56]. | +| NOTE 3: This MIME parameter of the EVS RTP payload type relates to EVS AMR-WB IO major operation mode and is defined in IETF RFC 4867 [23]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [56]. | +| NOTE 4: This SDP attribute is defined in TS 26.114 [104]. It applies to all codecs offered in an SDP media line. However, some values are specific to EVS. | +| NOTE 5: This MIME parameter of the EVS RTP payload type is defined in IETF RFC 4867 [23]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [56]. | +| NOTE 6: The received evs-mode-switch parameter has no influence on the Config-EVS-Code. | + +### 9.2.14 SDP Capability Negotiation (SDPCapNeg) + +The SDP Capability Negotiation (SDPCapNeg) as specified in IETF RFC 5939 [150] is adopted as an optional functionality to negotiate capabilities and their associated configurations according to 3GPP TS 24.229 [9]. + +The requirements and procedures as described in subclause 5.2.3 of 3GPP TS 23.333 [151] for MRFC and MRFP, apply to the MGCF and the IM-MGW when SDPCapNeg is used. + +### 9.2.15 Rate adaptation for media endpoints + +The MGCF and the IM-MGW may support rate adaptation for media endpoints using the enhanced bandwidth negotiation mechanism defined in 3GPP TS 26.114 [104]. + +The requirements and procedures as described in subclause 5.2.5 of 3GPP TS 23.333 [151] for the MRFC and the MRFP, apply to the MGCF and the IM-MGW if the MGCF and the IM-MGW perform media transcoding. + +## 9.3 Mn Signalling procedures + +This clause describes of logical signalling procedures (i.e. message identifiers are not part of the protocol) between the MGCF and IM-MGW. The procedures within this clause are intended to be implemented using the standard H.248 procedure as defined in ITU recommendation H.248.1 [2] with appropriate parameter combinations. + +### 9.3.1 Procedures related to terminations towards the IM CN Subsystem + +A mapping of the procedures defined here to H.248 procedures and parameters is provided in 3GPP TS 29.332 [15]. + +#### 9.3.1.1 Reserve IMS connection point + +This procedure is used to reserve local connection addresses and local resources. + +**Table 25: Procedures toward the IM Subsystem: Reserve IMS connection point** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|----------------------------------|-----------|------------------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserve IMS Connection Point | MGCF | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Priority information | O | This information element requests the IM-MGW to apply priority treatment for the terminations and bearer connections in the specified context. | +| | | IMS Termination Request | M | This information element requests a new IMS termination for the bearer to be established. | +| | | Local IMS Resources/ | M | This information element indicates the resource(s) (i.e. codecs) for which the IM-MGW shall be prepared to receive user data, | +| | | IP Interface Type | O | This information element indicates the used interface type | +| | | ReserveValue | O | This information element indicates if multiple local IMS resources are to be reserved. | +| | | Local Connection Addresses Request | M | This information element requests an IP address and port number on the IM-MGW that the remote end can send user plane data to. | +| | | Notify termination heartbeat | M | This information element requests termination heartbeat indications. | +| | | Notify Released Bearer | O | This information element requests a notification of a released bearer. | +| | | IP Realm Identifier | O | This information element indicates the IP realm of the IP termination. | +| | | ECN Enable | O | This information element requests the IM-MGW to apply ECN procedures | +| | | ECN Initiation Method | C | This information element specifies the ECN Initiation method and requests the IM-MGW to perform IP header settings as an ECN endpoint. It may be included only if ECN is enabled. | +| | | Notify ECN Failure Event | C | This information element requests a notification if an ECN failure occurs. It may only be supplied if ECN is enabled. | +| | | Diffserv Code Point | O | This information element requests the IM-MGW to apply a specific Diffserv Code Point to the IP headers. | +| | | ICE password request | O | This information element is present if MGCF requests an ICE password. | +| | | ICE Ufrag request | O | This information element is present if MGCF requests an ICE ufrag. | +| | | ICE host candidate request | O | This information element is present if MGCF requests an ICE host candidate. | +| | | STUN server request | O | This information element is present if MGCF requests the IM-MGW to answer STUN connectivity checks for ICE. | +| | | SDPCapNeg configuration | O | This information element provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. | +| Reserve IMS Connection Point Ack | IM-MGW | Context | M | This information element indicates the context where the command was executed. | +| | | IMS Termination | M | This information element indicates the IMS termination where the command was executed. | + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------|-----------|----------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Local IMS Resources | M | This information element indicates the resources that the IM-MGW has reserved to receive the user plane data from the IMS. | +| | | Local Connection Addresses | M | This information element indicates the IP address and port on the IM-MGW that shall receive user plane data from IMS. | +| | | ICE password | C | This information element shall be present only if it was contained in the request. It indicates the ICE password assigned by the IM-MGW. | +| | | ICE Ufrag | C | This information element shall be present only if it was contained in the request. It indicates the ICE Ufrag assigned by the IM-MGW. | +| | | ICE host candidate | C | This information element shall be present only if it was contained in the request. It indicates the ICE host candidate assigned by the IM-MGW. | +| | | ICE lite indication | C | This information element shall be present only if an ICE host candidate request was contained in the request, and the IM-MGW supports ICE lite, but not full ICE. It indicates that the IM-MGW only supports ICE lite. | +| | | SDPCapNeg configuration | C | This information element shall be present only if it was contained in the request. It provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. | + +#### 9.3.1.2 Configure IMS resources + +This procedure is used to select multimedia-processing resources for an Mb interface connection. + +**Table 26: Procedures toward the IM Subsystem: Select Local, +Select Remote IMS Processing Resource** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------|-----------|-------------------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Configure IMS Resources | MGCF | Context | M | This information element indicates the existing context. | +| | | IMS Termination | M | This information element indicates the existing bearer termination. | +| | | Local IMS Resources | O | This information element indicates the resources (i.e. codec) that the IM-MGW may use on the reception of user plane data. | +| | | Remote IMS Resources | M | This information element indicates the resources (i.e. codec) that the IM-MGW may send user plane data to. | +| | | Local Connection Addresses | O | This information element indicates the IP address and port on the IM-MGW that the IMS user can send user plane data to. | +| | | Remote Connection Addresses | M | This information element indicates the IP address and port that the IM-MGW can send user plane data to. | +| | | IP Interface Type | O | This information element indicates the used interface type | +| | | Reserve Value | O | This information element indicates if multiple IMS resources are to be reserved. | +| | | Remote Connection Addresses Source Filter | O | This information element indicates an optional source filter restricting the IP addresses and ports that the IM-MGW shall accept as source for incoming user plane data. If this information element is set, the IM-MGW shall silently discard incoming user plane data from disallowed sources. | +| | | ECN Enable | O | This information element requests the IM-MGW to apply ECN procedures. | +| | | ECN Initiation Method | C | This information element specifies the ECN Initiation method and requests the IM-MGW to perform IP header settings as an ECN endpoint. It may be included only if ECN is enabled. | +| | | Notify ECN Failure Event | C | This information element requests a notification if an ECN failure occurs. It may only be supplied if ECN is enabled. | +| | | ICE Connectivity Check | C | This information element requests the IM-MGW to perform ICE connectivity check as defined by IETF RFC 5245 [143]. It is only applicable for full ICE. | +| | | Notify ICE Connectivity Check Result | C | This information element requests a notification of ICE connectivity check result. It is only applicable for full ICE. | +| | | Notify New Peer Reflexive Candidate | C | This information element requests a notification of new peer reflexive candidate was discovered during a connectivity check. It is only applicable for full ICE. | +| | | Additional ICE Connectivity Check | C | This information element requests the IM-MGW to perform additional ICE connectivity check as defined by IETF RFC 5245 [143]. It is only applicable for full ICE. | +| | | ICE received candidate | O | This information element is present if MGCF indicates a received candidate for ICE. | +| | | ICE received password | O | This information element is present if MGCF indicates a received password for ICE. | + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------|-----------|---------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Allowed RTCP APP message types | O | This information element is present if the MGCF allows the IM-MGW to send RTCP APP packets of the indicated types. The IM-MGW shall not send other RTCP APP packets. If the parameter is not supplied, the IM-MGW shall not send any RTCP APP packets. | +| | | SDPCapNeg configuration | O | This information element provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. | +| | | Additional Bandwidth Properties | O | This information element indicates additional bandwidth properties using "a=bw-info" SDP attribute(s) as defined by 3GPP TS 26.114 [104]. | +| Configure IMS Resources Ack | IM-MGW | Context | M | This information element indicates the context where the command was executed. | +| | | IMS Termination | M | This information element indicates the IMS termination where the command was executed. | +| | | Local IMS Resource | O | This information element indicates the resources that the IM-MGW has reserved to receive the user plane data from the far end. | +| | | Remote IMS Resource | M | This information element indicates the resource (i.e. codec) that the IM-MGW shall use to send user data to. | +| | | Local Connection Address | O | This information element indicates the IP address and port on the IM-MGW that the remote end can send user plane data to. | +| | | Remote Connection Address | M | This information element indicates the IP address and port that the IM-MGW can send user plane data to. | + +#### 9.3.1.3 Reserve IMS Connection point and configure remote resources + +This procedure is used to reserve multimedia-processing resources for an Mb interface connection. + +**Table 27: Procedures toward the IM Subsystem: reserve local, reserve remote IMS connection point** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------------------------------------|-----------|-----------------------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserve IMS Connection Point and Configure Remote Resources | MGCF | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Priority information | O | This information element requests the IM-MGW to apply priority treatment for the terminations and bearer connections in the specified context. | +| | | IMS Termination/IMS Termination Request | M | This information element indicates the existing bearer termination or requests a new IMS termination for the bearer to be established. | +| | | Local IMS Resources | M | This information element indicates the resource(s) (i.e. codecs) for which the IM-MGW shall be prepared to receive user data. | +| | | Remote IMS Resources | M | This information element indicates the resources (i.e. codec) that the IM-MGW shall use to send user data in the IMS. | +| | | IP Interface Type | O | This information element indicates the used interface type | +| | | Reserve Value | O | This information element indicates if multiple IMS resources are to be reserved. | +| | | Local Connection Address request | M | This information element requests an IP address and a port number on the IM-MGW that the remote end can send user plane data to. | +| | | Remote Connection Addresses | M | This information element indicates the IP address and ports at an IMS user that the IM-MGW can send user plane data to. | +| | | Notify termination heartbeat | M | This information element requests termination heartbeat indications. | +| | | Notify Released Bearer | O | This information element requests a notification of a released bearer. | +| | | IP Realm Identifier | O | This information element indicates the IP realm of the IP termination. | +| | | ECN Enable | O | This information element requests the IM-MGW to apply ECN procedures and IP header settings as an ECN endpoint. | +| | | ECN Initiation Method | C | This information element specifies the ECN Initiation method and requests the IM-MGW to perform IP header settings as an ECN endpoint. It may be included only if ECN is enabled. | +| | | Notify ECN Failure Event | C | This information element requests a notification if an ECN failure occurs. It may only be supplied if ECN is enabled. | +| | | Diffserv Code Point | O | This information element requests the IM-MGW to apply a specific Diffserv Code Point to the IP headers. | +| | | STUN server request | O | This information element is present if MGCF requests the IM-MGW to answer STUN connectivity checks for ICE. | +| | | ICE Connectivity Check | C | This information element requests the IM-MGW to perform ICE connectivity check as defined by IETF RFC 5245 [143]. It is only applicable for full ICE. | +| | | Notify ICE Connectivity Check Result | C | This information element requests a notification of ICE connectivity check result. It is only applicable for full ICE. | + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------------------------------------------|-----------|-------------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Notify New Peer Reflexive Candidate | C | This information element requests a notification of new peer reflexive candidate was discovered during a connectivity check. It is only applicable for full ICE. | +| | | ICE password request | O | This information element is present if MGCF requests an ICE password. | +| | | ICE Ufrag request | O | This information element is present if MGCF requests an ICE ufrag. | +| | | ICE host candidate request | O | This information element is present if MGCF requests an ICE host candidate. | +| | | ICE received candidate | O | This information element is present if MGCF indicates a received candidate for ICE. | +| | | ICE received password | O | This information element is present if MGCF indicates a received password for ICE. | +| | | ICE received Ufrag | O | This information element is present if MGCF indicates a received Ufrag for ICE. | +| | | Allowed RTCP APP message types | O | This information element is present if the MGCF allows the IM-MGW to send RTCP APP packets of the indicated types. The IM-MGW shall not send other RTCP APP packets. If the parameter is not supplied, the IM-MGW shall not send any RTCP APP packets. | +| | | SDPCapNeg configuration | O | This information element provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. | +| | | Additional Bandwidth Properties | O | This information element indicates additional bandwidth properties using "a=bw-info" SDP attribute(s) as defined by 3GPP TS 26.114 [104]. | +| Reserve IMS Connection Point and Configure Remote Resources Ack | IM-MGW | Context | M | This information element indicates the context where the command was executed. | +| | | IMS Termination | M | This information element indicates the IMS termination where the command was executed. | +| | | Local IMS Resources | M | This information element indicates the resources that the IM-MGW has reserved to receive the user plane data from IMS. | +| | | Remote IMS Resources | M | This information element indicates the resource (i.e. codec) that the IM-MGW shall use to send user data. | +| | | Local Connection Addresses | M | This information element indicates the IP address on the IM-MGW that shall receive user plane data from the IMS. | +| | | ICE password | C | This information element shall be present only if it was contained in the request. It indicates the ICE password assigned by the IM-MGW. | +| | | ICE Ufrag | C | This information element shall be present only if it was contained in the request. It indicates the ICE Ufrag assigned by the IM-MGW. | +| | | ICE host candidate | C | This information element shall be present only if it was contained in the request. It indicates the ICE host candidate assigned by the IM-MGW. | +| | | ICE lite indication | C | This information element shall be present only if an ICE host candidate request was contained in the request, and the IM-MGW supports ICE lite, but not full ICE. It indicates that the IM-MGW only supports ICE lite. | + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------|-----------|--------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | SDPCapNeg configuration | C | This information element shall be present only if it was contained in the request. It provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. | + +#### 9.3.1.4 Release IMS termination + +This procedure is used by the MGCF to release a termination towards the IMS and free all related resources. + +**Table 28: Release IMS termination** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| Release IMS Termination | MGCF | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination to be released. | +| Release IMS Termination Ack | IM-MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +#### 9.3.1.5 Detect IMS RTP Tel event + +This procedure is used by the MGCF to request from the MGW the detection of telephony events signalled within RTP according to RFC 4733 [105] and the notification of received telephony events. This procedure is the same as that is defined in the clause "Detect DTMF" in 3GPP TS 23.205 [27]. + +**Table 29: VOID** + +#### 9.3.1.6 Notify IMS RTP Tel event + +This procedure is used by the MGW to notify the MGCF about the detection of telephony events signalled within RTP according to RFC 4733 [105]. This procedure is the same as that defined in the clause "Report DTMF" in 3GPP TS 23.205 [27]. + +**Table 30: VOID** + +#### 9.3.1.7 Void + +#### 9.3.1.8 Send IMS RTP Tel event + +This procedure is used by the MGCF to request from the MGW to signal a telephone event within RTP according to RFC 4733 [105]. This procedure is the same as that defined in the clause "Send DTMF" in 3GPP TS 23.205 [27]. + +#### 9.3.1.9 Stop IMS RTP Tel event + +This procedure is used by the MGW to request from the MGW to stop signalling a telephone event within RTP according to RFC 4733 [105]. This procedure is the same as that defined in the clause "Stop DTMF" in 3GPP TS 23.205 [27]. + +#### 9.3.1.10 Termination heartbeat indication + +This procedure is used to report indication of hanging termination. + +**Table 30a: Procedures between (G)MSC server and MGW: Hanging termination indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------------------------------| +| Termination heartbeat indication | MGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the termination heartbeat is reported. | +| | | Termination heartbeat | M | Hanging Termination event, as defined in TS 29.332 [15]. | +| Termination heartbeat indication Ack | (G)MSC-S | Context | M | This information element indicates the context where the command was executed. | + +#### 9.3.1.11 IMS Bearer Released + +This procedure is used by the IM-MGW to indicate towards the MGCF that an error occurred on an IMS termination which requires the release of the termination. This procedure is the same as that defined in the clause "Bearer Released" in 3GPP TS 23.205 [27]. + +#### 9.3.1.12 End IMS RTP Tel event + +This procedure is used by the MGCF to indicate to the IM-MGW to stop detection of telephony events signalled within RTP according to IETF RFC 4733 [105]. This procedure is the same as that is defined in the clause "Stop Detect DTMF" in 3GPP TS 23.205 [27]. + +#### 9.3.1.13 IMS Send Tone + +This procedure is used by the MGCF to order the IM-MGW to generate a tone at termination towards IMS. This procedure is the same as that defined in the clause "Send Tone" in 3GPP TS 23.205 [27]. + +#### 9.3.1.14 IMS Stop Tone + +This procedure is used by the MGCF to order the IM-MGW to stop generating a tone at a termination towards IMS. This procedure is the same as that defined in the clause "Stop Tone" in 3GPP TS 23.205 [27]. + +#### 9.3.1.15 IMS Tone Completed + +This procedure is used by the IM-MGW to indicate to the MGCF that a tone has finished being generated at a termination. This procedure is the same as that defined in the clause "Tone Completed" in 3GPP TS 23.205 [27]. + +#### 9.3.1.16 ECN Failure Indication + +This procedure is used to report ECN related errors (see clause 9.2.11.1c). + +**Table 9.3.1.16.1: Procedures toward the IM Subsystem: ECN Failure Indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|----------------------------|-----------|--------------------------|------------------------------|--------------------------------------------------------------------------------------------------| +| ECN Failure Indication | IM-MGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the ECN failure is reported. | +| | | ECN Failure Indication | M | This IE indicates an ECN failure event. | +| ECN Failure Indication Ack | MGCF | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed | + +#### 9.3.1.17 ICE Connectivity Check Result Notification + +This procedure is used to report ICE connectivity check result for Full ICE. + +**Table 9.3.1.17.1: Procedures between MGCF and IM-MGW: ICE Connectivity Check Result Notification** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------------------------------|-----------|-------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------| +| ICE Connectivity Check Result Notification | IM-MGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the ICE Connectivity Check Result is reported. | +| | | ICE Connectivity Check Result | M | This information element indicates an ICE Connectivity Check Result event. | +| ICE Connectivity Check Result Notification Ack | MGCF | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +#### 9.3.1.18 ICE New Peer Reflexive Candidate Notification + +This procedure is used to report ICE new peer reflexive candidate for Full ICE. + +**Table 9.3.1.18.1: Procedures between MGCF and IM-MGW: ICE New Peer Reflexive Candidate Notification** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------------------------------|-----------|----------------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------| +| ICE New Peer Reflexive Candidate Notification | IM-MGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the ICE New Peer Reflexive Candidate is reported. | +| | | ICE New Peer Reflexive Candidate | M | This information element indicates an ICE New Peer Reflexive Candidate event. | +| ICE New Peer Reflexive Candidate Notification Ack | MGCF | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 9.3.2 Procedures related to a termination towards an ISUP network + +A mapping of the procedures defined here to H.248 procedures and parameters is provided in 3GPP TS 29.332 [15]. + +#### 9.3.2.1 Reserve TDM circuit + +This procedure is used by the MGCF to reserve a TDM circuit in the IM-MGW towards the preceding/succeeding CS network element. + +**Table 31: Reserve TDM circuit procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------|-----------|--------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------| +| Reserve TDM Circuit | MGCF | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the physical bearer termination for the TDM circuit. | +| | | Bearer Service Characteristics | M | This information element indicates the bearer service requested by the user. | +| | | Notify termination heartbeat | O | This information element requests termination heartbeat indications. | +| | | Notify Released Bearer | O | This information element requests a notification of a released bearer | +| Reserve Circuit Ack | IM-MGW | Context | M | This information element indicates the context where the command was executed. | + +#### 9.3.2.2 Change TDM through-connection + +This procedure is used by the MGCF to modify the through-connection (forward, backward, both-way, inactive) of a TDM termination at the IM-MGW towards the PSTN. + +This procedure is the same as Change Through Connection in 3GPP TS 23.205 [27]. + +#### 9.3.2.3 Activate TDM voice-processing function + +This procedure is used by the MGCF to activate or de-activate a voice processing function of a TDM termination at the IM-MGW towards the PSTN. This voice processing function may include a cancellation for electronic echoes. + +This procedure is the same as Activate Voice Processing Function in 3GPP TS 23.205 [27]. + +#### 9.3.2.4 Send TDM tone + +This procedure is used by the MGCF to order the IM-MGW to generate a tone at a TDM termination towards the PSTN. + +This procedure is the same as Send Tone in 3GPP TS 23.205 [27]. + +#### 9.3.2.5 Stop TDM tone + +This procedure is used by the MGCF to order the IM-MGW to stop generating a tone at a TDM termination towards the PSTN. + +This procedure is the same as Stop tone in 3GPP TS 23.205 [27]. + +#### 9.3.2.6 Play TDM announcement + +This procedure is used by the MGCF to order the IM-MGW to generate an announcement at a TDM termination towards the PSTN. The MGCF may request a notification that the announcement is completed. This procedure is the same as Play Announcement in 3GPP TS 23.205 [27]. This procedure is optional. + +#### 9.3.2.7 TDM announcement completed + +This procedure is used by the IM-MGW to notify the MGCF that an announcement at a TDM termination towards the PSTN is completed. This procedure is the same as Announcement Completed in 3GPP TS 23.205 [27]. This procedure is optional. + +#### 9.3.2.8 Stop TDM announcement + +This procedure is the same as Stop Announcement 3GPP TS 23.205 [27]. This procedure is used by the MGCF to order the IM-MGW to stop generating an announcement at a TDM termination towards the PSTN. This procedure is optional. + +#### 9.3.2.9 Continuity check + +This procedure is used by the MGCF to order the IM-MGW to generate a continuity check tone at a TDM termination towards the PSTN and to inform the MGCF about the result of the continuity check as soon as the continuity check tone is received or a time-out occurs. This procedure is optional. + +**Table 32: Continuity check procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------|-----------|---------------------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------| +| Continuity check | MGCF | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | TDM Termination | M | This information element indicates the existing bearer termination | +| | | Request for continuity tone sending | M | This information request the IM-MGW to apply the continuity check procedure on the indicated TDM termination | +| | | Request for continuity check tone detection | M | This information request the IM-MGW to inform e continuity check procedure on the indicated TDM termination | + +#### 9.3.2.10 Continuity check verify + +This procedure is used by the IM-MGW to indicate towards the MGCF that the continuity check at a TDM termination towards the PSTN has been completed and to return the result of the check: success or failure. This procedure is optional. + +**Table 33: Continuity check verify procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------|-----------|---------------------------------|------------------------------|--------------------------------------------------------------------------------------------------| +| Continuity check Verify | IM-MGW | Context/t | M | This information element indicates the context where the command was executed. | +| | | TDM Termination | M | This information element indicates the TDM termination involved in the procedure | +| | | Outcome of the continuity check | M | This information element indicates the outcome of the continuity check (successful/unsuccessful) | + +#### 9.3.2.11 Continuity check response + +This procedure is used by the MGCF to order the IM-MGW to loop back an incoming continuity check tone at a TDM termination towards the PSTN. This procedure is optional. + +**Table 34: Continuity check response procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------|-----------|----------------------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------| +| Continuity check response | MGCF | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | TDM Termination | M | This information element indicates the existing bearer termination | +| | | Request for loop back of the continuity tone | M | This information request the IM-MGW to loop back the continuity check tone on the indicated TDM termination | + +#### 9.3.2.12 Release TDM termination + +This procedure is used by the MGCF to release a TDM termination at the IM-MGW towards the PSTN and free all related resources. + +**Table 35: Release TDM termination procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| Release TDM Termination | MGCF | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination to be released. | +| Release TDM Termination Ack | IM-MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +#### 9.3.2.13 Termination Out-of-Service + +This procedure is used by the IM-MGW to indicate towards the MGCF that one or several physical termination(s) will go out of service. This procedure is the same as Termination Out-of-Service in 3GPP TS 23.205 [27]. + +#### 9.3.2.14 Termination heartbeat indication + +This procedure is used to report indication of hanging termination. + +**Table 35a: Procedures between (G)MSC server and MGW: Hanging termination indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------------------------------| +| Termination heartbeat indication | MGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the termination heartbeat is reported. | +| | | Termination heartbeat | M | Hanging termination event, as defined in TS 29.332 [15]. | +| Termination heartbeat indication Ack | (G)MSC-S | Context | M | This information element indicates the context where the command was executed. | + +#### 9.3.2.15 Bearer Released + +This procedure is used by the IM-MGW to indicate towards the MGCF that an error occurred on a physical termination which requires the release of the termination. This procedure is the same as Bearer Released in 3GPP TS 23.205 [27]. + +#### 9.3.2.16 TDM tone completed + +This procedure is used by the IM-MGW to MGCF to indicate that a tone has finished being generated at a TDM termination. + +This procedure is the same as Tone Completed in 3GPP TS 23.205 [27]. + +### 9.3.3 Procedures related to a termination towards a BICC network + +The call related procedures detailed in table 36 shall be supported. Those procedures are defined in 3GPP TS 29.332 [15]. + +**Table 36: Required procedures defined in TS 29.332 [15]** + +| Procedure defined in TS 29.332 [15] | Remarks | +|--------------------------------------------|---------------------------------------------------| +| Establish Bearer | | +| Prepare Bearer | | +| Change Through-Connection | | +| Release Bearer | | +| Release Termination | | +| Bearer Established | | +| Bearer Released | | +| Send Tone | | +| Stop Tone | | +| Tone completed | | +| Play Announcement | Optional | +| Stop Announcement | Optional | +| Announcement Completed | Optional | +| Confirm Char | Optional | +| Modify Bearer Characteristics | Optional | +| Reserve Char | Optional | +| Bearer Modified | Optional | +| Activate Voice Processing Function | Optional | +| Tunnel Information Down | Conditional: For IP Transport at BICC termination | +| Tunnel Information Up | Conditional: For IP Transport at BICC termination | +| Termination Out-of-Service | | +| Termination heartbeat indication | | + +### 9.3.4 Non-call related procedures + +The procedures from 3GPP TS 23.205 [27] detailed in table 37 shall be applied for the IM-MGW handling component of the Mn interface. + +**Table 37: Non-call related procedures** + +| Procedure defined in TS 29.332 [15] | Corresponding Procedure defined in TS 23.205 [27] | Remarks | +|--------------------------------------------------|---------------------------------------------------|--------------------------------------------------------------------------------------------------------------------| +| IM-MGW Out of service | MGW Out of Service | | +| IM-MGW Communication Up | MGW Communication Up | | +| IM-MGW Restoration | MGW Restoration | | +| IM-MGW Register | MGW Register | | +| IM-MGW Re-register | MGW Re-register | | +| MGCF Ordered Re-register | (G)MSC Server Ordered Re-register | | +| MGCF Restoration | (G)MSC Server Restoration | | +| MGCF Out of Service | (G)MSC Server Out of Service | | +| Termination Out-of-Service | Termination Out-of-Service | The "Termination Out-of-Service procedure" is used as call-related H.248 command as well | +| Termination Restoration | Termination Restoration | | +| Audit Value | Audit Value | | +| Audit Capability | Audit Capability | | +| Command Rejected | Command Rejected | The "Command Rejected" procedure may be used in response both to call-related and non-call-related H.248 Commands. | +| IM-MGW Capability Change | Capability Update | | +| IM-MGW Resource Congestion Handling - Activate | MGW Resource Congestion Handling - Activate | | +| IM-MGW Resource Congestion Handling - Indication | MGW Resource Congestion Handling - Indication | | +| Control association monitoring | Control association monitoring | | +| Inactivity timeout activation | Inactivity timeout activation | | +| Inactivity timeout indication | Inactivity timeout indication | | +| Hanging termination detection | Hanging termination detection | | +| Hanging termination detection | Hanging termination detection | | + +### 9.3.5 Multiple IP Realms + +The procedures to support multiple IP realms in the present clause are optional. + +Figure 9.3.5.1 shows a scenario where multiple IP realms are applied. + + + +The diagram illustrates a central box labeled "IM-MGW". Inside this box, there are two sub-boxes labeled "Termination 1" and "Termination 2". To the left of the "IM-MGW" box is a cloud-shaped icon labeled "IM CN1", connected to the "Termination 1" box by a line with a small circle at the connection point. To the right of the "IM-MGW" box is another cloud-shaped icon labeled "CS CN1", connected to the "Termination 2" box by a line with a small circle at the connection point. + +Diagram of Multiple IP realms scenario showing IM CN1 connected to Termination 1 and CS CN1 connected to Termination 2 of an IM-MGW. + +**Figure 9.3.5.1 Multiple IP realms scenario** + +Shown in figure 9.3.5, the IM CN1 and CS CN1 represent separate IP realms. The definition of IP realm is specified in IETF RFC 2663[90]. + +The termination1 and termination2 are connected with different IP realms in the IM-MGW separately. + +For establishing session when multiple IP realms are used in the IM-MGW, the MGCF may indicate the IP realm identifier to the IM-MGW. The IM-MGW shall assign the IP termination with the indicated IP realm. + +A default IP realm may be configured in IM-MGW such that if the IM-MGW has not received the IP realm identifier and the IM-MGW supports multiple IP realms then the default IP realm shall be used. + +If the IM-MGW does not support the option to indicate an IP realm then it is free to select any IP port. + +## 9.4 Multimedia Priority Service (MPS) Support + +### 9.4.1 General + +The Multimedia Priority Service (MPS) is specified in 3GPP TS 22.153 [136]. The MGCF/IM-MGW may support the priority treatment of a call/session identified as an MPS call/session. If MPS is supported then upon receipt of the MPS priority information in the call control signalling: + +- The MGCF shall recognise the call/session as having priority. +- The MGCF shall send the Priority information for a context to the IM-MGW to enable the priority treatment described below related to the IM-MGW. +- The MGCF shall apply priority handling to H.248 transactions related to priority calls/sessions when network resources are congested, e.g., preferential treatment in any queues or buffers. +- If the H.248 control association utilises a transport with the possibility for prioritisation, the MGCF may apply priority using the appropriate prioritisation procedures. +- If the MPS Priority service requires a specific MPS DSCP setting, the MGCF shall configure the IM-MGW to apply a specific MPS DSCP marking to the user data transport packets to indicate that the packets are of a higher priority than those for normal calls. +- If the IM-MGW receives an indication to apply a specific MPS DSCP marking to the user data transport packets, it shall apply this DSCP marking to the IP headers. + +NOTE 1: Support of Diffserv procedures by the IMS-MGW assumes an operator uses Diffserv for prioritising user plane traffic related to an MPS call/session. + +- When the MGCF marks a Context with Priority information, the IM-MGW may use the Priority information for selecting resources for the media and 294isalignme transport with priority. The following actions may be taken by the IM-MGW if it has reached a congested state: + - i) seize priority reserved resources; or + - ii) if resources are completely congested, indicate that in a Command Response error code. + +NOTE 2: The Priority information can be used to derive Layer 2 QoS marking and trigger priority identification and priority treatment for other QoS technologies than Diffserv. + +This clause describes the Mn signalling procedures and their interactions with SIP signalling in the control plane and with user plane procedures to support the requirements for MPS. These Mn signalling procedures may or may not apply depending on the network configuration (e.g. whether the IM-MGW is shared by multiple MGCFs or whether the MGCF controls multiple IM-MGWs for a given route - Media Gateway Group). + +The MGCF can receive a SIP INVITE with MPS priority information (see 3GPP TS 23.228 [12], clause 5.21). + +### 9.4.2 IM-MGW Resource Congestion in ADD response, request is queued + +If the MGCF requests a resource via the Reserve IMS Connection Point and configure remote resources procedure or Reserve IMS Connection Point procedure and receives an error indicating that the requested resource could not be seized (e.g. H.248 error code #510 "insufficient resources") and the MGCF does not have an alternative IM-MGW through which it can route the call/session, the MGCF queues the priority call/session and gives it priority over any further Reserve IMS Connection Point and configure remote resources or Reserve IMS Connection Point procedures for + +lower priority calls/sessions towards this IM-MGW until the requested resource for this queued call/session is successfully seized. The example sequence is shown in Figure 9.4.2.1. + + + +``` + +sequenceDiagram + participant External + participant MGCF + participant IM-MGW + Note right of IM-MGW: IM-MGW is Congested + External->>MGCF: 1. INVITE [MPS priority indication] + Note left of MGCF: Reserve IMS Connection Point + MGCF->>IM-MGW: 2. H.248 ADD Req [C=?, T=?, Laddr=?, Lport=?, Local Resources, Priority] + IM-MGW-->>MGCF: 3. H.248 ADD Reject [Error = #510] + Note left of MGCF: 4. MGCF queues MPS request + Note left of MGCF: Reserve IMS Connection Point + MGCF->>IM-MGW: 5. H.248 ADD Req [C=?, T=?, Laddr=?, Lport=?, Local Resources, Priority] + Note right of IM-MGW: IM-MGW successfully seizes required resources + IM-MGW-->>MGCF: 6. H.248 ADD Resp [C=C1, T=T2, Laddr=IP2o, LPort=P2o] + +``` + +Sequence diagram for Figure 9.4.2.1: Request to Reserve MPS priority call resources when IM-MGW is congested. The diagram shows the interaction between an MGCF and an IM-MGW. The MGCF sends an INVITE with MPS priority indication. It then attempts to reserve an IMS Connection Point, which triggers an H.248 ADD Req to the IM-MGW. The IM-MGW responds with an H.248 ADD Reject (Error #510) because it is congested. The MGCF then queues the MPS request. After queuing, it attempts to reserve the IMS Connection Point again, which triggers another H.248 ADD Req to the IM-MGW. The IM-MGW then successfully seizes the required resources and responds with an H.248 ADD Resp. + +Figure 9.4.2.1: Request to Reserve MPS priority call resources when IM-MGW is congested + +### 9.4.3 IM-MGW Resource Congestion in ADD response, MGCF seizes new IM-MGW + +If the MGCF requests a resource via the Reserve IMS Connection Point and configure remote resources procedure or Reserve IMS Connection Point procedure and receives an error indicating that the requested resources could not be seized due to congestion (e.g. H.248 error code #510 "insufficient resources") and Media Gateway Groups are implemented the MGCF seizes a new IM-MGW from the same Media Gateway Group before resorting to any queuing of the priority call/session (as described in clause 9.4.2) to enable the MPS call/session to proceed as early as possible. + +### 9.4.4 IM-MGW Priority Resource Allocation + +If the IM-MGW supports the Priority information (e.g. determined through provisioning or package profile), the MGCF requests a resource via the Reserve IMS Connection Point and configure remote resources procedure or Reserve IMS Connection Point procedure and includes the Priority information. The IM-MGW may then provide priority allocation of resources once a congestion threshold is reached. The example sequence is shown in Figure 9.4.4.1. If the IM-MGW is completely congested it shall indicate this to the MGCF as described in clause 9.4.2. + + + +``` + +sequenceDiagram + participant External + participant MGCF + participant IM-MGW + Note right of IM-MGW: IM-MGW is in a congested state but allocates priority resources to this call. + External->>MGCF: 1. INVITE [MPS priority indication] + Note left of MGCF: Reserve IMS Connection Point + MGCF->>IM-MGW: 2. H.248 ADD Req [C=?, T=?, Laddr=?, Lport=?, Local Resources, Priority] + IM-MGW-->>MGCF: 3. H.248 ADD Resp [C=C1, T=T2, Laddr=IP2o, LPort=P2o] + +``` + +Sequence diagram for Figure 9.4.4.1: Request to reserve MPS priority call resources when IM-MGW is congested, priority resources are allocated. The diagram shows the interaction between an MGCF and an IM-MGW. The MGCF sends an INVITE with MPS priority indication. It then attempts to reserve an IMS Connection Point, which triggers an H.248 ADD Req to the IM-MGW. The IM-MGW responds with an H.248 ADD Resp, indicating that it is in a congested state but has allocated priority resources to this call. + +Figure 9.4.4.1: Request to reserve MPS priority call resources when IM-MGW is congested, priority resources are allocated + +The IM-MGW may also provide priority allocation for resources requested via a subsequent Configure IMS resources procedure not including Priority information if the related context has been marked with priority information during the Reserve IMS Connection Point procedure or Reserve IMS Connection point and configure remote resources procedure. + +### 9.4.5 IM-MGW Priority User Data marking + +The MGCF may request the streams associated to an MPS call/session to be marked with a certain priority code point as described in clause 8.4. The IM-MGW shall then mark each IP packet header accordingly. The example sequence is shown in Figure 9.4.5.1. + + + +``` +sequenceDiagram + participant External + participant MGCF + participant IM-MGW + Note left of MGCF: Reserve IMS Connection Point + External->>MGCF: 1. INVITE [MPS priority indication] + MGCF->>IM-MGW: 2. H.248 ADD Req [C=?, T= ?, Laddr = ?, Lport = ?, Local Resources, Diffserv Mark = DSCP1, Priority] + IM-MGW-->>MGCF: 3. H.248 ADD Resp [C=C1, T=T2, Laddr=IP2o, LPort=P2o] + Note right of IM-MGW: IM-MGW is requested to apply DSCP value in IP header of user data packets. +``` + +The diagram illustrates a sequence of interactions between an MGCF and an IM-MGW. It begins with an external INVITE message containing an MPS priority indication. The MGCF then sends an H.248 ADD Request to the IM-MGW, specifying parameters like C, T, Laddr, Lport, Local Resources, Diffserv Mark (DSCP1), and Priority. The IM-MGW responds with an H.248 ADD Response containing updated parameters like C=C1, T=T2, Laddr=IP2o, and LPort=P2o. A note on the right indicates that the IM-MGW is requested to apply the DSCP value in the IP header of user data packets. A bracket on the left side of the MGCF lifeline groups the INVITE and the subsequent H.248 messages under the label 'Reserve IMS Connection Point'. + +Sequence diagram showing the request to reserve IMS resources and apply DSCP marking for MPS between MGCF and IM-MGW. + +**Figure 9.4.5.1: Request to reserve IMS resources and apply DSCP marking for MPS** + +# --- Annex A (informative): Void + +# --- Annex B (normative): Codec Negotiation between a BICC CS network and the IM CN subsystem + +## B.1 Introduction + +This annex describes optional procedures for interworking of codec negotiation between a BICC CS network and the IM CN subsystem. + +## --- B.2 Control plane interworking + +The following optional procedures apply in addition to the procedures of clause 7.3 when both the BICC CS network and the IM CN subsystem support codec negotiation. All five variations of the bearer set-up procedures defined in clauses 7.4 and 7.5 of ITU-T Q.1902.4 [30] are supported. The codec negotiation procedures are also independent of the procedures for interworking between continuity procedures and SDP preconditions. + +### B.2.1 Incoming call interworking from SIP to BICC at I-MGCF + +#### B.2.1.1 Sending of IAM + +When the I-MGCF receives an INVITE with SDP offer, the I-MGCF shall follow the procedures of clause B.2.5 to convert the list of codecs in the SDP offer into a Supported Codec List for transmission in the outgoing IAM, according to clause 8.3.1 of ITU-T Q.1902.4 [30], and deleting those codecs not supported at the IM-MGW. When generating the Supported Codec List, the I-MGCF should add to the SDP offer all codec configurations for which it can provide transcoding. The I-MGCF shall allocate any IM-MGW resources as necessary to support the chosen bearer set-up procedures towards the BICC CS network. + +When the I-MGCF receives an INVITE without SDP offer, the I-MGCF shall continue call establishment without interworking of codec negotiation procedures. The mid-call interworking procedures of clause B.2.3 and clause B.2.4 may still apply. + +#### B.2.1.2 Sending of SDP answer + +The I-MGCF shall suspend the SDP answer procedure until it receives backward codec information from the BICC serving node terminating codec negotiation. When the I-MGCF receives the backward codec information, it shall select a codec configuration for use on the bearer interface to the IM CN subsystem from the codecs in the SDP offer, format an SDP answer based on this selected codec, send the SDP answer to the offerer in the appropriate SIP message (e.g., a reliable 18x response), and complete bearer establishment procedures. To avoid allocating a transcoder at the IM-MGW, the I-MGCF should preferably select a codec for the IM CN subsystem by converting the Selected Codec from the BICC CS network into an SDP answer according to the procedures of clause B.2.5, if allowed by the SDP offer/answer rules. Otherwise the I-MGCF should select the highest priority codec from the codecs in the received SDP offer supported by the IM-MGW for insertion in the SDP answer. Note that the I-MGCF stores the Available Codec List and does not send it to the offerer in the SDP answer. Codec negotiation is complete so it is not necessary for the offerer to begin a second phase offer/answer exchange using the PRACK request. + +### B.2.2 Outgoing call interworking from BICC to SIP at O-MGCF + +#### B.2.2.1 Sending of INVITE + +When the O-MGCF receives an IAM, the O-MGCF shall follow the procedures of clause B.2.5 to convert the Supported Codec List from the IAM into an SDP offer for transmission in the outgoing INVITE request, according to RFC 3264, deleting those codecs not supported at the IM-MGW. When generating the SDP offer, the O-MGCF should include all codec configurations for which it can provide transcoding in addition to those converted from the Supported Codec List. The O-MGCF shall include at least one AMR codec configuration in the SDP offer. The O-MGCF shall allocate any IM-MGW resources as necessary to support the inclusion of session address information in the SDP offer towards the IM CN subsystem. + +#### B.2.2.2 Responding to serving node initiating codec negotiation + +The O-MGCF shall suspend the incoming bearer set-up procedure while waiting for receipt of the SDP answer from the IM CN subsystem. When the O-MGCF receives the SDP answer while suspending the incoming bearer set-up procedure, it shall select a codec configuration for use on the bearer interface to the IM CN subsystem from the codecs in the SDP answer, construct the Available Codec List for the BICC CS network from the list of codecs received in the Supported Codec List by removing codecs not supported at the IM-MGW, choose the Selected Codec for the BICC CS network from the codecs in the Available Codec List, initiate the second SDP offer/answer exchange with the IM CN subsystem using the codec selected for the IM CN subsystem, if necessary, and resume the incoming bearer set-up procedure in the BICC CS network. The O-MGCF should select codecs for the bearer interfaces to the BICC CS network and IM CN subsystem in such a way as to avoid transcoding at the IM-MGW and minimize speech degradation, if possible, according to clause B.2.5. Otherwise the O-MGCF should choose the highest priority codec from the Available Codec List as the Selected Codec for the BICC CS network, and the highest priority codec from the codecs in the SDP answer as the codec for the IM CN subsystem. If the SDP answer only included a single voice codec, then there is no need for a second SDP offer/answer exchange, and the codec selected for the IM CN subsystem is the codec in the SDP answer. + +Certain BICC timers or events can force completion of the incoming bearer set-up procedure before the O-MGCF receives the SDP answer from the IM CN subsystem. In this case, the O-MGCF shall perform the terminating codec negotiation procedure according to clause 8.3.3 of ITU-T Q.1902.4 [30], including all supported codecs in the Available Codec List, and shall resume the incoming bearer set-up procedure without waiting any longer for the SDP answer. + +When an SDP answer arrives from the IM CN subsystem in response to the SDP offer in an INVITE request after the BICC incoming bearer set-up procedure has started, the O-MGCF shall select a codec configuration for use on the bearer interface to the IM CN subsystem from the codecs in the SDP answer, choose a new Selected Codec for the BICC CS network from the codecs in the Available Codec List constructed during incoming bearer set-up, and initiate the second SDP offer/answer exchange with the IM CN subsystem using the codec selected for the IM CN subsystem, if necessary. The O-MGCF should select codecs for the bearer interfaces to the BICC CS network and IM CN subsystem in such a way as to avoid transcoding at the IM-MGW and minimize speech degradation, if possible, according to clause B.2.5. Otherwise the O-MGCF should select the highest priority codecs from the available options for the two bearer interfaces. If the SDP answer only included a single voice codec, then there is no need for a second SDP offer/answer exchange, and the codec selected for the IM CN subsystem is the codec in the SDP answer. When the call in the BICC CS network enters a state capable of supporting codec modification, if the new Selected Codec is different from the Selected Codec chosen during the incoming bearer set-up procedure for the BICC CS network, the O-MGCF should initiate the codec modification procedure towards the BICC CS network using the new Selected Codec, according to clause 10.4.1 of ITU-T Q.1902.4 [30]. + +### B.2.3 Mid-call interworking from SIP to BICC at I-MGCF or O-MGCF + +#### B.2.3.1 Receipt of SDP offer + +When the MGCF receives a SIP message (e.g. UPDATE request or re-INVITE request) with an SDP offer that is not associated with incoming call bearer establishment or preconditions, if the call is in a state capable of supporting BICC codec negotiation, the MGCF shall follow the procedures of clause B.2.5 to convert the list of codecs in the SDP offer into a Supported Codec List, delete those codecs in the Supported Codec List not supported at the IM-MGW, and initiate the mid-call codec negotiation procedure according to clause 10.4.4 of ITU-T Q.1902.4 [30], by sending an APM with the Supported Codec List and an Action indicator set to "mid-call codec negotiation". When generating the Supported Codec List, the MGCF should add to the SDP offer all codec configurations for which it can provide transcoding. + +When the MGCF receives a SIP message with an SDP offer that is not associated with incoming call bearer establishment or preconditions, if the call is not in a state capable of supporting BICC codec negotiation, the MGCF shall respond to the SDP offer with existing procedures for the IM CN subsystem. When the call is in a state capable of supporting BICC codec negotiation, the MGCF may send a re-INVITE request without SDP towards the IM CN subsystem, soliciting a response with an SDP offer, thereby restarting the codec negotiation interworking procedure. + +#### B.2.3.2 Generating SDP answer + +After initiating a BICC codec negotiation procedure towards the BICC CS network in response to receipt of a SIP message with an SDP offer from the IM CN subsystem, the MGCF shall suspend the SDP answer procedure until it receives codec information from the succeeding BICC serving node. If the succeeding serving node returns a successful response, the MGCF shall select a codec configuration for use on the bearer interface to the IM CN subsystem from the codecs in the SDP offer, format an SDP answer based on this selected codec, send the SDP answer to the offerer in the appropriate SIP message (e.g. 200 OK (UPDATE) or 200 OK (INVITE)), send an APM to the succeeding serving node with an Action indicator set to "successful codec modification", and complete bearer establishment procedures. To avoid allocating a transcoder at the IM-MGW, the MGCF should preferably select a codec for the IM CN subsystem by converting the Selected Codec from the BICC CS network into an SDP answer according to the procedures of clause B.2.5, if allowed by the SDP offer/answer rules. Otherwise the MGCF should select the highest priority codec from the codecs in the received SDP offer supported by the IM-MGW for insertion in the SDP answer. Note that the MGCF stores the Available Codec List and does not send it to the offerer in the SDP answer. + +If the succeeding serving node returns an Action indicator set to "mid-call codec negotiation failure", the MGCF either should send a 488 response to the SDP offerer indicating rejection of the initial SDP offer, or should select the highest priority codec from the codecs in the received SDP offer supported by the IM-MGW, format an SDP answer based on this selected codec, and send the SDP answer to the offerer in the appropriate SIP message. If the MGCF sends a 488 response to the SDP offerer, it should continue the call with the bearer configuration in place before initiating this codec negotiation procedure. + +### B.2.4 Mid-call interworking from BICC to SIP at I-MGCF or O-MGCF + +#### B.2.4.1 Receipt of mid-call codec negotiation request + +When the MGCF receives an APM with an Action indicator set to "mid-call codec negotiation", the MGCF shall follow the procedures of clause B.2.5 to convert the Supported Codec List from the APM into an SDP offer for transmission in an appropriate SIP message (e.g. re-INVITE request) towards the IM CN subsystem, according to RFC 3264 [36], deleting those codecs not supported at the IM-MGW. When generating the SDP offer, the MGCF should include all codec configurations for which it can provide transcoding in addition to those converted from the Supported Codec List. The MGCF shall include at least one AMR codec configuration in the SDP offer. + +#### B.2.4.2 Responding to serving node initiating mid-call codec negotiation + +The MGCF shall delay responding to the mid-call codec negotiation from the BICC CS network until it receives a response to the SDP offer from the IM CN subsystem. If the MGCF receives an SDP answer, it shall construct the Available Codec List for the BICC CS network from the list of codecs received in the Supported Codec List by removing codecs not supported at the IM-MGW, choose the Selected Codec for the BICC CS network from the codecs in the Available Codec List, and complete the mid-call codec negotiation procedure towards the preceding serving node according to clause 10.4.5 of ITU-T Q.1902.4 [30]. The MGCF should choose the Selected Codec for the BICC CS network in such a way as to avoid transcoding at the IM-MGW and minimize speech degradation, if possible, according to clause B.2.5. Otherwise the MGCF should choose the highest priority codec from the Available Codec List for the Selected Codec for the BICC CS network. If the MGCF receives an APM from the preceding serving node with an Action indicator set to "codec modification failure", then the MGCF may initiate a new SDP offer/answer exchange towards the IM CN subsystem in an attempt to recreate the bearer configuration in place before this codec negotiation procedure began. + +If the MGCF receives a 488 response or other failure response (e.g. 3xx-6xx) to the SDP offer, either it should reject the mid-call codec negotiation from the BICC CS network by sending an APM with an Action indicator set to "mid-call codec negotiation failure" towards the preceding serving node, or it should continue as if it received an SDP answer with no change in codec selected for the IM CN subsystem. If the MGCF sends an APM with an Action indicator set to "mid-call codec negotiation failure", it should continue the call with the bearer configuration in place before initiating this codec negotiation procedure. + +#### B.2.4.3 Receipt of codec modification request + +If the MGCF receives an APM from a BICC CS network that includes an Action indicator set to "modify codec" with no change in the selected codec, it shall act as a serving node terminating codec modification, according to clause 10.4.2 of ITU-T Q.1902.4 [30], without interworking the procedure with the IM CN subsystem. + +If the MGCF receives an APM from a BICC CS network that includes an Action indicator set to "modify codec" and the new selected codec in the message is different from the Selected Codec at the IM-MGW bearer interface to the BICC CS network, the MGCF either may act as a serving node terminating codec modification, according to clause 10.4.2 of ITU-T Q.1902.4 [30], without interworking the procedure with the IM CN subsystem, or may follow the procedures of clause B.2.5 to convert the new Available Codec List (with new priority order) from the APM into an SDP offer for transmission in an appropriate SIP message (e.g. re-INVITE request) towards the IM CN subsystem, according to RFC 3264 [36], deleting those codecs not supported at the IM-MGW. When generating the SDP offer, the MGCF should include all codec configurations for which it can provide transcoding in addition to those converted from the new Available Codec List. The MGCF shall include at least one AMR codec configuration in the SDP offer. + +If the MGCF sends a SIP message with an SDP offer towards the IM CN subsystem in response to receipt of a BICC codec modification request, then it shall delay responding to the BICC codec modification request until it receives a response to the SDP offer from the IM CN subsystem. When the MGCF receives either an SDP answer or a rejection of the SDP offer within the appropriate SIP message (e.g. 200 OK (INVITE)) from the IM CN subsystem, it shall decide whether to accept or reject the BICC codec modification procedure and complete the procedure for a BICC serving node terminating codec modification, according to clause 10.4.2 of ITU-T Q.1902.4 [30]. + +If the MGCF sends an APM with an Action indicator set to "codec modification failure" in response to receipt of a codec modification request, the preceding BICC serving node may retry the request with a mid-call codec negotiation using an APM including an Action indicator set to "mid-call negotiation" and a Supported Codec List with a new priority order encouraging selection of a new codec. + +### B.2.5 Codec parameter translation between BICC CS network and the IM CN subsystem + +The IM CN subsystem uses the Session Description Protocol (SDP, defined in IETF RFC 4566 [56]) to select and potentially re-negotiate the codec type and configuration and associated bearer format attributes to be used in the user plane. IETF RFC 3550 [51] defines the Real Time Protocol (RTP) for framing of all codecs in the user plane, IETF RFC 3551 [52] and IETF RFC 3555 [53] define the framing details for many of the ITU-T codecs, and IETF RFC 4867 [23] defines framing details for the AMR family of codecs. This clause will focus only on codec-specific SDP parameters]. The signalling plane of the IM CN subsystem uses SDP offer/answer procedures defined in IETF RFC 3264 [36] to select the desired codec type and configuration for the user plane from a prioritized list of codec types and configurations and to re-negotiate the user plane attributes as necessary. + +The bearer independent CS network uses the Single Codec and Codec List information elements of the Application Transport Mechanism (APM) defined in ITU-T Recommendation Q.765.5 [35] to negotiate (offer and select) and potentially re-negotiate the codec type and configuration and associated bearer format attributes to be used in the user plane. 3GPP TS 29.414 [25] and 3GPP TS 29.415 [26] define the IuFP framing protocol for all codecs in the user plane for both ATM and IP transport, and 3GPP TS 26.102 [50] provides the framing details for AMR and PCM family codecs. The Codec List information element of the APM comprises multiple instances of the Single Codec information element in priority order, as shown in figure 13 of ITU-T Recommendation Q.765.5 [35]. Figure 14 of ITU-T Recommendation Q.765.5 [35] defines the Single Codec information element. Clause 11.1.7.2 of ITU-T Recommendation Q.765.5 [35] defines the encoding of the Single Codec information element for the ITU-T codecs. 3GPP TS 26.103 [57] defines the encoding of the Single Codec information element for the 3GPP codecs, and table 7.11.3.1.3-2 of 3GPP TS 28.062 [58] defines the preferred configurations of the narrowband AMR codecs (Config-NB-Code) for interoperation with TFO. The signalling plane of the bearer independent CS network uses the APM to negotiate the desired codec type and configuration for the user plane from the prioritized list of codec types and to re-negotiate the user plane attributes as necessary. + +The following clauses define the translations between the SDP payload format parameters of the IM CN subsystem and the corresponding subfields of the Single Codec information element of the bearer independent CS network for certain 3GPP and ITU-T codecs. Following these translation rules will in many cases allow the IM-MGW to perform interworking between the framing protocols on the bearer interfaces to the BICC CS network and the IM CN subsystem without transcoding. Implementations may signal other codec types not listed herein or other codec configurations of + +codec types listed herein. Implementations may also choose to perform transcoding between codec configurations signalled separately for the bearer interfaces to the networks, if necessary, but voice quality may suffer. + +#### B.2.5.1 Codec parameters for 3GPP AMR-NB codecs + +Table B.1 shows the correspondence between the codec format parameters in the Single Codec information element (3GPP TS 26.103 [57]) and the SDP for the 3GPP narrowband AMR codecs (IETF RFC 4867 [23]). + +**Table B.1: Mapping between Single Codec subfields and SDP parameters for 3GPP AMR-NB codecs** + +| Single Codec information element | | SDP payload format parameters | | | +|----------------------------------|-----------------------------------------------------------------------------|-------------------------------|---------------|----------------------------------------------------------------------------------| +| Codec Identification | ACS, SCS, OM, MACS | Payload Type number | Encoding name | Other Parameters (NOTE 1) (NOTE 2) | +| FR_AMR or OHR_AMR or HR_AMR | OM=0 or Selected Codec Type | dynamic | AMR | mode-set=values corresponding to ACS (NOTE 3) | +| FR_AMR or OHR_AMR or HR_AMR | (OM=1 or OM not present) and (Supported Codec List or Available Codec List) | dynamic | AMR | mode-set=select from values corresponding to ACS, SCS and MACS (NOTE 3) | +| UMTS_AMR | OM=0 or Selected Codec Type | dynamic | AMR | mode-set=values corresponding to ACS | +| UMTS_AMR | (OM=1 or OM not present) and (Supported Codec List or Available Codec List) | dynamic | AMR | mode-set=select from values corresponding to ACS, SCS and MACS (NOTE 4) | +| UMTS_AMR_2 | OM=0 or Selected Codec Type | dynamic | AMR | mode-set=values corresponding to ACS (NOTE 5) | +| UMTS_AMR_2 | (OM=1 or OM not present) and (Supported Codec List or Available Codec List) | dynamic | AMR | mode-set=select from values corresponding to ACS, SCS and MACS (NOTE 3) (NOTE 5) | + +NOTE 1: Table 1 of IETF RFC 4867 [23] provides the correspondence between codec rates and AMR modes for use when generating the "mode-set" parameter. When all modes are selected for use, the "mode-set" parameter shall not be included in SDP. + +NOTE 2: SDP payload format configurations in this table with only one value in the "mode-set" parameter shall not include the "mode-change-period" and "mode-change-neighbor" parameters. + +NOTE 3: Payload types for FR\_AMR, OHR\_AMR and HR\_AMR with more than one value in the "mode-set" parameter shall include the "mode-change-period=2", "mode-change-capability=2" parameters and should include the "mode-change-neighbor=1" parameter. + +NOTE 4: IETF RFC 4867 [23] does not currently provide a mechanism to signal the SCS, MACS or OM parameters in SDP, nor does it distinguish between the different AMR-NB codec types. Each AMR-NB codec type in the Supported Codec List or the Available Codec List with OM=1 should be translated into a list of SDP payload formats in priority order, where each includes a "mode-set" parameter with a unique value derived from the ACS, SCS and MACS. Each "mode-set" should correspond to a codec configuration that is compatible with the given codec type according to the compatibility rules defined in clauses 11 and 12 of TS 28.062 [58]. + +NOTE 5: Payload types for UMTS\_AMR\_2 should include the "mode-change-period=2", "mode-change-capability=2" and "mode-change-neighbor=1" parameters, normally used for signalling GSM AMR codecs, to assure end-to-end interoperability with OoBTC and TFO. Its actual capabilities would otherwise be signalled without these parameters. + +##### Definitions: + +**Supported Codec List:** contains the offered Codec Types and Configuration-possibilities of the node initiating codec negotiation in BICC (see also 3GPP TS 23.153). The Supported Codec List is sent from the initiating node forward to the terminating node. The Supported Codec List corresponds to an SDP offer during codec negotiation. + +**Available Codec List:** contains the offered Codec Types and Configuration-possibilities of the contiguous portion of the connection between initiating and terminating BICC nodes, including all intermediate nodes through the BICC network(s). The Available Codec List is sent from the BICC node terminating codec negotiation backward to the initiating node. The Available Codec List corresponds to information sometimes available in a first-round SDP answer. The Available Codec List might not represent an end-to-end view of the available Codec Types and Configuration-possibilities when traversing both BICC and SIP networks. + +**Selected Codec Type:** is determined by the node terminating codec negotiation. It specifies exactly the Codec Type and one unique Codec Configuration for the call. The Selected Codec Type corresponds to the final SDP answer. + +When translating from a Single Codec information element to the equivalent SDP payload format parameters, where either OM=0 (in the Supported or Available Codec List) or the information element is the Selected Codec Type, the SDP shall include a single payload type and any associated parameters from the corresponding row in table B.1. When translating from a Single Codec information element to the equivalent SDP payload format parameters, where OM=1 in the Supported or Available Codec List, the SDP shall only include payload formats corresponding to Codec Configurations compatible with the offered ACS, SCS and MACS, according to table B.1. Since the number of compatible payload formats can be large, implementations should select a reasonable subset of the higher-priority payload formats for inclusion in the SDP. When translating a list of Single Codec information elements into SDP, duplicate payload types (matching on all parameters) shall be removed. + +The following guidelines shall apply when translating from an SDP payload format specification to a Single Codec information element: + +- If there is no "mode-set" parameter for a payload format in the SDP and the SDP is to be translated into a Supported or Available Codec List, then the corresponding Single Codec subfields shall be OM=1, MACS=8, all SCS modes offered, and ACS modes offered. Alternatively it is sufficient to specify only the Codec Type (see below) and omit the other parameters. +- If there is no "mode-set" parameter for a payload format in an SDP answer that is to be translated into a Selected Codec Type, then the corresponding Single Codec subfields shall be derived from the payload type in the SDP offer (to which the SDP answer was sent in response). +- If there is a "mode-set" parameter for a payload format in the SDP, then the corresponding Single Codec subfields shall be OM=0 and ACS modes selected according to the value of "mode-set". The SCS shall be set identical to the ACS and MACS shall be set to the number of modes in the ACS. If this "mode-set" does not represent a valid configuration for the Codec Type (determined by OoBTC procedures), then the payload format shall not be translated. +- If a payload format in an SDP offer that is to be translated into a Supported Codec List includes "mode-change-period=2" parameter or includes "mode-change-capability=2" parameter, then the Codec Identification value for the corresponding Single Codec shall be FR\_AMR. +- If a payload format in an SDP answer that is to be translated into a Selected Codec Type or Available Codec List includes "mode-change-period=2", then the Codec Identification value for the corresponding Single Codec shall be one of FR\_AMR, HR\_AMR, OHR\_AMR or UMTS\_AMR\_2, if offered in the Supported Codec List. +- If a payload format in an SDP offer that is to be translated into a Supported Codec List does not include "mode-change-period=2" parameter and does not include "mode-change-capability=2" parameter, then the Codec Identification value for the corresponding Single Codec shall be UMTS\_AMR. +- If a payload format in an SDP answer that is to be translated into a Selected Codec Type or Available Codec List does not include "mode-change-period=2" parameter and does not include "mode-change-capability=2" parameter, then the Codec Identification value for the corresponding Single Codec shall be one of UMTS\_AMR\_2, FR\_AMR, HR\_AMR, OHR\_AMR or UMTS\_AMR, if offered in the Supported Codec List. + +#### B.2.5.2 Codec parameters for 3GPP AMR-WB codecs + +Table B.2 shows the correspondence between the codec format parameters in the Single Codec information element (3GPP TS 26.103 [57]) and the SDP for the 3GPP wideband AMR codecs (IETF RFC 4867 [23]). + +**Table B.2: Mapping between Single Codec subfields and SDP parameters for 3GPP AMR-WB codecs** + +| Single Codec information element | | SDP payload format parameters | | | +|----------------------------------|----------------|-------------------------------|----------------------------|--------------------------------------------------------------------| +| Codec Identification | Config-WB-Code | Payload Type number | Encoding name | Other Parameters(NOTE 1) | +| FR_AMR-WB or
OHR_AMR-WB | 0 | dynamic | AMR-WB | mode-set=0,1,2 | +| OFR_AMR-WB or
UMTS_AMR-WB | 0 | dynamic | AMR-WB | mode-set=0,1,2
(NOTE 2) | +| OFR_AMR-WB or
UMTS_AMR-WB | 1 | dynamic
dynamic
dynamic | AMR-WB
AMR-WB
AMR-WB | mode-set=0,1,2
mode-set=0,1,2,8
mode-set=0,1,2,4
(NOTE 2) | +| OFR_AMR-WB or
UMTS_AMR-WB | 2 | dynamic | AMR-WB | mode-set=0,1,2,4
(NOTE 2) | +| OFR_AMR-WB or
UMTS_AMR-WB | 3 | dynamic
dynamic
dynamic | AMR-WB
AMR-WB
AMR-WB | mode-set=0,1,2,4
mode-set=0,1,2,8
mode-set=0,1,2
(NOTE 2) | +| OFR_AMR-WB or
UMTS_AMR-WB | 4 | dynamic | AMR-WB | mode-set=0,1,2,8
(NOTE 2) | +| OFR_AMR-WB or
UMTS_AMR-WB | 5 | dynamic
dynamic
dynamic | AMR-WB
AMR-WB
AMR-WB | mode-set=0,1,2,8
mode-set=0,1,2,4
mode-set=0,1,2
(NOTE 2) | + +NOTE 1: Payload types for FR\_AMR-WB, OHR\_AMR-WB and OFR\_AMR-WB shall include the "mode-change-period=2" and "mode-change-capability=2" parameters and should include the "mode-change-neighbor=1" parameter. + +NOTE 2: Payload types for UMTS\_AMR-WB should include the "mode-change-period=2", "mode-change-capability=2" and "mode-change-neighbor=1" parameters, normally used for signalling GSM AMR-WB codecs, to assure end-to-end interoperability with OoBTC and TFO. Its actual capabilities would otherwise be signalled without these parameters. + +When translating from a Single Codec information element to the equivalent SDP payload format parameters, the SDP shall include a distinct payload type and any associated parameters for each row in the table that matches the Config-WB-Code parameter. For example, OFR\_AMR-WB with Config-WB-Code=3 can generate three SDP payload types for AMR-WB, each including the "mode-change-period=2" parameter, the "mode-change-neighbor=1" parameter, and the "mode-set" parameter with value sets "0,1,2,4", "0,1,2,8", and "0,1,2", respectively. When translating a list of Single Codec information elements into SDP, duplicate payload types (matching on all parameters) shall be removed. + +The following guidelines shall apply when translating from one or more SDP payload format specifications to a Single Codec information element: + +- Payload formats that match except for different values of "mode-set" shall be represented with the fewest values of Config-WB-Code, while retaining the priority represented by the order of the payload formats in the SDP. For example, three SDP payload types for AMR-WB, each including the "mode-change-period=2" parameter, the "mode-change-neighbor=1" parameter, and the "mode-set" parameter with value sets "0,1,2,4", "0,1,2,8", and "0,1,2", respectively, will generate Config-WB-Code=3. +- If there is no "mode-set" parameter for a payload format in the SDP and the SDP is to be translated into a Supported or Available Codec List, then the corresponding Single Codec shall have a Config-WB-Code value of 1. +- If there is no "mode-set" parameter for a payload format in an SDP answer that is to be translated into a Selected Codec Type, then the corresponding Config-WB-Code value shall be derived from the payload type in the SDP offer (to which the SDP answer was sent in response). +- If a payload format in an SDP offer that is to be translated into a Supported Codec List includes "mode-change-period=2" parameter or includes "mode-change-capability=2" parameter, then the Codec Identification value for the corresponding Single Codec shall be OFR\_AMR-WB. + +- If a payload format in an SDP answer is to be translated into a Selected Codec Type or Available Codec List, then the Codec Identification value for the corresponding Single Codec shall be one of OFR\_AMR-WB, FR\_AMR-WB, OHR\_AMR-WB or UMTS\_AMR-WB, if offered in the Supported Codec List. +- If a payload format in an SDP offer that is to be translated into a Supported Codec List does not include "mode-change-period=2" parameter and does not include "mode-change-capability=2" parameter, then the payload format shall not be translated. + +#### B.2.5.3 Codec parameters for 3GPP non-AMR codecs + +Table B.3 shows the correspondence between the codec format parameters in the Single Codec information element (3GPP TS 26.103 [57]) and the SDP for the 3GPP non-AMR codecs (IETF RFC 4867 [23], IETF RFC 3551 [52], IETF RFC 3555 [53] and IETF RFC 5993 [114]). + +**Table B.3: Mapping between Single Codec subfields and SDP parameters for 3GPP non-AMR codecs** + +| Single Codec information element
Codec Identification | SDP payload format parameters | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|---------------|------------------| +| | Payload Type number | Encoding name | Other Parameters | +| GSM FR | 3 | GSM | | +| GSM HR | dynamic | GSM-HR-08 | | +| GSM EFR (NOTE 1) | dynamic | GSM-EFR | | +| GSM EFR (NOTE 2) | dynamic | AMR | mode-set=7 | +| TDMA EFR (NOTE 2) | dynamic | AMR | mode-set=4 | +| PDC EFR (NOTE 2) | dynamic | AMR | mode-set=3 | +| NOTE 1: This translation for GSM EFR (GSM-EFR) is preferred to the alternative (AMR mode-set=7) if it is supported by the IM-MGW.
NOTE 2: AMR DTX is not compatible with the DTX schemes for any of the codecs in this list. The IM-MGW may support these configurations without transcoding by providing interworking between the DTX procedures and frame encodings on the bearer interfaces to the BICC CS network and the IM CN subsystem. | | | | + +#### B.2.5.4 Codec parameters for ITU-T codecs + +Table B.4 shows the correspondence between the codec format parameters in the Single Codec information element (Clause 11.1.7 of ITU-T Q.765.5 [35]) and the SDP for the ITU-T codecs (Table 4 of RFC 3551 [52], and RFC 3555 [53]). + +**Table B.4: Mapping between Single Codec subfields and SDP parameters for ITU-T codecs** + +| Single Codec information element | | | SDP payload format parameters | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|-------------------------------------------------|------------------------------------------|------------------------------------------|-------------------------------------| +| Codec Type subfield | Codec Name | Codec Configuration subfield (dcba) | Payload Type number | Encoding name | Other Parameters | +| 00000001 | G.711 64 kbit/s A-law | N/A | 8 | PCMA | | +| 00000010 | G.711 64 kbit/s μ-law | N/A | 0 | PCMU | | +| 00000011 | G.711 56 kbit/s A-law | N/A | N/A | N/A | | +| 00000100 | G.711 56 kbit/s μ-law | N/A | N/A | N/A | | +| 00000101 | G.722 (SB-ADPCM) | N/A | 9 | G722 | | +| 00000110 | G.723.1 | N/A | 4 | G723 | annexa=no | +| 00000111 | G.723.1 Annex A (silence suppression) | N/A | 4 | G723 | | +| 00001000 | G.726 (ADPCM) | xxx1
xx1x
x1xx
1xxx | dynamic
dynamic
dynamic
dynamic | G726-16
G726-24
G726-32
G726-40 | | +| 00001001 | G.727 (Embedded ADPCM) | xxxx | N/A | N/A | | +| 00001010 | G.728 | 111
(subsets of defined rates not supported) | 15 | G728 | | +| 00001011 | G.729 (CS-ACELP) | xx1
x1x
1xx | dynamic
18
dynamic | G729D
G729
G729E | annexb=no
annexb=no
annexb=no | +| 00001100 | G.729 Annex B (silence suppression) | xx1
x1x
1xx | dynamic
18
dynamic | G729D
G729
G72"E" | | +| NOTE: An "x" in a bit position of the Codec Configuration subfield indicates a "don't care" value. The SDP payload description for each listed codec includes a clock rate of 8000 Hz. TS 26.102 [50] only describes the BICC CS network framing for the PCM codecs. | | | | | | + +When translating from a Single Codec information element to the equivalent SDP payload format parameters, the SDP shall include a distinct payload type and any associated parameters for each matching instance of the Codec Configuration subfield. For example, G.726 (ADPCM) with Codec Configuration subfield "0101" shall generate SDP payload types for G726-32 and G726-16. + +When translating from an SDP payload format specification to the Single Codec information element, each SDP payload type should be represented by one matching Single Codec information element. For example, SDP payload types for G729 and G729E may generate one Single Codec information element for "G.729 Annex B" with Codec Configuration subfield "110". The G729 and G729E codecs may alternately be represented by two Single Codec information elements for "G.729 Annex B" with Codec Configuration subfields "100" and "010", respectively, if it is necessary to indicate preference between them. + +#### B.2.5.5 Codec parameters for 3GPP EVS codec + +Table B.2.5.5.1 and table B.2.5.5.2 show the correspondence between the codec format parameters in the Single Codec information element (3GPP TS 26.103 [57]) and the SDP for the 3GPP EVS codec (3GPP TS 26.445 [147]). + +**Table B.2.5.5.1: Mapping from Single Codec subfields UMTS\_EVS (Config-EVS-Code / Config-EVS-Code 2) to SDP parameters for 3GPP EVS codec** + +| Single Codec information element | | SDP payload format parameters | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------|--------------------------------------|-------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Codec Type | Config-EVS-Code / Config-EVS-Code 2 (NOTE 2) | Payload Type number | Encoding name
clock rate
encoding parameters | Other Parameters
(NOTE 1) | +| UMTS_EVS | 0 | Dynamic | EVS
16000
1 | br=5.9-8
bw=nb-wb
mode-set=0
mode-change-period=2
[mode-change-capability=2]
mode-change-neighbor=1
[dtx-recv=1]
[dtx=1]
cmr=1
ch-aw-recv=-1 | +| UMTS_EVS | 1 | Dynamic | EVS
16000
1 | br=5.9-13.2
bw=nb-swb
mode-set=0, 1, 2
mode-change-period=2
[mode-change-capability=2]
mode-change-neighbor=1
[dtx-recv=1]
[dtx=1]
cmr=1
ch-aw-recv={-1;0} | +| UMTS_EVS | 2 | Dynamic | EVS
16000
1 | br=5.9-24.4
bw=nb-fb
mode-set=0, 1, 2
mode-change-period=2
[mode-change-capability=2]
mode-change-neighbor=1
[dtx-recv=1]
[dtx=1]
cmr=1
ch-aw-recv={-1;0} | +| UMTS_EVS | 3 (NOTE 3) | Dynamic | EVS
16000
1 | br=9.6-13.2
bw=swb
mode-set=0, 1, 2
mode-change-period=2
[mode-change-capability=2]
mode-change-neighbor=1
[dtx-recv=1]
[dtx=1]
cmr=1
ch-aw-recv={-1;0} | +| NOTE 1: Square brackets "[ ]" indicate that the enclosed parameters may be omitted. Curved brackets "{ }" indicate a list of alternative values, separated by ";".
NOTE 2: If both Config-EVS-Code and Config-EVS-Code 2 subfields are included in the Single Codec information element, the SDP includes a distinct payload and any associated parameter for each subfield.
NOTE 3: This value is not applicable to Config-EVS-Code 2 subfield. | | | | | + +When translating a list of Single Codec information elements into SDP, duplicate payload types (matching on all parameters) shall be removed. + +NOTE: the number of Codecs included in the BICC-Offer is limited to 8. It is therefore not always possible to include more than one EVS Single Codec information element in a BICC-Offer. The EVS Single Codec information element can contain up to 2 EVS configurations in a BICC-Offer. + +**Table B.2.5.5.2: Mapping from SDP parameters for 3GPP EVS to Single Codec subfields UMTS\_EVS (Config-EVS-Code / Config-EVS-Code 2)** + +| SDP payload format parameters | | | Single Codec Information Element | | +|-------------------------------|----------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|---------------------------------------------------------------------------------------------| +| Payload Type number | encoding name
clock rate
encoding parameters
(NOTE 1) | Other Parameters (NOTE 1) | Codec Type | Config-EVS-Code/
Config-EVS-Code 2
(NOTE 3) | +| Dynamic | EVS
16000
[1] | br=5.9[-br2]; br2 = {8; ... 128}
bw=nb[-bw2]; bw2 = {wb;swb;fb}
[dtx=1]
[mode-set={0; 0,1,2}]
[mode-change-period=2]
[mode-change-capability=2]
[mode-change-neighbor=1]
[cmr={0,1}] NOTE 2 | UMTS_EVS | 0 if no br2;
0 if br2=8;
1 if
br2=13.2;
2 if
br2=24.4;
2 if br2 >
24.4 | +| Dynamic | EVS
16000
[1] | br=9.6[-br2]; br2 = {13.2; ... 128}
bw=swb
[dtx=1]
[mode-set={0; 0,1,2}]
[mode-change-period=2]
[mode-change-capability=2]
[mode-change-neighbor=1]
[cmr={0,1}] NOTE 2 | UMTS_EVS | 3 (NOTE 4) | + +NOTE 1: Square brackets "[ ]" indicate that the enclosed parameters may be omitted. Curved brackets "{ }" indicate a list of alternative values, separated by ";". + +NOTE 2: This mapping also applies if a cmr parameter with a value "-1" is received in the SDP body and if the IM-MGW supports RTCP-APP-CMR message as described in subclause 8.1.1.3.5. + +NOTE 3: If the Single Codec Information Element is included in a Selected Codec (BICC), only Config-EVS-Code is included. + +NOTE 4: This value is not applicable to Config-EVS-Code 2 subfield. + +The IM-MGW can handle the call without transcoding only if the received SDP offer or SDP answer is compliant with one of the entries in table B.2.5.5.2. + +The following guidelines shall apply when translating from one or more SDP payload format specifications to a Single Codec information element: + +- Payload formats that match except for different values of "mode-set" shall be represented with the fewest values of Config-EVS-Code 1 and optionally Config-EVS-Code 2, while retaining the priority represented by the order of the payload formats in the SDP. + +## B.3 MGCF - IM-MGW interaction during interworking of codec negotiation + +### B.3.1 Basic IM CN subsystem originated session + +This clause shows an example of the interworking of codec negotiation between an IM CN subsystem and a BICC CS network during session establishment for an IM CN subsystem originated session. The example applies to BICC forward bearer establishment. Similar procedures apply to the other four versions of bearer establishment procedure applicable to the BICC CS network. The exchange of codec information is identical in all five cases, but there are differences in the sequence of operations associated with bearer establishment within the BICC CS network. + +#### B.3.1.1 BICC forward bearer establishment + +##### B.3.1.1.1 IM-MGW selection + +The MGCF shall select an IM-MGW for the bearer connection before it performs the CS network side bearer establishment. This may happen either before sending the IAM or after receiving the APM message (signal 3 or signal 4 + +in figure B.1). In the latter case, the IM-MGW selection may be based on a possibly received MGW-id from the succeeding node. + +##### B.3.1.1.2 CS network side bearer establishment + +The MGCF shall either select bearer characteristics or request the IM-MGW to select and provide the bearer characteristics for the CS network side bearer connection before sending the IAM. In the latter case the MGCF shall use the Prepare Bearer procedure, not shown in figure B.1, to request the IM-MGW to select the bearer characteristics. After the succeeding node has provided a bearer address and a binding reference in the APM, the MGCF shall use the Establish Bearer procedure to request the IM-MGW to establish a bearer towards the destination CS-MGW. The MGCF shall provide the IM-MGW with the bearer address, the binding reference and the bearer characteristics (signal 5 in figure B.1). + +##### B.3.1.1.3 IM CN subsystem side session establishment + +When the MGCF receives the Selected Codec from the succeeding serving node in the CS network (signal 4 in figure B.1) and selects a codec for use in the IM CN subsystem, the MGCF shall initiate the Reserve IMS Connection Point and Configure Remote Resources procedure (signal 7 and 8 in figure B.1). From the received SDP and selected configuration data the MGCF: + +- Shall send the appropriate remote codec(s), the remote UDP port and the remote IP address to the IM-MGW. The remote UDP port and IP address refer to the destination of user plane data sent towards the IM CN subsystem. The remote codec(s) are the codec(s) the IM-MGW may select for user plane data sent towards the IM CN subsystem. +- Shall indicate to the IM-MGW the appropriate local codec(s) and request a local IP address and UDP port. The local IP address and UDP port are used by the IM-MGW to receive user plane data from the IM CN subsystem. The local codec(s) are the codec(s) the IM-MGW may select to receive user plane data from the IM CN subsystem. +- If DTMF support together with speech support is required, the reserve value indicator shall be set to "true". + +The IM-MGW: + +- Shall reply to the MGCF with the selected local codec(s) and the selected remote codec(s) and the selected local UDP port and IP address. +- Shall reserve resources for those codec(s). + +The MGCF shall send the local codec(s), UDP port and IP address to the IMS in the Session Progress (signal 9 in figure B.1). + +##### B.3.1.1.4 Through-connection + +During the Prepare Bearer and Establish Bearer procedures, the MGCF shall either use the Change Through-Connection procedure to request the IM-MGW to backward through-connect the BICC terminations, or the MGCF shall use this procedure to both-way through-connect the BICC termination already on this stage (signal 5 in figure B.1). During the Reserve IMS Connection Point procedure: + +- if the MGCF has been identified a call as an "ICS call" as specified in clause 7.3.3.1.2.n the MGCF shall request the IM-MGW to suspend sending media towards the IMS side by setting the through-connection of the IM CN subsystem side termination to "not through-connected" using the Change IMS Through-Connection procedure (signal 7 in figure B.1); and +- otherwise the MGCF shall use the Change IMS Through-Connection procedure to request the IM-MGW to backward through-connect the IMS termination (signal 7 in figure B.1). + +When the MGCF receives the BICC:ANM answer indication, it shall request the IM-MGW to both-way through-connect the termination using the Change Through-Connection or Change IMS Through-Connection procedures (signal 20 in figure B.1), unless those terminations are already both-way through-connected. + +##### B.3.1.1.5 Codec handling + +The IM-MGW may include a speech transcoder based upon the speech coding information provided to each termination. + +##### B.3.1.1.6 Failure handling in MGCF + +If any procedure between the MGCF and the IM-MGW is not completed successfully the default action by the MGCF is to release the session, as described in clause 9.2.6. If the MGCF receives a Bearer Released procedure from the IM-MGW the default action by the MGCF is to release the session as described in clause 9.2.7. + +NOTE: As an implementation option the MGCF may also decide for example to only release the resources in the IM-MGW that caused the failure, possibly select a new IM-MGW for the connection and continue the call establishment using new resources in the selected IM-MGW but such handling is outside of the scope of the present document. + +##### B.3.1.1.7 Message sequence chart + +Figure B.1 shows the message sequence chart for the IM CN subsystem originating session with BICC forward bearer establishment where the selection of IM-MGW is done after receipt of the APM. The MGCF then requests the seizure of a CS network side bearer termination and the establishment of the bearer. When the MGCF receives an answer indication, it requests the IM-MGW to both-way through-connect the terminations. + + + +``` + +sequenceDiagram + participant Client + participant MGCF + participant IM-MGW + Note left of Client: Establish Bearer, Change Through-Connection = both + Note left of Client: Reserve IMS Connection Point and Configure Remote Resources, Change IMS Through-Connection = backward + Note right of IM-MGW: Bearer Establishment + Note right of IM-MGW: Change IMS Through-Connection = both + + Client->>MGCF: 1. SIP: INVITE [supported codec list 1] + MGCF-->>Client: 2. SIP: 100 Trying + MGCF->>IM-MGW: 3. BICC: IAM [supported codec list 2] + IM-MGW-->>MGCF: 4. BICC: APM [selected codec 2] + MGCF->>IM-MGW: 5. H.248: ADD.req [Context ID = ?, Termination ID=?] + IM-MGW-->>MGCF: 6. H.248: ADD.resp [Context ID = C1, Termination ID = T2] + MGCF->>IM-MGW: 7. H.248: ADD.req [Context ID = C1, Termination ID = ?] + IM-MGW-->>MGCF: 8. H.248: ADD.resp [Context ID = C1, Termination ID = T1] + MGCF-->>Client: 9. SIP: 183 [selected codec 1] + Client->>MGCF: 10. SIP: PRACK + MGCF-->>Client: 11. SIP: 200 OK (PRACK) + MGCF-->>Client: 12. SIP: UPDATE + MGCF->>IM-MGW: 14. BICC: COT + IM-MGW-->>MGCF: 15. BICC: ACM + MGCF-->>Client: 16. SIP: 180 Ringing + Client->>MGCF: 17. SIP: PRACK + MGCF-->>Client: 18. SIP: 200 OK (PRACK) + MGCF->>IM-MGW: 19. BICC: ANM + MGCF->>IM-MGW: 20. H.248: MOD.req [Context ID=C1, Termination ID = T1] + IM-MGW-->>MGCF: 21. H.248: MOD.resp [Context ID = C1, Termination ID = T1] + MGCF-->>Client: 22. SIP: 200 OK (INVITE) + Client->>MGCF: 23. SIP: ACK + + Note over MGCF, IM-MGW: CALL IN ACTIVE STATE + +``` + +The sequence diagram illustrates the interaction between a Client, MGCF, and IM-MGW for a Basic IM CN Subsystem originating session. The process involves SIP signaling for call setup and BICC/H.248 signaling for bearer establishment and resource configuration. The MGCF acts as a bridge between the SIP client and the IM-MGW. The IM-MGW performs bearer establishment and IMS connection point configuration. The diagram is divided into two main phases: initial setup and bearer establishment/modification. A 'CALL IN ACTIVE STATE' is indicated at the bottom, spanning from the first H.248 ADD.req to the final SIP ACK. + +Sequence diagram showing Basic IM CN Subsystem originating session, BICC forward bearer establishment between MGCF and IM-MGW. + +Figure B.1: Basic IM CN Subsystem originating session, BICC forward bearer establishment (message sequence chart) + +### B.3.2 Basic CS network originated session + +This clause shows an example of the interworking of codec negotiation between a BICC CS network and an IM CN subsystem during session establishment for a BICC CS network originated session. The example applies to BICC forward bearer establishment. Similar procedures apply to the other four versions of bearer establishment procedure applicable to the BICC CS network. The exchange of codec information is identical in all five cases, but there are differences in the sequence of operations associated with bearer establishment within the BICC CS network. + +#### B.3.2.1 BICC forward bearer establishment + +##### B.3.2.1.1 IM-MGW selection + +The MGCF shall select an IM-MGW for the bearer connection before it performs the IM CN subsystem session establishment or the CS network side bearer establishment. + +##### B.3.2.1.2 IM CN subsystem side termination reservation + +The MGCF shall derive from the codec negotiation procedure one or several appropriate local codec(s) the IM-MGW may use to receive user plane data from the IM CN subsystem. The MGCF shall use the Reserve IMS Connection Point procedure (signals 2 and 3 in figure B.2/1). Within this procedure, the MGCF shall indicate the local codec(s) and request a local IP address and UDP port from the IM-MGW. The local IP address and UDP port are used by the IM-MGW to receive user plane data from the IM CN subsystem. If DTMF support together with speech support is required, or if the resources for multiple speech codecs shall be reserved at this stage, the reserve value indicator shall be set to "true". + +The IM-MGW shall reply to the MGCF with the selected local codec(s) and the selected local IP address and UDP port. + +The MGCF shall send this information in the INVITE (signal 4 in figure B.2/1) to the IM CN subsystem. + +##### B.3.2.1.3 IM CN subsystem side session establishment + +The MGCF shall use the Configure IMS Resources procedure (signals 7 and 8 in figure B.2/1) to provide configuration data (derived from SDP received in signal 6 in figure B.2/1 and the codec negotiation procedure) to the IM-MGW as detailed below: + +- The MGCF shall indicate the remote IP address and UDP port, i.e. the destination IP address and UDP port for data sent in the user plane towards the IM CN subsystem, +- The MGCF shall indicate the remote codec(s), i.e. the speech codec(s) for data sent in the user plane towards the IM CN subsystem. +- The MGCF may indicate the local codec(s) and the local IP address and UDP port. The MGCF shall indicate the local codec(s) if a change is required. +- IF DTMF support together with speech support is required, the reserve value indicator shall be set to "true". + +The IM-MGW shall reply with the selected remote codec(s) and reserve resources for these codec(s). If local codec(s) were received, the IM-MGW shall also reply with the selected local codec(s) and reserve the corresponding resources. + +If the selected local codec(s) differ from the codec(s) received in the SDP of signal 6 in figure B.2/1, the MGCF shall send the local reserved codec(s), and the local IP address and UDP port in the PRACK (signal 9 in figure B.2/1) to the IMS. + +##### B.3.2.1.4 CS network side bearer establishment + +The MGCF shall request the IM-MGW to prepare for the CS network side bearer establishment using the Prepare Bearer procedure (signals 11 and 12 in figure B.2/1). Within this procedure, the MGCF shall request the IM-MGW to provide a bearer address, a binding reference and optionally notify when the bearer is established. The MGCF shall also provide the IM-MGW with the bearer characteristics determined by the codec negotiation procedure. After the IM-MGW has replied with the bearer address and the binding reference, the MGCF provides the APM message (signal 13 in figure B.2/1) to the preceding node. The MGCF may also provide the IM-MGW-id in the APM message. + +##### B.3.2.1.5 Called party alerting + +The MGCF shall request the IM-MGW to provide an awaiting answer indication (ringing tone) to the calling party using the Send Tone procedure (signals 21 and 22 in figure B.2/1), when the following condition is satisfied: + +- the MGCF receives the first 180 Ringing message + +##### B.3.2.1.6 Called party answer + +When the MGCF receives a 200 OK message (signal 23 in figure B.2/2), it shall request the IM-MGW to stop providing the ringing tone to the calling party using the Stop Tone procedure (signals 26 and 27 in figure B.2/2). + +##### B.3.2.1.7 Through-Connection + +During the Prepare Bearer procedure, the MGCF shall either use the Change Through-Connection procedure to request the IM-MGW to backward through-connect the BICC termination, or the MGCF shall use this procedure to both-way through-connect the BICC termination already on this stage (signals 11 and 12 in figure B.2/1). During the Reserve IMS Connection Point procedure, the MGCF shall use the Change IMS Through-Connection procedure to request the IM-MGW to backward through-connect the IMS termination (signals 2 and 3 in figure B.2/1). + +When the MGCF receives the SIP 200 OK(INVITE) (signal 23 in figure B.2/2), it requests the IM-MGW to both-way through-connect the terminations using the Change IMS Through-Connection or Change Through-Connection procedures (signals 28 and 29 in figure B.2/2), unless those terminations are already both-way through-connected. + +##### B.3.2.1.8 Codec handling + +The IM-MGW may include a speech transcoder based upon the speech coding information provided to each termination. + +##### B.3.2.1.9 Failure handling in MGCF + +If any procedure between the MGCF and the IM-MGW is not completed successfully, the default action by the MGCF is to release the session as described in clause 9.2.6. If the MGCF receives a Bearer Released procedure from the IM-MGW the default action by the MGCF is to release the session, as described in clause 9.2.7. + +NOTE: As an implementation option the MGCF may also decide for example to only release the resources in the IM-MGW that caused the failure, possibly select a new IM-MGW for the connection and continue the call establishment using new resources in the selected IM-MGW but such handling is outside of the scope of the present document. + +##### B.3.2.1.10 Message sequence chart + +Figures B.2/1 and B.2/2 show the message sequence chart for the CS network originating session with BICC forward bearer establishment. + + + +``` + +sequenceDiagram + participant IM-MGW + participant MGCF + Note left of IM-MGW: Configure IMS Resources + IM-MGW->>MGCF: 1. BICC: IAM [supported codec list 1] + MGCF-->>IM-MGW: 2. H.248: ADD.req [Context ID = ?, Termination ID=?] + Note right of MGCF: Reserve IMS Connection Point, Change IMS Through-Connection = backward + IM-MGW->>MGCF: 3. H.248: ADD.resp [Context ID = C1, Termination ID = T1] + MGCF->>External: 4. SIP: INVITE [supported codec list 2] + External-->>MGCF: 5. SIP: 100 Trying + MGCF-->>External: 6. SIP: 183 [available codec list 2] + IM-MGW->>MGCF: 7. H.248: MOD.req Context ID = C1, Termination ID = T1] + IM-MGW->>MGCF: 8. H.248: MOD.resp [Context ID = C1, Termination ID = T1 ] + MGCF-->>External: 9. SIP: PRACK [selected codec 2] + External-->>MGCF: 10. SIP :200 OK (PRACK) [selected codec 2] + IM-MGW->>MGCF: 11. H.248: ADD.req [Context ID = C1, Termination ID = ?] + Note right of MGCF: Prepare Bearer, Change Through-Connection= both + IM-MGW->>MGCF: 12. H.248: ADD.resp [Context ID = C1, Termination ID = T2] + IM-MGW->>External: 13. BICC: APM [selected codec 1, available codec list 1] + Note left of IM-MGW: Bearer Establishment + IM-MGW->>MGCF: 14. BICC: COT + MGCF-->>External: 15. SIP: UPDATE + External-->>MGCF: 16. SIP :200 OK (UPDATE) + MGCF-->>External: 17. SIP :180 Ringing + MGCF-->>External: 18. SIP: PRACK + External-->>MGCF: 19. SIP :200 OK (PRACK) + IM-MGW->>External: 20. BICC: ACM + IM-MGW->>MGCF: 21. H.248: MOD.req [Context ID = C1, Termination ID = T2] + Note right of MGCF: Send Tone + IM-MGW->>MGCF: 22. H.248: MOD.resp [Context ID = C1, Termination ID = T2] + +``` + +The sequence diagram illustrates the interaction between the IM-MGW and the MGCF for a Basic CS Network Originating Session. The process begins with the IM-MGW sending a BICC: IAM message to the MGCF. The MGCF responds with an H.248: ADD.req, and the IM-MGW replies with an H.248: ADD.resp. The MGCF then sends a SIP: INVITE to an external entity, which responds with a 100 Trying and a 183 (available codec list 2). The MGCF sends a H.248: MOD.req to the IM-MGW, which responds with an H.248: MOD.resp. The MGCF sends a SIP: PRACK to the external entity, which responds with a 200 OK (PRACK). The IM-MGW sends a H.248: ADD.req to the MGCF, which responds with an H.248: ADD.resp. The IM-MGW then sends a BICC: APM message to the external entity. The IM-MGW sends a BICC: COT message to the MGCF, which responds with a SIP: UPDATE, which is acknowledged by a 200 OK (UPDATE). The MGCF sends a SIP: 180 Ringing to the external entity, which responds with a SIP: PRACK, which is acknowledged by a 200 OK (PRACK). The IM-MGW sends a BICC: ACM message to the external entity. The IM-MGW sends a H.248: MOD.req to the MGCF, which responds with an H.248: MOD.resp. The MGCF sends a tone to the external entity. + +Sequence diagram showing Basic CS Network Originating Session, BICC forward bearer establishment between IM-MGW and MGCF. + +Figure B.2/1: Basic CS Network Originating Session, BICC forward bearer establishment (message sequence chart) + + + +The sequence diagram illustrates the interaction between an IM-MGW and an MGCF. The sequence of messages is as follows: + +- 23. **SIP**: 200 OK (INVITE) - Received by MGCF from an external source. +- 24. **H.248**: MOD.req [Context ID=C1, Termination ID = T2] - Sent from MGCF to IM-MGW. An annotation "Stop Tone" is present next to this message. +- 25. **H.248**: MOD.resp [Context ID = C1, Termination ID = T2] - Sent from IM-MGW to MGCF. +- 26. **H.248**: MOD.req [Context ID=C1, Termination ID = T1] - Sent from MGCF to IM-MGW. +- 27. **H.248**: MOD.resp [Context ID = C1, Termination ID = T1] - Sent from IM-MGW to MGCF. An annotation "Change IMS Through-Connection = both" is present next to this message. +- 28. **BICC**: ANM - Sent from MGCF to an external destination (indicated by a leftward arrow). +- 29. **SIP**: ACK - Sent from MGCF to an external destination (indicated by a rightward arrow). + +A horizontal double-headed arrow at the bottom of the diagram, spanning the time between steps 24 and 28, is labeled "CALL IN ACTIVE STATE". + +Sequence diagram showing message exchanges between IM-MGW and MGCF. The diagram includes steps 23 through 29, with annotations like 'Stop Tone' and 'Change IMS Through-Connection = both'. A bracket at the bottom indicates 'CALL IN ACTIVE STATE'. + +Figure B.2/2: Basic CS Network Originating Session, BICC forward bearer establishment (message sequence chart continued) + +### B.3.3 CS network initiated mid-call codec negotiation + +Figure B.3 shows the CS network initiated mid-call codec negotiation procedure interworking with the IM CN subsystem. When the MGCF selects the codecs for the CS network and the IM CN subsystem (after signal 3 in figure B.3), the MGCF shall modify the CS network termination and the IM CN subsystem termination on the IM-MGW to conform to the newly selected configuration data on the two interfaces. The MGCF may perform bearer operations (not shown) at the IM-MGW before interworking the initial codec modification request (signal 2 in figure B.3) to determine new connection information, if necessary, or to verify resource availability. + + + +``` +sequenceDiagram + participant IM-MGW + participant MGCF + Note left of IM-MGW: Configure IMS Resources + IM-MGW->>MGCF: 1. BICC: APM [supported codec list 1] + MGCF->>IM-MGW: 2. SIP: re-INVITE [supported codec list 2] + MGCF-->>IM-MGW: 3. SIP: 200 OK (INVITE) [selected codec 2] + Note left of IM-MGW: Modify Bearer Characteristics + IM-MGW->>MGCF: 4. H.248: MOD.req Context ID = C1, Termination ID = T1] + MGCF->>IM-MGW: 5. H.248: MOD.resp [Context ID = C1, Termination ID = T1 ] + IM-MGW->>MGCF: 6. H.248: MOD.req [Context ID = C1, Termination ID = T2] + MGCF->>IM-MGW: 7. H.248: MOD.resp [Context ID = C1, Termination ID = T2] + MGCF-->>IM-MGW: 8. SIP: ACK + IM-MGW->>MGCF: 9. BICC: APM [selected codec 1] + MGCF->>IM-MGW: 10. BICC: APM [action = successful codec modification] +``` + +The sequence diagram illustrates the interaction between the IM-MGW and the MGCF for mid-call codec negotiation. The process begins with the IM-MGW sending a BICC: APM message with a supported codec list to the MGCF. The MGCF responds with a SIP: re-INVITE containing a supported codec list. The MGCF then sends a SIP: 200 OK (INVITE) with the selected codec. The IM-MGW then sends an H.248: MOD.req for Context ID = C1, Termination ID = T1. The MGCF responds with an H.248: MOD.resp. The IM-MGW then sends an H.248: MOD.req for Context ID = C1, Termination ID = T2. The MGCF responds with an H.248: MOD.resp. The MGCF then sends a SIP: ACK. The IM-MGW sends a BICC: APM with the selected codec to the MGCF. Finally, the MGCF sends a BICC: APM with the action = successful codec modification to the IM-MGW. + +Sequence diagram for CS network initiated mid-call codec negotiation between IM-MGW and MGCF. + +Figure B.3: CS network initiated mid-call codec negotiation +(message sequence chart) + +### B.3.4 IM CN subsystem initiated mid-call codec negotiation + +Figure B.4 shows the IM CN subsystem initiated mid-call codec negotiation procedure interworking with a BICC CS network. When the MGCF selects the codecs for the CS network and the IM CN subsystem (after signal 3 in figure B.4), the MGCF shall modify the CS network termination and the IM CN subsystem termination on the IM-MGW to conform to the newly selected configuration data on the two interfaces. The MGCF may perform bearer operations (not shown) at the IM-MGW before interworking the initial codec modification request (signal 2 in figure B.3) to determine new connection information, if necessary, or to verify resource availability. The MGCF may also perform bearer operations (not shown) at the IM-MGW after sending the final APM (signal 8 in figure B.4) to modify transport bandwidth, if necessary. + + + +``` +sequenceDiagram + participant IM-MGW + participant MGCF + Note right of MGCF: 1. SIP: re-INVITE [supported codec list 1] + MGCF->>IM-MGW: 2. BICC: APM [supported codec list 2] + IM-MGW->>MGCF: 3. BICC: APM [supported codec list 2] + Note left of IM-MGW: Configure IMS Resources + MGCF->>IM-MGW: 4. H.248: MOD.req [Context ID = C1, Termination ID = T1] + IM-MGW->>MGCF: 5. H.248: MOD.resp [Context ID = C1, Termination ID = T1] + Note left of IM-MGW: Modify Bearer Characteristics + MGCF->>IM-MGW: 6. H.248: MOD.req [Context ID = C1, Termination ID = T2] + IM-MGW->>MGCF: 7. H.248: MOD.resp [Context ID = C1, Termination ID = T2] + IM-MGW->>MGCF: 8. BICC: APM [action = successful codec modification] + Note right of MGCF: 9. SIP: 200 OK (INVITE) [selected codec 1] + MGCF->>IM-MGW: 10. SIP: ACK +``` + +The sequence diagram illustrates the mid-call codec negotiation process. It begins with the MGCF sending a SIP re-INVITE message (1) to an external entity. The MGCF then sends a BICC APM message with a supported codec list (2) to the IM-MGW. The IM-MGW responds with its own supported codec list (3). Next, the MGCF initiates resource configuration for the IMS (4, 5) and bearer characteristics modification (6, 7) using H.248 messages. The IM-MGW confirms the successful modification with a BICC APM message (8). Finally, the MGCF sends a SIP 200 OK (INVITE) with the selected codec (9) and receives an ACK (10) from the external entity. + +Sequence diagram for IM CN subsystem initiated mid-call codec negotiation between IM-MGW and MGCF. + +Figure B.4: IM CN subsystem initiated mid-call codec negotiation +(message sequence chart) + +# --- Annex C (normative): Interworking of CPC parameter + +The CPC extension to tel-URI Parameter is defined in clause 7.2A.12 of 3GPP TS 24.229 [9]. The SIP "Accept-Language" header is defined in IETF RFC 3261 [19]. + +## C.1 Interworking SIP to ISUP + +Table C.1.1 shows the mapping of a "cpc" URI parameter received within tel URI or the userinfo part of SIP URI with user="phone" in a P-Asserted-Identity header in the initial INVITE request to the Calling party's category parameter in the ISUP IAM. When the "cpc" URI parameter value "operator" is received the I-MGCF shall use an Accept-Language header field to determine the value of the Calling party's category parameter. + +**Table C.1.1: Mapping of the CPC parameter to the ISUP Calling party's category parameter** + +| SIP Parameters | | ISUP Parameters | +|-----------------------------------------------------|-----------------|---------------------------------------------------------------------------| +| "cpc" URI parameter in P-Asserted-Identity (NOTE 2) | Accept-Language | Calling party's category | +| operator | fr | operator, language French | +| operator | en | operator, language English | +| operator | de | operator, language German | +| operator | ru | operator, language Russian | +| operator | es | operator, language Spanish | +| ordinary | | ordinary calling subscriber | +| test | | test call | +| payphone | | payphone | +| unknown | | calling party's category unknown at this time (national use) | +| mobile-hplmn | | mobile terminal located in the home PLMN | +| mobile-vplmn | | mobile terminal located in a visited PLMN | +| emergency | | emergency service call per ANSI Standard ATIS-1000113.2005 [117] (NOTE 1) | + +NOTE 1: This is a national/regional specific value. Interworking shall only occur when interconnecting with indicated national network. +NOTE 2: In case the "cpc" URI parameter is absent or contains values that are not mapped per this table then the ISUP shall contain the default CPC value "ordinary calling subscriber". + +In case the Accept-Language header field is not received or contains values that are not in this table then based on operator policy the Calling party's category parameter shall contain the CPC value "operator, language X" (where X is one of the following languages: French, English, German, Russian or Spanish) or national/regional specific value. + +## C.2 Interworking ISUP to SIP + +Table C.2.1 shows the mapping of a Calling party's category received in an ISUP IAM to a "cpc" URI parameter within tel URI or the userinfo part of SIP URI with user="phone" in the P-Asserted-Identity header. When the Calling party's category parameter value "operator, language x" is received the O-MGCF shall generate an Accept-Language header field with the value that corresponds to language x. + +**Table C.2.1: Mapping of the ISUP Calling party's category parameter to the CPC parameter** + +| ISUP Parameter | SIP Parameters | | +|---------------------------------------------------------------------------|--------------------------------------------|-----------------| +| calling party's category | "cpc" URI parameter in P-Asserted-Identity | Accept-Language | +| operator, language French | operator | fr | +| operator, language English | operator | en | +| operator, language German | operator | de | +| operator, language Russian | operator | ru | +| operator, language Spanish | operator | es | +| ordinary calling subscriber | ordinary | - | +| test call | test | | +| payphone | payphone | | +| calling party's category unknown at this time (national use) | unknown | | +| mobile terminal located in the home PLMN | mobile-hplmn | | +| mobile terminal located in a visited PLMN | mobile-vplmn | | +| emergency service call per ANSI Standard ATIS-1000113.2005 [117] (NOTE 1) | emergency | | + +NOTE 1: This is a national/regional specific value. Interworking shall only occur when interconnecting with indicated national network. + +NOTE 2: In case the calling party's category contains values that are not in this table then based on operator policy the "cpc" URI parameter may be omitted or may contain national/regional specific value. + +--- + +Annex D (informative): +Void + +# Annex E (normative): + +# Multimedia interworking between the IP Multimedia Core Network (CN) Subsystem (IMS) and Circuit Switched (CS) networks + +## E.1 Basic Multimedia calls interworking between the IMS and CS Networks scenarios + +The Interworking between Circuit switched multimedia telephony service, as described in 3GPP TS 26.110 [78] and 3GPP TS 26.111 [79], and packet switched multimedia services, as described in 3GPP TS 26.114 [104] is addressed. + +NOTE: Examples in the present Annex assume that the ITU-T H.263 [84] video codec is used at the CS side. However, in the present release of 3GPP TS 26.114 [104], the H.263 video codec is no longer recommended (although it has been mandated in previous releases). + +![Figure E.1.1.1 Overview of relevant CS-Domain Protocols (from TS 26.110 [78]). The diagram shows the flow of multimedia data and control signals between various components and the 3GPP Network. A dashed box labeled '3GPP TS 26.111' encloses the Video Codec, Speech Codec, Data Protocols, H.245, CCSRL, NSRP, and an Optional Receive Path Delay. The System Control is connected to the H.245 block and the Call Set-up block. The Call Set-up block is connected to the 3GPP Network. The 3GPP Network is connected to the Optional Multilink H.324 Annex H block, which is in turn connected to the Multiplex/Demultiplex block. The Multiplex/Demultiplex block is connected to the Video Codec, Speech Codec, and Data Protocols. The Video I/O Equipment is connected to the Video Codec. The Audio I/O Equipment is connected to the Speech Codec. The User Data Applications are connected to the Data Protocols.](6324b252294c0f5d4e34dad4a1202075_img.jpg) + +The diagram illustrates the architecture for multimedia interworking between the IP Multimedia Core Network (CN) Subsystem (IMS) and Circuit Switched (CS) networks. It shows the flow of data and control signals through various protocols and equipment. + +- Video I/O Equipment** is connected to a **Video Codec** (H.263, [MPEG-4, H.261 ...]). +- Audio I/O Equipment** is connected to a **Speech Codec** (3GPP-AMR, [G.723.1 ...]). +- User Data Applications** ([T.120, ...]) are connected to **Data Protocols** ([V.14, LAPM, ...]). +- The **System Control** is connected to **H.245** and the **Call Set-up** block. +- The **Call Set-up** block is connected to the **3GPP Network**. +- The **3GPP Network** is connected to the **Optional Multilink H.324 Annex H** block. +- The **Optional Multilink H.324 Annex H** block is connected to the **Multiplex/Demultiplex** block. +- The **Multiplex/Demultiplex** block (H.223, H.223 Annex A, H.223 Annex B, [H.223 Annex C, H.223 Annex D]) is connected to the **Video Codec**, **Speech Codec**, and **Data Protocols**. +- An **Optional Receive Path Delay** block is connected between the **Speech Codec** and the **Multiplex/Demultiplex** block. +- The **H.245** block is connected to **CCSRL**, which is connected to **NSRP[LAP M/V.42]**, which is connected to the **Multiplex/Demultiplex** block. +- All the above components (Video Codec, Speech Codec, Data Protocols, H.245, CCSRL, NSRP, and Optional Receive Path Delay) are enclosed in a dashed box labeled **3GPP TS 26.111**. + +Figure E.1.1.1 Overview of relevant CS-Domain Protocols (from TS 26.110 [78]). The diagram shows the flow of multimedia data and control signals between various components and the 3GPP Network. A dashed box labeled '3GPP TS 26.111' encloses the Video Codec, Speech Codec, Data Protocols, H.245, CCSRL, NSRP, and an Optional Receive Path Delay. The System Control is connected to the H.245 block and the Call Set-up block. The Call Set-up block is connected to the 3GPP Network. The 3GPP Network is connected to the Optional Multilink H.324 Annex H block, which is in turn connected to the Multiplex/Demultiplex block. The Multiplex/Demultiplex block is connected to the Video Codec, Speech Codec, and Data Protocols. The Video I/O Equipment is connected to the Video Codec. The Audio I/O Equipment is connected to the Speech Codec. The User Data Applications are connected to the Data Protocols. + +Figure E.1.1.1 Overview of relevant CS-Domain Protocols (from TS 26.110 [78]) + +## E.2 Control plane interworking + +### E.2.1 General + +In addition to the control plane Interworking between SIP and ISUP or BICC, interactions between the H.245 signalling at the CS side and SIP/SDP signalling are described. + +The establishment of the H.223 multiplexing protocol and the subsequent H.245 signalling procedures take place after the set-up and both-way through-connection of the CS bearer. + +### E.2.2 Functionalities required in the MGCF for multimedia calls support + +In addition to the control plane Interworking between SIP and ISUP or BICC, the MGCF needs to mediate interactions between the H.245 signalling or MONA (Media Oriented Negotiation Acceleration) procedures at the CS side and SIP/SDP signalling at the IMS side. The interactions between H.245 signalling or MONA procedures and SIP/SDP signalling should aim at avoiding media transcoding by selecting the same codec for the CS side and the PS side. + +NOTE: Detailed procedures for the mapping between SDP parameters and H.245 parameters are not specified in the present release. + +### E.2.3 IM CN subsystem originated session + +#### E.2.3.1 Preconditions used at IMS side + +##### E.2.3.1.1 Interactions between H.245 or MONA and SIP/SDP + +Figure E.2.3.1.1.1 shows examples of interactions between H.245 or MONA procedures and SIP/SDP for IM CN subsystem originated session. Most SIP and ISUP or BICC messages are intentionally omitted, since the SDP may be embedded in various SIP messages and since the in-band H.245 Messages are not tightly coupled with out-of-band ISUP or BICC messages. + +Figure E.2.3.1.1.1 assumes that the IMS peer uses the SIP precondition extension to indicate that preconditions have not yet been met. + + + +``` + +sequenceDiagram + participant IMS + participant IWNode as Interworking Node (MGCF+ IM MGW) + participant CSNetwork as CS Network + + Note left of IMS: 1. SIP: INVITE +[SDP offer: +m = H.263, MP4V-ES, H.261; +m= AMR, +Preconditions not met] + IMS->>IWNode: 1. SIP: INVITE + IWNode->>CSNetwork: 2. IAM + Note right of IWNode: 4. Bearer Establishment + IWNode->>CSNetwork: 5. ANM + Note right of IWNode: 6. H.223 Bearer Setup including possible MONA Channel establishment method negotiation + Note right of IWNode: Alternative to 7-9: MONA messages + Note right of IWNode: 7. H.245: Terminal Capability Set +[H.263, MP4V-ES; H.261 AMR] + IWNode->>CSNetwork: 7. H.245: Terminal Capability Set + Note right of IWNode: 8. H.245: Terminal Capability Set +[H.261, MP4V-ES; +AMR, G.711] + IWNode->>CSNetwork: 8. H.245: Terminal Capability Set + Note right of IWNode: 9. H.245: Open Logical Channels +[MP4V-ES, AMR] + IWNode->>CSNetwork: 9. H.245: Open Logical Channels + Note left of IWNode: 10. SIP: 200 OK (INVITE) + IWNode->>IMS: 10. SIP: 200 OK (INVITE) + Note left of IWNode: 11. SIP: +[SDP offer; m =: MP4V-ES; a= +3gpp_MaxRecvSDUSize 600; m= AMR ] + IWNode->>IMS: 11. SIP + Note left of IWNode: 12. SIP: +[SDP answer; m = MP4V-ES, m= AMR] + IMS->>IWNode: 12. SIP + Note right of IWNode: CALL IN ACTIVE STATE + IWNode->>CSNetwork: CALL IN ACTIVE STATE + +``` + +Sequence diagram showing interactions between IMS, Interworking Node (MGCF+ IM MGW), and CS Network for an IM CN subsystem originated session. The diagram illustrates the flow of SIP and H.245 messages, including INVITE, IAM, ANM, and various H.245 capability sets and channel negotiations. A 'CALL IN ACTIVE STATE' is indicated at the bottom. + +**Figure E.2.3.1.1.1: Interactions between H.245 and SIP/SDP for IM CN subsystem originated session +IMS peer indicates unmet local preconditions** + +Upon receipt of a SIP INVITE request containing speech and video Codecs (signal 1 in figure E.2.3.1.1.1) the Interworking Node (consisting of MGCF and IM-MGW) starts the call set-up for multimedia call at the CS side by sending an IAM requesting an UDI bearer (signal 2 in figure E.2.3.1.1.1). + +If SDP local preconditions, which are not yet met, are contained in signal 1, the Interworking node should immediately send an SDP answer to allow for the IMS-side bearer set-up to progress. The Interworking node selects codecs supported by the IM-MGW and likely to be supported within the CS network and communicates the selected codecs towards the IMS side within an SDP answer message (signal 3 in figure E.2.3.1.1.1). If these codecs are contained in the SDP offer, the Interworking Node should select the H.263 codec and may select other codec from the SDP offer in addition. The interworking node should include a b:AS bandwidth modifier with a bandwidth suitable for the selected codec(s), but not higher than 64kbit/s plus RTP/UDP/IP overhead, in the SDP answer to request that the peer does not send media with a higher bandwidth. + +The Interworking Node shall engage in an H.223 bearer setup (step 6 in figure E.2.3.1.1.1). If the interworking Node supports MONA (Media Oriented Negotiation Acceleration), it shall first attempt a MONA Channel establishment method negotiation according to Annex K of ITU-T Recommendation H.324 [81]. If the interworking node does not support MONA, it shall use the multiplexing level negotiation procedures of Annex C of H.324 [81]. If the + +Interworking Node supports MONA, but the remote peer does not do so, a fallback to the multiplexing level negotiation procedures of Annex C of H.324 [81] will occur. + +If both the Interworking Node and the remote CS terminal support MONA procedures, the MONA procedures as per ITU-T Recommendation H.324 Annex K [81] may be used to replace the H.245 negotiation (signals 7 - 9) as shown in figure E.2.3.1.1.1. + +If MONA procedures are not used, the following applies: + +- After the completion of the H.223 bearer setup at the CS side, the Interworking Node shall send a Terminal Capability Set message describing its own capabilities (signal 7 in figure E.2.3.1.1.1). Unless the Interworking Node supports transcoding, the Interworking Node shall only send codecs that have been offered at the IM CN subsystem side (as received in signal 1 in figure E.2.3.1.1.1) within this message. +- The Interworking Node will receive an H.245 Terminal Capability Set message describing the supported Codecs at the peer's side (signal 8 in figure E.2.3.1.1.1). +- The codecs contained both in the sent and received terminal capability set messages may be selected at the CS side. The final decision of the selected codecs at the CS side is taken when the H.245 open logical Channels message (signal 9 in figure E.2.3.1.1.1) is sent or received. The direction of this message is determined by the H.245 master-slave determination procedure. + +If the Interworking Node does not transcode, it should indicate the codecs selected within the H.245 negotiation (signal 11 in figure E.2.3.1.1.1) or within the MONA procedures and enable any media that have previously been put on hold at the IMS side after the completion of the H.245 negotiation or MONA procedures. + +The interworking node should include in step 11 of figure E.2.3.1.1.1 the SDP "a" attribute "3gpp\_MaxRecvSDUSize" indicating the maximum SDU size of the application data that can be transmitted to the receiver without segmentation, as specified in clause 12.2.4.6 of 3GPP TS 26.114 [104]. + +#### E.2.3.2 Preconditions not used at IMS side + +##### E.2.3.2.1 Interactions between H.245 or MONA and SIP/SDP + +Figure E.2.3.2.1.1 shows examples of interactions between H.245 or MONA procedures and SIP/SDP for IM CN subsystem originated session. Most SIP and ISUP or BICC messages are intentionally omitted, since the SDP may be embedded in various SIP messages and since the in-band H.245 Messages are not tightly coupled with out-of-band ISUP or BICC messages. + +Figure E.2.3.2.1.1 assumes that the IMS peer does not use the SIP precondition extension. + + + +``` + +sequenceDiagram + participant IMS + participant IWNode as Interworking Node (MGCF+ IM MGW) + participant CSNetwork as CS Network + + Note left of IMS: 1. SIP: INVITE +[SDP offer: +m = H.263, MP4V-ES, H.261; +m= AMR] + IMS->>IWNode: 1. SIP: INVITE + IWNode->>CSNetwork: 2. IAM + Note right of IWNode: 3. Bearer Establishment + CSNetwork->>IWNode: 4. ANM + Note right of IWNode: 5. H.223 Bearer Setup including possible +MONA Channel establishment method negotiation + Note right of IWNode: Alternative to 6-8: MONA messages + Note right of IWNode: 6. H.245: Terminal Capability Set +[MP4V-ES; AMR] + IWNode->>CSNetwork: 6. H.245: Terminal Capability Set + Note right of IWNode: 7. H.245: Terminal Capability Set +[H.261, MP4V-ES; +AMR, G.711] + IWNode->>CSNetwork: 7. H.245: Terminal Capability Set + Note right of IWNode: 8. H.245: Open Logical Channels +[MP4V-ES, AMR] + IWNode->>CSNetwork: 8. H.245: Open Logical Channels + Note left of IMS: 9. SIP: 200OK (INVITE) +[SDP answer: +m = MP4V-ES; a= 3gpp_MaxRecvSDUSize 600; +m= AMR] + IWNode->>IMS: 9. SIP: 200OK (INVITE) + Note bottom: CALL IN ACTIVE STATE + +``` + +Sequence diagram showing interactions between IMS, Interworking Node (MGCF+ IM MGW), and CS Network for an IM CN subsystem originated session. The diagram illustrates the flow of SIP and H.245 messages for call setup. + +**Figure E.2.3.2.1.1 Interactions between H.245 and SIP/SDP for IM CN subsystem originated session +IMS peer does not use SIP preconditions** + +Upon receipt of a SIP INVITE request containing speech and video Codecs (signal 1 in figure E.2.3.2.1.1) the Interworking Node (consisting of MGCF and IM-MGW) starts the call set-up for multimedia call at the CS side by sending an IAM requesting an UDI bearer (signal 2 in figure E.2.3.2.1.1). + +If no unmet local SDP preconditions are contained in signal 1, the Interworking node should defer sending an SDP answer until the H.245 negotiation or MONA procedures is/are completed. + +The Interworking Node shall engage in an H.223 bearer setup (step 5 in figure E.2.3.2.1.1). If the interworking Node supports MONA (Media Oriented Negotiation Acceleration), it shall first attempt a MONA Channel establishment method negotiation according to Annex K of ITU-T Recommendation H.324 [81]. If the interworking node does not support MONA, it shall use the multiplexing level negotiation procedures of Annex C of H.324 [81]. If the Interworking Node supports MONA, but the remote peer does not do so, a fallback to the multiplexing level negotiation procedures of Annex C of H.324 [81] will occur. + +If both the Interworking Node and the remote CS terminal support MONA procedures, the MONA procedures as per ITU-T Recommendation H.324 [81] Annex K may be used to replace the H.245 negotiation (signals 6 - 8) as shown in figure E.2.3.2.1.1. + +If MONA procedures are not used, the following applies: + +- After the completion of the H.223 bearer setup at the CS side, the Interworking Node shall send a Terminal Capability Set message describing its own capabilities (signal 6 in figure E.2.3.2.1.1). Unless the Interworking Node supports transcoding, the Interworking Node shall only send codecs that have been offered at the IM CN subsystem side (as received in signal 1 in figure E.2.3.2.1.1) within this message. +- The Interworking Node will receive an H.245 Terminal Capability Set message describing the supported Codecs at the peer's side (signal 7 in figure E.2.3.2.1.1). +- The codecs contained both in the sent and received terminal capability set message may be selected at the CS side. The final decision of the selected codecs at the CS side is taken when the H.245 open logical Channels message (signal 8 in figure E.2.3.2.1.1) is sent or received. The direction of this message is determined by the H.245 master-slave determination procedure. + +If the Interworking Node does not transcode, it shall send an SDP answer (signal 9 in figure E.2.3.2.1.1) indicating the codecs selected within the H.245 negotiation or within the MONA procedures after the completion of the H.245 negotiation or MONA procedures. The interworking node should include a b:AS bandwidth modifier with a bandwidth suitable for the selected codec(s), but not higher than 64kbit/s plus RTP/UDP/IP overhead, in the SDP answer to request that the peer does not send media with a higher bandwidth. + +The interworking node should include in Step 9 of figure E.2.3.2.1.1 the SDP "a" attribute "3gpp\_MaxRecvSDUSize" indicating the maximum SDU size of the application data that can be transmitted to the receiver without segmentation, as specified in clause 12.2.4.6 of 3GPP TS 26.114 [104]. + +#### E.2.3.3 Fallback to speech at session establishment + +If SCUDIF Fallback (see 3GPP TS 23.172 [121]) occurs on the CS side, the APM message contains a speech codec as "Selected Codec". The MGCF shall then disable the video "m-line" in the first SDP answer, if not yet sent, and complete the call-setup in the same way as for a normal speech call. If the SDP answer was already sent (precondition used), the MGCF shall update the SIP session to speech by sending a SIP UPDATE message with a relevant SDP. + +If in a non-SCUDIF case (ISUP or BICC without SCUDIF) the called CS terminal or network rejects the video call setup by sending a REL message to the MGCF, the MGCF releases the CS video call being established, re-establishes the CS call in a speech only mode sending a new IAM with a speech BCIE to the CS network and updates the IM CN leg codecs to a speech only codec. Then the call/session continues as in a speech only case. If the interworking node does not support the fallback, it shall release the session. + +### E.2.4 CS network originated session + +#### E.2.4.1 Interactions between SIP/SDP and H.245 or MONA + +##### E.2.4.1.1 Normal Call setup + +Figure E.2.4.1.1 shows examples of interactions between H.245 or MONA and SIP/SDP for the CS network originated session. Most SIP and ISUP or BICC messages are intentionally omitted, since the SDP may be embedded in various SIP messages and since the in-band H.245 Messages are not tightly coupled with out-of-band ISUP or BICC messages. + + + +``` + +sequenceDiagram + participant CS Network + participant Interworking Node (MGCF+ IM MGW) + participant IMS + + Note left of CS Network: 4. Bearer Establishment + Note left of CS Network: 7. H.223 Bearer Setup including possible MONA Channel establishment method negotiation + Note left of CS Network: Alternative to 8-12: MONA messages + + CS Network->>Interworking Node: 1. IAM + Interworking Node->>IMS: 2. SIP: INVITE [SDP offer; m = H.263, MP4V-ES; m= AMR] + IMS->>Interworking Node: 3. SIP: [SDP answer: m = H.263, MP4V-ES; m= AMR] + IMS->>Interworking Node: 5. SIP: 200OK (INVITE) + Interworking Node->>CS Network: 6. ANM + CS Network->>Interworking Node: 8. H.245: Terminal Capability Set [H.263, H.261 AMR, G.711] + Interworking Node->>IMS: 9. SIP: [SDP offer m = H.263, H.261; m= AMR] + IMS->>Interworking Node: 10. SIP: [SDP answer m = H.263, H.261; m= AMR] + Interworking Node->>CS Network: 11. H.245: Terminal Capability Set [H.263, H.261 AMR] + CS Network->>Interworking Node: 12. H.245: Open Logical Channels [H.263, AMR] + Interworking Node->>IMS: 13. SIP: [SDP offer m = H.263; a= 3gpp_MaxRecvSDUSize 600; m= AMR] + IMS->>Interworking Node: 14. SIP: [SDP answer m = H.263; m= AMR] + + Note right of CS Network: CALL IN ACTIVE STATE + +``` + +Sequence diagram showing interactions between CS Network, Interworking Node (MGCF+ IM MGW), and IMS for a CS network originated session. The diagram illustrates the flow of signaling messages (IAM, INVITE, ANM, H.245) and the establishment of bearers and logical channels. + +NOTE: Messages 3 and 5 may be combined in some scenarios. + +**Figure E.2.4.1.1: Interactions between H.245 and SIP/SDP for CS network originated session** + +Upon receipt of an IAM request for a multimedia Call (signal 1 in figure E.2.4.1.1) the Interworking Node (consisting of MGCF and IM-MGW) starts the call set-up for multimedia call at the IM CN subsystem side by sending an INVITE request (signal 2 in figure E.2.4.1.1). For the INVITE request, the Interworking Node selects codecs supported by the IM-MGW and likely to be supported within the CS Network. The Interworking Node should select the H.263 codec and may select other codec in addition. The interworking node should add a b:AS bandwidth modifier with a bandwidth suitable for the selected codec(s), but not higher than 64kbit/s plus RTP/UDP/IP overhead, in the SDP offer to request that the peer does not send media with a higher bandwidth. + +NOTE: The SDP coding to express that either a combined voice and video call, or a voice call, or a Clearmode codec, or some other data call is desired is not defined in the present release. + +The Interworking Node shall engage in an H.223 bearer setup (step 7 in figure E.2.4.1.1). If the interworking Node supports MONA (Media Oriented Negotiation Acceleration), it shall first attempt a MONA Channel establishment method negotiation according to Annex K of ITU-T Recommendation H.324 [81]. If the interworking node does not support MONA, it shall use the multiplexing level negotiation procedures of Annex C of H.324 [81]. If the Interworking Node supports MONA, but the remote peer does not do so, a fallback to the multiplexing level negotiation procedures of Annex C of H.324 [81] will occur. + +If both the Interworking Node and the remote CS terminal support MONA procedures, the MONA procedures as per ITU-T Recommendation H.324 [81] Annex K may be used to replace the H.245 negotiation (signals 8, 11 and 12) as shown in figure E.2.4.1.1. Furthermore, the SIP codec renegotiation in signals 9 and 10 is then also not applicable. + +If MONA procedures are not used, the following applies: + +- After the completion of the H.223 bearer setup at the CS side the Interworking Node will receive a H.245 Terminal Capability Set message describing the supported Codecs at the peer's side (signal 8 in figure E.2.4.1.1). +- Due to information received in a Terminal Capability Set message (signal 8 in figure E.2.4.1.1), the Interworking node may send an SDP offer at the IMS side (signal 9 in figure E.2.4.1.1), to offer additional codecs supported at the CS side but not contained in the first SDP offer (signal 2 in figure E.2.4.1.1), or to restrict the selected codecs at the IMS side to codecs which are available at the CS side. + +NOTE: It is not clear if the addition of codecs not included in previous SDP exchange has any impacts on IMS procedures, e.g. resource reservation related procedures. + +- The Interworking Node shall send a Terminal Capability Set message describing its own capabilities (signal 11 in figure E.2.4.1.1). Unless the Interworking Node supports transcoding, the Interworking node shall only send codecs that are also negotiated at the IM CN subsystem side (as received in signal 3 in figure E.2.4.1.1) within this message. The Interworking Node may defer sending the Terminal Capability Set message for some time to attempt to receive the peer's Terminal Capability set message and perform a possible IMS-side codec renegotiation. However, to avoid blocking situations, the Interworking Node shall not defer sending the Terminal Capability Set message for an excessive period of time. +- The codecs contained both in the sent and received Terminal Capability Set message may be selected at the CS side. The final decision of the selected codecs at the CS side is taken when the H.245 open logical Channels message (signal 12 in figure E.2.4.1.1) is sent or received. The direction of this message is determined by the H.245 master-slave determination procedure. + +If the Interworking Node does not transcode, it should indicate the codecs selected within the H.245 negotiation or within MONA procedures after the completion of the H.245 negotiation (signal 13 in figure E.2.4.1.1) or MONA procedures. + +The interworking node should include in Step 11 of figure E.2.4.1.1 the SDP "a" attribute "3gpp\_MaxRecvSDUSize" indicating the maximum SDU size of the application data that can be transmitted to the receiver without segmentation, as specified in clause 12.2.4.6 of 3GPP TS 26.114 [104]. + +##### E.2.4.1.2 Call setup if multimedia call can not be recognized in an unambiguous manner + +If the Interworking Node is not able to determine from the information within the IAM request whether a multimedia call or some other type of data call is requested (for example, if only TMR=UDI but no BC IE is contained in the IAM), the Interworking Node may also include appropriate codecs for other possible types of data call it supports in the INVITE request. If video and audio codecs are contained in the first SDP answer (signal 3), the Interworking Node should continue to attempt to set up a multimedia call as described in clause E.2.4.1.1. Otherwise, calls are set up as described in clause 7.2.3.2. + +##### E.2.4.1.3 Fallback to speech during call setup + +The called party can reject the video component in the SDP offer (signal 2 in figure E.2.4.1.1) by returning an SDP answer where the video related m-line is disabled (in signal 3 in figure E.2.4.1.1). + +If the MGCF receives an SDP answer during call setup where the video related m-line is disabled, it shall react as follows: + +- If the MGCF has received a SCUDIF call setup from the CS side (MuMe and speech codecs in IAM message, see 3GPP TS 23.172 [121]), the MGCF shall apply a SCUDIF fallback to speech on the CS side. The MGCF shall use a speech codec as Selected Codec and exclude the MuMe codec from the available codec list. +- If the MGCF has received a multimedia call setup without SCUDIF from the CS side, and the CS network supports CS fallback, the MGCF should terminate the call. + +NOTE 1: A call termination can trigger the caller's device to set up a new speech call. + +NOTE 2: Other procedures to maintain the CS call, e.g. disabling the video component on the CS side or providing a suitable video announcement and discarding received video media from the CS side, are FFS. + +#### E.2.4.2 CS originated - IM CN transit - CS terminated + +Figure E.2.4.2.1 describes ISUP and SIP/SDP interactions in a CS originated - IM CN transit - CS terminated case with a clear channel through the IM CN. An interworking node A receives an IAM message with a UDI H.223 & H.245 video call request (message 1). If the interworking node A supports both CS/IMS video interworking and a clearmode codec / clear channel, it may send both audio and video codecs and a clearmode codec and a UDI & H.223 & H.245 video indication in the INVITE message towards the IMS (message 2). The message is received by an interworking node B. The interworking node B sends an IAM message with a UDI & H.223 & H.245 video call request to the terminating CS network (message 3). If the interworking node B supports a clearmode codec / clear channel, it may send a SIP response with a clearmode codec towards the calling side to indicate that a clear channel can be established between the IMS interworking nodes (message 5). After the called party answers, the interworking node B sends a SIP 200 OK (Invite) with the clearmode codec to the calling node to indicate that a clear channel can be established (message 11). After the called party has answered the call, either MONA procedures are performed and the H.223 bearer is established or the H.223 bearer is established and the H.245 signalling is performed (step 14 in figure E.2.4.2.1). + +If the interworking node A does not support CS-IMS video interworking, but supports a clearmode codec / clear channel, it sends the INVITE message with a clearmode codec and UDI & H.223 & H.245 indication, but without a video codec, to allow the establishment of a CS video call through a clear channel. The interworking node A may also send an audio codec (alone or with a clearmode codec) to allow a fallback to speech. The interworking node B either accepts the clearmode and sends the corresponding IAM message with a UDI & H.223 & H.245 request (message 3) and SIP response with a clearmode codec (message 5 or 11), or accepts the speech mode and sends the corresponding IAM message with a speech request (message 3) and SIP response with a speech codec (messages 5, 11), or rejects the INVITE message if the requested codec(s) cannot be supported. + +The format of the indication of UDI & H.223 & H.245 from interworking node A to interworking node B is defined in Annex F "PSTN XML Scheme". UDI & H.223 & H.245 indication is conveyed in PSTN XML body within "BearerCapability" ("InformationTransferCapability" and "UserInfoLayerProtocol") and "LowLayerCompatibility" elements. Elements are defined in ETSI EN 300 403-1 (V1.3.2) [96] clause 4.5.5 and in ISUP transported in the ATP is in Q.761-Q.764 [4] clause 3.5. + + + +``` + +sequenceDiagram + participant CS_Network_L as CS Network + participant Node_A as Interworking node A (MGCF+ IM MGW) + participant IMS + participant Node_B as Interworking node B (MGCF+ IM MGW) + participant CS_Network_R as CS Network + + Note left of CS_Network_L: 4. TDM circuit reservation + CS_Network_L->>Node_A: 1. IAM [UDI, H.223 & H.245] + Node_A->>Node_B: 2. SIP: INVITE [m = H.263, m= AMR; m=clearmode] [PSTN XML body] + Node_B->>CS_Network_R: 3. IAM [UDI, H.223 & H.245] + Note right of CS_Network_R: 6. TDM circuit reservation + CS_Network_R->>Node_B: 7. ACM + Node_B->>Node_A: 5. SIP : Response [m=audio, a=clearmode] + Node_A->>CS_Network_L: 9. ACM + CS_Network_R->>Node_B: 10. ANM + Node_B->>Node_A: 8. SIP :180 Ringing + Node_A->>CS_Network_L: 12. ANM + Node_B->>Node_A: 11. SIP:200 OK(INVITE) + Node_A->>Node_B: 13. SIP: ACK + Note over Node_A, Node_B: 14. Clear channel. Either MONA messages + H.223 bearer setup or H.223 bearer setup and H.245 signaling between CS terminals + Note over Node_A, Node_B: CALL IN ACTIVE STATE + +``` + +Sequence diagram showing ISUP and SIP/SDP interactions in a CS originated - IM CN transit - CS terminated case with a clear channel through the IM CN. The diagram involves two CS Networks and an IMS. The sequence starts with an IAM message from the left CS Network to Interworking node A (MGCF+ IM MGW) in the IMS. Node A sends a SIP INVITE to Interworking node B (MGCF+ IM MGW) in the right CS Network. Node B sends an IAM message to the right CS Network. The right CS Network performs TDM circuit reservation and sends an ACM message to node B. Node B sends a SIP Response to node A. Node A performs TDM circuit reservation and sends an ACM message to the left CS Network. The right CS Network sends an ANM message to node B. Node B sends a SIP :200 OK(INVITE) to node A. Node A sends a SIP ACK to node B. Finally, a 'Clear channel' message is sent between the two nodes, and the call enters an active state. + +Figure E.2.4.2.1: ISUP and SIP/SDP interactions in a CS originated - IM CN transit - CS terminated case with a clear channel through the IM CN + +### E.2.5 Service change + +##### E.2.5.2.1 SCUDIF + +##### E.2.5.2.1.0 General + +SCUDIF is standardised in 3GPPP 3GPP TS 23.172 [121]. + +###### E.2.5.2.1.1 IM CN subsystem originated change + +###### E.2.5.2.1.1.1 Change from multimedia to speech + +Figure E.2.5.2.1.1.1.1 shows an IM CN subsystem originated modification from multimedia to speech during an ongoing session when the CS leg supports BICC. The interworking node receives an INVITE message that indicates the dropping of the video media from the session, message 1. The interworking node can only accept the dropping of the media component and sends a corresponding codec modification request to the BICC network, message 2, and acknowledges the INVITE with a 200 OK message. The BICC network indicates a successful codec modification, message 5. + +![Sequence diagram for Figure E.2.5.2.1.1.1.1: IM CN subsystem originated modification from multimedia to speech when the CS leg supports BICC. The diagram shows the IMS and CS Network interacting via an Interworking Node (MGCF+ IM MGW). The session starts with Audio + Video. The IMS sends a SIP: INVITE [m= AMR] to the Interworking Node. The Interworking Node sends a Modify Codec (Selected Codec=AMR) to the CS Network. The CS Network responds with a Successful Codec Modification. The Interworking Node sends a SIP: 200 OK (INVITE) [m= AMR] to the IMS. The IMS responds with a SIP: ACK. The session ends with Speech.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +sequenceDiagram + participant IMS + participant IN as Interworking Node (MGCF+ IM MGW) + participant CS_Network as CS Network + Note over IMS, CS_Network: Audio + Video + IMS->>IN: 1. SIP: INVITE [m= AMR] + IN->>CS_Network: 2. Modify Codec (Selected Codec=AMR) + CS_Network-->>IN: 5. Successful Codec Modification + IN-->>IMS: 3. SIP: 200 OK (INVITE) [m= AMR] + IMS->>IN: 4. SIP: ACK + Note over IMS, CS_Network: Speech + +``` + +Sequence diagram for Figure E.2.5.2.1.1.1.1: IM CN subsystem originated modification from multimedia to speech when the CS leg supports BICC. The diagram shows the IMS and CS Network interacting via an Interworking Node (MGCF+ IM MGW). The session starts with Audio + Video. The IMS sends a SIP: INVITE [m= AMR] to the Interworking Node. The Interworking Node sends a Modify Codec (Selected Codec=AMR) to the CS Network. The CS Network responds with a Successful Codec Modification. The Interworking Node sends a SIP: 200 OK (INVITE) [m= AMR] to the IMS. The IMS responds with a SIP: ACK. The session ends with Speech. + +**Figure E.2.5.2.1.1.1.1: IM CN subsystem originated modification from multimedia to speech when the CS leg supports BICC** + +NOTE: Handling of a case, where a codec is received in BICC negotiation but not included in the available codec list negotiated previously, is not defined in the present release. + +###### E.2.5.2.1.1.2 Change from speech to multimedia + +Figure E.2.5.2.1.1.2.1 shows an IM CN subsystem originated modification from speech to multimedia during an ongoing session when the CS leg supports BICC. The interworking node receives an INVITE message that offers the adding of a video media to the ongoing speech session, message 1. The interworking node accepts the offer and sends a corresponding codec modification request to the BICC network, message 2. The BICC network indicates a successful codec modification, message 3. The interworking node acknowledges the INVITE with a 200 OK message after the MONA or H.245 in-band negotiation in step 4 is completed. + +If the codec modification is not successful in the BICC network, the interworking node responds to the INVITE message with the speech codec in the 200 OK message to retain the speech only session. + +![Sequence diagram for Figure E.2.5.2.1.1.2.1: IM CN subsystem originated modification from speech to multimedia when the CS leg supports BICC. The diagram shows the IMS and CS Network interacting via an Interworking Node (MGCF+ IM MGW). The session starts with Speech. The IMS sends a SIP: INVITE [m= AMR; m=H.263] to the Interworking Node. The Interworking Node sends a Modify Codec (Selected Codec=MuMe) to the CS Network. The CS Network responds with a Successful Codec Modification. The Interworking Node then performs MONA or H.245 inband negotiation with the CS Network. After negotiation, the Interworking Node sends a SIP: 200 OK (INVITE) [m= AMR; m=H.263] to the IMS. The IMS responds with a SIP: ACK. The session ends with Audio + Video.](c036e2540a94b31357ceb0002f0cacab_img.jpg) + +``` + +sequenceDiagram + participant IMS + participant IN as Interworking Node (MGCF+ IM MGW) + participant CS_Network as CS Network + Note over IMS, CS_Network: Speech + IMS->>IN: 1. SIP: INVITE [m= AMR; m=H.263] + IN->>CS_Network: 2. Modify Codec (Selected Codec=MuMe) + CS_Network-->>IN: 3. Successful Codec Modification + Note over CS_Network: 4. MONA or H.245 inband negotiation + IN-->>IMS: 5. SIP: 200 OK (INVITE) [m= AMR; m=H.263] + IMS->>IN: 6. SIP: ACK + Note over IMS, CS_Network: Audio + Video + +``` + +Sequence diagram for Figure E.2.5.2.1.1.2.1: IM CN subsystem originated modification from speech to multimedia when the CS leg supports BICC. The diagram shows the IMS and CS Network interacting via an Interworking Node (MGCF+ IM MGW). The session starts with Speech. The IMS sends a SIP: INVITE [m= AMR; m=H.263] to the Interworking Node. The Interworking Node sends a Modify Codec (Selected Codec=MuMe) to the CS Network. The CS Network responds with a Successful Codec Modification. The Interworking Node then performs MONA or H.245 inband negotiation with the CS Network. After negotiation, the Interworking Node sends a SIP: 200 OK (INVITE) [m= AMR; m=H.263] to the IMS. The IMS responds with a SIP: ACK. The session ends with Audio + Video. + +**Figure E.2.5.2.1.1.2.1: IM CN subsystem originated modification from speech to multimedia when the CS leg supports BICC** + +##### E.2.5.2.1.2 CS network originated change + +###### E.2.5.2.1.2.1 Change from multimedia to speech + +Figure E.2.5.2.1.2.1.1 shows a CS network originated modification from multimedia to speech during an ongoing session when the CS leg supports BICC. The interworking node receives a Modify Codec message that indicates the dropping of the video media from the session, message 1. The interworking node accepts the dropping of the video component and sends a corresponding INVITE message to the IM CN subsystem, message 2, and acknowledges the code modification request to the BICC network, message 3. The IM CN subsystem acknowledges the INVITE dropping the video media with a 200 OK, message 4. The IM CN subsystem acknowledges the code modification request to the BICC network, message 5. + + + +The diagram illustrates the interaction between the IMS and the CS Network via an Interworking Node (MGCF+ IM MGW). The sequence of messages is as follows: + +- 1. **Modify Codec (Selected Codec=AMR)**: A message from the CS Network to the Interworking Node. +- 2. **SIP: INVITE [m= AMR]**: A message from the Interworking Node to the IMS. +- 3. **Successful Codec Modification**: A message from the Interworking Node to the CS Network. +- 4. **SIP: 200 OK (INVITE) [m= AMR]**: A message from the IMS to the Interworking Node. +- 5. **SIP: ACK**: A message from the Interworking Node to the IMS. + +At the top, a double-headed arrow labeled "Audio + Video" spans across the IMS and CS Network. At the bottom, a double-headed arrow labeled "Speech" spans across the IMS and CS Network, indicating the change in media type. + +Sequence diagram showing the modification from multimedia to speech. + +**Figure E.2.5.2.1.2.1.1: CS network originated modification from multimedia to speech when the CS leg supports BICC** + +###### E.2.5.2.1.2.2 Change from speech to multimedia + +Figure E.2.5.2.1.2.2.1 shows a CS network originated modification from speech to multimedia during an ongoing session when the CS leg supports BICC. The interworking node receives a Modify Codec message that indicates the adding of a video media to the ongoing speech session, message 1. The interworking node accepts the offer and sends a corresponding INVITE message to the IM CN subsystem, message 2. The IM CN subsystem acknowledges the INVITE adding the video media with a 200 OK, message 3, and acknowledges the code modification request to the BICC network, message 4. The interworking node may have to update the codecs, messages 7 and 8, after the MONA or H.245 in-band negotiation in step 6. + +If the IM CN subsystem does not accept the addition of the video media to the session, the interworking node rejects the modify codec request to retain the speech only session. + + + +``` + + sequenceDiagram + participant IMS + participant IW as Interworking Node (MGCF+ IM MGW) + participant CS as CS Network + Note over IMS, CS: Speech + CS->>IW: 1. Modify Codec (Selected Codec=MuMe) + IW->>IMS: 2. SIP: INVITE [m= AMR; m=H.263] + IMS->>IW: 3. SIP: 200 OK (INVITE) [m= AMR; m=H.263] + IW->>CS: 4. Successful Codec Modification + IMS->>IW: 5. SIP: ACK + CS->>IW: 6. MONA or H.245 inband negotiation + IW->>IMS: 7. SIP: INVITE [m= AMR; m=H.263] + IMS->>IW: 8. SIP: 200 OK (INVITE) [m= AMR; m=H.263] + Note over IMS, CS: Audio + Video + +``` + +Sequence diagram showing CS network originated modification from speech to multimedia. The diagram involves IMS, an Interworking Node (MGCF+ IM MGW), and CS Network. It shows SIP messages (INVITE, 200 OK, ACK) and media flow changes from Speech to Audio + Video. + +**Figure E.2.5.2.1.2.2.1: CS network originated modification from speech to multimedia when the CS leg supports BICC** + +#### E.2.5.2.2 Non-SCUDIF case (ISUP or BICC without SCUDIF) + +###### E.2.5.2.2.1 Change from multimedia to audio + +Figure E.2.5.2.2.1.1 shows an IM CN subsystem originated modification from multimedia to audio during an ongoing session when the CS leg supports ISUP or BICC without SCUDIF. The interworking node receives an INVITE message that indicates the dropping of the video media from the session, message 1. The interworking node can only accept the dropping of the media component and acknowledges the INVITE with a 200 OK, message 2. There are three alternative ways to handle the issue: + +- The video component stays on in the CS leg. The interworking node may use the video component to send an announcement to the CS terminal to inform the user about the change of the end-to-end connection to audio only. Refer to figure E.2.5.2.2.1.1. +- The interworking node initiates an H.245 in-band negotiation to close the video channel. +- The interworking node terminates the session. + + + +``` + + sequenceDiagram + participant IMS + participant IW as Interworking Node (MGCF+ IM MGW) + participant CS as CS Network + Note over IMS, CS: Audio + Video + IMS->>IW: 1. SIP: INVITE [m= AMR] + IW->>IMS: 2. SIP: 200 OK (INVITE) [m= AMR] + IMS->>IW: 3. SIP: ACK + IW->>CS: Video announcement + Note over IMS, IW: Audio + Note over IW, CS: Audio + Note over IW, CS: Video + +``` + +Sequence diagram showing IM CN subsystem originated modification from multimedia to speech. The diagram involves IMS, an Interworking Node (MGCF+ IM MGW), and CS Network. It shows SIP messages (INVITE, 200 OK, ACK) and media flow changes from Audio + Video to Audio, with a video announcement being sent. + +**Figure E.2.5.2.2.1.1: IM CN subsystem originated modification from multimedia to speech when the CS leg supports ISUP or BICC without SCUDIF** + +###### E.2.5.2.2.2 Change from speech to multimedia + +Figure E.2.5.2.2.2.1 shows an IM CN subsystem originated attempt to change from speech to multimedia during an ongoing session when the CS leg supports ISUP or BICC without SCUDIF. The interworking node receives an INVITE message that offers the adding of a video media to the ongoing speech session, message 1. The interworking node turns down the offer and responds to the INVITE message with the speech codec in the 200 OK message to retain the speech only session, message 2. + + + +The diagram illustrates a sequence of messages between the IMS and the CS Network, mediated by an Interworking Node (MGCF+ IM MGW). The sequence is as follows: + +- A horizontal double-headed arrow labeled "Speech" spans the top of the diagram, indicating an ongoing session. +- Message 1: A solid arrow points from the IMS to the Interworking Node, labeled "1. **SIP**: INVITE [m= AMR; m=H.263]". +- Message 2: A solid arrow points from the Interworking Node to the IMS, labeled "2. **SIP**: 200 OK (INVITE) [m= AMR]". +- Message 3: A solid arrow points from the IMS to the Interworking Node, labeled "3. **SIP**: ACK". +- A horizontal double-headed arrow labeled "Speech" spans the bottom of the diagram, indicating the session remains a speech-only session. + +Sequence diagram showing the interaction between IMS and CS Network via an Interworking Node (MGCF+ IM MGW) for a speech to multimedia modification attempt. + +**Figure E.2.5.2.2.2.1: IM CN subsystem originated modification from speech to multimedia when the CS leg supports ISUP or BICC without SCUDIF** + +### E.2.6 Call release + +#### E.2.6.1 Call release initiated from the IM CN subsystem side + +When the MGCF has received a BYE message (signal 1 in figure E.2.6.1.1) from the IM CN subsystem side, the MGCF may end the H.245 session between the IM-MGW and the CS network side (signal 3 in figure E.2.6.1.1) firstly. + +**NOTE:** A call release using only ISUP/BICC signalling at the CS side proceeds faster. H.324 terminals can handle situations where they do not receive H.245 call release signalling (see clause 7.5.2 of ITU-T Recommendation H.324 [81]), and this scenario also occurs e.g. at loss of coverage or when a node transporting H.223 transparently releases the call. + +The procedure of ending the H.245 session is defined in the clause E.4. After receiving the BYE message, the MGCF shall also send a 200 OK [BYE] message (signal 2 in figure E.2.6.1.1) towards the IM CN subsystem. + +After ending the H.245 session, the MGCF shall send a REL message (signal 4 in figure E.2.6.1.1) to the succeeding node. If the IM CN subsystem interworks with ISUP based CS network, the interworking node shall release the resources for the IMS side and the CS network side (signal 6 in figure E.2.6.1.1) after sending the REL message. If the IM CN subsystem interworks with BICC based CS network, the interworking node shall release the resources for the IMS side and the CS network side (signal 6 in figure E.2.6.1.1) upon receiving the RLC message (signal 5 in figure E.2.6.1.1) from the CS network side. The procedures of releasing the resources for the IMS side and the CS network side are specified in the present 3GPP TS in clause 7. + +Figure E.2.6.1.1 shows the message sequence chart for the multimedia call release initiated from the IM CN subsystem side. + +![Sequence diagram showing call release initiated from the IM CN subsystem side. The diagram involves three main entities: IMS, Interworking node (MGCF+ IM-MGW), and CS Network. The sequence of messages is: 1. IMS sends SIP: BYE to the Interworking node; 2. Interworking node responds with SIP: 200 OK [BYE]; 3. A dashed box indicates H.245 Signalling to end the H.245 session between the IM-MGW and the CS network side; 4. The Interworking node sends BICC or ISUP: REL to the CS Network; 5. A dashed arrow indicates BICC: RLC from the CS Network back to the Interworking node; 6. A box indicates the release of resources for both the IMS and CS network sides; 7. A dashed arrow indicates ISUP: RLC from the CS Network back to the Interworking node.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` +sequenceDiagram + participant IMS + participant IN as Interworking node (MGCF+ IM-MGW) + participant CS as CS Network + + Note right of IN: 3. H.245 Signalling to end the H.245 session between the IM-MGW and the CS network side + Note right of IN: 6. Release the resources for the IMS side and the CS network side + + IMS->>IN: 1. SIP: BYE + IN-->>IMS: 2. SIP: 200 OK [BYE] + Note right of IN: 3. H.245 Signalling to end the H.245 session between the IM-MGW and the CS network side + IN->>CS: 4. BICC or ISUP: REL + CS-->>IN: 5. BICC: RLC + Note right of IN: 6. Release the resources for the IMS side and the CS network side + CS-->>IN: 7. ISUP: RLC +``` + +Sequence diagram showing call release initiated from the IM CN subsystem side. The diagram involves three main entities: IMS, Interworking node (MGCF+ IM-MGW), and CS Network. The sequence of messages is: 1. IMS sends SIP: BYE to the Interworking node; 2. Interworking node responds with SIP: 200 OK [BYE]; 3. A dashed box indicates H.245 Signalling to end the H.245 session between the IM-MGW and the CS network side; 4. The Interworking node sends BICC or ISUP: REL to the CS Network; 5. A dashed arrow indicates BICC: RLC from the CS Network back to the Interworking node; 6. A box indicates the release of resources for both the IMS and CS network sides; 7. A dashed arrow indicates ISUP: RLC from the CS Network back to the Interworking node. + +NOTE: Signal 7 is omitted when IM CN subsystem interworks with BICC based CS network and Signal 5 is omitted when IM CN subsystem interworks with ISUP based CS network. + +**Figure E.2.6.1.1: Call release initiated from the IM CN subsystem side** + +#### E.2.6.2 Call release initiated from the CS network side + +If the CS network side initiates the call release, it possibly ends the H.245 session with explicit signalling (signal 1 in figure E.2.6.2.1). The CS network side sends a REL message (signal 2 in figure E.2.6.2.1) towards the IM CN subsystem. The procedure of ending the H.245 session is defined in the clause E.4. + +When the MGCF receives a REL message (signal 2 in figure E.2.6.2.1) from the preceding node, the MGCF sends a BYE message (signal 3 in figure E.2.6.2.1) to the IM CN subsystem. After receiving the REL message, the interworking node also releases the resources for the IMS side and the CS network side (signal 4 in figure E.2.6.2.1). The procedure of the releasing the resources for the IMS side and the CS network side are specified in the present 3GPP TS in clause 7. After completion of resource release, the MGCF sends a RLC message (signal 5 in figure E.2.6.2.1) towards the preceding node. Figure E.2.6.2.1 shows the message sequence chart for the multimedia call release initiated from the CS network side. + +![Sequence diagram for call release initiated from the CS network side. The diagram shows the interaction between the IMS and the CS Network via an Interworking node (MGCF+ IM-MGW). The sequence of messages is: 1. H.245 Signalling to end the H.245 session (optional) from the Interworking node to the CS Network; 2. BICC or ISUP: REL from the CS Network to the Interworking node; 3. SIP: BYE from the Interworking node to the IMS; 4. Release the resources for the IMS side and the CS network side (action within the Interworking node); 5. BICC or ISUP: RLC from the Interworking node to the CS Network; 6. SIP: 200 OK [BYE] from the IMS to the Interworking node.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` + +sequenceDiagram + participant IMS + participant IN as Interworking node (MGCF+ IM-MGW) + participant CS as CS Network + + Note right of IN: 1. H.245 Signalling to end the H.245 session (optional) + CS->>IN: 2. BICC or ISUP: REL + IN->>IMS: 3. SIP: BYE + Note right of IN: 4. Release the resources for the IMS side and the CS network side + IN->>CS: 5. BICC or ISUP: RLC + IMS->>IN: 6. SIP: 200 OK [BYE] + +``` + +Sequence diagram for call release initiated from the CS network side. The diagram shows the interaction between the IMS and the CS Network via an Interworking node (MGCF+ IM-MGW). The sequence of messages is: 1. H.245 Signalling to end the H.245 session (optional) from the Interworking node to the CS Network; 2. BICC or ISUP: REL from the CS Network to the Interworking node; 3. SIP: BYE from the Interworking node to the IMS; 4. Release the resources for the IMS side and the CS network side (action within the Interworking node); 5. BICC or ISUP: RLC from the Interworking node to the CS Network; 6. SIP: 200 OK [BYE] from the IMS to the Interworking node. + +Figure E.2.6.2.1: Call release initiated from the CS network side + +#### E.2.6.3 Call release initiated from the interworking node + +The interworking node may end the H.245 session between the IM-MGW and the CS network side (signal 1 in figure E.2.6.3.1) firstly. The procedure of ending the H.245 session is defined in the clause E.4. + +NOTE: A Call Release using only SIP and ISUP/BICC signalling may proceed faster. H.324 terminals can handle situations where they do not receive H.245 call release signalling (see clause 7.5.2 of ITU-T Recommendation H.324 [81]), and this scenario also occurs e.g. at loss of coverage or when a node transporting H.223 transparently releases the call. + +To release the call, the MGCF shall send a REL message (signal 2 in figure E.2.6.3.1) to the succeeding node on the CS network side. The MGCF shall also send a BYE message (signal 3 in figure E.2.6.3.1) to the IM CN subsystem side. + +If the IM CN subsystem interworks with ISUP based CS network, the interworking node shall release the resources for the IMS side and the CS network side (signal 5 in figure E.2.6.3.1) after sending the REL message. If the IM CN subsystem interworks with BICC based CS network, the interworking node shall release the resources for the IMS side and the CS network side upon receiving the RLC message (signal 4 in figure E.2.6.3.1) from the CS network side. The procedures of releasing the resources for the IMS side and the CS network side are specified in the present 3GPP TS in clause 7. Figure E.2.6.3.1 shows the message sequence chart for the multimedia call release initiated from the interworking node. + + + +The diagram illustrates the sequence of messages for call release initiated from the interworking node (MGCF+ IM-MGW) between the IMS and the CS Network. The sequence is as follows: + +- The Interworking node (MGCF+ IM-MGW) sends H.245 Signalling to end the H.245 session between the IM-MGW and the CS network side (indicated by a dashed box). +- The Interworking node (MGCF+ IM-MGW) sends **2. BICC or ISUP: REL** to the CS Network. +- The Interworking node (MGCF+ IM-MGW) sends **3. SIP: BYE** to the IMS. +- The CS Network sends **4. BICC: RLC** to the Interworking node (MGCF+ IM-MGW) (indicated by a dashed line). +- The Interworking node (MGCF+ IM-MGW) releases the resources for the IMS side and the CS network side (indicated by a solid box). +- The CS Network sends **6. ISUP: RLC** to the Interworking node (MGCF+ IM-MGW) (indicated by a dashed line). +- The IMS sends **7. SIP: 200 OK [BYE]** to the Interworking node (MGCF+ IM-MGW). + +Sequence diagram showing call release initiated from the interworking node between IMS and CS Network. + +NOTE: Signal 6 is omitted when IM CN subsystem interworks with BICC based CS network and Signal 4 is omitted when IM CN subsystem interworks with ISUP based CS network. + +Figure E.2.6.3.1: Call release initiated from the interworking node + +## E.3 User plane interworking + +### E.3.1 Functionalities required in the IM-MGW for multimedia calls support + +To enable a multimedia Interworking, the IM-MGW needs to support the reframing of the H.263 video codec and the AMR audio codec between CS transport and PS transport as a minimum. The IM-MGW may also support the reframing of other codecs and the transcoding of audio and/or video codecs. + +At the CS side, the IM-MGW needs to terminate the H.223 protocol and multiplex / de-multiplex audio, video and H.245 signalling. How H.245 related information (e.g. H.245 messages or extracted information) is communicated between the MGCF and the IM-MGW is described in clause E.4. + +## E.4 MGCF and IM-MGW interactions + +### E.4.1 Introduction + +This clause describes requirements for extensions to the Mn interface protocol in 3GPP TS 29.332 [15] needed to support the Interworking of multimedia calls. ITU-T Recommendation H.248.1 [2] is used at the Mn interface. + +The H.245 signalling shall be handled by the MGCF. Upon reception of the H.245 messages from the CS side at the IM-MGW, the IM-MGW shall forward those H.245 messages as binary data within H.248 messages over the Mn interface towards the MGCF. Upon reception of encapsulated binary H.245 messages within H.248 messages, the IM-MGW shall forward those H.245 messages towards the CS side. + +NOTE: Procedures to support MONA (see Annex K of ITU-T Recommendation H.324 [81]) over the Mn interface are not defined in the present Release. Furthermore, the signalling flows in clause E.2 may not show MONA related signalling in sufficient detail for MONA related Mn interface interactions. + +### E.4.2 Mn signalling interactions + +#### E.4.2.1 Introduction + +The following Clauses describe the Mn interface procedures triggered by H.245 signalling received in the IM-MGW and SIP and RTCP and BICC or ISUP signalling received in the MGCF. + +All message sequence charts in these Clauses are examples. + +#### E.4.2.2 H.248 Context Model + +The H.248 context model depicted in figure E.4.2.2.1 shall be applied for Multimedia Interworking. + + + +Diagram of the H.248 Context Model for Multimedia Interworking. It shows a large oval labeled 'Context C1' spanning across two domains: 'CS-Domain' on the left and 'IMS' on the right. Inside the oval, there are three terminations: 'Termination T1' (a small circle), 'Termination T2' (a small circle), and 'Termination T3' (a vertical oval). Stream 1 is a horizontal double-headed arrow between T1 and T2. Stream 2 is a horizontal double-headed arrow between T2 and T3. Stream 3 is a diagonal double-headed arrow between T2 and T3. Arrows point from T1 to the left (CS-Domain) and from T3 to the right (IMS). + +##### Termination: + +T1 CS-Domain (CS-Bearer (BS30) for H.245 control, Speech, Video) + +T2 Multiplexing (H.245 control, Speech, Video) + +T3 Video (own RTP-stream) + Speech (own RTP-stream) + +##### Stream: + +Stream1 (between T1 and T2) data (H.245 control, speech, Video) + +Stream2 (between T2 and T3) Video + +Stream3 (between T2 and T3) Speech + +**Figure E.4.2.2.1: H.248 Context Model for Multimedia Interworking** + +#### E.4.2.3 Transport of H.245 messages between the MGCF and IM-MGW + +##### E.4.2.3.1 General + +H.245 messages shall be transported between the IM-MGW and MGCF over the Mn interface using H.248 Events (from the IM-MGW towards the MGCF) and H.248 Signals (from the MGCF towards the IM-MGW). The Events/Signals shall contain the following information: + +- H.245 message (binary). + +##### E.4.2.3.2 Transport from MGCF to IM-MGW + + + +``` + +sequenceDiagram + participant MGCF + participant IM_MGW as IM MGW + Note right of MGCF: Signal H245 Message + MGCF->>IM_MGW: 1. H.248 MOD.req +[C=C1,T=T2 +signal=H245msgout +{h245mc=XXXX} ] + IM_MGW-->>MGCF: 2. H.248 MOD.resp + Note left of IM_MGW: 3. send H.245 message XXXX in H.223 stream + IM_MGW->>IM_MGW: 3. send H.245 message XXXX in H.223 stream + +``` + +Sequence diagram showing Mn signalling interactions for sending H.245 message from MGCF to IM-MGW. + +Figure E.4.2.3.2.1: Mn signalling interactions for sending H.245 message + +In Signal 1, the MGCF requests the IM-MGW to send an H.245 message to the CS side. To request the IM-MGW to send a H.245 message to the CS side, the MGCF shall send an H.248 signal to the IM-MGW with the complete H.245 message content. + +NOTE: In order for this command to succeed, Termination T1 towards the CS side needs to be configured. If a sending of an H.245 message and a removal of termination T1 is desired, the MGCF needs to apply signal 1 before removing T1. + +Upon reception of this signal, the IM-MGW shall send the encapsulated H.245 message within the H.248 signal, through the H.245 control channel to the CS side (signal 3). + +##### E.4.2.3.3 Transport from IM-MGW to MGCF + + + +``` + +sequenceDiagram + participant MGCF + participant IM_MGW as IM MGW + Note right of MGCF: Add Multiplex Termination + MGCF->>IM_MGW: 1. H.248 ADD.req +[C=C1,T=? ... ,Event=H245msgin] + IM_MGW-->>MGCF: 2. H.248 ADD.resp + Note left of IM_MGW: 3. receive H.245 message XXXX in H.223 + IM_MGW->>IM_MGW: 3. receive H.245 message XXXX in H.223 + Note right of MGCF: Notify H245 Message + IM_MGW->>MGCF: 4. H.248 : Notify.req +[C=C1,T=T2 +Event=H245msgin +{h245mc=XXXX}] + MGCF-->>IM_MGW: 5. H.248 : Notify.resp + +``` + +Sequence diagram showing Mn signalling interactions for receiving H.245 message from IM-MGW to MGCF. + +Figure E.4.2.3.3.1: Mn signalling interactions for receiving H.245 message + +In signal 1, the MGCF requests the IM-MGW to detect received H.245 message from the CS side and forward them to the MGCF. To request the IM-MGW to detect and forward a H.245 message to the CS side, the MGCF shall send a suitable H.248 event to the IM-MGW. The event may be indicated through an H.248 ADD command. + +In signal 3, the IM-MGW receives an H.245 message from the CS side. Upon reception of an H.245 message from the CS side, the IM-MGW shall de-multiplex the H.245 message from the H.223 stream and forward the H.245 message to the MGCF within an H.248 Notify command (signal 4). + +#### E.4.2.4 Call establishment procedure + +The following information shall be provided from the MGCF towards the IM-MGW: + +- Properties to start H.223 Negotiation. +- Request for events for Notification of H.245 message received by the IM-MGW. +- Signals to provide H.245 messages that the IM-MGW shall send towards the CS side. + +- Properties to provide incoming and outgoing H.223 multiplex table. +- Properties to provide H.223 logical channel parameters. +- Property to provide remote H.223 capabilities. + +The Highest Multiplexing Level shall be predefined in the IM-MGW. + + + +Sequence diagram illustrating Mn signalling interactions for H.245 termination at the MGCF. The diagram shows interactions between the IM MGW and the MGCF, with a Bearer Establishment box indicating a side interaction. + +The sequence of messages is as follows: + +1. H.248: ADD.req [C=?, T=?, stream=1] (MGCF to IM MGW) +2. H.248: ADD.resp [C=C1, T=T1] (IM MGW to MGCF) - *Prepare Bearer or Establish Bearer or Reserve TDM Circuit* +3. H.248: ADD.req [C=C1, T=?, stream=2{Codec=H.263}, stream=3{Codec=AMR}] (MGCF to IM MGW) +4. H.248: ADD.resp [C=C1, T=T3] (IM MGW to MGCF) - *Reserve IMS Connection Point or Reserve IMS Connection Point and Configure Remote Resources* +5. Bearer Establishment (Internal to CS) +6. H.248: ADD.req [C=C1, T=?, Mux=H223 T1, LocalControl{muxlv=2} Event=H245msgin] (MGCF to IM MGW) +7. H.248: ADD.resp [C=C1, T=T2] (IM MGW to MGCF) - *Add Multiplex Termination* +8. H.223: Multiplexing Level Negotiation [level=2] (CS to IM MGW) +9. H.245: Terminal Capability Set, [AMR,MP4V-ES,H263] Master-Slave Determination (IM MGW to MGCF) +10. H.245: Terminal Capability Set Ack, Master-Slave Determination Ack (MGCF to IM MGW) +11. H.245: Terminal Capability Set, [H.261,H.263,AMR] Master-Slave Determination (IM MGW to MGCF) +12. H.245: Terminal Capability Set Ack, Master-Slave Determination Ack (MGCF to IM MGW) +13. H.245: Open Logical Channel [H245 logical Channel = LC1] (IM MGW to MGCF) +14. H.245: Open Logical Channel Ack (MGCF to IM MGW) +15. H.245: Open Logical Channel [H245 logical Channel = LC2] (IM MGW to MGCF) +16. H.245: Open Logical Channel Ack (MGCF to IM MGW) +17. H.245: Multiplex Entry Send (IM MGW to MGCF) +18. H.245: Multiplex Entry Send Ack (MGCF to IM MGW) +19. H.245: Multiplex Entry Send (IM MGW to MGCF) +20. H.245: Multiplex Entry Send Ack (MGCF to IM MGW) +21. H.248: MOD.req [C=C1, T=T2, Stream=1{LocalCont{h223capr,muxtbl\_in,muxtbl\_out}}, stream=2{LCN=LC1, Codec=H263}, stream=3{LCN=LC2, Codec=AMR}] (MGCF to IM MGW) +22. H.248: MOD.resp (IM MGW to MGCF) - *Configure Multiplex Termination* +23. H.248: MOD.req [C=C1, T=T3, stream=2{Codec=H263}, stream=3{Codec=AMR}] (MGCF to IM MGW) +24. H.248: MOD.resp [C=C1, T=T3] (IM MGW to MGCF) - *Configure IMS Ressources* + +Sequence diagram showing Mn signalling interactions for H.245 termination at the MGCF. The diagram involves three entities: IM MGW, MGCF, and CS (implied by the Bearer Establishment box). The sequence of messages is as follows: 1. H.248 ADD.req from MGCF to IM MGW; 2. H.248 ADD.resp from IM MGW to MGCF; 3. H.248 ADD.req from MGCF to IM MGW; 4. H.248 ADD.resp from IM MGW to MGCF; 5. Bearer Establishment (internal to CS); 6. H.248 ADD.req from MGCF to IM MGW; 7. H.248 ADD.resp from IM MGW to MGCF; 8. H.223 Multiplexing Level Negotiation between CS and IM MGW; 9. H.245 Terminal Capability Set from IM MGW to MGCF; 10. H.245 Terminal Capability Set Ack from MGCF to IM MGW; 11. H.245 Terminal Capability Set from IM MGW to MGCF; 12. H.245 Terminal Capability Set Ack from MGCF to IM MGW; 13. H.245 Open Logical Channel from IM MGW to MGCF; 14. H.245 Open Logical Channel Ack from MGCF to IM MGW; 15. H.245 Open Logical Channel from IM MGW to MGCF; 16. H.245 Open Logical Channel Ack from MGCF to IM MGW; 17. H.245 Multiplex Entry Send from IM MGW to MGCF; 18. H.245 Multiplex Entry Send Ack from MGCF to IM MGW; 19. H.245 Multiplex Entry Send from IM MGW to MGCF; 20. H.245 Multiplex Entry Send Ack from MGCF to IM MGW; 21. H.248 MOD.req from MGCF to IM MGW; 22. H.248 MOD.resp from IM MGW to MGCF; 23. H.248 MOD.req from MGCF to IM MGW; 24. H.248 MOD.resp from IM MGW to MGCF. Annotations on the right describe the actions performed by the MGCF at each step. + +NOTE 1: All H.245 messages (from Signal 9 to Signal 18) are transported through the IM-MGW between the MGCF and the CS side, using the procedures described in clause E.4.2.3 + +NOTE 2: Signals 21 and 22 are omitted if the same codec information has already been provisioned in signal 3. + +**Figure E.4.2.4.1: Mn signalling interactions for H.245 termination at the MGCF** + +The MGCF shall request terminations towards the CS network (Signal 1 and 2) and towards the IMS (Signal 3 and 4). For the terminations towards the IMS, the MGCF provides an estimate about the applicable codecs in the required information elements "Local IMS Resources" (for both "Reserve IMS Connection Point" procedure and "Reserve IMS + +Connection Point and Configure Remote Resources" procedure) and possibly "Remote IMS Resources" (only for "Reserve IMS Connection Point and Configure Remote Resources" procedure). + +The MGCF shall request that the H.223 stream is (de-)multiplexed at the MUX termination T2, and that the H.245 control in H.223 Logical channel 0 is separated (signal 6). Furthermore, the MGCF shall request that the H.223 negotiation is started, and shall request to be notified about all H.245 messages received by the IM-MGW. + +The IM-MGW shall start the H.223 Multiplexing Level Negotiation after receipt of the corresponding request from the MGCF and CS bearer establishment (Signal 8). + +Upon reception of a H.245 Terminal Capability Set message (Signal 9), the MGCF sends a H.245 Acknowledgment message (Signal 10). + +The MGCF shall know the H.324 related capabilities of the IM-MGW before starting the H.245 capability negotiation with the CS side, e.g. through configuration. The H.245 Terminal Capability Set message sent by the MGCF (Signal 11) should include the codecs which are supported by both the IMS side and the IM-MGW, and the codecs which could be transcoded by the IM-MGW from the codecs supported by the IMS side. + +The MGCF may defer sending the Terminal Capability Set message (Signal 11) for some time to wait for codec information from the CS peer's Terminal Capability Set message and perform a possible IMS-side codec re-negotiation. To avoid blocking situations, the MGCF shall not defer sending the signal for an excessive period of time. + +To avoid the CS side selecting the codecs that need to be transcoded at the IM-MGW, the MGCF should aim to be the master in the H.245 master-slave determination procedure (Signals 9 to 12). The MGCF shall set the Terminal Type parameter as a number larger than 128 in the H.245 Master Slave Determination message. The H.245 master-slave determination procedure could be combined with the messages used for the H.245 capability exchange. + +The codecs contained both in the sent and received terminal capability set message may be selected at the CS side. The final decision of the selected codecs at the CS side is taken with the H.245 open logical channel procedure (Signals 13 to 16). + +After the completion of the H.245 multiplex table exchange procedure (Signals 17 to 20), the MGCF shall configure the multiplexing termination T2 by indicating to the IM-MGW the contents of the incoming and outgoing multiplex tables (Signal 21). + +If codec information needs to be changed compared to what has been provisioned in signal 3, the MGCF shall also configure T3 with the appropriate video and/or speech codec(s) (signal 23). + +The call is in the active state. + +#### E.4.2.5 Handling of H.245 indication message + +##### E.4.2.5.1 Overview + +The MGCF shall support the following H.245 indication messages: Function Not Understood Indication / Function Not Supported Indication, Jitter Indication. The MGCF may support the H.245 User Input Indication message. All these H.245 messages are conveyed between the MGCF and the CS side through the IM-MGW, as described in clause E.4.2.3. + +##### E.4.2.5.2 Function Not Understood / Function Not Supported message + +This indication message is used to return requests, responses and commands that are not understood back to the transmitter. + +If the MGCF receives a Function Not Understood or Function Not Supported message from the CS side, the MGCF may choose to attempt simpler H.245 interaction than the previous H.245 interaction that caused this indication. If this is not possible, the MGCF may release the call. + +If the MGCF receives a H.245 request, response or command that can not be understood, the MGCF shall send H.245 Function Not Supported indication message to the CS side. + +##### E.4.2.5.3 User Input Indication message + +The User-Input-Indication message is used e.g. to transport the in-band DTMF information in the H.324 system. + +The MGCF and IM-MGW may support transporting the DTMF information both from the CS side to the IMS side, and from the IMS side to the CS side. + +Upon Receipt of a H.245 User-Input-Indication message, the MGCF may apply the procedures in clause 9.2.8.3 to request the IM-MGW to send corresponding RTP telephone-event(s) towards the IMS side. + +Upon receipt of RTP telephone events from the IMS, the MGCF will be notified by the IM-MGW using the procedures in clause 9.2.8.1, if the MGCF has previously configured the IM-MGW as also described in this subclause. Upon receipt of the notification, the MGCF may send a H.245 User-Input-Indication message to the CS side. + +#### E.4.2.6 Handling of H.245 Command message + +##### E.4.2.6.1 Overview + +The MGCF shall support the End Session command message. The MGCF may support the Flow Control command message and the videoFastUpdatePicture message. All these H.245 messages are conveyed between the MGCF and the CS side by the IM-MGW, as described in clause E.4.2.3. + +##### E.4.2.6.2 Flow control command + +The flow control command is used to restrict the upper limit of bit rate of either a single logical channel or the whole multiplex stream. The MGCF may support the flow control command received from the CS side. + +NOTE: It is very unlikely that the MGCF will receive a Flow control command, as the capability of controlling the video bit rate during a video call was neither implemented nor tested for UEs offering 3G-324M since R99, due to the lack of such a necessity in WCDMA where a fixed 64 kbps bearer is maintained to continuously transport 3G-324M PDUs. + + + +``` + +sequenceDiagram + participant IM MGW + participant MGCF + Note over IM MGW, MGCF: Call In Active State + MGCF->>IM MGW: 1. H.245: Flow Control Command + IM MGW->>MGCF: 2. H.248: Modify.req +C=C1,T=T2,stream{LCN}, stream mode=Recieve Only + MGCF->>IM MGW: 3. H.248: Modify.rsp + IM MGW->>MGCF: 4. H.245: Close Logical Channel{Old LCN} +Open Logical Channel {New LCN} + MGCF->>IM MGW: 5. H.245: Close Logical Channel ACK{Old LCN} +Open Logical Channel ACK{New LCN} + IM MGW->>MGCF: 6. H.248: Modify.req +C=C1,T=T2,stream{New LCN, codec}, stream mode = sendreceive + MGCF->>IM MGW: 7. H.248: Modify.rsp + IM MGW->>MGCF: 8. H.245: Flow Control indication + Note right of MGCF: 9. SIP:reINVITE +10. SIP:200 OK + MGCF->>IM MGW: 11. H.248: Modify.req +C=C1,T=T3,stream{codec} + IM MGW->>MGCF: 12. H.248: Modify.rsp + +``` + +Sequence diagram illustrating the Mn procedure of Flow control command between IM MGW and MGCF. + +**Figure E.4.2.6.2.1: Mn procedure of Flow control command** + +In Signal 1, the MGCF receives the Flow Control Command from the CS side. + +If the minimum bitrate of the current codec is larger than the bitrate requested by the H.245 Flow Control Command message, the MGCF indicates the IM-MGW to stop the transmission of the media stream over the logical channel (signal 2). Then the MGCF may select another codec that can satisfy the requested bitrate limit. In signal 4, the MGCF closes the old logical channel and opens a new logical channel with new codec to satisfy the bitrate limit in the CS side. In signal 6, the MGCF indicates the IM-MGW to modify the LCN, codec and stream mode of the multiplexing termination. In signal 8, the MGCF sends flow control indication message to CS side with the current maximum bitrate. If the MGCF chooses to change the CS-side codec, the MGCF may also adjust the codec at the IMS side accordingly. To do so, the MGCF may need to re-negotiate the codec at the IMS side using a SIP re-INVITE message (signals 9 and 10). In addition, the MGCF may modify the codec of IMS termination accordingly (signal 11). + +The MGCF may also apply interworking procedure towards RTCP at the IMS side as described in clause E.4.2.8 when receiving a H.245 Flow Control Command. + +##### E.4.2.6.3 End Session Command + +The end session command is used to close the H.245 control channel after all the logical channels have been closed. + +The MGCF may send an end session command to the CS side through the IM-MGW to release a call. + +If the MGCF receives an end session command from the CS side, it shall release the call if the call is in the active state. + +##### E.4.2.6.4 videoFastUpdatePicture + +The MGCF may apply interworking procedure towards RTCP as described in clause E.4.2.8 when receiving a H.245 videoFastUpdatePicture message. The MGCF may also be triggered by the procedures in clause E.4.2.8 to send a H.245 videoFastUpdatePicture message. + +When receiving frequent H.245 videoFastUpdatePicture messages for a SCUDIF call (see 3GPP TS 23.172 [121]), an MGCF should initiate a service-change from multimedia to speech and remove the IMS MTSI video component with SIP/SDP signalling. When receiving frequent H.245 videoFastUpdatePicture messages for a non-SCUDIF call, an MGCF should disable the CS video and remove the IMS MTSI video component with SIP/SDP signalling. + +**NOTE:** In a congestion situation at the IMS side, frequent packet losses might occur and dropping the video component may serve as a counter-measure to reduce the packet loss frequency. However, CS terminals might not be able to initiate such a switch-over to voice, but might rather react with repeated H.245 videoFastUpdatePicture message. + +#### E.4.2.7 Mn Signalling Interactions to support the Media Oriented Negotiation Acceleration (MONA) + +##### E.4.2.7.1 Overview + +Media Oriented Negotiation Acceleration (MONA), as specified in ITU-T H.324 [81] provides simplified procedures that allow for a faster call set-up of a H.324 Multimedia call than standard H.324 procedures, and also allow for a fallback to standard H.324 procedures if either party does not support the enhanced procedures. + +The support of MONA is optional for an IM-MGW and MGCF supporting multimedia interworking, as no call failure but only a fallback to standard H.324 setup procedures will occur if the procedures are not supported. + +MONA "preference message" signalling is used instead of H.324 Multiplexing level negotiation. Should standard H.324 Multiplexing level stuffing flags be received, a fallback to standard H.324 procedures is triggered. The sending of MONA preference messages is repeated by each MONA capable H.324 terminal until a reception is acknowledged by the peer. During this phase, two PDU types may optionally be attached by MONA terminals to these preference messages: + +- Media Preconfigured Channel (MPC) PDUs: MONA defines a small number of preconfigured H.223 channels for the most widespread audio and video codecs (AMR, AMR-WB, H.264 MPEG4 and H.263). Media PDUs for these codecs may be attached to the MONA "preference message" during the call setup. +- Signalling Preconfigured Channel (SPC) PDUs: These PDUs are H.245 generic request messages with special parameters defined by MONA. These PDUs may also be attached to MONA preference messages. + +According to MONA, each MONA capable terminal shall support at least one of these PDU types. The MONA capability of the IM-MGW can be audited by the MGCF. + +The MONA preference message exchange in combination with attached MPC or SPC PDUs may result in the establishment of the desired media channels without further H.245 signalling. Otherwise, H.245 will be used after the MONA preference message exchange is acknowledged to negotiate media channels, but MONA defines some accelerated H.245 procedures (ACP) to speed up these H.245 procedures. + +The design of Mn procedures to support MONA is guided by the following considerations: + +- The H.245 handling should be performed in the MGCF to keep procedures aligned as far as possible with standard Mn procedures to support H.324 interworking. +- The MGCF should also control MONA preference message exchange procedures in order to maintain the agreed architectural work split between MGCF and IM-MGW in analogy to the H.245 handling. +- However, the IM-MGW needs to understand the MONA preference messages at least to a sufficient degree to de-encapsulate the possibly attached MPC and SBC PDUs. +- Furthermore, the frequent retransmissions of MONA preference messages required by MONA procedures are to be performed by the IM-MGW autonomously to avoid unnecessary load at the Mn interface and the MGCF. +- Furthermore, for resource reservation at the IM-MGW, it is assumed that the IM-MGW has knowledge about supported predefined Media Preconfigured Channel configurations as specified in clause K.9.2 of H.324 [81] in order to limit the amount of information transferred in the Mn interface when establishing MPC channels. The offered channel resources are reserved by the IM-MGW. +- In order to avoid increasing call establishment time when interworking with legacy terminals and at the same time avoid unnecessary load at the Mn interface, the MGCF may initiate both MONA and legacy H.245 procedures simultaneously in parallel. The MGCF shall in this case arm a legacy detection event with an embedded signal descriptor including the initial legacy H.245 message. The IM-MGW will only send the signal in case a fallback condition to legacy is detected. + +##### E.4.2.7.2 Mn Interactions for MONA preference messages + + + +``` + +sequenceDiagram + participant IM MGW + participant MGCF + + MGCF->>IM MGW: 1. H.248: ADD.req [C=?, T=?, stream=1] + Note right of MGCF: Prepare Bearer or +Establish Bearer or +Reserve TDM Circuit + IM MGW-->>MGCF: 2. H.248: ADD.resp [C=C1, T=T1] + + MGCF->>IM MGW: 3. H.248: ADD.req [C=C1, T=?, stream=2{Codec=H.263}, stream=3{Codec=AMR}] + Note right of MGCF: Reserve IMS +Connection Point or +Reserve IMS +Connection Point +and Configure +Remote Resources + IM MGW-->>MGCF: 4. H.248: ADD.resp [C=C1, T=T3] + + Note left of IM MGW: 5. Bearer Establishment + + MGCF->>IM MGW: 6. H.248: ADD.req [C=C1, T=?, Mux=H223, T1, LocalControl{MONA preferences, muxlv=2}, Event=legacyDetected(h245msgout{octet string}), MONA-preference-reception, MONA-preference-completed, H245msgin, [MPC-reception, SBC-reception]] + Note right of MGCF: Add +Multiplex +Termination + IM MGW-->>MGCF: 7. H.248: ADD.resp [C=C1, T=T2] + + IM MGW->>IM MGW: 8. MONA preferences [ack=00] + IM MGW->>IM MGW: 8. MONA preferences [ack=00] + IM MGW->>IM MGW: 9. MONA preferences [ack=00] + IM MGW->>IM MGW: 10. MONA preferences [ack=01] + + MGCF->>IM MGW: 11. H.248: Notify.req [C=C1, T=T2, Event=MONA-preference-reception {MONA preferences}] + Note right of MGCF: Notify +MONA +prefrence +reception + IM MGW-->>MGCF: 12. H.248: Notify.resp + + IM MGW->>IM MGW: 9. MONA preferences [ack=00] + IM MGW->>IM MGW: 10. MONA preferences [ack=01] + IM MGW->>IM MGW: 13. MONA preferences [ack=01] + IM MGW->>IM MGW: 14. MONA preferences [ack=10] + + Note over IM MGW, MGCF: Optional Procedures for reception of SPC PDU, sending of SPC PDU, reception of MPC PDU, sending of MPC PDU + + IM MGW->>IM MGW: 13. MONA preferences [ack=01] + IM MGW->>IM MGW: 14. MONA preferences [ack=10] + IM MGW->>IM MGW: 15. MONA preferences [ack=10] + + MGCF->>IM MGW: 16. H.248: Notify.req [C=C1, T=T2, Event=MONA-preference-completed] + Note right of MGCF: Notify +MONA +prefrence +completed + IM MGW-->>MGCF: 17. H.248: Notify.resp + + Note over IM MGW, MGCF: 18. Accelerated H.245 call setup procedures + + MGCF->>IM MGW: 19. H.248: MOD.req [C=C1, T=T2, Stream=1{LocalControl{h223capr, muxtbl_in, muxtbl_out}}, stream=2{LCN=LC1, Codec=H263}, stream=3{LCN=LC2, Codec=AMR}] + Note right of MGCF: Configure +Multiplex +Termination + IM MGW-->>MGCF: 20. H.248: MOD.resp + + MGCF->>IM MGW: 21. H.248: MOD.req [C=C1, T=3, stream=2{Codec=H263}, stream=3{Codec=AMR}] + Note right of MGCF: Configure IMS +Ressources + IM MGW-->>MGCF: 22. H.248: MOD.resp [C=C1, T=T3] + +``` + +Sequence diagram showing Mn interactions for MONA preference messages between IM MGW and MGCF. + +NOTE 1: MONA preference messages are repeated several times. One repetition is shown for each such message, with the same signal number as the first message. + +NOTE 2: The Context model in figure E.4.2.2.1 is assumed in this call flow. + +**Figure E.4.2.7.2.1: Mn signalling interactions for MONA preference messages** + +The MGCF shall request terminations towards the CS network (Signal 1 and 2) and towards the IMS (Signal 3 and 4). For the terminations towards the IMS, the MGCF provides an estimate about the applicable codecs in the required information elements "Local IMS Resources" (for both "Reserve IMS Connection Point" procedure and "Reserve IMS + +Connection Point and Configure Remote Resources" procedure) and possibly "Remote IMS Resources" (only for "Reserve IMS Connection Point and Configure Remote Resources" procedure). + +The MGCF shall request that the H.223 stream is (de-)multiplexed at the MUX termination T2 (signal 6). Furthermore, the MGCF shall request that MONA preferences negotiation is started, and shall provision the MONA preferences to be indicated by the IM-MGW. The MGCF shall encode the MONA preferences as described in clause K.6 of ITU-T H.324 [81]. The MGCF shall take the H.324 related capabilities of the IM-MGW into account in the MONA preferences. The MGCF can know these capabilities by configuration. The IM-MGW will only support symmetric codec usage. If several codec alternatives are offered for MPC, it is the responsibility of the MGCF to ensure that symmetric codecs are established by not selecting transmit codec until the receive channel has been opened by MPC media. The MGCF shall also request to be notified about the reception of the remote MONA preferences and about the completion of the MONA preference exchange, or an H.245 message on the H.223 control channel. The MGCF may also initiate standard H.245 signalling in parallel in order to minimize the time for a legacy interworking fallback. This is done by arming a legacy detection event including an embedded signal descriptor. The embedded signal is the initial H.245 message out signal (including H.245 TCS+MSD) to send in case fallback to legacy interworking is detected. The IM-MGW will only send the embedded signal in case it detects H.223 related indications of a legacy interworking as specified in clause K.7.1.2 in H.324 [81]. Upon receiving the legacy detected event, the MGCF continues with standard H.245 call setup procedures waiting for the reception of a remote H.245 TCS as well as acknowledgements on the sent H.245 TCS+MSD. If the MGCF indicates the capability to receive SPC PDUs within the MONA preferences, it shall also request to be notified about incoming SPC PDUs, as detailed in clause E.4.2.7.4. If the MGCF indicates the capability to receive any MPC PDUs within the MONA preferences, it shall also request to be notified about incoming MPC PDUs, as detailed in clause E.4.2.7.3. + +The IM-MGW shall start sending MONA preference messages after receipt of the corresponding request from the MGCF and CS bearer establishment (Signal 8). The IM-MGW shall repeat sending those messages and increment the acknowledgment bits of sent MONA preference messages when receiving incoming MONA preference messages according to MONA procedures (signals 8, 10, 14). + +After sending at least 10 MONA preference messages, while the IM-MGW continues to send and receive MONA preference messages, it shall attach MPC or SPC PDUs if requested to do so by the MGCF as described in clauses E.4.2.7.3 and E.4.2.7.4, respectively. If the IM-MGW receives preference messages with an attachment, it shall inspect the first octet of that attachment that will contain a MUX code according to table K.15 of ITU-T H.324 [81] that identifies the attached PDU as either a MPC PDU of one of the predefined channels or a SPC PDU. The IM-MGW shall handle the attached MPC or SPC PDUs as described in clause E.4.2.7.3 and E.4.2.7.4, respectively. + +After sending at least 10 MONA preference messages, the IM-MGW should insert stuffing flags indicating the multiplexing level received from the MGCF between MONA preference messages as described in clause K.7.1.1 of ITU-T H.324 [81]. + +The IM-MGW shall notify the MGCF when receiving the first incoming MONA preference message (Signals 11 and 12) and forward the received information. Subsequent incoming MONA preference message will be identical apart from possible increments in the acknowledgement bits. The IM-MGW shall not notify the MGCF about these messages. Upon reception of the notification of a MONA preference message, the MGCF shall compare the received MONA preferences message with the preferences message it sent and react as described in clause 7.1 of ITU-T H.324 [81]. + +When receiving an incoming MONA preference message with acknowledgment bits 10 or receiving the first non-empty H.223 MUX PDU, the IM-MGW shall notify the MGCF about the completion of the MONA preference exchange procedure (signals 16 and 17). The notification shall be only triggered by the one of the two events which occurs first. If the IM-MGW is not configured to send and detect SPCs, the IM-MGW shall then stop sending MONA preference messages and, if a MONA preference message with acknowledgment bits 10 has been received, it shall also stop receiving MONA preference messages. If the IM-MGW is configured to send and detect SPCs, the IM-MGW shall continue sending and receiving MONA Preference messages encapsulating the SPC/MOS messages until the MGCF configures the IM-MGW stop sending and detecting SPCs. + +NOTE: In the unlikely case that a first non-empty H.223 MUX-PDU is received before the first MONA Preference Message has been received, the IM-MGW will continue the detection of incoming MONA Preference Messages and will apply the Notify-MONA-preference-Reception-procedure after the Notify-MONA-preference-completed procedure. + +After receiving the notification about the completion of the MONA preference exchange procedure, and a completion of the possible subsequent accelerated H.245 setup procedures, the MGCF shall configure the multiplexing termination T2 + +by indicating to the IM-MGW the contents of the incoming and outgoing multiplex tables (Signal 19), and may modify the selected codecs at both the MUX and the IMS side (signal 21). + +##### E.4.2.7.3 Mn Interactions for MONA MPCs + + + +``` + +sequenceDiagram + participant IM MGW + participant MGCF + Note left of IM MGW: 3 MONA preference message, Mux Code + Note left of IM MGW: 4 MONA preference message, Mux Code, MPC PDU + Note left of IM MGW: 5 MONA preference message, Mux Code + Note left of IM MGW: 10 PDU in MPC + Note left of IM MGW: 11 MONA preference message, Mux Code + Note left of IM MGW: 12 MONA preference message, Mux Code, MPC PDU + + MGCF->>IM MGW: 1. H.248 ADD.req [C=C1,T=? ... ,Event=MPC-reception, Signal =MPC MUX Code] + Note right of MGCF: Add Multiplex Termination + IM MGW-->>MGCF: 2. H.248 ADD.resp + IM MGW->>MGCF: 6. H.248 : Notify.req [C=C1,T=T2 Event=MONA-preference-reception {MONA preferences},] + Note right of MGCF: Notify MONA preference reception, + MGCF-->>IM MGW: 7. H.248 : Notify.resp + IM MGW->>MGCF: 8. H.248: MOD.req [C=C1, T=T2, Stream=1{LocalCont{.muxtbl_out}}] + Note right of MGCF: Configure Multiplex Termination + MGCF-->>IM MGW: 9. H.248: MOD.resp + IM MGW->>MGCF: 13. H.248 : Notify.req [C=C1,T=T2 Event=MPCin {muxcode=Mux Code}] + Note right of MGCF: Notify MPC + MGCF-->>IM MGW: 14. H.248 : Notify.resp + IM MGW->>MGCF: 15. H.248: MOD.req [C=C1, T=T2, Stream=1{LocalCont{.muxtbl_in}}] + Note right of MGCF: Configure Multiplex Termination + MGCF-->>IM MGW: 16. H.248: MOD.resp + +``` + +Sequence diagram showing Mn interactions for MONA MPCs between IM MGW and MGCF. The diagram includes 16 numbered messages and associated actions like 'Add Multiplex Termination', 'Notify MONA preference reception', 'Configure Multiplex Termination', and 'Notify MPC'. + +NOTE 1: MONA preference messages are repeated several times. One repetition is shown for each such message, with the same signal number as the first message. + +NOTE 2: The Context model in figure E.4.2.2.1 is assumed in this call flow. + +**Figure E.4.2.7.3.1: Mn interactions for MONA MPCs** + +If the MGCF indicates the ability to receive any predefined MPCs channel types in the MONA preferences messages, the MGCF shall request the IM-MGW to report the channel type of received MPC PDUs (Signal 1 in figure E.4.2.7.3.1, Event "MPC Reception"). + +If the MGCF intends to use MPCs for sending media during the MONA setup, the MGCF shall request the IM-MGW to send available media encoded according to the media predefined channel types defined by MONA (signal 1 in figure E.4.2.7.3.1, Signal "MPC MUX Code") while the MONA preference exchange described in clause E.4.2.7.2 is ongoing. The MGCF should select channel types for codecs which are supported by both the IMS side and the IM-MGW, and/or for codecs which could be transcoded by the IM-MGW from the codecs supported by the IMS side. The MGCF shall only include one channel type per each desired media type (audio, video) in the "MPC MUX Code" signal. The MGCF may also configure the MGW to receive these channels at the same time by supplying the Incoming Multiplex Table IE in the Add Multiplex Termination Procedure. + +Upon reception of this request, the IM-MGW shall forward any media received from the IMS side in MPC PDUs of the corresponding predefined channel type attached to MONA preference messages, transcoding the media if required (Signal 4). + +According to the procedures in clause E.4.2.7.2, the IM-MGW will notify the MGCF (signal 6) when receiving the first incoming MONA preference message (Signals 5). The MGCF shall then analyse the Media Preconfigured Channel Receive bits within the MONA preference message and configure the MGW accordingly: + +- If MPC(s) that the MGCF has previously configured within the "MPC MUX Code" signal are supported according to these bits, the MGCF shall configure the IM-MGW to send these MPC using the predefined channels (signal 10) by supplying the corresponding Outgoing Multiplex Table in the Configure Multiplex Termination procedure (signal 8). +- If some of the MPC(s) that the MGCF has previously configured within the "MPC MUX Code" signal are not supported according to these bits, the MGCF shall configure the IM-MGW to terminate the media on those MPC(s) by modifying the MPC Mux Code signal using the Configure Multiplex Termination procedure. In addition, the MGCF may configure the IM-MGW to send media on other supported MPC(s) by supplying the corresponding Outgoing Multiplex Table in the Configure Multiplex Termination procedure (not shown in figure E.4.2.7.3.1). +- If all of the MPC(s) that the MGCF has previously configured within the "MPC MUX Code" signal are not supported according to these bits, the MGCF shall configure the IM-MGW to terminate MPC operations in those unsupported channels. The MGCF shall either remove the MPC Mux Code signal using the Stop MPC procedure or configure the IM-MGW to send media on other supported MPC(s) by supplying the corresponding Outgoing Multiplex Table in the Configure Multiplex Termination procedure (not shown in figure E.4.2.7.3.1). + +When the MGCF provides an Outgoing Multiplex Table, the IM-MGW shall terminate sending any MPC PDUs as attachments to MONA preference message. + +NOTE: Any previously provisioned "MPC MUX Code" signal becomes irrelevant. + +When being notified about the receipt of the first incoming MONA preference message, the MGCF may also analyse the Media Preconfigured Channel Receive bits within the MONA preference message and configure the MGW with a suitable Incoming Multiplex Table using the Configure Multiplex Termination procedure (not shown in figure E.4.2.7.3.1). + +If the IM-MGW receives the first MONA preference message with attached MPC PDU of a given predefined channel type (signal 12), or if the IM-MGW receives the first non-empty H.223 MUX PDU of a given predefined channel type which has been configured with the Incoming Multiplex Table, and the MGCF has requested a notification about such an event, the IM-MGW shall notify the MGCF about the received channel type (signal 13). The IM-MGW shall not notify the MGCF about subsequent receptions of MPC PDUs of the same channel type. + +Upon reception of such a notification, if the IM-MGW supports the indicated channel type and has not yet been configured to receive media of that channel type, and if the MGCF has previously indicated the capability to receive MPCs of that channel type within MONA preference messages, the MGCF shall configure the IM-MGW to receive media of that channel type and forward them to the IMS side by supplying the Incoming Multiplex Table IE in the Configure Multiplex Termination procedure (Signal 15). + +If the MGCF determines (e.g. after receipt of signal 5 or signal 12) that some desired media channels can not be established using the MPC procedures, the MGCF should use accelerated H.245 procedures as defined by MONA to set up media channels. Corresponding H.245 messages shall be transported transparently between the IM-MGW and the MGCF using the "Signal H.245 message" and "Notify H.245 message" procedures. + +The MGCF can receive a forwarded MONA preference message from the IM-MGW when the MGCF has already configured the IM-MGW to send media on an MPC. If the processing of this message in the MGCF leads to the conclusion that MPC procedures need to be aborted because SPC preferred (SPP) is determined, the MGCF shall configure the IM-MGW to terminate MPC operations by removing the MPC related event MPC-reception and MPC Mux Code signal using the Stop MPC procedure. + +##### E.4.2.7.4 Mn Interactions for MONA SPCs + +###### E.4.2.7.4.1 General + +H.245 PDUs for SPC shall be transported between the IM-MGW and MGCF over the Mn interface using H.248 Events (from the IM-MGW towards the MGCF) and H.248 Signals (from the MGCF towards the IM-MGW). The Events/Signals shall contain the following information: + +- H.245 message (binary). + +The related procedures are distinct from the procedures in clause E.4.2.3, since the PDUs are received or sent by the IM-MGW using the SPC, i.e. as attachment to MONA preference messages. + +If the MGCF supports SPCs, it shall comply with the SPC procedures in clause K.8 of ITU-T H.324 [81]. The repetition of sending the same SPCs will be handled by the IM-MGW. When the MGCF receives an acknowledgement from the CS side it shall request the IM-MGW to stop the repetition sending of the SPCs, + +Within the sent SPC PDUs, the MGCF should include the codecs which are supported by both the IMS side and the IM-MGW, and the codecs which could be transcoded by the IM-MGW from the codecs supported by the IMS side. + +###### E.4.2.7.4.2 Transport from MGCF to IM-MGW + + + +``` + +sequenceDiagram + participant MGCF + participant IM-MGW + Note right of MGCF: Signal SPC + MGCF->>IM-MGW: 1. H.248 MOD.req [C=C1,T=T2, signal=SPCout {h245mc=XXXX} ] + IM-MGW-->>MGCF: 2. H.248 MOD.resp + Note left of IM-MGW: 3. send H.245 message XXXX attached to MONA preference request + IM-MGW->>CS: 3. send H.245 message XXXX attached to MONA preference request + Note left of IM-MGW: 3. send H.245 message XXXX attached to MONA preference request + IM-MGW->>CS: 3. send H.245 message XXXX attached to MONA preference request + +``` + +The diagram illustrates the interaction between the MGCF and the IM-MGW for sending MONA SPCs. The MGCF sends an H.248 MOD.req signal (Signal 1) to the IM-MGW, containing context and signal information. The IM-MGW responds with an H.248 MOD.resp signal (Signal 2). The IM-MGW then sends an H.245 message attached to a MONA preference request (Signal 3) to the CS side. The diagram shows two repetitions of Signal 3, indicating that the message is repeated several times. + +Sequence diagram showing Mn interactions for sending MONA SPCs between IM-MGW and MGCF. + +NOTE 1: MONA preference messages are repeated several times. One repetition is shown for each such message, with the same signal number as the first message. + +NOTE 2: The Context model in figure E.4.2.2.1 is assumed in this call flow. + +**Figure E.4.2.7.4.2.1: Mn interactions for sending MONA SPCs** + +In Signal 1, the MGCF requests the IM-MGW to send an H.245 message to the CS side. To request the IM-MGW to send a H.245 message to the CS side, the MGCF shall send an H.248 signal to the IM-MGW with the complete H.245 message content. + +Upon reception of this signal, the IM-MGW shall send the encapsulated H.245 message within the H.248 signal, as attachment to a MONA preference message as described in clause K.9.4 of ITU-T H.324 [81] (signal 3). It should repeat sending this H.245 message as attachment to subsequent MONA preference messages. + +###### E.4.2.7.4.3 Transport from IM-MGW to MGCF + + + +``` + +sequenceDiagram + participant External + participant IM_MGW as IM MGW + participant MGCF + Note right of MGCF: Add Multiplex Termination + MGCF->>IM_MGW: 1. H.248 ADD.req [C=C1,T=? ... ,Event=SPC-reception] + IM_MGW-->>MGCF: 2. H.248 ADD.resp + External->>IM_MGW: 3. receive H.245 message attached to MONA preference message + Note right of MGCF: Notify SPC + IM_MGW->>MGCF: 4. H.248 Notify.req [C=C1,T=T2 Event=SPCin {h245mc=XXXX}] + MGCF-->>IM_MGW: 5. H.248 Notify.resp + +``` + +Sequence diagram showing interactions between IM MGW and MGCF for receiving MONA SPCs. The diagram shows five messages: 1. H.248 ADD.req from MGCF to IM MGW; 2. H.248 ADD.resp from IM MGW to MGCF; 3. receive H.245 message attached to MONA preference message from an external source to IM MGW; 4. H.248 Notify.req from IM MGW to MGCF; 5. H.248 Notify.resp from MGCF to IM MGW. Annotations on the right indicate 'Add Multiplex Termination' for message 2 and 'Notify SPC' for message 4. + +NOTE 1: MONA preference messages are repeated several times. One repetition is shown for each such message, with the same signal number as the first message. + +NOTE 2: The Context model in figure E.4.2.2.1 is assumed in this call flow. + +**Figure E.4.2.7.4.3.1: Mn interactions for receiving MONA SPCs** + +In signal 1, the MGCF requests the IM-MGW to detect received H.245 message from the CS side in SPC PDUs attached to MONA preference messages and forward them to the MGCF. To request the IM-MGW to detect and forward these H.245 message, the MGCF shall send a suitable H.248 event to the IM-MGW. The event may be indicated through an H.248 ADD command. + +In signal 3, the IM-MGW receives an H.245 message from the CS side attached as SPC PDU to a MONA preference message. Upon reception of such an H.245 message from the CS side, the IM-MGW may check, based on bitwise comparison of the previously received H.245 message, if it has already forwarded the same H.245 message to the MGCF, in which case the IM-MGW may choose not to forward the same H.245 message to the MGCF. Otherwise the IM-MGW shall forward the H.245 message to the MGCF within an H.248 Notify command (signal 4). + +NOTE: According to H.324 [81] a MOS request Ack message shall be sent to every received MOS request. If the IM-MGW chooses, based on the bitwise comparison, not to forward the received H.245 message to the MGCF, no MOS request Ack message will be generated. However, the MGCF will request the IM-MGW to automatically retransmit the MOS request Ack message generated by the MGCF itself. + +If the IM-MGW does not support forwarding SPC PDUs or has not been requested by the MGCF to forward these PDUs, it shall discard received SPC PDUs. + +###### E.4.2.7.4.4 Termination of SPC procedure + + + +``` +sequenceDiagram + participant IM MGW + participant MGCF + Note left of IM MGW: 1 receive final H.245 message attached to MONA preference message + IM MGW->>MGCF: 2 H.248 : Notify.req [C=C1,T=T2 Event=SPCin {h245mc=XXXX}] + Note right of MGCF: Notify SPC + MGCF-->>IM MGW: 3 H.248 : Notify.resp + MGCF->>IM MGW: 4 H.248 MOD.req [C=C1,T=T2 Remove Signal-SPC+ SPC-reception] + Note right of MGCF: Stop SPC + IM MGW-->>MGCF: 5 H.248 MOD.resp +``` + +The diagram illustrates the interaction between the IM MGW and the MGCF for terminating the SPC procedure. It consists of five numbered messages: 1. An external message received by the IM MGW; 2. A Notify.req message from IM MGW to MGCF; 3. A Notify.resp message from MGCF to IM MGW; 4. A MOD.req message from MGCF to IM MGW; 5. A MOD.resp message from IM MGW to MGCF. Annotations on the right side indicate the actions 'Notify SPC' and 'Stop SPC' associated with the MGCF's messages. + +Sequence diagram showing the termination of SPC procedure between IM MGW and MGCF. + +NOTE 2: The Context model in figure E.4.2.2.1 is assumed in this call flow. + +**Figure E.4.2.7.4.4.1: Mn interactions for terminating SPC procedure** + +If the processing of an incoming MONA Preference Message in the MGCF leads to the conclusion that SPC procedures need to be aborted as a result of the test of the SPC bits, the MGCF shall configure the IM-MGW to terminate SPC operations by removing the SPC related event SPC-reception and SPCout signal using the Stop SPC procedure. In this case, H.245 signalling may be started simultaneously. + +If the MGCF determines the completion of the SPC procedures according to clause K.8 of ITU-T H.324 [81] (based on incoming signal 1 in figure E.4.2.7.4.4.1), the MGCF shall configure the IM-MGW to stop sending and detecting SPCs (signal 4 in figure E.4.2.7.4.4.1). + +##### E.4.2.7.5 Mn Interactions for fallback from MONA procedures to standard H.324 setup + + + +``` + +sequenceDiagram + participant IM MGW + participant MGCF + Note right of MGCF: Prepare Bearer or Establish Bearer or Reserve TDM Circuit + IM MGW->>MGCF: 1. H.248: ADD.req [C=?, T=?, stream=1] + MGCF-->>IM MGW: 2. H.248: ADD.resp [C=C1, T=T1] + Note right of MGCF: Reserve IMS Connection Point or Reserve IMS Connection Point and Configure Remote Resources + IM MGW->>MGCF: 3. H.248: ADD.req [C=C1, T=?, stream=2(Codec=H.263), stream=3(Codec=AMR)] + MGCF-->>IM MGW: 4. H.248: ADD.resp [C=C1, T=T3] + Note left of IM MGW: 5. Bearer Establishment + Note right of MGCF: Add Multiplex Termination + IM MGW->>MGCF: 6. H.248: ADD.req [C=C1, T=?, Mux=H223.T1, LocalControl(MONA preferences, muxlv=2), Event=legacyDetected(h245msgout{octet string}), MONA-preference-reception, MONA-preference-completed, H245msgin, MPC-reception, SBCin] + MGCF-->>IM MGW: 7. H.248: ADD.resp [C=C1, T=T2] + IM MGW->>IM MGW: 8. MONA preferences [ack=00] + IM MGW->>IM MGW: 8. MONA preferences [ack=00] + IM MGW->>MGCF: 9. Legacy interworking condition + MGCF-->>IM MGW: 10. octet string (H.245 TCS+MSD) + Note right of MGCF: Notify detection of legacy interworking + IM MGW->>MGCF: 11. H.248 : Notify.req [C=C1,T=T2] + MGCF-->>IM MGW: Event=legacyDetected + IM MGW->>MGCF: 12. H.248 : Notify.resp + Note left of IM MGW: 13. standard H.245 call setup procedures continuation, Figure E.4.2.4.1 starting with step 9 + +``` + +Sequence diagram showing Mn signalling interactions for fallback from MONA procedures to standard H.324 setup between IM MGW and MGCF. + +NOTE 1: MONA preference messages are repeated several times. One repetition is shown for each such message, with the same signal number as the first message. + +NOTE 2: The Context model in figure E.4.2.2.1 is assumed in this call flow. + +**Figure E.4.2.7.5.1: Mn signalling interactions for fallback from MONA procedures to standard H.324 setup** + +When the MGCF requests that the MONA preferences negotiation is started, the MGCF may also initiate standard H.245 signalling towards the IM-MGW that shall only be sent in case the IM-MGW detects legacy interworking. The MGCF arms an event to detect legacy interworking with an embedded signal descriptor including an H.245 message out signal. The embedded H.245 signal is the initial H.245 TCS+MSD signal to send in case fallback to legacy interworking is detected. The MGCF shall also request to be notified about an H.245 message on the H.223 control channel. The MGCF shall also provision a multiplexing level which will be advertised by the IM-MGW (Signal 6). + +If the IM-MGW detects a legacy interworking condition (signal 9), it shall stop sending MONA preference messages, including those MONA messages used to encapsulate MPC or SPC. The IM-MGW shall engage in normal H.324 multiplexing level negotiations. In case the MGCF armed a legacy detection event, the embedded H.245 signal shall be sent by the IM-MGW (signal 10). The legacy detection event is sent to the MGCF (signal 11). + +The MGCF shall upon detection of legacy interworking stop MONA procedures and continue with standard H.245 call set up procedures, as depicted in figure E.4.2.4.1 starting with step 9. + +If the IM-MGW receives a normal H.245 message (not depicted), it shall also forward this message to the MGCF. If the MGCF receives such a H.245 message during the MONA call setup, and this H.245 message is a normal Terminal Capability Set message, the MGCF shall also stop MONA procedures and continue with standard H.245 call set up procedures, as depicted in figure E.4.2.4.1 starting with step 9. + +To stop MONA related procedures at the IM-MGW, the MGCF shall remove the MONA related signals that were active (MONA Preferences, SPCout, MPC Mux Code; note that MONA Preference and SPCout causes the MGW to send the MONA Preference message or the contained H.245 message several times) and events (MonaPreferenceReception, MonaPreferenceCompleted, SPC-reception and MPC-reception, using the Stop MONA Negotiation procedure). + +#### E.4.2.8 Interworking between RTCP messages and H.245 messages + +##### E.4.2.8.1 Overview + +The following clauses describe the interworking procedures between the RTCP messages listed in table E.4.2.8.1.1, which are used to enhance the quality of the media distribution by MTSI terminals at the IMS side, and the corresponding H.245 messages in 3G-324M at the CS side listed in table E.4.2.8.1.1. + +As the H.245 protocol is terminated at the MGCF and RTCP is received at the IM-MGW, Mn procedures to support the transfer of RTCP related information are defined in the following Clauses to support this interworking. + +**Table E.4.2.8.1.1: RTCP and H.245 messages that may be interworked** + +| RTCP Messages | H.245 messages | Remarks | +|-----------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Picture Loss Indication (PLI) ([109]) | VideoFastUpdatePicture | | +| Temporary Maximum Media Stream Bit Rate Request (TMMBR) ([110]) | Flow Control Command/ Flow Control Indication | This interworking procedure is not recommended.
The reception of TMMBR at the IMS side is expected to be more frequent than the reception of Flow Control Command at the CS side. | + +NOTE 1: It is very unlikely that the MGCF will receive a Flow control command, as the capability of controlling the video bit rate during a video call was neither implemented nor tested for Ues offering 3G-324M since R99, due to the lack of such a necessity in WCDMA where a fixed 64 kbps bearer is maintained to continuously transport 3G-324M PDUs. + +NOTE 2: Terminals are expected to support receiving the FlowControlCommand, as this is a mandatory feature in clause 6.4.3 in H.324. But most terminals would not really follow the received FlowControlCommand, but rather ignore it. However, for older 3G-324M terminal lock-up or system crash was not uncommon during IOTs. Therefore safe handling of this command is not guaranteed absolutely + +The interworking shown in table E.4.2.8.1.1 is only applicable if video is relayed without transcoding. + +If transcoding is applied, the IM-MGW should adopt its transcoder accordingly if receiving the RTCP messages listed in table E.4.2.8.1.1, and the MGCF should configure the transcoder in the IM-MGW accordingly if it receives the H.245 messages in table E.4.2.8.1.1. + +For an MGCF and IM-MGW that support video interworking as specified in the present Annex E, the support of the procedures in the present clause E.4.2.8.2 and E.4.2.8.3 is optional. + +##### E.4.2.8.2 IM CN subsystem originated RTCP messages + +The MGCF may configure the IM-MGW to detect specific received RTCP packets and forward information derived from it by providing a bit pattern(s) for bits 3-15 of incoming RTCP packets as filter criterion in an event descriptor of event "RTCP-interworking". Bits 3-7 in the RTCP packet represent the Feedback message type (FMT), and bits 8-15 in the RTCP packet represent the Payload type (PT) RTCP header fields, see IETF RFC 4585 [109]. For instance, to request that an AVPF Picture Loss Indication (PLI) packet is detected for interworking, the MGCF needs to configure a combination of PT=206 (Payload-specific FB message) and FMT=1 (see IETF RFC 4585 [109]). To request that a AVPF Temporary Maximum Media Bit-rate Request (TMMBR) packet is detected for interworking, the MGCF needs to configure a combination of PT=205 (transport layer feedback message) and FMT=3 (see IETF RFC 5104 [110]). + +A IM-MGW configured in this way shall check after receiving an incoming RTCP Packet if it is of a desired type, as expressed by a bit pattern received from the MGCF. An incoming RTCP message can be of compound format and contain several RTCP packets. The IM-MGW shall then perform the check separately for each packet. If the IM-MGW determines that the received RTCP packet is of a desired type, the IM-MGW shall send information derived from the RTCP message as ObservedEventsDescriptor Parameter(s) of event "RTCP-interworking" in an H.248 "Notify" message to the MGCF. + +The information derived from the RTCP message to be sent to the MGCF is listed in table E.4.2.8.2.1. Information elements in table E.4.2.8.2.1 shall only be sent if the corresponding RTCP message has been received. + +Table E.4.2.8.2.1: RTCP information elements to be notified over Mn + +| RTCP message | Information elements transported over Mn interface | Remarks | +|-----------------------------------------------------------------|----------------------------------------------------|--------------------------------------------------------------------------------------------| +| Picture Loss Indication (PLI) ([109]) | UpdatePicture | | +| Temporary Maximum Media Stream Bit Rate Request (TMMBR) ([110]) | MaxBitRate | This information indicates the maximum media stream bit rate as received within the TMMBR. | + +Figure E.4.2.8.2.2.1 shows examples of interactions between RTCP and H.245 for IM CN subsystem originated feedback on the quality of the media distribution. + + + +``` + +sequenceDiagram + participant IMS + participant IM_MGW as IM MGW + participant MGCF + participant CS_Network as CS Network + + Note over IM_MGW, MGCF: CALL IN ACTIVE STATE + + MGCF->>IM_MGW: 1. H.248: MOD.req [C=C1, T=T1..., Event=RTCP-Interworking] + IM_MGW-->>MGCF: 2. H.248: MOD.resp + IMS->>IM_MGW: 3. receive RTCP feedback messages + IM_MGW-->>IMS: 4. send RTCP feedback Ack messages + IM_MGW->>MGCF: 5. H.248: Notify.req [C=C1, T=T1, Event=RTCP-Interworking] + MGCF-->>IM_MGW: 6. H.248: Notify.resp + MGCF->>CS_Network: 7. send H.245 message + CS_Network-->>MGCF: 8. receive H.245 message response + +``` + +Sequence diagram showing interactions between IMS, IM MGW, MGCF, and CS Network for RTCP feedback. The diagram illustrates a call in an active state with various signaling messages exchanged between the components. + +Figure E.4.2.8.2.2.1: Interactions between RTCP and H.245 for IM CN subsystem originated RTCP feedback on the quality of the media distribution + +In signal 1, the MGCF requests the IM-MGW to detect received RTCP feedback message from the IMS side and notify the feedback information elements to the MGCF when the interworking is required. To request the IM-MGW to detect and notify these feedback information elements, the MGCF shall send the "RTCP-interworking" H.248 event to the IM-MGW. The event may be indicated through an H.248 MOD command. + +In signal 3, the IM-MGW receives a RTCP feedback message from the IMS side. + +In signal 5, the IM-MGW notifies the feedback information elements from RTCP message to the MGCF. + +In signal 7, the MGCF send the corresponding H.245 message to the CS side to request for the media adaption. + +##### E.4.2.8.3 CS network originated H.245 messages + +Figure E.4.2.8.3.2.1 shows examples of interactions between H.245 and RTCP for CS network originated feedback on the quality of the media distribution. + + + +``` + +sequenceDiagram + participant IMS + participant IM MGW + participant MGCF + participant CS Network + + Note left of IM MGW: CALL IN ACTIVE STATE + CS Network->>MGCF: 1. receive H.245 message to feedback on the quality of the data distribution + MGCF-->>CS Network: 2. send H.245 message response + MGCF->>IM MGW: 3. H.248: MOD.req [C=C1, T=T1..., signal=H.245-Interworking] + IM MGW-->>MGCF: 4. H.248: MOD.resp + IM MGW->>IMS: 5. send RTCP feedback message + IMS-->>IM MGW: 6. receive RTCP feedback Ack message + +``` + +Sequence diagram showing interactions between IMS, IM MGW, MGCF, and CS Network for H.245 feedback. The diagram starts with a 'CALL IN ACTIVE STATE' message from CS Network to IM MGW. Then, MGCF receives an H.245 feedback message from CS Network (1), sends a response (2), and requests an RTCP message from IM MGW (3). IM MGW responds (4), sends the RTCP feedback message to IMS (5), and receives an RTCP feedback Ack message from IMS (6). + +**Figure E.4.2.8.3.2.1: Interactions between H.245 and RTCP for CS network originated H.245 feedback on the quality of the media distribution** + +In signal 1, the MGCF receives an H.245 feedback message from the CS side. + +In signal 3, the MGCF requests the IM\_MGW to send an RTCP message provisioning the signal "H.245 interworking" with parameters identifying information to be transported within this RTCP message. + +In signal 5, the IM-MGW send the corresponding RTCP message to the IMS side to request for the media adaption. + +To request the IM-MGW to send an RTCP message, the MGCF shall send the corresponding information elements listed in table E.4.2.8.3.2.1 as parameters of the "H.245-interworking signal" over the Mn interface. + +**Table E.4.2.8.3.2.1: Feedback information elements to be indicated** + +| RTCP message | Information elements transported over Mn interface | Remarks | +|-----------------------------------------------------------------|----------------------------------------------------|-------------------------------------------------------------------------------------------| +| Picture Loss Indication (PLI) ([109]) | UpdatePicture | | +| Temporary Maximum Media Stream Bit Rate Request (TMMBR) ([110]) | MaxBitRate | This information indicates the maximum media stream bit rate to be sent within the TMMBR. | + +### E.4.3 Mn Signalling procedures + +#### E.4.3.1 Overview + +This clause describes the logical signalling procedures (i.e. message identifiers are not part of the protocol) between the MGCF and IM-MGW. The procedures within this clause are intended to be implemented using the standard H.248 procedure as defined in ITU recommendation H.248.1 [2] with appropriate parameter combinations. + +#### E.4.3.2 Add Multiplex Termination + +This procedure is used to add a termination to multiplex/demultiplex H.223. This procedure containing the MuxDescriptor with H.223 value enables the IM-MGW to start the H.324 Multiplexing Level Negotiation. + +**Table E.4.3.2.1: Add Multiplex Termination Procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------|-----------|---------------------------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Add Multiplex Termination | MGCF | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element requests a new termination | +| | | MuxDescriptor | M | This information element indicates that data multiplexed according to H.223 shall be received, and from which termination. | +| | | Notify Termination Heartbeat | M | This information element requests termination heartbeat indications | +| | | Notify Released Bearer | O | This information element requests a notification of a released bearer. | +| | | Incoming H.245 message Notification Request | M | This Event shall indicate that a Notification about H.245 messages received by the IM-MGW is requested by the MGCF | +| | | MONA Preferences | O | This information element requests the MGW to start a MONA negotiation and provisions MONA preferences to be indicated by the IM-MGW, encoded as described in clause K.6 of ITU-T H.324 [81] | +| | | MONA Preference Reception | O | This information element requests a notification of the reception of the first MONA preference message. | +| | | MONA Preference Completed | O | This information element requests a notification of the reception of the first MONA preference message with indication that the MONA preference negotiation is completed. | +| | | Legacy Detected | O | This information element requests a notification of a legacy interworking condition. The Event Descriptor also embeds a signal descriptor including an H.245 message out signal which shall be send when legacy interworking is detected | +| | | MPC Reception | O | This information element requests a notification of the reception of the first MONA preference message with attached MPC. | +| | | SPC Reception | O | This information element requests a notification of the reception of a MONA preference message with attached SPC. | +| | | Incoming Multiplex Table | O | This information element indicates the value of the H.245 MultiplexEntrySend message and allows the MGW to identify incoming H.223 MUX PDUs of the channel types given in the table. | +| | | MPC Mux Code | O | This information element requests the MGW to send available media in MPCs and indicates the channel type to use for sending media. | +| Add Multiplex Termination Ack | IM-MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the new termination where the command was executed. | + +#### E.4.3.3 Configure Multiplex Termination + +This procedure is used to configure a termination to multiplex/demultiplex H.223. It is also used to exclude some of the outgoing MPC channel types due to the MONA Preference received from the peer. + +**Table E.4.3.3.1: Configure Multiplex Termination Procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Configure Multiplex Termination | MGCF | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the termination | +| | | Remote H223 Capability | O | This information element indicates the remote H223 capabilities, as received by the MGCF. The element shall not be included if the MPC Mux Code IE is included. | +| | | Incoming Multiplex Table | O | This information element indicates the value of the H245 MultiplexEntrySend message, as received by the MGCF from the remote H.245 peer. Either this element or the MPC Mux Code IE shall be included. | +| | | Outgoing Multiplex Table | O | This information element indicates the value of the H245 MultiplexEntrySend message, as sent by the MGCF towards the remote H.245 peer. Either this element or the MPC Mux Code IE shall be included. | +| | | MPC Mux Code | O | This information element requests the MGW to continue sending available media in MPC and indicates the channel type to use for sending media. It is used in this procedure only to restrict the list of channel types indicated previously in the Add Multiplex Termination procedure. Either this element or the Incoming and Outgoing Multiplex Table elements shall be included. | +| Configure Multiplex Termination Ack | IM-MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | + +#### E.4.3.4 Signal H245 Message + +This procedure is used to send a H245 message to the IM-MGW that the IM-MGW shall forward towards the CS side within H.223. + +**Table E.4.3.4.1: Signal H245 Message Procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------| +| Signal H245 Message | MGCF | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the termination | +| | | Signal | M | This information element indicates the signal to request forwarding of a H245 message towards the CS side within H.223 | +| | | H.245 message | M | This information element indicates the H.245 message to be forwarded | +| Signal H245 Message Ack | IM-MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | + +#### E.4.3.5 Notify H245 Message + +This procedure is used by the IM-MGW to notify the MGCF that the IM-MGW has received a H245 message from the CS side within H.223. + +**Table E.4.3.5.1: Notify H245 Message Procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------| +| Notify H245 Message | IM-MGW | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the termination | +| | | Event | M | This information element indicates the event to indicate that a H245 message has been received from the CS side within H.223 | +| | | H.245 message | M | information element indicates the received H.245 message | +| Notify H245 Message Ack | MGCF | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | + +#### E.4.3.6 Notify MONA Preference Reception + +This procedure is used by the IM-MGW to notify the MGCF that the IM-MGW has received the first MONA preference Message from the CS side. + +**Table E.4.3.6.1: Notify MONA Preference Reception Procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------|-----------|--------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------| +| Notify H245 Message | IM-MGW | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the termination | +| | | Event | M | This information element indicates the event to indicate that a MONA Preference Message has been received | +| | | MONA Preferences | M | This information element indicates the received MONA preference message | +| Notify H245 Message Ack | MGCF | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | + +#### E.4.3.7 Notify MONA Preference Completed + +This procedure is used by the IM-MGW to notify the MGCF that the IM-MGW has received the first MONA preference Message with indication that the MONA preference negotiation is completed. + +**Table E.4.3.7.1: Notify MONA Preference Completed Procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------|-----------|--------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Notify H245 Message | IM-MGW | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the termination | +| | | Event | M | This information element indicates the event to indicate that the first MONA preference Message with indication that the MONA preference negotiation is completed received | +| Notify H245 Message Ack | MGCF | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | + +#### E.4.3.8 Signal SPC + +This procedure is used to send a H245 message to the IM-MGW that the IM-MGW shall forward towards the CS side using the SPC, i.e. as attachment to MONA preference messages. + +**Table E.4.3.8.1: Signal SPC Procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Signal H245 Message | MGCF | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the termination | +| | | Signal | M | This information element indicates the signal to request forwarding of a H245 message towards the CS side using the SPC, i.e. as attachment to MONA preference messages | +| | | H.245 message | M | This information element indicates the H.245 message to be forwarded | +| Signal H245 Message Ack | IM-MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | + +#### E.4.3.9 Notify SPC + +This procedure is used by the IM-MGW to notify the MGCF that the IM-MGW has received a H245 message from the CS side in SPC PDUs attached to MONA preference messages. + +**Table E.4.3.9.1: Notify SPC Procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Notify H245 Message | IM-MGW | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the termination | +| | | Event | M | This information element indicates the event to indicate that a H245 message has been received from the CS side in SPC PDUs attached to MONA preference messages | +| | | H.245 message | M | information element indicates the received H.245 message | +| Notify H245 Message Ack | MGCF | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | + +#### E.4.3.10 Notify MPC + +This procedure is used by the IM-MGW to notify the MGCF that the IM-MGW has received the first MONA preference message with attached MPC from the CS side. + +**Table E.4.3.10.1: Notify MPC Procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------|-----------|--------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| Notify H245 Message | IM-MGW | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the termination | +| | | Event | M | This information element indicates the event to indicate that the first MONA preference message with attached MPC has been received. | +| | | MuxCode | M | information element that indicates the received Channel Type | +| Notify H245 Message Ack | MGCF | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | + +#### E.4.3.11 Notify Detection of Legacy Interworking + +This procedure is used by the IM-MGW to notify the MGCF that the IM-MGW detects a legacy interworking condition that causes it to abort MONA procedures. + +**Table E.4.3.11.1: Notify Detection of Legacy Interworking Procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------| +| Notify H245 Message | IM-MGW | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the termination | +| | | Event | M | This information element indicates the event to indicate that a legacy interworking condition has been detected. | +| Notify H245 Message Ack | MGCF | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | + +#### E.4.3.12 Request RTCP-Interworking + +This procedure is used by the MGCF to request the IM-MGW to detect the RTCP feedback message on the quality of the media distribution requiring interworking. + +**Table E.4.3.12.1: Request RTCP-Interworking** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------|-----------|--------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Request RTCP-Interworking | MGCF | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates an existing | +| | | RTCPfilter | M | This information element provides one or several bit pattern(s) for bits 3-15 of an RTCP packet. Information from RTCP packets that match those patterns shall be notified to the MGCF. | +| | | RTCP-Interworking | M | This information element requests a notification about information derived from the incoming RTCP packet types denoted by RTCPfilter. | +| Request RTCP-Interworking Ack | IM-MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the new termination where the command was executed. | + +#### E.4.3.13 Notify RTCP-Interworking + +This procedure is used by the IM-MGW to notify the MGCF the feedback information elements when the IM-MGW detects a RTCP feedback message on the quality of the media distribution requiring interworking. + +**Table E.4.3.13.1: Notify of RTCP-Interworking** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------------|-----------|--------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Notify RTCP-Interworking | IM-MGW | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the termination | +| | | UpdatePicture | C | This information element shall be included upon reception of a RTCP PLI message. It indicates the request of sending of full intra-pictures. | +| | | MaxBitRate | C | This information element shall be included upon reception of a RTCP TMMBR message. It shall contain the bandwidth as indicated in the RTCP TMMBR message excluding the overhead indicated in the RTCP TMMBR message. | +| Notify RTCP-Interworking Ack | MGCF | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | + +#### E.4.3.14 Signal-H.245-Interworking + +This procedure is used by the MGCF to indicate the IM-MGW the feedback information elements when a H.245 feedback message on the quality of the media distribution requiring interworking is received. + +**Table E.4.3.14.1: Signal H.245-Interworking** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------|-----------|--------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Signal H.245-Interworking | MGCF | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the termination | +| | | UpdatePicture | C | This information element indicates the request to send a RTCP PLI message. | +| | | MaxBitRate | C | This information element indicates the request to send a RTCP TMBR message. It shall contain the bandwidth as indicated in the RTCP TMMBR message excluding the overhead indicated in the RTCP TMMBR message. | +| Signal H.245-Interworking Ack | IM-MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | + +#### E.4.3.15 Stop MPC + +This procedure is used by the MGC to indicate to the MG that it is no longer allowed to send MPC media encapsulated in MONA Preference messages and that it shall stop MPC detection. + +**Table E.4.3.15.1: Stop MPC** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------------| +| Stop MPC | MGCF | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the termination | +| | | Stop MPC Reception | M | This information element indicates that the reception of MPC encapsulated in MONA Preference Messages shall be stopped. | +| | | Stop MPC Sending | M | This information element requests that the sending of the MPC shall be stopped. | +| Stop MPC Ack | IM-MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | + +#### E.4.3.16 Stop SPC + +This procedure is used by the MGC to indicate to the MG that it is no longer allowed to send MPC media encapsulated in MONA Preference messages and that it shall stop SPC detection. + +**Table E.4.3.16.1: Stop MPC** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------|-----------|--------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| Stop SPC | MGCF | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the termination | +| | | Stop SPC Sending | M | This information element requests that the sending of SPC encapsulated in MONA Preference messages shall be stopped. | +| | | Stop SPC Detection | M | This information element requests that the detection of received SPC encapsulated in MONA Preference Message shall be stopped. | +| Stop SPC Ack | IM-MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | + +#### E.4.3.17 Stop MONA Negotiation + +This procedure is used by the MGC to request the MG to stop all MONA negotiation related procedures. + +**Table E.4.3.17.1: Stop MONA Negotiation** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------|-----------|--------------------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Stop MONA Negotiation | MGCF | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the termination | +| | | Stop MONA Preference Message Sending | M | This information element requests that the sending of MONA Preference messages be stopped. | +| | | Stop MONA Detection | M | This information element requests that the detection of first MONA Preference Message and of the MONA negotiation completion be stopped. | +| | | Stop SPC Sending | C | This information element requests that the sending of SPC encapsulated in MONA Preference messages be stopped. Required only if SPC sending was previously configured. | +| | | Stop SPC Detection | C | This information element requests that the detection of received SPC encapsulated in MONA Preference Message be stopped. Required only if SPC reception was previously configured. | +| | | Stop MPC Reception | C | This information element indicates that the reception of MPC encapsulated in MONA Preference Messages shall be stopped. Required only if MPC reception was previously configured. | +| | | Stop MPC Sending | C | This information element requests that the sending of the MPC shall be stopped. Required only if MPC sending was previously configured. | +| Stop MONA Negotiation Ack | IM-MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | + +# Annex F (normative): PSTN XML Scheme + +## F.1 Scope + +This clause defines the PSTN XML Schema to be used for providing the BearerCapability, Low Layer Compatibility, High Layer Compatibility and Progress indicator embedded as body in SIP messages. + +The support of this PSTN XML Schema is a network option. + +## F.2 MIME type + +The XML schema defined in the present Annex is registered at IANA as "application/vnd.etsi.pstn+xml" MIME type. + +If the XML scheme is embedded in SIP messages as body, the Content-Type header shall be set to "application/vnd.etsi.pstn+xml" and the Content-Disposition shall be set to "signal" with the "handling" parameter set to "optional". + +## F.3 XML Schema definition + +``` + +
If NOA is "international number" then set to CC + NDC + SN. | +| Privacy header field, or Privacy header field escaped in the hi-entry above identified. (NOTE 2). | "history" or "session" or "header" | APRI | "presentation restricted" | +| | Privacy header field absent or "none" | | "presentation allowed" | + +NOTE 1: If the hi-targeted-to-uri is a SIP URI and does not contain "user=phone", then mapping to called IN number is impossible; therefore, there is no need to generate called IN number. + +NOTE 2: It is possible that an entry of the History-Info header field itself is marked as restricted or the whole History-Info header field. + +NOTE 3: The hi-target-param parameter set to "mp" as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed and shall appear in this hi-targeted-to-uri. Due to backward compatibility rules the hi-target-param may not appear in each concerned hi-entry; so that the identification of the hi-entry shall rely on the cause-param value. + +**Table L.1.2: Mapping of History-Info header field to original called IN number** + +| Source SIP header field and component | Source Component value | original called IN number | Derived value of parameter field | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Numbering plan indicator | "ISDN (Telephony) numbering plan (Recommendation E.164)" | +| hi-targeted-to-uri of the hi-entry with a hi-index that matches the first hi-entry with a cause-param URI parameter with the value "380" defined in IETF RFC 8119 [148] and a mp-param header field parameter (NOTE 4); the global number portion of the hi-targeted-to-uri is assumed to be in form "+" CC + NDC + SN (NOTE 2). | CC | Nature of address indicator | If CC is equal to the country code of the country where I-MGCF is located AND the next ISUP node is located in the same country, then set to "national (significant) number" else set to "international number" | +| | CC, NDC, SN | Address signals | If NOA is "national (significant) number" then set to NDC + SN.
If NOA is "international number" then set to CC + NDC + SN | +| Privacy header field, or Privacy header field escaped in the hi-entry above identified (NOTE 3). | "history" or "session" or "header" | APRI | "presentation restricted" | +| | Privacy header field absent or "none" | | "presentation allowed" | +| NOTE 1: The original called IN number is generated only when there are more than two hi-entries having a cause URI parameter set to the value defined in IETF RFC 8119 [148]. | | | | +| NOTE 2: If the hi-targeted-to-uri is a SIP URI and does not contain "user=phone", then mapping to original called IN number is impossible; therefore, there is no need to generate original called IN number. | | | | +| NOTE 3: It is possible that an entry of the History-Info header field itself is marked as restricted or the whole History-Info header field. | | | | +| NOTE 4: The hi-target-param parameter set to "mp" as defined in IETF RFC 7044 [91] indicates that the target of the Request-URI was changed and shall appear in this hi-targeted-to-uri. Due to backward compatibility rules the hi-target-param may not appear in each concerned hi-entry; so that the identification of the hi-entry shall rely on the cause-param value. | | | | + +## L.2 Interworking ISUP to SIP + +The O-MGCF may perform the following procedure based on the operator policy, if the History-Info header field is supported in the IMS network. + +When receiving the called IN number parameter (and the original called IN number parameter) in the incoming IAM, the O-MGCF may include the History-Info header field in the outgoing initial INVITE request as shown in table L.2.1, table L.2.2 and table L.2.3. + +The O-MGCF should first create hi-entries for the original called IN number and the called IN number and then those for the original called number and the redirecting number. + +NOTE: It is operator specific.if an IN number is used as a first dialled number and call diversions are at the later position (it is often forbidden to have a call diversion towards an IN service number) or the contrary. + +Table L.2.1: Mapping of original called IN number to History-Info header field + +| ISUP Parameter | Derived value of parameter field | SIP component | Value | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IAM | | Initial INVITE request | | +| Original called IN number | | History-Info header field | hi-targeted-to-uri of the first created hi-entry. | +| Nature of address indicator | "national (significant) number" | hi-targeted-to-uri | Add CC (of the country where the O-MGCF is located) to address signals of original called IN number, then map to user portion of URI scheme used.
Addr-spec
"+" CC NDC SN mapped to user portion of URI scheme used. | +| | "international number" | | Map complete address signals of original called IN number to user portion of URI scheme used. | +| Address signals | If NOA is "national (significant) number" then the format of the address signals is NDC + SN.
If NOA is "international number" then the format of the address signals is CC + NDC + SN. | hi-targeted-to-uri | "+" CC NDC SN mapped to user portion of URI scheme used. | +| APRI | "presentation restricted" | Privacy header field escaped in hi-targeted-to-uri corresponding to original called IN number | "history" | +| | "presentation allowed" | | Privacy header field absent or "none" | +| | | hi-index | "index=1" | + +Table L.2.2: Mapping of called IN number to History-Info header field + +| ISUP Parameter | Derived value of parameter field | SIP component | Value | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IAM | | Initial INVITE request | | +| Called IN number | | History-Info header field | If mapping of original called IN number is performed, then hi-targeted-to-uri of the second created hi-entry.
Otherwise, hi-targeted-to-uri of the first created hi-entry. | +| Nature of address indicator | "national (significant) number" | hi-targeted-to-uri | Add CC (of the country where the O-MGCF is located) to address signals of called IN number, then map to user portion of URI scheme used.
Addr-spec
"+" CC NDC SN mapped to user portion of URI scheme used. | +| | "international number" | | Map complete address signals of called IN number to user portion of URI scheme used. | +| Address signals | If NOA is "national (significant) number" then the format of the address signals is NDC + SN.
If NOA is "international number" then the format of the address signals is CC + NDC + SN. | hi-targeted-to-uri | "+" CC NDC SN mapped to user portion of URI scheme used. | +| APRI | "presentation restricted" | Privacy header field escaped in hi-targeted-to-uri corresponding to called IN number | "history" | +| | "presentation allowed" | | Privacy header field absent or "none" | +| | | hi-targeted-to-uri; cause-param URI parameter, as defined in IETF RFC 8119 [148]. | If mapping of original called IN number is performed, then set to "380".
Otherwise, no mapping is performed. | +| | | hi-index and hi-target-param | If mapping of original called IN number is performed, then set to "index=1.1" and "mp=1".
Otherwise, set to "index=1" and no mp-param is created. | + +Table L.2.3: Mapping of called party number to History-Info header field + +| ISUP Parameter | Derived value of parameter field | SIP component | Value | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IAM | | Initial INVITE request | | +| Called party number | | History-Info header field | If mapping of original called IN number is performed, then hi-targeted-to-uri of the third created hi-entry.
Otherwise, hi-targeted-to-uri of the second created hi-entry. | +| Nature of address indicator | "national (significant) number" | hi-targeted-to-uri | Add CC (of the country where the MGCF is located) to address signals of called party number, then map to user portion of URI scheme used.
Addr-spec
"+" CC NDC SN mapped to user portion of URI scheme used. | +| | "international number" | | Map complete address signals of called party number to user portion of URI scheme used. | +| Address signals | If NOA is "national (significant) number" then the format of the address signals is NDC + SN.
If NOA is "international number" then the format of the address signals is CC + NDC + SN. | hi-targeted-to-uri | "+" CC NDC SN mapped to user portion of URI scheme used. | +| | | hi-targeted-to-uri; cause-param URI parameter, as defined in IETF RFC 8119 [148]. | "380" | +| | | hi-index and hi-target-param | If both original called IN number and called IN number are mapped to hi-entries, then set to "index=1.1.1" and "mp=1.1".
If original called IN number is not mapped, but called IN number is mapped to hi-entry, then set to "index=1.1" and "mp=1". | + +# --- Annex M (informative): Change history + +| Change history | | | | | | | | +|-----------------------|--------------|-----------------|-----------|------------|--------------------------------------------------------------------------|------------------------|------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2014-12 | CT-66 | CP-140923 | 0830 | 2 | Interworking of Called IN number and original Called IN number | 12.5.0 | 13.0.0 | +| 2015-03 | CT-67 | CP-150130 | 0842 | | ICS call: reference correction | 13.0.0 | 13.1.0 | +| 2015-03 | CT-67 | CP-150130 | 0843 | | Announcement suppression for IMS hold request | 13.0.0 | 13.1.0 | +| 2015-03 | CT-67 | CP-150130 | 0845 | | Note 4 in Table 3 for mapping to CLI parameter | 13.0.0 | 13.1.0 | +| 2015-03 | CT-67 | CP-150130 | 0846 | | Appearance of Redirection Number Restriction parameter | 13.0.0 | 13.1.0 | +| 2015-03 | CT-67 | CP-150130 | 0861 | 1 | Reference update for UUSIW | 13.0.0 | 13.1.0 | +| 2015-03 | CT-67 | CP-150097 | 0855 | 2 | Correction of APRI Mapping for Generic Number | 13.0.0 | 13.1.0 | +| 2015-03 | CT-67 | CP-150097 | 0849 | 1 | Correction to attribute "a=inactive" in initial INVITE | 13.0.0 | 13.1.0 | +| 2015-03 | CT-67 | CP-150130 | 0847 | | Inclusion of RFC7044 | 13.0.0 | 13.1.0 | +| 2015-03 | CT-67 | CP-150129 | 0850 | 2 | Reference update: draft-mohali-dispatch-cause-for-service-number | 13.0.0 | 13.1.0 | +| 2015-03 | CT-67 | CP-150121 | 0864 | 2 | Adding support for EVS codec | 13.0.0 | 13.1.0 | +| 2015-06 | CT-68 | CP-150336 | 0873 | - | Reference Update: RFC7462 (alert-info urns) | 13.1.0 | 13.2.0 | +| 2015-06 | CT-68 | CP-150334 | 0879 | 4 | Handling of 415 response for multipart MIME | 13.1.0 | 13.2.0 | +| 2015-06 | CT-68 | CP-150358 | 0880 | 1 | Reference update: draft-mohali-dispatch-cause-for-service-number | 13.1.0 | 13.2.0 | +| 2015-06 | CT-68 | CP-150335 | 0886 | 2 | User-to-user information interworking | 13.1.0 | 13.2.0 | +| 2015-06 | CT-68 | CP-150364 | 0887 | 1 | Hold/Resume request indication | 13.1.0 | 13.2.0 | +| 2015-06 | CT-68 | CP-150359 | 0888 | 1 | Adding support for the EVS codec over UMTS CS | 13.1.0 | 13.2.0 | +| 2015-06 | CT-68 | CP-150338 | 0893 | 1 | APRI Mapping for multiple Privacy header values | 13.1.0 | 13.2.0 | +| 2015-06 | CT-68 | CP-150351 | 0895 | - | Bearer Termination in Acknowledgements | 13.1.0 | 13.2.0 | +| 2015-06 | CT-68 | CP-150334 | 0901 | 3 | URI scheme in History-Info header field | 13.1.0 | 13.2.0 | +| 2015-06 | CT-68 | CP-150364 | 0902 | - | CDIV - miscellaneous corrections | 13.1.0 | 13.2.0 | +| 2015-06 | CT-68 | CP-150353 | 0904 | 1 | EVS corrections | 13.1.0 | 13.2.0 | +| 2015-09 | CT-69 | CP-150470 | 0912 | 1 | Indication of "no backward early media" for ICS call | 13.2.0 | 13.3.0 | +| 2015-09 | CT-69 | CP-150479 | 0913 | 1 | Reference update: draft-mohali-dispatch-cause-for-service-number | 13.2.0 | 13.3.0 | +| 2015-09 | CT-69 | CP-150462 | 0920 | 2 | Sending of IAM at I-MGCF for SIP-BICC-interworking | 13.2.0 | 13.3.0 | +| 2015-12 | CT-70 | CP-150667 | 0914 | 8 | Stage 2 Mn supporting SDP capability negotiation | 13.3.0 | 13.4.0 | +| 2015-12 | CT-70 | CP-150656 | 0923 | - | HOLD request from CS side: suspending media to the conference | 13.3.0 | 13.4.0 | +| 2015-12 | CT-70 | CP-150657 | 0924 | 2 | Reference update: draft-mohali-dispatch-cause-for-service-number | 13.3.0 | 13.4.0 | +| 2015-12 | CT-70 | CP-150648 | 0925 | 3 | Updates to MGCF and IM-MGW to support EVS over UMTS CS | 13.3.0 | 13.4.0 | +| 2015-12 | CT-70 | CP-150670 | 0931 | 2 | URI scheme in History-Info header field | 13.3.0 | 13.4.0 | +| 2015-12 | CT-70 | CP-150655 | 0933 | 1 | ICS call: removal of non-interworking requirement | 13.3.0 | 13.4.0 | +| 2015-12 | CT-70 | CP-150796 | 0940 | 2 | Correcting the clause title and the NOTE for interworking of Request-URI | 13.3.0 | 13.4.0 | +| 2015-12 | CT-70 | CP-150670 | 0946 | 1 | Removal for the unsupported SIPS URI scheme | 13.3.0 | 13.4.0 | +| Change history | | | | | | | | +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------|--------| +| 2016-03 | CT#71 | CP-160102 | 0954 | 2 | B | Support of enhanced bandwidth negotiation mechanism for MTSI sessions | 13.5.0 | +| 2016-03 | CT#71 | CP-160112 | 0955 | 1 | B | Resolution of Editor's notes on EVS over UMTS CS | 13.5.0 | +| 2016-03 | CT#71 | CP-160105 | 0961 | 1 | F | Correction for the SIP-ISUP interworking parameter | 13.5.0 | +| 2016-03 | CT#71 | CP-160105 | 0967 | 2 | F | Clarification on the setting of the SIP message components | 13.5.0 | +| 2016-03 | CT#71 | CP-160105 | 0968 | - | F | Removal of references to TS 26.235 and TS 26.236 | 13.5.0 | +| 2016-03 | CT#71 | CP-160111 | 0970 | 2 | A | Corrections to EVS AMR-WB IO mode-change-capability MIME parameter handling | 13.5.0 | +| 2016-06 | CT#72 | CP-160257 | 0953 | 5 | A | Interworking of History-Info Header Field when Original Called Number is not present | 13.6.0 | +| 2016-06 | CT#72 | CP-160256 | 0974 | - | A | Mapping P-Access-Network-Info header to Location Number, clarifications | 13.6.0 | +| 2016-06 | CT#72 | CP-160272 | 0976 | 3 | F | Clarification on counting diverting entries | 13.6.0 | +| 2016-06 | CT#72 | CP-160261 | 0977 | - | F | Update ref to draft-mohali-dispatch-cause-for-service-number-06 | 13.6.0 | +| 2016-06 | CT#72 | CP-160260 | 0975 | - | F | Correcting name of "network-provided" parameter | 14.0.0 | +| 2016-09 | CT#73 | CP-160451 | 0978 | 1 | F | Correction for the SIP-ISUP interworking regarding redirection counter | 14.1.0 | +| 2016-09 | CT#73 | CP-160450 | 0980 | 1 | A | Correction on mapping from 3GPP EVS to UMTS EVS codec | 14.1.0 | +| 2016-09 | CT#73 | CP-160451 | 0981 | 1 | F | Clarification on handling of P-Early-Media header | 14.1.0 | +| 2016-09 | CT#73 | CP-160449 | 0983 | 1 | A | Updated ref to draft-mohali-dispatch-cause-for-service-number-07 | 14.1.0 | +| 2016-12 | CT#74 | CP-160635 | 0990 | 1 | F | Unknown User Identity for Call Diversion | 14.2.0 | +| 2016-12 | CT#74 | CP-160631 | 0991 | 2 | D | Correction of Calculation of Redirection Counter | 14.2.0 | +| 2016-12 | CT#74 | CP-160624 | 0993 | 1 | A | Updated ref to draft-mohali-dispatch-cause-for-service-number-09 | 14.2.0 | +| 2016-12 | CT#74 | CP-160617 | 0995 | 2 | A | Updates to EVS over CS aspects | 14.2.0 | +| 2016-12 | CT#74 | CP-160631 | 0996 | 1 | F | Correction of Calculation of Redirection Counter | 14.2.0 | +| 2016-12 | CT#74 | CP-160618 | 0999 | 1 | A | Handling of dtx and dtx-recv MIME parameters in SDP offer/answer | 14.2.0 | +| 2016-12 | CT#74 | CP-160631 | 1000 | - | D | Update of subclause 9.2.3.4.2 | 14.2.0 | +| 2017-03 | CT#75 | CP-170080 | 1005 | 1 | A | Update ref to draft-mohali-dispatch-cause-for-service-number | 14.3.0 | +| 2017-03 | CT#75 | CP-170085 | 1006 | - | B | Support of "Calling number verification" | 14.3.0 | +| 2017-06 | CT#76 | CP-171130 | 1007 | 1 | B | Addition of the location parameter | 14.4.0 | +| 2017-06 | CT#76 | CP-171131 | 1009 | - | F | Mapping of additional 4xx response codes for SPECTRE | 14.4.0 | +| 2017-06 | CT#76 | CP-171124 | 1011 | 1 | A | Reference Update RFC8119" | 14.4.0 | +| 2017-06 | CT#76 | CP-171131 | 1012 | 1 | F | Reference update: draft-ietf-sipcore-status-unwanted | 14.4.0 | +| 2017-06 | CT#76 | CP-171131 | 1013 | - | F | Reference update: draft-ietf-stir-rfc4474bis | 14.4.0 | +| 2017-09 | CT#77 | CP-172045 | 1014 | 1 | F | Reference Update for the ISUP location parameter | 14.5.0 | +| 2017-09 | CT#77 | CP-172049 | 1015 | - | F | Reference update from draft-ietf-sipcore-status-unwanted-06 to RFC 8197 | 14.5.0 | +| 2017-09 | CT#77 | CP-172050 | 1016 | 1 | F | "user=phone" URI parameter for SIP URIs in the SIP P-Asserted-Identity header field | 15.0.0 | +| 2017-12 | CT#78 | CP-173099 | 1018 | 1 | A | Reference Update for the ISUP location parameter | 15.1.0 | +| 2017-12 | CT#78 | CP-173099 | 1020 | - | A | Reference Update for the ISUP location parameter | 15.1.0 | +| 2018-03 | CT#79 | CP-180041 | 1021 | 2 | B | Interworking of Subaddress for user specified type | 15.2.0 | +| 2018-03 | CT#79 | CP-180042 | 1023 | - | A | Reference Update for the ISUP location parameter | 15.2.0 | +| 2018-03 | CT#79 | CP-180044 | 1025 | - | A | Reference update: RFC 8224 | 15.2.0 | +| 2018-06 | CT#80 | CP-181022 | 1026 | - | F | Interwork of Connected subaddress IE carried in ISUP CON message | 15.3.0 | +| 2018-06 | CT#80 | CP-181018 | 1031 | - | A | Correction of the Backward call indicators parameter interworking | 15.3.0 | +| 2018-06 | CT#80 | CP-181016 | 1040 | 1 | B | Providing attestation information | 15.3.0 | +| 2018-09 | CT#81 | CP-182028 | 1042 | 2 | F | Correction of the Interworking of the Redirecting Number | 15.4.0 | +| 2018-09 | CT#81 | CP-182024 | 1044 | - | A | Reference Update for the ISUP Q.850 location parameter | 15.4.0 | +| 2018-12 | CT#82 | CP-183112 | 1053 | - | A | Resolution of Editor's Notes in TS 29.163 | 15.5.0 | +| 2018-12 | CT#82 | CP-183115 | 1045 | 2 | B | New Q850 cause for Call completed elsewhere | 16.0.0 | +| 2019-03 | CT#83 | CP-190122 | 1054 | 1 | F | Correction for the encoding of the INFO message for overlap signalling using the in-dialog method | 16.1.0 | +| 2019-03 | CT#83 | CP-190126 | 1057 | 2 | A | Reference Update for the ISUP Cause Location Parameter Draft | 16.1.0 | +| 2019-06 | CT#84 | CP-191094 | 1061 | - | A | Reference Update for the ISUP Cause Location Parameter Draft | 16.2.0 | +| 2019-09 | CT#85 | CP-192174 | 1058 | 4 | F | Modification on the setting of P-Asserted-Identity header field when a calling party number is not available. | 16.3.0 | +| 2019-09 | CT#85 | CP-192166 | 1064 | 1 | A | Reference Update RFC8606 | 16.3.0 | +| 2019-09 | CT#85 | CP-192161 | 1069 | 1 | A | Mapping of History-Info header field to ISUP Original called number | 16.3.0 | +| 2019-12 | CT#86 | CP-193218 | 1070 | 4 | B | Interworking of Local Number Format in Generic Number | 16.4.0 | +| 2019-12 | CT#86 | CP-193218 | 1071 | - | F | Modification on the condition of setting of the Privacy header field when the call is diverted | 16.4.0 | +| 2019-12 | CT#86 | CP-193218 | 1072 | 1 | B | Interworking of Local Number Format in From Header Field | 16.4.0 | \ No newline at end of file diff --git a/marked/Rel-16/29_series/29165/421fc75480c21e7ebb25756826652367_img.jpg b/marked/Rel-16/29_series/29165/421fc75480c21e7ebb25756826652367_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b058640d94790558855159576ed75d7eb0af808d --- /dev/null +++ b/marked/Rel-16/29_series/29165/421fc75480c21e7ebb25756826652367_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b93050cb1d5f5b37ede0febd7acf612035e437a1b519453c780de25a321cf768 +size 89690 diff --git a/marked/Rel-16/29_series/29165/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Rel-16/29_series/29165/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9e9000a0390b8b0b570cdb3d352ace9e1612e00 --- /dev/null +++ b/marked/Rel-16/29_series/29165/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ffa2a7463bf7bd50936a69115bd878d9a26742c986e0f5fb8cdede63a683d09 +size 49061 diff --git a/marked/Rel-16/29_series/29165/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/29_series/29165/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e5fcbafb4f48a1002979a86d8ab4738ff57018a --- /dev/null +++ b/marked/Rel-16/29_series/29165/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df97d4088ebacdc7dde5b68c3cb0839e6965996e518043e8544a7518223814b0 +size 51055 diff --git a/marked/Rel-16/29_series/29165/d79d33da852cb7bca3e87b400a15c3e8_img.jpg b/marked/Rel-16/29_series/29165/d79d33da852cb7bca3e87b400a15c3e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28dd8f1e64dd7c1848c086744979c3df51ec4a66 --- /dev/null +++ b/marked/Rel-16/29_series/29165/d79d33da852cb7bca3e87b400a15c3e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90dd503267d3e5471a100cfb2e31a60c4a30d56ade3608edeb63f8ce4f25255e +size 17829 diff --git a/marked/Rel-16/29_series/29165/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/29_series/29165/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ebece03f57b733b55a72a8e58c54568f368d4c0 --- /dev/null +++ b/marked/Rel-16/29_series/29165/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba3ac90aa63fb729cdaa64a828d3082135749e6e751fe6f812a68fb0d530fb40 +size 22380 diff --git a/marked/Rel-16/29_series/29165/raw.md b/marked/Rel-16/29_series/29165/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0cb3d837f58697e97b7567b9e93b6b4321313e78 --- /dev/null +++ b/marked/Rel-16/29_series/29165/raw.md @@ -0,0 +1,6009 @@ + + + + +Error: + +2 + +Error: Reference source not found + +# Contents + +| | | +|---------------------------------------------------------------------------------------------------|----| +| Foreword..... | 8 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions, symbols and abbreviations..... | 17 | +| 3.1 Definitions..... | 17 | +| 3.2 Symbols..... | 18 | +| 3.3 Abbreviations..... | 18 | +| 4 Overview..... | 20 | +| 5 Reference model for interconnection between IM CN subsystems..... | 22 | +| 5.1 General..... | 22 | +| 5.2 Functionalities performed by entities at the edge of the network..... | 23 | +| 5.2.1 Interconnection Border Control Function (IBCF)..... | 23 | +| 5.2.2 Transition Gateway (TrGW)..... | 24 | +| 5.3 Identifying II-NNI traversal scenario..... | 24 | +| 5.3.1 General..... | 24 | +| 5.3.2 Mapping of the "iotl" SIP URI parameter to II-NNI traversal scenario..... | 24 | +| 6 Control plane interconnection..... | 25 | +| 6.1 Definition of Inter-IMS Network to Network Interconnection..... | 25 | +| 6.1.1 SIP methods and header fields..... | 25 | +| 6.1.1.1 General..... | 25 | +| 6.1.1.2 SIP methods..... | 25 | +| 6.1.1.3 SIP header fields..... | 26 | +| 6.1.1.3.0 General..... | 26 | +| 6.1.1.3.1 Trust and no trust relationship..... | 26 | +| 6.1.1.3.2 Derivation of applicable SIP header fields from 3GPP TS 24.229 [5]..... | 28 | +| 6.1.1.3.3 Applicability of SIP header fields on a roaming II-NNI..... | 28 | +| 6.1.1.3.4 Applicability of SIP header fields on a non-roaming II-NNI..... | 29 | +| 6.1.1.4 Notations of the codes..... | 29 | +| 6.1.1.5 Modes of signalling..... | 30 | +| 6.1.2 SDP protocol..... | 30 | +| 6.1.2.1 General..... | 30 | +| 6.1.3 Major capabilities..... | 30 | +| 6.1.4 SIP message bodies..... | 36 | +| 6.2 Control Plane Transport..... | 39 | +| 6.2.1 General..... | 39 | +| 6.3 SIP timers..... | 39 | +| 7 User plane Interconnection..... | 41 | +| 7.1 Media and Codec..... | 41 | +| 7.2 User Plane Transport..... | 41 | +| 8 Numbering, Naming and Addressing..... | 42 | +| 8.1 Numbering, Naming and Addressing for SIP message..... | 42 | +| 8.2 Numbering, Naming and Addressing for SDP..... | 43 | +| 9 IP Version..... | 43 | +| 10 Security..... | 43 | +| 11 Charging..... | 43 | +| 11.1 General..... | 43 | +| 11.2 Inter-operator accounting..... | 44 | +| 11.3 Transfer of IP multimedia service tariff information..... | 44 | +| 12 Supplementary services associated with the IMS multimedia telephony communication service..... | 45 | +| 12.1 General..... | 45 | +| 12.2 Malicious Communication IDentification (MCID)..... | 45 | + +| | | | +|---------|----------------------------------------------------------------------------------------------------------|----| +| 12.3 | Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR)..... | 46 | +| 12.4 | Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR)..... | 46 | +| 12.5 | Anonymous Communication Rejection (ACR)..... | 46 | +| 12.6 | Communication DIVersion (CDIV)..... | 47 | +| 12.7 | Communication Waiting (CW)..... | 47 | +| 12.8 | Communication HOLD (HOLD)..... | 47 | +| 12.9 | Message Waiting Indication (MWI)..... | 47 | +| 12.10 | Communication Barring (CB)..... | 48 | +| 12.10.1 | Incoming Communication Barring (ICB)..... | 48 | +| 12.10.2 | Outgoing Communication Barring (OCB)..... | 48 | +| 12.11 | Completion of Communications to Busy Subscriber (CCBS)..... | 48 | +| 12.12 | Completion of Communications by No Reply (CCNR)..... | 49 | +| 12.13 | Explicit Communication Transfer (ECT)..... | 49 | +| 12.13.1 | Consultative and blind transfer..... | 49 | +| 12.13.2 | Assured transfer..... | 50 | +| 12.14 | Customized Alerting Tone (CAT)..... | 50 | +| 12.15 | Customized Ringing Signal (CRS)..... | 50 | +| 12.16 | Closed User Group (CUG)..... | 51 | +| 12.17 | Personal Network Management (PNM)..... | 51 | +| 12.18 | Three-Party (3PTY)..... | 51 | +| 12.19 | Conference (CONF)..... | 52 | +| 12.20 | Flexible Alerting (FA)..... | 52 | +| 12.21 | Announcements..... | 53 | +| 12.21.1 | General..... | 53 | +| 12.21.2 | Providing announcements during the establishment of a communication session..... | 53 | +| 12.21.3 | Providing announcements during an established communication session..... | 53 | +| 12.21.4 | Providing announcements when communication request is rejected..... | 53 | +| 12.22 | Advice Of Charge (AOC)..... | 54 | +| 12.23 | Completion of Communications on Not Logged-in (CCNL)..... | 54 | +| 12.24 | Unstructured Supplementary Service Data (USSD)..... | 55 | +| 12.25 | Enhanced Calling Name (eCNAM)..... | 55 | +| 12.26 | Multi-Device and Multi-Identity (MuD and MiD)..... | 55 | +| 12.26.1 | Multi-Device (MuD)..... | 55 | +| 12.26.2 | Multi-Identity (MiD)..... | 55 | +| 13 | Interoperability of IMS Centralized Services (ICS) over II-NNI..... | 56 | +| 13.1 | General..... | 56 | +| 13.2 | IMS Centralized Services (ICS)..... | 56 | +| 14 | Interoperability of IMS Service Continuity over II-NNI..... | 57 | +| 14.1 | General..... | 57 | +| 14.2 | PS to CS Single Radio Voice Call Continuity (SRVCC) and Single Radio Video Call Continuity (vSRVCC)..... | 57 | +| 14.2.1 | Basic PS to CS SRVCC..... | 57 | +| 14.2.2 | PS to CS SRVCC for calls in alerting phase..... | 57 | +| 14.2.3 | Using the ATCF based architecture..... | 58 | +| 14.2.4 | PS to CS SRVCC for originating calls in pre-alerting phase..... | 58 | +| 14.2.5 | PS to CS SRVCC with the MSC server assisted mid-call feature..... | 58 | +| 14.2.6 | PS to CS SRVCC for terminating calls in pre-alerting phase..... | 58 | +| 14.3 | Inter UE Transfer (IUT)..... | 58 | +| 14.4 | MSC server assisted mid-call feature..... | 59 | +| 14.5 | CS to PS Single Radio Voice Call Continuity (SRVCC)..... | 60 | +| 14.5.1 | Basic CS to PS SRVCC..... | 60 | +| 14.5.2 | CS to PS SRVCC for calls in alerting phase..... | 60 | +| 14.5.3 | CS to PS SRVCC with the assisted mid-call feature..... | 60 | +| 14.6 | PS to CS dual radio voice call continuity (DRVCC)..... | 60 | +| 14.6.1 | Basic PS to CS DRVCC..... | 60 | +| 14.6.2 | PS to CS DRVCC with the assisted mid-call feature..... | 61 | +| 14.6.3 | PS to CS DRVCC for calls in alerting phase..... | 61 | +| 14.6.4 | PS to CS DRVCC for originating calls in pre-alerting phase..... | 61 | +| 14.7 | CS to PS Dual Radio Voice Call Continuity (DRVCC)..... | 61 | +| 14.7.1 | Basic CS to PS DRVCC..... | 61 | + +| | | | +|--------|--------------------------------------------------------------------------------|----| +| 14.7.2 | CS to PS DRVCC with the assisted mid-call feature..... | 62 | +| 14.7.3 | CS to PS DRVCC for calls in alerting phase..... | 62 | +| 14.7.4 | CS to PS DRVCC for originating calls in pre-alerting phase..... | 62 | +| 14.8 | PS to PS access transfer..... | 62 | +| 15 | Presence service..... | 63 | +| 15.0 | General..... | 63 | +| 15.1 | Subscription of presence information..... | 63 | +| 15.2 | Watcher subscribing to Presence List..... | 63 | +| 15.3 | Subscription to Watcher Information..... | 64 | +| 15.4 | Subscription to state changes in XML documents..... | 64 | +| 15.5 | Presence enhancements specified in Open Mobile Alliance (OMA) Release 1.1..... | 64 | +| 15.5.1 | General..... | 64 | +| 15.5.2 | OMA subscription of presence information..... | 64 | +| 15.5.3 | OMA watcher subscribing to Presence List..... | 64 | +| 15.5.4 | OMA subscription to Watcher Information..... | 65 | +| 15.6 | Presence enhancements specified in Open Mobile Alliance (OMA) Release 2.0..... | 65 | +| 15.6.1 | General..... | 65 | +| 15.6.2 | OMA subscription of presence information..... | 65 | +| 15.6.3 | OMA watcher subscribing to Presence List..... | 65 | +| 15.6.4 | OMA subscription to Watcher Information..... | 66 | +| 15.6.5 | Subscription to state changes in XML documents..... | 66 | +| 15.6.6 | Void..... | 66 | +| 15.6.7 | Void..... | 66 | +| 16 | Messaging service..... | 66 | +| 16.1 | General..... | 66 | +| 16.2 | Page-mode messaging..... | 67 | +| 16.4 | Session-mode messaging..... | 67 | +| 16.5 | Session-mode messaging conferences..... | 67 | +| 17 | Optimal Media Routeing..... | 68 | +| 17.1 | General..... | 68 | +| 17.2 | OMR related SDP attributes..... | 68 | +| 17.3 | IP realm names..... | 68 | +| 18 | Inter-UE transfer (IUT)..... | 68 | +| 18.1 | General..... | 68 | +| 18.2 | IUT without establishment of a collaborative session..... | 68 | +| 18.3 | IUT using a collaborative session..... | 69 | +| 18.3.1 | Collaborative session of participants of the same subscription..... | 69 | +| 18.3.2 | Establishment of a collaborative session during session setup..... | 69 | +| 18.3.3 | Assignment and transfer of control of a collaborative session..... | 70 | +| 18.3.4 | Collaborative session of participants of different subscriptions..... | 70 | +| 18.4 | Session replication / media replication..... | 70 | +| 18.4.1 | Pull mode..... | 70 | +| 18.4.2 | Push mode..... | 70 | +| 19 | Roaming Architecture for Voice over IMS with Local Breakout..... | 71 | +| 20 | Delivery of Media Resource Broker address information..... | 71 | +| 21 | Overload control..... | 71 | +| 21.1 | General..... | 71 | +| 21.2 | Feedback based mechanism..... | 72 | +| 21.3 | The load filter mechanism..... | 72 | +| 22 | Delivery of original destination identity..... | 72 | +| 23 | Telepresence using IMS..... | 72 | +| 24 | Barring of premium rate numbers..... | 73 | +| 25 | P-CSCF restoration..... | 73 | +| 25.1 | General..... | 73 | +| 25.2 | PCRF or PCF based P-CSCF restoration..... | 73 | + +| | | | +|----------|-------------------------------------------------------------------------------------------|----| +| 25.3 | HSS or UDM/HSS based P-CSCF restoration..... | 73 | +| 26 | Resource sharing..... | 73 | +| 27 | Service access number translation..... | 74 | +| 28 | Mission critical services..... | 74 | +| 28.1 | General..... | 74 | +| 28.2 | Interoperability of mission critical services for communication over II-NNI..... | 75 | +| 28.2.1 | Mission Critical services session establishment..... | 75 | +| 28.2.2 | MBMS transmission usage and location procedures..... | 76 | +| 28.2.3 | Affiliation procedure..... | 77 | +| 28.2.3.1 | General..... | 77 | +| 28.2.3.2 | Mandatory mode..... | 77 | +| 28.2.3.3 | Negotiated mode..... | 78 | +| 28.2.4 | Conference event package subscription..... | 78 | +| 28.2.5 | Mission critical services settings..... | 78 | +| 28.2.6 | Registration procedures..... | 79 | +| 28.2.7 | Group regrouping..... | 79 | +| 28.2.8 | Signalling plane messages for mission critical data..... | 80 | +| 28.2.9 | Functional alias management procedure..... | 80 | +| 29 | Calling number verification using signature verification and attestation information..... | 80 | +| 30 | IMS emergency service..... | 81 | +| 30.1 | IMS emergency registration..... | 81 | +| 30.2 | IMS emergency session..... | 81 | +| 30.3 | Next-Generation Pan-European eCall emergency service..... | 81 | + +| | | | +|-------------------------------|----------------------------------------------------------------------------------------------|------------| +| 31 | Restricted Local Operator Services (RLOS)..... | 81 | +| 32 | 3GPP PS data off extension..... | 82 | +| 33 | MTSI Data channel..... | 82 | +| Annex A (informative): | Summary of SIP header fields..... | 82 | +| Annex B (informative): | Dynamic view of SIP header fields within SIP messages..... | 86 | +| B.1 | Scope..... | 86 | +| B.2 | Methodology..... | 86 | +| B.3 | ACK method..... | 88 | +| B.4 | BYE method..... | 89 | +| B.5 | CANCEL method..... | 92 | +| B.6 | INFO method..... | 93 | +| B.7 | INVITE method..... | 97 | +| B.8 | MESSAGE method..... | 103 | +| B.9 | NOTIFY method..... | 106 | +| B.10 | OPTIONS method..... | 109 | +| B.11 | PRACK method..... | 113 | +| B.12 | PUBLISH method..... | 115 | +| B.13 | REFER method..... | 119 | +| B.14 | REGISTER method..... | 123 | +| B.15 | SUBSCRIBE method..... | 125 | +| B.16 | UPDATE method..... | 129 | +| Annex C (informative): | The list of option items for II-NNI..... | 133 | +| C.1 | Scope..... | 133 | +| C.2 | Format of option item table..... | 133 | +| C.3 | Option item table..... | 133 | +| C.3.0 | Supported II-NNI traversal scenarios..... | 133 | +| C.3.1 | Option item table common to roaming, non-roaming II-NNI and loopback traversal scenario..... | 134 | +| C.3.2 | Option item table specific to roaming II-NNI..... | 143 | +| C.3.3 | Option item table specific to non-roaming II-NNI and loopback traversal scenario..... | 146 | +| Annex D (informative): | Change history..... | 150 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +# --- 1 Scope + +The objective of this document is to address the Inter-IMS Network to Network Interface (II-NNI) consisting of Ici and Izi reference points between IMS networks in order to support end-to-end service interoperability. + +The present document addresses the issues related to control plane signalling (3GPP usage of SIP and SDP protocols, required SIP header fields) as well as other interconnecting aspects like security, numbering/naming/addressing and user plane issues as transport protocol, media and codecs actually covered in a widespread set of 3GPP specifications. A profiling of the Inter-IMS Network to Network Interface (II-NNI) is also provided. + +Charging aspects are addressed as far as SIP signalling is concerned. + +IMS emergency session establishment between IMS networks is addressed as far as SIP signalling is concerned. + +SIP signalling traversing the NNI between a CSCF and MRB, e.g. for media control or Voice Interworking with Enterprise IP-PBX, and SIP signalling traversing the NNI on the Mr interface between the CSCF and the MRFC, or on the Mr' interface between the AS and MRFC, or on the Rc interface between AS and MRB is not considered in the present release of this specification. + +SIP signalling traversing the NNI between an application server and the remaining IMS functional entities (e.g. for MCPTT interface SIP-2 in figure 7.3.1-2 in 3GPP TS 23.280 [200]) is not considered in the present release of this specification. + +SIP signalling traversing the NNI between an ISC gateway and an AS in an enterprise network, e.g. for media control and voice interworking with enterprise IP-PBX, on the ISC interface between the ISC gateway and the enterprise network is not considered in the present release of this specification. + +# --- 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] IETF RFC 791: "Internet Protocol". +- [3] 3GPP TS 23.002: "Network architecture". +- [4] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [5] 3GPP TS 24.229: "Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3". +- [6] 3GPP TR 24.930: "Signalling flows for the session setup in the IP Multimedia core network Subsystem (IMS) based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3". +- [7] IETF RFC 2460: "Internet Protocol, Version 6 (IPv6) Specification". +- [8] 3GPP TS 29.162: "Interworking between the IM CN subsystem and IP networks". +- [9] 3GPP TS 22.228: "Service requirements for the IP multimedia core network subsystem". +- [10] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security". + +- [11] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction". +- [12] ETSI TS 181 005 V1.1.1: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Services and Capabilities Requirements". +- [13] IETF RFC 3261: "SIP: Session Initiation Protocol". +- [14] IETF RFC 3966: "The tel URI for Telephone Numbers". +- [15] IETF RFC 3860: "Common Profile for Instant Messaging (CPIM)". +- [16] IETF RFC 3859: "Common Profile for Presence (CPP)". +- [17] IETF RFC 4975: "The Message Session Relay Protocol (MSRP)". +- [18] IETF RFC 3262: "Reliability of provisional responses in Session Initiation Protocol (SIP)". +- [19] IETF RFC 3428: "Session Initiation Protocol (SIP) Extension for Instant Messaging". +- [20] IETF RFC 6665: "SIP-Specific Event Notification". + +NOTE: In earlier releases of this document the predecessor IETF RFC 3265 is used. + +- [21] IETF RFC 3903: "An Event State Publication Extension to the Session Initiation Protocol (SIP)". +- [22] IETF RFC 3515: "The Session Initiation Protocol (SIP) REFER method". +- [23] IETF RFC 3311: "The Session Initiation Protocol (SIP) UPDATE method". +- [24] IETF RFC 7315: "Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3GPP". +- [24A] IETF RFC 7976: "Updates to Private Header (P-Header) Extension Usage in Session Initiation Protocol (SIP) Requests and Responses". +- [24B] IETF RFC 7913: "P-Access-Network-Info ABNF Update". +- [25] IETF RFC 7044: "An Extension to the Session Initiation Protocol (SIP) for Request History Information". +- [26] IETF RFC 6050: "A Session Initiation Protocol (SIP) Extension for the Identification of Services". +- [27] IETF RFC 4168: "The Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP)". +- [28] Void. +- [29] 3GPP TS 32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging". +- [30] 3GPP TS 22.173: "IP Multimedia Core Network Subsystem (IMS); Multimedia Telephony Service and supplementary services; Stage 1". +- [31] 3GPP TS 24.173: "IMS multimedia telephony communication service and supplementary services; Stage 3". +- [32] 3GPP TS 24.607: "Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM); Core Network (CN) subsystem". +- [33] 3GPP TS 24.616: "Malicious Communication Identification (MCID) using IP Multimedia (IM) Core Network (CN) subsystem". +- [34] IETF RFC 3323: "A Privacy Mechanism for the Session Initiation Protocol (SIP)". +- [35] 3GPP TS 23.003: "Numbering, addressing and identification". + +- [36] 3GPP TS 24.610: "Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem". +- [37] 3GPP TS 24.615: "Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem". +- [38] 3GPP TS 24.628: "Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem". +- [39] IETF RFC 6086: "Session Initiation Protocol (SIP) INFO Method and Package Framework". +- [40] IETF RFC 3312: "Integration of resource management and Session Initiation Protocol (SIP)". +- [41] IETF RFC 4032: "Update to the Session Initiation Protocol (SIP) Preconditions Framework". +- [42] IETF RFC 3313: "Private Session Initiation Protocol (SIP) Extensions for Media Authorization". +- [43] IETF RFC 3327: "Session Initiation Protocol Extension Header Field for Registering Non-Adjacent Contacts". +- [44] IETF RFC 3325: "Private Extensions to the Session Initiation Protocol (SIP) for Network Asserted Identity within Trusted Networks". +- [45] IETF RFC 3608: "Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration". +- [46] IETF RFC 3486: "Compressing the Session Initiation Protocol (SIP)". +- [47] IETF RFC 3329: "Security Mechanism Agreement for the Session Initiation Protocol (SIP)". +- [48] IETF RFC 3326: "The Reason Header Field for the Session Initiation Protocol (SIP)". +- [49] IETF RFC 6432: "Carrying Q.850 Codes in Reason Header Fields in SIP (Session Initiation Protocol) Responses". +- [50] IETF RFC 3581: "An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing". +- [51] IETF RFC 3841: "Caller Preferences for the Session Initiation Protocol (SIP)". +- [52] IETF RFC 4028: "Session Timers in the Session Initiation Protocol (SIP)". +- [53] IETF RFC 3892: "The Session Initiation Protocol (SIP) Referred-By Mechanism". +- [54] IETF RFC 3891: "The Session Initiation Protocol (SIP) 'Replaces' Header". +- [55] IETF RFC 3911: "The Session Initiation Protocol (SIP) 'Join' Header". +- [56] IETF RFC 3840: "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)". +- [57] IETF RFC 5079: "Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)". +- [58] IETF RFC 4458: "Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR)". +- [59] IETF RFC 4320: "Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction". +- [60] IETF RFC 4457: "The Session Initiation Protocol (SIP) P-User-Database Private-Header (P-header)". +- [61] IETF RFC 5031: "A Uniform Resource Name (URN) for Emergency and Other Well-Known Services". +- [62] IETF RFC 5627: "Obtaining and Using Globally Routable User Agent (UA) URIs (GRUU) in the Session Initiation Protocol (SIP)". + +- [63] Void. +- [64] IETF RFC 5002: "The Session Initiation Protocol (SIP) P-Profile-Key Private Header (P-Header)". +- [65] IETF RFC 5626: "Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)". +- [66] IETF RFC 5768: "Indicating Support for Interactive Connectivity Establishment (ICE) in the Session Initiation Protocol (SIP)". +- [67] IETF RFC 5365: "Multiple-Recipient MESSAGE Requests in the Session Initiation Protocol (SIP)". +- [68] IETF RFC 6442: "Location Conveyance for the Session Initiation Protocol". +- [69] IETF RFC 5368: "Referring to Multiple Resources in the Session Initiation Protocol (SIP)". +- [70] IETF RFC 5366: "Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)". +- [71] IETF RFC 5367: "Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP)". +- [72] IETF RFC 4967: "Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier". +- [73] IETF RFC 4964: "The P-Answer-State Header Extension to the Session Initiation Protocol for the Open Mobile Alliance Push to Talk over Cellular". +- [74] IETF RFC 5009: "Private Header (P-Header) Extension to the Session Initiation Protocol (SIP) for Authorization of Early Media". +- [75] IETF RFC 4694: "Number Portability Parameters for the 'tel' URI". +- [76] Void. +- [77] IETF RFC 4411: "Extending the Session Initiation Protocol (SIP) Reason Header for Preemption Events". +- [78] IETF RFC 4412: "Communications Resource Priority for the Session Initiation Protocol (SIP)". +- [79] IETF RFC 5393: "Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies". +- [80] IETF RFC 5049: "Applying Signaling Compression (SigComp) to the Session Initiation Protocol (SIP)". +- [81] IETF RFC 5688: "A Session Initiation Protocol (SIP) Media Feature Tag for MIME Application Sub-Types". +- [82] IETF RFC 5360: "A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP)". +- [83] IETF RFC 7433: "A Mechanism for Transporting User-to-User Call Control Information in SIP". +- [83A] IETF RFC 7434: "Interworking ISDN Call Control User Information with SIP". +- [84] IETF RFC 7316: "The Session Initiation Protocol (SIP) P-Private-Network-Indication Private Header (P-Header)". +- [85] IETF RFC 5502: "The SIP P-Served-User Private-Header (P-Header) for the 3GPP IP Multimedia (IM) Core Network (CN) Subsystem". +- [86] Void. +- [87] IETF RFC 8497: "Marking SIP Messages to Be Logged". +- [88] IETF RFC 6228: "Response Code for Indication of Terminated Dialog". + +- [89] IETF RFC 5621: "Message Body Handling in the Session Initiation Protocol (SIP)". +- [90] IETF RFC 6223: "Indication of support for keep-alive". +- [91] IETF RFC 5552: "SIP Interface to VoiceXML Media Services". +- [92] IETF RFC 3862: "Common Presence and Instant Messaging (CPIM): Message Format". +- [93] IETF RFC 5438: "Instant Message Disposition Notification". +- [94] IETF RFC 5373: "Requesting Answering Modes for the Session Initiation Protocol (SIP)". +- [95] Void. +- [96] IETF RFC 3959: "The Early Session Disposition Type for the Session Initiation Protocol (SIP)". +- [97] Void. +- [98] 3GPP TS 24.183: "Customized Ringing Signal (CRS) using IP Multimedia (IM) Core Network (CN) subsystem". +- [99] 3GPP TS 24.259: "Personal Network Management (PNM) using IP Multimedia (IM) Core Network (CN) subsystem". +- [100] 3GPP TS 24.238: "Session Initiation Protocol (SIP) based user configuration". +- [101] 3GPP TS 24.239: "Flexible Alerting (FA) using IP Multimedia (IM) Core Network (CN) subsystem". +- [102] Void. +- [103] 3GPP TS 24.654: "Closed User Group (CUG) using IP Multimedia (IM) Core Network (CN) subsystem". +- [104] Void. +- [105] 3GPP TS 24.605: "Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem". +- [106] 3GPP TS 24.147: "Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem". +- [107] Void. +- [108] Void. +- [109] 3GPP TS 24.642: "Completion of Communications to Busy Subscriber (CCBS) Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem". +- [110] Void. +- [111] Void. +- [112] 3GPP TS 24.606: "Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem". +- [113] 3GPP TS 24.608: "Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) using IP Multimedia (IM); Core Network (CN) subsystem". +- [114] 3GPP TS 24.611: "Communication Barring (CB) using IP Multimedia (IM); Core Network (CN) subsystem". +- [115] Void. +- [116] 3GPP TS 24.629: "Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem". + +- [117] 3GPP TS 24.604: "Communication DIVersion (CDIV) using IP Multimedia (IM) Core Network (CN) subsystem". +- [118] Void. +- [119] Void. +- [120] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) Centralized Services; Stage 2". +- [121] 3GPP TS 24.292: "IP Multimedia Core Network subsystem Centralized Services (ICS); Stage 3". +- [122] 3GPP TS 24.647: "Advice Of Charge (AOC) using IP Multimedia (IM) Core Network (CN) subsystem". +- [123] Void. +- [124] IETF RFC 7989: "End-to-End Session Identification in IP-Based Multimedia Communication Networks". +- [125] IETF RFC 6026: "Correct Transaction Handling for 2xx Responses to Session Initiation Protocol (SIP) INVITE Requests". +- [126] IETF RFC 5658: "Addressing Record-Route issues in the Session Initiation Protocol (SIP)". +- [127] IETF RFC 5954: "Essential correction for IPv6 ABNF and URI comparison in RFC3261". +- [128] Void. +- [129] 3GPP TS 24.182: "IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT)". +- [130] 3GPP TS 29.292: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and MSC Server for IMS Centralized Services (ICS)". +- [131] 3GPP TS 24.237: "IP Multimedia (IM) Core Network (CN) subsystem; IP Multimedia Subsystem (IMS) Service Continuity". +- [132] 3GPP TS 24.141: "Presence service using the IP Multimedia (IM) Core Network (CN) subsystem". +- [133] IETF RFC 6794: "A Framework for Session Initiation Protocol (SIP) Session Policies". +- [134] IETF RFC 5875: "An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package". +- [135] IETF RFC 4488: "Suppression of Session Initiation Protocol (SIP) REFER Method Implicit Subscription". +- [136] IETF RFC 7462: "URNs for the Alert-Info Header Field of the Session Initiation Protocol (SIP)". +- [137] Void. +- [138] OMA-TS-Presence\_SIMPLE-V2\_0-20120710-A: "Presence SIMPLE Specification". +- [139] 3GPP TS 24.247: "Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem". +- [140] IETF RFC 4538: "Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP)". +- [141] IETF RFC 5318: "The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)". +- [142] OMA-TS-Presence\_SIMPLE-V1\_1\_1-20100225-A: "Presence SIMPLE Specification". +- [143] IETF RFC 6809: "Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)". + +- [144] IETF RFC 5839: "An Extension to Session Initiation Protocol (SIP) Events for Conditional Event Notification". +- [145] Void. +- [146] IETF RFC 3264: "An Offer/Answer Model with the Session Description Protocol (SDP)". +- [147] IETF RFC 4566: "SDP: Session Description Protocol". +- [148] 3GPP TS 29.079: "Optimal Media Routeing within the IP Multimedia Subsystem; Stage 3". +- [149] 3GPP TS 24.337: "IP Multimedia Subsystem (IMS) inter-UE transfer". +- [150] IETF RFC 3960: "Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP)". +- [151] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications". +- [152] IETF RFC 768: "User Datagram Protocol". +- [153] IETF RFC 3551: "RTP Profile for Audio and Video Conferences with Minimal Control". +- [154] IETF RFC 3556: "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth". +- [155] IETF RFC 4585: "Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)". +- [156] IETF RFC 793: "Transmission Control Protocol". +- [157] IETF RFC 4733: "RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals". +- [158] IETF RFC 4916: "Connected Identity in the Session Initiation Protocol (SIP)". +- [159] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity". +- [160] IETF RFC 6140: "Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP)". +- [161] IETF RFC 6230: "Media Control Channel Framework". +- [162] IETF RFC 4145: "TCP-Based Media Transport in the Session Description Protocol (SDP)". +- [163] 3GPP TS 24.390: "Unstructured Supplementary Service Data (USSD)". +- [164] IETF RFC 6357: "Design Considerations for Session Initiation Protocol (SIP) Overload Control". +- [165] IETF RFC 7339: "Session Initiation Protocol (SIP) Overload Control". +- [166] IETF RFC 7415: "Session Initiation Protocol (SIP) Rate Control". +- [167] IETF RFC 7200: "A Session Initiation Protocol (SIP) Load-Control Event Package". +- [168] 3GPP TS 29.163: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks". +- [169] IETF RFC 2046: "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types". +- [170] IETF RFC 2387: "The MIME Multipart/Related Content-type". +- [171] IETF RFC 3420: "Internet Media Type message/sipfrag". +- [172] IETF RFC 3842: "A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)". +- [173] IETF RFC 3858: "An Extensible Markup Language (XML) Based Format for Watcher Information". + +- [174] IETF RFC 3863: "Presence Information Data Format (PIDF)". +- [175] IETF RFC 3994: "Indication of Message Composition for Instant Messaging". +- [176] IETF RFC 4661: "An Extensible Markup Language (XML) Based Format for Event Notification Filtering". +- [177] IETF RFC 4662: "A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists". +- [178] IETF RFC 4826: "Extensible Markup Language (XML) Formats for Representing Resource Lists". +- [179] IETF RFC 5262: "Presence Information Data Format (PIDF) Extension for Partial Presence". +- [180] IETF RFC 5874: "An Extensible Markup Language (XML) Document Format for Indicating a Change in XML Configuration Access Protocol (XCAP) Resources". +- [181] Void. +- [182] OMA-SUP-XSD\_prs\_suppnotFilter-V1\_0-20120710-A: "Presence - Event notification suppression filter". +- [183] 3GPP TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles". +- [184] IETF RFC 7090: "Public Safety Answering Point (PSAP) Callback". +- [185] IETF RFC 8055: "Session Initiation Protocol (SIP) Via Header Field Parameter to Indicate Received Realm". +- [186] 3GPP TS 29.658: "SIP Transfer of IP Multimedia Service Tariff Information". +- [187] 3GPP TS 22.153: "Multimedia priority service". +- [188] IETF RFC 7549: "3GPP SIP URI Inter Operator Traffic Leg parameter". +- [189] 3GPP TS 24.103: "Telepresence using the IP Multimedia (IM) Core Network (CN) Subsystem (IMS); Stage 3". +- [190] IETF RFC 8841: "Session Description Protocol (SDP) Offer/Answer Procedures for Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) Transport". +- [191] 3GPP TS 24.315: "IP Multimedia Subsystem (IMS) Operator Determined Barring (ODB)". +- [192] 3GPP TR 29.949: "Study on Technical aspects on Roaming End-to-end scenarios with VoLTE IMS and other networks". +- [193] IETF RFC 8119: "SIP "cause" URI Parameter for Service Number Translation". +- [194] IETF RFC 7647: "Clarifications for the Use of REFER with RFC6665". +- [195] IETF RFC 7614: "Explicit Subscriptions for the REFER Method". +- [196] IETF RFC 7621: "A Clarification on the Use of Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol SIP Event Notification Framework". +- [197] IETF RFC 2646: "The Text/Plain Format Parameter". +- [198] IETF RFC 1866: "Hypertext Markup Language - 2.0". +- [199] 3GPP TS 22.179: "Mission Critical Push To Talk (MCPTT); Stage 1". +- [200] 3GPP TS 23.280: "Common functional architecture to support mission critical services; Stage 2". +- [201] 3GPP TS 24.379: "Mission Critical Push To Talk (MCPTT) call control Protocol specification". + +- [202] 3GPP TS 24.380: "Mission Critical Push To Talk (MCPTT) floor control Protocol specification". +- [203] IETF RFC 8498: "A P-Served-User Header Field Parameter for an Originating Call Diversion (CDIV) Session Case in the Session Initiation Protocol (SIP)". +- [204] IETF RFC 4575: "A Session Initiation Protocol (SIP) Event Package for Conference State". +- [205] IETF RFC 4354: "A Session Initiation Protocol (SIP) Event Package and Data Format for Various Settings in Support for the Push-to-Talk over Cellular (PoC) Service". +- [206] IETF RFC 8224: "Authenticated Identity Management in the Session Initiation Protocol (SIP)". +- [207] IETF RFC 8197: "A SIP Response Code for Unwanted Calls". +- [208] IETF RFC 6910: "Completion of Calls for the Session Initiation Protocol (SIP)". +- [209] 3GPP TS 22.280: "Mission Critical Services Common Requirements". +- [210] 3GPP TS 24.281: "Mission Critical Video (MCVideo) signalling control; Protocol specification". +- [211] 3GPP TS 24.282: "Mission Critical Data (MCData) signalling control; Protocol specification". +- [212] 3GPP TS 24.581: "Mission Critical Video (MCVideo) media plane control; Protocol specification". +- [213] 3GPP TS 24.582: "Mission Critical Data (MCData) media plane control; Protocol specification". +- [214] IETF RFC 8606: "ISDN User Part (ISUP) Cause Location Parameter for the SIP Reason Header Field". +- [215] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions". +- [216] IETF RFC 8262: "Content-ID Header Field in the Session Initiation Protocol (SIP)". +- [217] 3GPP TS 24.196: "Technical Specification Group Core Network and Terminals; Enhanced Calling Name". +- [218] 3GPP TS 24.174: "Support of Multi-Device and Multi-Identity in IMS; Stage 3". +- [219] 3GPP TS 23.218: "IP Multimedia (IM) Session Handling; IM call model". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**example:** text used to clarify abstract rules by applying them literally. + +**IM CN subsystem:** (IP Multimedia CN subsystem) comprises of all CN elements for the provision of IP multimedia applications over IP multimedia sessions, as specified in 3GPP TS 22.228 [9]. + +**IP multimedia session:** as specified in 3GPP TS 22.228 [9] an IP multimedia session is a set of multimedia senders and receivers and the data streams flowing from senders to receivers. IP multimedia sessions are supported by the IP multimedia CN Subsystem and are enabled by IP connectivity bearers (e.g. GPRS as a bearer). A user can invoke concurrent IP multimedia sessions. + +**non-roaming II-NNI:** the II-NNI between IMS home networks, or, if the Roaming Architecture for Voice over IMS with Local Breakout is used, alternatively the II-NNI between the caller's visited network and the callee's home network. + +**roaming II-NNI:** the II-NNI between a visited IMS network and the IMS home network; for the Roaming Architecture for Voice over IMS with Local Breakout, the loopback traversal scenario is excluded. + +**loopback traversal scenario:** for the Roaming Architecture for Voice over IMS with Local Breakout, the scenario where the II-NNI between the caller's home network and the caller's visited network is being traversed by an initial INVITE request from the caller's home network to the caller's visited network or any subsequent SIP message within the same dialogue on the same call leg. + +**home-to-visited request on roaming II-NNI:** SIP request being sent from the callee's home network to the callee's visited network. + +**home routeing:** the scenario when the caller's home network routes a dialog creating SIP request directly to the callee's home network without using the loopback traversal scenario. + +**visited-to-home request on roaming II-NNI:** SIP request being sent from the caller's visited network to the caller's home network. + +**home-to-visited response on roaming II-NNI:** SIP response being sent from the caller's home network to the caller's visited network. + +**visited-to-home response on roaming II-NNI:** SIP response being sent from the callee's visited network to the callee's home network. + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.292 [120] apply: + +### **MSC Server enhanced for ICS** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.237 [159] apply: + +### **MSC server enhanced for SRVCC** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.237 [131] apply: + +### **MSC server enhanced for dual radio** + +For the purposes of the present document, the following term and definition given in 3GPP TS 23.218 [219] apply: + +### **Standalone transaction** + +## **3.2 Symbols** + +For the purposes of the present document, the following symbols apply: + +| | | +|-----|----------------------------------------------------------------------------------------------------------------------------------------------| +| I2 | Reference point between the MSC Server enhanced for ICS and the home IMS | +| Ici | Reference Point between an IBCF and another IBCF belonging to a different IM CN subsystem network | +| Izi | Reference Point between a TrGW and another TrGW or media handling node belonging to a different IM CN subsystem network | +| Mi | Reference Point between a BGCF and CSCF | +| Mm | Reference Point between a CSCF/BGCF/IMS ALG and an IP multimedia network | +| Mw | Reference Point between a CSCF and another CSCF | +| Mx | Reference Point between a CSCF/BGCF/MSC Server enhanced for ICS/ MSC Server enhanced for SRVCC / MSC server enhanced for dual radio and IBCF | + +## **3.3 Abbreviations** + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|------|------------------------------------------------| +| 18x | A SIP status-code in the range 180 through 189 | +| 2xx | A SIP status-code in the range 200 through 299 | +| 3PTY | Three-Party | +| 3xx | A SIP status-code in the range 300 through 399 | +| 4xx | A SIP status-code in the range 400 through 499 | +| 5GS | 5G System | + +| | | +|-----------|----------------------------------------------------------------------| +| 5xx | A SIP status-code in the range 500 through 599 | +| 6xx | A SIP status-code in the range 600 through 699 | +| ACR | Anonymous Communication Rejection | +| AOC | Advice Of Charge | +| AS | Application Server | +| ATCF | Access Transfer Control Function | +| B2BUA | Back 2 Back User Agent | +| BGCF | Breakout Gateway Control Function | +| CAT | Customized Alerting Tone | +| CB | Communication Barring | +| CCBS | Completion of Communications to Busy Subscriber | +| CCNL | Completion of Communications on Not Logged-in | +| CCNR | Communication Completion on No Reply | +| CDIV | Communication Diversion | +| CONF | Conference | +| CRS | Customized Ringing Signal | +| CSCF | Call Session Control Function | +| CW | Communication Waiting | +| DRVCC | Dual Radio Voice Call Continuity | +| eCNAM | Enhanced Calling Name | +| E-CSCF | Emergency CSCF | +| ECT | Explicit Communication Transfer | +| FA | Flexible Alerting | +| GRUU | Globally Routable User agent URIs | +| HOLD | Communication HOLD | +| IBCF | Interconnection Border Control Function | +| ICB | Incoming Communication Barring | +| ICID | IMS Charging Identifier | +| ICS | IMS Centralized Services | +| I-CSCF | Interrogating CSCF | +| II-NNI | Inter-IMS Network to Network Interface | +| IM | Instant Messaging | +| IMS-ALG | IMS Application Level Gateway | +| IOI | Inter Operator Identifier | +| IUT | Inter UE Transfer | +| MBMS | Multimedia Broadcast Multicast Service | +| MCDData | Mission Critical Data | +| MCID | Malicious Communication Identification | +| MCPTT | Mission Critical Push-To-Talk | +| MCVideo | Mission Critical Video | +| MiD | Multi-iDentity | +| MMTEL | Multimedia Telephony | +| MPS | Multimedia Priority Service | +| MRB | Media Resource Broker | +| MRFC | Media Resource Function Controller | +| MRFP | Multimedia Resource Function Processor | +| MSD | Minimum Set of Data | +| MSRP | Message Session Relay Protocol | +| MTSI | Multimedia Telephony Service for IMS | +| MuD | Multi-Device | +| MWI | Message Waiting Indication | +| NA(P)T-PT | Network Address (Port-Multiplexing) Translation-Protocol Translation | +| NNI | Network to Network Interface | +| OCB | Outgoing Communication Barring | +| OIP | Originating Identification Presentation | +| OIR | Originating Identification Restriction | +| OMA | Open Mobile Alliance | +| OMR | Optimal Media Routeing | +| P-CSCF | Proxy CSCF | +| PCF | Policy Control Function | +| PCRF | Policy and Charging Rules Function | + +| | | +|--------|-----------------------------------------| +| PNM | Personal Network Management | +| PRES | Presence | +| PSAP | Public Safety Answering Point | +| PSI | Public Service Identity | +| RLOS | Restricted Local Operator Services | +| RTT | Round-trip Time | +| S-CSCF | Serving CSCF | +| SRVCC | Single Radio Voice Call Continuity | +| STN | Session Transfer Number | +| TIP | Terminating Identification Presentation | +| TIR | Terminating Identification Restriction | +| TRF | Transit and Roaming Function | +| TrGW | Transition Gateway | +| UDM | Unified Data Management | +| vSRVCC | Single Radio Video Call Continuity | + +# 4 Overview + +Interconnection between two different IM CN subsystems shall be guaranteed in order to support end-to-end service interoperability. For this purpose, Inter-IMS Network to Network Interface (II-NNI) between two IM CN subsystem networks is adopted, according to the assumptions coming from 3GPP TS 23.002 [3] and 3GPP TS 23.228 [4]. + +NOTE: The end-to-end service interoperability within one IM CN subsystem over the Mi, Mm, Mw and I2 reference points not passing over the Mx reference point as defined in 3GPP TS 23.228 [4] is outside the scope of this document. + +Aiming to support the delivery of IMS services between two separated IM CN subsystems, protocol interconnection has to occur: + +- at a control plane level, in order that IMS procedures can be supported. In this case the adopted reference point is the Ici; and +- at a user plane level, where media streams are exchanged over the Izi reference point. + +IP multimedia sessions are managed by SIP. The transport mechanism for both SIP session signalling and media transport is IPv4 (IETF RFC 791 [2]) or IPv6 (IETF RFC 2460 [7]). The 3GPP profile of SIP defining the usage of SIP within the IM CN subsystem is specified in 3GPP TS 24.229 [5]. Example call flows are provided in 3GPP TR 24.930 [6]. + +The general interconnection model is shown in figure 4.1. + + + +``` + +graph LR + A((IM CN Subsystem)) --- B[II-NNI] + B --- C((IM CN Subsystem)) + +``` + +The diagram illustrates two grey oval shapes, each containing a white rectangular box with the text "IM CN Subsystem". These two ovals are connected by a horizontal line. In the center of this line, there is a vertical tick mark. Below the horizontal line, centered between the two ovals, is a white rectangular box containing the text "II-NNI". + +Diagram showing the interconnection model for two IM CN Subsystems connected via an II-NNI interface. + +**Figure 4.1: Interconnection Model for IM CN subsystems** + +The II-NNI traversal scenarios in this document are covered in figure 4.2, figure 4.3 and figure 4.4. + + + +This diagram illustrates II-NNI traversal scenarios when home routing is used. It features four nodes: IMS home network A, IMS home network B, IMS visited network X, and IMS visited network Y. IMS home network A and IMS home network B are connected by a horizontal line labeled 'non-roaming II-NNI'. Above this connection, an arrow points from A to B with the text 'request on non-roaming II-NNI (home routing)'. IMS visited network X is connected to IMS home network A by a vertical line labeled 'roaming II-NNI'. An arrow points from X to A with the text 'visited-to-home request on roaming II-NNI'. IMS visited network Y is connected to IMS home network B by a vertical line labeled 'roaming II-NNI'. An arrow points from B to Y with the text 'home-to-visited request on roaming II-NNI'. + +Diagram of II-NNI traversal scenarios with home routing. + +- NOTE 1: Any II-NNI can contain intermediate transit network(s). The intermediate transit network can either be an IMS transit network with or without a transit function as specified in 3GPP TS 24.229 [5] or a non-IMS transit network using standards outside the scope of 3GPP. +- NOTE 2: IMS home network A and IMS home network B represent the IMS home network on originating side and terminating side respectively. +- NOTE 3: IMS visited network X and IMS visited network Y represent the IMS visited network on originating side and terminating side respectively. + +**Figure 4.2: II-NNI traversal scenarios when P-CSCF is located in visited network and when home routing is used** + + + +This diagram illustrates II-NNI traversal scenarios when the roaming architecture for voice over IMS with local breakout is used. It features four nodes: IMS home network A, IMS home network B, IMS visited network X, and IMS visited network Y. IMS home network A and IMS home network B are connected by a horizontal line. Above this connection, an arrow points from A to B with the text 'request on non-roaming II-NNI (roaming architecture for voice over IMS with local breakout)'. IMS visited network X is connected to IMS home network A by a vertical line. An arrow points from X to A with the text 'visited-to-home request on roaming II-NNI'. Another arrow points from X to B with the text 'loopback traversal scenario'. IMS visited network Y is connected to IMS home network B by a vertical line. An arrow points from B to Y with the text 'home-to-visited request on roaming II-NNI'. + +Diagram of II-NNI traversal scenarios with local breakout. + +- NOTE 1: Any II-NNI can contain intermediate transit network(s). The intermediate transit network can either be an IMS transit network with or without a transit function as specified in 3GPP TS 24.229 [5] or a non-IMS transit network using standards outside the scope of 3GPP. +- NOTE 2: IMS home network A and IMS home network B represent the IMS home network on originating side and terminating side respectively. +- NOTE 3: IMS visited network X and IMS visited network Y represent the IMS visited network on originating side and terminating side respectively. + +**Figure 4.3: II-NNI traversal scenarios when P-CSCF is located in visited network and when the roaming architecture for voice over IMS with local breakout is used** + + + +Figure 4.4: IMS emergency session traversal scenario on non-roaming II-NNI. The diagram shows an 'Originating IMS network O' connected to a 'Terminating IMS network T' via a thick horizontal line representing the II-NNI. A curved arrow above the line points from O to T, labeled 'IMS emergency session traversal scenario on non-roaming II-NNI'. + +- NOTE 1: Originating IMS network O represents the IMS network to which the originating UE is attached to, and terminating IMS network T represents the IMS network which accomodates a PSAP. +- NOTE 2: Originating IMS network O can be a visited IMS network or a home IMS network. +- NOTE 3: The E-CSCF is located in the originating IMS network O. +- NOTE 4: Any II-NNI between originating IMS network O and terminating IMS network T does not use any specific capabilities for roaming II-NNI, and is treated as non-roaming II-NNI. + +**Figure 4.4: IMS emergency session traversal scenario on non-roaming II-NNI** + +The possible functional entities involved in the signalling plane interconnection (IBCF, I-CSCF, P-CSCF, ATCF, S-CSCF, E-CSCF, BGCF, MSC Server enhanced for ICS, MSC server enhanced for SRVCC, MSC server enhanced for dual radio and TRF) and in the user plane interconnection (TrGW) are specified in 3GPP TS 24.229 [5], in 3GPP TS 24.292 [121], 3GPP TS 29.292 [130], 3GPP TS 29.162 [8] and in 3GPP TS 24.237 [131]. + +IP Version interworking is described within 3GPP TS 29.162 [8]. + +Examples of usage of the Inter-IMS Network to Network Interface (II-NNI) for roaming scenarios are described in 3GPP TR 29.949 [192]. + +# 5 Reference model for interconnection between IM CN subsystems + +## 5.1 General + +Figure 5.1.1 illustrates the architecture diagram given in 3GPP TS 23.228 [4] showing the Inter-IMS Network to Network Interface (II-NNI) between two IM CN subsystem networks. + + + +Figure 5.1.1: Inter-IMS Network to Network Interface between two IM CN subsystem networks. The diagram shows two networks, 'IM CN subsystem network A' and 'IM CN subsystem network B', separated by a vertical dashed line labeled 'II-NNI'. Network A contains functional entities: P-CSCF, S-CSCF, I-CSCF, BGCF, IBCF, ATCF, MSC Server enhanced for ICS, SRVCC or dual radio, TrGW, TRF, TF, and AS. Network B contains the same entities. The IBCF in Network A is connected to the IBCF in Network B via the 'Ici' reference point. The TrGW in Network A is connected to the TrGW in Network B via the 'Izi' reference point. Various other reference points like 'Mx', 'Ix', and 'Lx' are shown between internal entities. A legend at the bottom left indicates that dashed lines represent 'Signalling' and solid lines represent 'Bearer'. + +NOTE: The TRF can reside in a stand-alone entity or can be combined with another functional entity. + +**Figure 5.1.1: Inter-IMS Network to Network Interface between two IM CN subsystem networks** + +The protocols over the two reference points Ici and Izi make up the Inter-IMS Network to Network Interface. + +The Ici reference point allows IBCFs to communicate with each other in order to provide the communication and forwarding of SIP signalling messaging between IM CN subsystem networks. The Izi reference point allows TrGWs to forward media streams between IM CN subsystem networks. + +IMS roaming performed by using II-NNI is considered, when the IBCFs are inserted at the network borders. The applicability of roaming scenario by using II-NNI is based on agreement between the operators. + +Whenever the Inter-IMS Network to Network Interface is used to interconnect two IM CN subsystem networks belonging to different security domains, security procedures apply as described in 3GPP TS 33.210 [10]. + +When an IMS transit network is providing application services and interconnecting two IM CN subsystem networks, as described in 3GPP TS 23.228 [4], interfaces on both sides of the IMS transit network are within the scope of this document. + +When two IM CN subsystem networks are interconnected for IMS emergency session establishment as described in 3GPP TS 23.167 [215], the interface between these IM CN subsystem networks is within the scope of this document. + +**NOTE:** Implementations of functional entities at the IMS network edge might include functions that are not described in this Release of the specification, for example fault management that sends SIP OPTIONS requests between the two IBCFs over the Ici. IBCF originated SIP OPTIONS standalone transactions and any other features not described in the main body of this specification are out of scope. + +## 5.2 Functionalities performed by entities at the edge of the network + +### 5.2.1 Interconnection Border Control Function (IBCF) + +An IBCF provides application specific functions at the SIP/SDP protocol layer in order to perform interconnection between IM CN subsystem networks by using Ici reference point. According to 3GPP TS 23.228 [4], IBCF can act both as an entry point and as an exit point for the IM CN subsystem network. + +The functionalities of IBCF are indicated in the 3GPP TS 23.228 [4] and specified in 3GPP TS 24.229 [5]. They include: + +- network topology hiding; +- application level gateway (for instance enabling communication between IPv6 and IPv4 SIP applications, or between a SIP application in a private IP address space and a SIP application outside this address space); +- controlling transport plane functions; +- controlling media plane adaptations; +- screening of SIP signalling information; +- selecting the appropriate signalling interconnect; +- generation of charging data records; +- privacy protection; +- additional routing functionality; and +- inclusion of a transit IOI in requests when acting as an entry point for a transit network and in responses when acting as an exit point for a transit network. + +Based on local configuration, the IBCF performs transit routing functions as specified in 3GPP TS 24.229 [5] clause I.2. + +The IBCF acts as a B2BUA when it performs IMS-ALG functionality. + +### 5.2.2 Transition Gateway (TrGW) + +According to 3GPP TS 23.002 [3], the TrGW is located at the network borders within the media path and is controlled by an IBCF. Forwarding of media streams between IM CN subsystem networks is applied over Izi reference point. + +The TrGW provides functions like network address/port translation and IPv4/IPv6 protocol translation. NAT-PT binds addresses in IPv6 network with addresses in IPv4 network and vice versa to provide transparent routing between the two IP domains without requiring any changes to end points. NA(P)T-PT provides additional translation of transport identifier (TCP and UDP port numbers). The approach is similar to that one described also in 3GPP TS 29.162 [8]. + +Further details are described in 3GPP TS 23.228 [4]. + +## 5.3 Identifying II-NNI traversal scenario + +### 5.3.1 General + +The procedures for identifying the II-NNI traversal scenario using the "iotl" SIP URI parameter defined in IETF RFC 7549 [188] is specified in 3GPP TS 24.229 [5]. + +This specification uses the following II-NNI traversal scenarios when describing requirements at II-NNI: + +- the non-roaming II-NNI traversal scenario; +- the roaming II-NNI traversal scenario; and +- the loopback II-NNI traversal scenario. + +When a requirement at II-NNI is dependent on direction the roaming II-NNI traversal scenario is further divided into: + +- the home-to-visited II-NNI traversal scenario; and +- the visited-to-home II-NNI traversal scenario. + +See figure 4.2 and figure 4.3 for information on how the II-NNI traversal scenarios above are applied between networks. + +### 5.3.2 Mapping of the "iotl" SIP URI parameter to II-NNI traversal scenario + +Table 5.3.2.1 describes how the "iotl" SIP URI parameter shall be used to identify the II-NNI traversal scenario. The table 5.3.2.1 contains the following items: + +- the first column, named "II-NNI traversal scenario", shows the II-NNI traversal scenarios within the scope of this specification; and +- the second column, named "Value of the "iotl" parameter", shows the value of the "iotl" SIP URI parameter as specified in IETF RFC 7549 [188]. + +**Table 5.3.2.1: Mapping of the "iotl" SIP URI parameter to II-NNI traversal scenario** + +| II-NNI traversal scenario | Value of the "iotl" parameter | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------| +| Non-roaming II-NNI traversal scenario (NOTE 1) | "homeA-homeB" or "visitedA-homeB" | +| Loopback traversal scenario | "homeA-visitedA" | +| Roaming II-NNI traversal scenario | "visitedA-homeA" or "homeB-visitedB" (NOTE 2) | +| Home-to-visited traversal scenario | "homeB-visitedB" | +| Visited-to-home traversal scenario | "visitedA-homeA" | +| NOTE 1: This is the default II-NNI traversal scenario, if the "iotl" SIP URI parameter is not present in the Request-URI or in any of the Route header fields in the SIP request and if an implementation dependent method of identifying the II-NNI traversal scenario is not used. | | +| NOTE 2: When the requirement at II-NNI is independent on direction any of the "visitedA-homeA" or "homeB-visitedB" can be used to identify the roaming II-NNI traversal scenario. | | + +# 6 Control plane interconnection + +## 6.1 Definition of Inter-IMS Network to Network Interconnection + +### 6.1.1 SIP methods and header fields + +#### 6.1.1.1 General + +The functional entity closest to the border of an II-NNI (see reference model in clause 5) shall provide the capabilities specified for that network element in clause A.2 of 3GPP TS 24.229 [5] with modifications as described in the following clauses. + +#### 6.1.1.2 SIP methods + +3GPP TS 24.229 [5] defines the methods allowing an IBCF to interconnect to an IBCF placed in another IM CN subsystem. + +The following SIP methods are supported on the II-NNI as defined in table 6.1. + +The following table is based on table A.5 and table A.163 of 3GPP TS 24.229 [5] and endorsed for this document: + +**Table 6.1: Supported SIP methods** + +| Item | Method | Ref. | II-NNI | | +|-------|---------------------------------------------------------------------------------|--------------------|---------|-----------| +| | | | Sending | Receiving | +| 1 | ACK request | IETF RFC 3261 [13] | m | m | +| 2 | BYE request | IETF RFC 3261 [13] | m | m | +| 3 | BYE response | IETF RFC 3261 [13] | m | m | +| 4 | CANCEL request | IETF RFC 3261 [13] | m | m | +| 5 | CANCEL response | IETF RFC 3261 [13] | m | m | +| 5A | INFO request | IETF RFC 6086 [39] | o | o | +| 5B | INFO response | IETF RFC 6086 [39] | o | o | +| 8 | INVITE request | IETF RFC 3261 [13] | m | m | +| 9 | INVITE response | IETF RFC 3261 [13] | m | m | +| 9A | MESSAGE request | IETF RFC 3428 [19] | o | o | +| 9B | MESSAGE response | IETF RFC 3428 [19] | o | o | +| 10 | NOTIFY request | IETF RFC 6665 [20] | c1 | c1 | +| 11 | NOTIFY response | IETF RFC 6665 [20] | c1 | c1 | +| 12 | OPTIONS request | IETF RFC 3261 [13] | m | m | +| 13 | OPTIONS response | IETF RFC 3261 [13] | m | m | +| 14 | PRACK request | IETF RFC 3262 [18] | m | m | +| 15 | PRACK response | IETF RFC 3262 [18] | m | m | +| 15A | PUBLISH request | IETF RFC 3903 [21] | c1 | c1 | +| 15B | PUBLISH response | IETF RFC 3903 [21] | c1 | c1 | +| 16 | REFER request | IETF RFC 3515 [22] | o | o | +| 17 | REFER response | IETF RFC 3515 [22] | o | o | +| 18 | REGISTER request | IETF RFC 3261 [13] | c2 | c2 | +| 19 | REGISTER response | IETF RFC 3261 [13] | c2 | c2 | +| 20 | SUBSCRIBE request | IETF RFC 6665 [20] | c1 | c1 | +| 21 | SUBSCRIBE response | IETF RFC 6665 [20] | c1 | c1 | +| 22 | UPDATE request | IETF RFC 3311 [23] | m | m | +| 23 | UPDATE response | IETF RFC 3311 [23] | m | m | +| c1: | In case of roaming II-NNI, the support of the method is m, else o. | | | | +| c2: | In case of roaming II-NNI, the support of the method is m, else n/a. | | | | +| NOTE: | In the above table, m, o and c and n/a have the meanings indicated in table 6.3 | | | | + +#### 6.1.1.3 SIP header fields + +##### 6.1.1.3.0 General + +The IBCF shall provide the capabilities to manage and modify SIP header fields according to clause 5.10 and annex A of 3GPP TS 24.229 [5] with modifications as described in the following clauses. + +##### 6.1.1.3.1 Trust and no trust relationship + +The IBCF acting as exit point applies the procedures described in clause 5.10.2 of 3GPP TS 24.229 [5] before forwarding the SIP signalling to the IBCF acting as entry point. The IBCF acting as entry point applies the procedures described in clause 5.10.3 of 3GPP TS 24.229 [5]. + +Additionally, in case there is no trust relationship between the two IM CN subsystems connected by II-NNI, the IBCF applies the procedures described in clause 4.4 of 3GPP TS 24.229 [5], before forwarding the SIP signalling. + +These procedures may be utilized on a per header field basis to realize overall trust as well as per service level screening of header fields. Trust relationships and trust domains may be defined by inter-operator agreements for individual services and/or individual SIP header fields. + +The management of the SIP header fields (if present) over II-NNI in case of a presence or not of a trust relationship between the two interconnected IM CN subsystems is wrapped up in the following table. + +**Table 6.2: Management of SIP header fields and parameters over II-NNI in presence or not of a trust relationship** + +| Item | Header field or parameter | Reference | Trust relationship | Not trust relationship | +|------|----------------------------------------|-----------------------------------|---------------------------------------------------------|--------------------------------------------------------------------------------------| +| 1 | P-Asserted-Identity | IETF RFC 3325 [44] | As specified in 3GPP TS 24.229 [5], clause 4.4 | As specified in 3GPP TS 24.229 [5], clause 4.4 | +| 2 | P-Access-Network-Info | IETF RFC 7315 [24] | As specified in 3GPP TS 24.229 [5], clause 4.4 | As specified in 3GPP TS 24.229 [5], clause 4.4 | +| 3 | Resource-Priority | IETF RFC 4412 [78] | As specified in 3GPP TS 24.229 [5], clause 4.4 | As specified in 3GPP TS 24.229 [5], clause 4.4 | +| 4 | History-Info | IETF RFC 7044 [25] | As specified in 3GPP TS 24.229 [5], clause 4.4 | As specified in clause 7 of IETF RFC 7044 [25] and in 3GPP TS 24.229 [5], clause 4.4 | +| 5 | P-Asserted-Service | IETF RFC 6050 [26] | As specified in 3GPP TS 24.229 [5], clause 4.4 (NOTE 3) | As specified in 3GPP TS 24.229 [5], clause 4.4 (NOTE 3) | +| 6 | P-Charging-Vector | IETF RFC 7315 [24] | As specified in 3GPP TS 24.229 [5], clause 5.10 | As specified in 3GPP TS 24.229 [5], clause 5.10 | +| 7 | P-Charging-Function-Addresses (NOTE 4) | IETF RFC 7315 [24] | As specified in 3GPP TS 24.229 [5], clause 5.10 | As specified in 3GPP TS 24.229 [5], clause 5.10 | +| 8 | P-Profile-Key (NOTE 2) | IETF RFC 5002 [64] | As specified in 3GPP TS 24.229 [5], clause 4.4 | As specified in 3GPP TS 24.229 [5], clause 4.4 | +| 9 | P-Private-Network-Indication | IETF RFC 7316 [84] | As specified in 3GPP TS 24.229 [5], clause 4.4 | As specified in 3GPP TS 24.229 [5], clause 4.4 | +| 10 | P-Served-User (NOTE 1, NOTE 2) | IETF RFC 5502 [85] | As specified in 3GPP TS 24.229 [5], clause 4.4 | As specified in 3GPP TS 24.229 [5], clause 4.4 | +| 11 | Reason (in a response) | IETF RFC 6432 [49] | As specified in 3GPP TS 24.229 [5], clause 4.4 | As specified in 3GPP TS 24.229 [5], clause 4.4 | +| 12 | P-Early-Media | IETF RFC 5009 [74] | As specified in 3GPP TS 24.229 [5], clause 4.4 | As specified in 3GPP TS 24.229 [5], clause 4.4 | +| 13 | Feature-Caps | IETF RFC 6809 [143] | As specified in 3GPP TS 24.229 [5], clause 4.4 | As specified in 3GPP TS 24.229 [5], clause 4.4 | +| 14 | Priority (NOTE 6) | IETF RFC 7090 [184] | As specified in 3GPP TS 24.229 [5], clause 4.4 | As specified in 3GPP TS 24.229 [5], clause 4.4 | +| 15 | "iotl" SIP URI parameter (NOTE 7) | IETF RFC 7549 [188] | As specified in 3GPP TS 24.229 [5], clause 4.4 | As specified in 3GPP TS 24.229 [5], clause 4.4 | +| 16 | "cpc" tel URI parameter (NOTE 5) | 3GPP TS 24.229 [5] clause 7.2A.12 | As specified in 3GPP TS 24.229 [5], clause 4.4 | As specified in 3GPP TS 24.229 [5], clause 4.4 | +| 17 | "oli" tel URI parameter (NOTE 5) | 3GPP TS 24.229 [5] clause 7.2A.12 | As specified in 3GPP TS 24.229 [5], clause 4.4 | As specified in 3GPP TS 24.229 [5], clause 4.4 | +| 18 | Restoration-Info (NOTE 2) | 3GPP TS 24.229 [5] clause 7.2.11 | As specified in 3GPP TS 24.229 [5], clause 4.4 | As specified in 3GPP TS 24.229 [5], clause 4.4 | +| 19 | Relayed-Charge (NOTE 4) | 3GPP TS 24.229 [5] clause 7.2.12 | As specified in 3GPP TS 24.229 [5], clause 4.4 | As specified in 3GPP TS 24.229 [5], clause 4.4 | +| 20 | Service-Interact-Info | 3GPP TS 24.229 [5] clause 7.2.14 | As specified in 3GPP TS 24.229 [5], clause 4.4 | As specified in 3GPP TS 24.229 [5], clause 4.4 | +| 21 | Cellular-Network-Info | 3GPP TS 24.229 [5] clause 7.2.15 | As specified in 3GPP TS 24.229 [5], clause 4.4 | As specified in 3GPP TS 24.229 [5], clause 4.4 | + +| | | | | | +|----|------------------------------|-------------------------------------|------------------------------------------------------|------------------------------------------------------| +| 22 | Response-Source | 3GPP TS 24.229 [5]
clause 7.2.17 | As specified in
3GPP TS 24.229 [5],
clause 4.4 | As specified in
3GPP TS 24.229 [5],
clause 4.4 | +| 23 | Attestation-Info
(NOTE 8) | 3GPP TS 24.229 [5]
clause 7.2.18 | As specified in
3GPP TS 24.229 [5],
clause 4.4 | As specified in
3GPP TS 24.229 [5],
clause 4.4 | +| 24 | Origination-Id
(NOTE 8) | 3GPP TS 24.229 [5]
clause 7.2.19 | As specified in
3GPP TS 24.229 [5],
clause 4.4 | As specified in
3GPP TS 24.229 [5],
clause 4.4 | +| 25 | Additional-Identity | 3GPP TS 24.229 [5]
clause 7.2.20 | As specified in
3GPP TS 24.229 [5],
clause 4.4 | As specified in
3GPP TS 24.229 [5],
clause 4.4 | + +NOTE 1: For a roaming II-NNI, a trust relationship with respect to this header field is required. +NOTE 2: This header field is only applicable on a roaming II-NNI. +NOTE 3: In addition, value-dependent operator policies may be applied. +NOTE 4: This header field is not applicable at II-NNI. +NOTE 5: The tel URI parameters "cpc" and "oli" can be included in the URI in the P-Asserted-Identity header field. +NOTE 6: Only the "psap-callback" value is part of the trust domain. +NOTE 7: The "iotl" SIP URI parameter can be transported in the Request-URI, Route header field, Path header field, Service-Route header field, "+g.3gpp.trf" header field parameter, "+g.3gpp.atcf-mgmt-uri" header field parameter and in the "ATU-STI" parameter in the "application/vnd.3gpp.srvcc-info+xml" MIME body. +NOTE 8: This header field is only applicable on non-roaming II-NNI. + +##### 6.1.1.3.2 Derivation of applicable SIP header fields from 3GPP TS 24.229 [5] + +For any method in table 6.1, the SIP header fields applicable on the II-NNI are detailed in the corresponding method tables for the UA role and proxy role sending behaviour in annex A of 3GPP TS 24.229 [5]. Unless other information is specified in the normative part of the present specification, the applicability of header fields at the II-NNI can be derived for each method from the corresponding tables in annex A of 3GPP TS 24.229 [5] as follows: + +- All header fields not present in the corresponding tables in annex A of 3GPP TS 24.229 [5] or marked as "n/a" in both the "RFC status" and "profile status" columns for the UA role and proxy role sending behaviour of that tables are not applicable at the II-NNI. + +NOTE 1: Operators could choose to apply header fields for other SIP extensions on an II-NNI based on bilateral agreements, but this is outside the scope of the present specification. + +- All header fields which are marked as "o" in at least one of the "RFC status" or the "profile status" profile columns for the sending behaviour in the corresponding UA role and proxy role tables in annex A of 3GPP TS 24.229 [5] and as "n/a" or "o" in the other such columns are applicable at II-NNI based on bilateral agreement between operators. +- All header fields which are marked as "m" in at least one of the "RFC status" or the "profile status" columns for the sending behaviour in the corresponding UA role or proxy role table in annex A of 3GPP TS 24.229 [5] and as "n/a", "o", or "m" in the other such columns are applicable at the II-NNI. +- If conditions are specified, they are also applicable at the II-NNI and the above rules are applicable to the "n/a", "o" and "m" values within the conditions. + +NOTE 2: In the above rules, the RFC profile columns are taken into account in order to enable interworking with non-3GPP networks. + +An informative summary of SIP header fields to be used over the II-NNI is proposed in annex A. + +##### 6.1.1.3.3 Applicability of SIP header fields on a roaming II-NNI + +The following SIP header fields are applicable on a roaming II-NNI but not on a non-roaming II-NNI: + +- Authentication-Info +- Authorization +- P-Associated-URI +- P-Called-Party-ID + +- P-Preferred-Service +- P-Profile-Key +- P-Served-User +- P-Visited-Network-ID +- Path +- Priority-Share +- Proxy-Authenticate +- Proxy-Authorization +- Resource-Share +- Restoration-Info +- Service-Route +- WWW-Authenticate + +##### 6.1.1.3.4 Applicability of SIP header fields on a non-roaming II-NNI + +The following SIP header fields are only applicable on a non-roaming II-NNI: + +- P-Refused-URI-List; +- Identity; +- Attestation-Info; and +- Origination-Id. + +#### 6.1.1.4 Notations of the codes + +In the table 6.1 the status codes "m", "o", "c" and "n/a" have the following meanings: + +**Table 6.3: Key to notation codes for SIP messages** + +| Notation code | Notation name | Sending side | Receiving side | +|----------------|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| m | mandatory | The message shall be supported at II-NNI.
Supporting sending a SIP message at the II-NNI means that this message shall be sent over the II-NNI if received from the serving network. It does not imply that network elements inside the serving network or user equipment connected to this network shall support this message. | Supporting receiving a SIP message at the II-NNI means that this message shall be forwarded to the serving network unless the operator's policy is applied as defined in clause 5.10.1 of 3GPP TS 24.229 [5]. It does not imply that network elements inside the serving network or user equipment connected to this network are supporting this message. | +| o | optional | The message may or may not be supported at II-NNI. The support of the message is provided based on bilateral agreement between the operators. | Same as for sending side. | +| n/a | not applicable | It is impossible to use/support the message. | It is impossible to use/support the message. This message will be discarded by the IBCF. | +| c
3GPP TS 24.229 [5] for
the profile status | Profile
status over
II-NNI | +|-------------|--------------------------------|----------------------------------------------------------------------------|-------------------------------------------| +|-------------|--------------------------------|----------------------------------------------------------------------------|-------------------------------------------| + +| | | UA Role
(NOTE 1) | Proxy role
(NOTE 2) | | +|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|--------------------------------------------|-----| +| | Basic SIP (IETF RFC 3261 [13]) | | | | +| 1 | registrations | 1, 2, 2A | - | c2 | +| 2 | initiating a session | 2B, 3, 4 | - | m | +| 3 | terminating a session | 5 | 3 | m | +| 4 | General proxy behaviour | - | 4, 5, 14, 15 | n/a | +| 5 | Managing several responses due to forking | 9,10 | 6 | m | +| 6 | support of indication of TLS connections in the Record-Route header | - | 7, 8 | n/a | +| 7 | Support of authentication | 7, 8, 8A | 8A | c2 | +| 8 | Timestamped requests (Timestamp header field) | 6 | - | m | +| 9 | Presence of date in requests and responses (Date header field) | 11 | 9 | m | +| 10 | Presence of alerting information data (Alert-info header field) | 12 | 10 | o | +| 11 | Support and handling of the Require header field for REGISTER and other requests or responses for methods other than REGISTER | - | 11, 12, 13 | m | +| 12 | Support and reading of the Supported and Unsupported header fields | - | 16, 17, 18 | m | +| 13 | Support of the Error-Info header field in 3xx - 6xx responses | - | 19 | o | +| 14 | Support and handling of the Organization header field | - | 19A, 19B | m | +| 15 | Support and handling of the Call-Info header field | - | 19C, 19D | m | +| 16 | Support of the Contact header field in 3xx response | - | 19E | m | +| 16A | Proxy reading the contents of a body or including a body in a request or response | - | 19F | n/a | +| | Extensions to basic SIP | | | | +| 16B | 3GPP TS 24.237 [131]: proxy modifying the content of a body | - | 19G | n/a | +| 17 | IETF RFC 6086 [39]: SIP INFO method and package framework | 13 | 20 | o | +| 17A | IETF RFC 6086 [39]: legacy INFO usage | 13A | 20A | o | +| 18 | IETF RFC 3262 [18]: reliability of provisional responses in SIP (PRACK method) | 14 | 21 | m | +| 19 | IETF RFC 3515 [22]: the SIP REFER method | 15 | 22 | o | +| 19A | IETF RFC 7647 [194]: Clarifications for the Use of REFER with RFC6665 | 15A | 22A | n/a | +| 19B | IETF RFC 7614 [195]: Explicit Subscriptions for the REFER Method | 15B | 22B | o | +| 20 | IETF RFC 3312 [40] and IETF RFC 4032 [41]: integration of resource management and SIP (Preconditions framework) | 2C, 16 | 23 | o | +| 21 | IETF RFC 3311 [23]: the SIP UPDATE method | 17 | 24 | m | +| 22 | IETF RFC 3313 [42]: SIP extensions for media authorization (P-Media-Authorization header field) | 19 | 26 | n/a | +| 23 | IETF RFC 6665 [20]: SIP specific event notification (SUBSCRIBE/NOTIFY methods) | 20, 22, 23 | 27 | c1 | +| 23A | IETF RFC 7621 [196]: A Clarification on the Use of Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol SIP Event Notification Framework | 22A | 28 | n/a | +| 24 | IETF RFC 3327 [43]: session initiation protocol extension header field for registering non-adjacent contacts (Path header field) | 24 | 29 | c2 | +| 25 | IETF RFC 3325 [44]: private extensions to the Session Initiation Protocol (SIP) for network asserted identity within trusted networks | 25 | 30 | c4 | +| 26 | IETF RFC 3325 [44]: the P-Preferred-Identity header field extension | - | - | n/a | +| 27 | IETF RFC 3325 [44]: the P-Asserted-Identity header field extension | - | - | c4 | +| 28 | IETF RFC 3323 [34], IETF RFC 3325 [44] and IETF RFC 7044 [25]: a privacy mechanism for the Session Initiation Protocol (SIP) (Privacy header field) | 26, 26A, 26B, 26C, 26D, 26E, 26F, 26G, 26H | 31, 31A, 31B, 31C, 31D, 31E, 31F, 31G, 31H | m | +| 29 | IETF RFC 3428 [19]: a messaging mechanism for the Session Initiation Protocol (SIP) (MESSAGE method) | 27 | 33 | o | + +| | | | | | +|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|----------------------------------|-----| +| 30 | IETF RFC 3608 [45]: session initiation protocol extension header field for service route discovery during registration (Service-Route header field) | 28 | 32 | c2 | +| 31 | IETF RFC 3486 [46]: compressing the session initiation protocol | 29 | 34 | n/a | +| 32 | IETF RFC 7315 [24]: private header extensions to the session initiation protocol for the 3 rd -Generation Partnership Project (3GPP) | 30 | 35 | o | +| 32A | IETF RFC 3325 [44]: act as first entity within the trust domain for asserted identity | 30A | 30A | n/a | +| 32B | IETF RFC 3325 [44]: act as entity within trust network that can route outside the trust network | 30B | 30B | n/a | +| 32C | IETF RFC 3325 [44]: act as entity passing on identity transparently independent of trust domain | 30C | 30C | n/a | +| 33 | IETF RFC 7315 [24] and IETF RFC 7976 [24A]: the P-Associated-URI header field extension | 31 | 36 | c2 | +| 34 | IETF RFC 7315 [24] and IETF RFC 7976 [24A]: the P-Called-Party-ID header field extension | 32 | 37 | c2 | +| 35 | IETF RFC 7315 [24] and IETF RFC 7976 [24A]: the P-Visited-Network-ID header field extension | 33 | 38, 39 | c2 | +| 36 | IETF RFC 7315 [24], IETF RFC 7976 [24A] and IETF RFC 7913 [24B]: the P-Access-Network-Info header field extension | 34 | 41, 42, 43 | c4 | +| 37 | IETF RFC 7315 [24] and IETF RFC 7976 [24A]: the P-Charging-Function-Addresses header field extension | 35 | 44, 44A | n/a | +| 38 | IETF RFC 7315 [24] and IETF RFC 7976 [24A]: the P-Charging-Vector header field extension | 36 | 45, 46 | c1 | +| 39 | IETF RFC 3329 [47]: security mechanism agreement for the session initiation protocol | 37 | 47 | n/a | +| 39A | 3GPP TS 24.229 [5] clause 7.2.A.7: Capability Exchange for Media Plane Security | 37A | 47A | n/a | +| 40 | IETF RFC 3326 [48]: the Reason header field for the session initiation protocol | 38 | 48 | o | +| 41 | IETF RFC 6432 [49]: carrying Q.850 codes in reason header fields in SIP (Session Initiation Protocol) responses | 38A | 48A | c4 | +| 41A | IETF RFC 8606 [214]: the Location Parameter for the SIP Reason Header Field | 38B | 48B | o | +| 42 | IETF RFC 3581 [50]: an extension to the session initiation protocol for symmetric response routing | 39 | 49 | o | +| 43 | IETF RFC 3841 [51]: caller preferences for the session initiation protocol (Accept-Contact, Reject-Contact and Request-Disposition header fields) | 40, 40A, 40B, 40C, 40D, 40E, 40F | 50, 50A, 50B, 50C, 50D, 50E, 50F | m | +| 44 | IETF RFC 3903 [21]: an event state publication extension to the session initiation protocol (PUBLISH method) | 41 | 51 | c1 | +| 45 | IETF RFC 4028 [52]: SIP session timer (Session-Expires and Min-SE headers) | 42 | 52 | m | +| 46 | IETF RFC 3892 [53]: the SIP Referred-By mechanism | 43 | 53 | m | +| 47 | IETF RFC 3891 [54]: the Session Initiation Protocol (SIP) "Replaces" header | 44 | 54 | o | +| 48 | IETF RFC 3911 [55]: the Session Initiation Protocol (SIP) "Join" header | 45 | 55 | o | +| 49 | IETF RFC 3840 [56]: the callee capabilities | 46 | 56 | o | +| 50 | IETF RFC 7044 [25]: an extension to the session initiation protocol for request history information (History-Info header field) | 47 | 57 | o | +| 50A | IETF RFC 7044 [25]: the "mp" header field parameter | 47A | 57A | o | +| 50B | IETF RFC 7044 [25]: the "rc" header field parameter | 47B | 57B | o | +| 50C | IETF RFC 7044 [25]: the "np" header field parameter | 47C | 57C | o | +| 51 | IETF RFC 5079 [57]: Rejecting anonymous requests in the session initiation protocol | 48 | 58 | o | +| 52 | IETF RFC 4458 [58]: session initiation protocol URIs for applications such as voicemail and interactive voice response (NOTE 3) | 49 | 59 | o | +| 52A | IETF RFC 8119 [193]: Session Initiation Protocol (SIP) Cause URI parameter for Service Number translation | 49A | 59A | o | +| 53 | IETF RFC 4320 [59]: Session Initiation Protocol's (SIP) non- | 50 | 61 | m | + +| | | | | | +|--|---------------------|--|--|--| +| | INVITE transactions | | | | +|--|---------------------|--|--|--| + +| | | | | | +|-----|----------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------|-------------------| +| 54 | IETF RFC 4457 [60]: the P-User-Database private header field extension | 51 | 60 | n/a | +| 55 | IETF RFC 5031 [61]: A Uniform Resource Name (URN) for Emergency and Other Well-Known Services | 52 | 62 | c7 | +| 56 | IETF RFC 5627 [62]: obtaining and using GRUUs in the Session Initiation Protocol (SIP) | 53 | 63 | c1 | +| 57 | Void | | | | +| 58 | IETF RFC 4168 [27]: the Stream Control Transmission Protocol (SCTP) as a Transport for the Session Initiation Protocol (SIP) | 55 | 65 | o | +| 59 | IETF RFC 5002 [64]: the SIP P-Profile-Key private header field extension | 56 | 66, 66A, 66B | c3 | +| 60 | IETF RFC 5626 [65]: managing client initiated connections in SIP | 57 | 67 | c1 | +| 61 | IETF RFC 5768 [66]: indicating support for interactive connectivity establishment in SIP | 58 | 68 | n/a | +| 62 | IETF RFC 5365 [67]: multiple-recipient MESSAGE requests in the session initiation protocol | 59 | 69 | o if 29, else n/a | +| 63 | IETF RFC 6442 [68]: Location conveyance for the Session Initiation Protocol | 60 | 70, 70A, 70B | m | +| 64 | IETF RFC 5368 [69]: referring to multiple resources in the session initiation protocol | 61 | 71 | o if 19, else n/a | +| 65 | IETF RFC 5366 [70]: conference establishment using request-contained lists in the session initiation protocol | 62 | 72 | o | +| 66 | IETF RFC 5367 [71]: subscriptions to request-contained resource lists in the session initiation protocol | 63 | 73 | o if 23, else n/a | +| 67 | IETF RFC 4967 [72]: dialstring parameter for the session initiation protocol uniform resource identifier | 64 | 74 | c2 | +| 68 | IETF RFC 4964 [73]: the P-Answer-State header extension to the session initiation protocol for the open mobile alliance push to talk over cellular | 65 | 75 | o | +| 69 | IETF RFC 5009 [74]: the SIP P-Early-Media private header field extension for authorization of early media | 66 | 76 | c4 | +| 70 | IETF RFC 4694 [75]: number portability parameters for the 'tel' URI | 67, 67A, 67B | 77, 77A, 77B | o | +| 71 | Void | | | | +| 72 | IETF RFC 4411 [77]: extending the session initiation protocol Reason header for preemption events | 69 | 79 | o | +| 73 | IETF RFC 4412 [78]: communications resource priority for the session initiation protocol (Resource-Priority header field) | 70, 70A, 70B | 80, 80A, 80B | o | +| 74 | IETF RFC 5393 [79]: addressing an amplification vulnerability in session initiation protocol forking proxies | 71 | 81 | m | +| 75 | IETF RFC 5049 [80]: the remote application identification of applying signalling compression to SIP | 72 | 82 | n/a | +| 76 | IETF RFC 5688 [81]: a session initiation protocol media feature tag for MIME application sub-types | 73 | 83 | c1 | +| 77 | IETF RFC 6050 [26]: Identification of communication services in the session initiation protocol | 74 | 84, 84A | o | +| 78 | IETF RFC 5360 [82]: a framework for consent-based communications in SIP | 75, 75A, 75B | 85 | o | +| 79 | IETF RFC 7433 [83]: a mechanism for transporting user-to-user call control information in SIP | 76 | 86 | c1 | +| 79A | IETF RFC 7434 [83A]: interworking ISDN call control user information with SIP | 76A | - | c1 | +| 80 | IETF RFC 7316 [84]: The SIP P-Private-Network-Indication private header (P-Header) | 77 | 87 | c1 | +| 81 | IETF RFC 5502 [85]: the SIP P-Served-User private header | 78 | 88 | c2 | +| 82 | IETF 8498 [203]: the SIP P-Served-User header extension for Originating CDIV session case | 79 | 89 | n/a | +| 83 | IETF RFC 8497 [87]: marking SIP messages to be logged | 80 | 90 | o | +| 84 | IETF RFC 6228 [88]: the 199 (Early Dialog Terminated) response code | 81 | 91 | m | +| 85 | IETF RFC 5621 [89]: message body handling in SIP | 82 | 92 | m | +| 86 | IETF RFC 6223 [90]: indication of support for keep-alive | 83 | 93 | o | +| 87 | IETF RFC 5552 [91]: SIP Interface to VoiceXML Media Services | 84 | 94 | n/a | +| 88 | IETF RFC 3862 [92]: common presence and instant | 85 | 95 | o | + +| | | | | | +|--|----------------------------------|--|--|--| +| | messaging (CPIM): message format | | | | +|--|----------------------------------|--|--|--| + +| | | | | | +|------|------------------------------------------------------------------------------------------------------------------------------------------|------|---------|-------------------| +| 89 | IETF RFC 5438 [93]: instant message disposition notification | 86 | 96 | o | +| 90 | IETF RFC 5373 [94]: requesting answering modes for SIP (Answer-Mode and Priv-Answer-Mode header fields) | 87 | 97, 97A | o | +| 91 | Void | | | | +| 92 | IETF RFC 3959 [96]: the early session disposition type for SIP | 89 | 99 | o | +| 93 | Void | | | | +| 94 | IETF RFC 7989 [124]: End-to-End Session Identification in IP-Based Multimedia Communication Networks | 91 | 101 | o | +| 95 | IETF RFC 6026 [125]: correct transaction handling for 200 responses to Session Initiation Protocol INVITE requests | 92 | 102 | m | +| 96 | IETF RFC 5658 [126]: addressing Record-Route issues in the Session Initiation Protocol (SIP) | 93 | 103 | o | +| 97 | IETF RFC 5954 [127]: essential correction for IPv6 ABNF and URI comparison in IETF RFC 3261 [13] | 94 | 104 | m | +| 98 | IETF RFC 4488 [135]: suppression of session initiation protocol REFER method implicit subscription | 95 | 105 | m if 19, else n/a | +| 99 | IETF RFC 7462 [136]: Alert-Info URNs for the Session Initiation Protocol | 96 | 106 | o | +| 100 | 3GPP TS 24.229 [5] clause 3.1: multiple registrations | 97 | 107 | c2 | +| 101 | IETF RFC 5318 [141]: the SIP P-Refused-URI-List private-header | 98 | 108 | c5 | +| 102 | IETF RFC 4538 [140]: request authorization through dialog identification in the session initiation protocol (Target-Dialog header field) | 99 | 109 | o | +| 103 | IETF RFC 6809 [143]: Mechanism to indicate support of features and capabilities in the Session Initiation Protocol (SIP) | 100 | 110 | o | +| 104 | IETF RFC 6140 [160]: registration of bulk number contacts | 101 | 111 | c3 | +| 105 | IETF RFC 6230 [161]: media control channel framework | 102 | 112 | o | +| 105A | 3GPP TS 24.229 [5] clause 4.14: S-CSCF restoration procedures | 103 | 113 | c3 | +| 106 | IETF RFC 6357 [164]: SIP overload control | 104 | 114 | o | +| 107 | IETF RFC 7339 [165]: feedback control | 104A | 114A | o | +| 108 | IETF RFC 7200 [167]: distribution of load filters | 104B | 114B | o | +| 109 | 3GPP TS 24.229 [5] clauses 5.1.2A.1.1, 5.1.3.1, 5.1.6.8, and 5.2.10: Handling of a 380 (Alternative service) response | 105 | 115 | n/a | +| 110 | IETF RFC 7090 [184]: Public Safety Answering Point (PSAP) Callback | 107 | 117 | o | +| 111 | IETF RFC 8055 [185]: Via header field parameter to indicate received realm | 106 | 116 | n/a | +| 112 | IETF RFC 7549 [188]: SIP URI parameter to indicate traffic leg | 108 | 118 | o
(NOTE 4) | +| 113 | 3GPP TS 24.229 [5] clause 4.14: PCF or PCRF based P-CSCF restoration | 109 | 119 | c3 | +| 114 | 3GPP TS 24.229 [5] clause 4.14: UDM/HSS or HSS based P-CSCF restoration | 110 | 120 | c3 | +| 115 | 3GPP TS 24.229 [5] clause 7.2.12: the Relayed-Charge header extension | 111 | 121 | n/a | +| 116 | 3GPP TS 24.229 [5]: resource sharing | 112 | 122 | c3 | +| 117 | 3GPP TS 24.229 [5] clause 7.2.15: the Cellular-Network-Info header extension | 113 | 123 | c4 | +| 118 | 3GPP TS 24.229 [5] clause 7.2.16: the Priority-Share header field | 114 | 124 | c3 | +| 119 | IETF RFC 8224 [206]: Authenticated Identity Management in the Session Initiation Protocol (SIP) | 116 | 126 | c5 | +| 120 | IETF RFC 8197 [207]: A SIP Response Code for Unwanted Calls | 117 | 127 | o | +| 121 | 3GPP TS 24.229 [5] clause 7.2.17: the Response-Source header extension | 115 | 125 | c6 | +| 121A | 3GPP TS 24.229 [5]: the 3GPP PS data off extension | 118 | - | c3 | +| 121B | 3GPP TS 24.229 [5]: Next-Generation Pan-European eCall emergency service | 120 | - | c8 | +| 122 | IETF RFC 8262 [216]: Content-ID Header Field in the Session Initiation Protocol (SIP) | 119 | - | o | +| 123 | 3GPP TS 24.229 [5] clause 7.2.18: the Attestation-Info header field | 121 | 128 | c5 | + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|-----|-----|----| +| 124 | 3GPP TS 24.229 [5] clause 7.2.19: the Origination-Id | 122 | 129 | c5 | +| 125 | 3GPP TS 24.229 [5] clause 4.18: Dynamic services interactions | 123 | 130 | c6 | +| 126 | 3GPP TS 24.229 [5] clause 7.2.20: the Additional-Identity | 124 | 131 | c6 | +| 127 | 3GPP TS 24.229 [5] clause 4.19: RLOS | 125 | 132 | c3 | +| c1: m in case of roaming II-NNI, else o
c2: m in case of roaming II-NNI, else n/a
c3: o in case of roaming II-NNI, else n/a
c4: m in case of trust relationship between the interconnected networks, else n/a
c5: o in case of non-roaming II-NNI and loopback traversal scenario, else n/a
c6: o in case of trust relationship between the interconnected networks, else n/a
c7: m in case of IMS emergency session traversal scenario on non-roaming II-NNI, else n/a
c8: o in case of IMS emergency session traversal scenario on non-roaming II-NNI, else n/a | | | | | +| NOTE 1: The item numbering corresponds to the one provided in table A.4 in 3GPP TS 24.229 [5]. | | | | | +| NOTE 2: The item numbering corresponds to the one provided in table A.162 in 3GPP TS 24.229 [5]. | | | | | +| NOTE 3: A common URI namespace is required to apply this feature on the II-NNI. | | | | | +| NOTE 4: For the roaming II-NNI the support of this major capability is recommended. | | | | | + +**Table 6.1.3.2: Key to notation codes for major capabilities** + +| Notation code | Notation name | Explanation | +|----------------|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| m | mandatory | The capability shall be supported at II-NNI.
SIP message relating to this capability shall be sent over the II-NNI if received from the serving network, unless they also make use of other unsupported capabilities.
SIP headers or other information elements relating to this capability shall be passed over the II-NNI if received from the sending side.
This does not imply that network elements inside the serving network or served network or user equipment connected to these networks shall support this capability. | +| o | optional | The capability may or may not be supported at II-NNI. The support of the capability is provided based on bilateral agreement between the operators. | +| n/a | not applicable | It is impossible to use/support the capability at the II-NNI. | +| c
clause 15.4,
clause 15.6.2,
clause 15.6.3,
clause 15.6.4,
clause 18.3.3 | IETF RFC 2046 [169] | +| 7 | multipart/related | clause 15.1,
clause 15.2,
clause 15.6.5 | IETF RFC 2387 [170] | +| 8 | multipart/alternative | - | IETF RFC 2046 [169] | +| 9 | application/pidf+xml | clause 15.1,
clause 28.2.3.2,
clause 28.2.9 | IETF RFC 3863 [174] | +| 10 | application/pidf-diff+xml | clause 15.1 | IETF RFC 5262 [179] | +| 11 | application/resource-lists+xml | clause 12.19,
clause 15.1,
clause 15.6.3,
clause 16.5,
clause 28.2.1,
clause 28.2.7 | IETF RFC 4826 [178] | +| 12 | application/rlmi+xml | clause 15.2,
clause 15.6.5 | IETF RFC 4662 [177] | +| 13 | application/sdp | - | IETF RFC 4566 [147] | +| 14 | application/simple-filter+xml | clause 15.1,
clause 15.6.4,
clause 28.2.3.2 | IETF RFC 4661 [176] | +| 15 | application/simple-message-summary+xml | clause 12.9 | IETF RFC 3842 [172] | +| 16 | message/sipfrag | clause 12.13,
clause 18.2,
clause 18.3.1 | IETF RFC 3420 [171] | +| 17 | application/vnd.3gpp.access-transfer-events+xml | clause 14.5.3 | 3GPP TS 24.237 [131], clause D.5.4 | +| 18 | application/vnd.3gpp.cw+xml | clause 12.7 | 3GPP TS 24.615 [37], clause C.1.1 | +| 19 | application/vnd.3gpp.iut+xml | clause 18.3.2,
clause 18.3.3 | 3GPP TS 24.337 [149], clause C.2.3 | +| 20 | application/vnd.3gpp.mid-call+xml | clause 14.4 | 3GPP TS 24.237 [131], clause D.1.3 | +| 21 | application/vnd.3gpp.replication+xml | clause 18.4.1,
clause 18.4.2 | 3GPP TS 24.337 [149], clause C.1.3 | +| 22 | application/vnd.3gpp.sms | - | | +| 23 | application/vnd.3gpp.srvcc-ext+xml | clause 14.5.1 | 3GPP TS 24.237 [131], clause D.4.4 | +| 24 | application/vnd.3gpp.srvcc-info+xml | clause 14.2.3 | 3GPP TS 24.237 [131], clause D.3.4 | +| 25 | application/vnd.3gpp.state-and-event-info+xml | clause 14.2.2,
clause 14.4 | 3GPP TS 24.237 [131], clause D.2.4 | +| 26 | application/vnd.3gpp.ussd | clause 12.24 | 3GPP TS 24.390 [163], clause 5.1.3 | +| 27 | application/vnd.etsi.aoc+xml | clause 12.22 | 3GPP TS 24.647 [122], clause E.1.1 | +| 28 | application/vnd.etsi.cug+xml | clause 12.16 | 3GPP TS 24.654 [103], clause 4.4.1 | +| 29 | application/vnd.etsi.mcid+xml | clause 12.2 | 3GPP TS 24.616 [33], clause 4.4 | +| 30 | application/vnd.etsi.pstn+xml | - | 3GPP TS 29.163 [168], clause F.2 | +| 31 | application/vnd.oma.suppnot+xml | clause 15.6.2,
clause 15.6.3 | OMA-SUP-XSD_prs_suppnotFilter-V1_0 [182] | +| 32 | application/watcherinfo+xml | clause 15.3 | IETF RFC 3858 [173] | +| 33 | application/xcap-diff+xml | clause 15.4,
clause 15.6.5 | IETF RFC 5874 [180] | +| 34 | application/session-info | - | 3GPP TS 29.163 [168], clause G.2 | +| 35 | application/load-control+xml | clause 21 | IETF RFC 7200 [167] | +| 36 | application/vnd.etsi.sci+xml | clause 11.3 | 3GPP TS 29.658 [186] | + +| | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------| +| 37 | text/plain | - | IETF RFC 2646 [197] | +| 38 | application/x-www-form-urlencoded | - | IETF RFC 1866 [198], clause 8.2.1 (NOTE 3) | +| 39 | application/vnd.3gpp.crs+xml | clause 12.15 | 3GPP TS 24.183 [98], clause D.1 | +| 40 | message/sip | - | IETF RFC 3261 [13] | +| 41 | application/vnd.3gpp.mcptt-info+xml | clause 28.2.1,
clause 28.2.3.2,
clause 28.2.3.3,
clause 28.2.4,
clause 28.2.5,
clause 28.2.6,
clause 28.2.7,
clause 28.2.9 | 3GPP TS 24.379 [201], clause F.1 | +| 42 | application/vnd.3gpp.mcptt-mbms-usage-info+xml | clause 28.2.2 | 3GPP TS 24.379 [201], clause F.2 | +| 42A | application/vnd.3gpp.mcvideo-mbms-usage-info+xml | clause 28.2.2 | 3GPP TS 24.281 [210], clause F.2 | +| 43 | application/vnd.3gpp.mcptt-location-info+xml | clause 28.2.2 | 3GPP TS 24.379 [201], clause F.3 | +| 43A | application/vnd.3gpp.mcvideo-location-info+xml | clause 28.2.2 | 3GPP TS 24.281 [210], clause F.3 | +| 44 | application/conference-info+xml | clause 12.19,
clause 28.2.4,
clause 16.5 | IETF RFC 4575 [204] | +| 45 | application/poc-settings+xml | clause 28.2.5 | IETF RFC 4354 [205] | +| 46 | application/vnd.3gpp.mcptt-floor-request+xml | clause 28.2.7 | 3GPP TS 24.379 [201], clause F.5 | +| 47 | application/vnd.3gpp.mcptt-affiliation-command+xml | clause 28.2.3.3 | 3GPP TS 24.379 [201], clause F.4 | +| 47A | application/vnd.3gpp.mcptt-signed+xml | clause 28.2.5,
clause 28.2.6 | 3GPP TS 24.379 [201], clause F.6 | +| 48 | application/call-completion | clause 12.11,
clause 12.12,
clause 12.23 | IETF RFC 6910 [208] | +| 49 | application/vnd.3gpp.mcvideo-info+xml | clause 28.2.1
clause 28.2.3.2,
clause 28.2.3.3,
clause 28.2.5,
clause 28.2.4,
clause 28.2.6, | 3GPP TS 24.281 [210], clause F.1 | +| 50 | application/vnd.3gpp.mcvideo-affiliation-command+xml | clause 28.2.3.3 | 3GPP TS 24.281 [210], clause F.4 | +| 51 | application/vnd.3gpp.mcdata-signalling | clause 28.2.1,
clause 28.2.8 | 3GPP TS 24.282 [211], clause E.1 | +| 52 | application/vnd.3gpp.mcdata-payload | clause 28.2.8 | 3GPP TS 24.282 [211], clause E.2 | +| 53 | application/vnd.3gpp.mcdata-info+xml | clause 28.2.1
clause 28.2.3.2,
clause 28.2.3.3,
clause 28.2.5,
clause 28.2.6,
clause 28.2.8 | 3GPP TS 24.282 [211], clause D.1.4 | +| 54 | application/vnd.3gpp.mcdata-affiliation-command+xml | clause 28.2.3.3 | 3GPP TS 24.282 [211], clause D.3.4 | +| NOTE 1: When no specific II-NNI requirements are defined, the II-NNI requirements may be derived from the additional information about MIME types in SIP requests and responses in annex A of 3GPP TS 24.229 [5]. | | | | +| NOTE 2: This column references the definition of the MIME body for informative purpose only, the usage is defined in other specifications not listed here. | | | | +| NOTE 3 The MIME body contains a string that is coded as described in the IETF RFC 1866 [198]. | | | | + +Applicable characteristics of the SIP message body MIMEs (i.e. the value(s) of Content-Disposition header field and Content-Language header field) over the II-NNI may be a subject of operator agreements. + +## 6.2 Control Plane Transport + +### 6.2.1 General + +The control plane transport of the II-NNI shall comply with clause 4.2A of 3GPP TS 24.229 [5]. + +Support of SCTP as specified in IETF RFC 4168 [27] is optional for an IBCF connected by II-NNI. Nevertheless this option is favourable if the operators would like to improve reliability over the Ici. + +## 6.3 SIP timers + +Table 6.3.1 shows values of SIP timers that should be supported at II-NNI. It contains the following items: + +- the first column, titled "SIP Timer", shows the timer names as defined in IETF RFC 3261 [13] or IETF RFC 6026 [125]; +- the second column reflects the timer meaning as defined in IETF RFC 3261 [13]; +- the third column reflects the reference to the proper clause in the IETF RFC 3261 [13] and in 3GPP TS 24.229 [5] and +- the final column lists the values recommended for the functional entities closest to the border of an II-NNI (see reference model in clause 5). + +Table 6.3.1 reports information from 3GPP TS 24.229 [5], table 7.7.1. Values between IM CN subsystem elements shown in the second column in 3GPP TS 24.229 [5], table 7.7.1 are applicable for the II-NNI and are reported in the fourth column of table 6.3.1. If there are any differences between table 6.3.1 and 3GPP TS 24.229 [5], table 7.7.1, the information within 3GPP TS 24.229 [5], table 7.7.1 is applicable. + +**Table 6.3.1: SIP timers at II-NNI** + +| SIP Timer | Meaning | Reference | Recommended values | +|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------|----------------------------------| +| T1 | RTT estimate | [13] clause 17.1.1.1
[5] table 7.7.1 | 500ms default
(see NOTE) | +| T2 | The maximum retransmit interval for non-INVITE requests and INVITE responses | [13] clause 17.1.2.2
[5] table 7.7.1 | 4s
(see NOTE) | +| T4 | Maximum duration a message will remain in the network | [13] clause 17.1.2.2
[5] table 7.7.1 | 5s
(see NOTE) | +| Timer A | INVITE request retransmit interval, for UDP only | [13] clause 17.1.1.2
[5] table 7.7.1 | initially T1 | +| Timer B | INVITE transaction timeout timer | [13] clause 17.1.1.2
[5] table 7.7.1 | 64*T1 | +| Timer C | proxy INVITE transaction timeout | [13] clause 16.6
[5] table 7.7.1 | > 3min | +| Timer D | Wait time for response retransmits | [13] clause 17.1.1.2
[5] table 7.7.1
[13] clause 17.1.1.2
[5] table 7.7.1 | > 32s for UDP
0s for TCP/SCTP | +| Timer E | non-INVITE request retransmit interval, UDP only | [13] clause 17.1.2.2
[5] table 7.7.1 | initially T1 | +| Timer F | non-INVITE transaction timeout timer | [13] clause 17.1.2.2
[5] table 7.7.1 | 64*T1 | +| Timer G | INVITE response retransmit interval | [13] clause 17.2.1
[5] table 7.7.1 | initially T1 | +| Timer H | Wait time for ACK receipt. | [13] clause 17.2.1
[5] table 7.7.1 | 64*T1 | +| Timer I | Wait time for ACK retransmits | [13] clause 17.2.1
[5] table 7.7.1
[13] clause 17.2.1
[5] table 7.7.1 | T4 for UDP
0s for TCP/SCTP | +| Timer J | Wait time for non-INVITE request retransmits | [13] clause 17.2.2
[5] table 7.7.1
[13] clause 17.2.2
[5] table 7.7.1 | 64*T1 for UDP
0s for TCP/SCTP | +| Timer K | Wait time for response retransmits | [13] clause 17.1.2.2
[5] table 7.7.1
[13] clause 17.1.2.2
[5] table 7.7.1 | T4 for UDP
0s for TCP/SCTP | +| Timer L | Wait time for accepted INVITE request retransmits | [125] clause 8.11
[5] table 7.7.1 | 64*T1 | +| Timer M | Wait time for retransmission of 2xx to INVITE or additional 2xx from other branches of a forked INVITE | [125] clause 8.11
[5] table 7.7.1 | 64*T1 | +| Timer N | Wait time for receipt of a NOTIFY request upon sending SUBSCRIBE | [20] clause 4.1.2
[5] table 7.7.1 | 64*T1 | +| NOTE: | As a network option, SIP T1 Timer's value can be extended, along with the necessary modifications of SIP T2 and SIP T4 Timer values, to take into account the specificities of the supported services when the MRFC and the controlling AS are under the control of the same operator and the controlling AS knows, based on local configuration, that the MRFC implements a longer value of SIP T1 Timer. | | | + +# 7 User plane Interconnection + +## 7.1 Media and Codec + +For "end-to-end" media session involving the II-NNI, the SIP/SDP codec negotiation procedure can be applied between IM CN subsystems using different media codecs. It is possible that the end-to-end codec negotiation could fail because no common codec could be supported by the UEs, in particular for voice services. + +To enhance interoperability, the IBCF, the MRFC, or other IMS network entities can interfere with the end-to-end codec negotiation to offer additional codec(s) available via transcoding, or to remove codecs. The IBCF can configure an attached TrGW to transcode, and the MRFC can configure an attached MRFP to transcode. + +Codecs applicable at the II-NNI may be a subject of interworking agreements. + +NOTE 1: Possible codecs which could be used at the II-NNI are described in 3GPP TS 26.114 [11] and ETSI TS 181 005 [12]. + +NOTE 2: As described in 3GPP TS 24.229 [5], the IETF RFC 4733 [157] is used to encode DTMF events and a payload type number associated with the MIME subtype "telephone-event" is included in a SDP message. + +However, to avoid that transcoding is performed several times, applicable codecs at the II-NNI should be restricted as little as possible in the inter-operator agreements. It is not recommended to set only codecs which are not agreed to use by the inter-operator agreement into the SDP of the SIP message at the II-NNI. Whether it is allowed to offer codecs which are not included in the applicable codec list made by inter-operator agreements over the II-NNI is also determined by the inter-operator agreement if necessary. + +NOTE 3: Transcoding can be performed in an IMS network serving an SDP offerer or in an IMS network serving an SDP answerer. To avoid that transcoding is performed multiple times, inter-operator agreements can clarify if it is preferred that IMS network serving an SDP offerer (with respect to the initial offer-answer exchange) or IMS network serving an SDP answerer (with respect to the initial offer-answer exchange) modify an SDP offer to offer transcoding. Furthermore, if transcoding is ongoing then subsequent SDP negotiation should avoid adding transcoding steps as specified in 3GPP TS 24.229 [5] Annex T.2 steps G), H), and I). + +If the IBCF performs media transcoding control, the IBCF shall apply the related procedures in 3GPP TS 24.229 [5]. + +## 7.2 User Plane Transport + +The user plane transport of the II-NNI may use the protocols listed in table 7.2.1. Protocols that use UDP, RTP, SCTP or TCP as the underlying transport protocol may be used based on agreements between operators. The used protocols to transport media are negotiated by means of the SDP offer/answer procedure specified in IETF RFC 3264 [146]. + +**Table 7.2.1: Supported transport-level RFCs to be described in SIP/SDP messages** + +| Item | RFC | Title | Support | +|------|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| +| 1 | IETF RFC 3550 [151] | RTP: A Transport Protocol for Real-Time Applications | Mandatory | +| 2 | IETF RFC 768 [152] | User Datagram Protocol | Mandatory | +| 3 | IETF RFC 3551 [153] | RTP Profile for Audio and Video Conferences with Minimal Control | Mandatory | +| 4 | IETF RFC 3556 [154] | Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth | Mandatory | +| 5 | IETF RFC 4585 [155] | Extended RTP Profile for Real-time Transport Control Protocol (RTCP) - Based Feedback (RTP/AVPF) | Optional (NOTE 1) | +| 6 | IETF RFC 793 [156] | Transmission Control Protocol | Optional (NOTE 2) | +| 7 | IETF RFC 8841 [190] | Session Description Protocol (SDP) Offer/Answer Procedures for Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) Transport | Optional (NOTE 3) | + +NOTE 1: Used by MTSI, as indicated in 3GPP TS 26.114 [11]. +NOTE 2: Used for MSRP service. +NOTE 3: Used for data channel in telepresence using IMS, as indicated in 3GPP TS 24.103 [189]. + +# 8 Numbering, Naming and Addressing + +## 8.1 Numbering, Naming and Addressing for SIP message + +The following URI formats in SIP messages may be applied at the Icf as standardized in 3GPP TS 24.229 [5]: + +- SIP URI defined in IETF RFC 3261 [13]; +- tel URI defined in IETF RFC 3966 [14]; +- IM URI defined in IETF RFC 3860 [15]; and +- PRES URI defined in IETF RFC 3859 [16]. + +According to 3GPP TS 24.229 [5], the IBCF acting as an exit or entry point in the IMS network supports these URI formats. These URI formats shall be supported at the roaming II-NNI. The SIP URI format shall be supported at the non-roaming II-NNI. For the loopback traversal scenario both the SIP URI and the tel URI shall be supported. The tel URI, IM URI and PRES URI formats may be supported at the non-roaming II-NNI based on agreement between operators. For the loopback traversal scenario the IM URI and PRES URI may be supported based on agreement between operators. Other URI formats may be supported over the II-NNI depending on the operator agreements. + +A global number as defined in IETF RFC 3966 [14] shall be used in a tel URI or in the user portion of a SIP URI with the user=phone parameter when conveyed via a non-roaming II-NNI or for the loopback traversal scenario in the Request-URI and in the P-Asserted-Identity header field, except when agreement exists between the operators to also allow other kinds of numbers. + +NOTE 1: In a SIP URI the user portion of the Request-URI represents a telephone number only if the SIP URI includes the user=phone parameter. + +NOTE 2: Agreements can exist between operators to allow local number (e.g. national service numbers, business trunking numbers, or private numbers) at a non-roaming II-NNI or for the loopback traversal scenario. A SIP URI with such a number, a user=phone parameter, and a phone-context parameter agreed between the operators can then be used. + +NOTE 3: 3GPP TS 24.229 [5] allows to restrict the number within a SIP Request-URI with user=phone parameter at a non-roaming II-NNI or for the loopback traversal scenario to be a global number (i.e. E.164 in international format) via an appropriate Application Server. Suitable configuration by the operator is needed to achieve the desired modification of the format. + +NOTE 4: The allowed phone number formats in the P-Asserted-Identity header field of a served user are configured by the operator. According to 3GPP TS 23.003 [35], international E.164 format is used within a P-Asserted-Identity header field. + +NOTE 5: The global number format usage within a SIP Request-URI with the user=phone parameter at a non-roaming II-NNI or for the loopback traversal scenario allows the terminating network to find the called subscriber, via HSS interrogation, without any further number translation and thus improves the success of the interconnection between IMS operators. + +NOTE 6: According to 3GPP TS 23.003 [35] and 3GPP TS 24.229 [5], public user identity takes the form of either SIP URI or tel URI. + +NOTE 7: Agreements can exist between operators to allow the "Unavailable User Identity" as defined in 3GPP TS 23.003 [35] in the P-Asserted-Identity header field at a non-roaming II-NNI or for the loopback traversal scenario. + +The optional "oli" and "cpc" tel URI parameters associated with a tel URI or a SIP URI with user=phone are described in 3GPP TS 24.229 [5] clause 7.2A.12 and can be part of the P-Asserted-Identity header field. Depending on operator agreements, those URI parameters may be supported at the non-roaming II-NNI or for the loopback traversal scenario. + +The "sos" SIP URI parameter associated with a URI in the Contact header field of a REGISTER request or a 200 (OK) response to REGISTER request is described in 3GPP TS 24.229 [5]. The "sos" SIP URI parameter shall be supported at the roaming II-NNI. + +The "sos" SIP URI parameter associated with the Request-URI for all dialogs and standalone SIP requests described in clause 5.2.10.3 of 3GPP TS 24.229 [5] and shall be supported at the roaming II-NNI. + +The "rn" and "npdi" number portability parameters for the tel URI and the SIP URI with user=phone as described within IETF RFC 4694 [75] can be part of the Request-URI. Depending on operator agreements these parameters may be exchanged over the non-roaming II-NNI or for the loopback traversal scenario. + +NOTE 7: The "rn" and "npdi" parameters can be used to address the entry point of the terminating operator depending on national rules for number portability. + +The "isub" tel URI parameter for the tel URI and the SIP URI with user=phone as described within IETF RFC 3966 [14] can be part of the Request-URI, To header field and P-Asserted-Identity header field. Depending on operator agreements, this URI parameter may be exchanged over the II-NNI. + +The "premium-rate" tel URI parameter for the tel URI and the SIP URI with user=phone as described within 3GPP TS 24.229 [5] clause 7.2A.17 can be part of the Request-URI. Depending on operator agreements, this URI parameter may be exchanged at the roaming II-NNI. + +The public service identity (PSI) that takes a form of a SIP URI without including a port number as described in clause 13.5 of 3GPP TS 23.003 [35] may be exchanged over the II-NNI depending on operator agreements. + +## 8.2 Numbering, Naming and Addressing for SDP + +The following URI format in the SDP exchange may be applied at the Ici as standardized in 3GPP TS 24.229 [5]: + +- MSRP URI for a session of instant messages defined in IETF RFC 4975 [17]. + +This URI format shall be supported at the roaming II-NNI and may be supported at the non-roaming II-NNI and for the loopback traversal scenario based on agreement between operators. Other URI formats may be supported over the II-NNI depending on the operator's agreements. + +# --- 9 IP Version + +The network elements interconnected by means of the II-NNI may support IPv4 only, IPv6 only or both. + +The support of one or both of the IP versions is an operator option and should be based on bilateral agreement. + +In case IPv4 and IPv6 networks are interconnected, the involved IBCFs and TrGWs shall apply the IP version interworking procedures as indicated in 3GPP TS 29.162 [8]. + +# --- 10 Security + +The supported security mechanisms for IP signalling transport over II-NNI interfaces are described in 3GPP TS 33.210 [10]. + +# --- 11 Charging + +## 11.1 General + +The accounting information to be supported over the Ici is described in 3GPP TS 32.260 [29] and 3GPP TS 32.240 [183]. It shall be configurable by the operator to use or not the accounting mechanisms provided by the IBCF. + +## 11.2 Inter-operator accounting + +For inter-operator accounting, the procedures related to the P-Charging-Vector header field specified in 3GPP TS 24.229 [5] shall be supported over the II-NNI as further specified below. + +NOTE 1: The "icid-value" header field parameter identifying a dialog or a transaction outside a dialog is included in the P-Charging-Vector header field as specified in 3GPP TS 24.229 [5]. The "icid-value" header field parameter value of a SIP response to a SIP request is identical to the "icid-value" of the SIP request. + +For the roaming II-NNI: + +- the P-Charging-Vector header field in the REGISTER requests, initial SIP requests and stand-alone SIP requests, containing the type 1 "orig-ioi" with the entry which identifies the visited network; and +- the P-Charging-Vector header field in the REGISTER responses (except the 100 (Trying) response), SIP responses (except the 100 (Trying) response) to initial SIP requests and SIP stand-alone requests, containing type 1 "orig-ioi" and type 1 "term-ioi" header field parameters with the entries which identify the visited network and the home network respectively; + +shall be supported. + +NOTE 2: Operator network identifiers populated in the type 1 "orig-ioi" and type 1 "term-ioi" header field parameters need to be exchanged by inter-operator agreements in advance. + +For the II-NNI between IMS home networks: + +- the P-Charging-Vector header field in the SIP requests containing the type 2 "orig-ioi" with the entry which identifies the home originating network; and +- the P-Charging-Vector header field in the SIP responses (except the 100 (Trying) response) containing the type 2 "orig-ioi" and type 2 "term-ioi" header field parameters with the entries which identify the home originating network and the home terminating network respectively; + +may be supported based on inter-operator agreements. + +If the roaming architecture for voice over IMS with local breakout is used, for the II-NNI between the caller's visited network and the callee's home network except for the roaming II-NNI: + +- the P-Charging-Vector header field in the SIP requests containing the type 2 "orig-ioi" with the entry which identifies the visited originating network; and +- the P-Charging-Vector header field in the SIP responses (except the 100 (Trying) response) containing the type 2 "orig-ioi" and type 2 "term-ioi" header field parameters with the entries which identify the visited originating network and the home terminating network respectively; + +may be supported based on inter-operator agreements. + +NOTE 3: Operator network identifiers populated in the type 2 "orig-ioi" and type 2 "term-ioi" header field parameters need to be exchanged by inter-operator agreements in advance. + +For the II-NNI for the transit scenario: + +- the P-Charging-Vector header field in the SIP requests and responses (except the 100 (Trying) response) containing the "transit-ioi" header field parameter with the entry(ies) which identify the transit network(s); + +may be supported based on inter-operator agreements. + +NOTE 4: Operator network identifiers populated in the value(s) of "transit-ioi" header field parameter need to be exchanged by inter-operator agreements in advance. + +## 11.3 Transfer of IP multimedia service tariff information + +In order to assure the end-to-end service interoperability through the Inter-IMS Network to Network Interface (II-NNI), transfer of IP multimedia service tariff information as specified in 3GPP TS 29.658 [186] may be supported on the II-NNI between two IMS networks. The support of transfer of IP multimedia service tariff information is based on agreement between operators. + +If transfer of IP multimedia service tariff information is supported, the "application/vnd.etsi.sci+xml" MIME body with the Content-Disposition header field set to either "render" with the "handling" parameter set to "optional" or to "signal" + +with the "handling" parameter set to "required" or "optional" based on operator agreement in 18x responses to the INVITE request and in the INFO request shall be supported at the II-NNI. + +# --- 12 Supplementary services associated with the IMS multimedia telephony communication service + +## 12.1 General + +In order to assure the end-to-end service interoperability through the Inter-IMS Network to Network Interface (II-NNI), the associated supplementary services of the multimedia telephony communication service may be supported on the II-NNI between the two IMS networks. + +The MMTEL communication service is identified by means of the "urn:urn-7:3gpp-service.ims.icsi.mmtel" URN. The "urn:urn-7:3gpp-service.ims.icsi.mmtel" can appear in: + +- the media feature tag "g.3gpp.icsi-ref" (specified in 3GPP TS 24.229 [5] clause 7.2A.8) in the Contact header field and the Accept-Contact header field; +- the feature-capability indicator "g.3gpp.icsi-ref" (specified in 3GPP TS 24.229 [5] clause 7.9A.2) in the Feature-Caps header field; and +- the P-Asserted-Service header field. + +The support of each associated supplementary service is based on agreement between operators. + +If a supplementary service is supported, the related procedures from the 3GPP TS 22.173 [30], the protocol details from the 3GPP TS 24.173 [31] and specifications referenced in the 3GPP TS 24.173 [31] shall be applied with the requirements in the relevant clause below due to the crossing of the II-NNI. + +A classification of the importance of supplementary services applicable over the II-NNI is available in the informative annex Db of 3GPP TS 22.173 [30]. + +NOTE: Agreeing on interworking of entire class of services according to this classification can simplify the cooperation between interconnecting networks but remains optional. + +## 12.2 Malicious Communication Identification (MCID) + +Service specific requirements in accordance with 3GPP TS 24.616 [33] shall be supported over the II-NNI. + +The P-Asserted-Identity header field shall be supported at the II-NNI. + +The INFO request and the 200 (OK) response to the INFO request containing the "application/vnd.etsi.mcid+xml" MIME body defined in 3GPP TS 24.616 [33] may be supported at the II-NNI. + +If a network terminating the dialog supports MCID, the terminating network shall only deliver the MCID request in the "application/vnd.etsi.mcid+xml" MIME body, as specified in the 3GPP TS 24.616 [33], if an agreement to use the MCID supplementary service according to the 3GPP TS 24.616 [33] exists with the network originating the dialog and if the INVITE request received by the terminating network does not contain the information of the originating party. + +NOTE: The IBCF and the AS in the terminating network interact to deliver the MCID request only if an agreement to use the MCID supplementary service exists, as specified in 3GPP TS 24.616 [33] and 3GPP TS 24.229 [5]. + +The originating network and the terminating network shall have a bilateral agreement to support transportation of the minimum information specified in clause 4.5.2.5.0 of the 3GPP TS 24.616 [33] between the networks. + +## 12.3 Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) + +Service specific requirements in accordance with 3GPP TS 24.607 [32] and 3GPP TS 24.229 [5] shall be supported over the II-NNI. + +The P-Asserted-Identity header field and the Privacy header field with values "id", "user", "none", "header" and "critical" shall be supported at the II-NNI. + +- NOTE 1: P-Asserted-Identity header fields are intended for end-to-end operation. Removal of such header fields will impact the intended end-to-end operation between the end users. Where a trust relationship exists on the P-Asserted-Identity header field between the two IMS networks, this header field cannot be altered when passing through the II-NNI according to 3GPP TS 24.229 [5]. Where no trust relationship exists on the P-Asserted-Identity header field between the two IMS networks, the IBCF determines whether to remove the P-Asserted-Identity header field according to procedures described in 3GPP TS 24.229 [5] clause 4.4.2 referencing IETF RFC 3325 [44] and local policy rules for using additional screening capabilities as defined in 3GPP TS 24.229 [5] clause 5.10.6. +- NOTE 2: Where a trust relationship exists with the remote domain the From header field will be passed transparently by the IBCF. If a SIP request is received by the terminating network and the application of the OIR service is required with the value "user" for the Privacy header field then the From header field will be anonymised in accordance with IETF RFC 3323 [34] by the terminating network. Where no trust relationship exists with the remote domain, the From header field can be, based on local policy rules, anonymised by the IBCF of the originating network prior passing through the II-NNI using screening capabilities defined in 3GPP TS 24.229 [5] clause 5.10.6 and clause 5.10.8. +- NOTE 3: The privacy level "session" and "critical" are not used in the OIP/OIR service as described in 3GPP TS 24.607 [32]. + +SIP based user configuration as described in 3GPP TS 24.238 [100] shall be supported at the roaming II-NNI. + +## 12.4 Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) + +Service specific requirements in accordance with 3GPP TS 24.608 [113] shall be supported over the II-NNI. + +The P-Asserted-Identity header field and the Privacy header field with values "id", "user", "none", "header" and "critical" shall be supported at the II-NNI. + +- NOTE: P-Asserted-Identity header fields are intended for end-to-end operation. Removal of such header fields will impact the intended end-to-end operation between the end users. Where a trust relationship exists on the P-Asserted-Identity header field between the two IMS networks, this header field will be passed transparently through the II-NNI according to 3GPP TS 24.229 [5]. Where no trust relationship exists on the P-Asserted-Identity header field between the two IMS networks, the IBCF determines whether to remove the P-Asserted-Identity header field according to procedures described in 3GPP TS 24.229 [5] clause 4.4.2, referencing IETF RFC 3325 [44] and local policy rules for using additional screening capabilities as defined in 3GPP TS 24.229 [5] clause 5.10.6. + +The option tag "from-change" defined in IETF RFC 4916 [158], in the Supported header field should be supported at II-NNI. + +## 12.5 Anonymous Communication Rejection (ACR) + +Service specific requirements in accordance with 3GPP TS 24.611 [114] shall be supported over the II-NNI. + +The P-Asserted-Identity header field and the Privacy header field shall be supported at the II-NNI. + +Procedures as described in clause 12.21.4 are used to provide announcements. + +The response code 433 (Anonymity Disallowed) shall be supported at the II-NNI. + +SIP based user configuration as described in 3GPP TS 24.238 [100] shall be supported at the roaming II-NNI. + +## 12.6 Communication Diversion (CDIV) + +Service specific requirements in accordance with 3GPP TS 24.604 [117] shall be supported over the II-NNI. + +- NOTE 1: The support of the Diversion header field not adopted in 3GPP TS 24.604 [117] requires bilateral agreement between the operators. + +Procedures as described in clause 12.21.2 are used to provide announcements. + +The Privacy header field with a priv-value set to "history" included in the hi-targeted-to-uri or as a standalone header field shall be supported at the II-NNI. + +The History-Info header field as described by 3GPP TS 24.604 [117] containing an "mp" header field parameter as defined by IETF RFC 7044 [25] and a "cause" SIP URI parameter with cause values as defined by the IETF RFC 4458 [58] shall be supported over the II-NNI. + +NOTE 2: The networks can have an internal limit in the number of allowed diversions, as described in 3GPP TS 24.604 [117], clause 4.5.2.6.1. To ensure efficiency of this control operators can indicate in their bilateral agreements their own number of allowed communication diversions, the parameter that is used for counting, and the network behavior when the internal limit is reached. + +The response code 181 (Call Is Being Forwarded) shall be supported at the II-NNI. + +The MESSAGE request procedure for indication of communication diversion to the diverting user as specified in 3GPP TS 24.604 [117] and 3GPP TS 24.229 [5] should be supported at the roaming II-NNI. + +NOTE 3: The content of the MESSAGE request is operator specific. + +SIP based user configuration as described in 3GPP TS 24.238 [100] shall be supported at the roaming II-NNI. + +## 12.7 Communication Waiting (CW) + +Service specific requirements in accordance with 3GPP TS 24.615 [37] shall be supported over the II-NNI. + +The "application/vnd.3gpp.cw+xml" MIME body defined in 3GPP TS 24.615 [37] in the INVITE request shall be supported at the roaming II-NNI. + +The Alert-Info header field set to "urn:alert:service:call-waiting" in a 180 (Ringing) response shall be supported at the II-NNI. + +As a network option, in case of expiry of the CW timer, the response code 480 (Temporarily Unavailable) including a Reason header field containing the protocol value "Q.850" and the "cause" header field parameter set to "19" shall be supported at the non-roaming II-NNI and for the loopback traversal scenario. + +Procedures as described in clause 12.21.2 are used to provide announcements. + +## 12.8 Communication HOLD (HOLD) + +Service specific requirements in accordance with 3GPP TS 24.610 [36] shall be supported over the II-NNI. + +NOTE: The support of an alternative method not adopted in 3GPP TS 24.610 [36] requires bilateral agreement between the operators and is outside the scope of the present document. + +Procedures as described in clause 12.21.3 are used to provide announcements. + +## 12.9 Message Waiting Indication (MWI) + +Service specific requirements in accordance with 3GPP TS 24.606 [112] shall be supported over the II-NNI. + +The event package name "message-summary" in the Event header field according to IETF RFC 6665 [20] and 3GPP TS 24.229 [5] in the SUBSCRIBE request shall be supported at the roaming II-NNI. + +The "application/simple-message-summary" MIME body described in 3GPP TS 24.606 [112] in the NOTIFY request shall be supported at the roaming II-NNI. + +## 12.10 Communication Barring (CB) + +### 12.10.1 Incoming Communication Barring (ICB) + +Service specific requirements in accordance with 3GPP TS 24.611 [114] shall be supported over the II-NNI. + +Procedures as described in clause 12.21.4 are used to provide announcements. + +The response code 603 (Decline) including a Reason header field containing the protocol value set to "SIP" and the "cause" header field parameter set to value "603" as described in 3GPP TS 24.611 [114] shall be supported at the II-NNI. + +A Reason header field containing the protocol value set to "SIP" and the "cause" header field parameter set to value "603" as described in 3GPP TS 24.611 [114] included in the BYE request shall be supported at the II-NNI. + +SIP based user configuration as described in 3GPP TS 24.238 [100] shall be supported at the roaming II-NNI. + +If the option IIFC (Inhibition of Incoming Forwarded Calls) is supported the transparency of information related to communication diversion (see clause 12.6) shall be supported at II-NNI. + +### 12.10.2 Outgoing Communication Barring (OCB) + +Service specific requirements in accordance with 3GPP TS 24.611 [114] shall be supported over the II-NNI. + +Procedures as described in clause 12.21.4 are used to provide announcements. + +The response code 603 (Decline) including a Reason header field containing the protocol value set to "SIP" and the "cause" header field parameter set to "603" as described in 3GPP TS 24.611 [114] shall be supported at the roaming II-NNI. + +SIP based user configuration as described in 3GPP TS 24.238 [100] shall be supported at the roaming II-NNI. + +## 12.11 Completion of Communications to Busy Subscriber (CCBS) + +Service specific requirements in accordance with 3GPP TS 24.642 [109] shall be supported over the II-NNI. + +The response code 486 (Busy Here) containing a Call-Info header field with a "purpose" header field parameter set to "call-completion" and the "m" parameter set to "BS" shall be supported at the non-roaming II-NNI and for the loopback traversal scenario. + +For invoking and revoking of the CCBS supplementary service, announcement procedures shall be used to provide announcements and inband-interaction procedures as described in clause 12.21.3 and clause 12.21.4 shall be supported at the roaming II-NNI. + +The response code 199 (Early Dialog Terminated) shall be supported at the roaming II-NNI. + +Basic call procedures and in case of a call-completion recall initiated by a REFER request, normal REFER method handling procedures according to 3GPP TS 24.229 [5] shall be supported at the roaming II-NNI. + +As a network option the special REFER request handling procedures according to 3GPP TS 24.628 [38] should be supported at the roaming II-NNI. + +NOTE 1: 3rd party call control procedures can be used when the REFER request is not supported at the II-NNI. + +NOTE 2: A REFER request can be rejected by IBCF based on operator policy as specified by 3GPP TS 24.229 [5]. + +The SUBSCRIBE and NOTIFY methods according to IETF RFC 6665 [20] and 3GPP TS 24.229 [5] containing the event package name "call-completion" in the Event header field and the Call-Info header field with a purpose parameter set to 'call-completion' and the m parameter set to "BS" shall be supported at the non-roaming II-NNI and for the loopback traversal scenario. + +The NOTIFY request containing the "application/call-completion" MIME body as defined in IETF RFC 6910 [208] shall be supported at the non-roaming II-NNI. + +The Request-URI with the "m" SIP URI parameter with a value set to "BS" and the Call-Info header field with a purpose parameter set to 'call-completion' and the "m" parameter set to "BS" in the INVITE method shall be supported at the non-roaming II-NNI and for the loopback traversal scenario. + +The Date header field in the 486 (Busy Here) response to the INVITE request shall be supported at the roaming II-NNI. + +SIP based user configuration as described in 3GPP TS 24.238 [100] shall be supported at the roaming II-NNI. + +## 12.12 Completion of Communications by No Reply (CCNR) + +Service specific requirements in accordance with 3GPP TS 24.642 [109] shall be supported over the II-NNI. + +The response code 180 (Ringing) containing a Call-Info header field with a purpose parameter set to 'call-completion' and the "m" parameter set to "NR" shall be supported at the non-roaming II-NNI and for the loopback traversal scenario. + +For invoking and revoking of the CCNR supplementary service, announcement procedures shall be used to provide announcements and inband-interaction procedures as described in clause 12.21.3 and clause 12.21.4 shall be supported at the roaming II-NNI. + +The response code 199 (Early Dialog Terminated) shall be supported at the roaming II-NNI. + +Basic call procedures and in case of a call-completion recall initiated by a REFER request, normal REFER method handling procedures according to 3GPP TS 24.229 [5] shall be supported at the roaming II-NNI. + +As a network option the special REFER request handling procedures according to 3GPP TS 24.628 [38] should be supported at the roaming II-NNI. + +NOTE 1: 3rd party call control procedures can be used when the REFER request is not supported at the II-NNI. + +NOTE 2: A REFER request can be rejected by IBCF based on operator policy as specified by 3GPP TS 24.229 [5]. + +The SUBSCRIBE and NOTIFY methods according to IETF RFC 6665 [20] and 3GPP TS 24.229 [5] containing the event package name "call-completion" in the Event header field and the Call-Info header field with a purpose parameter set to 'call-completion' and the m parameter set to "NR" shall be supported at the non-roaming II-NNI and for the loopback traversal scenario. + +The NOTIFY request containing the "application/call-completion" MIME body as defined in IETF RFC 6910 [208] shall be supported at the non-roaming II-NNI. + +The Request-URI with the "m" SIP URI parameter with a value set to "NR" and the Call-Info header field with a purpose parameter set to 'call-completion' and the "m" parameter set to "NR" in the INVITE method shall be supported at the non-roaming II-NNI and for the loopback traversal scenario. + +The Date header field in the 480 (Temporarily Unavailable) response to the INVITE request shall be supported at the roaming II-NNI. + +SIP based user configuration as described in 3GPP TS 24.238 [100] shall be supported at the roaming II-NNI. + +## 12.13 Explicit Communication Transfer (ECT) + +### 12.13.1 Consultative and blind transfer + +Service specific requirements in accordance with 3GPP TS 24.629 [116] shall be supported over the II-NNI. + +The REFER method, the Referred-By header field and the Replaces header field as specified in 3GPP TS 24.629 [116] and the NOTIFY method containing an "application/sipfrag" MIME body shall be supported at the II-NNI for call transfer without third party call control. + +The REFER method, the Referred-By header field and the Replaces header field as specified in 3GPP TS 24.629 [116] and the NOTIFY method containing an "application/sipfrag" MIME body shall be supported at the roaming II-NNI for call transfer with third party call control. + +The Refer-To URI header parameter in the REFER request containing the Require header field set to "replaces" shall be supported at the roaming II-NNI. + +The Replaces header field in the INVITE request shall be supported at the non-roaming II-NNI and for the loopback traversal scenario. + +### 12.13.2 Assured transfer + +The requirements for the assured transfer are the same as in clause 12.13.1 with the additional requirements in this subclause. + +An Expires header field parameter in the Refer-To URI of the REFER Request shall be supported at the II-NNI for call transfer without third party call control. + +An Expires header field parameter in the Refer-To URI of the REFER Request shall be supported at the roaming II-NNI for call transfer with third party call control. + +The Refer-To header field in the REFER request containing the method parameter set to "CANCEL" shall be supported at the II-NNI for call transfer without third party call control. + +The Refer-To header field in the REFER request containing the method parameter set to "CANCEL" shall be supported at the roaming II-NNI with third party call control. + +## 12.14 Customized Alerting Tone (CAT) + +Service specific requirements in accordance with 3GPP TS 24.182 [129] shall be supported over the II-NNI. + +The P-Early-Media header field as described in 3GPP TS 24.182 [129] shall be supported at the II-NNI. + +The response code 180 (Ringing) and the response code 183 (Session Progress) including a P-Early-Media header field shall be supported over the II-NNI. + +The response code 199 (Early Dialog Terminated) shall be supported over the II-NNI. + +The Supported header field and the Require header field with "early-session" option-tag shall be supported at the II-NNI, if the early session model is supported. + +An "application/sdp" MIME body with the Content-Disposition header field set to "early-session" as specified in IETF RFC 3959 [96] shall be supported at II-NNI, if the early session model is supported. + +A SDP "a=content" attribute with a "g.3gpp.cat" value in the 18x responses shall be supported at the II-NNI. + +The SIP INFO mechanism for DTMF transport, as defined in 3GPP TS 24.229 [5] may be supported at the roaming II-NNI. + +NOTE 1: For telephone-event based DTMF transport, the DTMF digits are sent as media and not visible in the control plane. + +NOTE 2: Multiple methods for DTMF transport are defined in 3GPP TS 24.182 [129]. + +SIP based user configuration as described in 3GPP TS 24.238 [100] shall be supported at the roaming II-NNI. + +## 12.15 Customized Ringing Signal (CRS) + +Service specific requirements in accordance with 3GPP TS 24.183 [98] shall be supported over the II-NNI. + +An Alert-Info header field in the initial INVITE request containing an URI followed by a URN "urn:alert:service:crs" shall be supported at the II-NNI. + +An "application/vnd.3gpp.crs+xml" MIME body in the initial INVITE request shall be supported at the II-NNI. + +A SDP "a=content" attribute with a "g.3gpp.crs" value in the PRACK request or the re-INVITE request may be supported at the II-NNI. + +The Supported header field and the Require header field with "early-session" option-tag may be supported at the II-NNI. + +An "application/sdp" MIME body with the Content-Disposition header field set to "early-session" as specified in IETF RFC 3959 [96] may be supported at II-NNI. + +The SIP INFO mechanism for DTMF transport, as defined in 3GPP TS 24.229 [5] may be supported at the II-NNI. + +NOTE: For telephone-event based DTMF transport, the DTMF digits are sent as media and not visible in the control plane. + +SIP based user configuration as described in 3GPP TS 24.238 [100] shall be supported at the roaming II-NNI. + +## 12.16 Closed User Group (CUG) + +Service specific requirements in accordance with 3GPP TS 24.654 [103] shall be supported over the II-NNI. + +The "application/vnd.etsi.cug+xml" MIME body as specified 3GPP TS 24.654 [103] shall be supported in INVITE requests at the II-NNI. + +NOTE: If no agreement between the originating network and the terminating network exists to support the CUG supplementary service the INVITE request is rejected as described in IETF RFC 5621 [89] when the "handling" parameter in the Content-Disposition header field of the " application/vnd.etsi.cug+xml" MIME body is set to "required". + +The 403 (Forbidden) response, the 603 (Decline) response and the 500 (Server Internal Error) response shall be supported at II-NNI. + +SIP based user configuration as described in 3GPP TS 24.238 [100] shall be supported at the roaming II-NNI. + +## 12.17 Personal Network Management (PNM) + +Service specific requirements in accordance with 3GPP TS 24.259 [99] shall be supported over the II-NNI. + +A "g.3gpp.iari\_ref" feature tag with the value "urn:urn-7:3gpp-application.ims.iari.pnm-controller" in the Contact header field of the REGISTER request shall be supported at the roaming II-NNI. + +A "g.3gpp.iari\_ref" feature tag with the value "urn:urn-7:3gpp-application.ims.iari.pnm-controller" in the Accept-Contact header field shall be supported at the II-NNI. + +The History-Info header field shall be supported at II-NNI. + +A "histinfo" option tag as described by 3GPP TS 24.259 [99] in the Supported header field shall be supported at II-NNI. + +## 12.18 Three-Party (3PTY) + +Service specific requirements in accordance with 3GPP TS 24.605 [105] shall be supported over the II-NNI. + +NOTE 1: The requirements below can be relaxed by bilateral agreements between operators. + +The requirements for the 3PTY supplementary service are the same as for the CONF supplementary service specified in clause 12.19 with the following additional requirement: + +- If a REFER request is supported at the II-NNI, a Replaces header field in the header portion of the SIP URI of the Refer-to header field of the REFER request shall also be supported at II-NNI. + +NOTE 2: Clause 12.19 describes the conditions for the support of the REFER request. + +## 12.19 Conference (CONF) + +Service specific requirements in accordance with 3GPP TS 24.605 [105] and 3GPP TS 24.147 [106] shall be supported over the II-NNI. + +NOTE 1: The requirements below can be relaxed by bilateral agreements between operators. + +The REFER request shall be supported at the roaming II-NNI in the direction from visited to home network. Based on inter-operator agreement, the REFER request may be supported at the non-roaming II-NNI, for the loopback traversal scenario, and at the roaming II-NNI in the direction from home network to visited network. + +NOTE 2: If the REFER request is not supported at the non-roaming II-NNI, for the loopback traversal scenario, or at the roaming II-NNI in the direction from home network to visited network, an attempt of an UE to send the REFER directly to peers to invite them to a conference without involvement of the conference focus can fail over such an II-NNI. However such failures can also occur if a peer is located in a circuit switched network, or if a peer does not support the REFER method. An operator can avoid such failures by configuring an AS to convert the REFER to an INVITE, as detailed in 3GPP TS 24.628 [38]. Information on security risks associated with the REFER request is provided within the "security consideration" of IETF RFC 3515 [22]. + +NOTE 3: A REFER request can be rejected by IBCF based on operator policy as specified by 3GPP TS 24.229 [5]. + +The "application/resource-lists+xml" MIME body in the INVITE request shall be supported at the roaming II-NNI. + +The Referred-By header field in the INVITE request shall be supported at the II-NNI. + +The "isfocus" feature parameter indicated in Contact header field of the INVITE request and in the 200 (OK) response shall be supported at the II-NNI. + +The SUBSCRIBE request including the "conference" event package name in the Event header field and the Accept header field containing an "application/conference-info+xml" MIME type shall be supported at the II-NNI. + +The NOTIFY request including an "application/conference-info+xml" MIME body shall be supported at the II-NNI. + +NOTE 4: The subscription to "conference event" package does not apply at the roaming II-NNI between the MSC Server enhanced for ICS/MSC Server enhanced for SRVCC/MSC server enhanced for dual radio and the IMS network where the communication is anchored. + +The Allow-Events header field in the INVITE request with the value "conference" shall be supported at the roaming II-NNI and may be supported at the non-roaming II-NNI and for the loopback traversal scenario. + +## 12.20 Flexible Alerting (FA) + +Service specific requirements in accordance with 3GPP TS 24.239 [101] shall be supported over the II-NNI. + +The 486 (Busy Here) response code shall be supported at the II-NNI. + +SIP based user configuration as described in 3GPP TS 24.238 [100] shall be supported at the roaming II-NNI. + +## 12.21 Announcements + +### 12.21.1 General + +Announcements may be provided during the establishment of a communication session, during an established communication session or when a communication request is rejected. All of them shall be managed over the II-NNI. + +### 12.21.2 Providing announcements during the establishment of a communication session + +Procedures as described in 3GPP TS 24.628 [38] are used to provide announcements during the establishment of a communication session. + +There are two methods defined in 3GPP TS 24.628 [38] to provide the announcement: + +- 1) sending an announcement as an early media; and + +NOTE 1: There are two methods to use early media for sending the announcement in-band. First method is the gateway model defined by IETF RFC 3960 [150] and 3GPP TS 24.628 [38] annex G, second method is described in 3GPP TS 24.628 [38] annex D. + +- 2) sending an Alert-Info header field in 180 (Ringing) response to the INVITE request. + +The P-Early-Media header field authorizing early media as defined in IETF RFC 5009 [74] during the establishment of a communication shall be supported at the II-NNI. + +The Alert-Info header field in the 180 (Ringing) response to the INVITE request during the establishment of a communication, should be supported at the II-NNI. + +NOTE 2: The IBCF can decide to remove the Alert-Info header field if required by local policy. + +### 12.21.3 Providing announcements during an established communication session + +Procedures as described in 3GPP TS 24.628 [38] are used to provide announcements during an established communication session. + +In case of provision of an announcement to a user over the II-NNI during an established communication, the Call-Info header field in a re-INVITE request should be supported at the II-NNI. + +NOTE 1: An alternative method to provide announcements is to use the existing media stream. + +NOTE 2: The IBCF can decide to remove the Call-Info header field if required by local policy. + +### 12.21.4 Providing announcements when communication request is rejected + +Procedures as described in 3GPP TS 24.628 [38] are used to provide announcements when a communication request is rejected. + +There are three methods defined in 3GPP TS 24.628 [38] to provide the announcement: + +- 1) sending an announcement as an early media; + +NOTE 1: There are two methods to use early media for sending the announcement in-band. First method is the gateway model defined by IETF RFC 3960 [150] and 3GPP TS 24.628 [38] annex G, second method is described in 3GPP TS 24.628 [38] annex D. + +- 2) sending an Error-Info header field in the 3xx, 4xx, 5xx or 6xx response to the INVITE request; and + +- 3) accept the communication request and then provide the announcement. + +NOTE 2: The II-NNI requirements for accepting the communication request and then provide the announcement is not within the scope of this subclause. + +The P-Early-Media header field authorizing early media as defined in IETF RFC 5009 [74] and the Reason header field with the proper cause value shall be supported at the II-NNI. + +The Error-Info header field in the 3xx, 4xx, 5xx or 6xx response to the INVITE request when rejecting the communication request, should be supported at the II-NNI. + +NOTE 3: The IBCF can decide to remove the Error-Info header field if required by local policy. + +## 12.22 Advice Of Charge (AOC) + +Service specific requirements in accordance with 3GPP TS 24.647 [122] shall be supported over the II-NNI. + +The Accept header field with "application/vnd.etsi.aoc+xml" shall be supported at the roaming II-NNI. + +The INVITE method containing an "application/vnd.etsi.aoc+xml" MIME body shall be supported at the roaming II-NNI. + +Non-100 provisional responses and the 200 (OK) response to the initial INVITE request containing an "application/vnd.etsi.aoc+xml" MIME body shall be supported at the roaming II-NNI. + +The INFO method containing an "application/vnd.etsi.aoc+xml" MIME body shall be supported at the roaming II-NNI. + +The response code 504 (Server Time-out) shall be supported at the II-NNI. + +A Reason header field containing the protocol value set to "SIP" and the "cause" header field parameter set to "504" or containing the protocol value set to "Q.850" and the "cause" header field parameter set to "31" in the BYE method shall be supported at the II-NNI. + +An "application/vnd.etsi.aoc+xml" MIME body in the BYE request or the final response to the BYE request shall be supported over the roaming II-NNI. + +## 12.23 Completion of Communications on Not Logged-in (CCNL) + +Service specific requirements in accordance with 3GPP TS 24.642 [109] shall be supported over the II-NNI. + +The response code 480 (Temporarily unavailable) containing a Call-Info header field with a purpose parameter set to 'call-completion' and the "m" parameter set to "NL" shall be supported at the non-roaming II-NNI and for the loopback traversal scenario. + +For invoking and revoking of the CCNL supplementary service, announcement procedures shall be used to provide announcements and inband-interaction procedures as described in clause 12.21.3 and clause 12.21.4 shall be supported at the roaming II-NNI. + +The response code 199 (Early Dialog Terminated) shall be supported at the roaming II-NNI. + +Basic call procedures and in case of a call-completion recall initiated by a REFER request, normal REFER method handling procedures according to 3GPP TS 24.229 [5] shall be supported at the roaming II-NNI. + +As a network option the special REFER request handling procedures according to 3GPP TS 24.628 [38] should be supported at the roaming II-NNI. + +NOTE: 3rd party call control procedures can be used when the REFER request is not supported at the II-NNI. + +The SUBSCRIBE and NOTIFY methods according to IETF RFC 6665 [20] and 3GPP TS 24.229 [5] containing the event package name "call-completion" in the Event header field and the Call-Info header field with a purpose parameter set to 'call-completion' and the "m" parameter set to "NL" shall be supported at the non-roaming II-NNI and for the loopback traversal scenario. + +The NOTIFY request containing the "application/call-completion" MIME body as defined in IETF RFC 6910 [208] shall be supported at the non-roaming II-NNI. + +The Request-URI with the "m" SIP URI parameter with a value set to "NL" and the Call-Info header field with a purpose parameter set to 'call-completion' and the "m" parameter set to "NL" in the INVITE method shall be supported at the non-roaming II-NNI and for the loopback traversal scenario. + +The Date header field in the 480 (Temporarily Unavailable) response to the INVITE request shall be supported at the roaming II-NNI. + +SIP based user configuration as described in 3GPP TS 24.238 [100] shall be supported at the roaming II-NNI. + +## 12.24 Unstructured Supplementary Service Data (USSD) + +Service specific requirements in accordance with 3GPP TS 24.390 [163] shall be supported over the II-NNI. + +The Recv-Info header field containing the "g.3gpp.ussd" info package name and the "application/vnd.3gpp.ussd" MIME body as described in annex B of 3GPP TS 24.390 [163] in the INVITE request shall be supported at the roaming II-NNI. + +The Recv-Info header field containing the "g.3gpp.ussd" info package name in the 200 (OK) response to the INVITE request shall be supported at the roaming II-NNI. + +The INFO request containing "application/vnd.3gpp.ussd" MIME body and the Info-Package header field containing the "g.3gpp.ussd" info package name shall be supported at the roaming II-NNI. + +The "application/vnd.3gpp.ussd" MIME body in the BYE request shall be supported at the roaming II-NNI. + +## 12.25 Enhanced Calling Name (eCNAM) + +Service specific requirements in accordance with 3GPP TS 24.196 [217] shall be supported over the II-NNI. + +An initial INVITE request with: + +- a display-name in a From header field; + +- a display-name in a P-Asserted-Identity header field; and +- Call-Info header field(s), + +shall be supported at the roaming II-NNI in the direction from home to visited network. + +## 12.26 Multi-Device and Multi-Identity (MuD and MiD) + +### 12.26.1 Multi-Device (MuD) + +Service specific requirements in accordance with 3GPP TS 24.174 [218] shall be supported over the II-NNI. + +NOTE: No specific SIP signalling requirements exist for MuD over the II-NNI. + +### 12.26.2 Multi-Identity (MiD) + +Service specific requirements in accordance with 3GPP TS 24.174 [218] shall be supported over the II-NNI. + +An initial INVITE request, a REFER request and a MESSAGE request with an Additional-Identity header field (as defined in 3GPP TS 24.229 [5] subclause 7.2.20) shall be supported over the roaming II-NNI. + +# --- 13 Interoperability of IMS Centralized Services (ICS) over II-NNI + +## 13.1 General + +In order to assure the end-to-end service interoperability through the Inter-IMS Network to Network Interface (II-NNI), the associated service of the IMS Centralized Services (ICS) may be supported on the II-NNI between two IMS networks. The support of ICS is based on agreement between operators. + +If ICS is supported, the related procedures from the 3GPP TS 24.292 [121] and 3GPP TS 29.292 [130] shall be applied with the requirements in the clause 13.2 due to the crossing of the II-NNI. + +## 13.2 IMS Centralized Services (ICS) + +Service specific requirements in accordance with 3GPP TS 24.292 [121] and 3GPP TS 29.292 [130] shall be supported over the II-NNI. + +The "g.3gpp.ics" media feature tag in the Contact header field as specified in annex B of 3GPP TS 24.292 [121] shall be supported at the roaming II-NNI. + +The "g.3gpp.accesstype" media feature tag in the Contact header field as specified in annex B of 3GPP TS 24.292 [121] shall be supported at the roaming II-NNI. + +The "g.3gpp.icsi-ref" media feature tag as specified in 3GPP TS 24.229 [5] the value for the IMS Multimedia Telephony Communication Service as specified in 3GPP TS 24.173 [31] shall be supported at the roaming II-NNI. + +An Accept-Contact header field and a Reject-Contact header field including the media feature tag "g.3gpp.accesstype" and the media feature tag "g.3gpp.ics" in any combination in the INVITE request shall be supported at the roaming II-NNI. + +The Target-Dialog header field in the INVITE request shall be supported at the roaming II-NNI. + +The P-Early-Media header field in the INVITE request and in non-100 provisional responses to the INVITE request shall be supported on the roaming II-NNI. + +The Reason header field containing the protocol value "Q.850" and the header field parameter "cause" with a various set of values in the CANCEL request, the BYE request and in 4xx responses and 6xx responses to the INVITE request shall be supported at the roaming II-NNI. + +The REFER request with the "method" SIP URI parameter set to the value "BYE" or "INVITE" or without the "method" SIP URI parameter in the Refer-To header field as specified in 3GPP TS 24.292 [121] shall be supported at the roaming II-NNI. + +The Event header field containing the event package name "conference" and the Accept header field with "application/conference-info+xml" in a SUBSCRIBE request shall be supported at the roaming II-NNI. + +The Allow-Event header field with "application/conference-info+xml" in an INVITE request shall be supported at the roaming II-NNI. + +The "application/conference-info+xml" MIME body and the Event header field containing the event package name "conference" in a NOTIFY request shall be supported at the roaming II-NNI. + +NOTE: Supplementary services as specified in clause 12 can be supported based on agreement between operators. + +# --- 14 Interoperability of IMS Service Continuity over II-NNI + +## 14.1 General + +In order to assure the end-to-end service interoperability through the Inter-IMS Network to Network Interface (II-NNI), the associated services of the IMS Service Continuity may be supported on the II-NNI between two IMS networks. The support of each service is based on agreement between operators. + +If a service is supported, the related procedures from the 3GPP TS 24.237 [131] shall be applied with the requirements in the relevant clause below due to the crossing of the II-NNI. + +## 14.2 PS to CS Single Radio Voice Call Continuity (SRVCC) and Single Radio Video Call Continuity (vSRVCC) + +### 14.2.1 Basic PS to CS SRVCC + +Service specific requirements in accordance with 3GPP TS 24.237 [131] shall be supported over the roaming II-NNI. + +Media type "video" in SDP m-lines may be supported at the roaming II-NNI. Related SDP can appear in SDP offer answer exchanges within INVITE dialogues at the roaming II-NNI, and in responses to OPTIONS requests at the roaming II-NNI. If media type "video" is supported within INVITE dialogues at the roaming II-NNI, it shall also be supported within responses to OPTIONS requests at the roaming II-NNI. + +The "+g.3gpp.srvcc" header field parameter (specified in 3GPP TS 24.237 [131] annex C) in the Feature-Caps header field of the INVITE request and in non-100 provisional responses or the 2xx response should be supported at the roaming II-NNI. + +The Reason header field containing the protocol value set to "SIP" and "cause" header field parameter set to "487" in the re-INVITE request shall be supported at the roaming II-NNI. + +The Reason header field containing the protocol value set to "SIP" and "cause" header field parameter set to "503" in the BYE request shall be supported at the roaming II-NNI. + +Procedures as described in clause 14.4 are used to provide MSC server assisted mid-call features. + +### 14.2.2 PS to CS SRVCC for calls in alerting phase + +The requirements for the PS to CS transfer for alerting calls are the same as in clause 14.2.1 with the following additional requirements: + +The "g.3gpp.srvcc-alerting" media feature tag (described in 3GPP TS 24.237 [131] annex C) in a Contact header field of the INVITE request and in non-100 provisional responses and the 2xx response to the INVITE request shall be supported at the roaming II-NNI. + +The "+g.3gpp.srvcc-alerting" header field parameter (described in 3GPP TS 24.237 [131] annex C) included in a Feature-Caps header field as described in IETF RFC 6809 [143] in an INVITE request and in non-100 provisional + +responses and the 2xx response to the INVITE request or in the UPDATE request and in the 2xx response to the UPDATE request shall be supported at the roaming II-NNI. + +The Target-Dialog header field in the INVITE request shall be supported at the roaming II-NNI. + +An INFO request containing the Info-Package header field as specified in IETF RFC 6086 [39] with "3gpp.state-and-event" info package name and an "application/vnd.3gpp.state-and-event-info+xml" XML body shall be supported at the roaming II-NNI. + +### 14.2.3 Using the ATCF based architecture + +The requirements for the ATCF based architecture is the same as in clause 14.2.1 with the following additional requirements: + +The "+g.3gpp.atcf", the "+g.3gpp.atcf-mgmt-uri" and the "+g.3gpp.atcf-path" header field parameters (specified in 3GPP TS 24.237 [131] annex C) in the Feature-Caps header field of the REGISTER request as described in IETF RFC 6809 [143] shall be supported at the roaming II-NNI. + +A MESSAGE request containing the "application/vnd.3gpp.srvcc-info+xml" MIME body as defined in annex D of 3GPP TS 24.237 [131] shall be supported at the roaming II-NNI. + +The URIs of SCC ASs authorised to provide PS to CS SRVCC information in the MESSAGE request need to be specified in the roaming agreement. + +The Target-Dialog header field in the INVITE request shall be supported at the roaming II-NNI. + +### 14.2.4 PS to CS SRVCC for originating calls in pre-alerting phase + +The requirements for the PS to CS transfer for originating calls in pre-alerting phase are the same as in clause 14.2.1 and in clause 14.2.2 with the additional requirements in this subclause. + +NOTE: If PS to CS transfer for originating calls in pre-alerting phase is supported also PS to CS SRVCC for calls in alerting phase specified in clause 14.2.2 is supported. + +The "g.3gpp.ps2cs-srvcc-orig-pre-alerting" media feature tag described in 3GPP TS 24.237 [131] annex C in a Contact header field of the REGISTER request and in the INVITE request shall be supported at the roaming II-NNI. + +The "g.3gpp.ps2cs-srvcc-orig-pre-alerting" feature-capability indicator as described in 3GPP TS 24.237 [131] annex C in the Feature-Caps header field as described in IETF RFC 6809 [143] in non-100 provisional responses and the 2xx response to the INVITE request and in any target refresh request and in non-100 provisional responses or the 2xx response to target refresh request shall be supported at the roaming II-NNI. + +### 14.2.5 PS to CS SRVCC with the MSC server assisted mid-call feature + +The requirements for the PS to CS SRVCC with the assisted mid-call feature are the same as in clause 14.2.1 and in clause 14.4. + +### 14.2.6 PS to CS SRVCC for terminating calls in pre-alerting phase + +The requirements for the PS to CS transfer for terminating calls in pre-alerting phase are the same as in subclause 14.2.1 and in subclause 14.2.2 with the additional requirements in this subclause. + +NOTE: If PS to CS transfer for terminating calls in pre-alerting phase is supported also PS to CS SRVCC for calls in alerting phase specified in subclause 14.2.2 is supported. + +The "g.3gpp.ps2cs-srvcc-term-pre-alerting" media feature tag described in 3GPP TS 24.237 [131] annex C in a Contact header field of the REGISTER request and in the INVITE request shall be supported at the roaming II-NNI. + +The g.3gpp.ps2cs-srvcc-term-pre-alerting feature-capability indicator as described in 3GPP TS 24.237 [131] annex C in the Feature-Caps header field as described in IETF RFC 6809 [143] in non-100 provisional responses and the 2xx response to the INVITE request and in any target refresh request and in non-100 provisional responses or the 2xx response to target refresh request shall be supported at the roaming II-NNI. + +## 14.3 Inter UE Transfer (IUT) + +IUT is described in clause 18. + +## 14.4 MSC server assisted mid-call feature + +Service specific requirements in accordance with 3GPP TS 24.237 [131] shall be supported over the roaming II-NNI. + +The Contact header field of the REGISTER request and the 200 (OK) response containing "g.3gpp.mid-call" media feature tag as described in annex C of 3GPP TS 24.237 [131] shall be supported at the roaming II-NNI. + +The Feature-Cap header field of the REGISTER request and the 200 (OK) response containing "+g.3gpp.mid-call" header field parameter specified in annex C of 3GPP TS 24.237 [131] shall be supported at the roaming II-NNI. + +The media feature tag "g.3gpp.accesstype" in the Contact header field of the REGISTER request shall be supported at roaming II-NNI. + +A Contact header field of the INVITE request and the 200 (OK) response containing the "g.3gpp.mid-call" media feature tag as described in annex C of 3GPP TS 24.237 [131] shall be supported at the roaming II-NNI. + +The "g.3gpp.mid-call" feature-capability indicator according to 3GPP TS 24.237 [131] annex C included in the Feature-Caps header field of the INVITE request, in responses to the INVITE request and in any target refresh request and in non-100 provisional responses or the 2xx response to target refresh request shall be supported at the roaming II-NNI. + +The Recv-Info header field containing the "g.3gpp.mid-call" package name in the INVITE request as specified in annex D of 3GPP TS 24.237 [131] shall be supported at the roaming II-NNI. + +An Accept header field in the INVITE request containing the MIME type "application/vnd.3gpp.mid-call+xml" as specified in clause D.1 of 3GPP TS 24.237 [131] shall be supported at the roaming II-NNI. + +The "application/vnd.3gpp.mid-call+xml" MIME body described in clause D.1.3 of 3GPP TS 24.237 [131] in the INVITE request shall be supported at the roaming II-NNI. + +The SUBSCRIBE request containing a "g.3gpp.mid-call" media feature tag in the Contact header field shall be supported at the roaming II-NNI. + +NOTE: The "g.3gpp.mid-call" media feature tag in the Contact header field of the SUBSCRIBE request may appear if the CONF supplementary service is supported at roaming II-NNI as described in clause 12.9. + +An INFO request containing the Info-Package header field as specified in IETF RFC 6086 [39] with "3gpp.state-and-event" info package name and an "application/vnd.3gpp.state-and-event-info+xml" XML body shall be supported at the roaming II-NNI. + +A REFER request sent inside an existing SIP dialog containing the "application/vnd.3gpp.mid-call+xml" MIME body specified in the clause D.1.3 of 3GPP TS 24.237 [131] shall be supported at the roaming II-NNI. + +The Contact header field of the REFER request and the 2xx response to the request containing "g.3gpp.mid-call" media feature tag as described in annex C of 3GPP TS 24.237 [131] shall be supported at the roaming II-NNI. + +The Target-Dialog header field in the INVITE request shall be supported at the roaming II-NNI. + +The communication HOLD supplementary service as specified in clause 12.8 for the roaming II-NNI shall be supported. + +The Allow-Event header field with "application/conference-info+xml" in an INVITE request shall be supported at the roaming II-NNI. + +The Event header field containing the event package name "conference" and the Accept header field with "application/conference-info+xml" in a SUBSCRIBE request shall be supported at the roaming II-NNI. + +The "application/conference-info+xml" MIME body and the Event header field containing the event package name "conference" in a NOTIFY request shall be supported at the roaming II-NNI. + +The REFER request with the "method" header field parameter set to the value "BYE" sent in the Refer-To header field shall be supported at the roaming II-NNI. + +## 14.5 CS to PS Single Radio Voice Call Continuity (SRVCC) + +### 14.5.1 Basic CS to PS SRVCC + +Service specific requirements in accordance with 3GPP TS 24.237 [131] shall be supported over the roaming II-NNI. + +Requirements for the ATCF based architecture at II-NNI as described in clause 14.2.3 shall be supported at the roaming II-NNI. + +Requirements for IMS Centralized Services (ICS) at II-NNI as described in clause 13 shall be supported at the roaming II-NNI. + +The "g.3gpp.cs2ps-srvcc" and "g.3gpp.path" media feature tags in the Contact header field of the REGISTER request shall be supported at the roaming II-NNI. + +The Feature-Caps header field with the "g.3gpp.cs2ps-srvcc" feature-capability indicator in the REGISTER request shall be supported at the roaming II-NNI. + +The MESSAGE request containing the Accept-Contact header field with the "g.3gpp.path" media feature tag and the "application/vnd.3gpp.srvcc-ext+xml" MIME body shall be supported at the roaming II-NNI. + +The URIs of SCC ASs authorised to provide CS to PS SRVCC information in the MESSAGE request need to be specified in the roaming agreement. + +### 14.5.2 CS to PS SRVCC for calls in alerting phase + +The requirements for the CS to PS SRVCC for calls in alerting phase are the same as in clause 14.5.1 with the following additional requirement: + +The "g.3gpp.cs2ps-srvcc-alerting" media feature tag in the Contact header field of the REGISTER request shall be supported at the roaming II-NNI. + +The REFER request sent inside an existing SIP dialog with the Refer-Sub header field and the "application/vnd.3gpp.state-and-event-info+xml" MIME body shall be supported at the roaming II-NNI. + +The INFO request with the Info-Package header field containing the "g.3gpp.state-and-event" package name and the "application/vnd.3gpp.state-and-event-info+xml" MIME body shall be supported at the roaming II-NNI. + +### 14.5.3 CS to PS SRVCC with the assisted mid-call feature + +The requirements for the CS to PS SRVCC with the assisted mid-call feature are the same as in clause 14.5.1 with the following additional requirement: + +The "application/vnd.3gpp.access-transfer-events+xml" MIME body in the REFER request shall be supported at the roaming II-NNI. + +## 14.6 PS to CS dual radio voice call continuity (DRVCC) + +### 14.6.1 Basic PS to CS DRVCC + +Service specific requirements in accordance with 3GPP TS 24.237 [131] shall be supported over the roaming II-NNI. + +The "g.3gpp.dynamic-stn" media feature tag according to 3GPP TS 24.237 [131] annex C included in the Contact header field of the INVITE request and in responses to the INVITE request shall be supported at the roaming II-NNI. + +The "g.3gpp.dynamic-stn" feature-capability indicator according to 3GPP TS 24.237 [131] annex C included in the Feature-Caps header field of the INVITE request, in responses to the INVITE request and in any target refresh request and in non-100 provisional responses or the 2xx response to target refresh request shall be supported at the roaming II-NNI. + +NOTE 1: The g.3gpp.dynamic-stn feature capability indicator from the home network contains an STN. The STN is a tel URI that the UE will use when establishing the call in CS. If the STN is known by the visited network the STN can also be used to identify that a call from a UE is a PS to CS dual radio access transfer allowing the visited network to suppress services and announcement that otherwise is executed during the CS call setup. The value of the tel URI STN needs to be communicated between operators when DRVCC is supported. + +The requirements for providing IMS Centralized Services (ICS) as described in clause 13.2 should be supported at the roaming II-NNI. + +NOTE 2: The support of IMS Centralized Services (ICS) as described in clause 13.2 is only needed if MSC servers in the visited network are enhanced for ICS. + +### 14.6.2 PS to CS DRVCC with the assisted mid-call feature + +The requirements for the PS to CS DRVCC with the assisted mid-call feature are the same as in clause 14.6.1 and in clause 14.4. + +NOTE: Transfer of an additional call requires the use of IMS Centralized Services (ICS). + +### 14.6.3 PS to CS DRVCC for calls in alerting phase + +The requirements for the PS to CS DRVCC for calls in alerting phase are the same as in clause 14.6.1 with the additional requirements in this subclause. + +The "g.3gpp.drvcc-alerting" media feature tag according to 3GPP TS 24.237 [131] annex C and IETF RFC 3840 [56] included in the Contact header field of the INVITE request and in responses to the INVITE request shall be supported at the roaming II-NNI. + +The "g.3gpp.drvcc-alerting" feature-capability indicator according to 3GPP TS 24.237 [131] annex C included in the Feature-Caps header field of the INVITE request, in responses to the INVITE request and in any target refresh request and in non-100 provisional responses or the 2xx response to target refresh request shall be supported at the roaming II-NNI. + +A 488 (Not Acceptable Here) response to the INVITE request without an SDP body shall be supported at the roaming II-NNI. + +### 14.6.4 PS to CS DRVCC for originating calls in pre-alerting phase + +The requirements for the PS to CS DRVCC for originating calls in pre-alerting phase are the same as in clause 14.6.1 and in clause 14.6.3 with the additional requirements in this subclause. + +The "g.3gpp.ps2cs-drvcc-orig-pre-alerting" media feature tag according to 3GPP TS 24.237 [131] annex C and IETF RFC 3840 [56] in the Contact header field of the INVITE request shall be supported at the roaming II-NNI. + +The "g.3gpp.ps2cs-drvcc-orig-pre-alerting" feature-capability indicator according to 3GPP TS 24.237 [131] annex C included in the Feature-Caps header field of the INVITE request, in responses to the INVITE request and in any target refresh request and in non-100 provisional responses or the 2xx response to target refresh request shall be supported at the roaming II-NNI. + +## 14.7 CS to PS Dual Radio Voice Call Continuity (DRVCC) + +### 14.7.1 Basic CS to PS DRVCC + +Service specific requirements in accordance with 3GPP TS 24.237 [131] shall be supported over the roaming II-NNI. + +The requirements for providing IMS Centralized Services (ICS) as described in clause 13.2 should be supported at the roaming II-NNI. + +NOTE: The support of IMS Centralized Services (ICS) as described in clause 13.2 is only needed if MSC servers in the visited network are enhanced for ICS. + +### 14.7.2 CS to PS DRVCC with the assisted mid-call feature + +The requirements for the PS to CS DRVCC with the assisted mid-call feature are the same as in clause 14.7.1 and in clause 14.4. + +### 14.7.3 CS to PS DRVCC for calls in alerting phase + +The requirements for the CS to PS DRVCC for calls in alerting phase are the same as in clause 14.7.1 with the additional requirements in this subclause. + +The "g.3gpp.cs2ps-drvcc-alerting" media feature tag as described included in the Contact header field of the INVITE request and in responses to the INVITE request shall be supported at the roaming II-NNI. + +The "g.3gpp.cs2ps-drvcc-alerting" feature-capability indicator according to 3GPP TS 24.237 [131] annex C included in the Feature-Caps header field of the INVITE request, in responses to the INVITE request and in any target refresh request and in non-100 provisional responses or the 2xx response to target refresh request shall be supported at the roaming II-NNI. + +A 488 (Not Acceptable Here) response to the INVITE request without an SDP body shall be supported at the roaming II-NNI. + +### 14.7.4 CS to PS DRVCC for originating calls in pre-alerting phase + +The requirements for the CS to PS DRVCC for originating calls in pre-alerting phase are the same as in clause 14.7.1 and in clause 14.7.3 with the following additional requirements: + +The "g.3gpp.cs2ps-drvcc-orig-pre-alerting" media feature tag according to 3GPP TS 24.237 [131] annex C and IETF RFC 3840 [56] in the Contact header field of the INVITE request shall be supported at the roaming II-NNI. + +The "g.3gpp.cs2ps-drvcc-orig-pre-alerting" feature-capability indicator according to 3GPP TS 24.237 [131] annex C included in the Feature-Caps header field of the INVITE request, in responses to the INVITE request and in any target refresh request and in non-100 provisional responses or the 2xx response to target refresh request shall be supported at the roaming II-NNI. + +## 14.8 PS to PS access transfer + +Service specific requirements in accordance with 3GPP TS 24.237 [131] clause 10 shall be supported over the roaming II-NNI. + +The "g.3gpp.pstops-sti" media feature tag in the Contact header field of the REGISTER request shall be supported at the roaming II-NNI. + +The INVITE request containing: + +- a) the "g.3gpp.ics" media feature tag; and +- b) either: + - the Replaces header field and the option tag value "replaces" in the Require header field; or + - the Target-Dialog header field and the option tag value "tdialog" in the Require header field, + +shall be supported at the roaming II-NNI. + +A Recv-Info header field containing the "g.3gpp.state-and-event" info package name in the 183 (Session Progress) response shall be supported at the roaming II-NNI. + +The INFO request containing the Info-Package header field as specified in IETF RFC 6086 [39] with the "g.3gpp.state-and-event" info package name and the "application/vnd.3gpp.state-and-event-info+xml" XML body shall be supported at the roaming II-NNI. + +# 15 Presence service + +## 15.0 General + +In order to assure the end-to-end service interoperability through the Inter-IMS Network to Network Interface (II-NNI), the associated functions of the Presence service may be supported on the II-NNI between two IMS networks. The support of each function is based on agreement between operators. + +If a function is supported, the related procedures from the 3GPP TS 24.141 [132] shall be applied with the requirements in the relevant clause below due to the crossing of the II-NNI. + +## 15.1 Subscription of presence information + +Service specific requirements in accordance with 3GPP TS 24.141 [132] shall be supported over the II-NNI. + +A PUBLISH request identifying the presentity using a SIP URI, a tel URI or a PRES URI and the Event header field with the value "presence" and containing an "application/pidf+xml" MIME body shall be supported at the roaming II-NNI. + +Additionally to the above and in any combination, a Content-Type header field with the value "multipart/related" and an "application/pidf-diff+xml" MIME body can be included in the PUBLISH request and shall be supported at the roaming II-NNI. + +A SUBSCRIBE request with a Request-URI containing a SIP URI, a tel URI or a pres URI, the Event header field set to "presence" and Accept header fields with values "application/pidf+xml" and "multipart/related" shall be supported at the II-NNI. + +Additionally to the above an "application/simple-filter+xml" MIME body can appear in the SUBSCRIBE request and shall be supported at the II-NNI. + +Additionally to the above and in any combination a Content-Type header field with the value "multipart/mixed" and an "application/resource-lists" MIME body can appear in the SUBSCRIBE request and shall be supported at the roaming II-NNI. + +A NOTIFY request including an Event header field with the value "presence" and an "application/pidf" MIME body shall be supported at the II-NNI. + +NOTE: The NOTIFY request can contain substantial amount of data and TCP is expected to be used as the transport protocol. + +The Allow-Events header field with the value "presence" shall be supported at the roaming II-NNI and may be supported at the non-roaming II-NNI. + +## 15.2 Watcher subscribing to Presence List + +Service specific requirements in accordance with 3GPP TS 24.141 [132] shall be supported over the II-NNI. + +The requirements for the watcher subscribing to the Presence List are the same as subscribing to presence information as specified in clause 15.1 with the following additional requirement: + +- The SUBSCRIBE request containing a Supported header field with the value "eventlist" shall also be supported at the roaming II-NNI; +- The SUBSCRIBE request containing a Accept header field with the value "application/rlmi+xml" shall be supported at the roaming II-NNI; +- A response code 200 (OK) to the SUBSCRIBE request containing the Require header field with the value "eventlist" shall be supported at the roaming II-NNI; and +- A NOTIFY message containing the "multipart/related" content type and an "application/rlmi+xml" MIME body shall be supported at the roaming II-NNI. + +NOTE: The NOTIFY request can contain substantial amount of data and TCP is expected to be used as the transport protocol. + +## 15.3 Subscription to Watcher Information + +Service specific requirements in accordance with 3GPP TS 24.141 [132] shall be supported over the II-NNI. + +A SUBSCRIBE request containing an Event header field with the value "presence.wininfo" and an Accept header field with value "application/watcherinfo+xml" shall be supported at the roaming II-NNI. + +A NOTIFY request containing the Event header field with the value "presence.wininfo" and an "application/watcherinfo+xml" MIME body shall be supported at the roaming II-NNI. + +NOTE: The NOTIFY request can contain substantial amount of data and TCP is expected to be used as the transport protocol. + +The Allow-Events header field with the value "presence.wininfo" shall be supported at the roaming II-NNI and may be supported at the non-roaming II-NNI. + +## 15.4 Subscription to state changes in XML documents + +Service specific requirements in accordance with 3GPP TS 24.141 [132] shall be supported over the II-NNI. + +A SUBSCRIBE request containing the Event header field with the value "xcap-diff" and parameters specified in IETF RFC 5875 [134], using the updated procedures from IETF RFC 6665 [20], shall be supported at the roaming II-NNI. + +A NOTIFY request containing the Event header field with the value "xcap-diff", the Content-Type header field with the value "multipart/mixed" and any MIME body shall be supported at the roaming II-NNI. + +NOTE: The NOTIFY request can contain substantial amount of data and TCP is expected to be the transport protocol. + +The Allow-Events header field with the value "xcap-diff" shall be supported at the roaming II-NNI and may be supported at the non-roaming II-NNI. + +For backward compatible reasons the Event header field with the value "ua-profile" should be supported at the roaming II-NNI. + +## 15.5 Presence enhancements specified in Open Mobile Alliance (OMA) Release 1.1 + +### 15.5.1 General + +In order to assure the end-to-end service interoperability through the Inter-IMS Network to Network Interface (II-NNI), the associated functions of the OMA Presence service may be supported on the II-NNI between two IMS networks. The support of each function is based on agreement between operators. + +If a function of the OMA Presence Release 1.1 is supported, the related procedures from the OMA-TS-Presence\_SIMPLE-V1\_1\_1 [142] shall be applied with the requirements in the relevant clause below due to the crossing of the II-NNI. + +### 15.5.2 OMA subscription of presence information + +The requirements for the OMA subscription of presence information are the same as clause 15.1. + +### 15.5.3 OMA watcher subscribing to Presence List + +The requirements for the OMA watcher subscribing to Presence List are the same as clause 15.2. + +### 15.5.4 OMA subscription to Watcher Information + +The requirements for the OMA subscription to Watcher Information are the same as clause 15.3. + +## 15.6 Presence enhancements specified in Open Mobile Alliance (OMA) Release 2.0 + +### 15.6.1 General + +In order to assure the end-to-end service interoperability through the Inter-IMS Network to Network Interface (II-NNI), the associated functions of the OMA Presence service may be supported on the II-NNI between two IMS networks. The support of each function is based on agreement between operators. + +If a function of the OMA Presence Release 2.0 is supported, the related procedures from the OMA-TS-Presence\_SIMPLE-V2\_0 [138] shall be applied with the requirements in the relevant clause below due to the crossing of the II-NNI. + +### 15.6.2 OMA subscription of presence information + +The requirements for the OMA subscription of presence information are the same as clause 15.5.2 with the following additional requirement: + +- An Allow header field containing the value "REFER" in a PUBLISH request shall be supported at the II-NNI. +- A Policy-Contact header field defined in IETF RFC 6794 [133] in a 488 (Not Acceptable Here) response to a PUBLISH request shall be supported at the II-NNI. + +NOTE: Conveyance of this header field in a 488 response to a PUBLISH request is not supported by IETF RFC 6794 [133] but is required to support Presence services according to OMA specifications OMA-TS-Presence\_SIMPLE-V2\_0 [138]. + +- A Suppress-If- Match header field in a SUBSCRIBE request shall be supported at the II-NNI. +- An Accept-Encoding header field containing the value "gzip" in a SUBSCRIBE request shall be supported at the II-NNI. +- An "application/vnd.oma.suppnot+xml" MIME body in a SUBSCRIBE request shall be supported at the II-NNI. +- A Content-Encoding header field containing the value "gzip" in a NOTIFY request shall be supported at the II-NNI. +- A Content-Type header field with the value "multipart/mixed" in a SUBSCRIBE request shall be supported at the II-NNI. +- A Refer-To header field with the value "method=PUBLISH?event=presence", a Refer-Sub header field and a SIP-If-Match header field in a REFER request shall be supported at the II-NNI. + +### 15.6.3 OMA watcher subscribing to Presence List + +The requirements for the OMA watcher subscribing to Presence List are the same as clause 15.5.3 with the following additional requirements: + +- A Suppress-If-Match header field in a SUBSCRIBE request shall be supported at the II-NNI. +- An Accept-Encoding header field containing the value "gzip" in a SUBSCRIBE request shall be supported at the II-NNI. +- An "application/vnd.oma.suppnot+xml" MIME body in a SUBSCRIBE request shall be supported at the II-NNI. +- An "application/resource-lists+xml" MIME body in a SUBSCRIBE request shall be supported at the II-NNI. +- A Content-Type header field with the value "multipart/mixed" in a SUBSCRIBE request shall be supported at the II-NNI. + +- A NOTIFY request with a Content-Encoding header field containing the value "gzip" shall be supported at the II-NNI. + +### 15.6.4 OMA subscription to Watcher Information + +The requirements for the OMA subscription to Watcher Information are the same as clause 15.5.4 with the following additional requirements: + +- Indicating support for "multipart/mixed" and "application/simple-filter+xml" in the Accept header field of the SUBSCRIBE request shall be supported at the II-NNI. +- Multiple "application/simple-filter+xml" MIME bodies in the NOTIFY request shall be supported at the II-NNI. +- A Suppress-If-Match header field in a SUBSCRIBE request shall be supported at the II-NNI. +- An Accept-Encoding header field containing the value "gzip" in the SUBSCRIBE request shall be supported at the II-NNI. +- A Content-Type header field with the value "multipart/mixed" in a NOTIFY request shall be supported at the II-NNI. +- A Content-Encoding header field with the value "gzip" in a NOTIFY request shall be supported at the II-NNI. +- A Refer-To header field with the value "method=SUBSCRIBE?Event=presence.wininfo" and a Refer-Sub header field in a REFER request sent to a Watcher Information Subscriber shall be supported at the II-NNI. + +### 15.6.5 Subscription to state changes in XML documents + +The requirements for the OMA watcher subscribing to Presence List are the same as clause 15.4 with the following additional requirements: + +- An Accept header field indicating the support for "application/xcap-diff+xml", "application/rlmi+xml" and "multipart/related" in a SUBSCRIBE request shall be supported at the II-NNI. +- An Accept-Encoding header field with the value "gzip" in a SUBSCRIBE request shall be supported at the II-NNI. +- A Content-Encoding header field containing the value "gzip" in a NOTIFY request shall be supported at the II-NNI. +- Multiple "multipart/related" MIME bodies in a NOTIFY request shall be supported at the II-NNI. +- An "application/rlmi+xml" MIME bodies in a NOTIFY request shall be supported at the II-NNI. + +### 15.6.6 Void + +### 15.6.7 Void + +# --- 16 Messaging service + +## 16.1 General + +In order to assure the end-to-end service interoperability through the Inter-IMS Network to Network Interface (II-NNI), the associated function of the messaging service may be supported on the II-NNI between two IMS networks. + +If a function is supported, the related procedures from the 3GPP TS 24.247 [139] shall be applied with the requirements in the relevant clause below due to the crossing of the II-NNI. + +## 16.2 Page-mode messaging + +Service specific requirements in accordance with clause 5 of 3GPP TS 24.247 [139] shall be supported over the II-NNI. + +A MESSAGE request containing the "application/recipient-list" MIME body specified in IETF RFC 5365 [67], a Required header field with the 'recipient-list-message' option-tag; and a body carrying payload shall be supported at the roaming II-NNI. + +A MESSAGE request containing: + +- a body that carrying payload; or +- the "application/im-iscomposing+xml" MIME body, + +shall be supported at the II-NNI. + +The response code 415 (Unsupported Media Type) and the response code 202 (Accepted) shall be supported at the II-NNI. + +## 16.4 Session-mode messaging + +Service specific requirements in accordance with clause 6 of 3GPP TS 24.247 [139] shall be supported over the II-NNI. + +No restrictions at the II-NNI identified. + +## 16.5 Session-mode messaging conferences + +Service specific requirements in accordance with clause 7 of 3GPP TS 24.247 [139] and 3GPP TS 24.147 [106] shall be supported over the II-NNI. + +The "application/resource-lists+xml" MIME body included in the INVITE request shall be supported at the roaming II-NNI. + +The media feature tag "isfocus" in the Contact header field of the INVITE request and responses to the INVITE request shall be supported at the II-NNI. + +The SUBSCRIBE request including the "conference" event package name in the Event header field and the Accept header field containing an "application/conference-info+xml" MIME type shall be supported at the II-NNI. + +The NOTIFY request including an "application/conference-info+xml" MIME body shall be supported at the II-NNI. + +The REFER request containing a Referred-By header field and NOTIFY requests procedures shall be supported at the II-NNI. + +The REFER request containing the BYE method URI parameter in the Refer-To header field shall be supported at the II-NNI. + +The Referred-By header field in the INVITE request shall be supported at the II-NNI. + +The Allow-Events header field in the INVITE request with the value "conference" shall be supported at the roaming II-NNI and may be supported at the non-roaming II-NNI. + +# --- 17 Optimal Media Routeing + +## 17.1 General + +Based on inter-operator agreement, the Optimal Media Routeing (OMR) procedures may be supported over the II-NNI. + +If OMR procedures are supported, the procedures in 3GPP TS 29.079 [148] shall be applied and the capabilities below shall be provided at the II-NNI. + +## 17.2 OMR related SDP attributes + +The "visited-realm", "secondary-realm", "omr-codecs", "omr-m-att", "omr-s-att", "omr-m-bw", "omr-s-bw", "omr-s-cksum", and "omr-m-cksum" SDP attributes defined in 3GPP TS 24.229 [5] shall be supported at the II-NNI. + +## 17.3 IP realm names + +Operators need to agree on unique names for IP realms (as defined in 3GPP TS 29.079 [148]) used in their own and interconnecting networks to avoid a collision of IP realm names. Operators may choose to share an IP realm, and shall then also assign a single unique name to that realm. As defined in 3GPP TS 24.229 [5], a public IPv4 or IPv6 address reachable from the open internet is associated with the special realm "IN". + +# --- 18 Inter-UE transfer (IUT) + +## 18.1 General + +Inter-UE transfer may be supported over the II-NNI. The IUT consist of several functional blocks, as described in the clauses below. The support of each of these functional blocks is based on agreement between operators. + +If a function is supported, the related procedures from the 3GPP TS 24.337 [149] shall be applied with the requirements in the relevant clause below. + +## 18.2 IUT without establishment of a collaborative session + +Service specific requirements in accordance with 3GPP TS 24.337 [149] shall be supported over the II-NNI. + +The REFER request shall be supported at the roaming II-NNI. + +The Refer-To header field containing a body parameter including a Replaces header field and the Require header field set to "replaces" shall be supported at the roaming II-NNI. + +The Refer-To header field containing a body parameter including a Target-Dialog header field and the Require header field set to "tdialog" shall be supported at the roaming II-NNI. + +The Refer-To header field containing a body parameter including an Accept-Contact header field with the "g.3gpp.icsi-ref" media feature tag and a P-Preferred-Service header field set to the IMS communication service identifier shall be supported at the roaming II-NNI. + +The Contact header field of the REFER request containing a public GRUU or temporary GRUU as specified in 3GPP TS 24.229 [5] shall be supported at the roaming II-NNI. + +The "g.3gpp.icsi-ref" media feature tag in the Accept-Contact header field of the REFER request shall be supported at the roaming II-NNI. + +NOTIFY requests containing a "sipfrag" MIME body as specified in IETF RFC 3515 [22], using the updated procedures from IETF RFC 6665 [20], shall be supported at the roaming II-NNI. + +## 18.3 IUT using a collaborative session + +### 18.3.1 Collaborative session of participants of the same subscription + +This clause describes the requirements at the II-NNI for an ongoing session. Service specific requirements in accordance with 3GPP TS 24.337 [149] shall be supported over the II-NNI. + +The "g.3gpp.iut-controller" media feature tag in the Accept-Contact header field in the REGISTER request shall be supported. + +A REFER request sent outside an existing dialog shall be supported at the roaming II-NNI with the following additional requirements: + +- The Refer-To header field containing a body parameter including a MIME sdp body and no method parameter, the method parameter set to "INVITE" or "BYE" shall be supported at the roaming II-NNI. +- The Accept header field containing the MIME type "message/sipfrag" in the REFER request shall be supported at the roaming II-NNI. +- The Target-Dialog header field in the REFER request shall be supported at the roaming II-NNI. + +- The Contact header field in the REFER request containing the "g.3gpp.iut-controller" media feature tag as described in annex B of 3GPP TS 24.337 [149] shall be supported at the roaming II-NNI. +- The Contact header field in the REFER request containing the "g.3gpp.current-iut-controller" media feature tag as described in annex B of 3GPP TS 24.337 [149] shall be supported at the roaming II-NNI. +- The "g.3gpp.iut-controller" media feature tag in the Accept-Contact header field shall be supported at the roaming II-NNI. +- The Referred-By header field shall be supported at the roaming II-NNI at the roaming II-NNI. + +The NOTIFY request containing a "sipfrag" MIME body as specified in IETF RFC 3515 [22], using the updated procedures from IETF RFC 6665 [20], shall be supported at the roaming II-NNI. + +Initial INVITE requests and re-INVITE requests as follows: + +- The Referred-By header field included in initial INVITE requests and re-INVITE requests shall be supported at the roaming II-NNI; +- The "g.3gpp.iut-controller" media feature tag as described in annex B of 3GPP TS 24.337 [149] in the Contact header field shall be supported at the roaming II-NNI. + +The "g.3gpp.iut-controller" media feature tag in responses to the INVITE request shall be supported at the roaming II-NNI. + +The SUBSCRIBE request including the Event header field with the "dialog" event package; and including the Accept-Contact header field with the "g.3gpp.iut-focus" media feature shall be supported at the roaming II-NNI. + +The "dialog-info+xml" MIME body in NOTIFY requests shall be supported at the roaming II-NNI. + +### 18.3.2 Establishment of a collaborative session during session setup + +Service specific requirements in accordance with 3GPP TS 24.337 [149] shall be supported over the II-NNI. + +The Accept header field containing the MIME type "application/vnd.3gpp.iut+xml" in initial INVITE requests shall be supported at the roaming II-NNI. + +A Content-Type header field containing the MIME type "application/vnd.3gpp.iut+xml" and an "application/vnd.3gpp.iut+xml" MIME body in the 300 (Multiple Choices) response shall be supported at the roaming II-NNI. + +### 18.3.3 Assignment and transfer of control of a collaborative session + +Service specific requirements in accordance with 3GPP TS 24.337 [149] shall be supported over the II-NNI. + +The "g.3gpp.current-iut-controller" media feature tag in the Contact header field of the 200 (OK) response to INVITE request shall be supported at the roaming II-NNI. + +A "multipart/mixed" MIME body containing the "application/vnd.3gpp.iut+xml" and the "application/sdp" MIME bodies in the INVITE request shall be supported at the roaming II-NNI. + +### 18.3.4 Collaborative session of participants of different subscriptions + +Service specific requirements in accordance with 3GPP TS 24.337 [149] shall be supported over the II-NNI. + +In addition to the requirements in clause 18.3.1, 18.3.2 or 18.3.3 the following applies: + +- The "g.3gpp.iut-focus" media feature tag (specified in 3GPP TS 24.337 [149] annex B) in the Contact header field shall be supported at the non-roaming II-NNI and for the loopback traversal scenario. +- The "+g.3gpp.iut-focus" header field parameter (specified in 3GPP TS 24.337 [149] annex B) in the Feature-Caps header field as described in IETF RFC 6809 [143] shall be supported at the non-roaming II-NNI and for the loopback traversal scenario. + +## 18.4 Session replication / media replication + +### 18.4.1 Pull mode + +Service specific requirements in accordance with 3GPP TS 24.337 [149] shall be supported over the II-NNI. + +The Target-Dialog header field and the Accept-Contact header field containing the "g.3gpp.iut-focus" media feature tag of the INVITE request shall be supported at the roaming II-NNI. + +A REFER request including: + +- the method parameter set to "MESSAGE" in the Refer-To header field; +- the In-Reply-To header field; +- the Target-Dialog header field; +- the Require header field populated with the option tag value "tdialog"; and +- the "application/vnd.3gpp.replication+xml" MIME body, + +shall be supported at the roaming II-NNI. + +A MESSAGE request including the In-Reply-To header field and the "application/vnd.3gpp.replication+xml" MIME body shall be supported at the roaming II-NNI. + +### 18.4.2 Push mode + +Service specific requirements in accordance with 3GPP TS 24.337 [149] shall be supported over the II-NNI. + +A REFER request including: + +- the Accept-Contact header field containing the "g.3gpp.iut-focus" media feature tag with explicit and require tags; +- the Target-Dialog header field; and +- the Refer-To header field containing the Accept-Contact header field, the P-Preferred-Service header field and the "application/sdp" MIME body, + +shall be supported at the roaming II-NNI. + +The "application/vnd.3gpp.replication+xml" MIME body of the REFER request shall be supported at the roaming II-NNI. + +# --- 19 Roaming Architecture for Voice over IMS with Local Breakout + +Based on inter-operator agreement, the roaming architecture for voice over IMS with local breakout procedure may be supported over the II-NNI. + +If the roaming architecture for voice over IMS with local breakout procedure is supported, the procedures in 3GPP TS 24.229 [5] shall be applied and the capabilities below shall be provided at the II-NNI. + +The "+g.3gpp.trf" header field parameter (defined in 3GPP TS 24.229 [5] clause 7.9A.3) with a TRF address included in a Feature-Caps header field as described in IETF RFC 6809 [143] in the INVITE request or in the UPDATE request and in the 2xx response to the UPDATE request shall be supported at the roaming II-NNI. + +The "+g.3gpp.loopback" header field parameter (defined in 3GPP TS 24.229 [5] clause 7.9A.4) with the identity of the caller's home network included in the Feature-Caps header field as described in IETF RFC 6809 [143] in the INVITE request or in the UPDATE request and in the 2xx response to the UPDATE request shall be supported for the loopback traversal scenario. + +The "loopback-indication" header field parameter (defined in 3GPP TS 24.229 [5] subclause 7.2A.5) included the P-Charging-Vector header field in 18x and 2xx responses to the INVITE request , in subsequent requests and in responses to subsequent requests shall be supported for the loopback traversal scenario and at the roaming II-NNI. + +The procedures in clause 17 shall be supported at the II-NNI. + +# --- 20 Delivery of Media Resource Broker address information + +Based on inter-operator agreement, the procedure to deliver MRB address information may be supported over the roaming II-NNI. + +NOTE: Subsequent interaction between home network MRB and visited network MRB is outside the scope of this document. + +If the procedure to enable optimised allocation of media resources is supported, the procedures in 3GPP TS 24.229 [5] shall be applied and the capabilities below shall be provided at the roaming II-NNI. + +The "g.3gpp.mrb" feature-capability indicator (defined in 3GPP TS 24.229 [5] clause 7.9A.6) with the MRB address included in the Feature-Caps header field as described in IETF RFC 6809 [143] in the INVITE request or in the UPDATE request and in the 2xx response to the UPDATE request shall be supported at the roaming II-NNI. + +# --- 21 Overload control + +## 21.1 General + +Based on inter-operator agreement, overload control may be supported over the II-NNI. + +The overload control defines two optional mechanisms: + +- a feedback based mechanism; +- and a load filter mechanism. + +The support of either one of the mechanism is based on operator agreements. + +If a mechanism is supported, the related procedures from the 3GPP TS 24.229 [5] shall be applied with the requirements in the relevant clause below. + +Based on regional/national requirements and inter-operator agreement, Multimedia Priority Service (MPS), as specified in 3GPP TS 22.153 [187], shall be exempted from SIP overload controls across II-NNI up to the point where further exemption would cause network instability. + +## 21.2 Feedback based mechanism + +The procedures in 3GPP TS 24.229 [5] shall be applied and the capabilities below shall be provided at the II-NNI. + +The feedback based mechanism, defined in IETF RFC 7339 [165], requires no additional support at the II-NNI as it is supported using header field parameters within existing header fields supported at the II-NNI. + +NOTE: An algorithm will need to be selected. The IETF RFC 7339 [165] also defines the default algorithm for usage of the feedback based mechanism in the IM CN subsystem. Additional algorithms are either already defined, e.g. the rate-based scheme defined in IETF RFC 7415 [166], or can also be defined in the future. + +## 21.3 The load filter mechanism + +The procedures in 3GPP TS 24.229 [5] shall be applied and the capabilities below shall be provided at the II-NNI. + +A SUBSCRIBE request containing the Event header field "load-control" and, optionally, an Accept header field containing the "application/load-control+xml" MIME type as defined in IETF RFC 7200 [167] shall be supported on the II-NNI. + +NOTE: The addresses to targets that can be supervised need to form part of the service level agreement. + +A NOTIFY request containing the "application/load-control+xml" MIME body defined in IETF RFC 7200 [167] shall be supported on the II-NNI. + +# --- 22 Delivery of original destination identity + +Based on inter-operator agreement, the procedure to deliver original identity may be supported over the II-NNI. + +NOTE: Service requirement related to the procedure is available in 3GPP TS 22.228 [9]. + +If the procedure to enable delivery of original destination identity is supported, the procedures in 3GPP TS 24.229 [5] shall be supported as further specified below. + +The "mp" header field parameter in the History-Info header field of the initial INVITE request, as defined in IETF RFC 7044 [25], shall be supported over the II-NNI. + +# --- 23 Telepresence using IMS + +Based on inter-operator agreement, the procedure to support telepresence using IMS may be supported over the II-NNI. + +NOTE: Service requirement related to the procedure is available in clause 7.10.2.2 of 3GPP TS 22.228 [9]. + +If the telepresence using IMS is supported, the procedures in 3GPP TS 24.103 [189] shall be applied and the capabilities below shall be provided at the II-NNI. + +The "+sip.clue" header field parameter included in a Contact header field as described in 3GPP TS 24.103 [189] in the INVITE request or in the UPDATE request and in the 2xx response to the UPDATE request shall be supported at the II-NNI. + +# --- 24 Barring of premium rate numbers + +Based on inter-operator agreement, barring of premium rate numbers as described in 3GPP TS 24.315 [191] may be supported over the II-NNI. + +If barring of premium rate numbers is supported, the "premium-rate" tel URI parameter defined in 3GPP TS 24.229 [5] clause 7.2A.17 shall be supported at the roaming II-NNI. + +# --- 25 P-CSCF restoration + +## 25.1 General + +Based on inter-operator agreement, P-CSCF restoration may be supported over the II-NNI. + +The P-CSCF restoration defines two optional mechanisms: + +- a PCRF or PCF based mechanism; and + +NOTE 1: In 5GS the mechanism is called "PCF based P-CSCF restoration" since the PCF takes the role of the PCRF. + +- an HSS or UDM/HSS based mechanism. + +NOTE 2: In 5GS the mechanism is called "UDM/HSS based P-CSCF restoration" since the UDM participates in the procedure. + +The support of either one of the mechanisms is based on operator agreements. + +If a mechanism is supported, the related procedures from the 3GPP TS 24.229 [5] shall be applied with the requirements in the relevant clause below. + +## 25.2 PCRF or PCF based P-CSCF restoration + +The procedures in 3GPP TS 24.229 [5] shall be applied and the capabilities below shall be provided at the II-NNI. + +The Restoration-Info header field containing IMSI information defined in 3GPP TS 24.229 [5] in the home-to-visited initial INVITE request shall be supported on the roaming II-NNI. + +## 25.3 HSS or UDM/HSS based P-CSCF restoration + +The procedures in 3GPP TS 24.229 [5] shall be applied and the capabilities below shall be provided at the II-NNI. + +The Restoration-Info header field containing information about failed node defined in 3GPP TS 24.229 [5] in the 408 (Request Timeout) response to the home-to-visited initial INVITE request and in the 504 (Server Time-out) response to the MESSAGE request, NOTIFY request, OPTIONS request, PUBLISH request, REFER request and the SUBSCRIBE request shall be supported on the roaming II-NNI. + +# --- 26 Resource sharing + +Based on inter-operator agreement, resource sharing may be supported over the II-NNI. + +If resource sharing is supported, the related procedures from the 3GPP TS 24.229 [5] shall be applied with the requirements in this clause. + +The Resource-Share header field shall be supported on the roaming II-NNI in the following SIP requests and SIP responses: + +- the ACK request, the INVITE request, the PRACK request, the REGISTER and UPDATE; +- 18x responses to the INVITE request; and +- 2xx responses to the PRACK request, INVITE request and the UPDATE request. + +# --- 27 Service access number translation + +Based on inter-operator agreement, service access number translation may be supported over the II-NNI. + +If service access number translation is supported, the related procedures in 3GPP TS 24.229 [5] shall be applied with the requirements in this clause. + +The Request-URI containing a "cause" SIP URI parameter, defined in IETF RFC 4458 [58], set to the value "380" defined in IETF RFC 8119 [193] shall be supported at the II-NNI. + +The History-Info header field containing a "cause" SIP URI parameter, defined in IETF RFC 4458 [58], set to the value "380" defined in IETF RFC 8119 [193] shall be supported at the II-NNI. + +# --- 28 Mission critical services + +## 28.1 General + +In order to assure the end-to-end service interoperability through the II-NNI, the associated services of the Mission Critical communication may be supported on the II-NNI. The support of mission critical services is based on the business relationships defined in 3GPP TS 23.280 [200] clause 6. + +II-NNI requirements for SIP signalling related to mission critical services interface SIP-1 and SIP-3 (see figure 7.3.1-2 in 3GPP TS 23.280 [200]) are addressed in the present specification as follows: + +- Apart from differences specified in the present clause 28, the SIP-1 interface is identical to the roaming II-NNI. +- Apart from differences specified in the present clause 28, the SIP-3 interface is identical to the non-roaming II-NNI. + +SIP signalling traversing the NNI between an mission critical services server and a SIP core (interface SIP-2 in figure 7.3.1-2 in 3GPP TS 23.280 [200]) is not considered in the present release of this specification. + +The mission critical services are identified by means of the following IMS Communication Service Identifiers: + +- 1) for MCPTT, the "urn:urn-7:3gpp-service.ims.icsi.mcptt" URN (defined in annex E of 3GPP TS 24.379 [201]) ; +- 2) for mission critical video communications, the "urn:urn-7:3gpp-service.ims.icsi.mcvideo" URN (defined in annex E of 3GPP TS 24.281 [210]); and +- 3) for mission critical data communications, the "urn:urn-7:3gpp-service.ims.icsi.mcdata" URN (defined in annex C of 3GPP TS 24.282 [211]) and additionally: + - for Short Data Service (SDS), the "urn:urn-7:3gpp-service.ims.icsi.mcdata.sds" URN (defined in annex C of 3GPP TS 24.282 [211]); and + - for File Distribution (FD), the "urn:urn-7:3gpp-service.ims.icsi.mcdata.fd" URN (defined in annex C of 3GPP TS 24.282 [211]). + +The IMS Communication Service Identifiers listed above can appear in: + +- the media feature tag "g.3gpp.icsi-ref" (specified in 3GPP TS 24.229 [5] subclause 7.9.2) in the Contact header field and the Accept-Contact header field; +- the P-Asserted-Service header field; and +- the P-Preferred-Service header field. + +If the mission critical services are supported, the related procedures from 3GPP TS 24.379 [201], 3GPP TS 24.380 [202], 3GPP TS 24.281 [210], 3GPP TS 24.581 [212], 3GPP TS 24.282 [211] and 3GPP TS 24.582 [213] shall be applied with the requirements in the clauses below due to the crossing of the II-NNI. + +## 28.2 Interoperability of mission critical services for communication over II-NNI + +### 28.2.1 Mission Critical services session establishment + +Service specific requirements in accordance with 3GPP TS 22.179 [199], 3GPP TS 22.280 [209], 3GPP TS 24.379 [201], 3GPP TS 24.281 [210] and 3GPP TS 24.282 [211] shall be supported over the II-NNI. + +The INVITE request including: + +A) For MCPTT: + +- 1) the "g.3gpp.mcptt" media feature tag (defined in annex C of 3GPP TS 24.379 [201]) in the Contact header field; +- 2) the media feature tag "isfocus" (defined in IETF RFC 3840 [56]) in the Contact header field; +- 3) the Content-Type header field with the value "multipart/mixed"; and +- 4) the "application/vnd.3gpp.mcptt-info+xml" MIME body; + +B) For MCVideio: + +- 1) the "g.3gpp.mcvideo" media feature tag (defined in annex D of 3GPP TS 24.281 [210]) in the Contact header field; +- 2) the media feature tag "isfocus" (defined in IETF RFC 3840 [56]) in the Contact header field; +- 3) the Content-Type header field with the value "multipart/mixed"; and + +4) the "application/vnd.3gpp.mcvideo-info+xml" MIME body; + +C) For MCData: + +1) the: + +a) "g.3gpp.mcdata.sds" media feature tag; or + +b) "g.3gpp.mcdata.fd" media feature tag, + +(defined in annex B of 3GPP TS 24.282 [211]) in the Contact header field; + +2) the media feature tag "isfocus" (defined in IETF RFC 3840 [56]) in the Contact header field; + +3) the Content-Type header field with the value "multipart/mixed"; + +4) the "application/vnd.3gpp.mcdata-info+xml" MIME body; and + +5) the "application/vnd.3gpp.mcdata-signalling" MIME body; + +shall be supported at the II-NNI. + +Responses to the INVITE request including: + +1) the: + +a) "g.3gpp.mcptt"; + +b) "g.3gpp.mcvideo"; + +c) "g.3gpp.mcdata.sds"; or + +d) "g.3gpp.mcdata.fd" + +media feature tag in the Contact header field; + +2) the media feature tag "isfocus" in the Contact header field; + +3) the Content-Type header field with the value "multipart/mixed"; + +4) the "application/vnd.3gpp.mcptt-info+xml" for MCPTT or "application/vnd.3gpp.mcvideo-info+xml" for MCVide or "application/vnd.3gpp.mcdata-info+xml" for MCData MIME body; and + +5) the Warning header field with the warn-code set to "399" and with the warn-text set to a quoted-string as specified in 3GPP TS 24.379 [201] clause 4.4.2 and 3GPP TS 24.281 [210] clause 4.4.2 and 3GPP TS 24.282 [211] clause 4.9; + +shall be supported at the II-NNI. + +The initial INVITE request including the Priority-Share header field (defined in 3GPP TS 24.229 [5]), the Resource-Share header field (defined in 3GPP TS 24.229 [5]) and the "application/resource-lists+xml" MIME body shall be supported at the roaming II-NNI. + +The Resource-Share header field and the Priority-Share header field in 18x and 2xx responses to the INVITE request shall be supported at the roaming II-NNI. + +The Resource-Share header field and the Priority-Share header field in the PRACK requests, the UPDATE requests, the ACK requests and in 2xx responses to the PRACK requests and the UPDATE requests shall be supported at the roaming II-NNI. + +The REFER request containing an "application/vnd.3gpp.mcptt-info+xml" MIME body in the headers portion in the Refer-To header field shall be supported at the roaming II-NNI. + +NOTE: How the "application/vnd.3gpp.mcptt-info+xml" MIME body is included in the headers portion is described in IETF RFC 3261 [13] section 19.1.1. + +The "m=" line set to "application
(table 6.2, item 25)
and clause 12.26.2 | o in case of a trust relationship between the interconnected networks, else n/a | +| 5 | Alert-Info | [5] | o | +| 6 | Allow | [5] | m | +| 7 | Allow-Events | [5] | m on roaming II-NNI, else o | +| 7a | Attestation-Info | [5], clause 6.1.1.3.1
(table 6.2, item 23)
and clause 29 | o on non-roaming II-NNI, else n/a | +| 8 | Authentication-Info | [5] | m on roaming II-NNI, else n/a | +| 9 | Authorization | [5] | m on roaming II-NNI, else n/a | +| 9a | Answer-Mode | [5] | o | +| 10 | Call-ID | [5] | m | +| 11 | Call-Info | [5] | m | +| 11a | Cellular-Network-Info | clause 6.1.1.3.1
(table 6.2, item 21) | o | +| 12 | Contact | [5] | m | +| 13 | Content-Disposition | [5] | m | +| 14 | Content-Encoding | [5] | m | +| 14a | Content-ID | [5] | o | +| 15 | Content-Language | [5] | m | +| 16 | Content-Length | [5] | m | +| 17 | Content-Type | [5] | m | +| 18 | CSeq | [5] | m | +| 19 | Date | [5] | m | +| 20 | Error-Info | [5] | o | +| 21 | Expires | [5] | m | +| 21a | Flow-Timer | [5] | m on roaming II-NNI, else o | +| 21b | Feature-Caps | clause 6.1.1.3.1
(table 6.2, item 13) | o | +| 22 | Event | [5] | m | +| 23 | From | [5] | m | +| 24 | Geolocation | [5] | m | +| 24a | Geolocation-Error | [5] | m | +| 24b | Geolocation-Routing | [5] | m | +| 25 | History-Info | clause 6.1.1.3.1
(table 6.2, item 4) | o | +| 25b | Identity | [206] and clause 29 | o on non-roaming II-NNI, else n/a | +| 25a | Info-Package | [5] | o | +| 26 | In-Reply-To | [5] | o | +| 27 | Join | [5] | o | +| 27a | Max-Breadth | [5] | m | +| 28 | Max-Forwards | [5] | m | +| 29 | Min-Expires | [5] | m | +| 30 | MIME-Version | [5] | m | +| 31 | Min-SE | [5] | m | +| 32 | Organization | [5] | m | +| 32a | Origination-Id | [5], clause 6.1.1.3.1
(table 6.2, item 24)
and clause 29 | o on non-roaming II-NNI, else n/a | +| 33 | P-Access-Network-Info | clause 6.1.1.3.1
(table 6.2, item 2) | m in case of a trust relationship between the interconnected networks, else n/a | +| 33a | P-Answer-state | [5] | o | +| 34 | P-Asserted-Identity | clause 6.1.1.3.1
(table 6.2, item 1) | m in case of a trust relationship between the interconnected networks, else n/a | +| 35 | P-Asserted-Service | clause 6.1.1.3.1
(table 6.2, item 5) | o | +| 35a | P-Associated-URI | [5] | m on roaming II-NNI, else n/a | +| 36 | P-Called-Party-ID | [5] | m on roaming II-NNI, else n/a | + +| Item | Header field | Ref. | II-NNI | +|------|-------------------------------|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------| +| 37 | P-Charging-Function-Addresses | clause 6.1.1.3.1
(table 6.2, item 7) | n/a | +| 38 | P-Charging-Vector | clause 6.1.1.3.1
(table 6.2, item 6) | m on roaming II-NNI, else o | +| 39 | P-Early-Media | clause 6.1.1.3.1
(table 6.2, item 12) | m in case of a trust relationship between the interconnected networks, else n/a | +| 40 | P-Media-Authorization | [5] | n/a | +| 41 | P-Preferred-Identity | [5] | n/a | +| 42 | P-Preferred-Service | [5] | m on roaming II-NNI, else n/a | +| 43 | P-Private-Network-Indication | clause 6.1.1.3.1
(table 6.2, item 9) | m on roaming II-NNI, else o | +| 44 | P-Profile-Key | clause 6.1.1.3.1
(table 6.2, item 8) | o on roaming II-NNI, else n/a | +| 44a | P-Refused-URI-List | [5] | o on non-roaming II-NNI, else n/a | +| 45 | P-Served-User | clause 6.1.1.3.1
(table 6.2, item 10) | m on roaming II-NNI, else n/a | +| 46 | P-User-Database | [5] | n/a | +| 47 | P-Visited-Network-ID | [5] | m on roaming II-NNI, else n/a | +| 47a | Path | [5] | m on roaming II-NNI, else n/a | +| 47b | Permission-Missing | [5] | o | +| 47c | Policy-Contact | [133] and
clause 15.6.2 | o | +| 48 | Priority | clause 6.1.1.3.1
(table 6.2, item 14) | o | +| 48b | Priority-Share | [5] clause 7.2.16 | o on roaming II-NNI, else n/a | +| 48a | Priv-Answer-Mode | [5] | o | +| 49 | Privacy | [5] | m | +| 50 | Proxy-Authenticate | [5] | m on roaming II-NNI, else n/a | +| 51 | Proxy-Authorization | [5] | m on roaming II-NNI, else n/a | +| 52 | Proxy-Require | [5] | m | +| 52a | RAck | [5] | m | +| 53 | Reason | [5] and
clause 6.1.1.3.1
(table 6.2, item 11) | o when in a request.
When in a response, m in case of a trust relationship between the interconnected networks, else n/a | +| 54 | Record-Route | [5] | m | +| 54a | Recv-Info | [5] | o | +| 55 | Referred-By | [5] | m | +| 55a | Refer-Sub | [5] | m in the case the REFER request is supported, else n/a | +| 55b | Refer-To | [5] | m in the case the REFER request is supported, else n/a | +| 56 | Reject-Contact | [5] | m | +| 56a | Relayed-Charge | clause 6.1.1.3.1
(table 6.2, item 19) | n/a | +| 57 | Replaces | [5] | o | +| 58 | Reply-To | [5] | o | +| 59 | Request-Disposition | [5] | m | +| 60 | Require | [5] | m | +| 61 | Resource-Priority | clause 6.1.1.3.1
(table 6.2, item 3) | o | +| 61c | Resource-Share | [5] clause 7.2.13 | o on roaming II-NNI, else n/a | +| 61d | Response-Source | [5] | o in case of a trust relationship between the interconnected networks, else n/a | +| 61b | Restoration-Info | clause 6.1.1.3.1
(table 6.2, item 18) | o on roaming II-NNI, else n/a | +| 61a | Retry-After | [5] | o | +| 62 | Route | [5] | m | +| 62a | RSeq | [5] | m | +| 63 | Security-Client | [5] | n/a | +| 63a | Security-Server | [5] | n/a | +| 64 | Security-Verify | [5] | n/a | +| 65 | Server | [5] | o | +| 65c | Service-Interact-Info | [5] and | o in case of a trust relationship between the | + +| Item | Header field | Ref. | II-NNI | +|------|--------------------|------------------------------------------|----------------------------------------------------------| +| | | clause 6.1.1.3.1
(table 6.2, item 20) | interconnected networks, else n/a | +| 65a | Service-Route | [5] | m on roaming II-NNI, else n/a | +| 65b | Session-ID | [5] | o | +| 66 | Session-Expires | [5] | m | +| 66a | SIP-ETag | [5] | m in the case the PUBLISH request is supported, else n/a | +| 66b | SIP-If-Match | [5] | m in the case the PUBLISH request is supported, else n/a | +| 67 | Subject | [5] | o | +| 67a | Subscription-State | [5] | m in the case the NOTIFY request is supported, else n/a | +| 67b | Suppress-If-Match | [144] and
clause 15.6.4 | o | +| 68 | Supported | [5] | m | +| 68a | Target-Dialog | [5] | o | +| 69 | Timestamp | [5] | m | +| 70 | To | [5] | m | +| 71 | Trigger-Consent | [5] | m | +| 71a | Unsupported | [5] | m | +| 72 | User-Agent | [5] | m | +| 73 | User-to-User | [5] | o | +| 74 | Via | [5] | m | +| 75 | Warning | [5] | o | +| 76 | WWW-Authenticate | [5] | m on roaming II-NNI, else n/a | + +**Table A.2: Key to notation codes for SIP header fields** + +| Notation code | Meaning | +|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| m | The SIP header field is applicable at II-NNI. Supporting a SIP header field at the II-NNI means that this header field is passed through the IBCF. It does not imply that network elements inside the serving and served networks or user equipment connected to these networks shall support this header field, where 3GPP TS 24.229 [5] is applied. If specified in 3GPP TS 24.229 [5], the IBCF modifies the SIP header field. | +| o | The applicability of SIP header field at II-NNI depends on bilateral agreement between the operators. | +| n/a | It is impossible to use the SIP header field at the II-NNI. This header field could be discarded by the IBCF. | + +# Annex B (informative): Dynamic view of SIP header fields within SIP messages + +## B.1 Scope + +This annex provides the applicability of SIP header fields in SIP messages over II-NNI by using the methodology of a so-called "dynamic view", as used in IETF RFC 3261 [13] and other SIP related RFCs. This methodology documents the presence of SIP header fields in SIP messages over the II-NNI and also takes into account dynamic conditions, for instance the presence of a SIP header field in a SIP request message as condition for the SIP header field in the corresponding SIP response message. + +Specific information about the applicability of SIP header fields in SIP messages in a dynamic view is also provided for cases where an MMTEL supplementary service is supported over the II-NNI between operators. + +The applicability of SIP header fields described in this annex is based on the procedures described in 3GPP TS 24.229 [5] and the list of SIP header fields in annex A of 3GPP TS 24.229 [5]. + +## B.2 Methodology + +The meaning of the notation codes used in the tables in subsequent clauses is as follows: + +In the "RFC status" column, the notation codes defined in IETF RFC 3261 [13] clause 20 are applied. + +In the "II-NNI condition" column the notation codes defined in table B.2.1 are used. If a capability of a SIP header field is specified as either optional or conditional in table 6.1.3.1, then "II-NNI condition" of the SIP header field is described with conditional expression. + +In each request-related table, the order of SIP header fields inherits that of clause A.2.2 of 3GPP TS 24.229 [5]. + +In each response-related table, the SIP status code for which the header field is applicable is described in the "SIP status code" column. The notation codes for the "where" column as defined in IETF RFC 3261 [13] clause 20 are applied. The notation code "r" in "SIP status code" column corresponds to any SIP status code which is described in annex A of 3GPP TS 24.229 [5] for the corresponding method. Any SIP header field not listed in a table is not applicable for the corresponding SIP message. + +**Table B.2.1: Key to notation codes for SIP header fields in dynamic view for II-NNI** + +| Notation code
(NOTE 1) | Meaning | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| dc | The SIP header field is required to be present in a SIP message over II-NNI according to the procedures specified in other specifications e.g. 3GPP TS 24.229 [5]. | +| dm | The SIP header field shall be always present in a SIP message over II-NNI, and if received, it must be handled according to 3GPP TS 24.229 [5]. | +| dm* | The SIP header field should be present in a SIP message over II-NNI, but the IMS network need to be prepared to receive a SIP message without that header field. | +| do | The SIP header field can be present in a SIP message over II-NNI, and if received, it must be handled according to 3GPP TS 24.229 [5]. (NOTE 2) | +| dt | The header field should be present in a SIP message over II-NNI, but the IMS network need to be prepared to receive a SIP message without that header field.
If TCP is used as a transport, then the header field must be present in a SIP message. | +| d* | The SIP header field is required to be present in a SIP message if the message body is not empty. | +| dn/a | The SIP header field is shall not be present in a SIP message over II-NNI. (NOTE 3) | +| dc
417 | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE 2) | +| 5 | Allow | 405 | [13] | m | dm | +| | | others | | o | do | +| 6 | Allow-Events | 2xx | [20] | o | IF table 6.1.3.1/23 THEN do (NOTE 2) | +| 7 | Authentication-Info | 2xx | [13] | o | IF table 6.1.3.1/7 THEN do (NOTE 2) | +| 8 | Call-ID | 100 | [13] | m | dm | +| | | others | | | | +| 9 | Cellular-Network-Info | r | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE 2) | +| 10 | Contact | 3xx
485 | [13] | o | do | +| 11 | Content-Disposition | r | [13] | o | IF dc1 (AOC: clause 12.22) THEN dm ELSE do | +| 12 | Content-Encoding | r | [13] | o | do | +| 13 | Content-ID | r | [216] | o | IF table 6.1.3.1/122 THEN do | +| 14 | Content-Language | r | [13] | o | do | +| 15 | Content-Length | 100 | [13] | t | dt | +| | | others | | | | +| 16 | Content-Type | r | [13] | * | d* | +| 17 | CSeq | 100 | [13] | m | dm | +| | | others | | | | +| 18 | Date | 100 | [13] | o | do | +| | | others | | | | +| 19 | Error-Info | 3xx-6xx | [13] | o | IF table 6.1.3.1/13 THEN do (NOTE 2) | +| 20 | From | 100 | [13] | m | dm | +| | | others | | | | +| 21 | Geolocation-Error | 424 | [68] | m | dm | +| | | others | | o | do | +| 22 | MIME-version | r | [13] | o | do | +| 23 | P-Access-Network-Info | r | [24], [2 4A], [2 4B] | o | IF table 6.1.3.1/36 THEN do (NOTE 2) | +| 24 | P-Asserted-Identity | r | [44] | o | IF table 6.1.3.1/27 THEN do (NOTE 2) | +| 25 | P-Charging-Function-Addresses | r | [24], [2 4A] | o | dn/a | +| 26 | P-Charging-Vector | 100 | [24], [2 4A] | o | dn/a | +| | | others | | o | IF table 6.1.3.1/38 THEN do (NOTE 2) | +| 27 | P-Preferred-Identity | r | [44] | o | dn/a | +| 28 | Privacy | r | [34] | o | do | +| 29 | Proxy-Authenticate | 401 (NOTE 1) | [13] | o | do | +| | | 407 (NOTE 1) | | m | dm | +| 30 | Record-Route | 2xx | [13] | o | do | +| 31 | Relayed-Charge | r | [5] | n/a | dn/a | +| 32 | Require | r | [13] | c | dc | +| 33 | Response-Source | 3xx-6xx | [5] | n/a | IF table 6.1.3.1/121 THEN do (NOTE 2) | +| 34 | Retry-After | 404
413
480
486
500
503 | [13] | o | do | + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | | +|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------|------------|-----------------------------------------|--| +| | | 600
603 | | | | | +| 35 | Security-Server | 421
494 | [47] | o | dn/a | | +| 36 | Server | r | [13] | o | do | | +| 37 | Session-ID | r | [124] | m | IF table 6.1.3.1/94 THEN dm
(NOTE 2) | | +| 38 | Supported | 2xx | [13] | o | do | | +| 39 | Timestamp | r | [13] | o | do | | +| 40 | To | 100
others | [13] | m | dm | | +| 41 | Unsupported | 420 | [13] | m | dm | | +| 42 | User-Agent | r | [13] | o | do | | +| 43 | User-to-User | r | [83] | o | IF table 6.1.3.1/79 THEN do
(NOTE 2) | | +| 44 | Via | 100
others | [13] | m | dm | | +| 45 | Warning | r | [13] | o | do | | +| 46 | WWW-Authenticate | 401
(NOTE 1) | [13] | m | dm | | +| | | 407
(NOTE 1) | | o | do | | +| dc1: | 200 (OK) response invoked due to AOC AND home-to-visited response on roaming II-NNI | | | | | | +| NOTE 1: | The SIP status code is only applicable over the roaming II-NNI. | | | | | | +| NOTE 2: | If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. | | | | | | + +## B.5 CANCEL method + +The table B.5.1 lists the supported header fields within the CANCEL request. + +**Table B.5.1: Supported header fields within the CANCEL request** + +| Item | Header field | Ref. | RFC status | II-NNI condition | +|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|------------|--------------------------------------------------------------------------| +| 1 | Accept-Contact | [51] | o | do | +| 2 | Authorization | [13] | o | IF table 6.1.3.1/7 THEN do (NOTE) | +| 3 | Call-ID | [13] | m | dm | +| 4 | Content-Length | [13] | t | dt | +| 5 | Content-Type | [13] | * | IF table 6.1.3.1/20 THEN do (NOTE) | +| 6 | CSeq | [13] | m | dm | +| 7 | Date | [13] | o | do | +| 8 | From | [13] | m | dm | +| 9 | Max-Breadth | [79] | o | do | +| 10 | Max-Forwards | [13] | m | dm | +| 11 | Privacy | [34] | o | do | +| 12 | Reason | [48] | o | IF dc1 (CW: clause 12.7) THEN dm ELSE IF table 6.1.3.1/40 THEN do (NOTE) | +| 13 | Record-Route | [13] | o | do | +| 14 | Reject-Contact | [51] | o | do | +| 15 | Request-Disposition | [51] | o | do | +| 16 | Resource-Priority | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE) | +| 17 | Route | [13] | c | dc | +| 18 | Session-ID | [124] | m | IF table 6.1.3.1/94 THEN dm (NOTE) | +| 19 | Supported | [13] | o | do | +| 20 | Timestamp | [13] | o | do | +| 21 | To | [13] | m | dm | +| 22 | User-Agent | [13] | o | do | +| 23 | Via | [13] | m | dm | +| dc1: | request invoked due to CW at the expiry of the "CW timer" | | | | +| NOTE: | If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. | | | | + +The table B.5.2 lists the supported header fields within the CANCEL response. + +**Table B.5.2: Supported header fields within the CANCEL response** + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|------|--------------------------|------------------------------------------------------|-------|------------|-------------------------------------| +| 1 | Accept-Resource-Priority | 2xx
417 | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE) | +| 2 | Call-ID | r | [13] | m | dm | +| 3 | Content-Length | r | [13] | t | dt | +| 4 | CSeq | r | [13] | m | dm | +| 5 | Date | r | [13] | o | do | +| 6 | Error-Info | 3xx-6xx | [13] | o | IF table 6.1.3.1/13 THEN do (NOTE) | +| 7 | From | r | [13] | m | dm | +| 8 | Privacy | r | [34] | o | do | +| 9 | Record-Route | 2xx | [13] | o | do | +| 10 | Response-Source | 3xx-6xx | [5] | n/a | IF table 6.1.3.1/121 THEN do (NOTE) | +| 11 | Retry-After | 404
413
480
486
500
503
600
603 | [13] | o | do | +| 12 | Session-ID | r | [124] | m | IF table 6.1.3.1/94 THEN dm (NOTE) | +| 13 | Supported | 2xx | [13] | o | do | +| 14 | Timestamp | r | [13] | o | do | +| 15 | To | r | [13] | m | dm | +| 16 | User-Agent | r | [13] | o | do | +| 17 | Via | r | [13] | m | dm | +| 18 | Warning | r | [13] | o | do | + +NOTE: If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. + +## B.6 INFO method + +As described in table 6.1, the support of INFO method over the II-NNI is based on bilateral agreement between the operators. + +The table B.6.1 lists the supported header fields within the INFO request. + +**Table B.6.1: Supported header fields within the INFO request** + +| Item | Header field | Ref. | RFC status | II-NNI condition | +|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|------------|--------------------------------------------| +| 1 | Accept | [13], [39] | o | do | +| 2 | Accept-Encoding | [13], [39] | o | do | +| 3 | Accept-Language | [13], [39] | o | do | +| 4 | Allow | [13], [39] | o | do | +| 5 | Allow-Events | [20] | o | IF table 6.1.3.1/23 THEN do (NOTE) | +| 6 | Authorization | [13], [39] | o | IF table 6.1.3.1/7 THEN do (NOTE) | +| 7 | Call-ID | [13], [39] | m | dm | +| 8 | Call-Info | [13], [39] | o | do | +| 9 | Cellular-Network-Info | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE) | +| 10 | Content-Disposition | [13], [39] | o | IF dc1 (AOC: clause 12.22) THEN dm ELSE do | +| 11 | Content-Encoding | [13], [39] | o | do | +| 12 | Content-ID | [216] | o | IF table 6.1.3.1/122 THEN do | +| 13 | Content-Language | [13], [39] | o | do | +| 14 | Content-Length | [13], [39] | o | do | +| 15 | Content-Type | [13], [39] | * | d* | +| 16 | CSeq | [13], [39] | m | dm | +| 17 | Date | [13], [39] | o | do | +| 18 | From | [13], [39] | m | dm | +| 19 | Geolocation | [68] | o | do | +| 20 | Geolocation-Routing | [68] | o | do | +| 21 | Info-Package | [39] | m* | IF table 6.1.3.1/17 THEN do (NOTE) | +| 22 | Max-Breadth | [79], [39] | n/a | dn/a | +| 23 | Max-Forwards | [13], [39] | o | do | +| 24 | MIME-Version | [13], [39] | o | do | +| 25 | P-Access-Network-Info | [24], [24B] | o | IF table 6.1.3.1/36 THEN do (NOTE) | +| 26 | P-Charging-Function-Addresses | [24] | o | dn/a | +| 27 | P-Charging-Vector | [24] | o | IF table 6.1.3.1/38 THEN do (NOTE) | +| 28 | Privacy | [34], [39] | o | do | +| 29 | Proxy-Authorization | [13], [39] | o | IF table 6.1.3.1/7 THEN do (NOTE) | +| 30 | Proxy-Require | [13], [39] | o | do | +| 31 | Reason | [48], [39] | o | IF table 6.1.3.1/40 THEN do (NOTE) | +| 32 | Record-Route | [13], [39] | o | do | +| 33 | Referred-By | [53], [39] | o | do | +| 34 | Relayed-Charge | [5] | n/a | dn/a | +| 35 | Request-Disposition | [51], [39] | o | do | +| 36 | Require | [13], [39] | o | do | +| 37 | Resource-Priority | [78], [39] | o | IF table 6.1.3.1/73 THEN do (NOTE) | +| 38 | Route | [13], [39] | o | do | +| 39 | Security-Client | [47], [39] | o | dn/a | +| 40 | Security-Verify | [47], [39] | o | dn/a | +| 41 | Session-ID | [124] | m | IF table 6.1.3.1/94 THEN dm (NOTE) | +| 42 | Subject | [13], [39] | o | do | +| 43 | Supported | [13], [39] | o | do | +| 44 | Timestamp | [13], [39] | o | do | +| 45 | To | [13], [39] | m | dm | +| 46 | User-Agent | [13], [39] | o | do | +| 47 | Via | [13], [39] | m | dm | +| dc1: | request invoked due to AOC AND home-to-visited request on roaming II-NNI | | | | +| NOTE: | If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. | | | | + +The table B.6.2 lists the supported header fields within the INFO response. + +###### **Table B.6.2: Supported header fields within the INFO response** + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|------|-------------------------------|---------------------------------|--------------------|------------|---------------------------------------| +| 1 | Accept | 2xx
415 | [13], [39] | o | do | +| 2 | Accept-Encoding | 2xx | [13], [39] | o | do | +| | | 415 | | c | dc | +| 3 | Accept-Language | 2xx
415 | [13], [39] | o | do | +| 4 | Accept-Resource-Priority | 2xx
417 | [78], [39] | o | IF table 6.1.3.1/73 THEN do (NOTE 2) | +| 5 | Allow | 405 | [13], [39] | m | dm | +| | | others | | o | do | +| 6 | Allow-Events | 2xx | [20] | o | IF table 6.1.3.1/23 THEN do (NOTE 2) | +| 7 | Authentication-Info | 2xx | [13], [39] | o | IF table 6.1.3.1/7 THEN do (NOTE 2) | +| 8 | Call-ID | 100 | [13], [39] | m | dm | +| | | others | | | | +| 9 | Call-Info | r | [13], [39] | o | do | +| 10 | Cellular-Network-Info | r | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE 2) | +| 11 | Content-Disposition | r | [13], [39] | o | do | +| 12 | Content-Encoding | r | [13], [39] | o | do | +| 13 | Content-ID | r | [216] | o | IF table 6.1.3.1/122 THEN do | +| 14 | Content-Language | r | [13], [39] | o | do | +| 15 | Content-Length | 100 | [13], [39] | o | do | +| | | others | | | | +| 16 | Content-Type | r | [13], [39] | * | d* | +| 17 | CSeq | 100 | [13], [39] | m | dm | +| | | others | | | | +| 18 | Date | 100 | [13], [39] | o | do | +| | | others | | | | +| 19 | Error-Info | 3xx-6xx | [13], [39] | o | IF table 6.1.3.1/13 THEN do (NOTE 2) | +| 20 | From | 100 | [13], [39] | m | dm | +| | | others | | | | +| 21 | Geolocation-Error | 424 | [68], [39] | m | dm | +| | | others | | o | do | +| 22 | MIME-version | r | [13], [39] | o | do | +| 23 | Organization | r | [13], [39] | n/a | dn/a | +| 24 | P-Access-Network-Info | r | [24], [24A], [24B] | o | IF table 6.1.3.1/36 THEN do (NOTE 2) | +| 25 | P-Charging-Function-Addresses | r | [24], [24A] | o | dn/a | +| 26 | P-Charging-Vector | 100 | [24], [24A] | o | dn/a | +| | | others | | o | IF table 6.1.3.1/38 THEN do (NOTE 2) | +| 27 | Privacy | r | [34], [39] | o | do | +| 28 | Proxy-Authenticate | 401
(NOTE 1) | [13], [39] | o | do | +| 29 | Record-Route | 2xx | [13], [39] | o | do | +| 30 | Relayed-Charge | r | [5] | n/a | dn/a | +| 31 | Require | r | [13], [39] | o | do | +| 32 | Response-Source | 3xx-6xx | [5] | n/a | IF table 6.1.3.1/121 THEN do (NOTE 2) | +| 33 | Retry-After | 404
413
480
486
500 | [13], [39] | o | do | + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|------|------------------|-------------------|------------|------------|-----------------------------------------| +| | | 503
600
603 | | | | +| 34 | Security-Server | 421
494 | [47], [39] | o | dn/a | +| 35 | Server | r | [13], [39] | o | do | +| 36 | Session-ID | r | [124] | m | IF table 6.1.3.1/94 THEN dm
(NOTE 2) | +| 37 | Supported | 2xx | [13], [39] | o | do | +| 38 | Timestamp | r | [13], [39] | o | do | +| 39 | To | 100
others | [13], [39] | m | dm | +| 40 | Unsupported | 420 | [13], [39] | o | do | +| 41 | User-Agent | r | [13], [39] | o | do | +| 42 | Via | 100
others | [13], [39] | m | dm | +| 43 | Warning | r | [13], [39] | o | do | +| 44 | WWW-Authenticate | 401
(NOTE 1) | [13], [39] | m | dm | + +NOTE 1: The SIP status code is only applicable over the roaming II-NNI. + +NOTE 2: If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. + +## --- B.7 INVITE method + +The table B.7.1 lists the supported header fields within the INVITE request. + +**Table B.7.1: Supported header fields within the INVITE request** + +| Item | Header field | Ref. | RFC status | II-NNI condition | +|------|-------------------------------|-------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Accept | [13] | o | IF dc1 (AOC: clause 12.22) THEN dm ELSE do | +| 2 | Accept-Contact | [51] | o | IF dc2 (PNM: clause 12.17) THEN dm ELSE do | +| 3 | Accept-Encoding | [13] | o | do | +| 4 | Accept-Language | [13] | o | do | +| 5 | Additional-Identity | [5] | n/a | IF table 6.1.3.1/126 THEN do (NOTE 3) | +| 6 | Alert-Info | [13] | o | IF dc3 (CRS: clause 12.15) THEN dm ELSE IF table 6.1.3.1/10 THEN do (NOTE 3) | +| 7 | Allow | [13] | o | do | +| 8 | Allow-Events | [20] | o | IF table 6.1.3.1/23 THEN do (NOTE 3) | +| 9 | Answer-Mode | [94] | o | IF table 6.1.3.1/90 THEN do (NOTE 3) | +| 10 | Authorization | [13] | o | IF table 6.1.3.1/7 THEN do (NOTE 3) | +| 11 | Attestation-Info | [5] | n/a | IF (non-roaming II-NNI OR loopback traversal scenario) AND table 6.1.3.1/123 THEN do (NOTE 3) | +| 12 | Call-ID | [13] | m | dm | +| 13 | Call-Info | [13] | o | IF dc4 (CCBS/CCNR/CCNL: clause 12.11/12.12/12.23) OR dc5 (announcements: clause 12.21) OR dc13 (eCNAM: clause 12.25) THEN dm ELSE do | +| 14 | Cellular-Network-Info | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE 3) | +| 15 | Contact | [13] | m | dm | +| 16 | Content-Disposition | [13] | o | IF dc6 (AOC: clause 12.22) THEN dm ELSE do | +| 17 | Content-Encoding | [13] | o | do | +| 18 | Content-ID | [216] | o | IF table 6.1.3.1/122 THEN do | +| 19 | Content-Language | [13] | o | do | +| 20 | Content-Length | [13] | t | dt | +| 21 | Content-Type | [13] | * | d* | +| 22 | CSeq | [13] | m | dm | +| 23 | Date | [13] | o | do | +| 24 | Expires | [13] | o | do | +| 25 | Feature-Caps | [143] | o | IF table 6.1.3.1/103 THEN do (NOTE 3) | +| 26 | From | [13] | m | dm | +| 27 | Geolocation | [68] | o | do | +| 28 | Geolocation-Routing | [68] | o | do | +| 29 | History-Info | [25] | o | IF dc7 (CDIV: clause 12.6) OR dc2 (PNM: clause 12.17) THEN dm ELSE IF table 6.1.3.1/50 AND initial request THEN do (NOTE 1, NOTE 3) | +| 30 | Identity | [206] | o | IF (non-roaming II-NNI OR loopback traversal scenario) AND table 6.1.3.1/119 THEN do (NOTE 3) | +| 31 | In-Reply-To | [13] | o | do | +| 32 | Join | [55] | o | IF table 6.1.3.1/48 THEN do (NOTE 3) | +| 33 | Max-Breadth | [79] | o | do | +| 34 | Max-Forwards | [13] | m | dm | +| 35 | MIME-Version | [13] | o | do | +| 36 | Min-SE | [52] | o | do | +| 37 | Organization | [13] | o | do | +| 38 | Origination-Id | [5] | n/a | IF (non-roaming II-NNI OR loopback traversal scenario) AND table 6.1.3.1/124 THEN do (NOTE 3) | +| 39 | P-Access-Network-Info | [24], [24B] | o | IF table 6.1.3.1/36 THEN do (NOTE 3) | +| 40 | P-Asserted-Identity | [44] | o | IF table 6.1.3.1/27 AND initial request THEN dm (NOTE 2, NOTE 3) | +| 41 | P-Asserted-Service | [26] | o | IF (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited request on roaming II-NNI) AND table 6.1.3.1/77 AND initial request THEN do (NOTE 3) | +| 42 | P-Called-Party-ID | [24] | o | IF home-to-visited request on roaming II-NNI AND table 6.1.3.1/34 THEN do (NOTE 3) | +| 43 | P-Charging-Function-Addresses | [24] | o | dn/a | +| 44 | P-Charging-Vector | [24] | o | IF table 6.1.3.1/38 AND initial request THEN dm (NOTE 3) | + +| Item | Header field | Ref. | RFC status | II-NNI condition | +|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|------------|------------------------------------------------------------------------------------------------------------------------------------| +| 45 | P-Early-Media | [74] | o | IF table 6.1.3.1/69 THEN do (NOTE 3) | +| 46 | P-Media-Authorization | [42] | o | dn/a | +| 47 | P-Preferred-Identity | [44] | o | dn/a | +| 48 | P-Preferred-Service | [26] | o | IF visited-to-home request on roaming II-NNI AND table 6.1.3.1/77 AND initial request THEN do (NOTE 3) | +| 49 | P-Private-Network-Indication | [84] | o | IF table 6.1.3.1/80 AND initial request THEN do (NOTE 3) | +| 50 | P-Profile-Key | [64] | o | IF table 6.1.3.1/59 AND initial request THEN do (NOTE 3) | +| 51 | P-Served-User | [85] | o | IF visited-to-home request on roaming II-NNI AND initial request being sent from "privileged sender" THEN dm (NOTE 3) | +| 52 | P-User-Database | [60] | o | dn/a | +| 53 | P-Visited-Network-ID | [24] | o | dn/a | +| 54 | Priority | [13] | o | do | +| 55 | Priority-Share | [5] | n/a | IF home-to-visited request on roaming II-NNI AND table 6.1.3.1/118 THEN do (NOTE 3) | +| 56 | Privacy | [34] | o | IF dc8 (OIP/OIR: clause 12.3) THEN dm ELSE do | +| 57 | Priv-Answer-Mode | [94] | o | IF table 6.1.3.1/90 THEN do (NOTE 3) | +| 58 | Proxy-Authorization | [13] | o | IF table 6.1.3.1/7 THEN do (NOTE 3) | +| 59 | Proxy-Require | [13] | o | do | +| 60 | Reason | [48] | o | IF table 6.1.3.1/40 AND subsequent request THEN do (NOTE 3) | +| 61 | Record-Route | [13] | o | do | +| 62 | Recv-Info | [39] | m | IF table 6.1.3.1/17 THEN dm (NOTE 3) | +| 63 | Referred-By | [53] | o | IF dc9 (ECT: clause 12.13) OR dc10 (CONF: clause 12.19) THEN dm ELSE do | +| 64 | Reject-Contact | [51] | o | do | +| 65 | Relayed-Charge | [5] | n/a | dn/a | +| 66 | Replaces | [54] | o | IF dc11 (ECT: clause 12.13) OR dc12 (CONF: clause 12.19) THEN dm ELSE IF table 6.1.3.1/47 THEN do (NOTE 3) | +| 67 | Reply-To | [13] | o | do | +| 68 | Request-Disposition | [51] | o | do | +| 69 | Require | [13] | c | IF dc11 (ECT: clause 12.13) THEN dm ELSE dc | +| 70 | Resource-Priority | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE 3) | +| 71 | Resource-Share | [5] | n/a | IF (home-to-visited request on roaming II-NNI OR visited-to-home request on roaming II-NNI) AND table 6.1.3.1/116 THEN do (NOTE 3) | +| 72 | Restoration-Info | [5] | n/a | IF home-to-visited request on roaming II-NNI AND initial request AND table 6.1.3.1/113 THEN do (NOTE 3) | +| 73 | Route | [13] | c | dc | +| 74 | Security-Client | [47] | o | dn/a | +| 75 | Security-Verify | [47] | o | dn/a | +| 76 | Service-Interact-Info | [5] | n/a | IF table 6.1.3.1/125 AND initial request THEN do (NOTE 3) | +| 77 | Session-Expires | [52] | o | do | +| 78 | Session-ID | [124] | m | IF table 6.1.3.1/94 THEN dm (NOTE 3) | +| 79 | Subject | [13] | o | do | +| 80 | Supported | [13] | m* | IF dc2 (PNM: clause 12.17) THEN dm ELSE dm* | +| 81 | Target-Dialog | [140] | o | IF table 6.1.3.1/102 THEN do (NOTE 3) | +| 82 | Timestamp | [13] | o | do | +| 83 | To | [13] | m | dm | +| 84 | Trigger-Consent | [82] | o | IF table 6.1.3.1/78 THEN do (NOTE 3) | +| 85 | User-Agent | [13] | o | do | +| 86 | User-to-User | [83] | o | IF table 6.1.3.1/79 THEN do (NOTE 3) | +| 87 | Via | [13] | m | dm | +| dc1: | request invoked due to AOC AND visited-to-home request on roaming II-NNI | | | | +| dc2: | initial request invoked due to PNM in case of ("PN UE redirection" OR "PN access control") AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited request on roaming II-NNI) | | | | + +| Item | Header field | Ref. | RFC status | II-NNI condition | +|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|------------|------------------| +| dc3: | initial request invoked due to CRS AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited request on roaming II-NNI) | | | | +| dc4: | initial request invoked due to CCBS/CCNR/CCNL AND "CC call" request AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited request on roaming II-NNI) | | | | +| dc5: | subsequent request invoked due to announcements using the Call-info header field AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited request on roaming II-NNI) | | | | +| dc6: | request invoked due to AOC AND home-to-visited request on roaming II-NNI | | | | +| dc7: | initial request towards the network serving "the diverted-to user" AND CFU/CFB/CFNR/CFNRc/CD/CFNL AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited request on roaming II-NNI) | | | | +| dc8: | (initial request invoked due to OIP/OIR AND "override the default setting" in temporary mode AND visited-to-home request on roaming II-NNI) OR (initial request invoked due to OIP/OIR AND "presentation of the public user identity is restricted" AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited request on roaming II-NNI)) | | | | +| dc9: | initial request invoked due to ECT AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited request on roaming II-NNI) | | | | +| dc10: | (initial request from "conference participant" receiving REFER request with Referred-By header field AND (visited-to-home request on roaming II-NNI OR non-roaming II-NNI OR loopback traversal scenario)) OR (initial request from "conference focus" receiving REFER request AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited request on roaming II-NNI)) | | | | +| dc11: | "Consultative transfer" due to ECT AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited request on roaming II-NNI) | | | | +| dc12: | initial request from "conference focus" receiving REFER request with Replaces header field escaped in Refer-To header field AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited request on roaming II-NNI) | | | | +| dc13: | initial request AND home-to-visited request on roaming II-NNI | | | | +| NOTE 1: | The Privacy header field can be escaped in the header field for CDIV. | | | | +| NOTE 2: | The header field is not included in some exceptional cases. (e.g. when an incoming call from a circuit-switched network has not included the required information to be mapped into the header field) | | | | +| NOTE 3: | If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. | | | | + +The table B.7.2 lists the supported header fields within the INVITE response. + +**Table B.7.2: Supported header fields within the INVITE response** + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|------|--------------------------|-----------------|-------------|------------|-----------------------------------------------------------------------------------------------------------------| +| 1 | Accept | 2xx | [13] | o | do | +| | | 415 | | c | dc | +| 2 | Accept-Encoding | 2xx | [13] | o | do | +| | | 415 | | c | dc | +| 3 | Accept-Language | 2xx | [13] | o | do | +| | | 415 | | c | dc | +| 4 | Accept-Resource-Priority | 2xx
417 | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE 3) | +| 5 | Alert-Info | 180 | [13] | o | IF dc1 (CW: clause 12.7) OR dc2 (announcements: clause 12.21) THEN dm ELSE IF table 6.1.3.1/10 THEN do (NOTE 3) | +| 6 | Allow | 2xx | [13] | m* | dm* | +| | | 405 | | m | dm | +| | | others | | o | do | +| 7 | Allow-Events | 2xx | [20] | o | IF table 6.1.3.1/23 THEN do (NOTE 3) | +| 8 | Answer-Mode | 2xx | [94] | o | IF table 6.1.3.1/90 THEN do (NOTE 3) | +| 9 | Authentication-Info | 2xx | [13] | o | IF table 6.1.3.1/7 THEN do (NOTE 3) | +| 10 | Call-ID | 100 | [13] | m | dm | +| | | others | | | | +| 11 | Call-Info | r | [13] | o | IF dc3 (CCBS: clause 12.11) OR dc4 (CCNR: clause 12.12) OR dc5 (CCNL: clause 12.23) THEN dm ELSE do | +| 12 | Cellular-Network-Info | r | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE 3) | +| 13 | Contact | 18x | [13]
[5] | o | dm | +| | | 199 | | | | +| | | 2xx | | m | dm | +| | | 3xx
485 | | o | do | +| 14 | Content-Disposition | r | [13] | o | IF dc6 (AOC: clause 12.22) THEN dm ELSE do | +| 15 | Content-Encoding | r | [13] | o | do | +| 16 | Content-ID | r | [216] | o | IF table 6.1.3.1/122 THEN do | +| 17 | Content-Language | r | [13] | o | do | +| 18 | Content-Length | 100 | [13] | t | dt | +| | | others | | | | +| 19 | Content-Type | r | [13] | * | IF dc7 (CCBS: clause 12.11) OR dc8 (CCNR/CCNL: clause 12.12/12.23) THEN dm ELSE d* | +| 20 | CSeq | 100 | [13] | m | dm | +| | | others | | | | +| 21 | Date | 100 | [13] | o | IF dc7 (CCBS: clause 12.11) OR dc8 (CCNR/CCNL: clause 12.12/12.23) THEN dm ELSE do | +| | | others | | | | +| 22 | Error-Info | 3xx-6xx | [13] | o | IF dc9 (announcements: clause 12.21) THEN dm ELSE IF table 6.1.3.1/13 THEN do (NOTE 3) | +| 23 | Expires | r | [13] | o | do | +| 24 | Feature-Caps | 18x | [143] | o | IF table 6.1.3.1/103 THEN do (NOTE 3) | +| | | 2xx | | | | +| 25 | From | 100 | [13] | m | dm | +| | | others | | | | +| 26 | Geolocation-Error | 424 | [68] | m | dm | +| | | others | | o | do | +| 27 | History-Info | r | [25] | o | IF dc10 (CDIV: clause 12.6) THEN dm ELSE IF table 6.1.3.1/50 AND response to initial request THEN do | + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|------|-------------------------------|-----------------|--------------------|------------|---------------------------------------------------------------------------------------------------------------------| +| | | | | | (NOTE 2, NOTE 3) | +| 28 | MIME-version | r | [13] | o | do | +| 29 | Min-SE | 422 | [52] | m | dm | +| 30 | Organization | r | [13] | o | do | +| 31 | P-Access-Network-Info | r | [24], [24A], [24B] | o | IF table 6.1.3.1/36 THEN do (NOTE 3) | +| 32 | P-Answer-State | 18x
2xx | [73] | o | IF table 6.1.3.1/68 THEN do (NOTE 3) | +| 33 | P-Asserted-Identity | r | [44] | o | IF dc11 (TIP/TIR: clause 12.4) THEN dm ELSE IF table 6.1.3.1/27 AND response to initial request THEN do (NOTE 3) | +| 34 | P-Charging-Function-Addresses | r | [24], [24A] | o | dn/a | +| 35 | P-Charging-Vector | 100 | [24], [24A] | o | dn/a | +| | | 18x, 2xx | | o | IF (table 6.1.3.1/38 AND response to initial request) OR dc 12(CONF: clause 12.19) THEN dm (NOTE 3) | +| | | 3xx-6xx | | o | do (NOTE 3) | +| 36 | P-Early-Media | 18x | [74] | o | IF dc13 (CAT: clause 12.14) OR dc14 (announcements: clause 12.21) THEN dm ELSE IF table 6.1.3.1/69 THEN do (NOTE 3) | +| 37 | P-Media-Authorization | 18x
2xx | [42] | o | dn/a | +| 38 | P-Preferred-Identity | r | [44] | o | dn/a | +| 39 | P-Refused-URI-List | 403 | [141] | o | IF (non-roaming II-NNI OR loopback traversal scenario) AND table 6.1.3.1/101 THEN do (NOTE 3) | +| 40 | Permission-Missing | 470 | [82] | o | IF table 6.1.3.1/78 THEN do (NOTE 3) | +| 41 | Priority-Share | 18x
2xx | [5] | n/a | IF home-to-visited response on roaming II-NNI AND table 6.1.3.1/118 THEN do (NOTE 3) | +| 42 | Privacy | r | [34] | o | IF dc15 (TIP/TIR: clause 12.4) THEN dm ELSE do | +| 43 | Priv-Answer-Mode | 2xx | [94] | o | IF table 6.1.3.1/90 THEN do (NOTE 3) | +| 44 | Proxy-Authenticate | 401
(NOTE 1) | [13] | o | do | + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|------|-----------------------|------------------------------------------------------|-------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | 407
(NOTE 1) | | m | dm | +| 45 | Reason | 18x
199
3xx-6xx | [48] | o | IF dc16 (CW: clause 12.7) OR
dc17 (ICB: clause 12.10.1) OR
dc18 (announcements: clause 12.21)
THEN dm ELSE IF table 6.1.3.1/40
THEN do (NOTE 3) | +| 46 | Record-Route | 18x
199
2xx | [13] | o | do | +| 47 | Recv-Info | 18x
199
2xx | [39] | c | IF table 6.1.3.1/17 THEN dc
(NOTE 3) | +| 48 | Relayed-Charge | r | [5] | n/a | dn/a | +| 49 | Reply-To | r | [13] | o | do | +| 50 | Require | r | [13] | c | IF dc19 (CAT: clause 12.14) THEN
dm ELSE dc | +| 51 | Resource-Share | 18x
2xx | [5] | n/a | IF (home-to-visited response on
roaming II-NNI OR visited-to-home
response on roaming II-NNI) AND
table 6.1.3.1/116 THEN do (NOTE 3) | +| 52 | Response-Source | 3xx-6xx | [5] | n/a | IF table 6.1.3.1/121 THEN do
(NOTE 3) | +| 53 | Restoration-Info | 408 | [5] | n/a | IF table 6.1.3.1/114 AND response to
initial request AND visited-to-home
response on roaming II-NNI THEN do
(NOTE 3) | +| 54 | Retry-After | 404
413
480
486
500
503
600
603 | [13] | o | do | +| 55 | RSeq | 18x
199 | [18] | o | do | +| 56 | Security-Server | 421
494 | [47] | o | dn/a | +| 57 | Server | r | [13] | o | do | +| 58 | Service-Interact-Info | 18x
2xx | [5] | n/a | IF table 6.1.3.1/125 AND response to
initial request THEN do (NOTE 3) | +| 59 | Session-Expires | 2xx | [52] | o | do | +| 60 | Session-ID | r | [124] | m | IF table 6.1.3.1/94 THEN dm
(NOTE 3) | +| 61 | Supported | 2xx | [13] | m* | dm* | +| 62 | Timestamp | r | [13] | o | do | +| 63 | To | 100
others | [13] | m | dm | +| 64 | Unsupported | 420 | [13] | m | dm | +| 65 | User-Agent | r | [13] | o | do | +| 66 | User-to-User | r | [83] | o | IF table 6.1.3.1/79 THEN do
(NOTE 3) | +| 67 | Via | 100
others | [13] | m | dm | +| 68 | Warning | r | [13] | o | IF dc20 (CDIV: clause 12.6) THEN
dm ELSE do | +| 69 | WWW-Authenticate | 401
(NOTE 1) | [13] | m | dm | + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------|------------|------------------| +| | | 407
(NOTE 1) | | o | do | +| dc1: | response invoked due to CW AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited response on roaming II-NNI) | | | | | +| dc2: | response to initial request invoked due to announcements using the Alert-Info header field AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited response on roaming II-NNI) | | | | | +| dc3: | 486 (Busy Here) response invoked due to CCBS AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited response on roaming II-NNI) | | | | | +| dc4: | 180 (Ringing) response invoked due to CCNR AND (non-roaming II-NNI OR loopback traversal scenario) | | | | | +| dc5: | 480 (Temporarily Unavailable) response invoked due to CCNL AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited response on roaming II-NNI) | | | | | +| dc6: | non-100 provisional response /200 (OK) response invoked due to AOC AND home-to-visited response on roaming II-NNI | | | | | +| dc7: | 486 (Busy Here) response invoked due to CCBS AND home-to-visited response on roaming II-NNI | | | | | +| dc8: | 480 (Temporarily Unavailable) response invoked due to CCNR/CCNL AND home-to-visited response on roaming II-NNI | | | | | +| dc9: | response to initial request invoked due to announcements using the Error-Info header field AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited response on roaming II-NNI) | | | | | +| dc10: | 180 (Ringing)/181 (Call Is Being Forwarded)/200 (OK) response to initial request AND CFU/CFB/CFNR/CFNRc/CD/CFNL AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited response on roaming II-NNI) | | | | | +| dc11: | (TIP/TIR AND 2xx response to initial request AND (visited-to-home response on roaming II-NNI OR non-roaming II-NNI OR loopback traversal scenario)) OR (TIP/TIR AND response to initial request AND "presentation is allowed" AND home-to-visited response on roaming II-NNI) | | | | | +| dc12: | first response from "conference focus" to initial request AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited response on roaming II-NNI) | | | | | +| dc13: | reliable 18x response to initial request invoked due to CAT using ("forking model" OR "gateway model") AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited response on roaming II-NNI) | | | | | +| dc14: | 18x response to initial request invoked due to announcements authorizing early media AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited response on roaming II-NNI) | | | | | +| dc15: | (TIP/TIR AND non-100 response to initial request AND "override the default setting" in temporary mode AND visited-to-home response on roaming II-NNI) OR (TIP/TIR AND 2xx response to initial request AND "presentation of the network asserted identity is restricted" AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited response on roaming II-NNI)) | | | | | +| dc16: | 480 (Temporarily Unavailable) response invoked due to CW at the expiry of the "CW timer" | | | | | +| dc17: | 603 (Decline) response invoked due to "dynamic ICB" on an early dialog | | | | | +| dc18: | 183 (Session Progress) response to initial request invoked due to announcements authorizing early media when rejecting a communication request AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited response on roaming II-NNI) | | | | | +| dc19: | first 18x response to initial request invoked due to CAT using "early session model" AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited response on roaming II-NNI) | | | | | +| dc20: | 480 (Temporarily Unavailable)/486 (Busy Here) response to initial request AND CFU/CFB/CFNR/CFNRc/CD/CFNL in case "maximum number of diversions" exceeds AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited response on roaming II-NNI) | | | | | +| NOTE 1: | The SIP status code is only applicable over the roaming II-NNI. | | | | | +| NOTE 2: | The Privacy header field can be escaped in the header field for CDIV. | | | | | +| NOTE 3: | If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. | | | | | + +## --- B.8 MESSAGE method + +As described in table 6.1, the support of MESSAGE method over the II-NNI is based on bilateral agreement between the operators. + +The table B.8.1 lists the supported header fields within the MESSAGE request. + +**Table B.8.1: Supported header fields within the MESSAGE request** + +| Item | Header field | Ref. | RFC status | II-NNI condition | +|------|-------------------------------|-------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Accept-Contact | [51] | o | IF dc1 (PNM: clause 12.17) THEN dm ELSE do | +| 2 | Additional-Identity | [5] | n/a | IF table 6.1.3.1/126 THEN do (NOTE) | +| 3 | Allow | [13], [19] | o | do | +| 4 | Allow-Events | [20] | o | IF table 6.1.3.1/23 THEN do (NOTE) | +| 5 | Attestation-Info | [5] | n/a | IF (non-roaming II-NNI OR loopback traversal scenario) AND table 6.1.3.1/123 THEN do (NOTE) | +| 6 | Authorization | [13], [19] | o | IF table 6.1.3.1/7 THEN do (NOTE) | +| 7 | Call-ID | [13], [19] | m | dm | +| 8 | Call-Info | [13], [19] | o | do | +| 9 | Cellular-Network-Info | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE) | +| 10 | Content-Disposition | [13], [19] | o | do | +| 11 | Content-Encoding | [13], [19] | o | do | +| 12 | Content-ID | [216] | o | IF table 6.1.3.1/122 THEN do | +| 13 | Content-Language | [13], [19] | o | do | +| 14 | Content-Length | [13], [19] | t | dt | +| 15 | Content-Type | [13], [19] | * | d* | +| 16 | CSeq | [13], [19] | m | dm | +| 17 | Date | [13], [19] | o | do | +| 18 | Expires | [13], [19] | o | do | +| 19 | Feature-Caps | [143] | o | IF table 6.1.3.1/103 AND request outside an existing dialog THEN do (NOTE) | +| 20 | From | [13], [19] | m | dm | +| 21 | Geolocation | [68] | o | do | +| 22 | Geolocation-Routing | [68] | o | do | +| 23 | History-Info | [25] | o | IF dc1 (PNM: clause 12.17) THEN dm ELSE IF table 6.1.3.1/50 AND request outside an existing dialog THEN do (NOTE) | +| 24 | Identity | [206] | o | IF (non-roaming II-NNI OR loopback traversal scenario) AND table 6.1.3.1/119 THEN do (NOTE) | +| 25 | In-Reply-To | [13], [19] | o | do | +| 26 | Max-Breadth | [79] | o | do | +| 27 | Max-Forwards | [13], [19] | m | dm | +| 28 | MIME-Version | [13] | o | do | +| 29 | Organization | [13], [19] | o | do | +| 30 | Origination-Id | [5] | n/a | IF (non-roaming II-NNI OR loopback traversal scenario) AND table 6.1.3.1/124 THEN do (NOTE) | +| 31 | P-Access-Network-Info | [24], [24B] | o | IF table 6.1.3.1/36 THEN do (NOTE) | +| 32 | P-Asserted-Identity | [44] | o | IF table 6.1.3.1/27 AND request outside an existing dialog THEN dm (NOTE) | +| 33 | P-Asserted-Service | [26] | o | IF (non-roaming II-NNI OR home-to-visited request on roaming II-NNI) AND table 6.1.3.1/77 AND request outside an existing dialog THEN do (NOTE) | +| 34 | P-Called-Party-ID | [24] | o | IF home-to-visited request on roaming II-NNI AND table 6.1.3.1/34 THEN do (NOTE) | +| 35 | P-Charging-Function-Addresses | [24] | o | dn/a | +| 36 | P-Charging-Vector | [24] | o | IF table 6.1.3.1/38 AND request outside an existing dialog THEN dm (NOTE) | +| 37 | P-Preferred-Identity | [44] | o | dn/a | +| 38 | P-Preferred-Service | [26] | o | IF visited-to-home request on roaming II-NNI AND table 6.1.3.1/77 AND request outside an existing dialog THEN do (NOTE) | +| 39 | P-Private-Network-Indication | [84] | o | IF table 6.1.3.1/80 AND request outside an existing dialog THEN do (NOTE) | +| 40 | P-Profile-Key | [64] | o | IF table 6.1.3.1/59 AND request outside an existing dialog THEN do (NOTE) | +| 41 | P-Served-User | [85] | o | IF visited-to-home request on roaming II-NNI AND request outside an existing dialog being sent from "privileged sender" THEN dm (NOTE) | +| 42 | P-User-Database | [60] | o | dn/a | +| 43 | P-Visited-Network-ID | [24] | o | dn/a | + +| Item | Header field | Ref. | RFC status | II-NNI condition | +|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------|----------------------------------------------------------------------------| +| 44 | Priority | [13], [19] | o | do | +| 45 | Privacy | [34] | o | IF dc2 (OIP/OIR: clause 12.3) THEN dm ELSE do | +| 46 | Proxy-Authorization | [13], [19] | o | IF table 6.1.3.1/7 THEN do (NOTE) | +| 47 | Proxy-Require | [13], [19] | o | do | +| 48 | Reason | [48] | o | IF table 6.1.3.1/40 AND request inside an existing dialog THEN do (NOTE) | +| 49 | Referred-By | [53] | o | do | +| 50 | Reject-Contact | [51] | o | do | +| 51 | Relayed-Charge | [5] | n/a | dn/a | +| 52 | Reply-To | [13], [19] | o | do | +| 53 | Request-Disposition | [51] | o | do | +| 54 | Require | [13], [19] | c | dc | +| 55 | Resource-Priority | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE) | +| 56 | Route | [13], [19] | c | dc | +| 57 | Security-Client | [47] | o | dn/a | +| 58 | Security-Verify | [47] | o | dn/a | +| 59 | Service-Interact-Info | [5] | n/a | IF table 6.1.3.1/125 AND request outside an existing dialog THEN do (NOTE) | +| 60 | Session-ID | [124] | m | IF table 6.1.3.1/94 THEN dm (NOTE) | +| 61 | Subject | [13], [19] | o | do | +| 62 | Supported | [13] | o | IF dc1 (PNM: clause 12.17) THEN dm ELSE do | +| 63 | Timestamp | [13], [19] | o | do | +| 64 | To | [13], [19] | m | dm | +| 65 | Trigger-Consent | [82] | o | IF table 6.1.3.1/78 THEN do (NOTE) | +| 66 | User-Agent | [13], [19] | o | do | +| 67 | Via | [13], [19] | m | dm | +| dc1: | request outside an existing dialog invoked due to PNM in case of ("PN UE redirection" OR "PN access control") AND (non-roaming II-NNI OR home-to-visited request on roaming II-NNI) | | | | +| dc2: | (request outside an existing dialog invoked due to OIP/OIR AND "override the default setting" in temporary mode AND visited-to-home request on roaming II-NNI) OR (request outside an existing dialog invoked due to OIP/OIR AND "presentation of the public user identity is restricted" AND (non-roaming II-NNI OR home-to-visited request on roaming II-NNI)) | | | | +| NOTE: | If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. | | | | + +The table B.8.2 lists the supported header fields within the MESSAGE response. + +###### **Table B.8.2: Supported header fields within the MESSAGE response** + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|------|-------------------------------|----------------------------|--------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Accept | 415 | [13], [19] | m* | dm* | +| 2 | Accept-Encoding | 415 | [13], [19] | m* | dm* | +| 3 | Accept-Language | 415 | [13], [19] | m* | dm* | +| 4 | Accept-Resource-Priority | 2xx
417 | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE 2) | +| 5 | Allow | 405 | [13], [19] | m | dm | +| | | others | | o | do | +| 6 | Allow-Events | 2xx | [20] | o | IF table 6.1.3.1/23 THEN do (NOTE 2) | +| 7 | Authentication-Info | 2xx | [13], [19] | o | IF table 6.1.3.1/7 THEN do (NOTE 2) | +| 8 | Call-ID | 100
others | [13], [19] | m | dm | +| 9 | Call-Info | r | [13], [19] | o | do | +| 10 | Cellular-Network-Info | r | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE 2) | +| 11 | Contact | 3xx
485 | [13], [19] | o | do | +| 12 | Content-Disposition | r | [13], [19] | o | do | +| 13 | Content-Encoding | r | [13], [19] | o | do | +| 14 | Content-ID | r | [216] | o | IF table 6.1.3.1/122 THEN do | +| 15 | Content-Language | r | [13], [19] | o | do | +| 16 | Content-Length | 100
others | [13], [19] | t | dt | +| 17 | Content-Type | r | [13], [19] | * | d* | +| 18 | CSeq | 100
others | [13], [19] | m | dm | +| 19 | Date | 100
others | [13], [19] | o | do | +| 20 | Error-Info | 3xx-6xx | [13], [19] | o | IF table 6.1.3.1/13 THEN do (NOTE 2) | +| 21 | Expires | r | [13], [19] | o | do | +| 22 | Feature-Caps | 2xx | [143] | o | IF table 6.1.3.1/103 AND response to request outside an existing dialog THEN do (NOTE 2) | +| 23 | From | 100
others | [13], [19] | m | dm | +| 24 | Geolocation-Error | 424
others | [68] | m
o | dm
do | +| 25 | History-Info | r | [25] | o | IF table 6.1.3.1/50 AND response to request outside an existing dialog THEN do (NOTE 2) | +| 26 | MIME-version | r | [13] | o | do | +| 27 | Organization | r | [13], [19] | o | do | +| 28 | P-Access-Network-Info | r | [24], [24A], [24B] | o | IF table 6.1.3.1/36 THEN do (NOTE 2) | +| 29 | P-Asserted-Identity | r | [44] | o | IF dc1 (TIP/TIR: clause 12.4) THEN dm ELSE IF table 6.1.3.1/27 AND response to request outside an existing dialog THEN do (NOTE 2) | +| 30 | P-Charging-Function-Addresses | r | [24], [24A], [24B] | o | dn/a | +| 31 | P-Charging-Vector | 100
18x, 2xx
3xx-6xx | [24], [24A] | o
o
o | dn/a
IF table 6.1.3.1/38 AND response to request outside an existing dialog THEN dm (NOTE 2)
do (NOTE 3) | +| 32 | P-Preferred-Identity | r | [44] | o | dn/a | +| 33 | Permission-Missing | 470 | [82] | o | IF table 6.1.3.1/78 THEN do (NOTE 2) | +| 34 | Privacy | r | [34] | o | IF dc2(TIP/TIR: clause 12.4) THEN dm ELSE do | +| 35 | Proxy-Authenticate | 401 | [13], [19] | o | do | + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|------------|------------|------------------------------------------------------------------------------------------| +| | | (NOTE 1) | | | | +| | | 407
(NOTE 1) | | m | dm | +| 36 | Relayed-Charge | r | [5] | n/a | dn/a | +| 37 | Reply-To | r | [13], [19] | o | do | +| 38 | Require | r | [13], [19] | c | dc | +| 39 | Response-Source | 3xx-6xx | [5] | n/a | IF table 6.1.3.1/121 THEN do
(NOTE 2) | +| 40 | Restoration-Info | 504 | [5] | n/a | IF table 6.1.3.1/114 AND visited-to-home response on roaming II-NNI THEN do (NOTE 2) | +| 41 | Retry-After | 404
413
480
486
500
503
600
603 | [13], [19] | o | do | +| 42 | Security-Server | 421
494 | [47] | o | dn/a | +| 43 | Server | r | [13], [19] | o | do | +| 44 | Service-Interact-Info | 18x
2xx | [5] | n/a | IF table 6.1.3.1/125 AND response to request outside an existing dialog THEN do (NOTE 2) | +| 45 | Session-ID | r | [124] | m | IF table 6.1.3.1/94 THEN dm
(NOTE 2) | +| 46 | Supported | 2xx | [13] | o | do | +| 47 | Timestamp | r | [13], [19] | o | do | +| 48 | To | 100
others | [13], [19] | m | dm | +| 49 | Unsupported | 420 | [13], [19] | o | do | +| 50 | User-Agent | r | [13], [19] | o | do | +| 51 | Via | 100
others | [13], [19] | m | dm | +| 52 | Warning | r | [13], [19] | o | do | +| 53 | WWW-Authenticate | 401
(NOTE 1) | [13], [19] | m | dm | +| | | 407
(NOTE 1) | | o | do | +| dc1: | (TIP/TIR AND 2xx response to request outside an existing dialog AND (visited-to-home response on roaming II-NNI OR non-roaming II-NNI)) OR (TIP/TIR AND response to request outside an existing dialog AND "presentation is allowed" AND home-to-visited response on roaming II-NNI) | | | | | +| dc2: | (TIP/TIR AND non-100 response to request outside an existing dialog AND "override the default setting" in temporary mode AND visited-to-home response on roaming II-NNI) OR (TIP/TIR AND 2xx response to request outside an existing dialog AND "presentation of the network asserted identity is restricted" AND (non-roaming II-NNI OR home-to-visited response on roaming II-NNI)) | | | | | +| NOTE 1: | The SIP status code is only applicable over the roaming II-NNI. | | | | | +| NOTE 2: | If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. | | | | | + +## --- B.9 NOTIFY method + +As described in table 6.1, the support of NOTIFY method over the non-roaming II-NNI is based on bilateral agreement between the operators. + +The table B.9.1 lists the supported header fields within the NOTIFY request. + +**Table B.9.1: Supported header fields within the NOTIFY request** + +| Item | Header field | Ref. | RFC status | II-NNI condition | +|------|-------------------------------|-------------|------------|-------------------------------------| +| 1 | Accept | [13], [20] | o | do | +| 2 | Accept-Contact | [51] | o | do | +| 3 | Accept-Encoding | [13], [20] | o | do | +| 4 | Accept-Language | [13], [20] | o | do | +| 5 | Allow | [13], [20] | o | do | +| 6 | Allow-Events | [20] | o | do | +| 7 | Authorization | [13], [20] | o | IF table 6.1.3.1/7 THEN do (NOTE) | +| 8 | Call-ID | [13], [20] | m | dm | +| 9 | Call-Info | [13] | o | do | +| 10 | Cellular-Network-Info | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE) | +| 11 | Contact | [13], [20] | m | dm | +| 12 | Content-Disposition | [13], [20] | o | do | +| 13 | Content-Encoding | [13], [20] | o | do | +| 14 | Content-ID | [216] | o | IF table 6.1.3.1/122 THEN do | +| 15 | Content-Language | [13], [20] | o | do | +| 16 | Content-Length | [13], [20] | t | dt | +| 17 | Content-Type | [13], [20] | * | d* | +| 18 | CSeq | [13], [20] | m | dm | +| 19 | Date | [13], [20] | o | do | +| 20 | Event | [20] | m | dm | +| 21 | Feature-Caps | [143] | o | IF table 6.1.3.1/103 THEN do (NOTE) | +| 22 | From | [13], [20] | m | dm | +| 23 | Geolocation | [68] | o | do | +| 24 | Geolocation-Routing | [68] | o | do | +| 25 | History-Info | [25] | o | IF table 6.1.3.1/50 THEN do (NOTE) | +| 26 | Max-Breadth | [79] | o | do | +| 27 | Max-Forwards | [13], [20] | m | dm | +| 28 | MIME-Version | [13], [20] | o | do | +| 29 | P-Access-Network-Info | [24], [24B] | o | IF table 6.1.3.1/36 THEN do (NOTE) | +| 30 | P-Asserted-Identity | [44] | o | IF table 6.1.3.1/27 THEN do (NOTE) | +| 31 | P-Charging-Function-Addresses | [24] | o | dn/a | +| 32 | P-Charging-Vector | [24] | o | IF table 6.1.3.1/38 THEN dm (NOTE) | +| 33 | P-Preferred-Identity | [44] | o | dn/a | +| 34 | Privacy | [34] | o | do | +| 35 | Proxy-Authorization | [13], [20] | o | IF table 6.1.3.1/7 THEN do (NOTE) | +| 36 | Proxy-Require | [13], [20] | o | do | +| 37 | Reason | [48] | o | IF table 6.1.3.1/40 THEN do (NOTE) | +| 38 | Record-Route | [13], [20] | o | do | +| 39 | Referred-By | [53] | o | do | +| 40 | Reject-Contact | [51] | o | do | +| 41 | Relayed-Charge | [5] | n/a | dn/a | +| 42 | Request-Disposition | [51] | o | do | +| 43 | Require | [13], [20] | o | do | +| 44 | Resource-Priority | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE) | +| 45 | Route | [13], [20] | c | dc | +| 46 | Security-Client | [47] | o | dn/a | +| 47 | Security-Verify | [47] | o | dn/a | +| 48 | Session-ID | [124] | m | IF table 6.1.3.1/94 THEN dm (NOTE) | +| 49 | Subscription-State | [20] | m | dm | +| 50 | Supported | [13], [20] | o | do | +| 51 | Timestamp | [13], [20] | o | do | +| 52 | To | [13], [20] | m | dm | +| 53 | User-Agent | [13], [20] | o | do | +| 54 | Via | [13], [20] | m | dm | +| 55 | Warning | [13], [20] | o | do | + +NOTE: If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. + +The table B.9.2 lists the supported header fields within the NOTIFY response. + +###### **Table B.9.2: Supported header fields within the NOTIFY response** + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|------|-------------------------------|------------------------------|--------------------|-------------|--------------------------------------------------------------------------------------| +| 1 | Accept | 415 | [13], [20] | o | do | +| 2 | Accept-Encoding | 415 | [13], [20] | o | do | +| 3 | Accept-Language | 415 | [13], [20] | o | do | +| 4 | Accept-Resource-Priority | 2xx
417 | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE 2) | +| 5 | Allow | 405
others | [13], [20] | m
o | dm
do | +| 6 | Allow-Events | 2xx
489 | [20] | o
m | do
dm | +| 7 | Authentication-Info | 2xx | [13], [20] | o | IF table 6.1.3.1/7 THEN do (NOTE 2) | +| 8 | Call-ID | 100
others | [13], [20] | m | dm | +| 9 | Cellular-Network-Info | r | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE 2) | +| 10 | Contact | 2xx
3xx
485 | [13], [20] | o
m
o | do
dm
do | +| 11 | Content-Disposition | r | [13], [20] | o | do | +| 12 | Content-Encoding | r | [13], [20] | o | do | +| 13 | Content-ID | r | [216] | o | IF table 6.1.3.1/122 THEN do | +| 14 | Content-Language | r | [13], [20] | o | do | +| 15 | Content-Length | 100
others | [13], [20] | t | dt | +| 16 | Content-Type | r | [13], [20] | * | d* | +| 17 | CSeq | 100
others | [13], [20] | m | dm | +| 18 | Date | 100
others | [13], [20] | o | do | +| 19 | Error-Info | 3xx-6xx | [13], [20] | o | IF table 6.1.3.1/13 THEN do (NOTE 2) | +| 20 | Feature-Caps | 2xx | [143] | o | IF table 6.1.3.1/103 THEN do (NOTE 2) | +| 21 | From | 100
others | [13], [20] | m | dm | +| 22 | Geolocation-Error | 424
others | [68] | m
o | dm
do | +| 23 | MIME-version | r | [13], [20] | o | do | +| 24 | P-Access-Network-Info | r | [24], [24A], [24B] | o | IF table 6.1.3.1/36 THEN do (NOTE 2) | +| 25 | P-Asserted-Identity | r | [44] | o | IF table 6.1.3.1/27 THEN do (NOTE 2) | +| 26 | P-Charging-Function-Addresses | r | [24], [24A] | o | dn/a | +| 27 | P-Charging-Vector | 100
18x, 2xx
3xx-6xx | [24], [24A] | o
o
o | dn/a
IF table 6.1.3.1/38 THEN dm (NOTE 2)
do (NOTE 3) | +| 28 | P-Preferred-Identity | r | [44] | o | dn/a | +| 29 | Privacy | r | [34] | o | do | +| 30 | Proxy-Authenticate | 401 (NOTE 1)
407 (NOTE 1) | [13], [20] | o
m | do
dm | +| 31 | Record-Route | 2xx | [13], [20] | o | do | +| 32 | Relayed-Charge | r | [5] | n/a | dn/a | +| 33 | Require | r | [13], [20] | o | do | +| 34 | Response-Source | 3xx-6xx | [5] | n/a | IF table 6.1.3.1/121 THEN do (NOTE 2) | +| 35 | Restoration-Info | 504 | [5] | n/a | IF table 6.1.3.1/114 AND visited-to-home response on roaming II-NNI THEN do (NOTE 2) | +| 36 | Retry-After | 404
413 | [13], [20] | o | do | + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|------|------------------|----------------------------------------|------------|------------|-----------------------------------------| +| | | 480
486
500
503
600
603 | | | | +| 37 | Security-Server | 421
494 | [47] | o | dn/a | +| 38 | Server | r | [13], [20] | o | do | +| 39 | Session-ID | r | [124] | m | IF table 6.1.3.1/94 THEN dm
(NOTE 2) | +| 40 | Supported | 2xx | [13], [20] | o | do | +| 41 | Timestamp | r | [13], [20] | o | do | +| 42 | To | 100
others | [13], [20] | m | dm | +| 43 | Unsupported | 420 | [13], [20] | o | do | +| 44 | User-Agent | r | [13], [20] | o | do | +| 45 | Via | 100
others | [13], [20] | m | dm | +| 46 | Warning | r | [13], [20] | o | do | +| 47 | WWW-Authenticate | 401
(NOTE 1) | [13], [20] | m | dm | +| | | 407
(NOTE 1) | | o | do | + +NOTE 1: The SIP status code is only applicable over the roaming II-NNI. + +NOTE 2: If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. + +## --- B.10 OPTIONS method + +The table B.10.1 lists the supported header fields within the OPTIONS request. + +**Table B.10.1: Supported header fields within the OPTIONS request** + +| Item | Header field | Ref. | RFC status | II-NNI condition | +|------|-------------------------------|-------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Accept | [13] | m* | dm* | +| 2 | Accept-Contact | [51] | o | IF dc1 (PNM: clause 12.17) THEN dm ELSE do | +| 3 | Accept-Encoding | [13] | o | do | +| 4 | Accept-Language | [13] | o | do | +| 5 | Allow | [13] | o | do | +| 6 | Allow-Events | [20] | o | IF table 6.1.3.1/23 THEN do (NOTE) | +| 7 | Authorization | [13] | o | IF table 6.1.3.1/7 THEN do (NOTE) | +| 8 | Call-ID | [13] | m | dm | +| 9 | Call-Info | [13] | o | do | +| 10 | Cellular-Network-Info | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE) | +| 11 | Contact | [13] | o | do | +| 12 | Content-Disposition | [13] | o | do | +| 13 | Content-Encoding | [13] | o | do | +| 14 | Content-ID | [216] | o | IF table 6.1.3.1/122 THEN do | +| 15 | Content-Language | [13] | o | do | +| 16 | Content-Length | [13] | t | dt | +| 17 | Content-Type | [13] | * | d* | +| 18 | CSeq | [13] | m | dm | +| 19 | Date | [13] | o | do | +| 20 | Feature-Caps | [143] | o | IF table 6.1.3.1/103 AND request outside an existing dialog THEN do (NOTE) | +| 21 | From | [13] | m | dm | +| 22 | Geolocation | [68] | o | do | +| 23 | Geolocation-Routing | [68] | o | do | +| 24 | History-Info | [25] | o | IF (dc1 (PNM: clause 12.17) THEN dm ELSE IF table 6.1.3.1/50 AND request outside an existing dialog THEN do (NOTE) | +| 25 | Max-Breadth | [79] | o | do | +| 26 | Max-Forwards | [13] | m | dm | +| 27 | MIME-Version | [13] | o | do | +| 28 | Organization | [13] | o | do | +| 29 | P-Access-Network-Info | [24], [24B] | o | IF table 6.1.3.1/36 THEN do (NOTE) | +| 30 | P-Asserted-Identity | [44] | o | IF table 6.1.3.1/27 AND request outside an existing dialog THEN dm (NOTE) | +| 31 | P-Asserted-Service | [26] | o | IF (non-roaming II-NNI OR home-to-visited request on roaming II-NNI) AND table 6.1.3.1/77 AND request outside an existing dialog THEN do (NOTE) | +| 32 | P-Called-Party-ID | [24] | o | IF home-to-visited request on roaming II-NNI AND table 6.1.3.1/34 THEN do (NOTE) | +| 33 | P-Charging-Function-Addresses | [24] | o | dn/a | +| 34 | P-Charging-Vector | [24] | o | IF table 6.1.3.1/38 AND request outside an existing dialog THEN dm (NOTE) | +| 35 | P-Preferred-Identity | [44] | o | dn/a | +| 36 | P-Preferred-Service | [26] | o | IF visited-to-home request on roaming II-NNI AND table 6.1.3.1/77 AND request outside an existing dialog THEN do (NOTE) | +| 37 | P-Private-Network-Indication | [84] | o | IF table 6.1.3.1/80 AND request outside an existing dialog THEN do (NOTE) | +| 38 | P-Profile-Key | [64] | o | IF table 6.1.3.1/59 AND request outside an existing dialog THEN do (NOTE) | +| 39 | P-Served-User | [85] | o | IF visited-to-home request on roaming II-NNI AND request outside an existing dialog being sent from "privileged sender" THEN dm (NOTE) | +| 40 | P-User-Database | [60] | o | dn/a | +| 41 | P-Visited-Network-ID | [24] | o | dn/a | +| 42 | Privacy | [34] | o | IF dc2 (OIP/OIR: clause 12.3) THEN dm ELSE do | +| 43 | Proxy-Authorization | [13] | o | IF table 6.1.3.1/7 THEN do (NOTE) | +| 44 | Proxy-Require | [13] | o | do | +| 45 | Reason | [48] | o | IF table 6.1.3.1/40 AND request inside an existing dialog THEN do (NOTE) | +| 46 | Record-Route | [13] | o | do | +| 47 | Recv-Info | [39] | n/a | dn/a | + +| Item | Header field | Ref. | RFC status | II-NNI condition | +|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|------------|--------------------------------------------| +| 48 | Referred-By | [53] | o | do | +| 49 | Reject-Contact | [51] | o | do | +| 50 | Relayed-Charge | [5] | n/a | dn/a | +| 51 | Request-Disposition | [51] | o | do | +| 52 | Require | [13] | c | dc | +| 53 | Resource-Priority | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE) | +| 54 | Route | [13] | c | dc | +| 55 | Security-Client | [47] | o | dn/a | +| 56 | Security-Verify | [47] | o | dn/a | +| 57 | Session-ID | [124] | m | IF table 6.1.3.1/94 THEN dm (NOTE) | +| 58 | Supported | [13] | o | IF dc1 (PNM: clause 12.17) THEN dm ELSE do | +| 59 | Timestamp | [13] | o | do | +| 60 | To | [13] | m | dm | +| 61 | User-Agent | [13] | o | do | +| 62 | Via | [13] | m | dm | +| dc1: | request outside an existing dialog invoked due to PNM in case of ("PN UE redirection" OR "PN access control") AND (non-roaming II-NNI OR home-to-visited request on roaming II-NNI) | | | | +| dc2: | (request outside an existing dialog invoked due to OIP/OIR AND "override the default setting" in temporary mode AND visited-to-home request on roaming II-NNI) OR (request outside an existing dialog invoked due to OIP/OIR AND "presentation of the public user identity is restricted" AND (non-roaming II-NNI OR home-to-visited request on roaming II-NNI)) | | | | +| NOTE: | If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. | | | | + +The table B.10.2 lists the supported header fields within the OPTIONS response. + +**Table B.10.2: Supported header fields within the OPTIONS response** + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|------|-------------------------------|-------------------|--------------------|------------|------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Accept | 2xx | [13] | m* | dm* | +| | | 415 | | c | dc | +| 2 | Accept-Encoding | 2xx | [13] | m* | dm* | +| | | 415 | | c | dc | +| 3 | Accept-Language | 2xx | [13] | m* | dm* | +| | | 415 | | c | dc | +| 4 | Accept-Resource-Priority | 2xx
417 | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE 2) | +| 5 | Allow | 2xx | [13] | m* | dm* | +| | | 405 | | m | dm | +| | | others | | o | do | +| 6 | Allow-Events | 2xx | [20] | o | IF table 6.1.3.1/23 THEN do (NOTE 2) | +| 7 | Authentication-Info | 2xx | [13] | o | IF table 6.1.3.1/7 THEN do (NOTE 2) | +| 8 | Call-ID | 100 | [13] | m | dm | +| | | others | | | | +| 9 | Call-Info | r | [13] | o | do | +| 10 | Cellular-Network-Info | r | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE 2) | +| 11 | Contact | 2xx
3xx
485 | [13] | o | do | +| 12 | Content-Disposition | r | [13] | o | do | +| 13 | Content-Encoding | r | [13] | o | do | +| 14 | Content-ID | r | [216] | o | IF table 6.1.3.1/122 THEN do | +| 15 | Content-Language | r | [13] | o | do | +| 16 | Content-Length | 100 | [13] | t | dt | +| | | others | | | | +| 17 | Content-Type | r | [13] | * | d* | +| 18 | CSeq | 100 | [13] | m | dm | +| | | others | | | | +| 19 | Date | 100 | [13] | o | do | +| | | others | | | | +| 20 | Error-Info | 3xx-6xx | [13] | o | IF table 6.1.3.1/13 THEN do (NOTE 2) | +| 21 | Feature-Caps | 2xx | [143] | o | IF table 6.1.3.1/103 AND response to request outside an existing dialog THEN do (NOTE 2) | +| 22 | From | 100 | [13] | m | dm | +| | | others | | | | +| 23 | Geolocation-Error | 424 | [68] | m | dm | +| | | others | | o | do | +| 24 | History-Info | r | [25] | o | IF table 6.1.3.1/50 AND response to request outside an existing dialog THEN do (NOTE 2) | +| 25 | MIME-version | r | [13] | o | do | +| 26 | Organization | r | [13] | o | do | +| 27 | P-Access-Network-Info | r | [24], [24A], [24B] | o | IF table 6.1.3.1/36 THEN do (NOTE 2) | +| 28 | P-Asserted-Identity | r | [44] | o | IF dc1 (TIP/TIR: clause 12.4) THEN dm ELSE IF table 6.1.3.1/27 AND response to request outside an existing dialog THEN do (NOTE 2) | +| 29 | P-Charging-Function-Addresses | r | [24], [24A] | o | dn/a | +| 30 | P-Charging-Vector | 100 | [24], | o | dn/a | + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | | +|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|-------|------------|-----------------------------------------------------------------------------------------|--| +| | | 18x, 2xx | [24A] | o | IF table 6.1.3.1/38 AND response to request outside an existing dialog THEN dm (NOTE 2) | | +| | | 3xx-6xx | | o | do (NOTE 2) | | +| 31 | P-Preferred-Identity | r | [44] | o | dn/a | | +| 32 | Privacy | r | [34] | o | IF dc2 (TIP/TIR: clause 12.4) THEN dm ELSE do | | +| 33 | Proxy-Authenticate | 401 (NOTE 1) | [13] | o | do | | +| | | 407 (NOTE 1) | | m | dm | | +| 34 | Record-Route | 2xx | [13] | o | do | | +| 35 | Recv-Info | 2xx
others | [39] | n/a | dn/a | | +| 36 | Relayed-Charge | r | [5] | n/a | dn/a | | +| 37 | Require | r | [13] | c | dc | | +| 38 | Response-Source | 3xx-6xx | [5] | n/a | IF table 6.1.3.1/121 THEN do (NOTE 2) | | +| 39 | Restoration-Info | 504 | [5] | n/a | IF table 6.1.3.1/114 AND visited-to-home response on roaming II-NNI THEN do (NOTE 2) | | +| 40 | Retry-After | 404
413
480
486
500
503
600
603 | [13] | o | do | | +| 41 | Security-Server | 421
494 | [47] | o | dn/a | | +| 42 | Server | r | [13] | o | do | | +| 43 | Session-ID | r | [124] | m | IF table 6.1.3.1/94 THEN dm (NOTE 2) | | +| 44 | Supported | 2xx | [13] | m* | dm* | | +| 45 | Timestamp | r | [13] | o | do | | +| 46 | To | 100
others | [13] | m | dm | | +| 47 | Unsupported | 420 | [13] | m | dm | | +| 48 | User-Agent | r | [13] | o | do | | +| 49 | Via | 100
others | [13] | m | dm | | +| 50 | Warning | r | [13] | o | do | | +| 51 | WWW-Authenticate | 401 (NOTE 1) | [13] | m | dm | | +| | | 407 (NOTE 1) | | o | do | | +| dc1: | (TIP/TIR AND 2xx response to request outside an existing dialog AND (visited-to-home response on roaming II-NNI OR non-roaming II-NNI)) OR (TIP/TIR AND response to request outside an existing dialog AND "presentation is allowed" AND home-to-visited response on roaming II-NNI) | | | | | | +| dc2: | (TIP/TIR AND non-100 response to request outside an existing dialog AND "override the default setting" in temporary mode AND visited-to-home response on roaming II-NNI) OR (TIP/TIR AND 2xx response to request outside an existing dialog AND "presentation of the network asserted identity is restricted" AND (non-roaming II-NNI OR home-to-visited response on roaming II-NNI)) | | | | | | +| NOTE 1: | The SIP status code is only applicable over the roaming II-NNI. | | | | | | +| NOTE 2: | If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. | | | | | | + +## --- B.11 PRACK method + +The table B.11.1 lists the supported header fields within the PRACK request. + +**Table B.11.1: Supported header fields within the PRACK request** + +| Item | Header field | Ref. | RFC status | II-NNI condition | +|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|------------|----------------------------------------------------------------------------------------------------------------------------------| +| 1 | Accept | [13], [18] | o | do | +| 2 | Accept-Contact | [51] | o | do | +| 3 | Accept-Encoding | [13], [18] | o | do | +| 4 | Accept-Language | [13], [18] | o | do | +| 5 | Allow | [13], [18] | o | do | +| 6 | Allow-Events | [20] | o | IF table 6.1.3.1/23 THEN do (NOTE) | +| 7 | Authorization | [13], [18] | o | IF table 6.1.3.1/7 THEN do (NOTE) | +| 8 | Call-ID | [13], [18] | m | dm | +| 9 | Cellular-Network-Info | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE) | +| 10 | Content-Disposition | [13], [18] | o | do | +| 11 | Content-Encoding | [13], [18] | o | do | +| 12 | Content-ID | [216] | o | IF table 6.1.3.1/122 THEN do | +| 13 | Content-Language | [13], [18] | o | do | +| 14 | Content-Length | [13], [18] | t | dt | +| 15 | Content-Type | [13], [18] | * | d* | +| 16 | CSeq | [13], [18] | m | dm | +| 17 | Date | [13], [18] | o | do | +| 18 | From | [13], [18] | m | dm | +| 19 | Max-Breadth | [79] | o | do | +| 20 | Max-Forwards | [13], [18] | m | dm | +| 21 | MIME-Version | [13], [18] | o | do | +| 22 | P-Access-Network-Info | [24], [24B] | o | IF table 6.1.3.1/36 THEN do (NOTE) | +| 23 | P-Charging-Function-Addresses | [24] | o | dn/a | +| 24 | P-Charging-Vector | [24] | o | IF table 6.1.3.1/38 THEN do (NOTE) | +| 25 | P-Early-Media | [74] | o | IF dc1 (CAT: clause 12.14) THEN dm ELSE IF table 6.1.3.1/69 THEN do (NOTE) | +| 26 | Priority-Share | [5] | n/a | IF home-to-visited request on roaming II-NNI AND table 6.1.3.1/118 THEN do (NOTE) | +| 27 | Privacy | [34] | o | do | +| 28 | Proxy-Authorization | [13], [18] | o | IF table 6.1.3.1/7 THEN do (NOTE) | +| 29 | Proxy-Require | [13], [18] | o | do | +| 30 | RAck | [18] | m | dm | +| 31 | Reason | [48] | o | IF table 6.1.3.1/40 THEN do (NOTE) | +| 32 | Record-Route | [13], [18] | o | do | +| 33 | Recv-Info | [39] | o | IF table 6.1.3.1/17 THEN do (NOTE) | +| 34 | Referred-By | [53] | o | do | +| 35 | Reject-Contact | [51] | o | do | +| 36 | Relayed-Charge | [5] | n/a | dn/a | +| 37 | Request-Disposition | [51] | o | do | +| 38 | Require | [13], [18] | c | dc | +| 39 | Resource-Priority | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE) | +| 40 | Resource-Share | [5] | n/a | IF (home-to-visited request on roaming II-NNI OR visited-to-home request on roaming II-NNI) AND table 6.1.3.1/116 THEN do (NOTE) | +| 41 | Route | [13], [18] | c | dc | +| 42 | Session-ID | [124] | m | IF table 6.1.3.1/94 THEN dm (NOTE) | +| 43 | Supported | [13], [18] | o | do | +| 44 | Timestamp | [13], [18] | o | do | +| 45 | To | [13], [18] | m | dm | +| 46 | User-Agent | [13], [18] | o | do | +| 47 | Via | [13], [18] | m | dm | +| dc1: | request invoked due to CAT to first 18x response with P-Early-Media header field cancelling "CAT service" provided by terminating AS AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited request on roaming II-NNI) | | | | +| NOTE: | If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. | | | | + +The table B.11.2 lists the supported header fields within the PRACK response. + +**Table B.11.2: Supported header fields within the PRACK response** + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|------|-------------------------------|------------------------------------|--------------------|------------|--------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Accept | 415 | [13], [18] | c | dc | +| 2 | Accept-Encoding | 415 | [13], [18] | c | dc | +| 3 | Accept-Language | 415 | [13], [18] | c | dc | +| 4 | Accept-Resource-Priority | 2xx
417 | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE 2) | +| 5 | Allow | 405 | [13], [18] | m | dm | +| | | others | | o | do | +| 6 | Allow-Events | 2xx | [20] | o | IF table 6.1.3.1/23 THEN do (NOTE 2) | +| 7 | Authentication-Info | 2xx | [13], [18] | o | IF table 6.1.3.1/7 THEN do (NOTE 2) | +| 8 | Call-ID | 100
r | [13], [18] | m | dm | +| 9 | Cellular-Network-Info | r | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE 2) | +| 10 | Contact | 3xx
485 | [13], [18] | o | do | +| 11 | Content-Disposition | r | [13], [18] | o | do | +| 12 | Content-Encoding | r | [13], [18] | o | do | +| 13 | Content-ID | r | [216] | o | IF table 6.1.3.1/122 THEN do | +| 14 | Content-Language | r | [13], [18] | o | do | +| 15 | Content-Length | 100
others | [13], [18] | t | dt | +| 16 | Content-Type | r | [13], [18] | * | d* | +| 17 | CSeq | 100
others | [13], [18] | m | dm | +| 18 | Date | 100
others | [13], [18] | o | do | +| 19 | Error-Info | 3xx-6xx | [13], [18] | o | IF table 6.1.3.1/13 THEN do (NOTE 2) | +| 20 | From | 100
others | [13], [18] | m | dm | +| 21 | MIME-version | r | [13], [18] | o | do | +| 22 | P-Access-Network-Info | r | [24], [24A], [24B] | o | IF table 6.1.3.1/36 THEN do (NOTE 2) | +| 23 | P-Charging-Function-Addresses | r | [24], [24A] | o | dn/a | +| 24 | P-Charging-Vector | 100
others | [24], [24A] | o
o | dn/a
IF table 6.1.3.1/38 THEN do (NOTE 2) | +| 25 | P-Early-Media | 2xx | [74] | o | IF table 6.1.3.1/69 THEN do (NOTE 2) | +| 26 | Priority-Share | 2xx | [5] | n/a | IF home-to-visited response on roaming II-NNI AND table 6.1.3.1/118 THEN do (NOTE 2) | +| 27 | Privacy | r | [34] | o | do | +| 28 | Proxy-Authenticate | 401
(NOTE 1)
407
(NOTE 1) | [13], [18] | o
m | do
dm | +| 29 | Record-Route | 2xx | [13], [18] | o | do | +| 30 | Recv-Info | 2xx
others | [39] | c
o | IF table 6.1.3.1/17 THEN dc (NOTE 2)
IF table 6.1.3.1/17 THEN do (NOTE 2) | +| 31 | Relayed-Charge | r | [5] | n/a | dn/a | +| 32 | Require | r | [13], [18] | c | dc | +| 33 | Resource-Share | 2xx | [5] | n/a | IF (home-to-visited response on roaming II-NNI OR visited-to-home response on roaming II-NNI) AND table 6.1.3.1/116 THEN do (NOTE 2) | +| 34 | Response-Source | 3xx-6xx | [5] | n/a | IF table 6.1.3.1/121 THEN do | + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|------|------------------|------------------------------------------------------|------------|------------|-----------------------------------------| +| | | | | | (NOTE 2) | +| 35 | Retry-After | 404
413
480
486
500
503
600
603 | [13], [18] | o | do | +| 36 | Security-Server | 421
494 | [47] | n/a | dn/a | +| 37 | Server | r | [13], [18] | o | do | +| 38 | Session-ID | r | [124] | m | IF table 6.1.3.1/94 THEN dm
(NOTE 2) | +| 39 | Supported | 2xx | [13], [18] | o | do | +| 40 | Timestamp | r | [13], [18] | o | do | +| 41 | To | 100
others | [13], [18] | m | dm | +| 42 | Unsupported | 420 | [13], [18] | m | dm | +| 43 | User-Agent | r | [13], [18] | o | do | +| 44 | Via | 100
others | [13], [18] | m | dm | +| 45 | Warning | r | [13], [18] | o | do | +| 46 | WWW-Authenticate | 401
(NOTE 1) | [13], [18] | m | dm | +| | | 407
(NOTE 1) | | o | do | + +NOTE 1: The SIP status code is only applicable over the roaming II-NNI. + +NOTE 2: If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. + +## --- B.12 PUBLISH method + +As described in table 6.1, the support of PUBLISH method over the non-roaming II-NNI is based on bilateral agreement between the operators. + +The table B.12.1 lists the supported header fields within the PUBLISH request. + +**Table B.12.1: Supported header fields within the PUBLISH request** + +| Item | Header field | Ref. | RFC status | II-NNI condition | +|------|-------------------------------|-------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Accept-Contact | [51] | o | IF dc1 (PNM: clause 12.17) THEN dm ELSE do | +| 2 | Allow | [13], [21] | o | do | +| 3 | Allow-Events | [20] | o | IF table 6.1.3.1/23 THEN do (NOTE) | +| 4 | Authorization | [13], [21] | o | IF table 6.1.3.1/7 THEN do (NOTE) | +| 5 | Call-ID | [13], [21] | m | dm | +| 6 | Call-Info | [13], [21] | o | IF dc2 (CCBS/CCNR/CCNL: clause 12.11/12.12/12.23) THEN dm ELSE do | +| 7 | Cellular-Network-Info | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE) | +| 8 | Contact | [13], [21] | n/a | dn/a | +| 9 | Content-Disposition | [13], [21] | o | do | +| 10 | Content-Encoding | [13], [21] | o | do | +| 11 | Content-ID | [216] | o | IF table 6.1.3.1/122 THEN do | +| 12 | Content-Language | [13], [21] | o | do | +| 13 | Content-Length | [13], [21] | t | dt | +| 14 | Content-Type | [13], [21] | * | d* | +| 15 | CSeq | [13], [21] | m | dm | +| 16 | Date | [13], [21] | o | do | +| 17 | Event | [20] | m | dm | +| 18 | Expires | [13], [21] | o | IF dc2 (CCBS/CCNR/CCNL: clause 12.11/12.12/12.23) THEN dm ELSE do | +| 19 | Feature-Caps | [143] | o | IF table 6.1.3.1/103 AND request outside an existing dialog THEN do | +| 20 | From | [13], [21] | m | dm | +| 21 | Geolocation | [68] | o | do | +| 22 | Geolocation-Routing | [68] | o | do | +| 23 | History-Info | [25] | o | IF dc1 (PNM: clause 12.17) THEN dm ELSE IF table 6.1.3.1/50 AND request outside an existing dialog THEN do (NOTE) | +| 24 | In-Reply-To | [13], [21] | n/a | dn/a | +| 25 | Max-Breadth | [79] | o | do | +| 26 | Max-Forwards | [13], [21] | m | dm | +| 27 | MIME-Version | [13], [21] | o | do | +| 28 | Organization | [13], [21] | o | do | +| 29 | P-Access-Network-Info | [24], [24B] | o | IF table 6.1.3.1/36 THEN do (NOTE) | +| 30 | P-Asserted-Identity | [44] | o | IF dc2 (CCBS/CCNR/CCNL: clause 12.11/12.12/12.23) OR table 6.1.3.1/27 AND request outside an existing dialog THEN dm (NOTE) | +| 31 | P-Asserted-Service | [26] | o | IF (non-roaming II-NNI OR home-to-visited request on roaming II-NNI) AND table 6.1.3.1/77 AND request outside an existing dialog THEN do (NOTE) | +| 32 | P-Called-Party-ID | [24] | o | IF home-to-visited request on roaming II-NNI AND table 6.1.3.1/34 THEN do (NOTE) | +| 33 | P-Charging-Function-Addresses | [24] | o | dn/a | +| 34 | P-Charging-Vector | [24] | o | IF table 6.1.3.1/38 AND request outside an existing dialog THEN dm (NOTE) | +| 35 | P-Preferred-Identity | [44] | o | dn/a | +| 36 | P-Preferred-Service | [26] | o | IF visited-to-home request on roaming II-NNI AND table 6.1.3.1/77 AND request outside an existing dialog THEN do (NOTE) | +| 37 | P-Private-Network-Indication | [84] | o | IF table 6.1.3.1/80 AND request outside an existing dialog THEN do (NOTE) | +| 38 | P-Profile-Key | [64] | o | IF table 6.1.3.1/59 AND request outside an existing dialog THEN do (NOTE) | +| 39 | P-Served-User | [85] | o | IF visited-to-home request on roaming II-NNI AND request outside an existing dialog being sent from "privileged sender" THEN dm (NOTE) | +| 40 | P-User-Database | [60] | o | dn/a | +| 41 | P-Visited-Network-ID | [24] | o | dn/a | +| 42 | Priority | [13], [21] | o | do | +| 43 | Privacy | [34] | o | IF dc3 (OIP/OIR: clause 12.3) THEN dm ELSE do | +| 44 | Proxy-Authorization | [13], [21] | o | IF table 6.1.3.1/7 THEN do (NOTE) | + +| Item | Header field | Ref. | RFC status | II-NNI condition | +|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------|--------------------------------------------------------------------------| +| 45 | Proxy-Require | [13], [21] | o | do | +| 46 | Reason | [48] | o | IF table 6.1.3.1/40 AND request inside an existing dialog THEN do (NOTE) | +| 47 | Referred-By | [53] | o | do | +| 48 | Reject-Contact | [51] | o | do | +| 49 | Relayed-Charge | [5] | n/a | dn/a | +| 50 | Reply-To | [13], [21] | n/a | dn/a | +| 51 | Request-Disposition | [51] | o | do | +| 52 | Require | [13], [21] | o | do | +| 53 | Resource-Priority | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE) | +| 54 | Route | [13], [21] | c | dc | +| 55 | Security-Client | [47] | o | dn/a | +| 56 | Security-Verify | [47] | o | dn/a | +| 57 | Session-ID | [124] | m | IF table 6.1.3.1/94 THEN dm (NOTE) | +| 58 | SIP-If-Match | [21] | o | do | +| 59 | Subject | [13], [21] | o | do | +| 60 | Supported | [13], [21] | o | IF dc1 (PNM: clause 12.17) THEN dm ELSE do | +| 61 | Timestamp | [13], [21] | o | do | +| 62 | To | [13], [21] | m | dm | +| 63 | User-Agent | [13], [21] | o | do | +| 64 | Via | [13], [21] | m | dm | +| dc1: | request outside an existing dialog invoked due to PNM in case of ("PN UE redirection" OR "PN access control") AND (non-roaming II-NNI OR home-to-visited request on roaming II-NNI) | | | | +| dc2: | (request inside an existing dialog invoked due to CCBS/CCNR/CCNL suspending the "CC request" AND (non-roaming II-NNI OR loopback traversal scenario) OR (request inside an existing dialog invoked due to CCBS/CCNR/CCNL resuming the "CC request" AND (non-roaming II-NNI OR loopback traversal scenario))) | | | | +| dc3: | (request outside an existing dialog invoked due to OIP/OIR AND "override the default setting" in temporary mode AND visited-to-home request on roaming II-NNI) OR (request outside an existing dialog invoked due to OIP/OIR AND "presentation of the public user identity is restricted" AND (non-roaming II-NNI OR home-to-visited request on roaming II-NNI)) | | | | +| NOTE: | If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. | | | | + +The table B.12.2 lists the supported header fields within the PUBLISH response. + +###### **Table B.12.2: Supported header fields within the PUBLISH response** + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|------|-------------------------------|-----------------------------|--------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Accept | 415 | [13], [21] | m* | dm* | +| 2 | Accept-Encoding | 415 | [13], [21] | m* | dm* | +| 3 | Accept-Language | 415 | [13], [21] | m* | dm* | +| 4 | Accept-Resource-Priority | 200
417 | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE 2) | +| 5 | Allow | 405
others | [13], [21] | m
o | dm
do | +| 6 | Allow-Events | 489 | [20] | m | dm | +| 7 | Authentication-Info | 2xx | [13], [21] | o | IF table 6.1.3.1/7 THEN do (NOTE 2) | +| 8 | Call-ID | 100
others | [13], [21] | m | dm | +| 9 | Call-Info | r | [13], [21] | o | do | +| 10 | Cellular-Network-Info | r | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE 2) | +| 11 | Contact | 3xx
485 | [13], [21] | o | do | +| 12 | Content-Disposition | r | [13], [21] | o | do | +| 13 | Content-Encoding | r | [13], [21] | o | do | +| 14 | Content-ID | r | [216] | o | IF table 6.1.3.1/122 THEN do | +| 15 | Content-Language | r | [13], [21] | o | do | +| 16 | Content-Length | 100
others | [13], [21] | t | dt | +| 17 | Content-Type | r | [13], [21] | * | d* | +| 18 | CSeq | 100
others | [13], [21] | m | dm | +| 19 | Date | 100
others | [13], [21] | o | do | +| 20 | Error-Info | 3xx-6xx | [13], [21] | o | IF table 6.1.3.1/13 THEN do (NOTE 2) | +| 21 | Expires | 2xx
others | [13], [21] | m
o | dm
do | +| 22 | Feature-Caps | 2xx | [143] | o | IF table 6.1.3.1/103 AND response to request outside an existing dialog THEN do | +| 23 | From | 100
others | [13], [21] | m | dm | +| 24 | Geolocation-Error | 424
others | [68] | m
o | dm
do | +| 25 | History-Info | r | [25] | o | IF table 6.1.3.1/50 AND response to request outside an existing dialog THEN do (NOTE 2) | +| 26 | MIME-version | r | [13], [21] | o | do | +| 27 | Min-Expires | 423 | [13], [21] | m | dm | +| 28 | Organization | r | [13], [21] | o | do | +| 29 | P-Access-Network-Info | r | [24], [24A], [24B] | o | IF table 6.1.3.1/36 THEN do (NOTE 2) | +| 30 | P-Asserted-Identity | r | [44] | o | IF dc1 (TIP/TIR: clause 12.4) THEN dm ELSE IF table 6.1.3.1/27 AND response to request outside an existing dialog THEN do (NOTE 2) | +| 31 | P-Charging-Function-Addresses | r | [24], [24A], [24B] | o | dn/a | +| 32 | P-Charging-Vector | 100
18xx, 2xx
3xx-6xx | [24], [24A] | o
o
o | dn/a
IF table 6.1.3.1/38 AND response to request outside an existing dialog THEN dm (NOTE 2)
do (NOTE 2) | +| 33 | P-Preferred-Identity | r | [44] | o | dn/a | +| 34 | Privacy | r | [34] | o | IF dc2 (TIP/TIR: clause 12.4) THEN dm ELSE do | +| 35 | Proxy-Authenticate | 401 | [13], [21] | o | do | + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | | +|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|------------|------------|--------------------------------------------------------------------------------------|--| +| | | (NOTE 1) | | | | | +| | | 407
(NOTE 1) | | m | dm | | +| 36 | Relayed-Charge | r | [5] | n/a | dn/a | | +| 37 | Require | r | [13], [21] | o | do | | +| 38 | Response-Source | 3xx-6xx | [5] | n/a | IF table 6.1.3.1/121 THEN do
(NOTE 2) | | +| 39 | Restoration-Info | 504 | [5] | n/a | IF table 6.1.3.1/114 AND visited-to-home response on roaming II-NNI THEN do (NOTE 2) | | +| 40 | Retry-After | 404
413
480
486
500
503
600
603 | [13], [21] | o | do | | +| 41 | Security-Server | 421
494 | [47] | o | dn/a | | +| 42 | Server | r | [13], [21] | o | do | | +| 43 | Session-ID | r | [124] | m | IF table 6.1.3.1/94 THEN dm
(NOTE 2) | | +| 44 | SIP-Etag | 2xx | [21] | m | dm | | +| 45 | Supported | 2xx | [13], [21] | o | do | | +| 46 | Timestamp | r | [13], [21] | o | do | | +| 47 | To | 100
others | [13], [21] | m | dm | | +| 48 | Unsupported | 420 | [13], [21] | o | do | | +| 49 | User-Agent | r | [13], [21] | o | do | | +| 50 | Via | 100
others | [13], [21] | m | dm | | +| 51 | Warning | r | [13], [21] | o | do | | +| 52 | WWW-Authenticate | 401
(NOTE 1) | [13], [21] | m | dm | | +| | | 407
(NOTE 1) | | o | do | | +| dc1: | (TIP/TIR AND 2xx response to request outside an existing dialog AND (visited-to-home response on roaming II-NNI OR non-roaming II-NNI)) OR (TIP/TIR AND response to request outside an existing dialog AND "presentation is allowed" AND home-to-visited response on roaming II-NNI) | | | | | | +| dc2: | (TIP/TIR AND non-100 response to request outside an existing dialog AND "override the default setting" in temporary mode AND visited-to-home response on roaming II-NNI) OR (TIP/TIR AND 2xx response to request outside an existing dialog AND "presentation of the network asserted identity is restricted" AND (non-roaming II-NNI OR home-to-visited response on roaming II-NNI)) | | | | | | +| NOTE 1: | The SIP status code is only applicable over the roaming II-NNI. | | | | | | +| NOTE 2: | If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. | | | | | | + +## --- B.13 REFER method + +As described in table 6.1, the support of REFER method over the II-NNI is based on bilateral agreement between the operators. + +The table B.13.1 lists the supported header fields within the REFER request. + +**Table B.13.1: Supported header fields within the REFER request** + +| Item | Header field | Ref. | RFC status | II-NNI condition | +|------|-------------------------------|-------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Accept | [13], [22] | o | do | +| 2 | Accept-Contact | [51] | o | IF dc1 (PNM: clause 12.17) THEN dm ELSE do | +| 3 | Accept-Encoding | [13], [22] | o | do | +| 4 | Accept-Language | [13], [22] | o | do | +| 5 | Additional-Identity | [5] | n/a | IF table 6.1.3.1/126 THEN do (NOTE) | +| 6 | Allow | [13], [22] | o | do | +| 7 | Allow-Events | [20] | o | IF table 6.1.3.1/23 THEN do (NOTE) | +| 8 | Authorization | [13], [22] | o | IF table 6.1.3.1/7 THEN do (NOTE) | +| 9 | Call-ID | [13], [22] | m | dm | +| 10 | Cellular-Network-Info | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE) | +| 11 | Contact | [13], [22] | m | dm | +| 12 | Content-Disposition | [13], [22] | o | do | +| 13 | Content-Encoding | [13], [22] | o | do | +| 14 | Content-ID | [216] | o | IF table 6.1.3.1/122 THEN do | +| 15 | Content-Language | [13], [22] | o | do | +| 16 | Content-Length | [13], [22] | o | do | +| 17 | Content-Type | [13], [22] | * | d* | +| 18 | CSeq | [13], [22] | m | dm | +| 19 | Date | [13], [22] | o | do | +| 20 | Expires | [13], [22] | o | do | +| 21 | Feature-Caps | [143] | o | IF table 6.1.3.1/103 AND request outside an existing dialog THEN do (NOTE) | +| 22 | From | [13], [22] | m | dm | +| 23 | Geolocation | [68] | o | do | +| 24 | Geolocation-Routing | [68] | o | do | +| 25 | History-Info | [25] | o | IF dc1 (PNM: clause 12.17) THEN dm ELSE IF table 6.1.3.1/50 AND request outside an existing dialog THEN do (NOTE) | +| 26 | Max-Breadth | [79] | o | do | +| 27 | Max-Forwards | [13], [22] | m | dm | +| 28 | MIME-Version | [13], [22] | o | do | +| 29 | Organization | [13], [22] | o | do | +| 30 | P-Access-Network-Info | [24], [24B] | o | IF table 6.1.3.1/36 THEN do (NOTE) | +| 31 | P-Asserted-Identity | [44] | o | IF table 6.1.3.1/27 AND request outside an existing dialog THEN dm (NOTE) | +| 32 | P-Asserted-Service | [26] | o | IF (non-roaming II-NNI OR home-to-visited request on roaming II-NNI) AND table 6.1.3.1/77 AND request outside an existing dialog THEN do (NOTE) | +| 33 | P-Called-Party-ID | [24], [24A] | o | IF home-to-visited request on roaming II-NNI AND table 6.1.3.1/34 THEN do (NOTE) | +| 34 | P-Charging-Function-Addresses | [24] | o | dn/a | +| 35 | P-Charging-Vector | [24] | o | IF table 6.1.3.1/38 AND request outside an existing dialog THEN dm (NOTE) | +| 36 | P-Preferred-Identity | [44] | o | dn/a | +| 37 | P-Preferred-Service | [26] | o | IF visited-to-home request on roaming II-NNI AND table 6.1.3.1/77 AND request outside an existing dialog THEN do (NOTE) | +| 38 | P-Private-Network-Indication | [84] | o | IF table 6.1.3.1/80 AND request outside an existing dialog THEN do (NOTE) | +| 39 | P-Profile-Key | [64] | o | IF table 6.1.3.1/59 AND request outside an existing dialog THEN do (NOTE) | +| 40 | P-Served-User | [85] | o | IF visited-to-home request on roaming II-NNI AND request outside an existing dialog being sent from "privileged sender" THEN dm (NOTE) | +| 41 | P-User-Database | [60] | o | dn/a | +| 42 | P-Visited-Network-ID | [24] | o | dn/a | +| 43 | Privacy | [34] | o | IF dc2 (OIP/OIR: clause 12.3) OR dc3 (ECT: clause 12.13) THEN dm ELSE do | +| 44 | Proxy-Authorization | [13], [22] | o | IF table 6.1.3.1/7 THEN do (NOTE) | +| 45 | Proxy-Require | [13], [22] | o | do | +| 46 | Reason | [48] | o | IF table 6.1.3.1/40 AND request inside an existing dialog THEN do (NOTE) | +| 47 | Record-Route | [13], [22] | o | do | + +| Item | Header field | Ref. | RFC status | II-NNI condition | +|-------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------|--------------------------------------------| +| 48 | Refer-Sub | [135] | o | do | +| 49 | Refer-To | [22] | dm | dm | +| 50 | Referred-By | [53] | o | IF dc4 (ECT: clause 12.13) THEN dm ELSE do | +| 51 | Reject-Contact | [51] | o | do | +| 52 | Relayed-Charge | [5] | n/a | dn/a | +| 53 | Request-Disposition | [51] | o | do | +| 54 | Require | [13], [22] | c | dc | +| 55 | Resource-Priority | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE) | +| 56 | Route | [13], [22] | c | dc | +| 57 | Security-Client | [47] | o | dn/a | +| 58 | Security-Verify | [47] | o | dn/a | +| 59 | Session-ID | [124] | m | IF table 6.1.3.1/94 THEN dm (NOTE) | +| 60 | Supported | [13], [22] | o | IF dc1 (PNM: clause 12.17) THEN dm ELSE do | +| 61 | Target-Dialog | [140] | o | IF table 6.1.3.1/102 THEN do (NOTE) | +| 62 | Timestamp | [13], [22] | o | do | +| 63 | To | [13], [22] | m | dm | +| 64 | Trigger-Consent | [82] | o | IF table 6.1.3.1/78 THEN do (NOTE) | +| 65 | User-Agent | [13], [22] | o | do | +| 66 | Via | [13], [22] | m | dm | +| dc1: | request outside an existing dialog invoked due to PNM in case of ("PN UE redirection" OR "PN access control") AND (non-roaming II-NNI OR home-to-visited request on roaming II-NNI) | | | | +| dc2: | (request outside an existing dialog invoked due to OIP/OIR AND "override the default setting" in temporary mode AND visited-to-home request on roaming II-NNI) OR (request outside an existing dialog invoked due to OIP/OIR AND "presentation of the public user identity is restricted" AND (non-roaming II-NNI OR home-to-visited request on roaming II-NNI)) | | | | +| dc3: | request inside an existing dialog invoked due to ECT including Referred-By header field with privacy requested in the "original communication" | | | | +| dc4: | request inside an existing dialog invoked due to ECT AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited request on roaming II-NNI) | | | | +| NOTE: | If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. | | | | + +The table B.13.2 lists the supported header fields within the REFER response. + +###### **Table B.13.2: Supported header fields within the REFER response** + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|------|-------------------------------|----------------------------|--------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Accept | 415 | [13], [22] | c | dc | +| 2 | Accept-Encoding | 415 | [13], [22] | c | dc | +| 3 | Accept-Language | 415 | [13], [22] | c | dc | +| 4 | Accept-Resource-Priority | 2xx
417 | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE 2) | +| 5 | Allow | 405
others | [13], [22] | m
o | dm
do | +| 6 | Allow-Events | 2xx | [20] | o | IF table 6.1.3.1/23 THEN do (NOTE 2) | +| 7 | Authentication-Info | 2xx | [13], [22] | o | IF table 6.1.3.1/7 THEN do (NOTE 2) | +| 8 | Call-ID | 100
others | [13], [22] | m | dm | +| 9 | Cellular-Network-Info | r | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE 2) | +| 10 | Contact | 2xx
3xx-6xx | [13], [22] | m
o | dm
do | +| 11 | Content-Disposition | r | [13], [22] | o | do | +| 12 | Content-Encoding | r | [13], [22] | o | do | +| 13 | Content-ID | r | [216] | o | IF table 6.1.3.1/122 THEN do | +| 14 | Content-Language | r | [13], [22] | o | do | +| 15 | Content-Length | 100
others | [13], [22] | t | dt | +| 16 | Content-Type | r | [13], [22] | * | d* | +| 17 | CSeq | 100
others | [13], [22] | m | dm | +| 18 | Date | 100
others | [13], [22] | o | do | +| 19 | Error-Info | 3xx-6xx | [13], [22] | o | IF table 6.1.3.1/13 THEN do (NOTE 2) | +| 20 | Feature-Caps | 2xx | [143] | o | IF table 6.1.3.1/103 AND response to request outside an existing dialog THEN do (NOTE 2) | +| 21 | From | 100
others | [13], [22] | m | dm | +| 22 | Geolocation-Error | 424
others | [68] | m
o | dm
do | +| 23 | History-Info | r | [25] | o | IF table 6.1.3.1/50 AND response to request outside an existing dialog THEN do (NOTE 2) | +| 24 | MIME-version | r | [13], [22] | o | do | +| 25 | Organization | r | [13], [22] | o | do | +| 26 | P-Access-Network-Info | r | [24], [24A], [24B] | o | IF table 6.1.3.1/36 THEN do (NOTE 2) | +| 27 | P-Asserted-Identity | r | [44] | o | IF dc1 (TIP/TIR: clause 12.4) THEN dm ELSE IF table 6.1.3.1/27 AND response to request outside an existing dialog THEN do (NOTE 2) | +| 28 | P-Charging-Function-Addresses | r | [24], [24A] | o | dn/a | +| 29 | P-Charging-Vector | 100
18x, 2xx
3xx-6xx | [24], [24A] | o
o
o | dn/a
IF dc2 (CONF: clause 12.19) OR (table 6.1.3.1/38 AND response to request outside an existing dialog) THEN dm (NOTE 2)
do (NOTE 2) | +| 30 | P-Preferred-Identity | r | [44] | o | dn/a | +| 31 | Permission-Missing | 470 | [82] | o | IF table 6.1.3.1/78 THEN do (NOTE 2) | +| 32 | Privacy | r | [34] | o | IF dc3 (TIP/TIR: clause 12.4) THEN dm ELSE do | +| 33 | Proxy-Authenticate | 401
(NOTE 1)
407 | [13], [22] | o
m | do
dm | + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|------------|------------|--------------------------------------------------------------------------------------|--|--|--|--|--| +| | | (NOTE 1) | | | | | | | | | +| 34 | Record-Route | 2xx | [13], [22] | o | do | | | | | | +| 35 | Refer-Sub | 2xx | [135] | o | IF table 6.1.3.1/98 THEN do (NOTE 2) | | | | | | +| 36 | Relayed-Charge | r | [5] | n/a | dn/a | | | | | | +| 37 | Require | r | [13], [22] | c | dc | | | | | | +| 38 | Response-Source | 3xx-6xx | [5] | n/a | IF table 6.1.3.1/121 THEN do (NOTE 2) | | | | | | +| 39 | Restoration-Info | 504 | [5] | n/a | IF table 6.1.3.1/114 AND visited-to-home response on roaming II-NNI THEN do (NOTE 2) | | | | | | +| 40 | Retry-After | 404
413
480
486
500
503
600
603 | [13], [22] | o | do | | | | | | +| 41 | Security-Server | 421
494 | [47] | o | dn/a | | | | | | +| 42 | Server | r | [13], [22] | o | do | | | | | | +| 43 | Session-ID | r | [124] | m | IF table 6.1.3.1/94 THEN dm (NOTE 2) | | | | | | +| 44 | Supported | 2xx | [13], [22] | o | do | | | | | | +| 45 | Timestamp | r | [13], [22] | o | do | | | | | | +| 46 | To | 100
others | [13], [22] | m | dm | | | | | | +| 47 | Unsupported | 420 | [13], [22] | o | do | | | | | | +| 48 | User-Agent | r | [13], [22] | o | do | | | | | | +| 49 | Via | 100
others | [13], [22] | m | dm | | | | | | +| 50 | Warning | r | [13], [22] | o | do | | | | | | +| 51 | WWW-Authenticate | 401
(NOTE 1) | [13], [22] | m | dm | | | | | | +| | | 407
(NOTE 1) | | o | do | | | | | | +| dc1: | (TIP/TIR AND 2xx response to request outside an existing dialog AND (visited-to-home response on roaming II-NNI OR non-roaming II-NNI)) OR (TIP/TIR AND response to request outside an existing dialog AND "presentation is allowed" AND home-to-visited response on roaming II-NNI) | | | | | | | | | | +| dc2: | first response from "conference focus" to request outside an existing dialog AND (non-roaming II-NNI OR home-to-visited response on roaming II-NNI) | | | | | | | | | | +| dc3: | (TIP/TIR AND non-100 response to request outside an existing dialog AND "override the default setting" in temporary mode AND visited-to-home response on roaming II-NNI) OR (TIP/TIR AND 2xx response to request outside an existing dialog AND "presentation of the network asserted identity is restricted" AND (non-roaming II-NNI OR home-to-visited response on roaming II-NNI)) | | | | | | | | | | +| NOTE 1: The SIP status code is only applicable over the roaming II-NNI. | | | | | | | | | | | +| NOTE 2: If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. | | | | | | | | | | | + +## --- B.14 REGISTER method + +As described in table 6.1, the REGISTER method is supported only over the roaming II-NNI. + +The table B.14.1 lists the supported header fields within the REGISTER request. + +**Table B.14.1: Supported header fields within the REGISTER request** + +| Item | Header field | Ref. | RFC status | II-NNI condition | +|------|-------------------------------|-------------|------------|-----------------------------------------------------------------------------------| +| 1 | Accept | [13] | o | do | +| 2 | Accept-Encoding | [13] | o | do | +| 3 | Accept-Language | [13] | o | do | +| 4 | Allow | [13] | o | do | +| 5 | Allow-Events | [20] | o | IF table 6.1.3.1/23 THEN do (NOTE) | +| 6 | Authorization | [13] | o | IF using IMS AKA OR using SIP digest THEN dm ELSE do | +| 7 | Call-ID | [13] | m | dm | +| 8 | Call-Info | [13] | o | do | +| 9 | Cellular-Network-Info | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE) | +| 10 | Contact | [13] | o | dm | +| 11 | Content-Disposition | [13] | o | do | +| 12 | Content-Encoding | [13] | o | do | +| 13 | Content-ID | [216] | o | IF table 6.1.3.1/122 THEN do | +| 14 | Content-Language | [13] | o | do | +| 15 | Content-Length | [13] | t | dt | +| 16 | Content-Type | [13] | * | d* | +| 17 | CSeq | [13] | m | dm | +| 18 | Date | [13] | o | do | +| 19 | Expires | [13] | o | do | +| 20 | Feature-Caps | [143] | o | IF table 6.1.3.1/103 THEN do (NOTE) | +| 21 | From | [13] | m | dm | +| 22 | Geolocation | [68] | o | do | +| 23 | Geolocation-Routing | [68] | o | do | +| 24 | History-Info | [25] | o | IF table 6.1.3.1/50 AND request outside an existing dialog THEN do (NOTE) | +| 25 | Max-Breadth | [79] | o | do | +| 26 | Max-Forwards | [13] | m | dm | +| 27 | MIME-Version | [13] | o | do | +| 28 | Organization | [13] | o | do | +| 29 | P-Access-Network-Info | [24] | o | IF table 6.1.3.1/36 THEN do (NOTE) | +| 30 | P-Charging-Function-Addresses | [24], [24B] | o | dn/a | +| 31 | P-Charging-Vector | [24] | o | dm | +| 32 | P-User-Database | [60] | o | dn/a | +| 33 | P-Visited-Network-ID | [24] | o | dm | +| 34 | Path | [43] | o | dm | +| 35 | Privacy | [34] | o | dn/a | +| 36 | Proxy-Authorization | [13] | o | do | +| 37 | Proxy-Require | [13] | o | do | +| 38 | Reason | [48] | o | IF table 6.1.3.1/40 THEN do (NOTE) | +| 39 | Recv-Info | [39] | o | IF table 6.1.3.1/17 THEN do (NOTE) | +| 40 | Referred-By | [53] | o | do | +| 41 | Relayed-Charge | [5] | n/a | dn/a | +| 42 | Request-Disposition | [51] | o | do | +| 43 | Require | [13] | c | dm | +| 44 | Resource-Priority | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE) | +| 45 | Resource-Share | [5] | n/a | IF visited-to-home request on roaming II-NNI AND table 6.1.3.1/116 THEN do (NOTE) | +| 46 | Route | [13] | c | dn/a | +| 47 | Security-Client | [47] | o | dn/a | +| 48 | Security-Verify | [47] | o | dn/a | +| 49 | Session-ID | [124] | m | IF table 6.1.3.1/94 THEN dm (NOTE) | +| 50 | Supported | [13] | o | dm | +| 51 | Timestamp | [13] | o | do | +| 52 | To | [13] | m | dm | +| 53 | User-Agent | [13] | o | do | +| 54 | Via | [13] | m | dm | + +NOTE: If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. + +The table B.14.2 lists the supported header fields within the REGISTER response. + +**Table B.14.2: Supported header fields within the REGISTER response** + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|------|-------------------------------|-----------------|----------------------|------------|---------------------------------------------------------------------------------------| +| 1 | Accept | 2xx | [13] | o | do | +| | | 415 | | c | dc | +| 2 | Accept-Encoding | 2xx | [13] | o | do | +| | | 415 | | c | dc | +| 3 | Accept-Language | 2xx | [13] | o | do | +| | | 415 | | c | dc | +| 4 | Accept-Resource-Priority | 2xx
417 | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE) | +| 5 | Allow | 405 | [13] | m | dm | +| | | others | | o | do | +| 6 | Allow-Events | 2xx | [20] | o | IF table 6.1.3.1/23 THEN do (NOTE) | +| 7 | Authentication-Info | 2xx | [13] | o | do | +| 8 | Call-ID | 100 | [13] | m | dm | +| | | others | | | | +| 9 | Call-Info | r | [13] | o | do | +| 10 | Contact | 2xx | [13] | o | dm | +| | | 3xx | | o | do | +| | | 485 | | | | +| 11 | Content-Disposition | r | [13] | o | do | +| 12 | Content-Encoding | r | [13] | o | do | +| 13 | Content-ID | r | [216] | o | IF table 6.1.3.1/122 THEN do | +| 14 | Content-Language | r | [13] | o | do | +| 15 | Content-Length | 100 | [13] | t | dt | +| | | others | | | | +| 16 | Content-Type | r | [13] | * | d* | +| 17 | CSeq | 100 | [13] | m | dm | +| | | others | | | | +| 18 | Date | 100 | [13] | o | do | +| | | others | | | | +| 19 | Error-Info | 3xx-6xx | [13] | o | IF table 6.1.3.1/13 THEN do (NOTE) | +| 20 | Feature-Caps | 2xx | [143] | o | IF table 6.1.3.1/103 THEN do (NOTE) | +| 21 | Flow-Timer | 2xx | [65] | o | do | +| 22 | From | 100 | [13] | m | dm | +| | | others | | | | +| 23 | Geolocation-Error | 424 | [68] | m | dm | +| | | others | | o | do | +| 24 | History-Info | r | [25] | o | IF table 6.1.3.1/50 AND response to request outside an existing dialog THEN do (NOTE) | +| 25 | MIME-version | r | [13] | o | do | +| 26 | Min-Expires | 423 | [13] | m | dm | +| 27 | Organization | r | [13] | o | do | +| 28 | P-Access-Network-Info | r | [24], [2 4A], [2 4B] | o | IF table 6.1.3.1/36 THEN do (NOTE) | +| 29 | P-Associated-URI | 2xx | [24] | o | dm | +| 30 | P-Charging-Function-Addresses | r | [24], [2 4A] | o | dn/a | +| 31 | P-Charging-Vector | 100 | [24], [24A] | o | dn/a | +| | | 18x, 2xx | | o | dm | +| | | 3xx-6xx | | o | do | +| 32 | Path | 2xx | [43] | o | dm | +| 33 | Privacy | r | [34] | o | do | +| 34 | Proxy-Authenticate | 401 | [13] | o | do | + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|-------|------------|-------------------------------------| +| | | 407 | | m | dm | +| 35 | Relayed-Charge | r | [5] | n/a | dn/a | +| 36 | Require | r | [13] | c | dc | +| 37 | Response-Source | 3xx-6xx | [5] | n/a | IF table 6.1.3.1/121 THEN do (NOTE) | +| 38 | Retry-After | 404
413
480
486
500
503
600
603 | [13] | o | do | +| 39 | Security-Server | 2xx
401 | [47] | n/a | dn/a | +| | | 421
494 | | o | dn/a | +| 40 | Server | r | [13] | o | do | +| 41 | Service-Route | 2xx | [45] | o | dm | +| 42 | Session-ID | r | [124] | m | IF table 6.1.3.1/94 THEN dm (NOTE) | +| 43 | Supported | 2xx | [13] | o | do | +| 44 | Timestamp | r | [13] | o | do | +| 45 | To | 100
others | [13] | m | dm | +| 46 | Unsupported | 420 | [13] | m | dm | +| 47 | User-Agent | r | [13] | o | do | +| 48 | Via | 100
others | [13] | m | dm | +| 49 | Warning | r | [13] | o | do | +| 50 | WWW-Authenticate | 401 | [13] | m | dm | +| | | 407 | | o | do | +| NOTE: | If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. | | | | | + +## --- B.15 SUBSCRIBE method + +As described in table 6.1, the support of SUBSCRIBE method over the non-roaming II-NNI is based on bilateral agreement between the operators. + +The table B.15.1 lists the supported header fields within the SUBSCRIBE request. + +**Table B.15.1: Supported header fields within the SUBSCRIBE request** + +| Item | Header field | Ref. | RFC status | II-NNI condition | +|------|-------------------------------|-------------|------------|------------------------------------------------------------------------------------------------------------------------------| +| 1 | Accept | [13], [20] | o | do | +| 2 | Accept-Contact | [51] | o | IF dc1 (PNM: clause 12.17) THEN dm ELSE do | +| 3 | Accept-Encoding | [13], [20] | o | do | +| 4 | Accept-Language | [13], [20] | o | do | +| 5 | Allow | [13], [20] | o | do | +| 6 | Allow-Events | [20] | o | do | +| 7 | Authorization | [13], [20] | o | IF table 6.1.3.1/7 THEN do (NOTE) | +| 8 | Call-ID | [13], [20] | m | dm | +| 9 | Call-Info | [13], [20] | o | IF dc2 (CCBS/CCNR/CCNL: clause 12.11/12.12/12.23) THEN dm ELSE dn/a | +| 10 | Cellular-Network-Info | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE) | +| 11 | Contact | [13], [20] | m | dm | +| 12 | Content-Disposition | [13], [20] | o | do | +| 13 | Content-Encoding | [13], [20] | o | do | +| 14 | Content-ID | [216] | o | IF table 6.1.3.1/122 THEN do | +| 15 | Content-Language | [13], [20] | o | do | +| 16 | Content-Length | [13], [20] | t | dt | +| 17 | Content-Type | [13], [20] | * | d* | +| 18 | CSeq | [13], [20] | m | dm | +| 19 | Date | [13], [20] | o | do | +| 20 | Event | [20] | m | dm | +| 21 | Expires | [13], [20] | o | IF dc2 (CCBS/CCNR/CCNL: clause 12.11/12.12/12.23) OR using reg event package THEN dm ELSE do | +| 22 | Feature-Caps | [143] | o | IF table 6.1.3.1/103 THEN do (NOTE) | +| 23 | From | [13], [20] | m | dm | +| 24 | Geolocation | [68] | o | do | +| 25 | Geolocation-Routing | [68] | o | do | +| 26 | History-Info | [25] | o | IF dc1 (PNM: clause 12.17) THEN dm ELSE IF table 6.1.3.1/50 AND initial request THEN do (NOTE) | +| 27 | Max-Breadth | [79] | o | dn/a | +| 28 | Max-Forwards | [13], [20] | m | dm | +| 29 | MIME-Version | [13], [20] | o | do | +| 30 | Organization | [13], [20] | o | do | +| 31 | P-Access-Network-Info | [24], [24B] | o | IF table 6.1.3.1/36 THEN do (NOTE) | +| 32 | P-Asserted-Identity | [44] | o | IF dc2 (CCBS/CCNR/CCNL: clause 12.11/12.12/12.23) OR table 6.1.3.1/27 AND initial request THEN dm (NOTE) | +| 33 | P-Asserted-Service | [26] | o | IF (non-roaming II-NNI OR home-to-visited request on roaming II-NNI) AND table 6.1.3.1/77 AND initial request THEN do (NOTE) | +| 34 | P-Called-Party-ID | [24] | o | IF home-to-visited request on roaming II-NNI AND table 6.1.3.1/34 THEN do (NOTE) | +| 35 | P-Charging-Function-Addresses | [24] | o | dn/a | +| 36 | P-Charging-Vector | [24] | o | IF table 6.1.3.1/38 AND initial request THEN dm (NOTE) | +| 37 | P-Preferred-Identity | [44] | o | dn/a | +| 38 | P-Preferred-Service | [26] | o | IF visited-to-home request on roaming II-NNI AND table 6.1.3.1/77 AND initial request THEN do (NOTE) | +| 39 | P-Private-Network-Indication | [84] | o | IF table 6.1.3.1/80 AND initial request THEN do (NOTE) | +| 40 | P-Profile-Key | [64] | o | IF table 6.1.3.1/59 AND initial request THEN do (NOTE) | +| 41 | P-Served-User | [85] | o | IF visited-to-home request on roaming II-NNI AND initial request being sent from "privileged sender" THEN dm (NOTE) | +| 42 | P-User-Database | [60] | o | dn/a | +| 43 | P-Visited-Network-ID | [24] | o | dn/a | +| 44 | Priority | [13], [20] | o | do | +| 45 | Privacy | [34] | o | IF dc3 (OIP/OIR: clause 12.3) THEN dm ELSE | + +| Item | Header field | Ref. | RFC status | II-NNI condition | +|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------|-----------------------------------------------------------| +| | | | | do | +| 46 | Proxy-Authorization | [13], [20] | o | IF table 6.1.3.1/7 THEN do (NOTE) | +| 47 | Proxy-Require | [13], [20] | o | do | +| 48 | Reason | [48] | o | IF table 6.1.3.1/40 AND subsequent request THEN do (NOTE) | +| 49 | Record-Route | [13], [20] | o | do | +| 50 | Referred-By | [53] | o | do | +| 51 | Reject-Contact | [51] | o | do | +| 52 | Relayed-Charge | [5] | n/a | dn/a | +| 53 | Request-Disposition | [51] | o | do | +| 54 | Require | [13], [20] | o | do | +| 55 | Resource-Priority | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE) | +| 56 | Route | [13], [20] | c | dc | +| 57 | Security-Client | [47] | o | dn/a | +| 58 | Security-Verify | [47] | o | dn/a | +| 59 | Session-ID | [124] | m | IF table 6.1.3.1/94 THEN dm (NOTE) | +| 60 | Supported | [13], [20] | o | IF dc1 (PNM: clause 12.17) THEN dm ELSE do | +| 61 | Target-Dialog | [140] | o | IF table 6.1.3.1/102 THEN do (NOTE) | +| 62 | Timestamp | [13], [20] | o | do | +| 63 | To | [13], [20] | m | dm | +| 64 | Trigger-Consent | [82] | o | IF table 6.1.3.1/78 THEN do (NOTE) | +| 65 | User-Agent | [13], [20] | o | do | +| 66 | Via | [13], [20] | m | dm | +| dc1: | initial request invoked due to PNM in case of ("PN UE redirection" OR "PN access control") AND (non-roaming II-NNI OR home-to-visited request on roaming II-NNI) | | | | +| dc2: | ("CC invocation request" due to CCBS/CCNR/CCNL AND non-roaming II-NNI) OR ("CC revocation request" due to CCBS/CCNR/CCNL AND non-roaming II-NNI) | | | | +| dc3: | (initial request invoked due to OIP/OIR AND "override the default setting" in temporary mode AND visited-to-home request on roaming II-NNI) OR (initial request invoked due to OIP/OIR AND "presentation of the public user identity is restricted" AND (non-roaming II-NNI OR home-to-visited request on roaming II-NNI)) | | | | +| NOTE: | If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. | | | | + +The table B.15.2 lists the supported header fields within the SUBSCRIBE response. + +###### **Table B.15.2: Supported header fields within the SUBSCRIBE response** + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|------|-------------------------------|----------------------------|---------------------|-------------|-----------------------------------------------------------------------------------------------------------------| +| 1 | Accept | 415 | [13], [20] | o | do | +| 2 | Accept-Encoding | 415 | [13], [20] | o | do | +| 3 | Accept-Language | 415 | [13], [20] | o | do | +| 4 | Accept-Resource-Priority | 2xx
417 | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE 2) | +| 5 | Allow | 405
others | [13], [20] | m
o | dm
do | +| 6 | Allow-Events | 2xx
489 | [20] | o
m | do
dm | +| 7 | Authentication-Info | 2xx | [13], [20] | o | IF table 6.1.3.1/7 THEN do (NOTE 2) | +| 8 | Call-ID | 100
r | [13], [20] | m | dm | +| 9 | Call-Info | r | [13], [20] | o | do | +| 10 | Cellular-Network-Info | r | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE 2) | +| 11 | Contact | 2xx
3xx
485 | [13], [20] | m
o | dm
do | +| 12 | Content-Disposition | r | [13], [20] | o | do | +| 13 | Content-Encoding | r | [13], [20] | o | do | +| 14 | Content-ID | r | [216] | o | IF table 6.1.3.1/122 THEN do | +| 15 | Content-Language | r | [13], [20] | o | do | +| 16 | Content-Length | 100
others | [13], [20] | t | dt | +| 17 | Content-Type | r | [13], [20] | * | d* | +| 18 | CSeq | 100
others | [13], [20] | m | dm | +| 19 | Date | 100
others | [13], [20] | o | do | +| 20 | Error-Info | 3xx-6xx | [13], [20] | o | IF table 6.1.3.1/13 THEN do (NOTE 2) | +| 21 | Expires | 2xx | [13], [20] | m | dm | +| 22 | Feature-Caps | 2xx | [143] | o | IF table 6.1.3.1/103 THEN do (NOTE 2) | +| 23 | From | 100
others | [13], [20] | m | dm | +| 24 | Geolocation-Error | 424
others | [68] | m
o | dm
do | +| 25 | History-Info | r | [25] | o | IF table 6.1.3.1/50 AND response to initial request THEN do (NOTE 2) | +| 26 | MIME-version | r | [13], [20] | o | do | +| 27 | Min-Expires | 423 | [13], [20] | m | dm | +| 28 | Organization | r | [13], [20] | o | do | +| 29 | P-Access-Network-Info | r | [24], [24A ], [24B] | o | IF table 6.1.3.1/36 THEN do (NOTE 2) | +| 30 | P-Asserted-Identity | r | [44] | o | IF dc1 (TIP/TIR: clause 12.4) THEN dm ELSE IF table 6.1.3.1/27 AND response to initial request THEN do (NOTE 2) | +| 31 | P-Charging-Function-Addresses | r | [24], [24A ] | o | dn/a | +| 32 | P-Charging-Vector | 100
18x, 2xx
3xx-6xx | [24], [24A] | o
o
o | dn/a
IF table 6.1.3.1/38 AND response to initial request THEN dm (NOTE 2)
do | +| 33 | P-Preferred-Identity | r | [44] | o | dn/a | +| 34 | Permission-Missing | 470 | [82] | o | IF table 6.1.3.1/78 THEN do (NOTE 2) | +| 35 | Privacy | r | [34] | o | IF dc2 (TIP/TIR: clause 12.4) THEN dm ELSE do | +| 36 | Proxy-Authenticate | 401 (NOTE 1) | [13], [20] | o | do | + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | | | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|------------|------------|--------------------------------------------------------------------------------------|--|--|--|--|--|--| +| | | 407
(NOTE 1) | | m | dm | | | | | | | +| 37 | Record-Route | 2xx | [13], [20] | o | do | | | | | | | +| 38 | Relayed-Charge | r | [5] | n/a | dn/a | | | | | | | +| 39 | Require | r | [13], [20] | o | do | | | | | | | +| 40 | Response-Source | 3xx-6xx | [5] | n/a | IF table 6.1.3.1/121 THEN do
(NOTE 2) | | | | | | | +| 41 | Restoration-Info | 504 | [5] | n/a | IF table 6.1.3.1/114 AND visited-to-home response on roaming II-NNI THEN do (NOTE 2) | | | | | | | +| 42 | Retry-After | 404
413
480
486
500
503
600
603 | [13], [20] | o | do | | | | | | | +| 43 | Security-Server | 421
494 | [47] | o | dn/a | | | | | | | +| 44 | Server | r | [13], [20] | o | do | | | | | | | +| 45 | Session-ID | r | [124] | m | IF table 6.1.3.1/94 THEN dm
(NOTE 2) | | | | | | | +| 46 | Supported | 2xx | [13], [20] | o | do | | | | | | | +| 47 | Timestamp | r | [13], [20] | o | do | | | | | | | +| 48 | To | 100
others | [13], [20] | m | dm | | | | | | | +| 49 | Unsupported | 420 | [13], [20] | o | do | | | | | | | +| 50 | User-Agent | r | [13], [20] | o | do | | | | | | | +| 51 | Via | 100
others | [13], [20] | m | dm | | | | | | | +| 52 | Warning | r | [13], [20] | o | do | | | | | | | +| 53 | WWW-Authenticate | 401
(NOTE 1) | [13], [20] | m | dm | | | | | | | +| | | 407
(NOTE 1) | | o | do | | | | | | | +| dc1: | (TIP/TIR AND 2xx response to initial request AND (visited-to-home response on roaming II-NNI OR non-roaming II-NNI)) OR (TIP/TIR AND response to initial request AND "presentation is allowed" AND home-to-visited response on roaming II-NNI) | | | | | | | | | | | +| dc2: | (TIP/TIR AND non-100 response to initial request AND "override the default setting" in temporary mode AND visited-to-home response on roaming II-NNI) OR (TIP/TIR AND 2xx response to initial request AND "presentation of the network asserted identity is restricted" AND (non-roaming II-NNI OR home-to-visited response on roaming II-NNI)) | | | | | | | | | | | +| NOTE 1: The SIP status code is only applicable over the roaming II-NNI. | | | | | | | | | | | | +| NOTE 2: If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. | | | | | | | | | | | | + +## --- B.16 UPDATE method + +The table B.16.1 lists the supported header fields within the UPDATE request. + +**Table B.16.1: Supported header fields within the UPDATE request** + +| Item | Header field | Ref. | RFC status | II-NNI condition | +|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|------------|----------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Accept | [13], [23] | o | do | +| 2 | Accept-Contact | [51] | o | do | +| 3 | Accept-Encoding | [13], [23] | o | do | +| 4 | Accept-Language | [13], [23] | o | do | +| 5 | Allow | [13], [23] | o | do | +| 6 | Allow-Events | [20] | n/a | dn/a | +| 7 | Authorization | [13], [23] | o | IF table 6.1.3.1/7 THEN do (NOTE) | +| 8 | Call-ID | [13], [23] | m | dm | +| 9 | Call-Info | [13], [23] | o | do | +| 10 | Cellular-Network-Info | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE) | +| 11 | Contact | [13], [23] | m | dm | +| 12 | Content-Disposition | [13], [23] | o | do | +| 13 | Content-Encoding | [13], [23] | o | do | +| 14 | Content-ID | [216] | o | IF table 6.1.3.1/122 THEN do | +| 15 | Content-Language | [13], [23] | o | do | +| 16 | Content-Length | [13], [23] | t | dt | +| 17 | Content-Type | [13], [23] | * | d* | +| 18 | CSeq | [13], [23] | m | dm | +| 19 | Date | [13], [23] | o | do | +| 20 | Feature-Caps | [143] | o | IF table 6.1.3.1/103 THEN do (NOTE) | +| 21 | From | [13], [23] | m | dm | +| 22 | Geolocation | [68] | o | do | +| 23 | Geolocation-Routing | [68] | o | do | +| 24 | Max-Breadth | [79] | o | dn/a | +| 25 | Max-Forwards | [13], [23] | m | dm | +| 26 | MIME-Version | [13], [23] | o | do | +| 27 | Min-SE | [52] | o | do | +| 28 | Organization | [13], [23] | o | do | +| 29 | P-Access-Network-Info | [24], [24B] | o | IF table 6.1.3.1/36 THEN do (NOTE) | +| 30 | P-Charging-Function-Addresses | [24] | o | dn/a | +| 31 | P-Charging-Vector | [24] | o | IF table 6.1.3.1/38 THEN do (NOTE) | +| 32 | P-Early-Media | [74] | o | IF dc1 (CAT: clause 12.14) OR
dc2 (announcements: clause 12.21) THEN dm
ELSE IF table 6.1.3.1/69 THEN do (NOTE) | +| 33 | Priority-Share | [5] | n/a | IF home-to-visited request on roaming II-NNI
AND table 6.1.3.1/118 THEN do (NOTE) | +| 34 | Privacy | [34] | o | do | +| 35 | Proxy-Authorization | [13], [23] | o | IF table 6.1.3.1/7 THEN do (NOTE) | +| 36 | Proxy-Require | [13], [23] | o | do | +| 37 | Reason | [48] | o | IF table 6.1.3.1/40 THEN do (NOTE) | +| 38 | Record-Route | [13], [23] | o | do | +| 39 | Recv-Info | [39] | o | IF table 6.1.3.1/17 THEN do (NOTE) | +| 40 | Referred-By | [53] | o | do | +| 41 | Reject-Contact | [51] | o | do | +| 42 | Relayed-Charge | [5] | n/a | dn/a | +| 43 | Request-Disposition | [51] | o | do | +| 44 | Require | [13], [23] | c | dc | +| 45 | Resource-Priority | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE) | +| 46 | Resource-Share | [5] | n/a | IF (home-to-visited request on roaming II-NNI
OR visited-to-home request on roaming II-NNI)
AND table 6.1.3.1/116 THEN do (NOTE) | +| 47 | Route | [13], [23] | c | dc | +| 48 | Security-Client | [47] | o | dn/a | +| 49 | Security-Verify | [47] | o | dn/a | +| 50 | Session-Expires | [52] | o | do | +| 51 | Session-ID | [124] | m | IF table 6.1.3.1/94 THEN dm (NOTE) | +| 52 | Supported | [13], [23] | o | do | +| 53 | Timestamp | [13], [23] | o | do | +| 54 | To | [13], [23] | m | dm | +| 55 | User-Agent | [13], [23] | o | do | +| 56 | Via | [13], [23] | m | dm | +| dc1: | request invoked due to stopping or restarting CAT early media on an existing dialog AND (non-roaming II-NNI OR loopback traversal scenario OR home-to-visited response on roaming II-NNI) | | | | +| dc2: | request invoked due to stopping or restarting announcement early media AND (non-roaming II-NNI OR | | | | + +| Item | Header field | Ref. | RFC status | II-NNI condition | +|----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|------------|------------------| +| loopback traversal scenario OR home-to-visited response on roaming II-NNI) | | | | | +| NOTE: | If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. | | | | + +The table B.16.2 lists the supported header fields within the UPDATE response. + +###### **Table B.16.2: Supported header fields within the UPDATE response** + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|------|-------------------------------|-----------------|--------------------|------------|--------------------------------------------------------------------------------------| +| 1 | Accept | 2xx | [13], [23] | o | do | +| | | 415 | | c | dc | +| 2 | Accept-Encoding | 2xx | [13], [23] | o | do | +| | | 415 | | c | dc | +| 3 | Accept-Language | 2xx | [13], [23] | o | do | +| | | 415 | | c | dc | +| 4 | Accept-Resource-Priority | 2xx
417 | [78] | o | IF table 6.1.3.1/73 THEN do (NOTE 2) | +| 5 | Allow | 405 | [13], [23] | m | dm | +| | | others | | o | do | +| 6 | Allow-Events | 2xx | [20] | n/a | dn/a | +| 7 | Authentication-Info | 2xx | [13], [23] | o | IF table 6.1.3.1/7 THEN do (NOTE 2) | +| 8 | Call-ID | 100 | [13], [23] | m | dm | +| | | others | | | | +| 9 | Call-Info | r | [13], [23] | o | do | +| 10 | Cellular-Network-Info | r | [5] | n/a | IF table 6.1.3.1/117 THEN do (NOTE 2) | +| 11 | Contact | 2xx | [13], [23] | m | dm | +| | | 3xx | | o | do | +| | | 485 | | o | do | +| 12 | Content-Disposition | r | [13], [23] | o | do | +| 13 | Content-Encoding | r | [13], [23] | o | do | +| 14 | Content-ID | r | [216] | o | IF table 6.1.3.1/122 THEN do | +| 15 | Content-Language | r | [13], [23] | o | do | +| 16 | Content-Length | 100 | [13], [23] | t | dt | +| | | others | | | | +| 17 | Content-Type | r | [13], [23] | * | d* | +| 18 | CSeq | 100 | [13], [23] | m | dm | +| | | others | | | | +| 19 | Date | 100 | [13], [23] | o | do | +| | | others | | | | +| 20 | Error-Info | 3xx-6xx | [13], [23] | o | IF table 6.1.3.1/13 THEN do (NOTE 2) | +| 21 | Feature-Caps | 2xx | [143] | o | IF table 6.1.3.1/103 THEN do (NOTE 2) | +| 22 | From | 100 | [13], [23] | m | dm | +| | | others | | | | +| 23 | Geolocation-Error | 424 | [68] | m | dm | +| | | others | | o | do | +| 24 | MIME-version | r | [13], [23] | o | do | +| 25 | Min-SE | 422 | [52] | m | dm | +| 26 | Organization | r | [13], [23] | o | do | +| 27 | P-Access-Network-Info | r | [24], [24A], [24B] | o | IF table 6.1.3.1/36 THEN do (NOTE 2) | +| 28 | P-Charging-Function-Addresses | r | [24], [24A] | o | dn/a | +| 29 | P-Charging-Vector | 100 | [24], [24A] | o | dn/a | +| | | others | | o | IF table 6.1.3.1/38 THEN do (NOTE 2) | +| 30 | P-Early-Media | 2xx | [74] | o | IF table 6.1.3.1/69 THEN do (NOTE 2) | +| 31 | Priority-Share | 2xx | [5] | n/a | IF home-to-visited response on roaming II-NNI AND table 6.1.3.1/118 THEN do (NOTE 2) | +| 32 | Privacy | r | [34] | o | do | +| 33 | Proxy-Authenticate | 401 (NOTE 1) | [13], [23] | o | do | +| | | 407 (NOTE 1) | | m | dm | +| 34 | Record-Route | 2xx | [13], [23] | o | do | +| 35 | Recv-Info | 2xx | [39] | c | IF table 6.1.3.1/17 THEN dc | + +| Item | Header field | SIP status code | Ref. | RFC status | II-NNI condition | +|------|------------------|------------------------------------------------------|------------|------------|--------------------------------------------------------------------------------------------------------------------------------------| +| | | others | | o | (NOTE 2)
IF table 6.1.3.1/17 THEN do (NOTE 2) | +| 36 | Relayed-Charge | r | [5] | n/a | dn/a | +| 37 | Require | r | [13], [23] | c | dc | +| 38 | Resource-Share | 2xx | [5] | n/a | IF (home-to-visited response on roaming II-NNI OR visited-to-home response on roaming II-NNI) AND table 6.1.3.1/116 THEN do (NOTE 2) | +| 39 | Response-Source | 3xx-6xx | [5] | n/a | IF table 6.1.3.1/121 THEN do (NOTE 2) | +| 40 | Retry-After | 404
413
480
486
500
503
600
603 | [13], [23] | o | do | +| 41 | Security-Server | 421
494 | [47] | o | dn/a | +| 42 | Server | r | [13], [23] | o | do | +| 43 | Session-Expires | 2xx | [52] | o | do | +| 44 | Session-ID | r | [124] | m | IF table 6.1.3.1/94 THEN dm (NOTE 2) | +| 45 | Supported | 2xx | [13], [23] | o | do | +| 46 | Timestamp | r | [13], [23] | o | do | +| 47 | To | 100
others | [13], [23] | m | dm | +| 48 | Unsupported | 420 | [13], [23] | m | dm | +| 49 | User-Agent | r | [13], [23] | o | do | +| 50 | Via | 100
others | [13], [23] | m | dm | +| 51 | Warning | r | [13], [23] | o | do | +| 52 | WWW-Authenticate | 401
(NOTE 1)
407
(NOTE 1) | [13], [23] | m
o | dm
do | + +NOTE 1: The SIP status code is only applicable over the roaming II-NNI. + +NOTE 2: If the capability specified in table 6.1.3.1 is not supported over the II-NNI, the IBCF in the receiving network can omit or modify the SIP header fields in the received SIP message prior to forwarding the SIP message as specified in 3GPP TS 24.229 [5] clause 5.10.6.2. + +# --- Annex C (informative): The list of option items for II-NNI + +## C.1 Scope + +This annex provides a list of items that are recommended to be selected by inter-operator agreements for the interconnection between IMS operators using the II-NNI. The items in this annex have an influence on the service interconnection. + +For the purposes of this annex, these items are called "option items". The option items are extracted from the present document other than this annex, and are categorized from the aspect of service provisioning by IMS operators. + +If an option item is used based on inter-operator agreements, then relating capabilities described in the references are used over the II-NNI. In case of misalignment between the normative part of the present document and this annex, the normative part of the present document takes precedence. + +## --- C.2 Format of option item table + +The format of option item table used in the subsequent clauses is as follows: + +- The 2nd column "Option item" shows the option item. +- The 3rd column "References" shows the relevant clauses of the present document for each option item. +- The 4th column "Applicability at the II-NNI" shows the selectable patterns for each option item. +- The 5th column "Details for operator choice" shows the details for the inter-operator agreements in case the corresponding pattern is chosen. This column intends to be used to exchange each detailed conditions of the II-NNI by means of filling the conditions in the columns corresponding to the selected pattern. Blank row intends to be used as a place holder for describing additional detailed II-NNI conditions specific to the operator network not associated with the explicit descriptions in this annex. + +## --- C.3 Option item table + +### C.3.0 Supported II-NNI traversal scenarios + +In this clause the table C.3.0.1 shows the supported II-NNI traversal scenarios option items. + +**Table C.3.0.1: Supported II-NNI traversal scenarios** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|----------------------------|------------------------------|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Roaming II-NNI support | entire present specification | Yes | Option items in clauses C.3.1 and C.3.2.
Applicability of "Roaming Architecture for Voice over IMS with Local Breakout" (Clause 19).
If "Roaming Architecture for Voice over IMS with Local Breakout" is applicable:
+ option items in clause C.3.3;
and
+ the default TRF address to use when not included in the "g.3gpp.trf" feature-capability indicator. | +| | | | No | | +| | | | Yes | Option items in clauses C.3.1 and C.3.3. | +| | | | No | | +| 2 | Non-roaming II-NNI support | entire present specification | Yes | Option items in clauses C.3.1 and C.3.3. | +| | | | No | | + +### C.3.1 Option item table common to roaming, non-roaming II-NNI and loopback traversal scenario + +This clause describes the option item tables common to the roaming II-NNI, the loopback traversal scenario, and the non-roaming II-NNI as follows: + +- Table C.3.1.1 shows the SIP methods option items. +- Table C.3.1.1A shows the SIP overload control option items. +- Table C.3.1.2 shows the SIP negotiation of resource reservation option item. +- Table C.3.1.2A shows the periodic refresh of SIP sessions option item. +- Table C.3.1.3 shows the replacing of SIP dialogs option item. +- Table C.3.1.4 shows the session participation option item. +- Table C.3.1.5 shows the conveying capabilities of UE option item. +- Table C.3.1.5A shows the authorization of early media option item. +- Table C.3.1.6 shows the asserting the service of authenticated users option item. +- Table C.3.1.7 shows the mode of signalling. +- Table C.3.1.7A shows the SIP message bodies option item. +- Table C.3.1.7B shows the SIP message body size option item. +- Table C.3.1.8 shows the control plane transport option item. +- Table C.3.1.9 shows the user plane transport, media, and codec option items. +- Table C.3.1.10 shows the dual tone multi frequency (DTMF) option item. +- Table C.3.1.10A shows the numbering, naming and addressing option item. +- Table C.3.1.11 shows the IP version option item. +- Table C.3.1.12 shows the supplementary services option items. + +- Table C.3.1.13 shows the additional functions option items. +- Table C.3.1.14 shows the SDP lines option items. +- Table C.3.1.15 shows the emergency services option items. +- Table C.3.1.16 shows indicating the II-NNI traversal scenario option items. +- Table C.3.1.17 shows the Mission critical services option items. +- Table C.3.1.18 shows the Calling number verification using signature verification and attestation information option items. + +**Table C.3.1.1: SIP method** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|----------------|------------------------------|-----------------------------|--------------------------------------------------------------------| +| 1 | INFO method | table 6.1/5A
table 6.1/5B | Yes | Info package name to use. | +| | | | No | | +| 2 | MESSAGE method | table 6.1/9A
table 6.1/9B | Yes | Inside or outside existing dialog, and content of MESSAGE request. | +| | | | No | | +| 3 | REFER method | table 6.1/16
table 6.1/17 | Yes | Inside or outside existing dialog. | +| | | | No | | + +**Table C.3.1.1A: SIP overload control** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|----------------------|----------------------------------|-----------------------------|--------------------------------------------------------| +| 1 | SIP overload control | table 6.1.3.1/106
clause 21.1 | Yes | Mechanisms to be used. | +| | | | | Whether to exempt MPS from SIP overload controls. | +| | | | No | | +| 2 | Feedback control | table 6.1.3.1/107
clause 21.2 | Yes | Algorithm to be used if not default (see clause 21.2). | +| | | | No | | +| 3 | Event control | table 6.1.3.1/108
clause 21.3 | Yes | Addresses to targets that can be supervised. | +| | | | No | | + +**Table C.3.1.2: Negotiation of resource reservation** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|----------------------------------------------------|------------------|-----------------------------|-----------------------------| +| 1 | Negotiation of resource reservation (precondition) | table 6.1.3.1/20 | Yes | | +| | | | No | | + +**Table C.3.1.2A: Periodic refresh of SIP sessions** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|---------------------------|------------------|-----------------------------|-------------------------------------------------------------------------------------------------------------------| +| 1 | SIP session timer (timer) | table 6.1.3.1/45 | Yes | Use conditions (Possible restriction on range of times and whether SIP session timer is applied in all sessions). | +| | | | | | + +**Table C.3.1.3: Replacing of SIP dialogs** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|-------------------------------------|------------------|-----------------------------|-----------------------------| +| 1 | Replacing of SIP dialogs (replaces) | table 6.1.3.1/47 | Yes | | +| | | | No | | + +**Table C.3.1.4: Session participation** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|------------------------------|------------------|-----------------------------|-----------------------------| +| 1 | Session participation (join) | table 6.1.3.1/48 | Yes | | +| | | | No | | + +**Table C.3.1.5: Conveying capabilities of UE** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|------------------------------|------------------|-----------------------------|-----------------------------| +| 1 | Conveying capabilities of UE | table 6.1.3.1/49 | Yes | | +| | | | No | | + +**Table C.3.1.5A: Authorization of early media** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|------------------------------|------------------|-----------------------------|------------------------------------------------------------------------------------------------------| +| 1 | Authorization of early media | table 6.1.3.1/69 | Yes | Whether to use authorization request of early media generated by the entity outside the IMS network. | +| | | | No | | + +**Table C.3.1.6: Asserting the service of authenticated users** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|-----------------------------------------------------------------------------------|------------------|-----------------------------|-----------------------------------| +| 1 | Managing the indication of the asserted service (P-Asserted-Service header field) | table 6.1.3.1/77 | Yes | Service identifier values to use. | +| | | | No | | + +**Table C.3.1.7: Mode of signalling** + +| No. | Option item | | References | Applicability at the II-NNI | Details for operator choice | +|-----|------------------------|------------------|----------------|-----------------------------|-----------------------------| +| 1 | Overlap signalling | In-dialog method | clause 6.1.1.5 | Yes | | +| | | | | No | | +| | Multiple-INVITE method | | | Yes | | +| | | | | No | | + +**Table C.3.1.7A: SIP message bodies** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|-------------|--------------|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | MIME type | clause 6.1.4 | Yes | MIME types to use. | +| | | | | Applicable characteristics of the SIP message body MIMEs (i.e. the value(s) of Content-Disposition header field and Content-Language header field) if necessary. | +| | | | | | + +**Table C.3.1.7B: SIP message body size** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|----------------------------------------------------|--------------|-----------------------------|-----------------------------| +| 1 | Limitation on maximum length of a SIP message body | clause 6.1.4 | Yes | Maximum length accepted. | +| | | | No | | + +**Table C.3.1.8: Control plane transport** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|-------------|------------|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| 1 | TCP | clause 6.2 | Yes | Use conditions (e.g. port number to accept, number of simultaneous connections in case of reuse of the existing connections). | +| | | | No | | +| 2 | UDP | clause 6.2 | Yes | Use conditions (e.g. port number to accept). | +| | | | No | | +| 3 | SCTP | clause 6.2 | Yes | Use conditions (e.g. port number to accept). | +| | | | No | | + +**Table C.3.1.9: User plane transport, media, and codec** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|-------------------------------|------------------------------|-----------------------------|------------------------------------------------------------------------------------------------------| +| 1 | Speech media (m=audio) | clause 7.1 | Yes | Names of speech codecs to use. (NOTE 1, NOTE 2) | +| | | | No | | +| 2 | Video media (m=video) | clause 7.1 | Yes | Names of video codecs to use. (NOTE 1, NOTE 2) | +| | | | No | | +| 3 | Other media | clause 7.1 | Yes | Media type (m=line of SDP) to use (e.g. application, image, message). | +| | | | No | | +| 4 | RTP/AVPF | clause 7.2 | Yes | Media type (m=line of SDP) that uses the protocol. | +| | | | No | | +| 5 | Transmission Control Protocol | clause 6.1.2.1
clause 7.2 | Yes | Media type (m=line of SDP) that uses the protocol. | +| | | | No | | +| 6 | Other user plane protocols | clause 7.2 | Yes | Protocols to use (e.g. udptl, TCP/MSRP) and media types (m=line of SDP) that describe the protocols. | +| | | | No | | + +NOTE 1: Codecs which are included in the applicable codec list made by inter-operator agreements are guaranteed to be supported at the II-NNI by the peer operators. + +NOTE 2: Whether it is allowed to offer codecs which are not included in the applicable codec list made by inter-operator agreements over the II-NNI is also determined by the inter-operator agreement if necessary. + +**Table C.3.1.10: Dual tone multi frequency (DTMF)** + +| No. | Option item | | References | Applicability at the II-NNI | Details for operator choice | +|-----|------------------------|----------------------------------------|----------------------------------------------------------------------------|-----------------------------|-----------------------------| +| 1 | DTMF transport | "telephone-event" based DTMF transport | clause 7.1
table 6.1/5A
table 6.1/5B
clause 12.14
clause 12.15 | Yes | Sampling rate to use. | +| | | | | No | | +| | The SIP INFO mechanism | | | Yes | | +| | | | | No | | + +**Table C.3.1.10A: Numbering, naming and addressing** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|---------------------------------------|------------|-----------------------------|-----------------------------| +| 1 | Subaddress ("isub" tel URI parameter) | clause 8.1 | Yes | | +| | | | No | | + +**Table C.3.1.11: IP version** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|-------------|------------|-----------------------------|----------------------------------------------------------| +| 1 | IPv4 | clause 9 | Yes | Use conditions (e.g. for control plane, for user plane). | +| | | | No | | +| 2 | IPv6 | clause 9 | Yes | Use conditions (e.g. for control plane, for user plane). | +| | | | No | | + +**Table C.3.1.12: Supplementary services** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|------------------------------------------------------------------------------------------------|---------------------------------------------|-----------------------------|--------------------------------------------------------------------------| +| 1 | Malicious Communication Identification (MCID) | clause 12.2 | Yes | Minimum information exchanged over the II-NNI. | +| | | | No | | +| 2 | Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) | clause 12.3 | Yes | | +| | | | No | | +| 3 | Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) | clause 12.4 | Yes | | +| | | | No | | +| 4 | Anonymous Communication Rejection (ACR) | clause 12.5 | Yes | | +| | | | No | | +| 5 | Communication DIVersion (CDIV) | clause 12.6 | Yes | | +| | | | No | | +| 6 | Communication Waiting (CW) | clause 12.7 | Yes | | +| | | | No | | +| 7 | Communication HOLD (HOLD) | clause 12.8 | Yes | | +| | | | No | | +| 8 | Message Waiting Indication (MWI) | clause 12.9 | Yes | | +| | | | No | | +| 9 | Incoming Communication Barring (ICB) | clause 12.10.1 | Yes | | +| | | | No | | +| 10 | Completion of Communications to Busy Subscriber (CCBS) | clause 12.11 | Yes | | +| | | | No | | +| 11 | Completion of Communications by No Reply (CCNR) | clause 12.12 | Yes | | +| | | | No | | +| 12 | Explicit Communication Transfer (ECT) | clause 12.13 | Yes | Type of explicit communication transfer to support. | +| | | | No | | +| 13 | Customized Alerting Tone (CAT) | clause 12.14 | Yes | CAT model to use (Gateway model, forking model and early session model). | +| | | | | Media type (m=line of SDP) applicable to CAT. | +| | | | No | | +| 14 | Customized Ringing Signal (CRS) | clause 12.15 | Yes | | +| | | | No | | +| 15 | Closed User Group (CUG) | clause 12.16 | Yes | | +| | | | No | | +| 16 | Personal Network Management (PNM) | clause 12.17 | Yes | | +| | | | No | | +| 17 | Three-Party (3PTY) | clause 12.18 | Yes | | +| | | | No | | +| 18 | Conference (CONF) | clause 12.19 | Yes | | +| | | | No | | +| 19 | Flexible Alerting (FA) | clause 12.20 | Yes | | +| | | | No | | +| 20 | Announcements | During the establishment of a session | Yes | Methods for sending announcement. | +| | | | | | +| | | During an established communication session | Yes | Methods for sending announcement. | +| | | | | | +| | | Providing announcements | Yes | Methods for sending announcement. | + +| No. | Option item | | References | Applicability at the II-NNI | Details for operator choice | +|------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|----------------------------------------|---------------------------------------------------------|-----------------------------|-----------------------------------------------------------------------------| +| | | when communication request is rejected | | No | | +| | | | | | | +| 21 | Advice Of Charge (AOC) | | clause 12.22 | Yes | | +| | | | | No | | +| 22 | Completion of Communications on Not Logged-in (CCNL) | | clause 12.23 | Yes | | +| | | | | No | | +| 23 | Presence service | | clause 15 | Yes | Presence services to use (TS 24.141 [132], OMA 1.1 [142] or OMA 2.0 [138]). | +| | | | | No | | +| 24 | Messaging service | Page-mode messaging | clause 16.2 | Yes | | +| | | | | No | | +| | | Session-mode messaging | clause 16.4 | Yes | | +| | | | | No | | +| 24A | | Session-mode messaging conferences | clause 16.5 | Yes | | +| | | | | No | | +| 24A | Delivery of original destination identity | | clause 22 | Yes | Services to apply the function. | +| | | | | No | | +| 24B | Service access number translation | | table 6.1.3.1/52A
clause 27 | Yes | | +| | | | | No | | +| 25 | Other additional service using other SIP extensions | | clause 6.1.1.3.2
clause 12.6 | Yes | The SIP extensions to use and the service that uses the extensions. | +| | | | | No | | +| 26 | Multi-Identity (MiD) | | clause 6.1.1.3.1
table 6.1.3.1/126
clause 12.26.2 | Yes | Types of non-native identities to support. (NOTE) | +| | | | | No | | +| NOTE: The non-native identities, as defined in 3GPP TS 24.174 [218] are: an alternative identity, an external alternative identity and a virtual identity. | | | | | | + +**Table C.3.1.13: Additional functions** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|------------------------------------------------------|-------------------|-----------------------------|-------------------------------------------------------------------------------------------------| +| 1 | Optimal Media Routeing | clause 17 | Yes | | +| | | | No | | +| 2 | Applying forking (NOTE 1) | table 6.1.3.1/5 | Yes | Usage of Request-Disposition header field with value "no-fork". (NOTE 3) | +| | | | No (NOTE 2) | | +| 3 | Transfer of IP multimedia service tariff information | clause 11.3 | Yes | The value of the Content-Disposition header field. | +| | | | No | | +| 4 | Telepresence using IMS | clause 23 | Yes | The value of "+sip.clue" media feature tag in Contact header field. | +| | | | No | | +| 5 | Dynamic services interactions | table 6.1.3.1/125 | Yes | The identities of the services in the Service-Interact-Info header field. | +| | | | No | | +| 6 | MTSI Data channel | clause 33 | Yes | The value "webrtc-datachannel" of "+sip.app-subtype" media feature tag in Contact header field. | +| | | | No | | + +NOTE 1: Support of handling of several responses due to forking and of the Request-Disposition header field, is mandated on the II-NNI. + +NOTE 2: In case the operator interconnects with IMS non-compliant networks, and wishes to use the II-NNI anyway, then the operators might want to negotiate if the forking procedures are applicable. + +NOTE 3: The Request-Disposition header field with value "no-fork" can be used to suppress that forking occurs. However, a peer operator might require the usage of forking e.g. to implement certain services. + +**Table C.3.1.14: SDP lines** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|-------------|--------------|-----------------------------|----------------------------------------------------| +| 1 | m=line | clause 6.1.2 | Yes | Used static RTP payload type numbers. | +| | | | | | +| 2 | b=line | clause 6.1.2 | Yes | Used bandwidth modifier types. | +| | | | | | +| 3 | a=line | clause 6.1.2 | Yes | Used attributes. | +| | | | | For the "rtpmap" attribute, used "encoding names". | + +**Table C.3.1.15: Emergency services** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|-----------------------------------------------|-------------------|-----------------------------|-------------------------------| +| 1 | Public Safety Answering Point (PSAP) Callback | table 6.1.3.1/110 | Yes | Used PSAP callback indicator. | +| | | | No | | + +**Table C.3.1.16: Indicating the II-NNI traversal scenario** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|----------------------------------------------------------------------------------|---------------------------------|-----------------------------|-----------------------------| +| 1 | Support of the "iotl" SIP URI parameter indicating the II-NNI traversal scenario | table 6.1.3.1/112
clause 5.3 | Yes | | +| | | | No | | + +**Table C.3.1.17: Mission critical services** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|--------------------------------------|---------------|-----------------------------|----------------------------------------------------------| +| 1 | Support of Mission critical services | clause 28.2.2 | Yes | MBMS transmission usage and location procedures support. | +| | | | No | | + +**Table C.3.1.18: Calling number verification using signature verification and attestation information** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|--------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-----------------------------|-----------------------------| +| 1 | Calling number verification using signature verification and attestation information | table 6.1.3.1/119
table 6.1.3.1/120
table 6.1.3.1/123
table 6.1.3.1/124
clause 29 | Yes | | +| | | | No | | + +### C.3.2 Option item table specific to roaming II-NNI + +This clause describes the option item tables specific to roaming II-NNI as follows: + +- Table C.3.2.1 shows the mechanism for authentication option items. +- Table C.3.2.1A shows the charging option items. +- Table C.3.2.2 shows the key of service profile for HSS query option item. +- Table C.3.2.3 shows the numbering, naming and addressing option items. +- Table C.3.2.4 shows the supplementary services option items. +- Table C.3.2.5 shows the access transfer services option items. +- Table C.3.2.6 shows the registration of bulk number contacts option items. +- Table C.3.2.7 shows the P-CSCF restoration option items. +- Table C.3.2.8 shows the resource sharing option items. +- Table C.3.2.9 shows the Priority sharing option items. +- Table C.3.2.9A shows the PS data off extension option items. +- Table C.3.2.10 shows the RLOS option items. + +**Table C.3.2.1: Mechanism for authentication** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|-----------------------------------------|-----------------|-----------------------------|-----------------------------| +| 1 | IMS AKA plus Ipsec ESP | table 6.1.3.1/7 | Yes | | +| | | | No | | +| 2 | SIP digest plus check of IP association | table 6.1.3.1/7 | Yes | | +| | | | No | | +| 3 | SIP digest plus Proxy Authentication | table 6.1.3.1/7 | Yes | | +| | | | No | | +| 4 | SIP digest with TLS | table 6.1.3.1/7 | Yes | | +| | | | No | | + +**Table C.3.2.1A: Charging** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|----------------------------------------------------|---------------------------------|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Inter-operator accounting | table 6.1.3.1/38
clause 11.2 | Yes | Operator network identifiers populated in the type 1 "orig-ioi" and "term-ioi" header field parameters of the P-Charging-Vector header field. | +| | | | No | | +| 2 | Inter-operator accounting for the transit scenario | clause 11.2 | Yes | Operator network identifiers populated in the "transit-ioi" header field parameters of the P-Charging-Vector header field. | +| | | | No | | + +**Table C.3.2.2: The key of service profile for HSS query** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|-----------------------------------------------------------------------|------------------|-----------------------------|-----------------------------| +| 1 | The key of service profile for HSS query (P-Profile-Key header field) | table 6.1.3.1/59 | Yes | | +| | | | No | | + +**Table C.3.2.3: Numbering, naming and addressing** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|---------------------------------------------------------------|--------------------------|-----------------------------|-----------------------------| +| 1 | Dial string ("user=dialstring" SIP URI parameter) | table 6.1.3.1/67 | Yes | | +| | | | No | | +| 2 | Barring of premium numbers ("premium-rate" tel URI parameter) | clause 8.1,
clause 24 | Yes | | +| | | | No | | + +**Table C.3.2.4: Supplementary services** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|-----------------------------------------|----------------|-----------------------------|-----------------------------| +| 1 | Outgoing Communication Barring (OCB) | clause 12.10.2 | Yes | | +| | | | No | | +| 2 | Unstructured Supplementary Service Data | clause 12.24 | Yes | | +| | | | No | | +| 3 | Enhanced Calling Name | clause 12.25 | Yes | | +| | | | No | | + +**Table C.3.2.5: Access transfer services** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|-----------------------------------------------------|-------------|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | IMS Centralized Services (ICS) | clause 13 | Yes | | +| | | | No | | +| 2 | PS to CS Single Radio Voice Call Continuity (SRVCC) | clause 14 | Yes | Additional use conditions (PS to CS SRVCC for calls in alerting phase, support of ATCF architecture, PS to CS SRVCC for calls in pre-alerting phase and PS to CS SRVCC with the MSC server assisted mid-call feature). | +| | | | | If the ATCF architecture applies, the URIs of SCC ASs authorised to provide PS to CS SRVCC information in the MESSAGE request. | +| | | | No | | +| | | | | | +| 3 | Single Radio Video Call Continuity (vSRVCC) | clause 14 | Yes | Additional use condition (transfer in alerting phase). | +| | | | No | | +| 4 | Inter UE Transfer (IUT) | clause 18 | Yes | | +| | | | No | | +| 5 | CS to PS Single Radio Voice Call Continuity (SRVCC) | clause 14.5 | Yes | The URIs of SCC ASs authorised to provide CS to PS SRVCC information in the MESSAGE request. | +| | | | | Additional use conditions (support of CS to PS SRVCC for calls in alerting phase and support of CS to PS SRVCC with the assisted mid-call feature). | +| | | | No | | +| | | | | | +| 6 | PS to CS Dual Radio Voice Call Continuity (DRVCC) | clause 14.6 | Yes | Additional use conditions (PS to CS DRVCC for calls in alerting phase, PS to CS DRVCC for originating calls in pre-alerting phase, PS to CS DRVCC with the MSC server assisted mid-call feature and the use of IMS Centralized Services (ICS) and the tel URI in STN). | +| | | | No | | +| 7 | CS to PS Dual Radio Voice Call Continuity (DRVCC) | clause 14.7 | Yes | Additional use conditions (CS to PS DRVCC for calls in alerting phase, CS to PS DRVCC for originating calls in pre-alerting phase, CS to PS DRVCC with the MSC server assisted mid-call feature) and the use of IMS Centralized Services (ICS). | +| | | | No | | + +**Table C.3.2.6: Registration of bulk number contacts** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|--------------------------------------|-------------------|-----------------------------|-----------------------------| +| 1 | Registration of bulk number contacts | table 6.1.3.1/104 | Yes | | +| | | | No | | + +**Table C.3.2.7: P-CSCF restoration** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|-----------------------------------------|-------------|-----------------------------|-----------------------------| +| 1 | PCRF or PCF based P-CSCF restoration | clause 25.2 | Yes | | +| | | | No | | +| 2 | HSS or UDM/HSS based P-CSCF restoration | clause 25.3 | Yes | | +| | | | No | | + +**Table C.3.2.8: Resource sharing** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|------------------|------------|-----------------------------|-----------------------------| +| 1 | Resource sharing | clause 26 | Yes | | +| | | | No | | + +**Table C.3.2.9: Priority sharing** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|------------------|---------------------------------|-----------------------------|-----------------------------| +| 1 | Priority sharing | clause 28,
table 6.1.3.1/118 | Yes | | +| | | | No | | + +**Table C.3.2.9A: 3GPP PS data off extension** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|----------------------------|----------------------------------|-----------------------------|-----------------------------| +| 1 | 3GPP PS data off extension | clause 32,
table 6.1.3.1/121A | Yes | | +| | | | No | | + +**Table C.3.2.10: RLOS** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|-------------|---------------------------------|-----------------------------|-----------------------------| +| 1 | RLOS | clause 31,
table 6.1.3.1/127 | Yes | | +| | | | No | | + +### C.3.3 Option item table specific to non-roaming II-NNI and loopback traversal scenario + +This clause describes the option item tables specific to the non-roaming II-NNI and the loopback traversal scenario as follows: + +- Table C.3.3.1 shows the SIP method option items. +- Table C.3.3.2 shows the charging option items. +- Table C.3.3.3 shows the GRUU option items. +- Table C.3.3.4 shows the media feature tags option items. +- Table C.3.3.5 shows the ISDN interworking option items. +- Table C.3.3.6 shows the corporate network option items. +- Table C.3.3.7 shows the numbering, naming and addressing option items. +- Table C.3.3.8 shows the additional functions option item. +- Table C.3.3.9 shows IMS emergency session traversal scenario option item. + +**Table C.3.3.1: SIP method** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|------------------|--------------------------------|-----------------------------|-----------------------------| +| 1 | NOTIFY method | table 6.1/10
table 6.1/11 | Yes | Event package name to use. | +| | | | No | | +| 2 | SUBSCRIBE method | table 6.1/20
table 6.1/21 | Yes | Event package name to use. | +| | | | No | | +| 3 | PUBLISH method | table 6.1/15A
table 6.1/15B | Yes | Event package name to use. | +| | | | No | | + +**Table C.3.3.2: Charging** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|----------------------------------------------------|---------------------------------|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| +| 1 | Inter-operator accounting | table 6.1.3.1/38
clause 11.2 | Yes | Operator network identifiers populated in the type 2 "orig-ioi" and "term-ioi" header field parameters of the P-Charging-Vector header field. | +| | | | No | | +| 2 | Inter-operator accounting for the transit scenario | clause 11.2 | Yes | Operator network identifiers populated in the "transit-ioi" header field parameters of the P-Charging-Vector header field. | +| | | | No | | + +**Table C.3.3.3: Globally routable user agent URIs (GRUU)** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|------------------------------------------|------------------|-----------------------------|-----------------------------| +| 1 | Globally Routable User Agent URIs (gruu) | table 6.1.3.1/56 | Yes | | +| | | | No | | + +**Table C.3.3.4: Media feature tags** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|--------------------|-----------------------------------------------------------------------------------|-----------------------------|-------------------------------------| +| 1 | Media feature tags | table 6.1.3.1/76
clause 12
clause 13
clause 14
clause 16
clause 18 | Yes | Names of media feature tags to use. | +| | | | No | | + +**Table C.3.3.5: ISDN interworking** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|--------------------------------------------------------------------------|------------------|-----------------------------|-----------------------------| +| 1 | User to User Call Control Information in SIP for ISDN Interworking (uui) | table 6.1.3.1/79 | Yes | | +| | | | No | | + +**Table C.3.3.6: Corporate network** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|-------------------------|------------------|-----------------------------|-----------------------------| +| 1 | Private network traffic | table 6.1.3.1/80 | Yes | | + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|---------------------------------------------|------------|-----------------------------|-----------------------------| +| | (P-Private-Network-Indication header field) | | No | | + +**Table C.3.3.7: Numbering, naming and addressing** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|------------------------------------------------------------------------|------------|-----------------------------|---------------------------------------------------------------------------------------| +| 0 | SIP URI | clause 8.1 | Yes | Any local numbers that are allowed in addition to global numbers. | +| | | | | Domain name(s) and/or IP address(es) of hostportion to accept. | +| | | | | Applicability of PSI to use. | +| | | | | Applicability of "Unavailable User Identity" in the P-Asserted-Identity header field. | +| | | | | | +| 0A | tel URI (NOTE) | clause 8.1 | Yes | Any local numbers that are allowed in addition to global numbers. | +| | | | | Applicability of the URI in the P-Asserted-Identity header field and/or Request-URI. | +| | | | No | | +| 0B | IM URI | clause 8.1 | Yes | | +| | | | No | | +| 0C | PRES URI | clause 8.1 | Yes | | +| | | | No | | +| 1 | Number Portability Routing Number ("rn" and "npdi" tel URI parameters) | clause 8.1 | Yes | | +| | | | No | | +| 2 | Calling Party's Category ("cpc" tel URI parameter) | clause 8.1 | Yes | cpc-values to use. | +| | | | No | | +| 3 | Originating Line Information ("oli" tel URI parameter) | clause 8.1 | Yes | oli-values to use. | +| | | | No | | + +NOTE: The option item is only for the non-roaming II-NNI. + +**Table C.3.3.8: Additional functions** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|-----------------------------------------|------------------------------|-----------------------------|-----------------------------| +| 1 | Support of out-of-dialog OPTIONS method | table 6.1/12
table 6.1/13 | Yes | The purpose of the method. | +| | | | No | | + +**Table C.3.3.9: IMS emergency session traversal scenario** + +| No. | Option item | References | Applicability at the II-NNI | Details for operator choice | +|-----|------------------------------------------------------|------------------------------------------------|-----------------------------|---------------------------------------------------------------| +| 1 | IMS emergency session traversal scenario | table 6.1.3.1/55
clause 30.1
clause 30.2 | Yes | The emergency service URN(s) to use. | +| | | | | The PSAP URI to use in the Route header field, if applicable. | +| | | | No | | +| 2 | Next-Generation Pan-European eCall emergency service | clause 30.3 | Yes | | +| | | | No | | + +# --- Annex D (informative): Change history + +| Change history | | | | | | | | +|-----------------------|--------------|-----------------|-----------|------------|-----------------------------------------------------------------------------------------------------|------------|------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 03/2015 | CT-67 | CP-150129 | 736 | 1 | Addition of an optional capability regarding a new cause-param value for service number translation | 12.7.0 | 13.0.0 | +| 03/2015 | CT-67 | CP-150130 | 719 | | Correction of a minor error in subclause C.3.1 | 12.7.0 | 13.0.0 | +| 03/2015 | CT-67 | CP-150130 | 723 | | Annex A corrections | 12.7.0 | 13.0.0 | +| 03/2015 | CT-67 | CP-150130 | 726 | 3 | Applying drafting rules | 12.7.0 | 13.0.0 | +| 03/2015 | CT-67 | CP-150130 | 729 | 1 | Adding missing abbreviations | 12.7.0 | 13.0.0 | +| 06/2015 | CT-68 | CP-150339 | 0741 | - | Reference Update: RFC 7462 (alert-info urns) | 13.0.0 | 13.1.0 | +| 06/2015 | CT-68 | CP-150341 | 0746 | - | Condition on usage of Refer-Sub header field | 13.0.0 | 13.1.0 | +| 06/2015 | CT-68 | CP-150356 | 0747 | 3 | Introducing resource sharing | 13.0.0 | 13.1.0 | +| 06/2015 | CT-68 | CP-150346 | 0749 | 1 | Correcting errors in annex B | 13.0.0 | 13.1.0 | +| 06/2015 | CT-68 | CP-150347 | 0751 | - | draft-holmberg-dispatch-iotl-parameter-04 updated to RFC 7549 | 13.0.0 | 13.1.0 | +| 06/2015 | CT-68 | CP-150350 | 0753 | 1 | Additional RFC 6665 related IETF drafts added | 13.0.0 | 13.1.0 | +| 06/2015 | CT-68 | CP-150357 | 0754 | 1 | Correcting inconsistencies in the major capability table | 13.0.0 | 13.1.0 | +| 06/2015 | CT-68 | CP-150364 | 0756 | 1 | Correction of Record-Route header field applicability in annex B | 13.0.0 | 13.1.0 | +| 06/2015 | CT-68 | CP-150364 | 0758 | - | Correction of applicable SIP status code for SIP header fields in PUBLISH response in annex B | 13.0.0 | 13.1.0 | +| 06/2015 | CT-68 | CP-150364 | 0760 | - | Addition of missing text referring to an option item table in annex C | 13.0.0 | 13.1.0 | +| 06/2015 | CT-68 | CP-150364 | 0762 | 1 | Correction of the P-Charging-Vector header field in annex B | 13.0.0 | 13.1.0 | +| 06/2015 | CT-68 | CP-150364 | 0763 | 1 | Correction of the P-Early-Media header field within the PRACK response in annex B | 13.0.0 | 13.1.0 | +| 06/2015 | CT-68 | CP-150364 | 0765 | - | Correction of the Server header field within the SUBSCRIBE response in annex B | 13.0.0 | 13.1.0 | +| 06/2015 | CT-68 | CP-150364 | 0766 | - | Correction of the Allow header field in annex B | 13.0.0 | 13.1.0 | +| 06/2015 | CT-68 | CP-150364 | 0767 | - | Clarifications on NNI impacts due to CAT service | 13.0.0 | 13.1.0 | +| 06/2015 | - | - | - | - | MCC Correction of implementation of CR0765 | 13.1.0 | 13.1.1 | +| 09/2015 | CT-69 | CP-150486 | 0768 | 3 | The privacy level "session" and "critical" are not used in OIP/OIR | 13.1.1 | 13.2.0 | +| 09/2015 | CT-69 | CP-150479 | 0769 | 1 | Service access number translation | 13.1.1 | 13.2.0 | +| 09/2015 | CT-69 | CP-150471 | 0771 | 1 | Reference update: draft-ietf-mmusic-sctp-sdp | 13.1.1 | 13.2.0 | +| 09/2015 | CT-69 | CP-150475 | 0773 | - | Missing SIP request in HSS based P-CSCF restoration | 13.1.1 | 13.2.0 | +| 09/2015 | CT-69 | CP-150479 | 0774 | - | draft-mohali-dispatch-cause-for-service-number updated to latest version | 13.1.1 | 13.2.0 | +| 09/2015 | CT-69 | CP-150486 | 0775 | 1 | The Service-Interact-Info header field | 13.1.1 | 13.2.0 | +| 09/2015 | CT-69 | CP-150478 | 0776 | 1 | Plain text message body missing in table 6.1.4.1 | 13.1.1 | 13.2.0 | +| 09/2015 | CT-69 | CP-150478 | 0777 | 1 | application/x-www-form-urlencoded missing in table 6.1.4.1 | 13.1.1 | 13.2.0 | +| 09/2015 | CT-69 | CP-150486 | 0778 | 1 | application/vnd.3gpp.crs+xml MIME body missing in CRS | 13.1.1 | 13.2.0 | +| 09/2015 | CT-69 | CP-150478 | 0779 | - | message/sip MIME body missing in table 6.1.4.1 | 13.1.1 | 13.2.0 | +| 09/2015 | CT-69 | CP-150478 | 0780 | - | Applicability of SIP header fields on a roaming II-NNI | 13.1.1 | 13.2.0 | +| 09/2015 | CT-69 | CP-150469 | 0783 | - | Reference update: RFC 7415 | 13.1.1 | 13.2.0 | +| 09/2015 | CT-69 | CP-150465 | 0787 | 1 | Correction for the II-NNI conditions | 13.1.1 | 13.2.0 | +| 12/2015 | CT-70 | CP-150796 | 0790 | 2 | Clarification on the II-NNI specifications of announcement | 13.2.0 | 13.3.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|--------------------------------------------------------------------|--------|--------| +| 12/2015 | CT-70 | CP-150796 | 0791 | 2 | Updating for annex B | 13.2.0 | 13.3.0 | +| 12/2015 | CT-70 | CP-150654 | 0795 | - | Telepresence IETF draft update | 13.2.0 | 13.3.0 | +| 12/2015 | CT-70 | CP-150659 | 0796 | 3 | Introducing MCPTT | 13.2.0 | 13.3.0 | +| 12/2015 | CT-70 | CP-150657 | 0797 | 2 | Reference update of draft-mohali-dispatch-cause-for-service-number | 13.2.0 | 13.3.0 | +| 12/2015 | CT-70 | CP-150664 | 0800 | 2 | Adding the "loopback-indication" to RAVEL | 13.2.0 | 13.3.0 | +| 12/2015 | CT-70 | CP-150731 | 0804 | 1 | ICS and the conference service | 13.2.0 | 13.3.0 | +| 12/2015 | CT-70 | CP-150660 | 0805 | - | SRVCC and subscription to conference package | 13.2.0 | 13.3.0 | +| 12/2015 | CT-70 | CP-150660 | 0806 | 1 | ICS and subscription to conference package | 13.2.0 | 13.3.0 | +| 12/2015 | CT-70 | CP-150656 | 0807 | 1 | Clarification of applicable URI formats for public user identity | 13.2.0 | 13.3.0 | +| 12/2015 | CT-70 | CP-150796 | 0808 | - | Miscellaneous editorial modification | 13.2.0 | 13.3.0 | +| 12/2015 | CT-70 | CP-150671 | 0810 | 1 | Update of UP6665 references | 13.2.0 | 13.3.0 | +| 12/2015 | CT-70 | CP-150662 | 0812 | 1 | P-CSCF restoration corrections | 13.2.0 | 13.3.0 | + +## Change history + +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +|---------|-------|-----------|------|-----|-----|-------------------------------------------------------------------------------------------------------|--------| +| 03/2016 | CT-71 | CP-160088 | 0813 | 2 | B | Adding MBMS usage info and location info procedure | 13.4.0 | +| 03/2016 | CT-71 | CP-160088 | 0814 | 2 | F | Adding "application/vnd.3gpp.mcptt-info" MIME body | 13.4.0 | +| 03/2016 | CT-71 | CP-160088 | 0815 | 2 | B | Adding MCPTT as option item in annex C | 13.4.0 | +| 03/2016 | CT-71 | CP-160088 | 0816 | 1 | B | Adding affiliation | 13.4.0 | +| 03/2016 | CT-71 | CP-160098 | 0817 | 1 | F | Adding "Timer N" in the timer table | 13.4.0 | +| 03/2016 | CT-71 | CP-160096 | 0819 | 1 | A | Updating "Details for operator choice" in DRVCC to include the STN | 13.4.0 | +| 03/2016 | CT-71 | CP-160088 | 0821 | 1 | F | Addressed MCPTT SIP interfaces | 13.4.0 | +| 06/2016 | CT-72 | CP-160262 | 0822 | 2 | F | Some error corrections and removing an editor's note | 13.5.0 | +| 06/2016 | CT-72 | CP-160262 | 0823 | 2 | F | Group regrouping | 13.5.0 | +| 06/2016 | CT-72 | CP-160262 | 0824 | 1 | F | Conference event package subscription | 13.5.0 | +| 06/2016 | CT-72 | CP-160262 | 0825 | 1 | F | MCPTT service settings | 13.5.0 | +| 06/2016 | CT-72 | CP-160262 | 0826 | - | F | Clarifying the Accept-Contact header field in MBMS usage info | 13.5.0 | +| 06/2016 | CT-72 | CP-160262 | 0827 | 2 | F | The affiliation procedure update | 13.5.0 | +| 06/2016 | CT-72 | CP-160259 | 0828 | 1 | F | Adding the Cellular-Network-Info header field | 13.5.0 | +| 06/2016 | CT-72 | CP-160258 | 0834 | 1 | A | Adding draft-mohali-dispatch-originating-cdiv-parameter | 13.5.0 | +| 06/2016 | CT-72 | CP-160258 | 0840 | 1 | A | Updates to RFC 7315 P-header extensions usage in SIP requests/responses | 13.5.0 | +| 06/2016 | CT-72 | CP-160258 | 0843 | 1 | A | P-Access-Network-Info ABNF Update | 13.5.0 | +| 06/2016 | CT-72 | CP-160261 | 0844 | 1 | F | Update ref to draft-mohali-dispatch-cause-for-service-number-06 | 13.5.0 | +| 06/2016 | CT-72 | CP-160273 | 0830 | 1 | F | Clarification of the note about forking | 14.0.0 | +| 06/2016 | CT-72 | CP-160273 | 0831 | - | F | Changing content type to correct terminology | 14.0.0 | +| 06/2016 | CT-72 | CP-160273 | 0835 | 1 | F | Clarification of Public Service Identity at II-NNI | 14.0.0 | +| 06/2016 | CT-72 | CP-160273 | 0836 | 1 | F | Correcting the subscription to the conference package for CONF and the session-mode messaging service | 14.0.0 | +| 06/2016 | CT-72 | CP-160273 | 0837 | 1 | F | Clarification on the applicability of P-Early-Media header field and early media over the II-NNI | 14.0.0 | +| 09/2016 | CT-73 | CP-160446 | 0846 | 1 | A | Usage of the Resource-Share header field | 14.1.0 | +| 09/2016 | CT-73 | CP-160447 | 0852 | 1 | A | Reference update: RFC 7913 | 14.1.0 | +| 09/2016 | CT-73 | CP-160449 | 0855 | 1 | A | Updated ref to draft-mohali-dispatch-cause-for-service-number-07 | 14.1.0 | +| 12/2016 | CT-74 | CP-160624 | 0857 | 1 | A | Updated ref to draft-mohali-dispatch-cause-for-service-number-09 | 14.2.0 | +| 12/2016 | CT-74 | CP-160620 | 0861 | 1 | A | Updated ref to draft-mohali-dispatch-originating-cdiv-parameter-02 | 14.2.0 | +| 12/2016 | CT-74 | CP-160620 | 0865 | - | A | Reference update: RFC 7976 | 14.2.0 | +| 12/2016 | CT-74 | CP-160621 | 0875 | - | A | Reference update: RFC 7989 | 14.2.0 | +| 12/2016 | CT-74 | CP-160623 | 0877 | 2 | A | Missing support of priority sharing | 14.2.0 | +| 12/2016 | CT-74 | CP-160631 | 0878 | - | F | Additional routing functionality at the IBCF | 14.2.0 | +| 03/2017 | CT-75 | CP-170087 | 0882 | 1 | A | Correction on PSAP callback indicator option item | 14.3.0 | +| 03/2017 | CT-75 | CP-170087 | 0883 | 1 | A | Correction on the architecture diagram of II-NNI | 14.3.0 | +| 03/2017 | CT-75 | CP-170087 | 0884 | 1 | A | Addition of application/call-completion MIME Type | 14.3.0 | +| 03/2017 | CT-75 | CP-170080 | 0886 | 1 | A | Update ref to draft-mohali-dispatch-cause-for-service-number | 14.3.0 | +| 03/2017 | CT-75 | CP-170078 | 0890 | 2 | A | Update ref to draft-mohali-dispatch-originating-cdiv-parameter | 14.3.0 | +| 03/2017 | CT-75 | CP-170079 | 0894 | - | A | Reference update: RFC 8055 | 14.3.0 | +| 03/2017 | CT-75 | CP-170077 | 0896 | - | A | Applicability of Resource-Share header field | 14.3.0 | +| 03/2017 | CT-75 | CP-170085 | 0897 | 1 | B | Support of "Calling number verification" | 14.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|---------------------------------------------------------------------------------------------|--------| +| 06/2017 | CT-76 | CP-171134 | 0872 | 5 | F | Clarification of II-NNI for IMS emergency session | 14.4.0 | +| 06/2017 | CT-76 | CP-171130 | 0898 | 2 | B | Addition of the location parameter | 14.4.0 | +| 06/2017 | CT-76 | CP-171128 | 0900 | - | A | MIME body types used by MCPTT | 14.4.0 | +| 06/2017 | CT-76 | CP-171126 | 0901 | - | F | Modifying references to align with rel-14 MCPTT stage 1 and stage 2 restructuring | 14.4.0 | +| 06/2017 | CT-76 | CP-171134 | 0902 | 1 | F | Missing support of Response-Source header field | 14.4.0 | +| 06/2017 | CT-76 | CP-171124 | 0904 | 1 | A | Reference Update RFC8119 | 14.4.0 | +| 06/2017 | CT-76 | CP-171123 | 0908 | 1 | A | Update ref to new naming of draft-mohali-sipcore-originating-cdiv-parameter | 14.4.0 | +| 06/2017 | CT-76 | CP-171131 | 0909 | 2 | F | Support of feature capability indicator "sip.607" | 14.4.0 | +| 06/2017 | CT-76 | CP-171122 | 0913 | - | A | Reference update: draft-ietf-mmusic-sctp-sdp | 14.4.0 | +| 06/2017 | CT-76 | CP-171131 | 0914 | - | F | Reference update: draft-ietf-stir-rfc4474bis | 14.4.0 | +| 06/2017 | CT-76 | CP-171125 | 0915 | 3 | B | IMS Trace (ISAT) Procedures | 14.4.0 | +| 06/2017 | CT-76 | CP-171127 | 0916 | 3 | B | Adding other Mission Critical services | 14.4.0 | +| 06/2017 | CT-76 | CP-171135 | 0910 | 1 | F | Added unspecified abbreviations | 15.0.0 | +| 06/2017 | CT-76 | CP-171135 | 0918 | 2 | F | Misalignment regarding transcoding between TS 24.229 and TS 29.165 | 15.0.0 | +| 06/2017 | CT-76 | | | | | Editorial changes by MCC | 15.0.1 | +| 09/2017 | CT-77 | CP-172049 | 0919 | 1 | A | Added the profile status in proxy role regarding "A SIP Response Code for Unwanted Calls" | 15.1.0 | +| 09/2017 | CT-77 | CP-172040 | 0920 | 1 | B | Support of IETF draft-ietf-sipcore-content-id | 15.1.0 | +| 09/2017 | CT-77 | CP-172045 | 0922 | 1 | A | Reference Update for the ISUP location parameter | 15.1.0 | +| 09/2017 | CT-77 | CP-172049 | 0925 | - | A | Reference update from draft-ietf-sipcore-status-unwanted-06 to RFC 8197 | 15.1.0 | +| 12/2017 | CT-78 | CP-173099 | 0928 | 1 | A | Reference Update for the ISUP location parameter | 15.2.0 | +| 12/2017 | CT-78 | CP-173091 | 0933 | 1 | A | Update draft ref for Originating-CDIV param in P-Served-User | 15.2.0 | +| 12/2017 | CT-78 | CP-173090 | 0934 | - | D | Editorial modification | 15.2.0 | +| 12/2017 | CT-78 | CP-173095 | 0935 | 1 | A | Adding MCData related MIME bodies | 15.2.0 | +| 12/2017 | CT-78 | CP-173098 | 0938 | 1 | A | Correction of II-NNI condition related to P-Early-Media header field | 15.2.0 | +| 12/2017 | CT-78 | CP-173102 | 0940 | - | A | Correction of II-NNI condition related to P-Early-Media header field for the UPDATE request | 15.2.0 | +| 12/2017 | CT-78 | CP-173096 | 0943 | - | A | Addition of sign XML MIME body | 15.2.0 | +| 12/2017 | CT-78 | CP-173092 | 0945 | - | F | Reference update: RFC 8262 | 15.2.0 | +| 03/2018 | CT-79 | CP-180038 | 0946 | 1 | B | Support of "Enhanced calling name" service | 15.3.0 | +| 03/2018 | CT-79 | CP-180048 | 0947 | - | F | bSRVCC-MT NNI | 15.3.0 | +| 03/2018 | CT-79 | CP-180048 | 0948 | 1 | F | Operator choice of DTMF sampling rate | 15.3.0 | +| 03/2018 | CT-79 | CP-180042 | 0950 | - | A | Reference Update for the ISUP location parameter | 15.3.0 | +| 03/2018 | CT-79 | CP-180048 | 0951 | - | F | Updating the title of referenced TS 22.179 | 15.3.0 | +| 03/2018 | CT-79 | CP-180044 | 0953 | - | A | Reference update: RFC 8224 | 15.3.0 | +| 03/2018 | CT-79 | CP-180048 | 0955 | - | F | Correction on the terminology of non-global number | 15.3.0 | +| 03/2018 | CT-79 | CP-180048 | 0956 | - | F | Correction of the option item name for Calling number verification | 15.3.0 | +| 03/2018 | CT-79 | CP-180048 | 0957 | 1 | F | Operator choice of CAT media type | 15.3.0 | +| 06/2018 | CT-80 | CP-181022 | 0958 | 1 | F | Missing explanation of abbreviation "5xx" | 15.4.0 | +| 06/2018 | CT-80 | CP-181016 | 0959 | 1 | B | Calling number verification using signature verification and attestation information | 15.4.0 | +| 06/2018 | CT-80 | CP-181170 | 0960 | 4 | F | MBMS transmission and location procedures for MCVideo service | 15.4.0 | +| 09/2018 | CT-81 | CP-182021 | 0961 | 1 | B | Functional Alias Management over II-NNI | 15.5.0 | +| 09/2018 | CT-81 | CP-182020 | 0966 | 1 | A | Update draft ref for Originating-CDIV param in P-Served-User | 15.5.0 | +| 09/2018 | CT-81 | CP-182018 | 0967 | 1 | F | Correction of NOTE numbering for trust relationship | 15.5.0 | +| 09/2018 | CT-81 | CP-182024 | 0969 | - | A | Reference Update for the ISUP Q.850 location parameter | 15.5.0 | +| 12/2018 | CT-82 | CP-183113 | 0974 | 2 | A | Update draft ref for Originating-CDIV param in P-Served-User | 15.6.0 | +| 12/2018 | CT-82 | CP-183114 | 0977 | 1 | A | Removal of editor's note on Service-Interact-Info | 15.6.0 | +| 12/2018 | CT-82 | CP-183111 | 0978 | - | F | Support of Origination-Id in INVITE and MESSAGE methods | 15.6.0 | +| 03/2019 | CT-83 | CP-190124 | 0980 | 2 | A | References update for ISAT after related RFC completed in IETF | 15.7.0 | +| 03/2019 | CT-83 | CP-190126 | 0982 | 2 | A | Reference Update for the ISUP Cause Location Parameter Draft | 15.7.0 | +| 03/2019 | CT-83 | CP-190123 | 0988 | 1 | A | P-Served-User case orig-cdiv is now RFC 8498 | 15.7.0 | +| 06/2019 | CT#84 | CP-191094 | 0989 | - | A | Reference Update for the ISUP Cause Location Parameter Draft | 15.8.0 | +| 09/2019 | CT#85 | CP-192166 | 0992 | 1 | A | Reference Update RFC8606 | 15.9.0 | +| 09/2019 | CT#85 | CP-192174 | 0990 | 3 | F | Clarification of the usage restriction of P-Asserted-Identity header field over the II-NNI. | 16.0.0 | +| 09/2019 | CT#85 | CP-192162 | 0993 | 1 | B | Support of "Multi-Device" and "Multi-Identity" services | 16.0.0 | +| 12/2019 | CT#86 | CP-193190 | 0995 | 2 | A | P-CSCF restoration in 5GS | 16.1.0 | +| 12/2019 | CT#86 | CP-193205 | 0996 | - | B | Additional-Identity header in REFER request | 16.1.0 | +| 12/2019 | CT#86 | CP-193207 | 1004 | 1 | A | Correction for setting condition of the Contact header field | 16.1.0 | +| 03/2020 | CT#87e | CP-200229 | 1005 | 2 | F | Clarification of the scope | 16.2.0 | +| 06/2020 | CT#88e | CP-201329 | 1006 | - | F | Corrections on the II-NNI specifications on the P-Charging-Vector header field | 16.3.0 | +| 06/2020 | CT#88e | CP-201240 | 1007 | 1 | F | Re-structure of subclause for MuD/MiD service | 16.3.0 | +| 06/2020 | CT#88e | CP-201242 | 1008 | 1 | F | Adding the RLOS requirements over the II-NNI | 16.3.0 | + +| | | | | | | | | +|---------|--------|-----------|------|---|---|----------------------------------------------------------------------------------------------------|--------| +| 09/2020 | CT#89e | CP-202076 | 1011 | 1 | A | Addition of missing capability | 16.4.0 | +| 09/2020 | CT#89e | CP-202075 | 1015 | - | A | Support of P-Charging-Vector header field in BYE and PRACK | 16.4.0 | +| 03/2021 | CT#91e | CP-210242 | 1022 | - | A | Reference update: RFC 8841 | 16.5.0 | +| 06/2021 | CT#92e | CP-211236 | 1025 | - | F | IMS data channel at the II-NNI | 16.6.0 | +| 06/2021 | CT#92e | CP-211222 | 1027 | - | A | Correction on Calling number verification using signature verification and attestation information | 16.6.0 | \ No newline at end of file diff --git a/marked/Rel-16/29_series/29172/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg b/marked/Rel-16/29_series/29172/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6648febc14d88296d928b085cb791af7dcf974e --- /dev/null +++ b/marked/Rel-16/29_series/29172/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93b52b7caafb39f72b5c7e3adec2185e5b23ec6d1c8dbd39673cf98dff67d504 +size 25513 diff --git a/marked/Rel-16/29_series/29172/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/29_series/29172/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d62fb9f2dea78b74524d9301ee4021c7cca0970b --- /dev/null +++ b/marked/Rel-16/29_series/29172/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:176c6929fece56407c1bc1055374a5c55ba34962b286a77ad06cd2b5b077f506 +size 9559 diff --git a/marked/Rel-16/29_series/29172/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/29_series/29172/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13bd11f13e0de2a9e992e881e76d9f7d1e8c31ca --- /dev/null +++ b/marked/Rel-16/29_series/29172/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78de62cf823141a76827a75c01d833e800b88bea4a70d465ab4ab8a7f28faee2 +size 6383 diff --git a/marked/Rel-16/29_series/29172/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/marked/Rel-16/29_series/29172/78ffccd66df9bafd96e3e081110d09dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81c54eb854bf7f1783fe146e56488c3d5c3c7714 --- /dev/null +++ b/marked/Rel-16/29_series/29172/78ffccd66df9bafd96e3e081110d09dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c83d6e16e619939b47e5aeab6a13843e7bc0a721c40c35a2f35ff813646587c +size 26510 diff --git a/marked/Rel-16/29_series/29172/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Rel-16/29_series/29172/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..128b14d8f79b4cd66d687fd22a17c3e55525d74a --- /dev/null +++ b/marked/Rel-16/29_series/29172/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a78b15f2c4ecbfc5bc1a23cde8067937c20ac49b6b8bb0764ec8ca1413c93124 +size 27049 diff --git a/marked/Rel-16/29_series/29172/b0d4609bc46c2d88a8318706bb5321f7_img.jpg b/marked/Rel-16/29_series/29172/b0d4609bc46c2d88a8318706bb5321f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3abe676053badf35ba4b017e1cae68d1c804959 --- /dev/null +++ b/marked/Rel-16/29_series/29172/b0d4609bc46c2d88a8318706bb5321f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e2afc431787cd1b0b86750c6bd1422bd13a2e22f16844888827b255f90c4106 +size 25040 diff --git a/marked/Rel-16/29_series/29172/raw.md b/marked/Rel-16/29_series/29172/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7a1325294351818ce9f2ab8aa3b35c135de57dfc --- /dev/null +++ b/marked/Rel-16/29_series/29172/raw.md @@ -0,0 +1,1688 @@ + + +# 3GPP TS 29.172 V16.1.0 (2022-03) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Location Services (LCS); Evolved Packet Core (EPC) LCS Protocol (ELP) between the Gateway Mobile Location Centre (GMLC) and the Mobile Management Entity (MME); SLg interface (Release 16)** + + + +The logo for LTE Advanced Pro, featuring the word "lte" in black with a green signal icon above the "t", and the words "Advanced Pro" in red and green to the right. + +LTE Advanced Pro logo + + + +The 3GPP logo, consisting of the letters "3GPP" in a stylized black font with a red signal icon below the "P", and the text "A GLOBAL INITIATIVE" in small black letters below it. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + +
NOTE: this value is only applicable to a deferred EPC-MT-LR. | +| LCS-Reference Number | LCS-Reference-Number | O | If present, this Information Element shall contain the reference number identifying the deferred location request or identifying the request for which delayed location reporting for UEs transiently not reachable is supported. This Information Element is applicable only when:
- the deferred MT-LR procedure is initiated; or
- an EPC-MT-LR or PS-MT-LR procedure is initiated and the message includes the indication that delayed location reporting for UEs transiently not reachable is supported. | +| Area Event Info | Area-Event-Info | O | If present, this Information Element shall contain area definition, type of area event, occurrence info and minimum interval time. For a deferred EPC-MT-LR, this Information Element may also contain the duration of event reporting, the maximum time interval between event reports, the maximum event sampling interval, and whether location | + +| | | | | +|--------------------------------------------------------------------|--------------------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | estimates shall be included in event reports. This Information Element is applicable only when the deferred MT-LR is initiated for the area event (UE entering or leaving or being in a pre-defined geographical area). | +| H-GMLC Address | GMLC-Address | O | If present, this Information Element shall contain the address identifying the H-GMLC which initiated the deferred MT-LR procedure. This Information Element is applicable only when the deferred MT-LR procedure is performed. | +| PLR Flags | PLR-Flags | O | This Information Element contains a bit mask. See 7.4.52 for the meaning of the bits. | +| Periodic LDR Information | Periodic-LDR-Information | O | If present, this Information Element shall contain reporting amount and reporting interval of deferred periodic location. This Information Element is applicable only when the deferred MT-LR procedure is initiated for the periodic location event. | +| Reporting PLMN List | Reporting-PLMN-List | O | If present, this Information Element shall contain a list of PLMNs in which the subsequent location estimates must be obtained, or the subsequent triggered or periodic events must be reported, by the UE as part of a periodic MO-LR TTTP or periodic MT-LR procedure. | +| Supported Features (See 3GPP TS 29.229 [17]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Motion Event Info | Motion-Event-Info | O | If present, this Information Element shall contain information for motion event reporting. This information includes the minimum linear distance for a motion event report, the duration of event reporting, the minimum and maximum time intervals between event reports, the maximum event sampling interval, whether location estimates shall be included in event reports, and whether only one location report is required or more than one. This Information Element is applicable only for a deferred EPC-MT-LR. | +| NOTE 1: At least one of these IEs shall be present in the message. | | | | + +Table 6.2.2-2: Provide Subscriber Location Answer + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|-------------------------------|-----------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M | This Information Element shall contain the result of the operation. The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [23]). The Experimental-Result AVP shall be used for ELP errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| Location Estimate | Location-Estimate | O | If present, this Information Element shall contain an estimate of the location of the UE in universal coordinates and the accuracy of the estimate.
This Information Element shall not be included if the PLA Flags Information Element is present and if the bit corresponding to the "UE-Transiently-Not-Reachable-Indicator" is set. | +| Accuracy Fulfilment Indicator | Accuracy-Fulfilment-Indicator | O | If present, this Information Element shall contain an indication of whether the requested accuracy (as indicated in the LCS-QoS IE in the request message) was fulfilled or not. | +| Age of Location Estimate | Age-of-Location-Estimate | O | If present, this Information Element shall contain an indication of how long ago the location estimate was obtained. | +| Velocity Estimate | Velocity-Estimate | O | If present, this Information Element shall contain an estimate of the velocity of the target UE, composed by horizontal speed, vertical speed, and their respective uncertainty (see 3GPP TS 23.032 [3]). | +| EUTRAN Positioning Data | EUTRAN-Positioning-Data | O | If present, this Information Element shall indicate the usage of each positioning method that was attempted to determine the location estimate, either successfully or unsuccessfully. The internal structure and encoding is defined in 3GPP TS 29.171 [7]. This Information Element is applicable only when the UE is attached to E-UTRAN access and when the message is sent by the MME or the combined MME/SGSN. | +| ECGI | ECGI | O | If present, this Information Element shall contain the current cell location of the target UE as delivered by the eNB to the MME. The E-UTRAN Cell Global Identifier (ECGI) is used to globally identify a cell. This Information Element is applicable only when the UE is attached to E-UTRAN access and when the message is sent by the MME or combined MME/SGSN. | +| GERAN Positioning Info | GERAN-Positioning-Info | O | If present, this Information Element shall indicate the usage of each positioning method that was attempted to determine the location estimate, either successfully or unsuccessfully. This Information Element is applicable only when the UE is attached to GERAN access and when the message is sent by the SGSN or combined MME/SGSN. | +| CGI | Cell-Global-Identity | O | If present, this Information Element shall contain the current cell location of the target UE. The Cell Global Identifier (CGI) is used to globally identify a cell. This Information Element is applicable only when the UE is attached to GERAN access and when the message is sent by the SGSN or combined MME/SGSN. | +| UTRAN Positioning Info | UTRAN-Positioning-Info | O | If present, this Information Element shall indicate the usage of each positioning method that was attempted to determine the location estimate, either successfully or unsuccessfully. This Information Element is applicable only when the UE is attached to UTRAN access and when the message is sent by the SGSN or combined MME/SGSN. | +| SAI | Service-Area-Identity | O | If present, this Information Element shall contain the current service area of the target UE. The Service Area Identifier (SAI) is used to globally identify a service area. This Information Element is applicable only when the UE is attached to UTRAN access and when the message is sent by the SGSN or combined MME/SGSN. | +| Target Serving Node Identity | Serving-Node | O | If present, this information element shall contain the address of the target side serving node for handover of an IMS Emergency Call. | +| PLA Flags | PLA-Flags | O | This Information Element contains a bit mask. See 7.4.53 for the meaning of the bits.
If this Information Element is present and if the bit corresponding to the "Deferred-MT-LR-Response-Indicator" is set, the "Location-Estimate" Information Element is ignored in this message. | + +| | | | | +|----------------------------------------------|---------------------|---|----------------------------------------------------------------------------------------------------------------------| +| E-SMLC provided Cell Info | ESMLC-Cell-Info | O | If present, this Information Element shall contain the current cell information of the target UE as known by E-SMLC. | +| Civic Address | Civic-Address | O | If present, this Information Element contains a location estimate for the target UE expressed as a Civic address. | +| Barometric Pressure | Barometric-Pressure | O | If present, this Information Element contains the barometric pressure measurement as reported by the target UE. | +| Supported Features (See 3GPP TS 29.229 [17]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +### 6.2.3 Unsuccessful Operation + +On receipt of a PROVIDE SUBSCRIBER LOCATION RESPONSE with a Result-Code or Experimental-Result AVP indicating failure the GMLC considers the positioning request as failed. + +If the GMLC receives "Optimized-LCS-Proc-Performed" bit within PLA-Flags set, it shall assume that the combined MME/SGSN has either performed EPC-MT-LR or PS-MT-LR procedure to retrieve the location of the target UE. And hence, it need not send another PROVIDE SUBSCRIBER LOCATION REQUEST message to the combined MME/SGSN. + +## 6.3 Subscriber Location Report + +### 6.3.1 General + +The Subscriber Location Report operation is used by an MME or SGSN to provide the location of a target UE to a GMLC, when a request for location has been implicitly issued or when a Delayed Location Reporting is triggered after receipt of a request for location for a UE transiently not reachable. + +### 6.3.2 Successful Operation + + + +``` + +sequenceDiagram + participant MME/SGSN + participant GMLC + Note left of MME/SGSN: + MME/SGSN->>GMLC: SUBSCRIBER LOCATION REPORT + Note right of GMLC: + GMLC-->>MME/SGSN: SUBSCRIBER LOCATION REPORT ACK + Note left of MME/SGSN: + +``` + +Sequence diagram showing the successful operation of the Subscriber Location Report procedure. The MME/SGSN sends a SUBSCRIBER LOCATION REPORT message to the GMLC, and the GMLC responds with a SUBSCRIBER LOCATION REPORT ACK message. + +**Figure 6.3.2-1: Subscriber Location Report procedure. Successful operation.** + +The MME or SGSN initiates the procedure by sending a SUBSCRIBER LOCATION REPORT message to the GMLC. The message may carry the identity of the UE, the location estimate and its age, and the event causing the location report. + +Upon reception of SUBSCRIBER LOCATION REPORT message, the GMLC shall return a SUBSCRIBER LOCATION REPORT ACK to the MME or SGSN and process the location report accordingly, e.g. transfer of the location estimate to an external LCS Client according to procedure described in 3GPP TS 23.271 [2]. + +If the Location-Event indicates a DEFERRED\_LR\_RESPONSE then the Location-Estimate shall not be sent if the LCS-Supported-GAD-Shapes had been received in Provide Subscriber Location request and the shape encoded in Location-Estimate was not marked as supported in LCS-Supported-GAD-Shapes. In such a case Termination-Cause in Deferred-MT-LR-Data shall be present with value SHAPE\_OF\_LOCATION\_ESTIMATE\_NOT\_SUPPORTED. + +This procedure is mapped to the commands Location-Report-Request/Answer in the Diameter application specified in clauses 7.3.3 and 7.3.4. + +Table 6.3.2-1: Subscriber Location Report + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|-------------------------------|-------------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location Event | Location-Event | M | This Information Element shall contain the type of event that caused the location procedure to be initiated. | +| IMSI | User-Name | C | If present, this Information Element shall contain the IMSI of the user whose UE is to be positioned (see Note 1). | +| MSISDN | MSISDN | C | If present, this Information Element shall contain the MSISDN of the user whose UE is to be positioned (see Note 1). | +| IMEI | IMEI | C | If present, this Information Element shall contain the IMEI of the UE to be positioned (see Note 1). | +| Client Name | LCS-EPS-Client-Name | O | If present, this Information Element shall contain the name of the LCS client where the result of the positioning operation should be sent. | +| Location Estimate | Location-Estimate | O | If present, this Information Element shall contain an estimate of the location of the UE in universal coordinates and the accuracy of the estimate. | +| Accuracy Fulfilment Indicator | Accuracy-Fulfilment-Indicator | O | If present, this Information Element shall contain an indication of whether the requested accuracy was fulfilled or not. | +| Age of Location Estimate | Age-of-Location-Estimate | O | If present, this Information Element shall contain an indication of how long ago the location estimate was obtained. | +| Velocity Estimate | Velocity-Estimate | O | If present, this Information Element shall contain an estimate of the velocity of the UE, composed by horizontal speed, vertical speed, and their respective uncertainty (see 3GPP TS 23.032 [3]). | +| EUTRAN Positioning Data | EUTRAN-Positioning-Data | O | If present, this Information Element shall indicate the usage of each positioning method that was attempted to determine the location estimate, either successfully or unsuccessfully. The internal structure and encoding is defined in 3GPP TS 29.171 [7]. This Information Element is applicable only when the UE is attached to E-UTRAN access and when the message is sent by the MME or the MME part of the combined MME/SGSN. | +| ECGI | ECGI | O | If present, this Information Element shall contain the current cell location of the target UE as delivered by the eNB to the MME. The E-UTRAN Cell Global Identifier (ECGI) is used to globally identify a cell. This Information Element is applicable only when the UE is attached to E-UTRAN access and when the message is sent by the MME or the MME part of the combined MME/SGSN. | +| GERAN Positioning Info | GERAN-Positioning-Info | O | If present, this Information Element shall indicate the usage of each positioning method that was attempted to determine the location estimate, either successfully or unsuccessfully. This Information Element is applicable only when the UE is attached to GERAN access and when the message is sent by the SGSN or the SGSN part of the combined MME/SGSN. | +| CGI | Cell-Global-Identity | O | If present, this Information Element shall contain the current cell location of the target UE. The Cell Global Identifier (CGI) is used to globally identify a cell. This Information Element is applicable only when the UE is attached to GERAN access and when the message is sent by the SGSN or the SGSN part of the combined MME/SGSN. | +| UTRAN Positioning Info | UTRAN-Positioning-Info | O | If present, this Information Element shall indicate the usage of each positioning method that was attempted to determine the location estimate, either successfully or unsuccessfully. This Information Element is applicable only when the UE is attached to UTRAN access and when the message is sent by the SGSN or the SGSN part of the combined MME/SGSN. | +| SAI | Service-Area-Identity | O | If present, this Information Element shall contain the current service area of the target UE. The Service Area Identifier (SAI) is used to globally identify a service area. This Information Element is applicable only when the UE is attached to UTRAN access and when the message is sent by the SGSN or the SGSN part of the combined MME/SGSN. | +| Service Type ID | LCS-Service-Type-ID | O | If present, this Information Element shall contain the service type associated for the particular positioning report identifying the service at the receiving LCS Client (the meaning of the different service types is defined in 3GPP TS 22.071 [15]). | +| Pseudonym Indicator | Pseudonym-Indicator | O | If present, this Information Element shall contain an indication of whether or not a pseudonym must be allocated by the network and | + +| | | | | +|-------------------------------------------------|---------------------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | transferred to the LCS client as the identity of the UE. | +| Supported Features
(See 3GPP TS 29.229 [17]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| LCS QoS Class | LCS-QoS-Class | O | If present, this Information Element shall contain the LCS-QoS-Class requested by the target UE. | +| Target Serving Node Identity | Serving-Node | O | If present, this information element shall contain the address of the target side serving node for handover of an IMS Emergency Call. | +| LRR Flags
(See 7.4.35) | LRR-Flags | C | This Information Element contains a bit mask. See 7.4.35 for the meaning of the bits.
It shall be present when the message is sent over Lgd interface. | +| LCS-Reference Number | LCS-Reference-Number | O | If present, this Information Element shall contain the reference number identifying the deferred location request or identifying the request for which Delayed Location Reporting is triggered. This is same as the reference number included in the Provide Subscriber Location request for the deferred MT-LR procedure or for the EPC-MT-LR or PS-MT-LR with the Delayed-Location-Reporting-Support indication, or the reference number included in the Subscriber Location Report Ack for periodic MO-LR TTTP procedure. This Information Element shall be included if the Location-Event is set to:
- "DEFERRED_MT_LR_RESPONSE"; or
- "DELAYED_LOCATION_REPORTING". | +| Deferred MT-LR Data | Deferred-MT-LR-Data | O | If present, this Information Element is used to report the deferred location event type, the location information and optionally a reason why the serving node or UE aborted monitoring the event to the GMLC. The deferred location event type may correspond to the location event type requested in the Provide Subscriber Location Request. For a deferred EPC-MT-LR, the deferred location event type may also indicate LDR activation in the UE or expiration of the maximum time interval between event reports. This Information Element shall be included when the Location-Event is set to "DEFERRED_MT_LR_RESPONSE". | +| H-GMLC Address | GMLC-Address | O | If present, this Information Element shall contain the address identifying the H-GMLC which should receive location estimates. This is the same as the H-GMLC address included in the Provide Subscriber Location request for the deferred MT-LR procedure or the H-GMLC address included in the Subscriber Location Report Ack for periodic MO-LR TTTP procedure. | +| Sequence Number | Reporting-Amount | O | If present, this parameter contains the number of the periodic location reports completed. The sequence number would be set to 1 in the first location report and increment by 1 for each new report. When the number reaches the reporting amount value, the H-GMLC (for a periodic MT-LR or a periodic MO-LR TTTP) will know the procedure is complete. This Information Element is applicable only when the message is sent by the SGSN or the SGSN part of the combined MME/SGSN. | +| Periodic LDR Information | Periodic-LDR-Information | O | If present, this Information Element shall contain the UE requested reporting amount and reporting interval of deferred periodic location reporting. This Information Element is applicable only when the periodic MO-LR TTTP procedure is initiated by the UE and when the message is sent by the SGSN or the SGSN part of the combined MME/SGSN. | +| E-SMLC provided Cell Info | ESMLC-Cell-Info | O | If present, this Information Element shall contain the current cell information of the target UE as known by E-SMLC. | +| 1xRTT Reference Cell ID | 1xRTT-RCID | O | If present, this Information Element shall contain the 1xRTT Reference Cell ID uniquely identifying of the target cell location for handover of an IMS emergency call. This Information Element is applicable only when the UE is making handover to a cdma2000 1xRTT access and when the message is sent by the MME or the MME part of the combined MME/SGSN. | +| Delayed Location Reporting Data | Delayed-Location-Reporting-Data | O | If present, this Information Element is used to report to the GMLC the reason why the serving node ended an earlier EPC-MT-LR or PS-MT-LR with the Delayed-Location-Reporting-Support indication received for a UE transiently not reachable.
This Information Element shall be included when the Location-Event is set to "DELAYED_LOCATION_REPORTING". | + +| | | | | +|--------------------------------------------------------------------|---------------------|---|-------------------------------------------------------------------------------------------------------------------| +| Civic Address | Civic-Address | O | If present, this Information Element contains a location estimate for the target UE expressed as a Civic address. | +| Barometric Pressure | Barometric-Pressure | O | If present, this Information Element contains the barometric pressure measurement as reported by the target UE. | +| NOTE 1: At least one of these IEs shall be present in the message. | | | | + +Table 6.3.2-2: Subscriber Location Report Ack + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|----------------------------------------------|-----------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result | Result-Code / Experimental-Result | M | This Information Element shall contain the result of the operation. The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [23]). The Experimental-Result AVP shall be used for ELP errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| H-GMLC Address | GMLC-Address | O | If present, this Information Element shall contain the address identifying the H-GMLC which should receive location estimates as part of periodic MO-LR TTTP procedure. This Information Element is applicable only when the message is sent towards the SGSN or the SGSN part of the combined MME/SGSN. | +| LRA Flags | LRA-Flags | O | This Information Element contains a bit mask. See 7.4.56 for the meaning of the bits. | +| Reporting PLMN List | Reporting-PLMN-List | O | If present, this Information Element shall contain a list of PLMNs in which the subsequent location estimates must be obtained as part of periodic MO-LR TTTP procedure. This Information Element is applicable only when the message is sent towards the SGSN or the SGSN part of the combined MME/SGSN. | +| LCS Reference Number | LCS-Reference-Number | O | If present, this Information Element shall contain the reference number identifying the deferred location request or identifying the request for which Delayed Location Reporting was triggered. This Information Element is applicable only when the message is sent towards the SGSN or the SGSN part of the combined MME/SGSN. | +| Supported Features (See 3GPP TS 29.229 [17]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +### 6.3.3 Unsuccessful Operation + +If for some reason the GMLC does not accept the SUBSCRIBER LOCATION REPORT APDU, the GMLC shall send a SUBSCRIBER LOCATION REPORT ACK message with a Result-Code or Experimental-Result AVP indicating failure. + +# 7 ELP Messages and Message Formats + +## 7.1 General + +The Diameter base protocol as specified in IETF RFC 6733 [23] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and error codes as specified in this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) shall be used unmodified. + +This clause specifies a Diameter application that allows a Diameter server and a Diameter client: + +- to retrieve the location information of a target UE +- to report the location information of a target UE + +The SLg/Lgd interface protocol is defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP (
This bit, when cleared, indicates that the Location Report Request message is sent on the SLg interface, i.e. the source node is an MME (or a combined MME/SGSN to which the UE is attached via E-UTRAN). | +| 1 | MO-LR-ShortCircuit-Indicator | This bit, when set, indicates that the MO-LR short circuit feature is used by the UE for location estimate. This bit is applicable only when for deferred MT-LR procedure and when the message is sent over Lgd interface. | +| 2 | MO-LR-ShortCircuit-Requested | This bit, when set, indicates that the UE is requesting to use MO-LR short circuit feature for location estimate. This bit is applicable only when periodic MO-LR TTTP procedure is initiated by the UE and when the message is sent over Lgd interface. | + +NOTE1: Bits not defined in this table shall be cleared by the sending MME or SGSN and discarded by the receiving GMLC. + +### 7.4.36 Deferred-Location-Type + +The Deferred-Location-Type AVP is of type Unsigned32 and it shall contain a bit mask. Each bit indicates a type of event, until when the location estimation is deferred. For details, please refer to 3GPP TS 23.271 [3] clause 4.4.2. The meaning of the bits shall be as defined in table 7.4.36/1: + +**Table 7.4.36/1: Deferred-Location-Type** + +| Bit | Event Type | Description | +|-----|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------| +| 0 | UE-Available | Any event in which the SGSN has established a contact with the UE. | +| 1 | Entering-Into-Area | An event where the UE enters a pre-defined geographical area. | +| 2 | Leaving-From-Area | An event where the UE leaves a pre-defined geographical area. | +| 3 | Being-Inside-Area | An event where the UE is currently within the pre-defined geographical area. | +| 4 | Periodic-LDR | An event where a defined periodic timer expires in the UE and activates a location report or a location request. | +| 5 | Motion-Event | An event where the UE moves by more than a minimum linear distance. This event is applicable to a deferred EPC-MT-LR only. | +| 6 | LDR-Activated | An event where deferred location reporting has been activated in the UE. This event is applicable to a deferred EPC-MT-LR only. | +| 7 | Maximum-Interval-Expiration | An event where the maximum reporting interval has expired. This event is applicable to a deferred EPC-MT-LR only. | + +### 7.4.37 LCS-Reference-Number + +The LCS-Reference-Number AVP is of type OctetString of length 1. It shall contain the reference number identifying the deferred location request. + +### 7.4.38 Area-Event-Info + +The Area-Event-Info AVP is of type Grouped. + +AVP format: + +``` +Area-Event-Info ::=
- receiving a PROVIDE SUBSCRIBER LOCATION RESPONSE with the UE-Transiently-Not-Reachable-Indicator set in the PLA-Flags IE; and
- receiving the location information in a subsequent SUBSCRIBER LOCATION REPORT when the UE becomes reachable. | + +NOTE1: Bits not defined in this table shall be cleared by the sending GMLC and discarded by the receiving MME or SGSN. + +### 7.4.53 PLA-Flags + +The PLA-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 7.4.53/1: + +**Table 7.4.53/1: PLA-Flags** + +| Bit | Name | Description | +|-----|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Deferred-MT-LR-Response-Indicator | This bit, when set, indicates that the message is sent in response to the deferred-MT location request. | +| 1 | MO-LR-ShortCircuit-Indicator | This bit, when set, indicates that the MO-LR short circuit feature is accepted by the UE, for periodic location reporting. This bit is applicable only when the message is sent over Lgd interface. | +| 2 | Optimized-LCS-Proc-Performed | This bit, when set, indicates that the combined MME/SGSN has performed the optimized LCS procedure to retrieve the location of the target UE. This bit is applicable only when the message is sent for the MT-LR procedure over the Lgd interface. | +| 3 | UE-Transiently-Not-Reachable-Indicator | This bit, when set, indicates that the UE is transiently not reachable due to power saving (e.g. UE is in extended idle mode DRX or in Power Saving Mode), and that the location information will be returned in a subsequent Subscriber Location Report when the UE becomes reachable. | + +NOTE1: Bits not defined in this table shall be cleared by the sending MME or SGSN and discarded by the receiving GMLC. + +### 7.4.54 Deferred-MT-LR-Data + +The Deferred-MT-LR-Data AVP is of type Grouped. + +AVP format: + +``` +Deferred-MT-LR-Data ::=
Result-Code AVP shall be used for errors defined in the Diameter base protocol (see IETF RFC 6733 [17]).
Experimental-Result AVP shall be used for SLh errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| IMSI | User-Name | C | This information element shall contain the IMSI of the targeted user. This IE shall be present if Result-Code is DIAMETER_SUCCESS and the MSISDN is absent. | +| MSISDN | MSISDN | C | This information element shall contain the MSISDN of the targeted user. This IE shall be present if Result-Code is DIAMETER_SUCCESS and the IMSI is absent. | +| LMSI | LMSI | C | This information element shall contain the LMSI allocated by the VLR. This IE should be present if Result-Code is DIAMETER_SUCCESS and LMSI is available in the HSS and MSC-Number is included in the Serving-Node AVP or in an Additional-Serving-Node AVP. | +| Serving Node | Serving-Node | C | This information element shall contain the information about the network node serving the targeted user i.e. the name/number of the serving node (MME, SGSN, 3GPP AAA server or MSC/MSC server), the LCS capabilities sets supported by the serving node and the IP address of the visited GMLC associated with the serving node. This IE shall be present if the Result-Code is DIAMETER_SUCCESS; otherwise it shall be absent. | +| Additional Serving Node | Additional-Serving-Node | C | This information element shall contain the information about another network node serving the targeted user. This IE may be present if Result-Code is DIAMETER_SUCCESS; otherwise it shall be absent. There may be multiple instances of this IE in the response provided by the HSS. | +| Home GMLC Address | GMLC-Address | C | This information element shall contain the IP address of the H-GMLC. This IE should be present if the Result-Code is DIAMETER_SUCCESS; otherwise it shall be absent. | +| PPR Address | PPR-Address | C | This information element shall contain the IP address of the Privacy Profile Register (PPR). This IE should be present if available in the HSS and the Result-Code is DIAMETER_SUCCESS; otherwise it shall be absent. | +| RIA Flags | RIA-Flags | O | This Information Element contains a bit mask. See 6.4.15 for the meaning of the bits. | +| Supported Features (See 3GPP TS 29.229 [8]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +#### 5.2.1.2 Detailed Behaviour of the HSS + +Upon reception of the Send Routing Info for LCS request, the HSS shall, in the following order: + +1. Check whether the requesting GMLC belongs to a network authorized to request UE location information. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_UNAUTHORIZED\_REQUESTING\_NETWORK in the Send Routing Information for LCS Response. +2. Check that the User Identity for whom data is asked exists in HSS. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN in the Send Routing Information for LCS Response. +- 2a. If both IMSI and MSISDN are present in the request, check whether they identify the same User. If not, the HSS Result-Code shall be set to DIAMETER\_CONTRADICTING\_AVPS in the Send Routing Information for LCS Response. +3. Check that there is at least one serving node associated with the targeted user. If not, Experimental-Result shall be set to DIAMETER\_ERROR\_ABSENT\_USER in the Send Routing Information for LCS Response. + +If there is an error in any of the above steps then the HSS shall stop processing and shall return the error code specified in the respective step (see 3GPP TS 29.329 [9] and 3GPP TS 29.229 [8] for an explanation of the error codes). + +If the HSS cannot fulfil the received request for reasons not stated in the above steps, e.g. due to a database error or empty mandatory data elements, it shall stop processing the request and set Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. + +Otherwise, the requested operation shall take place and the HSS shall return the Result-Code AVP set to DIAMETER\_SUCCESS. The HSS returns one or several of the network addresses of the current MME, SGSN, 3GPP AAA server and/or VMSC/MSC server, 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 the Send Routing Info for LCS request. If MSISDN was not provided in the Send Routing Info for LCS request and the subscription is MSISDN-less, the HSS shall return the dummy MSISDN value (see 3GPP TS 23.003 [10]). If both MSISDN and IMSI were provided in the Send Routing Info for LCS request, the HSS returns either MSISDN or IMSI or both. The HSS returns the address of the H-GMLC. The HSS also provides the address of the PPR, if available. + +The HSS shall include the Diameter Identity of the SGSN (i.e. SGSN-Name and SGSN-Realm), within the Serving-Node AVP or within an Additional-Serving-Node AVP, if and only if the HSS has received an indication that the Lgd interface is supported by the SGSN (see 3GPP TS 29.272 [12]). + +The HSS shall include the SGSN Number, within the Serving-Node AVP or Additional Serving-Node AVP, except if the HSS has received an indication that the Lg interface is not supported by the SGSN (see 3GPP TS 29.272 [12]). + +If the UE is served by the MME and SGSN parts of the same combined MME/SGSN (see 3GPP TS 29.272 [12] subclause 5.2.2.1.1 for how the HSS determines if the UE is served by the combined MME/SGSN) and if this combined MME/SGSN has indicated the support for optimized LCS procedure (via the Supported-Feature AVP as defined in 3GPP TS 29.272 [12] subclause 7.3.10) and if HSS supports this optimized LCS procedure, then the HSS shall set the "Combined-MME/SGSN-Supporting-Optimized-LCS-Proc" bit of the RIA-Flags. + +Regarding the LCS capabilities of the serving nodes, if the HSS registered an SGSN via the S6d reference point (i.e., the registered serving node is an S4-SGSN), the HSS shall set the LCS-Capabilities-Set value to indicate support of Capability Set 5 (i.e., LCS release 7 or later version). If the HSS registered an MME, the HSS shall not indicate any LCS capability value to the GMLC (i.e., the LCS-Capabilities-Set AVP shall be absent over SLh when the serving node is an MME); in this case, the GMLC shall assume that the MME supports LCS Capability Set 5. + +#### 5.2.1.3 Detailed Behaviour of the GLMC + +If there are a serving node as well as additional serving nodes in a successful Send Routing Info for LCS response, the receiving shall use the serving node in preference to the additional serving nodes. + +# --- 6 Protocol Specification and Implementations + +## 6.1 Introduction + +### 6.1.1 Use of Diameter Base Protocol + +The Diameter base protocol as specified in IETF RFC 6733 [17] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and error codes as specified in this + +specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) shall be used unmodified. + +### 6.1.2 Securing Diameter Messages + +For secure transport of Diameter messages, see 3GPP TS 33.210 [6]. + +### 6.1.3 Accounting Functionality + +Accounting functionality (Accounting Session State Machine, related command codes and AVPs) shall not be used on the SLh interface. + +### 6.1.4 Use of Sessions + +Between the GMLC and the HSS, Diameter sessions shall be implicitly terminated. An implicitly terminated session is one for which the server does not maintain state information. The client shall not send any re-authorization or session termination requests to the server. + +The Diameter base protocol as specified in IETF RFC 6733 [17] includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions. + +The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value NO\_STATE\_MAINTAINED (1), as described in IETF RFC 6733 [17]. As a consequence, the server shall not maintain any state information about this session and the client shall not send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses. + +### 6.1.5 Transport Protocol + +Diameter messages over the SLh interface shall make use of SCTP IETF RFC 4960 [7] as transport protocol. + +### 6.1.6 Routing Considerations + +This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host. + +If GMLC knows the address/name of the HSS for a certain user, both the Destination-Realm AVP and the Destination-Host AVP shall be present in the request. Otherwise, only the Destination-Realm AVP shall be present and the command shall be routed to the next Diameter node. Consequently, the Destination-Host AVP is declared as optional in the ABNF for all requests initiated by a GMLC. + +Destination-Realm AVP is declared as mandatory in the ABNF for all requests. + +If the Vendor-Specific-Application-ID AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node, and it shall not be used for routing purposes. + +### 6.1.7 Advertising Application Support + +The HSS and GMLC shall advertise support of the Diameter SLh Application by including the value of the application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the Diameter node as per IETF RFC 6733 [17]. + +### 6.1.8 Diameter Application Identifier + +The SLh interface protocol shall be defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP (
0-4 Mandatory
5-8 Excluded
9 Optional (Routing Key Management (RKM) Messages)
10 to 255 Excluded | +| 3.1.2 (Management (MGMT) message) | The values are classified as follow
0 Mandatory
1 Optional (Notify). When received and not supported the message maybe silently discarded.
2-255 Excluded | +| 3.1.2 (Transfer messages) | The values are classified as follow
0 Excluded
1 Mandatory
2 to 255 Excluded | +| 3.1.2 (Signalling network management (SSNM) messages) | The values are classified as follow
0 Excluded
1-6 Mandatory
7- 255 Excluded. | +| 3.1.2 (ASP State Maintenance (ASPSM) Messages) | The values are classified as follow
0 Excluded
1-6 Mandatory
7-255 Excluded | +| 3.1.2 (ASP Traffic Maintenance (ASPTM) Messages) | The values are classified as follow
0 Excluded
1-4 Mandatory
5 to 255 Excluded | +| 3.1.2 (Routing key management (RKM)) messages | Optional
If any of these messages is received and not supported an error message with the error code 0x04 (Unsupported message type) shall be sent | +| 3.1.3 Reserved | Mandatory | +| 3.1.4 Message length | Mandatory | + +| Section number in M3UA RFC | Comments | +|---------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3.2 Variable Length Parameter Format Common Parameters: |
The values are classified as follows
0x0000-- 0x0003, 0x0005, 0x0008, 0x000a, 0x000e, 0x000f, 0x0010 0x0014—0x01ff Excluded
0x0007, 0x0009, 0x000c and 0x0012 Mandatory
0x0004 optional (INFO String) if received and not supported the message is processed but the optional information element is silently discarded,
0x0006 optional (Routing Context if received and not supported the message is processed but the optional information element is silently discarded,
0x000b optional (Traffic Mode Type) if received and not supported the message is processed but the optional information element is silently discarded,
0x0011 (ASP Identifier) if received and not supported the message is processed but the optional information element is silently discarded,
0x0012 Affected point code is mandatory. The support of value 0 in the mask field is mandatory. All other values is outside the scope of this annex.
0x0013 (Correlation ID) if received and not supported the message is processed but the optional information element is silently discarded,
| +| 3.2 Variable Length Parameter Format M3UA Specific Parameters |The values are classified as follows
0x0201, 0x0202, 0x0203, 0x0211, 0x020d and 0x0214 to 0xffff Excluded
0x0204--0x0205, 0x0210 Mandatory
0x0200 optional (Network Appearance) if received and not supported the message is processed but the optional information element is silently discarded,
0x0206 Optinal (Concerned Destination). If received and not supported the message is processed but the optional information element is silently discarded.
0x0207 (Routing Key), 0x0208 (Registration Result), 0x0209 (Deregistration Result) 0x020a (Local Routing Key Identifier), 0x020b (Destination Point Code), 0x020c (Service Indicators) 0x020d (Subsystem Numbers), 0x020e (Originating Point Code List), 0x020f (Circuit Range), 0x0212 (Registration Status), 0x0213 (Deregistration Status) are parameters in optional message, and therefore no action is specified.
| +| 3.3 Transfer messages | These messages are mandatory at the interfaces A and C. | +| 3.3.1 Payload Data Message (DATA) |The parameters Network Appearance, Routing Context, Correlation ID are optional
The parameter Protocol data is mandatory.
| +| 3.4 SS7 signalling network management messages | Heading | +| 3.4.1 Destination Unavailable (DUNA) |The message is mandatory at the interface C.
The parameters Network Appearance, Routing Context, and INFO String are optional
The parameter Affected Point Code is mandatory
| +| 3.4.2 Destination Available (DAVA) |The message is mandatory at the interface C
The parameters Network Appearance, Routing Context, and INFO String are optional.
The parameter Affected Point Code is mandatory
| +| 3.4.3 Destination State Audit (DAUD) |The message is mandatory at the interface C
The parameters Network Appearance, Routing Context, and INFO String are optional.
The parameter Affected Point Code is mandatory
| + +| Section number in M3UA RFC | Comments | +|---------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3.4.4 Signalling Congestion (SCON) | The message is mandatory at the interface CThe parameters Network Appearance, Routing Context, Congestion Indications and INFO String are optional
The parameter Affected point code is mandatory. | +| 3.4.5 Destination User Part Unavailable (DUPU) | The message is mandatory at the interfaces A and C.
The parameters Network Appearance, Routing Context, and INFO String are optional.
The parameters Affected point code and User/Cause are mandatory | +| 3.4.6 Destination Restricted (DRST) message | This message is mandatory. | +| 3.5 ASP State Maintenance (ASPSM) Messages | These messages are mandatory at the interfaces A and C. | +| 3.5.1 ASP Up message | The ASP Identifier and Info String parameters are optional | +| 3.5.2 ASP Up Acknowledgement Message | The Info String parameter is optional. | +| 3.5.3 ASP Down message | The Info String parameter is optional. | +| 3.5.4 ASP Down Acknowledgement message | The Info String parameter is optional. | +| 3.5.5 Heartbeat message | The message is mandatory. | +| 3.5.6 Heartbeat Acknowledgement message | The message is mandatory | +| 3.6 Routing Key Management messages | These messages are optional at the interfaces A and C. | +| 3.7 ASP Traffic Maintenance (ASPTM) Messages | These messages are mandatory at the interfaces A and C. | +| 3.7.1 ASP Active message | The parameters Traffic Mode Type, Routing Context and INFO String are optional. | +| 3.7.2 ASP Active Acknowledgement message | The Traffic Mode Type, Routing Context and INFO String are optional. | +| 3.7.3 ASP inactive message | The parameters Routing Context and INFO String are optional. | +| 3.7.4 ASP Inactive Acknowledgement | The parameters Routing Context INFO String are optional. | +| 3.8 Management (MGMT) Messages | Heading | +| 3.8.1 Error message | The message is mandatory at the interfaces A and C | +| 3.8.2 Notify message | The message is optional at the interfaces A and C | +| 4 Procedure | The application of a particular procedure at a certain interface is detailed in the following sections | +| 4.1 Procedures to Support the M3UA-User | Heading | +| 4.1.1 Receipt of Primitives from the M3UA-User | The procedure is mandatory at the interfaces A and C. | +| 4.1.2 Receipt of Primitives from the Layer Management | This section is outside the scope of this annex. | +| 4.2 Procedures to Support the Management of SCTP Associations | The procedures are mandatory at the interfaces A and C | +| 4.2.1 Receipt of M3UA Peer Management Messages | The two first paragraphs are outside the scope of this annex.
Last paragraph is mandatory. | +| 4.3 AS and ASP State Maintenance | The procedure is mandatory at the interfaces A and C. | +| 4.3.1 ASP States | Mandatory | +| 4.3.2 AS States | Mandatory | + +| Section number in M3UA RFC | Comments | +|-------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4.3.3 M3UA Management Procedures for Primitives | This section is outside the scope of this annex. | +| 4.3.4 ASPM Procedures for Peer-to-Peer Messages | Heading | +| 4.3.4.1 ASP Up Procedure |
This procedure is mandatory at the interface C and is a subset of the procedure used at interface A. See also 4.3.4.1.2.
Note: The registration procedure is optional.
A received ASP Up must be acknowledged by an ASP Up Ack message, if no restriction applies e.g. maintenance.
| +| 4.3.4.1.1 M3UA Version Control | This procedure is mandatory at the interfaces A and C. | +| 4.3.4.1.2 IPSP Considerations (Asp Up) |This procedure is mandatory at the interface A.
All comments applicable for section 4.3.4.1 and 4.3.4.2 are also applicable for this section.
| +| 4.3.4.2 ASP-Down Procedure |This procedure is mandatory at the interface C and is a subset of the procedure used at interface A. See also 4.3.4.1.2.
A received ASP Down message must be acknowledged by an ASP Down Ack message, if no restriction applies eg maintenance reason.
| +| 4.3.4.3 ASP Active Procedure |This procedure is mandatory at interface C and is a subset of the procedure used at interface A. See also 4.3.4.3.1.
Configuration data define which AS an ASP is a member of. The ASP Active message does not contain a Routing Context parameter. Consequently, the ASP Active Ack message does not include any Routing Context(s) parameter.
The traffic state an ASP has, is configured within the associated Application Server. If more than one physical entity (ASPs, SGPs or IPSPs) implements a logical entity (SG, AS) then loadshare with 1+k is the mandatory traffic mode.
A received ASP Active must be acknowledged by an ASP Active Ack message, if no restriction applies e.g. maintenance reason.
If a Routing Context parameter is included in the ASP Active message it is not needed to include the Routing Context parameter in the ASP Active Ack message.
Note: This is a deviation to RFC 4666.
| +| 4.3.4.3.1 IPSP Considerations (ASP Active) |This procedure is mandatory at the interface A.
All comments applicable for section 4.3.4.3 are also applicable for this section.
| +| 4.3.4.4 ASP Inactive Procedures |This procedure is mandatory at the interface C and is a subset of the procedure used at interface A. See also 4.3.4.4.1.
Configuration data defines which AS an ASP is a member of.
It is optional to send several ASP Active Ack messages in response to a single ASP Active message.
A received ASP Inactive must be acknowledged by an ASP Inactive Ack message, if no restriction applies e.g. maintenance.
The sending of Notify message is mandatory if the As state is changed.
| +| 4.3.4.4.1 IPSP Considerations (ASP Inactive) |This procedure is mandatory at the interface A.
All comments applicable for section 4.3.4.4 are also applicable for this section.
| + +| Section number in M3UA RFC | Comments | +|----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 4.3.4.5 Notify Procedures | The procedure is mandatory at the interfaces A and C to reflect an AS state change. | +| 4.3.4.6 Heartbeat Procedures | The procedure is optional. | +| 4.4 Routing Key management procedure | The procedure is optional. | +| 4.5 Procedures to Support the Availability or Congestion Status of SS7 Destination | Heading | +| 4.5.1 At an SGP |Note: The use of Transfer restricted message is a national option and is about the scope of this specification.
If the SG knows that the ASP supports DRST, then SG shall Send a DRST message, if the SG does not know whether the ASP supports the DRST message the SGW shall send a DAVA message if the destination earlier was unavailable. If the destination was available then no action is required.
| +| 4.5.2 At an ASP | Heading | +| 4.5.2.1 Single SG Configurations | It is mandatory for an ASP to interoperate with one Signaling Gateway. | +| 4.5.2.2 Multiple SG Configurations | It shall be possible to configure an ASP to handle at least a configuration consisting of two Signalling Gateways. | +| 4.5.3 ASP Auditing | Only the part related to international use in Q.704 is inside the scope of this annex. | +| 4.6 MTP 3 restart | The procedure is mandatory. | +| 5. Examples of M3UA Procedures | Descriptive text | +| 5.1. Establishment of Association and Traffic between SGPs and ASPs | Note The procedures defined in the sub-sections to 5.1 are a subset of the procedures defined in section 5.5. | +| 5.1.1 Single ASP in an Application Server ("1+0" sparing) | Descriptive text | +| 5.1.1.1 Single ASP in an Application Server ("1+0" sparing), No Registration | The use of RCn is optional. | +| 5.1.1.2 Single ASP in Application Server ("1+0" sparing), Dynamic Registration | The use of dynamic registration is optional. | +| 5.1.1.3 Single ASP in Multiple Application Servers (each with "1+0" sparing), Dynamic Registration (Case 1 - Multiple Registration Requests) | The use of dynamic registration is optional. | +| 5.1.1.4 Single ASP in Multiple Application Servers (each with "1+0" sparing), Dynamic Registration (Case 2 - Single Registration Request) | The use of dynamic registration is optional. | +| 5.1.2 Two ASPs in Application Server ("1+1" sparing) | This procedure is optional. | +| 5.1.3 Two ASPs in an Application Server ("1+1" sparing, loadsharing case). | The traffic mode parameter is optional in ASP-Active message | +| 5.1.4 Three ASPs in an Application Server ("n+k" sparing, loadsharing case) | The procedure is optional. | +| 5.2 ASP Traffic Failover Examples | Heading | + +| Section number in M3UA RFC | Comments | +|---------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 5.2.1 (1+1 Sparing, Withdrawal of ASP, Backup Override) | The use of the procedure "backup override" is optional. | +| 5.2.2 (1+1 Sparing, Backup Override) | The use of the procedure "backup override" is optional. | +| 5.2.3 (n+k Sparing, Loadsharing case, Withdrawal of ASP) | The procedure is optional | +| 5.3 Normal Withdrawal of an ASP from an Application Server and Teardown of an Association | The registration procedure is optional. Routing Contexts (RC) is optional. | +| 5.3.X Normal Withdrawal of the ASP from an Application Server (1+1 sparing) loadsharing and Teardown of Association |Image: Sequence diagram showing the withdrawal of ASP 2 and ASP 1 from an SGP. The sequence is: 1. ASP 2 sends ASP Inactive to SGP; SGP responds with ASP Inactive Ack. 2. ASP 1 sends ASP Inactive to SGP; SGP responds with ASP Inactive Ack. 3. SGP sends Notify to ASP 2. 4. ASP 2 sends ASP Down to SGP; SGP responds with ASP Down Ack. 5. SGP sends Notify to ASP 1. 6. ASP 1 sends ASP Down to SGP; SGP responds with ASP Down Ack.
The figure is added for clarification.
| +| 5.4. Auditing Examples | Heading | +| 5.4.1. SG State: Uncongested/Available | Descriptive text. | +| 5.4.2. SG State: Congested (Congestion Level=2) /Available | Descriptive text. | +| 5.4.3. SG State: Unknown/Available | Descriptive text. | +| 5.4.4. SG State: Unavailable | Descriptive text. | +| 5.5 M3UA/MTP3-User Boundary Examples | Heading | +| 5.5.1 At an ASP | Heading | +| 5.5.1.1 Support for MTP-TRANSFER Primitives at the ASP | Heading | +| 5.5.1.1.1 Support for MTP-TRANSFER Request Primitive | The procedure is mandatory at the interface A and C. This description is also applicable for an IPSP, so replace the abbreviation ASP with ASP/IPSP and SGP with SGP/IPSP | +| 5.5.1.1.2 Support for the MTP-TRANSFER Indication Primitive | The support is mandatory at the interface A and C. This description is also applicable for an IPSP, so replace the abbreviation ASP with ASP/IPSP and SGP with SGP/IPSP. | +| 5.5.1.1.3 Support for ASP Querying of SS7 Destination States | This procedure is mandatory at the interface C. The querying of congestion states is an optional national procedure and outside the scope of this annex. | +| 5.5.2 At an SGP | Heading | +| 5.5.2.1 Support for MTP-TRANSFER Request Primitive at the SGP | The procedure is mandatory at the interface C. Network Appearance is optional. | + +| Section number in M3UA RFC | Comments | +|-----------------------------------------------------------------------------|--------------------------------------------------------------------------------| +| 5.5.2.2 Support for MTP-TRANSFER Indication Primitive at the SGP | The procedure is mandatory at the interface C | +| 5.5.2.3 Support for MTP-PAUSE, MTP-RESUME, MTP-STATUS Indication Primitives | Heading | +| 5.5.2.3.1 Destination Unavailable | The procedure is mandatory at the interface C | +| 5.5.2.3.2 Destination Available | The procedure is mandatory at the interface C | +| 5.5.2.3.3 SS7 Network Congestion | The procedure is mandatory at the interface C | +| 5.5.2.3.4 Destination User Part Unavailable | The procedure is mandatory at the interface C and optional at the interface A. | +| 5.6 Examples for IPSP communication. | Descriptive text. | + +# Annex B (Informative): The use of M2PA in 3GPP networks + +## B.1 Scope + +This annex defines the application of M2PA in 3GPP core networks as an option on interface B. The purpose of the Annex is to ensure the interoperability of different implementations of M2PA as used by different operators and vendors. This is achieved by: + +- Clarifying certain concepts which are used in RFC 4165; +- Defining those features in RFC 4165 for which support is mandatory; +- Defining those features in the RFC 4165 for which support is optional; +- Defining those features in RFC 4165 which shall not be used; + +This specification is intended for interfaces between network domains. However, it can also be used inside one network domain, and constitutes, in that case, a minimum set of M2PA requirements to be supported between IP nodes and between SRP nodes in a 3GPP network. + +## B.2 Introduction + +M2PA may be used between SRPs, i.e. interface B (refer to Figure 1 of Annex A). + +Figure 2 recommends how M2PA is used in a 3GPP IP based signalling network. + + + +Diagram illustrating the use of M2PA in 3GPP core networks. It shows two network domains connected via a series of nodes. The left domain is a 3GPP IP based signalling network containing three SG (Signalling Gateway) nodes and two SP (Service Point) nodes. The SG nodes are connected in a chain: SG - M2PA -> SG - MTP3/M2PA -> SG. The SP nodes are connected to the SG nodes. The right domain is an SS7 signalling network based on MTP3/MTP2. The connection between the two domains is via the third SG node, which is connected to the SS7 network through an MTP3/MTP2 interface. + +Figure B2.1: Use of M2PA in 3GPP core networks + +## B.3 Protocol conformance to RFC 4165 + +A minimum implementation shall support sections marked mandatory in the table below. It shall be possible to configure all implementations to interoperate (no error messages returned) with the minimum set. + +The table below makes comment to the sections in RFC 4165. In the comment column the following terms are used: + +- Mandatory: When support of text in a section is marked mandatory: + - On an information element, message or message class, it means that a receiver shall understand the information element, message or message class and carry out the requested action. + - For a procedure, it means that the procedure is mandatory to be carried out by the involved network elements. + +- Optional: When support of the text in a section is marked optional the feature involved is only guaranteed to work between peer entities which are subject to a bilateral agreement between operators of those entities. If one end uses an optional information element and the other does not support it, then a silent discard takes place of an information element as a part of the message. This is described as part of the handling of the optionality in the table. +- Excluded: This means that the feature shall not be used in a 3GPP environment + +Descriptive text means that the section does not include any requirements for this specification. + +Note: The word "heading" means that the section consists only of subordinate sections. + +The comments column also defines the behaviour of a minimum implementation if it does not support a message or an information element in a mandatory message. + + + +| Section number in M2PA RFC | Comments | +|--------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Abstract | Descriptive text | +| 1.Introduction | Descriptive text | +| 1.1 Scope | Descriptive text | +| 1.2 Terminology | Descriptive text. | +| 1.3 Abbreviations | Descriptive text. | +| 1.4 Conventions | Descriptive text. | +| 1.5. Signaling Transport Architecture | Descriptive text | +| 1.5.1 Point Code Representation | Mandatory | +| 1.6 Services Provided by M2PA | Descriptive text | +| 1.6.1 Support for MTP Level 2 / MTP Level 3 Interface Boundary | Mandatory | +| 1.6.2 Support for Peer-to-Peer Communication | Mandatory | +| 1.7. Functions Provided by M2PA | Heading | +| 1.7.1 MTP2 Functionality | Descriptive text | +| 1.7.2 Mapping of SS7 and IP Entities | Mandatory | +| 1.7.3 SCTP Association Management | Mandatory | +| 1.7.4 Retention of MTP3 in the SS7 Network | Descriptive text | +| 1.8. Definition of the M2PA Boundaries | Heading | +| 1.8.1 Definition of the M2PA/MTP Level3 Boundaries | Descriptive text | +| 1.8.2 Definition of the Lower Layer Boundary between M2PA and SCTP | Descriptive text | +| 1.9. Differences Between M2PA and M2UA | Descriptive text | +| 2. Protocol Elements | Mandatory | +| 2.1 Common message header | Mandatory | +| 2.1.1 Version: | Mandatory | +| 2.1.2 Spare | Mandatory | +| 2.1.3 Message class | Mandatory | +| 2.1.4 Message Type | Mandatory | +| 2.1.5 Message Length | Mandatory | +| 2.2 M2PA Header | Mandatory | +| 2.2.1 Backward Sequence Number (BSN) | Mandatory | +| 2.2.2 Forward Sequence Number (FSN) | Mandatory | +| 2.3 M2PA Messages | Mandatory | +| 2.3.1 User Data | Mandatory | +| 2.3.2 Link Status | Mandatory | +| 2.3.2.1 Link Status Proving | Mandatory | +| 3 State Control | Heading | +| 3.1 SCTP Association State Control | Descriptive text | +| 3.2 M2PA Link State Control | Descriptive text | +| 4 Procedures | Mandatory | +| 4.1 Procedures to Support MTP2 Feature | Heading | +| 4.1.1 Signal Unit Format, Delimitation, Acceptance | Descriptive text | +| 4.1.2 MTP and SCTP Entities |The content about how M2PA relates MTP and SCTP entities is Descriptive text.
The relationship between the streams of SCTP and M2PA Messages is mandatory.
| +| 4.1.3 Link Alignment | The procedure is Mandatory. | +| 4.1.4 Processor Outage | Mandatory | +| 4.1.5 Level 2 Flow Control | Mandatory | +| 4.1.6 Link Out of Service | Mandatory | +| 4.1.7 SCTP Association Problems | Mandatory | +| 4.1.8 Transmission and Reception Priorities | Mandatory | +| 4.1.9 M2PA Version Control | Mandatory | +| 4.2. Procedures to Support the MTP3/MTP2 Interface | Heading | +| 4.2.1 Sending and Receiving Messages | Mandatory | +| 4.2.2 MTP3 Signaling Link Congestion | Mandatory | +| 4.2.3 Changeover | Mandatory | +| 4.2.3.1 Multiple User Data Streams and Changeover | Descriptive text | +| 4.3 SCTP Considerations | Descriptive text | +| 4.3.1 SCTP Slow Start |Descriptive text
Avoiding the negative effects of slow start is Mandatory.
| + +| Section number in M2PA RFC | Comments | +|--------------------------------------------|------------------| +| 5 Examples of M2PA Procedures | Descriptive text | +| 5.1 Link Initialization (Alignment) | Descriptive text | +| 5.2 Message Transmission and Reception | Descriptive text | +| 5.3 Link Status Indication | Descriptive text | +| 5.4 Link Status Message (Processor Outage) | Descriptive text | +| 5.5 Level 2 Flow Control | Descriptive text | +| 5.6 MTP3 Signaling Link Congestion | Descriptive text | +| 5.7. Link Deactivation | Descriptive text | +| 5.8 Link Changeover | Descriptive text | + +# Annex C (informative): Change history + +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|----------|--------|-----------|------|-----|--------------------------------------------------------------------------------------------------------|--------| +| Feb 2001 | | | | | Initial draft | 0.0.2 | +| Feb 2001 | | | | | Second draft | 0.1.0 | +| Feb 2001 | | | | | Contributions and comments from TSG-CN WG4#6.1 Madrid Ad Hoc incorporated | 0.2.0 | +| Feb 2001 | | | | | Contributions and comments from TSG-CN WG4#6.1 Madrid Ad Hoc incorporated and draft further elaborated | 2.0.0 | +| Mar 2001 | | | | | Comments from TSG-CN WG4#7 incorporated. | 2.1.0 | +| Mar 2001 | CN#11 | NP-010079 | | | Annex A: M3UA updated to the latest available version 6 Approved in CN#11 | 4.0.0 | +| May 2001 | | | | | Foreword added | 4.0.1 | +| Sep 2001 | CN#13 | NP-010452 | 001 | | Change of M 3UA version | 4.1.0 | +| Sep 2001 | CN#13 | | | | Editorial clean up | 4.1.0 | +| Jun 2002 | CN#16 | | | | Corrupted Figure 5.3/1 fixed | 4.1.1 | +| Jun 2002 | CN#16 | | | | Rel-5 created after CN#16 | 5.0.0 | +| Sep 2002 | CN#17 | NP-020445 | 003 | 1 | Add reference to new IETF RFC on SCTP Checksum | 5.1.0 | +| Dec 2002 | CN#18 | NP-020585 | 007 | 2 | M3UA for 3GPP networks | 5.2.0 | +| Dec 2002 | CN#18 | NP-020585 | 009 | | IETF RFC reference for M3UA | 5.2.0 | +| Dec 2004 | CN#26 | | | | Rel-6 created after CN#26 | 6.0.0 | +| Jun 2007 | CT#36 | | | | Upgraded unchanged from Rel-6 | 7.0.0 | +| Jun 2007 | CT#36 | CP-070330 | 0013 | 3 | Use of M2PA in 3GPP core network signalling system | 8.0.0 | +| Sep 2007 | CT#37 | CP-070545 | 0014 | 2 | Protocol conformance to RFC4165(M2PA) | 8.1.0 | +| Sep 2007 | CT#37 | CP-070545 | 0015 | 2 | Change of protocol conformance to M3UA | 8.1.0 | +| Dec 2008 | CT#42 | | | | Copyright Notification updated | 8.1.1 | +| 2009-12 | - | - | - | - | Update to Rel-9 version (MCC) | 9.0.0 | +| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 10.0.0 | +| 2011-03 | CT#52 | CP-110371 | 0016 | | Removing reference to draft-ietf-sigtran-m3ua-implementors-guide-01 | 10.1.0 | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 11.0.0 | +| 2014-09 | - | - | - | - | Update to Rel-12 version (MCC) | 12.0.0 | +| 2015-12 | CT#70 | - | - | - | Update to Rel-13 version (MCC) | 13.0.0 | +| 2017-03 | CT#75 | - | - | - | Update to Rel-14 version (MCC) | 14.0.0 | +| 2018-06 | CT#80 | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-07 | CT#88e | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/29_series/29204/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/Rel-16/29_series/29204/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94e7ddc27139ef46286bdc46abb48e84b1cb78c6 --- /dev/null +++ b/marked/Rel-16/29_series/29204/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1df334847fe5d0be3e862f97bf36031af96619bbd02f336a89903768a61aca32 +size 82256 diff --git a/marked/Rel-16/29_series/29204/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg b/marked/Rel-16/29_series/29204/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..109a7b2e8ebfc99981f9735ab02363a7c23ee7ea --- /dev/null +++ b/marked/Rel-16/29_series/29204/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26b81e468be6612b26928b7eb4d2c2cab0059307cd99ceca63be9bc8c842c990 +size 36341 diff --git a/marked/Rel-16/29_series/29204/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Rel-16/29_series/29204/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc7793304db7d12e9a3efd3eecdd78ea673e344f --- /dev/null +++ b/marked/Rel-16/29_series/29204/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3da1188d50ea186818580ca733e141f1a24508623426d0f9a3c4688c06991e9b +size 67665 diff --git a/marked/Rel-16/29_series/29204/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/29_series/29204/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3799686114eee6e117f546906d648757008d63b6 --- /dev/null +++ b/marked/Rel-16/29_series/29204/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6b16681e53554f5fb504d1297b5f6f09f53e0507e09313af850dc19cca5035a +size 82056 diff --git a/marked/Rel-16/29_series/29204/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/29_series/29204/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ace3e96f9a656b62935eee2c5fe0d20adf5162b --- /dev/null +++ b/marked/Rel-16/29_series/29204/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:884d097ea545accb61c51c5db4835c8f676d9d8fa0cfd7ed973c66939f177c99 +size 72912 diff --git a/marked/Rel-16/29_series/29204/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg b/marked/Rel-16/29_series/29204/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b635b999bcbe12ae5578d97d185d5ca0c16137c6 --- /dev/null +++ b/marked/Rel-16/29_series/29204/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a631c2b288b70963dbcf661fdd2c9c22f3ae60d8529be71733a2f0b72dd3d00 +size 53806 diff --git a/marked/Rel-16/29_series/29204/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg b/marked/Rel-16/29_series/29204/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd4119d3f3faa99545bb92c85e182ec98ecffe36 --- /dev/null +++ b/marked/Rel-16/29_series/29204/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0c556159292eb30b2dd51d65ce873ca74e5652a14ba16e159756b177b803667 +size 54159 diff --git a/marked/Rel-16/29_series/29204/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/29_series/29204/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d404cbd24fc4357d50dd2bc17cc81c77389a890 --- /dev/null +++ b/marked/Rel-16/29_series/29204/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:beeb7f8c063755f3d8b23917bb4db53d6f6ca6881336458fce58ca83032cb508 +size 69934 diff --git a/marked/Rel-16/29_series/29204/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-16/29_series/29204/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d79378664d3ad92b41a0879157081344e7e9a445 --- /dev/null +++ b/marked/Rel-16/29_series/29204/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd2e5bc191b052b7b5fa0165f540d6fc775317d1672841f7d87da8465cb82bc8 +size 33166 diff --git a/marked/Rel-16/29_series/29204/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/29_series/29204/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c27ac7391bc7cf6ea0212ef6ab58d7b8d8d0e683 --- /dev/null +++ b/marked/Rel-16/29_series/29204/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e180e019fbd2166d280285e1bb1f9ecc5c28a52fabee332da2ca67d59c2a457 +size 104621 diff --git a/marked/Rel-16/29_series/29204/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/29_series/29204/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bc7aa7327cbb8d10781217bc4e3ad3597eedb85 --- /dev/null +++ b/marked/Rel-16/29_series/29204/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:832fe8d7c19f1e36c3672d9607f49e0a74721333e2702971218b5dcd95a9d92a +size 83725 diff --git a/marked/Rel-16/29_series/29204/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-16/29_series/29204/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6315e9e9916f88f85268c57f306638dbe798ff0 --- /dev/null +++ b/marked/Rel-16/29_series/29204/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4e146977ef4ec21b10c624413a58935cd5bee0518563062ab3217138e6ff2dc +size 72387 diff --git a/marked/Rel-16/29_series/29204/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/29_series/29204/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ab835f5948f3e05ae060050588b06c28da89b46 --- /dev/null +++ b/marked/Rel-16/29_series/29204/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:119cc7323fa6dbb57855c11ac2c28dff6d09f3ef5e6275afbcad9fdd9c98c3e6 +size 100345 diff --git a/marked/Rel-16/29_series/29204/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/Rel-16/29_series/29204/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b96f0851267852f4c05b1aad9aa2a60475953cf6 --- /dev/null +++ b/marked/Rel-16/29_series/29204/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00e1fd3fe0c6203932a64ffcfc95e0e60b7f3277b4207a6b5cfe4c12d31e58b5 +size 70841 diff --git a/marked/Rel-16/29_series/29204/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/29_series/29204/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a924c281bfe715fb9dd7a9df4e6f214fde3414ea --- /dev/null +++ b/marked/Rel-16/29_series/29204/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:052a48fb8169559b2142c01bd072a192249d923fda7728e351a583bcbd5b2f52 +size 93128 diff --git a/marked/Rel-16/29_series/29204/9791722d75115ddcc599b07d7bc35d73_img.jpg b/marked/Rel-16/29_series/29204/9791722d75115ddcc599b07d7bc35d73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f45af4642a26637e81e1ce13eb14178129a67c53 --- /dev/null +++ b/marked/Rel-16/29_series/29204/9791722d75115ddcc599b07d7bc35d73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d0e72348415bde4d561515b2785a315448c089c6cde6a0c2896be84d863d6b1 +size 50911 diff --git a/marked/Rel-16/29_series/29204/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/29_series/29204/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0b8b6f1bfcefe56bd2657438b6b3427179637de --- /dev/null +++ b/marked/Rel-16/29_series/29204/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d19eef58e709fa9aabe1e43bf6ccb612ddfc2789edc1296848b1f9fd3b3c1afa +size 93048 diff --git a/marked/Rel-16/29_series/29204/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/29_series/29204/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea7152bdb5a2a480f2674b5eadc3dbb798d2cece --- /dev/null +++ b/marked/Rel-16/29_series/29204/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5f8c9644b82e69b5ba3224a560ab744859e768a5334aa31a12dea443bf11ee7 +size 64191 diff --git a/marked/Rel-16/29_series/29204/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/29_series/29204/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..970688db3271216ec4c9ff03086760f4fba4c65e --- /dev/null +++ b/marked/Rel-16/29_series/29204/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75ee1482e2b319b465b6bf6a3b9b04290a4a3b0052b7c7daad646501d9daa8b5 +size 55025 diff --git a/marked/Rel-16/29_series/29204/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Rel-16/29_series/29204/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4561639e3f023fb3df66db087569900723a3ff0c --- /dev/null +++ b/marked/Rel-16/29_series/29204/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9a068f57805e185d26d05c4d3e5a5a7014fe4f822e222fdc174f933fdbdc28e +size 68883 diff --git a/marked/Rel-16/29_series/29204/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/29_series/29204/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4a6421d425dbbb8c1560dc1ae28554062fef00a --- /dev/null +++ b/marked/Rel-16/29_series/29204/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae0655bb2b2c780042a149208ad6da8cba60c38a8b58ab83a8a1b28951c8eb8f +size 88585 diff --git a/marked/Rel-16/29_series/29204/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/Rel-16/29_series/29204/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aca8cb499696df0dad7bd0c377f50660921dbfb0 --- /dev/null +++ b/marked/Rel-16/29_series/29204/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b272b7aa49319f9c944d538e8a57271e8acb40334583dae298ae0f1861dd235 +size 65794 diff --git a/marked/Rel-16/29_series/29204/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/29_series/29204/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd008e7b80f73151b3ad89102c252de3f93aba07 --- /dev/null +++ b/marked/Rel-16/29_series/29204/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:386d4d5702f988597a499adb0053a81e3c7583b753b59446f1b971267e8ee15f +size 57856 diff --git a/marked/Rel-16/29_series/29204/raw.md b/marked/Rel-16/29_series/29204/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8c03dc64a85159bd73c3ce27c0a5b5f1722a777d --- /dev/null +++ b/marked/Rel-16/29_series/29204/raw.md @@ -0,0 +1,1102 @@ + + + + + + +# --- Contents + +| | | +|--------------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| Introduction ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 6 | +| 4 Network architecture..... | 6 | +| 4.1 Scenarios ..... | 6 | +| 4.1.1 Outbound traffic (not yet protected) from own to foreign NE ..... | 7 | +| 4.1.2 Inbound traffic from foreign to own NE ..... | 7 | +| 4.1.3 Inbound transit traffic ..... | 8 | +| 4.1.4 Outbound transit traffic (not relayed)..... | 9 | +| 4.1.5 Outbound traffic from own to own NE ..... | 9 | +| 4.1.6 Inbound traffic from own to own NE ..... | 10 | +| 4.1.7 Outbound traffic from foreign to own NE..... | 11 | +| 4.1.8 Inbound traffic from own to foreign NE ..... | 11 | +| 4.1.9 Outbound traffic (already protected) from own to foreign NE ..... | 12 | +| 4.1.10 Outbound transit traffic (relayed by SRF)..... | 13 | +| 5 Detailed Behaviour of the SS7 Security Gateway ..... | 13 | +| 5.1 TCAP user traffic ..... | 13 | +| 5.1.1 General ..... | 13 | +| 5.1.2 Interactions with Mobile Number Portability..... | 28 | +| 5.1.3 Interactions with SCCP segmentation..... | 28 | +| 5.1.4 Protocol details ..... | 29 | +| 5.1.4.1 Transformation of unprotected message to protected message ..... | 29 | +| 5.1.4.2 Transformation of protected message to unprotected message ..... | 33 | +| 5.1.4.3 Handling of received XUDTS messages and UDTs messages ..... | 36 | +| Annex A (informative): Change history..... | 39 | + +# --- 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 absence of security in Signalling System No. 7 (SS7) networks is an identified security weakness in 2G systems. This was formerly perceived not to be a problem, since the SS7 networks were the provinces of a small number of large institutions. This is no longer the case, and so there is now a need for security precautions. + +For 3G systems it is a clear goal to be able to protect inter-network SS7 signalling protocols. The protection is done by security gateways which are located at the network border. As a consequence intra network SS7 signalling is not protected and network elements other than Security Gateways are not impacted. + +# --- 1 Scope + +The present document provides functional description of the SS7 Security Gateway. The document covers also network architecture, routing considerations, and protocol details. + +# --- 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 29.002: "Mobile Application Part (MAP) specification". +- [2] 3GPP TS 29.078: "Customized Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; CAMEL Application Part (CAP) specification". +- [3] ETSI ETS 300 358: "ISDN Completion of Calls to Busy Subscriber (CCBS) supplementary service; Functional capabilities and information flows". +- [4] 3GPP TS 23.066: "Support of GSM Mobile Number Portability (MNP) stage 2". +- [5] ITU-T Recommendation Q.773: "Specifications of Signalling System No.7; Transaction capabilities formats and encoding". +- [6] 3GPP TS 33.200: "3G Security; Network Domain Security (NDS); Mobile Application Part (MAP) application layer security". +- [7] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". +- [8] 3GPP TS 33.204: "3G Security; Network Domain Security (NDS); Transaction Capabilities Application Part (TCAP) user security". +- [9] ITU-T Recommendations Q.711 to Q.716 (07/96), White Book Signalling Connection Control Part (SCCP). +- [10] 3GPP TS 21.905: "Vocabulary for 3GPP Specifications". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [10] 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 [10]. + +| | | +|------------|-----------------------------------------------------------------------------| +| TCAP user: | Application Part identified by one of the following SCCP Subsystem Numbers: | +| | 0000 0110 HLR (MAP) | +| | 0000 0111 VLR (MAP) | +| | 0000 1000 MSC (MAP) | +| | 0000 1001 EIR (MAP) | +| | 0000 1010 is allocated for evolution (possible Authentication Centre) | +| | 1001 0001 GMLC (MAP) | +| | 1001 0010 CAP | +| | 1001 0011 gsmSCF (MAP) or IM-SSF (MAP) or Presence Network Agent | + +| | | +|-----------|------------| +| 1001 0101 | SGSN (MAP) | +| 1001 0110 | GGSN (MAP) | +| 0000 1011 | SSAP | + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|-----------------------------------------------------| +| CC | Country Code | +| GSMA | Global System for Mobile communications Association | +| IV | Initialisation Vector | +| MAC | Message Authentication Code | +| MNP | Mobile Number Portability | +| MSISDN | Mobile Station International ISDN Number | +| NDC | National Destination Code | +| NE | Network Entit | +| PLMN | Public Land Mobile Network y | +| RN | Routeing Number | +| SAD | Security Association Database | +| SEG | Security Gateway | +| SPD | Security Policy Database | +| SPI | Security Parameter Index | +| SRF | Signalling Relay Functio | +| TCAP | Transcation Capabilities Application Part | +| UDT | SCCP Unidata message | +| XUDT | SCCP Extended Unidata message n | + +# --- 4 Network architecture + +In a PLMN that employs SS7 Security Gateways all TCAP user signalling messages entering or leaving the PLMN have to transit an SS7 Security Gateway which belongs to the PLMN and which performs the protection of leaving (i.e. outbound) messages and the protection checking and de-protection or blocking of entering (i.e. inbound) messages. + +One or several SS7 Security Gateways may be employed within a PLMN. + +An SS7 Security Gateway may be co-located with any TCAP user NE or it may stand alone. However, for the purpose of this document and without imposing any restrictions, it is assumed that the SS7 Security Gateways is a stand alone entity. + +It is further assumed that the SS7 Security Gateways are located at the boarder of the PLMN i.e. inbound messages transit an SS7 Security Gateway before they reach any other node within the PLMN, and outbound messages transit an SS7 Security Gateway immediately before reaching a node outside the PLMN. + +SS7 routeing is not impacted by the SS7 Security Gateway Architecture. As a consequence SS7 Security Gateways are stateless at TCAP level: No TCAP dialogue states are maintained in the SS7 Security Gateway since the outbound dialogue request message may transit a different SS7 Security Gateway than the corresponding inbound dialogue response message; similarly the inbound dialogue request message may transit a different SS7 Security Gateway than the corresponding outbound dialogue response message. + +## 4.1 Scenarios + +SS7 Security Gateways perform protection, de-protection, blocking and unmodified passing of TCAP user messages depending on the scenario as described below: + +Note that scenarios 4.1.5, 4.1.6, 4.1.7, 4.1.8, and 4.1.9 are not applicable if all PLMN's TCAP user NEs are interconnected by PLMN internal signalling links and routing tables are set up not to allow these scenarios. + +### 4.1.1 Outbound traffic (not yet protected) from own to foreign NE + +This scenario is shown in figure 4.1.1. The message is originated at a NE inside the PLMN. It may transit several transit nodes inside the PLMN before it reaches the SS7 Security Gateway. This SS7 Security Gateway protects the message + +according to the relevant Security Policy with the relevant Security Association. The message may then transit several nodes outside the PLMN (including an SS7 Security Gateway) before it reaches its destination. + + + +The diagram illustrates the flow of an unprotected TCAP user message from a TCAP user NE within a PLMN cloud. The message path is: TCAP user NE → Transit Node → SS7 Security Gateway. From the SS7 Security Gateway, the message is shown as a protected TCAP user message exiting the PLMN towards a destination. Two lines from the label 'unprotected TCAP user message' point to the message path between the TCAP user NE and the SS7 Security Gateway. + +Diagram of outbound traffic from own to foreign NE + +Figure 4.1.1: Outbound traffic (not yet protected) from own to foreign NE + +### 4.1.2 Inbound traffic from foreign to own NE + +This scenario is shown in figure 4.1.2. The message is originated at a NE outside the PLMN. It may transit several transit nodes (including an SS7 Security Gateway) outside the PLMN before it reaches the PLMN's SS7 Security Gateway. This SS7 Security Gateway checks whether the message is correctly protected according to the relevant security association. If it is not, the message is blocked (discarded), otherwise it is de-protected. To determine the relevant security association the fact that the message may have been relayed by an MNP-SRF in a transit network (see Clause 4.1.10 and 5.1.2) needs to be taken into account. After successful de-protection the message may then transit several nodes inside the PLMN before it reaches the TCAP user NE. + + + +The diagram illustrates the flow of a protected TCAP user message from an origin outside the PLMN. The message path is: from origin → SS7 Security Gateway → Transit Node → TCAP user NE. The message is shown as a protected TCAP user message entering the PLMN through the SS7 Security Gateway. Two lines from the label 'unprotected TCAP user message' point to the message path between the SS7 Security Gateway and the TCAP user NE. + +Diagram of inbound traffic from foreign to own NE + +Figure 4.1.2: Inbound traffic from foreign to own NE + +### 4.1.3 Inbound transit traffic + +This scenario is shown in figure 4.1.3. The message is originated at a NE outside the transit PLMN. It may transit several transit nodes outside the transit PLMN before it reaches the SS7 Security Gateway in inbound direction. This SS7 Security Gateway passes the message unmodified. The message may then transit several transit nodes inside the transit PLMN, another SS7 Security Gateway of the transit PLMN in outbound direction (see Clause 4.1.4), and several transit nodes outside the transit and destination PLMN (potentially including an SS7 Security Gateway) before it reaches the destination PLMN. + +Note: A PLMN operator may decide not to act as transit network for specific or all combinations of origin and destination. In this case the SS7 Security Gateway may block the inbound message. + + + +The diagram illustrates the flow of inbound transit traffic within a PLMN. An orange cloud represents the PLMN. An arrow labeled 'from origin' points to a red box labeled 'SS7 Security Gateway' located outside the cloud. From this gateway, an arrow points into the cloud to a cyan box labeled 'Transit Node'. From the 'Transit Node', an arrow points to a blue box labeled 'SS7 SEG' located at the bottom of the cloud. An arrow labeled 'to destination' points from the 'SS7 SEG' out of the cloud. A label 'protected or unprotected TCAP user message' is shown with lines pointing to the arrows entering and leaving the 'SS7 Security Gateway' and the 'SS7 SEG'. + +Diagram of Inbound transit traffic + +Figure 4.1.3: Inbound transit traffic + +### 4.1.4 Outbound transit traffic (not relayed) + +This scenario is shown in figure 4.1.4. The message is originated at a NE outside the transit PLMN. It may transit several transit nodes outside the transit PLMN (including an SS7 Security Gateway), an SS7 Security Gateway of the transit PLMN in inbound direction (see Clause 4.1.3), and several transit nodes inside the transit PLMN before it reaches the SS7 Security Gateway in outbound direction. This SS7 Security Gateway passes the message unmodified. The message may then transit several transit nodes outside the transit and destination PLMN (potentially including an SS7 Security Gateway) before it reaches the destination PLMN. + + + +The diagram illustrates the flow of outbound transit traffic within a PLMN. An arrow labeled 'from origin' points to an 'SS7 SEG' box. From the 'SS7 SEG', an arrow points to a 'Transit Node' box. From the 'Transit Node', an arrow points to an 'SS7 Security Gateway' box. From the 'SS7 Security Gateway', an arrow points to 'to destination'. A label 'protected or unprotected TCAP user message' has lines pointing to the arrows between the 'SS7 SEG' and 'Transit Node', and between the 'Transit Node' and 'SS7 Security Gateway'. The entire path is contained within an orange cloud labeled 'PLMN'. + +Figure 4.1.4: Outbound transit traffic (not relayed). A diagram showing a message path within a PLMN cloud. The path starts from an origin, goes to an SS7 SEG, then to a Transit Node, and finally to an SS7 Security Gateway, which then points to the destination. Labels include 'from origin', 'protected or unprotected TCAP user message', 'PLMN', 'SS7 SEG', 'Transit Node', 'SS7 Security Gateway', and 'to destination'. + +Figure 4.1.4: Outbound transit traffic (not relayed) + +### 4.1.5 Outbound traffic from own to own NE + +This scenario is shown in figure 4.1.5. The message is originated at a NE inside the PLMN. It may transit several transit nodes inside the PLMN before it reaches the SS7 Security Gateway in outbound direction. This SS7 Security Gateway protects the message according to the relevant Security Association. The message may then transit several transit nodes outside the PLMN, another SS7 Security Gateway of the PLMN in inbound direction (see Clause 4.1.6) and several transit nodes within the PLMN before it reaches the destination NE inside the PLMN. + + + +The diagram illustrates the flow of outbound traffic from an own NE to another own NE within a PLMN. Two yellow boxes labeled 'TCAP user NE' are inside an orange cloud labeled 'PLMN'. Arrows from these boxes point to blue boxes labeled 'Transit Node'. One 'Transit Node' points to a red box labeled 'SS7 Security Gateway'. An arrow from the 'SS7 Security Gateway' points to a blue box labeled 'Transit Node' outside the cloud. From this 'Transit Node', an arrow points to a blue box labeled 'SS7 SEG'. From the 'SS7 SEG', an arrow points to a blue box labeled 'Transit Node' inside the cloud. From this 'Transit Node', an arrow points to a yellow box labeled 'TCAP user NE'. A label 'unprotected TCAP user message' has lines pointing to the arrows between the 'TCAP user NE' boxes and the 'Transit Node' boxes. A label 'protected TCAP user message' has lines pointing to the arrows between the 'SS7 Security Gateway' and the 'Transit Node' box outside the cloud, and between the 'SS7 SEG' and the 'Transit Node' box inside the cloud. + +Figure 4.1.5: Outbound traffic from own to own NE. A diagram showing a message path within a PLMN cloud. Two 'TCAP user NE' boxes point to 'Transit Node' boxes. One 'Transit Node' points to an 'SS7 Security Gateway' box, which then points to another 'Transit Node' box outside the PLMN cloud. The second 'Transit Node' points to an 'SS7 SEG' box, which then points to another 'Transit Node' box inside the PLMN cloud. The second 'Transit Node' points to a 'TCAP user NE' box. Labels include 'unprotected TCAP user message', 'PLMN', 'TCAP user NE', 'Transit Node', 'SS7 Security Gateway', 'SS7 SEG', and 'protected TCAP user message'. + +Figure 4.1.5: Outbound traffic from own to own NE + +### 4.1.6 Inbound traffic from own to own NE + +This scenario is shown in figure 4.1.6. The message is originated at a NE inside the PLMN. It may transit several transit nodes inside the PLMN, an SS7 Security Gateway of the PLMN in outbound direction (see Clause 4.1.5), and several + +transit nodes outside the PLMN before it reaches the SS7 Security Gateway in inbound direction. This SS7 Security Gateway checks whether the message is correctly protected according to the relevant Security Association. If it is not, the message is blocked (discarded), otherwise it is de-protected. The message may then transit several transit nodes inside the PLMN before it reaches the destination NE inside the PLMN. + + + +The diagram illustrates the flow of an unprotected TCAP user message within a PLMN. Two yellow boxes labeled 'TCAP user NE' are shown inside an orange cloud representing the PLMN. Arrows from these boxes point to cyan boxes labeled 'Transit Node'. From the top 'Transit Node', an arrow points to a purple box labeled 'SS7 SEG'. From the 'SS7 SEG', a red arrow points to another cyan 'Transit Node' outside the PLMN. From this external 'Transit Node', a red arrow points to a red box labeled 'SS7 Security Gateway'. From the 'SS7 Security Gateway', a red arrow points back to the external 'Transit Node', and then a red arrow points back into the PLMN to the bottom 'Transit Node'. Finally, an arrow points from the bottom 'Transit Node' to the bottom 'TCAP user NE'. The text 'unprotected TCAP user message' is on the left, and 'protected TCAP user message' is on the right, indicating the state of the message after passing through the security gateway. + +Diagram of inbound traffic from own to own NE within a PLMN. + +Figure 4.1.6: Inbound traffic from own to own NE + +### 4.1.7 Outbound traffic from foreign to own NE + +This scenario is shown in figure 4.1.7. The message is originated at a NE outside the PLMN. It may transit several transit nodes outside the PLMN, an SS7 Security Gateway of the PLMN in inbound direction (see Clause 4.1.2), and several transit nodes inside the PLMN before it reaches the SS7 Security Gateway in outbound direction. This SS7 Security Gateway protects the message according to the reverse relevant Security Association. The message may then transit several transit nodes outside the PLMN, another SS7 Security Gateway of the PLMN in inbound direction (see Clause 4.1.2) and several transit nodes within the PLMN before it reaches the destination NE inside the PLMN. + + + +This diagram illustrates the flow of outbound traffic from a foreign network element (NE) to an own NE within a PLMN. The PLMN is represented by an orange cloud. The traffic path is as follows: an arrow labeled 'from origin' points to an external SS7 SEG; from the SS7 SEG, a black arrow points to a Transit Node inside the PLMN; from this Transit Node, a black arrow points to an SS7 Security Gateway; from the SS7 Security Gateway, a red arrow points to another external Transit Node; from this external Transit Node, a red arrow points to another external SS7 SEG; from this SS7 SEG, a black arrow points to a second Transit Node inside the PLMN; from this second Transit Node, a black arrow points to a TCAP user NE. A white box labeled 'unprotected TCAP user message' is positioned near the first Transit Node, and a white box labeled 'protected TCAP user message' is positioned near the second SS7 SEG. + +Diagram of outbound traffic from foreign to own NE + +Figure 4.1.7: Outbound traffic from foreign to own NE + +### 4.1.8 Inbound traffic from own to foreign NE + +This scenario is shown in figure 4.1.8. The message is originated at a NE inside the PLMN. It may transit several transit nodes inside the PLMN, an SS7 Security Gateway of the PLMN in outbound direction (see Clause 4.1.1), and several transit nodes outside the PLMN before it reaches the SS7 Security Gateway in inbound direction. This SS7 Security Gateway checks whether the message is correctly protected according to the relevant security association. If it is not, the message is blocked (discarded); otherwise it is passed unmodified. The message may then transit several transit nodes inside the PLMN, another SS7 Security Gateway of the PLMN in outbound direction (see Clause 4.1.9) and several transit nodes outside the PLMN (including an SS7 Security Gateway) before it reaches the destination NE outside the PLMN. + + + +This diagram illustrates the flow of inbound traffic from an own NE to a foreign NE within a PLMN. The PLMN is represented by an orange cloud. The traffic path is as follows: a yellow box labeled 'TCAP user NE' sends a black arrow labeled 'unprotected TCAP user message' to a Transit Node inside the PLMN; from this Transit Node, a black arrow points to an SS7 SEG; from the SS7 SEG, a red arrow points to an external Transit Node; from this external Transit Node, a red arrow points to an SS7 Security Gateway; from the SS7 Security Gateway, a red arrow points to another external Transit Node; from this external Transit Node, a red arrow points to another external SS7 SEG; from this SS7 SEG, a black arrow points to a second Transit Node inside the PLMN; from this second Transit Node, a black arrow points to an arrow labeled 'to destination'. A white box labeled 'protected TCAP user message' is positioned near the second SS7 SEG. + +Diagram of inbound traffic from own to foreign NE + +Figure 4.1.8: Inbound traffic from own to foreign NE + +### 4.1.9 Outbound traffic (already protected) from own to foreign NE + +This scenario is shown in figure 4.1.9. The message is originated at a NE inside the PLMN. It may transit several transit nodes inside the PLMN, an SS7 Security Gateway of the PLMN in outbound direction (see Clause 4.1.1), several transit nodes outside the PLMN, an SS7 Security Gateway of the PLMN in inbound direction (see Clause 4.1.8), and several transit nodes inside the PLMN before it reaches the SS7 Security Gateway. This SS7 Security Gateway passes the message unmodified. The message may then transit several transit nodes outside the PLMN (including an SS7 Security Gateway) before it reaches the destination NE outside the PLMN. + + + +The diagram illustrates the path of a TCAP user message within a PLMN (represented by an orange cloud). A yellow box labeled 'TCAP user NE' originates an 'unprotected TCAP user message' (black arrow). The message flows through a 'Transit Node' (cyan box) to an 'SS7 SEG' (purple box). From the SS7 SEG, it passes through another 'Transit Node' and then to a second 'SS7 Security Gateway' (purple box with a red border). The message is then shown as a 'protected TCAP user message' (red arrow) exiting the PLMN towards the 'destination'. + +Diagram of outbound traffic (already protected) from own to foreign NE + +Figure 4.1.9: Outbound traffic (already protected) from own to foreign NE + +### 4.1.10 Outbound transit traffic (relayed by SRF) + +This scenario is shown in figure 4.1.10. The message (originally destined for the PLMN) is originated at a NE outside the transit PLMN. It may transit several transit nodes outside the transit PLMN (including an SS7 Security Gateway), an SS7 Security Gateway of the transit PLMN in inbound direction (see Clause 4.1.2), several transit nodes inside the transit PLMN, and an MNP-SRF which replaces the SCCP called party address of the message before it reaches the SS7 Security Gateway in outbound direction. This SS7 Security Gateway recognizes that the message was relayed by an SRF by analyzing the SCCP called party address and protects the message with the relevant Security Association. The message may then transit several transit nodes outside the transit and destination PLMN (potentially including an SS7 Security Gateway) before it reaches the destination PLMN. + + + +The diagram illustrates the flow of outbound transit traffic within a PLMN (represented by an orange cloud). A red arrow labeled 'from origin' points to an 'SS7 SEG' (blue box). From the 'SS7 SEG', a black arrow points to an 'MNP SRF' (pink box). From the 'MNP SRF', a black arrow points to an 'SS7 Security Gateway' (blue box with a red border). A red arrow labeled 'to destination' exits the 'SS7 Security Gateway'. A line labeled 'protected TCAP user message' originates from the 'SS7 SEG' and points to the 'SS7 Security Gateway'. Another line labeled 'unprotected TCAP user message' originates from the 'MNP SRF' and points to the 'SS7 Security Gateway'. + +Diagram of outbound transit traffic relayed by SRF within a PLMN. + +Figure 4.1.10: Outbound transit traffic (relayed by SRF) + +# 5 Detailed Behaviour of the SS7 Security Gateway + +## 5.1 TCAP user traffic + +### 5.1.1 General + +With regard to TCAP user traffic the SS7 Security Gateway performs message protection, protection checking and de-protection, transparent passing, and blocking of messages depending on the message's origin (SCCP calling party address), the message's destination (SCCP called party address), and the message's direction (inbound or outbound) as shown in figure 5.1.1. + + + +procedure SS7\_Security\_Gateway + +1(2) + +Procedure in the SS7 Security Gateway + +``` +graph TD; Idle([Idle]) --> TCAP[TCAP user message]; TCAP --> CheckDir[Check direction]; CheckDir --> INBOUND[INBOUND]; CheckDir --> OUTBOUND[OUTBOUND]; CheckDir --> NotCrossing[not crossing PLMN boundary]; INBOUND --> IN((IN)); OUTBOUND --> OUT((OUT)); NotCrossing --> Pass1((pass)); IN --> CheckOD[check origin and destination]; CheckOD --> OwnToOwn[own to own]; CheckOD --> OwnToForeign[own to foreign]; CheckOD --> ForeignToOwn[foreign to own]; CheckOD --> ForeignToForeign[foreign to foreign]; OwnToOwn --> InboundOwnToOwn[Inbound_own_to_own]; OwnToForeign --> InboundOwnToForeign[Inbound_own_to_foreign]; ForeignToOwn --> InboundForeignToOwn[Inbound_foreign_to_own]; ForeignToForeign --> Pass2((pass)); InboundOwnToOwn --> Result{result = block}; InboundOwnToForeign --> Result; InboundForeignToOwn --> Result; Result --> Yes[yes]; Result --> No[no]; Yes --> Block((block)); No --> Pass3((pass)); +``` + +Flowchart for SS7 Security Gateway procedure. It starts with 'Idle', followed by 'TCAP user message', then 'Check direction'. It branches into 'INBOUND' (IN), 'OUTBOUND', and 'not crossing PLMN boundary' (pass). The 'IN' path leads to 'check origin and destination', which branches into 'own to own' (Inbound\_own\_to\_own), 'own to foreign' (Inbound\_own\_to\_foreign), 'foreign to own' (Inbound\_foreign\_to\_own), and 'foreign to foreign' (pass). The first three paths lead to a 'result = block' decision, which branches into 'yes' (block) and 'no' (pass). + +Figure 5.1.1 Process SS7 Security Gateway (sheet 1 of 2) + + + +procedure SS7\_Security\_Gateway 2(2) + +Procedure in +the SS7 Security +Gateway + +``` +graph TD; OUT((OUT)) --> check[check origin and destination]; check --> own_to_own[own to own]; check --> own_to_foreign[own to foreign]; check --> foreign_to_own[foreign to own]; check --> foreign_to_foreign[foreign to foreign]; own_to_own --> Outbound_own_to_own[Outbound_own_to_own]; own_to_foreign --> Outbound_own_to_foreign[Outbound_own_to_foreign]; foreign_to_own --> Outbound_foreign_to_own[Outbound_foreign_to_own]; foreign_to_foreign --> Outbound_foreign_to_foreign[Outbound_foreign_to_foreign]; Outbound_own_to_own --> pass1((pass)); Outbound_own_to_foreign --> pass1; Outbound_foreign_to_own --> pass1; Outbound_foreign_to_foreign --> pass1; pass1 --> block((block)); pass1 --> pass2((pass)); pass2 --> TCAP[TCAP user message]; block --> Idle([Idle]); TCAP --> Idle; +``` + +Flowchart for SS7\_Security\_Gateway procedure. It starts with 'OUT', followed by 'check origin and destination'. A decision point branches into four cases: 'own to own' (Outbound\_own\_to\_own), 'own to foreign' (Outbound\_own\_to\_foreign), 'foreign to own' (Outbound\_foreign\_to\_own), and 'foreign to foreign' (Outbound\_foreign\_to\_foreign). All four cases lead to a 'pass' connector. Below this, a 'block' connector and a 'pass' connector (leading to 'TCAP user message') both lead to an 'Idle' terminal. + +Figure 5.1.1 Process SS7 Security Gateway (sheet 2 of 2) + + + +macrodefinition Check\_Direction + +1(1) + +``` +graph TD; Start([ ]) --> D1{previous node belongs to own PLMN}; D1 -- yes --> D2{next node belongs to own PLMN}; D1 -- no --> D3{next node belongs to own PLMN}; D2 -- yes --> E1(( )); E1 --> O1[not crossing PLMN boundary]; O1 --> OUTBOUND[OUTBOUND]; D2 -- no --> OUTBOUND; D3 -- yes --> E2(( )); E2 --> INBOUND[INBOUND]; D3 -- no --> E3(( )); E3 --> O2[not crossing PLMN boundary]; +``` + +Flowchart for macro Check\_Direction. It starts with a connector, then a decision 'previous node belongs to own PLMN'. If 'yes', it goes to another decision 'next node belongs to own PLMN'. If 'yes', it ends at 'not crossing PLMN boundary' (OUTBOUND). If 'no', it ends at 'OUTBOUND'. If 'no' from the first decision, it goes to another decision 'next node belongs to own PLMN'. If 'yes', it ends at 'INBOUND'. If 'no', it ends at 'not crossing PLMN boundary'. + +Figure 5.1.2 Macro Check\_Direction (sheet 1 of 1) + + + +macrodefinition Inbound\_own\_to\_own + +1(1) + +``` + +graph TD + Start([ ]) --> D1{message contains +protectable parameter} + D1 -- no --> P1((pass)) + D1 -- yes --> D2{message is +not protected} + + D2 -- yes --> D3{message should be +protected according +to SPD} + D3 -- no --> P2((pass)) + D3 -- yes --> D4{Fall Back allowed +according to SPD} + D4 -- yes --> P2 + D4 -- no --> B1((block)) + + D2 -- no --> D5{calling party address +consistent with SPI} + D5 -- no --> D6{protection mode +acceptable according +to SPD} + D5 -- yes --> D7{success} + + D6 -- no --> D7 + D6 -- yes --> Proc1[De-protect +message] + Proc1 --> D7 + + D7 -- no --> B1 + D7 -- yes --> P3((pass)) + +``` + +The flowchart titled 'macrodefinition Inbound\_own\_to\_own' (sheet 1 of 1) describes the logic for handling inbound messages. It starts with a check: 'message contains protectable parameter'. If 'no', it results in 'pass'. If 'yes', it checks if the 'message is not protected'. + +If the message is not protected ('yes' path), it checks if the 'message should be protected according to SPD'. If 'no', it results in 'pass'. If 'yes', it checks if 'Fall Back allowed according to SPD'. If 'yes', it results in 'pass'; if 'no', it results in 'block'. + +If the message is protected ('no' path from 'message is not protected'), it checks if the 'calling party address consistent with SPI'. If 'yes', it proceeds to a 'success' decision. If 'no', it checks if the 'protection mode acceptable according to SPD'. If 'no' to that, it proceeds to 'success'. If 'yes', it performs 'De-protect message' before checking 'success'. If the 'success' check is 'yes', it results in 'pass'; if 'no', it results in 'block'. + +Flowchart for macrodefinition Inbound\_own\_to\_own + +**Figure 5.1.3 Macro Inbound\_own\_to\_own (sheet 1 of 1)** + +The decision box "message contains protectable parameter" takes the "yes"-exit if user-information is present in the Dialogue Portion, or a parameter is present in an Invoke or ReturnError Component, or a result is present in a ReturnResult Component. + +The decision box "message is not protected" takes the "no"-exit if user-information within the Dialogue Portion is identified by the object identifier ss7-ProtectedDialogueAS or + +operationCode within an Invoke or ReturnResult Component takes the global value ss7-ProtectedDialogueAS or errorCode within an ReturnError Component takes the global value ss7-ProtectedDialogueAS. + +The decision box "message should be protected according to SPD" takes the "yes"-exit if the message's SCCP calling party address identifies a PLMN for which an SPD entry for incoming messages exists. + +The decision box "fall back allowed according to SPD" takes the "yes"-exit if the SPD entry for incoming messages is marked "fall back allowed". + +The decision box "calling party address consistent with SPI" takes the "yes"-exit if the SPI within the message's Security Header points to an SA that was negotiated with the PLMN derived from the message's SCCP calling party address. + +The decision box "protection mode acceptable according to SPD" takes the "yes"-exit if the protection mode within the message's Security Header is found in the SPD-entry for incoming messages. + + + +macrodefinition Inbound\_own\_to\_foreign + +1(1) + +``` +graph TD; Start([ ]) --> D1{message contains protectable parameter}; D1 -- no --> P1((pass)); D1 -- yes --> D2{message is not protected}; D2 -- no --> D3{called party address consistent with SPI}; D2 -- yes --> D4{message should be protected according to SPD}; D4 -- no --> P2((pass)); D4 -- yes --> D5{Fall Back allowed according to SPD}; D5 -- yes --> P3((pass)); D5 -- no --> B1((block)); D3 -- yes --> P4((pass)); D3 -- no --> D6{protection mode correct}; D6 -- yes --> P5((pass)); D6 -- no --> B2((block)); +``` + +Flowchart for macrodefinition Inbound\_own\_to\_foreign. The process starts with an oval connector. The first decision is 'message contains protectable parameter'. If 'no', it goes to a 'pass' connector. If 'yes', it goes to the next decision 'message is not protected'. If 'no', it goes to a third decision 'called party address consistent with SPI'. If 'yes', it goes to a 'pass' connector. If 'no', it goes to a fourth decision 'protection mode correct'. If 'yes', it goes to a 'pass' connector. If 'no', it goes to a 'block' connector. The third decision 'message should be protected according to SPD' has a 'no' exit to the 'pass' connector and a 'yes' exit to the fourth decision 'Fall Back allowed according to SPD'. The fourth decision 'Fall Back allowed according to SPD' has a 'yes' exit to a 'pass' connector and a 'no' exit to the 'block' connector. + +**Figure 5.1.4 Macro Inbound\_own\_to\_foreign (sheet 1 of 1)** + +The decision box "message contains protectable parameter" takes the "yes"-exit if user-information is present in the Dialogue Portion, or a parameter is present in an Invoke or ReturnError Component, or a result is present in a ReturnResult Component. + +The decision box "message is not protected" takes the "no"-exit if user-information within the Dialogue Portion is identified by the object identifier ss7-ProtectedDialogueAS or + +operationCode within an Invoke or ReturnResult Component takes the global value ss7-ProtectedDialogueAS or errorCode within an ReturnError Component takes the global value ss7-ProtectedDialogueAS. + +The decision box "message should be protected according to SPD" takes the "yes"-exit if the message's SCCP called party address identifies a PLMN for which an SPD entry for outgoing messages exists. + +The decision box "fall back allowed according to SPD" takes the "yes"-exit if the SPD entry for outgoing messages is marked "fall back allowed". + +The decision box "called party address consistent with SPI" takes the "yes"-exit if the SPI within the message's Security Header points to an SA that was negotiated with the PLMN derived from the message's SCCP called party address. + +The decision box "protection mode correct" takes the "yes"-exit if the presence/absence of octets 10 and 11 within the message's Security Header is consistent with the protection mode in the SPD-entry for outgoing messages. Note that octets 10 and 11 of the Security Header are only used to construct the IV which is not needed (and shall therefore be absent) if the protection mode is "authenticity and integrity". + + + +macrodefinition Inbound\_foreign\_to\_own + +1(2) + +``` +graph TD; Start([ ]) --> D1{message contains protectable parameter}; D1 -- no --> Pass1((pass)); D1 -- yes --> D2{message is not protected}; D2 -- no --> A((A)); D2 -- yes --> D3{relayed by SRF}; D3 -- no --> D4{message should be protected according to SPD (orig. network)}; D3 -- yes --> D5{message should be protected according to SPD (relay network)}; D5 -- no --> Pass2((pass)); D5 -- yes --> D6{Fall Back allowed according to SPD (relay network)}; D6 -- no --> Block((block)); D6 -- yes --> Pass3((pass)); D4 -- no --> Pass2; D4 -- yes --> D7{Fall Back allowed according to SPD (orig. network)}; D7 -- no --> Block; D7 -- yes --> Pass3; +``` + +The flowchart titled 'macrodefinition Inbound\_foreign\_to\_own' (sheet 1 of 2) outlines the decision logic for processing inbound messages from foreign networks. It begins with a start connector leading to a decision: 'message contains protectable parameter'. If 'no', the message is 'pass'. If 'yes', it proceeds to 'message is not protected'. If 'no', it goes to connector 'A'. If 'yes', it checks 'relayed by SRF'. If 'no', it proceeds to 'message should be protected according to SPD (orig. network)'. If 'yes', it checks 'message should be protected according to SPD (relay network)'. If 'no', it is 'pass'. If 'yes', it checks 'Fall Back allowed according to SPD (relay network)'. If 'no', it is 'block'. If 'yes', it is 'pass'. From 'message should be protected according to SPD (orig. network)', if 'no', it is 'pass'. If 'yes', it checks 'Fall Back allowed according to SPD (orig. network)'. If 'no', it is 'block'. If 'yes', it is 'pass'. + +Flowchart for macrodefinition Inbound\_foreign\_to\_own + +Figure 5.1.5 Macro Inbound\_foreign\_to\_own (sheet 1 of 2) + + + +macrodefinition Inbound\_foreign\_to\_own 2(2) + +``` +graph TD; A((A)) --> D1{calling party address consistent with SPI}; D1 -- yes --> DM[De-protect message]; D1 -- no --> D2{relayed by SRF}; D2 -- no --> B1((block)); D2 -- yes --> D3{protection mode acceptable according to SPD (relay network)}; D3 -- no --> B1; D3 -- yes --> DM; D3 -- no --> D4{protection mode acceptable according to SPD (orig. network)}; D4 -- yes --> DM; D4 -- no --> B2((block)); DM --> D5{success}; D5 -- yes --> P((pass)); D5 -- no --> B3((block)); +``` + +Flowchart for macrodefinition Inbound\_foreign\_to\_own (sheet 2 of 2). The process starts at node A. It enters a loop of decision boxes: 'calling party address consistent with SPI' (yes leads to 'De-protect message', no leads to 'relayed by SRF'), 'relayed by SRF' (yes leads to 'protection mode acceptable according to SPD (relay network)', no leads to 'block'), and 'protection mode acceptable according to SPD (relay network)' (yes leads to 'De-protect message', no leads to 'protection mode acceptable according to SPD (orig. network)'). The final decision 'protection mode acceptable according to SPD (orig. network)' (yes leads to 'De-protect message', no leads to 'block'). 'De-protect message' leads to 'success' (yes leads to 'pass', no leads to 'block'). + +**Figure 5.1.5 Macro Inbound\_foreign\_to\_own (sheet 2 of 2)** + +The decision box "message contains protectable parameter" takes the "yes"-exit if user-information is present in the Dialogue Portion, or a parameter is present in an Invoke or ReturnError Component, or a result is present in a ReturnResult Component. + +The decision box "message is not protected" takes the "no"-exit if user-information within the Dialogue Portion is identified by the object identifier ss7-ProtectedDialogueAS or + +operationCode within an Invoke or ReturnResult Component takes the global value ss7-ProtectedDialogueAS or errorCode within an ReturnError Component takes the global value ss7-ProtectedDialogueAS. + +The decision box "relayed by SRF" takes the "yes"-exit if the SCCP called party address consists of a Routing Number (RN) pointing to the own network and an MSISDN pointing to a relay network within the portability cluster. + +The decision box "message should be protected according to SPD (relay network)" takes the "yes"-exit if an SPD entry for incoming messages exists for the relay network. + +The decision box "Fall Back allowed according to SPD (relay network)" takes the "yes"-exit if the SPD entry for incoming messages (from the relay network) is marked "fall back allowed". + +The decision box "message should be protected according to SPD (orig. network)" takes the "yes"-exit if the message's SCCP calling party address identifies a PLMN for which an SPD entry for incoming messages exists. + +The decision box "Fall Back allowed according to SPD (relay network)" takes the "yes"-exit if the SPD entry for incoming messages (from the network identified by the SCCP calling party address) is marked "fall back allowed". + +The decision box "calling party address consistent with SPI" takes the "yes"-exit if the SPI within the message's Security Header points to an SA that was negotiated with the PLMN derived from the message's SCCP calling party address. + +The decision box "protection mode acceptable according to SPD (relay network)" takes the "yes"-exit if the presence/absence of octets 10 and 11 within the message's Security Header is consistent with a protection mode found in the SPD-entry (for incoming messages from the network identified by the SPI). Note that octets 10 and 11 of the Security Header are only used to construct the IV which is not needed (and shall therefore be absent) if the protection mode is "authenticity and integrity". + +The decision box "protection mode acceptable according to SPD (orig. network)" takes the "yes"-exit if the presence/absence of octets 10 and 11 within the message's Security Header is consistent with a protection mode found in the SPD-entry (for incoming messages from the network identified by the SCCP calling party address). Note that octets 10 and 11 of the Security Header are only used to construct the IV which is not needed (and shall therefore be absent) if the protection mode is "authenticity and integrity". + + + +macrodefinition Outbound\_own\_to\_own + +1(1) + +``` +graph TD; Start([ ]) --> D1{message contains protectable parameter}; D1 -- no --> Pass((pass)); D1 -- yes --> D2{message needs to be protected according to SPD}; D2 -- no --> Pass; D2 -- yes --> P[protect message]; P --> Pass; +``` + +Flowchart for macrodefinition Outbound\_own\_to\_own. It starts with a connector symbol, followed by a decision box 'message contains protectable parameter'. If 'no', it goes to a 'pass' connector. If 'yes', it goes to another decision box 'message needs to be protected according to SPD'. If 'no', it goes to the 'pass' connector. If 'yes', it goes to a 'protect message' box, which then leads to the 'pass' connector. + +**Figure 5.1.6 Macro Outbound\_own\_to\_own (sheet 1 of 1)** + +The decision box "message contains protectable parameter" takes the "yes"-exit if user-information is present in the Dialogue Portion, or a parameter is present in an Invoke or ReturnError Component, or a result is present in a ReturnResult Component. + +The decision box "message needs to be protected according to SPD" takes the "yes"-exit if an SPD entry for outgoing messages exists (for messages sent to the own network). + + + +macrodefinition Outbound\_own\_to\_foreign 1(1) + +``` +graph TD; Start([ ]) --> D1{message contains protectable parameter}; D1 -- no --> Pass((pass)); D1 -- yes --> D2{message is protected}; D2 -- yes --> Pass; D2 -- no --> D3{message needs to be protected according to SPD}; D3 -- no --> Pass; D3 -- yes --> P[protect message]; P --> Pass; +``` + +The flowchart illustrates the logic for the macro Outbound\_own\_to\_foreign. It begins with a start symbol (a circle with a vertical line) leading to a decision diamond labeled "message contains protectable parameter". If the answer is "no", the flow proceeds directly to a pass symbol (a circle with a vertical line). If the answer is "yes", it proceeds to the next decision diamond labeled "message is protected". If this second decision is "yes", the flow proceeds to the pass symbol. If the answer is "no", it proceeds to a third decision diamond labeled "message needs to be protected according to SPD". If the answer is "no", the flow proceeds to the pass symbol. If the answer is "yes", it proceeds to a process box labeled "protect message", which then leads to the pass symbol. + +Flowchart for macro Outbound\_own\_to\_foreign + +**Figure 5.1.7 Macro Outbound\_own\_to\_foreign (sheet 1 of 1)** + +The decision box "message contains protectable parameter" takes the "yes"-exit if user-information is present in the Dialogue Portion, or a parameter is present in an Invoke or ReturnError Component, or a result is present in a ReturnResult Component. + +The decision box "message is protected" takes the "yes"-exit if user-information within the Dialogue Portion is identified by the object identifier ss7-ProtectedDialogueAS or + +operationCode within an Invoke or ReturnResult Component takes the global value ss7-ProtectedDialogueAS or errorCode within an ReturnError Component takes the global value ss7-ProtectedDialogueAS. + +The decision box "message needs to be protected according to SPD" takes the "yes"-exit if an SPD entry for outgoing messages exists (for messages sent to the network identified by the SCCP called party address). + + + +macrodefinition Outbound\_foreign\_to\_own 1(1) + +``` +graph TD; Start([ ]) --> D1{message contains protectable parameter}; D1 -- no --> Pass((pass)); D1 -- yes --> D2{message needs to be protected according to SPD}; D2 -- no --> Pass; D2 -- yes --> P[protect message with reverse SA]; P --> Pass; +``` + +Flowchart for Outbound\_foreign\_to\_own macro. It starts with an oval connector, followed by a decision diamond 'message contains protectable parameter'. If 'no', it goes to a 'pass' connector. If 'yes', it goes to another decision diamond 'message needs to be protected according to SPD'. If 'no', it goes to the 'pass' connector. If 'yes', it goes to a process box 'protect message with reverse SA', which then leads to the 'pass' connector. + +**Figure 5.1.8 Macro Outbound\_foreign\_to\_own (sheet 1 of 1)** + +The decision box "message contains protectable parameter" takes the "yes"-exit if user-information is present in the Dialogue Portion, or + +a parameter is present in an Invoke or ReturnError Component, or a result is present in a ReturnResult Component. + +The decision box "message needs to be protected according to SPD" takes the "yes"-exit if an SPD entry for incoming messages exists (for messages received from the network identified by the SCCP calling party address). If more than one acceptable protection modes are present, one may be chosen. + +The task box "protect message with reverse SA" performs protection of the message with the SA that is to be used for de-protection when receiving messages from the network in question. + + + +macrodefinition Outbound\_foreign\_to\_foreign 1(1) + +``` +graph TD; Start([ ]) --> D1{message contains protectable parameter}; D1 -- no --> Pass((pass)); D1 -- yes --> D2{message is protected}; D2 -- yes --> Pass; D2 -- no --> D3{relayed by SRF}; D3 -- no --> Pass; D3 -- yes --> D4{message needs to be protected according to SPD}; D4 -- no --> Pass; D4 -- yes --> T1[protect message]; T1 --- T2[with SA own to foreign]; T1 --> Pass; +``` + +Flowchart for macro Outbound\_foreign\_to\_foreign. It starts with an oval connector, followed by a decision 'message contains protectable parameter'. If 'no', it goes to a 'pass' connector. If 'yes', it goes to a decision 'message is protected'. If 'yes', it goes to a 'pass' connector. If 'no', it goes to a decision 'relayed by SRF'. If 'no', it goes to a 'pass' connector. If 'yes', it goes to a decision 'message needs to be protected according to SPD'. If 'no', it goes to a 'pass' connector. If 'yes', it goes to a task 'protect message' which is associated with 'with SA own to foreign', and then to a 'pass' connector. + +Figure 5.1.9 Macro Outbound\_foreign\_to\_foreign (sheet 1 of 1) + +The decision box "message contains protectable parameter" takes the "yes"-exit if user-information is present in the Dialogue Portion, or a parameter is present in an Invoke or ReturnError Component, or a result is present in a ReturnResult Component. + +The decision box "message is protected" takes the "yes"-exit if user-information within the Dialogue Portion is identified by the object identifier ss7-ProtectedDialogueAS or operationCode within an Invoke or ReturnResult Component takes the global value ss7-ProtectedDialogueAS or errorCode within an ReturnError Component takes the global value ss7-ProtectedDialogueAS. + +The decision box "relayed by SRF" takes the "yes"-exit if the SCCP called party address consists of a Routing Number (RN) pointing to the own network and an MSISDN pointing to a relay network within the portability cluster. + +The decision box "message needs to be protected according to SPD" takes the "yes"-exit if an SPD entry for outgoing messages exists (for messages sent to the network identified by the SCCP called party address). + +### 5.1.2 Interactions with Mobile Number Portability + +In Mobile Number Portability scenarios (see 3GPP TS 23.066 [4]) a Signalling Relay Function (SRF) may relay SCCP traffic by modifying the SCCP called party address as shown in figure 4.1.10. + +A relayed message's SCCP called party address consists of a Routing Number (RN) and an MSISDN (see 3GPP TS 23.066 [4]). + +An SS7 Security Gateway needs to recognize (by analyzing the SCCP called party address) whether or not a message was relayed in order to + +- distinguish outbound transit traffic relayed by an SRF in the own network (which needs to be protected) from other outbound transit traffic (which needs to be passed transparently), and to +- distinguish inbound terminating traffic relayed by an SRF within the portability cluster (where the check needs to be based on the policy identified by the MSISDN within the SCCP called party address) from other inbound terminating traffic (where the check needs to be based on the policy identified by the SCCP calling party address). + +**NOTE :** In MNP-SRF scenarios, when the relaying PLMN does not make use of TCAP-User Security, messages sent from a source PLMN to a destination PLMN via the relaying PLMN are unprotected although protection may be desired for messages sent from the source PLMN to the destination PLMN. Network operators may therefore want to negotiate use of TCAP-User Security with all PLMNs of a portability cluster. + +### 5.1.3 Interactions with SCCP segmentation + +When the incoming SCCP message makes use of SCCP segmenting (i.e. several XUDT messages are received rather than one UDT or a single XUDT message) the SS7 Security Gateway has to perform reassembling before processing the message, and it may have to perform segmenting before sending the processed message. + +It may happen that the received SCCP message (containing an unprotected TCAP user payload) is not segmented (UDT or single XUDT), but after security processing the message's length is increased, so that the processed message needs to be segmented before it is sent. This situation may be undesired (since transfer of XUDT messages is not guaranteed by all transit networks) but cannot be avoided by the SS7 Security Gateway (see note). + +**Note:** The support of message segmentation at the SCCP layer in all transit networks could be enforced by mandating the usage of the White Book SCCP [9]. GSMA would work with International Carriers to ensure that fully operationally-verified support of XUDT is available before TCAPsec gateways are deployed. + +It may also happen that the received (protected) message is segmented (several XUDTs), but after security processing the message's length is decreased, so that the processed message does not need to be segmented before it is sent. In this case the de-protecting SS7 Security Gateway needs to know some SCCP-details of the original unprotected message as sent from the originating NE to the protecting SS7 Security Gateway. These original SCCP information needs to be transported within the TCAP-user parameter of the protected message. Depending on this information the de-protecting SS7-Security Gateway can decide whether to send a UDT or a single XUDT message towards the destination. . + +In cases where the received unprotected message is not segmented but the (to be) sent protected message needs to be segmented, the SS7 Security Gateway has to replace the message's SCCP calling party address with its own address. This is to guarantee uniqueness of the combination of the SCCP calling party address and the Segmentation local reference in the (to be) sent message. The original SCCP calling party address needs to be transported within the TCAP-user parameter of the (first segment of the) protected message. + +If the received protected message contains an original SCCP calling party address within the TCAP-user parameter, the de-protecting SS7 Security Gateway has to replace the SCCP calling party address with the original SCCP calling party address before forwarding the de-protected message to the destination. + +An SS7 Security Gateway that has sent a segmented, protected message with a replaced SCCP calling party address may receive an SCCP XUDTS message with its own address as called party address. In this case the SS7 Security Gateway shall retrieve the original SCCP calling party address, the original TCAP Message type and TCAP transaction id from the data parameter of the received XUDTS message and construct a UDT message with unmodified Return cause, called party address replaced with the retrieved original calling party address, unmodified calling party address, and Data parameter containing the retrieved TCAP message type and TCAP transaction id, and forward it to the destination. + +### 5.1.4 Protocol details + +#### 5.1.4.1 Transformation of unprotected message to protected message + +The unprotected TCAP-user message is either transported within an SCCP UDT message or it is transported within a single SCCP XUDT message or it is segmented over several SCCP XUDT messages. Other SCCP message types are not subject to protection. + +The transformation process is done in 3 steps: + +##### Step 1: SCCP re-assembly of the unprotected message + +In a first step the unprotected message is transformed into an intermediate unprotected representation which is made up of the following parameters: + +| | | +|-------------------------------------------------|--------------------------------------| +| SCCP Message type | | +| SCCP Protocol class | | +| SCCP Hop counter (optional) | | +| SCCP Called party address | | +| SCCP Calling party address | | +| SCCP Segmentation local reference (optional) | | +| SCCP Importance (optional) | | +| SCCP Data (made up of the following parameters: | TCAP Message type | +| | TCAP orig. Transaction Id (optional) | +| | TCAP dest. Transaction Id (optional) | +| | TCAP Dialogue Portion (optional) | +| | TCAP Component Portion (optional)) | + +If the unprotected message was transported within an SCCP UDT message, the intermediate unprotected representation of the message takes the following values: + +| | | +|-----------------------------------|-------------------------------------| +| SCCP Message type | UDT | +| SCCP Protocol class | same as in the received UDT message | +| SCCP Hop counter | absent | +| SCCP Called party address | same as in the received UDT message | +| SCCP Calling party address | same as in the received UDT message | +| SCCP Segmentation local reference | absent | +| SCCP Importance | absent | +| SCCP Data | same as in the received UDT message | + +If the unprotected message was transported within a single SCCP XUDT message, the intermediate unprotected representation of the message takes the following values: + +| | | +|-----------------------------------|--------------------------------------| +| SCCP Message type | XUDT | +| SCCP Protocol class | same as in the received XUDT message | +| SCCP Hop counter | same as in the received XUDT message | +| SCCP Called party address | same as in the received XUDT message | +| SCCP Calling party address | same as in the received XUDT message | +| SCCP Segmentation local reference | absent | +| SCCP Importance | same as in the received XUDT message | +| SCCP Data | same as in the received XUDT message | + +If the unprotected message was segmented over several SCCP XUDT messages, the intermediate unprotected representation of the message takes the following values: + +| | | +|-----------------------------------|-------------------------------------------------------------------------------------------------------| +| SCCP Message type | XUDT | +| SCCP Protocol class | same as in the first received XUDT message | +| SCCP Hop counter | same as in the first received XUDT message | +| SCCP Called party address | same as in the first received XUDT message | +| SCCP Calling party address | same as in the first received XUDT message | +| SCCP Segmentation local reference | same as in the first received XUDT message | +| SCCP Importance | same as in the first received XUDT message | +| SCCP Data | concatenation of the received segments (for details of the re-assembly procedure see ITU-T Q.714 [9]) | + +##### Step 2: Protection + +In a second step the intermediate unprotected representation is transformed into an intermediate protected representation which is made up of the following parameters: + +| | | +|----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------| +| SCCP Hop counter (optional) | | +| SCCP Called party address | | +| SCCP Calling party address | | +| SCCP Segmentation local reference (optional) | | +| SCCP Importance (optional) | | +| Original SCCP info (made up of the following parameters: | Original SCCP Calling party address (optional)Original SCCP Message type
Original SCCP Protocol class) | +| Original TCAP info (made up of the following parameters: | Original TCAP Message type
otid (optional)
dtid (optional)) | +| TCAPsec Security header | | +| TCAPsec Cipher- or Cleartext | | +| TCAPsecMAC | | + +The intermediate unprotected representation of the message takes the following values: + +| | | +|---------------------------------------------------------|----------------------------------------------------------------------------| +| SCCP Hop counter | same as SCCP Hop counter in the intermediate unprotected representation | +| SCCP Called party address | same as in the intermediate unprotected representation | +| SCCP Calling party address | same as in the intermediate unprotected representation | +| SCCP Segmentation local reference | same as in the intermediate unprotected representation | +| SCCP Importance | same as SCCP Importance in the intermediate unprotected representation | +| Original SCCP info made up of the following parameters: | | +| Original SCCP Message type | same as SCCP Message type in the intermediate unprotected representation | +| Original SCCP Protocol class | same as SCCP Protocol class in the intermediate unprotected representation | +| Original TCAP info made up of the following parameters: | | +| Original TCAP Message type | same as TCAP Message type in the intermediate unprotected representation | + +| | | +|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TCAP otid | same as TCAP orig. Transaction Id in the intermediate unprotected representation | +| TCAP dtid | same as TCAP dest. Transaction Id in the intermediate unprotected representation | +| TCAPsec Security header | See 3GPP TS 33.204 [8] | +| TCAPsec Cipher- or Cleartext | result of applying the encryption function to the concatenation of Dialogue Portion and Component Portion of the intermediate unprotected representation (ciphertext), or concatenation of Dialogue Portion and Component Portion of the intermediate unprotected representation(cleartext) | +| TCAPsec MAC | result of applying the integrity function to the concatenation of Security header and Cipher- or Cleartext of the intermediate protected representation. | + +##### Step 3: SCCP segmentation of the protected message + +In a third step the intermediate protected representation is transformed into a single SCCP UDT message, a single SCCP XUDT message, or several SCCP XUDT messages depending on the Original SCCP Message type of the intermediate protected representation and the need for segmentation as follows: + +If the Original SCCP Message type in the intermediate protected representation takes the value "UDT" and the message need not be segmented, it is transformed into a single SCCP UDT message with following parameter values: + +| | | +|-----------------------|-----------------------------------------------------------------------------------| +| Message Type | UDT | +| Protocol class | same as Original SCCP Protocol class in the intermediate protected representation | +| Called party address | same as SCCP Called party address in the intermediate protected representation | +| Calling party address | same as SCCP Calling party address in the intermediate protected representation | +| Data | (see below) | + +If the Original SCCP Message type in the intermediate protected representation takes the value "XUDT" and the message need not be segmented, it is transformed into a single SCCP XUDT message with following parameter values: + +| | | +|-----------------------|-----------------------------------------------------------------------------------| +| Message Type | XUDT | +| Protocol class | same as Original SCCP Protocol class in the intermediate protected representation | +| Hop counter | same as Original SCCP Hop counter in the intermediate protected representation | +| Called party address | same as SCCP Called party address in the intermediate protected representation | +| Calling party address | same as SCCP Calling party address in the intermediate protected representation | +| Data | (see below) | +| Segmentation | absent | +| Importance | same as Original SCCP Importance in the intermediate protected representation | + +If the Original SCCP Message type in the intermediate protected representation takes the value "UDT" and the message needs to be segmented, it is transformed into several SCCP XUDT message with following parameter values: + +| | | +|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Message Type | XUDT | +| Protocol class | first segment: class 1 (in sequence delivery), return option: same as in Original SCCP Protocol class in the intermediate protected representation
subsequent segment: class 1 (in sequence delivery), return option: no special options | +| Hop counter | absent | +| Called party address | same as SCCP Called party address in the intermediate protected representation | +| Calling party address | the SS7 Security Gateway's own address | +| Data | (segment of see below) | +| Segmentation | see [9] | +| Importance | absent | + +If the Original SCCP Message type in the intermediate protected representation takes the value "XUDT" and the message needs to be segmented, it is transformed into several SCCP XUDT message with following parameter values: + +| | | +|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Message Type | XUDT | +| Protocol class | first segment: class 1 (in sequence delivery), return option: same as in Original SCCP Protocol class in the intermediate protected representation
subsequent segment: class 1 (in sequence delivery), return option: no special options | +| Hop counter | same as Original SCCP Hop counter in the intermediate protected representation | + +| | | +|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Called party address | same as SCCP Called party address in the intermediate protected representation | +| Calling party address | if SCCP Segmentation Local reference is present in the intermediate protected representation: same as SCCP Calling party address in the intermediate protected representation;
otherwise: the SS7 Security Gateway's own address | +| Data | (segment of see below) | +| Segmentation | see [9]; if SCCP Segmentation Local reference is present in the intermediate protected representation, the same value shall be used. | +| Importance | same as Original SCCP Importance in the intermediate protected representation. | + +The SCCP Data parameter (re-assembled) shall take the following value: + +| | | +|-----------------------|----------------------------------| +| TCAP Message type | unidirectional | +| TCAP DialoguePortion | absent | +| TCAP ComponentPortion | one invoke component with: | +| invokeId | (any legal value) | +| linkId | absent | +| operationCode | local value 90 (secureTransport) | +| parameter | ANY DEFINED BY operationCode | + +``` +SS7-Secure-Transport-Operation-and-DataTypes { + itu-t identified-organization (4) etsi (0) mobileDomain (0) + gsm-Network (1) modules (3) ss7-Secure-Transport-Operation-and-DataTypes (27) version1 (1)} +``` + +``` +DEFINITIONS +IMPLICIT TAGS +::= +BEGIN +``` + +``` +EXPORTS + secureTransport +; +``` + +``` +IMPORTS + OPERATION +FROM Remote-Operations-Information-Objects { + joint-iso-itu-t remote-operations (4) + informationObjects (5) version1 (0) } + +; +``` + +| | +|--------------------------------------------------------------------------------------------------------| +|
secureTransport OPERATION ::= { ARGUMENT SecureTransportArg CODE local:90 } |
+|--------------------------------------------------------------------------------------------------------|
+
+| |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| SecureTransportArg ::= SEQUENCE { originalSCCP-Info [0] OriginalSCCP-Info OPTIONAL, originalTCAP-Info [1] OriginalTCAP-Info, protectedPayload [2] ProtectedPayload } |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+| |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| OriginalSCCP-Info ::= SEQUENCE { originalSCCP-MessageType [0] OriginalSCCP-MessageType OPTIONAL, -- original SCCP-MessageType shall be present if it is different from the actual -- SCCP-Message type; otherwise it may be absent originalSCCP-ProtocolClass [1] OriginalSCCP-ProtocolClass OPTIONAL -- originalSCCP-ProtocolClass shall be present if it is different from the actual -- SCCP-Protocol class (first segment); otherwise it may be absent. originalSCCP-CallingPartyAddress [2] OriginalSCCP-CallingPartyAddress OPTIONAL, -- originalSCCP-CallingPartyAddress shall be present if and only if the actual -- SCCP Calling party address is the SS7 Security Gateway's own address } |
+|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+
+```
+
+OriginalSCCP-MessageType ::= ENUMERATED {
+ udt (9),
+ xudt (17) }
+ -- this parameter shall take the value of the Original SCCP Message type from the
+ -- intermediate protected representation
+}
+
+OriginalSCCP-ProtocolClass ::= OCTET STRING(SIZE(1))
+ -- coded according to ITU-T Q.713
+}
+
+OriginalSCCP-CallingPartyAddress ::= OCTET STRING(SIZE(3..18))
+ -- coded according to ITU-T Q.713
+ -- Octet 1: Address indicator
+ -- Octets 2 - n: Address
+}
+
+OriginalTCAP-Info ::= SEQUENCE {
+ originalTCAP-MessageType OriginalTCAP-MessageType,
+ otid OTID OPTIONAL,
+ dtid DTID OPTIONAL
+}
+
+OriginalTCAP-MessageType ::= ENUMERATED {
+ unidirectional (97),
+ begin (98),
+ end (100),
+ continue (101),
+ abort (103) }
+ -- this parameter shall take the value of the Original TCAP Message type from the
+ -- intermediate protected representation
+}
+
+OTID ::= OCTET STRING(SIZE(1..4))
+ -- OTID shall take the value of the TCAP otid from the intermediate protected
+ -- representation
+}
+
+DTID ::= OCTET STRING(SIZE(1..4))
+ -- DTID shall take the value of the TCAP dtid from the intermediate protected
+ -- representation
+}
+
+ProtectedPayload ::= OCTET STRING(SIZE(13..3438))
+ -- The protected payload is the concatenation of
+ -- 9 or 11 octets SecurityHeader,
+ -- n octets ciphertext or cleartext, and
+ -- 4 octets MAC
+
+ -- The SecurityHeader is coded as follows (see 3GPP TS 33.204 [8]):
+ -- Octets 1-4: SPI
+ -- Octets 5-8: TVP. The TVP is a 32 bit time stamp. Its value is binary coded
+ --
+ -- and indicates the number of intervals of 100 milliseconds
+ -- elapsed since 1st January 2002, 0:00:00 UTC
+ -- Octet 9: Indicator Byte with bits 7-1 spare and bit 0 if set indicates presence of
+ -- Octets 10-11
+ -- Octet 10: SS7 SEG-Id
+ -- Octet 11: Prop
+}
+
+```
+
+END
+
+#### 5.1.4.2 Transformation of protected message to unprotected message
+
+The protected TCAP-user message is either transported within an SCCP UDT message or it is transported within a single SCCP XUDT message or it is segmented over several SCCP XUDT messages. Other SCCP message types are not subject to protection.
+
+The transformation process is done in 3 steps:
+
+##### Step 1: SCCP re-assembly of the protected message
+
+In a first step the protected message is transformed into the intermediate protected representation (see chapter 5.1.4.1):
+
+If the protected message was transported within an SCCP UDT message, the intermediate protected representation of the message takes the following values:
+
+| | |
+|-------------------------------------|---------------------------------------------------------------------------------------------------|
+| SCCP Hop counter | absent |
+| SCCP Called party address | same as in the received UDT message |
+| SCCP Calling party address | same as in the received UDT message |
+| SCCP Segmentation local reference | absent |
+| SCCP Importance | absent |
+| Original SCCP info | |
+| Original SCCP Calling party address | absent |
+| Original SCCP Message type | UDT |
+| Original SCCP Protocol class | same as SCCP Protocol class in the received UDT message |
+| Original TCAP info | |
+| Original TCAP Message type | same as Original TCAP Message type in the TCAP-invoke component parameter of the received message |
+| otid | same as otid in the TCAP-invoke component parameter of the received message |
+| dtid | same as dtid in the TCAP-invoke component parameter of the received message |
+| TCAPsec Security header | same as received in the TCAP-invoke component parameter of the received message |
+| TCAPsec Cipher- or Cleartext | same as received in the TCAP-invoke component parameter of the received message |
+| TCAPsec MAC | same as received in the TCAP-invoke component parameter of the received message |
+
+If the protected message was transported within a single SCCP XUDT message, the intermediate protected representation of the message takes the following values:
+
+| | |
+|-------------------------------------|---------------------------------------------------------------------------------------------------|
+| SCCP Hop counter | same as in the received XUDT message |
+| SCCP Called party address | same as in the received XUDT message |
+| SCCP Calling party address | same as in the received XUDT message |
+| SCCP Segmentation local reference | absent |
+| SCCP Importance | same as in the received XUDT message |
+| Original SCCP info | |
+| Original SCCP Calling party address | absent |
+| Original SCCP Message type | same as OriginalSCCP-Messagetype in the TCAP-invoke component parameter of the received message |
+| Original SCCP Protocol class | same as OriginalSCCP-ProtocolClass in the TCAP-invoke component parameter of the received message |
+| Original TCAP info | |
+| Original TCAP Message type | same as Original TCAP Message type in the TCAP-invoke component parameter of the received message |
+| otid | same as otid in the TCAP-invoke component parameter of the received message |
+| dtid | same as dtid in the TCAP-invoke component parameter of the received message |
+| TCAPsec Security header | same as received in the TCAP-invoke component parameter of the received message |
+| TCAPsec Cipher- or Cleartext | same as received in the TCAP-invoke component parameter of the received message |
+| TCAPsec MAC | same as received in the TCAP-invoke component parameter of the received message |
+
+If the protected message was transported within several SCCP XUDT message, the intermediate protected representation of the message takes the following values:
+
+| | |
+|---------------------------|--------------------------------------------|
+| SCCP Hop counter | same as in the first received XUDT message |
+| SCCP Called party address | same as in the first received XUDT message |
+
+| | |
+|-------------------------------------|---------------------------------------------------------------------------------------------------------------------|
+| SCCP Calling party address | same as in the first received XUDT message |
+| SCCP Segmentation local reference | same as in the first received XUDT message |
+| SCCP Importance | same as in the first received XUDT message |
+| Original SCCP info | |
+| Original SCCP Calling party address | same as OriginalSCCP-CallingPartyAddress in the TCAP-invoke component parameter of the received reassembled message |
+| Original SCCP Message type | same as OriginalSCCP-MessageType in the TCAP-invoke component parameter of the received reassembled message |
+| Original SCCP Protocol class | same as OriginalSCCP-ProtocolClass in the TCAP-invoke component parameter of the received reassembled message |
+| Original TCAP info | |
+| Original TCAP Message type | same as OriginalTCAP-MessageType in the TCAP-invoke component parameter of the received reassembled message |
+| otid | same as otid in the TCAP-invoke component parameter of the received reassembled message |
+| dtid | same as dtid in the TCAP-invoke component parameter of the received reassembled message |
+| TCAPsec Security header | same as received in the TCAP-invoke component parameter of the received reassembled message |
+| TCAPsec Cipher- or Cleartext | same as received in the TCAP-invoke component parameter of the received reassembled message |
+| TCAPsec MAC | same as received in the TCAP-invoke component parameter of the received reassembled message |
+
+##### Step 2: De-Protection
+
+In a second step the intermediate protected representation is transformed into an intermediate unprotected representation (see chapter 5.1.4.1):
+
+The intermediate unprotected representation of the message takes the following values:
+
+| | |
+|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| SCCP Message type | same as OriginalSCCP-MessageType from the TCAP-invoke component's parameter of the intermediate protected representation |
+| SCCP Protocol class | same as OriginalSCCP-ProtocolClass from the TCAP-invoke component's parameter of the intermediate protected representation |
+| SCCP Hop counter | same as SCCP Hop counter in the intermediate protected representation |
+| SCCP Called party address | same as SCCP Called party address in the intermediate protected representation |
+| SCCP Calling party address | if OriginalSCCP-CallingPartyAddress is present in the intermediate protected representation, its value is taken; otherwise same as SCCP Calling party address of the intermediate protected representation |
+| SCCP Segmentation local reference | if SCCP Message type in the intermediate unprotected representation is XUDT, then same as in the intermediate protected representation; otherwise absent. |
+| SCCP Importance | same as in the intermediate unprotected representation |
+| SCCP Data : | |
+| TCAP Message type | same as OriginalTCAP-MessageType in the intermediate protected representation |
+| TCAP orig. Transaction Id | same as otid in the intermediate protected representation |
+| TCAP dest. Transaction Id | same as dtid in the intermediate protected representation |
+| TCAP Dialogue Portion (optional) | First part of the cleartext (as indicated by TAG and LENGTH according to BER). If encryption was applied then ciphertext needs to be converted first to cleartext |
+| TCAP Component Portion (optional) | second part of the cleartext (as indicated by TAG and LENGTH according to BER). If encryption was applied then ciphertext needs to be converted first to cleartext |
+
+##### Step 3: SCCP segmentation of the unprotected message
+
+In a third step the intermediate unprotected representation is transformed into a single SCCP UDT message, a single SCCP XUDT message, or several SCCP XUDT messages depending on the SCCP Message type of the intermediate unprotected representation and the need for segmentation as follows:
+
+If the SCCP Message type in the intermediate unprotected representation is "UDT", it is transformed into a single SCCP UDT message with following parameter values:
+
+| | |
+|-----------------------|-----------------------------------------------------------------------------------|
+| Message Type | UDT |
+| Protocol class | same as SCCP Protocol class in the intermediate unprotected representation |
+| Called party address | same as SCCP Called party address in the intermediate unprotected representation |
+| Calling party address | same as SCCP Calling party address in the intermediate unprotected representation |
+| Data | same as SCCP Data in the intermediate unprotected representation |
+
+If the SCCP Message type in the intermediate unprotected representation is "XUDT" and the message does not need to be segmented, it is transformed into a single SCCP XUDT message with following parameter values:
+
+| | |
+|-----------------------|-----------------------------------------------------------------------------------|
+| Message type | XUDT |
+| Protocol class | same as SCCP Protocol class in the intermediate unprotected representation |
+| Hop counter | same as SCCP Hop counter in the intermediate unprotected representation |
+| Called party address | same as SCCP Called party address in the intermediate unprotected representation |
+| Calling party address | same as SCCP Calling party address in the intermediate unprotected representation |
+| Data | same as SCCP Data in the intermediate unprotected representation |
+| Segmentation | absent |
+| Importance | same as SCCP Importance in the intermediate unprotected representation |
+
+If the SCCP Message type in the intermediate unprotected representation is "XUDT" and the message needs to be segmented, it is transformed into several SCCP XUDT message with following parameter values:
+
+| | |
+|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
+| Message type (all segments) | XUDT |
+| Protocol class (first segment) | class 1 (in sequence delivery), return option: same as in SCCP Protocol class of the intermediate unprotected representation |
+| (subsequent segments) | class 1 (in sequence delivery), return option: no special options |
+| Hop counter (all segments) | same as SCCP Hop counter in the intermediate unprotected representation |
+| Called party address (all segments) | same as SCCP Called party address in the intermediate unprotected representation |
+| Calling party address (all segments) | same as SCCP Calling party address in the intermediate unprotected representation |
+| Data | segment of SCCP Data from the intermediate unprotected representation (see ITU-T Q.714 [9]) |
+| Segmentation | see [9]. Local reference shall be taken from the intermediate unprotected representation |
+| Importance (all segments) | same as SCCP Importance in the intermediate unprotected representation |
+
+#### 5.1.4.3 Handling of received XUDTS messages and UDTS messages
+
+An SS7 Security Gateway shall not try to re-assemble XUDTS messages, since the SCCP option "return on error" is not set for subsequent XUDT segments. As a consequence the SS7 Security Gateway shall not try to protect or de-protect XUDTS messages (fragments) or UDTS messages. However, special handling of XUDTS messages and UDTS messages is required as follows:
+
+##### Outbound direction
+
+Instead of re-assembling and protecting the XUDTS messages or protecting UDTS messages, the SS7 Security Gateway shall remove the TCAP Dialogue Portion and the TCAP Component Portion from the SCCP Data parameter before sending the XUDTS message or UDTS message. This is in order not to pass the cleartext (or fragment of the cleartext) in outbound direction. SCCP message type and addresses shall not be changed.
+
+An example is shown in figure 5.1.4.3-1: A transit node in PLMN 2 cannot deliver the UDT message and therefore returns an UDTS message. SS7 Security Gateway 2 in PLMN 2 removes the cleartext (TCAP dialogue portion and TCAP component portion) from the SCCP data parameter. SS7 Security Gateway 1 in PLMN 1 recognizes that the
+
+received UDT message does not contain a TCAP unidirectional message with a secure transport invoke component and therefore it does not modify the SCCP message.
+
+
+
+```
+
+sequenceDiagram
+ participant NE1 as NE 1
+ participant SGW1 as SS7 Sec Gateway 1
+ participant SGW2 as SS7 Sec Gateway 2
+ participant TN as Transit Node
+ participant NE2 as NE 2
+
+ Note left of NE1: PLMN 1
+ Note right of NE2: PLMN 2
+
+ NE1->>SGW1: UDT
+ SGW1->>SGW2: XUDT
+ SGW1->>SGW2: XUDT
+ SGW2->>TN: UDT
+ TN->>SGW2: UDT
+ SGW2->>SGW1: UDT
+ SGW1->>NE1: UDT
+
+```
+
+Sequence diagram showing message exchanges between NE 1, SS7 Sec Gateway 1, SS7 Sec Gateway 2, Transit Node, and NE 2 across PLMN 1 and PLMN 2.
+
+**Figure 5.1.4.3-1: XUDTS messages and UDTS messages (Outbound direction)**
+
+##### Inbound direction
+
+Instead of re-assembling and de-protecting the XUDTS messages or de-protecting UDTS messages, the SS7 Security Gateway shall analyze the SCCP Called party address. If it matches with the SS7 Security Gateway's own address, it shall recover the OriginalSCCP-CallingPartyAddress from the (fragment in the) data parameter and replace the SCCP Called party address with the recovered value. In any case the SS7 Security Gateway shall recover and analyze the TCAP Message type from the (fragment in the) data parameter. If the recovered value is "unidirectional" and a invoke component with operation code "secure transport" is included, the SS7 Security Gateway shall recover the originalTCAP-MessageType, otid, and dtid from the OriginalTCAP-Info, replace the TCAP Message type with the original TCAP-MessageType, insert otid and dtid and remove the remaining material from the SCCP data parameter. If the received message is an XUDTS message and the original SCCP Message type was UDT then the SS7 Security shall modify the SCCP Message type to UDTS.
+
+An example is shown in figure 5.1.4.3-2: A transit node in a transit network cannot deliver the XUDT messages and therefore returns an XUDTS message (note that the second XUDT does not have the SCCP return option set). SS7 Security Gateway 1 in PLMN 1 recognizes that the received XUDTS message does contain a TCAP unidirectional message with a secure transport invoke component and therefore, since the original SCCP-MessageType is UDT, modifies the SCCP Message type from XUDTS to UDTS. Furthermore, the TCAP Message type is modified from unidirectional to the original TCAP-MessageType, the Transaction Ids are inserted, and the remaining material (fragment of the ciphertext) is removed.
+
+In addition the SS7 Security Gateway 1 in PLMN 1 recognizes that the received XUDTS message does contain SS7 Security Gateway 1's own address as SCCP Called party address and therefore replaces it with the original SCCPCalling party address.
+
+
+
+The diagram illustrates a sequence of messages between network elements (NEs) and gateways across two PLMNs. PLMN 1 contains NE 1, SS7 Sec Gateway 1, and a Transit Node. PLMN 2 contains SS7 Sec Gateway 2 and NE 2. The message flow is as follows:
+
+- NE 1 sends a UDT message to SS7 Sec Gateway 1.
+- SS7 Sec Gateway 1 sends two XUDT messages to the Transit Node.
+- The Transit Node sends an XUDTS message back to SS7 Sec Gateway 1.
+- SS7 Sec Gateway 1 sends a UDTS message back to NE 1.
+
+```
+sequenceDiagram
+ participant NE1 as NE 1
+ participant SS7G1 as SS7 Sec Gateway 1
+ participant TN as Transit Node
+ participant SS7G2 as SS7 Sec Gateway 2
+ participant NE2 as NE 2
+
+ Note left of NE1: PLMN 1
+ Note right of NE2: PLMN 2
+
+ NE1->>SS7G1: UDT
+ SS7G1->>TN: XUDT
+ SS7G1->>TN: XUDT
+ TN->>SS7G1: XUDTS
+ SS7G1->>NE1: UDTS
+```
+
+Sequence diagram showing message exchanges between NE 1, SS7 Sec Gateway 1, Transit Node, SS7 Sec Gateway 2, and NE 2 across PLMN 1 and PLMN 2.
+
+Figure 5.1.4.3-2: XUDTS messages and UDTS messages (inbound direction)
+
+# --- Annex A (informative): Change history
+
+| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | New |
+|---------|--------|-----------|------|-----|----------------------------------------------------|--------|
+| 2006-06 | CT#32 | CP-060320 | | | Approved as version 7.0.0 | 7.0.0 |
+| 2006-09 | CT#33 | CP-060413 | 0001 | | Addition of abbreviations and correction of a note | 7.1.0 |
+| 2008-12 | CT#42 | | | | Upgraded unchanged from Rel-7 | 8.0.0 |
+| 2009-12 | - | - | - | - | Update to Rel-9 version (MCC) | 9.0.0 |
+| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 10.0.0 |
+| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 11.0.0 |
+| 2014-09 | - | - | - | - | Update to Rel-12 version (MCC) | 12.0.0 |
+| 2015-12 | CT#70 | - | - | - | Update to Rel-13 version (MCC) | 13.0.0 |
+| 2017-03 | CT#75 | - | - | - | Update to Rel-14 version (MCC) | 14.0.0 |
+| 2018-06 | CT#80 | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 |
+| 2020-07 | CT#88e | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 |
\ No newline at end of file
diff --git a/marked/Rel-16/29_series/29205/raw.md b/marked/Rel-16/29_series/29205/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..8f26ebd5aa6a11bd4c20b0b95d4913a40fe8c3ed
--- /dev/null
+++ b/marked/Rel-16/29_series/29205/raw.md
@@ -0,0 +1,948 @@
+
+
+
+
+
+
+# Contents
+
+| | |
+|--------------------------------------------------------------------------|-----------|
+| Foreword ..... | 5 |
+| 1 Scope..... | 6 |
+| 2 References..... | 6 |
+| 3 Definitions, symbols and abbreviations ..... | 7 |
+| 3.1 Definitions..... | 7 |
+| 3.2 Symbols..... | 7 |
+| 3.3 Abbreviations ..... | 7 |
+| 4 Protocols..... | 8 |
+| 4.1 Call control protocol (Nc interface) ..... | 8 |
+| 4.2 Interworking with other protocols..... | 8 |
+| 4.3 Resource control protocol (G)MSC and MGW (Mc Interface) ..... | 8 |
+| 4.4 Bearer control protocol between MGWs (Nb interface)..... | 9 |
+| 4.5 Signalling Transport..... | 9 |
+| 4.5.1 Call Control protocols ..... | 9 |
+| 4.5.2 Resource control protocol (G)MSC and MGW (Mc Interface) ..... | 9 |
+| 4.5.3 Bearer control protocol between MGWs (Nb interface) ..... | 9 |
+| Annex A: Void..... | 9 |
+| Annex B (normative): Transparent Support of Mobile Services ..... | 9 |
+| B.1 Introduction..... | 9 |
+| B.2 Mobile Service Transport (MST) – Format and Codes ..... | 10 |
+| B.2.1 Encapsulated Application Information..... | 10 |
+| B.2.1.1 General Layout ..... | 10 |
+| B.2.1.2 List of Identifiers ..... | 12 |
+| B.2.1.3 Mobile Equipment Identifier ..... | 12 |
+| B.2.1.4 LCLS Negotiation Request..... | 13 |
+| B.2.1.5 LCLS Negotiation Response ..... | 13 |
+| B.2.1.6 LCLS Status..... | 14 |
+| B.2.1.7 LCLS Status Change ..... | 14 |
+| B.2.1.8 LCLS Status Result ..... | 14 |
+| B.2.1.9 LCLS Global Call Reference..... | 15 |
+| B.2.1.10 LCLS Configuration Preference..... | 16 |
+| B.2.1.11 LCLS Configuration Change Request..... | 17 |
+| B.2.1.12 LCLS Configuration Change Result ..... | 17 |
+| B.2.2 Application Transport Instruction Indicators ..... | 18 |
+| Annex C (normative): LCLS Service Application ..... | 18 |
+| C.1 Use of MST ASE ..... | 18 |
+| C.2 Procedures..... | 18 |
+| C.2.1 Indication of LCLS Capability ..... | 18 |
+| C.2.1.1 LCLS Service Capability Indication ..... | 18 |
+| C.2.1.2 Actions at Originating Serving Node ..... | 19 |
+| C.2.1.3 Actions at Intermediate Serving Node..... | 19 |
+| C.2.1.4 Actions at Destination Serving Node ..... | 19 |
+| C.2.2 Backward LCLS Negotiation during Call Setup..... | 20 |
+| C.2.2.1 Introduction ..... | 20 |
+| C.2.2.2 Actions at Destination Serving Node ..... | 20 |
+| C.2.2.3 Actions at Intermediate Serving Node..... | 20 |
+| C.2.2.4 Actions at Originating Serving Node ..... | 20 |
+| C.2.3 Answer message..... | 21 |
+| C.2.3.1 Introduction ..... | 21 |
+| C.2.3.2 Actions at Destination Serving Node ..... | 21 |
+| C.2.3.3 Actions at Intermediate Serving Node..... | 21 |
+
+- C.2.3.4 Actions at Originating Serving Node ..... 21
+- C.2.4 LCLS Configuration Change Request..... 21
+- C.2.4.1 Introduction ..... 21
+- C.2.4.2 Actions at Initiating Serving Node ..... 22
+- C.2.4.3 Actions at Intermediate Serving Node..... 22
+- C.2.4.4 Actions at Terminating Serving Node ..... 22
+- C.2.5 LCLS Status Update..... 22
+- C.2.5.1 Introduction ..... 22
+- C.2.5.2 Actions at Initiating Serving Node ..... 23
+- C.2.5.3 Actions at Intermediate Serving Node..... 23
+- C.2.5.4 Actions at Terminating Serving Node ..... 23
+- C.2.6 LCLS Status Change Request..... 23
+- C.2.6.1 Introduction ..... 23
+- C.2.6.2 Actions at Initiating Serving Node ..... 23
+- C.2.6.3 Actions at Intermediate Serving Node..... 24
+- C.2.6.4 Actions at Terminating Serving Node ..... 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 describes the protocols to be used when ITU-T Q.1902 "Bearer Independent Call Control" is used as call control protocol in a 3GPP Bearer Independent CS core network 3GPP TS 23.205 [1]. The Q.1902 operates between (G)MSC servers. The BICC architecture as described in ITU-T Q.1902 [6]-[10] consists of a number of protocols. The following types of protocols are described: call control protocol, bearer control protocols and a resource control protocol for this architecture. The architecture complies with the requirements imposed by 3GPP TS 23.205 [1] and TS 23.153 [2].
+
+The present document is valid for a 3rd generation PLMN (UMTS) complying with Release 4 and later.
+
+Note: Q.1902 can be used in other network architectures than the one defined in 3GPP TS 23.205 [1]
+
+# --- 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 23.205: "Bearer Independent CS Core Network – Stage 2".
+- [2] 3GPP TS 23.153: "Out of Band Transcoder Control - Stage 2".
+- [3] 3GPP TS 29.232: "Media Gateway Controller (MGC) – Media Gateway (MGW) Interface; Stage 3".
+- [4] 3GPP TS 29.414: "Core Network Nb Data Transport and Signalling Transport".
+- [5] ITU-T Recommendation Q.765.5 (06/2000): "Application Transport Mechanism".
+- [6] ITU-T Recommendation Q.1902.1 (07/2001): "Bearer Independent Call Control CS2 Functional Description". Inclusive Amendment 3: "Support for the Customized Alerting Tone (CAT) service".
+- [7] ITU-T Recommendation Q.1902.2 (07/2001): "Bearer Independent Call Control CS2 General functions of messages and parameters". Inclusive Amendment 5: "Support for the Customized Alerting Tone (CAT) service".
+- [8] ITU-T Q.1902.3 (07/2001): "Bearer Independent Call Control CS2 Formats and Codes". Inclusive Amendment 5: "Support for the Customized Alerting Tone (CAT) service".
+- [9] ITU-T Recommendation Q.1902.4 (07/2001): "Bearer Independent Call Control CS2 Basic Call Procedures".
+- [10] ITU-T Recommendation Q.1902.5 (07/2001): "Exceptions to the Application Transport Mechanism in the Context of Bearer Independent Call Control".
+- [11] ITU-T Recommendation Q.1902.6 (07/2001): "Generic Signalling Procedures for the support of the ISDN User Part Supplementary Services and for bearer redirection".
+- [12] ITU-T Recommendation Q.1950 (07/2001): "Call Bearer Control Protocol".
+- [13] ITU-T Recommendations Q.2630.1 (12/1999), Q.2630.2 (12/2000): "AAL type 2 signalling protocol".
+- [14] ITU-T Recommendation Q.1990 (07/2001): "BICC Bearer Control tunnelling protocol".
+
+- [15] ITU-T Recommendation Q.1970 (07/2001): "BICC IP Bearer Control protocol".
+- [16] ITU-T Recommendation Q.1912.1 (07/2001): "Interworking between Signalling System No. 7 ISDN user part and the Bearer Independent Call Control protocol".
+- [17] ITU-T Recommendation Q.1912.2 (07/2001): "Interworking between selected Signalling System (PSTN Access DSS1, C5, R1, R2, TUP) and the Bearer Independent Call Control Protocol".
+- [18] ITU-T Recommendation Q.2150.0 (05/2001): "Generic Signalling Transport Service".
+- [19] ITU-T Recommendation Q.2150.1 (05/2001): "Signalling Transport Converter on MTP3 and MTP3b".
+- [20] ITU-T Recommendation Q.2150.3 (12/2002): "Signalling Transport Converter on SCTP".
+- [21] ITU-T Recommendation H.248.4 (11/2000): "Gateway Control Protocol: Transport over SCTP".
+- [22] 3GPP TS 29.202: "SS7 signalling transport in core network".
+- [23] ITU-T Recommendation H.248.5 (11/2000): "Gateway control protocol: Transport over ATM".
+- [24] ITU-T Q.765 (06/2000): "Signalling system No. 7 – Application transport mechanism".
+- [25] 3GPP TS 23.003: "Numbering, addressing and identification".
+- [26] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2".
+- [27] 3GPP TS 23.237: "IP Multimedia subsystem (IMS) Service Continuity; Stage 2".
+- [28] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
+- [29] 3GPP TS 23.284: "Local Call Local Switch; Stage 2".
+
+# --- 3 Definitions, symbols and abbreviations
+
+## 3.1 Definitions
+
+## 3.2 Symbols
+
+For the purposes of the present document, the following symbols apply:
+
+| | |
+|----|-----------------------------------------------------|
+| Nc | Interface between the (G)MSC servers. |
+| Mc | Interface between the server and the media gateway. |
+| Nb | Interface between media gateways (MGW). |
+
+## 3.3 Abbreviations
+
+For the purposes of the present document, the abbreviations as defined in 3GPP TR 21.905 [28] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [28].
+
+| | |
+|------|----------------------------------|
+| APM | Application Transport Mechanism |
+| | Application Transport Message |
+| APP | Application Transport Parameter |
+| BAT | Bearer Association Transport |
+| BICC | Bearer Independent Call Control |
+| C5 | CCITT signalling system number 5 |
+| GCR | Global Call Reference |
+| LCLS | Local Call Local Switch |
+| M3UA | MTP3 – User Adaptation Layer |
+| MGC | Media Gateway Controller |
+| MST | Mobile Service Transport |
+| R1 | Regional Signalling System 1 |
+
+| | |
+|------|--------------------------------------|
+| R2 | Regional Signalling System 2 |
+| SCTP | Stream Control Transmission Protocol |
+| SN | Serving Node |
+| TUP | Telephony User Part |
+
+# 4 Protocols
+
+Implementations providing any of the interfaces or protocols identified in the subclauses below shall implement the requirements of the specifications identified in those subclauses.
+
+## 4.1 Call control protocol (Nc interface)
+
+| | |
+|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Q.1902.1 | BICC PROTOCOL (CS2) FUNCTIONAL DESCRIPTION [6] |
+| Q.1902.2 | BICC PROTOCOL (CS2) AND SIGNALLING SYSTEM NO 7 ISUPGENERAL FUNCTIONS OF MESSAGES AND PARAMETERS [7] | +| Q.1902.3 | BICC PROTOCOL (CS2) AND SIGNALLING SYSTEM NO 7 ISUP
FORMATS AND CODES [8] (NOTE) | +| Q.1902.4 | BICC (CS2) BASIC CALL PROCEDURES [9] | +| Q.1902.5 | EXCEPTIONS TO THE APM IN THE CONTEXT OF BICC [10]
AMENDMENT TO ITU-T RECOMMENDATION Q.765.5 FOR BICC CS2 [5] | +| Q.1902.6 | GENERIC SIGNALLING PROCEDURES AND SUPPORT OF THE ISDN USER PART SUPPLEMENTARY
SERVICES WITH THE BEARER INDEPENDENT CALL CONTROL PROTOCOL [11] | +| NOTE: | The "Backward CAT indicators" parameter shall be encoded as an optional 3-octet parameter in the ACM, CPG and SEG messages rather than as a 1-octet parameter as incorrectly defined in Amendment 5 of ITU-T Recommendation Q.1902.3 [8]. | + +## 4.2 Interworking with other protocols + +| | | +|----------|-------------------------------------------------------------------------------------------------------------------------------------------| +| Q.1912.1 | ISUP-BICC INTERWORKING [16] | +| Q.1912.2 | INTERWORKING BETWEEN SELECTED SIGNALLING SYSTEMS (PSTN ACCESS DSS1 C5 R1 R2 TUP)
AND THE BEARER INDEPENDENT CALL CONTROL PROTOCOL [17] | + +## 4.3 Resource control protocol (G)MSC and MGW (Mc Interface) + +| | | +|----------------|------------------------------------------------------------------------------| +| 3GPP TS 29.232 | "Media Gateway Controller (MGC) – Media Gateway (MGW) Interface;Stage 3" [3] | +|----------------|------------------------------------------------------------------------------| + +## 4.4 Bearer control protocol between MGWs (Nb interface) + +| | | +|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3GPP TS 29.414 | "Core Network Nb Data Transport and Signalling Transport" [4]
including ITU-T Recommendation Q.1970 "IP bearer control protocol" [15] , ITU-T Recommendation Q.1990 "BICC tunneling control protocol" [14] , ITU-T Recommendation Q.2630.1-2 "AAL type 2 signalling protocol" [13]. | +|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## 4.5 Signalling Transport + +### 4.5.1 Call Control protocols + +| | | +|----------------|--------------------------------------------------------------------------------------------| +| Q.2150.0 | "Generic Signalling Transport Service" [18] | +| Q.2150.1 | "Signalling Transport Converter on MTP3 and MTP3b" [19] | +| Q.2150.3 | "Signalling Transport Converter on SCTP" [20] | +| 3GPP TS 29.202 | "SS7 signalling transport in core network" [22] Annex A: The use of M3UA in 3GPP networks. | + +### 4.5.2 Resource control protocol (G)MSC and MGW (Mc Interface) + +| | | +|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3GPP TS 29.232 | "Media Gateway Controller (MGC) – Media Gateway (MGW) Interface; Stage 3" [3] including ITU-T Recommendation H.248.4 "Transport over SCTP" [21], ITU-T Recommendation H.248.5 "Transport over ATM" [23], and 3GPP TS 29.202 "SS7 signalling transport in core network" [22] Annex A: The use of M3UA in 3GPP networks. | +|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### 4.5.3 Bearer control protocol between MGWs (Nb interface) + +| | | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3GPP TS 29.414 | "Core Network Nb Data Transport and signalling transport" [4] including ITU-T Recommendation Q.2630.1-2: "AAL type 2 signalling protocol" [13] and the tunnel-up and tunnel-down procedure in 3GPP TS 29.232 [31] | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +# --- Annex A: + +# Void + +# Annex B (normative): Transparent Support of Mobile Services + +## B.1 Introduction + +This Annex specifies a new mobile APM usage "Transparent support of mobile services". + +In ITU-T Recommendation Q.1902.3 [8], for the Application Transport Parameter (APP), the following codepoint is defined to refer to this application context identifier (ACI): + +0 0 0 0 1 1 1 MST
send notification indicator | | instruction indicator | reserved | general action
send notification indicator | | instruction indicator | 1 | + +The following codes are used in the subfields of the Compatibility information field. + +Bits 2 1 *Instruction indicator for general action* + +0 0 Pass on information element + +0 1 Discard information element + +1 0 Discard MST data + +1 1 Release call + +Bit 3 *Send notification indicator for general action* + +0 Do not send notification + +1 Send notification + +Bit 4 reserved + +Bits 6 5 *Instruction indicator for pass-on not possible* + +0 0 Release call + +0 1 Discard information element + +1 0 Discard MST data + +1 1 reserved (interpreted as 00) + +Bit 7 *Send notification indicator for pass-on not possible* + +0 Do not send notification + +1 Send notification + +Bit 8 *Extension indicator* + +0 Information continues through the next octet + +1 Last octet + +The Contents field is the substance of the element and contains the information the element is intended to convey. + +#### B.2.1.2 List of Identifiers + +Table B.2.1.2.1 contains the list of Identifiers. + +**Table B.2.1.2.1: List of identifiers** + +| Value | Information element name | Type | Reference | +|------------------------------|-----------------------------------|--------|-----------| +| 0000 0000 | spare | - | | +| 0000 0001 | Mobile Equipment Identifier | simple | B.2.1.3 | +| 0000 0010 | LCLS Negotiation Request | simple | B.2.1.4 | +| 0000 0011 | LCLS Negotiation Response | simple | B.2.1.5 | +| 0000 0100 | LCLS Status | simple | B.2.1.6 | +| 0000 0101 | LCLS Status Change | simple | B.2.1.7 | +| 0000 0110 | LCLS Status Result | simple | B.2.1.8 | +| 0000 0111 | LCLS Global Call Reference | simple | B.2.1.9 | +| 0000 1000 | LCLS Configuration Preference | simple | B.2.1.10 | +| 0000 1001 | LCLS Configuration Change Request | simple | B.2.1.11 | +| 0000 1010 | LCLS Configuration Change Result | simple | B.2.1.12 | +| 0000 1011
to
1101 1111 | reserved for 3GPP use | - | | +| 1110 0000
to
1111 1111 | reserved for national use | - | | + +#### B.2.1.3 Mobile Equipment Identifier + +The format of the Mobile Equipment Identifier is shown in Table B.2.1.3.1. + +**Table B.2.1.3.1: Mobile Equipment Identifier** + +| MSB | | | | | | | | LSB | | +|-----------------------------|---|---|---|---|---|---|---|-------|--| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | Octet | | +| Mobile Equipment Identifier | | | | | | | | 1 | | +| | | | | | | | | ... | | +| | | | | | | | | x | | + +The MEI contains either the International Mobile station Equipment Identity (IMEI) or the International Mobile station Equipment Identity and Software Version Number (IMEISV) as defined in subclause 6.2 of 3GPP TS 23.003 [25]. + +Both IMEI and IMEISV are TBCD encoded where IMEI is 15 digits and IMEISV is 16 digits. Bits 5 to 8 of octet n+1 (where n represents the octet of the IMEI(SV) being encoded) encodes digit 2n, bits 1 to 4 of octet n+1 encodes digit 2n-1 (i.e. the order of digits is swapped in each octet compared to the digit order defined in 3GPP TS 23.003 [25]). For IMEI, bits 5 to 8 of the last octet shall be filled with an end mark coded as '1111'. + +For the use of the Mobile Equipment Identifier (MEI) see 3GPP TS 23.216 [26] and 3GPP TS 23.237 [27]. + +#### B.2.1.4 LCLS Negotiation Request + +The format of the LCLS Negotiation Request is shown in Table B.2.1.4.1. + +**Table B.2.1.4.1: LCLS Negotiation Request** + +| MSB | | LSB | | | | | | Octet | +|---------------------|-------|-----|---|---|---|----------------------|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Extension Indicator | Spare | | | | | Permission Indicator | | 1 | + +The LCLS Negotiation Request is sent in the forward direction to indicate LCLS usage permission. + +##### **Bit 1 2 Permission Indicator** + +| | | +|---------|-------------------------| +| 00 | LCLS is allowed | +| 01 | LCLS is not allowed | +| 10 – 11 | Reserved for future use | + +Bit 3 - 7 Spare + +##### **Bit 8 Extension Indicator** + +| | | +|---|-------------------------------------| +| 0 | information continues in next octet | +| 1 | last octet | + +For the use of the LCLS Negotiation Request IE see Annex C.2.1 and 3GPP TS 23.284 [29]. + +#### B.2.1.5 LCLS Negotiation Response + +The format of the LCLS Negotiation Response is shown in Table B.2.1.5.1. + +**Table B.2.1.5.1: LCLS Negotiation Response** + +| MSB | | LSB | | | | | | Octet | +|-------|---|-----|---|---|----------------------|---|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Spare | | | | | Permission Indicator | | | 1 | + +The LCLS Negotiation Response contains information sent in the backwards direction to indicate result of the LCLS Negotiation Request. The LCLS Negotiation Response is coded as follows: + +##### **Bits 1 2 Permission Indicator** + +| | | +|----|--------------------------------------------| +| 00 | LCLS is allowed | +| 01 | LCLS is not allowed | +| 10 | LCLS is not supported by a subsequent node | +| 11 | spare | + +Bits 3 - 8 Spare + +For the use of the LCLS Negotiation Response IE see Annex C.2.2 and 3GPP TS 23.284 [29]. + +#### B.2.1.6 LCLS Status + +The format of the LCLS Status is shown in Table B.2.1.6.1. + +**Table B.2.1.6.1: LCLS Status** + +| • MSB | | | | | | | • LSB | Octet | +|-------------|---|---|---|---|---|---|-------|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| LCLS Status | | | | | | | | 1 | + +The LCLS Status contains information sent in forward and backward directions to indicate LCLS connection status. The LCLS Status is coded as follows: + +| Value | Meaning | +|-----------|----------------------------------------| +| 0000 0000 | no indication | +| 0000 0001 | LCLS is feasible but not yet connected | +| 0000 0010 | LCLS not connected | +| 0000 0011 | LCLS connected | + +All other values are reserved. + +For the use of the LCLS Status IE see Annex C.2.3, C.2.5 and 3GPP TS 23.284 [29]. + +#### B.2.1.7 LCLS Status Change + +The format of the LCLS Status Change is shown in Table B.2.1.7.1. + +**Table B.2.1.7.1: LCLS Status Change** + +| MSB | | | | | | | LSB | Octet | +|--------------------|---|---|---|---|---|---|-----|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| LCLS Status Change | | | | | | | | 1 | + +The LCLS Status Change Identifier contains information sent in forward and backward directions to indicate requested change of LCLS connection status. The LCLS Status Change Identifier is coded as follows: + +| Value | Meaning | +|-----------|---------------------------------------------| +| 0000 0000 | LCLS connection preparation | +| 0000 0001 | LCLS disconnection preparation | +| 0000 0010 | LCLS disconnection preparation for Handover | + +All other values are reserved. + +For the use of the LCLS Status Change IE see Annex C.2.6 and 3GPP TS 23.284 [29]. + +#### B.2.1.8 LCLS Status Result + +The format of the LCLS Status Result is shown in Table B.2.1.8.1. + +**Table B.2.1.8.1: LCLS Status Result** + +| MSB | | | | | | | LSB | Octet | +|-------|---|---|---------------------|---|---|----------------------|-----|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Spare | | | Rejection Indicator | | | Acceptance Indicator | | 1 | + +The LCLS Status Result contains information sent in forward and backward directions to indicate result of the LCLS Status Change Request. The LCLS Status Result is coded as follows: + +| Bit 1 | Acceptance Indicator | +|-------|-------------------------------------| +| 0 | LCLS Status Change request accepted | +| 1 | LCLS Status Change request rejected | + +| | | +|---------------------|-------------------------------| +| Bits 2 3 4 5 | Rejection Indicator | +| 0000 | No indication | +| 0001 | Ongoing supplementary service | +| 0010 – 1111 | Reserved for future use | +| Bits 6 - 8 | Spare | + +For the use of the LCLS Status Result IE see Annex C.2.6 and 3GPP TS 23.284 [29]. + +#### B.2.1.9 LCLS Global Call Reference + +The format of the LCLS Global Call Reference (GCR) is shown in Table B.2.1.9.1. + +**Table B.2.1.9.1: LCLS Global Call Reference** + +| MSB | | | | LSB | | | | Octet | +|---------------------------------------------------|---|---|---|-----|---|---|---|---------------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Network ID length indicator | | | | | | | | 1 | +| Network ID | | | | | | | | 2 | +| (variable length 3 – 5 octets) | | | | | | | | 4+m (m=0,1,2) | +| Node ID length indicator | | | | | | | | 5+m | +| Node ID | | | | | | | | 6+m | +| (fixed length: 2 octets) | | | | | | | | 7+m | +| Call Reference ID length indicator | | | | | | | | 8+m | +|
Call Reference ID
(fixed length: 5 octets) | | | | | | | | 9+m | +| | | | | | | | |
13+m | + +The LCLS GCR is information sent in forward direction to uniquely identify a call and correlate activities associated with that call. The LCLS GCR is coded as follows: + +- Network ID length indicator +Binary coded information indicating the number of octets in the Network ID field. +- Network ID +Information identifying a network. The Network ID field is specified in ITU-T Recommendation Q.1902.3 [8]. +- Node ID length Indicator +Binary coded information indicating the number of octets in the Node ID field. +- Node ID +A binary number that uniquely identifies within the network the node which generates the call reference. +- Call Reference ID length indicator +Binary coded information indicating the number of octets in the Call Reference ID field. +- Call Reference ID +A binary number used for the call reference of the call. It is generated by the originating serving node for each call. + +**NOTE:** If the originating serving radio access is GERAN the format of the Call Reference ID subfield is shown in Table B.2.1.9.2. The originating BSS ID is an integer that uniquely identifies the Base Station Subsystem (BSS) Node within an operator's network. + +**Table B.2.1.9.2: Call Reference ID** + +| MSB | | | | | | | | LSB | | | | | | | | +|------------------------------------------------|---|---|---|---|---|---|---|-----|--|--|--|--|--|--|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | Octet | +| Call Identifier
(fixed length: 3 octets) | | | | | | | | | | | | | | | 1 | +| Originating BSS ID
(fixed length: 2 octets) | | | | | | | | | | | | | | | 2 | + +For the use of the LCLS GCR IE see Annex C.2.1 and 3GPP TS 23.284 [29]. + +#### B.2.1.10 LCLS Configuration Preference + +The format of the LCLS Configuration Preference is shown in Table B.2.1.10.1. + +**Table B.2.1.10.1: LCLS Configuration Preference** + +| MSB | | | | | | | | LSB | | | | | | | | +|---------------------|-------|---|---|-----------------------------------|----------------------------------|---------------------------------|--------------------------------|-----|--|--|--|--|--|--|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | | | | | | | Octet | +| Extension Indicator | Spare | | | Backward Data Reception Indicator | Forward Data Reception Indicator | Backward Data Sending Indicator | Forward Data Sending Indicator | | | | | | | | 1 | + +The LCLS Configuration Preference contains information sent in forward and backward directions to indicate negotiated LCLS configuration preference. + +##### **Bit 1 Forward Data Sending Indicator** + +0 not required +1 required + +##### **Bit 2 Backward Data Sending Indicator** + +0 not required +1 required + +##### **Bit 3 Forward Data Reception Indicator** + +0 not required +1 required + +##### **Bit 4 Backward Data Reception Indicator** + +0 not required +1 required + +##### **Bits 5 - 7 Spare** + +##### **Bit 8 Extension Indicator** + +0 information continues in next octet +1 last octet + +For the use of the LCLS Configuration Preference IE see Annex C.2.1, C.2.2, C.2.4 and 3GPP TS 23.284 [29]. + +#### B.2.1.11 LCLS Configuration Change Request + +The format of the LCLS Configuration Change Request is shown in Table B.2.1.11.1. + +**Table B.2.1.11.1: LCLS Configuration Change Request** + +| MSB | | LSB | | | | | | Octet | +|---------------------|-------|-----|---|---|---|------|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Extension Indicator | Spare | | | | | Type | | | +| | | | | | | | | 1 | + +The LCLS Configuration Change Request contains information sent in the forward and backward directions to indicate type of LCLS Configuration Change Request. + +| | | +|----------------|----------------------------------------------------| +| Bit 1 2 | Type | +| 00 | LCLS Configuration Preference Modification Request | +| 01 - 11 | Spare | +|
| | +| Bit 3 - 7 | Spare | +|
| | +| Bit 8 | Extension Indicator | +| 0 | information continues in next octet | +| 1 | last octet | + +For the use of the LCLS Configuration Change Request IE see Annex C.2.4 and 3GPP TS 23.284 [29]. + +#### B.2.1.12 LCLS Configuration Change Result + +The format of the LCLS Configuration Change Result is shown in Table B.2.1.12.1. + +**Table B.2.1.12.1: LCLS Configuration Change Result** + +| MSB | | LSB | | | | | | Octet | +|-------|---|---------------------|---|---|---|----------------------|---|-------| +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +| Spare | | Rejection Indicator | | | | Acceptance Indicator | | | +| | | | | | | | | 1 | + +The LCLS Configuration Change Result contains information sent in the backward direction to indicate result of the LCLS Configuration Change Request. The LCLS Configuration Change Result is coded as follows: + +| | | +|---------------------|-------------------------------------------------------------------------------------------------------| +| Bit 1 | Acceptance Indicator | +| 0 | LCLS Configuration Change request accepted | +| 1 | LCLS Configuration Change request rejected (if set then Rejection Indicator provides further details) | +|
| | +| Bits 2 3 4 5 | Rejection Indicator | +| 0000 | No indication | +| 0001 | Requested LCLS configuration not supported | +| 0010 | Ongoing supplementary service | +| 0011 – 1111 | Reserved for future use | +|
| | +| Bits 6 - 8 | Spare | + +For the use of the LCLS Configuration Change Result IE see Annex C.2.4 and 3GPP TS 23.284 [29]. + +### B.2.2 Application Transport Instruction Indicators + +For the MST service the Application Transport Instruction Indicators (ATII) shall be set as follows: + +| | | | +|------|---|-------------------------------------| +| Bits | 1 | Release call indicator (RCI) | +| | 0 | do not release call | + +Bit 2 *Send notification indicator (SNI)* + +0 do not send notification + +# --- Annex C (normative): LCLS Service Application + +LCLS Service is defined in 3GPP TS 23.284 [29] and is dependent on the following identifiers being included in BICC/ISUP messaging. The following sections describe the detailed protocol behaviour when these identifiers are included. + +## --- C.1 Use of MST ASE + +LCLS service makes use of the services of the MST ASE described in Annex B. The services of the MST ASE are accessed by means of primitives (such as "MST\_data") which are the same as BAT ASE primitives defined in ITU-T Recommendation Q.765.5 [5]. + +## --- C.2 Procedures + +### C.2.1 Indication of LCLS Capability + +#### C.2.1.1 LCLS Service Capability Indication + +LCLS service shall be used for a call if MST\_data primitive associated with an IAM includes LCLS Information Elements: a LCLS GCR, a LCLS Negotiation Request and a LCLS Configuration Preference. The absence of the LCLS Negotiation, the LCLS Configuration Preference and the LCLS GCR Information Elements in the IAM specifies that the LCLS service shall not be used. + +The compatibility information of the LCLS Negotiation Request, the LCLS Configuration Preference and the LCLS GCR Information Elements shall be set so as to cause the Information Element to be discarded by nodes that do not support LCLS service. + +The procedures for call establishment using the LCLS service are described in 3GPP TS 23.284 [29]. + +#### C.2.1.2 Actions at Originating Serving Node + +An originating Serving Node (SN) that supports the LCLS service shall indicate this within the IAM message of the mobile originating call by including the LCLS Negotiation Request, the LCLS Configuration Preference and the LCLS GCR Information Elements within the MST Application Transport Parameter (APP) within the IAM. + +When the LCLS service is allowed to be used the IAM is sent to the succeeding node with the Permission Indicator of the LCLS Negotiation Request Information Element set to "LCLS is allowed". + +Depending on network requirements the originating SN may additionally indicate required configurations for user plane connectivity towards originating or terminating UE within the LCLS Configuration Preference Information Element. If the originating MSC server needs to: + +- send data towards the terminating UE it shall set Forward Data Sending Indicator to "required"; +- send data towards the originating UE it shall set Backward Data Sending Indicator to "required"; +- receive data from the originating UE it shall set Forward Data Reception Indicator to "required"; +- receive data from the terminating UE it shall set Backward Data Reception Indicator to "required". + +The originating SN shall perform the setting of LCLS Configuration Preference Information Element according to rules specified in sub-clause 4.2 of 3GPP TS 23.284 [29] or it may determine that LCLS is not allowed and indicate this by setting the value of Permission Indicator of the LCLS Negotiation Request Information Element to "LCLS is not allowed". + +#### C.2.1.3 Actions at Intermediate Serving Node + +For the intermediate Serving Node (SN), LCLS service indication (i.e. LCLS GCR, LCLS Negotiation Request and LCLS Configuration Preference Information Elements) shall be included only if received from the preceding node and if the node itself supports the LCLS service. + +The intermediate SN shall not change the LCLS GCR Information Element. If the intermediate SN receives Permission Indicator of the LCLS Negotiation Request Information Element set to "LCLS is not allowed" it shall not change it. + +Depending on network requirements the intermediate SN may additionally indicate required configurations for user plane connectivity towards originating or terminating UE by changing the received LCLS Configuration Preference Information Element. If the intermediate SN needs to: + +- send data towards the terminating UE it shall set Forward Data Sending Indicator to "required"; +- send data towards the originating UE it shall set Backward Data Sending Indicator to "required"; +- receive data from the originating UE it shall set Forward Data Reception Indicator to "required"; +- receive data from the terminating UE it shall set Backward Data Reception Indicator to "required". + +If the intermediate SN receives any of these indicators set to "required" it shall not change them. + +#### C.2.1.4 Actions at Destination Serving Node + +For the destination Serving Node (SN), LCLS service shall be supported only if the IAM with the LCLS Negotiation Request, LCLS Configuration Preference and LCLS GCR Information Elements within the MST Application Transport Parameter (APP) is received from the preceding node and if the node itself supports the LCLS service. + +Depending on network requirements the destination SN may additionally modify received configurations for user plane connectivity towards originating or terminating UE, by changing the settings of the LCLS Configuration Preference Information Element. If the destination SN needs to: + +- send data towards the terminating UE it shall set Forward Data Sending Indicator to "required"; +- send data towards the originating UE it shall set Backward Data Sending Indicator to "required"; +- receive data from the originating UE it shall set Forward Data Reception Indicator to "required"; +- receive data from the terminating UE it shall set Backward Data Reception Indicator to "required". + +If the destination SN receives any of these indicators set to "required" it shall not change them. + +The destination SN shall perform modification of LCLS Configuration Preference Information Element according to rules specified in sub-clause 4.2 of 3GPP TS 23.284 [29] or it may determine that LCLS is not allowed and shall indicate this by setting the value of Permission Indicator of the LCLS Negotiation Response Information Element to "LCLS is not allowed". + +### C.2.2 Backward LCLS Negotiation during Call Setup + +#### C.2.2.1 Introduction + +LCLS service shall be used for a call if MST\_data primitive associated with first backward (APM or ACM) message includes a LCLS Negotiation Response and a LCLS Configuration Preference Information Elements. The absence of the LCLS Negotiation Response and the LCLS Configuration Preference Information Elements in the first backward message specifies that the LCLS service shall not be used. + +The compatibility information of the LCLS Negotiation Response and the LCLS Configuration Preference Information Elements shall be set so as to cause the Information Element to be discarded by nodes that do not support LCLS service. + +#### C.2.2.2 Actions at Destination Serving Node + +If LCLS service is supported according to conditions specified in sub-clause C.2.1.4 a destination SN shall include in the first backward message (APM or ACM) the LCLS Negotiation Response and the LCLS Configuration Preference Information Elements in the MST\_Data request primitive. + +#### C.2.2.3 Actions at Intermediate Serving Node + +If LCLS service is supported according to conditions specified in sub-clause C.2.1.3 but a succeeding node does not return LCLS Negotiation Response Information Element in the first backward message, an Intermediate SN shall include the LCLS Negotiation Response Information Element. The Permission Indicator of the LCLS Negotiation Response Information Element shall be set to "LCLS is not supported by a subsequent node". + +On receipt of a backward message (APM, ACM or CPG) with the LCLS Negotiation Response and the LCLS Configuration Preference Information Elements the Intermediate SN shall store the LCLS configuration settings from the LCLS Configuration Preference Information Element and shall forward the LCLS Negotiation Response and the LCLS Configuration Preference Information Elements unchanged. + +#### C.2.2.4 Actions at Originating Serving Node + +If the first backward message does not contain the LCLS Negotiation Response and the LCLS Configuration Preference Information Elements the originating SN shall assume that LCLS is not supported by succeeding node and LCLS shall not be performed for that call; no further LCLS signalling shall take place for that call. + +If the first backward message contains the LCLS Negotiation Response Information Element but the Permission Indicator is set to "LCLS Not Allowed" or "LCLS is not supported by a subsequent node" then the originating SN shall not request establishment of the LCLS connection at this time. + +NOTE: A subsequent LCLS Negotiation Response Information Element can be received from succeeding nodes, e.g. in the event of a call forwarding on no reply. + +### C.2.3 Answer message + +#### C.2.3.1 Introduction + +LCLS connection may be established for a call if MST\_data primitive associated with an ANM includes a LCLS Status Identifier Information Element. The absence of the LCLS Status Identifier Information Element in the ANM specifies that the LCLS connection shall not be requested. + +The compatibility information of the LCLS Status Identifier shall be set so as to cause the Information Element to be discarded by nodes that do not support LCLS service. + +#### C.2.3.2 Actions at Destination Serving Node + +If a destination SN determines that LCLS service is feasible according to the conditions specified in sub-clause 6.2.1.3.4 of 3GPP TS 23.284 [29] it shall include the LCLS Status Identifier Information Element set to "LCLS feasible but not yet connected" within the MST Application Transport Parameter (APP) within the ANM. + +#### C.2.3.3 Actions at Intermediate Serving Node + +An Intermediate SN shall pass the LCLS Status Identifier within the ANM unchanged. + +#### C.2.3.4 Actions at Originating Serving Node + +When an originating SN receives an ANM with the LCLS Status Identifier indicating the LCLS service is feasible it shall request LCLS connection. + +### C.2.4 LCLS Configuration Change Request + +#### C.2.4.1 Introduction + +Modification of a LCLS configuration can only occur after the LCLS negotiation has been performed during the call set-up phase according to the procedures described in sub-clauses C.2.1 and C.2.2. A SN involved in a LCLS Configuration Change procedure must not initiate a new LCLS Configuration Change Request until the existing LCLS Configuration Change procedure has been completed. + +A LCLS Configuration Change Request message may be sent in either direction and at any time during the active phase of a call, after the LCLS negotiation has been performed during the call establishment. A LCLS Configuration Change Request and a LCLS Configuration Preference Information Elements indicating the requested change of the LCLS configuration shall be included in a MST\_data primitive, corresponding to an APM message. + +A MST\_Data primitive, corresponding to the APM message shall be issued in response, including the LCLS Configuration Preference and the LCLS Configuration Change Result Information Elements indicating if the requested change of LCLS configuration has been accepted and if it has not been accepted the reason for rejection. + +The compatibility information of the LCLS Configuration Preference, the LCLS Configuration Change Request and LCLS Configuration Change Result Information Elements shall be set so as to cause the Information Element to be discarded and send notification by nodes that do not support LCLS service. + +NOTE: The term "initiating" SN in the following clauses refers to a SN which initiates the LCLS Configuration Change Request. The term "terminating" SN in the following clauses refers to a SN which terminates the LCLS Configuration Change Request. + +#### C.2.4.2 Actions at Initiating Serving Node + +If a SN determines that LCLS configuration needs to be changed it may send an APM message which includes a LCLS Configuration Change Request and the LCLS Configuration Preference Information Elements to its succeeding and/or preceding node. The initiating SN shall set the desired configurations as described in sub-clause C.2.1.2. + +The LCLS Configuration Change Request may only be initiated if LCLS Negotiation was performed during call establishment. + +NOTE: this does not require that LCLS was permitted during the call establishment. + +On receipt of an APM message containing the LCLS Configuration Preference and the LCLS Configuration Change Result Information Elements, if the result indicates "accepted" the modification of the LCLS Configuration settings has been successful. If the LCLS Configuration Change Result Information Element indicates "rejected" the initiating SN shall resume the LCLS connection with the LCLS configuration unchanged. + +#### C.2.4.3 Actions at Intermediate Serving Node + +When an intermediate SN receives an APM message with the LCLS Configuration Change Request and the LCLS Configuration Preference Information Elements requesting a certain LCLS Configuration Change the intermediate SN shall check if it can support the requested LCLS configuration. If the intermediate SN can support the proposed LCLS configuration it shall forward the LCLS Configuration Preference and the LCLS Configuration Change Request Information Elements to its succeeding or preceding node. If the intermediate SN cannot support/permit the proposed LCLS configuration it shall respond with a LCLS Configuration Change Result Information Element set to "LCLS Configuration Change request rejected" along with the Rejection Indicator detailing the reason for rejection. + +On receipt of an APM message with the LCLS Configuration Change Result and LCLS Configuration Preference Information Elements from its succeeding/preceding node if the LCLS Configuration Change Result Information Elements indicates "accepted" the intermediate SN shall store the LCLS configuration settings from the LCLS Configuration Preference Information Element and shall forward the APM message to its preceding/succeeding node. + +If the LCLS Configuration Change Result Information Element indicates "rejected" the intermediate SN shall resume the LCLS connection with the LCLS configuration unchanged and the intermediate SN shall forward the APM message to its preceding/succeeding node. + +#### C.2.4.4 Actions at Terminating Serving Node + +When an SN which is a terminating SN with respect to a LCLS Configuration Change Request receives an APM message with the LCLS Configuration Change Request and LCLS Configuration Preference Information Elements requesting a certain LCLS Configuration Change the terminating SN shall check if it can support the requested LCLS configuration. + +If the terminating SN can support the proposed LCLS configuration change it shall return the LCLS Configuration Preference Information Element and the LCLS Configuration Change Result Information Element indicating acceptance of the LCLS Configuration Change to its succeeding or preceding node. If the terminating SN cannot support/permit the proposed LCLS configuration it shall respond with a LCLS Configuration Change Result Information Element set to "LCLS Configuration Change request rejected" along with the Rejection Indicator detailing the reason for rejection. + +### C.2.5 LCLS Status Update + +#### C.2.5.1 Introduction + +A LCLS Status Update message may be sent in either direction to indicate that a LCLS connection status has been changed. A LCLS Status Identifier Information Element indicating the new LCLS connection status value shall be included in a MST\_data primitive, corresponding to an APM message. + +The compatibility information of the LCLS Status Identifier shall be set so as to cause the Information Element to be discarded and send notification by nodes that do not support LCLS service. + +NOTE: The term "initiating" SN in the following clauses refers to an originating SN or a destination SN that may initiate the LCLS Status Update message. The term "terminating" SN in the following clauses refers to an originating SN or a destination SN that may receive the LCLS Status Update message. + +#### C.2.5.2 Actions at Initiating Serving Node + +If a SN determines that the LCLS connection status has been changed it shall send the new LCLS connection status value to an adjacent SN. An initiating SN shall send the LCLS Status Identifier Information Element within the MST Application Transport Parameter (APP) within the APM message. + +#### C.2.5.3 Actions at Intermediate Serving Node + +When an intermediate SN receives the APM message with the LCLS Status Identifier Information Element from the preceding/succeeding SN and if the same LCLS connection status value has not been already received from the succeeding/preceding SN, the intermediate SN shall store the new LCLS Connection status value and shall pass the LCLS Status Identifier Information Element within the APM message unchanged to its succeeding/preceding SN. + +#### C.2.5.4 Actions at Terminating Serving Node + +When a terminating SN receives the APM message with the LCLS Status Identifier Information Element from the adjacent SN, it shall update its LCLS connection status value. + +### C.2.6 LCLS Status Change Request + +#### C.2.6.1 Introduction + +A LCLS Status Change Request message may be sent in either direction and at any time during the active phase of a call, after the LCLS has been initially established. A LCLS Status Change Identifier Information Element indicating the requested change of the LCLS connection status shall be included in a MST\_data primitive, corresponding to an APM message. + +An MST\_Data primitive, corresponding to the APM message shall be issued in response, including the LCLS Status Change Identifier Information Element and a LCLS Status Result Identifier Information Element indicating if the requested change of LCLS connection status has been accepted and if it has not been accepted the reason for rejection. + +The compatibility information of the LCLS Status Change Identifier and the LCLS Status Result Identifier shall be set so as to cause the Information Element to be discarded and send notification by nodes that do not support LCLS service. + +NOTE: The term "initiating" SN in the following clauses refers to a SN which initiates the LCLS Status Change. The term "terminating" SN in the following clauses refers to a SN which terminates the LCLS Status Change. + +#### C.2.6.2 Actions at Initiating Serving Node + +When a SN determines that the LCLS connection status needs to be changed, it shall request the change of the LCLS connection status from its preceding and/or succeeding SN. An initiating SN shall send the LCLS Status Change Identifier Information Element within the MST Application Transport Parameter (APP) within an APM message. + +An APM message containing the LCLS Status Change Identifier Information Element and a LCLS Status Result Identifier Information Element will be received in response from the succeeding and/or preceding SN. + +If initiating SN is an SN serving a Radio Network (originating SN or destination SN), upon reception of the LCLS Status Result Identifier Information Element indicating the acceptance of the requested LCLS connection status change, the initiating SN shall change the LCLS connection status. + +NOTE: This change of LCLS connection status can be deferred until signalling interaction with the served Radio Network Controller, which is outside of the scope of this specification. + +#### C.2.6.3 Actions at Intermediate Serving Node + +When an intermediate SN receives from a preceding/succeeding SN an APM message that includes a LCLS Status Change Identifier Information Element within the MST Application Transport Parameter (APP) it shall check if it can support the required change of the LCLS connection status. + +If the intermediate SN cannot support the requested change of the LCLS connection status it shall respond to the preceding/succeeding SN with the APM message containing the LCLS Status Change Identifier Information Element and a LCLS Status Result Identifier Information Element with an Acceptance indicator set to "LCLS Status Change request rejected" along with a Rejection Indicator detailing the reason for rejection. + +If the intermediate SN can support the required change of the LCLS connection status it shall pass the LCLS Status Change Identifier Information Element within the APM message unchanged to its succeeding/preceding SN. An APM message will be received in response, including the LCLS Status Change Identifier Information Element and a LCLS Status Result Identifier Information Element from its succeeding/preceding SN. The intermediate SN shall pass the LCLS Status Change Identifier Information Element and the LCLS Status Result Identifier Information Element within the APM message unchanged to its succeeding/preceding SN. + +#### C.2.6.4 Actions at Terminating Serving Node + +Upon reception of an APM message that includes a LCLS Status Change Identifier Information Element, from the adjacent SN, a terminating SN shall check if it can support the required change of the LCLS connection status. + +If the terminating SN can support the required change, it shall change the LCLS connection status. If the result of the LCLS connection status change is successful the terminating SN shall send to the adjacent SN the APM message with the LCLS Status Change Identifier Information Element and a LCLS Status Result Identifier Information Element indicating the acceptance of the requested LCLS connection status change. + +NOTE: If the terminating SN is an SN serving a Radio Network (originating SN or destination SN), there can be additional signalling with the served Radio Network Controller, prior to responding to the LCLS Status Change Request; this is, however, outside of the scope of this specification. + +If the result of the LCLS connection status change is unsuccessful or if the terminating SN cannot support the required change it shall respond to the adjacent SN with the APM message containing the LCLS Status Change Identifier Information Element and a LCLS Status Result Identifier Information Element with an Acceptance indicator set to "LCLS Status Change request rejected" along with a Rejection Indicator detailing the reason for rejection. + +# Annex D (informative): Change history + +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|---------------------------------|-----------|------|------|-----------------------------------------------------------------------------------|--------| +| 17/1/01 | CN3/CN4
#66
Beijing | | | 0.1. | New Document approved | 0.1.0 | +| 15/2/01 | Ad hoc
CN 4#6 in
Madrid | | | 0.2 | Revised Document approved | 0.2.0 | +| 01/3/01 | CN 4 #7
Sophia—
Antopolis | | | 0.3 | Forwarded to TSG CN Plenary meeting #11 for approval | 2.0.0 | +| 03/2001 | CN#11 | NP-010083 | | | Modifications made during CN#11 | 2.1.0 | +| 03/2001 | CN#11 | NP-010214 | | | Approved in CN#11 | 4.0.0 | +| 06/2001 | CN#12 | NP-010285 | 0001 | 1 | Changes to provide interworking between signalling transport | 4.1.0 | +| 09/2001 | CN#13 | | | | Editorial clean up | 4.2.0 | +| 09/2001 | CN#13 | NP-010452 | 0002 | | Mc signalling transport in IP environment | 4.2.0 | +| 09/2001 | CN#13 | NP-010452 | 0003 | 1 | BICC signalling transport in IP environment | 4.2.0 | +| 09/2001 | CN#13 | NP-010452 | 0004 | | Status of ITU recommendation Q.2150.3 | 4.2.0 | +| 06/2002 | CN#16 | | | | Rel-5 created after CN#16 | 5.0.0 | +| 06/2003 | CN#20 | NP-030220 | 0006 | 2 | Alignment of references after renumbering of H248 by ITU-T | 5.1.0 | +| 12/2004 | CN#26 | | | | Rel-6 created after CN#26 | 6.0.0 | +| 06/2006 | CT#32 | CP-060298 | 0009 | 1 | | 6.1.0 | +| 06/2007 | CT#36 | | | | Upgraded unchanged from Rel-6 | 7.0.0 | +| 12/2008 | CT#42 | | | | Upgraded unchanged from Rel-7 | 8.0.0 | +| 06/2009 | CT#44 | CP-090312 | 0011 | 2 | Amendment for "multimedia Customized Alerting Tone (CAT) service in ITU ISUP/BICC | 8.1.0 | +| 06/2009 | CT#44 | CP-090499 | 0013 | 1 | Mobile Service Application Transport | 9.0.0 | +| 12/2009 | CT#46 | CP-090801 | 0017 | 2 | Introduction of IMEI IE to Mobile APM for SRVCC Emergency Call | 9.1.0 | +| 06/2010 | CT#48 | CP-100267 | 0020 | 1 | ITU amendments for Customized Alerting Tone (CAT) | 9.2.0 | +| 06/2010 | CT#48 | CP-100278 | 0018 | | IPBCP version | 9.2.0 | +| 03/2011 | CT#51 | CP-110041 | 0027 | 1 | Correcting non-specific external references | 9.3.0 | +| 03/2011 | CT#51 | CP-110081 | 0021 | 1 | Introduction of LCLS Application to Mobile Service Application Transport | 10.0.0 | +| 06/2011 | CT#52 | CP-110376 | 0028 | | Miscellaneous corrections | 10.1.0 | +| 09/2011 | CT#53 | CP-110571 | 0034 | | Indication of LCLS Negotiation type | 10.2.0 | +| 12/2011 | CT#54 | CP-110799 | 0036 | 1 | Correction to Procedures for Indication of LCLS Capability | 10.3.0 | +| 12/2011 | CT#54 | CP-110799 | 0037 | 2 | Correction to Procedures for Backward LCLS Negotiation | 10.3.0 | +| 12/2011 | CT#54 | CP-110799 | 0038 | 1 | Correction to Procedures for LCLS in Answer message | 10.3.0 | +| 12/2011 | CT#54 | CP-110799 | 0039 | 2 | Correction to Procedures for LCLS Negotiation Change | 10.3.0 | +| 12/2011 | CT#54 | CP-110799 | 0040 | 1 | Correction to Procedures for LCLS Status Update | 10.3.0 | +| 12/2011 | CT#54 | CP-110799 | 0041 | 1 | Correction to Procedures for LCLS Status Change | 10.3.0 | +| 12/2011 | CT#54 | CP-110799 | 0043 | 1 | Re-specify Information Elements for LCLS Negotiation and LCLS Negotiation Change | 10.3.0 | +| 12/2012 | CT#57 | | | | Upgraded unchanged from Rel-7 | 11.0.0 | +| 2014-09 | - | - | - | - | Update to Rel-12 version (MCC) | 12.0.0 | +| 2015-12 | CT#70 | - | - | - | Update to Rel-13 version (MCC) | 13.0.0 | +| 2017-03 | CT#75 | - | - | - | Update to Rel-14 version (MCC) | 14.0.0 | +| 2018-06 | CT#80 | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-07 | CT#88e | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/29_series/29217/731f533b0599c8e42a063f06e4332045_img.jpg b/marked/Rel-16/29_series/29217/731f533b0599c8e42a063f06e4332045_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4feca453bb209dfb2f1d789eb3c98837df1cb20c --- /dev/null +++ b/marked/Rel-16/29_series/29217/731f533b0599c8e42a063f06e4332045_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81728a1632efb214a3707a2351f3a87c356ff49874d3b9026a1c8d0483101bf6 +size 6527 diff --git a/marked/Rel-16/29_series/29217/raw.md b/marked/Rel-16/29_series/29217/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..542ad8a1a1fc9f0c604807136fe2d890885aa9ad --- /dev/null +++ b/marked/Rel-16/29_series/29217/raw.md @@ -0,0 +1,879 @@ + + + + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +| | | +|--------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 Np reference point..... | 7 | +| 4.1 Overview ..... | 7 | +| 4.2 Np reference model ..... | 8 | +| 4.3 Functional elements..... | 8 | +| 4.3.1 RCAF..... | 8 | +| 4.3.2 PCRF ..... | 9 | +| 4.3.3 H-PCRF ..... | 9 | +| 4.3.4 V-PCRF ..... | 9 | +| 4.4 Procedures over Np reference point..... | 9 | +| 4.4.1 RUCI Report..... | 9 | +| 4.4.1.1 General..... | 9 | +| 4.4.1.2 Non-aggregated RUCI report..... | 10 | +| 4.4.1.3 Aggregated RUCI report..... | 10 | +| 4.4.2 Reporting Restriction Provisioning ..... | 10 | +| 4.4.3 UE mobility between RCAFs..... | 11 | +| 4.4.4 Removal of UE context ..... | 11 | +| 4.4.5 Race condition handling ..... | 12 | +| 5 Np protocol ..... | 12 | +| 5.1 Protocol support ..... | 12 | +| 5.2 Initialization, maintenance and termination of connection and session..... | 12 | +| 5.3 Np specific AVPs..... | 13 | +| 5.3.1 General ..... | 13 | +| 5.3.2 Aggregated-Congestion-Info AVP..... | 13 | +| 5.3.3 Aggregated-RUCI-Report AVP ..... | 13 | +| 5.3.4 Congestion-Level-Definition AVP..... | 14 | +| 5.3.5 Congestion-Level-Range AVP..... | 14 | +| 5.3.6 Congestion-Level-Set-Id AVP ..... | 14 | +| 5.3.7 Congestion-Level-Value AVP..... | 14 | +| 5.3.8 Congestion-Location-Id AVP..... | 15 | +| 5.3.9 Conditional-Restriction AVP ..... | 15 | +| 5.3.10 eNodeB-Id AVP ..... | 15 | +| 5.3.11 IMSI-List AVP ..... | 15 | +| 5.3.12 RCAF-Id AVP ..... | 16 | +| 5.3.13 Reporting-Restriction AVP ..... | 16 | +| 5.3.14 RUCI-Action AVP ..... | 16 | +| 5.3.15 Extended-eNodeB-Id AVP ..... | 17 | +| 5.4 Np re-used AVPs..... | 17 | +| 5.4.1 General ..... | 17 | +| 5.4.2 Use of the Supported-Features AVP on the Np reference point..... | 18 | +| 5.5 Np specific Experimental-Result-Code AVP values ..... | 19 | +| 5.5.1 General ..... | 19 | +| 5.5.2 Success ..... | 19 | +| 5.5.3 Permanent Failures ..... | 19 | +| 5.5.4 Transient Failures ..... | 19 | +| 5.6 Np messages..... | 19 | +| 5.6.0 Command-Code Values..... | 19 | +| 5.6.1 Non-Aggregated-RUCI-Report-Request (NRR) command ..... | 20 | +| 5.6.2 Non-Aggregated-RUCI-Report-Answer (NRA) command..... | 20 | +| 5.6.3 Aggregated-RUCI-Report-Request (ARR) command..... | 21 | +| 5.6.4 Aggregated-RUCI-Report-Answer (ARA) command..... | 21 | + +5.6.5 Modify-Uecontext-Request (MUR) command..... 21 +5.6.6 Modify-Uecontext-Answer (MUA) command..... 22 +Annex A (informative): Change history..... 23 + +# --- 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 provides the stage 3 specification of the Np reference point. The functional requirements and the stage 2 specifications of the Np reference point are contained in 3GPP TS 23.203 [2]. The Np reference point lies between the RAN Congestion Awareness Function (RCAF) and the Policy and Charging Rules Function (PCRF) for the non-roaming case, between the RCAF and the H-PCRF for the home-routed scenario and between the RCAF and the V-PCRF for the visited access scenario. + +NOTE: If not specified explicitly, the PCRF also means H-PCRF for the home-routed scenario or V-PCRF in the visited access scenario in the specification. + +# 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.203: "Policy and charging control architecture". +- [3] 3GPP TS 29.213: "Policy and Charging Control signalling flows and QoS parameter mapping". +- [4] IETF RFC 4005: "Diameter Network Access Server Application". +- [5] IETF RFC 4006: "Diameter Credit Control Application". +- [6] 3GPP TS 29.229: "Cx and Dx interfaces based on Diameter protocol; Protocol details". +- [7] IETF RFC 3588: "Diameter Base Protocol". +- [8] 3GPP TS 23.401: "GPRS enhancements for E-UTRAN access". +- [9] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [10] 3GPP TS 29.215: "Policy and Charging Control (PCC) over S9 reference point; Stage 3". +- [11] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)". +- [12] 3GPP TS 29.274: "3GPP Evolved Packet System. Evolved GPRS Tunnelling Protocol for EPS (GTPv2)". +- [13] ITU-T Recommendation E.212: "The international identification plan for mobile terminals and mobile users". +- [14] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points". +- [15] IETF RFC 7683: "Diameter Overload Indication Conveyance". +- [16] IETF RFC 7944: "Diameter Routing Message Priority". +- [17] IETF RFC 8583: "Diameter Load Information Conveyance". +- [18] IETF RFC 6733: "Diameter Base Protocol". +- [19] IETF RFC 5719: "Updated IANA Considerations for Diameter Command Code Allocations". + +# 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**Home Routed Access:** Roaming scenario where the PCEF is located in the HPLMN. In a Home Routed roaming scenario, the UE obtains access to the packet data network from the HPLMN. + +**RAN user plane congestion:** RAN user plane congestion occurs when the demand for RAN resources exceeds the available RAN capacity to deliver the user data for a prolonged period of time. + +NOTE: Short-duration traffic bursts is a normal condition at any traffic load level, and is not considered to be RAN user plane congestion. Likewise, a high-level of utilization of RAN resources (based on operator configuration) is considered a normal mode of operation and might not be RAN user plane congestion. + +**Visited Access (also known as local breakout):** Roaming scenario where the PCEF is located in the VPLMN. In a Visited Access Roaming scenario, the UE obtains access to the packet data network from the VPLMN. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|--------|---------------------------------------| +| AF | Application Function | +| ARR | Aggregated RUCI Report Request | +| ARA | Aggregated RUCI Report Answer | +| DRMP | Diameter Routing Message Priority | +| H-PCRF | Home PCRF | +| MUR | Modify Uecontext Request | +| MUA | Modify Uecontext Answer | +| NRR | Non-Aggregated RUCI Report Request | +| NRA | Non-Aggregated RUCI Report Answer | +| PCC | Policy and Charging Control | +| PCRF | Policy and Charging Rule Function | +| RCAF | RAN Congestion Awareness Function | +| RUCI | RAN User Plane Congestion Information | +| V-PCRF | Visited PCRF | + +# 4 Np reference point + +## 4.1 Overview + +The Np reference point is located between the RCAF and the PCRF for the non-roaming scenario, between the RCAF and the H-PCRF for the home-routed scenario and between the RCAF and the V-PCRF for the visited access scenario. The Np reference point is used for: + +- Reporting the RUCI from the RCAF to the PCRF; +- Provisioning the Reporting Restriction from the PCRF to the RCAF; +- The User Equipment (UE) mobility between RCAF; +- The removal of the UE context in the RCAF. + +The stage 2 level requirements for the Np reference point are defined in 3GPP TS 23.203 [2]. + +Signalling flows related to Np interface are specified in 3GPP TS 29.213 [3]. + +Refer to Annex G of 3GPP TS 29.213 [3] for Diameter overload control procedures over the Np interface. + +Refer to Annex J of 3GPP TS 29.213 [3] for Diameter message priority mechanism procedures over the Np interface. + +Refer to Annex K of 3GPP TS 29.213 [3] for Diameter load control procedures over the Np interface. + +## 4.2 Np reference model + +The relationships between the involved functional entities are depicted in figure 4.2.1. The overall PCC architecture is depicted in clause 3a of 3GPP TS 29.213 [3] . + + + +The diagram shows two rectangular boxes, one on the left labeled 'RCAF' and one on the right labeled 'PCRF'. A horizontal line connects the two boxes. Above the line, centered between the boxes, is the label 'Np'. There is a small vertical tick mark on the line between the two boxes. + +Diagram of the Np reference model showing RCAF and PCRF connected via the Np interface. + +**Figure 4.2.1: Np reference model** + +NOTE: For the home-routed access scenario, the RCAF interacts with the H-PCRF. For the visited access scenario, the RCAF interacts with the V-PCRF. + +**Figure 4.2.2: Void** + +**Figure 4.2.3: Void** + +## 4.3 Functional elements + +### 4.3.1 RCAF + +The RCAF is a functional element which reports RAN User Plane Congestion Information (RUCI) via the Np interface to the PCRF to enable the PCRF to take the RAN user plane congestion status into account for policy decisions. RUCI includes the following information: + +- The user id (e.g. IMSI) identifying the UE impacted by congestion; +- PDN ID for which congestion information is reported; +- Congestion level information (either congestion level value or congestion level set id) of the UE impacted by congestion; +- eNodeB identifier, ECGI or SAI identifying the eNodeB, E-UTRAN cell or Service Area respectively, serving the UE if a conditional restriction to restrict location reporting is not enabled. + +NOTE 1: In case of E-UTRAN, whether the eNodeB identifier or the ECGI are included in the RUCI is up to operator configuration in the RCAF. + +The RCAF sends the RUCI to the PCRFs serving the UEs' PDN connections as follows: + +- For a PDN connection in a non-roaming scenario the RCAF reports the RUCI to the PCRF; +- For a PDN connection in a local breakout scenario, based on operator configuration, the RCAF reports the RUCI to the V-PCRF; +- For a PDN connection in a home routed scenario, based on the roaming agreement with the HPLMN and operator configuration, the RCAF reports the RUCI to the H-PCRF + +NOTE 2: Reporting of congestion information to the HPLMN may be used e.g. in case of a group of PLMNs which belong to a single business entity. + +The RCAF determines whether a given PDN connection is served in a local breakout or a home routed roaming scenario based on the APN operator identifier received as part of the APN information from the MME or the SGSN as documented in 3GPP TS 23.401 [8] and 3GPP TS 23.060 [9], respectively. + +NOTE 3: Operator configuration can be used to limit RUCI reporting on the Np interface to certain APNs only. + +The RCAF maintains a context per user id and APN. The context is identified by the IMSI and the APN. It contains the following information: + +- The previously reported congestion level over the Np reference point; +- The reporting restrictions received from the PCRF. The reporting restrictions are stored by the RCAF until the PCRF explicitly signals to remove the reporting restrictions. +- The logical PCRF id received from the PCRF to identify the PCRF that is the Np destination for the RCAF when sending aggregate messages. + +### 4.3.2 PCRF + +The PCRF is a functional element that encompasses policy control decision and flow based charging control functionalities. + +The PCRF may receive RUCI from the RCAF as input for policy decisions of congestion mitigation. The PCRF may provide, update or remove the reporting restrictions of RUCI, or stop or enable RUCI reporting for a given user id and PDN ID. The PCRF may enable or disable the reporting of congestion location identifier as part of RUCI. The PCRF may also remove the context at the RCAF for a given user id and PDN ID. + +NOTE: Depending on the RUCI reporting interval configured in the RCAF, a UE can move outside the area indicated without the RCAF immediately notifying the PCRF. In case the PCRF receives information about the cell currently serving a UE via Np and Gx when the location change reporting is enabled, then the information received via Gx is expected to take precedence. + +### 4.3.3 H-PCRF + +Functionality defined in clause 4.3.2 shall apply if UE is roaming with home-routed access scenario. + +NOTE: Reporting of congestion information to the HPLMN can be used e.g. in case of a group of PLMNs which belong to a single business entity. + +### 4.3.4 V-PCRF + +Functionality defined in clause 4.3.2 shall apply if UE is roaming with visited access scenario. + +## 4.4 Procedures over Np reference point + +### 4.4.1 RUCI Report + +#### 4.4.1.1 General + +The RCAF shall perform the RUCI reporting to the PCRF when at least one of the following conditions applies: + +- the RCAF detects a UE in the congestion area for the first time; +- a reporting restriction is enabled and the congestion level set id is changed; +- a reporting restriction is not enabled and the congestion level value is changed; +- a conditional restriction to restrict location reporting is not enabled and the UE is in a congested area and the location is changed; or +- the RCAF detects that the UE is no longer experiencing congestion (i.e. the UE is no longer detected in any of the congested cells that the RCAF is monitoring). + +The RCAF shall report the RUCI to the PCRF unless the RUCI reporting is disabled for the PDN ID or for the user id and the PDN ID. + +Two types of RUCI reports may be used on Np for transfer of congestion information from RCAF to PCRF: Non-aggregated RUCI report and Aggregated RUCI report. If the RCAF does not know the destination PCRF for the user id and PDN ID, the Non-aggregated RUCI report shall be used; otherwise the RCAF may use either the Non-aggregate RUCI report or Aggregated RUCI report for the user id and PDN ID. + +#### 4.4.1.2 Non-aggregated RUCI report + +For a Non-aggregated RUCI report, the RCAF shall send an NRR command to the PCRF by including the user id within the Subscription-Id AVP, PDN ID within the Called-Station-Id AVP and a congestion level set id within the Congestion-Level-Set-Id AVP if the reporting restriction was provided earlier or a congestion level value within the Congestion-Level-Value AVP if the reporting restriction was not provided earlier at the command level. The RCAF may also provide congestion location identifier of the UE within the Congestion-Location-Id AVP in the NRR command. The RCAF shall also include the RCAF Identity within the RCAF-Id AVP in every NRR command for a specific user id and PDN ID. + +Once the PCRF receives the NRR command, the PCRF shall store the related info and respond with an NRA command including the PCRF id within the PCRF-Address AVP. The PCRF may use the RUCI received from the RCAF as input for policy decisions. When the RCAF receives the NRA command, the RCAF may store the PCRF id in the UE context for this specific user id together with PDN ID for further aggregated RUCI report. + +If the ReportRestriction feature is supported by both the RCAF and the PCRF, the PCRF may provide reporting restrictions in the NRA command according to clause 4.4.2. + +#### 4.4.1.3 Aggregated RUCI report + +For an Aggregated RUCI report, the RCAF shall aggregate the RUCIs of different user ids and PDN IDs that have the same destination PCRF. The RCAF shall send an ARR command to the destination PCRF by including the PCRF id within the Destination-Host AVP, one or more Aggregated-RUCI-Report AVP with a congestion level set id within the Congestion-Level-Set-Id AVP if the reporting restriction was provided earlier or a congestion level value within the Congestion-Level-Value AVP if the reporting restriction was not provided earlier, the PDN ID within the Called-Station-ID AVP and a list of aggregated congestion information within the Aggregated-Congestion-Info AVP. + +NOTE 1: Each instance of Aggregated-RUCI-Report AVP aggregates the user id list of the subscribers that share the same level of congestion or share the same congestion level set id. + +NOTE 2: When the RCAF assembles a Diameter ARR command, if the message length of ARR command has exceeded the maximum length of Diameter message which can be configurable, the RCAF can divide the original ARR command into multiple aggregated RUCI messages for the delivery over Np reference point. + +Once the PCRF receives the ARR command, the PCRF shall store the related info and respond with an ARA command. The PCRF may use the RUCI received from the RCAF as input for policy decisions. + +### 4.4.2 Reporting Restriction Provisioning + +If the ReportRestriction feature is supported by both the RCAF and the PCRF, the PCRF may provide the reporting restrictions for a specific user id and PDN ID in the initial NRA command. The PCRF may also provide, modify or disable restrictions for RUCI reporting or stop or enable RUCI reporting for the specific user id and PDN ID at any later time. The PCRF may also use this procedure to enable or disable the reporting of congestion location identifier as part of RUCI. + +In order to initially provide the reporting restrictions, the PCRF shall send a Modify-Uecontext-Request (MUR) command including the targeted Subscription-Id AVP indicating the user id, the Called-Station-Id AVP indicating the targeted PDN ID and one or more Congestion-Level-Definition AVP(s) including the defined congestion level set within the Congestion-Level-Set-Id AVP and corresponding congestion level(s) within the Congestion-Level-Range AVP or reply with an NRA command including one or more Congestion-Level-Definition AVP(s) including the defined congestion level set within the Congestion-Level-Set-Id AVP and corresponding congestion level(s) within the Congestion-Level-Range AVP. The PCRF may also include the Reporting-Restriction AVP and Conditional-Restriction AVP to indicate when conditional reporting restrictions apply. + +The PCRF may modify already provided reporting restrictions. To do so the PCRF shall provide the complete list of congestion level sets and corresponding congestion levels to be used in the same manner as when initially providing reporting restrictions. This complete list shall replace any previously provided list. The absence of Reporting-Restriction AVP and Conditional-Restriction AVP indicates that previous state of reporting restrictions remains valid. + +If reporting restrictions has been provided for a specific user id and PDN ID, the PCRF may remove the reporting restrictions by, in the MUR command, including the Reporting-Restriction AVP set to 0 (No reporting restriction), together with Subscription-Id AVP indicating the user id and the Called-Station-Id AVP indicating the targeted PDN ID or reply with an NRA command including the Reporting-Restriction AVP set to 0 (No reporting restriction). + +The PCRF may disable RUCI reporting by, in the MUR command, including the RUCI-Action AVP set to 0 (Disable RUCI Reporting), together with Subscription-Id AVP indicating the user id and the Called-Station-Id AVP indicating the targeted PDN ID or reply with an NRA command including the RUCI-Action AVP set to 0 (Disable RUCI Reporting). + +To enable RUCI Reporting if previously disabled, the PCRF in the MUR command shall include the RUCI-Action AVP set to 1 (Enable RUCI Reporting), together with Subscription-Id AVP indicating the user id and the Called-Station-Id AVP indicating the targeted PDN ID or reply with an NRA command including the RUCI-Action AVP set to 1 (Enable RUCI Reporting). + +If reporting restrictions also applies, the PCRF shall include one or more Congestion-Level-Definition AVP(s) including the defined congestion level set with the Congestion-Level-Set-Id AVP and corresponding congestion level(s) within the Congestion-Level-Range AVP, within the same command. + +To provision the reporting restriction which disables the reporting of congestion location identifier of the UE as part of RUCI, the PCRF shall include Reporting-Restriction AVP set to 1 (Conditional reporting restriction) and Conditional-Restriction AVP with the bit 0 be set. To enable a previously disabled reporting of the congestion location identifier of the UE as part of RUCI, the PCRF shall include Reporting-Restriction AVP set to 2 (Unconditional reporting restriction). + +The PCRF shall include the value of the RCAF-Id AVP received in the NRR command for the specific user id and PDN ID in the Destination-Host AVP of the MUR command. + +The RCAF acknowledges the received MUR command by sending a Modify-Uecontext-Answer (MUA) command in all cases above. + +### 4.4.3 UE mobility between RCAFs + +If RUCI reporting is used for a specific user id and PDN ID and the PCRF receives a new non-aggregated RUCI report for the same user id and PDN ID but with a different RCAF id included in the RCAF-Id AVP, the PCRF shall update the related information and respond with an NRA command according to clause 4.4.1.1. + +The PCRF shall also initiate a removal of the UE context to the old RCAF according to clause 4.4.4. + +### 4.4.4 Removal of UE context + +This procedure is initiated when the PCRF needs to remove a UE context from the RCAF, e.g. at UE mobility between RCAFs. + +If the PCRF due to an event determines that a UE context needs to be removed from the RCAF, the PCRF shall send an MUR command to the targeted RCAF to explicitly release the context related to the user id and PDN ID by including the Subscription-Id AVP indicating the user id, the Called-Station-Id AVP indicating the PDN ID, the Destination-Host AVP indicating the targeted RCAF id and the RUCI-Action AVP set to 2 (Release Context). + +The RCAF when receiving the MUR command from the PCRF shall release the context related to the user id and PDN ID. If this is the last PDN ID stored for this user id the RCAF shall release the complete context. + +The RCAF shall acknowledge the received MUR command by sending an MUA command. + +### 4.4.5 Race condition handling + +If the RCAF receives an MUR command to remove a context for a specific user id and PDN ID, the request shall be handled immediately, regardless of whether there are any ongoing RUCI report transactions for that user id and PDN ID. + +If the PCRF receives an NRR command for a specific user id and PDN ID, and if there is an ongoing MUR command to remove the context for that user id and PDN ID, the PCRF shall reject the incoming request with a Diameter experimental result code of DIAMETER\_PENDING\_TRANSACTION. + +If the PCRF receives an ARR command for specific user id and PDN ID combinations for which there is at least one ongoing MUR command to remove the context, the PCRF shall accept the request and only update the context(s) that are not in the process of being removed. + +# --- 5 Np protocol + +## 5.1 Protocol support + +The Np application is defined as a vendor specific Diameter application, where the vendor is 3GPP and the Application-ID for the Np Application in the present release is 16777342. The vendor identifier assigned by IANA to 3GPP (
Feature: A short name that can be used to refer to the bit and to the feature, e.g. "EPS".
M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O").
Description: A clear textual description of the feature. | | | | + +## 5.2 Initialization and maintenance of connection and session + +The Diameter protocol between the PCRF and the OCS, shall always keep the session state, and use the same Session-Id parameter for the lifetime of each Diameter session. + +Each Diameter session shall identify a Sy session for a given user. In order to indicate that the session state is to be maintained, the Diameter client and server shall not include the Auth-Session-State AVP, either in the request or in the response messages (see IETF RFC 6733 [23]). + +The PCRF shall link the Gx session(s) or S9 session with the Sy session at Sy session initialization and maintain that until the IP-CAN session(s) for that subscriber are terminated or no IP-CAN session for the same user depends on the spending status information provided over Sy reference point. + +## 5.3 Sy specific AVPs + +### 5.3.0 General + +Table 5.3.0.1 describes the Diameter AVPs defined for the Sy reference point, their AVP Code values, types and possible flag values. The Vendor-Id header of all AVPs defined in the present document shall be set to 3GPP (10415). + +**Table 5.3.0.1: Sy specific Diameter AVPs** + +| Attribute Name | AVP Code | Clause defined | Value Type | AVP Flag rules (Note 1) | | | | Applicability (Note 2) | +|------------------------------------|----------|----------------|------------|-------------------------|-----|------------|----------|------------------------| +| | | | | Must | May | Should not | Must not | | +| Pending-Policy-Counter-Information | 2905 | 5.3.5 | Grouped | M,V | P | | | | +| Pending-Policy-Counter-Change-Time | 2906 | 5.3.6 | Time | M,V | P | | | | +| Policy-Counter-Identifier | 2901 | 5.3.1 | UTF8String | M,V | P | | | | +| Policy-Counter-Status | 2902 | 5.3.2 | UTF8String | M,V | P | | | | +| Policy-Counter-Status-Report | 2903 | 5.3.3 | Grouped | M,V | P | | | | +| SL-Request-Type | 2904 | 5.3.4 | Enumerated | M,V | P | | | | +| SN-Request-Type | 2907 | 5.3.7 | Unsigned32 | V | P | | M | ASR | + +NOTE 1: The AVP header bit denoted as 'M', indicates whether support of the AVP is required. The AVP header bit denoted as 'V', indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 6733 [23]. + +NOTE 2: AVPs marked with a supported feature are applicable as described in subclause 5.1.6. + +### 5.3.1 Policy-Counter-Identifier AVP + +The Policy-Counter-Identifier AVP (AVP code 2901) is of type UTF8String, and it uniquely identifies a policy counter that is maintained per subscriber within the OCS. + +### 5.3.2 Policy-Counter-Status AVP + +The Policy-Counter-Status AVP (AVP code 2902) is of type UTF8String, and identifies the policy counter status applicable for a specific policy counter and subscriber. + +NOTE: The valid values for the Policy-Counter-Status AVP are specific for each Policy-Counter-Identifier value. + +The values (e.g. valid, invalid or any other status) are not specified. The interpretation and actions related to the defined values are out of scope of 3GPP. + +### 5.3.3 Policy-Counter-Status-Report AVP + +The Policy-Counter-Status-Report AVP (AVP code 2903) is of type Grouped. It is used by the OCS to report the status of a specific policy counter. + +Associated pending policy counter statuses shall always be provided within Pending-Policy-Counter-Information AVPs if the pending policy counter statuses are applicable to the policy counter identifier. If there are no Pending-Policy-Counter-Information AVPs provided within the Policy-Counter-Status-Report AVP, previously provided pending counter statuses are removed. In addition, newly provided pending policy counter statuses overwrite previously provided ones. + +AVP Format: + +``` +Policy-Counter-Status-Report ::= < AVP Header: 2903 > + { Policy-Counter-Identifier } + { Policy-Counter-Status } + *[ Pending-Policy-Counter-Information ] + *[ AVP ] +``` + +### 5.3.4 SL-Request-Type AVP + +The SL-Request-Type AVP (AVP code 2904) is of type Enumerated, and informs the OCS whether the SLR command is being sent as part of the initial or intermediate spending limit report request procedure. + +The following values are defined: + +INITIAL\_REQUEST (0) + +This value indicates that this is the first request in the Diameter session. + +INTERMEDIATE\_REQUEST (1) + +This value indicates that this is the second or subsequent request in the Diameter session. + +### 5.3.5 Pending-Policy-Counter-Information AVP + +The Pending-Policy-Counter-Information AVP (AVP code 2905) is of type Grouped, which contains the pending policy counter status and the active time. If multiple pending policy counter AVPs are included, they shall be sorted in order of change time. + +AVP Format: + +``` +Pending-Policy-Counter-Information ::= < AVP Header: 2905 > + { Policy-Counter-Status } + { Pending-Policy-Counter-Change-Time } + *[ AVP ] +``` + +NOTE: The valid values for the Pending-Policy-Counter-Information AVP are specific for each Policy-Counter-Identifier value. + +### 5.3.6 Pending-Policy-Counter-Change-Time AVP + +The Pending-Policy-Counter-Change-Time AVP (AVP code 2906) is of type Time. This value indicates the NTP time at which the pending policy counter status becomes the current status of a policy counter. + +### 5.3.7 SN-Request-Type AVP + +The SN-Request-Type AVP (AVP code 2907) shall be of type Unsigned32 and shall contain a bit mask, and informs the PCRF about the type of the Spending-Status-Notification-Request (SNR). The bit 0 shall be the least significant bit. For example, to get the value of bit 0, a bit mask of 0x0001 should be used. + +The following values are defined, and multiple bits may be set in combination: + +**Table 5.3.7-1: SN-Request-Type AVP** + +| Bit | Name | Description | +|-----|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Normal Request | This bit, when set, indicates that the SNR is used only to convey a spending limit report as detailed in subclause 4.5.2. This shall be the default value that applies when the SN-Request-Type AVP is not included in an SNR. | +| 1 | Abort Session Request | This bit, when set, indicates that the SNR is used to request the termination of the Sy session as detailed in subclause 4.5.4 | + +## 5.4 Sy re-used AVPs + +Table 5.4 lists the Diameter AVPs re-used by the Sy reference point from existing Diameter Applications, reference to their respective specifications and a short description of their usage within the Sy reference point. Other AVPs from existing Diameter Applications, except for the AVPs from Diameter base protocol, do not need to be supported. The AVPs from Diameter base protocol are not included in table 5.4, but they are re-used for the Sy reference point. Unless otherwise stated, re-used AVPs shall maintain their 'M', 'P' and 'V' flag settings. Where 3GPP Radius VSAs are re-used, unless otherwise stated, they shall be translated to Diameter AVPs as described in RFC 4005 [4] with the exception that the 'M' flag shall be set and the 'P' flag may be set. + +**Table 5.4: Sy re-used Diameter AVPs** + +| Attribute Name | Reference | Description | +|-----------------------|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DRMP | IETF RFC 7944 [21] | Allows Diameter endpoints to indicate the relative priority of Diameter transactions. | +| Subscription-Id | IETF RFC 4006 [5] | The identification of the subscription (IMSI, MSISDN, etc) | +| Load | IETF RFC 8583 [22] | The AVP used to convey load information between Diameter nodes.
This AVP and all AVPs within this grouped AVP shall have the 'M' bit cleared. | +| Logical-Access-ID | ETSI TS 283 034 [17] | Contains a Circuit-ID (as defined in IETF RFC 3046 [18]). The Logical Access ID may explicitly contain the identity of the Virtual Path and Virtual Channel carrying the traffic. Applicable only for Fixed Broadband Access network convergence as defined in annex A.
This AVP shall have the 'M' bit cleared. | +| OC-OLR | IETF 7683 [20] | Contains the necessary information to convey an overload report. | +| OC-Supported-Features | IETF 7683 [20] | Defines the support for the Diameter overload indication conveyance by the sending node. | +| Physical-Access-ID | ETSI TS 283 034 [17] | Identifies the physical access to which the user equipment is connected. Includes a port identifier and the identity of the access node where the port resides. Applicable only for Fixed Broadband Access network convergence as defined in annex A.
This AVP shall have the 'M' bit cleared. | +| Supported-Features | 3GPP TS 29.229 [15] | If present in a request, this AVP informs the destination host about the features that the origin host supports. If present in an answer, this AVP informs the destination host about common features with the origin host. | + +## 5.5 Sy specific Experimental-Result-Code AVP values + +### 5.5.1 General + +IETF RFC 6733 [23] specifies the Experimental-Result AVP containing Vendor-ID AVP and Experimental-Result-Code AVP. The Experimental-Result-Code AVP (AVP Code 298) is of type Unsigned32 and contains a vendor-assigned value representing the result of processing a request. The Vendor-ID AVP shall be set to 3GPP (10415). + +### 5.5.2 Permanent Failures + +Errors that fall within the Permanent Failures category shall be used to inform the peer that the request failed, and the request should not be attempted again. + +The Result-Code AVP values defined in Diameter base protocol IETF RFC 6733 [23] are applicable. Also, the following Result-Code AVP value defined in IETF RFC 4006 [5] is applicable: + +DIAMETER\_USER\_UNKNOWN (5030) + +This error shall be used by the OCS to indicate to the PCRF that the end user specified in the request is unknown to the OCS and that the Sy session cannot be created. + +The following specific Sy Experimental-Result-Code value is defined for permanent failures: + +DIAMETER\_ERROR\_UNKNOWN\_POLICY\_COUNTERS (5570) + +This error shall be used by the OCS to indicate to the PCRF that the OCS does not recognize one or more Policy Counters specified in the request, when the OCS is configured to reject the request provided with unknown policy counter identifier(s). + +### 5.5.3 Transient Failures + +Errors that fall within the transient failures category are used to inform a peer that the request could not be satisfied at the time it was received, but may be able to satisfy the request in the future. + +The Result-Code AVP values defined in Diameter base protocol IETF RFC 6733 [23] are applicable. Also the following specific Sy Experimental-Result-Code value is defined for transient failures: + +DIAMETER\_ERROR\_NO\_AVAILABLE\_POLICY\_COUNTERS (4241) + +This error shall be used by the OCS to indicate to the PCRF that the OCS has no available policy counters for the subscriber. + +The PCRF may retry the request based on local configuration or operator policy on receipt of a transient failure. + +## 5.6 Sy Messages + +### 5.6.1 Command-Code Values + +This section defines the Command-Code values for the Sy interface application as allocated by IANA from the vendor-specific namespace defined in IETF RFC 5719 [6]. Every command is defined by means of the ABNF syntax IETF RFC 2234 [7], according to the rules in IETF RFC 6733 [23]. + +The following Command Codes are defined in this specification: + +**Table 5.6.1: Command-Code values for Sy** + +| Command-Name | Abbreviation | Code | Section | +|--------------------------------------|--------------|---------|---------| +| Spending-Limit-Request | SLR | 8388635 | 5.6.2 | +| Spending-Limit-Answer | SLA | 8388635 | 5.6.3 | +| Spending-Status-Notification-Request | SNR | 8388636 | 5.6.4 | +| Spending-Status-Notification-Answer | SNA | 8388636 | 5.6.5 | + +In addition, the Session-Termination-Request and Session-Termination-Answer commands are reused from IETF RFC 6733 [23]. + +For the commands defined in this specification and reused commands, the Application-ID field shall be set to 16777302. + +### 5.6.2 Spending-Limit-Request (SLR) command + +The SLR command, indicated by the Command-Code field set to 8388635 and the 'R' bit set in the Command Flags field, is sent by the PCRF to the OCS as part of the Initial or Intermediate Spending Limit Report Request procedure. + +Message Format: + +``` +
Type of authorization requested by the I-CSCF.
If the request corresponds to a de-registration, i.e. Expires field or expires parameter in Contact field in the REGISTER method is equal to zero, this AVP shall be present in the command and the value shall be set to DE-REGISTRATION.
If the request corresponds to an initial registration or a re-registration, i.e. Expires field or expires parameter in Contact field in the REGISTER method is not equal to zero then this AVP may be absent from the command. If present its value shall be set to REGISTRATION.
If the request corresponds to an initial registration or a re-registration or a de-registration and the I-CSCF explicitly queries the S-CSCF capabilities, then this AVP shall be present in the command and the value shall be set to REGISTRATION_AND_CAPABILITIES. The I-CSCF shall use this value when the S-CSCF currently assigned to the Public User Identity in the HSS, cannot be contacted and a new S-CSCF needs to be selected. The I-CSCF shall also use this value for RLOS related registrations when the S-CSCF currently assigned to the Public User Identity in the HSS does not support RLOS (see 3GPP TS 23.228 [1] annex Z) and a new S-CSCF (supporting RLOS) needs to be selected.
RLOS support of the different S-CSCFs shall be locally configured in the I-CSCF, and this capability is independent on the subscribed capabilities received from HSS.
| +| Private User Identity (See 7.3) | User-Name | M | Private User Identity | +| Routing Information (See 7.13) | Destination-Host, Destination-Realm | C | If the I-CSCF knows HSS name Destination-Host AVP shall be present in the command. Otherwise, only Destination-Realm AVP shall be present and the command shall be routed to the next Diameter node, e.g. SLF, based on the Diameter routing table in the I-CSCF. | +| UAR Flags (See 7.19) | UAR-Flags | O | This Information Element contains a set of indications. See 7.19 for the content of the information element. | + +**Table 6.1.1.2: User registration status response** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|----------------------------------|--------------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result(See 7.6) | Result-Code /
Experimental-Result | M | Result of the operation.
Result-Code AVP shall be used for errors defined in the Diameter base protocol (see IETF RFC 6733 [31]).
Experimental-Result AVP shall be used for Cx/Dx errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| S-CSCF capabilities
(See 7.5) | Server-Capabilities | O | Required capabilities of the S-CSCF to be assigned to the IMS Subscription. | +| S-CSCF Name
(See 7.4) | Server-Name | C | Name of the assigned S-CSCF. | + +#### 6.1.1.1 Detailed behaviour + +The HSS shall, in the following order (if there is an error in any of the following steps the HSS shall stop processing and return the corresponding error code, see TS 29.229 [5]): + +0. If the HSS supports WebRTC as described in TS 23.228 [1] clause U.2.1.4, it shall check if the Private User Identity and the Public User Identity are managed by a third party, if so the HSS continues in step 4. + +NOTE : How the HSS identifies that the Private User Identity and the Public User Identity are managed by a third party for WebRTC and how the HSS identifies the corresponding user profile are implementation specific. + +1. Check that the Private User Identity and the Public User Identity exists in the HSS. If not Experimental-Result-Code shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN. +2. Check that the Public User Identity matches a distinct Public User Identity in the HSS. If it doesn't, the Experimental-Result-Code shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN. +3. Check that the Public User Identity received in the request is associated with the Private User Identity received in the request. If not Experimental-Result-Code shall be set to DIAMETER\_ERROR\_IDENTITIES\_DONT\_MATCH. +4. Check whether the Public User Identity received in the request is barred from the establishment of multimedia sessions. + - If it is an IMS Emergency Registration (by checking the UAR Flags) or the Public User Identity received in the request is not barred, continue to step 5. + - Otherwise, the HSS shall check whether there are other non-barred Public User Identities to be implicitly registered with that one. + - If so, continue to step 5. + - If not, Result-Code shall be set to DIAMETER\_AUTHORIZATION\_REJECTED. +5. Check the User-Authorization-Type received in the request: + - If it is REGISTRATION or if User-Authorization-Type is absent from the request, the HSS shall check whether the UAR Flags indicate that this is an IMS Emergency Registration: + - If it is not, and the Public User Identity is allowed to roam in the visited network (if not Experimental-Result-Code shall be set to DIAMETER\_ERROR\_ROAMING\_NOT\_ALLOWED) and authorized to register (if not Result-Code shall be set to DIAMETER\_AUTHORIZATION\_REJECTED) then continue to step 6. + - If it is an IMS Emergency Registration, authorization shall be granted and the HSS shall not perform any check regarding roaming. Continue to step 6. + - If it is DE\_REGISTRATION, the HSS may not perform any check regarding roaming. Continue to step 6. + +- If it is REGISTRATION\_AND\_CAPABILITIES, the HSS shall check whether the UAR Flags indicate that this is an IMS Emergency Registration: +- If it is not, and the Public User Identity is allowed to roam in the visited network (if not Experimental-Result-Code shall be set to DIAMETER\_ERROR\_ROAMING\_NOT\_ALLOWED) and authorized to register (if not Result-Code shall be set to DIAMETER\_AUTHORIZATION\_REJECTED). The HSS may return the Server-Capabilities AVP, which enables the I-CSCF to select an S-CSCF. The returned capabilities, if any, shall satisfy all the requirements of all the service profiles associated with the IMS Subscription. If Server-Capabilities AVP is absent, it indicates to the I-CSCF that it can select any available S-CSCF. If an S-CSCF is already assigned in the HSS and IMS Restoration Procedures are supported in the HSS, the HSS shall set the S-CSCF reassignment pending flag and shall allow overwriting of the S-CSCF name in the next SAR request. Result-Code shall be set to DIAMETER\_SUCCESS. The HSS shall not return any S-CSCF name. Stop processing. +- If it is an IMS Emergency Registration, authorization shall be granted and the HSS shall not perform any check regarding roaming. The HSS may return the Server-Capabilities AVP, which enables the I-CSCF to select an S-CSCF. The returned capabilities, if any, shall satisfy all the requirements of all the service profiles associated with the IMS Subscription. The Server-Capabilities AVP may be absent, to indicate to the I-CSCF that it can select any available S-CSCF. Result-Code shall be set to DIAMETER\_SUCCESS. The HSS shall not return any S-CSCF name. Stop processing. + +##### 6. Check the state of the Public User Identity received in the request: + +- If it is registered, the HSS shall return the stored S-CSCF name. No S-CSCF capabilities shall be present in the response. If User-Authorization-Type is equal to REGISTRATION or is absent, Experimental-Result-Code shall be set to DIAMETER\_SUBSEQUENT\_REGISTRATION. If User-Authorization-Type is equal to DE-REGISTRATION, Result-Code shall be set to DIAMETER\_SUCCESS. +- If it is unregistered (i.e. registered as a consequence of an originating or terminating request or there is an S-CSCF keeping the user profile stored) and User-Authorization-Type is equal to DE-REGISTRATION, the HSS shall return the stored S-CSCF name and the Result-Code shall be set to DIAMETER\_SUCCESS. If the User-Authorization-Type is equal to REGISTRATION or is absent, then the HSS shall return the stored S-CSCF name and the Experimental-Result-Code set to DIAMETER\_SUBSEQUENT\_REGISTRATION. The HSS shall not return any S-CSCF capabilities. +- If it is not registered yet, the HSS shall check the value of User-Authorization-Type received in the request: + - If the value of User-Authorization-Type is DE\_REGISTRATION and the Authentication pending flag is set, the HSS shall return the stored S-CSCF name and Experimental-Result-Code set to DIAMETER\_SUCCESS. The HSS shall not return any S-CSCF capabilities. Otherwise, if Authentication pending flag is not set, the HSS shall not return any S-CSCF name or S-CSCF capabilities. The HSS shall set the Experimental-Result-Code to DIAMETER\_ERROR\_IDENTITY\_NOT\_REGISTERED in the response. + - If the value of User-Authorization-Type is REGISTRATION or is absent, then the HSS shall check if there is at least one Public User Identity within the IMS Subscription with an S-CSCF name assigned. + - If there is at least one Public User Identity within the IMS Subscription that is registered, the HSS shall return the S-CSCF name assigned for that Public User Identity and Experimental-Result-Code set to DIAMETER\_SUBSEQUENT\_REGISTRATION. The HSS shall not return any S-CSCF capabilities. + - If there is at least one Public User Identity within the IMS Subscription that is unregistered (i.e. registered as a consequence of an originating or terminating request or there is an S-CSCF keeping the user profile stored), then the HSS shall return the stored S-CSCF name and the Experimental-Result-Code set to DIAMETER\_SUBSEQUENT\_REGISTRATION. The HSS shall not return any S-CSCF capabilities. + - If there is no identity of the user within the same IMS Subscription that is registered or unregistered, the HSS shall check if there is an S-CSCF name stored for the user (e.g. the user is being authenticated by the S-CSCF as indicated by the Authentication pending flag). If it is, the HSS shall return the stored S-CSCF name and Experimental-Result-Code set to DIAMETER\_SUBSEQUENT\_REGISTRATION. The HSS shall not return any S-CSCF capabilities. + +- If there is not any Public User Identity within the IMS Subscription with an S-CSCF name assigned, then the HSS may return the Server-Capabilities AVP, which enables the I-CSCF to select an S-CSCF. The returned capabilities, if any, shall satisfy all the requirements of all the service profiles associated with the IMS Subscription. The Server-Capabilities AVP may be absent, to indicate to the I-CSCF that it may select any available S-CSCF. Experimental-Result-Code shall be set to DIAMETER\_FIRST\_REGISTRATION. The HSS shall not return any S-CSCF name. + +If the HSS cannot fulfil received request, e.g. due to database error, it shall set Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. No S-CSCF name or S-CSCF capabilities shall be present in the response. + +### 6.1.2 S-CSCF registration/deregistration notification + +This procedure is used between the S-CSCF and the HSS. The procedure is invoked by the S-CSCF, corresponds to the combination of the operations Cx-Put and Cx-Pull (see TS 23.228 [1]) and is used: + +- To assign an S-CSCF to a Public Identity, or to clear the name of the S-CSCF assigned to one or more Public Identities. +- To download from HSS the relevant user information for the S-CSCF. +- To backup and retrieve the S-CSCF Restoration Information (see TS 23.380 [19]) in the HSS. +- To provide a P-CSCF Restoration Indication to the HSS and trigger P-CSCF Restoration mechanism. + +This procedure is mapped to the commands Server-Assignment-Request/Answer in the Diameter application specified in TS 29.229 [5]. Tables 6.1.2.1 and 6.1.2.2 describe the involved information elements. + +Table 6.1.2.1: S-CSCF registration/deregistration notification request + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------------------------------|-----------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Public User Identity / Public Service Identity (See 7.2 and 7.2a) | Public-Identity | C | Public Identity or list of Public Identities.
One and only one Public Identity shall be present if the Server-Assignment-Type is any value other than TIMEOUT_DEREGISTRATION, USER_DEREGISTRATION, DEREGISTRATION_TOO_MUCH_DATA, TIMEOUT_DEREGISTRATION_STORE_SERVER_NAME, USER_DEREGISTRATION_STORE_SERVER_NAME or ADMINISTRATIVE_DEREGISTRATION.
If Server-Assignment-Type indicates deregistration of some type and Private Identity is not present in the request, at least one Public Identity shall be present. | +| S-CSCF Name (See 7.4) | Server-Name | M | Name of the S-CSCF. | +| Private User Identity / Private Service Identity (See 7.3 and 7.3a) | User-Name | C | Private Identity.
It shall be present if it is available when the S-CSCF issues the request. It may be absent during the initiation of a session to an unregistered Public Identity (Server-Assignment-Type shall contain the value UNREGISTERED_USER) or after S-CSCF recovery upon originating request different than REGISTER (Server-Assignment-Type shall contain the value NO_ASSIGNMENT).
In case of de-registration, Server-Assignment-Type equal to TIMEOUT_DEREGISTRATION, ADMINISTRATIVE_DEREGISTRATION, DEREGISTRATION_TOO_MUCH_DATA or TIMEOUT_DEREGISTRATION_STORE_SERVER_NAME if no Public-Identity AVPs are present then User-Name AVP shall be present. | +| Server Assignment Type (See 7.8) | Server-Assignment-Type | M | Type of update, request or notification that the S-CSCF requests in the HSS (e.g. de-registration). See 3GPP TS 29.229 [5] for all the possible values. | +| User Data Already Available (See 7.16) | User-Data-Already-Available | M | This indicates if the user profile and charging information and, if supported and present in the subscription, allowed WAF and/or WWSF identities are already available in the S-CSCF.
In the case where Server-Assignment-Type is not equal to NO_ASSIGNMENT, REGISTRATION, RE_REGISTRATION or UNREGISTERED_USER, the HSS shall not use User Data Already Available when processing the request. | +| Routing Information (See 7.13) | Destination-Host | C | If the S-CSCF knows the HSS name, the Destination-Host AVP shall be present in the command.
This information is available if the request belongs to an already existing registration, e.g. in case of the re-registration, where the HSS name is stored in the S-CSCF. The HSS name is obtained from the Origin-Host AVP, which is received from the HSS, e.g. included in the MAA command. This information may not be available if the command is sent as a consequence of a session termination for an unregistered Public Identity. In this case the Destination-Host AVP is not present and the command is routed to the next Diameter node, e.g. SLF, based on the Diameter routing table in the S-CSCF. | +| Wildcarded Public Identity (See 7.2b) | Wildcarded-Public-Identity | O | If the request refers to a Wildcarded PSI or Wildcarded Public User Identity, and the Server-Assignment-Type is set to UNREGISTERED_USER, NO_ASSIGNMENT, TIMEOUT_DEREGISTRATION_STORE_SERVER_NAME, ADMINISTRATIVE_DEREGISTRATION, DEREGISTRATION_TOO_MUCH_DATA or TIMEOUT_DEREGISTRATION, the S-CSCF may include the corresponding Wildcarded PSI or Wildcarded Public User Identity in this information element.
If this element is present, it shall be used by the HSS to identify the identity affected by the request. The terms Public Identity or Public Service Identity in the detailed behaviour refer then to the Wildcarded Public Identity. | +| S-CSCF Restoration Information (See 7.21) | SCSCF-Restoration-Info | C | When the S-CSCF supports IMS Restoration Procedures, if Server-Assignment-Type is REGISTRATION or RE_REGISTRATION, and any of the related restoration information changed compared to the previous one, the S-CSCF shall send this information element to the HSS. This information allows a later retrieval in case of an S-CSCF service interruption. | + +| | | | | +|---------------------------------------------|----------------------------------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Multiple-Registration-Indication (See 7.23) | Multiple-Registration-Indication | C | When the S-CSCF supports IMS Restoration Procedures, if Server-Assignment-Type is REGISTRATION and the registration is a multiple registration and the Public User Identity is not stored as registered with the Private User Identity as in the request in the S-CSCF, the S-CSCF shall send this information element to the HSS. | +| Session-Priority (See 7.24) | Session-Priority | O | This information element, if present, shall indicate the session's priority to the HSS. | +| SAR Flags (See 7.28) | SAR-Flags | O | This Information Element contains a set of indications. See 7.28 for the content of the information element. | + +Table 6.1.2.2: S-CSCF registration/deregistration notification response + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------------------------------|-----------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Private User Identity / Private Service Identity (See 7.3 and 7.3a) | User-Name | C | Private Identity.
It shall be present if it is available when the HSS sends the response.
It may be absent in the following error case: when the Server-Assignment-Type of the request is UNREGISTERED_USER and the received Public Identity is not known by the HSS. | +| Registration result (See 7.6) | Result-Code / Experimental-Result | M | Result of registration.
Result-Code AVP shall be used for errors defined in the Diameter base protocol (see IETF RFC 6733 [31]).
Experimental-Result AVP shall be used for Cx/Dx errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| User Profile (See 7.7) | User-Data | C | Relevant user profile.
It shall be present when Server-Assignment-Type in the request is equal to NO_ASSIGNMENT, REGISTRATION, RE_REGISTRATION or UNREGISTERED_USER according to the rules defined in clause 6.6.
If the S-CSCF receives more data than it is prepared to accept, it shall perform the de-registration of the Private Identity with Server-Assignment-Type set to DEREGISTRATION_TOO_MUCH_DATA and send back a SIP 3xx or 480 (Temporarily Unavailable) response, which shall trigger the selection of a new S-CSCF by the I-CSCF, as specified in 3GPP TS 24.229 [8]. | +| Charging Information (See 7.12) | Charging-Information | C | Addresses of the charging functions.
It shall be present when the User-Data AVP is sent to the S-CSCF according to the rules defined in clause 6.6.
When this parameter is included, either the Primary-Charging-Collection-Function-Name AVP or the Primary-Event-Charging-Function-Name AVP shall be included. All other elements shall be included if they are available. | +| Associated Private Identities | Associated-Identities | O | This AVP contains all Private Identities, which belong to the same IMS subscription as the Private Identity or Public Identity received in the SAR command.
If the IMS subscription contains only single Private Identity this AVP shall not be present. | +| Loose-Route Indication | Loose-Route-Indication | C | This AVP indicates to the S-CSCF that loose-route mechanism shall be applied to the public identities contained in the user profile received from the HSS.
If the loose-route mechanism is required, this AVP shall be present and set to LOOSE_ROUTE_REQUIRED.
If the Loose-Route mechanism is not required, this AVP may be either absent or present. If present, it shall be set to LOOSE_ROUTE_NOT_REQUIRED. | +| S-CSCF Restoration Information (See 7.21) | SCSCF-Restoration-Info | C | This information shall be present if it was stored by the S-CSCF in the HSS and Server-Assignment-Type is either UNREGISTERED_USER or NO_ASSIGNMENT.
This information shall also be present if it was stored by the S-CSCF in the HSS and the SAR indicates it is related to a multiple registration and Server-Assignment-Type is REGISTRATION.
This information may be present if it was stored by the S-CSCF in the HSS and Server-Assignment-Type is either REGISTRATION or RE_REGISTRATION and there are other Private Identities different from the Private Identity received in the SAR command being registered with the Public Identity received in the SAR command. | +| Associated Registered Private Identities (See 7.22) | Associated-Registered-Identities | C | This AVP contains all Private Identities that were registered with the Public Identity received in the SAR command.
The HSS shall send this information element if the IMS Restoration Procedures are supported and the value of Server-Assignment-Type in the request is REGISTRATION or RE_REGISTRATION and there are other Private Identities different from the Private Identity received in the SAR command being registered with the Public Identity received in the SAR command.
Otherwise, this AVP shall not be present. | + +| | | | | +|--------------------------------------------------------|--------------------------------------|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| S-CSCF Name
(See 7.4) | Server-Name | C | Name of the assigned S-CSCF.
This AVP shall be present, if the requesting S-CSCF name is different from the previously assigned S-CSCF name stored in the HSS. | +| Wildcarded Public Identity
(See 7.2b) | Wildcarded-Public-Identity | C | This AVP shall be present if:
- the value of Server-Assignment-Type in the request was UNREGISTERED_USER or NO_ASSIGNMENT and
- the Wildcarded-Public-Identity AVP in the request was not present and
- the Public Identity in the request fell within the range of a Wildcarded Public User Identity in the HSS whose state is registered/unregistered.
If this element is present, it shall be used by the S-CSCF to identify the identity affected by the request. | +| Privileged-
Sender
Indication
(See 7.26) | Privileged-
Sender-
Indication | O | This AVP indicates if the Private User Identity shall be considered as a privileged sender.
If not present, it means that the Private User Identity is not considered a privileged sender. | +| Allowed WAF
and/or WWSF
Identities (See
7.29) | Allowed-WAF-
WWSF-
Identities | C | Addresses of the WAFs and/or WWSFs the subscription is allowing to use.
This AVP shall be present if both
a) it is applicable for the subscription and
b) the User-Data AVP is present. | + +#### 6.1.2.1 Detailed behaviour + +On registering/deregistering a Public Identity the S-CSCF shall inform the HSS. The same procedure is used by the S-CSCF: + +- to get the user information which contains the user profile, the charging information and the allowed WAF and/or WWSF Identities. The relevant user profile downloaded is described in more detailed in clauses 6.5.1 and 6.6. +- to provide a P-CSCF Restoration Indication to the HSS when the S-CSCF, supporting the HSS based P-CSCF restoration mechanism described in TS 23.380 [19], has identified a P-CSCF failure for a given UE and then triggers the P-CSCF Restoration mechanism execution for this UE. + +The Public-Identity AVP and User-Data AVPs in this command pair shall contain only one type of identities i.e. either only Public User Identities, or only Public Service Identities. User initiated registration/deregistration procedures (i.e. server-assignment-type is set to RE\_REGISTRATION, USER\_DEREGISTRATION, etc.) shall only be allowed for distinct Public User Identities. + +The HSS holds information about the state of registration of all the identities related to an IMS Subscription. The S-CSCF uses this procedure to update such states. For Shared Public User Identities, the S-CSCF shall initiate this procedure towards the HSS for each Private User Identity undergoing a Registration or Deregistration related to the Shared Public User Identity. For implicitly registered identities, the rules defined in Clause 6.5.1 shall apply. + +When the request message was received because of a terminating session request, the HSS may prioritise the received request message according to priority level received within the Session-Priority AVP. + +NOTE 1: Refer to Annex J for HSS procedures associated with the handling of both the Session-Priority AVP and DRMP AVP received in the request message. + +The HSS shall, in the following order (in case of an error in any of the steps the HSS shall stop processing and return the corresponding error code, see TS 29.229 [5]): + +1. Check that the Public Identity and Private Identity exist in the HSS. If not Experimental-Result-Code shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN. +2. The HSS may check whether the Private and Public Identities received in the request are associated in the HSS. If not Experimental-Result-Code shall be set to DIAMETER\_ERROR\_IDENTITIES\_DONT\_MATCH. +3. If more than one Public-Identity AVP is present and the Server-Assignment-Type is one of the values defined in Table 6.1.2.1 as applying for only one identity, then the Result Code shall be set to DIAMETER\_AVP\_OCCURS\_TOO\_MANY\_TIMES and no user information shall be returned. +4. The HSS shall check the Public Identity type received in the request. + +- If the identity in the request is a distinct Public User Identity, continue in step 5, otherwise the HSS shall check the server-assignment-type: + +If it indicates REGISTRATION, RE\_REGISTRATION, USER\_DEREGISTRATION, USER\_DEREGISTRATION\_STORE\_SERVER\_NAME, AUTHENTICATION\_FAILURE or AUTHENTICATION\_TIMEOUT, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_IN\_ASSIGNMENT\_TYPE. + +- If the identity in the request is a Public Service Identity, then check if the PSI Activation State for that identity is active. If not, then the response shall contain Experimental-Result-Code set to DIAMETER\_ERROR\_USER\_UNKNOWN. + +##### 5. Check the Server Assignment Type value received in the request: + +- If it indicates REGISTRATION or RE\_REGISTRATION, the HSS shall check whether the Public Identity is assigned for the S-CSCF requesting the data. + +If there is already an S-CSCF assigned to the user and the requesting S-CSCF is not the same as the previously assigned S-CSCF, and IMS restoration procedures are not supported or the S-CSCF reassignment pending flag is not set, the HSS shall include the name of the previously assigned S-CSCF in the response message and the Experimental-Result-Code shall be set to DIAMETER\_ERROR\_IDENTITY\_ALREADY\_REGISTERED. + +If there is already an S-CSCF assigned to the user and the requesting S-CSCF is not the same as the previously assigned S-CSCF and IMS restoration procedures are supported, and the S-CSCF reassignment pending flag is set, the HSS shall overwrite the S-CSCF name and shall reset the S-CSCF reassignment pending flag. + +If there is no S-CSCF assigned to the user or the requesting S-CSCF is the same as the previously assigned S-CSCF stored in the HSS, the HSS shall download the relevant user information taking into consideration the value set in the User-Data-Already-Available AVP (see clause 6.6). The Result-Code shall be set to DIAMETER\_SUCCESS and the HSS shall set the registration state of the Public User Identity as registered (if not already registered). If the S-CSCF Restoration Information is included in the request and the HSS implements IMS Restoration procedures, and if it is RE\_REGISTRATION, the HSS shall store this information. If the Public User Identity's authentication pending flag which is specific for the Private User Identity is set, the HSS shall clear it. If there are multiple Private User Identities, which belong to the served IMS subscription the Associated-Identities AVP should be added to the answer message and it shall contain all Private User Identities associated to the IMS subscription. If the loose-route mechanism is required for the registered Public User Identities, the Loose-Route-Indication AVP shall be added to the answer message. If there are multiple Private User Identities being registered with the Public Identity received in the request message, and the IMS Restoration Procedures are supported in the HSS, the Associated-Registered-Identities AVP shall be added to the answer message and it shall contain all Private User Identities being registered with the Public Identity, and subject to the operator policy, the HSS may include all stored S-CSCF Restoration Information groups associated to the Private User Identities in the response. + +NOTE 2: If the HSS returns all the S-CSCF Restoration Information groups in the response, the S-CSCF can ignore the Associated-Registered-Identities AVP and skip additional Server-Assignment-Request since the information is already made available. + +If it is REGISTRATION and the HSS implements IMS Restoration procedures, if multiple registration indication is included in the request and the Public User Identity is stored as registered in the HSS, and there is restoration information related to the Private User Identity, the HSS shall not overwrite the stored S-CSCF Restoration Information, instead, it shall send the stored S-CSCF restoration information together with the user profile in the SAA. Subject to the operator policy, if there is S-CSCF Restoration Information associated with several Private User Identities, the HSS may include all the S-CSCF Restoration Information groups in the response. The Experimental-Result-Code shall be set to DIAMETER\_ERROR\_IN\_ASSIGNMENT\_TYPE. Otherwise, the HSS shall store the received S-CSCF restoration information. The Result-Code shall be set to DIAMETER\_SUCCESS. + +- If it indicates UNREGISTERED\_USER, the following applies. + +If the P-CSCF-Restoration-Indication is included in SAR-Flags AVP, the HSS supporting the P-CSCF-Restoration-mechanism feature shall check whether at least one of the serving node(s) for corresponding user support this feature. If none of the serving nodes support the feature, the HSS shall stop processing this + +request and the Result-Code shall be set to DIAMETER\_ERROR\_SERVING\_NODE\_FEATURE\_UNSUPPORTED. + +The HSS shall check whether the Public Identity is assigned for the S-CSCF requesting the data: + +- If there is already an S-CSCF assigned to the user and the requesting S-CSCF is not the same as the previously assigned S-CSCF, and IMS restoration procedures are not supported or the S-CSCF reassignment pending flag is not set and a P-CSCF-Restoration-Indication is not included in SAR-Flags AVP, the HSS shall include the name of the previously assigned S-CSCF in the response message and the Experimental-Result-Code shall be set to DIAMETER\_ERROR\_IDENTITY\_ALREADY\_REGISTERED. +- If there is already an S-CSCF assigned to the user and the requesting S-CSCF is not the same as the previously assigned S-CSCF and IMS restoration procedures are supported, and the S-CSCF reassignment pending flag is set, the HSS shall overwrite the S-CSCF name and shall reset the S-CSCF reassignment pending flag. +- If there is no S-CSCF assigned to the user or the requesting S-CSCF is the same as the previously assigned S-CSCF stored in the HSS, the HSS shall store the S-CSCF name. + +The HSS shall check the Public Identity registration state: + +- If the registration state of the Public Identity is not registered or unregistered, the HSS shall set or keep the registration state of the Public Identity as unregistered, i.e. registered as a consequence of an originating or terminating request and if a P-CSCF-Restoration-Indication is not included in SAR-Flags AVP download the relevant user information. The Result-Code shall be set to DIAMETER\_SUCCESS. If there are multiple Private User Identities associated to the Public User Identity in the HSS, the HSS shall arbitrarily select one of the Private User Identities and put it into the response message. +- If the registration state of the Public Identity is registered and IMS restoration procedures are not supported, the HSS shall set the registration state of the Public identity as unregistered, clear any S-CSCF Restoration Information associated with the Public User Identity (if any) and if a P-CSCF-Restoration-Indication is not included in SAR-Flags AVP download the relevant user information. The Result-Code shall be set to DIAMETER\_SUCCESS. If there are multiple Private User Identities associated to the Public User Identity in the HSS, the HSS shall arbitrarily select one of the Private User Identities and put it into the response message. + +NOTE 3: The case where S-CSCF Restoration Information is stored in the HSS even though IMS Restoration Procedures are not supported corresponds to the situation where the HSS supports IMS Restoration Procedures but a new assigned S-CSCF does not, while the former S-CSCF supported this feature. + +- If the registration state of the Public Identity is registered and IMS restoration procedures are supported and a P-CSCF-Restoration-Indication is not included in SAR-Flags AVP, the HSS shall include in the response all S-CSCF Restoration Information related with the Public User Identity. If there is S-CSCF Restoration Information associated with several Private User Identities, the HSS shall include all the S-CSCF Restoration Information groups in the response. The Experimental-Result-Code shall be set to DIAMETER\_ERROR\_IN\_ASSIGNMENT\_TYPE. +- If the registration state of the Public Identity is Registered and IMS Restoration Procedures are supported and a P-CSCF-Restoration-Indication is included in SAR-Flags AVP, the HSS shall set the registration state of the Public identity as Unregistered and clear any S-CSCF Restoration Information associated with the Public User Identity (if any). The Result-Code shall be set to DIAMETER\_SUCCESS. + +If there are multiple Private User Identities, which belong to the served IMS subscription the Associated-Identities AVP should be added to the answer message and it shall contain all Private User Identities associated to the IMS subscription. + +If the S-CSCF receives a wildcarded public identity from the I-CSCF, the S-CSCF shall use this wildcarded public identity to fetch the user profile (i.e. by sending a Cx-SAR including Wildcarded-Public-Identity AVP if the profile is not available) and registration information locally stored. + +If the S-CSCF does not receive a wildcarded public identity, the S-CSCF shall not perform wildcarded public identity matching and shall use the public identity received instead to fetch the user profile (i.e. by sending a + +Cx-SAR without including Wildcarded-Public-Identity AVP if the profile is not available) and registration information. + +NOTE 4: There may be SIP requests in which the S-CSCF does not receive information of a wildcarded public identity, e.g. originating call from an AS on behalf of a user. + +NOTE 5: Since a distinct public identity falling into the range of a wildcarded public identity can have a different service profile, the S-CSCF does not perform the wildcarded public identity matching against the public identity received to avoid using the wrong service profile. + +If the Wildcarded-Public-Identity AVP is not received and if the Public Identity falls within the range of a wildcarded public identity whose registration state is registered and a P-CSCF-Restoration-Indication is not included in SAR-Flags AVP, the HSS shall not overwrite the registration state. The Result-Code shall be set to DIAMETER\_ERROR\_IN\_ASSIGNMENT\_TYPE and the HSS shall include the Wildcarded-Public-Identity AVP in the response. Upon reception of this error, the S-CSCF should behave as if it has received a wildcarded public identity in the first place. + +If SAR-Flags AVP includes a P-CSCF-Restoration-Indication, the HSS supporting the P-CSCF-Restoration-mechanism feature shall send a P-CSCF restoration indication to the serving nodes where the IMSI associated to the received Private Identity is registered, i.e. SGSN and/or MME, using S6a/S6d IDR/IDA or Gr ISD request/answer as described in TS 23.380 [19] clause 5.4. The Result-Code shall be set to DIAMETER\_SUCCESS. + +- If it indicates TIMEOUT\_DEREGISTRATION, USER\_DEREGISTRATION, DEREGISTRATION\_TOO\_MUCH\_DATA or ADMINISTRATIVE\_DEREGISTRATION, the following applies. + +If it indicates ADMINISTRATIVE\_DEREGISTRATION and if the P-CSCF-Restoration-Indication is included in SAR-Flags AVP, the HSS supporting the P-CSCF-Restoration-mechanism feature shall check whether at least one of the serving node(s) for corresponding user support this feature. If none of the serving nodes support the feature, the HSS shall stop processing this request and the Result-Code shall be set to DIAMETER\_ERROR\_SERVING\_NODE\_FEATURE\_UNSUPPORTED. + +The HSS shall check the registration state for all the Public Identities in the request. + +- If a Private User Identity is present in the request, if the request did not contain Public Identities the HSS shall check the registration state of the Public Identities associated with the Private Identity identified in the request. For each Public Identity: + - If the registration state of the Public User Identity is Registered, the HSS shall check if the Public User Identity is currently registered with one or more Private User Identities. + - If the Public User Identity is currently registered with only one Private User Identity, the HSS shall set the registration state of the Public User Identity to Not Registered and clear the S-CSCF name and any S-CSCF Restoration Information associated with the Public User Identity. + - If the Public User Identity is currently registered with more than one Private User Identity, the HSS shall keep the registration state of the Public User Identity as Registered and retain the S-CSCF name associated with the Public User Identity. The HSS shall remove any S-CSCF Restoration Information associated to the registration of this Public User Identity with this Private User Identity. + - If a Private User Identity is absent in the request, if the Public User Identity is currently registered with more than one Private User Identity, the HSS shall stop processing this request and shall set the Result-Code to DIAMETER\_MISSING\_AVP. + - if the registration state of the Public Identity is Unregistered, the HSS shall set the registration state of the Public Identity to Not Registered and clear the S-CSCF name associated with the Public Identity. + +In case of ADMINISTRATIVE\_DEREGISTRATION, if SAR-Flags AVP includes a P-CSCF-Restoration-Indication, the HSS or combined HSS-UDM supporting the P-CSCF-Restoration-mechanism feature shall send a P-CSCF restoration indication to the serving nodes where the IMSI associated to the received Private Identity is registered, i.e. SGSN and/or MME, using S6a/S6d IDR/IDA or Gr ISD request/answer as described in TS 23.380 [19] clause 5.4, and SMF and/or AMF, using the Nudm\_UECM\_P-CSCF-RestorationNotification service operation as described in TS 23.380 [19] clause 5.8.4. + +The Result-Code shall be set to DIAMETER\_SUCCESS + +- If it indicates TIMEOUT\_DEREGISTRATION\_STORE\_SERVER\_NAME or USER\_DEREGISTRATION\_STORE\_SERVER\_NAME the HSS decides whether to keep the S-CSCF name associated to the Private User Identity stored or not for all the Public User Identities that the S-CSCF indicated in the request. If no Public User Identity is present in the request, the Private User Identity shall be present. +- If the HSS decides to keep the S-CSCF name stored the HSS shall keep the S-CSCF name stored for all the Public User Identities associated to the Private User Identity. The Result-Code shall be set to DIAMETER\_SUCCESS. + +The HSS shall check if each Public User Identity in the request is currently registered with one or more Private User Identities. If the request did not contain Public User Identities the HSS shall check if each Public User Identity associated with the Private User Identity in the request is currently registered with one or more Private User Identities. For each Public User Identity;- + +- If only one Private User Identity associated with the Public User Identity is currently registered with the Public User Identity, the HSS shall set the registration state of the Public User Identity to Unregistered and clear any S-CSCF Restoration Information associated with the Public User Identity +- If more than one Private User Identity that shares that Public User Identity is currently registered with the Public User Identity the HSS shall keep the registration state of the Public User Identity as Registered. The HSS shall remove any S-CSCF Restoration Information associated to the registration of this Public User Identity with the Private User Identity in the request. +- If the HSS decides not to keep the S-CSCF name the Experimental-Result shall be set to DIAMETER\_SUCCESS\_SERVER\_NAME\_NOT\_STORED. + +The HSS shall check if each Public User Identity in the request is currently registered with one or more Private User Identities. If the request did not contain Public User Identities the HSS shall check if each Public User Identity associated with the Private User Identity in the request is currently registered with one or more Private User Identities. For each Public User Identity;- + +- If only one Private User Identity associated with the Public User Identity is currently registered with the Public User Identity, the HSS shall set the registration state of the Public User Identity to Not Registered and clear the S-CSCF name associated with Public User Identity. +- If more than one Private User Identity that shares that Public User Identity is currently registered with the Public User Identity the HSS shall keep the registration state of the Public User Identity as Registered. +- If it indicates NO\_ASSIGNMENT, the HSS checks whether the Public Identity is assigned for the S-CSCF requesting the data. If the requesting S-CSCF is not the same as the assigned S-CSCF and the S-CSCF reassignment pending flag is not set, the Result-Code shall be set to DIAMETER\_UNABLE\_TO\_COMPLY, otherwise the HSS shall download the relevant user information and the Result-Code shall be set to DIAMETER\_SUCCESS. If relevant S-CSCF Restoration Information is stored in the HSS and IMS Restoration Procedures are supported, it shall be added to the answer message. If there is S-CSCF Restoration Information associated with several Private User Identities, the HSS shall include all the S-CSCF Restoration Information groups in the response. If there are multiple Private User Identities, which belong to the served IMS subscription the Associated-Identities AVP should be added to the answer message and it shall contain all Private User Identities associated to the IMS subscription. + +NOTE 6: the check of the S-CSCF reassignment pending flag is needed since an S-CSCF supporting restoration procedures can receive a user initiated de-registration for a Public Identity for which it does not have any registration data (see TS 23.380 [19]). In such case, the S-CSCF indicates NO\_ASSIGNMENT in Server-Assignment-Type to retrieve any possible restoration information from the HSS. + +- If it indicates AUTHENTICATION\_FAILURE (e.g. there is a mismatch in IP-address secure binding information) or AUTHENTICATION\_TIMEOUT (e.g. no response to Digest challenge), the HSS shall keep the registration state of the Public User Identity. The HSS shall check the registration state for the Public User Identity in the request and only if the registration state of the Public User Identity is Not Registered, the HSS shall clear the S-CSCF name associated with the Public User Identity. + +If the Public User Identity's authentication pending flag which is specific for the Private User Identity is set, the HSS shall clear it. The Result-Code shall be set to DIAMETER\_SUCCESS. + +If the HSS cannot fulfil the received request, e.g. due to database error, it shall set the Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. The HSS shall not modify any registration state nor download any Public Identity information to the S-CSCF. + +See chapter 8.1.2 and 8.1.3 for the description of the handling of the error situations: reception of an S-CSCF name different from the one stored in the HSS and reception of a Server-Assignment-Type value not compatible with the registration state of the Public Identity. + +### 6.1.3 Network initiated de-registration by the HSS, administrative + +In case of network initiated de-registration of by the HSS, the HSS change the state of the Public Identities to Not Registered and send a notification to the S-CSCF indicating the identities that shall be de-registered. The procedure is invoked by the HSS, corresponds to the functional level operation Cx-Deregister (see TS 23.228 [1]). + +This procedure is mapped to the commands Registration-Termination-Request/Answer in the Diameter application specified in TS 29.229 [5]. Tables 6.1.3.1 and 6.1.3.2 describe the involved information elements. + +**Table 6.1.3.1: Network Initiated Deregistration by HSS request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------------------------------|-------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Public User Identity / Public Service Identity (See 7.2 and 7.2a) | Public-Identity | C | It contains the list of Public Identities that are de-registered, in the form of SIP URL or TEL URL.
Public-Identity AVP shall be present if the de-registration reason code is NEW_SERVER_ASSIGNED. It may be present with the other reason codes. | +| Private User Identity / Private Service Identity (See 7.3 and 7.3a) | User-Name | M | It contains the Private Identity in the form of a NAI. The HSS shall always send a Private Identity that is known to the S-CSCF based on an earlier SAR/SAA procedure. | +| Reason for de-registration (See 7.11) | Deregistration-Reason | M | The HSS shall send to the S-CSCF a reason for the de-registration. The de-registration reason is composed of two parts: one textual message (if available) that is intended to be forwarded to the user that is de-registered, and one reason code (see 3GPP TS 29.229 [5]) that determines the behaviour of the S-CSCF | +| Routing Information (See 7.13) | Destination-Host | M | It contains the name of the S-CSCF which originated the last update of the name of the multimedia server stored in the HSS for a given IMS Subscription. The address of the S-CSCF is the same as the Origin-Host AVP in the message sent from the S-CSCF. | +| Associated Private Identities | Associated-Identities | O | This AVP contains Private Identities, which belong to the same IMS subscription as the Private Identity in the User-Name AVP and should be de-registered together with that one.
If the IMS subscription contains only a single Private Identity, this AVP shall not be present. | +| RTR Flags (See 7.30) | RTR-Flags | O | This information element contains a bit mask.
See 7.30 for the meaning of the bits. | + +**Table 6.1.3.2: Network Initiated Deregistration by HSS response** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------------|--------------------------------------|------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result
(See 7.6) | Result-Code /
Experimental-Result | M | This information element indicates the result of de-registration. Result-Code AVP shall be used for errors defined in the Diameter base protocol (see IETF RFC 6733 [31]). Experimental-Result AVP shall be used for Cx/Dx errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| Associated Private Identities | Associated-Identities | C | This AVP shall be present if the S-CSCF de-registered more than one Private Identity with the request. It contains all Private Identities that have been deregistered together with the one in the User-Name AVP of the request. | +| Identities with Emergency Registration
(See 7.25) | Identity-with-Emergency-Registration | C | This information element indicates a list of pairs of private and public user identities which have not been de-registered due to emergency registration. | + +#### 6.1.3.1 Detailed behaviour + +The HSS shall de-register the affected identities and invoke this procedure to inform the S-CSCF. The S-CSCF shall remove all the information stored in the S-CSCF for the affected identities. + +The HSS may de-register: + +- One Public Identity or a list of Public Identities. HSS may include all Public User Identities associated with the User-Name AVP to the request. This option is applicable with all reason codes. +- One or more Private Identities of the IMS Subscription with all associated Public Identities. No Public-Identity AVPs shall be present in this case. This option is applicable with reason codes PERMANENT\_TERMINATION, SERVER\_CHANGE, and REMOVE\_S-CSCF. +- All Public Service Identities that match a Wildcarded Public Service Identity. In this case the HSS may send one of the Public Service Identities that was received in the Server Assignment Request for that Wildcarded Public Service Identity and the associated Private Service Identity. +- A Wildcarded Public User Identity. In this case the HSS shall send a distinct Public User Identity that belongs to the same implicit registration set as the Wildcarded Public User Identity and the associated Private User Identity. + +The HSS shall send in the Deregistration-Reason AVP the reason for the de-registration, composed by a textual message (if available) aimed for the user and a reason code that determines the action the S-CSCF has to perform. The possible reason codes are: + +- PERMANENT\_TERMINATION: The HSS indicates to the S-CSCF that the S-CSCF will no longer be assigned to the Public Identity and associated implicitly registered/unregistered Public Identities (if any) for the Private Identity(ies) indicated in the request (e.g. due to an IMS subscription cancellation, or modification, or a removal of IP-address secure binding information when GIBA is used). This reason also indicates that no other S-CSCF can be assigned. + +The HSS shall check the registration state of the Public Identities. If no Public Identities are involved, the HSS shall check the registration state of the Public Identities associated with the Private User Identity identified. For each Public Identity: + +- If the registration state of the Public Identity is Registered, the HSS shall check if the Public User Identity is currently registered with one or more Private User Identities. + - If the Public User Identity is currently registered with only one Private User Identity, the HSS shall check whether the Public User Identity is included in the information element Identities with Emergency Registrations returned by S-CSCF in the response. + - If included, the HSS shall keep the S-CSCF name associated with the Public User Identity and set the registration state of the Public User Identity to Unregistered. + +- If not included, the HSS shall clear the S-CSCF name associated with the Public User Identity, and set the registration state of the Public User Identity to Not Registered. The S-CSCF initiates the de-registration of the Public User Identity unless it is emergency registered. +- If the Public User Identity is currently registered with more than one Private User Identity, the HSS shall keep the registration state of the Public User Identity as Registered and retain the S-CSCF name associated with the Public User Identity. The S-CSCF initiates the de-registration of the Public User Identity unless it is emergency registered. +- If the registration state of the Public Identity is Unregistered, the HSS shall check whether this Public User Identity is included in the information element Identities with Emergency Registrations returned by S-CSCF in the response. + - If included, the HSS shall keep the S-CSCF name associated with the Public User Identity. + - If not included, the HSS shall set the registration state of the Public Identity to Not Registered and clear the S-CSCF name associated with the Public Identity. +- NEW\_SERVER\_ASSIGNED: The HSS indicates to the S-CSCF that a new S-CSCF has been allocated to the IMS Subscription e.g. because the previous assigned S-CSCF was unavailable during a registration procedure. The S-CSCF shall remove all information for all of the Public Identities indicated in the request. +- SERVER\_CHANGE: The HSS indicates to the S-CSCF that the de-registration is requested to force the selection of new S-CSCF to assign to the IMS Subscription (e.g. when the S-CSCF capabilities are changed in the HSS or when the S-CSCF indicates that it has not enough memory for the updated User Profile). The HSS shall set the registration state to "Not Registered" and clear the S-CSCF name for all of the Public Identities affected by the request. If the S-CSCF does not indicate in the response all the Private Identities that were in the request, the HSS shall repeat this request for each of the remaining Private Identities in the IMS Subscription that are known to the S-CSCF. The S-CSCF should start the network initiated de-registration towards the user, i.e. all registrations within the IMS Subscription are de-registered and the user is asked to re-register to all existing registrations. +- REMOVE\_S-CSCF: The HSS indicates to the S-CSCF that the S-CSCF will no longer be assigned to an unregistered Public Identity(ies) (i.e. registered as a consequence of an originating or terminating request or there is a S-CSCF keeping the user profile stored) for a given IMS Subscription. + +The HSS shall check if an emergency registration exists in the S-CSCF, checking for each Public Identity contained in the request whether it is present in the information element Identities with Emergency Registrations returned by S-CSCF. + +- If an emergency registration does not exist in S-CSCF, for each Public Identity contained within the request, the HSS shall set the registration state of the Public Identity to Not Registered and clear the S-CSCF name associated with the Public Identity. The S-CSCF shall remove all information related to the Public User Identity contained within the request. +- If an emergency registration exists in S-CSCF for one or more Public User Identities contained in the request, the S-CSCF should include the corresponding Private Identity / Public User Identity pairs in the information element Identities with Emergency Registrations in the answer. The HSS, when receiving such an answer, shall not change the registration state of the Public User Identities present in the information element Identities with Emergency Registrations and shall keep unchanged the S-CSCF name associated with these Public User Identities. + +Public Identities which are emergency registered in the S-CSCF shall not be de-registered when a Cx-Deregistration request with a -reason code of PERMANENT\_TERMINATION or REMOVE\_S-CSCF is received from the HSS. In this case + +- if all to be de-registered identities are emergency registered, a Result-Code set to DIAMETER\_UNABLE\_TO\_COMPLY and a list of Private / Public Identity pairs which are emergency registered shall be returned to the HSS +- if a proper subset of the to be de-registered identities are emergency registered, a Result-Code of DIAMETER\_LIMITED\_SUCCESS and a list of Private Identity / Public Identity pairs which are emergency registered shall be returned to the HSS. + +NOTE 1: If the Public Identity that is emergency registered has normal registration as well, then for the normal registration the S-CSCF will perform the detailed de-registration procedures towards the UE for each reason code as described in TS 24.229 [8]. + +NOTE 2: It is assumed that Public Identities which are implicitly registered along with an emergency registration are also emergency registered. + +The detailed de-registration procedures performed by the S-CSCF are described in TS 24.229 [8]. + +### 6.1.4 User location query + +This procedure is used between the I-CSCF and the HSS to obtain the name of the S-CSCF assigned to a Public Identity, or the name of the AS hosting a PSI for direct routing. The procedure is invoked by the I-CSCF, is performed per Public Identity, and corresponds to the functional level operation Cx-Location-Query (see TS 23.228 [1]). + +This procedure is mapped to the commands Location Info Request/Answer in the Diameter application specified in TS 29.229 [5]. Tables 6.1.4.1 and 6.1.4.2 detail the involved information elements. + +**Table 6.1.4.1: User Location query** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|-------------------------------------------------------------------|-------------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Public User Identity / Public Service Identity (See 7.2 and 7.2a) | Public-Identity | M | Public Identity | +| Routing information (See 7.13) | Destination-Host, Destination-Realm | C | If the I-CSCF knows HSS name Destination-Host AVP shall be present in the command. Otherwise, only Destination-Realm AVP shall be present and the command shall be routed to the next Diameter node, e.g. SLF, based on the Diameter routing table in the I-CSCF. | +| Originating Request (See 7.18) | Originating-Request | O | It indicates that the request is related to an originating SIP message. | +| Type of Authorization (See 7.14) | User-Authorization-Type | C | This information element shall be present and set to REGISTRATION_AND_CAPABILITIES by the I-CSCF if IMS Restoration Procedures are supported and the S-CSCF currently assigned to the Public User Identity in the HSS cannot be contacted. | +| Session Priority (See 7.24) | Session-Priority | O | This information element, if present, shall indicate the session's priority to the HSS. | + +**Table 6.1.4.2: User Location response** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|--------------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result
(See 7.6) | Result-Code /
Experimental-Result | M | Result of the operation.
Result-Code AVP shall be used for errors defined in the Diameter base protocol (see IETF RFC 6733 [31]).
Experimental-Result AVP shall be used for Cx/Dx errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | +| S-CSCF Name / AS name
(See 7.4 and 7.4a) | Server-Name | C | Name of the assigned S-CSCF for basic IMS routing or the name of the AS for direct routing. | +| S-CSCF capabilities
(See 7.5) | Server-Capabilities | O | It contains the information to help the I-CSCF in the selection of the S-CSCF. | +| Wildcarded Public Identity
(See 7.2b) | Wildcarded-Public-Identity | O | If the requests refers to a Wildcarded PSI or Wildcarded Public User Identity (the Public Identity in the request matches a Wildcarded PSI or Wildcarded Public User Identity in the HSS), the HSS shall include the corresponding Wildcarded Public Identity in this information element.
The matching of distinct Public Identities takes precedence over the matching of wildcarded public identities. | +| LIA Flags
(See 7.27) | LIA-Flags | O | This information element contains a bit mask.
See 7.27 for the meaning of the bits. | + +#### 6.1.4.1 Detailed behaviour + +The HSS may prioritise the received request message according to priority level received within the Session-Priority AVP. + +NOTE 1: Refer to Annex J for HSS procedures associated with the handling of both the Session-Priority AVP and DRMP AVP received in the request message. + +The HSS shall, in the following order (if an error occurs in any of the steps the HSS shall stop processing and return the corresponding error code, see TS 29.229 [5]): + +The HSS shall, in the following order (if an error occurs in any of the steps the HSS shall stop processing and return the corresponding error code, see TS 29.229 [5]): + +1. Check that the Public Identity is known. If not the Experimental-Result-Code shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN. +2. Check the type of the Public Identity contained in the request: + - If this is a Public User Identity, continue to step 2a. + - If this is a Public Service Identity: + - Check if the PSI Activation State for that identity is active. If not, then the response shall contain Experimental-Result-Code set to DIAMETER\_ERROR\_USER\_UNKNOWN. + - Check if the name of the AS hosting the Public Service Identity is stored in the HSS and that the request does not contain the Originating-Request AVP. + - If this is the case, if IMS Restoration Procedures are supported, the HSS shall check if User-Authorization-Type was received in the request, and if the value is REGISTRATION\_AND\_CAPABILITIES: + - If it is, the HSS shall reject the request with Result-Code set to DIAMETER\_UNABLE\_TO\_COMPLY. + - Otherwise, the HSS shall return the AS name and the Result-Code AVP shall be set to DIAMETER\_SUCCESS. HSS may set PSI Direct Routing Indication bit in LIA-Flags AVP, then I-CSCF shall not perform IMS Restoration Procedures (see chapter 4.3.3 in TS 23.380 [19]). + +- Otherwise, continue to step 2a. +- 2a. If IMS Restoration procedures are supported, the HSS shall check if User-Authorization-Type was received in the request, and if the value is REGISTRATION\_AND\_CAPABILITIES: +- If it is, then the HSS may return the Server-Capabilities AVP. The returned capabilities, if any, shall satisfy all the requirements of all the service profiles associated with the IMS Subscription. If Server-Capabilities AVP is absent, it indicates to the I-CSCF that it can select any available S-CSCF. Also the HSS shall set the S-CSCF reassignment pending flag and allow overwriting of the S-CSCF name in the next SAR request, which enables the I-CSCF to select an S-CSCF. The Result-Code shall be set to DIAMETER\_SUCCESS. The HSS shall not return any S-CSCF name. Stop processing. + - Otherwise, continue to step 3. +3. Check the state of the Public Identity received in the request, and where necessary, check if the Public Identity has terminating services related to the unregistered state. +- If it is registered, the HSS shall return the stored S-CSCF name. The Server-Name AVP shall contain the SIP URI of the server. The Server-Capabilities AVP shall not be present. The Result-Code AVP shall be set to DIAMETER\_SUCCESS. + - If it is unregistered (i.e. registered as a consequence of an originating or terminating request or there is a S-CSCF keeping the user profile stored) the HSS shall return the S-CSCF name assigned for that Public Identity. The Server-Name AVP shall contain the SIP URI of the server. The Server-Capabilities AVP shall not be present. The Result-Code shall be set to DIAMETER\_SUCCESS. + - If it is not registered, but either it has terminating services related to unregistered state or the request contains the Originating-Request AVP, the HSS shall check if there is at least one Public Identity within the IMS Subscription with an S-CSCF name assigned: + - If this is the case the HSS shall return the S-CSCF name assigned for that Public Identity. The Server-Name AVP shall contain the SIP URI of the server. The Server-Capabilities AVP shall not be present. The Result-Code shall be set to DIAMETER\_SUCCESS. + - If there is not any S-CSCF name assigned to a Public Identity within the IMS Subscription, the HSS may return information about the required S-CSCF capabilities, which enables the I-CSCF to select an S-CSCF. The Server-Capabilities AVP may be present. The HSS shall send the same server capability set that is sent in the user registration status response during the registration. If Server-Capabilities AVP is not present, the I-CSCF shall understand that any S-CSCF is suitable for the IMS Subscription. The Server-Name AVP shall not be present. The Experimental-Result-Code shall be set to DIAMETER\_UNREGISTERED\_SERVICE. + - If it is not registered or unregistered, and the Public Identity has no terminating services related to the unregistered state and the request does not contain the Originating-Request AVP, the response shall contain Experimental-Result-Code set to DIAMETER\_ERROR\_IDENTITY\_NOT\_REGISTERED. + +If the HSS cannot fulfil the received request, e.g. due to database error, it shall set Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. No S-CSCF name or S-CSCF capabilities shall be present in the response. + +## 6.2 User data handling procedures + +### 6.2.1 User Profile download + +As part of the registration procedure ( TS 23.228 [1]) S-CSCF obtains user data and service related information by means of the Cx-Put Resp operation (see 6.1.2). + +### 6.2.2 HSS initiated update of User Information + +This procedure is initiated by the HSS to update at least one of the following user information in S-CSCF: + +- User profile information and/or + +- Charging information and/or +- Allowed WAF and/or WWSF Identities and/or +- SIP Digest authentication information in the S-CSCF. + +This procedure shall not be used by the HSS to add, delete, or update the value of the IMSI. + +This procedure corresponds to the functional level operation Cx-Update\_Subscr\_Data (see TS 23.228 [1]). + +This procedure is mapped to the commands Push-Profile-Request/Answer in the Diameter application specified in TS 29.229 [5]. Tables 6.2.2.1 and 6.2.2.2 describe the involved information elements. + +**Table 6.2.2.1: User Profile Update request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------------------------------|-----------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Private User Identity / Private Service Identity (See 7.3 and 7.3a) | User-Name | M | Private Identity.
The HSS shall always send a Private Identity that is known to the S-CSCF based on an earlier SAR/SAA procedure. | +| User profile (See 7.7) | User-Data | C | Updated user profile (see clauses 6.5.2.1 and 6.6.1), with the format defined in chapter 7.7.
It shall be present if the user profile is changed in the HSS. If the User-Data AVP is not present, the SIP-Auth-Data-Item or Charging-Information AVP or Allowed-WAF-WWSF-Identities AVP shall be present. | +| Authentication Data (See 7.9) | SIP-Auth-Data-Item | C | SIP Digest authentication information.
It shall be present if the used authentication scheme is SIP Digest and when password change has occurred in the HSS.
If the SIP-Auth-Data-Item AVP is not present, the Charging-Information or User-Data AVP or Allowed-WAF-WWSF-Identities AVP shall be present.
See Table 6.3.6 for the contents of this information element. | +| Charging Information (See 7.12) | Charging-Information | C | Addresses of the charging functions.
It shall be present if the charging addresses are changed in the HSS. If the Charging-Information AVP is not present, the SIP-Auth-Data-Item or User-Data AVP or Allowed-WAF-WWSF-Identities AVP shall be present.
When this parameter is included, either the Primary-Charging-Collection-Function-Name AVP or the Primary-Event-Charging-Function-Name AVP shall be included. All other charging information shall be included if it is available. | +| Routing Information (See 7.13) | Destination-Host | M | It contains the name of the S-CSCF which originated the last update of the name of the multimedia server stored in the HSS for a given IMS Subscription. The address of the S-CSCF is the same as the Origin-Host AVP in the message sent from the S-CSCF. | +| Allowed WAF and/or WWSF Identities (See 7.29) | Allowed-WAF-WWSF-Identities | C | Addresses of the WAFs and/or WWSFs the subscription is allowing to use.
It shall be present if the allowed WAF and/or WWSF identities are changed in the HSS. | + +**Table 6.2.2.2: User Profile Update response** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------|-----------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result (See 7.6) | Result-Code / Experimental-Result | M | This information element indicates the result of the update of User Profile in the S-CSCF.
Result-Code AVP shall be used for errors defined in the Diameter base protocol (see IETF RFC 6733 [31]).
Experimental-Result AVP shall be used for Cx/Dx errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | + +#### 6.2.2.1 Detailed behaviour + +The HSS shall make use of this procedure to update the relevant user information to the S-CSCF. See chapters 6.5.2.1 and 6.6.1 for the rules of user profile updating. See chapter 6.5.2.3 for the rules of Charging Information update. See chapter 6.5.2.4 for the rules of SIP Digest Authentication Data update. See chapter 6.5.2.5 for the rules of Allowed WAF and/or WWSF Identities update. + +If there are multiple registered Private User Identities associated to the Public User Identity in the HSS, the HSS shall send only single request and select arbitrarily one of the Private User Identities and put it into the request. For updates of the profile of a Wildcarded Public Identity, the HSS shall send only one single request. That request shall contain the Wildcarded Public Identity. + +The SIP-Auth-Data-Item AVP and/or Charging-Information AVP and/or the User-Data AVP shall be present in the request. + +If the User-Data AVP is present in the request, the S-CSCF shall overwrite, for the Public Identities indicated in the User profile included in the request, current information with the information received from the HSS, except in the error situations detailed in table 6.2.2.1.1. + +If the Charging-Information AVP is present in the request, the S-CSCF shall replace the existing charging information with the information received from the HSS. + +The SIP-Auth-Data-Item AVP shall be present if the command is sent in order to update SIP Digest authentication information due to a password change. + +If the S-CSCF receives data that it can not recognise, unsupported user data in a part of the request where it may not be ignored or more data than it can accept, it shall return the corresponding error code to the HSS as indicated in table 6.2.2.1.1. The S-CSCF shall not overwrite the data that it already has to give service to the IMS Subscription. The HSS shall initiate a network-initiated de-registration procedure towards the S-CSCF with Deregistration-Reason set to SERVER\_CHANGE, which will trigger the assignment of a new S-CSCF. + +If the HSS receives DIAMETER\_ERROR\_USER\_UNKNOWN from the S-CSCF in the Push-Profile-Answer, then the HSS shall re-send the request using another arbitrarily selected registered Private Identity (if any). If restoration procedures are not supported, the HSS shall set the unknown Private User Identity's registration status to "not registered"; this will allow the synchronization of the registration status in HSS and S-CSCF. + +NOTE: If restoration procedures are supported, restoration procedures will ensure synchronization of the registration status in HSS and S-CSCF, i.e. the S-CSCF can either immediately retrieve the S-CSCF restoration information for the registered Public User Identity (sending SAR with Server Assignment Type set to NO\_ASSIGNMENT), or wait for reception of a SIP request. + +Table 6.2.2.1.1 details the valid result codes that the S-CSCF can return in the response. + +**Table 6.2.2.1.1: User information update response valid result codes** + +| Result-Code AVP value | Condition | +|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| DIAMETER_SUCCESS | The request succeeded. | +| DIAMETER_ERROR_NOT_SUPPORTED_USER_DATA | The request failed. The S-CSCF informs the HSS that the received user information contained information, which was not recognised or supported by the S-CSCF due to unsupported S-CSCF capabilities. | +| DIAMETER_ERROR_USER_UNKNOWN | The request failed because the Private Identity is not found in S-CSCF. | +| DIAMETER_ERROR_TOO_MUCH_DATA | The request failed. The S-CSCF informs to the HSS that it tried to push too much data into the S-CSCF. | +| DIAMETER_UNABLE_TO_COMPLY | The request failed. | + +## 6.3 Authentication procedures + +This procedure is used between the S-CSCF and the HSS to exchange information to support the authentication between the end user and the home IMS network. The procedure is invoked by the S-CSCF, corresponds to the combination of the operations Cx-AV-Req and Cx-AV-Req-Resp (see TS 33.203 [3]) and is used: + +- To retrieve authentication vectors from the HSS. +- To resolve synchronization failures between the sequence numbers in the UE and the HSS for authentication schemes that support this capability (e.g. IMS-AKA). +- To promote the result of the NASS-level authentication to the IMS level. +- To retrieve the IP-address secure binding information for GPRS-IMS-Bundled Authentication (GIBA) from the HSS. + +This procedure is mapped to the commands Multimedia-Auth-Request/Answer in the Diameter application specified in TS 29.229 [5]. Tables 6.3.1 through 6.3.7 detail the involved information elements. + +**Table 6.3.1: Authentication Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|----------------------------------------|-------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Public User Identity (See 7.2) | Public-Identity | M | This information element contains the Distinct Public User Identity of the user | +| Private User Identity (See 7.3) | User-Name | M | This information element contains the Private User Identity | +| Number Authentication Items (See 7.10) | SIP-Number-Auth-Items | M | This information element indicates the number of authentication vectors requested. Certain authentication schemes do not support more than one set of authentication vectors (e.g. SIP Digest, GIBA). | +| Authentication Data (See 7.9) | SIP-Auth-Data-Item | M | See Table 6.3.2 for the contents of this information element. | +| S-CSCF Name (See 7.4) | Server-Name | M | This information element contains the name (SIP URL) of the S-CSCF. | +| Routing Information (See 7.13) | Destination-Host | C | If the S-CSCF knows the HSS name this AVP shall be present. This information is available if the MAR belongs to an already existing registration, e.g. in case of the re-registration, where the HSS name is stored in the S-CSCF. The HSS name is obtained from the Origin-Host AVP, which is received from the HSS, e.g. included in the MAA command. This information may not be available if the command is sent in case of the initial registration. In this case the Destination-Host AVP is not present and the command is routed to the next Diameter node, e.g. SLF, based on the Diameter routing table in the client. | + +**Table 6.3.2: Authentication Data content in Authentication Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------|----------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Authentication Scheme (See 7.9.2) | SIP-Authentication-Scheme | M | This information element indicates the authentication scheme. See 3GPP TS 29.229 [5] for a list of values | +| Authentication Context (See 7.9.7) | SIP-Authentication-Context | C | This information element shall contain authentication-related information relevant for performing the authentication. It shall be absent for IMS-AKA authentication schemes. | +| Authorization Information (See 7.9.4) | SIP-Authorization | C | This information element shall only be present for a request due to an IMS-AKA synchronization failure. If present, only IMS-AKA authentication schemes are allowed. | + +Table 6.3.3: Void + +Table 6.3.4: Authentication Request Response + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|----------------------------------------|-----------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Identity (See 7.2) | Public-Identity | C | Public User Identity. It shall be present when the result is DIAMETER_SUCCESS. | +| Private User Identity (See 7.3) | User-Name | C | Private User Identity. It shall be present when the result is DIAMETER_SUCCESS. | +| Number Authentication Items (See 7.10) | SIP-Number-Auth-Items | C | This information element indicates the number of authentication vectors delivered in the Authentication Data information element. It shall be present when the result is DIAMETER_SUCCESS. For SIP Digest, NASS Bundled authentication and GIBA this AVP shall be set to a value of 1. | +| Authentication Data (See 7.9) | SIP-Auth-Data-Item | C | If the SIP-Number-Auth-Items AVP is equal to zero or it is not present, then this information element shall not be present. See Table 6.3.5 for the contents of this information element. | +| Result (See 7.6) | Result-Code / Experimental-Result | M | This information element indicates the result of the operation. It shall be mapped to Result-Code AVP for errors defined in the Diameter base protocol (see IETF RFC 6733 [31]). It shall be mapped to Experimental-Result AVP for Cx/Dx errors. This information element is mapped to a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. | + +**Table 6.3.5: Authentication Data information element content in Authentication Request Response** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|-------------------------------------------|---------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Item Number
(See 7.9.1) | SIP-Item-Number | C | This information element shall only be present for IMS-AKA authentication schemes.
This information element shall be present when there are multiple occurrences of the Authentication Data information element in the Authentication Request Response, and the order in which they should be processed is significant.
In this scenario, Authentication Data information elements with a low Item Number information element value should be processed before Authentication Data information elements with a high Item Number information element value. | +| Authentication Scheme
(See 7.9.2) | SIP-Authentication-Scheme | M | This information element indicates the authentication scheme. | +| Authentication Information
(See 7.9.3) | SIP-Authenticate | C | This information element shall only be present for IMS-AKA authentication schemes. | +| Authorization Information
(See 7.9.4) | SIP-Authorization | C | This information element shall only be present for IMS-AKA authentication schemes. | +| Confidentiality Key
(See 7.9.5) | Confidentiality-Key | C | This information element shall be present for IMS AKA authentication schemes.
It shall contain the confidentiality key. | +| Integrity Key
(See 7.9.6) | Integrity-Key | C | This information element shall only be present for IMS-AKA authentication schemes.
This information element shall contain the integrity key. | +| Digest Authenticate
(See 7.9.8) | SIP-Digest-Authenticate | C | This information element shall only be present for SIP Digest authentication scheme.
See Table 6.3.7 for contents of this grouped AVP. | +| Line Identifier
(See 7.9.9) | Line-Identifier | C | This information element shall only be present for NASS Bundled authentication scheme.
This information element contains fixed broadband access line identifier associated to the user. This information element can be repeated. | +| Framed IP Address
(See 7.9.10) | Framed-IP-Address | C | This information element shall only be present for GPRS-IMS-Bundled authentication scheme.
If the IP Address of the User is an IPv4 address, this AVP shall be included. | +| Framed IPv6 Prefix
(See 7.9.11) | Framed-IPv6-Prefix | C | This information element shall only be present for GPRS-IMS-Bundled authentication scheme.
If the IP Address of the User is an IPv6 address, this AVP shall be included. | +| Framed Interface Id
(See 7.9.12) | Framed-Interface-Id | C | This information element shall only be present for GPRS-IMS-Bundled authentication scheme.
If and only if the IP Address of the User is an IPv6 address and the Framed-IPv6-Prefix AVP alone is not unique for the user this AVP shall be included. | + +**Table 6.3.6: Void** + +**Table 6.3.7: Digest Authenticate information element content – Response for SIP Digest** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|--------------------------------|-------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Digest Realm (See 7.9.8.1) | Digest-Realm | M | This information element corresponds to the Realm parameter as defined in IETF RFC 2617 [16]. | +| Digest Algorithm (See 7.9.8.3) | Digest-Algorithm | O | This information element contains the algorithm as defined in IETF RFC 2617 [16].
If this information element is not present, then "MD5" is assumed.
If this information element is present it shall contain "MD5". | +| Digest QoP (See 7.9.8.4) | Digest-QoP | M | This information element contains the QoP as defined in IETF RFC 2617 [16]. This information element shall be set to a value of "auth" by the HSS. | +| Digest HA1 (See 7.9.8.5) | Digest-HA1 | M | This information element contains the H(A1) as defined in IETF RFC 2617 [16]. | + +**Table 6.3.8: Void****Table 6.3.9: Void** + +### 6.3.1 Detailed behaviour + +The HSS shall, in the following order (in case of an error in any of the steps the HSS shall stop processing and return the corresponding error code, see TS 29.229 [5]): + +1. Check that the Private User Identity and the Public User Identity exist in the HSS. If not Experimental-Result-Code shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN. +2. Check that the Public User Identity matches a distinct Public User Identity in the HSS. If it doesn't, the Experimental-Result-Code shall be set to DIAMETER\_ERROR\_USER\_UNKNOWN. +3. Check whether the Private and Public User Identities in the request are associated in the HSS. If not Experimental-Result-Code shall be set to DIAMETER\_ERROR\_IDENTITIES\_DONT\_MATCH. +4. Check the authentication scheme indicated in the request, and + - if it is "Unknown", check the authentication scheme stored in HSS. If it is neither NASS-Bundled authentication nor SIP Digest authentication, Experimental-Result-Code shall be set to DIAMETER\_ERROR\_AUTH\_SCHEME\_NOT\_SUPPORTED. + - if not, check that the authentication scheme indicated in the request is supported. If not Experimental-Result-Code shall be set to DIAMETER\_ERROR\_AUTH\_SCHEME\_NOT\_SUPPORTED. + +This step is only applicable for IMS-AKA authentication. If the request indicates there is a synchronization failure, the HSS shall compare the S-CSCF name received in the request to the S-CSCF name stored in the HSS: + +- If they are identical the HSS shall process AUTS as described in TS 33.203 [3] and return the requested authentication information. The Result-Code shall be set to DIAMETER\_SUCCESS. +5. Check the registration status of the Public User Identity received in the request: + - If it is registered, the HSS shall compare the S-CSCF name received in the request to the S-CSCF name stored in the HSS: + - If they are different, the HSS shall overwrite the S-CSCF name. If IMS restoration procedures are supported and the S-CSCF reassignment pending flag is set, the HSS shall reset the flag and keep the S-CSCF restoration information associated with the Public User Identity. The HSS shall download SIP-Auth-Data-Item stored up to a maximum specified in SIP-Number-Auth-Items received in the command Multimedia-Auth-Request. If authentication scheme is neither NASS-Bundled nor GIBA, the HSS shall set the Public User Identity's authentication pending flag which is specific to the Private User Identity received in the request. The Result-Code shall be set to DIAMETER\_SUCCESS. + +- If they are identical, the HSS shall download SIP-Auth-Data-Item stored up to a maximum specified in SIP-Number-Auth-Items received in the command Multimedia-Auth-Request. The Result-Code shall be set to DIAMETER\_SUCCESS. +- If it is unregistered (i.e. registered as a consequence of an originating or terminating request or there is an S-CSCF keeping the user profile stored) or not registered, the HSS shall compare the S-CSCF name received in the request to the S-CSCF name stored in the HSS: + - If they are different or if there is no S-CSCF name stored in the HSS for any Public User Identity of the IMS subscription, the HSS shall store the S-CSCF name. The HSS shall download SIP-Auth-Data-Item stored up to a maximum specified in SIP-Number-Auth-Items received in the command Multimedia-Auth-Request. If authentication scheme is neither NASS-Bundled nor GIBA, the HSS shall set the Public User Identity's authentication pending flag which is specific to the Private User Identity which was received in the request. The Result-Code shall be set to DIAMETER\_SUCCESS. + - If they are identical, the HSS shall download SIP-Auth-Data-Item stored up to a maximum specified in SIP-Number-Auth-Items received in the command Multimedia-Auth-Request. If authentication scheme is neither NASS-Bundled nor GIBA, the HSS shall set the Public User Identity's authentication pending flag which is specific to the Private User Identity that was received in the request. The Result-Code shall be set to DIAMETER\_SUCCESS. + +Exceptions to the cases specified here shall be treated by HSS as error situations, the Result-Code shall be set to DIAMETER\_UNABLE\_TO\_COMPLY. No authentication information shall be returned. + +## 6.4 User identity to HSS resolution + +The User identity to HSS resolution mechanism enables the I-CSCF and the S-CSCF to find the identity of the HSS, that holds the subscriber data for a given Public Identity when multiple and separately addressable HSSs have been deployed by the network operator. The resolution mechanism is not required in networks that utilise a single HSS. An example for a single HSS solution is server farm architecture. + +The resolution mechanism described in TS 23.228 [1] shall use a Subscription Locator Function (SLF) or a Diameter Proxy Agent. + +The I-CSCF and the S-CSCF accesses the SLF via the Dx interface. The Dx interface shall always be used in conjunction with the Cx interface. The Dx interface shall be based on the Diameter base protocol as specified in IETF RFC 6733 [31]. The SLF functionality shall use the routing mechanism provided by an enhanced Diameter redirect agent. + +The SLF or the Diameter Proxy Agent shall be able to determine the HSS identity. + +To get the HSS identity the I-CSCF and the S-CSCF shall send the Cx request normally destined to the HSS to a pre-configured Diameter address/name. + +- If this Cx Request is received by an SLF (acting as a Diameter redirect agent), the SLF shall determine the HSS identity and sends to the I-CSCF or S-CSCF a notification of redirection towards the HSS identity, in response to the Cx request. Multiple HSS identities may be included in the response, as specified in IETF RFC 6733 [31]. In such a case, the I-CSCF or the S-CSCF shall send the Cx Request to the first HSS identity in the ordered list received in the Cx Response from the SLF. If the I-CSCF or S-CSCF does not receive a successful response to the Cx Request, the I-CSCF or S-CSCF shall send a Cx Request to the next HSS identity in the ordered list. This procedure shall be repeated until a successful response from an HSS is received. +- If this Cx Request is received by the Diameter Proxy Agent, the Diameter Proxy Agent shall determine the HSS identity based on the provided user identity and - if the Diameter load control mechanism is supported (see IETF RFC 8583 [29]) - optionally also based on previously received load values from Load AVPs of type HOST. The Diameter Proxy Agent shall then forward the Cx request directly to the determined HSS. The I-CSCF and S-CSCF shall determine the HSS identity from the response to the Cx request received from the HSS. + +While the I-CSCF is stateless, the S-CSCF shall store the HSS identity/name/Realm, as specified in TS 23.228 [1] and shall use it in further Cx requests associated to the same IMS Public Identity. + +In networks where the use of the user identity to HSS resolution mechanism is required, each I-CSCF and S-CSCF shall be configured with the address/name of the SLF or the Diameter Proxy Agent to enable use of these resolution mechanisms. + +## 6.5 Implicit registration + +Implicit registration is the mechanism by which a user is allowed to register simultaneously more than one of his/her Public User Identities. The HSS knows the identities that are to be implicitly registered when it receives the indication of the registration of an individual identity. + +What follows is an extension of the affected basic procedures. + +### 6.5.1 S-CSCF initiated procedures + +The result of the S-CSCF initiated procedures affects all the Public User Identities that are configured in the HSS to be in the same implicitly registered Public User Identity set with the targeted individual Public User Identity. Where the S-CSCF initiated procedure affects the Registration state of the targeted Public User Identity, the Registration states of the Public User Identities in the associated implicitly registered Public User Identity set are affected in the same way. + +#### 6.5.1.1 Registration + +The notification of a registration of a Public User Identity implies the registration of the corresponding implicitly registered Public User Identity set. The user information downloaded in the response contains the Public User Identities of the implicitly registered Public User Identity set with the associated service profiles. This allows the S-CSCF to know which Public User Identities belong to the implicitly registered Public User Identity set. The S-CSCF shall take from the set of implicitly registered Public User Identities the first identity which is not barred, and use this as the default Public User Identity. The default Public User Identity shall be a distinct Public User Identity. + +#### 6.5.1.2 De-registration + +The de-registration of a Public User Identity implies the de-registration of the corresponding implicitly registered Public User Identity set, both in the HSS and in the S-CSCF. The S-CSCF shall include in the request a single Public User Identity to deregister all the Public User Identities that belong to the corresponding implicitly registered Public User Identity set. + +The de-registration of a Private User Identity implies the de-registration of all the corresponding Public User Identities, both in the HSS and in the S-CSCF. + +#### 6.5.1.3 Authentication + +Setting the authentication pending flag for a Public User Identity implies setting the authentication pending flag for each corresponding implicitly registered Public User Identity in the HSS. + +#### 6.5.1.4 Downloading the user profile + +If the S-CSCF requests to download a user profile from HSS, the user profile in the response shall contain the Public User Identities of the corresponding implicitly registered Public User Identity set with the associated service profiles. + +#### 6.5.1.5 Initiation of a session to a non-registered user + +The change of a Public User Identity to the Unregistered state due to the initiation of a session from/to a Public Identity that was in Not Registered state and the opposite change from Unregistered state to Not Registered state implies the same change for all the Public User Identities in the same Implicit Registration Set. + +### 6.5.2 HSS initiated procedures + +#### 6.5.2.1 Update of User Profile + +A request sent by the HSS to update the user profile shall include only the Public User Identities of the implicitly registered Public User Identity set, with the associated service profiles (even if not updated). If other Public User Identities not associated with the implicitly registered Public User Identity set are affected, they shall be downloaded in separate commands. + +This procedure shall be used by the HSS to add a newly provisioned or Not Registered Public User Identity or Identities to an existing implicitly registered Public User Identity set that is in the state Registered or Unregistered. The added Public User Identity gets the registration state of the set it is added to. + +The HSS shall use this procedure if a Public User Identity or Identities are removed from the implicitly registered Public User Identity set that is in a state Registered or Unregistered. In practise, this is done by sending a PPR for the set without the removed identities. The S-CSCF shall remove all information stored in the S-CSCF for the removed identities. + +The HSS shall not use this procedure if there is no Public User Identities left in the implicitly registered Public User Identity set after the removal. In that case HSS shall use the RTR command instead. + +The HSS shall not use this procedure to change the default Public User Identity of the implicitly registered Public User Identity set that is in a state Registered. In that case the HSS shall use the RTR command to de-register the Public User Identity set. + +When a change of the Reference Location Information occurs (e.g.. a change of authorization), the HSS may use a network initiated de-registration instead of this procedure, and may indicate to the S-CSCF that the de-registration is sent due to change of Reference Location Information. + +Moving of a Public User Identity or Identities from one implicitly registered Public User Identity set to another set shall be done in two steps: First the identity or identities are removed from the "old" set as described above, then the identity or identities are added to the "new" set as described above. + +#### 6.5.2.2 De-registration + +A request sent by the HSS to de-register any of the identities included in an implicitly registered Public User Identity set shall affect all the Public User Identities of the deregistered set. + +The de-registration of a Private User Identity implies the de-registration of all the corresponding Public User Identities, both in the HSS and in the S-CSCF. + +#### 6.5.2.3 Update of the Charging information + +A request sent by the HSS to update the charging information shall include the Private User Identity for whom the charging information changed. + +If corresponding Public Identity is registered or unregistered (i.e. registered as a consequence of an originating or terminating request or there is a S-CSCF keeping the user profile stored) and charging information is changed, the HSS should immediately push this information to the S-CSCF. + +#### 6.5.2.4 Update of the SIP Digest Authentication Data + +A request sent by the HSS to update the authentication data shall include the Private User Identity for whom the authentication data changed. + +If corresponding Public Identity is registered and authentication data is changed, the HSS should immediately push this information to the S-CSCF. + +If corresponding Public Identity is either not registered or unregistered (i.e. registered as a consequence of an originating or terminating request or there is a S-CSCF keeping the user profile stored), authentication pending flag is set and authentication data is changed, the HSS should immediately push this information to the S-CSCF. + +#### 6.5.2.5 Update of the Allowed WAF and/or WWSF Identities + +A request sent by the HSS to update the WAF and/or WWSF identities allowed for the subscription shall include the Private User Identity for whom this information changed. + +If corresponding Public Identity is registered and allowed WAF and/or WWSF identities are changed, the HSS should immediately push this information to the S-CSCF. + +## 6.6 Download of the Relevant User Profile and Charging Information and Allowed WAF and/or WWSF Identities + +The download of the relevant user profile, charging information and, if supported and part of subscription, allowed WAF and/or WWSF identities from the HSS to the S-CSCF depends on whether the user profile, charging information and, if supported and part of subscription, allowed WAF and/or WWSF identities are already stored in the S-CSCF. If the SiFC feature is supported by the HSS and S-CSCF, the HSS shall download the identifiers of the shared iFC sets. If either the HSS or the S-CSCF does not support the SiFC feature, the HSS shall download the complete iFCs, and SiFC identifiers shall not be downloaded by the HSS. The SiFC feature is defined in TS 29.229 [5]. + +If User-Data-Already-Available is set to USER\_DATA\_NOT\_AVAILABLE the HSS shall download the requested user profile, charging information and, if supported and part of subscription, allowed WAF and/or WWSF identities. If the Public User Identity in the request is included in an implicitly registered Public User Identity set, the HSS shall include in the response the service profiles associated with all Public User Identities within the implicitly registered Public User Identity set to which the received Public User Identity belongs. + +If User-Data-Already-Available is set to USER\_DATA\_ALREADY\_AVAILABLE, the HSS should not return any user profile or charging information data or allowed WAF and/or WWSF identities. The HSS may override User-Data-Already-Available set to USER\_DATA\_ALREADY\_AVAILABLE and download the user profile, charging information and, if supported and part of subscription, allowed WAF and/or WWSF identities. + +### 6.6.1 HSS initiated update of User Profile + +The request to update the user profile in the S-CSCF includes only the Public User Identities of the implicitly registered Public User Identity set with the associated service profiles. See 6.5.2.1. + +If the Public Identity is registered or unregistered (i.e. registered as a consequence of an originating or terminating request or there is a S-CSCF keeping the user profile stored) and there are changes in the user profile, the HSS should immediately push the complete user profile to the S-CSCF. + +### 6.6.2 S-CSCF operation + +At deregistration of a Public User Identity, the S-CSCF shall store the user information if it sends Server-Assignment-Request command including Server-Assignment-Type AVP set to value USER\_DEREGISTRATION\_STORE\_SERVER\_NAME or TIMEOUT\_DEREGISTRATION\_STORE\_SERVER\_NAME and the HSS responds with DIAMETER\_SUCCESS. Otherwise the S-CSCF shall not keep user information. + +## 6.7 S-CSCF Assignment + +The list of mandatory and optional capabilities received by an I-CSCF from the HSS allows operators to distribute users between S-CSCFs, depending on the different capabilities (e.g. features, role, geographical location) that each S-CSCF may have. Alternatively, an operator has the possibility to steer users to certain S-CSCFs. + +The operator shall define (possibly based on the functionality offered by each S-CSCF installed in the network) the exact meaning of the S-CSCF mandatory and optional capabilities available in his network. It is an operator task to allocate a unique value to represent a single capability (e.g. support of "wildcarded PSI") or a set of capabilities (e.g. support of "alias" and "Shared IFC sets" and "wildcarded PSI") and to use these values to identify capabilities that are mandatory and/or optional to support for a given subscription. It is a configuration task for the operator to ensure that the I-CSCF has a correct record of the capability values received from the HSS for each S-CSCF available in his + +network. The I-CSCF and the HSS do not need to know the semantic of these values. This semantic is exclusively an operator issue. + +As a first choice, the I-CSCF shall select an S-CSCF that has all the mandatory and optional capabilities for the user. Only if that is not possible shall the I-CSCF apply a 'best-fit' algorithm. If more than one S-CSCF is identified that supports all mandatory capabilities the I-CSCF may then consider optional capabilities in selecting a specific S-CSCF. The 'best-fit' algorithm is implementation dependent and out of the scope of this specification. + +It is the responsibility of the operator to ensure that there are S-CSCFs which have mandatory capabilities indicated by the HSS for any given user. However, configuration errors may occur. If such errors occur and they prevent the I-CSCF from selecting an S-CSCF which meets the mandatory capabilities indicated by the HSS, the I-CSCF shall inform the operator via the O&M subsystem. + +As an alternative to selecting an S-CSCF based on the list of capabilities received from the HSS, it is possible to steer users to certain S-CSCFs. To do this, the operator may include one or more S-CSCF names as part of the capabilities of the user profile. The reason for the selection (e.g. all the users belonging to the same company/group could be in the same S-CSCF to implement a VPN service) and the method of selection are operator issues and out of the scope of this specification. If this alternative is chosen, the HSS shall include Server-Name AVPs in the Server-Capabilities AVP and should not include Mandatory-Capability AVPs or Optional-Capability AVPs in the Server-Capabilities AVP, and the I-CSCF when receiving Server-Name AVPs within the Server-Capabilities AVP shall discard any Mandatory-Capability AVP and any Optional-Capability AVP received within the Server-Capabilities AVP. + +The following table is a guideline for operators that records S-CSCF capabilities that need to be supported by an S-CSCF in order to serve a user or a service (identified by a Public User Identity or Public Service Identity), that cannot be served by an S-CSCF which is only compliant to a previous 3GPP release. + +Table 6.7: Guidelines for S-CSCF Capabilities + +| Capability | Mandatory or Optional (NOTE 1) | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Support of "Wildcarded PSI" | M | This capability indicates that the assigned S-CSCF shall support the handling of Wildcarded PSIs. | +| Support of "OrigUnreg SPT" | M | This capability indicates that the assigned S-CSCF shall be able to process iFCs with a Session Case "Originating_Unregistered" received from the HSS in the user profile. | +| Support of "OrigCDIV SPT" | M | This capability indicates that the assigned S-CSCF shall be able to process iFCs with a Session Case "Originating_CDIV" received from the HSS in the user profile. | +| Support of "Shared iFC sets" | O | This capability indicates that the assigned S-CSCF may support the "SiFC" feature defined in the 3GPP TS 29.229 [5]. | +| Support of "Display Name" | O | This capability indicates that the assigned S-CSCF may support the handling of "Display Name". The behaviour of the S-CSCF related to this missing data is the same as if the HSS did not send the Display Name. | +| Support of "Alias" | O | This capability indicates that the assigned S-CSCF may support the "AliasInd" feature defined in 3GPP TS 29.229 [5]. | +| Support of "SIP Digest Authentication" | M | This capability indicates that the assigned S-CSCF shall support the handling of SIP Digest Authentication. | +| Support of "NASS Bundled Authentication" | M | This capability indicates that the assigned S-CSCF shall support the handling of NASS Bundled Authentication. | +| Support of "Wildcarded IMPUs" | M | This capability indicates that the assigned S-CSCF shall support the handling of Wildcarded Public User Identities. | +| Support of "Loose-Route " | M | This capability indicates that the assigned S-CSCF shall support the loose-route mechanism. | +| Support of "Service Level Trace" | M | This capability indicates that the assigned S-CSCF shall support the Service Level Trace mechanism. | +| Support of "Priority Service" | M | This capability indicates that the S-CSCF shall support a network default pre-configured namespace (e.g. "wps") and the associated Service Priority Level. See IETF RFC 4412 [22] and 3GPP TS 24.229 [8]. | +| Support of "Extended Priority " (NOTE 2) | M | This capability indicates that the S-CSCF shall support the Priority Namespaces and their associated Priority Levels. See IETF RFC 4412 [22] and 3GPP TS 24.229 [8]. | +| Support of "Early IMS Security" | M | This capability indicates that the assigned S-CSCF shall support GIBA. | +| Support of "Reference Location" | M | This capability indicates that the assigned S-CSCF shall support the handling of reference location as defined in 3GPP TS 23.167 [23]. | +| Support of "Privileged-Sender" | M | This capability indicates that the S-CSCF shall support privileged sender. See 3GPP TS 24.229 [8]. | +| Support of "IMSI" | M | This capability indicates that the assigned S-CSCF shall support the handling of the IMSI. | +| Support of "Maximum Number of allowed simultaneous registrations" | M | This capability indicates that the assigned S-CSCF shall support the handling of maximum number of allowed simultaneous registrations per user as received from the HSS. | +| NOTE 1: Mandatory (M) corresponds to a Mandatory Capability that shall be supported by the assigned S-CSCF for a given user. The I-CSCF shall not select an S-CSCF that does not meet a mandatory capability. The selection of a S-CSCF not supporting this capability would lead to an unspecified network behaviour.
Optional (O) corresponds to an Optional Capability that may be supported by the assigned S-CSCF for a given user. The selection of a S-CSCF that would not support this capability will not significantly affect the network behaviour. | | | +| NOTE 2: Support of "Extended Priority " is backward compatible with continued support of the "Priority Service". | | | + +# --- 7 Information element contents + +## 7.1 Visited Network Identifier + +This information element contains the domain name of the visited network. + +## 7.2 Public User Identity + +This information element contains the Public User Identity. For definition of a Public User Identity, see TS 23.003 [17]. + +When GPRS-IMS-Bundled Authentication (GIBA) is used, a Temporary Public User Identity is derived from the IMSI used for bearer network access according to the rules in TS 23.003 [17]. + +### 7.2a Public Service Identity + +This information element contains a Public Service Identity (PSI) that is hosted by an application server. For definition of a PSI, see TS 23.003 [17]. + +### 7.2b Wildcarded Public Identity + +This information element contains a Wildcarded PSI that is hosted by an application server or a Wildcarded Public User Identity. For definition of a Wildcarded PSI and a Wildcarded Public User Identity, see TS 23.003 [17]. + +### 7.2c Void + +## 7.3 Private User Identity + +This information element contains the Private User Identity. For definition of a Private User Identity, see TS 23.003 [17]. + +When GPRS-IMS-Bundled Authentication (GIBA) is used, the Private User Identity is derived from the IMSI as specified in TS 33.203 [3]. + +### 7.3a Private Service Identity + +This information element contains the Private Service Identity. For definition of a Private Service Identity, see TS 23.003 [17]. + +## 7.4 S-CSCF Name + +This information element contains the S-CSCF Name of the S-CSCF assigned to an IMS Subscription. For definition of a S-CSCF Name, see TS 23.008 [18]. + +### 7.4a AS Name + +This information element contains the AS Name of the AS hosting a Public Service Identity. For definition of AS Name, see TS 23.008 [18]. + +## 7.5 S-CSCF Capabilities + +This information element carries information to assist the I-CSCF during the process of selecting an S-CSCF for a certain IMS Subscription. + +## 7.6 Result + +This information element contains result of an operation. See TS 29.229 [5] for the possible values. + +## 7.7 User Profile + +This information element contains the user profile in XML format. The user profile XML shall be valid against the user profile XML schema defined in Annex E. + +Annex B specifies the UML logical model of the user profile downloaded via the Cx interface. + +Annex D contains and informative, high level representation, of the wire representation of user profile data. + +## 7.8 Server Assignment Type + +Indicates the type of server assignment. See TS 29.229 [5] for the list of existing values. + +## 7.9 Authentication Data + +This information element is composed of the following sub-elements. + +### 7.9.1 Item Number + +This information element indicates the order in which the authentication vectors are to be consumed. See TS 29.229 [5] for coding details. + +### 7.9.2 Authentication Scheme + +This information element contains the authentication scheme, which is used to encode the authentication parameters. See TS 29.229 [5] for a list of values. + +### 7.9.3 Authentication Information + +This information element is used to convey the challenge and authentication token used during the authentication procedure, see TS 33.203 [3] for more information. See TS 29.229 [5] for coding details. + +### 7.9.4 Authorization Information + +This information element is used, in an authentication request, to indicate a failure of synchronization. In a response, it is used to convey the expected response to the challenge used to authenticate the user, see TS 33.203 [3] for more information. See TS 29.229 [5] for coding details. + +### 7.9.5 Confidentiality Key + +This information element contains the confidentiality key, see TS 33.203 [3] for more information. See TS 29.229 [5] for coding details. + +### 7.9.6 Integrity Key + +This information element contains the integrity key, see TS 33.203 [3] for more information. See TS 29.229 [5] for coding details. + +### 7.9.7 Authentication Context + +This information element contains authentication-related information relevant for performing the authentication but that is not part of the SIP authentication headers. Some mechanisms (e.g. PGP, digest with quality of protection set to authint defined in IETF RFC 2617 [16], digest with predictive nonces or sip access digest) request that part or the whole SIP request (e.g. the SIP method) is passed to the entity performing the authentication. In such cases the SIPAuthentication-Context AVP shall be carrying such information. + +See TS 29.229 [5] for coding details. + +### 7.9.8 Digest Authenticate + +This information element is composed of the following sub-elements. + +#### 7.9.8.1 Digest Realm + +This information element is part of the Digest authentication challenge, and corresponds to the Realm parameter as defined in IETF RFC 3261 [11]. This information element is used to convey the Realm to the S-CSCF during the SIP Digest authentication procedure. See TS 29.229 [5] for coding details. + +#### 7.9.8.2 Void + +#### 7.9.8.3 Digest Algorithm + +This information element is part of the Digest authentication challenge, defined in IETF RFC 2617 [16]. See TS 29.229 [5] for coding details. + +#### 7.9.8.4 Digest QoP + +This information element is part of the Digest authentication challenge, defined in IETF RFC 2617 [16]. It provides the Quality of Protection indication and has an effect on the digest computation. See TS 29.229 [5] for coding details. + +#### 7.9.8.5 Digest HA1 + +This information element is part of the Digest authentication challenge, defined in IETF RFC 2617 [16]. See TS 29.229 [5] for coding details. + +### 7.9.9 Line Identifier + +This information element contains the line identifier of the user's network termination. See TS 29.229 [5] for coding details. + +### 7.9.10 Framed IP Address + +See TS 29.229 [5] for more information. + +### 7.9.11 Framed IPv6 Prefix + +See TS 29.229 [5] for more information. + +### 7.9.12 Framed Interface Id + +See TS 29.229 [5] for more information. + +#### 7.9.8.1 Digest Realm + +This information element is part of the Digest authentication challenge, and corresponds to the realm parameter as defined in IETF RFC 3261 [11]. This information element is used to convey the realm to the S-CSCF during the SIP Digest authentication procedure. + +#### 7.9.8.2 Void + +#### 7.9.8.3 Digest Algorithm + +This information element is part of the Digest authentication challenge, defined in IETF RFC 2617 [16]. + +#### 7.9.8.4 Digest QoP + +This information element is part of the Digest authentication challenge, defined in IETF RFC 2617 [16]. It provides the Quality of Protection indication and has an effect on the digest computation. + +#### 7.9.8.5 Digest HA1 + +This information element is part of the Digest authentication challenge, defined in IETF RFC 2617 [16]. + +### 7.9.9 Line Identifier + +This information element contains the line identifier of the user's network termination. + +## 7.10 Number Authentication Items + +This information element contains the number of authentication vectors requested or delivered. + +## 7.11 Reason for de-registration + +This information element contains the reason for a de-registration procedure. + +## 7.12 Charging information + +Addresses of the charging functions. See TS 29.229 [5]. + +## 7.13 Routing information + +Information to route requests. + +## 7.14 Type of authorization + +Type of authorization requested by the I-CSCF. See TS 29.229 [5] for a list of values. + +## 7.15 Void + +Void + +## 7.16 User Data Already Available + +This information element indicates to the HSS if the user profile is already available in the S-CSCF. See TS 29.229 [5] for a list of values. + +## 7.17 Associated Private Identities + +This information element indicates to the S-CSCF the Private Identities, which belong to the same IMS Subscription as the Private Identity received in the request command. See TS 29.229 [5]. + +## 7.18 Originating-Request + +This information element indicates to the HSS that the request is related to an originating SIP message. See 3GPP 29.229 [5]. + +## 7.19 User Authorization Request Flags + +This information element carries the following indication (see 3GPP 29.229 [5] for coding details): + +- IMS Emergency Registration. + +## 7.20 Loose-Route Indication + +This information element indicates to the S-CSCF that the loose-route mechanism shall be applied to the public identities contained in the user profile received from the HSS. See TS 29.229 [5]. This information is static data for the duration of the subscription or the validity of the IMS identity. Modification of this data result in Network Initiated Deregistration (SERVER\_CHANGE); see clause 6.1.3.1. + +## 7.21 S-CSCF Restoration Information + +This information element contains information for the S-CSCF to handle traffic for a registered user. It is associated with the Private User Identity and the Implicit Registration Set that is affected by the SAR request. See TS 29.229 [5] for the contents of this information element. + +## 7.22 Associated Registered Private Identities + +This information element indicates to the S-CSCF the Registered Private Identities, which were registered with the Public Identity received in the request command. See TS 29.229 [5]. + +## 7.23 Multiple Registration Indication + +This information element indicates to the HSS that this is related to a multiple registration. See TS 29.229 [5]. + +## 7.24 Session-Priority + +This information element indicates the session's priority level to the HSS. See TS 29.229 [5]. + +## 7.25 Identities with Emergency Registration + +This information element indicates to the HSS a list of pairs of Private / Public Identities that are emergency registered. See TS 29.229 [5]. + +## 7.26 Privileged-Sender Indication + +This information element indicates to the S-CSCF that the Private User Identity shall be considered as a privileged sender, as described in TS 24.229 [8]. + +## 7.27 LIA Flags + +This information element carries the following indications. See TS 29.229 [5] for coding details. + +- PSI Direct Routing Indication + +## 7.28 Server Assignment Request Flags + +This information element carries the following indication (see 3GPP 29.229 [5] for coding details): + +- P-CSCF Restoration Indication + +## 7.29 Allowed WAF and/or WWSF Identities + +Addresses of the WebRTC Authentication Functions and/or WebRTC Web Server Functions allowed for a subscription. See TS 33.203 [3]. + +## 7.30 RTR Flags + +This information element carries the following indications. See TS 29.229 [5] for coding details. + +- Reference Location Information change + +# --- 8 Error handling procedures + +## 8.1 Registration error cases + +This clause describes the handling of error cases, which can occur during the registration process. If the new and previously assigned S-CSCF names sent in the Multimedia-Auth-Request command are different and the Multimedia-Auth-Request is not indicating synchronisation failure (i.e. the request does not contain *auts* parameter), then the HSS shall overwrite the S-CSCF name. + +If the new and previously assigned S-CSCF names sent in a command other than the Multimedia-Auth-Request command are different and the S-CSCF reassignment pending flag is not set, then the HSS shall not overwrite the S-CSCF name; instead it shall send a response to the S-CSCF indicating an error. + +### 8.1.1 Cancellation of the old S-CSCF + +It is possible that in certain situations the HSS receives a Multimedia-Auth-Request (MAR) command including a S-CSCF name, which is not the same as the previously assigned S-CSCF for the user. This can happen e.g. in case the new S-CSCF is selected due to a failure in the re-registration if the previously assigned S-CSCF does not respond to REGISTER message sent from the I-CSCF after a timeout. + +In this case, the new S-CSCF is assigned for the user and if registrations in the previously assigned S-CSCF exist for the user, these registrations in the old S-CSCF are handled locally in the old S-CSCF, e.g. re-registration timers in the old S-CSCF shall cancel the registrations. + +Additionally, the HSS should de-register the registrations in the old S-CSCF by using the Registration-Termination-Request command. In this case, the HSS shall first check whether the deregistration is really required by comparing the Diameter client address of the newly assigned S-CSCF received in the MAR command to the Diameter client address + +stored in the HSS. If the Diameter client addresses match, the deregistration shall not be initiated. Otherwise the deregistration should be initiated for all the registered Public User Identities for the corresponding IMS Subscription. HSS shall check whether IMS Restoration Procedures are supported to perform deregistration: + +- If supported, Registration-Termination-Request shall be sent for all Public User Identities (with their associated Private User Identities), with Deregistration-Reason AVP value set to NEW\_SERVER\_ASSIGNED. +- Otherwise, Registration-Termination-Request shall be sent with different Deregistration-Reason AVP values, in the following order: + 1. Deregistration-Reason AVP value set to NEW\_SERVER\_ASSIGNED, for the Public User Identity (with its associated Private User Identity), which is registered in the new S-CSCF. + 2. Deregistration-Reason AVP value set to SERVER\_CHANGE, for the user Public User Identities (with their associated Private User Identities), which are not yet registered in the new S-CSCF. + +### 8.1.2 Error in S-CSCF name + +If the S-CSCF name sent in the Server-Assignment-Request command and the previously assigned S-CSCF name stored in the HSS are different and the S-CSCF reassignment pending flag is not set, then the HSS shall not overwrite the S-CSCF name. If the Server Assignment Type indicates NO\_ASSIGNMENT, the HSS shall send a response to the S-CSCF with Result-Code value set to DIAMETER\_UNABLE\_TO\_COMPLY. For all other Server Assignment Types, the HSS shall send a response to the S-CSCF with Experimental-Result-Code value set to DIAMETER\_ERROR\_IDENTITY\_ALREADY\_REGISTERED. + +If the S-CSCF name sent in the Server-Assignment-Request command and the previously assigned S-CSCF name stored in the HSS are different and IMS Restoration Procedures are supported and the S-CSCF reassignment pending flag is set, then the HSS shall allow overwriting of the S-CSCF name and proceed with the processing of the SAR command as defined in clause 6.1.2. + +### 8.1.3 Error in S-CSCF assignment type + +If the Server-Assignment-Type in the Server-Assignment-Request command sent by the S-CSCF to the HSS is not allowed (i.e if the Server-Assignment-Type is not applicable based on the user state or it is not applicable based on the user identity type), the HSS shall send a response to the S-CSCF with the Experimental-Result-Code value set to DIAMETER\_ERROR\_IN\_ASSIGNMENT\_TYPE. + +# --- 9 Protocol version identification + +See TS 29.229 [5]. + +# --- 10 Operational Aspects + +See TS 29.229 [5]. + +# Annex A (normative): Mapping of Cx operations and terminology to Diameter + +## A.1 Introduction + +This appendix gives mappings from Cx to Diameter protocol elements. Diameter protocol elements are defined in TS 29.229 [5]. + +## A.2 Cx message to Diameter command mapping + +The following table defines the mapping between stage 2 operations and Diameter commands: + +**Table A.2.1: Cx message to Diameter command mapping** + +| Cx message | Source | Destination | Command-Name | Abbreviation | +|-------------------------------------|--------|-------------|-----------------------------------|--------------| +| Cx-Query + Cx-Select-Pull | I-CSCF | HSS | User-Authorization-Request | UAR | +| Cx-Query Resp + Cx-Select-Pull Resp | HSS | I-CSCF | User-Authorization-Answer | UAA | +| Cx-Put + Cx-Pull | S-CSCF | HSS | Server-Assignment-Request | SAR | +| Cx-Put Resp + Cx-Pull Resp | HSS | S-CSCF | Server-Assignment-Answer | SAA | +| Cx-Location-Query | I-CSCF | HSS | Location-Info-Request | LIR | +| Cx-Location-Query Resp | HSS | I-CSCF | Location-Info-Answer | LIA | +| Cx-AuthDataReq | S-CSCF | HSS | Multimedia-Authentication-Request | MAR | +| Cx-AuthDataResp | HSS | S-CSCF | Multimedia-Authentication-Answer | MAA | +| Cx-Deregister | HSS | S-CSCF | Registration-Termination-Request | RTR | +| Cx-Deregister Resp | S-CSCF | HSS | Registration-Termination-Answer | RTA | +| Cx-Update Subscr Data | HSS | S-CSCF | Push-Profile-Request | PPR | +| Cx-Update Subscr Data Resp | S-CSCF | HSS | Push-Profile-Answer | PPA | + +## A.3 Cx message parameters to Diameter AVP mapping + +The following table gives an overview about the mapping: + +**Table A.3.1: Cx message parameters to Diameter AVP mapping** + +| Cx parameter | AVP Name | +|----------------------------|----------------------------| +| Visited Network Identifier | Visited-Network-Identifier | +| Public Identity | Public-Identity | +| Private Identity | User-Name | +| S-CSCF Name | Server-Name | +| AS Name | | +| S-CSCF capabilities | Server-Capabilities | +| Result | Result-Code | +| | Experimental-Result-Code | + +| Cx parameter | AVP Name | +|------------------------------------|----------------------------------| +| User profile | User-Data | +| Server Assignment Type | Server-Assignment-Type | +| Authentication data | SIP-Auth-Data-Item | +| Item Number | SIP-Item-Number | +| Authentication Scheme | SIP-Authentication-Scheme | +| Authentication Information | SIP-Authenticate | +| Authorization Information | SIP-Authorization | +| Confidentiality Key | Confidentiality-Key | +| Integrity Key | Integrity-Key | +| Number Authentication Items | SIP-Number-Auth-Items | +| Reason for de-registration | Deregistration-Reason | +| Charging Information | Charging-Information | +| Routing Information | Destination-Host | +| Type of Authorization | Authorization-Type | +| Associated Private Identities | Associated-Identities | +| Digest Authenticate | SIP-Digest-Authenticate | +| Digest Realm | Digest-Realm | +| Digest Algorithm | Digest-Algorithm | +| Digest QoP | Digest-QoP | +| Digest HA1 | Digest-HA1 | +| Line Identifier | Line-Identifier | +| Wildcarded Public Identity | Wildcarded-Public Identity | +| Loose-Route Indication | Loose-Route-Indication | +| S-CSCF Restoration Information | SCSCF-Restoration-Info | +| Multiple Registration Indication | Multiple-Registration-Indication | +| Privileged-Sender Indication | Privileged-Sender-Indication | +| LIA Flags | LIA-Flags | +| Allowed WAF and/or WWSF Identities | Allowed-WAF-WWSF-Identities | + +## A.4 Message flows + +The following message flows give examples regarding which Diameter messages shall be sent in scenarios described in TS 23.228 [1]. + +### A.4.1 Registration– user not registered + + + +``` + +sequenceDiagram + participant UA + participant P-CSCF + participant I-CSCF + participant HSS + participant S-CSCF + + Note left of UA: Visited Network + Note right of S-CSCF: Home Network + + UA->>P-CSCF: 1. Register + P-CSCF->>I-CSCF: 2. Register + I-CSCF->>HSS: 3. UAR + HSS-->>I-CSCF: 4. UAA + Note right of I-CSCF: S-CSCF selection + I-CSCF->>S-CSCF: 5. Register + S-CSCF->>HSS: 6. MAR + Note right of HSS: Authentication vector selection + HSS-->>S-CSCF: 7. MAA + S-CSCF-->>I-CSCF: 8. 401 Unauthorised + Note right of S-CSCF: Authentication Information + I-CSCF-->>P-CSCF: 9. 401 Unauthorised + Note right of I-CSCF: Authentication Information + P-CSCF-->>UA: 10. 401 Unauthorised + Note right of P-CSCF: Authentication Information + UA->>P-CSCF: 11. Register response + P-CSCF->>I-CSCF: 12. Register response + I-CSCF->>HSS: 13. UAR + HSS-->>I-CSCF: 14. UAA + I-CSCF->>S-CSCF: 15. Register response + Note right of S-CSCF: Authentication + S-CSCF->>HSS: 18. SAR + HSS-->>S-CSCF: 19. SAA + S-CSCF-->>I-CSCF: 20. OK + I-CSCF-->>P-CSCF: 21. OK + P-CSCF-->>UA: 22. OK + +``` + +Sequence diagram for Registration – user not registered. The diagram shows the interaction between a User Agent (UA) in the Visited Network and various network elements (P-CSCF, I-CSCF, HSS, S-CSCF) in the Home Network. The process involves registration attempts, UAR/UAA exchanges, S-CSCF selection, authentication vector selection, and final OK responses. + +Figure A.4.1.1: Registration – user not registered + +### A.4.2 Registration – user currently registered + + + +``` +sequenceDiagram + participant UE + participant P-CSCF + participant I-CSCF + participant HSS + participant S-CSCF + Note left of UE: Visited Network + Note right of S-CSCF: Home Network + UE->>P-CSCF: 1. Register + P-CSCF->>I-CSCF: 2. Register + I-CSCF->>HSS: 3. UAR + HSS-->>I-CSCF: 4. UAA + I-CSCF->>S-CSCF: 5. Register + S-CSCF->>HSS: 6. SAR + HSS-->>S-CSCF: 7. SAA + S-CSCF->>I-CSCF: 8. 200 OK + I-CSCF->>P-CSCF: 9. 200 OK + P-CSCF->>UE: 10. 200 OK +``` + +Sequence diagram illustrating the Re-registration process (A.4.2.1). The diagram shows the interaction between the UE, P-CSCF, I-CSCF, HSS, and S-CSCF. The process starts with the UE sending a Register message to the P-CSCF. The P-CSCF forwards it to the I-CSCF, which sends a UAR to the HSS. The HSS responds with a UAA. The I-CSCF then sends a Register message to the S-CSCF. The S-CSCF sends a SAR to the HSS, which responds with a SAA. The S-CSCF then sends a 200 OK response to the I-CSCF, which in turn sends a 200 OK response to the P-CSCF, which finally sends a 200 OK response to the UE. + +Sequence diagram for Re-registration (A.4.2.1) + +Figure A.4.2.1: Re-registration + +### A.4.3 UE initiated de-registration + + + +``` +sequenceDiagram + participant UE + participant P-CSCF + participant I-CSCF + participant HSS + participant S-CSCF + Note left of UE: Visited Network + Note right of S-CSCF: Home Network + UE->>P-CSCF: 1. REGISTER + P-CSCF->>I-CSCF: 2. REGISTER + I-CSCF->>HSS: 3. UAR + HSS-->>I-CSCF: 4. UAA + I-CSCF->>S-CSCF: 5. REGISTER + S-CSCF->>HSS: 6. SAR + HSS-->>S-CSCF: 7. SAA + S-CSCF->>I-CSCF: 8. 200 OK + I-CSCF->>P-CSCF: 9. 200 OK + P-CSCF->>UE: 10. 200 OK +``` + +Sequence diagram illustrating the UE initiated de-registration process (A.4.3.1). The diagram shows the interaction between the UE, P-CSCF, I-CSCF, HSS, and S-CSCF. The process starts with the UE sending a REGISTER message to the P-CSCF. The P-CSCF forwards it to the I-CSCF, which sends a UAR to the HSS. The HSS responds with a UAA. The I-CSCF then sends a REGISTER message to the S-CSCF. The S-CSCF sends a SAR to the HSS, which responds with a SAA. The S-CSCF then sends a 200 OK response to the I-CSCF, which in turn sends a 200 OK response to the P-CSCF, which finally sends a 200 OK response to the UE. + +Sequence diagram for UE initiated de-registration (A.4.3.1) + +Figure A.4.3.1: UE initiated de-registration + +### A.4.4 Network initiated de-registration + +#### A.4.4.1 Registration timeout + + + +This sequence diagram illustrates the network-initiated de-registration process due to a registration timeout. It involves four entities: UE, P-CSCF, S-CSCF, and HSS. The process begins with timers expiring in both the P-CSCF and S-CSCF. The S-CSCF then sends a SAR (Service Authorization Request) to the HSS, which responds with an SAA (Service Authorization Answer). + +``` +sequenceDiagram + participant UE + participant P-CSCF + participant S-CSCF + participant HSS + Note right of P-CSCF: 1. Timer Expires + Note right of S-CSCF: 1. Timer Expires + S-CSCF->>HSS: 2. SAR + HSS-->>S-CSCF: 3. SAA +``` + +Sequence diagram for registration timeout de-registration + +Figure A.4.4.1.1: Network initiated de-registration – registration timeout + +#### A.4.4.2 Administrative de-registration + + + +This sequence diagram illustrates the network-initiated administrative de-registration process. It involves four entities: UE, P-CSCF, S-CSCF, and HSS. The process starts with the HSS sending an RTR (Re-Registration) to the S-CSCF. The S-CSCF then sends a Deregister message to the P-CSCF. The P-CSCF sends a UE Inform message to the UE. The UE responds with an OK 200 message to the P-CSCF, which in turn sends an OK 200 message to the S-CSCF. Finally, the S-CSCF sends an RTA (Re-Registration Termination Answer) to the HSS. + +``` +sequenceDiagram + participant UE + participant P-CSCF + participant S-CSCF + participant HSS + HSS->>S-CSCF: 1. RTR + S-CSCF->>P-CSCF: 2. Deregister + P-CSCF->>UE: 3. UE Inform + UE-->>P-CSCF: 5a. OK 200 + P-CSCF->>S-CSCF: 4. OK 200 + S-CSCF->>HSS: 5. RTA +``` + +Sequence diagram for administrative de-registration + +Figure A.4.4.2.1: Network initiated de-registration – administrative de-registration + +#### A.4.4.3 De-registration initiated by service platform + + + +``` +sequenceDiagram + participant UE + participant P-CSCF + participant S-CSCF + participant HSS + Note right of S-CSCF: 1. Service Control + S-CSCF->>P-CSCF: 2. Deregister + P-CSCF->>UE: 3. UE Inform + P-CSCF->>S-CSCF: 4. OK 200 + UE-->>P-CSCF: 5. OK 200 + S-CSCF->>HSS: 6. SAR + HSS->>S-CSCF: 7. SAA +``` + +Sequence diagram for network initiated de-registration initiated by service platform. Lifelines: UE, P-CSCF, S-CSCF, HSS. Steps: 1. Service Control (S-CSCF internal), 2. Deregister (S-CSCF to P-CSCF), 3. UE Inform (P-CSCF to UE), 4. OK 200 (P-CSCF to S-CSCF), 5. OK 200 (UE to P-CSCF), 6. SAR (S-CSCF to HSS), 7. SAA (HSS to S-CSCF). + +Figure A.4.4.3.1: Network initiated de-registration – initiated by service platform + +### A.4.5 UE Terminating SIP session set-up + + + +``` +sequenceDiagram + participant I-CSCF + participant HSS + participant S-CSCF + Note over I-CSCF, HSS, S-CSCF: Home Network + External->>I-CSCF: 1. INVITE + I-CSCF->>HSS: 2. LIR + HSS->>I-CSCF: 3. LIA + I-CSCF->>S-CSCF: 5. INVITE +``` + +Sequence diagram for UE Terminating SIP session set-up. Lifelines: I-CSCF, HSS, S-CSCF (under Home Network). Steps: 1. INVITE (External to I-CSCF), 2. LIR (I-CSCF to HSS), 3. LIA (HSS to I-CSCF), 5. INVITE (I-CSCF to S-CSCF). + +Figure A.4.5.1: UE Terminating SIP session set-up + +### A.4.6 Initiation of a session to a non-registered user + + + +This sequence diagram illustrates the interaction between an L-CSCF, HSS, and S-CSCF for session initiation to a non-registered user. The process begins with an external INVITE message to the L-CSCF. The L-CSCF sends a LIR to the HSS, which responds with a LIA. The L-CSCF then performs S-CSCF Selection and sends an INVITE to the S-CSCF. The S-CSCF sends a SAR to the HSS, which responds with a SAA. Finally, the S-CSCF performs Service Control and further actions. + +``` +sequenceDiagram + participant External + participant L-CSCF + participant HSS + participant S-CSCF + Note right of S-CSCF: 8. Service Control + Note right of S-CSCF: 9. S-CSCF performs further actions + + External->>L-CSCF: 1. INVITE + L-CSCF->>HSS: 2. LIR + HSS-->>L-CSCF: 3. LIA + Note left of L-CSCF: 4. S-CSCF Selection + L-CSCF->>S-CSCF: 5. INVITE + S-CSCF->>HSS: 6. SAR + HSS-->>S-CSCF: 7. SAA +``` + +Sequence diagram for session initiation to a non-registered user + +Figure A.4.6.1: Initiation of a session to a non-registered user + +#### A.4.6a AS originating session on behalf of a non-registered user + + + +This sequence diagram illustrates the interaction between an AS, I-CSCF, HSS, and S-CSCF for an AS originating session on behalf of a non-registered user. The AS sends an INVITE to the I-CSCF. The I-CSCF sends a LIR to the HSS, which responds with a LIA. The I-CSCF then performs S-CSCF Selection and sends an INVITE to the S-CSCF. The S-CSCF sends a SAR to the HSS, which responds with a SAA. Finally, the S-CSCF performs Service Control and further actions. A dashed box encloses the first five steps, indicating a specific interaction set. + +``` +sequenceDiagram + participant AS + participant I-CSCF + participant HSS + participant S-CSCF + Note right of S-CSCF: 4. Service Control + Note right of S-CSCF: 5. S-CSCF performs further actions + + AS->>I-CSCF: 1a. INVITE + Note left of I-CSCF: 1b1. INVITE + I-CSCF->>HSS: 1b2. LIR + HSS-->>I-CSCF: 1b3. LIA + Note left of I-CSCF: 1b4. S-CSCF Selection + I-CSCF->>S-CSCF: 1b5. INVITE + S-CSCF->>HSS: 2. SAR + HSS-->>S-CSCF: 3. SAA +``` + +Sequence diagram for AS originating session on behalf of a non-registered user + +Figure A.4.6a.1: AS originating session on behalf of a non-registered user + +### A.4.7 User Profile update + + + +``` +sequenceDiagram + participant S-CSCF + participant HSS + Note right of HSS: PPR + HSS->>S-CSCF: PPR + Note left of S-CSCF: PPA + S-CSCF->>HSS: PPA +``` + +Sequence diagram showing User Profile update between S-CSCF and HSS. The HSS sends a PPR message to the S-CSCF, and the S-CSCF sends a PPA message to the HSS. + +Figure A.4.7.1: User profile update + +# Annex B (informative): User profile UML model + +The purpose of this UML model is to define in an abstract level the structure of the user profile downloaded over the Cx interface and describe the purpose of the different information classes included in the user profile. + +## B.1 General description + +The following picture gives an outline of the UML model of the user profile, which is downloaded from HSS to S-CSCF: + + + +``` +classDiagram + IMSSubscription "1" *-- "1..n" ServiceProfile + IMSSubscription "1" *-- "0..1" ReferenceLocationInformation + class IMSSubscription { + Private User Identity + IMSI + } + class ServiceProfile + class ReferenceLocationInformation { + AccessType: string + AccessInfo: string + AccessValue: string + } +``` + +The diagram shows a UML class model for the User Profile. At the top is the **IMS Subscription** class, which contains two attributes: **Private User Identity** and **IMSI**. This class has a composition relationship with two other classes. To the left is the **ServiceProfile** class, with a multiplicity of **1..n** at its end. To the right is the **ReferenceLocationInformation** class, which contains three attributes: **AccessType: string**, **AccessInfo: string**, and **AccessValue: string**, with a multiplicity of **0..1** at its end. The composition is indicated by a solid diamond on the IMS Subscription side. + +UML Class Diagram of User Profile + +**Figure B.1.1: User Profile** + +IMS Subscription class contains as a parameter the private user identity of the user in NAI format and the IMSI of the user, if available, as defined in TS 23.003 [17]. + +Each instance of the IMS Subscription class contains zero or one instance of the class Reference Location Information. + +The class Reference Location Information contains zero or one attribute AccessType, zero or one attribute AccessInfo, and zero or one attribute AccessValue. + +The attribute AccessType indicates the type of access for which the reference location of the user is defined (e.g. ADSL). The attribute AccessInfo indicates the type of the access information defined for the reference location of the user (e.g. dsl-location). The attribute AccessValue contains the location information (e.g. line identifier in fixed access networks) as configured by the operator. + +Each instance of the IMS Subscription class contains one or several instances of the class Service Profile. + +## B.2 Service profile + +The following picture gives an outline of the UML model of the Service Profile class: + + + +``` +classDiagram + class ServiceProfile { + SharedIFCSetID: integer + } + class PublicIdentity + class CoreNetworkServicesAuthorization + class InitialFilterCriteria + + ServiceProfile "1" *-- "1..n" PublicIdentity + ServiceProfile "1" *-- "0..1" CoreNetworkServicesAuthorization + ServiceProfile "1" *-- "0..n" InitialFilterCriteria +``` + +The diagram shows a UML class structure. At the top is the **ServiceProfile** class, which contains an attribute **SharedIFCSetID: integer**. Below it, three classes are shown: **PublicIdentity**, **CoreNetworkServicesAuthorization**, and **InitialFilterCriteria**. The **ServiceProfile** class has a composition relationship with each of these three classes, indicated by a solid diamond. The multiplicities are: **ServiceProfile** (1) to **PublicIdentity** (1..n), **ServiceProfile** (1) to **CoreNetworkServicesAuthorization** (0..1), and **ServiceProfile** (1) to **InitialFilterCriteria** (0..n). + +UML Class Diagram for Service Profile + +**Figure B.2.1: Service Profile** + +Each instance of the Service Profile class consists of the following classes: + +- One or several instances of the Public-Identity class. PublicIdentity class contains the Public Identities associated with that service profile. The information in the CoreNetworkServicesAuthorization and InitialFilterCriteria classes apply to all PublicIdentification class instances, which are included in one ServiceProfile class. +- An optional instance of the CoreNetworkServicesAuthorization class. If no instance of the CoreNetworkServicesAuthorization class is present, no filtering related to subscribed media or restriction on IMS Communication Service Identifiers applies in the S-CSCF. +- Zero or several instances of the InitialFilterCriteria class. + +Each instance of the Service Profile class contains the following attributes: + +- Zero or more instances of the attribute SharedIFCSetID. A SharedIFCSetID attribute points to a set of Initial Filter Criteria locally administered and stored at the S-CSCF. Shared iFC Sets may be shared by several Service Profiles. + +### B.2.1 Public Identification + +The following picture gives an outline of the UML model of Public Identification class: + + + +``` + +classDiagram + class PublicIdentification["Public Identification"] { + BarringIndication: Boolean + Identity: anyURI + IdentityType: enumerated + WildcardedPSI: anyURI + DisplayName: string + AliasIdentityGroupId: string + WildcardedIMPU: anyURI + ServiceLevelTraceInfo: string + ServicePriorityLevel: enumerated + MaxNumOfAllowedSimultRegs: Integer + } + class ExtendedPriority { + PriorityNamespace: string + PriorityLevel: string + } + PublicIdentification "1" *-- "0..n" ExtendedPriority + +``` + +The diagram shows a class named "Public Identification" with the following attributes: BarringIndication (Boolean), Identity (anyURI), IdentityType (enumerated), WildcardedPSI (anyURI), DisplayName (string), AliasIdentityGroupId (string), WildcardedIMPU (anyURI), ServiceLevelTraceInfo (string), ServicePriorityLevel (enumerated), and MaxNumOfAllowedSimultRegs (Integer). Below this class is a diamond-shaped aggregation symbol connected to a class named "ExtendedPriority" with a multiplicity of "0..n". The "ExtendedPriority" class has two attributes: PriorityNamespace (string) and PriorityLevel (string). + +UML Class Diagram showing Public Identification and ExtendedPriority classes. + +**Figure B.2.1.1: Public Identification** + +The attribute BarringIndication is of type Boolean. If it is absent, or if it is present and set to FALSE, the S-CSCF shall not restrict the use of that public user identity in any IMS communications. If it is present and set to TRUE, the S-CSCF shall prevent that public identity from being used in any IMS communication except registrations and re-registrations, as specified in TS 24.229 [8]. + +Public Identification class can contain an Identity attribute. The attribute IdentityType indicates the type of identity contained in each case. It could be either: + +- A distinct Public User Identity +- A distinct Public Service Identity +- A Wildcarded Public Service Identity +- A non distinct Public User Identity, i.e. not explicitly provisioned in HSS. +- A Wildcarded Public User Identity + +If the identity type is not present, it is assumed to be a distinct Public User Identity. + +The attribute WildcardedPSI may be present (when IdentityType is WildcardedPSI) and contains the Wildcarded Public Service Identity that matched the Public Service Identity. This Wildcarded Public Service identity shall be sent as stored in the HSS, that is, including the delimiter described in TS 23.003 [17]. + +The attribute DisplayName allows a name to be associated with a Public Identity. + +The attribute AliasIdentityGroupID indicates the Alias Public User Identity Set to which the Public User Identity belongs. If the "AliasInd" feature is supported, all Public User Identities shall have an AliasIdentityGroupID allocated. Within an IMS subscription Public User Identities that have the same AliasIdentityGroupID allocated shall be in the same implicit registration sets, and shall share their service profile and the same service data for each and every service, and shall be regarded as aliases of each other, as defined in the TS 23.008 [18]. If the "AliasInd" feature is not supported, all Public User Identities within an IMS subscription that are within the same implicit registration set and share their service profile shall be regarded aliases of each other. + +The attribute WildcardedIMPU shall be present when IdentityType is a non distinct IMPU or it may be optionally present when IdentityType is a Wildcarded IMPU. It contains the Wildcarded Public User Identity that matched the + +Public User Identity. This Wildcarded Public User identity shall be sent as stored in the HSS, that is, including the delimiter described in TS 23.003 [17]. + +The attribute ServiceLevelTraceInfo provides the Service Level Tracing Information that is related to the Public User Identity. If the ServiceLevelTraceInfo is present, service level tracing shall be enabled in the S-CSCF for the related Public User Identity according to the configuration data received. If the ServiceLevelTraceInfo is not present, service level tracing is disabled in the S-CSCF for the related Public User Identity. + +The attribute ServicePriorityLevel provides the Priority Level allowed for the Public User Identity, which can be used by the S-CSCF and other network elements for Priority Service. + +The attribute PriorityNamespace provides the Namespace as specified in IETF RFC 4412 [22] and to which the Extended Priority refers. + +The attribute PriorityLevel provides the Priority Level allowed for the Public User Identity, for the Extended Priority. Its value depends on the PriorityNamespace. + +The attribute MaxNumOfAllowedSimultRegs provides the maximum number of allowed simultaneous registrations for the Public User Identity. + +### B.2.1A Core Network Service Authorization + +The following picture gives an outline of the UML model of Core Network Service Authorization class: + + + +``` +classDiagram + class CoreNetworkServiceAuthorization["Core Network Service Authorization"] + class SubscribedMediaProfileId["Subscribed Media Profile Id"] { + SubscribedMediaProfileId: Integer + } + class ListOfServiceIds["List of Service Ids"] + class ServiceId["Service Id"] { + ServiceId: string + } + + CoreNetworkServiceAuthorization "1" *-- "0..1" SubscribedMediaProfileId + CoreNetworkServiceAuthorization "1" *-- "0..1" ListOfServiceIds + ListOfServiceIds "1" *-- "0..n" ServiceId +``` + +The diagram illustrates the UML model for the Core Network Service Authorization class. It features three classes: Core Network Service Authorization, Subscribed Media Profile Id, and List of Service Ids. The Core Network Service Authorization class is at the top and has a composition relationship with both the Subscribed Media Profile Id and List of Service Ids classes, with a multiplicity of 0..1 for each. The List of Service Ids class further has a composition relationship with the Service Id class, with a multiplicity of 0..n. The Subscribed Media Profile Id class has an attribute SubscribedMediaProfileId of type Integer. The Service Id class has an attribute ServiceId of type string. + +UML Class Diagram for Core Network Service Authorization + +**Figure B.2.1A.1: Core Network Service Authorization** + +Each instance of the Core Network Service Authorization class contains zero or one instance of the class Subscribed Media Profile Id. If no instance of the class Subscribed Media Profile Id is present, no filtering related to subscribed media applies in S-CSCF. The Subscribed Media Profile Id is of type Integer and identifies a media profile in the S-CSCF for the authorization of media parameters. + +Each instance of the Core Network Service Authorization class contains zero or one instance of the class List of Service Ids. If no instance of the class List of Service Ids is present, no restriction on IMS Communication Service Identifiers related applies in S-CSCF. Each instance of the class List of Service Ids contains zero or more instances of the class Service Id. The Service Id is of type String and identifies an IMS Communication Service Identifier that the subscriber is authorized to use. + +### B.2.2 Initial Filter Criteria + +The following picture gives an outline of the UML model of Initial Filter Criteria class: + + + +``` + +classDiagram + class InitialFilterCriteria { + Priority: integer + ProfilePartIndicator: enumerated + } + class TriggerPoint { + ConditionTypeCNF: boolean + } + class ApplicationServer { + ServerName: SIP URL + DefaultHandling: enumerated + ServiceInfo: string + } + class SPT (ServicePointTrigger) { + ConditionNegated: boolean + Group: list of integers + } + class IncludeRegisterRequest + class IncludeRegisterResponse + + InitialFilterCriteria "1" *-- "0..1" TriggerPoint + InitialFilterCriteria "1" *-- "1" ApplicationServer + TriggerPoint "1" *-- "1..n" SPT + ApplicationServer "1" *-- "0..1" IncludeRegisterRequest + ApplicationServer "1" *-- "0..1" IncludeRegisterResponse + +``` + +The diagram illustrates the UML model for the Initial Filter Criteria class. At the top is the **InitialFilterCriteria** class with attributes **Priority: integer** and **ProfilePartIndicator: enumerated**. It has a composition relationship with the **TriggerPoint** class (multiplicity 0..1) and the **ApplicationServer** class (multiplicity 1). The **TriggerPoint** class has the attribute **ConditionTypeCNF: boolean** and is composed by the **SPT (ServicePointTrigger)** class (multiplicity 1..n). The **SPT** class has attributes **ConditionNegated: boolean** and **Group: list of integers**. The **ApplicationServer** class has attributes **ServerName: SIP URL**, **DefaultHandling: enumerated**, and **ServiceInfo: string**. It is composed by the **IncludeRegisterRequest** class (multiplicity 0..1) and the **IncludeRegisterResponse** class (multiplicity 0..1). + +UML Class Diagram of Initial Filter Criteria + +**Figure B.2.2.1.1: Initial Filter Criteria** + +Each instance of the InitialFilterCriteria class includes the following attributes: + +- One instance of Priority attribute that indicates the priority of the Filter Criteria. The higher the Priority Number the lower the priority of the Filter Criteria is; i.e., a Filter Criteria with a higher value of Priority Number shall be assessed after the Filter Criteria with a smaller Priority Number have been assessed. The same priority shall not be assigned to more than one initial Filter Criterion. +- An optional instance of ProfilePartIndicator attribute that is an enumerated type, with possible values "REGISTERED and UNREGISTERED, indicating if the iFC is a part of the registered or unregistered user profile. If ProfilePartIndicator is missing from the iFC, the iFC is considered to be relevant to both the registered and unregistered parts of the user profile, i.e. belongs to the common part of the user profile. + +Each instance of the InitialFilterCriteria class consists of the following classes: + +- An optional instance of TriggerPoint class that describes the trigger points that should be checked in order to find out if the indicated Application Server should be contacted or not. Each TriggerPoint is a boolean expression in Conjunctive or Disjunctive Normal form (CNF or DNF). The absence of Trigger Point instance will indicate an unconditional triggering to Application Server. + +The attribute ConditionTypeCNF attribute defines how the set of SPTs are expressed, i.e. either an Ored set of ANDed sets of SPT statements or an ANDed set of Ored sets of statements. Individual SPT statements can also be negated. These combinations are termed, respectively, Disjunctive Normal Form (DNF) and Conjunctive Normal Form (CNF) for the SPT (see Annex C). Both DNF and CNF forms can be used. ConditionTypeCNF is + +a boolean that is TRUE when the Trigger Point associated with the FilterCriteria is a boolean expression in Conjunctive Normal Form (CNF) and FALSE if the Trigger Point is expressed in Disjunctive Normal Form (DNF) (see Annex C). + +Each TriggerPoint class is composed by 1 to n instances of the SPT (ServicePointTrigger) class. + +- One instance of ApplicationServer class that defines the application server, which is contacted, if the trigger points are met. + +Each instance of the ApplicationServer class includes following attributes: + +- One instance of ServerName attribute that is the SIP URL of the application server to contact. +- An optional instance of DefaultHandling attribute that determines whether the dialog should be released if the Application Server could not be reached or not; it is of type enumerated and can take the values: SESSION\_ CONTINUED or SESSION\_ TERMINATED. +- One optional instance of the ServiceInfo attribute. The ServiceInfo attribute allows to download to S-CSCF information that is to be transferred transparently to an Application Server when the trigger points of a filter criterion are satisfied. ServiceInfo is a string conveying that information. See TS 23.218 [6] for a description of the use of this information element. + +Each instance of the ApplicationServer class includes following classes: + +- One optional instance of the IncludeRegisterRequest class that indicates to the S-CSCF that the incoming SIP REGISTER request is to be transferred to an Application Server when the trigger points of a filter criterion are satisfied. See TS 23.218 [6] for a description of the use of this information element. +- One optional instance of the IncludeRegisterResponse class that indicates to the S-CSCF that the final SIP response to the incoming SIP REGISTER request is to be transferred to an Application Server when the trigger points of a filter criterion are satisfied. See TS 23.218 [6] for a description of the use of this information element. + +### B.2.3 Service Point Trigger + +The following picture gives an outline of the UML model of Service Point Trigger class: + + + +``` + +classDiagram + class ServicePointTrigger { + ConditionNegated: boolean + Group: list of integer + RegistrationType: list of enumerated + } + class RequestURI { + RequestURI: string + } + class SIPMethod { + Method: string + } + class SIPHeader { + Header: string + Content: string + } + class SessionCase { + SessionCase: enumerated + } + class SessionDescription { + Line: string + Content: string + } + ServicePointTrigger <|-- RequestURI + ServicePointTrigger <|-- SIPMethod + ServicePointTrigger <|-- SIPHeader + ServicePointTrigger <|-- SessionCase + ServicePointTrigger <|-- SessionDescription + +``` + +The diagram shows a UML class hierarchy. At the top is the **Service Point Trigger** class, which has three attributes: **ConditionNegated** (boolean), **Group** (list of integer), and **RegistrationType** (list of enumerated). Below it, five classes inherit from **Service Point Trigger**: **Request-URI**, **SIP Method**, **SIP Header**, **Session Case**, and **Session Description**. Each of these five classes has its own specific attribute(s): **RequestURI** (string) for Request-URI, **Method** (string) for SIP Method, **Header** (string) and **Content** (string) for SIP Header, **SessionCase** (enumerated) for Session Case, and **Line** (string) and **Content** (string) for Session Description. + +UML Class Diagram for Service Point Trigger + +Figure B.2.3.1: Service Point Trigger + +The attribute **Group** of the class **Service Point Trigger** allows the grouping of SPTs that will configure the sub-expressions inside a CNF or DNF expression. For instance, in the following CNF expression $(A+B).(C+D)$ , $A+B$ and $C+D$ would correspond to different groups. + +In CNF, the attribute Group identifies the ORed sets of SPT instances. If the SPT belongs to different ORed sets, SPT can have more than one Group values assigned. At least one Group must be assigned for each SPT. + +In DNF, the attribute Group identifies the ANDed sets of SPT instances. If the SPT belongs to different ANDed sets, SPT can have more than one Group values assigned. At least one Group must be assigned for each SPT. + +The attribute ConditionNegated of the class Service Point Trigger defines whether the individual SPT instance is negated (i.e. NOT logical expression). + +**NOTE:** The operator should be aware that a negated Session Case implies that all other available session cases are set. The list of session cases depends on the release and can even be increased in the future, then a negated Session Case may end up triggering ASs unexpectedly (e.g. NOT ORIGINATED\_REGISTERED may trigger only TERMINATING\_UNREGISTERED and TERMINATING\_REGISTERED, or as well ORIGINATING\_UNREGISTERED and ORIGINATING\_CDIV). + +The attribute RegistrationType of the class Service Point Trigger is relevant only to the SIP Method SPT with a value of "REGISTER" and its' support is optional in the HSS and in the S-CSCF. The RegistrationType may contain a list of values that define whether the SPT matches to REGISTER messages that are related to initial registrations, re-registrations, and/or de-registrations. If RegistrationTypes are given, the SIP Method SPT with a value of "REGISTER" shall match if any of the RegistrationTypes match and the S-CSCF supports the RegistrationType attribute. If the SIP Method SPT contains value "REGISTER", and no RegistrationType is given, or if the S-CSCF does not support the RegistrationType attribute, the SIP Method SPT matches to all REGISTER messages. The attribute RegistrationType may be discarded if it is present in an SPT other than SIP Method with value "REGISTER". + +Request-URI class defines SPT for the Request-URI. Request-URI contains attribute RequestURI. + +SIP Method class defines SPT for the SIP method. SIP Method contains attribute Method which holds the name of any SIP method. + +SIP Header class defines SPT for the presence or absence of any SIP header or for the content of any SIP header. SIP Header contains attribute Header which identifies the SIP Header, which is the SPT, and the Content attribute defines the value of the SIP Header if required. + +The absence of the Content attribute and ConditionNegated = TRUE indicates that the SPT is the absence of a determined SIP header. + +Session Case class represents an enumerated type, with possible values "Originating", "Terminating\_Registered", "Terminating\_Unregistered", "Originating\_Unregistered", "Originating\_CDIV" indicating whether the filter should be used by the S-CSCF handling the Originating, Terminating for a registered end user, Terminating for an unregistered end user, Originating for an unregistered end user, or Originating after Call Diversion services. + +Session Description Information class defines SPT for the content of any SDP field within the body of a SIP Method. The Line attribute identifies the line inside the session description. Content is a string defining the content of the line identified by Line. + +# Annex C (informative): Conjunctive and Disjunctive Normal Form + +A Trigger Point expression is constructed out of atomic expressions (i.e. Service Point Trigger) linked by Boolean operators AND, OR and NOT. Any logical expression constructed in that way can be transformed to forms called Conjunctive Normal Form (CNF) and Disjunctive Normal Form (DNF). + +A Boolean expression is said to be in Conjunctive Normal Form if it is expressed as a conjunction of disjunctions of literals (positive or negative atoms), i.e. as an AND of clauses, each of which is the OR of one or more atomic expressions. + +Taking as an example the following trigger: + +Method = "INVITE" OR Method = "MESSAGE" OR (Method="SUBSCRIBE" AND NOT Header = "from" Content = "joe") + +The trigger can be split into the following atomic expressions: + +Method="INVITE" + +Method="MESSAGE" + +Method="SUBSCRIBE" + +NOT header="from" Content ="joe" + +Grouping the atomic expressions, the CNF expression equivalent to the previous example looks like: + +(Method="INVITE" OR Method = "MESSAGE" OR Method="SUBSCRIBE") AND (Method="INVITE" OR Method = "MESSAGE" OR (NOT Header = "from" Content = "joe")) + +This result in two "OR" groups linked by "AND" (CNF): + +(Method="INVITE" OR Method = "MESSAGE" OR Method="SUBSCRIBE") + +(Method="INVITE" OR Method = "MESSAGE" OR (NOT Header = "from" Content = "joe")) + +The XML representation of the trigger is: + +``` + +
0 (REGISTERED)
1 (UNREGISTERED) | +| tSharedIFCSetID | SharedIFCSetID | integer | >= 0 | +| tGroupID | Group | integer | >= 0 | +| tRegistrationType | RegistrationType | enumerated | Possible values:
0 (INITIAL_REGISTRATION)
1 (RE-REGISTRATION)
2 (DE-REGISTRATION) | +| tDefaultHandling | DefaultHandling | enumerated | Possible values:
0 (SESSION_CONTINUED)
1 (SESSION_TERMINATED) | +| tDirectionOfRequest | SessionCase | enumerated | Possible values:
0 (ORIGINATING_REGISTERED)
1 (TERMINATING_REGISTERED)
2 (TERMINATING_UNREGISTERED)
3 (ORIGINATING_UNREGISTERED)
4 (ORIGINATING_CDIV) | +| tPrivateID | PrivateID | anyURI | Syntax described in IETF RFC 2486 [14] | +| tSIP_URL | Identity | anyURI | Syntax described in IETF RFC 3261 [11] or 3GPP TS 23003 (See Note 1) | +| tTEL_URL | Identity | anyURI | Syntax described in IETF RFC 3966 [15] or 3GPP TS 23003 (See Note 1) | +| tIdentity | Identity | (union) | Union of tSIP_URL, and tTEL_URL | +| tIdentityType | IdentityType | enumerated | Possible values:
0 (DISTINCT_PUBLIC_USER_IDENTITY)
1 (DISTINCT_PSI)
2 (WILDCARDED_PSI) (See Note 2)
3 (NON_DISTINCT_IMPU) (See Note 3)
4 (WILDCARDED_IMPU) (See Note 4) | +| tServiceInfo | ServiceInfo | string | | +| tString | RequestURI, Method, Header, Content, Line, AccessType, AccessInfo, AccessValue | string | | +| tBool | ConditionTypeCNF, ConditionNegated, BarringIndication | boolean | Possible values:
0 (false)
1 (true) | +| tSubscribedMediaProfileId | SubscribedMediaProfileId | integer | >=0 | +| tDisplayName | DisplayName | string | | +| tAliasIdentityGroupID | AliasIdentityGroupID | string | | +| tServiceLevelTraceInfo | ServiceLevelTraceInfo | string | Syntax described in 3GPP TS 24.323 [32] | +| tServicePriorityLevel | ServicePriorityLevel | enumerated | Possible values:
0 (Highest priority)
1
2
3
4 (Lowest priority) | +| tPriorityNamespace | PriorityNamespace | string | Possible values are those of the namespaces that are defined in IETF RFC 4412 [22] or defined according to the IANA registration procedure described in IETF RFC 4412 [22] for Resource-Priority Namespaces. | +| tPriorityLevel | PriorityLevel | string | Possible values depend on the PriorityNamespace and are specified with the associated namespace that is defined in IETF RFC 4412 [22] or defined according to the IANA registration procedure described in IETF RFC 4412 [22] for Resource-Priority Namespaces | +| tIMSI | IMSI | string | Syntax described in 3GPP TS 23.003 [17]. ASCII encoded according to ANSI X3.4 [26]. | +| tMaxNumOfAllowedSi | MaxNumOfAllowedSi | integer | >= 1 | + +| | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|--|--| +| multRegistrations | multRegistrations | | | +| NOTE 1: Only when the "Identity" tag is a Wildcarded Identity the syntax is described in 1 23.003 [17]. It applies to both WILDCARDED_IMPU and WILDCARDED_PSI. | | | | +| NOTE 2: Wildcarded PSI could optionally be included as well in tPublicIdentityExtension. | | | | +| NOTE 3: The IMPU is not explicitly provisioned in HSS. In this case, corresponding Wildcarded IMPU is included in tPublicIdentityExtension3. | | | | +| NOTE 4: WILDCARDED_IMPU indicates that the content of the identity in the "Identity" tag is a Wildcarded Public User Identity. In this case, Wildcarded IMPU could optionally be included as well in tPublicIdentityExtension3. | | | | + +Table E.2: XML schema for the Cx interface user profile: complex data types + +| Data type | Tag | Compound of | | | +|-----------------------------------|----------------------------------|----------------------------------|-----------------------------------|----------------------| +| | | Tag | Type | Cardinality | +| tIMSSubscription | IMSSubscription | PrivateID | tPrivateID | 1 | +| | | ServiceProfile | tServiceProfile | (1 to n) | +| | | Extension | tIMSSubscriptionExtension | (0 to 1) | +| tIMSSubscriptionExtension | Extension | IMSI | tIMSI | (0 to 1) | +| | | Extension | tIMSSubscriptionExtension2 | (0 to 1) | +| tIMSSubscriptionExtension2 | Extension | ReferenceLocationInformation | tReferenceLocationInformation | (0 to n)
(NOTE 5) | +| tReferenceLocationInformation | ReferenceLocationInformation | AccessType | tString (NOTE 4) | (0 to 1) | +| | | AccessInfo | tString (NOTE 4) | (0 to 1) | +| | | AccessValue | tString (NOTE 4) | (0 to 1) | +| tServiceProfile | ServiceProfile | PublicIdentity | tPublicIdentity | (1 to n) | +| | | CoreNetworkServicesAuthorization | CoreNetworkServicesAuthorization | (0 to 1) | +| | | InitialFilterCriteria | tInitialFilterCriteria | (0 to n) | +| | | Extension | tServiceProfileExtension | (0 to 1) | +| tServiceProfileExtension | Extension | SharedIFCSetID | tSharedIFCSetID | (0 to n) | +| tCoreNetworkServicesAuthorization | CoreNetworkServicesAuthorization | SubscribedMediaProfileId | tSubscribedMediaProfileId | (0 to 1) | +| | | Extension | tCNServicesAuthorizationExtension | (0 to 1) | +| tPublicIdentity | PublicIdentity | BarringIndication | tBool | (0 to 1) | +| | | Identity | tIdentity | 1 | +| | | Extension | tPublicIdentityExtension | (0 to 1) | +| tInitialFilterCriteria | InitialFilterCriteria | Priority | tPriority | 1 | +| | | TriggerPoint | tTrigger | (0 to 1) | +| | | ApplicationServer | tApplicationServer | 1 | +| | | ProfilePartIndicator | tProfilePartIndicator | (0 to 1) | +| | | ConditionTypeCNF | tBool | 1 | +| tTrigger | TriggerPoint | SPT | tSePoTri | (1 to n) | +| | | ConditionNegated | tBool | (0 to 1) | +| tSePoTri | SPT | Group | tGroupID | (1 to n) | +| | | Choice of | RequestURI | tString | +| | | | Method | tString | +| | | | SIPHeader | tHeader | +| | | | SessionCase | tDirectionOfRequest | +| | | | SessionDescription | tSessionDescription | +| | | Extension | tSePoTriExtension | (0 to 1) | +| tSePoTriExtension | Extension | RegistrationType | tRegistrationType | (0 to 2) | +| tHeader | SIPHeader | Header | tString | 1 | +| | | Content | tString | (0 to 1) | +| tSessionDescription | SessionDescription | Line | tString | 1 | +| | | Content | tString | (0 to 1) | +| tApplicationServer | ApplicationServer | ServerName | tSIP_URL | 1 | +| | | DefaultHandling | tDefaultHandling | (0 to 1) | +| | | ServiceInfo | tServiceInfo | (0 to 1) | +| | | Extension | tApplicationServerExtension | (0 to 1) | +| tApplicationServerExtension | Extension | IncludeRegisterRequest | tIncludeRegisterRequest | (0 to 1) | +| | | IncludeRegisterResponse | tIncludeRegisterResponse | (0 to 1) | + +| | | | | | +|-----------------------------------|--------------------------|------------------------------------|-------------------------------------|----------| +| tIncludeRegisterRequest | IncludeRegisterRequest | (NOTE 2) | (NOTE 2) | (0 to 1) | +| tIncludeRegisterResponse | tIncludeRegisterResponse | (NOTE 2) | (NOTE 2) | (0 to 1) | +| tPublicIdentityExtension | Extension | IdentityType | tIdentityType | (0 to 1) | +| | | WildcardedPSI | anyURI (NOTE 3) | (0 to 1) | +| | | Extension | tPublicIdentityExtension2 | (0 to 1) | +| tPublicIdentityExtension2 | Extension | DisplayName | tDisplayName | (0 to 1) | +| | | AliasIdentityGroupID | tAliasIdentityGroupID | (0 to 1) | +| | | Extension | tPublicIdentityExtension3 | (0 to 1) | +| tPublicIdentityExtension3 | Extension | WildcardedIMPU | anyURI (NOTE 3) | (0 to 1) | +| | | ServiceLevelTraceInfo | tServiceLevelTraceInfo | (0 to 1) | +| | | ServicePriorityLevel | tServicePriorityLevel | (0 to 1) | +| | | Extension | tPublicIdentityExtension4 | (0 to 1) | +| tPublicIdentityExtension4 | Extension | ExtendedPriority | tExtendedPriority | (0 to n) | +| | | Extension | tPublicIdentityExtension5 | (0 to 1) | +| tPublicIdentityExtension5 | Extension | MaxNumOfAllowedSimultRegistrations | tMaxNumOfAllowedSimultRegistrations | (0 to 1) | +| tExtendedPriority | ExtendedPriority | PriorityNamespace | tPriorityNamespace | 1 | +| | | PriorityLevel | tPriorityLevel | 1 | +| tCNServicesAuthorizationExtension | Extension | ListOfServiceIds | tListOfServiceIds | (0 to 1) | +| tListOfServiceIds | ListOfServiceIds | ServiceId | tString | (0 to n) | + +NOTE 1: "n" shall be interpreted as non-bounded. +NOTE 2: empty cells shall be interpreted as complex XML elements without defined content. +NOTE 3: the syntax of Wildcarded Public User Identity and Wildcarded Service Identity shall be as described in 3GPP TS 23.003 [17]. +NOTE 4: the syntax of AccessType, AccessInfo and AccessValue is as described in 3GPP TS 24.229 [8] for P-Access-Network-Info header fields: AccessType corresponds to the "access-type" field whereas AccessInfo and AccessValue correspond to the type and associated value defined for the "access-info" field. +NOTE 5: the HSS shall not send more than one instance of ReferenceLocationInformation and if the S-CSCF receives more than one instance of ReferenceLocationInformation it may arbitrarily pick one for further processing. + +# Annex F (normative): Definition of parameters for service point trigger matching + +Table F.1 defines the parameters that are transported in the user profile XML. + +**Table F.1: Definition of parameters in the user profile XML** + +| Tag | Description | +|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| RequestURI | RequestURI tag shall include a regular expression in a form of Extended Regular Expressions (ERE) as defined in chapter 9 in IEEE 1003.1-2004 Part 1 [13]. For SIP URI, the regular expression shall be matched against the hostport of the SIP-URI. For definition of SIP-URI and hostport, see IETF RFC 3261 [11]. For Tel URI, the regular expression shall be matched against the telephone-subscriber of the telephone-uri. For definition of telephone-subscriber and telephone-uri, see IETF RFC 3966 [15]. | +| SIPHeader | A SIP Header SPT shall be evaluated separately against each header instance within the SIP message. The SIP Header SPT matches if at least one header occurrence matches the SPT. | +| Header (of SIPHeader) | Header tag shall include a regular expression in a form of Extended Regular Expressions (ERE) as defined in chapter 9 in IEEE 1003.1-2004 Part 1 [13]. The regular expression shall be matched against the header-name of the SIP header. For definition of header and header-name, see IETF RFC 3261 [11]. Before matching the header-name to the pattern, all SWSs shall be removed from the header-name and all LWSs in the header-name shall be reduced to a single white space character (SP). For definition of SWS and LWS, see IETF RFC 3261 [11]. | +| Content (of SIPHeader) | Content tag shall include a regular expression in a form of Extended Regular Expressions (ERE) as defined in chapter 9 in IEEE 1003.1-2004 Part 1 [13]. The regular expression shall be matched against the header-value of the SIP header. For definition of header and header-value, see IETF RFC 3261 [11]. If the SIP header contains several header-values in a comma-separated list, each of the header-value shall be matched against the pattern for the Content separately. Before matching the header-value to the pattern, all SWSs shall be removed from the header-value and all LWSs in the header-value shall be reduced to a single white space character (SP). For definition of SWS and LWS, see IETF RFC 3261 [11]. | +| SessionDescription | A Session Description SPT shall be evaluated separately against each SDP field instance within the SIP message. The Session Description SPT matches if at least one field occurrence matches the SPT. | +| Line (of SessionDescription) | Line tag shall include a regular expression in a form of Extended Regular Expressions (ERE) as defined in chapter 9 in IEEE 1003.1-2004 Part 1 [13]. The regular expression shall be matched against the type of the field inside the session description. For definition of type, see chapter 6 in IETF RFC 4566 [12]. | +| Content (of SessionDescription) | Content tag shall include a regular expression in a form of Extended Regular Expressions (ERE) as defined in chapter 9 in IEEE 1003.1-2004 Part 1 [13]. The regular expression shall be matched against the value of the field inside the session description. For definition of value, see chapter 6 in IETF RFC 4566 [12]. | + +# Annex G (normative): Emergency registrations + +S-CSCF and HSS shall handle emergency registrations as normal registrations with the following considerations: + +- Upon emergency registration, following cases apply: + - If a normal registration for the same user does not exist, the S-CSCF shall download corresponding user profile from HSS, ensure that the HSS allocates S-CSCF name to this subscriber and the registration status is set to UNREGISTERED. + - Otherwise, the S-CSCF shall ensure that the registration status of the user is not changed in the HSS. +- Upon deregistration or expiration of the last normal session, if an emergency registration is still active for this subscriber, the S-CSCF shall ensure that the HSS keeps S-CSCF name allocated to this subscriber and the registration status is set to UNREGISTERED. + +- Upon expiration of an emergency registration, the S-CSCF shall ensure the registration status of the user is not changed in the HSS if there are other normal registrations of the user. Otherwise, the S-CSCF may send SAR to the HSS to remove its name and set the registration status of the user to NOT REGISTERED. +- IMS Restoration procedures do not apply for IMS emergency sessions. + +# --- Annex H (normative): Diameter overload control mechanism + +## H.1 General + +Diameter overload control mechanism is an optional feature. + +IETF RFC 7683 [24] specifies a Diameter overload control mechanism which includes the definition and the transfer of related AVPs between Diameter nodes. + +It is recommended to make use of IETF RFC 7683 [24] on the Cx interface where, when applied, the I/S-CSCF shall behave as reacting nodes and the HSS as a reporting node. + +Depending on regional/national requirements and network operator policy, priority traffic (e.g. MPS as described in TS 22.153 [25]) shall be exempted from throttling due to Diameter overload control up to the point where requested traffic reduction cannot be achieved without throttling the priority traffic. + +## H.2 HSS behaviour + +The HSS requests traffic reduction from the I/S-CSCF when the HSS is in an overload situation, including OC-OLR AVP in answer commands as described in IETF RFC 7683 [24]. + +The HSS identifies that it is in an overload situation by implementation specific means. For example, the HSS may take into account the traffic over the Cx interfaces or other interfaces, the level of usage of internal resources (CPU, memory), the access to external resources, etc. + +The HSS determines the specific contents of OC-OLR AVP in overload reports and the HSS decides when to send OC-OLR AVPs by implementation specific means. + +## H.3 I/S-CSCF behaviour + +The I/S-CSCF applies required traffic reduction received in answer commands to subsequent applicable requests, as per IETF RFC 7683 [24]. + +The I/S-CSCF achieves requested traffic reduction by implementation specific means. For example, the I/S-CSCF may implement message throttling with prioritization or a message retaining mechanism for operations that can be postponed. + +Diameter requests related to priority traffic (e.g. MPS) and emergency, detected via the presence of priority information (e.g., Resource-Priority header field for MPS) in SIP messages as described in TS 24.229 [8], have the highest priority. Depending on regional/national regulatory and operator policies, these Diameter requests shall be the last to be throttled, when the I/S-CSCF has to apply traffic reduction. Relative priority amongst various priority traffic (e.g. MPS) and emergency traffic is subject to regional/national regulatory and operator policies. + +# --- Annex I (Informative): Diameter overload node behaviour + +## I.1 Message prioritization + +This clause describes possible behaviours of the I/S-CSCF regarding message prioritisation in an informative purpose. + +The I/S-CSCF may take the following into account when making throttling decisions: + +- Identification of the procedures that can be deferred (e.g. Deregistration Request), so to avoid to drop non deferrable procedures; +- Prioritisation of certain types of request (e.g. between MAR and SAR for S-CSCF, and between LIR and UAR for I-CSCF) according to the context of their use, in particular: + - Higher prioritisation of SAR commands for S-CSCF that are related to a registered user for a service, so to avoid the interruption of the registered service for the user; + - Higher prioritisation of LIR commands for I-CSCF that are related to a requested service different from registration or deregistration, so to get more originating or terminating services provided to the user; +- Skipping of optional authentication. +- Priority level of a priority user (e.g., MPS user). + +# --- Annex J (normative): Diameter message priority mechanism + +## J.1 General + +IETF RFC 7944 [27] specifies a Diameter message priority mechanism that allows Diameter nodes to indicate the relative priority of Diameter messages. With this information, other Diameter nodes may leverage the relative priority of Diameter messages into routing, resource allocation, set the DSCP marking for transport of the associated Diameter message, and also abatement decisions when overload control is applied. + +## J.2 Cx/Dx interfaces + +### J.2.1 General + +The Diameter message priority mechanism is an optional feature. + +It is recommended to make use of IETF RFC 7944 [27] over the Cx/Dx interfaces of an operator network when the overload control defined in Annex H is applied on these Cx/Dx interfaces. + +### J.2.2 S-CSCF/I-CSCF behaviour + +When the S-CSCF/I-CSCF supports the Diameter message priority mechanism, the S-CSCF/I-CSCF shall comply with IETF RFC 7944 [27]. + +The S-CSCF/I-CSCF sending a request shall determine the required priority according to its policies. When priority is required, the S-CSCF/I-CSCF shall include the DRMP AVP indicating the required priority level in the request it sends, and shall prioritise the request according to the required priority level. + +When the S-CSCF/I-CSCF receives the corresponding response, it shall prioritise the received response according to the priority level received within the DRMP AVP if present in the response, otherwise according to the priority level of the corresponding request. + +When the S-CSCF/I-CSCF receives a request, it shall handle the request according to the received DRMP AVP priority level. For the response, it may modify the priority level received in the DRMP AVP according to its policies and shall handle the response according to the required priority level. If the required priority level is different from the priority level received in the request, it shall include the DRMP AVP in the response. + +If: + +- the S-CSCF/I-CSCF supports using the Diameter message priority mechanism for DSCP marking purposes, +- the transport network utilizes DSCP marking, and +- message-dependant DSCP marking is possible for the protocol stack transporting Diameter, + +then the S-CSCF/I-CSCF shall set the DSCP marking for transport of the request or response according to the required priority level. + +Diameter requests related to priority traffic (e.g. MPS as identified by the S-CSCF/I-CSCF through SIP procedures, emergency) shall contain a DRMP AVP with a high priority of which the level value is operator dependent. + +When not-explicitly requested, the inclusion and priority value of the DRMP AVP in Diameter messages are implementation specific. + +### J.2.3 HSS/SLF behaviour + +When the HSS/SLF supports the Diameter message priority mechanism, the HSS/SLF shall comply with IETF RFC 7944 [27]. + +The HSS/SLF sending a request shall determine the required priority according to its policies. When priority is required, the HSS/SLF shall include the DRMP AVP indicating the required priority level in the request it sends, and shall prioritise the request according to the required priority level. + +When the HSS/SLF receives the corresponding response, it shall prioritise the received response according to the priority level received within the DRMP AVP if present in the response, otherwise according to the priority level of the corresponding request. + +When the HSS/SLF receives a request, it shall handle the request according to the received DRMP AVP priority level. For the response, it may modify the priority level received in the DRMP AVP according to its policies and shall handle the response according to the required priority level. If the required priority level is different from the priority level received in the request, it shall include the DRMP AVP in the response. + +If: + +- the HSS/SLF supports using the Diameter message priority mechanism for DSCP marking purposes, +- the transport network utilizes DSCP marking, and +- message-dependant DSCP marking is possible for the protocol stack transporting Diameter, + +then the HSS/SLF shall set the DSCP marking for transport of the request or response according to the required priority level. + +When not-explicitly requested, the inclusion and priority value of the DRMP AVP in Diameter messages are implementation specific. + +### J.2.4 Interactions + +If the HSS supporting the Diameter message priority mechanism receives the request message containing both the Session-Priority AVP and DRMP AVP, the HSS shall prioritize the request according to priority level received within the DRMP AVP. + +# --- Annex K (normative): Diameter load control mechanism + +## K.1 General + +The Diameter load control mechanism is an optional feature. + +It is recommended to make use of IETF IETF RFC 8583 [29] on the Cx interface where, when applied, the I-CSCF and the S-CSCF shall behave as reacting nodes and the HSS as a reporting node. + +## K.2 HSS behaviour + +The HSS may report its current load by including a Load AVP of type HOST in answer commands as described in IETF IETF RFC 8583 [29]. + +The HSS calculates its current load by implementation specific means. For example, the HSS may take into account the traffic over the Cx interface or other interfaces, the level of usage of internal resources (e.g. CPU, memory), the access to external resources, etc. + +The HSS determines when to send Load AVPs of type HOST by implementation specific means. + +## K.3 I-CSCF/S-CSCF behaviour + +When performing next hop Diameter Agent selection for requests that are routed based on realm, the I-CSCF/S-CSCF may take into account load values from Load AVPs of type PEER received from candidate next hop Diameter nodes, as per IETF IETF RFC 8583 [29]. + +# Annex L (informative): Change history + +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|----------|-------|-----------|-----|-----|----------------------------------------------------------------------------------------------------------|-------| +| Jun 2002 | CN#16 | NP-020264 | | | Version 2.0.0 approved at CN#16 | 5.0.0 | +| Sep 2002 | CN#17 | NP-020449 | 001 | 2 | Clarification of implicit registration | 5.1.0 | +| Sep 2002 | CN#17 | NP-020449 | 002 | 1 | Clarification of user registration status query | 5.1.0 | +| Sep 2002 | CN#17 | NP-020449 | 003 | 1 | Clarification of HSS initiated update of user profile | 5.1.0 | +| Sep 2002 | CN#17 | NP-020449 | 004 | 2 | Clarification of MAR command | 5.1.0 | +| Sep 2002 | CN#17 | NP-020449 | 005 | 1 | Conditionality of the SIP-Auth-Data-Item in MAA command | 5.1.0 | +| Dec 2002 | CN#18 | NP-020587 | 008 | 2 | Rejection of registration of a Temporary Public Identity without active implicit registration | 5.2.0 | +| Dec 2002 | CN#18 | NP-020587 | 010 | - | Removal of upper bounds in Cx i/f user profile | 5.2.0 | +| Dec 2002 | CN#18 | NP-020587 | 011 | - | S-CSCF Assignment | 5.2.0 | +| Dec 2002 | CN#18 | NP-020587 | 012 | - | NAS-Session-Key AVPs in MAA command | 5.2.0 | +| Dec 2002 | CN#18 | NP-020587 | 013 | 1 | Correction to detailed behaviour of user registration status query | 5.2.0 | +| Dec 2002 | CN#18 | NP-020587 | 014 | 1 | Removing the DDF dependencies from Cx interface | 5.2.0 | +| Dec 2002 | CN#18 | NP-020587 | 015 | 1 | Clarification of SERVER_CHANGE de-registration reason code | 5.2.0 | +| Dec 2002 | CN#18 | NP-020589 | 016 | 1 | Clarification of User-Authorization-Type AVP usage within the UAR | 5.2.0 | +| Dec 2002 | CN#18 | NP-020587 | 017 | 1 | Correction to HSS initiated update of user profile | 5.2.0 | +| Dec 2002 | CN#18 | NP-020588 | 019 | - | Correction in charging information | 5.2.0 | +| Dec 2002 | CN#18 | NP-020590 | 020 | 1 | Error handling in S-CSCF when receiving too much data | 5.2.0 | +| Dec 2002 | CN#18 | NP-020587 | 021 | 1 | Re-allocation of S-CSCF | 5.2.0 | +| Dec 2002 | CN#18 | NP-020591 | 022 | - | Correction of the SPI | 5.2.0 | +| Mar 2003 | CN#19 | NP-030101 | 025 | 1 | Clarification of service profile download at service profile modification | 5.3.0 | +| Mar 2003 | CN#19 | NP-030101 | 028 | - | Filter ID field removal in InitialFilterCriteria class | 5.3.0 | +| Mar 2003 | CN#19 | NP-030101 | 030 | 1 | Clarification of IMPU barring handling | 5.3.0 | +| Mar 2003 | CN#19 | NP-030101 | 032 | 1 | The default public user identity in the Server-Assignment-Answer | 5.3.0 | +| Mar 2003 | CN#19 | NP-030101 | 034 | 2 | Corrections to service profile | 5.3.0 | +| Mar 2003 | CN#19 | NP-030101 | 037 | 3 | Handling of non supported data in the S-CSCF when the profile is being updated | 5.3.0 | +| Mar 2003 | CN#19 | NP-030101 | 024 | 1 | Clarification of the HSS behaviour in REGISTRATION and DE REGISTRATION procedures at IMPU checking time. | 5.3.0 | +| Mar 2003 | CN#19 | NP-030101 | 027 | - | Deletion of Annex F | 5.3.0 | +| Mar 2003 | CN#19 | NP-030101 | 029 | - | Clarification of User-Authorization-Type AVP usage within UAR | 5.3.0 | +| Mar 2003 | CN#19 | NP-030101 | 031 | 1 | Update TS 29.228 after Diameter has become RFC | 5.3.0 | +| Mar 2003 | CN#19 | NP-030101 | 033 | 1 | Replacement of the NAS-Session-Key AVP | 5.3.0 | +| Mar 2003 | CN#19 | NP-030101 | 035 | 2 | Clarification on Re-allocation of S-CSCF | 5.3.0 | +| Mar 2003 | CN#19 | NP-030101 | 038 | 1 | Change of SPI to SPT | 5.3.0 | +| Mar 2003 | CN#19 | NP-030101 | 040 | 1 | Definition of the Subscribed Media Profile Identifier | 5.3.0 | +| Mar 2003 | CN#19 | NP-030101 | 026 | - | Error in definition of Service Point of Interest class | 5.3.0 | +| Jun 2003 | CN#20 | NP-030215 | 043 | - | Correct use of the Result-Code AVP | 5.4.0 | +| Jun 2003 | CN#20 | NP-030215 | 044 | 1 | Conditionality of User-Name AVP in Server-Assignment-Answer | 5.4.0 | +| Jun 2003 | CN#20 | NP-030215 | 045 | 2 | Corrections to the base 64 encoding examples | 5.4.0 | +| Jun 2003 | CN#20 | NP-030215 | 046 | 1 | Deregistration of implicitly registered public user identities | 5.4.0 | +| Jun 2003 | CN#20 | NP-030215 | 047 | - | Clarification on the Server-Assignment-Type NO_ASSIGNMENT | 5.4.0 | +| Jun 2003 | CN#20 | NP-030215 | 048 | 1 | Incorrect use of result-code | 5.4.0 | +| Jun 2003 | CN#20 | NP-030215 | 049 | 1 | Misalignment in the Public-User-Identity IE | 5.4.0 | +| Jun 2003 | CN#20 | NP-030215 | 050 | 1 | Duplicated Destination-Host AVP within MAR command code | 5.4.0 | +| Sep 2003 | CN#21 | NP-030383 | 042 | 3 | Error in S-CSCF Assignment Type | 5.5.0 | +| Sep 2003 | CN#21 | NP-030383 | 051 | 2 | Mistakes in the XML schema of 29.228-540 | 5.5.0 | +| Sep 2003 | CN#21 | NP-030383 | 055 | 1 | Extensibility of the public identity structure in the XML schema | 5.5.0 | +| Sep 2003 | CN#21 | NP-030394 | 041 | 2 | Introduction of Presence Stage 3 (Px) to the Cx interface | 6.0.0 | +| Sep 2003 | CN#21 | NP-030394 | 052 | - | Sharing public identities across multiple UEs | 6.0.0 | +| Dec 2003 | CN#22 | NP-030585 | 057 | 3 | Conditions for inclusion of Charging Information | 6.1.0 | +| Dec 2003 | CN#22 | NP-030500 | 060 | 1 | MAR in synchronisation failure case | 6.1.0 | +| Dec 2003 | CN#22 | NP-030500 | 061 | 1 | The S-CSCF name needs to be checked always in MAR | 6.1.0 | +| Dec 2003 | CN#22 | NP-030500 | 063 | - | Conditional AVPs in answer commands | 6.1.0 | +| Dec 2003 | CN#22 | NP-030500 | 065 | 1 | Server-Assignment-Request | 6.1.0 | +| Dec 2003 | CN#22 | NP-030500 | 067 | - | Determination of User-Authorization-Type AVP based on registration expiration | 6.1.0 | +| Dec 2003 | CN#22 | NP-030500 | 069 | 2 | Not registered state after deregistration with S-CSCF deleted at the HSS | 6.1.0 | +| Dec 2003 | CN#22 | NP-030500 | 071 | - | The extensibility of the XML schema | 6.1.0 | +| Dec 2003 | CN#22 | | | - | Reference [9] updated | 6.1.0 | +| Mar 2004 | CN#23 | NP-040046 | 077 | 1 | Clarification on S-CSCF-Name comparison | 6.2.0 | +| Mar 2004 | CN#23 | NP-040055 | 081 | - | Error for missing identification in SAR command | 6.2.0 | +| Mar 2004 | CN#23 | NP-040046 | 085 | 1 | Conditions for inclusion of Public Identity in SAR | 6.2.0 | +| Mar 2004 | CN#23 | NP-040046 | 087 | 1 | Correction to sending the Charging-Information AVP | 6.2.0 | + +| | | | | | | | +|----------|-------|-----------|------|---|-------------------------------------------------------------------------------------------------|-------| +| Mar 2004 | CN#23 | NP-040046 | 089 | - | Correction to User-Authorization-Answer | 6.2.0 | +| Mar 2004 | CN#23 | NP-040046 | 091 | - | Default handling of error cases during IMS registration | 6.2.0 | +| Jun 2004 | CN#24 | NP-040215 | 097 | 2 | Update of the charging addresses from HSS | 6.3.0 | +| Jun 2004 | CN#24 | NP-040215 | 095 | 1 | Content of the User Profile | 6.3.0 | +| Jun 2004 | CN#24 | NP-040215 | 099 | - | Correction of SessionCase attribute ambiguity | 6.3.0 | +| Sep 2004 | CN#25 | NP-040416 | 109 | 1 | LIR and services related to unregistered state | 6.4.0 | +| Sep 2004 | CN#25 | NP-040401 | 121 | 2 | Triggering initial REGISTER messages | 6.4.0 | +| Sep 2004 | CN#25 | NP-040401 | 118 | 1 | XML versioning | 6.4.0 | +| Sep 2004 | CN#25 | NP-040401 | 122 | 1 | Optimization of User Profile Download | 6.4.0 | +| Sep 2004 | CN#25 | NP-040396 | 124 | 2 | Simplification of the User Profile Split concept | 6.4.0 | +| Sep 2004 | CN#25 | NP-040416 | 120 | 3 | Use of regular expressions | 6.4.0 | +| Dec 2004 | CN#26 | NP-040523 | 138 | 1 | HSS initiated deregistration with "not registered" registration state | 6.5.0 | +| Dec 2004 | CN#26 | NP-040530 | 140 | 1 | HSS initiated deregistration with user profile removal for permanent termination | 6.5.0 | +| Dec 2004 | CN#26 | NP-040523 | 142 | 2 | HSS initiated deregistration using the network initiated de-registration procedure | 6.5.0 | +| Dec 2004 | CN#26 | NP-040530 | 146 | 1 | Clarification of R6 authentication scheme | 6.5.0 | +| Dec 2004 | CN#26 | NP-040523 | 150 | - | Regular Expressions | 6.5.0 | +| Dec 2004 | CN#26 | NP-040530 | 155 | - | Correction to XML Root Element | 6.5.0 | +| Dec 2004 | CN#26 | NP-040530 | 156 | 1 | Modification of User-Data-Already-Available in SAR command. | 6.5.0 | +| Dec 2004 | CN#26 | NP-040523 | 159 | 2 | Handling of Information Element marked as (M), (C) or (O) | 6.5.0 | +| Mar 2005 | CN#27 | NP-050030 | 166 | - | Avoiding undesired deregistration | 6.6.0 | +| Mar 2005 | CN#27 | NP-050030 | 168 | 1 | Correction to authentication procedures in not registered case | 6.6.0 | +| Mar 2005 | CN#27 | NP-050037 | 170 | 3 | Clarification of behaviour for Shared Public User Identities | 6.6.0 | +| Mar 2005 | CN#27 | NP-050037 | 172 | - | Distribution of Cipher Key and Integrity Key | 6.6.0 | +| Apr 2005 | | | | | Editorial correction on figure figure A.4.1.1 and on clauses: 6.1.4.1, 6.2.2, B.2.1 and 6.2.1.1 | 6.6.1 | +| Jun 2005 | CT#28 | CP-050086 | 181 | - | TEL-URI reference correction | 6.7.0 | +| Jun 2005 | CT#28 | CP-050086 | 183 | - | Clarification on Server Capabilities | 6.7.0 | +| Jun 2005 | CT#28 | CP-050086 | 185 | - | Incorrect Implementation of CR172 | 6.7.0 | +| Jun 2005 | CT#28 | CP-050081 | 188 | 1 | Clarification of the content of SIP-Authentication-Context | 6.7.0 | +| Jun 2005 | CT#28 | CP-050086 | 192 | - | Syntax correction for XML | 6.7.0 | +| Sep 2005 | CT#29 | CP-050422 | 196 | - | Authentication Registration with synchronization failure, Data requested from HSS | 6.8.0 | +| Sep 2005 | CT#29 | CP-050296 | 200 | - | Correction to XML Schema for SharedIFCSet | 6.8.0 | +| Sep 2005 | CT#29 | CP-050440 | 202 | 2 | Private identities on the Cx | 6.8.0 | +| Sep 2005 | CT#29 | CP-050282 | 204 | 1 | Charging-Information correction | 6.8.0 | +| Sep 2005 | CT#29 | CP-050296 | 207 | 1 | Corrections to UAR and LIR for shared public identities | 6.8.0 | +| Sep 2005 | CT#29 | CP-050422 | 208 | 1 | Behaviour of the Implicit Registration Set for the Unregistered state | 6.8.0 | +| Sep 2005 | CT#29 | CP-050296 | 210 | - | Change of stage 2 reference from Release 5 to Release 6 | 6.8.0 | +| Sep 2005 | CT#29 | CP-050294 | 211 | - | PSI Activation | 6.8.0 | +| Sep 2005 | CT#29 | CP-050271 | 213 | 2 | Removal of redundant restrictions for one Public User Identity in SAR | 6.8.0 | +| Sep 2005 | CT#29 | CP-050296 | 216 | - | Error code clean up | 6.8.0 | +| Sep 2005 | CT#29 | CP-050296 | 217 | 1 | Clarification of User Profile update | 6.8.0 | +| Dec 2005 | CT#30 | CP-050604 | 198 | 5 | XML syntax correction | 6.9.0 | +| Dec 2005 | CT#30 | CP-050611 | 220 | 1 | PSI impacts on the Cx Interface | 6.9.0 | +| Dec 2005 | CT#30 | CP-050611 | 221 | 3 | Routing for PSIs Matching a Wildcarded PSI | 6.9.0 | +| Dec 2005 | CT#30 | CP-050611 | 222 | 2 | Removal of overhead in Private Identities handling in RTR | 6.9.0 | +| Dec 2005 | CT#30 | CP-050605 | 229 | 2 | Use-Data description corrections | 6.9.0 | +| Dec 2005 | CT#30 | CP-050605 | 232 | 2 | S-CSCF assignment checking for notregistered state | 6.9.0 | +| Dec 2005 | CT#30 | CP-050605 | 236 | 4 | RTR correction | 6.9.0 | +| Dec 2005 | CT#30 | CP-050605 | 238 | 1 | PPR correction | 6.9.0 | +| Dec 2005 | CT#30 | CP-050611 | 239 | 1 | Private User Id in RTR | 6.9.0 | +| Dec 2005 | CT#30 | CP-050611 | 246 | 1 | Server capabilities associations with features | 6.9.0 | +| Dec 2005 | CT#30 | | | | Rel-7 version was created because of ETSI TISPAN references. | 7.0.0 | +| Mar 2006 | CT#31 | CP-060084 | 0243 | 1 | SPT for mobile orig unregistered | 7.1.0 | +| Mar 2006 | CT#31 | CP-060159 | 0247 | 2 | Removal of the terms Mobile Originated and Mobile Terminated | 7.1.0 | +| Mar 2006 | CT#31 | CP-060154 | 0254 | - | Alignment of Annex E with .xsd file | 7.1.0 | +| Mar 2006 | CT#31 | CP-060154 | 0256 | - | Incorrect implementation of CR 0198 | 7.1.0 | +| Mar 2006 | CT#31 | CP-060065 | 0260 | 2 | Handling of unknown errors | 7.1.0 | +| Mar 2006 | CT#31 | CP-060154 | 0263 | 2 | Private User ID in PPR and RTR | 7.1.0 | +| Mar 2006 | CT#31 | CP-060065 | 0269 | - | Message flow correction | 7.1.0 | +| Mar 2006 | CT#31 | CP-060065 | 0274 | - | Default public-id and PPR | 7.1.0 | +| Jun 2006 | CT#32 | CP-060302 | 0285 | - | S-CSCF reselection removal | 7.2.0 | +| Jun 2006 | CT#32 | CP-060308 | 0290 | 3 | Correction of the normative text in the table 6.7 | 7.2.0 | +| Jun 2006 | CT#32 | CP-060308 | 0292 | 2 | Using SiFC feature to define optional S-CSCF capabilities | 7.2.0 | +| Sep 2006 | CT#33 | CP-060308 | 0296 | - | S-CSCF assignment correction | 7.3.0 | +| Sep 2006 | CT#33 | CP-060405 | 0299 | - | Default Public User ID either SIP URI or tel URI | 7.3.0 | +| Sep 2006 | CT#33 | CP-060399 | 0304 | 1 | Barring Indication for public user identity | 7.3.0 | +| Sep 2006 | CT#33 | CP-060417 | 0306 | 2 | Deletion of description about Authentication-Data-Item | 7.3.0 | +| Sep 2006 | CT#33 | CP-060399 | 0313 | 1 | Registration message flow correction | 7.3.0 | +| Sep 2006 | CT#33 | CP-060417 | 0314 | 4 | AS originating requests on behalf of a user | 7.3.0 | + +| | | | | | | | +|----------|-------|-----------|------|---|---------------------------------------------------------------------------------|-------| +| Sep 2006 | CT#33 | CP-060416 | 0317 | 2 | Allowing a Display Name to be associated with a Public Identity. | 7.3.0 | +| Sep 2006 | CT#33 | CP-060417 | 0320 | - | Update of the Table 6.7 "Guidelines for S-CSCF Capabilities" | 7.3.0 | +| Dec 2006 | CT#34 | CP-060553 | 0325 | 1 | SDP reference correction | 7.4.0 | +| Dec 2006 | CT#34 | CP-060566 | 0326 | 1 | New message flow about AS originating session | 7.4.0 | +| Dec 2006 | CT#34 | CP-060566 | 0327 | 1 | Correction of Private Identity description in SAR | 7.4.0 | +| Dec 2006 | CT#34 | CP-060566 | 0330 | 3 | Correction of error code in SAA | 7.4.0 | +| Dec 2006 | CT#34 | CP-060566 | 0332 | 1 | Clarification on use of Authentication pending flag | 7.4.0 | +| Dec 2006 | CT#34 | CP-060566 | 0336 | 3 | Optimization of handling of Wildcarded PSIs | 7.4.0 | +| Dec 2006 | CT#34 | CP-060555 | 0338 | 1 | Wildcarded PSI as key in PPR | 7.4.0 | +| Dec 2006 | CT#34 | CP-060553 | 0342 | 1 | Correction of the HSS behaviour in UAR/UAA command pair | 7.4.0 | +| Dec 2006 | CT#34 | CP-060735 | 0343 | 3 | Clarification regarding URI canonicalization – 29.228 | 7.4.0 | +| Mar 2007 | CT#35 | CP-070020 | 0346 | 3 | Clarification of the server name in LIA | 7.5.0 | +| Mar 2007 | CT#35 | CP-070020 | 0350 | 3 | User profile data synchronisation | 7.5.0 | +| Mar 2007 | CT#35 | CP-070020 | 0352 | - | SAA result code correction | 7.5.0 | +| Mar 2007 | CT#35 | CP-070019 | 0353 | 2 | Removal of roaming restrictions for Emergency Registrations | 7.5.0 | +| Mar 2007 | CT#35 | CP-070020 | 0354 | - | Definition and use of the Wildcarded PSI information element | 7.5.0 | +| Jun 2007 | CT#36 | CP-070309 | 0358 | 1 | Removal of editor's note on IMS Recovery Procedures | 7.6.0 | +| Jun 2007 | CT#36 | CP-070479 | 0359 | 2 | Impacts of the IMS Communication Service Identifier | 7.6.0 | +| Jun 2007 | CT#36 | CP-070309 | 0361 | 2 | Clarification on LIA | 7.6.0 | +| Jun 2007 | CT#36 | CP-070309 | 0365 | 1 | Adding User-Authorization-Type is absent condition to UAR Detailed behaviour | 7.6.0 | +| Jun 2007 | CT#36 | CP-070312 | 0367 | - | Modification to the tag RegistrationType to RegistrationType in the Annex E | 7.6.0 | +| Sep 2007 | CT#37 | CP-070520 | 0374 | 1 | Authentication failure and timeout handling | 7.7.0 | +| Sep 2007 | CT#37 | CP-070522 | 0378 | - | Incorrect implemented CR 120r3 | 7.7.0 | +| Sep 2007 | CT#37 | CP-070527 | 0379 | - | User Data Already Available | 7.7.0 | +| Nov 2007 | CT#38 | CP-070743 | 0388 | 1 | Handling of USER_UNKNOWN and NOT_SUPPORTED_USER_DATA error in PPA | 7.8.0 | +| Nov 2007 | CT#38 | CP-070744 | 0392 | 2 | Alias | 7.8.0 | +| Nov 2007 | CT#38 | CP-070755 | 0376 | 6 | Updates to 29.228 for Digest on the Cx Interface | 8.0.0 | +| Mar 2008 | CT#39 | CP-080019 | 0393 | 1 | IMS Restoration after an S-CSCF failure | 8.1.0 | +| Mar 2008 | CT#39 | CP-080022 | 0395 | 2 | Update for Supporting NASS-Bundled-Authentication | 8.1.0 | +| Mar 2008 | CT#39 | CP-080019 | 0398 | - | SIP Digest password push | 8.1.0 | +| Mar 2008 | CT#39 | CP-080019 | 0400 | 1 | Wildcarded Public User Identities | 8.1.0 | +| Jun 2008 | CT#40 | CP-080261 | 0399 | 3 | Originating services after call forwarding | 8.2.0 | +| Jun 2008 | CT#40 | CP-080261 | 0406 | - | XML example | 8.2.0 | +| Jun 2008 | CT#40 | CP-080267 | 0408 | - | Emergency Registration for REGISTRATION AND CAPABILITIES | 8.2.0 | +| Jun 2008 | CT#40 | CP-080267 | 0410 | - | Removal of restriction for barred user at Emergency Registrations | 8.2.0 | +| Sep 2008 | CT#41 | CP-080456 | 0413 | 2 | Emergency Public User Identity removal | 8.3.0 | +| Sep 2008 | CT#41 | CP-080460 | 0420 | 1 | Support of "Loose-Route" indication from HSS | 8.3.0 | +| Sep 2008 | CT#41 | CP-080463 | 0421 | - | Cx Impacts of IMS Restoration Procedures | 8.3.0 | +| Sep 2008 | CT#41 | CP-080460 | 0423 | 2 | Filter Criteria enhancement for 3rd party REGISTER | 8.3.0 | +| Sep 2008 | CT#41 | CP-080463 | 0425 | 1 | Addition of Registered Private Identities in SAA | 8.3.0 | +| Sep 2008 | CT#41 | CP-080460 | 0426 | 1 | Add Assigned S-CSCF name to SAA | 8.3.0 | +| Dec 2008 | CT#42 | CP-080698 | 0427 | 2 | Service Restoration for Registered IMPU | 8.4.0 | +| Dec 2008 | CT#42 | CP-080707 | 0431 | 2 | Support for IMS Service Level Trace | 8.4.0 | +| Dec 2008 | CT#42 | CP-080708 | 0432 | - | Removal of Digest Domain | 8.4.0 | +| Dec 2008 | CT#42 | CP-080696 | 0433 | 3 | Diameter Proxy Agent - an alternative User Identity to HSS resolution mechanism | 8.4.0 | +| Dec 2008 | CT#42 | CP-080708 | 0434 | 2 | S-CSCF and AS procedures with Enhanced Filter Criteria | 8.4.0 | +| Mar 2009 | CT#43 | CP-090023 | 0435 | 1 | Priority Service | 8.5.0 | +| Mar 2009 | CT#43 | CP-090026 | 0436 | 1 | Multiple Registrations in Registration | 8.5.0 | +| Mar 2009 | CT#43 | CP-090036 | 0440 | 2 | HSS Addresses | 8.5.0 | +| Mar 2009 | CT#43 | CP-090025 | 0441 | 1 | Loose Route Indication | 8.5.0 | +| Mar 2009 | CT#43 | CP-090028 | 0442 | 2 | Support for GPRS IMS Bundled Authentication (GIBA) in Cx | 8.5.0 | +| Sep 2009 | CT#45 | CP-090728 | 0447 | 1 | Incorrect CR implementation | 8.6.0 | +| Dec 2009 | CT#46 | | 0452 | 1 | Unregistered user clarification | 8.7.0 | +| Dec 2009 | CT#46 | | 0456 | 2 | Session-Priority AVP | 8.7.0 | +| Dec 2009 | CT#46 | | 0457 | 2 | HSS behaviour after PPA with unknown user | 8.7.0 | +| Dec 2009 | CT#46 | | 0458 | 1 | Check of the S-CSCF Name | 8.7.0 | +| Dec 2009 | CT#46 | | 0460 | - | IMPI must be sent in SAR for UE initiated requests | 8.7.0 | +| Dec 2009 | CT#46 | | | - | Upgraded unchanged from Rel-8 | 9.0.0 | +| Mar 2010 | CT#47 | CP-100033 | 0462 | - | Default IMPU | 9.1.0 | +| Mar 2010 | CT#47 | CP-100031 | 0468 | 1 | Wildcarded Public Identity | 9.1.0 | +| Mar 2010 | CT#47 | CP-100033 | 0470 | 1 | Priority service attribute | 9.1.0 | +| Mar 2010 | CT#47 | CP-100033 | 0474 | 1 | User-Auth-Type not checked | 9.1.0 | +| Mar 2010 | CT#47 | CP-100033 | 0476 | 1 | GIBA is not allowed when auth. Scheme is Unknown | 9.1.0 | +| Mar 2010 | CT#47 | CP-100042 | 0477 | 2 | Clarification on the use of User-Data-Already-Available | 9.1.0 | +| Mar 2010 | CT#47 | CP-100015 | 0482 | - | Server Capabilities | 9.1.0 | +| Mar 2010 | CT#47 | CP-100031 | 0466 | - | RTR for wildcarded public user identity | 9.1.0 | +| May 2010 | | | | - | XML-file corrected | 9.1.1 | +| Jun 2010 | CT#48 | CP-100412 | 0484 | 3 | Table not aligned with XML schema for wildcarded identities | 9.2.0 | + +| | | | | | | | +|-----------|-------|-----------------|------|---|------------------------------------------------------------------------------------|--------| +| Jun 2010 | CT#48 | CP-100412 | 0487 | 3 | SAR with NO_ASSIGNMENT correction | 9.2.0 | +| Jun 2010 | CT#48 | CP-100412 | 0489 | 2 | Update of IETF Reference | 9.2.0 | +| Sep 2010 | CT#49 | CP-100447 | 0493 | 2 | Wildcarded Identities handling | 9.3.0 | +| Sep 2010 | CT#49 | CP-100447 | 0495 | | Wrong order in table for XML schema | 9.3.0 | +| Sep 2010 | CT#49 | CP-100447 | 0497 | 2 | Cx-MAR handling correction in restoration procedures | 9.3.0 | +| Sep 2010 | CT#49 | CP-100447 | 500 | 1 | Ambiguity of Presence Conditions of IEs and AVP ABNF | 9.3.0 | +| Sep 2010 | CT#49 | CP-100447 | 507 | | Correction for de-registration procedure at restoration | 9.3.0 | +| Sep 2010 | CT#49 | CP-100447 | 504 | 2 | Mandatory and optional capabilities handling | 9.3.0 | +| Dec 2010 | CT#50 | CP-100668 | 0519 | | Coding of SIP-Authorization AVP and SIP-Authenticate AVP | 9.4.0 | +| Dec 2010 | CT#50 | CP-100697 | 0509 | 1 | Clarification on Alias | 10.0.0 | +| Mar 2011 | CT#51 | CP-110044 | 0521 | - | Originating CDIV Session Case including in XML | 10.1.0 | +| Mar 2011 | CT#51 | CP-110060 | 0515 | 5 | MPS over Cx | 10.1.0 | +| Jun 2011 | CT#52 | CP-110349 | 0529 | 2 | Handling of RTR for Emergency Registration | 10.2.0 | +| Jun 2011 | CT#52 | CP-110356 | 0532 | 1 | Emergency Restoration | 10.2.0 | +| Jun 2011 | CT#52 | CP-110356 | 0535 | - | Incorrect Use of Result-Code AVP | 10.2.0 | +| Jun 2011 | CT#52 | CP-110356 | 0538 | 1 | Error in assignment type for backward compatibility scenarios | 10.2.0 | +| Jun 2011 | CT#52 | CP-110383 | 0520 | 4 | Reference Location over Cx interface | 11.0.0 | +| Sep 2011 | CT#53 | CP-110566 | 0542 | | Privileged sender | 11.1.0 | +| Sep 2011 | CT#53 | CP-110566 | 0546 | 1 | Public Identity in canonical form | 11.1.0 | +| Dec 2011 | CT#54 | CP-110781 | 0552 | 1 | Identity in the service profile | 11.2.0 | +| Dec 2011 | CT#54 | CP-110781 | 0557 | 2 | Providing the IMSI to the S-CSCF | 11.2.0 | +| Dec 2011 | CT#54 | CP-110809 | 0553 | 1 | Behaviour of HSS not supported IMS Restoration Procedures to LIR | 11.2.0 | +| Mar 2012 | CT#55 | CP-120014 | 0562 | 1 | Server-Capability AVP in LIA and UAA | 11.3.0 | +| Mar 2012 | CT#55 | CP-120014 | 0566 | 1 | Update of charging information and authentication data | 11.3.0 | +| Jun 2012 | CT#56 | CP-120245 | 0558 | 2 | Maximum Number of simultaneous registrations | 11.4.0 | +| Sep 2012 | CT#57 | CP-120439 | 0576 | 1 | Emergency registrations do not affect registration status | 11.5.0 | +| Sep 2012 | CT#57 | CP-120456 | 0577 | 1 | Add RequestURI parameter to SPT matching | 11.5.0 | +| Nov 2012 | | | | | The specification version number in the header corrected | 11.5.1 | +| Dec 2012 | CT#58 | CP-120743 | 0578 | - | Experimental-Result-Code correction | 11.6.0 | +| Dec 2012 | CT#58 | CP-120743 | 0582 | 3 | PSI direct routing with restoration procedures | 11.6.0 | +| Dec 2012 | CT#58 | CP-120743 | 0583 | - | Negated Session Case | 11.6.0 | +| Mar 2013 | CT#59 | CP-130011 | 0593 | 1 | Identities with emergency registration in RTR | 11.7.0 | +| Mar 2013 | CT#59 | CP-130020 | 0599 | 1 | Clarification on Reference Location information | 11.7.0 | +| Jun 2013 | CT#60 | CP-130374 | 0600 | 1 | Absent User-Name after S-CSCF recovery | 11.8.0 | +| Sep 2013 | CT#61 | CP-130439 | 0606 | 2 | Cancellation of the old S-CSCF for IMS Subscription and IMS Restoration Procedures | 11.9.0 | +| Sep 2013 | CT#61 | CP-13046 clause | 0601 | - | Correction on Emergency Registration | 12.0.0 | +| Dec 2013 | CT#62 | CP-130627 | 0607 | 5 | Cx Charging Information Download | 12.1.0 | +| Jun 2014 | CT#64 | CP-140237 | 0609 | 2 | Wildcarded Public Identity in SAA | 12.2.0 | +| Jun 2014 | CT#64 | CP-140243 | 0611 | 2 | Diameter Overload Control Over Cx | 12.2.0 | +| Sep 2014 | CT#65 | CP-140506 | 0624 | 2 | P-CSCF Restoration indication | 12.3.0 | +| Sep 2014 | CT#65 | CP-140515 | 0626 | - | Clarification on REGISTRATION AND CAPABILITIES for De-registration | 12.3.0 | +| Sep 2014 | CT#65 | CP-140515 | 0627 | - | Clarification on Unregistered User | 12.3.0 | +| Dec 2014 | CT#66 | CP-140794 | 0628 | 2 | HSS behaviour when P-CSCF Restoration indication is received | 12.4.0 | +| Dec 2014 | CT#66 | CP-140790 | 0630 | 1 | Priority Consideration for Diameter Overload Control | 12.4.0 | +| Dec 2014 | CT#66 | CP-140777 | 0632 | 1 | Addition of IMS-AKA based on HTTP Digest AKAv2 for WebRTC | 12.4.0 | +| Mar 2015 | CT#67 | CP-150023 | 0639 | 1 | IMSI Encoding over Cx | 12.5.0 | +| Jun 2015 | CT#68 | CP-150251 | 0633 | 4 | RTR handling when emergency registration | 12.6.0 | +| Jun 2015 | CT#68 | CP-150251 | 0642 | 1 | "Digest-AKAv1-MD5" is used as well for other Digest-AKA versions | 12.6.0 | +| Jun 2015 | CT#68 | CP-150251 | 0643 | | Confidentiality-key is mandatory | 12.6.0 | +| Jun 2015 | CT#68 | CP-150261 | 0640 | - | ADMINISTRATIVE_DEREGISTRATION with P-CSCF-Restoration-Indication | 12.6.0 | +| July 2016 | | | | | Correction of typo in previous line of history table. | 12.6.1 | +| Sep 2015 | CT#69 | CP-150428 | 0647 | 1 | Authentication tables and IE clarifications in MAR/MAA | 12.7.0 | +| Sep 2015 | CT#69 | CP-150428 | 0649 | - | Wrong CR update | 12.7.0 | +| Sep 2015 | CT#69 | CP-150432 | 0644 | 1 | S-CSCF Restoration Information deletion with SAT=UNREGISTERED_USER | 12.7.0 | +| Sep 2015 | CT#69 | CP-150436 | 0645 | - | P-CSCF Restoration when IMS Restoration is supported | 12.7.0 | +| Dec 2015 | CT#70 | CP-150754 | 0653 | 2 | Allowed WAF and/or WWSF Identities | 12.8.0 | +| Dec 2015 | CT#70 | CP-150750 | 0654 | 1 | Authentication Information IE clarification | 12.8.0 | +| Dec 2015 | CT#70 | CP-150749 | 0655 | 1 | De-registration without IMPI | 12.8.0 | +| Dec 2015 | CT#70 | CP-150749 | 0656 | 1 | IMSI change | 12.8.0 | +| Dec 2015 | CT#70 | CP-150759 | 0658 | 1 | Update reference to DOI new IETF RFC | 12.8.0 | +| Dec 2015 | CT#70 | CP-150775 | 0652 | 4 | HSS supports IMS subscriptions corresponding to users managed by third parties | 13.0.0 | +| Dec 2015 | CT#70 | CP-150768 | 0659 | 4 | DRMP AVP Procedures over Cx/Dx | 13.0.0 | +| Mar 2016 | CT#71 | CP-160031 | 0661 | 6 | Introduction of AAA-1 interface | 13.1.0 | +| Mar 2016 | CT#71 | CP-160046 | 0662 | - | De-registration of emergency registration correction | 13.1.0 | +| Jun 2016 | CT#72 | CP-160215 | 0665 | 1 | Diameter requests for priority traffic during overload control mechanism | 13.2.0 | +| 07-2016 | | | | | Correction to spec version number on cover page | 13.2.1 | + +| | | | | | | | +|---------|-------|-----------|------|---|-------------------------------------------------------------------|--------| +| 09-2016 | CT#73 | CP-160431 | 0666 | 1 | S-CSCF Restoration during Registration enhancement | 14.0.0 | +| 2016-12 | CT#74 | CP-160646 | 0673 | 2 | Reference Location | 14.1.0 | +| 2016-12 | CT#74 | CP-160672 | 0674 | 1 | Service Profile and IFC alignment between XML and text/UML | 14.1.0 | +| 2016-12 | CT#74 | CP-160681 | 0675 | 1 | Load Control | 14.1.0 | +| 2016-12 | CT#74 | CP-160664 | 0677 | - | Correction to change IETF drmp draft version to official RFC 7944 | 14.1.0 | +| 2017-03 | CT#75 | CP-170045 | 0678 | - | Mission Critical Services | 14.2.0 | +| 2017-03 | CT#75 | CP-170048 | 0679 | 1 | Update of reference for the Diameter base protocol | 14.2.0 | +| 2017-06 | CT#76 | CP-171034 | 0680 | 1 | IMS Trace (ISAT) Reference Updates | 14.3.0 | +| 2017-06 | CT#76 | CP-171018 | 0684 | 1 | Support for signaling transport level packet marking | 14.3.0 | +| 2017-09 | CT#77 | CP-172012 | 0686 | - | Correction of DRMP Procedures | 14.4.0 | +| 2017-12 | CT#78 | CP-173011 | 0687 | 1 | Cx Subscriber Deregistration Reason | 14.5.0 | +| 2018-06 | CT#80 | CP-181121 | 0688 | 1 | Change of Reference Location Information | 15.0.0 | +| 2018-09 | CT#81 | CP-182069 | 0689 | - | P-CSCF restoration for 5GC | 15.1.0 | +| 2019-03 | CT#83 | CP-190035 | 0690 | 1 | Reference Location Information change | 15.2.0 | +| 2019-09 | CT#85 | CP-192094 | 0693 | 2 | draft-ietf-dime-load published as RFC 8583 | 15.3.0 | +| 2019-09 | CT#85 | CP-192150 | 0691 | 1 | Wildcarded Public Identity in SAA | 16.0.0 | +| 2019-12 | CT#86 | CP-193047 | 0694 | - | RLOS related registrations | 16.1.0 | + +--- \ No newline at end of file diff --git a/marked/Rel-16/29_series/29229/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/29_series/29229/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..058bcf45b33fa39b8c7d44e16613109dbaa81eb7 --- /dev/null +++ b/marked/Rel-16/29_series/29229/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8a55d7379cd857b71b94cf0d9e9941199eff8f1d6ebbc170c47a79977e18e44 +size 10052 diff --git a/marked/Rel-16/29_series/29229/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/29_series/29229/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c1e42e488dac25b10fddef3549a3c673eb9879c --- /dev/null +++ b/marked/Rel-16/29_series/29229/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc01960b0976602485c7c2c35ad4902055181cdb6f6a785dc2ef3ec3cca6517c +size 6459 diff --git a/marked/Rel-16/29_series/29229/raw.md b/marked/Rel-16/29_series/29229/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..9a339f55973e1a0635a079a427d5e90bc512a204 --- /dev/null +++ b/marked/Rel-16/29_series/29229/raw.md @@ -0,0 +1,1902 @@ + + +# 3GPP TS 29.229 V16.2.0 (2020-06) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Cx and Dx interfaces based on the Diameter protocol; Protocol details (Release 16)** + + + +The logo for LTE Advanced Pro, featuring the letters 'lte' in a bold, lowercase font. Above the 'e' is the text 'Advanced Pro' in a smaller font. To the right of the 'e' is a green signal icon consisting of three curved lines. + +LTE Advanced Pro logo + + + +The 3GPP logo, featuring the letters '3GPP' in a stylized, bold font. Below the 'P' is a red signal icon consisting of three curved lines. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, uppercase font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +
NOTE 3 | 6.3.37 | UTF8String | M | | | V | No | +| Digest-Algorithm | 111
NOTE 3 | 6.3.39 | UTF8String | M | | | V | No | +| Digest-QoP | 110
NOTE 3 | 6.3.40 | UTF8String | M | | | V | No | +| Digest-HA1 | 121
NOTE 3 | 6.3.41 | UTF8String | M | | | V | No | +| UAR-Flags | 637 | 6.3.44 | Unsigned32 | V | | | M | No | +| Loose-Route-Indication | 638 | 6.3.45 | Enumerated | V | | | M | No | +| SCSCF-Restoration-Info | 639 | 6.3.46 | Grouped | V | | | M | No | +| Path | 640 | 6.3.47 | OctetString | V | | | M | No | +| Contact | 641 | 6.3.48 | OctetString | V | | | M | No | +| Subscription-Info | 642 | 6.3.49 | Grouped | V | | | M | No | +| Call-ID-SIP-Header | 643 | 6.3.49.1 | OctetString | V | | | M | No | +| From-SIP-Header | 644 | 6.3.49.2 | OctetString | V | | | M | No | +| To-SIP-Header | 645 | 6.3.49.3 | OctetString | V | | | M | No | +| Record-Route | 646 | 6.3.49.4 | OctetString | V | | | M | No | +| Associated-Registered-Identities | 647 | 6.3.50 | Grouped | V | | | M | No | +| Multiple-Registration-Indication | 648 | 6.3.51 | Enumerated | V | | | M | No | +| Restoration-Info | 649 | 6.3.52 | Grouped | V | | | M | No | + +| | | | | | | | | | +|--------------------------------------|---------------|--------|------------|---|--|--|------|----| +| Session-Priority | 650 | 6.3.56 | Enumerated | V | | | M | No | +| Identity-with-Emergency-Registration | 651 | 6.3.57 | Grouped | V | | | M | No | +| Privileged-Sender-Indication | 652 | 6.3.58 | Enumerated | V | | | M | No | +| LIA-Flags | 653 | 6.3.59 | Unsigned32 | V | | | M | No | +| OC-Supported-Features | 621
NOTE 4 | 6.3.60 | Grouped | | | | M, V | No | +| OC-OLR | 623
NOTE 4 | 6.3.61 | Grouped | | | | M, V | No | +| Initial-CSeq-Sequence-Number | 654 | 6.3.62 | Unsigned32 | V | | | M | No | +| SAR-Flags | 655 | 6.3.63 | Unsigned32 | V | | | M | No | +| Allowed-WAF-WWSF-Identities | 656 | 6.3.64 | Grouped | V | | | M | No | +| WebRTC-Authentication-Function-Name | 657 | 6.3.65 | UTF8String | V | | | M | No | +| WebRTC-Web-Server-Function-Name | 658 | 6.3.66 | UTF8String | V | | | M | No | +| DRMP | 301
NOTE 5 | 6.3.67 | Enumerated | | | | M, V | No | +| Load | NOTE 6 | 6.3.68 | Grouped | | | | M, V | No | +| RTR-Flags | 659 | 6.3.69 | Unsigned32 | V | | | M | No | +| P-CSCF-Subscription-Info | 660 | 6.3.70 | Grouped | V | | | M | No | +| Registration-Time-Out | 661 | 6.3.71 | Time | V | | | M | No | + +NOTE 1: The AVP header bit denoted as 'M', indicates whether support of the AVP is required. The AVP header bit denoted as 'V', indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 6733 [28]. + +NOTE 1a: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit. + +NOTE 2: Depending on the concrete command. + +NOTE 3: The value of these attributes is defined in IETF RFC 4590 [20]. + +NOTE 4: The value of these attributes is defined in IETF RFC 7683 [23]. + +NOTE 5: The value of this attribute is defined in IETF RFC 7944 [26]. + +NOTE 6: The value of this attribute is defined in IETF RFC 8583 [27]. + +### 6.3.1 Visited-Network-Identifier AVP + +The Visited-Network-Identifier AVP is of type OctetString. This AVP contains an identifier that helps the HSS to identify the visited network (e.g. the visited network domain name). Coding of octets is H-PLMN operator specific. The I-CSCF maps a received P-Visited-Network-ID onto an Octet String value that is consistently configured in I-CSCF and HSS to uniquely identify the visited network. + +### 6.3.2 Public-Identity AVP + +The Public-Identity AVP is of type UTF8String. This AVP contains the public identity of a user in the IMS. The syntax of this AVP corresponds either to a SIP URL (with the format defined in IETF RFC 3261 [3] and IETF RFC 2396 [4]) or a TEL URL (with the format defined in IETF RFC 3966 [8]). Both SIP URL and TEL URL shall be in canonical form, as described in 3GPP TS 23.003 [13]. + +### 6.3.3 Server-Name AVP + +The Server-Name AVP is of type UTF8String. This AVP contains a SIP-URL (as defined in IETF RFC 3261 [3] and IETF RFC 2396 [4]), used to identify a SIP server (e.g. S-CSCF name). + +### 6.3.4 Server-Capabilities AVP + +The Server-Capabilities AVP is of type Grouped. This AVP contains information to assist the I-CSCF in the selection of an S-CSCF. + +AVP format + +Server-Capabilities ::=
This AVP is optionally present only when Server-Assignment-Type takes the value ADMINISTRATIVE_DEREGISTRATION or UNREGISTERED_USER. | + +Note: Bits not defined in this table shall be cleared by the sending S-CSCF and discarded by the receiving HSS. + +### 6.3.64 Allowed-WAF-WWSF-Identities AVP + +The Allowed-WAF-WWSF-Identities AVP is of type Grouped and contains the addresses of the WAFs and WWSFs allowed for the subscription. + +AVP format + +Allowed-WAF-WWSF-Identities ::= < AVP Header : 656 10415 > + +\*[ WebRTC-Authentication-Function-Name ] + +\*[ WebRTC-Web-Server-Function-Name ] + +\*[ AVP ] + +### 6.3.65 WebRTC-Authentication-Function-Name AVP + +The WebRTC-Authentication-Function-Name AVP is of type UTF8String and contains the address of a WAF allowed for the subscription. For the format of the string see IETF draft-holmberg-sipcore-auth-id-01 [25]. + +### 6.3.66 WebRTC-Web-Server-Function-Name AVP + +The WebRTC-Web-Server-Function-Name AVP is of type UTF8String and contains the address of a WWSF allowed for the subscription. For the format of the string see IETF draft-holmberg-sipcore-auth-id-01 [25]. + +### 6.3.67 DRMP AVP + +The DRMP AVP is of type Enumerated and it is defined in IETF RFC 7944 [26]. This AVP allows the HSS/SLF and the S-CSCF/I-CSCF to indicate the relative priority of Diameter messages. The DRMP AVP may be used to set the DSCP marking for transport of the associated Diameter message. + +### 6.3.68 Load + +The Load AVP is of type Grouped and it is defined in IETF RFC 8583 [27]. This AVP is used to support the Diameter load control mechanism. + +### 6.3.69 RTR-Flags + +The RTR-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 6.3.69.1. + +**Table 6.3.69.1: RTR-Flags** + +| Bit | Name | Description | +|-----|---------------------------------------|----------------------------------------------------------------------------------------------------| +| 0 | Reference Location Information change | This bit, when set, indicates the request is sent due to change of Reference Location Information. | + +NOTE: Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving I-CSCF. + +### 6.3.70 P-CSCF-Subscription-Info AVP + +The P-CSCF-Subscription-Info AVP is of type Grouped and it contains the P-CSCF's subscription information. The Contact AVP contains the Contact Address and Parameters in the Contact header of the subscription request. + +AVP format + +``` +P-CSCF-Subscription-Info ::= < AVP Header: 660, 10415> + { Call-ID-SIP-Header } + { From-SIP-Header } + { To-SIP-Header } + { Contact } + *[ AVP ] +``` + +### 6.3.71 Registration-Time-Out + +The Registration-Time-Out AVP is of type Time (see IETF RFC 6733 [28]), and contains the point of time at which the UE's registration expires. + +## 6.4 Use of namespaces + +This clause contains the namespaces that have either been created in this specification, or the values assigned to existing namespaces managed by IANA. + +### 6.4.1 AVP codes + +This specification assigns the AVP values from the AVP Code namespace managed by 3GPP for its Diameter vendor-specific applications. See clause 6.3 for the assignment of the namespace in this specification. + +### 6.4.2 Experimental-Result-Code AVP values + +This specification has assigned Experimental-Result-Code AVP values 2001-2005 and 5001-5011. See clause 6.2. + +### 6.4.3 Command Code values + +This specification assigns the values 300-305 from the range allocated by IANA to 3GPP in IETF RFC 3589 [12]. + +### 6.4.4 Application-ID value + +IANA has allocated the value 16777216 for the 3GPP Cx interface application. + +# 7 Special Requirements + +## 7.1 Version Control + +New functionality - i.e. functionality beyond the Rel-5 standard - shall be introduced by post-Rel-5 versions of this specification to the Diameter applications as follows: + +1. If possible, the new functionality shall be defined optional. +2. If backwards incompatible changes can not be avoided, the new functionality should be introduced as a feature, see 7.1.1. +3. If the change would be backwards incompatible even as if it was defined as a feature, a new version of the interface shall be created by changing the application identifier of the Diameter application, see 7.1.2. + +### 7.1.1 Defining a new feature + +The base functionality for the Cx is the 3GPP Rel-5 standard and a feature is an extension to that functionality. A feature is a functional entity that has a significant meaning to the operation of a Diameter application i.e. a single new parameter without a substantial meaning to the functionality of the Diameter endpoints should not be defined to be a new feature. If the support for a feature is defined mandatory in a post-Rel-5 versions of this specification, the feature concept enables interworking between Diameter endpoints regardless of whether they support all, some or none of the features of the application. Features should be defined so that they are independent from one another. + +The content of a feature shall be defined as a part of the specification of the affected application messages. If new AVPs are added to the commands because of the new feature, the new AVPs shall have the 'M' bit cleared and the AVP shall not be defined mandatory in the command ABNF. The support for a feature may be defined to be mandatory behaviour of a node. + +As an option to defining a feature, an extension to S-CSCF functionality for post-Rel-5 version may be defined as part of the list of mandatory capabilities that is used by the I-CSCF during the process of selecting an S-CSCF, as described in 3GPP TS 29.228 [1]. Any new feature should be taken into account in the definition of the list of mandatory and optional S-CSCF capabilities. Guidelines for the definition of S-CSCF Capabilities are described in 3GPP TS 29.228 [1]. + +The following table of features shall apply to the Cx interface. + +Table 7.1.1: Features of Feature-List-ID 1 used in Cx + +| Feature bit | Feature | M/O | Description | +|-------------|-------------------|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | SiFC | O |
Shared iFC sets
This feature is applicable for the SAR/SAA and PPR/PPA command pairs. If both the HSS and the S-CSCF support this feature, subsets of Initial Filter Criteria may be shared by several service profiles and the HSS shall download the shared iFC sets implicitly by downloading the unique identifiers of the shared iFC sets to the S-CSCF. By means of a locally administered database, the S-CSCF then maps the downloaded identifiers onto the shared iFC sets.
If the DSAI feature, as defined in 3GPP TS 29.328 [16], is also active with the shared iFC sets feature then the HSS shall behave as described below:
If the DSAI feature is active with the shared iFC sets feature and if all the iFCs bounding to a Shared iFC set are not masked by the DSAI, the HSS shall download the unique identifier of the shared iFC set to the S-CSCF. If some iFCs or all the iFCs bounding to a shared iFC set are masked by the DSAI, the HSS shall not download the identifier of the shared iFC set. Instead the HSS shall
- - download the remaining non masked iFCs of the shared iFC set explicitly or
- - download suitable identifiers of other shared iFC sets, i.e. those covering exactly the remaining non masked iFCs and which do not contain masked iFCs or
- - download a combination of identifiers of shared iFC sets and explicit iFCs which cover exactly the remaining non masked iFCs.
If the S-CSCF does not support this feature, the HSS shall not download identifiers of shared iFC sets. Instead as a default behavior the HSS shall (by means of a locally administered database) download the iFCs of a shared iFC set explicitly.
If the HSS does not support this feature, no special default behaviour is required for the S-CSCF.
Note: In using this feature option, the network operator is responsible for keeping the local databases in the S-CSCFs and HSSs consistent.
| +| 1 | AliasInd | M |Alias Indication
This feature is applicable for the SAR/SAA and PPR/PPA command pairs. If both the HSS and the S-CSCF support this feature, different aliases groups may be sent within the same service profile. Identities within the same service profile that are aliases shall be sent with identical alias group ID.
If the S-CSCF does not support this feature, the HSS shall send within the service profile only those identities that are aliases. Public User Identities that are not aliases of each other shall be sent in different service profiles even if these service profiles have exactly the same Core Network Service Authorization, Initial Filter Criteria, and Shared iFC Set information and these service profiles only differ in the contained Public User Identities. This is done in order to allow backwards compatibility since part of the handling of aliases in the S-CSCF was there before this indication was required and it applied to identities that share the same service profile and implicit registration set. In this case, the S-CSCF does not provide any additional treatment of aliases than that which existed before this indication was required.
If the HSS does not support this feature, no special default behaviour is required for the S-CSCF.
Note: All identities included in a single SAA or PPR command are always within one implicit registration set.
| +| 2 | IMSRestorationInd | O |IMS Restoration Indication
This feature is applicable for the UAR/UAA, LIR/LIA, SAR/SAA command pairs.
If both the HSS and the I-CSCF support this feature, in case the S-CSCF currently assigned in the HSS to the Public User Identity cannot be contacted the I-CSCF shall trigger the assignment of a new S-CSCF.
If both the HSS and the S-CSCF support this feature, the S-CSCF shall send S-CSCF Restoration Information to the HSS. The HSS shall send this information element in SAA to the S-CSCF when required.
If the S-CSCF does not support this feature, the HSS shall not send the IMS Restoration Information to the S-CSCF.
| + +| | | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 3 | P-CSCF-Restoration-mechanism | O | HSS-based P-CSCF Restoration mechanism.This feature is applicable for the SAR/SAA command pair.
If both the HSS and the S-CSCF support this feature, the S-CSCF shall send the P-CSCF-Restoration-Indication in SAR-Flags AVP to the HSS when required as described by 3GPP TS 23.380 [24] clause 5.4.
If the HSS does not support this feature, the S-CSCF shall not send the P-CSCF-Restoration-Indication to HSS. | +| Feature bit: The order number of the bit within the Supported-Features AVP, e.g. "1".
Feature: A short name that can be used to refer to the bit and to the feature, e.g. "MOM".
M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O").
Description: A clear textual description of the feature. | | | | + +The origin host may discover the supported features of the destination host with the dynamic discovery mechanism defined in 7.2 or via local O&M interfaces. + +### 7.1.2 Changing the version of the interface + +The version of an interface shall be changed by a future version of this specification only if there is no technically feasible means to avoid backwards incompatible changes to the Diameter application, i.e. to the current version of the interface. However, if the incompatible changes can be capsulated within a feature, there is no need to change the version of the interface. The versioning of an interface shall be implemented by assigning a new application identifier for the interface. This procedure is in line with the Diameter base protocol (see IETF RFC 3588) which defines that if an incompatible change is made to a Diameter application, a new application identifier shall be assigned for the Diameter application. + +The following table shall apply to the Cx interface, column Application identifier lists the used application identifiers on Cx and 3GPP. + +**Table 7.1.2: Application identifiers used in Cx** + +| Application identifier | First applied | +|------------------------|---------------| +| 16777216 | 3GPP Rel-5 | + +The origin host may discover which versions of an interface the destination host supports within the capabilities exchange (i.e. CER/CEA command), via the error messages defined in the chapter 7.3 or via local O&M interfaces. + +## 7.2 Supported features + +Features that are not indicated in the Supported-Features AVPs within a given application message shall not be used to construct that message. A request application message shall always be compliant with the list of supported features indicated in the Supported-Features AVPs within the application message. If a feature does not have an effect on constructing an application message, the message is by definition compliant with the feature. If no features are indicated in the application message, no features - i.e. no extensions to Rel-5 - shall be used to construct the application message. An answer application message shall always indicate in the Supported-Features AVPs the complete set of features supported by the sender of the answer application message. An answer application message shall be compliant with the features commonly supported by the sender of the request and answer application messages. + +The sender of a request application message shall discover for a given application message pair which features a destination host supports as described in 7.2.1. The discovered features of one command pair may be applicable to other command pairs within the application. Different commands within an application may support a different set of features. After discovering the features a destination host supports for a given application message pair, the sender of the request application message may store the information on the supported features of the destination host and it may use the features the destination host supports to construct the subsequent request application messages sent to the destination host. + +### 7.2.1 Dynamic discovery of supported features + +When sending a request application message to a destination host whose supported features the sender does not know, the request application message shall include the Supported-Features AVP containing the set of features required to + +process the request and generate the answer. An exception to this is where the origin host does not use any features to construct the request application message and it is not prepared to accept an answer application message which is constructed by making use of any features. For this exception the origin host need not include the Supported-Features AVP within the message. + +The Supported-Features AVP within a request application message shall always have the 'M' bit set and within an answer application message the AVP shall never have the 'M' bit set. An exception to this is where the origin host does not use any supported feature to construct the request application message but is prepared to accept an answer application message which is constructed by making use of supported features. For this exception it is optional for the origin host to set the 'M' bit of the Supported-Features AVP within the request application message. + +On receiving a request application message, the destination host shall do one of the following: + +- If it supports all features indicated in the Supported-Features AVPs within the request message, the answer application message shall include Supported-Features AVPs identifying the complete set of features that it supports. The Experimental-Result-Code AVP shall not be set to DIAMETER\_ERROR\_FEATURE\_UNSUPPORTED. +- If the request application message does not contain any Supported-Features AVPs, the answer application message shall include either Supported-Features AVPs identifying the complete set of features that it supports or, if it does not support any features, no Supported-Features AVPs shall be present. The Experimental-Result-Code AVP shall not be set to DIAMETER\_ERROR\_FEATURE\_UNSUPPORTED. +- If it does not support all the features indicated in the Supported-Features AVPs with the 'M' bit set, it shall return the answer application message with the Experimental-Result-Code AVP set to DIAMETER\_ERROR\_FEATURE\_UNSUPPORTED and it shall include also Supported-Features AVPs containing lists of all features that it supports. +- If it does not support Supported-Features AVP and it receives a request application message containing Supported-Features AVPs with the 'M' bit set, it will return the answer application message with the Result-Code AVP set to DIAMETER\_AVP\_UNSUPPORTED and a Failed-AVP AVP containing at least one Supported-Features AVP as received in the request application message. + +If an answer application message is received with the Experimental-Result-Code AVP set to DIAMETER\_ERROR\_FEATURE\_UNSUPPORTED or with the Result-Code AVP set to DIAMETER\_AVP\_UNSUPPORTED, the sender of the request application message may, based on the information in the received Supported-Features AVP or the lack of the AVP in the message, re-send the Diameter message containing only the common supported features. + +## 7.3 Interface versions + +The sender of the request application message may discover which versions of an interface a destination host supports together with the capabilities exchange (i.e. CER/CEA command pair) and with error mechanisms defined to the application messages in 7.3.1. The sender of the request application message should store information on all versions of the interface the destination host supports. The sender of the request application message should use the latest common version of the application supported by the destination host to send the request. + +If the receiver of the request application message itself or the versions of the interface it supports are not yet known, the sender of the request application message should use the latest supported version of the interface of the Diameter peer (i.e. Diameter proxy, redirect or relay agent) discovered during the capabilities exchange. If the Diameter peer is a redirect or relay agent, which advertises the 0xffffffff as an application identifier, the sender of the request application message shall use its own latest supported version of the interface when initiating the request. + +### 7.3.1 Discovery of supported interface versions + +When a Diameter agent receives a request application message and the Diameter agent doesn't find any upstream peer that would support the application identifier indicated in the request, the Diameter agent shall return the result code DIAMETER\_UNABLE\_TO\_DELIVER and it may also return the list of the application identifiers, which are supported by the destination host of the request application message. The supported application identifiers are carried in the answer application message in the Supported-Applications grouped AVP. + +Message format for the answer application message (based on the RFC 3588, clause 7.2) is as follows: + +``` +
For a static RTP payload type, the codec type should be implied by the RTP payload type, if not then each codec type shall be provided in a separate SDP "a=rtpmap"-line and possibly additional SDP "a=fmtp"-line(s). See Clause 10.2.
For a dynamic RTP payload type, for each codec information on the codec type shall be provided in a separate SDP "a=rtpmap"-line and possibly additional SDP "a=fmtp"-line(s). See Clause 10.2 | +| Coding | Local control | As for the property "GSM channel coding" in subclause 15. 2.1.1 | +| Connchng | ObservedEventDescriptor | As for the ObservedEventDescriptor "Connection State Change" in subclause 15.2.6.2 | +| Ctmbits | Statistics descriptor | As for the Statistics descriptor "Characters Transferred" in subclause 15.2.6.4 | +| Ctmstate | TerminationState | As for the TerminationState "Text termination connection state" in subclause 15. 2.6.1. | +| Ctmtext version | Local control | As for the property "Text Protocol Version" in subclause 15.2.6.1. | +| Ctmtransport | Local control | As for the property "Text Transport" in subclause 15.2.6.1. | +| Delay Variation Tolerance | Local Control | This is the tman/dvt property from ITU-T Recommendation H.248.53 [69] | +| Desired listener context terminations | Local control | As for the property "Number of desired listener context terminations" in subclause 15.2.10.1 | +| Diffserv Code Point | Local Control | Defined according to the Differentiated Services Code Point property in ITU-T Recommendation H.248.52 [70]. | +| Diffserv Tagging Behaviour | Local Control | Defined according to the Tagging Behaviour property in ITU-T Recommendation H.248.52 [70]. | +| Distlist | ObservedEvent descriptor | As for the ObservedEventDescriptor parameter "Distant TFO List" in subclause 15. 2.2.2 | +| ECN Enabled | Local Descriptor or Remote Descriptor | Defined according to the "ECN Enabled" property in ITU-T Recommendation H.248.82 [79]. | +| ECN Failure | Events, Observed Events | Defined according to the "ECN Failure" Event in ITU-T Recommendation H.248.82 [79]. | +| ECN Failure Type | ObservedEvents Descriptor | As for the ObservedEventsDescriptor Parameter "Failure Type" in ITU-T Recommendation H.248.82 [79]. | +| ECN Initiation Method | Local Descriptor or Remote Descriptor | Defined according to "Initiation Method" property in ITU-T Recommendation H.248.82 [79]. | +| Error | Error descriptor | As defined in the subclause "Command error code" in ITU-T Recommendation H.248.1 [10] | +| Flextone | Signal descriptor | As for the signal "Flexible Tone" in subclause 15.2.8.3 | +| ICE host candidate request | Local Descriptor | The "a=candidate" SDP attribute defined in IETF RFC 5245 [80] of type "host" with the transport, port and priority parameters with wildcard sign "\$" to request the allocation of a host candidate | +| ICE host candidate | Local Descriptor | The "a=candidate" SDP attribute defined in IETF RFC 5245 [80] | +| ICE lite indication | Local Descriptor | The "a=ice-lite" SDP attribute defined in IETF RFC 5245 [80]. | +| ICE password request | Local Descriptor | The "a=ice-pwd" SDP attribute defined in IETF RFC 5245 [80] with wildcard sign "\$". | +| ICE password | Local Descriptor | The "a=ice-pwd" SDP attribute defined in IETF RFC 5245 [80]. | +| ICE received candidate | Remote Descriptor | The "a=candidate" SDP attribute defined in IETF RFC 5245 [80] | +| ICE received password | Remote Descriptor | The "a=ice-pwd" SDP attribute defined in IETF RFC 5245 [80]. | +| ICE received Ufrag | Remote Descriptor | The "a=ice-ufrag" SDP attribute defined in IETF RFC 5245 [80]. | +| ICE Ufrag request | Local Descriptor | The "a=ice-ufrag" SDP attribute defined in IETF RFC 5245 [80] with wildcard sign "\$". | +| ICE Ufrag | Local Descriptor | The "a=ice-ufrag" SDP attribute defined in IETF RFC 5245 [80]. | +| ICE Connectivity Check Result | Events, Observed Events | Defined according to Connectivity Check Result event in ITU-T Recommendation H.248.50 [81]. | + +| | | | +|-----------------------------------------------|-----------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ICE Send Connectivity Check | Signals | Defined as the ostuncc/scc signal in ITU-T Recommendation H.248.50 [81]. | +| ICE New Peer Reflexive Candidate | Events, Observed Events | Defined according to New Peer Reflexive Candidate event in ITU-T Recommendation H.248.50 [81], only applicable for full ICE. | +| ICE Send Additional Connectivity Check | Signals | Defined as the ostuncc/sacc signal in ITU-T Recommendation H.248.50 [81], only applicable for full ICE. | +| IMEI(SV) | Local control | As for the property "IMEI(SV)" in subclause 15.2.9.1 | +| IMSI | Local control | As for the property "IMSI" in subclause 15.2.9.1 | +| inactivity timeout | EventDescriptor | As for the EventsDescriptor in subclause 6.2/H.248.14 "Inactivity Timeout" | +| Inactivity timeout | ObservedEvent descriptor | As for the ObserverdEventDescriptor in subclause 6.2/H.248.14 "Inactivity Timeout " | +| Initdirection | Local control | As for the property "Initialization Direction" in subclause 15.1.1.1 | +| Interface | Local control | As for the property "Interface" in subclause 15.1.1.1 | +| IP Address | Local Descriptor or Remote Descriptor |
Editor's note: the value for other services in FFS. | +| Priority Information | NA | Priority Indicator (subclause 6.1.1 of ITU-T Recommendation H.248.1 [10]).
Binary Encoding: Encoding as per ITU-T Recommendation H.248.1 [10] Annex A "priority" context attribute
Textual Encoding: Encoding as per ITU-T Recommendation H.248.1 [10] Annex B "priority" context attribute | +| Rate | ObservedEvent descriptor | As for the ObservedEventDescriptor parameter "Rate Change" in subclause 15. 2.1.2 | +| Realm Availability Change | Events, Observed Events | According to Available Realms Changed event in ITU-T Recommendation H.248.41 [72]. | +| Reduction | ObservedEvent descriptor | As for the ObserverdEventDescriptor in subclause 4.2.1/H.248.10 "MGCongestion". | +| Remote Source Address Filtering | Local Control | Defined according to Remote Source Address Filtering property in ITU-T Recommendation H.248.43 [67]. | + +| | | | +|----------------------------------------------------------|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Remote Source Address Mask | Local Control | Defined according to Remote Source Address Mask property in ITU-T Recommendation H.248.43 [67]. | +| Remote Source Port Filtering | Local Control | Defined according to Remote Source Port Filtering property in ITU-T Recommendation H.248.43 [67]. | +| Remote Source Port | Local Control | Defined according to Remote Source Port property in ITU-T Recommendation H.248.43 [67]. | +| Remote Source Port Range | Local Control | Defined according to Remote Source Port Range property in ITU-T Recommendation H.248.43 [67]. | +| RTCP allocation | Local Control | Defined according to RTCP Allocation Specific Behaviour property in ITU-T Recommendation H.248.57 [66]. | +| Reserve_Value | Local Control | ITU-T Recommendation H.248.1 [10] Mode property.
Binary Encoding: Encoding as per ITU-T Recommendation H.248.1 Annex A "reserveValue"
Textual Encoding: Encoding as per ITU-T Recommendation H.248.1 Annex B "reservedValueMode". | +| Result | ObservedEvent descriptor | As for the ObservedEventDescriptor parameter "Protocol Negotiation Result" in subclause 15. 2.1.2 | +| RtcpbwRR | Local Descriptor or Remote Descriptor |
Context ID = Null
Termination ID = Root
Service Change Reason =
MGW impending failure
Termination Taken out of service
Service Change Method =
Graceful / Forced | | + +Delay is not used. + +NOTE: The termination that is taken out of service is a Media Gateway. + +### 14.1.2 MGW Communication Up + +This procedure is the same as described in the subclause "BIWF Lost Communication" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. + +Use of time stamps is optional. + +Context Id value Null shall be used in this procedure. + +The ServiceChangeMGCId parameter may be returned in the MGW Communication Up response if the MGC does not wish to sustain an association with the MGW. If present in the response, the MGW shall not consider itself registered and should preferably attempt to re-register with the MGC specified in the ServiceChangeMgcID before any further alternate MGCs. + +### 14.1.3 MGW Restoration + +This procedure is the same as described in the subclause "BIWF Service Restoration Indication" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. + +**Table 14.1.3: MGW Restoration** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = Null
Termination ID = Root | | + +Delay is not used. + +The ServiceChangeMGCId parameter may be returned in the MGW Restoration response if the MGC does not wish to sustain an association with the MGW. If present in the response, the MGW shall not consider itself registered and should preferably attempt to re-register with the MGC specified in the ServiceChangeMgcID before any further alternate MGCs. + +### 14.1.4 MGW Register + +This procedure is the same as that described in the subclause "BIWF Registration" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. + +#### 14.1.4: MGW Register + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------|--------------------| +| | ServiceChangeProfile =
mcprofileName / version | | + +Use of time stamps is optional. + +Context Id value Null shall be used in this procedure. + +Non Standard Data is shall not be supported. + +Service Change Address shall not be used. + +The ServiceChangeMGCId parameter may be returned in the MGW Register response. If present in the Register response, the MGW shall not consider itself registered and should preferably attempt to re-register with the MGC specified in the ServiceChangeMgcID before any further alternate MGCs. + +### 14.1.5 MGW Re-register + +This procedure is the same as that described in the subclause "BIWF Re-Registration" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. + +##### Table 14.1.5.1: MGW Re-register + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------|--------------------| +| | ServiceChangeProfile =
mcprofileName / version | | + +Use of time stamps is optional. + +Context Id value Null shall be used in this procedure. + +Non Standard Data is shall not be supported. + +Service Change Address shall not be used. + +The ServiceChangeMGCId parameter may be returned in the MGW Re-register response. If present in the response, the MGW shall not consider itself registered and should preferably attempt to re-register with the MGC specified in the ServiceChangeMgcID before any further alternate MGCs. + +### 14.1.6 (G)MSC Server Ordered Re-register + +This procedure is the same as described in the subclause "CCU Ordered BIWF Re-registration" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarifications: + +Context Id value Null shall be used in this procedure. + +### 14.1.7 (G)MSC Server Restoration + +This procedure is the same as described in the subclause "CCU Initiated Service Restoration" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. + +**Table 14.1.7.1: (G)MSC Server Restoration** + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Context ID = Null
Termination ID =
Root
Service Change Reason =
Cold Boot / Warm Boot
Service Change Method = Restart | | + +Delay is not used. + +### 14.1.8 Termination Out-of-Service + +This procedure is the same as described in the subclause "BIWF Service Cancellation Indication" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarifications. This procedure may be used to inform the MSC Server of the Service State of Terminations after MGW Restart or Registration. + +**Table 14.1.8.1: ServiceChange.req (Termination Out-of-Service) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = Contexts / Null / All
Termination ID = ALL/Termination(s)
Service Change Reason = Transmission failure / Termination malfunctioning /
Loss of lower layer connectivity / Termination taken out of service
Service Change Method = Graceful / Forced
NOTE1: "All" shall refer to 1 TDM group. 1 TDM group is at a T1/E1. | | + +Delay is not used. + +The MGW shall delay initiating a TDM Termination Out-of-Service procedure till completion of any on-going Termination Restoration procedure for the same TDM termination, if any, unless the MGW considers the previous transaction request or reply lost, due to e.g. failure of the control association. + +The following table illustrates the allowed combinations that can be obtained with the ServiceChange Command: + +**Table 14.1.8.2: Combinations of ContextID and TerminationID in Termination Out-of- Service Procedure** + +| ContextID | TerminationID | Description | +|-----------|---------------|----------------------------------------------------------------------------------------------------------------------------------------| +| Specific | Specific | Service Change of a specific Termination in a specific Context | +| Null | Wildcard | Service Change of all matching TDM T1/E1 level terminations in the Null Context | +| Null | Specific | Service Change of a specific termination in the Null Context | +| All | Wildcard | Service Change of all matching TDM T1/E1 level terminations in specific (non-Null) contexts in which the terminations currently exist. | + +### 14.1.9 Termination Restoration + +This procedure is the same as described in the subclause "BIWF Service Restoration Indication" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. This procedure may be used to inform the MSC Server of the Service State of Terminations after MGW Restart or Registration and shall be used when individual trunks are commissioned. + +**Table 14.1.9.1: Termination Restoration** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = Contexts / Null / All
Termination ID = ALL/Termination(s)
Service Change Reason = Service Restored
Service Change Method = Restart
NOTE1: "All" shall refer to 1 TDM group. 1 TDM group is at a T1/E1. | | + +Delay shall not be used. + +The MGW shall delay initiating a TDM Termination Restoration procedure till completion of any on-going Termination Out-of-Service procedure for the same TDM termination, if any, unless the MGW considers the previous transaction request or reply lost, due to e.g. failure of the control association. + +The following table illustrates the allowed combinations that can be obtained with the ServiceChange Command: + +**Table 14.1.9.2: Combinations of ContextID and TerminationID in Termination Restoration Procedure** + +| ContextID | TerminationID | Description | +|-----------|---------------|----------------------------------------------------------------------------------------------------------------------------------------| +| Specific | Specific | Service Change of a specific Termination in a specific Context | +| Null | Wildcard | Service Change of all matching TDM T1/E1 level terminations in the Null Context | +| Null | Specific | Service Change of a specific termination in the Null Context | +| All | Wildcard | Service Change of all matching TDM T1/E1 level terminations in specific (non-Null) contexts in which the terminations currently exist. | + +### 14.1.10 Audit Value + +This procedure is the same as described in the subclause "Audit Values" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]), with the following clarifications. This procedure shall be used by the MSC Server to determine the service state of physical terminations when the MSC Server itself has restarted if it is subsequently unsure of the service state of terminations or when O&M procedures indicate new physical trunks have been commissioned to an in service MGW. It shall also be used for determining the Termination State after MGW Registration (Cold Boot) prior to unblocking devices in the network if the MSC Server has not been informed specifically by Termination Restoration or Termination Out Of Service Procedure. Table 14.1.10.1: AUD\_VAL.req (Audit\_Values) MGC to MGW + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| |
Transaction ID = z
Context ID = Null/Context ID/ALL
Termination ID =
Termination/Root/ALL(see NOTE1)
Audit Descriptor =
Empty/
IndAuditParameter:=
IndAudMediaDescriptor:=
TermStateDescriptor (NOTE3)
Packages (See NOTE2)
Audit Descriptor = IndAuditParameter:= IndAudMediaDescriptor:=
IndAudTerminationStateDescriptor:= SDPCapNeg Supported Capabilities (NOTE4)
NOTE1: "All" shall refer to 1 TDM group. 1 TDM group is at a T1/E1 level It shall not be used for ATM or IP termination.
"Termination" may be used for individual TDM, IP or ATM terminations.
NOTE2: Packages is for
- Null/Root Combination
NOTE3: Pre Rel6 this is performed with Audit Token
NOTE4: Used for auditing SDPCapNeg Extensions when SDPCapNeg signalling to the gateway is supported.
| | + +Upon reception of the command in the MGW: + +- The Service State returns the current Service State +- When Packages are requested, the Package Names and Versions are returned + +The following table illustrates the allowed combinations that can be obtained with the AuditValue Command: + +**Table 14.1.10.2: Combinations of AuditValue Command** + +| ContextID | TerminationID | Information Obtained | +|-----------|---------------|-------------------------------------------------------------------------------------------------| +| Specific | Wildcard | Audit of matching Terminations in a Context | +| Specific | Specific | Audit of a single Termination in a Context | +| Null | Root | Audit of Media Gateway state and events | +| Null | Wildcard | Audit of all matching TDM T1/E1 level Terminations in the null Context | +| Null | Specific | Audit of a single Termination outside of any Context | +| All | Wildcard | Audit of all matching TDM T1/E1 level Terminations and the Context to which they are associated | +| All | Specific | (Non-null) ContextID in which the Termination currently exists | + +**Table 14.1.10.3: AUD\_VAL.resp MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| |Transaction ID = z
Context ID = Null/Context ID/ALL
Termination ID =
Termination/Root/ALL(see NOTE1)
Audit Descriptor =
Empty/
IndAuditParameter:=
IndAudMediaDescriptor:=
TermStateDescriptor (NOTE3)
Packages (See NOTE2)
Audit Descriptor = IndAuditParameter:= IndAudMediaDescriptor:=
IndAudTerminationStateDescriptor:= SDPCapNeg Supported Capabilities (NOTE4)
NOTE1: "All" shall refer to 1 TDM group. 1 TDM group is at a T1/E1 level It shall not be used for ATM or IP termination.
"Termination" may be used for individual TDM, IP or ATM terminations.
NOTE2: Packages is for
- Null/Root Combination
NOTE3: Pre Rel6 this is performed with Audit Token
NOTE4: Used for auditing SDPCapNeg Extensions when SDPCapNeg signalling to the gateway is supported.
| | + +### 14.1.11 Audit Capability + +This procedure is the same as described in the subclause "Audit Capabilities" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). + +### 14.1.12 MGW Capability Change + +This procedure is the same as described in the subclause "BIWF Capability Change" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification:. + +For Capability changes concerning the whole MGW: + +Service Change Reason Media/Event or Signal Capability Failure shall not be used instead the following information shall be used: + +ServiceChange.req (MGW Capability Change) + +MGW to MGC + +**Table 14.1.12.1: MGW Capability Change** + +| Address Information | Control information | Bearer information | +|--------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Service Change Reason =Packages Change/ Capability Change
Service Change Info = changed package/property/signal/event/ statistics | | +| Note: The changed package/property/signal/event/ statistics information is FFS | | | + +### 14.1.13 (G)MSC Server Out of Service + +This procedure is the same as that described in the subclause "CCU Initiated Service Cancellation" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. + +**Table 14.1.13.1: (G)MSC Server Out of Service** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------|--------------------| +| | Service Change Reason = Termination taken out of service | | + +Delay shall not be used. + +### 14.1.14 MGW Resource Congestion Handling - Activate + +If the procedure "MGW Resource Congestion Handling - Activate" is required the following procedure is initiated. + +The MGC sends a MOD.req command with the following information. + +**Table 14.1.14.1: MOD.req(MGW Resource Congestion Handling - Activate) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = Null
Termination ID = Root
NotificationRequested (Event ID = x, "MGW Resource Congestion Handling - Indication") | | + +When the processing of command (1) is complete, the MGW initiates the following procedure. + +**Table 14.1.14.2: MOD.resp (MGW Resource Congestion Handling - Activate) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = Null
TerminationID = Root | | + +### 14.1.15 MGW Resource Congestion Handling - Indication + +If the procedure "MGW Resource Congestion Handling - Indication" is required, the following procedure is initiated: + +The MGW sends a NOT.req command with the following information. + +**Table 14.1.15.1: NOT.req (MGW Resource Congestion Handling - Indication) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = Null
Termination ID = Root
Event_ID (Event ID = x, "MGW Resource Congestion Handling - Indication (Reduction)") | | + +When the processing of command (1) is complete, the MGC initiates the following procedure. + +**Table 14.1.15.2: NOT.resp (MGW Resource Congestion Handling - Indication) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = Null
Termination ID = Root | | + +### 14.1.16 Continuity Check Tone + +This procedure is the same as described in Annex B.7.1.1 of ITU-T Recommendation Q.1950 [23] with the following clarification: + +The addition to "Prepare BNC Notify" defined in Annex B.7.1.1 of ITU-T Recommendation Q.1950 [23] shall be applied instead to "Reserve Circuit", as defined in Clause 13.2.2.1 + +Note: This does not preclude the use of the continuity check tone for other maintenance procedures. If the termination is audited it shall report state in service. + +### 14.1.17 Continuity Check Verify + +This procedure is the same as described in Annex B.7.2.1 of ITU-T Recommendation Q.1950 [23]. + +### 14.1.18 Continuity Check Response + +This procedure is the same as described in Annex B.7.1.2 of ITU-T Recommendation Q.1950 [23] with the following clarification: + +The addition to "Prepare BNC Notify" defined in Annex B.7.1.2 of ITU-T Recommendation Q.1950 [23] shall be applied instead to "Reserve Circuit", as defined in Clause 13.2.2.1 + +Note: This does not preclude the use of the continuity check response for other maintenance procedures. If the termination is audited it shall report state in service. + +### 14.1.19 Inactivity Timeout - Activate + +If the procedure "Inactivity Timeout - Activate" is required the following procedure is initiated. + +The MGC sends a MOD.req command with the following information. + +**Table 14.1.19.1: MOD.req (Inactivity Timeout - Activate) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = Null
Termination ID = Root
NotificationRequested (Event ID = x, "Inactivity Timeout - Indication") | | + +When the processing of command (1) is complete, the MGW initiates the following procedure. + +**Table 14.1.19.2: MOD.resp (Inactivity Timeout - Activate) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = Null
TerminationID = Root | | + +### 14.1.20 Inactivity Timeout – Indication + +When the procedure "Inactivity Timeout indication" is required the following procedure is initiated: the MGW sends a NOT.req command with the following information. + +**Table 14.1.20.1: NOT.req (Inactivity Timeout - Indication) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = NULL
Termination ID = Root
Event_ID (Event ID = x,
" Inactivity Timeout - Indication ") | | + +When the processing of command is complete, the MGC initiates the following procedure. + +**Table 14.1.20.2: NOT.resp (Inactivity Timeout - Indication) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = NULL
Termination ID = Root | | + +### 14.1. 21 Realm Availability Change – Activation + +The MGC sends a MODIFY request command as in Table 14.1.221.1. + +**Table 14.1.21.1: Realm Availability Change – Activation** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= -
Termination ID = ROOT
NotificationRequested (Event ID = x,
"Realm Availability Change") | | + +The MGW responds as in Table 14.1.21.2. + +**Table 14.1.21.2: Realm Availability Change – Activation Ack** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = -
Termination ID = ROOT | | + +### 14.1. 22 Realm Availability Change – Indication + +The MGW sends a NOTIFY request command as in Table 14.1.22.1. + +**Table 14.1.22.1: Realm Availability Change – Indication** + +| Address Information | Control information | Bearer information | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= -
Termination ID = ROOT
Event_ID (Event ID = x,
"Realm Availability Change
(Changed Realms)") | | +| NOTE: The ObservedEvent Parameters returned within the Changed Realms are defined as mandatory since it shall contain at minimum 1 parameter but may contain both Newly Available Realms and Newly Unavailable Realms. | | | + +The MGC responds as in Table 14.1.22.2 + +**Table 14.1.22.2: Realm Availability Change – Indication Ack** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = -
Termination ID = ROOT | | + +## 14.2 Call related H.248 transactions + +Table 14.2.1 shows the relationship between each call-related procedure in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) and the corresponding stage 2 procedure defined in 3GPP TS 23.205 [2], as well as specifying the requirement for support of each procedure on the Mc interface. + +**Table 14.2.1: Correspondence between ITU-T Recommendation Q.1950 [23] call-related transactions and 3GPP TS 23.205 [2], 3GPP TS 23.153 [1], 3GPP TS 23.231 [54] and 3GPP TS 29.292 [60] procedures** + +| Transaction used in Q.1950 | Procedure defined in 3GPP TS 23.205 [2], 23.153 [1], 23.231 [54] or 29.292 [60] | Support | Comments | +|---------------------------------------|---------------------------------------------------------------------------------|-----------|------------------------------------------------------------------------------| +| Change_Topology | Change Flow Direction | Mandatory | | +| Join | Join Bearer Termination | Mandatory | | +| Isolate | Isolate Bearer Termination | Mandatory | | +| Establish_BNC_Notify+(tunnel) | Establish Bearer | Mandatory | | +| Prepare_BNC_Notify+(tunnel) | Prepare Bearer | Mandatory | | +| Cut_Through | Change Through Connection | Mandatory | | +| Not defined in Q.1950 | Activate Interworking Function | Optional | | +| Cut_BNC (include several procedures). | Release Bearer (Release Bearer and Release termination) | Mandatory | | +| BNC Established | Bearer Established | Mandatory | | +| BNC Release | Bearer Released | Mandatory | | +| Insert_Tone | Send Tone | Mandatory | | +| Insert_Announcement | Play Announcement | Mandatory | | +| Signal Completion | Announcement Completed | Mandatory | | +| Detect_Digit | Detect DTMF | Mandatory | | +| Insert_Digit | Send DTMF | Mandatory | | +| Digit Detected | DTMF | Mandatory | | +| Confirm_Char | Confirm Char | Optional | | +| Modify_Char | Modify Char | Optional | | +| Reserve_Char | Reserve Char | Optional | | +| BNC Modified | Bearer Modified | Optional | | +| Echo Canceller | Activate Voice Processing Function | Mandatory | | +| BNC Modification failed | Bearer Modified Failed | Optional | | +| Tunnel (MGC-MGW) | Tunnel Information Down | Optional | Shall be supported for BICC associated Nb interface transport protocol on IP | +| Tunnel (MGW-MGC) | Tunnel Information Up | Optional | Shall be supported for BICC associated Nb interface transport protocol on IP | +| Insert_Tone | Stop Tone | Mandatory | | +| Insert_Announcement | Stop Announcement | Mandatory | | +| Detect_Digit | Stop DTMF Detection | Optional | | +| Insert_Digit | Stop DTMF | Mandatory | | +| Signal Completion | Tone Completed | Optional | | +| Not defined | Reserve Circuit | Mandatory | | +| Not defined | Command Rejected | Mandatory | | +| Not defined | TFO Activation | Optional | | +| Not defined | Codec Modify | Optional | | +| Not defined | Optimal Codec and Distant List_Notify | Optional | | +| Not defined | Distant Codec List | Optional | | +| Not defined | TFO status Notify | Optional | | +| Not defined | TFO status | Optional | | +| Modify_Char | Modify Bearer Characteristics | Mandatory | | +| Not defined | Rate Change | Optional | | +| Not defined | Bearer Modification Support | Optional | | +| Not defined | Protocol Negotiation Result | Optional | | +| Reserve_Char | Reserve Bearer Characteristics | Optional | | +| Confirm_Char | Confirm Bearer Characteristics | Optional | | +| ECS_Indication | Emergency Call Indication | Optional | | +| Continuity Check Tone | Continuity Check Tone | Optional | See 14.1.16 | +| Continuity Check Verify | Continuity Check Verify | Optional | See 14.1.17 | +| Continuity Check Response | Continuity Check Response | Optional | See 14.1.18 | +| Not Defined | Prepare IP Transport | Optional | Shall be supported if IP used on lu interface | +| Not Defined | Modify IP Transport Address | Optional | Shall be supported if IP used on lu interface | + +| | | | | +|-------------|-----------------------------------------------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------| +| Not defined | Termination heartbeat | Mandatory | To allow detection of hanging contexts and terminations in the MGW that may result e.g. from a loss of communication between the MSC-S and the MGW | +| Not Defined | Reserve RTP Connection Point | Optional | Required for SIP-I associated Nb and A interface over IP | +| Not Defined | Configure RTP Connection Point | Optional | Required for SIP-I associated Nb and A interface over IP | +| Not defined | Reserve and Configure RTP Connection Point | Optional | Required for SIP-I associated Nb and A interface over IP | +| Not defined | Media Inactivity Notification | Optional | See 14.2.55 | +| Not defined | ECN Failure Indication (NOTE 2) | Optional | Only applicable if ECN support is required | +| Not defined | ICE Connectivity Check Result Indication | Optional | Only applicable if full ICE is supported. | +| Not defined | ICE New Peer Reflexive Candidate Notification | Optional | Only applicable if full ICE is supported | + +NOTE 1: A procedure defined in table 3 can be combined with another procedure in the same action. This means that they can share the same contextID and termination ID(s). +NOTE 2: ECN support is only applicable for MSC enhanced for ICS. + +### 14.2.1 Change Flow Direction + +This procedure is the same as that defined in the subclause "Change Connection Topology" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following additions. + +**Table 14.2.1.1: Change Flow Direction request additions** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------------------------------------------------------|--------------------| +| | Context ID = c1,?
Connection Configuration =
(TerminationID= x1, ?
TerminationID=x2,?
[type = x]),... | | + +This procedure shall not be used for Multiparty bridge contexts. + +The Change Flow Direction response shall contain the Context ID. + +A command is only required if this procedure is combined with some other procedure which changes a termination functionality. + +### 14.2.2 Isolate Bearer Termination + +This procedure is the same as that defined in the subclause "Isolate" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). + +### 14.2.3 Join Bearer Termination + +This procedure is the same as that defined in the subclause "Join" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). + +### 14.2.4 Establish Bearer + +This procedure is the same as that defined in the subclause "Establish BNC\_notify" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) except that the Command MOV shall not be used, BNC events are requested optionally and independently and with additions as shown below. If IPBCP Tunnel Option 1 is required then the Command Response shall always precede the IPBCP Notify Command. + +**Table 14.2.4.1: Establish Bearer additions** + +| Address Information | Control information | Bearer information | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |
UP mode = Mode
UP version = version
Delivery of erroneous SDUs = value
Interface = interface
If support mode:
Initdirection = initdir
If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")
If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange")
If detection of hanging termination is requested:
(NOTE 3)
NotificationRequested (Event ID = x, "termination heartbeat")
If Listener context: number of desired listener context terminations = required listener context terminations
If multiple IP realms: IP realm Identifier = required IP realm identifier
If indication on BNC Established requested:
NotificationRequested (Event ID = x, "BNC Established")
If indication on BNC Modified requested:
NotificationRequested (Event ID = x, "BNC Modified")
If indication on BNC Mod Failed requested:
NotificationRequested (Event ID = x, "BNC Mod Failed")
If indication on BNC Release requested:
NotificationRequested (Event ID = x, "BNC Release")
If SCUDIF multimedia call :
MuMe codec (NOTE 1)
If data call other than SCUDIF multimedia call and Access Termination or Anchor MGW Network Termination:
PLMN bearer capability = PLMN capability (NOTE2)
If GSM data call other than SCUDIF multimedia call and (Anchor MGW Network Termination):
GSM channel coding = coding
NOTE1: Bearer Service Characteristics shall be excluded when this property is included.
NOTE2: Bearer Service Characteristics may be included.
NOTE3: Termination heartbeat notification shall be included when requesting a new bearer termination.
| | | + +### 14.2.5 Prepare Bearer + +This procedure is the same as that defined in the subclause "Prepare\_BNC\_notify" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) except that the Commands MOD and MOV shall not be used, the MGW shall not choose the BNC Characteristics, the BNC-cut-through-capability shall not be used, BNC events are requested optionally and independently and with additions as shown below. + +**Table 14.2.5.1: Prepare Bearer additions** + +| Address Information | Control information | Bearer information | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |UP mode = mode
UP version = version
Delivery of erroneous SDUs = value
Interface = interface
If support mode:
Initdirection = initdir
If CTM call and Access Termination:
State= ctmstate
Transport= ctmtransport
Version= ctmtext version
If data call and Non-Anchor MGW RAN-side termination:
Bitrate = bitrate (NOTE1)
If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")
If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange")
If indication on Bearer Modification requested:
NotificationRequested (Event ID = x, "Bearer Modification Support")
If notification on CTM negotiation result requested:
NotificationRequested (Event ID = x, "connchange ")
NotificationRequested (Event ID = x, "termination heartbeat")
If VGCS/VBS context: number of needed conference terminations = required conference terminations
If multiple IP realms:
IP realm Identifier = required IP realm identifier.
If indication on BNC Established requested:
NotificationRequested (Event ID = x, "BNC Established")
If indication on BNC Modified requested:
NotificationRequested (Event ID = x, "BNC Modified")
If indication on BNC Mod Failed requested:
NotificationRequested (Event ID = x, "BNC Mod Failed")
If indication on BNC Release requested:
NotificationRequested (Event ID = x, "BNC Release")
If SCUDIF multimedia call and (network termination or Anchor MGW Access Termination):
MuMe codec (NOTE2)
If data call other than SCUDIF multimedia call and (Anchor MGW Access Termination or Anchor MGW Network Termination):
PLMN bearer capability = PLMN capability (NOTE3)
If GSM data call other than SCUDIF multimedia call and Anchor MGW Network Termination:
GSM channel coding = coding
NOTE1 : Bearer Service Characteristics shall be excluded when this property is included except for the case when bitrate = 64000 and then Bearer Service Characteristics may be included. Bitrate is optional for transparent data calls when the data rate is 64k bits/s.
NOTE2: Bearer Service Characteristics shall be excluded when this property is included.
NOTE3: Bearer Service Characteristics shall be excluded when this property is included, except for Anchor MGW network termination for which it may be included.
| | | + +### 14.2.6 Change Through Connection + +This procedure is the same as that defined in the subclause "Cut Through" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification and deletion. + +NotificationRequested = (Event ID = x, "Cut Through") is deleted and therefore only the Explicit (MGC Controlled Cut-Through procedure is supported. + +The MGW may support No\_Data RTP frames on RTP-A and RTP-CN terminations during the call establishment phase, i.e. when not in TrFO (see 3GPP TS 26.102 [26]), in which case it shall support it independently of the Stream Mode. + +### 14.2.7 Activate Interworking Function + +When the procedure "Activate Interworking Function" is required the following procedure is initiated: + +The MGC sends a MOD.req command with the following information. + +**Table 14.2.7.1: MOD.req (Activate Interworking function) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = zContext ID = c1
Termination ID = bearer1
Signal=actpro
If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")
If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange") | | + +When the processing of command (1) is complete, the MGW initiates the following procedure. + +**Table 14.2.7.2: MOD.resp (Activate Interworking function) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
TerminationID = bearer1 | | + +### 14.2.8 Release procedures + +This subclause includes a number of procedures. + +#### 14.2.8.1 Release Bearer + +This procedure is the same as that defined in the subclause "Release" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) including the Modify command in the transaction with the clarification that the Termination ID and/or Context ID may be wildcarded (ALL). + +#### 14.2.8.2 Release Termination + +This procedure is the same as that defined in the subclause "Release" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) including a Subtract command in the transaction with the following additions. + +**Table 14.2.8.1 Sub.req (Release termination) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1/ALL
Termination ID = bearer1/ALL | | + +**Table 14.2.8.2.2: Sub.resp (Release termination) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1/ALL
Termination ID = bearer1/ALL
If requested
Statistics= Ctmbits | | + +### 14.2.9 Bearer Released + +This procedure is the same as that defined in the subclause "BNC Release" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification: + +Termination ID shall be provided in the response. . + +The MGW may, as a configurable option, inhibit the reporting of normal AAL2 bearer release on a Iu termination. + +### 14.2.10 Bearer Established + +This procedure is the same as that defined in the subclause "BNC Established" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification: + +Termination ID shall be provided in the response. + +### 14.2.11 Send Tone + +This procedure is the same as that defined in the subclause "Media Content Insertion" - "Insert Tone" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following additions. + +**Table 14.2.11.1: Send Tone additions** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | If CAMEL Prepaid Warning Tone
Signal = warning tone
Or
Signal = flextone
If detection of hanging termination is requested:
NotificationRequested (Event ID = x,
"termination heartbeat") | | + +Signal Direction shall be either "internal" or "external". + +Only the Tone Signal Ids shall be used, not the Tone Ids within the PlayTone Signal Id. + +The termination heartbeat event shall be configured when requesting a new ephemeral bearer termination. + +### 14.2.12 Play Announcement + +This procedure is the same as that defined in the subclause "Media Content Insertion" - "Insert Announcement" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarifications: + +**Table 14.2.12.1: Play Announcement additions** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------------------------------------------------------------|--------------------| +| | If detection of hanging termination is requested:
NotificationRequested (Event ID = x,
"termination heartbeat") | | + +Signal Direction shall be either "internal" or "external". + +Stream mode may be maintained as for the ongoing call or may be restricted to "send only". + +Signal Lists shall be supported. + +The termination heartbeat event shall be configured when requesting a new ephemeral bearer termination. + +### 14.2.13 Send DTMF + +This procedure is the same as that defined in the subclause "Media Content Insertion" - "Insert Digit" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). The MGW shall ensure the minimum duration timing and minimum interval timing is achieved in accordance with the DTMF timing defined in TS 23.014 [27]. Maximum duration shall also be controlled by the MGW if required by the network. + +### 14.2.14 Detect DTMF + +This procedure is the same as that defined in the subclause "Media Content Detection" - "Detect Digit" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the exception that "long tone detected" (Event Id ltd) shall not be used. In addition "start tone detected" (EventId std) is optional and if not supported shall result in the command error code #449 "Unsupported or Unknown Parameter or Property Value". If both a request for "start tone detected" and "end tone detected" is received by the MGW that does not support "start tone detected" then it shall only report a notification upon detecting the end of a digit. + +Parameter *Duration* shall not be used. + +All digits shall be requested i.e. Tone\_Id shall be wildcarded. + +### 14.2.15 Report DTMF + +This procedure is the same as that defined in the subclause "Detected Digit" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification: + +Termination ID shall be provided in the response. + +### 14.2.16 Announcement Completed + +This procedure is the same as that defined in the subclause "Signal Completion" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification: + +Termination ID shall be provided in the response. + +The Signal List ID should be provided additionally if the completed Announcement belongs to a Signal List. + +### 14.2.17 Activate Voice Processing Function + +When the procedure "Activate Voice Processing Function" (VPF) is required the following procedure is initiated: + +The MGC sends an ADD.req, MOD.req or MOV.req command with the following information. + +**Table 14.2.17.1: ADD.req/MOD.req/MOV.req (Activate Voice Processing Function) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1
ActivateVPF "ec"= on/off | | + +When the MGW receives the command, it shall associate the relevant voice processing function resources with the specified termination. + +When the processing of command (1) is complete, the MGW may initiate the "Voice Processing Function Ack" procedure. + +**14.2.17.2: ADD.resp/MOD.resp/MOV.resp (Voice Processing Function Ack) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1 | | + +### 14.2.18 Reserve Circuit + +This procedure is activated when the "Reserve Circuit" procedure is initiated. + +An ADD.req command is sent with the following information. + +**Table 14.2.18.1: ADD.req (Reserve\_Circuit) CSM to BIWF** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Transaction ID = z
Termination ID = bearer1
Context Requested:
Context ID = ?
Context Provided:
Context ID = c1
If CTM call and Access Termination:
State= ctmstate
Transport= ctmtransport
Version= ctmtext version
If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")
If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange")
If notification on CTM negotiation result requested:
NotificationRequested (Event ID = x, "connchange ")
If detection of hanging termination is requested:
NotificationRequested (Event ID = x, "termination heartbeat")
If indication on Bearer Released requested:
NotificationRequested (Event ID = x, "BNC Release (Cause)") – as defined in ITU-T Recommendation Q.1950 [23]
If Listener context: number of desired listener context terminations = required listener context terminations | Bearer Service Characteristics
If data call, Access Termination:
PLMN capabilities
If GSM data call, Access Termination:
GSM channel coding = coding | + +Upon completion of processing command (1) an ADD.resp command (2) is sent. + +**Table 14.2.18.2: ADD.resp BIWF to CSM** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
TerminationID = bearer1 | | + +### 14.2.19 Tunnel Information Up + +This procedure is the same as that defined in the subclause "Tunnel" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the clarification that BT/TunOpt = ? and BT/TunOpt = NO shall not be used. + +NOTE: This procedure is always initiated from the MGW. + +### 14.2.20 Tunnel Information Down + +This procedure is the same as that defined in the subclause "Tunnel" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the clarification that BT/TunOpt = ? and BT/TunOpt = NO shall not be used. + +NOTE: This procedure is always initiated from the MGC. + +### 14.2.21 Tone Completed + +This procedure is the same as that defined in the subclause "Signal.Completion" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification: + +Termination ID shall be provided in the response. + +### 14.2.22 Stop Announcement + +This procedure is the same as that defined in the subclause "Insert Announcement" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. The signal descriptor shall not include any signal. + +## 14.2.23 Stop Tone + +This procedure is the same as that defined in the subclause "Insert Tone" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. The signal descriptor shall not include any signal. + +## 14.2.24 Stop DTMF Detection + +This procedure is the same as that defined in the subclause "Detect Digit" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with the following clarification. The eventDescriptor shall not include any event. + +## 14.2.25 Stop DTMF + +This procedure is the same as that defined in the subclause "Media Content Insertion" - "Insert Digit" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). The signal descriptor shall not include any signal. The MGW shall ensure the minimum duration timing and minimum interval timing is achieved in accordance with the DTMF timing defined in TS 23.014 [27]. Maximum duration shall also be controlled by the MGW if required by the network. + +## 14.2.26 Confirm Char + +This procedure is the same as that defined in the subclause "Confirm Char" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). + +## 14.2.27 Modify Char + +This procedure is the same as that defined in the subclause "Modify Char" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). + +## 14.2.28 Reserve Char + +This procedure is the same as that defined in the subclause "Reserve Char" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). + +## 14.2.29 Bearer Modified + +This procedure is the same as that defined in the subclause "BNC Modified" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). + +## 14.2.30 Bearer Modification Failed + +This procedure is the same as that defined in the subclause "BNC Modification failure" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). + +## 14.2.31 TFO Activation + +When the procedure "TFO activation" is required the following procedure is initiated: + +The MGC sends a ADD.req, MOD.req or MOV.req command with the following information. + +**Table 14.2.31.1: ADD.req/MOD.req/MOV.req (TFO activation) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID =
bearer1
tfoenable = tfoactvalue
If TFO codec list:
Property= TFOcodecList | | + +When the processing of command (1) is complete, the MGW initiates the following procedure. + +**Table 14.2.31.2: ADD.resp/MOD.resp/MOV.resp (TFO activation) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
TerminationID=bearer1 | | + +## 14.2.32 Optimal Codec and Distant List\_Notify + +When the procedure "Optimal Codec and Distant List" is required the following procedure is initiated: + +The MGC sends a ADD.req, MOD.req or MOV.req command with the following information. + +**Table 14.2.32.1: ADD.req/MOD.req/MOV.req (Codec modify and distant list) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1
Property= TFOcodecList
NotificationRequested (Event ID = x, "Codec modify")
NotificationRequested (Event ID = x, "Distant List") | | + +When the processing of command (1) is complete, the MGW initiates the following procedure. + +**Table 14.2.32.2: ADD.resp/MOD.resp/MOV.resp (Optimal codec and codec list) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
TerminationID= bearer1 | | + +## 14.2.33 Codec Modify + +When the procedure "Codec Modify" is required the following procedure is initiated: + +The MGW sends a NOT.req command with the following information. + +**Table 14.2.33.1: NOT.req (Codec modify) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1
Event ( Event Id = x, "codec_modify (optimalcodec)") | | + +When the processing of command (1) is complete, the MGC initiates the following procedure. + +**Table 14.2.33.2: NOT.resp (Codec modify) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1 | | + +## 14.2.34 Distant Codec List + +When the procedure "Distant Codec List" is required the following procedure is initiated: + +The MGW sends a NOT.req command with the following information. + +**Table 14.2.34.1: NOT.req (Distant codec list) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1
Event(Event ID = x, " distant_codec_list(distlist) ") | | + +When the processing of command (1) is complete, the MGC initiates the following procedure. + +**Table 14.2.34.2: NOT.resp (Distant codec list) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1 | | + +## 14.2.35 Command Rejected + +When the procedure "Command Reject" is required the following procedure is initiated: + +The MGW/MGC sends .resp to any command.req with the following information. + +**Table 14.2.34.1: NYcommand.resp (command reject ) GW/MGC to MGC/MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1 or no context
Reason=Error | | + +## 14.2.36 Modify Bearer Characteristics + +This procedure is the same as that defined in the subclause "Modify Char" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with additions as shown below. + +**Table 14.2.36.1: Modify bearer Characteristics additions** + +| Address Information | Control information | Bearer information | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | If framing protocol used:
UP mode = mode
UPversion =version
Delivery of erroneous SDUs=value
Interface=interface
If support mode:
Initdirection=initdir
If data call and Non-Anchor MGW RAN-side termination:
Bitrate = bitrate (NOTE1)
If indication on Protocol Negotiation
Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")
If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange") | If SCUDIF multimedia call and (network termination or Anchor MGW Access Termination):
MuMe codec (NOTE 2)
If data call other than SCUDIF multimedia call and (Anchor MGW Access Termination or Anchor MGW Network Termination):
PLMN bearer capability = PLMN capability (NOTE3)
If GSM data call other than SCUDIF multimedia call and Anchor MGW Network Termination:
GSM channel coding=coding | +| NOTE1 : Bearer Service Characteristics shall be excluded when this property is included except for the case when bitrate = 64000 and then Bearer Service Characteristics may be included. Bitrate is optional for transparent data calls when the data rate is 64k bits/s.
NOTE2: Bearer Service Characteristics shall be excluded when this property is included.
NOTE3: Bearer Service Characteristics shall be excluded when this property is included, except for Anchor MGW network termination for which it may be included. | | | + +If the "Modify Bearer Characteristics" procedure contains a codec that is not currently in use at the Termination when it receives this procedure, and if the framing protocol is used in support mode, the MGW shall be prepared to handle a framing protocol initialisation. If the "Modify Bearer Characteristics" contains no codec or the codec that is already in use at the Termination when it receives this procedure, the MGW does not need to be prepared to handle a framing protocol initialisation. + +## 14.2.37 Protocol Negotiation Result + +When the procedure "Protocol Negotiation Result" is required the following procedure is initiated: + +The MGW sends a NOT.req command with the following information. + +**Table 14.2.37.1: NOT.req (Protocol negotiation result) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1
Event (Event ID = x, " protres (Result,Cause)") | | + +When the processing of command (1) is complete, the MGC initiates the following procedure. + +**Table 14.2.37.2: NOT.resp (Protocol negotiation result) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1 | | + +## 14.2.38 Rate Change + +When the procedure "Rate Change" is required the following procedure is initiated: + +The MGW sends a NOT.req command with the following information. + +**Table 14.2.38.1: NOT.req (Rate change) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1
Event (Event ID = x, "ratechg(rate)") | | + +When the processing of command (1) is complete, the MGC initiates the following procedure. + +**Table 14.2.38.2: NOT.resp (Rate change) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1 | | + +## 14.2.39 Bearer Modification Support + +When the procedure "Bearer Modification Support" is required, the following procedure is initiated: + +The MGW sends a NOT.req command with the following information to indicate that the bearer can be modified. + +**Table 14.2.39.1: NOT.req (Bearer Modification Support) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1
Event (Event ID = x, "mod_link_supp") | | + +When the processing of command (1) is complete, the MGC initiates the following procedure. + +**Table 14.2.39.2: NOT.resp (Bearer Modification Support) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1 | | + +## 14.2.40 CTM report + +When the procedure "CTM report" is required the following procedure is initiated: + +The MGW sends a NOT.req command with the following information. + +**Table 14.2.40.1: NOT.req (CTM report) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1
Event (Event ID = x, "connchange (connchnge
") | | + +When the processing of command (1) is complete, the MGC initiates the following procedure. + +**Table 14.2.40.2: NOT.resp (CTM report) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1 | | + +## 14.2.41 Prepare IP transport + +This procedure is activated when the "Prepare IP transport" procedure is initiated. + +An ADD.req command is sent with the following information. + +**Table 14.2.41.1: ADD.req (Prepare IP transport) MGC to MGW** + +| Address Information | Control information | Bearer information | +|-------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Local Descriptor {
lu IP Address
= ?
lu IP Port = ?
} | Transaction ID = z
Termination ID = ?
Logical Port ID = y
If Context Requested:
Context ID = ?
If Context Provided:
Context ID = c1
UP mode = mode
UP version = version
Delivery of erroneous SDUs = value
Interface = interface
If support mode:
Initdirection = initdir
If CTM call and Access Termination:
State= ctmstate
Transport= ctmtransport
Version= ctmtext version
If data call and Non-Anchor MGW RAN-side termination:
Bitrate = bitrate (NOTE1)
If indication of BNC Established requested:
Notification_Requested (Event ID = x, "BNC Connected")
If indication of BNC Release requested:
Notification_Requested (Event ID = x, "BNC Release (Cause)")
If indication of BNC Modified requested:
Notification_Requested (Event ID = x, "BNC Modified")
If indication of BNC Mod Failed requested:
Notification_Requested (Event ID = x, "BNC Mod Failed")
(all bearer change notifications as defined in ITU-T Recommendation Q.1950 [23])
If multiple IP realms:
IP realm Identifier = required IP realm identifier
NotificationRequested (Event ID = x, "termination heartbeat") | If SCUDIF multimedia call and Anchor MGW Access Termination:
MuMe codec (NOTE 2)
If data call other than SCUDIF multimedia call, Anchor MGW Access Termination:
PLMN bearer capability = PLMN capability (NOTE2)
If data call and Non-Anchor RAN termination:
Bearer Service Characteristics (NOTE 1)
If speech call, Access Termination: Codec
Bearer Characteristics = "IP" | + +NOTE1 : Bearer Service Characteristics shall be excluded when this property is included except for the case when bitrate = 64000 and then Bearer Service Characteristics may be included. Bitrate is optional for transparent data calls when the data rate is 64k bits/s.. + +NOTE2: Bearer Service Characteristics shall be excluded when this property is included. + +When the processing of command (1) is complete, the MGW initiates the following procedure. + +**Table 14.2.41.2: ADD.resp (Prepare IP transport) MGW to MGC** + +| Address Information | Control information | Bearer information | +|------------------------------------------------------------------------------|-------------------------------------------------------------------|--------------------| +| Local Descriptor {
lu IP Address = IPaddress
lu IP Port = UDPport
} | Transaction ID = z
Context ID = c1
Termination ID = bearer1 | | + +## 14.2.42 Modify IP transport address + +This procedure is activated when the "Modify IP transport address" procedure is initiated. + +A MOD.req command is sent with the following information. + +**Table 14.2.42.1: MOD.req (Modify IP transport address) MSC to MGW** + +| Address Information | Control information | Bearer information | +|-------------------------------------------------------------------------------|-------------------------------------------------------------------|--------------------| +| Remote Descriptor {
lu IP Address = IPaddress
lu IP Port = UDPport
} | Transaction ID = z
Context ID = c1
Termination ID = bearer1 | | + +When the processing of command (1) is complete, the MGW initiates the following procedure. + +**Table 14.2.42.2: MOD.resp (Modify Ip transport address) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
TerminationID=bearer1 | | + +## 14.2.43 Reserve Bearer Characteristics + +This procedure is the same as that defined in the subclause "Reserve Char" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with additions as shown below. + +**Table 14.2.43.1: Reserve Bearer Characteristics additions** + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | If framing protocol used:
UP mode = mode
UPversion =version
Delivery of erroneous
SDUs=value
Interface=interface
Initdirection=initdirection | | + +If the "Reserve Bearer Characteristics" procedure contains a codec that is not currently in use at the Termination when it receives this procedure, and if the framing protocol is used in support mode, the MGW shall be prepared to handle a framing protocol initialisation. If the "Reserve Bearer Characteristics" contains no codec or the codec that is already in use at the Termination when it receives this procedure, the MGW does not need to be prepared to handle a framing protocol initialisation. + +## 14.2.44 Confirm Bearer Characteristics + +This procedure is the same as that defined in the subclause "Confirm Char" in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]) with additions as shown below. + +**Table 14.2.44: Confirm Bearer Characteristics additions** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | If framing protocol used:
UP mode = mode
UPversion =version
Delivery of erroneous SDUs=value
Interface=interface
Initdirerection=initdirection | | + +If the "Confirm Bearer Characteristics" procedure contains a codec that is not currently in use at the Termination when it receives this procedure, and if the framing protocol is used in support mode, the MGW shall be prepared to handle a framing protocol initialisation. If the "Confirm Bearer Characteristics" contains no codec or the codec that is already in use at the Termination when it receives this procedure, the MGW does not need to be prepared to handle a framing protocol initialisation. + +## 14.2.45 Trace activation/deactivation + +This procedure is activated when the "Trace activation/deactivation" procedure is initiated. + +An ADD.req command is sent with the following information. + +**Table 14.2.45.1: ADD.req/MOD.req (Trace activation/deactivation) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Termination ID = bearer1
Context ID = c1
Trace Reference
Trace Recording Session Reference
Trace Depth
Triggering events
List of interfaces
IMSI
IMEI(SV)
Trace activity control = trace activity request
If indication on Trace Activation Result requested:
NotificationRequested (Event ID = x, "Trace activation result") | | + +Upon completion of processing command (1) an ADD.resp or MOD.resp command (2) is sent. + +**Table 14.2.45.2: ADD.resp/MOD.resp/ MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
TerminationID = bearer1 | | + +## 14.2.46 Trace Activation result notification + +When the procedure "Trace Activation result notification" is required, the following procedure is initiated: + +The MGW sends a NOT.req command with the following information to indicate the result of the trace activation. + +**Table 14.2.46.1: NOT.req (Trace Activation result Notification) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1
Event_ID (Event ID = x, " tracact (res)") | | + +When the processing of command (1) is complete, the MGC initiates the following procedure. + +**Table 14.2.46.2: NOT.resp (Trace Activation result Notification) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID =
bearer1 | | + +## 14.2.47 Emergency Call Indication + +This procedure is the same as that defined in the subclause " ECS\_Indication " in ITU-T Recommendation Q.1950 Annex F [23] (see 3GPP TS 29.205 [7]) with additions as shown below. + +**Table 14.2.47.1: Emergency Call Indication additions** + +| Address Information | Control information | Bearer information | +|----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------| +| Or as per flow 14.2.4
Establish Bearer | Or as per flow 14.2.4
Establish Bearer
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication | Or as per flow 14.2.4
Establish Bearer | +| Or as per flow 14.2.5
Prepare Bearer | | Or as per flow 14.2.5
Prepare Bearer | +| Or as per flow 14.2.12
Play Announcement | Or as per flow 14.2.5
Prepare Bearer
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication | Or as per flow 14.2.12
Play Announcement | +| Or as per flow 14.2.18
Reserve_Circuit | | Or as per flow 14.2.18
Reserve_Circuit | +| Or as per flow 14.2.41
Prepare_IP_transport | Or as per flow 14.2.12
Play Announcement
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication | Or as per flow 14.2.41
Prepare_IP_transport | +| Or as per flow 14.2.2
Isolate Bearer Termination | | Or as per flow 14.2.2
Isolate Bearer Termination | +| Or as per flow 14.2.3
Join Bearer Termination | Or as per flow 14.2.18
Reserve_Circuit
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication | Or as per flow 14.2.3
Join Bearer Termination | +| Or as per flow 14.2.51
Reserve RTP Connection Point | | Or as per flow 14.2.51
Reserve RTP Connection Point | +| Or as per flow 14.2.53
Reserve and Configure RTP Connection Point | Or as per flow 14.2.41
Prepare_IP_transport
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication | Or as per flow 14.2.53
Reserve and Configure RTP Connection Point | +| | Or as per flow 14.2.2
Isolate Bearer Termination
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication | | +| | Or as per flow 14.2.3
Join Bearer Termination
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication | | +| | Or as per flow 14.2.51
Reserve RTP Connection Point
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication | | +| | Or as per flow 14.2.53
Reserve and Configure RTP Connection Point
With the following additions:
If Context Requested & Emergency Call:
Emergency Call Indication | | + +## 14.2.48 TFO status Notify + +When the procedure "TFO status notify" is required the following procedure is initiated: + +The MGC sends a ADD.req, MOD.req or MOV req. command with the following information. + +**Table 14.2.48.1: ADD.req/MOD.req/MOV.req (TFO status) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1
NotificationRequested (Event ID = x, "TFO Status") | | + +The support of the TFO status notification is optional in the TFO package. If supported, when the processing of command (1) is complete, the MGW initiates the following procedure. + +**Table 14.2.48.2: ADD.resp/MOD.resp/MOV.resp (TFO status) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
TerminationID= bearer1 | | + +Otherwise it returns an error codec to the MGC indicating that the requested event is unsupported or unknown., as specified in ITU-T Recommendation H.248.8 [14]. + +## 14.2.49 TFO Status + +When the procedure "TFO Status" is required the following procedure is initiated: + +The MGW sends a NOT.req command with the following information. + +**Table 14.2.49.1: NOT.req (TFO Status) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1
Event_ID (Event ID = x, " TFO_status(tfostatus) ") | | + +When the processing of command (1) is complete, the MGC initiates the following procedure. + +**Table 14.2.49.2: NOT.resp (TFO Status) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|-------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1 | | + +## 14.2.50 Termination heartbeat indication + +When the procedure "Termination heartbeat indication" is required the following procedure is initiated: the MGW sends a NOT.req command with the following information. + +**Table 14.2.50.1: NOT.req (Termination heartbeat) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID = bearer1
Event_ID (Event ID = x,
"termination heartbeat") | | + +When the processing of command is complete, the MGC initiates the following procedure. + +**Table 14.2.50.2: NOT.resp (Termination heartbeat) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|----------------------------------------------------------------------|--------------------| +| | Transaction ID = z
Context ID = c1
Termination ID =
bearer1 | | + +The heartbeat timer shall be configured to a value much greater than the mean call holding time. + +The MSC-S is in charge of correcting any detected mismatch, by subtracting hanging terminations or clearing hanging contexts. + +## 14.2.51 Reserve RTP Connection Point + +This procedure is used to reserve an RTP bearer termination for a SIP-I associated Nb user plane, as defined in 3GPP TS 29.414 [32], or for a A interface over IP termination, as defined in 3GPP TS 3GPP TS 48.103 [65]. When the procedure "Reserve RTP Connection Point" is required the following procedure is initiated. + +The MGC sends an ADD.req command with the following information. + +**Table 14.2.51.1: ADD.req (Reserve RTP Connection Point Request) MGC to MGW** + +| Address Information | Control information | Bearer information | +|------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Local Descriptor {
Port = ?
IP Address = ?
IP Version = IPv4 or IPv6
} | Transaction ID = z
Termination ID = ?
If Context Requested:
Context ID = ?
If MPS call/session:
Priority Indicator = x
If Context Provided:
Context ID = c1
If IP Interface Type:
IP interface = "IP interface type"
If CTM call and Access Termination:
State= ctmstate
Transport= ctmtransport
Version= ctmtext version
If Resources for multiple Codecs shall be reserved:
Reserve_Value
NotificationRequested (Event ID = x, "termination heartbeat")
If indication on Bearer Released requested:
NotificationRequested (Event ID = x, "BNC Release (Cause)") – as defined in ITU-T Recommendation Q.1950
If multiple IP realms: IP realm Identifier = required IP realm identifier
If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")
If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange")
If access termination and notification on CTM negotiation result requested:
NotificationRequested (Event ID = x, "connchange ")
If access termination and Listener context: number of desired listener context terminations = required listener context terminations
If diffserv required (NOTE 1):-
Diffserv Code Point
If tagging behaviour
Diffserv Tagging Behaviour
If Remote Source Address Filtering required (NOTE 1):-
Remote Source Address Filtering
If Remote Source Address range required:-
Remote Source Address Mask
If Remote Source Port Filtering required:-
Remote Source Port Filtering
If individual port:-
Remote Source Port
If range of ports: | Local Descriptor {
Codec List
RTP Payloads
RtcpbwRS
RtcpbwRR
If ICE is applied:
ICE host candidate request
ICE password request
ICE Ufrag request
If SDPCapNeg is signalled to the gateway:
SDPCapNeg configuration
}
If data call other than SCUDIF multimedia call and if Access Termination or Anchor MGW Network Termination:
PLMN bearer capability =
PLMN capability
If GSM data call other than SCUDIF multimedia call and if Access Termination or Anchor MGW Network Termination:
GSM channel coding = coding | + +| | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| |
Remote Source Port Range
If Media Inactivity Detection Required (NOTE 1):
NotificationRequested (Event ID = x, "Media Inactivity Detection (Media Inactivity Detection Time, Media Inactivity Detection Direction) ") (NOTE 2)
If Sustainable Data Rate Policing Required (NOTE 1):-
Policing Required
Sustainable Data Rate
Maximum Burst Size
If peak data rate policing (NOTE 1)
Policing Required
Peak Data Rate
If Delay Variation required
Delay Variation Tolerance
If RTCP handling required (NOTE 1):
RTCP allocation
If ECN Endpoint support required
ECN Enable = "True"
Initiation Method = "ECN Initiation Method"
If notification of ECN Failure
Report:
NotificationRequested (Event ID = x, "ECN Failure")
If ICE is applied:
STUN server request
NOTE 2: The event parameters "Media Inactivity Detection Time" and "Media Inactivity Detection Direction" are optional. | | | + +When the processing of command (1) is complete, the MGW initiates the following procedure. + +**Table 14.2.51.2: ADD.resp (Reserve RTP Connection Point Acknowledge) MGW to MGC** + +| Address Information | Control information | Bearer information | +|-------------------------------------------------------------|------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Local Descriptor {
Port
IP Address
IP Version
} | Transaction ID
Termination ID
Context ID | Local Descriptor {
Codec List
RTP Payloads
RtcpbwRS
RtcpbwRR
If ICE is applied:
ICE host candidate
ICE password
ICE Ufrag
If ICE lite implementation
ICE lite indication
If SDPCapNeg is signalled to the gateway:
SDPCapNeg configuration
} | + +## 14.2.52 Configure RTP Connection Point + +This procedure is used to configure or reconfigure an RTP bearer termination for a SIP-I associated Nb user plane, as defined in 3GPP TS 29.414 [32], or for a A interface over IP termination, as defined in 3GPP TS 48.103 [65]. + +When the procedure "Configure RTP Connection Point" is required the following procedure is initiated: + +The MGC sends an MOD.req command with the following information. + +**Table 14.2.52.1: MOD.req (Configure RTP Connection Point Request) MGC to MGW** + +| Address Information | Control information | Bearer information | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| If local resources are modified:
Local Descriptor {
Port
IP Address
IP Version
}
If remote resources are modified:
Remote Descriptor {
Port
IP Address
IP Version
} | Transaction ID
Termination ID
Context ID
If IP Interface Type:
IP interface = "IP interface type"
(NOTE 1)
If Resources for multiple Codecs shall be reserved:
Reserve_Value
If CTM call and Access Termination:
State= ctmstate
Transport= ctmtransport
Version= ctmtext version
If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")
If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange")
If access termination and notification on CTM negotiation result requested:
NotificationRequested (Event ID = x, " connchange ")
If access termination and Listener context: number of desired listener context terminations = required listener context terminations
If diffserv required (NOTE 2):-
Diffserv Code Point
If tagging behaviour
Diffserv Tagging Behaviour
If Remote Source Address Filtering required (NOTE 2):
Remote Source Address Filtering
If Remote Source Address range required:-
Remote Source Address Mask
If Remote Source Port Filtering required:-
Remote Source Port Filtering
If individual port:-
Remote Source Port
If range of ports:
Remote Source Port Range
If Media Inactivity Detection Required (NOTE 2):
NotificationRequested (Event ID = x, "Media Inactivity Detection (Media Inactivity Detection Time, Media Inactivity Detection Direction) ")
(NOTE 3)
If Sustainable Data Rate Policing Required (NOTE 2):-
Policing Required
Sustainable Data Rate
Maximum Burst Size
If peak data rate policing (NOTE 2)
Policing Required
Peak Data Rate
If Delay Variation required
Delay Variation Tolerance | If local resources are modified:
Local Descriptor {
Codec List
RTP Payloads
RtcpbwRS
RtcpbwRR
If SDPCapNeg is signalled to the gateway:
SDPCapNeg configuration
}
If remote resources are modified:
Remote Descriptor {
Codec List
RTP Payloads
RtcpbwRS
RtcpbwRR
If RTCP APP messages allowed
Allowed RTCP APP message types
If ICE is applied:
ICE received candidate
ICE received password
ICE received Ufrag
(NOTE 4)
If SDPCapNeg is signalled to the gateway:
SDPCapNeg configuration
}
If data call other than SCUDIF multimedia call and if Access Termination or Anchor MGW Network Termination:
PLMN bearer capability = PLMN capability
If GSM data call other than SCUDIF multimedia call and if Access Termination or Anchor MGW Network Termination:
GSM channel coding = coding | + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| |
If RTCP handling required (NOTE 2):
RTCP allocation
If ECN Endpoint support required
ECN Enable = "True"
Initiation Method = "ECN Initiation Method"
If notification of ECN Failure
Report:
NotificationRequested (Event ID
= x,"ECN Failure")
NOTE 1: If this property is included within the Reserve Connection Point procedure or the Reserve and Configure RTP Connection Point then it shall not be modified by this procedure.
NOTE 2: Only for terminations with border control functions support.
NOTE 3: The event parameters "Media Inactivity Detection Time" and "Media Inactivity Detection Direction" are optional.
NOTE 4: The support of ICE received candidate, ICE received password, ICE received Ufrag are optional for ICE lite, as specified in 3GPP TS 29.292 [60].
If local resources were provided in request:
Local Descriptor {
Port
IP Address
IP Version
}
If remote resources were provided in request:
Remote Descriptor {
Port
IP Address
IP Version
} NOTE
Transaction ID
Context ID
Termination ID
If local resources were provided in request:
Local Descriptor {
Codec List
RTP Payloads
RtcpbwRS
RtcpbwRR
}
If remote resources were provided in request:
Remote Descriptor {
Codec List
RTP Payloads
RtcpbwRS
RtcpbwRR
} NOTE
Port = ?
IP Address = ?
IP Version = IPv4 or IPv6
}
Remote Descriptor {
Port
IP Address
IP Version = IPv4 or IPv6
} | Transaction ID
Termination ID = ?
If Context Requested:
Context ID = ?
If MPS call/session:
Priority Indicator = x
If Context Provided:
Context ID = c1
If IP Interface Type:
IP interface = "IP interface type"
If Resources for multiple Codecs shall be reserved:
Reserve_Value
If CTM call and Access Termination:
State= ctmstate
Transport= ctmtransport
Version= ctmtext version
NotificationRequested (Event ID = x, "termination heartbeat")
If indication on Bearer Released requested:
NotificationRequested (Event ID = x, "BNC Release (Cause)") – as defined in ITU-T Recommendation Q.1950
If multiple IP realms: IP realm Identifier = required IP realm identifier
If indication on Protocol Negotiation Result requested:
NotificationRequested (Event ID = x, "Prot Negotiation Result")
If indication on Rate Change requested:
NotificationRequested (Event ID = x, "RateChange")
If access termination and notification on CTM negotiation result requested:
NotificationRequested (Event ID = x, " connchange ")
If diffserv required (NOTE 1):-
Diffserv Code Point
If tagging behaviour
Diffserv Tagging Behaviour
If Remote Source Address Filtering required (NOTE 1):-
Remote Source Address Filtering
If Remote Source Address range required:-
Remote Source Address Mask
If Remote Source Port Filtering required:-
Remote Source Port Filtering
If individual port:-
Remote Source Port
If range of ports:
Remote Source Port Range
If Media Inactivity Detection Required (NOTE 1):
NotificationRequested (Event ID = x, "Media Inactivity Detection (Media Inactivity Detection Time, Media Inactivity Detection Direction) ") (NOTE2) | Local Descriptor {
Codec List
RTP Payloads
RtcpbwRS
RtcpbwRR
If ICE is applied:
ICE host candidate request
ICE password request
ICE Ufrag request
If SDPCapNeg is signalled to the gateway:
SDPCapNeg configuration
}
Remote Descriptor {
Codec List
RTP Payloads
RtcpbwRS
RtcpbwRR
If RTCP APP messages allowed
Allowed RTCP APP message types
If ICE is applied:
ICE received candidate
ICE received password
ICE received Ufrag
(NOTE 3)
If SDPCapNeg is signalled to the gateway:
SDPCapNeg configuration
}
If data call other than SCUDIF multimedia call and Anchor MGW Network Termination:
PLMN bearer capability =
PLMN capability
If GSM data call other than SCUDIF multimedia call and Anchor MGW Network Termination:
GSM channel coding = coding | + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| |
If Sustainable Data Rate Policing Required (NOTE 1):-
Policing Required
Sustainable Data Rate
Maximum Burst Size
If peak data rate policing (NOTE 1)
Policing Required
Peak Data Rate
If Delay Variation required
Delay Variation Tolerance
If RTCP handling required (NOTE 1):
RTCP allocation
If ECN Endpoint support required
ECN Enable = "True"
Initiation Method = "ECN Initiation Method"
If notification of ECN Failure
Report:
NotificationRequested (Event ID
= x,"ECN Failure")
Port
IP Address
IP Version
}
Remote Descriptor {
Port
IP Address
IP Version
} NOTE | Transaction ID
Termination ID
Context ID | Local Descriptor {
Codec List
RTP Payloads
RtcpbwRS
RtcpbwRR
If ICE is applied:
ICE host candidate
ICE password
ICE Ufrag
If ICE lite implementation
ICE lite indication
If SDPCapNeg is signalled to the gateway:
SDPCapNeg configuration
}
Remote Descriptor {
Codec List
RTP Payloads
RtcpbwRS
RtcpbwRR
If SDPCapNeg is signalled to the gateway:
SDPCapNeg configuration
} NOTE | +| NOTE: Sending of the Remote Descriptor is optional | | | + +Editor's note: The usage of the Call Type Discrimination IE and Text Telephony IE is ffs. + +## 14.2.54 ECN Failure Indication + +The MGW sends a NOTIFY request command as in Table 14.2.54.1. + +**Table 14.2.54.1: ECN Failure Indication** + +| Address Information | Control information | Bearer information | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= C1
Termination ID = T1
Event_ID (Event ID = x,
"ECN Failure (ECN Failure Type)") | | + +The MGC responds as in Table 14.2.54.2 + +**Table 14.2.54.2: ECN Failure Indication Ack** + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = C1
Termination ID = T1 | | + +## 14.2.55 Media Inactivity Notification + +When the procedure "Media Inactivity Notification" is required the following procedure is initiated: the MGW sends a NOT.req command with the following information. + +**14.2.55.1 NOT.req (Media Inactivity) MGW to MGC** + +| Address Information | Control information | Bearer information | +|---------------------|------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = C1
Termination ID = T1
Event_ID (Event ID = x, "Media
Inactivity Detection") | | + +When the processing of command is complete, the MGC initiates the following procedure. + +**14.2.55.2 NOT.resp (Media Inactivity) MGC to MGW** + +| Address Information | Control information | Bearer information | +|---------------------|--------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID = C1
Termination ID = T1 | | + +## 14.2.56 ICE Connectivity Check Result Notification + +The MGW sends a NOTIFY request command as defined in Table 14.2.56.1. + +**Table 14.2.56.1: ICE Connectivity Check Result Notification** + +| Address Information | Control information | Bearer information | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| | Transaction ID = x
Context ID= C1
Termination ID = T1
Event_ID (Event ID = x,
" Connectivity Check Result
(Candidate/Transport Pair)") | | + +The MSC Server responds as defined in Table 14.2.56.2 + +**Table 14.2.56.2: ICE Connectivity Check Result Notification Ack** + +| Address Information | Control information | Bearer information | +|----------------------------|--------------------------------------------------------------|---------------------------| +| | Transaction ID = x
Context ID = C1
Termination ID = T1 | | + +## 14.2.57 ICE New Peer Reflexive Candidate Notification + +The MGW sends a NOTIFY request command as defined in Table 14.2.57.1. + +**Table 14.2.57.1: ICE New Peer Reflexive Candidate Notification** + +| Address Information | Control information | Bearer information | +|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| +| | Transaction ID = x
Context ID= C1
Termination ID = T1
Event_ID (Event ID = x,
" New Peer Reflexive Candidate
(Candidate)") | | + +The MSC Server responds as defined in Table 14.2.57.2 + +**Table 14.2.57.2: ICE New Peer Reflexive Candidate Ack** + +| Address Information | Control information | Bearer information | +|----------------------------|--------------------------------------------------------------|---------------------------| +| | Transaction ID = x
Context ID = C1
Termination ID = T1 | | + +## 15 UMTS packages + +### 15.1 Mandatory UMTS packages + +The following package shall be supported for the UMTS Bearer Independent Circuit-Switched Core Network: + +- 3GUP (User Plane) package (see subclause 15.1.1). + +#### 15.1.1 3GUP package. + +PackageID: threegup (0x002f) + +Version: 1 + +Extends: None + +This package identifies that the User Plane package is used for the termination. It also contains some parameters for the User Plane functions in the MGW. + +The UP Protocol operates independently of the stream mode property, i.e. type 14 UP PDUs (which are used for inband UP signalling) can be transported between UP peers, irrespective of the stream mode direction. However, other types of UP PDUs shall be handled according to the stream mode property. + +##### 15.1.1.1 Properties + +UP Mode of operation: + +PropertyID: mode (0x0001). + +Description: Defines the mode of operation of the User Plane functions , for further definitions see 3GPP TS 25.415 [4] and 29.415 [8]. + +Type: Enumeration. + +Possible Values: + +- "Trans" (0x0001) Transparent mode. +- "Supp" (0x0002) Support mode for predefined SDU sizes. + +Default: "Trans" (0x0001) Transparent mode. + +Defined in: Local Control descriptor. + +Characteristics: Read/Write. + +UP versions: + +PropertyID: upversions (0x0002). + +Description: Defines the required versions of the UP mode of operation. + +Type: Sub-list of enumeration. + +Possible Values: + +- "1" (0x01) Version 1. +- "2" (0x02) Version 2. +- "3" (0x03) Version 3. +- "4" (0x04) Version 4. +- "5" (0x05) Version 5. + +- "6" (0x06) Version 6. +- "7" (0x07) Version 7. +- "8" (0x08) Version 8. +- "9" (0x09) Version 9. +- "10" (0x0A) Version 10. +- "11" (0x0B) Version 11. +- "12" (0x0C) Version 12. +- "13" (0x0D) Version 13. +- "14" (0x0E) Version 14. +- "15" (0x0F) Version 15. +- "16" (0x10) Version 16. +- Default: "1" (0x01) Version 1. + +Defined in: Local Control descriptor. + +Characteristics: Read/Write. + +Delivery of erroneous SDUs: + +PropertyID: delerrsdu (0x0003). + +Description: Indicates how erroneous SDUs should be handled. If it is set to YES then the UP entity implements error checking and sets Frame Quality Classification (FQC) bits accordingly; bad frames are delivered to the UP layer. If it is set to NO then the UP entity performs error checking and if a bad frame is detected then it is discarded. These settings are required only when the payload is to be examined by upper layer services; an MGW may ignore the settings of this parameter if it passes frames transparently through the UP entities. If it is set to NA then no checking is performed. + +Type: Enumeration. + +Possible Values: + +- "Yes" (0x0001) Yes. +- "No" (0x0002) No. +- "NA" (0x0003) Not Applicable. + +Default: "NA" (0x0003) Not Applicable. + +Defined in: Local Control descriptor. + +Characteristics: Read/Write. + +Interface: + +PropertyID: interface (0x0004). + +Description: Indicates the type of interface on which the termination is used. + +Type: Enumeration. + +Possible Values: + +- "RAN" (0x0001) Iu interface. +- "CN" (0x0002) Nb interface. + +Defined in: Local Control descriptor. + +Characteristics: Read/Write. + +Initialisation Direction: + +PropertyID: initdir (0x0005). + +Description: Indicates whether or not the termination in the MGW should expect initialisation information, or initiate UP initialisation itself. + +For a termination with property "interface = CN": + +- If Initialisation Direction is set to Incoming then the MGW shall expect to receive an initialisation either at this termination or from an other Nb or Iu termination in the same context. +- If Initialisation Direction is set to outgoing, then the MGW shall send out an initialisation procedure from this termination. If another termination in the same context is initialised with the same codec type and configuration the MGW should re-use the RFCI values for its Initialisation PDU, otherwise it must assign its own values. + +For a termination with property "interface = RAN": + +- If Initialisation Direction is set to "incoming", then the initialisation received at this termination is from the originating RAN and can be forwarded internally to other terminations for subsequent UP initialisations. +- If Initialisation Direction is set to "outgoing", then initialisations received are from the terminating RAN and cannot be forwarded internally. RFCI value correction can be performed at this termination, and initialisations can be sent out to the RAN. + +Examples for the usage of this property are given in annex B. + +Type: Enumeration. + +Possible Values: + +- "In" (0x0001) Incoming. +- "Out" (0x0002) Outgoing. + +Defined in: Local Control descriptor. + +Characteristics: Read/Write. + +### 15.1.1.2 Events + +None. + +### 15.1.1.3 Signals + +None. + +### 15.1.1.4 Statistics + +None. + +### 15.1.1.5 Procedures + +The MGC uses this package to indicate to the MGW that the Iu (or Nb) User Plane is used between the RNC (or distant MGW) and the MGW. The package is sent in the Establish bearer, Modify Bearer Characteristics and Prepare bearer procedures. For more information on the User Plane and for a description of 'UP mode of operation', 'UP versions' and 'Delivery of erroneous SDUs' see 3GPP TS 25.415 [4]. + +The following procedures are valid for UP in Support Mode: + +- The MGW shall be able to initiate and respond to the UP control procedures (PDU type 14 frames) independently of the Stream Mode during the call establishment phase, i.e. when not in TrFO. + +- Otherwise, during TrFO the MGW shall be able to forward UP control procedures (PDU type 14 frames) received at one termination to the other termination. +- The UP Initialisation procedure is always acknowledged between MGW peers. If an MGW receives a request for a notification for the bearer establishment then the MGW shall not send the notification until after it has either sent or received the acknowledgement for the UP initialisation. +- The MGW shall always store RFCI parameters against the MGW termination that received or that sent the UP initialisation. +- If an MGW has the UP termination property Initialisation Direction = Incoming then it expects to either receive an Initialisation (externally) or after receiving initialisation information internally send an initialisation (externally), based on what occurs first. +- If an MGW has UP termination property Initialisation Direction = Outgoing and interface CN, then it generates a network originated Initialisation PDU as soon as the bearer towards the succeeding node is successfully established, with RFCIs corresponding to the last codec configured on the termination. If another termination in the same context is initialised with the same codec type and configuration the MGW should re-use the RFCI values for its Initialisation PDU, otherwise it must assign its own values. The initialisation information sent by the MGW depends on the service that the bearer supports. For CSD service see 3GPP TS 29.007 [6] chapter 11.5. For speech service see 3GPP TS 26.102 [26] chapter 8. +- If an MGW has UP termination property Initialisation Direction = Outgoing and interface RAN, then it expects to receive an Initialisation externally. It shall not pass the initialisation parameters internally. It may initiate RFCI Value Correction out from this termination. +- A CN incoming or outgoing termination having already completed its UP initialisation towards a peer MGW shall not send externally any new UP initialisation except if a reserve / modify characteristic procedure occurred on that termination since the last initialisation. +- RAN Outgoing termination may perform, during its lifetime, subsequent RFCI Value corrections, e.g. due to changes of RFCIs on other terminations. +- If an MGW has two terminations in the same context defined as supporting the UP package and with Initialisation Direction incoming, then when it receives an Initialisation procedure from one side (provided the bearer connection from the other termination to its peer MGW is established) it shall start the UP initialisation procedure towards the peer MGW. The MGW shall perform this procedure independently of the through-connection of the terminations in the context. The MGW shall relay control information from the first initialisation to the UP peer for use at the subsequent initialisation. Also, subsequent control procedures received on one UP shall be relayed to the other UP entity when the two UP entities are connected within the MGW. This behaviour is described in more detail in Annex A. - When adding a new CN incoming termination to a context that has already a RAN or CN incoming termination, if the existing termination has already completed its UP initialisation, the MGW shall not start an initialisation procedure on the new termination based on the control information already stored at the initialised incoming termination in the context. +- If an MGW has one termination with properties "interface = RAN" and "initialisation direction = outgoing" and another termination with property "initialisation direction = Incoming" in the same context, then the MGW shall not forward the UP initialisation from the Incoming termination until it has received a UP initialisation at the "RAN"/"outgoing" side. If the codec type and codec modes configured on both terminations are identical, and if the RFCI values stored at the "incoming" termination do not match the RFCI values stored at the "outgoing" RAN side then "RFCI Value Correction" may be performed to the "outgoing" RAN side: The MGW starts UP initialisation with the RFCI values 'relayed' from the "Incoming" side. No "RFCI Value Correction" is permitted at an outgoing RAN termination whose Iu initialisation negotiates the version 1 of the support mode, at an "incoming" Iu termination or at any Nb termination. +- If a new RAN outgoing termination is added to a context that has already a RAN incoming or CN incoming termination, and if the existing termination has already completed its UP initialisation, the MGW may carry out a RFCI value correction on the new RAN outgoing termination., The control information to be used for the RFCI value correction shall be relayed from the initialised incoming termination in the context. +- No RFCI value correction shall be triggered for data call. +- As an implementation option, "RFCI Value Correction" may be delayed if terminations are not through-connected; it will be triggered by connection modification. Otherwise it shall be performed immediately + +- If "RFCI Value Correction" is not performed the MGW shall map the indexes for frames from one side to the RFCI indexes for frames from the other side. This behaviour is described in more detail in Annex A. +- If an MGW has two RAN terminations connected to the same context then the "RFCI Value Correction" is performed by the Outgoing termination. +- If an MGW has two terminations which support the UP package connected to the same context and both RFCI sets match then the MGW may pass frames transparently through the UP entities; no monitoring of the frames is performed, provided that the terminations are through-connected. This behaviour is described further in Annex A. +- If the MGW is passing frames transparently, no UP monitoring is performed. When the MGW receives an H.248 procedure request which requires interpretation or interaction with the UP, then it shall resume its UP protocol responsibilities, i.e. perform monitoring or termination of the UP protocol. +- If an MGW sends an FP UP initialization message from a termination, the MGW shall only offer versions of the FP UP, which are given in the property "UP versions" of this termination and which are supported by the MGW for this termination. +- If an MGW receives an FP UP initialization message at a termination, the MGW shall only positively acknowledge this initialization message, if versions of the FP UP are offered, which are given in the property "UP versions" and which are supported at the MGW for this termination. In the positive FP UP initialization acknowledge message, the MGW shall select one of these versions. If none of these versions are offered in the FP UP initialization message, the MGW shall send a negative FP UP acknowledge message and it shall not forward the initialization to a possible second FP UP termination in the same context. +- If PCM is used on the Nb then FP UP initialization shall be performed by the termination with property "Outgoing". If the termination property is "Incoming" then it shall receive the RFCI's from its IuFP peer (or from internal MGW termination with IuFP and same codec). If IuFP is defined on another termination in the MGW but the codec is different, i.e. not TrFO then the relaying of RFCI's shall not be performed. These IuFP peer connection shall be seen as completely separate. +- the UP initialisation information attached to a termination (RFCI values, codec type and mode(s), UP initialisation completed or not) are kept unchanged when the termination is moved to a new context. +- the initialisation direction may be changed during the lifetime of a termination ; upon such a change, the MGW shall apply the behaviour attached to the new initialisation direction. + +The procedures for a termination configured in UP Transparent Mode are those described in 3GPP TS 25.415 [4]. + +## 15.2 Optional UMTS packages + +The following packages may be supported by the UMTS Bearer Independent Circuit-Switched Core Network as required by the network services deployed in the network: + +- Circuit Switched Data package (see subclause 15.2.1); +- TFO package (see subclause 15.2.2); +- 3G Expanded Call Progress Tones Generator package (see subclause 15.2.3); +- Modification of Link Characteristics Bearer Capability package (see subclause 15.2.4); +- Enhanced Circuit Switched Data package (see subclause 15.2.5); +- Cellular Text telephone Modem Text Transport package (see subclause 15.2.6); +- IP transport package (see subclause 15.2.7); +- Flexible Tone Generator Package (see subclause 15.2.8); +- Trace Package (see subclause 15.2.9); +- ASCII Group Call package (see subclause 15.2.10); +- 3G Interface Type package. + +## 15.2.1 Circuit Switched Data package + +PackageID: threegcsd (0x0030) + +Version: 1 + +Extends: None + +This package contains the information needed to be able to support GSM and UMTS Circuit Switched Data from the media gateway. + +### 15.2.1.1 Properties + +PLMN BC: + +PropertyID: plmnbc (0x0001). + +Description: The PLMN Bearer Capability. + +Type: Octet string. + +Possible values: + +- Specified in the subclause "Bearer capability" in 3GPP TS 24.008 [3] , including the Bearer Capability IEI and Length. + +Defined in: Local Control Descriptor. + +Characteristics: Read/Write. + +GSM channel coding: + +PropertyID: gsmchancod (0x0002). + +Description: Channel information needed for GSM. + +Type: Octet string. + +Possible values: + +- The second octet of Chosen Channel as specified in the subclause "Chosen Channel" in 3GPP TS 48.008 [9]. + +Defined in: Local Control Descriptor. + +Characteristics: Read/Write. + +### 15.2.1.2 Events + +Protocol Negotiation Result: + +EventID: protres (0x0001). + +Description: This event is used to report the result of the protocol negotiation. + +EventsDescriptor Parameters: None. + +ObservedEventsDescriptor Parameters: + +- Negotiation Result: + - ParameterId: result (0x0001). + - Description: reports whether the protocol negotiation has been successful. + - Type: Enumeration. + - Possible Values: + +- "Success" (0x0001): the protocol negotiation on the termination has been successful. +- "Failure" (0x0000): the protocol negotiation on the termination has failed. +- Possible Failure Cause: + - ParameterId: cause (0x0002). + - Description: indicates the possible failure cause. + - Type: Enumeration. + - Possible Values: + - "Unsp" (0x0001): the protocol negotiation has failed for an unspecified reason. + - "V8V34" (0x0002): the V.8 or the V.34 protocol negotiation has failed (modem termination only). + +Rate Change: + +EventID: ratechg (0x0002). + +Description: This event is used to report a rate change. For example for GSM FAX if the detected rate does not match the channel rate the MGW shall use this to request a new channel rate. See CMM in 3GPP TS 43.045 [35]. + +EventsDescriptor Parameters: None. + +ObservedEventsDescriptor Parameters: + +- New Rate: + - ParameterId: rate (0x0001). + - Description: reports the new rate for the termination. + - Type: Integer. + - Possible Values: transmission rate in bits per second, rounded to the nearest integer value. The value must be a valid bitrate; one of the following rates: 2400, 4800, 9600, 14400, 28800, 57600. An invalid rate shall cause the call to be released by the MSC Server. + +### 15.2.1.3 Signals + +Activate Protocol: + +SignalID: actprot (0x0001). + +Description: Activate the higher layer protocol. + +Signal type: Brief. + +Duration: N/A. + +Additional parameter: + +- Local Peer Role: + - ParameterID: localpeer (0x0001). + - Type: Enumeration. + - Possible values: + - "Orig" (0x0000): originating. + - "Term" (0x0001): terminating. + +- Description: This parameter is optional, but is required for modem and fax calls. It is used to inform the modem whether it should act as originating or terminating peer. This parameter is only included within signal towards the radio access. This may either be an Access Termination or a CN Termination toward another MGW that serves the radio access. + +### 15.2.1.4 Statistics + +None. + +### 15.2.1.5 Procedures + +This package is used to set up data calls within the CS domain. For more information on the IWF, refer to 3GPP TS 29.007 [6]. + +When the Media Gateway Controller initiates the "Establish Bearer" procedure, the "Prepare Bearer" procedure, the "Modify Bearer Characteristics" procedure, the "Reserve Circuit" procedure, the "Reserve RTP Connection Point" procedure, the "Configure RTP Connection Point" procedure or the "Reserve and Configure RTP Connection Point" procedure, it shall provide the PLMN BC ("plmnb" property above) for the termination on the mobile side and the ISDN BC (standard H.248 properties, subclause "Bearer Capabilities") for the termination on the fixed side. For a mobile-to-mobile call, it shall provide the PLMN BC on both terminations. + +The presence of the PLMN BC property may trigger the use of the IWF. + +Once the bearer has been established, after B-answer, the "Activate Interworking Function" procedure is used to activate the IWF. The Activate Protocol signal ("actprot") will start the negotiation of the layer 2 protocols on both sides. If a modem or fax service is requested, the signal shall contain the Local Peer Role parameter ("localpeer"), to tell the modem whether it should act as originating or terminating peer. + +NOTE: The Activate Protocol signal is needed only after B-answer as described above or after successful in-call modification from speech to fax, to activate the protocol timers at the correct time. This is the only time when this signal is needed (specifically, the signal is not used after a handover sequence or for lawful interception). + +The IWF Protocol Indication notifications are used by the MGW to inform the MSC server about IWF protocol events. The MSC has to request the detection of the events "Protocol Negotiation Result" and "Rate Change" in the "Activate IWF" procedure, the "Establish Bearer" procedure, the "Prepare Bearer" procedure, the "Modify Bearer Characteristics" procedure, the "Reserve Circuit" procedure, the "Reserve RTP Connection Point" procedure, the "Configure RTP Connection Point" procedure or the "Reserve and Configure RTP Connection Point" procedure. + +For handover to GSM, or change of channel characteristics within the GSM network, the property GSM Channel Coding ("gsmchancod"), which contains the information about the channel type and the number of channels, shall be transmitted to the termination on the mobile side in the "Establish Bearer", the "Prepare Bearer", the "Reserve Circuit", the "Reserve RTP Connection Point", the "Configure RTP Connection Point" and the "Reserve and Configure RTP Connection Point" procedures together with the PLMN BC. The presence of the GSM Channel Coding property also indicates that the termination is using a GSM access network. + +If the MGW has requested a rate change due to GSM fax rate mismatch (CMM procedure see 3GPP TS 43.045 [35]) then it shall suspend transmission until the MSC Server has modified the PLMN Bearer Capability and GSM Channel Coding property to match the required rate. If this occurs while other context manipulations are occurring the MGW shall only resume transmission when the streams are bothway connected and the PLMN Bearer Capability and Channel Coding are correct. The MGW shall not send subsequent rate change notifications while the outstanding rate change has not been performed by the MSC Server. + +## 15.2.2 TFO package + +PackageID: threegtfoc (0x0031) + +Version: 2 + +Extends: None + +This package defines events and properties for Tandem Free Operation (TFO) control. TFO uses inband signalling and procedures for Transcoders to enable compressed speech to be maintained between a tandem pair of transcoders. This package allows an MGW, which has inserted a transcoder, to support TFO. + +### 15.2.2.1 Properties + +TFO Activity Control: + +PropertyID: tfoenable (0x0001). + +Description: Defines if TFO is enabled or not. + +Type: Enumeration. + +Possible Values: + +- "On" (0x0001): TFO is enabled, TFO protocol is supported. +- "Off" (0x0002): TFO is not enabled, TFO protocol is not initiated or terminated. + +Defined in: Local Control descriptor. + +Characteristics: Read/Write. + +TFO Codec List: + +PropertyID: codeclist (0x0002). + +Description: List of codecs for use in TFO protocol, the Local Used Codec (see 3GPP TS 28.062 [5]) is always the first entry in the list. The MSC Server may enable TFO without providing a TFO Codec List ; in this case, the MGW shall behave as if it had received a TFO Codec List composed of the selected codec of the opposing termination within the Context. + +Type: Sub-list of Octet string. + +Possible Values: + +- List of codec types; each entry: + +Mc Single Codec, similar to as defined in ITU-T Recommendation Q.765.5 [24], for single codec information (figure 14/Q.765.5), where the Codec Information is defined either in ITU-T Recommendation Q.765.5 [24] or in another specification for the given Organization Identifier. For 3GPP codecs these are defined in 3GPP TS 26.103 [16]. The ACodec property in H.248 binary encoding or codecconfig attribute in H.248 text encoding contain the contents of the ITU-T Single Codec IE, excluding the Single Codec Identifier, Length Indication and Compatibility Information. + +In H.248 text encoding, the value of the codeclist property shall be encoded as: + +LBRKT codecconfig \*(COMMA codecconfig) RBRKT + +Example: H.248 text encoding of the TFO codec list (UMTS\_AMR\_2 with Preferred Configuration set 1, and UMTS\_AMR-WB with Preferred Configuration set 0): + +Threegtfc/codeclist = { 0206959504 , 020A00 } + +Where: + +- UMTS\_AMR\_2 parameters are: ETSI, UMTS\_AMR\_2, ACS={12.2, 7.4, 5.9, 4.75}, SCS={12.2, 7.4, 5.9, 4.75}, OM=0 plus MACS=4 +- UMTS\_AMR\_WB parameters are: ETSI, UTMS\_AMR\_WB, Config-WB-Code=00 + +Defined in: Local Control descriptor. + +Characteristics: Read/Write. + +### 15.2.2.2 Events + +Optimal Codec Event: + +EventID: codec\_modify (0x0010). + +Description: The event is used to notify the MGC that TFO negotiation has resulted in an optimal codec type being proposed. + +EventsDescriptor Parameters: None. + +ObservedEventsDescriptor Parameters: + +- Optimal Codec Type. + - ParameterID: optimalcodec (0x0011). + - Description: indicates which is the proposed codec type for TFO. + - Type: Octet string. + - Possible Values: + - Mc Single Codec; + - Similar to as defined in ITU-T Recommendation Q.765.5 [24], for single codec information (figure 14/Q.765.5), where the Codec Information is defined either in ITU-T Recommendation Q.765.5 [24] or in another specification for the given Organization Identifier. For 3GPP codecs these are defined in 3GPP TS 26.103 [16]. The ACodec property in H.248 binary encoding or codecconfig attribute in H.248 text encoding contain the contents of the ITU-T Single Codec IE, excluding the Single Codec Identifier, Length Indication and Compatibility Information. + +Codec List Event: + +EventID: distant\_codec\_list (0x0012). + +Description: The event is used to notify the MGC of the distant TFO partner's supported codec list. + +EventsDescriptor Parameters: None. + +ObservedEventsDescriptor Parameters: + +- Distant Codec List: + - ParameterID: distlist(0x0013). + - Description: indicates the codec list for TFO. + - Type: Sub-list of Octet string. + - Possible Values: + - List of codec types; each entry: + - Mc Single Codec similar to as defined in ITU-T Recommendation Q.765.5 [24], for single codec information (figure 14/Q.765.5), where the Codec Information is defined either in ITU-T Recommendation Q.765.5 [24] or in another specification for the given Organization Identifier. For 3GPP codecs these are defined in 3GPP TS 26.103 [16]. The ACodec property in H.248 binary encoding or codecconfig attribute in H.248 text encoding contain the contents of the ITU-T Single Codec IE, excluding the Single Codec Identifier, Length Indication and Compatibility Information. + +The first Codec Type in the list is the Distant Used Codec, received from the distant TFO partner (see 3GPP TS 28.062 [5]). . + +In H.248 text encoding, the value of the distlist parameter shall be encoded as: + +LBRKT codecconfig \*(COMMA codecconfig) RBRKT + +TFO Status Event: + +EventID: TFO\_status (0x0014). + +Description: The event is used to notify the MGC that a TFO link has been established or broken. + +EventsDescriptor Parameters: None. + +ObservedEventsDescriptor Parameters: + +- TFO Status: + - ParameterId: tfostatus (0x0015). + - Description: reports whether TFO has been established or broken. Upon TFO activation, no notification is sent if TFO has not been established. A TFO\_Off notification is only reported when a TFO link previously established is broken. The MGW should not report transient TFO status change. + - Type: Boolean + - Possible Values: + - "TFO\_On" : TFO has been established. + - "TFO\_Off" : TFO is no more established. + +### 15.2.2.3 Signals + +None. + +### 15.2.2.4 Statistics + +None. + +### 15.2.2.5 Procedures + +For the procedures for TFO see 3GPP TS 28.062 [5]. + +To enable TFO, the MSC Server shall configure the properties of this package on a MGW Termination with the media stream property for Codec Type set to ITU-T Recommendation G.711 [25] (see annex C of ITU-T Recommendation H.248 [10]) or Bearer Service Characteristics set to "Speech" or "3.1 kHz Audio" in TMR or USI due to Reserve Circuit Procedure, see in ITU-T Recommendation Q.1950 (see 3GPP TS 29.205 [7]). + +The TFO protocol shall be disabled if the call configuration becomes no longer TFO compatible or if the Codec Type property of the media stream at the opposing termination in the Context is reconfigured to G.711 or if the Bearer Service Characteristics of the opposing Termination is reconfigured to "Speech" or "3.1 kHz Audio". The TFO protocol may be disabled either by the MSC Server by using the TFO Activity Control property of this package or by the MGW in accordance with the TFO rules as described in [5] when it detects that TFO operation is no longer possible (for example it has G.711 encoding at opposing Terminations). + +## 15.2.3 3G Expanded Call Progress Tones Generator Package + +PackageID: threegxcg(0x0032) + +Version: 1 + +Extends: xcg version1 + +This package extends "Expanded Call Progress Tones Generator Package", as defined in ITU-T Recommendation Q.1950 [23] (see 3GPP TS 29.205 [7]). The package adds a new toneId for CAMEL prepaid warning tone. + +### 15.2.3.1 Properties + +None. + +### 15.2.3.2 Events + +None. + +### 15.2.3.3 Signals + +CAMEL Prepaid Warning Tone: + +SignalID: cpwt (0x004f). + +Description: Generate CAMEL prepaid warning tone to inform the party that the Max Call Period Duration is about to expire. CAMEL prepaid warning tone is defined in 3GPP TS 23.078 [22]. The physical characteristic of CAMEL prepaid warning tone is available in the gateway. + +Signal type: Brief. + +Duration: Provisioned, Not Auditable. + +Additional parameters: + +- Tone Direction. +- ParameterID: td (0x0010). +- Type: Enumeration. +- Values: + - "Ext" (0x01): external. + - "Int" (0x02): internal. + - "Both" (0x03): Both. +- Default: "Ext". + +### 15.2.3.4 Statistics + +None. + +### 15.2.3.5 Procedures + +None. + +## 15.2.4 Modification Of Link Characteristics Bearer Capability + +PackageName: Modification of Link Characteristics Bearer Capability + +PackageID: threegmlc(0x0046) + +Description: This package contains an event that when requested by the MGC will cause the MG to notify the MGC that modification of the link characteristics is allowed. This notification is typically generated when the bearer has been established. + +Version: 1 + +Extends: None + +### 15.2.4.1 Properties + +None. + +### 15.2.4.2 Events + +Bearer Modification Support Event. + +EventID: mod\_link\_supp (0x0001). + +Description: The event is used to notify the MGC that modification of the link characteristics of the current bearer connection is permitted. + +EventsDescriptor Parameters: None. + +ObservedEventsDescriptor Parameters: None. + +#### 15.2.4.3 Signals + +None. + +#### 15.2.4.4 Statistics + +None. + +#### 15.2.4.5 Procedures + +If the MGC is interested in determining whether or not the bearer associated with a termination supports modification of its link characteristics it shall send a request (Add/Modify/Move) with the Bearer Modification Support Event. When the bearer is established the MG will indicate in a Notify request to the MGC if modification of link characteristics is supported. A notify will NOT be generated if modification is NOT supported on the bearer. + +### 15.2.5 Enhanced Circuit Switched Data package + +PackageID: threeegcsden (0x0082) + +Version: 1 + +Extends: threeegcsd (0x030) Version 1 + +This package extends "Circuit Switched Data Package", as defined in subclause 15.1.2. This package adds a new property to define the user bitrate at a Iu termination. + +#### 15.2.5.1 Properties + +##### Bitrate + +PropertyID: bitrate (0x0003). + +Description: user bitrate. + +Type: Integer. + +Possible Values: transmission rate in bits per second, rounded to the nearest integer value. The value shall be a valid bitrate; one of the following rates: 2400, 4800, 9600, 14400, 28800, 57600, 64000. + +Defined in: Local Control Descriptor. + +Characteristics: Read/Write. + +#### 15.2.5.2 Events + +None. + +#### 15.2.5.3 Signals + +None. + +#### 15.2.5.4 Statistics + +None. + +#### 15.2.5.5 Procedures + +This package is used in addition to the 3GCSD package for CS data calls. It is used for indicating the user data rates for Inter-MSC SRNS Relocation and handover cases. If the Bitrate is not 64 kb/s at one termination in the MGW but its opposing termination has properties that define its bitrate to be 64 kb/s (e.g. TMR=UDI) then A-TRAU' protocol shall be applied by the MGW. For further details see 3GPP TS 29.007 [6]. + +## 15.2.6 Cellular Text telephone Modem Text Transport + +PackageName: CTM Text Transport + +PackageID: threegctm (0x0068) + +Description: The CTM text transport package is intended for enabling robust real time text conversation through a voice channel primarily intended for communication over mobile networks. This package includes the mechanisms needed to transport T.140 text conversation streams [19] in a voice channel environment, using the CTM Cellular Text Telephone Modem specified in 3GPP TS 26.226 [18]. The transport mechanism allows for alternating transport of voice and text. + +Version: 1 + +Extends: None + +### 15.2.6.1 Properties + +Text termination connection state: + +PropertyID: connstate (0x0001). + +Description: The connection state property is used to reflect details of the achieved text connection. For each new session connstate should be reset to "Prepare". + +Type: Enumeration. + +Possible values: + +- "Idle" (0x0001) meaning that CTM availability negotiation has failed; CTM is disabled except for monitoring the incoming line for CTM signals. +- "Prepare" (0x0002) for CTM being enabled, monitoring for CTM signals and ready to send CTM signals. +- "Connected" (0x0006) for CTM being enabled and to have detected CTM availability in the current session. + +Defined in: TerminationState. + +Characteristics: Read/Write. + +Text Transport: + +PropertyID: trpt (0x0002) + +Description: The transport parameter reflects the transport mechanism selected for the Text Conversation termination. In 3GPP, one possible transport mechanism is the Cellular Text Telephone Modem as in 3GPP TS 26.226 [18]. It is used when it is desired to transport the text conversation in a voice channel. CTM enables alternating use of the voice channel for voice and text during the call. + +Type: Enumeration. + +Possible values: + +- "ctm" (0x0008) for text transport in mobile voice channel as in 3GPP TS 26.226 [18]. + +Defined in: LocalControl. + +Characteristics: Read/Write. + +Text Protocol Version: + +PropertyID: textproto (0x0003). + +Description: The version of the ITU-T Recommendation T.140 [19] protocol used in the connection. + +Type: Integer. + +Possible values: + +- Any integer corresponding to a T.140 version number (currently 1) as in ITU-T Recommendation H.248 .2 [17]. + +Defined in: LocalControl. + +Characteristics: Read/Write. + +### 15.2.6.2 Events + +Connection State Change: + +EventID: connchange (0x0001). + +Description: + +- This event will occur when the text connection state for the termination has changed. +- The parameter values are the same as the Connection State property. +- If a CTM availability request timed out, the state is returned to Idle. + +EventDescriptorParameters: + +None. + +ObservedEventDescriptorParameters: + +ParameterName: Connection Change. + +ParameterID: connchng (0x0001). + +Type: Enumeration. + +Possible Values: As property threegctm/connstate. + +### 15.2.6.3 Signals + +None. + +### 15.2.6.4 Statistics + +Characters Transferred: + +StatisticsID: chartrans (0x0001). + +Description: Number of bytes of ITU-T Recommendation T.140 [19] data transferred through the termination. + +Units: count. + +### 15.2.6.5 Procedures + +If the MGC detects a CTM indication it shall send a request (Add/Modify/Move) with the CTM Transport property. Upon receivable of it, the MGW shall allocate a termination with CTM capabilities. Normal usage is that the CTM enabled termination handles one text stream and one voice stream and alternates between transporting voice and text in the voice channel according to the functionality of CTM. This termination could for example be combined in a context with a termination with the txp and ctyp packages for gateway functionality between PSTN text telephony and mobile CTM based text telephony. These packages are described in ITU-T Recommendation H.248.2 [17]. + +The CTM algorithm has states. The states defined in the text termination connection state property are mapped into CTM states in the following way: + +- Idle: CTM disabled because of an unsuccessful CTM availability negotiation. +- Prepare: normal initial state with CTM monitoring active. + +- Connected: CTM negotiation is completed. + +For each new call, the CTM termination shall be put in the Prepare state. + +When the CTM availability negotiation is completed, the state is Connected. + +The state transitions are automatic, except for setting Prepare state as described above. + +## 15.2.7 IP transport package + +This package has been replaced by the use of Annex C.6 IP and UDP properties (see subclauses 14.2.41 and 14.2.42). + +## 15.2.8 Flexible Tone Generator Package + +PackageID: threegflex (0x0084) + +Version: 1 + +Extends: threegxcg version 1 + +This package extends "3G Expanded Call Progress Tones Generator Package", as defined in chapter 15.1.4 above. This package adds a new tone for call duration control in CAMEL phase 4, supporting variable sequence of tones and burst list. + +### 15.2.8.1 Properties + +None. + +### 15.2.8.2 Events + +None. + +### 15.2.8.3 Signals + +Signal Name: Flexible Tone. + +SignalID: ft (0x0050). + +Description: Generate flexible 900 Hz tone. The physical characteristics of Flexible Tone is not described in the additional parameters. It shall be available in the Media Gateway. + +SignalType: Brief. + +Duration: Provisioned. + +Additional Parameters: + +- Parameter Name: Burst List Direction + +Description: Used to indicate the direction the tone is to be sent. External indicates that the tone is sent from the MG to an external point. Internal indicates that the tone is played into the Context to the other terminations. Both way indicates both internal and external behaviour. + +ParameterID: bld (0x0001). + +Type: Enumeration. + +Possible Values: + +- "Ext" (0x01): External. +- "Int" (0x02): Internal. +- "Both" (0x03): Both way. +- Default: "Ext" (0x01). + +Parameter Name: numberOfBursts. + +Description: Number of bursts in the burst list. + +ParameterID: nob (0x0002). + +Type: Integer. + +Possible values: 1 to 3. + +Default: 1. + +Parameter Name: burstInterval. + +Description: Time interval between two consecutive bursts expressed in amount of 100 ms units. + +ParameterID: bi (0x0003). + +Type: Integer. + +Possible values: 1 to 1200. + +Default: 2. + +Parameter Name: numberOfTonesInBurst. + +Description: Number of tones to be played in each burst. + +ParameterID: notib (0x0004). + +Type: Integer. + +Possible values: 1 to 3. + +Default: 3. + +Parameter Name: toneDuration. + +Description: Duration of each tone in a burst expressed in amount of 100 ms units. + +ParameterID: td (0x0005). + +Type: Integer. + +Possible values: 1 to 20. + +Default: 2. + +Parameter Name: toneInterval. + +Description: Time interval between two consecutive tones in a burst expressed in amount of 100 ms units. + +ParameterID: ti (0x0006). + +Type: Integer. + +Possible values: 1 to 20. + +Default: 2. + +## 15.2.8.4 Statistics + +None. + +## 15.2.8.5 Procedures + +The MGW should generate the tones using the above mentioned parameters as specified in 3GPP TS 23.078 [22] subclause 4.5.7.1.2 + +In case MGC requests to generate a flexible tone specifying a signal type "Timeout" and a "Duration" longer than the time needed to play the whole Burst List no action will be taken on the incoming stream to fill the gap. I.e. if any user plane stream is received on one side of the termination after the end of the burst list, it will be present, unchanged, on the other side of the termination as well (transparent mode). + +## 15.2.9 Trace Package + +PackageID: calltrace (0x0097) + +Version: 1 + +Extends: None + +This package defines properties for subscriber and equipment trace activation and deactivation properties to be attached to the trace record generated by MGW. + +### 15.2.9.1 Properties + +#### Trace Activation Control + +PropertyID: traceactivityrequest(0x0001) + +Description: Defines if trace is activated or deactivated. + +Type: Bool + +Possible Values: + +"on" (true): Trace Session is activated in MGW + +"off" (false): Trace Session is deactivated in MGW + +Defined in: Local Control descriptor + +Characteristics: Read/Write + +#### IMSI + +PropertyID: imsi(0x0002) + +Description: IMSI number of the traced subscriber to be attached to the trace record. Used for record identification like trace reference. + +Type: Octet string + +Possible Values: The IMSI is coded as defined in 3GPP TS 23.003 [43]. The IMSI is TBCD-coded with a fixed length of 8 octets. Two digits are encoded per octet, each digit is encoded 0000 to 1001 (0 to 9). Bits 8765 of octet n encodes digit 2n, bits 4321 of octet n encodes digit 2(n-1) +1 (i.e the order of digits is swapped in each octet compared to the digit order defined in 3GPP TS 23.003 [43]). 1111 is used as filler when there is an odd number of digits. Digits are packed contiguously with no internal padding. + +Defined in: Local Control descriptor + +Characteristics: Read/Write + +#### IMEI(SV) + +PropertyID: imei\_sv(0x0003) + +Description: IMEI(SV) number of the traced equipment to be attached to the trace record. Used for record identification like trace reference. + +Type: Octet string + +Possible Values: The IMEI(SV) is coded as defined in 3GPP TS 23.003 [43]. The IMEI(SV) is TBCD encoded. Two digits are encoded per octet, each digit is encoded 0000 to 1001 (0 to 9). Bits 8765 of octet n encodes digit 2n, bits 4321 of octet n encodes digit 2(n-1) +1 (i.e the order of digits is swapped in each octet compared to the + +digit order defined in 3GPP TS 23.003 [43]). 1111 is used as filler when there is an odd number of digits. Digits are packed contiguously with no internal padding. + +Defined in: Local Control descriptor + +Characteristics: Read/Write + +#### Trace Reference + +PropertyID: tracereference(0x0004) + +Description: Reference number to identify different Trace Session in OSS as defined in 3GPP TS 32.421 [29] and 3GPP TS 32.422 [30]. + +Type: Octet string + +Possible Values: OSS (EM) defines when activating a Trace Session + +Defined in: Local Control descriptor + +Characteristics: Read/Write + +#### Trace Recording Session Reference + +PropertyID: tracerecsessionref(0x0005) + +Description: A unique identifier within the Trace Session for identifying the Trace Recording sessions. Defined in 3GPP TS 32.421 [29] and in 3GPP TS 32.422 [30]. + +Type: Octet string + +Possible Values: Described in 3GPP 32.422 [30] + +Defined in: Local Control descriptor + +Characteristics: Read/Write + +#### Trace Depth + +PropertyID: tracedepth(0x0006) + +Description: Trace Depth as defined in 3GPP TS 32.421 [29] + +Type: Enumeration + +Possible Values: Defined in 3GPP TS 32.422 [30] + +Defined in: Local Control descriptor + +Characteristics: Read/Write + +#### Trigrering Events + +PropertyID: triggeringevent(0x0007) + +Description: Trigrering Events as defined in 3GPP TS 32.422 [30]. + +Type: Octet string + +Possible Values: Defined in 3GPP TS 32.422 [30]. + +Defined in: Local Control descriptor + +Characteristics: Read/Write + +#### List of interfaces + +PropertyID: listofinterfaces(0x0008) + +Description: List of interfaces to trace as defined in 3GPP TS 32.422 [30] + +Type: Octet string + +Possible Values: Defined in 3GPP TS 32.422 [30] + +Defined in: Local Control descriptor + +Characteristics: Read/Write + +## 15.2.9.2 Events + +Trace result + +EventID: tracact (0x0001) + +Description: Notification to the MSC Server if trace activation was successful/unsuccessful in the MGW. + +EventDescriptor parameters: None + +ObservedEventsDescriptor parameters: + +Result: Trace Activation Result + +res (0x0001) + +Type: enumeration + +Possible values: + +success (0x0001): "Trace Successfully activated" + +failure (0x0000): "Failure in trace activation" + +## 15.2.9.3 Signals + +None + +## 15.2.9.4 Statistics + +None + +## 15.2.9.5 Procedures + +For the network level procedures of the tracing see 3GPP 32.422 [30]. + +For the trace records of the MGW see 3GPP 32.423 [31]. + +In H.248 interface MSC Server uses 'Trace Activity Control' property to indicate MGW that a termination should be placed under trace or should be taken out of trace. In the call establishing phase MSC Server sets trace package information into proper command (Add or Modify) associated to the termination to be traced. Tracing can be activated either by giving IMEI(SV) or IMSI number as a further information. MSC Server shall also provide the values for all other properties described in this package that is IMSI if trace is activated based on IMSI, IMEI(SV) if trace is activated based on IMEI(SV), Trace reference, Trace recording session reference, Trace depth, triggering events in MGW, list of interfaces in MGW. When MSC Server activates the trace, it shall use 'Trace Activation Result' Event to detect if the Trace Activation was successful or not. MGW shall not reject the Add/Modify because of unsuccessful Trace Activation, but only send a Notification with this Event. Tracing is automatically deactivated in MGW when termination is taken out of the context in the end of the call. If the Termination is Moved to another Context, trace is automatically forwarded to new termination. + +## 15.2.10 ASCI Group call package + +PackageID: threegasci (0x00b2) + +Version: 2 + +Extends: None + +This package contains the information needed to be able to support VGCS (3GPP TS 43.068 [39]) and VBS (3GPP TS 43.069 [40]) services. + +### 15.2.10.1 Properties + +Number of needed conference terminations + +PropertyID: nct (0x0001) + +Description: Indicates the number of needed conference terminations for the call. + +Type: Integer + +Defined in Descriptor: Local Control Descriptor + +Characteristics: Read/Write + +Number of desired listener context terminations + +PropertyID: nlct (0x0002) + +Description: Indicates the number of desired terminations for a listener context. + +Type: Integer + +Defined in Descriptor: Local Control Descriptor + +Characteristics: Read/Write + +### 15.2.10.2 Events + +None. + +### 15.2.10.3 Signals + +None. + +### 15.2.10.4 Statistics + +None + +### 15.2.10.5 Procedures + +The MSC server receives the number of needed conference terminations from GCR (see 3GPP TS 43.068 [39]) and 3GPP TS 43.069 [40]) and reserves the requested number of needed Conference terminations for that call. The parameter "Number of needed conference terminations" shall be included when allocating the first termination of an ASCI-conference context. It is optional when adding further terminations. If the MGW is unable to reserve the number of requested terminations for that call, it shall response with error code 510 "insufficien resources". + +The parameter "Number of desired listener context terminations" should be included when allocating the first termination of a Listener context. + +## 15.2.11 3G Interface Type package + +PackageID: threegint (0x00e3) + +Version: 1 + +Extends: None + +This package contains a property to specify the used interface type for IP terminations. + +### 15.2.11.1 Properties + +IP Interface Type + +PropertyID: ipint (0x0001) + +Description: Indicates the type of external interface used by the termination. + +Type: Enumeration. + +Possible Values: + +- "NboIP" (0x0001) Nb over IP with SIP-I based Nc, see 29.414 [32]. +- "AoIP" (0x0002) A interface over IP. +- "MboIP" (0x0003) Mb interface +- "ExtSIPT" (0x0004) External SIP-I based network + +All other values reserved. + +Defined in: Local Control descriptor. + +Characteristics: Read/Write. + +### 15.2.11.2 Events + +None. + +### 15.2.11.3 Signals + +None. + +### 15.2.11.4 Statistics + +None + +### 15.2.11.5 Procedures + +The MSC server may indicate the interface type (reference point) associated with the RTP bearer termination to the MGW with this package. This allows MGW to collect statistics per interface type associated with the RTP bearer termination as required by 3GPP TS 32.407[58]. The provision of these statistics is outside of the scope of this specification. + +## Annex A (informative): Framing protocol Interworking Function (FPIF) + +### A.1 Introduction + +SDUs transmitted over an Iu or Nb interface and received at a MGW whose outgoing UP is also Iu or Nb shall be relayed to the outgoing UP MGW termination. If no interworking function (other than the FPIF) or transcoder device is inserted by the MGW, and if UP terminations are present, then PDUs and control procedures are passed between MGW terminations by the FPIF. The FPIF is the functional entity responsible for aligning or mapping control procedures (including RFCIs, frame numbers etc) on the separate UP interfaces according to the package procedures described in the main text. The FPIF determines if the two UP configurations are identical and thus the UP PDUs may be passed transparently. If the FPIF determines that the two UP configurations are not identical it applies the required mapping. The relaying of PDUs transparently can also be considered as FPIF bypass. + +NOTE: the implementation in the MGW can perform a more efficient processing of the PDUs in this case. The MGW switching and bypassing of the protocol functions during TrFO is left to the manufacturer's implementation. + +UP initialisations are not handled by the FPIF, only receipt of the Subflow combinations and the RFCI allocations are received by the FPIF for each UP. + +The RFCIs are relayed by the FPIF as described in main text for the UP package procedures. + + + +The diagram illustrates the FPIF architecture within a Media Gateway (MGW). At the top, two 'Iu/Nb Interface' blocks are shown. Below each interface is a box labeled 'Iu or Nb UP Support Mode Functions'. Between these boxes and the interfaces are double-headed arrows labeled 'Transfer of Iu FP protocol frames'. Below each 'Iu or Nb UP Support Mode Functions' box is a 'RNL/CNL-SAP' interface, represented by a circle. Below each 'RNL/CNL-SAP' is a 'TNL-SAP' interface, also represented by a circle. At the bottom, a thick horizontal line represents the MGW. Arrows point from each 'TNL-SAP' down to the MGW. At the top center, a pink box labeled 'FPIF' has double-headed arrows connecting it to both 'RNL/CNL-SAP' interfaces. + +Diagram of the Framing Protocol Interworking Function (FPIF) architecture. + +Figure A.1: The Framing Protocol Interworking Function + +## A.2 FPIF procedures with respect to Iu framing protocol + +This clause handles relay of user data indicated to the FPIF in a Nb- or Iu-UP-data-indication message and transmitted between peer UP layer entities in PDU types 0 and 1. The FPIF passes this information to the UP layer on the sending side in a Nb- or Iu-UP-data-request message. + +### A.2.1 Payload + +Received SDUs shall be forwarded unmodified to the next MGW. Note that if "delivery of erroneous SDUs" is set to 'no', faulty SDUs are already discarded by the Iu or Nb support mode functions and, hence, not delivered to the FPIF. + +### A.2.2 RFCIs + +If the RFCI values on the outgoing UP interface match those initialised on the incoming UP interface then the RFCI indicated by the lower layer (i.e. Iu or Nb) on the receiving side shall be forwarded unmodified to lower layer on the sending side. + +If the RFCI sets on the outgoing UP interface do not match those initialised on the incoming UP interface then the FPIF performs mapping between the RFCIs on each UP for the same initialised Subflow Combination. + +The FPIF is the entity that may perform the RFCI value correction procedure as described in the main text, after this procedure then relaying of the received RFCI shall be performed. + +### A.2.3 FQC + +The FQC indicated by the lower layer (i.e. Iu or Nb) on the receiving side shall be forwarded unmodified to lower layer on the sending side. + +### A.2.4 Frame number + +The frame number indicated by the lower layer (i.e. Iu or Nb) on the receiving side shall be forwarded unmodified to lower layer on the sending side. + +A discontinuity in framing protocol support mode frame numbers is allowed at the end of the TrFO break. + +## A.3 Relay of status information + +This clause handles relay of status information indicated to the FPIF in a Nb- or Iu-UP-status-indication message and transmitted between peer UP layer entities in PDU type 14. The FPIF in general passes this information to the UP layer on the sending side. + +### A.3.1 Void + +### A.3.2 Rate Control Frames + +The FPIF shall pass rate control request and rate control acknowledgement frames transparently between incoming UP interface and outgoing UP interface. + +Before a MGW reverts from TrFO break operation (for example during handover or relocation where the rate control procedures may have been operating independently between each UP interface) the FPIF may perform rate control procedures to each UP peer. It shall then use the Maximum rate and Current rate settings from the opposite UP configurations. This is performed to align the UP's on each side of the MGW to enable relaying of all subsequent PDUs as described above. + +Optionally, the UP layer protocol entity on the sending side may substitute the frame number received in a status request by another number, but shall then substitute the initial number back in the status indication containing the acknowledgement. Figure A.2 shows an example of the relay of the rate control procedure. + + + +``` + +sequenceDiagram + participant Iu UP entity + participant Relay Function + participant Nb UP entity + + Note left of Iu UP entity: RC(0) + Iu UP entity->>Relay Function: RC(0) + Relay Function->>Nb UP entity: RC(0) + Nb UP entity->>Nb UP entity: RC(0) + Nb UP entity->>Nb UP entity: RC-NACK(0) + Nb UP entity->>Nb UP entity: RC(1) + Nb UP entity->>Nb UP entity: RC-ACK(1) + Nb UP entity->>Relay Function: RC-ACK(0) + Relay Function->>Iu UP entity: RC-ACK(0) + Note right of Nb UP entity: Not the same frame number as received in the status request + Note right of Nb UP entity: Frame number 0 is substituted back in the status indication + +``` + +The diagram shows a sequence of messages between three entities: Iu UP entity, Relay Function, and Nb UP entity. The sequence starts with an external RC(0) message arriving at the Iu UP entity. The Iu UP entity sends an RC(0) message to the Relay Function, which in turn sends an RC(0) message to the Nb UP entity. The Nb UP entity then sends three internal messages: RC(0), RC-NACK(0), and RC(1). It also receives an RC-ACK(1) message from itself. The Nb UP entity then sends an RC-ACK(0) message to the Relay Function, which finally sends an RC-ACK(0) message to the Iu UP entity. Two callouts from the Nb UP entity indicate that the frame number in the RC-ACK(0) message is not the same as received in the status request and that frame number 0 is substituted back in the status indication. + +Sequence diagram illustrating the relay of a control procedure between an Iu UP entity, a Relay Function, and an Nb UP entity. + +Figure A.2: Relay of a control procedure + +### A.3.2 Time Alignment + +Time alignment frames shall be relayed unmodified. + +## Annex B (informative): Examples for Usage of the 3GUP Package "Initialization Direction" Property + + + +Figure B.1: 3G to 3G Call (A to B), originating RAB established after Nb bearer, same codec configuration on originating Iu and Nb bearers. The diagram shows a sequence of messages between an RNC (RNC A), two MGWs (MGW A and MGW B), and another RNC (RNC B). MGW A has an 'Incoming' Iu bearer and an 'Outgoing' Nb bearer. MGW B has an 'Incoming' Nb bearer and an 'Outgoing' Iu bearer. The RAB is established after the Nb bearer is set up. + +**Figure B.1: 3G to 3G Call (A to B), originating RAB established after Nb bearer, same codec configuration on originating Iu and Nb bearers** + +NOTE: The Initialization Direction property of the Nb termination of MGW A could alternatively be set to 'Outgoing', but different RFCIs may then be initialized on the Iu and Nb bearers. + + + +Figure B.2: 3G Originating Call, originating RAB established after Nb bearer, same codec configuration on originating Iu and Nb bearers. This diagram is similar to Figure B.1 but shows a different message sequence for an originating call where the RAB is established after the Nb bearer. + +**Figure B.2: 3G Originating Call, originating RAB established after Nb bearer, same codec configuration on originating Iu and Nb bearers** + +NOTE: The Initialization Direction property of the Nb termination of MGW A could alternatively be set to 'Outgoing', but different RFCIs may then be initialized on the Iu and Nb bearers. + + + +Figure B.3: 3G Terminating Call. The diagram shows a sequence of messages between an RNC (RNC A), two MGWs (MGW A and MGW B), and another RNC (RNC B). MGW A has an 'Incoming' Iu bearer and an 'Outgoing' Nb bearer. MGW B has an 'Incoming' Nb bearer and an 'Outgoing' Iu bearer. The RAB is established before the Nb bearer is set up. + +**Figure B.3: 3G Terminating Call** + + + +Figure B.4: 3G to 3G Call (A to B), originating RAB established before or in parallel to the Nb bearer or different codec configuration on originating Iu and Nb bearers. The diagram shows a sequence of messages between an RNC (RNC A), two MGWs (MGW A and MGW B), and another RNC (RNC B). MGW A has an 'Incoming' Iu bearer and an 'Outgoing' Nb bearer. MGW B has an 'Incoming' Nb bearer and an 'Outgoing' Iu bearer. The RAB is established before or in parallel to the Nb bearer. + +**Figure B.4: 3G to 3G Call (A to B), originating RAB established before or in parallel to the Nb bearer or different codec configuration on originating Iu and Nb bearers** + + + +This diagram illustrates a 3G originating call flow. It consists of four main components connected in a linear sequence: RNC, SMGW, GMGW, and PSTN. The RNC is connected to the SMGW via an 'Iu' interface. The SMGW is connected to the GMGW via an 'Nb' interface. The GMGW is connected to the PSTN. Above the SMGW, there are two labels: 'Incoming' and 'Outgoing'. Above the GMGW, there is a label: 'Incoming'. + +Diagram of a 3G originating call flow from RNC to PSTN via SMGW and GMGW. + +Figure B.5: 3G Originating Call, originating RAB established before or in parallel to the Nb bearer or different codec configuration on originating Iu and Nb bearers + + + +This diagram illustrates a 2G to 2G call flow. It consists of four main components connected in a linear sequence: BSC A, MGW A, MGW B, and BSC B. The BSC A is connected to the MGW A via an 'A' interface. The MGW A is connected to the MGW B via an 'Nb' interface. The MGW B is connected to the BSC B via an 'A' interface. Above the MGW A, there is a label: 'Outgoing'. Above the MGW B, there is a label: 'Incoming'. + +Diagram of a 2G to 2G call flow from BSC A to BSC B via MGW A and MGW B. + +Figure B.6: 2G to 2G Call (A to B) + +## Annex C (Normative): Profile description + +### C.1 Profile Identification + +| | | +|----------------------|--------------------| +| Profile name: | Threegbicsn | +| Version: | 7 | + +*The name and version of the profile that is sent in the service change command.* + +### C.2 Summary + +This Profile describes the minimum mandatory settings and procedures required to fulfil the requirements of the Mc interface media gateway control. In addition optional settings and procedures are described which fulfil optional features and where supported, the minimum mandatory settings within the optional procedures and packages are identified that must be supported in order to support that feature. + +"Optional" or "O" means that it is optional for either the sender or the receiver to implement an element. If the receiving entity receives an optional element that it has not implemented it should send an Error Code (e.g. 445" Unsupported or Unknown Property", 501"Not Implemented", etc.). "Mandatory" or "M" means that it is mandatory for the receiver to implement an element. Whether it is mandatory for the sender to implement depends on specific functions; detail of whether elements of the core protocol are mandatory to be sent are defined in the stage 2 procedures, stage 3 procedures and/or the descriptions of individual packages. + +The setting or modification of elements described in the profile under the heading "Used in Command" has the meaning that the property can be set/modified with that command. The property may be present in other commands (in order to preserve its value in accordance with ITU-T H.248.1[10]) when those commands are used for other procedures that affect the same descriptor. + +This profile supports Explicit Congestion Notification and Multimedia Priority Service. + +### C.3 Gateway Control Protocol Version + +#### ITU Recommendation H.248.1 Version 2 + +*The minimum H.248 version required to support the profile. This should be based upon base syntax support and not an arbitrary version assignment. This is related to the ServiceChangeVersion in clause C.8.8.* + +### C.4 Connection Model + +**Table C.4: Connection Model** + +| | | +|------------------------------------------------------------|----------------| +| Maximum number of contexts: | No restriction | +| Maximum number of terminations per context: | 32 | +| Allowed termination type combinations in a context: | All | + +## C.5 Context Attributes + +**Table C.5/1: Context attributes** + +| Context Attribute | Supported | Values Supported | +|---------------------------------------------|-------------------|--------------------------------------| +| Topology | Yes (NOTE 1) | See clause C.7.8 Topology Descriptor | +| Priority Indicator | Optional (NOTE 3) | 0-15 (NOTE 4) | +| Emergency Indicator | Yes | NA | +| IEPS Indicator (NOTE 2) | No | NA | +| ContextAttribute Descriptor (NOTE 2) | No | NA | +| ContextIDList Parameter (NOTE 2) | No | NA | + +NOTE 1: Stream ID in Topology Descriptor shall not be supported. +NOTE 2: This field requires at least version 3 of the H.248.1 protocol. +NOTE 3: This Context Attribute parameter is used for MPS as specified in 3GPP TS 22.153 [78]. +NOTE 4: Priority values 11 – 15 of the Priority Indicator are reserved for MPS. + +**Table C.5/2: AND/OR Context attributes** + +| AND/OR Context Attribute | No | NA | +|-----------------------------------------------------------------------|----|----| +| NOTE: This field requires at least version 3 of the H.248.1 protocol. | | | + +## C.6 Terminations + +### C.6.1 Termination Names + +#### C.6.1.1 General + +The Termination ID structure shall follow the guidelines of H.248 and the structure is either relevant or irrelevant for MGC and MGW. + +The relevance depends on the utilized bearer type for termination. With ephemeral ATM/AAL2 and IP endpoint bearer types the internal structure of Termination ID is irrelevant for MGW and MGC and therefore Termination ID is only numeric identifier for termination. When bearer type is physical timeslot within TDM circuit the Termination ID structure shall follow the Termination naming convention for TDM circuit bearer. + +Ephemeral terminations are further denoted in the profile by the following: + +- BICC (meaning applies to terminations towards BICC) +- BICC ATM (meaning applies to terminations towards BICC with ATM transport) +- BICC IP (meaning applies to terminations towards BICC with IP transport) +- Iu (meaning applies to terminations towards Iu interface) +- RTP (meaning applies to all IP terminations, e.g. SIP-I/Nb, Mb, AoIP) +- RTP-CN (meaning applies to terminations towards SIP-I) +- RTP-A (meaning applies to terminations towards A interface over IP) + +**Editor's Note:** it is FFS if specific handling in the profile for the RTP-CN or RTP-A types is needed. + +#### C.6.1.2 ASN.1 Coding + +##### C.6.1.2.1 General Structure + +The following general structure of termination ID shall be used: + +4 octets shall be used for the termination ID. The following defines the general structure for the termination ID: + +**Table C.6.1.2.1: ASN.1 coding** + +| | | +|------------------|---| +| Termination type | X | +|------------------|---| + +Termination type: + +- Length 3 bits +- Values: + + - 000 Reserved + - 001 Ephemeral termination + - 010 TDM termination + - 011 - 110 Reserved + - 111 Reserved for ROOT termination Id (ROOT Termination ID = 0xFFFFFFFF) + +X: + +- Length 29 bits. +- Usage dependent on Termination type. TDM terminations specified below in subclause C.6.1.2.2. Other usage un-specified. + +## C.6.1.2.2 Termination naming convention for TDM terminations + +**Table C.6.1.2.2 ASN.1 coding** + +| | | | +|--------------------------|------------|------------| +| Termination type (=010 ) | PCM system | Individual | +|--------------------------|------------|------------| + +PCM system: + +- Length 24 bits +- Usage unspecified. Uniquely identifies PCM interface in MGW + +Individual: + +- Length: 5 bits +- Max. of 32 individuals (timeslots) per PCM system (max. 24 for a 24 channel system) + +## C.6.1.3 ABNF Coding + +### C.6.1.3.1 General Structure + +The following general structure of termination ID shall be used: + +TerminationID = "ROOT" / pathName / "\$" / "\*" ; According to H.248.1 annex B + +### C.6.1.3.2 Termination naming convention for TDM terminations + +pathName = TDToken UNDERSCORE ((PCMsystem / "\*") SLASH (Individual / "\*")) + +TDToken = "TDM" + +UNDERSCORE = %x5F ;"\_" + +PCMsystem : Usage not specified + +Individual = 1 \* 2 (DIGIT) ; 0-31 + +### C.6.1.3.3 Termination naming convention for Ephemeral terminations + +pathName = EphTokenUNDERSCORE(EPHsystem/"\*") + +EphToken = "Ephemeral" + +UNDERSCORE = %x5F ; "\_" + +EPHsystem : Usage is not specified + +## C.6.2 Multiplexed terminations + +Table C.6.2: Multiplexed terminations + +| | | +|-----------------------------------|----| +| Multiplex terminations supported? | No | +|-----------------------------------|----| + +## C.7 Descriptors + +### C.7.1 Stream Descriptor + +Table C.7.1: Stream descriptors + +| | | | +|------------------------------------------------|-----|---| +| Maximum number of streams per termination type | All | 1 | +|------------------------------------------------|-----|---| + +#### C.7.1.1 LocalControl Descriptor + +Table C.7.1.1/1: Local Control Descriptor + +| | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|------------------|----------------| +| If not generic list appropriate termination and stream types. | | Termination Type | Stream Type | +| ReserveGroup used: | No | - | - | +| ReserveValue used: | Yes | BICC (NOTE), RTP | Not Applicable | +| NOTE: The support is needed for the optional procedures Modify Char (see 14.2.27) and Reserve Char (see 14.2.28). These procedures use Q.1950 procedures which define the use of the Reserve Value. | | | | + +Table C.7.1.1/2: Allowed Stream Modes + +| Termination Type | Stream Type | Allowed StreamMode Values | +|------------------|----------------|----------------------------------------| +| All | Not Applicable | SendOnly, RecvOnly, SendRecv, Inactive | + +### C.7.2 Events Descriptor + +All events contained in this profile may be set on any termination/stream with the following exceptions. + +Table C.7.2/1: Events Descriptor + +| | | | | +|--------------------------------------------------------|--------------------------------|------------------|----------------| +| Events settable on termination types and stream types: | Yes | | | +| If yes | EventID | Termination Type | Stream Type | +| | Cause (g/cause, 0x0001/0x0001) | All except ROOT | Not Applicable | + +| | | | +|------------------------------------------------------------------------------------|-----------------|-----------------------------------| +| Signal Completion (g/sc, 0x0001/0x0002) | All except ROOT | Not Applicable | +| Start tone detected (tonedet/std, 0x0004/0x0001) | All except ROOT | Not Applicable | +| End Tone detected (tonedet/etd, 0x0004/0x0002) | All except ROOT | Not Applicable | +| DTMF character 0 (dd/d0, 0x0006/0x0010) to DTMF character D (dd/dd, 0x0006/0x001d) | All except ROOT | Not Applicable | +| Completion (ct/cmp, 0x000a/0x0005) | TDM | Not Applicable | +| BNC Change (GB/BNCChange, 0x0021/0x01) | BICC, lu | Not Applicable | +| Tunnel Indication (BT/TIND, 0x0022/0x01) | BICC IP | Not Applicable | +| MGCon (chp/mgcon, 0x0029/0x0001) | ROOT | Not Applicable | +| Termination Heartbeat (hangterm/thb, 0x0098/0x0001) | All except ROOT | Not Applicable | +| Protocol Negotiation Result: (threeegcsd/protres, 0x0030/0x0001) | All except ROOT | Not Applicable | +| Rate Change (threeegcsd/ratechg, 0x0030/0x0002) | All except ROOT | Not Applicable | +| Optimal Codec Event (threeegfoc/codec_modify, 0x0031/0x0010) | All except ROOT | Not Applicable | +| Codec List Event (threeegfoc/distant_codec_list, 0x0031/0x0012) | All except ROOT | Not Applicable | +| TFO Status Event (threeegfoc/TFO_status, 0x0031/0x0014) | All except ROOT | Not Applicable | +| Bearer Modification Support Event (threeegmlc/mod_link_supp, 0x0046/0x0001) | lu | Not Applicable | +| Connection State Change (threeegctm/connchange, 0x0068/0x0001) | All except ROOT | Not Applicable | +| Trace result (calltrace/ tracact, 0x0097/0x0001) | All except ROOT | Not Applicable | +| Inactivity Timeout (it/ito, 0x0045/0x0001) | ROOT | Not Applicable | +| Available Realms Changed (ipra/arc, 0x00e0/0x0001) | ROOT | Not Applicable | +| IP Flow Stop Detection (adid/ipstop, 0x009c/0x0001) | RTP-CN | Not Applicable | +| ECN Failure (ecnrous/fail, 0x010b/0x0001) | IP | Audio, Video | +| ICE New Peer Reflexive Candidate (ostuncc/nprc, 0x00c3/0x0002) | IP | Any, only applicable for full ICE | +| ICE Connectivity Check Result (ostuncc/ccr, 0x00c3/0x0001) | IP | Any, only applicable for full ICE | + +NOTE: Stream ID may be ignored in Events Descriptor + +Table C.7.2/2: Event Buffer Control + +| | | +|---------------------------|----| +| EventBuffer Control used: | No | +|---------------------------|----| + +Table C.7.2/3: Keep active + +| | | +|----------------------------|-----| +| KeepActive used on events: | Yes | +|----------------------------|-----| + +**Table C.7.2/4: Embedded events and signals** + +| | | +|--------------------------------------------------|----| +| Embedded events in an Events Descriptor: | No | +| Embedded signals in an Events Descriptor: | No | + +**Table C.7.2/5: Regulated Embedded events** + +| | | +|-----------------------------------------------------------------------|------| +| Regulated Embedded events are triggered on: | None | +| NOTE: This field requires at least version 3 of the H.248.1 protocol. | | + +**Table C.7.2/6: ResetEventsDescriptor** + +| | | +|-----------------------------------------------------------------------|------| +| ResetEventsDescriptor used with events: | None | +| NOTE: This field requires at least version 3 of the H.248.1 protocol. | | + +**Table C.7.2/7: Notification Behaviour** + +| | | +|-----------------------------------------------------------------------|------------| +| NotifyImmediate: | ALL Events | +| NotifyRegulated: | None | +| NeverNotify: | None | +| NOTE: This field requires at least version 3 of the H.248.1 protocol. | | + +### C.7.3 EventBuffer Descriptor + +**Table C.7.3: Event Buffer Descriptor** + +| | | +|-------------------------------------|----| +| EventBuffer Descriptor used: | No | +|-------------------------------------|----| + +## C.7.4 Signals Descriptor + +**Table C.7.4/1: Signals Descriptor** + +| | | | | +|-----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------------------| +| The setting of signals is dependant on termination or streams types: | Yes
NOTE: "No" means that all signals can be played on any termination or stream. If "Yes", any signal not listed below may be played on any termination or stream, except Signals on ROOT termination shall not be supported. | | | +| If yes | SignalID | Termination Type | Stream Type / ID | +| | Establish BNC (GB/EstBNC, 0x0021/0x01) | BICC | Not Applicable | +| | Modify BNC (GB/ModBNC, 0x0021/0x02) | BICC | Not Applicable | +| | Release BNC (GB/RelBNC, 0x0021/0x03) | BICC ATM | Not Applicable | +| | Bearer Information Transport (BT/BIT, 0x0022/0x01) | BICC IP | Not Applicable | +| | Continuity Test (ct/ct, 0x000a/0x0003) | TDM | Not Applicable | +| | Respond (ct/rsp, 0x000a/0x0004) | TDM | Not Applicable | +| | Send Additional Connectivity Check (ostuncc/sacc, 0x00c3/0x0002) | IP | Any, only applicable for full ICE | +| | Send Connectivity Check (ostuncc/scc, 0x00c3/0x0001) | IP | Any, only applicable for full ICE | +| NOTE: Stream ID may be ignored for Signals Descriptor | | | | + +**Table C.7.4/2: Signal Lists** + +| | | | +|-----------------------------------------------------------------------|------------------------------------------------------|-----------------| +| Signals Lists supported: | Yes | | +| If yes | Termination Type Supporting Lists: | ALL except ROOT | +| | Stream Type Supporting lists: | ALL | +| | Maximum number of signals to a signal list: | FFS
(NOTE) | No | +| NOTE: This field requires at least version 3 of the H.248.1 protocol. | | + +**Table C.7.4/6: Signals played simultaneously** + +| | | +|---------------------------------------|----| +| Signals played simultaneously: | No | +|---------------------------------------|----| + +**Table C.7.4/7: Keep active** + +| | | +|------------------------------------|-----| +| KeepActive used on signals: | Yes | +|------------------------------------|-----| + +## C.7.5 DigitMap Descriptor + +**Table C.7.5: DigitMap Descriptor** + +| | | +|-----------------------------|----| +| DigitMaps supported: | No | +|-----------------------------|----| + +## C.7.6 Statistics Descriptor + +**Table C.7.6/1: Statistics Descriptor support** + +| | | +|---------------------------------|-------------| +| Statistics supported on: | Termination | +|---------------------------------|-------------| + +**Table C.7.6/2: Statistics Report on Subtract** + +| | | | +|------------------------------------------|---------------------------------|----------------------------------------------------------------------------------------------------| +| Statistics reported on Substract: | Yes | | +| If yes | StatisticalIDs reported: | If Global Text Telephony used:
Characters Transferred (threeegctm/chartrans ,
0x0068/0x0001) | + +## C.7.7 ObservedEvents Descriptor + +**Table C.7.7: ObservedEvents Descriptor** + +| | | +|----------------------------------------|----| +| Event detection time supported: | No | +|----------------------------------------|----| + +## C.7.8 Topology Descriptor + +**Table C.7.8: Topology Descriptor** + +| | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------| +| Allowed triples: | (T1, T2, isolate) (T1, T2, oneway) (T1, T2, bothway) | +| NOTE: The Topology Descriptor shall be supported by the MGW and MGC for VGCS, VBS, handover and lawful interception. It can also be used for sending tones and playing announcements. | | + +## C.7.9 Error Descriptor + +Which H.248.8 and package defined error codes are supported? + +**Table C.7.9/1: Error Codes Sent by MGC** + +| | | +|---------------------------------------------------|--------------------------------------------------------------------------------------------------| +| Supported H.248.8 Error Codes: | ALL H.248.8, list of individual numbers> | +| Supported Error Codes defined in packages: | For a list of error codes see clauses 5.14.x
Media (LocalControl, Local And Remote), Error
When ADD commands exclude an Audit Descriptor, the MGW response shall only include descriptors which contained underspecified or overspecified properties in the command request. Furthermore, only those properties that were underspecified or overspecified in the request shall be sent in the reply. Exceptions to this rule are:
- - The Error Descriptor
- - SDP properties returned in "Reserve RTP Connection Point" and "Reserve and Configure RTP Connection Point" procedures, as specified in 14.2.51 and 14.2.53
The applicability of this restriction for text encoding is FFS.
| +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### C.8.2 Modify + +**Table C.8.2/1: Descriptors used by Command Modify Request** + +| | | +|--------------------------------------------|----------------------------------------------------------------| +| Descriptors used by Modify request: | Events, Signals, Media (LocalControl, Local And Remote), Audit | +|--------------------------------------------|----------------------------------------------------------------| + +**Table C.8.2/2: Descriptors used by Command Modify Reply** + +| | | +|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Descriptors used by Modify reply: |Media (LocalControl, Local And Remote), Error
When MOD commands exclude an Audit Descriptor, the MGW response shall only include descriptors which contained underspecified or overspecified properties in the command request. Furthermore, only those properties that were underspecified or overspecified in the request shall be sent in the reply. Exceptions to this rule are:
- - The Error Descriptor
- - SDP properties returned in "Configure RTP Connection Point" in 14.2.52.
The applicability of this restriction for text encoding is FFS.
| +|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### C.8.3 Subtract + +**Table C.8.3/1: Descriptor used by Command Subtract Request** + +| | | +|----------------------------------------------|------| +| Descriptors used by Subtract request: | None | +|----------------------------------------------|------| + +**Table C.8.3/2: Descriptor used by Command Subtract Reply** + +| | | +|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Descriptors used by Subtract reply: |None or Statistics
Ctmbits statistics are returned in the Subtract reply when related to a termination with CTM capabilities. Otherwise no statistics are returned.
| +|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +### C.8.4 Move + +**Table C.8.4/1: Command Move** + +| | | +|---------------------------|-----| +| Move command used: | Yes | +|---------------------------|-----| + +**Table C.8.4/2: Descriptors used by Move Request** + +| | | +|------------------------------------------|----------------------------------------------------------------| +| Descriptors used by Move request: | Events, Signals, Media (LocalControl, Local And Remote), Audit | +|------------------------------------------|----------------------------------------------------------------| + +**Table C.8.4/3: Descriptors used by Move Reply** + +| | | +|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Descriptors used by Move reply: | Media (LocalControl, Local And Remote), ErrorWhen MOVE commands exclude an Audit Descriptor, the MGW response shall only include descriptors which contained underspecified or overspecified properties in the command request, with the exception of the Error Descriptor. Furthermore, only those properties that were underspecified or overspecified in the request shall be sent in the reply.
The applicability of this restriction for text encoding is FFS. | +|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| + +## C.8.5 AuditValue + +**Table C.8.5: Auditvalue** + +| Audited Properties: | Property Name and Identity | Descriptor | +|--------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------| +| Termination ID | TerminationState:
- TDM: ALL (indicating 1 TDM group) , individual termination (NOTE2)
- ATM/IP: individual termination
- Root (MGW Audit) | TerminationState Descriptor | +| Termination ID | For Packages:
- Root | Packages Descriptor (NOTE1) | +| Termination ID | None (MGW Audit) :
- Root | Audit (empty) Descriptor | +| Termination ID | IP Realm Availability :
- ipra/* (ROOT) | TerminationState Descriptor | +| Termination ID | SDPCapNeg Extensions:
- sdpe/* | TerminationState Descriptor | +| Audited Statistics: | None | | +| Audited Signals: | None | | +| Audited Events: | None | | +| Packages Audit Possible | Yes | | + +NOTE1: Support of this capability is optional. +NOTE2: Auditing a single termination of a TDM group is an alternative to the wildcarded audit (TDM: ALL) to derive the service state of the TDM group (all the terminations of the TDM group share the same service state). + +## C.8.6 AuditCapability + +**Table C.8.6/1: Auditcapability** + +| Audited Properties: | Property Name and Identity | Descriptor | +|----------------------------|-----------------------------------|-------------------| +| | FFS | FFS | +| Audited Statistics: | None | | +| Audited Signals: | None | | +| Audited Events: | None | | + +**Table C.8.6/2: Scoped Auditing** + +| | | +|-------------------------------------------------------------------------|------| +| Audited Properties / ContextAttributes used for a scoped audit : | None | +| NOTE: This field requires at least version 3 of the H.248.1 protocol. | | + +## C.8.7 Notify + +**Table C.8.7: Descriptors Used Notify** + +| | | +|------------------------------------------------------------------|-----------------------| +| Descriptors used by Notify Request or Reply: | ObservedEvents, Error | +| NOTE : The Error Descriptor shall not be used in Notify Request. | | + +## C.8.8 ServiceChange + +**Table C.8.8/1: ServiceChangeMethods and ServiceChangeReasons sent by MGC:** + +| Service Change Methods Supported: | ServiceChange Reasons supported: | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------| +| Restart (NOTE1) | "901 Cold Boot" (Optional)
"902 Warm Boot" (Optional) | +| Handoff (NOTE 1, NOTE 2) | "903 MGC Directed Change" (Mandatory) | +| Forced (NOTE1) | "905 Termination Taken Out Of Service" (Optional) | +| Graceful (NOTE1) | "905 Termination Taken Out Of Service" (Optional) | +| NOTE: When a Service Change command on the Root termination with a method other than Graceful is sent, the command shall always be sent as the only command in a message. The sending node shall always wait for the reply to a Service Change command on the Root termination with a method other than Graceful before sending further command requests. A Service Change command on the Root termination with method Graceful may be combined with other commands in a single message. | | +| NOTE1: ROOT Only. | | +| NOTE2: Not involving more than 1 MSC-S. This does not preclude the use of the MGCIId in a ServiceChange (Handoff) scenario, nor does it change the expected MG behaviour upon receipt of such a message, as the MGW has actually no means to differentiate whether the ServiceChangeMgCIId parameter that may be received in a ServiceChange (handoff) message relates to a logical MGC inside the same MSC server or is part of another MSC-Server. | | + +**Table C.8.8/2: ServiceChangeMethods and ServiceChangeReasons sent by MG:** + +| Service Change Methods Supported: | ServiceChange Reasons supported: | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Restart | "900 Service Restored" (Mandatory)
"901 Cold Boot" (Mandatory) (NOTE1)
"902 Warm Boot" (Mandatory) (NOTE1)
"910 Media Capability Failure " ALL except ROOT (Optional)
"913 Signal Capability Failure " ALL except ROOT (Optional)"914 Event Capability Failure " ALL except ROOT (Optional)
"916 Packages Change" (Optional)
"917 Capability Change "(Optional) | +| Graceful | "904 Termination Malfunction" , ALL except ROOT,(Mandatory)
"905 Termination Taken Out Of Service" , ALL,(Mandatory)
"906 Loss Of Lower Layer Connectivity" , ALL except ROOT,(Mandatory)
"907 Transmission Failure" , ALL except ROOT,(Mandatory)
"908 MG Impending Failure" ROOT only (Mandatory) | +| Forced | "904 Termination Malfunction", ALL except ROOT (Mandatory)
"905 Termination Taken Out Of Service" , Mandatory)
"906 Loss Of Lower Layer Connectivity" , ALL except ROOT (Mandatory)
"907 Transmission Failure" , ALL except ROOT (Mandatory)
"908 MG Impending Failure" ROOT only (Mandatory) | +| Handoff (NOTE 1, NOTE 2) | "903 MGC Directed Change" (Mandatory) | +| Disconnected (NOTE 1) | "900 Service Restored" (Mandatory)
"916 Packages Change" (Optional)
"917 Capability Change" (Optional) | +| NOTE: When a Service Change command on the Root termination with a method other than Graceful is sent, the command shall always be sent as the only command in a message. The sending node shall always wait for the reply to a Service Change command on the Root termination with a method other than Graceful before sending further command requests. A Service Change command on the Root termination with method Graceful may be combined with other commands in a single message. | | +| NOTE 1: ROOT Only. | | +| NOTE 2: In response to a MGC Ordered Re-Register. | | + +Table C.8.8/3: Service Change Address + +| | | +|-----------------------------------|----| +| ServiceChangeAddress used: | No | +|-----------------------------------|----| + +Table C.8.8/4: Service Change Delay + +| | | +|---------------------------------|----| +| ServiceChangeDelay used: | No | +|---------------------------------|----| + +Table C.8.8/5: Service Change Incomplete Flag + +| | | +|-----------------------------------------------------------------------|----| +| ServiceChange Incomplete Flag used: | No | +| NOTE: This field requires at least version 3 of the H.248.1 protocol. | | + +Table C.8.8/6: Service Change Version + +| | | +|----------------------------------------------|---| +| Version used in ServiceChangeVersion: | 2 | +|----------------------------------------------|---| + +Table C.8.8/7: Service Change Profile + +| | | +|----------------------------------------|-----| +| ServiceChangeProfile mandatory: | Yes | +|----------------------------------------|-----| + +Table C.8.8/8: Profile negotiation + +| | | +|---------------------------------------------|----| +| Profile negotiation as per H.248.18: | No | +|---------------------------------------------|----| + +## C.8.9 Manipulating and auditing context attributes + +Table C.8.9: Manipulating and auditing context attributes + +| | | +|----------------------------------------|---------------------------------------------------| +| Context Attributes Manipulated: | Topology, Emergency Indicator, Priority Indicator | +| Context Attributes Audited: | None | + +## C.9 Generic command syntax and encoding + +Table C.9.1: Encodings + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------| +| Supported Encodings: | Binary (optional) (NOTE 2)
Text (optional) (NOTE 1) | +| If binary encoding, is indefinite length encoding supported: | Yes (NOTE 3) | +|
NOTE 1: For a BICC network with IP transport and IPBCP is transported within H.248 messages, text encoding is not recommended to be used on Mc interface until ITU has resolved the contradiction in RFC2327 [34] and H.248.1 [10] on the usage of CR (ASCII carriage return 0x0d) and/or LF (ASCII newline 0x0a) characters e.g. in SDP these Characters are missing when using the currently specified "quotedString" type.
NOTE 2: Binary encoding is strongly recommended if only one encoding is selected to ensure interoperability.
NOTE 3: The binary encoding rules which are applicable to the defined Abstract Syntaxes are the Basic Encoding Rules for Abstract Syntax Notation One, defined in ITU-T Recommendation X.690 [41]. Specifically in accordance with ITU-T Recommendation X.690 [41] section 7.3, alternative encodings based on the definite and indefinite form of length are permitted by the basic encoding rules as a sender's option. Receivers shall support both alternatives.
| | + +## C.10 Transactions + +**Table C.10/1: Transactions per Message** + +| | | +|----------------------------------------------------------------------------------------------------------------------|----| +| Maximum number of TransactionRequests / TransactionReplies / TransResponseAcks / Segment Replies per message: | 10 | +|----------------------------------------------------------------------------------------------------------------------|----| + +**Table C.10/2: Commands per Transaction Requests** + +| | | +|-----------------------------------------------------------|-------------| +| Maximum number of commands per TransactionRequest: | Unspecified | +|-----------------------------------------------------------|-------------| + +**Table C.10/3: Commands per Transaction Reply** + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Maximum number of commands per TransactionReply: | Unspecified | +| NOTE: For auditing with wildcarded requests (e.g TDM E1) then the reply may include up to 32 commands to indicate the termination state) | | + +**Table C.10/4: Optional Commands** + +| | | +|-----------------------------------------------|-----| +| Commands able to be marked "Optional": | ALL | +|-----------------------------------------------|-----| + +**Table C.10/5: Commands for Wildcarded Responses** + +| | | +|---------------------------------------------------|------------------------------| +| Wildcarded responses may be requested for: | Modify, Subtract, AuditValue | +|---------------------------------------------------|------------------------------| + +**Table C.10/6: Procedures for Wildcarded Responses** + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------| +| Procedures that make use of wildcarded responses: | Release Bearer, Release Termination, Audit Value | +| NOTE: Used when multiple terminations are released with one command and in audit responses where multiple terminations are implied by the audit request. | | + +**Table C.10/7: Transaction Timers** + +| Transaction Timer: | Value | +|------------------------------------------|--------------| +| normalMGExecutionTime | Provisioned | +| normalMGCExecutionTime | Provisioned | +| MGOriginatedPendingLimit | Provisioned | +| MGCOOriginatedPendingLimit | Provisioned | +| MGProvisionalResponseTimerValue | Provisioned | +| MGCPProvisionalResponseTimerValue | Provisioned | + +## C.11 Messages + +The MGC/MGW shall be named according to the naming structure of the underlying transport protocol which carries the H.248 protocol. + +## C.12 Transport + +**Table C.12/1: Transport** + +| | | +|-----------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported Transports: |- 1) For pure IP connections, H.248/SCTP/IP should be used. In addition, to allow for flexible implementations of gateways and controllers in order to offer efficient use of SCTP associations the M3UA layer may also be added on top of SCTP
- 2) For pure ATM connections, H.248/MTP3b/SSCF/SSCOP/AAL5/ATM should be used.
- 3) For mixed IP&ATM connections, H.248/M3UA/SCTP/IP shall be used as the IP transport.
- 1. Inherent in Transport
- 2. H.248.14 (optional MGW-driven monitoring)
- 3. Empty AuditValue on Root (MGC-driven monitoring)
(NOTE 1) | v1 | +| Basic DTMF Generator Package (see ITU-T Recommendation H.248.1 [10] annex E.5) | dg, (0x0005) | v1 | +| DTMF Detection Package (see ITU-T Recommendation H.248.1 [10] annex E.6) | dd, (0x0006) | v1 | +| Generic Announcement Package (see ITU-T Recommendation H.248.7 [28]) – Fixed Announcements. | an, (0x001d) | v1 | +| TDM Circuit Package (see ITU-T Recommendation H.248.1 [10] annex E.13)
NOTE 2 | tdmc, (0x000d) | v1 | +| Media Gateway Resource Congestion Handling Package (see ITU-T Recommendation H.248.10 [15] ) | chp, (0x0029) | v1 | +| Hanging Termination Detection package (see ITU-T Recommendation H.248.36 [36]). | hangterm, (0x0098) | v1 | + +NOTE 1: This package is "for extension only" and shall not be published over the Mc interface. + +NOTE 2: Network Package is not supported. + +Table C.14/2: Optional packages + +| Optional Packages: | | | | +|-----------------------------------------------------------------------------------------------------------|----------------------|---------|---------------------------------------------| +| Package Name | PackageID | Version | Support dependent on: | +| Basic Call Progress Tones Generator with Directionality, (see ITU-T Recommendation Q.1950 [23] annex A.8) | bcg, (0x0023) | v1 | Services provided by network | +| Expanded Call Progress tones Generator Package (see ITU-T Recommendation Q.1950 [23] annex A.9) | xcg, (0x0024) | v1 | Services provided by network | +| Basic Services Tones Generation Package (see ITU-T Recommendation Q.1950 [23] annex A.10) | srvtn, (0x0025) | v1 | Services provided by network | +| Bearer Control Tunnelling Package (see ITU-T Recommendation Q.1950 [23] annex A.7) | Bt, (0x0022) | v1 | Interworking with BICC and IP transport | +| Expanded Services Tones Generation Package (see ITU-T Recommendation Q.1950 [23] annex A.11) | xsrvtn, (0x0026) | v1 | Services provided by network | +| Intrusion Tones Generation Package (see ITU-T Recommendation Q.1950 [23] annex A.12) | Int, (0x0027) | v1 | Services provided by network | +| Business Tones Generation Package (see ITU-T Recommendation Q.1950 [23] annex A.13) | BIZTN, (0x0028) | v1 | Services provided by network | +| Tone Generator Package (see ITU-T Recommendation H.248.1 [10] annex E.3) | tongen, (0x0003) | v1 | (NOTE) | +| Generic Announcement Package (see ITU-T Recommendation H.248.7 [28]) – Variable Announcements | an, (0x001d) | v1 | Variable Announcements | +| Text Telephony Package (see ITU-T Recommendation H.248.2 [17]). | txp, (0x0010) | v1 | Global text telephony support | +| Call Discrimination package (see ITU-T Recommendation H.248.2 [17]). | ctyp, (0x0011) | v2 | Global text telephony support | +| Basic Continuity Package (see ITU-T Recommendation H.248.1 [10] annex E.10). | ct, (0x000a) | v1 | Only required for TDM side terminations | +| Circuit Switched Data package (see subclause 15.2.1); | threegcd, (0x0030) | v1 | Circuit Switched Data support | +| TFO package (see subclause 15.2.2); | threegtfoc, (0x0031) | v2 | TFO support | +| 3G Expanded Call Progress Tones Generator package (see subclause 15.2.3); | threegxcg, (0x0032) | v1 | Services provided by network | +| Modification of Link Characteristics Bearer Capability package (see subclause 15.2.4); | threegmlc, (0x0046) | v1 | | +| Enhanced Circuit Switched Data package (see subclause 15.2.5); | threegcden,(0x0082) | v1 | Circuit Switched Data support | +| Cellular Text telephone Modem Text Transport package (see subclause 15.2.6); | threegctm, (0x0068) | v1 | Global text telephony support | +| Flexible Tone Generator Package (see subclause 15.2.8). | threegflex, (0x0084) | v1 | Services provided by network | +| Trace Package (see subclause 15.2.9) | calltrace, (0x0097) | v1 | | +| ASCI Group call package (see subclause 15.2.10) | threegasci, (0x00b2) | v2 | VGCS and VBS services supported | +| IP Domain connection package (see ITU-T Recommendation H.248.41 [42]) | ipdc, (0x009d) | v1 | Multiple IP realms supported | +| Inactivity timer package (see ITU-T Recommendation. H248.14 [45]) | it, (0x0045) | v1 | UDP transport supported | +| 3GUP (User Plane) package (see subclause 15.1.1) | threegup, (0x002f) | v1 | Mandatory for BICC and Iu terminations | +| Bearer Characteristics Package (see ITU-T Recommendation Q.1950 [23] annex A.3) | bcp, (0x001e) | v2 | Mandatory for BICC terminations | +| Generic Bearer Connection Package (see ITU-T Recommendation Q.1950 [23] annex A.6) | Gb, (0x0021) | v1 | Mandatory only for BICC and Iu terminations | +| 3G Interface Type package (see subclause 15.2.11) | threegint (0x00e3) | v1 | | +| RTP Control Protocol Package (ITU-T Recommendation H.248.57 [66]) | rtcp.h. (0x00b5) | v1 | Border control functions support | +| Gate management Source Address/Port Filtering Package (ITU-T Recommendation H.248.43, Clause 7 [67]) | gm, (0x008c) | v2 | Border control functions support | +| Traffic management (ITU-T Recommendation H.248.53 [69]) | tman, (0x008d) | v1 | Border control functions support | +| Diffserv (ITU-T Recommendation H.248.52 [70]) | ds, (0x008b) | v2 | Border control functions support | + +| | | | | +|----------------------------------------------------------------------------------------------------|-------------------|----|---------------------------------------------------------------------------------------| +| Application Data Inactivity Detection (ITU-T Recommendation H.248.40 [71]) | adid (0x009c) | v1 | Border control functions support | +| IP realm availability (ITU-T Recommendation H.248.41 Amendment 1) [72] | ipra (0x00e0) | v1 | Border control functions support | +| Explicit Congestion Notification for RTP-over-UDP Support (see ITU-T Recommendation H.248.82 [79]) | ecnrous(0x010b) | v1 | Support of ECN feature | +| MG Act-as STUN Server (ITU-T Recommendation H.248.50 [81]) | mgastuns (0x00c2) | v1 | Support of incoming STUN connectivity checks.
Applicable for ICE lite and full ICE | +| Originate STUN Continuity Check (see ITU-T Recommendation H.248.50 [81]) | ostuncc (0x00c3) | v1 | Support of originating STUN connectivity checks
Only applicable for full ICE | +| Enhanced Revised Offer/Answer SDP Support (ITU-T Recommendation H.248.80 [85]) | eroas, (0x0109) | v1 | Support of the SDP Capability Negotiation syntax | +| NOTE: This package is "for extension only" and shall not be published over the Mc interface. | | | | + +#### Package Usage Information + +This table specifies how the packages above will be used. For example: + +- it lists whether the properties/signals/events/statistics are optional or mandatory +- if the value of the property/signal/event provisioned the provisioned value should be specified. (e.g. names and number of cycles for an H.248.7 announcement). + +Specifies the values of properties which are specified as provisioned + +Package Usage Information: + +## C.14.1 Generic Package + +Table C.14.1: Package Usage Information For Generic Package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|------------------------------------------|--------------------------------------|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | - | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| | M | ADD, MOD, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| Cause (g/cause, 0x0001/0x0001) | General Cause (GeneralCause, 0x0001) | M | "NR" (0x0001) Normal Release
"UR" (0x0002) Unavailable Resources
"FT" (0x0003) Failure, Temporary
"FP" (0x0004) Failure, Permanent
"IW" (0x0005) Interworking Error
"UN" (0x0006) Unsupported | Not Applicable | | | +| | Failure Cause (FailureCause, 0x0002) | O | Octet String | Not Applicable | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| | M | ADD, MOD, MOVE, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| Signal Completion. (g/sc, 0x0001/0x0002) | Signal Identity (SigID, 0x0001) | M | pkgdName syntax | Not Applicable | | | +| | Termination Method (Meth, 0x0002) | M | "TO" (0x0001) Signal timed out or otherwise completed on its own
"EV" (0x0002) Interrupted by event
"SD" (0x0003) Halted by new Signals descriptor
"NC" (0x0004) Not completed, other cause | Not Applicable | | | +| | Signal List Id | O | Integer | Not Applicable | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +## C.14.2 Base Root Package + +Table C.14.2: Package Usage Information For Base Root Package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|--------------------------------------------------------------------------------------------|--------------------------|---------------------|------------------------------------------------------------|-----------------------------|--|--| +| MaxNrOfContexts
(root/numberOfContexts, 0x0002/0x0001) | O | Not used in command | 1 and up | Not Applicable | | | +| MaxTerminationsPerContext
(root/maxTerminationPerContext, 0x0002/0x0002) | O | Not used in command | See C.4 | Not Applicable | | | +| normalMGExecutionTime
(root/normalMGExecutionTime, 0x0002/0x0003) | O | Not used in command | Integer | Operator Defined | | | +| normalMGCEExecutionTime
(root/normalMGCEExecutionTime, 0x0002/0x0004) | O | Not used in command | Integer | Operator Defined | | | +| MGProvisionalResponseTimerValue
(root/MGProvisionalResponseTimerValue, 0x0002/0x0005) | O | Not used in command | Integer (initially NormalMGExecutionTime + networkdelay) | Operator Defined | | | +| MGCProvisionalResponseTimerValue
(root/MGCProvisionalResponseTimerValue, 0x0002/0x0006) | O | Not used in command | Integer (initially NormalMGCEExecutionTime + networkdelay) | Operator Defined | | | +| MGCOriGINatedPendingLimit
(root/MGCOriGINatedPendingLimit, 0x0002/0x0007) | O | Not used in command | Integer | Operator Defined | | | +| MGCOriGINatedPendingLimit
(root/MGCOriGINatedPendingLimit, 0x0002/0x0008) | O | Not used in command | Integer | Operator Defined | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.3 Tone Generator Package + +Table C.14.3: Package Usage Information For Tone Generator Package + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-----------------------------------------|---------------------------------|----------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| Play Tone
(tonegen/pt,0x0003/0x0001) | Not Used | - | - | - | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.4 Tone Detection Package + +Table C.14.4: Package Usage Information For Tone Detection Package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|--------------------------------------------------|---------------------------------|---------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | - | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| Start tone detected (tonedet/std, 0x0004/0x0001) | O | ADD, MOD, MOVE, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | Tone ID List (tl,0x0001) | M | wildcard | Not Applicable | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | Tone ID (tid,0x0003) | M | Value | Not Applicable | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| End Tone detected (tonedet/etd, 0x0004/0x0002) | M | ADD, MOD, MOVE, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | Tone ID List (tl,0x0001) | M | wildcard | Not Applicable | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | Tone ID (tid,0x0003) | M | Value | Not Applicable | | | +| | Duration (dur,0x0002) | O | Value | Not Applicable | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| Long Tone detected (tonedet/ltd, 0x0004/0x0003) | Not Used | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.5 Basic DTMF Generator Package + +Table C.14.5: Package Usage Information For Basic DTMF Generator Package + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-------------------------------------------|---------------------------------|----------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| DTMF character 0
(dg/d0,0x0005/0x0010) | M | ADD, MOD, MOVE | | | | | +| DTMF character 1
(dg/d1,0x0005/0x0011) | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| DTMF character 2
(dg/d2,0x0005/0x0012) | None | - | - | - | | | +| DTMF character 3
(dg/d3,0x0005/0x0013) | | | | | | | +| DTMF character 4
(dg/d4,0x0005/0x0014) | | | | | | | +| DTMF character 5
(dg/d5,0x0005/0x0015) | | | | | | | +| DTMF character 6
(dg/d6,0x0005/0x0016) | | | | | | | +| DTMF character 7
(dg/d7,0x0005/0x0017) | | | | | | | +| DTMF character 8
(dg/d8,0x0005/0x0018) | | | | | | | +| DTMF character 9
(dg/d9,0x0005/0x0019) | | | | | | | +| DTMF character *
(dg/ds,0x0005/0x0020) | | | | | | | +| DTMF character #
(dg/do,0x0005/0x0021) | | | | | | | +| DTMF character A
(dg/da,0x0005/0x001a) | | | | | | | +| DTMF character B
(dg/db,0x0005/0x001b) | | | | | | | +| DTMF character C
(dg/dc,0x0005/0x001c) | | | | | | | +| DTMF character D
(dg/dd,0x0005/0x001d) | | | | | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.6 Basic DTMF Detection Package + +Table C.14.6: Package Usage Information For Basic DTMF Generator Package + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | +|------------|---------------------|------------------|-------------------|--------------------| +| None | - | - | - | - | + +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +|-------------------------------------------|--------------------------|--------------------|-------------------|-----------------------------|--|--| +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| DTMF character 0
(dd/d0,0x0006/0x0010) | M | ADD, MOD, NOTIFY | | | | | +| DTMF character 1
(dd/d1,0x0006/0x0011) | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| DTMF character 2
(dd/d2,0x0006/0x0012) | None | - | - | - | | | +| DTMF character 3
(dd/d3,0x0006/0x0013) | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| DTMF character 4
(dd/d4,0x0006/0x0014) | None | - | - | - | | | +| DTMF character 5
(dd/d5,0x0006/0x0015) | | | | | | | +| DTMF character 6
(dd/d6,0x0006/0x0016) | | | | | | | +| DTMF character 7
(dd/d7,0x0006/0x0017) | | | | | | | +| DTMF character 8
(dd/d8,0x0006/0x0018) | | | | | | | +| DTMF character 9
(dd/d9,0x0006/0x0019) | | | | | | | +| DTMF character *
(dd/ds,0x0006/0x0020) | | | | | | | +| DTMF character #
(dd/d0,0x0006/0x0021) | | | | | | | +| DTMF character A
(dd/da,0x0006/0x001a) | | | | | | | +| DTMF character B
(dd/db,0x0006/0x001b) | | | | | | | +| DTMF character C
(dd/dc,0x0006/0x001c) | | | | | | | +| DTMF character D
(dd/dd,0x0006/0x001d) | | | | | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| | Not used | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.7 Continuity Package + +Table C.14.7: Package Usage Information For Basic Continuity Package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | +|------------|--------------------|------------------|-------------------|--------------------| +| None | - | - | - | - | + +| Signals | Mandatory/
Optional | Used in command: | | Duration Provisioned
Value: | | | +|---------------------------------------------------------------------------------------|-------------------------------------|--------------------------------|------------------------------|----------------------------------------|--|--| +| Continuity Test
(ct/ct,
0x000a/0x0003)
Respond
(ct/rsp,
0x000a/0x0004) | M | ADD, MOD, MOVE | | Default | | | +| | Signal Parameters | Mandatory/
Optional | Supported
Values: | Duration Provisioned
Value: | | | +| | None | - | - | - | | | +| Events | Mandatory/
Optional | Used in command: | | | | | +| Completion,
(ct/cmp,
0x000a/0x0005) | M | ADD, NOTIFY | | | | | +| | Event
Parameters | Mandatory/
Optional | Supported
Values: | Provisioned Value: | | | +| | None | - | - | - | | | +| | ObservedEvent
Parameters | Mandatory/
Optional | Supported
Values: | Provisioned Value: | | | +| | Result (res,0x0008) | M | success, failure | Not Applicable | | | +| Statistics | Mandatory/
Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.8 TDM Circuit Package + +Table C.14.8: Package Usage Information For TDM Circuit Package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-------------------------------------------|--------------------------|--------------------|-------------------|-----------------------------|--|--| +| Echo Cancellation (tdmc/ec,0x000d/0x0008) | M | ADD, MOD, MOVE | ALL | Default=off (False) | | | +| Gain Control (tdmc/gain,0x000d/0x000a) | Not Used | - | - | - | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.9 Text Telephony Package + +**Table C.14.9: Package Usage Information For Text Telephony Package** + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|---------------------------------------------------------------------------|--------------------------------------|------------------------|---------------------|-----------------------------|--|--| +| Conversation mode
(txp/convmode,
0x0010/0x0001) | O | ADD, MOD, MOVE | ALL | None | | | +| Communication Mode
(txp/commode,
0x0010/0x0002) | O | ADD, MOD, MOVE | ALL | None | | | +| Connection Mode
(txp/connmode,
0x0010/0x0003) | O | ADD, MOD, MOVE | ALL | None | | | +| Action at Loss of
Connection
(txp/lossconnection,
0x0010/0x0006) | O | ADD, MOD, MOVE | ALL | None | | | +| V18 Options
(txp/v18opt,
0x0010/0x0007) | O | ADD, MOD, MOVE | ALL | None | | | +| Character Set
(txp/characterset,
0x0010/0x0008) | O | ADD, MOD, MOVE | ALL | None | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| Connection Mode Changed
(txp/connchg,
0x0010/0x0001) | O | ADD, MOD, MOVE, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | - | | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | Communication Mode (commode, 0x0002) | O | As property commode | - | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| Number of Characters Transferred
(txp/chartrans,
0x0010/0x0001) | O | SUBTRACT | | | | | +| Number of Alternating Turns
(txp/altturns,
0x0010/0x0002) | O | SUBTRACT | | | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.10 Call Discrimination Package + +Table C.14.10: Package Usage Information For Call Discrimination Package + +| Properties | Mandatory/
Optional | Used in
command: | Supported
Values: | Provisioned
Value: | +|-----------------------------------------------------------------------------------|------------------------------------------------------|------------------------|----------------------|-----------------------------------| +| Call Types (ctyp/calltyp, 0x0011/0x0001) | O | ADD, MOD, MOVE | ALL | None | +| Text Call Types (ctyp/ttyp, 0x0011/0x0002) | O | ADD, MOD, MOVE | ALL | None | +| V8bis Support (ctyp/v8bsup, 0x0011/0x0003) | O | ADD, MOD, MOVE | ALL | None | +| Probe Message (ctyp/probmsg, 0x0011/0x0004) | O | ADD, MOD, MOVE | ALL | None | +| Probe Order (ctyp/probeorder, 0x0011/0x0005) | O | ADD, MOD, MOVE | ALL | None | +| Phase Reversal Detect (ctyp/phrevdet, 0x0011/0x0006) | O | ADD, MOD, MOVE | ALL | None | +| MG Responsible for Call Discrimination Signalling (ctyp/MGCallSig, 0x0011/0x0007) | O | ADD, MOD, MOVE | ALL | None | +| Signals | Mandatory/
Optional | Used in command: | | Duration
Provisioned
Value: | +| V8 Signal (ctyp/v8sig, 0x0011/0x0001) | O | MOD | | - | +| | Signal Parameters | Mandatory/
Optional | Supported
Values: | Duration
Provisioned
Value: | +| | V.8 Signal Type (ctyp/v8styp, 0x0011/0x0001) | O | ALL | - | +| | V8Sig Cont (ctyp/v8scont, 0x0011/0x0002) | O | ALL | - | +| | V18 XCI Enable (ctyp/v18xcien, 0x0011/0x0003) | O | ALL | - | +| Answer Signal (ctyp/ans, 0x0011/0x0002) | O | MOD | | - | +| | Signal Parameters | Mandatory/
Optional | Supported
Values: | Duration
Provisioned
Value: | +| | ANS Type (ctyp/AnsType, 0x0011/0x0001) | O | ALL | - | +| Calling Signal (ctyp/callsig, 0x0011/0x0003) | O | MOD | | - | +| | Signal Parameters | Mandatory/
Optional | Supported
Values: | Duration
Provisioned
Value: | +| | Call Signal Name (ctyp/csn, 0x0011/0x0001) | O | ALL | - | +| V8bis Signal | O | MOD | | - | +| | Signal Parameters | Mandatory/
Optional | Supported
Values: | Duration
Provisioned
Value: | +| | V8bisSigname (ctyp/V8bsn, 0x0011/0x0001) | O | ALL | - | +| | V8bis Signal Contents (ctyp/V8bscont, 0x0011/0x0002) | O | ALL | - | +| V18 Probe (ctyp/v18prob, 0x0011/0x0005) | O | MOD | | - | +| | Signal Parameters | Mandatory/
Optional | Supported
Values: | Duration
Provisioned
Value: | +| | None | - | - | - | + +| Events | Mandatory/
Optional | Used in command: | | | | | +|---------------------------------------------------------------------|------------------------------------------------|--------------------------------|------------------------------|-------------------------------|--|--| +| Discriminating Tone Detected
(ctyp/dtone, 0x0011/0x0001) | O | ADD, MOD, NOTIFY | | | | | +| | Event
Parameters | Mandatory/
Optional | Supported
Values: | Provisioned
Value: | | | +| | None | - | - | - | | | +| | ObservedEvent
Parameters | Mandatory/
Optional | Supported
Values: | Provisioned
Value: | | | +| | Discriminating Tone Type
(dtt,0x0001) | O | ALL | - | | | +| | Discriminating Tone Value
(dtvalue, 0x0002) | O | ALL | - | | | +| | V8bis Type (v8bist,
0x0003) | O | ALL | - | | | +| Call Type Discrimination Result
(ctyp/calldisres, 0x0011/0x0002) | O | ADD, MOD, NOTIFY | | | | | +| | Event
Parameters | Mandatory/
Optional | Supported
Values: | Provisioned
Value: | | | +| | None | - | - | - | | | +| | ObservedEvent
Parameters | Mandatory/
Optional | Supported
Values: | Provisioned
Value: | | | +| | Discriminated Call Type
(dct,0x0001) | O | ALL | - | | | +| Statistics | Mandatory/
Optional | Used in command: | | Supported
Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.11 Announcement Package + +Table C.14.11: Package Usage Information For Announcement Package + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|----------------------------------------------------|--------------------------------------------------|----------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| Fixed Announcement Play (an/apf, 0x001d/0x0001) | M | ADD, MOD, MOVE | |
(BCP/BNCChar,0x001e/0x01) | M | ADD | AAL type 2 /
IP/RTP | Not Applicable | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.15 Generic Bearer Connection Package + +Table C.14.15: Package Usage Information For Generic Bearer Connection Package + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | +|-------------------------------------------|--------------------------------------|----------------------------|--------------------------------------------------------------------------------------------------------------------------------|------------------------------------| +| None | - | - | - | - | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | +| Establish BNC
(GB/EstBNC, 0x0021/0x01) | M | | ADD, MOD | Not Applicable | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | +| | Not Applicable | - | - | Not Applicable | +| Modify BNC
(GB/ModBNC, 0x0021/0x02) | O | | MOD | Not Applicable | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | +| | Not Applicable | - | - | Not Applicable | +| Release BNC
(GB/RelBNC, 0x0021/0x03) | M (NOTE) | | MOD | Not Applicable | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | +| | General cause
(Generalcause,0x01) | O | Normal Release/
Unavailable
Resources/ Failure
Temporary/ Failure
Permanent/
Interworking Error/
Unsupported | Not Applicable | +| | Failure Cause
(Failurecause,0x02) | O | OCTET STRING | Not Applicable | +| | Reset (Reset,0x03) | O | 0/ 1 | Not Applicable | +| Events | Mandatory/ Optional | Used in command: | | | +| BNC Change
(GB/BNCChange, 0x0021/0x01) | M | | ADD, MOD, NOTIFY | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | +| | Type (Type ,0x01) | M | Bearer Established /
Bearer Modified/
Bearer Modification
Failure | Not Applicable | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | +| | Type (Type,0x01) | M | Bearer Established /
Bearer Modified/
Bearer Modification
Failure | Not Applicable | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | +| None | - | | - | - | +| Error Codes | Mandatory/ Optional | | | | +| None | - | | | | + +NOTE: Mandatory for BICC ATM Terminations. If received as part of a wildcarded command including other types of terminations then for other type of terminations no action is required from MGW, but a successful command reply. + +## C.14.16 Bearer Control Tunneling Package + +Table C.14.16: Package Usage Information For Bearer Control Tunneling Package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|----------------------------------------------------|------------------------------------------|---------------------------|--------------------------|------------------------------------|--|--| +| Tunneling Options (BT/TunOpt, 0x0022/0x01) | M | ADD | 1 /2 | Not Applicable | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| Bearer Information Transport (BT/BIT, 0x0022/0x01) | M | ADD, MOD | | Not Applicable | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | Bearer Information Tunnel (BIT, 0x01) | M | Octet String | Not Applicable | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| Tunnel Indication (BT/TIND, 0x0022/0x01) | M | ADD, MOD, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | Not applicable | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | Bearer Information transport (BIT, 0x01) | M | Octet String | Not Applicable | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.17 Basic Call Progress Tones Generator with Directionality + +**Table C.14.17: Package Usage Information For Basic Call Progress Tones Generator with Directionality Package** + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|---------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| Dial Tone (bcg/bdt, 0x0023/0x0040)
Ringing Tone (bcg/brt, 0x0023/0x0041)
Busy Tone (bcg/bbt, 0x0023/0x0042)
Congestion Tone (bcg/bct, 0x0023/0x0043)
Special Information Tone (bcg/bsit, 0x0023/0x0044)
Warning Tone (bcg/bwt, 0x0023/0x0045)
Payphone Recognition Tone (bcg/bpt, 0x0023/0x0046)
Call Waiting Tone (bcg/bcw, 0x0023/0x0047)
Caller Waiting Tone (bcg/bcr, 0x0023/0x0048)
Pay Tone (bcg/bpy, 0x0023/0x0049) | O | ADD, MOD, MOVE | | Value | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | Tone Direction (btd, 0x0001) | M | Internal / External | Default=External | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.18 Expanded Call Progress Tones Generator Package + +**Table C.14.18: Package Usage Information For Expanded Call Progress Tones Generator Package** + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| Comfort Tone (xcg/cmft,0x0024/0x004a)
Off-hook warning Tone (xcg/roh, 0x0024/0x004b)
Negative Acknowledgement (xcg/nack,0x0024/0x004c)
Vacant Number Tone (xcg/vac, 0x0024/0x004d)
Special Conditions Dial Tone (xcg/spec,0x0024/0x004e) | O | ADD, MOD, MOVE | | Value | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | Tone Direction (btd, 0x0001) | M | Internal / External | Default=External | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.19 Basic Services Tones Generation Package + +Table C.14.19: Package Usage Information For Basic Services Tones Generation Package + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| Recall Dial Tone
(srvtn/rdt,0x0025/0x004f)
Confirmation Tone
(srvtn/conf,0x0025/0x0050)
Held Tone
(srvtn/ht,0x0025/0x0051)
Message Waiting Tone
(srvtn/mwt,0x0025/0x0052) | O | ADD, MOD, MOVE | | Value | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | Tone Direction
(btd, 0x0001) | M | Internal / External | Default=External | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.20 Expanded Services Tones Generation Package + +Table C.14.20: Package Usage Information For Expanded Services Tones Generation Package + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| Call Transfer Dial Tone (xsrvtm/xferdt,0x0026/0x0053)
Call Forward Tone (xsrvtm/cft,0x0026/0x0054)
Credit Card service Tone (xsrvtm/ccst,0x0026/0x0055)
Special Recall Dial Tone (xsrvtm/srdt,0x0026/0x0056) | O | ADD, MOD, MOVE | | Value | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | Tone Direction (btd, 0x0001) | M | Internal / External | Default=External | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | | - | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.21 Intrusion Tones Generation Package + +Table C.14.21: Package Usage Information For Intrusion Tones Generation Package + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|----------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| Intrusion Pending Tone (int/pend,0x0027/0x0057)
Intrusion Tone (int/int,0x0027/0x0058)
Intrusion Reminder Tone (int/rem,0x0027/0x0059)
Toll Break-In Tone (int/tbi,0x0027/0x005a)
Intrusion Queue Tone (int/intque,0x0027/0x005b)
Busy Verification Tone (int/bv,0x0027/0x005c) | O | ADD, MOD, MOVE | | Value | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | Tone Direction (btd, 0x0001) | M | Internal / External | Default=External | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.22 Business Tones Generation Package + +Table C.14.22: Package Usage Information For Business Tones Generation Package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|---------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| Off-Hook Queuing Tone (biztn/ofque,0x0028/0x005d)
Expensive Route Warning Tone (biztn/erwt,0x0028/0x005e)
Distinctive Dial Tone (biztn/ddt,0x0028/0x005f)
Internal Dial Tone (biztn/idt,0x0028/0x0060) | O | ADD, MOD, MOVE | | Value | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | Tone Direction (btd, 0x0001) | M | Internal / External | Default=External | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.23 3GUP Package + +Table C.14.23: Package Usage Information For 3GUP Package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-------------------------------------------------------------------|--------------------------|--------------------|-------------------|-----------------------------|--|--| +| UP Mode of operation
(threegup/mode, 0x002f/0x0001) | M | ADD, MOD, MOVE | ALL | Default=1 (transparent) | | | +| UP versions
(threegup/upversions, 0x002f/0x0002) | M | ADD, MOD, MOVE | 1, 2 | Default = 1 | | | +| Delivery of erroneous SDUs
(threegup/delerrsdu, 0x002f/0x0003) | M | ADD, MOD, MOVE | ALL | Default = 3 (NA) | | | +| Interface
(threegup/interface, 0x002f/0x0004) | M | ADD, MOD, MOVE | ALL | None | | | +| Initialisation Direction
(threegup/initdir, 0x002f/0x0005) | M | ADD, MOD, MOVE | ALL | None | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.24 Modification of Link Characteristics Bearer Capability + +Table C.14.24: Package Usage Information For Modification of Link Characteristics Package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | +|------------------------------------------------------------------------------|---------------------------------|---------------------------|--------------------------|------------------------------------| +| None | - | - | - | - | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | +| None | - | - | - | - | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | +| | - | - | - | - | +| Events | Mandatory/Optional | Used in command: | | | +| Bearer Modification Support Event. ( threegmlc/mod_link_supp, 0x0046/0x0001) | M | ADD, MOD, MOVE NOTIFY | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | +| | None | - | - | - | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | +| | None | - | - | - | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | +| None | - | - | - | - | +| Error Codes | Mandatory/ Optional | | | | +| None | - | | | | + +## C.14.25 TFO package + +Table C.14.25: Package Usage Information For TFO + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|--------------------------------------------------------------------|--------------------------|------------------------|----------------------------|-----------------------------|--|--| +| TFO Activity Control (threegtfoc /tfoenable, (0x0031/0x0001)) | M | ADD, MOD, MOVE | ALL | None (default =Off) | | | +| TFO Codec List (threegtfoc /codeclist, (0x0031/0x0002)) | M | ADD, MOD, MOVE | See 3GPP TS 29.232 §15.2.2 | None | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| Optimal Codec Event (threegtfoc /codec_modify, (0x0031/0x0010)) | O | ADD, MOD, MOVE, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | | | | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| Codec List Event (threegtfoc /distant_codec_list, (0x0031/0x0012)) | O | ADD, MOD, MOVE, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | | | | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| TFO Status Event (threegtfoc /TFO_status) (0x0031/0x0014) | O | ADD, MOD, MOVE, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | | | | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| | - | | | | | | + +## C.14.26 Circuit Switched Data package + +Table C.14.26: Package Usage Information For CSD + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|--------------------------------------------------------------------|------------------------------------|--------------------|----------------------------------------------------------------------------------------------------------|-----------------------------|--|--| +| PLMNBC (threeegcsd /plmnb, 0x0030/0x0001) | M | ADD, MOD, MOVE | Specified in the subclause "Bearer capability" in 3GPP TS 24.008 [3]. | None | | | +| GSM Channel Coding (threeegcsd / gsmchancod, 0x0030/0x0002) | M | ADD, MOD, MOVE | The second octet of Chosen Channel as specified in the subclause "Chosen Channel" in 3GPP TS 48.008 [9]. | None | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| Activate Protocol (threeegcsd/ actprot, 0x0030/0x0001) | M | MOD | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | Local Peer Role (Localpeer 0x0001) | O | ALL | None | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| Protocol Negotiation Result (threeegcsd / protres, (0x0030/0x0001) | M | ADD, MOD, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | Negotiation Result (result 0x0001) | M | ALL | None | | | +| Rate Change (threeegcsd / ratechg, (0x0030/0x0002) | M | ADD, MOD, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | New Rate (rate 0x0001) | M | 2400, 4800, 9600, 14400, 28800, 57600 | None | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.27 Enhanced Circuit Switched Data package + +Table C.14.27: Package Usage Information For Enhanced CSD + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|------------------------------------------------|---------------------------------|----------------------------|----------------------------------------------|------------------------------------|--|--| +| Bitrate (threeegcsden /bitrate, 0x0082/0x0003) | M | ADD, MOD, MOVE | 2400, 4800, 9600, 14400, 28800, 57600, 64000 | None | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.28 3G Expanded Call Progress Tones package + +Table C.14.28: Package Usage Information For 3G Expanded Call Progress Tones + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-------------------------------------------------------------|---------------------------------|----------------------------|--------------------------|------------------------------------|--|--| +| None | | | | | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| CAMEL Prepaid Warning Tone (threeegxcg/cpwt, 0x0032/0x004f) | M | ADD, MOD, MOVE | | - | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | ToneDirection(td, 0x0010) | M | Ext, Int | Default=Ext | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.29 Cellular Text Telephone Modem Text Transport Package + +Table C.14.29: Package Usage Information For CTM + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|------------------------------------------------------------------------|--------------------------|------------------------|-----------------------|-----------------------------|--|--| +| Termination connection state(threeegctm/ connstate, 0x0068/0x0001) | M | ADD, MOD, MOVE | ALL | | | | +| Text Transport (threeegctm/ trpt (0x0068/0x0002) | M | ADD, MOD, MOVE | CTM | | | | +| Text Protocol Version (threeegctm/ textproto 0x0068/0x0003) | M | ADD, MOD, MOVE | ALL | Default=1 | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | -- | - | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| Connection State Change (threeegctm/ connchange 0x0068/0x0001) | M | ADD, MOD, MOVE, NOTIFY | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | None | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | Connchng | M | As property connstate | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| Number of Characters Transferred (threeegctm/ chartrans 0x0068/0x0001) | M | SUB | | | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +C.14.30 Void + +## C.14.31 Flexible Tone Generator package + +Table C.14.31: Package Usage Information For Flexible Tone Generator + +| Properties | Mandatory/ Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-----------------------------------------------|-------------------------------------|----------------------------|--------------------------|------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/ Optional | Used in command: | | Duration Provisioned Value: | | | +| Flexible Tone (threeegflex/ft, 0x0084/0x0050) | M | ADD, MOD, MOVE | | - | | | +| | Signal Parameters | Mandatory/ Optional | Supported Values: | Duration Provisioned Value: | | | +| | Burst list direction(bld, 0x0001) | M | Int, Ext | Default=Ext | | | +| | NumberOfBursts (nob, 0x0002) | M | 1-3 | Default = 1 | | | +| | BurstInterval (bi, 0x0003) | M | 1-1200 | Default = 2 | | | +| | numberOfTonesInBurst (notib 0x0004) | M | 1-3 | Default=3 | | | +| | toneDuration (td 0x0005) | M | 1-20 | Default=2 | | | +| | toneInterval (ti 0x0006) | M | 1-20 | Default=2 | | | +| Events | Mandatory/ Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/ Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/ Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.32 Trace Package + +Table C.14.32: Package Usage Information For Trace Package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|---------------------------------------------------------------------------------------|-------------------------------------|--------------------|----------------------------------------------------------------------------|-----------------------------|--|--| +| Trace Activity Control
(calltrace/traceactivityrequest,
0x0097/0x0001) | M | ADD, MOD | Trace Session is activated in MGW /
Trace Session is deactivated in MGW | Not Applicable | | | +| IMSI (calltrace/imsi,
0x0097/0x0002) | M | ADD, MOD | Octet string | Not Applicable | | | +| IMEI(SV) (calltrace/imei_sv,
0x0097/0x0003) | M | ADD, MOD | Octet string | Not Applicable | | | +| Trace Reference
(calltrace/tracereference,
0x0097/0x0004) | M | ADD, MOD | Octet string | Not Applicable | | | +| Trace Recording Session Reference
(calltrace/tracerecsessionref,
0x0097/0x0005) | M | ADD, MOD | Octet string | Not Applicable | | | +| Trace Depth (calltrace/tracedepth,
0x0097/0x0006) | M | ADD, MOD | Octet string | Not Applicable | | | +| Triggering Events
(calltrace/triggeringevent,
0x0097/0x0007) | M | ADD, MOD | Octet string | Not Applicable | | | +| List of interfaces
(calltrace/listofinterfaces,
0x0097/0x0008) | M | ADD, MOD | Octet string | Not Applicable | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| Trace result
(calltrace/tracact,
0x0097/0x0001) | M | ADD, MOD, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | TraceActivation Result (res,0x0001) | M | Trace Successfully activated/ Failure in trace activation | Not Applicable | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | + +## C.14.33 ASCI Group call + +Table C.14.33: Package usage information for ASCI Group Call package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|----------------------------------------------------------------------------------|--------------------------|--------------------|-------------------|-----------------------------|--|--| +| Number of needed conference terminations (threegasci/nct, 0x00b2/0x0001) | M | ADD | upto 32 | None | | | +| Number of desired listener context terminations (threegasci/nlct, 0x00b2/0x0002) | O | ADD | upto 32 | None | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +## C.14.34 IP domain connection + +Table C.14.34: Package usage information for IP domain connection package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|---------------------------|--------------------------|------------------------------------|--|--| +| IP Realm Identifier
(ipdc /realm, 0x009d /0x0001) | M | ADD | String | Operator Defined (NOTE) | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/ Optional | | | | | | +| None | - | | | | | | +| NOTE: A default IP realm may be configured such that if the MGW has not received the IP realm identifier and the MGW supports multiple IP realms then the default IP realm shall be used. | | | | | | | + +## C.14.35 Inactivity Timer Package + +Table C.14.35: Package Usage Information for Inactivity Timer package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|--------------------------------------------|---------------------------------------|---------------------------|--------------------------|-------------------------------------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| Inactivity Timeout (it/ito, 0x0045/0x0001) | M | MOD, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | Maximum Inactivity Time (mit, 0x0001) | M | Any integer | Unspecified, if not sent a value must be provisioned. | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | None | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +## C.14.36 3G Interface Type package + +Table C.14.36: Package Usage Information for 3G Interface Type package + +| Properties | Mandatory/Optional | Used in command: | Supported Values: | Provisioned Value: | | | +|-----------------------------------------------------------|---------------------------------|---------------------------|---------------------------------------------------------------------------------------------------|------------------------------------|--|--| +| IP interface type,
(threegint/ipint,
0x00e3/0x0001) | M | ADD, MOD | "NboIP"
(0x0001)
"AoIP"
(0x0002)
"MboIP"
(0x0003)
"ExtSIPI"
(0x0004)
NOTE | None | | | +| Signals | Mandatory/Optional | Used in command: | | Duration Provisioned Value: | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values: | Duration Provisioned Value: | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command: | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values: | Provisioned Value: | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command: | | Supported Values: | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | +| NOTE: Other values reserved | | | | | | | + +## C.14.37 Differentiated Services (ds) + +Table C.14.37: Differentiated Services package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|---------------------------------------------------------------|---------------------------------|---------------------------|-------------------------|-----------------------------------|--|--| +| Differentiated Services Code Point
(ds/dscp,0x008b/0x0001) | M | ADD, MODIFY | ALL | Yes | | | +| Tagging Behaviour
(ds/tb, 0x008b/0x0002) | O | ADD, MODIFY | ALL | Yes | | | +| Signals | Mandatory/Optional | Used in command | | Duration Provisioned Value | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values | Duration Provisioned Value | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command | Supported Values | | | | +| None | - | - | - | | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +## C.14.38 Gate Management (gm) + +Table C.14.38: Gate Management Package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|---------------------------------------------------------|--------------------------|--------------------|------------------|----------------------------|--|--| +| Remote Source Address Filtering (gm/saf,0x008c/0x0001) | M | ADD, MODIFY | ALL | Not Applicable | | | +| Remote Source Address Mask (gm/sam,0x008c/0x0002) | O | ADD, MODIFY | ALL | Not Applicable | | | +| Remote Source Port Filtering (gm/spf,0x008c/0x0003) | M | ADD, MODIFY | ALL | Not Applicable | | | +| Remote Source Port (gm/spr,0x008c/0x0004) | O | ADD, MODIFY | ALL | Not Applicable | | | +| Explicit Source Address Setting (gm/esas,0x008c/0x0005) | Not Supported | NONE | - | - | | | +| Local Source Address (gm/lsa,0x008c/0x0006) | Not Supported | NONE | - | - | | | +| Explicit Source Port Setting (gm/esps,0x008c/0x0007) | Not Supported | NONE | - | - | | | +| Local Source Port (gm/lsp,0x008c/0x0008) | Not Supported | NONE | - | - | | | +| Remote Source Port Range (gm/spr,0x008c/0x000A) | O | ADD, MODIFY | ALL | Not Applicable | | | +| Signals | Mandatory/Optional | Used in command | | Duration Provisioned Value | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values | Duration Provisioned Value | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| Statistics | Mandatory/Optional | Used in command | Supported Values | | | | +| Discarded Packets (gm/dp,0x008c/0x0001) | Not Supported | None | - | | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +NOTE : This package extends RTP Control Protocol package (ITU-T Recommendation H.248.57 [66]) and thus inherits RTCP Allocation Specific Behaviour property (rsb). + +## C.14.39 Traffic management (tman) + +Table C.14.39: Traffic Management Package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|-----------------------------------------------------|--------------------------|--------------------|------------------|----------------------------|--|--| +| Policing (tman/pol, 0x008d/0x0005) | M | ADD, MODIFY | ALL | Not Applicable | | | +| Peak Data Rate (tman/pdr, 0x008d/0x0001) | O | ADD, MODIFY | ALL | Not Applicable | | | +| Delay Variation Tolerance (tman/dvt, 0x008d/0x0004) | O | ADD, MODIFY | ALL | ANY | | | +| Sustainable Data Rate (tman/sdr, 0x008d/0x0002) | M | ADD, MODIFY | ALL | Not Applicable | | | +| Maximum burst size (tman/mbs, 0x008d/0x0003) | M | ADD, MODIFY | ALL | Not Applicable | | | +| Signals | Mandatory/Optional | Used in command | | Duration Provisioned Value | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values | Duration Provisioned Value | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command | | Supported Values | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +NOTE: The data rate shall be calculated using the packet size from IP layer upwards. The Token Bucket method as described by ITU-T Recommendation H.248.53 [69] sub-clause 9.4.3 (as per IETF RFC 2216 [73]) shall be followed where SDR = "r" and MBS = "b" (i.e. the additional "M" value does not apply). + +## C.14.40 IP Realm Availability (ipra) + +Table C.14.40: IP Realm Availability Package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|-----------------------------------------------------|----------------------------------------|---------------------------|--------------------------|-----------------------------------|--|--| +| Available Realms, (ipra/ar, 0x00e0/0x0001) | M | AUDITVALUE | ALL | Not Applicable | | | +| Signals | Mandatory/Optional | Used in command | | Duration Provisioned Value | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values | Duration Provisioned Value | | | +| | - | - | | - | | | +| Events | Mandatory/Optional | Used in command | | | | | +| Available Realms Changed, (ipra/arc, 0x00e0/0x0001) | M | MODIFY, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values: | Provisioned Value | | | +| | - | - | | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | Newly Available Realms (nar, 0x0001) | M | ALL | Not applicable | | | +| | Newly Unavailable Realms (nur, 0x0002) | M | ALL | Not applicable | | | +| Statistics | Mandatory/Optional | Used in command | | Supported Values | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +## C.14.41 RTCP Handling Package (rtcph) + +Table C.14.41: RTCP Handling Package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|---------------------------------------------------------------|---------------------------------|---------------------------|-------------------------|-----------------------------------|--|--| +| RTCP Allocation Specific Behaviour (rtcph/rsb, 0x00b5/0x0009) | M | ADD, MODIFY | ALL | OFF | | | +| Signals | Mandatory/Optional | Used in command | | Duration Provisioned Value | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values | Duration Provisioned Value | | | +| | - | - | | - | | | +| Events | Mandatory/Optional | Used in command | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | | - | | | +| Statistics | Mandatory/Optional | Used in command | | Supported Values | | | +| None | - | - | | - | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +## C.14.42 Application Data Inactivity Detection (adid) + +Table C.14.42: Application Data Inactivity Detection package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|-----------------------------------------------------|-----------------------------|---------------------|------------------|----------------------------|--|--| +| None | - | - | - | - | | | +| Signals | Mandatory/Optional | Used in command | | Duration Provisioned Value | | | +| None | - | - | - | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values | Duration Provisioned Value | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command | | | | | +| IP Flow Stop Detection (adid/ipstop, 0x009c/0x0001) | M | ADD, MODIFY, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | Detection time (dt, 0x0001) | M | ALL | Yes | | | +| | Direction (dir, 0x0002) | M | ALL | Yes | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command | Supported Values | | | | +| None | - | - | - | | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +## C.14.43 Explicit Congestion Notification for RTP-over-UDP Support (ecnrous) + +**Table C.14.43.1: Explicit Congestion Notification for RTP-over-UDP Support package** + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|----------------------------------------------------------------|----------------------------------|---------------------------|-------------------------|---------------------------------------------------------------------------------------------|--|--| +| ECN Enabled (ecnrous/ecnen, 0x010b/0x0001) | M | ADD, MODIFY | True, False | - | | | +| Congestion Response Method (ecnrous/crm, 0x010b/0x0002) | Not Signalled | - | - | "RDCC"(0x0002)
NOTE | | | +| Initiation Method (ecnrous/initmethod, 0x010b/0x0003) | M | ADD, MODIFY | "leap" | "leap" | | | +| ECN Mode (ecnrous/mode, 0x010b/0x0004) | Not Signalled | - | - | "setonly" (0x0001) in the Remote Descriptor and "readonly" (0x0002) in the Local Descriptor | | | +| ECT Marking (ecnrous/ectmark, 0x010b/0x0005) | Not Signalled | - | - | "0" (0x0002) | | | +| ECN Congestion Marking (ecnrous/congestmark, 0x010b/0x0006) | Not Signalled | - | - | "nomark" (0x0003) | | | +| ECN SDP Usage (ecnrous/ecnsdp, 0x010b/0x0007) | Not Signalled | - | - | "P" (0x0001) | | | +| Signals | Mandatory/Optional | Used in command | | Duration Provisioned Value | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values | Duration Provisioned Value | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command | | | | | +| ECN Failure (ecnrous/fail, 0x010b/0x0001) | M | ADD, MODIFY, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | - | - | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | Failure Type (type, 0x0001) | Mandatory | INIT, USE | - | | | +| | Media Sender SSRC (ssrc, 0x0002) | Not Supported | - | - | | | +| Statistics | Mandatory/Optional | Used in command | | Supported Values | | | +| Source (ecnrous/ssrc, 0x010b/0x0001) | Not Supported | - | | - | | | +| CE Counter (ecnrous/cecount, 0x010b/0x0002) | Not Supported | - | | - | | | +| ECT0 Counter (ecnrous/ectzero, 0x010b/0x0003) | Not Supported | - | | - | | | +| ECT1 Counter (ecnrous/ectone, 0x010b/0x0004) | Not Supported | - | | - | | | +| Not-ECT Counter (ecnrous/notect, 0x010b/0x0005) | Not Supported | - | | - | | | +| Lost Packets Counter (ecnrous/lost, 0x010b/0x0006) | Not Supported | - | | - | | | +| Extended Highest Sequence number (ecnrous/ehsn, 0x010b/0x0007) | Not Supported | - | | - | | | +| Duplication Counter (ecnrous/dup, 0x010b/0x0008) | Not Supported | - | | - | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +NOTE: Application Specific Rate Adaptation shall be applied in accordance with 3GPP TS 26.114 [77]. For speech this requires support of CMR and TMMBR for video. + +## C.14.44 MG Act-as STUN Server (mgastuns) + +Table C.14.44.1: MG Act-as STUN Server + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|--------------------------------------------------------|--------------------------|--------------------|------------------|----------------------------|--|--| +| Act-as STUN Server
(mgastuns/astuns, 0x00c2/0x0001) | M | ADD, MODIFY | ALL | - | | | +| Signals | Mandatory/Optional | Used in command | | Duration Provisioned Value | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values | Duration Provisioned Value | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | - | - | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command | Supported Values | | | | +| None | - | - | - | | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +## C.14.45 Originate STUN Continuity Check (ostuncc) + +Table C.14.45.1: Originate STUN Continuity Check Package + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|------------------------------------------------------------------|----------------------------------------|---------------------------|-----------------------------|-----------------------------------|--|--| +| Host Candidate Realm (ostuncc/hcr, 0x00c3/0x0001) | O | ADD, MODIFY | ALL | Yes | | | +| Signals | Mandatory/Optional | Used in command | | Duration Provisioned Value | | | +| Send Connectivity Check (ostuncc/scc, 0x00c3/0x0001) | M | ADD, MODIFY | | Not Applicable | | | +| | Signal Parameters | Mandatory/Optional | Supported Values | Duration Provisioned Value | | | +| | Control (cntrl, 0x0001) | O | "controlling", "controlled" | Not Applicable | | | +| Send Additional Connectivity Check (ostuncc/sacc, 0x00c3/0x0002) | Mandatory/Optional | Used in command | | Duration Provisioned Value | | | +| | M | MODIFY | | Not Applicable | | | +| | Signal Parameters | Mandatory/Optional | Supported Values | Duration Provisioned Value | | | +| | Control (cntrl, 0x0001) | O | "controlling", "controlled" | Not Applicable | | | +| Events | Mandatory/Optional | Used in command | | | | | +| Connectivity Check Result (ostuncc/ccr, 0x00c3/0x0001) | M | ADD, MODIFY, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| New Peer Reflexive Candidate (ostuncc/nprc, 0x00c3/0x0002) | Candidate/Transport Pair (ctp, 0x0001) | M | ALL | Not applicable | | | +| | Mandatory/Optional | Used in command | | | | | +| | M | ADD, MODIFY, NOTIFY | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | - | - | | | +| | ObservedEvent Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | Candidate (can, 0x0001) | M | ALL | Not applicable | | | +| Statistics | Mandatory/Optional | Used in command | Supported Values | | | | +| None | - | - | - | | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +## C.14.46 Enhanced Revised Offer/Answer SDP Support (eroas) + +**Table C.14.46: Enhanced Revised Offer/Answer SDP Support package** + +| Properties | Mandatory/Optional | Used in command | Supported Values | Provisioned Value | | | +|--------------------------------------------------------|-------------------------------------|---------------------------|-------------------------|---------------------------------------|--|--| +| SDPCapNeg Extensions
(eroas/sdpe,
0x0109/0x0001) | M | AuditValue | "cap-v0" | "cap-v0" | | | +| Signals | Mandatory/Optional | Used in command | | Duration
Provisioned Value | | | +| None | - | - | | - | | | +| | Signal Parameters | Mandatory/Optional | Supported Values | Duration
Provisioned Value | | | +| | - | - | - | - | | | +| Events | Mandatory/Optional | Used in command | | | | | +| None | - | - | | | | | +| | Event Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | - | - | | | +| | ObservedEvent
Parameters | Mandatory/Optional | Supported Values | Provisioned Value | | | +| | - | - | - | - | | | +| Statistics | Mandatory/Optional | Used in command | Supported Values | | | | +| None | - | - | - | | | | +| Error Codes | Mandatory/Optional | | | | | | +| None | - | | | | | | + +## C.15 Mandatory support of SDP and Annex C information elements + +Mandatory support of SDP and Annex C information elements shall be in accordance with subclause 11. + +**Table C.15: Mandatory Annex C and SDP information elements** + +| Information Element | Annex C Support | SDP Support | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------| +| Bearer Service Characteristics | TMR | | +| ISDN BC | USI | | +| NOTE 1: When text encoding is used, all the Information Elements shall be supported via their corresponding SDP parameters, as specified in subclause 11. Annex C SDP equivalents shall not be used. | | | + +## C.16 Optional support of SDP and Annex C information elements + +Table C.16: Optional Annex C and SDP information elements + +| Information Element | Annex C Support | SDP Support | +|---------------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| v-line | "SDP_V " | As in 3GPP TS 29.332 [51], clause A.15 (NOTE 1) | +| m-line | "SDP_M " | As in 3GPP TS 29.332 [51], clause A.15 (NOTE 1) | +| c-line | "SDP_C " | As in 3GPP TS 29.332 [51], clause A.15 (NOTE 1) | +| a-line | "SDP_A " | As in 3GPP TS 29.332 [51], clause A.15 (NOTE 1) (NOTE 7) | +| b-line | "SDP_B " | As in 3GPP TS 29.332 [51], clause A.15 (NOTE 1) (NOTE 8) | +| o-line | "SDP_O" | As in 3GPP TS 29.332 [51], clause A.15 | +| s-line | "SDP_S" |
The session name (s=) line contains a single field:
s= <session-name>.
The MG shall return the value received from the MGC or if there is no s-line sent by the MGC, the MG shall populate this line as follows:
- "s=" (NOTE 1)
IPv6 | As defined in ITU-T Recommendation H.248.1 [10] C6. Mandatory for Iu termination with IP transport (NOTE 5) | +| Iu IP Port | Port | As defined in ITU-T Recommendation H.248.1 [10] C6. Mandatory for Iu termination with IP transport (NOTE 6) | + +NOTE 1: If the procedures Reserve RTP Connection Point, Configure RTP Connection Point, Reserve and Configure RTP Connection Point are supported, these properties shall be supported. + +NOTE 2: When text encoding is used, all the Information Elements shall be supported via their corresponding SDP parameters, as specified in subclause 11. Annex C SDP equivalents shall not be used. + +NOTE 3: The BIR length shall be fixed at 4 Octets. + +NOTE 4: The NSAP length shall be fixed at 20 Octets. The content of the RNC Transport Address or BIWF Address depends on the used transport interface but the principle is that NSAP format is used. See 3GPP TS 25.414 [21] for RNC and for core network see 3GPP TS 29.414 [32]. For IP the IANA ICP IDI format of the NSAP addressing format as specified in X.213 [33] shall be used. For IPv4 networks the IPv4 format recommended by X.213 shall be adopted. + +NOTE 5: The value is mapped to/from the first 4(or 16) octets of the IPv4 (or IPv6) address part of the Transport Layer Address in 3GPP TS 25.413 [20]. + +NOTE 6: The value is mapped to/from the Binding ID in the RANAP IE Iu transport Association, 3GPP TS 25.413 [20]. + +NOTE 7: For the RTP Payload for Redundant Audio Data, the encoding name with "red" and "fmtp" attributes shall be provided to indicate the redundancy level and shall always be signalled in conjunction with the CLEARMODE Payload type as described in 10.2.3.5.2. No other Payload types are currently defined for use with the Redundant RTP Payload. + +NOTE 8: For RTP flows, where RTCP resources are reserved together with the RTP resources using the "RTP Specific Behaviour" property of the Gate Management package (gm) property, the MGC may also supply additional RTCP bandwidth modifiers (i.e. RR and RS, see IETF RFC 3556 [52]). The AS *bandwidth* value will include the bandwidth used by RTP. In the absence of the RTCP bandwidth modifiers, the MGW shall allow an additional 5% of the AS bandwidth value for the bandwidth for RTCP, in accordance with IETF RFC 3556 [52]. + +--- + +## Annex D (informative): Change history + +| Date | TSG # | TSG Doc. | CR | Re v | Subject/Comment | New | +|----------|-------|-----------|-----|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| Sep 2000 | | | | | Initial draft created after N4#4 based on N4-000620 | 0.1.0 | +| Oct 2000 | | | | | Updated after N4 R2000 Ad Hoc Stockholm based on N4-00823 and N4-000842 | 0.2.0 | +| Nov 2000 | | | | | Reference for MTP 3B corrected; RFC reference for SCTP added | 0.3.0 | +| Nov 2000 | | | | | Updated according to N4-000996, N4-000998, N4-000999, N4-001000, N4-001021, N4-001028 & N4-001097 as agreed in CN4 #5 | 1.0.0 | +| Nov 2000 | CN#10 | | | | To TSG-CN Plenary #10 for information | 1.1.0 | +| Jan 2001 | | | | | Updated according to NJ-010069, NJ-010030, NJ-010098, NJ-010094, NJ-010033, NJ-010097, NJ-010095, NJ-010112 as agreed in the Joint CN3/CN4 Meeting held during the CN4#6 | 1.1.1 | +| Jan 2001 | | | | | References ordered by specification/recommendation number; references to 3GPP specifications include full titles as shown on the title page; literal reference numbers and references to subclauses replaced with fields; all table cells outlined with 0.5pt lines; appropriate 3GPP paragraph styles applied. | 1.2.0 | +| Feb 2001 | | | | | Updated according to N4-010245, N4-010248, N4-010249, N4-010303, N4-010304, N4-010305, agreed in CN4 Release 4 ad hoc, Madrid. References to Q.1902.x replaced by references to 29.205; 3GPP styles applied consistently; form for ITU-T recommendations in text is now "ITU-T Recommendation A.NNNN". | 1.3.0 | +| Mar 2001 | | | | | Updated according to N4-010384, N4-010401 (part) & N4-010472, agreed in CN4 in Sophia Antipolis. References to Q.1950, Q.1970 and Q.1990 replaced by reference to 29.205. Reference to SIP-T deleted. Editor's note in 15.1.2.3 deleted. Editorial clean-up. | 2.0.0 | +| Mar 2001 | | | | | Sent to TSG CN#11 for approval | 2.1.0 | +| Mar 2001 | CN#11 | | | | References updated after comments in TSG CN #11 Approved in CN#11 | 4.0.0 | +| Jun 2001 | CN#12 | NP-010284 | 1 | 1 | Text encoding of codec information on Mc interface | 4.1.0 | +| Jun 2001 | CN#12 | NP-010284 | 4 | 2 | ATM-IP signalling transport Interworking | 4.1.0 | +| Jun 2001 | CN#12 | NP-010284 | 5 | 1 | Alignment of Procedure names to TS 23.205 and Q.1950 | 4.1.0 | +| Jun 2001 | CN#12 | NP-010284 | 6 | 3 | Clarifications in 3GUP package | 4.1.0 | +| Jun 2001 | CN#12 | NP-010284 | 7 | 1 | Clarification of Use of UP version property in 3GUP package | 4.1.0 | +| Jun 2001 | CN#12 | NP-010284 | 8 | 1 | Updates to UP Relay Function, Appendix A | 4.1.0 | +| Sep 2001 | CN#13 | | | | Editorial clean up | 4.2.0 | +| Sep 2001 | CN#13 | NP-010452 | 009 | | Addition of package numbers allocated by IANA | 4.2.0 | +| Sep 2001 | CN#13 | NP-010452 | 010 | 1 | Mc signalling transport in IP environment | 4.2.0 | +| Dec 2001 | CN#14 | NP-010619 | 011 | 1 | Inclusion of H.248 Annex L, "Error Codes and Service Change Reason Description" | 4.3.0 | +| Dec 2001 | CN#14 | NP-010619 | 012 | | Removal of the Reuse Idle Package | 4.3.0 | +| Dec 2001 | CN#14 | NP-010619 | 014 | | Correction of Release Procedures | 4.3.0 | +| Dec 2001 | CN#14 | NP-010619 | 015 | | Clarification Of Use Of 3GUP package For PCM | 4.3.0 | +| Dec 2001 | CN#14 | NP-010619 | 016 | | Corrections to ABNF coding of PackageIDs | 4.3.0 | +| Dec 2001 | CN#14 | NP-010619 | 017 | | Correction of BICC packages | 4.3.0 | +| Dec 2001 | CN#14 | NP-010619 | 020 | 1 | Correction of 3GUP package sub-list type | 4.3.0 | +| Dec 2001 | CN#14 | NP-010631 | 013 | 1 | Introduction of MGW Congestion Handling | 5.0.0 | +| Dec 2001 | CN#14 | NP-010631 | 019 | 2 | Maintenance locking of MG | 5.0.0 | +| Jan 2002 | | | | | A coverdheet fixed | 5.0.1 | +| Mar 2002 | CN#15 | NP-020029 | 025 | 2 | Naming convention for TDM resources | 5.1.0 | + +| Date | TSG # | TSG Doc. | CR | Re
v | Subject/Comment | New | +|----------|-------|-----------|-----|---------|---------------------------------------------------------------------------------------------|-------| +| Mar 2002 | CN#15 | NP-020029 | 027 | 2 | Correction of Bearer Modification Handling | 5.1.0 | +| Jun 2002 | CN#16 | NP-020260 | 030 | 1 | GTT enhancement on Mc | 5.2.0 | +| Jun 2002 | CN#16 | NP-020260 | 032 | | Update to TFO package to explicitly reference TS 26.103 for 3GPP codecs | 5.2.0 | +| Jun 2002 | CN#16 | NP-020260 | 033 | 2 | CTM Text Transport package | 5.2.0 | +| Jun 2002 | CN#16 | NP-020260 | 034 | | Allow the usage of logical port | 5.2.0 | +| Jun 2002 | CN#16 | NP-020249 | 036 | | Correction subclause 14.1.6 of 3GPP TS 29.332 | 5.2.0 | +| Sep 2002 | CN#17 | NP-020459 | 037 | 1 | Misalignment between TS 23.226 and TS 29.232 for Global Text Telephony | 5.3.0 | +| Sep 2002 | CN#17 | NP-020459 | 038 | 1 | Alignment of text in TS 29.232 for Global Text Telephony | 5.3.0 | +| Sep 2002 | CN#17 | NP-020459 | 039 | 1 | Alignment between prepare bearer and reserve bearer in TS 29.232 for Global Text Telephony. | 5.3.0 | +| Sep 2002 | CN#17 | NP-020463 | 044 | 1 | Missing Properties For Circuit Switched Data Calls | 5.3.0 | +| Dec 2002 | CN#18 | NP-020579 | 041 | 2 | Termination ID Correction | 5.4.0 | +| Dec 2002 | CN#18 | NP-020597 | 042 | 3 | New Procedures/Package for handling IP transport for Iu interface | 5.4.0 | +| Dec 2002 | CN#18 | NP-020578 | 046 | 2 | Updates to support Codec Modification | 5.4.0 | +| Dec 2002 | CN#18 | NP-020594 | 052 | 2 | CAMEL4 flexible tone package | 5.4.0 | +| Mar 2003 | CN#19 | NP-030108 | 053 | | Update to 3GUP – clarification of IuUP Initialisation handling | 5.5.0 | +| Mar 2003 | CN#19 | NP-030108 | 054 | 1 | Update to 3GUP – addition of reference to SDU format definition for Nb interface | 5.5.0 | +| Jun 2003 | CN#20 | NP-030211 | 057 | 1 | Alignment of references after renumbering of H248 by ITU-T | 5.6.0 | +| Jun 2003 | CN#20 | NP-030211 | 059 | | Clarification of handling of DTMF in split architecture – DTMF timing | 5.6.0 | +| Mar 2004 | CN#23 | NP-040052 | 061 | | Addition of Package Id for CTM | 5.7.0 | +| Mar 2004 | | | | | Addition of Package Ids allocated by IANA (0082 - 0084) | 5.7.0 | +| Sep 2004 | CN#25 | NP-040392 | 063 | | Correction of Procedure "Activate Voice Processing Function" | 5.8.0 | +| Sep 2004 | CN#25 | NP-040418 | 075 | 2 | 3GUP package corrections | 5.8.0 | +| Sep 2004 | CN#25 | NP-040418 | 064 | | Provisioning Of Base Root package properties | 5.8.0 | +| Sep 2004 | CN#25 | NP-040418 | 065 | | Service Change Address | 5.8.0 | +| Sep 2004 | CN#25 | NP-040418 | 066 | | Use Of Event Buffers | 5.8.0 | +| Sep 2004 | CN#25 | NP-040418 | 067 | | Digit Maps | 5.8.0 | +| Sep 2004 | CN#25 | NP-040418 | 068 | | IP secured transport | 5.8.0 | +| Sep 2004 | CN#25 | NP-040418 | 074 | | Termination Restoration | 5.8.0 | +| Sep 2004 | CN#25 | NP-040392 | 072 | 1 | Use Of Statistics | 5.8.0 | +| Dec 2004 | CN#26 | NP-040521 | 078 | | Correction of distant codec list | 5.9.0 | +| Dec 2004 | CN#26 | NP-040528 | 079 | | IP transport package Duplicate property ID in ASN.1 encoding | 5.9.0 | +| Dec 2004 | CN#26 | NP-040529 | 080 | 1 | H.248 Scope | 5.9.0 | +| Dec 2004 | CN#26 | NP-040529 | 081 | 1 | Q.1950 reference | 5.9.0 | +| Dec 2004 | CN#26 | NP-040529 | 082 | | Emdedded events | 5.9.0 | +| Dec 2004 | CN#26 | NP-040529 | 084 | | Multiple streams | 5.9.0 | +| Dec 2004 | CN#26 | NP-040529 | 085 | 1 | Overspec/underspec parameters | 5.9.0 | + +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|----------|-------|-----------|-----|-----|------------------------------------------------------------------------------------------|-------| +| Dec 2004 | CN#26 | NP-040529 | 088 | 2 | Procedures and Commands – removal of unwanted commands | 5.9.0 | +| Dec 2004 | CN#26 | NP-040547 | 092 | | Update of referenced H.248.1 version to version 2 | 6.0.0 | +| Mar 2005 | CN#27 | NP-050057 | 060 | 7 | Addition of the trace package | 6.1.0 | +| | | NP-050029 | 101 | 1 | Requirements for support of H.248 packages | | +| | | NP-050029 | 104 | 1 | Completion of specification of UMTS Packages | | +| | | NP-050036 | 106 | | Correction of implied option for Embedded Signals and Events | | +| | | NP-050036 | 108 | 2 | Removal of the 'Test' ServiceStates value from the TerminationState Descriptor | | +| | | NP-050036 | 111 | 1 | Removal of the usage of the ContextAttributeAuditReq construct | | +| | | NP-050036 | 113 | | Removal of the Multiplex descriptor | | +| | | NP-050036 | 115 | | Removal of the Modem descriptor | | +| | | NP-050133 | 120 | 4 | Requirements for support of procedures | | +| | | NP-050034 | 122 | 2 | Procedure for Emergency Call Indication | | +| | | NP-050036 | 128 | | Removal of the Error Descriptor usage in NotifyRequest | | +| | | NP-050036 | 130 | | Updating incomplete parameter definition for MGW Resource congestion handling procedures | | +| | | NP-050055 | 131 | | Removal of Signals on ROOT | | +| | | NP-050055 | 132 | | Removal of usage of Stream ID in Topology descriptor | | +| | | NP-050055 | 133 | | H.248.1 version contradiction | | +| | | NP-050036 | 135 | | Directionality of tones and announcements | | +| | | NP-050036 | 138 | 1 | New 'TFO status' event | | +| | | NP-050028 | 139 | 1 | TFO procedure clarification | | +| | | NP-050028 | 142 | 1 | TFO activation without TFO Codec List | | +| | | NP-050036 | 148 | 1 | Commands on ROOT | | +| | | NP-050036 | 149 | 1 | Use Of Audit Value | | +| | | NP-050036 | 151 | | Service Change Reasons Not supported | | +| | | NP-050036 | 155 | 1 | Descriptors in command replies | | +| | | NP-050036 | 157 | 1 | Introduction of formal profile name for Mc interface | | +| | | NP-050036 | 158 | | Service Change for Failover not defined for Mc Interface | | +| | | NP-050029 | 161 | | Removal Of VPF type | | +| | | NP-050029 | 164 | | Alignment of TFO Activation Procedure and associated parameters | | +| | | NP-050055 | 165 | 2 | Continuity Test | | +| Jun 2005 | CT#28 | CP-050236 | 184 | 1 | BNC Cut-Through Capability Package Removed | 6.2.0 | +| | | CP-050236 | 187 | 1 | Format of IP address | | +| | | CP-050101 | 188 | 2 | Profile Registration Mandatory/Negotiation Clarification | | +| | | CP-050236 | 196 | 1 | Clarification of Maintenance Procedures | | +| | | CP-050236 | 198 | 1 | Clarification of Use Of Topology and Multiparty | | +| | | CP-050236 | 200 | | Removal of Option in Prepare Bearer that the MGW can chose the BNC Characteristics | | +| | | CP-050236 | 202 | 1 | Clarification Of Use of Wildcarding | | +| | | CP-050080 | 209 | 2 | Text encoding of IPBCP for IP transport on Mc interface | | +| | | CP-050080 | 212 | 2 | Definition of requirement for support of commands | | +| | | CP-050238 | 213 | 1 | Correction to Profile registration procedures | | +| Sep 2005 | CT#29 | CP-050435 | 218 | 1 | Codec IE and Codec List on the Mc interface | 6.3.0 | +| | | CP-050290 | 224 | | Value range for BIR/NSAP | | +| | | CP-050290 | 229 | | Clarification of 'extended only' packages | | +| | | CP-050290 | 231 | | Correction to Prepare IP Transport procedure | | +| | | CP-050290 | 233 | 1 | Wildcarding of Release Procedures | | +| | | CP-050290 | 235 | | Clarification to use of local peer for CSD | | +| | | CP-050280 | 238 | 2 | Correction to clarify use of FAX and Channel Mode Modify | | +| | | CP-050290 | 242 | 1 | Clarification to use of PLMN-BC, GSM-Chanel Coding for CSD | | +| | | CP-050290 | 244 | 1 | Clarification to use of Init Dir parameter | | +| | | CP-050290 | 246 | 1 | Clarification to Termination Restoration and Termination Out Of Service | | +| | | CP-050290 | 248 | | Remove provisioning of Resource Congestion Event | | +| | | CP-050290 | 250 | | Remove Priority property | | +| | | CP-050290 | 252 | | Notifications for IP Bearer Establishment | | +| | | CP-050290 | 254 | 1 | Clarification for Use of Stream Mode Property with Announcements | | + +| Date | TSG # | TSG Doc. | CR | Re v | Subject/Comment | New | +|----------|-------|-----------|------|------|-------------------------------------------------------------------------------------------------------------------|-------| +| | | CP-050290 | 256 | | Removal of Stream Mode Loopback | | +| | | CP-050290 | 258 | | Correction to IPBCP Tunnel Procedures | | +| | | CP-050290 | 263 | | Exclusion of use of Signal ID Play Tone for DTMF | | +| | | CP-050290 | 265 | 1 | Miscellaneous Open Mc corrections | | +| | | CP-050308 | 266 | 1 | Use of Individual Audit Token | | +| | | CP-050438 | 268 | 1 | Restriction of Service Change Address in MGW Restriction | | +| | | CP-050308 | 271 | | Removal of BNC-cut-through-capability from Prepare Bearer procedure | | +| | | CP-050308 | 272 | | Updating Mc interface profile "threeegbicsn" to version 2 | | +| | | CP-050290 | 276 | | Defining a default value for "Echo cancelling" property | | +| | | CP-050309 | 278 | 1 | Correction on Burst interval duration | | +| | | CP-050308 | 281 | 1 | Clarification of "Normal Release" parameter | | +| Dec 2005 | CT#30 | CP-050603 | 0261 | 2 | Correction to clarify TFO Package use | 6.4.0 | +| | | CP-050607 | 0288 | 1 | Clarification to client/server behaviour with regards to SCTP Initiation | | +| | | CP-050607 | 0289 | 1 | Inclusion of Error Code #449 for unsupported parameter value | | +| | | CP-050618 | 0290 | 1 | Correction to Continuity Test Procedure | | +| | | CP-050607 | 0296 | 1 | Setting of CN/Outgoing Nb termination prior to bearer establishment | | +| | | CP-050607 | 0304 | 2 | Correction to use of BITRATE for CSD calls | | +| | | CP-050607 | 0308 | 1 | Bearer Released Event to Reserve Circuit procedure | | +| | | CP-050607 | 0322 | 1 | Corrections to use of GSM-Channel Coding for CSD | | +| | | CP-050618 | 0323 | 3 | Correct MCC Error in implementing CR #238 | | +| 2005-12 | CT#30 | CP-050629 | 0302 | 2 | Clean-up of hanging contexts and terminations | 7.0.0 | +| | | CP-050629 | 0309 | 1 | Clarification of MGW capability change | | +| 2006-03 | CT#31 | CP-060078 | 0307 | 2 | Clarification of Termination Restoration and Termination Out-of-Service procedures | 7.1.0 | +| | | CP-060064 | 0326 | 2 | Correction To Termination State Handling | | +| | | CP-060064 | 0329 | 1 | Send Tone procedure | | +| | | CP-060064 | 0330 | 1 | ContextID in Change Flow Direction response | | +| | | CP-060064 | 0333 | 1 | Correction To DTMF Detection | | +| | | CP-060078 | 0337 | 1 | Clarification to use of ServiceChangeMGCIId | | +| | | CP-060078 | 0338 | | Clarification to cut-through procedure | | +| | | CP-060064 | 0345 | 2 | Adding missing termination ID to Acknowledgement part of notification procedures | | +| | | CP-060078 | 0342 | 1 | Correction to syntax for event descriptions | | +| | | CP-060064 | 0348 | | Adding missing Codec, Bearer Characteristics and Bearer Service Characteristics to Prepare IP transport procedure | | +| | | CP-060067 | 0352 | 1 | Correction on the used descriptor for trace package | | +| 2006-06 | CT#32 | CP-060315 | 0377 | 2 | Introduction of Profile Description Annex to Mc interface | 7.2.0 | +| | | CP-060315 | 0379 | | Corrections to Formats and Codes table | | +| | | CP-060315 | 0382 | 1 | Clarification of H.248.2 version in references | | +| | | CP-060315 | 0386 | | Correction of the error definition of Flextone | | +| | | CP-060307 | 0370 | | Corrigendum for H.248.1 version 2 | | +| | | CP-060301 | 0365 | 2 | DTMF Detection Type | | +| | | CP-060301 | 0368 | 1 | Sequential Signal Lists | | +| | | CP-060301 | 0374 | 2 | Multimedia & CSD calls | | +| | | CP-060301 | 0385 | 1 | Clarification of ROOT termination naming | | +| 2006-09 | CT#33 | CP-060411 | 0388 | 1 | Profile Description Annex: Connection model and Context Attributes | 7.3.0 | +| | | CP-060411 | 0389 | 2 | Profile Description Annex: Terminations | | +| | | CP-060411 | 0390 | 2 | Profile Description Annex: Descriptors | | +| | | CP-060411 | 0391 | 1 | Profile Description Annex: Message, Transport and Security | | +| | | CP-060411 | 0392 | 1 | Profile Description Annex: Mandatory and optional packages | | +| | | CP-060411 | 0393 | 2 | Profile Description Annex: H.248 packages | | +| | | CP-060411 | 0394 | 2 | Profile Description Annex: BICC packages | | +| | | CP-060411 | 0395 | 2 | Profile Description Annex: Mandatory and optional 3G packages | | +| | | CP-060411 | 0396 | 1 | Profile Description Annex : Command API | | +| | | CP-060411 | 0397 | 1 | Profile Description Annex : Generic command syntax and encoding | | +| | | CP-060411 | 0398 | 1 | Profile Description Annex : Transactions | | +| | | CP-060411 | 0399 | 1 | Profile Description Annex : Mandatory support of SDP and Annex C information elements | | +| | | CP-060411 | 0400 | 1 | Profile Description Annex : Optional support of SDP and Annex C information elements | | +| | | CP-060411 | 0401 | | Encoding of G.711 codec | | + +| Date | TSG # | TSG Doc. | CR | Re v | Subject/Comment | New | +|---------|-------|-----------|------|------|-------------------------------------------------------------------------------------|-------| +| | | CP-060400 | 0404 | 3 | Profile registration procedure | | +| | | CP-060411 | 0407 | 2 | Definition of the use of mandatory and optional in Mc Profile Template | | +| | | CP-060402 | 0409 | | Trace Package ID | | +| | | CP-060400 | 0412 | | AuditValue procedure | | +| | | CP-060400 | 0415 | 1 | Use of topology for tones and announcements | | +| | | CP-060397 | 0420 | | Modification of eventId named distant codec_list in threegtfoc package | | +| | | CP-060402 | 0427 | | Wildcarding of Release Termination Response | | +| | | CP-060400 | 0430 | | Correction to Emergency Call Indication Procedure | | +| | | CP-060400 | 0436 | 1 | Use of IPSec for Mc Interface | | +| | | CP-060400 | 0439 | 2 | Correction to use of Local Peer for CSD when Anchor MGW | | +| | | CP-060411 | 0441 | 2 | New Error Code for Temporary Busy | | +| | | CP-060411 | 0442 | 1 | Profile Description Annex: Descriptors (complements) | | +| | | CP-060411 | 0443 | | Profile Description Annex: Trace package | | +| 2006-12 | CT#34 | CP-060402 | 0447 | | Incomplete list of optional UMTS packages | 7.4.0 | +| | | CP-060569 | 0376 | 6 | Enhancements for VGCS/VBS in SPLIT architecture | | +| | | CP-060569 | 0452 | | Correct the initiator of NOT.resp command | | +| | | CP-060569 | 0474 | 1 | Removal of TBD for Number of Commands Per Transaction | | +| | | CP-060569 | 0485 | 1 | Event Tunnel indication for type BICC IP | | +| | | CP-060569 | 0486 | | Tunnel Option shall be used with Add.Req only | | +| | | CP-060569 | 0487 | | IP transport package properties not used within Mov.Req | | +| | | CP-060552 | 0459 | | Encoding of PLMN BC | | +| | | CP-060561 | 0461 | 1 | Trace package correction | | +| | | CP-060554 | 0464 | | Commands in Change flow direction procedure | | +| 2007-03 | CT#35 | CP-060718 | 0481 | 3 | Definite vs Indefinite encoding rules for binary H.248 | 7.5.0 | +| | | CP-070014 | 0490 | 3 | IP domain connection indication | | +| | | CP-070014 | 0491 | | Commands Marked Optional | | +| | | CP-070014 | 0494 | 1 | Prevention of signalling overload due to Notifications | | +| | | CP-070009 | 0497 | | Exclusion of use of inherited properties from network package | | +| | | CP-070014 | 0498 | 1 | Changing Profile description Annex C from Informative to Normative | | +| | | CP-070009 | 0501 | 1 | Signal List ID to Announcement Completed procedure | | +| 2007-06 | CT#36 | CP-070014 | 0508 | 1 | Stream ID parameters in Signals and Events | 7.6.0 | +| | | CP-070314 | 0511 | 1 | IMSI/IMEI encoding in trace package | | +| | | CP-070322 | 0512 | | Adding package ID to ASCI package | | +| | | CP-070322 | 0513 | | ServiceChangeMGCId parameter | | +| | | CP-070308 | 0520 | | RFC 3309 for SCTP checksum | | +| 2007-09 | CT#37 | CP-070322 | 0522 | | Modification to EventID name definition | 7.7.0 | +| | | CP-070530 | 0524 | 3 | Service Change Methods and Reasons | | +| | | CP-070530 | 0527 | | H.248 Message Encoding | | +| | | CP-070530 | 0528 | 1 | General Corrections To Profile | | +| | | CP-070530 | 0531 | 2 | Mc profile corrections | | +| | | CP-070530 | 0535 | 2 | Support inactivity timer (H.248.14) for MGWs detecting the failure of MGC | | +| 2007-09 | CT#37 | CP-070530 | 0537 | 1 | Completion of Text Telephony and Call Discrimination Packages | 8.0.0 | +| 2007-10 | | CP-070569 | 0536 | 3 | Mandatory use termination heartbeat (H.248.36) when establish bearer/prepare bearer | 8.0.1 | +| 2007-12 | CT#38 | | | | Track marks removed | 8.1.0 | +| | | CP-070752 | 0538 | 2 | Mc enhancements for SIP-I support | | +| | | CP-070756 | 0539 | 1 | Examples for Usage of the 3GUP Package "Initialization Direction" Property | | +| | | CP-070756 | 0541 | 1 | Optional reporting of normal AAL2 bearer release | | +| | | CP-070756 | 0556 | 1 | Individual audit of TDM termination | | +| | | CP-070749 | 0545 | | Heartbeat event in Send Tone and Play Announcement procedures | | +| | | CP-070749 | 0551 | 1 | Event Descriptor correction in Mc profile | | +| | | CP-070749 | 0553 | | Reference corrections | | +| | | CP-070749 | 0555 | 1 | Number of needed listener context terminations to ASCI package | | +| 2008-03 | CT#39 | CP-070740 | 0549 | 1 | Sequencing of Termination Out-of-Service and Termination Restoration procedures | 8.2.0 | +| | | CP-080020 | 0557 | 1 | Reserve / Configure RTP Connection Point, Modify Bearer Characteristics | | +| | | CP-080020 | 0558 | 1 | Other codecs for SIP-I based Nc | | +| | | CP-080011 | 0562 | 1 | BNC events in Prepare Bearer / Establish Bearer procedures | | +| | | CP-080025 | 0564 | | CAMEL prepaid warning tone missing from formats and codes table | | +| 2008-06 | CT#40 | CP-080020 | 0575 | 1 | Applicability of descriptors to RTP terminations | 8.3.0 | +| | | CP-080270 | 0585 | | Coding of the UDP Port Property | | + +| Date | TSG # | TSG Doc. | CR | Re
v | Subject/Comment | New | +|---------|------------|-----------|------|---------|------------------------------------------------------------------------------------|--------| +| | | CP-080269 | 0581 | 1 | Use of Release Bearer Procedure | | +| | | CP-080271 | 0576 | 1 | Correction of the inconsistencies in several procedures' description | | +| | | CP-080264 | 0577 | 2 | A interface over IP support | | +| | | CP-080262 | 0578 | 1 | Addition of SIP-I based Nc within the scope of TS 29.232 | | +| 2008-09 | CT#41 | CP-080466 | 0591 | 3 | IP interface type indicator | 8.4.0 | +| | | CP-080466 | 0592 | 1 | Use of Global Text Telephony with A over IP | | +| | | CP-080466 | 0593 | | Use of 'plmnbc' and 'gsm channel coding' in AoIP | | +| | | CP-080461 | 0594 | 1 | Expansion of scope for IMS Centralised Service Access | | +| | | CP-080466 | 0599 | | Support of GSM codec | | +| | | CP-080468 | 0601 | | CTM properties setting | | +| | | CP-080466 | 0604 | 1 | Emergency Call Indication for AoIP and SIP-I terminations | | +| | | CP-080453 | 0608 | | Service Change Reason in (G)MSC Server Out of Service | | +| 2008-12 | CT#42 | CP-080686 | 0610 | 1 | SDP Media Parameters For RTP Terminations | 8.5.0 | +| | | CP-080705 | 0611 | 1 | IP transport package properties handling | | +| | | CP-080697 | 0612 | 2 | No Data frame handling independent of Stream Mode property | | +| | | CP-080705 | 0613 | - | Adding package ID to 3G Interface Type package | | +| | | | 0617 | 2 | Support of Redundancy for CSD in Mc interface for AoIP | | +| | | | 0618 | 1 | CTM transport property in the Reserve and Configure RTP connection Point procedure | | +| | | | 0621 | | IP interface type for external SIP-I based network | | +| 2009-03 | CT#43 | CP-090034 | 0622 | - | Solving Incorrect references | 8.6.0 | +| | | | 0623 | | Removing of IP transport package from packages chapter of Mc profile | | +| 2009-06 | CT#44 | CP-090297 | 0624 | 1 | Missing Signalling Object in Formats and Codes table | 8.7.0 | +| 2009-09 | CT#45 | CP-090541 | 0625 | | Clarification of Use of Reserve and Configure RTP Connection Point | 8.8.0 | +| | | CP-090541 | 0626 | 1 | Missing RTP procedures from Circuit Switched Data package description | | +| | | CP-090544 | 0627 | - | Audit of Hanging Termination Detection package | | +| 2009-12 | CT#46 | CP-090763 | 0628 | - | Commands Using IP Interface Type | 8.9.0 | +| 2009-12 | CT#46 | | | | Upgraded unchanged from Rel-8 | 9.0.0 | +| 2010-04 | | | | | History table corrected | 9.0.1 | +| 2011-03 | CT#51 | CP-110100 | 0629 | 1 | Adding CS-Ix functionalities to Mc-profile | 9.1.0 | +| 2011-03 | CT#51 | CP-110277 | 0630 | 10 | ECN Support in Mc Interface | 10.0.0 | +| 2011-03 | CT#51 | CP-110070 | 0631 | 1 | Complete Inactivity Timeout Indication Procedure | | +| 2011-06 | CT#52 | CP-110368 | 0635 | 1 | ECN Failure improvements | 10.1.0 | +| | | CP-110368 | 0637 | 1 | Alignment of 3GPP profiles with SG16 ECN package definition | | +| 2011-09 | CT#53 | CP-110563 | 0639 | - | Media inactivity notification procedure | 10.2.0 | +| 2011-12 | CT#54 | CP-110789 | 0640 | 1 | ECN Improvements | 10.3.0 | +| 2012-06 | CT#56 | CP-120226 | 0641 | 1 | Reference update: draft-ietf-avtcore-ecn-for-rtp | 10.4.0 | +| 2012-09 | CT#57 | CP-120478 | 0642 | 1 | Support of Multimedia Priority Service (MPS) over Mc Interface – Stage 3 | 11.0.0 | +| 2012-12 | CT#58 | CP-120723 | 0646 | - | Mc interface updates of ECN Support Package | 11.1.0 | +| 2012-12 | CT#58 | CP-120727 | 0648 | 1 | H.248.52 Status Update | 11.1.0 | +| 2013-06 | CT#60 | CP-130294 | 0650 | 2 | ECN relying reference change | 11.2.0 | +| 2014-06 | CT#64 | CP-140248 | 0655 | 2 | ICE support in Mc interface | 12.0.0 | +| 2014-12 | CT#66 | CP-140788 | 0656 | 1 | Adding support for EVS codec | 12.1.0 | +| 2015-06 | CT#68 | CP-150272 | 0657 | 1 | Adding support for the EVS codec over UMTS CS | 13.0.0 | +| 2016-03 | CT#71 | CP-160048 | 0658 | 1 | Removal of references to TS 26.236 | 13.1.0 | +| 2016-03 | CT#71 | CP-160027 | 0659 | - | Resolution of Editor's note on EVS over UMTS CS | 13.1.0 | +| 2016-03 | CT#71 | CP-160021 | 0660 | 1 | Mc stage 3 to support SDP Capability Negotiation | 13.1.0 | +| 2016-12 | CT#74 | CP-160662 | 0661 | 1 | Update to example of Mc Single Codec encoding for EVS | 13.2.0 | +| 2017-03 | - | - | - | - | Update to Rel-14 version (MCC) | 14.0.0 | +| 2018-06 | CT#88
e | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-07 | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/29_series/29235/08e8bbb2a063a3935a0c649b39ade125_img.jpg b/marked/Rel-16/29_series/29235/08e8bbb2a063a3935a0c649b39ade125_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c38d2edb2f7a55fcf612396a4d641f991b0f12a0 --- /dev/null +++ b/marked/Rel-16/29_series/29235/08e8bbb2a063a3935a0c649b39ade125_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b455765c73787a06fa4e73e9a4ea6d7eebe3339755476bd4584508280c0b1c86 +size 45549 diff --git a/marked/Rel-16/29_series/29235/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/Rel-16/29_series/29235/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa85798fbbcd92ba33dbea1102d05f51f054e255 --- /dev/null +++ b/marked/Rel-16/29_series/29235/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62a1df3bd51d4a60cba86f98a349b1b9284b84e28c0ef931d8fd3df103aeb6f6 +size 71094 diff --git a/marked/Rel-16/29_series/29235/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg b/marked/Rel-16/29_series/29235/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e9383191d6db829a242aa79fbac35d690098afe --- /dev/null +++ b/marked/Rel-16/29_series/29235/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60307b3e82b2c56785e63cedb00a948175f0536c3505e913f7f050fd346bfda4 +size 29285 diff --git a/marked/Rel-16/29_series/29235/26e334e61dd059cff029338a2a604d8d_img.jpg b/marked/Rel-16/29_series/29235/26e334e61dd059cff029338a2a604d8d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b8b6bc77fe4a97c183a21e1df0b6fdeb825a37b --- /dev/null +++ b/marked/Rel-16/29_series/29235/26e334e61dd059cff029338a2a604d8d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0606bef9eabffc4f1e4b0cd57ae1046eff00b63865676bb2459f907df6524a45 +size 26595 diff --git a/marked/Rel-16/29_series/29235/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-16/29_series/29235/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8dee38ec4f9cc9a189af1b8767ba4d76cfc0294 --- /dev/null +++ b/marked/Rel-16/29_series/29235/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f98ad7f9b88a644e30767db069a4f4866c3879d005c1fbd5f2deb0fd8974ff00 +size 155424 diff --git a/marked/Rel-16/29_series/29235/2d863654cf3803cea82b686d9b3ebee8_img.jpg b/marked/Rel-16/29_series/29235/2d863654cf3803cea82b686d9b3ebee8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cd6dc6dbfbac4a33ae97b219cd5bd5a864eefaa --- /dev/null +++ b/marked/Rel-16/29_series/29235/2d863654cf3803cea82b686d9b3ebee8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9b8369d19519e189e9fbd6e2254d84fe56eb0438887bb1374a80355043446cb +size 26182 diff --git a/marked/Rel-16/29_series/29235/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Rel-16/29_series/29235/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..de30722ecb8f4b4cd0782a8bec300b5f585a833b --- /dev/null +++ b/marked/Rel-16/29_series/29235/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fb105a73206625274b4b7ba094a870437cf4b1111cfaa07bc838fd742071062 +size 136043 diff --git a/marked/Rel-16/29_series/29235/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/29_series/29235/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba1d3dcea77d3da20fc52a0ef3bf6c018e2b07d6 --- /dev/null +++ b/marked/Rel-16/29_series/29235/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:daf1714ef521d6f38f6fabcea3e546656e07b0e87b90e040f19aec356a52cca9 +size 53462 diff --git a/marked/Rel-16/29_series/29235/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-16/29_series/29235/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..803726c51b52b0622f553a525f92d3cf2f1a216a --- /dev/null +++ b/marked/Rel-16/29_series/29235/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c1dc7f20fc8c0b395fd70224f545c8b3fe0c8fca24e8c655895e29247c98d92 +size 77999 diff --git a/marked/Rel-16/29_series/29235/3c04b14104f95eb8f7100f6d497d956e_img.jpg b/marked/Rel-16/29_series/29235/3c04b14104f95eb8f7100f6d497d956e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea4d6628c9e666999cb32f5a81eae0b0436a4667 --- /dev/null +++ b/marked/Rel-16/29_series/29235/3c04b14104f95eb8f7100f6d497d956e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af4fb263c6e7d4a0b267828af39841dbf0b415b778e5f4b5dce0b8c2426b38e0 +size 165293 diff --git a/marked/Rel-16/29_series/29235/421fc75480c21e7ebb25756826652367_img.jpg b/marked/Rel-16/29_series/29235/421fc75480c21e7ebb25756826652367_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e984fe327a20121363a02011c51e6f7247f87ce --- /dev/null +++ b/marked/Rel-16/29_series/29235/421fc75480c21e7ebb25756826652367_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39393ca32831d941b215ae5dd1ab1d6f142e0f3b5ac1e1aae67d07210707c4c4 +size 32755 diff --git a/marked/Rel-16/29_series/29235/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-16/29_series/29235/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a05685e95c99d8c0cee676f6bbc0e02536e2c04 --- /dev/null +++ b/marked/Rel-16/29_series/29235/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4864e4a56b8a81cf2832d43118e706fdef9a9ae2c1a688d9e869ba185108a9a1 +size 186439 diff --git a/marked/Rel-16/29_series/29235/747516f5861a0ddf31e3851da8e34b95_img.jpg b/marked/Rel-16/29_series/29235/747516f5861a0ddf31e3851da8e34b95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..baa32e692972f22d89ef63f4937e33e1a0a040ee --- /dev/null +++ b/marked/Rel-16/29_series/29235/747516f5861a0ddf31e3851da8e34b95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09078281c4cf7a5fce5cde525f76a56219ba68edd2beabfd0d0ff334a9475fa1 +size 17574 diff --git a/marked/Rel-16/29_series/29235/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-16/29_series/29235/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e04bcd2548fd1d81e2b081001b54e1027c927ac0 --- /dev/null +++ b/marked/Rel-16/29_series/29235/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22f499008b8a98a7082b6e62fdd872062651c6883eb485c9363cf02f347bc8eb +size 97181 diff --git a/marked/Rel-16/29_series/29235/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-16/29_series/29235/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a56b53303c4e44b9c7357de10a1a6d58ed36a97c --- /dev/null +++ b/marked/Rel-16/29_series/29235/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e3fc58136316c6446496dfe815f124fad69a3c9d680f56261b3891263d8ec6d +size 69587 diff --git a/marked/Rel-16/29_series/29235/836b0790cef5469a167fa8931df4e408_img.jpg b/marked/Rel-16/29_series/29235/836b0790cef5469a167fa8931df4e408_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cb4ae4a4d0a6ad715706700faa7cf9111477b98 --- /dev/null +++ b/marked/Rel-16/29_series/29235/836b0790cef5469a167fa8931df4e408_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:246ad46b09a6a2f288d4917b149048b9c95274b05a87ff7fdc4f5b4ae95a2752 +size 28033 diff --git a/marked/Rel-16/29_series/29235/86bd357c573c9696393f5bde4d4cce4f_img.jpg b/marked/Rel-16/29_series/29235/86bd357c573c9696393f5bde4d4cce4f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6b46ad19e4b25f39d9e1ef7d7f4c15daf55b89a --- /dev/null +++ b/marked/Rel-16/29_series/29235/86bd357c573c9696393f5bde4d4cce4f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbff368fe6295548b7be95f52c6ded18d84c6c752da22941fe426b5e53796724 +size 20912 diff --git a/marked/Rel-16/29_series/29235/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-16/29_series/29235/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a478045159814640aeebf1171c07f7d0982f749 --- /dev/null +++ b/marked/Rel-16/29_series/29235/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18f9277e6f6864796038f63fefd49a38a327e779798d2a9a72797cc75f244c2d +size 21847 diff --git a/marked/Rel-16/29_series/29235/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/29_series/29235/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c638db78201d88fe54a7ef66fbb60b3f5ea0a6e4 --- /dev/null +++ b/marked/Rel-16/29_series/29235/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a864cfbb4640882d88e016f7c533abe9fc7c2167e838afdf970f2a3a9e9aca71 +size 186523 diff --git a/marked/Rel-16/29_series/29235/99781d878388c3e0f359b1d6ce14119c_img.jpg b/marked/Rel-16/29_series/29235/99781d878388c3e0f359b1d6ce14119c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ef61074406dfdc6e8ed2e9015488bd9f73dad43 --- /dev/null +++ b/marked/Rel-16/29_series/29235/99781d878388c3e0f359b1d6ce14119c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c25dd209b1a080822fee7bf0530d38171362c94cb4407a211c897d6d51c7637 +size 17754 diff --git a/marked/Rel-16/29_series/29235/9a14684f8ae1345c6efea6f5994c730c_img.jpg b/marked/Rel-16/29_series/29235/9a14684f8ae1345c6efea6f5994c730c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73d245ea4139ed4175528ad035f86ca3012021c6 --- /dev/null +++ b/marked/Rel-16/29_series/29235/9a14684f8ae1345c6efea6f5994c730c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34983d5e1ec9c53a9c891b0059f3846ff50e6661354c983619328fb4f075f39e +size 73179 diff --git a/marked/Rel-16/29_series/29235/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-16/29_series/29235/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35fdc6614c94696e7399737581a90569391632e9 --- /dev/null +++ b/marked/Rel-16/29_series/29235/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e5bbb032e353b96c1454c93a13ac545f8dff80879bed76249a4f98e70d3c448 +size 176172 diff --git a/marked/Rel-16/29_series/29235/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/29_series/29235/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c72d4a098f4770c072dc571daded8c8e3275726 --- /dev/null +++ b/marked/Rel-16/29_series/29235/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f70fbb64abf49ce2b71dbb919167bb9c413ba9cb6c2b002e68c59c458fa00045 +size 197546 diff --git a/marked/Rel-16/29_series/29235/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/29_series/29235/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c4c5d88f372e07e28f6bcca2f562fa4298829c8 --- /dev/null +++ b/marked/Rel-16/29_series/29235/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3057aa1615aeaae4e41b10c0e8cb6415033f8faf518203156e87a70317772f3d +size 42605 diff --git a/marked/Rel-16/29_series/29235/a4bfa2343d75076b79f7e33d93915e00_img.jpg b/marked/Rel-16/29_series/29235/a4bfa2343d75076b79f7e33d93915e00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34b34c16c4805f19390187ee88ac4f50fb827f95 --- /dev/null +++ b/marked/Rel-16/29_series/29235/a4bfa2343d75076b79f7e33d93915e00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e75d7c570cd86177b22e66da8f201d12d9df99bb1e9498b2c504578e02a54e5 +size 160035 diff --git a/marked/Rel-16/29_series/29235/a70e0adcabc973b01b413b6a141884f3_img.jpg b/marked/Rel-16/29_series/29235/a70e0adcabc973b01b413b6a141884f3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..faa07d220986d30a124f248f69c968ac7bdecc78 --- /dev/null +++ b/marked/Rel-16/29_series/29235/a70e0adcabc973b01b413b6a141884f3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93aaabdfee7cbb9f5593c2be36b70dadfacdbfabe8fad323d6bdf362f7c993b3 +size 42266 diff --git a/marked/Rel-16/29_series/29235/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/29_series/29235/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfed976a556891f7cc74b2f4edb7214770291437 --- /dev/null +++ b/marked/Rel-16/29_series/29235/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8aeda62b03be828c76404e234377f93577c62b82c41d8349738559719e1c4189 +size 175966 diff --git a/marked/Rel-16/29_series/29235/b6ad8b32179842fca5ad086cf22b03eb_img.jpg b/marked/Rel-16/29_series/29235/b6ad8b32179842fca5ad086cf22b03eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f278cab33f35abe190091582be1e753866ef0698 --- /dev/null +++ b/marked/Rel-16/29_series/29235/b6ad8b32179842fca5ad086cf22b03eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:246adfac0819adb4ac7c5dc357abff84daf76a0e0fdedb71916d79130a657892 +size 54755 diff --git a/marked/Rel-16/29_series/29235/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg b/marked/Rel-16/29_series/29235/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e1ab2fd3ea9f9b53458d9e3e8b88064f97d1ab3 --- /dev/null +++ b/marked/Rel-16/29_series/29235/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a09feab251c0306069a1660ee479da7f78e58012749ea90e1a043250729d5b6 +size 30990 diff --git a/marked/Rel-16/29_series/29235/d8698aacaeead6dfed9a1e448670a2e4_img.jpg b/marked/Rel-16/29_series/29235/d8698aacaeead6dfed9a1e448670a2e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..120afc9c013208fcd537993ec89353733d97770c --- /dev/null +++ b/marked/Rel-16/29_series/29235/d8698aacaeead6dfed9a1e448670a2e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33b07d5a28c14f47510143e412e318bdc21923d868c43b88aa65da1ce6f89cc2 +size 38300 diff --git a/marked/Rel-16/29_series/29235/dbbc0baac7341cda76cc4f8355dce23f_img.jpg b/marked/Rel-16/29_series/29235/dbbc0baac7341cda76cc4f8355dce23f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..415ae96f681c946014cf3cea2f966a5a3745c100 --- /dev/null +++ b/marked/Rel-16/29_series/29235/dbbc0baac7341cda76cc4f8355dce23f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:150ceb8e4d0a7f06e29d92b776225608edcc12137b591913ca7594446368a014 +size 53456 diff --git a/marked/Rel-16/29_series/29235/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/29_series/29235/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0c6f1e420b2429cb09d98118fc995479af54bca --- /dev/null +++ b/marked/Rel-16/29_series/29235/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb27790d0e053c545c10b394d1ea0cbee160c962db0354348f8f1d487372b941 +size 183376 diff --git a/marked/Rel-16/29_series/29235/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/29_series/29235/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f36d94bb588c8325874668f0968bf36ca185a3e --- /dev/null +++ b/marked/Rel-16/29_series/29235/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:477604459bf5dcc2dcb12ead511a0814e72382553ffb839a00766b04ecc02de8 +size 178391 diff --git a/marked/Rel-16/29_series/29235/f468e577645d646f5157ce3eefb4ed96_img.jpg b/marked/Rel-16/29_series/29235/f468e577645d646f5157ce3eefb4ed96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..815bc44eec0f74eac3a1705da058285248e31fa8 --- /dev/null +++ b/marked/Rel-16/29_series/29235/f468e577645d646f5157ce3eefb4ed96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8535f57de6ca083e22cd066e63c49e408806dfa2ed0773a6a7da63cd965b4d8b +size 54716 diff --git a/marked/Rel-16/29_series/29235/raw.md b/marked/Rel-16/29_series/29235/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ad08ae2a0a4000f29c4f2ab1f831313ad8ede692 --- /dev/null +++ b/marked/Rel-16/29_series/29235/raw.md @@ -0,0 +1,3749 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 9 | +| 1 Scope..... | 10 | +| 2 References..... | 10 | +| 3 Definitions and abbreviations ..... | 12 | +| 3.1 Definitions..... | 12 | +| 3.2 Abbreviations ..... | 13 | +| 4 Interworking between a SIP-I based circuit-switched core network and an external SIP-I based network..... | 14 | +| 4.1 Reference Model ..... | 14 | +| 4.2 Signalling Interworking of a Call from the external SIP-I based network towards the SIP-I based circuit-switched core network..... | 15 | +| 4.2.1 Interworking of SIP-I messages received from external SIP-I network..... | 15 | +| 4.2.1.1 General..... | 15 | +| 4.2.1.2 Call Release from external SIP-I network when encapsulated REL is missing ..... | 15 | +| 4.2.2 Special Procedures for the reception of initial SIP INVITE requests ..... | 15 | +| 4.2.2.1 Receipt of SIP INVITE request ..... | 15 | +| 4.2.2.2 Receipt of SIP INVITE requests with SDP ..... | 15 | +| 4.2.2.3 Receipt of SIP INVITE request without SDP..... | 15 | +| 4.2.2.4 MGW Selection ..... | 16 | +| 4.2.3 Interworking of SIP-I messages received from succeeding 3GPP node ..... | 16 | +| 4.2.4 Special Procedures for Profile Interworking ..... | 16 | +| 4.2.4.1 Support of 100Rel..... | 16 | +| 4.2.4.2 Support for UPDATE method ..... | 16 | +| 4.2.4.3 Support for Preconditions ..... | 17 | +| 4.2.5 Support for Codec Negotiation..... | 17 | +| 4.2.6 Special Procedures for the reception of SIP Re-INVITE requests..... | 17 | +| 4.2.6.1 Receipt of SIP Re-INVITE request without SDP ..... | 17 | +| 4.3 Signalling Interworking of a Call from SIP-I based circuit-switched core network towards the external SIP-I based network ..... | 18 | +| 4.3.1 Interworking of SIP-I messages received from preceding 3GPP node ..... | 18 | +| 4.3.1.1 General..... | 18 | +| 4.3.1.2 Call Release from external SIP-I network when encapsulated REL is missing ..... | 18 | +| 4.3.2 Special Procedures for the reception of SIP INVITE requests..... | 18 | +| 4.3.3 Special Procedures for Profile Interworking ..... | 18 | +| 4.3.3.1 Support of 100Rel..... | 18 | +| 4.3.3.2 Support for UPDATE method ..... | 19 | +| 4.3.3.3 Support for Preconditions ..... | 19 | +| 4.3.4 Support for Codec Negotiation..... | 20 | +| 4.3.5 MGW Selection ..... | 20 | +| 4.4 DMTF Signalling Interworking applicable for all Calls between an external SIP-I based network and a SIP-I based circuit-switched core network..... | 21 | +| 4.4.1 General ..... | 21 | +| 4.4.2 DTMF support in SDP offer sent to External SIP-I network ..... | 21 | +| 4.4.3 DTMF support in SDP offer received from External SIP-I network ..... | 22 | +| 4.5 User Plane Interworking..... | 23 | +| 4.5.1 General ..... | 23 | +| 4.5.2 DTMF Interworking ..... | 23 | +| 4.6 Example Call flows ..... | 23 | +| 4.6.1 General ..... | 23 | +| 4.6.2 Incoming Call flows ..... | 24 | +| 4.6.2.1 Incoming Call - no preconditions in external network ..... | 24 | +| 4.6.2.2 Incoming Call with preconditions not met ..... | 26 | +| 4.6.3 Outgoing Call flows ..... | 28 | +| 4.6.3.1 Outgoing Call with support for preconditions ..... | 28 | +| 4.6.3.2 Outgoing Call with support of 100rel but no support for preconditions ..... | 30 | +| 4.6.3.3 Outgoing Call without support for 100rel and preconditions ..... | 32 | + +| | | | +|-----------|------------------------------------------------------------------------------------------------------------------------------------|----| +| 5 | Interworking between a SIP-I based circuit-switched core network and an ISUP based network..... | 34 | +| 5.1 | Reference Model ..... | 34 | +| 5.2 | Control Plane Interworking ..... | 34 | +| 5.3 | Signalling Interworking of a Call from the ISUP based network towards the SIP-I based circuit-switched core network..... | 36 | +| 5.3.1 | General ..... | 36 | +| 5.3.1.1 | Sending of ISUP information to adjacent SIP nodes ..... | 36 | +| 5.3.1.2 | Receipt of encapsulated ISUP information within SIP-I ..... | 36 | +| 5.3.1.3 | Special procedures related to outgoing INVITE..... | 37 | +| 5.3.1.3.1 | Overlap Signalling..... | 37 | +| 5.3.1.3.2 | Coding of encapsulated ISUP IAM parameters in outgoing INVITE ..... | 37 | +| 5.3.1.3.3 | Media offered in SDP of outgoing INVITE..... | 37 | +| 5.4 | Signalling Interworking of a Call from SIP-I based circuit-switched core network towards the ISUP based network..... | 37 | +| 5.4.1 | General ..... | 37 | +| 5.4.2 | Interworking of received ISUP messages to SIP messages..... | 37 | +| 5.4.3 | Interworking of received SIP messages to ISUP messages..... | 37 | +| 5.4.3.1 | Receipt of encapsulated ISUP information within SIP..... | 37 | +| 5.4.3.2 | Special Procedures for the Reception of SIP INVITE request ..... | 38 | +| 5.4.3.2.1 | Propagation of overlap signalling toward the 3GPP CS domain ..... | 38 | +| 5.4.3.2.2 | Derivation of TMR, USI and HLC parameters within sent IAM message..... | 38 | +| 5.4.3.2.3 | Receipt of SIP INVITE without SDP offer ..... | 38 | +| 5.4.3.2.4 | Special Procedures for deferred MGW selection procedure..... | 38 | +| 5.5 | Supplementary services..... | 38 | +| 5.5.1 | Special procedures for supplementary service interworking..... | 38 | +| 5.5.2 | Interworking of CLIP/CLIR supplementary service ..... | 39 | +| 5.5.3 | Interworking of Call Hold (HOLD) supplementary service..... | 39 | +| 5.5.4 | Interworking of Completion of Calls to Busy Subscriber (CCBS) supplementary service to SIP networks ..... | 39 | +| 5.6 | User Plane Interworking..... | 39 | +| 5.6.1 | General ..... | 39 | +| 5.6.2 | DTMF ..... | 39 | +| 5.7 | Example Call flows ..... | 40 | +| 6 | Interworking between a SIP-I based circuit-switched core network and a BICC based network ..... | 40 | +| 6.1 | Reference Model ..... | 40 | +| 6.2 | Control Plane Interworking ..... | 41 | +| 6.2.1 | General ..... | 41 | +| 6.2.2 | Signalling interactions between network entities in the control plane ..... | 41 | +| 6.3 | Signalling Interworking of a Call from the BICC based network towards the SIP-I based circuit-switched core network..... | 42 | +| 6.4 | Signalling Interworking of a Call from SIP-I based circuit-switched core network towards the BICC based network..... | 42 | +| 6.5 | Supplementary services..... | 42 | +| 6.6 | Codec Negotiation between a BICC based network and a SIP-I based circuit-switched core network ..... | 43 | +| 6.6.1 | General ..... | 43 | +| 6.6.2 | Codec Negotiation from SIP-I on Nc to BICC Network..... | 43 | +| 6.6.2.1 | Sending of IAM ..... | 43 | +| 6.6.2.2 | Sending of SDP Answer ..... | 43 | +| 6.6.2.3 | Mid-call Codec Negotiation initiated from SIP-I on Nc..... | 43 | +| 6.6.3 | Codec Negotiation from BICC Network to SIP-I on Nc..... | 43 | +| 6.6.3.1 | Sending of initial SDP Offer..... | 43 | +| 6.6.3.2 | Responding to Serving Node initiating Codec Negotiation..... | 43 | +| 6.6.3.3 | Mid-call Codec Negotiation initiated from BICC ..... | 44 | +| 6.7 | DMTF Signalling Interworking applicable for all Calls between a BICC network and a SIP-I based circuit-switched core network ..... | 44 | +| 6.7.1 | General ..... | 44 | +| 6.7.2 | DTMF transfer from SIP-I on Nc to BICC network (Out-of-Band DTMF) ..... | 44 | +| 6.7.3 | DTMF transfer from BICC network (Out-of-Band DTMF) to SIP-I on Nc ..... | 45 | +| 6.7.4 | SIP-I on Nc interworking with BICC for Inband DTMF ..... | 46 | +| 6.8 | User Plane Interworking..... | 46 | +| 6.8.1 | General ..... | 46 | + +| | | | +|---------|--------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 6.8.2 | DTMF Interworking ..... | 46 | +| 6.9 | Example Call flows ..... | 46 | +| 7 | Interworking between a SIP-I based circuit-switched core network and the IP Multimedia (IM) Core Network (CN) Subsystem ..... | 47 | +| 7.1 | Reference Model ..... | 47 | +| 7.1.1 | General ..... | 47 | +| 7.1.2 | Signalling interactions between network entities in the control plane ..... | 47 | +| 7.2 | Signalling Interworking of a Call from the IP Multimedia Subsystem towards the SIP-I based circuit-switched core network..... | 48 | +| 7.2.1 | General ..... | 48 | +| 7.2.2 | Exceptions from forwarding received SIP messages ..... | 49 | +| 7.2.3 | Sending SIP INVITE request ..... | 49 | +| 7.2.4 | Updating Precondition Information..... | 50 | +| 7.2.5 | SDP Codec Negotiation..... | 50 | +| 7.2.6 | MGW Selection ..... | 50 | +| 7.2.7 | Autonomous Release..... | 50 | +| 7.2.8 | Further setting of SIP header values..... | 50 | +| 7.3 | Signalling Interworking of a Call from SIP-I based circuit-switched core network towards the IP Multimedia Subsystem..... | 52 | +| 7.3.1 | General ..... | 52 | +| 7.3.2 | Exceptions from forwarding received SIP messages ..... | 52 | +| 7.3.3 | Sending SIP INVITE request ..... | 53 | +| 7.3.4 | Updating Precondition Information..... | 53 | +| 7.3.5 | Receipt of SIP redirect (3xx) response ..... | 54 | +| 7.3.6 | SDP Codec Negotiation..... | 54 | +| 7.3.7 | MGW Selection ..... | 54 | +| 7.3.8 | Autonomous Release..... | 55 | +| 7.3.9 | Handling of forked SIP Responses..... | 55 | +| 7.3.9.1 | SIP Dialogues ..... | 55 | +| 7.3.9.2 | Reception of non-100 provisional Responses to initial INVITE..... | 55 | +| 7.3.9.3 | Reception of final Responses to initial INVITE..... | 55 | +| 7.3.10 | Further setting of SIP header values..... | 56 | +| 7.4 | DMTF Signalling Interworking applicable for all Calls between an IP Multimedia CN Subsystem and a SIP-I based circuit-switched core network..... | 57 | +| 7.5 | User Plane Interworking..... | 57 | +| 7.5.1 | General ..... | 57 | +| 7.5.2 | DTMF Interworking ..... | 58 | +| 7.6 | Example Call flows ..... | 58 | +| 7.6.1 | General ..... | 58 | +| 7.6.2 | Incoming Call flows ..... | 58 | +| 7.6.2.1 | Successful Call Establishment and Call Release ..... | 58 | +| 7.6.2.2 | Autonomous Release at MGCF ..... | 60 | +| 7.6.3 | Outgoing Call flows ..... | 61 | +| 7.6.3.1 | Outgoing Call, Sending of INVITE is deferred ..... | 61 | +| 7.6.3.2 | Outgoing Call, Sending of INVITE is not deferred..... | 62 | +| 7.6.3.3 | Interworking with forked SIP INVITE Requests ..... | 64 | +| 7.7 | CS CN Supplementary Services and IMS Supplementary Services ..... | 67 | +| 7.7.0 | General ..... | 67 | +| 7.7.1 | Number Identification Services ..... | 67 | +| 7.7.1.1 | CS CN Supplementary Service - Calling Line Identification Presentation/Restriction (CLIP/CLIR)..... | 67 | +| 7.7.1.2 | CS CN Supplementary Service - Connected Line Identification Presentation /Restriction (COLP/COLR)..... | 67 | +| 7.7.1.3 | IMS Supplementary Service - Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR)..... | 67 | +| 7.7.1.4 | IMS Supplementary Service - Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) ..... | 67 | +| 7.7.1.5 | CS CN Supplementary Service - Direct Dialling In ..... | 67 | +| 7.7.1.6 | CS CN Supplementary Service - Malicious Call Identification ..... | 68 | +| 7.7.1.7 | IMS Supplementary Service - Malicious Communication Identification (MCID) ..... | 68 | +| 7.7.1.8 | CS CN Supplementary Service - Subaddressing ..... | 68 | + +| | | | +|----------|-----------------------------------------------------------------------------------------------------------------------------------------------|----| +| 7.7.2 | Diversion Services..... | 68 | +| 7.7.2.1 | CS CN Supplementary Service - Call Forwarding Services (CFU, CFB, CFNRy, CFNRc)..... | 68 | +| 7.7.2.2 | CS CN Supplementary Service - Call Deflection (CD)..... | 68 | +| 7.7.2.3 | IMS Supplementary Service - Communication Diversion (CDIV)..... | 68 | +| 7.7.3 | Waiting Services..... | 68 | +| 7.7.3.1 | CS CN Supplementary Service - Call Waiting..... | 68 | +| 7.7.3.2 | IMS Supplementary Service - Communication Waiting (CW)..... | 68 | +| 7.7.4 | Hold Services..... | 68 | +| 7.7.4.1 | CS CN Supplementary Service - Call Hold..... | 68 | +| 7.7.4.2 | IMS Supplementary Service - Communication Hold (HOLD)..... | 69 | +| 7.7.5 | Multipart Services..... | 69 | +| 7.7.5.1 | CS CN Supplementary Services - Conference Calling (CONF) and Three-Party (3PTY)..... | 69 | +| 7.7.5.2 | IMS Supplementary Service - Conference (CONF)..... | 69 | +| 7.7.6 | Closed User Group Service..... | 69 | +| 7.7.6.1 | CS CN Supplementary Service - Closed User Group (CUG)..... | 69 | +| 7.7.6.2 | IMS Supplementary Service - Closed User Group (CUG)..... | 69 | +| 7.7.7 | Charging Services..... | 69 | +| 7.7.7.1 | CS CN Supplementary Service - Advice of Charge (AoC)..... | 69 | +| 7.7.7.2 | IMS Supplementary Service - Advice of Charge (AOC)..... | 69 | +| 7.7.7.3 | CS CN Supplementary Service - International Telecommunication Charge Card (ITCC)..... | 69 | +| 7.7.7.4 | CS CN Supplementary Service - Reverse Charging (REV)..... | 69 | +| 7.7.8 | Barring Services..... | 70 | +| 7.7.8.1 | CS CN Supplementary Service - Barring of Outgoing Calls..... | 70 | +| 7.7.8.2 | CS CN Supplementary Service - Barring of Incoming Calls..... | 70 | +| 7.7.8.3 | CS CN Supplementary Service - Anonymous Call Rejection (ACR)..... | 70 | +| 7.7.8.4 | IMS Supplementary Service - Communication Barring (CB)..... | 70 | +| 7.7.8.5 | IMS Supplementary Service - Anonymous Communication Rejection (ACR)..... | 70 | +| 7.7.9 | Transfer Services..... | 70 | +| 7.7.9.1 | CS CN Supplementary Service - Explicit Call Transfer (ECT)..... | 70 | +| 7.7.9.2 | IMS Supplementary Service - Explicit Communication Transfer (ECT)..... | 70 | +| 7.7.10 | Call Completion Services..... | 71 | +| 7.7.10.1 | CS CN Supplementary Service - Completion of Calls to Busy Subscriber (CCBS)..... | 71 | +| 7.7.10.2 | CS CN Supplementary Service - Completion of Calls on No Reply (CCNR)..... | 71 | +| 7.7.10.3 | IMS Supplementary Service - Completion of Communications to Busy Subscriber (CCBS) and
Completion of Communication on No Reply (CCNR)..... | 71 | +| 7.7.11 | Miscellaneous Services..... | 71 | +| 7.7.11.1 | CS CN Supplementary Service - Multi-Level Precedence and Pre-emption (MLPP)..... | 71 | +| 7.7.11.2 | CS CN Supplementary Service - Multiple Subscriber Profile (MSP)..... | 71 | +| 7.7.11.3 | CS CN Supplementary Service - Multicall..... | 71 | +| 7.7.11.4 | CS CN Supplementary Service - Calling Name Presentation..... | 71 | +| 7.7.11.5 | CS CN Supplementary Service - User-to-User Signalling (UUS)..... | 71 | +| 7.7.11.6 | IMS Supplementary Service - Message Waiting Indication (MWI)..... | 71 | +| 7.7.11.7 | CS CN Supplementary Service - Global Virtual Network Service (GVNS)..... | 71 | +| 7.7.11.8 | CS CN Supplementary Service - Terminal Portability (TP)..... | 72 | +| 7.7.12 | Customized Alerting Tones Services..... | 72 | +| 7.7.12.1 | CS CN Supplementary Service - Customized Alerting Tones (CAT)..... | 72 | +| 7.7.12.2 | IMS Supplementary Service - Customized Alerting Tones (CAT) for early session model..... | 72 | +| 7.7.12.3 | IMS Supplementary Service - Customized Alerting Tones (CAT) for forking model..... | 72 | +| 7.7.12.4 | IMS Supplementary Service - Customized Alerting Tones (CAT) for gateway model..... | 72 | +| 7.8 | MGCF - IM-MGW Interaction..... | 72 | +| 7.8.1 | General..... | 72 | +| 7.8.2 | Call related Procedures for Terminations towards the IM CN Subsystem..... | 72 | +| 7.8.3 | Call related Procedures for Terminations towards SIP-I based Circuit-switched Core Network..... | 72 | +| 7.8.4 | Non-call related procedures..... | 73 | + +| | | | +|-----------------------------|-------------------------------------------------------------------------------|-----------| +| Annex A (normative): | Interconnecting functionalities in SIP-I based CS domain ..... | 74 | +| A.1 | General ..... | 74 | +| A.2 | Stage 2 Requirements..... | 74 | +| A.3 | Border Control architecture ..... | 75 | +| A.4 | Void..... | 75 | +| A.5 | Procedures at the CS-IBCF ..... | 75 | +| A.5.1 | General ..... | 75 | +| A.5.2 | CS-IBCF as an exit point ..... | 76 | +| A.5.2.1 | Initial requests ..... | 76 | +| A.5.2.2 | Subsequent requests..... | 76 | +| A.5.2.3 | CS-IBCF-initiated call release..... | 77 | +| A.5.2.4 | THIG functionality in the CS-IBCF ..... | 77 | +| A.5.2.4.1 | General..... | 77 | +| A.5.2.4.2 | Encryption for network topology hiding ..... | 78 | +| A.5.2.5 | ALG functionality in the CS-IBCF ..... | 78 | +| A.5.2.6 | Screening of SIP-I signalling..... | 78 | +| A.5.2.6.1 | General..... | 78 | +| A.5.2.6.2 | CS-IBCF procedures for SIP headers ..... | 79 | +| A.5.2.6.3 | CS-IBCF procedures for SIP message bodies ..... | 79 | +| A.5.2.7 | Void..... | 79 | +| A.5.3 | CS-IBCF as an entry point ..... | 79 | +| A.5.3.1 | Initial requests ..... | 79 | +| A.5.3.2 | Subsequent requests..... | 79 | +| A.5.3.3 | CS-IBCF-initiated call release..... | 80 | +| A.5.3.4 | THIG functionality in the CS-IBCF ..... | 80 | +| A.5.3.4.1 | General..... | 80 | +| A.5.3.4.2 | Decryption for network topology hiding ..... | 81 | +| A.5.3.5 | ALG functionality in the CS-IBCF ..... | 81 | +| A.5.3.6 | Screening of SIP-I signalling..... | 81 | +| A.5.3.7 | Void..... | 81 | +| A.6 | Procedures at the CS-TrGW ..... | 82 | +| A.6.1 | Transport Plane Control procedures..... | 82 | +| A.7 | CS-IBCF - CS-TrGW Interaction ..... | 82 | +| A.7.1 | General ..... | 82 | +| A.7.1.1 | Network Model..... | 82 | +| A.7.1.2 | Signalling flows ..... | 82 | +| A.7.1.2.1 | Basic Procedures..... | 82 | +| A.7.1.2.1.1 | Call Establishment..... | 82 | +| A.7.1.2.1.2 | Call Release..... | 85 | +| A.7.1.2.2 | Specific Use Cases..... | 85 | +| A.7.1.2.2.1 | CS-IBCF as Entry Point, Call Establishment with IP Version Interworking ..... | 85 | +| A.7.1.2.2.2 | Hanging Termination Detection..... | 86 | +| A.7.1.2.2.3 | Gate Management ..... | 87 | +| A.7.1.2.2.4 | QoS Packet Marking ..... | 87 | +| A.7.1.2.2.5 | IP Realms ..... | 88 | +| A.7.1.2.2.6 | Media Inactivity Detection..... | 88 | +| A.7.1.2.2.7 | RTCP Handling..... | 89 | +| A.7.1.2.2.8 | Bandwidth Policing ..... | 90 | +| A.7.1.2.2.8.1 | Overview ..... | 90 | +| A.7.1.2.2.8.2 | Bandwidth policing procedures..... | 90 | +| A.7.1.2.2.9 | Through-Connection ..... | 91 | +| A.7.1.2.2.10 | Emergency Call..... | 91 | +| A.7.1.2.2.11 | Interactive Connectivity Establishment ..... | 91 | +| A.7.1.2.2.12 | SDP Capability Negotiation (SDPCapNeg)..... | 91 | +| A.7.2 | Ix Signalling Procedures ..... | 92 | +| A.7.2.1 | Introduction ..... | 92 | +| A.7.2.2 | Call Related Procedures ..... | 92 | + +| | | | +|-------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| A.7.2.2.1 | Reserve TrGW Connection Point ..... | 92 | +| A.7.2.2.2 | Configure TrGW Connection Point ..... | 95 | +| A.7.2.2.3 | Reserve and Configure TrGW Connection Point ..... | 98 | +| A.7.2.2.4 | Release TrGW Termination ..... | 101 | +| A.7.2.2.5 | IP Bearer Released ..... | 102 | +| A.7.2.2.6 | Media Inactivity Detection ..... | 102 | +| A.7.2.2.7 | Termination heartbeat indication ..... | 103 | +| A.7.2.2.8 | Change Through-Connection ..... | 103 | +| A.7.2.3 | Non-Call Related Procedures ..... | 104 | +| A.7.2.3.1 | Introduction ..... | 104 | +| A.7.2.3.2 | Realm Availability Change - Activate ..... | 105 | +| A.7.2.3.3 | Realm Availability Change - Indication ..... | 106 | +| A.8 | (G)MSC - CS-MGW Interaction ..... | 106 | +| A.8.1 | General ..... | 106 | +| A.8.1.1 | Network Model ..... | 106 | +| A.8.1.2 | Signalling flows ..... | 106 | +| Annex B (normative): | Additional Interworking Procedures between a SIP-I based circuit-switched Core Network and the IP Multimedia (IM) Core Network (CN) Subsystem to Support Special Services ..... | 108 | +| B.1 | General ..... | 108 | +| B.2 | Global Text Telephony ..... | 108 | +| Annex C (informative): | Change history ..... | 109 | + +--- + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater indicates TSG approved document under change control. +- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. +- z the third digit is incremented when editorial only changes have been incorporated in the document. + +--- + +# 1 Scope + +The present document specifies the interworking between SIP-I based circuit-switched core network, as specified in TS 23.231 [3] and TS 29.231 [4], with out-of-band transcoder control related procedures in TS 23.153 [5], and: + +- an external SIP-I based signalling network compliant to ITU-T Recommendation Q.1912.5 [6], +- an ISUP (ITU-T Recommendations Q.761 to Q.764 [7]) based network such as an ISUP based 3GPP CS Domain or a PSTN, +- a BICC (ITU-T Recommendations Q.1902.1 to Q.1902.6 [8]) based network such as an BICC based 3GPP CS Domain as specified in TS 23.205 [9] and TS 29.205 [10], +- an IP Multimedia Subsystem, as specified in TS 23.228 [11] and TS 24.229 [12]. + +--- + +# 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.002: "Network architecture". +- [3] 3GPP TS 23.231: " SIP-I based circuit-switched core network; Stage 2". +- [4] 3GPP TS 29.231: "Application of SIP-I Protocols to Circuit Switched (CS) core network architecture; Stage 3". +- [5] 3GPP TS 23.153: "Out of Band Transcoder Control; Stage 2". +- [6] ITU-T Recommendation Q.1912.5 (03/04): "Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control Protocol or ISDN User Part". +- [7] ITU-T Recommendations Q.761 to Q.764 (12/99): "Specifications of Signalling System No.7 ISDN User Part (ISUP)". +- [8] ITU-T Recommendations Q.1902.1 to Q.1902.6 (07/01): "Bearer Independent Call Control". +- [9] 3GPP TS 23.205: "Bearer-independent circuit-switched core network; Stage 2". +- [10] 3GPP TS 29.205: "Application of Q.1900 series to Bearer Independent CS Network architecture; Stage 3". +- [11] 3GPP TS 23.228: "IP Multimedia subsystem (IMS)". +- [12] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP". +- [13] 3GPP TS 29.163: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks". +- [14] IETF RFC 791: "Internet Protocol". +- [15] IETF RFC 768: "User Datagram Protocol". +- [16] IETF RFC 793: "Transmission Control Protocol". + +- [17] IETF RFC 2460: "Internet Protocol, Version 6 (IPv6) Specification". +- [18] IETF RFC 4960: "Stream Control Transmission Protocol". +- [19] IETF RFC 3204: "MIME media types for ISUP and QSIG Objects". +- [20] IETF RFC 3261: "SIP: Session Initiation Protocol". +- [21] IETF RFC 3262: "Reliability of Provisional Responses in the Session Initiation Protocol (SIP)". +- [22] IETF RFC 3264: "An Offer/Answer Model with the Session Description Protocol (SDP)". +- [23] IETF RFC 3312: "Integration of Resource Management and Session Initiation Protocol (SIP)". +- [24] 3GPP TS 23.014: "Support of Dual Tone Multi-Frequency (DTMF) signalling". +- [25] 3GPP TS 24.629: "Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem". +- [26] 3GPP TS 24.610: "Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem". +- [27] ITU-T Recommendation Q.765 (2000): "Signalling System No. 7 - Application transport mechanism". +- [28] ITU-T Recommendation Q.765.5 (2000): "Signalling system No. 7 - Application transport mechanism: Bearer Independent Call Control (BICC)". +- [29] 3GPP TS 29.238: "Interconnection Border Control Functions - Transition Gateway; H.248 Profile; Stage 3". +- [30] IETF RFC 3263: "Session Initiation Protocol (SIP): Locating SIP Servers". +- [31] IETF RFC 4028: "Session Timers in the Session Initiation Protocol (SIP)". +- [32] IETF RFC 3325: "Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks". +- [33] ITU-T Recommendation H.248.1 (2002): "Gateway control protocol: Version 3". +- [34] Void. +- [35] Void. +- [36] IETF RFC 5079: "Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)". +- [37] 3GPP TS 29.162: "Interworking between the IM CN subsystem and IP networks". +- [38] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications". +- [39] IETF RFC 3556: "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth". +- [40] IETF RFC 3605: "Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)". +- [41] IETF RFC 2474: "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers". +- [42] IETF RFC 2216 (1997): "Network Element Service Template". +- [43] 3GPP TS 29.414: "Core network Nb data transport and transport signalling". +- [44] 3GPP TS 32.407: "Telecommunication Management; Performance Management (PM) Performance measurements Core Network (CN) Circuit Switched (CS) domain". +- [45] 3GPP TS 23.226: "Global Text Telephony (GTT); stage 2". + +- [46] ITU-T Recommendation T.140 (02/98): "Text conversation presentation protocol". +- [47] IETF RFC 4103: "RTP Payload for Text Conversation". +- [48] ITU-T Recommendation V.18 (11/00): "Operational procedures for modems in the text telephone mode". +- [49] 3GPP TS 26.226: "Cellular text telephone modem; General description". +- [50] Void. +- [51] Void. +- [52] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction". +- [53] ITU-T Recommendation H.248.1 (05/2002): "Gateway control protocol: Version 2" including the Corrigendum1 for Version 2 (03/04). +- [54] 3GPP TS 29.332: "Media Gateway Control Function (MGCF) - IM-Media Gateway (IM-MGW) interface, Stage 3". +- [55] 3GPP TS 29.232: "Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3". +- [56] IETF RFC 5245: "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols". +- [57] IETF RFC 5939: "Session Description Protocol (SDP) Capability Negotiation". + +--- + +## 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: + +**ICE lite:** The lite implementation of the Interactive Connectivity Establishment (ICE) specified in IETF RFC 5245 [56]. + +**Full ICE:** The full implementation of the Interactive Connectivity Establishment (ICE) specified in IETF RFC 5245 [56]. + +**Interworking Unit (IWU):** Logical entity that interworks SIP-I signalling in the 3GPP CS Domain with any of the following signalling: (a) SIP-I signalling of an external SIP-I network, (b) ISUP signalling of a PSTN, and (c) BICC or ISUP signalling of a 3GPP CS Domain. + +**User Plane Interworking Unit (UP-IWU):** Logical entity that performs user plane interworking between the SIP-I based CS Domain and an external SIP-I network, or external ISUP network, or BICC/ISUP based 3GPP CS network. + +### 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]. + +| | | +|-------|-----------------------------------| +| ALG | Application Level Gateway | +| ANM | ANswer Message | +| APM | Application Transport Mechanism | +| B2BUA | (SIP) Back-to-Back User Agent | +| BGCF | Breakout Gateway Control Function | +| BICC | Bearer Independent Call Control | +| CON | Connect message | +| COT | Continuity message | +| CPG | Call ProGress message | + +| | | +|-----------|----------------------------------------------------------------------------------| +| CS-IBCF | CS (domain) IBCF | +| CS-TrGW | CS (domain) TrGW | +| IBCF | Interconnection Border Control Function | +| ICE | Interactive Connectivity Establishment | +| ITU-T | International Telecommunication Union - Telecommunication Standardization Sector | +| IM-MGW | IP Multimedia Media Gateway Function | +| IW-MSC | Interworking MSC | +| MIME | Multi-purpose Internet Mail Extensions | +| MRFP | Multimedia Resource Function Processor | +| NA(P)T | Network Address Translation / Network Address and Port Translation | +| NNI | Network to Network Interface | +| O-MSC | Originating MSC | +| OoB | Out of Band | +| OoBTC | Out of Band Transcoder Control | +| RES | RESume | +| RLC | Release Complete | +| SCTP | Stream Control Transmission Protocol | +| SDPCapNeg | SDP Capability Negotiation | +| SIP-I | SIP with encapsulated ISUP | +| STUN | Session Traversal Utilities for NAT | +| SUS | SUSpend | +| TDM | Time-Division Multiplexing | +| THIG | Topology Hiding Internetwork Gateway | +| TMR | Transmission Medium Requirement | +| TrGW | Transition Gateway | +| UA | (SIP) User Agent | +| UP-IWU | User Plane Interworking Unit | +| USI | User Service Information | + +## 4 Interworking between a SIP-I based circuit-switched core network and an external SIP-I based network + +### 4.1 Reference Model + +Figure 4.1.1 shows the interworking reference model for the interworking between a SIP-I based circuit-switched core network and an external SIP-I based network: + + + +The diagram illustrates the interworking reference model between an External SIP-I Network and a 3GPP CS Domain. The External SIP-I Network is represented by a grey oval on the left. It connects to the 3GPP CS Domain via two main paths: a control plane path and a user plane path. The control plane path goes from the External SIP-I Network through a GMSC Server, MSC Server (containing an IWU) to an MSC Server. The user plane path goes from the External SIP-I Network through an MGW (containing a UP-IWU) to another MGW. The 3GPP CS Domain is represented by a dashed box on the right. The diagram shows the following components and interfaces: + +- External SIP-I Network:** Grey oval on the left. +- Control Plane:** Dashed lines representing signaling. The path from the External SIP-I Network to the GMSC Server, MSC Server is labeled "SIP-I over TCP or UDP or SCTP". The path between the GMSC Server, MSC Server and the MSC Server is labeled "SIP-I over SCTP" and "Nc". +- User Plane:** Solid lines representing media. The path from the External SIP-I Network to the MGW is labeled "Media/ RTP/ UDP/ IP". The path between the MGW and the MGW is labeled "Media/ RTP/ UDP/ IP" and "Nb". +- Internal Interfaces:** The path between the GMSC Server, MSC Server and the MGW is labeled "Mc". The path between the MGW and the MGW is labeled "Mc". +- Scope:** Indicated by a hatched box. The IWU in the GMSC Server, MSC Server and the UP-IWU in the MGW are highlighted with hatched boxes. +- Legend:** + - Solid line: User Plane + - Dashed line: Control Plane + - Hatched box: Scope + +Figure 4.1.1: interworking reference model diagram + +**Figure 4.1.1: interworking reference model** + +The IWU provides the control plane interworking between the external network and the SIP-I based circuit-switched core network. The IWU is a logical function within the GMSC Server (for incoming calls) and the MSC Server (for outgoing calls) that may reside with other 3GPP logical functions. + +The user plane interworking is provided by the UP-IWU. The UP-IWU is a logical function within the MGW. + +**NOTE:** In call scenarios without the need for the (G)MSC server to manipulate the bearer, the (G)MSC server may perform call control signalling without any associated MGW by not inserting a MGW in the bearer path during the call establishment. Call scenarios where the (G)MSC server needs to manipulate the bearer, e.g. scenarios with insertion of tones or announcements, lawful interception, CAMEL services do not allow this optimisation. + +**Nb reference point:** The Nb reference point is defined in accordance with TS 29.414 [43]. + +**Nc reference point:** The Nc reference point is defined in accordance with TS 29.231 [4]. + +## 4.2 Signalling Interworking of a Call from the external SIP-I based network towards the SIP-I based circuit-switched core network + +### 4.2.1 Interworking of SIP-I messages received from external SIP-I network + +#### 4.2.1.1 General + +The IWU shall decapsulate the ISUP message from the received SIP message according to the rules for Profile C in ITU-T Recommendation Q.1912.5 [6]. + +The resulting ISUP message shall be encapsulated into the SIP message. The selected SIP Header fields relating to the handling of the ISUP body shall be set as specified in clause 5.4.1.2 of ITU-T Recommendation Q.1912.5 [6]. The IWU sends the constructed SIP message to the succeeding 3GPP node. + +#### 4.2.1.2 Call Release from external SIP-I network when encapsulated REL is missing + +If the IWU receives a SIP BYE request without an encapsulated ISUP message then the IWU may construct an ISUP REL message according to the rules specified in ITU-T Recommendation Q.1912.5 [6] and encapsulate it into a SIP message, which is sent to the succeeding 3GPP node. + +NOTE: A SIP BYE request without an encapsulated ISUP message can be received from a CS-IBCF or from a node of an interconnect network when they initiate autonomous call release. It is expected that a generated ISUP REL won't add any additional information which is not available in the received SIP BYE request. + +The IWU shall send a 200 OK final response to the BYE request without an encapsulated RLC message towards the external SIP-I network. + +### 4.2.2 Special Procedures for the reception of initial SIP INVITE requests + +#### 4.2.2.1 Receipt of SIP INVITE request + +If the initial SIP-I INVITE request does not provide a complete number, then the IWU shall collect all digits required to identify the called subscriber in subsequent SIP INVITE requests as specified for Profile C in ITU-T Recommendation Q.1912.5 [6]. The IWU shall not propagate overlap signalling as described for Profile C in ITU-T Recommendation Q.1912.5 [6]. + +The IWU shall trigger GMSC functions after having constructed the ISUP message, as described in 4.2.1 above. The GMSC interrogates the HLR to get a roaming number (MSRN). The Called Party Number in the ISUP IAM message is changed by the GMSC function to the MSRN. The IWU shall include the MSRN into the Request-URI as the new target. + +#### 4.2.2.2 Receipt of SIP INVITE requests with SDP + +Based on configuration the IWU may choose to transcode media. But the IWU shall always provide the TMR/USI/HLC parameters as received on the incoming side. + +#### 4.2.2.3 Receipt of SIP INVITE request without SDP + +An IWU may reject receipt of SIP INVITE requests without SDP offer. Otherwise the rules of clause 4.2.2.1 apply with the following deviations: + +The IWU shall construct an SDP offer with contents according to local policy, e.g. SDP for a G.711 speech call. The IWU may use the TMR and USI parameters of the encapsulated IAM to determine the desired service and construct the SDP offer accordingly. The IWU may then send to the succeeding 3GPP node the SIP INVITE request with the constructed SDP offer and encapsulated IAM. + +If reliable provisional responses (see IETF RFC 3262 [21]) are supported in the external SIP-I network, the IWU may immediately send the SDP offer within a 183 Session Progress message to the preceding node. When the IWU receives the SDP answer then the IWU should send to the succeeding 3GPP node the SIP INVITE request with an encapsulated IAM message. Otherwise, the IWU shall behave in accordance with the paragraph above. + +#### 4.2.2.4 MGW Selection + +The IWU may apply the optional "optimised MGW selection", "deferred MGW selection" or "MGW bypass" procedures towards the succeeding SIP-I based circuit switched core network as described in clause 4.4 of TS 23.231 [3]. + +If MGW bypass is implemented and the IWU receives a MGW identifier: + +- in a SDP offer from external SIP-I network the IWU shall remove the MGW identifier from the SDP offer before propagating the SDP offer to the succeeding 3GPP node; + +- in a SDP answer from the succeeding 3GPP node the IWU shall remove the MGW identifier from the SDP answer before propagating back the SDP answer to the external network. + +NOTE: If MGW bypass is implemented and the external network does not include a specified connection address (0.0.0.0 for IPv4) then this will be interpreted as supporting deferred MGW selection by the succeeding node. The succeeding node will select a MGW accordingly and may return the MGW Identifier to the IWU). + +Otherwise the IWU shall seize a MGW and shall include the MGW connection address into the SDP offer of the initial SIP INVITE request it will send to the succeeding 3GPP node. + +#### 4.2.3 Interworking of SIP-I messages received from succeeding 3GPP node + +Whenever the IWU receives from the succeeding 3GPP node a SIP message with an encapsulated CON, ACM, CPG, ANM, SUS, RES message then the IWU sends the SIP message in accordance with rules in accordance with ITU-T Recommendation Q.1912.5 [6] to the external SIP-I network and the encapsulated ISUP message shall not be modified. + +#### 4.2.4 Special Procedures for Profile Interworking + +##### 4.2.4.1 Support of 100Rel + +The IWU receiving a SIP INVITE with or without tag "100Rel" in the SUPPORTED or the REQUIRED header from the external SIP-I network shall advertise its preference of provisional reliable responses to the succeeding 3GPP node via a SUPPORTED header in the initial SIP INVITE request. + +As an option the IWU may consider a received SIP INVITE request without "100Rel" as erroneous and reject the INVITE request with a 421 "Extension Required" response. + +NOTE: The option to forward a SIP INVITE request to the succeeding 3GPP node with or without tag "100Rel", if the external network does not support reliable provisional responses, is not specified in the present specification. + +##### 4.2.4.2 Support for UPDATE method + +The IWU receiving a SIP INVITE with or without the UPDATE method included in the ALLOW header shall advertise its support for the UPDATE method to the succeeding 3GPP node by listing the UPDATE method in the ALLOW header field. + +As an option the IWU may consider a received initial SIP INVITE request without listing UPDATE in the ALLOW header field as erroneous and reject the INVITE request with a 403 "Forbidden" response. + +NOTE: The option to forward a SIP INVITE request to the succeeding 3GPP node without indicating support of the UPDATE method, if the external network does not support the UPDATE method, is not specified in the present specification. + +##### 4.2.4.3 Support for Preconditions + +When the incoming SIP INVITE request indicates that remote preconditions are met and local preconditions are met then the IWU may either not include the tag "precondition" and exclude appropriate SDP lines, or include the tag "preconditions" in the SUPPORTED header and provide an SDP offer indicating that preconditions are met. + +When the incoming SIP INVITE request does not contain a "precondition" tag the IWU shall assume the preconditions have been met within the external SIP-I network. If local preconditions are met then the IWU may either not include the tag "precondition" and exclude appropriate SDP lines, or include the tag "precondition" in the SUPPORTED header and provide an SDP offer indicating that preconditions are met. + +When the incoming SIP INVITE request indicates that remote preconditions are not met or when local preconditions are not met then the IWU shall include the tag "precondition" in the REQUIRE header or SUPPORTED header in the SIP INVITE request and shall encode preconditions in the SDP offer that the related local preconditions for QoS are not met, using the segmented status type, as defined in IETF RFC 3312 [23], as well as the strength-tag value "mandatory" for the local segment and the strength-tag value "optional" for the remote segment when sending the message to the succeeding 3GPP node. Or the IWU may defer forwarding the SIP INVITE request until remote local preconditions are met. + +When the incoming SIP INVITE request indicates that preconditions have not been met and the IWU will not include a MGW the SDP with preconditions information shall be transited unchanged and the "precondition" tag shall be transited in the same header as received. + +NOTE 1: The use of the SUPPORTED header is a deviation from IETF RFC 3312 [23] when the strength-tag contains a "mandatory" value. + +NOTE 2: The support of preconditions is mandated at the Nc interface. Therefore a response without "precondition" can be considered as erroneous if preconditions were not met. + +NOTE 3: The setting of the "Continuity Check Indicator" in the "Nature of Connection Indicators" parameter within the encapsulated IAM by the IWU is of no significance. The value is ignored by the succeeding 3GPP node. + +## 4.2.5 Support for Codec Negotiation + +If the IWU uses the MGW bypass option as defined in TS 23.231 [3], then the IWU is not involved in the codec negotiation procedure and transits SDP offers and answers unchanged. Otherwise, the remaining text of this clause applies: + +If the IWU receives from the external SIP-I based network a SIP request with an SDP offer containing a codec list with or without the 3GPP\_OoBTC\_Indicator, the IWU shall follow the procedures defined for a 3GPP Intermediate Node in clause 9 of TS 23.153 [5]. + +If the IWU receives from the external SIP-I based network an INVITE or re-INVITE request without any codec information, the IWU shall send an SDP offer to the succeeding 3GPP SIP-I node, where it either shall follow the procedures defined for a 3GPP node originating SDP offer in clause 9 of TS 23.153 [5], or shall create an SDP offer with the default PCM codec. The IWU shall send the selected codec within an SDP offer towards the preceding external node. + +NOTE: Which codecs are negotiable with the external SIP-I network may depend on operator choices and preferences (local policy). + +## 4.2.6 Special Procedures for the reception of SIP Re-INVITE requests + +### 4.2.6.1 Receipt of SIP Re-INVITE request without SDP + +Upon receipt of a SIP Re-INVITE request without SDP, the IWU shall: + +- construct an SDP offer with contents reflecting the SDP already negotiated with the external SIP-I network for the call, including codec information as specified in clause 4.2.5, and send the SDP offer within a 200 OK (INVITE) message to the external SIP-I network; or +- reject the SIP Re-INVITE request. + +## 4.3 Signalling Interworking of a Call from SIP-I based circuit-switched core network towards the external SIP-I based network + +### 4.3.1 Interworking of SIP-I messages received from preceding 3GPP node + +#### 4.3.1.1 General + +An IWU receiving SIP messages with encapsulated ISUP information shall apply any interworking procedures detailed for Profile C in ITU-T Recommendation Q.1912.5 [6] affecting parameters within the ISUP, and then proceed to encapsulate any ISUP information received (with the exception of the excluded messages detailed in 5.4.3 of ITU-T Recommendation Q.1912.5 [6]) in a SIP message in a MIME body according to IETF RFC 3204 [19]. The selected SIP Header fields relating to the handling of the ISUP body shall be set as specified in ITU-T Recommendation Q.1912.5 [6]. + +#### 4.3.1.2 Call Release from external SIP-I network when encapsulated REL is missing + +If the IWU receives a SIP BYE request or 4XX, 5XX, 6XX final response to the initial INVITE request without an encapsulated ISUP REL message then the IWU may construct the ISUP REL message according to the rules specified + +in ITU-T Recommendation Q.1912.5 [6] and encapsulate it into the SIP message, which is sent to the preceding 3GPP node. + +NOTE: A SIP BYE request without an encapsulated ISUP message can be received from a CS-IBCF or from a node of an interconnect network when they initiate autonomous call release. It is expected that a generated ISUP REL message won't add any additional information which is not available in the received SIP BYE request. + +The IWU shall send a 200 OK final response to the BYE request without an encapsulated ISUP RLC message towards the external SIP-I network. + +## 4.3.2 Special Procedures for the reception of SIP INVITE requests + +The IWU shall decapsulate the ISUP message. The IWU forwards the ISUP information to the "IW-MSC" functions, which may result in a modified ISUP message. + +Based on configuration the IWU may choose to transcode media. If the IWU transcodes, it should set the TMR/USI/HLC parameters according to the codec applied in the SIP-I network. Otherwise, it should provide the TMR/USI/HLC parameters as received in the encapsulated IAM. + +The IWU shall proceed to encapsulate the ISUP message into the SIP-INVITE request. The request URI shall be aligned with the called party number. + +## 4.3.3 Special Procedures for Profile Interworking + +### 4.3.3.1 Support of 100Rel + +An IWU shall consider an initial SIP INVITE request received from the preceding 3GPP node without the tag "100Rel" in the SUPPORTED header or REQUIRED header as erroneous and shall reject the call accordingly. + +An IWU sending a SIP INVITE request towards the external SIP-I network shall advertise its preference of provisional reliable responses via a SUPPORTED header containing the tag "100Rel". + +If an IWU receives a provisional 101-199 response from the external SIP-I network with a REQUIRE header present with tag "100rel" then it shall include the tag "100Rel" into the REQUIRE header when the IWU propagates the response to the preceding 3GPP node. + +If an IWU receives from the external SIP-I network a provisional 101-199 response without tag "100rel" in the REQUIRE header then the IWU shall: + +- either includes the tag "100Rel" into the REQUIRE header when it forwards the response to the preceding 3GPP node, +- or consider the response as erroneous and reject the call accordingly. + +NOTE: The option to forward the response to the preceding 3GPP node without tag "100Rel", if the external network does not support reliable provisional responses, is not specified in the present specification. + +### 4.3.3.2 Support for UPDATE method + +An IWU sending a SIP INVITE towards the external SIP-I network shall advertise its support of the UPDATE method via the ALLOW header listing the UPDATE method. + +The IWU receiving a response to a SIP INVITE request is allowed to generate the UPDATE method towards the external network if an ALLOW header is present listing the UPDATE method. Otherwise, the IWU is not allowed to generate UPDATE requests towards the external SIP-I network and one of the following options applies: + +- The IWU shall return the response to the preceding 3GPP node containing an ALLOW header listing the UPDATE method. +- The IWU shall consider the response received from the external network as erroneous and reject the call accordingly. + +NOTE: The option to forward the response to the preceding 3GPP node without UPDATE in the ALLOW header field, if the external network does not support the UPDATE method, is not specified in the present specification. + +#### 4.3.3.3 Support for Preconditions + +When the incoming SIP INVITE request indicates that preconditions have not been met or when local preconditions are not met, the IWU shall use one of the following options: + +- a) The IWU shall send a SIP INVITE request to a succeeding external SIP-I network and include the tag "precondition" in the SUPPORTED header. The IWU shall encode preconditions in the SDP offer indicating that the related local preconditions for QoS are not met, using the segmented status type, as defined in IETF RFC 3312 [23], as well as the strength-tag value "mandatory" for the local segment and the strength-tag value "optional" for the remote segment. The "precondition" tag shall be included in the SUPPORTED header. The IWU shall encapsulate the IAM message into the SIP INVITE request and should insert "continuity check not required" as the value of the Continuity check indicator within the Nature of Connection Indicators parameter in order to avoid that an external node, which does not support preconditions, is waiting for a COT message when the IWU is not able to send the COT message. + +NOTE 1: Such an external node is not compliant to ITU-T Recommendation Q.1912.5 [6]. + +NOTE 2: The use of the SUPPORTED header is a deviation from IETF RFC 3312 [23] when a "mandatory" strength-tag is used. + +The subsequent action depends on whether the response indicates support of preconditions: + +- i) If the IWU receives from the external SIP-I network a provisional 101-199 response with a REQUIRE header or SUPPORTED header containing tag "precondition", then the IWU shall progress the call and when preconditions are met it shall send an UPDATE message or PRACK message indicating that preconditions have been fulfilled. Preconditions are fulfilled when local preconditions are met and, if the incoming SIP INVITE request indicated that preconditions had not been met, the IWU has received an indication from the preceding 3GPP node that the preconditions are subsequently met. +- ii) If the IWU receives from the external SIP-I network a provisional 101-199 response without a REQUIRE header or SUPPORTED header containing tag "precondition" and if a provisional response or successful final response carrying an encapsulated ISUP message is received from external SIP-I network prior to preconditions being met, then these responses shall be queued and later be propagated to the preceding 3GPP node once preconditions are met. If responses carrying encapsulated ISUP are to be queued and the response carrying an encapsulated ISUP message is the first response carrying an SDP answer then the IWU shall generate a 183 Progress with the SDP answer and send it to the preceding node. The IWU shall not encapsulate an ISUP message into the 183 Progress. + +NOTE 3: The option to allow the SIP response to be immediately forwarded is not specified in the present will result in the O-MSC receiving encapsulated ISUP prior to preconditions being met. In addition, reception of response without indication of support for preconditions at the O-MSC is not specified in the present specification. + +If the IWU receives a failure response from the external network, then this shall immediately be forwarded to the preceding 3GPP node. + +- b) Before sending the INVITE request to the external network the IWU shall wait until local preconditions are met and, if the incoming SIP INVITE request indicated that preconditions have not been met, it has received an indication from the preceding 3GPP node that the preconditions are met. + +The initial INVITE request to the external SIP-I network may include a precondition tag in SUPPORTED header and indicate that preconditions have been met. + +- c) The IWU shall send a SIP INVITE request to a succeeding external SIP-I network and include the tag "precondition" in the REQUIRE header. The IWU shall encode preconditions in the SDP offer indicating that the related local preconditions for QoS are not met, using the segmented status type, as defined in IETF RFC 3312 [23], as well as the strength-tag value "mandatory" for the local segment and the strength-tag value "optional" for the remote segment. The IWU shall encapsulate the IAM message into the SIP INVITE request and should insert "continuity check not required" as the value of the Continuity check indicator within + +the Nature of Connection Indicators parameter in order to avoid that an external node, which does not support preconditions, is waiting for a COT message when the IWU is not able to send the COT message. + +NOTE 4: Such an external node is not compliant to ITU-T Recommendation Q.1912.5 [6]. + +The subsequent action depends on whether the response indicates support of preconditions: + +- i) If the IWU receives from the external SIP-I network a provisional 101-199 response with a REQUIRE header or SUPPORTED header containing tag "precondition", then the IWU shall continue the call per response handling procedures described in option a) above. +- ii) If the IWU receives a 420 Bad Extension final response, then the IWU shall continue per option b) above by waiting for preconditions to be met before repeating the initial INVITE request. + +When the incoming SIP INVITE request indicates that precondition are met and local preconditions are met, the IWU shall set up the session and may include a precondition tag in the SUPPORTED header and indicate that preconditions have been met. + +When the incoming SIP INVITE request indicates that preconditions have not been met and the IWU will not include a MGW the SDP with preconditions information shall be transited unchanged and the "precondition" tag shall be transited in the same header as received. + +#### 4.3.4 Support for Codec Negotiation + +When the IWU receives an INVITE with an SDP offer containing a structured codec list, the IWU shall follow the procedures defined for a 3GPP Intermediate Node in clause 9 of TS 23.153 [5], unless the IWU uses the MGW bypass option. + +NOTE: Which codecs are negotiable with the external SIP-I network may depend on operator choices and preferences (local policy). + +#### 4.3.5 MGW Selection + +The IWU shall not perform "optimised MGW selection", or "deferred MGW selection" towards an external SIP-I network. The IWU shall select a MGW and include the MGW connection address in the SDP offer of the initial SIP INVITE request it sends to the external SIP-I network. The "MGW bypass" option may be deployed but in the case that the preceding 3GPP node signals the MGW identifier this identifier shall not be signalled to the external SIP-I network. + +### 4.4 DMTF Signalling Interworking applicable for all Calls between an external SIP-I based network and a SIP-I based circuit-switched core network + +#### 4.4.1 General + +DTMF signalling via the RTP Telephony Event (RTP Telephony Event) is mandated to be supported over the Nb interface for SIP-I based Circuit Switched Core Network on Nc Interface, see TS 23.231 [3]. + +NOTE 1: According to TS 23.231 [3] it is an option to choose either the RTP Telephony Event or inband DTMF transport within the PCM codec when only the default PCM codec is selected, however once RTP Telephony Event is chosen (indicated in the SDP answer) it must be used for any selected codec. + +If MGW bypass is supported within the CS CN (see TS 23.231 [3], clause 4.4.5), a terminating MSC or a 3GPP SIP-I intermediate node controlling a MGW that interfaces directly to the external network shall behave as an IWU, as its MGW is providing an UP-IWU function and therefore the SIP-I Server shall also comply with the procedures in this subclause. A GMSC Server or SIP-I intermediate node which is applying the MGW Bypass option shall then relay the SDP media lines for codecs and RTP Telephony Event in the SDP offers and answers transparently between the external SIP-I network and the 3GPP CS CN and is therefore not constrained by the procedures described in this subclause. + +If the SDP answer sent towards the external SIP-I network or received from the external SIP-I network includes the RTP Telephony event, then the IWU shall request its MGW to transmit and receive the DTMF to/from the external SIP-I node within the RTP Telephony Event. + +If the SDP answer sent towards or received from the SIP-I based CS CN includes the RTP Telephony event, then the IWU shall request its MGW to transmit and receive the DTMF to/from the SIP-I based CS CN within the RTP Telephony Event. + +DTMF interworking is specified for interworking towards an external SIP-I network with the assumption that the following applies: + +- External SIP-I network includes RTP Telephony event within SDP offers or SDP answers together with non-PCM speech codecs; +- External SIP-I network includes default PCM codec in SDP offers or SDP answers. + +Therefore only the case where the external SIP-I network includes default PCM codec when not including the RTP Telephony event is described. + +#### 4.4.2 DTMF support in SDP offer sent to External SIP-I network + +If an IWU receives an *initial* SDP offer from a preceding 3GPP SIP-I node with the RTP Telephony Event it shall forward the RTP Telephony Event in the offer to the succeeding (external) node. If the IWU then receives a SDP answer from the succeeding node (external network) including the RTP Telephony Event, the IWU shall include the RTP Telephony Event in the SDP answer it forwards to the SIP-I based CS CN independently of the selected codec type, i.e. any DTMF payload received would then be simply relayed through the interworking MGW, and the IWU shall also include the RTP-telephony event in possible subsequent SDP offers it sends towards the succeeding external network node. + +If an IWU receives an SDP offer from a preceding 3GPP SIP-I node without the RTP Telephony Event (only permitted if only default PCM codec offered) then it may: + +- Include additional non-PCM speech codecs and shall then include the RTP Telephony Event in the subsequent offer to the succeeding external SIP-I node; + +NOTE: If the answer from the external SIP-I node does not include the RTP Telephony Event then no interworking of DTMF Telephony Events or tones is required by the MGW. + +or: + +- send the SDP Offer to the external SIP-I node without the RTP Telephony Event (no compressed codecs included in the offer) and then no inband DTMF detection/insertion is required; or: +- Send the SDP Offer to the external SIP-I node without any additional non-PCM speech codecs and include the RTP Telephony Event. + +If the answer from the external SIP-I node includes the RTP Telephony event and the RTP Telephony event has not been offered by the preceding 3GPP SIP-I network then the IWU shall request its MGW (UP-IWU) to detect/insert inband DTMF tones to/from its preceding 3GPP SIP-I node and send/receive the DTMF to the external SIP-I node within the RTP Telephony Event, see clause 14.4.8 in TS 23.231 [3], + +If an IWU receives a SDP offer from a preceding 3GPP SIP-I node with the RTP Telephony Event and then receives a SDP answer from the external SIP-I network which includes only the PCM speech codec and excludes the RTP Telephony Event the IWU may: + +- apply "transcoding at the PLMN border" by selecting another speech codec than the default PCM codec for the interface toward the SIP-I based CS CN (if included in the offer) and then the IWU shall include the RTP Telephony Event in the answer it forwards to the SIP-I based CS CN, or: +- select default PCM codec towards the SIP-I CS CN and may include the RTP Telephony Event in the reply to the preceding (3GPP SIP-I) node and shall then request its MGW to relay inband DTMF to the RTP Telephony Event to/from the external network, see clause 14.4.8 in TS 23.231 [3], or: +- select default PCM codec towards the SIP-I CS CN and exclude the RTP Telephony Event in the reply to the preceding (3GPP SIP-I) node and then no inband DTMF detection/insertion is required. + +### 4.4.3 DTMF support in SDP offer received from External SIP-I network + +If an IWU receives an SDP offer from the external SIP-I network with the RTP Telephony Event it shall forward the RTP Telephony Event in the offer to the succeeding node. If the SDP answer from the succeeding (3GPP internal) SIP-I node includes the RTP Telephony Event the IWU shall configure its MGW to relay the RTP Telephony Events transparently as described in clause 14.4.3 of TS 23.231 [3]. + +If an IWU receives a SDP offer from the external SIP-I network without the RTP Telephony Event the IWU shall include the RTP Telephony Event in the offer to the succeeding node if any codec other than the default PCM speech codec is offered to the succeeding node. If only the default PCM speech codec is offered to the succeeding node, the IWU may include the RTP Telephony Event in the offer to the succeeding SIP-I CS CN node. + +If the IWU receives a SDP answer from the succeeding (3GPP internal) SIP-I node including the RTP Telephony Event and the RTP Telephony Event had not been received in the offer from the external network the IWU returns the default PCM codec in the SDP answer to the external SIP-I network. The IWU shall then request its MGW (UP-IWU) to detect any inband DTMF from the external SIP-I network and signal the DTMF to the succeeding 3GPP SIP-I node within the RTP Telephony Event and insert DTMF tones into the external SIP-I network if DTMF digits received via RTP Telephony Event from the succeeding 3GPP SIP-I node, see clause 14.4.8 in TS 23.231 [3]. + +If an IWU receives a SDP answer from the succeeding (3GPP internal) SIP-I node excluding the RTP Telephony Event (i.e. default PCM codec selected) but received an RTP Telephony Event in the SDP offer from the external SIP-I network it may return RTP Telephony Event in the SDP answer to the external SIP-I network. It shall then configure its MGW (UP-IWU) for transferring DTMF between inband PCM and RTP Telephony Events as described in clause 14.4.8 in TS 23.231 [3]. If the IWU chooses not to include the RTP Telephony Event in the SDP answer then default PCM codec shall be signalled in the SDP answer to the external SIP-I network. No inband DTMF detection or insertion is required; any DTMF tones received are passed transparently inband. + +If an IWU receives a SDP answer from the succeeding (3GPP internal) SIP-I node excluding the RTP Telephony Event (i.e. default PCM codec selected) and did not receive an RTP Telephony Event in the SDP offer from the external SIP-I network the IWU returns the default PCM codec as the selected codec in the SDP answer to the external network and shall not request its MGW to configure RTP Telephony Event; therefore any inband DTMF tones are passed transparently inband. + +## 4.5 User Plane Interworking + +### 4.5.1 General + +Figure 4.5.1.1 shows the user plane protocol stacks within the external SIP-I network and the 3GPP SIP-I based circuit switched core network. + + + +The diagram illustrates the user plane protocol stacks for interworking between an External SIP-I Network and a 3GPP SIP-I based circuit switched core network. On the left, an oval labeled 'External SIP-I Network' is connected to a table representing the protocol stacks. The table has two columns for different codecs and five rows for the protocol layers. + +| Codec,
e.g. G.711 | Codec,
e.g. NB-AMR | +|----------------------|-----------------------| +| RTP | RTP | +| UDP | UDP | +| IP | IP | +| L2, L1 | L2, L1 | + +The bottom row of the table (L2, L1) is connected to a horizontal line representing the network interface, which is labeled 'Nb' at the right end. + +Diagram of user plane interworking showing protocol stacks for External SIP-I Network and 3GPP SIP-I based circuit switched core network. + +**Figure 4.5.1.1: user plane interworking** + +If the same speech codec is used on both sides, no speech transcoding is required. + +## 4.5.2 DTMF Interworking + +For general information of DTMF interworking, see clause 4.4.1. + +The IWU may configure its UP-IWU with RTP Telephony Event at the 3GPP SIP-I termination and the external SIP-I termination. The UP-IWU shall then relay any DTMF received within the RTP Telephony Event Payload Type from one network interface to the other. + +The IWU may configure the UP-IWU with only one network termination with RTP Telephony Event and the other termination configured for default PCM. The UP-IWU shall then detect DTMF tones from the PCM-encoded speech path and transmit them as RTP Telephony Events toward the other network and shall detect RTP Telephony Events and insert the DTMF as Tones in the corresponding PCM-encoded path. + +If the IWU does not configure RTP Telephony Event on either network terminations then the UP-IWU simply relays the PCM-encoded speech from one network to the other (which may contain and therefore relay DTMF tones). + +If RTP Telephony Event is selected for either the external SIP-I connection or for the internal 3GPP CS CN connection, but not for both, then the MGW shall filter out (delete) the DTMF from the default PCM-coded speech path (when relaying the DTMF via the RTP Telephony Event) to prevent potential double signalling of the same digit if a later insertion back to inband DTMF tone transmission were to occur. + +The related UP-IWU control procedures and UP-IWU behaviour is described in clauses 14.4.3 and 14.4.8 of TS 23.231 [3], where the MGW shall be understood as UP-IWU. + +## 4.6 Example Call flows + +### 4.6.1 General + +In this clause call flows are shown as examples to demonstrate the signalling interworking of the IWU. Within the message sequence charts some content of the messages are shown in order to visualise some of the important interworking aspects, which were described in previous clauses of this document. It is to be noted that the intention is neither to show the complete content of the SIP messages nor to use the exact syntax of SIP and SDP messages as it is defined in the respective RFCs. It is also not the intention to show all alternative options that are possible for a certain call flow. + +### 4.6.2 Incoming Call flows + +#### 4.6.2.1 Incoming Call - no preconditions in external network + +Figure 4.6.2.1.1 shows a terminating call where the external network does not indicate the support of preconditions and where the SDP body contains a list of codecs according to IETF RFC 3264 [22]. The IWU assumes that remote preconditions are met. The incoming side RTP bearer termination is yet not successfully reserved and configured and therefore local preconditions are not met. Thus the IWU initiates precondition signalling when sending the INVITE request to the succeeding 3GPP node. The IWU and the 3GPP node perform codec negotiation according to 3GPP rules as specified in TS 23.153 [5]. The IWU answers to the external network with a single selected codec. If possible the selected codec is the same as received from the 3GPP node to avoid transcoding at the network border. + +The IWU changes the content of the Request URI (either a tel-URI or a SIP-URI with "user=phone") from the MSISDN of the called subscriber to the MSRN received from the HLR. The IWU inserts its own address into the From header of the initial SIP INVITE request being sent to the succeeding 3GPP node. + + + +``` + +sequenceDiagram + participant ExternalNetwork as from External Network + participant GMSC as GMSC Server IWU + participant HLR as HLR Interrogation fetches MSRN + participant MGW as MGW UP-IWU + participant Node as to 3GPP Node + + Note left of GMSC: NNI + Note right of GMSC: Nc + Note right of MGW: Mc + + ExternalNetwork->>GMSC: INVITE [SDP, IAM] +Request URI: MSISDN +100rel, UPDATE +IETF codec list, +IAM + GMSC-->>ExternalNetwork: TRYING + + GMSC->>HLR: HLR Interrogation fetches MSRN + HLR-->>GMSC: + + Note right of GMSC: remote preconditions are met; +local preconditions are not met + GMSC->>MGW: Seize outgoing side RTP bearer terminations + GMSC->>Node: INVITE [SDP, IAM] +Request URI: MSRN +From: SIP URI of GMSC +100rel, UPDATE, +precondition tag +3gOoBTC, supported codec list, +preconditions not met +IAM (updated) + Node-->>GMSC: 183 Progress [SDP] +100rel, UPDATE, precondition tag, +3gOoBTC, selected codec, available codecs + + Note right of GMSC: local preconditions are met + GMSC->>MGW: Seizure of incoming side RTP bearer terminations, though-connection + GMSC-->>ExternalNetwork: 183 Progress [SDP] +100rel, UPDATE +selected codec + ExternalNetwork->>GMSC: PRACK + GMSC-->>ExternalNetwork: 200 OK (PRACK) + GMSC-->>ExternalNetwork: 180 Ringing [ACM] + ExternalNetwork->>GMSC: PRACK + GMSC-->>ExternalNetwork: 200 OK (PRACK) + GMSC-->>ExternalNetwork: 200 OK (INVITE) [ANM] + ExternalNetwork->>GMSC: ACK + + Note right of MGW: preconditions met + MGW-->>Node: PRACK [SDP] +preconditions met + Node-->>MGW: 200 OK (PRACK) [SDP] + MGW-->>Node: 180 Ringing [ACM] + MGW-->>Node: PRACK + Node-->>MGW: 200 OK (PRACK) + MGW-->>Node: 200 OK (INVITE) [ANM] + MGW-->>Node: ACK + +``` + +Sequence diagram for an incoming call from an external network to a 3GPP node via a GMSC Server IWU and an MGW UP-IWU. The diagram shows the flow of SIP messages including INVITE, TRYING, 183 Progress, PRACK, 200 OK, 180 Ringing, and ACK, with internal processing steps like HLR interrogation and RTP bearer termination. + +Figure 4.6.2.1.1: Incoming Call (message sequence chart), +example without support for preconditions at the NNI + +#### 4.6.2.2 Incoming Call with preconditions not met + +In figure 4.6.2.2.1 the external network indicates that its preconditions are not met. Because support for preconditions is mandated at the interface to the succeeding 3GPP node, the IWU can immediately send the INVITE towards the destination. + +The IWU receives from the external network the information that preconditions are met either in the PRACK or UPDATE request, where the SDP parameters are set accordingly. The IWU sends the information that preconditions are met either within the PRACK or with an UPDATE request to the 3GPP node such that the called subscriber can be alerted. + + + +``` + +sequenceDiagram + participant Ext as to External Network + participant GMSC as GMSC Server IWU + participant MGW as MGW UP-IWU + participant Node as to 3GPP Node + + Note over Ext, GMSC: NNI + Note over GMSC, Node: Nc + Note over GMSC, MGW: Mc + + Ext->>GMSC: INVITE [SDP, IAM] +Request URI: MSIDN +100rel, UPDATE, precondition tag, +IETF codec list, preconditions not met + GMSC-->>Ext: TRYING + Note over GMSC: HLR Interrogation + GMSC->>MGW: Seize outgoing side RTP bearer terminations + GMSC->>Node: INVITE [SDP, IAM] +Request URI: MSRN +From: SIP URI of GMSC +100rel, UPDATE, precondition tag, +3gOoBTC, supported codec list, preconditions not met + Node-->>GMSC: 183 Progress [SDP] +100rel, UPDATE, precondition tag, +gOoBTC, selected codec, available codecs + GMSC->>MGW: Seizure of incoming side RTP bearer terminations, though-connection + GMSC-->>Ext: 183 Progress [SDP] +100rel, UPDATE, precondition tag, +selected codec + Note right of GMSC: Selected codec chosen from succeeding +3GPP node may be supported on +external network. If not then another +codec must be chosen + Ext->>GMSC: PRACK + GMSC->>Node: PRACK + Node-->>GMSC: 200 OK (PRACK) + GMSC-->>Ext: 200 OK (PRACK) + Ext->>GMSC: UPDATE [SDP] +Preconditions met + GMSC->>Node: UPDATE [SDP] +Preconditions met + Node-->>GMSC: 200 OK (UPDATE[SDP]) + GMSC-->>Ext: 200 OK (UPDATE[SDP]) + Node-->>GMSC: 180 Ringing [ACM] + GMSC-->>Ext: 180 Ringing [ACM] + Ext->>GMSC: PRACK + GMSC->>Node: PRACK + Node-->>GMSC: 200 OK (PRACK) + GMSC-->>Ext: 200 OK (PRACK) + Node-->>GMSC: 200 OK (INVITE) [ANM] + GMSC-->>Ext: 200 OK (INVITE) [ANM] + Ext->>GMSC: ACK + GMSC->>Node: ACK + +``` + +Sequence diagram for an incoming call with precondition update. Lifelines: External Network, GMSC Server IWU, MGW UP-IWU, and 3GPP Node. The process involves INVITE, TRYING, HLR Interrogation, Seize outgoing side RTP bearer terminations, INVITE to 3GPP node, 183 Progress, Seizure of incoming side RTP bearer terminations, 183 Progress to external network, PRACK, 200 OK (PRACK), UPDATE, 200 OK (UPDATE), 180 Ringing, PRACK, 200 OK (PRACK), 200 OK (INVITE), and ACK messages. + +**Figure 4.6.2.2.1: Incoming Call (message sequence chart), +example with precondition update** + +## 4.6.3 Outgoing Call flows + +### 4.6.3.1 Outgoing Call with support for preconditions + +Figure 4.6.3.1.1 shows an outgoing call where the preconditions are not met when the IWU receives the initial SIP INVITE. Support for preconditions is confirmed from the external network. Within this example the external node provides a single codec, therefore no second SDP offer/answer is needed for codec negotiation. + +When the IWU receives from the preceding 3GPP node that preconditions are met, then it informs the external node that called subscriber can be alerted with an UPDATE request, where the SDP contains the appropriate precondition offer and the selected codec. + + + +``` + +sequenceDiagram + participant 3GPP Node + participant MGW UP-IWU + participant MSC Server / IWU + participant External Network + + Note left of MGW: from 3GPP Node + Note right of External Network: to External Network + + MGW->>MSC: INVITE [SDP, IAM] +100rel, UPDATE, precondition tag +3gOoBTC, supported codec list +preconditions not met + MSC-->>MGW: 100 TRYING + Note right of MGW: Seize outgoing side RTP bearer terminations +preconditions are not met + MSC->>External: INVITE [SDP, IAM] +100rel, UPDATE, precondition tag +3gOoBTC, supported codec list (updated) +preconditions not met + External-->>MSC: 100 TRYING + Note right of MGW: Seize incoming side RTP bearer terminations + External-->>MSC: 183 Progress [SDP] +100rel, UPDATE, precondition tag +IETF codec, local preconditions met + MGW-->>External: 183 Progress [SDP] +100rel, UPDATE, preconditions +3gOoBTC, selected codec, available codecs +local preconditions met + MGW->>MSC: PRACK + External-->>MSC: PRACK + MGW-->>External: 200 OK (PRACK) + External-->>MSC: 200 OK (PRACK) + MGW->>MSC: UPDATE [SDP] +preconditions are met + External-->>MSC: UPDATE [SDP] +selected codec, preconditions are met + External-->>MSC: 200 OK (UPDATE) [SDP] +selected codec, local preconditions met + MGW-->>External: 200 OK (UPDATE) [SDP] +local preconditions met + External-->>MSC: 180 Ringing [ACM] + MGW-->>External: 180 Ringing [ACM] + MGW->>MSC: PRACK + External-->>MSC: PRACK + MGW-->>External: 200 OK (PRACK) + External-->>MSC: 200 OK (PRACK) + External-->>MSC: 200 OK (INVITE) [ANM] + MGW-->>External: 200 OK (INVITE) [ANM] + MGW->>MSC: ACK + External-->>MSC: ACK + +``` + +Sequence diagram of an outgoing call with preconditions support. Lifelines: 3GPP Node, MGW UP-IWU, MSC Server / IWU, and External Network. The process involves INVITE, 100 TRYING, preconditions check, 183 Progress, PRACK, 200 OK, UPDATE, 200 OK (UPDATE), 180 Ringing, PRACK, 200 OK (PRACK), 200 OK (INVITE), and ACK messages. + +Figure 4.6.3.1.1: Outgoing call (message sequence chart), +example with support for preconditions + +#### 4.6.3.2 Outgoing Call with support of 100rel but no support for preconditions + +Figure 4.6.3.2.1 depicts an outgoing call where the external network supports reliable provisional responses and the UPDATE method but does not support preconditions. Therefore the IWU cannot exchange SDP precondition offers/answers with the external node. + +In this example the IWU receives more than one single codec in the 183 Progress from the external node. Therefore the IWU selects one of the received codecs and makes a second SDP offer to the external node in the PRACK in order to lock the codec. + +The IWU receives a 180 Ringing provisional response from the external network before preconditions are fulfilled. The IWU forwards the 180 Ringing response after preconditions have been fulfilled. + +NOTE 1: The IWU may also have received a successful final response to the INVITE before preconditions have been met. In this case the forwarding of the 180 Ringing response and of the final successful response towards the preceding 3GPP node is delayed until preconditions are fulfilled. + +NOTE 2: As an alternative the IWU could send PRACK to the external node when PRACK is received from the preceding 3GPP node acknowledging the 180 Ringing response. Since the sending of the 180 Ringing response to the 3GPP network may be delayed, this may lead to the retransmission of 180 Ringing response sent by the external node. + + + +The sequence diagram illustrates the interaction for an outgoing call. The participants are a 3GPP Node, an MGW UP-IWU, an MSC Server / IWU, and an External Network. The MGW UP-IWU is connected to the 3GPP Node via the Nc interface and to the MSC Server / IWU via the Mc interface. The MSC Server / IWU is connected to the External Network via the NNI interface. + +The call sequence is as follows: + +- The 3GPP Node sends an **INVITE [SDP, IAM]** to the MGW UP-IWU. The message includes **100rel, UPDATE, precondition tag 3gOoBTC, supported codec list, precondition not met**. +- The MGW UP-IWU responds with **TRYING**. +- The MGW UP-IWU performs **Seize outgoing side RTP bearer terminations**. At this point, **preconditions are not met**. +- The MGW UP-IWU sends the **INVITE [SDP, IAM]** to the MSC Server / IWU. The message includes **100rel, UPDATE, precondition tag 3gOoBTC, supported codec list (updated), preconditions not met**. +- The MSC Server / IWU responds with **100 TRYING**. +- The MSC Server / IWU sends **183 Progress [SDP]** with **100rel, UPDATE, IETF codec list**. +- The MGW UP-IWU receives this and notes that **O-IWU selects codec**. It then performs **Seize incoming side RTP bearer terminations**. +- The MGW UP-IWU sends **183 Progress [SDP]** back to the 3GPP Node with **100rel, UPDATE, precondition tag 3gOoBTC, selected codec, available codecs, local preconditions met**. +- The MGW UP-IWU sends **PRACK** to the MSC Server / IWU. +- The MSC Server / IWU responds with **200 OK (PRACK) [SDP]** containing the **selected codec**. +- The MGW UP-IWU responds with **200 OK (PRACK)** to the 3GPP Node. +- The MSC Server / IWU sends **180 Ringing [ACM]** to the MGW UP-IWU. +- The MGW UP-IWU sends **PRACK** to the MSC Server / IWU. +- The MSC Server / IWU responds with **200 OK (PRACK)**. +- The MGW UP-IWU sends **UPDATE [SDP]** to the MSC Server / IWU, noting that **preconditions met**. +- The MSC Server / IWU responds with **200 OK (UPDATE) [SDP]**, noting that **local preconditions met**. +- The MGW UP-IWU sends **180 Ringing [ACM]** to the 3GPP Node. +- The MGW UP-IWU sends **PRACK** to the MSC Server / IWU. +- The MGW UP-IWU responds with **200 OK (PRACK)** to the 3GPP Node. +- The MSC Server / IWU receives a message from the External Network and notes that **preconditions are met**. It then sends **200 OK (INVITE) [ANM]** to the MGW UP-IWU. +- The MGW UP-IWU responds with **200 OK (INVITE) [ANM]** to the 3GPP Node. +- The MGW UP-IWU sends **ACK** to the MSC Server / IWU. +- The MSC Server / IWU sends **ACK** to the External Network. + +Sequence diagram for an outgoing call from a 3GPP Node to an External Network via an MGW UP-IWU and an MSC Server / IWU. The diagram shows the flow of SIP messages including INVITE, TRYING, 100rel, 183 Progress, PRACK, 200 OK, 180 Ringing, and ACK. It highlights the handling of preconditions, which are not met at the MGW but are updated and eventually met at the MSC Server. + +**Figure 4.6.3.2.1: Outgoing Call (message sequence chart), +example with support of 100rel but no support for preconditions** + +#### 4.6.3.3 Outgoing Call without support for 100rel and preconditions + +Figure 4.6.3.3.1 depicts an outgoing call where the external network does not support reliable provisional responses and therefore no SDP precondition signalling can be performed with the UPDATE method. With the 183 Progress the IWU receives an IETF codec list "unreliably". If the answer includes more than one codec the IWU cannot make a second offer to the external node (to lock the selected codec) during the early dialogue. However, the IWU can make use of the received information and start codec negotiation when forwarding the 183 Progress to the preceding 3GPP node. + +The IWU immediately sends 200 OK to PRACKs received from the 3GPP node, because it cannot forward them to the external node. The reliable provisional responses cannot be signalled end-to-end. + +The final response from the external network should include the same codecs as received previously within the Progress message. If this answer includes more than one codec the IWU makes a second offer to the external network with a re-INVITE request. + + + +``` + +sequenceDiagram + participant 3GPP Node + participant MGW UP-IWU + participant MSC Server / IWU + participant External Network + + Note left of MGW: from 3GPP Node + Note right of MSC: to External Network + + MGW->>MSC: INVITE [SDP, IAM] +100rel, UPDATE, precondition tag +3gOoBTC, supported codec list, +preconditions not met + MGW->>3GPP Node: TRYING + Note right of MGW: Seize outgoing side RTP bearer terminations + MSC->>External Network: INVITE [SDP, IAM] +100rel, UPDATE, precondition tag +3gOoBTC, supported codec list (updated) +preconditions not met + Note right of MSC: local preconditions are not met + External Network->>MSC: 100 TRYING + External Network->>MSC: 183 Progress [SDP] +IETF codec list + Note right of MSC: O-IWU selects codec + Note right of MGW: Seize incoming side RTP bearer terminations + MGW->>3GPP Node: 183 Progress [SDP] +100rel, UPDATE, precondition tag +3gOoBTC, selected codec, available codecs +local preconditions met + MGW->>MSC: PRACK + MGW->>3GPP Node: 200 OK (PRACK) + MGW->>MSC: UPDATE [SDP] +preconditions met + MGW->>3GPP Node: 200 OK (UPDATE) [SDP] +local preconditions met + Note right of MSC: preconditions are met + External Network->>MSC: 180 Ringing [ACM] + MGW->>3GPP Node: 180 Ringing [ACM] + MGW->>MSC: PRACK + MGW->>3GPP Node: 200 OK (PRACK) + External Network->>MSC: 200 OK (INVITE) [SDP, ANM] +IETF codec list + MGW->>3GPP Node: 200 OK (INVITE) [ANM] + MGW->>MSC: ACK + MSC->>External Network: ACK + MSC->>External Network: Re-INVITE [SDP] +selected codec + External Network->>MSC: 200 OK (re-INVITE) [SDP] +selected codec + MSC->>External Network: ACK + +``` + +Sequence diagram for an outgoing call from a 3GPP Node to an External Network via an MGW UP-IWU and an MSC Server / IWU. The diagram shows the signaling flow for INVITE, TRYING, Progress, OK, and ACK messages, with specific SDP details and bearer termination steps. + +Figure 4.6.3.3.1: Outgoing Call (message sequence chart), +example without support for 100rel and preconditions + +## 5 Interworking between a SIP-I based circuit-switched core network and an ISUP based network + +### 5.1 Reference Model + +Figure 5.1.1 details the interworking reference model for clause 5 of the present specification + + + +Figure 5.1.1: interworking reference model. The diagram shows two main components: 'SIP-I based CS CN' on the left and 'ISUP based network, either CS CN or external network' on the right, both represented by grey ovals. Between them is a light blue rectangular box labeled 'Scope of this TS'. Inside this box are two white rectangular boxes: 'IWU' at the top and 'UP-IWU' at the bottom. A vertical dashed line labeled 'H.248' connects the IWU and UP-IWU. A solid horizontal line (User Plane) connects the SIP-I based CS CN to the UP-IWU, and another solid horizontal line (User Plane) connects the UP-IWU to the ISUP based network. A dashed horizontal line (Control Plane) connects the SIP-I based CS CN to the IWU, labeled 'SIP-I over Nc' and 'media/ RTP/ UDP/IP/ over Nb'. Another dashed horizontal line (Control Plane) connects the IWU to the ISUP based network, labeled 'ISUP'. A solid horizontal line (User Plane) also connects the IWU to the ISUP based network, labeled 'TDM'. A legend at the bottom left shows a solid line for 'User Plane' and a dashed line for 'Control Plane'. A legend at the bottom right shows a light blue box for 'Scope of this TS'. + +NOTE: The IWU is a logical function that may reside with other 3GPP logical functions in the same physical nodes, e.g. in an (G)MSC Server. The figure shows only the logical separation. + +**Figure 5.1.1: interworking reference model** + +**Nb reference point:** The Nb reference point is defined in accordance with TS 29.414 [43]. + +**Nc reference point:** The Nc reference point is defined in accordance with TS 29.231 [4]. + +### 5.2 Control Plane Interworking + +The following clauses define the signalling interworking between the ISDN User Part (ISUP) protocols and Session Initiation Protocol (SIP) with its associated Session Description Protocol (SDP) and encapsulated ISUP at an IWU. + +The IWU shall act as a Type A or Type B exchange (ITU-T Recommendation Q.764 [7]) for the purposes of ISUP compatibility procedures. + +NOTE: An IWU may apply additional procedures to support interworking for national-specific capabilities. + +The ISUP capabilities or signalling information defined for national use are outside the scope of the present document. + +The services that can be supported through the use of the signalling interworking are limited to the services that are supported both within the ISUP based network and the SIP-I based CS CN. The IWU will originate and/or terminate services or capabilities that do not interwork seamlessly across domains according to the relevant protocol recommendation or specification. + +Table 5.2.1 lists the services seamlessly interworked within the scope of the present document. + +**Table 5.2.1: Seamlessly interworked Services** + +| Service | +|------------------------------------------------------------------| +| Speech/3.1 kHz audio | +| Data Calls (optional) | +| En bloc address signalling | +| Out of band transport of DTMF tones and information. (BICC only) | +| Inband transport of DTMF tones and information. (BICC and ISUP) | +| Multiple Subscriber Number (MSN) | +| Calling Line Identification Presentation (CLIP) | +| Calling Line Identification Restriction (CLIR) | +| Connected line presentation (COLP) | +| Connected line restriction (COLR) | +| Call Hold | +| Call Forwarding | +| Explicit Call Transfer (ECT) | +| User-to-User Signalling (UUS) | +| Call Deflection (CD) | +| Closed User Group (CUG) | +| Completion of Calls to Busy Subscriber (CCBS) | +| Multi-Level Precedence and Pre-emption (MLPP) | +| Call Waiting | + +The clause 5.3.2 of ITU-T Recommendation Q.1912.5 [6] describes additional general principles specific to SIP-I. + +The interworking procedures in clauses 5.3, 5.4 and 5.4 are based on ITU-T Recommendation Q.1912.5 [6] profile C. Clarifications are made within this specification on the application of ITU-T Recommendation Q.1912.5 [6] profile C. + +The control plane between the ISUP network and the SIP-I based CN is as shown in figure 5.2.1. + + + +The diagram illustrates the control plane interworking between an ISUP based network and a SIP-I based CS CN. It features a central 'Interworking Unit' (IWU) represented by a box with a split top. The IWU is divided into two vertical sections. The left section contains three stacked boxes labeled 'ISUP', 'MTP3', and 'MTP2'. The right section contains two stacked boxes labeled 'SIP-I' and 'SCTP'. Below these, the left section has an 'L1' box and the right section has an 'IP' box. To the left of the IWU, an arrow labeled 'ISUP' points to the top-left box, and an arrow labeled 'TDM' points to the bottom-left box. To the right of the IWU, an arrow labeled 'SIP-I' points from the top-right box, and an arrow labeled 'IP' points from the bottom-right box. Below the IWU, the text 'ISUP based network' is on the left and 'SIP-I based CS CN' is on the right. + +Diagram of control plane interworking between an ISUP based network and a SIP-I based CS CN through an Interworking Unit. + +**Figure 5.2.1: Control plane interworking between a SIP-I based circuit-switched core network and an ISUP based network** + +## 5.3 Signalling Interworking of a Call from the ISUP based network towards the SIP-I based circuit-switched core network + +### 5.3.1 General + +The procedures for Profile C in clause 7 of ITU-T Recommendation Q.1912.5 [6] shall be applied with the modifications provided in this subclause. + +#### 5.3.1.1 Sending of ISUP information to adjacent SIP nodes + +The IWU receiving ISUP information shall apply any interworking procedures detailed in clause 7 of ITU-T Recommendation Q.1912.5 [6] affecting parameters within the ISUP, and then proceed to encapsulate any ISUP information received (with the exception of the excluded messages detailed in 5.4.3 of ITU-T Recommendation Q.1912.5 [6]) in a SIP message in a MIME body according to IETF RFC 3204 [19]. SIP Header fields relating to the handling of the ISUP body shall be set as specified in clause 5.4.1.2 of ITU-T Recommendation Q.1912.5 [6]. + +NOTE 1: The text in the preceding paragraph has been derived from ITU-T Recommendation Q.1912.5 [6], clause 5.4.1. + +For a basic call setup, the SIP message used to encapsulate the ISUP message shall be the SIP message that was first triggered to be sent from the IWU as a result of the interworking specified in clause 7 of ITU-T Recommendation Q.1912.5 [6]. As an example, this means that an ISUP IAM will be encapsulated within the INVITE message that is sent out from the IWU. For the ISUP messages listed in table 1 of ITU-T Recommendation Q.1912.5 [6], the special procedures in clause 5.4.3 of ITU-T Recommendation Q.1912.5 [6] are applicable. + +NOTE 2: The text in the preceding paragraph has been derived from ITU-T Recommendation Q.1912.5 [6], clause 5.4.1.3. + +#### 5.3.1.2 Receipt of encapsulated ISUP information within SIP-I + +On receipt of a SIP message containing encapsulated ISUP, the IWU shall de-encapsulate the ISUP message from the SIP message body. The received SIP message shall be mapped to an ISUP message and merged with the de-encapsulated ISUP information according to the rules in clause 7 of ITU-T Recommendation Q.1912.5 [6]. + +NOTE 1: The text in the preceding paragraph has been derived from ITU-T Recommendation Q.1912.5 [6], clause 5.4.2. + +NOTE 2: These precedence rules have been derived from the following principles, which can also be applied for any ISUP information not covered by the present specification: + +- 1 Where a SIP header mapping to ISUP field(s) is possible (for example the mapping of Request-URI to Called Party Number), the SIP header is given precedence over the encapsulated ISUP value in the alignment process. (Conflicts can be caused by a possible service invocation within the SIP network.) +- 2 De-encapsulated ISUP information overrides ISUP information derived from default values (rather than SIP information). +- 3 Local ISUP procedures may modify information derived from SIP or default values. + +This Note has been derived from text in ITU-T Recommendation Q.1912.5 [6], clause 5.4.2 + +NOTE 3: There is a certain change against ITU-T Recommendation Q.1912.5 [6], where the above note is formulated as normative procedures. However, this is very high level and not required if you look at the real interworking procedures later on. Therefore formulating this as a Note makes much more sense. + +#### 5.3.1.3 Special procedures related to outgoing INVITE + +##### 5.3.1.3.1 Overlap Signalling + +The IWU does not need to support procedures related to overlap signalling in clause 7 of ITU-T Recommendation Q.1912.5 [6]. + +NOTE: No overlap signalling is used in a 3GPP CS domain. A G-MSC acting as IWU will collect all digits required to identify the called party and not propagate the overlap signalling further. + +### 5.3.1.3.2 Coding of encapsulated ISUP IAM parameters in outgoing INVITE + +The IWU may choose to transcode media, or attempt to interwork media without transcoding. If the IWU transcodes, it should set the TMR/USI/HLC parameters according to the codec applied in the SIP-I network. Otherwise, it should provide the TMR/USI/HLC parameters as received in the incoming IAM. If the IWU offers several codecs within SDP, it should set the TMR/USI/HLC parameters according to the preferred codec, applying the rules above for this codec. + +NOTE: ITU-T Recommendation Q.1912.5 [6] does not describe the relationship between TMR/USI/HLC and SDP codec negotiation. + +### 5.3.1.3.3 Media offered in SDP of outgoing INVITE + +The IWU should offer codecs known to be supported within the SIP-I based CS CN network. If multiple speech codecs are offered, Out of Band Transcoder Control (OoBTC) procedures shall be applied by the IWU in accordance with TS 23.153 [5]. Otherwise only the default PCM speech codec shall be signalled in an SDP offer; auxiliary payload types such as the Telephony Event RTP payload type may be included in addition. + +If the IWU applies the optional "optimised MGW selection" procedure, it shall include a MGW Identifier in the SDP. Related signalling procedures are described in clause 4.4 of TS 23.231 [3] and the encoding of the MGW Identifier is defined in TS 29.231 [4]. + +## 5.4 Signalling Interworking of a Call from SIP-I based circuit-switched core network towards the ISUP based network + +### 5.4.1 General + +The procedures for Profile C in clause 6 of ITU-T Recommendation Q.1912.5 [6] shall be applied with the modifications provided in this subclause. + +### 5.4.2 Interworking of received ISUP messages to SIP messages + +The IWU receiving backwards ISUP information shall apply any interworking procedures detailed in clause 6 of ITU-T Recommendation Q.1912.5 [6] affecting parameters within the ISUP, and then proceed to encapsulate any ISUP information received (with the exception of the excluded messages detailed in 5.4.3 of ITU-T Recommendation Q.1912.5 [6]) in a SIP message in a MIME body according to IETF RFC 3204 [19]. The selected SIP Header fields relating to the handling of the ISUP body shall be set as specified in clause 5.4.1.2 of ITU-T Recommendation Q.1912.5 [6]. + +### 5.4.3 Interworking of received SIP messages to ISUP messages + +#### 5.4.3.1 Receipt of encapsulated ISUP information within SIP + +On receipt of a SIP message containing encapsulated ISUP, the IWU shall de-encapsulate the ISUP message from the SIP message body. The received SIP message shall be mapped to an ISUP message and merged with the de-encapsulated ISUP message according to the rules for Profile C in clause 6 of ITU-T Recommendation Q.1912.5 [6]. + +NOTE 1: These precedence rules have been derived from the following principles, which can also be applied for any ISUP information not covered by the present specification: + +- 1 Where a SIP header mapping to ISUP field(s) is possible (for example the mapping of Request-URI to Called Party Number), the SIP header is given precedence over the encapsulated ISUP value in the alignment process. +- 2 De-encapsulated ISUP information overrides ISUP information derived from default values (rather than SIP information). +- 3 Local ISUP procedures may modify information derived from SIP or default values. + +This note has been derived from text in ITU-T Recommendation Q.1912.5 [6], clause 5.4.2. + +NOTE 2: There is a certain change against ITU-T Recommendation Q.1912.5 [6], where the above note is formulated as normative procedures. However, this is very high level and not required if you look at the real interworking procedures later on. Therefore formulating this as a note makes much more sense. + +### 5.4.3.2 Special Procedures for the Reception of SIP INVITE request + +#### 5.4.3.2.1 Propagation of overlap signalling toward the 3GPP CS domain + +The procedures in clause 6 of ITU-T Recommendation Q.1912.5 [6] related to the propagation of overlap signalling are not applicable, since no overlap signalling is used within the CS CN. + +#### 5.4.3.2.2 Derivation of TMR, USI and HLC parameters within sent IAM message + +The IWU may choose to transcode media and shall then set the parameters according to the coding applied within the CS Domain. Otherwise, the IWU shall select a codec for the SIP side termination using SDP offer-answer procedures, IETF RFC 3264 [22], and shall map the SDP information of this codec to the TMR/USI/HLC parameters according to table 2a of TS 29.163 [13]. If the information derived from this mapping matches the information in the TMR/USI/HLC parameters in the encapsulated ISUP, the TMR/USI/HLC parameters from the encapsulated ISUP should be used as they may contain additional information. If the information derived from this mapping contradicts the information in the TMR/USI/HLC parameters in the encapsulated ISUP, the TMR/USI/HLC parameters derived by the mapping shall be used. + +NOTE: The procedures in this note are an amendment compared to ITU-T Recommendation Q.1912.5 [6], which simply states the TMR parameters in encapsulated ISUP shall take precedence, However this is inappropriate if an incompatible codec is selected. + +#### 5.4.3.2.3 Receipt of SIP INVITE without SDP offer + +An IWU may reject receipt of SIP INVITE without SDP offer, otherwise the procedures in section 4.2.2.3 shall be followed. + +NOTE: A SIP INVITE without SDP offer is not used within the CS CN. + +#### 5.4.3.2.4 Special Procedures for deferred MGW selection procedure. + +If the IWU supports the optional "deferred MGW selection" procedure and receives an unspecified connection address in the SDP offer contained in the INVITE request, it should include a MGW Identifier for the IWU-UP it selects in the corresponding SDP answer. Related signalling procedures are described in clause 4.4 of TS 23.231 [3] and the encoding of the MGW Identifier is defined in TS 29.231 [4]. + +## 5.5 Supplementary services + +### 5.5.1 Special procedures for supplementary service interworking + +The supplementary services described in table 5.2.1 are interworked by using the parameters of the (de)encapsulated ISUP. No other interworking is required, except if otherwise described within the clauses below. + +### 5.5.2 Interworking of CLIP/CLIR supplementary service + +For the interworking of call towards the SIP-I based CS CN: the service shall be supported by encapsulation. + +For the interworking of call from the SIP-I based CS CN: ITU-T Recommendation Q.1912.5 [6], Annex B.1, shall apply. + +### 5.5.3 Interworking of Call Hold (HOLD) supplementary service + +The Profile C procedures in ITU-T Recommendation Q.1912.5 [6], clause B.10, shall be followed. + +### 5.5.4 Interworking of Completion of Calls to Busy Subscriber (CCBS) supplementary service to SIP networks + +The Profile C procedures of ITU-T Recommendation Q.1912.5 [6], clause B.11 shall be applied. + +## 5.6 User Plane Interworking + +### 5.6.1 General + +This clause describes user plane issues including interworking of DTMF. + +Figure 5.6.1.1 shows the user plane protocol stacks within the SIP-I based CS CN and an ISUP network. + +Apart from speech codecs, data call related codecs, e.g. as listed in table 2a of TS 29.163 [13], may be used. + + + +The diagram illustrates the user plane protocol stack for interworking between a SIP-I based CS CN and an ISUP based network. The stack consists of five layers: L1, L2, IP, UDP, and RTP. Above the stack, a 'Transcoding or Relay' function is indicated by a double-headed arrow. To the right of the stack, a box contains 'Codec, e.g. AMR' and 'e.g. G.711', with 'TDM' written below it. Below the stack, a box is labeled 'UP-IWU'. + +| | | +|-----------------------|---------------| +| Codec,
e.g.
AMR | e.g.
G.711 | +| RTP | TDM | +| UDP | | +| IP | | +| L2 | | +| L1 | | + +Diagram of User Plane Interworking and ISUP based CS Domain. It shows two network clouds connected via a central protocol stack. The left cloud is 'SIP-I based CS CN' and the right is 'ISUP based network'. The central stack has five layers: L1, L2, IP, UDP, and RTP. Above the stack, 'Transcoding or Relay' is indicated with a double-headed arrow. To the right of the stack, a box contains 'Codec, e.g. AMR' and 'e.g. G.711', with 'TDM' written below it. Below the stack, a box is labeled 'UP-IWU'. + +Figure 5.6.1.1: User Plane Interworking and ISUP based CS Domain + +### 5.6.2 DTMF + +If RTP Telephony Event is selected by the 3GPP CS CN the MGW shall filter out (delete) the DTMF from the default PCM codec when relaying the DTMF via the RTP Telephony Event to prevent potential double signalling of the same digit if a later insertion back to inband PCM transmission were to occur. + +## 5.7 Example Call flows + +The call flow examples in ITU-T Recommendation Q.1912.5 [6] Appendix III are applicable with the following exceptions for the reasons specified: + +- III.2.1.1 En bloc, subscriber free indication - flow does not include use of reliable provisional response within the SIP-I network +- III.2.1.2 En bloc, early ACM - flow does not include use of reliable provisional response within the SIP-I network +- III.2.1.3 En bloc, early media scenario - flow does not include use of reliable provisional response within the SIP-I network +- III.2.1.4 En bloc, simple segmentation procedures - flow does not include use of reliable provisional response within the SIP-I network +- III.2.1.10 Overlap signalling - 3GPP G-MSC will collect all digits before continuing the call +- III.2.2.1 Backward release during call setup - flow does not include use of reliable provisional response within the SIP-I network + +## 6 Interworking between a SIP-I based circuit-switched core network and a BICC based network + +### 6.1 Reference Model + +Figure 6.1.1 details the interworking reference model for clause 6 of the present specification. + + + +Figure 6.1.1: interworking reference model diagram. The diagram shows two main entities: 'SIP-I based CS CN' on the left and 'BICC based network, either CS CN or external network' on the right. Between them is a central box representing the 'Scope Of this TS', which contains two sub-components: 'IWU' (top) and 'UP-IWU' (bottom). The IWU is connected to the SIP-I based CS CN via a dashed line labeled 'SIP-I over Nc'. The UP-IWU is connected to the SIP-I based CS CN via a solid line labeled 'media/ RTP/ UDP/IP/ over Nb'. The IWU is connected to the BICC based network via a dashed line labeled 'BICC'. The UP-IWU is connected to the BICC based network via a solid line labeled 'TDM'. A vertical dashed line labeled 'H.248' connects the IWU and the UP-IWU. A legend at the bottom indicates that solid lines represent the 'User Plane' and dashed lines represent the 'Control Plane'. A light blue box represents the 'Scope Of this TS'. + +NOTE: The IWU is a logical function that may reside with other 3GPP logical functions in the same physical nodes, e.g. in an (G)MSC Server. The figure shows only the logical separation. + +**Figure 6.1.1: interworking reference model** + +**Nb reference point:** The Nb reference point is defined in accordance with TS 29.414 [43]. + +**Nc reference point:** The Nc reference point is defined in accordance with TS 29.231 [4]. + +## 6.2 Control Plane Interworking + +### 6.2.1 General + +The following clauses define the signalling interworking between the Bearer Independent Call Control (BICC) protocol (see ITU-T Recommendation Q.1902.1 to Q.1902.6 [8]) and the Session Initiation Protocol (SIP) with its associated Session Description Protocol (SDP) and encapsulated ISUP at an IWU. + +The IWU shall act as a Type A or Type B exchange (ITU-T Recommendation Q.764 [7]) for the purposes of ISUP compatibility procedures. + +The BICC capabilities or signalling information defined for national use are outside the scope of the present document. + +NOTE: An IWU may apply additional procedures to support interworking for national-specific capabilities. + +The services that can be supported through the use of the signalling interworking are limited to the services that are supported both within the BICC based network and the SIP-I based CS CN. The IWU will originate and/or terminate services or capabilities that do not interwork seamlessly across domains according to the relevant protocol recommendation or specification. + +Table 5.2.1 in clause 5.2 lists the services seamlessly interworked within the scope of the present document. + +The clause 5.3.2 of ITU-T Recommendation Q.1912.5 [6] describes additional general principles specific to SIP-I. + +The interworking procedures in the clauses 6.3 and 6.4 are based on ITU-T Recommendation Q.1912.5 [6] profile C. Clarifications are made within this specification on the application of ITU-T Recommendation Q.1912.5 [6] profile C. Specific rules for handling of the APM mechanism have been added, which are not specified in ITU-T Recommendation Q.1912.5 [6]. + +## 6.2.2 Signalling interactions between network entities in the control plane + +The control plane between a SIP-I based CS core networks and a BICC based network, where the underlying signalling transport is either IP or ATM respectively, is shown in figures 6.2.2.1 and 6.2.2.2. + + + +Figure 6.2.2.1: Control plane interworking between SIP-I based CS CN and a BICC based network with IP signalling transport. The diagram shows a central 'Interworking Unit' box with five layers. From top to bottom, the layers are: BICC, STCMTP, M3US, SCTP, and IP. On the left side, the top two layers (BICC and STCMTP) are connected to a 'BICC network'. The bottom three layers (M3US, SCTP, and IP) are connected to an 'IP' transport. On the right side, the top layer (BICC) is connected to an 'SIP-I' entity. The middle layer (M3US) is connected to an 'SCTP' entity. The bottom layer (IP) is connected to an 'IP' transport. Arrows indicate bidirectional signalling flow between the networks and the Interworking Unit. + +**Figure 6.2.2.1: Control plane interworking between SIP-I based CS CN and a BICC based network with IP signalling transport** + + + +Figure 6.2.2.2: Control plane interworking between SIP-I based CS CN and a BICC based network with ATM signalling transport. The diagram shows a central 'Interworking Unit' box with six layers. From top to bottom, the layers are: BICC, STC, MTP3B, SSCF, SSCOP, and AAL5. On the left side, the top four layers (BICC, STC, MTP3B, and SSCF) are connected to a 'BICC network'. The bottom two layers (SSCOP and AAL5) are connected to an 'ATM' transport. On the right side, the top layer (BICC) is connected to an 'SIP-I' entity. The fifth layer (SSCOP) is connected to an 'SCTP' entity. The bottom layer (AAL5) is connected to an 'IP' transport. Arrows indicate bidirectional signalling flow between the networks and the Interworking Unit. + +**Figure 6.2.2.2: Control plane interworking between SIP-I based CS CN and a BICC based network with ATM signalling transport** + +Signalling between the SIP-I based CS CN and the Interworking Unit uses the services of IP (IETF RFC 791 [14] or IETF RFC 2460 [17]), SCTP (IETF RFC 4960 [18]) and SIP-I. + +## 6.3 Signalling Interworking of a Call from the BICC based network towards the SIP-I based circuit-switched core network + +The procedures in clause 5.3 shall be applied with the modifications provided in the present subclause. + +The text in clause 5.3 is to be understood as follows: + +- Where "ISUP" is mentioned, this shall be understood as BICC. As an exception, references to ISUP encapsulated within SIP-I shall be understood without modification, i.e. they still refer to ISUP rather than BICC. + +If an IAM message is received, the APM information elements (see ITU-T Recommendation Q.765 [27]) relating to the BICC APM user (see ITU-T Recommendation Q.765.5 [28]) shall be removed before the IAM message is encapsulated in the triggered SIP INVITE message. + +An APM message received from the CS side (see ITU-T Recommendation Q.765 [27]) that relates to the BICC APM user (see ITU-T Recommendation Q.765.5 [28]) shall not be encapsulated in any triggered SIP message. + +## 6.4 Signalling Interworking of a Call from SIP-I based circuit-switched core network towards the BICC based network + +The procedures in clause 5.4 shall be applied with the modifications provided in the present subclause. + +The text in clause 5.4 is to be understood as follows: + +- Where "ISUP" is mentioned, this shall be understood as BICC. As an exception, references to ISUP encapsulated within SIP-I shall be understood without modification, i.e. they still refer to ISUP rather than BICC. + +An APM message received from the BICC side (see ITU-T Recommendation Q.765 [27]) that relates to the BICC APM user (see ITU-T Recommendation Q.765.5 [28]) shall not be encapsulated in any triggered SIP message. + +## 6.5 Supplementary services + +The procedures in clause 5.5 shall be applied. + +## 6.6 Codec Negotiation between a BICC based network and a SIP-I based circuit-switched core network + +### 6.6.1 General + +The procedures in Annex B of TS 29.163 [13] shall be applied with the modifications provided in the following clauses. + +The text in Annex B of TS 29.163 [13] is to be understood as follows: + +- Where "MGCF" is mentioned, this shall be understood as IWU. +- Where "IM-MGW" is mentioned, this shall be understood as UP-IWU. +- Where "IM CN subsystem" is mentioned, this shall be understood as SIP-I based circuit-switched core network. + +The offer/answer procedures of the Session Description Protocol (SDP) for media negotiation shall be applied as specified in TS 29.231 [4]. + +### 6.6.2 Codec Negotiation from SIP-I on Nc to BICC Network + +#### 6.6.2.1 Sending of IAM + +When the IWU receives an initial INVITE request with SDP offer containing a codec list with the 3GPP\_OoBTC\_Indicator, the procedures defined for a 3GPP node terminating SDP offer in clause 9 of TS 23.153 [5] shall be applied. The IWU shall follow the procedures of clause B.2.5 of TS 29.163 [13] to create a Supported Codec List for transmission in the outgoing IAM. + +#### 6.6.2.2 Sending of SDP Answer + +When the IWU receives the backward codec information, it shall apply the procedure defined in the clause B.2.1.2 of TS 29.163 [13] and shall create the SDP answer in accordance with the procedures defined for a 3GPP node terminating SDP offer in clause 9 of TS 23.153 [5]. + +#### 6.6.2.3 Mid-call Codec Negotiation initiated from SIP-I on Nc + +When the mid-call codec negotiation is initiated from the SIP-I based CS CN side the IWU: + +- shall apply the procedures defined for a 3GPP node terminating SDP offer in clause 9 of TS 23.153 [5] for the SIP-I based CS CN side, and +- shall apply the procedures from the clause B.2.3 of TS 29.163 [13] for the BICC network side. + +### 6.6.3 Codec Negotiation from BICC Network to SIP-I on Nc + +#### 6.6.3.1 Sending of initial SDP Offer + +When the IWU receives an IAM, the IWU shall follow the procedures of clause B.2.5 of TS 29.163 [13] to convert the Supported Codec List from the IAM into an SDP offer for transmission in the outgoing INVITE request. When generating the initial SDP offer, the IWU shall apply the procedures defined for a 3GPP node originating SDP offer in clause 9 of TS 23.153 [5]. + +#### 6.6.3.2 Responding to Serving Node initiating Codec Negotiation + +When the IWU receives the SDP answer it shall select a codec configuration for the SIP-I based CS CN side in accordance with clause 9 of TS 23.153 [5]. For the BICC network side the IWU shall apply the procedure defined in the clause B.2.2.2 of TS 29.163 [13]. + +#### 6.6.3.3 Mid-call Codec Negotiation initiated from BICC + +When the mid-call codec negotiation is initiated from the BICC side the IWU: + +- shall apply the procedures from the clause B.2.4 of TS 29.163 [13] for the BICC network side, and +- shall apply the procedures defined for a 3GPP node originating SDP offer in clause 9 of TS 23.153 [5] for the SIP-I based CS CN side. + +## 6.7 DMTF Signalling Interworking applicable for all Calls between a BICC network and a SIP-I based circuit-switched core network + +### 6.7.1 General + +DTMF signalling via the RTP telephony-event is mandated to be supported over the Nb interface for SIP-I based Circuit Switched Core Network on Nc Interface, see TS 23.231 [3]. However it is an option to use this transmission method when only the default PCM codec selected. + +BICC over Nc supports both inband DTMF and DTMF via OoB signalling within the BICC APM, see TS 23.205 [9]. If OoB TC is supported then use of OoB DTMF is mandated, see TS 23.153 [5]. External BICC networks may also transport DTMF either inband or via OoB signalling within the BICC APM. + +If the usage of the RTP Telephony Event has been negotiated within the SIP-I based CS CN, the IWU shall configure this payload type at the UP-IWU. + +### 6.7.2 DTMF transfer from SIP-I on Nc to BICC network (Out-of-Band DTMF) + +If RTP Telephony Event has been selected for the 3GPP SIP-I CS CN and OoB DTMF transmission is required in the succeeding BICC network the IWU shall use the Detect DTMF procedure to request the MGW to report DTMF Digits as described in clause 14.4.6 of TS 23.231 [3], i.e. RTP Telephony Event is configured in addition to the Detect DTMF Event. An example for the interworking with explicit duration reporting in BICC is shown in figure 6.7.2.1. + +NOTE 1: If the implicit duration is reported via the BICC Out Of Band procedure it can result in the duration being shorter than the original duration of the DTMF received at the MGW and even shorter than the minimum duration required by TS 23.014 [24]. + +An example for the interworking with implicit duration reporting in BICC is shown in figure 6.7.2.2. + +NOTE 2: Support of "start of DTMF detection" is optional for the MGW (UP-IWU). + + + +This sequence diagram illustrates the explicit duration DTMF interworking between an IWU and a UP-IWU, with a BICC Network (PLMN or External) and a Server. The process is triggered by the detection of a DTMF digit via an RTP Tel Event (start DTMF and StopDTMF). The sequence of messages is as follows: + + +- The IWU sends a **MOD. Request** [RTP Tel Event, Event = EndTone] (Tx) to the UP-IWU. Context (Cx) is indicated. +- The UP-IWU responds with a **MOD. Reply** (Tx). +- Simultaneously, the IWU sends an **RTP Telephony Event** [(Digit), E=1, Duration = y] Context (Cx) to the UP-IWU. +- The UP-IWU then sends a **Notify.Request** [Report DTMF, end tone, Digit, (duration=y)] (Tx) to the BICC Network. +- The BICC Network forwards the **Report DTMF Digit** to the Server via a **BICC OoB DTMF** (Digit (duration=y)) message. +- The UP-IWU receives a **Notify. Reply** (Tx) from the BICC Network. Context (Cx) is indicated. + +Figure 6.7.2.1: DTMF interworking: SIP-I to BICC, explicit duration (message sequence chart). + +Figure 6.7.2.1: DTMF interworking: SIP-I to BICC, explicit duration (message sequence chart) + + + +This sequence diagram illustrates the implicit duration DTMF interworking between an IWU and a UP-IWU, with a BICC Network (PLMN or External) and a Server. The process is triggered by the detection of a DTMF digit via an RTP Tel Event (start DTMF and StopDTMF). The sequence of messages is as follows: + + +- The IWU sends a **MOD. Request** [RTP Tel Event, Event = StartTone, EndTone] (Tx) to the UP-IWU. Context (Cx) is indicated. +- The UP-IWU responds with a **MOD. Reply** (Tx). +- Simultaneously, the IWU sends an **RTP Telephony Event** [(Digit), E=0, bit = 0, Duration = x] Context (Cx) to the UP-IWU. +- The UP-IWU then sends a **Notify.Request** [Report DTMF, start tone, Digit] (Tx) to the BICC Network. +- The BICC Network forwards the **Report start of DTMF Digit** to the Server via a **BICC OoB DTMF** (Start\_Digit) message. +- The UP-IWU receives a **Notify. Reply** (Tx) from the BICC Network. Context (Cx) is indicated. +- Subsequently, the IWU sends another **RTP Telephony Event** [(Digit), E=1, bit = 1, Duration = y] Context (Cx) to the UP-IWU. +- The UP-IWU then sends a **Notify.Request** [Report DTMF, end tone, Digit] (Tx) to the BICC Network. +- The BICC Network forwards the **Report end of DTMF Digit** to the Server via a **BICC OoB DTMF** (Stop\_Digit) message. +- The UP-IWU receives a **Notify. Reply** (Tx) from the BICC Network. Context (Cx) is indicated. + +Figure 6.7.2.2: DTMF interworking: SIP-I to BICC, implicit duration (message sequence chart). + +Figure 6.7.2.2: DTMF interworking: SIP-I to BICC, implicit duration (message sequence chart) + +If RTP Telephony Event has not been selected on 3GPP SIP-I CS CN interface and OoB DTMF is required in the BICC network the IWU shall request inband DTMF detection as described in clause 14.4.2.1 of TS 23.205 [9], i.e. the RTP Telephony Event is not configured. The same principles apply for signalling implicit or explicit DTMF digits. + +### 6.7.3 DTMF transfer from BICC network (Out-of-Band DTMF) to SIP-I on Nc + +If RTP Telephony Event has been selected for the 3GPP SIP-I CS CN and OoB DTMF transmission is selected in the succeeding BICC network the IWU shall use the "Send DTMF" procedure and may use the "Stop DTMF" procedures to request the MGW to play out DTMF to the IM CN subsystem whenever it receives out-of-band DTMF indications from the BICC network. + +The UP-IWU (MGW) shall signal the RTP Telephony event(s) in accordance with clause 14.4.4 of TS 23.231 [3]. + +If implicit DTMF timing is deployed (as shown in example message sequence chart in figure 6.7.3.1) and the MGW has already completed the digit transmission it shall not take any action upon the reception of the Stop DTMF procedure. + +![Sequence diagram for DTMF Interworking: BICC to SIP-I, implicit duration. The diagram shows three lifelines: (G)MSC-S (BICC), (G)MSC-S (SIP-I), and MGW. The interaction starts with the BICC (G)MSC-S sending a 'BICC Start DTMF (Digit)' message to the SIP-I (G)MSC-S, which includes a 'Context (Cx)'. The SIP-I (G)MSC-S then sends a 'MOD. Request [RTP Tel Event, signal = Digit] (Tx)' to the MGW. The MGW responds with 'Send DTMF Digit via RTP Tel Event, E=0'. The SIP-I (G)MSC-S receives a 'MOD. Reply (Tx)' from the MGW and sends a 'Context (Cx)' back to the BICC (G)MSC-S. Next, the BICC (G)MSC-S sends a 'Stop DTMF (Digit)' message to the SIP-I (G)MSC-S, which includes a 'Context (Cx)'. The SIP-I (G)MSC-S sends a 'MOD. Request [RTP Tel Event, stop signal = Digit] (Tx)' to the MGW. The MGW responds with 'Stop DTMF Digit via RTP Tel Event, E=1'. The SIP-I (G)MSC-S receives a 'MOD. Reply (Tx)' from the MGW and sends a 'Context (Cx)' back to the BICC (G)MSC-S. The diagram is numbered 1 and 2 in circles.](32ff77da4286b58c4778033acaa10836_img.jpg) + +Sequence diagram for DTMF Interworking: BICC to SIP-I, implicit duration. The diagram shows three lifelines: (G)MSC-S (BICC), (G)MSC-S (SIP-I), and MGW. The interaction starts with the BICC (G)MSC-S sending a 'BICC Start DTMF (Digit)' message to the SIP-I (G)MSC-S, which includes a 'Context (Cx)'. The SIP-I (G)MSC-S then sends a 'MOD. Request [RTP Tel Event, signal = Digit] (Tx)' to the MGW. The MGW responds with 'Send DTMF Digit via RTP Tel Event, E=0'. The SIP-I (G)MSC-S receives a 'MOD. Reply (Tx)' from the MGW and sends a 'Context (Cx)' back to the BICC (G)MSC-S. Next, the BICC (G)MSC-S sends a 'Stop DTMF (Digit)' message to the SIP-I (G)MSC-S, which includes a 'Context (Cx)'. The SIP-I (G)MSC-S sends a 'MOD. Request [RTP Tel Event, stop signal = Digit] (Tx)' to the MGW. The MGW responds with 'Stop DTMF Digit via RTP Tel Event, E=1'. The SIP-I (G)MSC-S receives a 'MOD. Reply (Tx)' from the MGW and sends a 'Context (Cx)' back to the BICC (G)MSC-S. The diagram is numbered 1 and 2 in circles. + +Figure 6.7.3.1: DTMF Interworking: BICC to SIP-I, implicit duration (message sequence chart) + +## 6.7.4 SIP-I on Nc interworking with BICC for Inband DTMF + +The interworking between inband and out-of-band transport shall be performed according to clause 14.4.8 in TS 23.231 [3], if required. + +If the RTP Telephony event has not been negotiated within the SIP-I based CS CN, the interworking MSC towards a BICC network with inband DTMF transport shall not configure the RTP Telephony event at the attached MGW. The MGW will then transfer DTMF within the speech codec without detecting it. + +## 6.8 User Plane Interworking + +### 6.8.1 General + +This clause describes user plane issues including interworking of DTMF. + +### 6.8.2 DTMF Interworking + +If RTP Telephony Event is selected for the internal 3GPP CS CN connection and inband DTMF is selected for the BICC network the MGW shall filter out (delete) the DTMF from the default PCM codec when relaying the DTMF via the RTP Telephony Event to prevent potential double signalling of the same digit if a later insertion back to inband PCM transmission were to occur. + +## 6.9 Example Call flows + +See clause 5.7. + +# 7 Interworking between a SIP-I based circuit-switched core network and the IP Multimedia (IM) Core Network (CN) Subsystem + +## 7.1 Reference Model + +### 7.1.1 General + +Figure 7.1.1.1 details the reference model required to support interworking between the 3GPP IM CN subsystem, as specified in 3GPP TS 23.228 [11] and 3GPP TS 24.229 [12] and a SIP-I based circuit-switched core network, as specified in 3GPP TS 23.231 [3] and 3GPP TS 29.231 [4]. + + + +Figure 7.1.1.1: IM CN subsystem to CS network logical interworking reference model. The diagram shows the logical interworking between the IM CN subsystem and the CS network. At the top, BGCF and CSCF are connected to MGCF via control plane interfaces Mj and Mg respectively. MGCF is connected to IM-MGW via a control plane interface Mn. IM-MGW is connected to a network entity (Note 1) via a user plane interface Mb and to the CS network via a user plane interface Nb. A legend indicates that solid lines represent the User Plane and dotted lines represent the Control Plane. + +NOTE 1: The IM-MGW may be connected via the Mb to various network entities, such as a UE (via a GTP Tunnel to a GGSN), an MRFP, a TrGW or an AGW. + +**Figure 7.1.1.1: IM CN subsystem to CS network logical interworking reference model** + +**Nb reference point:** The Nb reference point is defined in accordance with 3GPP TS 29.414 [43]. + +**Nc reference point:** The Nc reference point is defined in accordance with 3GPP TS 29.231 [4]. + +**Mg reference point:** The Mg reference point is defined in accordance with 3GPP TS 24.229 [12]. + +**Mj reference point:** The Mj reference point is defined in accordance with 3GPP TS 24.229 [12]. + +**Mb reference point:** The Mb reference point is defined in accordance with 3GPP TS 23.002 [2]. + +**Mn reference point:** The Mn reference point is defined in accordance with 3GPP TS 29.332 [54]. + +## 7.1.2 Signalling interactions between network entities in the control plane + +The control plane between the IM CN Subsystem supporting SIP and a 3GPP CS network supporting a SIP-I based Nc interface is as shown in figure 7.1.2. + + + +Figure 7.1.2.1: Control plane interworking protocol stack between the IM CN subsystem and a 3GPP CS network supporting SIP-I based Nc interface. The diagram shows the protocol stack for signalling. On the left, the 3GPP IMS DOMAIN contains a SIP signalling function with layers SIP, TCP/UDP/SCTP, and IP. On the right, the 3GPP CS DOMAIN contains a SIP-I signalling function with layers SIP-I, SCTP, and IP. In the center, the MGCF acts as a protocol converter with layers SIP, TCP/UDP/SCTP, and IP on the IMS side, and SIP-I, SCTP, and IP on the CS side. Arrows indicate the flow of signalling: IMS-SIP between the IMS SIP function and the MGCF SIP layer, and SIP-I/Nc between the MGCF SIP-I layer and the CS SIP-I function. IP layers are connected across all domains. + +**Figure 7.1.2.1: Control plane interworking protocol stack between the IM CN subsystem and a 3GPP CS network supporting SIP-I based Nc interface** + +Signalling between the SIP signalling function and the MGCF uses the services of IP (RFC 2460 [17]), and transport protocol such as TCP (RFC 793 [16]) or UDP (RFC 768 [15]) or SCTP (RFC 4960 [18]) (see TS 24.229 [12]), and SIP. + +Signalling between the SIP-I signalling function and the MGCF uses the services of IP (IETF RFC 791 [14] or IETF RFC 2460 [17]), SCTP (IETF RFC 4960 [18]) and SIP-I. + +## 7.2 Signalling Interworking of a Call from the IP Multimedia Subsystem towards the SIP-I based circuit-switched core network + +### 7.2.1 General + +If not otherwise stated within this clause the MGCF shall follow the below listed procedures for interworking incoming SIP calls: + +Sending SIP messages to the succeeding SIP-I based circuit-switched core network: + +- When an incoming SIP message is received from the preceding IMS node then the MGCF shall send this SIP message to the succeeding SIP-I based circuit-switched core network unless otherwise specified in the clauses below. +- The MGCF shall only send SIP methods, SIP headers, SDP body contents and other bodies as permitted by the profile for SIP-I on Nc as defined in TS 29.231 [4]. +- The MGCF shall, if defined by TS 29.163 [13], generate an ISUP message following TS 29.163 [13] and include this ISUP message into the SIP message in a MIME body according to IETF RFC 3204 [19]. The Content-Type header field and the Content-Disposition header field shall be set as specified in clause 5.4.1.2 of ITU-T Recommendation Q.1912.5 [6]. + +Sending SIP messages to the preceding IMS node: + +- When the MGCF receives a SIP-I message from the succeeding SIP-I based circuit-switched core network then the MGCF shall send this message to the preceding IMS node unless otherwise specified in the clauses below. +- The MGCF shall only send SIP methods, SIP headers, SDP body contents and other bodies which are permitted by the IMS profile as defined in TS 24.229 [12]. +- The MGCF shall construct IMS specific headers and bodies according to the procedures defined in TS 29.163 [13]. + +### 7.2.2 Exceptions from forwarding received SIP messages + +If call clearing is initiated either from the preceding IMS network or from the succeeding SIP-I based circuit switched core network then the MGCF shall apply the call clearing procedures as defined within TS 23.231 [3] clause 7.3.1. + +When a BYE request, 4xx, 5xx or 6xx final response to an initial INVITE request is received from the succeeding SIP-I based circuit switched core network and if a Reason Header field was not received and encapsulated ISUP REL message is included, then the ISUP Cause value received in the encapsulated ISUP REL message shall be mapped into SIP Reason header fields as specified in TS 29.163 [13]. If SIP message did not contain neither a Reason header nor encapsulated ISUP REL message, then a 4xx, 5xx, or 6xx final response shall be mapped to an ISUP cause value as specified in TS 29.163 [13] table 18 or BYE request shall be mapped to cause value 16; this cause value shall be mapped into the SIP Reason header fields as specified in TS 29.163 [13]. + +When a SIP failure response to an initial INVITE request is to be sent to the preceding IMS node, the cause value contained in the Reason header to be sent shall be used to determine the SIP failure response code as specified in TS 29.163 [13] table 9. + +If different SIP methods are used within the SIP-I based circuit switched core network and within the IMS network for basic call signalling or supplementary service signalling, then the MGCF shall map the received SIP message into the appropriate SIP message of the network the message is sent to. + +If the interworking procedures within TS 29.163 [13] do not result in any mapping then the MGCF shall not send the SIP message, which is received either from the SIP-I based circuit switched core network or from the IMS network, towards the other side. + +If the MGCF supports overlap signalling from the preceding IMS node and the first incoming SIP INVITE request does not provide a complete number, then the MGCF shall not forward this first SIP INVITE request and additional SIP INVITE requests or SIP INFO requests, which are used by the MGCF to collect all digits required to identify the called subscriber. + +The MGCF shall generate 100 Trying provisional SIP responses to acknowledge the receipt of INVITE requests. The MGCF shall not forward received 100 Trying provisional SIP responses. + +### 7.2.3 Sending SIP INVITE request + +The MGCF may reject receipt of SIP INVITE without SDP offer. Otherwise the MGCF shall construct an SDP offer with contents according to local policy, e.g. SDP for a G.711 speech call, in accordance with the built encapsulated IAM message. In the constructed SDP offer the MGCF shall encode preconditions as not met. + +NOTE 1: A SIP-I INVITE always includes an SDP offer within the CS CN. + +The MGCF shall forward the SIP INVITE request with the SDP offer and encapsulate an IAM message after the reception of the SIP INVITE request irrespective of the status of local and remote preconditions: + +When the incoming SIP INVITE request indicates that remote preconditions are not met or when local preconditions are not met then the MGCF shall include the tag "precondition" in the SUPPORTED header and shall encode preconditions in the SDP offer that the related local preconditions for QoS are not met. + +If the incoming SIP INVITE request indicates that remote preconditions are met, or if the incoming SIP INVITE request does not contain a precondition tag, and if local preconditions are met then the MGCF may either not include the tag "precondition" and exclude appropriate SDP lines, or include the tag "preconditions" in the SUPPORTED header and provide an SDP offer indicating that preconditions are met. + +NOTE 2: The use of SUPPORTED header is a deviation from IETF RFC 3312 [23] when the strength-tag contains a "mandatory" value. + +NOTE 3: The setting of the "Continuity Check Indicator" in the "Nature of Connection Indicators" parameter within the encapsulated IAM is of no significance. The value is ignored by the succeeding node of the SIP-I based circuit-switched core network. + +The MGCF shall not use the MGW bypass option, because some functions will not work as the succeeding SIP-I node does not know that it is interworking any IMS function. For example an incoming multimedia call from IMS does not result in a CS multimedia telephony service on the SIP-I based circuit switched core network. + +If the incoming SIP INVITE request does not provide a complete number, then the MGCF shall defer sending the SIP INVITE request until the MGCF has collected all digits required to identify the called subscriber. The additional digits may either, as a network option, be received in in-dialog SIP INFO requests or in additional SIP INVITE requests with the same Call-ID and From tag as a previous SIP INVITE. The MGCF shall apply the signalling procedures on the IMS side as specified in TS 29.163 [13]. + +### 7.2.4 Updating Precondition Information + +If the MGCF previously indicated to the succeeding SIP-I based circuit-switched core network that preconditions were not met, the MGCF shall send to the succeeding SIP-I based circuit-switched core network appropriate SDP lines indicating that local preconditions are met + +- when the MGCF receives from the preceding IMS network SDP indication that preconditions are met and local preconditions are met, +- or when remote preconditions at the preceding IMS network were already met and local precondition status of the MGCF changes to be met. + +NOTE: ISUP COT is not supported within SIP-I on Nc and therefore the ISUP COT message shall not be included into the SIP message. + +### 7.2.5 SDP Codec Negotiation + +When sending an SDP offer/answer to negotiate codecs with the succeeding SIP-I based circuit-switched core network the MGCF shall follow the procedures defined for a 3GPP Intermediate Node in clause 9 of TS 23.153 [5]. + +When sending an SDP offer/answer to negotiate codecs with the preceding IMS network the MGCF shall send codec information in accordance to TS 24.229 [12]. + +NOTE 1: Which codecs are negotiable with the IMS network may depend on operator choices and preferences (local policy). + +## 7.2.6 MGW Selection + +If the MGCF supports either the optional "Optimised MGW Selection" or the optional "Deferred MGW Selection" then the MGCF may include the SDP MGW Identifier into the SIP message being sent to the succeeding SIP-I based circuit switched core network in accordance to clause 4.4 of TS 23.231 [3]. + +Otherwise the MGCF shall seize a MGW and shall include the MGW connection address into the SDP offer of the initial SIP INVITE request it will send to the succeeding 3GPP SIP-I based circuit switched core network node. + +## 7.2.7 Autonomous Release + +For interworking towards the preceding IMS node the MGCF shall use the procedure as defined in TS 29.163 [13]. + +For call clearing towards the succeeding SIP-I based circuit switched core network the MGCF shall use the procedures as defined within TS 23.231 [3] clause 7.3. + +## 7.2.8 Further setting of SIP header values + +The MGCF shall act as a B2BUA as defined in IETF RFC 3261 [20]. The MGCF shall terminate the incoming SIP session and the MGCF shall originate an outgoing SIP-I call towards the SIP-I based circuit switched core network. Therefore the MGCF shall generate the SIP headers and values of Cseq, Call-ID, Via, Record-Route, Route and Contact independently from the received SIP message. For the generation of the Request-URI of an initial INVITE request and header fields To, From, Max-Forwards, and P-Asserted-Identity the MGCF shall use the information received from the preceding IMS node and perform the procedures specified below. + +The Request-URI of in-dialogue SIP requests will be populated with information received within the Contact header of previous responses according to SIP procedures. When sending a request towards the SIP-I based circuit switched core network the MGCF shall generate a From tag independent of the value received from the IMS. Furthermore, when sending a response towards the IMS, the MGCF shall generate a To tag independent of the value received from the SIP-I based circuit switched core network. + +The procedures for population of the Request-URI and header fields To, From, Max-Forwards, and P-Asserted-Identity are based on the mapping procedures specified in TS 29.163 [13]. The text in TS 29.163 [13] is to be understood as follows: + +- Where ISUP called party number is mentioned, this shall be understood as internal ISUP called party number. +- Where ISUP calling party number is mentioned, this shall be understood as internal ISUP calling party number. +- Where ISUP Generic Number (additional calling party number) is mentioned, this shall be understood as internal Generic Number (additional calling party number). +- Where ISUP Hop Counter parameter is mentioned, this shall be understood as internal ISUP Hop Counter parameter. + +NOTE: Only the userinfo component of the received SIP URI is used by mapping procedures according to TS 29.163 [13] while the received host part is ignored and a new value is generated by the MGCF. + +When sending an initial INVITE request towards the SIP-I based circuit switched core network the MGCF shall perform the following actions to generate the Request-URI and the To header field: + +- Create an internal ISUP called party number from the received Request URI according to TS 29.163 [13]. When Number Portability is supported the MGCF shall follow the procedures specified in clause 7.2.3.1.2A of TS 29.163 [13]. Otherwise the ISUP called party number is generated as specified in clause 7.2.3.1.2.1 of TS 29.163 [13]. +- Generate the new Request-URI and the new To header field from the internal ISUP called party number according to TS 29.163 [13]. +When Number Portability is supported the MGCF shall follow the procedures specified in clause 7.2.3.2.2A of TS 29.163 [13]. Otherwise the Request-URI and the To header field are generated as specified in clause 7.2.3.2.2.1 of TS 29.163 [13]. + +When sending an initial INVITE request towards the SIP-I based circuit switched core network the MGCF shall perform the following actions to generate the P-Asserted-Identity and the From header fields: + +- create an internal ISUP calling party number and an internal Generic Number (additional calling party number) as specified in clauses 7.2.3.1.2.6 and 7.2.3.1.2.7 of TS 29.163 [13]; and +- generate the new P-Asserted-Identity and the From header from the internal ISUP calling party number and the internal Generic Number (additional calling party number) as specified in clause 7.2.3.2.2.3 of TS 29.163 [13]. + +When sending the initial SIP INVITE request to the SIP-I based circuit-switched core network and if the Hop Counter procedure is supported in the SIP-I based circuit switched core network (national option), then the MGCF shall perform the following actions: + +- create an internal ISUP Hop Counter parameter from the received Max-Forwards value according to clause 7.2.3.1.2.9 of TS 29.163 [13]; and +- either generate the new Max-Forwards value from the internal ISUP Hop Counter parameter by applying the rules in clause 7.2.3.2.2.4 of TS 29.163 [13] and decrementing the resulting value by one or forward the received Max-Forwards value decremented by one. + +Otherwise if the MGCF forwards SIP request, it shall either set the Max-Forwards header to a default value or forward the received Max-Forwards value decremented by one. + +When receiving any SIP request with a Max-Forwards field value of zero, and if request shall be propagated to the other side, the MGCF shall reject the request with a 483 (Too Many Hops) SIP final response, in accordance with IETF RFC 3261 [20]. + +## 7.3 Signalling Interworking of a Call from SIP-I based circuit-switched core network towards the IP Multimedia Subsystem + +### 7.3.1 General + +If not otherwise stated within this clause the MGCF shall follow the below listed procedures for interworking outgoing SIP calls: + +Sending SIP messages to the succeeding IMS node: + +- When the MGCF receives a SIP-I message from the preceding SIP-I based circuit-switched core network then the MGCF shall send this message to the succeeding IMS network unless otherwise specified in the clauses below. +- The MGCF shall only send SIP methods, SIP headers, SDP body contents and other bodies which are permitted by the IMS profile as defined in TS 24.229 [12]. +- The MGCF shall construct IMS specific headers and bodies according to the procedures defined in TS 29.163 [13]. + +NOTE 1: This implies that if the incoming SIP-I message contained an encapsulated ISUP message then the ISUP message is removed from the forwarded SIP message. But the ISUP information may be mapped into a PSTN XML body, if supported as a network option. + +- Within IMS the initial INVITE request may be routed to a forking proxy. The MGCF shall be ready to receive responses generated due to a forked request and behave according to the procedures specified in IETF RFC 3261 [20] and clause 7.3.9 of the present specification. + +NOTE 2: The multiple early dialogues are not propagated to the preceding SIP-I based circuit-switched core network. + +NOTE 3: The MGCF does not, itself, perform forking. + +Sending SIP messages to the preceding SIP-I based circuit switched core network: + +- When the MGCF receives a SIP message from the succeeding IMS node then the MGCF shall send this SIP message to the preceding SIP-I based circuit-switched core network unless otherwise specified in the clauses below. + +- The MGCF shall only send SIP methods, SIP headers, SDP body contents and other bodies as permitted by the profile for SIP-I on Nc as defined in TS 29.231 [4]. +- The MGCF shall, if defined by TS 29.163 [13], construct an ISUP message following TS 29.163 [13] and include this ISUP message into the SIP message in a MIME body according to IETF RFC 3204 [19]. The Content-Type header field and the Content-Disposition header field shall be set as specified in clause 5.4.1.2 of ITU-T Recommendation Q.19.12.5 [6]. +- When sending an encapsulated ISUP ACM message or ISUP CPG message the MGCF shall follow the procedures defined within TS 29.163 [13] for the handling of the ring tone and therefore may request the IM-MGW to send ring tone in the backwards direction. + +### 7.3.2 Exceptions from forwarding received SIP messages + +If call clearing is initiated either from the succeeding IMS node or from the preceding SIP-I based circuit switched core network then the MGCF shall apply the call clearing procedures as defined within TS 23.231 [3] clause 7.3.1. + +When a BYE request is sent to the succeeding IMS node and if a Reason Header field was not received, then the received ISUP Cause value being received in the encapsulated ISUP REL message shall be mapped into SIP Reason header fields as defined by TS 29.163 [13]. + +When a BYE request, 4xx, 5xx or 6xx final response to an initial INVITE request is received from the succeeding IMS Node and the SIP message did not contain a Reason header, then a 4xx, 5xx, or 6xx final response shall be mapped to an ISUP cause value as specified in TS 29.163 [13] table 18 or BYE shall be mapped to cause value 16; this cause value shall be included in the encapsulated ISUP REL messages as specified in TS 29.163 [13]. + +When a SIP failure response to an initial INVITE request is to be sent to the preceding SIP-I node, the cause value contained in the encapsulated ISUP REL message to be sent shall be used to determine the SIP failure response code as specified in TS 29.163 [13] table 9. + +If different SIP methods are used within the SIP-I based circuit switched core network and within the IMS network for basic call signalling or supplementary service signalling, then the MGCF shall map the received SIP message into the appropriate SIP message of the network the message is sent to. + +The MGCF shall modify the SDP it forwards to include local address information from the IM-MGW and to adjust the codec information if the IM-MGW is configured to transcode. + +The MGCF shall not forward the received 100 Trying provisional SIP responses, and shall generate 100 Trying provisional SIP responses to acknowledge the receipt of INVITE requests. + +If the MGCF defers sending an INVITE request until preconditions are met (see clause 7.6.3.1), the MGCF shall reply to the INVITE request from the SIP-I based CS CN with a 183 Session Progress provisional response and shall not forward the subsequent PRACK and UPDATE requests from the SIP-I based CS CN, but reply with a final response to the received request. When the MGCF then receives from the preceding SIP-I based circuit-switched core network an SDP indication that preconditions are met and local preconditions are met, the MGCF shall forward to the succeeding IMS node the previously received INVITE request with appropriate SDP lines indicating that local preconditions are met. If MGCF then receives a 183 Session Progress provisional response, it shall either: + +- not forward this provisional response and acknowledge the receipt with a PRACK request toward the IMS; or +- if defined by TS 29.163 [13], construct an ISUP message and include this ISUP message into the 183 Session Progress provisional response in a MIME body and remove the SDP answer from the 183 Session Progress provisional response and forward it toward the SIP-I based CS CN. + +### 7.3.3 Sending SIP INVITE request + +When the MGCF receives an incoming SIP INVITE request the MGCF shall ignore the value of the Continuity Check indicator in the Nature of Connection Indicators parameter in the included IAM. If the incoming SIP INVITE request indicates that remote preconditions are not met or when local preconditions are not met then the MGCF should defer sending the INVITE request until remote and local preconditions are met. + +NOTE: This recommendation follows TS 29.163 [13] to avoid clipping and other obstacles, when the receiving IMS terminal does not support SIP preconditions and the SIP UPDATE method. + +As an option, instead of following the above procedure, the MGCF may include the tag "precondition" in the SUPPORTED header and encode preconditions in the SDP offer that the related local preconditions for QoS are not met. + +### 7.3.4 Updating Precondition Information + +If the MGCF previously indicated to the succeeding IMS node that preconditions were not met and a provisional response from the succeeding node indicated support for preconditions, then the MGCF shall send to the succeeding IMS node appropriate SDP lines indicating that local preconditions are met + +- when the MGCF receives from the preceding SIP-I based circuit-switched core network an SDP indication that preconditions are met and local preconditions are met, +- or when remote preconditions at the preceding SIP-I based circuit-switched core network were already met and local precondition status of the MGCF changes to be met. + +For each early SIP dialogue for which a provisional response has been received from the succeeding node indicating support for preconditions the MGCF, using an UPDATE or a PRACK request, shall send a confirmation that all the required preconditions have been met. This applies regardless of whether the early SIP dialogue existed prior to the preconditions being met or is subsequently created. The MGCF shall not interwork more than one 200 OK response to an UPDATE request sent in multiple early dialogues, and should select the 200 OK response for the early dialogue for which the resources at the IM-MGW are configured (see clause 7.3.9.2) for interworking. + +A 580 Precondition Failure response might be received from the succeeding IMS node as a response either to the INVITE request, to the UPDATE request or to the PRACK request. All early dialogues are considered terminated upon reception of the 580 Precondition Failure response to the INVITE request. The MGCF shall release the call in accordance with TS 29.163 [13], which also defines the coding of the REL message with Cause Code '127 Interworking' to be sent to the SIP-I based circuit-switched core network. The MGCF shall encapsulate the REL message into the 500 Server Internal Error response and send it to the SIP-I based circuit-switched 3GPP core network. + +Upon reception of the 580 Precondition Failure response to the UPDATE or to the PRACK request within early dialogue MGCF shall immediately send a BYE request to terminate this early dialogue. Only if there is no more early dialogues, the MGCF shall encapsulate the REL message with Cause Code '127 Interworking' into the 500 Server Internal Error response and send it to the SIP-I based circuit-switched 3GPP core network. + +### 7.3.5 Receipt of SIP redirect (3xx) response + +When receiving a SIP response with a response code 3xx, the default behaviour of the MGCF is to release the call, where the MGCF sends to the preceding SIP-I based circuit-switched core network 480 Temporarily unavailable and encapsulate an ISUP REL message with a cause code value 127 (Interworking unspecified). + +NOTE 1: The MGCF may also decide for example to redirect the call towards the URIs in the Contact header field of the response as an operator option, but such handling is outside of the scope of the present document. + +NOTE 2: Above default behaviour and Note 1 is adopted from TS 29.163 [13]. + +### 7.3.6 SDP Codec Negotiation + +When sending an SDP offer/answer to negotiate codecs with the succeeding IMS network the MGCF shall send codec information in accordance with TS 24.229 [12]. + +When sending an SDP offer/answer to negotiate codecs with the preceding SIP-I based circuit-switched core network the MGCF shall follow the procedures defined for a 3GPP Intermediate Node in clause 9 of TS 23.153 [5]. + +NOTE: Which codecs are negotiable with the IMS network may depend on operator choices and preferences (local policy). + +If the MGCF received an SDP answer without the OoBTC Indicator and multiple codecs from the IMS, and initiates a second offer toward the IMS in accordance with the procedures for a 3GPP Intermediate Node in clause 9 of TS 23.153 [5], the MGCF shall: + +- if it added the SDP offer to a SIP message received from the SIP-I based CS CN (e.g. a PRACK), remove the SDP answer from the corresponding response before sending it to the SIP-I based CS CN; and + +- if it created a new SIP message (e.g. UPDATE or re-INVITE) to send the SDP offer to the IMS, not forward the SIP message with the SDP answer (e.g. a 200 OK) to the SIP-I based CS CN. + +If the MGCF receives from the IMS due to forking for one SDP offer multiple SDP answers in provisional SIP responses of different early dialogues, the MGCF shall only interwork the first SDP answer and the MGCF shall not include any SDP answers in any subsequent SIP early responses it decides to forward. + +If the MGCF sends an SDP offer within multiple UPDATE requests for different early dialogues towards the IMS side, it will receive an SDP answer in the response to each UPDATE request and the MGCF shall not interwork more than one 200 OK response to an UPDATE request sent in multiple early dialogues, and should select the 200 OK response for the early dialogue for which the resources at the IM-MGW are configured (see clause 7.3.9.2) for interworking. + +### 7.3.7 MGW Selection + +If the MGCF supports either the optional "Optimised MGW Selection" or the optional "Deferred MGW Selection" then the MGCF shall not send a SDP MGW Identifier towards the succeeding IMS network. The MGCF shall seize an IM-MGW and shall then include the connection address in the SDP offer of the initial SIP INVITE request it will send to the succeeding IMS node. + +If the MGCF supports the optional "deferred MGW selection" procedure and receives an unspecified connection address in the SDP offer contained in the SIP INVITE request, it should include an MGW\_Identifier for the IM-MGW it selects in the corresponding answer. The encoding of the MGW\_Identifier is defined in TS 29.231 [4]. + +The MGCF shall not use the "MGW bypass" option. + +### 7.3.8 Autonomous Release + +For interworking towards the succeeding IMS node the MGCF shall use the procedure as defined in TS 29.163 [13]. + +For call clearing towards the preceding SIP-I based circuit switched core network the MGCF shall use the procedures as defined within TS 23.231 [3] clause 7.3 for call clearing towards the originating side. + +### 7.3.9 Handling of forked SIP Responses + +#### 7.3.9.1 SIP Dialogues + +The MGCF shall inspect the tag in the 'To' header field of a non-100 provisional and a 2xx final responses in accordance to SIP procedures specified in IETF RFC 3261 [20] to identify the SIP dialogue the response belongs to. If responses belonging to different dialogues are received, the initial INVITE request has been forked. + +#### 7.3.9.2 Reception of non-100 provisional Responses to initial INVITE + +Since the MGCF does not know that forking has occurred until a second non-100 provisional response creating a new early dialogue arrives the MGCF shall request the bearer resources as required by the first received SDP answer. + +For each subsequent non-100 provisional response within a new early dialogue that is received, the MGCF shall apply the following procedures: + +- Depending on the requirements in the SDP answer and the presence of P-Early-Media header the MGCF may either refrain from reconfiguring the IM-MGW, or it may use the Configure IMS Resources procedure. +- The MGCF shall construct an ISUP message in accordance to TS 29.163 [13], and send it within the SIP message to the SIP-I based circuit-switched 3GPP core network. The MGCF shall use only one SIP dialogue within the SIP-I based circuit-switched 3GPP core network, and the MGCF shall thus supply the same 'To' header field in all SIP responses relating to a call it sends towards the SIP-I based circuit-switched 3GPP core network. +- However, the MGCF may refrain from sending additional subsequent non-100 provisional response to the SIP-I based CS CN if they do not contain any new information compared to the last previous non-100 provisional response it sent towards the SIP-I based CS CN. +- If the MGCF already received an SDP answer in a previous non-100 provisional response within another early dialogue (and thus forwarded the SDP answer), the MGCF shall not include the SDP answers in any subsequent non-100 provisional response it decides to send towards the SIP-I based CS CN. + +- The MGCF shall send a PRACK request to the IMS to acknowledge the receipt of the subsequent non-100 provisional response. The MGCF will receive a response to the PRACK and shall not forward this response to the SIP-I based CS CN. +- If multiple codecs were contained in the provisional response, the MGCF shall include an SDP offer with the codec configured at the IM-MGW within the PRACK request. + +### 7.3.9.3 Reception of final Responses to initial INVITE + +Upon reception of a non-2xx final response to initial INVITE all early dialogues are considered terminated. The MGCF shall acknowledge it with an ACK request. In addition the MGCF shall create an encapsulated REL message as described in TS 29.163 [13] and shall send it within a non-2xx final response (initial INVITE) to the SIP-I based circuit-switched 3GPP core network. + +When a first 2xx final response is received for one of the early dialogues or when a received 2xx final response to an INVITE creates a new dialogue, the MGCF shall acknowledge it with the ACK request. If the remote IMS resources configured at the IM-MGW do not match the remote resources selected for the confirmed dialogue MGCF shall require updating the allocated resources. In addition the MGCF shall create an encapsulated ANM or CON message as described in TS 29.163 [13] and shall send it within a final 200 OK response to the initial INVITE to the SIP-I based circuit-switched 3GPP core network. If the previously negotiated codecs in the SIP-I based CS CN differ from the remote resources selected for the confirmed dialogue, to avoid transcoding the MGCF should construct a new SDP offer based upon those remote resources and send it to the SIP-I based CS CN within an UPDATE or re-INVITE request. + +Upon the reception of a subsequent final 2xx response for any further dialogue for an INVITE request due to forking, the MGCF shall: + +- 1) acknowledge the response with the ACK request; and +- 2) send a BYE request to this dialogue in order to terminate it. + +The INVITE transaction is completed 64\*T1 seconds after the reception of the first 2xx response. At this point the MGCF shall terminate all early dialogs that have not been already transitioned to confirmed or terminated state. + +### 7.3.10 Further setting of SIP header values + +The MGCF shall act as a B2BUA as defined in IETF RFC 3261 [20]. The MGCF shall terminate the incoming SIP-I session and the MGCF shall originate an outgoing SIP session towards the succeeding IMS node. Therefore the MGCF shall generate the SIP headers and values of Cseq, Call-ID, Via, Record-Route, Route and Contact independently from the received SIP-I message. For the generation of the Request-URI of an initial INVITE requests and header fields To, From, Max-Forwards, and P-Asserted-Identity the MGCF shall use the information received from the SIP-I based circuit switched core network node and perform the procedures specified below. + +The Request-URI of in-dialogue SIP requests will be populated with information received within the Contact header of previous responses according to SIP procedures. When sending a request towards the IMS the MGCF shall generate a From tag independent of the value received from the SIP-I based circuit switched core network. Furthermore, when sending a response towards the SIP-I based circuit switched core network, the MGCF shall generate a To tag independent of the value received from the IMS. + +The procedures for population of the Request-URI and header fields To, From, Max-Forwards, and P-Asserted-Identity are based on the mapping procedures specified in TS 29.163 [13]. The text in TS 29.163 [13] is to be understood as follows: + +- Where ISUP called party number is mentioned, this shall be understood as internal ISUP called party number. +- Where ISUP calling party number is mentioned, this shall be understood as internal ISUP calling party number. +- Where ISUP Generic Number (additional calling party number) is mentioned, this shall be understood as internal ISUP Generic Number (additional calling party number). + +NOTE: Only the userinfo component of the received SIP URI is used by mapping procedures according to TS 29.163 [13] while the received host part is ignored and a new value is generated by the MGCF. + +When sending an initial INVITE request towards the IMS network the MGCF shall perform the following actions to generate the Request-URI and the To header field: + +- Create an internal ISUP called party number from the received Request URI according to TS 29.163 [13]. When Number Portability is supported the MGCF shall follow the procedures specified in clause 7.2.3.1.2A of TS 29.163 [13]. Otherwise the internal ISUP called party number is generated as specified in clause 7.2.3.1.2.1 of TS 29.163 [13]. +- Generate the new Request-URI and the new To header field from the internal ISUP called party number according to TS 29.163 [13]. When Number Portability is supported the MGCF shall follow the procedures specified in clause 7.2.3.2.2A of TS 29.163 [13]. Otherwise the Request-URI and the To header field are generated as specified in clause 7.2.3.2.2.1 of TS 29.163 [13]. + +When sending an initial INVITE request towards the IMS network the MGCF shall perform the following actions to generate the P-Asserted-Identity and the From header fields: + +- create an internal ISUP calling party number and an internal Generic Number (additional calling party number) as specified in clauses 7.2.3.1.2.6 and 7.2.3.1.2.7 of TS 29.163 [13]; and +- generate the new P-Asserted-Identity and the From header from the internal ISUP calling party number and the internal Generic Number (additional calling party number) as specified in clause 7.2.3.2.2.3 of TS 29.163 [13]. + +When sending the initial SIP INVITE request to the IMS network and if the Hop Counter procedure is supported in the SIP-I based circuit switched core network (national option), then the MGCF shall either generate the Max-Forwards value from the received ISUP Hop Counter parameter by applying the rules in clause 7.2.3.2.2.4 of TS 29.163 [13] and decrementing the resulting value by one or forward the received Max-Forwards value decremented by one. + +Otherwise if the MGCF forwards SIP request, it shall either set the Max-Forwards header to a default value or forward the received Max-Forwards value decremented by one. + +When receiving any SIP request with a Max-Forwards field value of zero, and if request shall be propagated to the other side, the MGCF shall reject the request with a 483 (Too Many Hops) SIP final response, in accordance with IETF RFC 3261 [20]. + +## 7.4 DMTF Signalling Interworking applicable for all Calls between an IP Multimedia CN Subsystem and a SIP-I based circuit-switched core network + +The procedures in clause 4.4 are applicable with modifications described in the present subclause. + +Where the external SIP-I network is mentioned in the procedures in clause 4.4, this shall be understood as IP Multimedia (IM) Core Network (CN) Subsystem. Where an "IWU" is mentioned in those procedures, this shall be understood as MGCF. + +The IMS need not include the PCM codec in SDP offers and answers it sends. + +However, it is assumed that the RTP Telephony Event will always be included in SDP offers and answers from the IMS. + +If an IWU receives an SDP offer from a preceding 3GPP SIP-I node without the RTP Telephony Event (only permitted if only default PCM codec offered) then it shall include the RTP Telephony Event in the subsequent offer to the IMS. + +Procedures in clause 4.4 related to receiving SDP offers or answers from the external network without the RTP Telephony Event do not apply for the interworking towards the IMS. + +## 7.5 User Plane Interworking + +### 7.5.1 General + +This clause describes user plane issues including interworking of DTMF. + +Figure 7.5.1.1 shows the user plane protocol stacks within the IP Multimedia Subsystem and the 3GPP SIP-I based circuit switched core network. + + + +The diagram illustrates the user plane interworking between an IMS (IP Multimedia Subsystem) and a SIP-I based CS CN (Circuit Switched Core Network). The IMS is represented by a grey oval on the left, connected via an Mb interface. The SIP-I based CS CN is represented by a grey oval on the right, connected via an Nb interface. Between them is a protocol stack table with five rows. Above the table, a label 'Transcoding or Relaying' with a double-headed arrow indicates the function of the MGCF (Media Gateway Control Function). + +| | | +|-----------------------|-----------------------| +| Codec,
e.g. NB-AMR | Codec,
e.g. NB-AMR | +| RTP | RTP | +| UDP | UDP | +| IP | IP | +| L2, L1 | L2, L1 | + +Diagram of user plane interworking between IMS and SIP-I based CS CN. The diagram shows a stack of protocols: Codec (e.g. NB-AMR), RTP, UDP, IP, and L2, L1. The IMS side connects via an Mb interface, and the SIP-I based CS CN side connects via an Nb interface. A 'Transcoding or Relaying' label with a double-headed arrow is above the protocol stack, indicating the function of the MGCF. + +**Figure 7.5.1.1: user plane interworking** + +If the same speech codec is used on both sides, no speech transcoding is required. + +## 7.5.2 DTMF Interworking + +The procedures in clause 4.5.2 are applicable, however where the external SIP-I network is mentioned in those procedures, this shall be understood as IP Multimedia (IM) Core Network (CN) Subsystem. Where an "IWU" is mentioned in those procedures, this shall be understood as MGCF. + +# 7.6 Example Call flows + +## 7.6.1 General + +In this clause call flows are shown as examples to demonstrate the signalling interworking of the MGCF. Within the message sequence charts some contents of the messages are shown in order to visualise some of the important interworking aspects, which were described in previous clauses of this document. It is to be noted that the intention is neither to show the complete content of the SIP messages nor to use the exact syntax of SIP and SDP messages as it is defined in the respective RFCs. It is also not the intention to show all alternative options that are possible for a certain call flow. + +## 7.6.2 Incoming Call flows + +The first call flow shows the signalling for a successful basic call establishment and the later call release. The second call flow depicts a failed call setup. + +### 7.6.2.1 Successful Call Establishment and Call Release + +Figure 7.6.2.1.1 shows the first part of the incoming call signalling until the called party is alerted and the MGCF is waiting for an answer message. + +Before the received SIP INVITE request is forwarded to SIP-I based circuit switched core network the MGCF removes the PSTN XML body (after content mapped into SIP-I message), replaces the received codec list by a 3GPP structured codec list, and encapsulates the ISUP IAM message, which the MGCF mapped from the received SIP INVITE request. + +The incoming side RTP bearer termination is not yet successfully reserved and configured and therefore local preconditions are not met. Thus the MGCF initiates precondition signalling when sending the INVITE request to the succeeding SIP-I based circuit-switched network. + +The MGCF and the succeeding node perform codec negotiation according to 3GPP rules as specified in TS 23.153 [5]. The MGCF answers to the preceding IMS node with a single selected codec. If possible, the selected codec is the same as received from the 3GPP node to avoid transcoding at the network border. + +With the 183 Progress the MGCF authorizes the preceding node to use early media. Therefore, it is not necessary to include the P-Early-Media header in the 180 Ringing response. + + + +The sequence diagram illustrates the message flow for an incoming call. The participants are IMS core node (CSCF, BGCf, TrGW), MGCF, IM-MGW, and SIP-I based circuit-switched core network. The MGCF is connected to the IMS core node via the Mj/Mg interface, to the SIP-I network via the Nc interface, and to the IM-MGW via the Mn interface. + +``` + +sequenceDiagram + participant IMS as IMS core node (CSCF, BGCf, TrGW) + participant MGCF + participant IM-MGW + participant SIP as SIP-I based circuit-switched core network + + Note right of MGCF: remote preconditions are met; local preconditions are not met + IMS->>MGCF: INVITE [SDP, PSTN XML] +100rel, UPDATE, P-Early-Media, IMS codec list, PSTN XML + MGCF-->>IMS: 100 Trying + MGCF->>IM-MGW: Seize outgoing side RTP bearer terminations + MGCF->>SIP: INVITE [SDP, IAM] +100rel, UPDATE, precondition tag, 3gOoBTC, supported codec list, preconditions not met, IAM + IM-MGW-->>MGCF: 100 Trying + IM-MGW-->>MGCF: 183 Progress [SDP] +100rel, UPDATE, precondition tag, 3gOoBTC, selected codec, available codecs + MGCF->>IM-MGW: Seizure of ingoing side RTP bearer terminations, though-connection + Note right of MGCF: local preconditions are met, authorise early media + MGCF-->>IMS: 183 Progress [SDP] +100rel, UPDATE, P-Early-Media, selected codec + IMS->>MGCF: PRACK + MGCF-->>IMS: 200 OK (PRACK) + IMS->>MGCF: 180 Ringing + MGCF-->>IM-MGW: PRACK + IM-MGW-->>MGCF: 200 OK (PRACK) + MGCF-->>SIP: 180 Ringing [ACM] + MGCF->>SIP: PRACK + SIP-->>MGCF: 200 OK (PRACK) + +``` + +Key message details: + +- INVITE [SDP, PSTN XML]** from IMS to MGCF includes 100rel, UPDATE, P-Early-Media, IMS codec list, and PSTN XML. +- 100 Trying** is returned from MGCF to IMS. +- Seize outgoing side RTP bearer terminations** is a control message from MGCF to IM-MGW. +- INVITE [SDP, IAM]** from MGCF to SIP includes 100rel, UPDATE, precondition tag, 3gOoBTC, supported codec list, preconditions not met, and IAM. +- 100 Trying** is returned from IM-MGW to MGCF. +- 183 Progress [SDP]** from IM-MGW to MGCF includes 100rel, UPDATE, precondition tag, 3gOoBTC, selected codec, and available codecs. +- Seizure of ingoing side RTP bearer terminations, though-connection** is a control message from MGCF to IM-MGW. +- 183 Progress [SDP]** from MGCF to IMS includes 100rel, UPDATE, P-Early-Media, and selected codec. +- PRACK** is sent from IMS to MGCF. +- 200 OK (PRACK)** is returned from MGCF to IMS. +- 180 Ringing** is sent from IMS to MGCF. +- PRACK** is sent from MGCF to IM-MGW. +- 200 OK (PRACK)** is returned from IM-MGW to MGCF. +- 180 Ringing [ACM]** is sent from MGCF to SIP. +- PRACK** is sent from MGCF to SIP. +- 200 OK (PRACK)** is returned from SIP to MGCF. + +Sequence diagram for an incoming call (message sequence chart) showing interactions between IMS core node, MGCF, IM-MGW, and SIP-I based circuit-switched core network. + +**Figure 7.6.2.1.1: Incoming Call (message sequence chart), Called Party alerted** + +Figure 7.6.2.1.2 shows how the call setup is finalised and how the call is later released from the IMS side. + + + +The diagram illustrates the message sequence for an incoming call. It features four lifelines: IMS core node (CSCF, BGCF, TrGW), MGCF, IM-MGW, and SIP-I based circuit-switched core network. The sequence begins with a 200 OK (INVITE) message from the MGCF to the IMS core node, followed by an ACK message from the IMS core node to the MGCF. Simultaneously, the MGCF sends a 200 OK (INVITE) [ANM] message to the SIP-I based circuit-switched core network, which is acknowledged by an ACK message. A box labeled "For preceding signalling sequences see Figure 7.6.2.1.1" indicates the start of the sequence. The "Active Session" phase is shown between the MGCF and the SIP-I based circuit-switched core network. The call is terminated with a BYE message from the MGCF to the IMS core node, followed by a 200 OK (BYE) message from the IMS core node to the MGCF. The MGCF also sends a BYE [REL] message to the SIP-I based circuit-switched core network, which is acknowledged by a 200 OK (BYE) [RLC] message. + +``` + +sequenceDiagram + participant IMS as IMS core node (CSCF, BGCF, TrGW) + participant MGCF + participant IM-MGW + participant SIP as SIP-I based circuit-switched core network + + Note right of MGCF: For preceding signalling sequences see Figure 7.6.2.1.1 + + Note over MGCF, SIP: Active Session + + MGCF->>IMS: 200 OK (INVITE) + IMS->>MGCF: ACK + MGCF->>SIP: 200 OK (INVITE) [ANM] + SIP->>MGCF: ACK + + MGCF->>IMS: BYE + IMS->>MGCF: 200 OK (BYE) + MGCF->>SIP: BYE [REL] + SIP->>MGCF: 200 OK (BYE) [RLC] + +``` + +Sequence diagram for an incoming call. Lifelines: IMS core node (CSCF, BGCF, TrGW), MGCF, IM-MGW, and SIP-I based circuit-switched core network. The diagram shows the signaling flow for an incoming call, starting with a 200 OK (INVITE) and ending with a BYE and 200 OK (BYE) sequence. A box indicates that preceding signaling sequences are shown in Figure 7.6.2.1.1. + +**Figure 7.6.2.1.2: Incoming Call (message sequence chart), +Continuation of figure 7.6.2.1.1** + +## 7.6.2.2 Autonomous Release at MGCF + +In this example, the MGCF is waiting for an answer from the called subscriber, i.e. the final response to the SIP INVITE request. Figure 7.6.2.2.1 shows the signalling when the waiting timer expires. The MGCF initiates call clearing towards the succeeding SIP-I based circuit-switched network by sending an ISUP REL message included in a SIP BYE request. It also sends a final response for the SIP INVITE request towards the preceding IMS node indicating the error that happened. + +![Figure 7.6.2.2.1: Incoming Call Failure (message sequence chart), called subscriber does not answer. The diagram shows a sequence of messages between an IMS core node (CSCF, BGCF, TrGW), an MGCF, an IM-MGW, and a SIP-I based circuit-switched core network. The sequence starts with a message from the IMS core node to the MGCF. The MGCF sends a message to the IM-MGW. The IM-MGW sends a message to the SIP-I based circuit-switched core network. The SIP-I based circuit-switched core network sends a 480 Temporarily Unavailable message to the MGCF. The MGCF sends an ACK message to the IMS core node. The MGCF also sends a BYE [REL] message to the IM-MGW. The IM-MGW sends a 200 OK (BYE) [RLC] message to the MGCF. A timer T9 'awaiting answer' expires at the MGCF. A note indicates that for preceding signalling sequences see Figure 7.6.2.1.1.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +The diagram illustrates the message sequence for an incoming call failure where the called subscriber does not answer. The participants are: IMS core node (CSCF, BGCF, TrGW), MGCF, IM-MGW, and SIP-I based circuit-switched core network. The sequence of messages is as follows: + +- The IMS core node sends a message to the MGCF. +- The MGCF sends a message to the IM-MGW. +- The IM-MGW sends a message to the SIP-I based circuit-switched core network. +- The SIP-I based circuit-switched core network sends a **480 Temporarily Unavailable** message to the MGCF with a reason header: cause = 19. +- The MGCF sends an **ACK** message to the IMS core node. +- At the MGCF, **Timer T9 "awaiting answer" expires**. +- The MGCF sends a **BYE [REL]** message to the IM-MGW with a reason header: cause = 19 and a Cause value in REL = 19 "no answer from user (user alerted)". +- The IM-MGW sends a **200 OK (BYE) [RLC]** message to the MGCF. + +For preceding signalling sequences see Figure 7.6.2.1.1 + +Figure 7.6.2.2.1: Incoming Call Failure (message sequence chart), called subscriber does not answer. The diagram shows a sequence of messages between an IMS core node (CSCF, BGCF, TrGW), an MGCF, an IM-MGW, and a SIP-I based circuit-switched core network. The sequence starts with a message from the IMS core node to the MGCF. The MGCF sends a message to the IM-MGW. The IM-MGW sends a message to the SIP-I based circuit-switched core network. The SIP-I based circuit-switched core network sends a 480 Temporarily Unavailable message to the MGCF. The MGCF sends an ACK message to the IMS core node. The MGCF also sends a BYE [REL] message to the IM-MGW. The IM-MGW sends a 200 OK (BYE) [RLC] message to the MGCF. A timer T9 'awaiting answer' expires at the MGCF. A note indicates that for preceding signalling sequences see Figure 7.6.2.1.1. + +**Figure 7.6.2.2.1: Incoming Call Failure (message sequence chart), called subscriber does not answer** + +## 7.6.3 Outgoing Call flows + +The first two call flows show the signalling for a successful basic call establishment. The third call flow shows interworking when the call is forked within the IMS. + +### 7.6.3.1 Outgoing Call, Sending of INVITE is deferred + +Figure 7.6.3.1.1 shows an outgoing call where the preconditions are not met when the MGCF receives the initial SIP INVITE. The MGCF defers sending of INVITE until preconditions are met. The MGCF selects a codec and sends back 183 Progress. When the MGCF receives the SIP UPDATE request remote preconditions are met. + +When the MGCF sends the SIP INVITE request to the next IMS node, it does not request the support for preconditions. The selected codec is inserted as the first one within the list of offered codecs. Shown, as a network option, is the inclusion of the PSTN XML body, which is mapped from the previously received ISUP information. The MGCF offers the support for early media which is confirmed by the IMS node in the 183 progress. In this example, the answer does not authorise early media because in-band tones or announcements are not provided. + +When a 180 Ringing provisional response is received from the succeeding IMS the MGCF orders the IM-MGW to start sending the ringing tone before it propagates the 180 Ringing, which includes the ISUP ACM, to the preceding SIP-I based circuit-switched core network. + + + +The diagram illustrates the signaling flow for an outgoing call where the sending of the INVITE message is deferred until preconditions are met. The participants involved are a SIP-I based circuit-switched core network, an IM-MGW, an MGCF, and an IMS core node (CSCF, BGCF, TrGW). + +**Sequence of Events:** + +- The SIP-I based circuit-switched core network sends an **INVITE [SDP, IAM]** to the IM-MGW. +- The IM-MGW responds with **100rel, UPDATE, precondition tag 3gOoBTC, supported codec list**. A note indicates that **preconditions not met**. +- The IM-MGW sends a **100 TRYING** response back to the core network. +- A shaded box indicates **Seize incoming side RTP bearer terminations** at the IM-MGW. +- The IM-MGW sends a **183 Progress [SDP]** response. Details include: **100rel, UPDATE, preconditions 3gOoBTC, selected codec, available codecs**. A note indicates **local preconditions met**. +- The IM-MGW sends a **PRACK** response. +- The IM-MGW receives a **200 OK (PRACK)** response. +- The IM-MGW sends an **UPDATE [SDP]** message. A note indicates **preconditions are met**. +- The IM-MGW receives a **200 OK (UPDATE) [SDP]** response. A note indicates **local preconditions met**. +- A shaded box indicates **Seize outgoing side RTP bearer terminations** at the IM-MGW. +- At this point, a note indicates **IMS will not send inband ringing tone**. +- The IM-MGW sends a **Send Tone (Ringing)** message. +- The IM-MGW receives a **180 Ringing [ACM]** response. +- The IM-MGW sends a **PRACK** response. +- The IM-MGW receives a **200 OK (PRACK)** response. +- Simultaneously, the MGCF sends an **INVITE [SDP, PSTN XML]** to the IMS core node. Details include: **100rel, UPDATE, P-Early-Media, IMS codec list (selected codec, ...), PSTN XML**. +- The IMS core node responds with **100 TRYING**. +- The IMS core node sends a **183 Progress [SDP]** response. Details include: **100rel, UPDATE, selected codec**. +- The IMS core node receives a **PRACK [SDP]** response. +- The IMS core node receives a **200 OK (PRACK) [SDP]** response. +- The IMS core node sends a **180 Ringing** message. +- The IMS core node receives a **200 OK (INVITE)** response. +- A shaded box indicates **Stop Tone (Ringing)** at the IM-MGW. +- The IM-MGW receives a **200 OK (INVITE) [ANM]** response. +- The IM-MGW sends an **ACK** response. +- The MGCF receives an **ACK** response from the IMS core node. + +Sequence diagram for Outgoing Call with deferred INVITE until preconditions are met. + +Figure 7.6.3.1.1: Outgoing Call, sending of INVITE is deferred until preconditions are met + +### 7.6.3.2 Outgoing Call, Sending of INVITE is not deferred + +Figure 7.6.3.2.1 shows an outgoing call where the preconditions are not met when the MGCF receives the initial SIP INVITE. When the MGCF sends the SIP INVITE request to the next IMS node before preconditions are fulfilled, it requests the support for preconditions. + +Support for preconditions is confirmed from the IMS node. The MGCF receives more than one codec in the 183 Progress from the external node. Therefore the MGCF selects one of the received codecs and makes a second SDP offer to the external node in the SIP PRACK request in order to lock the codec. + +When the MGCF receives from the incoming side an UPDATE message indicating that preconditions are fulfilled, it propagates the UPDATE message towards the IMS. + +When a 180 Ringing provisional response is received from the succeeding IMS the MGCF orders the IM-MGW to start sending the ringing tone before it propagates the 180 Ringing, which includes the ISUP ACM, to the preceding SIP-I based circuit-switched core network. + + + +The sequence diagram illustrates the call flow for an outgoing call where the INVITE is not deferred. The participants are: + + +- SIP-I based circuit-switched core network** (left) +- IM-MGW** (Intermediate Media Gateway) +- MGCF** (Media Gateway Control Function) +- IMS core node (CSCF, BGCF, TrGW)** (right) + + The sequence of messages is as follows: + + +- The SIP-I network sends an **INVITE [SDP, IAM]** to the IM-MGW. +- The IM-MGW responds with **100rel, UPDATE**, indicating that preconditions are not met. +- The IM-MGW sends a **100 TRYING** response back to the SIP-I network. +- The IM-MGW sends a **Seize outgoing side RTP bearer terminations** message to the MGCF. The MGCF notes that preconditions are *not met*. +- The MGCF sends an **INVITE [SDP, PSTN XML]** to the IMS core node, including a precondition tag and P-Early-Media. +- The IMS core node responds with **100 TRYING**. +- The IMS core node sends a **183 Progress [SDP]** response. The IM-MGW notes that the IMS IETF codec is modified and local preconditions are met. A note indicates that the IMS will not send an inband ringing tone. +- The IM-MGW sends a **Seize incoming side RTP bearer terminations** message to the MGCF. +- The IM-MGW sends a **183 Progress [SDP]** response to the SIP-I network, indicating that local preconditions are met. +- The IM-MGW sends a **PRACK** message to the MGCF. +- The MGCF sends a **PRACK** message to the IMS core node. +- The IMS core node responds with **200 OK (PRACK)**. +- The IM-MGW sends a **200 OK (PRACK)** response to the SIP-I network. +- The IM-MGW sends an **UPDATE [SDP]** message to the MGCF. The MGCF notes that preconditions are met. +- The MGCF sends an **UPDATE [SDP]** message to the IMS core node, indicating that the selected codec and preconditions are met. +- The IMS core node responds with **200 OK (UPDATE) [SDP]**, indicating that local preconditions are met. +- The IM-MGW sends a **200 OK (UPDATE) [SDP]** response to the SIP-I network. +- The MGCF sends a **180 Ringing** message to the IMS core node. +- The IM-MGW sends a **Send Tone (Ringing)** message to the MGCF. +- The IM-MGW sends a **180 Ringing [ACM]** response to the SIP-I network. +- The IM-MGW sends a **PRACK** message to the MGCF. +- The IM-MGW sends a **200 OK (PRACK)** response to the SIP-I network. +- The IMS core node sends a **200 OK (INVITE)** response to the MGCF. +- The IM-MGW sends a **Stop Tone (Ringing)** message to the MGCF. +- The IM-MGW sends a **200 OK (INVITE) [ANM]** response to the SIP-I network. +- The IM-MGW sends an **ACK** message to the MGCF. +- The MGCF sends an **ACK** message to the IMS core node. + +Sequence diagram for Outgoing Call (Figure 7.6.3.2.1) showing interactions between SIP-I based circuit-switched core network, IM-MGW, MGCF, and IMS core node (CSCF, BGCF, TrGW). + +Figure 7.6.3.2.1: Outgoing Call, sending of INVITE is not deferred until preconditions are met + +### 7.6.3.3 Interworking with forked SIP INVITE Requests + +In this example, the SIP INVITE request is routed within the IMS to a forking proxy. Therefore the MGCF has to interwork with multiple early dialogues. This is shown in figures 7.6.3.3.1 and 7.6.3.3.2, where only those message contents are shown that are needed for the understanding of this call flow. + +When receiving the first 183 Session Progress within dialogue A, the handling is done as in the previous call flow example (figure 7.6.3.2.1). Afterwards the MGCF receives another 183 Session Progress but within a second dialogue + +B. In this example, the received codec list does not include the codec which is already selected for dialogue A. Therefore the MGCF can not directly send the selected codec to the succeeding IMS node within the second dialogue B. + +When the SIP UPDATE request is received, which indicates that preconditions are met, the MGCF sends two SIP UPDATE requests to the succeeding IMS node to signal within both dialogues that preconditions are met. + + + +``` + +sequenceDiagram + participant IMS_CSN as SIP-I based circuit-switched core network + participant IM_MGW as IM-MGW + participant MGCF as MGCF + participant IMS_Core as IMS core node (CSCF, BGCF, CS-IBCF) + + Note right of MGCF: Nc, Mn, Mj, Mg + + IMS_CSN->>IM_MGW: INVITE [SDP, IAM] +..... remote preconditions not met + IM_MGW-->>IMS_CSN: 100 Trying + IM_MGW->>MGCF: Seize outgoing side RTP bearer terminations + MGCF->>IMS_Core: INVITE [SDP] +....IMS codec list, preconditions not met, .... + IMS_Core-->>MGCF: 100 Trying + IMS_Core-->>MGCF: 183 Session Progress [SDP] +To: tag A, IMS codec list A, ..... + MGCF->>IM_MGW: Seize incoming side RTP bearer terminations + MGCF-->>IMS_Core: 183 Session Progress [SDP] +To: tag X +3gOoBTC, selected codec A, available +codecs XA + MGCF->>IMS_Core: PRACK +To: tag X + IMS_Core-->>MGCF: 200 OK (PRACK) [SDP] +To: tag A + MGCF-->>IMS_CSN: 200 OK (PRACK) +To: tag X + IMS_Core-->>MGCF: 183 Session Progress [SDP] +To: tag B, IMS codec list B, ..... + MGCF->>IMS_Core: PRACK +To: tag B + IMS_Core-->>MGCF: 200 OK (PRACK) +To: tag B + MGCF->>IMS_Core: UPDATE [SDP] +To: tag X, preconditions are met + IMS_Core-->>MGCF: UPDATE [SDP] +To: tag A, preconditions are met + IMS_Core-->>MGCF: UPDATE [SDP] +To: tag B, preconditions are met + IMS_Core-->>MGCF: 200 OK (UPDATE) [SDP] +To: tag A, local preconditions met + IMS_Core-->>MGCF: 200 OK (UPDATE) [SDP] +To: tag B, local preconditions met + MGCF-->>IMS_CSN: 200 OK (UPDATE) [SDP] +To: tag X, local preconditions met + +``` + +Sequence diagram for Outgoing Call, multiple early dialogues. The diagram shows the interaction between an SIP-I based circuit-switched core network (via IM-MGW), an MGCF, and an IMS core node (CSCF, BGCF, CS-IBCF). The MGCF initiates two dialogues, A and B, with the IMS core node. Dialogue A is established first, followed by Dialogue B. The MGCF sends SIP INVITE, 100 Trying, 183 Session Progress, PRACK, 200 OK (PRACK), UPDATE, and 200 OK (UPDATE) messages. The IM-MGW performs RTP bearer terminations (seize outgoing and incoming) during the call setup. + +Figure 7.6.3.3.1: Outgoing Call, multiple early dialogues + +Figure 7.6.3.3.2 shows that only the first 180 Ringing received from the IMS node is interworked with the SIP-I based circuit-switched core network. + +Finally, the SIP INVITE request is answered with a 200 OK within dialogue B. + +Any subsequent final response within dialogue A is acknowledged (with an ACK request) and immediately rejected by sending back a SIP BYE request. + + + +The diagram illustrates the signaling sequence for an outgoing call involving multiple early dialogues (A and B) between an SIP-I based circuit-switched core network and an IMS core node, mediated by an IM-MGW and an MGCF. + +**Participants:** + +- SIP-I based circuit-switched core network (via IM-MGW) +- MGCF +- IMS core node (CSCF, BGCF, CS-IBCF) + +**Interfaces:** + +- IM-MGW to MGCF: Nc, Mn +- MGCF to IMS core node: Mj, Mg + +**Sequence of Events:** + +- The IMS core node sends a **180 Ringing** (To: tag B) to the MGCF. +- The MGCF sends a **Send Tone (Ringing)** message to the IM-MGW. +- The IM-MGW sends a **180 Ringing [ACM]** (To: tag X) to the SIP-I based circuit-switched core network. +- The SIP-I based circuit-switched core network sends a **PRACK** (To: tag X) to the IM-MGW. +- The IM-MGW sends a **200 OK (PRACK)** (To: tag X) to the MGCF. +- The MGCF sends a **PRACK** (To: tag B) to the IMS core node. +- The IMS core node sends a **200 OK (PRACK)** (To: tag B) to the MGCF. +- The IMS core node then sends a **180 Ringing** (To: tag A) to the MGCF. +- The MGCF sends a **PRACK** (To: tag A) to the IMS core node. +- The IMS core node sends a **200 OK (PRACK)** (To: tag A) to the MGCF. +- The IMS core node sends a **200 OK (INVITE)** (To: tag B) to the MGCF. +- The MGCF sends an **ACK** (To: tag B) to the IMS core node. +- The IMS core node sends a **200 OK (INVITE)** (To: tag A) to the MGCF. +- The MGCF sends an **ACK** (To: tag A) to the IMS core node. +- The IMS core node sends a **BYE** (To: tag A) to the MGCF. +- The MGCF sends a **200 OK (BYE)** (To: tag A) to the IMS core node. +- Meanwhile, the MGCF sends an **INVITE [SDP]** (To: tag X, 3gOoBTC, selected codec XB, available codecs XB) to the IM-MGW. +- The IM-MGW sends a **200 OK (INVITE) [SDP]** (To: tag X) to the MGCF. +- The MGCF sends an **ACK** (To: tag X) to the IM-MGW. + +**Notes:** + +- For preceding signalling sequences see Figure 7.6.3.3.1 +- if second 200 OK response is received (referring to dialogue A) +- If received codec list for established dialogue did not include the previous selected codec A (referring to dialogue A) + +Sequence diagram for Outgoing Call, multiple early dialogues. The diagram shows signaling between an SIP-I based circuit-switched core network (via IM-MGW), an MGCF, and an IMS core node (CSCF, BGCF, CS-IBCF). It details two dialogues, A and B, showing 180 Ringing, PRACK, 200 OK, ACK, and BYE messages. A note indicates that only the first 180 Ringing for dialogue B is sent to the circuit-switched network. Another note explains that if a second 200 OK is received for dialogue A, a BYE is sent. A third note indicates that if the received codec list for dialogue A did not include the previous selected codec A, the sequence continues as shown. + +Figure 7.6.3.3.2: Outgoing Call, multiple early dialogues (continuation of figure 7.6.3.3.1) + +## 7.7 CS CN Supplementary Services and IMS Supplementary Services + +### 7.7.0 General + +The following clauses describe the MGCF behaviour when: + +- Supplementary services are invoked within the SIP-I based circuit switched core network and +- Supplementary services are invoked within the IMS. + +The support of these supplementary services is optional. If the supplementary services are supported, the procedures described within this clause shall be applied. + +Within the SIP-I based circuit switched core network: + +- Service information is carried within encapsulated ISUP messages. +- The procedures specified for the ISUP side in TS 29.163 [13] clauses 7.4 and 7.5 shall be applied to the encapsulated ISUP. + +### 7.7.1 Number Identification Services + +#### 7.7.1.1 CS CN Supplementary Service - Calling Line Identification Presentation/Restriction (CLIP/CLIR) + +There is no additional interworking beyond clauses 7.2 and 7.3 when the Calling Line Identification Presentation or a Calling Line Identification Restriction supplementary service is invoked within the SIP-I based circuit switched core network. + +#### 7.7.1.2 CS CN Supplementary Service - Connected Line Identification Presentation/Restriction (COLP/COLR) + +When the Connected Line Identification Presentation or Connected Line Identification Restriction supplementary service is invoked within the SIP-I based circuit switched core network, the MGCF shall perform the mapping to the Terminating Identification Presentation / Restriction service as specified in TS 29.163 [13] clause 7.5.2. + +#### 7.7.1.3 IMS Supplementary Service - Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) + +There is no additional interworking beyond clauses 7.2 and 7.3, when the Originating Identification Presentation or Originating Identification Restriction supplementary service is invoked within the IMS network. + +#### 7.7.1.4 IMS Supplementary Service - Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR) + +When the Terminating Identification Presentation or Terminating Identification Restriction supplementary service is invoked within the IMS network, the MGCF shall perform the mapping to the Connected Line Identification Presentation / Restriction supplementary service as specified in TS 29.163 [13] clause 7.5.2. + +#### 7.7.1.5 CS CN Supplementary Service - Direct Dialling In + +There is no additional interworking beyond clauses 7.2 and 7.3, when the Direct Dialling In supplementary service is invoked within the SIP-I based circuit switched core network. + +#### 7.7.1.6 CS CN Supplementary Service - Malicious Call Identification + +When the Malicious Call Identification supplementary service is invoked within the SIP-I based circuit switched core network the MGCF shall perform the mapping as specified in TS 29.163 [13] clause 7.5.9. + +### 7.7.1.7 IMS Supplementary Service - Malicious Communication Identification (MCID) + +When Malicious Communication Identification service is invoked within the IMS network, then as specified in TS 29.163 [13] clause 7.5.9.2, the interworking to the Malicious Call Identification supplementary service shall not be applied. + +### 7.7.1.8 CS CN Supplementary Service - Subaddressing + +When the Subaddressing supplementary service is invoked within the SIP-I based circuit switched core network, the procedures specified in TS 29.163 [13] clause 7.4.5 shall be applied. + +## 7.7.2 Diversion Services + +### 7.7.2.1 CS CN Supplementary Service - Call Forwarding Services (CFU, CFB, CFNRy, CFNRc) + +When any of the call forwarding supplementary services (CFU, CFB, CFNRy, and CFNRc) is invoked within the SIP-I based circuit switched core network, the MGCF shall perform the mapping to the Communication Diversion service as specified in TS 29.163 [13] clauses 7.5.4.2.2 and 7.5.4.3. + +### 7.7.2.2 CS CN Supplementary Service - Call Deflection (CD) + +When the Call Deflection supplementary service is invoked within the SIP-I based circuit switched core network the MGCF shall perform the mapping to the Communication Diversion service as specified in TS 29.163 [13] clauses 7.5.4.2.2 and 7.5.4.3. + +### 7.7.2.3 IMS Supplementary Service - Communication Diversion (CDIV) + +When a Communication Diversion supplementary service is invoked within the IMS network, the MGCF shall perform the mapping to a Call Diversion supplementary service as specified in TS 29.163 [13] clauses 7.5.4.2.1 and 7.5.4.3. + +## 7.7.3 Waiting Services + +### 7.7.3.1 CS CN Supplementary Service - Call Waiting + +When the Call Waiting supplementary service is invoked within the SIP-I based circuit switched core network, the MGCF shall perform the mapping to the Communication Waiting service as specified in TS 29.163 [13] clause 7.5.12.1. + +### 7.7.3.2 IMS Supplementary Service - Communication Waiting (CW) + +When the Communication Waiting supplementary service is invoked within the IMS network, the MGCF shall perform the mapping to the Call Waiting supplementary service as specified in TS 29.163 [13] clause 7.5.12.2. + +## 7.7.4 Hold Services + +### 7.7.4.1 CS CN Supplementary Service - Call Hold + +There is no additional interworking beyond clauses 7.2 and 7.3, when the Call Hold supplementary service is invoked within the SIP-I based circuit switched core network. + +### 7.7.4.2 IMS Supplementary Service - Communication Hold (HOLD) + +There is no additional interworking beyond clauses 7.2 and 7.3, when the Communication Hold supplementary service is invoked within the IMS network. + +NOTE: Call hold for IMS is specified in TS 24.610 [26]. + +## 7.7.5 Multiparty Services + +### 7.7.5.1 CS CN Supplementary Services - Conference Calling (CONF) and Three-Party (3PTY) + +When the Conference Calling and Three-Party supplementary services are invoked within the SIP-I based circuit switched core network, the procedures specified in TS 29.163 [13] clause 7.4.14 shall be applied. + +### 7.7.5.2 IMS Supplementary Service - Conference (CONF) + +When the Conference supplementary service is invoked within the IMS network, the procedures specified in TS 29.163 [13] clause 7.5.6 shall be applied. + +## 7.7.6 Closed User Group Service + +### 7.7.6.1 CS CN Supplementary Service - Closed User Group (CUG) + +When the Closed User Group supplementary service is invoked within the SIP-I based circuit switched core network, the procedures specified in TS 29.163 [13] clause 7.5.10.2 shall be applied. + +### 7.7.6.2 IMS Supplementary Service - Closed User Group (CUG) + +When the Closed User Group supplementary service is invoked within the IMS network, the procedures specified in TS 29.163 [13] clause 7.5.10.1 shall be applied. + +## 7.7.7 Charging Services + +### 7.7.7.1 CS CN Supplementary Service - Advice of Charge (AoC) + +NOTE: Interworking for AoC is not specified in the present Release. + +### 7.7.7.2 IMS Supplementary Service - Advice of Charge (AOC) + +NOTE: Interworking for AOC is not specified in the present Release. + +### 7.7.7.3 CS CN Supplementary Service - International Telecommunication Charge Card (ITCC) + +When the International Telecommunication Charge Card supplementary service is invoked within the SIP-I based circuit switched core network no additional treatment is required by the MGCF. + +### 7.7.7.4 CS CN Supplementary Service - Reverse Charging (REV) + +When the Reverse Charging supplementary service is invoked within the SIP-I based circuit switched core network, the procedures specified in TS 29.163 [13] clause 7.4.17 shall be applied. + +## 7.7.8 Barring Services + +### 7.7.8.1 CS CN Supplementary Service - Barring of Outgoing Calls + +There is no additional interworking beyond clauses 7.2 and 7.3, when the Barring of Outgoing Call supplementary service is invoked within the SIP-I based circuit switched core network. + +### 7.7.8.2 CS CN Supplementary Service - Barring of Incoming Calls + +There is no additional interworking beyond clauses 7.2 and 7.3, when the Barring of Incoming Calls supplementary service is invoked within the SIP-I based circuit switched core network. + +### 7.7.8.3 CS CN Supplementary Service - Anonymous Call Rejection (ACR) + +When the Anonymous Call Rejection supplementary service is invoked within the SIP-I based circuit switched core network, the procedures specified in TS 29.163 [13] clause 7.4.23.1 shall be applied. + +#### 7.7.8.4 IMS Supplementary Service - Communication Barring (CB) + +NOTE: Interworking of Communication Barring is not specified in the present Release. + +#### 7.7.8.5 IMS Supplementary Service - Anonymous Communication Rejection (ACR) + +When the Anonymous Communication Rejection supplementary service is invoked within the IMS network, the procedures specified in TS 29.163 [13] clause 7.4.23.2 shall be followed with the following modifications at the SIP-I on Nc side: + +- The response code 433 (Anonymity Disallowed) defined by IETF RFC 5079 [36] is supported on SIP-I on Nc. + +### 7.7.9 Transfer Services + +#### 7.7.9.1 CS CN Supplementary Service - Explicit Call Transfer (ECT) + +When the Explicit Call Transfer supplementary service is invoked within the SIP-I based circuit switched core network and the MGCF receives from the SIP-I based circuit-switched core network an INFO message with encapsulated ISUP FAC for the notification of ECT invocation, then the MGCF shall: + +- map the FAC into a SIP re-INVITE request or SIP UPDATE request according to TS 29.163 [13] if the call is in active state (after answer). +- map the FAC into a SIP UPDATE request according to TS 29.163 [13] if the call is in active state (before answer). + +#### 7.7.9.2 IMS Supplementary Service - Explicit CommunicationTransfer (ECT) + +When the Explicit CommunicationTransfer supplementary service is invoked within the IMS network and if the transferee is another IMS terminal and the transfer target is a CS terminal, then the MGCF will receive a SIP INVITE request. No special interworking is required at the MGCF. + +NOTE: The protocol for ECT within IMS is specified in TS 24.629 [25]. The IMS terminal, which invokes the ECT service, sends a SIP REFER request to the transferee. The transferee sends a SIP INVITE request to the transfer target. + +### 7.7.10 Call Completion Services + +#### 7.7.10.1 CS CN Supplementary Service - Completion of Calls to Busy Subscriber (CCBS) + +When the Completion of Calls to Busy Subscriber supplementary service is invoked within the SIP-I based circuit switched core network, the procedures specified in TS 29.163 [13] clause 7.4.11 shall be applied. + +#### 7.7.10.2 CS CN Supplementary Service - Completion of Calls on No Reply (CCNR) + +When the Completion of Calls on No Reply supplementary service is invoked within the SIP-I based circuit switched core network, the procedures specified in TS 29.163 [13] clause 7.4.12 shall be applied. + +#### 7.7.10.3 IMS Supplementary Service - Completion of Communications to Busy Subscriber (CCBS) and Completion of Communication on No Reply (CCNR) + +When the Completion of Communications to Busy Subscriber or Completion of Communication on No Reply supplementary service is invoked within the IMS network, the procedures specified in TS 29.163 [13] clause 7.5.11.1 shall be applied. + +### 7.7.11 Miscellaneous Services + +#### 7.7.11.1 CS CN Supplementary Service - Multi-Level Precedence and Pre-emption (MLPP) + +When the Multi-Level Precedence and Pre-emption (MLPP) supplementary service is invoked within the SIP-I based circuit switched core network the procedures specified in TS 29.163 [13] clause 7.4.17 shall be applied. + +#### 7.7.11.2 CS CN Supplementary Service - Multiple Subscriber Profile (MSP) + +There is no additional interworking beyond clauses 7.2 and 7.3 when a Multiple Subscriber Profile supplementary service is invoked within the SIP-I based circuit switched core network. + +#### 7.7.11.3 CS CN Supplementary Service - Multicall + +There is no additional interworking beyond clauses 7.2 and 7.3 when the Multicall supplementary service is invoked within the SIP-I based circuit switched core network. + +#### 7.7.11.4 CS CN Supplementary Service - Calling Name Presentation + +There is no additional interworking beyond clauses 7.2 and 7.3, when the Calling Name Presentation supplementary service is invoked within the SIP-I based circuit switched core network. + +#### 7.7.11.5 CS CN Supplementary Service - User-to-User Signalling (UUS) + +NOTE: Interworking for User-to-User Signalling is not specified in the present Release. + +#### 7.7.11.6 IMS Supplementary Service - Message Waiting Indication (MWI) + +NOTE: Interworking for Message Waiting Indication is not specified in the present Release. + +#### 7.7.11.7 CS CN Supplementary Service - Global Virtual Network Service (GVNS) + +When the Global Virtual Network Service supplementary service is invoked within the SIP-I based circuit switched core network the procedures specified in TS 29.163 [13] clause 7.4.18 shall be applied. + +#### 7.7.11.8 CS CN Supplementary Service - Terminal Portability (TP) + +When the Terminal Portability supplementary service is invoked within the SIP-I based circuit switched core network, the procedures specified in TS 29.163 [13] clause 7.4.13 shall be applied. + +### 7.7.12 Customized Alerting Tones Services + +#### 7.7.12.1 CS CN Supplementary Service - Customized Alerting Tones (CAT) + +When the Customized Alerting Tones supplementary service is invoked within the SIP-I based circuit switched core network, the MGCF shall perform the mapping as specified in TS 29.163 [13] clause 7.4.24. + +#### 7.7.12.2 IMS Supplementary Service - Customized Alerting Tones (CAT) for early session model + +When the Customized Alerting Tones supplementary service is invoked within the IMS network using early session model, the MGCF shall perform the mapping for normal session SDP negotiation and early session SDP negotiation as specified in TS 29.163 [13] clause 7.5.13.2. + +#### 7.7.12.3 IMS Supplementary Service - Customized Alerting Tones (CAT) for forking model + +When the Customized Alerting Tones supplementary service is invoked within the IMS network using forking model, the MGCF shall perform the mapping as specified in TS 29.163 [13] clause 7.5.13.3. + +#### 7.7.12.4 IMS Supplementary Service - Customized Alerting Tones (CAT) for gateway model + +When the Customized Alerting Tones supplementary service is invoked within the IMS network using gateway model, the MGCF shall perform the mapping as specified in TS 29.163 [13] clause 7.5.13.4. + +## 7.8 MGCF - IM-MGW Interaction + +### 7.8.1 General + +The present clause describes signalling procedures that are applicable at the Mn interface when the MGCF and attached IM-MGW interwork between an IM CN Subsystem and a SIP-I based circuit-switched core network. + +The MGCF shall interact with the IM-MGW across the Mn reference point. The signalling interface across the Mn reference point is defined in accordance with ITU-T Recommendation H.248.1 [53] and shall conform to 3GPP specific extensions as detailed in TS 29.332 [54]. + +### 7.8.2 Call related Procedures for Terminations towards the IM CN Subsystem + +Clause 9.3.1 in TS 29.163 [13] shall apply. + +### 7.8.3 Call related Procedures for Terminations towards SIP-I based Circuit-switched Core Network + +Those procedures defined in TS 23.205 [9] that are listed in table 7.8.3.1 shall apply. + +**Table 7.8.3.1: Call related Procedures defined in TS 23.205 [9] that are applicable at terminations towards SIP-I based circuit-switched core network** + +| Procedure defined in TS 23.205 [9] | Remarks | +|--------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Change Flow Direction | NOTE 1 in that clause is replaced by:
NOTE 1: This procedure may be combined with the "Reserve RTP Connection Point" procedure, the "Configure RTP Connection Point" procedure, or the "Reserve and Configure RTP Connection Point" procedure. | +| Change Through-Connection | The NOTE in that clause is replaced by:
NOTE 2: This procedure may be combined with the "Reserve RTP Connection Point" procedure, the "Configure RTP Connection Point" procedure, or the "Reserve and Configure RTP Connection Point" procedure. | +| Bearer Released | | +| Release Termination | | +| Send Tone | | +| Stop Tone | | +| Play Announcement | Optional | +| Stop Announcement | Optional | +| Announcement Completed | Optional | +| Tone Completed | | +| Activate Voice Processing Function | Optional | +| Termination heartbeat indication | | +| Reserve RTP Connection Point | | +| Configure RTP Connection Point | | +| Reserve and Configure RTP Connection Point | | + +### 7.8.4 Non-call related procedures + +Clause 9.3.4 in TS 29.163 [13] shall apply. + +--- + +# Annex A (normative): Interconnecting functionalities in SIP-I based CS domain + +## A.1 General + +This annex describes a collection of functions that can be performed on interconnection boundaries between two SIP-I based 3GPP CS networks or between a SIP-I based CS network and other SIP-I based external network, based on operator configuration. + +In clauses A.2 and A.3 Stage 2 requirements and border control architecture are described. + +--- + +## A.2 Stage 2 Requirements + +Based on operator preference, border control functions may be applied between two SIP-I based 3GPP CS domains or between a SIP-I based 3GPP CS domain and other SIP-I based external network. These functions, provided by the CS-IBCF, are: + +- Controlling transport plane functions; +- Supporting functions to allow establishing communication between disparate address realms' SIP-I applications; +- Providing network configuration hiding to restrict the following information from being passed outside of an operator's network: exact number of MSC servers, capacity and topology of the network, naming and addressing of the network nodes; +- Screening SIP signalling information based on source/destination and operator policy (e.g. remove information that is of local significance to an operator); +- Selecting the appropriate signalling interconnections (e.g. domain based routing). The IP interconnection between core networks may be supported either by direct connection or by using an intermediate carrier; +- Supporting network resources allocation taking into consideration the codec negotiation performed by (G)MSCs across one or multiple interconnects, remaining transparent to the SDP negotiation. + +In case border control concepts are to be applied in a SIP-I based CS network, the CS-IBCF acts as an entry point for this network, and also acts as an exit point for this network. + +On the media plane the following functions shall be supported by the CS-TrGW: + +- Gate Management: + - Opening/closing of gates; + - Remote source address filtering; + - Remote source port filtering; +- QoS packet marking (differentiated services); +- NA(P)T and IP Version Interworking; +- Bandwidth policing; +- Hanging termination detection; +- IP Realm Indication. + +Additionally, the following functions may be supported by the CS-TrGW: + +- IP Realm Availability. + +## A.3 Border Control architecture + +Figure A.3.1 presents a high-level architecture diagram showing how CS-IBCF and CS-TrGW logical functions fit into the SIP-I based CS domain. + + + +Figure A.3.1: CS-IBCF and CS-TrGW in SIP-I based CS domain. The diagram shows a network architecture with three main components: IWU, UP-IWU, and a 'border control logical functions' block. The IWU is connected to the UP-IWU via an Mc reference point. The UP-IWU is connected to the 'border control logical functions' block via a Media/RTP/UDP/IP bearer. The 'border control logical functions' block contains two sub-functions: CS-IBCF (which includes ALG and THIG) and CS-TrGW. The CS-IBCF is connected to the UP-IWU via a SIP-I signalling path. The CS-TrGW is connected to the UP-IWU via a CS-Ix signalling path. The 'border control logical functions' block is connected to a 'SIP-I based 3GPP CS domain/External SIP-I Network' via a dashed line representing a bearer path. A legend indicates that dashed lines represent Signalling and solid lines represent Bearer. + +Figure A.3.1: CS-IBCF and CS-TrGW in SIP-I based CS domain + +The CS-IBCF, which provides border control functions, shall be transparent to the call control application of the adjacent 3GPP SIP-I nodes. That is, outgoing SIP-I messages from a 3GPP MSC-IWU shall assume that it is signalling to an external network. The CS-IBCF shall not perform SIP-I profile interworking functions that are defined by the main text of this specification. The CS-IBCF is a logical function that either is co-located with IWU in a single physical (G)MSC-S node, or is within a separate physical node, e.g. when co-locating with IMS-IBCF. + +The Nb reference point allows CS-MGWs to communicate with a CS-TrGW in order to provide border control functions. The CS-TrGW is a logical function that may reside in the UP-IWU. The CS-TrGW, which provides border control functions, shall be transparent to adjacent 3GPP MGWs. The CS-TrGW shall not perform any SIP-I user plane interworking functions that are defined by the main text of this specification. The CS-TrGW is a logical function that can be co-located with UP-IWU in a single physical CS-MGW node, but can also be in a separate physical node, e.g. when co-locating with IMS-TrGW. + +If the logical functions are co-located with (G)MSC and CS-MGW then the Mc profile as defined by TS 29.232 [55] shall provide the required functionality (described in clause A.8). If CS-IBCF is physically separated then the CS-IBCF control function is connected to the CS-TrGW via the CS-Ix reference point (described in clause A.7), which is realised by the Ix profile as defined by TS 29.238 [29]. + +## A.4 Void + +## A.5 Procedures at the CS-IBCF + +### A.5.1 General + +Border control functions may be applied between two SIP-I based CS domains subsystems or between an SIP-I based CS domains and other SIP-I based networks based on operator preference. The CS-IBCF may act both as an entry point and as an exit point for a network. If it processes a SIP request received from other network it functions as an entry point (see clause A.5.3) and it acts as an exit point whenever it processes a SIP request sent to other network (see clause A.5.2). + +Depending on its rule, the functions of the CS-IBCF include: + +- network configuration hiding (described in clauses A.5.2.4 and A.5.3.4); + +- application level gateway (in clauses A.5.2.5 and A.5.3.5); +- screening of SIP signalling (in clauses A.5.2.6 and A.5.3.6); +- charging (in clauses A.5.2.7 and A.5.3.7). + +NOTE: The functions performed by the CS-IBCF are configured by the operator, and they are network specific. + +## A.5.2 CS-IBCF as an exit point + +### A.5.2.1 Initial requests + +Upon receipt of any request, the CS-IBCF shall: + +- 1) if the request is an INVITE request, respond with a 100 (Trying) provisional response; +- 2) if the request is an INVITE request and the CS-IBCF is configured to perform application level gateway and/or transport plane control functionalities, save the Contact, CSeq, From and Record-Route header field values received in the request such that the CS-IBCF is able to release the session if needed; +- 3) if network topology hiding is required, apply the procedures as described in clause A.5.2.4; +- 4) if screening of SIP signalling is required, apply the procedures as described in clause A.5.2.6; +- 5) select an entry point of the destination network and forward the request to that entry point; + +NOTE: The list of the entry points can be either obtained as specified in IETF RFC 3263 [30] or provisioned in the CS-IBCF. The entry point can be a CS-IBCF or an (G)MSC server. + +When the CS-IBCF receives an INVITE request, the CS-IBCF may require the periodic refreshment of the session to avoid hung states in the CS-IBCF. If the CS-IBCF requires the session to be refreshed, the CS-IBCF shall apply the procedures described in IETF RFC 4028 [31] clause 8. + +IETF RFC 3325 [32] provides for the existence and trust of an asserted identity within a trust domain. A CS-IBCF at the boundary of the trust domain will need to determine whether to remove the P-Asserted-Identity header according to IETF RFC 3325 [32] when SIP signalling crosses the boundary of the trust domain. + +When the CS-IBCF receives a response to the initial request and network topology hiding is required, then the CS-IBCF shall apply the procedures as described in clause A.5.2.4. + +When the CS-IBCF receives a response to the initial request and screening of SIP signalling is applied, then the CS-IBCF shall apply the procedures as described in clause A.5.2.6. + +When the CS-IBCF receives a response to the initial INVITE request that establishes a dialogue, and the CS-IBCF is configured to perform application level gateway and/or transport plane control functions, the CS-IBCF shall save the Contact, To and Record-Route header field values received in the response such that the CS-IBCF is able to release the session if needed. + +### A.5.2.2 Subsequent requests + +Upon receipt of any request, the CS-IBCF shall: + +- 1) if the request is an INVITE request, respond with a 100 (Trying) provisional response; +- 2) if the request is a target refresh request and the CS-IBCF is configured to perform application level gateway and/or transport plane control functions, save the Contact and CSeq header field values received in the request such that the CS-IBCF is able to release the session if needed; +- 3) if the subsequent request is other than a target refresh request (including requests relating to an existing dialogue where the method is unknown) and the CS-IBCF is configured to perform application level gateway and/or transport plane control functionalities, save the Contact and CSeq header field values received in the request such that the CS-IBCF is able to release the session if needed; +- 4) if network topology hiding is required, apply the procedures as described in clause A.5.2.4; + +- 5) if screening of SIP signalling is required, apply the procedures as described in clause A.5.2.6. + +When the CS-IBCF receives a response to the subsequent request and network topology hiding is required, then the CS-IBCF shall apply the procedures as described in clause A.5.2.4. + +When the CS-IBCF receives a response to the subsequent request and screening of SIP signalling is required, then the CS-IBCF shall apply the procedures as described in clause A.5.2.6. + +### A.5.2.3 CS-IBCF-initiated call release + +If the CS-IBCF provides transport plane control functionality and receives an indication of a transport plane related error the CS-IBCF may: + +- 1) if the CS-IBCF has already sent an initial INVITE request to the terminating side, apply SIP procedures detailed in IETF RFC 3261 [20] to terminate any corresponding SIP dialogue(s) or otherwise cancel the INVITE at the terminating side, making use of CANCEL and/or BYE request(s), based on information saved for the related dialogue; and +- 2) if the CS-IBCF has not yet sent out a final response for the initial INVITE request, send an appropriate failure response for the initial INVITE request to the originating side; and +- 3) if the CS-IBCF has already sent out a final response for the initial INVITE request, generate a BYE request for the originating side based on the information saved for the related dialogue. + +NOTE 1: Transport plane related errors can be indicated from TrGW. + +NOTE 2: Since the CS-IBCF does not handle the encapsulated ISUP, the BYE message(s) generated by the CS-IBCF will not contain any encapsulated ISUP REL message. + +If the CS-IBCF is able to determine an appropriate Q.850 cause value, then this may be included in a Reason header in the BYE message(s). + +### A.5.2.4 THIG functionality in the CS-IBCF + +#### A.5.2.4.1 General + +The following procedures shall only be applied if network topology hiding is required by the network. The network requiring network topology hiding is called the hiding network. + +NOTE 1: Requests and responses are handled independently; therefore, no state information is needed for that purpose within a CS-IBCF. + +The CS-IBCF shall apply network topology hiding to all headers which reveal topology information, such as Via, Route, Record-Route, and Path. Therefore, the CS-IBCF shall: + +- either act as a B2BUA, i.e. set above headers as defined for a SIP user agent client by IETF RFC 3261 [20], +- or as an option follow the procedures defined in clause A.5.2.4.2. + +The CS-IBCF shall not screen SIP parameters for which there is a related ISUP parameter defined within ITU-T Recommendation Q.1912.5 [6]. + +NOTE 2: SIP-I screening is normally done by the MSC, where the encapsulated ISUP message and the SIP headers are consistently screened. + +Upon receiving an incoming initial request for which network topology hiding has to be applied and which includes a Record-Route header, the CS-IBCF shall add its own routable SIP URI to the top of the Record-Route header. + +#### A.5.2.4.2 Encryption for network topology hiding + +Upon receiving a request/response, outgoing from the hiding network the CS-IBCF shall perform the encryption for network topology hiding purposes, i.e. the CS-IBCF shall: + +- 1) use the whole header values which were added by one or more specific entity of the hiding network as input to encryption; + +- 2) not change the order of the headers subject to encryption when performing encryption; +- 3) use for one encrypted string all received consecutive header entries subject to encryption, regardless if they appear in separate consecutive headers or if they are consecutive entries in a comma separated list in one header; +- 4) construct a hostname that is the encrypted string; +- 5) append a "tokenized-by" parameter and set it to the value of the encrypting network's name, after the constructed hostname; +- 6) form one valid entry for the specific header out of the resulting NAI, e.g. prepend "SIP/2.0/UDP" for Via headers or "sip:" for Path, Route and Record-Route headers; +- 7) if the CS-IBCF encrypted an entry in the Route header, then it also inserts its own URI before the topmost encrypted entry; and +- 8) if the CS-IBCF encrypted an entry in the Via header, then it also inserts its own URI before the topmost encrypted entry. + +NOTE: Even if consecutive entries of the same network in a specific header are encrypted, they will result in only one encrypted header entry. For example: + +``` +Via: SIP/2.0/UDP ibcf1.home1.net;lr, + SIP/2.0/UDP Token( SIP/2.0/UDP msc2.home1.net;lr, + SIP/2.0/UDP msc1.home1.net;lr); + tokenized-by=home1.net, + SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd] +``` + +## A.5.2.5 ALG functionality in the CS-IBCF + +The CS-IBCF shall only apply the following procedures if application level gateway functionality is required by the network. + +The CS-IBCF acts as a B2BUA when it performs ALG functionality. The CS-IBCF, although acting as a UA, does not initiate any registration of its associated addresses. These are assumed to be known by peer-to-peer arrangements within the SIP-I based CS domain. + +In case the initial INVITE request is received from own network, i.e. the CS-IBCF acts as an exit point, the CS-IBCF shall generate a new initial INVITE request and forward it to the entry point of the other network. + +The internal function of the CS-IBCF as an ALG is equal to that one defined in TS 29.162 [37]. + +## A.5.2.6 Screening of SIP-I signalling + +### A.5.2.6.1 General + +This section relates to the screening of the SIP headers and SDP of the SIP-I signalling for policing purposes. Inspection of ISUP MIME bodies is out of the scope of this specification. + +The CS-IBCF shall act as a B2BUA when it performs screening of SIP signalling functionality. In this case the B2BUA behaviour of the CS-IBCF shall comply with the description given in clause A.5.2.5 for the ALG functionality. + +NOTE 1: Many headers are intended for end-to-end operation; removal of such headers will impact the intended end-to-end operation between nodes. Additionally security mechanisms covering SIP headers are not precluded; any such removal can prevent validation of all headers covered by the security mechanism. + +NOTE 2: SIP-I screening is normally done by the MSC, where the encapsulated ISUP message and the SIP headers are consistently screened. + +### A.5.2.6.2 CS-IBCF procedures for SIP headers + +If specified by local policy rules, the CS-IBCF may omit or modify any received SIP headers prior to forwarding SIP messages, with some exceptions. + +NOTE 1: If the CS-IBCF modifies SIP information elements (SIP headers, SIP message bodies) other than as specified by SIP procedures (e.g., IETF RFC 3261 [20]) caution needs to be taken that SIP functionality (e.g., routing using Route, Record-Route and Via) is not impacted in a way that could create interoperability problems with networks that assume that this information is not modified. + +NOTE 2: Where operator requirements can be achieved by configuration hiding, then these procedures can be used in preference to screening. + +#### A.5.2.6.3 CS-IBCF procedures for SIP message bodies + +If IP address translation (NA(P)T or IP version interworking) occurs on the user plane, the CS-IBCF shall modify SDP according to TS 29.162 [37]. + +#### A.5.2.7 Void + +### A.5.3 CS-IBCF as an entry point + +#### A.5.3.1 Initial requests + +Upon receipt of any request, the CS-IBCF shall: + +- 1) if the request is an INVITE request, then respond with a 100 (Trying) provisional response; +- 2) if the request is an INVITE request and the CS-IBCF is configured to perform application level gateway and/or transport plane control functions, save the Contact, Cseq, From and Record-Route header field values received in the request such that the CS-IBCF is able to release the session if needed; +- 3) if network topology hiding is required, then apply the procedures as described in clause A.5.3.4; +- 4) if screening of SIP signalling is required, apply the procedures as described in clause A.5.3.6; +- 5) If CS-IBCF receives an initial request for a dialogue or standalone transaction that contains a single Route header pointing to itself, and it is co-located with an (G)MSC server, or it has a preconfigured (G)MSC server to be contacted, then forward the request to that (G)MSC server. Otherwise select an (G)MSC server and forward the request to that (G)MSC server. + +When the CS-IBCF receives an INVITE request, the CS-IBCF may require the periodic refreshment of the session to avoid hung states in the CS-IBCF. If the CS-IBCF requires the session to be refreshed, the CS-IBCF shall apply the procedures described in IETF RFC 4028 [31] clause 8. + +When the CS-IBCF receives a response to an initial request (e.g. 183 or 2xx), the CS-IBCF shall: + +- 1) if network topology hiding is required, apply the procedures as described in clause A.5.3.4; +- 2) if screening of SIP signalling is applied, apply the procedures as described in clause A.5.3.6; and +- 3) if the response establishes a dialogue, and the CS-IBCF is configured to perform application level gateway and/or transport plane control functions, the CS-IBCF shall save the Contact, To and Record-Route header field values received in the response such that the CS-IBCF is able to release the session if needed. + +#### A.5.3.2 Subsequent requests + +Upon receipt of any request, the CS-IBCF shall: + +- 1) if the request is an INVITE request, then respond with a 100 (Trying) provisional response; +- 2) if the request is a target refresh request and the CS-IBCF is configured to perform application level gateway and/or transport plane control functions, save the Contact and Cseq header field values received in the request such that the CS-IBCF is able to release the session if needed; +- 3) if the subsequent request is other than a target refresh request (including requests relating to an existing dialogue where the method is unknown) and the CS-IBCF is configured to perform application level gateway and/or transport plane control functions, save the Contact and Cseq header field values received in the request such that the CS-IBCF is able to release the session if needed; + +- 4) if network topology hiding is required, then apply the procedures as described in clause A.5.3.4; +- 5) if screening of SIP signalling is required, apply the procedures as described in clause A.5.3.6. + +When the CS-IBCF receives a response to the subsequent request and network topology hiding is required, then the CS-IBCF shall apply the procedures as described in clause A.5.3.4. + +When the CS-IBCF receives a response to the subsequent request and screening of SIP signalling is required, then the CS-IBCF shall apply the procedures as described in clause A.5.3.6. + +### A.5.3.3 CS-IBCF-initiated call release + +If the CS-IBCF provides transport plane control functionality and receives an indication of a transport plane related error the CS-IBCF may: + +- 1) if the CS-IBCF has already sent an initial INVITE request to the terminating side, apply SIP procedures detailed in IETF RFC 3261 [20] to terminate any corresponding SIP dialogue(s) or otherwise cancel the INVITE at the terminating side, making use of CANCEL and/or BYE request(s), based on information saved for the related dialogue; and +- 2) if the CS-IBCF has not yet sent out a final response for the initial INVITE request, send an appropriate failure response for the initial INVITE request to the originating side; and +- 3) if the CS-IBCF has already sent out a final response for the initial INVITE request, generate a BYE request for the originating side based on the information saved for the related dialogue. + +NOTE 1: Transport plane related errors can be indicated from e.g. TrGW. + +NOTE 2: Since the CS-IBCF does not handle the encapsulated ISUP, the BYE message(s) generated by the CS-IBCF will not contain any encapsulated ISUP REL message. + +If the CS-IBCF is able to determine an appropriate Q.850 cause value, then this may be included in a Reason header in the BYE message(s). + +### A.5.3.4 THIG functionality in the CS-IBCF + +#### A.5.3.4.1 General + +The following procedures shall only be applied if network topology hiding is required by the network. The network requiring network topology hiding is called the hiding network. + +NOTE 1: Requests and responses are handled independently; therefore, no state information is needed for that purpose within a CS-IBCF. + +The CS-IBCF shall apply network topology hiding to all headers which reveal topology information, such as Via, Route, Record-Route, and Path. Therefore, the CS-IBCF shall + +- either act as a B2BUA, i.e. set above headers as defined for a SIP user agent client by IETF RFC 3261 [20], +- or as an option follow the procedures defined in A.5.3.4.2. + +The CS-IBCF shall not screen SIP parameters for which there is a related ISUP parameter defined within ITU-T Recommendation Q.1912.5 [6]. + +NOTE 2: SIP-I screening is normally done by the GMSC, where the encapsulated ISUP message and the SIP headers are consistently screened. + +Upon receiving an incoming initial request for which network topology hiding has to be applied and which includes a Record-Route header, the CS-IBCF shall add its own routable SIP URI to the top of the Record-Route header. + +#### A.5.3.4.2 Decryption for network topology hiding + +Upon receiving a request/response, incoming to the hiding network, the CS-IBCF shall perform the decryption for network topology hiding purposes, i.e. the CS-IBCF shall: + +- 1) identify hostnames encrypted by the network this CS-IBCF belongs to within all headers of the incoming message; +- 2) use those hostnames that carry the identification of the hiding network within the value of the "tokenized-by" parameter as input to decryption; +- 3) use as encrypted string the hostname which follows the sent-protocol (for Via Headers, e.g. "SIP/2.0/UDP") or the URI scheme (for Route and Record-Route Headers, e.g. "sip:"); +- 4) replace all content of the received header which carries encrypted information with the entries resulting from decryption. + +EXAMPLE: An encrypted entry to a Via header that looks like: + +``` +Via: SIP/2.0/UDP Token(SIP/2.0/UDP msc2.home1.net;lr, +SIP/2.0/UDP msc1.home1.net;lr);tokenized-by=home1.net +``` + +will be replaced with the following entries: + +``` +Via: SIP/2.0/UDP msc2.home1.net;lr, SIP/2.0/UDP msc1.home1.net;lr +``` + +NOTE: Motivations for these decryption procedures are e.g. to allow the correct routing of a response through the hiding network, to enable loop avoidance within the hiding network, or to allow the entities of the hiding network to change their entries within e.g. the Record-Route header. + +### A.5.3.5 ALG functionality in the CS-IBCF + +The CS-IBCF shall only apply the following procedures if application level gateway functionality is required by the network. + +The CS-IBCF acts as a B2BUA when it performs ALG functionality. The CS-IBCF, although acting as a UA, does not initiate any registration of its associated addresses. These are assumed to be known by peer-to-peer arrangements within the SIP-I based CS domain. + +When the CS-IBCF receives an initial INVITE request from another SIP network, the CS-IBCF shall generate a new initial INVITE request and forward it to the (G)MSC Server. + +The internal function of the CS-IBCF as an ALG is equal to that one defined in TS 29.162 [37]. + +### A.5.3.6 Screening of SIP-I signalling + +The text in clause A.5.2.6 applies without changes. + +### A.5.3.7 Void + +--- + +## A.6 Procedures at the CS-TrGW + +### A.6.1 Transport Plane Control procedures + +--- + +## A.7 CS-IBCF - CS-TrGW Interaction + +### A.7.1 General + +#### A.7.1.1 Network Model + +Figure A.7.1.1.1 shows the network model. The broken line represents the call control signalling. The dotted line represents the bearer control signalling (if applicable) and the user plane. The CS-IBCF uses one context with two + +terminations in the TrGW. The termination T1 is used towards the 3GPP PLMN and the bearer termination T2 is used for the bearer towards the external IP network. + + + +The diagram illustrates the H.248 Context Model. It features four main components: '3GPP PLMN' on the left, 'CS-IBCF' at the top center, 'TrGW' at the bottom center, and 'Ext Network' on the right. A dashed green line connects the '3GPP PLMN' to the 'CS-IBCF'. A dashed red line connects the 'TrGW' to the 'Ext Network'. A solid blue vertical line connects the 'CS-IBCF' to the 'TrGW'. Inside the 'TrGW' box, there is a label 'CTXI' with two arrows pointing to 'T1' and 'T2'. The 'T1' termination is connected to the dashed red line towards the '3GPP PLMN', and the 'T2' termination is connected to the dashed red line towards the 'Ext Network'. + +Diagram of H.248 Context Model showing 3GPP PLMN, CS-IBCF, TrGW, and Ext Network components and their connections. + +Figure A.7.1.1.1: H.248 Context Model + +## A.7.1.2 Signalling flows + +### A.7.1.2.1 Basic Procedures + +#### A.7.1.2.1.1 Call Establishment + +Figure A.7.1.2.1.1.1 depicts the signalling flow for a call setup from external network towards 3GPP PLMN. The same signalling flow applies for a call setup from the 3GPP PLMN towards an external network with the exception that terminations T1 and T2 are then exchanged. + + + +``` + +sequenceDiagram + participant CS-TrGW + participant CS-IBCF + + Note over CS-IBCF: 1. SDP offer (IP2o, P2o) + Note right of CS-IBCF: 2. Use case X detected +that needs TrGW +functionality + CS-IBCF->>CS-TrGW: 3. H.248 ADD req +(C= ?, T= ?, LAddr=?, LPort=?) + Note left of CS-TrGW: 4. Create outgoing termination T1 + CS-TrGW->>CS-IBCF: 5. H.248 ADD resp. +(C=C1, T=T1, +LAddr=IP1o, LPort=P1o) + Note right of CS-IBCF: 6. Modify SDP offer + Note over CS-IBCF: 7. SDP offer (IP1o, P1o) + Note over CS-IBCF: 8. SDP answer (IP1a, P1a) + CS-IBCF->>CS-TrGW: 9. H.248 MOD req +(C= C1, T= T1, +RAddr=IP1a, RPort=P1a) + Note left of CS-TrGW: 10. Configure Outgoing Termination T1 + CS-TrGW->>CS-IBCF: 11. H.248 MOD Resp +(C= C1, T= T1) + CS-IBCF->>CS-TrGW: 12. H.248 ADD req +(C= C1, T= ?, LAddr=?, LPort=?, +RAddr=IP2o, RPort=P2o) + Note left of CS-TrGW: 13. Create incoming Termination T2 + CS-TrGW->>CS-IBCF: 14. H.248 ADD Resp +(C= C1, T= T2, +LAddr=IP2a, LPort=P2a, +RAddr=IP1a, RPort=P1a) + Note right of CS-IBCF: 15. Modify SDP answer + Note over CS-IBCF: 16. SDP answer (IP2a, P2a) + +``` + +Sequence diagram showing the interaction between CS-TrGW and CS-IBCF for TrGW functionality. The diagram includes 16 steps: 1. SDP offer (IP2o, P2o) to CS-IBCF; 2. Use case X detected; 3. H.248 ADD req to CS-TrGW; 4. Create outgoing termination T1; 5. H.248 ADD resp; 6. Modify SDP offer; 7. SDP offer (IP1o, P1o) to network; 8. SDP answer (IP1a, P1a) from network; 9. H.248 MOD req to CS-TrGW; 10. Configure Outgoing Termination T1; 11. H.248 MOD Resp; 12. H.248 ADD req for T2; 13. Create incoming Termination T2; 14. H.248 ADD Resp; 15. Modify SDP answer; 16. SDP answer (IP2a, P2a) to network. Brackets on the right indicate phases: Reserve TrGW Connection Point, Configure TrGW Connection Point, and Reserve And Configure TrGW Connection Point. + +1. The CS-IBCF receives an SDP offer in SIP signalling. +2. The CS-IBCF detects that one of the CS-TrGW functions is required, e.g. NAPT/NAT +3. The CS-IBCF sends a H.248 ADD command to create the outgoing termination and to request resources to execute CS-TrGW function +4. The CS-TrGW creates the outgoing termination +5. The CS-TrGW replies to CS-IBCF with a H.248 Add reply command and provides the local address and port of the outgoing termination +6. The CS-IBCF replaces the IP address inside the SDP using the information coming from CS-TrGW +7. SDP offer is sent to the network at the outgoing side +8. SDP answer is received by CS-IBCF + +9. The CS-IBCF sends a H.248 MOD command to configure the outgoing termination with Address and port information received in the SDP answer + 10. The CS-TrGW configures the outgoing termination + 11. The CS-TrGW replies to CS-IBCF with a H.248 MOD reply command + 12. The CS-IBCF sends a H.248 ADD command to create the incoming termination and to request resources to execute CS-TrGW function + 13. The CS-TrGW creates the incoming termination + 14. The CS-TrGW replies to the CS-IBCF with a H.248 Add reply command and provides the local address and port of the incoming termination. +- Note: Steps 12 to 14 may also be executed after step 2. +15. The CS-IBCF replaces the IP address inside the SDP using the information coming from CS-TrGW + 16. SDP answer is sent to the network at the incoming side + +**Figure A.7.1.2.1.1.1: CS-IBCF and CS-TrGW interaction at Call establishment** + +When creating the termination T1, the CS-IBCF may also indicate that the IP Interface type is "NboIP". + +When creating the termination T2, the CS-IBCF may also indicate that the IP Interface type is "ExtSIPI". + +NOTE: The IP Interface Type allows the CS-TrGW to collect statistics per interface type associated with the RTP bearer termination as required by TS 32.407 [44]. The provision of these statistics is outside of the scope of this specification. + +### A.7.1.2.1.2 Call Release + +Figure A.7.1.2.1.2.1 depicts the signalling flow for a call release. + + + +``` + +sequenceDiagram + participant CS-IBCF + participant CS-TrGW + Note right of CS-IBCF: 1. Event causing release + CS-IBCF->>CS-TrGW: 2. H.248 SUB req (C=C1, T=T1) + Note left of CS-TrGW: 3. Destroy outgoing termination T1 + CS-TrGW-->>CS-IBCF: 4. H.248 SUB resp. (C=C1, T=T1) + Note right of CS-IBCF: Release TrGW Termination + CS-IBCF->>CS-TrGW: 5. H.248 SUB req (C=C1, T=T2) + Note left of CS-TrGW: 6. Destroy incoming termination T2 + CS-TrGW-->>CS-IBCF: 7. H.248 SUB resp. (C=C1, T=T2) + Note right of CS-IBCF: Release TrGW Termination + +``` + +Sequence diagram showing the interaction between CS-TrGW and CS-IBCF for call release. The process starts with an event causing release at CS-IBCF, followed by H.248 SUB requests and responses for outgoing and incoming terminations. + +1. The CS-IBCF identifies that the call is to be released. Typically this will be by the receipt of a SIP BYE request. +2. The CS-IBCF sends a H.248 SUB command to release the outgoing termination +3. The CS-TrGW destroys the outgoing termination +4. The CS-TrGW replies to CS-IBCF with a H.248 Sub reply command +5. The CS-IBCF sends a H.248 SUB command to release the incoming termination +6. The CS-TrGW destroys the incoming termination +7. The CS-TrGW replies to CS-IBCF with a H.248 Sub reply command + +Note 1: Steps 5 to 7 may also be executed before steps 2 to 4 or in parallel with steps 2 to 4. + +Note 2: Rather than releasing the two terminations separately, the CS-IBCF may request the CS-TrGW to release both terminations in a single request. + +**Figure A.7.1.2.1.2.1: CS-IBCF and CS-TrGW interaction at Call release** + +### A.7.1.2.2 Specific Use Cases + +#### A.7.1.2.2.1 CS-IBCF as Entry Point, Call Establishment with IP Version Interworking + +This case considers the call establishment message flow for the CS-IBCF and CS-TrGW, when the CS-IBCF is acting as an Entry point and IP version interworking is required. The example assumes that the external SIP-I network uses IPv4 addressing and the CS CN uses IPv6 addressing. + +With reference to the steps in figure A.7.1.2.1.1.1, the following additions are required, specific to this use case: + +3. The CS-IBCF requests the CS-TrGW to choose an IPv6-based local connection address for the created outgoing termination. + +5. The local address and port returned to the CS-IBCF are IPv6-based. +6. Specifically, the IPv6 address and port number received from the CS-TrGW in the local connection address of the outgoing termination replace the IPv4 address and port number received from the external SIP-I network. +9. Specifically, the CS-IBCF passes the IPv6 address and port number received in the SDP answer to the CS-TrGW as the remote connection address on the outgoing termination. +12. The CS-IBCF requests the CS-TrGW to choose an IPv4-based local connection address on the incoming termination. The CS-IBCF uses the IPv4 addresses and port numbers received in the initial SDP offer as the remote connection address on the incoming termination. +14. The local address and port returned to the CS-IBCF are IPv4-based. +15. Specifically, the IPv4 address and port number received from the CS-TrGW in the local connection address of the incoming termination replace the IPv6 address and port number received from the CS-CN. + +#### A.7.1.2.2.2 Hanging Termination Detection + +This clause considers the message flow for the CS-IBCF and CS-TrGW, when IP hanging termination detection is required. Hanging termination detection procedure allows the CS-IBCF to detect a hanging context and termination in the TrGW resulting, for example, from a loss of communication between the CS-IBCF and the CS-TrGW. + +When the CS-IBCF requests the CS-TrGW to reserve terminations, the CS-IBCF shall also request the CS-TrGW to periodically report termination heartbeat indications. If the CS-IBCF includes an indication of the periodicity of the termination heartbeat notifications, the specified period shall be much greater than the mean call holding time. + +The CS-IBCF and the CS-TrGW shall support detection of hanging terminations. + +The call is established as described in clause A.7.1.2.1.1. With reference to the steps in figure A.7.1.2.1.1, the following additions are required, specific to this use case: + +3. The CS-IBCF requests the CS-TrGW to send termination heartbeat notifications for the created termination. It may also include an indication of the periodicity of the termination heartbeat notifications. +12. The CS-IBCF requests the CS-TrGW to send termination heartbeat notifications for the created termination. It may also include an indication of the periodicity of the termination heartbeat notifications. + +Subsequently, the CS-TrGW shall periodically send termination heartbeat notifications, as shown in figure A.7.1.2.2.2.1, until the call is released. + +When the CS-IBCF receives a termination heartbeat notification from the CS-TrGW via the Termination heartbeat - Indication procedure, the CS-IBCF shall return a Termination heartbeat -Indication Ack (without an error) if the context id / termination identity combination exists in the CS-IBCF. If this combination does not exist, the CS-IBCF shall return an error and shall correct the mismatch, for example by requesting the CS-TrGW to subtract the indicated termination and to clear any associated context. + + + +``` +sequenceDiagram + participant CS-TrGW + participant CS-IBCF + Note left of CS-TrGW: CS-IBCF requests heartbeat notifications + CS-TrGW->>CS-IBCF: Termination Heartbeat Indication + CS-IBCF-->>CS-TrGW: Termination Heartbeat Indication Ack +``` + +Sequence diagram showing the interaction between CS-TrGW and CS-IBCF for termination heartbeat notifications. The CS-TrGW sends a 'Termination Heartbeat Indication' message to the CS-IBCF, and the CS-IBCF responds with a 'Termination Heartbeat Indication Ack' message. + +**Figure A.7.1.2.2.2.1: CS-IBCF and CS-TrGW interaction for termination heartbeat notifications** + +#### A.7.1.2.2.3 Gate Management + +This clause considers the message flow for the CS-IBCF and CS-TrGW, when the CS-IBCF is acting as an Entry point and remote source address filtering is required for the termination towards the external SIP-I network. + +Gate Management shall be a mandatory feature of the CS-TrGW, but an optional feature of the CS-IBCF. + +As a security related option, on request from the CS-IBCF, filtering may be enabled to check/validate the source address or source address and port number of incoming packets from the external network. If the CS-IBCF requests address filtering, it may additionally provide an address specification, which may identify either a single address or a range of addresses, against which filtering is to be performed. The absence of such an address specification in the request implicitly requests filtering against the IP address of the remote connection address. In addition to address filtering, the CS-IBCF may also request port filtering. If the CS-IBCF requests port filtering, it may additionally include either a port or a range of ports, against which filtering is to be performed. The absence of a port specification in the request implicitly requests filtering against the port of the remote connection address. + +If the CS-TrGW is configured to apply source IP address and possibly source port filtering, it shall only pass incoming IP packets from the identified source, and discard IP packets from other sources. + +The call is established as described in clause A.7.1.2.1.1. With reference to the steps in figure A.7.1.2.1.1.1, the following additions are required, specific to this use case: + +12. If remote source address filtering is required for the created termination, then the CS-IBCF includes the information element "Remote source address filtering" in the request sent to the CS-TrGW. In addition, it may also include the information element "Remote source address mask". + +If remote source port filtering is required for the created termination (in addition to remote source address filtering), then the CS-IBCF includes the information element "Remote source port filtering" in the request sent to the CS-TrGW. It may also include one of the information elements "Remote source port" or "Remote source port range". + +Subsequently, the CS-TrGW applies filtering as requested to the packets arriving from the external network. Any packet arriving, which does not meet the filtering requirement, is discarded. + +#### A.7.1.2.2.4 QoS Packet Marking + +This clause considers the message flow for the CS-IBCF and CS-TrGW, when the CS-IBCF requires the use of differentiated services (see IETF RFC 2474 [41]). + +It is optional for the CS-IBCF to support differentiated service controlled over the Ix Interface. It shall be mandatory for the CS-TrGW to support differentiated service controlled over the Ix Interface. A CS-TrGW can also support DiffServ Code Point marking based on local configuration. The CS-IBCF may request the CS-TrGW to set diffserv codepoints for outgoing packets on a termination. The CS-IBCF may either indicate the applicable DSCP value or configure the TrGW to copy the DSCP value in the corresponding received packet. When the CS-IBCF requests the CS-TrGW to create a termination and if differentiated services are required for the created termination, the CS-IBCF shall include the information elements "DiffServ Code Point" and/or "DiffServ Tagging Behaviour" in the request sent to the CS-TrGW. + +The call is established as described in clause A.7.1.2.1.1. With reference to the steps in figure A.7.1.2.1.1.1, the following additions are required, specific to this use case: + +3. If differentiated services are required for the created termination, then the CS-IBCF includes the information elements "DiffServ Code Point" and/or "DiffServ Tagging Behaviour" in the request sent to the CS-TrGW. +12. If differentiated services are required for the created termination, then the CS-IBCF includes the information elements "DiffServ Code Point" and/or "DiffServ Tagging Behaviour" in the request sent to the CS-TrGW. + +Subsequently, for all egress packets, the CS-TrGW shall set the DiffServ Code Point in the IP header as specified by the CS-IBCF: + +- If the DiffServ Tagging Behaviour information element was received with a value to indicate that the DiffServ Code Point should be copied, then the CS-TrGW shall copy the DiffServ Code Point in the IP header of the egress packet from the ingress packet. +- If the DiffServ Tagging Behaviour information element was not received, or was received with a value to indicate that the DiffServ Code Point should be set to a specific value, then: + +- If the DiffServ Code Point information element was received, then the CS-TrGW shall set the DiffServ Code Point in the IP header of the egress packet to the value received in the DiffServ Code Point information element. +- If the DiffServ Code Point information element was not received, then the CS-TrGW may set the DiffServ Code Point in the IP header of the egress packet to a configured default value. + +#### A.7.1.2.2.5 IP Realms + +This clause considers the message flow for the CS-IBCF and CS-TrGW, when the two networks are in different IP realms. IP realms are described in TS 23.205 [9] clause 20. + +The CS-IBCF and the CS-TrGW shall support IP realm indication. + +The call is established as described in clause A.7.1.2.1.1.1. With reference to the steps in figure A.7.1.2.1.1.1, the following additions are required, specific to this use case: + +3. The CS-IBCF may specify the required IP Realm. +4. The CS-TrGW allocates resources from the appropriate IP realm as specified by the CS-IBCF in step 3. +12. The CS-IBCF may specify the required IP Realm. +13. The CS-TrGW allocates resources from the appropriate IP realm as specified by the CS-IBCF in step 12. + +If there is a change in the IP Realms that are available or if they are modified in the CS-TrGW then the CS-TrGW shall inform the CS-IBCF via the IP Realm Availability Procedure (see clause A.7.2.3), if this procedure is supported by the CS-TrGW. The basic flow is depicted in figure A.7.1.2.2.5.1 + + + +``` +sequenceDiagram + participant CS-TrGW + participant CS-IBCF + Note left of CS-TrGW: IP Realm Availability Indication + CS-TrGW->>CS-IBCF: IP Realm Availability Indication + Note right of CS-IBCF: IP Realm Availability Indication Ack + CS-IBCF->>CS-TrGW: IP Realm Availability Indication Ack +``` + +The diagram illustrates a sequence of messages between two entities, CS-TrGW and CS-IBCF. It starts with a message labeled 'IP Realm Availability Indication' sent from CS-TrGW to CS-IBCF. Following this, a return message labeled 'IP Realm Availability Indication Ack' is sent from CS-IBCF back to CS-TrGW. + +Sequence diagram showing the IP Realm Availability procedure between CS-TrGW and CS-IBCF. + +**Figure A.7.1.2.2.5.1: IP Realm Availability** + +The monitoring of IP realm availability is optional and if supported by the CS-TrGW may be requested by the CS-IBCF. + +#### A.7.1.2.2.6 Media Inactivity Detection + +The CS- TrGW and the CS-IBCF may support the detection of inactive media flows. + +The CS-IBCF may request a CS-TrGW that supports media inactivity detection to detect if a media flow is inactive. + +- NOTE: The decision to apply or not to apply media inactivity detection is general for all sessions with the same media characteristics (i.e. not user specific). Detailed conditions when media inactivity detection can be requested are not specified in the present release. + +When the CS-IBCF requests the CS-TrGW to reserve transport addresses/resources, the CS-IBCF may indicate to the CS-TrGW that detection of an inactive media flow is required and may additional specify inactivity detection time and inactivity detection direction. The IBCF may request the detection of media inactivity on a termination or a stream basis. + +The call is established as described in clause A.7.1.2.1.1.1. With reference to the steps in figure A.7.1.2.1.1.1, the following additions are required, specific to this use case: + +3. The CS-IBCF indicates to the CS-TrGW that detection of an inactive media flow is required and can additional specify inactivity detection time and inactivity detection direction. + +12. The CS-IBCF indicates to the CS-TrGW that detection of an inactive media flow is required and can additional specify inactivity detection time and inactivity detection direction. + +The CS- TrGW shall determine a media flow to be inactive if there is no media sent and/or received within the inactivity detection time period. + +When the CS-IBCF receives a notification of inactive media from the CS-TrGW via the Media Inactivity Notification procedure, the CS-IBCF shall return a Media Inactivity Notification Ack and shall take appropriate action (e.g. release the termination). + + + +``` + +sequenceDiagram + participant IBCF + participant TrGW + Note left of IBCF: IBCF + Note right of TrGW: TrGW + TrGW->>IBCF: Media Inactivity Notification + IBCF->>TrGW: Media Inactivity Notification - Ack + +``` + +Sequence diagram showing Media Inactivity Notification between IBCF and TrGW. The IBCF sends a 'Media Inactivity Notification' message to the TrGW, and the TrGW responds with a 'Media Inactivity Notification - Ack' message. + +**Figure A.7.1.2.2.6.1: Media Inactivity Notification** + +#### A.7.1.2.2.7 RTCP Handling + +The CS-IBCF and the CS-TrGW shall support control via the Ix interface of the specific RTCP behaviour associated to an RTP flow. + +When the CS-IBCF requests the CS-TrGW to reserve transport addresses/resources for an RTP flow, the CS-IBCF may indicate to the CS-TrGW whether to reserve corresponding RTCP resources should also request the CS-TrGW to reserve resources for the corresponding RTCP flow, but may alternatively request the CS-TrGW not to reserve resources for the corresponding RTCP flow. When the CS-IBCF requests the CS-TrGW to reserve transport addresses/resources for a non-RTP flow, the CS-IBCF shall not request the CS-TrGW to reserve resources for an RTCP flow. + +To request the CS-TrGW to reserve resources for an RTCP flow, the CS-IBCF shall provide the RTCP handling information element with a value indicating that resources for RTCP shall be reserved. + +To request the CS-TrGW not to reserve resources for an RTCP flow, the CS-IBCF shall either provide the RTCP handling information element with a value indicating that resources for RTCP shall not be reserved or omit the RTCP handling information element. + +If the CS-TrGW receives the indication to reserve RTCP resources, the TrGW shall allocate a local port with even number for an RTP flow also reserve the consecutive local port with odd number for the associated RTCP flow, and it shall send and be prepared to receive RTCP. + +If the CS-TrGW receives the indication to not reserve RTCP resources, or does not receive any indication, it shall not allocate an RTCP port when allocating a port for an RTP flow. The CS-TrGW shall not send any RTCP packets and shall silently discard any received RTCP packets. + +When RTCP resources are requested, the CS-IBCF may also specify: + +- the remote RTCP port, and optionally the remote address, where to send RTCP packets; if not specified, the CS-TrGW shall send RTCP packets to the port contiguous to the remote RTP port; +- bandwidth allocation requirements for RTCP, if the RTCP bandwidth level for the session is different than the default RTCP bandwidth as specified in RFC 3556 [39]. + +NOTE: In line with the recommendations of RFC 3605 [40], separate address or non-contiguous RTCP port numbers will not be allocated by the TrGW. + +The CS-TrGW shall return an error if it can not allocate the requested RTCP resources. + +The call is established as described in clause A.7.1.2.1.1. With reference to the steps in figure A.7.1.2.1.1.1, the following additions are required, specific to this use case: + +3. The CS-IBCF may specify if RTCP handling is required. +4. The CS-TrGW allocates RTCP resources as specified by the CS-IBCF in step 3. +12. The CS-IBCF may specify if RTCP handling is required. +13. The CS-TrGW allocates RTCP as specified by the CS-IBCF in step 12. + +#### A.7.1.2.2.8 Bandwidth Policing + +##### A.7.1.2.2.8.1 Overview + +The CS-IBCF may support traffic policing of incoming media flows. + +The CS-TrGW shall support traffic policing of the maximum average bitrate, defined as sustainable data rate (see IETF RFC 2216 [42]) of incoming media flows and may support traffic policing of the peak data rate of incoming media flows. + +The CS-IBCF may require the CS-TrGW to police the media flows to ensure that they conform to the expected data rates. + +When the CS-IBCF requests the CS-TrGW to reserve transport addresses/resources, the CS-IBCF may indicate to the CS-TrGW that policing of the related media streams is required and provide traffic policing related parameters as detailed in clause A.7.1.2.2.8.2. + +If such policing is requested, the CS-TrGW shall police the corresponding media streams as detailed in clause A.7.1.2.2.8.2, by measuring the data rate for the received packets within that media stream. If the permissible data rate provided by the CS-IBCF is exceeded, the CS-TrGW shall discard packets to reduce their data rate to the permissible data rate. + +##### A.7.1.2.2.8.2 Bandwidth policing procedures + +The call is established as described in clause A.7.1.2.1.1. With reference to the steps in figure A.7.1.2.1.1.1, the following additions are required, specific to this use case: + +3. If traffic policing is required for the created termination, then the CS-IBCF shall include the information element "Traffic Policing Required" in the request sent to the CS-TrGW. If policing of sustainable data rate is required, then the CS-IBCF shall include the information elements "Sustainable Data Rate" and "Maximum Burst Size" in the request. If policing of peak data rate is required, then the CS-IBCF shall include the information element "Peak Data Rate" in the request and may additionally include the information element "Delay Variation Tolerance". +12. If traffic policing is required for the created termination, then the CS-IBCF shall include the information element "Traffic Policing Required" in the request sent to the CS-TrGW. If policing of sustainable data rate is required, then the CS-IBCF shall include the information elements "Sustainable Data Rate" and "Maximum Burst Size" in the request. If policing of peak data rate is required, then the CS-IBCF shall include the information element "Peak Data Rate" in the request and may additionally include the information element "Delay Variation Tolerance". + +When requested by the CS-IBCF, the CS-TrGW shall police the media stream flow rates according to one or more of the following media policing(s), in accordance with IETF RFC 2216 [42]. + +The following media policing shall be supported at the CS-TRGW: + +- **Sustainable Data Rate (SDR) Policing:** + +To request policing of the sustainable data rate of a media stream, the CS-IBCF shall request media policing for that media stream and shall provide the sustainable data rate, and shall provide a maximum burst size (MBS) indicating the expected maximum size of packet bursts for that media stream. The CS-TrGW shall then measure the data rate for the received packets within that media stream as per IETF RFC 2216 [42] for "Token Bucket", where $r$ =SDR and $b$ =MBS. If the permissible sustainable data rate is exceeded, the CS-TRGW shall discard packets to reduce the data rate to the permissible sustainable data rate. + +NOTE 1: The CS-IBCF can derive the sustainable data rate from bandwidth parameters if it receives them within an SDP description. + +The following media policing may be supported in addition at the CS-TRGW; if supported, then the following applies: + +- **Peak Data Rate Policing:** + +To request policing of the peak data rate of a media stream, the CS-IBCF shall request media policing for that media stream and shall provide the peak data rate, and may provide a Delay Variation Tolerance indicating the expected maximum delay variation due to jitter for that media stream. The CS-TRGW shall then measure the data rate for the received packets within that media stream. If the permissible peak data rate is exceeded, the CS-TRGW shall discard packets to reduce the data rate to the permissible peak data rate. If both peak data rate and sustainable data rate have been provided for the same media stream, the CS-TRGW shall discard packets to reduce the data rate to the permissible peak data rate and should discard packets to reduce the data rate to the permissible sustainable data rate. + +NOTE 2: The decision to apply or not traffic policing is general for all sessions with the same media characteristics (i.e. not user specific). The conditions which media policings to apply are beyond the scope of the specification. This can be based on the media characteristics of the session (e.g. media type). + +#### A.7.1.2.2.9 Through-Connection + +The Change Through-Connection procedure is mandatory for CS-IBCF and CS-TrGW to support. + +The CS-IBCF sets the Stream mode parameter using the Change Through-Connection procedure to request the CS-TrGW to both-way or one-way through-connect or block media streams on a termination. + +The CS-IBCF may combine the Change Through-Connection procedure with the Reserve and Configure TrGW Connection Point, Reserve TrGW Connection Point or Configure TrGW Connection Point procedure in figure A.7.1.2.1.1.1., or may apply this procedure separately. + +#### A.7.1.2.2.10 Emergency Call + +This procedure is identical to that of clause A.7.1.2.1.1 apart from the CS-IBCF requesting the CS-TrGW to treat the call as emergency call with a preferential handling by including the information element "Emergency Call Indicator" when creating a context within the "Reserve and Configure TrGW Connection Point" or "Reserve TrGW Connection Point" procedure. + +With reference to the steps in figure A.7.1.2.1.1.1, the following additions are required, specific to this use case: + +3. If step 3 is performed before step 13, the CS-IBCF requests the CS-TrGW to handle the call as emergency call by including the "Emergency Call Indicator". +13. If step 13 is performed before step 3, the CS-IBCF requests the CS-TrGW to handle the call as emergency call by including the "Emergency Call Indicator". + +#### A.7.1.2.2.11 Interactive Connectivity Establishment + +The CS-IBCF and the CS-TrGW may support ICE functionality as specified in IETF RFC 5245 [56] and TS 24.229 [12]. + +Support of full ICE functionality is optional, but if ICE is supported, the CS-IBCF and the CS-TrGW shall at least support ICE lite as specified in IETF RFC 5245 [56]. + +The requirements as described in TS 29.162 [37] for IBCF and TrGW, apply to the CS-IBCF and the CS-TrGW when the ICE procedures are supported. + +#### A.7.1.2.2.12 SDP Capability Negotiation (SDPCapNeg) + +The SDP Capability Negotiation (SDPCapNeg) as specified in IETF RFC 5939 [57] is adopted as an optional functionality to negotiate capabilities and their associated configurations according to 3GPP TS 24.229 [12]. + +The requirements and procedures as described in subclause 10.2.24 of 3GPP TS 29.162 [37] for IBCF and TrGW, apply to the CS-IBCF and the CS-TrGW when SDPCapNeg is used. + +## A.7.2 Ix Signalling Procedures + +### A.7.2.1 Introduction + +This clause describes the logical signalling procedures (i.e. message identifiers are not part of the protocol) between the CS-IBCF and CS-TrGW. The procedures within this clause are intended to be implemented using the standard H.248 procedure as defined in ITU-T Recommendation H.248.1 [33] with appropriate parameter combinations. + +### A.7.2.2 Call Related Procedures + +#### A.7.2.2.1 Reserve TrGW Connection Point + +This procedure is used to reserve a termination at the CS-TrGW. + +**Table A.7.2.2.1.1: Reserve TrGW Connection Point** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------|-----------|----------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserve TrGW Connection Point | CS-IBCF | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Emergency Call Indicator | O | This information element identifies the call as emergency call that requires a preferential handling. | +| | | Termination Request | M | This information element requests a new termination for the bearer to be established. | +| | | IP Interface | O | This information element specifies the type of external interface to be used for the IP termination (e.g. ExtSIPI, NboIP). | +| | | Local IP Resources | O | This information element indicates the resource(s) (e.g. codec, auxiliary payload types) for which the CS-TrGW shall be prepared to receive user data. | +| | | ReserveValue | C | This information element indicates if multiple local resources are to be reserved.
This information element shall be included if a speech codec and auxiliary payload types are configured. | +| | | Local Connection Address Request | M | This information element requests an IP address and port number on the CS-TrGW that the remote end can send user plane data to. | +| | | Notify termination heartbeat | M | This information element requests termination heartbeat indications and may specify their periodicity. | +| | | Notify Released Bearer | O | This information element requests a notification of a released bearer. | +| | | IP Realm Identifier | O | This information element indicates the IP realm of the IP termination. | +| | | IP Version | C | This information element indicates the version of the internet protocol to be applied at the termination for the user plane. This is required for IP address translation. | +| | | DiffServ Code Point | O | This information element indicates a specific DiffServ code point to be used in the IP header in packets sent on the IP termination. | +| | | DiffServ Tagging Behaviour | O | This information element indicates whether the Diffserv code point in the IP header in packets sent on the IP termination should be copied from the received value or set to a specific value. | +| | | Remote Source Address Filtering | O | This information element indicates that remote source address filtering is required. | +| | | Remote Source Address Mask | C | This information element provides information on the valid remote source addresses. This may be included if remote source address filtering is included. It shall not be included if remote source address filtering is not included. | +| | | Remote Source Port Filtering | O | This information element indicates that remote source port filtering is required. | + +| | | | | | +|-----------------------------------|---------|-------------------------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Remote Source Port | C | This information element identifies the valid remote source port. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| | | Remote Source Port Range | C | This information element identifies a range of valid remote source ports. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| | | Media Inactivity Detection Required | O | This information element indicates that detection of inactive media flows is required. | +| | | Inactivity Detection Time | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection time. | +| | | Inactivity Detection Direction | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection direction. | +| | | RTCP handling | O | Indicates whether or not the CS-TrGW shall reserve a port for an RTCP flow. | +| | | Traffic Policing Required | O | This information element indicates that policing of the media flow is required. | +| | | Peak Data Rate | O | This information element may be present if Policing is required and specifies the permissible peak data rate for a media stream. (NOTE 2) | +| | | Sustainable Data Rate | O | This information element may be present if Policing is required and specifies the permissible sustainable data rate for a media stream. (NOTE 2) | +| | | Delay Variation Tolerance | O | This information element may be present if Policing on Peak Data Rate is required and specifies the maximum expected delay variation tolerance for the corresponding media stream. | +| | | Maximum Burst Size | C | This information element shall be present if Policing on Sustainable Data Rate is required and specifies the maximum expected burst size for the corresponding media stream. | +| | | ICE password request | O | This information element is present if CS-IBCF requests an ICE password. | +| | | ICE Ufrag request | O | This information element is present if CS-IBCF requests an ICE ufrag. | +| | | ICE host candidate request | O | This information element is present if CS-IBCF requests an ICE host candidate. | +| | | STUN server request | O | This information element is present if CS-IBCF requests the CS-TrGW to answer STUN connectivity checks for ICE. | +| | | SDPCapNeg configuration | O | This information element provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. | +| Reserve TrGW Connection Point Ack | CS-TrGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | + +| | | | | | +|---------------------------------------------------------------------------------|--|--------------------------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Local IP Resources | C | This information element indicates the resources that the CS-TrGW has reserved to receive the user plane data from the remote peer. This IE shall be present if it was contained in the request. If the IE was not contained in the request, it may be present in the reply. | +| | | Local Connection Address | M | This information element indicates the IP address and port on the CS-TrGW that shall receive user plane data from the remote peer. | +| | | ICE password | C | This information element shall be present only if it was contained in the request. It indicates the ICE password assigned by the CS-TrGW. | +| | | ICE Ufrag | C | This information element shall be present only if it was contained in the request. It indicates the ICE Ufrag assigned by the CS-TrGW. | +| | | ICE host candidate | C | This information element shall be present only if it was contained in the request. It indicates the ICE host candidate assigned by the CS-TrGW. | +| | | ICE lite indication | C | This information element shall be present only if an ICE host candidate request was contained in the request, and the CS-IBCF supports ICE lite, but not full ICE. It indicates that the CS-TrGW only supports ICE lite. | +| | | SDPCapNeg configuration | C | This information element shall be present only if it was contained in the request. It provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. | +| NOTE 1: Remote Source Port and Remote Source Port Range are mutually exclusive. | | | | | +| NOTE 2: At least one of these IEs shall be present when policing is required. | | | | | + +#### A.7.2.2.2 Configure TrGW Connection Point + +This procedure is used to configure or reconfigure a termination at the CS-TrGW. + +**Table A.7.2.2.2.1: Configure TrGW Connection Point** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------------|-----------|-------------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Configure TrGW Connection Point | CS-IBCF | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the existing bearer termination. | +| | | IP Interface | O | This information element specifies the type of external interface to be used for the IP termination (e.g. ExtSIPI, NboIP). | +| | | Local IP Resources | O | This information element indicates the resources (e.g. codec, auxiliary payload types) that the CS-TrGW may use on the reception of user plane data. | +| | | Remote IP Resources | O | This information element indicates the resources (e.g. codec, auxiliary payload types) that the CS-TrGW may send user plane data to. | +| | | Local Connection Address | O | This information element indicates the IP address and port on the CS-TrGW that the remote peer can send user plane data to. | +| | | Remote Connection Address | O | This information element indicates the IP address and port that the CS-TrGW can send user plane data to. | +| | | Reserve Value | O | This information element indicates if multiple resources are to be reserved. | +| | | Notify termination heartbeat | O | This information element requests termination heartbeat indications and may specify their periodicity. | +| | | DiffServ Code Point | O | This information element indicates a specific DiffServ code point to be used in the IP header in packets sent on the IP termination. | +| | | DiffServ Tagging Behaviour | O | This information element indicates whether the Diffserv code point in the IP header in packets sent on the IP termination should be copied from the received value or set to a specific value. | +| | | Remote Source Address Filtering | O | This information element indicates that remote source address filtering is required. | +| | | Remote Source Address Mask | C | This information element provides information on the valid remote source addresses. This may be included if remote source address filtering is included. It shall not be included if remote source address filtering is not included. | +| | | Remote Source Port Filtering | O | This information element indicates that remote source port filtering is required. | +| | | Remote Source Port | C | This information element identifies the valid remote source port. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| | | Remote Source Port Range | C | This information element identifies a range of valid remote source ports. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| | | Media Inactivity Detection Required | O | This information element indicates that detection of inactive media flows is required. | + +| | | | | | +|-------------------------------------|---------|--------------------------------------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Inactivity Detection Time | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection time. | +| | | Inactivity Detection Direction | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection direction. | +| | | RTCP handling | O | Indicates whether or not the CS-TrGW shall reserve a port for an RTCP flow. | +| | | Traffic Policing Required | O | This information element indicates that policing of the media flow is required. | +| | | Peak Data Rate | O | This information element may be present if Policing is required and specifies the permissible peak data rate for a media stream.(NOTE 2) | +| | | Sustainable Data Rate | O | This information element may be present if Policing is required and specifies the permissible sustainable data rate for a media stream.(NOTE 2) | +| | | Delay Variation Tolerance | O | This information element may be present if Policing on Peak Data Rate is required and specifies the maximum expected delay variation tolerance for the corresponding media stream. | +| | | Maximum Burst Size | C | This information element shall be present if Policing on Sustainable Data Rate is required and specifies the maximum expected burst size for the corresponding media stream. | +| | | ICE Connectivity Check | C | This information element requests the CS-TrGW to perform ICE connectivity check as defined by IETF RFC 5245 [ab]. It is only applicable for full ICE. | +| | | Notify ICE Connectivity Check Result | C | This information element requests a notification of ICE connectivity check result. It is only applicable for full ICE. | +| | | Notify New Peer Reflexive Candidate | C | This information element requests a notification of new peer reflexive candidate was discovered during a connectivity check. It is only applicable for full ICE. | +| | | Additional ICE Connectivity Check | C | This information element requests the CS-TrGW to perform additional ICE connectivity check as defined by IETF RFC 5245 [ab]. It is only applicable for full ICE. | +| | | ICE received candidate | O | This information element is present if CS-IBCF indicates a received candidate for ICE. | +| | | ICE received password | O | This information element is present if CS-IBCF indicates a received password for ICE. | +| | | ICE received Ufrag | O | This information element is present if CS-IBCF indicates a received Ufrag for ICE. | +| Configure TrGW Connection Point Ack | CS-TrGW | SDPCapNeg configuration | O | This information element provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. | +| | | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|---------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Local IP Resources | O | This information element indicates the resources that the CS-TrGW has reserved to receive the user plane data from the far end. | +| | | Remote IP Resources | O | This information element indicates the resource (i.e. codec) that the CS-TrGW shall use to send user data to. | +| | | Local Connection Address | O | This information element indicates the IP address and port on the CS-TrGW that the remote end can send user plane data to. | +| | | Remote Connection Address | O | This information element indicates the IP address and port that the CS-TrGW can send user plane data to. May be present only if corresponding IE is present in the request. | +| NOTE 1: Remote Source Port and Remote Source Port Range are mutually exclusive.
NOTE 2: At least one of these IEs shall be present when policing is required. | | | | | + +### A.7.2.2.3 Reserve and Configure TrGW Connection Point + +This procedure is used to reserve and configure multimedia-processing resources for a termination at the CS-TrGW. + +**Table A.7.2.2.3.1: Reserve and Configure TrGW Connection Point** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------------------------|-----------|----------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserve and Configure TrGW Connection Point | CS-IBCF | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Emergency Call Indicator | O | This information element identifies the call as emergency call that requires a preferential handling. | +| | | Termination/ Termination Request | M | This information element indicates the existing bearer termination or requests a new termination for the bearer to be established. | +| | | IP Interface | O | This information element specifies the used interface type for the IP termination (e.g. ExtSIPI, NboIP). | +| | | Local IP Resources | O | This information element indicates the resource(s) (e.g. codec, auxiliary payload types) for which the CS-TrGW shall be prepared to receive user data, | +| | | Remote IP Resources | O | This information element indicates the resources (e.g. codec, auxiliary payload types) that the CS-TrGW shall use to send user data. | +| | | Reserve Value | O | This information element indicates if multiple IP resources are to be reserved. | +| | | Local Connection Address request | M | This information element requests an IP address and a port number on the CS-TrGW that the remote end can send user plane data to. | +| | | Remote Connection Address | M | This information element indicates the IP address and ports of the remote party that the CS-TrGW can send user plane data to. | +| | | Notify termination heartbeat | M | This information element requests termination heartbeat indications and may specify their periodicity. | +| | | Notify Released Bearer | O | This information element requests a notification of a released bearer. | +| | | IP Realm Identifier | O | This information element indicates the IP realm of the IP termination. | +| | | IP Version | C | This information element indicates the version of the internet protocol to be applied at the termination for the user plane. This is required for IP address translation. | +| | | DiffServ Code Point | O | This information element indicates a specific DiffServ code point to be used in the IP header in packets sent on the IP termination. | +| | | DiffServ Tagging Behaviour | O | This information element indicates whether the Diffserv code point in the IP header in packets sent on the IP termination should be copied from the received value or set to a specific value. | +| | | Remote Source Address Filtering | O | This information element indicates that remote source address filtering is required. | +| | | Remote Source Address Mask | C | This information element provides information on the valid remote source addresses. This may be included if remote source address filtering is included. It shall not be included if remote source address filtering is not included. | +| | | Remote Source Port Filtering | O | This information element indicates that remote source port filtering is required. | + +| | | | +|--------------------------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Remote Source Port | C | This information element identifies the valid remote source port. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| Remote Source Port Range | C | This information element identifies a range of valid remote source ports. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 1) | +| Media Inactivity Detection Required | O | This information element indicates that detection of inactive media flows is required. | +| Inactivity Detection Time | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection time. | +| Inactivity Detection Direction | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection direction. | +| RTCP handling | O | Indicates whether or not the CS-TrGW shall reserve a port for an RTCP flow. | +| Traffic Policing Required | O | This information element indicates that policing of the media flow is required. | +| Peak Data Rate | O | This information element may be present if Policing is required and specifies the permissible peak data rate for a media stream. (NOTE 2) | +| Sustainable Data Rate | O | This information element may be present if Policing is required and specifies the permissible sustainable data rate for a media stream. (NOTE 2) | +| Delay Variation Tolerance | O | This information element may be present if Policing on Peak Data Rate is required and specifies the maximum expected delay variation tolerance for the corresponding media stream. | +| Maximum Burst Size | C | This information element shall be present if Policing on Sustainable Data Rate is required and specifies the maximum expected burst size for the corresponding media stream. | +| STUN server request | O | This information element is present if CS-IBCF requests the CS-TrGW to answer STUN connectivity checks for ICE. | +| ICE Connectivity Check | C | This information element requests the CS-TrGW to perform ICE connectivity check as defined by IETF RFC 5245 [ab]. It is only applicable for full ICE. | +| Notify ICE Connectivity Check Result | C | This information element requests a notification of ICE connectivity check result. It is only applicable for full ICE. | +| Notify New Peer Reflexive Candidate | C | This information element requests a notification of new peer reflexive candidate was discovered during a connectivity check. It is only applicable for full ICE. | +| ICE password request | O | This information element is present if CS-IBCF requests an ICE password. | +| ICE Ufrag request | O | This information element is present if CS-IBCF requests an ICE ufrag. | +| ICE host candidate request | O | This information element is present if CS-IBCF requests an ICE host candidate. | +| ICE received candidate | O | This information element is present if CS-IBCF indicates a received candidate for ICE. | +| ICE received password | O | This information element is present if CS-IBCF indicates a received password for ICE. | +| ICE received Ufrag | O | This information element is present if CS-IBCF indicates a received Ufrag for ICE. | + +| | | | | | | +|---------------------------------------------------------------------------------|---------|----------------------------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | SDPCapNeg configuration | O | This information element provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. | | +| Reserve and Configure TrGW Connection Point Ack | CS-TrGW | Context | M | This information element indicates the context where the command was executed. | | +| | | Termination | M | This information element indicates the termination where the command was executed. | | +| | | Local IP Resources | C | This information element indicates the resources that the CS-TrGW has reserved to receive the user plane data from the remote side. This IE shall be present if it was contained in the request. If the IE was not contained in the request, it may be present in the reply. | | +| | | Remote IP Resources | O | This information element indicates the resource (i.e. codec) that the CS-TrGW shall use to send user data. | | +| | | Local Connection Addresses | M | This information element indicates the IP address and port on the CS-TrGW that shall receive user plane data. | | +| | | Remote Connection Address | O | This information element indicates the IP address and port that the CS-TrGW can send user plane data to. May be present only if corresponding IE is present in the request. | | +| | | ICE password | C | This information element shall be present only if it was contained in the request. It indicates the ICE password assigned by the CS-TrGW. | | +| | | ICE Ufrag | C | This information element shall be present only if it was contained in the request. It indicates the ICE Ufrag assigned by the CS-TrGW. | | +| | | ICE host candidate | C | This information element shall be present only if it was contained in the request. It indicates the ICE host candidate assigned by the CS-TrGW. | | +| | | ICE lite indication | C | This information element shall be present only if an ICE host candidate request was contained in the request, and the CS-TrGW supports ICE lite, but not full ICE. It indicates that the CS-TrGW only supports ICE lite. | | +| | | SDPCapNeg configuration | C | This information element shall be present only if it was contained in the request. It provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. | | +| NOTE 1: Remote Source Port and Remote Source Port Range are mutually exclusive. | | | | | | +| NOTE 2: At least one of these IEs shall be present when policing is required. | | | | | | + +#### A.7.2.2.4 Release TrGW Termination + +This procedure is used to release multimedia-processing resources for a termination at the CS-TrGW. + +**Table A.7.2.2.4.1: Release TrGW Termination** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------------|------------------|---------------------------------|-------------------------------------|------------------------------------------------------------------------------------| +| Release TrGW Termination | CS-IBCF | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the existing bearer termination to be released. | +| Release TrGW Termination Ack | CS-TrGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | + +### A.7.2.2.5 IP Bearer Released + +**Table A.7.2.2.5.1: IP Bearer Released** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------|------------------|---------------------------------|-------------------------------------|-----------------------------------------------------------------------------------------------| +| IP Bearer Released | CS-TrGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Termination | M | This information element indicates the bearer termination where the bearer was released. | +| | | Bearer Released | M | This information element notifies a bearer release. | +| | | Release Cause | M | This information element indicates the cause of a bearer release. | +| IP Bearer Released Ack | CS-IBCF | Context | M | This information element indicates all context are where the command was executed. | +| | | Termination | M | This information element indicates that Bearer termination is where the command was executed. | + +### A.7.2.2.6 Media Inactivity Detection + +This command is used to notify the CS-IBCF of media inactivity on the CS-TrGW. + +**Table A.7.2.2.6.1: Media Inactivity Notification** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------------|------------------|---------------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------------------------| +| Media Inactivity Notification | CS-TrGW | Context | M | This information element indicates the existing context for the bearer termination. | +| | | Termination | M | This information element indicates that bearer termination is where the media inactivity detection was activated. | +| | | Media Inactivity | M | This information element notifies the CS-IBCF of Media inactivity detection on the bearer termination. | +| Media Inactivity Notification Ack | CS-IBCF | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the bearer termination where the command was executed. | + +### A.7.2.2.7 Termination heartbeat indication + +This command is used by the CS-TrGW to periodically notify the CS-IBCF of a termination heartbeat. + +**Table A.7.2.2.7.1: Termination heartbeat indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------------------------------| +| Termination heartbeat indication | CS-TrGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the termination heartbeat is reported. | +| | | Termination heartbeat | M | Hanging Termination event | +| Termination heartbeat indication Ack | CS-IBCF | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### A.7.2.2.8 Change Through-Connection + +This procedure is used to change the Through-connection in the bearer termination. + +**Table A.7.2.2.8.1: Change Through-Connection** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------|-----------|-----------------------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| Change Through-Connection | CS-IBCF | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Bearer Termination/Bearer Termination Request | M | This information element indicates the existing bearer termination or requests a new Bearer termination where the through connection is changed. | +| | | Through-Connection | M | This information element indicates the through-connection of the bearer termination | +| Change Through-Connection Ack | CS-TrGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +NOTE: This procedure may be combined with Reserve and Configure TrGW Connection Point, Reserve TrGW Connection Point or Configure TrGW Connection Point procedure. This list of procedures is not exhaustive. + +### A.7.2.2.9 ICE Connectivity Check Result Notification + +This procedure is used to report ICE connectivity check result for Full ICE. + +**Table A.7.2.2.9.1: ICE Connectivity Check Result Notification** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------------------------------|-----------|------------------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------| +| ICE Connectivity Check Result Notification | CS-TrGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the ICE Connectivity Check Result is reported. | +| | | ICE Connectivity Check Result Indication | M | This information element indicates an ICE Connectivity Check Result event. | +| ICE Connectivity Check Result Notification Ack | CS-IBCF | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### A.7.2.2.10 ICE New Peer Reflexive Candidate Notification + +This procedure is used to report ICE new peer reflexive candidate for Full ICE. + +**Table A.7.2.2.10.1: ICE New Peer Reflexive Candidate Notification** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------------------------------|-----------|---------------------------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------| +| ICE New Peer Reflexive Candidate Notification | CS-TrGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the ICE New Peer Reflexive Candidate is reported. | +| | | ICE New Peer Reflexive Candidate Indication | M | This information element indicates an ICE New Peer Reflexive Candidate event. | +| ICE New Peer Reflexive Candidate Notification Ack | CS-IBCF | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +## A.7.2.3 Non-Call Related Procedures + +### A.7.2.3.1 Introduction + +The procedures detailed in table A.7.2.3.1 shall be applied for the CS-TrGW handling component of the Ix interface. Where a corresponding procedure in TS 23.205 [9] is specified, that procedure shall apply. Where no corresponding procedure in TS 23.205 [9] is specified, the procedure is specified in a clause of this specification. + +**Table A.7.2.3.1.1: Non-call related procedures** + +| Procedure defined in TS 29.238 [29] | Corresponding Procedure defined in TS 23.205 [9] | Remarks | +|------------------------------------------------|--------------------------------------------------|--------------------------------------------------------------------------------------------------------------------| +| TrGW Out of service | MGW Out of Service | | +| TrGW Communication Up | MGW Communication Up | | +| TrGW Restoration | MGW Restoration | | +| TrGW Register | MGW Register | | +| TrGW Re-register | MGW Re-register | | +| CS-IBCF Ordered Re-register | (G)MSC Server Ordered Re-register | | +| CS-IBCF Restoration | (G)MSC Server Restoration | | +| CS-IBCF Out of Service | (G)MSC Server Out of Service | | +| Termination Out-of-Service | Termination Out-of-Service | The "Termination Out-of-Service procedure" is also used as a call-related H.248 command | +| Audit Value | Audit Value | | +| Command Rejected | Command Rejected | The "Command Rejected" procedure may be used in response both to call-related and non-call-related H.248 Commands. | +| TrGW Capability Change | Capability Update | | +| TrGW Resource Congestion Handling - Activate | MGW Resource Congestion Handling - Activate | | +| TrGW Resource Congestion Handling - Indication | MGW Resource Congestion Handling - Indication | | +| Inactivity timeout activation | Inactivity timeout activation | | +| Inactivity timeout indication | Inactivity timeout indication | | +| Realm Availability Change Activate | | See clause A.7.2.3.2. | +| Realm Availability Change Indication | | See clause A.7.2.3.3. | + +### A.7.2.3.2 Realm Availability Change - Activate + +This procedure is used to activate the realm availability notification mechanism. + +**Table A.7.2.3.2.1: Realm Availability Change - Activate** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------------------|-----------|------------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| Realm Availability Change - Activate | CS-IBCF | Context | M | This information element indicates the NULL context. | +| | | Root Termination | M | This information element indicates that root termination is where the realm availability change notification mechanism is activated. | +| | | Realm Availability Change Activate | M | This information element requests to activate the realm availability change notification mechanism. | +| Realm Availability Change -Activate Ack | TrGW | Context | M | This information element indicates the NULL context. | +| | | Root Termination | M | This information element indicates that root termination is where the command was executed. | + +### A.7.2.3.3 Realm Availability Change - Indication + +This procedure is used to inform the CS-IBCF that there has been a change to the list of currently available realms. + +**Table A.7.2.3.3.1: Realm Availability Change - Indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------------------------|-----------|-------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Realm Availability Change - Indication | TrGW | Context | M | This information element indicates the NULL context. | +| | | Root Termination | M | This information element indicates that root termination is where the realm availability change notification mechanism was activated. | +| | | Changes to Realm Availability | M | This information element indicates the changes to the list of available realms. | +| Realm Availability Change - Indication Ack | CS-IBCF | Context | M | This information element indicates the NULL context. | +| | | Root Termination | M | This information element indicates that root termination is where the command was executed. | + +## A.8 (G)MSC - CS-MGW Interaction + +### A.8.1 General + +#### A.8.1.1 Network Model + +figure A.8.1.1.1 shows the network model. The squared line represents the call control signalling. The dotted line represents the bearer control signalling (if applicable) and the user plane. The (G)MSC uses one context with at least two terminations in the CS-MGW. The termination T1 is used towards the 3GPP PLMN and the bearer termination T2 is used for the bearer towards the external IP network. + + + +Figure A.8.1.1.1: H.248 Context Model diagram showing a 3GPP PLMN connected to a (G)MSC, which is connected to a CS-MGW. The CS-MGW has two terminations, T1 and T2, connected to an External Network. The (G)MSC and CS-MGW are connected by a solid line (call control signalling). The 3GPP PLMN and (G)MSC are connected by a dotted line (bearer control signalling). The CS-MGW and External Network are connected by a dotted line (bearer control signalling). + +**Figure A.8.1.1.1: H.248 Context Model** + +#### A.8.1.2 Signalling flows + +The signalling flows in A.7.1.2 apply with the following additions: + +- Instead of the procedure Reserve TrGW Connection Point the procedure Reserve RTP Connection Point as defined by TS 23.205 [9] is used. +- Instead of the procedure Reserve and Configure TrGW Connection Point the procedure Reserve and Configure RTP Connection Point as defined by TS 23.205 [9] is used. +- Instead of the procedure Configure TrGW Connection Point the procedure Configure RTP Connection Point as defined by TS 23.205 [9] is used. + +--- + +## Annex B (normative): + +# Additional Interworking Procedures between a SIP-I based circuit-switched Core Network and the IP Multimedia (IM) Core Network (CN) Subsystem to Support Special Services + +## B.1 General + +The present annex describes additional interworking between a SIP-I based circuit-switched core network and the IP Multimedia (IM) Core Network (CN) Subsystem to interwork special services such as global text telephony. Those procedures apply in combination with the procedures in clause 7. + +The procedures in the present Annex are optional. However, if a special service covered in this Annex is interworked, the procedures in the corresponding clause of this Annex shall be applied. + +--- + +## B.2 Global Text Telephony + +Global Text Telephony (GTT) offers real time conversation in text, optionally combinable with voice. GTT is mainly used for distant conversation with hearing or speech impaired users. + +GTT is supported in IMS via the Real-Time Text protocol over RTP, using IETF SIP/SDP for the negotiation of the text media and IETF RFC 4103 [47] RTP-text for transport, with text coded according to ITU-T Recommendation T.140 [46]. See TS 23.226 [45] and TS 26.114 [52]. + +Within a SIP-I based circuit-switched Core Network the default PCM codec is used to transport the PTSN inband text telephony format. PCM will also be negotiated as codec within SIP-I /SDP, without further information allowing identifying a call using global text telephony. Different specified systems for text telephony exist as PTSN inband text telephony format and are used in different regions, e.g. Baudot (in US), EDT, V.21, Bell103, Minitel and V.18. They are described in the annexes of ITU-T V.18 [48]. + +The Interworking procedures in Annex I of TS 29.163 [13] shall be applied with the following clarifications: + +- Where ISUP signalling is mentioned or depicted, the corresponding SIP-I signalling is applicable. + +## Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|------|-----|--------------------------------------------------|-------------------------------------------------------------------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 06/2014 | TSG#64 | CP-140397 | 0101 | 3 | ICE support for Ix towards SIP-I based CS CN | 11.3.0 | 12.0.0 | +| 06/2015 | TSG#68 | CP-150351 | 0102 | - | Bearer Termination in Acknowledgements | 12.0.0 | 12.1.0 | +| 12/2015 | TSG#70 | CP-150667 | 0103 | 6 | Stage 2 Ix supporting SDP capability negotiation | 12.1.0 | 13.0.0 | +| Change history | | | | | | | | +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +| 03/2016 | CT#71 | CP-160105 | 0104 | - | F | Removal of references to TS 26.235 and TS 26.236 | 13.1.0 | +| 03/2017 | CT#75 | CP-170087 | 0105 | 1 | F | Correction to reference model | 14.0.0 | +| 06/2018 | CT#80 | | | | | Automatic upgrade from previous Release | 15.0.0 | +| 12/2018 | CT#82 | CP-183121 | 0113 | 1 | A | Removal of Editor's notes for supplementary services interworking | 15.1.0 | +| 2020-07 | SA#88e | - | - | - | | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/29_series/29250/06da11ab76cacc38bbcd714e437797ea_img.jpg b/marked/Rel-16/29_series/29250/06da11ab76cacc38bbcd714e437797ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..919330c7c99ba78684ecc50ad736d3ad01dc159f --- /dev/null +++ b/marked/Rel-16/29_series/29250/06da11ab76cacc38bbcd714e437797ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b268420450c1781b78e76162499ad70f07fb33a26736f8a612f94ca35fe8dcde +size 5792 diff --git a/marked/Rel-16/29_series/29250/20136850feb70fd71c7d41cdae203ebb_img.jpg b/marked/Rel-16/29_series/29250/20136850feb70fd71c7d41cdae203ebb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a015729cc949ba83778c9c88cd42c9848dc0fa71 --- /dev/null +++ b/marked/Rel-16/29_series/29250/20136850feb70fd71c7d41cdae203ebb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6843778665566ab7535e4dffad603281eb18c504cd372da433174b7af32478b +size 16555 diff --git a/marked/Rel-16/29_series/29250/99bae07626f60f9ede10e2e387ef7051_img.jpg b/marked/Rel-16/29_series/29250/99bae07626f60f9ede10e2e387ef7051_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae2fe1edfa74cb8e4a953200bcfa82b25190682e --- /dev/null +++ b/marked/Rel-16/29_series/29250/99bae07626f60f9ede10e2e387ef7051_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ec2f0ee2463b2c022c550c3aabe5cd336491373d057940af2a045c7cffe2f88 +size 34571 diff --git a/marked/Rel-16/29_series/29250/raw.md b/marked/Rel-16/29_series/29250/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..aefbd46f0ef17618b79529ce6a7cb63bde5cadb5 --- /dev/null +++ b/marked/Rel-16/29_series/29250/raw.md @@ -0,0 +1,1203 @@ + + + + + + +# Contents + +| | | +|----------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 Nu reference point..... | 7 | +| 4.1 Overview ..... | 7 | +| 4.2 Nu reference model ..... | 7 | +| 4.3 Functional elements..... | 8 | +| 4.3.1 PFDF..... | 8 | +| 4.3.2 SCEF..... | 8 | +| 4.4 Procedures over Nu reference point..... | 8 | +| 4.4.1 Management of PFD..... | 8 | +| 4.4.2 PFD management notification ..... | 9 | +| 5 Nu protocol ..... | 9 | +| 5.1 Introduction ..... | 9 | +| 5.2 Transport layer ..... | 10 | +| 5.3 Application delivery layer..... | 10 | +| 5.3.1 General ..... | 10 | +| 5.3.2 HTTP status codes..... | 10 | +| 5.3.3 Methods ..... | 10 | +| 5.3.4 Resources and URI design..... | 11 | +| 5.3.5 HTTP request/response formats ..... | 11 | +| 5.3.5.1 General..... | 11 | +| 5.3.5.2 POST /nuapplication/provisioning ..... | 12 | +| 5.3.5.3 POST /nuapplication/notification ..... | 14 | +| 5.3.6 Feature negotiation ..... | 15 | +| 5.3.6.1 General..... | 15 | +| 5.3.6.2 HTTP custom headers..... | 16 | +| 5.3.6.2.1 3gpp-Optional-Features..... | 16 | +| 5.3.6.2.2 3gpp-Required-Features ..... | 16 | +| 5.3.6.2.3 3gpp-Accepted-Features..... | 16 | +| 5.4 Specific application communication ..... | 17 | +| 5.4.1 General ..... | 17 | +| 5.4.2 Content type..... | 17 | +| 5.4.3 JSON provisioning fields ..... | 17 | +| 5.4.3.1 General..... | 17 | +| 5.4.3.2 scef-notification-uri ..... | 17 | +| 5.4.4 Void..... | 18 | +| 5.4.5 JSON errors and informational response fields..... | 18 | +| 5.4.5.1 General..... | 18 | +| 5.4.6 JSON report fields ..... | 18 | +| 5.4.6.1 General..... | 18 | +| 5.4.6.2 pfd-reports..... | 18 | +| 5.4.6.3 application-ids..... | 19 | +| 5.4.7 JSON notification fields ..... | 19 | +| 5.4.7.1 General..... | 19 | +| 5.4.7.2 notification-pfd-reports ..... | 19 | +| 5.4.7.3 user-plane-location-area..... | 20 | +| 5.4.7.4 cell-ids..... | 20 | +| 5.4.7.5 enodeb-ids..... | 20 | +| 5.4.7.6 extended-enodeb-ids ..... | 20 | +| 5.4.7.7 routing-area-ids..... | 20 | +| 5.4.7.8 tracking-area-ids ..... | 21 | +| 5.5 PFDF discovery..... | 21 | + +| | | | +|-------------------------------|-----------------------------------------------|-----------| +| 5.6 | SCEF discovery..... | 21 | +| 6 | Secure communication..... | 21 | +| Annex A (informative): | JSON Schema ..... | 21 | +| A.1 | Provisioning schema ..... | 21 | +| A.2 | Error and Informational response schema ..... | 23 | +| A.3 | PFD management notification schema ..... | 25 | +| Annex B (informative): | Call Flows..... | 28 | +| B.1 | General..... | 28 | +| B.2 | Provisioning of PFDs ..... | 28 | +| Annex C (informative): | Change history..... | 29 | + +# --- 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 provides the stage 3 specification of the Nu reference point. The functional requirements and the stage 2 specifications of the Nu reference point are specified in 3GPP TS 23.682 [2]. The Nu reference point lies between the Packet Flow Description Function (PFDF) and the Service Capability Exposure Function (SCEF). + +# 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.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [3] 3GPP TS 23.203: "Policy and charging control architecture". +- [4] 3GPP TS 29.213: "Policy and Charging Control signalling flows and QoS parameter mapping". +- [5] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security". +- [6] IETF RFC 2818: "HTTP Over TLS". +- [7] IETF RFC 793: "Transmission Control Protocol". +- [8] Void. +- [9] 3GPP TS 29.251: "Gw and Gwn reference points for sponsored data connectivity". +- [10] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". +- [11] IETF RFC 7159: "The JavaScript Object Notation (JSON) Data Interchange Format". +- [12] IETF draft-newton-json-content-rules-09: "A Language for Rules Describing JSON Content". + +NOTE: This individual draft will not further progress in IETF. It is available from the following link: +
(NOTE 1) | 5.3.5.2 | Content-Type:
application/json
The SCEF shall include PFDs content associated with application identifier(s) using the schema defined in Annex A. | SCEF | Successful response: The PFDF may include informational data in the body of the response in Annex A. | +| POST | {sceF-notification-uri}
or
/nuapplication/notification
(NOTE 2) | 5.3.5.3 | Content-Type:
application/json
The PFDF shall include notification result and application identifier(s) using the schema defined in Annex A. | PFDF | | + +NOTE 1: A different path from /nuapplication/provisioning may be used when it is configured in the SCEF. In that case the "path" part set in the different methods should use the configured one. + +NOTE 2: A different path from /nuapplication/notification may be used when it is configured in the PFDF and no sceF-notification-uri is received in the provisioning POST. In that case the "path" part set in the different methods should use the configured one. + +#### 5.3.5.2 POST /nuapplication/provisioning + +The provisioning of the PFDs shall be performed by the SCEF by using the POST method as follows: + +- The request URI formatted as defined in subclause 5.3.4 with the "path" part set to: /nuapplication/provisioning. +- The Content-Type header field set to "application/json" +- The body of the message encoded in JSON format as defined in Annex A. The body shall include + - for the PFD(s) creation for a new application identifier, a new application identifier and its full list of PFD(s) to be created; + - for the PFD(s) full update for an existing application identifier, the existing application identifier and its new full list of PFD(s) + - for the PFD(s) partial update for an existing application identifier, the existing application identifier, partial update indication and + - new PFD(s) with new PFD identifier(s) to add new PFD(s), + - new PFD(s) with existing PFD identifier(s) to update existing PFD(s), and/or + - the existing PFD identifier(s) without any content to remove the existing PFD(s); + - for the PFD(s) removal for an existing application identifier, the existing application identifier and the removal indication. + +Upon receipt of the HTTP POST request, the PFDF shall respond to the SCEF indicating whether the provisioning was successful or not using one of the HTTP status codes as defined in subclause 5.3.2. If the provisioning was accepted, the + +PFDF shall respond with an HTTP 200 OK status code if no resource is created, or an HTTP 201 Created status code if one or more resources are created. If the allowed delay is too short according to the criteria in subclause 4.4.1, the PFDF shall respond with an HTTP 200 OK status code and additional information in the body of the response indicating failure reason "too short allowed delay" and the value of caching time as defined in Annex A. If the provisioning was rejected, the PFDF shall indicate the reason using an appropriate HTTP status code as defined in subclause 5.3.2 and optionally additional information in the body of the response as defined in Annex A. + +Below is an example of an HTTP POST and a corresponding successful response: + +POST /nuapplication/provisioning HTTP/1.1 + +Host: pfdserver.example.com + +Content-Type: application/json + +Content-Length: ... + +``` +[ +{ + "application-identifier":"test-application-1", + "removal-flag":true +}, +{ + "application-identifier":"test-application-2", + "allowed-delay":600, + "pfds":[ + { + "pfd-identifier":"pfd1", + "flow-descriptions":[ + "permit in ip from 10.68.28.39 80 to any" + ] + }, + { + "pfd-identifier":"pfd2", + "urls":[ + "^http://test.example.com(/\\S*)?$" + ] + } + ], + "partial-flag":true +} +``` + +``` + +"pfds":[ +{ + "pfd-identifier":"pfd3", + "urls":[ + "^http://test.example2.net(/\\S*)?$" + ] +}, +{ + "pfd-identifier":"pfd4" +} +] +} +] + +``` + +Here is an example of a successful response: + +HTTP/1.1 200 OK + +Date: Mon, 7 May 2012 16:00:00 GMT + +Server: pfdserver.example.com + +Content-Type: application/json + +``` + +{ + "success-message": "Notification was processed successfully.", +} + +``` + +#### 5.3.5.3 POST /nuapplication/notification + +The notification of the PFD management shall be performed by the PFDF by using the POST method as follows: + +- The request URI formatted as defined in subclause 5.3.4 with the "path" part set to: /nuapplication/notification. +- The Content-Type header field set to "application/json". +- The body of the message encoded in JSON format as defined in Annex A. The body shall include the pfd-report. + +Upon receipt of the HTTP POST request, the SCEF shall respond to the PFDF with HTTP 200 OK status code. + +Below is an example of an HTTP POST and a corresponding response: + +POST /nuapplication/notification HTTP/1.1 + +Host: scefserver.example.com + +Content-Type: application/json + +Content-Length: ... + +``` + +{ + "notification-pfd-reports": [ + { + +``` + +``` + + "application-ids": ["test-application-1", "test-application-2", "test-application-3"], + "pfd-failure-code": "PARTIAL_FAILURE", + "user-plane-location-area": { + "cell-ids" : ["46000045BD6007", "46000045BD6008"], + "tracking-area-ids" : ["46000063F8", "46000063F9"] + } +} +] +} + +``` + +Here is an example of a response: + +HTTP/1.1 200 OK + +Date: Mon, 7 May 2018 16:00:00 GMT + +Server: scefserver.example.com + +Content-Type: application/json + +### 5.3.6 Feature negotiation + +#### 5.3.6.1 General + +The REST based Nu interface needs to provide a mechanism to advertise required and optional features supported by both the SCEF and PFDF for interoperability reasons as the functionality of the REST Nu based interface is augmented. + +Feature negotiation shall take place during the first interaction (i.e. HTTP POST in provisioning) between the PFDF and the SCEF. The client shall include in the HTTP request the set of supported features as follows: + +- if a feature is required for the proper operation of the application, it shall be included within the 3gpp-Required-Features header; +- if a feature is optional for the proper operation of the application, it shall be included within the 3gpp-Optional-Features header. + +The server shall include, within the 3gpp-Accepted-Features header in the HTTP response, the set of features it supports in common with the client. + +If the server does not support any of the required features advertised by the client within the 3gpp-Required-Features header, the server shall reject the HTTP request with an HTTP 412 Precondition Failed status code and shall include the commonly supported features with the client within the 3gpp-Accepted-Features. + +If the server requires certain features to be supported that are not advertised by the client, the server shall reject the HTTP request with an HTTP 412 Precondition Failed status code and shall include the commonly supported features with the client within the 3gpp-Accepted-Features and the required features in the 3gpp-required-features. + +If the SCEF and the PFDF successfully negotiate supported features, the list of commonly supported features shall be applicable for the lifetime of the application. Features that are not advertised as supported shall not be used. + +The sender may send information that is related to the supported features. Any unrecognized information shall be ignored by the receiver. + +The table below defines the features applicable to the Nu interface. + +**Table 5.3.6.1-1: Features used in Nu Interface** + +| Feature | M/O | Description | +|-------------------------------------------------------------------------------------------------------------------------|-----|---------------------------------------------------------------------------------------------------| +| DomainNameProtocol | O | This feature supports the additional protocol matching condition for the domain name in PFD data. | +| PfdMgmtNotification | O | This feature supports the PFD management notification. | +| Feature: A short name for the feature to which the M/O and description pertain. | | | +| M/O: Indication on whether the implementation of the feature is mandatory ("M") or optional ("O") in this 3GPP Release. | | | +| Description: Textual description of the feature. | | | + +NOTE: The base functionality for the Nu interface is defined in the Release-14 version of this specification and a feature is an extension of that functionality. The negotiation of supported features allows interworking between the endpoints of the Nu interface whereby each entity may support all, some, or none of the features that the Nu application can support defined in this specification. Features are defined so that they are independent of each other. Any introduced feature is explicitly defined in this specification. + +Since a post Release-16 version of SCEF does not send any supported feature information, the interworking PFDF supporting Release-16 version does not need to send any information related to supported feature and both sides shall behave as specified in the Release-14 version of this specification. + +A post Release-16 version of PFDF may receive supported feature information from a Release-16 version of SCEF, those information will be ignored by the PFDF and both sides shall behave as specified in the Release-14 version of this specification. + +#### 5.3.6.2 HTTP custom headers + +This subclause defines any new HTTP custom headers introduced by this specification. + +##### 5.3.6.2.1 3gpp-Optional-Features + +This header is used by the client to advertise the optional features that are supported by the client. + +The encoding of the header follows the ABNF as defined in IETF RFC 7230 [13]. + +3gpp-Optional-Features = "3gpp-Optional-Features" ":" 1#token + +An example is: 3gpp-Optional-Features: feature1, feature2 + +##### 5.3.6.2.2 3gpp-Required-Features + +This header is used by the client to announce the mandatory features that must be supported in the server. + +This header is also used by the server to indicate the missing features that must be supported in the client. + +The encoding of the header follows the ABNF as defined in IETF RFC 7230 [13]. + +3gpp-Required-Features = "3gpp-Required-Features" ":" 1#token + +An example is: 3gpp-Required-Features: feature1, feature2 + +##### 5.3.6.2.3 3gpp-Accepted-Features + +The header is used by the server to confirm the commonly supported set of features with the client. + +The encoding of the header follows the ABNF as defined in IETF RFC 7230 [13]. + +3gpp-Accepted-Features = "3gpp-Accepted-Features" ":" 1#token + +An example is: 3gpp-Accepted-Features: feature1, feature2 + +## 5.4 Specific application communication + +### 5.4.1 General + +Specific application communication represents the presentation of application data structures by transforming data into the form that the application accepts. It establishes the context between application-layer entities. + +NOTE: This release only supports the content type JSON. + +### 5.4.2 Content type + +The body of HTTP messages shall be in JSON format. The content of the JSON text is defined in subclause 5.4.3 and Annex A. + +The MIME media type that shall be used within the Content-Type header field is "application/json" as defined in IETF RFC 7159 [11]. + +### 5.4.3 JSON provisioning fields + +#### 5.4.3.1 General + +Table 5.4.3.1-1 describes the JSON provisioning fields used within the body of the HTTP messages representing the PFDs information associated with an application identifier. The table includes the information about the name of the field and the type of the fields. + +**Table 5.4.3.1-1: Nu Provisioning JSON fields** + +| Field Name | Clause defined | JSON Value Type
(NOTE 1) | JCR Type
(NOTE 2) | Applicability
(NOTE 4) | +|------------------------|--------------------|-----------------------------|----------------------|---------------------------| +| application-identifier | 3GPP TS 29.251 [9] | string | string | | +| allowed-delay | 3GPP TS 29.251 [9] | number | uint64 | | +| pfdids | 3GPP TS 29.251 [9] | array | array | | +| pfd-identifier | 3GPP TS 29.251 [9] | string | string | | +| flow-descriptions | 3GPP TS 29.251 [9] | array | array | | +| urls | 3GPP TS 29.251 [9] | array | array | | +| domain-names | 3GPP TS 29.251 [9] | array | array | | +| removal-flag (NOTE 3) | 3GPP TS 29.251 [9] | boolean | boolean | | +| partial-flag (NOTE 3) | 3GPP TS 29.251 [9] | boolean | boolean | | +| dn-protocol | 3GPP TS 29.251 [9] | string | string | DomainNameProtocol | +| scef-notification-uri | 5.4.3.2 | string | string | PfdMgmtNotification | + +NOTE 1: The basic JSON value types are defined in IETF RFC 7159 [11]. +NOTE 2: The JCR types are defined in IETF draft-newton-json-content-rules [12]. +NOTE 3: Only one of the removal-flag and the partial-flag for the application identifier shall be set to true. +NOTE 4: Fields marked with a supported feature are applicable as described in subclause 5.3.6. + +#### 5.4.3.2 scef-notification-uri + +The scef-notification-uri is of type string indicating the SCEF sent URI for receiving notifications. + +### 5.4.4 Void + +### 5.4.5 JSON errors and informational response fields + +#### 5.4.5.1 General + +Table 5.4.4.1-1 describes the JSON fields defined for the errors and informational responses including their types and the field names. + +**Table 5.4.5.1-1: JSON fields for errors and informational response** + +| Field Name | Subclause defined | JSON Value Type (NOTE 1) | JCR Type (NOTE 2) | Applicability (NOTE 5) | +|-----------------|-----------------------------|--------------------------|-----------------------------------------------------------------|------------------------| +| errors | 3GPP TS 29.251 [9] (NOTE 4) | array | array | | +| error-type | 3GPP TS 29.251 [9] (NOTE 4) | string | "application"
"interface"
"server"
"other"
(NOTE 3) | | +| error-message | 3GPP TS 29.251 [9] | string | string | | +| error-tag | 3GPP TS 29.251 [9] | string | string | | +| error-path | 3GPP TS 29.251 [9] | string | string | | +| error-info | 3GPP TS 29.251 [9] | object | object | | +| success-message | 3GPP TS 29.251 [9] | string | string | | +| success-path | 3GPP TS 29.251 [9] | string | string | | +| success-info | 3GPP TS 29.251 [9] | object | object | | + +NOTE 1: The basic JSON value types are defined in IETF RFC 7159 [11]. +NOTE 2: The JCR types are defined in IETF draft-newton-json-content-rules [12]. +NOTE 3: The quoted strings for a string type. +NOTE 4: The error is sent from the PPDF to the SCEF. +NOTE 5: Fields marked with a supported feature are applicable as described in subclause 5.3.6. + +### 5.4.6 JSON report fields + +#### 5.4.6.1 General + +Table 5.4.6.1-1 describes the JSON fields defined for the report information objects which are included in the error-info field. + +**Table 5.4.6.1-1: JSON fields for Report from the PPDF** + +| Field Name | Subclause defined | JSON Value Type (NOTE 1) | JCR Type (NOTE 2) | Applicability (NOTE 4) | +|------------------|-----------------------------|--------------------------|-------------------|------------------------| +| pfd-reports | 5.4.6.2 | array | array | | +| application-ids | 5.4.6.3 | array | array | | +| pfd-failure-code | 3GPP TS 29.251 [9] (NOTE 3) | string | string | | +| caching-time | 3GPP TS 29.251 [9] | number | uint64 | | + +NOTE 1: The basic JSON value types are defined in IETF RFC 7159 [11]. +NOTE 2: The JCR types are defined in IETF draft-newton-json-content-rules [12]. +NOTE 3: The additional failure reasons for Nu are "TOO\_SHORT\_ALLOWED\_DELAY". +NOTE 4: Fields marked with a supported feature are applicable as described in subclause 5.3.6. + +#### 5.4.6.2 pfd-reports + +The pfd-reports field is of type array and it contains a list of pfd reports. + +The pfd-reports field can be used in an HTTP response to report failures in the installation/modification of PFDs. In this case, it shall be provided as a sub field of the error-info field. + +Multiple pfd report instances shall be provided within the pfd-reports field if different pfd-failure-code values are applicable within the same HTTP response. + +caching-time field is included if the pfd-failure-code is set to the value "TOO\_SHORT\_ALLOWED\_DELAY". + +A report instance shall contain application-ids and pfd-failure-code fields. + +The JCR format for the pfd-reports is: + +\$pfd-reports = "pfd-reports" : [ + +``` +{ $application-ids, + $pfd-failure-code, +``` + +\$aching-time, + +} + + +] + +#### 5.4.6.3 application-ids + +The application-ids field is of type array of string, and contains one or more application identifiers to which the PFDs belong. + +### 5.4.7 JSON notification fields + +#### 5.4.7.1 General + +Table 5.4.7.1-1 describes the JSON notification fields used within the body of the HTTP messages. The table includes the information about the name of the field and the type of the fields. + +**Table 5.4.7.1-1: Nu Notification JSON fields** + +| Field Name | Clause defined | JSON Value Type (NOTE 1) | JCR Type (NOTE 2) | Applicability (NOTE 3) | +|--------------------------|------------------------------|--------------------------|-------------------|------------------------| +| notification-pfd-reports | 5.4.7.2 | array | array | PfdMgmtNotification | +| application-ids | 5.4.6.3 | array | array | PfdMgmtNotification | +| pfd-failure-code | 3GPP TS 29.251 [9] ( NOTE 4) | string | string | PfdMgmtNotification | +| user-plane-location-area | 5.4.7.3 | object | object | PfdMgmtNotification | +| cell-ids | 5.4.7.4 | array | array | PfdMgmtNotification | +| enodeb-ids | 5.4.7.5 | array | array | PfdMgmtNotification | +| extended-enodeb-ids | 5.4.7.6 | array | array | PfdMgmtNotification | +| routing-area-ids | 5.4.7.7 | array | array | PfdMgmtNotification | +| tracking-area-ids | 5.4.7.8 | array | array | PfdMgmtNotification | + +NOTE 1: The basic JSON value types are defined in IETF RFC 7159 [11]. +NOTE 2: The JCR types are defined in IETF draft-newton-json-content-rules [12]. +NOTE 3: Fields marked with a supported feature are applicable as described in subclause 5.3.6. +NOTE 4: The additional failure reasons for Nu are "PARTIAL\_FAILURE". + +#### 5.4.7.2 notification-pfd-reports + +The notification-pfd-reports field is of type array and it contains a list of pfd reports. + +The notification-pfd-reports field can be used in an HTTP POST to notify the failures in the installation/modification of PFDs. In this case, it shall be included in the body of the message. + +Multiple pfd report instances shall be provided within the notification-pfd-reports field if different pfd-failure-code values are applicable within the same HTTP response. + +user-plane-location-area field is included if the pfd-failure-code is set to the value "PARTIAL\_FAILURE". + +A report instance shall contain application-ids and pfd-failure-code fields. + +The JCR format for the notification-pfd-reports is: + +``` +$notification-pfd-reports = "notification-pfd-reports" : [ +{ + $application-ids, + $pfd-failure-code, + $user-plane-location-area ? +} + +] +``` + +#### 5.4.7.3 user-plane-location-area + +The user-plane-location-areas field is of type object and it contains location areas of the user plane(s) which can not enforce the PFD(s) successfully. + +The JCR format for the user-plane-location-area is: + +``` +$user-plane-location-area = // : { + $cell-ids ?, + $enodeb-ids ?, + $extended-enodeb-ids ?, + $routing-area-ids ?, + $tracking-area-id ? +} +``` + +#### 5.4.7.4 cell-ids + +The cell-ids is of type string array and it contains a list of Cell Global Identities served by the user plane(s) which can not enforce the PFD(s) successfully. The content of the string has the same encoding as defined in subclause 8.21.1 of 3GPP TS 29.274 [19]. + +#### 5.4.7.5 enodeb-ids + +The enodeb-ids is of type string array and it contains a list of eNodeB identities served by the user plane(s) which can not enforce the PFD(s) successfully. The content of the string has the same encoding as defined in subclause 8.21.7 of 3GPP TS 29.274 [19]. + +#### 5.4.7.6 extended-enodeb-ids + +The enodeb-ids is of type string array and it contains a list of eNodeB identities served by the user plane(s) which can not enforce the PFD(s) successfully. The content of the string has the same encoding as defined in subclause 8.21.8 of 3GPP TS 29.274 [19]. + +#### 5.4.7.7 routing-area-ids + +The routing-area-ids is of type string array and it contains a list of Routing Area Identities served by the user plane(s) which can not enforce the PFD(s) successfully. The content of the string has the same encoding as defined in subclause 8.21.3 of 3GPP TS 29.274 [19]. + +#### 5.4.7.8 tracking-area-ids + +The tracking-area-ids is of type string array and it contains a list of Tracking Area Identities served by the user plane(s) which can not enforce the PFD(s) successfully. The content of the string has the same encoding as defined in subclause 8.21.4 of 3GPP TS 29.274 [19]. + +## 5.5 PFDF discovery + +The PFDF URI may be pre-configured on the SCEF. + +The SCEF may select the PFDF by this configuration. + +## 5.6 SCEF discovery + +The SCEF notification URI may be pre-configured on the PFDF. + +The SCEF notification URI may also be sent to the PFDF in the PFD provisioning. + +The PFDF may select the SCEF by the pre-configuration or use the notification URI received in the PFD provisioning. + +# 6 Secure communication + +Either the NDS/IP network layer security defined in 3GPP TS 33.210 [5] or HTTP over TLS as defined in IETF RFC 2818 [6] should be used to secure communication over the REST based Nu interface. + +# Annex A (informative): JSON Schema + +## A.1 Provisioning schema + +This subclause defines the JSON schema for the body of HTTP request providing the provisioned PFDs. The schema is based on IETF draft-newton-json-content-rules [12] and is defined below: + +``` +# jcr-version 0.7 +``` + +``` +# ruleset-id 3gpp.nuapplication.provisioning +``` + +``` +# import 3gpp.gwapplication.pfds as pfds +``` + +``` +; JCR representing the PFDs provisioning data +``` + +``` +$provisioning-root = @ {root} { +``` + +``` + $application-identifier, +``` + +``` + $removal-flag ?, +``` + +``` + $partial-flag ?, +``` + +``` + $allowed-delay ?, +``` + +``` + $pfds ?, +``` + +``` + $scefn-notification-uri ? +``` + +``` +} +``` + +``` +; An array list of the PFDs for multiple application identifiers +``` + +``` +$pfds-array-root = @ {root} [ $provisioning-root * ] +``` + +``` +; The detected application traffic identifier for the PFDs +``` + +``` +$application-identifier = "application-identifier" : string +``` + +``` +; The allowed delay time for the PFDs deployment +``` + +``` +$allowed-delay = "allowed-delay" : uint64 +``` + +``` +; The PFDs associated with the same application identifier +``` + +``` +$pfds = "pfds" : [ $pfd * ] +``` + +``` +; The PFD content +``` + +``` + +$pid = { + $pid-identifier, + ( $flow-descriptions | $urls | $domain-names | // : any) ?, + $pids.dn-protocol ? +} + +; The PFD identifier +$pid-identifier = "pid-identifier" : string + +; The flow descriptions +$flow-descriptions = "flow-descriptions" : [ string + ] + +; The url matching expressions +$urls = "urls" : [ string + ] + +; The domain name match criteria +$domain-names = "domain-names" : [ string + ] + +; A flag indicates whether this is a removal or not +$removal-flag = "removal-flag" : boolean + +; A flag indicates whether this is a partial update or not +$partial-flag = "partial-flag" : boolean + +; The URI in the SCEF for receiving notifications from the PPDF +$scef-notification-uri = "scef-notification-uri" : string + +``` + +## A.2 Error and Informational response schema + +This subclause defines the JSON schema for the body of HTTP responses in case of errors or success. The schema is based on IETF draft-newton-json-content-rules [12] and is defined below: + +``` + +# jcr-version 0.7 + +# ruleset-id 3gpp.nuapplication.info + +; A JCR for the error/successful response body +; Errors information + +``` + +\$errors-root = @ {root} { \$errors } + +; Success information + +\$success-root = @ {root} { + \$success-message, + \$success-path ?, + \$success-info ? +} + +; Resource fields definitions + +; The list of errors returned in responses sent by the PCEF/TDF + +\$errors = "errors" : [ +{ + \$error-type, + \$error-message, + \$error-tag ?, + \$error-path ?, + \$error-info ? +} + +] + +; The error type for an error. It can be one of 'application', 'interface', 'server' and 'other'. + +\$error-type = "error-type" : ( "application" | "interface" | "server" | "other" ) + +; The error text message + +\$error-message = "error-message" : string + +; The error tag for a specific error + +\$error-tag = "error-tag" : string + +; A JSON pointer path to the error resource + +\$error-path = "error-path" : string + +; Any additional information for the error + +\$error-info = "error-info" : { + +``` +$pfd-reports ?, + // : any * +} + +; Report fields definitions +; The list of pfd reports sent to the SCEF +$pfd-reports = "pfd-reports" : [ +{ + $application-ids, + $pfd-failure-code, + $caching-time +} + +] + +; The application identifiers for the PFDs +$application-ids = "application-ids" : [string+] + +; The string format for the pfd failure code +$pfd-failure-code =: ( + "MALFUNCTION" | + "RESOURCES_LIMITATION" | + "TOO_SHORT_ALLOWED_DELAY" | + "PARTIAL_FAILURE" | + "OTHER_REASON" +) + +; The caching time for the PFDs +$caching-time = "caching-time" : uint64 + +; The successful text message +$success-message = "success-message" : string + +; A JSON pointer path to the success resource +$success-path = "success-path" : string + +; Any additional information for the success. +``` + +``` +$success-info = "success-info" : { // : any *} +``` + +## A.3 PFD management notification schema + +This subclause defines the JSON schema for the body of HTTP request providing the notification of PFD management. The schema is based on IETF draft-newton-json-content-rules [12] and is defined below: + +``` +# jcr-version 0.7 +``` + +``` +# ruleset-id 3gpp.nuapplication.notification +``` + +``` +; A JCR for the notification body +``` + +``` +$notification-root = @ {root} { +``` + +``` + $notification-pfd-reports +``` + +``` +} +``` + +``` +; Report fields definitions +``` + +``` +; The list of pfd reports sent to the SCEF +``` + +``` +$notification-pfd-reports = "notification- pfd-reports" : [ +``` + +``` +{ +``` + +``` + $application-ids, +``` + +``` + $pfd-failure-code, +``` + +``` + $user-plane-location-area ? +``` + +``` +} + +``` + +``` +] +``` + +``` +; The application identifiers for the PFDs +``` + +``` +$application-ids = "application-ids" : [string+] +``` + +``` +; The string format for the pfd failure code +``` + +``` +$pfd-failure-code =: ( +``` + +``` + "MALFUNCTION" | +``` + +``` + "RESOURCES_LIMITATION" | +``` + +``` + "PARTIAL_FAILURE" | +``` + +``` + "OTHER_REASON" +``` + +``` +) +``` + +``` +; The location area of user planes which can not enforce the PFDs successfully +``` + +``` +$user-plane-location-area = { +``` + +\$cell-ids ?, +\$enodeb-ids ?, +\$extended-enodeb-ids ?, +\$routing-area-ids ?, +\$tracking-area-ids ? + +} + +; The cell IDs served by the user planes which can not enforce the PFDs successfully + +\$cell-ids = "cell-ids" : [ string + ] + +; The eNodeB IDs served by the user planes which can not enforce the PFDs successfully + +\$enodeb-ids = "enodeb-ids" : [ string + ] + +; The extended eNodeB IDs served by the user planes which can not enforce the PFDs successfully + +\$extended-enodeb-ids = "extended-enodeb-ids" : [ string + ] + +; The Routing Area IDs served by the user planes which can not enforce the PFDs successfully + +\$routing-area-ids = "routing-area-ids" : [ string + ] + +; The Tracking Area IDs served by the user planes which can not enforce the PFDs successfully + +\$tracking-area-ids = "tracking-area-ids" : [ string + ] + +# Annex B (informative): Call Flows + +## B.1 General + +This annex describes the procedures for the interactions between the PFDF and the SCEF. + +## B.2 Provisioning of PFDs + +This subclause describes the signalling flow for the Provisioning of PFDs. + + + +``` +sequenceDiagram + participant SCEF + participant PFDF + Note right of SCEF: 1. HTTP POST + SCEF->>PFDF: 1. HTTP POST + Note left of PFDF: 2. HTTP 200 OK + PFDF-->>SCEF: 2. HTTP 200 OK +``` + +The diagram is a sequence diagram illustrating the interaction between the SCEF (Service Capability Exposure Function) and the PFDF (PDN Gateway Selection Function) for provisioning PFDs. It consists of two lifelines: SCEF on the left and PFDF on the right. The first message is an arrow from SCEF to PFDF labeled '1. HTTP POST'. The second message is an arrow from PFDF back to SCEF labeled '2. HTTP 200 OK'. + +Sequence diagram showing the provisioning of PFDs between SCEF and PFDF. + +**Figure B.2.1: Provisioning of PFDs** + +1. The SCEF sends the HTTP POST to the PFDF to indicate the creation, modification or deletion of PFDs for one or more application identifier(s) including the parameters defined in subclause 5.3.5.2. +2. The PFDF sends the HTTP 200 OK response to the SCEF including the parameters defined in subclause 5.3.5.2. + +# Annex C (informative): Change history + +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +|---------|-------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------|--------| +| 2016-10 | | | | | | TS skeleton of Nu reference point stage 3. | 0.0.0 | +| 2016-10 | | | | | | Inclusion of C3-163247, C3-163248, C3-163322 and editorial change from Rapporteur. | 0.1.0 | +| 2016-12 | | | | | | Inclusion of C3-164069, C3-164227 and editorial change from Rapporteur. | 0.2.0 | +| 2017-01 | | | | | | Inclusion of C3-170053, C3-17 0054, C3-170056 and editorial change from Rapporteur. | 0.3.0 | +| 2017-02 | | | | | | Inclusion of C3-171187, C3-171324, and editorial change from Rapporteur. | 0.4.0 | +| 2017-04 | | | | | | Inclusion of C3-172121, C3-172193, C3-172278, and editorial change from Rapporteur. | 0.5.0 | +| 2017-05 | | | | | | Inclusion of C3-173200, C3-173202, C3-173332, C3-173333 and editorial change from Rapporteur. | 0.6.0 | +| 2017-06 | CT#76 | CP-171145 | | | | TS sent to plenary for information and approval | 1.0.0 | +| 2017-06 | CT#76 | CP-171145 | | | | TS approved at plenary | 14.0.0 | +| 2017-09 | CT#77 | CP-172047 | 0001 | 2 | F | Caching time over the Nu interface | 14.1.0 | +| 2017-09 | CT#77 | CP-172047 | 0002 | 2 | F | Clarification of partial update | 14.1.0 | +| 2017-09 | CT#77 | CP-172047 | 0003 | 1 | F | Correct the example of the PFD provisioning | 14.1.0 | +| 2017-09 | CT#77 | CP-172047 | 0004 | 1 | F | Update the reference of HTTP 1.1 | 14.1.0 | +| 2017-09 | CT#77 | CP-172047 | 0007 | - | F | PFD handling for Push or Combination mode in PFDF | 14.1.0 | +| 2017-12 | CT#78 | CP-173100 | 0008 | - | F | JSON example correction | 14.2.0 | +| 2018-06 | CT#80 | | | | | Automatic upgrade from previous Release | 15.0.0 | +| 2019-03 | CT#83 | CP-190131 | 0010 | 2 | B | Supported feature negotiation | 16.0.0 | +| 2019-03 | CT#83 | CP-190133 | 0012 | 2 | B | PFD extension | 16.0.0 | +| 2019-06 | CT#84 | CP-191097 | 0015 | - | A | Reference update: draft-newton-json-content-rules | 16.1.0 | +| 2019-06 | CT#84 | CP-191100 | 0016 | - | F | Encoding of custom header fields | 16.1.0 | +| 2019-06 | CT#84 | CP-191102 | 0018 | 1 | B | PFD management notification | 16.1.0 | +| 2019-12 | CT#86 | CP-193220 | 0019 | 3 | B | PFD partial failure notification | 16.2.0 | \ No newline at end of file diff --git a/marked/Rel-16/29_series/29251/1b893df61c2b73b7a85e65fc1f58e203_img.jpg b/marked/Rel-16/29_series/29251/1b893df61c2b73b7a85e65fc1f58e203_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38a516f2be2fdb78733c094a258f69b6c3ad3053 --- /dev/null +++ b/marked/Rel-16/29_series/29251/1b893df61c2b73b7a85e65fc1f58e203_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b537892ddf28b0b6135345f99b8cf734714b5e25459a611f342e3310c2256c9 +size 23016 diff --git a/marked/Rel-16/29_series/29251/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/29_series/29251/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..844b4e4d476b5175a9c4457388d3262cfa9812d4 --- /dev/null +++ b/marked/Rel-16/29_series/29251/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:175364e97f238d026beb5a17c18ff881531def9d19be4af966378528f7c64cf5 +size 34124 diff --git a/marked/Rel-16/29_series/29251/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/29_series/29251/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58c2438f33c6ed5b704b716302ec43f294786f39 --- /dev/null +++ b/marked/Rel-16/29_series/29251/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:776a4e437c814e16d58f366cc10daf441c9180ea7dfb3409d4d4f20b78061e22 +size 17208 diff --git a/marked/Rel-16/29_series/29251/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/29_series/29251/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..174a9b2c17f2573f562a8a66ccc840ad04352dd9 --- /dev/null +++ b/marked/Rel-16/29_series/29251/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86ebd29e895b77fd3bc42ab4d29c406288b1c46f8cbc53ea97dd57fd5a9d6257 +size 6711 diff --git a/marked/Rel-16/29_series/29251/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg b/marked/Rel-16/29_series/29251/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f5dcf93b14f220f98312d587dfd7ebb2258be0a --- /dev/null +++ b/marked/Rel-16/29_series/29251/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a70a56b3243584418ffefc65eb0a3d099e8e4e51e3f00fbece50bf7b352e42e8 +size 16915 diff --git a/marked/Rel-16/29_series/29251/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg b/marked/Rel-16/29_series/29251/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4973c835f063ac0b71ce904cb2c6f20a9ddfe156 --- /dev/null +++ b/marked/Rel-16/29_series/29251/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22fdb11cd4d73815caf8b3ab02bcb23d0d3ca9f8869bd02ae611a0a7cb1b2ada +size 5829 diff --git a/marked/Rel-16/29_series/29251/raw.md b/marked/Rel-16/29_series/29251/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..633b34842a9541273b75f66fcf73b61e96fbdb57 --- /dev/null +++ b/marked/Rel-16/29_series/29251/raw.md @@ -0,0 +1,1504 @@ + + + + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +| | | +|-----------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 Gw reference point..... | 7 | +| 4.1 Overview ..... | 7 | +| 4.2 Gw reference model ..... | 7 | +| 4.3 Functional elements..... | 8 | +| 4.3.1 PFDF..... | 8 | +| 4.3.2 PCEF..... | 8 | +| 4.4 Procedures over Gw reference point ..... | 8 | +| 4.4.1 Request for PFDs ("Pull mode" and "Combination mode")..... | 8 | +| 4.4.2 Provisioning of PFDs ("Push mode" and "Combination mode") ..... | 9 | +| 5 Gwn reference point..... | 10 | +| 5.1 Overview ..... | 10 | +| 5.2 Gwn reference model ..... | 10 | +| 5.3 Functional elements..... | 10 | +| 5.3.1 PFDF..... | 10 | +| 5.3.2 TDF..... | 10 | +| 5.4 Procedures over Gwn reference point ..... | 10 | +| 6 Gw/Gwn protocol..... | 11 | +| 6.1 Introduction ..... | 11 | +| 6.2 Transport layer ..... | 11 | +| 6.3 Application delivery layer..... | 12 | +| 6.3.2 Resources and URI design..... | 12 | +| 6.3.2.1 General..... | 12 | +| 6.3.2.2 URI design for Pull mode ..... | 13 | +| 6.3.2.3 URI design for Push mode..... | 13 | +| 6.3.3 HTTP request/response formats ..... | 13 | +| 6.3.3.1 General..... | 13 | +| 6.3.3.2 GET /gwapplication/pfds/{application-identifier} ..... | 14 | +| 6.3.3.3 GET /gwapplication/pfds?{query-parameters} ..... | 15 | +| 6.3.3.4 GET /gwapplication/pfds..... | 17 | +| 6.3.3.5 POST /gwapplication/provisioning..... | 18 | +| 6.3.4 HTTP status codes ..... | 20 | +| 6.3.5 Feature negotiation ..... | 20 | +| 6.3.5.1 General..... | 20 | +| 6.3.5.2 HTTP custom headers..... | 21 | +| 6.3.5.2.1 3gpp-Optional-Features..... | 21 | +| 6.3.5.2.2 3gpp-Required-Features..... | 21 | +| 6.3.5.2.3 3gpp-Accepted-Features..... | 21 | +| 6.3.5.3 Precedence for HTTP custom headers ..... | 22 | +| 6.4 Specific application communication ..... | 22 | +| 6.4.1 General ..... | 22 | +| 6.4.2 Content type..... | 22 | +| 6.4.3 JSON PFDs fields..... | 22 | +| 6.4.3.1 General..... | 22 | +| 6.4.3.2 application-identifier..... | 22 | +| 6.4.3.3 void ..... | 23 | +| 6.4.3.4 caching-time..... | 23 | +| 6.4.3.5 pfd..... | 23 | +| 6.4.3.6 pfd-identifier ..... | 23 | +| 6.4.3.7 flow-descriptions ..... | 23 | + +6.4.3.8 urls ..... 23 + +6.4.3.9 domain-names..... 24 + +6.4.3.10 dn-protocol..... 24 + +6.4.4 JSON provisioning fields ..... 24 + +6.4.4.1 General..... 24 + +6.4.4.2 notification-flag ..... 24 + +6.4.4.3 removal-flag..... 24 + +6.4.4.4 allowed-delay..... 25 + +6.4.4.5 partial-flag..... 25 + +6.4.5 JSON errors and informational response fields..... 25 + +6.4.5.1 General..... 25 + +6.4.5.2 error-tag ..... 25 + +6.4.6 JSON report fields ..... 25 + +6.4.6.1 General..... 25 + +6.4.6.2 pfd-reports..... 26 + +6.4.6.3 pfd-failure-code ..... 26 + +6.5 The discovery of PCEF/TDF and PFDF ..... 26 + +6.5.1 PCEF/TDF discovery ..... 26 + +6.5.2 PFDF discovery ..... 26 + +7 Secure communication..... 27 + +**Annex A (normative): JSON Schema ..... 28** + +A.1 PFDs schema..... 28 + +A.2 Provisioning schema ..... 29 + +A.3 Error and Informational response schema ..... 30 + +**Annex B (informative): Call Flows..... 33** + +B.1 General ..... 33 + +B.2 Request for PFDs (“Pull mode”)..... 33 + +B.3 Provisioning of PFDs (“Push mode”) ..... 33 + +B.4 Provisioning of PFDs by Push with Notifications ..... 34 + +Annex C (informative): Change history..... 36 + +# --- 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 provides the stage 3 specification of the Gw and Gwn reference points. The functional requirements and the stage 2 specifications of the Gw and Gwn reference points are specified in 3GPP TS 23.203 [2]. The Gw reference point lies between the Packet Flow Description Function (PFDF) and the Policy and Charging Enforcement Function (PCEF). The Gwn reference point lies between the Packet Flow Description Function (PFDF) and the Traffic Detection Function (TDF). + +# 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.203: "Policy and charging control architecture". +- [3] 3GPP TS 29.213: "Policy and Charging Control signalling flows and QoS parameter mapping" +- [4] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [5] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points". +- [6] IETF RFC 793: "Transmission Control Protocol". +- [7] Void. +- [8] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security". +- [9] IETF RFC 2818: "HTTP Over TLS". +- [10] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax" +- [11] IETF RFC 7159: "The JavaScript Object Notation (JSON) Data Interchange Format". +- [12] IETF draft-newton-json-content-rules-09: "A Language for Rules Describing JSON Content". + +NOTE: This individual draft will not further progress in IETF. It is available from the following link: +
(NOTE 1) | 6.3.3.2 | None | PCEF
/TDF | Successful response: The PFDF shall include the representation of the corresponding PDFs of the specified application identifier in the body of the response as per Annex A.1 | +| GET | /gwapplication/pfds?{query-parameters}
(NOTE 1) | 6.3.3.3 | None | PCEF
/TDF | Successful response: The PFDF shall include the representation of the corresponding PDFs for a set of application identifier(s) in the body of the response as per Annex A.1 | +| GET | /gwapplication/pfds
(NOTE 1) | 6.3.3.4 | None | PCEF
/TDF | Successful response: The PFDF shall include the representation of the corresponding PDFs for all application identifier(s) in the body of the response as per Annex A.1 | +| POST | /gwapplication/provisioning
(NOTE 2) | 6.3.3.5 | Content-Type: application/json
The PFDF may include PFDs content and/or notification associated with application identifier(s) using the schema defined in Annex A.2. | PFDF | Successful response: The PCEF/TDF may include informational data in the body of the response as per Annex A.3 | + +NOTE 1: A different path from /gwapplication/pfds/ may be used when it is configured in the PCEF/TDF. In that case the "path" part set in the different methods should use the configured one. + +NOTE 2: A different path from /gwapplication/provisioning may be used when it is configured in the PFDF. In that case the "path" part set in the different methods should use the configured one. + +#### 6.3.3.2 GET /gwapplication/pfds/{application-identifier} + +To retrieve the PFDs for a specific application identifier, the PCEF/TDF shall send an HTTP GET request to the PFDF as follows: + +- the request URI formatted as defined in subclause 6.3.2 with the "path" part set to: /gwapplication/pfds/{application-identifier}, where the application-identifier is the application id with which the PFDs are associated. + +Upon receipt of the HTTP GET, the PFDF shall respond to the PCEF/TDF indicating whether the querying of the resource was successful or not using one of the HTTP status codes as defined in subclause 6.3.4. If the resource exists, the PFDF shall respond with an HTTP 200 OK status code and include the PFDs representation state within the body of the response as defined in Annex A.1. If no resource was found, the PFDF shall respond with an HTTP 404 not found. The PFDF shall also include the Content-Type header field set to "application/json". + +If the PCEF/TDF receives the HTTP 404 not found status code, the PCEF/TDF shall remove all the PFD(s) of the queried application identifier. + +Below is an example of a corresponding HTTP GET: + +GET /gwapplication/pfds/test-application-1 HTTP/1.1 + +Host: pfdfserver.example.com + +Here is an example of a successful response : + +HTTP/1.1 200 OK + +Server: pfdserver.example.com + +Content-Type: application/json + +Content-Length: ... + +``` +{ + "application-identifier":"test-application-1", + + "caching-time":200000, + + "pfds":[ + { + + "pfd-identifier":"pfd1", + "flow-descriptions":[ + "permit in ip from 10.68.28.39 80 to any", + "permit out ip from any to 10.68.28.39 80" + ] + }, + { + + "pfd-identifier":"pfd2", + "urls":[ + "^http://test.example.com(/\\S*)?\\$" + ] + } + ] +} +``` + +#### 6.3.3.3 GET /gwapplication/pfds?{query-parameters } + +To retrieve the PFDs for a set of application identifier(s), the PCEF/TDF may send an HTTP GET request to the PFDF as follows: + +- The request URI formatted as defined in subclause 6.3.2 with the "path" part set to: /gwapplication/pfds?{query-parameters}, where the query-parameters contains one or multiple application identifier(s) delimited by comma with a parameter name "application-identifiers". As an example: "application-identifiers=id1,id2,id3" +- Any "=" and "," for any application identifier in the query parameters shall be encoded as "%3D" and "%2C" in the URI. + +Upon receipt of the HTTP request, the PFDF shall respond to the PCEF/TDF indicating whether the querying of the resources was successful or not using one of the HTTP status codes as defined in subclause 6.3.4. If at least one resource exists, the PFDF shall respond with an HTTP 200 OK status code and include a list of the PFDs associated with the found application identifier(s) within the body of the response as defined in Annex A.1. If the PFDs associated with a queried application-identifier are not provided in the response, it implicitly means that the corresponding application-identifier does not exist at the PFDF. If no resource was found, the PFDF shall respond with an HTTP 404 not found. The PFDF shall also include the Content-Type header field set to "application/json". + +If the PCEF/TDF receives the 200 OK but one or more queried application identifier(s) is not provided in the response, the PCEF/TDF shall remove the PFD(s) of the queried application identifier(s) which is not included in the response. + +If the PCEF/TDF receives the HTTP 404 not found status code, the PCEF/TDF shall remove all the PFD(s) of the queried application identifier(s). + +Below is an example of this HTTP GET on two sets of PFDs query. But only one is found in the PFDF. + +GET /gwapplication/pfds?application-identifiers=test-application-1,test-application-2 HTTP/1.1 + +Host: pfdserver.example.com + +Here is an example of a successful response : + +HTTP/1.1 200 OK + +Server: pfdserver.example.com + +Content-Type: application/json + +Content-Length: ... + +``` +[ + { + "application-identifier":"test-application-1", + "caching-time":200000, + "pfd": [ + { + "pfd-identifier":"pfd1", + "flow-descriptions": [ + "permit in ip from 10.68.28.39 80 to any", + "permit out ip from any to 10.68.28.39 80" + ] + }, + { + "pfd-identifier":"pfd2", + "urls": [ + "^http://test.example.com(/\\S*)?$" + ] + } + ] + } +] +``` + +``` + } +] +``` + +#### 6.3.3.4 GET /gwapplication/pfds + +To retrieve PFDs associated with all application identifiers, the PCEF/TDF may send an HTTP GET request to the PFDF as follows: + +- The request URI formatted as defined in subclause 6.3.2 with the "path" part set to: /gwapplication/pfds. + +Upon receipt of the HTTP request, the PFDF shall respond to the PCEF/TDF indicating whether the querying of the resources was successful or not using one of the HTTP status codes as defined in subclause 6.3.4. If at least one resource exists, the PFDF shall respond with an HTTP 200 OK status code and include a list of the PFDs associated with the found application identifier(s) within the body of the response as defined in Annex A.1. If no resource was found, the PFDF shall respond with an HTTP 404 not found. The PFDF shall also include the Content-Type header field set to "application/json". + +If the PCEF/TDF receives the 200 OK but one or more application identifier(s) which exists at the PCEF/TDF is not provided in the response, the PCEF/TDF shall remove the PFD(s) of the application identifier(s) which is not included in the response. + +If the PCEF/TDF receives the HTTP 404 not found status code, the PCEF/TDF shall remove all the PFD(s) of all the identifier(s) which exist at the PCEF/TDF. + +Below is an example of this HTTP GET. + +GET /gwapplication/pfds HTTP/1.1 + +Host: pfdserver.example.com + +Here is an example of a successful response : + +HTTP/1.1 200 OK + +Server: pfdserver.example.com + +Content-Type: application/json + +Content-Length: ... + +``` +[ + { + "application-identifier": "test-application-1", + "caching-time": 200000, + "pfds": [ + { + "pfd-identifier": "pfd1", + "flow-descriptions": [ + "permit in ip from 10.68.28.39 80 to any", + "permit out ip from any to 10.68.28.39 80" + ] + }, + ], + }, +] +``` + +``` + + { + "pfd-identifier":"pfd2", + "urls":[ + "^http://test.example.com(/\\S*)?$" + ] + } + ] +} +] + +``` + +#### 6.3.3.5 POST /gwapplication/provisioning + +The provisioning of the PFDs shall be performed by the PFDF by using the POST method as follows: + +- The request URI formatted as defined in subclause 6.3.2 with the "path" part set to: /gwapplication/provisioning. +- The Content-Type header field set to "application/json" +- The body of the message encoded in JSON format as defined in Annex A.2. The body shall include + - for the PFD(s) creation for a new application identifier, a new application identifier and its full list of PFD(s) to be created; + - for the PFD(s) full update for an existing application identifier, the existing application identifier and its new full list of PFD(s); + - for the PFD(s) partial update for an existing application identifier, the existing application identifier, partial update indication and + - new PFD(s) with new PFD identifier(s) to install the new PFD(s) , + - new PFD(s) with existing PFD identifier(s) to update the existing PFD(s), and/or + - the existing PFD identifier(s) without any content to remove the PFD(s); + - for the PFD(s) removal for an existing application identifier, the existing application identifier and the removal indication; + - for the PFD(s) notification, the notification indication and an optional allowed delay time for the PCEF/TDF to pull the corresponding PFD(s) within the allowed delay time. + +Upon receipt of the HTTP POST, the PCEF/TDF shall respond to the PFDF indicating whether the provisioning was successful or not using one of the HTTP status codes as defined in subclause 6.3.4. If the provisioning was accepted, the PCEF/TDF shall respond with an HTTP 200 OK status code if no resource is created, or an HTTP 201 Created status code if one or more resources are created. If the provisioning was rejected, the PCEF/TDF shall indicate the reason using an appropriate HTTP status code for as defined in subclause 6.3.4 and optionally additional information in the body of the response as defined in Annex A.3. If the pfd-reports is included, the PCEF/TDF shall identify the failed PFDs by including the application-identifier and specify the failed reason code by including a pfd-failure-code field. + +Depending on the value of the pfd-failure-code field, the PFDF may provision the PFDs again. + +Below is an example of an HTTP POST and a corresponding successful response: + +POST /gwapplication/provisioning HTTP/1.1 + +Host: pcefserver.example.com + +Content-Type: application/json + +Content-Length: ... + +``` +[ + { + "application-identifier":"test-application-1", + "notification-flag":true, + "allowed-delay":600 + }, + { + "application-identifier":"test-application-2", + "removal-flag":true + }, + { + "application-identifier":"test-application-3", + "pfd": [ + { + "pfd-identifier":"pfd1", + "flow-descriptions": [ + "permit in ip from 10.68.28.39 80 to any" + ] + } + ] + }, + { + "application-identifier":"test-application-4", + "partial-flag":true, + "pfd": [ + { + "pfd-identifier":"pfd3", + "urls": [ + "^http://test.example2.net(/\\S*)?$" + ] + }, + { + "pfd-identifier":"pfd4" + } + ] + } +] +``` + +``` +] +} +] +``` + +Here is an example of a successful response: + +HTTP/1.1 200 OK + +Date: Mon, 23 Apr 2012 17:10:00 GMT + +Server: pcefserver.example.com + +Content-Type: application/json + +``` +{ + "success-message": "Notification was processed successfully.", +} +``` + +### 6.3.4 HTTP status codes + +HTTP status codes are used as defined in IETF RFC 7231 [17] + +### 6.3.5 Feature negotiation + +#### 6.3.5.1 General + +The REST based Gw/Gwn interface needs to provide a mechanism to advertise required and optional features supported by both the PCEF/TDF and PFDF for interoperability reasons as the functionality of the REST Gw/Gwn based interface is augmented. + +Feature negotiation shall take place during the first interaction (either HTTP POST in push or HTTP GET in pull) between the PFDF and the PCEF/TDF. The client shall include in the HTTP request the set of supported features as follows: + +- if a feature is required for the proper operation of the application, it shall be included within the 3gpp-Required-Features header; +- if a feature is optional for the proper operation of the application, it shall be included within the 3gpp-Optional-Features header. + +The server shall include, within the 3gpp-Accepted-Features header in the HTTP response, the set of features it supports in common with the client. + +If the server does not support any of the required features advertised by the client within the 3gpp-Required-Features header, the server shall reject the HTTP request with an HTTP 412 Precondition Failed status code and shall include the commonly supported features with the client within the 3gpp-Accepted-Features. + +If the server requires certain features to be supported that are not advertised by the client, the server shall reject the HTTP request with an HTTP 412 Precondition Failed status code and shall include the commonly supported features with the client within the 3gpp-Accepted-Features and the required features in the 3gpp-required-features. + +If the PCEF/TDF and the PFDF successfully negotiate supported features, the list of commonly supported features shall be applicable for the lifetime of the application. Features that are not advertised as supported shall not be used. + +The sender may send information that is related to the supported features. Any unrecognized information shall be ignored by the receiver. + +The table below defines the features applicable to the Gw interface. + +**Table 6.3.5.1-1: Features used in Gw Interface** + +| Feature | M/O | Description | +|-------------------------------------------------------------------------------------------------------------------------|-----|---------------------------------------------------------------------------------------------------| +| PartialUpdate | O | The PPDF can use this feature for partial update in PFD push. | +| DomainNameProtocol | O | This feature supports the additional protocol matching condition for the domain name in PFD data. | +| Feature: A short name for the feature to which the M/O and description pertain. | | | +| M/O: Indication on whether the implementation of the feature is mandatory ("M") or optional ("O") in this 3GPP Release. | | | +| Description: Textual description of the feature. | | | + +The table below defines the features applicable to the Gwn interface. + +**Table 6.3.5.1-2: Features used in Gwn Interface** + +| Feature | M/O | Description | +|-------------------------------------------------------------------------------------------------------------------------|-----|---------------------------------------------------------------------------------------------------| +| PartialUpdate | O | The PPDF can use this feature for partial update in PFD push. | +| DomainNameProtocol | O | This feature supports the additional protocol matching condition for the domain name in PFD data. | +| Feature: A short name for the feature to which the M/O and description pertain. | | | +| M/O: Indication on whether the implementation of the feature is mandatory ("M") or optional ("O") in this 3GPP Release. | | | +| Description: Textual description of the feature. | | | + +NOTE: The base functionality for the Gw/Gwn interface is defined in the Release-14 version of this specification and a feature is an extension of that functionality. The negotiation of supported features allows interworking between the endpoints of the Gw/Gwn interface whereby each entity may support all, some, or none of the features that the Gw/Gwn application can support defined in this specification. Features are defined so that they are independent of each other. Any introduced feature is explicitly defined in this specification. + +#### 6.3.5.2 HTTP custom headers + +This subclause defines any new HTTP custom headers introduced by this specification. + +##### 6.3.5.2.1 3gpp-Optional-Features + +This header is used by the client to advertise the optional features that are supported by the client. + +The encoding of the header follows the ABNF as defined in IETF RFC 7230 [16]. + +3gpp-Optional-Features = "3gpp-Optional-Features" ":" 1#token + +An example is: 3gpp-Optional-Features: feature1, feature2 + +##### 6.3.5.2.2 3gpp-Required-Features + +This header is used by the client to announce the mandatory features that must be supported in the server. + +This header is also used by the server to indicate the missing features that must be supported in the client. + +The encoding of the header follows the ABNF as defined in IETF RFC 7230 [16]. + +3gpp-Required-Features = "3gpp-Required-Features" ":" 1#token + +An example is: 3gpp-Required-Features: feature1, feature2 + +##### 6.3.5.2.3 3gpp-Accepted-Features + +The header is used by the server to confirm the commonly supported set of features with the client. + +The encoding of the header follows the ABNF as defined in IETF RFC 7230 [16]. + +3gpp-Accepted-Features = "3gpp-Accepted-Features" ":" 1#token + +An example is: 3gpp-Accepted-Features: feature1, feature2 + +#### 6.3.5.3 Precedence for HTTP custom headers + +The server shall evaluate the HTTP custom headers first if other conditional headers (e.g. If-None-Match, as defined in IETF RFC 7232 [18]) are also present. + +## 6.4 Specific application communication + +### 6.4.1 General + +Specific application communication represents the presentation of application data structures by transforming data into the form that the application accepts. It establishes the context between application-layer entities. + +NOTE: This release only supports the content type JSON + +### 6.4.2 Content type + +The HTTP POST requests in pull mode shall be an encoded string which is defined in subclause 6.3.3.4. + +The HTTP responses in pull mode as well as the HTTP messages in push mode shall be in JSON format. The content of the JSON text is defined in subclause 6.4.3, 6.4.4 and Annex A. + +The MIME media type that shall be used within the Content-Type header field is “application/json” as defined in IETF RFC 7159 [11]. + +### 6.4.3 JSON PFDs fields + +#### 6.4.3.1 General + +Table 6.4.3.1.1 describes the JSON fields used within the body of the HTTP messages representing the PFDs information associated with an application identifier. The table includes the information about the name of the field and the type of the fields. + +**Table 6.4.3.1.1: Gw/Gwn PFD JSON fields** + +| Field Name | Clause defined | JSON Value Type (NOTE 1) | JCR Type (NOTE 2) | Applicability (NOTE 3) | +|------------------------|----------------|--------------------------|-------------------|------------------------| +| application-identifier | 6.4.3.2 | string | string | | +| caching-time | 6.4.3.4 | number | uint64 | | +| pfds | 6.4.3.5 | array | array | | +| pfd-identifier | 6.4.3.6 | string | string | | +| flow-descriptions | 6.4.3.7 | array | array | | +| urls | 6.4.3.8 | array | array | | +| domain-names | 6.4.3.9 | array | array | | +| dn-protocol | 6.4.3.10 | string | string | DomainNameProtocol | + +NOTE 1: The basic JSON value types are defined in IETF RFC 7159 [11]. +NOTE 2: The JCR types are defined in IETF draft-newton-json-content-rules [12]. +NOTE 3: Fields marked with a supported feature are applicable as described in subclause 6.3.5. + +#### 6.4.3.2 application-identifier + +The application-identifier field is of type string, and contains the application identifier to which the PFDs belong. + +#### 6.4.3.3 void + +#### 6.4.3.4 caching-time + +The caching-time field is of type uint64. It's a caching time value in seconds. When the caching timer elapses, the PCEF/TDF shall re-fetch the PFDs associated with the corresponding application-identifier from the PFDF. If the caching-time is: + +- omitted, the PCEF/TDF shall use the preconfigured default caching time value to control how long the PFDs valid; or +- set to zero, then the PFDs are valid until explicitly deleted by the PFDF. + +NOTE: The value zero of caching-time is only valid in the Combination mode and can be used as an indication of infinite PFD validity. It can be used to avoid unnecessary PFD refreshment for an application, in such case, the PFDs cannot be deleted at the expiration of the caching timer if it was not stopped at reception of caching-time set to zero value. + +#### 6.4.3.5 pfd + +The pfd field is of type array. It contains the PFDs that belong to a specific application identifier. When multiple PFDs are associated with the application identifier, the application is detected when any of the PFDs associated with the application identifier is matched. + +The following defines the content of the PFD: + +The pfd-identifier field shall be included within the PFD, and shall be unique within the context of an application identifier. + +At least one of the flow-descriptions field, the urls field, the domain-names field or a custom field shall be present for the application traffic detection. If a PFD contains multiple filter types, the PFD is only matched when every filter type contained in the PFD has a matching value. + +The custom field is type of any with an arbitrary field name. Any primitive type, array, or object defined in IETF RFC 7159 [11] can be set to this field. It provides the extensions for the proprietary application traffic detection mechanisms, based on the agreement between the ASP and the mobile operator. + +Below are the JCR for the PFD: + +``` +$pfd = { + $pfd-identifier, + ($flow-descriptions | $urls | $domain-names | // : any) ? +} +``` + +#### 6.4.3.6 pfd-identifier + +The pfd-identifier is of type string. It uniquely identifies a PFD within its associated application identifier. + +#### 6.4.3.7 flow-descriptions + +The flow-descriptions is of type string array. The content of the string has the same encoding as the IPFilterRule AVP value as defined in IETF RFC 6733 [13]. It represents a 3-tuple with protocol, server ip and server port for UL/DL application traffic. + +#### 6.4.3.8 urls + +The urls is type of string array. The content of the string shall be a URL or a regular expression which is used to match the significant parts of the URL. + +#### 6.4.3.9 domain-names + +The domain-names is type of string array. The content of the string shall be an FQDN or a regular expression as a domain name matching criteria. + +#### 6.4.3.10 dn-protocol + +The dn-protocol is type of string. It indicates the additional protocol and protocol field for domain names to be matched, applicable when domain-names field is present. + +The following values are defined: + +##### DNS\_QNAME + +Identifies the DNS protocol and the question name in DNS query. + +##### TLS\_SNI + +Identifies the Server Name Indication in TLS ClientHello message. + +##### TLS\_SAN + +Identifies the Subject Alternative Name in TLS ServerCertificate message. + +##### TLS\_SCN + +Identifies the Subject Common Name in TLS ServerCertificate message. + +### 6.4.4 JSON provisioning fields + +#### 6.4.4.1 General + +In addition to subclause 6.4.3, Table 6.4.4.1.1 describes the extra JSON fields used within the body of the HTTP messages representing the PFDs provisioning information in push mode. The table includes the information about the name of the field and the type of the fields. + +**Table 6.4.4.1.1: Gw/Gwn Provisioning JSON fields** + +| Field Name | Clause defined | JSON Value Type (NOTE 1) | JCR Type (NOTE 2) | Applicability (NOTE 3) | +|-----------------------------------------------------------------------------------------------------------------------------------|----------------|--------------------------|-------------------|------------------------| +| notification-flag (NOTE 4) | 6.4.4.2 | boolean | boolean | | +| removal-flag (NOTE 4) | 6.4.4.3 | boolean | boolean | | +| allowed-delay (NOTE 4) | 6.4.4.4 | number | uint64 | | +| partial-flag (NOTE 4) | 6.4.4.5 | boolean | boolean | PartialUpdate | +| NOTE 1: The basic JSON value types are defined in IETF RFC 7159 [11]. | | | | | +| NOTE 2: The JCR types are defined in IETF draft-newton-json-content-rules [12]. | | | | | +| NOTE 3: Fields marked with a supported feature are applicable as described in subclause 6.3.5. | | | | | +| NOTE 4: Only one of the notification-flag, removal-flag and the partial-flag for the application identifier shall be set to true. | | | | | + +#### 6.4.4.2 notification-flag + +The notification-flag is of type boolean. + +If the value of the flag is true, then it indicates a PFDs notification, and the corresponding PFDs information for the application identifier is not provided in the JSON body. Instead, the PCEF/TDF shall reload it with the application identifier via the pull procedure. + +#### 6.4.4.3 removal-flag + +The removal-flag is of type boolean. + +If the value of the flag is true, then it indicates the PFDs and its associated application identifier have been removed in the PPDF. The PCEF/TDF shall unbind all PFDs associated with that application identifier. + +#### 6.4.4.4 allowed-delay + +The allowed-delay field is of type uint64. It contains a time interval in seconds. The PFDs shall be deployed within this time interval. If the allowed-delay is omitted, or if it is set to zero, then the PFDs shall be immediately deployed. + +#### 6.4.4.5 partial-flag + +The partial-flag is of type boolean. + +If the value of the flag is true, then it indicates some PFDs for the application identifier(s) have been created/updated/deleted in the PFDF. The PCEF/TDF shall update existing PFDs or add new PFDs for the PFD identifier(s) with PFDs, or unbind all PFDs associated with the PFD identifier(s) without any PFDs content. + +### 6.4.5 JSON errors and informational response fields + +#### 6.4.5.1 General + +Table 6.4.5.1.1 describes the JSON fields defined for the errors and informational responses including their types and the field names. + +**Table 6.4.5.1.1: JSON fields for errors and informational response** + +| Field Name | Subclause defined | JSON Value Type (NOTE 1) | JCR Type (NOTE 2) | +|---------------------------------------------------------------------------------|------------------------------|--------------------------|-----------------------------------------------------------------| +| errors | 3GPP TS 29.155 [15] (NOTE 4) | array | array | +| error-type | 3GPP TS 29.155 [15] (NOTE 4) | string | "application"
"interface"
"server"
"other"
(NOTE 3) | +| error-message | 3GPP TS 29.155 [15] | string | string | +| error-tag | 6.4.5.2 | string | string | +| error-path | 3GPP TS 29.155 [15] | string | string | +| error-info | 3GPP TS 29.155 [15] | object | object | +| success-message | 3GPP TS 29.155 [15] | string | string | +| success-path | 3GPP TS 29.155 [15] | string | string | +| success-info | 3GPP TS 29.155 [15] | object | object | +| NOTE 1: The basic JSON value types are defined in IETF RFC 7159 [11]. | | | | +| NOTE 2: The JCR types are defined in IETF draft-newton-json-content-rules [12]. | | | | +| NOTE 3: The quoted strings for a string type. | | | | +| NOTE 4: The error is sent from the PCEF/TDF to the PFDF. | | | | + +#### 6.4.5.2 error-tag + +The error-tag field is of type string. It defines a tag for a particular error. + +##### PFD\_EVENT + +This error-tag shall be used when the PFDs cannot be installed/modified at the PCEF, pfd-reports shall be provided in the error-info as described in subclause 6.4.6. + +### 6.4.6 JSON report fields + +#### 6.4.6.1 General + +Table 6.4.6.1.1 describes the JSON fields defined for the report information objects which are included in the error-info field. + +**Table 6.4.6.1.1: JSON fields for Report from the PCEF** + +| Field Name | Subclause defined | JSON Value Type (NOTE 1) | JCR Type (NOTE 2) | +|---------------------------------------------------------------------------------|---------------------|--------------------------|-------------------| +| pdf-reports | 6.4.6.2 | array | array | +| application-ids | 3GPP TS 29.250 [14] | array | array | +| pfd-failure-code | 6.4.6.3 | string | string | +| NOTE 1: The basic JSON value types are defined in IETF RFC 7159 [11]. | | | | +| NOTE 2: The JCR types are defined in IETF draft-newton-json-content-rules [12]. | | | | + +#### 6.4.6.2 pfd-reports + +The pfd-reports field is of type array and it contains a list of pfd reports. + +The pfd-reports field can be used in an HTTP response to report failures in the installation/modification of PFDs in the Push mode. In this case, it shall be provided as a sub field of the error-info field. + +Multiple pfd report instances shall be provided within the pfd-reports field if different pfd-failure-code values are applicable within the same HTTP response. + +A report instance shall contain the application-ids and pfd-failure-code fields. + +The JCR format for the pfd-reports is: + +\$pfd-reports = "pfd-reports" : [ + +{ \$application-ids, + +\$pfd-failure-code + +} + + +] + +#### 6.4.6.3 pfd-failure-code + +The pfd-failure-code is of type string. + +The following values are defined in this release: + +MALFUNCTION + +RESOURCES\_LIMITATION + +OTHER\_REASON + +## 6.5 The discovery of PCEF/TDF and PFDF + +### 6.5.1 PCEF/TDF discovery + +For “Push mode”, the PFDF requires a method to discover the PCEF(s)/TDF(s). + +A list of PCEF/TDF URIs may be pre-configured on the PFDF. + +The PFDF may select the PCEF/TDF by this configuration. + +NOTE: Other methods to discover the PCEF(s)/TDF(s) are implementation specific. + +### 6.5.2 PFDF discovery + +For “Pull mode”, the PCEF/TDF requires a method to discover the PFDF. + +The PFDF URI may be pre-configured on the PCEF/TDF. + +The PCEF/TDF may select the PFDF by this configuration. + +NOTE 1: Other methods to discover the PFDF are implementation specific. + +NOTE 2: If multiple PFDFs are deployed within one PLMN, coordination between the PFDFs is needed to avoid duplicated provisioning, e.g. to avoid that the PCEF/TDFs served by different PFDFs are overlapping + +# --- 7 Secure communication + +Either the NDS/IP network layer security defined in 3GPP TS 33.210 [8] or HTTP over TLS as defined in IETF RFC 2818 [9] should be used to secure communication over the REST based Gw and Gwn interfaces. + +# Annex A (normative): JSON Schema + +## A.1 PFDs schema + +This subclause defines the JSON schema for the body of HTTP responses providing the state of one or more PFDs resources in pull mode. The schema is based on IETF draft-newton-json-content-rules [12] and is defined below: + +``` +# jcr-version 0.7 +``` + +``` +# ruleset-id 3gpp.gwapplication.pfds +``` + +``` +; JCR representing the pfds root resource +``` + +``` +$pfds-root = @ {root} { +``` + +``` + $application-identifier, +``` + +``` + $caching-time ?, +``` + +``` + $pfds +``` + +``` +} +``` + +``` +; An array list of the PFDs for multiple application identifiers +``` + +``` +$pfds-array-root = @ {root} [ $pfds-root * ] +``` + +``` +; The caching timer for the PFDs +``` + +``` +$caching-time = "caching-time" : uint64 +``` + +``` +; The PFDs associated with the same application identifier +``` + +``` +$pfds = "pfds" : [ $pfd * ] +``` + +``` +; The PFD content +``` + +``` +$pfd = { +``` + +``` + $pfd-identifier, +``` + +``` + ( $flow-descriptions | $urls | $domain-names | // : any) ?, +``` + +``` + $dn-protocol ? +``` + +``` +} +``` + +``` +; The PFD identifier +``` + +``` +$pfd-identifier = "pfd-identifier" : string +``` + +; The flow descriptions + +\$flow-descriptions = "flow-descriptions" : [ string + ] + +; The url matching expressions + +\$urls = "urls" : [ string + ] + +; The domain name match criteria + +\$domain-names = "domain-names" : [ string + ] + +; The domain name protocol + +``` +$dn-protocol =: ( + "DNS_QNAME" | + "TLS_SNI" | + "TLS_SAN" | + "TLS_SCN" +) +``` + +## --- A.2 Provisioning schema + +This subclause defines the JSON schema for the body of HTTP request providing the provisioned PFDs as well as the PFDs notifications in push mode. The schema is based on IETF draft-newton-json-content-rules [12] and is defined below: + +``` +# jcr-version 0.7 +``` + +``` +# ruleset-id 3gpp.gwapplication.provisioning +``` + +``` +# import 3gpp.gwapplication.pfds as pfds +``` + +``` +; JCR representing the PFDs provisioning data +``` + +``` +$provisioning-root = @{root} { + $pfds.application-identifier, + $notification-flag ?, + $removal-flag ?, + $partial-flag ?, + $allowed-delay ?, + $pfds.pfds ? +``` + +} + +; An array list of the PFDs provisioning/notification for multiple application identifiers + +\$provisioning-array-root = @{root} [ \$provisioning-root \* ] + +; A flag indicates whether this is a notification or a provisioning + +\$notification-flag = "notification-flag" : boolean + +; A flag indicates whether this is a removal or not + +\$removal-flag = "removal-flag" : boolean + +; A flag indicates whether this is a partial update or not + +\$partial-flag = "partial-flag" : boolean + +; The allowed delay time for the PFDs deployment + +\$allowed-delay = "allowed-delay" : uint64 + +## --- A.3 Error and Informational response schema + +This subclause defines the JSON schema for the body of HTTP responses in case of errors or success. The schema is based on IETF draft-newton-json-content-rules [12] and is defined below: + +# jcr-version 0.7 + +# ruleset-id 3gpp.gwaplication.info + +; A JCR for the error/successful response body + +; Errors information + +\$errors-root = @{root} { \$errors } + +; Success information + +\$success-root = @{root} { + +\$success-message, + +\$success-path ?, + +\$success-info ? + +} + +; Resource fields definitions + +; The list of errors returned in responses sent by the PCEF/TDF + +\$errors = "errors" : [ + +{ + +\$error-type, + +\$error-message, + +\$error-tag ?, + +\$error-path ?, + +\$error-info ? + +} + + +] + +; The error type for an error. It can be one of 'application', 'interface', 'server' and 'other'. + +\$error-type = "error-type" : ( "application" | "interface" | "server" | "other" ) + +; The error text message + +\$error-message = "error-message" : string + +; The error tag for a specific error + +\$error-tag = "error-tag" : string + +; A JSON pointer path to the error resource + +\$error-path = "error-path" : string + +; Any additional information for the error + +\$error-info = "error-info" : { + +\$pfd-reports ?, + +// : any \* + +} + +; Report fields definitions + +; The list of pfd reports sent to the PFDF + +\$pfd-reports = "pfd-reports" : [ + +{ \$application-ids, + +\$pfd-failure-code + +} + + +----- + +----- + +] + +; The string format for the pfd failure code + +\$pfd-failure-code =: ( + +"MALFUNCTION" | + +"RESOURCES\_LIMITATION" | + +"OTHER\_REASON" + +) + +; The successful text message + +\$success-message = "success-message" : string + +; A JSON pointer path to the success resource + +\$success-path = "success-path" : string + +; Any additional information for the success. + +\$success-info = "success-info" : { // : any \* } + +; application identifiers + +\$application-ids = "application-ids" : [ string + ] + +# Annex B (informative): Call Flows + +## B.1 General + +This annex describes the procedures for the interactions between the PFDF and the PCEF/TDF. + +## B.2 Request for PFDs (“Pull mode”) + +This subclause describes the signalling flow for the request for PFDs. + + + +``` +sequenceDiagram + participant PCEF/TDF + participant PFDF + Note right of PCEF/TDF: 1. HTTP GET + PCEF/TDF->>PFDF: 1. HTTP GET + Note left of PFDF: 2. HTTP 200 OK + PFDF->>PCEF/TDF: 2. HTTP 200 OK +``` + +The diagram illustrates a sequence of two messages between two entities: PCEF/TDF and PFDF. The PCEF/TDF sends a message labeled '1. HTTP GET' to the PFDF. The PFDF responds with a message labeled '2. HTTP 200 OK' back to the PCEF/TDF. + +Sequence diagram showing the request for PFDs (Pull mode) between PCEF/TDF and PFDF. + +**Figure B.2.1: Request for PFDs** + +1. The PCEF/TDF sends the HTTP GET to the PFDF to request the PFDs including the parameters defined in subclause 6.3.3.2, 6.3.3.3 or 6.3.3.4. +2. The PFDF sends the HTTP 200 OK response to the PCEF/TDF including the parameters defined in subclause 6.3.3.2, 6.3.3.3 or 6.3.3.4. + +## B.3 Provisioning of PFDs (“Push mode”) + +This subclause describes the signalling flow for the provisioning of PFDs. + + + +``` +sequenceDiagram + participant PCEF/TDF + participant PFDF + PFDF->>PCEF/TDF: 1. HTTP POST + PCEF/TDF->>PFDF: 2. HTTP 200 OK +``` + +A sequence diagram showing the interaction between PCEF/TDF and PFDF. The diagram consists of two vertical lifelines. The first message is an arrow from PFDF to PCEF/TDF labeled '1. HTTP POST'. The second message is an arrow from PCEF/TDF to PFDF labeled '2. HTTP 200 OK'. + +Sequence diagram for provisioning of PFDs + +**Figure B.3.1: Provisioning of the PFDs** + +1. The PFDF sends the HTTP POST to the PCEF/TDF to provision the PFDs of one or more application identifiers including the parameters defined in subclause 6.3.3.5. +2. The PCEF/TDF sends the HTTP 200 OK response to the PFDF including the parameters defined in subclause 6.3.3.5. + +## B.4 Provisioning of PFDs by Push with Notifications + +This subclause describes the signalling flow for the provisioning of PFDs by push with notifications. + + + +``` +sequenceDiagram + participant PCEF/TDF + participant PFDF + PFDF->>PCEF/TDF: 1. HTTP POST + PCEF/TDF->>PFDF: 2. HTTP 200 OK + Note over PCEF/TDF, PFDF: 3. Request for the PFDs +``` + +A sequence diagram showing the interaction between PCEF/TDF and PFDF. The diagram consists of two vertical lifelines. The first message is an arrow from PFDF to PCEF/TDF labeled '1. HTTP POST'. The second message is an arrow from PCEF/TDF to PFDF labeled '2. HTTP 200 OK'. Below these, a rectangular box labeled '3. Request for the PFDs' is shown, spanning across both lifelines, indicating a procedure initiated by PCEF/TDF. + +Sequence diagram for provisioning of PFDs by push with notification + +**Figure B.4.1: Provisioning of the PFDs by push with notification** + +1. The PFDF sends the HTTP POST to the PCEF/TDF to provision the notification of creation/update for one or more application identifiers including the parameters defined in subclause 6.3.3.5. +2. The PCEF/TDF sends the HTTP 200 OK response to the PFDF including the parameters defined in subclause 6.3.3.5. +3. Within the allowed-delay provided in the step1, the PCEF/TDF initiates the procedure defined in Annex B.2 to request the PFDs for the application identifiers. + +NOTE: The step 3 can be executed multiple times if the PCEF/TDF initiates separate pull requests to retrieve the PFDs for different application identifier(s). + +# Annex C (informative): Change history + +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +|---------|-------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2016-10 | | | | | | TS skeleton of Gw and Gwn reference points stage 3. | 0.0.0 | +| 2016-10 | | | | | | Inclusion of C3-163212, C3-163213, C3-163304, C3-163323, C3-163326, C3-163327 and editorial change from Rapporteur. | 0.1.0 | +| 2016-11 | | | | | | Inclusion of C3-164174, C3-164177, C3-164231 and editorial change from Rapporteur. | 0.2.0 | +| 2017-01 | | | | | | Inclusion of C3-170055, C3-170060, C3-170061, C3-170063, C3-170065 and editorial change from Rapporteur. | 0.3.0 | +| 2017-02 | | | | | | Inclusion of C3-171274, C3-171304, C3-171307, C3-171308, C3-171319, and editorial change from Rapporteur. | 0.4.0 | +| 2017-03 | CT#75 | CP-170101 | | | | TS sent for Information to Plenary | 1.0.0 | +| 2017-04 | | | | | | Inclusion of C3-172137, C3-172195, C3-172197, C3-172237, C3-172238, C3-172246, and editorial change from Rapporteur. | 1.1.0 | +| 2017-05 | | | | | | Inclusion of C3-173120, C3-173154, C3-173196, C3-173198, C3-173201, C3-173288, C3-173289, C3-173290, C3-173295, C3-173297, C3-173320, C3-173322, C3-173331, and editorial change from Rapporteur. | 1.2.0 | +| 2017-06 | CT#76 | CP-171144 | | | | TS sent for approval to plenary. | 2.0.0 | +| 2017-06 | CT#76 | CP-171144 | | | | TS approved at plenary. | 14.0.0 | +| 2017-09 | CT#77 | CP-172047 | 0001 | 2 | F | Clarification of partial update. | 14.1.0 | +| 2017-09 | CT#77 | CP-172047 | 0002 | 3 | F | Clarification of combination mode. | 14.1.0 | +| 2017-09 | CT#77 | CP-172047 | 0005 | 2 | F | Clarification of PCEF's behaviour in the pull mode. | 14.1.0 | +| 2017-09 | CT#77 | CP-172047 | 0006 | 1 | F | Update the reference of HTTP 1.1. | 14.1.0 | +| 2017-09 | CT#77 | CP-172047 | 0007 | 1 | F | Caching time correction. | 14.1.0 | +| 2017-09 | CT#77 | CP-172047 | 0011 | 1 | F | PFD error report correction. | 14.1.0 | +| 2017-09 | CT#77 | CP-172047 | 0012 | 1 | F | Correction for PFD provisioning notification. | 14.1.0 | +| 2017-09 | CT#77 | CP-172047 | 0014 | 1 | F | Reference and URI design correction. | 14.1.0 | +| 2017-09 | CT#77 | CP-172047 | 0015 | 1 | F | Correction to PFD removal. | 14.1.0 | +| 2017-12 | CT#78 | CP-173100 | 0016 | - | F | Correction to PFD removal. | 14.2.0 | +| 2017-12 | CT#78 | CP-173100 | 0017 | - | F | Precedence for 3GPP custom headers. | 14.2.0 | +| 2018-06 | SA#80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2018-12 | CT#82 | CP-183120 | 0019 | 1 | A | Correction to PFD retrieval by pull mode | 15.1.0 | +| 2019-03 | CT#83 | CP-190133 | 0020 | 3 | B | PFD extension | 16.0.0 | +| 2019-06 | CT#84 | CP-191097 | 0023 | - | A | Reference update: draft-newton-json-content-rules | 16.1.0 | +| 2019-06 | CT#84 | CP-191097 | 0026 | - | A | Encoding of custom header fields | 16.1.0 | +| 2019-09 | CT#85 | CP-192168 | 0029 | | A | Correct presence condition in PFD definition | 16.2.0 | \ No newline at end of file diff --git a/marked/Rel-16/29_series/29272/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/29_series/29272/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da9fe820f1e0711c894adb39147866c4af20ab91 --- /dev/null +++ b/marked/Rel-16/29_series/29272/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bd6d46f945acbf52a777a76a6b880a6283dcf733e92797b288748d58070cc22 +size 9691 diff --git a/marked/Rel-16/29_series/29272/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/29_series/29272/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea8a115b27e3c83e6d6ab67af3b349460bdbaf3f --- /dev/null +++ b/marked/Rel-16/29_series/29272/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e6e22bb5df694cc1f0a2659d92dd92b8197006dec0ce9458f97fc1605e3c7d2 +size 5657 diff --git a/marked/Rel-16/29_series/29272/raw.md b/marked/Rel-16/29_series/29272/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..58ce661e32a72dd4c089d76b8b5bae8d248aa7bd --- /dev/null +++ b/marked/Rel-16/29_series/29272/raw.md @@ -0,0 +1,6993 @@ + + +# 3GPP TS 29.272 V16.7.0 (2022-06) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol (Release 16)** + + + +The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green curved lines representing signal waves. + +5G logo + + + +The 3GPP logo, featuring the text "3GPP" in a stylized, bold, black font. Below the "3GPP" text is a red signal icon consisting of three curved lines. Below the icon, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + +
(See IETF RFC 6733 [61]) | M | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [3], clause 2.2. | +| Supported Features
(See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Terminal Information
(See 7.3.3) | Terminal-Information | O | This information element shall contain information about the user's mobile equipment. Within this Information Element, only the IMEI and the Software-Version AVPs shall be used on the S6a/S6d interface. | +| ULR Flags
(See 7.3.7) | ULR-Flags | M | This Information Element contains a bit mask. See 7.3.7 for the meaning of the bits. | +| Visited PLMN Id
(See 7.3.9) | Visited-PLMN-Id | M | This IE shall contain the MCC and the MNC, see 3GPP TS 23.003 [3]. It may be used to apply roaming based features. | +| Equivalent PLMN List
(See 7.3.151) | Equivalent-PLMN-List | O | This Information Element shall contain the equivalent PLMN list of which the MME/SGSN requests the corresponding CSG Subscription data. | +| RAT Type
(See 7.3.13) | RAT-Type | M | This Information Element contains the radio access type the UE is using. See clause 7.3.13 for details. | +| SGSN number
(See 7.3.102) | SGSN-Number | C | This Information Element contains the ISDN number of the SGSN, see 3GPP TS 23.003 [3]. It shall be present when the message is sent on the S6d interface and the SGSN supports LCS (using MAP based Lg interface) or SMS functionalities or the Gs interface.
It may be present when the message is sent on the S6a interface and the requesting node is a combined MME/SGSN. | +| Homogeneous Support of IMS Voice Over PS Sessions | Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions | O | This Information Element, if present, indicates whether or not "IMS Voice over PS Sessions" is supported homogeneously in all TAs or RAs in the serving node (MME or SGSN or combined MME/SGSN).
The value "SUPPORTED" indicates that there is support for "IMS Voice over PS Sessions" in all TAs or RAs.
The value "NOT_SUPPORTED" indicates that there is not support for "IMS Voice over PS Sessions" in any of the TAs or RAs. | +| V-GMLC address | GMLC-Address | C | This Information Element shall contain, if available, the IPv4 or IPv6 address of the V-GMLC associated with the serving node. | +| Active APN | Active-APN | O | This Information Element, if present, contains the list of active APNs stored by the MME or SGSN, including the identity of the PDN GW assigned to each APN. For the case of explicitly subscribed APNs, the following information shall be present:
- Context-Identifier: context id of subscribed APN in use
- Service-Selection: name of subscribed APN in use
- MIP6-Agent-Info: including PDN GW identity in use for subscribed APN
- Visited-Network-Identifier: identifies the PLMN where the PDN GW was allocated
For the case of the Wildcard APN, the following information shall be present:
- Context-Identifier: context id of the Wildcard APN
- Specific-APN-Info: list of APN-in use and related PDN GW identity when the subscribed APN is the wildcard APN
It may be present when MME or SGSN needs to restore PDN GW data in HSS due to a Reset procedure. | +| UE SRVCC Capability | UE-SRVCC-Capability | C | This information element shall indicate if the UE supports or does not support the SRVCC capability and shall be present if the MME or the SGSN supports SRVCC and this information is available to the MME or the SGSN. | +| MME Number for MT SMS | MME-Number-for-MT-SMS | C | This Information Element contains the ISDN number of the MME to route SMS to the UE through the MME, see 3GPP TS 23.003 [3]. It shall be present when the MME supports SMS in MME and wishes to provide SMS in MME. | + +| | | | | +|------------------------------------------|--------------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| SMS Register Request | SMS-Register-Request | C | This information element is used to inform the HSS if the MME or the SGSN needs to be registered for SMS, prefers not to be registered for SMS or has no preference. It shall be present when the MME supports SMS in MME and requests to be registered for SMS. It shall be present when the SGSN supports "SMS in SGSN" as defined in clause 5.3.18 in 23.060 [12], and requests to be registered for SMS. | +| SGs MME identity | SGs-MME-Identity | O | This information element is used to inform the HSS of the MME identity that the MME will use over the SGs interface. This information element shall be present, if the MME supports this information element and if the MME identity used over SGs is different from the MME Diameter identity used over S6a. | +| Coupled node's Diameter identity | Coupled-Node-Diameter-ID | O | This information element contains the Diameter identity of the coupled node (i.e. MME's Diameter identity for the SGSN and SGSN's Diameter identity for the MME) when the message is sent by the combined MME/SGSN.
This information element may be present when the message is sent on the S6a/S6d interface and the requesting node is a combined MME/SGSN. | +| Adjacent PLMNs | Adjacent-PLMNs | O | This information element, if present, shall contain the list of PLMNs where an UE served by the MME/SGSN is likely to make a handover from the PLMN where the MME/SGSN is located. This list is statically configured by the operator in the MME/SGSN, according to the geographical disposition of the different PLMNs in that area, the roaming agreements, etc... | +| Supported Services (3GPP TS 29.336 [54]) | Supported-Services | O | If present, this Information Element shall contain AVPs indicating details of the services supported by the MME/SGSN. | + +**Table 5.2.1.1/2: Update Location Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|-----------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported Features (See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Result (See 7.4) | Result-Code / Experimental-Result | M | This IE shall contain the result of the operation.
The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [61]).
The Experimental-Result AVP shall be used for S6a/S6d errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.
The following errors are applicable:
- User Unknown
- Unknown EPS Subscription
- RAT Not Allowed
- Roaming Not Allowed | +| Error-Diagnostic | Error-Diagnostic | O | If the Experimental Result indicates "Unknown EPS Subscription", Error Diagnostic may be present to indicate whether or not GPRS subscription data are subscribed (i.e. whether or not Network Access Mode stored in the HSS indicates that only circuit service is allowed).
If the Experimental Result indicates "Roaming Not Allowed", and the Update Location is rejected due to ODB, Error Diagnostic may be present to indicate the specific type of ODB. | +| ULA-Flags (See 7.3.8) | ULA-Flags | C | This Information Element contains a bit mask. See 7.3.8 for the meaning of the bits. It shall be present only when the Result-Code AVP is DIAMETER_SUCCESS. | +| Subscription Data (See 7.3.2) | Subscription-Data | C | This Information Element shall contain the complete subscription profile of the user. It shall be present if success is reported, unless an explicit "skip subscriber data" indication was present in the request. | +| Reset-IDs (See 7.3.184) | Reset-ID | O | The Reset-ID uniquely identifies a fallible resource in the HSS on which the user (IMSI) depends. In the event of a restart of the fallible resource a Reset message containing the Reset-ID will exactly identify the impacted subscribers. | + +#### 5.2.1.1.2 Detailed behaviour of the MME and the SGSN + +The MME shall make use of this procedure to update the MME identity stored in the HSS (e.g. at initial attach, inter MME tracking area update or radio contact after HSS reset). + +The SGSN shall make use of this procedure to update the SGSN identity stored in the HSS (e.g. at initial attach, inter SGSN routing area update or radio contact after HSS reset). + +The MME shall make use of this procedure to request SMS data and to become registered for SMS. + +The SGSN shall make use of this procedure to request to become registered for SMS. + +A combined MME/SGSN which uses different Diameter Identities for the MME and SGSN parts shall not send a second ULR when in a first ULA the ULA-Flag "Separation Indication" was not set. + +For UEs receiving emergency services, in which the UE was not successfully authenticated, the MME or SGSN shall not make use of the Update Location procedure. + +If the Update Location request is to be sent due to an inter node (SGSN to MME) update and the previous SGSN is a Gn/Gp SGSN, the MME shall set the "Single-Registration-Indication" flag in the ULR-Flags information element in the request. + +If the Update Location request is to be sent due to an initial attach, the MME or SGSN shall set the "Initial-Attach-Indicator" flag in the ULR-Flags information element in the request. + +When receiving and supporting Reset-ID AVPs in the response, the MME or SGSN shall delete all the stored Reset-IDs, if there are any, and then store all the received Reset-IDs. + +A combined MME/SGSN shall set the "Skip Subscriber Data" flag in the ULR-Flags if subscriber data are already available due to a previous location update. + +A combined MME/SGSN that has advertised its support for the combined MME/SGSN capability, by either including the SGSN Number within ULR sent over S6a or including the Coupled-Node-Diameter-ID within ULR sent over S6a/S6d or by using same Diameter identity over S6a and S6d interfaces, shall be prepared to receive a single subscription data update message (IDR or DSR) from the HSS when the subscription data is modified. + +If the MME or SGSN knows about the homogeneity of the support of IMS Voice over PS Sessions in all TAs or RAs associated to that serving node (i.e., it is supported in all the TA/RAs or it is not supported in any of the TA/RAs) and for the serving subscriber taking into account roaming relationship for IMS Voice over PS Sessions, it shall include this indication to the HSS in the "Homogeneous Support of IMS Voice over PS Sessions" IE. + +The MME or SGSN may include dynamic APN and PGW ID data in the list of Active-APN AVPs, in order to restore this information in the HSS after a Reset procedure. + +The MME/SGSN may include an equivalent PLMN list to request the CSG Subscription data of the equivalent PLMNs. + +A standalone MME shall not indicate its support for any SGSN specific features, and it shall not request explicitly the download of GPRS data (via the GPRS-Subscription-Data-Indicator flag; see clause 7.3.7). A standalone MME that does not support the "SMS in MME" feature shall not provide its MME Number for MT SMS, "SMS only" indication or SMS Registration Request and therefore not indicate its support for any SMS related features (such as ODB or barring services). + +For an SGSN, if a DIAMETER\_ERROR\_CAMEL\_SUBSCRIPTION\_PRESENT is received, the SGSN shall initiate the update location procedure with MAP over Gr interface and use Gr for the subsequent mobility procedures. + +For a standalone MME or SGSN, if EPS or GPRS subscription data is received, the standalone MME or SGSN shall replace all of the EPS or GPRS subscription data of the user in the MME or SGSN. Any optional EPS or GPRS data not received, but stored in the standalone MME or SGSN, shall be deleted. + +For a combined MME/SGSN, if EPS subscription data of the user is received, it shall replace all of the EPS subscription data of the user. Any optional EPS data not received by the combined MME/SGSN, but stored in the MME/SGSN, shall be deleted. + +For a combined MME/SGSN, if GPRS subscription data of the user is received, it shall replace all of the GPRS subscription data of the user. Any optional GPRS data not received by the combined MME/SGSN, but stored in the MME/SGSN, shall be deleted. + +When receiving an Update Location response from the HSS, the MME or SGSN shall check the result code. If it indicates success the MME or SGSN shall store the received subscription profile (if any), and it shall store the HSS identity as received in the Origin-Host AVP. + +If an Additional MSISDN (A-MSISDN) is available in the subscription data and downloaded in the A-MSISDN AVP to the MME/SGSN in an Update Location and if the MME or SGSN supports the additional MSISDN feature, the MME or SGSN shall use the Additional MSISDN as C-MSISDN. + +For UEs receiving emergency services (i.e. emergency attached UEs or normal attached UEs with a UE Requested PDN Connection for emergency services), and if the MME or SGSN supports emergency services for users in limited service state, the MME or SGSN shall proceed even if the Update Location procedure fails (e.g. authenticated users with roaming restrictions or RAT-Type restrictions in HSS). + +When receiving GPRS-Subscription-Data AVP in the response, the SGSN or combined MME/SGSN shall delete all the stored PDP-Contexts, if there are any, and then store all the received PDP-Contexts. + +When receiving the APN-Configuration-Profile AVP in a ULA, the MME or SGSN shall delete all the stored APN-Configurations, if there are any, and then store all the received APN-Configurations. + +For each of the received APN-Configurations in the APN-Configuration-Profile, if both the MIP6-Agent-Info and the PDN-GW-Allocation-Type AVPs are absent in the APN-Configuration AVP and the MME or SGSN does not have any associated PGW information, the MME or SGSN shall perform the PGW selection (static or dynamic) according to the local configuration. If MIP6-Agent-Info is present, and PDN-GW-Allocation-Type is not present, this means that the PDN GW address included in MIP6-Agent-Info has been statically allocated. If the MIP6-Agent-Info contains an FQDN of the PDN GW, the MME shall retrieve the PGW PLMN ID from the MIP-Home-Agent-Host AVP within the MIP6-Agent-Info AVP. + +When receiving an Update Location response from the HSS in the TAU or RAU procedure, for each of the received APN-Configurations in the APN-Configuration-Profile, if both the MIP6-Agent-Info and the PDN-GW-Allocation-Type AVPs are absent in the APN-Configuration AVP and the MME or SGSN has associated PGW information and the UE-level access restriction "HO-To-Non-3GPP-Access Not Allowed" is not set, the MME or SGSN should send a Notify Request if HO to the WLAN is supported in the network, including the APN and PDN GW identity to the HSS in order to restore this information in the HSS e.g. after a Reset procedure. + +If the MME/SGSN supports interworking with Gn/Gp-SGSNs, it shall ensure that the Context -Identifier sent over GTPv1 for each of the received APN-Configurations is within the range of 1 and 255. + +NOTE 1: If the MME/SGSN receives from HSS a Context-Identifier value higher than 255, how this value is mapped to a value between 1 and 255 is implementation specific. + +If the subscriber is not roaming and the SIPTO-Permission information for an APN is present, the MME or SGSN shall allow SIPTO above RAN for that APN only if the SIPTO-Permission information indicates so. + +If the subscriber is not roaming and the SIPTO-Permission information for an APN is not present, the MME or SGSN may allow SIPTO above RAN for that APN. + +If the subscriber is roaming and the SIPTO-Permission information for an APN is present, the MME or SGSN shall allow SIPTO above RAN for that APN only if the SIPTO-Permission information indicates so and the VPLMN Dynamic Address is allowed and the MME or SGSN selects a PDN GW in the VPLMN. + +If the subscriber is roaming and the SIPTO-Permission information for an APN is not present, the MME or SGSN shall not allow SIPTO above RAN for that APN. + +NOTE 2: Based on local configuration, the MME or SGSN can determine not to allow SIPTO above RAN for an APN, regardless if the SIPTO-Permission information is present. + +If the subscriber is not roaming and the SIPTO-Local-Network-Permission information for an APN is present, the MME or SGSN shall allow SIPTO at the local network for that APN only if the SIPTO-Local-Network-Permission information indicates so. + +If the subscriber is not roaming and the SIPTO-Local-Network-Permission information for an APN is not present, the MME or SGSN may allow SIPTO at the local network for that APN. + +If the subscriber is roaming and the SIPTO-Local-Network-Permission information for an APN is present, the MME or SGSN shall allow SIPTO at the local network for that APN only if the SIPTO-Local-Network-Permission information indicates so and the VPLMN Dynamic Address is allowed and the MME or SGSN selects a L-GW in the VPLMN. + +If the subscriber is roaming and the SIPTO-Local-Network-Permission information for an APN is not present, the MME or SGSN shall not allow SIPTO at the local network for that APN. + +NOTE 3: Based on local configuration, the MME or SGSN can determine not to allow SIPTO at the local network for an APN, regardless if the SIPTO-Local-Network-Permission information is present. + +If MPS-Priority AVP is present and the UE is subscribed to the eMLPP or 1x RTT priority service in the CS domain as indicated by the MPS-CS-Priority bit of the AVP, the MME shall allow the UE to initiate the RRC connection with higher priority than other normal UEs during CS Fallback procedure. If the MPS-Priority AVP is present and the UE is subscribed to MPS in the EPS domain as indicated by the MPS-EPS-Priority bit of the AVP, the MME shall allow the UE to initiate the RRC connection with higher priority than other normal UEs. + +If the subscriber is not roaming, the MME or SGSN may allow or prohibit the UE to use LIPA as indicated by LIPA-Permission for a specific APN. + +If the subscriber is roaming and the VPLMN-LIPA-Allowed AVP indicates that the UE is not allowed to use LIPA in the VPLMN where the UE is attached, the MME or SGSN shall not provide LIPA for the UE and shall not consider the LIPA-Permission AVP. If the VPLMN-LIPA-Allowed AVP indicates that the UE is allowed to use LIPA in the VPLMN, the MME or SGSN may allow or prohibit the UE to use LIPA as indicated by LIPA-Permission for a specific APN. The VPLMN-Dynamic-Address-Allowed AVP shall not be considered if it is received when the MME or SGSN establishes a PDN connection with LIPA. + +If the LIPA-Permission information for an APN indicates LIPA only, the MME or SGSN shall only allow LIPA for that APN via the authorized CSGs according to the CSG Subscription Data. If the LIPA-Permission information for an APN indicates LIPA prohibited, the MME or SGSN shall not allow LIPA for that APN. If the LIPA-Permission information for an APN indicates LIPA conditional, the MME or SGSN shall allow non LIPA, and LIPA for that APN via the authorized CSGs according to the CSG Subscription Data. If the LIPA-Permission AVP is not present for a specific APN, the APN shall not be allowed to use LIPA. + +The LIPA-Permission information for the Wildcard APN shall apply to any APN that is not explicitly present in the subscription data. + +The SIPTO-Permission information for the Wildcard APN shall apply to any APN that is not explicitly present in the subscription data. + +The SIPTO-Local-Network-Permission information for the Wildcard APN shall apply to any APN that is not explicitly present in the subscription data. + +If the subscription data received for a certain APN indicates that the APN was authorized as a consequence of having the Wildcard APN in the user subscription in HSS, then the MME shall not store this APN data beyond the lifetime of the UE session and the MME shall delete them upon disconnection of the UE. + +If the MME supports the Relay Node functionality (see 3GPP TS 36.300 [40]) and the subscription data indicates that the subscriber is not a relay, the MME shall reject the attach request from a device attempting to attach to EPS as a Relay Node. If a device requests to be attached to EPS as an UE, the MME shall proceed with the attach procedure regardless of the content of the Relay Node Indicator. + +If trace data are received in the subscriber data, the MME or SGSN shall start a Trace Session. For details, see 3GPP TS 32.422 [23]. + +If the Ext-PDP-Type AVP is present in the PDP-Context AVP, the SGSN or combined MME/SGSN shall ignore the value of the PDP-Type AVP. + +If the subscriber is not roaming and the Subscribed-Periodic-RAU-TAU-Timer information is present, the MME or SGSN shall allocate the subscribed value to the UE as periodic RAU or TAU timer. If the subscriber is roaming and the Subscribed-Periodic-RAU-TAU-Timer information is present, the MME or SGSN may use the subscribed periodic RAU/TAU timer value as an indication to decide for allocating a locally configured periodic RAU/TAU timer value to the UE. + +For a combined MME/SGSN, the node may include the Coupled-Node-Diameter-ID AVP to allow the HSS to determine if the UE is served by the MME and SGSN parts of the same combined MME/SGSN. When the message is sent over S6a interface and if this AVP is included, the MME shall include the Diameter identity of the coupled SGSN which is used by the SGSN over S6d interface. When the message is sent over S6d interface and if this AVP is included, the SGSN shall include the Diameter identity of the coupled MME which is used by the MME over S6a interface. + +NOTE 4: The Coupled-Node-Diameter-ID AVP allows the HSS to determine if the UE is served by the MME and SGSN parts of the same combined MME/SGSN, when the SGSN number is not available and when Diameter identity of S6a and S6d interfaces of the combined MME/SGSN are not the same. + +If the MME supports the "SMS in MME" feature and the UE has requested a combined EPS/IMSI attach or Combined TA/LA Update (see 3GPP TS 23.272 [44]) and the MME is not currently registered for SMS, the MME requests to be registered for SMS by indicating its MME Number for MT SMS in the request, including the SMS-Register-Request AVP and the SMS-Only-Indication flag set in the ULR-Flags AVP if UE indicates "SMS only". + +If the MME supports the "SMS in MME" feature, when receiving an EPS attach or a TAU from a UE accessing NB-IoT which requests SMS by indicating "SMS transfer without Combined Attach" (see 3GPP TS 23.401 [2]), and if the MME is not currently registered for SMS, the MME requests to be registered for SMS by indicating its MME Number for MT SMS in the request, including the SMS-Register-Request AVP. + +If the HSS provides the MME with SMS data in the ULA and the ULA-Flags is received with "MME Registered for SMS" flag set, the MME shall store this data for providing SMS in MME service and consider itself registered for SMS. + +If the SGSN supports the "SMS in SGSN" feature as specified in 3GPP TS 23.060 [12], clause 5.3.18, and wishes to provide SMS via SGSN it shall set the "SMS in SGSN" flag in the Feature-List AVP, and include SMS-Register-Request AVP. If the SGSN supports the Diameter based Gdd interface for SMS in SGSN, it shall set the "Gdd-in-SGSN" flag in the Feature-List AVP. If the UE has indicated "SMS-Only" this shall be indicated to the HSS setting the SMS-Only-Indication flag in the ULR-Flags AVP. + +NOTE 5: the setting of the "SMS in SGSN" feature bit reflects the "SMS in SGSN Offered" as described in stage 2 above. + +If the SMS-In-SGSN-Allowed-Indication flag is set in the received Subscription-Data-Flags AVP, the SGSN shall store the subscription data for providing SMS in SGSN service. + +If the subscriber is not roaming and the Restoration-Priority information for a certain APN is present, the MME or SGSN shall consider the subscribed value as the relative priority of the user's PDN connection among PDN connections to the same APN when restoring PDN connections affected by an SGW or PGW failure/restart (see 3GPP TS 23.007 [43]). If the subscriber is roaming and the Restoration-Priority information for a certain APN is present, the MME or SGSN may use the subscribed value as an indication of the relative priority of the user's PDN connection among PDN connections to the same APN based on service level agreements. The MME/SGSN may use a locally configured value as default restoration priority if the Restoration-Priority AVP for a certain APN is not present, or if it is not permitted by service level agreements for an in-bound roamer. + +If the subscription data received for a certain APN includes WLAN-offloadability AVP, then the MME or SGSN shall determine the offloadability of the UE's PDN Connection(s) to that APN based on subscription data and locally configured policy (e.g. for roaming users or when the subscription data does not include any offloadability indication). + +NOTE 6: As indicated in clause 7.3.31, if the UE-level access restriction "HO-To-Non-3GPP-Access Not Allowed" is set, the offload of PDN Connections to WLAN is not allowed for any APN. + +If the subscription data received for the user includes the DL-Buffering-Suggested-Packet-Count AVP, then the MME or SGSN should take into account the subscription data, in addition to local policies, to determine whether to invoke extended buffering of downlink packets at the SGW for High Latency Communication. Otherwise, the MME or SGSN shall make this determination based on local policies only. + +When receiving IMSI-Group-Id AVP(s) within the Subscription-Data AVP, the MME or SGSN shall replace stored IMSI-Group Ids (if any) with the received information rather than add the received information to the stored information. + +When receiving one or more Monitoring-Event-Configuration AVP(s) in the ULA, the MME or SGSN shall start the detection of the Monitoring events indicated in those AVP(s), if not already started, and shall stop the detection and delete the previous monitoring events (if any) which are not indicated in those AVP(s). If there is a failure when starting + +the detection (e.g. maximum resources exceeded), the MME or SGSN shall not store the failed configuration(s) and shall send a notification of those events whose configuration have failed, as described in clause 5.2.5.1.2 (NOR/NOA commands). If the Subscription-Data AVP is received in the ULA but it does not contain any Monitoring-Event-Configuration AVP(s), the MME or SGSN shall stop the detection and delete all stored monitoring event configurations (if any). + +If the MME/SGSN supports Monitoring, the MME/SGSN shall include the Supported-Services AVP with Supported-Monitoring-Events included in the ULR command. + +If the MME and the UE support Attach without PDN connection (i.e. EMM-REGISTERED without PDN connection) and the PDN-Connection-Restricted flag is set in the received Subscription-Data-Flags AVP, the MME shall not establish any non-emergency PDN connection and shall tear down any existing non-emergency PDN connection for this user. + +If the subscription data received for the user includes the Preferred-Data-Mode AVP, for an IP APN configuration or for a non-IP APN configuration with SGi based delivery, then the MME should (if the subscriber is not roaming) or may (if the subscriber is roaming) take into account the subscription data, in addition to local policies and the UE's Preferred Network Behaviour, to determine whether to transmit the traffic associated with this APN over the User Plane and/or over the Control Plane. Otherwise, the MME shall make this determination based on local policies and the UE's Preferred Network Behaviour only. + +If the MME receives from the HSS an Update Location response containing the Emergency-Info AVP in the Subscription-Data, the MME shall use the PDN-GW identity included in Emergency-Info as the PDN-GW used to establish emergency PDN connections with the emergency APN, for non-roaming authenticated UEs requesting the handover of an emergency PDN connection if the MME is configured to use a dynamic PDN-GW for emergency services for such user. + +When receiving V2X-Subscription-Data in the ULA, the MME shall determine whether the UE is authorized to use V2X communication over PC5 according to V2X subscription data and UE provided network capability. If the UE is authorized to use V2X communication over PC5, the MME shall store the "V2X service authorized" indication together with the UE AMBR used for PC5 interface (i.e. UE-PC5-AMBR), and provide such information to the eNodeB when needed. + +If the MME/SGSN receives from the HSS an Update Location response without the bit set for "NR as Secondary RAT" in the Feature-List AVP, the MME/SGSN, based on local policy, may restrict access for NR as secondary RAT when all relevant entities except HSS supports it. + +If the MME receives from the HSS an Update Location response containing in the subscription data the Core-Network-Restrictions AVP with the bit "5GC not allowed" set, the MME shall restrict mobility towards 5GC. + +### 5.2.1.1.3 Detailed behaviour of the HSS + +When receiving an Update Location request the HSS shall check whether subscription data exists for the IMSI. + +If the HSS determines that there is not any type of subscription for the IMSI (including EPS, GPRS and CS subscription data), a Result Code of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned. + +If the Update Location Request is received over the S6a interface, and the subscriber has not any APN configuration, the HSS shall return a Result Code of DIAMETER\_ERROR\_UNKNOWN\_EPS\_SUBSCRIPTION. + +If the Update Location Request is received over S6a, from an MME that does not support the "Non-IP PDN Type APNs" feature, and the user's subscription profile contains only APN configurations of type "Non-IP", the HSS shall return a Result Code of DIAMETER\_ERROR\_UNKNOWN\_EPS\_SUBSCRIPTION. + +If the Update Location Request is received over the S6d interface, and the subscriber has neither an APN configuration profile nor GPRS subscription data, the HSS shall return a Result Code of DIAMETER\_ERROR\_UNKNOWN\_EPS\_SUBSCRIPTION. + +When sending DIAMETER\_ERROR\_UNKNOWN\_EPS\_SUBSCRIPTION, an Error Diagnostic information may be added to indicate whether or not GPRS subscription data are subscribed (i.e. whether or not Network Access Mode stored in the HSS indicates that only CS service is allowed). + +The HSS shall check whether the RAT type the UE is using is allowed for the subscriber in the serving PLMN. If it is not, a Result Code of DIAMETER\_ERROR\_RAT\_NOT\_ALLOWED shall be returned. + +The HSS shall check whether access to EPC is allowed, based on the active Core Network Restrictions of the subscriber. If access to EPC is restricted, a Result Code of DIAMETER\_ERROR\_UNKNOWN\_EPS\_SUBSCRIPTION shall be returned. + +The HSS shall check whether roaming is not allowed in the VPLMN due to ODB. If so a Result Code of DIAMETER\_ERROR\_ROAMING\_NOT\_ALLOWED shall be returned. When this error is sent due to the MME or SGSN not supporting a certain ODB category, an Error Diagnostic information element may be added to indicate the type of ODB; if this error is sent due to the ODB indicating "Barring of Roaming", Error Diagnostic shall not be included. + +If the Update Location Request is received over the S6d interface and the HSS supports the "SGSN CAMEL Capability" feature, and the SGSN indicates support of SGSN CAMEL capability, the HSS shall check if the subscriber has SGSN CAMEL Subscription data. If the subscriber has SGSN CAMEL Subscription data, the HSS shall return a Result Code of DIAMETER\_ERROR\_CAMEL\_SUBSCRIPTION\_PRESENT. + +If the Update Location Request is received over the S6a interface, the HSS shall send a Cancel Location Request with a Cancellation-Type of MME\_UPDATE\_PROCEDURE (CLR; see chapter 7.2.7) to the previous MME (if any) and replace the stored MME-Identity with the received value (the MME-Identity is received within the Origin-Host AVP). The HSS shall reset the "UE purged in MME" flag and delete any stored last known MME location information of the (no longer) purged UE. If the "Single-Registration-Indication" flag was set in the received request, the HSS shall send a Cancel Location Request with a Cancellation-Type of SGSN\_UPDATE\_PROCEDURE to the SGSN (MAP Cancel Location), and delete the stored SGSN address and SGSN number. If the "Initial-Attach-Indicator" flag was set in the received request, and the "Single-Registration-Indication" flag was not set, the HSS shall send a Cancel Location Request with a Cancellation-Type of INITIAL\_ATTACH\_PROCEDURE (CLR; see chapter 7.2.7, or MAP Cancel Location) to the SGSN if there is an SGSN registration. + +If the Update Location Request is received over the S6d interface, the HSS shall send a Cancel Location Request with a Cancellation-Type of SGSN\_UPDATE\_PROCEDURE (CLR; see chapter 7.2.7, or MAP Cancel Location) to the previous SGSN (if any) and replace the stored SGSN-Identity with the received value (the SGSN-Identity is received within the Origin-Host AVP). The HSS shall reset the "UE purged in SGSN" flag and delete any stored last known SGSN location information of the (no longer) purged UE. If the "Initial-Attach-Indicator" flag was set in the received request, the HSS shall send a Cancel Location Request with a Cancellation-Type of INITIAL\_ATTACH\_PROCEDURE (CLR; see chapter 7.2.7) to the MME if there is an MME registration. + +When the HSS receives the Update Location Request, if a 15th digit of the IMEI AVP is received, the HSS may discard the digit. + +If the Update Location Request includes the list of active APNs, the HSS shall delete all the stored dynamic PDN GW information, if there are any, and then replace them by the PDN GW information received in the list of Active-APN AVPs. + +If the Update Location Request includes an equivalent PLMN list, the HSS shall return the CSG list (if any) for each equivalent PLMN to the MME with the subscription data, and Visited-PLMN-Id AVP shall be present in the CSG-Subscription-Data AVP to indicate the corresponding PLMN. If there is no equivalent PLMN list received, the HSS may not include Visited-PLMN-Id AVP in the CSG-Subscription-Data AVP, and the CSG-Subscription-Data AVP shall contain the CSG subscription data of the registered PLMN of the MME or the SGSN. + +If the Update Location Request is received over the S6a interface for a user for which the URRP-MME parameter is set in the HSS, the HSS shall clear the URRP-MME parameter and send an indication to the corresponding Service Related Entities. + +If the Update Location Request is received over the S6d interface for a user for which the URRP-SGSN parameter is set in the HSS, the HSS shall clear the URRP-SGSN parameter and send an indication to the corresponding Service Related Entities. + +If no result code has been sent to the MME or SGSN so far, the HSS shall include the subscription data in the ULA command according to the ULR-Flags and the supported/unsupported features of the MME or SGSN, unless an explicit "skip subscriber data" indication has been received in the request, and shall return a Result Code of DIAMETER\_SUCCESS. + +When the APN-Configuration-Profile AVP is present in the Subscription-Data AVP sent within a ULA, the AVP shall contain at least the default APN Configuration and a Context-Identifier AVP that identifies the per subscriber's default APN configuration. The default APN Configuration shall not contain the Wildcard APN (see 3GPP TS 23.003 [3], clause 9.2); the default APN shall always contain an explicit APN. + +The GPRS Subscription data (if available in the HSS) shall only be present in the ULA command if it was indicated by the serving node in the ULR-Flags AVP (see clause 7.3.7), or when the subscription data is returned by a Pre-Rel-8 HSS (via an IWF) or when the Update Location Request is received over the S6d interface and there is no APN configuration profile stored for the subscriber. + +The HSS shall use the indication received in the GPRS-Subscription-Data-Indicator for future use in the subscriber data update procedures. + +The HSS shall store the new terminal information and/or the new UE SRVCC capability, if they are present in the request. If the UE SRVCC capability is not present, the HSS shall store that it has no knowledge of the UE SRVCC capability. + +If the MME/SGSN indicates support of the Additional-MSISDN feature and an additional MSISDN (A-MSISDN) is available in the subscription data, the HSS shall send the provisioned additional MSISDN together with the MSISDN. + +If the MME/SGSN does not support the Additional-MSISDN feature, the HSS shall populate the MSISDN AVP either with the subscribed MSISDN or the subscribed additional MSISDN based on operator policy and availability. + +NOTE: When the MME/SGSN does not support the Additional-MSISDN feature, the MME/SGSN will use the MSISDN from the MSISDN AVP as C-MSISDN. + +LCS-Info, Teleservice-List and Call-Barring-Info data shall be included according to the list of supported features indicated by the serving node (see clause 7.3.10). + +If the HSS supports the "SMS in MME" feature and receives the indication that the MME supports the "SMS in MME" feature and requests to be registered for SMS by including the MME Number for MT SMS, SMS-Register-Request AVP and/or setting the SMS-Only-Indication flag in the ULR-Flags AVP if indicated from the UE, the HSS shall determine if SMS can be provided via the MME as described in 3GPP TS 23.272 [44]. If SMS in MME is accepted the HSS shall register the MME for SMS, store the "MME number for MT SMS" as the corresponding MSC number to be used for MT SMS and return an indication of MME registered for SMS in ULA-Flags AVP. + +If the MME is successfully registered for SMS the HSS shall download the available SMS related subscription data that may comprise SMS teleservice, MSISDN, ODB and barring services for SMS according to supported features. Also, if the user is considered as not reachable (i.e., MNRF flag is set in HSS for that user), and the UE is considered to have free available memory (i.e., MCEF flag is not set in HSS for that user), the HSS shall send a MAP-Alert-Service-Centre message or S6c-Alert-Service-Centre-Request to the SMS-IWMSC (see 3GPP TS 29.338 [48]). + +If the HSS supports the "SMS in SGSN" feature as described in 3GPP TS 23.060 [12], clause 5.3.18 and receives the indication from the SGSN that it supports "SMS in SGSN" feature, and SMS-Register-Request AVP and/or the SMS-Only-Indication flag in the ULR-Flags AVP if indicated from the UE, and the PS subscriber data allow for SMS services (e.g. the subscription information indicates "PS and SMS-Only"), the HSS shall determine if SMS can be provided via the SGSN as described in 3GPP TS 23.060 [12]. If "SMS in SGSN" is accepted the HSS shall indicate in the ULA that "SMS in SGSN" is allowed to the SGSN and shall handle MT SMS as described in 3GPP TS 23.060 [12], clause 5.3.18. If the HSS supports the "Gdd-in-SGSN" feature and receives the indication from the SGSN that it supports the "Gdd-in-SGSN" feature, the HSS shall store the information that the SGSN supports the Gdd interface. Also, if the user is considered as not reachable (i.e., MNRF flag is set in HSS for that user), and the UE is considered to have free available memory (i.e., MCEF flag is not set in HSS for that user), the HSS shall send a MAP-Alert-Service-Centre message or S6c-Alert-Service-Centre-Request to the SMS-IWMSC (see 3GPP TS 29.338 [48]). + +The HSS may use the indication received in the Node-Type-Indicator for future use in the subscriber data update procedures. + +Subscriber-Status AVP shall be present in the Subscription-Data AVP when sent within a ULA. If the value "OPERATOR\_DETERMINED\_BARRING" is sent, the Operator-Determined-Barring AVP or HPLMN-ODB AVP shall also be present in the Subscription-Data AVP, or vice versa. + +Access-Restriction-Data AVP shall be present within the Subscription-Data AVP sent within a ULA if at least one of the defined restrictions applies. + +The AMBR AVP shall be present in the Subscription-Data AVP when the APN-Configuration-Profile AVP is sent within a ULA (as part of the Subscription-Data AVP) and may be present in the Subscription-Data AVP when the GPRS-Subscription-Data AVP is present. + +The EPS-Subscribed-QoS-Profile AVP and the AMBR AVP shall be present in the APN-Configuration AVP when the APN-Configuration AVP is sent in the APN-Configuration-Profile AVP and when the APN-Configuration-Profile AVP is sent within a ULA (as part of the Subscription-Data AVP). + +For those APNs that have been authorized as a consequence of having the Wildcard APN in the user subscription, the HSS shall include the specific APN name and associated PDN-GW identity inside the APN context of the Wildcard APN. This indicates to the MME that the particular APN shall not be cached in the MME and it shall be deleted when the UE session is terminated. + +If a Result Code of DIAMETER\_SUCCESS is returned, the HSS shall set the Separation Indication in the response. + +If the HSS receives an indication in the ULR command about the homogeneous support of IMS Voice over PS Sessions in all TA/RAs associated to a serving node, it may use this information in the future in order to skip the T-ADS data retrieval, as described in clause 5.2.2.1 (IDR/IDA commands). + +Subscribed-VSRVCC AVP shall be present within the Subscription-Data AVP sent within a ULA only if the user is subscribed to the SRVCC and vSRVCC. + +If the UE is allowed to use Proximity-based Services in the visited PLMN, the HSS shall include ProSe-Subscription-Data AVP within the Subscription-Data AVP sent within a ULA. + +If the HSS receives the SGs MME identity and if the HSS supports this information element, the HSS shall store it for use with VLR restoration. + +If the HSS receives Update Location Request over both the S6a and S6d interfaces then based on the following conditions the HSS concludes if the UE is served by the MME and SGSN parts of the same combined MME/SGSN: + +- if both the messages contain the same SGSN number; or +- if the Diameter identity received over S6a matches with the Diameter identity received over S6d; or +- if the Coupled-Node-Diameter-ID AVP received over S6a interface matches with the Diameter identity received within Origin-Host AVP over S6d interface OR if the Coupled-Node-Diameter-ID AVP received over S6d interface matches with the Diameter identity received within Origin-Host AVP over S6a interface. + +If the HSS supports the handling of access restrictions for adjacent PLMNs, and it receives a list of adjacent PLMNs from the MME/SGSN, the HSS may send the associated Access Restriction Data, according to local operator policies, in the Adjacent-Access-Restriction-Data AVP, so the MME/SGSN can use this information to allow, or prevent, inter-RAT inter-PLMN handovers towards any of the PLMNs indicated by the HSS. The HSS shall not include in the list of Adjacent-Access-Restriction-Data the PLMN-ID, and its access restrictions, of the current PLMN where the MME/SGSN is located, since this information is already conveyed in the Access-Restriction-Data AVP inside the Subscription-Data AVP. + +If the HSS supports Monitoring events and receives a Supported-Services AVP it shall only trigger those services which are supported by the MME/SGSN. + +If the HSS has previously received over SWx (see 3GPP TS 29.273 [59]) the identity of the PDN-GW to be used for the establishment of emergency PDN connections, it shall include it as part of the Subscription-Data AVP (in the Emergency-Info AVP), in the Update Location response to the MME. + +If the UE is allowed to use V2X service in the visited PLMN and the MME supports V2X service, the HSS shall include V2X-Subscription-Data AVP into Subscription-Data AVP within the ULA command. + +If the MME/SGSN supports the "External-Identifier" feature, the HSS shall include the External-Identifier associated with Monitoring Event Configuration in the External-Identifier AVP if populated in the subscription. When multiple External Identifiers are defined for a same subscription, the HSS shall send a default External Identifier in the External-Identifier AVP of the Subscription-Data AVP, and shall include a specific External Identifier (if different from the default External Identifier) associated to each Monitoring Event Configuration in the External-Identifier AVP of each Monitoring-Event-Configuration AVP occurrence inside the Subscription-Data AVP. + +The Aerial-UE-Subscription-Information AVP shall be present within the Subscription-Data AVP sent within a ULA only if the user has Aerial UE subscription information. + +## 5.2.1.2 Cancel Location + +### 5.2.1.2.1 General + +The Cancel Location Procedure shall be used between the HSS and the MME and between the HSS and the SGSN to delete a subscriber record from the MME or SGSN. The procedure shall be invoked by the HSS and is used: + +- to inform the MME or SGSN about a subscription withdrawal, or a change in the subscriber profile that does not allow PS services anymore (e.g., the Network Access Mode does not allow PS services), or a change in the subscriber profile that does not allow access to EPC anymore, or +- to inform the MME or SGSN about an ongoing update procedure i.e. MME or SGSN change or +- to inform the MME or SGSN about an initial attach procedure. + +This procedure is mapped to the commands Cancel-Location-Request/Answer (CLR/CLA) in the Diameter application specified in chapter 7. + +Table 5.2.1.2.1/1 specifies the involved information elements for the request. + +Table 5.2.1.2.1/2 specifies the involved information elements for the answer. + +**Table 5.2.1.2.1/1: Cancel Location Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|------------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | User-Name (See IETF RFC 6733 [61]) | M | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [3], clause 2.2. | +| Supported Features (See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Cancellation Type (See 7.3.24) | Cancellation-Type | M | Defined values that can be used are:
- MME-Update Procedure,
- SGSN-Update Procedure,
- Subscription Withdrawal,
- Update Procedure_IWF,
- Initial Attach Procedure. | +| CLR Flags (See 7.3.152) | CLR-Flags | O | This Information Element contains a bit mask. See 7.3.152 for the meaning of the bits and the condition for each bit to be set or not. | + +**Table 5.2.1.2.1/2: Cancel Location Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|-----------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported Features (See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Result (See 7.4) | Result-Code / Experimental-Result | M | The result of the operation.
The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [61]). | + +### 5.2.1.2.2 Detailed behaviour of the MME and the SGSN + +When receiving a Cancel Location request the MME or SGSN shall check whether the IMSI is known. + +If it is not known, a result code of DIAMETER\_SUCCESS is returned. + +If it is known, the MME or SGSN shall check the Cancellation Type and act accordingly. + +If the Cancellation Type is "Subscription Withdrawal", the MME or SGSN shall delete the subscription data and detach the UE; in addition, if the Reattach-Required flag is set, the MME or SGSN shall indicate to the UE to initiate an immediate re-attach procedure, as described in 3GPP TS 23.401 [2] and 3GPP TS 23.060 [12]. A result code of DIAMETER\_SUCCESS shall be returned. + +If a cancellation type of "Initial Attach Procedure" is received, the MME or SGSN shall not delete the subscription data. For details see 3GPP TS 23.401 [2] and 3GPP TS 23.060 [12]. If the MME receives this cancellation type, and it is registered for SMS, it shall consider itself as unregistered for SMS. Also in this case a result code of DIAMETER\_SUCCESS shall be returned. + +When a UE is served by a single combined MME/SGSN for both E-UTRAN and non-E-UTRAN access, the combined MME/SGSN shall check the Cancellation-Type. If it indicates Subscription Withdrawal or Update Procedure\_IWF, the CLR is processed both in the MME part and in the SGSN part of the combined node. If it indicates Initial Attach Procedure, and if the CLR-Flags AVP is received and supported by the combined MME/SGSN, the CLR is processed only in the affected part of the combined node as indicated by the "S6a/S6d-Indicator" flag in the CLR-Flags AVP. Otherwise, the CLR is processed only in the affected part of the combined node and subscription data are kept for the not affected part. + +### 5.2.1.2.3 Detailed behaviour of the HSS + +The HSS shall make use of this procedure when the subscription is withdrawn by the HSS operator, and when the HSS detects that the UE has moved to a new MME or SGSN area, and when EPC access is not allowed due to Core Network Restrictions. + +The HSS+UDM shall also make use of this procedure when the HSS+UDM detects that the UE has moved to a new AMF area, if the AMF indicates to the HSS+UDM to cancel MME and/or SGSN. The HSS+UDM shall include a cancellation type as specified in clause 5.4.2.2 of 3GPP TS 29.563 [70]. + +The HSS shall include a cancellation type of "Subscription Withdrawal" if the subscription is withdrawn by the operator, or if the subscriber profile does not allow PS services anymore, or if the Core Network Restrictions do not allow access to EPC anymore; the HSS may set the Reattach-Required flag in order to request the MME or the SGSN to trigger an immediate reattachment of the UE. + +The HSS shall include a cancellation type of "MME Update Procedure" if the UE moved to a new MME area. + +The HSS shall include a cancellation type of "SGSN Update Procedure" if the UE moved to a new SGSN area. + +The HSS shall include a cancellation type of "Initial Attach Procedure" if the cancel location is initiated due to an Initial Attach from the UE. + +The HSS shall include the CLR-Flags with the "S6a/S6d-Indicator" flag indicating the affected part of the combined node if the cancel location is to be sent to a combined MME/SGSN during initial attach procedure. + +### 5.2.1.3 Purge UE + +#### 5.2.1.3.1 General + +The Purge UE Procedure shall be used between the MME and the HSS and between the SGSN and the HSS to indicate that the subscriber's profile has been deleted from the MME or SGSN either by an MMI interaction or automatically, e.g. because the UE has been inactive for several days. + +This procedure is mapped to the commands Purge-UE-Request/Answer (PUR/PUA) in the Diameter application specified in chapter 7. + +Table 5.2.1.3.1/1 specifies the involved information elements for the request. + +Table 5.2.1.3.1/2 specifies the involved information elements for the answer. + +**Table 5.2.1.3.1/1: Purge UE Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|------------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------| +| IMSI | User-Name (See IETF RFC 6733 [61]) | M | This information element shall contain user IMSI, formatted according to 3GPP TS 23.003 [3], clause 2.2. | +| Supported Features (See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| PUR-Flags (See 7.3.149) | PUR-Flags | O | If present, this Information Element shall contain a bitmask. See clause 7.3.149 for the meaning of the bits. | +| EPS-Location-Information (See 7.3.111) | EPS-Location-Information | C | This Information Element shall contain the last known EPS-Location Information of the purged UE. Shall be present if available. | + +**Table 5.2.1.3.1/2: Purge UE Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|-----------------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported Features (See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Result (See 7.4) | Result-Code / Experimental-Result | M | This IE shall contain the result of the operation. The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [61]). The Experimental-Result AVP shall be used for S6a/S6d errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. The following errors are applicable:
- User Unknown | +| PUA-Flags (See 7.3.48) | PUA-Flags | C | This Information Element shall contain a bit mask. See clause 7.3.48 for the meaning of the bits. It shall be present only when the Result-Code AVP is DIAMETER_SUCCESS. | + +### 5.2.1.3.2 Detailed behaviour of the MME and the SGSN + +The MME shall make use of this procedure to set the "UE Purged in the MME" flag in the HSS when the subscription profile is deleted from the MME database due to MMI interaction or after long UE inactivity. + +The SGSN shall make use of this procedure to set the "UE Purged in SGSN" flag in the HSS when the subscription profile is deleted from the SGSN database due to MMI interaction or after long UE inactivity. + +The combined MME/SGSN when using a single Origin-Host identity shall make use of this procedure to set the "UE Purged in MME" and "UE Purged in SGSN" flags in the HSS when the subscription profile is deleted from the common MME/SGSN database due to MMI interaction or after long UE inactivity on all registered accesses. If the HSS has indicated support for the Partial Purge feature (see clause 7.3.10), the combined MME/SGSN may also indicate to the HSS a Purge of the UE in only one of the serving nodes in the combined node (either in the MME or in the SGSN). + +The combined MME/SGSN when using different Origin-Host identities for MME and SGSN shall send two **Purge UE Requests** as if it was not combined. + +When receiving a Purge UE response from the HSS the MME shall check the Result Code. If it indicates success, the MME shall check the PUA flag "freeze M-TMSI", and if set freeze the M-TMSI i.e. block it for immediate re-use. + +When receiving a Purge UE response from the HSS the SGSN shall check the Result Code. If it indicates success, the SGSN shall check the PUA flag "freeze P-TMSI", and if set freeze the P-TMSI i.e. block it for immediate re-use. + +When receiving a Purge UE response from the HSS the combined MME/SGSN shall check the Result Code. If it indicates success, the combined MME/SGSN shall check the PUA flag "freeze M-TMSI" and "freeze P-TMSI", and if set freeze the M-TMSI and/or the P-TMSI i.e. block it for immediate re-use. + +### 5.2.1.3.3 Detailed behaviour of HSS + +When receiving a Purge UE request the HSS shall check whether the IMSI is known. + +If it is not known, a result code of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned. + +If it is known, the HSS shall set the result code to DIAMETER\_SUCCESS and compare the received identity in the Origin-Host with the stored MME-Identity and with the stored SGSN-Identity. + +If the received identity matches the stored MME-identity and the stored SGSN-Identity (no matter whether the node type indicator bit in ULR-Flags was set or clear), then: + +- if the HSS supports the Partial Purge feature (see clause 7.3.10), and the combined MME/SGSN indicated that the UE was purged in only one of the serving nodes, the HSS shall set the PUA flags according to the serving node where the purge was done (i.e., either "freeze M-TMSI" if the purge was done in the MME, or "freeze P-TMSI" if the purge was done in the SGSN); similarly, the HSS shall either set the "UE purged in MME" flag and store the received last known MME Location information of the purged UE, or set the "UE purged in SGSN" flag and store the received last known SGSN-Location Information of the purged UE, accordingly; +- if the HSS does not support the Partial Purge feature, or the combined MME/SGSN did not indicate that the UE was purged in only one of the serving nodes, the HSS shall set the PUA flags "freeze M-TMSI" and "freeze P-TMSI" in the answer message and set the flag "UE purged in MME" and "UE purged in SGSN" and store the received last known EPS Location Information of the purged UE; + +If the received identity matches the stored MME-identity but not the stored SGSN-identity, the HSS shall set the PUA flag "freeze M-TMSI" and clear the PUA flag "freeze P-TMSI" in the answer message, set the flag "UE purged in MME" and store the received last known MME location information of the purged UE; + +If the received identity matches the stored SGSN-identity but not the stored MME-identity, the HSS shall set the PUA flag "freeze P-TMSI" and clear the PUA flag "freeze M-TMSI" in the answer message and set the flag "UE purged in SGSN" and store the received last known SGSN location information of the purged UE; + +If the received identity does not match the stored MME-identity and does not match the stored SGSN-identity, the HSS shall clear the PUA flags "freeze M-TMSI" and "freeze P-TMSI" in the answer message. + +## 5.2.2 Subscriber Data Handling Procedures + +### 5.2.2.1 Insert Subscriber Data + +#### 5.2.2.1.1 General + +The Insert Subscriber Data Procedure shall be used between the HSS and the MME and between the HSS and the SGSN for updating and/or requesting certain user data in the MME or SGSN in the following situations: + +- due to administrative changes of the user data in the HSS and the user is now located in an MME or SGSN, i.e. if the user was given a subscription and the subscription has changed; subscription data that are applicable to MMEs but not to SGSNs should not be sent to the SGSN unless the SGSN is known to be a combined MME/SGSN; similarly subscription data that are applicable to SGSNs but not to MMEs should not be sent to the MME unless the MME is known to be a combined MME/SGSN. +- the operator has applied, changed or removed Operator Determined Barring for this user; +- activate subscriber tracing in the MME or the SGSN; +- to indicate to the MME or SGSN that the HSS has requested to be notified when the UE has become reachable; +- to request from the MME or SGSN the necessary data to support the T-ADS functionality; +- to retrieve location information and/or state information from the MME or the SGSN; + +- to retrieve from the MME or the SGSN the Local Time Zone of the location in the visited network where the UE is attached; +- to update the STN-SR (e.g., as a result of an Sh interaction with an SCC-AS). +- to update the MME/SGSN with the identity of a dynamically allocated PDN GW as a result of the first PDN connection establishment associated with an APN over non 3GPP access. +- to update the MME with the identity of a PDN GW for Emergency Services as a result of the PDN connection establishment for Emergency Services over non 3GPP access. +- to indicate to the MME that the HSS has deregistered the MME for SMS. +- to indicate to the MME/SGSN that the HSS-based P-CSCF restoration procedure, as described in 3GPP TS 23.380 [51] clause 5.4, shall be executed. +- to request the MME or the SGSN to configure and report the detection of Monitoring events, or delete stored Monitoring events configuration. +- to update the MME with the O&M configured desired Active Time for power saving mode (PSM), or with the value received from the SCEF if Active Time is provided as part of the Suggested-Network-Configuration AVP. +- to update the MME with the O&M configured desired Core Network Restrictions to restrict/allow mobility to 5GC. + +If the HSS knows that the UE has attached to the MME and SGSN parts of the same combined MME/SGSN via both the E-UTRAN and UTRAN/GERAN (refer to clause 5.2.1.1.2, 5.2.1.1.3 for further details), the HSS should invoke this procedure for a single time to update and/or request certain user data in the combined MME/SGSN, i.e. the HSS should not invoke this procedure for each of the MME and the SGSN registered respectively. + +If the Node-Type-Indicator information has been previously received as cleared in the ULR-Flags and if the MME has not been registered for SMS during update location procedure for the MME, the HSS may skip any change of the SMS related subscription data and consequently does not have to make use of the Insert Subscriber Data procedure to update the SMS subscription data in the MME. + +This procedure is mapped to the commands Insert Subscriber Data-Request/Answer (IDR/IDA) in the Diameter application specified in clause 7. + +Table 5.2.2.1.1/1 specifies the involved information elements for the request. + +Table 5.2.2.1.1/2 specifies the involved information elements for the answer. + +**Table 5.2.2.1.1/1: Insert Subscriber Data Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|-------------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | User-Name (See IETF RFC 673 3 [61]) | M | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [3], clause 2.2. | +| Supported Features (See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Subscription Data (See 7.3.2) | Subscription-Data | M | This Information Element shall contain the part of the subscription profile that either is to be added to the subscription profile stored in the MME or SGSN or is replacing a part of the subscription profile stored in the MME or SGSN. | +| IDR Flags (See 7.3.103) | IDR-Flags | C | This Information Element shall contain a bit mask. See 7.3.103 for the meaning of the bits. | +| Reset-IDs (See 7.3.184) | Reset-ID | O | The Reset-ID uniquely identifies a fallible resource in the HSS on which the user (IMSI) depends. In the event of a restart of the fallible resource a Reset message containing the Reset-ID will exactly identify the impacted subscribers. | + +**Table 5.2.2.1.1/2: Insert Subscriber Data Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported Features
(See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host.
A combined MME/SGSN that makes use of separate origin host values in Update Location Request messages sent on S6a and Update Location Request messages sent on S6d can detect whether the IDR from HSS was sent to the MME or to the SGSN.
IDA sent from such combined MME/SGSN corresponds to the MME's or the SGSN's supported features respectively.
A combined MME/SGSN that makes use of a common origin host value in Update Location Request messages sent on S6a and Update Location Request messages sent on S6d cannot detect whether the IDR from HSS was sent to the MME or to the SGSN.
IDA sent from such combined MME/SGSN uses the union of the MME's and the SGSN's supported features. | +| Result
(See 7.4) | Result-Code / Experimental-Result | M | This IE shall contain the result of the operation.
Result-Code AVP shall be used to indicate success / errors defined in the Diameter base protocol (see IETF RFC 6733 [61]).
The Experimental-Result AVP shall be used for S6a/S6d errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.
The following errors are applicable in this case:
- User Unknown | +| IMS Voice over PS Sessions Supported
(See 7.3.106) | IMS-Voice-Over-PS-Sessions-Supported | C | If available to the serving node, this information element shall indicate whether or not "IMS Voice over PS Sessions" is supported by the UE's most recently used TA or RA in the serving node (MME or SGSN or combined MME/SGSN). If the UE is in detached state, this information element shall not be included in the response. | +| Last UE Activity Time
(See 7.3.108) | Last-UE-Activity-Time | C | If available to the serving node, this information element shall contain the time of the last radio contact with the UE. If the UE is in detached state, this information element shall not be included in the response. | +| RAT Type
(See 7.3.13) | RAT-Type | C | If available to the serving node, this information element shall indicate the RAT Type of the access where the UE was present at the time of the last radio contact. If the UE is in detached state, this information element shall not be included in the response. | +| IDA-Flags
(See 7.3.47) | IDA-Flags | C | This Information Element shall contain a bit mask. See 7.3.47 for the meaning of the bits. | +| EPS-User-State
(See 7.3.110) | EPS-User-State | C | This Information Element shall contain the EPS-User State. It shall be present if EPS user state was requested within IDR. | +| EPS-Location-Information
(See 7.3.111) | EPS-Location-Information | C | This Information Element shall contain the EPS-Location Information. It shall be present if EPS location information was requested within IDR. | +| Local Time Zone
(See 7.3.156) | Local-Time-Zone | C | This Information Element shall contain information on the Local Time Zone of the location in the visited network where the UE is attached. It shall be present if the Local Time Zone was requested within IDR. | +| Monitoring Event Report | Monitoring-Event-Report | C | This Information Element shall contain the report of Monitoring event. It shall be present if Monitoring event configuration is included within IDR and any of the requested Monitoring events are available to be reported. (see NOTE 1) | +| Monitoring Event Config Status | Monitoring-Event-Config-Status | C | This Information Element shall be present if Monitoring event configuration is included in IDR. It shall contain all the configuration status for each Monitoring event that was requested. | +| Supported Services
(3GPP TS 29.336 [54]) | Supported-Services | O | If present, this Information Element shall contain AVPs indicating details of the services supported by the MME/SGSN. | +| NOTE 1: In IWK-SCEF scenarios, an event is available to be reported by the visited MME only if the event is considered as authorized by the visited MME after checking with the IWK-SCEF. Otherwise, the immediate report shall be not be sent in this command (S6a/IDA), and it shall be sent over T6a using RIR command (see 3GPP TS 29.128 [63]). | | | | + +#### 5.2.2.1.2 Detailed behaviour of the MME and the SGSN + +When receiving an Insert Subscriber Data request the MME or SGSN shall check whether the IMSI is known. + +If it is not known, a result code of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned. + +If it is known, the MME or SGSN shall replace the specific part of the stored subscription data with the received data, or shall add the received data to the stored data. + +When receiving the APN-Configuration-Profile AVP within the Subscription-Data AVP, the MME or SGSN shall check the All-APN-Configurations-Included-Indicator value. If it indicates "All\_APN\_CONFIGURATIONS\_INCLUDED", the MME or SGSN shall delete all stored APN-Configurations and then store all received APN-Configurations. Otherwise, the MME or SGSN shall check the Context-Identifier value of each received APN-Configuration. If the Context-Identifier of a received APN-Configuration matches a Context-Identifier of a stored APN-Configuration, the MME or SGSN shall replace the stored APN-Configuration with the received APN-Configuration. If the Context-Identifier of a received APN-Configuration does not match a Context-Identifier of a stored APN-Configuration, the MME or SGSN shall add the received APN-Configuration to the stored APN-Configurations. If the addition or update of the subscription data succeeds in the MME or SGSN, the Result-Code shall be set to DIAMETER\_SUCCESS. The MME or SGSN shall then acknowledge the Insert Subscriber Data message by returning an Insert Subscriber Data Answer. + +For each of the received APN-Configurations in the APN-Configuration-Profile, if both the MIP6-Agent-Info and the PDN-GW-Allocation-Type AVPs are absent in the APN-Configuration AVP, the MME or SGSN shall perform the PGW selection (static or dynamic) according to the local configuration. If MIP6-Agent-Info is present, and PDN-GW-Allocation-Type is not present, this means that the PDN GW address included in MIP6-Agent-Info has been statically allocated. + +If the MME/SGSN supports interworking with Gn/Gp-SGSNs, it shall ensure that the context identifier sent over GTPv1 for each of the received APN-Configurations is within the range of 1 and 255. + +NOTE 1: If the MME/SGSN receives from HSS a Context-Identifier value higher than 255, how this value is mapped to a value between 1 and 255 is implementation specific. + +If the MME is requested to notify the HSS when the UE becomes reachable, the MME shall set the URRP-MME parameter to indicate the need to inform the HSS about UE reachability, e.g. when the next NAS activity from the UE is detected. If the SGSN is requested to notify the HSS when the UE becomes reachable, the SGSN shall set the URRP-SGSN parameter to indicate the need to inform the HSS about UE reachability, e.g. when the next NAS activity from the UE is detected. + +When receiving GPRS-Subscription-Data AVP within the Subscription-Data AVP, the SGSN or combined MME/SGSN shall check the Complete-Data-List-Included-Indicator value. If it indicates "All\_PDP\_CONTEXTS\_INCLUDED", the SGSN or combined MME/SGSN shall delete all stored PDP-Contexts and then store all received PDP-Contexts. Otherwise, the SGSN or combined MME/SGSN shall check the Context-Identifier value of each received PDP-Context. If the Context-Identifier of a received PDP-Context matches a Context-Identifier of a stored PDP-Context, the SGSN or combined MME/SGSN shall replace the stored PDP-Context with the received PDP-Context. If the Context-Identifier of a received PDP-Context does not match a Context-Identifier of a stored PDP-Context, the SGSN or combined MME/SGSN shall add the received PDP-Context to the stored PDP-Contexts. + +If the MME or SGSN receives an empty Subscription-Data AVP, it shall take no action with regard to the stored subscription data. + +When receiving HPLMN-ODB AVP within the Subscription-Data AVP, the MME or SGSN shall replace stored HPLMN-ODB data (if any) with the received information rather than add the received information to the stored information. Unsupported Barring categories need not be stored. + +When receiving Operator-Determined-Barring AVP within the Subscription-Data AVP, the MME or SGSN shall replace stored ODB subscription information (if any) with the received information rather than add the received information to the stored information. Unsupported Barring categories need not be stored. + +When receiving Access-Restriction-Data or Adjacent-Access-Restriction-Data AVPs within the Subscription-Data AVP, the MME or SGSN shall replace the corresponding stored information (if any) with the new received information, rather than adding received information to stored information. The handling of access restrictions per-PLMN is defined in 3GPP TS 23.221 [53], clause 6.3.5a and in 3GPP TS 23.401 [2] clause 4.3.28. + +When receiving APN-OI-Replacement AVP within the Subscription-Data AVP, the MME or SGSN shall replace the stored information (if any) with the received information. + +When receiving Regional-Subscription-Zone-Code AVP within the Subscription-Data AVP, the MME or SGSN shall replace stored Zone Codes (if any) with the received information rather than add the received information to the stored information. MMEs and SGSNs that do not support regional subscription need not store zone codes. If due to regional subscription restrictions or access restrictions the entire SGSN area is restricted, SGSN shall report it to the HSS by returning the "SGSN Area Restricted" indication within the IDA flags. + +When receiving CSG-Subscription-Data AVPs within the Subscription-Data AVP the MME or SGSN shall replace all stored information from previously received CSG-Subscription-Data AVPs (if any) with the received information rather than add the received information to the stored information. + +When receiving Teleservice-List AVP, Call-Barring-Info, or LCS-Info AVP, the MME or SGSN shall replace stored information (if any) with the received information rather than add the received information to the stored information. + +When receiving ProSe-Subscription-Data AVP, the MME or combined MME/SGSN shall replace stored information (if any) with the received information rather than add the received information to the stored information. + +When receiving and supporting Reset-ID AVPs within the request, the MME or SGSN shall replace stored information (if any) with received information rather than add received information to stored information. + +When receiving the IDR-Flags with the "T-ADS Data Request" bit set, and the UE is in attached state, the MME or SGSN or combined MME/SGSN shall return in the IDA message the time stamp of the UE's most recent radio contact and the associated RAT Type, and an indication of whether or not IMS Voice over PS is supported in the current (and most recently used) TA or RA. If the UE is in detached state, the MME or SGSN or combined MME/SGSN shall answer successfully to the T-ADS request from HSS, but it shall not include any of the T-ADS IEs in the response (IMS Voice over PS Sessions Supported, RAT Type and Last UE Activity Time). + +When receiving the IDR-Flags with the "EPS User State Request" bit and/or "EPS Location Information Request" bits set the MME or SGSN shall return the corresponding user information to the HSS. If the serving node is a combined MME/SGSN, and the UE is attached via both E-UTRAN and UTRAN/GERAN on the same node, the combined MME/SGSN shall provide the corresponding user information relevant for both MME and SGSN. If the Current Location Request bit was also set and the UE is in idle mode and is expected to be reachable even when it uses a power saving feature (e.g. extended idle mode DRX or PSM as defined in 3GPP TS 23.685 [55]), then the MME or SGSN or combined MME/SGSN shall page the UE in order to return the most up-to-date corresponding user information. If the Current Location Request bit was also set and either paging is unsuccessful or the UE is not expected to be reachable, then the last known location of the UE shall be returned to the HSS. If the Current Location Request bit was also set and the UE (attached via E-UTRAN) is in connected mode, then the MME or combined MME/SGSN shall use SIAP Location Reporting Control procedure towards the eNB prior to reporting the E-UTRAN Cell Global Identification in order to return the UE's most up-to-date cell information. When the location is returned to the HSS, the MME or the combined MME/SGSN shall provide the age of location information if stored in the MME or the combined MME/SGSN or received from eNB. + +When receiving the IDR-Flags with only the "Current Location Request" bit set (i.e. the "EPS Location Information Request" bit is not set), the MME or SGSN or combined MME/SGSN shall set the Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. + +If the "Local Time Zone Request" bit was set the MME or SGSN if supported shall provide the Local Time Zone corresponding to the location (e.g. TAI or RAI) of the UE to the HSS. + +If the MME or SGSN cannot fulfil the received request, e.g. due to a database error or any of the required actions cannot be performed, it shall set the Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. If subscription data are received, the MME or SGSN shall mark the subscription record "Subscriber to be restored in HSS". + +If trace data are received in the subscriber data, the MME or SGSN shall start a Trace Session. For details, see 3GPP TS 32.422 [23]. + +If the Ext-PDP-Type AVP is present in the PDP-Context AVP, the SGSN or combined MME/SGSN shall ignore the value of the PDP-Type AVP. + +When receiving the IDR-Flags with the bit "Remove SMS Registration" set, the MME shall consider itself unregistered for SMS. + +If the subscription data received for a certain APN includes WLAN-offloadability AVP, then the MME or SGSN shall determine the offloadability of the UE's PDN Connection(s) to that APN based on subscription data and locally configured policy (e.g. for roaming users or when the subscription data does not include any offloadability indication). + +NOTE 2: As indicated in clause 7.3.31, if the UE-level access restriction "HO-To-Non-3GPP-Access Not Allowed" is set, the offload of PDN Connections to WLAN is not allowed for any APN. + +When receiving the IDR-Flags with the "P-CSCF Restoration Request" bit set, the MME or SGSN or combined MME/SGSN shall execute the procedures for HSS-based P-CSCF Restoration, as described in 3GPP TS 23.380 [51] clause 5.4. + +If the subscription data received for the user includes the DL-Buffering-Suggested-Packet-Count AVP, then the MME or SGSN should take into account the subscription data, in addition to local policies, to determine whether to invoke extended buffering of downlink packets at the SGW for High Latency Communication. Otherwise, the MME or SGSN shall make this determination based on local policies only. + +When receiving IMSI-Group-Id AVP(s) within the Subscription-Data AVP, the MME or SGSN shall replace stored IMSI-Group Ids (if any) with the received information rather than add the received information to the stored information. + +In the present clause, if the feature "Extended Reference IDs" (see clause 7.3.10) is supported by the HSS and the MME/SGSN, the term "SCEF Reference ID" shall refer to the content of the 64-bit long "SCEF-Reference-ID-Ext" AVP, and the term "SCEF Reference ID for Deletion" shall refer to the content of the 64-bit long "SCEF-Reference-ID-for-Deletion-Ext" AVP. + +When receiving a Monitoring-Event-Configuration in the IDR: + +- if the SCEF Reference ID for Deletion is present in the IDR, the MME or SGSN shall stop the detection of the Monitoring event related to the SCEF Reference ID for Deletion and SCEF-ID pair, and shall delete the corresponding Monitoring event configuration data; +- if the SCEF Reference ID is present in the IDR but not stored in the MME or SGSN, the MME or SGSN shall store the received Monitoring event configuration data related to the SCEF Reference ID and SCEF-ID pair, and shall start the detection for the specified Monitoring event(s). +- if the SCEF Reference ID is present in the IDR and stored in the MME or SGSN, the MME or SGSN shall replace the stored Monitoring event configuration data related to the SCEF Reference ID and SCEF-ID pair with the received information. + +NOTE 3: In roaming scenarios the MME/SGSN can reply immediately to the HSS without waiting for the outcome of the interaction with the IWK-SCEF. + +For the monitoring event configurations for which the configuration status have changed since the last status informed to the HSS, the MME/SGSN shall notify the HSS about the outcome of the interaction with the IWK-SCEF as specified in clause 5.2.5.1.2. + +If the HSS indicates the support of Monitoring event feature to the MME/SGSN and the MME/SGSN supports Monitoring, the MME/SGSN shall include the Supported-Services AVP with Supported-Monitoring-Event included in the IDA command. + +When receiving the Maximum-Response-Time in Monitoring-Event-Configuration in IDR, the MME shall use the Maximum-Response-Time as the Active Time for the usage of PSM in UE. If not, when the MME receives the Active-Time in subscription data, the MME shall use the Active-Time as the Active Time for the usage of PSM in UE. + +When receiving AESE-Communication-Pattern AVP(s) within the Subscription-Data AVP with an SCEF Reference ID for which the MME has already stored data, it shall delete the stored data (CP set(s)) and store the received ones. + +When receiving AESE-Communication-Pattern AVP(s) within the Subscription-Data AVP with one or more SCEF Reference ID for deletion the MME shall delete the data related to the indicated SCEF Reference ID. + +If the MME and the UE support an Attach without PDN connection (i.e. EMM-REGISTERED without PDN connection) and the PDN-Connection-Restricted flag is set in the received Subscription-Data-Flags AVP, the MME shall not establish any non-emergency PDN connection and shall tear down any existing non-emergency PDN connection for this user. + +If the subscription data received for the user includes the Preferred-Data-Mode AVP, for an IP APN configuration or for a non-IP APN configuration with SGi based delivery, then the MME should (if the subscriber is not roaming) or may (if the subscriber is roaming) take into account the subscription data, in addition to local policies and the UE's Preferred Network Behaviour, to determine whether to transmit the traffic associated with this APN over the User Plane and/or over the Control Plane. Otherwise, the MME shall make this determination based on local policies and the UE's Preferred Network Behaviour only. + +If the MME subscription data received for the user includes the Emergency-Info AVP, the MME shall use the PDN-GW identity contained in such AVP as the PDN-GW used to establish emergency PDN connections with the emergency APN, for non-roaming authenticated UEs requesting the handover of an emergency PDN connection if the MME is configured to use a dynamic PDN-GW for emergency services for such user. + +When receiving V2X-Subscription-Data in the IDR, the MME shall determine whether the UE is authorized to use V2X communication over PC5 according to V2X subscription data and UE provided network capability. If the UE is authorized to use V2X communication over PC5, the MME shall store the "V2X service authorized" indication together with the UE AMBR used for PC5 interface (i.e. UE-PC5-AMBR), and provide such information to the eNodeB when needed. + +If the MME/SGSN receives from the HSS an Insert Subscriber Data request without the bit set for "NR as Secondary RAT" in the Feature-List AVP, the MME/SGSN, based on local policy, may restrict access for NR as secondary RAT when all relevant entities except HSS supports it. + +If the MME receives from the HSS Insert Subscriber Data request containing in the subscription data the Core-Network-Restrictions AVP with the bit "5GC not allowed" set, the MME shall restrict mobility towards 5GC. + +#### 5.2.2.1.3 Detailed behaviour of HSS + +The HSS shall make use of this procedure to replace a specific part of the user data stored in the MME or SGSN with the data sent, or to add a specific part of user data to the data stored in the MME or SGSN. The HSS shall also make use of this procedure to indicate to the MME that it is no longer registered for SMS. + +NOTE: When a Cancel Location message is required for other reasons, the use of IDR to indicate that the MME is no longer registered for SMS is not needed (see clause 5.2.1.2). + +Subscriber-Status AVP shall be present in the Subscription-Data AVP, sent within IDR, if the current value in the MME or SGSN needs to be changed. To remove all Operator Determined Barring Categories the Subscriber-Status shall be set to "SERVICE\_GRANTED". If Subscriber-Status AVP is present and set to OPERATOR\_DETERMINED\_BARRING, the Operator-Determined-Barring AVP or HPLMN-ODB AVP shall also be present in the Subscription-Data AVP. + +Access-Restriction-Data AVP shall be present within the Subscription-Data AVP sent within an IDR if the information stored in the MME or SGSN needs to be modified. + +APN-OI-Replacement AVP shall be present in the Subscription-Data AVP sent within an IDR, if the UE level APN-OI-Replacement has been added or modified in the HSS. + +The APN-Configuration-Profile AVP shall be present in the Subscription-Data AVP sent within an IDR if the Context-Identifier associated with the default APN configuration is changed or at least one APN-Configuration is added or modified by the HSS. If the default APN is changed in the HSS, the APN-Configuration-Profile AVP shall contain the Context-Identifier associated with the default APN and the APN-Configuration AVP for the default APN. The default APN Configuration shall not contain the Wildcard APN (see 3GPP TS 23.003 [3], clause 9.2); the default APN shall always contain an explicit APN. + +The EPS-Subscribed-QoS-Profile AVP and the AMBR AVP shall be present in the APN-Configuration AVP when the APN-Configuration AVP is sent in the APN-Configuration-Profile AVP and when the APN-Configuration-Profile AVP is sent within an IDR (as part of the Subscription-Data AVP). + +If the GPRS-Subscription-Data-Indicator information has been previously received as set in the ULR-Flags during update location procedure for the SGSN or combined MME/SGSN, the HSS shall make use of this procedure to replace the GPRS Subscription Data stored in the SGSN or combined MME/SGSN with the data sent or to add a PDP-Context to the data stored in the SGSN or combined MME/SGSN. + +ProSe-Subscription-Data AVP shall be present in the Subscription-Data AVP sent within an IDR, if the ProSe Subscription data has been added or modified in the HSS. + +If the HSS receives a message (e.g. via MAP ATM or Sh Sh-Subs-Notif) from a Service Related Entity (e.g. IP-SM-GW) indicating that the UE is unreachable, + +- the HSS shall associate the subscription to UE reachability of the service-related entity to the URRP-MME and the URRP-SGSN parameters (if not already done) +- and if the URRP-MME and/or the URRP-SGSN parameters were not already set (i.e. at least one service-related entity already listed as subscribed), the HSS shall + - set the URRP-MME and/or URRP-SGSN parameters and + - send an IDR command to the registered MME and/or to the registered SGSN including the "UE Reachability Request flag" in the IDR Request Flags in order to request the MME and/or SGSN to notify the HSS when the UE becomes reachable again, unless the HSS knows from the previous ULR command that the registered MME and/or the registered SGSN do not support UE reachability notifications. + +If the IDR is sent for the only purpose to request the MME and/or SGSN about the UE reachability status notification, the Subscription-Data AVP shall be included empty. + +If the HSS has received a message from a service related entity requesting EPS User State and/or EPS Location Information without the Serving Node Indication IE, the HSS shall set the "EPS User State Request" bit and/or "EPS Location Information Request" bit respectively in the IDR-Flags. The HSS may optionally also set the "Current Location Request" bit along with the "EPS Location Information Request" bit in the IDR-Flags, if the most up-to-date set of information is needed, unless the HSS knows from the previous ULR command that the registered MME and/or the registered SGSN do not support State/Location Information retrieval. If the IDR is sent only for the purpose of requesting the MME or the SGSN User State or Location Information, the Subscription-Data AVP included shall be empty. + +If the HSS cannot request EPS Location Information from the MME/SGSN e.g. because the UE is purged from the MME/SGSN, the HSS may make use of stored EPS Location information received in a previous IDA or PUR message. + +If the HSS has received a message from an AS requesting the current access network's support status of "IMS Voice over PS Sessions", and there is no indication about homogeneous support of IMS Voice over PS Sessions in all the serving nodes currently registered in HSS for the UE, the HSS shall set the "T-ADS Data Request flag" in the IDR Request Flags, unless the HSS knows from the previous ULR command that the registered MME and/or the registered SGSN do not support T-ADS data retrieval. If the IDR is sent for the only purpose to retrieve the "IMS Voice over PS Sessions Supported" indication from the MME or SGSN, the Subscription-Data AVP included shall be empty. + +If the HSS has received a message from an AS requesting the Local Time Zone, the HSS shall set the "Local Time Zone Request" bit in the IDR-Flags, unless the HSS knows from the previous ULR command that the registered MME and/or the registered SGSN do not support Local Time Zone retrieval. If the IDR is sent only for the purpose of requesting the Local Time Zone, the Subscription-Data AVP included shall be empty. + +If the HSS received an indication in a former ULR command from the MME or SGSN about homogeneous support of IMS Voice over PS Sessions in all TA/RAs associated to that serving node, it may use this information to skip the retrieval of T-ADS data. This can only be done if all the registered serving nodes in HSS for the UE indicated in ULR the same type of homogeneous support (i.e. both serving nodes indicated "SUPPORTED", or both serving nodes indicated "NOT\_SUPPORTED"); otherwise, the retrieval of T-ADS data shall be done, to receive the time of the last radio contact with the UE. + +All APN and PGW-ID pairs stored in the HSS not associated with an explicit APN subscription, (i.e. the access to that APN has been authorized as a consequence of having the Wildcard APN in the user subscription), shall be included by the HSS inside the APN context of the Wildcard APN, as multiple instances of the Specific-APN-Info AVP. + +When receiving an Insert Subscriber Data answer with "SGSN Area Restricted" the HSS shall set the SGSN area restricted flag as "SGSN area restricted". + +Subscribed-VSRVCC AVP may be present within the Subscription-Data AVP sent within an ISR only if the user is subscribed to the SRVCC and vSRVCC. + +If the HSS determines that the MME shall be unregistered for SMS it shall set the "Remove SMS Registration" bit in the IDR-Flags. If the IDR is sent for the only purpose to indicate that the MME is no longer registered for SMS, the Subscription-Data AVP shall be included empty. + +If the HSS needs to request to the MME/SGSN the execution of the HSS-based P-CSCF restoration procedure, as described in 3GPP TS 23.380 [51] clause 5.4, the HSS shall set the "P-CSCF Restoration Request" bit in the IDR-Flags, if supported by the MME/SGSN. If the IDR is sent only for the purpose of requesting the execution of the HSS-based P-CSCF restoration procedures, the Subscription-Data AVP included shall be empty. + +If the HSS receives a SCEF request to configure Monitoring events for the UE to be handled by the MME/SGSN or receives a SCEF request for deleting Monitoring events for the UE in the MME/SGSN, the HSS shall include Monitoring-Event-Configuration AVP(s) in the Subscription-Data AVP sent within the IDR. If the HSS has registered both an MME and an SGSN as serving nodes for a given user, and both nodes are not part of a same combined MME/SGSN node, the HSS shall send the Monitoring-Event-Configuration AVP(s) to each one of the serving nodes that supports the Monitoring event service. If the HSS receives the IDA with Monitoring-Event-Report AVP(s), the HSS shall forward the Monitoring-Event-Report AVP(s) to the SCEF associated to those Monitoring events. + +If the HSS does not receive a SCEF request to configure Monitoring events for the UE to be handled by the MME/SGSN and does not receive an Active Time with the Suggested-Network-Configuration AVP, the HSS may send an O&M configured desired Active Time value within the Active-Time AVP. + +If the HSS receives a Supported-Services AVP it shall only trigger those services which are supported by the MME/SGSN. + +If the HSS has previously received over SWx (see 3GPP TS 29.273 [59]) the identity of the PDN-GW to be used for the establishment of emergency PDN connections, it shall send it to the registered MME (if any) in the IDR command as part of the Subscription-Data AVP (in the Emergency-Info AVP). + +If V2X subscription data has been added or modified in the HSS, the HSS shall include the V2X-Subscription-Data AVP in the Subscription-Data AVP sent within an IDR. + +If the External-Identifier associated with Monitoring Event Configuration for the UE has been added or modified in the HSS and the MME/SGSN supports the "External-Identifier" feature, the HSS shall include the External-Identifier AVP in the Subscription-Data AVP. When multiple External Identifiers are defined for a same subscription, the HSS shall send a default External Identifier in the External-Identifier AVP of the Subscription-Data AVP, and shall include a specific External Identifier (if different from the default External Identifier) associated to each Monitoring Event Configuration in the External-Identifier AVP of each Monitoring-Event-Configuration AVP occurrence inside the Subscription-Data AVP. + +The Aerial-UE-Subscription-Information AVP may be present within the Subscription-Data AVP sent within an IDR only if the user has Aerial UE subscription information. + +If Core Network Restrictions in subscription data (5GC allowed/not allowed) has been added or modified in the HSS, the HSS shall include the Core-Network-Restrictions AVP in the Subscription-Data AVP sent within an IDR. + +## 5.2.2.2 Delete Subscriber Data + +### 5.2.2.2.1 General + +This procedure shall be used between the MME and the HSS and between the SGSN and the HSS, to remove some data of the HSS user profile stored in the MME or SGSN. The procedure shall be invoked by the HSS and it corresponds to the functional level operation Delete Subscriber Data (see 3GPP TS 23.401 [2]). + +It shall be used to remove: + +- a subset (which may or may not be the complete set of APN configurations) of the APN Configuration Profile for the subscriber from the SGSN or combined MME/SGSN; +- a proper subset (i.e. a subset that is not equal to the complete set of APN configurations and does not contain the default APN configuration) of the APN Configuration Profile for the subscriber from the MME; +- the regional subscription; +- the subscribed charging characteristics; +- Session Transfer Number for SRVCC; +- trace data; + +- ProSe subscription data; +- Reset-IDs; +- MSISDN; +- UE Usage Type; +- V2X subscription data. +- External Identifier(s). + +If the HSS knows that the UE has attached to the MME and SGSN parts of the same combined MME/SGSN via both E-UTRAN and UTRAN/GERAN(refer to clause 5.2.1.1.2, 5.2.1.1.3 for further details), the HSS should invoke this procedure for a single time to remove some or all data of the HSS user profile stored in the combined MME/SGSN, i.e. not invoke this procedure for each of the MME and the SGSN registered respectively. + +If the Node-Type-Indicator information has been previously received as cleared in the ULR-Flags and if the MME has not been registered for SMS during update location procedure for the MME, the HSS may skip any removal of the SMS related subscription data and consequently does not have to make use of the Delete Subscriber Data procedure to update the SMS subscription data in the MME. + +This procedure is mapped to the commands Delete-Subscriber-Data-Request/Answer (DSR/DSA) in the Diameter application specified in chapter 7. + +Table 5.2.2.2.1/1 specifies the involved information elements for the request. + +Table 5.2.2.2.1/2 specifies the involved information elements for the answer. + +**Table 5.2.2.2.1/1: Delete Subscriber Data Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|---------------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | User-Name
(See IETF RFC 6733 [61]) | M | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [3], clause 2.2. | +| Supported Features
(See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| DSR Flags
(See 7.3.25) | DSR-Flags | M | This Information Element shall contain a bit mask. See 7.3.25 for the meaning of the bits. | +| Trace Reference
(See 7.3.64) | Trace-Reference | C | This parameter shall contain the same value as used for the activation of the Trace Session.
This element shall be present only if the "Trace Data Withdrawal" bit is set in the DSR-Flags. | +| Context Identifier
(See 7.3.27) | Context-Identifier | C | This parameter shall identify the PDN subscription context or GPRS-PDP context that shall be deleted.
This element shall be present only if the "PDN subscription contexts Withdrawal" bit or the "PDP context withdrawal" bit is set in the DSR-Flags.
In the "PDN subscription contexts Withdrawal" case, the Context-Identifier shall not be associated with the default APN configuration.
For the compatibility with the MAP protocol as defined in the 3GPP TS 29.002 [24], this parameter shall not have a value of zero. | +| TS Code List
(See 7.3.100) | TS-Code | C | This parameter shall contain the teleservice codes that are to be deleted from the subscription.
This element shall be present only if the "SMS Withdrawal" bit is set in the DSR-Flags and the SMS related teleservice codes are to be deleted. | +| SS Code List
(See 7.3.87) | SS-Code | C | This parameter shall contain the supplementary service codes that are to be deleted from the subscription.
This element shall be present only if the "SMS Withdrawal" bit is set or the "LCS Withdrawal" bit is set in the DSR-Flags. | +| SCEF-Id
(See 3GPP TS 29.336 [54]) | SCEF-ID | C | This parameter shall contain the identity of the SCEF to which monitoring events that are to be deleted are associated.
This element shall be present if the "Delete monitoring events" bit is set in the DSR-Flags. | +| eDRX Related RAT List | eDRX-Related-RAT | C | This parameter shall contain the RAT types for which the eDRX Cycle Lengths is to be deleted from the subscription.
This element shall be present only if the "eDRX-Cycle-Length-Withdrawal" bit is set in the DSR-Flags and the corresponding eDRX Cycle Lengths are to be deleted.
If the "eDRX-Cycle-Length-Withdrawal" bit is set in DSR-Flags, but the eDRX-Related-RAT AVP is absent in this command, the MME/SGSN shall delete the stored eDRX cycle lengths for all RATs. | +| External Identifiers | External-Identifiers | O | If present, this parameter shall contain the External Identifier(s) to be deleted from the subscriber data; the MME/SGSN shall also delete those monitoring events that include an External-Identifier AVP in their event configuration matching any of the External-Identifiers in this IE.
This IE shall be absent if the "External-Identifier-Withdrawal" bit is not set in the DSR-Flags.
If this IE is absent, and "External-Identifier-Withdrawal" bit is set in DSR-Flags, the MME/SGSN shall delete the default External-Identifier in the Subscription-Data AVP and it shall also delete all monitoring events that include an External-Identifier AVP in their event configuration. | + +**Table 5.2.2.2.1/2: Delete Subscriber Data Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|-----------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported Features
(See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Result
(See 7.4) | Result-Code / Experimental-Result | M | This IE shall contain the result of the operation.
The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [61]).
The Experimental-Result AVP shall be used for S6a/S6d errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.
The following errors are applicable in this case:
- User Unknown | +| DSA Flags
(See 7.3.26) | DSA-Flags | C | This Information Element shall contain a bit mask. See 7.3.26 for the meaning of the bits. | + +## 5.2.2.2.2 Detailed behaviour of the MME and the SGSN + +When receiving a Delete Subscriber Data request, the MME or SGSN shall check whether the IMSI is known. + +If it is not known, a result code of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned. + +If it is known, but the Context-Identifier is associated with the default APN configuration, the MME shall not delete the PDN subscription context, and return an error with a Result-Code set to DIAMETER\_UNABLE\_TO\_COMPLY. + +Otherwise, the MME or SGSN shall delete the corresponding data according to the indication as sent in the request, and acknowledge the Delete Subscriber Data message by returning a Delete Subscriber Data Answer. + +If an MME receives a Delete Subscriber Data Request with the "Complete APN Configuration Profile Withdrawal" bit set in the DSR-Flags AVP, it shall return an error with a Result-Code set to DIAMETER\_UNABLE\_TO\_COMPLY. + +If the deletion of the subscription data succeeds in the MME or SGSN, the Result-Code shall be set to DIAMETER\_SUCCESS. + +If the Regional Subscription is deleted from the subscription data, the SGSN shall check for its routing areas whether they are allowed or not. If the entire SGSN area is restricted, SGSN shall report it to the HSS by returning the "SGSN Area Restricted" indication within the DSA flags. + +If the EPS Subscription Data is deleted from the subscription data, the MME or SGSN shall check whether all EPS Subscription Data for the subscriber is deleted or if only a subset of the stored EPS Subscription Data for the subscriber is deleted, the MME or SGSN may then deactivate the associated affected active EPS bearers. + +If the Subscribed Charging Characteristics are deleted from the subscription data, the Gn/Gp-SGSN shall maintain the existing Subscribed Charging Characteristics throughout the lifetime of the existing MM and PDP contexts, see 3GPP TS 32.251 [33]. + +If the Subscribed Charging Characteristics are deleted from the subscription data, the MME or S4-SGSN shall maintain the existing Subscribed Charging Characteristics throughout the lifetime of the existing IP CAN bearer, see 3GPP TS 32.251 [33]. + +If the MSISDN is deleted from the subscription data, the MME or SGSN shall maintain the existing MSISDN throughout the lifetime of the existing PDN connections that were established prior to the deletion of the MSISDN (i.e., other network nodes, such as PDN-GW, are not informed of such deletion for the existing PDN connections). + +If the MME or SGSN cannot fulfil the received request for other reasons, e.g. due to a database error, it shall set the Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. In this case, the MME or SGSN shall mark the subscription record "Subscriber to be restored in HSS". + +If trace data are deleted from the subscription data, the MME or SGSN shall deactivate the Trace Session identified by the trace reference. For details, see 3GPP TS 32.422 [23]. + +If External Identifiers are requested to be deleted from the subscription data, the MME/SGSN shall check whether any of the identifiers to be deleted match the default External-Identifier provided by HSS in the Subscription-Data AVP (unless all External Identifiers are requested to be deleted from the subscription); in such case, the MME/SGSN shall reject the request and return an error with a Result-Code set to DIAMETER\_UNABLE\_TO\_COMPLY. + +#### 5.2.2.2.3 Detailed behaviour of the HSS + +The HSS shall make use of this procedure to remove deleted subscription data from the MME or SGSN. + +The HSS shall make use of this procedure to remove deleted GPRS Subscription Data from the SGSN or combined MME/SGSN if the GPRS-Subscription-Data-Indicator information has been previously received as set in the ULR-Flags during update location procedure for the MME. + +The HSS shall not set the "Complete APN Configuration Profile Withdrawal" bit in the DSR-Flags AVP when sending a Delete Subscriber Data Request to an MME, since the default APN shall always be present in an MME. + +When receiving a Delete Subscriber Data Answer with "SGSN Area Restricted" the HSS shall set the SGSN area restricted flag as "SGSN area restricted". + +### 5.2.3 Authentication Procedures + +#### 5.2.3.1 Authentication Information Retrieval + +##### 5.2.3.1.1 General + +The Authentication Information Retrieval Procedure shall be used by the MME and by the SGSN to request Authentication Information from the HSS. + +This procedure is mapped to the commands Authentication-Information-Request/Answer (AIR/AIA) in the Diameter application specified in chapter 7. + +Table 5.2.3.1.1/1 specifies the involved information elements for the request. + +Table 5.2.3.1.1/2 specifies the involved information elements for the answer. + +**Table 5.2.3.1.1/1: Authentication Information Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|-----------------------------------------------------------|-------------------------------------------|------|---------------------------------------------------------------------------------------------------------------| +| IMSI | User-Name
(See IETF RFC 6733 [61]) | M | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [3], clause 2.2. | +| Supported Features
(See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Requested E-UTRAN Authentication Info
(See 7.3.11) | Requested-EUTRAN-Authentication-Info | C | This information element shall contain the information related to authentication requests for E-UTRAN. | +| Requested UTRAN/GERAN Authentication Info
(See 7.3.12) | Requested-UTRAN-GERAN Authentication-Info | C | This information element shall contain the information related to authentication requests for UTRAN or GERAN. | +| Visited PLMN ID
(See 7.3.9) | Visited-PLMN-ID | M | This IE shall contain the MCC and the MNC of the visited PLMN, see 3GPP TS 23.003 [3]. | +| AIR Flags
(See 7.3.201) | AIR-Flags | O | This IE, if present, contains a bit mask. See clause 7.3.201 for the meaning of the different bits. | + +**Table 5.2.3.1.1/2: Authentication Information Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|-----------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result
(See 7.4) | Result-Code / Experimental-Result | M | This IE shall contain the result of the operation.
This IE shall contain the Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [61]).
The Experimental-Result AVP shall be used for S6a/S6d errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.
The following errors are applicable in this case:
- User Unknown
- Unknown EPS Subscription
- Authentication Data Unavailable | +| Error-Diagnostic | Error-Diagnostic | O | If the Experimental Result indicated "Unknown EPS Subscription", Error Diagnostic may be present to indicate whether or not GPRS subscription data are subscribed (i.e. whether or not Network Access Mode stored in the HSS indicates that only CS service is allowed). | +| Supported Features
(See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Authentication Info
(See 7.3.17) | Authentication-Info | C | This IE shall contain the Authentication Vectors. | +| UE Usage Type
(See 7.3.202) | UE-Usage-Type | C | This IE shall be present if the HSS supports the Dedicated Core Networks feature, and the "Send UE Usage Type" flag was set in the AIR-Flags AVP in the AIR command, and this information is available in the user subscription.
If present, this IE shall contain the UE Usage Type of the subscriber (see clause 7.3.202). | + +### 5.2.3.1.2 Detailed behaviour of the MME and the SGSN + +The MME or SGSN shall make use of this procedure in order to retrieve the Authentication Vectors from the HSS. + +If the MME or SGSN supports Emergency services for users in limited service state, and the user's IMSI is not available from the UE, or the user's IMSI is marked as unauthenticated, the MME or SGSN shall not make use of the Authentication Information Retrieval procedure. + +If the request is triggered by a synchronization failure during E-UTRAN authentication, the MME or combined MME/SGSN shall include the Re-Synchronization Information in the Requested-EUTRAN-Authentication-Info AVP in the request. + +If the request is triggered by a synchronization failure during UTRAN or GERAN authentication, the SGSN or combined MME/SGSN shall include the Re-Synchronization Information in the Requested-UTRAN-GERAN-Authentication-Info AVP in the request. + +Re-Synchronization Information shall not be present in both the Requested-EUTRAN-Authentication-Info AVP and the Requested-UTRAN-GERAN-Authentication-Info AVP. + +A stand alone MME shall include the Requested-EUTRAN-Authentication-Info AVP and shall not include the Requested-UTRAN-GERAN-Authentication-Info AVP in the request. The Immediate-Response-Preferred AVP should be present if a EUTRAN-Vector is needed for immediate use. + +A stand alone SGSN shall not include the Requested-EUTRAN-Authentication-Info AVP and shall include the Requested-UTRAN-GERAN-Authentication-Info AVP in the request. The Immediate-Response-Preferred AVP should be present if a UTRAN/GERAN-Vector is needed for immediate use. + +A combined MME/SGSN may include both the Requested-EUTRAN-Authentication-Info AVP and the Requested-UTRAN-GERAN-Authentication-Info AVP in the request. If both the Requested-EUTRAN-Authentication-Info AVP and the Requested-UTRAN-GERAN-Authentication-Info AVP are present in the request, the Immediate-Response-Preferred AVP shall be present if the requested authentication vectors are needed for immediate use. The content of the Immediate-Response-Preferred AVP shall correspond to the access type which the UE is currently to be authenticated. The Immediate-Response-Preferred AVP shall not be present in both the Requested-EUTRAN-Authentication-Info AVP and the Requested-UTRAN-GERAN-Authentication-Info AVP. The presence of an Immediate-Response-Preferred AVP shall indicate that a vector is needed for immediate use. + +When EUTRAN-AVs and UTRAN-AVs or GERAN-AVs are requested, presence of Immediate-Response-Preferred AVP within the Requested-EUTRAN-Authentication-Info AVP shall indicate that EUTRAN-AVs are requested for immediate use in the MME/SGSN; presence of Immediate-Response-Preferred AVP within the Requested-UTRAN-GERAN-Authentication-Info AVP shall indicate that UTRAN-AVs or GERAN-AVs are requested for immediate use in the MME/SGSN. It may be used by the HSS to determine the number of vectors to be obtained from the AuC and the number of vectors downloaded to the MME or SGSN. + +If the MME or SGSN supports the Dedicated Core Networks functionality, and the MME or SGSN needs to retrieve the UE Usage Type from the HSS, it shall set the "Send UE Usage Type" flag in the AIR-Flags AVP in the AIR command. + +When receiving an Authentication Information response from the HSS, the MME or SGSN shall check the Result Code. If it indicates success and Authentication Information is present in the result, the MME or SGSN shall use the received vectors. For details see 3GPP TS 33.401 [5]. + +If the MME or SGSN supports Emergency services for users in limited service state, the MME or SGSN shall proceed even if the Authentication Information Retrieval procedure has failed. In this case, the MME or SGSN shall mark the user's IMSI as unauthenticated. + +Vectors with lower Item Number should be used before Vectors with higher Item Number are used in the MME or SGSN. For Vectors received within different requests those received by the earlier request should be used before those received by the later request. + +### 5.2.3.1.3 Detailed behaviour of the HSS + +When receiving an Authentication Information request the HSS shall check whether subscription data exists for the IMSI. + +If the HSS determines that there is not any type of subscription for the IMSI (including EPS, GPRS and CS subscription data), a result code of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned. + +If the Authentication Information Request contains a Requested-EUTRAN-Authentication-Info AVP but no Requested-UTRAN-GERAN-Authentication-Info AVP, and the subscriber has not any APN configuration, the HSS shall return a Result Code of DIAMETER\_ERROR\_UNKNOWN\_EPS\_SUBSCRIPTION. + +If the Authentication Information Request contains a Requested-UTRAN-GERAN-Authentication-Info AVP but no Requested-EUTRAN-Authentication-Info AVP, and the subscriber has neither an APN configuration profile nor GPRS subscription data, the HSS shall return a Result Code of DIAMETER\_ERROR\_UNKNOWN\_EPS\_SUBSCRIPTION. + +If the Authentication Information Request contains both Requested-EUTRAN-Authentication-Info AVP and Requested-UTRAN-GERAN-Authentication-Info AVP, and the Requested-EUTRAN-Authentication-Info AVP does not contain an Immediate-Response-Preferred AVP, and the subscriber has not any APN configuration, the HSS shall not return E-UTRAN vectors. + +If the Authentication Information Request contains both Requested-EUTRAN-Authentication-Info AVP and Requested-UTRAN-GERAN-Authentication-Info AVP, and the Requested-EUTRAN-Authentication-Info AVP contains an Immediate-Response-Preferred AVP, and the subscriber does not have any APN configuration, the HSS shall return a Result Code of DIAMETER\_ERROR\_UNKNOWN\_EPS\_SUBSCRIPTION. + +When sending DIAMETER\_ERROR\_UNKNOWN\_EPS\_SUBSCRIPTION, an Error Diagnostic information may be added to indicate whether or not GPRS subscription data are subscribed (i.e. whether or not Network Access Mode stored in the HSS indicates that only circuit service is allowed). + +If EUTRAN-Authentication-Info is requested, the HSS shall check if serving nodes within the realm identified by the received Origin-Realm AVP are allowed to request authentication information for use in the serving network identified by the received Visited-PLMN-Id AVP. + +The HSS shall then request the AuC to generate the corresponding requested Authentication Vectors (AVs). Subject to load considerations and/or other implementation specific considerations which may be based on the presence of an Immediate-Response-Preferred AVP, less AVs than the requested number of AVs may be generated. + +If EUTRAN-Authentication-Info is requested, when receiving AVs from the AuC, the HSS shall generate the KASME before sending the response to the MME or combined MME-SGSN. + +If the AuC is unable to calculate any corresponding AVs due to unallowed attachment for the UE, e.g. the UE is attaching via E-UTRAN with a SIM card equipped, the HSS shall return an error DIAMETER\_AUTHORIZATION\_REJECTED, the HSS shall not return any AV to the requesting node in the response. Otherwise, if no corresponding pre-computed AV is available, and the AuC is unable to calculate any corresponding AVs due to unknown failures, such as the internal database error, the result code shall be set to DIAMETER\_AUTHENTICATION\_DATA\_UNAVAILABLE. The MME or the SGSN may request authentication vectors again. + +For details see 3GPP TS 33.401 [5]. KASME generation is not performed before sending the response to the SGSN. + +If the Requested-EUTRAN-Authentication-Info AVP is present in the request, the HSS shall download E-UTRAN authentication vectors to the MME. If the Requested-UTRAN-GERAN-Authentication-Info AVP is present in the request, the HSS shall download UTRAN or GERAN authentication vectors to the SGSN. + +If the Immediate Response Preferred parameter has been received, the HSS may use it together with the number of requested vectors and the number of vectors stored in the HSS that are pre-computed to determine the number of vectors to be obtained from the AuC. The HSS may return less number of vectors than requested to the MME or SGSN. If both the Requested-EUTRAN-Authentication-Info AVP and the Requested-UTRAN-GERAN-Authentication-Info AVP are in the request, and one of them includes the Immediate Response Preferred parameter, the HSS may omit the vectors request that are not for immediate use. If both the Requested-EUTRAN-Authentication-Info AVP and the Requested-UTRAN-GERAN-Authentication-Info AVP are in the request, and both of them includes the Immediate Response Preferred parameter, the HSS may return E-UTRAN authentication vectors and UTRAN or GERAN authentication vectors. KASME is always computed for each E-UTRAN vector due to the PLMN-binding before sending the response to the MME independent of the presence of the Immediate Response Preferred parameter. + +If the Re-Synchronization-Info AVP has been received, the HSS shall check the AUTS parameter before sending new authentication vectors to the MME or the SGSN. For details see 3GPP TS 33.102 [18]. If both the Requested-EUTRAN-Authentication-Info AVP and the Requested-UTRAN-GERAN-Authentication-Info AVP are in the request, + +and both of them include the Re-Synchronization-Info AVP, the HSS shall not check the AUTS parameter and return the result code of DIAMETER\_UNABLE\_TO\_COMPLY. Any authentication vectors shall not be sent by the HSS to the requesting node in the response. + +If more than one EPS or UTRAN or GERAN Vector is to be included within one Authentication-Info AVP, the Item-Number AVP shall be present within each Vector. + +If the HSS supports the Dedicated Core Networks functionality, and the MME or SGSN has set the "Send UE Usage Type" flag in the AIR-Flags AVP in the AIR command: + +- if the UE Usage Type value is available in the subscription data of the user: + - if the Immediate Response Preferred parameter is not present in the Requested-EUTRAN-Authentication-Info nor in the Requested-UTRAN-GERAN-Authentication-Info, the HSS may return no authentication vectors in the response; the HSS shall then return the result code DIAMETER\_SUCCESS and may return the generated AVs (if any) to the MME or SGSN; +- the HSS shall include the UE-Usage-Type AVP in the AIA response command if the result code is DIAMETER\_SUCCESS or DIAMETER\_AUTHENTICATION\_DATA\_UNAVAILABLE. +- if the UE Usage Type value is not available in the subscription data of the user, the HSS shall answer as if the MME/SGSN had not requested the UE Usage Type parameter. + +## 5.2.4 Fault Recovery Procedures + +### 5.2.4.1 Reset + +#### 5.2.4.1.1 General + +The Reset Procedure shall be used by the HSS, after a restart, to indicate to the MME and to the SGSN that a failure has occurred. + +The Reset Procedure may also be used by the HSS as part of operation and maintenance actions e.g. to allow planned HSS outage without service interruption, or to update subscription data shared by multiple subscribers. + +This procedure is mapped to the commands Reset-Request/Answer (RSR/RSA) in the Diameter application specified in chapter 7. + +Table 5.2.4.1.1/1 specifies the involved information elements for the request. + +Table 5.2.4.1.1/2 specifies the involved information elements for the answer. + +**Table 5.2.4.1.1/1: Reset Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|----------------------------|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| User Id List
(See 7.3.50) | User-Id | O | This IE shall contain a list of User-Ids where a User-Id comprises the leading digits of an IMSI (i.e. MCC, MNC, leading digits of MSIN) and it shall identify the set of subscribers whose IMSIs begin with the User-Id. The HSS may include this information element if the occurred failure is limited to subscribers identified by one or more User-Ids. | +| Supported Features
(See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Reset-IDs
(See 7.3.184) | Reset-ID | O | If present, this information element identifies the set of impacted subscribers. | +| Subscription Data
(See 7.3.2) | Subscription-Data | O | If the Reset Procedure is used to add/ modify subscription data shared by multiple subscribers, this Information Element shall contain the part of the subscription profile that either is to be added to the subscription profile stored in the MME or SGSN or combined MME/SGSN or is replacing a part of the subscription profiles of the impacted subscribers stored in the MME or SGSN.
Shall be absent if Subscription-Data-Deletion AVP is present.
Shall be absent if Reset-ID AVP is absent | +| Subscription Data Deletion
(See 7.3.208) | Subscription-Data-Deletion | O | If the Reset Procedure is used to delete subscription data shared by multiple subscribers, this Information Element shall contain identifications of the part of the subscription profile that is to be deleted from the subscription profiles of the impacted subscribers stored in the MME or SGSN or combined MME/SGSN.
Shall be absent if Subscription-Data AVP is present.
Shall be absent if Reset-ID AVP is absent | + +**Table 5.2.4.1.1/2: Reset Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|-----------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported Features
(See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Result
(See 7.4) | Result-Code / Experimental-Result | M | This IE shall contain the result of the operation.
The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [61]).
The Experimental-Result AVP shall be used for S6a/S6d errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.
There are no Experimental-Result codes applicable for this command. | + +#### 5.2.4.1.2 Detailed behaviour of the MME and the SGSN + +When receiving a Reset message neither containing Subscription-Data nor Subscription-Data-Deletion the MME or SGSN or combined MME/SGSN shall mark all impacted subscriber records "Location Information Confirmed in HSS " as "Not Confirmed". + +When receiving a Reset message containing Subscription-Data or Subscription-Data-Deletion the MME or SGSN or combined MME/SGSN shall update all impacted subscriber records accordingly, i.e. each impacted subscriber record is updated as if an individual IDR or DSR for that subscriber was received; for details see clauses 5.2.2.1.2 and 5.2.2.2.2. The MME or SGSN or combined MME/SGSN shall not mark successfully updated subscriber records "Location Information Confirmed in HSS " as "Not Confirmed". If an impacted subscriber record cannot be updated for any reason (e.g. the updated data is considered not shareable by the MME or SGSN or combined MME/SGSN, or the update requires an individual acknowledgement to be sent to the HSS), the MME or SGSN or combined MME/SGSN shall mark that record "Location Information Confirmed in HSS " as "Not Confirmed". + +NOTE: Which subscription data are considered by the MME or SGSN or combined MME/SGSN not shareable by multiple subscribers is implementation specific. + +If the update of shared subscription data requires only local updates in the MME or SGSN or combined MME/SGSN (i.e., the update of the profile does not imply to initiate any signalling interaction towards other network nodes), the updates should be performed immediately (e.g. deleting an Operator Determined Barring). + +If the update of shared subscription data implies initiating a signalling interaction towards other nodes (e.g. towards the PGW/PCRF for the change of an APN configuration parameter, such as APN-AMBR), depending on the UE's state the following shall apply: + +- If the UE is in CONNECTED state, the updates shall be performed immediately including signalling towards other nodes. +- If the UE is in IDLE state, the signalling towards other nodes should be deferred to the next authenticated radio contact with that UE. + +NOTE: The rational for the recommendation to defer signalling towards other nodes until the next authenticated radio contact is to consider impacts to the network only when the updates are required, and to spread the signalling towards other nodes over some time, based on user's activity. + +In both cases, to avoid high processing/signalling load resulting from shared subscription data update, processing/signalling actions resulting from data updates in the MME or SGSN or combined MME/SGSN may take a maximum operator configuration-depending time. + +If the Reset-IDs IE is supported and received, the MME or SGSN or combined MME/SGSN shall make use of the Reset-IDs (together with the HSS's realm) in order to determine which subscriber records are impacted (i.e. check whether at least one received Reset-ID is associated with the subscriber); otherwise the MME or SGSN or combined MME/SGSN shall make use of the HSS Identity received in the Origin-Host AVP (by comparing it with the value stored after successful ULA) and may make use of the received User-Id-List (if any) in order to determine which subscriber records are impacted. + +At the next authenticated radio contact with the UE concerned, if the subscriber record "Location Information Confirmed in HSS" is marked as "Not Confirmed", the restoration procedure shall be triggered. + +See also 3GPP TS 29.118 [46] clause 5.9.2. + +#### 5.2.4.1.3 Detailed behaviour of the HSS + +The HSS shall make use of this procedure in order to indicate to all relevant MMEs, SGSN, and combined MME/SGSNs that the HSS has restarted and may have lost the current MME-Identity and SGSN-Identity of some of its subscribers who may be currently roaming in the MME area and/or SGSN area, and that the HSS, therefore, cannot send a Cancel Location messages or Insert Subscriber Data messages when needed. + +The HSS may make use of this procedure in order to indicate to all relevant MMEs, SGSN, and combined MME/SGSNs that the HSS has updated subscription data shared by some of its subscribers who may be currently roaming in the MME area and/or SGSN area. + +If the Reset-ID feature is not supported by the MME/SGSN and HSS, the HSS optionally may include a list of Ids identifying a subset of subscribers served by the HSS, if the occurred failure is limited to those subscribers. + +If the Reset-ID feature is supported by the MME or SGSN, the HSS optionally may include one (or several) Reset-ID AVPs identifying e.g. failed hardware components if the occurred failure is limited to those subscribers associated with e.g. the identified failed hardware components. + +The HSS should invoke this procedure towards a combined MME/SGSN only for a single time even if some of the impacted subscribers are attached to the combined MME/SGSN via UTRAN/GERAN and some of the impacted subscribers are attached to the combined MME/SGSN via E-UTRAN. + +## 5.2.5 Notification Procedures + +### 5.2.5.1 Notification + +#### 5.2.5.1.1 General + +The Notification Procedure shall be used between the MME and the HSS and between the SGSN and the HSS when an inter MME or SGSN location update does not occur but the HSS needs to be notified about + +- an update of terminal information; +- an update of the UE SRVCC capability (only if the MME/SGSN supports SRVCC). + +The Notification Procedure shall also be used between the MME and the HSS and between the SGSN and the HSS if the HSS needs to be notified about: + +- an assignment/change of a dynamically allocated PDN GW for an APN, if such a notification is needed taking into account the access restrictions and the type of PDN; + +NOTE: If the PDN is of type "non-IP", the APN is not accessible via non-3GPP access and therefore the PDN-GW ID does not need to be conveyed across accesses. + +- an assignment/change of a dynamically allocated PDN GW for the establishment of emergency PDN connections, if such notification is needed for a non roaming authenticated user, based on operator policy (e.g. on whether the operator uses static PDN GW or not for emergency services) taking into account the access restrictions and feature support; +- the failed monitoring event configurations at the MME or SGSN (if received in ULA) or the status of the monitoring event configurations at the IWK-SCEF; +- the deletion of a monitoring event configuration in SCEF for a UE (i.e. due to an SCEF restart, see 3GPP TS 23.007 [43]). + +The Notification Procedure shall be used between the MME and the HSS when an inter MME location update does not occur but the HSS needs to be notified about + +- the need to send a Cancel Location to the current SGSN. + +The Notification Procedure shall be used between the MME and the HSS when the "SMS in MME" feature is applied and between the SGSN and the HSS when an earlier short message delivery failed and the HSS needs to be notified about: + +- the UE is reachable or the UE has memory capacity available to receive one or more short messages. + +The Notification Procedure shall be used between the MME and the HSS and between the SGSN and the HSS when the HSS has requested to be notified about: + +- the UE is reachable. + +The Notification Procedure shall be used between the MME and the HSS and between the SGSN and the HSS to notify the HSS about: + +- an update of the Homogeneous Support of IMS Voice Over PS Sessions. + +The Notification Procedure shall be used between the MME and the HSS to notify the HSS about: + +- removal of MME registration for SMS. + +This procedure is mapped to the commands Notify-Request/Answer (NOR/NOA) in the Diameter application specified in chapter 7. + +Table 5.2.5.1.1/1 specifies the involved information elements for the request. + +Table 5.2.5.1.1/2 specifies the involved information elements for the answer. + +**Table 5.2.5.1.1/1: Notify Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|-----------------------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | User-Name
(See IETF RFC 6733 [61]) | M | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [3], clause 2.2. | +| Supported Features
(See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Terminal Information
(See 7.3.3) | Terminal-Information | C | This information element shall contain information about the user's mobile equipment.
When notifying the HSS about any change of Terminal Information, the MME or SGSN shall include the new Terminal Information in the request.
Within this Information Element, only the IMEI and the Software-Version AVPs shall be used on the S6a/S6d interface. | +| PDN GW Identity
(See 7.3.45) | MIP6-Agent-Info | C | This IE shall contain the identity of the selected and dynamically allocated PDN GW for an APN. It shall be present if a new PDN-GW has been selected and the subscriber is allowed handover to non 3GPP access. When notifying the HSS about a newly selected PDN GW, the MME or SGSN shall include the PDN-GW-Identity in the request.
For establishment of emergency PDN connections, this IE shall contain the identity of the PDN-GW used to establish those PDN connections. | +| PGW PLMN ID | Visited-Network-Identifier | C | This IE identifies the PLMN in which the PDN GW is located. It shall be present when the PDN GW Identity is present and does not contain an FQDN. | +| Context Identifier
(See 7.3.27) | Context-Identifier | O | This parameter shall identify the APN Configuration with which the selected PDN GW shall be correlated.
It may be present if it is available and the PDN-GW is present and is particular for one specific APN and not common to all the APNs.
For the compatibility with the MAP protocol as defined in the 3GPP TS 29.002 [24], this parameter shall not have a value of zero. | +| APN
(See TS 23.008 [30]) | Service-Selection
(See IETF RFC 5778 [20]) | C | This IE shall contain the APN for the selected and dynamically allocated PDN GW.
For establishment of non-emergency PDN connections, it shall be present if the selected PDN-GW is present and is particular for one specific APN and not common to all the APNs.
For establishment of emergency PDN connections (i.e., the Emergency-Services AVP is present, with the Emergency-Indication flag set), this AVP shall be left absent. | +| Alert Reason
(See 7.3.83) | Alert-Reason | C | This parameter shall indicate if the mobile subscriber is present or the MS has memory available.
It shall be present when notifying the HSS about the presence of the UE or the UE has memory capacity available to receive one or more short messages. | +| UE SRVCC Capability | UE-SRVCC-Capability | C | This information element shall indicate if the UE supports or does not support the SRVCC capability.
If the MME/SGSN supports SRVCC and the UE SRVCC Capability has changed, the MME or SGSN shall include the new UE SRVCC Capability in the request. | +| NOR Flags
(See 7.3.49) | NOR-Flags | C | This Information Element shall contain a bit mask. See 7.3.49 for the meaning of the bits. Absence of this information element shall be interpreted as all bits set to 0.
When notifying the HSS about the need to send cancel location to the current SGSN, the MME shall set the "Single-Registration-Indication" flag in the NOR-Flags.
When notifying the HSS about the "restricted" status of the current SGSN area, the SGSN shall set the "SGSN area restricted" flag in the NOR-Flags.
When notifying the HSS about the reachability of the UE or the UE has memory capacity available to receive one or more short messages, the MME, if the "SMS in MME" feature is applied, or SGSN shall set the "Ready for SM" flag correspondingly in the NOR-Flags.
When notifying the HSS that the UE is reachable, the MME or SGSN shall | + +| | | | | +|-----------------------------------------------------------------|----------------------------------------------------|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | | set the "UE Reachable" flag correspondingly in the NOR-Flags.
When notifying the HSS about update of the Homogeneous Support of IMS Voice Over PS Sessions, the MME or the SGSN shall set the "Homogeneous Support of IMS Voice Over PS Sessions" flag and S6a/S6d-Indicator flag for a combined MME/SGSN correspondingly in the NOR-Flags.
When notifying the HSS about removal of MME registration for SMS, the MME shall set the "Removal of MME Registration for SMS" flag correspondingly in the NOR-Flags. | +| Homogeneous Support of IMS Voice Over PS Sessions (See 7.3.107) | Homogeneous -Support-of-IMS-Voice-Over-PS-Sessions | C | This Information Element shall be present if Homogeneous Support of IMS Voice Over PS Sessions is modified to one of the values "SUPPORTED" or "NOT_SUPPORTED".
The value "SUPPORTED" indicates that there is support for "IMS Voice over PS Sessions" in all TAs or RAs.
The value "NOT_SUPPORTED" indicates that there is not support for "IMS Voice over PS Sessions" in any of the TAs or RAs. | +| Maximum UE Availability Time | Maximum-UE-Availability-Time | O | This information element may be included when notifying the HSS that the UE is reachable. When present, it shall indicate the timestamp (in UTC) until which a UE using a power saving mechanism (such as extended idle mode DRX) is expected to be reachable for SM Delivery.
This information may be used by the SMS Center to prioritize the retransmission of Short Message to UEs using a power saving mechanism. | +| Monitoring Event Config Status | Monitoring-Event-Config-Status | C | This information element shall be present if the MME/SGSN sends the Notify Request after receiving the Configuration-Information-Answer from the IWK-SCEF. This information element shall only contain the monitoring event configuration status of those events whose configuration status has changed since the last status informed to the HSS.
This information element shall also be present if any of the monitoring events configurations received in ULA failed and shall only contain the monitoring event configuration status of those events whose detection could not be started at the MME/SGSN.
This information element shall also be present if the MME or SGSN determines that a Monitoring Event Configuration for a UE is to be deleted in the HSS (i.e. SCEF responds to a Monitoring Event Report with DIAMETER_ERROR_SCEF_REFERENCE_ID_UNKNOWN). | +| Emergency Services (See 3GPP TS 29.273 [59]) | Emergency-Services | C | The MME shall include this information element, and set the Emergency-Indication flag, to notify the HSS that a new PDN-GW has been selected for the establishment of an emergency PDN connection, whose identity is conveyed in the "PDN GW Identity" IE. | + +Table 5.2.5.1.1/2: Notify Answer + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|-----------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result (See 7.4) | Result-Code / Experimental-Result | M | This IE shall contain the result of the operation.
The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [61]).
The Experimental-Result AVP shall be used for S6a/S6d errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.
The following errors are applicable in this case:
- User Unknown | +| Supported Features (See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +#### 5.2.5.1.2 Detailed behaviour of the MME and the SGSN + +If the MME or SGSN supports Emergency services, the MME or SGSN shall not make use of the Notification procedure for emergency attached unauthenticated UEs; for authenticated UEs, the MME shall make use of the Notification procedure to inform the HSS about the PDN-GW selected to establish emergency PDN connections, if the MME is configured to use a dynamic PGW for emergency services for such UEs. + +The MME or SGSN shall not make use of the Notification procedure to inform the HSS about the identity of the dynamically selected PDN-GW, if the access restrictions indicate that the user is not allowed to get service via non-3GPP access, or the PDN type of the APN is of type "non-IP". + +The MME or SGSN shall include conditional AVPs in NOR according to the description given in table 5.2.5.1.1/1. + +If the MME sends a Notify Request to inform the HSS that the UE has become reachable again, the MME shall clear the corresponding URRP-MME for the UE. + +If the SGSN sends a Notify Request to inform the HSS that the UE has become reachable again, the SGSN shall clear the corresponding URRP-SGSN for the UE. + +If the MME sends a Notify Request to inform the HSS about the presence of the UE to receive one or more short messages, the MME shall clear the corresponding MNRF for the UE. + +If the SGSN sends a Notify Request to inform the HSS about the presence of the UE to receive one or more short messages, the SGSN shall clear the corresponding MNRG for the UE. + +If the MME or SGSN determines that it needs to update the Homogeneous Support of IMS Voice Over PS Sessions in the HSS, the MME or SGSN shall send a Notify Request with the "Homogeneous Support of IMS Voice Over PS Sessions" bit set in the NOR-Flags AVP; if there is homogeneous support, or homogeneous non-support, of IMS Voice Over PS Sessions, the MME or SGSN shall report it by including the updated Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions AVP; if the support is not homogeneous, the MME or SGSN shall report it by leaving such AVP absent in the Notify Request to the HSS. MME or SGSN shall ensure the status of Homogeneous Support of IMS Voice Sessions in HSS does not contradict with the value of "IMS voice over PS session indicator" provided to UE over NAS as specified in 3GPP TS 24.008 [31] and 3GPP TS 24.301 [64]; + +if "IMS voice over PS session indicator" sent to UE has changed from "not supported" to "supported" when status Homogenous Support of IMS Voice in HSS is "not supported", MME or SGSN shall immediately send Notify Request indicating as either homogenous support or not homogenous; + +if "IMS voice over PS session indicator" sent to UE has changed from "supported" to "not supported" when status Homogenous Support of IMS Voice in HSS is "supported", MME or SGSN shall immediately send Notify Request indicating as either homogenous non-support or not homogenous. + +If the MME needs to indicate to the HSS that it is no longer registered for SMS in the HSS, the MME shall send a Notify Request with "Removal of MME Registration for SMS" flag set in the NOR-Flags AVP. + +When receiving a Notify response from the HSS, if the result code indicates + +DIAMETER\_ERROR\_UNKNOWN\_SERVING\_NODE, the MME or SGSN shall consider the Notification procedure as failed, and it shall mark the subscriber record as "Subscriber to be restored in HSS". + +When receiving a Notify response from the HSS, if the result code indicates + +DIAMETER\_ERROR\_USER\_UNKNOWN, the MME or SGSN shall detach the subscriber and remove the subscriber from its database. + +If the MME/SGSN has received the monitoring event configurations in an ULA command and one, several or all event detections fail to be started (e.g due to maximum resources exceeded), the MME/SGSN shall send the Notify Request command with the Monitoring-Event-Config-Status AVP for the failed monitoring event configurations. + +If the MME or SGSN receives a failure response, e.g. DIAMETER\_UNABLE\_TO\_COMPLY, corresponding to a Notify Request to notify the HSS about the selected PDN-GW, the MME or SGSN shall not trigger a detach for the subscriber based only on this failure. + +NOTE 1: A failure to indicate the selected PDN-GW to the HSS does not impact connectivity provided via 3GPP access. + +When the MME/SGSN has received the Configuration-Information-Answer from the IWK-SCEF during the monitoring event configuration procedure, the MME/SGSN shall send the Notify Request command with the Monitoring-Event-Config-Status AVP as received from the IWK-SCEF in the Configuration-Information-Answer, for the monitoring + +event configurations whose status have changed (due to authorization performed by the IWK-SCEF) since last informed to the HSS. + +NOTE 2: If the Monitoring-Event-Configuration was received at the MME/SGSN in the ULA command, then the HSS is not yet informed of any status of the monitoring event configuration. In this case, the entire Monitoring-Event-Config-Status as received from IWK-SCEF has to be transferred to the HSS through a Notify Request Command. + +If the MME or SGSN determines that a Monitoring Event Configuration for a UE is to be deleted in the HSS (i.e. SCEF responds to a Monitoring Event Report with DIAMETER\_ERROR\_SCEF\_REFERENCE\_ID\_UNKNOWN), the MME or SGSN shall send a Notify Request with the Monitoring-Event-Config-Status AVP. The Monitoring-Event-Config-Status AVP shall include the error as received from SCEF. + +#### 5.2.5.1.3 Detailed behaviour of the HSS + +When receiving a Notify request the HSS shall check whether the IMSI is known. + +If it is not known, a result code of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned. + +If the IMSI is known, and the source MME or SGSN originating the Notify message is not currently registered in HSS for that UE, a result code of DIAMETER\_ERROR\_UNKNOWN\_SERVING\_NODE shall be returned. + +If the IMSI is known, and the source MME or SGSN is currently registered in HSS, the HSS shall set the result code to DIAMETER\_SUCCESS, unless otherwise stated, and + +- store the new terminal information if present in the request; +- store the new UE SRVCC capability if present in the request; +- store the new PDN GW and PLMN ID for an APN if present in the request and the APN is present in the subscription and if PDN GW is dynamically allocated; otherwise the HSS shall not store the new PDN GW data and shall set the result code to DIAMETER\_UNABLE\_TO\_COMPLY; +- store the new PDN GW and PLMN ID, and the APN itself, if both are present in the request, and the APN is not present in the subscription but a wild card APN is present in the subscription; +- if the Emergency Services IE is present, with the Emergency-Indication flag set, store the new PDN GW, as the PDN GW used to establish emergency PDN connections; the HSS shall store this information not bound to any specific APN; +- mark the location area as "restricted" if so indicated in the request; +- send Cancel Location to the current SGSN if so indicated in the request; +- if the UE has become reachable again, and NOR is received on S6a from an MME or on S6d from an SGSN, the HSS shall respectively clear the URRP-MME or the URPP-SGSN parameter for the UE and send an indication to the Service Related Entities if there is any; +- when NOR is received on S6d from an SGSN (with the Alert Reason present), the HSS shall reset the MNRG flag and send a MAP-Alert-Service-Centre message or S6c-Alert-Service-Centre-Request (see 3GPP TS 29.338 [48], i.e. the behaviour in the HSS should be the same as when a MAP-Ready for SM is received from an SGSN; +- when NOR is received on S6a from an MME (with the Alert Reason present), the HSS shall reset the MNRF flag and send a MAP-Alert-Service-Centre message or S6c-Alert-Service-Centre-Request (see 3GPP TS 29.338 [48], i.e. the behaviour in the HSS should be the same as when a MAP-Ready for SM is received from a VLR/MSC; +- when NOR is received on S6a from an MME or on S6d from an SGSN to update the Homogeneous Support of IMS Voice Over PS Sessions, the HSS shall store the updated Homogeneous Support of IMS Voice Over PS Sessions and may use this information in the future in order to skip the T-ADS data retrieval, as described in clause 5.2.2.1 (IDR/IDA commands). If the "Homogeneous Support of IMS Voice Over PS Sessions" bit is set in the NOR-Flags AVP received but without Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions AVP present in the NOR message, the HSS shall take the Homogeneous Support of IMS Voice Over PS Sessions as unknown to the serving node. If the "Homogeneous Support of IMS Voice Over PS Sessions" bit is not set in the NOR-Flags AVP, the HSS shall ignore (if present) the Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions AVP; + +- when NOR is received on S6a from an MME for removal of MME registration for SMS, the HSS shall remove the MME registration for SMS and the "MME number for SMS" as the corresponding MSC number to be used for MT SMS. +- when NOR is received on S6a from an MME or on S6d from an SGSN with the Monitoring-Event-Config-Status AVP, the HSS shall either trigger a Monitoring event cancelation procedure for the monitoring events that were not successfully authorized at the MME/SGSN by the IWK-SCEF or a Monitoring event suspension procedure for the monitoring events that were not successfully configured at the MME/SGSN, as specified in clause 7.2.2.2 of 3GPP TS 29.336 [54]. The HSS shall trigger a Monitoring event cancelation or suspension procedure based on the result code as indicated by MME/SGSN (e.g. DIAMETER\_ERROR\_UNAUTHORIZED\_REQUESTING\_ENTITY (5510) returned by IWK-SCEF triggers a Monitoring event cancelation procedure in HSS). +- when NOR is received on S6a from an MME or on S6d from an SGSN with an indication of the deletion of a monitoring event configuration in SCEF (DIAMETER\_ERROR\_SCEF\_REFERENCE\_ID\_UNKNOWN in the Monitoring-Event-Config-Status AVP), the HSS shall locally delete the corresponding Monitoring Event Configuration and shall not trigger a Monitoring event cancelation procedure. + +and then send the response to the MME or SGSN. + +--- + +## 5A MME – CSS (S7a) and SGSN – CSS (S7d) + +### 5A.1 Introduction + +The S7a interface enables the transfer of subscriber related CSG data in the VPLMN between the MME and the CSS as described in 3GPP TS 23.401 [2]. + +The S7d interface enables the transfer of subscriber related CSG data in the VPLMN between the SGSN and the CSS as described in 3GPP TS 23.060 [12]. + +### 5A.2 Mobility Services + +#### 5A.2.1 Location Management Procedures + +##### 5A.2.1.1 Update VCSG Location + +###### 5A.2.1.1.1 General + +The Update VCSG Location Procedure shall be used between the MME and the CSS or between the SGSN and the CSS to update location information in the CSS or retrieve the CSG subscription data of the UE from the CSS. The procedure allows: + +- to inform the CSS about the identity of the MME or SGSN currently serving the user, +- to update MME or SGSN with user CSG subscription data received from the CSS. + +This procedure is mapped to the commands Update-VCSG-Location-Request/Answer (UVR/UVA) in the Diameter application specified in chapter 7. + +Table 5A.2.1.1.1/1 specifies the involved information elements for the request. + +Table 5A.2.1.1.1/2 specifies the involved information elements for the answer. + +**Table 5A.2.1.1.1/1: Update VCSG Location Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|---------------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | User-Name
(See IETF RFC 6733 [61]) | M | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [3], clause 2.2. | +| Supported Features
(See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| MSISDN | MSISDN | C | This information element shall contain the user MSISDN, formatted according to 3GPP TS 29.329 [25]. It shall be present if available. | +| UVR Flags
(See 7.3.153) | UVR-Flags | M | This Information Element contains a bit mask. See 7.3.153 for the meaning of the bits. | +| SGSN number
(See 7.3.102) | SGSN-Number | C | This Information Element contains the ISDN number of the SGSN, see 3GPP TS 23.003 [3].
It shall be present when the message is sent on the S7d interface.
It may be present when the message on the S7a interface and the requesting node is a combined MME/SGSN. | + +**Table 5A.2.1.1.1/2: Update VCSG Location Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|-----------------------------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported Features
(See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Result
(See 7.4) | Result-Code / Experimental-Result | M | This IE shall contain the result of the operation.
The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [61]).
The Experimental-Result AVP shall be used for S7a/S7d errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.
The following errors are applicable:
- User Unknown | +| VPLMN CSG Subscription Data
(See 7.3.155) | VPLMN-CSG-Subscription-Data | C | This Information Element shall contain the list of CSG Ids and the associated expiry dates stored in the CSS. It shall be present if success is reported, unless an explicit "skip subscriber data" indication was present in the request or the Temporary Empty VPLMN CSG Subscription Data flag is set. | +| UVA Flags
(See 7.3.154) | UVA-Flags | C | This Information Element contains a bit mask. See 7.3.154 for the meaning of the bits. | + +#### 5A.2.1.1.2 Detailed behaviour of the MME and the SGSN + +The MME or SGSN shall make use of this procedure to register the UE in the CSS and to retrieve the "CSG subscription data from CSS" when: + +- the VPLMN supports Autonomous CSG Roaming +- and the HPLMN has enabled Autonomous CSG Roaming in the VPLMN +- and the UE has requested an initial attach or a tracking area procedure or a routing area procedure to a CSG cell +- and the MME or SGSN have not yet registered the UE in the CSS. + +If the Autonomous CSG Roaming in the VPLMN is not supported or is not allowed by the HPLMN of the subscriber, the MME or SGSN shall not make use of the Update CSG Location procedure. + +For UEs receiving emergency services, in which the UE was not successfully authenticated, the MME or SGSN shall not make use of the Update VCSG Location procedure. + +A combined MME/SGSN shall set the "Skip Subscriber Data" flag in the UVR-Flags if the "CSG subscription data from CSS" are already available due to a previously VCSG Location updating. + +A combined MME/SGSN that has chosen the option to include the SGSN Number within an Update VCSG Request sent over S7a shall be prepared to receive a single CSG subscription data update message from the CSS when the CSG subscription data is modified in the CSS. + +When receiving an Update VCSG Location Answer from the CSS, the MME or SGSN shall check the result code. If it indicates success the MME or SGSN shall delete all the stored "CSG subscription data from CSS" (if any) and then store the received "CSG subscription data from the CSS" (if any), and it shall store the CSS identity as received in the Origin-Host AVP. + +If the same CSG Id exists in both "CSG subscription data from CSS" and "CSG subscription data from HSS", the "CSG subscription data from HSS" shall take precedence over the "CSG subscription data from CSS" in further use. + +If an error response is received from the CSS, the MME or SGSN shall not reject the UE and shall end the procedure when the UE is attaching to a normal cell. If the UE is attaching to a CSG cell, in this case the MME or SGSN shall check if there is such CSG Id from the HSS. If there is no such CSG Id, the MME or SGSN shall reject the UE. + +#### 5A.2.1.1.3 Detailed behaviour of the CSS + +When receiving an Update VCSG Location request the CSS shall check whether the user is known. + +If the user is not known, and if the Update VCSG Location Request is received over the S7a/S7d interface, the CSS may: + +- store the MME or SGSN identity received within the Origin-Host AVP, and include the UVA-Flags AVP with "Temporary Empty VPLMN CSG Subscription Data" flag set, and return a Result Code of DIAMETER\_SUCCESS, or +- return a Result Code of DIAMETER\_ERROR\_USER\_UNKNOWN. + +NOTE: A mechanism is needed in the CSS to associate the CSG subscription data of the user with the received IMSI. + +If the Update VCSG Location Request is received over the S7a/S7d interface, the CSS shall replace the stored MME or SGSN identity with the received value (the identity is received within the Origin-Host AVP). + +If no result code indicating an error is sent to the MME or SGSN, the CSS shall include the VPLMN CSG subscription data in the Update VCSG Location Answer unless an explicit "skip subscriber data" indication has been received in the request, and shall return a Result Code of DIAMETER\_SUCCESS. + +#### 5A.2.1.2 Cancel VCSG Location + +##### 5A.2.1.2.1 General + +The Cancel VCSG Location Procedure shall be used between the CSS and the MME and between the CSS and the SGSN. The procedure shall be invoked by the CSS and is used: + +- to inform the MME or SGSN about the subscriber's VCSG subscription withdrawal by the CSS operator and the removal of their registration in the CSS. + +This procedure is mapped to the commands Cancel-VCSG-Location-Request/Answer (CVR/CVA) in the Diameter application specified in chapter 7. + +Table 5A.2.1.2.1/1 specifies the involved information elements for the request. + +Table 5A.2.1.2.1/2 specifies the involved information elements for the answer. + +**Table 5A.2.1.2.1/1: Cancel VCSG Location Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|---------------------------------------|------|--------------------------------------------------------------------------------------------------------------| +| IMSI | User-Name
(See IETF RFC 6733 [61]) | M | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [3], clause 2.2. | +| Supported Features
(See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Cancellation Type
(See 7.3.24) | Cancellation-Type | M | Defined values that can be used are:
- Subscription Withdrawal, applied to the VPLMN CSG subscription. | + +**Table 5A.2.1.2.1/2: Cancel VCSG Location Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|-----------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported Features
(See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Result
(See 7.4) | Result-Code / Experimental-Result | M | The result of the operation.
The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [61]). | + +### 5A.2.1.2.2 Detailed behaviour of the MME and the SGSN + +When receiving a Cancel VCSG Location request the MME or SGSN shall check whether the IMSI is known. + +If it is not known, a result code of DIAMETER\_SUCCESS is returned. + +If it is known, the MME or SGSN shall check if the Cancellation Type is Subscription Withdrawal. In this case, the MME or SGSN shall remove the information of their registration in the CSS and the stored VPLMN CSG subscription if any. Also in this case a result code of DIAMETER\_SUCCESS is returned. + +When a UE is served by a single combined MME/SGSN for both E-UTRAN and non-E-UTRAN access, the combined MME/SGSN shall check if the Cancellation Type is Subscription Withdrawal. In this case, the Cancel VCSG Location request is processed both in the MME part and in the SGSN part of the combined node. + +### 5A.2.1.2.3 Detailed behaviour of the CSS + +The CSS shall make use of this procedure when the user's VPLMN CSG subscription is withdrawn by the CSS operator and shall include a cancellation type of "Subscription Withdrawal". + +## 5A.2.2 Subscriber Data Handling Procedures + +### 5A.2.2.1 Insert VCSG Subscriber Data + +#### 5A.2.2.1.1 General + +The Insert VCSG Subscriber Data Procedure shall be used between the CSS and the MME and between the CSS and the SGSN for updating CSG subscription data in the MME or SGSN in the following situations: + +- due to administrative changes of the user data in the CSS and the user is now located in an MME or SGSN, i.e. if the user was given a CSG subscription and the CSG subscription has changed; + +If the CSS knows that the UE has attached to the same combined MME/SGSN via both the E-UTRAN and UTRAN/GERAN, i.e. the CSS has received the Update VCSG Location Request over both the S7a interface and S7d interface respectively with the same SGSN number, the CSS should invoke this procedure for a single time to update CSG subscription data in the combined MME/SGSN, i.e. the CSS should not invoke this procedure for each of the MME and the SGSN registered respectively. + +This procedure is mapped to the commands Insert-Subscriber Data-Request/Answer (IDR/IDA) in the Diameter application specified in clause 7. + +Table 5A.2.2.1.1/1 specifies the involved information elements for the request. + +Table 5A.2.2.1.1/2 specifies the involved information elements for the answer. + +**Table 5A.2.2.1.1/1: Insert VCSG Subscriber Data Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|------------------------------------|------|---------------------------------------------------------------------------------------------------------------------| +| IMSI | User-Name (See IETF RFC 6733 [61]) | M | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [3], clause 2.2. | +| Supported Features (See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| VPLMN CSG Subscription Data (See 7.3.2) | VPLMN-CSG-Subscription-Data | M | This Information Element shall contain the list of CSG Ids and the associated expiry dates stored in the VPLMN CSS. | + +**Table 5A.2.2.1.1/2: Insert VCSG Subscriber Data Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|---------------------------------------------|-----------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported Features (See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Result (See 7.4) | Result-Code / Experimental-Result | M | This IE shall contain the result of the operation. Result-Code AVP shall be used to indicate success / errors defined in the Diameter base protocol (see IETF RFC 6733 [61]). The Experimental-Result AVP shall be used for S7a/S7d errors. This is a grouped AVP which shall contain the 3GPP Vendor Id in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. The following errors are applicable in this case:
- User Unknown. | + +#### 5A.2.2.1.2 Detailed behaviour of the MME and the SGSN + +When receiving an Insert VCSG Subscriber Data request, the MME or SGSN shall check whether the IMSI is known. + +If it is not known, a result code of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned. + +If the request does not contain any CSG-Subscription-Data AVP, Experimental-Result shall be set to DIAMETER\_ERROR\_SUBS\_DATA\_ABSENT. + +If the request contains at least one CSG-Subscription-Data AVPs, the MME or SGSN shall delete all the stored "CSG subscription data from CSS" (if any), and then store the received "CSG subscription data from CSS". + +If the MME or SGSN cannot fulfil the received request, e.g. due to a database error, it shall set the Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. + +If the same CSG Id exists in both "CSG subscription data from CSS" and "CSG subscription data from HSS", the "CSG subscription data from HSS" shall take precedence over the "CSG subscription data from CSS" in further use. + +#### 5A.2.2.1.3 Detailed behaviour of CSS + +The CSS shall make use of this procedure to delete the "CSG subscription data from CSS" stored in the MME or SGSN and replace them with the CSG subscription data sent. + +If the CSS receives a Insert VCSG Subscriber Data answer with the Result Code DIAMETER\_ERROR\_USER\_UNKNOWN, the CSS shall clear the stored MME or SGSN identity. + +#### 5A.2.2.2 Delete VCSG Subscriber Data + +##### 5A.2.2.2.1 General + +This procedure shall be used between the CSS and the MME or between the CSS and the SGSN, to remove all the "CSG subscription data from CSS" stored in the MME or SGSN. The procedure shall be invoked by the CSS. + +If the CSS knows that the UE has attached to the same combined MME/SGSN via both E-UTRAN and UTRAN/GERAN, i.e. the CSS has received the Update VCSG Location Request over both the S7a interface and S7d interface respectively with the same SGSN number, the CSS should invoke this procedure for a single time to remove all the "CSG subscription data from CSS" stored in the combined MME/SGSN, i.e. not invoke this procedure for each of the MME and the SGSN registered respectively. + +This procedure is mapped to the commands Delete-Subscriber-Data-Request/Answer (DSR/DSA) in the S7a/S7d Diameter application specified in clause 7. + +Table 5A.2.2.2.1/1 specifies the involved information elements for the request. + +Table 5A.2.2.2.1/2 specifies the involved information elements for the answer. + +**Table 5A.2.2.2.1/1: Delete VCSG Subscriber Data Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|---------------------------------------|------|--------------------------------------------------------------------------------------------------------------| +| IMSI | User-Name
(See IETF RFC 6733 [61]) | M | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [3], clause 2.2. | +| Supported Features
(See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| DSR Flags
(See 7.3.25) | DSR-Flags | M | This Information Element shall contain a bit mask. See 7.3.25 for the meaning of the bits. | + +**Table 5A.2.2.2.1/2: Delete VCSG Subscriber Data Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|-----------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Supported Features
(See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | +| Result
(See 7.4) | Result-Code / Experimental-Result | M | This IE shall contain the result of the operation.
The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [61]).
The Experimental-Result AVP shall be used for S7a/S7d errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.
The following errors are applicable in this case:
- User Unknown | + +#### 5A.2.2.2.2 Detailed behaviour of the MME and the SGSN + +When receiving a Delete VCSG Subscriber Data request, the MME or SGSN shall check whether the IMSI is known. + +If it is not known, a result code of DIAMETER\_ERROR\_USER\_UNKNOWN shall be returned. + +If it is known, the MME or SGSN shall delete all the stored "CSG subscription data from CSS". + +If the deletion of the subscription data succeeds in the MME or SGSN, the Result-Code shall be set to DIAMETER\_SUCCESS. + +If the MME or SGSN cannot fulfil the received request for other reasons, e.g. due to a database error, it shall set the Result-Code to DIAMETER\_UNABLE\_TO\_COMPLY. + +#### 5A.2.2.2.3 Detailed behaviour of the CSS + +The CSS shall make use of this procedure to remove all the CSG subscription data associated to CSS from the MME or SGSN. + +NOTE: When a Delete VCSG Subscriber Data procedure occurs, the MME or SGSN remains registered in the CSS + +If the CSS receives a Delete VCSG Subscriber Data answer with the Result Code DIAMETER\_ERROR\_USER\_UNKNOWN from the MME or SGSN, the CSS shall clear the stored MME or SGSN identity. + +### 5A.2.3 Fault Recovery Procedures + +#### 5A.2.3.1 VCSG Reset + +##### 5A.2.3.1.1 General + +The VCSG Reset Procedure shall be used by the CSS, after a restart, to indicate to the MME and to the SGSN that a failure has occurred. + +This procedure is mapped to the commands Reset-Request/Answer (RSR/RSA) in the S7a/S7d Diameter application specified in chapter 7. + +Table 5A.2.3.1.1/1 specifies the involved information elements for the request. + +Table 5A.2.3.1.1/2 specifies the involved information elements for the answer. + +**Table 5A.2.3.1.1/1: VCSG Reset Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|-------------------------|------|-------------------------------------------------------------------------------------------------------| +| Supported Features
(See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +**Table 5A.2.3.1.1/2: VCSG Reset Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|------------------------------------------------|-----------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result
(See 7.4) | Result-Code / Experimental-Result | M | This IE shall contain the result of the operation.
The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [61]).
The Experimental-Result AVP shall be used for S7a/S7d errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.
There are no Experimental-Result codes applicable for this command. | +| Supported Features
(See 3GPP TS 29.229 [9]) | Supported-Features | O | If present, this information element shall contain the list of features supported by the origin host. | + +#### 5A.2.3.1.2 Detailed behaviour of the MME and the SGSN + +When receiving a VCSG Reset message, the MME or SGSN or combined MME/SGSN, for all roaming users for which they have a registration in CSS, shall mark "Location Information Confirmed in CSS" record as "Not Confirmed". The MME or SGSN or combined MME/SGSN shall make use of the CSS Identity received in the Origin-Host AVP (by comparing it with the value stored after successful ULA) in order to determine which user records are impacted. + +When, as described in 3GPP TS 23.007 [43], an event requiring the MME or SGSN to check the "CSG subscription data from CSS" occurs, and if the user record "Location Information Confirmed in CSS" is marked as "Not Confirmed", the restoration procedure shall be triggered. + +#### 5A.2.3.1.3 Detailed behaviour of the CSS + +The CSS shall make use of this procedure in order to indicate to all relevant MMEs, SGSNs, and combined MME/SGSNs that the CSS has restarted and may have lost the current MME-Identity and SGSN-Identity of some of its users who may be currently roaming in the MME area and/or SGSN area, and to which the CSS, therefore, cannot send e.g. Insert VCSG Subscriber Data messages when needed. + +The CSS should invoke this procedure towards a combined MME/SGSN only for a single time even if some of the impacted subscribers are attached to the combined MME/SGSN via UTRAN/GERAN and some of the impacted subscribers are attached to the combined MME/SGSN via E-UTRAN. + +## 6 MME – EIR (S13) and SGSN – EIR (S13') + +### 6.1 Introduction + +The S13 interface shall enable the ME Identity check procedure between the MME and the EIR as described in the 3GPP TS 23.401 [2]. + +The S13' interface shall enable the ME Identity check procedure between the SGSN and the EIR as described in the 3GPP TS 23.060 [12]. + +### 6.2 ME Identity Check Procedures + +#### 6.2.1 ME Identity Check + +##### 6.2.1.1 General + +This Mobile Equipment Identity Check Procedure shall be used between the MME and the EIR and between the SGSN and the EIR to check the Mobile Equipment's identity status (e.g. to check that it has not been stolen, or, to verify that it does not have faults). + +This procedure is mapped to the commands ME-Identity-Check-Request/Answer (ECR/ECA) in the Diameter application specified in chapter 6. + +Table 6.2.1.1/1 specifies the involved information elements for the request. + +Table 6.2.1.1/2 specifies the involved information elements for the answer. + +**Table 6.2.1.1/1: ME Identity Check Request** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|----------------------------------|------------------------------------|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Terminal Information (See 7.3.3) | Terminal-Information | M | This information element shall contain the information about the used mobile equipment i.e. the IMEI. Within this Information Element, only the IMEI and the Software-Version AVPs shall be used on the S13/S13' interface. | +| IMSI | User-Name (See IETF RFC 6733 [61]) | O | This information element shall contain the user IMSI, formatted according to 3GPP TS 23.003 [3], clause 2.2. | + +**Table 6.2.1.1/2: ME Identity Check Answer** + +| Information element name | Mapping to Diameter AVP | Cat. | Description | +|-------------------------------|-----------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Result (See 7.4) | Result-Code / Experimental-Result | M | This IE shall contain the result of the operation.
The Result-Code AVP shall be used to indicate success / errors as defined in the Diameter base protocol (see IETF RFC 6733 [61]).
The Experimental-Result AVP shall be used for S13/S13' errors. This is a grouped AVP which shall contain the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP.
The following errors are applicable in this case:
- Unknown equipment | +| Equipment Status (See 7.3.51) | Equipment-Status | C | This information element shall contain the status of the requested mobile equipment as defined in 3GPP TS 22.016 [13].
It shall be present if the result of the ME Identity Check is DIAMETER_SUCCESS. | + +### 6.2.1.2 Detailed behaviour of the MME and the SGSN + +The MME or the SGSN shall make use of this procedure to check the ME identity, if the MME or the SGSN is configured to check the IMEI with the EIR. + +Terminal-Information, when sent by the MME/SGSN to the EIR, shall contain the IMEI AVP, and it may contain also the Software-Version AVP. + +IMSI may be sent together with Terminal Information to the EIR for operator-determined purposes. + +When receiving the ME Identity Check answer from the EIR, the MME or the SGSN shall check the result code and the equipment status. Dependent upon the result, the MME or the SGSN will decide its subsequent actions (e.g. sending an Attach Reject if the EIR indicates that the Mobile Equipment is unknown or blacklisted). + +### 6.2.1.3 Detailed behaviour of the EIR + +When receiving an ME Identity Check request, the EIR shall check whether the mobile equipment is known. + +The EIR shall identify the mobile equipment based on the first 14 digits of the IMEI AVP; if a 15th digit is received in the IMEI AVP, this digit shall be ignored by the EIR. + +Based on operator policies, the EIR may also use the Software-Version AVP, in addition to the first 14 digits of the IMEI AVP, to check the equipment identity against Black and Grey lists (see 3GPP TS 22.016 [13]). + +If the mobile equipment identity is not known, a result code of DIAMETER\_ERROR\_EQUIPMENT\_UNKNOWN is returned. + +If it is known, the EIR shall return DIAMETER\_SUCCESS with the equipment status. + +## 7 Protocol Specification and Implementation + +### 7.1 Introduction + +#### 7.1.1 Use of Diameter base protocol + +The Diameter base protocol as specified in IETF RFC 6733 [61] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and error codes as specified in this specification. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) shall be used unmodified. + +#### 7.1.2 Securing Diameter Messages + +For secure transport of Diameter messages, see 3GPP TS 33.210 [16]. + +If there are no intermediate Diameter Agent networks located between the visited PLMN and the home PLMN, the HSS or the first Diameter Agent located in the home PLMN which has direct connection with the serving network is required to check that the realm contained in the Origin-Realm AVP in the request from the serving network corresponds to the right serving network. + +If there are intermediate Diameter Agent networks located between the visited PLMN and home PLMN, the first Diameter Agent which has direct connection with the serving network is required to check that the realm contained in the Origin-Realm AVP in the request from the serving network corresponds to the right serving network. + +NOTE 1: How to do the above check is implementation specific, e.g. it may be done by checking if the IP addresses of the serving network nodes match with the realm received in the Origin-Realm AVP in the request. + +NOTE 2: Network configurations where a (potential) visited PLMN acts as intermediate Diameter Agent network are not allowed. + +NOTE 3: In the case there are intermediate Diameter Agent networks, the home network has to trust these intermediate Diameter agent networks to do the check and other hop by hop security check. This trust is usually substantiated by contracts since there are no remote technical means to verify if the checks were actually performed. + +#### 7.1.3 Accounting functionality + +Accounting functionality (Accounting Session State Machine, related command codes and AVPs) shall not be used on the S6a, S6d, S13 and S13' interfaces. + +#### 7.1.4 Use of sessions + +Between the MME and the HSS and between the SGSN and the HSS and between the MME and the EIR, Diameter sessions shall be implicitly terminated. An implicitly terminated session is one for which the server does not maintain state information. The client shall not send any re-authorization or session termination requests to the server. + +The Diameter base protocol specified in IETF RFC 6733 [61] includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions. + +The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value NO\_STATE\_MAINTAINED (1), as described in IETF RFC 6733 [61]. As a consequence, the server shall not maintain any state information about this session and the client shall not send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses. + +#### 7.1.5 Transport protocol + +Diameter messages over the S6a, S6d, S13, S13', S7a and S7d interfaces shall make use of SCTP IETF RFC 4960 [14]. + +## 7.1.6 Routing considerations + +This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host. + +If an MME or SGSN knows the address/name of the HSS for a certain user, and the associated home network domain name, both the Destination-Realm and Destination-Host AVPs shall be present in the request. + +NOTE: When sending a ULR command for a certain user due to HSS restoration procedure (i.e, after the MME/SGSN have received a Reset command from the HSS), the MME or the SGSN might consider the stored address/name of the HSS for the user to be invalid and hence not known. + +If an MME or SGSN knows only the home network domain name for a certain user, the Destination-Realm AVP shall be present and the command shall be routed to the next Diameter node. + +If an MME or SGSN knows only the identity of the user, the home network domain name shall be derived from the user's IMSI (MNC and MCC values) to construct the EPC Home Network Realm/Domain, as indicated in 3GPP TS 23.003 [3], clause 19.2, and use it as Destination-Realm. + +Consequently, the Destination-Host AVP is declared as optional in the ABNF for all requests initiated by an MME or SGSN. + +The address/name of the EIR shall be locally configured in the MME. + +Requests initiated by the HSS towards an MME or SGSN shall include both Destination-Host and Destination-Realm AVPs. + +The HSS obtains the Destination-Host AVP to use in requests towards an MME or SGSN, from the Origin-Host AVP received in previous requests from the MME or SGSN. Consequently, the Destination-Host AVP is declared as mandatory in the ABNF for all requests initiated by the HSS. The Origin-Host AVP received in requests from the MME may contain a Diameter identity of the MME encoded as specified in clause 19.4.2.4 of 3GPP TS 23.003 [3]. The Origin-Host AVP received in requests from the SGSN may contain a Diameter identity of the SGSN encoded as specified in clause 19.4.2.6 of 3GPP TS 23.003 [3]. + +The HSS obtains the Destination-Realm AVP to use in requests towards an MME or SGSN, from the Origin-Realm AVP received in previous requests from the MME or SGSN. The Origin-Realm AVP in the requests received by the HSS in roaming cases, should contain the domain name of the network to which the MME or the SGSN belongs, encoded as specified in clause 19.2 of 3GPP TS 23.003 [3]. + +The Destination-Realm AVP is declared as mandatory in the ABNF for all requests. + +If the Vendor-Specific-Application-ID AVP is received in any of the commands defined in this specification, it shall be ignored by the receiving node, and it shall not be used for routing purposes. + +## 7.1.7 Advertising Application Support + +The HSS, MME, SGSN and EIR shall advertise support of the Diameter S6a/S6d and/or S13/S13' Application by including the value of the application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +The vendor identifier value of 3GPP (10415) shall be included in the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. + +The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above shall indicate the manufacturer of the Diameter node as per IETF RFC 6733 [61]. + +## 7.1.8 Diameter Application Identifier + +This clause specifies three Diameter applications: The S6a/S6d interface application, the S13/S13' interface application, and the S7a/S7d interface application. + +The S6a/S6d interface application allows a Diameter server and a Diameter client: + +- to exchange location information; +- to authorize a user to access the EPS; +- to exchange authentication information; +- to download and handle changes in the subscriber data stored in the server. + +The S6a/S6d interface protocol shall be defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP (
This attribute holds the EPS PDN Connection Charging Characteristics data for an EPS APN Configuration, or the PDP context Charging Characteristics for GPRS PDP context, or the Subscribed Charging Characteristics data for the subscriber level 3GPP Charging Characteristics; refer to 3GPP TS 23.008 [30]. | | +| Supported-Features | 3GPP TS 29.229 [9] | | | +| Feature-List-ID | 3GPP TS 29.229 [9] | | | +| Feature-List | 3GPP TS 29.229 [9] | See clause 7.3.10 | | +| Served-Party-IP-Address | 3GPP TS 32.299 [8] | holds the PDN IP Address of the user | | +| QoS-Class-Identifier | 3GPP TS 29.212 [10] | | | +| Allocation-Retention-Priority | 3GPP TS 29.212 [10] | See clause 7.3.40 | | +| Priority-Level | 3GPP TS 29.212 [10] | | | +| Pre-emption-Capability | 3GPP TS 29.212 [10] | | | +| Pre-emption-Vulnerability | 3GPP TS 29.212 [10] | | | +| Max-Requested-Bandwidth-DL | 3GPP TS 29.214 [11] | | | +| Max-Requested-Bandwidth-UL | 3GPP TS 29.214 [11] | | | +| Extended-Max-Requested-BW-DL | 3GPP TS 29.214 [11] | | | +| Extended-Max-Requested-BW-UL | 3GPP TS 29.214 [11] | | | +| RAT-Type | 3GPP TS 29.212 [10] | See clause 7.3.13 | Must set | +| MSISDN | 3GPP TS 29.329 [25] | | | +| MIP6-Agent-Info | IETF RFC 5447 [26] | | | +| MIP-Home-Agent-Address | IETF RFC 4004 [27] | | | +| MIP-Home-Agent-Host | IETF RFC 4004 [27] | | | +| PDP-Address | 3GPP TS 32.299 [8] | | | +| Confidentiality-Key | 3GPP TS 29.229 [9] | See clause 7.3.57 | | +| Integrity-Key | 3GPP TS 29.229 [9] | See clause 7.3.58 | | +| Visited-Network-Identifier | 3GPP TS 29.229 [9] | See clause 7.3.105 | Must not set | +| GMLC-Address | 3GPP TS 29.173 [37] | See clause 7.3.109 | Must not set | +| User-CSG-Information | 3GPP TS 32.299 [8] | | Must not set | +| ProSe-Subscription-Data | 3GPP TS 29.344 [49] | See clause 7.3.180 | Must not set | +| OC-Supported-Features | IETF RFC 7683 [50] | See clause 7.3.178 | Must not set | +| OC-OLR | IETF RFC 7683 [50] | See clause 7.3.179 | Must not set | +| SCEF-Reference-ID | 3GPP TS 29.336 [54] | | Must not set | + +| Attribute Name | Reference | Comments | M-bit | +|------------------------------------|---------------------|---------------------|--------------| +| SCEF-ID | 3GPP TS 29.336 [54] | | Must not set | +| AESE-Communication-Pattern | 3GPP TS 29.336 [54] | see clause 7.3.193 | Must not set | +| Communication-Pattern-set | 3GPP TS 29.336 [54] | see clause 7.3.194 | Must not set | +| Monitoring-Event-Configuration | 3GPP TS 29.336 [54] | See clause 7.3.195 | Must not set | +| Monitoring-Event-Report | 3GPP TS 29.336 [54] | See clause 7.3.196 | Must not set | +| UE-Reachability-Configuration | 3GPP TS 29.336 [54] | See clause 7.3.197 | Must not set | +| eNodeB-ID | 3GPP TS 29.217 [56] | See clause 7.3.198 | Must not set | +| SCEF-Reference-ID-for-Deletion | 3GPP TS 29.336 [54] | | Must not set | +| Monitoring-Type | 3GPP TS 29.336 [54] | | Must not set | +| Maximum-Number-of-Reports | 3GPP TS 29.336 [54] | | Must not set | +| Monitoring-Duration | 3GPP TS 29.336 [54] | | Must not set | +| Charged-Party | 3GPP TS 29.336 [54] | | Must not set | +| UE-Reachability-Configuration | 3GPP TS 29.336 [54] | | Must not set | +| Location-Information-Configuration | 3GPP TS 29.336 [54] | | Must not set | +| Reachability-Type | 3GPP TS 29.336 [54] | | Must not set | +| Maximum-Response-Time | 3GPP TS 29.336 [54] | | Must not set | +| Reachability-Information | 3GPP TS 29.336 [54] | | Must not set | +| Monitoring-Event-Config-Status | 3GPP TS 29.336 [54] | | Must not set | +| Supported-Services | 3GPP TS 29.336 [54] | See clause 7.3.199 | Must not set | +| Supported-Monitoring-Events | 3GPP TS 29.336 [54] | See clause 7.3.200 | Must not set | +| DRMP | IETF RFC 7944 [57] | See clause 7.3.203 | Must not set | +| Reference-ID-Validity-Time | 3GPP TS 29.336 [54] | | Must not set | +| Maximum-UE-Availability-Time | 3GPP TS 29.338 [48] | See clause 5.3.3.22 | Must not set | +| Emergency-Services | 3GPP TS 29.273 [59] | | | +| Load | IETF RFC 8583 [60] | See clause 7.3.211 | Must not set | +| Extended-eNodeB-ID | 3GPP TS 29.217 [56] | See clause 7.3.218 | Must not set | +| External-Identifier | 3GPP TS 29.336 [54] | | Must not set | + +| Attribute Name | Reference | Comments | M-bit | +|---------------------------------------|---------------------|--------------------|-------------------| +| Loss-Of-Connectivity-Reason | 3GPP TS 29.336 [54] | | Must not set | +| Active-Time | 3GPP TS 29.128 [63] | | Must not set | +| Idle-Status-Indication | 3GPP TS 29.128 [63] | | Must not set | +| MTC-Provider-Info | 3GPP TS 29.336 [54] | | Must not set | +| Traffic-Profile | 3GPP TS 29.336 [54] | | Must not set | +| PDN-Connectivity-Status-Configuration | 3GPP TS 29.336 [54] | See clause 7.3.195 | Must not set | +| PDN-Connectivity-Status-Report | 3GPP TS 29.336 [54] | See clause 7.3.196 | Must not set | +| Battery-Indicator | 3GPP TS 29.336 [54] | | Battery-Indicator | +| SCEF-Reference-ID-Ext | 3GPP TS 29.336 [54] | | Must not set | +| SCEF-Reference-ID-for-Deletion-Ext | 3GPP TS 29.336 [54] | | Must not set | + +NOTE 1: The M-bit settings for re-used AVPs override those of the defining specifications that are referenced. Values include: "Must set", "Must not set". If the M-bit setting is blank, then the defining specification applies. + +NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit. + +### 7.3.2 Subscription-Data + +The Subscription-Data AVP is of type Grouped. It shall contain the information related to the user profile relevant for EPS and GERAN/UTRAN. + +AVP format: + +Subscription-Data ::=
This bit, when cleared, indicates that the ULR message is sent on the S6d interface, i.e. the source node is an SGSN (or a combined MME/SGSN to which the UE is attached via UTRAN or GERAN). | +| 2 | Skip Subscriber Data | This bit, when set, indicates that the HSS may skip subscription data in ULA. If the subscription data has changed in the HSS after the last successful update of the MME/SGSN, the HSS shall ignore this bit and send the updated subscription data. If the HSS effectively skips the sending of subscription data, the GPRS-Subscription-Data-Indicator flag can be ignored. | +| 3 | GPRS-Subscription-Data-Indicator | This bit, when set, indicates that the HSS shall include in the ULA command the GPRS subscription data, if available in the HSS; it shall be included in the GPRS-Subscription-Data AVP inside the Subscription-Data AVP (see 7.3.2).
Otherwise, the HSS shall not include the GPRS-Subscription-Data AVP in the response, unless the Update Location Request is received over the S6d interface and there is no APN configuration profile stored for the subscriber, or when the subscription data is returned by a Pre-Rel-8 HSS (via an IWF).
A standalone MME shall not set this bit when sending a ULR. | +| 4 | Node-Type-Indicator | This bit, when set, indicates that the requesting node is a combined MME/SGSN.
This bit, when cleared, indicates that the requesting node is a single MME or SGSN; in this case, if the S6a/S6d-Indicator is set, the HSS may skip the check of those supported features only applicable to the SGSN, and if, in addition the MME does not request to be registered for SMS, the HSS may consequently skip the download of the SMS related subscription data to a standalone MME. NOTE2 | +| 5 | Initial-Attach-Indicator | This bit, when set, indicates that the HSS shall send Cancel Location to the MME or SGSN if there is the MME or SGSN registration. | +| 6 | PS-LCS-Not-Supported-By-UE | This bit, when set, indicates to the HSS that the UE does not support neither UE Based nor UE Assisted positioning methods for Packet Switched Location Services. The MME shall set this bit on the basis of the UE capability information. The SGSN shall set this bit on the basis of the UE capability information and the access technology supported by the SGSN. | +| 7 | SMS-Only-Indication | This bit, when set, indicates that the UE indicated "SMS only" when requesting a combined IMSI attach or combined RA/LU. | +| 8 | Dual-Registration-5G-Indicator | This bit, when set by an MME over S6a interface, indicates that the HSS+UDM shall not send Nudm_UECM_DeregistrationNotification to the registered AMF (if any); when not set by an MME over S6a interface, it indicates that the HSS+UDM shall send Nudm_UECM_DeregistrationNotification to the registered AMF (if any). See 3GPP TS 29.503 [66].
An SGSN shall not set this bit when sending ULR over S6d interface. | + +NOTE1: Bits not defined in this table shall be cleared by the sending MME or SGSN and discarded by the receiving HSS. + +NOTE2: If the MME is registered for SMS then the HSS will download the SMS related data also for the standalone MME. + +## 7.3.8 ULA-Flags + +The ULA-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 7.3.8/1: + +**Table 7.3.8/1: ULA-Flags** + +| Bit | Name | Description | +|----------------------------------------------------------------------------------------------------------------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | Separation Indication | This bit, when set, indicates that the HSS stores SGSN number and MME number in separate memory. A Rel-8 HSS shall set the bit. An IWF interworking with a pre Rel-8 HSS/HLR shall clear the bit. | +| 1 | MME Registered for SMS | This bit, when set, indicates that the HSS has registered the MME for SMS. | +| NOTE: Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving MME or SGSN. | | | + +## 7.3.9 Visited-PLMN-Id + +The Visited-PLMN-Id AVP is of type OctetString. This AVP shall contain the concatenation of MCC and MNC. See 3GPP TS 23.003 [3]. The content of this AVP shall be encoded as an octet string according to table 7.3.9-1. + +See 3GPP TS 24.008 [31], clause 10.5.1.13, PLMN list, for the coding of MCC and MNC. If MNC is 2 digits long, bits 5 to 8 of octet 2 are coded as "1111". + +**Table 7.3.9/1: Encoding format for Visited-PLMN-Id AVP** + +| 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | | +|---|---|---|---|-------------|---|---|---|---------| +| | | | | MCC digit 2 | | | | octet 1 | +| | | | | MNC digit 3 | | | | octet 2 | +| | | | | MNC digit 2 | | | | octet 3 | + +## 7.3.10 Feature-List AVP + +### 7.3.10.1 Feature-List AVP for the S6a/S6d application + +The syntax of this AVP is defined in 3GPP TS 29.229 [9]. + +For the S6a/S6d application, the meaning of the bits shall be as defined in table 7.3.10/1 for the Feature-List-ID 1 and in table 7.3.10/2 for the Feature-List-ID 2. + +**Table 7.3.10/1: Features of Feature-List-ID 1 used in S6a/S6d** + +| Feature bit | Feature | M/O | Description | +|-------------|-------------------------------------------|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | ODB-all-APN | O | Operator Determined Barring of all Packet Oriented Services
This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send this ODB barring category to the MME or SGSN within ULA. Instead the HSS may reject location update by sending DIAMETER_ERROR_ROAMING_NOT_ALLOWED and, optionally, including the type of ODB in the Error-Diagnostic AVP. If the MME or SGSN does not indicate support of this feature in IDA and the HSS has sent this ODB category within IDR, the HSS may apply barring of roaming and send CLR. | +| 1 | ODB-HPLMN-APN | O | Operator Determined Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN
This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send this ODB barring category to the MME or SGSN within ULA. Instead the HSS may reject location update by sending DIAMETER_ERROR_ROAMING_NOT_ALLOWED and, optionally, including the type of ODB in the Error-Diagnostic AVP. If the MME or SGSN does not indicate support of this feature in IDA and the HSS has sent this ODB category within IDR, the HSS may apply barring of roaming and send CLR. | +| 2 | ODB-VPLMN-APN | O | Operator Determined Barring of Packet Oriented Services from access points that are within the roamed to VPLMN
This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send this ODB barring category to the MME or SGSN within ULA. Instead the HSS may reject location update by sending DIAMETER_ERROR_ROAMING_NOT_ALLOWED and, optionally, including the type of ODB in the Error-Diagnostic AVP. If the MME or SGSN does not indicate support of this feature in IDA and the HSS has sent this ODB category within IDR, the HSS may apply barring of roaming and send CLR. | +| 3 | ODB-all-OG | O | Operator Determined Barring of all outgoing calls
This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send this ODB barring category to the MME or SGSN within ULA. Instead the HSS may reject location update. If the MME or SGSN does not indicate support of this feature in IDA and the HSS has sent this ODB category within IDR, the HSS may apply barring of roaming and send CLR. | +| 4 | ODB-all-InternationalOG | O | Operator Determined Barring of all outgoing international calls
This feature is applicable for the ULR/ULA and IDR/IDA command pairs.If the MME or SGSN does not support this feature, the HSS shall not send this ODB barring category to the MME or SGSN within ULA. Instead the HSS may reject location update. If the MME or SGSN does not indicate support of this feature in IDA and the HSS has sent this ODB category within IDR, the HSS may apply barring of roaming and send CLR. | +| 5 | ODB-all-InternationalOGNotToHPLMN-Country | O | Operator Determined Barring of all outgoing international calls except those directed to the home PLMN country
This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send this ODB barring category to the MME or SGSN within ULA. Instead the HSS may reject location update. If the MME or SGSN does not indicate support of this feature in IDA and the HSS has sent this ODB category within IDR, the HSS may apply barring of roaming and send CLR. | + +| | | | | +|----|-------------------------------------------------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6 | ODB-all-Interzonal OG | O | Operator Determined Barring of all outgoing inter-zonal calls
This feature is applicable for the ULR/ULA and IDR/IDA command pairs.
If the MME or SGSN does not support this feature, the HSS shall not send this ODB barring category to the MME or SGSN within ULA. Instead the HSS may reject location update.
If the MME or SGSN does not indicate support of this feature in IDA and the HSS has sent this ODB category within IDR, the HSS may apply barring of roaming and send CLR. | +| 7 | ODB-all-Interzonal OGNotTo HPLMN-Country | O | Operator Determined Barring of all outgoing inter-zonal calls except those directed to the home PLMN country
This feature is applicable for the ULR/ULA and IDR/IDA command pairs.
If the MME or SGSN does not support this feature, the HSS shall not send this ODB barring category to the MME or SGSN within ULA. Instead the HSS may reject location update.
If the MME or SGSN does not indicate support of this feature in IDA and the HSS has sent this ODB category within IDR, the HSS may apply barring of roaming and send CLR. | +| 8 | ODB-all-Interzonal OGAndInternational OGNotTo HPLMN-Country | O | Operator Determined Barring of all outgoing international calls except those directed to the home PLMN country and Barring of all outgoing inter-zonal calls
This feature is applicable for the ULR/ULA and IDR/IDA command pairs.
If the MME or SGSN does not support this feature, the HSS shall not send this ODB barring category to the MME or SGSN within ULA. Instead the HSS may reject location update.
If the MME or SGSN does not indicate support of this feature in IDA and the HSS has sent this ODB category within IDR, the HSS may apply barring of roaming and send CLR. | +| 9 | RegSub | O | Regional Subscription
This feature is applicable for the ULR/ULA, IDR/IDA and DSR/DSA command pairs.
If the MME or SGSN does not support this feature, the HSS shall not send Regional Subscription Zone Codes to the MME or SGSN within ULA. Instead the HSS may reject location update.
If the MME or SGSN does not indicate support of this feature in IDA and the HSS has sent Regional Subscription Zone Codes within IDR, the HSS may apply barring of roaming and send CLR. | +| 10 | Trace | O | Trace Function
This feature is applicable for the ULR/ULA, IDR/IDA and DSR/DSA command pairs.
If the MME or SGSN does not indicate support of this feature in ULR, the HSS shall not send Trace Data to the MME or SGSN within ULA.
If the MME or SGSN does not indicate support of this feature in IDA, and the HSS has sent Trace Data within IDR, the HSS may store this indication, and not send any further Trace Data to that MME or SGSN.
If the MME or SGSN does not indicate support of this feature in DSA, and the HSS has sent Trace Data within DSR, the HSS may store this indication, and not send any further Trace Data to that MME or SGSN | +| 11 | LCS-all-PrivExcep (NOTE 1) | O | All LCS Privacy Exception Classes
This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports MAP based Lg interface.
If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA.
If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN. | + +| | | | | +|----|-----------------------------------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 12 | LCS-Universal (NOTE 1) | O |
Allow location by any LCS client
This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports MAP based Lg interface.
If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA.
If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
| +| 13 | LCS-CallSessionRelated (NOTE 1) | O |Allow location by any value added LCS client to which a call/session is established from the target UE
This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports MAP based Lg interface.
If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA.
If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
| +| 14 | LCS-CallSessionUnrelated (NOTE 1) | O |Allow location by designated external value added LCS clients
This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports MAP based Lg interface.
If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA.
If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
| +| 15 | LCS-PLMNOperator (NOTE 1) | O |Allow location by designated PLMN operator LCS clients
This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports MAP based Lg interface.
If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA.
If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
| +| 16 | LCS-ServiceType (NOTE 1) | O |Allow location by LCS clients of a designated LCS service type
This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports MAP based Lg interface.
If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA.
If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
| +| 17 | LCS-all-MOLR-SS (NOTE 1) | O |All Mobile Originating Location Request Classes
This feature is applicable for the ULR/ULA and IDR/IDA command pairs. Over S6d interface, this feature is applicable when the SGSN supports MAP based Lg interface.
If the MME or SGSN does not support this feature, the HSS shall not send the related LCS information to the MME or SGSN within ULA.
If the MME or SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that MME or SGSN.
| + +| | | | | +|----|-------------------------------------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 18 | LCS-BasicSelf Location (NOTE 1) | O |Allow an MS to request its own location
This feature is applicable for the ULR/ULA and IDR/IDA command pairs. Over S6d interface, this feature is applicable when the SGSN supports MAP based Lg interface. If the MME or SGSN does not support this feature, the HSS shall not send the related LCS information to the MME or SGSN within ULA.
If the MME or SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that MME or SGSN.
| +| 19 | LCS-AutonomousSelfLocation (NOTE 1) | O |Allow an MS to perform self location without interaction with the PLMN
This feature is applicable for the ULR/ULA and IDR/IDA command pairs. Over S6d interface, this feature is applicable when the SGSN supports MAP based Lg interface. If the MME or SGSN does not support this feature, the HSS shall not send the related LCS information to the MME or SGSN within ULA.
If the MME or SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that MME or SGSN.
| +| 20 | LCS-TransferToThirdParty | O |Allow an MS to request transfer of its location to another LCS client
This feature is applicable for the ULR/ULA and IDR/IDA command pairs. Over S6d interface, this feature is applicable when the SGSN supports MAP based Lg interface. If the MME or SGSN does not support this feature, the HSS shall not send the related LCS information to the MME or SGSN within ULA.
If the MME or SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that MME or SGSN.
| +| 21 | SM-MO-PP (NOTE 1) | O |Short Message MO-PP
This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send the related SMS information to the MME or SGSN within ULA.
If the MME or SGSN does not indicate support of this feature in IDA, and the HSS has sent the related SMS information within IDR, the HSS may store this indication, and not send any further SMS information to that MME or SGSN.
| +| 22 | Barring-Outgoing Calls | O |Barring of Outgoing Calls
This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send the related SMS information to the MME or SGSN within ULA.
If the MME or SGSN does not indicate support of this feature in IDA, and the HSS has sent the related SMS information within IDR, the HSS may store this indication, and not send any further SMS information to that MME or SGSN.
| +| 23 | BAOC | O |Barring of all outgoing calls
This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send the related SMS information to the MME or SGSN within ULA.
If the MME or SGSN does not indicate support of this feature in IDA, and the HSS has sent the related SMS information within IDR, the HSS may store this indication, and not send any further SMS information to that MME or SGSN.
| + +| | | | | +|----|--------------------------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 24 | BOIC | O |Barring of outgoing international calls
This feature is applicable for the ULR/ULA and IDR/IDA command pairs.
If the SGSN does not support this feature, the HSS shall not send the related SMS information to the MME or SGSN within ULA.
If the MME or SGSN does not indicate support of this feature in IDA, and the HSS has sent the related SMS information within IDR, the HSS may store this indication, and not send any further SMS information to that MME or SGSN.
| +| 25 | BOICExHC | O |Barring of outgoing international calls except those directed to the home PLMN Country
This feature is applicable for the ULR/ULA and IDR/IDA command pairs.
If the MME or SGSN does not support this feature, the HSS shall not send the related SMS information to the MME or SGSN within ULA.
If the MME or SGSN does not indicate support of this feature in IDA, and the HSS has sent the related SMS information within IDR, the HSS may store this indication, and not send any further SMS information to that MME or SGSN.
| +| 26 | UE-Reachability-Notification | O |UE Reachability Notification
This feature is applicable for the ULR/ULA and IDR/IDA command pairs, over S6a and S6d.
If the MME or SGSN indicates in the ULR command that it does not support the UE-Reachability-Notifications, the HSS shall not set the "UE-Reachability-Request" bit in IDR-Flags in subsequent IDR commands towards that MME or SGSN.
| +| 27 | T-ADS Data Retrieval | O |Terminating Access Domain Selection Data Retrieval
This feature is applicable for the ULR/ULA and IDR/IDA command pairs, over S6a and S6d.
If the MME or SGSN indicates in the ULR command that it does not support the retrieval of T-ADS data via IDR/IDA commands, the HSS shall not set the "T-ADS Data Request" bit in IDR-Flags in subsequent IDR commands towards that MME or SGSN.
| +| 28 | State/Location-Information-Retrieval | O |State/Location Information Retrieval
This feature is applicable for the ULR/ULA and IDR/IDA command pairs, over S6a and S6d.
If the MME or SGSN indicates in the ULR command that it does not support State/Location Information Retrieval, the HSS shall not set the "EPS User State Request", "EPS Location Information Request" or "Current Location Request" bits in IDR-Flags in subsequent IDR commands towards that MME or SGSN.
| +| 29 | Partial Purge | O |Partial Purge from a Combined MME/SGSN
This feature is applicable for the ULR/ULA and PUR/PUA command pairs, over S6a and S6d.
If the HSS indicates in the ULA command that it does not support Partial Purge, the combined MME/SGSN shall not include in the PUR command the indication of the specific serving node where the Purge has been done.
| +| 30 | Local Time Zone Retrieval | O |UE Time Zone Retrieval
This feature is applicable for the ULR/ULA and IDR/IDA command pairs, over S6a and S6d.
If the MME or SGSN indicates in the ULR command that it does not support the retrieval of Local Time Zone via IDR/IDA commands, the HSS shall not set the "Local Time Zone Request" bit in IDR-Flags in subsequent IDR commands towards that MME or SGSN.
| + +| | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 31 | Additional MSISDN | O |Additional MSISDN
This feature is applicable for the ULR/ULA, IDR/IDA and DSR/DSA command pairs, over S6a and S6d.
If the MME or SGSN indicates in the ULR command that it does not support A-MSISDN, the HSS shall populate the MSISDN AVP either with the subscribed MSISDN or the subscribed additional MSISDN based on operator policy and availability and the HSS shall not send IDR with the A-MSISDN AVP or DSR with the "A-MSISDN Withdrawal" bit to the serving nodes when the subscription data is changed.
If the MME or SGSN indicates in the IDA command that it does not support this feature and the HSS has already sent an A-MSISDN value within IDR, the HSS may store this indication and not send any further A-MSISDN updates to that MME or SGSN.
| +|Feature bit: The order number of the bit within the Supported-Features AVP, e.g. "1".
Feature: A short name that can be used to refer to the bit and to the feature, e.g. "ODB-HPLMN-APN".
M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O").
Description: A clear textual description of the feature.
NOTE 1: If both bits, corresponding to the feature defined for Lg interface and Lgd interface respectively, are not set, and the HSS supports the feature, the HSS shall not send the related LCS information to the SGSN within ULA and IDR.
SMS in MME
This feature is applicable for the ULR/ULA, IDR/IDA, DSR/DSA, NOR/NOA command pairs, over S6a.
It is used by the MME to notify the HSS it is capable of SMS transfer without the need of establishing an SGs association with an MSC.
If the MME does not support this feature, the HSS shall not send the related SMS information to the MME within ULA.
If the MME does not indicate support of this feature in IDA, and the HSS has sent the related SMS information within IDR, the HSS may store this indication, and not send any further SMS information to that MME.
If the HSS does not support this feature, the HSS shall ignore any request for a registration for SMS; the MME may store this feature indication, and not send any further request for a registration for SMS to the HSS.
| +| 1 | SMS in SGSN | O |SMS in SGSN
This feature is applicable for the ULR/ULA command pair, over S6d.
If the SGSN indicates in the ULR command that it does not support this feature, the HSS shall not indicate "SMS in SGSN Allowed" to the SGSN.
| +| 2 | Dia-LCS-all-PrivExcep (NOTE 1) | O |All LCS Privacy Exception Classes
This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports Diameter based Lgd interface.
If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA.
If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
| +| 3 | Dia-LCS-Universal (NOTE 1) | O |Allow location by any LCS client
This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports Diameter based Lgd interface.
If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA.
If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
| +| 4 | Dia-LCS-CallSessionRelated (NOTE 1) | O |Allow location by any value added LCS client to which a call/session is established from the target UE
This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports Diameter based Lgd interface.
If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA.
If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
| +| 5 | Dia-LCS-CallSessionUnrelated (NOTE 1) | O |Allow location by designated external value added LCS clients
This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports Diameter based Lgd interface.
If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA.
If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
| + +| | | | | +|----|-----------------------------------------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 6 | Dia-LCS-PLMNOperator (NOTE 1) | O |Allow location by designated PLMN operator LCS clients
This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports Diameter based Lgd interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA.
If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
| +| 7 | Dia-LCS-ServiceType (NOTE 1) | O |Allow location by LCS clients of a designated LCS service type
This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports Diameter based Lgd interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA.
If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
| +| 8 | Dia-LCS-all-MOLR-SS (NOTE 1) | O |All Mobile Originating Location Request Classes
This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports Diameter based Lgd interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA.
If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
| +| 9 | Dia-LCS-BasicSelfLocation (NOTE 1) | O |Allow an MS to request its own location
This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports Diameter based Lgd interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA.
If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
| +| 10 | Dia-LCS-AutonomousSelfLocation (NOTE 1) | O |Allow an MS to perform self location without interaction with the PLMN
This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports Diameter based Lgd interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA.
If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
| +| 11 | Dia-LCS-TransferToThirdParty (NOTE 1) | O |Allow an MS to request transfer of its location to another LCS client
This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports Diameter based Lgd interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA.
If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
| +| 12 | Gdd-in-SGSN | O |Support of Diameter based Gdd interface for SMS in SGSN
This feature is applicable for the ULR/ULA command pair over S6d, when the SGSN supports the Diameter based Gdd interface for SMS in SGSN.
| + +| | | | | +|----|----------------------------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 13 | Optimized-LCS-Proc-Support | O |Support for the optimized LCS procedure
This feature is applicable for the ULR/ULA command pair over S6a/S6d, when the network supports ISR and when the node is combined MME/SGSN and supports optimized LCS procedure as described in 3GPP TS 29.172 [47] clause 6.2.2.
| +| 14 | SGSN CAMEL Capability | O |Support of SGSN CAMEL Capability
This feature is applicable for the ULR/ULA command pair over S6d, when the SGSN supports the CAMEL capability.
| +| 15 | ProSe Capability | O |Support of ProSe Capability
This feature is applicable for the ULR/ULA and IDR/IDA command pairs over S6a (and S6d), when the MME (or combined MME/SGSN) supports the ProSe capability.
If the MME or combined MME/SGSN does not support this feature, the HSS shall not send the related ProSe subscription data to the MME or combined MME/SGSN within ULA.
If the MME or combined MME/SGSN does not indicate support of this feature in IDA, and the HSS has sent the related ProSe subscription data within IDR, the HSS may store this indication, and not send any further ProSe subscription data to that MME.
| +| 16 | P-CSCF Restoration | O |Support of P-CSCF Restoration
This feature is applicable to the ULR/ULA and IDR/IDA command pairs over the S6a or S6d interfaces, when the MME or SGSN supports the execution of the P-CSCF restoration procedures.
If the MME or the SGSN does not indicate support of this feature in ULR, the HSS shall not send subsequent IDR commands requesting the execution of HSS-based P-CSCF restoration procedures, as described in 3GPP TS 23.380 [51] clause 5.4.
| +| 17 | Reset-IDs | O |Support of Reset-IDs
This feature is applicable to the ULR/ULA and IDR/IDA and DSR/DSA and RSR/RSA command pairs over the S6a and S6d interfaces.
If the MME or SGSN indicates in the ULR command that it does not support Reset-IDs, the HSS shall not include Reset-ID AVPs in RSR commands sent to that MME or SGSN.
If the MME or SGSN indicates that it does not support this feature in IDA, and the HSS has already sent a Reset-ID value within IDR, the HSS may store this indication and not send any further Reset-ID updates to that MME or SGSN.
| +| 18 | Communication-Pattern | O |Support of AESE communication patterns
This feature is applicable to the ULR/ULA and IDR/IDA command pairs over S6a (and S6d), when the MME (or combined MME/SGSN) supports the AESE communication patterns.
If the MME or combined MME/SGSN does not indicate the support for this feature, the HSS shall not send CP parameter sets to the MME or combined MME/SGSN within IDR/ULA command.
If the MME or combined MME/SGSN indicates that it does not support this feature in IDA, and the HSS has already sent CP parameter sets within IDR, the HSS may store this indication and not send any further updates related to CP parameter sets to that MME or combined MME/SGSN.
| + +| | | | | +|----|-------------------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 19 | Monitoring-Event | O |Support of Monitoring Event
This feature is applicable to the ULR/ULA and IDR/IDA command pairs over the S6a or S6d interfaces, when the MME or SGSN supports the Monitoring event feature.
If the MME or SGSN does not indicate support of this feature in ULR, the HSS shall not send Monitoring event configuration data to the MME or SGSN within ULA and shall not send subsequent IDR commands requesting the configuration of Monitoring events in the MME or SGSN.
If the MME or SGSN indicates that it does not support this feature in IDA, and the HSS has already sent Monitoring event configuration data within IDR, the HSS may store this indication and not send any further updates related to Monitoring events to that MME or SGSN.
| +| 20 | Dedicated Core Networks | O |Support of Dedicated Core Networks
This feature is applicable to the ULR/ULA, IDR/IDA and DSR/DSA command pairs over the S6a and S6d interfaces.
If the MME/SGSN does not indicate support of this feature in the ULR command, the HSS shall not send DCN-related subscription data (e.g., UE Usage Type) in ULA, and shall not send subsequent IDR or DSR commands when such subscription data are updated.
If the MME/SGSN does not indicate support of this feature in the IDA command and the HSS has already sent DCN-related subscription data in IDR, the HSS may store this indication and not send further updates related to DCN subscription data.
| +| 21 | Non-IP PDN Type APNs | O |Support of Non-IP PDN Type APNs
This feature is applicable to the ULR/ULA and IDR/IDA command pairs over the S6a and S6d interfaces.
If the MME/SGSN does not indicate support of this feature in the ULR command, the HSS shall not send APN configurations with a Non-IP PDN type in the subscription data sent in ULA or in IDR, and shall not send IDR commands with the only purpose to update such subscription data.
If the MME or SGSN indicates in the IDA command that it does not support this feature, and the HSS has already sent Non-IP PDN Type APNs within IDR, the HSS may store this indication, and not send any further updates related to Non-IP PDN Type APNs to that MME or SGSN.
| +| 22 | Non-IP PDP Type APNs | O |Support of Non-IP PDP Type APNs
This feature is applicable to the ULR/ULA and IDR/IDA command pairs over the S6a/S6d interface.
If the MME/SGSN does not indicate support of this feature in the ULR command, the HSS shall not send PDP contexts (as part of the GPRS-Subscription-Data) with a Non-IP PDP type in the subscription data sent in ULA or in IDR, and shall not send IDR commands with the only purpose to update such subscription data.
If the MME or SGSN indicates in the IDA command that it does not support this feature, and the HSS has already sent Non-IP PDP Type APNs within IDR, the HSS may store this indication, and not send any further updates related to Non-IP PDP Type APNs to that MME or SGSN.
| +| 23 | Removal of MSISDN | O |Support of Removal of MSISDN
This feature is applicable to the ULR/ULA and DSR/DSA command pairs over the S6a/S6d interface.
If the MME/SGSN does not indicate support of this feature in the ULR command, the HSS shall not send DSR with the "MSISDN Withdrawal" bit set, to remove an existing MSISDN value from the subscription profile stored in the MME/SGSN.
| + +| | | | | +|----|------------------------------|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 24 | Emergency Service Continuity | O |Support of Emergency Services Continuity
This feature is applicable to the ULR/ULA, NOR/NOA and IDR/IDA command pairs over the S6a interface, when the HSS and the MME support the continuity of emergency services upon mobility between 3GPP and WLAN accesses, as specified in 3GPP TS 23.401 [2].
If the MME does not indicate support of this feature in a former ULR command, the HSS shall not include the Emergency Info in an ULA command and shall not send an IDR command to update the PGW in use for emergency services.
If the HSS does not indicate support of this feature in a former ULA command, the MME shall not send a NOR command to update the PGW in use for emergency services.
If the HSS supports this feature on S6a, it shall also support the Emergency Service Continuity feature on SWx, see 3GPP TS 29.273 [59].
| +| 25 | V2X Capability | O |Support of V2X Service
This feature is applicable for the ULR/ULA and IDR/IDA command pairs over S6a (and S6d), when the MME (or combined MME/SGSN) supports the V2X service.
If the MME or combined MME/SGSN does not support this feature, the HSS shall not send the related V2X subscription data to the MME or combined MME/SGSN within ULA.
If the MME or combined MME/SGSN does not indicate support of this feature in IDA, and the HSS has sent the related V2X subscription data within IDR, the HSS may store this indication, and not send any further V2X subscription data to that MME or that combined MME/SGSN.
| +| 26 | External-Identifier | O |Support of External-Identifier
This feature is applicable for the ULR/ULA, DSR/DSA and IDR/IDA command pairs over S6a (and S6d), when the MME (or combined MME/SGSN) supports the External-Identifier.
If the MME or combined MME/SGSN does not support this feature:
- -The HSS shall not send the External-Identifier subscription data to the MME or combined MME/SGSN within ULA.
- -The HSS shall not send Monitoring Event configuration for UEs that are part of a group and have no MSISDN as part of its subscription data to the MME/SGSN.
- -The HSS shall not indicate External-Identifier-Withdrawal in the DSR-Flags AVP of the DSR.
Support of NR as Secondary RAT
This feature is applicable to the ULR/ULA and IDR/IDA command pairs over S6a (and S6d) when the MME (or combined MME/SGSN) supports NR as Secondary RAT, and over S6d when the SGSN supports the indication related to NR as Secondary RAT (such as, e.g., the related Access Restriction Data, or extended QoS parameters).
If the MME, SGSN, or combined MME/SGSN does not support this feature, the HSS shall not send (in ULA) or update (in IDR) subscription data related to NR as Secondary RAT.
If the HSS does not support this feature, the MME shall ignore the bit "NR as Secondary RAT Not Allowed" in Access-Restriction-Data.
| + +| | | | | +|----|--------------------------------------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 28 | Unlicensed Spectrum as Secondary RAT | O |Support of Unlicensed Spectrum as Secondary RAT
This feature is applicable to the ULR/ULA and IDR/IDA command pairs over S6a (and S6d) when the MME (or combined MME/SGSN) supports the use of unlicensed spectrum in the form of LAA or LWA/LWIP as Secondary RAT.
If the MME (or combined MME/SGSN) does not support this feature, the HSS shall not send (in ULA) or update (in IDR) subscription data related to the use of unlicensed spectrum in the form of LAA, LWA/LWIP or NR in unlicensed bands as Secondary RAT (such as, e.g., the related Access Restriction Data).
If the HSS does not support this feature, the MME shall ignore the bit "Unlicensed Spectrum as Secondary RAT Not Allowed" in Access-Restriction-Data.
| +| 29 | Ethernet PDN Type APNs | O |Support of Ethernet PDN Type APNs
This feature is applicable to the ULR/ULA and IDR/IDA command pairs over the S6a and S6d interfaces.
If the MME (or combined MME/SGSN) does not indicate support of this feature in the ULR command, the HSS shall not send APN configurations with an Ethernet PDN type in the subscription data sent in ULA or in IDR, and shall not send IDR commands with the only purpose to update such subscription data.
If the MME (or combined MME/SGSN) indicates in the IDA command that it does not support this feature, and the HSS has already sent Ethernet PDN Type APNs within IDR, the HSS may store this indication, and not send any further updates related to Ethernet PDN Type APNs to that MME (or combined MME/SGSN).
| +| 30 | Extended Reference IDs | O |Extended Reference IDs
This feature is applicable to the ULR/ULA and IDR/IDA command pairs over the S6a or S6d interfaces, when the HSS and MME/SGSN support handling 64-bit long Reference IDs.
If the MME or SGSN does not indicate support of this feature in ULR, the HSS shall not send ULA or IDR commands containing 64-bit long SCEF Reference IDs or SCEF Reference IDs for Deletion.
| + +Feature bit: The order number of the bit within the Supported-Features AVP, e.g. "1". +Feature: A short name that can be used to refer to the bit and to the feature, e.g. "SMS in MME". +M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O"). +Description: A clear textual description of the feature. +NOTE 1: If both bits, corresponding to the same feature defined for Lg interface and Lgd interface, are not set, and the HSS supports the feature, the HSS shall not send the related LCS information to the SGSN within ULA and IDR. + +Features that are not indicated in the Supported-Features AVPs within a given application message shall not be used to construct that message. + +### 7.3.10.2 Feature-List AVP for the S7a/S7d application + +For the S7a/S7d application, the feature list does not contain any feature in this release. + +## 7.3.11 Requested-EUTRAN-Authentication-Info + +The Requested-EUTRAN-Authentication-Info is of type Grouped. It shall contain the information related to the authentication requests for E-UTRAN. + +AVP format + +Requested-EUTRAN-Authentication-Info ::=(Note 1) | +| 4 | STN-SR | This bit, when set, indicates that the Session Transfer Number for SRVCC shall be deleted from the subscriber data. | +| 5 | Complete PDP context list Withdrawal | This bit, when set, indicates that all PDP contexts for the subscriber shall be deleted from the subscriber data. | +| 6 | PDP contexts Withdrawal | This bit, when set, indicates that the PDP contexts whose identifier is included in the Context-Identifier AVP shall be deleted.
(Note 2) | +| 7 | Roaming Restricted due to unsupported feature | This bit, when set, indicates that the roaming restriction shall be deleted from the subscriber data in the MME or SGSN. | +| 8 | Trace Data Withdrawal | This bit, when set, indicates that the Trace Data shall be deleted from the subscriber data. | +| 9 | CSG Deleted | This bit, when set, indicates that
- - the "CSG-Subscription-Data from HSS" shall be deleted in the MME or SGSN when received over the S6a or S6d interface
- - the "CSG-Subscription-Data from CSS" shall be deleted in the MME or SGSN when received over the S7a or S7d interface.
Note 2: If the Complete PDP context list Withdrawal bit is set, this bit should not be set.
Note 3: Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving MME or SGSN.
Note 4: Bits 3 and 6 are excluding alternatives and shall not both be set.
Note 5: When this AVP is transferred over the S7a/S7d interface, only the bit 9 (CSG Deleted) is meaningful, other bits shall be cleared. | | | + +## 7.3.26 DSA-Flags + +The DSA-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits is defined in table 7.3.26/1: + +**Table 7.3.26/1: DSA-Flags** + +| Bit | Name | Description | +|---------------------------------------------------------------------------------------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| 0 | Network Node area restricted | This bit, when set, shall indicate that the complete Network Node area (SGSN area) is restricted due to regional subscription. | +| Note: Bits not defined in this table shall be cleared by the sending SGSN and discarded by the receiving HSS. | | | + +## 7.3.27 Context-Identifier + +The Context-Identifier AVP is of type Unsigned32. + +## 7.3.28 Void + +## 7.3.29 Subscriber-Status + +The 3GPP Subscriber Status AVP is of type Enumerated. It shall indicate if the service is barred or granted. The following values are defined: + +SERVICE\_GRANTED (0) + +OPERATOR\_DETERMINED\_BARRING (1) + +### 7.3.30 Operator-Determined-Barring + +The Operator-Determined-Barring AVP is of type Unsigned32 and it shall contain a bit mask indicating the services of a subscriber that are barred by the operator. The meaning of the bits is the following: + +**Table 7.3.30/1: Operator-Determined-Barring** + +| Bit | Description | +|-----|--------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | All Packet Oriented Services Barred | +| 1 | Roamer Access HPLMN-AP Barred | +| 2 | Roamer Access to VPLMN-AP Barred | +| 3 | Barrying of all outgoing calls | +| 4 | Barrying of all outgoing international calls | +| 5 | Barrying of all outgoing international calls except those directed to the home PLMN country | +| 6 | Barrying of all outgoing inter-zonal calls | +| 7 | Barrying of all outgoing inter-zonal calls except those directed to the home PLMN country | +| 8 | Barrying of all outgoing international calls except those directed to the home PLMN country and Barrying of all outgoing inter-zonal calls | + +### 7.3.31 Access-Restriction-Data + +The Access-Restriction-Data AVP is of type Unsigned32 and it shall contain a bit mask where each bit when set to 1 indicates a restriction. The meaning of the bits is the following: + +**Table 7.3.31/1: Access-Restriction-Data** + +| Bit | Description | +|-------------------------------------------------------------------------------------------------------------|--------------------------------------------------| +| 0 | UTRAN Not Allowed | +| 1 | GERAN Not Allowed | +| 2 | GAN Not Allowed | +| 3 | I-HSPA-Evolution Not Allowed | +| 4 | WB-E-UTRAN Not Allowed | +| 5 | HO-To-Non-3GPP-Access Not Allowed | +| 6 | NB-IoT Not Allowed | +| 7 | Enhanced Coverage Not Allowed | +| 8 | NR as Secondary RAT in E-UTRAN Not Allowed | +| 9 | Unlicensed Spectrum as Secondary RAT Not Allowed | +| 10 | NR in 5GS Not Allowed | +| 11 | LTE-M Not Allowed | +| 12 | WB-E-UTRAN Except LTE-M Not Allowed | +| NOTE 1: Bits not defined in this table shall be cleared by the HSS and discarded by the receiving MME/SGSN. | | +| NOTE 2: Bits 11 and 12 are only used when bit 4 is not set. | | + +The restriction "HO-To-Non-3GPP-Access Not Allowed" shall take a higher precedence than the APN-level parameter "WLAN-Offloadability" (see clause 7.3.181). + +### 7.3.32 APN-OI-Replacement + +The APN-OI-Replacement AVP is of type UTF8String. This AVP shall indicate the domain name to replace the APN OI for the non-roaming case and the home routed roaming case when constructing the APN, and the APN-FQDN upon which to perform a DNS resolution. See 3GPP TS 23.003 [3] and 3GPP TS 29.303 [38]. + +The contents of the APN-OI-Replacement AVP shall be formatted as a character string composed of one or more labels separated by dots ("."). + +### 7.3.33 All-APN-Configurations-Included-Indicator + +The All-APN-Configurations-Included-Indicator AVP is of type Enumerated. The following values are defined: + +ALL\_APN\_CONFIGURATIONS\_INCLUDED (0) + +MODIFIED\_ADDED\_APN\_CONFIGURATIONS\_INCLUDED (1) + +### 7.3.34 APN-Configuration-Profile + +The APN-Configuration-Profile AVP is of type Grouped. It shall contain the information related to the user's subscribed APN configurations for EPS. + +The AVP format shall conform to: + +``` +APN-Configuration-Profile ::=
This bit, when cleared, indicates that the NOR message is sent on the S6d interface, i.e. the message is from the SGSN or the SGSN part on the combined MME/SGSN. | +| 9 | Removal of MME Registration for SMS | This bit, when set, shall indicate that the MME requests to remove its registration for SMS. | +| NOTE 1: The S6a/S6d-Indicator flag shall be used together with Homogeneous Support of IMS Voice Over PS Sessions flag, i.e. if the Homogeneous Support of IMS Voice Over PS Sessions bit is set, the S6a/S6d-Indicator bit shall be set if the message is sent from the MME or the MME part on the combined MME/SGSN, and shall be cleared if the message is sent from the SGSN or the SGSN part on the combined MME/SGSN. This S6a/S6d-Indicator bit shall be discarded by the receiving HSS if the Homogeneous Support of IMS Voice Over PS Sessions bit is not set. | | | +| NOTE 2: Bits not defined in this table shall be cleared by the sending MME or SGSN and discarded by the receiving HSS. | | | + +### 7.3.50 User-Id + +The User-Id AVP shall be of type UTF8String. It shall contain the leading digits of an IMSI (i.e. MCC, MNC, leading digits of MSIN, see 3GPP TS 23.003 [3], clause 2.2) formatted as a character string. Within a HSS, a User-Id identifies a set of subscribers, each with identical leading IMSI digits. + +### 7.3.51 Equipment-Status + +The Equipment-Status AVP is of type Enumerated, and shall contain the status of the mobile equipment. The following values are defined: + +WHITELISTED (0) + +BLACKLISTED (1) + +GREYLISTED (2) + +### 7.3.52 Regional-Subscription-Zone-Code + +The Regional-Subscription-Zone-Code AVP is of type OctetString. It shall contain a Zone Code (ZC) as defined in 3GPP TS 23.003 [3], clause 4.4. Up to 10 Zone Codes per VPLMN can be defined as part of the user's subscription data. + +NOTE 1: Each zone code represents a collection of tracking area or routing areas (defined by the operator of the VPLMN) where the user is allowed, or disallowed, to roam. The determination of which areas are actually allowed, and which ones are not allowed, is done by the serving node (MME/SGSN) in an implementation-dependent manner. + +NOTE 2: The description of RSZI in 3GPP TS 23.003 [3] is applicable, in the context of this specification, not only to location areas, but also to routing and tracking areas. + +### 7.3.53 RAND + +The RAND AVP is of type OctetString. This AVP shall contain the RAND. See 3GPP TS 33.401 [5]. + +### 7.3.54 XRES + +The XRES AVP is of type OctetString. This AVP shall contain the XRES. See 3GPP TS 33.401 [5]. + +### 7.3.55 AUTN + +The AUTN AVP is of type OctetString. This AVP shall contain the AUTN. See 3GPP TS 33.401 [5]. + +### 7.3.56 KASME + +The KASME AVP is of type OctetString. This AVP shall contain the K\_ASME. See 3GPP TS 33.401 [5]. + +### 7.3.57 Confidentiality-Key AVP + +The Confidentiality-Key is of type OctetString, and shall contain the Confidentiality Key (CK). + +### 7.3.58 Integrity-Key AVP + +The Integrity-Key is of type OctetString, and shall contain the Integrity Key (IK). + +### 7.3.59 Kc AVP + +The Kc AVP is of type OctetString, and shall contain the Ciphering Key (Kc). + +### 7.3.60 SRES + +The SRES AVP is of type OctetString. This AVP shall contain the SRES. See 3GPP TS 33.102 [18]. + +### 7.3.61 Void + +### 7.3.62 PDN-Type + +The PDN-Type AVP is of type Enumerated and indicates the address type of the PDN, when it is IP-based. + +NOTE: There are certain PDNs that can be accessed without using IP. These are identified by a specific PDN type indicator in their APN configuration settings (e.g. see clauses 7.3.204 and 7.3.232). + +The following values are defined: + +IPv4 (0) + +This value shall be used to indicate that the PDN can be accessed only in IPv4 mode. + +IPv6 (1) + +This value shall be used to indicate that the PDN can be accessed only in IPv6 mode. + +IPv4v6 (2) + +This value shall be used to indicate that the PDN can be accessed both in IPv4 mode, in IPv6 mode, and also from UEs supporting dualstack IPv4v6. + +IPv4\_OR\_IPv6 (3) + +This value shall be used to indicate that the PDN can be accessed either in IPv4 mode, or in IPv6 mode, but not from UEs supporting dualstack IPv4v6. It should be noted that this value will never be used as a requested PDN Type from the UE, since UEs will only use one of their supported PDN Types, i.e., IPv4 only, IPv6 only or IPv4v6 (dualstack). This value is only used as part of the APN subscription context, as an authorization mechanism between HSS and MME. + +### 7.3.63 Trace-Data AVP + +The Trace-Data AVP is of type Grouped. This AVP shall contain the information related to trace function. + +AVP format + +Trace-Data ::=