hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 5.1 IPCablecom Architecture Framework | At a very high level, the IPCablecom 1.5 architecture contains three networks: the "DOCSIS® HFC Access Network", the "Managed IP Network" and the PSTN. The Cable Modem Termination System (CMTS) provides connectivity between the "DOCSIS® HFC Access Network" and the "Managed IP Network". Both the Signalling Gateway (SG) ... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 5.2 IPCablecom Zones and Domains | Administrative Domain 1 Administrative Domain 3 Administrative Domain 2 MSO A Zone 1 MSO A Zone 2 MSO B Zone 3 MSO C Zone 4 PSTN Gateway PSTN PSTN Gateway PSTN PSTN Gateway PSTN ` ` ` ` ` CMS Managed IP Backbone CMS CMS CMS Figure 2: Zones and Administrative Domains An IPCablecom zone consists of the set of MTAs in one... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 5.3 IPCablecom 1.5 Analog Trunking Specifications | IPCablecom 1.5 consists of the twenty Technical Specifications shown in table 1. ETSI ETSI TS 103 161-2 V1.1.1 (2011-10) 16 Table 1: IPCablecom 1.5 Specifications and Reports IPCablecom Technical Document Reference Number Brief Document Description TS 103 161-1 [i.38] IPCablecom 1.5 Overview TR 103 161-2 Architecture F... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 5.4 IPCablecom 1.5 Design Considerations | In order to enable real-time multimedia communications across the cable network infrastructure, IPCablecom 1.5 specifications define protocols in the following areas: • Call Signalling. • Quality of Service. • Media Stream Transport and Encoding. • Device Provisioning. • Event Messaging. • Security. • Electronic Survei... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 5.4.1 General Architectural Goals | • Enable voice quality capabilities similar to or better than the PSTN as perceived by the end-user. • Provide a network architecture that is scalable and capable of supporting millions of subscribers. • Ensure the one-way delay for local IP access and IP egress (i.e. excluding the IP backbone network) is less than 45 ... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 5.4.2 Call Signalling | • Define a network-based signalling architecture. • Provide end-to-end call signalling for the following call models: - calls that originate from the PSTN and terminate on the cable network; - calls that originate on the cable network and terminate on the cable network; - calls that originate from the cable network and... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 5.4.3 Quality of Service | • Provide a rich set of policy mechanisms to enable and manage QoS for IPCablecom services over the access network. • Provide admission control mechanisms for both upstream and downstream directions. • Allow dynamic changes in QoS while an IPCablecom call is under way. • Minimize abusive QoS usage, including theft-of-s... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 5.4.4 CODEC and Media Stream | • Minimize the effects of latency, packet-loss, and jitter on voice quality in the IP telephony environment. • Define a minimum set of audio codecs that must be supported on all IPCablecom endpoint devices (MTAs and MGs). Evaluation criteria for mandatory codecs are selected as those most efficient with respect to voic... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 5.4.5 Device Provisioning and OSS | • Support dynamic and static provisioning of customer premise equipment (MTA and Cable Modem). • Common provisioning changes should not require reboot of MTA. • Allow dynamic assignment and management of IP addresses for subscriber devices. ETSI ETSI TS 103 161-2 V1.1.1 (2011-10) 19 • Ensure that real-time provisioning... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 5.4.6 Security | • Enable residential voice capabilities with the same or higher level of perceived privacy as in the PSTN. • Provide protection against attacks on the MTA. • Protect the cable operator from various denial of service, network disruption and theft-of-service attacks. • Design considerations include confidentiality, authe... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 5.4.7 Lawful Interception | • Support the ability to perform lawful interception by reporting call data and call content. |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6 IPCablecom Functional Components | This clause describes the functional components present in an IPCablecom 1.5 network. Component descriptions are not intended to define or imply product implementation requirements but rather to describe the functional role of each of these components in the reference architecture. NOTE: Specific product implementation... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.1 Media Terminal Adapter (MTA) | An MTA is an IPCablecom client device that contains a subscriber-side interface to the subscriber's CPE (e.g. telephone) and a network-side signalling interface to call control elements in the network. An MTA provides codecs and all signalling and encapsulation functions required for media transport and call signalling... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.1.1 MTA Functional Requirements | An MTA is responsible for providing the following functionality: • NCS call signalling with the CMS. • QoS signalling with the CMTS. • Authentication, confidentiality and integrity of some messages between the MTA and other IPCablecom network elements. • Mapping media streams to the MAC services of the DOCSIS® access n... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.1.2 MTA Attributes | The following attributes characterize the E-MTA: • An embedded MTA has two MAC addresses, one for the cable modem and one for the MTA. • An embedded MTA has two IP addresses, one for the cable modem and one for the MTA. • An embedded MTA has two Fully Qualified Domain Names (FQDN), one for the cable modem and one for t... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.2 Cable Modem (CM) | The cable modem (CM) is a network element that is defined by DOCSIS® [i.14]. The CM is a modulator/demodulator residing on the customer premises that provides data transmission over the cable network using the DOCSIS® protocol. In IPCablecom, the CM plays a key role in handling the media stream and provides services su... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.3 HFC Access Network | IPCablecom-based services are carried over the Hybrid fibre/Coax (HFC) access network. The access network is a bi- directional, shared-media system that consists of the Cable Modem (CM), the Cable Modem Termination System (CMTS), and the DOCSIS® MAC and PHY access layers. |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.4 Cable Modem Termination System (CMTS) | The CMTS provides data connectivity and complementary functionality to cable modems over the HFC access network (DOCSIS®). It also provides connectivity to wide area networks. The CMTS is located at the cable television system head-end or distribution hub. The CMTS is responsible for the following functions: • Providin... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.4.1 CMTS Gate | The CMTS is responsible for allocating and scheduling upstream and downstream bandwidth in accordance with MTA requests and QoS authorizations established by the Gate Controller. The CMTS implements an IPCablecom Dynamic QoS Gate or CMTS Gate between the DOCSIS® cable network and an IP Backbone. The CMTS Gate is a func... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.5 Call Management Server (CMS) | The Call Management Server provides call control and signalling related services for the MTA, CMTS, and PSTN gateways in the IPCablecom network. The CMS is a trusted network element that resides on the managed IP portion of the IPCablecom network. An IPCablecom 1.5 CMS consists of the following logical IPCablecom compo... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.6 PSTN Gateway | IPCablecom allows MTAs to interoperate with the current PSTN through the use of PSTN Gateways. In order to enable operators to minimize cost and optimize their PSTN interconnection arrangements, the PSTN Gateway is decomposed into three functional components: Media Gateway Controller (MGC) - The MGC maintains the call ... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.6.1 Media Gateway Controller (MGC) | The Media Gateway Controller (MGC) receives and mediates call-signalling information between the IPCablecom network and the PSTN. It maintains and controls the overall call state for calls requiring PSTN interconnection. The MGC controls the MG by instructing it to create, modify, and delete connections that support th... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.6.2 Media Gateway (MG) | The Media Gateway provides bearer connections between the PSTN and the IPCablecom IP network. Each bearer is represented as an endpoint, and the MGC instructs the MG to set-up and control media connections to other endpoints on the IPCablecom network. The MGC also instructs the MG to detect and generate events and sign... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.6.2.1 Media Gateway Functions | The following functions are performed by the Media Gateway: • Terminates and controls physical circuits in the form of bearer channels from the PSTN. • Detects events on endpoints and connections as requested by the MGC. • Generates signals on endpoints and connections as instructed by the MGC (e.g. continuity tests). ... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.6.3 Signalling Gateway (SG) | The Signalling Gateway function sends and receives circuit-switched network signalling at the edge of the IPCablecom network. For IPCablecom 1.5, the signalling gateway function supports only non-facility associated signalling in the form of SS7. |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.6.3.1 SS7 Signalling Gateway Functions | The following functions are performed by the Signalling Gateway function: • Terminates physical SS7 signalling links from the PSTN (A, F links). • Implements security features, to ensure that the Gateway security is consistent with IPCablecom and SS7 network security requirements. • Terminates Message Transfer Part (MT... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.7 OSS Back Office Components | The OSS back office contains business, service, and network management components supporting the core business processes. As defined by the ITU TMN framework, the main functional areas for OSS are fault management, performance management, security management, accounting management, and configuration management. IPCable... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.7.1 Security Server - Key Distribution Centre (KDC) | For IPCablecom, the term KDC is utilized for a Kerberos security server. The Kerberos protocol with the public key PKINIT extension is used for key management on the interfaces between the MTA and the CMS and Provisioning Server. Refer to [i.10] for more information. Following MTA authentication using the PKINIT protoc... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.7.2 Dynamic Host Configuration Protocol Server (DHCP) | The DHCP server is a back office network element used during the MTA device provisioning process to allocate IP addresses and other client configuration information. See RFC 2131 [i.17]. |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.7.3 Domain Name System Server (DNS) | The DNS server is a back office network element used to map between domain names and IP addresses. 6.7.4 Trivial File Transfer Protocol Server or Hypertext Transfer Protocol Server (TFTP or HTTP) The TFTP server is a back office network element used during the MTA device provisioning process to download a configuration... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.7.5 SYSLOG Server (SYSLOG) | The SYSLOG server is an optional back office network element used to collect event notification messages indicating that certain events such as device errors have occurred. |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.7.6 Record Keeping Server (RKS) | The RKS is a trusted network element component that receives IPCablecom Event Messages from other trusted IPCablecom network elements such as the CMS, CMTS, and MGC. The RKS also, at a minimum, is a short-term repository for IPCablecom Event Messages. The RKS may assemble or correlate the Event Messages into coherent s... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.8 Announcement Server (ANS) | An Announcement Server (ANS) is a network component that manages and plays informational tones and messages in response to events that occur in the network. An ANS is a logical entity composed of an Announcement Controller (ANC) and an Announcement player (ANP). ETSI ETSI TS 103 161-2 V1.1.1 (2011-10) 26 |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.8.1 Announcement Controller (ANC) | The ANC initiates and manages all announcement services provided by the Announcement Player. The ANC requests the ANP to play announcements based on call state as determined by the CMS. When information is collected from the end-user by the ANP, the ANC is responsible for interpreting this information and manage the se... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 6.8.2 Announcement Player (ANP) | The Announcement Player is a media resource server. It is responsible for receiving and interpreting commands from the ANC and for delivering the appropriate announcement(s) to the MTA. The ANP also is responsible for accepting and reporting user inputs (e.g. DTMF tones). The ANP functions under the control of the ANC. |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7 Protocol Interfaces | Protocol specifications have been defined for most of the component interfaces in the IPCablecom 1.5 architecture. An overview of each protocol interface is provided within this clause. The individual IPCablecom specifications should be consulted for the complete protocol requirements. It is possible that some of these... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.1 Call Signalling Interfaces | Call signalling requires multiple interfaces within the IPCablecom architecture. These interfaces are identified in figure 5. Each interface in the diagram is labelled, and further described in the subsequent table 2. pkt-c2 pkt-c4 pkt-c6 pkt-c5 Figure 5: Call Signalling Interfaces ETSI ETSI TS 103 161-2 V1.1.1 (2011-1... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.1.1 Network-based Call Signalling (NCS) Framework | The IPCablecom Network-based Call Signalling (NCS) protocol (pkt-c1) is a profile of the MGCP call signalling protocol defined in RFC 3435 [i.31]. The NCS architecture places call state and feature implementation in a centralized component, the Call Management Server (CMS), and places device control intelligence in the... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.1.2 PSTN Signalling Framework | PSTN signalling interfaces are summarized in table 2 (pkt-c3 through pkt-c8). These interfaces provide access to PSTN-based services and to PSTN subscribers from the IPCablecom network. The IPCablecom PSTN signalling framework consists of a PSTN gateway that is divided into three functional components: • Media Gateway ... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.1.3 CMS to CMS Signalling Framework | IPCablecom 1.5 supports both inter-domain and intra-domain CMS-CMS and CMS-MGC signalling as defined in the IPCablecom CMSS specification [i.11]. The CMSS signalling architecture is based on the IETF Session Initiation Protocol (SIP) (RFC 3261 [i.26]). CMSS defines a call signalling protocol. It does not address routin... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.2 Media Streams | The IETF standard Real-time Transport Protocol (RTP) (RFC 1889) is used to transport media streams in the IPCablecom network [i.15]. IPCablecom uses the RTP profile for audio streams as defined in RFC 1890 [i.18]. The primary media flow paths in the IPCablecom network architecture are shown in figure 6. Note that the m... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.2.1 Real-time Transport Control Protocol (RTCP) | RTCP is defined in RFC 1889 [i.15]. It is based on the periodic transmission of control packets to all participants in the session, using the same distribution mechanism as the data packets. RTCP provides feedback on the quality of the data distribution. This is an integral part of the RTP's role as a transport protoco... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.3 MTA Device Provisioning | MTA Device Provisioning enables an MTA to register with the operator network and to provide subscriber services over the HFC network. Provisioning covers initialization, authentication, and registration functions required for MTA device provisioning. The IPCablecom 1.5 MTA Device Provisioning Specification [i.9] also i... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.4 SNMP Element Management Layer Interfaces | IPCablecom requires SNMP to interface the MTA to element management systems for MTA device provisioning. IPCablecom specifications rely on standard SNMP protocol operations such as "traps" and "informs" for event reporting, and "sets" and "gets" for device provisioning and management. The IPCablecom MIB modules are def... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.5 Event Messages Interfaces | |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.5.1 Event Message Framework | An Event Message is a data record containing information about network usage and activities. A single Event Message may contain a complete set of data regarding usage or it may only contain part of the total usage information. When correlated by the Record Keeping Server (RKS), information contained in multiple Event M... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.6 Quality of Service (QoS) | |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.6.1 QoS Framework | The IPCablecom QoS Framework is represented in figure 11. CMS/Gate Controller C M CM MTA Record Keeping Server Record Keeping Server CMTS CMTS CMS/Gate Controller pkt-q2 pkt-q2 MTA pkt-q3 pkt-q3 pkt-q1 pkt-q1 pkt-q4 pkt-q4 pkt-q5 pkt-q5 pkt-q6 Figure 11: IPCablecom QoS Interfaces Table 6 briefly identifies each interfa... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.6.2 Dynamic Quality of Service | IPCablecom Dynamic QoS (DQoS) utilizes the call signalling information at the time that the call is made to authorize resources for the call. This Dynamic QoS architecture prevents various theft of service attack types by integrating the QoS messaging with other protocols and network elements. The network elements that... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.7 CMS Subscriber Provisioning | The CMS Subscriber Provisioning specification [i.12] provides a means for automated service activation by defining an interface between the Provisioning Server (or an authorized Back Office component) and the CMS. The CMS Subscriber Provisioning framework is represented in figure 12. pkt-prov-p2 pkt-prov-p1 Figure 12: ... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.8 Lawful Interception | The IPCablecom lawful interception framework for Law Enforcement Authorities (LEA) to lawfully intercept the IP Telephony services over cable operators' broadband IP networks is in accordance with TS 102 836-1 [i.13]. The delivery of the intercepted call data and contents is in accordance with the delivery requirements... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.9 Security | |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.9.1 Overview | Each of IPCablecom's protocol interfaces is subject to threats that could pose security risks to both the subscriber and service provider. The IPCablecom architecture addresses these threats by specifying, for each defined protocol interface, the underlying security mechanisms (such as IPsec) that provide the protocol ... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.9.2 Device Provisioning Security | IPCablecom 1.5 allows device provisioning to occur in an unsecured mode, or in a secured mode. IPCablecom 1.5 also allows for insecure SNMPv2 management after the MTA has been securely provisioned. Since this clause of this Technical Report is dedicated to security, we assume that the network is operating in secure mod... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.9.2.1 Subscriber Enrolment | The subscriber enrolment process establishes a permanent subscriber billing account that uniquely identifies the MTA to the CMS via the MTA's MAC address. The billing account is also used to identify the services to which the MTA has subscribed. Subscriber enrolment may occur in-band or out-of-band. The specification o... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.9.2.2 Device Provisioning | The MTA device authenticates itself to the KDC using the PKINIT extension to Kerberos. After checking the authentication credentials and ensuring that the MTA is known to the backend provisioning system, the KDC issues a ticket for the Provisioning Server. The MTA uses the ticket to exchange SNMPv3 keys in a secure man... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.9.2.3 Dynamic Provisioning | SNMPv3 security will be used for dynamically provisioning and managing voice communications capabilities and other aspects of the MTA. |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.9.2.4 Device Authorization | Device authorization occurs when a provisioned MTA device authenticates itself to the Call Management Server, and establishes a security association with that server prior to becoming fully operational. Device authorization allows subsequent call signalling to be protected under the established security association. Th... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.9.2.5 Signalling Security | All signalling traffic, which includes QoS signalling, call signalling, and signalling with the PSTN Gateway Interface, travels through IPsec pipes. IPsec security association management occurs using some combination of Kerberos and IKE. Kerberos with the PKINIT extension is used to exchange keys between MTA clients an... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.9.2.6 Media Stream Security | During call setup, MTAs negotiate a particular encryption algorithm for the bearer stream. At a minimum, devices are required to support null encryption and AES encryption. Encryption is applied to the RTP packet's payload, but not to its header. Each RTP packet may include an optional message authentication code (MAC)... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 7.9.2.7 OSS and Billing System Security | The SNMP agents in IPCablecom MTAs implement SNMPv3 when operated in secure mode. The SNMPv3 User Security Model (RFC 3414 [i.28]) provides authentication and privacy services for SNMP traffic. SNMPv3 view-based access control (RFC 3415 [i.29]) may be used for access control to MIB objects. The IKE or Kerberos key mana... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 8 Network Design Considerations | |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 8.1 Time Keeping and Reporting Issues | In order to maintain service quality, it is highly recommended that all network equipment clocks be maintained to within 200 milliseconds of Universal Time Coordinated (UTC). Devices that send Event Messages are required to maintain time synchronization with the Network Time Protocol (NTP) [i.19]. It is recommended tha... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 8.2 Timing for Playout Buffer Alignment with Coding Rate | Equipment that generates and/or processes packets generally operates with a free-running clock. Problems may arise when offering isochronous services with such equipment due to the plesiochronous nature of these clocks. The difference in clock speed between these plesiochronous entities is generally exhibited as overru... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 8.3 IP Addressing | An MTA is a multi-function entity with one function required for CM administration and the second function being the MTA function itself. IPCablecom 1.5 MTAs are required to have two IP addresses (one for the CM and one for the MTA) and two MAC addresses (also one for the CM and one for the MTA). IPCablecom 1.5 support... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 8.4 Dynamic IP Address Assignment | An operational requirement exists to dynamically assign IP addresses to MTAs for both device provisioning and management and the various protocol operations. The call signalling model specified in the IPCablecom 1.5 NCS specification is based on the ability for a Call Management Server to map a subscriber's service to ... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 8.5 Fully Qualified Domain Name (FQDN) Assignment | It is assumed that the OSS back office systems will generate the FQDNs for IPCablecom devices and pass this data to the appropriate IPCablecom devices and other network elements. These interfaces are not defined in IPCablecom 1.5. |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 8.6 Priority Marking of Signalling and Media Stream Packets | The media and signalling streams for IPCablecom-based services require methods for properly marking and transporting packets at a sufficiently high level of Quality of Service, both in the DOCSIS® access network and in the managed IP backbone. The mechanism for providing low-latency Quality of Service for media streams... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 8.7 Fax Support | IPCablecom supports real-time fax transmission. In IPCablecom 1.5, fax is best accomplished using the ITU-T Recommendation T.38 [i.32] for fax relay over IP networks (i.e. local termination of fax and translating the fax stream to an IP fax-relay data stream). If a call is established using an audio codec, the MTA is i... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 8.8 Analog Modem Support | Analog modems may be supported in one of two ways: pass-through or modem relay via V.152 [i.34]. Similar to fax pass-through - an MTA will be asked to detect modem tones and, when such tones are detected, the CMS will instruct the MTA to switch over to the G.711 codec if it is not already in use. Echo cancellation is a... |
ae46d4a064bbd179e81aa4eea2c8ee4d | 103 161-2 | 8.9 DTMF Relay | DTMF is the use of dual-tone multiple frequency signals either by an autodialing system or through manual entry of tones. In order for DTMF tones to be captured correctly by the receiving device, tonal integrity (frequency accuracy and signal duration) must be maintained even through compression and transcoding. IPCabl... |
73535ac364a8b104e477068601d9e7fb | 103 141 | 1 Scope | The present document specifies the Facilities layer MCO functionalities. It specifies the entities and its interfaces with protocols in relation with other MCO entities at other layers and with the applications and services at the Facilities and Application layers. |
73535ac364a8b104e477068601d9e7fb | 103 141 | 2 References | |
73535ac364a8b104e477068601d9e7fb | 103 141 | 2.1 Normative 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 referenced document (including any amendments) applies. Referenced documents which a... |
73535ac364a8b104e477068601d9e7fb | 103 141 | 2.2 Informative 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 referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
73535ac364a8b104e477068601d9e7fb | 103 141 | 3 Definition of terms, symbols and abbreviations | |
73535ac364a8b104e477068601d9e7fb | 103 141 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 697 [i.1] apply. ETSI ETSI TS 103 141 V2.2.1 (2022-11) 6 |
73535ac364a8b104e477068601d9e7fb | 103 141 | 3.2 Symbols | Void. |
73535ac364a8b104e477068601d9e7fb | 103 141 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AER Application Error ASN Abstract Syntax Notation BME Bandwidth Management Entity CAM Cooperative Awareness Message C-ITS Cooperative Intelligent Transport Systems CLR Channel Load Ratio FCL Functional Configuration Limits FCP Functional Conf... |
73535ac364a8b104e477068601d9e7fb | 103 141 | 4 Facilities layer MCO functional operation | |
73535ac364a8b104e477068601d9e7fb | 103 141 | 4.1 Introduction | The Facilities layer MCO functional architecture is part of the MCO architecture as specified in ETSI TS 103 697 [i.1] based on general C-ITS architectural aspects defined in ETSI TS 103 696 [i.2] from which functional and technical aspects have been identified in the ETSI TR 103 439 [i.3]. The ETSI TS 103 697 [i.1] in... |
73535ac364a8b104e477068601d9e7fb | 103 141 | 4.2 Bandwidth Management entity operation | The Bandwidth Management Entity (BME) is responsible for the collection of the communication requirements of the ITS applications via the MCO_APP_FAC_MMT interface specified in clause 5.2 and may collect IPv6 protocol requests from the Networking & Transport layer using the MCO_FAC_NET_MMT interface as specified in ETS... |
73535ac364a8b104e477068601d9e7fb | 103 141 | 4.3 Message Handling entity operation | All active ITS applications that make use of MCO send message generation requests by providing their application data to the applicable MGEs, which in turn generates message handling requests to the Message Handling Entity (MHE) for the dissemination of the messages. Each message handling request sent to the MHE is ass... |
73535ac364a8b104e477068601d9e7fb | 103 141 | 4.4 Message Collecting entity operation | The Message Collecting Entity (MCE) collects the messages received from the lower layers through the MCO_FAC_NET_DATA interface specified in ETSI TS 103 836-4-1 [1] and shall provide the messages to the appropriate Message Receiving Entity (MRE) through the MCO_FAC_MS_DATA interface specified in clause 5.3 (see Figure ... |
73535ac364a8b104e477068601d9e7fb | 103 141 | 5 Interface Requirements | |
73535ac364a8b104e477068601d9e7fb | 103 141 | 5.1 Introduction | As identified in the ETSI TS 103 697 [i.1] and in clause 4 and as illustrated in Figure 7, the MCO_FAC has the following interfaces MCO_APP_FAC_MMT, MCO_FAC_MS_DATA, MCO_FAC_NET_MMT and MCO_FAC_NET_DATA. MCO_APP_FAC_MMT and MCO_FAC_MS_DATA interfaces are specified in the clauses below. The MCO_FAC_NET_MMT and MCO_FAC_N... |
73535ac364a8b104e477068601d9e7fb | 103 141 | 5.2 MCO_APP_FAC_MMT | Before triggering the generation of messages, ITS applications send their communication requirements to the MCO_FAC through an FCP using the parameters in Table 1. Each set of communication requirements corresponds to an FCP and is associated to an FcpID. Table 1: FCP parameters (input to MCO_FAC) M- Param.No Name of M... |
73535ac364a8b104e477068601d9e7fb | 103 141 | 5.3 MCO_FAC_MS_DATA | MGEs shall send to MCO_FAC a message handling request with the information in Table 4 for the transmission of each message. The message shall be embedded in a Facility-layer message together with the Protocol Control Information (PCI) required to be passed to the ITS Networking & Transport Layer. MGEs may attach MCI as... |
3cf9e5bf0c1fd1e4657bba058295b28d | 102 943 | 1 Scope | The present document specifies services to ensure that that the confidentiality of information sent to and from an Intelligent Transport System (ITS) station can be maintained at a level that is acceptable to the users of the station. |
3cf9e5bf0c1fd1e4657bba058295b28d | 102 943 | 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... |
3cf9e5bf0c1fd1e4657bba058295b28d | 102 943 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 133 102: "Universal Mobile Telecommunications System (UMTS); LTE; 3G security; Security architecture (3GPP TS 33.102)". [2] ETSI TS 102 940: "Intelligent Transport Systems (ITS); Security; ITS communications securi... |
3cf9e5bf0c1fd1e4657bba058295b28d | 102 943 | 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. |
3cf9e5bf0c1fd1e4657bba058295b28d | 102 943 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 2G Second Generation mobile telephony 3G Third Generation mobile telephony ESP Encapsulating Security Payload G5A Frequency band ranging from 5,875 GHz to 5,905 GHz IP Internet Protocol ITS Intelligent Transport System ITS-S ITS Station LTE Lo... |
3cf9e5bf0c1fd1e4657bba058295b28d | 102 943 | 4 Confidentiality requirements | |
3cf9e5bf0c1fd1e4657bba058295b28d | 102 943 | 4.1 Confidentiality for different application groups | TS 102 940 [2] identifies ITS application groups and their confidentiality requirements, as summarized below: • Cooperative awareness: No confidentiality services are needed. • Static local hazard warning: No confidentiality services are needed. • Dynamic local hazard warning: Depends on the details of the application.... |
3cf9e5bf0c1fd1e4657bba058295b28d | 102 943 | 5 Confidentiality Services | |
3cf9e5bf0c1fd1e4657bba058295b28d | 102 943 | 5.1 Application Layer | The present document does not mandate specific confidentiality services for use at the application layer. Applications may use any appropriate confidentiality service, for example the data encryption services provided by IEEE P1609.2 [4]. |
3cf9e5bf0c1fd1e4657bba058295b28d | 102 943 | 5.2 Network Layer | |
3cf9e5bf0c1fd1e4657bba058295b28d | 102 943 | 5.2.1 IP | Confidentiality services for IPv6 shall be provided using the Encapsulating Security Payload (ESP) protocol within IPSec [5]. The key management services for IPv6 shall be as defined in TS 102 941 [3]. |
3cf9e5bf0c1fd1e4657bba058295b28d | 102 943 | 5.2.2 Basic Transport Protocol | No confidentiality services for the ITS Basic Transport Protocol are defined. ETSI ETSI TS 102 943 V1.1.1 (2012-06) 7 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.