hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 1 Scope | The present document defines a protocol applicable to the a4 interface between the User Access Authorization Function (UAAF) and the Connectivity session Location and repository Function (CLF), based on the Diameter protocol. Whenever it is possible the present document specifies the requirements for this protocol by r... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 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... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 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] ETSI ES 282 004: "Telecommunications and Internet con... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 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. |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 3 Definitions and abbreviations | |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Attribute-Value Pair (AVP): corresponds to an Information Element in a Diameter message NOTE: See definition in RFC 3588 [9]. NASS User: See definition in ES 282 004 [1]. |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ABNF Augmented Backus-Naur Form AVP Attribute-Value Pair CLF Connectivity session Location and repository Function CNGCF Customer Network Gateway Configuration Function DHCP Dynamic Host Configuration Protocol IANA Internet Assigned Numbers Au... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 4 Overview | The Network Attachment Sub-System (NASS), defined in ES 282 004 [1], maintains information about IPconnectivity associated with NASS User connected to TISPAN networks. The document specifies the protocol for the NASS a4 interface between the User Access Authorization Function (UAAF) and the Connectivity session Locatio... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 5 Procedure descriptions | |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 5.1 General | |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 5.1.1 Information elements | The following clauses describe the realization of the functional procedures defined in the NASS (ES 282 004 [1]) using Diameter commands described in clause 7. This involves describing a mapping between the Information Elements defined in the NASS specification (ES 282 004 [1]) and Diameter AVPs. Admission applications... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 5.1.2 NASS User profile | NASS User profile information sent over the a4 interface comprises QoS profile information and initial gate setting information. Each of these pieces of information may be sent in the form of an identifier using the QoS-Profile-ID and Initial-Gate-Setting-ID AVPs or in the form of an explicit description using the QoS-... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 5.2 Procedures on the a4 interface | |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 5.2.1 Access profile push | |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 5.2.1.1 Overview | This procedure is used to push the Access Profile information from the UAAF to the CLF. This information flow occurs when a NASS User has been successful authenticated or in case a modification occurs on a profile that has already been pushed to the CLF. UAAF may decide to send in the same Access Profile Push some prof... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 5.2.1.2 Procedure at the UAAF side | The UAAF knows the address of the CLF entity where the information should be pushed, either from configuration data or from the NASS User profile (i.e. received from the PDBF). The UAAF shall populate the Access Profile Push as follows: • The Logical-Access-ID AVP shall be present. • In case PPP is applied, the Globall... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 5.2.1.3 Procedure at the CLF side | If the Logical-Access-ID AVP is not present or is invalid, the CLF shall return an Access Profile Push response with a Result-Code AVP value set to DIAMETER_INVALID_AVP_VALUE. ETSI ETSI TS 183 066 V2.1.1 (2009-01) 12 If the Logical Access ID contained in the Logical-Access-ID AVP is not known, the CLF shall: • Create a... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 5.2.2 Access profile pull | |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 5.2.2.1 Overview | The Access Profile Pull information flow is used by the CLF to request the Access Profile information from the UAAF. This information flow is used when the CLF - UAAF operates in pull mode or in the context of CLF recovery procedures. This procedure is mapped to the commands User-Data-Request/Answer in the Diameter app... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 5.2.2.2 Procedure at the CLF side | The CLF shall populate the Access Profile Pull Request as follows: 1) The User-Name AVP or the Globally-Unique-Address AVP or the Logical-Access-ID AVP shall be included. The Globally-Unique-Address AVP shall be included in configurations where more than one IP address may be assigned per NASS User ID. 2) If present, t... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 5.2.2.3 Procedure at the UAAF side | Upon reception of the Access Profile Pull Request, the UAAF shall, in the following order: 1) If the Logical-Access-ID AVP is present, use this information as a key to retrieve the requested Access Profile. 2) If the Logical-Access-ID AVP is absent but the Globally-Unique-Address AVP is present, use the latter informat... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 5.2.3 Remove Access Profile | |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 5.2.3.1 Overview | The Remove Access Profile information flow is used by the UAAF to request the CLF to delete the information it held about a NASS User. This event occurs as a result of network management actions. This procedure is mapped to the commands Push-Notification-Request/Answer in the Diameter application specified in clause 7.... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 5.2.3.2 Procedure at the UAAF side | The UAAF shall populate the Remove Access Profile Indication as follows: • The Logical-Access-ID AVP shall be present. • In case PPP is applied, the Globally-Unique-Address AVP shall be present. In case DHCP is applied, this AVP is optional. The Globally-Unique-Address AVP shall contain a Frame-IP-Address or Frame-IPv6... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 5.2.3.3 Procedure at the CLF side | If the Logical Access ID contained in the Logical-Access-ID AVP is not known, the CLF shall stop processing the request and set the Experimental-Result-Code to DIAMETER_ERROR_USER_UNKNOWN in the Remove Access Profile Response. If the Logical Access ID contained in the Logical-Access-ID AVP is already known, the CLF sha... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 6 Use of the Diameter base protocol | With the clarifications listed in the following clauses the Diameter Base Protocol defined by RFC 3588 [9] shall apply. |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 6.1 Securing Diameter Messages | For secure transport of Diameter messages, IPSec may be used. Guidelines on the use of SCTP with IPSec can be found in RFC 3554 [8]. |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 6.2 Accounting functionality | Accounting functionality (Accounting Session State Machine, related command codes and AVPs) is not used on the a4 interface. |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 6.3 Use of sessions | Diameter sessions are implicitly terminated. An implicitly terminated session is one for which the server does not maintain state information. The client does not need to send any re-authorization or session termination requests to the server. The Diameter base protocol includes the Auth-Session-State AVP as the mechan... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 6.4 Transport protocol | Diameter messages over the a4 interface shall make use of SCTP RFC 2960 [6] and shall utilize the new SCTP checksum method specified in RFC 3309 [7]. ETSI ETSI TS 183 066 V2.1.1 (2009-01) 16 |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 6.5 Routing considerations | This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host. Requests initiated by the UAAF towards the CLF shall include both Destination-Host and Destination-Realm AVPs. The UAAF obtains the Destination-Host AVP to use in requests towards a CLF, from configuration data in UAAF or... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 6.6 Advertising Application Support | The CLF and UAAF shall advertise support of the a4 specific application by including the value 16777257 of the application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. The vendor identifier... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 7 DIAMETER application | This clause specifies a Diameter application that allows a Diameter server and Diameter client exchange information related to NASS User network profile information. The Diameter application identifier assigned to this application is 16777257 (allocated by IANA). The Diameter Base Protocol as specified in RFC 3588 [9] ... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 7.1 Commands | The present document re-uses and modifies commands defined in the TS 129 329 [3] for the Sh interface. Only the following commands defined in TS 129 329 [3] are used. Any other command defined in TS 129 329 [3] shall be ignored. Table 7.1: Command-code values Command-Name Abbreviation Code User-Data-Request UDR 306 Use... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 7.1.1 User-Data-Request command | The User-Data-Request (UDR) command, indicated by the Command-Code field set to 306 and the "R" bit set in the Command Flags field, is sent by a Diameter client to a Diameter server in order to request user data. This command is defined in TS 129 329 [3] and used with additional AVPs defined in the present document. NO... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 7.1.2 User-Data-Answer command | The User-Data-Answer (UDA) command, indicated by the Command-Code field set to 306 and the "R" bit cleared in the Command Flags field, is sent by a server in response to the User-Data-Request command. This command is defined in TS 129 329 [3] and used with additional AVPs defined in the present document. The Experiment... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 7.1.3 Push-Notification-Request command | The Push-Notification-Request (PNR) command, indicated by the Command-Code field set to 309 and the "R" bit set in the Command Flags field, is sent by a Diameter server to a Diameter client in order to notify changes in the user data in the server. This command is defined in TS 129 329 [3] and used with additional AVPs... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 7.1.4 Push-Notification-Answer command | The Push-Notifications-Answer (PNA) command, indicated by the Command-Code field set to 309 and the "R" bit cleared in the Command Flags field, is sent by a client in response to the Push-Notification-Request command. This command is defined in TS 129 329 [3]. The Experimental-Result AVP may contain one of the values d... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 7.2 Result-Code AVP values | This clause defines new result code values that must be supported by all Diameter implementations that conform to the present document. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and Result-Code AVP shall be absent. |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 7.2.1 Success | Result codes that fall within the Success category are used to inform a peer that a request has been successfully completed. No result codes within this category have been defined so far. |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 7.2.2 Permanent failures | Errors that fall within the Permanent Failures category are used to inform the peer that the request failed, and should not be attempted again. ETSI ETSI TS 183 066 V2.1.1 (2009-01) 19 No errors within this category have been defined so far. However the following error defined in TS 129 229 [2] is used in the present d... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 7.2.3 Transient failures | Errors that fall within the transient failures category are those used to inform a peer that the request could not be satisfied at the time that it was received. The request may be able to be satisfied in the future. No errors within this category have been defined so far. However the following error defined in TS 129 ... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 7.3 AVPs | The following tables summarize the AVP used in the present document, beyond those defined in the Diameter Base Protocol. Table 7.2 describes the Diameter AVPs defined in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. The Vendor-Id header of all AVPs... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 7.3.1 Data-Operation-Indicator | The Data-Operation-Indicator AVP (AVP code 420 13019) is of type Enumerated and represents the type of data operation the receiver shall perform after receiving this AVP. When the Data-Operation-Indicator AVP is omitted, the receiver shall perform the update operation by default. The following values are defined: • UPD... |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 7.4 Use of namespaces | This clause contains the namespaces that have either been created in the present document, or the values assigned to existing namespaces managed by IANA. |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 7.4.1 AVP codes | The present document assigns the AVP values in the 420 to 439 range from the AVP Code namespace managed by ETSI for its Diameter vendor-specific applications. See clause 7.3 for the assigned values. |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 7.4.2 Experimental-Result-Code AVP values | The present document does not assign any Experimental-Result-Code AVP value. ETSI ETSI TS 183 066 V2.1.1 (2009-01) 21 |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 7.4.3 Command Code values | The present document does not assign command code values but uses existing command codes assigned to 3GPP. |
8417e56860be9e8305a0eeb862fa5f87 | 183 066 | 7.4.4 Application-ID value | The present document uses value 16777257, allocated by IANA, as application identifier. ETSI ETSI TS 183 066 V2.1.1 (2009-01) 22 Annex A (informative): Mapping of a4 operations and terminology to Diameter Table A.1 defines the mapping between the information flows defined in ES 282 004 [1] and Diameter commands. Table ... |
cde0dbe1a14aa46ac50042d67991544b | 186 007-3 | 1 Scope | The present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on the Test Suite Structure and Test Purposes defined in TS 186 007-2 [2]. The test notation used in the ATS is TTCN-3 (see ES 201 873-1 [7]). The following test specific... |
cde0dbe1a14aa46ac50042d67991544b | 186 007-3 | 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... |
cde0dbe1a14aa46ac50042d67991544b | 186 007-3 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 610: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Communication HOLD (HOLD) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specifica... |
cde0dbe1a14aa46ac50042d67991544b | 186 007-3 | 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. Not applicable. |
cde0dbe1a14aa46ac50042d67991544b | 186 007-3 | 3 Definitions and abbreviations | |
cde0dbe1a14aa46ac50042d67991544b | 186 007-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-7 [6], TS 102 587-2 [9] and TS 102 790-3 [3] apply. |
cde0dbe1a14aa46ac50042d67991544b | 186 007-3 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 [5], ISO/IEC 9646-7 [6], TS 102 790-3 [3] and TS 124 610 [1] apply. |
cde0dbe1a14aa46ac50042d67991544b | 186 007-3 | 4 Abstract Test Method (ATM) | For the purposes of the present document, the ATM described in clause 4 of TS 102 790-3 [3] applies with following additions. |
cde0dbe1a14aa46ac50042d67991544b | 186 007-3 | 4.1 Configurations for testing UE | The Gm interface is located between SUT (UE) and the IMS. SUT TS UE IMS Gm Figure 1: Test configuration CF_1GmUE ETSI ETSI TS 186 007-3 V3.1.1 (2012-01) 7 The ISC interface provides an access to the AP. SUT IMS AS ISC TS Figure 2: Test configuration CF_1ISC |
cde0dbe1a14aa46ac50042d67991544b | 186 007-3 | 5 The ATS development process | |
cde0dbe1a14aa46ac50042d67991544b | 186 007-3 | 5.1 Requirements and Test Purposes | For each test purpose there is a table defined in clause 5 of TS 186 007-2 [2]. The requirements applicable to this TP are given by a reference to TS 124 610 [1]. There are no explicit formulations of requirements. |
cde0dbe1a14aa46ac50042d67991544b | 186 007-3 | 5.2 ATS structure | |
cde0dbe1a14aa46ac50042d67991544b | 186 007-3 | 5.2.1 Test case grouping | The ATS structure defined in Table 1 is based on the structuring of Test Purposes in clause 4 of TS 186 007-2 [2]. The group names in column 2 of Table 1 are those assigned in the ATS; they are based on the names provided in clause 4 of TS 186 007-2 [2], but use the naming conventions defined for the ATS (see clause 5.... |
cde0dbe1a14aa46ac50042d67991544b | 186 007-3 | 5.2.2 Test case identifiers | The test case names are built up according to the following scheme: "<TC>"_"<Group index>"_"<TC number>" where: a) double quotes (") are used to enclose literal strings; b) <Group path index> is the group index in Table 1 (which uniquely identifies the path of groups/subgroups); c) <TC number> is a running 3-digit deci... |
cde0dbe1a14aa46ac50042d67991544b | 186 007-3 | 5.3 ATS specification framework | |
cde0dbe1a14aa46ac50042d67991544b | 186 007-3 | 5.3.1 ATS Library | For this ATS the TTCN-3 library modules are basically organized as: 1) AtsCommon modules. 2) LibIms modules. 3) LibSip modules (RFC 3261 [4]). 4) LibCommon modules (taken from an improved version of TS 102 351 [8]). NOTE: Due to the common LibSip and LibIms library approach with some other parallel running projects the... |
cde0dbe1a14aa46ac50042d67991544b | 186 007-3 | 5.3.2 Use of TTCN-3 | For the purposes of the present document, the description of the use of TTCN-3 described in clause 5.3.2 of TS 102 790-3 [3] applies. ETSI ETSI TS 186 007-3 V3.1.1 (2012-01) 10 Annex A (normative): Partial PIXIT proforma Notwithstanding the provisions of the copyright clause related to the text of the present document,... |
83397221380043918c10ad89da3c4c25 | 183 065 | 1 Scope | The present document provides the ETSI TISPAN endorsement of DSL Forum TR-069 "CPE WAN Management Protocol" (CWMP) in line with the requirements of TISPAN NGN for the specification of the e3 interface. |
83397221380043918c10ad89da3c4c25 | 183 065 | 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... |
83397221380043918c10ad89da3c4c25 | 183 065 | 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] DSL Forum Technical Report TR-069: "CPE WAN managemen... |
83397221380043918c10ad89da3c4c25 | 183 065 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACS Auto-Configuration Server CND Customer Network Device CNG Customer Network Gateway CNGCF Customer Network Gateway Configuration Function CPN Customer Premises Network CPNCF Customer Premises Network Configuration Function CPE Customer Prem... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 1 Scope | The present document provides the stage 3 description of the NGN integrated IPTV subsystem based on the architecture and stage 2 information flows described in TS 182 028 [4]. The protocol enhancements will form the scope of new or enhanced protocol specifications. The interaction with other NGN subsystems such as PES,... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 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... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI ES 282 001 (Release 3): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture". [2] ETSI ES 282 004 (Release 3): "Telecommunications and Intern... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 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 TR 187 013 (Release 3): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Feasibility study on ... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 3 Definitions and abbreviations | |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: NGN Integrated IPTV subsystem: IPTV subsystem integrated within TISPAN NGN architecture which provides advanced personalized interactive IPTV services UE (converged): end user device, e.g. set top box or enhanced TV, capable of support... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 3.2 Abbreviations | For the purposes of the present document the abbreviations given in TS 182 028 [4] and the following apply: ADM Ad Management Service ADS Ad Decision Service ASF Application Server Function BC BroadCast BCG Broadband Content Guide BiM Binary MPEG format for XML BTV Broadcast TV CCF Cluster Controller Function CDF Conte... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 4 Applicability | The following clauses explain the concept and approach used to define the protocols for the NGN integrated IPTV subsystem. |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 4.1 Concept and Approach | This clause outlines concept and approach adopted in the present document. The approach is then applied to protocol selections, mapping to interfaces and protocol extensions. The present document focuses on defining protocols for flexible functional architecture described in [4], which can: • allow development of new I... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 4.2 Overview | The clause describes applicability of the protocols discussed further in the present document to reference points defined in TS 182 028 [4]. The overall functional architecture for the NGN integrated IPTV service conforms to [4]. Figure 1 presents mapping of protocols to interfaces in NGN integrated NGN-IPTV and to int... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 4.3 Functional Entities | The functional entities that constitute the NGN integrated IPTV subsystem are defined in TS 182 028 [4]. The following clauses summarize the functionality of each functional entity. |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 4.3.1 User Equipment(UE) | The UE is a functional entity that provides the user with access to IPTV services. |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 4.3.2 Service Discovery and Selection (SD&S) | The Service Discovery and Selection (SD&S) is a functional entity that provides description information for discovery of the service as well as information required for description and selection of IPTV services. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 18 |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 4.3.3 Customer Facing IPTV Applications (CF-IPTV-Apps) | The Customer Facing IPTV Application (CFIA) is a functional entity that provides IPTV service provisioning, selection and authorization. |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 4.3.4 IPTV Control (IPTV-C) | The IPTV Control (IPTV-C) is a functional entity that checks if UE has been authorized by the Customer Facing IPTV Application to use IPTV Service Control and Delivery Functions (provides selection of the Media Control Function). |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 4.3.5 Media Control Function (MCF) | The Media Control Function (MCF) is a functional entity that provides the UE with functions required to control media flows and manages the MDFs under its control. |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 4.3.6 Media Delivery Function (MDF) | The Media Delivery Function (MDF) is a functional entity that delivers content data to the UE. |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 4.3.7 IPTV User Data Function (IPTV UDF) | IPTV user data (IUDF) functional entity is responsible for handling NGN integrated IPTV user data. |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 4.3.8 NGN User Data Access Function (NGN UDAF) | NGN Application User Data FE (NGN UDF) is a functional entity responsible for handling NGN application and user data. |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 4.3.9 Inter-destination media synchronization entities | Figure 1a shows the two functional entities involved in inter-destination media synchronization, i.e. the synchronization client (SC) and the media synchronization application server (MSAS). Optionally, there is also a Synchronisation Client' (SC'). These functional entities are described in clauses 4.3.9.1, 4.3.9.2 an... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 4.3.9.1 MSAS | The MSAS is a functional entity that coordinates session synchronization with SCs and SC's for inter-destination synchronization purposes. The MSAS session-level capabilities are reflected as elementary functions of the CFIA, its media-level capabilities are reflected as independent functional entities or as adjunct fu... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 4.3.9.2 SC | The SC is a functional entity that coordinates session synchronization with the MSAS for inter-destination synchronization purposes. It is an elementary function of the UE or an adjunct function of the Transport Processing Functions. Tasks of the SC are: • setting up and accepting synchronization sessions with/from the... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 4.3.9.3 SC' | The SC' is a functional entity that assists session synchronization by the MSAS for inter-destination media synchronization purposes. It is an elementary or adjunct function of functional entities that modify and/or re-originate media streams, e.g. a transcoder or a mixer in an MDF. |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 4.3.10 Service Protection and Content Protection function (SCP) | The functional entities and elementary functions that in the NGN integrated IPTV subsystem responsible for Service protection and content protection are defined in TS 182 028 [4] clause 7 and TISPAN NGN security architecture TS 187 003 [i.17] in clause 9 and IPTV security TR 187 013 [i.1]. |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 4.4 Compliance | Compliance for the Integrated IPTV service conforms to table 1a. Table 1a: IPTV services and features supported by NGN integrated IPTV subsystem: NGN IPTV Release Service and Feature Short name (ServiceType) TISPAN R3 Stage 2 NGN integrated IPTV subsystem TISPAN R3 Stage 3 NGN integrated IPTV subsystem Specification TS... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5 Procedures using HTTP for NGN integrated IPTV | NGN integrated IPTV reference points (Tr, Ct2, Ss, Ss') using http shall follow HTTP/1.1 [9]. NOTE: Other protocols such as RTSP may be used on Ct2, Ss and Ss'. If URI is supplied as "http:" [40], the receiver and the sender shall conform to HTTP/1.1 [9] and use port specified in the URI. When the URI is specified as "... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1 User Equipment (UE) and Control Functions | Mechanism used for user interaction between UE and Control Function shall support service personalization and multiple user behind UE. Access to personalized IPTV services may required additional user authentication and authorization, e.g. PIN for content purchase, access to restricted content. The personalization of I... |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1.1 Procedures for SD&S | Mechanisms used to identify service providers and services in the context of service discovery shall apply conforming to TS 102 034 [5], clause 5.2. SD&S segments may be encoded with BiM conforming to TS 102 034 [5], clause 5.5. |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1.1.1 Push mode | Push model delivery of BCGs using multicast shall use the DVBSTP protocol for this purpose in alignment with clause 4.1.2 of TS 102 034 [5]. ETSI ETSI TS 183 064 V3.4.1 (2011-02) 22 |
0c678f4294f75d371c5dbfd089522f4b | 183 064 | 5.1.1.2 Pull Mode | In the pull model of unicast delivery of a DVB SD&S data, the HTTP protocol shall be used conforming to TS 102 034 [5], clause 5.4.2. In the pull model of unicast container-based delivery of DVB BCG data, the HTTP protocol shall be used conforming to TS 102 539 [8], clause 4.1.2.2.2. In the pull model of unicast query ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.