WO2006080330A1

WO2006080330A1 - Communication device, communication system, communication method, communication program, and communication circuit

Info

Publication number: WO2006080330A1
Application number: PCT/JP2006/301106
Authority: WO
Inventors: Koji Sakai; Hitoshi Naoe; Fumihiro Fukae; Shohei Osawa
Original assignee: Sharp Kabushiki Kaisha
Priority date: 2005-01-28
Filing date: 2006-01-25
Publication date: 2006-08-03

Abstract

In an client device (1) having OBEX, a pseudo-response command is generated for a request command by a lower layer processing unit (13) as a lower layer of an OBEX layer processing layer (12) and this is reported to the OBEX layer processing layer (12). This enables communication by object exchange with a server device having no transmission function.

Description

Specification

Communication device, communication system, communication method, communication program, communication circuit

The present invention relates to a communication device, a communication system, a communication method, a communication program, and a communication circuit for exchanging data and exchanging and transferring data. Background art

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

[0003] Applications that adopt OBEX 'Software can exchange various objects with each other without having to be aware of differences in communication devices and communication methods, and uses IrDA (Infra Red Data Association) ) It has been adopted in a wide range of fields as a session protocol such as the Blue tooth (registered trademark) communication method that uses wireless communication (2.4 GHz band).

[0004] As an object, in addition to normal files, device diagnosis, business cards, bank account details, electrocardiograms, receipts, and the like are assumed. For example, it will be possible to exchange address book data and business card data between laptop computers, mobile phones, and PDAs (portable information communication devices) equipped with IrDA or Blue tooth communication functions. It can also be used to send video data taken with a mobile phone or digital still camera to a TV, monitor, or street corner kiosk. In addition, it can be used to control TV receivers and VTRs.

[0005] OBEX is an IrDA high-level protocol equivalent to the OSI (Open System Interconnection) reference model session 'layer' and has the same functions as the HTTP (Hyper Text Transform Protocol) of the Internet. It does not require

[0006] Figure 7 shows the standard IrDA protocol stack. The IrDA protocol stack includes IrPHY (IrDA Physical Layer), which defines modulation method, signal strength, directivity, etc. In addition to error control function according to C (High level Data Link Control), transparent transmission, and flow control, function to negotiate communication speed and maximum data size with each other prior to communication, and unspecified external to be connected Multiplexing corresponding to port numbers used in IrLAP (IrDA Link Access Protocol) and TCP / IP (Transmission Control Protocol 1 / Internet Protocol) TCP and UDP, which define procedures for searching and finding devices It consists of IrLMP (IrDA Link Management Protocol), which provides separation functions, and TinyTP (Transport Protocol) for performing flow control over individual logical links. OBEX is positioned above the transport protocol 'TinyTP'. To do.

In OBEX, a device that requests a command is called a client device, and a device that returns a response in response to the request is called a server device. Normally, the client device issues a request command such as Put ZGet to the server device, and the Sano device returns a response command.

[0008] Request commands defined by OBEX generally include the following. Connect with the communication partner Z Disconnect CONNECTZDISCONNECT, send files and other objects PUTZGET to receive Z, set the destination path (current path) of the server device on the receiving device to SETPATH, and send and receive objects There is an A BORT that is forcibly interrupted.

FIG. 8 illustrates the exchange of basic request command Z response commands between the client device and the server device. When receiving a user-powered object exchange request, 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.

[0010] When the server device that has received the CONNECT command can connect to the client device, the server device returns a SUCCESS response command and the client device receives the SUCCE SS response command. A connection is established between server devices.

[0011] After establishing the connection, the client device starts exchanging objects, and transmits a PUT command for transmitting the object to the Sano device. When the Sano device receives the PUT command from the client device normally, it returns a CONTINUE response command and The client device receives the CONTINUE response command with the server device power, confirms that the server device has received the PUT command normally, and then transmits the next PUT command. The client device sends a PUT command until all objects have been sent. When the server device has successfully received the last PUT command, it returns a SUCCES S response command to the client device.

[0012] After receiving the SUCCESS response command from the Sano device, the client device sends a DISCONNECT command indicating a disconnect request to the server device in order to disconnect from the server device.

[0013] The server device that has received the DISCONNECT command returns a SUCCESS response command that indicates disconnection permission to the client device, and the client device receives the SUCCE SS response command. Between the client device and server device is completed.

[0014] In this way, in OBEX, the server device returns a response command in response to a request command that requires a client device, and the object is exchanged.

[0015] In addition, in the communication protocol having a hierarchical structure such as OSI as in the IrD A protocol stack described above, header information is defined for each layer independently of the other layers. The header information is sequentially added to the data to be transferred in each layer from the highest layer to the lowest layer. For received data, header information is sequentially removed from each layer from the lowest layer to the highest layer, and the data is passed to the upper layer.

[0016] As shown in FIG. 9, on the client device side, the request command force generated in the OBEX layer, header information independently defined for each layer in each of the TinyTP layer, IrLMP layer, and IrLAP layer is sequentially added, Data is passed to the lower layer. The server device removes the header information from the lower layer sequentially for the data received by the client device, and passes the data to the upper layer. The OBEX layer removes the lower layer header information. Requested commands (CONNECT, PUT, DISCONNECT commands, etc.) are raised from the lower layer.

[Patent Document 1] Japanese Patent Publication “JP 2000-196622 A (publication date 2000) July 14,

As mentioned above, OBEX can exchange various objects without being aware of differences in devices and systems, so it has been adopted as an object exchange protocol by IrDA, Blue tooth, etc. It is mounted on various devices such as mobile terminals.

[0018] However, in order to realize object exchange between a client device equipped with OBEX and a Sano device, the server device must always have a transmission function for returning a response command. Arise. Having a server device with a transmission function leads to increased device cost and development difficulty, and object exchange has been realized by providing only the minimum necessary reception functions! There is.

[0019] Also, as described above, in the object exchange by the PUT command of OBEX !, during the object exchange, the CONTIN UE response command for the PUT command from the client is also transmitted by the server. . The SUCCES S response command for the last PUT command is a force necessary for the client to know that the object exchange has been performed reliably. The CONTINUE response command is used to send the CONTINUE response command. Given the bandwidth, it may not always be necessary

[0020] In addition, as described above, OBEX is currently implemented in various devices, and if it is not easy to change the specifications, existing assets can be diverted. Disappear.

Disclosure of the invention

[0021] An object of the present invention is to prevent a server device from returning a response command in response to a specific request command or all request commands from a client device when communication is performed using an object exchange protocol. Another object is to provide a communication device, a communication system, a communication method, a communication program, and a communication circuit.

In order to achieve the above object, the communication device according to the present invention issues a request command and receives a response command in response to the request command, thereby transmitting an object to the object exchange layer of the secondary station. Communication device as a primary station having an object exchange layer An object exchange layer processing unit that processes a communication protocol of the object exchange layer, and a lower layer processing unit that processes a communication protocol of a lower layer located below the object exchange layer, and A lower layer processing unit generates a pseudo response command simulating a response command from the secondary station and notifies the object exchange layer processing unit, and a request command is generated from the object exchange layer processing unit. A lower layer control unit that controls the response generation unit to generate the pseudo response command in response to the request command and to notify the object exchange layer processing unit when the notification is received. RU

[0023] In addition, the communication method according to the present invention includes an object exchange layer that issues a request command and transmits an object to the object exchange layer of the secondary station by receiving a response command in response to the request command. A communication method in a primary station, and when a lower layer located below the object exchange layer receives a request command generation notification from the object exchange layer, a response from the secondary station responding to the request command A pseudo response command simulating the command is generated and notified to the object exchange layer.

[0024] With the configuration and method described above, in the primary station (for example, client device), a lower layer below the object exchange layer generates a pseudo response command and notifies the object exchange layer.

[0025] Therefore, object exchange with a secondary station (for example, a server device) having a minimum reception function that does not have a transmission function without changing a communication protocol for performing object exchange by a request command Z response command. There is an effect that becomes possible. In addition, since it is not necessary to change the communication protocol (object exchange protocol) of the object exchange layer in order to transmit / receive to / from the secondary station as described above, it is possible to divert existing assets. Play.

[0026] A communication system according to the present invention includes the communication device as a primary station and a communication device as a secondary station that receives the communication device power object. Furthermore, the communication system according to the present invention is characterized in that the communication device as the secondary station does not transmit a response command. [0027] According to the above communication system, even if the secondary station cannot transmit a response command, the primary station generates a pseudo response command and notifies the object exchange layer. Therefore, it is possible to exchange objects with a secondary station that has a minimum reception function that does not have a transmission function without changing the conventional communication protocol, such as object exchange by request command Z response command. The effect of becoming.

[0028] Further, the communication device according to the present invention receives an object command from the object exchange layer of the primary station by receiving a request command having a primary power and issuing a response command in response to the request command. A communication apparatus as a secondary station having a layer, an object exchange layer processing unit that processes the communication protocol of the object exchange layer, and a lower layer that processes a communication protocol of a lower layer located below the object exchange layer A layer processing unit, and when the lower layer processing unit receives the response command issued by the object exchange layer processing unit, it does not transmit the response command to the primary station. As a feature.

[0029] Further, the communication method according to the present invention receives an object command from an object exchange layer of a primary station by receiving a request command having a primary power and issuing a response command in response to the request command. In a communication method in a secondary station having a layer, when a lower layer located below the object exchange layer receives a response command issued by the object exchange layer, the response command is transmitted to the primary station. It is characterized by not.

[0030] With the configuration and method described above, even if the object exchange layer of the secondary station issues an unnecessary response command, the secondary station power can be prevented from being transmitted. For example, when the object exchange layer of the secondary station (for example, server device) is configured to always return a response command to the request command, the request command from the primary station (for example, client device) When a response command is not required, the lower layer does not send a response command issued by the object exchange layer of the secondary station.

Accordingly, there is an effect that it is possible to reduce the power required for the transmission of the secondary station. If the secondary station sends a response command, the primary station does not need a response command, so the response command from the secondary station may collide with the next request command from the primary station. There is also an effect that it is possible to prevent it.

[0032] A communication system according to the present invention includes the communication device as a secondary station and the communication device as a primary station that transmits an object to the communication device.

[0033] According to the communication system described above, when the request command from the primary station is V that requires a response command, the lower layer does not transmit the response command issued by the object exchange layer of the secondary station.

[0034] Therefore, even the conventional communication protocol in which the object exchange layer of the secondary station performs object exchange using the request command Z response command does not change it, only the minimum necessary response command is required. It is possible to exchange objects with the primary station that receives the reply.

[0035] In this case, the communication device may be realized by a computer. In this case, communication of the communication device that realizes the communication device by the computer by operating the computer as each unit of the communication device. A program and a computer-readable recording medium on which the program is recorded also fall within the scope of the present invention.

[0036] The communication device may be realized by a communication circuit functioning as each of the above-described units.

[0037] The communication device is suitable for a mobile phone that performs communication using the communication device. According to the above mobile phone, it is possible to perform communication with high transfer efficiency using an object exchange protocol (including OBEX).

[0038] The communication device is suitable for a display device that displays data based on data received by the communication device. According to such a display device, communication can be performed with high transfer efficiency using an object exchange protocol (including OBEX).

[0039] The communication apparatus is suitable for a printing apparatus that performs printing based on data received by the communication apparatus. According to such a printing apparatus, it is possible to perform communication with high transfer efficiency using an object exchange protocol (including OBEX).

[0040] The communication device is suitable for a recording device for recording data received by the communication device. According to such a recording apparatus, it is possible to perform communication with high transfer efficiency using an object exchange protocol (including OBEX). [0041] Still other objects, features, and advantages of the present invention will be sufficiently provided by the following description. The advantages of the present invention will be apparent from the following description with reference to the accompanying drawings.

Brief Description of Drawings

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

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

FIG. 3 is a block diagram showing a configuration example of a Sano device in the communication system.

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

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

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

FIG. 7 is a conceptual diagram showing an IrDA protocol stack.

FIG. 8 is a sequence diagram showing a basic request command 'response command exchange procedure in the OBEX communication standard.

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

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

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

FIG. 12 is a sequence diagram showing a procedure of data transfer processing in the third embodiment and the fourth embodiment.

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

[Fig.14] Flow showing the operation of the lower layer processing unit of the OBEX layer in a conventional server device It is a chart.

FIG. 15 is a flowchart showing the operation of the lower layer processing unit of the OBEX layer in the server device in the communication system according to the fifth embodiment.

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

圆 17] A block diagram showing a configuration of a server device in the communication system according to the sixth embodiment of the present invention.

FIG. 18 is a flowchart showing the operation of the lower layer processing unit of the OBEX layer in the server device in the communication system of the sixth embodiment.

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

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

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

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

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

FIG. 24 is a flowchart showing the operation of the OBE X layer in the client device in the communication system according to the seventh embodiment.

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

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

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

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

[29] A server in the communication system according to the ninth and tenth embodiments of the present invention. It is a block diagram which shows the other structure of bar apparatus.

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

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

圆 32] A flowchart showing the operation of the OBEX layer in the Sano device in the communication system according to the tenth embodiment of the present invention.

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

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

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

36] 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.

[37] FIG. 37 is a schematic diagram showing the correspondence between the OSI7 hierarchical model, the IrDA hierarchy, and the hierarchy of the present invention.

FIG. 38 (a) is a sequence diagram of connection establishment according to the embodiment of the present invention. (b) is a sequence diagram of connection establishment according to the embodiment of the present invention. (C) is a packet format for connection establishment according to the embodiment of the present invention.

FIG. 39 (a) shows a data exchange sequence according to the embodiment of the present invention. (b

() Is a diagram showing a data exchange sequence according to the embodiment of the present invention.

FIG. 40 (a) is a diagram showing a packet format used in IrDA data exchange.

(b) is a figure which shows the packet format used by the data exchange of this invention.

FIG. 41 (a) shows a data exchange sequence according to the embodiment of the present invention. (b

FIG. 42 (a) is a diagram showing a cutting sequence according to the embodiment of the present invention. (b) is a diagram showing a cutting sequence according to the embodiment of the present invention. (C) Implementation of the present invention It is the packet format of the cutting | disconnection sequence which concerns on a form of.

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

FIG. 44 (a) is an explanatory diagram showing a change in data in a function between layers indicated by right-pointing arrows in FIGS. 43 and 45 in the connection sequence according to the embodiment of the present invention. (b) is a diagram showing a change in data in a function between layers according to the embodiment of the present invention.

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

FIG. 46 is a sequence diagram showing functions (commands, messages) and packet flows between layers during data exchange according to the embodiment of the present invention.

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

FIG. 48 is a sequence diagram showing functions (commands, messages) and packet flows between layers during data exchange according to the embodiment of the present invention.

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

FIG. 50 (a) is an explanatory diagram showing a change in data in a function between layers indicated by right-pointing arrows in FIGS. 49 and 51 in the cutting sequence according to the embodiment of the present invention. (b) is an explanatory view showing a change in data in a function between layers according to the embodiment of the present invention.

FIG. 51 is a sequence diagram showing functions (commands, messages) and packet flows between layers in the cutting sequence according to the embodiment of the present invention.

[52] FIG. 52 is a schematic diagram showing connection request function data and connection parameter passing in the primary station according to the embodiment of the present invention. [53] FIG. 53 is a schematic diagram showing delivery of connection parameters of the connection request function in the secondary station according to the embodiment of the present invention.

FIG. 54 shows a connection confirmation function in the primary station and a connection in the secondary station according to the embodiment of the present invention. It is a schematic diagram showing delivery of the data of a continuous notification function, and a connection parameter.

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

FIG. 56 is a schematic diagram showing delivery of connection parameters of a connection confirmation function in the primary station according to the embodiment of the present invention.

FIG. 57 is a schematic diagram showing connection request function data and connection parameter delivery at the primary station when connection parameters are shared between layers, which is a modification of the embodiment;

FIG. 58 is a schematic diagram showing the connection notification function data and the transfer of connection parameters in the secondary station when the connection parameters are shared between layers, which is a modification of the embodiment.

FIG. 59 is a schematic diagram showing connection request function data and connection parameter delivery in the primary station when connection parameters are separately passed to lower layers, which is a modification of the embodiment.

Explanation of symbols

1 Client device (communication device, primary station)

11 Application layer processor

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

121 Control unit

122 Request notification section

123 Response receiver

13 Lower layer processing section

131 Control unit (lower layer control unit)

132 Request receiver

133 Request notification section

134 Response generator

14 Transmitter

15 Receiver

2 Client equipment (communication equipment, primary station) Application layer processor

OBEX layer processing unit (object exchange layer processing unit) Control unit

Request notification section

Response receiver

Lower layer processing section

Control unit (lower layer control unit)

Request receiver

Request notification section

Response receiver

Response notification section

Response generator

Multiplexer

Timer

Transmitter

Receiver

Client equipment (communication equipment, primary station) Application layer processing section

OBEX layer processing unit (object exchange layer processing unit) Control unit

Request notification section

Response receiver

Lower layer processing section

Control unit (lower layer control unit)

Request receiver

Request notification section

Response receiver

Response notification section 336 Response generator

337 Multiplexer

34 Transmitter

35 Receiver

4 Client equipment (communication equipment, primary station)

41 Application layer processing section

42 OBEX layer processing unit (object exchange layer processing unit) 421 Control unit

422 Request notification part

423 response receiver

43 Lower layer processing section

431 Control unit (lower layer control unit)

432 Request receiver

433 Request notification section

434 Response receiver

435 Response notification part

436 Response generator

437 multiplexer

438 Header information analysis part

44 Transmitter

45 Receiver

5 Server equipment (communication equipment, secondary station)

51 Application layer processor

52 OBEX Layer Processing Unit (Object Exchange Layer Processing Unit) 521 Control Unit

525 Requirements Analysis Department

53 Lower layer processing section

531 Control unit 535 Requirements analysis part

54 Transmitter

55 Receiver

1000 Server equipment (communication equipment, secondary station)

1010 Application layer processor

1020 OBEX layer processing unit (object exchange layer processing unit) 1021 Control unit

1022 Response notification part

1025 Requirements analysis part

1030 Lower layer processing section

1031 Control unit (lower layer control unit)

1032 Response receiver

1035 Requirements analysis part

1050 receiver

1100 Server equipment (communication equipment, secondary stations)

1110 Application layer processor

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

1121 Control unit

1122 Response notification part

1125 Requirements analysis part

1130 Lower layer processing section

1131 Control unit (lower layer control unit)

1132 Response receiver

1135 Requirements Analysis Department

1140 Transmitter

1150 Receiver

1300 Client equipment (communication equipment, primary station)

1310 Application layer processor 1320 OBEX Layer Processing Unit (Object Exchange Layer Processing Unit)

1321 Control unit

1322 Request notification section

1323 Response receiver

1324 Communication direction selector

1330 Lower layer processing section

1340 Transmitter

1350 Receiver

1500 Server equipment (communication equipment, secondary station)

1510 Application layer processor

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

1521 Control unit

1522 Response notification part

1523 Requirements analysis part

1530 Lower layer processing section

1540 Transmitter

1550 receiver

BEST MODE FOR CARRYING OUT THE INVENTION

[0044] [Overview]

In each embodiment to be described later, the configuration and operation of the client device (primary station) and the server device (secondary station) of the communication system according to the present invention will be described in detail based on the OSI7 layer model. Here, the OSI 7 layer model is also called “OSI basic reference model” or “OSI hierarchical model”.

[0045] In the OSI seven-layer model, in order to realize data communication between different models, communication functions that a computer should have are divided into seven layers, and standard function modules are defined for each layer.

Specifically, the first layer (physical layer) is in charge of electrical conversion or mechanical work for sending data to the communication line. The second layer (data link layer) secures a physical communication path. And error detection of data flowing through the communication path. The third layer (network layer) selects the communication path and manages the addresses in the communication path. The fourth layer (transport layer) performs data compression, error correction, and retransmission control. The fifth layer (session layer) establishes and releases a virtual route (connection) for communication programs to send and receive data. Layer 6 (Presentation Layer) converts the data received from Layer 5 into a format that is easy for the user to understand, and converts the data sent from Layer 7 into a format suitable for communication. . The seventh layer (application layer) provides various services using data communication to humans and other programs.

[0047] Each communication layer of the communication system according to each embodiment also has a function equivalent to the corresponding layer of the OSI7 layer model. However, in each embodiment, the communication system has a six-layer structure with one session layer and one presentation layer. In each embodiment, an example will be described in which the communication layer including the session layer and the presentation layer is realized by OBEX (OBject EXchange protocol). A communication layer located below the OBEX layer and provided with a lower layer processing unit (described later) will be described as a transport layer. However, the communication layer in which the lower layer processing unit is provided may be a network layer or a data link layer. Note that description of the application layer is omitted.

[0048] The present invention is widely applicable to communication systems in which a transmitter and a receiver establish communication of a plurality of communication layers and perform communication. In other words, the division of communication functions may not follow the OSI 7 layer model. The number of communication layers can be arbitrarily selected as long as there are a plurality of communication layers to be connected.

In each embodiment, for convenience of explanation, 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. IrSimple is an improvement on some of the functions of conventional IrDA. The present invention is not limited to wireless communication using infrared rays, but is effective in other wireless communication and wired communication.

In each embodiment, in accordance with IrSimple, the data link layer, network layer, transport layer, session layer + presentation layer may be expressed as LAP, LMP, SMP, and OB EX, respectively. [0051] Hereinafter, each embodiment of the communication method, the communication program, the recording medium, the communication device, and the communication system according to the present invention will be described with reference to FIGS. 1 to 59 (FIGS. 7 to 9, FIG. 14, FIG. 21, FIG. 22, FIG. 27 and FIG. 28 are explanatory diagrams of the prior art).

As for the communication apparatus according to the present invention, as shown in FIG. 2, an object is exchanged from a client device (communication device) 1 as a communication device to a server device 5 as a counterpart device by infrared as a medium. The transfer method (transmission method) conforming to IrDA will be described as an example. However, the present invention is not limited to this.

[0053] Examples of the client device 1 include a computer, a mobile phone, a personal digital assistant (PDA), and a digital camera. Examples of the Sano device 5 include a television (TV), a printer, a projector, a computer, a mobile phone, a personal digital assistant (PDA), and a digital camera.

[0054] Examples of the medium include, in addition to infrared rays, radio waves used for cellular phones such as 100 MHz to 5 GHz, visible light using an optical fiber as a transmission path, and the like. Data that can be used for object exchange includes image files and text data.

[First Embodiment]

The client device 1 as the first embodiment according to the present invention is described below with reference to FIG. Note that the terms (including members and functions) defined in other embodiments are used in accordance with the definitions in this embodiment unless otherwise specified.

FIG. 1 is a block diagram showing a configuration of client device 1 of the communication system in the present embodiment. As shown in FIG. 1, the client device 1 includes an application layer processing unit 11, an OBEX layer processing unit (object exchange layer processing unit) 12, a lower layer processing unit 13, a transmission unit 14 and a reception unit 15. It has. The application layer processing unit 11, the OBEX layer processing unit 12, and the lower layer processing unit 13 are a plurality of types of communication protocols having a hierarchical structure in this order.

[0057] The application layer processing unit 11 requests the OBEX layer processing unit 12 to issue a request command for communication with the outside in response to a user instruction input to an operation unit (not shown). Also, when receiving a notification from the OBEX layer processor 12 that a response command has been received Then, predetermined processing is performed in accordance with the received response command.

The OBEX layer processing unit 12 includes a control unit 121, a request notification unit 122, and a response reception unit 123. In response to a request from the application layer processing unit 11, the control unit 121 notifies (controls) the request notification unit 122 to generate a request command and issue the request command to a lower layer. Also, upon receiving the response command reception result notification from the response receiving unit 123, the application layer processing unit 11 is notified of the response command reception result.

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

[0060] The lower layer processing unit 13 includes a control unit (lower layer control unit) 131, a request receiving unit 132, a request notification unit 133, and a response generation unit 134. The control unit 131 controls each block of the request reception unit 132, the request notification unit 133, and the response generation unit 134. Details will be described later.

[0061] The request receiving unit 132 receives the request command output from the OBEX layer processing unit 12, analyzes the request command, and notifies the control unit 131 that the command analysis result and the request command are received. Notification of. In addition, the request command which is the received data is transmitted to the request notification unit 133.

[0062] The request notification unit 133 receives the request command issuance notification from the control unit 131 based on the command analysis result and the reception of the request command, and receives the request command that is the data received from the request reception unit 132. In response to this, the request command is regenerated by adding the necessary header information, and transmitted to the transmitter 14.

[0063] The transmission unit 14 transmits the request command received from the lower layer processing unit 13 to the outside via the infrared communication path. The receiving unit 15 receives a response command transmitted from the counterpart device (server device) indicating that the request command has been received via the infrared communication path, and sends the received response command to the lower layer processing unit 13. Output.

[0064] As shown in FIG. 3, in the case where the Sano device 5 does not have a transmission unit or has a transmission unit 54, the transmission unit 14 also responds to the request command transmitted to the server device 5. For example, the response command may not be returned because at least a part of the response notification unit or the response transmission unit is lacking. In data communication with the server device 5 in these cases, inconvenience may occur if object exchange between the client device 1 and the server device 5 becomes impossible.

Therefore, in this embodiment, in order to avoid the inconvenience, a response generation unit 134 is separately provided in the lower layer processing unit 13. The response generation unit 134 receives the response command generation notification from the control unit 131 based on the reception of the command analysis result and the request command in the request reception unit 132, and receives a pseudo response corresponding to the response command. A command is generated and output to the OBEX layer processing unit 12 via the response receiving unit 123 which is an upper layer.

Thus, in the present embodiment, the server device 5 that cannot return the response command does not receive the original response command, but by receiving the pseudo response command to the upper layer processing unit, The communication state from the client device 1 to the server device 5 can be maintained while conforming to the communication protocol of the client device, and the object can be transmitted from the client device 1 to the server device 5.

Such a server device 5 will be described below with reference to FIG. The server device 5 has at least an application layer processing unit 51, an OBEX layer processing unit 52, a lower layer processing unit 53, and a receiving unit 55.

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

Further, the request analysis unit 525 removes the OBEX header from the received request command, and outputs application data to the application layer processing unit 51 based on an instruction from the control unit 521. The control unit 521 notifies the analysis result notified from the request analysis unit 525 to the application layer processing unit 51, and forwards the application data to the request analysis unit 525 to the application layer processing unit 51 based on the analysis result. To instruct.

The lower layer processing unit 53 includes a control unit 531 and a request analysis unit 535. Requirements analysis The unit 535 analyzes the request command from the client device 1 output from the receiving unit 55, and notifies the control unit 531 of the analysis result (command type, etc.).

Further, the request analysis unit 535 removes header information added in each layer from the received request command, extracts an OBEX packet, and based on a transfer instruction from the control unit 531, the OBEX layer processing unit The OBEX packet data extracted to 52 is output.

[0072] The control unit 531 notifies the OBEX layer processing unit 52 of the analysis result notified from the request analysis unit 535, and the OBEX packet data extracted by the request analysis unit 535 based on the analysis result. The OBEX layer processing unit 52 is instructed to transfer.

Next, a procedure (communication method) of data transfer processing between the client and the server in the embodiment of the present invention will be described with reference to the sequence of FIG. 4 and FIG. Figure 4 shows the connection, data transfer, and disconnect transfer processing in the IrDA protocol stack.

[0074] The application layer processing unit 11 that has received a user-powered object exchange instruction from the client device 1 connects the OBEX layer processing unit 12 to the server device 5 that is the counterpart device. Make a request.

Upon receiving the connection request, the control unit 121 in the OBEX layer processing unit 12 receives the connection request from the application layer processing unit 11, generates a connection request command to the request notification unit 122, and generates a lower layer processing unit 13. Command to issue a connection request command to

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

In response to the notification of the completion of reception of the connection request command from the request reception unit 132, the control unit 131 instructs the request notification unit 133 to issue a connection request command. Upon receiving an instruction to issue a connection request command from the control unit 131, the request notification unit 133 adds header information to the data received from the request reception unit 132 and outputs a connection request command to the transmission unit 14. Notify connection request command output completion to 1. Upon receiving the notification of the completion of the connection request command output from the request notification unit 133, the control unit 131 instructs the response generation unit 134 to issue a pseudo response command corresponding to the response command for the CONNECT command. .

[0079] In response to the pseudo response command issuance instruction for the CONNECT command from the control unit 131, the response generation unit 134 generates a SUCCESS pseudo response command that is a response command to the CONNECT command conforming to the OBEX standard that is the upper layer. And output to the OBEX layer processing unit 12.

[0080] The response receiving unit 123 in the OBEX layer processing unit 12 receives the SUCCESS pseudo response command output from the lower layer processing unit 13, and the pseudo response command is a response to the CONNECT command conforming to the normal OBEX standard. Recognizing the command, the control unit 121 is notified of the completion of receiving the response command in response to the connection request.

[0081] Upon receiving the notification of the completion of the response command reception for the connection request from the response receiving unit 123, the control unit 121 has completed the connection with the server device 5 that is the counterpart device to the application layer processing unit 11 that is the upper layer. Notify that. Thus, the application layer processing unit 11 can confirm that the connection with the server device 5 has been completed, and can start object exchange.

Here, as the lower layer processing unit 13, the power of expressing each layer of the TinyTP layer, the IrLMP layer, and the IrLAP layer as one block, of course, each layer may constitute one block. Also, in FIG. 4, the force illustrated in the TinyTP layer located immediately below the OBEX layer processing unit 12 to generate a pseudo response command to the OBEX layer processing unit 12 is IrLMP layer, IrLAP which is the other layer. You can generate pseudo response commands in layers!

[0083] However, generating a pseudo-response command for the OBEX layer processing unit 12 in the TinyTP layer located immediately below the OBEX layer processing unit 12 adds extra header information. It is preferable to save the time and trouble of deletion. That is, when generated in the TinyTP layer, a pseudo response command corresponding to a response command conforming to OBEX (substantially the same) may be generated and notified to the OBEX layer processing unit 12. Since it is necessary to generate a pseudo-response command that is transparent to the OBEX layer processing unit 12, the header information suitable for the protocol layer between the OB EX layer and the layer that generates the pseudo-response command is as follows: As shown in Table 1, it is necessary to add to the above pseudo response command.

[0084] [Table 1]

After the connection is completed, the PUT command for transferring object data and the DISCONNECT command for disconnection processing with the other device are also located at the lower level of the OBEX layer processing unit 12 as in the case of the CONNECT command. By generating a pseudo-response command such as CONTINUE or SUCCESS for the request command in the lower layer processing unit 13, it is possible to transfer the object data to the server device 5, which is the counterpart device, and to disconnect from the server device 5. Since it is clear, I will omit explanations about them here.

[0085] As described above, the client device 1 according to the present embodiment communicates using a communication protocol having a hierarchical structure, and responds to a request command transmitted by the client device 1 that requests a command. The communication system adopts an object exchange protocol for exchanging objects by receiving a response command returned from the server device that responds in response to the request. When a request command issued by the object exchange protocol is received in a communication protocol located in a lower layer of the protocol for use, a pseudo response command to the request command conforming to the object exchange protocol is sent. It has a function to generate and notify the object exchange protocol, which is a higher layer.

[0086] Therefore, object exchange with server device 5, which is a device having a minimum reception function that does not have a transmission function without changing a protocol for performing an object exchange by a request command Z response command, is performed. It becomes possible. In addition, it is not necessary to change the object exchange protocol, so existing assets can be used.

Next, an example of a data structure used in the communication protocol will be described. This data structure example can also be applied to the embodiments described later. First, the data structure of the request command in the case of a connection request is shown in Table 2 below. [0088] [Table 2]

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

(Description of each field)

• connect packet length, connect response packet length: Packet length of response command to connection request command and connection request command.

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

• flags: Indicates whether multiple IrLMP connections are supported only for response commands.

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

Next, Table 4 below shows examples of request commands and response commands.

[0091] [Table 4] Client request: Bytes Meaning

Opcode 0x80 CONNECT

0x0007 packet length of 7

0x10 Vers ion 1. 0 of OBEX

0x00 no connect f l ags

0x2000 8K max packet s i ze

Server response: Bytes Meaning

response code OxAO SUCCESS

0x0007 packet l ength of 7

0x10 Vers ion 1. 0 of OBEX

0x00 no connect flags

Table 5 below shows the data structure of the request command in the case of 0x0800 2K max packet size and data transfer request.

[0092] [Table 5]

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

[0093] [Table 6]

Next, the description of each field described in Table 5 and Table 6 above is shown below. • packet length, Response packet length: Packet length of data transfer command and response command to data transfer command.

Next, examples of request commands and response commands described in Table 5 and Table 6 are shown in Table 7 and Table 9 below, respectively.

[0095] [Table 7] Client request: Bytes Meaning

0x02 PUT

0x0422 1058 bytes is length of packet

0x01 Header ID for Name header

0x0017 Length of Name header

JUMAR. TXT name of object

0xC3 Header ID for Length header

Opcode

0x00001000 Length of object is 4K bytes

Header ID for Object Body Chunk

0x48

header

Length of Body header (IK) plus

0x0403

Header ID and Header length

Ox IK bytes of body

Server response:

0x90 CONTINUE

response code

0x0003 length of response packet

[Table 8]

[Table 9]

Continue !, according to the data structure of the request command in case of data disconnection request Table 10 shows,

[0096] [Table 10]

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

[0097] [Table 11]

The explanation of each field described in Table 10 and Table 11 is shown below. • packet length, response packet length: Packet length of response command to disconnection request command and disconnection request command.

Next, examples of request commands and response commands described in Table 10 and Table 11 are shown in Table 12 below.

[0099] [Table 12]

Finally, typical Opcode, Header, and Response Code in OBEX are shown in Table 13 to Table 15 below.

[Table 13] • OBEX Operations and Opcode definitions

[Table 14]

• OBEX Headers

[Table 15]

• Response Code values

[Second Embodiment]

The client device (communication device) of the transfer data transfer system (communication system) according to the second embodiment of the present invention is described below with reference to FIG. Note that the terms (including members and functions) defined in the other embodiments are used in accordance with the definitions in this embodiment unless otherwise specified.

FIG. 5 is a block diagram showing the configuration of the client device in the present embodiment. As shown in FIG. 5, the client device (communication device) 2 has the same function as the client device 1 of FIG. Are provided with an application layer processing unit 21, an OBEX layer processing unit (object exchange layer processing unit) 22, a lower layer processing unit 23, a transmission unit 24, and a reception unit 25.

The application layer processing unit 21 requests the OBEX layer processing unit 22 to issue a request command in response to a user instruction input to an operation unit (not shown). Also, when receiving a notification that the response command has been received from the OBEX layer processing unit 22, In response, predetermined processing is performed.

[0104] The OBEX layer processing unit 22 includes a control unit 221, a request notification unit 222, and a response reception unit 223. In response to a request from the application layer processing unit 21, the control unit 221 notifies the request notification unit 222 to generate a request command and issue a request command to a lower layer. In response to the response command reception result notification from the response receiving unit 223, the application layer processing unit 21 is notified of the response command reception result.

Upon receiving the request command issuance notification from the control unit 221, the request notification unit 222 generates a request command and outputs it to the lower layer processing unit 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 that the command analysis result and the response command have been received. Make a notification.

The lower layer processing unit 23 includes a control unit (lower layer control unit) 231, a request reception unit 232, a request notification unit 233, a response reception unit 234, a response notification unit 235, and a response generation unit 236. And a multiplexer 237 and a timer 238.

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

[0108] 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 that the command analysis result and the request command have been received. Do. At this time, when the control unit 231 receives the notification, the control unit 231 activates the timer 238. The timer 238 measures the elapsed time after the operation.

Also, the received data is output to request notification section 233. Upon receiving the request command issuance notification from the control unit 231, the request notification unit 233 generates a request command by adding necessary header information and outputs the request command to the transmission unit 24.

[0110] The response receiving unit 234 receives the data from the lower layer receiving unit 25, analyzes the received data, and notifies the control unit 231 that the command analysis result and the response command have been received. Do. Also, the received response command power header information is removed and output to the multiplexer 237.

[0111] The response notifying unit 235 sends the response command output from the multiplexer 237 to the OBEX layer process. Output to the physical unit 22. The response generation unit 236 receives the response command generation notification from the control unit 231, generates a pseudo response command similar to that of the first embodiment described above, and transmits the pseudo response command to the multiplexer 237.

[0112] The multiplexer 237 switches the output of the pseudo response command generated by the response generation unit 236 or the response command from the lower layer output from the response reception unit 234 in accordance with the control signal from the control unit 231. And output to the response notification unit 235. The timer 238 is used by the control unit 231 to measure a predetermined elapsed time.

That is, when the control unit 231 receives a command analysis result and a notification that the request command has been received from the request reception unit 232, the control unit 231 activates the timer 238 to measure (measure) the elapsed time. After receiving the notification, when the elapsed time has passed a preset time, when the command analysis result from the response receiving unit 234 and the notification that the response command has been received are not received, the pseudo response The response generation unit 236 and the multiplexer 237 are controlled so as to output the command to the response notification unit 235.

[0114] The transmission unit 24 transmits the request command received from the lower layer processing unit 23 to the outside via the infrared communication path. The receiving unit 25 receives the response command transmitted from the counterpart device (server device) via the infrared communication path, and outputs the received response command to the lower layer processing unit 23.

Next, a procedure (communication method) of data transfer processing between client servers in the second embodiment of the present invention will be described with reference to the sequence of FIG. 6 and FIG. Figure 6 shows the connection, data transfer, and disconnection transfer processing in the IrDA protocol stack.

In the client device 2, the application layer processing unit 21 that has received an object exchange instruction with user power makes a connection request to the server device 5, which is the counterpart device, to the OBEX layer processing unit 22.

[0117] Upon receiving the connection request, the control unit 221 in the OBEX layer processing unit 22 receives the connection request from the application layer processing unit 21 and generates a connection request command to the request notification unit 222 and the lower layer processing unit 23. Command to issue a connection request command to

[0118] The request notification unit 222 receives the connection request command issuance instruction from the control unit 221 and connects. A CONNECT command is generated as a request command, and a CONNECT command is output to the lower layer processing unit 23. The request receiving unit 232 in the lower layer processing unit 23 receives the CONNECT command output from the OBEX layer processing unit 22, notifies the control unit 231 that the connection request command has been received, and sends the received data to the request notification unit 233. Output.

In response to the notification of the completion of reception of the connection request command from the request reception unit 232, the control unit 231 instructs the request notification unit 233 to issue a connection request command. Upon receiving an instruction to issue a connection request command from the control unit 231, the request notification unit 233 adds header information to the data received from the request reception unit 232 and outputs a connection request command to the transmission unit 24. Notify connection request command output completion to 1.

The control unit 231 receives the notification of the connection request command output completion from the request notification unit 233, and starts the timer 238. When the measurement time in the timer 238 exceeds a predetermined set time, the control unit 231 determines that a response command from the server device 5 which is the counterpart device is not returned, and sends a response to the CONNECT command to the response generation unit 236. An instruction is issued to issue a pseudo-response command, and the multiplexer 237 is controlled to output a pseudo-response command corresponding to the CONNECT command output from the response generation unit 236 to the response notification unit 235.

[0121] The response generation unit 236 receives a pseudo response command issuance command for the CONNECT command from the control unit 231 and generates a SUCCESS pseudo response command for the CONNECT command conforming to the OBEX standard, which is the upper layer. Output to multiplexer 237.

[0122] If a response command is returned from the server that is the counterpart device before the measurement time of the timer 238 passes the predetermined time, the receiving unit 25 also outputs the counterpart device power. Data (including the response command) is received and output to the lower layer processing unit 23.

[0123] The response receiving unit 234 in the lower layer processing unit 23 analyzes the data received from the receiving unit 25, notifies the control unit 231 that the response command has been received in response to the connection request, and removes the header information. The received data is output to the multiplexer 237.

[0124] The control unit 231 receives a response command reception completion notification for the connection request from the response reception unit 234, and notifies the multiplexer 237 of the output data from the response reception unit 234. Control to output to part 235. The multiplexer 237 switches the output of the reception data from the response reception unit 234 and the response generation unit 236 based on the control signal from the control unit 231, and outputs it to the response notification unit 235.

In response to the notification of response command issuance from the control unit 231, the response notification unit 235 outputs the response command received from the multiplexer 237 to the OBEX layer processing unit 22 that is an upper layer. The response receiving unit 223 in the OBEX layer processing unit 22 receives the response command for the CONNECT command of the lower layer power, and notifies the control unit 221 of the completion of the response command reception for the CONNECT command.

Upon receiving the response command reception completion notification for the CONNECT command from the response receiving unit 223, the control unit 221 notifies the application layer processing unit 21, which is a higher layer, that the connection with the counterpart device has been completed. In this way, the application layer processing unit 21 can confirm that the connection with the counterpart device (server device) is completed, and can start object exchange.

Here, as the lower layer processing unit 23, the power expressing each layer of the TinyTP layer, the IrLMP layer, and the IrLAP layer as one block, of course, each layer may constitute one block. In addition, in FIG. 6, the force illustrated in the TinyTP layer located immediately below the OBEX layer processing unit 22 to generate a pseudo response command to the OBEX layer processing unit 22 is IrLMP layer and IrLAP layer which are other layers. You may generate pseudo response commands for any of these! / However, in the TinyTP layer located one level below the OBEX layer processing unit 12, generating a pseudo-response command for the OBEX layer processing unit 12 can be done by adding and deleting extra header information as described above. This is preferable because it saves time and effort.

[0128] After the connection is completed, the PUT command for transferring object data and the DISCONNECT command for disconnection processing with the other device are also requested in the lower layer of the OBEX layer, as in the case of the CONNECT command. By generating a pseudo-response command for the command, it is possible to perform object data transfer and disconnection processing with the other device, so the explanation is omitted here.

[0129] As described above, the client device 2 according to the present embodiment uses the object exchange protocol according to the communication protocol positioned in the lower layer of the object exchange protocol. After a request command issued by a server is issued to a communication protocol located in a lower layer, a response response to the request command from the server device, which is the partner device, is not received when a predetermined set time has elapsed. When receiving, it has a function of generating a pseudo-response command for the request command conforming to the object exchange protocol and notifying the object exchange protocol, which is an upper layer.

[0130] Therefore, in communication with a server device having a transmission function, it is possible to perform off-object exchange using the conventional request command Z response command. In communication with the server device 5 that does not have a transmission function, the lower layer is used. By generating a pseudo-response command and notifying it to the upper layer, communication between the client device 2 and the Sano device 5 can be started and maintained, and object exchange between the two can be performed. It becomes possible.

[Third Embodiment]

The client device (communication device) of the transfer data transfer system (communication system) according to the third embodiment of the present invention is described below with reference to FIG. Note that the terms (including members and functions) defined in the other embodiments are used in accordance with the definitions in this embodiment unless otherwise specified.

FIG. 10 is a block diagram showing the configuration of the client device in the present embodiment. As shown in FIG. 10, the client device (communication device) 3 has the same function as the client device 1 in FIG. Each includes an application layer processing unit 31, an OBEX layer processing unit (object exchange layer processing unit) 32, a lower layer processing unit 33, a transmission unit 34, and a reception unit 35.

The application layer processing unit 31 requests the OBEX layer processing unit 32 to issue a request command in response to a user instruction input to an operation unit (not shown). In addition, when a notification indicating that a response command has been received is received from the OBEX layer processing unit 32, predetermined processing is performed in accordance with the received response command.

The OBEX layer processing unit 32 includes a control unit 321, a request notification unit 322, and a response reception unit 323. In response to a request from the application layer processing unit 31, the control unit 321 generates a request command to the request notification unit 322 and issues a request command to a lower layer (connection request, data transfer request, final data transfer request , Disconnect request, etc.). Also In response to the response command reception result notification from the response receiving unit 323, the application layer processing unit 31 is notified of the response command reception result.

Upon receiving the request command issuance notification from the control unit 321, the request notification unit 322 generates a request command and outputs it to the lower layer processing unit 33. The response receiving unit 323 receives the response command output from the lower layer processing unit 33, analyzes the received response command, and controls the control unit 32.

1 is notified that the command analysis result and the response command have been received.

The lower layer processing unit 33 includes a control unit (lower layer control unit) 331, a request reception unit 332, a request notification unit 333, a response reception unit 334, a response notification unit 335, and a response generation unit 336. And a multiplexer 337.

[0137] The control unit 331 includes a request reception unit 332, a request notification unit 333, a response reception unit 334, and a response notification unit.

Each block of 335, response generation unit 336, and multiplexer 337 is controlled. Details will be described later.

[0138] The request receiving unit 332 receives the request command from the OBEX layer processing unit 32, analyzes the command, and notifies the control unit 331 that the command analysis result and the request command have been received. Do.

In addition, request reception unit 332 outputs the received data to request notification unit 333. Upon receiving a request command issue notification from the control unit 331, the request notification unit 333 generates a request command by adding necessary header information, and outputs the request command to the transmission unit 34.

[0140] The response receiving unit 334 receives the data from the lower layer receiving unit 35, analyzes the received data, and notifies the control unit 331 that the command analysis result and the response command have been received. Do. Also, the received response command power header information is removed and output to the multiplexer 337.

[0141] Response notifying section 335 outputs the response command output from multiplexer 337 to OBEX layer processing section 32.

[0142] Upon receiving the response command generation notification from the control unit 331, the response generation unit 336 generates a pseudo response command similar to that in the first embodiment and the second embodiment described above, and the multiplexer 337 Send to.

In response to the control signal from the control unit 331, the multiplexer 337 receives the response from the response generation unit 336. The generated pseudo response command or the output of the response command from the lower layer output from the response receiving unit 334 is switched and output to the response notifying unit 335.

[0144] The control unit 331 has the power to receive a response command to the request command transmitted by the server device in response to the request command issue notification issued from the upper layer OBEX layer processing unit 32, OBEX Generates a pseudo response command corresponding to a response command to a request command conforming to the standard, and determines whether to notify the OBEX layer. In other words, the control unit 331 determines whether or not the server device capability depends on the type of request command issued notification request issued from the OBEX layer processing unit 32 (connection request, data transfer request, final data transfer request, disconnection request, etc.). A process for switching the power to receive a response command to the request command to be transmitted and whether to output a response command generation notification to the response generation unit 336 is performed.

[0145] When a response command to the request command for which the determination result is also transmitted by the Sano device is received, the response reception unit 334 receives the response command from the server device received from the reception unit 35 as a response notification unit. The multiplexer 337 is controlled to output to 335. When the determination result generates a pseudo response command, the response generation unit 336 and the multiplexer 337 are controlled so that the pseudo response command is output to the response notification unit 335.

[0146] The transmission unit 34 transmits the request command received from the lower layer processing unit 33 to the outside via the infrared communication path. The receiving unit 35 receives the response command transmitted from the counterpart device (server device) via the infrared communication path, and outputs the received response command to the lower layer processing unit 33.

Next, a procedure (communication method) of data transfer processing between client servers in the third embodiment of the present invention will be described with reference to the sequence of FIG. 12 and FIG. Fig. 12 shows the connection, data transfer, and disconnect transfer processing in the IrDA protocol stack.

[0148] In the client device 3, the application layer processing unit 31 that has received an object replacement instruction from the user has requested the OBEX layer processing unit 32 to make a connection request, data transfer request, Disconnect requests are made sequentially. [0149] Upon receiving the above request, the control unit 321 in the OBEX layer processing unit 32 receives the request from the application layer processing unit 31, and sends a request command (connection request, data transfer request, final data) to the request notification unit 322. (Transfer request, disconnection request, etc.) and issuing a request command to the lower layer processing unit 33.

In response to the request command issuance instruction from the control unit 321, the request notification unit 322 generates a request command and outputs the request command to the lower layer processing unit 33. The request receiving unit 332 in the lower layer processing unit 33 receives the request command output from the OBEX layer processing unit 32, notifies the control unit 331 that the request command has been received, and outputs the received data to the request notification unit 333. Do

[0151] In the control unit 331, in response to the control signal notified from the OBEX layer processing unit 32, the power to receive a response command to the request command transmitted by the server device power, the request command conforming to the OBEX standard Generates a pseudo-response command corresponding to the response command to and determines whether to notify the OBEX layer. Here, the control unit 331 requests the command transmitted from the server device in accordance with the type of request command notified from the OBEX layer processing unit 32 (connection request, data transfer request, final data transfer request, disconnection request, etc.). Whether to output a response command generation notification to the response generation unit 336 is determined.

[0152] In this embodiment, when a data transfer request notified from an upper layer is not a final data transfer request at the time of data transfer, a pseudo command corresponding to a response command corresponding to a request command compliant with the OBEX standard is used. A response command is generated and notified to the OBEX layer. In other words, SUCCE SS response commands issued at the time of a connection request, disconnection request, and final data transfer request are received by the response command output from the server device, and the CONTINUE response command is equivalent to that. Generate a pseudo response command to notify the OBEX layer.

In response to the notification of request command reception completion from the request reception unit 332, the control unit 331 instructs the request notification unit 333 to issue a request command. Upon receiving an instruction to issue a request command, the request notification unit 333 adds header information to the data received from the request reception unit 332, outputs the request command to the transmission unit 34, and outputs the request command to the control unit 331. Request command Notification of output completion.

[0154] The control unit 331 receives the notification of the completion of the request command output from the request notification unit 333, and in the case of data transfer, when the data transfer request notified from the upper layer is not the final data transfer request, The response generation unit 336 is instructed to issue a CONTINUE response command, which is a pseudo response command for the PUT command, and the multiplexer 337 is supplied with a CONTINU E that is a pseudo response command for the PUT command output from the response generation unit 336. Control to output a response command to the response notification unit 335.

[0155] In response generation unit 336, in response to an instruction to issue a CONTINUE response command that is a pseudo response command to the PUT command from control unit 331, a pseudo response command of a CONTINUE command to a PUT command that conforms to the OBEX standard, which is an upper layer, Is output to the multiplexer 337.

[0156] When the control unit 331 receives a connection request, a disconnection request, or a final data transfer request from an upper layer, it responds with a normal reception process, that is, a response command to the request command received from the server device. Control multiplexer 337 to output to notification unit 335

[0157] At this time, the response receiving unit 334 in the lower layer processing unit 33 analyzes the data received from the receiving unit 35, notifies the control unit 331 of the completion of reception of the response command for the request command, and stores the header information. The received data is output to the multiplexer 337.

The control unit 331 controls the multiplexer 337 to output the output data from the response receiving unit 334 to the response notifying unit 335 upon receipt of a response command reception completion notification for the connection request from the response receiving unit 334. The multiplexer 337 switches the output of the received data from the response receiving unit 334 and the response generating unit 336 based on the control signal from the control unit 331, and outputs the data to the response notifying unit 335.

In response to the notification of response command issuance from the control unit 331, the response notification unit 335 outputs the response command received from the multiplexer 337 to the OBEX layer processing unit 32 that is an upper layer. The response reception unit 323 in the OBEX layer processing unit 32 receives a response command for a request command having a lower layer capability, and notifies the control unit 321 of the completion of reception of the response command for the request command. [0160] Upon receiving a response command completion notification for the request command from the response receiver 323, the control unit 321 completes connection, data transfer, and disconnection to the application layer processing unit 31 that is the upper layer. Notify you. In this way, the application layer processing unit 31 can confirm that the connection, data transfer, and disconnection with the counterpart device (Sano << device) are completed, and the object exchange with the server device is completed.

Here, as the lower layer processing unit 33, the power expressing each layer of the TinyTP layer, the IrLMP layer, and the IrLAP layer as one block, of course, each layer may constitute one block. In addition, in FIG. 10, the force illustrated in the TinyTP layer located immediately below the OBEX layer processing unit 32 to generate a pseudo response command to the OBEX layer processing unit 32 is IrLMP layer and IrLAP layer which are other layers. You may generate pseudo response commands for any of these! / However, generating a pseudo-response command for the OBEX layer processing unit 32 in the TinyTP layer located one level below the OBEX layer processing unit 32, as described above, adds and deletes extra header information. This is preferable because it saves time and effort.

[0162] As described above, the client device 3 according to the present embodiment has a communication protocol located in a lower layer of the object exchange protocol and a lower layer of the layer corresponding to the object exchange protocol. The communication protocol located in the layer has the ability to receive a response to the request command from the counterpart device according to the type of the request command when the request command is issued. A function of generating a pseudo-response command corresponding to a response command to the request command compliant with the object exchange protocol and switching a force to notify a layer corresponding to the object exchange protocol which is an upper layer; The

[0163] Therefore, it is possible to ensure the reliability of communication by receiving only the minimum necessary response commands such as connection request, disconnection request, and final data transfer request. For the response command to the data transfer request other than the data transfer request, it is not necessary to perform reception processing, so the circuit scale can be reduced.

[Fourth Embodiment]

A client device (communication device) of a transfer data transfer system (communication system) according to the fourth embodiment of the present invention is described below with reference to FIG. Na Unless otherwise specified, terms (including members and functions) defined in other embodiments are used in accordance with the definitions in this embodiment.

FIG. 11 is a block diagram showing the configuration of the client device in the present embodiment. As shown in FIG. 11, client device (communication device) 4 has the same function as client device 1 in FIG. Each includes an application layer processing unit 41, an OBEX layer processing unit (object exchange layer processing unit) 42, a lower layer processing unit 43, a transmission unit 44, and a reception unit 45.

The application layer processing unit 41 requests the OBEX layer processing unit 42 to issue a request command in accordance with a user instruction input to an operation unit (not shown). In addition, when a notification indicating that a response command has been received is received from the OBEX layer processing unit 42, predetermined processing is performed in accordance with the received response command.

[0167] The OBEX layer processing unit 42 includes a control unit 421, a request notification unit 422, and a response reception unit 423. In response to a request from the application layer processing unit 41, the control unit 421 notifies the request notification unit 422 to generate a request command and issue a request command to a lower layer. In response to the response command reception result notification from the response receiving unit 423, the application layer processing unit 41 is notified of the response command reception result.

In response to the request command issuance notification from the control unit 421, the request notification unit 422 generates a request command and outputs it to the lower layer processing unit 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 42 1 that the command analysis result and the response command have been received. Make a notification.

[0169] The lower layer processing unit 43 includes a control unit (lower layer control unit) 431, a request reception unit 432, a request notification unit 433, a response reception unit 434, a response notification unit 435, and a response generation unit 436. And a multiplexer 437 and a header information analysis unit 438.

[0170] The control unit 431 controls each block of the request reception unit 432, the request notification unit 433, the response reception unit 434, the response notification unit 435, the response generation unit 436, the multiplexer 437, and the header information analysis unit 438. Do. Details will be described later.

[0171] The request reception unit 432 receives the request command from the OBEX layer processing unit 42, analyzes the command, and receives the command analysis result and the request command from the control unit 431. Make a notification to the effect. In addition, the received data is output to the header information analysis unit 438.

[0172] The header information analysis unit 438 analyzes the header information of the request command received from the request reception unit 432 and complies with the OBEX standard to receive a response command to the request command from the server device. A pseudo response command corresponding to a response command to the request command is generated, and it is determined whether to notify the upper layer OBEX layer processing unit 42, and the control unit 431 is notified of the determination result. The received data is output to the request notification unit 433.

In response to the request command issuance notification from the control unit 431, the request notification unit 433 generates a request command by adding necessary header information, and outputs the request command to the transmission unit 44.

[0174] When the response receiving unit 434 receives transmission data from the receiving unit 45, the response receiving unit 434 analyzes the received data and notifies the control unit 431 that the command analysis result and the response command have been received. Make a notification. Also, the header information is removed from the received response command and output to the multiplexer 437.

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

In response to the response command generation notification from the control unit 431, the response generation unit 436 generates a pseudo response command similar to that in the first embodiment described above, and transmits the pseudo response command to the multiplexer 437.

[0177] The multiplexer 437 switches between the pseudo response command generated by the response generation unit 436 or the output of the response command from the lower layer output from the response reception unit 434 according to the control signal from the control unit 431. And output to the response notifying unit 435.

[0178] The control unit 431 receives a command analysis result and a notification that the request command has been received from the request reception unit 432, and is transmitted based on the determination result notified from the header information analysis unit 438. When receiving a notification that a response command to the request command is received, the response receiving unit 434 outputs a response command received from the receiving unit 45 to the response notifying unit 435. To control. In addition, when the control unit 431 receives a notification that a pseudo response command is to be generated, the control unit 431 causes the response generation unit 436 and the multiplexer 437 to output the pseudo response command to the response notification unit 435. Control. That is, the control unit 331 is analyzed by the header information analysis unit 438. Depending on the header information, the server device power is able to receive a response command for the transmitted request command, generates a pseudo-response command corresponding to the response command for the request command compliant with the OBEX standard, and the OBEX layer The process of switching whether to notify is performed.

[0179] The transmission unit 44 transmits the request command received from the lower layer processing unit 43 to the outside via the infrared communication path. The receiving unit 45 receives the response command transmitted from the counterpart device (server device) via the infrared communication path, and outputs the received response command to the lower layer processing unit 43.

Next, the procedure (communication method) of data transfer processing between the client and server in the fourth embodiment of the present invention will be described with reference to the sequence of FIG. 12 and FIG. Fig. 12 shows the connection, data transfer, and disconnect transfer processing in the IrDA protocol stack.

[0181] In the client device 4, the application layer processing unit 41 that has received an object replacement instruction from the user has requested the OBEX layer processing unit 42 to make a connection request and data transfer request to the server device 5 that is the counterpart device. Then, the disconnection request is made sequentially.

[0182] Upon receiving the above request, the control unit 421 in the OBEX layer processing unit 42 receives the request from the application layer processing unit 41, generates a request command to the request notification unit 422, and sends it to the lower layer processing unit 43. Instructs issue of request command.

In response to a request command issuance instruction from the control unit 421, the request notification unit 422 generates a request command and outputs the request command to the lower layer processing unit 43. The request reception 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 reception of the request command, and sends the received data to the header information analysis unit 438. Output.

[0184] The header information analysis unit 438 analyzes the request command received from the request reception unit 432. For example, by analyzing the Opcode of the OBEX request command shown in Table 13 above, it is possible to receive a response command to the request command transmitted by the server device. Pseudo pseudo equivalent to the response command to the request command conforming to the OBEX standard A response command may be generated to determine whether to notify the OBEX layer. here Then, for CONNECT (0x80), DISCONNECT (0x81) and the last PUT (0x82) sent, the response command output from the server device is received, and for other PUT (0x02), OBEX A pseudo response command corresponding to the response command to the request command conforming to the standard is generated and notified to the OBEX layer. In other words, for the response command of SUCCESS, the response command output from the server device is received, and for the CONTINUE response command, a corresponding pseudo response command is generated and notified to the OBEX layer.

The control unit 431 receives a request command reception completion notification from the request reception unit 432 and instructs the request notification unit 433 to issue a request command. The request notification unit 433 receives an instruction to issue a request command as many as the control unit 431, adds header information to the data received from the request reception unit 432, outputs the request command to the transmission unit 44, and outputs the request command to the control unit 431. Request command Notify completion of output.

[0186] Upon receiving notification of the completion of the request command output from the request notification unit 433, the control unit 431 generates a pseudo response command corresponding to a response command to the request command conforming to the OBEX standard from the header information analysis unit 428. When receiving a notification to notify the OBEX layer, that is, when a PUT command (0x02) other than the last PUT transmitted from the OBEX layer is received, the response generation unit 436 To issue a CONTINUE response command that is a pseudo response command to the PUT command, and to the multiplexer 437, a response notification unit sends a CON TINUE response command that is a pseudo response command to the PUT command output from the response generation unit 436. Control to output to 435.

[0187] In response generation unit 436, upon receiving an instruction to issue a CONTINUE response command that is a pseudo response command to the PUT command from control unit 431, a pseudo response command of the CONTINUE command to a PUT command that conforms to the OBEX standard as the upper layer Is output to the multiplexer 437.

[0188] Also, the header information analysis unit 428 receives a notification to receive a response command that also outputs the server device power, that is, the OBEX layer power and others receive the CONNECT command, the DISCONNECT command, and the last PUT command transmitted. In such a case, the multiplexer 437 is controlled so as to perform normal reception processing. [0189] At this time, the response receiving unit 434 in the lower layer processing unit 43 analyzes the data received from the receiving unit 45, notifies the control unit 431 of the completion of receiving the response command for the request command, and The received data is output to the multiplexer 437.

The control unit 431 controls the multiplexer 437 to output the output data from the response receiving unit 434 to the response notifying unit 435 upon receiving a response command reception completion notification for the connection request from the response receiving unit 434. The multiplexer 437 switches the output of the reception data from the response reception unit 434 and the response generation unit 436 based on the control signal from the control unit 431, and outputs it to the response notification unit 435.

[0191] Upon receiving the response command issuance notification from the control unit 431, the response notification unit 435 outputs the response command received from the multiplexer 437 to the OBEX layer processing unit 42, which is the upper layer. The response receiving unit 423 in the OBEX layer processing unit 42 receives a response command for a request command having a lower layer capability, and notifies the control unit 421 of the completion of reception of the response command for the request command.

[0192] Upon receiving the response command reception completion notification for the request command from the response receiving unit 423, the control unit 421 notifies the application layer processing unit 41, which is a higher layer, that the connection with the counterpart device has been completed. . In this way, the application layer processing unit 41 can confirm that the connection, data transfer, and disconnection with the counterpart device (server device) are completed, and the object exchange with the server device is completed.

Here, as the lower layer processing unit 43, the power expressing each layer of the TinyTP layer, the IrLMP layer, and the IrLAP layer as one block, of course, each layer may constitute one block. In addition, in FIG. 12, the force illustrated in the TinyTP layer located immediately below the OBEX layer processing unit 42 to generate a pseudo-response command for the OBEX layer processing unit 42 is IrLMP layer and IrLAP layer which are other layers. You may generate pseudo response commands for any of these! / However, in the TinyTP layer located immediately below the OBEX layer processing unit 42, generating a pseudo-response command for the OBEX layer processing unit 42, as described above, eliminates the trouble of adding extra header information and deleting it. This is preferable because it saves time and effort.

[0194] As described above, the client device 4 according to the present embodiment uses the object exchange protocol according to the communication protocol positioned in the lower layer of the object exchange protocol. The communication protocol located in the lower layer of the layer corresponding to the protocol refers to the header information of the request command issued by the object exchange protocol power, and according to the type of the header information, The ability to receive a response command to a request command of a layer that generates a pseudo-response command corresponding to the response command to the request command conforming to the object exchange protocol and that corresponds to the object exchange protocol that is the upper layer. A function to switch whether to notify is provided.

[0195] Therefore, the reliability of communication can be ensured by receiving only the minimum necessary response commands such as connection request, disconnection request, and final data transfer request. For the response command to the data transfer request other than the data transfer request, it is not necessary to perform reception processing, so the circuit scale can be reduced.

[Fifth embodiment]

The server device (communication device) of the transfer data transfer system (communication system) according to the fifth embodiment of the present invention will be described below with reference to FIG. Note that the terms (including members and functions) defined in other embodiments are used in accordance with the definitions in this embodiment unless otherwise specified.

FIG. 13 is a block diagram showing a configuration of the server device according to the present embodiment. As shown in FIG. 13, the server device (communication device) 1000 includes at least an application layer processing unit 1010, an OB EX layer processing unit (object exchange layer processing unit) 1020, a lower layer processing unit 1030, and a receiving unit 105. Yes.

[0198] The application layer processing unit 1010 requests the OBEX layer processing unit 1020 for request command processing in accordance with a user instruction input to an operation unit (not shown). In addition, when a notification that the request command has been received is received from the OB EX layer processing unit 1020, predetermined processing is performed according to the received request command.

The OBEX layer processing unit 1020 includes a control unit 1021, a response notification unit 1022, and a request analysis unit 1025. The control unit 1021 notifies the response notification unit 1022 to generate a response command and issue a response command to the lower layer according to the request from the application layer processing unit 1010 and the analysis result from the request analysis unit 1025. . Also, upon receiving the request command reception result notification from the request analysis unit 10 25, the application layer processing unit 1010 is requested. Notify the reception result of the request command.

[0200] Upon receiving the response command issuance notification from the control unit 1021, the response notification unit 1022 generates a response command and outputs it to the lower layer processing unit 1030. The request analysis unit 1025 receives the request command output from the lower layer processing unit 1030, analyzes the received request command, and notifies the control unit 1021 that the command analysis result and the request command have been received. Do.

[0201] The lower layer processing unit 1030 includes a control unit (lower layer control unit) 1031, a response receiving unit 1032, and a request analysis unit 1035.

[0202] The control unit 1031 controls the response reception unit 1032 and the request analysis unit 1035. Details will be described later.

[0203] 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 that the command analysis result and the response command have been received. I do.

[0204] When the request analysis unit 1035 receives the transmission data of the client device from the reception unit 1050, the request analysis unit 1035 analyzes the received data and notifies the control unit 1031 that the command analysis result and the request command have been received. Make a notification. Also, the header information is removed from the received request command and output to the OBEX layer processing unit 1020.

[0205] Control unit 1031 receives a command analysis result and a notification that a response command has been received from response reception unit 1032, but does not transmit the received response command to the client device.

[0206] Receiving unit 1050 receives a request command transmitted from the counterpart device (client device) via the infrared communication path, and outputs the received request command to lower layer processing unit 1030.

Next, the operation of the control unit in the lower layer processing unit of the OBEX layer in the conventional server device will be described using the flowchart shown in FIG.

[0208] Step S11 is a step of determining whether or not a request command is received from the client. If there is a reception, go to step S12.

Transition to S 11 respectively. [0209] Step SI2 is a step of notifying the OBEX layer processing unit of the received request command. After the notification is completed, the process proceeds to step S13.

[0210] Step S13 is a step of determining whether or not a response command is received from the OBEX layer processing unit. If received, go to step S14.

, Transition to step S13 again.

[0211] Step S14 is a step of transmitting the above-mentioned OBEX layer response command to the client device. After completion of transmission, the process proceeds to step S11.

[0212] With the above operation, the lower layer processing unit of the OBEX layer in the conventional server device performs O

The BEX layer exchanges reception request commands and transmission response commands.

[0213] However, in the case of a communication that does not need to send a response command, the lower layer processing unit that performs the conventional operation has a step of sending a response command from the OBEX layer processing unit to the client device. The power for sending the response command is wasted.

In contrast, as shown in FIG. 15, the control unit 1 of the lower layer processing unit 1030 of the present embodiment.

031 is characterized by having no step of transmitting a response command. The operation of the control unit 1031 of the lower layer processing unit 1030 of the present embodiment will be described using the flowchart shown in FIG.

[0215] Step S21 is a step of determining whether or not a request command is received from the client. If received, go to step S22.

Transition to S21.

[0216] Step S22 is a step of notifying the OBEX layer processing unit 1020 of the received request command. After the notification is completed, the process proceeds to step S23.

Step S23 is a step of determining whether or not a response command has been received from the OBEX layer processing unit 1020. If received, the process goes to step S21. If not received, the process goes to step S23 again. Note that step S23 may not be provided, and after step S22 is completed, the process may proceed to step S21.

[0218] Through the above operation, a response command from the OBEX layer processing unit 1020 is sent to the lower layer processing unit 10.

It is possible to realize the control unit 1031 that 30 does not transmit. It is also possible to use a conventional OBEX layer processing unit that performs operations such as issuing response commands to request commands. This makes it possible to divert assets.

[0219] Next, FIG. 16 shows the exchange of commands between the client device and the server device in the present embodiment.

[0220] As shown in Fig. 16, in the server device 1000, even if it is issued from the OBEX layer processing unit 1020 to the TinyTP layer, which is a lower layer, even if it is issued to the TinyTP layer, which is a lower layer, it is a TinyTP that is a lower layer. The layer does not send the response command to the client device by not sending the response command to the lower layer. In FIG. 16, the TinyTP layer, which is one layer below the OBEX layer, is used as the lower layer processing unit 1030, and the ability to perform processing that does not send a response command to the lower layer. A similar control may be performed using a certain IrLMP layer or IrLAP layer as the lower layer processing unit 1030.

[Sixth embodiment]

The server device (communication device) of the transfer data transfer system (communication system) according to the sixth embodiment of the present invention will be described as follows. Note that terms (including members and functions) defined in other embodiments are used in accordance with the definitions in this embodiment unless otherwise specified.

FIG. 17 shows a configuration block diagram of the Sano device 1100 according to the present embodiment. The Sano device 1100 according to the present embodiment includes at least an application layer processing unit 1110, an OB EX layer processing unit 1120, a lower layer processing unit 1130, a transmission unit 1140, and a reception unit 1150.

[0223] The application layer processing unit 1110 requests the OBEX layer processing unit 1120 to perform request command processing in accordance with a user instruction input to an operation unit (not shown). In addition, when a notification indicating that the request command has been received is received from the OB EX layer processing unit 1120, predetermined processing is performed according to the received request command.

[0224] The OBEX layer processing unit 1120 includes a control unit 1121, a response notification unit 1122, and a request analysis unit 1125. The control unit 1121 notifies the response notification unit 1122 to generate a response command and issue a response command to the lower layer according to the request from the application layer processing unit 1110 and the analysis result from the request analysis unit 1125. . The requirements analysis section 11 In response to the request command reception result notification from 25, the reception result of the request command is notified to the application layer processing unit 1110.

In response to the response command issuance notification from the control unit 1121, the response notification unit 1122 generates a response command and outputs it to the lower layer processing unit 1130. The request analysis unit 1125 receives the request command output from the lower layer processing unit 1130, analyzes the received request command, and notifies the control unit 1121 that the command analysis result and the request command have been received. Do.

The lower layer processing unit 1130 includes a control unit (lower layer control unit) 1131, a response receiving unit 1132, and a request analysis unit 1135.

The control unit 1131 controls the response reception unit 1132 and the request analysis unit 1135. Details will be described later.

[0228] 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 that the command analysis result and the response command have been received. I do.

[0229] When the request analysis unit 1135 receives the transmission data of the client device from the reception unit 1150, the request analysis unit 1135 analyzes the reception data, and notifies the control unit 1131 that the command analysis result and the request command have been received. Make a notification. Also, the header information is removed from the received request command and output to the OBEX layer processing unit 1120.

[0230] The control unit 1131 receives a command analysis result and a notification that the response command has been received from the response reception unit 1132, but does not transmit the received response command to the client device.

[0231] Transmitting section 1140 transmits the response command received from lower layer processing section 1030 to the outside via the infrared communication path.

[0232] Receiving section 1150 receives the request command transmitted from the counterpart device (client device) via the infrared communication path, and outputs the received request command to lower layer processing section 1130.

Next, the operation of control section 1131 of lower layer processing section 1130 according to the present embodiment will be described using the flowchart of FIG. [0234] Step S31 is a step of determining whether the client device power is also the power that received the request command. If received, the process proceeds to step S32. If not received, the process proceeds to step S31 again.

[0235] In step S32, the OBEX layer processing unit 112 receives the request command received also by the client device capability.

This is a step to notify 0. After the notification is completed, the process proceeds to step S33.

Step S33 is a step of determining whether or not a response command is received from the OBEX layer processing unit 1120. If received, the process proceeds to step S34. If not received, the process proceeds again to step S33.

Step S34 is a step of analyzing the response command received from the OBEX layer processing unit 1120. After the analysis is completed, the process proceeds to step S35.

[0238] Step S35 is a step of determining whether or not the response command received from the OBEX layer processing unit 1120 is necessary to be transmitted to the client as a result of the analysis in step S34. If it is determined to be necessary, the process proceeds to step S36. If it is determined to be unnecessary, the process proceeds to step S31. In this step S35, for example, when a CONTINUE response command for the Put command in OBEX is not transmitted! And only the SUCCESS response command is transmitted, selection is performed.

Step S36 is a step of transmitting a response command to the client device. After completion of transmission, the process proceeds to step S31.

[0240] The lower layer processing unit 1130 of the server device 1100 performs the above operation, thereby enabling processing in which only a response command from a specific OBE X layer is not transmitted to the client device. In addition, assets can be diverted because it is possible to use the conventional OBEX layer processing unit that issues a response command to the request command.

[0241] Next, FIG. 19 shows the exchange of commands between the client device and the server device in the present embodiment.

[0242] As shown in the figure, in the server device 1100, a specific response command (request command CONTINUE in the figure) for a request command that has the power of the client device is issued from the 1S OBEX layer processing unit 1120 to the TinyTP layer that is the lower layer Even if it is, the TinyT P layer, which is a lower layer, does not notify the lower layer of the response command. On the other hand, a specific response command is not transmitted. In FIG. 19, the TinyTP layer, which is one layer below the OBEX layer, is used as the lower layer processing unit 1130, and the processing power is not transmitted to the lower layer. The same control may be performed using the IrLMP layer or the IrLAP layer which is the lower layer as the lower layer processing unit 1130.

[0243] Further, another operation of lower layer processing section 1130 will be described using the flowchart of FIG.

[0244] Step S41 is a step of determining whether the client device power is also the power that received the request command. If received, the process proceeds to step S42. If not received, the process proceeds to step S41 again.

Step S42 is a step of notifying the OBEX layer processing unit 1120 of the request command that has received the client device capability. After the notification is completed, the process proceeds to step S43.

Step S43 is a step of determining whether or not a response command has been received from the OBEX layer processing unit 1120. If received, the process proceeds to step S44. If not received, the process proceeds again to step S43.

[0247] Step S44 is a step of analyzing the header of the response command received from the OBEX layer processing unit 1120. What is done here is to determine whether it is a C ONTINUE response command for a Put command that is not final, for example, specifically, the first byte of the response command from the OBEX layer processing unit 1120 is CONTINUE (0x10 Or 0x90) to determine whether the force is SUCCESS (0x20 or OxAO). After the analysis is completed, the process goes to step S45.

[0248] Step S45 is a step of determining whether or not the response command received from the OBEX layer processing unit 1120 is required to be transmitted to the client as a result of the analysis in step S44. If it is determined to be necessary, the process proceeds to step S46. If it is determined to be unnecessary, the process proceeds to step S41. In this step S45, for example, when a CONTINUE response command for the Put command in OBEX is not transmitted !, only the SUCCESS response command is transmitted.

[0249] Step S46 is a step of transmitting a response command to the client device. After the transmission is completed, the process proceeds to step S41.

[0250] The lower layer processing unit 1130 of the server device 1100 performs the above operation, so that a specific OBE Processing that does not send only response commands from the X layer to the client device becomes possible. In addition, assets can be diverted because it is possible to use the conventional OBEX layer processing unit that issues a response command to the request command.

[0251] Also in the case of the operation of the lower layer processing unit 1130 shown in the flowchart of FIG. 20, the exchange of commands between the client device and the server device has the sequence shown in FIG.

That is, as shown in FIG. 19, in the server device 1100, a specific response command to the request command from the client device (response command CONTINUE in the figure) is sent from the OBEX layer processing unit 1120 to the lower layer TinyTP. Even if it is issued to a layer, the TinyTP layer, which is a lower layer, does not send the response command to the lower layer, thereby preventing a specific response command from being sent to the client device is doing. In FIG. 19, the TinyTP layer, which is one layer below the OBEX layer, is used as the lower layer processing unit 1130. The same control may be performed by using a certain IrLMP layer or IrLAP layer as the lower layer processing unit 1130.

[Seventh Embodiment]

The client device (communication device) of the transfer data transfer system (communication system) according to the seventh embodiment of the present invention will be described as follows. Note that terms (including members and functions) defined in other embodiments are used in accordance with the definitions in this embodiment unless otherwise specified.

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

As shown in FIG. 21, a conventional client device (communication device) 1200 includes an application layer processing unit 1210, an OBEX layer processing unit (object exchange layer processing unit) 1220, a lower layer processing unit 1230, A transmission unit 1240 and a reception unit 1250 are provided at least.

[0256] The application layer processing unit 1210 requests the OBEX layer processing unit 1220 to issue a request command in response to a user instruction input to an operation unit (not shown).

[0257] The OBEX layer processing unit 1220 includes a control unit 1221, a request notification unit 1222, and a response reception unit 1223. And.

In response to a request from the application layer processing unit 1210, the control unit 1221 notifies the request notification unit 1222 to generate a request command and issue a request command to a lower layer. In response to the response command reception result notification from the response reception unit 1223, the response layer reception unit 1210 is notified of the response command reception result.

Upon receiving the request command issue notification from the control unit 1221, the request notification unit 1222 generates a request command and outputs it to the lower layer processing unit 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 that the command analysis result and the response command have been received. Do.

[0260] The lower layer processing unit 1230 adds an appropriate lower layer header to the request command from the OBEX layer processing unit 1220 and passes it to the transmission unit 1240, and also receives an appropriate response from the reception response command from the reception unit 1250. The lower layer header is removed and passed to the OBEX layer processing unit 1220.

[0261] The transmission unit 1240 transmits the request command received from the lower layer processing unit 1230 to the outside via the infrared communication path.

[0262] Reception unit 1250 receives the response command transmitted from the counterpart device (server device) via the infrared communication path, and outputs the received response command to lower layer processing unit 1230.

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.

[0264] Step S51 is a step for determining whether a request command to the server device has been issued to the application layer processing unit 1210 of the client device 1200 and the control unit 1221 of the OBEX layer processing unit 1220! It is. If it has occurred, the process proceeds to step S52. If it has occurred, the process proceeds to step S51 again.

Step S52 is a step of transmitting a request command to the server device to the lower layer processing unit 1230. After transmission ends, the process proceeds to step S53.

[0266] Step S53 is a step of determining whether or not a response command from the Sano device has been received from the lower layer processing unit 1230. If received, go to step S54. If received, go to step S53 again. [0267] Step S54 is a step of analyzing the received response command. After the analysis is completed, the process goes to step S55.

[0268] Step S55 is a step of determining whether or not the communication end power. If the communication has not ended, the process returns to step S51.

[0269] Through the above operation, the OBEX layer processing unit 1220 of the conventional client device 1200 can perform communication by issuing a request command, analyzing a response command to the request command, and issuing the next request command again. It becomes possible.

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

In order to solve this, as shown in the flowchart of FIG. 24, the client device 1300 according to the present embodiment (FIG. 23) issues a request command to the server device and then sends a response command from the server device. It is possible to issue the next request command without receiving. Specifically, it is as follows.

[0272] Step S61 is a step of determining whether a request command to the server device is generated in the application layer processing unit 1310 of the client device 1300 and the control unit 1321 of the OBEX layer processing unit 1320. If it has occurred, the process proceeds to step S62. If it has occurred, the process proceeds to step S61 again.

Step S62 is a step of transmitting a request command to the Sano device to the lower layer processing unit 1330. After transmission ends, the process proceeds to step S65.

[0274] Step S65 is a step of determining whether or not the communication end power. If the communication has not ended, the process returns to step S61.

[0275] The above operation is performed by the control unit 1321 of the OBEX layer processing unit 1320 of the client device 1300, so that a request command is transmitted from the client device 1300 and a response command from the server device is not received. The next request command can be transmitted.

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

[0277] OBEX layer processing unit (object exchange layer processing unit) Each block other than the communication direction selection unit 1324 of 1320 is the OBEX layer processing of the conventional client device 1200 described above with reference to FIG. Since it has the same function as each block of the logic unit 1220, description thereof is omitted.

[0278] The communication direction selection unit 1324 has a function of selecting whether the communication is one-way communication or two-way communication. One-way communication here refers to communication that does not require a response command from a server device in response to a request command that requires a client device. If the server device does not have a transmitter, or if the client device does not have a receiver, it will necessarily be one-way communication, but the client device and the Sano device each have a transmitter and receiver. However, if the signal flow is one-way to the client device power server device, it is still one-way communication. In addition, bidirectional communication is a communication method in which a server device transmits a response command to a request command to which the client device capability is also transmitted, and the client device transmits the next request command again after analyzing the response command. is there. In this case, if an agreement is made in advance in both the OBEX layer of the client device and the OBEX layer of the sano device that does not require a response command for every request command, a specific command can be used. Response command for request command is not always required!

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

[0280] Step S70 is a step in which the communication direction selection unit 1324 selects bidirectional communication or unidirectional communication. In the case of bidirectional communication, the process proceeds to step S71, and in the case of one-way communication, the process proceeds to S81.

Step S71 is a step of determining whether a request command to the server device is generated in the application layer processing unit 1310 or the control unit 1321 of the OB EX layer processing unit 1320 in bidirectional communication. If so, go to step S72. If not, go to step S71 again.

Step S72 is a step of transmitting a request command to the server device to the lower layer processing unit 1330 in bidirectional communication. After transmission ends, the process proceeds to step S73.

[0283] Step S73 is a step of determining whether or not a response command having a server device capability has been received in bidirectional communication. If received, the process proceeds to step S74. If not received, the process proceeds to step S73 again.

[0284] Step S74 analyzes the response command of server equipment in bidirectional communication. It is a step. After the analysis is completed, the process proceeds to step S75.

[0285] Step S75 is a step of determining whether or not to end communication in bidirectional communication. If not, the process returns to step S71.

On the other hand, in step S81, in the one-way communication, the application layer processing unit 1310 or the control unit 1321 of the OBEX layer processing unit 1320 determines whether a request command to the server device is generated. is there. If it has occurred, the process proceeds to step S82. If not, the process proceeds to step S81 again.

Step S82 is a step of transmitting a request command to the server device to the lower layer processing unit 1330 in the one-way communication. After transmission ends, the process proceeds to step S85.

[0288] Step S85 is a step of determining whether or not to end communication in one-way communication. If not, the process returns to step S81.

[0289] The above operation is performed by the control unit 1321 of the OBEX layer processing unit 1320 of the client device 1300, so that in bidirectional communication, a response command from the server device is waited for and the next request command is transmitted. In one-way communication, it is possible to send the next request command without receiving a response command with the server equipment.

[Eighth Embodiment]

The client device (communication device) of the transfer data transfer system (communication system) according to the eighth embodiment of the present invention will be described as follows. Note that terms (including members and functions) defined in other embodiments are used in accordance with the definitions in this embodiment unless otherwise specified.

FIG. 23 is a block diagram of the client device 1300 according to the present embodiment. That is, it is the same as the seventh embodiment described above, and the operation of each block other than the control unit 1321 of the OBEX layer processing unit 1320 is basically the same as the operation of each block in the seventh embodiment. Therefore, the description is omitted.

Operation of control unit 1321 of OBEX layer processing unit 1320 according to the present embodiment will be described using the flowchart shown in FIG.

[0293] Step S91 determines whether or not a Put request command to the server device has occurred in the control unit 1321 of the application layer processing unit 1310 or the OBEX layer processing unit 1320. This is a step to determine. If it has occurred, the process proceeds to step S92. If it has not occurred, the process proceeds to step S91 again.

[0294] Step S92 is a step of transmitting a Put request command to the Sano device. After completion of transmission, the process proceeds to step S93.

[0295] Step S93 is a step of determining whether the transmitted Put request command is not the final Put request command. If it is final, the process proceeds to step S94. If it is not final, the process proceeds to step S91.

[0296] Step S94 is a step of determining whether or not the force has received the response command from the Sano device. If received, go to step S95.

Transition to S94.

[0297] Step S95 is a step of analyzing a response command from the Sano device. After the analysis is completed, the process proceeds to step S96. At this time, the SUCC for the final Put request command

It will be determined whether or not the force has received the ESS response command.

[0298] Step S96 is a step of determining whether or not the communication is terminated. If not, the process returns to step S91.

[0299] The above operation is performed by the control unit 1321 of the OBEX layer processing unit 1320 of the client device 1300.

It is possible to send the next Put request command without waiting for the NUE response command.

It is possible to increase communication efficiency. In addition, since the client device 1300 confirms the SUCCESS response command from the server device in response to the final Put command, it is necessary to determine whether the client device 1300 can successfully transfer data to the server device. Is possible.

[0300] Also, as shown in Fig. 26, in combination with bidirectional communication and one-way communication switching by communication direction selection unit 1324, only the final Put command can be used during bidirectional communication.

SS response command is required, and during one-way communication, it is possible to perform all operations without requiring a response command for all request commands.

[0301] [Ninth embodiment]

The server of the transfer system (communication system) for transfer data according to the ninth embodiment of the present invention The following describes the device (communication device). Note that terms (including members and functions) defined in other embodiments are used in accordance with the definitions in this embodiment unless otherwise specified.

[0302] First, Fig. 27 shows a block diagram of a server device that performs communication using the conventional OBEX protocol.

[0303] As shown in FIG. 27, the Sano device (communication device) 1400 includes an application layer processing unit 14

10, OBEX layer processing unit (object exchange layer processing unit) 1420, lower layer processing unit 1430

The transmitter 1440 and the receiver 1450 are provided at least.

[0304] The application layer processing unit 1410 requests the OBEX layer processing unit 1420 to execute a reception request command process and a response command in response to a user instruction input to an operation unit (not shown).

[0305] The OBEX layer processing unit 1420 includes a control unit 1421, a response notification unit 1422, and a request analysis unit 1423.

In response to a request from application layer processing unit 1410, control unit 1421 notifies response notifying unit 1422 to generate a response command and issue a response command to a lower layer. In response to the request command reception result notification from the request analysis unit 1423, the application layer processing unit 1410 is notified of the request command reception result.

In response to the response command issue notification from control unit 1421, response notification unit 1422 generates a response command and outputs it to lower layer processing unit 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 that the command analysis result and the request command have been received. Do.

[0308] The lower layer processing unit 1430 adds an appropriate lower layer header to the response command from the OBEX layer processing unit 1420 and passes the response command to the transmission unit 1440, and from the reception request command from the reception unit 1450, an appropriate response is received. The lower layer header is removed and passed to the OBEX layer processing unit 1420.

[0309] The transmission unit 1440 transmits the request command received from the lower layer processing unit 1430 to the outside via an infrared communication path or the like.

[0310] Receiver 1450 transmits from partner device (client device) via infrared communication path The received request command is received, and the received request command is output to the lower layer processing unit 1430.

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

[0312] Step S101 is a step of determining whether or not the client device power is also the power that received the request command. If received, the process proceeds to step S102. If not received, the process proceeds to step S101 again.

[0313] Step S102 is a step of analyzing a request command for a client device.

After the analysis is completed, the process proceeds to step S103.

[0314] Step S103 is a step of creating a response command to the client device. After creating the response command, the process proceeds to step S104.

[0315] Step S104 is a step of transmitting the response command to the client device.

After completion of transmission, the process proceeds to step S105.

Step S105 is a step of determining whether or not to end communication. If not completed, the process returns to step S101.

[0317] With the above operation, the OBEX layer processing unit 1420 of the conventional server device 1400 can perform communication by receiving and analyzing the request command, and generating and transmitting a response command to the request command.

[0318] In the operation of the OBEX layer processing unit 1420 of the conventional server device 1400 described above, a response command is generated and transmitted in response to a request command from the client device. In communications that do not require transmission from the server device 1400, such as communications, the power used to generate response commands is wasted.

[0319] In order to solve this problem, as shown in the flowchart of FIG. 30, the server device 1500 (FIG. 29) according to the present embodiment receives and analyzes the request command of the client device, and then sends it to the client device. It is possible to receive the next request command immediately after generating and sending the response command. Specifically, it is as follows.

[0320] Step S111 is a step of determining whether or not a request command having a client device capability has been received. If received, go to step S112. If not received, The process transits again to step S111.

[0321] Step S112 is a step of analyzing the received request command. After the analysis is completed, the process proceeds to step S115.

[0322] Step S115 is a step of determining whether or not the communication has ended. If not completed, the process proceeds to step S111 again.

[0323] The above operation is performed by the control unit 1521 of the OBEX layer processing unit 1520 of the server device 1500, so that the next request command is received without generating or transmitting a response command to the received request command. It becomes possible.

Here, FIG. 29 is a block diagram of server device 1500 according to another embodiment of the present invention.

[0325] OBEX layer processing unit (object exchange layer processing unit) The blocks other than the communication direction selection unit 1524 of 1520 are the same as the blocks of the OBEX layer processing unit 1420 of the conventional server device 1400 described above with reference to FIG. Description is omitted because it has a function.

[0326] The communication direction selection unit 1524 has a function of selecting whether the communication is one-way communication or two-way communication. One-way communication here refers to communication that does not require a response command from a server device in response to a request command that requires a client device. If the server device does not have a transmitter, or if the client device does not have a receiver, it will necessarily be one-way communication, but the client device and the Sano device each have a transmitter and receiver. However, if the signal flow is one-way to the client device power server device, it is still one-way communication. In addition, bidirectional communication is a communication method in which a server device transmits a response command to a request command to which the client device capability is also transmitted, and the client device transmits the next request command again after analyzing the response command. is there. In this case, if an agreement is made in advance in both the OBEX layer of the client device and the OBEX layer of the sano device that does not require a response command for every request command, a specific command can be used. Response command for request command is not always required!

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

Step S120 is a step in which communication direction selection section 1524 selects bidirectional communication or one-way communication. For bidirectional communication, go to step S121, or for unidirectional communication. If this is the case, transition to SI 31 respectively.

[0329] Step S121 is a step of determining whether or not a force has been received from the client device in bidirectional communication. If it has been received, the process proceeds to step S122. If it has been received!

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

[0331] Step S123 is a step of creating a response command to the client device in bidirectional communication. After completing the response command, the process proceeds to step S124.

[0332] Step S124 is a step of notifying the lower layer processing unit 1530 in order to transmit the created response command to the client device in bidirectional communication. After the notification is completed, the process proceeds to step S125.

Step S125 is a step of determining whether or not to end communication. If not, the process returns to step S121.

On the other hand, step S131 is a step of determining whether or not a request command from a client device has been received in one-way communication. If received, the process proceeds to step S132. If received, the process proceeds to step S131 again.

Step S132 is a step of analyzing the request command from the client device in the one-way communication. After the analysis is completed, the process proceeds to step S135.

[0336] Step S135 is a step of determining whether or not the communication has ended in the one-way communication. If not completed, the process proceeds to step S131 again.

[0337] The above operation is performed by the control unit 1521 of the OBEX layer processing unit 1520 of the server device 1500, so that in bidirectional communication, a response command is generated and transmitted when a request command of the client device is received, Also, in one-way communication, it is possible to receive the next request command without generating or transmitting a response command after receiving a request command having a client device capability.

[Tenth Embodiment]

The server device (communication device) of the transfer data transfer system (communication system) according to the tenth embodiment of the present invention will be described as follows. Other embodiments Unless otherwise specified, the terms (including members and functions) defined in the above are used in accordance with the definitions in this embodiment.

FIG. 29 is a block diagram of server device 1500 according to the present embodiment. That is, since it is the same as the ninth embodiment described above, and the operation of each block other than the control unit 1521 of the OBEX layer processing unit 1520 is basically the same as the operation of each block in the ninth embodiment. The description is omitted.

Operation of control unit 1521 of OBEX layer processing unit 1520 according to the present embodiment will be described using the flowchart shown in FIG.

[0341] Step S141 is a step of determining whether or not the client device has received the Put command. If received, the process proceeds to step S142. If not received, the process proceeds to step S141 again.

[0342] Step S142 is a step of analyzing the received Put command. After the analysis is completed, the process proceeds to step S143.

Step S143 is a step of determining whether or not the analyzed Put command is a Put command whose final Put command is not final. If it is the final Put command, the process goes to Step S144. If it is a non-final Put command, the process goes to Step S141 again.

Step S 144 is a step of generating a response command to the client device. After generating the response command, the process proceeds to step S145. In step S144, the generated response command is, for example, a SUCCESS response command when all Put commands from the client device have been normally completed. Other cases are not mentioned in this embodiment.

[0345] Step S145 is a step of notifying the lower layer processing unit 1530 to transmit the above-described response command to the client device. After notification ends, the process proceeds to step S146.

[0346] Step S146 is a step of determining whether or not the communication is terminated. If not, the process proceeds to step S141.

[0347] The control unit 1521 of the OBEX layer processing unit 1520 of the server device 1500 performs the above operation. Therefore, for a Put request command that is not final, a SUCCESS response command is generated for the final Put request command without generating or sending a CONTINUE response command that was generated by the conventional OBEX layer processing unit. Therefore, it is possible to increase the efficiency of communication. In addition, since the SUCCESS response command for the final Put command is transmitted to the client device, it is possible to determine whether the client device has successfully transferred data to the server device 1500.

[0348] Also, as shown in Fig. 31, by combining bidirectional communication and one-way communication switching by the communication direction selector 1524, only SUCCE SS response command is sent for the final Put command during bidirectional communication. During generation, transmission, and one-way communication, operations can be performed without generating and transmitting response commands for all request commands.

[Eleventh Embodiment]

The transfer data transfer system (communication system) according to the eleventh embodiment of the present invention is described as follows. Note that the terms (including members and functions) defined in other embodiments are used in accordance with the definitions in this embodiment unless otherwise specified.

[0350] An example of communication between mobile phones according to the present embodiment will be described using FIG.

[0351] In this embodiment, the client device (transmitter) and the sano device (receiver) are connected using a mobile phone, but either the client device (transmitter) or the server device (receiver) is used. If the other device is a mobile phone, the opposite device may not be a mobile phone as long as data can be transmitted or received by infrared rays or the like by any of the communication methods of the present invention described above.

[0352] In Fig. 33, the mobile phone A force S client device (transmission side) and the mobile phone B are shown as the server device (reception side), but the reverse is also possible.

In FIG. 33, data in mobile phone A is transmitted to mobile phone B using infrared rays. When the mobile phone B receives the data transmitted from the mobile phone A, it stores the received data in the memory in the mobile phone B or in the connected external memory. The aforementioned data includes text data, image data, voice data, phone book data, system information, etc., and is not limited to a specific format. The data in mobile phone A is the Either the data in phone A's internal memory or the data in external memory (non-volatile memory such as SD card) connected to the mobile phone.

[0354] An example of communication between mobile phones according to the present embodiment will be described in detail as follows.

[0355] For example, during bidirectional communication, the sending client device (mobile phone A) is not the last OBEX layer. When sending a Put command, the next Put command without waiting for a CONTINUE response command. When sending the final Put command, wait for the SUCCESS response command from the receiving server device (cell phone B) to check whether the communication was successful. Note that the OBEX layer that requires the conventional CONTINUE response command may be used by artificially creating the above CONTINUE response command in the lower layer processing unit of the OBEX layer and notifying the OBEX layer.

[0356] Also, in the receiving server device (cell phone B), when the OBEX layer receives a Put command that is not the final from the sending client device (cell phone A), it does not generate or transmit a CONTINUE response command. When the final Put command is received, a SUCCESS response command is generated and sent. When a non-final Put command is received, the conventional OBEX layer that generates and sends the CONTINUE response command is diverted, and only the CONTINUE command is not sent to the client device in the lower layer.

[0357] By realizing the above communication between the sending client device (mobile phone and receiving server device (mobile phone B)), in two-way communication, the communication efficiency is high and the communication quality is high. Data transfer can be performed using

[0358] Also, for example, in one-way communication, in the sending client device (mobile phone A), when the OBEX layer sends all request commands, the next request command without waiting for a response command from the server device is sent. Send. For each request command with OBEX layer strength, an appropriate response command is artificially created in the lower layer of OBEX and notified to the OBEX layer, so that the OBEX layer that requires the conventional response command can be created. You may divert.

[0359] Also, in the receiving server device (mobile phone B), when the OBEX layer receives all request commands of the sending client device (mobile phone A), it does not generate or send a response command. In addition, a response command for the received request command is created and transmitted. Don't send the response command from the OBEX layer to the client device in the lower layer by using the existing OBEX layer.

[0360] By realizing the above communication between the sending client device (mobile phone and receiving server device (mobile phone B)), even in one-way communication, data can be exchanged using an object exchange protocol such as OBEX. Transfer can be performed.

[Twelfth embodiment]

The transfer data transfer system (communication system) according to the twelfth embodiment of the present invention is described as follows. Terms defined in other embodiments

Unless otherwise specified, (including members and functions) is used in accordance with the definition in this embodiment.

[0362] A communication example between the mobile phone and the display device according to the present embodiment will be described with reference to FIG.

[0363] In this embodiment, the client device (transmitter) and the Sano device (receiver) are respectively used by using the mobile phone A and the display device B (for example, a TV). The client device (transmitter) may not be a mobile phone as long as data can be transmitted by infrared rays or the like by any method of the invention. The display device B may be a client device (transmitter) and the mobile phone A may be a server device (receiver)!

In FIG. 34, data in mobile phone A is transmitted to display device B using infrared rays. Display device B performs appropriate processing on the data transmitted from mobile phone A. For example, if it is image data, display is performed by decompressing the compressed data if necessary. Yes, but not limited to this. The above-mentioned data includes text data, image data, audio data, phone book data, system information, etc., and is not limited to a specific format. The data in the mobile phone A may be either data in the internal memory of the mobile phone A or data in an external memory (non-volatile memory such as an SD card) connected to the mobile phone.

[0365] An example of communication between the mobile phone and the display device according to the present embodiment will be described in detail as follows.

[0366] For example, during bidirectional communication, the sending client device (cell phone A) uses OBEX. When the layer is not final, when sending a Put command, the next Put command is sent without waiting for the CONTINUE response command. When sending the final Put command, the SUCCESS response command of the receiving server device (display device B) is used. And check whether the communication was successful. Note that the OBEX layer that requires the conventional CONTINUE response command may be used by artificially creating the above CONTINUE response command in the lower layer processing unit of the OBEX layer and notifying the OBEX layer.

[0367] In the receiving server device (display device B), when the OBEX layer receives the Put command from the sending client device (mobile phone A), the CONTINUE response command is not generated or transmitted. When the final Put command is received, a SUCCESS response command is generated and sent. When a Put command that is not final is received, the conventional OBEX layer that generates and transmits the CONTINUE response command is diverted, and only the CONTINUE command is not transmitted to the client device in the lower layer.

[0368] By realizing the above communication between the sending client device (mobile phone and receiving server device (display device B)), in two-way communication, the communication efficiency is high, the communication quality is also high, and the object exchange For example, it becomes possible to transfer image data.

[0369] Also, for example, in the case of one-way communication, the sending client device (mobile phone A) does not wait for the response command from the server device when the OBEX layer sends all request commands. Send a request command. For each request command with OBEX layer strength, an appropriate response command is artificially created in the lower layer of OBEX and notified to the OBEX layer, so that the OBEX layer that requires the conventional response command can be created. You may divert.

[0370] In the receiving server device (display device B), when the OBEX layer receives all request commands from the sending client device (mobile phone A), it does not generate or send a response command. Note that the conventional OBEX layer that creates and transmits a response command for the received request command may be used, and the response command from the OBEX layer may not be transmitted to the client device in the lower layer.

[0371] By realizing the above communication between the sending client device (mobile phone and receiving server device (display device B)), objects such as OBEX can be used even in one-way communication. For example, it is possible to transfer image data using a data exchange protocol.

[Thirteenth Embodiment]

The transfer data transfer system (communication system) according to the thirteenth embodiment of the present invention is described as follows. Terms defined in other embodiments

[0373] An example of communication between the mobile phone and the printing apparatus according to the present embodiment will be described with reference to FIG.

[0374] In the present embodiment, the mobile device A and the printing device B (for example, a printer) are used for the client device (transmitter) and the Sano device (receiver), respectively. The client device (transmitter) may not be a mobile phone as long as data can be transmitted by infrared rays or the like by any of the methods of the present invention. Also, the printing apparatus B may be a client device (transmitter) and the mobile phone A may be a server device (receiver)!

In FIG. 35, data in the mobile phone A is transmitted to the printing apparatus B using infrared rays. The printing device B performs appropriate processing on the data transmitted from the mobile phone A. For example, if it is image data, printing is performed by decompressing the compressed data if necessary. Yes, but not limited to this. The above-mentioned data includes text data, image data, audio data, phone book data, system information, etc., and is not limited to a specific format. The data in the mobile phone A may be either data in the internal memory of the mobile phone A or data in an external memory (non-volatile memory such as an SD card) connected to the mobile phone.

[0376] An example of communication between the mobile phone and the printing apparatus according to the present embodiment will be described in detail as follows.

[0377] For example, during two-way communication, the sending client device (mobile phone A) is not the last OBEX layer. When sending a Put command, the next Put command without waiting for a CONTINUE response command. When the final Put command is sent, it waits for the SUCCESS response command from the receiving server device (printing device B), and confirms whether or not communication has been performed normally. Note that the above CONTINUE response command is processed in the lower layer of the OBEX layer. The OBEX layer that requires the conventional CONTINUE response command may be diverted by creating it in a simulated manner and notifying the OBEX layer.

[0378] In the receiving server device (printing device B), when the OBEX layer receives the Put command from the sending client device (cell phone A), the CONTINUE response command is not generated or transmitted. When the final Put command is received, a SUCCESS response command is generated and sent. When a Put command that is not final is received, the conventional OBEX layer that generates and transmits the CONTINUE response command is diverted, and only the CONTINUE command is not transmitted to the client device in the lower layer.

[0379] By realizing the above communication between the sending client device (mobile phone and receiving server device (printing device B)), in two-way communication, the communication efficiency is high and the communication quality is high. For example, it becomes possible to transfer image data.

[0380] Also, for example, during one-way communication, when the OBEX layer sends all request commands to the sending client device (mobile phone A), it does not wait for a response command from the server device. Send a request command. For each request command with OBEX layer strength, an appropriate response command is artificially created in the lower layer of OBEX and notified to the OBEX layer, so that the OBEX layer that requires the conventional response command can be created. You may divert.

[0381] In the receiving server device (printing device B), when the OBEX layer receives all request commands from the transmitting client device (mobile phone A), it does not generate or send a response command. Note that the conventional OBEX layer that creates and transmits a response command for the received request command may be used, and the response command from the OBEX layer may not be transmitted to the client device in the lower layer.

[0382] By realizing the above communication between the sending client device (mobile phone and receiving server device (printing device B)), even in one-way communication, using an object exchange protocol such as OBEX, for example, It is possible to transfer image data.

[Embodiment 14]

The transfer data transfer system (communication system) according to the fourteenth embodiment of the present invention is described as follows. Terms defined in other embodiments Unless otherwise specified, (including members and functions) is used in accordance with the definition in this embodiment.

[0384] An example of communication between the mobile phone and the recording device according to the present embodiment will be described with reference to FIG.

[0385] In the present embodiment, the mobile device A and the recording device B (for example, HDD recorder, DVD recorder, etc.) are used for the client device (transmitter) and the Sano device (receiver), respectively. However, the client device (transmitter) does not have to be a mobile phone as long as it can transmit data using infrared rays by any of the above-described methods of the present invention. Further, the recording device B may be a client device (transmitter) and the mobile phone A may be a server device (receiver).

In FIG. 36, data in the mobile phone A is transmitted to the recording device B using infrared rays. Recording device B performs appropriate processing on the data transmitted from mobile phone A. For example, if it is video data, it performs appropriate compression processing, decompression processing, and other video processing if necessary. After that, the recording is performed in the recording unit in the recording apparatus, but this is not restrictive. The above-mentioned data is text data, image data, video data, audio data, telephone book data, system information, etc., and is not limited to a specific format. The data in mobile phone A may be either data in the internal memory of mobile phone A or data in an external memory (non-volatile memory such as an SD card) connected to the mobile phone.

[0387] An example of communication between the mobile phone and the recording device according to the present embodiment will be described in detail as follows.

[0388] For example, during two-way communication, the sending client device (cell phone A) is not the final OBEX layer. When sending a Put command, the next Put command without waiting for a CONTINUE response command. When the final Put command is sent, it waits for the SUCCESS response command from the receiving server device (recording device B) to check whether communication has been performed normally. Note that the OBEX layer that requires the conventional CONTINUE response command may be used by artificially creating the above CONTINUE response command in the lower layer processing unit of the OBEX layer and notifying the OBEX layer. [0389] The receiving server device (recording device B) does not generate or send a CONTINUE response command when the OBEX layer receives the Put command, which is the final from the sending client device (cell phone A). When the final Put command is received, a SUCCESS response command is generated and sent. When a Put command that is not final is received, the conventional OBEX layer that generates and transmits the CONTINUE response command is diverted, and only the CONTINUE command is not transmitted to the client device in the lower layer.

[0390] By realizing the above communication between the sending-side client device (mobile phone A) and the receiving-side server device (recording device B), in two-way communication, communication efficiency is high and communication quality is high. For example, video data can be transferred using object exchange.

[0391] Also, for example, in one-way communication, in the sending client device (mobile phone A), when the OBEX layer sends all request commands, the next request command without waiting for a response command from the server device is sent. Send. For each request command with OBEX layer strength, an appropriate response command is artificially created in the lower layer of OBEX and notified to the OBEX layer, so that the OBEX layer that requires the conventional response command can be created. You may divert.

[0392] In the receiving server device (recording device B), when the OBEX layer receives all request commands from the sending client device (mobile phone A), it does not generate or send a response command. Note that the conventional OBEX layer that creates and transmits a response command for the received request command may be used, and the response command from the OBEX layer may not be transmitted to the client device in the lower layer.

[0393] By realizing the above communication between the sending client device (mobile phone and receiving server device (display device B), even in one-way communication, using an object exchange protocol such as OBEX, for example, It is possible to transfer video data.

[Fifteenth embodiment]

The following will describe another embodiment of the present invention with reference to FIGS. Note that the communication protocol described in the present embodiment is applied to the first to fourteenth embodiments. Therefore, the terms defined in the first to fourteenth embodiments are also defined in the present embodiment unless otherwise specified. It shall be used as a rule.

[0395] (1) Communication layer

FIG. 37 is a schematic diagram showing the correspondence between the OSI 7 hierarchical model, the IrDA hierarchy, and the hierarchy of the communication system according to the present invention.

[0396] Each communication layer of the communication system according to the present embodiment also has a function equivalent to the corresponding layer of the OSI 7 layer model. However, as shown in Fig. 37, the above communication system has a 6-layer structure with one session layer and one presentation layer.

[0397] In the present embodiment, for convenience of explanation, 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. IrSimple is an improvement on some of the functions of conventional IrDA.

In this embodiment, the data link layer, network layer, transport layer, session layer + presentation layer may be expressed as LAP, LAMP, SMP, and OBEX, respectively, in accordance with IrSimple. When the communication layer is distinguished by transmitter and 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 transmitter.

[0399] (2) Transmitter Sequence between receivers

(2-1) Connection sequence

[A] Response available

FIG. 38 (a) is a sequence diagram showing a connection sequence of the present embodiment (response is sent). FIG. 38 (c) is an explanatory diagram showing the data structure of communication data in the connection sequence of the present embodiment (response is sent).

[0400] In this embodiment (with response), the SNRM command can have the same function as the search by using the global address for the SNRM Destination Device Address (Fig. 38 (c)). SNRM command).

[0401] In the present embodiment (with a response), the upper layer such as the network layer, transport layer, session layer, presentation layer, etc. is included in the SN RM command and UA response that are connection packets of the data link layer. Enter the parameters and commands necessary for the connection. As a result, to connect each upper layer, which was necessary in conventional IrDA Connection packets can be condensed into a single packet.

[0402] Therefore, the search and connection sequence, which conventionally required multiple packets, can be performed with one packet pair.

[0403] [B] No response

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

[0404] Depending on the user or application and the data type, a communication method that omits the response from the receiver can be selected. In this case, as shown in FIG. 38 (b), it can be assumed that the search and connection are completed only by the SNRM command.

[0405] As described above, the connection sequence of the present embodiment shortens the time required for connection by summarizing connection requests of a plurality of communication layers. Therefore, even when the communication path is disconnected, the connection sequence is repeated. Easy connection. Therefore, the communication path is easy to cut, for example, it is particularly suitable for wireless communication using infrared rays. However, it is also effective in IEEE802.il wireless, other wireless communication including Bluetooth, and wired communication.

[0406] Also, in this embodiment, an example in which connections of all communication layers are connected by one communication will be described, but the present invention is not limited to this. For example, after one communication layer is connected, the remaining plurality of communication layers may be connected. In addition, one communication layer may be connected by a plurality of communications. For example, if the network layer connection requires two communications, the data link layer connection and the network layer first connection are combined into one connection request, and the network layer second connection and the transport layer are combined. May be combined into a single connection request.

[0407] (2-2) Data exchange sequence

[A] Response available

FIGS. 39 (a) and 39 (b) are sequence diagrams showing a data exchange sequence according to the present embodiment (response is sent). FIG. 39 (a) is an explanatory diagram showing the data structure of communication data in the data exchange sequence of the present embodiment (response is sent). [0408] In the present embodiment (with a response), the response of the lower layer and the upper layer is reduced as much as possible between each piece of data, and a response indicating whether there was an error or helpless after sending a lot of data is returned.

[0409] The transmitter is constructed with a sequential packet number and a flag for asking whether there is a problem with the received data during data communication, and divided data obtained by dividing the data according to the packet size. Use packets.

[0410] As shown in Fig. 39 (a), the transmitter transmits a packet with the flag turned on after transmitting a predetermined number of packets. On the other hand, if the receiver receives a packet from the beginning of the previous data or when the above flag is turned on and sends a reply, and if it does not detect an error, it indicates that it has been received normally. Notify the transmitter. In addition, if the receiver detects an error from the beginning of the previous data, or after receiving a packet with the above flag turned on and sending a reply, the receiver receives the packet after the powerful packet that cannot be received. Ignores the divided data part, checks only the flag, and if the flag is on, notifies the transmitter of a powerful packet number that cannot be received due to an error.

[0411] Furthermore, when the transmitter receives a message indicating that it has been normally received, the transmitter transmits from the next packet. When the transmitter receives a notification that an error has occurred, it retransmits from the packet number that could not be received to the packet with the flag turned on.

[0412] Thereby, it is possible to close between the packets, and efficient communication becomes possible.

[0413] As shown in Fig. 39 (a), in this embodiment (response is sent), a UI frame (Fig. 40 (b)) is used. For this reason, the data link layer (LAP layer) cannot recognize missing packets and detects them in the transport layer.

[0414] The data part of the UI frame transport layer is provided with a sequential number and a data confirmation flag, whether it is the last packet of the data, and a flag indicating whether the received data is normal. Send.

[0415] [B] No response

FIGS. 41 (a) and 41 (b) are sequence diagrams showing a data exchange sequence according to the present embodiment (no response is sent). FIG. 41 (b) is an explanatory diagram showing the data structure of communication data in the data exchange sequence of the present embodiment (no response is sent). [0416] In the present embodiment (no response), if the receiver response is not required, only the integrity of the data is confirmed. Therefore, the transmitter assigns a sequence number to the packet and transmits all data continuously.

[0417] Then, the receiver only checks whether there is an error or not, and when receiving normally, after receiving all the data, it recognizes that it is normal reception within the receiver, and next Perform the operation. The next operation in this case is, for example, displaying received data, printing, or saving. On the other hand, if an error is detected, the receiver recognizes that it has failed to receive normally in the receiver and performs the following operations. In this case, the next operation is an indicator to notify the user that the failure has occurred or a state of waiting for the next reception.

[0418] Note that the UI frame (Fig. 40 (b)) shown in Fig. 41 (b) is also used in this embodiment (no response).

[0419] (2-3) Disconnection sequence

[A] Response available

FIG. 42 (a) is a sequence diagram showing a disconnection sequence of the present embodiment (response is sent). FIG. 42 (c) is an explanatory diagram showing the data structure of communication data in the disconnection sequence of the present embodiment (response is sent).

[0420] As shown in Fig. 42 (c), in this embodiment (with response), the parameters and commands necessary for disconnecting upper layers such as the network layer, transport layer, session layer, and presentation layer are set to DISC. Inserted into commands and UA responses.

[0421] Thereby, the disconnection sequence, which conventionally required a plurality of packets, can be performed with one packet pair.

[0422] [B] No response

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

[0423] As shown in Fig. 42 (b), in this embodiment (no response), when connection is made without requiring a response from the receiver, search and disconnection are completed with only the DISC command. You can do it.

[0424] (3) Sequence in transmitter and receiver

43 to 59, for convenience of explanation, the data link layer is denoted as LAP, the network layer is denoted as LAMP, the transport layer is denoted as TTP or SMP, and the session layer and the presentation layer are denoted as OBEX. In order to distinguish the communication layer 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 transmitter.

[0425] (3-1) Connection sequence

[A] Response available

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

[0426] As shown in Fig. 43, in this embodiment (with a response), both the transmitter and the receiver prepare for connection. After that, the transmitter passes the upper layer request as it is to the lower layer and transmits it as one packet (SNRM). On the other hand, the receiver receives the SNRM packet, notifies the upper layer as it is, and then passes the OBEX (S) response to the lower layer as it is, as one packet (UA). Send. When the transmitter receives the UA, the transmitter completes the connection and raises a notification (Connect. Confirm) to the upper layer.

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

[0428] First, each communication layer of the transmitter will be described.

[0429] OBEX (P) promptly issues a connection request function (Primitive) by entering a connection request command into the data to the lower layer (SMP (P)) when a connection request for application power comes. To be born. Also, when OBEX (P) receives a connection confirmation function from SMP (P), it confirms the response of the OBEX connection from the data, and if the response indicates that there is no problem (Success), the connection is completed. And

[0430] The SMP (P) receives the connection request function from OBEX (P) and promptly uses the connection request function data of OBEX (P) to communicate with the SMP (S) of the receiver. A connection request function is generated for the lower layer (LMP (P)) with the parameter added. Also, SMP (P) is LMP ( When the connection confirmation function is received from P), the parameter generated by the SMP (S) of the receiver is extracted from the function data data, the value is confirmed, and the negotiation with SMP (S) is completed. Also, SMP (P) sends the data of the connection confirmation function with the data of SMP (S) removed, as connection confirmation function to OBEX (P).

[0431] The LMP (P) receives the connection request function from the SMP (P) and promptly adds the parameters required for communication with the LMP (S) of the receiver to the data of the connection request function of the SMP (P). And a connection request function is generated for the lower layer (LAP (P)). Also, when LMP (P) receives a connection confirmation function from LAP (P), it extracts the parameter generated by the LMP (S) of the receiver from the function data, confirms the value, and The negotiation with is terminated. Also, LMP (P) sends the data of the connection confirmation function with the data of LMP (S) removed, as a connection confirmation function to SMP (P).

[0432] Normally, LSAP (Link Service Access Point) is defined to manage logical ports. And if you have a one-to-one connection, you don't need to use LMP. In this case, the connectionless value is used as a fixed value for LSAP. This eliminates the need to exchange LMP connection parameters.

[0433] The LAP (P) receives the connection request function from the LMP (P) and promptly adds the parameters required for communication with the LAP (S) of the receiver to the data of the connection request function of the LMP (P). And output the SNRM command to the physical layer of the receiver. Also, when the LAP (P) receives the physical layer strength UA response of the receiver, the LAP (S) extracts the parameters generated by the LAP (S) of the receiver from the data of the UA response and confirms the value. End the negotiation with. LAP (P) sends the data obtained by removing the LAP (S) parameter from the UA response data to LMP (P) as a connection confirmation function.

[0434] Next, each communication layer of the receiver will be described.

[0435] OBEX (S) receives the connection request function for the application power and enters a reception standby state. OBEX (S) confirms the OBEX connection command from the data when the lower layer (SMP (S)) force also receives the connection notification function (Indication), and if there is no problem, the response is Success. Is output to SMP (S) as a connection response function (Response) to complete the connection. [0436] In response to the connection request function from OBEX (S), SMP (S) enters a reception standby state. In addition, when SMP (S) receives a connection notification function from the lower layer (SMP (S)), it extracts the parameters generated by SMP (P) of the transmitter from the data of the function and responds to it. After creating the response parameter of, and excluding the SMP (P) parameter from the data of the above function and issuing the connection request function with the added data to OBEX (S), the connection response function from OBEX (S) is Wait. When SMP (S) receives a connection response function from OBEX (S), it adds the above response parameter to the data of the connection response function of OBEX (S) to LMP (S), A connection response function is generated for LMP (S), and SMP layer negotiation is terminated.

[0437] In response to the connection request function from SMP (S), LMP (S) enters a reception standby state. Also, when the LMP (S) receives the connection notification function from the lower layer (LAP (S)), it extracts the parameters generated by the LMP (P) of the transmitter from the function data, and After creating a response parameter, excluding the data power LMP (P) parameter of the above function and issuing a connection request function containing the data to SMP (S), the connection response function from SMP (S) is wait. In addition, when the LMP (S) receives a connection response function from the SMP (S), the LMP (S) adds the above response parameter to the data of the connection response function of the SMP (S) to the LAP (S). The connection response function is generated for LAP (S), and the negotiation of the LMP layer is completed.

[0438] Usually, LSAP (Link Service Access Point) is defined to manage logical ports. And if you have a one-to-one connection, you don't need to use LMP. In this case, the connectionless value is used as a fixed value for LSAP. This eliminates the need to exchange LMP connection parameters.

[0439] LAP (S) receives a connection request function with LMP (S) power and enters a reception standby state. When the physical layer strength SNRM command is received, the LAP (S) extracts the parameters generated by the transmitter LAP (P) from the SNRM command data, and the LAP (P) parameters from the SNRM command data. After issuing the connection request function containing the data to the LMP (S), create a response parameter for that function and wait for the connection response function from the LMP (S). When the LAP (S) receives the connection response function from the LMP (S), the LAP (S) adds the above response parameter to the data of the connection response function of the LMP (S), and the UA record is sent to the physical layer. The response is output and the LAP layer negotiation is terminated. [0440] [B] No response

FIG. 45 is a sequence diagram showing a connection sequence of the present embodiment (no response is sent). FIG. 44 (a) is an explanatory diagram showing the data structure of communication data in the connection sequence of the present embodiment (no response is sent).

As shown in FIG. 45, in the present embodiment (no response is sent), both the transmitter and the receiver prepare for connection. After that, the transmitter passes the upper layer request as it is to the lower layer and transmits it as one packet (SNRM). Then, the transmitter sends a notification (Connect. Confirm) from the LAP (P) to the upper layer as connection completion when the SNRM packet is transmitted. On the other hand, the receiver receives the SNRM packet, notifies the upper layer as it is, and completes the connection when notifying OBEX (S).

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

[0443] First, each communication layer of the transmitter will be described.

[0444] OBEX (P) promptly puts a connection request command into the data to the lower layer (S MP (P)) when a connection request is received from the application, and requests the connection request function (Primitive) Is generated. OBEX (P) completes connection when it receives a connection confirmation function from SMP (P).

[0445] SMP (P) receives the connection request function from OBEX (P) and promptly uses the connection request function data of OBEX (P) to communicate with SMP (S) of the receiver. A connection request function is generated for the lower layer (LMP (P)) by adding parameters. Also, when the SMP (P) receives the connection confirmation function from the LMP (P) manager, the SMP layer negotiation is terminated, assuming that the transmitted parameters can be negotiated. At this time, SMP (P) sends a connection confirmation function to OBE X (P).

[0446] The LMP (P) receives the connection request function from the SMP (P) and promptly adds the parameters required for communication with the LMP (S) of the receiver to the data of the connection request function of the SMP (P). And a connection request function is generated for the lower layer (LAP (P)). Also, when the LMP (P) receives the connection confirmation function for the LAP (P) force, the LMP (P) terminates the negotiation of the LMP layer, assuming that the transmitted parameters can be negotiated. At this time, LMP (P) transmits a connection confirmation function to SMP (P). [0447] Usually, LSAP (Link Service Access Point) is defined to manage logical ports. And if you have a one-to-one connection, you don't need to use LMP. In this case, the connectionless value is used as a fixed value for LSAP. This eliminates the need to exchange LMP connection parameters.

[0448] The LAP (P) receives the connection request function from the LMP (P) and promptly adds the parameters required for communication with the LAP (S) of the receiver to the data of the connection request function of the LMP (P). And output the SNRM command to the physical layer of the receiver. In addition, LAP (P) terminates the LA p layer negotiation, assuming that it has negotiated with the transmitted parameters when it outputs the SNRM command. At this time, LAP (P) sends a connection confirmation function to LMP (P).

[0449] Next, each communication layer of the receiver will be described.

[0450] OBEX (S) also receives a connection request function for application power and enters a reception standby state. If OBEX (S) receives the connection notification function (Indication) as well as the lower layer (SMP (S)) force, the OBEX (S) will also check the OBEX connection command for the data's intermediate force and if there is no problem, the connection will be completed And

[0451] SMP (S) receives a connection request function from OBEX (S) and enters a reception standby state. In addition, when SMP (S) receives a connection notification function from the lower layer (SMP (S)), it extracts the parameter generated by SMP (P) of the transmitter from the function data, Use to complete the negotiation. And SMP (S) removes the parameter of SM P (P) from the data of the above function! The connection request function with the stored data is issued to OBEX (S).

[0452] In response to the connection request function from SMP (S), LMP (S) enters a reception standby state. Also, when the LMP (S) receives a connection notification function from the lower layer (LAP (S)), it extracts the parameter generated by the transmitter LMP (P) from the function data and uses that parameter. To complete the negotiation. And LMP (S) excludes the parameter of data force LMP (P) of the above function! The connection request function with the stored data is issued to SMP (S).

[0453] Normally, LSAP (Link Service Access Point) is defined to manage logical ports. And if you have a one-to-one connection, you don't need to use LMP. In this case, the connectionless value is used as a fixed value for LSAP. Because of this, LMP There is no need to exchange connection parameters.

[0454] LAP (S) receives a connection request function with LMP (S) power and enters a reception standby state. Also, when the physical layer strength SNRM command is received, the LAP (S) extracts the parameter generated by the transmitter LAP (P) from the SNRM command data and completes the negotiation using the parameter. Then, the LAP (S) issues a connection request function to the LMP (S) that includes the data power of the above function, excluding the parameters of the LAP (P).

[0455] (3-2) Data exchange sequence

[A] Response available

FIG. 46 is a sequence diagram showing a data exchange sequence according to the present embodiment (response is sent). FIG. 47 is an explanatory diagram showing the data structure of communication data in the data exchange sequence of the present embodiment (response is sent).

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

[0457] On the other hand, the receiver receives the data and sends a notification to the upper layer. At this time, SMP (

In S), OBEX (S) in the upper layer is notified that data will continue (status = truncated).

[0458] After sending a certain number of packets, the transmitter turns on the flag to check whether the data has arrived properly and sends it. In response to this, in the receiver, SMP (S) notifies the transmitter of the number of errors in which the error occurred.

[0459] If there is no error, the transmitter outputs the next packet group, and if there is an error, the transmitter retransmits the packets after the packet with the error.

[0460] When the end of data is reached, the transmitter sets the flag indicating the end of data to ON and transmits. On the other hand, if this flag is ON, the receiver notifies OBEX (S) that the data is ready (status = OK) and waits for the response of OBEX (S). . When an OBEX (S) response occurs, the data is transmitted to the lower layer and output as a UI frame.

[0461] If the received response is Success, the transmitter ends normally. [0462] The sequence in the transmitter and receiver at this time is as follows.

[0463] At the transmitter, OBEX (P) outputs a PUT command as a data transmission function to the lower layer. However, if OBEX (P) can be sent with SMP (P) without requiring a PUT command response other than the PUT Final (last PUT) command (Continue is returned when normal), The following command is output. In the case of a command other than the PUT Final command or the PUT command, it waits for the data notification function from the lower layer and ends the command by looking at the response in that data.

Here, the data transmission function is a function (Data Re quest) for requesting data transmission to the lower layer. The data notification function is a function (Data Indicate) notifying that the lower layer force data has been received.

[0465] In the receiver, OBEX (S) receives the data by receiving the data notification function for the lower layer force.

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 transmission function for a command other than a PUT Final command or a PUT command.

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

[0467] When SMP receives a data transmission function from OBEX, (a) when the size that can be transmitted by LMP is smaller than the size of the data in the data transmission function, LMP can transmit the data. (B) When the size that can be sent by LMP is larger than the size of the data in the data transmission function, several data are combined and larger data that is smaller than the size that can be sent is combined. create. In addition, SMP is a sequential number, an argument that inquires the other device about the data reception status, an argument that indicates the end of the data, an argument that the SMP of the other device requires an OBEX response, and the received data is normal Create an SMP header with an argument indicating whether or not. Then, a data transmission function including the data attached to the data obtained by dividing or combining the SMP header is issued to the LMP.

[0468] Further, when the SMP receives the data notification function from the LMP, the SMP extracts the SMP header from the data in the function, and the sequence number is normal (ie, the sequence number comes in order without omission). Check the force). If it is normal, it issues a data notification function to OBEX. At this time, the data notification function may be output for each data notification function from the lower layer, and V, and the data notification function data from several lower layers may be output together! / ,.

[0469] The SMP (P) of the transmitter converts the data transmission function of OBEX (P) force into a data transmission function to LMP (P), and transmits data of a certain fixed amount of data. Issue a function. After that, SMP (P) sets the argument that inquires the receiver about the data reception status to True, issues a data transmission function, and waits for the data notification function of LMP (P).

[0470] SMP (P) analyzes the SMP header in the data notification function of LMP (S) force and indicates that the argument indicating whether the received data was normal was received normally. If it is ready to send the next data, it becomes a state that can be sent to OBEX (P). In other words, data from OBEX (P) can be accepted in this state.

[0471] On the other hand, SMP (P) has a normal argument that indicates whether the received data is normal by analyzing the SMP header of the data notification function received by LMP (S) force. If it indicates that it has not received power, the data transmission function that has been notified that the data has not been received correctly is generated again up to the data transmission function with the argument that inquires the other device about the data reception status set to True. To do. SMP (P) repeats re-occurrence until the data by all data transmission functions are notified to the receiver or a certain specified number of times.

[0472] Furthermore, when the SMP (P) receives a data transmission function with an argument that the end of data is True from OBEX (P), the LM P containing the last data of the data transmission function is inserted. The data transmission function to (P) is issued with the argument indicating that this data transmission function is the end of the data or the argument indicating that the OBEX (S) response of the receiver is required as True.

[0473] On the other hand, when the SMP (S) of the receiver receives the data notification function from the LMP (S), it needs to respond to the end of the data or the OBEX (S) of the receiver. When the indicated argument is True, a data notification function is entered in which data from which the SMP (S) header has been removed is inserted into OBEX (S).

[0474] In addition, when the SMP (S) receives the LMP (S) power of the data notification function, the SMP (S) Analyzes the SMP header from the data in the intelligent function and confirms the sequential number. SMP (S) can normally receive an argument indicating whether or not the received data is normal if it can receive normally until it receives a header whose argument is True to inquire the receiver about the data reception status. The SMP header is created to indicate this, and the data transmission function is issued to the LMP (S) as data.

[0475] On the other hand, when the SMP (S) detects that it has failed to receive normally, it stores the number of the SMP header that is predicted to have not been received normally. For example, when 0, 1, 2, 3, 5 is received, if the 5th should be 4, but it does not receive 4, the number predicted to be unable to receive normally is 4. Become. After that, SMP (S) checks only whether the argument for inquiring the data reception status to the receiver of the SMP header is True, and stops outputting the data notification function to OBEX (S).

[0476] When SMP (S) receives a data notification function whose argument is True to inquire the receiver about the data reception status, SMP (S) cannot properly receive an argument indicating whether or not the received data is normal. The SMP header is created by inserting the SMP header number that has been successfully received and inserted into the field for the sequential number, and the data transmission function is issued to LMP (S) as data. .

[0477] In addition, SMP (S) received a data notification function in which the argument indicating the end of the data or the argument indicating that the response of the OBEX (S) of the receiver was required was True. In this case, after outputting the data notification function to OBEX (S), it waits for a data transmission request from OBEX (S).

[0478] When SMP (S) receives a data transmission request from OBEX (S), it creates an SMP header that indicates that the received data was successfully received as an argument indicating whether the received data was normal, This is added to the data of the OBEX (S) data transmission request and the data transmission function is issued to LMP (S). If there is an error, notification to OBEX (S) stops, so the wait is only normal.

[0479] Next, when the LMP receives the upper layer data transmission request function, it creates the data by adding an LMP header to the data in the function, and issues a data transmission request function containing the data in the LAP. . In addition, when the LMP receives the LAP force data notification function, Creates data that excludes the LMP header from the data in the function, and issues a data notification function that contains the data in the SMP.

[0480] Note that it is not necessary to use LMP when making a one-to-one connection. in this case,

The LMP header contains an LSAP containing a connectionless value.

[0481] When the LAP receives a data transmission request function from the LMP, the LAP creates a data with a LAP header attached to the data in the function, and issues a UI frame containing the data in the physical layer. When the LAP receives a data reception notification from the physical layer, the LAP creates the data by removing the LAP header from the data in the UI frame, and issues a data notification function that contains the data in the LMP. In this embodiment, the LAP header text includes a connection address and a UI indicator.

[0482] [B] No response

FIG. 48 is a sequence diagram showing a data exchange sequence according to the present embodiment (no response is sent). FIG. 47 is an explanatory diagram showing the data structure of communication data in the data exchange sequence of the present embodiment (no response is sent).

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

[0484] On the other hand, the receiver receives data and sends notifications to higher layers. At this time, SMP (

[0485] Then, when the end of data is reached, the transmitter turns on the flag indicating the end of data and transmits the data. On the other hand, if this flag is ON, the receiver notifies OBEX (S) that the data is ready (status = OK), and ends the data exchange sequence.

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

[0487] At the transmitter, OBEX (P) outputs a PUT command as a data transmission function to the lower layer. However, OBEX (P) can terminate commands without requiring responses to all commands. OBEX (P) then outputs the next command when it can be sent by SMP (P). [0488] At the receiver, OBEX (S) receives the data notification function for the lower layer power, and receives only data without returning a response to all commands.

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

[0490] When the SMP receives a data transmission function from OBEX, (a) when the size that can be transmitted by the LMP is smaller than the size of the data in the data transmission function, the LMP can transmit the data. (B) When the size that can be sent by LMP is larger than the size of the data in the data transmission function, several data are combined and larger data that is smaller than the size that can be sent is combined. create. In addition, SMP is a sequential number, an argument that inquires the other device about the data reception status, an argument that indicates the end of the data, an argument that the SMP of the other device requires an OBEX response, and the received data is normal Create an SMP header with an argument indicating whether or not. Then, a data transmission function including the data attached to the data obtained by dividing or combining the SMP header is issued to the LMP.

[0491] Furthermore, when the SMP receives the data notification function from the LMP, the SMP header is extracted from the data in the function, and the force that the sequence number is normal (ie, the force that comes in order without missing) is confirmed. To do. If it is normal, it issues a data notification function to OBEX. At this time, the data notification function may be output for each data notification function from the lower layer, and V, and the data notification function data from several lower layers may be output together! / ,.

[0492] The SMP (P) of the transmitter converts the data transmission function of OBEX (P) force into a data transmission function to LMP (P). When a data transmission function is received from OBEX (P) whose argument is “False”, the data with the SMP header added is sent to LMP (P). In contrast, when SMP (P) receives from OBEX (P) a data transmission function with an argument that it is true, the last data of the data transmission function is inserted. Set the data transmission function to LMP (P) to True to indicate that this data transmission function is the end of the data or that the OBEX (S) response of the receiver is required. To emit.

[0493] On the other hand, when the SMP (S) of the receiver receives the data notification function from the lower layer, it Analyze the SMP header from the data in the data notification function and check the sequential number. When SMP (S) analyzes the SMP header and confirms that reception has been successful, it issues a data transmission function to LMP (S).

[0494] On the other hand, when SMP (S) detects that it has failed to receive normally, it

Notify EX (S) as an error. For example, when you receive 0, 1, 2, 3, 5, the fifth should be 4, but you did not receive 4.

[0495] After that, SMP (S) waits for the argument indicating the end of the data in the SMP header or that the OBEX (S) response of the receiver is True to be True. , The power to receive a data notification function that is True (note that even if it is received, it does not notify OBEX (S)), the power to receive a disconnect notification function, or data to OBEX (S) until a certain time has passed. Do not send notifications.

[0496] Next, when the LMP (P) of the transmitter receives a data transmission request function from SMP (S), it creates the data by adding an LMP header to the data in the function, and then generates LAP (P ) The data transmission request function containing the data is issued.

[0497] On the other hand, when the LMP (S) of the receiver also receives the data notification function, the LMP (S) of the receiver creates data excluding the LMP header from the data in the function, and SMP (S) The data notification function that contains the data is issued.

[0498] Note that it is not necessary to use LMP when making a one-to-one connection. in this case,

The LMP header contains an LSAP containing a connectionless value.

[0499] When the LAP (P) of the transmitter receives the data transmission request function, the LAP (P) of the transmitter creates the data by adding a LAP header to the data in the function, and the data enters the physical layer. Emits a UI frame.

[0500] On the other hand, when receiving the data reception notification from the physical layer, the LAP (S) of the receiver creates data excluding the LAP header from the data of the UI frame, and stores the data in the LMP (S). The data notification function containing the data is issued. In this embodiment, the LAP header includes a connection address and a UI indicator.

[0501] (3-3) Disconnect sequence

[A] Response available FIG. 49 is a sequence diagram showing a disconnection sequence of the present embodiment (response is sent). FIGS. 50 (a) and 50 (b) are explanatory diagrams showing the data structure of communication data in the disconnection sequence of the present embodiment (response is sent).

[0502] As shown in Fig. 49, in the present embodiment (with a response), the disconnect command of the transmitter is transmitted to the lower layer, and the DISC command is generated. The receiver receives the DISC command and notifies it to the upper layer, returns the response, and generates a UA response. After that, the upper layer of the transmitter is notified that the UA response has been received and ends.

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

[0504] First, each communication layer of the transmitter will be described.

[0505] OBEX (P) promptly sends a disconnect request command to the lower layer (SMP (P)) in the data and issues a disconnect request function (Primitive) when an application power disconnect request is received. To be born. Also, when OBEX (P) receives a disconnection confirmation function from SMP (P), it confirms the response of OBEX disconnection from the data, and if the response indicates that there is no problem (Success), disconnection is complete. And

[0506] Upon receiving the disconnect request function from OBEX (P), SMP (P) promptly stores the data in the disconnect request function of OBEX (P) and is necessary for communication with SMP (S) of the receiver. A parameter is added to generate a disconnect request function for the lower layer (LMP (P)). In addition, when SMP (P) receives a disconnection confirmation function from LMP (P), the data power of the function extracts the parameters generated by SMP (S) of the receiver, confirms the value, and SMP (S) The disconnection process is terminated. In addition, SMP (P) sends the data of the disconnection confirmation function with the data of SMP (S) removed, to OBEX (P) as a disconnection confirmation function. However, there is usually no new parameter to be added with SMP (P) when disconnecting.

[0507] The LMP (P) receives the SMP (P) force disconnection request function, and promptly adds the SMP (P) disconnection request function data to the parameters necessary for communication with the LMP (S) of the receiver. Is added and a disconnection request function is generated for the lower layer (LAP (P)). Also, when LMP (P) receives a disconnection confirmation function from LAP (P), it extracts the parameter generated by the LMP (S) of the receiver from the function data, confirms the value, and The disconnection process is terminated. In addition, LM P (P) is the data power of the cutting confirmation function, the data from which the parameter of LMP (S) is removed, Send to SMP (P) as a disconnect confirmation function. However, there is usually no new parameter added with LMP (P) when disconnecting.

[0508] The LAP (P) receives the LMP (P) force disconnection request function, and promptly adds the LMP (P) disconnection request function data to the parameters required for communication with the LAP (S) of the receiver. And a DISC command is output to the physical layer of the receiver. Also, when the LAP (P) receives the physical layer strength UA response of the receiver, it extracts the parameter generated by the LAP (S) of the receiver from the data of the UA response, confirms the value, and the LAP (S ). In addition, LAP (P) issues data obtained by removing the LAP (S) parameter from the UA response data to LMP (P) as a disconnect confirmation function. However, there is usually no new parameter to be added with LAP (P) when disconnecting.

[0509] Next, each communication layer of the receiver will be described.

[0510] When OBEX (S) receives the disconnect notification function (Indication) for the lower layer (SMP (S)) force, the OBEX (S) checks the data's intermediate OBEX disconnect command, and if there is no problem, the response is Success. Is output to SMP (S) as a disconnect response function (Response), and disconnection is completed.

[0511] When the SMP (S) receives the disconnect notification function from the lower layer (SMP (S)), it extracts the parameter generated by the SMP (P) of the transmitter from the function data and Create a response parameter, remove the SMP (P) parameter from the data of the above function, issue a disconnect request function containing the data to OBEX (S), then disconnect response function from OBEX (S) Wait. When SMP (S) receives a disconnect response function from OBEX (S), it adds the above response parameter to the data of the disconnect response function of OBEX (S) for LMP (S), and A disconnect response function is generated for L MP (S), and the SMP layer disconnection process is terminated. However, there is usually no new parameter to be added with SMP (S) when disconnecting!

[0512] When the LMP (S) force receives the disconnection notification function, the LMP (S) extracts the parameter generated by the transmitter LMP (P) from the function data and responds to it. The parameter of the data function LMP (P) of the above function is removed, the disconnection request function containing the data is issued to SMP (S), and the disconnection response function from SMP (S) is waited for . In addition, when LMP (S) receives a disconnect response function from SMP (S), LMP (S) Add the above response parameter to the SMP (S) disconnect response function data, generate a disconnect response function for LAP (S), and terminate the LMP layer disconnect processing. However, there is usually no new parameter added with LMP (S) when disconnecting!

[0513] LAP (S) extracts the parameters generated by the transmitter LAP (P) from the DISC command data when the physical layer force is also received by the DISC command, and the DISC command data force is also LAP (P). After issuing the disconnection request function containing the data to LMP (S), create a response parameter for that and wait for the disconnection response function from LMP (S). When the LAP (S) receives a disconnect response function from the LMP (S), the LAP (S) adds the response parameter to the data of the LMP (S) disconnect response function, and the UA responds to the physical layer. Output LAP layer disconnection processing. However, there is usually no new parameter to be added with LAP (S) when disconnecting.

[0514] [B] No response

FIG. 51 is a sequence diagram showing a disconnection sequence according to the present embodiment (no response is sent). FIG. 50 (a) is an explanatory diagram showing the data structure of communication data in the disconnection sequence of the present embodiment (no response is sent).

[0515] As shown in FIG. 51, in this embodiment (no response is sent), the transmitter disconnect command is transmitted to the lower layer, and the DISC command is generated. At this point, the transmitter ends the disconnection process. On the other hand, the receiver receives the DISC command and transmits it to the upper layer, and the disconnection process ends when it is notified to the upper layer.

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

[0517] First, each communication layer of the transmitter will be described.

[0518] OBEX (P) promptly sends a disconnect request command to the lower layer (S MP (P)) and issues a disconnect request function (Primitive) when a disconnect request is received. To be born. In addition, OBEX (P) completes disconnection when it receives a disconnect confirmation function from SMP (P).

[0519] Upon receiving the disconnect request function from OBEX (P), SMP (P) promptly stores the data in the disconnect request function of OBEX (P) and is necessary for communication with SMP (S) of the receiver. A parameter is added to generate a disconnect request function for the lower layer (LMP (P)). Also, SMP (P) is LMP ( When the disconnection confirmation function is received from P), it is determined that the transmitted parameters can be disconnected, and the SMP layer cutting process is terminated. SMP (P) also sends a disconnect confirmation function to OBEX (P). However, normally there is no new parameter added by SMP (P) when cutting.

[0520] The LMP (P) receives the SMP (P) force disconnection request function, and promptly adds the SMP (P) disconnection request function data to the parameters necessary for communication with the receiver LMP (S). Is added and a disconnection request function is generated for the lower layer (LAP (P)). Further, when the LMP (P) receives the disconnection confirmation function from the LAP (P), it assumes that it has been disconnected with the transmitted parameters, and terminates the LMP layer disconnection process. LMP (P) also sends a disconnect confirmation function to SMP (P). However, there is usually no new parameter added by LMP (P) when cutting.

[0521] The LAP (P) receives the LMP (P) force disconnection request function, and promptly adds the LMP (P) disconnection request function data to the parameters required for communication with the LAP (S) of the receiver. And a DISC command is output to the physical layer of the receiver. Also, when the LAP (P) outputs the DISC command, it assumes that it has been disconnected with the transmitted parameters and terminates the LAP layer disconnection process. LAP (P) issues a disconnection confirmation function to LMP (P). However, there is usually no new parameter to add with LAP (P) when disconnecting!

[0522] Next, each communication layer of the receiver will be described.

[0523] When OBEX (S) receives the disconnect notification function (Indication) for the lower layer (SMP (S)) force, the OBEX (S) confirms the data's intermediate OBEX disconnect command. The

[0524] When SMP (S) receives the lower layer (SMP (S)) power disconnection notification function, it extracts the parameter generated by SMP (P) of the transmitter from the function data and uses that parameter. To complete the cutting. SMP (S) also issues a disconnect request function to OBEX (S) that includes the data power of the above function, excluding the parameters of SMP (P). However, there is usually no new parameter to be added with SMP (S) when disconnecting!

[0525] When the LMP (S) force also receives the disconnect notification function, the LMP (S) extracts the parameter generated by the transmitter LMP (P) from the function data and uses that parameter. To complete the cutting. LMP (S) also issues a disconnect request function to SMP (S) that includes the data power of the above function, excluding the parameters of LMP (P). However, usually when cutting There are no new parameters added to LMP (S)!

[0526] When the LAP (S) receives a physical layer DISC command, the LAP (S) extracts the parameter generated by the transmitter LAP (P) from the DISC command data and completes the disconnection using that parameter. . Also, LAP (S) issues a disconnect request function to LMP (S) that contains data obtained by removing the LAP (P) parameter from the DISC command data. However, there is usually no new parameter to add with LAP (S) when disconnecting!

[0527] (4) Switching response

The flow of data and parameters between the communication layers of the transmitter and receiver will be described with reference to FIGS.

[0528] In this embodiment, each communication layer LAP, LMP, SMP, OBEX of the transmitter and the receiver has a connection request function, a connection notification function, a connection response function, and a connection confirmation function. These functions are used to access the LAP layer from the upper layer (ie, LMP layer).

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

[0530] On the other hand, Qos notifies the specification of negotiation parameters such as baud rate determined by LAP and negotiation results to higher layers including OBEX. Qos

It is also used in IrDA.

[0531] For example, when a QoS with a parameter that requires the transmitter application or OBEX (P) force response is required, Z is transmitted to the lower layer in order to LAP (P). LAP (P) then sets the QoS value to the negotiation parameter (Ack Less Connect

) And send it to the receiver.

[0532] As a result, each communication layer of the transmitter and the receiver

Response required by OBEX (P) Operates according to the Z-unnecessary specification, so bidirectional Z one-way connection is possible.

[0533] Figs. 52 to 56 show the connection sequence (Fig. 43) of this embodiment (response is sent).

It is explanatory drawing which shows the flow of the data and parameter between communication layers. OBEX—S QoS parameters between MPs, between SMP and LMP, and between LMP and LAP may be the same or different. Therefore, in the figure, -a, -b, and -c are added to distinguish them.

[0534] In the transmitter, as shown in Fig. 52, the data to be transmitted to the receiver and the data of QoS-1 (QoS requested by the transmitter) are transmitted by con.req (data) (Fig. 43). Pass from layer to lower layer.

[0535] On the other hand, as shown in Fig. 53, the receiver passes only QoS-2 (QoS requested by the receiver) data from the upper layer to the lower layer by con.req.

[0536] After that, when the LAP (S) receives the SNRM command, the receiver compares the QoS-1 of the transmitter with the QoS-2 of the own device, and sets QoS-3 as a common negotiated parameter. create. Then, as shown in FIG. 54, LAP (S) notifies QoS-3 to the upper layer together with the data from the transmitter by con.ind (data). Each upper layer stores this QoS-3 and holds it as a connection parameter at the time of connection.

[0537] Continuing! / In the receiver, QoS is not required when con.resp (data) is notified! Therefore, as shown in Fig. 55, only the data is passed from the upper layer to the lower layer in con.resp (data). When LAP (S) receives con.resp (data), QoS-3 is inserted into the UA response and a UA response is issued.

[0538] Next, at the transmitter, the LAP (P) receives the UA response and stores QoS-3 as a negotiated parameter. Then, as shown in FIG. 56, LAP (P) notifies QoS-3 to the upper layer together with the receiver data by con.conKdata). Each communication layer holds this Q ◦ S-3 as a connection parameter for the established connection.

[0539] In the present embodiment, for example, as QoS of con.req, Requested-QoS: Baud- Rate + Max-Turn- Around-Time + Disconnect—Threshold + Databize + Ack less connection + Min- Packet- Interval Is used. Also, as the o¾ of Con.ind 'con.conf, Resultant-oS: Baua- Rate + Disconnect- Threshold + Databize + Ack less connection (indication primitive only) is used.

[0540] In addition, in the connection sequence of this embodiment (no response) (Fig. 45), the flow of data and parameters between the communication layers is as follows.

[0541] In the transmitter, as shown in Fig. 52, the data to be transmitted to the receiver and the data of QoS-1 (QoS required by the transmitter) are transmitted by con.req (data) (Fig. 45). Pass from layer to lower layer. [0542] Then, the LAP (P) of the transmitter stores QoS-1 as it is as QoS-3. Then, LA P (P) notifies QoS-3 to the upper layer by con.conf as shown in FIG. Each communication layer holds this QoS-3 as a connection parameter for the established connection.

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

[0544] Thereafter, at the time when the LAP (S) receives the SNRM command, the receiver sets the QoS-1 of the transmitter to QoS-3. In addition, if the parameters of QoS-2 are not satisfactory in combination with QoS-1, it cannot be received.

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

[0546] As a result, the application indicates whether there is a response or not, and the application uses the above QoS-1 and QoS-2 as upper layers.

(Application) Can be switched by operating.

[0547] Here, as a reference for switching with / without a response, the file format of the file to be transmitted, application, selection of the user, and the like can be considered.

[0548] Specifically, when the file format is used as a reference, for example, in the case of a multimedia-related file, both the presence / absence of a response can be selected, and data such as a phone book, mail, and schedule can be received. If it is desired to confirm that the response has been made, “with response” may be automatically selected. In addition, when the application is used as a reference, for example, in the case of a slide show, no response may be automatically selected. In addition, in the case of user selection, for example, the user may select from the menu display with / without response.

FIG. 57 to FIG. 59 are explanatory diagrams showing modifications of the flow of data and parameters between communication layers in the connection sequence of the present embodiment.

[0550] When the first SNRM command includes all communication layer information in the transmitter (Fig. 43), data and parameters are relayed and transmitted in each communication layer (Fig. 52). Thus, it can be configured to pass directly from each communication layer to the LAP layer.

[0551] Conversely, as shown in Fig. 58, the data included in the SNRM command is received at the receiver. It can be configured by taking out all parameters and passing them directly from the LAP layer to each destination communication layer.

[0552] Also, as shown in Fig. 59, in the transmitter, the data and parameters of OBEX (P), SMP (P), and LMP (P) are integrated with LMP (P), and further, with LAP (P). It can be configured by adding the LAP (P) parameter to the integrated data parameter and generating the SNRM command.

[0553] The present invention is not limited to the above-described embodiments, and various modifications are possible within the scope shown in the claims. The technical means disclosed in different embodiments are appropriately combined. The obtained embodiments are also included in the technical scope of the present invention.

[0554] The client device and the server device in each of the above embodiments include, for example, a mobile phone, a PDA (Personal Digital Assistants), a digital camera, a personal computer, and the like.

[0555] In addition, each block of the client device and the server device in each of the above embodiments may be configured by hardware logic (communication circuit), or software using an arithmetic processing unit such as a CPU as follows. It may be realized by. In other words, the above-described client device and server device have a CPU (central processing unit) that executes instructions of a communication program for control described so that each function can be executed by a computer, and a ROM (read only) that stores the program. memory), a RAM (r andom access memory) for expanding the program, and a storage device (recording medium) such as a memory for storing the program and various data.

[0556] An object of the present invention is to provide a recording medium in which a program code (execution format program, intermediate code program, source program) of a communication program, which is software that realizes the above-described functions, is recorded so as to be readable by a computer. This can also be achieved by supplying the above client device and server device and reading and executing the program code recorded on the recording medium by the computer (or CPU or MPU).

[0557] Examples of the recording medium include a tape system such as a magnetic tape and a cassette tape, a magnetic disk such as a floppy disk Z hard disk, and a CD-ROMZMOZ. A disk system including an optical disk such as MD / DVD / CD-R, a card system such as an IC card (including a memory card) Z optical card, or a semiconductor memory system such as a mask ROMZEPROMZEEPROMZ flash ROM can be used.

[0558] The client device and the server device may be configured to be connectable to a communication network, and the program code may be supplied via the communication network. The communication network is not particularly limited. For example, the Internet, intranet, extranet, LAN, ISDN, VAN, CATV communication network, virtual private network, telephone line network, mobile communication network, satellite A communication network or the like is available. Furthermore, the present invention can also be realized in the form of a carrier wave or a data signal sequence in which the program code is embodied by electronic transmission.

[0559] As described above, the communication device according to the present invention issues a request command and receives an answer command in response to the request command, thereby transmitting an object to the object exchange layer of the secondary station. A communication apparatus as a primary station having a layer, an object exchange layer processing unit for processing the communication protocol of the object exchange layer, and a lower layer for processing a communication protocol of a lower layer located below the object exchange layer A response generation unit that generates a pseudo response command that simulates a response command from the secondary station and notifies the object exchange layer processing unit, and a response generation unit that includes the processing unit. Upon receipt of a request command generation notification from the exchange layer processing unit, the pseudo response command responding to the request command Generated and are characterized by having a lower layer control unit which controls the response generation unit to notify the object exchange layer processing unit.

[0560] Further, the communication method according to the present invention has an object exchange layer for sending an object to the object exchange layer of the secondary station by issuing a request command and receiving a response command in response to the request command. A communication method in a primary station, and when a lower layer located below the object exchange layer receives a request command generation notification from the object exchange layer, a response from the secondary station responding to the request command A pseudo response command simulating the command is generated and notified to the object exchange layer. [0561] With the above configuration and method, in the primary station (for example, client device), the lower layer below the object exchange layer generates a pseudo response command and notifies the object exchange layer.

[0562] Therefore, object exchange with a secondary station (for example, server equipment) that has a minimum reception function that does not have a transmission function without changing the communication protocol for exchanging objects with the request command Z response command. Is possible. In addition, since it is not necessary to change the communication protocol (object exchange protocol) of the object exchange layer in order to send / receive data to / from the secondary station as described above, it is possible to divert existing assets.

[0563] Furthermore, the communication device according to the present invention includes a timer that operates when the lower layer processing unit receives a request command generation notification from the object exchange layer processing unit, and measures an elapsed time. Even if the elapsed time of the timer reaches a preset value, the lower layer control unit generates the pseudo response command when the secondary local response command is not received, and generates the object exchange layer. The response generation unit is controlled so as to notify the processing unit.

[0564] With the above configuration, there is further provided a function of waiting for a response command of secondary station power for a predetermined time, and if the response command does not come from the secondary station, the secondary station transmits a response command. Judgment can be made to generate a pseudo-response command and notify the object exchange layer.

[0565] Therefore, in communication with a secondary station having a transmission function, object exchange by the conventional request command Z response command can be performed, and in communication with a secondary station having no transmission function, in a lower layer. It is possible to exchange objects by generating a pseudo response command.

[0566] Furthermore, in the communication device according to the present invention, the lower layer control unit of the lower layer processing unit receives from the secondary station according to the type of request command issued by the object exchange layer processing unit. The ability to notify a response command to be received to the object exchange layer processing unit, and to switch whether to generate a pseudo response command to the response generation unit and to notify the object exchange layer processing unit .

[0567] With the above configuration, a response command from the secondary station is further generated according to the type of request command. It is possible to switch between waiting for a command and generating a pseudo response command. Thus, for example, the minimum necessary response commands such as connection request, disconnection request, and final data transfer request are received, while response commands for data transfer requests other than the final data transfer request are received. Processing can be omitted.

[0568] Therefore, the communication process can be simplified while ensuring the reliability of communication by receiving only the minimum necessary response command in the secondary local power. Therefore, it is possible to reduce the scale of programs and circuits.

[0569] Further, in the communication device according to the present invention, the lower layer processing unit includes a header information analysis unit that analyzes header information of a request command issued by the object exchange layer processing unit, and the lower layer control According to the type of header information analyzed by the header information analysis unit, the response command received from the secondary station is notified to the object exchange layer processing unit, or a pseudo response command is sent to the response generation unit. It is characterized by switching whether to generate and notify the object exchange layer processing unit.

[0570] With the above configuration, whether to wait for a response command from the secondary station or to generate a pseudo response command can be switched according to the type of header information of the request command. Therefore, for example, the minimum required response commands such as connection request, disconnection request, and final data transfer request are received, while response commands for data transfer requests other than the final data transfer request are received. Can be omitted.

[0571] Therefore, by receiving only the minimum necessary response command in the secondary local power, communication processing can be simplified while ensuring communication reliability. Therefore, it is possible to reduce the scale of programs and circuits.

[0572] Further, a communication system according to the present invention includes the communication apparatus as a primary station and a communication apparatus as a secondary station that receives the communication apparatus power object. Furthermore, the communication system according to the present invention is characterized in that the communication device as the secondary station does not transmit a response command.

[0573] According to the communication system, even if the secondary station cannot transmit a response command, the primary station generates a pseudo response command and notifies the object exchange layer. Therefore, traditional communication programs such as object exchange using request command Z response command It is possible to exchange objects with a secondary station that has a minimum necessary reception function that does not have a transmission function without changing the protocol.

[0574] Further, the communication device according to the present invention receives an object exchange command for receiving an object from the object exchange layer of the primary station by receiving a request command for the primary station and issuing a response command for responding to the request command. A communication apparatus as a secondary station having a layer, an object exchange layer processing unit that processes the communication protocol of the object exchange layer, and a lower layer that processes a communication protocol of a lower layer located below the object exchange layer A layer processing unit, and when the lower layer processing unit receives the response command issued by the object exchange layer processing unit, it does not transmit the response command to the primary station. As a feature.

[0575] Further, the communication method according to the present invention receives an object command from the object exchange layer of the primary station by receiving a request command from the primary station and issuing a response command in response to the request command. In a communication method in a secondary station having a layer, when a lower layer located below the object exchange layer receives a response command issued by the object exchange layer, the response command is transmitted to the primary station. It is characterized by not.

[0576] With the configuration and method described above, even when the object exchange layer of the secondary station issues an unnecessary response command, the secondary station power is not transmitted. For example, when the object exchange layer of the secondary station (for example, server device) is configured to always return a response command to the request command, the request command from the primary station (for example, client device) When a response command is not required, the lower layer does not send a response command issued by the object exchange layer of the secondary station.

[0577] Therefore, it is possible to reduce the power required for the transmission of the secondary station. In addition, when the secondary station transmits a response command, the primary station does not need a response command, so the response command from the secondary station may collide with the next request command of the primary station power. Can be prevented.

[0578] Further, in the communication device according to the present invention, the lower layer processing unit analyzes a response command issued by the object exchange layer processing unit, and the response analysis unit And a lower layer control unit that switches whether the response command is transmitted to the primary station or not to be transmitted depending on the type of response command analyzed by! /

[0579] With the above configuration, the lower layer can determine whether to transmit or not to transmit a response command issued by the object exchange layer depending on the type of response command.

[0580] Therefore, for example, when the object exchange layer communication protocol is OBEX (OBject EXchange protocol), do not send a CONTINUE response command to the PUT command. This can be done without changing the communication protocol of the layer.

[0581] Further, in the communication device according to the present invention, the lower layer processing unit includes a header information analysis unit that analyzes header information of a response command issued by the object exchange layer processing unit, and the header information analysis unit includes According to the type of the header information analyzed, it has a power to transmit the response command to the primary station, and a lower layer control unit that switches whether or not to transmit the response command.

[0582] With the above configuration, the lower layer can determine whether to transmit or not to transmit a response command issued by the object exchange layer according to the type of header information of the response command.

[0583] Thus, for example, when the communication protocol of the object exchange layer is OBEX (OBject EXchange protocol), do not send a CONTINUE response command to the PUT command. This can be done without changing the communication protocol of the layer.

[0584] Further, a communication system according to the present invention includes the communication device as a secondary station, and the communication device as a primary station that transmits an object to the communication device.

[0585] According to the above communication system, when the request command from the primary station is a V command that does not require a response command, the lower layer does not transmit the response command issued by the object exchange layer of the secondary station.

[0586] Therefore, even a conventional communication protocol in which the object exchange layer of the secondary station performs object exchange by the request command Z response command can be changed. It is possible to exchange objects with the primary station that receives only the minimum necessary response commands.

[0587] Further, in the communication device according to the present invention, the communication protocol of the object exchange layer is OB.

It is characterized by EX (OBject EXchange protocol).

[0588] With the above configuration, the object exchange protocol is replaced with an object that does not have a transmission function without changing the OBEX standard that has already been widely adopted for IrDA, Blue tooth (registered trademark), etc. Is possible.

[0589] Note that in this case, the communication device may be realized by a computer. In this case, communication of the communication device that realizes the communication device by the computer by operating the computer as each unit of the communication device. A program and a computer-readable recording medium on which the program is recorded also fall within the scope of the present invention.

[0590] The communication device may be realized by a communication circuit functioning as each of the above-described units.

[0591] In addition, the communication device is suitable for a mobile phone that performs communication using the communication device. According to the above mobile phone, it is possible to perform communication with high transfer efficiency using an object exchange protocol (including OBEX).

[0592] The communication device is suitable for a display device that displays data based on data received by the communication device. According to such a display device, communication can be performed with high transfer efficiency using an object exchange protocol (including OBEX).

[0593] Further, the communication apparatus is suitable for a printing apparatus that performs printing based on data received by the communication apparatus. According to such a printing apparatus, it is possible to perform communication with high transfer efficiency using an object exchange protocol (including OBEX).

[0594] Further, the communication device is suitable for a recording device for recording data received by the communication device. According to such a recording apparatus, it is possible to perform communication with high transfer efficiency using an object exchange protocol (including OBEX).

[0595] Finally, the communication device of the present invention may be configured as follows.

[0596] (1. Communication method that performs pseudo response under OBEX)

The communication method according to the present invention includes a request command transmitted by a device requesting a command. On the other hand, using each communication protocol in a hierarchical structure having at least an object exchange protocol for exchanging objects by receiving a response command sent back by the responding device in response to the request. A communication method for performing communication, wherein a communication protocol of a layer located below a layer corresponding to the object exchange protocol is configured to receive the request command issued by the object exchange protocol. A pseudo response command corresponding to a response command to the request command conforming to the tag exchange protocol is generated, and notification is made to a layer corresponding to the object exchange protocol, which is an upper layer.

[0597] (2. Communication equipment that responds under OBEX)

In the communication device according to the present invention, the client device receives a response command that is returned by the Sano device that responds to the request command transmitted by the client device requesting the command in response to the request command. Thus, an object exchange layer processing unit for exchanging objects and a lower layer processing unit for communication located in a lower layer than the object exchange layer processing unit, the lower layer processing unit includes the response layer. A pseudo response command corresponding to the command is generated and a response generation unit for notifying the object exchange layer processing unit and a request command generation notification from the object exchange layer processing unit are received, and a pseudo response command is generated. A lower layer control unit that controls the response generation unit to notify the object exchange layer processing unit. Featuring Rukoto, Ru

[0598] According to the above method and configuration, a pseudo-response command is generated on the client device side and notified to the object exchange protocol and the object exchange layer processing unit. Without changing the protocol that performs this, the object can be exchanged with a server device that does not have a transmission function but has a minimum required reception function. Further, in the above configuration and method, it is not necessary to change the object exchange protocol, so it is possible to divert existing assets.

[0599] (3. Communication method for pseudo response under OBEX (timer management))

Further, another communication method according to the present invention provides a response command returned by a device responding to a request command transmitted by a device requesting a command in response to the request. A communication method for performing communication using each of the hierarchical communication protocols having at least an object exchange protocol for exchanging objects by receiving the data, wherein a layer corresponding to the object exchange protocol is provided. The communication protocol located at the lower level is a predetermined period from when the request command issued by the object exchange protocol is issued to the communication protocol located at the lower layer until the response to the request command from the counterpart device is received. When a period of time elapses, a pseudo response command corresponding to the response command to the request command conforming to the object exchange protocol is generated, and notification is made to the layer corresponding to the object exchange protocol, which is an upper layer It is characterized by that.

[0600] (4. Communication device that performs pseudo-response under OBEX (timer management))

In another communication apparatus according to the present invention, the client device sends a response command returned by the server device responding to the request command to the request command transmitted by the client device requesting the command. An object exchange layer processing unit for exchanging objects by receiving and a lower layer processing unit for communication located at a lower layer than the object exchange layer processing unit, wherein the lower layer processing unit includes: Generates a pseudo response command corresponding to the response command and notifies the object exchange layer processing unit, and operates upon receiving a request command generation notification from the object exchange layer processing unit. A timer for measuring the elapsed time, and even if the elapsed time of the timer reaches a preset value, A lower layer control unit that controls the response generation unit to generate a pseudo response command and notify the object exchange layer processing unit when the response command is unreceived.ヽ.

[0601] According to the above method and configuration, in communication with a device having a transmission function, object exchange by a conventional request command / response command can be performed, and in communication with a device having no transmission function, a lower layer It is possible to perform object exchange by generating a pseudo response command and notifying the object exchange protocol, which is an upper layer, or the object exchange layer processing unit.

[0602] (5. Communication method that performs pseudo response under OBEX (command type)) In addition, another communication method according to the present invention receives a response command sent back by a device that responds to a request command transmitted by a device requesting a command in response to the request command. A communication method for performing communication using each hierarchical communication protocol having at least an object exchange protocol for exchanging objects, wherein the communication is positioned below a layer corresponding to the object exchange protocol. The protocol includes a power for receiving a response to the request command from the counterpart device according to the type of the request command when the request command for the object exchange protocol is issued, and the object exchange protocol. Generate a pseudo response command corresponding to the response command for the request command conforming to A feature to switch whether to notify the layer corresponding to an object replacement protocol, Ru.

[0603] (6. Communication device that performs pseudo-response under OBEX (command type))

In another communication apparatus according to the present invention, the client device sends a response command returned by the server device responding to the request command to the request command transmitted by the client device requesting the command. An object exchange layer processing unit for exchanging objects by receiving and a lower layer processing unit for communication located at a lower layer than the object exchange layer processing unit, wherein the lower layer processing unit includes: When a request command is issued from a response generation unit for generating a pseudo response command corresponding to the response command and notifying the object exchange layer processing unit, and the object exchange protocol, the request command is issued. Depending on the type of command, a response to the request command from the other device is received, or the response generator To produce a similar response command, possess a lower layer control unit that switches whether to notify the object exchange layer processing section! /, Characterized by that!

[0604] According to the above method and configuration, for example, communication reliability can be improved by receiving from the server device only the minimum necessary response commands such as when a connection is requested, when a disconnection is requested, and when a final data transfer is requested. As a response command to a data transfer request other than at the time of final data transfer request does not need to be received, the circuit scale can be reduced.

[0605] (7. Communication method for pseudo-response under OBEX (see OBEX header)) In addition, another communication method according to the present invention receives a response command returned by a device that responds to a request command transmitted by a device requesting a command in response to the request command. A communication method for performing communication using each hierarchical communication protocol having at least an object exchange protocol for exchanging objects, the communication being located in a lower layer corresponding to the object exchange protocol The protocol has the ability to receive a response command to the request command from the counterpart device according to the type of the header information by referring to the header information of the request command issued by the object exchange protocol. Corresponds to the response command for the request command conforming to the object exchange protocol Similar to generate a response command, it is characterized that you switch between whether to notify the corresponding layer to the object exchange protocol which is an upper layer.

[0606] (8. Communication device that responds under OBEX (see OBEX header))

In another communication apparatus according to the present invention, the client device sends a response command returned by the server device responding to the request command to the request command transmitted by the client device requesting the command. An object exchange layer processing unit for exchanging objects by receiving and a lower layer processing unit for communication located at a lower layer than the object exchange layer processing unit, wherein the lower layer processing unit includes: A response generation unit for generating a pseudo response command corresponding to the response command and notifying the object exchange layer processing unit, and a header for analyzing header information of the request command issued for the object exchange protocol Depending on the type of header information analyzed by the information analysis unit and the header information analysis unit, a request command from the counterpart device And a lower layer control unit that switches whether to generate a pseudo response command to the response generation unit and notify the object exchange layer processing unit of the response generation unit. As a feature.

[0607] According to the above method and configuration, for example, communication reliability can be improved by receiving from the server device only the minimum necessary response commands such as when a connection is requested, when a disconnection is requested, and when a final data transfer is requested. Since there is no need to perform reception processing for response commands to data transfer requests other than at the time of final data transfer request, The road scale can be reduced.

[0608] (9. Communication method that does not propagate response from OBEX to lower layer under OBEX)

In addition, another communication method according to the present invention receives a response command sent back by a device that responds to a request command transmitted by a device requesting a command in response to the request command. A communication method for performing communication using each hierarchical communication protocol having at least an object exchange protocol for exchanging objects, wherein the layer is located below a layer corresponding to the object exchange protocol. This communication protocol is characterized in that it does not transmit the response command when it receives the response command issued by the object exchange protocol.

[0609] (10. Communication device that does not propagate response from OBEX to lower layer under OBEX)

Further, another communication device according to the present invention sends a response command returned by the server device responding to the request command to the request command transmitted by the client device requesting the command to the client device. An object exchange layer processing unit for exchanging objects upon reception by the device, and a lower layer processing unit for communication located in a lower layer than the object exchange layer processing unit, the lower layer processing unit When receiving the response command issued from the object exchange layer processing unit, the response command is not transmitted to the opposite station.

[0610] According to the above method and configuration, for example, in a protocol for object exchange that does not require a response command to be returned in response to a request command from the client equipment side, the client equipment side tries to exchange objects. If the object exchange protocol on the server device side implements a response command in response to the request command, the object exchange protocol control unit on the server device side is By not transmitting in response to powerful transmission requests, the power required for transmission can be reduced. If the server device sends a response command, the client device does not need a response command, so the response command from the server device and the next request command from the client device may collide, This can be prevented.

[0611] (11. Communication method that does not propagate response from OBEX to lower layer under OBEX (command type)) In addition, another communication method according to the present invention receives a response command sent back by a device that responds to a request command transmitted by a device requesting a command in response to the request command. A communication method for performing communication using each hierarchical communication protocol having at least an object exchange protocol for exchanging objects, wherein the communication is positioned below a layer corresponding to the object exchange protocol. When a protocol response response command for object exchange is issued, the protocol may or may not transmit the response command to the other device according to the type of the response command. Features switching between what to do! / Speak.

[0612] (12. Communication device that does not propagate response from OBEX to lower layer under OBEX (command type))

Further, another communication device according to the present invention sends a response command returned by the server device responding to the request command to the request command transmitted by the client device requesting the command to the client device. An object exchange layer processing unit for exchanging objects upon reception by the device, and a lower layer processing unit for communication located in a lower layer than the object exchange layer processing unit, the lower layer processing unit Has a response analysis unit for analyzing the response command issued by the object exchange layer processing unit, and transmits the response command to the opposite device according to the type of response command analyzed by the response analysis unit. And a lower layer control unit that switches whether to transmit or not to transmit.

[0613] According to the above method and configuration, it becomes possible for the lower layer to determine whether to send or not to send a response command issued by the object exchange protocol depending on the type of response command. For example, it is possible to perform processing such as not transmitting a CONTINUE response command for the above-mentioned non-final PUT command without changing the upper OBEX layer.

[0614] (13. Communication method that does not propagate response from OBEX to lower layer under OBEX (refer to OBEX header))

Further, another communication method according to the present invention provides a response command returned by a device responding to a request command transmitted by a device requesting a command in response to the request. A communication method for performing communication using each of the hierarchical communication protocols having at least an object exchange protocol for exchanging objects by receiving the data, wherein a layer corresponding to the object exchange protocol is provided. The communication protocol located at the lower level is configured to transmit the response command to the counterpart device according to the type of the header information by referring to the header information of the response command issued. It is characterized by switching whether to transmit or not transmit.

[0615] (14. Communication devices that do not propagate responses from OBEX to lower layers under OBEX (see OBEX header))

Further, another communication device according to the present invention sends a response command returned by the server device responding to the request command to the request command transmitted by the client device requesting the command to the client device. An object exchange layer processing unit for exchanging objects upon reception by the device, and a lower layer processing unit for communication located in a lower layer than the object exchange layer processing unit, the lower layer processing unit Has a header information analysis unit that analyzes the header information of the response command when receiving the response command issued by the object exchange processing unit, and the header information that the header information analysis unit has prayed for A lower layer control unit that switches whether or not to transmit the response command to the opposite device according to the type of the device. As! /

[0616] According to the above method and configuration, it becomes possible for the lower layer to determine whether to send or not to send a response command issued by the object exchange protocol depending on the type of response command. For example, it is possible to perform processing such as not transmitting a CONTINUE response command for the above-mentioned non-final PUT command without changing the upper OBEX layer.

[0617] (15. Communication method that does not require a response in the OBEX layer)

Further, another communication method according to the present invention is a communication method for transmitting an object to an opposite station using an object exchange protocol OBEX (OBject Exchange protocol). After transmitting an OBEX command, an OBEX response from the opposite station is transmitted. It is characterized by sending the next OBEX command without receiving it.

[0618] (16. Communication method that does not require a response only during one-way transmission) Another communication method according to the present invention further includes a bidirectional communication method that does not require an OBEX response from the opposite station and a bidirectional communication that requires an OBEX response from the opposite station after the transmission of the OBEX command. Only when the one-way communication is selected, the next OBEX command may be transmitted without receiving the OBEX response from the opposite station after the OBEX command is transmitted. .

[0619] (17. Communication device that does not require a response in the OBEX layer)

In addition, another communication device according to the present invention further includes a communication device having an OBEX layer processing unit capable of transmitting an object to an opposite station using an object exchange protocol OBEX (OBject Exchange protocol). The layer processing unit is characterized in that after generating and transmitting an OBEX command, the next OBE X command is generated and transmitted without receiving an OBEX response from the opposite station.

[0620] (18. Communication device that does not require a response only during one-way transmission)

Another communication apparatus according to the present invention further includes a two-way communication that requires an OBEX response from the opposite station and an OBEX response from the opposite station, particularly after the OBEX command is transmitted. A communication method switching unit for switching directional communication, and only when the communication method switching unit selects one-way communication, after generating and transmitting the OBE X command, receiving an OBEX response from the opposite station Let's generate and send the next OBEX command.

[0621] According to the above method and configuration, for example, in one-way communication using OBEX, the client device side cannot receive a response command of the server in response to a request command of the client device side force. It is possible to send objects via OBEX. In bidirectional communication, communication to confirm the response from the server is performed. In one-way communication, communication can be performed without a response from the server, and bidirectional communication and one-way communication are performed in one OBEX. It can be realized with a protocol.

[0622] (19. Communication method that does not require a response for Put commands other than Final)

Further, another communication method according to the present invention is a communication method for transmitting an object to an opposite station using an object exchange protocol OBEX (OBject Exchange protocol). OBEX response from It is characterized by sending a non-final Put command or a final Put command of the next OBEX without receiving it.

[0623] (20. Communication device that does not require a response for Put commands other than Final)

Further, another communication device according to the present invention is a communication device having an OBEX layer processing unit capable of transmitting an object to an opposite station using an object exchange protocol OBEX (OBject Exchange protocol). Only after generating and sending a non-final Put command of OBEX, without receiving an OBEX response from the opposite station, generate and send the final OBEX !, Put command or final Put command. It is a feature.

[0624] According to the method and configuration described above, it is possible to realize object exchange that does not require only the CONTINUE response command to the PUT command described above.

[0625] (21. Communication method that does not send response in OBEX layer)

Another communication method according to the present invention is an OBEX response always received after receiving an OBEX command from the opposite station in a communication method for receiving an opposite station power object using the object exchange protocol OBEX (OBject EXchange protocol). It is characterized by not transmitting.

[0626] (22. A communication method that does not send a response on the OBEX layer only during one-way reception)

Further, the other communication method according to the present invention further does not require the two-way communication that requires the OBEX response from the opposite station and the OBEX response from the opposite station after the transmission of the OB EX command. Only when the one-way communication is selected and the one-way communication is selected, do not always send an OBEX response to the opposite station after receiving the OBEX command!

[0627] (23. Communication device that does not send response in OBEX layer)

Further, another communication apparatus according to the present invention is a communication apparatus having an OBE X layer processing unit capable of receiving an object from an opposite station using an object exchange protocol OBEX (OBject Exchange protocol). The processing unit is characterized in that it always does not send an OBEX response after receiving the OBE X command of the opposite station power.

[0628] (24. A communication device that does not send a response on the OBEX layer only during one-way reception) Further, the other communication apparatus according to the present invention further does not require bidirectional communication that requires an OBEX response from the opposite station and an OBEX response from the opposite station, particularly after the transmission of the OB EX command, in the communication apparatus described above. A communication method switching unit for switching one-way communication may be provided, and only when the communication method switching unit selects one-way communication, an OBEX response may not always be transmitted to the opposite station after receiving the OBEX command.

[0629] According to the above method and configuration, for example, in one-way communication using OBEX, when the client device side does not need to send a response command on the server device side to the request command on the client device side force, It is possible to control such that unnecessary response commands are not generated and transmitted. In bidirectional communication, a response command can be sent to the client device to check the communication on the client device. In one-way communication, unnecessary response commands are generated to the client device. And it becomes possible not to transmit, and bi-directional communication and one-way communication can be realized with one OBEX protocol.

[0630] (25. Communication method that does not respond only to Put commands other than Final)

In addition, another communication method according to the present invention is a communication method for receiving an object from an opposite station using the object exchange protocol OBEX (OBject Exchange protocol). When a non-final Put command is received, an OBEX response is received. It is characterized in that the OBEX response is transmitted when the final Put command is received without transmission.

[0631] (26. Communication device that does not respond only to Put commands that are not Final)

Further, another communication apparatus according to the present invention is a communication apparatus having an OBE X layer processing unit capable of receiving an object from an opposite station using an object exchange protocol OBEX (OBject Exchange protocol). The processing unit does not transmit an OBEX response when receiving a Put command that is not the final OBEX, and generates and transmits an OBEX response when receiving the final Put command.

[0632] According to the above method and configuration, it is possible to generate only a CONTINUE response command for a non-final PUT command from the client device side and transmit it! Band efficiency can be improved. [0633] (27. Communication method where object exchange protocol is OBEX)

In the communication method, the object exchange protocol may be OBEX. According to the above method, the object exchange protocol has already been widely adopted in IrD A and Bluetooth (registered trademark), etc., and it has been exchanged with devices that do not have a transmission function without changing the OBEX standard. Is possible.

[0634] (28. Communication program)

The communication program of the present invention is a program that causes a computer to execute each procedure of each communication protocol of the communication method described in any of the above! / The above communication method can be realized by realizing each procedure of each communication protocol of the above communication method by a computer using the above communication program.

[0635] (29. Recording medium)

The recording medium of the present invention is characterized by being readable by a computer on which the communication program is recorded. According to the above configuration, the communication method can be realized on the computer by the communication program read from the recording medium.

[0636] (30. Communication system)

A communication system according to the present invention is a communication system for exchanging objects between a client device and a server device, wherein the server device cannot transmit a response response, and the client device A communication device according to any one of the above.

[0637] According to the communication system, even if the server device response response cannot be transmitted, the client device generates a pseudo response command and notifies the object exchange layer processing unit. Request command Exchange of objects with a Sano device with a minimum reception function that does not have a transmission function without changing the conventional communication protocol, such as object exchange by Z response command, is possible.

[0638] (31. Mobile phone)

A mobile phone as a communication device according to the present invention is characterized in that it is a mobile phone that realizes the above-mentioned communication! According to the above mobile phone, object exchange protocol Using col (including OBEX), one-way communication or communication with high transfer efficiency can be performed.

[0639] (32.Display device)

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

[0640] (33. Printing device)

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

[0641] (34. Recording device)

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

[0642] The specific embodiments or examples made in the detailed description of the invention are to clarify the technical contents of the present invention, and are limited to such specific examples. Therefore, various modifications may be made within the scope of the spirit of the present invention and the claims described below.

Industrial applicability

[0643] The communication device, communication system, communication method, communication program, and communication circuit of the present invention allow object exchange with a device (secondary station) that does not have a transmission function without changing the protocol for exchange outside the Obzier. Therefore, the present invention can be widely used for communication of, for example, a mobile phone, a PDA, and a personal computer. In particular, object exchange for exchanging objects between a client device that sends a request command and a server device that sends back a response command, such as infrared communication based on IrDA or wireless communication based on Bluetooth. This is suitable for communication employing a protocol.

Claims

The scope of the claims

[1] A communication device as a primary station having an object exchange layer that sends an object to the object exchange layer of a secondary station by issuing a request command and receiving a response command in response to the request command. There,

An object exchange layer processing unit that processes the communication protocol of the object exchange layer; and a lower layer processing unit that processes a communication protocol of a lower layer located below the object exchange layer;

The lower layer processing unit

A response generation unit that generates a pseudo response command simulating a response command from the secondary station and notifies the object exchange layer processing unit;

Upon receiving a request command generation notification from the object exchange layer processing unit, the response generation unit is controlled to generate the pseudo response command in response to the request command and notify the object exchange layer processing unit And a lower layer control unit.

[2] The lower layer processing unit further includes:

It operates upon receiving a request command generation notification from the object exchange layer processing unit, and has a timer for measuring elapsed time,

The lower layer control unit generates the pseudo response command when the response command from the secondary station is not received even when the elapsed time of the timer reaches a preset setting value, and the object exchange 2. The communication device according to claim 1, wherein the response generation unit is controlled to notify a layer processing unit.

[3] The lower layer control unit of the lower layer processing unit,

In response to the type of request command issued by the object exchange layer processing unit, the response command received from the secondary station is notified to the object exchange layer processing unit. 2. The communication device according to claim 1, wherein the communication unit switches whether to notify the object exchange layer processing unit.

[4] The lower layer processing unit further includes: A header information analysis unit for analyzing header information of a request command issued by the object exchange layer processing unit;

According to the type of header information analyzed by the header information analysis unit, the lower layer control unit notifies the response command received by the secondary local power to the object exchange layer processing unit, or to the response generation unit. 2. The communication apparatus according to claim 1, wherein the communication apparatus switches whether to generate a pseudo response command and to notify the object exchange layer processing unit.

[5] Communication as a secondary station having an object exchange layer that receives an object exchange layer force object of the primary station by receiving a request command having a primary station power and issuing a response command in response to the request command A device,

The lower layer processing unit

When receiving the response command issued by the object exchange layer processing unit, the communication device does not transmit the response command to the primary station.

[6] The lower layer processing unit

A response analysis unit that analyzes a response command issued by the object exchange layer processing unit;

A lower layer control unit that switches whether or not to transmit the response command to a primary station according to the type of response command analyzed by the response analysis unit. Item 6. The communication device according to item 5.

[7] The lower layer processing unit

A header information analysis unit for analyzing header information of a response command issued by the object exchange layer processing unit;

And a lower layer control unit for switching whether or not to transmit the response command to the primary station according to the type of header information analyzed by the header information analysis unit. The communication device according to claim 5.

[8] A communication method in a primary station having an object exchange layer that sends an object to the object exchange layer of a secondary station by issuing a request command and receiving a response command in response to the request command. And

When a lower layer located below the object exchange layer receives a request command generation notification from the object exchange layer, it generates a pseudo response command that simulates a response command from the secondary station that responds to the request command. And notifying the object exchange layer.

[9] Communication method in a secondary station having an object exchange layer that receives an object exchange layer force object of the primary station by issuing a response command in response to the request command in response to the request command of the primary station power Because

A communication method characterized in that when a lower layer located below the object exchange layer receives a response command issued by the object exchange layer, the response command is not transmitted to a primary station.

10. The communication device according to any one of claims 1 to 7, wherein a communication protocol of the object exchange layer is OBEX (OBject EXchange protocol).

[11] A communication device as a primary station according to any one of claims 1 to 4, and

A communication system comprising: a communication device as a secondary station that receives the communication device power outside the object.

12. The communication device as the secondary station does not transmit a response command.

The communication system according to 1.

[13] A communication device as a secondary station according to any one of claims 5 to 7,

A communication apparatus as a primary station for transmitting an object to the communication apparatus.

[14] A communication program for operating the communication device according to [1] above, wherein the computer operates as each of the above-described units.

15. A communication circuit for operating the communication device according to claim 1, wherein the communication device functions as each of the above-described units.

[16] The communication device according to any one of claims 1 to 7 is mounted and communicated by the communication device. A mobile phone characterized by performing communication.

[17] A display device comprising the communication device according to any one of [5] to [7], and displaying based on data received by the communication device.

18. A printing apparatus comprising the communication device according to any one of claims 5 to 7 and performing printing based on data received by the communication device.

[19] A recording device comprising the communication device according to any one of claims 5 to 7, and recording data received by the communication device.