agent
Click on the red underlined text to get to the source
... datagram messages, called Setups,
between the user host and an agent inside the WPS called the "Service
Agent." Setups are used to reserve, allocate, modify, free, and
deallocate network ...
... between the user host and an agent inside the WPS called the "Service
Agent." Setups are used to reserve, allocate, modify, free, and
deallocate network resources. Each allocated resource has a unique
identifier ...
... group address in the destination field of
that message. The Service Agent also permits a host to inquire about
resources it owns.
...
... received by the WPS from the source host (or is sent by
a WPS agent) and is last checked when the message is
queued for transmission out the I/O interface to the
...
... The Service Agent ...
... datagram messages, called Setup
messages, between the user host and the Service Agent (network
address ...
... address zero). Setup operations include reserving, allocating,
modifying, freeing, and deallocating resources. The Service Agent
causes the requested action to be carried out and serves as the
intermediary between the user and the rest of the network ...
... bases are updated to reflect the current state of the referenced
resource. The Service Agent also permits a host to inquire about
resources it owns using Information Request and Information Reply
messages ...
... host involves a 3-way exchange
where: (1) the requesting host sends a Setup Request to the Service
Agent, (2) the Service Agent returns a Setup Reply to the requesting
host ...
... where: (1) the requesting host sends a Setup Request to the Service
Agent, (2) the Service Agent returns a Setup Reply to the requesting
host, and (3) the requesting host ...
... host, and (3) the requesting host returns a Setup Acknowledgment to
the Service Agent. This procedure is used to ensure reliable
transmission of Setup Requests and Replies. In order to allow more
than one Setup Request message ...
...
Setup exchanges initiated by the Service Agent involve a two-way
exchange where: (1) the Service Agent sends a Notification ...
... Setup exchanges initiated by the Service Agent involve a two-way
exchange where: (1) the Service Agent sends a Notification to
affected hosts ...
... hosts, and (2) the hosts return a Setup Acknowledgment to
the Service Agent. Notifications are used to inform a host of
...
... Notification ID. The Setup Acknowledgment returned by the notified
host to the Service Agent must contain the Notification ID. The host
...
... host sends an Information Request message to
the Service Agent, and (2) the Service Agent sends back an
Information Reply. There is no acknowledgment mechanism, since this
...
... Request message to
the Service Agent, and (2) the Service Agent sends back an
Information Reply. There is no acknowledgment mechanism, since this
request does not change any resource allocation. Furthermore, if
...
... datagram message header must be
HAP_PROTO_SETUP (1) (see Appendix C) for messages sent to the Service
Agent and will be HAP_PROTO_SETUP in messages received from the
Service Agent. The Service Agent ...
... HAP_PROTO_SETUP (1) (see Appendix C) for messages sent to the Service
Agent and will be HAP_PROTO_SETUP in messages received from the
Service Agent. The Service Agent does not recognize or support use
of other higher level protocols (e.g., IP ...
... Service
Agent and will be HAP_PROTO_SETUP in messages received from the
Service Agent. The Service Agent does not recognize or support use
of other higher level protocols (e.g., IP), in setup messages, and
...
...
The format of the Service Agent Header is illustrated in Figure 6.
The body of the message will depend on the particular message type ...
... +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
SERVICE AGENT HEADER
Figure 6
...
... Checksum. The checksum is the 2's-complement of the
2's-complement sum of the words in the Service Agent
Header (excluding the checksum ...
... host to
uniquely identify outstanding requests (Request ID) and
by the Service Agent to uniquely identify outstanding
notifications (Notification ...
... protocol.) The use of these messages is illustrated in the scenario
of exchanges between a host and the Service Agent shown in Figure 7
where the host establishes a stream ...
... Stream Request message (Figure 8) to the Service Agent. After the
network has processed the Create ...
... network has processed the Create Stream Request, the Service Agent
will reply with a Create Stream ...
... network has processed the Change Stream
Request, the Service Agent will respond by sending a Change Stream
Reply (Figure 11) to the host ...
... processed the Delete Stream Request, the Service Agent will respond
by sending a Delete Stream ...
...
Note that streams, like all other resources allocated by the Service
Agent, may be reclaimed by the network if unused. Currently, if no
traffic ...
... specifically including group addresses, may be used
(except the Service Agent's address, 0). Messages sent
in the stream ...
... S0[8-15] Reply Code. If the request was valid, the Service
Agent will have marked the stream for deletion even if
the stream ...
...
S0[8-15] Reply Code. The Service Agent will have marked all of
the host's streams for deletion, even if the stream ...
... deleted via setup
messages exchanged between the hosts and the Service Agent.
Membership in a group may be any arbitrary subset of the network ...
... illustrates a scenario of exchanges between three hosts and the
Service Agent. In the scenario one host, Host A, creates ...
...
Part of the group creation procedure involves the Service Agent
returning to the creating host a 48-bit ...
...
In the figure below, the network Service Agent is pictured as a
single entity for simplicity.
...
... group, once it knows the group
address and the 48-bit key, by sending the Service Agent the Join
Group ...
... host to the group by sending the
Service Agent the Add Group Member Request message (Figure 21). The
...
... Group Member Request message (Figure 21). The
Service Agent will respond with an Add Group Member Reply (Figure
22).
...
... drop out of the group. To do this, the host sends the Service Agent
a Leave Group Request (Figure 23). The Service Agent ...
... Service Agent
a Leave Group Request (Figure 23). The Service Agent will respond
with a Leave Group Reply (Figure 24).
...
... host may expel another member of the group by sending the
Service Agent the Remove Group Member Request message ...
... Group Member Request message (Figure 25).
The Service Agent will respond with a Remove Group Member Reply
...
... Delete Group
Reply (Figure 28). The Service Agent will also send the other
members of the group, if any, a notification ...
... host must acknowledge receipt of Setup Replies and Notifications
from the Service Agent, as described earlier. The format for the
Setup Acknowledgment message is shown in Figure 30.
...
... host by sending an
Information Request message to the Service Agent. The Information
Reply that is returned will enable the host to determine 1) what
...
... uniquely identify outstanding requests (Request ID).
This ID is copied into Information Replies by the
Service Agent.
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
...
... outstanding requests. This ID is copied into the
Information Reply message by the Service Agent.
S3[0-7] Number of entries included in the Information Reply
message ...
... 0 any HAP_PROTO_IP (0x800)
1 Service Agent HAP_PROTO_SETUP (1)
1 other HAP_PROTO_NONE (0)
...
... In HAP version 0, messages between a host and the Service Agent were
allowed to contain Internet Protocol headers ...