JP2001249868A - Data communication method, client, repeater, gateway, server and recording medium with communication program therefor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To realize data communication between client servers when plural clients with a PDA function, etc., are connected to a mobile terminal and the mobile terminal is functioned as a repeater. SOLUTION: The repeater 3 transmits a message (SA9) received from a client 4 to a server 1 via a gateway 2 by adding a client identifier in a datagram header of the message (SA10, SA11). The server 1 transmits the message to the repeater 3 via the gateway 2 by adding the client identifier in the datagram header of the message when the message is transmitted to the client 4 (SA12, SA13). The repeater 3 transmits the message to the client 4 according to the client identifier to be included in the datagram header of the message received from the gateway 2 (SA14).

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a data communication method, a client, a relay device, a gateway, a server, and a recording medium on which a communication program is recorded, and more particularly to a data communication method for adding a client identifier to a datagram header. .

[0002]

2. Description of the Related Art Hitherto, means for realizing data communication between a mobile terminal and a server across different protocol domains, such as between a wireless communication domain and an Internet domain, has been known. An example of data communication between a mobile terminal and a server is “Wi-Fi
reless Application Protocol Architecture Specifica
tion, WAP Architecture Version 30-Apr-1998 ". One example of realizing server-led data communication is “Wireless Application Protocol Push Archite.
ctural Overview, WAP Push Architectural Overview P
roposed Version 16-August-1999 '' and `` Wireless App
lication Group User Agent Profile Specification, W
AG UAPROF Proposed Version 0.6, 22-Jun-1999 ".

As shown in FIG. 1, a conventional data communication system between a mobile terminal and a server includes a WAP mobile terminal, a WAP gateway, and a WAP server. The data communication system between the mobile terminal and the server having such a configuration operates as shown in FIG.

[0004] The WAP mobile terminal 3 communicates with the WAP gateway 2.
The profile of the WAP mobile terminal 3 is notified. The WAP gateway 2 stores the profile of the WAP mobile terminal 3 in the profile storage unit 2a. The WAP server 1 requests the profile of the WAP mobile terminal 3 to the WAP gateway 2 before transmitting data to the WAP mobile terminal 3,
After forming data in a format suitable for the WAP mobile terminal 3 according to the profile of the mobile terminal 3, the data is transmitted to the WAP gateway 2. The WAP gateway 2 receives the data from the WAP server 1, converts the protocol, and transmits the data to the WAP mobile terminal 3.

[0005]

A first problem is that when a plurality of clients are physically connected to a mobile terminal in a conventional system and the mobile terminal functions as a relay device, data communication between the client and the server is performed. Cannot be realized.

The reason is that the data received from the server or the gateway cannot be distributed to the client because the relay device has no means for identifying the client.

An object of the present invention is to provide a data communication method capable of realizing data communication between a plurality of clients and a server via a relay device, a client, a relay device, a gateway, a server, and a storage for recording a communication program thereof. To provide a medium.

Another object of the present invention is to include a client identifier in a datagram header so that a relay device
It is an object of the present invention to provide a data communication method capable of efficiently realizing communication between clients, a client, a relay device, a gateway, a server, and a recording medium recording the communication program thereof.

[0009]

The relay apparatus according to the present invention comprises: means for determining a client identifier of a client which has made a registration request; means for managing a client identifier and a client profile as a profile list; Means are provided for adding an identifier.

[0010] The gateway of the present invention comprises means for determining a client to which data is transmitted from a profile list, and means for adding a client identifier to a datagram header.

The server of the present invention comprises means for determining a client to which data is to be transmitted from a profile list, and means for adding a client identifier to a datagram header.

[0012] The data communication method of the present invention includes the relay device,
The object of the present invention can be achieved by adding the client identifier in the datagram header, comprising the server, the client, and the gateway.

[0013]

Next, embodiments of the present invention will be described in detail with reference to the drawings. Referring to FIG.
The first embodiment of the present invention includes a client 4, a relay device 3, a gateway 2, and a server 1.

Each of these operates roughly as follows.

The client 4 registers a profile describing the processing capability of the client itself in the relay device 3. The client 4 sends a message to the relay device 3. The client 4 receives the message from the relay device 3.

The relay device 3 shown in FIG. 4 determines the client identifier of the client which has requested the registration process, and compiles the client profile and the client identifier into a pair profile. The relay device 3 makes the pair profile of one or a plurality of clients a profile list and notifies the gateway 2 of the pair list. The relay device 3 transmits the message received from the client 4 to the gateway 2. The relay device 3 extracts the client identifier included in the message received from the gateway 2 and transmits the received message to the client 4 according to the client identifier.

When the gateway 2 shown in FIG. 5 receives the profile list from the relay device, it stores and manages the profile list for each relay device. When receiving a profile request from the server 1, the gateway 2 responds with a profile list of the requested relay device. Gateway 2 is a relay device 3
Is transmitted to the server 1.
The gateway 2 transmits the message received from the server 1 to the relay device 3. The gateway 2 converts a protocol when a different protocol is used.

The server 1 shown in FIG. 6 requests the gateway 2 for a profile list of the relay device to which the message is to be transmitted, and receives the corresponding profile list from the gateway 2 at the time of server-initiated message transmission. The server 1 selects the client identifier of the client 4 sending the message from the profile list,
The message is converted based on the profile, a client identifier is added to the datagram header of the message, and the message is transmitted to the gateway 2. The server 1 receives the message from the gateway 2. When transmitting a data transmission request from a client at the time of client-initiated message transmission, the server 1 requests the gateway 2 for a profile list of the relay device connected to the client that has made the data transmission request, and stores the corresponding profile list. receive. Then, the message is converted based on the profile, a client identifier is added to the datagram header of the message, and the message is transmitted to the gateway 2.

The profile management storage unit 35 shown in FIG.
Is composed of a device identifier (D-Id), an identifier (TE-Id), and a corresponding list of client profiles.

The profile management storage unit 25 shown in FIG.
The profile management storage unit 15 stores the identifier shown in FIG.
(TE-Id) and a corresponding list of client profiles.

Next, the overall operation of the present embodiment will be described in detail with reference to FIG. 3, FIG. 4, FIG. 5, FIG. 6, FIG.

First, registration of a client profile will be described.

One or a plurality of clients 4 connected to the relay device each transmit a profile registration message to the relay device 3 (SA1, SA2 in FIG. 3). The profile registration message includes D-Id, which is its own ID, as the management information of the client, and a profile describing the processing capability of the client itself.

The relay device 3 includes one or more clients 4
When the profile registration message is received, the processing in FIG. 4 starts.

After analyzing the profile registration message, the message analysis unit 31 stores the profile and the device identifier (D-Id) included in the message in the profile management storage unit 3.
5 is stored. Next, a request for processing the received message is issued to the main control unit 34. The main control unit 34 uses the D-Id of the profile management storage unit 35 to determine a client identifier (TE-Id) that can be uniquely associated with the D-Id, and stores the TE-Id in the profile management storage unit 35. .

Next, a profile list, which is a pair profile group of the TE-Id and the profile stored in the profile management storage unit 35, is sent to the message composition unit 32, and a processing request for profile notification is sent to the message composition unit 32. Issue. The message composing unit 32 composes a profile notification message using the profile list, and transmits the message to the gateway 2 (SA3).

When the gateway 2 receives the profile notification message from the relay device 3, it starts the processing shown in FIG.

After analyzing the profile notification message, the message analyzer 21 stores the profile list in the profile manager 25. The profile list is stored and managed for each relay device.

Next, a case where server-led data communication is performed will be described. In server-led data communication,
By the processing of SA1 to SA3 described above, the relay device 3
A correspondence list including a device identifier (D-Id), an identifier (TE-Id), and a client profile corresponding to one or a plurality of clients connected to the relay device 3 as shown in FIG. Stores a correspondence list including identifiers (TE-Ids) of one or more clients connected to the relay device of the communication destination shown in FIG. 8 and a client profile.

First, the server 1 starts the processing shown in FIG. 6 when a data transmission request is issued from the user.

After analyzing the data transmission request from the user, the user request analysis unit 12 transmits the transmission data, the transmission data information, and the identifier (MT) of the transmission destination relay device included in the data transmission request.
-Id) is stored in the memory 13 and the processing request is sent to the main control unit 14.
Send to The transmission data information includes content type information of the transmission data. The content type information includes images,
Content type information such as text and moving images is included.

The main control unit 14 stores the profile management storage unit 1
If the profile list of the relay device of the data transmission destination is not stored in 5, it issues a client profile request processing request to the message composition unit 16. The message composition unit 16 stores the identifier (MT-I
A client profile request message including d) is formed and transmitted to the gateway 2 (SA4).

Upon receiving the client profile request message from the server 1, the gateway 2 starts the processing in FIG.

After analyzing the client profile request message, the message analyzer 27 issues a request for processing the received message to the main controller 24. Main control unit 2
4 sends a profile list corresponding to the identifier (M-Id) of the relay device included in the client profile request message from the profile management storage unit 25 to the message composition unit 22, and transmits a client profile response to the message composition unit 22. Issue a processing request. The message composition unit 22 constructs a client profile response message using the profile list,
Send to (SA5)

The server 1 has a profile management storage unit 15
6 stores the profile list of the relay device of the transmission destination, or when a client profile response message is received from the gateway 2, the processing in FIG. 6 is started.

The message analyzer 11 is a gateway 2
If a client profile response message is received, after analyzing the client profile response message, the profile list included in the message is stored in the profile management storage unit 15 for each relay device, and the main control unit 14 is requested to process the received message. Issue

The main control unit 14 stores the content type information of the transmission data information in the memory 13 and the profile management storage unit 1
5 is compared with the profile list, the client identifier (TE-Id) of the client transmitting the data is determined, and stored in the memory 13.

For example, if the content type information is an image, an image is used as a search key, and a client profile capable of processing the image is searched from a profile list.
When there are a plurality of searched client profiles, the largest client profile is selected by comparing the display size and the like, and the TE-Id corresponding to the client profile is determined. In selecting a client profile, a client profile having a minimum display size or the like and a minimum transmission data amount may be selected.

Next, the transmission data in the memory 13 is converted according to the profile such as the display size included in the client profile.

Next, the transmission data and TE-Id of the memory 13 are sent to the message composition unit 16 and a data transmission processing request is issued to the message composition unit 16. The message composition unit 16 composes a data transmission message using the transmission data and the TE-Id, and transmits the message to the gateway. (SA
6)

Upon receiving the data transmission message from the server 1, the gateway 2 starts the processing in FIG.

After analyzing the data transmission message, the message analyzer 27 stores the datagram in the message in the memory 2.
3 and issues a received message processing request to the main control unit 24. After converting the datagram in the memory 23, the main control unit 24 sends the datagram to the message composition unit 26 and issues a data transmission processing request to the message composition unit 26. The message composition unit 26 composes a data transmission message using the datagram, and transmits the data transmission message to the relay device 3. (SA7)

When receiving the data transmission message from the gateway 2, the relay device 3 starts the processing in FIG.

After analyzing the data transmission message, the message analyzer 37 analyzes the transmission data contained in the message and the client identifier (TE-Id) contained in the datagram header.
Is stored in the memory 33, and a received message processing request is issued to the main control unit 34. The main control unit 34 is a memory 33
Profile management storage unit 3 using the TE-Id of
The device identifier (D-Id) is searched from the profile list of No. 5. Next, the retrieved D-Id and the transmission data stored in the memory 33 are sent to the message composition unit 36, and a data transmission processing request is issued to the message composition unit 36. The message composition unit 36 composes a data transmission message using the D-Id and the transmission data, and transmits the data transmission message to the client 4. (SA8)

Next, a case in which client-initiated data communication is performed will be described. In the client-initiated data communication, by performing the above-described processes of SA1 to SA3, the relay device 3 is provided with a device identifier (D-Id) corresponding to one or a plurality of clients connected to the relay device 3 as shown in FIG. ), An identifier (TE-Id), and a correspondence list including a client profile are stored.
It is assumed that an identifier (TE-Id) of one or more clients connected to the relay device of the communication destination illustrated in FIG. 8 and a correspondence list including a client profile are stored.

First, the client 4 transmits a data request message to the relay device 3. (SA9)

When the relay device 3 receives the data request message from the client 4, it starts the processing in FIG.

After analyzing the data request message, the message analyzer 31 analyzes the device identifier (D
-Id) is stored in the memory 33. Next, a received message processing request is issued to the main control unit 34. Main control unit 34
Searches for the client identifier (TE-Id) from the profile list in the profile management storage unit 35 using the D-Id of the memory 33 as a search key, and sends the TE-Id to the message composition unit 32. Next, a data request processing request is issued to the message composition unit 32. The message composition unit 32 has the TE-Id
Constructs a data request message using
Send to (SA10)

Upon receiving the data request message from the relay device 3, the gateway 2 starts the processing in FIG.

After analyzing the data request message, the message analyzer 21 stores the datagram in the message in the memory 2.
3 and issues a received message processing request to the main control unit 24. The main control unit 24 sends the datagram in the memory 23 to the message composing unit 22 and issues a data request processing request to the message composing unit 22. The message composing unit 22 composes a data request message using the datagram, and transmits the data request message to the server 1. (SA11)

Upon receiving the data request message from the gateway 2, the server 1 starts the processing in FIG.

After analyzing the data request message, the message analyzer 11 stores the client identifier (TE-Id) included in the message in the memory 13 and issues a request for processing the received message to the main controller 14. Main control unit 1
4 stores the response data to the request message in the memory 13 from the data storage unit 17.

Next, when the profile list of the relay device to which the client that transmitted the data request message is connected or the pair profile of the client is not stored in the profile management storage unit 15, the main control unit 14 A processing request for the client profile request is issued to the unit 16. The message composition unit 16 composes a client profile request message including the identifier (MT-Id) of the relay device to which the client is connected, and transmits the message to the gateway 2 (SA12).

Upon receiving the client profile request message from the server 1, the gateway 2 starts the processing in FIG.

After analyzing the client profile request message, the message analyzer 27 issues a received message processing request to the main controller 24. Main control unit 2
4 sends a profile list corresponding to the identifier (MT-Id) of the relay device included in the client profile request message from the profile management storage unit 25 to the message composition unit 22, and sends a client profile response to the message composition unit 22. Issue a processing request. The message composition unit 22 composes a client profile response message using the profile list, and transmits the message to the server 1 (SA13). If the server 1 holds the profile list of the relay device to which the client that transmitted the data transmission message is connected to the profile management storage unit 15 or the pair profile of the client that has made the data transmission request, the client profile request ( SA12) and the flow of the client profile response (SA13) may be omitted.

When the client profile is included in the message of the data request (SA11), the flow of the client profile request (SA12) and the client profile response (SA13) may be omitted.

Server 1 requests client profile
Client identifier (TE-Id) in the message of (SA12)
And the gateway 2 may respond only with a pair of pair profiles corresponding to the TE-Id in the client profile response (SA13).

The server 1 stores the profile list of the relay device of the transmission destination or the pair profile of the client that has made the data transmission request in the profile management storage unit 15, or receives the client profile response message from the gateway 2 when the server 1 receives the client profile response message. The process at 6 is started.

[0059] The message analysis unit 11
If a client profile response message is received, after analyzing the client profile response message, the profile list included in the message or the pair profile corresponding to the client of the transmission destination is stored in the profile management storage unit 15, and the main control unit 14 Issues a received message processing request. The profile list or the pair profile is managed for each identifier (MT-Id) of the relay device 3.

Using the client identifier (TE-Id) of the memory 13 as a search key, the main control unit 14 searches the profile list or the pair profile of the profile management storage unit 15 for the client profile of the client that has issued the data transmission request.

Next, the response data in the memory 13 is converted according to the profile such as the display size included in the searched client profile. Next, TE-Id
And the response data to the message composition unit 16,
It issues a data response processing request to the message composition unit 16. The message composition unit 16 stores the response data, TE-Id
To send a data response message to the gateway 2. (SA14)

When the gateway 2 receives the data response message from the server 1, the gateway 2 starts the processing shown in FIG.

After analyzing the data response message, the message analyzer 27 stores the datagram in the message in the memory 2.
3 and issues a received message processing request to the main control unit 24. The main control unit 24 sends the datagram in the memory 23 to the message composition unit 26, and issues a data response processing request to the message composition unit 26. The message composition unit 26 composes a data response message using the datagram, and transmits the data response message to the relay device 3. (SA1
5)

When the relay device 3 receives the data response message from the gateway 2, it starts the processing shown in FIG.

After analyzing the data response message, the message analyzer 37 stores the response data and the client identifier (TE-Id) included in the message in the memory 33, and issues a received message processing request to the main controller 34. . The main control unit 34 searches for a device identifier (D-Id) from the profile list in the profile management storage unit 35 using the TE-Id of the memory 33 as a search key. Next, D-Id and memory 3
3 is stored in the message constructing unit 36.
And issues a data response processing request. The message composition unit 36 composes a data response message using the D-Id and response data, and transmits the data response message to the client 4. (S
A16)

Next, the effect of the present embodiment will be described.

In this embodiment, since the client identifier (TE-Id) is included in the datagram header flowing between the relay device 3 and the server 1, the relay from the relay device 3 to the client 4 becomes possible, and the efficiency is improved. Communication between the relay device and the client can be realized.

In this embodiment, the TE-Id
And the client profile information are provided to the server 1, so that the server 1 can specify the data transmission destination client 4.

Next, a second embodiment of the present invention will be described in detail with reference to the drawings.

Referring to FIG. 12, a second embodiment of the present invention is characterized in that a client identifier is not included in a datagram header flowing between a gateway and a server, and that a plurality of clients are included in a profile response (SA5 '). Is different in that the merged profile is returned as the merge profile of the client.

Referring to FIG. 13, the difference is that the gateway 2 'has a client identifier storage unit 28'.
The profile management storage unit 25 'in FIG. 13 includes the identifier (TE-Id) shown in FIG. 8 and a corresponding list of client profiles.

Referring to FIG. 14, the server 1 'has the same hardware configuration, but differs in the processing contents. FIG.
The fourth profile management storage unit 15 'is composed of a merge profile shown in FIG. FIG. 15 shows a merge profile obtained by merging the profile list of FIG. In merging the profile lists, a method of including all the applications included in the profile list and maximizing the display size and the like is used.

Next, FIG. 12, FIG. 13, FIG. 14 and FIG.
The operation of the present embodiment will be described with reference to FIG.

The flow SA1-SA3 of the second embodiment shown in FIG. 12 is the same as the flow SA1-SA3 of the first embodiment, and the description is omitted.

A case in which server-initiated data communication is performed will be described. In the server-initiated data communication, the relay device 3 is provided with a device identifier (D-Id) corresponding to one or a plurality of clients connected to the relay device 3 as shown in FIG. ), Identifier (T
E-Id), a correspondence list including a client profile is stored, and the gateway 2 ′ stores identifiers (TE-Id) of one or more clients connected to the relay device of the communication destination shown in FIG. It is assumed that a correspondence list including a profile is stored.

First, when a data transmission request is issued from the user, the server 1 'starts the processing in FIG.

After analyzing the data transmission request from the user, the user request analysis unit 12 ′ stores the transmission data, the transmission data information, and the identifier (MT-Id) of the destination relay device included in the data transmission request in the memory 13 ′. It stores and sends a processing request to the main control unit 14 '. The transmission data information includes content type information of the transmission data. The content type information includes content type information such as images, texts, and moving images.

When the profile management storage unit 15 'does not store the merge profile of the data transmission destination relay device, the main control unit 14' issues a client profile request processing request to the message composition unit 16 '. The message composition unit 16 'constructs a client profile request message including the identifier (MT-Id) of the destination relay device, and transmits the message to the gateway 2'.
(SA4 ').

When the gateway 2 'receives the client profile request message from the server 1', the gateway 2 'shown in FIG.
To start the process.

After analyzing the client profile request message, the message analyzer 27 'issues a received message processing request to the main controller 24'. The main control unit 24 'merges the profile list corresponding to the identifier (M-Id) of the relay device included in the client profile request message from the profile management storage unit 25' as a single profile, and forms the merged profile into a message. Send to section 22 '. Next, the main control unit 24 '
Issues a client profile response processing request to the message composition unit 22 '. Message composition part 2
2 'constructs a client profile response message using the merge profile and transmits it to the server 1'. (SA5 ')

The server 1 ′ has a profile management storage unit 1
When the merge profile of the relay device of the transmission destination is stored in 5 ′, or when the client profile response message is received from the gateway 2 ′, FIG.
To start the process.

When receiving the client profile response message from the gateway 2 ', the message analysis unit 11' analyzes the client profile response message and stores the merge profile contained in the message in the profile management storage unit 15 '(FIG. 15). Then, it issues a received message processing request to the main control unit 14 '.

The main control unit 14 'converts the transmission data of the memory 13' according to the profile such as the display size included in the merge profile of the profile management storage unit 15 '. Next, the transmission data and transmission data information of the memory 13 'are sent to the message composition unit 16', and a data transmission processing request is issued to the message composition unit 16 '. The message construction unit 16 'constructs a data transmission message using the transmission data and the transmission data information, and transmits the data transmission message to the gateway 2'. (SA6 ')

When the gateway 2 'receives the data transmission message from the server 1', the processing in FIG. 13 starts.

After analyzing the data transmission message, the message analysis unit 27 'stores the transmission data and transmission data information in the message in the memory 23', and issues a request for processing the received message to the main control unit 24 '. Main control unit 2
4 ′ compares the content type information of the transmission data information of the memory 23 ′ with the profile list of the profile management storage unit 25 ′, determines the client identifier (TE-Id) of the client that transmits the data, and
To be stored.

For example, if the content type information is an image, a client profile that can process the image is searched from the profile list using the image as a search key.
When there are a plurality of searched client profiles, the largest client profile is selected by comparing the display size and the like, and the TE-Id corresponding to the client profile is determined. In selecting a client profile, a client profile having a minimum display size or the like and a minimum transmission data amount may be selected. Next, according to the profile such as the display size included in the client profile,
The transmission data in the memory 23 'is converted.

Next, the transmission data of the memory 23 ', TE-Id
To the message composition unit 26 ', and the message composition unit 2
6 ', a data transmission processing request is issued. The message composition unit 26 ′ composes a data transmission message using the transmission data and the TE-Id, and transmits the data transmission message to the relay device 3.
(SA7)

The flow SA7-SA8 of the second embodiment shown in FIG. 12 according to the second embodiment is the same as the flow SA7-SA8 of the first embodiment, and a description thereof will be omitted.

Next, a case in which client-initiated data communication is performed will be described. In the client-initiated data communication, the relay device 3 is provided with the device identifier (D-Id) corresponding to one or a plurality of clients connected to the relay device 3 as shown in FIG. ), An identifier (TE-Id), and a correspondence list including a client profile are stored.
It is assumed that an identifier (TE-Id) of one or more clients connected to the relay device of the communication destination illustrated in FIG. 8 and a correspondence list including a client profile are stored.

First, the client 4 transmits a data request message to the relay device 3. (SA9)

Since the flows SA9-SA10 of the second embodiment shown in FIG. 12 are the same as the flows SA9-SA10 of the first embodiment,
Description is omitted.

When the gateway 2 'receives the data request message shown in SA10 from the relay device 3, the gateway 2' starts the processing in FIG.

After analyzing the data request message, the message analyzer 21 'stores the datagram in the message in the memory 23', extracts the client identifier (TE-Id) from the datagram header, and stores the TE-Id in the client. It is stored in the identifier storage unit 28 '. Next, a received message processing request is issued to the main control unit 24 '. Main control unit 2
4 'sends the datagram in the memory 23' to the message composing unit 22 ', and issues a data request processing request to the message composing unit 22'. The message construction unit 22 'constructs a data request message using the datagram, and transmits the data request message to the server 1'. (SA11 ')

When the server 1 'receives the data request message from the gateway 2', it starts the processing in FIG.

After analyzing the data request message, the message analyzer 11 'issues a request for processing the received message to the main controller 14'. The main control unit 14 'stores response data to the request message from the data storage unit 17' in the memory 13 '.

Next, when the merge profile of the relay device to which the client which transmitted the data request message is connected is not stored in the profile management storage unit 15 ', the main control unit 14' stores the message in the message composition unit 16 '. On the other hand, it issues a client profile request processing request. The message composition unit 16 'constructs a client profile request message including the identifier (MT-Id) of the relay device to which the client is connected, and transmits the message to the gateway 2' (SA12 ').

When the gateway 2 'receives the client profile request message from the server 1', the gateway 2 'shown in FIG.
To start the process.

After analyzing the client profile request message, the message analyzer 27 'issues a request for processing the received message to the main controller 24'. The main control unit 24 'merges the profile list corresponding to the identifier (MT-Id) of the relay device included in the client profile request message from the profile management storage unit 25' as a single profile, and forms the merged profile into a message. Send it to unit 22. Next, the main control unit 2
4 'issues a client profile response processing request to the message composition unit 22'. The message composition unit 22 'constructs a client profile response message using the merge profile, and transmits it to the server 1' (SA13 ').

If the server 1 'holds a merge profile, a client profile request (SA
12 '), client profile response (SA13')
This flow may not be necessary.

In the case where the merge profile is included in the message of the data request (SA11 '), the flow of the client profile request (SA12') and the client profile response (SA13 ') may be omitted.

The server 1 'is a profile management storage unit 1.
When the merge profile of the relay device of the transmission destination is stored in 5 ′, or when the client profile response message is received from the gateway 2 ′, the processing in FIG. 14 is started.

When receiving the client profile response message from the gateway 2 ', the message analysis unit 11' analyzes the client profile response message, stores the merge profile included in the message in the profile management storage unit 15 ', and executes the main control. Part 1
4 ', a request for processing the received message is issued. The merge profile is managed for each identifier (MT-Id) of the relay device 3.

The main control unit 14 is the profile management storage unit 1
The response data in the memory 13 'is converted according to the profile such as the display size included in the merge profile 5'. Next, the response data is stored in the message
6 ′, and to the message composition unit 16 ′,
Issues a data response processing request. Message composition part 1
6 'constructs a data response message using the response data,
Transmit to gateway 2 '. (SA14 ')

When the gateway 2 'receives the data response message from the server 1', the processing in FIG. 13 starts.

After analyzing the data response message, the message analysis unit 27 'stores the response data in the message in the memory 2.
3 '. Next, the client identifier storage unit 2
It sends the client identifier (TE-Id) 8 'to the memory 23' and issues a received message processing request to the main controller 24 '. The main control unit 24 'searches for a profile from the profile list of the profile management storage unit 25' using the TE-Id of the memory 23 'as a search key. Next, the response data in the memory 23 'is converted according to the profile such as the display size included in the client profile. Next, the TE-Id of the memory 23 'and the response data are sent to the message composition unit 26', and the message composition unit 26 '
Issue a data response processing request. The message composition unit 26 ′ constructs a data response message using the response data and the TE-Id, and transmits the data response message to the relay device 3. (S
A15)

The flow SA15-SA16 of the second embodiment shown in FIG. 12 is the same as the flow SA15-SA16 of the first embodiment, and a description thereof will be omitted.

In the present embodiment, since the client identifier (TE-Id) is included in the datagram header flowing between the relay device 3 and the gateway 2 ′, the relay from the relay device 3 to the client 4 becomes possible. Efficient communication between the relay device and the client can be realized.

Further, in the present embodiment, the TE-Id
And client profile information are provided to the gateway 2 ', but not to the server 1', so that it is unnecessary to change the server 1 'configured by the existing processing system.

In the configuration of the data communication system, FIG.
As shown in the eighth server / gateway 1-2, the server and the gateway in the first and second embodiments may be configured by one device.

Next, an embodiment of a medium in which a communication program of the present invention is recorded will be described. In the present embodiment, the server 1, gateway 2, relay device 3, client 4, and server / gateway 1-2 of the present invention in the first and second embodiments of the present invention are a data processing device, a storage device, respectively. And a storage medium on which a communication program is recorded (not particularly shown). This recording medium may be a magnetic disk, a semiconductor memory, a CD-ROM, or another recording medium.

The communication program for controlling the server 1 is read from the recording medium into the storage device of the server 1, and stored in the data processing device by the message analyzing units 11, 11 ', the user request analyzing units 12, 12', the main control unit 14 and the like. , 14 ′ and the message composition units 16, 16 ′ are generated, and the memory 1 is stored in the storage device.
Areas 3 and 13 ', profile management storage sections 15 and 15', and data storage sections 17 and 17 'are secured and their operations are controlled.

The data processing device controls the server 1 in the first and second embodiments under the control of the communication program.
Execute the same processing as the communication processing.

A communication program for controlling the gateway 2 is read from a recording medium into the storage device of the gateway 2 and transmitted to the data processing device by the message analyzing units 21 and 21.
1 ′, message constituent units 22, 22 ′, main control unit 24,
24 ′, the message composition units 26 and 26 ′, and the message analysis units 27 and 27 ′ are generated.
23 ', an area for the profile management storage units 25, 25' is secured and its operation is controlled. In the embodiment of the medium corresponding to the second embodiment, an area of the client identifier storage unit 28 'is further secured in the storage device.

The data processing device executes the same processing as the communication processing of the gateway 2 in the first and second embodiments under the control of the above-mentioned communication program.

A communication program for controlling the relay device 3 includes:
The data is read from the recording medium to the storage device of the relay device 3 and stored in the data processing device by the message analysis units 31, 31 ', the message configuration units 32, 32', the main control units 34, 34 ', the message configuration units 36, 36' Message analyzer 37,3
7 'is generated, the areas of the memories 33, 33' and the profile management storage units 35, 35 'are secured in the storage device, and the operation is controlled.

The data processing device executes the same processing as the communication processing of the relay device 3 in the first and second embodiments under the control of the above-mentioned communication program.

The communication program for controlling the client 4 is read from the recording medium into the storage device of the relay device 3,
An area for storing necessary data and the like in the storage device is secured, and the operation of the data processing device is controlled.

The data processing device executes the same processing as the communication processing of the client 4 in the first and second embodiments under the control of the above-mentioned communication program.

The communication program for controlling the server / gateway is read from the recording medium into the storage device of the server / gateway, and the data processing device generates means for realizing the functions of the server and the gateway described above. In the same way as the server and the gateway, areas such as a profile management storage unit, a memory, and a data storage unit are secured, and their operations are controlled.

The data processing device controls the server / server in the first and second embodiments under the control of the communication program.
Executes the same processing as the communication processing of the gateway.

[0121]

Next, the operation of this embodiment will be described with reference to specific examples. Such an example corresponds to the first embodiment of the present invention.

In this embodiment, as shown in FIG. 9, a WAP terminal is provided as a client, a WAP mobile terminal is provided as a relay device, a WAP gateway is provided as a gateway, and a WAP server is provided as a server. ing. FIG. 4 shows the hardware configuration of the WAP mobile terminal,
FIG. 5 shows a WAP gateway, and FIG. 6 shows a WAP server.

The protocol stack between the devices is shown in FIG.
0 is shown. The datagram of the message transmitted / received between the respective devices is shown in FIG. 11, the datagram between the WAP server and the WAP gateway is an Internet section datagram P1, and the datagram between the WAP gateway and the WAP mobile terminal is wireless. Section datagram P2, WAP
The datagram between the mobile terminal and the WAP terminal is a terminal I / F section datagram P3.

The Internet section datagram P1 is composed of fields of an IP header, a TCP header, an HTTP header, and user data. The IP header includes fields of a source address, a destination address, and various IP parameters. The TCP header is composed of a source port, a destination port, and various TCP parameter fields. HTTP header is WAP mobile terminal identifier (MT-Id), WAP terminal identifier (TE-I
d), composed of various HTTP parameters. The HTTP parameter field also includes transmission data information on transmission data. User data is composed of transmission data.
The client profile list is transmitted as user data.

The wireless section datagram P2 is a WDP header, W
It consists of TP header, WSP header, and user data fields. The WDP header includes fields of a source address, a destination address, a source port, a destination port, and various WDP parameters. WTP header is various WTP
Consists of parameter fields. WSP header is W
It consists of AP terminal identifier (TE-Id) and various WSP parameter fields. The various WSP parameter fields also include transmission data information on transmission data. User data is composed of transmission data. The client profile list is transmitted as user data.

The terminal I / F section datagram P3 is composed of MS header and user data fields. The MS header includes a device identifier (D-Id) and various MS parameter fields. The various MS parameter fields also include transmission data information on transmission data. The client profile is transmitted as user data.

In this embodiment, the identifier (TE-Id) in FIGS. 7 and 8 corresponds to the WAP terminal identifier (TE-Id).

Next, the overall operation of this embodiment will be described in detail with reference to FIGS. 4, 5, 6, 7, 8, 9, 10, and 11. FIG.

First, registration of a client profile will be described.

[0130] One or more WAP terminals 4 transmit a profile registration message to WAP mobile terminal 3. (FIG. 9
SB1, SB2). The datagram of the message is terminal I
/ F section datagram P3.

When the WAP mobile terminal 3 receives the profile registration message from the WAP terminal 4, it starts the processing shown in FIG.

After analyzing the profile registration message, the message analyzer 31 analyzes the WAP mobile terminal profile included in the user data field of the terminal I / F section datagram P3 and the device identifier included in the datagram header.
(D-Id) is stored in the profile management storage unit 35. Next, a request for processing the received message is issued to the main control unit 34.

The main control unit 34 has the profile management storage unit 3
5, a WAP terminal identifier (TE-Id) that can be uniquely associated with the D-Id is determined, and the profile management storage unit 35
Store TE-Id in. Next, the profile management storage unit 3
The profile list composed of the pair profile group of the TE-Id and the profile stored in 5 is sent to the message composition unit 32. Next, the Port / Address of the WAP mobile terminal 3 stored in the memory 33 and the WAP gateway 2
The port / address is sent to the message composition unit 32, and a processing request for profile notification is issued to the message composition unit 32.

The message composing unit 32 composes a profile notification message in the format of the wireless section datagram P2 using the profile list and Port / Address, and transmits the message to the WAP gateway 2 (SB3). The profile notification message is S-Connect.req of WAP-WSP protocol.
Respond to messages.

When the WAP gateway 2 receives the profile notification message from the WAP mobile terminal 3, it starts the processing in FIG.

After analyzing the profile notification message, the message analysis unit 21 stores the profile list included in the user data field of the wireless section datagram P2 in the profile management storage unit 25, and stores the Port / Address included in the datagram header in the memory. 23. The profile list is the WAP mobile terminal identifier of the WAP mobile terminal 3.
It is managed for each (MT-Id). Next, a request for processing the received message is issued to the main control unit 24. Next, the Port / Address of the memory 23 is sent to the message composition unit 26,
It issues a profile notification confirmation processing request to the message composition unit 26.

The message composing section 26 composes a profile notification confirmation message in the format of the wireless section datagram P2 using Port / Address, and transmits it to the WAP mobile terminal 3 (SB3a). The profile notification confirmation message corresponds to the S-Connect.res message of the WAP-WSP protocol.

Next, a case in which server-initiated data communication is performed will be described. In server-led data communication,
By the above-described processing of SB1 to SBa3, the WAP mobile terminal 3 has a device identifier (D-Id) corresponding to one or a plurality of WAP terminals 4 connected to the WAP mobile terminal 3 as shown in FIG. A correspondence list including a terminal identifier (TE-Id) and a client profile is stored, and the WAP gateway 2 has one or more WAP terminals 4 connected to the WAP mobile terminal 3 of the communication destination shown in FIG. It is assumed that a correspondence list including a terminal identifier (TE-Id) and a client profile is stored.

First, when a data transmission request is issued from the user, the WAP server 1 starts the processing in FIG.

After analyzing the data transmission request from the user, the user request analysis unit 12 stores in the memory 13 the transmission data, transmission data information, and the WAP mobile terminal identifier (MT-Id) of the data transmission destination included in the data transmission request. Then, a processing request for the data transmission request is sent to the main control unit 14. The transmission data information includes content type information of the transmission data. The content type information includes content type information such as images, texts, and moving images.

The main control unit 14 is the profile management storage unit 1
5 does not store the profile list of the WAP mobile terminal 3 of the data transmission destination, the Port / Address of the WAP server 1 stored in the memory 13 and the WAP gateway 2
Port / Address and MT-Id are sent to the message composition unit 16,
It issues a client profile request processing request to the message composition unit 16. The message composition unit 16
Using the Port / Address and the MT-Id, a client profile request message is formed in the format of the Internet section datagram P1, and transmitted to the WAP gateway 2 (SB4). The client profile request message corresponds to the ccq-message message of the WAP-PAP protocol.

When the WAP gateway 2 receives the client profile request message from the WAP server 1, FIG.
To start the process.

After analyzing the client profile request message, the message analyzer 27 analyzes the Port / A included in the datagram header of the Internet section datagram P1.
It sends ddress and MT-Id to the memory 23 and issues a request for processing the received message to the main control unit 24. Main control unit 2
4 selects a profile list corresponding to the MT-Id stored in the memory 23 from the profile management storage unit 25 and sends it to the message composition unit 22. Next, the port / address and MT-Id stored in the memory 23 are sent to the message composition unit 22, and a processing request for a client profile response is issued to the message composition unit 22. The message composition unit 22 includes a profile list, Port / Address, MT
Using -Id, a client profile response message is formed in the format of the Internet section datagram P1, and transmitted to the WAP server 1 (SB5). The client profile response message corresponds to the ccq-response message of the WAP-PAP protocol.

The WAP server 1 has a profile management storage unit 1
If the profile list of the destination WAP mobile terminal 3 is stored in 5 or if a client profile response message is received from the WAP gateway 2, the processing in FIG.

When receiving the client profile response message from the WAP gateway 2, the message analysis unit 11 analyzes the client profile response message, and then stores the profile list included in the user data field of the Internet section datagram P1 into the profile management storage unit 15. , Port / Address, MT
-Id is stored in the memory 13. Profile list is WAP
It is managed for each WAP mobile terminal identifier (MT-Id) of the mobile terminal 3.

Next, a request for processing the received message is issued to the main control unit 14. The main control unit 14 compares the content type information of the transmission data information stored in the memory 13 with the profile list of the profile management unit 15, determines the client identifier (TE-Id) of the WAP terminal 4 that can transmit data, The TE-Id is stored in the memory 13.

For example, if the content type information is an image, a client profile that can process the image is searched from the profile list using the image as a search key.
When there are a plurality of searched client profiles, the largest client profile is selected by comparing the display size and the like, and the TE-Id corresponding to the client profile is determined. In selecting a client profile, a client profile having a minimum display size or the like and a minimum transmission data amount may be selected.

Next, the transmission data stored in the memory 13 is converted according to the profile such as the display size included in the client profile. Next, the transmission data, Port / Address,
The MT-Id and the TE-Id are sent to the message composition unit 16, and a data transmission processing request is issued to the message composition unit. The message composition unit 16 includes transmission data, Port / Address, MT-I
d, a data transmission message is formed in the format of the Internet section datagram P1 using the TE-Id and transmitted to the WAP gateway 2 (SB6). The data transmission message corresponds to a push-message message of the WAP-PAP protocol.

When the WAP gateway 2 receives the data transmission message from the WAP server 1, it starts the processing in FIG.

After analyzing the data transmission message, the message analysis unit 27 stores the datagram of the Internet section datagram P1 in the memory 23, and issues a request for processing the received message to the main control unit 24. Main control unit 2
4 sends the Port / Address, the mobile terminal identifier (MT-Id), and the client identifier (TE-Id) included in the Internet section datagram header stored in the memory 23 to the message composing unit 22, and On the other hand, it issues a data transmission confirmation processing request.

Next, the Internet section datagram P1 stored in the memory 23 is converted into a radio section datagram P2 together with the address conversion, and the message composition unit 2
6 and issues a data transmission processing request to the message composition unit 26. In the address conversion, the main control unit 24 is included in the Internet section datagram header.
Port / Address is converted to a wireless section address based on the MT-Id.

The message composing section 26 composes a data transmission message in the format of the radio section datagram P2 using the datagram, and transmits it to the WAP mobile terminal 3 (S
B7). Data transmission message is P of WAP-OTA protocol.
Corresponds to the o-ConfirmedPush.req message. The message composition unit 22 composes a data transmission confirmation message using the Port / Address, MT-Id, and TE-Id in the Internet section datagram P1, and transmits the message to the WAP server 1 (SB
6a). The data transmission confirmation message corresponds to a push-response message of the WAP-PAP protocol.

When the WAP mobile terminal 3 receives the data transmission message from the WAP gateway 2, it starts the processing in FIG.

After analyzing the data transmission message, the message analysis section 37 transmits the transmission data contained in the user data field of the data section P2 of the radio section, the Port / Address contained in the datagram header, and the client identifier (TE-I).
d), the mobile terminal identifier (MT-Id) is stored in the memory 33, and a received message processing request is issued to the main control unit 34.

The main controller 34 stores the Port / Address, TE-Id, and MT-Id stored in the memory 33 into the message
And issues a data transmission confirmation processing request to the message composition unit 32. Next, a device identifier (D-Id) is searched from the profile list stored in the profile management storage unit 35 using the TE-Id stored in the memory 33 as a search key. Next, the retrieved D-Id and the transmission data stored in the memory 33 are stored in the message
6 and issues a data transmission processing request to the message composition unit 36.

The message composing section 36 composes a data transmission message in the format of the terminal I / F section datagram P3 using the D-Id and the transmission data, and transmits it to the WAP terminal 4 (SB8). The message composition unit 32 has Port / Address, TE
A data transmission confirmation message is formed in the format of the wireless section datagram P2 using the -Id and MT-Id, and transmitted to the WAP gateway 2 (SB7a). The data transmission confirmation message corresponds to the Po-ConfirmedPush.res message of the WAP-OTA protocol.

Next, a case in which client-initiated data communication is performed will be described. In the client-led data communication, the processing of SB1 to SBa3 described above
The AP mobile terminal 3 includes a device identifier (D-Id), a WAP terminal identifier (TE-Id) corresponding to one or a plurality of WAP terminals 4 connected to the WAP mobile terminal 3 as shown in FIG. Correspondence list including profile is stored,
The WAP gateway 2 has a communication destination W shown in FIG.
It is assumed that a correspondence list including a WAP terminal identifier (TE-Id) of one or a plurality of WAP terminals connected to the AP mobile terminal 3 and a client profile is stored.

[0158] First, the WAP terminal 4
A data request message is transmitted (SB9). The datagram of the message is composed of the terminal I / F section datagram P3.

When the WAP mobile terminal 3 receives the data request message from the WAP terminal 4, the processing in FIG. 4 starts.

After analyzing the data request message, the message analyzer 31 compares the device identifier (D-Id) contained in the datagram header of the terminal I / F section datagram P3 and the data request destination HTTP address contained in the user data field. It is stored in the memory 33 and issues a received message processing request to the main control unit 34.

The main control unit 34 uses the D-Id stored in the memory 33 as a search key and
The client identifier (TE-Id) is searched from the profile list stored in the
Send to Next, the Port / Address of the WAP mobile terminal 3 and the Port / Addres of the WAP gateway 2 stored in the memory 33 are stored.
s, the HTTP address of the data request destination
And issues a data request processing request to the message composition unit 32.

The message composing section 32 has Port / Address, TE
A data request message is formed in the format of the wireless section datagram P2 using the -Id and the data request destination HTTP address, and transmitted to the WAP gateway 2 (SB10).
The data request destination HTTP address is the wireless section datagram P2
Is added to the WSP header. Data request message is WAP
-Corresponds to the WSP protocol S-MethodInvoke.req message.

When the WAP gateway 2 receives the data request message from the WAP mobile terminal 3, it starts the processing shown in FIG.

After analyzing the data request message, the message analyzer 21 stores the datagram of the wireless section datagram P2 in the memory 23, and stores the Port / Address and the client identifier (TE-Id) included in the datagram header in the memory 23. To be stored. Next, a received message processing request is issued to the main control unit 24. The main control unit 24 is a memory 23
Is transmitted to the message composition unit 26, and a data request confirmation processing request is issued to the message composition unit 26.

Next, the radio section datagram P2 stored in the memory 23 is converted into an Internet section datagram P1 together with the address conversion, and the message composing section 2 is converted.
Send to 2. Next, the mobile terminal identifier (MT) is obtained from the Port / Address of the WAP mobile terminal 3 included in the wireless section datagram header.
-Id), and sends it to the message composition unit 22 to issue a data request processing request to the message composition unit 22. In the address conversion, the main control unit 24 transmits the data request destination HTT included in the WSP header of the wireless section datagram P2.
Port / Address is converted to an Internet section address based on the P address.

The message constructing section 22 includes a datagram, MT
Using -Id, a data request message is formed in the format of the Internet section datagram P1, and transmitted to the WAP server 1 (SB11). Data request message is HTTP
Corresponds to the protocol HTTP request message. The message composing unit 26 composes a data request confirmation message in the format of the wireless section datagram P2 using the Port / Address and TE-Id, and transmits the message to the WAP mobile terminal 3 (SB1)
0a). The data request confirmation message corresponds to the S-MethodInvoke.res message of the WAP-WSP protocol.

When the WAP server 1 receives the data request message from the WAP gateway 2, it starts the processing in FIG.

[0168] After analyzing the data request message, the message analysis unit 11 analyzes the Port / Address, WAP mobile terminal identifier (MT-Id), and WAP terminal identifier (TE-Id) included in the datagram header of the Internet section datagram P1. Memory 13
And issues a received message processing request to the main control unit 14. The main control unit 14 extracts response data to the request message from the data storage unit 17 and stores it in the memory 13.

Next, the main control unit 14 stores the profile list of the WAP mobile terminal 3 to which the WAP terminal 4 that transmitted the data transmission message is connected or the pair profile of the WAP terminal 3 in the profile management storage unit 15. If not, the Port / Address and MT-Id are sent to the message composition unit 16, and the message
Issues a processing request for the client profile request.
The message composition unit 16 uses Port / Address and MT-Id,
A client profile request message is formed in the format of the Internet section datagram P1, and transmitted to the WAP gateway 2 (SB12). The client profile request message is a WAP-PAP protocol ccq-
Corresponds to the message message.

When the WAP gateway 2 receives the client profile request message from the WAP server 1, FIG.
To start the process.

After analyzing the client profile request message, the message analyzer 27 analyzes Port / A included in the datagram header of the Internet section datagram P1.
It sends ddress and MT-Id to the memory 23 and issues a request for processing the received message to the main control unit 24. Main control unit 2
4 selects a profile list for the MT-Id stored in the memory 23 from the profile management storage unit 25 and sends it to the message composition unit 22. Next, the port / address and MT-Id stored in the memory 23 are sent to the message composition unit 22, and a processing request for a client profile response is issued to the message composition unit 22. The message composition unit 22 includes a profile list, Port / Address, MT
Using -Id, a client profile response message is formed in the format of the Internet section datagram P1, and transmitted to the WAP server 1 (SB13). The client profile response message corresponds to the ccq-response message of the WAP-PAP protocol.

The WAP server 1 has the profile management storage 1
5 holds the profile list of the WAP mobile terminal 3 to which the WAP terminal 4 that has transmitted the data transmission message is connected or the pair profile of the WAP terminal 4 that has made the data transmission request. ), Client profile response
The flow of (SB13) may not be necessary.

When a client profile is included in the message of the data request (SB11), the flow of the client profile request (SB12) and the flow of the client profile response (SB13) may be omitted.

The WAP server 1 sends the client identifier (TE-ID) to the message of the client profile request (SB12).
The configuration may also be such that the WAP gateway 2 responds only to a pair of pair profiles corresponding to the TE-Id in the client profile response (SB13), including Id).

The WAP server 1 has a profile management storage 1
5 stores the profile list of the destination WAP mobile terminal 3 or the pair profile of the WAP terminal 4 that has made the data transmission request, or when a client profile response message is received from the WAP gateway 2, the processing in FIG. Start.

When receiving the client profile response message from the WAP gateway 2, the message analysis unit 11 analyzes the client profile response message, and then analyzes the client profile response message and returns the profile list or the destination WAP terminal included in the user data field of the Internet section datagram P1. 4 is stored in the profile management storage unit 15. The profile list or pair profile is the WAP mobile terminal 3 W
It is managed for each AP mobile terminal identifier (MT-Id). Next, a request for processing the received message is issued to the main control unit 14.

The main control unit 14 uses the TE-Id stored in the memory 13 as a search key and
The client profile is searched from the profile list or the pair profile stored in No.5.

Next, the response data stored in the memory 13 is converted according to the profile such as the display size included in the searched client profile. Next, it sends the Port / Address, MI-Id, TE-Id, and response data to the message composition unit 16 and issues a data response processing request to the message composition unit 16. The message composition unit 16 composes a data response message in the format of the Internet section datagram P1 using the Port / Address, MT-Id, TE-Id, and response data, and transmits the data response message to the WAP gateway 2 (SB14). Data response message is HTTP
Corresponds to the HTTPresponse message of the protocol.

When the WAP gateway 2 receives the data response message from the WAP server 1, it starts the processing in FIG.

After analyzing the data response message, the message analyzer 27 stores the datagram of the Internet section datagram P1 in the memory 23, and issues a request for processing the received message to the main controller 24. Main control unit 2
4 converts the Internet section datagram P1 stored in the memory 23 into a wireless section datagram P2 together with the address conversion and sends it to the message composition unit 26, and issues a data response processing request to the message composition unit 26.

In the address conversion, the main control unit 24 converts Port / Address into an address of a wireless section based on the MT-Id included in the Internet section datagram header.
The message composing unit 26 composes a data response message in the format of the wireless section datagram P2 using the datagram, and transmits it to the WAP mobile terminal 3 (SB15). Data response message is S-MethodRe of WAP-WSP protocol.
Corresponds to sult.req message.

When the WAP relay device 3 receives the data response message from the WAP gateway 2, it starts the process shown in FIG.

After analyzing the data response message, the message analysis unit 37 analyzes the response data included in the user data field of the wireless section datagram P2, the Port / Address included in the datagram header, and the client identifier (TE-I
d), the mobile terminal identifier (MT-Id) is stored in the memory 33, and a received message processing request is issued to the main controller 34.

The main controller 34 stores the Port / Address, TE-Id, and MT-Id stored in the memory 33 into the message
And issues a data transmission confirmation processing request to the message composition unit 32. Next, a device identifier (D-Id) is searched from the profile list stored in the profile management storage unit 35 using the TE-Id stored in the memory 33 as a search key. Next, the retrieved D-Id and the response data stored in the memory 33 are stored in the message
6 and issues a data response processing request to the message composition unit 36. The message composing unit 36 composes a data transmission message in the format of the terminal I / F section datagram P3 using the D-Id and the response data, and transmits the message to the WAP terminal 4 (SB16).

The message composing section 32 has Port / Address, TE
A data response confirmation message is formed in the format of the wireless section datagram P2 using the -Id and MT-Id, and transmitted to the WAP gateway 2 (SB15a). Data response confirmation message is Po-ConfirmedPush.res of WAP-OTA protocol.
Respond to messages.

Next, a second embodiment will be described with reference to the drawings. Such an example corresponds to the second embodiment of the present invention.

The present embodiment has the same device configuration as the first embodiment as shown in FIG.
The operation of the gateway and the operation of the WAP server as a server are different from those of the first embodiment.

Datagrams of messages transmitted and received between the respective devices are shown in FIG. 17, and datagrams between the WAP server and the WAP gateway are internet section datagrams P.
1 ′, the datagram between the WAP gateway and the WAP mobile terminal is a wireless section datagram P2, and the datagram between the WAP mobile terminal and the WAP terminal is a terminal I / F section datagram P3.

The Internet section datagram P1 'is IP
It consists of header, TCP header, HTTP header, and user data fields. The IP header is the source address,
It consists of fields for the destination address and various IP parameters. The TCP header contains the source port, destination port,
It consists of various TCP parameter fields. HTTP
The header includes a WAP mobile terminal identifier (MT-Id) and various HTTP parameters. The HTTP parameter field also includes transmission data information on transmission data. User data is composed of transmission data. The client merge profile is transmitted as user data.

The wireless section datagram P2 is a WDP header, W
It consists of TP header, WSP header, and user data fields. The WDP header includes fields of a source address, a destination address, a source port, a destination port, and various WDP parameters. WTP header is various WTP
Consists of parameter fields. WSP header is W
It consists of AP terminal identifier (TE-Id) and various WSP parameter fields. The various WSP parameter fields also include transmission data information on transmission data. User data is composed of transmission data. The client profile list is transmitted as user data.

The terminal I / F section datagram P3 is composed of MS header and user data fields. The MS header includes a device identifier (D-Id) and various MS parameter fields. The various MS parameter fields also include transmission data information on transmission data. The client profile is transmitted as user data.

In the present embodiment, the identifier (TE-Id) in FIGS. 7 and 8 corresponds to the WAP terminal identifier (TE-Id).

Next, FIG. 13, FIG. 14, FIG. 15, FIG.
The overall operation of the present embodiment will be described in detail with reference to FIG.

The flow S of the second embodiment shown in FIG.
B1-SB3a corresponds to the flow SB1-SB of the first embodiment.
3a, the description is omitted.

A case where server-initiated data communication is performed will be described. In the data communication led by the server, the WAP mobile terminal 3 is provided with the device identifier (1) corresponding to one or a plurality of WAP terminals connected to the WAP mobile terminal 3 as shown in FIG. D
-Id), an identifier (TE-Id), and a corresponding list including a client profile are stored in the WAP gateway 2 ', and one or more WAP terminals connected to the communication destination WAP mobile terminal shown in FIG. (TE-Id) and a correspondence list including a client profile are stored.

First, when a data transmission request is issued from the user, the WAP server 1 'starts the processing in FIG.

After analyzing the data transmission request from the user, the user request analysis unit 12 'stores the transmission data, transmission data information, and the WAP mobile terminal identifier (MT-Id) of the data transmission destination included in the data transmission request in the memory 13'. And sends a processing request for the data transmission request to the main control unit 14 '. The transmission data information includes content type information of the transmission data. The content type information includes content type information such as images, texts, and moving images.

When the profile management storage unit 15 'does not store the merge profile of the data transmission destination WAP mobile terminal, the main control unit 14' stores the Port / Address of the WAP server 1 'stored in the memory 13'. Port / Address and MT-Id of WAP gateway 2 '
6 'and issues a client profile request processing request to the message composition unit 16'. The message composition unit 16 'constructs a client profile request message in the format of the Internet section datagram P1' using Port / Address and MT-Id, and transmits it to the WAP gateway 2 '(SB4'). The client profile request message is ccq-me of WAP-PAP protocol.
Corresponds to ssage message.

Upon receiving the client profile request message from the WAP server 1 ', the WAP gateway 2' starts the processing in FIG.

[0200] After analyzing the client profile request message, the message analyzing unit 27 'analyzes the client profile request message and outputs the Pogram included in the datagram header of the Internet section datagram P1'.
rt / Address and MT-Id are sent to the memory 23 ', and the main control unit 2
4 ', a request for processing the received message is issued. The main control unit 24 'selects a profile list corresponding to the MT-Id stored in the memory 23' from the profile management storage unit 25 ', and merges it as a single profile. Next, the merged profile is sent to the message composition unit 22 '. Next, the port / address and MT-Id stored in the memory 23 'are sent to the message composition unit 22', and a processing request for a client profile response is issued to the message composition unit 22 '. The message composition unit 22 ′ composes a client profile response message in the format of the Internet section datagram P 1 ′ using the merge profile, Port / Address, and MT-Id, and
It is transmitted to the P server 1 '(SB5'). The client profile response message conforms to the WAP-PAP protocol.
Corresponds to the ccq-response message.

The WAP server 1 ′ stores the merge profile of the destination WAP mobile terminal in the profile management storage unit 15 ′, or the WAP gateway 2 ′.
When the client profile response message is received, the processing in FIG. 14 starts.

When receiving the client profile response message from the WAP gateway 2 ′, the message analysis unit 11 ′ analyzes the client profile response message and then analyzes the Internet section datagram P1 ′.
Stored in the profile management storage unit 15 ′ (FIG. 15),
Port / Address and MT-Id are stored in the memory 13 '. The merge profile is the WAP mobile terminal identifier (M
It is managed for each T-Id). Next, a request for processing the received message is issued to the main control unit 14 '.

[0203] The main control unit 14 'operates according to the profile such as the display size included in the merge profile stored in the profile management storage unit 15'.
The transmission data stored in 3 'is converted. Next, the transmission data, transmission data information, Port / Address, and MT-Id stored in the memory 13 'are sent to the message composition unit 16', and a data transmission processing request is issued to the message composition unit 16 '. . The message composing section 16 'constructs a data transmission message in the form of the Internet section datagram P1' using the transmission data, transmission data information, Port / Address, and MT-Id, and transmits the message to the WAP gateway 2 '( SB6 ').

[0204] The transmission data information is added to the HTTP header of the Internet section datagram P1 '. The data transmission message corresponds to a push-message message of the WAP-PAP protocol.

When the WAP gateway 2 'receives the data transmission message from the WAP server 1', the processing in FIG. 13 starts.

[0206] After analyzing the data transmission message, the message analyzer 27 'analyzes the Internet section datagram P1'.
Is stored in the memory 23 ', and the main control unit 2
4 ', a request for processing the received message is issued. The main control unit 24 'sends the Port / Address and the mobile terminal identifier (MT-Id) included in the Internet section datagram header stored in the memory 23' to the message composition unit 22 ', and sends the message to the message composition unit 22'. Issue a data transmission confirmation processing request. Next, the content type information of the transmission data information included in the HTTP header of the Internet section datagram P1 ′ stored in the memory 23 ′ is compared with the profile list of the profile management storage unit 25 ′, and the WAP terminal capable of transmitting data is compared. 4 is determined, and the TE-Id is stored in the client identifier storage unit 28 '.

For example, if the content type information is an image, a client profile capable of processing the image is searched from the profile list using the image as a search key.
When there are a plurality of searched client profiles, the largest client profile is selected by comparing the display size and the like, and the TE-Id corresponding to the client profile is determined. In selecting a client profile, a client profile having a minimum display size or the like and a minimum transmission data amount may be selected.

Next, transmission data included in the user data field of the Internet section datagram P1 ′ stored in the memory 23 ′ is converted according to the profile such as the display size included in the client profile. Next, the Internet section datagram P1 'stored in the memory 23' is converted into a wireless section datagram P2 together with the address conversion and sent to the message composing section 26 '. Next, the client identifier storage unit 2
The TE-Id stored in the message composition unit 26 '
And issues a data transmission processing request to the message composition unit 26 '. In the address conversion, the main control unit 24 'converts Port / Address into an address of a wireless section based on the MT-Id included in the Internet section datagram header. The message construction unit 26 'is a datagram, TE
Using -Id, a data transmission message is formed in the format of the wireless section datagram P2 and transmitted to the WAP mobile terminal 3 (SB7). The data transmission message corresponds to the Po-ConfirmedPush.req message of the WAP-OTA protocol.
The message composing unit 22 'constructs a data transmission confirmation message in the form of the Internet section datagram P1' using the Port / Address and MT-Id, and transmits it to the WAP server 1 '(SB6a'). The data transmission confirmation message corresponds to a push-response message of the WAP-PAP protocol.

A flow S of the second embodiment shown in FIG.
B7-SB8 corresponds to the flow SB7-SB8 of the first embodiment.
Therefore, the description is omitted.

[0210] Next, a case in which client-initiated data communication is performed will be described. In the client-led data communication, the processing of SB1 to SB3a described above
The AP mobile terminal 3 includes a device identifier (D-Id), an identifier (TE-Id), and a client profile corresponding to one or a plurality of WAP terminals connected to the WAP mobile terminal 3 as shown in FIG. The WAP gateway 2 stores an identifier (TE-address) of one or more WAP terminals connected to the communication destination WAP mobile terminal shown in FIG.
Id), it is assumed that a correspondence list including a client profile is stored.

[0211] First, the WAP terminal 4
Send a data request message. (SB9)

The flow S of the second embodiment shown in FIG.
B9-SB10 corresponds to the flow SB9-SB of the first embodiment.
Since it is the same as 10, description is omitted.

When WAP gateway 2 ′ receives the data request message shown in SB10 from WAP mobile terminal 3, WAP gateway 2 ′ starts the processing in FIG.

[0214] After analyzing the data request message, the message analyzer 21 'stores the datagram of the wireless section datagram P2 in the memory 23', extracts the client identifier (TE-Id) included in the datagram header, and extracts the TE. -Id is stored in the client identifier storage unit 28 '. Next, the Port / Address included in the datagram header and the TE-Id stored in the client identifier storage unit 28 'are stored in the memory 2
3 ', and issues a received message processing request to the main control unit 24'.

[0215] The main control unit 24 'transmits the Port / Address and TE-Id stored in the memory 23' to the message composing unit 26 '.
And issues a data request confirmation processing request to the message composition unit 26 '. Next, the wireless section datagram P2 in the memory 23 'is converted into an Internet section datagram P1' together with the address conversion and sent to the message composing section 22 '. Next, a mobile terminal identifier (MT-Id) is determined from the Port / Address of the WAP mobile terminal 3 included in the wireless section datagram header, sent to the message composition unit 22 ', and sent to the message composition unit 22' for the data request. Issue a processing request.

In the address conversion, the main control unit 24 'converts Port / Address to an Internet section address based on the data request destination HTTP address contained in the WSP header of the wireless section datagram P2. Message composition part 2
2 ′ uses a datagram and MT-Id to form a data request message in the form of an Internet section datagram P1 ′ and transmits it to the WAP server 1 ′ (SB1
1 '). The data request message is HTTP protocol HTTP
Corresponds to the request message.

[0217] The message composing unit 26 'has Port / Address,
Using the TE-Id, a data request confirmation message is formed in the format of the wireless section datagram P2, and transmitted to the WAP mobile terminal 3 (SB10a). The data request confirmation message corresponds to the S-MethodInvoke.res message of the WAP-WSP protocol.

When the WAP server 1 'receives the data request message from the WAP gateway 2', it starts the processing shown in FIG.

[0219] After analyzing the data request message, the message analyzer 11 'analyzes the Internet section datagram P1'.
And stores the Port / Address and WAP mobile terminal identifier (MT-Id) included in the datagram header in the memory 13 ', and issues a received message processing request to the main control unit 14'. The main controller 14 'retrieves response data to the request message from the data storage 17' and stores it in the memory 13 '.

Next, the main control unit 14 'sends the data request message to the profile management storage unit 15'.
If the merge profile of the WAP mobile terminal to which the P terminal is connected is not stored, Port / Address, MT-Id
To the message composition unit 16 ', and the message composition unit 1
6 ', a processing request for the client profile request is issued.

The message constructing section 16 ′ is composed of Port / Address,
Using the MT-Id, a client profile request message is formed in the format of the Internet section datagram P1 'and transmitted to the WAP gateway 2' (SB1
2 '). Client profile request message is WAP
-Corresponds to the PAP protocol ccq-message message.

When the WAP gateway 2 'receives the client profile request message from the WAP server 1', the processing in FIG. 13 starts.

[0223] After analyzing the client profile request message, the message analysis unit 27 'analyzes the PoI contained in the datagram header of the Internet section datagram P1'.
rt / Address and MT-Id are sent to the memory 23 ', and the main control unit 2
4 ', a request for processing the received message is issued. The main control unit 24 'stores the profile list for the MT-Id stored in the memory 23' in the profile management storage unit 2.
Select from 5 'and merge as a single profile. Next, the merged profile is sent to the message composition unit 22 '. Next, the port / address and MT-Id stored in the memory 23 'are sent to the message composition unit 22', and a processing request for a client profile response is issued to the message composition unit 22 '. The message composition unit 22 ′ composes a client profile response message in the format of the Internet section datagram P 1 ′ using the merge profile, Port / Address, and MT-Id, and
It is transmitted to the P server 1 '(SB13'). The client profile response message corresponds to the ccq-response message of the WAP-PAP protocol.

When the WAP server 1 'holds the merge profile, the client profile request
(SB12 '), client profile response (SB1')
The flow of 3 ′) may not be necessary.

If the merge request or the client profile is included in the data request (SB11 ') message, the client profile request
(SB12 '), client profile response (SB1')
The flow of 3 ′) may not be necessary.

The WAP server 1 ′ stores the merge profile of the destination WAP mobile terminal in the profile management storage unit 15 ′, or the WAP gateway 2 ′.
When the client profile response message is received, the processing in FIG. 14 starts.

When receiving the client profile response message from the WAP gateway 2 ', the message analysis unit 11' analyzes the client profile response message and then analyzes the Internet section datagram P1 '.
Is stored in the profile management storage unit 15 ′. The merge profile is the WAP mobile terminal identifier (MT-
It is managed for each Id). Next, for the main control unit 14 ',
Issues a received message processing request.

[0228] The main control unit 14 'operates according to the profile such as the display size included in the merge profile stored in the profile management storage unit 15'.
The response data stored in 3 'is converted. Next, Po
rt / Address, MI-Id, and response data in message component 1
6 ', and issues a data response processing request to the message composition unit 16'. The message composition part 16 'is Po
Using the rt / Address, the MT-Id, and the response data, a data response message is formed in the format of the Internet section datagram P1 'and transmitted to the WAP gateway 2' (S
B14 ').

The data response message conforms to the HTTP protocol.
Corresponds to HTTP response message.

When the WAP gateway 2 'receives the data response message from the WAP server 1', the processing in FIG. 13 starts.

[0231] After analyzing the data response message, the message analyzer 27 'analyzes the Internet section datagram P1'.
Is stored in the memory 23 ', and the main control unit 2
4 'is issued. The main control unit 24 'extracts the client identifier (TE-Id) stored in the client identifier storage unit 28', and stores the client identifier (TE-Id) in the memory 23 'according to the profile such as the display size included in the client profile corresponding to the TE-Id. The response data included in the user data field of the current Internet section datagram P1 'is converted.

Next, the Internet section datagram P1 'stored in the memory 23' is converted into a radio section datagram P2 together with the address conversion and sent to the message composing section 26 '. Next, the client identifier storage unit 2
The TE-Id stored in the message composition unit 26 '
And issues a data response processing request to the message composition unit 26 '.

In the address conversion, the main control unit 24 ′ transmits the MT-Id included in the Internet section datagram header.
Is converted to the address of the wireless section based on The message composing unit 26 ′ composes a data response message in the format of the wireless section datagram P 2 using the datagram and the TE-Id, and transmits the data response message to the WAP mobile terminal 3.
(SB15). The data response message corresponds to the S-MethodResult.req message of the WAP-WSP protocol.

The flow S of the second embodiment shown in FIG.
B15-SB16 corresponds to the flow SB15- of the first embodiment.
The description is omitted because it is the same as SB16.

[0235]

A first effect is that data communication between a client and a server can be performed in a system including a client, a relay device, a gateway, and a server.

The reason is that a client identifier is added to the datagram header.

[0237] The second effect is that the processing of data communication between the relay apparatus and the client is improved.

The reason is that, since the client identifier is added to the datagram, the client can be clearly determined in the data distribution transmission from the relay device to the client.

[Brief description of the drawings]

FIG. 1 is a diagram showing a protocol stack according to a conventional technique.

FIG. 2 is a flowchart showing an operation of the embodiment according to the conventional technique.

FIG. 3 is a flowchart showing the operation of the first embodiment.

FIG. 4 is a block diagram showing a configuration of a relay device and a WAP mobile terminal.

FIG. 5 is a block diagram illustrating a configuration of a gateway and a WAP gateway according to the first embodiment and an example.

FIG. 6 shows a server and a server according to the first embodiment and an example.
FIG. 3 is a block diagram illustrating a configuration of a WAP server.

FIG. 7 is a table illustrating a configuration of a profile management storage unit in FIG. 4;

FIG. 8 is a table for explaining a configuration of a profile management storage unit in FIGS. 5 and 6;

FIG. 9 is a flowchart showing the operation of the first embodiment.

FIG. 10 is a diagram illustrating a protocol stack according to the embodiment.

FIG. 11 is a diagram illustrating a configuration of a datagram according to the first embodiment;

FIG. 12 is a flowchart showing the operation of the second embodiment.

FIG. 13 is a block diagram illustrating a configuration of a gateway and a WAP gateway according to a second embodiment and an example.

FIG. 14 is a block diagram illustrating a configuration of a server and a WAP server according to a second embodiment and an example.

FIG. 15 is a table for explaining a configuration of a profile management storage unit in FIG. 14;

FIG. 16 is a flowchart showing the operation of the second embodiment.

FIG. 17 is a diagram illustrating a configuration of a datagram according to the second embodiment;

FIG. 18 is a flowchart showing an operation when the server and the gateway are configured by one device.

[Explanation of symbols]

 1 (1 ') server and WAP server 11 (11') message analysis unit 12 (12 ') user request analysis unit 13 (13') memory 14 (14 ') main control unit 15 (15') profile management storage unit 16 (16 ') Message composition unit 17 (17') Data storage unit 2 (2 ') Gateway and WAP gateway 2a Profile storage unit 21 (21') Message analysis unit 22 (22 ') Message composition unit 23 (23') Memory 24 (24 ') main control unit 25 (25') profile management storage unit 26 (26 ') message construction unit 27 (27') message analysis unit 28 'client identifier storage unit 3 relay device and WAP mobile terminal 31 message analysis unit 32 Message composition part 33 Memory 34 Main control part 35 Profile management storage part 36 Message composition 37 message analyzing unit 4 the client and the WAP terminal P1 (P1 ') Internet section datagram P2 radio section datagram P3 terminal I / F section datagrams

Continued on the front page (72) Inventor Kazuhiro Okanoue 5-7-1 Shiba, Minato-ku, Tokyo NEC Corporation (72) Inventor Masahiro Ono 5-7-1 Shiba, Minato-ku, Tokyo NEC Corporation Within the company (72) Inventor Hikaru Ebata 5-7-1 Shiba, Minato-ku, Tokyo NEC Corporation (72) Inventor Masahiko Tsuki 5-7-1 Shiba, Minato-ku, Tokyo NEC Corporation F term (reference) 5B089 GA11 GA21 GA25 GA31 JB00 KA06 KB04 KG08 5K030 GA10 HA05 HC09 HD03 JL01 JT02 JT09 KA04 LA08 LB13 5K034 AA17 EE03 EE10 FF01 FF06 FF11 FF13 HH13 HH61 FF21H13 EE13 HH61 5K017A13HH

Claims (57)

[Claims] At least one client requests a relay device to register a client profile describing its processing capability, and the relay device assigns a client identifier to the client requesting the client profile registration. Transmitting a profile list including one or a plurality of client pair profiles including the client identifier and the client profile to a gateway, wherein the gateway receives the profile list and stores the profile list for each relay device. Characteristic data communication method. 2. When receiving a data transmission request from a user, the server requests the gateway for a profile list of the data transmission destination relay device if the server does not hold the profile list of the data transmission destination relay device. The gateway, upon receiving the request for the profile list, transmits the profile list of the relay device to the server.If the server holds the received profile list or the profile list of the relay device of the data transmission destination, 2. The data communication method according to claim 1, wherein a client transmitting the transmission data is determined based on the profile list, and the transmission data is transmitted including the client identifier. 3. The data communication method according to claim 2, wherein the server converts the transmission data based on the client profile, and transmits the converted transmission data. 4. When the server receives a data transmission request from a client, if the server does not hold a client profile of the client, the server requests the gateway for a profile list of a relay device connected to the client. When receiving the request for the profile list, transmits the profile list of the relay device to the server, the server converts the transmission data based on the received profile list, and transmits the transmission data including the client identifier The data communication method according to claim 1, wherein the data communication is performed. 5. When a server receives a data transmission request from a client, if the server does not hold a client profile of the client, the server makes a request for a client profile of the client to a gateway. Upon receiving the request, the client transmits a client profile to the server, the server converts transmission data based on the received client profile, and transmits the transmission data including the client identifier. Claim 1
The data communication method described in 1. 6. When receiving a data transmission request from a client, the gateway extracts a client profile of the client from the profile list,
The data transmission request is transmitted to the server, and the server, upon receiving the data transmission request from the gateway, converts the transmission data based on the client profile and transmits the transmission data including the client identifier. The data communication method according to claim 1, wherein 7. The relay device according to claim 2, wherein the relay device, upon receiving the transmission data from the server, transmits the transmission data to the client based on the client identifier. Data communication method described. 8. Requesting the relay device to register a client profile describing its own processing capability, causing the relay device to assign a client identifier to the client requesting registration of the client profile, And a profile list comprising one or a plurality of client pair profiles including the client profile and the client profile, causing the gateway to store the profile list for each of the relay devices, being converted from a server based on the client profile. A client, wherein transmission data including a client identifier is received by the relay device via a gateway, and data transmitted based on the client identifier is received. 9. A client profile registration request describing the processing capability of a client is received from one or a plurality of clients, a client identifier is assigned to the client that has requested the client profile registration, and the client identifier and A profile list including one or a plurality of client pair profiles including the client profile is transmitted to the gateway,
When the gateway stores a profile list for each relay device, and receives, via the gateway, transmission data converted from the server based on the client profile and including the client identifier, the transmission data is converted based on the client identifier. A relay device for transmitting to a client. 10. A request for registration of a client profile describing the processing capability of its own client is made from one or a plurality of clients to a relay device, and a client identifier is assigned to the client which has requested the client profile registration in the relay device. Is assigned, receives a profile list composed of one or a plurality of client pair profiles including the client identifier and the client profile, and stores the profile list for each of the relay devices;
A gateway for transmitting a profile list or a pair profile of a relay device requested by a server to the server. 11. A request for registration of a client profile describing the processing capability of its own client is made from one or a plurality of clients to a relay device, and a client identifier is assigned to the client which has requested the client profile registration in the relay device. Is assigned, receives a profile list composed of one or a plurality of client pair profiles including the client identifier and the client profile, and stores the profile list for each of the relay devices;
Upon receiving a data transmission request from the client, the gateway includes a client profile of the client in the data transmission request and transmits the data to the server. 12. When a data transmission request is received from a user, a pair profile of one or a plurality of clients including a client identifier for identifying one or a plurality of clients and a client profile describing the processing capability of the client is provided. Requests a profile list of a relay device of a data transmission destination to a gateway storing a profile list for each relay device, and upon receiving the profile list from the gateway, determines a client to transmit data based on the profile list. And transmitting data including the client identifier. 13. Upon receiving a data transmission request from a client, a profile list including one or a plurality of pair profiles including a client identifier for identifying one or a plurality of clients and a profile describing the processing capability of the client is provided. A request for a profile list of the relay device connected to the client is made to the gateway stored for each relay device, and when the profile list is received from the gateway, the transmission data is converted based on the profile list, and the client is converted. A server for transmitting transmission data including an identifier. 14. Upon receiving a data transmission request from a client, a profile list including one or a plurality of pair profiles including a client identifier for identifying one or a plurality of clients and a profile describing a processing capability of the client is provided. A request for a client profile of the client is made to a gateway stored for each relay device. When the client profile is received from the gateway, the transmission data is converted based on the client profile, and the transmission data including the client identifier is converted. Server. 15. One or more clients request the relay device to register a client profile describing its processing capability, and the relay device assigns a client identifier to the client requesting the client profile registration. Transmitting a profile list comprising a pair profile of one or more clients including the client identifier and the client profile to a gateway with a server function, the gateway with a server function receives the profile list, and A data communication method comprising storing a list. 16. Upon receiving a data transmission request from a user, the server-equipped gateway determines a client to transmit transmission data based on a profile list of a relay device of a transmission destination, and includes a transmission data including the client identifier. The data communication method according to claim 1, wherein the data communication is transmitted. 17. The data communication method according to claim 16, wherein the gateway with a server function converts the transmission data based on the client profile and transmits the converted transmission data. 18. A server-equipped gateway, upon receiving a data transmission request from a client, converts the transmission data based on the profile list of the client, and transmits the transmission data including the client identifier. The data communication method according to claim 1, wherein 19. The data communication method according to claim 17, wherein the relay device, upon receiving the transmission data from the server, transmits the transmission data to the client based on the client identifier. 20. By requesting a relay device to register a client profile describing its own processing capability,
The relay device assigns a client identifier to the client that has requested the registration of the client profile, and sends a profile list including a pair profile of one or more clients including the client identifier and the client profile to the gateway with a server function. A client, wherein transmission data including a client identifier converted based on the client profile is received from the gateway with a server function and received by the relay device, and data transmitted based on the client identifier is received. . 21. A request for registration of a client profile describing the processing capability of a client is received from one or a plurality of clients, a client identifier is assigned to the client that has requested the registration of the client profile, and the client identifier and A profile list including one or a plurality of client pair profiles including the client profile is transmitted to a gateway with a server function, a profile list is stored for each relay device, and conversion is performed based on the client profile from the gateway with a server function. And receiving the transmission data including the client identifier, transmitting the transmission data to the client based on the client identifier. 22. A request for registration of a client profile describing the processing capability of its own client is made from one or a plurality of clients to the relay device, and a client identifier is issued to the client which has requested the client profile registration in the relay device. Receiving a profile list including one or a plurality of pair profiles of clients including the client identifier and the client profile, and storing the profile list for each of the relay devices. . 23. When a data transmission request is received from a user, a pair profile of one or a plurality of clients including a client identifier for identifying one or a plurality of clients and a client profile describing the processing capability of the client is provided. A gateway with a server function, which determines a client to transmit data based on a profile list, and transmits data including the client identifier. 24. When a data transmission request is received from a client, a profile list including one or a plurality of pair profiles including a client identifier for identifying one or a plurality of clients and a profile describing the processing capability of the client is provided. A gateway with a server function, which converts transmission data on the basis of the transmission data and transmits the transmission data including the client identifier. 25. When a data transmission request is received from a client, transmission data is determined based on one or a plurality of pair profiles including a client identifier for identifying one or a plurality of clients and a profile describing the processing capability of the client. And transmitting transmission data including the client identifier. 26. One or a plurality of clients request the relay device to register a client profile describing its own processing capability, and the relay device assigns a client identifier to the client requesting the client profile registration. Transmitting a profile list comprising one or more client pair profiles including the client identifier and the client profile to a gateway, the gateway receiving the profile list, storing a profile list for each relay device, A data communication method, wherein a merge profile is created by merging one or a plurality of client profiles based on a list. 27. When receiving a data transmission request from a user, the server requests the gateway for a merge profile of the data transmission destination relay device if the server does not hold the merge profile of the data transmission destination relay device. Upon receiving the request for the merge profile, the gateway transmits a merge profile of the relay device to the server, and the server converts transmission data based on the received merge profile and transmits the converted data. Item 29. The data communication method according to Item 26. 28. Upon receiving transmission data from the server, the gateway determines a destination client based on the profile, converts the transmission data based on the determined client profile, and converts the converted transmission data into the converted transmission data. 28. The data communication method according to claim 27, wherein the data communication method includes transmitting the client identifier to the relay device. 29. Upon receiving a data transmission request from a client, the gateway stores the client identifier of the client, and upon receiving the data transmission request from the gateway, the server sends a data transmission request to the client that made the data transmission request. If you do not hold the merge profile of the connected relay device,
The gateway sends a request for a merge profile of the relay device connected to the client that has made a data transmission request to the gateway.When the gateway receives the request for the merge profile, the gateway transmits the merge profile of the relay device to the server. And converting transmission data based on the received merge profile and transmitting the converted data.
7. The data communication method according to 6. 30. Upon receipt of a data transmission request from a client, the gateway stores the client identifier of the client, and transmits the merge profile of the relay device connected to the client to the server in the data transmission request. 27. The data communication method according to claim 26, wherein upon receiving the data transmission request from the gateway, the server converts and transmits transmission data based on the merge profile. 31. When receiving transmission data from a server, the gateway converts the transmission data based on the profile of the client corresponding to the client identification, and transmits the converted transmission data including the client identifier of the client to the relay device. 31. The data communication method according to claim 29, wherein the data communication is performed. 32. The data communication method according to claim 28, wherein the relay device, upon receiving the transmission data from the gateway, transmits the transmission data to the client based on the client identifier. 33. By requesting a relay device to register a client profile describing its own processing capability,
A client identifier is assigned to a client that has requested the registration of the client profile, a profile list including one or a plurality of pair profiles including the client identifier and the client profile is registered in a relay device, and the profile list is registered in a gateway. And cause the gateway to store a profile list for each relay device, cause the gateway to merge one or a plurality of client profiles from the profile list, transmit the merged merged profile in response to a request from the server, The data converted based on the merge profile is received by a gateway, and the gateway converts transmission data based on a client profile, and the relay device And receiving transmission data transmitted from the relay device based on the client identifier. 34. Receiving a request for registration of a client profile describing the processing capability of the client from one or more clients, assigning a client identifier to the client requesting registration of the client profile, A profile list including one or a plurality of pair profiles including a client profile is transmitted to the gateway, and client profiles of one or a plurality of clients are merged at the gateway from the profile list, and converted based on the merge profile from the server. When the transmission data received by the gateway is received by the gateway and the transmission data converted based on the client profile is received by the gateway, the data is transmitted based on the client identifier. Relay apparatus and transmits the data. 35. A request for registration of a client profile describing the processing capability of its own client is made from one or a plurality of clients to the relay device, and a client identifier is assigned to the client which has requested the client profile registration in the relay device. Is assigned, receives from the relay device a profile list including a pair profile including the client identifier and the client profile, stores the profile list for each of the relay devices, and is connected to the relay device requested by the server. Merges the client profiles of one or more clients, transmits the merge profile to the server, and receives transmission data converted based on the merge profile from the server; A client that determines a transmission destination client from the client, converts data based on the determined client profile of the client, and transmits the converted transmission data including the client identifier of the client to the relay device. 36. A request for registration of a client profile describing the processing capability of its own client is made from one or a plurality of clients to the relay device, and a client identifier is assigned to the client which has requested the registration of the client profile in the relay device. Is assigned, receives a profile list composed of one or a plurality of client pair profiles including the client identifier and the client profile, and stores the profile list for each of the relay devices;
When a data transmission request is received from the client, the client identifier of the client is stored, and the profile list of the relay device connected to the client is merged and included in the data transmission request and transmitted to the server. Upon receiving the transmission data converted based on the merge profile, the data is converted based on the client profile corresponding to the client identifier, and the converted transmission data is transmitted to the relay device including the client identifier of the client. A gateway, characterized in that: 37. Upon receiving a data transmission request from a user, one or more data including a client identifier for identifying one or a plurality of clients connected to the relay device of the transmission destination and a client profile describing the processing capability of the client. Requesting a gateway a merge profile in which a profile list including a pair profile of a plurality of clients is merged, receiving the merge profile from the gateway, converting transmission data based on the merge profile, and transmitting the converted data. Server to do. 38. When a request for data transmission is received from a client via a relay device, a client identifier identifying one or a plurality of clients connected to the relay device and a client profile describing a processing capability of the client. Requesting a gateway a merge profile in which a profile list including one or more pair profiles of one or more clients including a merge profile is received, and receiving the merge profile from the gateway, converting and transmitting transmission data based on the merge profile. A server characterized by the above-mentioned. 39. A recording medium on which a communication program of a client is recorded, wherein a request for registration of a client profile describing its own processing capability is made to a relay device, thereby requesting said relay device to register said client profile. A client is assigned a client identifier, a profile list including one or a plurality of client pair profiles including the client identifier and the client profile is transmitted to a gateway, and the gateway lists the profile list for each of the relay devices. The transmission data converted from the server based on the client profile and including the client identifier is received by the relay device via the gateway, and is transmitted based on the client identifier. It has been recorded medium recording a client communication program for causing a function to the client to receive data. 40. A recording medium on which a communication program of a relay device is recorded, wherein a request for registration of a client profile describing a processing capability of the client is received from one or a plurality of clients, and a request for registration of the client profile is made. Assigning a client identifier to the client, and transmitting a profile list including one or more client pair profiles including the client identifier and the client profile to the gateway,
When the gateway stores a profile list for each relay device, and receives, via the gateway, transmission data converted from the server based on the client profile and including the client identifier, the transmission data is converted based on the client identifier. A recording medium recording a relay device communication program, wherein the relay device functions to transmit to a client. 41. A recording medium on which a communication program of a gateway is recorded, wherein one or a plurality of clients make a request for registration of a client profile describing the processing capability of the client to the relay device, and the relay device requests the registration. A client identifier is assigned to the client that has requested the registration of the client profile, a profile list including one or a plurality of client pair profiles including the client identifier and the client profile is received, and the profile is set for each of the relay devices. Store the list,
A recording medium storing a gateway communication program, wherein the gateway functions to transmit a profile list or a pair profile of a relay device requested by a server to the server. 42. A recording medium on which a communication program of a gateway is recorded, wherein one or a plurality of clients make a request for registration of a client profile describing the processing capability of the client to the relay device, and the relay device requests the registration. A client identifier is assigned to the client that has requested the registration of the client profile, a profile list including one or a plurality of client pair profiles including the client identifier and the client profile is received, and the profile is set for each of the relay devices. Store the list,
A recording medium on which a gateway communication program is recorded, wherein upon receiving a data transmission request from the client, the gateway causes the gateway to include a client profile of the client in the data transmission request and transmit the data to a server. 43. A recording medium on which a communication program of a server is recorded, wherein, when a request for data transmission is received from a user, a client profile for identifying one or a plurality of clients and a processing capability of the client are described. Requesting a profile list of a relay device of a data transmission destination to a gateway storing a profile list including one or a plurality of client pair profiles for each of the relay devices, and receiving the profile list from the gateway. A recording medium on which a server communication program is recorded, which determines a client to transmit data based on the profile list, and causes the server to transmit data including the client identifier. 44. A recording medium on which a communication program of a server is recorded, wherein when a request for data transmission is received from a client, a client identifier for identifying one or a plurality of clients and a profile describing the processing capability of the client. Requests a profile list of a relay device connected to the client to a gateway storing a profile list including one or a plurality of pair profiles for each of the relay devices, and upon receiving the profile list from the gateway, A recording medium on which a server communication program is recorded, wherein the server functions to convert transmission data based on a profile list and transmit transmission data including the client identifier. 45. A recording medium on which a communication program of a server is recorded, wherein when a request for data transmission is received from a client, a client identifier for identifying one or a plurality of clients and a profile describing the processing capability of the client. Requesting a client profile of the client to a gateway storing a profile list including one or a plurality of pair profiles for each relay device, and transmitting the client profile based on the client profile when the client profile is received from the gateway. A recording medium on which a server communication program is recorded, wherein the server functions to convert data and transmit transmission data including the client identifier. 46. A recording medium on which a communication program of a client is recorded, wherein a request for registration of a client profile describing its own processing capability is made to a relay device, thereby requesting said relay device to register said client profile. A client identifier is assigned to the client, and a profile list including one or a plurality of pair profiles of the client including the client identifier and the client profile is transmitted to the gateway with the server function. The transmission data converted based on the client identifier is received by the relay device, and the client is operable to receive the data transmitted based on the client identifier. Recording medium storing a client communication program characterized Rukoto. 47. A recording medium for recording a communication program of a relay device, comprising: a request for registering a client profile describing a processing capability of a client from one or a plurality of clients; A client list including the client identifier and the client profile, and a profile list including a pair profile of one or more clients including the client identifier and the client profile to a gateway with a server function, and storing a profile list for each relay device Receiving the transmission data converted from the gateway with the server function based on the client profile and including the client identifier, the transmission data is cleaved based on the client identifier. Recording medium that records the relay apparatus communication program for causing a function to the relay device to transmit to Ianto. 48. A recording medium in which a communication program of a gateway with a server function is recorded, wherein one or a plurality of clients request a relay device to register a client profile describing the processing capability of its own client, A client identifier is assigned to the client that has requested the registration of the client profile, and a profile list including one or a plurality of pair profiles of the client including the client identifier and the client profile is received; A storage medium storing a communication program for a gateway with a server function, which causes the gateway with a server function to store the profile list. 49. A recording medium on which a communication program for a gateway with a server function is recorded, wherein when a data transmission request is received from a user, a client identifier for identifying one or a plurality of clients and a processing capability of the client are described. A client that transmits data is determined based on a profile list including one or a plurality of pair profiles of clients including the client profile obtained by the client function, and the gateway with the server function functions to transmit data including the client identifier. A recording medium on which a communication program for a gateway with a server function is recorded. 50. A recording medium on which a communication program of a gateway with a server function is recorded, wherein upon receiving a data transmission request from a client, a client identifier for identifying one or a plurality of clients and a processing capability of the client are described. And converting the transmission data based on a profile list including one or a plurality of paired profiles including the selected profile, and transmitting the transmission data including the client identifier to the gateway with the server function. A recording medium on which a communication program for a gateway with a server function is recorded. 51. A recording medium on which a communication program of a gateway with a server function is recorded, wherein upon receiving a data transmission request from a client, a client identifier for identifying one or a plurality of clients and a processing capability of the client are described. A transmission function that converts the transmission data based on one or a plurality of pair profiles including the selected profile, and causes the gateway with the server function to transmit the transmission data including the client identifier. Recording medium on which a communication program is recorded. 52. A recording medium in which a communication program of a client is recorded, wherein a request for registration of a client profile describing its own processing capability to a relay device is issued to the client requesting registration of the client profile. A client identifier is assigned, a profile list including one or a plurality of pair profiles including the client identifier and the client profile is registered in the relay device, and the profile list is transmitted to the gateway. Is stored, the profile of one or a plurality of clients is merged into the gateway from the profile list, the merged profile is transmitted by a request from the server, The data converted based on the merge profile is received at the gateway, the transmission data is converted at the gateway based on the client profile, received by the relay device, and transmitted from the relay device based on the client identifier. A recording medium storing a communication program for a client, wherein the recording medium causes the client to function to receive transmission data. 53. A recording medium on which a communication program of a relay device is recorded, wherein a request for registration of a client profile describing a processing capability of the client is received from one or a plurality of clients, and a request for registration of the client profile is made. Assigning a client identifier to the client, transmitting a profile list including one or more pair profiles including the client identifier and the client profile to the gateway, and transmitting the client profile of one or more clients to the gateway from the profile list. The transmission data converted based on the merge profile is received from the server at the gateway, and the transmission data converted based on the client profile at the gateway. Upon receiving the data, a recording medium that records the relay apparatus communication program for causing a function to transmit data based on the client identifier to the relay apparatus. 54. A recording medium on which a communication program of a gateway is recorded, wherein one or a plurality of clients request a registration of a client profile describing the processing capability of its own client to a relay device. A client identifier is assigned to the client that has requested the registration of the client profile, a profile list including a pair profile including the client identifier and the client profile is received from the relay device, and the profile list is stored for each relay device. Storing, merging the client profile of one or more clients connected to the relay device requested by the server, transmitting the merge profile to the server, and transmitting the merge profile from the server based on the merge profile. Upon receiving the converted transmission data, determine the destination client from the profile list, convert the data based on the determined client profile of the client, including the client identifier of the client in the converted transmission data, A recording medium storing a communication program for a gateway, wherein the recording medium causes the gateway to transmit to a relay device. 55. A recording medium in which a communication program of a gateway is recorded, wherein one or a plurality of clients request a relay device to register a client profile describing the processing capability of its own client. A client identifier is assigned to the client that has requested the registration of the client profile, a profile list including one or a plurality of client pair profiles including the client identifier and the client profile is received, and the profile is set for each of the relay devices. Store the list,
When a data transmission request is received from the client, the client identifier of the client is stored, and the profile list of the relay device connected to the client is merged and included in the data transmission request and transmitted to the server. Upon receiving the transmission data converted based on the merge profile, the data is converted based on the client profile corresponding to the client identifier, and the converted transmission data is transmitted to the relay device including the client identifier of the client. A recording medium storing a gateway communication program, wherein the recording medium causes the gateway to function. 56. A recording medium on which a communication program of a server is recorded, wherein, when a request for data transmission is received from a user, a client identifier for identifying one or a plurality of clients connected to the relay device of the transmission destination and the client Requesting a gateway a merge profile in which a profile list including one or a plurality of client pair profiles including a client profile describing the processing capability of the client, and receiving the merge profile from the gateway based on the merge profile A recording medium on which a server communication program is recorded, wherein the server functions to convert transmission data and transmit the data. 57. A recording medium on which a communication program of a server is recorded, wherein when a request for data transmission is received from a client via a relay device, the client identifies one or a plurality of clients connected to the relay device. A request is made to a gateway for a merge profile in which a profile list including one or a plurality of pair profiles of a client including an identifier and a client profile describing a processing capability of the client is received, and when the merge profile is received from the gateway, the merge is performed. A recording medium on which a server communication program is recorded, wherein said server functions to convert and transmit transmission data based on a profile.