Transmission system, transmission device and transmission method
The transmission system and method address inefficiencies in MIPI A-PHY packet error notification by using error notification data with MC numbers and various formats, improving error recovery speed and efficiency.
Patent Information
- Application Number
- DE112024001114
- Authority / Receiving Office
- DE · DE
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-02-20
- Publication Date
- 2025-12-24
AI Technical Summary
Current packet error notification schemes in MIPI A-PHY standards are inefficient due to the time required for processing packet errors, necessitating a more suitable and timely notification mechanism.
A transmission system and method that involves generating error notification data with an added MC number for error packets, allowing for direct notification and recovery of packet types using correspondence information, and employing various notification formats such as PKTERR+MC, CM+CN+MC, and error notification packets to expedite error reporting.
Enhances the efficiency of packet error notification by reducing data length and transmission time, enabling faster recovery and processing of packet errors in MIPI A-PHY networks.
Smart Images

Figure 00000021_0000 
Figure 00000022_0000 
Figure 00000023_0000
Abstract
Description
TECHNICAL AREA
[0001] The present disclosure relates to a transmission system, a transmission device and a transmission method, and in particular to a transmission system, a transmission device and a transmission method that enable more suitable notification of a packet error. STATE OF THE ART
[0002] One of the standards defined by the Mobile Industry Processor Interfaces (MIPI) Alliance is the Automotive PHY (A-PHY) standard (see, for example, Non-Patent Document 1). The A-PHY is a standard that applies to a PHY layer of a serializer / deserializer (SerDes) for use in vehicles. An A-PHY network uses an A-packet. CITATION LIST NON-PATENT DOCUMENT
[0003] Non-Patent Document 1: MIPI Alliance Specification for A-PHY, Version 1.1, MIPI Alliance, Inc., August 9, 2021. SUMMARY OF THE INVENTION PROBLEMS THAT THE INVENTION IS INTENDED TO SOLVE.
[0004] In a current scheme, if an error occurs in an A packet being transmitted, a receiving page notifies a transmitting page of the packet error according to a determination made by an upper layer. However, there is a problem with the time required to process the packet error, and a new scheme for packet error notification has been proposed.
[0005] The present disclosure was made in view of such circumstances and is intended to provide a more suitable notification of the packet error in a case where an error occurs in a packet. SOLUTIONS FOR THE PROBLEMS
[0006] A transmission system according to one aspect of the present disclosure is a transmission system with a first transmission device and a second transmission device connected via an A-PHY-I / F defined in a MIPI standard, wherein the first transmission device comprises a first transmission unit which, in a case where an error is detected in an A packet transmitted by the second transmission device, generates error notification data to which an MC number of an error packet, which is the A packet in which the error was detected, is added, and transmits the generated error notification data to the second transmission device, the second transmission device comprising a second transmission unit which holds correspondence information in which a type of the transmitted A packet is associated with an MC number of the A packet, and in a case wherein which the fault notification data transmitted by the first transmission device is received, a type of A-packet is determined from the held correspondence information according to the MC number of the fault packet added to the received fault notification data, and a type of fault packet is recovered, and the first transmission unit and the second transmission unit perform processing with respect to A-PHY.
[0007] In the transmission system according to one aspect of the present disclosure, the first transmission device and the second transmission device are connected via the A-PHY-I / F defined in the MIPI standard. In a case where an error is detected in an A packet transmitted by the second transmission device, the first transmission unit of the first transmission device generates error notification data to which an MC number of an error packet is added, which is the A packet in which the error was detected, and transmits the generated error notification data to the second transmission device. The second transmission unit of the second transmission device holds correspondence information in which the type of the transmitted A packet is associated with the MC number of the A packet. In a case where the error notification data transmitted by the first transmission device is received,From the held correspondence information, the type of the A packet is determined according to the MC number of the error packet added to the received error notification data, and a type of the error packet is recovered. Additionally, the first and second transmission units perform processing with respect to A-PHY.
[0008] A transmission device according to one aspect of the present disclosure comprises a transmission unit that receives an A packet transmitted by another transmission device connected via an A-PHY-I / F defined in a MIPI standard, in a case where an error is detected in the A packet, generates error notification data to which an MC number of an error packet is added, which is the A packet in which the error was detected, and transmits the generated error notification data to the other transmission device, and the transmission unit performs processing with respect to A-PHY.
[0009] A transmission method according to one aspect of the present disclosure is a transmission method of a transmission device with a transmission unit that performs processing with respect to A-PHY as defined in a MIPI standard, wherein the transmission method comprises the transmission unit receiving an A packet transmitted by another transmission device connected via an A-PHY I / F, generating error notification data in a case where an error is detected in the A packet, to which an MC number of an error packet is added, which is the A packet in which the error was detected, and transmitting the generated error notification data to the other transmission device.
[0010] In the transmission device and transmission method according to one aspect of the present disclosure, the A packet, which is transmitted from another transmission device connected via the A-PHY-I / F, is received by the transmission unit, which performs processing with respect to A-PHY as defined in the MIPI standard, and in a case where an error is detected in the A packet, error notification data is generated, to which an MC number of an error packet is added, which is the A packet in which the error was detected, and the generated error notification data is transmitted to the other transmission device.
[0011] A transmission device according to one aspect of the present disclosure is a transmission device comprising: a transmission unit that transmits an A packet to another transmission device connected via an A-PHY-I / F defined in a MIPI standard, holds correspondence information in which a type of the transmitted A packet is associated with an MC number of the A packet, in a case where error notification data transmitted from the other transmission device is received, retrieves from the held correspondence information a type of A packet corresponding to an MC number of an error packet added to the received error notification data, and restores a type of A packet in which an error was detected as the error packet in which the transmission unit performs processing with respect to A-PHY.
[0012] A transmission method according to one aspect of the present disclosure is a transmission method of a transmission device with a transmission unit that performs processing with respect to A-PHY as defined in a MIPI standard, wherein the transmission method comprises the transmission unit transmitting an A packet to another transmission device connected via an A-PHY I / F, holding correspondence information in which a type of the transmitted A packet is associated with an MC number of the A packet, and in a case where error notification data transmitted from the other transmission device is received, retrieving from the held correspondence information a type of A packet corresponding to an MC number of an error packet added to the received error notification data, and restoring a type of A packet in which an error was detected as the error packet.
[0013] In the transmission device and transmission method according to one aspect of the present disclosure, an A-packet is transmitted from the transmission unit performing processing with respect to A-PHY to another transmission device connected via an A-PHY-I / F, correspondence information is held in which a type of the transmitted A-packet is associated with an MC number of the A-packet, and in a case where error notification data transmitted from the other transmission device is received, a type of A-packet corresponding to an MC number of an error packet added to the received error notification data is retrieved from the held correspondence information, and the type of A-packet in which an error was detected is recovered as the error packet.
[0014] It should be noted that, according to one aspect of the present disclosure, the transmission device may be an independent device or an internal block forming a device. BRIEF DESCRIPTION OF THE DRAWINGS Fig. Figure 1 is a view illustrating a configuration example of an embodiment of a transmission system to which the present disclosure is applied. Fig. Figure 2 is a view illustrating a first example of a configuration of an error notification package to which a new scheme is applied. Fig. Figure 3 is a view that illustrates a second example of the configuration of the error notification package to which the new scheme is applied. Fig. Figure 4 is a view to explain IPG+packet, which is used in a current scheme. Fig. Figure 5 is a view illustrating a combination of ISS and Idle of EOI from the current scheme. Fig. Figure 6 is a view to explain PKTERR+MC, to which the new scheme is applied. Fig. Figure 7 is a view illustrating an example of a combination of ISS and Idle that differs from EOI in a case where the new scheme is applied. Fig. Figure 8 is a view illustrating a transfer of PKTERR+MC and additional information to which the new scheme is applied. Fig. Figure 9 is a view that illustrates an example of control nibbles to which the new schema is applied. Fig. 10 is a view to explain CM+CN+MC, to which the new scheme is applied. Fig. Figure 11 is a view illustrating a transfer of CM+CN+MC and additional information to which the new scheme is applied. Fig. Figure 12 is a view illustrating a configuration example of a source and a sink that can handle a case where a downlink A packet is corrupted or lost. Fig. Figure 13 is a view showing the flow of a signal during a notification using an error notification packet in a case where a downlink A packet is corrupted or lost. Fig. Figure 14 is a view showing the flow of a signal during a notification using CM+CN+MC in a case where a downlink A packet is corrupted or lost. Fig. Figure 15 is a view illustrating a configuration example of a source and a sink that can handle a case where an uplink A packet is corrupted or lost. Fig. Figure 16 is a view showing the flow of a signal during a notification using an error notification packet in a case where an uplink A packet is corrupted or lost. Fig. Figure 17 is a view showing the flow of a signal during a notification using PKTERR+MC in a case where an Uplink-A packet is damaged or lost. Fig. Figure 18 is a flowchart showing a series of flows until a notification is given to a sink side in a case where damage to or loss of a received packet is detected on a source side. Fig. Figure 19 is a flowchart showing the flow of processing a receive error notification and notification analysis to be performed between the source and the sink. Fig. 20 is a view that shows an example of a customization type. Fig. 21 is a view that shows an example of a customization type. Fig. Figure 22 is a flowchart showing a series of flows until a notification is given to a source side in a case where damage to or loss of a received packet is detected on a sink side. Fig. Figure 23 is a flowchart showing the flow of processing a receive error notification and notification analysis to be performed between the sink and the source. Fig. Figure 24 is a sequence diagram showing signals to be exchanged between the source side and the sink side in a case where the current scheme is used. Fig. Figure 25 is a sequence diagram illustrating signals to be exchanged between the source side and the sink side in a case where the new scheme is used. Mode for executing the invention <systemkonfiguration>
[0015] Fig. Figure 1 is a view illustrating a configuration example of an embodiment of a transmission system to which the present disclosure is applied.
[0016] In Fig. Document 1 comprises a transmission system 1, a transmission device 10, and a transmission device 20. The transmission device 10 and the transmission device 20 exchange data via a transmission path 30, such as a cable. In the transmission system 1, data is transmitted between the transmission device 10 and the transmission device 20 via an A-PHY network. A-PHY is a standard defined by the MIPI Alliance as a SerDes physical layer for use in vehicles. In this disclosure, the standard defined by the MIPI Alliance is referred to as the MIPI Standard.
[0017] The transmission device 10 comprises a processing unit 101 and a transmission unit 102. The processing unit 101 comprises a chip that performs processing with respect to a protocol adaptation layer (PAL), a central processing unit (CPU) that controls the operation of each unit of the transmission device 10, and the like. The transmission unit 102 comprises a chip that performs processing with respect to data transmission, and the like. The transmission unit 102 performs processing with respect to A-PHY (processing a PHY layer and a data link layer). The processing unit 101 performs processing with respect to an upper layer, which is an upper layer of A-PHY.
[0018] The transmission device 20 comprises a processing unit 201 and a transmission unit 202. The processing unit 201 comprises a chip that performs processing with respect to PAL, a CPU that controls the operation of each unit of the transmission device 20, and the like. The transmission unit 202 comprises a chip that performs processing with respect to data transmission, and the like. The transmission unit 202 performs processing with respect to A-PHY. The processing unit 201 performs processing with respect to an upper layer, which is an upper layer of A-PHY.
[0019] In transmission system 1, one of the transmission devices 10 and 20 serve as a source, and the other serves as a sink. The source and sink are defined in the MIPI standard, and the following description presents an example case where transmission device 10 is the source and transmission device 20 is the sink. Transmission from the source to the sink is called the downlink, and transmission from the sink to the source is called the uplink. The transmission speed (communication speed) differs between the downlink and the uplink, with the downlink transmission speed being higher than the uplink transmission speed.
[0020] Here, for example, in transmission system 1, a case is assumed in which an A packet is transmitted from transmission device 10 on the source side to transmission device 20 on the sink side via serial communication over transmission path 30. In this case, processing unit 101 processes data in various schemes, such as general-purpose input / output (GPIO), interconnected circuit (I2C), serial camera interface 2 (CSI2), and serial peripheral interface (SPI). Processing unit 101 generates an A packet from data in these different schemes.
[0021] The transmission unit 102 transmits the A packet generated by the processing unit 101. In this case, a message counter number (MC number) is added to the A packet to be transmitted. For example, the MC number is a value from 0 to 255, and a different number is added for each A packet. In this example, the MC number can be added continuously by setting a starting value to 0, incrementing it for each A packet, and reverting to 0 when the value reaches 255. The transmission unit 102 can maintain a transmission table as correspondence information, in which a type of transmitted A packet is associated with the MC number.In other words, the MC number is added to the A packet to be transmitted, and thus the transmission table, in which the type (protocol type) of the data stored in the A packet is associated with the MC number added to the A packet, can be maintained until a certain period of time has elapsed since the transmission of the A packet. For example, in the transmission table, MC = 0, MC = 1, MC = 2, MC = 3, and so on are each associated with GPIO, CSI2, CSI2, and I2C, respectively.
[0022] In this case, when an error occurs in the A packet being transmitted, the sink's transmission unit 202 detects the error, generates error notification data, and transmits this data to the source's transmission unit 102. The error notification data includes the MC number of the error packet, which is the A packet in which the error was detected. Upon receiving the error notification data transmitted by transmission unit 202, transmission unit 102 consults its transmission table and determines the type (protocol type) of the A packet corresponding to the MC number of the error packet contained in the error notification data. As a result, transmission unit 102 can reconstruct the error packet type and notify processing unit 101 of the error packet type.
[0023] It should be noted that even if an error occurs in a case where the A packet is transmitted from the transmission device 20 on the sinking side to the transmission device 10 on the source side, essentially similar processing is carried out, although the processing on the source side and the processing on the sinking side are reversed, which will be described in detail later.
[0024] As described above, transmission system 1 uses a scheme in which transmission unit 102 or transmission unit 202, which is performing processing with respect to A-PHY, directly notifies the receiving transmission unit that an error has occurred in the A packet being transmitted between transmission device 10 on the source side and transmission device 20 on the receiving side. Any of the following three notification methods can be used for this new scheme.
[0025] The first notification method involves redefining a packet (packet error notification packet) to notify the A packet of an error and send a notification of the error's occurrence. The second notification method involves redefining a PKTERR+MC format for an IPG+ packet used in the current scheme and sending a notification of an error in the A packet via PKTERR+MC. Details of IPG+ packet and PKTERR+MC are described later. The third notification method involves redefining a packet error notification (PER) format in control nibbles (CN) for CM+CN used in the current scheme and sending a notification of an error in the A packet via CM+CN+MC.Details of CM+CN and CM+CN+MC will be described later. Details of the three notification procedures are described below in sequence. <Erstes Benachrichtigungsverfahren>
[0026] In the first notification procedure, a packet (packet error notification packet, hereinafter also referred to as error notification packet) is redefined to provide notification of an error in the A packet, and notification of the occurrence of the error is provided by the packet.
[0027] Fig. Figure 2 is a view illustrating a first example of a configuration for an error notification package to which the new scheme is applied. As shown in Fig. Figure 2 illustrates that the error notification packet is configured as an A packet. Fig. 2. The A packet comprises an A packet header, an A packet payload, and an A packet tail.
[0028] The A packet header includes an eight-bit adaptation descriptor field, an eight-bit service descriptor field, an eight-bit placement descriptor field, an eight-bit PHY2 field, an eight-bit destination address field, an eight-bit PHY3 field, an eight-bit payload length field, and an eight-bit PHY header CRC field.
[0029] The matching descriptor includes a matching type field of four bits, and the remaining bits are reserved (Res). The service descriptor includes a PHY1 field of two bits, a priority field of two bits, a quality of service (QoS) field of two bits, and a poor indication (BAD) field of one bit, and the remaining bits are reserved (Res). The placement descriptor includes a matching layer specific information (ALEI) field of three bits, an odd byte (OB) field of one bit, and an order field of two bits, and the remaining bits are reserved (Res).
[0030] One value of the adaptation type of the adaptation descriptor is 4'h1. In a case where the adaptation type value is set to 1 (4'h1), it indicates that the service is a link service. One value of ALEI is 3'b100. Here, ALEI = 3'b000, 3'b001 has already been defined in the current schema, and thus unused ALEI = 3'b100 is used in the new schema.
[0031] The A-packet payload includes fields for BAD or DROP, MC number, and timestamp. BAD or DROP is a field containing a damage / loss flag indicating whether an error packet is damaged (BAD) or lost (DROP). MC number is a field containing the MC number of the error packet. Timestamp is a field containing a timestamp. Note that the error notification packet in Fig. 2 is a packet that is defined by the link service and can be retransmitted.
[0032] Fig. Figure 3 is a view that illustrates a second example of the configuration of the error notification package to which the new scheme is applied. Fig. 3 is the error notification package, configured as the A package, in a similar way to the configuration in Fig. 2 is configured, but the value of the adaptation type is different. In other words, in the A packet header, the value of the adaptation type of the adaptation descriptor is 4'h0. In a case where the value of the adaptation type is set to 0(4'h0), it indicates that the service is a PHY service. A value of ALEI is 3'b100. In Fig. 3 includes the A-packet payload fields of BAD or DROP, MC number, and timestamp. Note that the error notification packet is in Fig. 3 is a packet that is defined by the PHY service and cannot be retransmitted.
[0033] As described above, in the first notification method, the error notification packet, which is the packet used to notify the A packet of an error, is defined in the link service or PHY service defined in the MIPI standard, and notification of the error can be sent via this packet. The first notification method can be used in both the uplink and downlink. For example, the source transmission unit 102 can send an error notification packet to the sink transmission unit 202 to notify the A packet of an error. Furthermore, the sink transmission unit 202 can send an error notification packet to the source transmission unit 102 to notify the A packet of an error. <Zweites Benachrichtigungsverfahren>
[0034] In the second notification method, a PKTERR+MC format for IPG+packet, used in the current scheme, is redefined, and a notification about the occurrence of a packet error is sent via PKTERR+MC. This second notification method can be used in the downlink.
[0035] The IPG+ package used in the current scheme is referred to as follows: Fig. 4 and Fig. 5 described. Fig. Figure 4 illustrates downlink transmission, where an intermediate packet gap (IPG) is provided before an A packet, represented by header tokens, payload data, and CRC-32 tokens. In other words, a state between the A packet and the A packet becomes an IDLE state. In a case where end of idle (EOI) occurs after the last IDLE in the IPG, the A packet is subsequently transmitted. As shown in Fig. As illustrated in Figure 5, the EOI of the current scheme is defined by a combination of ISS and Idle, which is set for each symbol period.
[0036] Fig. Figure 6 is a view to explain PKTERR+MC, to which the new scheme is applied. Fig. Figure 6 illustrates a downlink transmission, and PKTERR+MC is transmitted in IPG during IDLE. PKTERR+MC comprises a code (PKTERR) indicating a packet error and an MC number (MC) appended to the code. A PKTERR+MC notification can be made using a combination of ISS and Idle, which differs from EOI defined in the current scheme. Fig. Figure 7 is a view illustrating an example of a combination of ISS and Idle that differs from EOI in a case where the new scheme is applied. Fig. 7 differs in the combination of ISS and Idle, which is set for each symbol period, from that in Fig. 5. This makes it possible to differentiate between EOI and PKTERR in IPG.
[0037] As described above, by mixing the PKTERR code (codes other than 0) with the IDLE data transmitted during the A packet, it is possible to send a notification of the MC number added to PKTERR, along with the PKTERR code indicating a packet error. Furthermore, additional information can be added to PKTERR+MC. For example, as described in Fig. Figure 8 illustrates that additional information is added which is BAD or DROP, that is, a damage / loss flag indicating that the error packet is a damaged or lost packet.
[0038] As described above, the second notification method defines PKTERR+MC, and PKTERR+MC can be used to notify the A packet of the error. This second notification method can be used in the downlink, and, for example, transmission unit 102 of the source can transmit PKTERR+MC to transmission unit 202 of the sink to notify the A packet of the error. The second notification method uses code, thus reducing the data length compared to using the first notification method, and PKTERR+MC can be transmitted in a shorter time. <Drittes Benachrichtigungsverfahren>
[0039] The third notification method defines a new format for CM+CN by redefining a packet error indicator (PER) in control nibbles (CN) for CM+CN, which is used in the current scheme. This enables notification of a packet error occurring via CM+CN+MC. The third notification method can be used in the uplink.
[0040] Fig. Figure 9 is a view that illustrates an example of control nibbles (CN) to which the new schema is applied. Fig. In section 9, Null, Packet Start (PS), Packet End (PE), Ret.Req.Start (RRS), Req.End (RE), Gap Req.Start (GRS), Re-Train Req. (RTR), sCMax Req. (CMR), Interrupt (INT) / Packet Continue (PC), and Ack Indication (ACK) are CNs defined by the current scheme. Fig. 9 is a packet error indicator (PER) CN, redefined by the new scheme, indicating a packet error. The code (code) for PER can be 0111, which is unused in the current scheme. A new format of CM+CN can be used as a result. Note that CN includes CN1 and CN2.
[0041] In the upstream path of the current scheme, each request or packet is transmitted by sending CM+CN, that is, Control Nibbles (CM) and Control Nibbles (CN), sequentially. In the upstream path of the new scheme, it is possible to transmit CM+CN+MC by adding an MC number to CM+CN, using PER for CN, and employing a new format for CM+CN.
[0042] Fig. 10 is a view to explain CM+CN+MC, to which the new scheme is applied. Fig. Figure 10 illustrates an uplink transmission. CN1 = zero (0000) and CN2 = PER (0111) are designated by CN, followed by CM, and a notification of a packet error is sent. Additionally, the MC number is notified by MC, followed by CN. By adopting the format of Fig. 10. It is possible to send a notification of the MC number of the A package in which the error occurred.
[0043] The format of CM+CN+MC is not the same as the format of Fig. limited to 10 and other formats are possible, such as in Fig. 11 illustrates, can be assumed. Fig. 11 are similar to those in Fig. CN1 = null and CN2 = PER, and a notification is sent regarding the occurrence of the packet error. Furthermore, in Fig. 11. A multitude of MC numbers can be designated by MC1 and MC2. For example, a multitude of MC numbers can be designated in a range from MC1 to MC2, that is, a range from the MC number designated by MC1 to the MC number designated by MC2. As a result, in a case where an error has occurred in the A package, a notification of a multitude of MC numbers can be issued. Furthermore, information such as BAD or DROP, indicating a damage / loss flag, and a timestamp, indicating a time stamp, can be added.
[0044] As described above, the third notification method defines CM+CN+MC, and a notification about the occurrence of the error in the A packet can be sent via CM+CN+MC. This third notification method can be used in the uplink, and, for example, the sink's transmission unit 202 can send CM+CN+MC to the source's transmission unit 102 to send a notification about the error in the A packet. The third notification method uses code or similar, and thus the data length can be reduced compared to using the first notification method, allowing CM+CN+MC to be transmitted in a shorter time. <A. Fall, in dem ein Downlink-A-Paket beschädigt ist / verloren geht>
[0045] The operation of the source and sink in a case where a downlink A packet is damaged or lost is described with reference to Fig. 12 to Fig. 14 described. Fig. Figure 12 is a view illustrating a source and sink configuration example that can handle a case where the downlink A packet is corrupted or lost. Fig. 12 is the transmission unit 102 of the transmission device 10 illustrated as a source configuration, and the transmission unit 202 of the transmission device 20 is illustrated as a sink configuration.
[0046] The transmission unit 102 of the source comprises a transmission system 102A and a receiving system 102B. The transmission system 102A comprises a retransmission (RTS) 111, which performs processing related to retransmission, and the like, a scrambler 112, which scrambles a signal, and the like. The receiving system 102B comprises a decoder 113, which decodes a signal, a de-scrambler 114, which de-scrambles a signal, a current controller 115, which controls a current, an RTS 116, which performs processing related to retransmission, and the like.
[0047] The sink's transmission unit 202 comprises a transmission system 202A and a receiving system 202B. Transmission system 202A includes an RTS 211, which performs retransmission processing, a current controller 212, a signal scrambler 213, an encoder 214, a packet generator 217, which generates an error notification packet, and the like. However, if a notification method other than the first one is used, the packet generator 217 is not required. Receiving system 202B includes a signal de-scrambler 215, which de-scrambles a signal, an RTS 216, which performs retransmission processing, and the like.
[0048] It should be noted that the transmission system and the receiving system in transmission unit 102 and transmission unit 202 are separate for the sake of simplicity in description, and that part of the receiving system can operate at the time of transmission if required, or part of the transmission system can operate at the time of reception if required. <<a1. Erstes Benachrichtigungsverfahren: Fehlerbenachrichtigungspaket> >
[0049] Fig. Figure 13 is a view that shows the flow of a signal during a notification of an error occurring using an error notification packet in a case where a downlink A packet is used in the source and sink configuration. Fig. 12 is damaged or lost. In Fig. In section 13, the flow of the signal is represented by a patterned arrow.
[0050] In Fig. In transmission unit 102 of the source, each unit of transmission system 102A performs processing to transmit A packets in the order of the MC number in a transmission table T1 (S11). In transmission unit 202 of the sink, each unit of receiving system 202B performs processing to receive the A packets transmitted by transmission unit 102 (S12). In this case, a case is assumed in which the received A packet is damaged. In transmission unit 202, receiving system 202B detects damage or loss of the received A packet and transmits the damaged packet to processing unit 201, which performs processing with respect to the upper layer. Additionally, receiving system 202B notifies packet generation unit 217 of transmission system 202A of the MC number of the damaged A packet (S13).
[0051] Packet generation unit 217 generates an error notification packet to which the notified MC number is added (S13). In transmission system 202A, each unit performs processing to transmit the error notification packet generated by packet generation unit 217 (S14). In transmission unit 102, each unit of receiving system 102B performs processing to receive the error notification packet transmitted by transmission unit 202 (S15). Receiving system 102B extracts the MC number of the damaged A packet from the received error notification packet and notifies transmission system 102A of the MC number (S16).The transmission system 102A retrieves a protocol type for the destination MC number, for which the notification was made, from the transmission table T1, which is also held after a total delay, and notifies the processing unit 101, which performs processing with respect to the upper layer of the protocol type (S17). It is defined here that after the packet is held for a certain period, the packet is no longer held due to the total delay until the packet is transmitted by the counterpart (there is no possibility of it being transmitted). <<a2. Drittes Benachrichtigungsverfahren: CM+CN+MC> >
[0052] Fig. Figure 14 is a view showing the flow of a signal during a notification of an error occurring using CM+CN+MC in a case where a downlink A packet is present in the source and sink configuration. Fig. 12 is damaged or lost. Also in Fig. In Figure 14, the flow of the signal is represented by a patterned arrow.
[0053] In Fig. In transmission unit 102 of the source, each unit of transmission system 102A performs processing to transmit A packets in the order of the MC number in the transmission table T1 (S21). In transmission unit 202 of the sink, each unit of receiving system 202B performs processing to receive the A packets transmitted by transmission unit 102 (S22). In this case, a case is assumed in which the received A packet is damaged. In transmission unit 202, receiving system 202B detects damage or loss of the received A packet and transmits the damaged packet to processing unit 201, which performs processing with respect to the upper layer. Additionally, receiving system 202B notifies transmission system 202A of the MC number of the damaged A packet (S23).
[0054] Transmission system 202A generates CM+CN+MC, in which the notified MC number is added to CM+CN, where CN1 = zero and CN2 = PER (S23). Transmission system 202A transmits the generated CM+CN+MC (S24). In transmission unit 102, each unit of receiving system 102B performs processing to receive the CM+CN+MC transmitted by transmission unit 202 (S25). Here, the third notification procedure that can be used in the uplink is applied, and the sinking transmission unit 202 transmits CM+CN+MC to the source transmission unit 102 to notify the source of the error in the A packet. Receiving system 102B extracts the MC number of the corrupted A packet from the received CM+CN+MC and notifies transmission system 102A of the extracted MC number (S26).The transmission system 102A retrieves a protocol type of the MC number for which the notification was made from the transmission table T1, which is held after the total delay, and notifies the processing unit 101, which performs processing with respect to the upper layer of the protocol type (S27). <B. Fall, in dem ein Uplink-A-Paket beschädigt / verloren gegangen ist>
[0055] The operation of the source and sink in a case where an uplink-A packet is damaged or lost is described with reference to Fig. 15 to Fig. 17 described. Fig. Figure 15 is a view illustrating a source and sink configuration example that can handle a case where the uplink A packet is corrupted or lost. Fig. 15 is similar to in Fig. 12 the transmission unit 102 of the transmission device 10 is illustrated as the configuration of the source, and the transmission unit 202 of the transmission device 20 is illustrated as the configuration of the sink.
[0056] In Fig. 15 the transmission unit 102 has a configuration in which, compared to the one in Fig. In the configuration illustrated in section 12, a packet generation unit 117, which generates an error notification packet, is added to the transmission system 102A. The transmission unit 202 has a configuration in which, compared to the one in Fig. In the configuration shown in Figure 12, the packet generation unit 217, which is provided in the transmission system 202A, has been removed. Other components are the same as those shown in Figure 12. Fig. 12 are illustrated, and therefore their descriptions are omitted. <<b1. Erstes Benachrichtigungsverfahren: Fehlerbenachrichtigungspaket> >
[0057] Fig. Figure 16 is a view showing the flow of a signal during a notification of an error occurring using the error notification packet in a case where the Uplink-A packet is configured in the source and sink configuration. Fig. 15 is damaged or lost. In Fig. In Figure 16, the flow of the signal is represented by a patterned arrow.
[0058] In Fig. In the sink transmission unit 202, each unit of transmission system 202A performs processing to transmit A packets in the order of the MC number of the transmission table T2 (S31). In the source transmission unit 102, each unit of receiving system 102B performs processing to receive the A packets transmitted by transmission unit 202 (S32). In this case, a scenario is assumed in which the received A packet is damaged. In transmission unit 102, receiving system 102B detects the damage or loss of the received A packet and forwards the damaged packet to processing unit 101, which performs processing with respect to the upper layer. Additionally, receiving system 102B notifies packet generation unit 117 of transmission system 102A of the MC number of the damaged A packet (S33).
[0059] Packet generation unit 117 generates an error notification packet to which the notified MC number is added (S33). In transmission system 102A, each unit performs processing to transmit the error notification packet generated by packet generation unit 117 (S34). In transmission unit 202, each unit of receiving system 202B performs processing to receive the error notification packet transmitted by transmission unit 102 (S35). Receiving system 202B extracts the MC number of the corrupted A packet from the received error notification packet and notifies transmission system 202A of the MC number (S36).The transmission system 202A retrieves a protocol type of the MC number for which the notification was made from the transmission table T2, which is held after the total delay, and notifies the processing unit 201, which performs processing with respect to the upper layer of the protocol type (S37). <<b2. Zweites Benachrichtigungsverfahren: PKTERR+MC> >
[0060] Fig. Figure 17 is a view showing the flow of a signal during a notification of an error occurring using PKTERR+MC in a case where an uplink A packet is present in the source and sink configuration. Fig. 15 is damaged or lost. Also in Fig. In Figure 17, the flow of the signal is represented by a patterned arrow.
[0061] In Fig. 17. In the sink transmission unit 202, each unit of transmission system 202A performs processing to transmit A packets in the order of the MC number of the transmission table T2 (S41). In the source transmission unit 102, each unit of receiving system 102B performs processing to receive the A packets transmitted by transmission unit 202 (S42). In this case, a scenario is assumed in which the received A packet is damaged. In transmission unit 102, receiving system 102B detects the damage or loss of the received A packet and transmits the damaged packet to processing unit 101, which performs processing with respect to the upper layer. Additionally, receiving system 102B notifies transmission system 102A of the MC number of the damaged A packet (S43).
[0062] Transmission system 102A generates PKTERR+MC, which is obtained by adding the notified MC number to the code, which is PKTERR (S43). Transmission system 102A transmits the generated PKTERR+MC (S44). In transmission unit 202, each unit of receiving system 202B performs processing to receive PKTERR+MC transmitted by transmission unit 102 (S45). Here, the second notification procedure that can be used in the downlink is applied, and the source transmission unit 102 transmits PKTERR+MC to the sink transmission unit 202 to notify the A packet of the error. Receiving system 202B extracts the MC number of the corrupted A packet from the received PKTERR+MC and notifies transmission system 202A of the MC number (S46).The transmission system 202A retrieves a protocol type of the destination MC number for which the notification was made from the transmission table T2, which is held after the total delay, and notifies the processing unit 201, which performs processing with respect to the upper layer of the protocol type (S47). <verarbeitungsfluss><<a. Detektion von Beschädigung / Verlust auf der Quellenseite> >
[0063] Referring to the flowcharts of Fig. 18 and Fig. Section 19 describes a series of flows until the receiving side is notified in a case where damage to or loss of a received packet is detected on the source side. In the description of Fig. 18 and Fig. 19 describes a case as an example in which (the transmission unit 102 of) the transmission device 10 serves as the source and (the transmission unit 202 of) the transmission device 20 serves as the sink.
[0064] In the flowchart of Fig. 18. The receiving system 102B of the source's transmission unit 102 performs processing from steps S111 to S123 (excluding processing of S122). In other words, the receiving system 102B receives the A packet transmitted by the transmission unit 202 (S111) and determines whether the CRC8 header of the received A packet and the CRC32 data are good (have no errors) (S112, S113). If CRC8 is determined to be bad (S112: No), the corresponding packet is discarded (S114). Furthermore, if CRC8 and CRC32 are determined to be good (S112: Yes, S113: Yes), the MC number is good. On the other hand, in a case where CRC8 is determined to be good, but CRC32 is not (S112: Yes, S113: No), the MC number is bad. In the receiving system 102B, the information regarding the MC number is written to an RTS buffer along with the data of the received A packet (S115).
[0065] The receiving system 102B then reads the data written to the RTS buffer in MC number order (S116) and determines whether the data is in MC number order (S117). If the data is found to be in MC number order (S117: Yes), it determines whether the BAD flag is present (S118). If the BAD flag is not present (S118: No), the A packet, which was received normally, is forwarded to the upper layer (S123). Conversely, if the BAD flag is present (S118: Yes), it determines whether the total delay has been exceeded (S120). If the total delay has been exceeded (S120: Yes), the A packet is corrupted, and processing is performed (S122) to which the new scheme is applied.Details of the processing (S122) to which the new scheme is applied will be given later with reference to the flowchart of . Fig. 19 described.
[0066] In a case where it is determined that the data is not in the order of the MC numbers (S117: No), it is determined whether the total delay has been exceeded (S119). In a case where it is determined that the total delay has been exceeded (S119: Yes), it is determined whether the BAD flag is present (S121). In a case where it is determined that the BAD flag is present (S121: Yes), the A packet is lost or corrupted, and thus a processing operation (S122) is performed to which the new schema is applied. Additionally, in a case where it is determined that the BAD flag is not present (S121: No), the A packet is lost, and thus a processing operation (S122) is performed to which the new schema is applied. Details of the processing operation (S122) to which the new schema is applied will be explained later with reference to the flowchart of Fig. 19 described.
[0067] In a case where it is determined that the total delay has not been exceeded (S119: No, S120: No), the processing returns to step S116, the data written to the RTS buffer is read again in the order of the MC number, and the processing described above is repeated.
[0068] Here, the processing to which the new scheme is applied and step S122 is shown. Fig. 18 corresponds, in detail with reference to a flowchart of Fig. 19 described. In the flowchart of Fig. 19. The processing in steps S141 to S144 is carried out by the transmission system 102A of the transmission unit 102 of the source, and the processing of steps S151 to S156 is carried out by a part of the receiving system 202B and the transmission system 202A of the transmission unit 202 of the sink.
[0069] In other words, damage to or loss of the A-package resulting from the processing described above, which is in Fig. When signal 18 is displayed, received, detected, and thus the transmission system 102A in the transmission unit 102 generates the error notification data to perform a notification of a reception error of the A packet using the MC number of the damaged or lost A packet (S141). The downlink is present here, and thus an error notification packet can be generated using the first notification method, or PKTERR+MC can be generated using the second notification method. The transmission system 102A scrambles the generated error notification data (S142), converts the scrambled signal from a parallel signal to a serial signal (S143), and transmits the converted signal (S144).
[0070] In the transmission unit 202, the receiving system 202B receives the signal transmitted by the transmission unit 102 via serial communication (S151) and converts the received signal from serial to parallel (S152). Furthermore, the receiving system 202B decodes the converted signal (S153) and analyzes the resulting received signal (S154). In cases where the first notification method is used, the MC number of the damaged or lost A packet is extracted from the error notification packet. In cases where the second notification method is used, the MC number of the damaged or lost A packet is extracted from PKTERR+MC.Then, the transmission system 202A checks consistency between the MC number of the error packet captured from the error notification data and the MC number of the transmission packet buffer by referring to the transmission table T2, captures a packet type (protocol type) of the destination MC number (S155) and notifies the upper layer of the packet type (S156).
[0071] Furthermore, in this case, the sink's transmission unit 202 can recover the adaptation type contained in the adaptation descriptor of the error packet header from the error packet's MC number, which is captured from the error notification data transmitted by the source's transmission unit 102. As a result, the sink's transmission unit 202 can notify the upper layer for each adaptation type. Fig. 20 and Fig. Figure 21 illustrates the adaptation type defined in the MIPI standard. <<b. Detektion von Beschädigung / Verlust auf der Senkenseite> >
[0072] Next, with reference to the flowcharts of Fig. 22 and Fig. 23 describes a series of flows until the source side is notified, in a case where damage to or loss of a received packet is detected on the destination side. In the description of Fig. 22 and Fig. 23 will be done in a similar way to in Fig. 18 and Fig. 19 a case is described as an example in which (the transmission unit 102 of) the transmission device 10 serves as the source and (the transmission unit 202 of) the transmission device 20 serves as the sink.
[0073] In the flowchart of Fig. 22, the processing of steps S211 to S223 (where processing of S222 is excluded) is similar to the processing in steps S111 to S123 of Fig. 18 (where the processing of S122 is excluded), differs, however, in that the object of processing is not the receiving system 102B of the transmission unit 102 of the source, but the receiving system 202B of the transmission unit 202 of the sink. The processing in step S222 in Fig. 22 is a processing step to which the new scheme is applied, and details of the processing are given with reference to the flowchart in Fig. 23 described. In the flowchart of Fig. 23 The processing of steps S241 to S244 is carried out by the transmission system 202A of the transmission unit 202 of the sink, and the processing in steps S251 to S256 is carried out by a part of the receiving system 102B and the transmission system 102A of the transmission unit 102 of the source.
[0074] In other words, damage to or loss of the A-package resulting from the processing described above, which is in Fig. When signal 22 is displayed, received, detected, and thus the transmission system 202A in the transmission unit 202 generates the error notification data to perform a notification of a reception error of the A packet using the MC number of the damaged or lost A packet (S241). The uplink is present here, and thus an error notification packet can be generated using the first notification method, or CM+CN+MC can be generated using the third notification method. The transmission system 202A scrambles the generated error notification data (S242), converts the scrambled signal from a parallel signal to a serial signal (S243), and transmits the converted signal (S244).
[0075] In the transmission unit 102, the receiving system 102B receives the signal transmitted by the transmission unit 202 via serial communication (S251) and converts the received signal from serial to parallel (S252). Furthermore, the receiving system 102B decodes the converted signal (S253) and analyzes the resulting received signal (S254). In a case where the first notification method is used, the MC number of the damaged or lost A packet is extracted from the error notification packet. In a case where the third notification method is used, the MC number of the damaged or lost A packet is extracted from CM+CN+MC.Then, the transmission system 102A checks the consistency between the MC number of the error packet captured from the error notification data and the MC number of the transmission packet buffer by referring to the transmission table T1, captures a packet type (protocol type) of the destination MC number (S255) and notifies the upper layer of the packet type (S256). <Wirkungen des neuen Schemas>
[0076] The effects obtained by adopting the new scheme are described. This is done with reference to... Fig. 24 and Fig. 25 describes a case in which the time until the upper layer is notified can be reduced if the A packet is damaged or lost, in a case where the new scheme is adopted, compared with a case where the current scheme is adopted. <<a. Fall des aktuellen Schemas> >
[0077] Fig. Figure 24 is a sequence diagram showing signals to be exchanged between the source and sink sides in a case where the current scheme is used. Fig. In the figure, the left part (24) is the source side, the right part (24) is the sink side, and a time direction is a direction from the top to the bottom side of the figure. In a case where the source side corresponds to the transmission device 10, the system (CPU) and PAL correspond to the processing unit 101, and the source connection corresponds to the transmission unit 102. In a case where the sink side corresponds to the transmission device 20, the system (CPU) and PAL correspond to the processing unit 201, and the sink connection corresponds to the transmission unit 202.
[0078] In Fig. In section 24, the system on the receiving end delivers data in various schemes, such as GPIO, I2C, and SPI, to PAL. PAL generates A packets from this data in different schemes (protocol types). The receiving end transmits the A packets from PAL sequentially. In this case, MC numbers are added to the A packets. Additionally, the MC numbers and protocol types can be managed in association with each other using table T.
[0079] On the source side, the A packets transmitted from the sink side are received sequentially and forwarded from the source connection to PAL. Here, we consider a case where noise occurs in a transmission path during serial communication. In this case, normally one A packet (MC = 0) and one A packet (MC = 1) are transmitted from the sink side to the source side, but one A packet (MC = 2) and one A packet (MC = 3) are corrupted or lost due to the noise. Consequently, a CRC32 error is detected from the A packets of MC = 2 and 3, and a retransmission request is issued. The sink side retransmits the A packets (MC = 3) and (MC = 2) from the source side in response to the retransmission request.
[0080] Upon receiving the retransmitted A packet (MC = 3), the source side does not receive the A packet (MC = 2), and the maximum delay period (MC = 2 Max RTS Delay) of the A packet (MC = 2) is exceeded. Therefore, the source side notifies PAL that the A packet (MC = 2) is corrupted (BAD) and submits a break request during processing by the system. The system notifies PAL of an error flag in response to the break request, and the source connection notifies the sink side of the break (GPIO packet) from PAL. Then, on the sink side, a break (GPIO packet) notified by the source side is transmitted from the sink connection to PAL, allowing the system to detect the error in the A packet.
[0081] As described above, in a case where the current scheme is used, packet corruption or loss is determined at the upper layer, and a notification is sent via GPIO or similar means. This process takes considerable time from the source to the sink. Additionally, if an A packet is lost, the source cannot determine the specific type of lost A packet. In the case of I2C, in particular, there is a timeout on the order of 100 ms before the A packet loss is detected. Furthermore, the source cannot identify which of the transmitted A packets is corrupted.The source page can confirm that the A packet is corrupted or lost by reading DIAG_CNT, but querying a register in ESS_CCI is required, and the type of the corrupted packet cannot be determined. <<b. Fall des neuen Schemas> >
[0082] Fig. Figure 25 is a sequence diagram showing signals to be exchanged between the source and sink sides in a case where the new scheme is used. Fig. 25 will be done in a similar way to how in Fig. 24 In a case where the left part of the figure is the source side and the right part is the sink side, the A packets transmitted from the sink side are received sequentially at the source side. However, noise occurs in the transmission path, a CRC32 error is detected from the A packets of MC = 2 and 3, and a retransmission request is made. The sink side retransmits the A packet (MC = 3) and the A packet (MC = 2) in response to the retransmission request from the source side. However, a maximum delay period (MC = 2 Max RTS Delay) is exceeded at the source side before the retransmitted A packet (MC = 2) is received. Consequently, the source side notifies PAL that the A packet (MC = 2) is corrupted (BAD) and makes an interruption request during system processing.
[0083] In this case, the source connection on the source side, in the new schema, notifies the sinking side of the error in the A packet using error notification data to which the MC number is added. This notification procedure, such as the first notification procedure described above, allows the sinking connection to detect that the error occurred in the transmitted A packet on the sinking side. Furthermore, by adding the MC number when notifying the sinking side of the error in the A packet, the sinking connection can recover the type of the damaged or lost A packet from the MC number, referencing table T, and notify the upper layer of the type of damaged or lost A packet. As a result, for example, the system on the sinking side can confirm the severity of the error packet and implement a countermeasure according to its severity.
[0084] As described above, in a case where the new scheme is used, the source's transmission unit 202 can directly notify the counterpart's transmission unit 102 about the occurrence of the error in packet A, thus reducing the processing time until the source side is notified. Additionally, the source's transmission unit 102 provides notification of the MC number of the packet A containing the error, allowing the counterpart's transmission unit 202 to identify the packet type (protocol type) from the stored table T. As a result, the system (CPU) can detect the occurrence of an error at an early stage.
[0085] More precisely, as specified in a frame A1, which is defined by a one-point catenary in Fig. As specified in 24, if the A packet (MC = 2) cannot be received, even if the maximum delay period (MC = 2 Max RTS Delay) is exceeded, the source connection notifies the upper layer that an error has occurred in the packet. The upper layer then notifies the sinking layer according to an instruction. Thus, a period T1 is required from time t1, after the maximum delay period has elapsed on the source side, until time t2, at which the system detects the packet error on the sinking side.
[0086] On the other hand, as indicated in a frame A2, which is defined by a one-point catenary in Fig. As specified in paragraph 25, if the source connection cannot receive the A packet (MC = 2), even if the maximum delay period (MC = 2 Max RTS Delay) on the source side is exceeded, the sink connection, which is the counterpart, can directly notify that an error has occurred in the packet, using a notification procedure such as the first notification procedure described above. Thus, a period T2 is required from time t1, after the maximum delay period on the source side has elapsed, until time t3, at which the system detects the packet error on the sink side. Therefore, when comparing the period T1 in a case where the current scheme is used with the period T2 in a case where the new scheme is used, it is clear that the system can detect the occurrence of the error more quickly using the new scheme.
[0087] As described above, in the present disclosure, the transmission system 1, comprising the transmission device 10 and the transmission device 20, which are connected via the A-PHY-I / F defined in the MIPI standard, has the following configuration. In other words, the transmission device 10 includes the transmission unit 102, and in a case where an error is detected in the A packet transmitted by the transmission device 20, the transmission unit 102 generates error notification data to which an MC number of an error packet, which is the A packet in which the error was detected, is added, and transmits the generated error notification data to the transmission device 20.Additionally, the transmission device 20 includes the transmission unit 202, and the transmission unit 202 holds correspondence information in which the type of the transmitted A packet is associated with the MC number of the A packet, and in a case where the error notification data transmitted by the transmission device 10 is received, it retrieves a type of A packet corresponding to the MC number of the error packet added to the received error notification data from the held correspondence information and restores a type of error packet.
[0088] In a case where transmission unit 102 is the source and transmission unit 202 is the sink, the error notification data is transmitted in the downlink. Therefore, either the first or second notification method can be used, and the error notification packet, or PKTERR+MC, is generated as the error notification data. In this case, the corresponding information is, for example, the transmission table T2. Conversely, in a case where transmission unit 102 is the sink and transmission unit 202 is the source, the error notification data is transmitted in the uplink. Therefore, either the first or third notification method can be used, and the error notification packet, or CM+CN+MC, is generated as the error notification data.In this case, the correspondence information is, for example, the transfer table T1.
[0089] In a case where the transmission system 1, to which this disclosure applies, has the above configuration and an error has occurred in the A packet being transmitted, the error packet can be specified by exchanging the error notification data, to which the MC number of the error packet is added, between transmission unit 102 and transmission unit 202, which perform processing with respect to A-PHY, and capturing the MC number of the error packet. In other words, determining whether processing unit 101 or processing unit 201 performs processing with respect to the upper layer is unnecessary, thus making it possible to detect the occurrence of an error at an early stage and to perform the processing.As described above, in the transmission system 1 to which the present disclosure is applied, in a case where an error has occurred in a packet, notification of the packet error can be made more appropriate. <modifikationen>
[0090] The above description outlines three notification procedures as the new scheme, but each of the first, second, and third notification procedures can be performed not only independently but also simultaneously by combining a variety of notification procedures. For example, in the downlink, the first and second notification procedures can be combined to generate and transmit both the error notification packet and PKTERR+MC. In the uplink, the first and third notification procedures can be combined to generate and transmit both the error notification packet and CM+CN+MC.It should be noted that the transfer table T1 and the transfer table T2 can be recorded and retained in a storage device such as random access memory (RAM) contained in the transfer unit 102 and the transfer unit 202. It should also be noted that the damaged / lost flag can indicate at least one damaged or lost packet.
[0091] It should be noted that the embodiment of the present disclosure is not limited to the embodiment described above and various modifications can be made without deviating from the core of the present disclosure. Furthermore, the effects described in this specification are merely examples and are not limiting, and some other effects can be achieved.
[0092] Furthermore, the present disclosure may have the following configurations.
[0093] (1) Transmission system comprising a first transmission device and a second transmission device connected via an A-PHY-I / F defined in a MIPI standard, wherein The first transmission device comprises a first transmission unit, which In a case where an error is detected in an A packet transmitted by the second transmission device, error notification data is generated, to which an MC number of an error packet, which is the A packet in which the error was detected, is added, and transmits the generated error notification data to the second transmission device, the second transmission device includes a second transmission unit that Correspondence information is held in which a type of the transmitted A packet is associated with an MC number of the A packet, and In a case where the fault notification data transmitted by the first transmission device is received, a type of A packet is determined from the held correspondence information according to the MC number of the fault packet added to the received fault notification data, and a type of fault packet is recovered. The first transmission unit and the second transmission unit perform processing with respect to A-PHY.
[0094] (2) transmission system according to (1) in which The error notification data is an error notification package that includes an A package, and The error notification package includes the MC number in a payload.
[0095] (3) transmission system according to (2), in which The payload also includes a flag indicating damage to or loss of the fault packet.
[0096] (4) transmission system according to (2) or (3), wherein The error notification packet is a packet defined by a link service or PHY service defined in the MIPI standard.
[0097] (5) transmission system according to (1) in which The error notification data is a code indicating a packet error, and the MC number is added to the code, and The code includes a combination of Idle and ISS, which differs from EOI.
[0098] (6) transmission system according to (5), in which a flag that indicates damage to or loss of the error packet, which is also added to the code.
[0099] (7) transmission system according to (1), wherein The error notification data includes CM and CN, which are transmitted consecutively, and the MC number, which is added to the CM and CN, which are consecutive. The CN contains a code that indicates an error in the A package.
[0100] (8) transmission system according to (7), in which a flag indicating damage or loss of the error packet is added to the CM and CN, which are consecutive.
[0101] (9) transmission system according to one of (1) to (8), wherein The correspondence information is a table that is kept until a certain period of time has elapsed since the transmission of the A packet.
[0102] (10) Transmission device comprising: a transmission unit that receives an A packet transmitted by another transmission device connected via an A-PHY-I / F defined in a MIPI standard, In a case where an error is detected in the A packet, error notification data is generated, to which an MC number of an error packet, which is the A packet in which the error was detected, is added, and transmits the generated error notification data to the other transmission device, wherein The transmission unit performs processing in relation to A-PHY.
[0103] (11) Transmission device according to (10), wherein The error notification data is an error notification package that includes an A package, and The error notification package includes the MC number in a payload.
[0104] (12) Transmission device according to (10), wherein The error notification data is a code indicating a packet error, and the MC number is added to the code, and The code includes a combination of Idle and ISS, which differs from EOI.
[0105] (13) Transmission device according to (10), wherein The error notification data includes CM and CN, which are transmitted consecutively, and the MC number, which is added to the CM and CN, which are consecutive. The CN contains a code that indicates an error in the A package.
[0106] (14) Transmission method of a transmission device with a transmission unit that performs processing with respect to A-PHY as defined in a MIPI standard, wherein the transmission method comprises: through the transmission unit Receiving an A packet transmitted by another transmission device connected via an A-PHY-I / F; In a case where an error is detected in the A packet, generate error notification data to which an MC number of an error packet, which is the A packet in which the error was detected, is added; and The transmission unit transfers the generated error notification data to the other transmission device.
[0107] (15) Transmission device comprising: a transmission unit that transmits an A packet to another transmission device connected via an A-PHY-I / F defined in a MIPI standard, Correspondence information is held in which a type of the transmitted A packet is associated with an MC number of the A packet, In a case where error notification data transmitted from the other transmission device is received, a type of A packet corresponding to an MC number of an error packet added to the received error notification data is captured from the held correspondence information, and a type of A packet in which an error was detected is restored as the error packet, wherein The transmission unit performs processing in relation to A-PHY.
[0108] (16) Transmission device according to (15), wherein The error notification data is an error notification package that includes an A package, and The error notification package includes the MC number in a payload.
[0109] (17) Transmission device according to (15), wherein The error notification data is a code indicating a packet error, and the MC number is added to the code, and The code includes a combination of Idle and ISS, which differs from EOI.
[0110] (18) Transmission device according to (15), wherein The error notification data includes CM and CN, which are transmitted consecutively, and the MC number, which is added to the CM and CN, which are consecutive. The CN contains a code that indicates an error in the A package.
[0111] (19) Transmission method of a transmission device with a transmission unit that performs processing with respect to A-PHY as defined in a MIPI standard, wherein the transmission method comprises: through the transmission unit Transmitting an A packet to another transmission device connected via an A-PHY-I / F; Holding correspondence information in which a type of the transmitted A packet is associated with an MC number of the A packet; and In a case where error notification data transmitted from the other transmission device is received, capture a type of A packet corresponding to an MC number of an error packet added to the received error notification data from the held correspondence information and Restore a type of A packet in which an error was detected, as the error packet. REFERENCE MARK LIST 1 transmission system 10 Transmission device 20 Transmission device 30 transmission path 101 processing units 102 transmission unit 102A transmission system 102B Receiving System 111 RTS 112 dicers 113 decoders 114 dicers 115 Current control 116 RTS 117 Packet generation unit 201 processing unit 202 transmission unit 202A transmission system 202B Receiving System 211 RTS 212 Current control 213 dicers 214 Coders 215 dicers 216 RTS 217 Packet generation unit QUOTES INCLUDED IN THE DESCRIPTION
[0000] This list of documents cited by the applicant was automatically generated and is included solely for the reader's convenience. The list is not part of the German patent or utility model application. The DPMA accepts no liability for any errors or omissions. Cited non-patent literature
[0000] MIPI Alliance Specification for A-PHY, Version 1.1, MIPI Alliance, Inc., August 9, 2021
[0003] < / modifikationen> < / verarbeitungsfluss> < / systemkonfiguration>
Claims
[1] Transmission system comprising a first transmission device and a second transmission device connected via an A-PHY-I / F defined in a MIPI standard, wherein The first transmission device comprises a first transmission unit, which In a case where an error is detected in an A packet transmitted by the second transmission device, error notification data is generated, to which an MC number of an error packet, which is the A packet in which the error was detected, is added, and transmits the generated error notification data to the second transmission device, The second transmission device comprises a second transmission unit that holds correspondence information in which a type of the transmitted A packet is associated with an MC number of the A packet, and In a case where the fault notification data transmitted by the first transmission device is received, a type of A packet is determined from the held correspondence information according to the MC number of the fault packet added to the received fault notification data, and a type of fault packet is recovered. The first transmission unit and the second transmission unit perform processing with respect to A-PHY. [2] Transmission system according to claim 1, wherein The error notification data is an error notification package that includes an A package, and The error notification package includes the MC number in a payload. [3] Transmission system according to claim 2, wherein the payload further comprises a flag indicating damage to or loss of the error packet. [4] Transmission system according to claim 2, wherein the error notification packet is a packet defined by a link service or PHY service defined in the MIPI standard. [5] Transmission system according to claim 1, wherein The error notification data is a code indicating a packet error, and the MC number is added to the code, and The code includes a combination of Idle and ISS, which differs from EOI. [6] Transmission system according to claim 5, wherein a flag indicating damage to or loss of the error packet is further added to the code. [7] Transmission system according to claim 1, wherein The error notification data includes CM and CN, which are transmitted consecutively, and the MC number, which is added to the CM and CN, which are consecutive. The CN contains a code that indicates an error in the A package. [8] Transmission system according to claim 7, wherein a flag indicating damage or loss of the error packet is further added to the CM and the CN, which are consecutive. [9] Transmission system according to claim 1, wherein the correspondence information is a table which is retained until a certain period of time has elapsed since the transmission of the A packet. [10] Transmission device with: a transmission unit that receives an A packet transmitted by another transmission device connected via an A-PHY-I / F defined in a MIPI standard, In a case where an error is detected in the A packet, error notification data is generated, to which an MC number of an error packet, which is the A packet in which the error was detected, is added, and transmits the generated error notification data to the other transmission device, wherein The transmission unit performs processing in relation to A-PHY. [11] Transmission device according to claim 10, wherein The error notification data is an error notification package that includes an A package, and The error notification package includes the MC number in a payload. [12] Transmission device according to claim 10, wherein The error notification data is a code indicating a packet error, and the MC number is added to the code, and The code includes a combination of Idle and ISS, which differs from EOI. [13] Transmission device according to claim 10, wherein The error notification data includes CM and CN, which are transmitted consecutively, and the MC number, which is added to the CM and CN, which are consecutive. The CN contains a code that indicates an error in the A package. [14] Transmission method of a transmission device with a transmission unit that performs processing with respect to A-PHY as defined in a MIPI standard, wherein the transmission method comprises: through the transmission unit, Receiving an A packet transmitted by another transmission device connected via an A-PHY-I / F; In a case where an error is detected in the A packet, generate error notification data to which an MC number of an error packet, which is the A packet in which the error was detected, is added; and Transferring the generated error notification data to the other transmission device. [15] Transmission device with: a transmission unit that transmits an A packet to another transmission device connected via an A-PHY-I / F defined in a MIPI standard, Correspondence information is held in which a type of the transmitted A packet is associated with an MC number of the A packet, In a case where error notification data transmitted from the other transmission device is received, a type of A packet corresponding to an MC number of an error packet added to the received error notification data is captured from the held correspondence information, and a type of A packet in which an error was detected is restored as the error packet, wherein The transmission unit performs processing in relation to A-PHY. [16] Transmission device according to claim 15, wherein The error notification data is an error notification package that includes an A package, and The error notification package includes the MC number in a payload. [17] Transmission device according to claim 15, wherein The error notification data is a code indicating a packet error, and the MC number is added to the code, and The code includes a combination of Idle and ISS, which differs from EOI. [18] Transmission device according to claim 15, wherein The error notification data includes CM and CN, which are transmitted consecutively, and the MC number, which is added to the CM and CN, which are consecutive. The CN contains a code that indicates an error in the A package. [19] Transmission method of a transmission device with a transmission unit that performs processing with respect to A-PHY as defined in a MIPI standard, wherein the transmission method comprises: through the transmission unit, Transmitting an A packet to another transmission device connected via an A-PHY-I / F; Holding correspondence information in which a type of the transmitted A packet is associated with an MC number of the A packet; and In a case where error notification data transmitted from the other transmission device is received, capture a type of A packet corresponding to an MC number of an error packet added to the received error notification data from the held correspondence information and restore a type of A packet in which an error was detected as the error packet.