hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 6.6 General IPCablecom Network Element Requirements | This clause lists requirements placed on the IPCablecom network elements. The CMS, CMTS, and MGC shall create a security relationship with each RKS that these network elements will send Event Messages as defined in the IPCablecom Security Specification [2]. The CMS shall support multiple sets of primary and secondary R... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 6.7 Event Message Interfaces | This clause describes the interfaces between the IPCablecom network elements that are involved in the Event Messages process. It should be noted that additional requirements are imposed on these by other IPCablecom specifications and that the requirements listed in the present document are specific to Event Messages. I... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 6.7.1 CMS to CMTS (pkt-em1*) | The CMS to CMTS interface is defined by the IPCablecom DQoS protocol [3]. The CMS sends the BCID and other data as defined in table 1 to the CMTS via the DQoS GateSet message as specified in the DQoS specification [3]. |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 6.7.2 CMS to MGC (pkt-em2) | The CMS to MGC interface is defined by the IPCablecom CMSS specification [7]. The CMS and MGC exchange originating/terminating information such as BCID, FEID, etc. across this interface as defined in [7]. |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 6.7.3 CMS to RKS (pkt-em3) | The CMS to RKS interface is defined by the IPCablecom security specification [2] and also by the Event Message transport and syntax rules defined in the present document. ETSI ETSI TS 103 161-6 V1.1.1 (2011-04) 22 |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 6.7.4 CMTS to RKS (pkt-em4) | The CMTS to RKS interface is defined by the IPCablecom security specification [2] and by the Event Message transport and syntax rules defined in the present document. |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 6.7.5 MGC to RKS (pkt-em5) | The MGC to RKS interface is defined by the IPCablecom Security specification [2] and by the Event Message transport and syntax rules defined in the present document. |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 6.7.6 CMS to CMS (pkt-em6) | The CMS to CMS interface is defined by the IPCablecom CMSS specification [7]. The originating CMS and terminating CMS exchange originating/terminating information such as BCID, FEID, etc., across this interface as defined in [7]. |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 6.7.7 Security Requirements | When the network IPSec Security Associations are established, security keys shall be created and exchanged between each RKS (primary, secondary, etc.) and every CMS, CMTS, and MGC that will send Event Messages to any of those RKSes. The Event Messages are sent from the CMS, CMTS, and MGC to the RKS using one of the sup... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 7.1 IPCablecom Call Configurations | This clause describes the three basic IPCablecom 1.5 call configurations: On-Net to On-Net, On-Net to Off-Net, and Off-Net to On-Net. A required minimum set of Event Messages shall be generated for each of these three basic call configurations. If specific services are initiated along with the basic call, then refer to... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 7.1.1 On-Net to On-Net Call Configuration | A single-zone On-Net to On-Net call is within a single cable operator's network, using two different MTAs that are both connected to the same CMS. For IPCablecom 1.5, it is assumed that both the originating and terminating MTAs are using the same CMS and possibly two different CMTSes. Refer to the IPCablecom Call Flow ... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 7.1.2 On-Net to Off-Net Call Configuration (Outgoing PSTN Interconnect) | The only Off-Net interconnection supported by IPCablecom 1.5 is to the PSTN. Therefore the CMS sends all Off-Net calls to the PSTN. The Interconnect_Start Event Message identifies the type of Off-Net trunk, for example SS7/FG-D trunks, Type 1/DTMF trunks or some other type of trunks as required. The Off-Net call (i.e. ... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 7.1.3 Off-Net to On-Net Service (Incoming PSTN Interconnection) | The CMS receives calls that are incoming from other entities and establishes communications with the MTA on the cable operator's network. For IPCablecom Release 1.5, it is assumed that all incoming calls are from the PSTN. Refer to the IPCablecom Call Flow document [i.6] for a complete description of this call configur... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 7.2 Specific Services | A basic set of Event Messages shall be generated based on the type of call configuration: On-Net to On-Net, On-Net to Off-Net, Off-Net to On-Net. The basic set of Event Messages is described in clause 7.1. This clause describes additional Event Messages that shall be generated along with the basic set in order to descr... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 7.2.1 911 Service | A 911 call follows the standard On-Net to Off-Net Event Message flow described above in clause 7.1.2. 911 calls require special treatment. In IPCablecom Release 1.5, it is assumed that the cable operator sends 911 calls to the PSTN on a special trunk. The Trunk Group ID is captured in the Interconnect_Start and Interco... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 7.2.2 Other N11 Services (311, 411, 611) | These calls are identical to the 911 call both from a call flow and Event Message perspective. The determination of whether to bill or not can be performed at the Billing System based on the "Called Party Number" attribute. For example, charges for calls to 411 for directory assistance may be different than charges for... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 7.2.3 Toll-Free Services | Toll-Free Services follow the standard On-Net to Off-Net Event Message flow described above in clause 7.1.2. In IPCablecom 1.5, toll-free calls can be handled two ways: • Send all Toll-free calls to the PSTN on a special trunk. The call is treated exactly like the 911 case discussed in clause 7.2.1 in terms of Event Me... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 7.2.4 Operator Services | Operator Services follow the standard On-Net to Off-Net Event Message configuration described above in clause 7.1.2. There are no new additional Event Messages beyond those already described for the On-Net to Off-Net calls in that clause. The CMS sends that call to the designated Operator Service Provider using the PST... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 7.2.5 Call Block Service | Event Messages are generated for Call Block Service only if the CMS blocks a call. Call Blocking is supported by all of the three basic call configurations: On-Net to On-Net, On-Net to Off-Net, and Off-Net to On-Net. The CMS can block calls depending on the policies laid out by the cable operator. For example, the cabl... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 7.2.6 Call Waiting Service | At any given time the caller may be talking and will hear the call waiting tone when another call is incoming. It is understood that at some point prior to this call, the called party subscribed to call waiting service. The called party can switch back and forth between the two calls by using the flash hook. Call Waiti... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 7.2.7 Call Forwarding Service | Call Forwarding Service applies only to calls terminating On-Net as described in clauses 7.1.1 and 7.1.3. The CMS gets notification that a call needs to be completed to a specific dialled number/end device. The CMS checks its internal database and determines that the called number has subscribed to Call Forwarding, Cal... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 7.2.8 Return Call Service | This service applies only to calls originating On-Net, described in clauses 7.1.1 and 7.1.2. The CMS shall keep a register with the Calling Party Number of the last call. Return Call Service returns the last call that was made to an MTA. Upon instantiation of Return Call feature, the CMS initiates another call with the... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 7.2.9 Repeat Call Service | Repeat Call Service applies only to calls terminating On-Net as described in clauses 7.1.1 and 7.1.3. Repeat Call can be initiated when the caller dials a number and gets a busy signal. With this feature the caller dials a special pre-determined string of digits (*66 in the United States of America) which then instruct... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 7.2.10 Voice Mail Service | Voice Mail Service only applies to calls terminating On-Net, described in clauses 7.1.1 and 7.1.3. It is assumed that the voice mail server will be located Off-Net for IPCablecom 1.5. It is therefore assumed if voicemail billing is usage sensitive, that connections to the Off-Net voicemail system will be counted in the... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 7.2.11 Message Waiting Indicator Service | It is assumed that an Off-Net voicemail system is used as described in clause 7.2.10. Because it seems unreasonable for the CMS to have to place a separate call to the Off-Net system each time a voicemail subscriber goes off-hook, it is assumed that a mechanism exists which allows the Off-Net voicemail system pass the ... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 7.2.12 Three-Way Call Service | The Three-Way Call Service allows a subscriber to add a third party to an active call. Three-Way Call Service applies to the originating and terminating CMS. To operate Three-Way Call Service, the subscriber dials the first call party. While on the first call, the subscriber presses the switch hook or flash key to plac... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 7.2.13 Customer Originated Trace Service | The Customer Originated Trace Service (COT) allows subscribers to activate an immediate trace on an annoyance or nuisance call. After a nuisance call is terminated, a subscriber who wishes to trace the call picks up the handset and goes off-hook, listens to dial tone, and then dials the Customer Originated Trace activa... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 7.2.14 Account Code and Authorization Code Service | The Account Code and Authorization Code Service defines two service capabilities as one service in support of account & authorization codes. The account and authorization codes may be used by Business Support Systems (BSS) to apply various accounting & charging rules based on the codes. Account codes allow call chargin... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8 IPCablecom event message structure | This clause describes the various Event Messages, together with their associated list of attributes. Refer to clause 9 for a detailed description of the attributes described in this clause. Refer to clause 7 for a detailed description of the services and their associated Event Messages. The description of each event me... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8.1 Event Message Structure | An Event Message contains a header followed by attributes. The header is required on every Event Message. The attributes vary based on the type of service the Event Message is describing. Refer to table 38 for a description of the Event Message Header (EM_Header Attribute Structure). |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8.2 Service_Instance | This event captures the fact that a service event has happened. The Event_Time attribute in the EM_Header Structure (see table 38) shall contain the time at which the service occurred. This Event Message indicates the time at which the CMS provides an instance of a call control/feature service. For example, the time at... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8.3 Service_Activation | This event captures a subscriber activating a service. The Event_Time attribute in the EM_Header Structure (see table 38) shall contain the time when the service was activated. This Event Message indicates the time at which the CMS records an attempt to activate a service. For example, the time at which call-forwarding... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8.4 Signaling_Start | This Event Message indicates the time at which signalling starts. It is intended to capture the point at which the NE starts processing a call once a routable set of digits have been obtained from the originator. The CMS or MGC shall timestamp this message prior to digit translation. Note that the attributes contained ... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8.5 Signaling_Stop | This Event Message indicates the time at which signalling terminates. It is intended to capture the point at which the NE processes the final signalling message for the call. A Signaling_Stop message shall not be generated unless a Signaling_Start message with the same BCID has been generated for the call. A Signaling_... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8.6 Service_Deactivation | This Event Message indicates the time at which the CMS records an attempt to deactivate a service. For example, the time at which call-forwarding is deactivated by the MTA user, the time at which the call-waiting service is deactivated by the MTA user, etc. These service deactivations are typically requested via a XX ... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8.7 Database_Query | This Event Message indicates the time at which a one-time request/response transaction or database dip is completed by an intelligent peripheral (800 number database, LNP database, etc.). The CMS originating the call shall timestamp this message immediately upon a receipt of the response from the Intelligent Peripheral... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8.8 Intelligent_Peripheral_Usage_Start | Deferred. |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8.9 Intelligent_Peripheral_Usage_Stop | Deferred. |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8.10 Interconnect_Start | This Event Message indicates the time at which the start of network interconnect occurs. Only the MGC is permitted to issue this Event Message. The MGC shall timestamp this message immediately upon transmission/receipt of an IAM to/from the Signaling Gateway that communicates with the SS7 network. ETSI ETSI TS 103 161-... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8.11 Interconnect_Stop | This Event Message indicates the termination of bandwidth between the IPCablecom network and the PSTN. Only the MGC is permitted to issue this Event Message. The MGC shall timestamp this message immediately upon transmission/receipt of an RLC to/from the Signaling Gateway that communicates with the SS7 network. The MGC... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8.12 Call_Answer | This Event Message indicates that the media connection is open because answer has occurred. It is intended to capture the earliest point at which the NE can determine that the termination side has gone off-hook, resulting in a 2-way media path. ETSI ETSI TS 103 161-6 V1.1.1 (2011-04) 41 Originating CMS In the single-zo... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8.13 Call_Disconnect | This Event Message indicates the time at which the media connection is closed because the calling party has terminated the call by going on-hook, or that the destination party has gone on-hook and the called-party's call-continuation timer has expired. In the current telephony network, when the called party goes on-hoo... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8.14 QoS_Reserve | This Event Message indicates the time at which the CMTS reserves bandwidth on the IPCablecom access network. The CMTS shall also generate this event if the Reserved bandwidth changes or if the service flow is authorized by another gate (through the association of a different Gate than originally authorized the flow). T... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8.15 QoS_Release | This Event Message indicates the time at which the CMTS released its bandwidth commitment on the IPCablecom access network. The originating and terminating CMTS shall timestamp this message immediately upon: • transmission of a DSC-RSP that indicates that authorization and admission control for a DSC-REQ against an exi... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8.16 Time_Change | This event captures an instance of a time change. Whenever the (IPCablecom) clock on the network element (CMS,MGC or CMTS) is changed by more than 200 milliseconds, the network element shall generate a Time Change message. This includes time shift events (Daylight savings time), step adjustments to synchronize with the... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8.17 QoS_Commit | This Event Message indicates the time at which the CMTS commits bandwidth on the IPCablecom access network. The CMTS shall also generate this event if the Committed bandwidth changes or if the service flow is authorized by another gate (through the association of a different Gate than originally authorized the flow). T... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8.18 RTP_Connection_Parameters Event Message | Deferred. |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8.19 Media_Alive | If the IPCablecom architecture is expected to support this Media_Alive Event Message, then it is recommended that all CMS, CMTS, and MGC be pre-configured with the same Media_Alive generation time. This Event Message indicates that service is active due to the continued existence of a bearer connection. This Event Mess... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 8.20 Media_Statistics | This Event Message is generated when a gateway returns VoIP Metrics in NCS or TGCP messages. CMSs and MGCs may generate and time-stamp this message when an NCS or TGCP signalling message is received from the MTA/MG that contains VoIP Metrics data. If this optional Event Message is generated, it shall contain all of the... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 9 IPCablecom event message attributes | This clause describes the IPCablecom attributes included in the IPCablecom Event Messages. Event Messages and attributes denoted by an asterisk "*" in table 36 indicate that the message or attribute is specific to electronic surveillance Event Messages. Electronic surveillance specific Event Messages and/or attributes ... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 9.1 EM_Header Attribute Structure | Table 38 contains a detailed description of the fields in the EM_Header attribute structure. This Event Message Header attribute shall be the first attribute in every IPCablecom Event Message. ETSI ETSI TS 103 161-6 V1.1.1 (2011-04) 55 Table 38: EM_Header Attribute Structure Field Name Semantics Value Type Length Versi... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 9.1.1 Billing Correlation ID (BCID) Field Structure | Table 39 describes the Billing Correlation ID field (BCID). The RKS, or some other back office application, uses the BCID to correlate Event Messages that are generated for a single transaction. It is one of the fields in the Event Message Header attribute. The BCID is unique for each transaction in the network. All Ev... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 9.1.2 Status Field Structure | The Status field of the Event Message Header attribute is a 32-bit mask. Bit 0 is the low-order bit; the field is treated as a 4 byte unsigned integer. table 40 presents Status field description. ETSI ETSI TS 103 161-6 V1.1.1 (2011-04) 58 Table 40: Status Field Description Bit Semantics Bit Count 0-1 Error Indicator: 0... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 9.2 Call_Termination_Cause Attribute Structure | Table 41 describes the data structure of the Call_Termination_Cause attribute. It is important to note that in some cases, the Call_Termination_Cause attribute may include a Call Completion Code that may indicate a successful call completion. Table 41: Call Termination Cause Data Structure Field Name Semantics Value Ty... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 9.3 Trunk Group ID Attribute Structure | Table 42 describes the Trunk Group ID Data Structure. Table 42: Trunk Group ID Data Structure Field Name Semantics Value Type Length Trunk_Type 1 = when Non-SS7 (MF) direct trunk group is used 2 = Not Used 3 = when an SS7 signalling trunk is directly connected to IC/INC, SS7 direct trunk group number 4 = when an SS7 si... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 9.4 QoS Descriptor Attribute Structure | Table 43 describes the QoS Descriptor Data Structure. Table 43: QoS Descriptor Data Structure Field Name Semantics Value Type Length Status_Bitmask Bitmask describing structure contents. (See table 38) Bit map 4 bytes Service_Class_Name Service profile name Right justified, space padded ASCII character string 16 bytes ... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 9.5 Redirected-From-Info Attribute Structure | Table 45 describes the data structure of the Redirected-From-Info. Table 45: Data Structure of the Redirected-From-Info Attribute Field Name Semantics Value Type Length Last_Redirecting_Party E.164 [9] address of most recent redirecting party ASCII string 20 bytes Original_Called_Party E.164 [9] address of the original... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 9.6 Electronic-Surveillance-Indication Attribute Structure | Table 46 describes the data structure of the Electronic-Surveillance-Indication. The Electronic-Surveillance-Indication attribute appears in the Signaling_Start EM or Surveillance_Stop EM. This attribute creates a "chain" of DFs as calls are redirected from one endpoint to another. In such scenarios, the DF associated ... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 9.7 Attributes For Conference Parties | Table 47 describes the data structure of the attributes Communicating_Party, Joined_Part and Removed_Party. Table 47: Communicating_Party, Joined_Party and Removed_Party attributes Field Name Semantics Value Type Length Party_ID E.164 [9] formatted address specifying the number of the party. In the future other numberi... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 11 IPCablecom event message file format | The IPCablecom Event Message File Format has the following basic structure. |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 11.1 File Bit / Byte Order | Table 49 defines the Bit / Byte order for the Event Message file. For fields that span multiple bytes, the high-order bit of the field is the highest order bit of the lowest-numbered byte. Conversely, the low-order bit of a multi-byte field is the lowest-order bit of the highest-numbered byte. Table 49: Bit / Byte Orde... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 11.2 File Header | The following header shall be written at the start of a file formatted using the IPCablecom Event Message File Format: Table 50: File Header for IPCablecom Event Message File Format Field Name Semantics Length Type Format_Version Identifies the version of this file format. The value must be 1 to comply this version of ... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 11.3 File Naming Convention | Files created using the IPCablecom Event Message File Format shall use the following naming convention: "PKT- EM_yyyymmddhhmmss_pri_type_elementid_seq.bin." ETSI ETSI TS 103 161-6 V1.1.1 (2011-04) 64 |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 11.3.1 Filename Components | Table 51 describes each of the components of the filename: Table 51: Filename Components Component Semantics Type Length File_ID Identifies this file as containing IPCablecom Event Messages Literal string 'PKT-EM' 6 characters Timestamp Time at which file was opened by the network element yyyymmddhhmmss 14 characters P... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 11.4 Configuration Items | The following items shall be configurable by the IPCablecom network element creating the file: Table 52: Required Configuration Items Name Semantics Type Length Maximum File Length Maximum size of file, in bytes, to which flat file can grow before being closed for transport. Unsigned integer 4 octets Maximum Open Time ... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 11.5 File EM Structure Header | When an EM is written out to a file, each event message shall be identified by a structure header. The following identifies the File-based EM Packet Structure. Table 53: File-based EM Packet Structure Field Name Semantics Description ID Indicates an EM structure 2 byte, value of 0xAA 55. The value 0xAA 55 is chosen to ... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 12 Transport Protocol | This clause specifies the possible transport protocols used between the IPCablecom network elements that generate Event Messages (CMS, CMTS, MGC) and the Record Keeping Server (RKS). These network elements shall support RADIUS Accounting (RFC 2866 [5]) with IPCablecom extensions as defined in the present document. The ... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 12.1 RADIUS Accounting Protocol | The RADIUS Accounting protocol is a client/server protocol that consists of two message types: Accounting-Request and Accounting-Response. IPCablecom network elements that generate Event Messages are RADIUS clients that send Accounting-Request messages to the RKS. The RKS is a RADIUS server that sends Accounting-Respon... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 12.1.1 Reliability | The RADIUS messages are transported over UDP, which does not guarantee reliable delivery of messages, hence the request/response nature of the protocol (see RFC 2865 [4] for the technical justification of choosing UDP over TCP for the transport of Authentication, Authorization, and Accounting messages). ETSI ETSI TS 10... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 12.1.2 RADIUS Client Reliability | All Network Elements shall store Event Messages until they have received an Acknowledgement (Ack) from an RKS that the data was correctly received and stored, or until the maximum number of retries has been reached. Only when an Ack is received or the maximum retries reached are the NEs allowed to delete these Event Me... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 12.1.3 Authentication and Confidentiality | Refer to the IPCablecom security specification [2] for details concerning the use of IPSec to provide both authentication and confidentiality of the RADIUS messages, and the details of the correct usage of the RADIUS shared secret. |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 12.1.4 Standard RADIUS Attributes | Each RADIUS message starts with the standard RADIUS header shown in table 54. Table 54: RADIUS Message Header Field Name Semantics Field Length Code Accounting-Request = 4 Accounting-Response = 5 1 byte Identifier Used to match accounting-request and accounting-response messages. 1 byte Length Total length of RADIUS me... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 12.1.5 IPCablecom Extensions | |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 12.1.5.1 IPCablecom RADIUS Accounting-Request Packet Syntax | <<RADIUS Accounting-Request> ::== <RADIUS message Header> <RADIUS NAS-IP-Address Attribute> <RADIUS Acct-Status-Type Attribute> <IPCablecom EM List> <IPCablecom EM List> ::== <IPCablecom EM> | <IPCablecom EM List> <IPCablecom EM> <IPCablecom EM> ::== <RADIUS VSA for IPCablecom EM Header Attribute> <IPCablecom EM Attrib... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 12.1.5.2 Concatenation of Attributes | The Vendor Specific Attribute (VSA) limits the size of the attribute value to 247 bytes (see table 57). However there may be instances where the attribute value cannot fit into a single VSA, for example, the SDP attributes used in electronic surveillance. In cases where the value of an attribute is greater than 247 byt... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 12.2 File Transport Protocol (FTP) | The File Transfer Protocol (FTP) [i.12] may be used by an IPCablecom network element to transport Event Messages to the RKS. The RKS shall have FTP Server support. If this transport protocol is used, the RKS hosts an FTP server to accept files transferred by the IPCablecom network element. The IPCablecom network elemen... |
659b1078712043fc30a677ea2a11a302 | 103 161-6 | 12.2.1 Required FTP Server Capabilities | The FTP Server at the RKS shall have at minimum the following capabilities: • Minimum implementation as described in Internet Protocol Standards - STD9 [i.12] Section 5.1. • PASV Mode (passive mode) command. • Data Type I, Image (binary). • Authentication support (PASS command). • File Transfer logging. ETSI ETSI TS 10... |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 1 Scope | The present document defines the system architecture for the information exchange between different Geo-location Databases (GLDBs) enabling the operation of White Space Devices (WSDs) for the protection of the incumbent service. The architecture stems from the system requirements described in clause 7.1 of ETSI TS 102 ... |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 2 References | |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 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 reference document (including any amendments) applies. Referenced documents which ar... |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 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 reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 3 Definitions and abbreviations | |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: communication function: hardware/software module that provides communication services required by the interfaces between logical entities based on communications protocol stack database function: software/hardware that stores necessary... |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: CEPT Conférence Européenne des administrations des Postes et Télécommunications CRS Cognitive Radio System DB-SAP DataBase- Service Access Point EIRP Effective Isotropic Radiated Power GLDB Geo-Location DataBase GL-SAP GeoLocation - Service Ac... |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 4.1 Introduction | This clause describes the general WSD GLDBs architecture as well as the reference model of the logical entity, the GLDB, involved in the scope. The architecture shows the relationship of logical entities and the logical interface as detailed in the following clauses. The reference model shows the abstract architecture ... |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 4.2 Architecture | Figure 4.1 shows the instance of the G-G logical interface. The interface is used for the information exchange between GLDBs for enabling the operation of White Space Devices (WSDs) for the protection of the incumbent service. Figure 4.1: Architecture |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 4.3 Reference model of GLDB | Figure 4.2 shows an architectural view of a GLDB emphasizing the separation of GLDB into Database function, Geo- location function and G-G Interface function. A function can access the services provided by another function via a corresponding Service Access Point (SAP). A GLDB exchanges information with another GLDB by... |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 4.4 Reference model between GLDBs | Figure 4.3 shows an alternative view of the reference model for the information exchange between two GLDBs. A communication function is a hardware/software module that provides the communication services required by the interfaces between logical entities based on a communications protocol stack. ETSI ETSI TS 103 143 V... |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 5 Reference Points | |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 5.1 Reference point: Logical interface between GLDBs | Figure 5.1: Reference point for information exchange between GLDBs Figure 5.1 shows the reference point between GLDBs which is the G-G logical interface between the GLDBs for enabling the operation of White Space Devices (WSDs) for the protection of the incumbent service. Specifically, the reference point enables one G... |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 5.2 Reference point requirements | The following requirements do not mandate that GLDB implements any specific calculation methods. • The reference point shall support information exchange between GLDB A and GLDB B to allow GLDB A to discover its affecting/neighbouring GLDB B. • The reference point shall support information exchange between GLDB A and G... |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 6.1 Basic Procedures | |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 6.1.1 Incumbents information sharing procedure | Subject to regulatory agreements, a GLDB can send the information related to its registered incumbents to other GLDBs. This procedure populates the incumbent's information among GLDBs so that each GLDB can determine the available channels of CRSs independently of other GLDBs and protect the incumbents registered in dif... |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 6.1.2 Victim GLDB discovery procedure | Before providing information of available channels to a CRS, the managing GLDB shall check whether the use of such available channels by the CRS brings interference to incumbents registered in other GLDBs. To this end, the managing GLDB sends a "victim discovery request" to a list of potential victim GLDBs. This list o... |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 6.1.3 CRS spectrum usage modification procedure | Once a GLDB is found to be a victim GLDB of the querying GLDB, the operating parameters for available channels of the CRS managed by the querying GLDB shall be modified. The modification can include changes on the available frequency bands, maximum permitted EIRP of certain frequency band and spectrum validity time. Th... |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 6.1.4 CRS Operating Parameters checking procedure | Knowing the identification numbers of the CRS and its managing GLDB, a GLDB can obtain information on the channel usage of CRSs that are managed by other GLDBs. The procedure is shown in Figure 6.6 and shall consist of the following steps: 1. The GLDB A sends a "Channel_Usage_Query" message to GLDB B including the IDs ... |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 6.1.5 Procedure of CRS channel usage registration between GLDBs | A CRS selects channels to operate on from the list of available channels provided by the GLDB. GLDB A, after receiving selected channels from a CRS under its own management, provides such information to other GLDBs such that the other GLDBs can register the CRSs ID associated with their affected incumbents. A CRS may r... |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 6.1.6 Exchange the number of CRSs over a certain region | A GLDB may need to know the number of CRSs that are managed by other GLDBs so as to calculate the maximum allowable EIRP for a given CRS over a given region. The procedure of obtaining the number of CRSs is given in Figure 6.8 below. Figure 6.8: CRS number discovery procedure The procedure shall consist of the followin... |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 6.1.7 Update the number of CRSs over a certain region | A GLDB may need to update the number of CRSs that are managed by other GLDBs so as to calculate the maximum allowable EIRP for a given CRS over a given region. The procedure is given in Figure 6.9 below. ETSI ETSI TS 103 143 V1.1.1 (2015-01) 15 Figure 6.9: CRS number update procedure The update procedure shall consist ... |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 6.1.8 Sequence of exchange the number of CRSs over a certain region | The procedures described in clause 6.1.6 and clause 6.1.7 are combined as shown in Figure 6.10 below. ETSI ETSI TS 103 143 V1.1.1 (2015-01) 16 Figure 6.10: Complete procedure for the updating of CRSs over a certain region 1. The GLDB A obtains the total number of CRS with the procedure described in clause 6.1.6. 2. The... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.