hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.2.4 Committed-Recovery | In the Committed state the flow associated with the Gate is active. If the CMTS detects that the flow is unused for a time in excess of the T3 timer, the CMTS notifies the PS (who notifies the AM) that the service-flow associated with the gate has been unused, starts the T4 timer and transitions the Gate to the Committ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.3 COPS Profile for IPCablecom Multimedia | As defined earlier, admission control involves the process of managing QoS resource requests based on administrative policies and available resources. High-level operational modules associated with this process are depicted in [15]. Under this model administrative policies are stored in a policy database and controlled... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4 Gate Control Protocol Message Formats | Protocol messages for Gate Control shall be transported within the COPS protocol messages. The PDP and PEP shall establish and use a TCP connection for communication, and utilize the mechanisms specified in [16] to secure the communication path. |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.1 COPS Common Message Format | Each COPS message consists of the COPS header followed by a number of typed objects. The Application Manager, Policy Server and CMTS shall use the COPS Common Message format as defined below as the message format for all message exchanges. In the object specifications that follow, each row represents a 4-byte word as a... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2 Additional COPS Objects for Gate Control | As with the COPS-PR and COPS-RSVP profiles, the IPCablecom Client-Type defines a number of additional object formats. These objects shall be placed inside a Decision object, C-Num = 6, C-Type = 4 (Client Specific Decision Data) when carried from PDP to PEP in a Decision message. They shall also be placed in a ClientSI ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.1 TransactionID | TransactionID is a 2-byte unsigned integer quantity, which contains a token that is used by the Application Manager to match responses from the Policy Server and by the Policy Server to match responses from the CMTS to the previous requests. The TransactionID shall also contain the command type that identifies the acti... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.2 AMID | AMID, the Application Manager ID, consists of two fields, the Application Manager Tag and Application Type. The Application Manager Tag is a 2-byte unsigned integer value which identifies the Application Manager responsible for handling the session. The Application Type is a 2-byte unsigned integer value which identifi... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.3 SubscriberID | There are two different versions of the SubscriberID object which differ in the IP version of the addresses that they contain. The simply named SubscriberID object contains a 4-byte value giving the IPv4 address (represented as four concatenated octet values) of the subscriber for this service request. The IPv6Subscrib... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.4 GateID | GateID is a 4-byte unsigned integer value which identifies the Gate referenced in the command message, or referenced by the CMTS for a response message. The CMTS shall ensure the GateID is unique. If the CMTS also supports IPCablecom 1.x, the GateID shall not duplicate a IPCablecom 1.x GateID currently in use. The Gate... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.5 GateSpec | GateSpec defines a specific set of attributes associated with a Gate. The GateSpec object shall conform to the following format. Length = 16 S-Num = 5 S-Type = 1 Flags DSCP/TOS Field DSCP/TOS Mask SessionClassID Timer T1 Timer T2 Timer T3 Timer T4 Flag is a 1-byte bit-field value defined as follows: Bit 0: Direction bi... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.6 Classifiers | There are three types of classifiers supported in the present document. An Application Manager shall use either the Classifier, Extended Classifier, or IPv6 Classifier objects in accordance with clause 6.1.5. The Classifier object specifies the packet matching rules associated with a Gate. As defined in clauses 6.4.3.1... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.7 Traffic Profiles | There are four different ways to express a traffic profile. The traffic profile can be expressed via a FlowSpec, a DOCSIS Service Class Name, DOCSIS-specific parameters or Upstream Drop. The four methods are distinguished via a different S-Type value in the Traffic Profile (S-Num = 7) object. S-Type of 1 indicates the ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.7.1 Flow Spec | The FlowSpec object defines the Traffic Profile associated with a Gate through an RSVP-like parameterization scheme. The mapping of these parameters to DOCSIS parameters is specified in clause 8. The FlowSpec object shall conform to the following specification. ETSI ETSI TS 102 879 V1.1.1 (2010-06) 51 Length = 36 or 64... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.7.2 DOCSIS Service Class Name | The DOCSIS Service Class Name object defines the preconfigured Service Class Name associated with a Gate. The DOCSIS Service Class Name object shall conform to the following specification. Length = 12 or 16 or 20 or 24 S-Num = 7 S-Type = 2 Envelope Reserved Reserved Reserved Service Class Name The Service Class Name is... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.7.3 Best Effort Service | The Best Effort object defines the Traffic Profile associated with a Gate through an upstream DOCSIS-specific parameterization scheme. The Best Effort object shall conform to the following specification. Length = 44, 80 or 116 S-Num = 7 S-Type = 3 Envelope Reserved Reserved Reserved Authorized Envelope Traffic Priority... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.7.4 Non-Real-Time Polling Service | The Non-Real Time Polling object defines the Traffic Profile associated with an upstream Gate through a DOCSIS-specific parameterization scheme. The Non-Real Time Polling object shall conform to the following specification. Length = 48, 88 or 128 S-Num = 7 S-Type = 4 Envelope Reserved Reserved Reserved Authorized Envel... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.7.5 Real-Time Polling Service | The Real-Time Polling object defines the Traffic Profile associated with an upstream Gate through a DOCSIS-specific parameterization scheme. The Real-Time Polling object shall conform to the following specification. ETSI ETSI TS 102 879 V1.1.1 (2010-06) 55 Length = 48, 88 or 128 S-Num = 7 S-Type = 5 Envelope Reserved R... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.7.6 Unsolicited Grant Service | The Unsolicited Grant object defines the Traffic Profile associated with an upstream Gate through a DOCSIS-specific parameterization scheme. The Unsolicited Grant object shall conform to the following specification. Length = 36, 64 or 92 S-Num = 7 S-Type = 6 Envelope Reserved Reserved Reserved Authorized Envelope Reque... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.7.7 Unsolicited Grant Service with Activity Detection | The Unsolicited Grant with Activity Detection object defines the Traffic Profile associated with an upstream Gate through a DOCSIS-specific parameterization scheme. The Unsolicited Grant with Activity Detection object shall conform to the following specification. Length = 44, 80 or 116 S-Num = 7 S-Type = 7 Envelope Res... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.7.8 Downstream Service | The Downstream object defines the Traffic Profile associated with a Gate through a downstream DOCSIS-specific parameterization scheme. The Downstream object shall conform to the following specification. Length = 48, 88 or 128 S-Num = 7 S-Type = 8 Envelope Reserved Reserved Reserved Authorized Envelope Traffic Priority ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.7.9 Upstream Drop | The Upstream Drop object defines the Traffic Profile associated to a Gate with a null service flow. The Upstream Drop object shall conform to the following specification. Length = 8 S-Num = 7 S-Type = 9 Envelope = 7 Reserved Reserved Reserved ETSI ETSI TS 102 879 V1.1.1 (2010-06) 61 DOCSIS 3.0 [1] clause 7.5.1.2.2 deta... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.8 Event Generation Info | The Event Generation Info object contains all the information necessary to support the event messages as specified and required in [14]. The IPv4 Event Generation Info object is used when the RKS Addresses are specified in IPv4 format, whereas the IPv6 Event Generation Info object is used when the RKS Addresses are spe... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.9 Volume-Based Usage Limit | The Volume-Based Usage Limit object specifies the amount of data that can be transmitted over this Gate before meeting a volume threshold. This object is OPTIONAL in every Gate-Set message. It shall be provided by the PEP in Gate-Info-Ack messages if it has been provided by the PDP in any Gate-Set message. It shall not... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.10 Time-Based Usage Limit | The Time-Based Usage Limit object specifies the amount of time a Gate can remain committed before meeting a time limit threshold. The Time-Based Usage Limit object shall conform to the following specification. Length = 8 S-Num = 10 S-Type = 1 Time Limit ETSI ETSI TS 102 879 V1.1.1 (2010-06) 63 Time Limit is a 4-byte un... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.11 Opaque Data | The Opaque Data object contains information that a Policy Server or Application Manager may store on a CMTS that remains opaque to the CMTS. The opaque data object is OPTIONAL in every Gate-Set message. It shall not be used in any other messages issued by the PDP to the PEP. If the object has been defined by a successf... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.12 Gate Time Info | The Gate Time Info object contains the total amount of time the Gate has been in the Committed and Committed Recovery states. This counter shall be stopped upon the Gate transitioning out of the Committed or Committed Recovery states to either the Reserved state or Authorized state. If the Gate subsequently transitions... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.13 Gate Usage Info | The Gate Usage Info object contains a counter indicating the number of kilobytes transmitted over this Gate. The Gate Usage Info object shall conform to the following specification. Length = 12 S-Num = 13 S-Type = 1 Octet Count Octet Count is a 8-byte unsigned integer which represents the number of bytes (counted from ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.14 IPCablecom Error | The IPCablecom Error object contains information on the type of error that has occurred. The error is generated in response to a Gate Control command and is contained in Gate-Set-Err, Gate-Info-Err and Gate-Delete-Err messages. The IPCablecom Error object shall conform to the following specification. Length = 8 S-Num =... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.15 Gate State | The information in the Gate State object reflects the current state of the Gate. The CMTS shall include the Gate State object in any unsolicited messages that it sends to the Policy Server. The Policy Server may use this information to report state to the Application Manager, or for enforcing complex rules that might r... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.16 Version Info | The Version Info object is used to enable Multimedia applications to adapt their interactions with other devices so that interoperability can be achieved between products supporting different protocol versions. Both the Major Version Number and the Minor Version Number are 2 byte unsigned integers. Both the PDP and the... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.17 PSID | PSID is a 4-byte unsigned integer value which uniquely identifies a Policy Server. The PSID number space is a subset of the AMID number space; therefore the PSID for a policy server shall also be unique among all the AMIDs that have been provisioned for Application Managers. The object shall be formatted as follows. Le... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.18 Synch Options | The Synch Options object is used to specify the details of how synchronization should be performed when a PDP issues a synchronization request. The object shall be formatted as follows. Length = 8 S-Num = 18 S-Type = 1 Reserved Report Type Synch Type Report Type is a 1-byte unsigned integer used to indicate the type of... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.19 Msg Receipt Key | The Msg Receipt Key is a 32-bit unsigned integer value, and is assigned by the PEP. This object may be included in any message sent from a PEP to a PDP and when it is present it is an indication that the PEP is requesting that the PDP confirms that it received the message. There are no constraints on how the PEP assign... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.20 UserID | The UserID is a UTF-8 string value that identifies the user associated with a gate. This object is optional, and may be associated with a gate by an AM when the gate is originally created. If the length (in bytes) of the string value is not a multiple of 4, then the value shall be padded with null bytes until the lengt... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.2.21 SharedResourceID | The Shared Resource Identifier is a 4-byte unsigned integer value assigned by the CMTS for Multicast Gate requests. There are no constraints, other than being locally unique within the scope of the CMTS, on how the CMTS assigns this value, and for that reason the PS and/or AM should not make any assumptions about how i... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.3 Gate Control Messages | There are two separate profiles for Gate Control messages: one for messages exchanged between the Application Manager and the Policy Server, and one for messages between the Policy Server and the CMTS. While similar, these two profiles do exhibit some minor differences. The following statements describe the PCMM messag... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.3.1 Profile for Application Manager to Policy Server Interface | Messages that perform gate control between the Application Manager and Policy Server are defined and shall be formatted as follows. Note that messages from the Application Manager to Policy Server shall be formatted as COPS Decision messages, and messages from Policy Server to Application Manager shall be formatted as ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.4.3.2 Profile for Policy Server to CMTS Interface | Messages that perform Gate Control between the Policy Server and CMTS are defined and shall be formatted as follows. Note that messages from Policy Server to CMTS shall be formatted as COPS Decision messages, and messages from CMTS to Policy Server shall be formatted as COPS Report-State messages. <Client Open> = <COPS... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5 Gate Control Protocol Operation | |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.1 Initialization Sequence | When a PEP (Policy Server or CMTS) boots, it shall listen for incoming COPS connections on the IANA-assigned TCP port number 3918. Any Application Manager or Policy Server (PDP) with a need to contact a PEP shall initiate a TCP connection to the PEP on that port. It is expected that multiple Application Managers will e... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.2 Operation Sequence | The protocol between the PDP and PEP is used for purposes of resource control and resource allocation policy. The Application Manager requests policy decisions from the Policy Server, and the Policy Server authorizes the requests and installs them on the CMTS for enforcement through the use of Gates. Messages that may ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.3 Procedures for Validating Resource Envelopes | The set of service flow characteristics that are important for the purposes of providing enhanced Quality of Service is known as the envelope. A IPCablecom Multimedia Gate contains up to three envelopes - one that indicates the Authorized resources, one that indicates the Reserved resources, and one that indicates the ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.3.1 Flow Spec | In table 3, the second column indicates the operation that should be used to compare a parameter of A's envelope to a corresponding parameter in B's envelope. In other words, envelope A fits within envelope B if each of A's parameters meets the criteria specified in the table. Table 3: Envelope Comparison Rules Paramet... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.3.2 DOCSIS Service Class Name | For traffic profiles in the form of a Service Class Name, the Service Class Name string shall exactly match the preexisting Service Class Name on the CMTS. No envelope comparison is necessary as all three envelopes must share the same envelope parameters. |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.3.3 DOCSIS Service Flow Parameters | |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.3.3.1 Upstream Encodings | In table 4, the second column indicates the operation that should be used to compare a parameter of A's envelope to a corresponding parameter in B's envelope. In other words, envelope A fits within envelope B if each of A's parameters meets the criteria specified in the table. ETSI ETSI TS 102 879 V1.1.1 (2010-06) 74 T... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.3.3.2 Downstream Encodings | In table 5, the second column indicates the operation that should be used to compare a parameter of A's envelope to a corresponding parameter in B's envelope. In other words, envelope A fits within envelope B if each of A's parameters meets the criteria specified in the table. Table 5: Downstream Envelope Comparison Pa... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.3.4 Upstream Drop | Gate-Set commands with a traffic profile of type Upstream Drop do not contain envelope attributes. As a result, the CMTS need not perform resource envelope validations. |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.4 Procedures for Authorizing Resources through a Gate | The Gate-Set message may be sent by the PDP to the PEP to initialize or modify the operational parameters of a Gates. Figure 7 provides an example of Gate-Set signalling. NOTE: As an example, the "Start Session" message can be used to indicate to the Client that the resources have been authorized. ETSI ETSI TS 102 879 ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.4.1 Procedures for Authorizing Multicast Gates | In addition to the requirements specified in clause 6.5.4 above, the following requirements are added for Multicast Gate requests. Upon receipt of a Gate-Set message without a GateID and with a classifier specifying a destination IP address of type Multicast, the CMTS shall determine if this Multicast Gate request can ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.5 Procedures for Querying a Gate | When a Policy Server or Application Manager wishes to query the current parameter settings of a Gate, it sends to the CMTS a Gate-Info message. The CMTS shall respond to a Gate-Info message with either a Gate-Info-Ack, indicating success, or a Gate-Info-Err, indicating failure. A Gate-Info-Ack shall contain all the cur... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.6 Procedures for Modifying a Gate | To modify the Traffic Profile associated with an existing Gate, an Application Manager may send a Gate-Set message with the GateID of the Gate to be modified and the new Traffic Profile. If the Gate-Set fails the Policy Server's checks, the Policy Server shall send a Gate-Set-Err to the Application Manager and shall no... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.6.1 Procedures for Modification of Multicast Gates | If a Gate modification request for a Multicast Gate changes the resource requested by the Gate to be another shared or unshared resource, the CMTS shall re-apply admission control logic for the newly requested resource, as it would during an initial Gate creation request, see clause 6.5.4.1. The CMTS may refuse to allo... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.7 Procedures for Supporting Usage Limits | The Application Manager, Policy Server and CMTS all have a role in enforcing Usage Limits. There are subtle differences between Time-Based and Volume-Based Limits so each of these is described separately. The Volume-Based and Time-Based Usage Limits are relative to the Gate-Usage-Info and Gate-Time-Info values respecti... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.7.1 Procedures For Supporting Volume-Based Usage Limits | Since the CMTS is the only trusted IPCablecom Multimedia device in the packet path, it is the only device capable of accurately tracking the usage of individual Gates. Thus, the CMTS shall track the usage of all Gates regardless of whether or not they have an associated Volume-Based Usage Limit. The CMTS may track the ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.7.2 Procedures For Supporting Time-Based Usage Limits | While it is a desirable design goal to keep the Volume-Based and Time-Based Usage Limit procedures as similar as possible, the number of CMTS interrupts required to support enforcement of Time-Based Usage Limits by the CMTS makes this impractical. Thus, the Application Manager shall enforce the Time-Based Usage Limit o... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.7.3 Resource and Error Recovery | While it is required that the Application Manager perform one of several actions when a Gate's Usage Limit has been reached, there is always the possibility that the Application Manager will not respond appropriately. In this case, the RKS will still be recording the usage of this Gate so this activity will still be bi... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.7.4 Tracking Time-Based and Volume-Based Usage Limits | IPCablecom Multimedia Gates can be committed and uncommitted multiple times (to support, for example, a "pause" function on a game or streaming media). Since a subscriber cannot transmit/receive data while the Gate is not a committed state, these periods should not be counted against them. For Volume-Based Limits this ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.8 Procedures for Deleting a Gate | Normally, when a Multimedia session ends, the Application Manager tells the Policy Server that the session has ended, and the Policy Server in turn instructs the CMTS to remove the Gate via a Gate-Delete message. The CMTS shall respond to a Gate-Delete message with a Gate-Delete-Ack, indicating success, or a Gate-Delet... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.8.1 Procedures for Deleting Multicast Gates | When a Multicast Gate is deleted, the CMTS shall delete all information and state associated with the deleted gate and respond with a Gate-Delete-Ack. If the assigned SharedResourceID is still being used by other Multicast Gates, the CMTS shall preserve the SharedResourceID and the resource it references. If the delete... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.9 Procedure for Committing a Gate | In Scenario 1, the Policy Server is responsible for committing a Gate through a Traffic Profile containing a Committed Envelope. The CMTS commits the Gate and activates the DOCSIS Service Flow using the parameters passed down to it by the Policy Server. |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.9.1 Procedure for Committing a Multicast Gate | When a Multicast Gate is committed, the CMTS should treat the commit operation as a "JoinMulticastSession" for the multicast session specified in the Gate. For more information regarding handling of a "JoinMulticastSession" please refer to [1]. |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.10 Termination Sequence | When the PEP is shutting down its TCP connection to the PDP, it may first send a Delete-Request-State (DRQ) message (including the Handle object used in the initial Request message). If the PEP chooses to send the DRQ message, the PEP shall use COPS reason code 4 (Tear). The PEP may follow that with a Client-Close mess... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.11 Procedures for Multiple Grants Per Interval | Multiple Grants Per Interval provides the ability to map multiple gates (application flows) using identical UGS traffic profiles destined for the same CM into a single flow at the DOCSIS level (Service Flow). This is accomplished by incrementing the number of grants per interval for each application flow serviced by a ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.12 Procedures for Identifying a PDP to a PEP | When a PDP establishes a new connection with a PEP, it may send a PDP-Config message to declare the AMID(s) (for an application manager) or the PSID (for a policy server) that will be used by that PDP. This allows the PEP to associate state for this PDP from previous TCP connections with this new connection. For exampl... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.13 Procedures for Delivering Gate-Report-State Messages | To determine how to send a Gate-Report-State message (or any other asynchronous notification message), a PEP should follow these steps (in order): 1. If the PEP has an association between the gate and an active TCP connection (such as the COPS Client Handle) then it should send the Gate-Report-State using that connecti... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.14 Procedures for Gate Control Operations Initiated by a Policy Server | There may be situations when it is desirable for a Policy Server to initiate a gate control operation (Gate-Info, or Gate-Delete) for gates that it may be "managing". For example, during a state synchronization a PS may need to issue a Gate-Info request to obtain the complete data for a gate. To accomplish this, the PS... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.15 Procedures for State Synchronization | This clause provides a general overview of the synchronization process. ETSI ETSI TS 102 879 V1.1.1 (2010-06) 83 |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.15.1 Initiating State Synchronization | Synchronization is always initiated by the PDP. To initiate synchronization, the PDP sends a Synch-Request message to the PEP. Although both the PSID and the AMID are optional in this message, one of the two objects shall be present in the message. Both objects may be specified. If the PSID is specified, it shall be th... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.15.2 Full Synchronization | A full synchronization is one in which the PEP sends information about all the gates that match the filtering criteria (PSID, AMID, SubscriberID) specified in the originating Synch-Request. A PDP requests a full synchronization by setting the Synch Type field to 0 in the Synch Options object sent in the Synch-Request. ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.15.3 Incremental Synchronization | An incremental synchronization is one in which the PEP sends information about gates that have had recent state changes for which the PDP may not have received notification. It is further restricted to gates that match the filtering criteria (PSID, AMID) specified in the Synch-Request. An incremental synchronization re... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.15.4 Reporting Gate State Information | The PEP sends one Synch-Report message to the PDP for each gate that is included in the synchronization. The TransactionID in the Synch-Report message shall be the same as the TransactionID in the Synch-Request message that initiated the synchronization. The PSID in the Synch-Report shall be the same value that was spe... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.15.5 Completing the Synchronization | After all the Synch-Report messages for a synchronization request have been sent, the PEP shall send a Synch- Complete message to the PDP to signal the end of the synchronization. The AMID and PSID objects shall be specified as they were in the Synch-Request that initiated the synchronization. The TransactionID in the ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.15.6 Relaying Out of Sync Data | If a Policy Server discovers during the synchronization process that it is out of sync with a CMTS and that the associated data has not yet been forwarded to the Application Manager, then it shall generate a Gate-Report-State for the affected gates and send those reports to the appropriate AMs. Creating a Gate-Report-S... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.15.7 Synchronization with Stateless Policy Servers | Although a stateless policy server has no state, it should still support state synchronization. When an Application Manager issues a synchronization request it should be transparent to the AM whether the policy server maintains state. This may be implemented by: • Translating incoming synchronization requests into sync... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.16 Procedures for Confirming PDP Receipt of Messages | Under some circumstances it may be desirable for a PEP to be able to determine if a message has actually been received by a PDP. For example, if a PEP implements incremental synchronization, it needs to determine if the PDP has actually received a Gate-Report-State message. NOTE 1: Just because it was sent successfully... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 6.5.17 Procedures for Indicating Updated or Lost Shared Resource | When Multicast Gates are in use, it is possible that changing conditions may make a single shared resource previously used for several Multicast Gates inappropriate for some or all of those Gates. In such a case, the CMTS shall send a Gate-Report-State message to the Policy Server for each affected Gate indicating the ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7 Event Messaging Interface Description | |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.1 Introduction | As in the IPCablecom 1.x architecture, event messages within IPCablecom Multimedia provide detailed information regarding QoS resource utilization, such as reservation, activation, and release. New for the IPCablecom Multimedia framework is the need to track status of policy decisions (requests, updates, deletions). Al... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.2 Record Keeping Server Requirements | The Record Keeping Server (RKS) is a trusted network element function. The RKS is generally depicted in the present document as a distinct standalone element, but the present document does not preclude some other application from performing the functions of an RKS, providing that the application conforms to the require... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.3.1 Element ID | Each IPCablecom network element that generates an Event Message shall identify itself with a static, unique element ID. The Element ID is a statically configured element number, unique within a IPCablecom domain, which shall be in the range 0 to 99,999. |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.3.2 Timing | It is important for elements that generate Event Messages to remain closely synchronized with one another and with a standard clock. The requirements in this clause ensure that such elements maintain this synchronization and report events with timestamps that are both accurate and precise. Elements that generate Event ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.3.3 Primary and Secondary RKS Considerations | IPCablecom Multimedia supports an architecture that consists of a primary and secondary RKS. The secondary RKS is used as a fallback RKS when a network element (PS, CMTS) is unable to successfully send a message to the primary RKS. IPCablecom Multimedia network elements shall support event message transport to a primar... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.3.4 Interaction with IPCablecom RKS | An Application Manager may provide an optional Event Generation Info object in the first Gate-Set message to enable Event Messaging for the Gate. If the Event Generation Info object is not provided in the first Gate-Set message (by either the AM or PS), Event Messaging shall not be used for the life of the Gate. In eit... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.4 Event Messages for IPCablecom Multimedia | This clause provides a detailed description and definition of each of the Event Messages defined for IPCablecom Multimedia. |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.4.1 Policy Events | The Policy Event Messages are new for IPCablecom Multimedia. They indicate the time at which the Policy Server receives a request for a policy action and serve to bracket the ensuing set of Event Messages for any resource usage associated with the various instances of a service. Policy event messages are used to indica... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.4.1.1 Policy_Request | The Policy Server shall send a Policy_Request event message to the RKS if a request to create a new policy is received. The PS shall set the Policy_Decision_Status to either Approved (1) or Declined (2), based upon the outcome of authorization and admission control. NOTE: Because the PS does not send the Policy_Request... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.4.1.2 Policy_Delete | The Policy Server shall send a Policy_Delete Event Message to the RKS when it receives a Gate-Delete-Ack from the CMTS in response to an AM or PS initiated Gate-Delete, or a Gate-Report-State from the CMTS indicating that the resources are no longer available for a session. The PS shall always generate a Policy_Delete ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.4.1.3 Policy_Update | The Policy Server shall send a PolicyUpdate Event Message to the RKS if a request to change the traffic profile, classifier, volume limit, time limit, or opaque data of a Gate is received from the AM. Additionally for Multicast Gates, if the PS receives an update to the SharedResourceID from the CMTS, the PS shall send... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.4.2 QoS Events | The QoS Event Messages are sent by the CMTS to the RKS and indicate events related to the IPCablecom access network resources used by the CMTS. |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.4.2.1 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. The CMTS shall timestamp this message immediately upon transmission of a DSA-ACK or DSC-ACK acknowledging a successful DSA-RSP or DSC-RS... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.4.2.2 QoS_Commit | The QoS_Commit 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. The CMTS shall timestamp this message immediately upon transmission of a DSA-ACK or DSC-ACK acknowledging a successful DSA-RSP... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.4.2.3 QoS_Release | The QoS_Release Event Message indicates the time at which the CMTS releases its reservation and/or bandwidth commitment on the IPCablecom access network. The CMTS shall timestamp this message immediately upon Transmission of a DSD-REQ that indicates the request to delete bandwidth. The CMTS is not required to support E... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.4.3 Time_Change | This event captures an instance of a time change. Whenever the (IPCablecom) clock on the network element (PS 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 NTP ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.5 Event Messaging Attributes for IPCablecom Multimedia | This clause describes and defines the IPCablecom attributes included in the IPCablecom Event Messages. Table 15 provides a mapping between each of the IPCablecom Event Messages and their associated attributes. Table 16 offers a detailed description of each of these attributes. Table 15: IPCablecom Attributes Mapped to ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.5.1 EM_Header Attribute Structure | Table 17 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. Table 17: EM_Header Attribute Structure Field Name Semantics Value Type Length Version_ID Identifies version of this EM Header ... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.5.2 Billing Correlation ID (BCID) Field Structure | Table 18 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... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.5.3 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 19 presents Status field description. Table 19: Status Field Description Start Bit Semantics Bit Count 0-1 Error Indicator: 0 = No Error 1 = Possible Error 2 = Kn... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.5.4 QoS Descriptor Attribute Structure | Table 20 describes the QoS Descriptor Data Structure. Table 20: QoS Descriptor Data Structure Field Name Semantics Value Type Length Status_Bitmask Bitmask describing structure contents (see table 21) Bit map 4 bytes Service_Class_Name Service profile name Right justified, space padded ASCII character string 16 bytes Q... |
e35de7dafaf1d43786af9e01f4d2c6f3 | 102 879 | 7.6 RADIUS Accounting Protocol | This clause specifies the protocol used between the IPCablecom network elements that generate Event Messages (PS, CMTS) and the Record Keeping Server (RKS). These network elements shall support RADIUS Accounting (RFC 2866 [11]) with IPCablecom extensions as defined in the present document. ETSI ETSI TS 102 879 V1.1.1 (... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.