TWI386807B - Digital data interface device message format - Google Patents

Description

Digital data interface device message format

The present invention is generally related to data communication. More specifically, the present invention relates to a digital data interface device message format.

In recent years, computers, mobile phones, mobile phone cameras and video capture devices, personal digital assistants, video game related products, and various video technologies (such as digital video discs (DVDs) and high-definition video recorders) have been Significant progress has been made to provide a high resolution of still images, video, video on demand, and capture and presentation of graphics. Because of the combination of such images with high-quality audio material such as CD-type sound reproduction, DVDs, and other devices with associated audio signal output, it is more realistic, informative, or true for the end user. Multimedia experience. In addition, a highly mobile and high quality sound system and music transmission mechanism such as an MP3 player have been developed to play music only to users.

The rapid growth of high-quality data has driven the need to create dedicated interfaces for transferring data at high data rates so that data quality is not degraded or compromised. One such interface is a Mobile Display Digital Interface (MDDI) for exchanging high speed data, such as between a lower clamshell and an upper clamshell of a cellular telephone having a camera. MDDI is a low-cost, low-power transmission mechanism that enables extremely high-speed data transmission between a host and a client device via a short-range communication link. MDDI requires a minimum of four wires and power supplies for bidirectional data transmission up to 3.2 Gbits (3.2 billion bits) per second.

In one application, MDDI significantly reduces the number of wires used to connect digital baseband controllers to liquid crystal displays (LCDs) and/or cameras through the hinge of a flip-type phone, thereby enhancing the coverage of cell phones. Reliability and reduce its power consumption. This reduction in wire also allows handset manufacturers to simplify the design of clamshell handsets or sliding handsets while reducing development costs.

While MDDI or other data interfaces can be used to efficiently provide high-speed data transfer rates via interfaces, interface systems that exchange data received via MDDI or other data interface links are typically slow and are not targeted for processing such as The interface system is optimized for a particular application of camera images and control data exchanged between the lower and upper cover portions of the cell phone.

There is a need for a digital data device interface that provides efficient processing of data collected and exchanged via MDDI or other high speed links. Such a device is described in the co-pending U.S. Patent Application Serial No. ________ (Attorney Docket No. 15494235001) "Digital Data Interface Device" filed on November 23, 2005. This application illustrates a message format that can be used within a digital data interface device.

The present invention provides a digital data interface device message format for describing commands and response messages to be exchanged between a digital device having a system controller and a digital data interface device. The digital data interface device includes a message interpreter, a content module, and a control module. The message interpretation module receives and interprets commands from a system controller via a communication link, and generates a response message to be transmitted to the system controller via the communication link, interpreting the messages, and The information content of the command is transmitted to an appropriate module in the digital data interface device. The content module receives data from a peripheral device, stores the data, and transmits the data to the system controller via the communication link. The control module receives information from the message interpreter and transmits the information to a control unit of the peripheral device.

In one example, the digital data interface device includes an MDDI link controller. The digital data interface device can be used to control a peripheral device such as a camera, barcode reader, image scanner, sound device, or other sensor. In a specific example, a cell phone with a camera having an MDDI link and a digital data device interface is provided.

The digital data interface device message format includes a transaction identification field, a count field, a command recognition field, and a status field. Alternatively, the message format can include a data field. When an MDDI link is used, a digital data interface device message can be included in an MDDI register access packet.

Further embodiments, features, and advantages of the present invention, as well as the structure and operation of the various embodiments of the present invention, are described in detail herein.

This description discloses one or more embodiments that incorporate the features of the invention. One or more of the disclosed is merely illustrative of the invention. The scope of the invention is not limited to the disclosed embodiment. The invention is defined by the scope of the appended claims.

The one or more embodiments, and the words "one embodiment", "an embodiment", "an exemplary embodiment" and the like in the specification means that the one or more A particular feature, structure, or characteristic is included, but each embodiment may not necessarily include that particular feature, structure, or feature. Moreover, these terms are not necessarily referring to the same embodiment. In addition, when describing a particular feature, structure, or feature relating to an embodiment, it is to be understood that this is in connection with the implementation of other embodiments of the invention that are specifically described or not explicitly described. Within the knowledge of the characteristics, structure, or characteristics.

Embodiments of the invention may be practiced in hardware, firmware, software, or any combination of the above. Embodiments of the invention may also be implemented as instructions stored on a machine readable medium and can be read and executed by one or more processors. Machine readable media can include any mechanism for storing or transmitting information in a form readable by a machine (e.g., an computing device). For example, the machine readable medium may include a read only memory (ROM), a random access memory (RAM), a disk storage medium, an optical storage medium, and a flash. Memory devices, electrical, optical, acoustic, or other forms of propagating signals (eg, carrier, infrared, and digital signals, etc.), and other media. In addition, firmware, software, routines, and instructions may be described in this specification as performing certain actions. However, we understand that these descriptions are for convenience only, and that such actions are in fact caused by computing devices, processors, controllers, or other devices that perform firmware, software, routines, or instructions.

1 shows a digital data interface device (100) coupled to a digital device (150) and a peripheral device (180). The digital device (150) may include, but is not limited to, a cellular telephone, a number of assistants, a smart phone, or a personal computer. In general, the digital device (150) can include a processing unit that can be used as a digital command and a digital device for processing digital representation data. The digital device (150) includes a system controller (160) and a link controller (170).

The peripheral device (180) may include, but is not limited to, a camera, a code reader, an image scanner, an audio device, and a sensor. In general, the peripheral device (180) can include an audio, video, or image capture and display device that exchanges digital representations between a peripheral and a processing unit. The peripheral device (180) includes a number of control units (190). When the peripheral device (180) is such as a camera, the control unit (190) may include, but is not limited to, a lens control unit, a flash or white light emitting diode (LED) control unit, and a shutter control unit.

Digital representation data may include digital data for presentation of audio, video, and multimedia material.

The digital data interface device (100) transmits the digital representation data at a high rate via a communication link (105). In one example, one of the two-way data transmissions supporting the maximum bandwidth of 3.2 Gbits per second can be used. Other high data transmission rates above or below the instantiation rate may be supported depending on the communication link. The digital data interface device (100) includes a message interpretation module (110), a content module (120), a control module (130), and a link controller (140).

A link controller (140) located within the digital data interface (100) and a link controller (170) located within the digital device (150) establish a communication link (105). The link controller (140) and the link controller (170) may be MDDI link controllers.

The Video Electronics Standards Association (VESA) MDDI standard describes the requirements for a high-speed digital packet interface that enables portable devices to transfer digital images from a small portable device to a larger external display. MDDI applications are ideal for connecting portable computing devices, communication devices, and entertainment devices to emerging products such as wearable microdisplays, such as miniature connector systems and thin flexible cables. The standard also includes information on how to simplify the connection between the main processor and the display device to reduce costs and improve the reliability of these connections. The link controllers (140) and (170) establish a communication path (105) in accordance with the VESAMDDI standard.

U.S. Patent 6,760,772, "Generating and Implementing a Communication Protocol and Interface for High Data Rate Signal Transfer" ("Patent 6,760,772"), which is assigned to Zou et al. on July 6, 2004, describes a data interface for utilizing linked A plurality of packet structures are used to transfer digital data between a host device and a client device via a communication path to form a communication protocol for expressing data. An embodiment of the invention disclosed in the patent 6,760,772 relates to an MDDI interface. A number of link controllers, such as link controllers (140) and (170), use the signal protocol, and the configuration of the link controllers is configured to generate, transmit, and receive to form the communication protocol. Encapsulating, and configured to form the digital data into one or more types of data packets, wherein at least one link controller is disposed in the primary device and is coupled to the communication path via a communication path such as a communication path (105) The client device. The interface provides a low cost, low power, bidirectional high speed data transfer mechanism via a short range of "sequence" type data links for embodiments having a miniature connector system and a thin flexible cable. An embodiment of the link controllers (140) and (170) establishes a communication path (105) in accordance with the disclosure of Patent 6,760,772. The entire disclosure of this patent is hereby incorporated by reference.

Moreover, the primary device includes one of several types of devices that can benefit from the use of the present invention. For example, the primary device can be a portable computer such as one of the digital devices (150) in the form of a handheld computer, laptop, or similar mobile computing device. The primary device can also be one of a number of PDAs, a calling device, or a plurality of wireless telephones or modems. Alternatively, a host device can be a portable entertainment or presentation device such as a portable DVD or CD player, or gaming device.

The host can be located as a master or control element in a variety of other widely used or planned commercial products that require a high speed communication link with a client device. For example, a host can be used to transfer data from a video recording device at a high rate to a storage-type client device for better response or to a larger, high-resolution screen for display. An appliance such as a refrigerator having a built-in inventory inspection system or computing system and/or a Bluetooth connection to other handheld devices may have an Internet or Bluetooth connection mode a preferred display capability, or when the computer or control system (master device) is placed in other parts of the electrical enclosure, the electrical device is in-machine display (a user terminal device) and a button set or scanner (customer device) ) There are lower wiring requirements. In general, those skilled in the art will appreciate that a variety of modern electronic devices and appliances that can benefit from the use of the interface of the present invention, as well as the ability to retrofit older devices at higher data transfer rates, are used. Transfer information with a limited number of conductors that can be used in new or existing connectors or cables.

At the same time, a client device can include various devices for presenting information to an end user or for presenting information to a host device from a user. For example, the client device includes a microdisplay provided in a goggle or a pair of glasses, a projection device built in a hat or a helmet, and a built-in (such as in a window or a windshield) in a vehicle. Small screen or hologram display components, or a variety of speakers, headphones, or sound systems for playing high-quality sound or music. Other presentation devices include projectors or projection devices for presenting information or for film and television images in a conference. Another example would be a device that uses a touchpad or touch sensing device, a voice recognition input device, and a security scanner, etc., where the actual "input" is rarely used except for touch or sound from the user. In this case, the devices are used passively to transfer a large amount of information from a device or system user. In addition, the computer's docking station and the wireless phone's car wiring kit or desktop computer connectivity kit and mobile phone holder can be used as an interface device with the end user or other devices and devices. And especially when it comes to high speed networks, a user terminal device (such as an output or input device of a mouse or the like) or a master device is employed to assist in the transmission of data.

However, those skilled in the art will readily appreciate that the present invention is not limited to these devices, but many other devices on the market that aim to provide high quality images and sounds to end users, and are recommended for storage and transmission. Or for presentation when playing. The present invention is used to increase the amount of data transfer between components or devices to accommodate the high data transfer rates necessary to achieve the desired user experience.

The MDDI and communication signal protocols of the present invention can be used to simplify the interconnection of a host processor, controller, or circuit component, for example, to a device or a display within a device housing or structure (referred to as Internal mode) to reduce costs or reduce the complexity of these connections and associated power and control requirements or limitations, and improve reliability, not just for connections to external components, devices, or devices (called For external mode).

Each wireless communication device has or comprises components such as, but not limited to, a wireless handset or telephone, a cellular telephone, a data transceiver, or a call receiver or a position determining receiver, and the wireless communication device can view It is hand-held or portable or installed in vehicles (including cars, trucks, ships, trains, and airplanes). However, while wireless communication devices are generally considered to be mobile devices, it is also understood that the disclosure of the present invention can be applied to "fixed" units in certain configurations. Moreover, the disclosure of the present invention can be applied to, for example, can be used to transmit data and/or voice communications and can communicate with other devices for transmission of information using, for example, cables or other conventional wireless links or connections. A wireless device such as one or more data modules or data machines of commands, or audio signals. In addition, commands can be used to cause each modem or module to operate in a predetermined coordinated or associated manner to communicate information via multiple communication channels. Wireless communication devices are sometimes referred to as user terminals, mobile stations, mobile units, subscriber units, mobile radio or radiotelephones, wireless units, or "users" referred to as abbreviations in some communication systems, or "mover".

In the context of a wireless device, the present invention can be used in conjunction with wireless devices of various industry standards such as, but not limited to, the Analog Advanced Mobile Phone System (AMPS). And the following digital cellular systems: Code Division Multiple Access (CDMA) spread spectrum system, Time Division Multiple Access (TDMA) system, and simultaneous use of TDMA and A newer hybrid digital communication system for CDMA technology. A CDMA cell system is described in the Telecommunications Industry Association/Electronic Industries Association (TIA/EIA) standard IS-95. Combined AMPS and CDMA systems are described in the TIA/EIA standard IS-98. IMT-2000/UM (or International Mobile Telecommunications System 2000), commonly referred to as Broadband CDMA (WCDMA), cdma2000 (eg cdma2000 1x-rxtt, or cdma2000 1x, 3x, or MC standard) or TD-SCDMA, is covered. Other communication systems are described in the standard /Generalized Mobile Telecommunications System. Satellite-based communication systems also use these or similar conventional standards.

In other embodiments, the link controllers (140) and (170) may both be a universal serial bus (USB) link controller, or the two link controllers may include, for example, an MDDI link. The controller is combined with one of several controllers, such as another type of link controller of a USB link controller. Alternatively, link controllers (140) and (170) may include a single link controller such as an MDDI link controller and an acknowledgment message for exchanging digital data interface device (100) with digital device (150) A combination of several controllers, etc. Link controllers (140) and (170) in turn support other types of interfaces such as Ethernet or RS-232 serial port interfaces. Additional interfaces may also be supported as will be appreciated by those skilled in the art in light of the disclosure herein.

In the digital data interface device (100), the message interpretation module (110) receives commands via the communication link (105) of the system controller (160) and generates a response message, interpreting the command messages, and The information content of the command is transmitted to an appropriate module within the digital data interface device (100). Figure 2 shows the details of the architecture and functionality of the message interpretation module (110).

Referring to FIG. 2, the message interpretation module (110) includes a message interpreter controller (210), a response buffer (220), and a command buffer (230).

The message interpreter controller (210) reads and interprets the incoming message, generates a scratchpad access, and generates a response message. The incoming message includes instructions such as from the digital device (150) for controlling the peripheral device (180). The response message may include a confirmation message to be sent back to the digital device (150) to indicate whether an instruction has been executed. The response message may also include a request to read data from the peripheral device (180), and an unsolicited control command to the digital device (150).

The response buffer (220) is coupled to the message interpreter controller (210) and buffers the stored response message. A response buffer controller (225) can be coupled between the response buffer (220) and the link controller (140) to regulate the flow of response messages to the link controller (140).

The command buffer (230) is also coupled to the message interpreter controller (210) and buffers the incoming command messages. A command buffer controller (235) can be coupled between the command buffer (230) and the link controller (140) to regulate the flow of incoming command messages received from the link controller (140). The command buffer controller (235) also identifies a valid command message and detects a new transaction within the valid command message. The command buffer controller (235) includes an error detection mechanism for checking a predetermined unique identification code associated with a command message to detect one or more of a specific command message or a group of command messages Lost part. In an embodiment, the predetermined unique identification code comprises a single bit at the beginning of a command message.

Referring again to FIG. 1, the content module (120) receives data from the peripheral device (180), stores the data, and transmits the data to the system controller (160) via the communication link (105). Figure 3 illustrates further details of the architecture and functionality of the content module (120).

Referring to FIG. 3, the content module (120) includes a content buffer (310), a read control module (320), a write and synchronization control module (330), and a register unit (340). ). The content buffer (310) stores material previously received from the peripheral device (180).

The read control module (320) manages the transfer of data from the content buffer (310) to the link controller (140). For example, the read control module (320) can receive a request for data from the digital device (150) via the link controller (140). The read control module (320) can provide a digital device (150) with information indicating the capacity of the data and whether the data can be transmitted. When the data is available, the data can then be transferred directly from the content buffer (310) or indirectly via the read control module (320).

The write and sync control module (330) manages the flow of data from the peripheral device (180) to the content buffer (310). The write and sync control module (330) includes means for selectively writing all or a portion of the data received from the peripheral device (180) to the content buffer (310). The write and sync control module (330) also includes means for checking the sync pulse included in the received data to determine one or more data boundaries of the different content. In addition, the write and sync control module (330) can include means for inserting timing information into the data.

The register unit (340) stores job parameters that affect the behavior of at least one of the content buffer (310), the read control module (320), and the write and synchronization control module (330). The register unit (340) can also be coupled to the message interpretation module (110) for receiving job parameters. For example, the scratchpad unit (340) can store a video data mask, and when the peripheral device (180) is a camera, the video data mask can be used to perform a video signal or a frame integer. Reduce the sampling rate (decimation). Similarly, the job parameters may include instructions for sub-sampling of various frames and scan lines of a video signal, and instructions for determining the edges of a video signal. These parameters may also include the number of pixels per scan line and window height and width information that may be used to specify the behavior of the write and sync control module (330) and the read control module (320).

Referring again to FIG. 1, the control module (130) receives information from the message interpreter (110) and transmits the information to the control unit (190) of the peripheral device (180). The control module (130) can also receive information from the control unit (190) and transmit the message to the message interpretation module (110). Figure 4 illustrates further details of the architecture and functionality of the control module (130).

Referring to FIG. 4, the control module (130) includes a control register unit (410) and a peripheral device control unit (420). The control register unit (410) includes a plurality of registers for providing control instructions to the peripheral device control unit (420). A control register unit (410) is coupled between the message interpretation module (110) and the peripheral device control unit (420). Peripheral device control unit (420) collects peripheral device control information from control register unit (410) and uses this information to control peripheral devices (180). For example, when the peripheral device (180) is a camera, the peripheral device control unit (420) may include flash or white light emitting diode (LED) control, shutter and exposure control, lens control, and main control of the camera. Some control units.

Figure 5 is a block diagram of a cellular telephone (500) having an upper cover portion and a lower cover portion, wherein the cellular telephone (500) uses an MDDI interface to provide high speed data between the components in the upper and lower covers. communication. The description below relating to the cellular telephone (500) provides an example to further illustrate the utility of the digital data interface device (100) and provide additional details related to its embodiment and use. The use of a digital data interface device (100) in conjunction with other devices, such as a number of assistants and other types of mobile phones, will be readily apparent to those skilled in the art and within the spirit and scope of the present invention.

Referring to FIG. 5, the lower cover portion (502) of the cell phone (500) includes a Mobile Station Modem (MSM) baseband chip (504). The MSM (504) is a digital baseband controller. The invention is not limited to use with MSM baseband chips (504). In other embodiments, the MSM baseband chip (504) may be another type of baseband processor, a programmable digital signal processor (DSP), or a controller. An upper cover portion (514) of the cellular phone (500) includes a liquid crystal display (LCD) module (516) and a camera module (518). The lower cover portion (502) and the upper cover portion (514) are enclosed by plastic commonly used for cell phones. The shafts (550) and (552) mechanically connect the lower cover (502) to the upper cover (514). The flexible coupling (554) provides electrical coupling between the lower cover (502) and the upper cover (514).

The MDDI link (510) connects the camera module (518) to the MSM (504). An MDDI link controller can be provided for each of the camera module (518) and the MSM (504). For example, within a cellular telephone (500), an MDDI host device (522) is integrated into an interface system (530) coupled to the camera module (518), and an MDDI client device (506) is located in the MDDI. The MSM end of the link (510). In an embodiment, the MDDI master is the primary controller of the MDDI link.

In the cell phone (500), the interface system (530) first receives the pixel data from the camera module (518) using the MDDI host device (522) and formats the pixel data into MDDI packets before the MDDI The packet is transmitted to the MDDI link (510). The MDDI client device (506) receives the MDDI packets and reconverts the MDDI packets into pixel data in the same format as that produced by the camera module (518). The pixel data is then transferred to an appropriate unit in the MSM (504) for processing.

Likewise, the MDDI link (512) connects the LCD module (516) to the MSM (504). The MDDI link (512) connection is integrated into one of the MSM (504) MDDI masters (508) and one of the MDDI client devices (520) integrated into the interface system (532) coupled to the LCD module (516). The display data generated by a graphics controller of the MSM (504) is first received by the MDDI master (508) and formatted into MDDI packets before being transmitted to the MDDI link (512). The MDDI client device (520) receives the MDDI packets, and reconverts the MDDI packets into display data, and processes the display data by the interface system (532) for use by the LCD module (516).

Interface systems (530) and (532) represent different embodiments of the digital data device interface (100). In the case of the interface system (530), the components of the digital data device interface (100) are implemented to support data transfer of camera images and camera control functions of the camera. In the case of the interface system (532), the components of the digital data device interface (100) are implemented to support data display for an LCD and control functions of the LCD. The interface system (530) will be further described to illustrate one of the use of a digital data device interface (100) in a cellular telephone (e.g., a cellular telephone (500) having a camera module (518)) having a camera. Example.

The relationship between the devices shown in Figure 1 and the cellular telephone (500) will be described below. The digital data device interface (100) is represented by an interface system (530). The link controller (140) is represented by the MDDI master (522). The peripheral device (180) is represented by a camera module (518). The MSM (504) represents the system controller (160) and the MDDI client device (506) represents the link controller (170).

Figure 6 shows the upper cover (514) and provides further details regarding the interface system (530) to emphasize an embodiment of the digital data device interface (100) for use in a cellular telephone having a camera. The interface system (530) includes an MDDI host device (522), a camera message interpreter (602), a camera video interface (604), an I2C master device (606), a motor control unit (608), and a flash/white LED timer. (610). The I2C bus is a commonly used control bus that provides a communication link between circuits. The I2C busbar was developed by Philips Electronics N.V. in the 1980s.

As mentioned previously, the interface system (530) corresponds to the digital data device interface (100). The components of the interface system (530) correspond to the components of the digital data device interface (100) in the manner described below. The camera message interpreter (602) corresponds to the message interpretation module (110). The camera video interface (604) corresponds to the content module (120). The I2C master device (606), the motor control unit (608), and the flash/white LED timer (610) collectively correspond to the control module (130).

The camera message interpreter (602) receives the command via the MDDI host device (522) of the MSM (504) and generates a response message. The camera message interpreter (602) interprets the messages and transmits the information content to appropriate units within an interface system (530) that can be referred to as an MDDI camera interface device. The camera video interface (604) receives image data from the camera (620), stores the image data, and transmits the image data to the MDDI host device (522). The I2C master (606), the motor control unit (608), and the flash/white LED timer (610) are combined to form a camera control unit. In this case, the I2C master (606) provides control of the management camera (620), the motor control unit (608) provides control of the management lens (622) (eg, lens telescoping function), and the flash/white LED A timer (610) provides control of the management flash/white LED (624) (eg, flash brightness and duration).

Figure 7 shows a digital data device interface message format (700). For example, the digital data device interface message format (700) can be used to format messages that exchange information and commands between the digital data interface device (100) and the digital device (150). The message format (700) includes a transaction identification field (710), a count field (720), a command recognition field (730), a status field (740), and a data field (750). In one example, the transaction identification field (710), the count field (720), the command identification field (730), and the status field (740) are each a one-tuple. The data field (750) is one or more fields that may or may not appear. When the data field (750) appears, the data field (750) is four or eight bytes. In other examples, the length of the field may be other lengths depending on the particular messaging needs. The field length is in the format of 8-bit in each tuple. In other examples, the bit format can include other formats, such as a 4-bit or 16-bit format.

The command and response messages can be formatted using the above message format. There are two types of command messages: write commands, and read commands. A write command is a message that executes a command, and a read command is a message that reads information from one or more scratchpads. There are three types of response messages: write confirmation, read response, and unsolicited message. Write acknowledgment is a response message used to indicate a successful register access. A read response message contains information that has been read from one or more registers. In some examples, a read response message may include a status indicator or signal that was not previously stored in a scratchpad. An unsolicited message is generated, for example, by the digital data interface device (100) without the requirements of the system controller (160).

When the communication link (105) is an MDDI link, the digital data device interface message can be encapsulated in the MDDI register access packet. A scratchpad access packet is defined within the VESAMDDI standard.

Figure 8 illustrates a scratchpad access packet format (800). The scratchpad access packet format (800) includes a packet length field (810), a packet type field (820), a client device identification field (830), and a read/write flag field. (840), a temporary register address field (850), a parameter Cyclic Redundancy Check (CRC) field (860), a register data list field (870), and a Register CRC field (880). Except for the scratchpad address field (850) and the scratchpad data list field (870), each field is a two-byte group. The scratchpad address field (850) is a four-byte group, and the scratchpad data list field (870) is a multiple of four bytes. A digital data device interface message of the digital data device interface message format (700) can be encapsulated in the register data list field (870). The specific use of other fields is not germane to the present invention and is more fully illustrated in the VESAMDDI standard for the specific use of other fields.

In general, the digital data interface device (100) receives commands from the system controller (160) using MDDI anti-encapsulation packets. The command identification codes are embedded in the packet and decoded by the message interpretation module (110). The contents of the commands are then transferred to the appropriate units within the digital data interface device (100). Similarly, the message interpretation module (110) is also responsible for constructing a response message to the system controller (160). These messages are an unsolicited message generated by one of the specific commands of the system controller (160), or the digital data interface device (100) or peripheral device (180).

The use of an MDDI message to encapsulate a digital data device interface message is intended to provide an example of how to encapsulate a digital data device interface message with other existing message types, and is not intended to limit the invention. Based on the disclosure of this specification, those skilled in the art will be able to determine how to package digital data interface device messages into other types of messages.

Referring again to Figure 7, the transaction identification field (710) is used to identify the message. The transaction identification field (710) can also be used to associate a command message with a corresponding response message. Additionally, the transaction identification field (710) may include a byte containing a unique value used to specify an unsolicited response message. Referring to Figure 1, the system controller (160) specifies a transaction identifier that is used to populate the field and uses the transaction identification field (710) to identify responses to a particular command.

The Count field (720) is used to determine the length of a message. The count field (720) can also be used to determine the status of a message and the number of bytes in the data field.

The Command Identification field (730) identifies the type of command to be executed. Each particular command identification code is the value of the scratchpad base address for a particular portion of the digital data interface device (100). When the peripheral device (180) is a camera such as that shown in Fig. 6, the command identification code of an exemplary group is as follows:

The status field (740) is used to determine whether to read or write to a scratchpad unit. The status field (740) can also be used to request an acknowledgment indicating whether a command has been executed. Similarly, the status field (740) can be used to specify whether a command has been successfully executed. In one example, bit 0 is used to identify that the message is a read command or a write command. Bit 1 is used to indicate if an acknowledgment is required. Bit 3 is used to provide a confirmation status.

When a message is a write command, the data field (750) contains the data to be written to one or more registers. In this case, the data is transferred to a register unit based on a value in the command identification field (730). When a message is a response message, the data field (750) contains data read from one or more registers. For an unsolicited response message, the data field (750) contains information relating to the event that caused the unsolicited response to be transmitted.

When the peripheral device (180) is one of the cameras shown in Fig. 6, some message encoding is provided below as an example of possible encoding.

The format of the command message transmitted by the system controller (160) to the digital data device interface (100) for the scratchpad control of the digital data device interface (100) is as follows:

A message using the above format may contain all of the scratchpad settings/configuration settings required by the digital data device interface (100). The command identification code indicates the starting address to be addressed in the digital data device interface (100). The digital data device interface (100) will automatically increment the scratchpad address of each successive byte until all of the scratchpad values in the message are consumed. This count indicates the number of scratchpad accesses in the packet (which includes read/write bytes). The following table lists the example register groups (and corresponding command ID values) that can be configured using the message format settings in the Digital Data Device Interface (100):

The following two tables provide examples of how to format a command message to support a peripheral device such as a camera. The format of an I2C command message is shown in the following table:

The format of the flash control (for example, using a white LED) command message is shown in the following table:

As previously described, commands received from the system controller (160) may require confirmation from the digital data device interface (100) or a return value response. The confirmation request bit in the byte 3 of a command message is set, and the above confirmation or return value response is specified. The three types of response messages are: a confirmation response message indicating that one of the control registers in the digital data interface device (100) is successfully accessed; and a response message is read for reading from a peripheral device. The information obtained; and the unsolicited message, is generated by the digital data interface device (100) without the request from the system controller (160).

The format of the confirmation response message is as shown in the following table:

The format for reading the response message is as shown in the following table:

The format of the unsolicited response message is as shown in the following table:

The above message format is intended to provide an example and is not intended to limit the scope of the invention. Based on the disclosure of this specification, those skilled in the art will be able to develop additional message formats depending on the particular application and the peripheral device being used.

in conclusion

Embodiments of the invention have been provided. The invention is not limited to these examples. These examples are not provided in this specification for the sake of limitation. It will be readily apparent to those skilled in the art that various substitutions (including equivalents, extensions, variations, and deviations of the matter recited in the present specification) can be made in accordance with the disclosure. Such substitutions are still within the scope and spirit of the invention.

All publications, patents, and patent applications referred to in this specification are entitled to the extent of the disclosure of the invention, and the invention The publications, patents, and patent applications are hereby incorporated by reference.

100. . . Digital data interface device

150. . . Digital device

180. . . Peripheral device

160. . . System controller

140,170. . . Link controller

190. . . control unit

105. . . Communication link

110. . . Message interpretation module

120. . . Content module

130. . . Control module

210. . . Message interpreter controller

220. . . Response buffer

230. . . Command buffer

225. . . Response buffer controller

235. . . Command buffer controller

310. . . Content buffer

320. . . Read control module

330. . . Write and synchronization control module

340. . . Register unit

410. . . Control register unit

420. . . Peripheral device control unit

500. . . Cellular phone

502. . . Lower cover part

504. . . Mobile station data baseband chip

514. . . Upper cover part

516. . . LCD module

518. . . Camera module

550,552. . . Rotating shaft

554. . . Flexible coupling

510,512. . . MDDI: link

508,522. . . MDDI: main unit

530,532. . . Interface system

506,520. . . MDDI: User device

602. . . Camera message interpreter

604. . . Camera video interface

606. . . I2C: main unit

608. . . Motor control unit

610. . . Flash / white light: LED: timer

620. . . camera

622. . . Lens

624. . . Flash / white light: LED

700. . . Digital data interface device message format

710. . . Transaction ID field

720. . . Count field

730. . . Command recognition field

740. . . Status field

750. . . Data field

800. . . Scratch access packet format

810. . . Packet length field

820. . . Packet type field

830. . . Client device identification field

840. . . Read/write flag field

850. . . Scratchpad address field

860. . . Parameter cyclic redundancy check field

870. . . Register data list field

880. . . Register data parameter cyclic redundancy check field

The invention has been described with reference to the drawings. In the drawings, the same reference numerals indicate the same or functionally similar elements. The leftmost digit of the corresponding code of a component indicates the first occurrence of the schema number of the component.

Figure 1 shows a digital data device interface coupled to a digital device and a peripheral device.

Figure 2 shows a message interpretation module.

Figure 3 shows a content module.

Figure 4 shows a control module.

Figure 5 illustrates a cellular telephone having an upper cover portion and a lower cover portion, wherein the cellular telephone uses an MDDI interface to provide high speed data communication between the electronic components located in the upper and lower covers.

Figure 6 shows a cell phone top cover with a camera using an MDDI interface.

Figure 7 shows the digital data interface device message format.

Figure 8 illustrates a scratchpad access packet containing an anti-packaged message containing a digital data interface device message therein.

710. . . Transaction ID field

720. . . Count field

730. . . Command recognition field

740. . . Status field

750. . . Data field

Claims (15)

A data structure of a digital data interface device message for exchanging information and commands between a digital data interface device and a digital camera device, the data structure comprising: a transaction identification field for identifying the exchanged Information and camera control commands, wherein the exchanged information includes identifying a specific delivery command message and a corresponding response message; a count field for determining the length of the message; and a command recognition field for providing camera control Identifying; and a status field for deciding whether to read or write from a register block and for confirming that the transmitted command message has been successfully executed. For example, the data structure of the digital data interface device message of the first application of the patent scope, wherein each field of the fields includes an 8-bit format. For example, the data structure of the digital data interface device message in the first application of the patent scope includes a data field. For example, the data structure of the digital data interface device message of claim 3, wherein the data field contains four or eight bytes. For example, the data structure of the digital data interface device message of claim 3, wherein for a write command, the data field contains data to be written to one or more temporary registers; and wherein the response message In this case, the data field contains data read from one or more registers. For example, the data structure of the digital data interface device message of the third application of the patent scope, wherein for an unsolicited response message, the data field contains information relating to the event causing the unsolicited response to be transmitted. . For example, the data structure of the digital data interface device message of claim 3, wherein the data field includes data transmitted to a temporary memory block according to a value of the identification field of the command. For example, the data structure of the digital data interface device message of claim 1 of the patent scope, wherein the transaction identification field includes a byte used to identify a message. For example, the data structure of the digital data interface device message of claim 8 wherein the transaction identification field includes a tuple that associates the command message with the corresponding response message. For example, the data structure of the digital data interface device message of claim 8 wherein the transaction identification field includes a tuple, and the byte includes a value for specifying an unsolicited response message; Where the value of the byte is unique. For example, the data structure of the digital data interface device message of claim 3, wherein the counting field includes a byte used to determine the status of the message and the number of bytes of the data field. For example, the data structure of the digital data interface device message of the first application of the patent scope, wherein the status field includes a bit used to determine whether to read from a scratchpad block or write to a register block. group. For example, the data structure of the digital data interface device message of claim 1 of the patent scope, wherein the status field contains a byte that is used to request confirmation of whether a command has been executed. For example, the data structure of the digital data interface device message of claim 1 of the patent scope, wherein the status field contains is used to indicate whether it has been successfully Execute one of the commands for a byte. A digital data interface device for transmitting digital representation data at a high rate between a host device and a camera via a communication link, the digital data interface device comprising: a message interpretation module for Receiving a camera control command from a system controller and generating a response message for transmission to the system controller via the communication link, interpreting the messages, and transmitting the information content of the commands to the digit a suitable module in the data interface device; a content module for receiving data from the camera, storing the data, and transmitting the data to the system controller via the communication link; a control module, Receiving information from the message interpretation module and transmitting the information to a control block of the camera; and a set of messages, wherein each message includes a transaction identification field, a count field, and a command recognition field a status field, and a data field, wherein the transaction identification field is used to identify the exchanged information and camera control commands and messages, wherein the exchanged information Determining a specific delivery command message and a corresponding response message, and wherein the status field is used to determine whether to read or write from a register block and further including an acknowledgement indicating the transmitted command The message has been successfully executed.