TWI407319B - Systems and methods for digital data transmission rate control - Google Patents

Description

Digital data transmission rate control system and method

The invention is broadly related to data transmission. More particularly, the present invention relates to dynamically adjusting the rate and size of data packet transmissions.

Computers, mobile phones, mobile phone cameras and video capture devices, personal data assistants, video game related products and various video technologies (such as video discs (DVD's) and high-definition video recorders (high difinition VCRs) It has grown by leaps and bounds over the past few years, providing increasingly high resolution still, video, on-demand and images. Combine such visual images with high-quality audio material, such as music CD-ROM sounds, and combine audio-visual discs with other devices that have associated audio signal output to create more realistic and more content for end users. Rich, or more authentic multimedia experience. In addition, in order to present pure audio to the user, highly mobile, high quality sound systems and music moving mechanisms, such as MP3 players, have been developed.

The rapid development of high-quality data has driven the need to create proprietary interfaces that can transmit data at high data rates so that the quality of the data is not compromised or compromised. One such interface is a mobile display digital interface (MDDI) for exchanging high-speed data in a top and bottom shell-type body, for example, a cellular mobile phone with a camera. MDDI is a cost-effective, low-power consumption transmission mechanism that enables data to be transmitted over a short-distance communication link between a host and a client. MDDI requires a minimum of four lines plus power, and current technology provides bidirectional data transmission up to 3.2 Gbits per second per second.

While MDDI and other data interfaces can be used to efficiently provide high-speed data rate through interfaces, there is an increasing demand for optimizing performance and more efficient use of digital transmission links such as MDDI links. In particular, depending on the particular mode of operation of the device, the bandwidth allocation is dynamically adjusted within the MDDI link to accommodate the varying latency requirements.

The present invention provides systems and methods for adaptive digital data transmission rate control. A digital data transmission system for adaptively transmitting packets on a transmission link, comprising a client device having a bandwidth control module, and a host device coupled to the client device on the transmission link. The host device includes one or more bandwidth control registers and a packet builder. The bandwidth control module determines the packet rate and/or size of the packet transmitted from the host device to the client device over the transport link. The requested packet rate and/or size is stored in the bandwidth control register.

The present invention also provides a method of adjusting a packet transmission rate coupled to a transmission link between a client device and a host device in an electronic device. The method includes determining a change in state within the electronic device. Based on the change in state, the client device determines the desired transmission rate and/or packet size. Once the desired transmission rate and/or packet size has been determined, the client device transmits the desired transmission rate and/or packet size to the host device. Once the host device receives the desired rate and/or packet size, it stores the transmission rate in the scratchpad of the host device. When the host device transmits the packet to the client device, the host device accesses the scratchpad containing the transmission rate and/or the packet size, and transmits the packet according to the rate and/or size of the contents of the register.

In an embodiment, the transport link is an MDDI link. However, the present invention is not limited to MDDI links, but can be used for digital transmission links in which the electronic device changes state so as to dynamically control the transmission rate and packet size to improve delay and improve overall system performance.

Further embodiments, features and advantages of the present invention, as well as the structure and operation of various embodiments of the present invention, are described below with reference to the drawings.

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

The described embodiments, and the description in this specification refers to an embodiment, an embodiment, an example embodiment, and the like, and represents the described embodiments. Unique features, structures, or characteristics may be included, but not every embodiment necessarily includes such unique features, structures, or characteristics. In particular, such words are not necessarily referring to the same embodiment. In addition, the features, structures, or characteristics of the present invention are described in connection with an embodiment, and it is believed that those skilled in the art are aware that the features, structures, or characteristics are connected to other embodiments, whether or not they are clearly understood.

Embodiments of the invention may be implemented as a 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, readable and executable by one or more processors. A machine-readable medium can comprise any medium that stores or transmits information in a form readable by a machine (eg, a computing device). For example, a machine-readable medium can include read only memory (ROM); random access memory (RAM); disk storage media; optical storage media; flash memory devices; electrical, optical, acoustic waves ( Acoustical or other forms of propagation signals (such as carrier waves, infrared signals, digital signals, etc.) and others. In addition, firmware, software, subprograms, and instructions may be described herein as performing specific actions. However, it should be understood that such descriptions are merely convenient, and such acts are actually performed by a computing device, processor, controller, or other device to perform the firmware, software, subprograms, instructions, and so forth.

1 is an illustration of a digital data device interface 100 coupled to a digital device 150 and a peripheral device 180. The digital device 150 can include, but is not limited to, a cellular mobile phone, a personal data assistant, a smart phone, or a personal computer. In general, the digital device 150 can include a digital device as a processing unit for digital instruction and digital presentation data processing. The digital device 150 includes a system controller 160 and a connection controller 170.

Peripheral device 180 can include, but is not limited to, a camera, a barcode reader, a shadow scanner, an audio device, and a sensor. In general, peripheral device 180 can include audio, video or image capture and display devices in which digital presentation data is exchanged between the perimeter and the processing unit. Peripheral device 180 includes control block 190. When peripheral device 180 is, for example, a camera, control block 190 can include, but is not limited to, lens control, flash or white LED control and shutter control. Digital presentation data may contain digital data representing audio, video, or multimedia material.

The digital data interface device 100 transmits digital presentation data at a high speed over the communication link 105. In one example, an MDDI communication link that can be used to support bi-directional data transmission of a maximum bandwidth of 3.2 billion bits per second can be used. Other high-speed data transmission visual communication link support at or above this rate. The digital data device interface 100 includes a message interpretation module 110, a content module 120, a control module 130, and a connection controller 140.

The link controller 140 located in the digital data interface 100 establishes a communication link 105 with the link controller 170 located in the digital device 150. The link controller 140 and the link controller 170 can be MDDI link controllers.

The MDDI standard of the Video Electronics Standards Association (〝VESA〞), which is incorporated by reference in its entirety, describes high-speed digital packets that enable portable devices to transfer digital images from small portable devices to larger external displays. Interface needs. MDDI will connect portable computing, communication and entertainment devices, and is ideal for miniature connector systems and flexible lines for emerging products such as wearable mocro displays. It also includes information on how to simplify the connection between host processors and display devices to reduce costs and increase the reliability of such links. The link controllers 140 and 170 establish a communication channel 105 based on the VESA MDDI standard.

U.S. Patent No. 6,760,772 ("772 Patent"), issued to Zou et al., issued to Zou et al., the disclosure of which is incorporated herein by reference. The packet structure of the data communication protocol is used to transmit the data interface of the digital data between the host and the client on the communication channel. The inventive embodiment described in the '772 patent is directed to the MDDI interface. The signal protocol is used by a link controller such as link controllers 140 and 170. The link controllers are configured to generate, transmit, and receive packets forming a protocol, and form the digital data into one or more data packets, at least one of which resides in the host device and is coupled through a communication channel such as the communication channel 105. To the client.

This interface provides a high-speed data transfer mechanism that is cost-effective, low-power, bidirectional, and can be implemented with micro-connectors and thin flexible lines on short-sequence (〞serial〞) data links. Embodiments of the link controllers 140 and 170 establish a communication channel 105 based on the description of the '772 patent. The '772 patent' is incorporated herein by reference in its entirety.

In addition, the host side contains several devices that can benefit from the use of the present invention. For example, the host side can be a portable computer in the form of a handheld, laptop or similar mobile computing device, such as the digital device 150 depicted. It can also be a personal data assistant (PDA), a pager device, or one of a variety of infinite phones or modems. Alternatively, the host device can be a portable entertainment or presentation device, such as a portable video or music disc player, or a game playback device.

In addition, the host side can be used as a host side device or a control element in a variety of other widely used or planned commercial products in which high speed communication with a client is desired. For example, the host side can be used to transfer data from a video recording device to a storage-based client at a high speed to enhance the response, or to a high resolution large screen for convenient presentation. Household appliances that contain internal stock or computing systems and/or Bluetooth links to other household devices, such as refrigerators, can have better display capabilities when operating in the internet or Bluetooth connectivity mode, or When the computer (computer) or control system (host side) is in the box, it is the door display (client) and the keyboard or scanner (client), which has a lower wire drawing requirement. In general, those skilled in the art will appreciate that a variety of modern electronic devices and appliances that use this interface can be benefited, as well as retrofitting older devices, using new or existing connectors or cables with limited wiring, The ability to transmit information at a higher data rate.

At the same time, the client may include a variety of presentation information to the end user, or a device useful for presenting information to the host from the user. For example, a microdisplay integrated into a frog mirror or spectacles, a projection device built into a hat or helmet, built into a vehicle, such as a small screen or even a full-image component on a window or windshield. Or a variety of speakers, headphones, or sound systems that present high-quality sound or music. Other rendering devices include projectors or projection devices for conferencing or movie and television images, presenting information. Another example is the use of touch pads or sensitive devices, voice recognition input devices, security scanners, etc., which can be used from a device or system, with little or no actual addition to user touch or sound. Enter "to transfer a large amount of information." In addition, the docking station of the computer, and the on-board kit or desk kit and base for the wireless telephone can be used as an interface device to the end user or to other devices and equipment, and can also utilize the client (output Or input devices such as a mouse or host to assist in the transmission of data, especially where high speed networks are involved.

At the same time, the client may include a variety of devices for presenting information to the end user or for presenting information to the host. For example, a microdisplay contained in a frog mirror or glasses, a projection device built into a hat or a helmet, a small screen or even a holographic built into a vehicle such as a window or a windshield. A component, or a variety of speakers, headphones, or sound systems for high-quality sound or music. Other rendering devices include projectors or projection devices for presenting information for a meeting, or for movie or television images. Another example is the use of a touch pad or a sensitive device, a voice recognition input device, a security scanner, etc., which can transmit a large amount of information from a device or system user, and only need to be in addition to the user's contact or sound. In addition, a small amount of actual "input". In addition, the docking station of the computer and car kit, or the desk kit and the support base of the radiotelephone, can be used as an interface device to the user or other devices and equipment, and the client (output or input device can be used) Such as a mouse or host, to assist with data transmission, especially when it involves high-speed networks.

However, those skilled in the art will immediately recognize that the present invention is not limited to these devices. There are many other devices that are already on the market or are proposed to be used, intended to provide high quality images and sounds for end users in storage and transmission or presentation during playback. The present invention is highly practical for increasing the data flow between different components or devices to accommodate the high data rates required to achieve the desired user experience.

The inventive MDDI and communication signal protocol can be used to simplify the interconnection of host-side processors, controllers or, for example, circuit components, with devices or device chassis or structures (referred to as internal modes) to reduce the cost or complexity of these connections. Degrees, associated power and control requirements, or restrictions on these links, and enhance the reliability of not only being connected to or being an external component, device or equipment (referred to as an external mode).

Each of the wireless communication devices possesses or contains devices such as, but not limited to, a wireless handset or telephone, a cellular mobile telephone, a data transceiver, or a call or location determination receiver, and can be carried or carried, such as loading as intended On vehicles (including cars, trucks, ships, trains and airplanes). However, wireless communication devices are generally considered to be mobile, but the description of the present invention is also understood to be applicable to "fixed" units in certain configurations. In addition, the description of the present invention is also applicable to, for example, one or more of the data and/or voice traffic that can be used to communicate with other devices by means of a cable or other known wireless connection or connection, for example, to transmit information, commands, or A data module for a sound signal or a wireless device for a data machine. In addition, commands can be used to operate the data unit or module in a predetermined coordinated or connected manner to transmit information over multiple communication channels. Wireless communication devices are also sometimes referred to as user terminals, mobile stations, mobile units, subscriber units, mobile radios or radiotelephones, wireless units, or only in certain communication systems. "user" or "mobile".

In a wireless device environment, the present invention can be used with wireless devices using a variety of industry standards, such as, but not limited to, the Analog Advanced Mobile Phone System (AMPS), and the digital cellular system described below: A Code Division Multiple Access (CDMA) spread spectrum system; a Time Division Multiple Access (TDMA) system, and a hybrid digital communication system that uses both TDMA and CDMA. The CDMA cellular system is described in the Telecommunications Industry Association/Electronics Industries Association (TIA/EIA) standard IS-95. The combined AMPS and CDMA systems are described in the TIA/EIA standard IS-98. Other communication systems are described in the International Mobile Telecommunications System 2000/Universal Mobile Telecommunications Systems or IMT-2000/UM standards, and are generally referred to as Wideband CDMA (WCDMA), cdma2000 (eg, Cdma2000 1x-rxtt cdma2000 1x, 3x or MC standard) or TD-SCDMA. Satellite-based communication systems also utilize these or similar known standards.

In other embodiments, the link controllers 140 and 170 can both be universal serial bus (USB) link controllers, or both can include a combination of controllers, such as an MDDI link controller and a different type of link controller. , for example, a USB link controller. Alternatively, the connection controllers 140 and 170 can include a combination of controllers, such as an MDDI connection controller and a single link for exchanging approval messages between the digital data interface device 100 and the digital device 150. The link controllers 140 and 170 can additionally support other types of interfaces, such as an Ethernet or RS-232 serial interface. Based on the above description, other interfaces known to those skilled in the art may also support.

Within the digital data interface device 100, the message interpretation module 110 receives the command from the system controller 160 and generates a response message through the communication link 105 to the system controller 160, interprets the command message, and transfers the information content of the command to the digital position. Appropriate modules within the data interface device 100.

The content module 120 receives the data from the peripheral device 180, stores the data, and transmits the data to the system controller 160 via the communication link 105.

The control module 130 receives information from the message interpreter 130 and forwards the information content to the control block 190 of the peripheral device 180. The control module 130 can also receive information from the control block 190 and forward the information to the message interpretation module 110.

Figure 2 is a block diagram of a cellular mobile phone 200 having upper and lower shell cover portions and utilizing the MDDI interface to provide high speed data communication between the components of the upper and lower shell covers. The following discussion of the cellular mobile phone 200 provides an exemplary example of further display of the digital data interface device 100 and provides additional details regarding its implementation and use. It will be apparent from the discussion herein that the digital data interface device 100 and other devices, such as personal digital assistants, and other types of mobile phones, are within the spirit and scope of the present invention.

Referring to FIG. 2, the shell cover portion 202 of the cellular mobile phone 200 includes a Mobile Station Modem (MSM) baseband chip 204. The mobile station modem 504 is a digital baseband controller. The invention is not limited to use with the MSM baseband chip 504. In other embodiments, the MSM baseband chip 504 can be another baseband processor, a digital signal processor (DSPs) or a controller. The shell cover portion 214 of the cellular mobile phone 200 includes a liquid crystal display (LCD) module 216 and a camera module 218. Lower shell portion 202 and upper shell portion 214 are typically wrapped within, for example, plastic, or other protective material typically used in cellular mobile phones. The hubs 250 and 252 mechanically connect the lower cover 202 to the upper cover 214. The flexible connection 254 provides electrical coupling between the lower shell cover 202 to the upper shell cover 214.

The MDDI link 210 connects the camera module 218 to the mobile station data unit 204. In one embodiment, each camera module 218 and mobile station modem 204 provide an MDDI link controller. For example, within the cellular mobile phone 200, the MDDI host 222 is integrated into the interface system 230, which in turn is coupled to the camera module 212, while the MDDI client 206 resides on the MSM side of the MDDI link 210. In an embodiment, the MDDI host is the master controller of the MDDI link.

Within the cellular mobile phone 200, pixel data from the camera module 218 is received and formatted by the interface system 230, using the MDDI host 222, as an MDDI packet prior to transmission to the MDDI link 210. The MDDI client 206 receives the MDDI packet and reconverts it to pixel data in the same format as received from the camera module 218. The pixel data is then sent to the appropriate block within the mobile station data unit 204 for processing.

Similarly, MDDI link 212 connects liquid crystal display module 216 to mobile station data machine 204. The MDDI link 212 is integrated into the MDDI host 208 within the mobile station modem 204 and integrated into the MDDI client 220 within the interface system 232. The interface system 232 is coupled to the liquid crystal display module 216. Display data generated by the graphics controller of the mobile station modem 204 is received and formatted by the MDDI host 208 as an MDDI packet prior to transmission to the MDDI link 212. The MDDI client 220 receives the MDDI packet, reconverts it to display data, and processes the data through the interface system 232 for use by the liquid crystal display module 216.

Interface systems 230 and 232 represent embodiments of digital data interface device 100. In the example of interface system 230, components of digital data interface device 100 are installed to support camera camera image and camera control function data transfer. In the example of the interface system 232, components of the digital data interface device 100 are installed to support the display of data display to the liquid crystal display and the liquid crystal display. The interface system 230 is further explained to show an embodiment of the digital data interface device 100 when used in a cellular mobile phone with a camera, such as a cellular mobile phone 200 having a camera module 218.

The relationship between the device of Fig. 1 and the cellular mobile phone 200 is as follows. The digital data interface device 100 is represented by an interface system 230. Link controller 140 is represented by MDDI host 222. Peripheral device 180 is represented by camera module 218. System controller 160 is represented by mobile station modem 204 and link controller 170 is represented by MDDI client 206.

3 is a diagram of an upper shell cover 214, providing more details regarding the interface system 230 to illustrate an exemplary embodiment of the digital data interface device 100 for use in a cellular mobile phone having a camera. The interface system 230 includes an MDDI host 222, a camera message interpreter 302, a camera video interface 304, an I2C master 303, a motor control 308, and a flash/white light emitting diode (LED) timer 310. The I2C bus is a common control bus that provides inter-circuit communication links. The I2C bus was developed in the 1980s by Philips Electronics N.V.

Recall that the interface system 230 corresponds to the digital data interface device 100. The components of the interface system 230 correspond to the digital data interface device 100 in the following manner. The camera message interpreter 302 corresponds to the message interpretation module 100. The camera video interface 304 corresponds to the content module 120. The I2C master 303, the motor control 308, and the flash/white LED timer 310 collectively correspond to the control module 130.

Camera message interpreter 302 receives the command and generates a response message through MDDI host 222 to mobile station modem 204. The camera message interpreter 302 interprets the message and forwards the information content to the interface system 230, which may be referred to as the appropriate block of the MDDI camera interface device. The camera video interface 304 receives image data from the camera 320, stores the image data, and transmits the image data to the MDDI host 222. The I2C master 306, motor control 308, and flash/white LED timer 310 together form a camera control block. In this example, the I2C master 303 provides control for managing the camera 320, the motor control 308 provides control for managing the lens 322 (such as a telescopic lens function), and the flash/white LED timer 310 provides for managing the flash. / White LED 324 control (such as flash brightness and length of time).

4 is a diagram of the MDDI host terminal 222. The MDDI host 222 includes a microprocessor interface 410, a command processor 420, a register group 430, a Direct Memory Access (DMA) interface 440, an MDDI packetizer 450, and a data handshake. Module 460 and data pad 470. The microprocessor interface 410 communicates with the host processor controlling the MDDI host 222 via the bus. The host processor uses the microprocessor interface 410 to set the scratchpad, read the scratchpad and issue commands to the MDDI host 222. The microprocessor interface 410 looks at the address value and forwards the data to the appropriate module in the MDDI host 222, including the transfer write to the command processor 420, and the read and write to the scratchpad value in the scratchpad group 430.

Command processor 420 processes commands received from the host processor. The command includes turning off the MDDI link 210 power, turning on the MDDI link 210 power, resetting the MDDI host 222, and generating certain types of data packets.

The register group 430 is stored as a register for transmitting data through the MDDI link 210. The scratchpad in the scratchpad group 430 controls the behavior of the MDDI link 222 and the configuration of the MDDI host 222.

The DMA interface 440 provides a burst request to the external memory to receive information from the interface system 230 for data buffering by the MDDI packet constructor 450. The DMA interface 440 analyzes the data of the link list node headers and adjusts the pointer to read the actual packet data. The DMA interface 440 presents the information of the next data packet for delivery to the MDDI packet constructor 450.

The MDDI Packet Builder 450 determines which packets are to be transmitted next, as well as the entity packets that are subject to the MDDI link 222. The packet is constructed from internal scratchpads, counters, and data recovered by the DMA interface 440. When data is output on the MDDI link 210, the output data can be generated from several sources. The first packet source is a control class packet internally generated to the MDDI packet constructor 450. The example packet includes sub-frame header packets, fill packets, and link shutdown packets. Another source of the package is through the DMA interface 440. These packets contain packets that are transmitted through the linked list. In other embodiments, the video material may be sent directly to the MDDI packet constructor 450 when the peripheral includes a video camera. Regardless of the source of the packet, all packets are processed by a cyclic redundancy check (CRC) generation system resident in the MDDI packet constructor 450.

The data handshake module 460 manages the entity's MDDI link 210. This is done with a state machine responsible for data handshake, data output, back-and-forth measurement, and reverse data. The data handshake module 460 receives the data from the MDDI packet constructor 450 and forwards the data to the data tablet 470. The latter moves the data out to the MDDI link 222.

The digital data interface device 100 constructs a packet having a message format of the digital data interface device as shown in FIG. The digital data interface device message format 500 can be used, for example, to format messages for exchanging information and commands between the digital data interface device 100 and the digital device 150. The message format 500 includes a transaction identifier field 510, a count field 520, a command recognition field 530, a status bar 540, and a data field 550. In one example, the transaction identification field 510, the count field 520, the command recognition field 530, and the status bar 540 can each be a single byte. The data field 550 is an optional column. When there are times, the data column 550 is a four or eight byte. In other cases, the size of the column can be as long as the specific message needs, and other lengths. The size of the column uses the format of each tuple octet. In other examples, the bit format may include other formats, such as a four-bit or six-bit format.

Command and response messages can be formatted using the above message format. There are two types of command messages: write commands and read commands. The write command is a message to execute a command, and the read command is a message that reads information from one or more scratchpads. There are three types of response messages: write acknowledgement, read response, and unsolicited messages. Write a response message that is acknowledged to be a successful scratchpad access. The read response message contains information read from one or more registers. In some cases, the read response message may contain a status indicator or a signal that is not stored in the scratchpad. Unsolicited messages are generated, for example, by the digital data interface device 100 without the request of the system controller 160.

When the communication link 105 is an MDDI link, the digital data device interface message can be packaged in the MDDI register access packet. The scratchpad access packet is defined in the VESA MDDI standard. When wrapped in a scratchpad access packet, these messages are referred to as reversed encapsulated messages.

Figure 6 shows the scratchpad access packet format 600. The scratchpad access packet format 600 includes a packet length column 610, a packet type column 620, a client identification column 630, a read/write flag column 640, a register address field 650, and a cyclic redundancy check. , 〝 〞 栏 column 660, register data list column 670 and register data CRC column 680. Except for the scratchpad address field 650 and the scratchpad data list column 670, each column is two bytes. The register address field 650 is a four-byte group. The register data list column 670 is a fourteen byte. The digital data device interface message conforming to the digital data device interface message format 500 can be packaged in the register data list column 670. The particular use of the other columns is not germane to the present invention and is more fully described in the VESA MDDI standard.

In general, digital data interface device 100 receives commands from system controller 160 via MDDI reverse wrap packets. The command number is included in the packet and is decoded by the message interpreter 110. The content of the message is then sent to the appropriate block in the digital data interface device 100. Similarly, the message interpreter 110 is also responsible for constructing a response message to the system controller 160. These messages are either responses to system controller 160 specific commands, such as image data to be transmitted, or unsolicited messages generated by digital data interface device 100, or peripheral device 180.

The use of MDDI messages to package digital data device interface messages is intended to provide an example of a digital data device interface message that can be packaged in other existing message categories without intending to limit the invention. Based on the above description, individuals who are familiar with the relevant art can decide how to package the digital data interface device information into other kinds of information.

In certain situations, it is desirable to dynamically adjust the bandwidth of the link 105 from the link controller 140 to the link controller 170. For example, when less need to transmit image information from the peripheral device 180 to the digital device 150, it may be desirable to adjust the bandwidth throughput rate on the communication link 105 to minimize delays in controlling messages from the digital device 150 to the digital interface device 100. .

For example, when the peripheral device 180 is a camera and the digital device 150 is the mobile station data device 204, the mobile station data device 204 can have at least three states, including an image preview mode, an image capture mode, and a sleep mode. In the image preview mode, the user of the cellular phone 200 is previewing the image to be taken. In the image preview mode, the MDDI host 222 transmits less data to the mobile station modem 204 from the camera module 218 than in the image capture mode. In the image preview mode, the mobile station data unit 204 only needs a portion of the pixels to make decisions about how to adjust the auto focus, light balance, exposure, and the like.

Since the system needs to make very fast adjustments and send the adjustment back to the camera module 218, the delay of the control message that affects, for example, focus, light balance, exposure time must be short. One method of improving latency is to send fewer pixels from the MDDI host 222 to release the bandwidth and transmit control signals from the MDDI client 206 to the MDDI host 222. The present invention can provide instructions for sending fewer pixels. However, the present invention additionally allows the digital device 150 to dynamically allocate the bandwidth of the forward and reverse through the communication link 105 to provide a reduced delay time for command or data messages in a particular mode of operation, ensuring that low latency is important.

FIG. 7 shows a control block that dynamically adapts to the bandwidth of the communication link 210. FIG. 7 highlights the MDDI host 222 coupled to the MDDI client 206 on the MDDI link 210. The MDDI client 206 includes an MDDI packet builder 730 and a bandwidth control module 740. Moreover, although not shown in FIG. 7 for ease of depiction, the MDDI client 206 will include the same components as the MDDI host 222 of FIG.

The bandwidth control module 740 determines the current operational state of a device. For example, the bandwidth control module 740 determines whether the device 200 is in an image preview mode, an image capture mode, or a sleep mode. Based on the mode determination, the bandwidth control module 740 provides instructions to the MDDI packet constructor 740 to transmit the packet rate and/or packet size request to the MDDI host 222.

In FIG. 7, for ease of drawing, the MDDI host 222 displays only the MDDI packet constructor 450 and the register group 430. The scratchpad group 430 includes bandwidth registers 710 and 720 for controlling the data rate of the reverse packet data packet and the reverse packed data packet to be sent from the MDDI host 222 to the MDDI client 206, respectively. When the MDDI host 222 receives the data rate or data size request from the MDDI client 206, the MDDI host 222 stores the data rate information in the bandwidth register 710, and the data size is stored in the bandwidth register 720. . The MDDI packet constructor 460 utilizes the information stored in the bandwidth registers 710 and 720 to determine the packet size and rate to be sent to the MDDI client 206.

8 provides a flow diagram of a method 800 of adjusting a packet transmission rate over a transmission link coupling a client device to a host device within an electronic device. Method 800 begins at step 810. In step 810, a change in state of the electronic device is determined. For example, MDDI client 206 determines that the state of the device has transitioned from image capture mode to image preview mode.

In step 820, the desired transmission rate is determined. For example, the bandwidth control module 740 can determine the packet rate to be sent from the MDDI host 222 to the MDDI client 206 on the MDDI link 210. The decision of packet rate and size can be based on the system's knowledge of the command delay requirements in a particular state of the electronic device. Alternatively, the size of the desired packet can be determined, or the desired packet size and desired transmission rate can be determined.

In step 830, the desired transmission rate is transmitted from the client device to the host device. For example, MDDI client 206 transmits the desired transmission rate to MDDI host 222. Alternatively, MDDI client 206 can transmit the desired transmission rate and/or the desired packet size.

In step 840, the desired transmission rate is stored. For example, MDDI host 222 stores the desired transmission rate in bandwidth register 710.

In step 850, the desired transmission rate is accessed. For example, MDDI packet constructor 460 accesses the contents of bandwidth register 710 to determine the desired transmission rate. Alternatively, MDDI packet constructor 460 can access the contents of bandwidth registers 710 and/or 720 to achieve the desired transmission rate and packet size.

In step 860, the data packet is transmitted at the desired transmission rate. For example, MDDI host 222 transmits the reverse packed data packet to MDDI client 206 on MDDI link 210 using the transmission rate from bandwidth register 710. Alternatively, the transmitted data packet may be derived from the bandwidth register 710 and/or may be adjusted based on the desired packet size contained in the bandwidth register 720. In step 870, method 800 ends.

Exemplary embodiments of the invention have been presented. The invention is not limited to these examples. The statements herein are intended to be illustrative, and not limiting. Other forms, including equivalents, extensions, variations, variations, etc. described herein, should be apparent to those skilled in the art. Such other forms are also within the spirit and scope of the invention.

All publications, patents, and patent applications referred to in this specification are indicative of the technical level of those skilled in the art of the present invention, and the scope of the disclosure is equivalent to the various publications, patents, and patent applications. The indication is specific and the individual reference income is average.

100. . . Digital data device interface

105. . . Communication link

110. . . Message interpretation module

120. . . Content module

130. . . Control module

140. . . Link controller

150. . . Digital device

160. . . System controller

170. . . Link controller

180. . . Peripheral device

190. . . Control block

200. . . Honeycomb mobile phone

202. . . Lower shell cover

204. . . Mobile station data machine

206,220. . . MDDI client

208,222. . . MDDI host

210,212. . . MDDI link

214. . . Upper shell cover

216. . . Liquid crystal display module

218. . . Camera module

230,232. . . Interface system

250,252. . . hub

254. . . Flexible connection

302. . . Camera message interpreter

303. . . I2C main end

304. . . Camera video interface

308. . . Motor control

310. . . Flash/white LED timer

320. . . camera

322. . . Lens

324. . . Flash/white light emitting diode

410. . . Microprocessor interface

420. . . Command processor

430. . . Register

440. . . DMA interface

450,730. . . MDDI packet builder

460. . . Data handshake module

470. . . Data tablet

500. . . Digital data interface device message format

510. . . Transaction identification column

520. . . Counting bar

530. . . Command identification field

540. . . Status Bar

550. . . Data column

600. . . Scratch access packet format

610. . . Packet length column

620. . . Packet type column

630. . . Client identification field

640. . . Read/write flag bar

650. . . Register address bar

660. . . Parameter cyclic redundancy check

670. . . Register data list bar

680. . . Register data cyclic redundancy check column

710,720. . . Bandwidth register

740. . . Bandwidth control module

800. . . method

810,820,830,840. . . step

The invention is described with reference to the drawings. In the figures, the same reference numerals indicate the same or functionally similar elements. The number of the first occurrence of the component is indicated by the leftmost digit of the relative reference number.

1 is a block diagram of a digital data device interface coupled to a digital device and a peripheral device; FIG. 2 is a block diagram of a cellular mobile phone having an upper and lower shell cover portion for providing high speed data communication using an MDDI interface; The camera's cellular mobile phone has an illustration of the shell cover; Figure 4 is an illustration of the MDDI host; Figure 5 is a graphical representation of the digital data interface device; Figure 6 is a temporary storage message for reverse packaging. Figure 7 is a diagram of a control block that dynamically adapts to the bandwidth of the communication link; Figure 8 is an illustration of the control link that couples the client device to the host device in the electronic device. A flow chart of a method of packet transmission rate.

206. . . MDDI client

222. . . MDDI host

210. . . MDDI link

730. . . MDDI packet builder

460. . . Data handshake module

710,720. . . Bandwidth register

740. . . Bandwidth control module

Claims (7)

A method of adjusting a packet transmission rate transmitted over a transmission link within an electronic device, the transmission coupling coupling a client device to a host device, the method comprising: determining a change in state within the electronic device, wherein the state change is Converting one of the group members of the group consisting of an image preview mode, an image capture mode, and a device sleep mode to another member mode; based on the determined change of the state, the client device determines the desired a transmission rate of the desired transmission rate from the client device to the host device; storing the transmission rate in a register of the host device; accessing the register containing the transmission rate And transmitting, on the transport link, the data packet from the host device to the client device at a transmission rate that is the same as the transmission rate stored in the register. The method of claim 1, wherein the link is a Mobile Display Digital Interface (MDDI) link. The method of claim 2, wherein the electronic device is a cellular mobile phone having a camera module. A method of adjusting a size of a packet transmitted on a transport link within an electronic device, the transport link coupling a client device to a host device, the method comprising: determining a change in state within the electronic device, wherein the change in state is caused by An image preview mode, an image capture mode, and a device sleep mode Converting one of the group members into another member mode; determining a desired packet size based on the determined change of the state; transmitting the desired packet size from the client device to the host device Storing the packet size in a register of the host device; accessing the register containing the packet size; and on the transport link, the same size as the packet stored in the register The packet size is transmitted from the host device to the client device. The method of claim 4, wherein the link is a Mobile Display Digital Interface (MDDI) link. The method of claim 5, wherein the electronic device is a cellular mobile phone having a camera module. An apparatus for adjusting a packet transmission rate transmitted on a transmission link within an electronic device, the transmission coupling coupling a client device and a host device, the device comprising: means for determining a change in state within the electronic device, wherein the state The change from one member mode to another member mode in a group consisting of an image preview mode, an image capture mode, and a device sleep mode; for using the determined change of the state a means for determining, by the client device, a desired transmission rate; means for transmitting the desired transmission rate from the client device to the host device; a means for storing the transmission rate in a register of the host device; means for accessing the register containing the transmission rate; and for transmitting the connection, A data packet is transmitted from the host device to a component of the client device at a transmission rate that is the same as the transmission rate stored in the register.