JPH0720157B2 - Shared system of applied association - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION [Industrial field of use] The present invention relates to a system for sharing an application association between a plurality of individual applications in an application layer of OSI.

[Conventional technology]

The concept of architecture as an architectural style was originally introduced into the field of data communication, and network architecture has emerged. The basic idea of network architecture is virtualization, layering and standardization. Here, virtualization is a concept that allows individual communication devices having different software structures and transmission control functions and terminals connected thereto to be viewed as a common image when viewed from a communication partner. Hierarchicalization is a concept in which communication functions are divided and stacked. Standardization refers to the uniform specification of protocol and interface specifications.

ISO (International Organization for Standardization) is advancing standardization of an architecture called OSI (Open Systems Interconnection) to realize free communication between computers. In the OSI basic reference model, the data communication function from the lower level near the transmission path to the higher level up to the user application is divided into seven layers. Then, a protocol as a communication method in the same layer and an interface between upper and lower layers are defined.

By the way, the uppermost layer as the OSI seventh layer is called an application layer. Conventionally, individual applications perform their own processing in this 7th layer, and at that time, common service elements necessary to set the communication path.
Formed an Application Entity with ACS (Association Control Service). The application has been set up between a pair of application entities.

[Problems to be Solved by the Invention]

In this way, in the 7th layer of OSI, when an individual application forms an application entity, even if another application entity has already set an application association to the same communication destination, another application entity sets an application association in a similar procedure. There was a need. Therefore, there is a problem that duplicate processing occurs and the resources required for the processing increase.

Therefore, an object of the present invention is to notify an individual application as if an application application has been established, without newly establishing an application association when there is an available application association. It is to provide a shared system of applied associations that enables it.

[Means for Solving the Problems]

According to the present invention, in the case where an individual application sets an application association using a common application service element in the application layer of the seventh layer of the open type system interconnection, an application association setting request from the individual application is received. If there is no matching application association, an application association setting request is sent to the application service element, while if there is a matching application association, an application association management means for sharing the application association is provided.

Then, if there is an application association that can be used by this application association management means, the application association is shared.

〔Example〕

 Hereinafter, the present invention will be described in detail with reference to Examples.

FIG. 1 shows the configuration of a common system of the application association of this embodiment. In the shared system of the application association of this embodiment, the individual application
An application association management function (application association management means) 13 between the 11 and the application service element (ACS) 12
Is arranged.

When the application association management function 13 receives an application association setting request from all the individual applications 11, it searches for an available application association and, if there is an available application association, does not establish a new application association. , Has a function of notifying the individual application 11 as if the application association was established.

Therefore, the application association management function 13 has the following functions.

(I) A management table (not shown) is provided, and the application context and identifier of the set application association are managed by this management table. Similarly, a registration table (not shown) is provided, and mapping information indicating which application association the individual application 11 is using is registered in this registration table and managed.

(Ii) Receive the application association setting request from the individual application 11 and retrieve the management table from the received application context. If they match, the communication path of the already set application association is used as it is, and the identifier of the application association and the individual application name are registered in the registration table. Then, the identifier is returned to the individual application 11. If they do not match, an application association setting request is transmitted to the application service element 12.

(Iii) When receiving the application association setting instruction or confirmation from the application service element 12, the management table and the registration table are created from the application context of the transmission parameter, the individual application name and the application association identifier.

(Iv) Individual application 11 and applied service elements
When the application association release is received from 12, the corresponding data on the management table and the registration table is deleted.

The application association management function 13 is adapted to receive the following primitives to perform such a function.

(B) Application association setting request primitive 21 from individual application 11.

(B) The application association setting instruction primitive 22 from the application service element 12.

(C) Application association setting response primitive 23 from individual application 11.

(D) The application association setting confirmation primitive 24 from the application service element 12.

(E) Application association release request primitive 25 from individual application 11.

(F) Application association release instruction primitive 26 from the application service element 12.

(G) Application association release response primitive 27 from individual application 11.

(H) An application association release confirmation primitive 28 from the application service element 12.

FIG. 2 shows a processing flow of the application association management function when the application association setting request is received from the individual application.

When the application association setting request primitive 21 is received from the individual application 11, the individual application name and application context are obtained from the individual application 11 (step in FIG. 2). Then, the management data is searched in the received application context to find a matching application association (step). If there is no match (N), a new application association setting request is sent to the application service element 12.

If there is a match in the step (Y), the identifier of the application association and the received individual application name are registered in the registration table (step). Then, the application association setting completion and the identifier are returned to the individual application 11. (Step).

FIG. 3 shows a flow of processing when an application association setting instruction and confirmation are received from the application service element.

When the application association setting instruction primitive 22 or the confirmation primitive 24 is received from the application service element 12, the application association identifier, application context, and individual application name are obtained (step in FIG. 3). Then, the received identifier and application context are set in the management data (step). Next, data is registered in the registration table from the received data (step), and an application association setting instruction or confirmation is transmitted to the individual application 11 (step).

FIG. 4 shows the flow of processing when an application association setting response is received from an individual application.

When the application association setting response primitive 23 is received from the individual application 11, the individual application name and the application association identifier are obtained from the individual application (step in FIG. 4). Next, the registration data is searched based on the received identifier to find a matching application association (step). Then, the application association setting response is transmitted to the application service element 12 of the corresponding application association (step).

FIG. 5 shows the flow of processing when an application association release request is received from an individual application.

When the application association release request primitive 25 is received from the individual application 11, the application association identifier is obtained (step in FIG. 5), the registered data is searched by this identifier, and the matching application association is searched (step). Then, the application association release request is transmitted to the application service element 12 on the applicable application association. (Step).

FIG. 6 shows the flow of processing when an application association release instruction is received from the application service element.

When the application association release instruction primitive 26 is received from the application service element 12, the identifier of the application association and the individual application name are obtained (step in FIG. 6). Next, the received data is used to search the registered data to find the destination individual application 11 (step). Then, the application association release instruction is transmitted to the individual application 11 (step).

FIG. 7 shows a processing flow at the time of application association release response from an individual application.

When the application association release response primitive 27 is received from the individual application 11, the application association identifier is obtained (step in FIG. 7). Corresponding registration data in the registration table is deleted from the received identifier (step), and the registration table is searched from this identifier to check whether another same application association is shared (step). If there is no shared one (Y), the management data of the management table corresponding to the received identifier is deleted (step). Then, the application association release result is sent to the application service element 12 with the result of the application association release as "normal end" (step).

If there is something shared in the step (N), the result data of the application association release is set as “unreleased”,
An application association release response is sent to the application service element 12 (step).

Finally, FIG. 8 shows the flow at the time of receiving the application association release confirmation from the application service element.

When the application association release confirmation primitive 28 is received from the application service element 12, the individual application name and the application association identifier are obtained (step in FIG. 8). Based on this identifier, the corresponding registration data in the registration table is deleted (step). Further, it is determined whether the received result data is “normal end” (step). If the result is “normal end” (Y),
The corresponding management data in the management table is deleted from the received identifier (step).

On the other hand, if the result is “unreleased” (step;
N), set the result data to "normal end" (step). Then, the application association release confirmation is transmitted to the individual application 11 (step). Similar processing is performed after the processing of the step is performed.

〔The invention's effect〕

As described above, according to the present invention, in each individual application, since the application association is shared by setting and releasing the application association using the application association management means, the establishment of the duplicate application association to the same system is established. This eliminates unnecessary processing and resources for establishing an application association. Further, according to the present invention, since the existing function can be used by such a function of the application association management means, it is possible to eliminate the failure in establishing the application association.

[Brief description of drawings]

The drawings are for explaining one embodiment of the present invention, in which FIG. 1 is an explanatory view showing various primitives received by an application association management function in a shared system of application associations, and FIG. FIG. 3 is a flow chart showing the processing flow of the application association management function when the application association setting request is received, and FIG. 3 shows the processing flow of the application association management function when receiving the application association setting instruction from the application service element and the confirmation. FIG. 4 is a flow chart showing the processing flow of the application association management function when the application association setting response is received from the individual application, and FIG. 5 is the application association management machine when the application association release request is received from the individual application. 6 is a flow chart showing the flow of processing of FIG. 6, FIG. 6 is a flow chart showing the flow of processing of the application association management function when an application association release instruction is received from the application service element, and FIG. 7 is an application association release response from an individual application. Flowchart showing the flow of processing of the applied association management function at time, No. 8
The figure is a flow chart showing the processing flow of the application association management function when the application association release confirmation is received from the application service element. 11 …… Individual application, 12 …… Application service element, 13 …… Application association management function.

Claims (1)

[Claims] 1. An application association setting request from an individual application when an individual application sets an application association using a common application service element in an application layer of the seventh layer of open system interconnection. If there is no matching application association, it sends an application association setting request to the above application service element, while if there is a matching application association, it comprises an application association management means for sharing the application association. A shared system of applied associations.