hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
4.3.2.5 Platform adaptation requirements
|
For the execution of this test suite implementations of the following external functions have to be provided (cp. module LibSip_Steps): 1) rndStr() return charstring; returns a random charstring; 2) putInLowercase(charstring par_string) return charstring; returns the equivalent string in lower case; 3) getIpAddr(charstring host_name) return charstring; resolves a domain name to its equivalent IPv4 address; ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 15 4) calculateDigestResponse(charstring nonce, charstring cnonce, charstring user, charstring realm, charstring passwd, charstring alg, charstring nonceCount, charstring method, charstring qop, charstring URI, charstring HEntity) return charstring; generates a digest response according to RFC 2617 [13] (HTTP Authentication: Basic and Digest Access Authentication), and RFC 1321 [14] The MD5 Message-Digest Algorithm. (See RFC 2617 [13], chapter 5 Sample implementation, for example usage, as the signature of calculateDigestResponse is according to the example given in the RFC.)
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
5 The ATS development process
| |
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
5.1 Requirements and Test Purposes
|
For each test purpose there is a table defined in clause 6 of TS 186 001-3 [9]. The requirements applicable to this TP are given by a reference to RFC 3261 [2] (SIP) or ES 283 003 [1]. There are no explicit formulations of requirements.
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
5.2 ATS structure
| |
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
5.2.1 Test case grouping
|
The ATS structure defined in table 4 is based on the structuring of Test Purposes in clause 5 of TS 186 001-3 [9]. The group names in columns 1 to 2 of table 4 are those assigned in the ATS; they are based on the names provided in clause 5 of TS 186 001-3 [9], but use the naming conventions defined for the ATS (see clause 5.3.2.2). Table 4: ATS structure C – Plane / U – Plane Basic_Call Successful Normal call establishment SS___XX___xx Codec negotiation SS___CN___xx UPDATE SS___XX__UP__xx Unsuccessful SS___XX__Uxx Supplementary_Services OIP SS___XXSS_OIPxx OIR SS___XXSS_OIRxx TIP SS___XXSS_TIPxx TIR SS___XXSS_TIRxx HOLD SS___XXSS_CHxx CDIV CFU SS___XXSS_CFUxx CFB SS___XXSS_CFBxx CFNR SS___XXSS_CFNRxx CFNRc SS___XXSS_CFNRcxx CFNL SS___XXSS_CFNLxx CD SS___XXSS_CDxx CONF CONF_CRE SS___XXSS_CONF_CRExx CONF_IN SS___XXSS_CONF_INVxx CONF_LEAV SS___XXSS_CONF_LEAVxx CONF_REMOV SS___XXSS_CONF_REMOVxx CW SS___XXSS_CWxx CCBS SS___XXSS_CCBSxx CCNR SS___XXSS_CCNRxx ECT SS___XXSS_ECT ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 16
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
5.2.2 Test case identifiers
|
The test case names are built up according to the following scheme: Table 5: TC identifier naming convention scheme Identifier: TC_SS_<tp_name> SS = Supplementary Services < tp_name> = Test Purpose Name as defined in the test purpose doc
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
5.3 ATS specification framework
| |
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
5.3.1 ATS Library
|
For this ATS the TTCN-3 library modules are basically organized as: 1) SIP/IMS modules; 2) SIP Common modules (RFC 3261 [2]); 3) LibCommon modules (taken from an improved version of TS 102 351 [11]). Table 6 shows the organisation of the ATS as library of modules. ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 17 Table 6: Library of modules Module Class Module Id Description LibCommon LibCommon_AbstractData Generic data types for a stack and its operations LibCommon_BasicTypesAndValues Basic type and value definitions (integer and Boolean) LibCommon_DataStrings Bit and Octet string types LibCommon_Sync Co-ordination/synchronization of test components LibCommon_TextStrings Basic character and string types with fixed length LibCommon_Time Time handling functions and module parameter LibCommon_VerdictControl Basic functions for setting of test component verdicts LibIms LibIms_PIXITS IMS specific common Module Parameter (e.g. addresses related to SUT components and TS) declarations associated with PIXIT LibIms_Interface IMS component (see note) LibIms_SIPTypesAndValues IMS specific user and interface specific profile data (see note) LibIms_Templates Modified templates with IMS specific header fields LibIms_Steps functions using IMS specific types LibSip LibSip_PIXITS SIP general common Module Parameter (e.g. SDP/SIP procedure options) declarations associated with PIXIT LibSip_Interface SIP component LibSip_SIPTypesAndValues SIP message types and constants, simple user profiles (see note) LibSip_SDPTypes SDP types and constants LibSip_Templates Basic and modified templates with SIP specific header fields LibSip_Steps SIP specific behaviour function library LibSip_XMLTypes XML type system for SIP tests XSDAUX ASN.1 base type definitions AtsNIT_SipSip AtsNIT_SipSip_BC_TCFunctions TC functions used by the test component for Basic Call AtsNIT_SipSip_PICS Module Parameter declarations associated with PICS AtsNIT_SipSip_PIXITS Module Parameter declarations associated with PIXIT AtsNIT_SipSip_SS_TCFunctions TC functions used by the test component for supplementary services AtsNIT_SipSip_Steps Module specific behaviour function library AtsNIT_SipSip_Testcases Test case definitions for the complete module AtsNIT_SipSip_TestConfiguration Functions for mapping of test components to help setup and tear down different test configurations and configuration of the SUT adapter AtsNIT_SipSip_TestExecution Module control: execute test cases depending on selection conditions AtsNIT_SipSip_TestSystem TSI components, test system internal ports NOTE: In order to build a comprehensive library all SIP message header (incl. IMS specific) have been defined in LibSip_SIPTypesAndValues only.
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
5.3.2 Use of TTCN-3
| |
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
5.3.2.1 General
|
TTCN-3 as defined in ES 201 873-1 [6] is used as ATS specification language. A number of requirements have been identified for the development and production of the TTCN-3 specification for the SIP IMS ATS: 1) Top-down design. 2) A uniquely defined testing architecture and test method. 3) Uniform TTCN-3 style and naming conventions. 4) TTCN-3 is human-readable. 5) TTCN-3 specification is feasible, implementable, compilable and maintainable. 6) Test cases shall be designed in a way to be easily adaptable, upwards compatible with the evolution of the base protocol and protocol interworking of future releases. ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 18 7) The test declarations, data structures and data values shall be largely reusable. 8) Modularity and modular working method. 9) Minimizing the requirements of intelligence on the emulators of the lower testers. 10) Giving enough design freedom to the test equipment manufacturers. Fulfilling these requirements should ensure the investment of the test equipment manufacturers and users of the ATS having stable testing means for a relatively long period.
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
5.3.2.2 TTCN-3 naming conventions
|
Like in other software projects using a programming language, the use of naming conventions supports or increases: a) the readability; b) the detection of semantic errors; c) the shared work of several developers; d) the maintainability. The naming conventions applied to the SIP/IMS ATS are based on the following underlying principles: • when constructing meaningful identifiers, the general guidelines specified for naming in EG 202 568 [12], clause 8 should be followed; • the names of TTCN-3 objects being associated with standardized data types (e.g. in the base protocols) should reflect the names of these data types as close as possible (of course not conflicting with syntactical requirements or other conventions being explicitly stated); • the subfield names of TTCN-3 objects being associated with standardized data type should also be similar to corresponding element names in the base standards (be recognizable in the local context); • in most other cases, identifiers should be prefixed with a short alphabetic string (specified in table 3) indicating the type of TTCN-3 element it represents; • prefixes should be separated from the body of the identifier with an underscore ("_"); • only test case names, module names, data type names and module parameters should begin with an upper-case letter. All other names (i.e. the part of the identifier following the prefix) should begin with a lower-case letter. Table 7 specifies the naming guidelines for each element of the TTCN-3 language indicating the recommended prefix and capitalization. ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 19 Table 7: TTCN-3 naming conventions Language element Naming convention Prefix Example Notes Module Use upper-case initial letter none IPv6Templates TSS grouping Use all upper-case letters as specified in clause 7.1.2.1.1 none TP_RT_PS_TR Item group within a module Use lower-case initial letter none messageGroup SIP message type Use upper-case initial letter none Request, Response See note 1 SIP header type Use upper-case initial letter none MaxForwards See note 1 Basic common data types (e.g. bit string types of fixed length) Use upper-case initial letter none Take from common module Other Data types Use upper-case initial letter none SetupContents Signature template Use lower-case initial letter s_ s_callSignature Port instance Use lower-case initial letter none signallingPort Test component ref Use lower-case initial letter none userTerminal Constant Use lower-case initial letter c_ c_maxRetransmission External constant Use lower-case initial letter cx_ cx_macId Function Use lower-case initial letter f_ f_authentication() External function Use lower-case initial letter fx_ fx_calculateLength() Altstep (incl. Default) Use lower-case initial letter a_ a_receiveSetup() Test case Use naming as specified in clause 5.2.2 TC_ TC_IMST2_xxxxx Variable (local) Use lower-case initial letter v_ v_macId Variable (defined within a component) Use lower-case initial letters vc_ vc_systemName Timer (local) Use lower-case initial letter t_ t_wait Timer (defined within a component) Use lower-case initial letters tc_ tc_authMin Module parameter Use initial upper case letters PX PX_MAC_ID See note 2 Parameterization Use lower-case initial letter p_ p_macId Enumerated Value Use lower-case initial letter e_ e_syncOk NOTE 1: This convention has been used in TS 102 027-3 [10] (SIP ATS). NOTE 2: In this case it is acceptable to use underscore as a word delimiter.
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
5.3.2.3 Additional TTCN-3 IMS/SIP naming convention
|
In addition to the general TTCN-3 naming conventions listed in clause 5.3.2.2, the following rules have been applied to templates. Table 8: TTCN-3 naming conventions Language element Naming convention Prefix Example Notes Message template Use lower-case initial letter, followed by message type in upper-case letters (for requests) or "Response" keyword m_ m_BYE_Request_UE Message template with wildcard or matching expression Use lower-case initial letters mw_ mw_SUBSCRIBE_Request_IMS Templates have been defined in a 3-step approach. First, a dummy template is defined for every message type and direction, e.g. m_ACK_Dummy and mw_ACK_Dummy. Secondly, for each message type and direction a base template has been defined that respective dummy templates and includes all mandatory header fields. Template identifiers of this modifications include the keyword "Base", e.g. m_ACK_Request_Base, mw_ACK_Request_Base. More specific templates are then derived on the basis of these base templates and modify fields that need to be restricted for a very speicifc purpose, e.g. m_ACK_Request_route etc. ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 20
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
5.3.2.4 Additional concepts and conventions
|
IMS procedures and tests requires the inclusion of user identification and network address information in SIP messages. Since this information depends on the specific SUT at hand it is defined using module parameters. Due to the big amount of such parameters a profile concept have been introduced for particular parameter collections (records) that are related to IMS users and interfaces. The so-called user profile information (cp. module LibSip_SIPTypesAndValue) contains the following elements: userprofile identifier, current IP port and address to exchange SIP messages, IP port and address for further contact, IP address used by the TS to exchange media streams, public identity (home domain, username), quality-of-protection parameters, authentication parameters (RFC 2617 [13], clause 3.2.2). A list of user profile identifiers (module LibIMS_SIPTypesAndValue) introduces available settings for UE with different locations and homes: e.g. c_userProfile_UE1atSUThome should be used in case where UE1 is a registered user of SUT and currently not visiting another IMS. User profiles are construced from module parameters (cp. module LibIMS_Steps). Additionally some interface information is needed to indicate or validate IMS component addresses to be used in SIP header fields like Via, Route, etc. They are defined in a similar way as user profiles (cp. LibIms_SIPTypeAndValues) and contain IP address, port and domain information.
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
5.3.2.5 PICS information
|
A TTCN-3 control part has been defined for this test suite. If applicable PICS information is evaluated at the begining of each test case definition using an "if" statement. Log information is provided in case that a test has not been executed due to PICS setting violation.
|
c45631e0028c3d0fb8d0af05c5209d8c
|
186 001-4
|
5.3.2.6 Test Suite documentation
|
In order to allow browsing of the SIP/IMS ATS without the use of a specific TTCN-3 test development environment, the TTCN ATS is made available in HTML format with hyperlinks between entities in the ATS. The documentation in the ATS makes use of special comment tags used by the tool that converts the ATS to the HTML format. These tags are defined in clause 9 of ES 201 873-6 [8] and the tags are shown in table 9. Table 9: TTCN-3 comment tags Tag Description @author Specifies the names of the authors or an authoring organization which either has created or is maintaining a particular piece of TTCN-3 code. @desc Describes the purpose of a particular piece of TTCN-3 code. The description should be concise yet informative and describe the function and use of the construct. @remark Adds extra information, such as the highlighting of a particular feature or aspect not covered in the description. @img Associates images with a particular piece of TTCN-3 code. @see Refers to other TTCN-3 definitions in the same or another module. @url Associates references to external files or web pages with a particular piece of TTCN-3 code, e.g. a protocol specification or standard. @return Provides additional information on the value returned by a given function. @param Documents the parameters of parameterized TTCN-3 definitions. @version States the version of a particular piece of TTCN-3 code. ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 21 Annex A (normative): Partial PIXIT proforma Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the PIXIT proforma in this annex so that it can be used for its intended purposes and may further publish the completed PIXIT proforma. A.1 Introduction This partial PIXIT proforma contained in the present document is provided for completion, when the related Abstract Test Suite is to be used against the Implementation Under Test (IUT). The completed partial PIXIT will normally be used in conjunction with the completed PICS, as it adds precision to the information provided by the PICS. A.2 PIXIT items According to the interworking type of ATS defined in the present document, the PIXIT are divided in SIP-related PIXIT and IMS-related PIXIT. NOTE: The tables in clause A.2 have been generated automatically from the TTCN-3 modules. A.2.1 SIP-related PIXIT Each PIXIT item corresponds to a Module Parameter of the ATS. NOTE: The SIP-related PIXIT definitions are part of a SIP TTCN-3 library that contains additional PIXIT definitions on SIP and TS address information that are not used in this ATS and therefore not present in table A.1. ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 22 Table A.1: SIP-related PIXIT items No PIXIT Name Description 1 PX_SIP_SDP_dyn charstring for SDP dynamic port 2 PX_SIP_SDP_b_modifier charstring for SDP bandwidth modifier 3 PX_SIP_SDP_b_bandwidth integer for SDP bandwidth value 4 PX_SIP_SDP_encoding charstring for SDP media attribute encoding supported by the IUT 5 PX_SIP_TRANSPORT charstring for Used Transport in upper case "UDP"/"TCP" 6 PX_SIP_SUT_PORT integer for SUT port number to exchange SIP messages 7 PX_SIP_SUT_IPADDR charstring for SUT IP address to exchange SIP messages 8 PX_SIP_TS1_PORT integer for port number used by the TS1 to exchange SIP messages 9 PX_SIP_TS1_IPADDR charstring for IP address used by the TS1 to exchange SIP messages 10 PX_SIP_TS1_LOCAL_DOMAIN charstring for identity of the tester local domain 11 PX_SIP_TS1_LOCAL_USER charstring for identity of the tester local user 12 PX_SIP_TS1_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams 13 PX_SIP_TS2_PORT integer for port number used by the TS2 to exchange SIP messages 14 PX_SIP_TS2_IPADDR charstring for IP address used by the TS2 to exchange SIP messages 15 PX_SIP_TS2_LOCAL_DOMAIN charstring for identity of the tester local domain 16 PX_SIP_TS2_LOCAL_USER charstring for identity of the tester local user 17 PX_SIP_TS2_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams 18 PX_SIP_REGISTRATION boolean for the SIP user if it have to register itself before executing a test case 19 PX_SIP_SUT_REGISTRAR_DOMAIN charstring for REGISTRAR domain 20 PX_SIP_CheckConversation boolean for True, if conversation check is implemented. 21 PX_SIP_REGISTER_AUTHENTICATION_ENABLED boolean for option controlling if authentication is enabled/disabled for REGISTER messages 22 PX_SIP_INVITE_AUTHENTICATION_ENABLED boolean for option controlling if authentication is enabled/disabled for INVITE messages 23 PX_SIP_SUT_UE1_QOP charstring for RFC 2617 [13], clause 3.2.1 qop options: Quoted string of one or more tokens indicating the "quality of protection" values supported by the server. The value"auth" indicates authentication; the value "auth-int" indicates authentication with integrity protection 24 PX_SIP_SUT_UE1_USERNAME charstring for RFC 2617 [13], clause 3.2.2 username: The name of user in the specified realm 25 PX_SIP_SUT_UE1_PASSWD charstring for RFC 2617 [13], clause 3.2.2.2 passwd: A known shared secret, the password of user of the specified username 26 PX_SIP_SUT_UE2_QOP charstring for RFC 2617 [13], clause 3.2.1 qop options: Quoted string of one or more tokens indicating the "quality of protection" values supported by the server. The value"auth" indicates authentication; the value "auth-int" indicates authentication with integrity protection. 27 PX_SIP_SUT_UE2_USERNAME charstring for RFC 2617 [13], clause 3.2.2 username: The name of user in the specified realm 28 PX_SIP_SUT_UE2_PASSWD charstring for RFC 2617 [13], clause 3.2.2.2 passwd: A known shared secret, the password of user of the specified username 29 PX_SIP_T1 float for T1 RTT estimate (500 ms) 30 PX_SIP_TF float for TDELAY default value for timeout on outgoing SIP request (ie 64*T1) 31 PX_SIP_TWAIT float for TWait default value for waiting an operator action 32 PX_SIP_TACK float for TAck default value for waiting an acknowledgement ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 23 No PIXIT Name Description 33 PX_SIP_TRESP float for TResp default value for waiting for a response from the IUT 34 PX_SIP_TNOACT float for TNoAct default value for waiting no message from the IUT Value given for PX_TNOACT should be less than value of SHORT_REGISTRATION constant (which is currently "3" (seconds)) 35 PX_SIP_TGUARD float for TGUARD default value for an extra long timer to limit test execution A.2.2 IMS-related PIXIT Each PIXIT item corresponds to a Module Parameter of the ATS. NOTE: The IMS-related PIXIT definitions are part of a IMS TTCN-3 library that contains additional PIXIT definitions on IMS that are not used in this ATS and therefore not present table A.2. Table A.2: IMS-related PIXIT items No PIXIT Name Description 1 PX_IMS_SUT_PCSCF1_IPADDR charstring for SUT - PCSCF1 IP address to exchange SIP messages - connection point for UE1 2 PX_IMS_SUT_PCSCF1_PORT integer for SUT - PCSCF1 port number to exchange SIP messages - connection point for UE1 3 PX_IMS_SUT_PCSCF1_HOME_DOMAIN charstring for SUT/PCSCF1 domain - connection point for UE1 4 PX_IMS_SUT_UE1_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams for UE1 5 PX_IMS_SUT_UE1_HOME_DOMAIN charstring for identity of the tester UE1 local domain 6 PX_IMS_SUT_UE1_PUBLIC_USER charstring for identity of the tester UE1 local user 7 PX_IMS_SUT_UE1_PRIVAT_USERNAME charstring for RFC 2617 [13], clause 3.2.2 username of UE1: The name of user in the specified realm 8 PX_IMS_SUT_UE1_PRIVAT_PASSWD charstring for RFC 2617 [13], clause 3.2.2.2 passwd of UE1: A known shared secret, the password of user of the specified username 9 PX_IMS_SUT_UE1_QOP charstring for RFC 2617 [13], clause 3.2.1 qop options of UE1: Quoted string of one or more tokens indicating the "quality of protection" values supported by the server; the value "auth" indicates authentication; the value "auth-int" indicates authentication with integrity protection 10 PX_IMS_SUT_UE1_REGISTRAR charstring for home(SUT) REGISTRAR domain of UE1 11 PX_IMS_SUT_PCSCF2_IPADDR charstring for SUT - PCSCF2 IP address to exchange SIP messages - connection point for UE2 12 PX_IMS_SUT_PCSCF2_PORT integer for SUT - PCSCF2 port number to exchange SIP messages - connection point for UE2 13 PX_IMS_SUT_PCSCF2_HOME_DOMAIN charstring for SUT/PCSCF2 domain - connection point for UE2 14 PX_IMS_SUT_UE2_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams for UE2 15 PX_IMS_SUT_UE2_HOME_DOMAIN charstring for identity of the tester UE2 local domain 16 PX_IMS_SUT_UE2_PUBLIC_USER charstring for identity of the tester UE2 local user 17 PX_IMS_SUT_UE2_PRIVAT_USERNAME charstring for RFC 2617 [13], clause 3.2.2 username of UE2: The name of user in the specified realm 18 PX_IMS_SUT_UE2_PRIVAT_PASSWD charstring for RFC 2617 [13], clause 3.2.2.2 passwd: A known shared secret, the password of user of the specified username of UE2 19 PX_IMS_SUT_UE2_QOP charstring for RFC 2617 [13], clause 3.2.1 qop options UE2: Quoted string of one or more tokens indicating the "quality of protection" values supported by the server, the value "auth" indicates authentication; the value "auth-int" indicates authentication with integrity protection ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 24 No PIXIT Name Description 20 PX_IMS_SUT_UE2_REGISTRAR charstring for home(SUT) REGISTRAR domain of UE2 21 PX_IMS_SUT_UE3_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams for UE3 22 PX_IMS_SUT_UE3_HOME_DOMAIN charstring for identity of the tester UE2 local domain 23 PX_IMS_SUT_UE3_PUBLIC_USER charstring for identity of the tester UE3 local user 24 PX_IMS_SUT_UE3_PRIVAT_USERNAME charstring for RFC 2617 [13], clause 3.2.2 username of UE3: The name of user in the specified realm 25 PX_IMS_SUT_UE3_PRIVAT_PASSWD charstring for RFC 2617 [13], clause 3.2.2.2 passwd: A known shared secret, the password of user of the specified username of UE3 26 PX_IMS_SUT_UE3_QOP charstring for RFC 2617 [13], clause 3.2.1 qop options UE3: Quoted string of one or more tokens indicating the "quality of protection" values supported by the server, the value "auth" indicates authentication; the value "auth-int" indicates authentication with integrity protection 27 PX_IMS_SUT_UE3_REGISTRAR charstring for home(SUT) REGISTRAR domain of UE3 28 PX_IMS_SUT_UE4_BEARER_IPADDR charstring for IP address used by the TS to exchange media streams for UE4 29 PX_IMS_SUT_UE4_HOME_DOMAIN charstring for identity of the tester UE2 local domain 30 PX_IMS_SUT_UE4_PUBLIC_USER charstring for identity of the tester UE4 local user 31 PX_IMS_SUT_UE4_PRIVAT_USERNAME charstring for RFC 2617 [13], clause 3.2.2 username of UE4: The name of user in the specified realm 32 PX_IMS_SUT_UE4_PRIVAT_PASSWD charstring for RFC 2617 [13], clause 3.2.2.2 passwd: A known shared secret, the password of user of the specified username of UE2 33 PX_IMS_SUT_UE4_QOP charstring for RFC 2617 [13], clause 3.2.1 qop options UE4: Quoted string of one or more tokens indicating the "quality of protection" values supported by the server, the value "auth" indicates authentication; the value "auth-int" indicates authentication with integrity protection 34 PX_IMS_SUT_UE4_REGISTRAR charstring for home(SUT) REGISTRAR domain of UE4 35 PX_IMS_SUT_unknownUE_PUBLIC_USER charstring for identity of unknown UE public user 36 PX_IMS_SUT_EMERGENCY_HOME_DOMAIN charstring for identity of emergency service local domain 37 PX_IMS_SUT_EMERGENCY_SERVICE charstring for identity of the emergency service 38 PX_IMS_SUT_EMERGENCY_SERVICE_INVALID charstring for identity of the invalid emergency service 39 PX_IMS_SUT_IBCF1_IPADDR charstring for SUT/IBCF1 IP address to exchange SIP messages 40 PX_IMS_SUT_IBCF1_PORT integer for SUT/IBCF1 port number to exchange SIP messages 41 PX_IMS_SUT_IBCF1_HOME_DOMAIN charstring for SUT/IBCF1 domain 42 PX_IMS_SUT_IBCF2_IPADDR charstring for SUT/IBCF2 IP address to exchange SIP messages 43 PX_IMS_SUT_IBCF2_PORT integer for SUT/IBCF2 port number to exchange SIP messages 44 PX_IMS_SUT_IBCF2_HOME_DOMAIN charstring for SUT/IBCF2 domain 45 PX_IMS_SUT_PCSCF_IPADDR charstring for SUT/P-CSCF IP address to exchange SIP messages 46 PX_IMS_SUT_PCSCF_PORT integer for SUT/P-CSCF port number to exchange SIP messages 47 PX_IMS_SUT_PCSCF_HOME_DOMAIN charstring for SUT/P-CSCFdomain 48 PX_IMS_SUT_SCSCF_IPADDR charstring for SUT/S-CSCF IP address to exchange SIP messages 49 PX_IMS_SUT_SCSCF_PORT integer for SUT/S-CSCF port number to exchange SIP messages 50 PX_IMS_SUT_SCSCF_HOME_DOMAIN charstring for SUT/S-CSCFdomain 51 PX_IMS_SUT_ICSCF_IPADDR charstring for SUT/I-CSCF IP address to exchange SIP messages 52 PX_IMS_SUT_ICSCF_PORT integer for SUT/I-CSCF port number to exchange SIP messages 53 PX_IMS_SUT_ICSCF_HOME_DOMAIN charstring for SUT/I-CSCFdomain ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 25 No PIXIT Name Description 54 PX_IMS_SUT_AS_IPADDR charstring for SUT - AS IP address to exchange SIP messages - connection point for SCSCF 55 PX_IMS_SUT_AS_PORT integer for SUT - AS port number to exchange SIP messages - connection point for SCSCF 56 PX_IMS_SUT_AS_HOME_DOMAIN charstring for SUT/AS domain 57 PX_IMS_SUT_IMGCF_IPADDR charstring for SUT/I-MGCF IP address to exchange SIP messages 58 PX_IMS_SUT_IMGCF_PORT integer for SUT/I-MGCF port number to exchange SIP messages 59 PX_IMS_SUT_IMGCF_HOME_DOMAIN charstring for SUT/I-MGCFdomain 60 PX_IMS_SUT_CONF_PORT integer for SUT/conference port number to exchange SIP messages 61 PX_IMS_SUT_CONF_HOME_DOMAIN charstring for SUT/conference domain 62 PX_IMS_SUT_CONF_FACTORY_NAME charstring for conference factory URI name 63 PX_IMS_TS_UE1_IPADDR charstring for IP address used by the UE1 to exchange SIP messages 64 PX_IMS_TS_UE1_PORT integer for port number used by the UE1 to exchange SIP messages 65 PX_IMS_TS_UE2_IPADDR charstring for IP address used by the UE2 to exchange SIP messages 66 PX_IMS_TS_UE2_PORT integer for port number used by the UE2 to exchange SIP messages 67 PX_IMS_TS_UE3_IPADDR charstring for IP address used by the UE3 to exchange SIP messages 68 PX_IMS_TS_UE3_PORT integer for port number used by the UE3 to exchange SIP messages 69 PX_IMS_TS_UE4_IPADDR charstring for IP address used by the UE3 to exchange SIP messages 70 PX_IMS_TS_UE4_PORT integer for port number used by the UE3 to exchange SIP messages 71 PX_IMS_TS_IBCF_IPADDR charstring for TS/IBCF IP address to exchange SIP messages 72 PX_IMS_TS_IBCF_PORT integer for TS/IBCF port number to exchange SIP messages 73 PX_IMS_TS_ICSCF_IPADDR charstring for TS/I-CSCF IP address to exchange SIP messages 74 PX_IMS_TS_ICSCF_PORT integer for IUT/I-CSCF port number to exchange SIP messages 75 PX_IMS_TS_PCSCF_IPADDR charstring for TS/P-CSCF IP address to exchange SIP messages 76 PX_IMS_TS_PCSCF_PORT integer for IUT/P-CSCF port number to exchange SIP messages 77 PX_IMS_TS_PCSCF_HOME_DOMAIN charstring for TS/P-CSCFdomain 78 PX_IMS_TS_SCSCF_IPADDR charstring for TS/S-CSCF IP address to exchange SIP messages 79 PX_IMS_TS_SCSCF_PORT integer for TS/S-CSCF port number to exchange SIP messages 80 PX_IMS_TS_SCSCF_HOME_DOMAIN charstring for TS/S-CSCFdomain 81 PX_IMS_TS_ECSCF_IPADDR charstring for TS/E-CSCF IP address to exchange SIP messages 82 PX_IMS_TS_ECSCF_PORT integer for TS/E-CSCF port number to exchange SIP messages 83 PX_IMS_TS_IMS1UE_PUBLIC_USER charstring for public userinfo/displayname addressing IMS1UE (simulated by the TS) 84 PX_IMS_TS_IMS1UE_HOME_DOMAIN charstring for TS/domain 85 PX_IMS_TS_ISUP_PUBLIC_USER charstring for public userinfo addressing ISUPUE (simulated by the TS) 86 PX_IMS_TS_ISUP_HOME_DOMAIN charstring for ISUP TS/domain or IPAddres 87 PX_IMS_TS_AS1_IPADDR charstring for TS/AS1 IP address to exchange SIP messages 88 PX_IMS_TS_AS1_PORT integer for TS/AS1 port number to exchange SIP messages 89 PX_IMS_TS_AS1_HOME_DOMAIN charstring for TS/AS1 domain ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 26 No PIXIT Name Description 90 PX_IMS_TS_AS2_IPADDR charstring for TS/AS2 IP address to exchange SIP messages 91 PX_IMS_TS_AS2_PORT integer for TS/AS2 port number to exchange SIP messages 92 PX_IMS_TS_AS2_HOME_DOMAIN charstring for TS/AS2 domain A.2.3 ATS-related PIXIT Each PIXIT item corresponds to a Module Parameter of the ATS. Table A.3: NIT ATS specific PIXIT items No PIXIT Name Description 1 PX_SIP_Tnr float default value for No reply timer (TS 124 504 [i.1], clause 4.8.1) 2 PX_UE2_HI_index record of integer default value for HistoryInfo index of UE2 node 3 PX_UE3_HI_index record of integer default value for HistoryInfo index of UE3 node ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 27 Annex B (informative): TTCN-3 library modules The TTCN-3 library modules are contained in archive ts_18600104v020201p0.zip which accompanies the present document. NOTE: The TTCN-3 code contained in LibCommon, LibSIP and LibIMS is shared with other STFs. ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 28 History Document history V2.2.1 September 2010 Publication
|
f867071dbea0e55b4369d86f8f5971d1
|
184 006
|
1 Scope
|
The present document analyzes the issues concerned with interconnection and routeing in NGN and their implications and requirements for numbering, naming and addressing and related resolution functionalities. Several different interconnection scenarios are considered, based on TISPAN "NGN Functional Architecture" ([5]), although not all require the use of all architectural functions. The role of the transit network has also been considered in order to evaluate the knowledge of numbers/names served by different operators and related requirements for routing purposes. Some scenarios may require the availability of infrastructure systems for numbering/naming resolutions, such as infrastructure ENUM, or other database based system for route resolution, and may require coordinated provision by involved operators. The present document focuses on calls routed between subscribers identified by E.164 numbers, coded through either tel URI and SIP URI formats. It also applies only to the transfer of calls across interconnection points between the home network of the A-Party and the home network of the B-Party. It does not consider in detail interconnections needed to support roaming scenarios. A further issue of the present document will consider interconnect scenarios related to roaming. The present document is relevant not just to IMS but to any NGN SIP-based interconnection.
|
f867071dbea0e55b4369d86f8f5971d1
|
184 006
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
f867071dbea0e55b4369d86f8f5971d1
|
184 006
|
2.1 Normative references
|
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] Void. [2] ETSI TS 181 005: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Services and Capabilities Requirements". ETSI ETSI TS 184 006 V2.1.1 (2008-09) 6 [3] ETSI TS 182 012: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based PSTN/ISDN Emulation Sub-system (PES); Functional architecture". [4] ETSI ES 282 007: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture". [5] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture". [6] ETSI ES 283 018: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: H.248 Profile for controlling Border Gateway Functions (BGF) in the Resource and Admission Control Subsystem (RACS); Protocol specification". [7] ETSI ES 283 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 [Release 7], modified]". [8] ETSI TS 123 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228 version 7.5.0 Release 7)". [9] ITU-T Recommendation Q.3401: "NGN NNI Signalling Profile (Protocol Set 1)". [10] ETSI EN 383 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control (BICC) Protocol or ISDN User Part (ISUP) [ITU-T Recommendation Q.1912.5, modified]". [11] ETSI TS 123 228: "IP Multimedia Subsystem (IMS); Stage 2". [12] ETSI TS 124 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Signalling flows for the IP multimedia call control based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.228 Release 5)". [13] ETSI TS 124 229: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229 Release 8)". [14] ETSI TS 129 163: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks (3GPP TS 29.163 Release 7)". [15] ETSI TS 184 002: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Identifiers (IDs) for NGN". [16] Void. [17] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". [18] IETF RFC 3261: "SIP: Session Initiation Protocol".
|
f867071dbea0e55b4369d86f8f5971d1
|
184 006
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI TR 180 000: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Terminology". ETSI ETSI TS 184 006 V2.1.1 (2008-09) 7 [i.2] ETSI TR 184 007: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Naming/Numbering Address Resolution (NAR)".
|
f867071dbea0e55b4369d86f8f5971d1
|
184 006
|
3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project BGCF Breakout Gateway Control Function BICC Bearer-Independent Call Control CP Communication Provider DNS Domain Name System ENUM E.164 telephone NUmber Mapping GRX GRPS Roaming eXchange GSMA GSM Association IBCF Interconnection Border Control Function I-CSCF Interrogating-Call/Session Control Function I-ENUM Infrastructure ENUM IETF Internet Engineering Task Force IMS IP Multimedia System IPX IP Packet eXchange ISUP ISDN Signalling User Part IWF InterWorking Function MGCF Media Gateway Control Function NAR Naming/Numbering Addressing Resolution NGN Next generation Network NNI Network to Network Interface OPID Originating Party IDentity P-CSCF Proxy-Call/Session Control Function PES PSTN Emulation Service PSTN Public Switched Telephone Network RACS Resource and Admission Control Subsystem S-CSCF Serving-Call/Session Control Function SDP Session Description Protocol SIP Session Initiation Protocol TPID Terminating Party IDentity UA User Agent URI Uniform Resource Identifier
|
f867071dbea0e55b4369d86f8f5971d1
|
184 006
|
4 Introduction
|
This Technical Specification: • Defines a Routeing Model for NGN Interconnection. • Proposes the first set of Requirements and related CP Routeing Roles. • Defines the resolution process for tel URI and SIP URI. • Proposes the possible basic structure of NAR [i.2] Interconnect Framework. ETSI ETSI TS 184 006 V2.1.1 (2008-09) 8
|
f867071dbea0e55b4369d86f8f5971d1
|
184 006
|
5 Routeing Model for NGN Interconnection
| |
f867071dbea0e55b4369d86f8f5971d1
|
184 006
|
5.1 Reference scheme for interconnection
|
Figure 1 describes the NGN layers and the reference scheme for interconnection in NGN. The routeing resolution in NGN includes both the typical IP interworking routeing rules that are bounded into the transport layer and the service/control layer ones. Transport Layer Service/Control Layer Transport Layer Service/Control Layer Network A Network B NTP NTP NNI Signalling E.164 number IP address Figure 1: Reference scheme for Interconnection and routeing The call control and service control functions take into account service capabilities requirements for routeing. Some applications entities (for instance redirect servers and/or location application) may also be required to define the route. For the purpose of interconnection the Call Control function has to resolve routeing in order to get the next hop and reach the required destination (the transport layer has to allocate the resource required based on the services characteristics). As a consequence, the NGN routeing determination process includes both service and transport functions to define the correct destination and requires an appropriate service transport resources allocation at the interconnection level. The functionalities used for routeing at the transport layer follow the existing IP intrinsic routeing mechanisms, and have also to satisfy the NGN service requirements and the transport resource requirements (RACS function [4], [5]). Therefore routeing resolution at transport layer is outside the scope of the present document. The destination number/name and the type of service required are essential to identify the route for service layer routeing. The ETSI standards on NGN public identity [15] state that E.164 numbering is the main customer identification scheme. However in addition domain name based identifiers can be also used. In the case of the SIP protocol, as defined in relevant ETSI standards ([7]), such public identifiers are carried through so-called SIP URI (i.e. SIP URI: <E.164 number>@<home network domain>) and tel URI (i.e. tel URI: <E.164 number>). Public identifiers resolution is an essential part of the routeing process to determine the next hop network entity for the session setup: this entity can either be identified by an intermediate URI translated into an appropriate IP address using DNS functionality, or directly mapped to an IP address.
|
f867071dbea0e55b4369d86f8f5971d1
|
184 006
|
5.2 Interconnection and Routeing
|
The innovative approach for NGN routeing requires identifying a common routeing model that guarantees interoperability between networks; besides more networks, provided by different operators, can be involved in session setup and routeing process and related decisions depends on its specific role within the session setup process (i.e. originating, transit, triggering, termination or interworking). The routeing model for interconnection should take in account required type of service and existing interconnection bilateral agreements in order to resolve the route. ETSI ETSI TS 184 006 V2.1.1 (2008-09) 9 User A Originating/Access Terminating CC CC CC Originating Role Triggering Role Terminating Role User B Triggering Figure 2: Functional framework for routeing and CP roles Figure 2 identifies the essential Communication Providers' (CP) routeing roles for the routeing process of a generic session setup established for two users. The user A sends a service request to the NGN call control of the originating CP that has the objectives of processing the request and putting through the communication to other CPs or/and the user B. An individual CP may assume different roles on defining the route of the session for a service request and it can apply particular routeing procedures related also to the knowledge of the service required and the partial or full information on the final destination to reach (i.e. external routeing). The same representation can be also be adopted to include the cases where the same CP fulfils all the routeing roles for an internal call/session started and terminated on the same CP's domain/domains (i.e. internal routeing). The CP can implement one or more routeing roles at the same time, and can also provide these capabilities for other CPs (e.g. in the case of hosting). A description of the basic routeing roles follows: • Originating Role: responsible for the communication service offered to the end customer and basic service request and related call/session handling. It is influenced by the Originating customer profile. • Triggering Role: Responsible for numbering resolution, routeing determination toward final destination and the choice of appropriate next hop entity (internal or external) to reach it; additionally it is in charge to identify specific interworking requirements for NGN (IMS or not IMS networks) or for PSTN/ISDN interoperability. • The numbering resolution process implies the determination of "routable SIP URI" that includes the domain associated to operator which called user is subscribed to. In the case of terminating calls toward legacy networks (i.e. PSTN/ISDN or PLMN) the numbering resolution output can be a tel URI. • Terminating Role: responsible for terminating and serving the session-oriented communication to end user.
|
f867071dbea0e55b4369d86f8f5971d1
|
184 006
|
5.3 Transit capabilities
|
In addition to the previous basic CPs' roles the case where one or more transit networks are involved is relevant. • Transit Role: Route the session-oriented communication request to the next hop CP without any SIP URI or tel URI mapping in routable SIP URI. All the session related information is carried on to next hop transparently. The routeing process for transit is limited to transparently deliver the session setup to the appropriate next hop CP (without numbering resolution or mapping in a routable SIP URI). However the transit routeing process has to guarantee appropriate transport resources allocation to preserve service requirements. ETSI ETSI TS 184 006 V2.1.1 (2008-09) 10
|
f867071dbea0e55b4369d86f8f5971d1
|
184 006
|
5.4 Example of complete set of CP's roles
|
Figure 3 points out an example of a complete set of CP's roles for SoIx Interconnection (see SoIx in the NGN Architecture [5]) that highlights different application of routeing model for route determination. Originating Role UE A UE B CP2 CP4 CP5 CP7 Transit Role Transit Role Terminating Role CP3 PSTN/ ISDN Other “IP Network” UE C Service/Control layer signalling Transport layer Signalling Control functionalities CP1 Triggering Role CP6 Triggering Role for Interworking Figure 3: CPs roles for routeing process for SoIx interconnection Following is the routeing process implementation among different CPs, and the description of guidelines for implementations: • Originating role, on the basis of service required by session-based originated by Originating user, forwards the session setup request for routeing analysis to the Triggering Role entity, which is provided internally or by a different CP on the basis of bilateral agreements. • Triggering role is per definition responsible for resolving public user identities to determine the next hop outbound route towards the operator to which the destination user is subscribed. • Transit role is assumed by a CP that, on the basis of bilateral agreements, transparently forwards the session setup request to the appropriate next hop CP. • Terminating role is responsible for delivering communication service session setup to the destination end user; the numbering/naming analysis and related routeing process is limited to internal identification of session control entity associated to end user for required service communication session setup and then to determination of the IP address associated to the user terminal equipment. Where a Routable SIP URI is used, the CP with the terminating role for a service communication session is identified through the domain part of the routable SIP URI. ETSI ETSI TS 184 006 V2.1.1 (2008-09) 11
|
f867071dbea0e55b4369d86f8f5971d1
|
184 006
|
5.5 Routeing process requirements and related CP roles
|
At least the following parameters and functional elements shall be available as input of NGN Routeing Model (see figure 4): • Service parameters: set of parameters that represents service requirement for a specific session setup. • Terminating Party Identity (TPID): it is an E.164 number in tel URI or SIP URI coding format; optionally a domain name identifier can be also used. • Originating Party Identity (OPID): is an E.164 number in tel URI or SIP URI coding format; optionally a domain name identifier can be also used. • Performance parameters: That parameter can be taken into account for defining special action on routeing (i.e. bearer resources allocation, requirements on possible route, congestion and/or unavailable resources, etc.). It is also relevant to include the case of route determination for the case of overlap signalling (see [7]) in which a partial routeing decision can be made before dialling is completed. At least the following parameters and functional elements shall be available as output of NGN Routeing Model (see figure 4): • SIP URI or tel URI identifying the destination user. • Next Hop ID: it identifies the network entity (i.e. border gateway or other signalling/control functionality) that enables or is in charge of reaching next hop CP. • Transport resource parameters: parameters meaningful for transport addressing and routeing process at transport layer for resource allocation. The SIP URI that it is obtained through the numbering/naming resolution process is called a routable SIP URI since its domain part identifies the appropriate terminating CP. Common input: OPID TPID Bearer/media service requirements Performance, media and resources available If external routeing: Next Hop border gateway (naming or IP addressing) Routing policy (i.e. load sharing, etc.) OPID TPID tel URI, SIP URI or routable SIP URI Other service dependent characterizations Etc If internal routeing: Next Hop control functional entity/Node (naming or IP addressing) Bearer/media service requirements Routing policy (i.e. load sharing, etc.) OPID TPID tel URI, SIP URI or routable SIP URI Other service dependent features E IP addressing Resource allocation requirements Transport Routeing Next Hop Node or Gateway for transport layer Originating and destination IP address IP internetworking routing policy Service/Application Service and Control routing functionalities Service profile parameter Service dependent input: tel URI, SIP URI or Routable SIP URI Destination Party Location other protocol information Figure 4: Common general purpose Routeing Model for NGN ETSI ETSI TS 184 006 V2.1.1 (2008-09) 12 Considering figure 4, the common requirements for the routeing model are the following: • Numbering and naming resolution functionality are applied for routable SIP URI determination, based on specific mapping functionalities (database with relation with numbering/naming and destination CPs, etc.). • The routeing process shall depend on the service characteristics and associated parameters that are meaningful for determination of the route to the destination network. The process shall check and validate the service requirements compatibility with user service profile and network resource availability. • Originating and Terminating Party Public Identities shall be considered the essential information for routeing process. • Other service dependent parameters (for instance location parameters) can be considered if meaningful for routeing process application. Considering the different roles identified for routeing in figure 3, the routeing model for NGN will be appropriately characterized to apply associated functionalities and input/output parameters. Table 1: Requirements and actions for CP roles CP roles Requirement and actions summing up Originating TPID is not resolved by CP's call control. Service session setup request has to be forwarded to Transit or Triggering CP. Triggering tel URI or SIP URI is resolved in a "routable" SIP URI. Triggering for interworking tel URI or SIP URI can not be resolved, since final destination is PSTN/ISDN or PLMN or an "All IP" network not compliant with ETSI NGN specifications. tel URI is forwarded to interworking function to apply specific resolution mechanisms and procedures. Terminating The domain part of the routable SIP URI corresponds to the domain of the terminating CP and end user shall be identified. Transit Call/session is to be delivered transparently to a terminating CP, basing on a tel URI or a Routable SIP URI domain part different from the transit CP. tel URI or SIP URI, after having identified routing towards terminating CP, is passed on unmodified.
|
f867071dbea0e55b4369d86f8f5971d1
|
184 006
|
5.6 SIP and E.164 numbering
|
Also at interconnection [i.2] applies and table 2 shows the relationship between the Public ID that identifies a Terminating and Originating user parties and the formats used in SIP header fields. The present document is focused on E.164 numbering in tel URI or SIP URI coding formats. Table 2: Public IDs and formats Public ID (User parties) NGN coding formats User/Service Identifiers "User@Domain" format SIP URI International or national E.164 Numbers tel URI SIP URI Thus the two formats that may be used are: • tel URI for international or national numbers, e.g. tel: +431505641636. • SIP URI, e.g. sip: +431505641636@<serving operator>;user=phone. NOTE: "user=phone" is appended where the user part of the SIP URI is a string that is the same as a tel URI. Additionally, the SIP "phone-context" parameter is used in case of national E.164 numbers and other digit strings that are non-E.164 numbers. ETSI ETSI TS 184 006 V2.1.1 (2008-09) 13
|
f867071dbea0e55b4369d86f8f5971d1
|
184 006
|
5.7 Address Resolution, Routeing requirements
|
Address resolution function can be logically divided in two general phases: • Number to naming mapping: where the number is converted to a format which can be used by the name resolution function. • Naming resolution: where the internal domain naming, looking up in an infrastructure ENUM or in equivalent database or static table, to retrieve "Routeable" SIP URI (that contains the serving operator domain). If number or name can not be solved locally, address resolution function passes number on, towards a pre-configured triggering internal entity or different CP network, using tel URI format. When the number/name has been resolved, the Routeable SIP URI is used to derive the IP address of next functional entity, generally basing on DNS mechanisms or on local naming-address mapping table functionalities. Figure 5 illustrates such a resolution process that is required for number and naming translations from the dial string to the IP address, associated to the next hop functional entity. Process Dialed Digits Name/Number to SIP URI Translation Route Determination & Selection Dial String Target Name ( tel URI, SIP URI, URN) Target Routable SIP URI Address Resolution Target Home Operator/CP Target Network Element / User IP-Address E.164 SIP URI Hostname Figure 5: Naming/Numbering Address Resolution overview (for details see [i.2] clause 6.3) ETSI ETSI TS 184 006 V2.1.1 (2008-09) 14 It should be noted that ENUM can provide only the domain of the home CP for the B-party or terminating CP. On the basis of such domain information, the internal routeing functions, have to define the next hop entity or border gateway to handle call/session and/or the transit role CP, on the base of specific routeing arrangement defined by CPs (e.g. on the base of bilateral agreements). NOTE: Generally, in alignment with ETSI/3GPP specifications, the presence of an E.164 number in a specific infrastructure ENUM assures that associated terminating/serving CP is reachable through pre-defined interconnection arrangements and related networks interconnection; for instance, that is the case of IPX (GRX successor), and internal carrier ENUM infrastructures managed by GSMA and related to the fixed- mobile international interconnection context. The following rules for SIP header coding apply: 1) The called/terminating user identity is inserted in the TO field. 2) The Request-URI field content shall be, when available, a "Routeable" SIP URI that is a SIP URI with domain part identifying terminating/serving CP determined from an authoritative source or locally pre-defined. Otherwise Request-URI field content shall be E.164 number coded by tel URI format. The number in the tel URI coding format can be in national or international E.164 number format, in accordance with ITU-T Recommendation E.164 [17]. 3) Route header field contains the next hop(s). The above is based on figure 6 which is derived from analysis of various parts of RFC 3261 [18]. ETSI ETSI TS 184 006 V2.1.1 (2008-09) 15 Figure 6: header handling in SIP
|
f867071dbea0e55b4369d86f8f5971d1
|
184 006
|
5.7.1 tel URI and SIP URI resolution requirements and procedures
|
Figure 7 describes a general process and related functions for tel URI and SIP URI, provided by the user (Dialling) or in interconnection scenarios, based on ENUM systems or other translation database functions. The flow shows the potential usage of infrastructure ENUM (if available) or of other DBs in order to define the correct route towards both local network terminations and out-bound interconnected network and CPs. Note that, in figure 7, the local Number Analysis function (NAR) is used to handle cases where I-ENUM fails to find the number and associated NAPTR record and to find out the appropriate destination which delivers the call/session to; that could be the situation in which dialled number is not present in ENUM or the derived SIP URI domain part is not recognized locally as a reachable CP. The general outputs of figure 7 procedures and functions are the following: • if the resolution of tel URI or SIP URI has succeeded, then the session is delivered to the customer network termination point or the "Routable" SIP URI is passed on to the interconnected CP; • if the resolution has not succeeded, then analysis functions will check if it is a circuit-switched PSTN/ISDN or PLMN destination or other "All IP" networks not integrated with NGN environment or reachable by other interconnected CPs, in which case a tel URI or SIP URI will be provided to for routeing resolution. ETSI ETSI TS 184 006 V2.1.1 (2008-09) 16 Number Block |CP | Domain | Interconnection Geo. Num. |CP1 | @ cp1.it | SoIx Non geo Num |CP2 | @ cp2.it | SoIx Num. X |CPx | --- | TDM SIP URI tel URI or SIP URI Resolution through I-ENUM? Query I-ENUM using the tel URI Number Analysis Y N Is NAPTR available? Y (Routable SIP URI) N Is CP domain available? Forward request of resolution to CP across other ALL IP Network N Dialling Interworking with TDM (i.e. SIP/ISUP interworking) tel URI (In-bound) Interconnection SIP URI (In-bound) Domain recognized ? Y Interconnection Is a Local User? Y Terminate the session to end user Is a Local User? N N (no resolution) Y Query DB DB Numbering I-ENUM N Y (Routable SIP URI) Interconnection Interconnection Interworking? Y N Figure 7: General functions and procedures for tel URI and SIP URI resolution in NGN ETSI ETSI TS 184 006 V2.1.1 (2008-09) 17
|
f867071dbea0e55b4369d86f8f5971d1
|
184 006
|
5.8 Relation with NAR Interconnection general framework
|
The gap analysis based on NAR [i.2] use cases has identified a requirement to introduce NAR functionality in ETSI NGN architecture. The present document provides further definition of NAR functionality for NGN Interconnection routeing. NAR for Interconnection and routeing is concentrated in the control and service layers which are responsible for handling numbering, naming and routing tasks and driving lower layer requirements (e.g. transport entities). NAR does not correspond either to new entities or new specific reference points. Instead there is a need to focus on a homogeneous description that addresses these specific needs of NGN interconnection and routeing. Because the NAR functionality is the context aware resolution of an identifier into a result which is useable for NGN routeing, it shall include also the interconnection and routeing requirements. Figure 8 describes, on the basis of [4], the specific NAR functionality applied to the interconnection and routeing entities that can consist in general of one or more relations with service/control layers entities. Other networks Other subsystems Core IMS PSTN/ISDN Emulation subsystem User Equipment Service Layer Transport Layer Transfer Functions Resource and Admission Control Subsystem Network Attachment Subsystem Applications User profiles NAR functionality Figure 8: NAR functionality in ETSI NGN architecture for interconnection 6 Interconnection, interworking, interface and routeing requirements Interconnection refers to the connection of two networks so that they can support interoperable services. There could be pure transport IP connectivity interconnection, either with "best effort" or with specific QoS classes, or "service-aware" interconnection for multimedia and innovative "session-based" services. Interconnection takes place at a reference point at which a specific Network to Network Interface (NNI) is defined, generally related to different end-to-end interoperable offered service. The characteristics of the NNI depend on the kind of networks / administrative domains to be interconnected, for instance IMS, PSTN/ISDN, and PLMN, other IP-based networks, etc. ETSI ETSI TS 184 006 V2.1.1 (2008-09) 18 In general two different networks are interconnected by session border functionalities, often located in specific border equipments in which any necessary interworking functionalities (for instance, the conversion from one protocol to another) are provided. That allows separating the two networks like two different domains, in order to manage them independently. Thus for successful interconnection definition, there is a need to identify at least: • Interconnection service required, i.e. pure IP connectivity or "session-based" voice/multimedia service. • NNI Interface requirement for specification, also for rules between the signalling and transmission control on each side of the session border functionalities or interworking function As a reference scheme figure 9 shall be considered. Figure 9: Reference scheme for NNI Interconnection between two networks
|
f867071dbea0e55b4369d86f8f5971d1
|
184 006
|
6.1 Interconnection NNI in IMS and NGN architecture
|
Figure 10, which is based on the relevant ETSI standards and specifications [4] and [5], provides an overview of different possible NNIs. Clause 5 of the present document, which describes the routeing model for interconnection, covers the following types of service interconnections: • "basic end-to-end service interconnection" for the routeing and setting up of a call/session between two NGN domains and related end users; • "Roaming end-to-end interconnection" to support a call originated from a roaming (visited) network or a call extended from the B-party serving (home) network to the roaming (visited) network. However this case is out scope of the present document. The following possible locations of NNIs are also considered to be in the scope of the present document (excluding internal interfaces because they are not interconnection points towards other networks): 1) Signalling and transport NNI between IMS networks in different administrative domains. 2) Signalling and transport NNI between IMS network and other Non IMS IP networks. Although the general NGN routeing model can be adapted to include transport layer interconnection scenarios described in the NGN general architecture [4], they are outside the scope of the present document which relates only to end-to-end service interconnection. NNI Network A Border Element Network B ETSI standard for NNI Transport Signalling Border Element Service/control functions Transport functions Transport functions Service/control functions ETSI ETSI TS 184 006 V2.1.1 (2008-09) 19 Figure 10: NNI possibilities based on [4], and [5]
|
f867071dbea0e55b4369d86f8f5971d1
|
184 006
|
6.2 Transit network scenarios
|
The term transit refers to the routeing of calls and other communications through networks other than the originating and terminating ones. There are essentially two general categories of NGN transit networks: • "IP Connectivity only" transit network, where IP packets traffic is delivered by transit network without any knowledge of the carried service. This is referred to as CoIx Interconnection. • "Service related" transit network, where the transit network interacts with the communications at the service control level for end-to-end service interoperability. This is referred to as SoIx Interconnection. Every network provides at least some connectivity but may or may not provide service related transit. The proxy functions needed for service related transit may be provided by a third party on a connectivity platform. Some options are illustrated in figure 11. ETSI ETSI TS 184 006 V2.1.1 (2008-09) 20 Originating network Terminating network Transport Transport Transport Transport Service Service Originating network Terminating network Transport Transport Transport Transport Service Service Service related transit Connectivity only transit Hub Hub Figure 11: Examples of different transit network scenarios There are two main types of platforms providing IP-level connectivity: a) Dedicated "telco type" networks (e.g. via IPX which can be viewed as an extranet). b) The public Internet. Note also that transit level functionality may be provided on a hop-by-hop basis across multiple networks that each run their own service related transit function. Figure 12 illustrates SoIx interconnection where the transit network does interact with the signalling. Gq’ Ic Ia Gq’ Ia Iz Gq’ Ia Ic Iz Gq’ Ia Transport processing Function Transport processing Function RACS RACS Service Layer Service Layer Transport processing Function RACS Service Layer Gq’ Ic Ia Gq’ Ia Iz Gq’ Ia Ic Iz Gq’ Ia Transport processing Function Transport processing Function RACS RACS Service Layer Service Layer Transport processing Function RACS Service Layer Figure 12: SoIx-to-SoIx Transit Interconnection In this figure, end-to-end service interoperability can be guaranteed by the Transit Domain as a result of SoIx interconnection on both sides. End-to-end service requirements are delivered by all interconnected networks through the control of transport resources via the RACS functions. ETSI ETSI TS 184 006 V2.1.1 (2008-09) 21
|
f867071dbea0e55b4369d86f8f5971d1
|
184 006
|
6.3 Application to different NGN scenarios
|
Table 3 shows the application of NGN scenarios, based on an "IP-based, session-based" NNI and related naming/numbering requirements. Starting from ETSI NGN architectures and related subsystems (i.e. PES, IMS, etc.) and considering concrete "IP-based" NNI "session-based" interconnection scenarios, a limited number of cases can be identified. Table 3: Main interconnection scenarios, protocols and related numbering/naming requirements "IP-based" session-based interconnection scenario ETSI NNI signalling protocol NNI transport (control and user plane) Naming/numbering requirements NGN (CS domain)↔NGN (CS domain) SIP-I IP-based E.164 number or tel URI (in case of SIP URI the user part is the key for routeing. The domain part could be used for media gateway selection) NGN (PS domain)↔NGN (PS domain) SIP IP-based tel URI or SIP URI NGN (PS domain)↔NGN (CS domain) SIP-I or SIP IP-based E.164 number, tel URI or SIP URI NGN↔ other IP network SIP IP-based SIP URI NGN↔PSTN/ISDN/PLMN ISUP/BICC SS7 and TDM E.164 number Note that in the table above, the term "CS domain" means that the control plane is NGN subsystem (IMS, PES) and the user plane or bearer is based on circuit switch technology. Figure 13 describes the interworking of NGN with PSTN/ISDN and Other IP Network (that has been defined into [5]) that are described into the last two lines of table 3. T-MGF I-BGF SGF Transport Layer Service Layer PSTN/ISDN Other IP Networks Iz bearer signalling PSTN/ISDN Transport interfaces Figure 13: Network interconnection at transport layer [5] The following conclusions can be drawn: • NNI definitions should not depend on the specific NGN subsystem involved, since it is a fundamental objective to converge toward strictly limited NNI interfaces and protocols that cover all possible scenarios. • NGN must be able to support interworking with circuit-switched networks. ETSI ETSI TS 184 006 V2.1.1 (2008-09) 22 Annex A (informative): Protocols at the NNI points and interworking The signalling NNI protocol used for IMS interconnection is SIP and both ETSI and ITU-T Recommendation Q.3401 [9] (NNI for voice band services) have made adaptations of SIP, defined by IETF in RFC 3261 [18], for different network applications. Interconnection between networks adherent to different versions of the SIP standard can require an interworking function. The main different SIP standards are the following: • The ITU-T profile for the pure SIP NNI specified in ITU-T Recommendation Q.3401 [9]. • The ITU-T Recommendation Q.1912.5 "Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part" [10]. ITU-T Recommendation Q.1912.5 [10] adapts and references RFC 3261 [18] for interworking with BICC/ISUP networks. • The 3GPP pure SIP IMS call control documents: - TS 123 228 [11] Stage 2 which gives the main signalling flows for the IMS core network. - TS 124 228 [12] Stage 3 signalling flows which gives example signalling flows for the IMS call control and expands on the information in TS 123 228 [11]. - TS 124 229 [13 ]Stage 3 protocol which specifies the IMS call control protocol using SIP and SDP for the IMS core network. TS 124 229 [13] makes is an endorsement/modification of RFC 3261 [18] and other RFCs. - TS 129 163 [14] Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks, based on ITU-T Recommendation Q.1912.5 [10]; • The TISPAN pure SIP IMS call control document: - ES 283 003 [7] which modifies and endorses TS 124 229 [13]. Figure A.1 shows the development from the base SIP specification of the three different forms of SIP used for NNIs, i.e. SIP-I, IMS SIP, and non-IMS pure SIP. ETSI ETSI TS 184 006 V2.1.1 (2008-09) 23 Figure A.1: Development of SIP variants for NNIs Figure A.2 shows the development of the interworking specifications that relate the different forms of SIP to ISUP and BICC. The figure again shows SIP-I, the IMS SIP, and the non-IMS pure SIP. Figure A.2: Development of SIP interworking specifications ETSI ETSI TS 184 006 V2.1.1 (2008-09) 24 Annex B (informative): SIP Header Fields at the NNI relevant to routing and identification The critical SIP element from a routeing point of view is the INVITE method. An example of an INVITE method is shown in figure B.1. It is a text string, and consists of: • The word INVITE followed by either a tel URI or a SIP URI, which may be followed by one or more parameters. • A number of subsequent lines called headers, where each line starts with a pre-defined word and is followed by one or more header fields. Each header field may contain one or more parameters. These terms are shown in figure B.1. Session Initiation Protocol Request-Line: INVITE sip:+41454000191@cp-domain;user=phone SIP/2.0 Message Header To: <sip:+41454000191@cp-domain;user=phone> From: “Name“ <sip:+41454000201@cp-domain;transport=udp>; tag= <?> Call-ID: <?> CSeq: 1 INVITE Max-Forwards: 68 Content-Length: 343 Via: SIP/2.0/UDP 123.45.123.48 :5060;branch= <?> Via: SIP/2.0/UDP 123.45.123.150:5060;branch= <?> Via: SIP/2.0/UDP 192.168.1.36 :2725; received=10.7.7.149;branch= <?>; rport=56608 Route: <sip:scscf1.intranet.net:6050;lr> Record-Route: <sip: <?>cp-domain@scscf1.intranet.net:6050; maddr=123.45.123.48;lr> Contact: <sip:+41454000201@123.45.123.150:5060; transport=udp>; flow-id=1 Content-Type: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO Allow-Events: talk Allow-Events: hold Allow-Events: refer Accept: application/sdp Supported: 100rel, replaces, callerid P-Asserted-Identity: “Name" <sip:+41454000201@cp-domain> User-Agent: snom320/SC0825 P-Charging-Vector: icid-value=<?> Session-Expires: 360 Min-SE: 360 P-Key-Flags: keys="3" Message body Session Description Protocol Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): root xx yy IN IP4 10.1.1.149 Session Name (s): call Connection Information (c): IN IP4 123.45.123.85 Time Description, active time (t): 0 0 Media Description, name and address (m): audio 14734 RTP/AVP 18 8 9 2 3 4 101 Media Attribute (a): rtpmap:18 g729/8000 Media Attribute (a): rtpmap:8 pcma/8000 Media Attribute (a): rtpmap:9 g722/8000 Media Attribute (a): rtpmap:2 g726-32/8000 Media Attribute (a): rtpmap:3 gsm/8000 Media Attribute (a): rtpmap:4 g723/8000 Media Attribute (a): rtpmap:101 telephone-event/8000 Media Attribute (a): fmtp:101 0-16 Media Attribute (a): ptime:20 Media Attribute (a): sendrecv Headers Figure B.1: Structure of the INVITE Message ETSI ETSI TS 184 006 V2.1.1 (2008-09) 25 The specification of SIP protocol is defined in ES 283 003 [7]. The following explains the main header fields relevant to routing and identification as used in TISPAN. NOTE 1: Some of these uses are more restrictive than are specified in RFC 3261 [18]. • Request-URI The Request-URI field identifies the incoming call server (the I-CSCF in the case of IMS) of the serving network. A proxy can only change the Request-URI of a request during forwarding if it is responsible for that URI. • VIA The VIA header field(s) keeps track of all the proxies a request has traversed. The response uses these VIA(s) to be routed back via the same proxies as traversed by the request. The VIA header is mandatory in all SIP messages, and as a minimum lists the involved UAs. If the host portion of the "sent-by" parameter contains a domain name, or if it contains an IP address that differs from the packet source address, the server must add a "received" parameter to that VIA header field value. This parameter must contain the source address from which the packet was received. (This is to assist the server transport layer in sending the response, since it must be sent to the source IP address from which the request came.) Consider a request received by the server transport which looks like, in part: INVITE sip:bob@Biloxi.com SIP/2.0 Via: SIP/2.0/UDP bobspc.biloxi.com:5060 The request is received with a source IP address of 192.0.2.4. Before passing the request up, the transport adds a "received" parameter, so that the request would look like, in part: INVITE sip:bob@Biloxi.com SIP/2.0 Via: SIP/2.0/UDP bobspc.biloxi.com:5060; received=192.0.2.4 • Contact Contact headers are exchanged in order to let peer UAs exchange SIP signalling directly with no intermediaries. This applies except for the proxies that have explicitly requested to remain in the signalling path by adding their URI in a previous Record-Route. • Record-Route The header is added by a Proxy during a transaction in order for the Proxy to remain in the path for all requests sent within the dialog. The set of all recorded routes are carried in the response to this request. Route headers are added by the initiator in subsequent transactions to enforce the routing as recorded by the Record-Routes The Record-Route header field is inserted by proxies in a request to force future requests in the dialog to be routed through the proxy. • Route Enforces the routing as recorded in a previous transaction by applying Record-Routes. • P-Called-Party-ID Identifies which of the several possible identities an INVITE is addressed to. • To This header is used for UA-UA purposes and so should be passed unchanged and unused by transit networks. NOTE 2: This header is used by the networks in the REGISTER process. NOTE 3: The "tag" parameter is used in the To and From header fields of SIP messages. It serves as a general mechanism to identify a dialog, which is the combination of the Call-ID along with two tags, one from each participant in the dialog. ETSI ETSI TS 184 006 V2.1.1 (2008-09) 26 • Call-ID: The Call-ID header field acts as a unique identifier to group together a series of messages. It shall be the same for all requests and responses sent by either UA in a dialog. It should be the same in each registration from a UA. • Branch: The Via header field value shall contain a branch parameter. This parameter is used to identify the transaction created by that request. This parameter is used by both the client and the server. The branch parameter value shall be unique across space and time for all requests sent by the UA. ETSI ETSI TS 184 006 V2.1.1 (2008-09) 27 History Document history V2.1.1 September 2008 Publication
|
d7056ed53c012ccc416d1b8f10e65f81
|
183 054
|
1 Scope
|
The present document specifies the, stage three, Protocol Description of the Closed User Group (CUG) service.
|
d7056ed53c012ccc416d1b8f10e65f81
|
183 054
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
d7056ed53c012ccc416d1b8f10e65f81
|
183 054
|
2.1 Normative references
|
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] Void. [2] Void. [3] Void. [4] ETSI TS 124 454: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services; Protocol specification Closed User Group (CUG) (3GPP TS 24.454 Release 8)".
|
d7056ed53c012ccc416d1b8f10e65f81
|
183 054
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. ETSI ETSI TS 183 054 V2.2.0 (2008-06) 6
|
d7056ed53c012ccc416d1b8f10e65f81
|
183 054
|
3 Definitions and abbreviations
| |
d7056ed53c012ccc416d1b8f10e65f81
|
183 054
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 124 454 [4] apply.
|
d7056ed53c012ccc416d1b8f10e65f81
|
183 054
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TS 124 454 [4] apply.
|
d7056ed53c012ccc416d1b8f10e65f81
|
183 054
|
4 Closed User Group (CUG)
|
The provisions of the present document are contained in TS 124 454 [4]. ETSI ETSI TS 183 054 V2.2.0 (2008-06) 7 Annex A (informative): Bibliography Information is contained in TS 124 454 [4]. ETSI ETSI TS 183 054 V2.2.0 (2008-06) 8 History Document history V2.1.0 November 2007 Publication V2.2.0 June 2008 Publication
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
1 Scope
|
The present document specifies normative rules for how to use the Gq', Rq, Ia and Re protocols (TS 183 017 [4], ES 283 026 [3] ES 283 018 [7] and TS 183 060 [9]) as of TISPAN release 2. These rules apply to the interface between: • P-CSCF and SPDF using Gq'; • IBCF and SPDF using Gq'; • SPDF and (C- and I-) BGF using Ia; • SPDF and x-RACF using Rq; • x-RACF and RCEF using Re. In addition, to illustrate the usage of these rules, the present document contains informative signalling flows between the above-listed entities. The present document covers both IMS and non-IMS AFs, and both conversational services such as telephony and non-conversational services such as IPTV. For IPTV, both unicast and multicast are covered, as well as the push and pull models for interactions with the ECF/EFF. Conversational multicast services and the usage of pull for conversational services is out of the scope for the present document. In case of any discrepancy between the end-to-end IMS signalling flows in the present document and the ETSI TISPAN IMS specifications (TS 182 006 [5], ES 283 003 [6] and TS 183 063 [10]), the ETSI TISPAN IMS specifications shall take precedence. The following specific topics are covered in the present document; • policy enforcement in the RCEF; • error handling over Ia; • transcoding in the I/C-BGF; • reservations requests in overbooking mode; • address latching for hosted NAPT/NAPT-PT traversal.
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. ETSI ETSI TS 183 048 V2.2.1 (2009-08) 6
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
2.1 Normative references
|
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications". [2] ETSI TS 129 207: "Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS); Policy control over Go interface (3GPP TS 29.207)". [3] ETSI ES 283 026: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN);Resource and Admission Control; Protocol for QoS reservation information exchange between the Service Policy Decision Function (SPDF) and the Access-Resource and Admission Control Function (A-RACF) in the Resource and Protocol specification". [4] ETSI TS 183 017: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER protocol for session based policy set-up information exchange between the Application Function (AF) and the Service Policy Decision Function (SPDF);Protocol specification". [5] ETSI TS 182 006: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Stage 2 description (3GPP TS 23.228 v7.2.0, modified)". [6] ETSI ES 283 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 [Release 7], modified]". [7] ETSI ES 283 018: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: H.248 Profile for controlling Border Gateway Functions (BGF) in the Resource and Admission Control Subsystem (RACS); Protocol specification". [8] ETSI TS 124 229: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229)". [9] ETSI TS 183 060: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Subsystem (RACS); Re interface based on the DIAMETER protocol". [10] ETSI TS 183 063: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based IPTV stage 3 specification". [11] IETF RFC 3588: "Diameter Base Protocol". [12] ITU-T Recommendation H.248.1: "Gateway control protocol: Version 3". [13] IETF RFC 3246: "An Expedited Forwarding PHB (Per-Hop Behavior)". [14] IETF RFC 4566: "SDP: Session Description Protocol". [15] IETF RFC 2597: "Assured Forwarding PHB Group". [16] ETSI TS 124 615: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specification. (3GPP TS 24.615)". ETSI ETSI TS 183 048 V2.2.1 (2009-08) 7
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable.
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: AAA AA-Answer AAR AA-Request AF Application Function A-RACF Access - Resource Admission Control Function AS Application Server AVP Attribute Value Pair BGF Border Gateway Function C/I-BGF Core/Interconnection Border Gateway Function CLF Connectivity session Location and repository Function CW Communication Waiting DL Down Link FE Functional Entity IBCF Interconnection Border Control Function IMS IP Multimedia Subsystem IP Internet Protocol LD Local Descriptor MG Media Gateway MGC Media Gateway Controller NAPT Network Address and Port Translation NAPT-PT Network Address and Port Translation - Protocol Translation NAT Network Address Translation NDUB Network Determined User Busy PCMU Pulse Code Modulation Mu-law P-CSCF Proxy - Call Session Control Function RACS Resource and Admission Control Subsystem RCEF Resource Control Enforcement Function RTCP Real Time Control Protocol RTP Real Time Protocol SDP Session Description Protocol SIP Session Initiation Protocol SPDF Service-based Policy Decision Function UDP User Datagram Protocol UE User Equipment UL Up Link XML eXtensible Markup Language ETSI ETSI TS 183 048 V2.2.1 (2009-08) 8
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
4 Example call flow
|
This clause contains a set of informative example call flows. Figure 4.1: RACS, RCEF, BGF and P-CSCF/IBCF interactions (alternative 1) Figure 4.1 illustrates the basic interactions involved when requesting a resource reservation from RACS for an IMS call. It should be noted that the SPDF may interrogate I/C-BGF and x-RACF (shown as A-RACF in figure 4.1) in any order. Hence, interacting with the C-BGF after the x-RACF as shown in figure 4.1 is not mandated, and the SPDF may instead interrogate the x-RACF before the I/C-BGF as shown in figure 4.2, or interrogate these entities in parallel. ETSI ETSI TS 183 048 V2.2.1 (2009-08) 9 C-BGF/I-BGF SPDF P-CSCF/IBCF A-RACF SDP offer/ answer received Define connection info. Diameter AAR SPDF policy H.248 ADD Create terminations H.248 ADD reply Extract termination addresses Diameter AAR Resource and policy based admission control Diameter AAA Diameter AAA Modify SDP offer/answer A-RACF Policy install Diameter PIR Diameter PIA Figure 4.2: RACS, RCEF, BGF and P-CSCF/IBCF interactions (alternative 2) For some deployments, the extraction of termination addresses done by the SPDF for signalling to the x-RACF may rely on information coming from I/C-BGF. For example, the x-RACF may need the local termination address at the C-BGF when performing resource and admission control for the network in between the RCEF and the C-BGF. Unless this address information can be derived by other means, the SPDF needs to interrogate the C-BGF to obtain the local termination address at the C-BGF before issuing a Diameter AAR to the x-RACF. The interactions illustrated in figure 4.1 (and figure 4.2) are repeated twice for each call setup and each SPDF instance along the path of the attempted call as described in the following clauses.
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
5 RACS related procedures
|
This clause specifies normative rules for how to use the Gq', Rq, Ia and Re protocols.
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
5.1 Procedures at P-CSCF/IBCF
| |
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
5.1.1 Resource and admission control
|
This clause describes the rules used by the P-CSCF/IBCF to derive the bandwidth to request from RACS. In case being present, the b= attribute will correspond to the bandwidth required by the most bandwidth demanding codec in the list. Hence, the Max-Requested-Bandwidth-UL and -DL shall be set to the value given by the b= attribute if present. In case the b= attribute is not present the P-CSCF/IBCF shall set these AVPs according to one of the following rules: • Set the AVPs to the value locally associated to the codec received in the m= line when only one codec is listed in the m= line or the highest bandwidth required by the codecs listed in the SDP offer (when multiple codecs are proposed for this media component). ETSI ETSI TS 183 048 V2.2.1 (2009-08) 10 • Set the AVPs to the value locally associated to the codec received in the m= line when only one codec is listed in the m= line or the lowest bandwidth required by the codecs listed in the SDP offer (when multiple codecs are proposed for this media component). In this case the Max-Requested-Bandwidth-UL and -DL AVPs may not reflect the actual bandwidth value that will be negotiated for the session. • Omit the AVPs and let RACS determine a default bandwidth based on the combination of Reservation-Class and Media-Type AVPs. The above-given rules are in line with the description given in annex B (table B.1) of TS 183 017 (Gq') [4] for how to populate the Max-Requested-Bandwidth-UL and -DL AVPs. These rules provide however more details on how to populate these AVPs referred to from TS 183 017 [4] in annex B (table B.1). It should be noted that the above-given rules imply that the Max-Requested-Bandwidth-UL and -DL AVPs may be modified during the SDP negotiation (i.e. when the codec to be used is finally agreed between the endpoints).
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
5.1.2 NAPT/NAPT-PT at the P-CSCF/IBCF
|
Details on NAPT/NAPT-PT operations at the P-CSCF are given in TS 124 229 [8]. The IBCF supports controlled NAPT/NAPT-PT but does not support hosted NAPT/NAPT-PT traversal. That is, the IBCF is capable of replacing addresses and ports in the SDP as ephemeral terminations are created following the rules given in clauses 5.2.1.3 and 5.2.1.4, but the IBCF cannot handle address latching as used for hosted NAPT/NAPT-PT traversal. The P-CSCF is capable of both hosted NAPT/NAPT-PT traversal and controlled NAPT/NAPT-PT.
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
5.2 Procedures at SPDF
|
For resource and admission control purposes the SPDF will determine on local policy as specified in TS 183 017 [4] whether a C-BGF and/or an A-RACF need to be involved in the AF session. The SPDF procedures related to the Gq' interface involved in supporting NAPT/NAPT-PT services provided by the BGF and in supporting resource and admission control services provided by the A-RACF are described in TS 183 017 [4]. Based on these procedures this clause describes the operations of the SPDF involved in co-ordinating requests for these services made over Gq' with the required signalling over the Ia and Rq interfaces. The co-ordination of request made over Gq' with the required signalling over the Ia interface is described in clause 5.2.1, while the co-ordination required between Gq' and the Rq interface is described in clause 5.2.2. Clause 5.2.3 describes the co-ordination of signalling over the Ia and Rq interfaces.
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
5.2.1 Reservation with BGF involved
|
The translation of values not specific to address translation received over Gq' to values used for request made over Ia is described in clause 5.2.1.1, operations involved in co-ordinating requests for NAPT/NAPT-PT services are described in clauses 5.2.1.2, 5.2.1.3 and 5.2.1.4, BGF media transcoding is described in clause 5.2.1.5 and BGF transport plane failure detection is described in clause 5.2.1.6.
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
5.2.1.1 Resource reservation at the BGF
|
Upon reception of an initial reservation (SDP offer) the SPDF will extract from the information received with the AAR the important information in order to reserve resources at the transport layer, different AVPs will be received included in the AAR, only some of them will be retransmitted over the Ia interface. The aim of this clause is to provide the transcription for those AVPs: • The Transport class AVP may be used for pointing to a class of transport services to be applied as detailed in TS 183 017 [4], in that way it may indicate the DSCP marking and the command syntax over the Ia interface may be ds/dscp, this information may be sent through the local control descriptor. • The value of the Reservation priority AVP may be sent over the Ia interface as the priority of the context. The following table summarizes the population rules for setting context and termination properties, based on received DIAMETER AVPs and local configuration data. ETSI ETSI TS 183 048 V2.2.1 (2009-08) 11 Table 5.2.1.1.1 Context parameters Descriptor Descriptor Descriptor Properties Population rules Context ID Always set by the BGF Priority Indicator Set from the Reservation-Priority AVP Emergency Indicator Set from the Service Class AVP Term ID See ES 283 018 [7] Media Stream Local Control Mode Set from Flow-Status in Media-Component-Description and/or Flow-Status in Media-Component. Media-Sub-Component. ds/dscp Set from Transport-Class in Media-Component-Description. gm/saf Depends on the Service-Class AVP and BGF profile information. gm/spf Depends on the Service-Class AVP and BGF profile information. gm/sam If gm/saf is set to ON, the gm/sam property is set from the Flow-Description in Media-Component. Media-Sub-Component. gm/spr If gm/spf is set to ON, the gm/spr property is set from the Flow-Description in Media-Component. Media-Sub-Component. gm/rsb Depends on the value of the Media-Type AVP and BGF profile information. gm/esas Depends on the Service-Class AVP and whether NAP-PT is activated. gm/lsa If gm/esas is set to ON, gm/lsa is set from the address (c= line) contained in the remote descriptor of the opposite termination. gm/esps Depends on the Service-Class AVP and whether NAP-PT is activated. gm/lsp If gm/esps is set to ON, gm/lsp is set from the port (m= line) contained in the remote descriptor of the opposite termination. tman/pdr If the Transport-Class corresponds to constant bit rate traffic, the tman/pdr property shall be equivalent to the b= line of the local descriptor or absent. If the Transport-Class corresponds to variable bit rate traffic, the tman/pdr property shall be equivalent to the b= line of the local descriptor. tman/mbs From Reservation-Class AVP tman/dvt From Reservation-Class AVP tman/sdr If the Transport-Class corresponds to constant bit rate traffic, this property shall be omitted or identical to tman/pdr. If the Transport-Class corresponds to variable bit rate traffic this property shall be derived from tman/pdr using rules specific to the transport class. tman/pol Set from the Transport-Class AVP. Local c= If NAPT-PT is activated, the address shall be assigned by the BGF. Otherwise the address is set from the contents of the remote descriptor of the opposite termination. See ES 283 018 [7] for the setting of other fields of the c= line. ETSI ETSI TS 183 048 V2.2.1 (2009-08) 12 Context parameters Descriptor Descriptor Descriptor Properties Population rules m= If NAPT-PT is activated, the port shall be assigned by the BGF. Otherwise the port is set from the contents of the remote descriptor of the opposite termination. See ES 283 018 [7] for the setting of other fields of the m= line. b= Shall be set from the Max-Requested-Bandwidth-UL or Max-Requested-Bandwidth-DL depending on the termination (upstream or downstream). (see note) Remote c= The address is set from the Flow-Description in Media-Component. Media-Sub-Component. See ES 283 018 [7] for the setting of other fields of the c= line. m= The port is set from the Flow-Description in Media-Component. Media-Sub-Component. See ES 283 018 [7] for the setting of other fields of the m= line. b= Shall be set from the Max-Requested-Bandwidth-UL or Max-Requested-Bandwidth-DL depending on the termination (upstream or downstream). (see note) NOTE: If gm/rsb is set to ON, the value of the AVPs associated to the RTCP flow shall be added.
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
5.2.1.2 Initial reservation for an session (SDP offer)
|
Upon reception of an initial AAR with connection information, the SPDF shall extract the connection information from the Media-Component-Description AVP(s). Each Media-Component-Descriptor AVP received (one per m= line or media stream) contains one or more Media-Sub-Component AVP(s) carrying a set of Flow-Descriptor AVP(s) that describe a unidirectional IP flow associated with the media stream. The SPDF shall from the set of Flow-Descriptor AVP(s) identify the direction of the corresponding IP flows i.e. uplink or downlink. The direction of each IP flow is given by the value of the direction attribute of the corresponding Flow-description AVP (i.e. "in" for uplink IP flows, and "out" for downlink IP flows). For each potential requesting application that requires the services of a BGF, the SPDF shall hold a local mapping table that enables SPDF to ensure, that both ephemeral terminations created for the session in the BGF are configured with connection information that matches appropriately the IP flow direction with the network interface connecting the ephemeral termination. In the P-CSCF case, an uplink IP flow originates from the UE served by the P-CSCF, and a downlink IP flow is directed towards the UE served by the P-CSCF. In the IBCF case, an uplink IP flow is directed from the local core network towards the peer core network, and a downlink IP flow is directed from the peer core network towards the local core network. The Binding-Input-List AVP shall be populated with an even number of V4-Transport-Address AVP or V6-Transport-Address list elements. The first list element in each pair of list elements applies to the access side and the second element applies to the core side. In case one of the V4-Transport-Address AVP or V6-Transport-Address AVP in such pair is unknown, an even number of list elements shall be still provided with the unknown V4-Transport-Address AVP or V6-Transport-Address AVP wild-carded. The above-given rules apply to the P-CSCF but are also valid for the IBCF provided that "access side" is replaced by "local core side" and "core side" by "peer core side". It shall be one pair of V4-Transport-Address AVP or V6-Transport-Address list elements in the Binding-Input-List AVP for each single Media-Component-Description AVP in an AAR. The list of such pairs shall be given in the same order as the list of Media-Component-Description AVPs. This provides an explicit coupling between each Media-Component-Description AVP, each pair of list elements in the Binding-Input-List AVP, and each pair of terminations in the BGF. ETSI ETSI TS 183 048 V2.2.1 (2009-08) 13 The following description for how to create ephemeral terminations applies to the P-CSCF but is also valid for the IBCF provided that "access network" is replaced by "local core network" and "core network" by "peer core network". After selection of the BGF to be contacted for the session, the SPDF requests initial configuration of the BGF to create a context with two ephemeral terminations: • ephemeral termination TA connecting the access network to the BGF; and • ephemeral termination TC connecting the core network to the BGF. H.248 Context H.248 Context TA Gate ⇔ TC Gate ⇔ Access Local Core Local Core Peer Core UL DL H.248 Context H.248 Context TA Gate ⇔ TC Gate ⇔ Access Local Core Local Core Peer Core UL DL Figure 5.2.1.2.1: BGF connection and flow model representation For connection information corresponding to a downlink IP flow, the SPDF shall: • on termination TA: - define one media stream per Media-Component-Description AVP occurrence (see note 1): for each media stream: - set the remote Descriptor to the corresponding destination IP and port address of the Flow-Description AVP marked with "out" direction and contained in the Media-Sub-Component AVP for which the Flow-Usage AVP is either absent or set to "no_information". • on termination TC: - define one media stream per Media-Component-Description AVP occurrence (see note 1): for each media stream: - if destination address NAPT(-PT) is activated for DL IP flows, request the BGF to select an IP and port address in the local Descriptor and store the selected value; - otherwise i.e. if destination address NAPT(-PT) is not activated for DL IP flows, set the local Descriptor to the value assigned to the remote Descriptor of termination TA; - optionally, configure the local control Descriptor with the gm/lsa and gm/lsp set to the value assigned to the remote Descriptor of termination TA (see note 2). For connection information corresponding to an uplink IP flow, the SPDF shall: • on termination TC: - define one media stream per Media-Component-Description AVP occurrence (see note 1): for each media stream: - set the remote Descriptor to the corresponding destination IP and port address of the Flow-Description AVP marked with "in" direction and contained in the Media-Sub-Component AVP for which the Flow-Usage AVP is either absent or set to "no_information". ETSI ETSI TS 183 048 V2.2.1 (2009-08) 14 • on termination TA: - define one media stream per Media-Component-Description AVP occurrence (see note 1): for each media stream: - if destination address NAPT(-PT) is activated for UL IP flows, request the BGF to select an IP and port address in the local Descriptor and store the selected value; - otherwise i.e. if destination address NAPT(-PT) is not activated for UL IP flows, set the local Descriptor to the value assigned to the remote Descriptor of termination TC; - Optionally, configure the local control Descriptor with the gm/lsa and gm/lsp properties set to the value assigned to the Remote Descriptor of termination TC (see note 3). NOTE 1: The SPDF can also specify additional media stream for RTCP this is described in ES 283 018 [7]. NOTE 2: This ensures that UL IP flows will be sent towards the core network using a source IP and port address identical to the address used by the UE for sending packets, assuming that the UE sends and receives packets using the same address and port. NOTE 3: This ensures that DL IP flows will be sent towards the access network using a source IP and port address identical to the address used to by the peer for sending packets, assuming that the peer sends and receives packets using the same address and port. If destination address NAPT(-PT) is activated for UL and/or DL IP flows, the SPDF shall return in the AAA message the list of IP and port address(es) selected by the BGF as local Descriptors in the Binding-Output-List AVP for each media stream in the same order as the corresponding Binding-Input-List AVP of the AAR message. That is, each address and port pair received in the local Descriptor shall be included in the Binding-Output-List AVP in the same position as the address and port pair that has been included in the remote Descriptor to which it is connected and was given in the Binding-Input-List AVP. Note that the addresses and ports in the same positions in the Binding-Input-List and the Binding-Output-List AVPs correspond to terminations at different sides of the BGF.
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
5.2.1.3 Connection information received from the opposite direction (SDP answer)
|
Upon reception of a subsequent AAR with connection information, the SPDF shall extract the connection information from the Media-Component-Description AVP(s). These operations are performed as described in the previous clause. The rules for how to populate the Binding-Input-List AVP and its relation to Media-Component-Description AVPs given in clause 5.2.1.3 apply also to this clause. The following description for how to create ephemeral terminations applies to the P-CSCF but is also valid for the IBCF provided that "access network" is replaced by "local core network" and "core network" by "peer core network". After selection of the BGF to be contacted for the session, the SPDF requests subsequent configuration of the context created within the BGF. For connection information corresponding to a downlink IP flow, SPDF shall: • modify termination TA: - for each media stream: set the remote Descriptor to the corresponding destination IP and port address of the Flow-Description AVP marked with "out" direction and contained in the Media-Sub-Component AVP for which the Flow-Usage AVP is either absent or set to "no_information". • modify termination TC: - for each media stream: if destination address NAPT(-PT) is activated for DL IP flows, request the BGF to select an IP and port address in the local Descriptor and store the selected value; otherwise i.e. if destination address NAPT(-PT) is not activated for DL IP flows, set the local Descriptor to the value assigned to the remote Descriptor of termination TA; ETSI ETSI TS 183 048 V2.2.1 (2009-08) 15 Optionally, configure the local control Descriptor with the gm/lsa and gm/lsp properties set to the value assigned to the Remote Descriptor of termination TA (see note 2). For connection information corresponding to an uplink IP flow, the SPDF shall: • modify termination TC: - for each media stream: set the remote Descriptor to the corresponding destination IP and port address of the Flow-Description AVP marked with "in" direction and contained in the Media-Sub-Component AVP for which the Flow-Usage AVP is either absent or set to "no_information". • modify termination TA: - for each media stream: if destination address NAPT(-PT) is activated for UL IP flows, request the BGF to select an IP and port address in the local Descriptor and store the selected value; otherwise i.e. if destination address NAPT(-PT) is not activated for UL IP flows, set the local Descriptor to the value assigned to the remote Descriptor of termination TC; Optionally, configure the local control Descriptor with the gm/lsa and gm/lsp set to the value assigned to the remote Descriptor of termination TC (see note 1). NOTE 1: This ensures that DL IP flows will be sent towards the access network using a source IP and port address identical to the address used to by the peer for sending packets, assuming that the peer sends and receives packets using the same address and port. NOTE 2: This ensures that UL IP flows will be sent towards the core network using a source IP and port address identical to the address used by the UE for sending packets, assuming that the UE sends and receives packets using the same address and port. If destination address NAPT(-PT) is activated for UL and/or DL IP flows, the SPDF shall return in the AAA message the list of IP and port address(es) selected by the BGF as local Descriptors in the Binding-Output-List AVP for each media stream in the same order as the corresponding Binding-Input-List AVP of the AAR message. That is, each address and port pair received in the local Descriptor shall be included in the Binding-Output-List AVP in the same position as the address and port pair that has been included in the remote Descriptor to which it is connected and was given in the Binding-Input-List AVP. Note that the addresses and ports in the same positions in the Binding-Input-List and the Binding-Output-List AVPs correspond to terminations at different sides of the BGF. 5.2.1.4 Connection information (SDP answer) received corresponding to multiple early dialogues The SPDF may receive more than one AAR with SDP answer connection info in case the AF identifies that multiple early dialogues are being created. These AAR will be marked with a SIP-Forking-Indication AVP set to value SEVERAL_DIALOGUES. The SPDF shall request resources from the BGF as if this was an AAR (SDP answer) without Forking-Indication but shall be prepared to restore QoS requirements for one of the early dialogues. The final dialogue is identified when an AAR (SDP answer) is received without the SIP-Forking-Indication AVP.
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
5.2.1.5 BGF Media Transcoding
|
The BGF media transcoding abilities can be triggered by the Application Function (AF) in order to resolve codec incompatibilities between UEs or administratively through local configuration in order to enforce the use of specific codecs within the core network. If used to resolve codec incompatibilities between UEs, the procedures for Media Transcoding control described in TS 124 229 [8], clause 5.10.7.2 (Media transcoding control procedures) apply. If used to administratively enforce the use of specific codecs within a core network, local configuration may trigger the BGF to transcode media going in to and out of the core network. ETSI ETSI TS 183 048 V2.2.1 (2009-08) 16
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
5.2.1.6 BGF transport plane failure detection
|
When detecting a transport plane event (like loss of RTP on an ephemeral termination), the BGF can send a Notify command to the SPDF indicating the cause of the event. In order for this to happen, the SPDF must first indicate that it wishes to be notified about the event in question. This is achieved by including the particular event in the Events descriptor in an Add or Modify request (depending on the type of event). When the SPDF receives notification of an event from the BGF, the SPDF can take appropriate action. It notifies the application function (P-CSCF A) which in turn terminates the session between the affected UEs. It then releases the resources affected by the event. The AF uses the Specific-Action AVP in the AA-Request to indicate which events it wants to be informed of.
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
5.2.2 Reservation with x-RACF involved
|
The SPDF may provide different amounts of information over Rq to the x-RACF depending on the particular service being requested by the AF over Gq'. For example, for services that do not involve an policy enforcement in the RCEF, port numbers are not needed and may hence be left out by the SPDF for signalling over Rq although ports numbers are present in Gq' (and Ia) signalling. However, the recommended behaviour of the SPDF is to always provide complete information over Rq to the x-RACF. This is to avoid making the SPDF aware of x-RACF operations for different services and requiring it to operate differently for different services. Some AVPs are transparently forwarded by the SPDF between the Gq' and Rq interfaces, while SPDF policies are applied to other AVPs, which consequently may be altered by the SPDF before it signals to the x-RACF. The following AVPs are forwarded transparently by the SPDF over Rq to the x-RACF: • Media-Component-Description: - Media-Component-Number. - Media-Sub-Component. - AF-Application-Identifier. - Media-Type. - Max-Requested-Bandwidth-UL. - Max-Requested-Bandwidth-DL. - Flow-Status. - RS-Bandwidth. - RR-Bandwidth. - Codec-Data. • Flow-Grouping. • AF-Charging-Identifier. • User-Name. • Globally-Unique-Address. • Overbooking-indicator. ETSI ETSI TS 183 048 V2.2.1 (2009-08) 17 The following AVPs may be altered by the SPDF before signalled to the x-RACF (AVPs with no specific information on the mapping may be mapped to a different value based on local configuration): • Media-Component-Description: - Reservation-Class. - Reservation-Priority. - Transport-Class. - Media-Authorization-Context-Id. • Specific-Action: INDICATION_OF_RELEASE_OF_BEARER shall be forwarded without change over Rq, while INDICATION_OF_LOSS_OF_BEARER and INDICATION_OF_RECOVERY_OF_BEARER shall not be forwarded over Rq at all (i.e. these values concerns BGF service only). The SPDF may decide to include INDICATION_OF_SUBSCRIBER_DETACHMENT and/or INDICATION_OF_RESERVATION_EXPIRATION values in Specific-Action AVPs sent over Rq to subscribe to the corresponding information from the x-RACF. These values are however not reported to the AF over Gq'. • Reservation-Priority. • Service-Class. • Authorization-Lifetime. Should not by mapped to a value smaller than provided over Gq'. This would require the SPDF to periodically refresh session state in the x-RACF without being triggered by messages over Gq'. • Authorization-Package-Id.
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
5.2.3 Reservation involving both x-RACF and BGF
|
The signalling flow when both the x-RACF and BGF are involved is a combination of the procedures for accessing the BGF specified in clause 5.2.1 and the procedures for accessing the x-RACF specified clause 5.2.2 and in ES 283 026 [3]. The sequence used by the SPDF to access x-RACF and BGF is a local decision in the SPDF, e.g. the SPDF is able to decide whether to access the x-RACF and then the BGF, or vice versa, or both in parallel. This is valid for request, modification and release. However, the SPDF may need to interrogate the BGF before the x-RACF to firstly obtain local termination IP addresses and ports from the BGF to thereafter provide them to the x-RACF. This is needed when the x-RACF performs resource and admission control for the network segment between the RCEF and the C-BGF, and when the RCEF shall be instructed to perform policy enforcement on source IP addresses and ports. When both x-RACF and BGF Functional Entities (FEs) are involved in a session, the SPDF needs to keep the previous service information before each resource modification operation. In case the resource modification operation succeeds in one or more external FEs but fails in a later FE, after receiving the modification failure response from the FE which fails in the modification, the SPDF is responsible to control all the relevant external FEs to recover. If any of the external FEs cannot recover by itself because of not keeping the previous state, the SPDF sends the previous corresponding service information to the FE for the FE to recover. In case the resource modification operation succeeds in all of the external FEs, the SPDF should remove the previous service information immediately for most scenarios. In certain scenarios where the resource modification is a preliminary operation (e.g. when a subsequent SDP answer from a remote UE is required to confirm the modification), the SPDF may need to keep the previous service information for a certain period in case the information is needed in the rollback procedures when the UE denies the modification. ETSI ETSI TS 183 048 V2.2.1 (2009-08) 18
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
5.3 Procedures at x-RACF
|
The x-RACF determines based on local configuration whether or not the RCEF service shall be requested for sessions established via Rq. The x-RACF may use information provided by the SPDF over Rq for this decision, but can also be configured to request service from the RCEF for all sessions established over Rq. In case RCEF service is needed for a particular session, the x-RACF request service for Re messages with the Flow-Status AVP set to ENABLED.
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
5.3.1 Determining RCEF involvement
|
In case the RCEF involvement is dynamically determined from Rq messages, one or more of the following AVPs are used by the x-RACF to decide whether or not to request service from the RCEF: • Reservation-Priority. • User-Name. • Globally-Unique-Address. • Service-Class. • Authorization-Package-Id. • AF-Application-Identifier. • Media-Type. • Reservation-Class. • Transport-Class. • Media-Authorization-Context-Id.
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
5.3.2 Reporting RCEF failure
|
In case of failure in activating the requested policy with a PI-Request, the value of the Rule-Failure-Code AVP reported over Re may be carried in the Error-Message AVP to report the failure over Rq and Gq'. In case the RCEF deactivates a policy with a CC-Request, any value of the Termination-Cause AVP reported over Re shall be translated into the BEARER_RELEASED value of the Abort-Cause AVP reported over Rq and Gq'.
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
5.3.3 Multicast authorization
|
When the x-RACF receives an Authorization-Package-Id AVP or a Media-Authorization-Context-Id AVP over Rq, it shall map the received AVP to information that is locally preconfigured on the allowed IP multicast addresses and ports for the currently authorized application service. These addresses are further used to populate the required number of Flow-Description AVPs in the corresponding PI-Request over Re.
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
5.4 Diameter request routing considerations
|
The same IETF vendor specific Diameter application with application ID 16777222 (vendor 3GPP) is reused for both the Gq' and Rq reference points. Since Diameter agents use the Auth-Application-Id AVP to decide where to forward a Diameter Gq' or Rq initial request, normal request routing rules do not apply due to the ambiguity of whether to forward the initial request to the SPDF or to the x-RACF. Use of the Destination-Host AVP is therefore advised when forwarding an initial request using a Diameter agent. NOTE: Use of the Destination-Host AVP in the AA-Request command is permitted implicitly through the *[AVP] construct in the definition of the AA-Request command in [4], clause 7.1.1 and according to the normal Diameter request routing procedures described in [11], section 6.1. ETSI ETSI TS 183 048 V2.2.1 (2009-08) 19
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
6 Example signalling flows (informative)
|
The examples of stage 3 signalling flows for TISPAN NGN release 2 provided by the present document cover signalling between AFs and RACS as well as signalling within RACS. In addition, signalling between different AF entities are shown to clarify when RACS is interrogated for the illustrated signalling examples. The signalling between AF entities is however not complete for all signalling examples in the sense that some messages between AF entities are omitted for brevity.
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
6.1 Basic IMS end-to-end signalling flow
|
Figure 6.1.1 illustrates the example network architecture. Figure 6.1.1: IMS end-to-end signalling flow between two SIP end-points - without IBGF As indicated in [1] RTP should use an even destination port number and the corresponding RTCP stream should use the next higher (odd) destination port number. Following these recommendations the addresses and ports used in the example are as follows: • A1 = Voice: 192.168.0.2:23942 for RTP and 192.168.0.2:23943 for RTCP. • A1 = Video: 192.168.0.2:51372 for RTP and 192.168.0.2:51373 for RTCP. • A2 = Voice: 192.168.0.1:4444 for RTP and 192.168.0.1:4445 for RTCP. • A2 = Video: 192.168.0.1:31444 for RTP and 192.168.0.1:31445 for RTCP. • A3 = Voice: 10.0.0.1:2222 for RTP and 10.0.0.1:2223 for RTCP. • A3 = Video: 10.0.0.1:17462 for RTP and 10.0.0.1:17463 for RTCP. • B1 = Voice: 192.168.1.2:29792 for RTP and 192.168.1.2:29793 for RTCP. • B1 = Video: 192.168.1.2:25552 for RTP and 192.168.1.2:25553 for RTCP. • B2 = Voice: 192.168.1.1:3332 for RTP and 192.168.1.1:3333 for RTCP. • B2 = Video: 192.168.1.1:32124 for RTP and 192.168.1.1:32125 for RTCP. • B3 = Voice: 10.0.0.2:1110 for RTP and 10.0.0.2:1111 for RTCP. • B3 = Video: 10.0.0.2:1612 for RTP and 10.0.0.2:1613 for RTCP. • C = 10.0.1.1:5555 for RTP and 10.0.1.1:5556 for RTCP. ETSI ETSI TS 183 048 V2.2.1 (2009-08) 20 The RTP stream is assumed to consume 96 kbps, while the RTCP is assumed to use 8 kbps. No packet loss occurs. The statistics are approximately chosen in the message flows. Identifiers used in the examples are selected to follow the formats defined for the respective protocols. Figure 6.1.2 focuses on the two C-BGF entities, which are H.248-controlled MG entities, and highlights the "BGF Connection Model", which relates to single H.248 Contexts with each two H.248 IP terminations. It has to be noted that figure 6.1.2 is just an example, indicating only the single H.248 Stream solution for RTP and RTCP together. NOTE: The picture highlights the BGF Connection models. Figure 6.1.2: Simplified network model with focus on BGF entities only H.248 Context H.248 Context H.248 MG: C- BGF A TA A Gate ⇔ TA B Gate ⇔ H.248 Context H.248 Context H.248 MG: C- BGF A TA A Gate ⇔ TA B Gate ⇔ H.248 Context H.248 Context H.248 MG: C -BGF B TB A Gate ⇔ TB B Gate ⇔ H.248 Context H.248 Context H.248 MG: C -BGF B TB A Gate ⇔ TB B Gate ⇔ SIP UA: Phone B SIP UA: Phone A IP Realm “A" IF1 IP Realm “Core" IF1 IF2 IP Realm “B" IF2 This H.248 Context is created in steps 3/4, and again modified in steps 43/44. This H.248 Context is created in steps 11/12, and again modified in steps 19/20 and 51/52. 192.168.0.x 192.168.1.x 10.0.0.x ETSI ETSI TS 183 048 V2.2.1 (2009-08) 21
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
6.1.1 Session setup
|
Phone A P-CSCF A S-CSCF SPDF A A-RACF A C-BGF A Phone B P-CSCF B SPDF B A-RACF B C-BGF B INVITE B AAR Add Termination Reply AAR AAA AAA INVITE B INVITE B AAR Add Termination Reply AAR AAA AAA INVITE B 180 Ringing AAR Modify Termination Reply AAR AAA AAA 200 OK 200 OK AAR Modify Termination Reply AAR AAA AAA 200 OK ACK ACK ACK ACK BIDIRECTIONAL RTP DATA RCEF A RCEF B PIR PIA PIR PIA 100 Trying 1 2 4 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 100 Trying 100 Trying 180 Ringing 180 Ringing 180 Ringing 200 OK 1 2 4 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 Figure 6.1.1.1: IMS end-to-end signalling chart between two SIP end-points - session setup ETSI ETSI TS 183 048 V2.2.1 (2009-08) 22 Table 6.1.1.1: IMS end-to-end messages between two SIP end-points - session setup Step Protocol Interface From To Message 1 SIP Phone A P-CSCF A INVITE B INVITE sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 70 Route: <sip:p-cscf-a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_a@phone-a.example.com> Content-Type: application/sdp Content-Length: 129 v=0 o=user_a 2890844526 2890842807 IN IP4 phone-a.example.com s=- c=IN IP4 192.168.0.2 t=0 0 m=audio 23942 RTP/AVP 0 a=sendrecv 2 SIP P-CSCF A Phone A 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Content-Length: 0 3 DIAMETER Gq' P-CSCF A SPDF A AAR The P-CSCF uses the IP address registered for signalling as the Globally-Unique-Address. The Gq' protocol specification [4] and the Rq protocol specification [3] both specify rules for how to assign numbers to the Flow-Number AVP and Media-Component-Number AVP respectively. The Flow-Number AVP is specified as the ordinal number of the IP flow(s), assigned according to the rules in annex C of [2] and the Media-Component-Number AVP is specified as the ordinal number of the media component, assigned according to the rules in annex C of [2]. In annex C.1 in [2] it is stated that both these numbers are to start at 1 for a given session. Following the rules defined in clause 4, the P-CSCF translates the single codec indicated in the m= line to bandwidth using locally configured information on the mapping between codec and bandwidth taking account for the packetization overhead (i.e. AVP/RTP 0 translates to PCMU/8000, which is 64 kbps that becomes 96 kbps plus 8 kbps with packetization overhead). Given the reception of a=sendrecv in the SDP the P-CSCF issues a bi-directional reservation request to the SPDF. Following the rules given in clause 5.2.1.3 the Binding-Information AVPs are set to 0.0.0.0 and 0 respectively since no addresses or ports at the core side is available. <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-a.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from any to 192.168.0.2 23942" ] [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 96000 ] [ Max-Requested-Bandwidth-UL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from any to 192.168.0.2 23943" ] [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-DL = 8000 ] [ Max-Requested-Bandwidth-UL = 8000 ] ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 23 Step Protocol Interface From To Message [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "uplink offer m=audio 23942 RTP/AVP 0" ] ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 23942 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 23943 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] } ] [ Reservation-Priority = DEFAULT (0) ][ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 4 H.248 Ia SPDF A C-BGF A Add terminations The default value of H.248 StreamMode is "Inactive", the H.248 Streams are by default created as "Inactive". Hence, the Mode descriptor is omitted in this message. The Diameter <AA-Request> for an RTP flow and an RTCP flow is translated here into an H.248 Termination/Stream model by using the default RTP Specific behaviour of the BGF. The specific behaviour is controlled via the gm/rsb ("RTP Specific Behaviour") property. This property is disabled by default in version 2 of the H.248/Ia protocol profile so it must be explicitly enabled in order to allocate a port for the RTCP flow. Alternatively, RTCP port allocation could be controlled by the presence of an "a=rtcp" descriptor attribute as described in 5.17.1.7.1 in [7]. Alternatively, the RTP and RTCP flows could be mapped on two separate H.248 Streams (clause 5.17.1.1 in [7]). The media type is implicitly provided as audio in the "m="-line by the payload type field (payload type 0 implies PCMU audio data). If the signalled BGF mode is media type aware, the "m="-line can also be written as: "m=audio <port number or ‘$'> RTP/AVP 0". If the signalled BGF mode is media agnostic, the "m="-line should be written as: "m=- $ - -" (e.g. as the only option in version 1 of the H.248 Ia profile). NOTE 1: The port number provided in the Gq' Codec-Data AVP is not used to populate Local or Remote descriptors since the port number may be incorrect due to Network Address Translation. MEGACO/3 [spdf-a.example.com]:55555 Transaction = 1 { Context = ${ Add = ip/1/$/$ { /* NOTE 1 */ Media { Stream = 1 { LocalControl { ipdc/realm = "A", gm/rsb = ON } Local { v=0 m=- $ RTP/AVP 0 c=IN IP4 $ b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 192.168.0.2 s=- ETSI ETSI TS 183 048 V2.2.1 (2009-08) 24 Step Protocol Interface From To Message t=0 0 m=- 23942 RTP/AVP 0 c=IN IP4 192.168.0.2 b=AS:104 } } /* Stream */ } /* Media */ } /* Add */ Add = ip/1/$/$ { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 m=- $ RTP/AVP 0 c=IN IP4 $ b=AS:104 } } /* Stream */ } /* Media */ } /* Add */ } /* Context */ } /* Transaction */ NOTE 2: The wildcard CHOOSE must be used for the interface part of the termination id. With the exception of the interface field, only the "Id" part may be wildcarded (see table 4 in [7]). 5 H.248 Ia C-BGF A SPDF A Reply (Add) It should be noted that H.248 replies typically contain only new information not previously given in preceding H.248 request triggering the replies. The following H.248 message and all other H.248 replies shown in the present document includes however all information offered in the H.248 request together with the new information created by the BGF. The complete information is shown to clearly illustrate the interaction between the SPDF and the BGF for the depicted scenario. MEGACO/3 [abgf-a.example.com]:55555 Reply = 1 { Context = 1 { Add = ip/1/if1/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "A", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 192.168.0.1 s=- t=0 0 m=- 4444 RTP/AVP 0 c=IN IP4 192.168.0.1 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 192.168.0.2 s=- t=0 0 m=- 23942 RTP/AVP 0 c=IN IP4 192.168.0.2 b=AS:104 } } /* Stream */ } /* Media */ } /* Add */ Add = ip/1/if2/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 25 Step Protocol Interface From To Message o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 2222 RTP/AVP 0 c=IN IP4 10.0.0.1 b=AS:104 } } /* Stream */ } /* Media */ } /* Add */ } /* Context */ } /* Reply */ NOTE 3: The origin, session name and time (o=, s= and t=) SDP information elements are optional when sent from the SPDF to the BGF but the SPDF shall accept them in command responses from the BGF according to clause 7.1.8 in [12]. NOTE 4: It is mandatory for the BGF to include the o=, s= and t= information elements in the Local Descriptor in command responses. If supplied by the SPDF in the initial command, the BGF must return the same values in the command response. 6 DIAMETER Rq SPDF A A-RACF A AAR The A-RACF does not need the port numbers in this step. They are however needed for this signalling scenario in later steps when it interrogates the RCEF over Re for policy enforcement. These numbers should be included in all Rq AAR commands even if Re is not used since that is the desired default behaviour. That is, the SPDF should not need to keep track of whether or not port numbers are needed. It should be noted that although source IP addresses are not provided the A-RACF can determine the sources from the Globally-Unique-Address of the subscriber (i.e. the A-RACF knows the location of each subscriber as this identifier comes associated with a Logical-Access-ID from the CLF over e4). The SPDF uses the local IP address and port at if2 obtained from the C-BGF in its request over Rq. This is to facilitate resource and admission control to resources in the network between the RCEF and the C-BGF for cases when the A-RACF cannot determine the correct interface at the C-BGF by other means. <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "aracf-a.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from 192.168.0.1 4444 to 192.168.0.2 23942" ] [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 96000 ] [ Max-Requested-Bandwidth-UL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from 192.168.0.1 4445 to 192.168.0.2 23943" ] [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-DL = 8000 ] [ Max-Requested-Bandwidth-UL = 8000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 26 Step Protocol Interface From To Message 7 DIAMETER Rq A-RACF A SPDF A AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 8 DIAMETER Gq' SPDF A P-CSCF A AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 23942 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 23943 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2222 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2223 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] ] ] ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 27 Step Protocol Interface From To Message 9 SIP P-CSCF A S-CSCF INVITE B INVITE sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 69 Record-Route: <sip:p-cscf-a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_a@phone-a.example.com> Content-Type: application/sdp Content-Length: 129 v=0 o=user_a 2890844526 2890842807 IN IP4 phone-a.example.com s=- c=IN IP4 10.0.0.1 t=0 0 m=audio 2222 RTP/AVP 0 a=sendrecv 10 SIP S-CSCF P-CSCF A 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Content-Length: 0 11 SIP S-CSCF P-CSCF B INVITE B INVITE sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 68 Record-Route: <sip:s-cscf.example.com;lr>,<sip:p-cscf-a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_a@phone-a.example.com> Content-Type: application/sdp Content-Length: 125 v=0 o=user_a 2890844526 2890842807 IN IP4 phone-a.example.com s=- c=IN IP4 10.0.0.1 t=0 0 m=audio 2222 RTP/AVP 0 a=sendrecv 12 SIP S-CSCF P-CSCF B 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 28 Step Protocol Interface From To Message 13 DIAMETER Gq' P-CSCF B SPDF B AAR It should be noted that the IP address registered for signalling, which equals the Globally Unique IP Address, cannot be safely assumed to also be the source IP address for media. Hence, using this address as the source address for media may cause problems in case source filtering is applied. For this reason no source IP address is provided although the IP address registered for signalling to Phone B may be the same source IP address used for media. <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-b.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Description = "permit out 17 from any to any" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 96000 ] [ Max-Requested-Bandwidth-DL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Description = "permit out 17 from any to any" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-UL = 8000 ] [ Max-Requested-Bandwidth-DL = 8000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "downlink offer m=audio 2222 RTP/AVP 0" ] ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2222 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2223 } ] } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 29 Step Protocol Interface From To Message 14 H.248 Ia SPDF B C-BGF B Add terminations MEGACO/3 [spdf-b.example.com]:43924 Transaction = 1 { Context = $ { Add = ip/1/$/$ { Media { Stream = 1 { LocalControl { ipdc/realm = "B", gm/rsb = ON } Local { v=0 m=- $ RTP/AVP 0 c=IN IP4 $ b=AS:104 } } /* Stream */ } /* Media */ } /* Add */ Add = ip/1/$/$ { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 m=- $ RTP/AVP 0 c=IN IP4 $ b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 2222 RTP/AVP 0 c=IN IP4 10.0.0.1 b=AS:104 } } /* Stream */ } /* Media */ } /* Add */ } /* Context */ } /* Transaction */ 15 H.248 Ia C-BGF B SPDF B Reply (Add) MEGACO/3 [abgf-b.example.com]:43924 Reply = 1 { Context = 1 { Add = ip/1/if1/1{ Media { Stream = 1 { LocalControl { ipdc/realm = "B", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 192.168.1.1 s=- t=0 0 m=- 3332 RTP/AVP c=IN IP4 192.168.1.1 b=AS:104 } } /* Stream */ } /* Media */ } /* Add */ Add = ip/1/if2/1{ Media { Stream = 1 { LocalControl { ETSI ETSI TS 183 048 V2.2.1 (2009-08) 30 Step Protocol Interface From To Message ipdc/realm = "Core", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 m=- 1110 RTP/AVP 0 c=IN IP4 10.0.0.2 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 2222 RTP/AVP 0 c=IN IP4 10.0.0.1 b=AS:104 } } /* Stream */ } /* Media */ } /* Add */ } /* Context */ } /* Reply */ 16 DIAMETER Rq SPDF B A-RACF B AAR The A-RACF determines the access line from the Globally-Unique-Address AVP since the source and destination IP addresses for that reservation endpoint are not given in the request (i.e. they are both set to "any"). <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "aracf-b.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 17 from any to 192.168.1.1 3332" ] [ Flow-Description = "permit out 17 from any to any" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 96000 ] [ Max-Requested-Bandwidth-DL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit in 17 from any to 192.168.1.1 3333" ] [ Flow-Description = "permit out 17 from any to any" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-UL = 8000 ] [ Max-Requested-Bandwidth-DL = 8000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 31 Step Protocol Interface From To Message 17 DIAMETER Rq A-RACF B SPDF B AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 18 DIAMETER Gq' SPDF B P-CSCF B AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2222 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2223 } ] } [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 3332 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 3333 } ] ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 32 Step Protocol Interface From To Message 19 SIP P-CSCF B Phone B INVITE B INVITE sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 67 Record-Route: <sip:p-cscf-b.example.com;lr>,<sip:s-cscf.example.com;lr>,<sip:p-cscf- a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_a@phone-a.example.com> Content-Type: application/sdp Content-Length: 128 v=0 o=user_a 2890844526 2890842807 IN IP4 phone-a.example.com s=- c=IN IP4 192.168.1.1 t=0 0 m=audio 3332 RTP/AVP 0 a=sendrecv 20 SIP Phone B P-CSCF B 180 Ringing SIP/2.0 180 Ringing Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Record-Route: <sip:p-cscf-b.example.com;lr>,<sip:s-cscf.example.com;lr>,<sip:p-cscf- a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com Contact: <sip:user_b@phone-b.example.com> CSeq: 1 INVITE Content-Type: application/sdp Content-Length: 0 21 SIP P-CSCF B S-CSCF 180 Ringing SIP/2.0 180 Ringing Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Record-Route: <sip:s-cscf.example.com;lr>,<sip:p-cscf-a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com Contact: <sip:user_b@phone-b.example.com> CSeq: 1 INVITE Content-Type: application/sdp Content-Length: 0 22 SIP S-CSCF P-CSCF A 180 Ringing SIP/2.0 180 Ringing Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Record-Route: <sip:p-cscf-a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com Contact: <sip:user_b@phone-b.example.com> CSeq: 1 INVITE Content-Type: application/sdp Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 33 Step Protocol Interface From To Message 23 SIP P-CSCF A Phone A 180 Ringing SIP/2.0 180 Ringing Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Record-Route: <sip:p-cscf-a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com Contact: <sip:user_b@phone-b.example.com> CSeq: 1 INVITE Content-Type: application/sdp Content-Length: 0 24 SIP Phone B P-CSCF B 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 70 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_b@phone-b.example.com> Content-Type: application/sdp Content-Length: 119 v=0 o=user_b 29381748101 2948193018 IN IP4 phone-b.example.com s=- c=IN IP4 192.168.1.2 t=0 0 m=audio 29792 RTP/AVP 0 25 DIAMETER Gq' P-CSCF B SPDF B AAR (Modify) In this AAR modifying an existing session both in and out Flow-Description AVPs and both the Max-Requested-Bandwidth-UL and the Max-Requested-Bandwidth-DL are provided in the request. Although this may seem be redundant information (as the in Flow-Description AVP and Max-Requested-Bandwidth-UL are already provided to RACS) the Gq' specification does not explicitly allow any of those AVPs to be omitted. Hence, they are all included. <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-b.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from any to 192.168.1.2 29792" ] [ Flow-Description = "permit in 17 from any to 192.168.1.1 3332" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 96000 ] [ Max-Requested-Bandwidth-UL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from any to 192.168.1.2 29793" ] [ Flow-Description = "permit in 17 from any to 192.168.1.1 3333" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-DL = 8000 ] [ Max-Requested-Bandwidth-UL = 8000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = ENABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "uplink answer m=audio 29792 RTP/AVP 0" ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 34 Step Protocol Interface From To Message [ Codec-Data = "downlink offer m=audio 3333 RTP/AVP 0" ] ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 29792 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2222 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 29793 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2223 } ] } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 26 H.248 Ia SPDF B C-BGF B Modify terminations MEGACO/3 [spdf-b.example.com]:43924 Transaction = 2 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "B", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 192.168.1.1 s=- t=0 0 m=- 3332 RTP/AVP 0 c=IN IP4 192.168.1.1 b=AS:104 } Remote { v=0 o=- 0 0 IN IP4 192.168.1.2 s=- t=0 0 m=- 29792 RTP/AVP 0 c=IN IP4 192.168.1.2 b=AS:104 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.0.2 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 35 Step Protocol Interface From To Message s=- t=0 0 m=- 1110 RTP/AVP 0 c=IN IP4 10.0.0.2 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 2222 RTP/AVP 0 c=IN IP4 10.0.0.1 b=AS:104 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Transaction */ 27 H.248 Ia C-BGF B SPDF B Reply (Modify) MEGACO/3 [abgf-b.example.com]: 43924 Reply = 2 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "B", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 192.168.1.1 s=- t=0 0 m=- 3332 RTP/AVP 0 c=IN IP4 192.168.1.1 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 192.168.1.2 s=- t=0 0 m=- 29792 RTP/AVP 0 c=IN IP4 192.168.1.2 b=AS:104 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = SendReceive }, Local { v=0 m=- 1110 RTP/AVP 0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 c=IN IP4 10.0.0.2 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 36 Step Protocol Interface From To Message m=- 2222 RTP/AVP 0 c=IN IP4 10.0.0.1 b=AS:104 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Reply */ 28 DIAMETER Rq SPDF B A-RACF B AAR (Modify) <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "aracf-b.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from 192.168.1.1 3332 to 192.168.1.2 29792" ] [ Flow-Description = "permit in 17 from 192.168.1.2 29792 to 192.168.1.1 3332" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 96000 ] [ Max-Requested-Bandwidth-DL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from 192.168.1.1 3333 to 192.168.1.2 29793" ] [ Flow-Description = "permit in 17 from 192.168.1.2 29793 to 192.168.1.1 3333" ] [ Flow-Usage = RTCP(1) ] [ Max-Requested-Bandwidth-UL = 8000 ] [ Max-Requested-Bandwidth-DL = 8000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = ENABLED } [ Reservation-Priority = DEFAULT (0) ] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 29 DIAMETER Re A-RACF B RCEF B PIR The Origin-State-Id AVP is left out of this command since the A-RACF is a statefull entity that can be assumed to preserve states at restart or failover to a backup entity. In that case, it is not an entity that always starts up with no active sessions and thereby it does not need this AVP [11]. The ToS-Traffic-Class AVP is set to 101110, which is the codepoint allocated by IANA for the EF DiffServ per-hop behaviour [13]. This value is herein provided as an example only. < PI-Request > ::= < Diameter Header: 315, REQ, PXY > < Session-Id = "aracf-b.example.com;66389;469" > { Auth-Application-Id = 16777253 (Re) } { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Destination-Host = "rcef-b.example.com" } { PI-Request-Type = INITIAL_REQUEST } { PI-Request-Number = 0 } [ Auth-Session-State = NO_STATE_MAINTAINED (1) ] [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-B-UL" } [ Service-Identifier = 1 ] [ Rating-Group = 1 ] [ Framed-IP-Address = 192.168.1.2 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 37 Step Protocol Interface From To Message [ Address-Realm = "example.com" ] [ Flow-Description = "permit in 17 from 192.168.1.2 29792 to 192.168.1.1 3332" ] [ Flow-Description = "permit in 17 from 192.168.1.2 29793 to 192.168.1.1 3333" ] [ Flow-Status = ENABLED-UPLINK (0) ] [ QoS-Information = [ Max-Requested-Bandwidth-UL = 104000 ] [ ToS-Traffic-Class = 101110 ] ] [ Precedence = 1] [ Flows = { Media-Component-Number = 1 } [ Flow-Number = 1 ] [ Flow-Number = 2 ] ] ] ] [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-B-DL" } [ Service-Identifier = 1 ] [ Rating-Group = 1 ] [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] [ Flow-Description = "permit out 17 from 192.168.1.1 3332 to 192.168.1.2 29792" ] [ Flow-Description = "permit out 17 from 192.168.1.1 3333 to 192.168.1.2 29793" ] [ Flow-Status = ENABLED-DOWNLINK (1) ] [ QoS-Information = [ Max-Requested-Bandwidth-DL = 104000 ] [ ToS-Traffic-Class = 101110 ] ] [ Precedence = 1] [ Flows = { Media-Component-Number = 1 } [ Flow-Number = 1 ] [ Flow-Number = 2 ] ] ] ] 30 DIAMETER Re RCEF B A-RACF B PIA <PI-Answer> ::= < Diameter Header: 315, PXY > < Session-Id = "aracf-b.example.com;66389;469" > { Origin-Host = "rcef-b.example.com" } { Origin-Realm = "example.com" } { PI-Request-Type = INITIAL_REQUEST } { PI-Request-Number = 0 } [ Result-Code DIAMETER_SUCCESS (2001) ] 31 DIAMETER Rq A-RACF B SPDF B AAA (Modify) <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 32 DIAMETER Gq' SPDF B P-CSCF B AAA (Modify) <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } ETSI ETSI TS 183 048 V2.2.1 (2009-08) 38 Step Protocol Interface From To Message { Port-Number = 29792 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2222 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 29793 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2223 } ] } [ Binding-Output-List = 10.0.0.2 [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1110 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 3332 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1111 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 3333 } ] ] ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 33 SIP P-CSCF B S-CSCF 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 69 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_b@phone-b.example.com> Content-Type: application/sdp Content-Length: 126 v=0 o=user_b 29381748101 2948193018 IN IP4 phone-b.example.com s=- c=IN IP4 10.0.0.2 t=0 0 m=audio 1110 RTP/AVP 0 a=sendrecv ETSI ETSI TS 183 048 V2.2.1 (2009-08) 39 Step Protocol Interface From To Message 34 SIP S-CSCF P-CSCF A 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 68 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_b@phone-b.example.com> Content-Type: application/sdp Content-Length: 126 v=0 o=user_b 29381748101 2948193018 IN IP4 phone-b.example.com s=- c=IN IP4 10.0.0.2 t=0 0 m=audio 1110 RTP/AVP 0 a=sendrecv 35 DIAMETER Gq' P-CSCF A SPDF A AAR (Modify) <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-a.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Description = "permit out 17 from any to 192.168.0.2 23942" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 96000 ] [ Max-Requested-Bandwidth-DL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Description = "permit out 17 from any to 192.168.0.2 23943" ] [ Flow-Usage = RTCP(1) ] [ Max-Requested-Bandwidth-UL = 8000 ] [ Max-Requested-Bandwidth-DL = 8000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = ENABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "uplink offer m=audio 23942 RTP/AVP 0" ] ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 23942 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1110 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 23943 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1111 } ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 40 Step Protocol Interface From To Message } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 36 H.248 Ia SPDF A C-BGF A Modify Terminations A (A to B) MEGACO/3 [spdf-a.example.com]:55555 Transaction = 2 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "A", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 192.168.0.1 s=- t=0 0 m=- 4444 RTP/AVP 0 c=IN IP4 192.168.0.1 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 192.168.0.2 s=- t=0 0 m=- 23942 RTP/AVP 0 c=IN IP4 192.168.0.2 b=AS:104 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 2222 RTP/AVP 0 c=IN IP4 10.0.0.1 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 m=- 1110 RTP/AVP 0 c=IN IP4 10.0.0.2 b=AS:104 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Transaction */ ETSI ETSI TS 183 048 V2.2.1 (2009-08) 41 Step Protocol Interface From To Message 37 H.248 Ia C-BGF A SPDF A Reply (Modify) MEGACO/3 [abgf-a.example.com]:55555 Reply = 2 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "A", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 192.168.0.1 s=- t=0 0 m=- 4444 RTP/AVP 0 c=IN IP4 192.168.0.1 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 192.168.0.2 s=- t=0 0 m=- 23942 RTP/AVP 0 c=IN IP4 192.168.0.2 b=AS:104 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 2222 RTP/AVP 0 c=IN IP4 10.0.0.1 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 m=- 1110 RTP/AVP 0 c=IN IP4 10.0.0.2 b=AS:104 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Reply */ ETSI ETSI TS 183 048 V2.2.1 (2009-08) 42 Step Protocol Interface From To Message 38 DIAMETER Rq SPDF A A-RACF A AAR (Modify) <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "aracf-a.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from 192.168.0.1 4444 to 192.168.0.2 23942" ] [ Flow-Description = "permit in 17 from 192.168.0.2 23942 to 192.168.0.1 4444" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 96000 ] [ Max-Requested-Bandwidth-DL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from 192.168.0.1 4445 to 192.168.0.2 23943" ] [ Flow-Description = "permit in 17 from 192.168.0.2 23943 to 192.168.0.1 4445" ] [ Flow-Usage = RTCP(1) ] [ Max-Requested-Bandwidth-UL = 8000 ] [ Max-Requested-Bandwidth-DL = 8000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = ENABLED ] [ Reservation-Priority = DEFAULT (0) ] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 39 DIAMETER Re A-RACF A RCEF A PIR < PI-Request > ::= < Diameter Header: 315, REQ, PXY > < Session-Id = "aracf-a.example.com;32475;112" > { Auth-Application-Id = 16777253 (Re) } { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Destination-Host = "rcef-a.example.com" } { PI-Request-Type = INITIAL_REQUEST } { PI-Request-Number = 0 } [ Auth-Session-State = NO_STATE_MAINTAINED (1) ] [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-A-UL" } [ Service-Identifier = 1 ] [ Rating-Group = 1 ] [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] [ Flow-Description = "permit in 17 from 192.168.0.2 23942 to 192.168.0.1 4444" ] [ Flow-Description = "permit in 17 from 192.168.0.2 23943 to 192.168.0.1 4445" ] [ Flow-Status = ENABLED-UPLINK (0) ] [ QoS-Information = [ Max-Requested-Bandwidth-UL = 104000 ] [ ToS-Traffic-Class = 101110 ] ] [ Precedence = 1] [ Flows = { Media-Component-Number = 1 } [ Flow-Number = 1 ] [ Flow-Number = 2 ] ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 43 Step Protocol Interface From To Message ] ] [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-A-DL" } [ Service-Identifier = 1 ] [ Rating-Group = 1 ] [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] [ Flow-Description = "permit out 17 from 192.168.0.1 4444 to 192.168.0.2 23942" ] [ Flow-Description = "permit out 17 from 192.168.0.1 4445 to 192.168.0.2 23943" ] [ Flow-Status = ENABLED-DOWNLINK (1) ] [ QoS-Information = [ Max-Requested-Bandwidth-DL = 104000 ] [ ToS-Traffic-Class = 101110 ] ] [ Precedence = 1] [ Flows = { Media-Component-Number = 1 } [ Flow-Number = 1 ] [ Flow-Number = 2 ] ] ] ] 40 DIAMETER Re RCEF A A-RACF A PIA <PI-Answer> ::= < Diameter Header: 315, PXY > < Session-Id = "aracf-a.example.com;32475;112" > { Origin-Host = "rcef-a.example.com" } { Origin-Realm = "example.com" } { PI-Request-Type = INITIAL_REQUEST } { PI-Request-Number = 0 } [ Result-Code DIAMETER_SUCCESS (2001) ] 41 DIAMETER Rq A-RACF A SPDF A AAA (Modify) <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 42 DIAMETER Gq' SPDF A P-CSCF A AAA (Modify) <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 23942 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1110 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 23943 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1111 } ] } [ Binding-Output-List = ETSI ETSI TS 183 048 V2.2.1 (2009-08) 44 Step Protocol Interface From To Message [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2222 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.1 } { Port-Number = 4444 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2223 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.1 } { Port-Number = 4445 } ] ] ] [ Authorization-Lifetime = 450 ] { Auth-Grace-Period = 10 } 43 SIP P-CSCF A Phone A 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 67 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_b@phone-b.example.com> Content-Type: application/sdp Content-Length: 129 v=0 o=user_b 29381748101 2948193018 IN IP4 phone-b.example.com s=- c=IN IP4 192.168.0.1 t=0 0 m=audio 4444 RTP/AVP 0 a=sendrecv 44 SIP Phone A P-CSCF A ACK ACK sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 70 Route: <sip:p-cscf-a.example.com;lr>,<sip:s-cscf.example.com;lr>,<sip:p-cscf-b.example.com;lr> From: User A <sip:user_a@example.com>;tag=348123 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 ACK Content-Length: 0 45 SIP P-CSCF A S-CSCF ACK ACK sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 69 Route: <sip:s-cscf.example.com;lr>,<sip:p-cscf-b.example.com;lr> From: User A <sip:user_a@example.com>;tag=348123 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 ACK Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 45 Step Protocol Interface From To Message 46 SIP S-CSCF P-CSCF B ACK ACK sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 68 Route: <sip:p-cscf-b.example.com;lr> From: User A <sip:user_a@example.com>;tag=348123 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 ACK Content-Length: 0 47 SIP P-CSCF B Phone B ACK ACK sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060; branch=z9hG4bK74b03 Max-Forwards: 67 From: User A <sip:user_a@example.com>;tag=348123 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 ACK Content-Length: 0
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
6.1.2 Session termination
|
Figure 6.1.2.1: MS end-to-end signalling chart between two SIP end-points - session teardown ETSI ETSI TS 183 048 V2.2.1 (2009-08) 46 Table 6.1.2.1: IMS end-to-end messages between two SIP end-points - session teardown Step Protocol Interface From To Message 48 SIP Phone B P-CSCF B BYE BYE sip:user_a@example.com SIP/2.0 Via: SIP/2.0/UDP phone-b.example.com:5060;branch=z9hG4bKjwafcb9 Max-Forwards: 70 Route: <sip:p-cscf-b.example.com;lr>,<sip:s-cscf.example.com;lr>,<sip:p-cscf-a.example.com;lr> From: User B <sip:user_b@example.com>;tag=4fxdce12ls To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 49 DIAMETER Gq' P-CSCF B SPDF B STR <ST-Request> ::= < Diameter Header: 275, REQ, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Origin-Host = "p-cscf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Termination-Cause = DIAMETER_LOGOUT } { Auth-Application-Id = 16777222 (Gq) } [ Destination-Host = " spdf-b.example.com" ] 50 H.248 Ia SPDF B C-BGF B Subtract termination B MEGACO/3 [spdf-b.example.com]:43924 Transaction = 3 { Context = 1 { Subtract = ip/1/if1/1 {Audit{Statistics}} Subtract = ip/1/if2/1 {Audit{Statistics}} } /* Context */ } /* Transaction */ 51 H.248 Ia C-BGF B SPDF B Reply MEGACO/3 [abgf-b.example.com]:43924 Reply = 3 { Context = 1 { Subtract = ip/1/if1/1 { Statistics { nt/dur=450000, ; in milliseconds nt/os=5400000, ; Octets Sent nt/or=5400000, ; Octets Received gm/dp=0 ; number of packets discarded } } Subtract = ip/1/if2/1 { Statistics { nt/dur=450000, ; in milliseconds nt/os=450000, ; Octets Sent nt/or=450000, ; Octets Received gm/dp=0 ; number of packets discarded } /* Statistics */ } /* Subtract */ } /* Context */ } /* Reply */ 52 DIAMETER Rq SPDF B A-RACF B STR <ST-Request> ::= < Diameter Header: 275, REQ, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Auth-Application-Id = 16777222 (Gq) } { Termination-Cause = DIAMETER_LOGOUT } [ Destination-Host = " aracf-b.example.com" ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 47 Step Protocol Interface From To Message 53 DIAMETER Re A-RACF B RCEF B PIR < PI-Request > ::= < Diameter Header: 315, REQ, PXY > < Session-Id = "aracf-b.example.com;66389;469" > { Auth-Application-Id = 16777253 (Re) } { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Destination-Host = "rcef-b.example.com" } { PI-Request-Type = TERMINATION_REQUEST } { PI-Request-Number = 1 } [ Policy-Rule-Remove = [ Policy-Rule-Definition = [ Policy-Rule-Name = "policy-rule-example-B-UL" ] ] ] [ Policy-Rule-Remove = [ Policy-Rule-Definition = [ Policy-Rule-Name = "policy-rule-example-B-DL" ] ] ] 54 DIAMETER Re RCEF B A-RACF B PIA <PI-Answer> ::= < Diameter Header: 315, PXY > < Session-Id = "aracf-b.example.com;66389;469" > { Origin-Host = "rcef-b.example.com" } { Origin-Realm = "example.com" } { PI-Request-Type = TERMINATION_REQUEST } { PI-Request-Number = 1 } [ Result-Code DIAMETER_SUCCESS (2001) ] 55 DIAMETER Rq A-RACF B SPDF B STA <ST-Answer> ::= < Diameter Header: 275, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] 56 DIAMETER Gq' SPDF B P-CSCF B STA <ST-Answer> ::= < Diameter Header: 275, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] 57 SIP P-CSCF B S-CSCF BYE BYE sip:user_a@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP phone-b.example.com:5060;branch=z9hG4bKjwafcb9 Max-Forwards: 69 Route: <sip:s-cscf.example.com;lr>,<sip:p-cscf-a.example.com;lr> From: User B <sip:user_b@example.com>;tag=4fxdce12ls To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 48 Step Protocol Interface From To Message 58 SIP S-CSCF P-CSCF A BYE BYE sip:user_a@example.com SIP/2.0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP phone-b.example.com:5060;branch=z9hG4bKjwafcb9 Max-Forwards: 68 Route: <sip:p-cscf-a.example.com;lr> From: User B <sip:user_b@example.com>;tag=4fxdce12ls To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 59 DIAMETER Gq' P-CSCF A SPDF A STR <ST-Request> ::= < Diameter Header: 275, REQ, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Origin-Host = "p-cscf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Termination-Cause = DIAMETER_LOGOUT } { Auth-Application-Id = 16777222 (Gq) } [ Destination-Host = " spdf-a.example.com" ] 60 H.248 Ia SPDF A C-BGF A Subtract Termination A MEGACO/3 [spdf-a.example.com]:5555 Transaction = 3 { Context = 1 { Subtract = ip/1/if1/1 {Audit{Statistics}} Subtract = ip/1/if2/1 {Audit{Statistics}} } /* Context */ } /* Transaction */ 61 H.248 Ia C-BGF A SPDF A Reply MEGACO/3 [abgf-a.example.com]:21398 Reply = 3 { Context = 1 { Subtract = ip/1/if1/1 { Statistics { nt/dur=450000, ; in milliseconds nt/os=5400000, ; Octets Sent nt/or=5400000, ; Octets Received gm/dp=0 ; number of packets discarded } } Subtract = ip/1/if1/2 { Statistics { nt/dur=450000, ; in milliseconds nt/os=450000, ; Octets Sent nt/or=450000, ; Octets Received gm/dp=0 ; number of packets discarded } /* Statistics */ } /* Subtract */ } /* Context */ } /* Reply */ 62 DIAMETER Rq SPDF A A-RACF A STR <ST-Request> ::= < Diameter Header: 275, REQ, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Auth-Application-Id = 16777222 (Gq) } { Termination-Cause = DIAMETER_LOGOUT } [ Destination-Host = " aracf-a.example.com" ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 49 Step Protocol Interface From To Message 63 DIAMETER Re A-RACF A RCEF A PIR < PI-Request > ::= < Diameter Header: 315, REQ, PXY > < Session-Id = "aracf-a.example.com;32475;112" > { Auth-Application-Id = 16777253 (Re) } { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Destination-Host = "rcef-a.example.com" } { PI-Request-Type = TERMINATION_REQUEST } { PI-Request-Number = 1 } [ Policy-Rule-Remove = [ Policy-Rule-Definition = [ Policy-Rule-Name = "policy-rule-example-A-UL" ] ] ] [ Policy-Rule-Remove = [ Policy-Rule-Definition = [ Policy-Rule-Name = "policy-rule-example-A-DL" ] ] ] 64 DIAMETER Re RCEF A A-RACF A PIA <PI-Answer> ::= < Diameter Header: 315, PXY > < Session-Id = "aracf-a.example.com;32475;112" > { Origin-Host = "rcef-a.example.com" } { Origin-Realm = "example.com" } { PI-Request-Type = TERMINATION_REQUEST } { PI-Request-Number = 1 } [ Result-Code DIAMETER_SUCCESS (2001) ] 65 DIAMETER Rq A-RACF A SPDF A STA <ST-Answer> ::= < Diameter Header: 275, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] 66 DIAMETER Gq' SPDF A P-CSCF A STA <ST-Answer> ::= < Diameter Header: 275, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] 67 SIP P-CSCF B Phone A BYE BYE sip:user_a@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP phone-b.example.com:5060;branch=z9hG4bKjwafcb9 Max-Forwards: 67 From: User B <sip:user_b@example.com>;tag=4fxdce12ls To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 50 Step Protocol Interface From To Message 68 SIP Phone A P-CSCF A 200 OK (BYE) SIP/2.0 200 OK Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP phone-b.example.com:5060;branch=z9hG4bKjwafcb9 Max-Forwards: 70 From: User B <sip:user_b@example.com>;tag=4fxdce12ls To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 69 SIP P-CSCF A S-CSCF 200 OK (BYE) SIP/2.0 200 OK Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP phone-b.example.com:5060;branch=z9hG4bKjwafcb9 Max-Forwards: 69 From: User B <sip:user_b@example.com>;tag=4fxdce12ls To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 70 SIP S-CSCF P-CSCF B 200 OK (BYE) SIP/2.0 200 OK Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP phone-b.example.com:5060;branch=z9hG4bKjwafcb9 Max-Forwards: 68 From: User B <sip:user_b@example.com>;tag=4fxdce12ls To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 71 SIP P-CSCF B Phone B 200 OK (BYE) SIP/2.0 200 OK Via: SIP/2.0/UDP phone-b.example.com:5060;branch=z9hG4bKjwafcb9 Max-Forwards: 67 From: User B <sip:user_b@example.com>;tag=4fxdce12ls To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 51
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
6.1.3 Session failures
| |
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
6.1.3.1 RCEF failure at session setup
|
Figure 6.1.3.1.1: Failure in RCEF B at session setup Table 6.1.3.1.1: Messages to handle failure in RCEF B at session setup Step Protocol Interface From To Message 30a DIAMETER Re RCEF B A-RACF B PIA <PI-Answer> ::= < Diameter Header: 315, PXY > < Session-Id = "aracf-b.example.com;66389;469" > { Origin-Host = "rcef-b.example.com" } { Origin-Realm = "example.com" } { PI-Request-Type = INITIAL_REQUEST } { PI-Request-Number = 0 } [ Result-Code DIAMETER_UNABLE_TO_COMPLY (5012) ] [ Policy-Rule-Report = [ Policy-Rule-Name = "policy-rule-example-B-UL" ] [ Policy-Rule-Name = "policy-rule-example-B-DL" ] [ Policy-Rule-Status = INACTIVE (1) ] [ Rule-Failure-Code = RESOURCES_LIMITATION (5) ] ] [ Failed-AVP = [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-B-UL" } [ Service-Identifier = 1 ] [ Rating-Group = 1 ] [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] [ Flow-Description = "permit in 17 from 192.168.1.2 29792 to 192.168.1.1 3332" ] [ Flow-Description = "permit in 17 from 192.168.1.2 29793 to 192.168.1.1 3333" ] [ Flow-Status = ENABLED-UPLINK (0) ] [ QoS-Information = [ Max-Requested-Bandwidth-UL = 104000 ] [ ToS-Traffic-Class = 101110 ] ] [ Precedence = 1] [ Flows = { Media-Component-Number = 1 } [ Flow-Number = 1 ] [ Flow-Number = 2 ] ] ] ] [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-B-DL" } [ Service-Identifier = 1 ] [ Rating-Group = 1 ] [ Framed-IP-Address = 192.168.1.2 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 52 Step Protocol Interface From To Message [ Address-Realm = "example.com" ] [ Flow-Description = "permit out 17 from 192.168.1.1 3332 to 192.168.1.2 29792" ] [ Flow-Description = "permit out 17 from 192.168.1.1 3333 to 192.168.1.2 29793" ] [ Flow-Status = ENABLED-DOWNLINK (1) ] [ QoS-Information = [ Max-Requested-Bandwidth-DL = 104000 ] [ ToS-Traffic-Class = 101110 ] ] [ Precedence = 1] [ Flows = { Media-Component-Number = 1 } [ Flow-Number = 1 ] [ Flow-Number = 2 ] ] ] ] ] 31a DIAMETER Rq A-RACF B SPDF B AAA (Modify) <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_UNABLE_TO_COMPLY (5012) ] [ Error-Message = "RCEF: Rule-Failure-Code = RESOURCES_LIMITATION (5)" ] [ Error-Reporting-Host = "rcef-b.example.com" ] 32a H.248 Ia SPDF B C-BGF B Subtract termination B MEGACO/3 [spdf-b.example.com]:43924 Transaction = 2 { Context = 1 { Subtract = ip/1/if1/1 {Audit{Statistics}} Subtract = ip/1/if2/1 {Audit{Statistics}} } /* Context */ } /* Transaction */ 33a H.248 Ia C-BGF B SPDF B Reply MEGACO/3 [abgf-b.example.com]:43924 Reply = 2 { Context = 1 { Subtract = ip/1/if1/1 { Statistics { nt/dur=450, ; in milliseconds nt/os=0, ; Octets Sent nt/or=0, ; Octets Received gm/dp=0 ; number of packets discarded } } Subtract = ip/1/if2/1 { Statistics { nt/dur=450, ; in milliseconds nt/os=0, ; Octets Sent nt/or=0, ; Octets Received gm/dp=0 ; number of packets discarded } /* Statistics */ } /* Subtract */ } /* Context */ } /* Reply */ 34a DIAMETER Gq' SPDF B P-CSCF B AAA (Modify) <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_UNABLE_TO_COMPLY (5012) ] [ Error-Message = "RCEF: Rule-Failure-Code = RESOURCES_LIMITATION (5)" ] [ Error-Reporting-Host = "rcef-b.example.com" ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 53 Step Protocol Interface From To Message 35a SIP P-CSCF B S-CSCF 480 Temporarily Unavailable SIP/2.0 480 Temporarily Unavailable Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 69 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_b@phone-b.example.com> Content-Length: 0 36a SIP S-CSCF P-CSCF A 480 Temporarily Unavailable SIP/2.0 480 Temporarily Unavailable Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 68 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_b@phone-b.example.com> Content-Length: 0 37a DIAMETER Gq' P-CSCF A SPDF A STR <ST-Request> ::= < Diameter Header: 275, REQ, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Origin-Host = "p-cscf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Auth-Application-Id = 16777222 (Gq) } { Termination-Cause = DIAMETER_LOGOUT (1) } [ Destination-Host = "spdf-a@example.com" ] 38a H.248 Ia SPDF A C-BGF A Subtract Termination A MEGACO/3 [spdf-a.example.com]:5555 Transaction = 2 { Context = 1 { Subtract = ip/1/if1/1 {Audit{Statistics}} Subtract = ip/1/if2/1 {Audit{Statistics}} } /* Context */ } /* Transaction */ 39a H.248 Ia C-BGF A SPDF A Reply MEGACO/3 [abgf-a.example.com]:21398 Reply = 2 { Context = 1 { Subtract = ip/1/if1/1 { Statistics { nt/dur=450, ; in milliseconds nt/os=0, ; Octets Sent nt/or=0, ; Octets Received gm/dp=0 ; number of packets discarded } } Subtract = ip/1/if1/2 { Statistics { nt/dur=450, ; in milliseconds nt/os=0, ; Octets Sent nt/or=0, ; Octets Received gm/dp=0 ; number of packets discarded } /* Statistics */ } /* Subtract */ } /* Context */ } /* Reply */ ETSI ETSI TS 183 048 V2.2.1 (2009-08) 54 Step Protocol Interface From To Message 40a DIAMETER Rq SPDF A A-RACF A STR <ST-Request> ::= < Diameter Header: 275, REQ, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Auth-Application-Id = 16777222 (Gq) } { Termination-Cause = DIAMETER_LOGOUT (1) } [ Destination-Host = "aracf-a@example.com" ] 41a DIAMETER Rq A-RACF A SPDF A STA <ST-Answer> ::= < Diameter Header: 275, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] 42a DIAMETER Gq' SPDF A P-CSCF A STA <ST-Answer> ::= < Diameter Header: 275, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] 43a SIP P-CSCF A Phone A 480 Temporarily Unavailable SIP/2.0 480 Temporarily Unavailable Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 67 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_b@phone-b.example.com> Content-Length: 0
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
6.1.3.2 RCEF failure after session setup
|
Figure 6.1.3.2.1: Failure in RCEF B after session setup ETSI ETSI TS 183 048 V2.2.1 (2009-08) 55 Table 6.1.3.2.1: Messages to handle failure in RCEF B after session setup Step Protocol Interface From To Message 48a DIAMETER Re RCEF B A-RACF B CCR In case the policy was established with a pull request from the RCEF to the A-RACF as illustrated in clause 6.4, the Logical-Access-Id AVP would be used as Transport Resource Classifier instead of the Framed-IP-Address AVP and the Address-Realm AVP, which are used in this example to match the policy established with a push request as illustrated in clause 6.1. That is, the same Transport Resource Classifier(s) as used when the policy was established shall be used by the RCEF when issuing a CCR to deactivate the policy. <CC-Request> ::= < Diameter Header: 272, REQ, PXY > < Session-Id = "rcef-b.example.com;66389;469" > { Origin-Host = "rcef-b.example.com" } { Origin-Realm = "example.com " } { Destination-Realm = "example.com " } { Auth-Application-Id = 16777253 (Re) } { Service-Context-Id = "service_1@rcef-a.example.com" } { CC-Request-Type = "TERMINATION_REQUEST" } { CC-Request-Number = 0 } [ Termination-Cause "DIAMETER_LINK_BROKEN" ] [ Flow-Description = "permit in 17 from 192.168.1.2 29792 to 192.168.1.1 3332" ] [ Flow-Description = "permit in 17 from 192.168.1.2 29793 to 192.168.1.1 3333" ] [ Flow-Description = "permit out 17 from 192.168.1.1 3332 to 192.168.1.2 29792" ] [ Flow-Description = "permit out 17 from 192.168.1.1 3333 to 192.168.1.2 29793" ] [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com"] 49a DIAMETER Re A-RACF B RCEF B CCA <CC-Answer> ::= < Diameter Header: 272, PXY > < Session-Id = "rcef-b.example.com; 66389;469" > { Origin-Host = "a-racf-b.example.com" } { Origin-Realm = "example.com " } { Auth-Application-Id = 16777253 (Re) } { Result-Code = DIAMETER_SUCCESS (2001) } { CC-Request-Type = "TERMINATION_REQUEST" } { CC-Request-Number = 0 } [ Policy-Rule-Remove = [ Policy-Rule-Definition = [ Policy-Rule-Name = "policy-rule-example-B-UL" ] [ Policy-Rule-Name = "policy-rule-example-B-DL" ] ] ] 50a DIAMETER Rq A-RACF B SPDF B ASR <AS-Request> ::= < Diameter Header: 274, REQ, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Destination-Host = "spdf-b.example.com" } { Auth-Application-ID = 16777222 (Gq) } { Abort-Cause = "BEARER_RELEASED" } 51a DIAMETER Rq SPDF B A-RACF B ASA <AS-Answer> ::= < Diameter Header: 274, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 56 Step Protocol Interface From To Message 52a H.248 Ia SPDF B C-BGF B Subtract termination B MEGACO/3 [spdf-b.example.com]:43924 Transaction = 3 { Context = 1 { Subtract = ip/1/if1/1 {Audit{Statistics}} Subtract = ip/1/if2/1 {Audit{Statistics}} } /* Context */ } /* Transaction */ 53a H.248 Ia C-BGF B SPDF B Reply MEGACO/3 [abgf-b.example.com]:43924 Reply = 3 { Context = 1 { Subtract = ip/1/if1/1 { Statistics { nt/dur=45000, ; in milliseconds nt/os=540000, ; Octets Sent nt/or=540000, ; Octets Received gm/dp=0 ; number of packets discarded } } Subtract = ip/1/if2/1 { Statistics { nt/dur=45000, ; in milliseconds nt/os=45000, ; Octets Sent nt/or=45000, ; Octets Received gm/dp=0 ; number of packets discarded } /* Statistics */ } /* Subtract */ } /* Context */ } /* Reply */ 54a DIAMETER Gq' SPDF B P-CSCF B ASR <AS Request> ::= < Diameter Header: 274, REQ, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Destination-Host = "p-cscf-b.example.com" } { Auth-Application-ID = 16777222 (Gq) } { Abort-Cause = "BEARER_RELEASED" } 55a DIAMETER Gq' P-CSCF B SPDF B ASA <AS-Answer> ::= < Diameter Header: 274, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Origin-Host = "p-cscf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] 56a SIP P-CSCF B Phone B BYE BYE sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Max-Forwards: 70 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 57 Step Protocol Interface From To Message 57a SIP Phone B P-CSCF B 200 OK (BYE) SIP/2.0 200 OK Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Max-Forwards: 70 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 58a SIP P-CSCF B S-CSCF BYE BYE sip:user_a@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Max-Forwards: 70 Route: <sip:s-cscf.example.com;lr>,<sip:p-cscf-a.example.com;lr> From: User B <sip:user_b@example.com>;tag=4fxdce12ls To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 59a SIP S-CSCF P-CSCF A BYE BYE sip:user_a@example.com SIP/2.0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Max-Forwards: 69 Route: <sip:p-cscf-a.example.com;lr> From: User B <sip:user_b@example.com>;tag=372183 To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 60a DIAMETER Gq' P-CSCF A SPDF A STR <ST-Request> ::= < Diameter Header: 275, REQ, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Origin-Host = "p-cscf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Auth-Application-Id = 16777222 (Gq) } { Termination-Cause = DIAMETER_LOGOUT (1) } 61a H.248 Ia SPDF A C-BGF A Subtract Termination A MEGACO/3 [spdf-a.example.com]:5555 Transaction = 3 { Context = 1 { Subtract = ip/1/if1/1 {Audit{Statistics}} Subtract = ip/1/if2/1 {Audit{Statistics}} } /* Context */ } /* Transaction */ 62a H.248 Ia C-BGF A SPDF A Reply MEGACO/3 [abgf-a.example.com]:21398 Reply = 3 { Context = 1 { Subtract = ip/1/if1/1 { Statistics { nt/dur=45000, ; in milliseconds nt/os=540000, ; Octets Sent nt/or=540000, ; Octets Received gm/dp=0 ; number of packets discarded } } Subtract = ip/1/if1/2 { Statistics { nt/dur=45000, ; in milliseconds nt/os=45000, ; Octets Sent nt/or=45000, ; Octets Received gm/dp=0 ; number of packets discarded ETSI ETSI TS 183 048 V2.2.1 (2009-08) 58 Step Protocol Interface From To Message } /* Statistics */ } /* Subtract */ } /* Context */ } /* Reply */ 63a DIAMETER Rq SPDF A A-RACF A STR <ST-Request> ::= < Diameter Header: 275, REQ, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Auth-Application-Id = 16777222 (Gq) } { Termination-Cause = DIAMETER_LOGOUT (1) } 64a DIAMETER Rq A-RACF A SPDF A STA <ST-Answer> ::= < Diameter Header: 275, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] 65a DIAMETER Gq' SPDF A P-CSCF A STA <ST-Answer> ::= < Diameter Header: 275, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] 66a SIP P-CSCF A Phone A BYE BYE sip:user_a@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Max-Forwards: 66 From: User B <sip:user_b@example.com>;tag=372183 To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 67a SIP Phone A P-CSCF A 200 OK (BYE) SIP/2.0 200 OK Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Max-Forwards: 70 From: User B <sip:user_b@example.com>;tag=372183 To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 68a SIP P-CSCF A S-CSCF 200 OK (BYE) SIP/2.0 200 OK Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Max-Forwards: 69 From: User B <sip:user_b@example.com>;tag=372183 To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 59 Step Protocol Interface From To Message 69a SIP S-CSCF P-CSCF B 200 OK (BYE) SIP/2.0 200 OK Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Max-Forwards: 68 From: User B <sip:user_b@example.com>;tag=372183 To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
6.1.3.3 C-BGF A transport plane failure
|
NOTE: In this scenario, session signalling according to clause 6.1.1 (with the exception of steps 3a, 4a and 35a shown in table 6.1.3.2.1) has been completed and the session is successfully established when C-BGF A detects a transport plane failure and sends a Notify command to SPDF A in step 48a. Figure 6.1.3.3.1: C-BGF A transport plane failure after successful session establishment Table 6.1.3.3.1: BGF transport plane failure Step Protocol Interface From To Message 3a DIAMETER Gq' P-CSCF A SPDF A AAR <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-a.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from any to 192.168.0.2 23942" ] [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 96000 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 60 Step Protocol Interface From To Message [ Max-Requested-Bandwidth-UL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from any to 192.168.0.2 23943" ] [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-DL = 8000 ] [ Max-Requested-Bandwidth-UL = 8000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "uplink offer m=audio 23942 RTP/AVP 0" ]] [ Specific-Action = INDICATION_OF_LOSS_OF_BEARER (2) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 23942 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 23943 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] } ] [ Reservation-Priority = DEFAULT (0) ][ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] NOTE 1: By including the Specific-Action AVP, P-CSCF A requests the SPDF to provide a notification at the loss of a bearer. 4a H.248 Ia SPDF A C-BGF A Add terminations MEGACO/3 [spdf-a.example.com]:55555 Transaction = 1 { Context = ${ Add = ip/1/$/$ { /* NOTE 1 */ Media { Stream = 1 { LocalControl { ipdc/realm = "A", gm/rsb = ON } Local { v=0 m=- $ RTP/AVP 0 c=IN IP4 $ b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 192.168.0.2 s=- t=0 0 m=- 23942 RTP/AVP 0 c=IN IP4 192.168.0.2 b=AS:104 } } /* Stream */ }, /* Media */ ETSI ETSI TS 183 048 V2.2.1 (2009-08) 61 Step Protocol Interface From To Message Events = 1234 { g/cause } /* Events */ } /* Add */ Add = ip/1/$/$ { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 m=- $ RTP/AVP 97 a=rtpmap:97 AMR/8000/1 c=IN IP4 $ b=AS:104 } } /* Stream */ }, /* Media */ Events = 1235 { g/cause } /* Events */ } /* Add */ } /* Context */ } /* Transaction */ 35a DIAMETER Gq' P-CSCF A SPDF A AAR (Modify) <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-a.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Description = "permit out 17 from any to 192.168.0.2 23942" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 96000 ] [ Max-Requested-Bandwidth-DL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Description = "permit out 17 from any to 192.168.0.2 23943" ] [ Flow-Usage = RTCP(1) ] [ Max-Requested-Bandwidth-UL = 8000 ] [ Max-Requested-Bandwidth-DL = 8000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = ENABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "uplink offer m=audio 23942 RTP/AVP 0" ] ] [ Specific-Action = INDICATION_OF_LOSS_OF_BEARER (2) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 23942 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1110 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 23943 } ETSI ETSI TS 183 048 V2.2.1 (2009-08) 62 Step Protocol Interface From To Message ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1111 } ] } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] NOTE 2: If the Specific-Action AVP is provided in an initial AA-Request, it shall have the same value if provided also in a modifying AA-Request. 48a H.248 Ia C-BGF A SPDF A Notify The session was successfully established as in 6.1.1.1 with modifications according to the steps above. Mid-session, C-BGF A detects loss of RTP on the ephemeral termination ip/1/if1/1 and sends a Notify command containing the g/cause event in the ObservedEvents descriptor to SPDF A. MEGACO/3 [abgf-a.example.com]:55555 Transaction = 3 { Context = 1 { Notify = ip/1/if1/1 { ObservedEvents { g/cause } } /* Notify */ } /* Context */ } /* Transaction */ 49a H.248 Ia SPDF A C-BGF A Reply (Notify) MEGACO/3 [abgf-a.example.com]:55555 Reply = 3 { Context = 1 { Notify = ip/1/if1/1 } /* Context */ } /* Transaction */ 50a DIAMETER Gq' SPDF A P-CSCF A RAR SPDF A correlates the termination id in the Notify command sent in step 48a with the corresponding Session-Id and sends a Re-Authorization Request containing the session id affected by the occurred event to P-CSCF A. <RA-Request> ::= < Diameter Header: 258, REQ, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Destination-Host = "p-cscf-a.example.com" } { Auth-Application-Id = 16777222 (Gq) } { Specific-Action = INDICATION_OF_LOSS_OF_BEARER (2) } 51a SIP Mw P-CSCF A S-CSCF BYE BYE sip:user_a@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKjwafcb9 Max-Forwards: 69 From: User B <sip:user_b@example.com>;tag=4fxdce12ls To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 63 Step Protocol Interface From To Message 52a SIP Mw S-CSCF P-CSCF B BYE BYE sip:user_a@example.com SIP/2.0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKjwafcb9 Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKjwafcb9 Max-Forwards: 68 From: User B <sip:user_b@example.com>;tag=4fxdce12ls To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 53a DIAMETER Gq' P-CSCF B SPDF B STR <ST-Request> ::= < Diameter Header: 275, REQ, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Origin-Host = "p-cscf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Termination-Cause = DIAMETER_LOGOUT } { Auth-Application-Id = 16777222 (Gq) } [ Destination-Host = " spdf-b.example.com" ] 54a H.248 Ia SPDF B C-BGF B Subtract termination B MEGACO/3 [spdf-b.example.com]:43924 Transaction = 3 { Context = 1 { Subtract = ip/1/if1/1 {Audit{Statistics}} Subtract = ip/1/if2/1 {Audit{Statistics}} } /* Context */ } /* Transaction */ 55a H.248 Ia C-BGF B SPDF B Reply (Subtract) MEGACO/3 [abgf-b.example.com]:43924 Reply = 3 { Context = 1 { Subtract = ip/1/if1/1 { Statistics { nt/dur=450000, ; in milliseconds nt/os=5400000, ; Octets Sent nt/or=5400000, ; Octets Received gm/dp=0 ; number of packets discarded } } Subtract = ip/1/if2/1 { Statistics { nt/dur=450000, ; in milliseconds nt/os=450000, ; Octets Sent nt/or=450000, ; Octets Received gm/dp=0 ; number of packets discarded } /* Statistics */ } /* Subtract */ } /* Context */ } /* Reply */ 56a DIAMETER Rq SPDF B A-RACF B STR <ST-Request> ::= < Diameter Header: 275, REQ, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Auth-Application-Id = 16777222 (Gq) } { Termination-Cause = DIAMETER_LOGOUT } [ Destination-Host = " aracf-b.example.com" ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 64 Step Protocol Interface From To Message 57a DIAMETER Re A-RACF B RCEF B PIR < PI-Request > ::= < Diameter Header: 315, REQ, PXY > < Session-Id = "aracf-b.example.com;66389;469" > { Auth-Application-Id = 16777253 (Re) } { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Destination-Host = "rcef-b.example.com" } { PI-Request-Type = TERMINATION_REQUEST } { PI-Request-Number = 1 } [ Policy-Rule-Remove = [ Policy-Rule-Definition = [ Policy-Rule-Name = "policy-rule-example-B-UL" ] ] ] [ Policy-Rule-Remove = [ Policy-Rule-Definition = [ Policy-Rule-Name = "policy-rule-example-B-DL" ] ] ] 58a DIAMETER Re RCEF B A-RACF PIA <PI-Answer> ::= < Diameter Header: 315, PXY > < Session-Id = "aracf-b.example.com;66389;469" > { Origin-Host = "rcef-b.example.com" } { Origin-Realm = "example.com" } { PI-Request-Type = TERMINATION_REQUEST } { PI-Request-Number = 1 } [ Result-Code DIAMETER_SUCCESS (2001) ] 59a DIAMETER Rq A-RACF B SPDF B STA <ST-Answer> ::= < Diameter Header: 275, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] 60a DIAMETER Gq' SPDF B P-CSCF B STA <ST-Answer> ::= < Diameter Header: 275, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) 61a SIP Gm P-CSCF B Phone B BYE BYE sip:user_a@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKjwafcb9 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKjwafcb9 Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKjwafcb9 Max-Forwards: 67 From: User B <sip:user_b@example.com>;tag=372183 To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 62a SIP Gm Phone B P-CSCF B 200 OK (BYE) SIP/2.0 200 OK Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKs1pp0 Max-Forwards: 70 From: User B <sip:user_b@example.com>;tag=372183 To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 65 Step Protocol Interface From To Message 63a SIP Mw P-CSCF B S-CSCF 200 OK (BYE) SIP/2.0 200 OK Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKs1pp0 Max-Forwards: 69 From: User B <sip:user_b@example.com>;tag=372183 To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 64a SIP Mw S-CSCF P-CSCF A 200 OK (BYE) SIP/2.0 200 OK Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKs1pp0 Max-Forwards: 68 From: User B <sip:user_b@example.com>;tag=372183 To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 65a DIAMETER Gq' P-CSCF A SPDF A RAA <RA-Answer > ::= < Diameter Header: 258, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Origin-Host = "p-cscf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] 66a DIAMETER Gq' P-CSCF A SPDF A STR <ST-Request> ::= < Diameter Header: 275, REQ, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Origin-Host = "p-cscf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Termination-Cause = DIAMETER_LOGOUT } { Auth-Application-Id = 16777222 (Gq) } [ Destination-Host = " spdf-a.example.com" ] 67a H.248 Ia SPDF A C-BGF A Subtract MEGACO/3 [spdf-a.example.com]:5555 Transaction = 3 { Context = 1 { Subtract = ip/1/if1/1 {Audit{Statistics}} Subtract = ip/1/if2/1 {Audit{Statistics}} } /* Context */ } /* Transaction */ ETSI ETSI TS 183 048 V2.2.1 (2009-08) 66 Step Protocol Interface From To Message 68a H.248 Ia C-BGF A SPDF A Reply (Subtract) MEGACO/3 [abgf-a.example.com]:21398 Reply = 3 { Context = 1 { Subtract = ip/1/if1/1 { Statistics { nt/dur=450000, ; in milliseconds nt/os=5400000, ; Octets Sent nt/or=5400000, ; Octets Received gm/dp=0 ; number of packets discarded } } Subtract = ip/1/if1/2 { Statistics { nt/dur=450000, ; in milliseconds nt/os=450000, ; Octets Sent nt/or=450000, ; Octets Received gm/dp=0 ; number of packets discarded } /* Statistics */ } /* Subtract */ } /* Context */ } /* Reply */ 69a DIAMETER Rq SPDF A A-RACF A STR <ST-Request> ::= < Diameter Header: 275, REQ, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Auth-Application-Id = 16777222 (Gq) } { Termination-Cause = DIAMETER_LOGOUT } [ Destination-Host = " aracf-a.example.com" ] 70a DIAMETER Re A-RACF A RCEF A PIR < PI-Request > ::= < Diameter Header: 315, REQ, PXY > < Session-Id = "aracf-a.example.com;32475;112" > { Auth-Application-Id = 16777253 (Re) } { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Destination-Host = "rcef-a.example.com" } { PI-Request-Type = TERMINATION_REQUEST } { PI-Request-Number = 1 } [ Policy-Rule-Remove = [ Policy-Rule-Definition = [ Policy-Rule-Name = "policy-rule-example-A-UL" ] ] ] [ Policy-Rule-Remove = [ Policy-Rule-Definition = [ Policy-Rule-Name = "policy-rule-example-A-DL" ] ] ] 71a DIAMETER Re RCEF A A-RACF A PIA <PI-Answer> ::= < Diameter Header: 315, PXY > < Session-Id = "aracf-a.example.com;32475;112" > { Origin-Host = "rcef-a.example.com" } { Origin-Realm = "example.com" } { PI-Request-Type = TERMINATION_REQUEST } { PI-Request-Number = 1 } [ Result-Code DIAMETER_SUCCESS (2001) ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 67 Step Protocol Interface From To Message 72a DIAMETER Rq A-RACF A SPDF A STA <ST-Answer> ::= < Diameter Header: 275, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] 73a DIAMETER Gq' SPDF A P-CSCF A STA <ST-Answer> ::= < Diameter Header: 275, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] 74a SIP Gm P-CSCF A Phone A BYE BYE sip:user_a@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKs1pp0 Max-Forwards: 69 From: User B <sip:user_b@example.com>;tag=372183 To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 75a SIP Gm Phone A P-CSCF A 200 OK (BYE) SIP/2.0 200 OK Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKs1pp0 Max-Forwards: 69 From: User B <sip:user_b@example.com>;tag=372183 To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
6.1.3.4 Admission denial
|
Figure 6.1.3.4.1: Signalling for admission denial in A-RACF A at session setup ETSI ETSI TS 183 048 V2.2.1 (2009-08) 68 Table 6.1.3.4.1: Messages for admission denial in A-RACF A at session setup Step Protocol Interface From To Message 7d DIAMETER Rq A-RACF A SPDF A AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } [ Experimental-Result = { Vendor-Id = ETSI (13019) } { Experimental-Result-Code = INSUFFICIENT_RESOURCES (4041) } ] 8d H.248 Ia SPDF A C-BGF A Subtract termination A MEGACO/3 [spdf-a.example.com]:5555 Transaction = 2 { Context = 1 { Subtract = ip/1/if1/1 {Audit{Statistics}} Subtract = ip/1/if2/1 {Audit{Statistics}} } /* Context */ } /* Transaction */ 9d H.248 Ia C-BGF A SPDF A Reply MEGACO/3 [abgf-a.example.com]:21398 Reply = 2 { Context = 1 { Subtract = ip/1/if1/1 { Statistics { nt/dur=450, ; in milliseconds nt/os=0, ; Octets Sent nt/or=0, ; Octets Received gm/dp=0 ; number of packets discarded } } Subtract = ip/1/if1/2 { Statistics { nt/dur=450, ; in milliseconds nt/os=0, ; Octets Sent nt/or=0, ; Octets Received gm/dp=0 ; number of packets discarded } /* Statistics */ } /* Subtract */ } /* Context */ } /* Reply */ 10d DIAMETER Gq' SPDF A P-CSCF A AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } [ Experimental-Result = { Vendor-Id = ETSI (13019) } { Experimental-Result-Code = INSUFFICIENT_RESOURCES (4041) } ] 11d SIP P-CSCF A Phone A 488 Not Acceptable Here SIP/2.0 488 Not Acceptable Here Warning: 370 example.com "RACS: INSUFFICIENT_RESOURCES (4041)" Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 70 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 MESSAGE Contact: <sip:user_b@phone-b.example.com> Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 69
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
6.1.4 Session Update
|
Phone A P-CSCF A S-CSCF SPDF A A-RACF A C-BGF A Phone B P-CSCF B SPDF B A-RACF B C-BGF B INVITE B AAR Modify Termination Reply AAR AAA AAA INVITE B INVITE B AAR Modify Termination Reply AAR AAA AAA INVITE B AAR Modify Termination Reply AAR AAA AAA 200 OK 200 OK AAR Modify Termination Reply AAR AAA AAA 200 OK ACK ACK ACK ACK BIDIRECTIONAL VOICE/VIDEO RTP DATA RCEF A RCEF B PIR PIA PIR PIA 200 OK 100 Trying 100 Trying 100 Trying 48a 49a 50a 51a 52a 53a 54a 55a 56a 57a 58a 59a 60a 61a 62a 63a 64a 65a 66a 67a 68a 69a 70a 71a 72a 73a 74a 75a 76a 77a 78a 79a 80a 81a 82a 83a 84a 85a 86a 87a 88a 89a 90a 48a 49a 50a 51a 52a 53a 54a 55a 56a 57a 58a 59a 60a 61a 62a 63a 64a 65a 66a 67a 68a 69a 70a 71a 72a 73a 74a 75a 76a 77a 78a 79a 80a 81a 82a 83a 84a 85a 86a 87a 88a 89a 90a Figure 6.1.4.1: IMS end-to-end signalling chart between two SIP end-points - session update ETSI ETSI TS 183 048 V2.2.1 (2009-08) 70 Table 6.1.4.1: IMS end-to-end messages between two SIP end-points - session update Step Protocol Interface From To Message 48a SIP Phone A P-CSCF A INVITE B Phone A updates the session to include video by sending a mid-session re-invite to Phone B indicating the desired video codec to use in the call, in this case H.261. The b= SDP header element is used to advertise the maximum bandwidth the UE can receive for the advertised codec as described in annex B of [5]. INVITE sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 70 Route: <sip:p-cscf-a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 2 INVITE Contact: <sip:user_a@phone-a.example.com> Content-Type: application/sdp Content-Length: 204 v=0 o=user_a 2890844526 2890842807 IN IP4 phone-a.example.com s=- c=IN IP4 192.168.0.2 t=0 0 m=audio 23942 RTP/AVP 0 a=sendrecv m=video 51372 RTP/AVP 31 a=rtpmap:31 H261/90000 a=sendrecv b=AS:640 49a SIP P-CSCF A Phone A 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 2 INVITE Content-Length: 0 50a DIAMETER Gq' P-CSCF A SPDF A AAR Given the reception of a=sendrecv in the SDP the P-CSCF issues a bi-directional reservation modification request to the SPDF in order to reserve bandwidth for the added video media flow. A second media component is added to the Diameter session. The SPDF already contain the state for the first media component of this session. Therefore, only the new media component describing the video media flow need be present in the AA-Request. Following the rules given in clause 5.2.1.3, the Binding-Information AVPs are set to 0.0.0.0 and 0 respectively since no addresses or ports at the core side are allocated yet for the video flow. RTCP bandwidth is set to 5 % of the media stream bit rate in accordance with RFC 3556. <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-a@example.com" ] [ Media-Component-Description = { Media-Component-Number = 2 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from any to 192.168.0.2 51372" ] [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 640000 ] [ Max-Requested-Bandwidth-UL = 640000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from any to 192.168.0.2 51373" ] [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-DL = 32000 ] [ Max-Requested-Bandwidth-UL = 32000 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 71 Step Protocol Interface From To Message ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = VIDEO (1) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "uplink offer m=video 51372 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640" ] ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 51372 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 51373 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 51a H.248 Ia SPDF A C-BGF A Modify terminations A Modify is sent to C-BGF A to add a second stream to the termination for the video media flow. Since the SPDF already contains the state for the first media component of this session, the SPDF ignores the information for the voice media flow knowing that that terminations are already established in the C-BGF for the voice media flow. MEGACO/3 [spdf-a.example.com]:55555 Transaction = 3 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "A", gm/rsb = ON } Local { v=0 c=IN IP4 $ m=video $ RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 }, Remote { v=0 o=- 0 0 IN IP4 192.168.0.2 s=- t=0 0 c=IN IP4 192.168.0.2 m=video 51372 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { ETSI ETSI TS 183 048 V2.2.1 (2009-08) 72 Step Protocol Interface From To Message Media { Stream = 2 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 c=IN IP4 $ m=video $ RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Transaction */ 52a H.248 Ia C-BGF A SPDF A Reply (Modify) MEGACO/3 [abgf-a.example.com]:55555 Reply = 3 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "A", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 192.168.0.1 s=- t=0 0 c=IN IP4 192.168.0.1 m=video 31782 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 }, Remote { v=0 o=- 0 0 IN IP4 192.168.0.2 s=- t=0 0 c=IN IP4 192.168.0.2 m=video 51372 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 c=IN IP4 10.0.0.1 m=video 17462 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Reply */ ETSI ETSI TS 183 048 V2.2.1 (2009-08) 73 Step Protocol Interface From To Message 53a DIAMETER Rq SPDF A A-RACF A AAR Since the SPDF already contains the state for the first media component of this session, the SPDF ignores the information for the voice media flow knowing that that admission and policy control are already performed in the A-RACF for the voice media flow. <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "aracf-a@example.com" ] [ Media-Component-Description = { Media-Component-Number = 2 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from 192.168.0.1 31782 to 192.168.0.2 51372" ] [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 640000 ] [ Max-Requested-Bandwidth-UL = 640000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from 192.168.0.1 31783 to 192.168.0.2 51373" ] [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-DL = 32000 ] [ Max-Requested-Bandwidth-UL = 32000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = VIDEO (1) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 54a DIAMETER Rq A-RACF A SPDF A AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 55a DIAMETER Gq' SPDF A P-CSCF A AAA Because the AA-Request contained binding information for both the voice and the video media flows, the SPDF returns the complete set of binding information to the P-CSCF. In case the P-CSCF had not provided information on the previously established voice media flow, the SPDF would neither have returned binding information for this flow. <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 51372 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } ETSI ETSI TS 183 048 V2.2.1 (2009-08) 74 Step Protocol Interface From To Message { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 51373 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17462 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17463 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] ] ] ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 56a SIP P-CSCF A S-CSCF INVITE B INVITE sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 69 Record-Route: <sip:p-cscf-a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 2 INVITE Contact: <sip:user_a@phone-a.example.com> Content-Type: application/sdp Content-Length: 201 o=user_a 2890844526 2890842807 IN IP4 phone-a.example.com s=- c=IN IP4 10.0.0.1 t=0 0 m=audio 2222 RTP/AVP 0 a=sendrecv m=video 17462 RTP/AVP 31 a=rtpmap:31 H261/90000 a=sendrecv b=AS:640 57a SIP S-CSCF P-CSCF A 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 2 INVITE Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 75 Step Protocol Interface From To Message 58a SIP S-CSCF P-CSCF B INVITE B INVITE sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 68 Record-Route: <sip:s-cscf.example.com;lr>,<sip:p-cscf-a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 2 INVITE Contact: <sip:user_a@phone-a.example.com> Content-Type: application/sdp Content-Length: 201 o=user_a 2890844526 2890842807 IN IP4 phone-a.example.com s=- c=IN IP4 10.0.0.1 t=0 0 m=audio 2222 RTP/AVP 0 a=sendrecv m=video 17462 RTP/AVP 31 a=rtpmap:31 H261/90000 a=sendrecv b=AS:640 59a SIP P-CSCF B S-CSCF 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 2 INVITE Content-Length: 0 60a DIAMETER Gq' P-CSCF B SPDF B AAR <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-b@example.com" ] [ Media-Component-Description = { Media-Component-Number = 2 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Description = "permit out 17 from any to any" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 640000 ] [ Max-Requested-Bandwidth-DL = 640000] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Description = "permit out 17 from any to any" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-UL = 32000 ] [ Max-Requested-Bandwidth-DL = 32000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "downlink Offer m=video 17462 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 76 Step Protocol Interface From To Message ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17462 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17463 } ] } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 61a H.248 Ia SPDF B C-BGF B Modify terminations MEGACO/3 [spdf-b.example.com]:43924 Transaction = 3 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "B", gm/rsb = ON } Local { v=0 c=IN IP4 $ m=video $ RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 c=IN IP4 $ m=video $ RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 c=IN IP4 10.0.0.1 m=video 17462 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 } } /* Stream */ } /* Media */ ETSI ETSI TS 183 048 V2.2.1 (2009-08) 77 Step Protocol Interface From To Message } /* Modify */ } /* Context */ } /* Transaction */ 62a H.248 Ia C-BGF B SPDF B Reply (Add) MEGACO/3 [abgf-b.example.com]:43924 Reply = 3 { Context = 1 { Modify = ip/1/if1/1{ Media { Stream = 2 { LocalControl { ipdc/realm = "B", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 192.168.1.1 s=- t=0 0 c=IN IP4 192.168.1.1 m=video 32124 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1{ Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 c=IN IP4 10.0.0.2 m=video 1612 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 c=IN IP4 10.0.0.1 m=video 2222 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Reply */ 63a DIAMETER Rq SPDF B A-RACF B AAR <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "aracf-b@example.com" ] [ Media-Component-Description = { Media-Component-Number = 2 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 17 from any to 192.168.1.1 32124" ] [ Flow-Description = "permit out 17 from any to any" ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 78 Step Protocol Interface From To Message [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 640000 ] [ Max-Requested-Bandwidth-DL = 640000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit in 17 from any to 192.168.1.1 32125" ] [ Flow-Description = "permit out 17 from any to any" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-UL = 32000 ] [ Max-Requested-Bandwidth-DL = 32000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = VIDEO (1) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 64a DIAMETER Rq A-RACF B SPDF B AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 65a DIAMETER Gq' SPDF B P-CSCF B AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17462 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17463 } ] } [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 32124 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 79 Step Protocol Interface From To Message [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 32125 } ] ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 66a SIP P-CSCF B Phone B INVITE B INVITE sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 67 Record-Route: <sip:p-cscf-b.example.com;lr>,<sip:s-cscf.example.com;lr>,<sip:p-cscf- a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 2 INVITE Contact: <sip:user_a@phone-a.example.com> Content-Type: application/sdp Content-Length: 194 v=0 o=user_a 2890844526 2890842807 IN IP4 phone-a.example.com s=- c=IN IP4 192.168.1.1 t=0 0 m=audio 3332 RTP/AVP 0 a=sendrecv m=video 32124 RTP/AVP 31 a=rtpmap:31 H261/90000 a=sendrecv b=AS:640 67a SIP Phone B P-CSCF B 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 70 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 2 INVITE Contact: <sip:user_b@phone-b.example.com> Content-Type: application/sdp Content-Length: 194 v=0 o=user_b 29381748101 2948193018 IN IP4 phone-b.example.com s=- c=IN IP4 192.168.1.2 t=0 0 m=audio 29792 RTP/AVP 0 a=sendrecv m=video 25552 RTP/AVP 31 a=rtpmap:31 H261/90000 a=sendrecv b=AS:640 68a DIAMETER Gq' P-CSCF B SPDF B AAR (Modify) <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-b@example.com" ] [ Media-Component-Description = ETSI ETSI TS 183 048 V2.2.1 (2009-08) 80 Step Protocol Interface From To Message { Media-Component-Number = 2 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from any to 192.168.1.2 25552" ] [ Flow-Description = "permit in 17 from any to 192.168.1.1 32124" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 640000 ] [ Max-Requested-Bandwidth-UL = 640000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from any to 192.168.1.2 25553" ] [ Flow-Description = "permit in 17 from any to 192.168.1.1 32124" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-DL = 32000 ] [ Max-Requested-Bandwidth-UL = 32000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = VIDEO (1) ] [ Flow-Status = ENABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "uplink answer m=video 25552 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640" ] [ Codec-Data = "downlink offer m=video 32124 RTP/AVP 31 a=rtpmap:31 H261/90000 b=as:640" ] ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 25552 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17462 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 25553 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17463 } ] } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 69a H.248 Ia SPDF B C-BGF B Modify terminations MEGACO/3 [spdf-b.example.com]:43924 Transaction = 4 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "B", gm/rsb = ON, mode = SendReceive }, Local { v=0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 81 Step Protocol Interface From To Message o=- 0 0 IN IP4 192.168.1.1 s=- t=0 0 c=IN IP4 192.168.1.1 m=video 32124 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 } Remote { v=0 o=- 0 0 IN IP4 192.168.1.2 s=- t=0 0 c=IN IP4 192.168.1.2 m=video 25552 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 c=IN IP4 10.0.0.2 m=video $ RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 c=IN IP4 10.0.0.1 m=video 17462 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Transaction */ 70a H.248 Ia C-BGF B SPDF B Reply (Modify) MEGACO/3 [abgf-b.example.com]: 43924 Reply = 4 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "B", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 192.168.1.1 s=- t=0 0 c=IN IP4 192.168.1.1 m=video 32124 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 82 Step Protocol Interface From To Message }, Remote { v=0 o=- 0 0 IN IP4 192.168.1.2 s=- t=0 0 c=IN IP4 192.168.1.2 m=video 25552 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 c=IN IP4 10.0.0.2 m=video 1612 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 c=IN IP4 10.0.0.1 m=video 17462 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Reply */ 71a DIAMETER Rq SPDF B A-RACF B AAR (Modify) <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "aracf-b@example.com" ] [ Media-Component-Description = { Media-Component-Number = 2 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from 192.168.1.1 32124 to 192.168.1.2 25552" ] [ Flow-Description = "permit in 17 from 192.168.1.2 25552 to 192.168.1.1 32124" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 640000 ] [ Max-Requested-Bandwidth-DL = 640000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from 192.168.1.1 32125 to 192.168.1.2 25553" ] [ Flow-Description = "permit in 17 from 192.168.1.2 25553 to 192.168.1.1 32125" ] [ Flow-Usage = RTCP(1) ] [ Max-Requested-Bandwidth-UL = 32000 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 83 Step Protocol Interface From To Message [ Max-Requested-Bandwidth-DL = 32000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = VIDEO (1) ] [ Flow-Status = ENABLED } [ Reservation-Priority = DEFAULT (0) ] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 72a DIAMETER Re A-RACF B RCEF B PIR A policy modification request is sent to the RCEF by sending the Policy Install Request command with the PI-Request-Type AVP value set to UPDATE_REQUEST (2). The maximum requested bandwidth value in the QoS-Information AVP is set to the sum of the video media flow bandwidth and the RTCP bandwidth (672 000 bits/second). < PI-Request > ::= < Diameter Header: 315, REQ, PXY > < Session-Id = "aracf-b.example.com;66389;469" > { Auth-Application-Id = 16777253 (Re) } { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Destination-Host = "rcef-b.example.com" } { PI-Request-Type = UPDATE_REQUEST (2) } { PI-Request-Number = 1 } [ Auth-Session-State = NO_STATE_MAINTAINED (1) ] [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-B-UL" } [ Service-Identifier = 1 ] [ Rating-Group = 1 ] [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] [ Flow-Description = "permit in 17 from 192.168.1.2 25552 to 192.168.1.1 32124" ] [ Flow-Description = "permit in 17 from 192.168.1.2 25553 to 192.168.1.1 32125" ] [ Flow-Status = ENABLED-UPLINK (0) ] [ QoS-Information = [ Max-Requested-Bandwidth-UL = 672000 ] [ ToS-Traffic-Class = 101110 ] ] [ Precedence = 1] [ Flows = { Media-Component-Number = 2 } [ Flow-Number = 1 ] [ Flow-Number = 2 ] ] ] ] [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-B-DL" } [ Service-Identifier = 1 ] [ Rating-Group = 1 ] [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] [ Flow-Description = "permit out 17 from 192.168.1.1 31124 to 192.168.1.2 25552" ] [ Flow-Description = "permit out 17 from 192.168.1.1 31125 to 192.168.1.2 25553" ] [ Flow-Status = ENABLED-DOWNLINK (1) ] [ QoS-Information = [ Max-Requested-Bandwidth-DL = 672000 ] [ ToS-Traffic-Class = 101110 ] ] [ Precedence = 1] [ Flows = { Media-Component-Number = 2 } [ Flow-Number = 1 ] [ Flow-Number = 2 ] ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 84 Step Protocol Interface From To Message ] ] 73a DIAMETER Re RCEF B A-RACF B PIA <PI-Answer> ::= < Diameter Header: 315, PXY > < Session-Id = "aracf-b.example.com;66389;469" > { Origin-Host = "rcef-b.example.com" } { Origin-Realm = "example.com" } { PI-Request-Type = UPDATE_REQUEST (2) } { PI-Request-Number = 1 } [ Result-Code DIAMETER_SUCCESS (2001) ] 74a DIAMETER Rq A-RACF B SPDF B AAA (Modify) <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 75a DIAMETER Gq' SPDF B P-CSCF B AAA (Modify) <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 25552 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17462 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 25553 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17463 } ] } [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1612 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 32124 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1613 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 32125 } ] ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 85 Step Protocol Interface From To Message 76a SIP P-CSCF B S-CSCF 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 69 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_b@phone-b.example.com> Content-Type: application/sdp Content-Length: 189 v=0 o=user_b 29381748101 2948193018 IN IP4 phone-b.example.com s=- c=IN IP4 10.0.0.2 t=0 0 m=audio 1110 RTP/AVP 0 a=sendrecv m=video 1612 RTP/AVP 31 a=rtpmap:31 H261/90000 a=sendrecv b=AS:640 77a SIP S-CSCF P-CSCF A 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 68 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_b@phone-b.example.com> Content-Type: application/sdp Content-Length: 189 v=0 o=user_b 29381748101 2948193018 IN IP4 phone-b.example.com s=- c=IN IP4 10.0.0.2 t=0 0 m=audio 1110 RTP/AVP 0 a=sendrecv m=video 1612 RTP/AVP 31 a=rtpmap:31 H261/90000 a=sendrecv b=AS:640 78a DIAMETER Gq' P-CSCF A SPDF A AAR (Modify) <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-a@example.com" ] [ Media-Component-Description = { Media-Component-Number = 2 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Description = "permit out 17 from any to 192.168.0.2 51372" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 640000 ] [ Max-Requested-Bandwidth-DL = 640000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Description = "permit out 17 from any to 192.168.0.2 51373" ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 86 Step Protocol Interface From To Message [ Flow-Usage = RTCP(1) ] [ Max-Requested-Bandwidth-UL = 32000 ] [ Max-Requested-Bandwidth-DL = 32000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = VIDEO (1) ] [ Flow-Status = ENABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "uplink offer m=video 31372 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640" ] ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 31372 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1612 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 31373 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1613 } ] } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 79a H.248 Ia SPDF A C-BGF A Modify Terminations A (A to B) MEGACO/3 [spdf-a.example.com]:55555 Transaction = 4 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "A", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 192.168.0.1 s=- t=0 0 c=IN IP4 192.168.0.1 m=video $ RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 }, Remote { v=0 o=- 0 0 IN IP4 192.168.0.2 s=- t=0 0 c=IN IP4 192.168.0.2 m=video 51372 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 } } /* Stream */ ETSI ETSI TS 183 048 V2.2.1 (2009-08) 87 Step Protocol Interface From To Message } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 c=IN IP4 10.0.0.1 m=video 17462 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 c=IN IP4 10.0.0.2 m=video 1612 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Transaction */ 80a H.248 Ia C-BGF A SPDF A Reply (Modify) MEGACO/3 [abgf-a.example.com]:55555 Reply = 4 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "A", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 c=IN IP4 192.168.0.1 m=video 31444 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 }, Remote { v=0 o=- 0 0 IN IP4 192.168.0.2 s=- t=0 0 c=IN IP4 192.168.0.2 m=video 51372 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, ETSI ETSI TS 183 048 V2.2.1 (2009-08) 88 Step Protocol Interface From To Message mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 c=IN IP4 10.0.0.1 m=video 17462 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 c=IN IP4 10.0.0.2 m=video 1612 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:640 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Transaction */ 81a DIAMETER Rq SPDF A A-RACF A AAR (Modify) <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "aracf-a@example.com" ] [ Media-Component-Description = { Media-Component-Number = 2 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from 192.168.0.1 31444 to 192.168.0.2 51372" ] [ Flow-Description = "permit in 17 from 192.168.0.2 51372 to 192.168.0.1 31444" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 640000 ] [ Max-Requested-Bandwidth-DL = 640000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from 192.168.0.1 31445 to 192.168.0.2 51373" ] [ Flow-Description = "permit in 17 from 192.168.0.2 51373 to 192.168.0.1 31445" ] [ Flow-Usage = RTCP(1) ] [ Max-Requested-Bandwidth-UL = 32000 ] [ Max-Requested-Bandwidth-DL = 32000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = VIDEO (1) ] [ Flow-Status = ENABLED ] [ Reservation-Priority = DEFAULT (0) ] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 82a DIAMETER Re A-RACF A RCEF A PIR < PI-Request > ::= < Diameter Header: 315, REQ, PXY > < Session-Id = "aracf-a.example.com;32475;112" > { Auth-Application-Id = 16777253 (Re) } { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } ETSI ETSI TS 183 048 V2.2.1 (2009-08) 89 Step Protocol Interface From To Message { Destination-Host = "rcef-a.example.com" } { PI-Request-Type = UPDATE_REQUEST (2) } { PI-Request-Number = 1 } [ Auth-Session-State = NO_STATE_MAINTAINED (1) ] [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-A-UL" } [ Service-Identifier = 1 ] [ Rating-Group = 1 ] [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] [ Flow-Description = "permit in 17 from 192.168.0.2 51372 to 192.168.0.1 31444" ] [ Flow-Description = "permit in 17 from 192.168.0.2 51373 to 192.168.0.1 31445" ] [ Flow-Status = ENABLED-UPLINK (0) ] [ QoS-Information = [ Max-Requested-Bandwidth-UL = 672000 ] [ ToS-Traffic-Class = 101110 ] ] [ Precedence = 1] [ Flows = { Media-Component-Number = 2 } [ Flow-Number = 1 ] [ Flow-Number = 2 ] ] ] ] [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-A-DL" } [ Service-Identifier = 1 ] [ Rating-Group = 1 ] [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] [ Flow-Description = "permit out 17 from 192.168.0.1 31444 to 192.168.0.2 51372" ] [ Flow-Description = "permit out 17 from 192.168.0.1 31445 to 192.168.0.2 51373" ] [ Flow-Status = ENABLED-DOWNLINK (1) ] [ QoS-Information = [ Max-Requested-Bandwidth-DL = 672000 ] [ ToS-Traffic-Class = 101110 ] ] [ Precedence = 1] [ Flows = { Media-Component-Number = 2 } [ Flow-Number = 1 ] [ Flow-Number = 2 ] ] ] ] 83a DIAMETER Re RCEF A A-RACF A PIA <PI-Answer> ::= < Diameter Header: 315, PXY > < Session-Id = "aracf-a.example.com;32475;112" > { Origin-Host = "rcef-a.example.com" } { Origin-Realm = "example.com" } { PI-Request-Type = UPDATE_REQUEST (2) } { PI-Request-Number = 1 } [ Result-Code DIAMETER_SUCCESS (2001) ] 84a DIAMETER Rq A-RACF A SPDF A AAA (Modify) <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 90 Step Protocol Interface From To Message 85a DIAMETER Gq' SPDF A P-CSCF A AAA (Modify) <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 51371 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1612 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 51373 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1613 } ] } [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17462 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.1 } { Port-Number = 31444 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17463 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.1 } { Port-Number = 31445 } ] ] ] [ Authorization-Lifetime = 450 ] { Auth-Grace-Period = 10 } 86a SIP P-CSCF A Phone A 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 67 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_b@phone-b.example.com> Content-Type: application/sdp Content-Length: 192 v=0 o=user_b 29381748101 2948193018 IN IP4 phone-b.example.com s=- c=IN IP4 192.168.0.1 t=0 0 m=audio 4444 RTP/AVP 0 a=sendrecv m=video 31444 RTP/AVP 31 a=rtpmap:31 H261/90000 a=sendrecv b=AS:640 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 91 Step Protocol Interface From To Message 87a SIP Phone A P-CSCF A ACK ACK sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 70 Route: <sip:p-cscf-a.example.com;lr>,<sip:s-cscf.example.com;lr>,<sip:p-cscf-b.example.com;lr> From: User A <sip:user_a@example.com>;tag=348123 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 2 ACK Content-Length: 0 88a SIP P-CSCF A S-CSCF ACK ACK sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 69 Route: <sip:s-cscf.example.com;lr>,<sip:p-cscf-b.example.com;lr> From: User A <sip:user_a@example.com>;tag=348123 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 2 ACK Content-Length: 0 89a SIP S-CSCF P-CSCF B ACK ACK sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 68 Route: <sip:p-cscf-b.example.com;lr> From: User A <sip:user_a@example.com>;tag=348123 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 2 ACK Content-Length: 0 90a SIP P-CSCF B Phone B ACK ACK sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060; branch=z9hG4bK74b03 Max-Forwards: 67 From: User A <sip:user_a@example.com>;tag=348123 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 2 ACK Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 92
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
6.2 IMS signalling flow involving IBCF entities
|
Figure 6.2.1 illustrates the example network architecture. Figure 6.2.1: IMS end-to-end signalling flow between two SIP end-points - including IBGF The additional addresses and ports used in the example compared to the basic call flow described in clause 5.1 are as follows: • A4 = 10.0.0.3:5554 for RTP and 10.0.0.3:5555 for RTCP. • A5 = 10.0.1.1:6666 for RTP and 10.0.1.1:6667 for RTCP. • B4 = 10.0.0.5:7776 for RTP and 10.0.0.5:7777 for RTCP. • B5 = 10.0.1.2:8888 for RTP and 10.0.1.2:8889 for RTCP. ETSI ETSI TS 183 048 V2.2.1 (2009-08) 93
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
6.2.1 Session setup
|
I-BGF A IBCF A SPDF AA IBCF B SPDF BB I-BGF B INVITE B AAR Add Reply AAA INVITE B S-CSCF A S-CSCF B AAR Add Reply AAA INVITE B 200 OK AAR Add Reply AAA 200 OK AAR Add Reply AAA 200 OK ACK ACK ACK 10.0 10.1 10.3 10.2 10.4 10.5 10.6 10.7 10.8 10.9 10.10 33.0 33.1 33.2 33.3 33.4 33.5 33.6 33.7 33.8 33.9 33.10 45.0 45.1 45.2 100 Trying 100 Trying 100 Trying 10.11 10.12 10.13 10.0 10.1 10.3 10.2 10.4 10.5 10.6 10.7 10.8 10.9 10.10 10.11 10.12 10.13 33.0 33.1 33.2 33.3 33.4 33.5 33.6 33.7 33.8 33.9 33.10 45.0 45.1 45.2 Figure 6.2.1.1: IMS end-to-end signalling chart for the IBCF - session setup ETSI ETSI TS 183 048 V2.2.1 (2009-08) 94 Table 6.2.1.1: IMS end-to-end messages for IBCF - session setup Step Protocol Interface From To Message 10.0 SIP S-CSCF A IBCF A INVITE B INVITE sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP s-cscf-a.example.com:5060;branch=z9hG4bKpm5lmx Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 68 Record-Route: <sip:s-cscf-a.example.com;lr>,<sip:p-cscf-a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_a@phone-a.example.com> Content-Type: application/sdp Content-Length: 135 v=0 o=user_a 2890844526 2890842807 IN IP4 phone-a.example.com s=- c=IN IP4 10.0.0.1 t=0 0 m=audio 2222 RTP/AVP 0 a=sendrecv 10.1 SIP IBCF A S-CSCF A 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP s-cscf-a.example.com:5060;branch=z9hG4bKpm5lmx Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Content-Length: 0 10.2 DIAMETER Gq' IBCF A SPDF AA AAR IBCF A uses the IP address of the SDP as the Globally-Unique-Address (i.e. the local IP address and port of the termination in C-BGF A that is associated with the IP address and port of Phone A). It is assumed that this association is statically established in C-BGF A to facilitate SIP signalling between the different address domains. It should be noted that the out direction indicates when given by an IBCF the inbound direction towards the local core network (i.e. for this message from B to A). <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "ibcf-a.example.com;14511D;557" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "ibcf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-aa.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from any to 10.0.0.1 2222" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from any to 10.0.0.1 2223" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-DL = 8000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } ETSI ETSI TS 183 048 V2.2.1 (2009-08) 95 Step Protocol Interface From To Message { Port-Number = 2222 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2223 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 10.0.0.1 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 10.3 H.248 Ia SPDF AA I-BGF A Add terminations The terminations are by default created as Inactive. Hence, the LocalControl descriptor is omitted in this message. SPDF AA defines all IP termination fields except the Id field. The Interface field is set to if1, which is at the peer core network side of I-BGF A, to define the direction at which the termination is to be created. MEGACO/3 [ibcf-a.example.com]:55555 Transaction = 1 { Context = ${ Add = ip/1/$/$ { Media { Stream = 1 { LocalControl { ipdc/realm = "CoreA", gm/rsb = ON } Local { v=0 m=- $ - - c=IN IP4 $ b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 2222 - - c=IN IP4 10.0.0.1 b=AS:104 } } /* Stream */ } /* Media */ } /* Add */ Add = ip/1/$/$ { Media { Stream = 1 { LocalControl { ipdc/realm = "BCoreNNI", gm/rsb = ON } Local { v=0 m=- $ - - c=IN IP4 $ b=AS:104 } } /* Stream */ } /* Media */ } /* Add */ } /* Context */ } /* Transaction */ ETSI ETSI TS 183 048 V2.2.1 (2009-08) 96 Step Protocol Interface From To Message 10.4 H.248 Ia I-BGF A SPDF AA Reply (Add) MEGACO/3 [ibgf-a.example.com]:55555 Reply = 1 { Context = 1 { Add = ip/1/if1/1, Media { Stream = 1 { LocalControl { ipdc/realm = "CoreA", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 10.0.0.3 s=- t=0 0 m=- 5554 - - c=IN IP4 10.0.0.3 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 2222 - - c=IN IP4 10.0.0.1 b=AS:104 } } /* Stream */ } /* Media */ } /* Add */ Add = ip/1/if2/1, Media { Stream = 1 { LocalControl { ipdc/realm = "BCoreNNI", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 10.0.1.1 s=- t=0 0 m=- 6666 - - c=IN IP4 10.0.1.1 b=AS:104 } } /* Stream */ } /* Media */ } /* Add */ } /* Context */ } /* Reply */ 10.5 DIAMETER Gq' SPDF AA IBCF A AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "ibcf-a.example.com; 14511D;557" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-aa.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2222 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2223 } ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 97 Step Protocol Interface From To Message [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.1.1 } { Port-Number = 6666 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.1.1 } { Port-Number = 6667 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] ] ] ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 10.6 SIP IBCF A IBCF B INVITE B INVITE sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP ibcf-a.example.com:5060;branch=z9hG4bKhfj55z Via: SIP/2.0/UDP s-cscf-a.example.com:5060;branch=z9hG4bKpm5lmx Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 67 Record-Route: <sip:ibcf-a.example.com;lr>,<sip:s-cscf-a.example.com;lr>,<sip:p-cscf- a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_a@phone-a.example.com> Content-Type: application/sdp Content-Length: 135 v=0 o=user_a 2890844526 2890842807 IN IP4 phone-a.example.com s=- c=IN IP4 10.0.1.1 t=0 0 m=audio 6666 RTP/AVP 0 a=sendrecv 10.7 SIP IBCF B IBCF A 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP ibcf-a.example.com:5060;branch=z9hG4bKhfj55z Via: SIP/2.0/UDP s-cscf-a.example.com:5060;branch=z9hG4bKpm5lmx Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 98 Step Protocol Interface From To Message 10.8 DIAMETER Gq' IBCF B SPDF BB AAR IBCF B uses the IP address of the signalling destination as the Globally-Unique-Address (i.e. the IP address and port of the IP address and port of C-BGF B that is associated with the IP address and port of Phone B). It is assumed that this association is statically established in C-BGF B to facilitate SIP signalling between the different address domains. It should be noted that the "in" direction indicates when given by an IBCF the inbound direction towards the peer core network (i.e. for this message from B to A). The Flow-Description is given from any to any based on the decision that it is to provide addresses for the local core network and not the link between the two core networks. This decision follows the same logic as used for the access where the Flow-Description provides addresses for the access network domain only. <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "ibcf-b.example.com;25536F;231" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "ibcf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-bb.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-DL = 8000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.1.1 } { Port-Number = 6666 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.1.1 } { Port-Number = 6667 } ] } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 10.0.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 10.9 H.248 Ia SPDF BB I-BGF B Add terminations MEGACO/3 [ibcf-b.example.com]:55555 Transaction = 1 { Context = $ { Add = ip/1/$/$ { Media { Stream = 1 { LocalControl { ipdc/realm = "CoreB", gm/rsb = ON } ETSI ETSI TS 183 048 V2.2.1 (2009-08) 99 Step Protocol Interface From To Message Local { v=0 m=- $ - - c=IN IP4 $ b=AS:104 } } /* Stream */ } /* Media */ } /* Add */ Add = ip/1/$/$ { Media { Stream = 1 { LocalControl { ipdc/realm = "ACoreNNI", gm/rsb = ON } Local { v=0 m=- $ - - c=IN IP4 $ b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 10.0.1.1 s=- t=0 0 m=- 6666 - - c=IN IP4 10.0.1.1 b=AS:104 } } /* Stream */ } /* Media */ } /* Add */ } /* Context */ } /* Transaction */ 10.10 H.248 Ia I-BGF B SPDF BB Reply (Add) MEGACO/3 [ibgf-b.example.com]:55555 Reply = 1 { Context = 1 { Add = ip/1/if1/1 Media { Stream = 1 { LocalControl { ipdc/realm = "CoreB", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 10.0.0.5 s=- t=0 0 m=- 7776 - - c=IN IP4 10.0.0.5 b=AS:104 } } /* Stream */ } /* Media */ } /* Add */ Add = ip/1/if2/1 Media { Stream = 1 { LocalControl { ipdc/realm = "ACoreNNI", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 10.0.1.2 s=- t=0 0 m=- 8888 - - c=IN IP4 10.0.1.2 b=AS:104 }, ETSI ETSI TS 183 048 V2.2.1 (2009-08) 100 Step Protocol Interface From To Message Remote { v=0 o=- 0 0 IN IP4 10.0.1.1 s=- t=0 0 m=audio 6666 RTP/AVP 0 c=IN IP4 10.0.1.1 b=AS:104 } } /* Stream */ } /* Media */ } /* Add */ } /* Context */ } /* Reply */ 10.11 DIAMETER Gq' SPDF BB IBCF B AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "ibcf-b.example.com;25536F;231" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-bb.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.1.1 } { Port-Number = 6666 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.1.1 } { Port-Number = 6667 } ] [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.5 } { Port-Number = 7776 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.5 } { Port-Number = 7777 } ] ] ] ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 10.12 SIP IBCF B S-CSCF B INVITE B INVITE sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP ibcf-b.example.com:5060;branch=z9hG4bKH23gzx Via: SIP/2.0/UDP ibcf-a.example.com:5060;branch=z9hG4bKhfj55z Via: SIP/2.0/UDP s-cscf-a.example.com:5060;branch=z9hG4bKpm5lmx Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 66 Record-Route: <sip:ibcf-b.example.com;lr>,<sip:ibcf-a.example.com;lr>,<sip:s-cscf- a.example.com;lr>,<sip:p-cscf-a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> ETSI ETSI TS 183 048 V2.2.1 (2009-08) 101 Step Protocol Interface From To Message Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_a@phone-a.example.com> Content-Type: application/sdp Content-Length: 125 v=0 o=user_a 2890844526 2890842807 IN IP4 phone-a.example.com s=- c=IN IP4 10.0.0.5 t=0 0 m=audio 7776 RTP/AVP 0 a=sendrecv 10.13 SIP S-CSCF B IBCF B 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP ibcf-b.example.com:5060;branch=z9hG4bKH23gzx Via: SIP/2.0/UDP ibcf-a.example.com:5060;branch=z9hG4bKhfj55z Via: SIP/2.0/UDP s-cscf-a.example.com:5060;branch=z9hG4bKpm5lmx Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Content-Length: 0 The above message finishes the first addition to the basic call setup signalling flow. Below follows the second addition to that signalling flow. 33.0 SIP S-CSCF B IBCF B 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP ibcf-b.example.com:5060;branch=z9hG4bKH23gzx Via: SIP/2.0/UDP ibcf-a.example.com:5060;branch=z9hG4bKhfj55z Via: SIP/2.0/UDP s-cscf-a.example.com:5060;branch=z9hG4bKpm5lmx Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 68 Record-Route: <sip:p-cscf-b.example.com;lr>,<sip:s-cscf-b.example.com;lr>,<sip:ibcf- b.example.com;lr>,<sip:ibcf-a.example.com;lr>,<sip:s-cscf-a.example.com;lr>,<sip:p-cscf- a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_b@phone-b.example.com> Content-Type: application/sdp Content-Length: 126 v=0 o=user_b 29381748101 2948193018 IN IP4 phone-b.example.com s=- c=IN IP4 10.0.0.2 t=0 0 m=audio 1110 RTP/AVP 0 a=sendrecv 33.1 DIAMETER Gq' IBCF B SPDF BB AAR (Modify) IBCF B uses the IP address of the signalling destination as the Globally-Unique-Address (i.e. the IP address and port of the IP address and port of C-BGF B that is associated with the IP address and port of Phone B). It should be noted that the "in" direction indicates when given by an IBCF the inbound direction towards the peer core network (i.e. for this message from B to A) and out direction indicates when given by an IBCF the inbound direction towards the local core network (i.e. for this message from A to B). This message contains addresses and ports for both directions in the Binding-Input-List to allow these addresses and ports to be uniquely related to the directions given in the Flow-Descriptions (i.e. although the termination for the "in" direction is already established). That is, the direction given by the first Flow-Description refers to the first V4-Transport-Address in the Binding-Input-List, the second Flow-Description gives the direction of the second V4-Transport-Address in the Binding-Input-List, and so on. ETSI ETSI TS 183 048 V2.2.1 (2009-08) 102 Step Protocol Interface From To Message <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "ibcf-b.example.com;25536F;231" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "ibcf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-bb.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from any to 10.0.0.2 1110" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from any to 10.0.0.2 1111" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-DL = 8000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = ENABLED ] [ Reservation-Priority = DEFAULT (0) ] ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1110 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.1.1 } { Port-Number = 6666 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1111 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.1.1 } { Port-Number = 6667 } ] } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 10.0.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 33.2 H.248 Ia SPDF BB I-BGF B Modify terminations SPDF BB (i.e. since it is a state full MGC) knows that the termination for the "in" direction is already established and therefore issues an add message for the "out" direction only. MEGACO/3 [ibcf-b.example.com]:55555 Transaction = 2 { Context = 1{ Modify = ip/1/if1/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "CoreB", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.0.5 s=- t=0 0 m=- 7776 - - c=IN IP4 10.0.0.5 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 103 Step Protocol Interface From To Message b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 m=- 1110 - - c=IN IP4 10.0.0.2 b=AS:104 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "ACoreNNI", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.1.2 s=- t=0 0 m=- 8888 - - c=IN IP4 10.0.1.2 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 10.0.1.1 s=- t=0 0 m=- 6666 - - c=IN IP4 10.0.1.1 b=AS:104 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Transaction */ 33.3 H.248 Ia I-BGF B SPDF BB Reply (Modify) MEGACO/3 [ibgf-b.example.com]:55555 Reply = 2 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "CoreB", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.0.5 s=- t=0 0 m=- 7776 - - c=IN IP4 10.0.0.5 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 m=- 1110 - - c=IN IP4 10.0.0.2 b=AS:104 } ETSI ETSI TS 183 048 V2.2.1 (2009-08) 104 Step Protocol Interface From To Message } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "ACoreNNI", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.1.2 s=- t=0 0 m=- 8888 - - c=IN IP4 10.0.1.2 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 10.0.1.1 s=- t=0 0 m=- 6666 - - c=IN IP4 10.0.1.1 b=AS:104 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Reply */ 33.4 DIAMETER Gq' SPDF BB IBCF B AAA Since SPDF BB provided Binding-Input-Lists for all addresses and ports in both directions the AAA will include this complete set of addresses and ports in the Binding-Information AVP as well. <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "ibcf-b.example.com;25536F;231" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-bb.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1110 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.1.1 } { Port-Number = 6666 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1111 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.1.1 } { Port-Number = 6667 } ] [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.1.2 } { Port-Number = 8888 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.5 } { Port-Number = 7776 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.1.2 } { Port-Number = 8889 } ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 105 Step Protocol Interface From To Message [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.5 } { Port-Number = 7777 } ] ] ] ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 33.5 SIP IBCF B IBCF A 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP ibcf-a.example.com:5060;branch=z9hG4bKhfj55z Via: SIP/2.0/UDP s-cscf-a.example.com:5060;branch=z9hG4bKpm5lmx Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 67 Record-Route: <sip:p-cscf-b.example.com;lr>,<sip:s-cscf-b.example.com;lr>,<sip:ibcf- b.example.com;lr>,<sip:ibcf-a.example.com;lr>,<sip:s-cscf-a.example.com;lr>,<sip:p-cscf- a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_b@phone-b.example.com> Content-Type: application/sdp Content-Length: 126 v=0 o=user_b 29381748101 2948193018 IN IP4 phone-b.example.com s=- c=IN IP4 10.0.1.2 t=0 0 m=audio 8888 RTP/AVP 0 a=sendrecv 33.6 DIAMETER Gq' IBCF A SPDF AA AAR (Modify) It should be noted that the "in" direction indicates when given by an IBCF the inbound direction towards the peer core network (i.e. for this message from A to B) and "out" direction indicates when given by an IBCF the inbound direction towards the local core network (i.e. for this message from B to A). <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "ibcf-a.example.com;14511D;557" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "ibcf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-aa.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-DL = 8000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = ENABLED ] [ Reservation-Priority = DEFAULT (0) ] ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2222 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.1.2 } ETSI ETSI TS 183 048 V2.2.1 (2009-08) 106 Step Protocol Interface From To Message { Port-Number = 8888 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2223 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.1.2 } { Port-Number = 8887 } ] } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 10.0.0.1 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 33.7 H.248 Ia SPDF AA I-BGF A Modify terminations SPDF AA (i.e. since it is a state full MGC) knows that the termination for the "out" direction is already established and therefore issues an add message for the "in" direction only. MEGACO/3 [ibcf-b.example.com]:55555 Transaction = 2 { Context = 1{ Modify = ip/1/if1/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "CoreA", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.0.3 s=- t=0 0 m=- 5554 - - c=IN IP4 10.0.0.3 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 2222 - - c=IN IP4 10.0.0.1 b=AS:104 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "BCoreNNI", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.1.1 s=- t=0 0 m=- 6666 - - c=IN IP4 10.0.1.1 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 10.0.1.2 s=- ETSI ETSI TS 183 048 V2.2.1 (2009-08) 107 Step Protocol Interface From To Message t=0 0 m=- 8888 - - c=IN IP4 10.0.1.2 b=AS:104 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Transaction */ 33.8 H.248 Ia I-BGF A SPDF AA Reply (Modify) MEGACO/3 [ibgf-b.example.com]:55555 Reply = 2 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "CoreA", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.0.3 s=- t=0 0 m=- 5554 - - c=IN IP4 10.0.0.3 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 2222 - - c=IN IP4 10.0.0.1 b=AS:104 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "BCoreNNI", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.1.1 s=- t=0 0 m=- 6666 - - c=IN IP4 10.0.1.1 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 10.0.1.2 s=- t=0 0 m=- 8888 - - c=IN IP4 10.0.1.2 b=AS:104 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Reply */ ETSI ETSI TS 183 048 V2.2.1 (2009-08) 108 Step Protocol Interface From To Message 33.9 DIAMETER Gq' SPDF AA IBCF A AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "ibcf-a.example.com;14511D;557" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-aa.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2222 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.1.2 } { Port-Number = 8888 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2223 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.1.2 } { Port-Number = 8889 } ] [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.1.1 } { Port-Number = 6666 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.3 } { Port-Number = 5554 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.1.1 } { Port-Number = 6667 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.3 } { Port-Number = 5555 } ] ] ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 33.10 SIP IBCF A S-CSCF A 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP ibcf-a.example.com:5060;branch=z9hG4bKhfj55z Via: SIP/2.0/UDP s-cscf-a.example.com:5060;branch=z9hG4bKpm5lmx Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 66 Record-Route: <sip:p-cscf-b.example.com;lr>,<sip:s-cscf-b.example.com;lr>,<sip:ibcf- b.example.com;lr>,<sip:ibcf-a.example.com;lr>,<sip:s-cscf-a.example.com;lr>,<sip:p-cscf- a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_b@phone-b.example.com> Content-Type: application/sdp Content-Length: 126 v=0 o=user_b 29381748101 2948193018 IN IP4 phone-b.example.com s=- c=IN IP4 10.0.0.3 t=0 0 m=audio 5554 RTP/AVP 0 a=sendrecv ETSI ETSI TS 183 048 V2.2.1 (2009-08) 109 Step Protocol Interface From To Message The above message finishes the second addition to the basic call setup signalling flow. Below follows the third addition to that signalling flow. 45.0 SIP S-CSCF A IBCF A ACK ACK sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP s-cscf-a.example.com:5060;branch=z9hG4bKpm5lmx Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 68 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 2 ACK Contact: <sip:user_a@phone-a.example.com> Content-Length: 0 45.2 SIP IBCF A IBCF B ACK ACK sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP ibcf-a.example.com:5060;branch=z9hG4bKhfj55z Via: SIP/2.0/UDP s-cscf-a.example.com:5060;branch=z9hG4bKpm5lmx Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 67 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 2 ACK Contact: <sip:user_a@phone-a.example.com> Content-Length: 0 45.3 SIP IBCF B S-CSCF B ACK ACK sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP ibcf-b.example.com:5060;branch=z9hG4bKH23gzx Via: SIP/2.0/UDP ibcf-a.example.com:5060;branch=z9hG4bKhfj55z Via: SIP/2.0/UDP s-cscf-a.example.com:5060;branch=z9hG4bKpm5lmx Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 66 From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 4 UPDATE Contact: <sip:user_a@phone-a.example.com> Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 110
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
6.2.2 Session termination
|
Figure 6.2.2.1: IMS end-to-end signalling chart for IBCF - session teardown Table 6.2.2.1: IMS end-to-end messages for IBCF - session teardown Step Protocol Interface From To Message 57.0 SIP S-CSCF B IBCF B BYE BYE sip:user_a@example.com SIP/2.0 Via: SIP/2.0/UDP s-cscf-b.example.com:5060;branch=fg7gjHl3ss8r Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP phone-b.example.com:5060;branch=z9hG4bKjwafcb9 Max-Forwards: 68 Route: <sip:ibcf-b.example.com;lr>,<sip:ibcf-a.example.com;lr>, <sip:s-cscf-a.example.com;lr>, <sip:p-cscf-a.example.com;lr From: User B <sip:user_b@example.com>;tag=4fxdce12ls To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 57.1 DIAMETER Gq´ IBCF B SPDF BB STR <ST-Request> ::= < Diameter Header: 275, REQ, PXY > < Session-Id = "ibcf-b.example.com;25536F;231" > { Origin-Host = "ibcf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Termination-Cause = DIAMETER_LOGOUT } { Auth-Application-Id = 16777222 (Gq) } [ Destination-Host = " spdf-bb.example.com" ] 57.2 H.248 Ia SPDF BB I-BGF B Subtract termination BB MEGACO/3 [ibcf-b.example.com]:55555 Transaction = 3 { Context = 1 { Subtract = ip/1/if1/1 {Audit{Statistics}} Subtract = ip/1/if2/1 {Audit{Statistics}} } /* Context */ } /* Transaction */ 57.3 H.248 Ia I-BGF B SPDF BB Reply MEGACO/3 [ibgf-b.example.com]:55555 Reply = 3 { Context = 1 { Subtract = ip/1/if1/1 { Statistics { nt/dur=450000, ; in milliseconds nt/os=5400000, ; Octets Sent ETSI ETSI TS 183 048 V2.2.1 (2009-08) 111 Step Protocol Interface From To Message nt/or=5400000, ; Octets Received gm/dp=0 ; number of packets discarded } } Subtract = ip/1/if2/1 { Statistics { nt/dur=450000, ; in milliseconds nt/os=450000, ; Octets Sent nt/or=450000, ; Octets Received gm/dp=0 ; number of packets discarded } } /* Subtract */ } /* Context */ } /* Reply */ 57.4 DIAMETER Gq' SPDF BB IBCF B STA <ST-Answer> ::= < Diameter Header: 275, PXY > < Session-Id = "ibcf-b.example.com;25536F;231" > { Origin-Host = "spdf-bb.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] 57.5 SIP IBCF B IBCF A BYE BYE sip:user_a@example.com SIP/2.0 Via: SIP/2.0/UDP ibcf-b.example.com:5060;branch=z9hG4bKH23gzx Via: SIP/2.0/UDP s-cscf-b.example.com:5060;branch=fg7gjHl3ss8r Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP phone-b.example.com:5060;branch=z9hG4bKjwafcb9 Max-Forwards: 67 Route: <sip:ibcf-a.example.com;lr>, <sip:s-cscf-a.example.com;lr>, <sip:p-cscf-a.example.com;lr From: User B <sip:user_b@example.com>;tag=4fxdce12ls To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0 57.6 DIAMETER Gq' IBCF A SPDF AA STR <ST-Request> ::= < Diameter Header: 275, REQ, PXY > < Session-Id = "ibcf-a.example.com;14511D;557" > { Origin-Host = "ibcf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Termination-Cause = DIAMETER_LOGOUT } { Auth-Application-Id = 16777222 (Gq) } [ Destination-Host = " spdf-aa.example.com" ] 57.7 H.248 Ia SPDF AA I-BGF A Subtract termination AA MEGACO/3 [ibcf-a.example.com]:55555 Transaction = 3 { Context = 1 { Subtract = ip/1/if1/1 {Audit{Statistics}} Subtract = ip/1/if2/1 {Audit{Statistics}} } /* Context */ } /* Transaction */ 57.8 H.248 Ia I-BGF A SPDF AA Reply MEGACO/3 [ibgf-a.example.com]:55555 Reply = 3 { Context = 1 { Subtract = ip/1/if1/1 { Statistics { nt/dur=450000, ; in milliseconds nt/os=5400000, ; Octets Sent nt/or=5400000, ; Octets Received gm/dp=0 ; number of packets discarded } } Subtract = ip/1/if2/1 { Statistics { nt/dur=450000, ; in milliseconds nt/os=450000, ; Octets Sent ETSI ETSI TS 183 048 V2.2.1 (2009-08) 112 Step Protocol Interface From To Message nt/or=450000, ; Octets Received gm/dp=0 ; number of packets discarded } } /* Subtract */ } /* Context */ } /* Reply */ 57.9 DIAMETER Gq' SPDF AA IBCF A STA <ST-Answer> ::= < Diameter Header: 275, PXY > < Session-Id = "ibcf-a.example.com;14511D;557" > { Origin-Host = "spdf-aa.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] 57.10 SIP IBCF A S-CSCF A BYE BYE sip:user_a@example.com SIP/2.0 Via: SIP/2.0/UDP ibcf-a.example.com:5060;branch=z9hG4bKhfj55z Via: SIP/2.0/UDP ibcf-b.example.com:5060;branch=z9hG4bKH23gzx Via: SIP/2.0/UDP s-cscf-b.example.com:5060;branch=fg7gjHl3ss8r Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP phone-b.example.com:5060;branch=z9hG4bKjwafcb9 Max-Forwards: 66 Route: <sip:s-cscf-a.example.com;lr>, <sip:p-cscf-a.example.com;lr From: User B <sip:user_b@example.com>;tag=4fxdce12ls To: User A <sip:user_a@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 BYE Content-Length: 0
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
6.3 IMS-based IPTV
|
6.3.1 Enabling BC service Figure 6.3.1.1 illustrates the example network architecture. AF (P-CSCF A) SPDF A A-RACF A Gq’ Rq AF (BC-SCF) RCEF/ BTF A Re Access Node A Gm AF (S-CSCF) Mw ISC UE A MDF Network AF (BC-SCF) A1 A2 Figure 6.3.1.1: IMS-based IPTV -BC service ETSI ETSI TS 183 048 V2.2.1 (2009-08) 113 The addresses and ports used in the example are as follows: • A1 = 192.168.0.2 (used as identifier of the user only). • A2 = 192.168.0.3 (the MDF uses different port numbers for different BC channels and IP multicast addresses). • Three BC channels: - Source 192.168.0.3 14368, Multicast 235.160.32.14 12954. - Source 192.168.0.3 14370, Multicast 235.160.32.10 12832. - Source 192.168.0.3 14368, Multicast 235.160.32.12 12996. The RTP stream is assumed to consume 2 500 000 kbps for HD TV. The TTL set for the multicast streams is 10. Note that the TTL is required at the c-line by [14]. However, as stated in [14] its use to scope multicast traffic is deprecated and applications SHOULD use an administratively scoped address instead. UE A P-CSCF A SPDF A A-RACF A BC-SCF INVITE BC AAR AAR AAA AAA INVITE BC INVITE BC 200 OK 200 OK ACK ACK ACK RCEF/BTF A S-CSCF 100 Trying 1 2 4 3 5 6 7 8 9 10 11 12 13 14 15 16 17 100 Trying 200 OK MULTICAST JOIN PIR PIA 1 2 4 3 5 6 7 8 9 10 11 12 13 14 15 16 17 AAR AAR AAA AAA 18 19 20 21 18 19 20 21 Figure 6.3.1.2: Enabling BC service -IMS-based IPTV ETSI ETSI TS 183 048 V2.2.1 (2009-08) 114 Table 6.3.1.1: Messages for enabling BC service -IMS-based IPTV Step Protocol Interface From To Message 1 SIP Gm UE A P-CSCF A INVITE BC Before issuing the INVITE for BC IPTV, the UE needs to perform Service Discovery and Service Selection following the procedures defined in [10]. The signalling involved in performing those procedures is out of the scope for the present document. INVITE sip:bc_service@example.com SIP/2.0 Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 70 Route: <sip:p-cscf-a.example.com;lr> From: UE A <sip:ue_a@example.com>;tag=372183 To: BC service <sip:bc_service@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 INVITE Contact: <sip:user_a@ue-a.example.com> Content-Type: application/sdp Content-Length: 256 v=0 o=user_a 2890844526 2890842807 IN IP4 ue-a.example.com s=- c=IN IP4 235.160.32.14/10 m=video 12954 RTP/AVP 33 a=rtpmap:33 dvbip-alfec-base/90000 a=bc_service:channel_1@iptv_broadcast_example a=bc_service_package:package_1@3FB7 a=recvonly b=AS:2500 2 SIP Gm P-CSCF A UE A 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 From: User A <sip:user_a@example.com>;tag=372183 To: BC service <sip:bc_service@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 INVITE Content-Length: 0 3 DIAMETER Gq' P-CSCF A SPDF A AAR The P-CSCF maps the parameters in the SDP to service information for Diameter AVPs in the AA-Request over Gq' according to annex C.1 in (TS 183 017 V2.3.1 [4]). <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = spdf-a@example.com ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from any to 235.160.32.14 12954" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 2500000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = VIDEO (1) ] [ Flow-Status = DISABLED (3) ] [ Reservation-Priority = DEFAULT (0) ] [ Media-Authorization-Context-Id = "package_1@3FB7"] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 115 Step Protocol Interface From To Message 4 DIAMETER Rq SPDF A A-RACF A AAR <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = aracf-a@example.com ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from any to 235.160.32.14 12954" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 2500000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = VIDEO (1) ] [ Flow-Status = DISABLED (3)] [ Reservation-Priority = DEFAULT (0) ] [ Media-Authorization-Context-Id = "package_1@3FB7"] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 5 DIAMETER Rq A-RACF A SPDF A AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 6 DIAMETER Gq' SPDF A P-CSCF A AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 7 SIP Mw P-CSCF A S-CSCF INVITE BC INVITE sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 69 Record-Route: <sip:p-cscf-a.example.com;lr> From: UE A <sip:ue_a@example.com>;tag=372183 To: BC service <sip:bc_service@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 INVITE Contact: <sip:user_a@ue-a.example.com> Content-Type: application/sdp Content-Length: 256 v=0 o=user_a 2890844526 2890842807 IN IP4 ue-a.example.com s=- c=IN IP4 235.160.32.14/10 m=video 12954 RTP/AVP 33 a=rtpmap:33 dvbip-alfec-base/90000 a=bc_service:channel_1@iptv_broadcast_example a=bc_service_package:package_1@3FB7 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 116 Step Protocol Interface From To Message a=recvonly b=AS:2500 8 SIP Mw S-CSCF P-CSCF A 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 From: User A <sip:user_a@example.com>;tag=372183 To: BC service <sip:bc_service@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 INVITE Content-Length: 0 9 SIP ISC S-CSCF BC-SCF INVITE BC INVITE sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 68 Record-Route: <sip:s-cscf.example.com;lr>,<sip:p-cscf-a.example.com;lr> From: UE A <sip:ue_a@example.com>;tag=372183 To: BC service <sip:bc_service@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 INVITE Contact: <sip:user_a@ue-a.example.com> Content-Type: application/sdp Content-Length: 256 v=0 o=user_a 2890844526 2890842807 IN IP4 ue-a.example.com s=- c=IN IP4 235.160.32.14/10 m=video 12954 RTP/AVP 33 a=rtpmap:33 dvbip-alfec-base/90000 a=bc_service:channel_1@iptv_broadcast_example a=bc_service_package:package_1@3FB7 a=recvonly b=AS:2500 10 SIP ISC BC-SCF A S-CSCF 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 70 From: User A <sip:user_a@example.com>;tag=372183 To: BC service <sip:bc_service@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:bc_service@bc-scf.example.com> Content-Type: application/sdp Content-Length: 264 v=0 o=BC service 2890844526 2890842807 IN IP4 bc_service.example.com s=- c=IN IP4 235.160.32.14/10 m=video 12954 RTP/AVP 33 a=rtpmap:33 dvbip-alfec-base/90000 a=bc_service:channel_1@iptv_broadcast_example a=bc_service_package:package_1@3FB7 a=sendonly b=AS:2500 11 SIP Mw S-CSCF P-CSCF A 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 69 From: User A <sip:user_a@example.com>;tag=372183 To: BC service <sip:bc_service@example.com> Call-ID: 398174293@phone-a.example.com ETSI ETSI TS 183 048 V2.2.1 (2009-08) 117 Step Protocol Interface From To Message CSeq: 1 INVITE Contact: <sip:bc_service@bc-scf.example.com> Content-Type: application/sdp Content-Length: 264 v=0 o=BC service 2890844526 2890842807 IN IP4 bc_service.example.com s=- c=IN IP4 235.160.32.14/10 m=video 12954 RTP/AVP 33 a=rtpmap:33 dvbip-alfec-base/90000 a=bc_service:channel_1@iptv_broadcast_example a=bc_service_package:package_1@3FB7 a=sendonly b=AS:2500 12 DIAMETER Gq' P-CSCF A SPDF A AAR <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from any to 235.160.32.14 12954" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 2500000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = VIDEO (1) ] [ Flow-Status = ENABLED DOWNLINK (1) ] [ Reservation-Priority = DEFAULT (0) ] [ Media-Authorization-Context-Id = "package_1@3FB7"] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 13 DIAMETER Rq SPDF A A-RACF A AAR <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from any to 235.160.32.14 12954" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 2500000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = VIDEO (1) ] [ Flow-Status = ENABLED DOWNLINK (1) ] [ Reservation-Priority = DEFAULT (0) ] [ Media-Authorization-Context-Id = "package_1@3FB7"] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 118 Step Protocol Interface From To Message 14 DIAMETER Re A-RACF A RCEF A PIR The A-RACF maps the value of the Authorization-Package-Id AVP to information that is locally preconfigured on the allowed IP multicast addresses and ports for the currently authorized application service. In this example, "package_1@3FB7" maps into a set of three IP multicast addresses and ports, whereof one is provided in the Rq AAR command since it is the IP multicast address that the UE intends to join first. This address and port is provided in the SDP offer according to [10]. The activation of the policy occurs however shown in this step with the arrival of the 200 OK following the example signalling flow given in clause A.4.1 of [10]. Furthermore, the A-RACF maps the value of the Media-Authorization-Context-Id AVP to source IP addresses and ports that are locally preconfigured, The ToS-Traffic-Class AVP is set to 001010, which is the codepoint allocated by IANA for the AF11 DiffServ per-hop behaviour [15]. This value is herein provided as an example only. < PI-Request > ::= < Diameter Header: 315, REQ, PXY > < Session-Id = "aracf-a.example.com;32475;112" > { Auth-Application-Id = 16777253 (Re) } { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Destination-Host = "rcef-a.example.com" } { PI-Request-Type = INITIAL_REQUEST } { PI-Request-Number = 0 } [ Auth-Session-State = NO_STATE_MAINTAINED (1) ] [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-BC-IPTV-DL" } [ Service-Identifier = 1 ] [ Rating-Group = 1 ] [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] [ Flow-Description = "permit out 17 from 192.168.0.3 14368 to 235.160.32.14 12954" ] [ Flow-Description = "permit out 17 from 192.168.0.3 14370 to 235.160.32.10 12832" ] [ Flow-Description = "permit out 17 from 192.168.0.3 14368 to 235.160.32.12 12996" ] [ Flow-Status = ENABLED-DOWNLINK (1) ] [ QoS-Information = [ Max-Requested-Bandwidth-UL = 2500000 ] [ ToS-Traffic-Class = 001010] ] [ Precedence = 1] [ Flows = { Media-Component-Number = 1 } [ Flow-Number = 1 ] ] ] ] 15 DIAMETER Re RCEF A A-RACF A PIA <PI-Answer> ::= < Diameter Header: 315, PXY > < Session-Id = "aracf-a.example.com;32475;112" > { Origin-Host = "rcef-a.example.com" } { Origin-Realm = "example.com" } { PI-Request-Type = INITIAL_REQUEST } { PI-Request-Number = 0 } [ Result-Code DIAMETER_SUCCESS (2001) ] 16 DIAMETER Rq A-RACF A SPDF A AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 119 Step Protocol Interface From To Message 17 DIAMETER Gq' SPDF A P-CSCF A AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 18 SIP Gm P-CSCF A UE A 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 68 From: User A <sip:user_a@example.com>;tag=372183 To: BC service <sip:bc_service@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:bc_service@bc-scf.example.com> Content-Type: application/sdp Content-Length: 264 v=0 o=BC service 2890844526 2890842807 IN IP4 bc_service.example.com s=- c=IN IP4 235.160.32.14/10 m=video 12954 RTP/AVP 33 a=rtpmap:33 dvbip-alfec-base/90000 a=bc_service:channel_1@iptv_broadcast_example a=bc_service_package:package_1@3FB7 a=sendonly b=AS:2500 19 SIP Gm UE A P-CSCF A ACK ACK sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 70 Route: <sip:p-cscf-a.example.com;lr>,<sip:s-cscf.example.com;lr> From: User A <sip:user_a@example.com>;tag=348123 To: BC service <sip:bc_service@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 ACK Content-Length: 0 20 SIP Mw P-CSCF A S-CSCF ACK ACK sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 69 Route: <sip:s-cscf.example.com;lr> From: User A <sip:user_a@example.com>;tag=348123 To: BC service <sip:bc_service@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 ACK Content-Length: 0 21 SIP ISC S-CSCF BC-SCF ACK ACK sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 68 From: User A <sip:user_a@example.com>;tag=348123 To: BC service <sip:bc_service@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 ACK Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 120 6.3.2 Enabling CoD service Figure 6.3.2.1 illustrates the example network architecture [10]. Figure 6.3.2.1: IMS-based IPTV -CoD service The addresses and ports used in the example are as follows: • A1 = RTSP: 192.168.0.2: 33942. • A1 = Audio: 192.168.0.2: 23942 for RTP and 192.168.0.2:23943 for RTCP. • A1 = Video: 192.168.0.2:51372 for RTP and 192.168.0.2:51373 for RTCP. • A2 = RTSP: 192.168.0.1:34444. • A2 = Audio: 192.168.0.1:4444 for RTP and 192.168.0.1:4445 for RTCP. • A2 = Video: 192.168.0.1:31444 for RTP and 192.168.0.1:31445 for RTCP. • A3 = RTSP: 10.0.0.1:32222. • A3 = Audio: 10.0.0.1:2222 for RTP and 10.0.0.1:2223 for RTCP. • A3 = Video: 10.0.0.1:17462 for RTP and 10.0.0.1:17463 for RTCP. • B1 = RTSP: 192.168.1.2:39792. • B1 = Audio: 192.168.1.2:39792 for RTP and 192.168.1.2:29793 for RTCP. • B1 = Video: 192.168.1.2:25552 for RTP and 192.168.1.2:25553 for RTCP. • B2 = RTSP: 192.168.1.1:33332. • B2 = Audio: 192.168.1.1:3332 for RTP and 192.168.1.1:3333 for RTCP. ETSI ETSI TS 183 048 V2.2.1 (2009-08) 121 • B2 = Video: 192.168.1.1:32124 for RTP and 192.168.1.1:32125 for RTCP. • B3 = RTSP: 10.0.0.2:31110. • B3 = Audio: 10.0.0.2:31110 for RTP and 10.0.0.2:1111 for RTCP. • B3 = Video: 10.0.0.2:1612 for RTP and 10.0.0.2:1613 for RTCP. • RTSP-URL of MF : media.example.com. ETSI ETSI TS 183 048 V2.2.1 (2009-08) 122 Figure 6.3.2.2: Enabling CoD service -IMS-based IPTV (based on A.3.1.1 of [10]) ETSI ETSI TS 183 048 V2.2.1 (2009-08) 123 Table 6.3.2.1: Messages for enabling CoD service -IMS-based IPTV Step Protocol Interface From To Message 1 SIP UE A P-CSCF A INVITE B INVITE sip:mf_b@example.com SIP/2.0 Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 70 Route: <sip:p-cscf-a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 INVITE Contact: <sip:user_a@ue-a.example.com> Content-Type: application/sdp Content-Length: 129 v=0 o=user_a 2890844526 2890842807 IN IP4 ue-a.example.com s=- c=IN IP4 192.168.0.2 t=0 0 m=application 9 tcp iptv_rtsp a=sendrecv a=setup:active a=connection:new 2 SIP P-CSCF A UE A 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 INVITE Content-Length: 0 3 DIAMETER Gq' P-CSCF A SPDF A AAR The value of Max-Requested-Bandwidth-DL / Max-Requested-Bandwidth-UL may be pre-configured in P-CSCF. <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-a.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 6 from any to 192.168.0.2 9" ] [ Flow-Description = "permit in 6 from any to any" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 20000 ] [ Max-Requested-Bandwidth-UL = 20000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = APPLICATION (3) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "uplink offer m=application 9 tcp iptv_rtsp" ] ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 9 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] } ETSI ETSI TS 183 048 V2.2.1 (2009-08) 124 Step Protocol Interface From To Message ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 4 H.248 Ia SPDF A C-BGF A Add terminations MEGACO/3 [spdf-a.example.com]:55555 Transaction = 1 { Context = ${ Add = ip/1/$/$ { /* NOTE 1 */ Media { Stream = 1 { LocalControl { ipdc/realm = "A", gm/rsb = ON } Local { v=0 m=- $ tcp 0 c=IN IP4 $ b=AS:20 }, Remote { v=0 o=- 0 0 IN IP4 0.0.0.0 s=- t=0 0 m=- 0 tcp 0 c=IN IP4 0.0.0.0 b=AS:20 } } /* Stream */ } /* Media */ } /* Add */ Add = ip/1/$/$ { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 m=- $ tcp 0 c=IN IP4 $ b=AS:20 } } /* Stream */ } /* Media */ } /* Add */ } /* Context */ } /* Transaction */ NOTE: The wildcard CHOOSE must be used for the interface part of the termination id. With the exception of the interface field, only the "Id" part may be wildcarded (see table 4 in [7]). 5 H.248 Ia C-BGF A SPDF A Reply (Add) MEGACO/3 [abgf-a.example.com]:55555 Reply = 1 { Context = 1 { Add = ip/1/if1/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "A", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 192.168.0.1 s=- t=0 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 125 Step Protocol Interface From To Message m=- 34444 tcp 0 c=IN IP4 192.168.0.1 b=AS:20 }, Remote { v=0 o=- 0 0 IN IP4 0.0.0.0 s=- t=0 0 m=- 0 tcp 0 c=IN IP4 0.0.0.0 b=AS:20 } } /* Stream */ } /* Media */ } /* Add */ Add = ip/1/if2/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 32222 tcp 0 c=IN IP4 10.0.0.1 b=AS:20 } } /* Stream */ } /* Media */ } /* Add */ } /* Context */ } /* Reply */ 6 DIAMETER Rq SPDF A A-RACF A AAR <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "aracf-a.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 6 from 192.168.0.1 34444 to 192.168.0.2 9" ] [ Flow-Description = "permit in 6 from any to any" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 20000 ] [ Max-Requested-Bandwidth-UL = 20000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = APPLICATION (3) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 126 Step Protocol Interface From To Message 7 DIAMETER Rq A-RACF A SPDF A AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 8 DIAMETER Gq' SPDF A P-CSCF A AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 9 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 32222 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] ] ] ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 9 SIP P-CSCF A S-CSCF INVITE B INVITE sip:mf_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 69 Record-Route: <sip:p-cscf-a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 INVITE Contact: <sip:user_a@ue-a.example.com> Content-Type: application/sdp Content-Length: 129 v=0 o=user_a 2890844526 2890842807 IN IP4 ue-a.example.com s=- c=IN IP4 10.0.0.1 t=0 0 m=application 32222 tcp iptv_rtsp a=sendrecv a=setup:active a=connection:new ETSI ETSI TS 183 048 V2.2.1 (2009-08) 127 Step Protocol Interface From To Message 10 SIP S-CSCF P-CSCF A 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 INVITE Content-Length: 0 11 SIP S-CSCF P-CSCF B INVITE B INVITE sip:mf_b@example.com SIP/2.0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 68 Record-Route: <sip:s-cscf.example.com;lr>,<sip:p-cscf-a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 INVITE Contact: <sip:user_a@ue-a.example.com> Content-Type: application/sdp Content-Length: 125 v=0 o=user_a 2890844526 2890842807 IN IP4 ue-a.example.com s=- c=IN IP4 10.0.0.1 t=0 0 m=application 32222 tcp iptv_rtsp a=sendrecv a=setup:active a=connection:new 12 SIP S-CSCF P-CSCF B 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 INVITE Content-Length: 0 13 DIAMETER Gq' P-CSCF B SPDF B AAR <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-b.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 6 from any to any" ] [ Flow-Description = "permit out 6 from any to any" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 20000 ] [ Max-Requested-Bandwidth-DL = 20000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = APPLICATION (3) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "downlink offer m=application 32222 tcp iptv_rtsp" ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 128 Step Protocol Interface From To Message ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 32222 } ] } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 14 H.248 Ia SPDF B C-BGF B Add terminations MEGACO/3 [spdf-b.example.com]:43924 Transaction = 1 { Context = $ { Add = ip/1/$/$ { Media { Stream = 1 { LocalControl { ipdc/realm = "B", gm/rsb = ON } Local { v=0 m=- $ tcp 0 c=IN IP4 $ b=AS:20 } } /* Stream */ } /* Media */ } /* Add */ Add = ip/1/$/$ { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 m=- $ tcp 0 c=IN IP4 $ b=AS:20 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 32222 tcp 0 c=IN IP4 10.0.0.1 b=AS:20 } } /* Stream */ } /* Media */ } /* Add */ } /* Context */ } /* Transaction */ ETSI ETSI TS 183 048 V2.2.1 (2009-08) 129 Step Protocol Interface From To Message 15 H.248 Ia C-BGF B SPDF B Reply (Add) MEGACO/3 [abgf-b.example.com]:43924 Reply = 1 { Context = 1 { Add = ip/1/if1/1{ Media { Stream = 1 { LocalControl { ipdc/realm = "B", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 192.168.1.1 s=- t=0 0 m=- 33332 tcp 0 c=IN IP4 192.168.1.1 b=AS:20 } } /* Stream */ } /* Media */ } /* Add */ Add = ip/1/if2/1{ Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 m=- 31110 tcp 0 c=IN IP4 10.0.0.2 b=AS:20 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 32222 tcp 0 c=IN IP4 10.0.0.1 b=AS:20 } } /* Stream */ } /* Media */ } /* Add */ } /* Context */ } /* Reply */ 16 DIAMETER Rq SPDF B A-RACF B AAR <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "aracf-b.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 6 from any to 192.168.1.1 33332" ] [ Flow-Description = "permit out 6 from any to any" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 20000 ] [ Max-Requested-Bandwidth-DL = 20000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = APPLICATION (3) ] [ Flow-Status = DISABLED ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 130 Step Protocol Interface From To Message [ Reservation-Priority = DEFAULT (0) ] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 17 DIAMETER Rq A-RACF B SPDF B AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 18 DIAMETER Gq' SPDF B P-CSCF B AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 32222 } ] } [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 33332 } ] ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 19 SIP P-CSCF B MF INVITE B INVITE sip:mf_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 67 Record-Route: <sip:p-cscf-b.example.com;lr>,<sip:s-cscf.example.com;lr>,<sip:p-cscf- a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 INVITE Contact: <sip:user_a@ue-a.example.com> Content-Type: application/sdp Content-Length: 128 v=0 o=user_a 2890844526 2890842807 IN IP4 ue-a.example.com s=- c=IN IP4 192.168.1.1 t=0 0 m=application 33332 tcp iptv_rtsp ETSI ETSI TS 183 048 V2.2.1 (2009-08) 131 Step Protocol Interface From To Message a=sendrecv a=setup:active a=connection:new 20 SIP MF P-CSCF B 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 70 From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 INVITE Contact: <sip:mf_b@mf-b.example.com> Content-Type: application/sdp Content-Length: 119 v=0 o=mf_b 29381748101 2948193018 IN IP4 mf-b.example.com s=- c=IN IP4 192.168.1.2 t=0 0 m=application 39792 tcp iptv_rtsp a=setup:passive a=connection:new 21 DIAMETER Gq' P-CSCF B SPDF B AAR (Modify) <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-b.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 6 from any to 192.168.1.2 39792" ] [ Flow-Description = "permit in 6 from any to 192.168.1.1 33332" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 20000 ] [ Max-Requested-Bandwidth-UL = 20000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = APPLICATION (3) ] [ Flow-Status = ENABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "uplink answer m=application 39792 tcp iptv_rtsp" ] [ Codec-Data = "downlink offer m=application 3333 tcp iptv_rtsp" ] ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 39792 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 32222 } ] } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.1.2 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 132 Step Protocol Interface From To Message [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 22 H.248 Ia SPDF B C-BGF B Modify terminations MEGACO/3 [spdf-b.example.com]:43924 Transaction = 2 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "B", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 192.168.1.1 s=- t=0 0 m=- 33332 tcp 0 c=IN IP4 192.168.1.1 b=AS:20 } Remote { v=0 o=- 0 0 IN IP4 192.168.1.2 s=- t=0 0 m=- 39792 tcp 0 c=IN IP4 192.168.1.2 b=AS:20 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 m=- 31110 tcp 0 c=IN IP4 10.0.0.2 b=AS:20 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 32222 tcp 0 c=IN IP4 10.0.0.1 b=AS:20 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Transaction */ 23 H.248 Ia C-BGF B SPDF B Reply (Modify) MEGACO/3 [abgf-b.example.com]: 43924 Reply = 2 { Context = 1 { Modify = ip/1/if1/1 { ETSI ETSI TS 183 048 V2.2.1 (2009-08) 133 Step Protocol Interface From To Message Media { Stream = 1 { LocalControl { ipdc/realm = "B", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 192.168.1.1 s=- t=0 0 m=- 33332 tcp 0 c=IN IP4 192.168.1.1 b=AS:20 }, Remote { v=0 o=- 0 0 IN IP4 192.168.1.2 s=- t=0 0 m=- 39792 tcp 0 c=IN IP4 192.168.1.2 b=AS:20 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 m=- 31110 tcp 0 c=IN IP4 10.0.0.2 b=AS:20 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 32222 tcp 0 c=IN IP4 10.0.0.1 b=AS:20 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Reply */ ETSI ETSI TS 183 048 V2.2.1 (2009-08) 134 Step Protocol Interface From To Message 24 DIAMETER Rq SPDF B A-RACF B AAR (Modify) <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "aracf-b.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 6 from 192.168.1.1 33332 to 192.168.1.2 39792" ] [ Flow-Description = "permit in 6 from 192.168.1.2 39792 to 192.168.1.1 33332" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 20000 ] [ Max-Requested-Bandwidth-DL = 20000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = APPLICATION (3) ] [ Flow-Status = ENABLED } [ Reservation-Priority = DEFAULT (0) ] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 25 DIAMETER Re A-RACF B RCEF B PIR < PI-Request > ::= < Diameter Header: 315, REQ, PXY > < Session-Id = "aracf-b.example.com;66389;469" > { Auth-Application-Id = 16777253 (Re) } { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Destination-Host = "rcef-b.example.com" } { PI-Request-Type = INITIAL_REQUEST } { PI-Request-Number = 0 } [ Auth-Session-State = NO_STATE_MAINTAINED (1) ] [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-B-UL" } [ Service-Identifier = 1 ] [ Rating-Group = 1 ] [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] [ Flow-Description = "permit in 6 from 192.168.1.2 39792 to 192.168.1.1 33332" ] [ Flow-Status = ENABLED-UPLINK (0) ] [ QoS-Information = [ Max-Requested-Bandwidth-UL = 20000 ] [ ToS-Traffic-Class = 1031110 ] ] [ Precedence = 1] [ Flows = { Media-Component-Number = 1 } [ Flow-Number = 1 ] [ Flow-Number = 2 ] ] ] ] [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-B-DL" } [ Service-Identifier = 1 ] [ Rating-Group = 1 ] [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] [ Flow-Description = "permit out 6 from 192.168.1.1 33332 to 192.168.1.2 39792" ] [ Flow-Status = ENABLED-DOWNLINK (1) ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 135 Step Protocol Interface From To Message [ QoS-Information = [ Max-Requested-Bandwidth-DL = 20000 ] [ ToS-Traffic-Class = 1031110 ] ] [ Precedence = 1] [ Flows = { Media-Component-Number = 1 } [ Flow-Number = 1 ] [ Flow-Number = 2 ] ] ] ] 26 DIAMETER Re RCEF B A-RACF B PIA <PI-Answer> ::= < Diameter Header: 315, PXY > < Session-Id = "aracf-b.example.com;66389;469" > { Origin-Host = "rcef-b.example.com" } { Origin-Realm = "example.com" } { PI-Request-Type = INITIAL_REQUEST } { PI-Request-Number = 0 } [ Result-Code DIAMETER_SUCCESS (2001) ] 27 DIAMETER Rq A-RACF B SPDF B AAA (Modify) <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 28 DIAMETER Gq' SPDF B P-CSCF B AAA (Modify) <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 39792 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 32222 } ] } [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 31110 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 33332 } ] ] ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 136 Step Protocol Interface From To Message 29 SIP P-CSCF B S-CSCF 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 69 From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 INVITE Contact: <sip:mf_b@mf-b.example.com> Content-Type: application/sdp Content-Length: 126 v=0 o=mf_b 29381748101 2948193018 IN IP4 mf-b.example.com s=- c=IN IP4 10.0.0.2 t=0 0 m=application 31110 tcp iptv_rtsp a=sendrecv a=setup:passive a=connection:new 30 SIP S-CSCF P-CSCF A 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 68 From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 INVITE Contact: <sip:mf_b@mf-b.example.com> Content-Type: application/sdp Content-Length: 126 v=0 o=mf_b 29381748101 2948193018 IN IP4 mf-b.example.com s=- c=IN IP4 10.0.0.2 t=0 0 m=application 31110 tcp iptv_rtsp a=sendrecv a=setup:passive a=connection:new 31 DIAMETER Gq' P-CSCF A SPDF A AAR (Modify) <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-a.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 6 from any to any" ] [ Flow-Description = "permit out 6 from any to 192.168.0.2 9" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 20000 ] [ Max-Requested-Bandwidth-DL = 20000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = APPLICATION (3) ] [ Flow-Status = ENABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "uplink offer m=application 9 tcp iptv_rtsp" ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 137 Step Protocol Interface From To Message ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 9 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 31110 } ] } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 32 H.248 Ia SPDF A C-BGF A Modify Terminations A (A to B) MEGACO/3 [spdf-a.example.com]:55555 Transaction = 2 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "A", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 192.168.0.1 s=- t=0 0 m=- 34444 tcp 0 c=IN IP4 192.168.0.1 b=AS:20 }, Remote { v=0 o=- 0 0 IN IP4 192.168.0.2 s=- t=0 0 m=- 9 tcp 0 c=IN IP4 192.168.0.2 b=AS:20 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 32222 tcp iptv_rtsp c=IN IP4 10.0.0.1 b=AS:20 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 138 Step Protocol Interface From To Message m=- 31110 tcp iptv_rtsp c=IN IP4 10.0.0.2 b=AS:20 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Transaction */ 33 H.248 Ia C-BGF A SPDF A Reply (Modify) MEGACO/3 [abgf-a.example.com]:55555 Reply = 2 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "A", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 192.168.0.1 s=- t=0 0 m=- 34444 tcp 0 c=IN IP4 192.168.0.1 b=AS:20 }, Remote { v=0 o=- 0 0 IN IP4 0.0.0.0 s=- t=0 0 m=- $ tcp 0 c=IN IP4 0.0.0.0 b=AS:20 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 32222 tcp 0 c=IN IP4 10.0.0.1 b=AS:20 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 m=- 31110 tcp 0 c=IN IP4 10.0.0.2 b=AS:20 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Reply */ ETSI ETSI TS 183 048 V2.2.1 (2009-08) 139 Step Protocol Interface From To Message 34 DIAMETER Rq SPDF A A-RACF A AAR (Modify) <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "aracf-a.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 6 from 192.168.0.1 34444 to 192.168.0.2 9" ] [ Flow-Description = "permit in 6 from 192.168.0.2 9 to 192.168.0.1 34444" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 20000 ] [ Max-Requested-Bandwidth-DL = 20000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = APPLICATION (3) ] [ Flow-Status = ENABLED ] [ Reservation-Priority = DEFAULT (0) ] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 35 DIAMETER Re A-RACF A RCEF A PIR < PI-Request > ::= < Diameter Header: 315, REQ, PXY > < Session-Id = "aracf-a.example.com;32475;112" > { Auth-Application-Id = 16777253 (Re) } { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Destination-Host = "rcef-a.example.com" } { PI-Request-Type = INITIAL_REQUEST } { PI-Request-Number = 0 } [ Auth-Session-State = NO_STATE_MAINTAINED (1) ] [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-A-UL" } [ Service-Identifier = 1 ] [ Rating-Group = 1 ] [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] [ Flow-Description = "permit in 6 from 192.168.0.2 9 to 192.168.0.1 34444" ] [ Flow-Status = ENABLED-UPLINK (0) ] [ QoS-Information = [ Max-Requested-Bandwidth-UL = 20000 ] [ ToS-Traffic-Class = 1031110 ] ] [ Precedence = 1] [ Flows = { Media-Component-Number = 1 } [ Flow-Number = 1 ] [ Flow-Number = 2 ] ] ] ] [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-A-DL" } [ Service-Identifier = 1 ] [ Rating-Group = 1 ] [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] [ Flow-Description = "permit out 6 from 192.168.0.1 34444 to 192.168.0.2 9" ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 140 Step Protocol Interface From To Message [ Flow-Status = ENABLED-DOWNLINK (1) ] [ QoS-Information = [ Max-Requested-Bandwidth-DL = 20000 ] [ ToS-Traffic-Class = 1031110 ] ] [ Precedence = 1] [ Flows = { Media-Component-Number = 1 } [ Flow-Number = 1 ] [ Flow-Number = 2 ] ] ] ] 36 DIAMETER Re RCEF A A-RACF A PIA <PI-Answer> ::= < Diameter Header: 315, PXY > < Session-Id = "aracf-a.example.com;32475;112" > { Origin-Host = "rcef-a.example.com" } { Origin-Realm = "example.com" } { PI-Request-Type = INITIAL_REQUEST } { PI-Request-Number = 0 } [ Result-Code DIAMETER_SUCCESS (2001) ] 37 DIAMETER Rq A-RACF A SPDF A AAA (Modify) <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 38 DIAMETER Gq' SPDF A P-CSCF A AAA (Modify) <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 9 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 31110 } ] } [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 32222 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.1 } { Port-Number = 34444 } ] ] ] [ Authorization-Lifetime = 450 ] { Auth-Grace-Period = 10 } ETSI ETSI TS 183 048 V2.2.1 (2009-08) 141 Step Protocol Interface From To Message 39 SIP P-CSCF A UE A 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 67 From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 INVITE Contact: <sip:mf_b@mf-b.example.com> Content-Type: application/sdp Content-Length: 129 v=0 o=mf_b 29381748101 2948193018 IN IP4 mf-b.example.com s=- c=IN IP4 192.168.0.1 t=0 0 m=application 34444 tcp iptv_rtsp a=sendrecv a=setup:passive a=connection:new 40 SIP UE A P-CSCF A ACK ACK sip:mf_b@example.com SIP/2.0 Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 70 Route: <sip:p-cscf-a.example.com;lr>,<sip:s-cscf.example.com;lr>,<sip:p-cscf-b.example.com;lr> From: User A <sip:user_a@example.com>;tag=348123 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 ACK Content-Length: 0 41 SIP P-CSCF A S-CSCF ACK ACK sip:mf_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 69 Route: <sip:s-cscf.example.com;lr>,<sip:p-cscf-b.example.com;lr> From: User A <sip:user_a@example.com>;tag=348123 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 ACK Content-Length: 0 42 SIP S-CSCF P-CSCF B ACK ACK sip:mf_b@example.com SIP/2.0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 68 Route: <sip:p-cscf-b.example.com;lr> From: User A <sip:user_a@example.com>;tag=348123 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 ACK Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 142 Step Protocol Interface From To Message 43 SIP P-CSCF B MF ACK ACK sip:mf_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060; branch=z9hG4bK74b03 Max-Forwards: 67 From: User A <sip:user_a@example.com>;tag=348123 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 ACK Content-Length: 0 44 RTSP UE A MF DESCRIBE DESCRIBE rtsp://media.example.com RTSP/1.0 Accept: application/sdp Cseq: 1 45 RTSP MF UE A 200 OK RTSP/1.0 200 OK CSeq: 1 Content-Type: application/sdp Content-Length: xxx v=0 o=- 29382748101 2948293018 IN IP4 10.0.0.2 s=- c=IN IP4 0.0.0.0 t=0 0 a=control:rtsp://media.example.com m=audio 0 RTP/AVP 0 b=AS:512 a=control:rtsp://media.example.com/audio a=rtpmap:14 MPA/90000 m=video 0 RTP/AVP 31 b=AS:4096 a=rtpmap:31 H261/90000 a=control:rtsp://media.example.com/video 46 RTSP UE A MF SETUP (audio) SETUP rtsp://media.example.com/audio RTSP/1.0 CSeq: 2 Transport: RTP/AVP/UDP;unicast;client_port=23942-23943 47 RTSP MF UE A 200 OK (SETUP (audio)) RTSP/1.0 200 OK CSeq: 2 Transport: RTP/AVP/UDP;unicast;client_port=23942-23943;server_port=39792-39793 Session: 11111111 48 RTSP UE A MF SETUP (video) SETUP rtsp://media.example.com/video RTSP/1.0 CSeq: 3 Transport: RTP/AVP/UDP;unicast;client_port=51372-51373 Session: 11111111 49 RTSP MF UE A 200 OK (SETUP (video)) RTSP/1.0 200 OK CSeq: 3 Transport: RTP/AVP/UDP;unicast;client_port=51372-51373;server_port=25552-25553 Session: 11111111 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 143 Step Protocol Interface From To Message 50 SIP UE A P-CSCF A INVITE B INVITE sip:mf_b@example.com SIP/2.0 Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 70 Route: <sip:p-cscf-a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 2 INVITE Contact: <sip:user_a@ue-a.example.com> Content-Type: application/sdp Content-Length: 129 v=0 o=user_a 2890844526 2890842807 IN IP4 ue-a.example.com s=- c=IN IP4 192.168.0.2 t=0 0 m=application 33942 tcp iptv_rtsp a=sendrecv a=setup:active a=connection:existing m=audio 23942 RTP/AVP 0 b=AS:512 a=recvonly m=video 51372 RTP/AVP 31 b=AS:4096 a=rtpmap:31 H261/90000 a=recvonly 51 SIP P-CSCF A UE A 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 2 INVITE Content-Length: 0 52 DIAMETER Gq' P-CSCF A SPDF A AAR <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-a.example.com" ] [ Media-Component-Description = { Media-Component-Number = 2 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from any to 192.168.0.2 23942" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 512000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from any to 192.168.0.2 23943" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-DL = 20000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "uplink offer m=audio 23942 RTP/AVP 0" ] ] [ Media-Component-Description = { Media-Component-Number = 3 } ETSI ETSI TS 183 048 V2.2.1 (2009-08) 144 Step Protocol Interface From To Message [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from any to 192.168.0.2 51372" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 4096000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from any to 192.168.0.2 51373" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-DL = 100000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = VIDEO (1) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "uplink offer m=video 51372 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196" ] ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 23942 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 23943 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 51372 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 51373 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 145 Step Protocol Interface From To Message 53 H.248 Ia SPDF A C-BGF A Modify terminations MEGACO/3 [spdf-a.example.com]:55555 Transaction = 3 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "A", gm/rsb = ON } Local { v=0 m=- $ RTP/AVP 0 c=IN IP4 $ b=AS:532 }, Remote { v=0 o=- 0 0 IN IP4 192.168.0.2 s=- t=0 0 m=- 23942 RTP/AVP 0 c=IN IP4 192.168.0.2 b=AS:532 } } /* Stream */ Stream = 3 { LocalControl { ipdc/realm = "A", gm/rsb = ON } Local { v=0 c=IN IP4 $ m=video $ RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 }, Remote { v=0 o=- 0 0 IN IP4 192.168.0.2 s=- t=0 0 c=IN IP4 192.168.0.2 m=video 51372 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 m=- $ RTP/AVP 0 c=IN IP4 $ b=AS:532 } } /* Stream */ Stream = 3 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 c=IN IP4 $ m=video $ RTP/AVP 31 a=rtpmap:31 H261/90000 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 146 Step Protocol Interface From To Message b=AS:4196 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Transaction */ 54 H.248 Ia C-BGF A SPDF A Reply (Modify) MEGACO/3 [abgf-a.example.com]:55555 Reply = 3 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "A", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 192.168.0.1 s=- t=0 0 m=- 4444 RTP/AVP 0 c=IN IP4 192.168.0.1 b=AS:532 }, Remote { v=0 o=- 0 0 IN IP4 192.168.0.2 s=- t=0 0 m=- 23942 RTP/AVP 0 c=IN IP4 192.168.0.2 b=AS:532 } } /* Stream */ Stream = 3 { LocalControl { ipdc/realm = "A", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 192.168.0.1 s=- t=0 0 c=IN IP4 192.168.0.1 m=video 31782 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 }, Remote { v=0 o=- 0 0 IN IP4 192.168.0.2 s=- t=0 0 c=IN IP4 192.168.0.2 m=video 51372 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 10.0.0.1 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 147 Step Protocol Interface From To Message s=- t=0 0 m=- 2222 RTP/AVP 0 c=IN IP4 10.0.0.1 b=AS:532 } } /* Stream */ Stream = 3 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 c=IN IP4 10.0.0.1 m=video 17462 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Reply */ 55 DIAMETER Rq SPDF A A-RACF A AAR <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Media-Component-Description = { Media-Component-Number = 2 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from 192.168.0.1 4444 to 192.168.0.2 23942" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 512000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from 192.168.0.1 4445 to 192.168.0.2 23943" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-DL = 20000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] ] [ Media-Component-Description = { Media-Component-Number = 3 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from 192.168.0.1 31782 to 192.168.0.2 51372" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 4096000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from 192.168.0.1 31783 to 192.168.0.2 51373" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-DL = 100000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = VIDEO (1) ] [ Flow-Status = DISABLED ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 148 Step Protocol Interface From To Message [ Reservation-Priority = DEFAULT (0) ] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 56 DIAMETER Rq A-RACF A SPDF A AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 57 DIAMETER Gq' SPDF A P-CSCF A AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 23942 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 23943 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 51372 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 51373 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2222 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2223 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } ETSI ETSI TS 183 048 V2.2.1 (2009-08) 149 Step Protocol Interface From To Message { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17462 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17463 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] ] ] ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 58 SIP P-CSCF A S-CSCF INVITE B INVITE sip:mf_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 69 Record-Route: <sip:p-cscf-a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 2 INVITE Contact: <sip:user_a@ue-a.example.com> Content-Type: application/sdp Content-Length: 129 v=0 o=user_a 2890844526 2890842807 IN IP4 ue-a.example.com s=- c=IN IP4 10.0.0.1 t=0 0 m=application 32222 tcp iptv_rtsp a=sendrecv a=setup:active a=connection:existing m=audio 2222 RTP/AVP 0 b=AS:512 a=recvonly m=video 17462 RTP/AVP 31 b=AS:4096 a=rtpmap:31 H261/90000 a=recvonly 59 SIP S-CSCF P-CSCF A 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 2 INVITE Content-Length: 0 60 SIP S-CSCF P-CSCF B INVITE B INVITE sip:mf_b@example.com SIP/2.0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 68 Record-Route: <sip:s-cscf.example.com;lr>,<sip:p-cscf-a.example.com;lr> ETSI ETSI TS 183 048 V2.2.1 (2009-08) 150 Step Protocol Interface From To Message From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 2 INVITE Contact: <sip:user_a@ue-a.example.com> Content-Type: application/sdp Content-Length: 125 v=0 o=user_a 2890844526 2890842807 IN IP4 ue-a.example.com s=- c=IN IP4 10.0.0.1 t=0 0 m=application 32222 tcp iptv_rtsp a=sendrecv a=setup:active a=connection:existing m=audio 2222 RTP/AVP 0 b=AS:512 a=recvonly m=video 17462 RTP/AVP 31 b=AS:4096 a=rtpmap:31 H261/90000 a=recvonly 61 SIP S-CSCF P-CSCF B 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 2 INVITE Content-Length: 0 62 DIAMETER Gq' P-CSCF B SPDF B AAR <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Media-Component-Description = { Media-Component-Number = 2 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 512000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-UL = 20000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "downlink offer m=audio 2222 RTP/AVP 0" ] ] [ Media-Component-Description = { Media-Component-Number = 3 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 4096000 ] ] [ Media-Sub-Component = ETSI ETSI TS 183 048 V2.2.1 (2009-08) 151 Step Protocol Interface From To Message { Flow-Number = 2 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-UL = 100000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "downlink Offer m=video 17462 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 ] ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2222 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2223 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17462 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17463 } ] } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 152 Step Protocol Interface From To Message 63 H.248 Ia SPDF B C-BGF B Modify terminations MEGACO/3 [spdf-b.example.com]:43924 Transaction = 3 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "B", gm/rsb = ON } Local { v=0 m=- $ RTP/AVP 0 c=IN IP4 $ b=AS:532 } } /* Stream */ Stream = 3 { LocalControl { ipdc/realm = "B", gm/rsb = ON } Local { v=0 c=IN IP4 $ m=video $ RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 m=- $ RTP/AVP 0 c=IN IP4 $ b=AS:532 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 2222 RTP/AVP 0 c=IN IP4 10.0.0.1 b=AS:532 } } /* Stream */ Stream = 3 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 c=IN IP4 $ m=video $ RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 c=IN IP4 10.0.0.1 m=video 17462 RTP/AVP 31 a=rtpmap:31 H261/90000 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 153 Step Protocol Interface From To Message b=AS:4196 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Transaction */ 64 H.248 Ia C-BGF B SPDF B Reply (Modify) MEGACO/3 [abgf-b.example.com]:43924 Reply = 3 { Context = 1 { Modify = ip/1/if1/1{ Media { Stream = 2 { LocalControl { ipdc/realm = "B", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 192.168.1.1 s=- t=0 0 m=- 3332 RTP/AVP c=IN IP4 192.168.1.1 0 b=AS:532 } } /* Stream */ Stream = 3 { LocalControl { ipdc/realm = "B", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 192.168.1.1 s=- t=0 0 c=IN IP4 192.168.1.1 m=video 32124 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1{ Media { Stream = 2 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 m=- 1110 RTP/AVP 0 c=IN IP4 10.0.0.2 b=AS:532 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 2222 RTP/AVP 0 c=IN IP4 10.0.0.1 b=AS:532 } } /* Stream */ Stream = 3 { LocalControl { ipdc/realm = "Core", ETSI ETSI TS 183 048 V2.2.1 (2009-08) 154 Step Protocol Interface From To Message gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 c=IN IP4 10.0.0.2 m=video 1612 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 c=IN IP4 10.0.0.1 m=video 2222 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Reply */ 65 DIAMETER Rq SPDF B A-RACF B AAR <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Media-Component-Description = { Media-Component-Number = 2 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 17 from any to 192.168.1.1 3332" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 512000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit in 17 from any to 192.168.1.1 3333" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-UL = 20000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] ] [ Media-Component-Description = { Media-Component-Number = 3 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 17 from any to 192.168.1.1 32124" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 4096000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit in 17 from any to 192.168.1.1 32125" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-UL = 100000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = VIDEO (1) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.1.2 ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 155 Step Protocol Interface From To Message [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 66 DIAMETER Rq A-RACF B SPDF B AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 67 DIAMETER Gq' SPDF B P-CSCF B AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2222 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2223 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17462 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17463 } ] } [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 3332 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 3333 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } ETSI ETSI TS 183 048 V2.2.1 (2009-08) 156 Step Protocol Interface From To Message { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 32124 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 32125 } ] ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 68 SIP P-CSCF B MF INVITE B INVITE sip:mf_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 67 Record-Route: <sip:p-cscf-b.example.com;lr>,<sip:s-cscf.example.com;lr>,<sip:p-cscf- a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 2 INVITE Contact: <sip:user_a@ue-a.example.com> Content-Type: application/sdp Content-Length: 128 v=0 o=user_a 2890844526 2890842807 IN IP4 ue-a.example.com s=- c=IN IP4 192.168.1.1 t=0 0 m=application 33332 tcp iptv_rtsp a=sendrecv a=setup:active a=connection:existing m=audio 3332 RTP/AVP 0 b=AS:512 a=sendonly m=video 32124 RTP/AVP 31 b=AS:4096 a=rtpmap:31 H261/90000 a=sendonly 69 SIP MF P-CSCF B 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 70 From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 2 INVITE Contact: <sip:mf_b@mf-b.example.com> Content-Type: application/sdp Content-Length: 119 v=0 o=mf_b 29381748101 2948193018 IN IP4 mf-b.example.com s=- c=IN IP4 192.168.1.1 t=0 0 m=application 33332 tcp iptv_rtsp a=sendrecv a=setup:passive ETSI ETSI TS 183 048 V2.2.1 (2009-08) 157 Step Protocol Interface From To Message a=connection:existing m=audio 3332 RTP/AVP 0 b=AS:512 a=sendonly m=video 32124 RTP/AVP 31 b=AS:4096 a=rtpmap:31 H261/90000 a=sendonly 70 DIAMETER Gq' P-CSCF B SPDF B AAR (Modify) <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Media-Component-Description = { Media-Component-Number = 2 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 17 from any to 192.168.1.1 3332" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 512000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit in 17 from any to 192.168.1.1 3333" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-UL = 20000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = ENABLED-UPLINK (0) ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "uplink answer m=audio 29792 RTP/AVP 0" ] [ Codec-Data = "downlink offer m=audio 3333 RTP/AVP 0" ] ] [ Media-Component-Description = { Media-Component-Number = 3 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 17 from any to 192.168.1.1 32124" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 4096000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit in 17 from any to 192.168.1.1 32124" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-UL = 100000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = VIDEO (1) ] [ Flow-Status = ENABLED-UPLINK (0) ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "uplink answer m=video 25552 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196" ] [ Codec-Data = "downlink offer m=video 32124 RTP/AVP 31 a=rtpmap:31 H261/90000 b=as:640" ] ] [ Binding-Information = { Binding-Input-List = ETSI ETSI TS 183 048 V2.2.1 (2009-08) 158 Step Protocol Interface From To Message [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 29792 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2222 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 29793 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2223 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 25552 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17462 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 25553 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17463 } ] } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 71 H.248 Ia SPDF B C-BGF B Modify terminations MEGACO/3 [spdf-b.example.com]:43924 Transaction = 4 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "B", gm/rsb = ON, mode = ReceiveOnly }, Local { v=0 o=- 0 0 IN IP4 192.168.1.1 s=- t=0 0 m=- 3332 RTP/AVP 0 c=IN IP4 192.168.1.1 b=AS:532 } Remote { v=0 o=- 0 0 IN IP4 192.168.1.2 s=- t=0 0 m=- 29792 RTP/AVP 0 c=IN IP4 192.168.1.2 b=AS:532 } } /* Stream */ Stream = 3 { LocalControl { ipdc/realm = "B", gm/rsb = ON, ETSI ETSI TS 183 048 V2.2.1 (2009-08) 159 Step Protocol Interface From To Message mode = ReceiveOnly }, Local { v=0 o=- 0 0 IN IP4 192.168.1.1 s=- t=0 0 c=IN IP4 192.168.1.1 m=video 32124 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 } Remote { v=0 o=- 0 0 IN IP4 192.168.1.2 s=- t=0 0 c=IN IP4 192.168.1.2 m=video 25552 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = ReceiveOnly }, Local { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 m=- 1110 RTP/AVP 0 c=IN IP4 10.0.0.2 b=AS:532 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 2222 RTP/AVP 0 c=IN IP4 10.0.0.1 b=AS:532 } } /* Stream */ Stream = 3 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = ReceiveOnly }, Local { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 c=IN IP4 10.0.0.2 m=video $ RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 c=IN IP4 10.0.0.1 m=video 17462 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 160 Step Protocol Interface From To Message } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Transaction */ 72 H.248 Ia C-BGF B SPDF B Reply (Modify) MEGACO/3 [abgf-b.example.com]: 43924 Reply = 4 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "B", gm/rsb = ON, mode = ReceiveOnly }, Local { v=0 o=- 0 0 IN IP4 192.168.1.1 s=- t=0 0 m=- 3332 RTP/AVP 0 c=IN IP4 192.168.1.1 b=AS:532 }, Remote { v=0 o=- 0 0 IN IP4 192.168.1.2 s=- t=0 0 m=- 29792 RTP/AVP 0 c=IN IP4 192.168.1.2 b=AS:532 } } /* Stream */ Stream = 3 { LocalControl { ipdc/realm = "B", gm/rsb = ON, mode = ReceiveOnly }, Local { v=0 o=- 0 0 IN IP4 192.168.1.1 s=- t=0 0 c=IN IP4 192.168.1.1 m=video 32124 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 }, Remote { v=0 o=- 0 0 IN IP4 192.168.1.2 s=- t=0 0 c=IN IP4 192.168.1.2 m=video 25552 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = ReceiveOnly }, Local { ETSI ETSI TS 183 048 V2.2.1 (2009-08) 161 Step Protocol Interface From To Message v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 m=- 1110 RTP/AVP 0 c=IN IP4 10.0.0.2 b=AS:532 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 2222 RTP/AVP 0 c=IN IP4 10.0.0.1 b=AS:532 } } /* Stream */ Stream = 3 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = ReceiveOnly }, Local { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 c=IN IP4 10.0.0.2 m=video 1612 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 c=IN IP4 10.0.0.1 m=video 17462 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Reply */ 73 DIAMETER Rq SPDF B A-RACF B AAR (Modify) <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Media-Component-Description = { Media-Component-Number = 2 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 17 from 192.168.1.2 29792 to 192.168.1.1 3332" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 512000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit in 17 from 192.168.1.2 29793 to 192.168.1.1 3333" ] [ Flow-Usage = RTCP(1) ] [ Max-Requested-Bandwidth-UL = 20000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = ENABLED-UPLINK (0) } ETSI ETSI TS 183 048 V2.2.1 (2009-08) 162 Step Protocol Interface From To Message [ Reservation-Priority = DEFAULT (0) ] ] [ Media-Component-Description = { Media-Component-Number = 3 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 17 from 192.168.1.2 25552 to 192.168.1.1 32124" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 4096000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit in 17 from 192.168.1.2 25553 to 192.168.1.1 32125" ] [ Flow-Usage = RTCP(1) ] [ Max-Requested-Bandwidth-DL = 100000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = VIDEO (1) ] [ Flow-Status = ENABLED-UPLINK (0) } [ Reservation-Priority = DEFAULT (0) ] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 74 DIAMETER Re A-RACF B RCEF B PIR < PI-Request > ::= < Diameter Header: 315, REQ, PXY > < Session-Id = "aracf-b.example.com;66389;469" > { Auth-Application-Id = 16777253 (Re) } { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Destination-Host = "rcef-b.example.com" } { PI-Request-Type = UPDATE_REQUEST (2) } { PI-Request-Number = 1 } [ Auth-Session-State = NO_STATE_MAINTAINED (1) ] [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-B-UL" } [ Service-Identifier = 1 ] [ Rating-Group = 1 ] [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] [ Flow-Description = "permit in 17 from 192.168.1.2 25552 to 192.168.1.1 32124" ] [ Flow-Description = "permit in 17 from 192.168.1.2 25553 to 192.168.1.1 32125" ] [ Flow-Status = ENABLED-UPLINK (0) ] [ QoS-Information = [ Max-Requested-Bandwidth-UL = 672000 ] [ ToS-Traffic-Class = 101110 ] ] [ Precedence = 1] [ Flows = { Media-Component-Number = 3 } [ Flow-Number = 1 ] [ Flow-Number = 2 ] ] ] ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 163 Step Protocol Interface From To Message 75 DIAMETER Re RCEF B A-RACF B PIA <PI-Answer> ::= < Diameter Header: 315, PXY > < Session-Id = "aracf-b.example.com;66389;469" > { Origin-Host = "rcef-b.example.com" } { Origin-Realm = "example.com" } { PI-Request-Type = UPDATE_REQUEST (2) } { PI-Request-Number = 1 } [ Result-Code DIAMETER_SUCCESS (2001) ] 76 DIAMETER Rq A-RACF B SPDF B AAA (Modify) <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 77 DIAMETER Gq' SPDF B P-CSCF B AAA (Modify) <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 29792 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2222 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 29793 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2223 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 25552 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17462 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 25553 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17463 } ] } [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1110 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 3332 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1111 } ETSI ETSI TS 183 048 V2.2.1 (2009-08) 164 Step Protocol Interface From To Message ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 3333 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1612 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 32124 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1613 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 32125 } ] ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 78 SIP P-CSCF B S-CSCF 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 69 From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 1 INVITE Contact: <sip:mf_b@mf-b.example.com> Content-Type: application/sdp Content-Length: 189 v=0 o=mf_b 29381748101 2948193018 IN IP4 mf-b.example.com s=- c=IN IP4 10.0.0.2 t=0 0 m=application 31110 tcp iptv_rtsp a=sendrecv a=setup:passive a=connection:existing m=audio 1110 RTP/AVP 0 b=AS:512 a=sendonly m=video 1612 RTP/AVP 31 b=AS:4096 a=rtpmap:31 H261/90000 a=sendonly ETSI ETSI TS 183 048 V2.2.1 (2009-08) 165 Step Protocol Interface From To Message 79 SIP S-CSCF P-CSCF A 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 68 From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 2 INVITE Contact: <sip:mf_b@mf-b.example.com> Content-Type: application/sdp Content-Length: 126 v=0 o=mf_b 29381748101 2948193018 IN IP4 mf-b.example.com s=- c=IN IP4 10.0.0.2 t=0 0 m=application 31110 tcp iptv_rtsp a=sendrecv a=setup:passive a=connection:existing m=audio 1110 RTP/AVP 0 b=AS:512 a=sendonly m=video 1612 RTP/AVP 31 b=AS:4096 a=rtpmap:31 H261/90000 a=sendonly 80 DIAMETER Gq' P-CSCF A SPDF A AAR (Modify) <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Media-Component-Description = { Media-Component-Number = 2 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from any to 192.168.0.2 23942" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 512000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from any to 192.168.0.2 23943" ] [ Flow-Usage = RTCP(1) ] [ Max-Requested-Bandwidth-DL = 20000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = ENABLED-DOWNLINK (1) ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "uplink offer m=audio 23942 RTP/AVP 0" ] ] [ Media-Component-Description = { Media-Component-Number = 3 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from any to 192.168.0.2 51372" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 4096000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from any to 192.168.0.2 51373" ] [ Flow-Usage = RTCP(1) ] [ Max-Requested-Bandwidth-DL = 100000 ] ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 166 Step Protocol Interface From To Message [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = VIDEO (1) ] [ Flow-Status = ENABLED-DOWNLINK (1) ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "uplink offer m=video 31372 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196" ] ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 23942 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1110 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 23943 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1111 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 31372 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1612 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 31373 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1613 } ] } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 81 H.248 Ia SPDF A C-BGF A Modify Terminations A (A to B) MEGACO/3 [spdf-a.example.com]:55555 Transaction = 4 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "A", gm/rsb = ON, mode = Sendonly }, Local { v=0 o=- 0 0 IN IP4 192.168.0.1 s=- t=0 0 m=- 4444 RTP/AVP 0 c=IN IP4 192.168.0.1 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 167 Step Protocol Interface From To Message b=AS:532 }, Remote { v=0 o=- 0 0 IN IP4 192.168.0.2 s=- t=0 0 m=- 23942 RTP/AVP 0 c=IN IP4 192.168.0.2 b=AS:532 } } /* Stream */ Stream = 3 { LocalControl { ipdc/realm = "A", gm/rsb = ON, mode = Sendonly }, Local { v=0 o=- 0 0 IN IP4 192.168.0.1 s=- t=0 0 c=IN IP4 192.168.0.1 m=video $ RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 }, Remote { v=0 o=- 0 0 IN IP4 192.168.0.2 s=- t=0 0 c=IN IP4 192.168.0.2 m=video 51372 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = Sendonly }, Local { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 2222 RTP/AVP 0 c=IN IP4 10.0.0.1 b=AS:532 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 m=- 1110 RTP/AVP 0 c=IN IP4 10.0.0.2 b=AS:532 } } /* Stream */ Stream = 3 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = Sendonly }, Local { v=0 o=- 0 0 IN IP4 10.0.0.1 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 168 Step Protocol Interface From To Message s=- t=0 0 c=IN IP4 10.0.0.1 m=video 17462 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 c=IN IP4 10.0.0.2 m=video 1612 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Transaction */ 82 H.248 Ia C-BGF A SPDF A Reply (Modify) MEGACO/3 [abgf-a.example.com]:55555 Reply = 4 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "A", gm/rsb = ON, mode = Sendonly }, Local { v=0 o=- 0 0 IN IP4 192.168.0.1 s=- t=0 0 m=- 4444 RTP/AVP 0 c=IN IP4 192.168.0.1 b=AS:532 }, Remote { v=0 o=- 0 0 IN IP4 192.168.0.2 s=- t=0 0 m=- 23942 RTP/AVP 0 c=IN IP4 192.168.0.2 b=AS:532 } } /* Stream */ Stream = 3 { LocalControl { ipdc/realm = "A", gm/rsb = ON, mode = Sendonly }, Local { v=0 o=- 0 0 IN IP4 192.168.0.1 s=- t=0 0 c=IN IP4 192.168.0.1 m=video 31444 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 }, Remote { v=0 o=- 0 0 IN IP4 192.168.0.2 s=- t=0 0 c=IN IP4 192.168.0.2 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 169 Step Protocol Interface From To Message m=video 51372 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 2 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = Sendonly }, Local { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 2222 RTP/AVP 0 c=IN IP4 10.0.0.1 b=AS:532 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 m=- 1110 RTP/AVP 0 c=IN IP4 10.0.0.2 b=AS:532 } } /* Stream */ Stream = 3 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = Sendonly }, Local { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 c=IN IP4 10.0.0.1 m=video 17462 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 c=IN IP4 10.0.0.2 m=video 1612 RTP/AVP 31 a=rtpmap:31 H261/90000 b=AS:4196 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Transaction */ 83 DIAMETER Rq SPDF A A-RACF A AAR (Modify) <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Media-Component-Description = { Media-Component-Number = 3 } [ Media-Sub-Component = ETSI ETSI TS 183 048 V2.2.1 (2009-08) 170 Step Protocol Interface From To Message { Flow-Number = 1 } [ Flow-Description = "permit out 17 from 192.168.0.1 31444 to 192.168.0.2 51372" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 4096000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from 192.168.0.1 31445 to 192.168.0.2 51373" ] [ Flow-Usage = RTCP(1) ] [ Max-Requested-Bandwidth-DL = 100000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = VIDEO (1) ] [ Flow-Status = ENABLED-DOWNLINK (1) ] [ Reservation-Priority = DEFAULT (0) ] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 84 DIAMETER Re A-RACF A RCEF A PIR < PI-Request > ::= < Diameter Header: 315, REQ, PXY > < Session-Id = "aracf-a.example.com;32475;112" > { Auth-Application-Id = 16777253 (Re) } { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Destination-Host = "rcef-a.example.com" } { PI-Request-Type = UPDATE_REQUEST (2) } { PI-Request-Number = 1 } [ Auth-Session-State = NO_STATE_MAINTAINED (1) ] [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-A-DL" } [ Service-Identifier = 1 ] [ Rating-Group = 1 ] [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] [ Flow-Description = "permit out 17 from 192.168.0.1 31444 to 192.168.0.2 51372" ] [ Flow-Description = "permit out 17 from 192.168.0.1 31445 to 192.168.0.2 51373" ] [ Flow-Status = ENABLED-DOWNLINK (1) ] [ QoS-Information = [ Max-Requested-Bandwidth-DL = 672000 ] [ ToS-Traffic-Class = 101110 ] ] [ Precedence = 1] [ Flows = { Media-Component-Number = 3 } [ Flow-Number = 1 ] [ Flow-Number = 2 ] ] ] ] 85 DIAMETER Re RCEF A A-RACF A PIA <PI-Answer> ::= < Diameter Header: 315, PXY > < Session-Id = "aracf-a.example.com;32475;112" > { Origin-Host = "rcef-a.example.com" } { Origin-Realm = "example.com" } { PI-Request-Type = UPDATE_REQUEST (2) } { PI-Request-Number = 1 } [ Result-Code DIAMETER_SUCCESS (2001) ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 171 Step Protocol Interface From To Message 86 DIAMETER Rq A-RACF A SPDF A AAA (Modify) <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 87 DIAMETER Gq' SPDF A P-CSCF A AAA (Modify) <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 23942 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1110 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 23943 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1111 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 51371 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1612 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.2 } { Port-Number = 51373 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1613 } ] } [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2222 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.1 } { Port-Number = 4444 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2223 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.1 } { Port-Number = 4445 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17462 } ] [ V4-Transport-Address = ETSI ETSI TS 183 048 V2.2.1 (2009-08) 172 Step Protocol Interface From To Message { Framed-IP-Address = 192.168.0.1 } { Port-Number = 31444 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 17463 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.1 } { Port-Number = 31445 } ] ] ] [ Authorization-Lifetime = 450 ] { Auth-Grace-Period = 10 } 88 SIP P-CSCF A UE A 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 67 From: User A <sip:user_a@example.com>;tag=372183 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 2 INVITE Contact: <sip:mf_b@mf-b.example.com> Content-Type: application/sdp Content-Length: 129 v=0 o=mf_b 29381748101 2948193018 IN IP4 mf-b.example.com s=- c=IN IP4 192.168.0.1 t=0 0 m=audio 34444 tcp iptv_rtsp a=sendrecv a=setup:passive a=connection:existing m=audio 4444 RTP/AVP 0 b=AS:512 a=sendonly m=video 31444 RTP/AVP 31 b=AS:4096 a=rtpmap:31 H261/90000 a=sendonly 89 SIP UE A P-CSCF A ACK ACK sip:mf_b@example.com SIP/2.0 Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 70 Route: <sip:p-cscf-a.example.com;lr>,<sip:s-cscf.example.com;lr>,<sip:p-cscf-b.example.com;lr> From: User A <sip:user_a@example.com>;tag=348123 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 2 ACK Content-Length: 0 90 SIP P-CSCF A S-CSCF ACK ACK sip:mf_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 69 Route: <sip:s-cscf.example.com;lr>,<sip:p-cscf-b.example.com;lr> From: User A <sip:user_a@example.com>;tag=348123 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 2 ACK Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 173 Step Protocol Interface From To Message 91 SIP S-CSCF P-CSCF B ACK ACK sip:mf_b@example.com SIP/2.0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 68 Route: <sip:p-cscf-b.example.com;lr> From: User A <sip:user_a@example.com>;tag=348123 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 2 ACK Content-Length: 0 92 SIP P-CSCF B MF ACK ACK sip:mf_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bKs1pp0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bKra1ar Via: SIP/2.0/UDP p-cscf-a.example.com:5060;branch=z9hG4bKvp2yml Via: SIP/2.0/UDP ue-a.example.com:5060; branch=z9hG4bK74b03 Max-Forwards: 67 From: User A <sip:user_a@example.com>;tag=348123 To: MF <sip:mf_b@example.com> Call-ID: 398174293@ue-a.example.com CSeq: 2 ACK Content-Length: 0 93 RTSP UE A MF PLAY PLAY rtsp://media.example.com RTSP/1.0 CSeq: 4 Session: 11111111 Range: npt=0- 94 RTSP MF UE A 200 OK RTSP/1.0 200 OK CSeq: 4 Session: 11111111 Range: npt=0-100 RTP-Info: url=rtsp:// media.example.com;seq=232433;rtptime=148274937
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
6.4 Traffic policy activation request -PULL mode
|
Figure 6.4.1 illustrates the example network architecture. Figure 6.4.1: Traffic policy request -PULL mode The addresses and ports used in the example are as follows: • A1 = 192.168.0.2:23942 for RTP and 192.168.0.2:23943 for RTCP. • B1 = 192.168.1.2:29792 for RTP and 192.168.1.2:29793 for RTCP. ETSI ETSI TS 183 048 V2.2.1 (2009-08) 174
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
6.4.1 Policy activation
|
Figure 6.4.1.1: Traffic policy activation request signalling chart -PULL mode Table 6.4.1.1: Traffic policy activation request messages chart -PULL mode Step Protocol Interface From To Message 1 DIAMETER Re RCEF A A-RACF A CCR <CC-Request> ::= < Diameter Header: 272, REQ, PXY > < Session-Id = "rcef-a.example.com;13815C;391" > { Origin-Host = "rcef-a.example.com" } { Origin-Realm = "example.com " } { Destination-Realm = "example.com " } { Auth-Application-Id = 16777253 (Re) } { Service-Context-Id = "service_1@drcef-a.example.com" } { CC-Request-Type = "INITIAL_REQUEST" } { CC-Request-Number = 0 } [ Logical-Access-Id = "ue_a" ] [ Flow-Description = "permit out 17 from 192.168.1.2 29792 to 192.168.0.2 23942" ] [ Flow-Description = "permit in 17 from 192.168.0.2 23942 to 192.168.1.2 29792" ] [ Flow-Description = "permit out 17 from 192.168.1.2 29793 to 192.168.0.2 23943" ] [ Flow-Description = "permit in 17 from 192.168.0.2 23943 to 192.168.1.2 29793" ] [ QoS-Information = [ Max-Requested-Bandwidth-UL = 104000 ] [ Max-Requested-Bandwidth-DL = 104000 ] ] 2 DIAMETER Re A-RACF A RCEF A CCA <CC-Answer> ::= < Diameter Header: 272, PXY > < Session-Id = "rcef-a.example.com;13815C;391" > { Origin-Host = "a-racf-a.example.com" } { Origin-Realm = "example.com " } { Auth-Application-Id = 16777253 (Re) } { Result-Code = DIAMETER_SUCCESS (2001) } { CC-Request-Type = "INITIAL_REQUEST" } { CC-Request-Number = 0 } [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-pull-UL" } [ Flow-Status = ENABLED-UPLINK (0) ] [ QoS-Information = [ ToS-Traffic-Class = 101110 ] ] [ Precedence = 1] ] ] [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-pull-DL" } [ Flow-Status = ENABLED-DOWNLINK (1) ] [ QoS-Information = [ ToS-Traffic-Class = 101110 ] ] [ Precedence = 1] ] ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 175
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
6.4.2 Policy deactivation
|
Figure 6.4.2.1: Traffic policy deactivation request signalling chart -PULL mode Table 6.4.2.1: Traffic policy deactivation request messages chart -PULL mode Step Protocol Interface From To Message 3 DIAMETER Re RCEF A A-RACF A CCR <CC-Request> ::= < Diameter Header: 272, REQ, PXY > < Session-Id = "rcef-a.example.com;13815C;391" > { Origin-Host = "rcef-a.example.com" } { Origin-Realm = "example.com " } { Destination-Realm = "example.com " } { Auth-Application-Id = 16777253 (Re) } { Service-Context-Id = "service_1@drcef-a.example.com" } { CC-Request-Type = "TERMINATION_REQUEST" } { CC-Request-Number = 1 } [ Logical-Access-Id = "ue_a" ] 4 DIAMETER Re A-RACF A RCEF A CCA <CC-Answer> ::= < Diameter Header: 272, PXY > < Session-Id = "rcef-a.example.com;13815C;391" > { Origin-Host = "a-racf-a.example.com" } { Origin-Realm = "example.com " } { Auth-Application-Id = 16777253 (Re) } { Result-Code = DIAMETER_SUCCESS (2001) } { CC-Request-Type = "TERMINATION_REQUEST" } { CC-Request-Number = 1 } [ Policy-Rule-Remove = [ Policy-Rule-Name = "policy-rule-example-pull-UL" ] [ Policy-Rule-Name = "policy-rule-example-pull-DL" ] ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 176
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
6.5 Communication Waiting
|
Core Network(s) P-CSCF C SPDF C C-BGF C A-RACF C Gq’ Rq Ia P-CSCF B SPDF B C-BGF B A-RACF B Gq’ Rq Ia RCEF C RCEF B Re Re Phone C Phone B AS (CW) C2 B1 C3 C1 B2 B3 P-CSCF A SPDF A C-BGF A A-RACF A Gq’ Rq Ia RCEF A Re Phone A A2 A3 A1 S-CSCF Figure 6.5.1: Communication Waiting Scenario network architecture The communication waiting scenario call flow uses the above network architecture. User C calls User B while User A and User B has a session in progress. An Application Server, AS(CW), inserts a communication waiting indication XML tag in the SDP sent to Phone B when the AS detects a Network Determined User Busy (NDUB) condition. Addresses and ports used in the example are as follows: • B1 = 192.168.1.2:25552 for RTP and 192.168.1.2:25553 for RTCP. • B2 = 192.168.1.1:32124 for RTP and 192.168.1.1:32125 for RTCP. • B3 = 10.0.0.2:16120 for RTP and 10.0.0.2:16121 for RTCP. • C3 = 10.0.0.3:33942 for RTP and 10.0.0.3:33943 for RTCP. NOTE: Details are omitted on the C side. Address/port combinations C2 and C1 are therefore not used/shown in this example. ETSI ETSI TS 183 048 V2.2.1 (2009-08) 177 Note: Figure 6.5.2 is simplified. Only network elements on the B side are shown in detail. Communication between Phone C and P-CSCF C is omitted. Regular procedures between P-CSCF C and RACS elements in domain C apply but are omitted for brevity. Application Server AS is a SIP proxy or B2BUA providing Communication Waiting indication functionality as described in [16], clause 4 in the event of NDUB (Network Determined User Busy) condition. Figure 6.5.2: IMS end-to-end signalling chart between two SIP end-points -communication waiting Table 6.5.1: IMS end-to-end messages between two SIP end-points -communication waiting Step Protocol Interface From To Message 48 SIP Mw P-CSCF C S-CSCF INVITE B Phone A has established a session with Phone B with active RTP data. Phone C calls Phone B. An invite is sent from Phone C and bandwidth is reserved in Phone C's access network according to the procedures described in clause 6.1.1. INVITE sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 Max-Forwards: 69 Route: <sip:p-cscf-c.example.com;lr>,<sip:phone-c.example.com;lr> From: User C <sip:user_c@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com CSeq: 1 INVITE Contact: <sip:user_c@phone-c.example.com> Content-Type: application/sdp Content-Length: (…) ETSI ETSI TS 183 048 V2.2.1 (2009-08) 178 Step Protocol Interface From To Message v=0 o=user_c 2890844526 2890842807 IN IP4 phone-c.example.com s=- c=IN IP4 10.0.0.3 t=0 0 m=audio 33942 RTP/AVP 0 a=sendrecv b=AS:96000 49 SIP Mw S-CSCF P-CSCF 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 From: User C <sip:user_c@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com CSeq: 1 INVITE Content-Length: 0 50 SIP Mw S-CSCF AS INVITE INVITE sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 Max-Forwards: 68 Route: <sip:s-cscf.example.com;lr>,<sip:p-cscf-c.example.com;lr>,<sip:phone-c.example.com;lr> From: User C <sip:user_c@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com CSeq: 1 INVITE Contact: <sip:user_c@phone-c.example.com> Content-Type: application/sdp Content-Length: (…) v=0 o=user_c 2890844526 2890842807 IN IP4 phone-c.example.com s=- c=IN IP4 10.0.0.3 t=0 0 m=audio 33942 RTP/AVP 0 a=sendrecv b=AS:96000 51 SIP Mw AS S-CSCF 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 From: User C <sip:user_c@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com CSeq: 1 INVITE Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 179 Step Protocol Interface From To Message 52 SIP Mw AS S-CSCF INVITE (CW Indication) The Application Server has determined an approaching NDUB (Network Determined User Busy) condition and inserts a Communications Waiting indication in the request before sending it to the S-CSCF. INVITE sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP as.example.com:5060;branch=z9hG4bK80c3bb6b24e50 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 Max-Forwards: 67 Route: <sip:as.example.com;lr>,<sip:s-cscf.example.com;lr>,<sip:p-cscf- c.example.com;lr>,<sip:phone-c.example.com;lr> From: User C <sip:user_c@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com CSeq: 1 INVITE Contact: <sip:user_c@phone-c.example.com> Accept: application/sdp,application/3gpp-ims+xml Content-Type: multipart/mixed;boundary="boundary1" Content-Length: (…) --boundary1 Content-Type: application/sdp v=0 o=user_c 2890844526 2890842807 IN IP4 phone-c.example.com s=- c=IN IP4 10.0.0.3 t=0 0 m=audio 33942 RTP/AVP 0 a=sendrecv b=AS:96000 --boundary1 Content-Type: application/3gpp-ims+xml Content_Disposition: 3gpp-alternative-service <3gpp-ims version="1"> <alternative-service> <type/> <reason/> <action> <call-waiting-indication/> </action> </alternative-service> </3gpp-ims> --boundary1-- 53 SIP Mw S-CSCF AS 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP as.example.com:5060;branch=z9hG4bK80c3bb6b24e50 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 From: User C <sip:user_c@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com CSeq: 1 INVITE Content-Length: 0 54 SIP Mw S-CSCF P-CSCF B INVITE (CW Indication) INVITE sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP as.example.com:5060;branch=z9hG4bK80c3bb6b24e50 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 Max-Forwards: 66 Route: <sip:s-cscf.example.com;lr>,<sip:as.example.com;lr>,<sip:s-cscf.example.com;lr>,<sip:p- cscf-c.example.com;lr>,<sip:phone-c.example.com;lr> From: User C <sip:user_c@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com CSeq: 1 INVITE Contact: <sip:user_c@phone-c.example.com> ETSI ETSI TS 183 048 V2.2.1 (2009-08) 180 Step Protocol Interface From To Message Accept: application/sdp,application/3gpp-ims+xml Content-Type: multipart/mixed;boundary="boundary1" Content-Length: (…) --boundary1 Content-Type: application/sdp v=0 o=user_c 2890844526 2890842807 IN IP4 phone-c.example.com s=- c=IN IP4 10.0.0.3 t=0 0 m=audio 33942 RTP/AVP 0 a=sendrecv b=AS:96000 --boundary1 Content-Type: application/3gpp-ims+xml Content_Disposition: 3gpp-alternative-service <3gpp-ims version="1"> <alternative-service> <type/> <reason/> <action> <call-waiting-indication/> </action> </alternative-service> </3gpp-ims> --boundary1-- 55 SIP Mw P-CSCF B S-CSCF 100 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP as.example.com:5060;branch=z9hG4bK80c3bb6b24e50 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 From: User C <sip:user_c@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com CSeq: 1 INVITE Content-Length: 0 56 Diameter Gq' P-CSCF B SPDF B AAR Triggered by the presence of the CW indication in the SIP INVITE, the P-CSCF inserts the Overbooking-Indicator AVP (AVP Code 460) set to the value OVERBOOKING_MODE_REQUIRED (1) into the AAR indicating that no extra resources are required for this session since Phone B must either release the ongoing call or put the ongoing call on hold in order to establish the session requested by Phone C. NOTE 1: Bandwidth resources on the path shared for both sessions between from User B to any of User A and User C are not booked twice due to the presence of the Overbooking-Indication AVP in the AAR below. Neither are they relinquished if User B releases the session with User A to respond to User C's invite. <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = spdf-b@example.com ] [ Media-Component-Description = { Media-Component-Number = 2 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Description = "permit out 17 from any to any" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 96000 ] [ Max-Requested-Bandwidth-DL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Description = "permit out 17 from any to any" ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 181 Step Protocol Interface From To Message [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-UL = 8000 ] [ Max-Requested-Bandwidth-DL = 8000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "downlink Offer m=audio 33942 RTP/AVP 0 ] ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.3 } { Port-Number = 33942 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.3 } { Port-Number = 33943 } ] } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] [ Overbooking-Indicator = OVERBOOKING_MODE_REQUIRED (1) ] 57 H.248 Ia SPDF B C-BGF B Add Termination MEGACO/3 [spdf-b.example.com]:43924 Transaction = 3 { Context = $ { Add = ip/1/$/$ { Media { Stream = 1 { LocalControl { ipdc/realm = "B", gm/rsb = ON } Local { v=0 c=IN IP4 $ m=audio $ RTP/AVP 0 a=rtpmap:0 PCMU/8000 } } /* Stream */ } /* Media */ } /* Add */ Add = ip/1/$/$ { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 c=IN IP4 $ m=audio $ RTP/AVP 0 a=rtpmap:0 PCMU/8000 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.3 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 182 Step Protocol Interface From To Message s=- t=0 0 c=IN IP4 10.0.0.3 m=audio 33942 RTP/AVP 0 a=rtpmap:0 PCMU/8000 } } /* Stream */ } /* Media */ } /* Add */ } /* Context */ } /* Transaction */ 58 H.248 Ia C-BGF B SPDF B Add (reply) MEGACO/3 [abgf-b.example.com]:43924 Reply = 3 { Context = 2 { Add = ip/1/if1/2{ Media { Stream = 1 { LocalControl { ipdc/realm = "B", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 192.168.1.1 s=- t=0 0 c=IN IP4 192.168.1.1 m=audio 32124 RTP/AVP 0 a=rtpmap:0 PCMU/8000 } } /* Stream */ } /* Media */ } /* Add */ Add = ip/1/if2/2{ Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 c=IN IP4 10.0.0.2 m=audio 16120 RTP/AVP 0 a=rtpmap:0 PCMU/8000 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.3 s=- t=0 0 c=IN IP4 10.0.0.3 m=audio 33942 RTP/AVP 0 a=rtpmap:0 PCMU/8000 } } /* Stream */ } /* Media */ } /* Add */ } /* Context */ } /* Reply */ 59 Diameter Rq SPDF B A-RACF B AAR <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = aracf-b@example.com ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 183 Step Protocol Interface From To Message [ Media-Component-Description = { Media-Component-Number = 2 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 17 from any to 192.168.1.1 32124" ] [ Flow-Description = "permit out 17 from any to any" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 96000 ] [ Max-Requested-Bandwidth-DL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit in 17 from any to 192.168.1.1 32125" ] [ Flow-Description = "permit out 17 from any to any" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-UL = 8000 ] [ Max-Requested-Bandwidth-DL = 8000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = AUDIO (1) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] [ Overbooking-Indicator = OVERBOOKING_MODE_REQUIRED (1) ] 60 Diameter Rq A-RACF B SPDF B AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 61 DIAMETER Gq' SPDF B P-CSCF B AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.3 } { Port-Number = 33942 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.3 } { Port-Number = 33943 } ] } [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 32124 } ETSI ETSI TS 183 048 V2.2.1 (2009-08) 184 Step Protocol Interface From To Message ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 32125 } ] ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 62 SIP Gm P-CSCF B Phone B INVITE (CW indication) Recognizing the 3GPP IMS XML Communication Waiting indication, phone B sounds an alert or presents User B with a visible indication that either a termination of the current session with User A is required or User B needs to put User A on hold in order to accept the invite from User C. NOTE 2: The action taken by User B (and corresponding signalling) is not shown here. If User B puts User A on hold, allocated resources unique for the session with User A will become inactive. If User B releases the call, allocated resources unique for the session with user A will be relinquished. INVITE sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bK74b03 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP as.example.com:5060;branch=z9hG4bK80c3bb6b24e50 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 Max-Forwards: 65 Record-Route: <sip:p-cscf-b.example.com;lr>,<sip:s- cscf.example.com;lr>,<sip:as.example.com;lr>,<sip:s-cscf.example.com;lr>,<sip:p-cscf- c.example.com;lr>,<sip:phone-c.example.com;lr> From: User C <sip:user_c@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com CSeq: 1 INVITE Contact: <sip:user_c@phone-c.example.com> Accept: application/sdp,application/3gpp-ims+xml Content-Type: multipart/mixed;boundary="boundary1" Content-Length: (…) --boundary1 Content-Type: application/sdp v=0 o=user_c 2890844526 2890842807 IN IP4 phone-c.example.com s=- c=IN IP4 192.168.1.1 t=0 0 m=audio 32124 RTP/AVP 0 a=sendrecv b=AS:96000 --boundary1 Content-Type: application/3gpp-ims+xml Content_Disposition: 3gpp-alternative-service <3gpp-ims version="1"> <alternative-service> <type/> <reason/> <action> <call-waiting-indication/> </action> </alternative-service> </3gpp-ims> --boundary1-- ETSI ETSI TS 183 048 V2.2.1 (2009-08) 185 Step Protocol Interface From To Message 63 SIP Gm Phone B P-CSCF B 180 Ringing SIP/2.0 180 Ringing Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bK74b03 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP as.example.com:5060;branch=z9hG4bK80c3bb6b24e50 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 Record-Route: <sip:p-cscf-b.example.com;lr>,<sip:s- cscf.example.com;lr>,<sip:as.example.com;lr>,<sip:s-cscf.example.com;lr>,<sip:p-cscf- c.example.com;lr>,<sip:phone-c.example.com;lr> From: User C <sip:user_c@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com Contact: <sip:user_b@phone-b.example.com> CSeq: 1 INVITE Content-Type: application/sdp Content-Length: 0 64 SIP Mw P-CSCF B S-CSCF 180 Ringing SIP/2.0 180 Ringing Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP as.example.com:5060;branch=z9hG4bK80c3bb6b24e50 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 Record-Route: <sip:s-cscf.example.com;lr>,<sip:as.example.com;lr>,<sip:s- cscf.example.com;lr>,<sip:p-cscf-c.example.com;lr>,<sip:phone-c.example.com;lr> From: User C <sip:user_c@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com Contact: <sip:user_b@phone-b.example.com> CSeq: 1 INVITE Content-Type: application/sdp Content-Length: 0 65 SIP Mw S-CSCF AS 180 Ringing SIP/2.0 180 Ringing Via: SIP/2.0/UDP as.example.com:5060;branch=z9hG4bK80c3bb6b24e50 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 Record-Route: <sip:as.example.com;lr>,<sip:s-cscf.example.com;lr>,<sip:p-cscf- c.example.com;lr>,<sip:phone-c.example.com;lr> From: User C <sip:user_c@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com Contact: <sip:user_b@phone-b.example.com> CSeq: 1 INVITE Content-Type: application/sdp Content-Length: 0 66 SIP Mw AS S-CSCF 180 Ringing (Alert-Info:) SIP/2.0 180 Ringing Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 Record-Route: <sip:s-cscf.example.com;lr>,<sip:p-cscf-c.example.com;lr>,<sip:phone- c.example.com;lr> From: User C <sip:user_c@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com Contact: <sip:user_b@phone-b.example.com> CSeq: 1 INVITE Content-Type: application/sdp Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 186 Step Protocol Interface From To Message 67 SIP Mw S-CSCF P-CSCF C 180 Ringing (Alert-Info:) NOTE 3: The last 180 Ringing from P-CSCF C to Phone C is omitted. SIP/2.0 180 Ringing Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 Record-Route: <sip:p-cscf-c.example.com;lr>,<sip:phone-c.example.com;lr> From: User C <sip:user_c@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com Contact: <sip:user_b@phone-b.example.com> CSeq: 1 INVITE Content-Type: application/sdp Content-Length: 0 68 SIP Gm Phone B P-CSCF B 200 OK (SDP) NOTE 4: User B has either released the session with User A or put User A on hold. Details are omitted for brevity. SIP/2.0 200 OK Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bK74b03 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP as.example.com:5060;branch=z9hG4bK80c3bb6b24e50 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 Record-Route: <sip:p-cscf-b.example.com;lr>,<sip:s- cscf.example.com;lr>,<sip:as.example.com;lr>,<sip:s-cscf.example.com;lr>,<sip:p-cscf- c.example.com;lr>,<sip:phone-c.example.com;lr> From: User C <sip:user_c@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com CSeq: 1 INVITE Contact: <sip:user_b@phone-b.example.com> Content-Type: application/sdp Content-Length: (…) v=0 o=user_b 29381748101 2948193018 IN IP4 phone-b.example.com s=- c=IN IP4 192.168.1.2 t=0 0 m=audio 25552 RTP/AVP 0 a=sendrecv b=AS:96000 69 DIAMETER Gq' P-CSCF B SPDF B AAR (Modify) <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = spdf-b@example.com ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from any to 192.168.1.2 25552" ] [ Flow-Description = "permit in 17 from any to 192.168.1.1 32124" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 96000 ] [ Max-Requested-Bandwidth-UL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from any to 192.168.1.2 25553" ] [ Flow-Description = "permit in 17 from any to 192.168.1.1 32123" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-DL = 8000 ] [ Max-Requested-Bandwidth-UL = 8000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = ENABLED ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 187 Step Protocol Interface From To Message [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "uplink answer m=audio 25552 RTP/AVP 0 a=rtpmap:0 PCMU/8000 ] [ Codec-Data = "downlink offer m=audio 32124 RTP/AVP 0 a=rtpmap:0 PCMU/8000 ] ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 25552 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.3 } { Port-Number = 33942 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 25553 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.3 } { Port-Number = 33943 } ] } ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 70 H.248 Ia SPDF B C-BGF B Modify terminations MEGACO/3 [spdf-b.example.com]:43924 Transaction = 4 { Context = 2 { Modify = ip/1/if1/2 { Media { Stream = 1 { LocalControl { ipdc/realm = "B", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 192.168.1.1 s=- t=0 0 c=IN IP4 192.168.1.1 m=audio 32124 RTP/AVP 0 a=rtpmap:0 PCMU/8000 } Remote { v=0 o=- 0 0 IN IP4 192.168.1.2 s=- t=0 0 c=IN IP4 192.168.1.2 m=audio 25552 RTP/AVP 0 a=rtpmap:0 PCMU/8000 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/2 { Media { Stream = 1 { LocalControl { ETSI ETSI TS 183 048 V2.2.1 (2009-08) 188 Step Protocol Interface From To Message ipdc/realm = "Core", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 c=IN IP4 10.0.0.2 m=audio $ RTP/AVP 0 a=rtpmap:0 PCMU/8000 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.3 s=- t=0 0 c=IN IP4 10.0.0.3 m=audio 33942 RTP/AVP 0 a=rtpmap:0 PCMU/8000 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Transaction */ 71 H.248 Ia C-BGF B SPDF B Reply (Modify) MEGACO/3 [abgf-b.example.com]: 43924 Reply = 4 { Context = 2 { Modify = ip/1/if1/2 { Media { Stream = 1 { LocalControl { ipdc/realm = "B", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 192.168.1.1 s=- t=0 0 c=IN IP4 192.168.1.1 m=audio 32124 RTP/AVP 0 a=rtpmap:0 PCMU/8000 }, Remote { v=0 o=- 0 0 IN IP4 192.168.1.2 s=- t=0 0 c=IN IP4 192.168.1.2 m=audio 25552 RTP/AVP 0 a=rtpmap:0 PCMU/8000 } } /* Stream */ } /* Media */ } /* Modify */ Modify = ip/1/if2/2 { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 c=IN IP4 10.0.0.2 m=audio 16120 RTP/AVP 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 189 Step Protocol Interface From To Message a=rtpmap:0 PCMU/8000 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.3 s=- t=0 0 c=IN IP4 10.0.0.3 m=audio 33942 RTP/AVP 0 a=rtpmap:0 PCMU/8000 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Reply */ 72 DIAMETER Rq SPDF B A-RACF B AAR (Modify) <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = aracf-b@example.com ] [ Media-Component-Description = { Media-Component-Number = 2 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from 192.168.1.1 32124 to 192.168.1.2 25552" ] [ Flow-Description = "permit in 17 from 192.168.1.2 25552 to 192.168.1.1 32124" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 640000 ] [ Max-Requested-Bandwidth-DL = 640000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from 192.168.1.1 32125 to 192.168.1.2 25553" ] [ Flow-Description = "permit in 17 from 192.168.1.2 25553 to 192.168.1.1 32125" ] [ Flow-Usage = RTCP(1) ] [ Max-Requested-Bandwidth-UL = 32000 ] [ Max-Requested-Bandwidth-DL = 32000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = AUDIO (1) ] [ Flow-Status = ENABLED } [ Reservation-Priority = DEFAULT (0) ] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 73 DIAMETER Re A-RACF B RCEF B PIR A policy modification request is sent to the RCEF by sending the Policy Install Request command with the PI-Request-Type AVP value set to UPDATE_REQUEST (2). The maximum requested bandwidth value in the QoS-Information AVP is set to the sum of the audio media flow bandwidth and the RTCP bandwidth (104 000 bits/second). < PI-Request > ::= < Diameter Header: 315, REQ, PXY > < Session-Id = "aracf-b.example.com;66389;469" > { Auth-Application-Id = 16777253 (Re) } { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } { Destination-Host = "rcef-b.example.com" } { PI-Request-Type = UPDATE_REQUEST (2) } { PI-Request-Number = 1 } [ Auth-Session-State = NO_STATE_MAINTAINED (1) ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 190 Step Protocol Interface From To Message [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-B-UL" } [ Service-Identifier = 1 ] [ Rating-Group = 1 ] [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] [ Flow-Description = "permit in 17 from 192.168.1.2 25552 to 192.168.1.1 32124" ] [ Flow-Description = "permit in 17 from 192.168.1.2 25553 to 192.168.1.1 32125" ] [ Flow-Status = ENABLED-UPLINK (0) ] [ QoS-Information = [ Max-Requested-Bandwidth-UL = 104000 ] [ ToS-Traffic-Class = 101110 ] ] [ Precedence = 1] [ Flows = { Media-Component-Number = 1 } [ Flow-Number = 1 ] [ Flow-Number = 2 ] ] ] ] [ Policy-Rule-Install = [ Policy-Rule-Definition = { Policy-Rule-Name = "policy-rule-example-B-DL" } [ Service-Identifier = 1 ] [ Rating-Group = 1 ] [ Framed-IP-Address = 192.168.1.2 ] [ Address-Realm = "example.com" ] [ Flow-Description = "permit out 17 from 192.168.1.1 31124 to 192.168.1.2 25552" ] [ Flow-Description = "permit out 17 from 192.168.1.1 31125 to 192.168.1.2 25553" ] [ Flow-Status = ENABLED-DOWNLINK (1) ] [ QoS-Information = [ Max-Requested-Bandwidth-DL = 104000 ] [ ToS-Traffic-Class = 101110 ] ] [ Precedence = 1] [ Flows = { Media-Component-Number = 1 } [ Flow-Number = 1 ] [ Flow-Number = 2 ] ] ] ] 74 DIAMETER Re RCEF B A-RACF B PIA <PI-Answer> ::= < Diameter Header: 315, PXY > < Session-Id = "aracf-b.example.com;66389;469" > { Origin-Host = "rcef-b.example.com" } { Origin-Realm = "example.com" } { PI-Request-Type = UPDATE_REQUEST (2) } { PI-Request-Number = 1 } [ Result-Code DIAMETER_SUCCESS (2001) ] 75 DIAMETER Rq A-RACF B SPDF B AAA (Modify) <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "spdf-b.example.com;41295;512" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "aracf-b.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 76 DIAMETER Gq' SPDF B P-CSCF B AAA (Modify) <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-b.example.com;481C43;583" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-b.example.com" } ETSI ETSI TS 183 048 V2.2.1 (2009-08) 191 Step Protocol Interface From To Message { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 25552 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.3 } { Port-Number = 33942 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.2 } { Port-Number = 25553 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.3 } { Port-Number = 33943 } ] } [ Binding-Output-List = 10.0.0.2 [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 16120 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 32124 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 16121 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.1.1 } { Port-Number = 32125 } ] ] ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] 77 SIP P-CSCF B S-CSCF 200 OK (SDP) SIP/2.0 200 OK Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP as.example.com:5060;branch=z9hG4bK80c3bb6b24e50 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 Record-Route: <sip:s-cscf.example.com;lr>,<sip:as.example.com;lr>,<sip:s- cscf.example.com;lr>,<sip:p-cscf-c.example.com;lr>,<sip:phone-c.example.com;lr> From: User C <sip:user_c@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com CSeq: 1 INVITE Contact: <sip:user_b@phone-b.example.com> Content-Type: application/sdp Content-Length: (…) v=0 o=user_b 29381748101 2948193018 IN IP4 phone-b.example.com s=- c=IN IP4 10.0.0.2 t=0 0 m=audio 16120 RTP/AVP 0 a=sendrecv b=AS:96000 78 SIP Mw S-CSCF AS 200 OK SIP/2.0 200 OK Via: SIP/2.0/UDP as.example.com:5060;branch=z9hG4bK80c3bb6b24e50 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 192 Step Protocol Interface From To Message Record-Route: <sip:as.example.com;lr>,<sip:s-cscf.example.com;lr>,<sip:p-cscf- c.example.com;lr>,<sip:phone-c.example.com;lr> From: User C <sip:user_c@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com CSeq: 1 INVITE Contact: <sip:user_b@phone-b.example.com> Content-Type: application/sdp Content-Length: (…) v=0 o=user_b 29381748101 2948193018 IN IP4 phone-b.example.com s=- c=IN IP4 10.0.0.2 t=0 0 m=audio 16120 RTP/AVP 0 a=sendrecv b=AS:96000 79 SIP Mw AS S-CSCF 200 OK SIP/2.0 200 OK Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 Record-Route: <sip:s-cscf.example.com;lr>,<sip:p-cscf-c.example.com;lr>,<sip:phone- c.example.com;lr> From: User C <sip:user_c@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com CSeq: 1 INVITE Contact: <sip:user_b@phone-b.example.com> Content-Type: application/sdp Content-Length: (…) v=0 o=user_b 29381748101 2948193018 IN IP4 phone-b.example.com s=- c=IN IP4 10.0.0.2 t=0 0 m=audio 16120 RTP/AVP 0 a=sendrecv b=AS:96000 80 SIP Mw S-CSCF P-CSCF C 200 OK NOTE 5: Details of the signalling between P-CSCF C and Phone C and associated resource reservation procedures are omitted for brevity. SIP/2.0 200 OK Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 Record-Route: <sip:p-cscf-c.example.com;lr>,<sip:phone-c.example.com;lr> From: User C <sip:user_c@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com CSeq: 1 INVITE Contact: <sip:user_b@phone-b.example.com> Content-Type: application/sdp Content-Length: (…) v=0 o=user_b 29381748101 2948193018 IN IP4 phone-b.example.com s=- c=IN IP4 10.0.0.2 t=0 0 m=audio 16120 RTP/AVP 0 a=sendrecv b=AS:96000 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 193 Step Protocol Interface From To Message 81 SIP Mw P-CSCF C S-CSCF ACK ACK sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 Max-Forwards: 69 Route: <sip:s-cscf.example.com;lr>,<sip:as.example.com;lr>,<sip:s-cscf.example.com;lr>,<sip:p- cscf-b.example.com;lr> From: User C <sip:user_c@example.com>;tag=348123 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com CSeq: 2 ACK Content-Length: 0 82 SIP Mw S-CSCF AS ACK ACK sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 Max-Forwards: 68 Route: <sip:as.example.com;lr>,<sip:s-cscf.example.com;lr>,<sip:p-cscf-b.example.com;lr> From: User C <sip:user_c@example.com>;tag=348123 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com CSeq: 2 ACK Content-Length: 0 83 SIP Mw AS S-CSCF ACK ACK sip:user_b@example.com SIP/2.09 Via: SIP/2.0/UDP as.example.com:5060;branch=z9hG4bK80c3bb6b24e50 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 Max-Forwards: 67 Route: <sip:s-cscf.example.com;lr>,<sip:p-cscf-b.example.com;lr> From: User C <sip:user_c@example.com>;tag=348123 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com CSeq: 2 ACK Content-Length: 0 84 SIP Mw S-CSCF P-CSCF B ACK ACK sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP as.example.com:5060;branch=z9hG4bK80c3bb6b24e50 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 Max-Forwards: 66 Route: <sip:p-cscf-b.example.com;lr> From: User C <sip:user_c@example.com>;tag=348123 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com CSeq: 2 ACK Content-Length: 0 85 SIP Gm P-CSCF B Phone B ACK ACK sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP p-cscf-b.example.com:5060;branch=z9hG4bK74b03 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP as.example.com:5060;branch=z9hG4bK80c3bb6b24e50 Via: SIP/2.0/UDP s-cscf.example.com:5060;branch=z9hG4bK07eeac51 Via: SIP/2.0/UDP p-cscf-c.example.com:5060;branch=z9hG4bK0691563b Via: SIP/2.0/UDP phone-c.example.com:5060;branch=z9hG4bK1594C1AB9 Max-Forwards: 65 From: User C <sip:user_c@example.com>;tag=348123 To: User B <sip:user_b@example.com> Call-ID: 88490-3838@phone-c.example.com CSeq: 2 ACK Content-Length: 0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 194
|
7e6c49a670de0a8ba391478d00f7fd4c
|
183 048
|
6.6 Media Latching/Hosted NAT traversal
|
Figure 6.6.1: Media Latching/Hosted NAT architecture Support for Hosted NAT traversal is required for the scenario where an interim NAT device is placed between the client and the Border Gateway Function (BGF) The interim NAT device (in this scenario: CNG NAT between Phone A and RCEF A in the figure above) translates the local internal IP address A1 used inside the CNG to the external address A2 residing in the same address space as the access side interface of C-BGF A with IP address A3. Phone A will use its local IP address in SDP information. C-BGF A will be instructed to latch on to the media stream sent from Phone A in order to correlate RTP flows between Phone A and Phone B. NOTE 1: It is required that the CNG NAT device performs symmetric Network Address Translation for this scenario to work. • A1 = Voice: 172.16.0.2:11212 for RTP and 172.16.0.2:11213 for RTCP. • A2 = Voice: 192.168.0.2:29412 for RTP and 192.168.0.2:29413 for RTCP. • A3 = Voice: 192.168.0.1:4444 for RTP and 192.168.0.1:4445 for RTCP. • A4 = Voice: 10.0.0.1:2222 for RTP and 10.0.0.1:2223 for RTCP. • B1 = Voice: 192.168.1.2:29792 for RTP and 192.168.1.2:29793 for RTCP. • B2 = Voice: 192.168.1.1:3332 for RTP and 192.168.1.1:3333 for RTCP. • B3 = Voice: 10.0.0.2:1110 for RTP and 10.0.0.2:1111 for RTCP. NOTE 2: Port allocation for address A2 is performed by the CNG NAT device. It may (depending on the type of device) not allocate an even port to RTP and adjacent higher port to RTCP. Any downstream device requiring such a port allocation scheme may therefore not work in this scenario. ETSI ETSI TS 183 048 V2.2.1 (2009-08) 195 Phone A P-CSCF A S-CSCF SPDF A A-RACF A C-BGF A Phone B P-CSCF B SPDF B A-RACF B C-BGF B INVITE B AAR Add Termination Reply AAR AAA AAA INVITE B INVITE B AAR Add Termination Reply AAR AAA AAA INVITE B 180 Ringing AAR Modify Termination Reply AAR AAA AAA 200 OK 200 OK AAR Modify Termination Reply AAR AAA AAA 200 OK ACK ACK ACK ACK RTP DATA RCEF A RCEF B PIR PIA PIR PIA 100 Trying 1a 2 4a 3a 5a 6a 7 8a 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35a 36a 37a 38a 39 40 41 42a 43 44 45 46 47 1a 2 4a 3a 5a 6a 7 8a 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35a 36a 37a 38a 39 40 41 42a 43 44 45 46 47 100 Trying 100 Trying 180 Ringing 180 Ringing 180 Ringing 200 OK RTP DATA RTP DATA X 48 48 49 50 49 50 Figure 6.6.2: Media Latching/CNG NAT call flow ETSI ETSI TS 183 048 V2.2.1 (2009-08) 196 Table 6.61 describes the call flow in a hosted NAT traversal scenario. NOTE 3: Only steps that differ from the signalling in clause 6.1.1 are shown below. They are represented in the table as 1a, 3a, 4a etc. Table 6.6.1: Media Latching with CNG NAT traversal Step Protocol Interface From To Message 1a SIP Gm Phone A P-CSCF A INVITE B Phone A uses its internal address to populate the SDP information. INVITE sip:user_b@example.com SIP/2.0 Via: SIP/2.0/UDP phone-a.example.com:5060;branch=z9hG4bK74b03 Max-Forwards: 70 Route: <sip:p-cscf-a.example.com;lr> From: User A <sip:user_a@example.com>;tag=372183 To: User B <sip:user_b@example.com> Call-ID: 398174293@phone-a.example.com CSeq: 1 INVITE Contact: <sip:user_a@phone-a.example.com> Content-Type: application/sdp Content-Length: 129 v=0 o=user_a 2890844526 2890842807 IN IP4 phone-a.example.com s=- c=IN IP4 172.16.0.2 t=0 0 m=audio 11212 RTP/AVP 0 a=sendrecv NOTE 1: Please refer to table 6.1.1 for details of signalling in step 2. 3a DIAMETER Gq' P-CSCF A SPDF A AAR The P-CSCF identifies that phone A resides behind NAT based on local policies, e.g. by figuring out that the source IP address used for SIP signalling differs from the IP address conveyed in the c-line of SDP. It therefore sets the Latching-Indication AVP to the value LATCH (0) in order for SPDF A to trigger the Media Latching capability in C-BGF A. NOTE 2: The source IP address A2 from the SIP INVITE message to P-CSCF A is used to populate the Globally-Unique-Address AVP in the AA-Request to SPDF A. <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-a.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from any to 172.16.0.2 11212" ] [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 96000 ] [ Max-Requested-Bandwidth-UL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from any to 172.16.0.2 11213" ] [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-DL = 8000 ] [ Max-Requested-Bandwidth-UL = 8000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "uplink offer m=audio 11212 RTP/AVP 0" ] ] [ Binding-Information = ETSI ETSI TS 183 048 V2.2.1 (2009-08) 197 Step Protocol Interface From To Message { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 172.16.0.2 } { Port-Number = 11212 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 172.16.0.2 } { Port-Number = 11213 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] } ] [ Latching-Indication = LATCH (0) ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 4a H.248 Ia SPDF A C-BGF A Add terminations The ipnapt/napt signal is set to inform C-BGF A that the true remote address of Phone A is unavailable due to Phone A being located behind a NA(P)T device incapable of performing ALG services. C-BGF A should therefore latch on to the media stream being sent from Phone A to the address allocated in the Local Descriptor (LD) on the interface in realm "A". MEGACO/3 [spdf-a.example.com]:55555 Transaction = 1 { Context = ${ Add = ip/1/$/$ { /* NOTE 1 */ Media { Stream = 1 { LocalControl { ipdc/realm = "A", gm/rsb = ON } Local { v=0 m=- $ RTP/AVP 0 c=IN IP4 $ b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 172.16.0.2 s=- t=0 0 m=- 11212 RTP/AVP 0 c=IN IP4 172.16.0.2 b=AS:104 } } /* Stream */ }, /* Media */ Signals { ipnapt/latch { napt=LATCH, stream=1 } /* ipnapt/latch */ } /* Signals */ } /* Add */ Add = ip/1/$/$ { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 198 Step Protocol Interface From To Message m=- $ RTP/AVP 0 c=IN IP4 $ b=AS:104 } } /* Stream */ } /* Media */ } /* Add */ } /* Context */ } /* Transaction */ 5a H.248 Ia C-BGF A SPDF A Reply (Add) C-BGF A will correlate the incoming media flow to 192.168.0.1:4444 with the source address of Phone A. MEGACO/3 [abgf-a.example.com]:55555 Reply = 1 { Context = 1 { Add = ip/1/if1/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "A", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 192.168.0.1 s=- t=0 0 m=- 4444 RTP/AVP 0 c=IN IP4 192.168.0.1 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 192.168.0.2 s=- t=0 0 m=- 11212 RTP/AVP 0 c=IN IP4 172.16.0.2 b=AS:104 } } /* Stream */ }, /* Media */ Signals { ipnapt/latch { napt=LATCH, stream=1 } /* ipnapt/latch */ } /* Signals */ } /* Add */ Add = ip/1/if2/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON } Local { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 2222 RTP/AVP 0 c=IN IP4 10.0.0.1 b=AS:104 } } /* Stream */ } /* Media */ } /* Add */ } /* Context */ } /* Reply */ ETSI ETSI TS 183 048 V2.2.1 (2009-08) 199 Step Protocol Interface From To Message 6a DIAMETER Rq SPDF A A-RACF A AAR <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "aracf-a.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from 192.168.0.1 4444 to 172.16.0.2 11212" ] [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-DL = 96000 ] [ Max-Requested-Bandwidth-UL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from 192.168.0.1 4445 to 172.16.0.2 11213" ] [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Usage = RTCP (1) ] [ Max-Requested-Bandwidth-DL = 8000 ] [ Max-Requested-Bandwidth-UL = 8000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = DISABLED ] [ Reservation-Priority = DEFAULT (0) ] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 NOTE 3: Refer to table 6.1.1 for signalling details of step 7. 8a DIAMETER Gq' SPDF A P-CSCF A AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 172.16.0.2 } { Port-Number = 11212 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 172.16.0.2 } { Port-Number = 11213 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2222 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } ETSI ETSI TS 183 048 V2.2.1 (2009-08) 200 Step Protocol Interface From To Message { Port-Number = 0 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2223 } ] [ V4-Transport-Address = { Framed-IP-Address = 0.0.0.0 } { Port-Number = 0 } ] ] ] ] [ Authorization-Lifetime = 450 ] [ Auth-Grace-Period = 10 ] NOTE 4: Address/port information used in the next step (see table 6.1.1, step 9 for details) is allocated by C-BGF A in step 5a. NOTE 5: Please refer to table 6.1.1 for steps 9 to 34. 35a DIAMETER Gq' P-CSCF A SPDF A AAR (Modify) <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "p-cscf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "spdf-a.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Description = "permit out 17 from any to 172.16.0.2 11212" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 96000 ] [ Max-Requested-Bandwidth-DL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit in 17 from any to any" ] [ Flow-Description = "permit out 17 from any to 172.16.0.2 11213" ] [ Flow-Usage = RTCP(1) ] [ Max-Requested-Bandwidth-UL = 8000 ] [ Max-Requested-Bandwidth-DL = 8000 ] ] [ AF-Application-Identifier = "GQPRIME_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = ENABLED ] [ Reservation-Priority = DEFAULT (0) ] [ Codec-Data = "uplink offer m=audio 11212 RTP/AVP 0" ] ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 172.16.0.2 } { Port-Number = 11212 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1110 } ] [ V4-Transport-Address = { Framed-IP-Address = 172.16.0.2 } { Port-Number = 11213 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1111 } ] } ] [ Latching-Indication = LATCH (0) ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 201 Step Protocol Interface From To Message [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] 36a H.248 Ia SPDF A C-BGF A Modify Terminations MEGACO/3 [spdf-a.example.com]:55555 Transaction = 2 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "A", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 192.168.0.1 s=- t=0 0 m=- 4444 RTP/AVP 0 c=IN IP4 192.168.0.1 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 172.16.0.2 s=- t=0 0 m=- 11212 RTP/AVP 0 c=IN IP4 172.16.0.2 b=AS:104 } } /* Stream */ }, /* Media */ Signals { ipnapt/latch { napt=LATCH, stream=1 } /* ipnapt/latch */ } /* Signals */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 2222 RTP/AVP 0 c=IN IP4 10.0.0.1 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 m=- 1110 RTP/AVP 0 c=IN IP4 10.0.0.2 b=AS:104 } } /* Stream */ } /* Media */ } /* Modify */ ETSI ETSI TS 183 048 V2.2.1 (2009-08) 202 Step Protocol Interface From To Message } /* Context */ } /* Transaction */ 37a H.248 Ia C-BGF A SPDF A Reply (Modify) MEGACO/3 [abgf-a.example.com]:55555 Reply = 2 { Context = 1 { Modify = ip/1/if1/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "A", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 192.168.0.1 s=- t=0 0 m=- 4444 RTP/AVP 0 c=IN IP4 192.168.0.1 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 172.16.0.2 s=- t=0 0 m=- 11212 RTP/AVP 0 c=IN IP4 172.16.0.2 b=AS:104 } }, /* Stream */ }, /* Media */ Signals { ipnapt/latch { napt=LATCH, stream=1 } /* ipnapt/latch */ } /* Signals */ } /* Modify */ Modify = ip/1/if2/1 { Media { Stream = 1 { LocalControl { ipdc/realm = "Core", gm/rsb = ON, mode = SendReceive }, Local { v=0 o=- 0 0 IN IP4 10.0.0.1 s=- t=0 0 m=- 2222 RTP/AVP 0 c=IN IP4 10.0.0.1 b=AS:104 }, Remote { v=0 o=- 0 0 IN IP4 10.0.0.2 s=- t=0 0 m=- 1110 RTP/AVP 0 c=IN IP4 10.0.0.2 b=AS:104 } } /* Stream */ } /* Media */ } /* Modify */ } /* Context */ } /* Reply */ ETSI ETSI TS 183 048 V2.2.1 (2009-08) 203 Step Protocol Interface From To Message 38a DIAMETER Rq SPDF-A A-RACF A AAR (Modify) <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id = "spdf-a.example.com;429C3;412" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } { Destination-Realm = "example.com" } [ Destination-Host = "aracf-a.example.com" ] [ Media-Component-Description = { Media-Component-Number = 1 } [ Media-Sub-Component = { Flow-Number = 1 } [ Flow-Description = "permit out 17 from 192.168.0.1 4444 to 172.16.0.2 11212" ] [ Flow-Description = "permit in 17 from 172.16.0.2 11212 to 192.168.0.1 4444" ] [ Flow-Usage = NO_INFORMATION(0) ] [ Max-Requested-Bandwidth-UL = 96000 ] [ Max-Requested-Bandwidth-DL = 96000 ] ] [ Media-Sub-Component = { Flow-Number = 2 } [ Flow-Description = "permit out 17 from 192.168.0.1 4445 to 172.16.0.2 11213" ] [ Flow-Description = "permit in 17 from 172.16.0.2 11213 to 192.168.0.1 4445" ] [ Flow-Usage = RTCP(1) ] [ Max-Requested-Bandwidth-UL = 8000 ] [ Max-Requested-Bandwidth-DL = 8000 ] ] [ AF-Application-Identifier = "RQ_SAMPLE_APP"] [ Media-Type = AUDIO (0) ] [ Flow-Status = ENABLED ] [ Reservation-Priority = DEFAULT (0) ] ] [ Reservation-Priority = DEFAULT (0) ] [ Globally-Unique-Address = [ Framed-IP-Address = 192.168.0.2 ] [ Address-Realm = "example.com" ] ] [ Authorization-Lifetime = 450 ] NOTE 6: Please refer to table 6.1.1 for details on steps 39 to 41. 42a DIAMETER Gq' SPDF A P-CSCF A AAA <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id = "p-cscf-a.example.com;13815C;391" > { Auth-Application-Id = 16777222 (Gq) } { Origin-Host = "spdf-a.example.com" } { Origin-Realm = "example.com" } [ Result-Code = DIAMETER_SUCCESS (2001) ] [ Binding-Information = { Binding-Input-List = [ V4-Transport-Address = { Framed-IP-Address = 172.16.0.2 } { Port-Number = 11212 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1110 } ] [ V4-Transport-Address = { Framed-IP-Address = 172.16.0.2 } { Port-Number = 11213 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.2 } { Port-Number = 1111 } ] } [ Binding-Output-List = [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2222 } ] ETSI ETSI TS 183 048 V2.2.1 (2009-08) 204 Step Protocol Interface From To Message [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.1 } { Port-Number = 4444 } ] [ V4-Transport-Address = { Framed-IP-Address = 10.0.0.1 } { Port-Number = 2223 } ] [ V4-Transport-Address = { Framed-IP-Address = 192.168.0.1 } { Port-Number = 4445 } ] ] ] [ Authorization-Lifetime = 450 ] { Auth-Grace-Period = 10 } NOTE 7: Please refer to table 6.1.1 for details of steps 43 to 47. 48 RTP Phone B C-BGF A Media Flow RTP media flows from Phone B (through C-BGF B) to C-BGF A but since C-BGF A is still awaiting media from Phone A, the latching procedure is incomplete and the media flow is dropped at C-BGF A. 49 RTP Phone A C-BGF A Media Flow Phone A starts sending media through its CNG NAT device to address 192.168.0.1:4444. C-BGF A latches on to the media flow and associates the source address from the CNG NAT device with the media flow destined for Phone B. The latching procedure is now complete and bidirectional media can flow through C-BGF A. 50 RTP Phone A Phone B Media Flow Bidirectional media flows from Phone A to Phone B through C-BGF A and C-BGF B. ETSI ETSI TS 183 048 V2.2.1 (2009-08) 205 Annex A (informative): Bibliography • IETF RFC 2865: "Remote Authentication Dial In User Service (RADIUS)". ETSI ETSI TS 183 048 V2.2.1 (2009-08) 206 Annex B (informative): Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 23/01/09 19tTD270 001 - F New version of the RACS signalling version 2. It is based on TS 183 048 v1.4.0. 1.4.0 2.0.1 19tTD271 - Output draft from TISPAN19ter 2.0.1 2.0.2 27/02/09 20WTD156 002 1 D Input draft to TISPAN20wg 2.0.2 2.0.3 27/02/09 20WTD059 009 3 F Update of clause 4 2.0.1 2.0.4 27/02/09 20WTD061 003 2 B Update of clause 6 with Re commands 2.0.1 2.0.4 27/02/09 20WTD063 004 2 F Revision of clause 6 H.248/Ia signalling to H.248/Ia v.2 2.0.1 2.0.4 27/02/09 20WTD080 005 1 B Update of clause 1 (scope) 2.0.1 2.0.4 27/02/09 20WTD098 008 1 F Update of clause 6, Rq commands 2.0.1 2.0.4 27/02/09 20WTD157 006 1 C Update of clause 5 2.0.1 2.0.4 27/02/09 20WTD225 007 1 F Initial example of signalling with BGF transcoding. 2.0.1 2.0.4 28/02/09 20WTD295 Output draft from TISPAN20WGs 2.0.3 2.0.4 18/03/09 20bTD146 010 1 B Diameter request routing and Diameter-Host AVP Usage 2.0.4 2.1.1 18/03/09 20bTD023 011 2 F Update of signalling diagrams in clause 6 2.0.4 2.1.1 18/03/09 20bTD029 012 1 B Failure in RCEF at session setup, clause 6 2.0.4 2.1.1 18/03/09 20bTD036 013 1 B Session Update Procedures, clause 6 2.0.4 2.1.1 18/03/09 20bTD101 014 1 B Usage of Authorization-Package AVP, clause 6 2.0.4 2.1.1 18/03/09 20bTD114 015 1 B Re PULL, clause 6 2.0.4 2.1.1 18/03/09 20bTD144 016 1 F Addition of procedure of Session Modification 2.0.4 2.1.1 18/03/09 20bTD258 017 3 B Overbooking-Indication AVP and Communication Waiting 2.0.4 2.1.1 18/03/09 20bTD268 018 1 B Admission denial, clause 6 2.0.4 2.1.1 18/03/09 20bTD058 019 2 F Remove Destination-Realm and Auth- Application-Id AVPs 2.0.4 2.1.1 18/03/09 20bTD057 020 2 F Add Termination Cause to Gq'/Rq STR 2.0.4 2.1.1 18/03/09 20bTD053 021 2 F Add Destination Host to Gq' AAR 2.0.4 2.1.1 18/03/09 20bTD054 022 2 F Add Destination Host to Gq'/Rq STR 2.0.4 2.1.1 18/03/09 20bTD055 023 2 F Add Destination Host to the Rq AAR messages 2.0.4 2.1.1 19/03/09 20bTD285 Output draft from TISPAN20WGs 2.0.4 2.1.1 29/05/09 WG3-05-001 024 2 B Re call-back upon RCEF failure, and session teardown 2.1.1 2.1.2 29/05/09 WG3-05-002 025 1 B x-RACF procedures 2.1.1 2.1.2 29/05/09 WG3-05-003 026 1 B List of AVPs for Gq' to Rq mapping 2.1.1 2.1.2 29/05/09 WG3-05-004 027 1 B H248 signalling update 2.1.1 2.1.2 29/05/09 WG3-05-005 028 1 B BGF Media Transcoding 2.1.1 2.1.2 29/05/09 WG3-05-006 029 3 B BGF Transport Plane Failure 2.1.1 2.1.2 29/05/09 WG3-05-008 032 1 F Session update, P-CSCF keeping state on established flows 2.1.1 2.1.2 29/05/09 WG3-05-009 033 1 F Clarification of ordering of elements in binding lists 2.1.1 2.1.2 29/05/09 WG3-05-010 034 1 F Correction of message flow for establishing BC service 2.1.1 2.1.2 29/05/09 WG3-05-011 035 3 B Hosted NAT traversal/Media Latching 2.1.1 2.1.2 29/05/09 WG3-05-012 036 1 B Update of clause 6.5 2.1.1 2.1.2 29/05/09 WG3-05-013 037 1 F Adding Destination-Host to messages missing this AVP 2.1.1 2.1.2 29/05/09 WG3-05-014 038 1 F Correction of change history 2.1.1 2.1.2 29/05/09 WG3-05-015 030 3 F Addition of procedure of IMS-based CoD service 2.1.1 2.1.2 29/05/09 WG3-05-016 031 1 F Clarification of SIP URI for session modification 2.1.1 2.1.2 29/05/09 21WTD042 Input draft to TISPAN21WGs 2.1.1 2.1.2 08/06/09 21WTD159 039 2 B Clarification of SPDF state 2.1.2 2.1.3 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 207 Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 08/06/09 21WTD160 040 1 F Update of scope, adding that non-IMS is supported 2.1.2 2.1.3 08/06/09 21WTD161 041 1 F Correction of CoD flow 2.1.2 2.1.3 08/06/09 21WTD202 042 1 F Removal of incomplete message flow for session modification 2.1.2 2.1.3 08/06/09 21WTD206 043 1 D Editorial corrections 2.1.2 2.1.3 09/06/09 21WTD242 044 3 F Removal of media transcoding examples 2.1.2 2.1.3 09/06/09 21WTD261 Output draft from TISPAN21WGs 2.1.2 2.1.3 Publication 2.1.3 2.2.1 ETSI ETSI TS 183 048 V2.2.1 (2009-08) 208 History Document history V1.4.0 June 2008 Publication V2.2.1 August 2009 Publication
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
1 Scope
|
The present document describes the signalling behaviour of the transport functions BTF & RCEF for the listed multicast and unicast transport control protocols (IGMP, MLD, RSVP) and Diameter Re and provides a mapping between these multicast and unicast transport control protocols and the TISPAN RACS Re interface.
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
2 References
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
2.1 Normative references
|
The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] IETF RFC 2205: "Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification". [2] ETSI TS 183 060: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Subsystem (RACS); Re interface based on the DIAMETER protocol". [3] IETF RFC 3181: "Signaled Preemption Priority Policy Element". [4] IETF RFC 3182: "Identity Representation for RSVP". [5] IETF draft-ietf-tsvwg-rsvp-proxy-proto: "RSVP Extensions for Path-Triggered RSVP Receiver Proxy". [6] IETF RFC 3376: "Internet Group Management Protocol, Version 3". [7] IETF RFC 2236: "Internet Group Management Protocol, Version 2". [8] IETF RFC 3810: "Multicast Listener Discovery Version 2 (MLDv2) for IPv6".
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
2.2 Informative references
|
The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. ETSI ETSI TS 183 067 V3.1.1 (2009-11) 6
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
3 Definitions and abbreviations
| |
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
3.1 Definitions
|
For the purposes of the present document, the following terms and definitions apply: termination point: element acting as the neighbouring multicast router receiving and handling IGMP/MLD request from the UE
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: AF Application Function A-RACF Access-Resource and Admission Control Function BTF Basic Transport Functions CAC Connection Admission Control CCA Credit-Control-Answer CCR Credit-Control-Request CPN Customer Premises Network IGMP Internet Group Management Protocol IPTV Internet Protocol Television MLD Multicast Listener Discovery QoS Quality of Service RACS Resource and Admission Control Subsystem RCEF Resource Control Enforcement Function RSVP Resource ReSerVation Protocol UE User Equipment
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
4 Overview
|
4.1 Overview of multicast transport control protocol to Re mapping PULL mode for multicast applies in two cases: • PULL mode case 1: when it applies below the termination point in the access segment, the PULL mode is used to request resources for a channel in the access network and/or to indicate that the resources associated to a channel can be released as the channel is left. This is per user and can be combined with the PUSH mode at session initiation to allow the A-RACF to download the permitted multicast flow for that user to the RCEF. • PULL mode case 2: when it applies beyond the termination point, the PULL mode is used to request shared resources to transport a multicast flow corresponding to a channel that has been requested by one or more users. The following figure shows a generic scenario for both cases of PULL mode. Transport processing nodes comprises one or several BTFs and one or several RCEFs that may be colocalised. ETSI ETSI TS 183 067 V3.1.1 (2009-11) 7 Figure 4.1: A generic scenario for both cases of PULL mode 1) Upon session activation, the RACS downloads the policy rules in the RCEF in charge of enforcing policies applicable to the access segment. This corresponds e.g. to the list of subscribed channels in case of IPTV service activation. For each policy, bandwidth is set to zero, this will force the transport processing node to trigger the PULL mode. 2) The BTF receives a multicast request. This message may contain IGMP/MLD "leave" and/or "join" requests. 3) The BTF requests CAC towards the RCEF. The RCEF checks that the requested channel corresponds to an existing policy-rule. If not, it ignores the request and the user will not receive the channel. If a policy-rule exists, and if PULL mode applies below the termination point, the RCEF sends a CC-Request to the RACS based on parameters received in the multicast request. It has therefore to indicate to the RACS that the UE wants to leave a particular channel and/or wants to join another one. If enough resource is available to join the requested channel, the RACS answers positively to the RCEF. 4) If the step 3 is successful, the BTF forwards the request to the RCEF dealing with resource beyond the termination point. If PULL mode applies beyond the termination point, the RCEF sends a CC-Request to the RACS based on parameters received in the multicast request. It does not have to check any policy-rule previously downloaded because this request is not linked to any user's rights. The RACS can determine if enough resource is available in the aggregation segment. If this is the case, the RACS answers positively to the RCEF. 4.2 Overview of unicast transport control protocol to Re mapping The mapping between unicast transport control protocol and Re may be invoked in the Push Mode or the Pull Mode. An overview is provided below for both cases. The mapping is defined with RSVP ([1]) as the unicast transport control protocol.
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
4.2.1 Push Mode
|
Figure 4.2 illustrates the RSVP to Re mapping in Push Mode with on-path QoS reservation in the case of a successful reservation establishment. ETSI ETSI TS 183 067 V3.1.1 (2009-11) 8 Figure 4.2: RSVP to Re mapping in Push Mode with on-path QoS reservation 1) As a result of a request from the AF for admission and resource reservation, the RACS sends a Policy-Install-Request to the RCEF in order to install a policy rule into the Transport Processing Nodes. 2) In the Push mode with on-path QoS signaling, the RCEF communicates the request to the BTF that issues an RSVP Path message to initiate path-coupled QoS signaling in order to establish the necessary reservation in the Transport Processing Nodes. 3) On receipt of an RSVP Resv message, the BTF communicates the reservation establishment to the RCEF. 4) The RCEF sends a Policy-Install-Answer to the RACS to confirm policy rule installation in the Transport Processing Nodes.
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
4.2.2 Pull Mode
|
Figure 4.3 illustrates the RSVP to Re mapping in Pull Mode in the case of a successful reservation establishment. Figure 4.3: RSVP to Re mapping in Pull Mode ETSI ETSI TS 183 067 V3.1.1 (2009-11) 9 1) The BTF receives an RSVP Path message corresponding to a path-coupled QoS reservation initiation request from a Transport Node (e.g. a CPN Device). The BTF communicates the request to the RCEF. 2) The RCEF sends a CCR request to the RACS to request authorization of the reservation initiation request based on parameters mapped from the RSVP Path message. 3) The RCEF responds to the RCEF with a CCA to confirm that the reservation initiation request is authorized. The RCEF confirms the authorization decision to the BTF. 4) The BTF forwards the RSVP Path message towards the reservation destination. 5) The BTF receives an RSVP Resv message requesting reservation establishment. After successful RSVP reservation establishment, the BTF communicates the resource reservation establishment to the RCEF. 6) The RCEF sends a CCR request to the RACS to request resource reservation based on parameters mapped from the RSVP Resv message. 7) The RACS responds to the RCEF with a CCA to confirm the reservation establishment. The RCEF communicates the establishment decision to the BTF. 8) The BTF forwards the RSVP Resv message towards the reservation source.
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
5 Behaviours of the transport functions for multicast
| |
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
5.1 PULL mode: case 1
|
On reception of an IGMPv3/MLDv2 request, the BTF communicates the request to the RCEF. If the type is set to 0x22 "v3 Membership Report" in case of IGMPv3 or to 143 "Version 2 Multicast Listener Report" in case of MLDv2, the RCEF shall take the following actions for each Group/multicast Records present in the request: • If Record Type indicates ALLOW_NEW_SOURCE with INCLUDE filter mode or CHANGE_TO_EXCLUDE_MODE with no "Source address" fields, the RCEF shall check for each multicast address/source address pair if it corresponds to an existing policy rule. If not, the RCEF shall ignore the request for that pair. If this is the case, the RCEF shall consider that the UE wants to join the corresponding multicast flow and shall send a CC-Request applying the mapping defined in clause 6.1 for IGMPv3/MLDv2. • If Record Type indicates BLOCK_OLD_SOURCE or CHANGE_TO_INCLUDE_MODE with an empty source list, the RCEF shall consider that the UE wants to leave the corresponding multicast flow and shall send a CC-Request applying the mapping defined in clause 6.1 for IGMPv3/MLDv2. On reception of an IGMPv2 request, the BTF communicates the request to the RCEF. If the type is set to 0x16 "v2 Membership Report", the RCEF shall consider that the UE wants to join the corresponding multicast flow and shall take the following actions: • If the multicast address indicated in the Group Address parameter corresponds to an existing policy rule, the RCEF shall consider that the UE wants to join the corresponding multicast flow and shall send a CC-Request applying the mapping defined in clause 6.1 for IGMPv2. • If not, the RCEF shall ignore the request for that pair. If the type is set to 0x17 "Leave Group", the RCEF shall consider that the UE wants to leave the corresponding multicast flow and shall send a CCR request applying the mapping defined in clause 6.1 for IGMPv2. On receipt of a CC-Answer, the RCEF shall behave as defined in TS 183 060 [2]. For each Policy-Rule-Install AVP that corresponds to a previously reported Policy-Update-Request in the CCR, the RCEF shall update the Max-Requested-Bandwidth-DL for the corresponding policy based on the value received from the A-RACF. If the value is set to zero, the BTF shall not forward the corresponding multicast flow. ETSI ETSI TS 183 067 V3.1.1 (2009-11) 10
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
5.2 PULL mode: case 2
|
On reception of an IGMPv3/MLDv2 request, the BTF communicates the request to the RCEF. If the type is set to 0x22 "v3 Membership Report" in case of IGMPv3 or to 143 "Version 2 Multicast Listener Report" in case of MLDv2, the RCEF shall take the following actions for each Group/multicast Records present in the request: • If Record Type indicates ALLOW_NEW_SOURCE with INCLUDE filter mode or CHANGE_TO_EXCLUDE_MODE with no "Source address" fields, the RCEF shall check for each multicast address/source address pair if the corresponding multicast flow is already received. If it is the case, the RCEF shall ignore the request for that pair. If not, the RCEF shall send a CC-Request applying the mapping defined in clause 6.2 for IGMPv3/MLDv2. • If Record Type indicates BLOCK_OLD_SOURCE or CHANGE_TO_INCLUDE_MODE with an empty source list, the RCEF shall check if other UE are still requesting the corresponding multicast flow. If not, the RCEF may send a CC-Request applying the mapping defined in clause 6.2 for IGMPv3/MLDv2. NOTE: The way the transport functions know that a channel is not required by any other UEs is based on Membership Query mechanisms as defined in RFC 3376 [6] (IGMPv3) and RFC 2236 [7] (IGMPv2) and based on Membership Listener query mechanisms as defined in RFC 3810 [8] (MLDv2). On reception of an IGMPv2 request, BTF communicates the request to the RCEF. If the type is set to 0x16 "v2 Membership Report", the RCEF shall check if the requested multicast address indicated in the Group Address parameter is already received. If it is the case, the RCEF shall ignore the request. If not, the RCEF shall send a CC-Request applying the mapping defined in clause 6.2 for IGMPv2. If the type is set to 0x17 "Leave Group", the RCEF shall consider that the UE wants to leave the corresponding multicast flow and shall check if other UEs are still requesting the corresponding multicast flow. If not, the RCEF may send a CC-Request applying the mapping defined in clause 6.2 for IGMPv2. On receipt of a CC-Answer, the RCEF shall behave as defined in TS 183 060 [2]. For each Policy-Rule-Install AVP that corresponds to a previously reported Flow-Description, the RCEF shall create the corresponding policy. The transport function shall forward the corresponding multicast flow applying QoS parameters defined in the Policy-Rule-Install AVP. For any previously reported Flow-Description that does not receive any corresponding Policy-Rule-Install AVP, the BTF shall not forward the corresponding multicast flow.
|
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
6 Multicast to Re parameters mapping
| |
ca21a3998d34549327b3d05d69fb17e5
|
183 067
|
6.1 PULL mode: case 1
|
When the RCEF sends a CCR for PULL mode case 1, it shall use the mapping defined in table 6.1 for IGMPv3/MLDv2 request. Table 6.1: Rules for derivation of CCR AVPs from IGMPv3/MLDv2 requests for PULL mode case 1 CCR AVPs Derivation from IGMPv3/MLDv2 Parameters CC-Request-Type It shall be set to UPDATE_REQUEST. Event-Trigger It shall be set to RESOURCES_MODIFICATION. Policy-Update-Request For each multicast/source address: • Policy-rule-Name shall be set to the corresponding policy rule name for that pair. • Policy_rule_status shall be set to ACTIVE. • if Record Type indicates ALLOW_NEW_SOURCE with INCLUDE filter mode or CHANGE_TO_EXCLUDE_MODE with no "Source address" fields: o Max-Requested-Bandwidth-UL shall be set to zero. o Max-Requested-Bandwidth-DL shall be set to FFFFFFFF. • if Record Type indicates BLOCK_OLD_SOURCE or CHANGE_TO_INCLUDE_MODE with an empty source list: o Max-Requested-Bandwidth-UL shall be set to zero. o Max-Requested-Bandwidth-DL shall be set to zero. ETSI ETSI TS 183 067 V3.1.1 (2009-11) 11 When the RCEF sends a CCR for PULL mode case 1, it shall use the mapping defined in table 6.2 for IGMPv2 request. Table 6.2: Rules for derivation of CCR AVPs from IGMPv2 requests for PULL mode case 1 CCR AVPs Derivation from IGMPv2 Parameters CC-Request-Type It shall be set to UPDATE_REQUEST. Event-Trigger It shall be set to RESOURCES_MODIFICATION. Policy-Update-Request • Policy-rule-Name shall be set to the corresponding policy rule name for that group address indicated in the request. • Policy_rule_status shall be set to ACTIVE. • If the type is set to 0x16 "v2 Membership Report": o Max-Requested-Bandwidth-UL shall be set to zero. o Max-Requested-Bandwidth-DL shall be set to FFFFFFFF. • If the type is set to 0x17 "Leave Group": o Max-Requested-Bandwidth-UL shall be set to zero. o Max-Requested-Bandwidth-DL shall be set to zero.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.