hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
4b865607874b1644b476b1f82e62a1b7 | 103 146-3 | 8.5 Class Definitions for Interface | Each interface class related to URAI can be defined using the template presented in clause 6.2 and in accordance with the UML diagram of figure 8.1 which specifies the interface classes related to URAI. Tables 8.1 to 8.3 specify all the operations related to the three interface classes above described. Table 8.4: Radio... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 1 Scope | The present document defines an information model and protocol for reconfigurable radio frequency interface for reconfigurable mobile devices. The work will be based on the Use Cases defined in ETSI TR 102 944 [i.1], on the system requirements defined in ETSI EN 302 969 [1] and on the radio reconfiguration related arch... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 2 References | |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 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... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 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... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 3 Definitions and abbreviations | |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Application Processor (AP): part of mobile device hardware working under OS control and on which User Applications, among others, are executed channel: designated part of the information transfer capability having specified characteris... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACK Acknowledge ASIC Application Specific Integrated Circuit ASN Abstract Syntax Notation ASN.1 Abstract Syntax Notation One BBIC BaseBand Integrated Circuit BLER Block Error Rate CSL Communication Services Layer EU European Union MD Mobile De... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 4 Introduction | A reconfigurable MD is capable of running multiple radios simultaneously and of changing the set of radios by loading new Radio Application Package (RAP). All Radio Applications (RAs) are called Unified Radio Applications (URAs) when they exhibit a common behavior from the reconfigurable MD's point of view [1]. In orde... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 5 System Identification | |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 5.1 Radio Computer Structure | Figure 5.1 illustrates how URA and RF Transceiver interact with each other using RRFI. Figure 5.1: Interconnection between URA and RF Transceiver using RRFI for Reconfigurable MD As shown in figure 5.1, RRFI can support up to 5 kinds of services depending on the applicable MDRC [1]. Note that a Reconfigurable Mobile De... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 5.2 URA | RAs need to be subject to a common reconfiguration, multiradio execution and resource sharing strategy framework (depending on the concerned MDRC). Since all RAs exhibit a common behaviour from the reconfigurable MD perspective, those RAs are called URAs [i.8]. |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 5.3 RF Transceiver | RF Transceiver, which includes transceiver chain(s), is part of the Radio Platform in Radio Computer that transforms, in Tx mode, the baseband signal to radio signal, and in Rx mode, the radio signal to baseband signal. |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 5.4 RF Interfaces | The RF Interfaces depicted in figure 5.1 denote digital interfaces which define the physical interconnections between base-band and RFIC (Radio Frequency Integrated Circuit), for example, the DigRFSM specification defining the interface between an RFIC and a BBIC (Base-Band Integrated Circuit) in a mobile device. RRFI ... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 5.5 Radio Computer RF System Requirement Mapping | The Radio Computer components above described shall support the RF system requirements shown in table 5.2 and described in clause 6.5 of ETSI EN 302 969 [1]. NOTE: The transceiver requirements defined in clauses 6.5.5, 6.5.6 and 6.5.8 of ETSI EN 302 969 [1] are not related to the RF Interface defined in the present doc... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 6 Notational Tools | |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 6.1 Notational Tool for Information Model Classes | Table 6.1 shows a template for defining information model classes [i.4]. Each information model class is defined in clause 7.2 in accordance with the template shown in table 6.1. Note that ASN.1 is used throughout the present document for abstract type definitions; however, alternative ways are possible and are not exc... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 6.2 Notational Tool for Interface Classes | Table 6.2 shows a template for defining interface classes for RRFI. Each interface class for RRFI will be defined in clause 8.7 in accordance with the template shown in table 6.2. Table 6.2: Template for defining Interface Classes Class<Class name>[(abstract class)] <Description of the class> OPERATIONS <Operation name... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 7 Information Model for Radio Computer | |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 7.1 Radio Computer | Figure 7.1 shows the UML® class diagram for Radio Computer classes related to RRFI which are required to support Software Reconfiguration. ETSI ETSI TS 103 146-2 V1.1.1 (2015-05) 13 <<interface>> IRRFI RadioComputer RCMeasurements -listOfActiveMeasurements: ActiveMeasurementsList RCConfiguration Link RCCapabilities -li... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 7.2 Class Definitions for Information Model | Each class of Radio Computer can be defined using the template presented in clause 6.1 and in accordance with the UML® diagram of figure 7.1 which specifies the relations among all the classes of Radio Computer. Radio Computer classes defined in this way are shown in table 7.1 to table 7.15 below. Table 7.1: RadioCompu... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 8 Interface Definition | |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 8.1 Interface Overview | The RRFI is complementary to other RF Interfaces, such as DigRF [i.6] which defines the data flow (mechanisms) between Base Band and RF components. In this context, the RRFI Interface proposes additions to those existing interfaces. Those additions are in particular addressing software reconfiguration requirements, suc... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 8.2 Spectrum Control Services | |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 8.2.1 Overview on Spectrum Control Services | Table 8.1 describes the services associated with the Spectrum Control. Class definition and related operations are described in clause 8.7. Table 8.1: Overview on Spectrum Control Services Spectrum Control Services Explanation Setting of Center Frequency Since the RF band to be used by a given RAT may have to be change... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 8.2.2 Messages for Spectrum Control Services | The interfaces for Spectrum Control Services are used to transmit the following messages: • From URA to RF transceiver: - Request of centre frequency set up - Request of bandwidth set up - Request of sampling rate set up - Request of getting Tx chain parameters - Request of getting Rx chain parameters • From RF transce... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 8.3 Power Control Services | |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 8.3.1 Overview on Power Control Services | Table 8.2 describes the services associated with the Power Control. Class definition and related operations are described in clause 8.7. Table 8.2: Overview on Power Control Services Power Control Services Explanation Setting of Maximum Transmit Power Since each RAT might be associated with its own maximum power level,... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 8.3.2 Messages for Power Control Services | The interfaces for Power Control Services are used to transmit the following messages: • From URA to RF transceiver: - Request of maximum power level set up for Tx chain - Request of Tx power set up per Tx antenna - Request of Rx gain set up for Rx chain • From RF transceiver to URA: - Confirmation of maximum power lev... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 8.4 Antenna Management Services | |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 8.4.1 Overview on Antenna Management Services | Table 8.3 describes the services associated with the Antenna Management. Class definition and related operations are described in clause 8.7. ETSI ETSI TS 103 146-2 V1.1.1 (2015-05) 24 Table 8.3: Overview on Antenna Management Services Antenna Management Services Explanation Selection of Antenna Port In the case of mul... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 8.4.2 Messages for Antenna Management Services | The interfaces for Antenna Management Services are used to transmit the following messages: • From URA to RF transceiver: - Request of Tx antenna port selection - Request of Rx antenna port selection • From RF transceiver to URA: - Confirmation of Tx antenna port selection - Confirmation of Rx antenna port selection - ... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 8.5 Tx/Rx Chain Control Services | |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 8.5.1 Overview on Tx/Rx Chain Control Services | Table 8.4 describes the services associated with the Chain Control. Class definition and related operations are described in clause 8.7. Table 8.4: Overview on Tx/Rx Chain Control Services Tx/Rx Chain Control Services Explanation Setting of start/stop Time for Transmission Since Tx of data stream is active for a given ... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 8.5.2 Messages for Tx/Rx Chain Control Services | The interfaces for Tx/Rx Chain Control Services are used to transmit the following messages: • From URA to RF transceiver: - Request of Tx start time set up - Request of Tx stop time set up - Request of Rx start time set up - Request of Rx stop time set up ETSI ETSI TS 103 146-2 V1.1.1 (2015-05) 25 - Request of Tx/Rx c... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 8.6 RVM Protection Services | |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 8.6.1 Overview on RVM Protection Services | Table 8.5 describes the services associated with the Radio Virtual Machine protection. Class definition and related operations are described in clause 8.7. ETSI ETSI TS 103 146-2 V1.1.1 (2015-05) 26 Table 8.5: Overview on RVM Protection Services RVM Protection Services Explanation Selection of RF Protection Class In th... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 8.6.2 Messages for RVM Protection Services | The interfaces for RVM Protection Services are used to transmit the following messages: • From URA to RF transceiver: - Request of RF protection class selection - Request of change of RF protection class - Request of RF protection class Status - Request of information on data modification by RF protection - Request of ... |
b545e18e80f7062ea1626da27abadc12 | 103 146-2 | 8.7 Class Definitions for Interface | Each interface class related to RRFI can be defined using the template presented in clause 6.2 and in accordance with the UML® diagram of figure 8.3 which specifies the interface classes related to RRFI. Tables 8.6 to 8.10 below specify all the operations related to the five interface classes above described. Table 8.6... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 1 Scope | The present document defines an information model and protocol for multiradio interface for mobile device reconfiguration. The work will be based on the Use Cases defined in TR 103 062 [i.1], TR 102 839 [i.2] and TR 102 944 [i.3], on the system requirements defined in TS 102 969 [1] and on the radio reconfiguration rel... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 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 referenced document (including any amendments) applies. Referenced documents which are... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 969 (V1.1.1): "Reconfigurable Radio Systems (RRS); Radio Reconfiguration related Requirements for Mobile Devices". [2] ETSI TS 103 095 (V1.1.1): "Reconfigurable Radio Systems (RRS); Radio Reconfiguration relate... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 2.2 Informative references | The following referenced documents arenot necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TR 103 062: "Reconfigurable Radio Systems (RRS) Use Cases and Scenarios for Software Defined Radio (SDR) Reference Architecture for Mobile Device"... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 3 Definitions and abbreviations | |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Communication Services Layer (CSL): software layer related to communication services supporting generic applications NOTE: Communication Services Layer supports generic applications like Internet access. In the present document, it con... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASN.1 Abstract Syntax Notation One BLER Block Error Rate CM Configuration Manager CSL Communication Services Layer FC Flow Controller ID Identification MD Moblile Device MPM Mobility Policy Manager MRC Multiradio Controller MURI Multiradio Int... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 4 System Identification | Multiradio Interface (MURI) is an interface to be defined between Communication Services Layer (CSL) and Radio Control Framework (RCF) [2] in the present document. Figure 4.1 illustrates how CSL and RCF interact with each other using MURI. As shown in figure 4.1, MURI supports 3 kinds of services, i.e. Administrative S... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 4.1 Communication Services Layer | CSL is a software layer that is related to communication services supporting generic applications like, for example, Internet access. CSL includes the following functional components [2]: Administrator, Mobility Policy Manager (MPM), Networking stack and Monitor. Mobile Device (MD) user can control and manage each Radi... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 4.2 Radio Control Framework | RCF is a control framework which, as a part of the Operating System (OS), extends the OS capabilities in terms of radio resource management. Any appropriate OS empowered by RCF, is referred to as Radio Operating System (ROS). RCF provides functionalities of processing instructions for the CSL to manage the URA. RCF con... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 4.3 Radio Computer Interfaces | RadioComputer <<interface>> IMURI <<interface>> IURAI <<interface>> IRRFI <<interface>> IRPI Figure 4.2: UML® class diagram for Radio Computer Interfaces Figure 4.2 illustrates UML® (Unified Modeling LanguageTM) class diagram for Radio Computer Interfaces. As shown in figure 4.2, Radio Computer shall realize 4 interfac... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 5 Notational Tools | |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 5.1 Notational Tool for Information Model Classes | Table 5.1 shows a template for defining information model classes [i.4]. Each information model class will be defined in clause 6.2 in accordance with the template shown in table 5.1. Although neither "DERIVED FROM" nor "SUPPORTED EVENTS" are used in present document, these are presented in table 5.1 to maintain compat... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 5.2 Notational Tool for Interface Classes | Table 5.2 shows a template for defining interface classes for MURI. Each interface class for MURI will be defined in clause 7.5 in accordance with the template shown in table 5.2. ETSI ETSI TS 103 146-1 V1.1.1 (2013-11) 10 Table 5.2: Template for defining Interface Classes Class<Class name>[(abstract class)] <Descripti... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 6 Information Model for Radio Computer | |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 6.1 Information Model Classes | In this clause, each class of Radio Computer is defined using the template presented in clause 5.1. In order to define each class of Radio Computer, UML® class diagram for all the Radio Computer classes related to MURI should be determined [i.4]. Figure 6.1 illustrates the UML® class diagram for Radio Computer classes ... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 6.2 Class Definitions for Information Model | Each class of Radio Computer can be defined using the template presented in clause 5.1 in accordance with the UML® diagram of figure 6.1 which specifies relations among all the classes of Radio Computer. Radio Computer classes are defined as follows: Table 6.1: RadioComputerClass Class RadioComputer This class describe... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 7 Interface Definition | |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 7.1 Interface Overview | Figure 7.1: Multiradio interface (MURI) Figure 7.1 illustrates the relationship among RadioComputer, RCUser, and MURI. As shown in figure 7.1, MURI shall be the provided interface to Radio Computer, while the MURI shall be the required interface to RCUser. Figure 7.2 illustrates a UML® diagram for MURI. As shown in fig... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 7.2 Administrative Services | |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 7.2.1 Interfaces for Administrative Services | Figure 7.3 illustrates interfaces supporting Administrative Services. Figure 7.3: IAdministrativeServices interface Administrative Services are responsible for operations with RA as follows: • Installation/Uninstallation of RA from Radio Package; • Creating/Deleting instance of RA; • Providing information about the RA ... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 7.2.2 Messages for Administrative Services | Interfaces for Administrative Services are used to transmit the following messages: • From CSL to RCF: - Request of installation/uninstallation of RA - Request of creating/deleting instance of RA - Request of getting/configuring parameters of RA - Request of installed/instantiated/activated RA(s) list • From RCF to CSL... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 7.3 Access Control Services | |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 7.3.1 Interfaces for Access Control Services | Figure 7.4 illustrates interfaces supporting Access Control Services. <<interface>> Figure 7.4: IAccessControlServices interface Access Control Services include the following operations: • activation/deactivation of RA; • monitoring radio environment and Radio Computer capabilities; • providing information about the RA... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 7.3.2 Messages for Access Control Services | Interfaces for Access Control Services are used to transmit the following messages: • From CSL to RCF: - Request of activation/deactivation of RA - Request of installed/instantiated/activated RA(s) list - Request of measurements for radio environment - Request of measurements for MD capabilities - Request of creating d... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 7.4 Data Flow Services | |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 7.4.1 Interfaces for Data Flow Services | Figure 7.5 illustrates interfaces supporting Data Flow Services. Figure 7.5: IDataFlowServices interface Data Flow Services provide means for sending or receiving user data. Data Flow Services support the following operations: • sendingUser Data; • receivingUser Data. ETSI ETSI TS 103 146-1 V1.1.1 (2013-11) 21 |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 7.4.2 Messages for Data Flow Services | Interfaces for Data Flow Services are used to transmit the following messages: • From CSL to RCF: - Request of transfer user data • From RCF to CSL: - Confirmation of transfer user data - Failure of transfer user data |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 7.5 Class Definitions for Interface | Each interface class related to MURI can be defined using the template presented in clause 5.2 in accordance with the UML® diagram of figure 7.2 which specifies the interface classes related to MURI. The interface classes are specified as follows: Table 7.1: IAdministrativeServices Class ClassIAdministrativeServices Th... |
71f6f5e8b5df01652b7b4d799c643217 | 103 146-1 | 8 Conclusion | In the present document, we have suggested the information model and protocol for multiradio interface for MD reconfiguration. • System Identification: - Detailed substances of system identification are given in clause 4. • Notational Tools: - Detailed substances of notational tool for defining both information model c... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 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... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 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... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 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... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 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... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 3 Definitions and abbreviations | |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 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 ter... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 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 ... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 4 Void | |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 5 Technical Overview | |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 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 c... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 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 M... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 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... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 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 a... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 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 par... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 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-w... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 5.6.2 IPCablecom Transaction | A IPCablecom transaction is a collection of events on the IPCablecom network when delivering a service to a subscriber. Event Messages for the same transaction are identified by one unique BCID (as described in table 39). For some services, multiple transactions may be required to provide information that is necessary ... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 5.6.3 Call | A call is an instance of user-initiated voice communication capabilities. 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 i... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 5.6.4 Event Message | An Event Message is a set of data, representative of an event in the IPCablecom architecture that could be indicative of usage of one or more billable IPCablecom capabilities. An Event Message by itself may not be fully indicative of a customer's billable activities, but an Event Message correlated with other Event Mes... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 5.6.5 Attribute | An Event Message Attribute is a predefined data element described by an attribute definition and attribute type. |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 5.7 Supporting Documentation | A number of documents and specifications describe the IPCablecom project. The IPCablecom Architecture Framework [i.2] is the starting point for understanding the IPCablecom project and the various IPCablecom Interface Specifications, technical reports and other IPCablecom documents. |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 6 IPCablecom objectives | |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 6.1 IPCablecom 1.5 Required Services and Capabilities | IPCablecom 1.5 provides basic voice capabilities and therefore shall support Event Messages for the following services. These services are described in more detail in clause 7 of the present document: • Interconnection with circuit-switched PSTN. • Support for emergency services. • n11 assume outside directory service.... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 6.2 Additional IPCablecom Supported Services and Capabilities | The following represents a list of possible additional IPCablecom services that may be supported. The list, though meant as a rough guideline, is by no means comprehensive, and it is expected that as the scope of services grows, this list will be expanded. These services are not defined in more detail in the present do... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 6.2.1 IPCablecom Multimedia | The IPCablecom Multimedia specification defines a service delivery framework that provides general-purpose QoS, event-based accounting, and security functionality founded upon the mechanisms defined in IPCablecom 1.5. It is defined in [i.13]. The IPCablecom Multimedia specification extends the present document and the ... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 6.3 Assumptions | The following assumptions have been made which apply to the entire document: • IPCablecom 1.5 does not specify the interface between an RKS and a billing system. • All IP based Intelligent Peripherals (these include Announcement Servers, for example) will be connected to the originating CMS or MGC. • IPCablecom 1.5 doe... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 6.4 IPCablecom Event Message Collection | Event Message collection occurs as follows: when trigger events occur [such as call signalling starts, activation of QoS service resources, call signalling stops, etc.], the relevant IPCablecom network element generates an Event Message. These messages may be sent immediately to the RKS, or a group of messages may be c... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 6.5 IPCablecom Network Elements | The IPCablecom architecture supports a system capable of creating, collecting, and delivering usage data from a subset of IPCablecom network elements to a cable operator's back office applications. Trusted IPCablecom 1.5 network elements that create Event Messages include the Call Management Server (CMS) and Cable Mode... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 6.5.1 Call Management Server (CMS) | The Call Management Server (CMS) provides signalling services necessary for voice communications. The primary purpose of the CMS is to establish standard "calls," as that term is used in the IPCablecom context. The media servers also provide support services for the media streams such as conference mixing bridges and a... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 6.5.2 Media Gateway Controller (MGC) | The Media Gateway Controller (MGC) is the overall controller function of the PSTN gateway. It receives, mediates, and routes call signalling information between the IPCablecom and PSTN domains and it maintains and controls the overall call state for all calls connecting to and from the PSTN. It controls the Media Gatew... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 6.5.3 Cable Modem Termination System (CMTS) | The Cable Modem Termination System terminates the connection from the cable modem on the customer premises into the IPCablecom network. The CMTS generates QoS Event Messages. QoS event messages are generated individually for both upstream and downstream bandwidth. The CMTS shall generate the appropriate Event Messages ... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 6.5.4 Record Keeping Server (RKS) | The Record Keeping Server (RKS) is a trusted network element function. In many cases, for simplicity reasons, the RKS is depicted in the present document as a separate standalone element, but the present document does not preclude a CMS, Billing System, or other application from performing the RKS functionality. The RK... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.