BDP Procedure Issues to Consider (1/1)

1. BDP Procedure Issues to Consider (1/1) • Specify two modes (symmetrical to the BDD Procedure) • Complete mode • If the queue is full, the Service Provider stops reading data from the communication service creating backpressure to the user. • If the situation persists, the only means for the user is to PEER-ABORT (derived procedures may add more sophistication) • Timely mode • If the input queue is full the Service Provider discards the oldest transfer buffer from which no data unit has started processing yet. • The user will not notified; it is assumed that the service will have one or more monitored parameters indicating the quality of service (e.g. data unit loss counter) Alternatively a service can derive a procedure that adds a notification. CSTS Spring Meeting- BDPP

2. BDP Procedure Issues to Consider (1/2) • How do we handle the interrupted state? • Do not discard queued data and resume processing when the PS recovers. • Include a maximum queuing time after which a data unit is discarded? This can be added in a service specific derived procedure. This procedure does not have an earliest or latest processing time. • The provider shall ensure that either all or none of the data units in a transfer buffer are processed (except for catastrophic failure, protocol error, STOP, or ABORT) i.e. the provider shall not discard part of a transfer buffer when the input queue overflows. • The maximum size of the transfer buffer shall be managed parameter. CSTS Spring Meeting- BDPP