ETSI TS 103 161-6 V1.1.1 (2011-04)

Technical Specification
Access, Terminals, Transmission and Multiplexing (ATTM);
Integrated Broadband Cable and Television Networks;
IPCablecom 1.5;
Part 6: Event Message Specification

2 ETSI TS 103 161-6 V1.1.1 (2011-04)

Reference
DTS/ATTM-003011-6
Keywords
access, broadband, cable, IP, multimedia, PSTN
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2011.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI TS 103 161-6 V1.1.1 (2011-04)
Contents
Intellectual Property Rights . 6
Foreword . 6
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 9
3 Definitions and abbreviations . 10
3.1 Definitions . 10
3.2 Abbreviations . 10
4 Void . 11
5 Technical Overview . 11
5.1 Traditional Telephony Billing Formats . 11
5.2 Motivation for Event Based Billing . 11
5.3 Originating/Terminating Call Model to Support Customer Billing and Settlements . 12
5.4 Real-Time Billing . 12
5.5 Real-Time and Batch Event Message Delivery . 13
5.6 Terminology and Concepts. 13
5.6.1 Service . 14
5.6.2 IPCablecom Transaction . 14
5.6.3 Call. 14
5.6.4 Event Message . 14
5.6.5 Attribute . 14
5.7 Supporting Documentation . 14
6 IPCablecom objectives . 14
6.1 IPCablecom 1.5 Required Services and Capabilities. 14
6.2 Additional IPCablecom Supported Services and Capabilities . 15
6.2.1 IPCablecom Multimedia . 16
6.3 Assumptions . 16
6.4 IPCablecom Event Message Collection . 17
6.5 IPCablecom Network Elements . 17
6.5.1 Call Management Server (CMS) . 18
6.5.2 Media Gateway Controller (MGC) . 18
6.5.3 Cable Modem Termination System (CMTS) . 18
6.5.4 Record Keeping Server (RKS). 19
6.6 General IPCablecom Network Element Requirements . 20
6.7 Event Message Interfaces . 21
6.7.1 CMS to CMTS (pkt-em1*) . 21
6.7.2 CMS to MGC (pkt-em2) . 21
6.7.3 CMS to RKS (pkt-em3) . 21
6.7.4 CMTS to RKS (pkt-em4) . 22
6.7.5 MGC to RKS (pkt-em5) . 22
6.7.6 CMS to CMS (pkt-em6) . 22
6.7.7 Security Requirements . 22
7 IPCablecom services and their associated event messages . 22
7.1 IPCablecom Call Configurations . 22
7.1.1 On-Net to On-Net Call Configuration . 22
7.1.2 On-Net to Off-Net Call Configuration (Outgoing PSTN Interconnect) . 23
7.1.3 Off-Net to On-Net Service (Incoming PSTN Interconnection) . 23
7.2 Specific Services . 24
7.2.1 911 Service . 24
7.2.2 Other N11 Services (311, 411, 611) . 24
7.2.3 Toll-Free Services . 24
ETSI
4 ETSI TS 103 161-6 V1.1.1 (2011-04)
7.2.4 Operator Services . 25
7.2.5 Call Block Service . 25
7.2.6 Call Waiting Service . 25
7.2.7 Call Forwarding Service . 26
7.2.8 Return Call Service . 26
7.2.9 Repeat Call Service . 27
7.2.10 Voice Mail Service . 27
7.2.11 Message Waiting Indicator Service . 28
7.2.12 Three-Way Call Service . 28
7.2.13 Customer Originated Trace Service . 28
7.2.14 Account Code and Authorization Code Service . 28
8 IPCablecom event message structure . 29
8.1 Event Message Structure . 32
8.2 Service_Instance . 32
8.3 Service_Activation . 34
8.4 Signaling_Start . 35
8.5 Signaling_Stop . 37
8.6 Service_Deactivation . 38
8.7 Database_Query . 38
8.8 Intelligent_Peripheral_Usage_Start . 39
8.9 Intelligent_Peripheral_Usage_Stop . 39
8.10 Interconnect_Start . 39
8.11 Interconnect_Stop . 40
8.12 Call_Answer . 40
8.13 Call_Disconnect . 42
8.14 QoS_Reserve . 42
8.15 QoS_Release . 43
8.16 Time_Change . 43
8.17 QoS_Commit . 44
8.18 RTP_Connection_Parameters Event Message . 44
8.19 Media_Alive . 44
8.20 Media_Statistics . 46
9 IPCablecom event message attributes . 47
9.1 EM_Header Attribute Structure . 54
9.1.1 Billing Correlation ID (BCID) Field Structure . 56
9.1.2 Status Field Structure . 57
9.2 Call_Termination_Cause Attribute Structure . 58
9.3 Trunk Group ID Attribute Structure . 59
9.4 QoS Descriptor Attribute Structure . 59
9.5 Redirected-From-Info Attribute Structure . 60
9.6 Electronic-Surveillance-Indication Attribute Structure . 60
9.7 Attributes For Conference Parties . 61
10 Transport independent event message attribute TLV format . 62
11 IPCablecom event message file format . 62
11.1 File Bit / Byte Order . 62
11.2 File Header . 63
11.3 File Naming Convention . 63
11.3.1 Filename Components . 64
11.4 Configuration Items . 64
11.5 File EM Structure Header . 65
12 Transport Protocol . 65
12.1 RADIUS Accounting Protocol . 65
12.1.1 Reliability . 65
12.1.2 RADIUS Client Reliability . 66
12.1.3 Authentication and Confidentiality . 66
12.1.4 Standard RADIUS Attributes . 66
12.1.5 IPCablecom Extensions . 67
12.1.5.1 IPCablecom RADIUS Accounting-Request Packet Syntax . 67
12.1.5.2 Concatenation of Attributes . 68
ETSI
5 ETSI TS 103 161-6 V1.1.1 (2011-04)
12.2 File Transport Protocol (FTP) . 68
12.2.1 Required FTP Server Capabilities . 68
Annex A (normative): PCES Support . 70
A.1 Service_Instance . 71
A.2 Signaling_Start . 71
A.3 Signaling_Stop . 73
A.4 Call_Answer . 74
A.5 Call_Disconnect . 74
A.6 QoS_Reserve . 74
A.7 QoS_Release . 75
A.8 QoS_Commit . 75
A.9 Media_Report . 76
A.10 Signal_Instance . 77
A.11 Terminal_Display_Info Attribute Structure . 79
A.12 Conference_Party_Change . 80
A.13 Surveillance_Stop . 80
A.14 Redirection . 82
Annex B (informative): Bibliography . 83
History . 84

ETSI
6 ETSI TS 103 161-6 V1.1.1 (2011-04)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Access, Terminals, Transmission
and Multiplexing (ATTM).
The present document is part 6 of a multi-part deliverable covering Access, Terminals, Transmission and Multiplexing
(ATTM); Integrated Broadband Cable and Television Networks; IPCablecom 1.5, as identified below:
Part 1: "Overview";
Part 2: "Architectural framework for the delivery of time critical services over cable Television networks using
cable modems";
Part 3: "Audio Codec Requirements for the Provision of Bi-Directional Audio Service over Cable Television
Networks using Cable Modems";
Part 4: "Network Call Signalling Protocol";
Part 5: "Dynamic Quality of Service for the Provision of Real Time Services over Cable Television Networks
using Cable Modems";
Part 6: "Event Message Specification";
Part 7: "Media Terminal Adapter (MTA) Management Information Base (MIB)";
Part 8: "Network Call Signalling (NCS) MIB Requirements";
Part 9: "Security";
Part 10: "Management Information Base (MIB) Framework";
Part 11: "Media Terminal Adapter (MTA) device provisioning";
Part 12: "Management Event Mechanism";
Part 13: "Trunking Gateway Control Protocol - MGCP option";
Part 14: "Embedded MTA Analog Interface and Powering Specification";
Part 15 "Analog Trunking for PBX Specification";
Part 16: "Signalling for Call Management Server";
Part 17: "CMS Subscriber Provisioning Specification";
Part 18: "Media Terminal Adapter Extension MIB";
Part 19: "IPCablecom Audio Server Protocol Specification - MGCP option";
Part 20: "Management Event MIB Specification";
ETSI
7 ETSI TS 103 161-6 V1.1.1 (2011-04)
Part 21: "Signalling Extension MIB Specification".
NOTE 1: Additional parts may be proposed and will be added to the list in future versions.
NOTE 2: The choice of a multi-part format for this deliverable is to facilitate maintenance and future
enhancements.
ETSI
8 ETSI TS 103 161-6 V1.1.1 (2011-04)
1 Scope
The present document describes the concept of Event Messages used to collect usage for the purposes of billing within
the IPCablecom 1.5 architecture. It details the RADIUS protocol used to carry these messages, defines the various
Event Messages, lists the attributes each Event Message contains, and lists the required and optional Event Messages
associated with each type of end-user service supported.
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 are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
[1] Void.
[2] PKT-SP-SEC1.5- I02-070412: "PacketCable 1.5 Security Specification", April 12, 2007, Cable
Television Laboratories, Inc.
[3] PKT-SP-DQOS1.5-I04-090624: "PacketCable 1.5 Dynamic Quality of Service", March 29, 2007,
Cable Television Laboratories, Inc.
[4] IETF RFC 2865 (2000): "Remote Authentication Dial In User Service (RADIUS)".
[5] IETF RFC 2866 (2000): "RADIUS Accounting".
[6] Telcordia GR-1100-CORE: "BAF Generic requirements".
[7] ETSI TS 103 161-16: "Access, Terminals, Transmission and Multiplexing (ATTM) Integrated
Broadband Cable and Television Networks; IPCablecom 1.5; Part 16: Signalling for Call
Management Server".
[8] ETSI TS 101 909-20: "Digital Broadband Cable Access to the Public Telecommunications
Network; IP Multimedia Time Critical Services; Part 20: Lawful Interception".
[9] ITU-T Recommendation E.164 (2005): "The International Public Telecommunication Numbering
Plan".
[10] IETF RFC 1305 (1992): "Network Time Protocol (Version 3), Specification, Implementation and
Analysis".
[11] Void.
[12] Void.
ETSI
9 ETSI TS 103 161-6 V1.1.1 (2011-04)
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] Void.
[i.2] PKT-TR-ARCH1.5-V02-070412, PacketCable 1.5 Architecture Framework Technical Report,
April 12, 2007, Cable Television Laboratories, Inc.
[i.3] ETSI ES 201 488-2: "Access and Terminals (AT); Data Over Cable Systems; Part 2: Radio
Frequency Interface Specification".
[i.4] PKT-TR-CF-ON-ON-V03-030815: "PacketCable Architecture Call Flow Technical Report, On-
Net MTA to On-Net MTA"August 15, 2003, Cable Television Laboratories, Inc.
[i.5] PKT-TR-CF-ON-PSTN-V02-030815: "PacketCable Architecture Call Flow Technical Report, On-
Net MTA to PSTN", August 15, 2003, Cable Television Laboratories, Inc.
[i.6] PKT-TR-CF-PSTN-ON-V03-030815: "PacketCable Architecture Call Flow Technical Report,
PSTN to On-Net MTA", August 15, 2003, Cable Television Laboratories, Inc.
[i.7] GR-1298-CORE, AINGR: Switching Systems (GR-1298).
[i.8] GR-1299-CORE, AINGR: Switch - Service Control Point (SCP)/Adjunct Interface (GR-1299).
[i.9] GR-533-CORE, LSSGR: Database Services Service Switching Points - Toll-Free Service (FSD
31-01-0000), A Module of LSSGR, FR-64 (GR-533), Telcordia.
[i.10] GR-2892-CORE, Switching and Signaling Generic Requirements for Toll-Free Service Using AIN
(GR-2892), Telcordia.
[i.11] TRQ No. 2, Technical Requirements Number 2, Number Portability Switching Systems (ANSI
T1S1.6 Working Group).
[i.12] Internet Protocol Standards - STD9, October 1985, J. Postel, J. Reynolds, File Transfer Protocol
(TFP).
[i.13] ETSI TS 101 909-15: "IPCablecom Services for delivering multimedia and voice over DOCSIS
network infrastructure".
[i.14] Telcordia GR-605-CORE - LSSGR: Authorization Codes for Automatic Flexible Routing (AFR)
and Account Codes for Basic Business Group and AFR (FSD 02-02-1010) - Telecordia.
[i.15] Telcordia GR-580-CORE LSSGR: Call Forwarding Variable, Telecordia.
[i.16] Telcordia GR-586-CORE LSSGR: Call Forwarding Subfeatures, Telecordia.
[i.17] Telcordia GR-317-CORE LSSGR: Switching System Generic Requirements for Call Control
Using Integrated Services Digital Network User Part (ISDNUP).
[i.18] GR-2936-CORE Local Number Portability Capability Specification, Telecordia.
[i.19] IETF RFC 2620: "RADIUS Accounting Client MIB".
ETSI
10 ETSI TS 103 161-6 V1.1.1 (2011-04)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
attribute: Event Message Attribute is a predefined data element described by an attribute definition and attribute type
cable modem: layer two termination device that terminates the customer end of the DOCSIS connection
cable modem termination system: as used in this standard, a CMTS is a layer two termination device that terminates
the network end of the DOCSIS connection
NOTE: It is technology specific.
call: instance of user-initiated voice communication capabilities
NOTE: In traditional telephony, a call is generally considered as the establishment of connectivity directly
between two points: originating party and terminating party. In the IPCablecom context, as noted above,
the communication between the parties is "connectionless" in the traditional sense.
event message: set of data, representative of an event in the IPCablecom architecture that could be indicative of usage
of one or more billable IPCablecom capabilities
NOTE: An Event Message by itself may not be fully indicative of a customer's billable activities, but an Event
Message correlated with other Event Messages builds the basis of a billable Usage Detail Record.
IPCablecom transaction: collection of events on the IPCablecom network when delivering a service to a subscriber
NOTE: Event Messages for the same transaction are identified by one unique Billing Correlation ID (as described
in table 32). For some services, multiple transactions may be required to provide information that is
necessary to collect the total usage for the service. Multiple Event Messages may be required to track
resources for each individual service used. A transaction may persist over time.
IPCablecom: project that includes an architecture and a series of standards that enable the delivery of real-time services
over the cable television networks using cable modems
service: individual or package of communications features a subscriber may select
NOTE: A service is identified by a set of one or more "calls" or transactions that deliver the desired functionality
to the subscriber. Examples of a service include: a voice communication between two local IPCablecom
subscribers, a 3-way call, pay-per-view movie, and a web surfing session. A service may be instantaneous
or persist over time.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
Ack Acknowledgement
AMA Automated Message Accounting
BAF Bellcore AMA Format
BCID Billing Correlation ID
BSS Business Support Systems
CDR Call Detail Record
CF Collection Function
CM Cable Modem
CMS Call Management Server
CMSS Call Management Server Signalling
CMTS Cable Modem Termination System
DF Delivery Function
DLCX DeLeteConnection
DQoS Dynamic Quality-of-Service
ETSI
11 ETSI TS 103 161-6 V1.1.1 (2011-04)
DTMF Dual-tone Multi Frequency
EM Event Messages
FEID Financial Entity ID
FID Flow Identifier
IAM Initial Address message
IANA Internet Assigned Numbers Authority
IP Internet Protocol
ISUP ISDN User Part
LEA Law Enforcement Agency
LIDB Line Information Database
LNP Local Number Portability
LRN Location Routing Number
MGC Media Gateway Controller
MTA Media Terminal Adapter
NCS Network Call Signalling
NE Network Element
NTP Network Time Protocol
OSS Operations Support System
PSTN Public Switched Telephone Network
QoS Quality of Service
RKS Record-Keeping Server
RLC Release Complete Message
SDP Session Description Protocol
SFID Service Flow ID (SFID)
SS7 Signalling System No. 7
TCAP Transaction Capabilities Application Protocol
TGCP Trunking Gateway Control Protocol
VoIP Voice over IP
VSA Vendor Specific Attributes
4 Void
5 Technical Overview
5.1 Traditional Telephony Billing Formats
The telephony industry has traditionally recorded call detail transactions on telephone switches utilizing various
standard and proprietary billing formats such as Automated Message Accounting (AMA), sometimes referred to as
Bellcore AMA Format (BAF). The switches generate multiple transactions based upon the type of call the customer
placed. These transactions are correlated and packaged into a single Call Detail Record (CDR) at the end of the service
instance for billing purposes. In this traditional telephony model, services and awareness of "call state" is usually
maintained in one or at most two nodes of the network, which makes such correlation relatively straightforward. The
CDR is then delivered to the billing system for the purpose of placing a charge on the customer's account.
5.2 Motivation for Event Based Billing
The event-based approach to capturing information to be used for billing is necessary to accommodate the distributed
architecture of IPCablecom. "Call state awareness" no longer resides in one or two network elements, but is instead
spread out among many. Each network element shall be responsible for generating Event Messages for the portion of
the communication pertaining to them.
The primary motivating factor behind articulating the structure and details of these various Event Messages is to support
multi-vendor interoperability between network elements and record keeping servers. The present document defines the
Event Message syntax and in addition it describes the transport protocols.
ETSI
12 ETSI TS 103 161-6 V1.1.1 (2011-04)
Event based billing has the added advantage that it enables IPCablecom services to be billed in real-time, making the
information about billable communications available as the network equipment processes them. This allows the system
as a whole to be more responsive, allowing, for example, fraudulent behaviour to be detected sooner, saving revenue for
the provider. It also allows a more fully integrated solution, as it becomes possible for the billing system and the
network equipment to exchange information about the availability of a service as the customer is requesting that
service.
With respect to the Event Message format, there are a large number of formats in use today. The most widely used
formats carry the legacy of the traditional CDR, which is generated at the end of the call. While these formats capture
much of the information content needed to bill for IPCablecom services, bringing along their full structure would make
it difficult to support the real-time nature of certain enhanced IPCablecom services. The present document leverages the
value of the information content from the existing billing formats, augmenting that with the distributed nature of the
IPCablecom architecture.
5.3 Originating/Terminating Call Model to Support Customer
Billing and Settlements
The IPCablecom Event Messages contain sufficient per-call information to support customer billing for service as well
as settlement between IPCablecom network providers for access. The information contained in the Event Messages
supports a wide variety of billing and settlement models. IPCablecom does not mandate the use of specific billing or
settlement models as these models are defined by and based on the specific business requirements of the individual
cable operators. IPCablecom neither mandates nor precludes the use of a clearinghouse for settlements.
The IPCablecom Event Messages are based on a model where a call or service is divided into an originating half and a
terminating half. The originating CMS or MGC shall generate a unique Billing Correlation ID (BCID) to identify all
Event Messages associated with the originating half of the call. The terminating CMS or MGC shall generate a unique
BCID to identify all Event messages associated with the terminating half of the call. For each half of the call or service,
the set of IPCablecom network elements that generate Event Messages (CMS, MGC, CMTS) must provide all
necessary information required for billing and/or settlements as appropriate based on the service. The information
generated by the originating half shall be sent to the RKS supporting the originating half. The information generated by
the terminating half shall be sent to the RKS supporting the terminating half. The IPCablecom network elements also
generate Event Messages that are not associated with any call. For those cases, the network element generating the
Event Message shall generate a unique BCID for the event and send the Event Message to appropriate RKS supporting
the network element.
The IPCablecom Event Messages support billing and settlement for single-zone, intra-domain and inter-domain
architectures. In most cases, the basic set of Event Messages, their associated attributes, and the triggers for the Event
Message are identical for these three architectures. In the case of intra-domain and inter-domain architectures,
additional triggers exist for a subset of the Event Messages. The IPCablecom Event Message specification details these
requirements.
For the purposes of settlements, each IPCablecom zone is divided into one or more logical Financial Entities.
Settlements occur between Financial Entities. Each Financial Entity is identified by a Financial Entity ID (FEID).
FEIDs are pre-assigned to every CMS and MGC in the IPCablecom network. A single CMS may be assigned at most
one FEID. One or more CMSes may be assigned the same FEID.
In the Intra-domain and Inter-domain cases, the originating and terminating CMSes exchange BCIDs and FEIDs. The
originating CMS sends its BCID and FEID in the INVITE message. The terminating CMS sends its BCID and FEID in
the first response to the INVITE message which is typically the 183 SDP.
5.4 Real-Time Billing
The billing system can be regarded as a functional block of the back office Operations Support System (OSS). The
inputs to the billing system are the billing events and the outputs are the account balance and invoice. The billing
system relates the billing events to the account balance by rating the events according to the pricing structure and other
business logic.
ETSI
13 ETSI TS 103 161-6 V1.1.1 (2011-04)
Real-time Billing Systems relate the billing events to the account balance as events occur. As the billing system receives
these real-time billing events, its rating engine rates the events and immediately posts balances. Real-time Billing
Systems may be required to support advanced IPCablecom features such as pre-paid calling card, real-time fraud
prevention, and real-time credit enforcement.
The IPCablecom Event Message architecture can be used to support both real-time and batch billing systems.
5.5 Real-Time and Batch Event Message Delivery
Event Messages may be delivered to the RKS in real time as they are created. This enables support for a growing
number of services that require purchase limits such as prepaid calling cards.
As an alternative, Event Messages may be stored for some period of time and batched together before being sent to the
RKS. This approach provides a more efficient use of network resources.
5.6 Terminology and Concepts
This clause defines terminology associated with usage data as it relates to IPCablecom Services. The concept of a "call"
is well understood and used within the telecommunications marketplace today. A traditional telephony "call" involves
establishing a dedicated, circuit-switched path between the calling and called parties. Packet-switched architectures,
including IPCablecom, do not establish any such dedicated paths. To the contrary, the IPCablecom architecture assumes
a shared medium between the head-end and the customer, as compared to the dedicated loop plant in traditional
telephony; and during a traditional telephone call, as noted above, a circuit-switched "connection" is established
between the parties, whereas packet switching is inherently "connectionless." All that said, the term "call" is sufficiently
well entrenched that it will be used in the present document to refer to packet-mode voice communications between two
parties over an IPCablecom network, even though in technical terms (as will be seen) there is little resemblance to a
traditional telephone "call." It is envisioned that many new voice, video, data and other multimedia services will be
developed to take advantage of the inherent extensibility of the IPCablecom architecture. These new services, which
likely will not be derived from traditional telephony principals, will be based on the term transaction, which is more
indicative of the data flows across the IPCablecom network. The Event Message structure is designed to be flexible and
enable the addition of new IPCablecom services and features while maintaining backward compatibility with existing
applications. Event Messages may support information required for billing of DOCSIS data services, video services,
and the encapsulation of vendor specific proprietary data.
Service
Call 1 or Packet Call 2 or Packet Call n or Packet
Cable Transaction 1 Cable Transaction 2 Cable Transaction n
Event
Event Event Event
Message 2 Message 3 Message n
Message 1
Figure 1: IPCablecom Terminology
ETSI
14 ETSI TS 103 161-6 V1.1.1 (2011-04)
5.6.1 Service
A service is an individual or package of communications features a subscriber may select. A service is identified by a
set of one or more "calls" or transactions that deliver the desired functionality to the subscriber. Examples of a service
include: a voice communication between two local IPCablecom subscribers, a 3-way call, pay-per-view movie, and a
web surfing session. A service may be instantaneous or persist over time. Service in the context of IPCablecom 1.5
...