Browse Prior Art Database

Status Reporting Requirements in a Network

IP.com Disclosure Number: IPCOM000121317D
Original Publication Date: 1991-Aug-01
Included in the Prior Art Database: 2005-Apr-03
Document File: 3 page(s) / 104K

Publishing Venue

IBM

Related People

Gainey Jr, CW: AUTHOR

Abstract

Disclosed is a method by which each command request that constitutes the request of a request/report pair has a status-reporting requirements tag included as part of the command request when it is transmitted in a network. Such a tag is used to convey instructions to the recipient of the request about if and how the recipient is to report varying forms of status relevant to the acceptance, execution, and completion of the command request that contains the tag.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Status Reporting Requirements in a Network

      Disclosed is a method by which each command request that
constitutes the request of a request/report pair has a
status-reporting requirements tag included as part of the command
request when it is transmitted in a network.  Such a tag is used to
convey instructions to the recipient of the request about if and how
the recipient is to report varying forms of status relevant to the
acceptance, execution, and completion of the command request that
contains the tag.

      A command request contains a particular task to accomplish and
a report conveys status about the request. Protocols exist that
define several classes of report that return information about the
initial, continuing and final status of a request.  A mechanism is
provided to match one or more reports with the appropriate request.
Certain reports from the recipient are always expected by the sender
of the request.  The status-reporting requirements tag is added to
the command-request part of a request/report to select the set of
reports that are desired.

      The additional tag conveys instructions to the recipient of the
request on how the recipient is to respond. The information in the
tag defines the treatment for a number of classes of command report
and three types of treatment for each class.  The tag may designate
from a single report class up to a maximum of all defined report
classes.  The types of treatment that are assigned to each report
class are:
     1.  Suppressed  -  The recipient is prohibited from generating a
report of the associated class.
     2.  Optional - The recipient is permitted to generate a report
of the associated class.  The recipient uses its local knowledge of
the processing characteristics of the particular request in order to
make a decision of whether or not to produce a report of a particular
class.
     3.  Required - The recipient is required to generate a report of
the associated class.

      Formation of a report in a particular class is, primarily, a
matter of the design of the recipient.  If, by the nature of the
recipient, it does not produce a report of a given class, then
specifying a required treatment for that class will not cause a
report of that class to be produced.

      The classes of report are:
      1.  Rejection - The request is rejected by the recipient.  The
report may include information indicating the reason for the
rejection.
      2.  Acceptance - The request is accepted by the recipient.  The
recipient will attempt to process the request.
      3.  Intermediate - Execution of the request has begun and has
p...