The terms and conventions given in this standard are used as references for service definition standards that define connection-oriented or connectionless (N) services as specified in the Open Systems Interconnection Reference Model (GB9387). In particular, conventions related to point-to-point connections (i.e., instances of point-to-point communication within a layer of the reference model) are given. The scope of application of this standard is limited to meeting the urgent needs of the network layer, transport layer, and session layer. If appropriate, it can also be used in other layers. GB/T 15129-1994 Information Processing System Open Systems Interconnection Service Agreement GB/T15129-1994 Standard download decompression password: www.bzxz.net

National Standard of the People's Republic of China
Information processing systems
Open systems interconnection
Information processing systems-Open systemsInterconnection-Service conventions This standard is equivalent to ISO/TR8509--1987 & Information processing systems-0 Introduction
Open systems interconnection
GB/T15129-94
1ISO/TR8509-1987
Service conventions",
This standard is a guide for users and developers of various service standards, and its purpose is to provide common term definitions and timing diagrams for reference by various service standards, especially for service standards of network layer, transport layer and session layer. The progress of the formulation of network service definition, transport service definition and session service definition requires the use of common service conventions. This standard aims to meet this requirement, but does not meet all the requirements of all service standards that can be derived from the basic reference model. Moreover, it is impossible to guarantee complete consistency between the above three service standards and this standard. Almost all the differences are technically insignificant and generally involve only slightly different representations of the same type of information. In order to avoid delaying the publication of the above service standards due to the insistence on complete consistency, a more realistic and less perfect solution is adopted. This standard defines this general convention and also points out the explicit and most specific conventions adopted by specific service standards. 1 Subject matter and scope of application
The terms and conventions given in this standard are used as references for service definition standards that define face-to-face connection or connectionless mode (N) services specified in the open system connection reference model (GB9387). In particular, the conventions that are compatible with point-to-point connections (i.e., instances of point-to-point communication within a layer of the reference model) are given.
The scope of application of this standard is limited to meeting the urgent needs of the network layer, transport layer and session layer. If appropriate, it can also be used in other layers. Conventions for other types of (N> services and broader topics related to the semantic models used for (NV) services are for further study.
2 Referenced standards
GB9387 Basic reference model for information processing systems Open Systems Interconnection GB12453 Definition of information processing systems Open System Qiu Lian Transport Service GB/T15128 Definition of information processing systems Open Systems Interconnection connection-oriented basic session service ISO8348 Definition of information processing systems data communication network service 3 Terminology
3.1 This standard is based on the concepts proposed in GB9387 and uses the following terms defined therein: H, (N) layer;
b, (N) service)
C. (N) implementation:bzxZ.net
Approved by the State Administration of Technical Supervision on July 16, 1994 and implemented on March 1, 1995
(N) service access point;
(V) service access point address.
GB/T 15129
Note, (1) In other than this standard and in the definition of network, transport and conference services, the use of the term "service" is not always consistent with the definition in GB 9387. In many cases, it is used to indicate a special part or element of the entire (N) layer service. In general, special usage can be explained based on naming conventions or context.
② When describing the relationship between primitives related to a single connection, the term "service access point" is used. The inclusion of the concept of connection endpoints in this description is for further study. However, connection endpoints have been referenced in existing network and transport service definitions (ISO 8348 and GB 12453). 3.2 This standard also uses the following terms:
3.2.1 Service user: service-user is an entity that uses services in a single open system through a service access point. 3.2.2 Service provider: service-provider is an abstraction of all entities that provide services to peer service users. Note: The behavior of a service provider is described using an abstract method. service primitivesprinitive
3.2.3 Service primitive: an abstract representation of an implementation-independent transaction between a service user and a service provider. Note: Since a service user is usually a (N) entity (except an application), and since the service provider usually generates a number of (N) entities and low-level services (except the physical layer), a service primitive is also an abstract representation of an implementation-independent transaction between two adjacent (N) entities. 3.2.4 Request (primitive) request (primitive) A representation of an interaction that a service user uses to call a procedure. 3.2.5 Indication (primitive) indication (primitive) A representation of an interaction that a service provider uses to indicate that: a. it has actively called a procedure. or b. a service user has called a procedure at a peer service access point. 3.2.6 response (primitive) response (primitive) An indication of an interaction by which a service user indicates that it has completed a procedure previously invoked by an interaction represented by an indication primitive. 3.2.7 confirmation (primitive) confirmation (primitive) An indication of an interaction by which a service provider indicates, at a particular service access point, that a procedure previously invoked by an interaction represented by a request primitive has completed.
3. 2.8 (N) mandatory-service (N)-mandatory-service A special service among all (N) services that is always included in the implementation of (N) service. 3.2.9 (N) provider-optional-service A special part of all (N) services that may or may not be included in the implementation. 3.2.10 (N) user-optional-service A special part of (N) service that is implemented only after mutual agreement between the peer service users during the connection establishment phase. 3.2.11 Confirmed-scrvice causes the service provider to issue an explicit confirmation of the specific part of the (N) service to the service user who initiated the service. NOTE: There is not necessarily any relationship between the confirmation and the response from the peer service user. 3.2.12 Non-confirmed-service does not cause the service provider to issue an explicit confirmation of the specific part of the (N) service to the service user who initiated the service. 3.2.13 (N)-provider-initialed-service The service provider, rather than the service user, initiates the specific part of the (N) service. 4-layer service model Layer services are defined using an abstract model with the following elements: (V) service user;
b. (N) service provider.
GB/T 15129—94
Each service user accesses a service provider through a service access point. During the lifetime of a particular connection, two service users are associated at different service access points (see Figure 1).Service primitives; B—(N—1) Service primitives; C=(N) Peer protocol D—(N) Entity 5 Service primitives
5.1 Overview
The use of primitives does not imply any particular implementation of the service access point. The following comments apply to this definition technique based on service primitives:
Service primitives are conceptual and do not necessarily relate directly to protocol elements, nor are they necessarily viewed as macro calls to layer service access methods. It is possible to represent the same layer service using other sets of primitives. These sets of primitives are not defined in this standard. h.
Only service primitives related to service-only elements involving two service users need to be considered. Interactions between service users and providers c
that are only related to local agreements are not relevant to this broadcasting technique. For example, some implementations may provide localized functionality. Since the service users are not involved, this functionality is not visible outside the main system. 5.2 Service Classification
This standard specifies the following types of services: mandatory services (see 3.2.8)
b. Provider optional services (see 3.2.9), user optional services (see 3.2.10).
GB/T15129—94
User optional services can be mandatory services or provider optional services. 5.3 Service Primitive Types
This standard specifies four types of service primitives:
. Request primitive (see 3.2.4)
Indication primitive (see 3.2.5)
Response primitive (see 3.2.6);
Confirmation primitive (see 3.2.7).
5.4 Primitive Properties
Interactions described by primitives should be considered as instantaneous events that cannot be interrupted by another interaction. A primitive has: a direction, indicating the main flow of information, which can be a.
1) from the service user to the service provider, or 2) from the service provider to the service user; one or more parameters, each of which has a defined range of values. The values ​​associated with the interaction described by the primitive are passed in the appropriate direction of the given primitive.
5.5 Primitive Names
Each primitive name contains three elements:
One or more opening letters, representing the English name of a specific service [A1 in Appendix A (reference)], referring to the name of a special part of the entire (N) service [see A2 in Appendix A (reference)]h.
Name indicating the type of primitive [see A3 in Appendix A (reference).c
Note: In the relevant provisions of the definition of session services (GB/T15128) , introduces an improved naming structure that indicates specific subdivisions of a single special service within an event service. This division is indicated in parentheses after the name of the special part of the service. 6 Sequence Diagram Conventions
Sequence diagrams are used to describe the temporal relationship of interaction sequences. The sequence diagram (see Figure 3) presents:
. The sequence of events at each user/provider interface; b, if appropriate, the sequence of events between peer users. Each diagram is divided into three areas by two lines. The middle area represents the service provider, The two areas represent two service users. The two vertical lines represent the service access points between the service users and the service provider and represent the passage of time from top to bottom. At each service access point, the sequence of events is located in chronological order from top to bottom along the appropriate vertical line. The arrows in the area representing the service users indicate the main flow of information (i.e., flow to or from the service user) during the execution of the interaction described by the service primitive. This information flow may be subject to implicit flow control between the service user and the service provider. The sequential relationship between the interactions at the two service access points can be expressed in two ways. The logically correct expression is shown in Figure 3a, and the expression commonly used in the network, transport and session service definitions is shown in Figure 3b. Both expressions are intended to express the same basic meaning. For example, in Figures 3a and 3h, it can be seen from the straight lines shown in the service provider area that the request primitive issued by a service user at time 1 causes an indication to query the peer service user at time t.
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.