CN101006706B - Communication device, communication system and communication method - Google Patents

Abstract

In the client device (1) with OBEX mounted, a lower layer processing part (13) which is a lower layer of an OBEX layer processing part (12) generates a virtual response command to a request command, and notifies the OBEX layer processing part (12) of the virtual response command. This enables communication by target exchange with a server device having no transmission function.

Description

Communication device, communication system and communication method

technical field

The present invention relates to a communication device, a communication system, a communication method, a communication program, and a communication circuit that transmit and receive data while exchanging data. the

Background technique

OBEX (OBject EXchange protocol) is known as a communication protocol for data transmission and reception, that is, object exchange for data communication. OBEX standardizes the process of sending and receiving data through an infrared port in the format of "exchange of objects (general data entities such as files)" (see Patent Document 1). the

The application software using OBEX can exchange various objects without being aware of differences in communication equipment or communication methods. Not only the IrDA (Infra Red Data Association) communication method using infrared rays, but also wireless (2.4GHz frequency band) Conversational protocols such as the Bluetooth (registered trademark) communication method and the like have been adopted in many fields. the

As objects, in addition to normal documents, diagnosis of equipment, business cards, bank account details, electrocardiograms, receipts, and the like are assumed. For example, house address book data or business card data can be exchanged between portable computers, mobile phones, and PDAs (portable information communication devices) equipped with IrDA or Bluetooth. In addition, it is also possible to transmit video data captured by a mobile phone or a digital camera to a television or a monitor, or a kiosk on the street. In addition, it can also be used to control TV receivers or VCRs. the

OBEX is a high-level protocol equivalent to IrDA in the session layer of the OSI (Open System Interconnection) reference model. It has the same function as the HTTP (Hyper Text Transform Protocol) of the Internet, but has the feature of not requiring as many resources as HTTP. the

Figure 7 shows the standard IrDA protocol stack. The protocol stack of IrDA is composed of IrPHY (IrDA Physical Layer), IrLAP (IrDA Link Access Protocol), IrLMP (IrDA Link Management Protocol), and TinyTP (Transport Protocol). IrPHY defines the modulation mode, signal strength, directionality, etc., and IrLAP defines the basis The general-purpose HDLC (High level Data Link Control) error control function, the function of negotiating the communication speed and the maximum amount of data before communication in addition to the transmission and flow control, and the function of searching and discovering uncertain external devices that should be connected Procedures, etc., IrLMP provides functions equivalent to the multiplexing and multiplexing separation of port numbers used by TCP or UDP of the TCP/IP (Transmission Control Protocol/Internet Protocol) protocol, and TinyTP is used for flow control in individual logical links , OBEX is located at the upper layer of the TinyTP transport protocol. the

In OBEX, a device that requests a command is called a client device, and a device that returns a response to the request is called a server device. Generally, a client/server model in which a client device issues a request command such as Put/Get to a server device, and the server device returns a response command. the

Request commands specified by OBEX roughly include the following request commands. There are CONNECT/DISCONNECT for connecting/disconnecting with the communication partner, PUT/GET for sending/receiving objects such as files, SETPATH for changing the receiving destination path (current path) of the server device that is the receiving device side, and setting ABORT where the sending or receiving of an object is forcibly aborted. the

FIG. 8 illustrates a basic request command/reply command exchange between a client device and a server device. When receiving an object exchange request from a user, the client device sends a CONNECT command indicating a connection request to the server device in order to establish a connection with the server device. the

When the server device having received the CONNECT command sends back a SUCCESS response command to the client device if the connection is possible, the client device receives the SUCCESS response command, thereby establishing a connection between the client device and the server device. the

After the connection is established, the client device starts exchanging objects, and sends a PUT command for sending objects to the server device. When the server device normally receives the PUT command from the client device, it sends back a CONTINUE response command, and the client device receives the CONTINUE response command from the server device, and after confirming that the server device has received the PUT command normally, sends the next PUT command . In the client device, the transmission of the PUT command is performed until all the objects are transmitted. The server device sends back a SUCCESS response command to the client device when the last PUT command is normally received. the

After receiving the SUCCESS response command from the server device, the client device transmits a DISCONNECT command indicating a disconnection request to the server device in order to perform disconnection processing with the server device. the

By receiving the server device of the DISCONNECT command, the client device sends back a response command of SUCCESS which means permission disconnection, and the client device receives the response command of SUCCESS, thereby disconnecting the connection between the client device and the server device. A series of object exchanges between the client device and the server device are completed. the

In this way, in OBEX, objects are exchanged by returning a response command from the server device to the request command from the client. the

In addition, as in the above-mentioned IrDA protocol stack, in a communication protocol having a layered structure such as OSI, header information is defined for each layer independently of other layers, and the data that should be transmitted between computing devices is defined in each layer. Header information is added sequentially from the highest layer to the lowest layer. On the other hand, for received data, header information is sequentially removed in each layer from the lowest layer to the highest layer, and the data is transferred to the upper layer. the

As shown in Figure 9, on the client device side, header information independently defined for each layer is sequentially added to the request command generated by the OBEX layer in each layer of the TinyTP layer, IrLMP layer, and IrLAP layer, and the data is transferred to lower level. On the other hand, the server device removes the header information sequentially from the lower layer on the data received from the client device, and when transferring the data to the upper layer, at the OBEX layer, request commands (CONNECT, PUT, DISCONNECT commands, etc.) rise from the lower levels. the

Japanese Laid-Open Patent Publication 'JP-A-2000-196622 (publication date July 14, 2000)'

As mentioned above, OBEX can exchange various objects regardless of differences in equipment or methods. It is adopted as an object exchange protocol in IrDA, Bluetooth, etc., and is installed in various portable terminals such as mobile phones and PDAs. in such equipment. the

However, in order to realize object exchange between a client device and a server device in which OBEX is installed, a requirement arises that the server device must have a sending function for sending back a reply command. Enabling the server device to have a sending function increases the cost of the device and the difficulty of development, and sometimes it is required to realize object exchange by only having the minimum necessary receiving function. the

Also, as described above, in the object exchange by the PUT command of OBEX, a CONTINUE response command to the PUT command from the client is transmitted from the server during the object exchange. A SUCCESS response command to the last PUT command is also required to let the client know that the object exchange has been reliably performed, but considering the frequency band used for the transmission of the CONTINUE response command, it may not necessarily be necessary to notify the CONTINUE response command that passed halfway. the

Furthermore, as described above, OBEX is currently installed in various devices, and it is not easy to change the specification, and when the specification is changed, existing resources cannot be called. the

Contents of the invention

The object of the present invention is to provide a communication device, a communication system, a communication method, a communication program, and a communication circuit. In the case of communicating using a protocol for object exchange, the server can respond to a specific request command or all request commands from a client device. The device does not send back an acknowledgment command. the

In order to achieve the above object, the communication device of the present invention, as the master station with the object exchange layer, sends the object to the object exchange layer of the secondary station by sending a request command and accepting a response command that responds to the request command. In that, the communication device includes: an object exchange layer processing part, which processes the communication protocol of the object exchange layer, sends the request command through a lower layer under the object exchange layer, and accepts the response command; and The low-level processing part processes the low-level communication protocol, and the low-level processing part includes: a response generating part that generates a virtual response command that simulates a response command from the secondary station, and notifies the object switching layer processing part and a low-level control section that controls the response generation section to generate the virtual response command for responding to the request command when accepting the generation notification of the request command from the object exchange layer processing section, thereby notifying the object In the exchange layer processing part, the communication protocol of the object exchange layer is an object exchange layer protocol, namely OBEX (Object Exchange Protocol). the

In addition, the communication method of the present invention is used for a master station having an object exchange layer, and the object exchange layer sends an object to an object exchange layer of a secondary station by sending a request command and receiving a response command in response to the request command, It is characterized in that, the object exchange layer sends the request command through the lower layer under the object exchange layer, and accepts the response command, when the lower layer receives the request command from the object exchange layer When generating the notification, a virtual response command simulating the response command from the secondary station in response to the request command is generated and notified to the object exchange layer. The communication protocol of the object exchange layer is the object exchange layer protocol, namely OBEX. the

According to the above structure and method, at the master station (for example, client device), a lower layer lower than the object exchange layer generates a dummy reply command, thereby notifying the object exchange layer. the

Therefore, there is an effect that object exchange can be performed with a secondary station (for example, a server device) having a minimum reception function that does not have a transmission function without changing the communication protocol for object exchange based on request commands/response commands. In addition, since it is not necessary to change the communication protocol (protocol for object exchange) of the object exchange layer to perform transmission and reception with the above-mentioned secondary station, there is an effect that existing resources can be used. the

Furthermore, a communication system according to the present invention is characterized by including the above-mentioned communication device as a master station and a communication device as a secondary station receiving an object from the communication device. Furthermore, the communication system of the present invention is characterized in that the communication device serving as the secondary station does not transmit a response command. the

According to the above-mentioned communication system, even if the secondary station cannot send the reply command, the master station generates a dummy reply command and notifies the object switching layer. Therefore, there is an effect that object exchange can be performed with a secondary station that does not have a transmission function but has a minimum required reception function without changing the conventional communication protocol that performs object exchange based on a request command/response command. the

In addition, in the communication device of the present invention, as a secondary station having an object switching layer, the object switching layer accepts a request command from the master station and issues a response command in response to the request command, thereby receiving object, characterized in that the communication device includes: an object exchange layer processing part, which processes the communication protocol of the object exchange layer, and outputs the response command to a lower layer located under the object exchange layer; and a lower layer processing part , processing the communication protocol of the lower layer of the lower layer, while the lower layer processing part does not send the response command to the master station when receiving the response command sent by the object exchange layer processing part, the object exchange Layer communication protocol is the object exchange layer protocol, namely OBEX. the

In addition, the communication method of the present invention is used for a secondary station having an object exchange layer. The object exchange layer accepts a request command from the master station and issues a response command in response to the request command, so that the object exchange layer of the master station Receiving an object is characterized in that the object exchange layer outputs the response command to a lower layer below the object exchange layer; when the lower layer accepts the response command sent by the object exchange layer, it does not The response command is sent to the master station, and the communication protocol of the object exchange layer is the object exchange layer protocol, that is, OBEX. the

According to the above structure and method, even if the target switching layer of the secondary station issues an unnecessary response command, it is not possible to send it from the secondary station. For example, when the object switching layer that becomes a secondary station (for example, a server device) always sends back an installation of a response command to a request command, when the request command from the master station (for example, a client device) does not need a response command, The lower layer does not send the response command issued by the object switching layer of the secondary station. the

Therefore, there is an effect that the power consumed in transmission of the secondary station can be reduced. In the case where the secondary station sends a response command, since the master station does not need a response command, there is a possibility that the response command from the secondary station and the request command from the master station may conflict, so it has the effect of preventing such a conflict. . the

Furthermore, the communication system of the present invention is characterized by including the above-mentioned communication device as a secondary station, and a communication device as a master station that transmits an object to the communication device. the

According to the communication system described above, when the request command from the master station is a request command that does not require a response command, the lower layer does not transmit the response command from the target switching layer of the secondary station. the

Therefore, even if there is a conventional communication protocol in which the object exchange layer of the secondary station performs object exchange based on the request command/response command, it can be performed with the master station that only receives the minimum required response command without changing it. The effect of object swapping. the

In addition, the above-mentioned communication device can also be realized by a computer. In this case, by making the computer operate as each part of the above-mentioned communication device, the communication program of the communication device of the above-mentioned communication device and the computer that recorded it can be realized by the computer. Reading recording media also falls within the scope of the present invention. the

In addition, the above-mentioned communication device may also be realized by a communication circuit having the functions of the above-mentioned parts. the

In addition, the communication device described above is suitable for a mobile phone that communicates via the communication device. According to the above-mentioned mobile phone, communication with high transmission efficiency can be performed using an object exchange protocol (including OBEX). the

In addition, the communication device described above is suitable for a display device that performs display based on data received by the communication device. According to such a display device, communication with high transmission efficiency can be performed using an object exchange protocol (including OBEX). the

Furthermore, the communication device described above is suitable for a printing device that performs printing based on data received by the communication device. According to such a printing apparatus, communication with high transmission efficiency can be performed using an object exchange protocol (including OBEX). the

Furthermore, the communication device described above is suitable as a recording device that records data received by the communication device. According to such a recording device, communication with high transmission efficiency can be performed using an object exchange protocol (including OBEX). the

Other objects, features, and advantages of the present invention will be made clear by the description below. Rather, the advantages of the present invention will become apparent from the following description with reference to the accompanying drawings. the

Description of drawings

FIG. 1 is a block diagram showing the configuration of a client device of a communication system according to a first embodiment of the present invention. the

FIG. 2 is a block diagram showing the configuration of the above communication system. the

Fig. 3 is a block diagram showing a configuration example of a server device of the above communication system. the

FIG. 4 is a sequence diagram showing the procedure of data transfer processing in the above-mentioned first embodiment. the

5 is a block diagram showing the configuration of a client device of a communication system according to a second embodiment of the present invention. the

FIG. 6 is a sequence diagram showing the procedure of data transfer processing in the above-mentioned second embodiment. the

FIG. 7 is a conceptual diagram showing the protocol stack of IrDA. the

Fig. 8 is a sequence diagram showing the procedure of exchanging a basic request command and a response command in the OBEX communication standard. the

Fig. 9 is a sequence diagram for explaining the general procedure of data transmission in the OBEX communication standard. the

FIG. 10 is a block diagram showing the configuration of a client device of a communication system according to a third embodiment of the present invention. the

Fig. 11 is a block diagram showing the configuration of a client device in a communication system according to a fourth embodiment of the present invention. the

FIG. 12 is a sequence diagram showing the procedure of data transfer processing in the above-mentioned third and fourth embodiments. the

13 is a block diagram showing the configuration of a server device of a communication system according to a fifth embodiment of the present invention. the

FIG. 14 is a flow chart showing the operation of the low-level processing part of the OBEX layer of the conventional server device. the

FIG. 15 is a flowchart showing operations in the low-level processing portion of the OBEX layer of the server device of the communication system according to the fifth embodiment. the

FIG. 16 is a sequence diagram showing the procedure of data transfer processing in the fifth embodiment. the

Fig. 17 is a block diagram showing the configuration of a server device of a communication system according to a sixth embodiment of the present invention. the

FIG. 18 is a flowchart showing operations in the low-level processing portion of the OBEX layer of the server device of the communication system according to the sixth embodiment. the

FIG. 19 is a sequence diagram showing the procedure of data transfer processing in the sixth embodiment. the

FIG. 20 is a flowchart showing another operation in the lower-level processing portion of the OBEX layer of the server device of the communication system according to the sixth embodiment. the

FIG. 21 is a block diagram showing the configuration of a client device in a conventional communication system. the

Fig. 22 is a flowchart showing the operation of the OBEX client in the conventional communication system. the

FIG. 23 is a block diagram showing a configuration of a client device in a communication system according to the seventh embodiment and the eighth embodiment of the present invention. the

Fig. 24 is a flowchart showing the operation of the OBEX layer of the client device in the communication system according to the seventh embodiment. the

25 is a flowchart showing another operation of the OBEX layer of the client device in the communication system according to the seventh embodiment of the present invention. the

26 is a flowchart showing the operation of the OBEX layer of the client device in the communication system according to the eighth embodiment of the present invention. the

Fig. 27 is a block diagram showing the configuration of a server device in a conventional communication system. the

Fig. 28 is a flowchart showing the operation of the OBEX server in the conventional communication system. the

Fig. 29 is a block diagram showing another configuration of a server of the communication system according to the ninth embodiment and the tenth embodiment of the present invention. the

Fig. 30 is a flowchart showing the operation of the OBEX layer of the server device of the communication system according to the ninth embodiment. the

Fig. 31 is a flowchart showing another operation of the OBEX layer of the server device of the communication system according to the ninth embodiment. the

32 is a flowchart showing the operation of the OBEX layer of the server device of the communication system according to the tenth embodiment of the present invention. the

33 is a diagram showing an example of communication between mobile phones in the communication system according to the eleventh embodiment of the present invention. the

34 is a diagram showing an example of communication between a mobile phone and a display device in a communication system according to a twelfth embodiment of the present invention. the

35 is a diagram showing an example of communication between a mobile phone and a printing device in a communication system according to a thirteenth embodiment of the present invention. the

36 is a diagram showing an example of communication between a mobile phone and a recording device in a communication system according to a fourteenth embodiment of the present invention. the

Fig. 37 is a schematic diagram showing the correspondence between the OSI7 layer model, the layers of IrDA, and the layers of the present invention. the

Fig. 38(a) is a diagram showing the sequence of establishing a connection according to an embodiment of the present invention, Fig. 38(b) is a diagram showing a sequence of establishing a connection according to an embodiment of the present invention, and Fig. 38(c) is a diagram showing the sequence of establishing a connection according to an embodiment of the present invention The packet format used to establish the connection. the

FIG. 39( a ) is a diagram showing the data exchange procedure according to the embodiment of the present invention, and FIG. 39( b ) is a diagram showing the data exchange procedure according to the embodiment of the present invention. the

FIG. 40( a ) is a diagram showing a packet format used in data exchange of IrDA, and FIG. 40( b ) is a diagram showing a packet format used in data exchange of the present invention. the

FIG. 41( a ) is a diagram showing the data exchange procedure according to the embodiment of the present invention, and FIG. 41( b ) is a diagram showing the data exchange procedure according to the embodiment of the present invention. the

Fig. 42(a) is a diagram showing the disconnection sequence of the embodiment of the present invention, Fig. 42(b) is a diagram showing the disconnection sequence of the embodiment of the present invention, and Fig. 42(c) is a diagram of the disconnection sequence of the embodiment of the present invention. Break-order grouping format. the

43 is a sequence diagram showing the flow of functions (commands, messages) and packets between layers in the connection sequence according to the embodiment of the present invention. the

Fig. 44 (a) is an explanatory diagram showing the change of data in the function between the layers of the right direction arrows in Fig. 43 and Fig. 45 when the connection sequence of the embodiment of the present invention is shown, and Fig. A graph of the variation of the data as a function of the layers of the embodiment. the

45 is a sequence diagram showing the flow of functions (commands, messages) and packets between layers in the connection sequence according to the embodiment of the present invention. the

Fig. 46 is a sequence diagram showing the flow of functions (commands, messages) and packets between layers at the time of data exchange according to the embodiment of the present invention. the

FIG. 47 is a diagram showing changes in data in functions between layers in FIG. 46 and FIG. 48 at the time of data exchange according to the embodiment of the present invention. the

Fig. 48 is a sequence diagram showing the flow of functions (commands, messages) and packets between layers at the time of data exchange according to the embodiment of the present invention. the

Fig. 49 is a sequence diagram showing the flow of functions (commands, messages) and packets between layers in the disconnection sequence according to the embodiment of the present invention. the

Fig. 50(a) is an explanatory diagram showing the change of data in the function of the right arrows in Fig. 49 and Fig. It is an explanatory diagram of a change in data in a function between layers according to an embodiment of the invention. the

Fig. 51 is a sequence diagram showing the flow of functions (commands, messages) and packets between layers in the disconnection sequence according to the embodiment of the present invention. the

Fig. 52 is a schematic diagram showing transfer of data and connection parameters of the connection request function of the master station according to the embodiment of the present invention. the

Fig. 53 is a schematic diagram showing the transfer of connection parameters in the connection request function of the secondary station according to the embodiment of the present invention. the

54 is a schematic diagram showing exchange of data and connection parameters of the connection confirmation function of the master station and the connection notification function of the slave station according to the embodiment of the present invention. the

Fig. 55 is a schematic diagram showing data transfer of the connection reply function of the secondary station according to the embodiment of the present invention. the

Fig. 56 is a schematic diagram showing the transfer of connection parameters of the connection confirmation function of the master station according to the embodiment of the present invention. the

Fig. 57 is a schematic diagram showing transfer of data and connection parameters of the connection request function of the master station when the connection parameters are shared between layers as a modified example of the embodiment. the

Fig. 58 is a schematic diagram showing transfer of data and connection parameters of the connection notification function of the secondary station when the connection parameters are shared between layers as a modified example of the embodiment. the

Fig. 59 is a schematic diagram showing transfer of data and connection parameters of the connection request function of the master station in a case where each layer transfers connection parameters to lower layers as a modified example of the embodiment. the

Label description

1 Client device (communication device, master station)

11 Application layer processing part

12OBEX layer processing part (object exchange layer processing part)

121 control part

122 request notification section

123 response receiving part

13 Low-level processing part

131 control part (lower control part)

132 request receiving part

133 Request Notification Section

134 response generation part

14 Sending part

15 receiving part

2Client equipment (communication device, master station)

21 Application layer processing part

22OBEX layer processing part (object exchange layer processing part)

221 control part

222 request notification section

223 response receiving part

23 Low-level processing part

231 control part (low-level control part)

232 request receiving part

233 Request Notification Section

234 response receiving part

235 response notification part

236 response generation part

237 multiplexer

238 timer

24 Send part

25 receiving part

3Client equipment (communication device, master station)

31 Application layer processing part

32OBEX layer processing part (object exchange layer processing part)

321 control part

322 request notification section

323 response receiving part

23 Low-level processing part

331 control part (low-level control part)

332 request receiving part

333 Request Notification Section

334 response receiving part

335 response notification part

336 response generation part

337 multiplexer

34 sending part

35 receiving part

4Client equipment (communication device, master station)

41 Application layer processing part

42OBEX layer processing part (object exchange layer processing part)

421 control part

422 request notification section

423 response receiving part

43 Low-level processing part

431 control part (low-level control part)

432 request receiving part

433 request notification section

434 response receiving part

435 response notification part

436 response generation part

437 multiplexer

438 header information analysis part

44 sending part

45 receiving part

5 server equipment (communication device, secondary station)

51 Application layer processing part

52OBEX layer processing part (object exchange layer processing part)

521 control part

525 request parsing part

53 low-level processing part

531 control part

535 request parsing part

54 sending part

55 receiving part

1000 server equipment (communication device, secondary station)

1010 application layer processing part

1020OBEX layer processing part (object exchange layer processing part)

1021 control part

1022 response notification part

1025 request parsing part

1030 low-level processing part

1031 control part (lower control part)

1032 request parsing part

1050 receiving part

1100 server equipment (communication device, secondary station)

1110 application layer processing part

1120OBEX layer processing part (object exchange layer processing part)

1121 control part

1122 Response Notification Section

1125 request parsing part

1130 low-level processing part

1131 control part (lower control part)

1132 response receiving part

1135 request parsing part

1140 sending part

1150 receiving part

1300 client equipment (communication device, master station)

1310 application layer processing part

1320OBEX layer processing part (object exchange layer processing part)

1321 control part

1322 request notification section

1323 response receiving part

1324 communication direction selection part

1330 low-level processing part

1340 sending part

1350 receiving part

1500 server equipment (communication device, secondary station)

1510 application layer processing part

1520OBEX layer processing part (object exchange layer processing part)

1521 control part

1522 Response Notification Section

1523 request parsing part

1530 low-level processing part

1540 sending part

1550 receiving part

Detailed ways

In each embodiment described later, the configuration and operation of the client device (master station) and server device (secondary station) in the communication system of the present invention will be described in detail based on the OSI 7-layer model. Here, the OSI 7-layer model is also referred to as 'OSI basic reference model' and 'OSI layered model'. the

In the OSI7-layer model, in order to realize data communication between different models, the communication functions that computers should have are divided into seven layers, and standard functional modules are defined for each layer. the

Specifically, the first layer (physical layer) is in charge of electrical conversion or mechanical work for outputting data to a communication line. The second layer (data link layer) secures a physical communication path, and performs error detection and the like on data flowing through the communication path. The third layer (network layer) selects a communication path and manages addresses within the communication path. Layer 4 (transport layer) performs data compression, error correction, and retransmission control. The fifth layer (session layer) establishes or releases a virtual path (connection) for transmitting and receiving data between communication programs. The 6th layer (display layer) converts the data received from the 5th layer into a format easily understood by the user, or converts the data sent from the 7th layer into a form suitable for communication. The seventh layer (application layer) provides various services utilizing data communication to humans and other programs. the

Each communication layer of the communication system according to each embodiment also has functions equivalent to the corresponding layers of the above-mentioned OSI 7-layer model. However, in each of the embodiments, the communication system described above has a six-layer structure in which the session layer and the display layer are formed into one layer. In each embodiment, an example in which the communication layer in which such a session layer and a display layer are formed into one layer is realized by OBEX (OBject EXchange protocol) will be described. Furthermore, a communication layer provided with a lower layer processing section (described later) as a lower layer located in the OBEX layer will be described as a transport layer. However, the communication layer in which the lower layer processing part is set may also be a network layer or a data link layer. Note that, regarding the application layer, description is omitted. the

The present invention is widely applicable to a communication system in which a transmitter and a receiver establish connections of multiple communication layers to communicate. That is, the division of the communication function does not need to be based on the OSI7-layer model. Also, if there are multiple communication layers to be connected, the number of communication layers can be selected arbitrarily. the

In each embodiment, for convenience of description, description will be made based on IrSimple which is an application example of the present invention. However, the present invention is not limited to IrSimple. Furthermore, IrSimple has improved some functions of the conventional IrDA. In addition, the present invention is not limited to infrared wireless communication, and is also effective in other wireless communication and wired communication. the

In each embodiment, the data link layer, the network layer, the transport layer, and the session layer+display layer are sometimes expressed as LAP, LMP, SMP, and OBEX according to IrSimple. the

Hereinafter, the communication method, communication program, and record of the present invention will be described based on FIGS. Various embodiments of media, communication devices, and communication systems. the

Regarding the communication device of the present invention, as shown in FIG. 2 , from a client device (communication device) 1 as a communication device, to a server device 5 as a counterpart device, based on IrDA in which objects are exchanged by infrared rays as a medium Delivery method (transmission method). However, the present invention is not limited thereto. the

Examples of the above-mentioned client device 1 include a computer, a mobile phone, a portable information terminal (PDA), a digital camera, and the like. Examples of the server device 5 include a television (TV), a printer, a projector, a computer, a mobile phone, a portable information terminal (PDA), and a digital camera. the

Examples of the medium include, in addition to infrared rays, radio waves used in mobile phones at 100 MHz to 5 GHz, visible light using optical fibers as a transmission path, and the like. As data to be exchanged by objects, image files, text data, and the like can be cited. the

The client device 1 according to the first embodiment of the present invention will be described below based on FIG. 1 . It should be noted that terms (including members and functions) defined in other embodiments are assumed to be used in accordance with their definitions in this embodiment unless otherwise specified. the

FIG. 1 is a block diagram showing the configuration of a client device 1 of the communication system according to the present embodiment. As shown in FIG. 1 , the client device 1 includes: an application layer processing section 11 , an OBEX layer processing section (object exchange layer processing section) 12 , a lower layer processing section 13 , a sending section 14 and a receiving section 15 . The application layer processing section 11, the OBEX layer processing section 12, and the lower layer processing section 13 have a layered structure in this order, and each of various types of communication protocols. the

The application layer processing unit 11 requests the OBEX layer processing unit 12 to issue a request command for communication with the outside in accordance with a user instruction input to an operation unit not shown. On the other hand, when the notification that the response command has been received from the OBEX layer processing unit 12 is received, predetermined processing is performed based on the received response command. the

The OBEX layer processing section 12 includes: a control section 121 , a request notification section 122 and a response reception section 123 . The control section 121 notifies (controls) the request notifying section 122 of the generation of the request command and issues the request command to the lower layer according to the request from the application layer processing section 11 . In addition, the response command reception result notification from the response receiving section 123 is accepted, and the application layer processing section 11 is notified of the reception result of the response command. the

The request notification section 122 receives a request command issue notification from the control section 121 , generates a request command, and outputs it to the lower layer processing section 13 . The response receiving section 123 receives the response command output from the lower layer processing section 13 , analyzes the received response command, and notifies the control section 121 of the received command analysis result and the response command. the

The low layer processing section 13 includes a control section (low layer control section) 131 , a request receiving section 132 , a request notification section 133 and a response generating section 134 . The control section 131 performs control of each block of the request reception section 132, the request notification section 133, and the response generation section 134. Details will be discussed later. the

The request receiving part 132 receives the request command output from the OBEX layer processing part 12, analyzes the request command, and notifies the control part 131 of receiving the command analysis result and the request command. Furthermore, a request command as received data is sent to the request notification section 133 . the

The request notification unit 133 receives the request command notification from the control unit 131 based on the received command analysis result and the meaning of the request command, and reproduces the request command as data received from the request receiving unit 132 by adding necessary header information. Into a request command, and sent to the sending part 14. the

The transmission section 14 transmits the request command received from the lower layer processing section 13 to the outside through an infrared communication line. The receiving section 15 receives a response command from the counterpart device (server device) indicating receipt of the above-mentioned request command via an infrared communication line, and outputs the received response command to the lower layer processing section 13 . the

As shown in FIG. 3, in the server device 5, due to the situation that there is no sending part, or even if the sending part 54 is included, there is a lack of, for example, a response notification for generating a response command to a request command sent from the sending part 14 to the server device 5. part or at least part of the response sending part, so sometimes the reply command cannot be sent back. In data communication with the server device 5 in these cases, an uncomfortable situation in which object exchange cannot be performed sometimes occurs between the client device 1 and the server device 5 . the

Therefore, in the present embodiment, in order to avoid the above-mentioned uncomfortable situation, the response generation section 134 is separately provided in the lower layer processing section 13 . The above-mentioned response generation part 134 receives the response command generation notification from the control part 131 based on the received command analysis result and the meaning of the request command in the request receiving part 132, generates a dummy response command equivalent to the above-mentioned response command, and passes the The response receiving section 123 outputs to the OBEX layer processing section 12 . the

Thus, in this embodiment, even if the original response command from the server device 5 that cannot send back the response command cannot be received, by notifying the above-mentioned dummy response command to the high-level processing part, it is possible to comply with the conventional communication protocol and at the same time The communication state from the client device 1 to the server device 5 is maintained, and an object can be transmitted from the client device 1 to the server device 5 . the

Such a server device 5 will be described below based on FIG. 3 . The server device 5 has at least: an application layer processing section 51 , an OBEX layer processing section 52 , a low layer processing section 53 , and a receiving section 55 . the

The application layer processing section 51 receives application data (image data, text data, etc.) output from the OBEX layer processing section 52, and performs predetermined processing. The OBEX layer processing section 52 includes a control section 521 and a request analysis section 525 . The request analysis section 525 analyzes the request command output from the lower layer processing section 53 and notifies the control section 521 of the analysis result (command type, etc.). the

Furthermore, the request analysis section 525 removes the OBEX header from the received request command, outputs the application data to the application layer processing section 51 based on an instruction from the control section 521, and the control section 521 notifies the analysis result notified from the request analysis section 525 To the application layer processing section 51 , furthermore, based on the analysis result, the request analysis section 525 is instructed to transfer the application data to the application layer processing section 51 . the

The low-level processing section 53 includes a control section 531 and a request analysis section 535 . The request analysis section 535 analyzes the request command from the client device 1 output from the reception section 55 , and notifies the control section 531 of the analysis result (the type of command, etc.). the

Also, the request analysis unit 535 removes the header information attached to each layer from the received request command, extracts the OBEX packet, and outputs the extracted OBEX packet data to the OBEX layer processing unit 52 based on the transfer instruction from the control unit 531 . the

The control section 531 notifies the OBEX layer processing section 52 of the analysis result notified from the request analysis section 535, and instructs to transfer the OBEX packet data extracted by the request analysis section 535 to the OBEX layer processing section 52 based on the analysis result. the

Next, the procedure (communication method) of the client-server data transfer process of this embodiment will be described with reference to the procedure of FIG. 4 and FIG. 1 . In addition, FIG. 4 shows the state of transfer processing of connection, data transfer, and disconnection in the protocol stack of IrDA. the

In the client device 1, the application layer processing unit 11 that has received an object exchange instruction from the user issues a connection request to the OBEX layer processing unit 12 with the server device 5 as a partner device. the

The control section 121 in the OBEX layer processing section 12 that has accepted the above-mentioned connection request accepts the connection request from the application layer processing section 11, instructs the request notification section 122 to generate a connection request command and indicates that the connection request is sent to the low-level processing communication device 3 Order. the

The request notification section 122 accepts an instruction to issue a connection request command from the control section 121 , generates a CONNECT command as a connection request command, and outputs the CONNECT command to the lower layer processing section 13 . The request receiving section 132 in the lower layer processing section 13 receives the CONNECT command output from the OBEX layer processing section 12, notifies the control section 131 of the completion of reception of the connection request command, and outputs received data to the request notification section 133. the

The control section 131 receives the notification of the completion of reception of the connection request command from the request reception section 132 , and instructs the request notification section 133 to issue the connection request command. The request notification section 133 accepts an instruction to issue a connection request command from the control section 131, adds header information to the data received from the request reception section 132, thereby outputs a connection request command to the transmission section 14, and notifies the control section 131 of the connection request The command ends. the

The control unit 131 receives the notification from the request notification unit 133 that the output of the connection request command has been completed, and instructs the response generation unit 134 to issue a dummy response command corresponding to the response command corresponding to the CONNECT command. the

Response generating section 134 accepts an instruction to issue a virtual response command corresponding to the CONNECT command from the control section 131, generates a virtual response command of SUCCESS in accordance with the response command corresponding to the CONNECT command of the high-level OBEX standard, and outputs it to OBEX Layer processing section 12. the

The response receiving part 123 in the OBEX layer processing part 12 receives the dummy response command of SUCCESS outputted from the lower layer processing part 13, recognizes the dummy response command as the response command corresponding to the CONNECT command according to the usual OBEX standard, thereby controlling Section 121 notifies the end of reception of the response command corresponding to the connection request. the

The control section 121 receives the notification from the response receiving section 123 that the response command corresponding to the connection request has been received, and notifies the upper application layer processing section 11 that the connection with the server device 5 as the other party device has been terminated. Thereby, in the application layer processing unit 11, it can be confirmed that the connection with the server device 5 has been terminated, and the object exchange can be started. the

Here, the TinyTP layer, the IrLMP layer, and the IrLAP layer are represented as one block as the lower layer processing unit 13, but of course each layer may constitute one block. In addition, in FIG. 4, in the TinyTP layer located in the next layer of the OBEX layer processing part 12, the virtual response command to the OBEX layer processing part 12 is illustrated, but it can also be used in the IrLMP layer, IrLAP layer as other layers. The layer generates dummy reply commands. the

However, it is preferable to generate a dummy response command to the OBEX layer processing section 12 in the TinyTP layer located next to the OBEX layer processing section 12, saving the time of adding redundant header information and the time of eliminating it. That is, in the case of generation in the TinyTP layer, it is only necessary to generate a dummy response command equivalent to (substantially the same as) a response command based on OBEX and notify the OBEX layer processing unit 12, and generate it in a layer other than the layer directly below In the case of , since it is necessary to generate a virtual response command until passing through the OBEX layer processing part 12, as shown in Table 1 below, it is necessary to add the header information suitable for the protocol layer between the OBEX layer and the layer that generates the virtual response command In the dummy answer command above. the

IrLAP layer header information IrLMP layer header information TinyTP layer header information OBEX virtual answer command

After the connection is completed, for the PUT command used for the transmission of the object data and the DISCONNECT command used for the disconnection process with the counterparty device, it can be seen that, as in the case of the above-mentioned CONNECT command, by the lower layer located in the lower layer of the OBEX layer processing part 12 The processing section 13 can generate a dummy response command corresponding to CONTINUE or SUCCESS of the request command, and can perform transfer to the server device 5 of the partner device as the object data, and disconnection processing with the above-mentioned server device 5, so descriptions of them are omitted here. . the

As described above, as communication using a communication protocol having a layered structure, the request command sent by the client device 1 on the request side receives the response command sent back by the server device that responds to the request. In a communication system using a protocol for object exchange that exchanges objects, the client device 1 of the present embodiment has a function of receiving, in a communication protocol at a lower layer of the above-mentioned object exchange protocol, When a request command is requested, a dummy response command corresponding to the request command based on the above-mentioned protocol for object exchange is generated and notified to the protocol for object exchange that is a higher layer. the

Therefore, without changing the protocol for exchanging objects based on the request command/response command, it is possible to exchange objects with the server device 5 which does not have a sending function but has a minimum required receiving function. In addition, since there is no need to change the protocol for object exchange, existing resources can be called. the

Next, an example of the data structure used in the communication protocol described above will be described. In addition, such a data structure example is applicable also to embodiment mentioned later. First, the data structure of the request command in the case of a connection request is shown in Table 2 below. the

Byte0 Bytes1 and 2 Byte3 Byte4 Bytes5 and 6 Bytes7 to n opcode 0x80 Connect packet length OBEX version Number flags maximum OBEX packet length optional headers

Next, the data structure of the response command in the case of a connection request is shown in Table 3 below. the

Byte0 Bytes1 and 2 Byte3 Byte4 Bytes5 and 6 Bytes7 to n response code Connect response packet length OBEX version Number flags Maximum OBEX packet length Optional headers

(Description of each field) 

· connect packet length, connect response packet length: the packet length of the connection request command and the response command corresponding to the connection request command. the

· OBEX version number: The version number of the OBEX protocol. the

flags: Indicates whether to correspond to multiple IrLMP connections only in the case of a reply command. the

· maximum OBEX packetlength: Indicates the maximum OBEX packet length that each device can receive. the

Next, each example of the request command and the response command is shown in Table 4 below. the

Next, the data structure of the request command in the case of a data transfer request is shown in Table 5 below. the

Byte 0 Bytes 1, 2 Bytes 3 to n Opcode0x02 (0x82: final PUT request)  packet length sequence of headers

Next, the data structure of the response command in the case of a data transfer request is shown in Table 6 below. the

Byte 0 Bytes 1, 2 Bytes 3 to n Response code typical values 0x90 for Continue 0xA0 for Success Response packet length optional response headers

Next, a description of each field described in Table 5 and Table 6 is shown below. the

Packet length, Response packet length: the packet length of the data transfer command and the response command corresponding to the data transfer command. the

Next, examples of the respective request commands and response commands described in the above-mentioned Tables 5 and 6 are shown in the following Tables 7 to 9, respectively. the

Next, the data structure of the request command in the case of a data disconnection request is shown in Table 10 below. the

Byte 0 Byte 1, 2 Bytes 3 to n Opcode 0x81  packet length Optional headers

Next, the data structure of the response command in the case of a data disconnection request is shown in Table 11 below. the

Byte 0 Byte 1, 2 Bytes 3 to n response code 0xA0 or 0xD3 response packet length Optional response headers

Next, a description of each field described in the above-mentioned Table 10 and Table 11 is shown below. the

· packet length, response packet length: the packet length of the disconnection request command and the response command corresponding to the disconnection request command. the

Next, the following Table 12 shows examples of each request command and response command recorded in the above-mentioned Table 10 and Table 11. the

Finally, representative Opcode, Header, and Response Code of OBEX are shown in Table 13 to Table 15 below, respectively. the

·OBEX Operations and Opcode definitions

Opcode Definition Meaning 0x80 Connect choose your partner, negotiation capabilities 0x81 Disconnect signal the end of the session 0x02(0x82) Put send an object

·OBEX Headers

Header ID Header name Description 0x01 Name name of the object(often a file name) 0xC3 Length the length object in bytes 0x48 0x49 Body End of Body a chunk of the object body the final chunk of the object body

·Response Code values

OBEX response code Definition 0x10(0x90) Continue 0x20(0xA0) OK, Success 0x53(0xD3) Service Unavailable

The client device (communication device) of the data transfer system (communication system) according to the second embodiment of the present invention will be described below with reference to FIG. 5 . In addition, terms (including members and functions) defined in other embodiments are assumed to be used in accordance with their definitions in this embodiment unless otherwise stated. the

FIG. 5 is a block diagram showing the configuration of a client device according to this embodiment. As shown in Figure 5, the client device (communication device) 2 has respectively possessed the function identical with the client device 1 of Fig. 1, comprises: application layer processing part 21, OBEX layer processing part (object exchange layer processing part) 22, A low layer processing section 23 , a sending section 24 and a receiving section 25 . the

The application layer processing section 21 requests the OBEX layer processing section 22 to issue a request command in accordance with a user's instruction input to an operation section not shown. In addition, when a notification that a response command has been received is received from the OBEX layer processing section 22, predetermined processing is performed based on the received response command. the

The OBEX layer processing section 22 includes: a control section 221 , a request notification section 222 and a response reception section 223 . The control section 221 notifies the request notification section 222 of the generation of the request command and issues the request command to the lower layer in accordance with the request from the application layer processing section 21 . In addition, the response command reception result notification from the response receiving section 223 is accepted, and the application layer processing section 21 is notified of the reception result of the response command. the

The request notification section 222 receives a request command issue notification from the control section 221 , generates a request command, and outputs it to the lower layer processing section 23 . The response receiving unit 223 receives the response command output from the lower layer processing unit 23, analyzes the received response command, and notifies the control unit 221 of the received command analysis result and the meaning of the response command. the

The low layer processing section 23 includes: a control section (low layer control section) 231, a request reception section 232, a request notification section 233, a response reception section 234, a response notification section 235, a response generation section 236, a multiplexer 237, and a timer 238 . the

The control section 231 performs control of each block of the request reception section 232 , request notification section 233 , response reception section 234 , response notification section 235 , response generation section 236 , multiplexer 237 , and timer 238 . Details will be discussed later. the

The request receiving unit 232 receives the request command from the OBEX layer processing unit 22, analyzes the command, and notifies the control unit 231 of the received command analysis result and the meaning of the request command. At this time, the control unit 231 activates the timer 238 when receiving the notification. The above-mentioned timer 238 measures the elapsed time after the operation. the

Also, the received data is output to the request notification section 233 . The request notification section 233 receives the notification of the request command from the control section 231, adds necessary header information to generate a request command, and outputs it to the transmission section 24. the

The response receiving unit 234 receives data from the lower receiving unit 25, analyzes the received data, and notifies the control unit 231 of the received command analysis result and the meaning of the response command. Also, header information is removed from the received response command, and output to the multiplexer 237 . the

The response notification section 235 outputs the response command output from the multiplexer 237 to the OBEX layer processing section 22 . Response generation unit 236 receives a response command generation notification from control unit 231 , generates a dummy response command similar to that of the above-mentioned first embodiment, and sends it to multiplexer 237 . the

The multiplexer 237 switches the output of the virtual response command generated by the response generation part 236 or the response command from the lower layer output from the response reception part 234 according to the control signal from the control part 231, and outputs to the response notification Section 235. The timer 238 is used to measure a prescribed elapsed time in the control section 231 . the

That is, when the control unit 231 receives the notification of the command analysis result and the meaning of the request command from the request receiving unit 232, it operates the timer 238 to measure (measure) the elapsed time, and after receiving the notification, , even if the above-mentioned elapsed time exceeds the preset setting time, when the notification of the command analysis result and the meaning of the response command from the response receiving part 234 has not been accepted, the above-mentioned virtual response command can be output to the response notification part 235. Control the response generation part 236 and the multiplexer 237. the

The transmission section 24 transmits the request command received from the lower layer processing section 23 to the outside through an infrared communication line. The receiving section 25 receives a response command sent from the counterpart device (server device) through an infrared communication line, and outputs the received response command to the lower layer processing section 23 . the

Next, the procedure (communication method) of the client-server data transfer process according to the second embodiment of the present invention will be described with reference to the procedure of FIG. 6 and FIG. 5 . In addition, FIG. 6 shows the state of transfer processing of connection, data transfer, and disconnection in the protocol stack of IrDA, respectively. the

In the client device 2, the application layer processing unit 21 that received the object exchange instruction from the user sends a connection request to the OBEX layer processing unit 22 with the server device 5 as the partner device. the

The control section 221 in the OBEX layer processing section 22 that has accepted the above-mentioned connection request accepts the connection request from the application layer processing section 21, and instructs the request notification section 222 to generate a connection request command and instructions to send a connection request to the low-level processing communication device 3. Order. the

The request notification section 222 accepts an instruction to issue a connection request command from the control section 221, generates a CONNECT command as a connection request command, and outputs the CONNECT command to the lower layer processing section 23. The request receiving section 232 in the lower layer processing section 23 receives the CONNECT command output from the OBEX layer processing section 22, notifies the control section 231 of the completion of reception of the connection request command, and outputs received data to the request notification section 233. the

The control section 231 accepts the notification of the completion of reception of the connection request command from the request reception section 232 and instructs the request notification section 233 to issue a connection request command. The request notification section 233 receives an instruction from the connection request command from the control section 231, adds header information to the data received from the request reception section 232, thereby outputs a connection request command to the transmission section 24, and notifies the control section 231 of the connection request. The command output ends. the

The control section 231 starts the timer 238 upon receiving the notification from the request notification section 233 that the output of the connection request command has been completed. When the measurement time of the timer 238 has passed the prescribed setting time, the control section 231 judges that a response command has not been sent back from the server device 5 as the counterpart device, and instructs the response generation section 236 to issue a virtual response corresponding to the CONNECT command. The multiplexer 237 is controlled to output the dummy reply command corresponding to the CONNECT command output from the response generating section 236 to the response notifying section 235 . the

Response generation section 236 accepts a virtual response command instruction corresponding to CONNECT command from control section 231, generates a virtual response command of SUCCESS corresponding to CONNECT command in accordance with the OBEX standard as a higher layer, and outputs it to the multiplexer. device 237. the

In addition, when the response command from the server as the counterpart device is sent back before the measurement time of the timer 238 passes a predetermined time, the receiving part 25 receives the data output from the counterpart device (including the above-mentioned response command), and outputs to the low-level processing section 23 . the

The response receiving section 234 in the lower layer processing section 23 analyzes the data received from the receiving section 25, notifies the control section 231 of the completion of reception of the response command corresponding to the connection request, removes the header information, and outputs the received data to the multiplexer. Multiplexer 237. the

The control section 231 receives notification of the completion of reception of the response command corresponding to the connection request from the response receiving section 234 , and controls the multiplexer 237 so that the output data from the response receiving section 234 is output to the response notifying section 235 . Multiplexer 237 switches the output of the received data from response receiving section 234 and response generating section 236 based on a control signal from control section 231 , and outputs the received data to response notification section 235 . the

The response notifying section 235 accepts the notification of the response command from the control section 231, and outputs the response command received from the multiplexer 237 to the OBEX layer processing section 22 which is a higher layer. The response receiving section 223 in the OBEX layer processing section 22 receives a response command corresponding to the CONNEC command from the lower layer, and notifies the control section 221 of the completion of receiving the response command corresponding to the CONNECT command. the

The control section 221 receives notification of the completion of reception of the response command corresponding to the CONNECT command from the response reception section 223 , and notifies the upper application layer processing section 21 that the connection with the partner device has been completed. In this way, the application layer processing unit 21 can confirm that the connection with the partner device (server device) is completed, and the object exchange can be started. the

Here, the TinyTP layer, the IrLMP layer, and the IrLAP layer are represented as one block as the lower layer processing unit 23, but of course each layer may constitute one block. In addition, in FIG. 6, it is illustrated that a virtual response command corresponding to the OBEX layer processing section 22 is generated at the TinyTP layer located one layer lower than the OBEX layer processing section 22, but in any of the IrLMP layer, IrLAP layer of other layers, One can also perform virtual response command generation. However, as described above, it is preferable to generate a dummy response command corresponding to the OBEX layer processing section 12 in the TinyTP layer located one layer lower than the OBEX layer processing section 12, so as to save time and effort for appending redundant header information. The time of deletion. the

After the connection is completed, even for the PUT command for transferring the object data and the DISCONNECT command for disconnecting from the partner device, similar to the case of the above-mentioned CONNECT command, a dummy response corresponding to the request command is generated in the lower layer of the OBEX layer. The command can be used to transfer object data and disconnect from the other device, so it will not be described here. the

As described above, the client device 2 of the present embodiment has a function of issuing a request command issued by the object exchange protocol to a communication protocol located in a lower layer of the communication protocol located in the lower layer of the object exchange protocol. , when a predetermined set time has elapsed, when no response command corresponding to the request command from the server device as the counterpart device is received, a dummy response command corresponding to the request command according to the object exchange protocol is generated , to notify the high-level object exchange protocol. the

Therefore, in communication with a server device having a sending function, object exchange based on a conventional request command/response command can be performed, and in communication with a server device 5 not having a sending function, by generating a dummy response command at a lower layer, Higher layers are thus notified that the communication between the client device 2 and the server device 5 can be started and can be maintained for an object exchange between the two. the

The client device (communication device) of the data transfer system (communication system) according to the third embodiment of the present invention will be described below with reference to FIG. 10 . It should be noted that terms (including members and functions) defined in other embodiments are assumed to be used in accordance with their definitions in this embodiment unless otherwise stated. the

FIG. 10 is a block diagram showing the configuration of a client device according to this embodiment. As shown in Figure 10, client device (communication device) 3 has possessed the same function as client device 1 of Fig. 1 respectively, comprises: application layer processing part 31, OBEX layer processing part (object exchange layer processing part) 32, A low layer processing section 33 , a sending section 34 and a receiving section 35 . the

The application layer processing unit 31 requests the OBEX layer processing unit 32 to issue a request command based on a user's instruction input to an operation unit not shown. In addition, when a notification that a response command has been received is received from the OBEX layer processing unit 32, predetermined processing is performed based on the received response command. the

The OBEX layer processing section 32 includes: a control section 321 , a request notification section 322 and a response reception section 323 . The control section 321 notifies the request notification section 322 of generation of a request command and issuance of a request command (connection request, data transfer request, final data transfer request, disconnection request, etc.) to the lower layer according to a request from the application layer processing section 31. In addition, the response command reception result notification from the response receiving section 323 is accepted, and the application layer processing section 31 is notified of the reception result of the response command. the

The request notification section 322 receives a request command issue notification from the control section 321 , generates a request command, and outputs it to the lower layer processing section 33 . The response receiving unit 323 receives the response command output from the lower layer processing unit 33, analyzes the received response command, and notifies the control unit 321 of the received command analysis result and the meaning of the response command. the

The low layer processing section 33 includes a control section (low layer control section) 331 , a request receiving section 332 , a request notification section 333 , a response receiving section 334 , a response notification section 335 , a response generating section 336 and a multiplexer 337 . the

The control unit 331 controls each block of the request receiving unit 332 , the request notifying unit 333 , the response receiving unit 334 , the response notifying unit 335 , the response generating unit 336 , and the multiplexer 337 . Details will be discussed later. the

The request receiving unit 332 receives a request command from the OBEX layer processing unit 32, analyzes the command, and notifies the control unit 331 of the received command analysis result and the meaning of the request command. the

Furthermore, the request receiving section 332 outputs the received data to the request notifying section 333 . The request notification unit 333 receives the request command issuance notification from the control unit 331 , adds necessary header information to generate a request command, and outputs it to the transmission unit 34 . the

The response receiving unit 334 receives data from the lower receiving unit 35, analyzes the received data, and notifies the control unit 331 of the received command analysis result and the meaning of the response command. Also, header information is removed from the received response command, and output to the multiplexer 337 . the

The response notification section 335 outputs the response command output from the multiplexer 337 to the OBEX layer processing section 32 . the

Response generation unit 336 receives a response command generation notification from control unit 331 , generates a dummy response command similar to that in the first and second embodiments described above, and sends it to multiplexer 337 . the

The multiplexer 337 switches the output of the virtual response command generated by the response generation part 336 or the response command from the lower layer output from the response reception part 334 according to the control signal from the control part 331, and outputs to the response notification Section 335. the

The control section 331 sends a notification based on the request command sent from the OBEX layer processing section 32 as a high level, and determines whether to receive a response command corresponding to a request command sent from the server device or to generate a response command corresponding to a request command corresponding to the OBEX standard. Virtually answer the command and notify the OBEX layer. That is, the control section 331 performs whether to receive the request corresponding to the slave server device according to the type of the request command (connection request, data transfer request, final data transfer request, disconnection request, etc.) notified from the request command sent from the OBEX layer processing section 32. The response command to the transmitted request command is also a switching process for outputting a response command generation notification to the response generating section 336 . the

Then, in the case that the result of the determination is that the response command corresponding to the request command sent from the server device is received, the multiplexer 337 is controlled so that the response receiving part 334 receives the response command received from the receiving part 35 from the server device The response command is output to the response notification section 335. On the other hand, when the result of the determination is that a virtual response command is generated, the response generation section 336 and the multiplexer 337 are controlled so as to output the above-mentioned virtual response command to the response notification section 335 . the

The transmission section 34 transmits the request command received from the lower layer processing section 33 to the outside through an infrared communication line. The reception section 35 receives a response command sent from the counterpart device (server device) through an infrared communication line, and outputs the received response command to the lower layer processing section 33 . the

Next, the procedure (communication method) of the client-server data transfer process according to the third embodiment of the present invention will be described with reference to the procedure of FIG. 12 and FIG. 10 . In addition, FIG. 12 shows the state of transfer processing of connection, data transfer, and disconnection in the protocol stack of IrDA, respectively. the

In the client device 3, the application layer processing unit 31 that received the object exchange instruction from the user sequentially sends a connection request, a data transfer request, and a disconnection request to the OBEX layer processing unit 32 with the server device 5 as the counterpart device. . the

The control section 321 in the OBEX layer processing section 32 that has accepted the above-mentioned request accepts the request from the application layer processing section 31, and instructs the request notification section 322 to generate a request command (connection request, data transfer request, final data transfer request, open request, etc.) and instructs to issue a request command to the lower layer processing section 33. the

The request notification section 322 accepts an instruction to issue a request command from the control section 321 , generates a request command, and outputs the request command to the lower layer processing section 33 . The request receiving section 332 in the lower layer processing section 33 receives the request command output from the OBEX layer processing section 32 , notifies the control section 331 of the completion of reception of the request command, and outputs received data to the request notification section 333 . the

In the control section 331, based on the control signal notified from the OBEX layer processing section 32, it is judged whether to receive a response command corresponding to a request command sent from the server device or to generate a dummy response corresponding to a response command corresponding to a request command based on the OBEX standard. command and notify the OBEX layer. Here, the control section 331 judges that the one corresponding to the request command sent from the server device is received based on the kind of the request command (connection request, data transfer request, final data transfer request, disconnection request, etc.) notified from the OBEX layer processing section 32. The response command also outputs a response command generation notification to the response generating section 336 . the

In this embodiment, when data transfer is performed, if the data transfer request notified from the upper layer is not the final data transfer request, it is assumed that a dummy response command corresponding to a response command corresponding to a request command based on the OBEX standard is generated, and the OBEX layer notification. That is, for the response command of SUCCESS issued at the time of connection request, disconnection request, and final data transfer request, the response command output from the server device can be received, and for the CONTINUE response command, a virtual response command corresponding to it can be generated to notify the OBEX layer . the

In the control section 331, accepting the notification of the end of the request command from the request receiving section 332, instructs the request notification section 333 to issue the request command. The request notification section 333 accepts an instruction from the control section 331 to issue a request command, adds header information to the data received from the request reception section 332, outputs the request command to the transmission section 34, and notifies the control section 331 of the end of the request command output. the

The control section 331 receives the notification of the completion of the output of the request command from the request notification section 333, and instructs the response generation section 336 to issue an output request as The CONTINUE response command corresponding to the virtual response command of the PUT command controls the multiplexer 337 to output the CONTINUE response command which is the virtual response command corresponding to the PUT command output from the response generating section 336 to the response notification Section 335. the

In the response generation part 336, accept the indication that the CONTINUE response command corresponding to the virtual response command of the PUT command from the control part 331 sends out, generate the virtual response command corresponding to the CONTINUE command of the PUT command according to the OBEX standard as a high level, and Output to multiplexer 337. the

In addition, when the control section 331 accepts a connection request, a disconnection request, and a final data transfer request from a higher layer, it controls the multiplexer 337 so that the The response command to the request command is output to the response notification section 335 . the

At this time, the response receiving section 334 in the lower layer processing section 33 analyzes the data received from the receiving section 35, notifies the control section 331 of the completion of reception of the response command corresponding to the request command, removes the header information, and transfers the received data Output to multiplexer 337. the

The control section 331 receives notification of the completion of reception of the response command corresponding to the connection request from the response reception section 334 , and controls the multiplexer 337 so that the output data from the response reception section 334 is output to the response notification section 335 . The multiplexer 337 switches the output of the received data from the response receiving section 334 and the response generating section 336 based on a control signal from the control section 331 , and outputs the received data to the response notifying section 335 . the

The response notifying section 335 accepts the notification of the response command from the control section 331, and outputs the response command received from the multiplexer 337 to the OBEX layer processing section 32 which is a higher layer. The response receiving section 323 in the OBEX layer processing section 32 receives the response command corresponding to the request command from the lower layer, and notifies the control section 321 of the completion of reception of the response command corresponding to the request command. the

The control unit 321 receives notification of the completion of reception of the response command corresponding to the request command from the response receiving unit 323 , and notifies the upper application layer processing unit 31 of completion of connection, data transfer, and disconnection with the partner device. In this way, the application layer processing unit 31 can confirm that the connection, data transfer, and disconnection with the partner device (server device) have been completed, and the object exchange with the server device can be completed. the

Here, the TinyTP layer, the IrLMP layer, and the IrLAP layer are represented as one block as the lower layer processing unit 33 , but of course each layer may constitute one block. In addition, in FIG. 10 , it is illustrated that a virtual response command corresponding to the OBEX layer processing section 32 is generated at the TinyTP layer located one layer lower than the OBEX layer processing section 32, but in any of the IrLMP layer, IrLAP layer of other layers, One can also perform virtual response command generation. However, as described above, it is preferable to generate a dummy response command corresponding to the OBEX layer processing section 32 in the TinyTP layer located one layer lower than the OBEX layer processing section 32, so as to save time and money for appending redundant header information. The time of deletion. the

As described above, the client device 3 of the present embodiment has the function of: among the communication protocols located at the lower layer of the protocol for object exchange, the communication protocol located at the lower layer corresponding to the layer of the protocol for object exchange according to the When a request command is issued according to the protocol for object exchange, a response corresponding to the request command from the partner device is received according to the type of the request command, or a response corresponding to the request command based on the protocol for object exchange is generated. The virtual response command of the command is notified to the protocol layer for object switching corresponding to the upper layer, and switching is performed between the two. the

Therefore, by receiving only the minimum necessary response commands such as connection request, disconnection request, and final data transfer request from the server device, the reliability of communication can be ensured. Response commands, etc., do not require receiving processing, so the circuit scale can be reduced. the

The client device (communication device) of the data transfer system (communication system) according to the fourth embodiment of the present invention will be described below based on FIG. 11 . It should be noted that terms (including members and functions) defined in other embodiments are assumed to be used in accordance with their definitions in this embodiment unless otherwise specified. the

FIG. 11 is a block diagram showing the configuration of a client device according to this embodiment. As shown in Figure 11, client device (communication device) 4 has possessed the same function as client device 1 of Fig. 1 respectively, comprises: application layer processing part 41, OBEX layer processing part (object exchange layer processing part) 42, A low layer processing section 43 , a sending section 44 and a receiving section 45 . the

The application layer processing unit 41 requests the OBEX layer processing unit 42 to issue a request command based on a user's instruction input to an operation unit not shown. In addition, when a notification that a response command has been received is received from the OBEX layer processing unit 42, predetermined processing is performed based on the received response command. the

The OBEX layer processing section 42 includes: a control section 421 , a request notification section 422 and a response reception section 423 . The control section 421 notifies the request notification section 422 of the generation of the request command and the issuance of the request command to the lower layer according to the request from the application layer processing section 41 . In addition, the response command reception result notification from the response receiving section 423 is received, and the application layer processing section 41 is notified of the reception result of the response command. the

The request notification section 422 accepts a request command issue notification from the control section 421, generates a request command, and outputs it to the lower layer processing section 43. The response receiving unit 423 receives the response command output from the lower layer processing unit 43, analyzes the received response command, and notifies the control unit 421 of the received command analysis result and the meaning of the response command. the

The low layer processing section 43 includes: a control section (low layer control section) 431, a request reception section 432, a request notification section 433, a response reception section 434, a response notification section 435, a response generation section 436, a multiplexer 437, and header information Parsing section 438 . the

The control unit 431 controls each block of the request receiving unit 432 , request notifying unit 433 , response receiving unit 434 , response notifying unit 435 , response generating unit 436 , multiplexer 437 , and header information analyzing unit 438 . Details will be discussed later. the

The request receiving unit 432 receives the request command from the OBEX layer processing unit 42, analyzes the command, and notifies the control unit 431 of the received command analysis result and the meaning of the request command. Also, the received data is output to the header information analysis section 438 . the

In the header information analysis part 438, the analysis of the header information of the request command received from the request receiving part 432 is performed, and it is judged whether a response command corresponding to the request command from the server device can be received or a request corresponding to the OBEX standard can be generated. The virtual response command of the response command of the command is notified to the OBEX layer processing unit 42 which is a higher layer, and the judgment result is notified to the control unit 431 . Also, the received data is output to the request notification section 433 . the

The request notification unit 433 receives the request command issuance notification from the control unit 431 , adds necessary header information to generate a request command, and outputs it to the transmission unit 44 . the

The response receiving unit 434 analyzes the received data when receiving the transmission data from the server device from the receiving unit 45 , and notifies the control unit 431 of the received command analysis result and the meaning of the response command. Also, header information is removed from the received response command, and output to the multiplexer 437 . the

The response notification section 435 outputs the response command output from the multiplexer 437 to the OBEX layer processing section 42 . the

Response generation unit 436 receives a response command generation notification from control unit 431 , generates a dummy response command similar to that in the first embodiment, and sends it to multiplexer 437 . the

The multiplexer 437 switches the output of the virtual response command generated by the response generation part 436 or the response command from the lower layer output from the response reception part 434 according to the control signal from the control part 431, and outputs to the response notification Section 435. the

The control section 431 receives notification of the received command analysis result and the meaning of the request command from the request receiving section 432, based on the determination result notified by the header information analysis section 438, upon receiving the response corresponding to the request command transmitted from the server device In the case of notification of the intent of the command, the multiplexer 437 is controlled so that the response receiving unit 434 outputs the response command from the server device received from the receiving unit 45 to the response notifying unit 435 . Further, the control section 431 controls the response generation section 436 and the multiplexer 437 to output the above-mentioned virtual response command to the response notification section 435 when receiving the notification of generating the virtual response command. That is, the control section 431 determines whether to receive a response command corresponding to a request command sent from the server device or to generate a response command corresponding to a request command according to the OBEX standard, based on the header information analyzed by the header information analysis section 438. Virtually respond to the command and notify the switching process of the OBEX layer. the

The transmission section 44 transmits the request command received from the lower layer processing section 43 to the outside through an infrared communication line. The reception section 45 receives a response command sent from the counterpart device (server device) through an infrared communication line, and outputs the received response command to the lower layer processing section 43 . the

Next, the procedure (communication method) of the client-server data transfer process according to the fourth embodiment of the present invention will be described with reference to the procedure of FIG. 12 and FIG. 11 . In addition, FIG. 12 shows the state of transfer processing of connection, data transfer, and disconnection in the protocol stack of IrDA, respectively. the

In the client device 4, the application layer processing unit 41 that received the object exchange instruction from the user sequentially sends a connection request, a data transfer request, and a disconnection request to the OBEX layer processing unit 42 with the server device 5 as the counterpart device. . the

The control section 421 in the OBEX layer processing section 42 that has received the request receives the request from the application layer processing section 41, instructs the request notification section 422 to generate a request command and instructs the lower layer processing section 43 to issue a request command. the

The request notification section 422 accepts an instruction to issue a connection request command from the control section 421 , generates a request command, and outputs the request command to the lower layer processing section 43 . The request receiving unit 432 in the lower layer processing unit 43 receives the request command output from the OBEX layer processing unit 42 , notifies the control unit 431 of the completion of the request command reception, and outputs received data to the header information analyzing unit 438 . the

In the header information analysis section 438, analysis of the request command received from the request reception section 432 is performed. For example, by analyzing the Opcode of the OBEX request command shown in Table 13 above, whether to receive a response command corresponding to a request command sent from the server device or to generate a virtual code corresponding to a response command corresponding to a request command based on the OBEX standard Respond to the command and notify the judgment of the OBEX layer. Here, it is assumed that for CONNECT (0x80), DISCONNECT (0x81) and the last sent PUT (0x82), the response command output from the server device is received, and for other PUTs (0x02), a request corresponding to the OBEX standard is generated The command's response command is a virtual response command and notifies the OBEX layer. That is, for the response command of SUCCESS, the response command output from the server device can be received, and for the response command of CONTINUE, a dummy response command corresponding to it can be generated and notified to the OBEX layer. the

The control section 431 receives the notification of the completion of the request command from the request reception section 432 and instructs the request notification section 433 to issue the request command. The request notification section 433 accepts an instruction from the control section 431 to issue a request command, adds header information to the data received from the request reception section 432, outputs the request command to the transmission section 44, and notifies the control section 431 of the end of the request command output. the

The control section 431 receives the notification of the completion of the output of the request command from the request notification section 433, generates a virtual response command corresponding to the response command corresponding to the request command according to the OBEX standard from the header information analysis section 428, and accepts the notification to the OBEX layer. Notification, that is, when receiving a PUT command (0x02) other than the last sent PUT from the OBEX layer, instruct the response generation part 436 to issue a CONTINUE response command as a dummy response command corresponding to the PUT command, to multiplex The controller 437 controls to output the CONTINUE response command, which is a dummy response command corresponding to the PUT command output from the response generation section 436 , to the response notification section 435 . the

In the response generation part 436, accept the instruction that is sent as the CONTINUE response command corresponding to the virtual response command of the PUT command from the control part 431, generate the virtual response command corresponding to the CONTINUE command of the PUT command according to the high-level OBEX standard, and output to multiplexer 437. the

In addition, in the case of accepting the notification that the response command output from the server device can be received from the header information analysis section 428, that is, receiving the CONNECT command, the DISCONNECT command, and the last sent PUT command from the OBEX layer, multiplex 437 to perform normal reception processing. the

At this time, the response receiving section 434 in the lower layer processing section 43 analyzes the data received from the receiving section 45, notifies the control section 431 of the completion of reception of the response command corresponding to the request command, removes the header information, and outputs the received data. to multiplexer 437. the

In the control section 431, the multiplexer 437 is controlled to output the output data from the response receiving section 434 to the response notifying section 435 in response to notification from the response receiving section 434 that the reception of the response command corresponding to the connection request is completed. The multiplexer 437 switches the output of the received data from the response reception section 434 and the response generation section 436 based on the control signal from the control section 431 , and outputs the received data to the response notification section 435 . the

The response notifying section 435 accepts the notification of the response command from the control section 431, and outputs the response command received from the multiplexer 437 to the OBEX layer processing section 42 which is a higher layer. The response receiving section 423 in the OBEX layer processing section 42 receives the response command corresponding to the request command from the lower layer, and notifies the control section 421 of the completion of reception of the response command corresponding to the request command. the

The control unit 421 receives notification of the completion of reception of the response command corresponding to the request command from the response receiving unit 423 , and notifies the upper application layer processing unit 41 that the connection with the partner device has been completed. In this way, the application layer processing unit 41 can confirm that the connection, data transfer, and disconnection with the partner device (server device) have been completed, and the object exchange with the server device can be completed. the

Here, the TinyTP layer, the IrLMP layer, and the IrLAP layer are expressed as one block as the lower layer processing unit 43 , but of course each layer may constitute one block. In addition, in FIG. 12 , it is illustrated that a virtual response command corresponding to the OBEX layer processing section 32 is generated at the TinyTP layer located one layer lower than the OBEX layer processing section 42, but in any of the IrLMP layer, IrLAP layer of other layers, One can also perform virtual response command generation. However, as described above, it is preferable to generate a dummy response command corresponding to the OBEX layer processing section 42 in the TinyTP layer located one layer lower than the OBEX layer processing section 42, so as to save time and effort for appending redundant header information. The time of deletion. the

As described above, the client device 4 of this embodiment has the function of passing through the communication protocol located at the lower layer corresponding to the layer of the protocol for object exchange among the communication protocols located at the lower layer of the protocol for object exchange. Referring to the header information of the request command issued by the object exchange protocol, according to the type of the request command, receiving a response command corresponding to the request command from the partner device, or generating a response command corresponding to the object exchange protocol. The virtual response command of the response command of this request command is notified to the layer corresponding to the protocol for object switching which is a higher layer, and switching between the two is performed. the

Therefore, by receiving only the minimum necessary response commands such as connection request, disconnection request, and final data transfer request from the server device, the reliability of communication can be ensured. Response commands, etc., do not require receiving processing, so the circuit scale can be reduced. the

The server device (communication device) of the data transmission system (communication system) according to the fifth embodiment of the present invention will be described below based on FIG. 13 . It should be noted that terms (including members and functions) defined in other embodiments are assumed to be used in accordance with their definitions in this embodiment unless otherwise specified. the

FIG. 13 is a block diagram showing the configuration of a server device according to this embodiment. As shown in FIG. 13 , server device (communication device) 1000 includes at least: application layer processing part 1010, OBEX layer processing part (object exchange layer processing part) 1020, low layer processing part 1030 and receiving part 1050. the

The application layer processing unit 1010 requests the OBEX layer processing unit 1020 to perform request command processing based on a user instruction input to an operation unit not shown. In addition, when receiving a notification that a request command has been received from the OBEX layer processing unit 1020, predetermined processing is performed according to the received request command. the

The OBEX layer processing part 1020 includes: a control part 1021 , a response notification part 1022 and a request parsing part 1025 . The control section 1021 notifies the response notification section 1022 of generating a response command and issuing a response command to the lower layer based on the request from the application layer processing section 1010 and the analysis result from the request analysis section 1025 . In addition, the request command reception result notification from the request analysis unit 1025 is accepted, and the application layer processing unit 1010 is notified of the request command reception result. the

The response notification section 1022 accepts a response command issuance notification from the control section 1021 , generates a response command, and outputs it to the lower layer processing section 1030 . The request analysis unit 1025 receives the response command output from the lower layer processing unit 1030, analyzes the received request command, and notifies the control unit 1021 of the received command analysis result and the meaning of the request command. the

The low layer processing section 1030 includes: a control section (low layer control section) 1031 , a response receiving section 1032 , and a request parsing section 1035 . the

The control section 1031 performs control of the response reception section 1032 and the request analysis section 1035 . The details will be discussed later. the

The response receiving unit 1032 receives the response command from the OBEX layer processing unit 1020, analyzes the command, and notifies the control unit 1031 of the received command analysis result and the meaning of the response command. the

When the request analysis unit 1035 receives transmission data from the client device through the reception unit 1050 , it analyzes the received data, and notifies the control unit 1031 of the received command analysis result and the meaning of the request command. Also, header information is removed from the received request command, and output to the OBEX layer processing section 1020 . the

The control section 1031 receives the notification of the command analysis result and the meaning of the response command from the response receiving section 1032, but does not transmit the received response command to the client device. the

The receiving section 1050 receives a request command transmitted from a counterpart device (client device) through an infrared communication line, and outputs the received request command to the lower layer processing section 1030 . the

Next, the operation of the control section in the low-level processing section of the OBEX layer of the conventional server device will be described with reference to the flowchart shown in FIG. 14 . the

Step S11 is a step of judging whether or not a request command from the client is being received. When received, it transfers to step S12, and when not received, it transfers to step S11 again. the

Step S12 is a step of notifying the OBEX layer processing unit that the request command has been received. After the notification is completed, the process moves to step S13. the

Step S13 is a step of judging whether or not a response command has been received from the OBEX layer processing section. When received, it transfers to step S14, and when not received, it transfers to step S13 again. the

Step S14 is a step of sending the above-mentioned OBEX layer response command to the client device. After the transmission is completed, the process moves to step S11. the

Through the above operations, the lower processing part of the OBEX layer in the conventional server device exchanges the reception request command and the transmission response command with the OBEX layer. the

However, in the case of the low-level processing part that performs conventional operations, there is a step of sending a response command from the OBEX layer processing part to the client device, and in communication that does not need to send a response command, the power at the time of sending the response command is reduced. waste. the

In contrast, as shown in FIG. 15 , the control section 1031 of the lower layer processing section 1030 of the present embodiment is characterized by not having a step of sending a response command. The operation of the control unit 1031 of the lower layer processing unit 1030 of this embodiment will be described using the flowchart shown in FIG. 15 . the

Step S21 is a step of judging whether or not a request command from the client is being received. When it is received, it transfers to step S22, and when it does not, it transfers to step S21 again. the

Step S22 is a step of notifying the OBEX layer processing section 1020 that the request command has been received. After the notification is completed, the process moves to step S23. the

Step S23 is to judge whether or not a response command is being received from the OBEX layer processing section 1020 . When received, it transfers to step S21, and when not received, it transfers to step S23 again. In addition, this step S23 may not be provided, and after step S22 is finished, it may transfer to step S21. the

Through the above operations, the control section 1031 in which the lower layer processing section 1030 does not send a response command from the OBEX layer processing section 1020 can be realized. In addition, since the conventional OBEX layer processing part for issuing the response command corresponding to the request command can be used, the resource can be called. the

Next, exchange of commands between the client device and the server device according to this embodiment is shown in FIG. 16 . the

As shown in FIG. 16, in the server device 1000, even if the response command corresponding to the request command from the client device is issued from the OBEX layer processing section 1020 to the TinyTP layer as the lower layer, the lower layer is not notified by the TinyTP layer as the lower layer. The response command, for the client device, realizes that no response command is sent. Furthermore, in FIG. 16, the TinyTP layer of the lower layer of the OBEX layer is used as the lower layer processing part 1030, and the processing of not sending a response command to the lower layer is performed, but the lower layer IrLMP layer or IrLAP layer may also be used as the lower layer processing part 1030, Do the same control. the

A server device (communication device) of a data transfer system (communication system) according to a sixth embodiment of the present invention will be described below. It should be noted that terms (including members and functions) defined in other embodiments are assumed to be used in accordance with their definitions in this embodiment unless otherwise specified. the

FIG. 17 is a block diagram showing the configuration of a server device 1100 according to this embodiment. The server device (communication device) 1100 of this embodiment includes at least: an application layer processing part 1110 , an OBEX layer processing part 1120 , a low layer processing part 1130 , a sending part 1140 and a receiving part 1150 . the

The application layer processing unit 1110 requests the OBEX layer processing unit 1120 to perform request command processing based on a user instruction input to an operation unit not shown. In addition, when receiving a notification that a request command has been received from the OBEX layer processing unit 1020, predetermined processing is performed according to the received request command. the

The OBEX layer processing part 1120 includes: a control part 1121 , a response notification part 1122 and a request parsing part 1125 . The control section 1121 notifies the response notifying section 1122 of generating a response command and issuing a response command to the lower layer based on the request from the application layer processing section 1110 and the analysis result from the request analysis section 1125 . In addition, the request command reception result notification from the request analysis unit 1125 is accepted, and the application layer processing unit 1110 is notified of the request command reception result. the

The response notification section 1122 accepts a response command issue notification from the control section 1121 , generates a response command, and outputs it to the lower layer processing section 1130 . The request analysis unit 1125 receives the response command output from the lower layer processing unit 1130 , analyzes the received request command, and notifies the control unit 1121 of the received command analysis result and the meaning of the request command. the

The low layer processing section 1130 includes: a control section (low layer control section) 1131, a response receiving section 1132, and a request parsing section 1135. the

The control section 1131 performs control of the response reception section 1132 and the request analysis section 1135 . The details will be discussed later. the

The response receiving unit 1132 receives the response command from the OBEX layer processing unit 1120, analyzes the command, and notifies the control unit 1131 of the received command analysis result and the meaning of the response command. the

When the request analysis unit 1135 receives transmission data from the client device from the reception unit 1150 , it analyzes the received data, and notifies the control unit 1131 of the received command analysis result and the meaning of the request command. Also, header information is removed from the received request command, and output to the OBEX layer processing section 1120 . the

The control section 1131 accepts the notification that the command analysis result and the meaning of the response command were received from the response receiving section 1132 , but does not transmit the received response command to the client device. the

The transmission section 1140 transmits the response command received from the lower layer processing section 1030 to the outside through an infrared communication line. the

The receiving section 1150 receives a request command transmitted from a counterpart device (client device) through an infrared communication line, and outputs the received request command to the lower layer processing section 1130 . the

Next, the operation of the control unit 1131 in the lower layer processing unit 1130 of the present embodiment will be described using the flowchart shown in FIG. 18 . the

Step S31 is a step of judging whether or not a request command has been received from the client device. When received, it transfers to step S32, and when not received, it transfers to step S31 again. the

Step S32 is a step of notifying the OBEX layer processing section 1120 that the request command has been received from the client device. After the notification is completed, the process moves to step S33. the

Step S33 is a step of discriminating whether or not a response command is being received from the OBEX layer processing section 1120 . When received, it transfers to step S34, and when not received, it transfers to step S33 again. the

Step S34 is a step of parsing the response command received from the OBEX layer processing section 1120 . After the analysis is completed, the process moves to step S35. the

Step S35 is a step of judging whether the result of the analysis in step S34, the response command received from the OBEX layer processing section 1120 needs to be sent to the client. When it is judged that it is necessary, it transfers to step S36, and when it judges that it is unnecessary, it transfers to step S31. In this step S35, for example, do not send the CONTINUE response command corresponding to the Put command of OBEX, and select to only send the SUCCESS response command. the

Step S36 is a step of sending a response command to the client device. After the transmission is completed, the process moves to step S31. the

By performing the above-described operations in the low-level processing unit 1130 of the server device 1100, it is possible to perform processing that does not send only a response command from a specific OBEX layer to the client device. In addition, since a conventional OBEX layer processing part that issues a response command corresponding to a request command can be used, resource calling can be performed. the

Next, FIG. 19 shows the exchange of commands between the client device and the server device according to this embodiment. the

As shown in the figure, in the server device 1100, even if a specific response command (response command CONTINUE in the figure) corresponding to the request command from the client device is issued from the OBEX layer processing section 1120 to the TinyTP layer as the lower layer, but By not notifying the lower layer of the response command from the TinyTP layer as a lower layer, it is realized that the client device does not transmit a specific response command. Furthermore, in FIG. 19 , the TinyTP layer next to the OBEX layer is used as the lower layer processing unit 1130 to perform processing that does not send a response command to the lower layer, but the lower layer IrLMP layer or IrLAP layer may also be used as the lower layer processing unit 1130. , perform the same control. the

In addition, other operations of the low-level processing unit 1130 are shown using the flowchart of FIG. 20 . the

Step S41 is a step of judging whether or not a request command has been received from the client device. When received, it transfers to step S42, and when not received, it transfers to step S41 again. the

Step S42 is a step of notifying the OBEX layer processing section 1120 that the request command has been received from the client device. After the notification is completed, the process moves to step S43. the

Step S43 is a step of judging whether or not a response command has been received from the OBEX layer processing section 1120 . When received, it transfers to step S44, and when not received, it transfers to step S43 again. the

Step S44 is a step of analyzing the header of the response command received from the OBEX layer processing section 1120 . The analysis carried out here is, for example, judging whether it is a CONTINUE response command corresponding to a non-final Put command, specifically, judging that the first byte of the response command from the OBEX layer processing part 1120 is for CONTINU (0x10 or 0x90), Still SUCCESS (0x20 or 0xA0). After the analysis is completed, the process proceeds to step S45. the

Step S45 is a step of judging whether it is necessary to send the result of the analysis in step S44, the response command received from the OBEX layer processing section 1120, to the client. When it is judged that it is necessary, it transfers to step S46, and when it judges that it is unnecessary, it transfers to step S41. In this step S45, for example, do not send the CONTINUE response command corresponding to the Put command of OBEX, but select to send only the SUCCESS response command. the

Step S46 is a step of sending a response command to the client device. After the transmission is completed, the process moves to step S41. the

By performing the above-described operations in the low-layer processing section 1130 of the server device 1100, it is possible to perform processing that does not send only a response command from a specific OBEX layer to the client device. In addition, since a conventional OBEX layer processing part that issues a response command corresponding to a request command can be used, resource calling can be performed. the

In addition, in the case of the operation of the low-level processing unit 1130 shown in the flowchart of FIG. 20, the exchange of commands between the client device and the server device is also in the sequence shown in FIG. 19 . the

That is, as shown in FIG. 19, in the server device 1100, even if a specific response command (response command CONTINUE in the figure) corresponding to the request command from the client device is issued from the OBEX layer processing section 1120 to TinyTP as the lower layer layer, but the TinyTP layer, which is a lower layer, does not notify the lower layer of the response command, so that the client device does not transmit a specific response command. Furthermore, in FIG. 19, the TinyTP layer which is the next layer of the OBEX layer is used as the lower layer processing part 1130, and the processing of not sending a response command to the lower layer is performed, but the lower layer IrLMP layer or IrLAP layer may also be used as the lower layer processing. Part 1130, performs the same control. the

A client device (communication device) of a data transfer system (communication system) according to a seventh embodiment of the present invention will be described below. It should be noted that terms (including members and functions) defined in other embodiments are assumed to be used in accordance with their definitions in this embodiment unless otherwise specified. the

First, FIG. 21 is a block diagram of a client device that communicates using the conventional OBEX protocol. the

As shown in FIG. 21, a conventional client device (communication device) 1200 includes at least: an application layer processing section 1210, an OBEX layer processing section (object exchange layer processing section) 1220, a low-level processing section 1230, a sending section 1240, and a receiving section 1250. . the

The application layer processing unit 1210 requests the OBEX layer processing unit 1220 to issue a request command based on a user instruction input to an operation unit not shown. the

The OBEX layer processing section 1220 includes: a control section 1221 , a request notification section 1222 and a response reception section 1223 . the

The control section 1221 notifies the request notification section 1222 of the generation of the request command and the issuance of the request command to the lower layers, according to the request from the application layer processing section 1210 . In addition, the response command reception result notification from the response receiving section 1223 is received, and the application layer processing section 1210 is notified of the reception result of the response command. the

The request notification section 1222 receives a request command issue notification from the control section 1221 , generates a request command, and outputs it to the lower layer processing section 1230 . The response receiving unit 1223 receives the response command output from the lower layer processing unit 1230 , analyzes the received response command, and notifies the control unit 1221 of the received command analysis result and the meaning of the response command. the

The lower layer processing section 1230 adds an appropriate lower layer header to the request command from the OBEX layer processing section 1220 and forwards it to the sending section 1240, and simultaneously removes the appropriate lower layer header from the reception response command from the receiving section 1250, and transmits it to OBEX layer processing section 1220 . the

The transmission section 1240 transmits the request command received from the lower layer processing section 1230 to the outside through an infrared communication line. the

Transmitting section 1250 receives a response command transmitted from a counterpart device (server device) through an infrared communication line, and outputs the received response command to low layer processing section 1230 . the

Next, the operation of the control unit 1221 of the OBEX layer processing unit 1220 in FIG. 21 will be described using the flowchart shown in FIG. 22 . the

Step S51 is a step of discriminating whether or not a request command to the server device has occurred in the application layer processing section 1210 of the client device 1200 and the control section 1221 of the OBEX layer processing section 1220 . When it occurs, it transfers to step S52, and when it does not occur, it transfers to step S51 again. the

Step S52 is a step of sending a request command to the server device to the lower layer processing section 1230 . After the transmission is completed, the process moves to step S53. the

Step S53 is a step of discriminating whether or not a response command from the server device has been received from the lower layer processing section 1230 . When it is received, it transfers to step S54, and when it does not receive it, it transfers to step S53 again. the

Step S54 is a step of analyzing the received response command. After the analysis is completed, the process proceeds to step S55. the

Step S55 is a step of judging whether or not the communication has ended. When the communication has not ended, it transfers to step S51 again. the

Through the above operations, the OBEX layer processing unit 1220 of the conventional client device 1200 can issue a request command, analyze the corresponding response command, and issue the next request command again to perform communication. the

However, in the operation of the OBEX layer processing unit 1220 of the conventional client device 1200 described above, there is a problem that the next request command cannot be transmitted unless a response command is received from the server device. the

In order to solve this problem, as shown in the flowchart of FIG. 24, in the client device 1300 (FIG. 23) of this embodiment, after sending a request command to the server device, even if no response command from the server device is received, the The next request command can be issued. Specifically, it is as follows. the

Step S61 is a step of discriminating whether or not a request command to the server device has occurred in the application layer processing section 1310 of the client device 1300 and the control section 1321 of the OBEX layer processing section 1320 . When it occurs, it transfers to step S62, and when it does not occur, it transfers to step S61 again. the

Step S62 is a step of sending a request command to the server device to the lower layer processing section 1330 . After the transmission is completed, the process moves to step S65. the

Step S65 is a step of judging whether or not the communication has ended. If the communication has not ended, the procedure goes to step S61 again. the

After the above operations are performed by the control unit 1321 of the OBEX layer processing unit 1320 of the client device 1300, after the request command is sent from the client device 1300, the next request command can be sent even if no response command is received from the server device. the

Here, FIG. 23 is a block diagram of the client device 1300 of the present embodiment. the

Each block of the OBEX layer processing section (object exchange layer processing section) 1320 other than the communication direction selection section 1324 has the same function as each block of the OBEX layer processing section 1220 of the above-mentioned conventional client device 1200 described using FIG. 21 , So omit description. the

The communication direction selection section 1324 has a function of selecting whether the communication is one-way communication or two-way communication. The so-called one-way communication here is communication in which a request command from a client device does not require a response command from a server device. In the case where there is no sending part in the server device, or in the case where there is no receiving part in the client device, it must be one-way communication, but in the case where the client device and the server device have a sending part and a receiving part respectively, but the signal In the case where the flow is unidirectional from the client device to the server device, it is still a unidirectional communication. The two-way communication is a communication method in which, for a request command sent by the client device, the server device sends a response command, and after the response command is analyzed, the client device sends the next request command. In this case, if the response command is not necessarily required for all request commands, it is not necessarily necessary to respond to a specific request command if both the OBEX layer of the client device and the OBEX layer of the server device agree in advance. Answer the command. the

Next, the operation of the control unit 1321 of the OBEX layer processing unit 1320 of the client device 1300 according to this embodiment will be described using the flowchart of FIG. 25 . the

Step S70 is a step in which the communication direction selection section 1324 selects whether bidirectional communication or unidirectional communication. In the case of two-way communication, it transfers to step S71, and in the case of one-way communication, it transfers to S81. the

Step S71 is a step of discriminating whether or not a request command to the server device has occurred in the application layer processing section 1310 or the control section 1321 of the OBEX layer processing section 1320 in bidirectional communication. When it occurs, it transfers to step S72, and when it does not occur, it transfers to step S71 again. the

Step S72 is a step of sending a request command to the server device to the lower layer processing section 1330 in two-way communication. After the transmission is completed, the process moves to step S73. the

Step S73 is a step of judging whether or not a response command from the server device has been received in bidirectional communication. When received, it transfers to step S74, and when not received, it transfers to step S73 again. the

Step S74 is a step of analyzing the response command from the server device in bidirectional communication. After the analysis is completed, the process proceeds to step S75. the

Step S75 is a step of judging whether or not to end the communication during the two-way communication. When not finished, it transfers to step S71 again. the

On the other hand, step S81 is a step of discriminating whether a request command to the server device has occurred in the application layer processing section 1310 or the control section 1321 of the OBEX layer processing section 1320 in one-way communication. When it occurs, it transfers to step S82, and when it does not occur, it transfers to step S81 again. the

Step S82 is a step of sending a request command to the server device to the lower layer processing section 1330 in one-way communication. After the transmission is completed, the process moves to step S85. the

Step S85 is a step of judging whether to end the communication during the one-way communication. When not finished, it transfers to step S81 again. the

The above operations are performed by the control section 1321 of the OBEX layer processing section 1320 of the client device 1300. In two-way communication, the next request command is sent from waiting for a response command from the server device. The response command of the server device can also send the next request command. the

A client device (communication device) of a data transmission system (communication system) according to an eighth embodiment of the present invention will be described below. It should be noted that terms (including members and functions) defined in other embodiments are assumed to be used in accordance with their definitions in this embodiment unless otherwise specified. the

FIG. 23 is a block diagram of a client device 1300 of the present embodiment. That is, it is the same as the above-mentioned seventh embodiment, and the operation of each block other than the control section 1321 of the OBEX layer processing section 1320 is basically the same as that of the seventh embodiment, so description thereof will be omitted. the

The operation of the control unit 1321 of the OBEX layer processing unit 1320 in this embodiment will be described using the flowchart shown in FIG. 26 . the

Step S91 is a step of discriminating whether a Put request command to the server device has occurred in the application layer processing section 1310 or the control section 1321 of the OBEX layer processing section 1320 . When it occurs, it transfers to step S92, and when it does not occur, it transfers to step S91 again. the

Step S92 is a step of sending a Put request command to the server device. After the transmission is completed, the process moves to step S93. the

Step S93 is a step of judging whether the transmitted Put request command is the final Put request command. When it is final, it transfers to step S94, and when it is not final, it transfers to step S91. the

Step S94 is a step of judging whether a response command from the server device has been received. When received, it transfers to step S95, and when not received, it transfers to step S94 again. the

Step S95 is a step of parsing the response command from the server device. After the analysis is completed, the process proceeds to step S96. At this time, it is judged whether or not a SUCCESS response command corresponding to the final Put request command has been received. the

Step S96 is a step of judging whether or not the communication has ended. When not finished, it transfers to step S91 again. the

By performing the above actions by the control section 1321 of the OBEX layer processing section 1320 of the client device 1300, the next Put request command can be sent without waiting for the CONTINUE response command from the server device for a Put request command that is not the final one, which can improve communication. s efficiency. In addition, since the client device 1300 confirms the SUCCESS response command from the server device corresponding to the final Put command, the client device 1300 can determine whether data transfer to the server device can be normally performed. the

In addition, as shown in Figure 26, through the switching and combination of two-way communication and one-way communication of the communication direction selection part 1324, the following actions can be performed: when it becomes two-way communication, only the final Put command needs a SUCCESS response command, and when one-way communication , no response command is required for all request commands. the

A server device (communication device) of a data transfer system (communication system) according to a ninth embodiment of the present invention will be described below. It should be noted that terms (including members and functions) defined in other embodiments are assumed to be used in accordance with their definitions in this embodiment unless otherwise specified. the

First, FIG. 27 shows a block diagram of a server device that communicates using the conventional OBEX protocol. the

As shown in Figure 27, the server device (communication device) 1400 at least includes: application layer processing part 1410, OBEX layer processing part (object exchange layer processing part) 1420, low layer processing part 1430, sending part 1440 and receiving part 1450. the

The application layer processing unit 1410 requests the OBEX layer processing unit 1420 to process a reception request command and issue a response command based on a user instruction input to an operation unit not shown. the

The OBEX layer processing part 1420 includes: a control part 1421 , a response notification part 1422 and a request parsing part 1423 . the

The control section 1421 notifies the response notification section 1422 that a response command can be generated and that a response command is issued to a lower layer, according to a request from the application layer processing section 1410 . In addition, the request command reception result from the request analysis unit 1423 is accepted, and the application layer processing unit 1410 is notified of the request command reception result. the

The response notification section 1422 accepts a response command issuance notification from the control section 1421 , generates a response command, and outputs it to the lower layer processing section 1430 . The request analysis unit 1423 receives the request command output from the lower layer processing unit 1430 , analyzes the received request command, and notifies the control unit 1421 of the received command analysis result and the meaning of the request command. the

The lower layer processing part 1430 adds the appropriate lower layer header to the response command from the OBEX layer processing part 1420 and transfers it to the transmission part 1440, and removes the appropriate lower layer header from the reception request command from the receiving part 1450, and then transfers to the OBEX layer processing section 1420 . the

The transmission section 1440 transmits the request command received from the lower layer processing section 1430 to the outside through an infrared communication line or the like. the

The receiving section 1450 receives a request command transmitted from a counterpart device (client device) through an infrared communication line or the like, and outputs the received request command to the low layer processing section 1430 . the

Next, the operation of the control unit 1421 of the OBEX layer processing unit 1420 of the conventional OBEX server device 1400 shown in FIG. 27 will be described using the flowchart shown in FIG. 28 . the

Step S101 is a step of judging whether or not a request command has been received from a client device. In the case of reception, transfer to step S102, and in the case of non-reception, transfer to step S101 again. the

Step S102 is a step of parsing the request command from the client device. After the analysis is completed, the process moves to step S103. the

Step S103 is a step of forming a response command to the client device. After the completion of the response command formation, the process moves to step S104. the

Step S104 is a step of sending the response command to the client device. After the transmission is completed, the process moves to step S105. the

Step S105 is a step of judging whether to end the communication. When not finished, it transfers to step S101 again. the

Through the above operations, the OBEX layer processing unit 1420 of the conventional server device 1400 receives and analyzes the request command, generates and transmits a corresponding response command, thereby enabling communication. the

However, in the operation of the OBEX layer processing unit 1420 of the above-mentioned conventional server device 1400, a response command is generated and transmitted for a request command from the client device, so, for example, one-way communication does not require a response command from the server device 1400. In the communication of sending and receiving, the electric power consumed for generating the response command becomes wasted electric power. the

In order to solve this, as shown in the flowchart of FIG. 30, in the server device 1500 (FIG. 29) of this embodiment, after receiving and analyzing the request command from the client device, it is not necessary to generate and send a response to the client device. command while receiving the next request command. Specifically, it is as follows. the

Step S111 is a step of judging whether or not a request command from the client device has been received. When received, it transfers to step S112, and when not received, it transfers to step S111 again. the

Step S112 is a step of analyzing the received request command. After the analysis is completed, the process moves to step S115. the

Step S115 is a step of judging whether or not the communication has ended. When not finished, it transfers to step S111 again. the

By performing the above operations by the control unit 1521 of the OBEX layer processing unit 1520 of the server device 1500, the next request command can be received without generating and transmitting a response command corresponding to the received request command. the

Here, FIG. 29 is a block diagram of a server device 1500 in another form of this embodiment. the

Each block other than the communication direction selection part 1524 of the OBEX layer processing part (object exchange layer processing part) 1520 has the same function as each block of the OBEX layer processing part 1420 of the above-mentioned conventional server device 1400 described with FIG. 27, so Description omitted. the

The communication direction selection section 1524 has a function of selecting whether the communication is one-way communication or two-way communication. Here, the so-called one-way communication is communication that does not require a response command from the server device for a request command from the client device. In the case where there is no sending part in the server device, or in the case where there is no receiving part in the client device, it must be one-way communication, but in the case where the client device and the server device have a sending part and a receiving part respectively, but the signal In the case where the flow is unidirectional from the client device to the server device, it is still a unidirectional communication. The two-way communication is a communication method in which, for a request command sent from a client device, the server device sends a response command, and after the response command is analyzed, the client device sends the next request command. In this case, if a response command is not necessarily required for all request commands, a response corresponding to a specific request command is not necessarily required if both the OBEX layer of the client device and the OBEX layer of the server device agree in advance. Order. the

Next, the operation of the control unit 1521 of the OBEX layer processing unit 1520 of the server device 1500 according to this embodiment will be described using the flowchart of FIG. 31 . the

Step S120 is a step in which communication direction selection section 1524 selects whether bidirectional communication or unidirectional communication. In the case of two-way communication, it transfers to step S121, and in the case of one-way communication, it transfers to S131. the

Step S121 is a step of judging whether or not a request command has been received from the client device in bidirectional communication. When received, it transfers to step S122, and when not received, it transfers to step S121 again. the

Step S122 is a step of parsing the request command from the client device in bidirectional communication. After the analysis is completed, the process moves to step S123. the

Step S123 is a step of forming a response command to the client device in two-way communication. After completion of the response command formation, the process proceeds to step S124. the

Step S124 is a step of notifying the lower layer processing section 1530 in order to transmit the formed response command to the client device in bidirectional communication. After the notification ends, the process moves to step S125. the

Step S125 is a step of judging whether to end the communication. When not finished, it transfers to step S121 again. the

On the other hand, step S131 is a step of discriminating whether or not a request command from the client device has been received in the one-way communication. When received, it transfers to step S132, and when not received, it transfers to step S131 again. the

Step S132 is a step of parsing the request command from the client device in one-way communication. After the analysis ends, transfer to step S135 again. the

Step S135 is a step of judging whether or not the communication has ended during the one-way communication. When not finished, it transfers to step S131 again. the

By performing the above actions by the control part 1521 of the OBEX layer processing part 1520 of the server device 1500, in two-way communication, when receiving a request command from a client device, a response command can be generated and sent; After receiving a request command from the client device, the next request command is received without generating and transmitting a response command. the

A server device (communication device) of a data transmission system (communication system) according to a tenth embodiment of the present invention will be described below. It should be noted that terms (including members and functions) defined in other embodiments are assumed to be used in accordance with their definitions in this embodiment unless otherwise specified. the

FIG. 29 is a block diagram of server device 1500 of the present embodiment. That is, it is the same as the above-mentioned ninth embodiment, and the operation of each block other than the control section 1521 of the OBEX layer processing section 1520 is also basically the same as that of the ninth embodiment, so description thereof will be omitted. the

The operation of the control unit 1521 of the OBEX layer processing unit 1520 in this embodiment will be described using the flowchart shown in FIG. 32 . the

Step S141 is a step of judging whether or not a Put command has been received from the client device. When received, it transfers to step S142, and when not received, it transfers to step S141 again. the

Step S142 is a step of analyzing the received Put command. After the analysis is completed, the process moves to step S143. the

Step S143 is a step of judging whether the analyzed Put command is not the final Put command. When it is the final Put command, it transfers to step S144, and when it is not the final Put command, it transfers to step S141 again. the

Step S144 is a step of generating a response command to the client device. After the generation of the response command is completed, the process proceeds to step S145. In addition, in this step S144, when all the Put commands from the client are normally completed in the response command generated in this step S144, it becomes a SUCCESS response command, for example. However, other cases are not mentioned in this embodiment. the

Step S145 is a step of notifying the lower layer processing section 1530 in order to transmit the above-mentioned response command to the client device. After the notification ends, the process moves to step S146. the

Step S146 is a step of judging whether or not the communication has ended. When not finished, it transfers to step S141. the

By performing the above actions by the control section 1521 of the OBEX layer processing section 1520 of the server device 1500, for the non-final Put request command, the generation and transmission of the CONTINUE response command generated by the conventional OBEX layer processing section may not be performed. Request commands, generate and send SUCCESS response commands, which can improve communication efficiency. In addition, since the SUCCESS response command corresponding to the final Put command is transmitted to the client device, the client device can determine whether or not data transfer to the server device 1500 can be normally performed. the

In addition, as shown in FIG. 31, through the switching and combination of two-way communication and one-way communication of the communication direction selection part 1524, the following actions can be performed: in the case of two-way communication, only generate and send a SUCCESS response command for the final Put command, and In one-way communication, response commands are not generated and transmitted for all request commands. the

A transmission system (communication system) for transmitting data according to an eleventh embodiment of the present invention will be described below. It should be noted that terms (including members and functions) defined in other embodiments are assumed to be used in accordance with their definitions in this embodiment unless otherwise specified. the

An example of communication between mobile phones according to this embodiment will be described with reference to FIG. 33 . the

Furthermore, in this embodiment, a mobile phone is used on the client device (sender) and the server device (receiver), but either the client device (sender) or the server device (receiver) is a mobile phone Just can, as long as one of the communication methods of the present invention mentioned above can be used to send or receive data by infrared rays, etc., the opposite device does not need to be a mobile phone. the

In addition, in FIG. 33, mobile phone A is shown as a client device (transmitter), and mobile phone B is shown as a server device (receiver), but the reverse may also be used. the

In FIG. 33, data in mobile phone A is transmitted to mobile phone B using infrared rays. When mobile phone B receives data transmitted from mobile phone A, the received data is stored in a memory in mobile phone B or in a connected external memory. The data mentioned above are text data, image data, audio data, phonebook data, system information, etc., and are not limited to a specific format. The data in the mobile phone A may be any data in the internal memory of the mobile phone A or data in an external memory (nonvolatile memory such as an SD card) connected to the mobile phone. the

An example of communication between mobile phones according to this embodiment will be described in detail as follows. the

For example, in two-way communication, in the sender client device (mobile phone A), when a Put command that is not the final is sent at the OBEX layer, the next Put command is sent without waiting for the CONTINUE response command, and the final Put command is sent. , wait for the SUCCESS response command from the receiving end server device (portable phone B) to confirm whether the communication is normally carried out. In addition, the OBEX layer that requires the conventional CONTINUE response command can also be called by analogously forming the above-mentioned CONTINUE response command in the low-level processing part of the OBEX layer and notifying the OBEX layer. the

In addition, in the server device (mobile phone B) on the receiving side, when the OBEX layer receives a non-final Put command from the client device (mobile phone A) on the sending side, it does not generate and send a CONTINUE response command, but receives the final Put command. Generate and send a SUCCESS command for the Put command. When a non-final Put command is received, the conventional OBEX layer that generates and transmits a CONTINUE response command is called, and the lower layer only needs not to transmit the CONTINUE command to the client device. the

By implementing the above communication between the client device (mobile phone A) on the sending side and the server device (mobile phone B) on the receiving side, data can be transferred using object switching with high communication efficiency and good communication quality in two-way communication. . the

Also, for example, in one-way communication, when the OBEX layer sends all the request commands in the sending client device (mobile phone A), the next request command is sent without waiting for a response command from the server device. Furthermore, for each request command from the OBEX layer, the lower layer of OBEX simulates an appropriate response command and notifies the OBEX layer, so that the OBEX layer of the conventional necessary response command can be called. the

Also, when the OBEX layer receives all the request commands from the source client device (mobile phone A) in the receiving server device (mobile phone B), it does not generate and transmit a response command. Instead of calling the conventional OBEX layer that generates and transmits a response command corresponding to the received request command, the lower layer may transmit the response command from the OBEX layer to the client device. the

By realizing the above-mentioned communication between the client device (mobile phone A) on the sending side and the server device (mobile phone B) on the receiving side, even in one-way communication, data can be transferred using an object exchange protocol such as OBEX. the

A transmission system (communication system) for transmitting data according to a twelfth embodiment of the present invention will be described below. It should be noted that terms (including members and functions) defined in other embodiments are assumed to be used in accordance with their definitions in this embodiment unless otherwise specified. the

An example of communication between the mobile phone and the display device according to this embodiment will be described with reference to FIG. 34 . the

Furthermore, in this embodiment, the mobile phone A and the display device B (such as TV, etc.) are respectively used on the client device (transmitter) and the server device (receiver), but if any one of the above-mentioned present inventions If data can be transmitted using infrared rays or the like, the server device (transmitter) does not need to be a mobile phone. In addition, the display device B may be a client device (transmitter), and the mobile phone A may be a server device (receiver). the

In addition, in FIG. 34, the data in the mobile phone A is transmitted to the display device B using infrared rays. In the display device B, the data transmitted from the mobile phone A is appropriately processed, for example, in the case of image data, if necessary, the compressed data is decompressed and displayed, but not limited thereto. In addition, the above-mentioned data are text data, image data, voice data, phone book data, system information, etc., and are not limited to data in a specific format. In addition, the data in the mobile phone A may be data in the internal memory of the mobile phone A or data in an external memory (nonvolatile memory such as an SD card) connected to the mobile phone. the

An example of communication between the mobile phone and the display device according to this embodiment will be described in detail below. the

For example, during two-way communication, in the client device (mobile phone A) at the sending end, when a Put command that is not final is sent at the OBEX layer, the next Put command is sent without waiting for the CONTINUE response command, and the final Put command is sent after sending the final Put command. In the case of a Put command, it waits for a SUCCESS response command from the server device (display device B) at the receiving end, and confirms whether the communication is normally performed. Furthermore, by analogously forming the above-mentioned CONTINUE response command in the low-level processing part of the OBEX layer and notifying the OBEX layer, the OBEX layer that required the conventional CONTINUE response command can be called. the

In the receiving end server device (display device B), when the OBEX layer receives a non-final Put command from the sending end client device (mobile phone A), it does not generate and send a CONTINUE response command, and receives the final Put command. For command, generate and send SUCCESS response command. In addition, when a not-final Put command is received, the conventional OBEX layer that generates and transmits a CONTINUE response command is called, and the lower layer does not need to transmit the CONTINUE command to the client device. the

By realizing the above-mentioned communication between the client device (mobile phone A) on the sending side and the server device (display device B) on the receiving side, it is possible to exchange, for example, image data in two-way communication using object exchange with high communication efficiency and high communication quality. transmission. the

Also, for example, in the case of one-way communication, when all the request commands are sent at the OBEX layer in the sending client device (mobile phone A), the next request command is sent without waiting for a response command from the client device. Furthermore, for each request command from the OBEX layer, by generating an appropriate response command in the lower layer of OBEX analogously and notifying the OBEX layer, the OBEX layer of the conventional necessary response command can be called. the

In the receiving side server device (display device B), when the OBEX layer receives all the request commands from the sending side client device (mobile phone A), it does not generate and transmit a response command. In addition, the conventional OBEX layer that generates and transmits a response command corresponding to the received request command may be called instead of sending the response command from the OBEX layer to the client device by the lower layer. the

By implementing the above communication between the client device (mobile phone A) on the sending side and the server device (display device B) on the receiving side, even in one-way communication, for example, image data can be transferred using an object exchange protocol such as OBEX . the

A transmission system (communication system) for transmitting data according to the thirteenth embodiment of the present invention will be described. It should be noted that terms (including members and functions) defined in other embodiments are assumed to be used in accordance with their definitions in this embodiment unless otherwise specified. the

An example of communication between the mobile phone and the printer according to this embodiment will be described with reference to FIG. 35 . the

Furthermore, in this embodiment, the mobile phone A and the printing device B (such as a printer, etc.) are respectively used on the client device (sender) and the server device (receiver), but if any of the modes of the present invention described above Since data can be transmitted using infrared rays, etc., the server device (transmitter) does not need to be a mobile phone. Also, the printer B may be a client device (sender) and the mobile phone A may be a server device (receiver). the

In addition, in FIG. 35, the data in the mobile phone A is transmitted to the printer B using infrared rays. In the printing device B, the data sent from the mobile phone A is appropriately processed, for example, in the case of image data, if necessary, the compressed data is decompressed, etc., and then printed, but not limited to this. In addition, the above-mentioned data are text data, image data, voice data, phone book data, system information, etc., and are not limited to data in a specific format. In addition, the data in the mobile phone A may be data in the internal memory of the mobile phone A or data in an external memory (nonvolatile memory such as an SD card) connected to the mobile phone. the

An example of communication between the mobile phone and the printing device according to this embodiment will be described in detail below. the

For example, during two-way communication, in the client device (mobile phone A) at the sending end, when a Put command that is not final is sent at the OBEX layer, the next Put command is sent without waiting for the CONTINUE response command, and the final Put command is sent after sending the final Put command. In the case of the Put command, it waits for a SUCCESS response command from the server device (printer B) at the receiving end, and confirms whether the communication is normally performed. Furthermore, by analogously forming the above-mentioned CONTINUE response command in the low-level processing part of the OBEX layer and notifying the OBEX layer, the OBEX layer that required the conventional CONTINUE response command can be called. the

In the receiving server device (printer B), when the OBEX layer receives a non-final Put command from the sending client device (mobile phone A), it does not generate and send a CONTINUE response command, and receives the final Put command. command, generate and send a SUCCESS response command. In addition, when a not final Put command is received, the conventional OBEX layer that generates and transmits a CONTINUE response command is called, and the lower layer does not need to transmit the CONTINUE command to the client device. the

By implementing the above communication between the client device (mobile phone A) on the sending side and the server device (printing device B) on the receiving side, in two-way communication, object exchange with high communication efficiency and good communication quality can be used, such as image data transmission. the

Also, for example, in the case of one-way communication, when all the request commands are sent at the OBEX layer in the sending client device (mobile phone A), the next request command is sent without waiting for a response command from the client device. Furthermore, for each request command from the OBEX layer, by generating an appropriate response command in the lower layer of OBEX analogously and notifying the OBEX layer, the OBEX layer of the conventional necessary response command can be called. the

In the receiving client device (printer B), when the OBEX layer receives all the request commands from the transmitting client device (mobile phone A), it does not generate and transmit a response command. In addition, the conventional OBEX layer that generates and transmits a response command corresponding to the received request command may be called instead of sending the response command from the OBEX layer to the client device by the lower layer. the

By realizing the above-mentioned communication between the client device (mobile phone A) on the sending side and the server device (printing device B) on the receiving side, even in one-way communication, it is possible to use an object exchange protocol such as OBEX, for example, to transfer image data . the

A transmission system (communication system) for transmitting data according to a fourteenth embodiment of the present invention will be described below. It should be noted that terms (including members and functions) defined in other embodiments are assumed to be used in accordance with their definitions in this embodiment unless otherwise specified. the

An example of communication between the mobile phone and the printer according to this embodiment will be described with reference to FIG. 36 . the

Furthermore, in this embodiment, a mobile phone A and a recording device B (for example, an HDD recording device, a DVD recording device, etc.) are respectively used on the client device (transmitter) and the server device (receiver). In any aspect of the present invention, if data can be transmitted by infrared rays or the like, the server device (transmitter) does not need to be a mobile phone. In addition, the recording device B may be a client device (transmitter), and the mobile phone A may be a server device (receiver). the

In addition, in FIG. 36, the data in the mobile phone A is transmitted to the recording device B using infrared rays. In the printer B, the data transmitted from the mobile phone A is appropriately processed. For example, in the case of video data, if necessary, appropriate compression processing, decompression processing, and other video processing are performed, and then recorded in the A recording section within a recording device, but not limited thereto. In addition, the above-mentioned data are text data, image data, video data, voice data, phone book data, system information, etc., and are not limited to data in a specific format. In addition, the data in the mobile phone A may be data in the internal memory of the mobile phone A or data in an external memory (nonvolatile memory such as an SD card) connected to the mobile phone. the

Next, an example of communication between the mobile phone and the recording device according to this embodiment will be described in detail. the

For example, during two-way communication, in the client device (mobile phone A) at the sending end, when a Put command that is not final is sent at the OBEX layer, the next Put command is sent without waiting for the CONTINUE response command, and the final Put command is sent after sending the final Put command. In the case of a Put command, it waits for a SUCCESS response command from the server device (recorder B) at the receiving end, and checks whether the communication is performed normally. Furthermore, by analogously forming the above-mentioned CONTINUE response command in the low-level processing part of the OBEX layer and notifying the OBEX layer, the OBEX layer that required the conventional CONTINUE response command can be called. the

In the receiving server device (recorder B), when the OBEX layer receives a non-final Put command from the sending client device (mobile phone A), it does not generate and send a CONTINUE response command, and receives the final Put command. command, generate and send a SUCCESS response command. In addition, when a not final Put command is received, the conventional OBEX layer that generates and transmits a CONTINUE response command is called, and the lower layer does not need to transmit the CONTINUE command to the client device. the

By realizing the above communication between the client device (mobile phone A) on the sending side and the server device (recording device B) on the receiving side, in two-way communication, object exchange with high communication efficiency and good communication quality can be used, such as video data transmission. the

Also, for example, in the case of one-way communication, when all the request commands are sent at the OBEX layer in the sending client device (mobile phone A), the next request command is sent without waiting for a response command from the client device. Furthermore, for each request command from the OBEX layer, by generating an appropriate response command in the lower layer of OBEX analogously and notifying the OBEX layer, the OBEX layer of the conventional necessary response command can be called. the

In the receiving client device (recorder B), when the OBEX layer receives all the request commands from the transmitting client device (mobile phone A), it does not generate and transmit a response command. In addition, the conventional OBEX layer that generates and transmits a response command corresponding to the received request command may be called instead of sending the response command from the OBEX layer to the client device by the lower layer. the

By realizing the above-mentioned communication between the client device (mobile phone A) on the sending side and the server device (recording device B) on the receiving side, even in one-way communication, object exchange protocols such as OBEX can be used to transfer video data, for example . the

Other embodiments of the present invention will be described as follows based on FIGS. 37 to 59 . In addition, the communication protocol described in this embodiment is applicable to the first to fourteenth embodiments. Therefore, in this embodiment, it is assumed that the terms defined in the first to fourteenth embodiments are used according to their definitions unless otherwise specified. the

(1) Communication layer

FIG. 37 is a schematic diagram showing the correspondence relationship between the OSI7 layer model, the layer of IrDA, and the layer of the communication system of the present invention. the

Each communication layer of the communication system according to this embodiment also has functions equivalent to the corresponding layers of the above-mentioned OSI 7-layer model. However, as shown in FIG. 37, the communication system described above has a six-layer structure in which the session layer and the display layer are one layer. the

In this embodiment, for convenience of description, description will be made based on IrSimple which is an application example of the present invention. However, the present invention is not limited to IrSimple. In addition, IrSimple is an improvement of some functions of the conventional IrDA. the

In this embodiment, according to IrSimple, the data link layer, network layer, transport layer, and session layer+display layer may be expressed as LAP, LAMP, SMP, and OBEX, respectively. Also, when distinguishing communication layers by a transmitter and a receiver, "P" is added to the transmitter (primary station), and "S" is added to the receiver (secondary station). For example, "LAP(P)" means the data link layer of the sender. the

(2) Sequence between transmitter and receiver

(2-1) Connection sequence

Responsive

FIG. 38( a ) is a sequence diagram showing the connection sequence (response) in this embodiment. On the other hand, FIG. 38(c) is an explanatory diagram showing the data structure of the communication data in the connection procedure of the present embodiment (response). the

In this embodiment (response), by using the global address in the SNRM Destination Device Address, the SNRM command can have the same function as the search (SNRM command in FIG. 38(c)). the

In addition, in this embodiment (responsive), SNRM commands and UA responses, which are connection packets of the data link layer, insert information necessary for connection with higher layers such as the network layer, transport layer, session layer, and display layer. parameters and commands. As a result, connection packets for connecting each higher layer, which are necessary in conventional IrDA, can be aggregated into one packet. the

Therefore, it is possible to perform a search and a connection sequence that conventionally required a plurality of packets with one packet pair. the

No response

Fig. 38(b) is a sequence diagram showing the connection sequence in this embodiment (no response). On the other hand, FIG. 38(c) is an explanatory diagram showing the data structure of the communication data in the connection procedure of the present embodiment (no response). In addition, in this embodiment (no response), no UA response (UA response for SNRM in FIG. 38(c)) is required. the

Depending on the user, application, and data type, a communication method that omits a response from the receiver can be selected. In this case, as shown in FIG. 38(b), the search and connection can be terminated only with the SNRM command. the

In this way, the connection sequence of this embodiment shortens the time required for connection by collecting connection requests from a plurality of communication layers, so that reconnection can be easily performed even if the communication line is disconnected. Therefore, it is particularly suitable for wireless communication such as infrared rays where the communication line is easily disconnected. However, it is also effective in other wireless communication and wired communication including IEEE802.11 wireless and Bluetooth. the

In addition, in this embodiment, an example in which all communication layers are connected by one communication has been described, but the present invention is not limited thereto. For example, after one communication layer is connected, the remaining multiple communication layers may be connected. In addition, the connection of one communication layer can also be performed by multiple times of communication. For example, when the connection at the network layer requires two communications, the connection at the data link layer and the first connection at the network layer are combined into one connection request, and the second connection at the network layer and the connection at the transport layer are combined Just for one connection request. the

(2-2) Data exchange sequence

Responsive

Fig. 39(a) and Fig. 39(b) are sequence diagrams showing the data exchange procedure in this embodiment (response). On the other hand, FIG. 39( a ) is an explanatory diagram showing the data structure of communication data in the data exchange procedure of the present embodiment (response). the

In this embodiment (responsive), try to reduce the low-level and high-level response between each data, and send back whether there is an error or no error after sending multiple data. the

In data communication, the transmitter uses a packet constructed from a packet number for order inquiry, a flag indicating that there is no problem in received data, and divided data obtained by dividing the data according to the size of the packet. the

As shown in FIG. 39(a), the transmitter transmits the packet with the above flag after transmitting a predetermined number of packets. In contrast, the receiver notifies the transmitter of normal reception when no error is detected from the beginning of receiving previous data or from receiving and returning a packet with the above-mentioned flag. In addition, when the receiver detects an error from the beginning of receiving previous data, or from receiving and returning a packet with the above-mentioned flag, it ignores the above-mentioned divided data part after the unreceivable packet, and only confirms the above-mentioned flag. , and when the above-mentioned flag is set, the sender is notified of the packet number that cannot be received due to an error. the

Then, when the transmitter accepts that the receiver has received normally, it transmits from the next packet. On the other hand, when the sender receives the notification that there is an error, it retransmits from the unreceivable packet number up to the packet with the above-mentioned flag. the

As a result, the interval between packets can be shortened, and efficient communication can be performed. the

As shown in FIG. 39( a ), in this embodiment (responsive), a UI frame is used ( FIG. 40( b )). Therefore, omission of packets cannot be identified at the data link layer (LAP layer), and detection is performed at the transport layer. the

The data portion of the transport layer of the UI frame is provided with a sequence number, a data confirmation flag, a flag indicating whether it is the last packet of data, and a flag indicating whether the received data is normal, and data is transmitted using these flags. the

No response

Fig. 41(a) and Fig. 41(b) are sequence diagrams showing the data exchange procedure in this embodiment (no response). On the other hand, FIG. 41(b) is an explanatory diagram showing the data structure of communication data in the data exchange procedure of the present embodiment (no response). the

In this embodiment (no response), only the integrity of data is confirmed when no response from the receiver is required. Therefore, the transmitter assigns sequence numbers to the packets, and transmits all the data consecutively. the

Then, only when the receiver checks whether there is an error or not, if the receiver receives all the data normally, it confirms the normal reception in the receiver and proceeds to the next operation. The next action in this case is to display, print, or save the received data, for example. On the other hand, when an error is detected, it is confirmed in the receiver that reception cannot be performed normally, and the next operation is performed. The next action in this case is to let the user know that a reception failure instruction has occurred, or to change to the next reception waiting state. the

In addition, even in this embodiment (no response), the UI frame shown in Fig. 41(b) is used (Fig. 40(b)). the

(2-3) Disconnect sequence

Responsive

Fig. 42(a) is a sequence diagram showing the disconnection sequence of the present embodiment (response). On the other hand, FIG. 42(c) is an explanatory diagram showing the data structure of the communication data in the disconnection sequence of the present embodiment (response). the

As shown in FIG. 42(c), in this embodiment (responsive), the parameters and commands required for disconnection of high layers such as the network layer, the transport layer, the session layer, and the display layer are inserted into the DISC command and the UA In response. the

As a result, it is possible to perform a disconnection sequence that conventionally required a plurality of packets with one packet pair. the

No response

FIG. 42( b ) is a sequence diagram showing the disconnection sequence in this embodiment (no response). On the other hand, FIG. 42(c) is an explanatory diagram showing the data structure of the communication data in the disconnection sequence of the present embodiment (response). In addition, in this embodiment (no response), the UA response (UAresponse in FIG. 42(c)) is not required. the

As shown in FIG. 42( b ), in the present embodiment (no response), when connecting without requiring a response from the receiver, the search and disconnection can be terminated only with the DIS command. the

(3) The sequence in the transmitter and receiver

In Fig. 43 to Fig. 59, for the convenience of explanation, the data link layer is marked as LAP, the network layer is marked as LAMP, the transport layer is marked as TTP or SMP, and the session layer and display layer are marked as OBEX. In addition, in order to distinguish the communication layers between the transmitter and the receiver, "P" is added to the transmitter and "S" is added to the receiver. For example, "LAP(P)" means the data link layer of the sender. the

(3-1) Connection sequence

Responsive

FIG. 43 is a sequence diagram showing the connection procedure in this embodiment (response). 44( a ) and FIG. 44( b ) are explanatory diagrams showing the data structure of communication data in the connection procedure of the present embodiment (response). the

As shown in FIG. 43, in this embodiment (response), both the transmitter and receiver prepare for connection. Then, when the sender transfers the request from the upper layer to the lower layer as it is, it transmits it as one packet (SNRM). On the other hand, the receiver receives the SNRM packet, notifies the upper layer that the connection can be made without change, and then transmits the OBEX(S) response as it is to the lower layer, and sends it as one packet (UA). The sender terminates the connection after accepting the UA, and notifies the upper layer (Connect.confirm). the

The sequence in the transmitter and receiver at this time is as follows. the

First, each communication layer related to the transmitter will be described. the

When OBEX(P) receives a connection request from an application, it quickly adds a connection request command to the data to the lower layer (SMP(P)) and generates a connection request function (Primitive). On the other hand, when the OBEX (P) receives the connection confirmation function from the SMP (P), it confirms the response of the OBEX connection from the data, and if there is no problem (Success) response, the connection is completed. the

SMP(P) accepts the connection request function from OBEX(P), and quickly adds the parameters necessary for the SMP(P) communication with the receiver to the data of the connection request function of OBEX(P), so that the lower layer (LMP) (P)) generates a connection request function. On the other hand, when the SMP(P) receives the connection confirmation function from the LMP(P), it extracts the parameters generated by the SMP(P) of the receiver from the data of the function, confirms its value, and ends the negotiation with the SMP(S) . In addition, SMP(P) transmits the data obtained by excluding the parameter of SMP(S) from the data of the connection confirmation function as the connection confirmation function to OBEX(P). the

The LMP(P) accepts the connection request function from the SMP(P), and quickly adds the parameters required for the LMP(S) communication with the receiver to the data of the connection request function of the SMP(P), thereby to the lower layer (LMP( P)) generates a connection request function. On the other hand, when the LMP(P) receives the connection confirmation function from the LAP(P), it extracts the parameter generated by the LMP(S) of the receiver from the data of the function, confirms its value, and ends the negotiation with the LMP(S) . In addition, LMP(P) transmits the data obtained by excluding the parameter of LMP(S) from the data of the connection confirmation function as the connection confirmation function to SMP(P). the

Furthermore, LSAP (Link Service Access Point) is usually defined for managing logical ports. Therefore, in the case of making one connection in a one-to-one manner, there is no need to use LMP. In this case, use the connectionless value as a fixed value in LSAP. Therefore, no connection parameter exchange of LMP is required. the

The LAP(P) accepts the connection request function from the LMP(P), and quickly adds the parameters required for the LAP(S) communication with the receiver to the data of the connection request function of the LMP(P), so that the receiver's physical The layer outputs SNRM commands. On the other hand, when the LAP(P) receives the UA response from the receiver's physical layer, it extracts the parameters generated by the receiver's LAP(S) from the data of the UA response, confirms its value, and ends the communication with the LAP(S) negotiate. In addition, LAP(P) transmits the data except the parameters of LAP(S) from the UA response data as the connection confirmation function to LMP(P). the

Next, each communication layer related to the receiver will be described. the

OBEX(S) accepts the connection request function from the application, and becomes the reception standby state. Also, when OBEX(S) receives the connection notification function (Indication) from the lower layer (SMP(S)), confirm the OBEX connection command from the data, and if there is no problem, a response such as Success is used as the connection response function (Response) output to SMP(S), and complete the connection. the

SMP(S) accepts the connection request function from OBEX(S) and enters the reception standby state. On the other hand, when the SMP(S) receives the connection notification function from the lower layer (SMP(S)), the parameters generated by the SMP(P) of the transmitter are extracted from the data of the function, and the parameters of responses to these parameters are generated, and After sending the connection request function to OBEX(S) which added the data except the parameter of SMP(P) from the data of the above function, it waits for the connection response function from OBEX(S). And when SMP(S) accepts the connection response function from OBEX(S), add the parameters of the above response to the data of the connection response function of OBEX(S) to LMP(S), so that LMP(S) ) A connection response function occurs and the negotiation of the SMP layer ends. the

The LMP(S) receives a connection request function from the SMP(S), and enters a reception standby state. On the other hand, when the LMP(S) has received the connection notification function from the lower layer (LMP(S)), parameters generated by the LMP(P) of the transmitter are extracted from the data of the function, parameters of a response to these parameters are generated, and After sending to SMP(S) the connection request function adding the data except the parameter of LMP(P) from the data of the above function, it waits for the connection response function from SMP(S). On the other hand, when LMP(S) accepts the connection response function from SMP(S), the parameters of the above-mentioned response are added to the data of the connection response function of SMP(S) to LAP(S), thereby to LAP(S) ) A connection response function occurs, and the LMP layer agreement ends

Furthermore, LSAP (Link Service Access Point) is usually defined for managing logical ports. Therefore, in the case of making one connection in a one-to-one manner, there is no need to use LMP. In this case, use the connectionless value as a fixed value in LSAP. Therefore, no connection parameter exchange of LMP is required. the

The LAP(S) receives a connection request function from the LMP(S), and enters a reception standby state. On the other hand, when the LAP(S) receives the SNRM command from the physical layer, the parameters generated by the receiver LAP(P) are extracted from the data of the SNRM command, and the parameters added to the data of the SNRM command sent to the LMP(S) are removed. After receiving the connection request function of the data of the parameters of the LAP(P), generate the parameters of the response to the function, and wait for the connection response function from the LMP(S). On the other hand, when the LAP(S) receives the connection response function from the LMP(S), the parameters of the above response are added to the data of the connection response function of the LMP(S), the UA response is output to the physical layer, and the LAP layer is terminated. negotiation. the

No response

FIG. 45 is a sequence diagram showing the connection procedure in this embodiment (no response). On the other hand, FIG. 44(a) is an explanatory diagram showing the data structure of the communication data in the connection procedure of the present embodiment (no response). the

As shown in FIG. 45, in this embodiment (no response), both the transmitter and the receiver prepare for connection. Then, when the sender transfers the request from the upper layer to the lower layer as it is, it transmits it as one packet (SNRM). Then, the transmitter completes the connection when the SNRM packet is transmitted, and notifies (Connect.confirm) from the LAP (P) to the upper layer. On the other hand, the receiver receives the SNRM packet, notifies the upper layer that the connection can be made as it is, and completes the connection when it notifies the OBEX(S). the

The sequence in the transmitter and receiver at this time is as follows. the

First, each communication layer related to the transmitter will be described. the

When OBEX(P) receives a connection request from an application, it quickly adds a connection request command to the data to the lower layer (SMP(P)) and generates a connection request function (Primitive). On the other hand, when the OBEX(P) receives the connection confirmation function from the SMP(P), the connection is completed. the

SMP(P) accepts the connection request function from OBEX(P), and quickly adds the parameters necessary for the SMP(P) communication with the receiver to the data of the connection request function of OBEX(P), so that the lower layer (LMP) (P)) generates a connection request function. On the other hand, when the SMP(P) receives the connection confirmation function from the LMP(P), it assumes that the negotiation is performed using the transmitted parameters, and the negotiation at the SMP layer ends. Also, at this time, SMP(P) sends a connection confirmation function to OBEX(P). the

The LMP(P) accepts the connection request function from the SMP(P), and quickly adds the parameters required for the LMP(S) communication with the receiver to the data of the connection request function of the SMP(P), thereby to the lower layer (LMP( P)) generates a connection request function. On the other hand, when the LMP(P) receives the connection confirmation function from the LAP(P), it assumes that the negotiation is performed using the transmitted parameters, and the negotiation at the LMP layer ends. Also, at this time, the LMP(P) sends a connection confirmation function to the SMP(P). the

Furthermore, LSAP (Link Service Access Point) is usually defined for managing logical ports. Therefore, in the case of making one connection in a one-to-one manner, there is no need to use LMP. In this case, use the connectionless value as a fixed value in LSAP. Therefore, no connection parameter exchange of LMP is required. the

The LAP(P) accepts the connection request function from the LMP(P), and quickly adds the parameters required for the LAP(S) communication with the receiver to the data of the connection request function of the LMP(P), so that the receiver's physical The layer outputs SNRM commands. On the other hand, when the LAP(P) outputs the SNRM command, it is assumed that negotiation is performed using the transmitted parameters, and the negotiation at the LAP layer ends. Also, at this time, the LAP(P) sends a connection confirmation function to the LMP(P). the

Next, each communication layer related to the receiver will be described. the

OBEX(S) accepts the connection request function from the application, and becomes the reception standby state. Also, when the OBEX(S) receives the connection notification function (Indication) from the lower layer (SMP(S)), it confirms the OBEX connection command from the data, and completes the connection if there is no problem. the

SMP(S) accepts the connection request function from OBEX(S) and enters the reception standby state. On the other hand, when the SMP(S) receives the connection notification function from the lower layer (SMP(S)), it extracts the parameter generated by the SMP(P) of the transmitter from the data of the function, and completes the negotiation using the parameter. Then, the SMP(S) transmits to the OBEX(S) a connection request function in which the data of the SMP(P) is removed from the data of the above function. the

The LMP(S) receives a connection request function from the SMP(S), and enters a reception standby state. On the other hand, when the LMP(S) receives the connection notification function from the lower layer (LMP(S)), it extracts a parameter generated by the LMP(P) of the transmitter from the data of the function, and completes the negotiation using the parameter. Then, the LMP(S) transmits to the SMP(S) a connection request function in which the data of the LMP(P) is removed from the data of the above function. the

Furthermore, LSAP (Link Service Access Point) is usually defined for managing logical ports. Therefore, in the case of making one connection in a one-to-one manner, there is no need to use LMP. In this case, use the connectionless value as a fixed value in LSAP. Therefore, no connection parameter exchange of LMP is required. the

The LAP(S) receives a connection request function from the LMP(S), and enters a reception standby state. On the other hand, when the LAP(S) receives the SNRM command from the physical layer, it extracts the parameters generated by the LAP(P) from the data of the SNRM command, and completes the negotiation using the parameters. Then, the LAP(S) transmits to the LMP(P) a connection request function in which the data of the LAP(P) is removed from the data of the above function. the

(3-2) Data exchange sequence

Responsive

FIG. 46 is a sequence diagram showing the data exchange procedure in this embodiment (response). On the other hand, FIG. 47 is an explanatory diagram showing the data structure of communication data in the data exchange procedure of the present embodiment (response). the

As shown in FIG. 46, in this embodiment (response), the transmitter generates a PUT command, and the command is transmitted to the lower layer and output as a UI frame (FIG. 40(b)). the

On the other hand, the receiver receives the data and notifies the upper layer. At this time, the SMP(S) notifies the OBEX(S) of the upper layer of data continuation (status=truncated). the

After sending a certain number of packets, the sender sets the flag to confirm whether the data has just arrived to ON and sends it. Accepting this flag, the receiver checks whether there is an error in the SMP(S), and if there is an error, notifies the transmitter of the number where the error occurred. the

If there is no error, the transmitter outputs the next group of packets, and if there is an error, the transmitter retransmits the packets subsequent to the errored packet. the

When it is the last data, the transmitter turns ON a flag indicating that it is the last data, and transmits it. On the other hand, if this flag is ON, the receiver, that is, the SMP(S), notifies the OBEX(S) that the data is ready (status=OK), and waits for a response from the OBEX(S). Then, when an OBEX(S) response is generated, the data is transferred to the lower layer and output as a UI frame. the

If the accepted response is Success, the sender ends normally. the

The sequence in the transmitter and receiver at this time is as follows. the

At the sender, OBEX(P) outputs the PUT command to the lower layer as a data send function. However, when OBEX(P) does not need a response to a PUT command other than the PUT Final (last PUT) command (normally, Continue returns) and can be sent with SMP(P), it continues to output subsequent commands. In the case of a PUT Final command or a command other than the PUT command, wait for the data notification function from the lower layer, observe the response in the data, and end the command. the

Here, the data sending function is a function (Data Request) that requests data sending to the lower layer. The data notification function is a function that notifies that data has been received from the lower layer (Data Indicate). the

In the receiver, OBEX(S) accepts the data notification function from the lower layer, and accepts the data. However, OBEX(S) does not return a response to a PUT command other than a PUT Final command, and returns a response as a data sending function in the case of a PUT Final command or a command other than a PUT command. the

Here, the headers in the upper and lower layer data transmission functions and data notification functions common to the transmitter and receiver will be described. the

When SMP receives the data sending function from OBEX, for LMP, (a) when the amount (size) that can be sent by LMP is smaller than the amount of data in the data sending function, divide the data into the amount that can be sent by LMP, (b) in When the amount that can be sent by LMP is larger than the amount of data in the data sending function, several pieces of data are combined to generate larger data that is less than the amount that can be sent. In addition, SMP generates an SMP header, and the SMP header adds a sequence number, an argument to inquire about the status of receiving data from the other device, an argument indicating the last data, an argument indicating that the SMP of the other party needs an OBEX response, and an argument indicating Argument whether the received data is normal or not, etc. Then, a data-added data transmission function that adds the SMP header to the above-mentioned divided or combined data is transmitted to the LMP. the

And, when the SMP receives the data notification function from the LMP, it extracts the SMP header from the data in the function, and checks whether the sequence number is normal (that is, whether it arrives in an order not missing). Then, under normal circumstances, send data notification function to OBEX. At this time, the data notification function may output for each data notification function from the lower layer, or may output together with data from several data notification functions of the lower layer. the

The SMP(P) of the transmitter converts the data transmission function from the OBEX(P) into a data transmission function to the LMP(P), and transmits a data transmission function of a certain predetermined amount of data. Then, SMP(P) sets the argument of inquiring about the data receiving status to the receiver as True, transmits the data sending function, and waits for the data notification function of LMP(P). the

SMP(P) analyzes the SMP header in the data notification function from LMP(S), and when the argument indicating whether the received data is normal is received normally, preparations for sending the subsequent data are made , and it becomes possible to send to OBEX(P). That is, data from OBEX(P) can be accepted in this state. the

On the other hand, when SMP(P) analyzes the SMP header of the received data notification function from LMP(S) and the argument indicating whether the received data is normal is not received normally, the slave notification failure occurs again. The received data sending function is to the data sending function that sets the argument of inquiring about the data receiving status to the partner device as True. SMP(P) repeats for a predetermined number of times, or until all the data generated by the data sending function is notified to the receiver. the

Furthermore, when the SMP(P) receives the data sending function whose last data argument is True from OBEX(P), it makes the data sending function indicate that it is the last data argument or OBEX indicating that a receiver is required. The argument of the response of (S) is True, and the last data added to this data transmission function, the data transmission function to LMP(P), is transmitted. the

Conversely, when the SMP(S) of the receiver receives the data notification function from the LMP(S), if the argument indicating that it is the last data or that a response from the OBEX(S) of the receiver is True, the OBEX (S) A data notification function that transmits data with the SMP(S) header removed. the

Also, when the SMP(S) receives the data notification function from the LMP(S), it analyzes the SMP header from the data in the data notification function, and checks the serial number. If the SMP(S) can normally receive until the header that inquires the receiver of the data reception status argument is True, it means that the argument indicating whether the received data is normal can be received normally, and the SMP is generated The header is used as data, and the data sending function is sent to LMP(S). the

On the other hand, when the SMP(S) detects that it cannot be received normally, it stores the number of the SMP header predicted to be impossible to receive normally. For example, when 0, 1, 2, 3, and 5 are received, and 4 is not received when the fifth one should be 4, the number predicted to be impossible to receive normally is 4. Then, after that, the SMP(S) only checks whether the argument of the receiver inquiry data reception status to the SMP header is True, and stops the output of the data notification function to the OBEX(S). the

When the SMP(S) accepts the data notification function in which the argument for inquiring about the data reception status to the receiver is True, the argument indicating whether the received data is normal is set to indicate that it has not been received normally, and generates a function for inserting into The data transmission function sends the number of the SMP header that cannot be received normally to the SMP header in the sequence number field (field), thereby sending it as data to the LMP(S). the

On the other hand, when SMP(S) accepts an argument indicating that it is the last data, or a data notification function in which an argument indicating that a response from OBEX(S) of the receiver is required is True, the output to OBEX(S) After the data notification function, wait for the data sending request from OBEX(S). the

When SMP(S) accepts a data transmission request from OBEX(S), it generates an SMP header with an argument indicating whether the received data is normal or not, and attaches it to OBEX(S) ) in the data of the data transmission request, so as to transmit the data transmission function to LMP(S). In addition, when there is an error, since the notification to OBEX(S) is stopped, it is regarded as normal while waiting. the

Next, when the LMP receives the data transmission request function from the upper layer, the LMP header is added to the data in the function to generate data, and the data transmission request function with the data added is transmitted to the LAP. Also, when the LMP receives the data notification function from the LAP, it generates data in which the LMP header is removed from the data in the function, and transmits the data notification function in which the data is added to the SMP. the

Also, in the case of making one connection in a one-to-one manner, it is not necessary to use LMP. In this case, the LSAP to which the connectionless value is added is added to the LMP header. the

When the LAP receives the data transmission request function from the LMP, it adds a LAP header to the data in the function to generate data, and transmits a UI frame including the data to the physical layer. Also, when the LAP receives the notification of data reception from the physical layer, it generates data with the LAP header removed from the data of the UI frame, and transmits the data notification function adding the data to the LMP. Furthermore, in this embodiment, the LAP header includes a connection address and a UI indicator. the

No response

FIG. 48 is a sequence diagram showing the data exchange procedure in this embodiment (no response). On the other hand, FIG. 47 is an explanatory diagram showing the data structure of communication data in the data exchange procedure of the present embodiment (no response). the

As shown in FIG. 48, in this embodiment (no response), the transmitter generates a PUT command, which is passed to the lower layer and output as a UI frame. the

On the other hand, the receiver receives the data and notifies the upper layer. At this time, the SMP(S) notifies the OBEX(S) of the upper layer of data continuation (status=truncated). the

Then, when it becomes the last data, the transmitter turns ON a flag indicating that it is the last data, and transmits it. On the other hand, if this flag is ON, the receiver, that is, the SMP(S), notifies the OBEX(S) that the data is ready (status=OK), and the data exchange procedure ends. the

The sequence in the transmitter and receiver at this time is as follows. the

In the transmitter, OBEX (P) outputs the PUT command to the lower layer as a data transmission function. However, OBEX(P) may end commands without responding to all commands. Then, OBEX(P) continues to output the following commands under the condition that SMP(P) can be sent. the

In the receiver, OBEX(S) accepts a data notification function from a lower layer, and accepts only data without returning a response to all commands. the

Here, the headers in the upper and lower layer data transmission functions and data notification functions common to the transmitter and receiver will be described. the

When SMP receives the data sending function from OBEX, for LMP, (a) when the amount (size) that can be sent by LMP is smaller than the amount of data in the data sending function, divide the data into the amount that can be sent by LMP, (b) in When the amount that can be sent by LMP is larger than the amount of data in the data sending function, several pieces of data are combined to generate larger data that is less than the amount that can be sent. In addition, SMP generates an SMP header, and the SMP header adds a sequence number, an argument to inquire about the status of receiving data from the other device, an argument indicating the last data, an argument indicating that the SMP of the other party needs an OBEX response, and an argument indicating Argument whether the received data is normal or not, etc. Then, a data-added data transmission function that adds the SMP header to the above-mentioned divided or combined data is transmitted to the LMP. the

And, when the SMP receives the data notification function from the LMP, it extracts the SMP header from the data in the function, and confirms whether the sequence number is normal (that is, whether it arrives in an unextracted order). Then, under normal circumstances, send data notification function to OBEX. At this time, the data notification function may output for each data notification function from the lower layer, or may output together with data from several data notification functions of the lower layer. the

The SMP(P) of the transmitter converts the data transmission function from the OBEX(P) into the data transmission function to the LMP(P). Then, when the data transmission function whose argument formed when the last data is False is received from OBEX(P), the data with the SMP header added to the data is transmitted to LMP(P). On the other hand, when SMP(P) has received from OBEX(P) the data sending function whose argument as the last data is True, it sets the argument indicating that the data sending function is the last data, or indicates that the receiver is required. The argument of the response of OBEX(S) is True, and the last data added to this data sending function, the data sending function to LMP(P) is sent. the

On the other hand, when the SMP(S) of the receiver receives the data notification function from the lower layer, it analyzes the SMP header from the data in the data notification function, and checks the sequence number. Then, when the SMP(S) analyzes the SMP header and confirms that it can be received normally, it transmits the data transmission function to the LMP(S). the

Conversely, when SMP(S) detects that it cannot receive normally, it notifies OBEX(S) of an error. For example, when 0, 1, 2, 3, and 5 are received, since the fifth should be 4, it is the case that 4 is not accepted. the

Therefore, after that, the SMP (S) waits for the argument indicating the last data of the SMP header or the argument indicating that the response of the OBEX (S) of the receiver is required to be True, and accepts the data notification function as True (again Yes, do not send notification to OBEX(S) even if accepted), or accept disconnection notification function, or do not perform data notification to OBEX(S) until a certain period of time passes. the

Next, when the LMP(P) of the transmitter receives the data transmission request function from the SMP(S), it adds the LMP header to the data in the function to generate data, and transmits the data with the data added to the LAP(P) Send request function. the

On the other hand, when the LMP(S) of the receiver receives the data notification function from the LAP(S), it generates data with the LMP header removed from the data in the function, and adds the The data notification function for this data. the

Also, in the case of making one connection in a one-to-one manner, it is not necessary to use LMP. In this case, the LSAP to which the connectionless value is added is added to the LMP header. the

When the LAP(P) of the transmitter receives the data transmission request function from the LMP(P), it adds a LAP header to the data in the function to form data, and transmits a UI frame incorporating the data to the physical layer. the

On the other hand, when the LAP(S) of the receiver receives the notification of data reception from the physical layer, it generates data with the LAP header removed from the data of the UI frame, and adds the data to the LMP(S) transmission. The data notification function. Furthermore, in this embodiment, the LAP header includes a connection address and a UI indicator. the

(3-3) Disconnect sequence

Responsive

FIG. 49 is a sequence diagram showing the disconnection procedure of the present embodiment (response). 50( a ) and FIG. 50( b ) are explanatory diagrams showing the data structure of the communication data at the time of the disconnection procedure of the present embodiment (response). the

As shown in FIG. 49, in the present embodiment (response), a DISC command is generated when a disconnect command from the transmitter is transmitted to the lower layer. When the receiver accepts the DISC command and notifies the upper layer, it returns its response and generates a UA response. Then, it is terminated after notifying the reception of the UA response up to the upper layer of the transmitter. the

The sequence in the transmitter and receiver at this time is as follows. the

First, each communication layer related to the transmitter will be described. the

When OBEX(P) receives a disconnection request from an application, it quickly adds a disconnection request command to the data to the lower layer (SMP(P)) and generates a disconnection request function (Primitive). On the other hand, when the OBEX (P) has received the disconnection confirmation function from the SMP (P), the response to confirm the disconnection of the OBEX is confirmed from the data, and if there is no problem (Success) response, the disconnection is assumed to be completed. the

SMP(P) accepts the disconnection request function from OBEX(P), and quickly adds the parameters necessary for SMP(P) communication with the receiver to the data of the disconnection request function of OBEX(P), so that the lower layer (LMP(P)) generates a disconnection request function. On the other hand, when the SMP(P) receives the disconnection confirmation function from the LMP(P), it extracts the parameter generated by the SMP(S) of the receiver from the data of the function, confirms its value, and ends the communication with the SMP(S) Disconnect processing. In addition, SMP(P) transmits, as a disconnection confirmation function to OBEX(P), data obtained by excluding the parameter of SMP(S) from the data of the disconnection confirmation function. However, there are usually no parameters newly added by the SMP(P) at the time of disconnection. the

The LMP(P) accepts the disconnection request function from the SMP(P), and quickly adds the parameters required for the LMP(S) communication with the receiver to the data of the disconnection request function of the SMP(P), thereby to the lower layer ( LMP(P)) generates a disconnection request function. On the other hand, when the LMP(P) receives the disconnect confirmation function from the LAP(P), it extracts the parameter generated by the receiver's LMP(S) from the data of the function, confirms its value, and ends the communication with the LMP(S) Disconnect processing. In addition, LMP(P) transmits, as a disconnection confirmation function to SMP(P), data obtained by excluding the parameter of LMP(S) from the data of the disconnection confirmation function. However, there are usually no parameters newly added by LMP(P) at the time of disconnection. the

The LAP(P) accepts the disconnection request function from the LMP(P), and quickly adds the parameters required for the LAP(S) communication with the receiver to the data of the disconnection request function of the LMP(P), thereby to the receiver The physical layer outputs DISC commands. On the other hand, when the LAP(P) receives the UA response from the receiver's physical layer, it extracts the parameters generated by the receiver's LAP(S) from the data of the UA response, confirms its value, and ends the communication with the LAP(S) connect. Also, the LAP(P) transmits the data obtained by excluding the parameters of the LAP(S) from the UA response data as a disconnect confirmation function to the LMP(P). However, there are usually no parameters newly added by the LAP(P) at the time of disconnection. the

Next, each communication layer related to the receiver will be described. the

When the OBEX(S) receives the disconnection request function (Indication) from the lower layer (SMP(S)), confirm the OBEX disconnection command from the data, and if there is no problem, a response such as Success is regarded as a disconnection response The function (Response) is output to the SMP(S), and it is assumed that the disconnection is complete. the

In the case where the SMP(S) has received the disconnection notification function from the lower layer (SMP(S)), the parameters generated by the SMP(P) of the transmitter are extracted from the data of the function, the parameters of the response to these parameters are generated, and After sending to OBEX(S) the disconnection request function adding the data except the parameter of SMP(P) from the data of the above function, it waits for the disconnection response function from OBEX(S). And in the case that SMP(S) has accepted the disconnection response function from OBEX(S), the parameter of the above-mentioned response is added to the data of the disconnection response function of OBEX(S) to LMP(S), thereby to LMP (S) A disconnection response function occurs, and the disconnection processing of the SMP layer ends. However, there are usually no parameters newly added by the SMP(S) at the time of disconnection. the

When the LMP(S) receives the disconnection request function from the lower layer (LAP(S)), it extracts the parameter generated by the LMP(P) of the transmitter from the data of the function, and generates a parameter of a response to the parameter, And after sending to SMP(S) the disconnection request function which added the data except the parameter of LMP(P) from the data of the above function, it waits for the disconnection response function from SMP(S). And under the situation that LMP (S) has accepted the disconnection response function from SMP (S), add the parameter of above-mentioned response in the data of SMP (S) to the disconnection response function of LAP (S), thereby to LAP ( S) A disconnection response function occurs, and the disconnection processing of the LMP layer ends. However, there are usually no parameters newly added by the LMP(S) at the time of disconnection. the

When the LAP(S) receives the DISC command from the physical layer, it extracts the parameters generated by the LAP(P) of the transmitter from the data of the DISC command, and removes it from the data sent by the DISC command to the LMP(S). After receiving the disconnection request function of the parameter data of the LAP(P), generate the parameter of the response to it, and wait for the disconnection response function from the LMP(S). Also, when the LAP(S) has received the disconnection response function from the LMP(S), it adds the parameter of the above response to the data of the disconnection response function of the LMP(S), outputs a UA response to the physical layer, and ends Disconnect handling at the LAP layer. However, there are usually no parameters newly added by the LAP(S) at the time of disconnection. the

No response

FIG. 51 is a sequence diagram showing the disconnection procedure of the present embodiment (no response). On the other hand, FIG. 50( a ) is an explanatory diagram showing the data structure of the communication data in the disconnection procedure of the present embodiment (no response). the

As shown in FIG. 51, in this embodiment (no response), a DISC command is generated when a disconnect command from the transmitter is transmitted to the lower layer. At the transmitter, the disconnection process ends at this point. On the other hand, when the receiver receives the DISC command and transmits it to the higher layer, it terminates the disconnection process at the time when the higher layer is notified. the

The sequence in the transmitter and receiver at this time is as follows. the

First, each communication layer related to the transmitter will be described. the

When OBEX(P) receives a disconnection request from an application, it quickly adds a disconnection request command to the data to the lower layer (SMP(P)) and generates a disconnection request function (Primitive). On the other hand, when the OBEX(P) has received the disconnection confirmation function from the SMP(P), it is assumed that the disconnection is completed. the

SMP(P) accepts the disconnection request function from OBEX(P), and quickly adds the parameters necessary for SMP(P) communication with the receiver to the data of the disconnection request function of OBEX(P), so that the lower layer (LMP(P)) generates a disconnection request function. On the other hand, when the SMP(P) receives the disconnect confirmation function from the LMP(P), disconnection is performed using the transmitted parameters, and the disconnection processing of the SMP layer ends. Also, SMP(P) sends a disconnect confirmation function to OBEX(P). However, there are usually no parameters newly added by the SMP(P) at the time of disconnection. the

The LMP(P) accepts the disconnection request function from the SMP(P), and quickly adds the parameters required for the LMP(S) communication with the receiver to the data of the disconnection request function of the SMP(P), thereby to the lower layer ( LMP(P)) generates a disconnection request function. When the LMP (P) receives the disconnect confirmation function from the LAP (P), it is assumed that the disconnection is performed with the parameters sent, thereby ending the disconnection process of the LMP layer. Also, the LMP(P) sends a disconnect confirmation function to the SMP(P). However, there are usually no parameters newly added by LMP(P) at the time of disconnection. the

The LAP(P) accepts the disconnection request function from the LMP(P), and quickly adds the parameters required for the LAP(S) communication with the receiver to the data of the disconnection request function of the LMP(P), thereby to the receiver The physical layer outputs DISC commands. On the other hand, when the LAP(P) outputs the DISC command, it is assumed that the disconnection is performed using the transmitted parameters, and the disconnection processing of the LMP layer ends. In addition, the LAP(P) sends a disconnect confirmation function to the LMP(P). However, there are usually no parameters newly added by the LAP(P) at the time of disconnection. the

Next, each communication layer related to the receiver will be described. the

When the OBEX (S) receives the disconnection notification function (Indication) from the lower layer (SMP(S)), it confirms the OBEX disconnection command from the data, and if there is no problem, it is assumed that the disconnection is completed. the

When the SMP(S) receives the disconnection notification function from the lower layer (SMP(S)), it extracts a parameter generated by the SMP(P) of the transmitter from the data of the function, and completes disconnection using the parameter. In addition, SMP(S) transmits to OBEX(S) a disconnection request function in which data of SMP(P) parameters are removed from the data of the above function. However, there are usually no parameters newly added by the SMP(S) at the time of disconnection. the

When the LMP(S) receives the disconnection notification function from the lower layer (LAP(S)), it extracts a parameter generated by the LMP(P) of the transmitter from the data of the function, and completes disconnection using the parameter. Also, the LMP(S) transmits to the SMP(S) a disconnection request function in which the data of the LMP(P) is removed from the data of the above function. However, there are usually no parameters newly added by the LMP(S) at the time of disconnection. the

When the LAP(S) receives the DISC command from the physical layer, it extracts a parameter generated by the LAP(P) of the transmitter from the data of the DISC command, and completes disconnection using the parameter. In addition, the LAP(S) transmits to the LMP(S) a disconnection request function in which the data of the DISC command except the parameter of the LAP(P) is added. However, there are usually no parameters newly added by the LAP(S) at the time of disconnection. the

(4) Switching with or without response

Next, the flow of data and parameters between the communication layers of the transmitter and receiver will be described with reference to FIGS. 52 to 59 . the

In this embodiment, each communication layer LAP, LMP, SMP, and OBEX of the transmitter and receiver has a connection request function, a connection notification function, a connection response function, and a connection confirmation function. These functions are functions for accessing from a higher layer (i.e., LMP layer) to the LAP layer. the

Furthermore, the above function may specify Data (hereinafter, referred to as data) and Requested-Qos or Returned-QoS as arguments. As described above, the above data is set in each communication layer. the

On the other hand, Qos notifies the upper layers including OBEX of the designation of negotiation parameters such as the baud rate determined by the LAP and the result of the negotiation. Furthermore, Qos can be used even with the conventional IrDA. the

For example, when the application or OBEX(P) of the transmitter transmits QoS to which a parameter such as response required/non-required is added, it is sequentially transmitted to the lower layer up to the LAP(P). Then, the LAP(P) reflects the value of this QoS as the value of the negotiation parameter (Ack Less Connect), and transmits it to the receiver. the

As a result, each communication layer of the transmitter and the receiver operates according to the application of the transmitter or the OBEX(P) request/non-response designation, so bidirectional/unidirectional connection is possible. the

52 to 56 are explanatory diagrams showing the flow of data and parameters between communication layers in the connection procedure (FIG. 43) of the present embodiment (response). In addition, the QoS parameters between OBEX-SMP, SMP-LMP, and LMP-LAP may be the same or different. Therefore, in the figure, -a, -b, -c are appended to distinguish. the

In the transmitter, as shown in FIG. 52, the data of Data and QoS-1 (QoS requested by the transmitter) sent to the receiver is transferred from the upper layer to the lower layer by con.req(data) (FIG. 43). the

On the other hand, in the receiver, as shown in FIG. 53, only the data of QoS-2 (QoS requested by the receiver) is transferred from the upper layer to the lower layer respectively by con.req. the

Then, when the LAP(S) receives the SNRM command, the receiver compares the QoS-1 of the transmitter with the QoS-2 of its own, and generates QoS-3 as a parameter negotiated under common use. Then, as shown in FIG. 54, the LAP(S) notifies the upper layer of QoS-3 together with the data from the transmitter according to con.ind(data). Each upper layer stores this QoS-3 and holds it as a connection parameter at the time of connection. the

Next, at the receiver, when notifying con.resp(data), QoS is not required. Therefore, as shown in FIG. 55, only data is transferred from the upper layer to the lower layer in con.resp(data). Then, when the LAP(S) receives con.resp(data), it adds QoS-3 to the UA response and sends the UA response. the

Then, at the sender, the LAP(P) accepts the UA response and stores QoS-3 as a negotiated parameter. Then, as shown in FIG. 56, the LAP(P) notifies the upper layer of the QoS together with the data of the receiver through con.conf(data). Each communication layer holds this QoS-3 as a connection parameter of an established connection. the

In this embodiment, for example, as the QoS of con.req, Requested-Qos: Baud-Rate+Max-Turn-Around-Time+Disconnect-Threshold+DataSize+Ack less connection+Min-Packet-Interval is used. As the QoS of Con.ind and con.conf, use Resultant-QoS: Baud-Rate+Disconnect-Threshold+DataSize+Ack less connection (indication primitive only). the

In addition, in the connection procedure (FIG. 45) of this embodiment (no response), the flow of data and parameters between communication layers is as follows. the

In the transmitter, as shown in FIG. 52, the data of Data and QoS-1 (QoS requested by the transmitter) sent to the receiver is transferred from the upper layer to the lower layer by con.req(data) (FIG. 45). the

Then, the LAP(P) of the transmitter stores QoS-1 as it is as QoS-3. Then, as shown in Figure 56, the LAP(P) notifies the upper layer of QoS-3 through con.conf. Each communication layer holds this QoS-3 as a connection parameter of an established connection. the

On the other hand, in the receiver, as shown in FIG. 53, only the data of QoS-2 (QoS requested by the receiver) is transferred from the upper layer to the lower layer respectively by con.req. the

Then, at the receiver, when the LAP(S) receives the SNRM command, QoS-1 of the transmitter is set to QoS-3. In addition, when the combination of the parameters of QoS-2 and QoS-1 is not satisfied, reception cannot be performed. the

Next, as shown in FIG. 54, the LAP(S) notifies the upper layer of QoS-3 together with the data from the transmitter through con.ind(data). Each upper layer stores this QoS-3 and holds it as a connection parameter at the time of connection. the

In this way, the presence/absence of response can be switched by applying high-level (application) operations on the above-mentioned QoS-1 and QoS-2. the

Here, the file format of the file to be transmitted, the application, the user's selection, and the like can be considered as a criterion for switching between response and non-response. the

Specifically, in the case of a document format, for example, in the case of a multimedia-related file, both the presence/absence of response should be selected, and in the case of checking that data is received as a file such as a phone book, mail, or dispatch , can also be automatically selected to respond. On the other hand, in the case of using the application as a reference, for example, in the case of a slide show, it is sufficient to automatically select no response. In addition, in the case of selection based on the user, for example, it is sufficient for the user to select from a menu display with or without response. the

57 to 59 are explanatory diagrams showing modified examples of the flow of data and parameters between communication layers in the connection sequence of this embodiment. the

In the case where the first SNRM command in the transmitter includes information on all communication layers (FIG. 43), instead of transmitting data or parameters while relaying each communication layer (FIG. 52), it may be configured as follows As shown in Fig. 57, it is directly transferred from each communication layer to the LAP layer. the

Conversely, as shown in FIG. 58, in the receiver, all the data or parameters included in the SNRM command may be taken out and directly transferred from the LAP layer to each communication layer as the destination. the

In addition, as shown in FIG. 59, in the transmitter, the data or parameters of OBEX(P), SMP(P), and LMP(P) can also be configured by LMP(P), and further, LAP(P) The SNRM command is generated by adding the parameter of LAP(P) to the above-mentioned unified data or parameters. the

The present invention is not limited to the above-mentioned embodiments, and various changes can be made within the scope shown in the claims. Embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Inside. the

In addition, examples of the client device and the server device in each of the above-mentioned embodiments include mobile phones, PDAs (Personal Digital Assistants), digital cameras, personal computers, and the like. the

In addition, each block of the client device and the server device in each of the above-described embodiments may be configured by hardware (communication circuit), or may be realized by software using an arithmetic processing device such as a CPU as follows. That is, the above-mentioned client device and server device include: a CPU (central processing unit) that executes commands that describe a communication program for control that can execute various functions by a computer, a ROM (read only memory) that stores the above-mentioned program, and stores the above-mentioned RAM (random access memory) for program development, storage device (recording medium) such as memory for storing the above program and various data, etc. the

Therefore, by supplying the above-mentioned client device and server device with a recording medium in which a program code (executable form program, intermediate code program, source program) of a communication program as software realizing the above-mentioned function is recorded in a computer-readable manner, the computer ( Or CPU or MPU) reads and executes the program code recorded in the recording medium, also can realize the purpose of the present invention. the

As the above-mentioned recording medium, for example, magnetic tapes such as magnetic tapes or cassette tapes, disks including magnetic disks such as floppy (registered trademark) disks/hard disks, or optical disks such as CD-ROM/MO/MD/DVD/CD-R, Cards such as IC cards (including memory cards)/optical cards, or semiconductor memories such as mask ROM/EPROM/EEPROM/flash ROM, etc. the

In addition, the client device and the server device may be configured to be connectable to a communication network, and the above-mentioned program code may be supplied via the communication network. Such a communication network is not particularly limited, and for example, the Internet, intranet, extranet, LAN, ISDN, VAN, CATV communication network, virtual private network (virtual private network), telephone line network, mobile communication network, satellite communication network, etc. Furthermore, the present invention can also be implemented in the form of carrier waves or data signal strings in which the above-mentioned program codes are embodied electronically. the

As above, the communication device of the present invention, as a master station having an object exchange layer, sends out a request command and receives a response command in response to the request command, thereby sending an object to an object exchange layer of a secondary station. In that, the communication device includes: an object exchange layer processing part, which processes the communication protocol of the object exchange layer; and a low layer processing part, which processes a lower layer communication protocol lower than the object exchange layer, and the The part includes: a response generation part that generates a virtual response command that simulates a response command from the secondary station, and notifies the object switching layer processing part; and a low-level control part that controls the response generation part so that When the object exchange layer processing part receives the generation notification of the request command, it generates the virtual response command for responding to the request command, thereby notifying the object exchange layer processing part. the

In addition, the communication method of the present invention is used for a master station having an object exchange layer, and the object exchange layer sends an object to an object exchange layer of a secondary station by issuing a request command and receiving a response command in response to the request command. , it is characterized in that, when the lower layer lower than the object switching layer receives the generation notification of the request command from the object switching layer, it generates a virtual response simulating a response command from the secondary station in response to the request command command, thereby notifying the object exchange layer. the

According to the above structure and method, at the master station (for example, client device), a lower layer than that located at the object exchange layer generates a dummy reply command, thereby notifying the object exchange layer. the

Therefore, without changing the communication protocol for object exchange based on request command/response command, object exchange can be performed with a secondary station (for example, a server device) that does not have a transmission function but has a minimum required reception function. In addition, in order to perform transmission and reception with the above-mentioned secondary station, it is not necessary to change the communication protocol (protocol for object exchange) of the object exchange layer, so existing resources can be used. the

Furthermore, the communication device of the present invention is characterized in that the low-level processing section further includes: a timer that operates when receiving a request command generation notification from the object switching layer processing section to measure the elapsed time, and at the same time, the low-level control and partially controlling the response generating section to generate the dummy response command when the response command from the secondary station has not been received even if the elapsed time of the timer reaches a preset setting value, thereby The object exchange layer processing part is notified. the

According to the above structure, only the response command from the secondary station is waited for a specified time, if the response command is not received from the secondary station, it is judged that the secondary station does not have the function of sending a response command, thereby generating a dummy response command, and notifying the target switching layer . the

Therefore, in the communication with the secondary station with the sending function, object exchange based on the conventional request command/response command can be performed, and in the communication with the secondary station without the sending function, by generating a virtual response command at the lower layer, Object exchange is possible. the

Furthermore, the communication device of the present invention is characterized in that said low-level control section of said low-level processing section performs notification of a response command received from said secondary station according to the type of request command issued by said target switching layer processing section. The object exchange layer processing section, or causes the response generation section to generate a virtual response command and notify the switching of the object exchange layer processing section. the

According to the above configuration, it is also possible to switch between waiting for a response command from the secondary station and generating a dummy response command according to the type of the request command. Therefore, it is possible to receive, for example, the minimum necessary response commands at the time of a connection request, a disconnection request, and a final data transfer request, while omitting the reception of response commands corresponding to data transfer requests other than the final data transfer request. deal with. the

Therefore, by receiving only the minimum necessary response commands from the secondary station, communication processing can be simplified while ensuring reliability of communication. Therefore, the scale of programs and circuits can be reduced. the

Moreover, the communication device of the present invention is characterized in that the low-level processing section further includes: a header information analysis section for analyzing the header information of the request command issued by the object exchange layer processing section, and at the same time, the low-level control section according to The category of the header information analyzed by the header information analysis part is used to notify the object switching layer processing part of the response command received from the secondary station, or to make the response generation part generate a virtual response command and notify the The object switching layer handles the switching of parts. the

According to the above configuration, it is also possible to switch whether to wait for a response command from the secondary station or to generate a dummy response command according to the type of header information of the request command. Therefore, it is possible to receive, for example, the minimum necessary response commands at the time of a connection request, a disconnection request, and a final data transfer request, while omitting the reception of response commands corresponding to data transfer requests other than the final data transfer request. deal with. the

Therefore, by receiving only the minimum necessary response commands from the secondary station, communication processing can be simplified while ensuring reliability of communication. Therefore, the scale of programs and circuits can be reduced. the

Furthermore, a communication system according to the present invention is characterized by including: the above-mentioned communication device as a master station; and a communication device as a secondary station receiving an object from the communication device. Furthermore, the communication system of the present invention is characterized in that the communication device serving as the secondary station does not transmit a response command. the

According to the communication system described above, even if the secondary station cannot transmit the response command, the master station generates a dummy response command and notifies the target switching layer. Therefore, without changing the conventional communication protocol of object exchange based on request command/response command, object exchange with a secondary station that does not have a transmission function but has a minimum required reception function can be performed. the

In addition, the communication device of the present invention has a secondary station as an object exchange layer, and the object exchange layer receives a request command from the master station and issues a response command in response to the request command, thereby receiving a request from the object exchange layer of the master station. object, characterized in that the communication device includes: an object exchange layer processing part processing a communication protocol of the object exchange layer; The lower layer processing section does not send the response command to the master station when receiving the response command from the object exchange layer processing section. the

In addition, the communication method of the present invention is used for a secondary station having an object exchange layer. The object exchange layer accepts a request command from the master station and issues a response command in response to the request command, thereby exchanging objects from the master station. The layer receives the object, and the feature is that when the lower layer lower than the object switching layer receives the response command sent by the object switching layer, it does not send the response command to the master station. the

According to the above structure and method, even if the target switching layer of the secondary station issues an unnecessary response command, it is not necessary to send it from the secondary station. For example, in the case where the object exchange layer of a secondary station (for example, a server device) often sends back a response command to a request command, when a request command from a master station (for example, a client device) is a command that does not require a response command When , the lower layer does not send the response command issued by the object switching layer of the secondary station. the

Therefore, it is possible to reduce the power consumed in the transmission of the secondary station. In addition, when the secondary station transmits a response command, since the master station does not necessarily need a response command, it is possible to prevent the possibility of a conflict between the response command from the secondary station and the next request command from the master station. the

Moreover, the communication device of the present invention is characterized in that the low-level processing section includes: a response analysis section that analyzes a response command issued by the object exchange layer processing section; and a low-level control section that analyzes the response based on the response analysis section. The type of the command is switched between sending or not sending the response command to the master station. the

According to the above configuration, it is also possible for the lower layer to determine whether to transmit or not to transmit the response command issued by the target switching layer according to the type of the response command. the

Therefore, for example, when the communication protocol of the object exchange layer is OBEX (OBject EXchange protocol), the communication protocol of the object exchange layer can not be changed without sending a CONTINUE response command corresponding to a PUT command that is not the last one. the

Furthermore, the communication device of the present invention is characterized in that the low-level processing section includes: a header information analysis section that analyzes header information of a response command issued by the object exchange layer processing section; and a low-level control section based on the The category of the header information analyzed by the header information analysis part performs switching of sending or not sending the response command to the master station. the

According to the above configuration, it is also possible for the lower layer to determine whether to transmit or not to transmit the response command issued by the object switching layer based on the type of header information of the response command. the

Therefore, for example, when the communication protocol of the object exchange layer is OBEX (OBject EXchange protocol), the communication protocol of the object exchange layer can not be changed without sending a CONTINUE response command corresponding to a PUT command that is not the last one. the

Furthermore, the communication system of the present invention is characterized by including: the above-mentioned communication device as a secondary station; and a communication device as a master station to transmit to the communication device. the

According to the communication system described above, when the request command from the master station does not require a response command, the lower layer does not transmit the response command from the object switching layer of the secondary station. the

Therefore, even if it is a conventional communication protocol in which the object exchange layer of the slave station performs object exchange based on the request command/response command, it can communicate with the master station that only receives the minimum required response command without changing it. object exchange. the

Furthermore, the communication device of the present invention is characterized in that the communication protocol of the object exchange layer is OBEX (Object EXchange protocol). the

According to the above configuration, object exchange with devices that do not have a transmission function can also be performed without changing the OBEX standard that has been widely adopted in IrDA, Bluetooth (registered trademark), etc., as a protocol for object exchange. the

Furthermore, the above-mentioned communication device can be realized by a computer. In this case, the communication program of the communication device of the above-mentioned communication device and the computer recording the program are realized by the computer by making the computer have the functions of each part of the above-mentioned communication device. Readable recording media are also within the scope of the present invention. the

In addition, the above-mentioned communication device may also be realized by a communication circuit having the functions of the above-mentioned parts. the

In addition, the communication device described above is suitable for a mobile phone that communicates with the communication device. According to the mobile phone described above, communication with high transmission efficiency can be performed using an object exchange protocol (including OBEX). the

Furthermore, the communication device described above is suitable for a display device that displays based on data received by the communication device. According to such a display device, communication with high transmission efficiency can be performed using an object exchange protocol (including OBEX). the

Furthermore, the communication device described above is suitable for a printing device that performs printing based on data received by the communication device. According to such a printing apparatus, communication with high transmission efficiency can be performed using an object exchange protocol (including OBEX). the

In addition, the communication device described above is suitable as a recording device that performs recording based on data received by the communication device. According to such a recording device, communication with high transmission efficiency can be performed using an object exchange protocol (including OBEX). the

Finally, the communication device of the present invention may also be configured as follows. the

(1. Communication method for simulated response under OBEX) 

In the communication method of the present invention, for the request command sent by the device on the side requesting the command, by receiving the response command sent back by the device on the side that responds to the request, using at least an object exchange protocol capable of exchanging objects. Each communication protocol of the layered structure is used for communication, and it is characterized in that, when the communication protocol of the layer corresponding to the lower layer of the layer corresponding to the object exchange protocol receives a request command sent from the object exchange protocol, it generates A dummy response command corresponding to a response command corresponding to the request command according to the protocol for object exchange is notified to a layer corresponding to the protocol for object exchange as a higher layer. the

(2. Communication device for analog response under OBEX)

The communication device of the present invention is characterized in that it includes: an object exchange layer processing part, for the request command sent by the client device on the side requesting the command, the client device receives the request command sent by the server device on the side that responds to the request command. A response command back, thereby exchanging objects; and a low-level processing part for performing communication at a lower layer lower than the object exchange layer processing layer, and the low-level processing part has: a response generation part that generates an equivalent to the response command and notify the object exchange layer processing part; and the low-level control part controls the response generating part to generate a virtual Respond to the command, thereby notifying the object exchange layer processing section. the

According to the above method and structure, on the side of the client device, a virtual response command is generated and notified to the object exchange protocol or the object exchange layer processing part, so the protocol for object exchange based on the request command/response command can not be changed, and there is no transmission Functional server devices with the required minimum reception capabilities perform object exchange. In addition, in the above structure and method, since it is not necessary to change the protocol for object exchange, existing resources can be called. the

(3. Communication method for analog response under OBEX (timer management)) 

In addition, in other communication methods of the present invention, for the request command sent by the device on the side requesting the command, by receiving the response command sent back by the device on the side that responds to the request, an object exchange with at least an object exchange that can be performed is used. Communication is carried out with each communication protocol of the layered structure of the protocol, and it is characterized in that the communication protocol at the lower layer corresponding to the layer of the protocol for the object exchange sends the communication protocol for the object exchange from the communication protocol at the lower layer. A request command issued by the protocol, until a response corresponding to the request command is received from the partner device, when a predetermined time elapses, a response command corresponding to the request command according to the protocol for object exchange is generated. Virtually respond to the command and notify the layer corresponding to the protocol for object exchange which is a higher layer. the

(4. Communication device for analog response under OBEX (timer management)) 

Another communication device of the present invention is characterized in that it includes: an object exchange layer processing part, for a request command transmitted by a client device on the side requesting a command, and receiving, through the client device, a server device on the side that responds according to the request command A response command sent back, thereby exchanging objects; and a low-level processing section for communication at a lower layer than the above-mentioned object exchange layer processing section, the low-level processing section having: a response generation section generating an equivalent to the response command The virtual response command of the object exchange layer is notified to the processing part of the object exchange layer; the timer acts when the object exchange layer processing part accepts the notification of the generation request command, and measures the elapsed time; and the low-level control part controls the The response generation section controls to generate a dummy response command to notify the object exchange layer even when the elapsed time of the timer reaches a preset setting value without receiving a response command from the server device processing part. the

According to the above method and structure, in the communication with the device having the sending function, object exchange based on the conventional request command/response command can be performed, and in the communication with the device not having the sending function, a dummy response command is generated by the lower layer Objects can be exchanged by notifying the protocol for object exchange that is a higher layer or the processing part of the object exchange layer. the

(5. Communication method (command type) for analog response under OBEX) 

In addition, in other communication methods of the present invention, for the request command sent by the device on the side requesting the command, by receiving the response command sent back by the device on the side that responds to the request, an object exchange with at least an object exchange that can be performed is used. Communication is carried out using each communication protocol of the layered structure of the protocol, and it is characterized in that the communication protocol located at a lower layer corresponding to the layer of the protocol for object exchange, when a request command is issued from the protocol for object exchange, according to the The type of the request command is switched as follows: receiving a response corresponding to the request command from the counterpart device, or generating a virtual response command equivalent to a response command corresponding to the request command based on the object exchange protocol, and notifying the corresponding A layer of a protocol for object exchange as a high-level layer. the

(6. Communication device for analog response under OBEX (command type)) 

Another communication device of the present invention is characterized in that it includes: an object exchange layer processing part, for the request command sent by the client device on the request command side, the server device on the side that responds according to the above request command is received by the client device A response command sent back, thereby exchanging objects; and a low-level processing section for communication at a lower layer than the above-mentioned object exchange layer processing section, the low-level processing section having: a response generation section generating an equivalent to the response command and notify the object switching layer processing part; and the low-level control part, when sending a request command from the object switching protocol, switches as follows according to the type of the request command: The response of the request command, or generate a virtual response command for the response generation part, and notify the object exchange layer processing part. the

According to the above-mentioned method and structure, for example, by receiving only the minimum response command required at the time of connection request, or disconnection request, final data transfer request, etc. from the server device, the reliability of communication can be ensured, for Response commands to data transfer requests other than the final data transfer request do not need to be received, so that the circuit scale can be reduced. the

(7. Communication method for analog response under OBEX (refer to OBEX header)) 

In addition, in other communication methods of the present invention, for the request command sent by the device on the side requesting the command, by receiving the response command sent back by the device on the side that responds to the request, an object exchange with at least an object exchange that can be performed is used. The communication is carried out using each communication protocol of the layered structure of the protocol, and it is characterized in that the communication protocol located at the lower layer corresponding to the layer of the protocol for object exchange refers to the header of the request command issued from the protocol for object exchange. According to the type of the request command, switching is performed as follows: receiving a response command corresponding to the request command from the other party device, or generating a virtual object equivalent to the response command corresponding to the request command according to the object exchange protocol. It responds to the command and notifies the layer corresponding to the protocol for object switching which is a higher layer. the

(8. Communication device for analog response under OBEX (refer to OBEX header)) 

Another communication device of the present invention is characterized in that it includes: an object exchange layer processing part, for a request command transmitted by a client device on the side requesting a command, and receiving, through the client device, a server device on the side that responds according to the request command A response command sent back, thereby exchanging objects; and a low-level processing section for communication at a lower layer than the above-mentioned object exchange layer processing section, the low-level processing section having: a response generation section generating an equivalent to the response command virtual response command, and notify the object exchange layer processing part; the header information analysis part analyzes the header information of the request command sent from the object exchange protocol; and the low-level control part, according to the header The category of the header information analyzed by the information parsing part, and switch as follows: receive a response command corresponding to a request command from the other party equipment, or generate a virtual response command for the response generation part, and notify the object exchange layer processing part . the

According to the above-mentioned method and structure, for example, by receiving only the minimum response command required at the time of connection request, or disconnection request, final data transfer request, etc. from the server device, the reliability of communication can be ensured, for Response commands to data transfer requests other than the final data transfer request do not need to be received, so that the circuit scale can be reduced. the

(9. The communication method that does not propagate the response from OBEX to the lower layer under OBEX) 

In addition, in other communication methods of the present invention, for the request command sent by the device on the side requesting the command, by receiving the response command sent back by the device on the side that responds to the request, an object exchange with at least an object exchange that can be performed is used. Communication is carried out with each communication protocol of the layered structure of the protocol, and it is characterized in that, when the communication protocol located at the lower layer corresponding to the layer of the protocol for object exchange receives a response command sent from the protocol for object exchange, The reply command is not sent. the

(10. Do not propagate responses from OBEX to low-level communication devices under OBEX)

In addition, another communication device of the present invention is characterized in that it includes: an object exchange layer processing section that receives, through the client device, the request command sent by the client device on the side that requests the command, from the client device on the side that responds to the request command. A reply command sent back by the server device, thereby exchanging objects; and a low layer processing section for communication at a lower layer than the above-mentioned object exchange layer processing section, said low layer processing section receiving the object exchange layer processing section by said object exchange layer processing section When the response command is issued, the response command is not sent to the counterpart station. the

According to the above method and structure, for example, in the object exchange protocol that does not need to return a response command to the request command from the client device side, even if the object exchange is performed on the client device side, even in the server device If the object exchange protocol on one side does not return a response command to the request command, it does not transmit the transmission request from the object exchange protocol control part on the server side, so it is related to the power consumption for transmission. reduce. On the other hand, if the response command is sent from the server device side, since the client device side does not need a response command, it is possible to prevent the conflict between the response command from the server device side and the next request command from the client device side. possibility. the

(11. The communication method (command type) that does not propagate the response from OBEX to the lower layer under OBEX)

In addition, in other communication methods of the present invention, for the request command sent by the device on the side requesting the command, by receiving the response command sent back by the device on the side that responds to the request, an object exchange with at least an object exchange that can be performed is used. Communication is carried out using each communication protocol of the layered structure of the protocol, and it is characterized in that the communication protocol located at a lower layer corresponding to the layer of the protocol for object exchange, when a response command is issued from the protocol for object exchange, according to The type of the response command is switched as follows: the response command is sent to the other device, or not sent. the

(12. Under OBEX, the response from OBEX is not propagated to the low-level communication device (command type))

In addition, another communication device of the present invention is characterized in that it includes: an object exchange layer processing section that receives, through the client device, the request command sent by the client device on the side that requests the command, from the client device on the side that responds to the request command. A response command sent back by the server device, thereby exchanging objects; and a low layer processing section for communication located at a lower layer than the above-mentioned object exchange layer processing section, the low layer processing section having functions for processing by the object exchange layer The response analysis part that analyzes the response command issued by the part has a low-level control part that switches between sending the response command to the counterpart device or not according to the type of the response command analyzed by the response analysis part. the

According to the above method and structure, for the response command sent by the object exchange protocol, the lower layer can judge whether to send or not to send according to the type of the response command. Processing such as the CONTINUE response command of the PUT command. the

(13. The communication method that does not propagate the response from OBEX to the lower layer under OBEX (refer to the OBEX header)) 

In addition, in other communication methods of the present invention, for the request command sent by the device on the side requesting the command, by receiving the response command sent back by the device on the side that responds to the request, an object exchange with at least an object exchange that can be performed is used. The communication is carried out using each communication protocol of the layered structure of the protocol, and it is characterized in that the communication protocol located at the lower layer corresponding to the layer of the protocol for object exchange refers to the header of the response command issued from the protocol for object exchange. According to the type of the header information, switching is performed as follows: the response command is sent to the counterpart device or not sent. the

(14. Under OBEX, the response from OBEX is not propagated to lower-level communication devices (refer to OBEX header))

In addition, another communication device of the present invention is characterized in that it includes: an object exchange layer processing section that receives, through the client device, the request command sent by the client device on the side that requests the command, from the client device on the side that responds to the request command. A reply command sent back by the server device, thereby exchanging objects; and a low-level processing section for communication located at a lower layer than the above-mentioned object exchange layer processing section, said low-level processing section having When the response command is issued, the header information parsing part for parsing the header information of the response command has the category of the header information parsed according to the header information parsing part, and switches as follows: The counterpart device transmits the response command, or the low-level control part not transmitted. the

According to the above method and structure, for the response command sent by the object exchange protocol, the lower layer can judge whether to send or not to send according to the type of the response command. Processing such as the CONTINUE response command of the PUT command. the

(15. Communication methods that do not require a response under the OBEX layer) 

In addition, another communication method of the present invention uses an object exchange protocol OBEX (OBjectEXchange protocol) to transmit an object to a counterpart station, and is characterized in that after sending an OBEX command, the next OBEX is sent without receiving an OBEX response from the counterpart station. Order. the

(16. A communication method that does not require a response when only one-way transmission is required) 

Other communication methods of the present invention, also in above-mentioned communication method, have after OBEX command is sent, switch to the two-way communication that needs the OBEX response from opposite station and the step that does not need the one-way communication of the OBEX response from opposite station, only in When the one-way communication is selected, after the OBEX command is sent, the next OBEX command can be sent without receiving an OBEX response from the counterpart station. the

(17. Communication devices that do not need to respond under the OBEX layer)

In addition, other communication devices of the present invention also have an OBEX layer processing part that can send an object to the opposite station using the protocol OBEX (OBject EXchange protocol) for object exchange, and it is characterized in that, in the OBEX layer processing part, the After sending an OBEX command, the next OBEX command is generated and sent without receiving an OBEX response from the partner station. the

(18. A communication device that does not require a response when sending only in one direction)

Another communication device of the present invention, in the above communication device, further has a communication method switching section for switching between two-way communication requiring an OBEX response from the counterpart station and one-way communication requiring no OBEX response from the counterpart station after the OBEX command is sent. , only when the communication method switching part selects one-way communication, after the OBEX command is generated and sent, the next OBEX command is generated and sent without receiving an OBEX response from the counterpart station. the

According to the above method and structure, for example, in one-way communication using OBEX, even if the client device side cannot receive the response command from the server corresponding to the request command from the client device side, OBEX can be performed. The objects below are sent. On the other hand, in the case of two-way communication, communication for confirming the response from the server is performed, and in the case of one-way communication, communication can be performed without a response from the server, and one OBEX protocol can be used to realize two-way communication and one-way communication. the

(19. Only the non-Final Put command does not require a response communication method)

In addition, another communication method of the present invention uses an object exchange protocol OBEX (OBjectEXchange protocol) to transmit an object to a counterparty station, and is characterized in that only after a non-final Put command of OBEX is sent, no OBEX from the counterparty station is received. In response, the next OBEX non-final Put command or final Put command is sent. the

(20. Only the non-Final Put command does not need to respond to the communication device)

In addition, other communication devices of the present invention have an OBEX layer processing part that can use the object exchange protocol OBEX (OBject EXchange protocol) to send objects to the counterparty station, and it is characterized in that, in the OBEX layer processing part, only when generating and After the OBEX non-final Put command is transmitted, the next OBEX non-final Put command or final Put command is generated and transmitted without receiving an OBEX response from the partner station. the

According to the above method and structure, it is possible to realize object exchange that does not only require a CONTINUE response command corresponding to the PUT command. the

(21. The communication method that does not send a response under the OBEX layer) 

Another communication method of the present invention uses the protocol OBEX (OBject EXchange protocol) for object exchange to receive objects from the counterpart station, and is characterized in that after receiving the OBEX command from the counterpart station, the OBEX response is not always sent. the

(22. When only receiving in one direction, the communication method that does not send a response under the OBEX layer) 

In addition, other communication methods of the present invention, in the above-mentioned communication method, have the step of switching between two-way communication that requires an OBEX response from the counterpart station and one-way communication that does not require an OBEX response from the counterpart station especially after the OBEX command is sent , only when the one-way communication is selected, after the OBEX command is received, the OBEX response may not always be sent to the counterpart station. the

(23. A communication device that does not send a response under the OBEX layer) 

In addition, other communication devices of the present invention have an OBEX layer processing part that can use the object exchange protocol OBEX (OBject EXchange protocol) to receive an object from a counterpart station, and it is characterized in that, in the OBEX layer processing part, after receiving the The OBEX response is not always sent after the OBEX command of the other station. the

(24. A communication device that does not send a response under the OBEX layer when only receiving in one direction)

In addition, other communication devices of the present invention are further provided with a communication method for switching between two-way communication that does not require an OBEX response from the counterpart station and one-way communication that does not require an OBEX response from the counterpart station after the OBEX command is sent in the above-mentioned communication device. The switching section may not always transmit an OBEX response to the counterpart station after receiving the OBEX command only when the communication method switching section selects one-way communication. the

According to the above-mentioned method and structure, for example, in one-way communication using OBEX, in the case where the client device side does not need to send a response command from the server device side corresponding to the request command from the client device side, it is possible to Control is performed not to generate and send unnecessary response commands. In the two-way communication, by sending a response command to the client device side, the communication confirmation on the client device side can be performed, and in the one-way communication, it is not necessary to generate and send an unnecessary response command to the client device, and a single The OBEX protocol realizes two-way communication and one-way communication. the

(25. Only the non-Final Put command does not respond to the communication method)

In addition, another communication method of the present invention uses the protocol OBEX (OBjectEXchange protocol) for object exchange to receive an object from a partner station, and is characterized in that when a non-final Put command of OBEX is received, no OBEX response is sent, and the final When the Put command is received, the OBEX response is sent. the

(26. Only the non-Final Put command does not respond to the communication device)

In addition, other communication devices of the present invention have an OBEX layer processing part that can use an object exchange protocol OBEX (OBject EXchange protocol) to receive an object from a counterpart station, and it is characterized in that, in the OBEX layer processing part, after receiving the OBEX When a non-final Put command is issued, the OBEX response is not sent, and when the final Put command is received, an OBEX response is generated and sent. the

According to the above method and structure, only the CONTINUE response command corresponding to the non-final PUT command from the client device side can be generated and controlled not to be transmitted, and high efficiency of the communication band can be realized. the

(27. The object exchange protocol is the communication method of OBEX)

In addition, in the communication method described above, the object exchange protocol may be OBEX. According to the method described above, object exchange with a device that does not have a transmission function can be performed without changing the widely used OBEX standard such as IrDA or Bluetooth (registered trademark) as a protocol for object exchange. the

(28. Communication program)

Furthermore, the communication program of the present invention is characterized in that it is a program for realizing each step of each communication protocol of any one of the communication methods described above by a computer. Through the above-mentioned communication program, each step of each communication protocol of the above-mentioned communication method is realized by a computer, so that the above-mentioned communication method can be realized. the

(29. Recording media) 

Furthermore, the recording medium of the present invention is characterized in that the above-mentioned communication program is recorded so as to be readable by a computer. According to the above-mentioned configuration, the above-mentioned communication method can be implemented on a computer by the communication program read from the above-mentioned recording medium. the

(30. Communication system)

The communication system of the present invention is used for exchanging objects between a client device and a server device, wherein the server device cannot send a response, and the client device is the communication device described in any one of the above items. the

According to the above-mentioned communication system, even if the server device cannot send a response response, on the client device side, a dummy response command is generated and notified to the object switching layer processing section, so the conventional communication protocol that performs object switching based on request command/response command is not changed. , objects can be exchanged with a server device that does not have a sending function but has the required minimum receiving function. the

(31. Mobile phone)

A mobile phone as a communication device of the present invention is characterized in that it is a mobile phone that realizes any one of the above-mentioned communications. According to the mobile phone described above, it is possible to perform one-way communication or communication with high transmission efficiency by using an object exchange protocol (including OBEX). the

(32. Display device)

A display device as a communication device of the present invention is characterized in that it is a display device that realizes any one of the above-mentioned communications. According to the display device described above, one-way communication or communication with high transfer efficiency can be performed using an object exchange protocol (including OBEX). the

(33. Printing device)

A printing device as a communication device of the present invention is characterized in that it is a printing device that realizes any one of the above-mentioned communications. According to the printing apparatus described above, one-way communication or communication with high transmission efficiency can be performed using an object exchange protocol (including OBEX). the

(34. Recording device) 

A recording device as a communication device of the present invention is characterized in that it is a recording device that realizes any one of the above-mentioned communications. According to the recording device described above, it is possible to perform one-way communication or communication with high transmission efficiency using an object exchange protocol (including OBEX). the

The specific implementation modes or examples formed in the detailed description of the invention are to clarify the technical content of the present invention after all, and should not be limited to such specific examples and be interpreted in a narrow sense. In the spirit of the present invention and the claims Various changes can be made within the scope of implementation. the

Industrial Utilization Possibility

In the communication device, communication system, communication method, communication program, and communication circuit of the present invention, without changing the protocol for object exchange, object exchange can be performed with equipment (secondary stations) that do not have a sending function, so the present invention can be widely used For communication such as mobile phones, PDAs, personal computers, etc. It is particularly suitable for communication using a protocol for object exchange that exchanges objects between a client device that sends a request command through infrared communication based on IrDA or wireless communication based on Bluetooth, and a server device that sends back a response command. the

Claims (16)

1. communicator, as the main website with object exchange layer, this object exchange layer is by sending request command, and accepts acknowledgement command that this request command is responded, thereby the object exchange layer at pair station is sent object, it is characterized in that,

Described communicator comprises:

The communication protocol of described object exchange layer is handled in object exchange layer processing section; And the low layer processing section, handle the communication protocol of described low layer,

Described object exchange layer processing section comprises: control section, request notification section and response receiving unit, control section is according to the request from the application layer process part, request notification section notice is carried out the generation of request command and sent request command to low layer, and accept acknowledgement command reception result notice from the response receiving unit, reception result to application layer processing section notice acknowledgement command, the request notification section is accepted to give notice from the request command of control section, generate request command and output to the low layer processing section, the response receiving unit receives from the acknowledgement command of low layer processing section output, the acknowledgement command that receives is resolved, the control section notice is received command analysis result and acknowledgement command

Described low layer processing section comprises: request receiving unit, request notification section, low layer control section and response generating portion; The described request receiving unit receives from the request command of described object exchange layer processing section output, carry out the parsing of request command, described low layer control section notice has been received command analysis result and request command, and will send to the described request notification section of described low layer processing section as the request command of the data that receive; The described request notification section of described low layer processing section is accepted to give notice from the request command of described low layer control section based on receiving command analysis result and request command, additional necessary header information and generate request command; The described response generating portion of described low layer processing section generates carries out virtual virtual acknowledgement command to the acknowledgement command from described secondary station, and notifies described object exchange layer processing section; Described low layer control section, control the described response generating portion of described low layer processing section, with when the generation of the order that accepts request from described object exchange layer processing section is notified, generation is used to respond the described virtual acknowledgement command of this request command, thereby notifies described object exchange layer processing section;

The communication protocol of described object exchange layer is object exchange layer protocol, i.e. OBEX.

2. communicator as claimed in claim 1 is characterized in that,

Described low layer processing section also comprises:

Timer moves when the generation of the order that accepts request from described object exchange layer processing section is notified, thereby measures the elapsed time,

Described low layer control section is controlled described response generating portion simultaneously, even arrive predefined set point with elapsed time at described timer, and when not receiving acknowledgement command from described secondary station yet, generate described virtual acknowledgement command, thereby notify described object exchange layer processing section.

3. communicator as claimed in claim 1 is characterized in that,

The described low layer control section of described low layer processing section is according to the kind of the request command that is sent by described object exchange layer processing section, carry out and to notify described object exchange layer processing section from the acknowledgement command that described secondary station receives, or make described response generating portion generate virtual acknowledgement command and notify the switching of described object exchange layer processing section.

4. communicator as claimed in claim 1 is characterized in that,

Described low layer processing section also comprises:

Header information is resolved part, resolves the header information of the request command that is sent by described object exchange layer processing section,

Described low layer control section divides the classification of the header information of resolving according to described header information analysis unit simultaneously, carry out and to notify described object exchange layer processing section from the acknowledgement command that described secondary station receives, or make described response generating portion generate virtual acknowledgement command and notify the switching of described object exchange layer processing section.

5. communicator, as the pair station with object exchange layer, this object exchange layer sends the acknowledgement command that this request command is responded by accepting the request command from main website, thereby receives object from the object exchange layer of main website, it is characterized in that,

Described communicator comprises: object exchange layer processing section, handle the communication protocol of described object exchange layer; And

The communication protocol of described low layer is handled in the low layer processing section,

Described object exchange layer processing section comprises control section and request analysis part;

The described request analysis unit is divided the request command of resolving from the output of described low layer processing section, notify described control section with analysis result, described control section will be notified to the application layer process part from the analysis result of described request analysis unit branch notice, and based on described analysis result, described request is resolved the part indication partly transmit application data to described application layer process

The low layer processing section comprises: low layer control section and request analysis part;

The described request analysis unit of described low layer processing section is divided the request command of resolving from described main website, analysis result is notified the described low layer control section of described low layer processing section, and from the request command of accepting, extract the object exchange grouping, based on the object exchange grouped data that is extracted from the transmission indication of the described control section of described low layer processing section and to the output of described object exchange layer processing section; Described low layer control section will be resolved the analysis result of partly notifying from the described request of described low layer processing section and be notified described object exchange layer processing section,

Described low layer processing section does not send to main website with this acknowledgement command when having accepted the described acknowledgement command that is sent by described object exchange layer processing section,

The communication protocol of described object exchange layer is object exchange layer protocol, i.e. OBEX.

6. communicator as claimed in claim 5 is characterized in that,

Described low layer processing section comprises:

Part is resolved in response, resolves the acknowledgement command that is sent by described object exchange layer processing section; And

The low layer control section according to the kind that described response analysis unit is divided the acknowledgement command of resolving, carries out sending or not sending to main website the switching of described acknowledgement command.

7. communicator as claimed in claim 5 is characterized in that,

Described low layer processing section comprises:

Header information is resolved part, resolves the header information of the acknowledgement command that is sent by described object exchange layer processing section; And

The low layer control section divides the classification of the header information of resolving according to described header information analysis unit, carries out sending or not sending to main website the switching of described acknowledgement command.

8. communication means is used to have the main website of object exchange layer, and this object exchange layer is by sending request command, and accepts acknowledgement command that this request command is responded, and the object exchange layer at pair station is sent object, it is characterized in that,

Handle the communication protocol of described object exchange layer at described object exchange layer, handle the communication protocol of described low layer being positioned at low layer under the described object exchange layer, wherein

Carry out at described object exchange layer: according to request from the application layer process part, request notification section notice is carried out the generation of request command and sent request command to low layer, and accept acknowledgement command reception result notice from the response receiving unit, reception result to application layer processing section notice acknowledgement command, the request notification section is accepted to give notice from the request command of control section, generate request command and output to the low layer processing section, the response receiving unit receives from the acknowledgement command of low layer processing section output, the acknowledgement command that receives is resolved, the control section notice is received command analysis result and acknowledgement command

Carry out at the low layer that is positioned under the described object exchange layer: receive from the request command of described object exchange layer processing section output from the request receiving unit of described low layer, carry out the parsing of request command, control section notice to described low layer has received command analysis result and request command, and will send to the request notification section of described low layer as the request command of the data that receive; The described request notification section of described low layer is based on receiving command analysis result and request command, accepts to give notice from the request command of the control section of described low layer additional necessary header information and generate request command; The described response generating portion of described low layer generates carries out virtual virtual acknowledgement command to the acknowledgement command from described secondary station, and notifies described object exchange layer processing section; The control section of described low layer is controlled the described response generating portion of described low layer processing section, with when the generation of the order that accepts request from described object exchange layer processing section is notified, generation is used to respond the described virtual acknowledgement command of this request command, thereby notify described object exchange layer processing section

The communication protocol of described object exchange layer is object exchange layer protocol, i.e. OBEX.

9. communication means is used to have the pair station of object exchange layer, and this object exchange layer sends the acknowledgement command that this request command is responded by accepting the request command from main website, thereby receives object from the object exchange layer of main website, it is characterized in that,

At described object exchange layer,

Handle the communication protocol of described object exchange layer, handle the communication protocol of described low layer being positioned at low layer under the described object exchange layer, wherein

Carry out at described object exchange layer:

The request analysis of described object exchange layer is partly resolved from the request command of described low layer output, notifies the control section of described object exchange layer with analysis result,

The control section of described object exchange layer will be notified to the application layer process part from the analysis result that the request analysis of described object exchange layer is partly notified, and based on described analysis result, the request analysis of described object exchange layer partly indicated to described application layer process partly transmit application data

Carry out at the low layer that is positioned under the described object exchange layer: resolve request command from described main website, analysis result is notified the described low layer control section of described low layer, and from the request command of accepting, extract the object exchange grouping, based on the object exchange grouped data that is extracted from the transmission indication of the described control section of described low layer and to the output of described object exchange layer processing section; The described low layer control section of described low layer will be resolved the analysis result of partly notifying from the described request of described low layer and be notified described object exchange layer processing section,

Described low layer does not send to main website with this acknowledgement command when having accepted the acknowledgement command that is sent by described object exchange layer,

The communication protocol of described object exchange layer is object exchange layer protocol, i.e. OBEX.

10. communication system is characterized in that comprising:

As any one described communicator of claim 1 to 4 as main website, and

As the communicator that receives the pair station of object from this communicator.

11. communication system as claimed in claim 10 is characterized in that,

Communicator as described secondary station does not send acknowledgement command.

12. a communication system is characterized in that comprising:

Any one described communicator of claim 5 to 7 as secondary station; And

As the communicator that sends the main website of object to this communicator.

13. a portable phone has loaded any one described communicator of claim 1 to 7, and communicates by this communicator.

14. a display unit has been loaded any one described communicator of claim 5 to 7, and shows based on the data that received by this communicator.

15. a printing equipment has loaded any one described communicator of claim 5 to 7, and prints based on the data that received by this communicator.

16. a tape deck has loaded any one described communicator of claim 5 to 7, and record is by the data of this communicator reception.

Images