WO2006080330A1 - Dispositif, systeme, procede, programme et circuit de communication - Google Patents

Dispositif, systeme, procede, programme et circuit de communication Download PDF

Info

Publication number
WO2006080330A1
WO2006080330A1 PCT/JP2006/301106 JP2006301106W WO2006080330A1 WO 2006080330 A1 WO2006080330 A1 WO 2006080330A1 JP 2006301106 W JP2006301106 W JP 2006301106W WO 2006080330 A1 WO2006080330 A1 WO 2006080330A1
Authority
WO
WIPO (PCT)
Prior art keywords
response
command
communication
processing unit
request
Prior art date
Application number
PCT/JP2006/301106
Other languages
English (en)
Japanese (ja)
Inventor
Koji Sakai
Hitoshi Naoe
Fumihiro Fukae
Shohei Osawa
Original Assignee
Sharp Kabushiki Kaisha
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from PCT/JP2005/014446 external-priority patent/WO2006013979A1/fr
Application filed by Sharp Kabushiki Kaisha filed Critical Sharp Kabushiki Kaisha
Priority to CN2006800006069A priority Critical patent/CN101006706B/zh
Priority to JP2007500532A priority patent/JP4394141B2/ja
Priority to US11/628,040 priority patent/US7787391B2/en
Publication of WO2006080330A1 publication Critical patent/WO2006080330A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability

Definitions

  • 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.
  • OBEX OBject EXchange protocol
  • 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).
  • 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
  • FIG. 7 shows the standard IrDA protocol stack.
  • the IrDA protocol stack includes IrPHY (IrDA Physical Layer), which defines modulation method, signal strength, directivity, etc.
  • IrPHY IrDA Physical Layer
  • 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
  • IrLMP IrDA Link Management Protocol
  • TinyTP Transport Protocol
  • 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.
  • the client device issues a request command such as Put ZGet to the server device, and the Sano device returns a response command.
  • 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.
  • the client 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.
  • 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.
  • the client device After establishing the connection, the client device starts exchanging objects, and transmits a PUT command for transmitting the object to the Sano device.
  • 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.
  • the server device has successfully received the last PUT command, it returns a SUCCES S response command to the client device.
  • the client device 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.
  • 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.
  • the server device returns a response command in response to a request command that requires a client device, and the object is exchanged.
  • 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.
  • 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.
  • 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,
  • 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.
  • the server device 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.
  • 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
  • OBEX is currently implemented in various devices, and if it is not easy to change the specifications, existing assets can be diverted. Disappear.
  • 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.
  • the communication device 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.
  • 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.
  • a lower layer below the object exchange layer generates a pseudo response command and notifies the object exchange layer.
  • 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.
  • a secondary station for example, a server device
  • object exchange protocol the communication protocol of the object exchange layer
  • a communication system 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.
  • the communication device 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.
  • the communication method 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.
  • 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.
  • the secondary station power can be prevented from being transmitted.
  • the object exchange layer of the secondary station for example, server device
  • the request command from the primary station for example, client device
  • the lower layer does not send a response command issued by the object exchange layer of the secondary station.
  • a communication system includes the communication device as a secondary station and the communication device as a primary station that transmits an object to the communication device.
  • the lower layer 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.
  • the communication device may be realized by a computer.
  • 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.
  • the communication device may be realized by a communication circuit functioning as each of the above-described units.
  • 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).
  • object exchange protocol including OBEX
  • 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).
  • object exchange protocol including OBEX
  • 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).
  • object exchange protocol including OBEX
  • 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).
  • object exchange protocol including OBEX
  • 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.
  • 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.
  • 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.
  • 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.
  • ⁇ 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.
  • a server in the communication system according to the ninth and tenth embodiments of the present invention 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.
  • 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.
  • 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.
  • 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.
  • 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 shows a data exchange sequence according to the embodiment of the present invention.
  • 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.
  • 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.
  • 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.
  • 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.
  • Client device (communication device, primary station)
  • Control unit (lower layer control unit)
  • OBEX layer processing unit object exchange layer processing unit
  • Control unit
  • Control unit lower layer control unit
  • Client equipment communication equipment, primary station
  • Application layer processing section
  • OBEX layer processing unit object exchange layer processing unit
  • Control unit
  • Control unit lower layer control unit
  • Control unit (lower layer control unit)
  • OBEX layer processing unit object exchange layer processing unit
  • Application layer processor 1320 OBEX Layer Processing Unit (Object Exchange Layer Processing Unit)
  • OBEX layer processing unit object exchange layer processing unit
  • 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.
  • the OSI 7 layer model is also called “OSI basic reference model” or “OSI hierarchical model”.
  • the first 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
  • the fifth layer (session layer) establishes and releases a virtual route (connection) for communication programs to send and receive data.
  • Layer 6 Presentation Layer
  • the seventh layer provides various services using data communication to humans and other programs.
  • Each communication layer of the communication system also has a function equivalent to the corresponding layer of the OSI7 layer model.
  • the communication system has a six-layer structure with one session layer and one presentation layer.
  • the communication layer including the session layer and the presentation layer is realized by OBEX (OBject EXchange protocol).
  • 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.
  • 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.
  • 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.
  • 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.
  • IrSimple is an application example of the present invention.
  • 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.
  • the data link layer, network layer, transport layer, session layer + presentation layer may be expressed as LAP, LMP, SMP, and OB EX, respectively.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the control unit 121 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the transmission unit 14 also responds to the request command transmitted to the server device 5.
  • the response command may not be returned because at least a part of the response notification unit or the response transmission unit is lacking.
  • inconvenience may occur if object exchange between the client device 1 and the server device 5 becomes impossible.
  • 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.
  • 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.
  • 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.
  • 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.).
  • 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.).
  • 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.
  • 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.
  • FIG. 4 shows the connection, data transfer, and disconnect transfer processing in the IrDA protocol stack.
  • 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.
  • control unit 121 in the OBEX layer processing unit 12 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.
  • the control unit 131 instructs the request notification unit 133 to issue a connection request command.
  • 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.
  • 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. .
  • the response generation unit 134 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.
  • 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.
  • the control unit 121 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.
  • each layer may constitute one block.
  • 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!
  • 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.
  • 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.
  • 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.
  • a pseudo-response command such as CONTINUE or SUCCESS for the request command in the lower layer processing unit 13
  • the client device 1 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.
  • 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.
  • 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.
  • connect 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.
  • maximum OBEX packet length Indicates the maximum OBEX packet length that each device can receive.
  • Table 4 shows examples of request commands and response commands.
  • Table 5 below shows the data structure of the request command in the case of 0x0800 2K max packet size and data transfer request.
  • 0x00001000 Length of object is 4K bytes
  • the client device (communication device) of the transfer data transfer system (communication system) 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.
  • 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.
  • 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.
  • the OBEX layer processing unit 22 includes a control unit 221, a request notification unit 222, and a response reception unit 223.
  • the control unit 221 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.
  • the application layer processing unit 21 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.
  • the request notification unit 222 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.
  • 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.
  • the received data is output to request notification section 233.
  • the request notification unit 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.
  • 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.
  • 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.
  • 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.
  • control unit 231 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.
  • 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.
  • FIG. 6 shows the connection, data transfer, and disconnection transfer processing in the IrDA protocol stack.
  • 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.
  • control unit 221 in the OBEX layer processing unit 22 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
  • 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.
  • the control unit 231 instructs the request notification unit 233 to issue a connection request command.
  • 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.
  • 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.
  • the receiving unit 25 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.
  • 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.
  • 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.
  • 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.
  • the control unit 221 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.
  • each layer may constitute one block.
  • 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! /
  • 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.
  • 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.
  • 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.
  • the client device 2 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.
  • the client device (communication device) of the transfer data transfer system (communication system) 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.
  • 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.
  • OBEX layer processing unit object exchange layer processing unit
  • 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).
  • an operation unit not shown
  • 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.
  • the control unit 321 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.
  • the request notification unit 322 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.
  • 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.
  • 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.
  • 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.
  • request reception unit 332 outputs the received data to request notification unit 333.
  • 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.
  • 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.
  • Response notifying section 335 outputs the response command output from multiplexer 337 to OBEX layer processing section 32.
  • the response generation unit 336 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 12 shows the connection, data transfer, and disconnect transfer processing in the IrDA protocol stack.
  • 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.
  • 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.
  • the request notification unit 322 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the control unit 331 instructs the request notification unit 333 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.
  • 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.
  • 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.
  • control unit 331 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
  • 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.
  • the response notification 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.
  • the control unit 321 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.
  • each layer may constitute one block.
  • 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.
  • the client device 3 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 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.
  • 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.
  • OBEX layer processing unit object exchange layer processing unit
  • 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).
  • an operation unit not shown
  • predetermined processing is performed in accordance with the received response command.
  • the OBEX layer processing unit 42 includes a control unit 421, a request notification unit 422, and a response reception unit 423.
  • the control unit 421 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.
  • the application layer processing unit 41 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.
  • the request notification unit 422 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the response receiving unit 434 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.
  • the response generation unit 436 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.
  • 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.
  • 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.
  • the response receiving unit 434 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.
  • the control unit 431 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.
  • 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.
  • 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.
  • FIG. 12 shows the connection, data transfer, and disconnect transfer processing in the IrDA protocol stack.
  • 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.
  • 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.
  • the request notification unit 422 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.
  • 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.
  • 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.
  • the control unit 431 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.
  • 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.
  • 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.
  • 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.
  • the multiplexer 437 is controlled so as to perform normal reception processing.
  • 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.
  • the response notification unit 435 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.
  • the control unit 421 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.
  • each layer may constitute one block.
  • 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! /
  • generating a pseudo-response command for the OBEX layer processing unit 42 eliminates the trouble of adding extra header information and deleting it. This is preferable because it saves time and effort.
  • the client device 4 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.
  • connection request disconnection request
  • 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.
  • the server device (communication device) of the transfer data transfer system (communication system) 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.
  • 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.
  • 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).
  • an operation unit not shown
  • 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.
  • the response notification unit 1022 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.
  • 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.
  • control unit 1031 controls the response reception unit 1032 and the request analysis unit 1035. Details will be described later.
  • 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.
  • the request analysis unit 1035 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • control unit 1 of the lower layer processing unit 1030 of the present embodiment In contrast, as shown in FIG. 15, the control unit 1 of the lower layer processing unit 1030 of the present embodiment.
  • control unit 1031 of the lower layer processing unit 1030 of the present embodiment will be described using the flowchart shown in FIG.
  • Step S21 is a step of determining whether or not a request command is received from the client. If received, go to step S22.
  • 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.
  • control unit 1031 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.
  • FIG. 16 shows the exchange of commands between the client device and the server device in the present embodiment.
  • 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.
  • the server device (communication device) of the transfer data transfer system (communication system) 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.
  • 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).
  • an operation unit not shown
  • predetermined processing is performed according to the received request command.
  • 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.
  • the response notification unit 1122 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.
  • 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.
  • the request analysis unit 1135 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.
  • 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.
  • Transmitting section 1140 transmits the response command received from lower layer processing section 1030 to the outside via the infrared communication path.
  • 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.
  • 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.
  • step S32 the OBEX layer processing unit 112 receives the request command received also by the client device capability.
  • step S33 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.
  • 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.
  • 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.
  • 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.
  • FIG. 19 shows the exchange of commands between the client device and the server device in the present embodiment.
  • a specific response command 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • a specific response command to the request command from the client device 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.
  • 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.
  • the client device (communication device) of the transfer data transfer system (communication system) 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. 21 is a block diagram of a client device that performs communication using the conventional OBEX protocol.
  • 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.
  • 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).
  • the OBEX layer processing unit 1220 includes a control unit 1221, a request notification unit 1222, and a response reception unit 1223. And.
  • the control unit 1221 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.
  • the request notification unit 1222 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.
  • 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.
  • the transmission unit 1240 transmits the request command received from the lower layer processing unit 1230 to the outside via the infrared communication path.
  • 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.
  • control unit 1221 of the OBEX layer processing unit 1220 in FIG. 21 will be described using the flowchart shown in FIG.
  • 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.
  • 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.
  • Step S54 is a step of analyzing the received response command. After the analysis is completed, the process goes to step S55.
  • 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.
  • 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.
  • the client device 1300 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.
  • 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.
  • 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.
  • FIG. 23 is a block diagram of client device 1300 according to the present embodiment.
  • 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.
  • 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.
  • 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.
  • 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.
  • control section 1321 of OBEX layer processing section 1320 of client device 1300 will be described using the flowchart of FIG.
  • 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.
  • 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.
  • 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.
  • Step S75 is a step of determining whether or not to end communication in bidirectional communication. If not, the process returns to step S71.
  • 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.
  • 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.
  • 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.
  • the client device (communication device) of the transfer data transfer system (communication system) 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.
  • control unit 1321 of OBEX layer processing unit 1320 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • Step S96 is a step of determining whether or not the communication is terminated. If not, the process returns to step S91.
  • 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.
  • the server of the transfer 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.
  • Fig. 27 shows a block diagram of a server device that performs communication using the conventional OBEX protocol.
  • the Sano device (communication device) 1400 includes an application layer processing unit 14
  • 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.
  • 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).
  • the OBEX layer processing unit 1420 includes a control unit 1421, a response notification unit 1422, and a request analysis unit 1423.
  • control unit 1421 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.
  • response notification unit 1422 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Step S102 is a step of analyzing a request command for a client device.
  • 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.
  • Step S104 is a step of transmitting the response command to the client device.
  • step S105 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.
  • 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.
  • 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.
  • 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.
  • Step S112 is a step of analyzing the received request command. After the analysis is completed, the process proceeds to step S115.
  • Step S115 is a step of determining whether or not the communication has ended. If not completed, the process proceeds to step S111 again.
  • FIG. 29 is a block diagram of server device 1500 according to another embodiment of the present invention.
  • 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.
  • 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.
  • 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.
  • 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.
  • control unit 1521 of the OBEX layer processing unit 1520 of the server device 1500 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the server device (communication device) of the transfer data transfer system (communication system) 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.
  • control unit 1521 of OBEX layer processing unit 1520 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Step S146 is a step of determining whether or not the communication is terminated. If not, the process proceeds to step S141.
  • 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.
  • 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.
  • 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.
  • 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.
  • data in mobile phone A is transmitted to mobile phone B using infrared rays.
  • 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.
  • the sending client device (mobile phone A) is not the last OBEX layer.
  • the next Put command without waiting for a CONTINUE response command.
  • 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.
  • 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.
  • the OBEX layer 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.
  • a SUCCESS response command is generated and sent.
  • 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.
  • the OBEX layer 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.
  • 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)!
  • 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.
  • the sending client device uses OBEX.
  • the layer is not final, when sending a Put command, the next Put command is sent without waiting for the CONTINUE response command.
  • the SUCCESS response command of the receiving server device display device B
  • 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.
  • the OBEX layer receives the Put command from the sending client device (mobile phone A)
  • the CONTINUE response command is not generated or transmitted.
  • a SUCCESS response command is generated and sent.
  • 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.
  • the sending client device does not wait for the response command from the server device when the OBEX layer sends all request commands. Send a request command.
  • 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.
  • the OBEX layer 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.
  • the mobile device A and the printing device B 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.
  • the printing apparatus B may be a client device (transmitter) and the mobile phone A may be a server device (receiver)!
  • 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.
  • the sending client device (mobile phone A) is not the last OBEX layer.
  • the next Put command without waiting for a CONTINUE response command.
  • 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.
  • 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.
  • the OBEX layer receives the Put command from the sending client device (cell phone A)
  • the CONTINUE response command is not generated or transmitted.
  • a SUCCESS response command is generated and sent.
  • 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.
  • 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.
  • 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.
  • the OBEX layer 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.
  • 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.
  • the mobile device A and the recording device B are used for the client device (transmitter) and the Sano device (receiver), respectively.
  • 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.
  • the recording device B may be a client device (transmitter) and the mobile phone A may be a server device (receiver).
  • 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.
  • the sending client device (cell phone A) is not the final OBEX layer.
  • the next Put command without waiting for a CONTINUE response command.
  • the final Put command it waits for the SUCCESS response command from the receiving server device (recording device B) to check whether communication has been performed normally.
  • 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.
  • the receiving server device 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).
  • the final Put command is received, a SUCCESS response command is generated and sent.
  • 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.
  • the sending client device mobile phone A
  • 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.
  • the OBEX layer receives all request commands from the sending client device (mobile phone A), it does not generate or send a response command.
  • 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.
  • 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.
  • 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.
  • the above communication system has a 6-layer structure with one session layer and one presentation layer.
  • IrSimple is an application example of the present invention.
  • the present invention is not limited to IrSimple.
  • IrSimple is an improvement on some of the functions of conventional IrDA.
  • 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.
  • LAP LAP
  • SMP SMP
  • OBEX OBEX
  • 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).
  • 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).
  • 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.
  • the search and connection sequence which conventionally required multiple packets, can be performed with one packet pair.
  • 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).
  • the UA response (UA response for SNRM in FIG. 38 (c)) is not required.
  • 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.
  • connections of all communication layers are connected by one communication
  • the present invention is not limited to this.
  • the remaining plurality of communication layers may be connected.
  • 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.
  • 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).
  • 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.
  • 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.
  • the transmitter transmits a packet with the flag turned on after transmitting a predetermined number of packets.
  • 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.
  • 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.
  • the transmitter 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.
  • a UI frame (Fig. 40 (b)) is used.
  • the data link layer LAP layer cannot recognize missing packets and detects them in the transport layer.
  • 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.
  • 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).
  • the transmitter assigns a sequence number to the packet and transmits all data continuously.
  • 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.
  • the receiver recognizes that it has failed to receive normally in the receiver and performs the following operations.
  • the next operation is an indicator to notify the user that the failure has occurred or a state of waiting for the next reception.
  • 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).
  • the disconnection sequence which conventionally required a plurality of packets, can be performed with one packet pair.
  • 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).
  • the UA response (UA response in Fig. 42 (c)) is not required.
  • the data link layer is denoted as LAP
  • the network layer is denoted as LAMP
  • the transport layer is denoted as TTP or SMP
  • the session layer and the presentation layer are denoted as OBEX.
  • P is added to the transmitter and “S” is added to the receiver.
  • LAP (P) means the data link layer of the transmitter.
  • 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).
  • 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.
  • 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
  • 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.
  • 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 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).
  • 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).
  • LSAP Link Service Access Point
  • 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.
  • 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.
  • SMP (S) In response to the connection request function from OBEX (S), SMP (S) enters a reception standby state.
  • SMP (S) 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.
  • SMP (S) receives a connection response function from OBEX (S)
  • a connection response function is generated for LMP (S), and SMP layer negotiation is terminated.
  • LMP (S) 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.
  • LSAP Link Service Access Point
  • LMP Link Service Access Point
  • LAP (S) receives a connection request function with LMP (S) power and enters a reception standby state.
  • 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.
  • the connection request function containing the data to the LMP (S) 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).
  • 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.
  • 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).
  • 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).
  • 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).
  • 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.
  • 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).
  • 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).
  • LSAP Link Service Access Point
  • the connectionless value is used as a fixed value for LSAP. This eliminates the need to exchange LMP connection parameters.
  • 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.
  • LAP (P) terminates the LA p layer negotiation, assuming that it has negotiated with the transmitted parameters when it outputs the SNRM command.
  • LAP (P) sends a connection confirmation function to LMP (P).
  • 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
  • SMP (S) receives a connection request function from OBEX (S) and enters a reception standby state.
  • SMP (S) receives a connection notification function from the lower layer (SMP (S))
  • SMP (P) extracts the parameter generated by SMP (P) of the transmitter from the function data, Use to complete the negotiation.
  • 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).
  • LMP (S) 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).
  • LAP lower layer
  • LSAP Link Service Access Point
  • LMP Link Service Access Point
  • 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).
  • 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).
  • the transmitter 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)). .
  • the receiver receives the data and sends a notification to the upper layer.
  • SMP (SMP
  • the transmitter 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.
  • the transmitter 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.
  • OBEX (P) outputs a PUT command as a data transmission function to the lower layer.
  • 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.
  • 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.
  • 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.
  • OBEX receives the data by receiving the data notification function for the lower layer force.
  • OBEX 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.
  • 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.
  • SMP 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.
  • 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.
  • the SMP 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! / ,.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • SMP (S) 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. .
  • 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).
  • SMP (S) 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.
  • the LMP 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. .
  • 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.
  • the LMP header contains an LSAP containing a connectionless value.
  • the LAP 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.
  • 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.
  • the LAP header text includes a connection address and a UI indicator.
  • 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).
  • the transmitter In this embodiment (no response), the transmitter generates a PUT command, which is transmitted to the lower layer and output as a UI frame.
  • the receiver receives data and sends notifications to higher layers.
  • SMP SMP
  • the transmitter turns on the flag indicating the end of data and transmits the data.
  • OBEX (P) 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.
  • 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.
  • the SMP 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.
  • 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.
  • 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.
  • 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! / ,.
  • the SMP (P) of the transmitter converts the data transmission function of OBEX (P) force into a data transmission function to LMP (P).
  • OBEX (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).
  • 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.
  • 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.
  • SMP (S) analyzes the SMP header and confirms that reception has been successful, it issues a data transmission function to LMP (S).
  • 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.
  • 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.
  • the LMP (S) of the receiver 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.
  • the LMP header contains an LSAP containing a connectionless value.
  • the LAP (P) of the transmitter 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.
  • the LAP (S) of the receiver when receiving the data reception notification from the physical layer, 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.
  • the LAP header includes a connection address and a UI indicator.
  • 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).
  • 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.
  • 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
  • SMP (P) 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)).
  • LMP (P) lower layer
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • OBEX (S) 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.
  • the disconnect notification function Indication
  • SMP (S) lower layer
  • the SMP (S) 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.
  • 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)
  • a disconnect response function is generated for L MP (S), and the SMP layer disconnection process is terminated.
  • the LMP (S) force 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 .
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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).
  • SMP (P) 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.
  • 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.
  • 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!
  • SMP (S) 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!
  • the LMP (S) force 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)!
  • the LAP (S) 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!
  • 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).
  • 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.
  • Qos notifies the specification of negotiation parameters such as baud rate determined by LAP and negotiation results to higher layers including OBEX.
  • OBEX (P) Operates according to the Z-unnecessary specification, so bidirectional Z one-way connection is possible.
  • Figs. 52 to 56 show the connection sequence (Fig. 43) of this embodiment (response is sent).
  • the data to be transmitted to the receiver and the data of QoS-1 are transmitted by con.req (data) (Fig. 43). Pass from layer to lower layer.
  • the receiver passes only QoS-2 (QoS requested by the receiver) data from the upper layer to the lower layer by con.req.
  • 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.
  • 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.
  • the data to be transmitted to the receiver and the data of QoS-1 are transmitted by con.req (data) (Fig. 45). Pass from layer to lower layer.
  • the LAP (P) of the transmitter stores QoS-1 as it is as QoS-3.
  • 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.
  • 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.
  • the receiver sets the QoS-1 of the transmitter to QoS-3.
  • the parameters of QoS-2 are not satisfactory in combination with QoS-1, it cannot be received.
  • LAP 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.
  • the application indicates whether there is a response or not, and the application uses the above QoS-1 and QoS-2 as upper layers.
  • 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.
  • the application is used as a reference, for example, in the case of a slide show, no response may be automatically selected.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • a program code execution format program, intermediate code program, source program
  • 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.
  • 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.
  • 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.
  • 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.
  • the communication device 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.
  • the pseudo response command responding to the request command Generated are characterized by having a lower layer control unit which controls the response generation unit to notify the object exchange layer processing unit.
  • 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.
  • 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.
  • object exchange with a secondary station for example, server equipment
  • a secondary station for example, server equipment
  • a secondary station for example, server equipment
  • the communication device 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.
  • 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 .
  • 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.
  • 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.
  • 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.
  • 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.
  • a communication system 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.
  • the communication device 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.
  • the communication method 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.
  • 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.
  • the secondary station power is not transmitted.
  • the object exchange layer of the secondary station for example, server device
  • the request command from the primary station for example, client device
  • the lower layer does not send a response command issued by the object exchange layer of the secondary station.
  • 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! /
  • 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.
  • the object exchange layer communication protocol is OBEX (OBject EXchange protocol)
  • OBEX OBject EXchange protocol
  • 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.
  • 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.
  • a communication system includes the communication device as a secondary station, and the communication device as a primary station that transmits an object to the communication device.
  • the lower layer 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.
  • the communication protocol of the object exchange layer is OB.
  • 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.
  • the communication device may be realized by a computer.
  • 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.
  • the communication device may be realized by a communication circuit functioning as each of the above-described units.
  • 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).
  • object exchange protocol including OBEX
  • 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).
  • object exchange protocol including OBEX
  • 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).
  • object exchange protocol including OBEX
  • 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).
  • object exchange protocol including OBEX
  • the communication device of the present invention may be configured as follows.
  • the communication method includes a request command transmitted by a device requesting a command.
  • 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.
  • 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.
  • 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.
  • 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.
  • Another communication method 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Another communication method 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.
  • 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.
  • 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.
  • 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.
  • the circuit scale can be reduced.
  • Another communication method 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.
  • 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.
  • 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.
  • 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.
  • another communication method 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.
  • another communication 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 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.
  • 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.
  • Another communication method 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.
  • the protocol may or may not transmit the response command to the other device according to the type of the response command.
  • another communication 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 to the client device.
  • a lower layer control unit that switches whether to transmit or not to transmit.
  • the lower layer determines 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.
  • another communication method 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.
  • 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.
  • another communication 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 to the client device.
  • 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.
  • the lower layer determines 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.
  • another communication method 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.
  • OBEX object exchange protocol
  • 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. .
  • another communication device 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).
  • 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.
  • Another communication apparatus 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.
  • 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.
  • bidirectional communication communication to confirm the response from the server is performed.
  • 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.
  • another communication method 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.
  • another communication device 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).
  • OBEX object exchange protocol
  • Another communication method 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.
  • OBEX object exchange protocol
  • 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!
  • another communication apparatus 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).
  • 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.
  • the other communication apparatus 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.
  • another communication method is a communication method for receiving an object from an opposite station using the object exchange protocol OBEX (OBject Exchange protocol).
  • OBEX object exchange protocol
  • OBEX response is received. It is characterized in that the OBEX response is transmitted when the final Put command is received without transmission.
  • another communication apparatus 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).
  • 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.
  • OBEX object exchange protocol
  • the object exchange protocol may be OBEX.
  • 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.
  • 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.
  • 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.
  • a communication system 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.
  • the client device 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.
  • a mobile phone as a communication device 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.
  • object exchange protocol Using col including OBEX
  • a display device as a communication device 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).
  • object exchange protocol including OBEX
  • a printing apparatus as a communication device 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).
  • object exchange protocol including OBEX
  • 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).
  • object exchange protocol including OBEX
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Communication Control (AREA)

Abstract

Grâce à la présente invention, il est possible de générer, dans un dispositif client (1) pourvu d'un OBEX, une commande de pseudo-réponse pour une commande de requête émise par une unité de traitement de couche inférieure (13) agissant comme une couche inférieure d'une couche de traitement de couche OBEX (12) et ceci est signalé à la couche de traitement de la couche OBEX (12). L'opération permet la communication par échange d'objet avec un dispositif serveur n'ayant pas de fonction de transmission.
PCT/JP2006/301106 2005-01-28 2006-01-25 Dispositif, systeme, procede, programme et circuit de communication WO2006080330A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN2006800006069A CN101006706B (zh) 2005-01-28 2006-01-25 通信装置、通信系统和通信方法
JP2007500532A JP4394141B2 (ja) 2005-01-28 2006-01-25 通信装置、通信システム、通信方法、通信プログラム、通信回路
US11/628,040 US7787391B2 (en) 2005-01-28 2006-01-25 Communication device, communication system, communication method, communication program, and communication circuit

Applications Claiming Priority (16)

Application Number Priority Date Filing Date Title
JP2005-022209 2005-01-28
JP2005022209 2005-01-28
JP2005023929 2005-01-31
JP2005-023929 2005-01-31
JP2005023901 2005-01-31
JP2005-023901 2005-01-31
JP2005-116096 2005-04-13
JP2005116096 2005-04-13
JP2005-152910 2005-05-25
JP2005152910 2005-05-25
JP2005-192903 2005-06-30
JP2005192903 2005-06-30
PCT/JP2005/014446 WO2006013979A1 (fr) 2004-08-06 2005-08-05 Emetteur, recepteur, systeme de communication, procede de communication et programme de communication
JPPCT/JP2005/014446 2005-08-05
JP2005271234 2005-09-16
JP2005-271234 2005-09-16

Publications (1)

Publication Number Publication Date
WO2006080330A1 true WO2006080330A1 (fr) 2006-08-03

Family

ID=36740360

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2006/301106 WO2006080330A1 (fr) 2005-01-28 2006-01-25 Dispositif, systeme, procede, programme et circuit de communication

Country Status (1)

Country Link
WO (1) WO2006080330A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2010114838A (ja) * 2008-11-10 2010-05-20 Toshiba Corp 通信プロトコル変換装置、方法およびプログラム
JP2011221970A (ja) * 2010-04-14 2011-11-04 Olympus Corp サービス利用端末、サービス提供端末、サービス利用端末の制御方法、サービス提供端末の制御方法およびサービス提供システム
JP5092019B2 (ja) * 2008-10-08 2012-12-05 シャープ株式会社 無線伝送システム及び無線伝送方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000196622A (ja) * 1998-12-28 2000-07-14 Nec Corp 赤外線非接続型オブジェクト交換通信方法および装置
JP2003263403A (ja) * 2002-03-07 2003-09-19 Canon Inc オブジェクト交換装置及びオブジェクト受信方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000196622A (ja) * 1998-12-28 2000-07-14 Nec Corp 赤外線非接続型オブジェクト交換通信方法および装置
JP2003263403A (ja) * 2002-03-07 2003-09-19 Canon Inc オブジェクト交換装置及びオブジェクト受信方法

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5092019B2 (ja) * 2008-10-08 2012-12-05 シャープ株式会社 無線伝送システム及び無線伝送方法
JP2010114838A (ja) * 2008-11-10 2010-05-20 Toshiba Corp 通信プロトコル変換装置、方法およびプログラム
JP2011221970A (ja) * 2010-04-14 2011-11-04 Olympus Corp サービス利用端末、サービス提供端末、サービス利用端末の制御方法、サービス提供端末の制御方法およびサービス提供システム
US8977732B2 (en) 2010-04-14 2015-03-10 Olympus Corporation Service usage terminal, service providing terminal, control method of service providing terminal, control method of service providing terminal and service providing system

Similar Documents

Publication Publication Date Title
JP4198741B2 (ja) 通信機器、通信システム、通信方法、通信プログラム、通信回路
US7787391B2 (en) Communication device, communication system, communication method, communication program, and communication circuit
KR101705764B1 (ko) 무선 도킹
JP4689689B2 (ja) 通信機器、通信システム、通信方法、通信プログラム、通信回路、携帯電話、表示装置、印刷装置および記録装置
US8051182B2 (en) Communication device, communication system, communication method, communication program, and communication circuit
CN1812405B (zh) 在请求-响应传输协议上的可靠单向消息传送的方法
JP4094657B2 (ja) 通信機器、通信システム、通信方法、通信プログラム、通信回路
CN101662315B (zh) 通信设备、通信系统以及通信方法
WO2006080330A1 (fr) Dispositif, systeme, procede, programme et circuit de communication
CN101006706B (zh) 通信装置、通信系统和通信方法
JP4948113B2 (ja) 送信機、受信機、通信システム、通信方法、通信プログラム
JP2008079330A (ja) 通信機器、通信方法、通信プログラム、通信回路、携帯電話、表示装置、印刷装置、記録装置
JP4394141B2 (ja) 通信装置、通信システム、通信方法、通信プログラム、通信回路
CN111225423B (zh) 一种数据前转的方法和设备
WO2009084506A1 (fr) Dispositif de communication, système de communication, procédé de communication, et programme
EP2157825A1 (fr) Appareil de communication, système de communication, procédé de communication et programme
WO2006080403A1 (fr) Dispositif de communication, systeme de communication, procede de communication, programme de communication et circuit de communication
JP4137992B2 (ja) 通信機器、通信システム、通信方法、通信プログラム、通信回路、携帯電話、表示装置、印刷装置、記録装置
WO2006080372A1 (fr) Dispositif, systeme, procede, programme et circuit de communication
CN117640606A (zh) 媒体数据通信方法、系统、设备及存储介质
CN112839243A (zh) 码流中转方法、装置、电子设备及存储介质
JP2006081112A (ja) データ通信装置及びデータ通信方法
JPH11249994A (ja) 画像通信システム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2007500532

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 11628040

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 200680000606.9

Country of ref document: CN

122 Ep: pct application non-entry in european phase

Ref document number: 06712301

Country of ref document: EP

Kind code of ref document: A1

WWW Wipo information: withdrawn in national office

Ref document number: 6712301

Country of ref document: EP