System and method for supporting data communication in a heterogeneous environment

Abstract

Systems and methods for supporting data communication in a heterogeneous environment, the method including receiving, by a first device, an identifier value from a second device that is associated with a software platform installed on the second device; identifying the software platform based on the identifier value; determining a device type of the second device based on the identified software platform; configuring the first device to be in a host mode or an accessory mode based on the determined device type of the second device; and establishing data communication between the first device and the second device via a communication interface associated with the determined device type of the second device.

1 - 30 . (canceled) 
     
     
         31 . A method for supporting data communication in a heterogeneous environment, the method comprising:
 receiving, by a first device, an identifier value from a second device, wherein the identifier value is associated with a software platform installed on the second device;   identifying, by the first device, the software platform installed on the second device based on whether the identifier value matches a predetermined value corresponding to the software platform;   determining, by the first device, a device type of the second device based on the identified software platform;   configuring the first device to be in a host mode or an accessory mode based on the determined device type of the second device for handling a data communication between the first device and the second device; and   establishing the data communication between the first device and the second device via a communication interface associated with the determined device type of the second device.   
     
     
         32 . The method of  claim 31 , further comprising:
 transmitting a message from the first device to the second device to initiate the data communication, when the first device is configured to be in the host mode.   
     
     
         33 . The method of  claim 32 , further comprising:
 exchanging data via the communication interface, when an acknowledgement message in response to the message is received from the second device; or   ignoring the second device, when the acknowledgement message is not received from the second device or an error message is received from the second device.   
     
     
         34 . The method of  claim 31 , further comprising:
 switching the first device from the host mode into the accessory mode, when the first device is configured to be in the host mode and the second device is determined to be in a particular device type.   
     
     
         35 . The method of  claim 34 , further comprising:
 sending a role switching message from the first device to the second device; and   receiving, by the first device, a message from the second device to initiate the data communication.   
     
     
         36 . The method of  claim 31 , further comprising:
 connecting the first device to the second device using a socket of the first device, wherein the socket supports connections with different types of devices associated with different installed software platforms.   
     
     
         37 . The method of  claim 36 , wherein the socket is adapted to serve as a charging interface that is associated with different types of devices. 
     
     
         38 . The method of  claim 31 , wherein the identifier value is a device descriptor including at least one of a vendor identifier (VID) or a product identifier (PID). 
     
     
         39 . An apparatus for supporting data communication in a heterogeneous environment, the apparatus comprising:
 a controller; and   a memory associated with the controller, wherein the memory stores instructions and the controller is configured to execute the instructions to:
 receive an identifier value from a device connected to the apparatus, wherein the identifier value is associated with a software platform installed on the device; 
 identify the software platform installed on the device based on whether the identifier value matches a predetermined value stored in the memory corresponding to the software platform; 
 determine a device type of the device based on the identified software platform; 
 configure the apparatus in a host mode or an accessory mode based on the determined device type of the device for handing a data communication between the apparatus and the device; and 
 establish the data communication between the apparatus and the device via a communication interface associated with the determined device type of the device. 
   
     
     
         40 . The apparatus of  claim 39 , wherein the controller is configured to execute the instructions to:
 transmit a message to the device to initiate the data communication, when the apparatus is configured to be in the host mode.   
     
     
         41 . The apparatus of  claim 40 , wherein the controller is configured to execute the instructions to:
 exchange data via the communication interface, when an acknowledgement message in response to the message is received from the device; or   ignore the device, when the acknowledgement message is not received from the device or an error message is received from the device.   
     
     
         42 . The apparatus of  claim 39 , wherein the controller is configured to execute the instructions to:
 switch the apparatus from the host mode into the accessory mode, when the apparatus is configured to be in the host mode and the device is determined to be in a particular device type.   
     
     
         43 . The apparatus of  claim 42 , wherein the controller is configured to execute the instructions to:
 send a role switching message to the device; and   receive a message from the device to initiate the data communication.   
     
     
         44 . The apparatus of  claim 39 , further comprising:
 a socket configured to be connected to the device, wherein the socket supports connections with different types of devices associated with different installed software platforms.   
     
     
         45 . The apparatus of  claim 44 , wherein the socket is adapted to serve as a charging interface that is associated with different types of devices. 
     
     
         46 . The apparatus of  claim 39 , wherein the identifier value is a device descriptor including at least one of a vendor identifier (VID) or a product identifier (PID). 
     
     
         47 . A non-transitory computer-readable medium with instructions stored thereon, that when executed by a processor, perform steps comprising:
 receiving, by a first device, an identifier value from a second device, wherein the identifier value is associated with a software platform installed on the second device;   identifying, by the first device, the software platform installed on the second device based on whether the identifier value matches a predetermined value corresponding to the software platform;   determining, by the first device, a device type of the second device based on the identified software platform;   configuring the first device to be in a host mode or an accessory mode based on the determined device type of the second device for handing the data communication between the first device and the second device; and   establishing a data communication between the first device and the second device via a communication interface associated with the determined device type of the second device.   
     
     
         48 . The non-transitory computer-readable medium of  claim 47 , when executed by the processor, further perform the steps comprising:
 transmitting a message from the first device to the second device to initiate the data communication, when the first device is configured to be in the host mode.   
     
     
         49 . The non-transitory computer-readable medium of  claim 48 , when executed by the processor, further perform the steps comprising:
 exchanging data via the communication interface, when an acknowledgement message in response to the message is received from the second device; or   ignoring the second device, when the acknowledgement message is not received from the second device or an error message is received from the second device.   
     
     
         50 . The non-transitory computer-readable medium of  claim 47 , when executed by the processor, further perform the steps comprising:
 switching the first device from the host mode into the accessory mode, when the first device is configured to be in the host mode and the second device is determined to be in a particular device type; and   sending a role switching message from the first device to the second device.