MIPI conversion in GMSL tunneling mode
By converting MIPI protocols in serializers and deserializers, the data transmission speed limit of MIPI protocol in tunnel mode is solved, and high bandwidth and reliable data transmission is achieved, which is suitable for applications such as advanced driver assistance systems.
Patent Information
- Application Number
- CN202411347994.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2020-07-16
- Filing Date
- 2021-07-15
- Publication Date
- 2024-11-12
AI Technical Summary
The existing MIPI protocol limits end-to-end data protection in tunnel mode, resulting in slow data transmission between sensors and SoCs, which cannot meet high bandwidth requirements, especially in applications such as advanced driver assistance systems.
By implementing a protocol converter in the serializer and deserializer, the ECC value of the D-PHY packet is converted into the CRC value of the C-PHY packet, or vice versa, to coordinate the header structure of different protocols to ensure the data during transmission. Integrity and reliability.
It realizes high bandwidth and reliable data transmission in end-to-end systems, breaks through the speed limit of MIPI interface, supports higher data throughput, is suitable for the transmission of multiple video streams, and meets the application needs of high resolution and high frame rate. .
Smart Images

Figure CN118945241A_ABST
Abstract
Description
[0001] This application is a divisional application of the patent application with the same name with application number 202110799621.0 filed on July 15, 2021.
[0002] CROSS-REFERENCE TO RELATED APPLICATIONS
[0003] This application claims the benefit of priority under 35 U.S.C. §119(e) to co-pending and commonly assigned U.S. patent application No. 63 / 052,557, filed on July 16, 2020, entitled “MIPI conversion in GMSL tunnel mode,” which lists Paul Fuller, Yan Yan, Gary Murdock, and Prem Ramachandran Nayar as inventors, and which is incorporated herein by reference in its entirety. Background Art
[0004] The present disclosure relates generally to secure high-speed data communication systems. More specifically, the present disclosure relates to data transmission and flow control in a signal processing system utilizing a packet-based communication protocol for end-to-end communication.
[0005] Data packets transmitted to convey information between system components typically have a packet structure that conforms to a certain transmission protocol, which typically includes protection mechanisms to facilitate reliable data transmission. For example, the packet construction defined by the Mobile Industry Processor Interface (MIPI) standard is different between C-Physical Layer (PHY) packets and D-PHY packets, which utilize different protection algorithms. D-PHY (used for differential signaling) protects packets using error correction codes (ECC), while C-PHY (using 3-level signaling) protects packets using cyclic redundancy checks (CRC). Therefore, the limitation of existing MIPI methods that utilize tunnel mode end-to-end CRC / ECC protection is that sensors, systems on chips (SoCs), and similar devices must use the same MIPI protocol on both sides of the communication path.
[0006] Specifically, to achieve end-to-end data protection, the CRC (or ECC) value generated by the transmitting component (e.g., sensor) must be received by the receiving component (e.g., processor in SoC), that is, the value must pass through the serializer / deserializer (serdes) path (e.g., including serializer, serial link and deserializer) without modification or regeneration. If a bit error occurs during the transmission from the sensor output to the SoC input using a serdes scheme (which is generally intended to minimize the number of I / O pins and interconnects), the ECC / CRC value on the sensor side of the transmission will not match the ECC / CRC check in the SoC.
[0007] Although more and more SoCs are compatible with C-PHY technology, almost all camera sensors are based on MIPID-PHY technology, i.e., C-PHY sensors are almost non-existent. In practice, this makes end-to-end data protection limited to D-PHY speeds (e.g., 2.5 Gbps per lane), which are much slower than the bit rate of C-PHY (e.g., 5.7 Gbps per lane). C-PHY includes an encoding scheme that allows 2.28 bits to be transmitted per clock cycle, while D-PHY transmission is limited to 1 bit per clock cycle. Therefore, a common 4-lane C-PHY port can transmit at a much higher throughput of 4×5.7 Gbps (i.e., 22.8 Gbps). In contrast, a common 4-lane D-PHY port can only transmit 4×2.5 Gbps (i.e., 10 Gbps), which particularly limits designs that aggregate multiple video streams in the deserializer and transmit them through MIPIDHY. For example, four GMSL2 6Gbps (~5.2Gbps data throughput) cameras would require a MIPI interface greater than 20Gbps to transmit the aggregated video stream.
[0008] Therefore, existing limitations of the slower MIPI interface prevent system designers from securely transmitting large amounts of data in applications, such as advanced driver assistance systems (ADAS) applications, which greatly benefit from higher camera resolutions and frame rates in higher ASIL systems. Therefore, it would be desirable to have systems and methods that overcome the limitations of otherwise incompatible protocols to enable tunneling mode in an end-to-end system and facilitate reliable, high-bandwidth communications between many interconnected components (such as cameras, displays, and processors) in mobile, video, automotive, and other applications. BRIEF DESCRIPTION OF THE DRAWINGS
[0009] Reference will be made to embodiments of the present disclosure, examples of which may be shown in the accompanying drawings. These drawings are intended to be illustrative, not restrictive. Although the accompanying disclosure is generally described in the context of these embodiments, it should be understood that it is not intended to limit the scope of the present disclosure to these specific embodiments.
[0010] FIG. 1 illustrates a camera serial interface (CSI)-2 packet flow using a common data structure according to the MIPI standard.
[0011] FIG. 2A shows the packet header and trailer details of a common long packet structure of the D-PHY physical layer.
[0012] FIG. 2B shows the packet header and trailer details of a common short packet structure of the D-PHY physical layer.
[0013] FIG. 3A shows the packet header and trailer details of a long packet structure of the C-PHY physical layer.
[0014] FIG. 3B shows the packet header and trailer details of the short packet structure of the C-PHY physical layer.
[0015] Figure 4A An exemplary mapping between a long packet structure physical layer D-PHY data packet and a long packet structure physical layer C-PHY data packet according to various embodiments of the present disclosure is shown.
[0016] Figure 4B An exemplary mapping between a short packet structure physical layer D-PHY data packet and a short packet structure physical layer C-PHY data packet according to various embodiments of the present disclosure is shown.
[0017] Figure 4C Exemplary data identifiers according to embodiments of the present disclosure are shown.
[0018] Figure 5 Exemplary mappings between D-PHY and C-PHY for respective long and short packets are shown according to various embodiments of the present disclosure.
[0019] Figure 6 An exemplary communication system according to various embodiments of the present disclosure is presented.
[0020] Figure 7 is a flow chart of an exemplary high-speed data communication process according to various embodiments of the present disclosure.
[0021] Figure 8 Depicted is a simplified block diagram of an information handling system in accordance with an embodiment of the present invention. DETAILED DESCRIPTION
[0022] In the following description, for the purpose of explanation, specific details are set forth in order to provide an understanding of the present disclosure. However, it will be apparent that one skilled in the art can practice the present disclosure without these details. In addition, one skilled in the art will recognize that the embodiments of the present disclosure described below can be implemented in various ways such as a process, an apparatus, a system / device, or a method on a tangible computer readable medium.
[0023] The components or modules shown in the figures illustrate exemplary embodiments of the present disclosure and are intended to avoid blurring the present disclosure. It should also be understood that throughout this discussion, components may be described as separate functional units that may include subunits, but those skilled in the art will recognize that various components or their multiple parts may be separated into separate components or may be integrated together, including being integrated into a single system or component. It should be noted that the functions or operations discussed herein may be implemented as components. Components may be implemented with software, hardware, or a combination thereof.
[0024] In addition, the connection between the components or systems in the drawings is not intended to be limited to direct connections. On the contrary, the data between these components can be modified, reformatted, or otherwise changed by intermediate components. Moreover, additional connections or fewer connections can be used. It should also be noted that the terms "coupled", "connected" or "communicatively coupled" should be understood to include direct connections, indirect connections through one or more intermediate devices, and wireless connections.
[0025] In this specification, references to "one embodiment", "preferred embodiment", "embodiment", or "multiple embodiments" mean that a particular feature, structure, characteristic, or function described in conjunction with the embodiment is included in at least one embodiment of the present disclosure and may be in more than one embodiment. Moreover, the above phrases appearing in different places in this specification do not necessarily all refer to the same embodiment or embodiments.
[0026] Certain terms are used in various places in this specification for purposes of illustration and should not be construed as limiting. The terms "include," "including," "comprise," and "comprising" should be understood as open terms and any listed items that follow are examples and are not intended to be limited to the listed items.
[0027] A service, function, or resource is not limited to a single service, function, or resource; the use of these terms may refer to a group of related services, functions, or resources that may be dispersed or aggregated. The use of memory, database, information base, data storage device, table, hardware, etc. may be used herein to refer to one or more system components into which information may be input or otherwise recorded. The terms "data," "information," and similar terms may be replaced by other terms referring to a group of bits and may be used interchangeably. The terms "packet" or "frame" should be understood to refer to a group of bits. The term "frame" should not be interpreted as limiting embodiments of the present invention to a 2-layer network; and, the term "packet" should not be interpreted as limiting embodiments of the present invention to a 3-layer network. The terms "packet," "frame," "data," or "data traffic" may be replaced by other terms referring to a group of bits, such as "datagram" or "cell."
[0028] It should be noted that: (1) certain steps may be performed optionally; (2) the steps may not be limited to the specific order set forth herein; (3) certain steps may be performed in a different order; and (4) certain steps may be performed in a sequential manner.
[0029] FIG. 1 illustrates a CSI-2 packet stream using a common data structure according to the MIPI standard. Stream 100 includes short packets 102 and long packets 116, including data (e.g., 112), located between a start of transmission 104 packet and an end of transmission 106 packet. As depicted, the end of transmission 106 packet may be followed by a low power state 108. Long packet 116 includes a packet header 110, a packet trailer 114, and, if applicable, a packet filler. The CSI-2 packets in stream 100 typically have some low-level protocol features, such as: (1) transmission of arbitrary data (independent of the payload); (2) 8-bit word length; (3) support for up to four interleaved virtual channels on the same link; (4) special packets for frame start, frame end, line start, and line end information; (5) descriptors for type, pixel depth, and format of dedicated payload data; (6) 16-bit checksum code for error detection; and (7) 8-bit ECC for error correction (D-PHY physical layer only) and error detection. Details of the packet header 110 and trailer 114 of the long packet 116 structure of the D-PHY physical layer are shown in Figure 2A. Figure 2B shows the header 252 of the short packet structure 250 of the D-PHY physical layer.
[0030] The data identifier (ID) 202 in the long packet structure 200 in Figure 2A is an 8-bit data identifier (DI) that contains 2-bit virtual channel (VC) information and 6-bit data type (DT) information. VC (bits 7:6) represents the two least significant bits of the 4-bit virtual channel identifier of the D-PHY physical layer option. DT (bits 5:0) represents the format / content of the dedicated payload data. Used by the dedicated layer. The receiver reads the data word of the next 16-bit word count (WC) 204, regardless of its value. The receiver does not look for any embedded synchronization sequence in the payload data, but uses the WC value to determine the end of the packet payload. The 6-bit error correction code (ECC) (bits 5:0) in field 206 enables correction of 1-bit errors in the 32-bit packet header 208 and detection of 2-bit errors. 2-bit VC extension (VCX). VCX (bits 7:6) in field 206 are the two most significant bits of the 4-bit VC identifier of the D-PHY physical layer option. The dedicated payload 210 includes packet data 214, the length of which is equal to the word count (WC) multiplied by the data word width (8 bits). There is no restriction on the value of the data word. The checksum / CRC 212 includes a 16-bit packet trailer 216.
[0031] The details of the packet header and trailer of the long packet structure of the C-PHY physical layer are shown in Figure 3A. The 5-bit reserved field (RES) (bit 7:3) in field 302 is set to zero and is reserved for future use. The 3-bit VCX field (bit 2:0) in field 302 is the three most significant bits of the 5-bit VC identifier of the C-PHY physical layer option. The 8-bit DI304 used by the dedicated layer contains 2-bit VC information and 6-bit DT information. VC (bit 7:6) is the two least significant bits of the 5-bit virtual channel identifier of the C-PHY physical layer option. DT (bit 5:0) represents the format / content of the dedicated payload data. Regarding the 16-bit WC 306, 312, the receiver reads the next WC 8-bit data word after the packet header and uses the WC value to determine the end of the packet payload. The 16-bit CRC code 308, 314 of the packet header is calculated based on the reserved field, data ID field and word count field (4 bytes) to enable detection of multi-bit errors. As a result of executing the CSI-2PPI command, the physical layer inserts a synchronization word simultaneously on all N lanes after the CRC code 308 , 314 .
[0032] The 16-bit packet trailer includes a 16-bit packet data CRC 318 calculated based on the WC packet data word. Following the packet trailer 318 are fillers 320, 322, which include FC 8-bit bytes added to ensure that all lanes transmit the same number of 16-bit words. The dedicated payload 316 includes the packet data, which has a length equal to WC*data word width (8 bits). As with the D-PHY packet structure, there is no restriction on the value of the data word.
[0033] 3B shows the details of the short packet structure of the C-PHY physical layer. The VCX field 352 is LS 3 bits and all RES are zero. The short packet 350 has 6N×16 bits 350, where N is the physical layer count. In response to a single CSI-2PPI command, the physical layer inserts a 7-symbol sync word simultaneously on all N lanes after the 16-bit CRC code.
[0034] Not only do the C-PHY protocol and the D-PHY protocol use slightly different header information, but they also use different protection algorithms. The D-PHY packet header is protected with a 6-bit ECC value, while the C-PHY packet header is protected with a 16-bit CRC value. The data protected in the header information is the same, except for the 5-bit "RES" field in the C-PHY packet. This field is reserved for "future use" and, starting with the CSI-2v3.0 specification version, all 5 bits are set to zero.
[0035] Figure 4AAn exemplary mapping between a long packet structure physical layer D-PHY data packet and a long packet structure physical layer C-PHY data packet according to various embodiments of the present disclosure is shown. The D-PHY data packet 400 includes a data identifier 402, such as Figure 4C As shown, the data identifier may include a 2-bit VC identifier 482 and a 6-bit DT information 484 . Figure 4A 400 further includes: a 16-bit word count 404; an ECC and VCX field 206, wherein the ECC can enable bit error detection and correction in a packet header including fields 402 to 406; a payload 408 to 410, e.g., 8-bit wide pixel data; and a packet trailer 412. In contrast, a C-PHY data packet 401 includes: a RES and VCX field 420; a data identifier 422; a 16-bit word count 424; a 16-bit checksum 426, wherein the packet header includes fields 420 to 426; a payload 428 to 430; and a packet trailer 432.
[0036] In an embodiment, Figure 5 , which summarizes an exemplary mapping between D-PHY and C-PHY for corresponding long packets and short packets according to various embodiments of the present disclosure, Figure 4A The data identifier 402 and the 16-bit word count 404 in the long packet structure physical layer D-PHY data packet 400 in FIG. 400 can be directly mapped to the corresponding data identifier 422 and the 16-bit word count 424 in the long packet structure physical layer C-PHY data packet 401. Similarly, Figure 4B The data identifier 440 and the 16-bit short packet data field 442 in the short packet structure physical layer D-PHY data packet 460 can be directly mapped to the corresponding data identifier 452 and the 16-bit short packet data field 454 in the short packet structure physical layer C-PHY data packet 461.
[0037] from Figure 5 As can be seen, the figure highlights the similarities and differences in the header structure and packet structure for D-PHY and C-PHY long and short packets, including the 16-bit word count and VCX. The two main differences between the D-PHY and C-PHY header packets for long and short packets are: (1) the ECC data (i.e., a number calculated based on certain header data information) does not match the CRC data (i.e., a number calculated based on other header data information), and (2) the reserved field RES, which is present in the C-PHY header packet but not in the D-PHY header packet.
[0038] Note that since the C-PHY protocol and the D-PHY protocol use different header information, packet structures, and data protection mechanisms specified by each protocol, in existing systems and applications (such as systems and applications using a pixel mode in which pure pixel data is transmitted without paying too much attention to data protection), the packet sent by a device at one end of the communication path and obtained by the serializer is different from the packet output by the deserializer to another device at the other end of the communication path, which creates problems such as possible data loss, undetected data corruption, etc. during transmission (for example, along a 15m cable).
[0039] In contrast, according to FIG. 4A to FIG. 4C and Figure 5 Embodiments presented herein convert portions of a data packet that protect the transmitted data from one format compliant with one protocol (e.g., D-PHY) to another format compliant with a different protocol (e.g., C-PHY) to reconcile otherwise incompatible protocols to enable reliable, high-speed end-to-end communications for safety-critical applications. Various embodiments take advantage of the fact that certain data in the C-PHY header and the D-PHY header are similar or identical.
[0040] Figure 6 An exemplary communication system according to various embodiments of the present disclosure is shown. As depicted, the communication system 600 includes a camera sensor 602, which can be any device that generates or processes image data (such as LIDAR or radar data); a communication serializer 604, for example, a multi-port GMSL serializer; a communication interface 612, for example, a MIPI D-PHY interface; and a link 614, for example, a bidirectional GMSL interface that can be implemented, for example, over a single coaxial cable or a shielded twisted pair cable. The communication system 600 can further include a deserializer 606 that outputs data 620 (e.g., a deserialized GMSL stream) at an output interface 618 (e.g., a MIPI C-PHY interface) that is designed to be coupled to a MIPI SoC 608 or any other processing device.
[0041] although Figure 6 Not shown, but it should be understood that other and additional components, such as microcontrollers, memory devices, etc., may be employed, for example, to program the serializer 604, the deserializer 606, or any peripheral device, such as to assist in data aggregation, conversion, encryption, and performing signal processing and auxiliary functions to achieve the purposes of the present disclosure. For example, the serialized stream may include a reference clock signal that may be provided by a phase-locked loop (PLL) oscillator. According to various embodiments of the present disclosure, the serializer 604 and / or the deserializer 606 may include a protocol converter that converts at least a portion of a data packet compatible with one protocol (e.g., a header) to be compatible with another protocol.
[0042] In an embodiment, in response to data packet 613 arriving at serializer 604, for example (on a differential data channel on communication interface 612), serializer 604 may serialize data packet 613 and transmit serialized data 616, for example, one bit at a time over a single wire and at a relatively high rate. The transmitted data 616 may be received and processed at deserializer 606 using a C-PHY-based protocol, for example, at a relatively high rate, and then fed to SoC 608 for further image, audio, etc. processing.
[0043] It should be understood that interface 612 represents multiple interfaces that receive data packets from any number of sources, and serialized data 616 can be aggregated with data from any number of communication serializers (e.g., 604). It is further understood that many existing standards and protocol types that may be based on different data structures can also benefit from the teachings of the present disclosure, even if not explicitly mentioned herein.
[0044] In an embodiment, the camera sensor 602 may generate a MIPID-PHY packet 613 including a MIPID-PHY CSI-2 ECC value in its header and provide the packet 613 to the serializer 604, for example, at the communication interface 612. In response to the serializer 604 receiving the MIPID-PHY CSI-2 packet 613 for transmission from the camera sensor 602 at the communication interface 612, the serializer 604 may convert the received packet, for example, into a serialized GMSL packet stream 616, which may be provided to the deserializer 606 via a wired GMSL interface. In an embodiment, the serializer 604 may extract the incoming ECC value from the packet 613 and perform error checking or correction, for example, according to the D-PHY protocol by using a D-PHY algorithm that calculates the ECC value and compares it to the ECC value in the received header to, for example, verify whether the data ID, word count, and VCX in the D-PHY packet have been correctly transmitted to the serializer 604.
[0045] In an embodiment, in pixel transfer mode, the serializer 604 may, in response to validating the incoming MIPID-PHY CSI-2 ECC, strip the ECC from the CSI-2 packet 613 and transmit substantially only the pixel data (e.g., 616) to the deserializer 606. In an embodiment, independent of the transfer mode, to protect the data traveling on the link 614, the serializer 604 may protect the stripped packet by adding (e.g., appending) a CRC (e.g., a GMSL CRC) to the packet before transmitting such packet over the link 614.
[0046] In an embodiment, the deserializer 606, in response to receiving a MIPI CSI-2 packet including a GMSL CRC, can remove the CRC, for example, after a CRC check to determine whether the CSI-2 CRC value matches the data. In addition, the deserializer 606 generates and / or adds a C-PHY CRC to the packet before passing the packet to the SoC 608 via the MIPI CSI-PHY interface 618.
[0047] In the embodiment, according to FIG. 4A to FIG. 4B and Figure 5 , once the conversion or translation mode has been enabled, the serializer 604 or deserializer 606 can reorder the received D-PHY packet header to convert it into a new packet header that includes a C-PHY packet header structure with a 16-bit CRC field. (Conversely, the C-PHY header packet may be reordered into a D-PHY packet header with a 6-bit ECC value). The C-PHY CRC can prevent data corruption from occurring, for example, between the serializer 604 checking the D-PHY ECC and the deserializer 606 generating the C-PHY MIPI CSI-2 packet. In this way, the communication system 600 can ensure that the header data in the newly formed C-PHY packet header matches the incoming D-PHY MIPI CSI-2 packet. In an embodiment, to form the C-PHY packet header, the data ID and word count of the D-PHY packet can be used to directly convert to the corresponding fields of the C-PHY header. According to FIG. 4A to FIG. 4B and Figure 5 In an embodiment, when converting VCX, a bit (e.g., zero) may be added to satisfy the C-PHY protocol, which uses the third bit to provide 32 options for VCX, unlike the D-PHY protocol. In addition, the RES value may be set to zero. Note that in pixel mode, the data field in the packet containing pixel data does not need to be modified.
[0048] In an embodiment, based on the order of the newly generated C-PHY packets and their header information, and before transmitting the packets, an internal or local CRC (e.g., a 16-bit CRC) can be generated, for example, by checking the data in the header of the generated C-PHY packets. This can be achieved by calculating the CRC value and comparing it with the data in the incoming D-PHY packet to ensure that the data in the two packets match each other, or in other words, to ensure that the D-PHY packet has been correctly converted into a C-PHY packet and there are no bit errors, thereby ensuring the integrity of the data. The newly formed packet can then be transmitted to the SoC 608 for further processing. In an embodiment, if the CRC operation does reveal a bit error that may have occurred on the line (unlike ECC, this is generally uncorrectable), some predetermined measures can be taken, for example, a flag can be generated and the defective packet can be discarded.
[0049] In an embodiment, instead of receiving a MIPI C-PHY CSI-2 packet 612 to be transmitted from the camera sensor 602, the serializer 604 may receive a MIPI C-PHY CSI-2 packet (not shown) with a MIPI C-PHY CSI-2 CRC value in its header. In pixel mode, the serializer 604 may extract the CRC value from the packet, perform error checking according to the C-PHY protocol to calculate a CRC value that is compared to the CRC value in the received header. In response to verifying the CRC, the serializer 604 may strip the CRC from the CSI-2 packet, add a GMSL CRC to protect the data traveling on the link 614, and convert the data into a serialized packet stream, and then transmit the MIPI CSI-2 pixel data including the added GMSL CRC to the deserializer 606. The deserializer 606 may then perform a CRC check to determine whether the CSI-2 CRC value matches the data; remove the GMSL CRC; and add a D-PHY ECC to the packet before passing the packet to the SoC 608 via the MIPI D-PHY interface (not shown).
[0050] In an embodiment, the communication system 600 can operate in a tunnel mode that facilitates end-to-end ECC or CRC protection from the camera sensor 602 to the SoC 608. In tunnel mode, in response to verifying the incoming MIPI D-PHY CSI-2 ECC, the serializer 604 can, for example, transmit the entire MIPI CSI-2 packet in a transparent manner, including the D-PHY ECC after adding the GMSL CRC to the D-PHY CSI-2 packet. As in pixel mode, in response to receiving a packet including the GMSL CRC, the deserializer 606 can perform a CRC check; remove the D-PHY CRC; check and remove the D-PHY ECC; and add a C-PHY CRC to the MIPI CSI-2 packet to generate a C-PHY MIPI CSI-2 packet, and then pass the generated packet to the SoC 608 via the MIPI C-PHY interface 618.
[0051] Note that while the examples herein are depicted as utilizing only one deserializer 606, this is not intended to limit the scope of the present disclosure, as any number of deserializers (e.g., 606) may be used. Thus, embodiments may utilize, for example, dual deserializers or quad deserializers, each of which may have an appropriate number of MIPI ports and may be frame synchronized to aggregate video streams. Further note that, for example, for redundancy purposes, the header information in the modified data packet may be transmitted to the second interface more than once, for example, based on the number of lanes and / or the communication mode used.
[0052] Figure 7 700 may begin at step 705 when, at a first interface, such as a serializer interface designed to be coupled to a first device (such as a camera), a data packet compliant with a first communication protocol (e.g., a D-PHY protocol) is received, including a header portion and a payload portion.
[0053] In an embodiment, the header portion may include fields, and at a second step 710, the protocol converter may modify these fields, for example by replacing, removing or adding fields and / or bits depending on the transmission type, to generate a modified data packet, which includes an error detection or error correction field (for example, a CRC or ECC field that may be based on some modified fields) that may comply with a second communication protocol (for example, a C-PHY protocol).
[0054] Finally, at step 715, the modified data packet may be transmitted to a second interface (eg, in a deserializer) designed to be coupled to a second device, such as a processor in a SoC.
[0055] In one or more embodiments, aspects of the present patent document may relate to, include, or be implemented on one or more information handling systems (or computing systems). An information handling system / computing system may include any tool or collection of tools operable to calculate, compute, determine, classify, process, transmit, receive, retrieve, cause, route, switch, store, display, deliver, manifest, detect, record, reproduce, process, or utilize any form of information, intelligence, or data. For example, a computing system may be or may include a personal computer (e.g., a laptop), a tablet computer, a mobile device (e.g., a personal digital assistant (PDA), a smart phone, a tablet phone, a tablet computer, etc.), a smart watch, a server (e.g., a blade server or a rack server), a network storage device, a camera, or any other suitable device, and may vary in size, shape, performance, functionality, and price. A computing system may include random access memory (RAM), one or more processing resources such as a central processing unit (CPU) or hardware or software control logic, read-only memory (ROM), and / or other types of memory. Additional components of a computing system may include one or more disk drives, one or more network ports for communicating with external devices, and various input and output (I / O) devices, such as a keyboard, mouse, stylus, touch screen, and / or video display. A computing system may also include one or more buses operable to transmit communications between various hardware components.
[0056] Figure 8 800 is a simplified block diagram of an information handling system (or computing system) according to an embodiment of the present disclosure. It will be understood that the illustrated functionality of system 800 may operate to support various embodiments of the computing system, but it should be understood that the computing system may be configured in different ways and include different components, including having Figure 8 Fewer or more components than depicted in FIG.
[0057] like Figure 8 As shown, computing system 800 includes one or more central processing units (CPUs) 801 that provide computing resources and control the computer. CPU 801 can be implemented using a microprocessor or the like, and can also include one or more graphics processing units (GPUs) 802 and / or floating point coprocessors for mathematical calculations. In one or more embodiments, one or more GPUs 802 can be incorporated into a display controller 809, such as part of one or more graphics cards. System 800 can also include system memory 819, which can include RAM, ROM, or both.
[0058] Multiple controllers and peripherals are also available, such as Figure 8As shown. Input controller 803 represents an interface to various input devices 804 such as a keyboard, mouse, touch screen and / or stylus. The computing system 800 may also include a storage controller 807 for interfacing with one or more storage devices 808, each of which includes a storage medium such as a tape or disk, or an optical medium that can be used to record instruction programs of operating systems, utilities and applications, which programs may include embodiments of programs that implement various aspects of the present disclosure. (Multiple) storage devices 808 may also be used to store processed data or data to be processed according to the present disclosure. The system 800 may also include a display controller 809 for providing an interface to a display device 811, which may be a cathode ray tube (CRT) display, a thin film transistor (TFT) display, an organic light emitting diode, an electroluminescent panel, a plasma panel, or any other type of display. The computing system 800 may also include one or more peripheral device controllers or interfaces 805 for one or more peripheral devices 806. Examples of peripheral devices may include one or more printers, scanners, input devices, output devices, sensors, etc. The communication controller 814 can interface with one or more communication devices 815, which enables the system 800 to connect to remote devices through any of a variety of networks, including the Internet, cloud resources (e.g., Ethernet cloud, Fibre Channel over Ethernet (FCoE) / Data Center Bridging (DCB) cloud, etc.), local area network (LAN), wide area network (WAN), storage area network (SAN) or through any suitable electromagnetic carrier signal (including infrared signals). As shown in the depicted embodiment, the computing system 800 includes one or more fans or fan trays 818 and one or more cooling subsystem controllers 817, which monitor the thermal temperature(s) of the system 800 (or its components) and operate the fans / fan trays 818 to help regulate the temperature.
[0059] In the system shown, all major system components can be connected to bus 816, which can represent more than one physical bus. However, the various system components may or may not be physically close to each other. For example, input data and / or output data can be remotely transmitted from one physical location to another. In addition, programs that implement various aspects of the present disclosure can be accessed from a remote location (e.g., a server) over a network. Such data and / or programs can be transmitted by any of a variety of machine-readable media including, for example, the following: magnetic media, such as hard disks, floppy disks, and tapes; optical media, such as CD-ROMs and holographic devices; magneto-optical media; and hardware devices specifically configured for storage or for storing and executing program code, such as application specific integrated circuits (ASICs), programmable logic devices (PLDs), flash memory devices, other non-volatile memory (NVM) devices (such as 3D XPoint-based devices), and ROM devices and RAM devices.
[0060] Aspects of the present disclosure may be encoded on one or more non-transient computer-readable media using instructions for one or more processors or processing units to enable steps to be performed. It should be noted that the one or more non-transient computer-readable media should include volatile memory and / or non-volatile memory. It should be noted that alternative implementations are possible, including hardware implementations or software / hardware implementations. (Multiple) ASICs, programmable arrays, digital signal processing circuit systems, etc. can be used to implement the functions of hardware implementations. Therefore, the "means" term in any claim is intended to cover both software implementations and hardware implementations. Similarly, the term "one or more computer-readable media" as used herein includes software and / or hardware or a combination thereof having an instruction program embodied thereon. In view of these alternatives to the embodiments, it will be understood that the accompanying drawings and accompanying descriptions provide functional information that will be needed for those skilled in the art to write program code (i.e., software) and / or manufacture circuits (i.e., hardware) to perform the required processing.
[0061] It should be noted that the embodiments of the present disclosure may further relate to a computer product having a non-transitory tangible computer-readable medium having thereon computer code for performing various computer-implemented operations. The medium and computer code may be specially designed and constructed for the purposes of the present disclosure, or they may belong to the types known or available to those skilled in the relevant art. Examples of tangible computer-readable media include, for example: magnetic media, such as hard disks, floppy disks, and tapes; optical media, such as CD-ROMs and holographic devices; magneto-optical media; and hardware devices specially configured for storing or for storing and executing program codes, such as application specific integrated circuits (ASICs), programmable logic devices (PLDs), flash memory devices, other non-volatile memory (NVM) devices (such as 3DXPoint-based devices), and ROM devices and RAM devices. Examples of computer code include machine code such as generated by a compiler and files containing high-level code executed by a computer using an interpreter. The embodiments of the present disclosure may be implemented in whole or in part as machine executable instructions that may be in a program module executed by a processing device. Examples of program modules include libraries, programs, routines, objects, components, and data structures. In a distributed computing environment, program modules may be physically located in local, remote, or both environments.
[0062] Those skilled in the art will recognize that no computing system or programming language is essential for the practice of the present disclosure. Those skilled in the art will also recognize that the multiple elements described above can be physically and / or functionally divided into multiple modules and / or submodules or combined together.
[0063] It will be understood by those skilled in the art that the foregoing examples and embodiments are exemplary and not limiting of the scope of the present disclosure. It is intended that all permutations, enhancements, equivalents, combinations, and improvements thereto that are apparent to those skilled in the art after reading this specification and studying the drawings are included within the true spirit and scope of the present disclosure. It should also be noted that the elements of any claim may be arranged in different ways, including with multiple dependencies, configurations, and combinations.
Claims
1. A secure end-to-end high-speed data communication method, the method comprising: receiving a data packet compliant with a first Mobile Industry Processor Interface (MIPI) protocol, the data packet comprising a header portion and a payload portion; modifying the header portion of the data packet to create a modified data packet compliant with a second MIPI protocol; verifying said header portion of said modified data packet based on an error detection process applied to at least one field within said header portion; as well as The modified data group is output.
2. The method of claim 1, wherein: The first MIPI protocol is a D-Physical Layer (PHY) protocol, and the second MIPI protocol is a C-PHY protocol, or vice versa.
3. The method of claim 1, wherein: The data packet is received at a first interface coupling a first device to a serializer, and wherein the modified data packet is output at a second interface coupling a second device to a deserializer.
4. The method of claim 3, wherein: The serializer and the deserializer communicate over a bidirectional link supporting the first MIPI protocol and the second MIPI protocol, and the second device includes a processor implemented on a system on a chip (SoC).
5. The method of claim 1, wherein: The modified data packet is generated by modifying at least one field among the multiple fields or multiple bits in one or more fields.
6. The method of claim 1, wherein: The error detection process includes at least one of a cyclic redundancy check (CRC) or an error correction code (ECC).
7. The method of claim 6, further comprising performing an inner CRC checksum by using at least one of: a data identifier, a word count, or a virtual channel extension.
8. A high-speed serializer, comprising: An input interface for receiving a data packet compliant with a first Mobile Industry Processor Interface (MIPI) protocol, the data packet comprising a header portion and a payload portion; a protocol converter coupled to the input interface, the protocol converter modifying the header portion of the data packet to create a modified data packet compliant with a second MIPI protocol; an error detector coupled for receiving the modified data packet, the error detector validating the modified data packet based on an error detection process applied to at least one field within the header portion; as well as An output interface outputs the modified data packet to a device.
9. The high speed serializer of claim 8, wherein: The first MIPI protocol is a D-Physical Layer (PHY) protocol, and the second MIPI protocol is a C-PHY protocol, or vice versa.
10. The high speed serializer of claim 8, wherein: The output interface couples the device to a deserializer.
11. The high speed serializer of claim 10, wherein: The high-speed serializer and the deserializer communicate over a bidirectional link supporting the first MIPI protocol and the second MIPI protocol, and the device includes a processor implemented on a system on a chip (SoC).
12. The high speed serializer of claim 10, wherein: The protocol converter is coupled to at least one of a serializer or a deserializer.
13. The high speed serializer of claim 8, wherein: The modified data packet is generated by modifying at least one field among the multiple fields or multiple bits in one or more fields.
14. The high speed serializer of claim 8, wherein: The error detection process includes at least one of a cyclic redundancy check (CRC) or an error correction code (ECC).
15. A secure end-to-end high-speed data encoding and communication method, the method comprising: receiving a D-physical layer (PHY) data packet including a header portion and a payload portion; modifying the header portion of the D-PHY data packet to create a C-PHY data packet; validating the header portion of the C-PHY data packet based on an error detection process applied to at least one field within the header portion; as well as Output the modified data grouping.
16. The method of claim 15, wherein: The data packet is received at a first interface coupling a first device to a serializer, and wherein the modified data packet is output at a second interface coupling a second device to a deserializer.
17. The method of claim 16, wherein: The serializer and the deserializer communicate via a bidirectional link supporting a MIPI protocol, and the second device includes a processor implemented on a system on a chip (SoC).
18. The method of claim 15, wherein: The C-PHY data packet is generated by modifying at least one field among a plurality of fields or a plurality of bits among one or more fields.
19. The method of claim 15, wherein: The error detection process includes at least one of a cyclic redundancy check (CRC) or an error correction code (ECC).
20. The method of claim 19, further comprising performing an inner CRC checksum by using at least one of: a data identifier, a word count, or a virtual channel extension.
