hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.2.2.5 Connection Parameters | Connection parameters are encoded as a string of type and value pairs, where the type is one of the codes in table 11, and the value is a decimal integer. Types are separated from values by an "="sign. Parameters are separated from each other by a comma. Table 11: Connection Parameters Connection Parameter Name Code Co... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.2.2.6 Reason Codes | Reason codes are three-digit numeric values. The reason code is optionally followed by a white space and commentary, e.g.: E: 900 Endpoint malfunctioning A list of reason-codes can be found in clause 7.6. |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.2.2.7 Connection Mode | The connection mode describes the connection's operation mode. The possible values are shown in table 12: Table 12: Connection Mode Mode Meaning M: sendonly The gateway should only send packets. M: recvonly The gateway should only receive packets. M: sendrecv The gateway should send and receive packets. M: confrnce The... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.2.2.8 Event/Signal Name Coding | Event/signal names are composed of an optional package name, separated by a slash (/) from the name of the actual event. The event name can optionally be followed by an at sign (@) and the identifier of a connection on which the event should be observed. Event names are used in the RequestedEvents, SignalRequests, Dete... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.2.2.9 RequestedEvents | The RequestedEvents parameter provides the list of events that have been requested. The currently defined event codes are described in annex A. Each event can be qualified by a requested action, or by a list of actions. Not all actions can be combined - please refer to clause 7.3.1 for valid combinations. The actions, ... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.2.2.10 SignalRequests | The SignalRequests parameter provides the name of the signals that have been requested. The currently defined signals can be found in Annex A. A given signal can only appear once in the list, and all signals will, by definition, be applied at the same time. The MTA shall support, at a minimum, a single signal on each e... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.2.2.11 ObservedEvents | The observed events parameters provide the list of events that have been observed. The event codes are the same as those used in the NotificationRequest. When an event is detected on a connection, the observed event will identify the connection the event was detected on using the "@<connection>" syntax. Examples of obs... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.2.2.12 RequestedInfo | The RequestedInfo parameter contains a comma separated list of parameter codes, as defined in the "Parameter lines" clause - clause 7.3.8 lists the parameters that can be audited. The values listed in table 17 below are supported as well. Table 17: RequestedInfo Parameter Values RequestedInfo Parameter Code LocalConnec... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.2.2.13 QuarantineHandling | The quarantine handling parameter contains a list of comma separated keywords: • The keyword "process" or "discard" to indicate the treatment of quarantined and observed events. If neither process nor discard is present, process is assumed. • The keyword "step" or "loop" to indicate whether at most one notification is ... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.2.2.14 DetectEvents | The DetectEvents parameter is encoded as a comma separated list of events, such as for example: T: hu,hd,hf,[0-9#*] It should be noted, that no actions can be associated with the events. |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.2.2.15 EventStates | The EventStates parameter is encoded as a comma separated list of events, such as for example: ES: hu It should be noted, that no actions can be associated with the events. |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.2.2.16 ResourceID | The ResourceID parameter is a return parameter used for Dynamic Quality of Service to signal the resource ID assigned for the gate in question. The ResourceID is encoded as a string of up to 8 hex characters, such as for example: DQ-RI: AB345DC |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.2.2.17 RestartMethod | The RestartMethod parameter is encoded as one of the keywords "graceful", "cancel-graceful", "forced", "restart", or "disconnected", as for example: RM: restart |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.2.2.18 VersionSupported | The VersionSupported parameter is encoded as a comma separated list of versions supported, such as for example: VS: MGCP 1.0, MGCP 1.0 NCS 1.0 ETSI ETSI TS 103 161-4 V1.1.1 (2011-10) 79 |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.2.2.19 MaxMGCPDatagram | The MaxMGCPDatagram parameter is encoded as a string of up to nine decimal digits - leading zeroes are not permitted. The following example illustrate the use of this parameter: MD: 8100 |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.3 Response Header Formats | The response header is composed of a response line optionally followed by headers that encode the response parameters. The response line starts with the response code, which is a three-digit numeric value. The code is followed by a white space, the transaction identifier, and optional commentary preceded by a white spa... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.3.1 CreateConnection | In the case of a CreateConnection message, the response line is followed by a Connection-Id parameter with a successful response (code 200). A LocalConnectionDescriptor is furthermore transmitted with a positive response. The LocalConnectionDescriptor is encoded as a "session description", as defined in clause 8.4. It ... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.3.2 ModifyConnection | In the case of a successful ModifyConnection message, the response line is followed by a LocalConnectionDescriptor, if the modification resulted in a modification of the session parameters (e.g. changing only the mode of a connection does not alter the session parameters). The LocalConnectionDescriptor is encoded as a ... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.3.3 DeleteConnection | Depending on the variant of the DeleteConnection message, the response line may be followed by a Connection Parameters parameter line, as defined in clause 8.2.2.5. 250 1210 OK P: PS=1245, OS=62345, PR=780, OR=45123, PL=10, JI=27, LA=48, PC/RPS=782, PC/ROS=45238, PC/RPL=5, PC/RJI=26 |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.3.4 NotificationRequest | A NotificationRequest response does not include any additional response parameters. |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.3.5 Notify | A Notify response does not include any additional response parameters. |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.3.6 AuditEndpoint | In the case of an AuditEndPoint the response line may be followed by information for each of the parameters requested- each parameter will appear on a separate line. Parameters for which no value currently exists, e.g. digit map, will still be provided. Each local endpoint name "expanded" by a wildcard character will a... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.3.7 AuditConnection | In the case of an AuditConnection, the response may be followed by information for each of the parameters requested. Parameters for which no value currently exists will still be provided. Connection descriptors will always appear last and each will be preceded by an empty line, as for example: 200 1203 OK C: A3C47F2145... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.3.8 RestartInProgress | The response to a RestartInProgress may include the name of another Call Agent to contact, for instance when the Call Agent redirects the endpoint to another Call Agent as in: 521 1204 Redirect N: CA-1@ca.whatever.net |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.4 Session Description Encoding | The session description is encoded in conformance with the session description protocol (SDP), however, embedded clients may make certain simplifying assumptions about the session description as specified in the following. It should be noted, that session descriptions are case sensitive per [3]. SDP usage depends on th... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.4.1 Use of SDP | In an analogue line gateway, we only have to describe sessions that use exactly one MIME media type at a given point in time; either "audio" (for voice or voice-band data) or "image" (for T.38 fax calls). The parameters of SDP that are relevant for both the "audio" and "image" based media types are specified in clause ... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.4.2.1 Protocol Version (v=) | v= <version> "v= 0" Send: shall be provided in accordance with [3] (i.e. v=0). Receive: shall be provided in accordance with [3]. |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.4.2.2 Origin (o=) | The origin field consists (o=) of 6 sub-fields in [3]: o= <username> <session-ID> <version> <network-type> <address-type> <address> "o= - 2987933615 2987933615 IN IP4 126.16.64.4" Username: Send: Hyphen shall be used as username when privacy is requested.Hyphen should be used otherwise. (Since NCS endpoints do not know... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.4.2.3 Session Name (s=) | s= <session-name> "s= -" Send: Hyphen shall be used as Session name. Receive: This field shall be ignored. ETSI ETSI TS 103 161-4 V1.1.1 (2011-10) 85 |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.4.2.4 Session and Media Information (i=) | i= <session-description> Send: For NCS, the field shall not be used. Receive: This field shall be ignored. |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.4.2.5 URI (u=) | u= <URI> Send: For NCS, the field shall not be used. Receive: This field shall be ignored. |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.4.2.6 E-Mail Address and Phone Number (e=, p=) | e= <e-mail-address> p= <phone-number> Send: For NCS, the field shall not be used. Receive: This field shall be ignored. |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.4.2.7 Connection Data (c=) | The connection data consists of 3 sub-fields: c= <network-type> <address-type> <connection-address> "c= IN IP4 10.10.111.11" Network Type: Send: Type 'IN' shall be used. Receive: Type "IN" shall be present. Address Type: Send: Type "IP4" shall be used. Receive: Type "IP4" shall be present. Connection Address: Send: Thi... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.4.2.8 Bandwidth (b=) | b= <modifier> : <bandwidth-value> "b= AS : 64" Send: Bandwidth information is optional in SDP but it should always be included. When an rtpmap or a non well-known codec is used, the bandwidth information shall be used. NOTE 1: Since NCS endpoints do not know when privacy is requested, they should always use a hyphen. N... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.4.2.9 Time, Repeat Times and Time Zones (t=, r=, z=) | t= <start-time> <stop-time> "t= 36124033 0" r= <repeat-interval> <active-duration> <list-of-offsets-from-start-time> z= <adjustment-time> <offset> Send: Time shall be present; start time may be zero, but should be the current time, and stop time should be zero. Repeat Times, and Time Zones should NOT be used, if they a... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.4.2.10 Attributes (a=) | a= <attribute> : <value> a= mptime: <alternative 1> <alternative 2 > … a= recvonly a= sendrecv a= sendonly a= ptime a=pmft: <modem-fax-transport> Send: One or more of the "a" attribute lines specified below may be included. Receive: One or more of the "a" attribute lines specified below may be included and shall be act... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.4.3 SDP Audio Service Use | The following SDP parameters are applied at the media level and are specific to Audio Service Use. Audio Service Use includes VBD mode as defined in V-152 [12]. IPCablecom endpoints shall not send any of these parameters within an image media descriptor (see clause 8.4.4). If, however, the endpoint receives an SDP with... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.4.3.1 Encryption Keys: | k= <method> k= <method> : <encryption-keys> Security services for IPCablecom are defined by IPCablecom Security [7]. The security services specified for RTP and RTCP do not comply with those of [i.1], [2], and [3]. In the interest of interoperability with non-IPCablecom devices, the "k" parameter will therefore not be ... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.4.3.2 Attributes (a=) | a= <attribute> : <value> a= rtpmap : <payload type> <encoding name>/<clock rate> [/<encoding parameters>] a= rtpmap : 0 PCMU / 8000 a= fmtp:<format><format specific parameters> a= X-pc-codecs: <alternative 1> <alternative 2> … a= X-pc-secret: <method>:<encryption key> [pad] a= X-pc-csuites-rtp: <alternative 1> <alterna... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.4.3.3 Media Announcements (m=) | Media Announcements (m=) consists of 4 sub-fields: m= <media> <port> <transport> <fmt list> "m= audio 3456 RTP/AVP 0 97" Media: Send: The 'audio' media type shall be used. Receive: The type received shall be 'audio'. Port: Send: Shall be filled in accordance with [3]. The port specified is the receive port, regardless ... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.4.4 SDP Image Service Use for T.38 | The following SDP parameters are applied at the media level and are specific to Image Service Use for T.38. IPCablecom endpoints shall not send any of these parameters within an audio media descriptor (see clause 8.4.3). If, however, the endpoint receives an SDP with attribute parameters specific to audio only within a... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.4.4.1 Encryption Keys: | k= <method> k= <method> : <encryption-keys> There are currently no security services defined for the "image/t38" media type. Send: shall not be used. Receive: This field should be ignored. |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.4.4.2 Attributes (a=) | a= <attribute> : <value> a=T38FaxVersion: <version> a=T38MaxBitrate: <bitrate> a=T38FaxRateManagement: <faxratemanagement> a=T38FaxMaxBuffer: <maxbuffer> a=T38FaxMaxDatagram: <maxsize> a=T38FaxUdpEC: <ECmethod> a=T38FaxFillBitRemoval a=T38FaxTranscodingMMR a=T38FaxTranscodingJBIG Send: One or more of the "a" attribute ... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.4.4.3 Media Announcements (m=) | Media Announcements (m=) consists of 4 sub-fields: m= <media> <port> <transport> <fmt list> "m= image 3456 udptl t38" Media: Send: The 'image' media type shall be used for UDPTL-based T.38. Receive: The type received shall be 'image' for UDPTL-based T.38. Port: Send: Shall be filled in accordance with [3]. The port spe... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.5 Transmission Over UDP | |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.5.1 Reliable Message Delivery | MGCP messages are transmitted over UDP. Commands are sent to one of the IP addresses defined in the Domain Name System (DNS) for the specified endpoint or Call Agent. The responses are sent back to the source address of the command. However, it should be noted that the response may, in fact, come from another IP addres... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.5.2 Retransmission Strategy | The present document avoids specifying any static values for the retransmission timers since these values are typically network-dependent. Normally, the retransmission timers should estimate the timer by measuring the time spent between sending a command and the return of a response. Embedded clients shall implement a ... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.5.3 Maximum Datagram Size, Fragmentation and Reassembly | MGCP messages being transmitted over UDP rely on IP for fragmentation and reassembly of large datagrams. The maximum theoretical size of an IP datagram is 65 535 bytes. With a 20-byte IP header, and an 8-byte header, this leaves us with a maximum theoretical MGCP message size of 65 507 bytes when using UDP. However, IP... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.6 Piggy-Backing | There are cases when a Call Agent will want to send several messages at the same time to one or more endpoints in a gateway and vice versa. When several messages have to be sent in the same UDP packets, they are separated by a line of text that contains a single dot, as in for example: 200 2005 OK . DLCX 1244 aaln/2@rg... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.7 Transaction Identifiers And Three Ways Handshake | Transaction identifiers are integer numbers in the range from 1 to 999,999,999. Call-agents may decide to use a specific number space for each of the gateways that they manage, or to use the same number space for all gateways that belong to some arbitrary group. Call agents may decide to share the load of managing a la... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 8.8 Provisional Responses | In some cases, transaction completion times may be significantly longer than otherwise. NOTE: For instance when resources are reserved and committed externally as part of a transaction. NCS uses UDP as the transport protocol and reliability is achieved by selective time-out based retransmissions where the time-out is b... |
a013481e544daf33cdc470586dede914 | 103 161-4 | 9 Security | If unauthorized entities could use the MGCP, they would be able to set up unauthorized calls or interfere with authorized calls. Security is not provided as an integral part of MGCP. Instead MGCP assumes the existence of a lower layer providing the actual security. Security requirements and solutions for NCS are provid... |
5eae13bf4f56c2a723451406771aa632 | 103 161-18 | 1 Scope | New objects that are being introduced beyond IPCablecom 1.0 for MTA MIBS are being grouped in the present document so that the additional changes made can be tracked easily. |
5eae13bf4f56c2a723451406771aa632 | 103 161-18 | 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... |
5eae13bf4f56c2a723451406771aa632 | 103 161-18 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ANSI/SCTE 23-3 (2010): "DOCSIS 1.1 Part 3: Operations Support System Interface". [2] Cable Television Laboratories, Inc. (CL-SP-MIB-CLABDEF- I09-110210): "CableLabs® Definition MIB Specification", November 2, 2010. [3] ANS... |
5eae13bf4f56c2a723451406771aa632 | 103 161-18 | 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. |
5eae13bf4f56c2a723451406771aa632 | 103 161-18 | 3 Definitions and abbreviations | Not applicable. |
5eae13bf4f56c2a723451406771aa632 | 103 161-18 | 4 Void | ETSI ETSI TS 103 161-18 V1.1.1 (2011-10) 7 |
5eae13bf4f56c2a723451406771aa632 | 103 161-18 | 5 Requirements | The IPCablecom Extension MTA MIB must be implemented as defined below, using these references: [1], [2], [3], [4], and [5]. PKTC-EN-MTA-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE FROM SNMPv2-SMI OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF pktcEnhancements FROM CLAB-DEF-MIB; pktcEnMtaMib MODULE-... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 1 Scope | The present document defines the interface used between the Call Management Server (CMS) and Provisioning Server (PS) for the exchange of service provisioning information. The interface employs a Web Service model. Specified in Web Service Description Language 1.1 (WSDL 1.1), the interface transports XML encoded object... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 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... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] PacketCable 1.5 PKT-TR-ARCH1.5-V02-700412: "Architecture Framework Technical Report", April 12 2007, Cable Television Laboratories, Inc. [2] PacketCable 1.5 PKT-SP-PROV1.5-I04-090624: "MTA Device Provisioning Specification... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 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] Web Services Description Language. NOTE: Available at http://www.w3.org/TR/wsdl. [i.2] Simple Object Access Protocol. NOTE: Available at http://www.w3... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 3 Definitions and abbreviations | |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: active: service flow is said to be "active" when it is permitted to forward data packets NOTE: A service flow must first be admitted before it is active. endpoint: Terminal, Gateway or Multipoint Conference Unit Internet key exchange: ... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAA Authentication, Authorization and Accounting BPP Basic POTS Provisioning CFP Call Feature Provisioning CM DOCSIS Cable Modem CMS Call Management Server ETSI ETSI TS 103 161-17 V1.1.1 (2011-04) 9 CMS Cryptographic Message Syntax CMTS Cable ... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 4 Void | |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 5 Technical Overview | |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 5.1 Void | Figure 1: Void |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 5.2 IPCablecom Reference Architecture | Figure 2 shows the reference architecture for the IPCablecom 1.5 Network. Refer to the Architecture Document [1] for more detailed information on this reference architecture. ETSI ETSI TS 103 161-17 V1.1.1 (2011-04) 10 Figure 2: IPCablecom 1.5 Network Component Reference Model |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 5.3 Components and Interfaces | Provisioning is defined as the operations necessary to provide a specified service to a customer. IPCablecom service provisioning can be viewed as two distinct operations: MTA provisioning and CMS subscriber provisioning. Figure 3 presents the provisioning related interfaces maintained by the PS and other authorized Ba... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 5.4 Components | 5.4.1 Back Office Components (Service Provider Business and Service Management Systems) These are the Back Office Components that a service provider uses to manage customers and other components that make up their business. These systems provide the IPCablecom provisioning process with service orders or optionally indi... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 5.4.2 Provisioning Server | This system forms the interface between the provider's Back Office Components and some or all of the IPCablecom elements. IPCablecom does not address the implementation of this system or its relationship to other OSSs that a service provider might employ. The Provisioning Server is defined in [2] as consisting of a pro... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 5.4.3 CMS | The Call Management Server component is described in [1]. This component provides call control and signalling- related services for the MTA and CMTS components in the IPCablecom network. |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 5.4.4 MTA | A Media Terminal Adapter is an IPCablecom client device that contains a subscriber-side interface to the customer's CPE (e.g. telephone) and a network side signalling interface to call control elements in the network. This component is described in [1]. |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 5.4.5 TFTP | A configuration file service that is the basis for most device configuration in an IPCablecom network. This could be a standalone TFTP Service that delivers statically-defined files to devices or a dynamic service that creates configurations on-the-fly from other data sources. |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 5.5 Interface Descriptions | |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 5.5.1 Pkt-p1 | This interface is defined in [2]. |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 5.5.2 Pkt-p4 | This interface is defined in [2]. |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 5.5.3 Pkt-prov-p1 | The interface defined in the present document. ETSI ETSI TS 103 161-17 V1.1.1 (2011-04) 12 |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 6 Assumptions | • The Back Office components is responsible for coordinating endpoint updates with affected network entities (MTAs, CMTSs, etc.) and the CMS. • CMS will not play a manager role nor does it specify SNMP communications to an MTA during CMS provisioning. • The CMS and PS reside in the same secure provisioning domain. Secu... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 7 Subscriber Provisioning | Subscriber provisioning consists of: • Customer record/billing support. • Equipment setup/configuration. |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 7.1 Customer Records (Billing) | Establishment of a customer record that contains the information needed to deliver service, bill, and collect payment from a customer. Customer record creation/billing is considered part of the back office OSS application and is currently out of scope for IPCablecom. |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 7.2 Equipment Setup and Configuration | This may include physical installation and/or connection of equipment as well as any software and/or database updates necessary to actually deliver the service to the customer. Equipment setup affects two major components in an IPCablecom environment: • Customer premises equipment. For IPCablecom, this is the MTA. The ... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 7.2.1 CMS Basic POTS Provisioning (BPP) | BPP provides the CMS with the minimal set of data necessary for routing of simple telephony service (POTS) in the IPCablecom network. This minimal set of data consists of a telephone number mapped to its associated MTA's FQDN and NCS endpoint identifier. This data will be used to setup translation tables enabling the C... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 7.2.2 CMS Call Feature Provisioning (CFP) | In addition to BPP, CFP is performed to provide call features to a customer. CFP is more complicated than BPP as the parameters passed may vary on a feature-by-feature basis and may also be dependent on vendor specific implementations. ETSI ETSI TS 103 161-17 V1.1.1 (2011-04) 13 |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 7.3 Static Versus Dynamic Subscriber Provisioning Data | Data required by the CMS for subscriber provisioning falls into two classifications: 1) Static, billed, permanently assigned service state. This data does not change call to call. Examples would be DQoS settings, call feature subscribed/non-subscribed states, caller ID information, etc. 2) Dynamic, non-billed, semi per... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 8 Requirements | |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 8.1 General Requirements | • The interface shall make no assumptions regarding PS and CMS implementation technologies. Multiple partnering vendors will undoubtedly provide CMS and PS implementations on various hardware, software, and development language platforms. A platform and language neutral interface is required. • The interface shall supp... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 8.2 Transport Requirements | • The transport shall make no assumptions regarding the physical networking infrastructure between a PS and a CMS. It is anticipated that multiple service providers will be interoperating over a single access network. Thus, multiple enterprises will be communicating, potentially using CMS and PS implementations from va... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 9 Data Model | This clause provides a high level description of the PCSP data model and its XML encoding. It is intended as descriptive and non-authoritative. The authoritative definition of the data model and its encoding is found in the PCSP XML schema in annex A. |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 9.1 Overview | The data model for IPCablecom CMS provisioning is displayed in figure 4. It consists of two categories of entities: • Objects. • Relations between objects. -Service ID (key) -Billing ID -IsPrimary flag -AdminStatus -Caller ID params -Offnet PIC codes -LNP params -Announcement params -Call Feature subscriptions -Extensi... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 9.1.1 PcspService Object | The service object is the entity to which an IPCablecom 1.5 customer subscribes. It represents a phone number and all related functionality. The data model allows more than one service to be provisioned to a single endpoint. The PcspService object contains the following generic information (for complete details, see th... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 9.1.2 PcspMta Object | A Media Terminal Adapter aggregates one or more endpoints (physically contained within the MTA). It contains the following generic information (for complete details, see the PCSP XML schema): • MTA's FQDN, uniquely identifying this MTA. • MTA's NCS listener port (default: 2427). • FQDN of controlling CMTS. • Time zone ... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 9.1.3 PktcEndpoint Object | An endpoint is a physical port on a MTA/Gateway. It contains the following generic information (for complete details, see the PCSP XML schema): • EndpointId - uniquely identifies this endpoint. • Signalling protocol selection. Optionally overrides MTA setting. • Administrative status of the endpoint (disconnected, norm... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 9.1.4 PktcCMS Object | This object maintains associations between Endpoints/CMSs and Services/CMSs. It contains the following generic information (for complete details, see the PCSP XML schema): • FQDN uniquely identifying this CMS. • A single point for extension. |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 9.1.5 Inter Object Relationships | Within figure 4, the lines connecting the classes represent object "relations" (sometimes called associations). The relations depicted in figure 4 shall be supported: • Service/CMS. A typical CMS will own a block of phone numbers. • Endpoint/CMS. An endpoint requires a CMS for signalling purposes. • Service/Endpoint. A... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 9.2.1 The PCSP XML Schema | Annex A contains the PCSP XML schema. The schema defines the XML encoding syntax for the following entities (the entities shall conform to the schema): • The PcspService, PcspEndpoint, PcspMta, and PcspCms objects. These are the main data model objects. • PcspRelation. This is used to establish or teardown relations be... |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 9.2.2 Sample PCSP Entity Encodings | Sample XML encodings of all the PCSP data model entities can be found in annex B. |
8a524ffce5ea9575e878ecc3b6833ea4 | 103 161-17 | 9.2.3 Object Extensions | The PCSP XML schema permits extensions for all objects (PcspService, PcspEndpoint, PscpMta and PcspCms). Extensions are accomplished via the <Extension> element placed in each object. Most objects specify this element at the end of the main body of the object. PcspService includes an additional <Extension> element at t... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.