hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
ce0695ed7aa1e9a5cdc0ce2d8895c007 | 185 001 | 10.1 Scenario 1 - Proxied QoS with policy-push | In the "Proxied QoS with policy-push" scenario, the user terminal or home gateway does not itself support native QoS signalling mechanisms. It requests an application-specific service by sending a "Service Request" to the Service controller. It is then the Service controller's responsibility to determine the QoS needs ... |
ce0695ed7aa1e9a5cdc0ce2d8895c007 | 185 001 | 10.2 Scenario 2 - User-requested QoS with policy-push-pull | In scenario 2, "User-requested QoS with policy-push-pull", the user terminal or home gateways is capable of signalling and managing its own QoS resources but requires prior authorization of these requests via the Service controller. It requests an application-specific service by sending a "Service Request" to the Servi... |
ce0695ed7aa1e9a5cdc0ce2d8895c007 | 185 001 | 10.3 Scenario 3 - User-requested QoS with policy-pull | The user's terminal or Home gateway is capable of sending QoS Request over signalling and management protocols for its own QoS needs, and does not require prior authorization. The user's terminal or Home gateway is capable of sending QoS Request over Layer 3 QoS signalling for its own QoS needs. Authorization for the Q... |
ce0695ed7aa1e9a5cdc0ce2d8895c007 | 185 001 | 11 QoS Architecture Requirements | |
ce0695ed7aa1e9a5cdc0ce2d8895c007 | 185 001 | 11.1 Architectural requirements | The NGN QoS architecture should be able to manage different types of access network (xDSL, 3GPP access network, etc.) and different types of core networks, which could be in the same administrative domain or in different administrative domains. The NGN QoS Architecture should support the following requirements: 1) Supp... |
ce0695ed7aa1e9a5cdc0ce2d8895c007 | 185 001 | 11.2 QoS architecture | The QoS architecture describes in figure 7 support the previous requirements. SPDF NCRP NGN Service stratum NGN Transport stratum Application Functions CCRP Other domains Core RACF 2 Core RACF 1 Access RACF n Access RACF 1 SCRP SCRP SCRP SCRP NCRP CPE Access Transport Functions Core Transport Functions Figure 7: QoS ar... |
ce0695ed7aa1e9a5cdc0ce2d8895c007 | 185 001 | 12 QoS Signalling Requirements | 12.1 QoS Signalling Requirements in Call/Connection Control Reference Point The QoS signalling between the Service stratum and the RACS of Transport stratum on Call/Connection Control Reference Point should accomplish the following functions: • Request for resources: - Service stratum initiates a QoS request to the RAC... |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 1 Scope | The purpose of the present document is to provide the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma for Network Integration Testing (NIT) to verify the overall compatibility of SIP networks based on Session Initiation Protocol (SIP) and Session Description ... |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI ES 283 003 (V2.6.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Descr... |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TS 124 504 (V8.5.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; TISPAN; PSTN... |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 3 Definitions and abbreviations | |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-7 [4] and the following apply: abstract test case: Refer to ISO/IEC 9646-1 [3]. Abstract Test Method (ATM): Refer to ISO/IEC 9646-1 [3]. Abstract Test Suite (ATS): Refer to ISO/IEC 9646-1 [3]. Implementation Under Test (IUT): Refe... |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 [3], ISO/IEC 9646-7 [4] and the following apply: AS Application Server ATM Abstract Test Method ATS Abstract Test Suite CSCF Call Session Control Function EDS Encoding/Decoding System ETS Executable Test Suite IBCF Interconnection Borde... |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 4 Abstract Test Method (ATM) | This clause describes the ATM used to test TS 186 001-3 [9]. |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 4.1 Network architecture | The SUT is assumed as a complete IMS core network and contains the following components: P-CSCF, I/S-CSCF and possibly IBCF. Figure 1: SUT test interface |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 4.2 Protocol architecture | The Implementation Under Test (IUT) for which this test case specification applies consists of the IMS Supplementary Services, the underlying SIP Core Network and the SIP protocol (see figure 2). UE1 SUT (IMS) Gm UEx UE2 Gm UEy SIP protocol SIP protocol ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 9 IMS Supplementary Servic... |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 4.3 Test architecture | |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 4.3.1 Test configuration | The target SUT to be covered by the test purposes of TS 186 001-3 [9] addresses the IMS functional entities that are accessible via the Gm interface. This clause introduces the test configuration that has been used for the test purpose definitions. The Test System (TS) simulates the behaviour of one or more UEs. |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 4.3.1.1 Configurations using Gm interface only | The Gm interface is located between UE and the SUT. Figure 3: Test configuration CF_1 IMS SUT ue1home ue2home UE1 UE2 gm gm UE1atSUThome UE2atSUThome ETSI ETSI TS 186 001-4 V2.2.1 (2010-09) 10 Figure 4: Test configuration CF_2 Figure 5: Test configuration CF_3 |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 4.3.2 Test system architecture | |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 4.3.2.1 General | Test systems that implement this ATS shall conform to the requirements as defined in this clause. |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 4.3.2.2 Structure | An abstract architecture for a Test System (TS) implementing a TTCN-3 ATS is displayed in figure 6 and also stated in ES 201 873-5 [7]. Test Management (TM) Test Control (TC) Test Logging (TL) TCI TTCN-3 Executable (TE) TTCN-3 Runtime System (T3RTS) Executable Test Suite (ETS) Encoding/Decoding System TRI SUT Adapter (... |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 4.3.2.3 Interaction between TTCN-3 Executable (TE) and SUT Adapter (SA) | |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 4.3.2.3.1 Sending and receiving SIP/IMS messages | Before starting a test case, the SA shall provide the transport of SIP messages by establishing appropriate connections on the lower layers (shown in figure 6). In order to forward messages received in the SA to the test suite and to send them to the SUT a clear und unique association between the TTCN-3 TSI ports and t... |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 4.3.2.3.2 Security and messages compression feature | Security transport layer, and signalling compression may be used transparently to the ATS. |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 4.3.2.3.3 Additional SA constraints | In order to execute this test suite the SA should support: • communication channel handling (at least UDP and possibly also TCP); • IPv4 transport. |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 4.3.2.4 Encoding/Decoding requirements | |
c45631e0028c3d0fb8d0af05c5209d8c | 186 001-4 | 4.3.2.4.1 Encoding/Decoding System requirements for basic SIP messages/headers | SIP is a text-based protocol that allows different syntactical presentations of the same information. In general, an implementation of this ATS should use a EDS to parse received encoded messages into TTCN-3 type structures and values, and encode structured TTCN-3 type structures and values into encoded messages. This ... |
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(charst... |
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 cla... |
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: Lib... |
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 namin... |
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 under... |
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 (fo... |
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 paramet... |
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 fo... |
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])... |
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 accept... |
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 In... |
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 Interne... |
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 Associa... |
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 (20... |
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/Contr... |
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 set... |
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... |
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 N... |
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 fo... |
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 Pu... |
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 st... |
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 ... |
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 laye... |
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 intercon... |
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... |
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 ca... |
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 accept... |
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: "Digit... |
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) ... |
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 scope for the present document is to specify normative rules for how to use the Gq', Rq and Ia protocols (TS 183 017 [4], ES 283 026 [3] and ES 283 018 [7]) as of TISPAN release 1. 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... |
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 accept... |
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-Ti... |
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: A-RACF Access - Resource Admission Control Function AAA AA-Answer AAR AA-Request AF Application Function AVP Attribute Value Pair C/I-BGF Core/Interconnection Border Gateway Function CLF Connectivity session Location and repository Function IB... |
7e6c49a670de0a8ba391478d00f7fd4c | 183 048 | 4 Example call flow (informative) | Figure 4.1: RACS, BGF and P-CSCF/IBCF interactions 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 A-RACF in any order. Hence, interacting with the I/C-BGF before the A-RACF as shown in ... |
7e6c49a670de0a8ba391478d00f7fd4c | 183 048 | 5 RACS related procedures (normative) | |
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 ... |
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 ... |
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. |
7e6c49a670de0a8ba391478d00f7fd4c | 183 048 | 5.2.1 Reservation with BGF involved | 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-or... |
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 ai... |
7e6c49a670de0a8ba391478d00f7fd4c | 183 048 | 5.2.1.2 Specific Actions at the BGF | See Ia-to-Gq' mapping guidelines in ES 283 018 [7], annex E. NOTE: The present document has TISPAN Release 1 in scope, whereas the referred ES 283 018 [7] provides the H.248 Ia profile version 2 for TISPAN Release 2. This is considered not to be an issue because the present document is not yet providing signalling flow... |
7e6c49a670de0a8ba391478d00f7fd4c | 183 048 | 5.2.1.3 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 AV... |
7e6c49a670de0a8ba391478d00f7fd4c | 183 048 | 5.2.1.4 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-... |
7e6c49a670de0a8ba391478d00f7fd4c | 183 048 | 5.2.2 Reservation involving both A-RACF and BGF | The signalling flow when both the A-RACF and BGF are involved is a combination of the procedures for accessing the BGF specified in clauses 5.2.1 and the procedures for accessing the A-RACF specified in ES 283 026 [3]. The sequence used by the SPDF to access A-RACF and BGF is a local decision in the SPDF, e.g. the SPDF... |
7e6c49a670de0a8ba391478d00f7fd4c | 183 048 | 6 Example signalling flows (informative) | The examples of stage 3 signalling flows for TISPAN NGN release 1 provided by the present document cover signalling between P-CSCF and SPDF using Gq', IBCF and SPDF using Gq', SPDF and (C- and I-) BGF using Ia, and SPDF and A-RACF using Rq. The examples all build on a basic IMS end-to-end signalling flow between two SI... |
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... |
7e6c49a670de0a8ba391478d00f7fd4c | 183 048 | 6.1.1 Session setup | 1 2 3 4 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 INVITE B 100 Trying AAR Phone A P-CSCF A SPDF A A-RACF A C-BGF A S-CSCF C-BGF B A-RACF B SPDF B P-CSCF B Phone B Add Termination Reply AAR AAA INVITE B 100 Trying INVITE B 100 Trying AAA AAR Add Termi... |
7e6c49a670de0a8ba391478d00f7fd4c | 183 048 | 6.1.2 Session termination | 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 BIDIRECTIONAL RTP DATA BYE STR Subtract Termination Reply STR STA STA BYE BYE STR Subtract Termination Reply STR STA STA BYE 200 OK 200 OK (BYE) 200 OK (BYE) 200 OK 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 44 45 ... |
7e6c49a670de0a8ba391478d00f7fd4c | 183 048 | 6.2 IMS signalling flow involving IBCF entities | Core Network B Core Network A AF (P-CSCF A) SPDF A C-BGF A A-RACF A Gq’ Rq Ia AF (P-CSCF B) SPDF B C-BGF B A-RACF B Gq’ Rq Ia RCEF/ L2TF A RCEF/ L2TF B Re Re Access Node A Access Node B Ra Ra Phone A Phone B AF (S-CSCF A) A2 B1 A3 A1 B2 B3 AF (S-CSCF B) AF (IBCF A) AF (IBCF B) I-BGF A I-BGF B Ia SPDF AA SPDF BB Ia Gq’ ... |
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 200 OK AAR Add Reply AAA 200 OK 10.0 10.1 10.2 10.3 10.4 10.5 10.6 10.7 10.8 10.9 10.10 10.11 10.12 10.13 31.0 31.1 31.2 31.3 31.4 31.5 31.6 31.7 31.8 31.9 31.10 100 Trying... |
7e6c49a670de0a8ba391478d00f7fd4c | 183 048 | 6.2.2 Session termination | I-BGF A IBCF A SPDF AA IBCF B SPDF BB I-BGF B S-CSCF A S-CSCF B BYE STR Subtract Reply STA BYE STR Subtract Reply STA BYE 51.0 51.1 51.2 51.3 51.4 51.5 51.6 51.7 51.8 51.9 51.10 51.0 51.1 51.2 51.3 51.4 51.5 51.6 51.7 51.8 51.9 51.10 Figure 6.2.2.1: IMS end-to-end signalling chart for IBCF - session teardown Table 6.2.... |
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 accept... |
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) ... |
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) ... |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 3 Definitions and abbreviations |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.