WO2009084506A1 - 通信装置、通信システム、通信方法及びプログラム - Google Patents
通信装置、通信システム、通信方法及びプログラム Download PDFInfo
- Publication number
- WO2009084506A1 WO2009084506A1 PCT/JP2008/073322 JP2008073322W WO2009084506A1 WO 2009084506 A1 WO2009084506 A1 WO 2009084506A1 JP 2008073322 W JP2008073322 W JP 2008073322W WO 2009084506 A1 WO2009084506 A1 WO 2009084506A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- protocol
- communication
- pcl
- protocols
- processing unit
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/323—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the physical layer [OSI layer 1]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/326—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the transport layer [OSI layer 4]
Definitions
- the present invention relates to a communication device, a communication system, a communication method, and a program.
- Patent Document 1 a mobile communication system that is intended to transmit mobile information to a general-purpose portable terminal owned by a mobile user is known.
- the present invention has been made in view of the above problems, and an object of the present invention is to ensure communication compatibility when a host application includes one or more protocols. It is an object to provide a new and improved communication device, communication system, communication method and program.
- a physical layer that transmits and receives signals to and from other communication partners, and a protocol conversion unit that connects a higher-level application and the physical layer
- the protocol conversion unit is provided in common to devices that can communicate with each other, and is provided corresponding to a common processing unit that performs basic processing for protocol conversion, and one or more protocols of the upper application.
- a communication device including a conversion processing unit that converts a protocol selected from the one or more protocols into a protocol for communication in the physical layer by the common processing unit.
- signals are transmitted / received to / from other communication partners by the physical layer, and the upper application and the physical layer are connected by the protocol conversion unit.
- the common processing unit of the protocol conversion unit is provided in common to devices that can communicate with each other, and basic processing for protocol conversion is performed by the common processing unit.
- the conversion processing unit of the protocol conversion unit is provided corresponding to one or more protocols of the upper application. Then, the protocol selected from the one or more protocols by the common processing unit is converted into a protocol for communication in the physical layer by the conversion processing unit. Accordingly, since a protocol is selected from one or a plurality of protocols by a common processing unit provided in common to each device that can communicate with each other, it is possible to select an optimal protocol for communication, and communication compatibility. Sex can be secured.
- the common processing unit may perform basic operations including at least starting and stopping the protocol conversion. According to such a configuration, a basic operation including starting and stopping of protocol conversion can be realized by a common processing unit provided in common to devices that can communicate with each other.
- the common processing unit may select a protocol that matches a protocol of a higher-level application provided in the communication partner from the one or a plurality of protocols according to a result of negotiation with the communication partner. Good. According to such a configuration, a protocol that matches the protocol of the upper application included in the communication partner is selected from one or a plurality of protocols according to the result of the negotiation with the communication partner. It is possible to ensure communication with the communication partner.
- the common processing unit does not perform connection with the communication partner when there is no protocol that matches the protocol of the upper application included in the communication partner in the one or more protocols. There may be. According to such a configuration, when there is no protocol that matches the protocol of the higher-level application included in the communication partner in one or a plurality of protocols, the connection with the communication partner is not performed, so unnecessary processing is performed. It can be deterred.
- the common processing unit determines whether the software version of the protocol conversion unit matches the software version of the protocol conversion unit included in the communication partner according to the result of the negotiation with the communication partner.
- a check function may be provided. According to such a configuration, since it is determined whether or not the software version of the protocol conversion unit matches the software version of the protocol conversion unit included in the communication partner according to the result of the negotiation with the communication partner, the communication Compatibility with the other party can be ensured, and communication with the other party can be performed reliably.
- the common processing unit does not connect to the communication partner when the software version of the protocol conversion unit does not match the software version of the protocol conversion unit included in the communication partner. Also good. According to such a configuration, when the software version of the protocol conversion unit does not match the software version of the protocol conversion unit included in the communication partner, since the connection with the communication partner is not performed, unnecessary processing is performed. Can be deterred.
- the physical layer may communicate data with a communication partner with data with a profile ID indicating a data type for the data whose protocol has been converted by the conversion processing unit. According to this configuration, a plurality of logical channels can be realized on one physical layer.
- a communication system in which communication apparatuses communicate with each other, wherein the communication apparatus transmits and receives signals between communication apparatuses serving as communication partners.
- a protocol conversion unit that connects between the upper application and the physical layer, and the protocol conversion unit is provided in common in each communication device that can communicate with each other, and is a basic for protocol conversion
- a common processing unit that performs processing and one or more protocols of the higher-level application are provided to communicate with the physical layer a protocol selected from the one or more protocols by the common processing unit.
- a communication system including a conversion processing unit that converts the protocol into the protocol is provided.
- the common processing unit of the protocol conversion unit is provided in common to devices that can communicate with each other, and basic processing for protocol conversion is performed by the common processing unit.
- the conversion processing unit of the protocol conversion unit is provided corresponding to one or more protocols of the upper application. Then, the protocol selected from the one or more protocols by the common processing unit is converted into a protocol for communication in the physical layer by the conversion processing unit. Accordingly, since a protocol is selected from one or a plurality of protocols by a common processing unit provided in common to each device that can communicate with each other, it is possible to select an optimal protocol for communication, and communication compatibility. Sex can be secured.
- a communication method in which communication devices communicate with each other, wherein the communication device is a protocol with another communication device that is a communication partner.
- a step of exchanging information a step of selecting a protocol that matches a protocol of an upper application included in a communication partner from one or a plurality of protocols of an upper application based on the protocol information, and communicating the selected protocol Converting to a protocol for communicating with the other party.
- protocol information is exchanged with another communication device that is a communication partner, and one or more protocols of a higher-level application are based on the protocol information.
- a protocol that matches the protocol of the host application provided in the communication partner is selected, and the selected protocol is converted into a protocol for communicating with the communication partner. Therefore, it is possible to select the optimum protocol for communication based on the protocol information exchanged with the communication partner, and to ensure communication compatibility.
- a computer for causing a computer to function as means for selecting a protocol that matches a protocol of a higher-level application included in a communication partner from among a plurality of protocols, and means for converting the selected protocol into a protocol for communicating with the communication partner A program is provided.
- protocol information is exchanged with another communication device serving as a communication partner, and based on the protocol information, the protocol of the upper application provided in the communication partner is selected from one or more protocols of the upper application. Is selected, and the selected protocol is converted into a protocol for communicating with the communication partner. Therefore, it is possible to select the optimum protocol for communication based on the protocol information exchanged with the communication partner, and to ensure communication compatibility.
- the host application when the host application includes one or more protocols, it is possible to ensure communication compatibility.
- the wireless communication system of the present embodiment is a communication method for transmitting and receiving data between a pair of devices, and wirelessly transmits and receives data between devices in a short distance.
- FIG. 1 is a schematic diagram showing two devices (communication devices) constituting the wireless communication system of the present embodiment. Each of the two devices has a role of a responder and an initiator. The initiator is the “side that issues the connection request”, and the responder is the “side that receives the connection request”. In this embodiment, one-to-one (P2P) communication is performed. At the time of connection, the initiator issues a connection request, and the responder enters the accepting state, but both have different roles at the time of connection, and the configuration of the devices related to the connection is the same. Examples of the initiator include portable devices and electronic cards, and examples of responders include devices such as personal computers, portable devices, and electronic cards.
- FIG. 1 schematically shows a state in which wireless communication is performed via a physical layer included in each device of the present embodiment.
- the physical layer is referred to as a JET physical layer, but the physical layer is not limited to this, and can be applied to a general-purpose physical layer for communication.
- the JET physical layer is particularly suitable for large-capacity data communication such as photographs and moving images by using a profile ID, CSDU, etc., which will be described later.
- both initiator and responder devices may be collectively referred to as a JET device (or simply JET).
- FIG. 2 is a schematic diagram showing the configuration of each device of the initiator and the responder as a hierarchical structure in the wireless communication system according to the present embodiment.
- a user application 100 in order from the upper layer, a user application 100 and a PCL (Protocol) A conversion layer (102), a data transfer layer (DTL) 104, a connection layer (CNL) 106, and a physical layer (Physical Layer) 108 are configured.
- PCL Protocol
- DTL data transfer layer
- CNL connection layer
- Physical Layer Physical Layer
- the user application 100 uses a service provided by software on the upper layer of the physical layer 108 in a device equipped with the physical layer 108 capable of short-range wireless communication according to the present embodiment.
- a device equipped with the physical layer 108 capable of short-range wireless communication according to the present embodiment.
- USB USB
- TCP / IP IP
- OBEX etc.
- applications that perform device operations including UI (User Interface) etc. (for example, Windows (registered trademark), Linux, OS, etc.) Applicable.
- UI User Interface
- these upper level protocols or user applications are not particularly defined, and can be freely set by a user (manufacturer) configuring the device. Accordingly, each device may include a plurality of higher level protocols or the user application 100.
- PCL102 (protocol conversion unit) supports a protocol conversion function that mutually converts any protocol (USB, OBEX, etc.) used by the user who configures the device into a protocol unique to JET. Accordingly, it is possible to support various protocols by flowing a plurality of types of protocols to the physical layer (PHY layer) 108 of JET. Note that even with the same USB, protocol conversion may differ depending on the OS such as Windows (registered trademark) and Linux.
- the PCL 102 performs processing for converting content data such as audio and video generated by the upper user application 100, data of other protocols, commands, and the like into a data format that can be handled by the lower DTL 104.
- the PCL 102 performs processes necessary for JET communication such as connection, disconnection, device authentication, operation mode setting, and initialization.
- FIG. 3 is a schematic diagram showing the flow of data in the initiator and responder.
- the user application 100 performs two types of control: connection by JET and data transfer.
- the JET provides services necessary for realizing these functions in the highest-level PCL 102, and performs conversion to a JET original protocol and connection management.
- the data is transferred to the DTL 104 and the CNL 106 that generate CSDU (CNL service data unit) compliant with the JET standard.
- CSDU CNL service data unit
- the DTL 104 shapes the data received from the upper PCL 102 into a predetermined packet structure, and performs transmission between the initiator and the responder using a service provided by the lower CNL 106. In reception, the data received by the CNL 106 is analyzed, CSDU is extracted, and the payload is delivered to the upper PCL 102.
- the CSDU includes status information that can be used by the user application 100 other than the communication by the physical layer (PHY layer) 108, and the DTL 104 also performs the generation process, error notification, and the like.
- the DTL 104 shapes the data input from the upper layer into a DTL packet and passes it to the lower CNL 106, extracts the DTL packet from the lower received data, and passes the DTL packet payload to the upper layer. It is possible. However, although the DTL 104 itself can accept data sent from different protocols from the PCL 102, since transmission / reception of data of different protocols in JET requires session disconnection once, DTL with multiple protocols is required. The service is not used.
- the DTL 104 does not multiplex the data. Even if the received data from the CNL 106 includes a plurality of protocols, processing such as analysis of the protocol, distribution to the PCL 102 in accordance with the contents of each protocol, or disconnection of the session due to error detection is performed. Not performed.
- the PCL 102 side that uses the service provided by the DTL 104 must use the service provided by the DTL 104 in a state where the protocol to be used is fixed to one type. It is the role of the PCL common, which will be described later, to determine these protocol methods and perform necessary transmission / reception, and PCL emulation performs generation and parsing of protocol data. Exclusive processing is also the role of the PCL common so that the DTL service cannot be used simultaneously from a plurality of protocols.
- the DTL 104 provides a service necessary for the PCL common to establish a connection, and a service necessary for the PCL emulation to transmit and receive data after the connection is established.
- the DTL 104 sets a profile ID (Profile ID) indicating whether the currently executed service is halfway data of the total transfer size, the last data, or a parameter instead of data. And inserted into the CSDU packet header generated using the lower CNL service.
- the DTL 104 embeds a plurality of logical channels as shown in FIG. 6 on one physical layer (PHY layer) 108 by embedding transmission parameters in a part of a CSDU packet generated when JET transmits data. Realize.
- the DTL 104 has a function of generating a CSDU packet defined in the JET standard.
- a parameter for understanding the type of the CSDU packet is added to the CSDU packet header. What is added is Profile ID, Size, and Data Payload.
- DTL 104 performs data transfer in units of CSDU provided by CNL 106. DTL 104 assigns the following three types of profile IDs (T_DATA, LT_DATA, CNL_DATA) to CSDU during CSDU transmission. Further, when receiving CSDU, processing corresponding to the type of profile ID is performed.
- T_DATA, LT_DATA The DTL 104 gives T_DATA to the CSDU that transfers user data. However, LT_DATA is assigned when it becomes the final CSDU in the division into CSDU payloads. Only the user data is stored in the payload of the CSDU, and the DTL 104 does not embed header information or the like.
- CNL_DATA The DTL 104 gives CNL_DATA to the CSDU that transfers control data unique to the JET system. Examples of control data include parameter information (details are TBD). Header information (details are TBD) is embedded in the CSDU payload. The DTL 104 interprets this header information and performs appropriate processing.
- the CNL 106 In response to a request from the higher-level DTL 104, the CNL 106 performs communication using the service of the physical layer 108, establishes or disconnects the connection of the physical layer 108, and guarantees data continuity.
- the physical layer 108 is a JET physical layer of a wireless communication system capable of short-distance large-capacity communication according to the present embodiment, and includes an error correction function and a preamble sense function.
- Figure 4 shows JET Based on the role of the software of the device on which the device is mounted, the configuration of FIG. 2 is shown as an OSI reference model.
- the physical layer (first layer) 108 is responsible for electrical conversion and mechanical work for sending data to a communication line. Pin shape, cable characteristics, and the like are also defined in the first layer.
- DTL 104 and CNL 106 correspond to a data link layer (second layer) and a transport layer (fourth layer).
- the data link layer secures a physical communication path with the communication partner and performs error detection of data flowing through the communication path.
- the transport layer performs data compression, error correction, retransmission control, and the like for reliably and efficiently delivering data to the communication partner.
- the network layer (third layer) in the OSI reference model is not provided, and the system can be simplified.
- the PCL 102 corresponds to the session layer (fifth layer) and the presentation layer (sixth layer).
- the session layer establishes and releases a virtual path (connection) for communication programs to transmit and receive data.
- the presentation layer performs processing such as converting data received from the session layer into a format that is easy for the user to understand, and converting data sent from the application layer into a format suitable for communication.
- User application 100 corresponds to the application layer (seventh layer).
- the application layer provides various services using data communication to humans and other programs.
- FIG. 5 is a schematic diagram showing a data flow, and shows a data flow of file and data transmission / reception in each layer in the JET device.
- the PCL 102 has functions divided into PCL common and PCL emulation. Since PCL emulation is used for data transfer, the processing by the PCL 102 shown in FIG. 5 is a function realized by PCL emulation.
- the CSDU input to the physical layer 108 is defined as a data format, and the data format handled by the DTL 104 that generates and analyzes the header information is the same.
- PCL common for providing a common function is defined.
- PCL emulation performs data conversion processing according to the user protocol, it depends on the system specifications according to each protocol. To do.
- FIG. 6 is a schematic diagram showing a logical channel by CSDU. As shown in FIG. 6, Profile ID is used to specify the type of data. Thereby, a plurality of transmission channels can be logically used at the level of the physical layer 108. Therefore, the communication rate can be greatly improved, and is particularly suitable for large-capacity data communication such as moving images.
- FIG. 7 is a schematic diagram showing how the CSDU is mapped.
- CSDU is a data unit exchanged between CNL 106 and DTL 104, and is mapped to a CNL frame as shown in FIG.
- the user data size transmitted and received by the user application 100 is not particularly defined.
- the PCL 102 divides the data into a plurality of CSDU payloads.
- the PCL 102 is a unit of a CSDU payload, and transmits / receives user data by calling a DTL service.
- the DTL 104 adds a header to the CSDU payload and passes it to the lower CNL 106.
- the CSDU header is composed of a Profile ID and Length indicating the length of the CSDU payload.
- FIG. 8 is a schematic diagram showing the hardware configuration of the devices of this system.
- each of the initiator and the responder includes a chip 200 that constitutes the physical layer 108 and a CPU 210.
- the physical layer 108 includes a baseband part.
- the user application 100, the PCL 102, the DTL 104, and the CNL 106 described above are realized by causing the CPU 210 to function by software (program).
- the software is stored in an initiator, a memory included in a communication device that constitutes a responder, a recording medium outside the communication device, or the like.
- FIG. 9 is a schematic diagram showing an access point of a service provided by each layer and a relationship between the layers.
- the upper level of the PCL 102 is the user application 100.
- the PCL 102 is a layer that provides a service using the lower-level DTL 104.
- the PCL 102 controls the host user application 100 by the PCL common 102a (common processing unit) and the data transfer is performed by the PCL emulation 102b (conversion processing unit). Services are defined for each.
- the service by the PCL common 102 a provides the following service by calling a connection / disconnection / other control service of the DTL 104 in response to a request from the user application 100.
- ⁇ Control service such as connection and disconnection
- Event notification service such as error
- PCL emulation 102b The service by the PCL emulation 102b exists individually for each corresponding protocol.
- Each PCL emulation is a protocol service that enables communication by placing commands and data of general-purpose protocols (USB, OBEX, etc.) on the payload of CSDU.
- the PCL 102 it is permitted to start only a service corresponding to the protocol method selected by the PCL emulation service. Inside the PCL emulation service, a CSDU payload for using the service by the DTL 104 is generated in accordance with the request of the upper protocol. Having a plurality of services by the PCL emulation 102b makes it possible to realize a plurality of emulation services (Emulation Service) with one JET device.
- the PCL common 102a manages only one type of emulation service that can be used in one session.
- the function of the PCL 102 is divided into a PCL common 102a and a PCL emulation 102b.
- the PCL common 102a provides basic functions such as initialization, connection, and disconnection of lower layer services according to requests from the upper user application 100. Since the PCL common 102a performs basic function processing, the same processing is performed regardless of which protocol is selected.
- the PCL emulation 102b converts an arbitrary protocol possessed by the user application 100 into a protocol format handled by the lower-level DTL 104 and CNL 106 after activation is completed by the PCL common 102a.
- the PCL common 102a provides common function services such as initialization and basic communication (connection, disconnection, device authentication) to the user application 100.
- the PCL common 102a is software provided in common for all JET devices. Accordingly, the PCL 102 cannot operate with the configuration of only the PCL emulation 102b.
- the PCL emulation 102b performs user data transfer after being connected by the PCL common 102a, and has a role of mutually converting user protocols (general protocol data such as USB and OBEX) into a data format handled by the DTL 104.
- the PCL emulation 102 b has a role of converting user protocol data sent from the user application 100 into a format that can be interpreted by the lower-level DTL 104.
- the emulation block in the PCL 102 (conversion module of the PCL emulation 102b) provides a data transfer function in a manner equivalent to controlling an existing device such as USB MSC or NFC. Provide service.
- the DTL 104 provides a function using the service of the lower CNL 106 as a DTL service to the upper two types of PCL (PCL Common 102a, PCL Emulation 102b).
- PCL Common 102a PCL Common 102a
- PCL Emulation 102b converts conversion modules (Protocol A, Protocol B, Protocol C,... Protocol for each user protocol. Z), but only one type can be used in one session (connection), and the control is performed by the PCL common 102a.
- the upper level protocol is USB
- different conversion modules are prepared depending on whether it is a mass storage class or another method.
- the user who configures the device can construct the PCL emulation 102b by freely setting the conversion module corresponding to the upper protocol.
- the user can freely add and delete conversion modules.
- the PCL common 102a is a basic function for protocol conversion, it is required to be common to all JET devices.
- FIG. 9 shows Protocol A to Z as user protocols, and Protocol ⁇ ⁇ B is active among them, and shows a state in which connection is made by Protocol B.
- Protocol ⁇ ⁇ B is active among them, and shows a state in which connection is made by Protocol B.
- both the initiator and the responder are connected by Protocol ⁇ ⁇ B.
- Which protocol is used for connection is determined by negotiation between the initiator and the responder.
- FIG. 10 is a schematic diagram showing state transition in the system of the present embodiment.
- the PCL 102 performs a state transition as shown in FIG. 10 by changing the connection state between the initiator and the responder by the physical layer 108 and using the PCL service from the user application.
- the responder is in a state of waiting for a connection from the initiator, and the initiator is in a state of searching for the responder of the connection destination.
- connection between the initiator and the responder is started (Start Connection)
- negotiation is performed between the initiator and the responder.
- the software version is confirmed between the JET devices, and the emulation method (what protocol each other has) is confirmed.
- connection is made and the connection by the physical layer 108 is completed (Connected). Thereafter, emulation is started (Emulatiion), and data transfer between the user applications 100 is possible.
- the connection is not made (Disconnect).
- the responder enters a connection waiting state.
- the PCL common 102 a has a negotiation function for performing version check and discrimination of an emulation method based on the version information of the PCL 102. As a result of the negotiation, if the version and the emulation method match, the connection using the same protocol is performed between the initiator and the responder. Version control function (PCL Version Management) and emulation discrimination function (PCL) required for negotiation (Select Emulation) will be described later.
- the negotiation is not a service provided to the user application 100, but is an internal function that is automatically executed when a connection is detected while waiting for a connection.
- FIG. 11 is a schematic diagram showing the negotiation process.
- the processing in FIG. 11 can be realized by causing the CPU 210 to function by software in each layer in FIG. As an example, the determination itself is performed by the responder, and the initiator waits for the determination result.
- the version information of the connection destination is acquired by the CNL 106, and the version information is automatically exchanged at the time of connection (step S1).
- the version information exchanged at this time is referred to as a JET version.
- the PCL 102 the information on the JET version of the connection destination JET device has already been acquired when the connection is detected by the event from the lower CNL 106 and DTL 104. For this reason, first, as shown in FIG. 11, the CNL 106 software version check (CNL Ver check) and the DTL software version check (DTL Ver check) is performed. What is performed inside the PCL 102 is determination of the emulation method by checking the PCL version included in the JET version.
- the determination of the emulation method is led by, for example, a responder.
- the version information of the PCL 102 is exchanged between the initiator and the responder, and the software version information of the PCL 102 is checked by the PCL version check function of the PCL common 102a (PCL Ver check).
- the emulation type is a parameter that describes an emulation method (protocol) that allows mutual JET devices to communicate.
- the responder side compares the emulation types of the initiator and the responder, and determines that they can be connected if they are identical.
- the PCL 102 notifies the user application 100 when the emulation type is determined, and the user application 100 calls PCL_start_emu service (step S2). Then, a command Start_Emu is sent from the PCL common 102a to the PCL emulation 102b. As a result, the activation by the PCL common 102a is completed, and the emulation by the PCL emulation 102b is started (step S3). Then, the protocol of the user application 100 is converted by the PCL emulation 102b, and communication with the lower-level DTL 104 and CTL 106 becomes possible.
- the user application 100 is notified of this.
- one of these emulation types is designated on the user application 100 side, information to that effect is sent to the PCL 102.
- one emulation type designated in advance can be designated.
- an emulation type of an appropriate protocol corresponding to the communication speed can be selected.
- the emulation selection is a function that is executed inside the PCL common 102a when negotiation is performed on the responder side that has detected connection detection from the initiator. From the PCL version information in the JET version exchanged between JET devices at the time of connection, it is confirmed whether they have emulations compatible with each other.
- FIG. 12 is a schematic diagram for explaining JET version information.
- the PCL 102 manages the version information of the own device and the version information of the connection destination JET device.
- the version information of its own device is always loaded at startup, and the version information of the connection destination device is held when connection is detected and during connection.
- the JET version information has a total of 10 bytes.
- Platform information (1 byte)
- JET driver version information (2 bytes)
- CNL version information (1 byte)
- DTL version information (2 bytes) from the upper layer.
- PCL version information (2 bytes)
- reserved (2 bytes) information the JET version information.
- the first byte is the version No. (T.B.D) of the software for maintaining system compatibility.
- One byte in the latter half indicates an emulation method supported by the device (JET device).
- JET device the device
- USB, TCP / IP, OBEX... are exemplified as emulation methods, and 1-bit data is given to each method. A bit of 1 indicates that the emulation method is supported, and a bit of 0 indicates that the emulation method is not supported. There is no provision for the maximum value of the emulation method supported by one JET device, but at least one emulation method must be supported.
- the version information is checked sequentially from the information on the upper layer side (platform side) in FIG. 12, as shown in FIG. After checking the version information of the PCL 102, the emulation type is checked.
- FIG. 13 is a schematic diagram showing an emulation selection sequence.
- the selected emulation type (EMUTYPE) is notified as PCL_conf_r.ind to the responder user application 100 (UsrAppl) and as PCL_conf_i.ind to the initiator (see FIG. 13).
- FIG. 14 and 15 are schematic diagrams showing services related to the PCL emulation 102b.
- each service will be described. Activation and termination are performed by the PCL common 102a, but transmission and reception of data can be performed by communicating from the user application 100 to the PCL emulation 102b. Therefore, the service is divided into a service (FIG. 14) provided with the PCL common 102a and a service (FIG. 15) provided with the user application 100.
- the Start service is a service provided as a standard, and is a service that provides initialization processing of the PCL emulation 102b executed by the PCL common 102a when starting emulation.
- the Start service is completed, data transmission / reception using the user protocol can be performed from the user application 100.
- End service is a service provided as a standard, and is a service that provides an emulation end process executed by the PCL common 102a when the emulation is ended.
- End is completed, data transmission / reception using the user protocol from the user application 100 becomes impossible.
- PCL common 102a executes this service before executing disconnection (PCL_Disconect).
- the Open service is a service that provides processing necessary when a communication path is opened on a user protocol.
- the Close service is a service that provides processing necessary when closing a communication path on the user protocol.
- the Read service is a service that provides a process necessary when acquiring connection destination data on the user protocol.
- Write service (Mandatory; Fig. 15) Write service is a service that provides processing necessary when data is transmitted to a connection destination on a user protocol.
- Open service and Close service are processes corresponding to the initialization process of the upper protocol by the PCL common 102a.
- Read service and Write service are processes related to transmission and reception of data by the user application 100.
- the service does not correspond to the above-described service, and can be defined as a unique service by a user configuring the apparatus.
- Customized areas that can be freely set by the user who configures the JET device, except for “Open”, “Close”, “Send (Write)”, and “Read” data.
- the type of user application 100 Windows (registered trademark), Linux, etc.
- the user can freely set.
- “Start” and “End” by the PCL common 102a are necessary as described above, and are common to all JET devices.
- the PCL 102 that converts the protocol of the user application 100 is provided, and one or more protocols of the user application 100 can be selected by the PCL common 102a provided in common to each communication device. A protocol that matches the protocol of the communication partner is selected. Then, since the selected protocol is converted into a protocol for performing communication in the physical layer 108, it is possible to select an optimal protocol for communication according to the protocol of the user application 100 of the communication partner, and communication compatibility Sex can be secured.
- the wireless communication system has been described as an example. However, the communication system may be wired.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Communication Control (AREA)
- Computer And Data Communications (AREA)
Abstract
Description
102 PCL
102a PCLコモン
102b PCLエミュレーション
108 物理層
210 CPU
Conversion Layer)102、DTL(Data Transfer Layer)104、CNL(Connection Layer)106、物理層(Physical Layer)108が構成されている。
DTL104は、ユーザデータを転送するCSDUに対して、T_DATAを付与する。ただし、CSDUペイロードへの分割において、最終のCSDUとなる場合にはLT_DATAを付与する。CSDUのペイロードには、ユーザデータのみが格納され、DTL104がヘッダ情報などを埋め込むことはない。
DTL104は、JETシステム固有の制御データを転送するCSDUに対して、CNL_DATAを付与する。制御データの例としては、パラメータ情報(詳細はTBD)などがある。CSDUペイロードにはヘッダ情報(詳細はTBD)が埋め込まれる。DTL104はこのヘッダ情報を解釈し、適切な処理を行う。
deviceを搭載する機器のソフトウェアの役割に基づいて、図2の構成をOSI参照モデルで示したものである。図4に示すように、物理層(第1層)108は、データを通信回線に送出するための電気的な変換や機械的な作業を受け持つ。ピンの形状やケーブルの特性なども第1層で定められる。
・接続、切断などの制御サービス
・エラーなどのイベント通知サービス
・エミュレーション制御サービス
Z)を有するが、1度のセッション(接続)で利用できるのは1種類だけであり、その制御はPCLコモン102aによって行われる。例えば、上位プロトコルがUSBの場合、マスストレージクラスであるか、あるいは他の方式かによって異なる変換モジュールが用意されている。
Select Emulation)については後で説明する。ネゴシエーションはユーザアプリケーション100に対して提供されるサービスではなく、接続待機中の状態で、接続を検知した際に自動で実行される内部機能である。
check)が行われる。PCL102の内部で行われるのは、JETバージョン内に含まれるPCLバージョンのチェックによるエミュレーション方式の判別である。
Start serviceは、標準で提供されるサービスであり、エミュレーションを開始する際、PCLコモン102aにより実行されるPCLエミュレーション102bの初期化処理を提供するサービスである。Startが完了した時点で、ユーザアプリケーション100から、ユーザプロトコルを用いたデータ送受信が可能となる。
End serviceは、標準で提供されるサービスであり、エミュレーションを終了する際、PCLコモン102aにより実行されるエミュレーションの終了処理を提供するサービスである。Endが完了した時点で、ユーザアプリケーション100から、ユーザプロトコルを用いたデータ送受信は不可能となる。PCLコモン102aはエミュレーションがStartされていた場合、切断(PCL_Disconect)を実行する前に、このサービスを実行する。
Open serviceは、ユーザプロトコル上での通信路のオープン時に必要な処理を提供するサービスである。
Close serviceは、ユーザプロトコル上での通信路のクローズ時に必要な処理を提供するサービスである。
Read serviceは、ユーザプロトコル上で、接続先のデータを取得する際に必要な処理を提供するサービスである。
Write serviceは、ユーザプロトコル上で、接続先にデータを送信する際に必要な処理を提供するサービスである。
上述のサービスに該当しないサービスであり、装置を構成するユーザが独自のサービスとして定義できるものである。通信路を“開く(Open)”、“閉じる(Close)”、データを“送る(Write)”、“受ける(Read)”以外の部分は、JETデバイスを構成するユーザが自由に設定できるカスタマイズ領域とされ、例えばユーザアプリケーション100の種類(Windows(登録商標), Linux等)に応じて、ユーザが自由に設定することができる。但し、どのアプリケーションを使用した場合でも、上述のようにPCLコモン102aによる“Start”、“End”は必要であり、全てのJETデバイスで共通である。
Claims (10)
- 他の通信相手との間で信号の送受信を行う物理層と、
上位アプリケーションと前記物理層との間を接続するプロトコル変換部とを備え、
前記プロトコル変換部は、
互いに通信可能な各装置に共通に設けられ、プロトコル変換のための基本処理を行う共通処理部と、
前記上位アプリケーションの1又は複数のプロトコルに対応して設けられ、前記共通処理部により前記1又は複数のプロトコルの中から選択されたプロトコルを前記物理層で通信するためのプロトコルに変換する変換処理部と、を含むことを特徴とする、通信装置。 - 前記共通処理部は、少なくとも前記プロトコル変換の起動、停止を含む基本動作を行うことを特徴とする、請求項1に記載の通信装置。
- 前記共通処理部は、前記通信相手とのネゴシエーションの結果に応じて、前記1又は複数のプロトコルの中から前記通信相手が備える上位アプリケーションのプロトコルと一致するプロトコルを選択することを特徴とする、請求項1に記載の通信装置。
- 前記共通処理部は、前記1又は複数のプロトコルの中に、前記通信相手が備える上位アプリケーションのプロトコルと一致するプロトコルが存在しなかった場合は、当該通信相手との接続を行わないことを特徴とする、請求項3に記載の通信装置。
- 前記共通処理部は、通信相手とのネゴシエーションの結果に応じて、前記プロトコル変換部のソフトウェアのバージョンが、通信相手が備えるプロトコル変換部のソフトウェアのバージョンと一致するか否かを判定するバージョンチェック機能を備えることを特徴とする、請求項1に記載の通信装置。
- 前記共通処理部は、前記プロトコル変換部のソフトウェアのバージョンが、通信相手が備えるプロトコル変換部のソフトウェアのバージョンと一致しなかった場合は、当該通信相手との接続を行わないことを特徴とする、請求項5に記載の通信装置。
- 前記物理層は、前記変換処理部でプロトコルが変換されたデータに対してデータの種別を表すプロファイルIDが付されたデータを通信相手との間で通信することを特徴とする、請求項1に記載の通信装置。
- 通信装置同士が通信を行う通信システムであって、
前記通信装置は、
通信相手となる通信装置の間で信号の送受信を行う物理層と、
上位アプリケーションと前記物理層との間を接続するプロトコル変換部とを備え、
前記プロトコル変換部は、
互いに通信可能な各通信装置に共通に設けられ、プロトコル変換のための基本処理を行う共通処理部と、
前記上位アプリケーションの1又は複数のプロトコルに対応して設けられ、前記共通処理部により前記1又は複数のプロトコルの中から選択されたプロトコルを前記物理層で通信するためのプロトコルに変換する変換処理部と、を含むことを特徴とする、通信システム。 - 通信装置同士が通信を行う通信方法であって、
前記通信装置が通信相手となる他の通信装置との間でプロトコル情報を交換するステップと、
前記プロトコル情報に基づいて、上位アプリケーションの1又は複数のプロトコルの中から、通信相手が備える上位アプリケーションのプロトコルと一致するプロトコルを選択するステップと、
選択されたプロトコルを通信相手と通信するためのプロトコルに変換するステップと、
を備えることを特徴とする、通信方法。 - 通信相手となる他の通信装置との間でプロトコル情報を交換する手段、
前記プロトコル情報に基づいて、上位アプリケーションの1又は複数のプロトコルの中から、通信相手が備える上位アプリケーションのプロトコルと一致するプロトコルを選択する手段、
選択されたプロトコルを通信相手と通信するためのプロトコルに変換する手段、
としてコンピュータを機能させるためのプログラム。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/747,399 US20100260202A1 (en) | 2007-12-28 | 2008-12-22 | Communication Device, Communication System, Communication Method and Program |
EP08868651A EP2226728A4 (en) | 2007-12-28 | 2008-12-22 | COMMUNICATION DEVICE, COMMUNICATION SYSTEM, COMMUNICATION METHOD, AND PROGRAM |
CN200880120772.1A CN101896893A (zh) | 2007-12-28 | 2008-12-22 | 通信设备、通信系统、通信方法以及程序 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2007340440A JP2009163361A (ja) | 2007-12-28 | 2007-12-28 | 通信装置、通信システム、通信方法及びプログラム |
JP2007-340440 | 2007-12-28 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2009084506A1 true WO2009084506A1 (ja) | 2009-07-09 |
Family
ID=40824220
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2008/073322 WO2009084506A1 (ja) | 2007-12-28 | 2008-12-22 | 通信装置、通信システム、通信方法及びプログラム |
Country Status (7)
Country | Link |
---|---|
US (1) | US20100260202A1 (ja) |
EP (1) | EP2226728A4 (ja) |
JP (1) | JP2009163361A (ja) |
KR (1) | KR20100097690A (ja) |
CN (1) | CN101896893A (ja) |
TW (1) | TW201002014A (ja) |
WO (1) | WO2009084506A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102082588A (zh) * | 2009-11-27 | 2011-06-01 | 索尼公司 | 通信设备、通信系统、通信方法和程序 |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8775544B2 (en) * | 2009-02-04 | 2014-07-08 | Citrix Systems, Inc. | Methods and systems for dynamically switching between communications protocols |
US20180376516A1 (en) * | 2017-06-21 | 2018-12-27 | Aruba Networks, Inc. | Establishing a Datagram Transport Layer Security Connection between Nodes in a Cluster |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2004363993A (ja) * | 2003-06-05 | 2004-12-24 | Sharp Corp | 通信端末 |
JP2005191819A (ja) | 2003-12-25 | 2005-07-14 | Sony Corp | 移動体通信システムおよび携帯端末装着装置 |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5619528A (en) * | 1993-04-16 | 1997-04-08 | Trans Video Electronics | High speed teleconference system |
JP2001177872A (ja) * | 1999-12-20 | 2001-06-29 | Canon Inc | 無線通信システム |
KR100405662B1 (ko) * | 2001-12-28 | 2003-11-14 | 엘지전자 주식회사 | 서로 다른 세대 이동통신 시스템간 핸드오프 장치 및 방법 |
FR2844946B1 (fr) * | 2002-03-15 | 2004-10-22 | Thales Sa | Procede de selection et de tri de paquets mis a disposition d'un equipement par un reseau de transmission de donnees par paquets |
JP2004062748A (ja) * | 2002-07-31 | 2004-02-26 | Canon Inc | 通信制御システム、通信制御装置、通信制御方法、及び制御プログラム |
JP2004289239A (ja) * | 2003-03-19 | 2004-10-14 | Matsushita Electric Ind Co Ltd | パケット受信装置 |
US7660235B2 (en) * | 2003-03-20 | 2010-02-09 | Alcatel-Lucent Usa Inc. | Low latency shared data path allocation |
US7586881B2 (en) * | 2004-02-13 | 2009-09-08 | Broadcom Corporation | MIMO wireless communication greenfield preamble formats |
-
2007
- 2007-12-28 JP JP2007340440A patent/JP2009163361A/ja active Pending
-
2008
- 2008-12-22 CN CN200880120772.1A patent/CN101896893A/zh active Pending
- 2008-12-22 US US12/747,399 patent/US20100260202A1/en not_active Abandoned
- 2008-12-22 KR KR1020107012933A patent/KR20100097690A/ko not_active Application Discontinuation
- 2008-12-22 WO PCT/JP2008/073322 patent/WO2009084506A1/ja active Application Filing
- 2008-12-22 EP EP08868651A patent/EP2226728A4/en not_active Withdrawn
- 2008-12-26 TW TW097151030A patent/TW201002014A/zh unknown
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2004363993A (ja) * | 2003-06-05 | 2004-12-24 | Sharp Corp | 通信端末 |
JP2005191819A (ja) | 2003-12-25 | 2005-07-14 | Sony Corp | 移動体通信システムおよび携帯端末装着装置 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2226728A4 |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102082588A (zh) * | 2009-11-27 | 2011-06-01 | 索尼公司 | 通信设备、通信系统、通信方法和程序 |
EP2328318A1 (en) * | 2009-11-27 | 2011-06-01 | Sony Corporation | Communication device, communication system, communication method, and program |
US8819430B2 (en) | 2009-11-27 | 2014-08-26 | Sony Corporation | Communication device, communicaton system, communication method, and program |
CN102082588B (zh) * | 2009-11-27 | 2014-10-22 | 索尼公司 | 通信设备、通信系统、通信方法和程序 |
Also Published As
Publication number | Publication date |
---|---|
EP2226728A1 (en) | 2010-09-08 |
KR20100097690A (ko) | 2010-09-03 |
CN101896893A (zh) | 2010-11-24 |
JP2009163361A (ja) | 2009-07-23 |
TW201002014A (en) | 2010-01-01 |
US20100260202A1 (en) | 2010-10-14 |
EP2226728A4 (en) | 2013-02-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7787391B2 (en) | Communication device, communication system, communication method, communication program, and communication circuit | |
US8284684B2 (en) | Communication device, communication system, communication method, and communication circuit | |
WO2017045276A1 (zh) | 终端互联方法、装置和存储介质 | |
JP2009182459A (ja) | 通信装置、通信システム、通信方法及びプログラム | |
CN104115500A (zh) | 经由用户输入返回信道的双向隧穿用于无线显示 | |
WO2006013979A1 (ja) | 送信機、受信機、通信システム、通信方法、通信プログラム | |
JP2010528535A (ja) | ニアフィールド・リンクを最適化する方法 | |
US11166137B2 (en) | Method, device, and system for adjusting packet length in near field communication | |
TW200835208A (en) | Communications device, communications method, communications circuit, mobile phone, and computer-readable storage medium containing the computer program | |
JP4609550B2 (ja) | 通信装置、通信システム、通信方法及びプログラム | |
WO2006080357A1 (ja) | 通信機器、通信システム、通信方法、通信プログラム、通信回路 | |
WO2011140754A1 (zh) | 无线优盘的实现方法及系统 | |
JP5698366B2 (ja) | 制御方法、装置、及びシステム | |
JP2009182458A (ja) | 通信装置、通信システム、通信方法及びプログラム | |
WO2006002579A1 (fr) | Procede de transmission de donnees entre des appareils de reseau | |
WO2009084506A1 (ja) | 通信装置、通信システム、通信方法及びプログラム | |
Mamdouhi et al. | Bluetooth wireless monitoring, managing and control for inter vehicle in vehicular ad-hoc networks | |
Wu et al. | Research on Bluetooth expansion of communication based on android system | |
KR20190021121A (ko) | 근거리 무선 통신 장치 및 방법 | |
JP4137992B2 (ja) | 通信機器、通信システム、通信方法、通信プログラム、通信回路、携帯電話、表示装置、印刷装置、記録装置 | |
JP4394141B2 (ja) | 通信装置、通信システム、通信方法、通信プログラム、通信回路 | |
KR100842584B1 (ko) | 대용량 파일을 전송하기 위한 방법 | |
CN116346534A (zh) | 一种多网融合通信方法及其系统 | |
JP4028539B2 (ja) | データ通信装置及びデータ通信方法 | |
JP2007150390A (ja) | 通信装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200880120772.1 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 08868651 Country of ref document: EP Kind code of ref document: A1 |
|
REEP | Request for entry into the european phase |
Ref document number: 2008868651 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2008868651 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2473/CHENP/2010 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 12747399 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 20107012933 Country of ref document: KR Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: PI 2010001933 Country of ref document: MY |
|
NENP | Non-entry into the national phase |
Ref country code: DE |