Method and device for serial data transmission which is adapted to memory sizes
28 claims: 13 independent, 15 dependent
- 1バスを介してメッセージを受信又は送信する少なくとも2つの関与するデータ処理ユニットを備えたバスシステム内での直列データ伝送のための方法であって、 前記送信されるメッセージは、CAN規格ISO11898-1に準拠した論理構造を有し、 前記論理構造は、スタートオブフレームビット、アービトレーションフィールド、コントロールフィールド、データフィールド、CRCフィールド、アクノリッジフィールド、エンドオブフレームシーケンスを含み、 前記コントロールフィールドは、前記データフィールドの長さについての情報を含むデータ長コードを含む、前記方法において、 第1の切り替え条件が存在する際には、前記メッセージの前記データフィールドは、CAN規格ISO11898-1から外れて8バイトを超えることが可能であり、 前記第1の切り替え条件が存在する際に前記データフィールドの大きさを確認するために、前記データ長コードの値が、少なくとも部分的にCAN規格ISO11898-1から外れて解釈され、 前記データフィールドとアプリケーションソフトウェア(640)との間のデータ転送のために、少なくとも1つの一時メモリ(620)が設けられ、前記転送されるデータ量は少なくとも、前記データフィールドの大きさが、利用される前記一時メモリ(620)の大きさと異なる場合には、データフィールドと利用される一時メモリ(620)の大きさの違いに対応して調整されることを特徴とする、方法。
- 2前記データフィールドの大きさが、前記利用される一時メモリの大きさを上回る場合には、前記バスを介して受信されたメッセージの前記データフィールドから、前記一時メモリの大きさに対応するデータ量が、予め設定され又は予め設定可能な選択方法に従って選択されて、前記一時メモリへと転送されることを特徴とする、請求項1に記載の方法。
- 3前記データフィールドの大きさが、前記利用される一時メモリの大きさを上回る場合には、前記バスを介して送信されるメッセージの前記データフィールドには、前記一時メモリの内容が、前記メッセージの前記データフィールドの少なくとも1つの予め設定され又は予め設定可能な範囲内に記録され、前記データフィールドの残りの前記範囲は、予め設定され又は予め設定可能な方法に従って充填されることを特徴とする、請求項1又は2に記載の方法。
- 4前記バスを介して受信されたメッセージの前記データフィールドの大きさが8バイトよりも大きい際には、前記少なくとも1つの一時メモリを介して、前記データフィールドの予め設定され又は予め設定可能な8バイトが、前記アプリケーションソフトウェアへと渡されることを特徴とする、請求項1~3のいずれか1項に記載の方法。
- 5前記バスを介して送信されるメッセージの前記データフィールドの大きさが8バイトよりも大きい際には、前記データフィールドの前記残りの範囲のビットが、予め設定され又は予め設定可能な値で充填されることを特徴とする、請求項 3に 記載の方法。
- 6前記バスを介して送信されるメッセージの前記データフィールドの前記充填される範囲内の前記ビットは、CAN規格ISO11898-1の規定に従って当該範囲にスタッフビットを挿入する必要がないように、充填されることを特徴とする、請求項 5に 記載の方法。
- 7前記第1の切り替え条件の値に従って、前記データ長コードの4ビットの、各可能な値の組み合わせが、前記データフィールドの許容される大きさの1つに割り当てられることを特徴とする、請求項1~6のいずれか1項に記載の方法。
- 8前記メッセージのデータフィールドがCAN規格ISO11898-1から外れて8バイトを超えることが可能なメッセージであって、前記データフィールドの前記大きさの確認のために、前記データ長コードの前記値が少なくとも部分的にCAN規格ISO11898-1から外れて解釈される前記メッセージは、CAN規格に準拠したメッセージの前記アービトレーションフィールド内、及び/又は、前記コントロールフィールド内の第1の標識によって区別されうることを特徴とする、請求項1~7のいずれか1項に記載の方法。
- 9前記第1の標識は、前記関与するデータ処理ユニット内で、前記第1の切り替え条件を定めるために評価され、従って、前記第1の切り替え条件に従って、前記受信のプロセスが前記データフィールドの大きさに対して調整されることを特徴とする、請求項8に記載の方法。
- 10前記第1の標識は、識別子の最終ビットと前記データ長コードの第1ビットとの間にその位置が存在する第1の標識ビット(EDL)であって、メッセージ内でCAN規格ISO11898-1に従って、固定値を有するビットがその位置に存在する前記第1の標識ビット(EDL)によって与えられることを特徴とする、請求項8~9のいずれか1項に記載の方法。
- 11切り替え条件の値に従って、前記メッセージの前記CRCフィールドは、少なくとも2つの異なるビット数を有することが可能であり、前記CRCフィールド内の有効な前記ビット数の少なくとも1つは、CAN規格ISO11898-1から外れたビット数であり、前記外れたビット数を有するこのようなCRCフィールドの内容を設定するために、CAN規格ISO11898-1から外れた生成多項式が利用されることを特徴とする、請求項1~10のいずれか1項に記載の方法。
- 12更なる別の切り替え条件の値に従って、メッセージ内の時間的ビット長は、少なくとも2つの異なる値を取ることが可能であり、前記メッセージ内の少なくとも1つの第1の予め設定可能な範囲について、前記時間的ビット長は、約1マイクロ秒の予め設定された最小値よりも大きく又は当該最小値と等しく、前記メッセージ内の少なくとも1つの第2の設定可能な範囲内では、前記時間的ビット長は、前記第1の予め設定可能な範囲と比べて低減された値を有することを特徴とする、請求項1~11のいずれか1項に記載の方法。
- 13メッセージ内の前記時間的ビット長の前記少なくとも2つの異なる値は、最小時間単位又は駆動中の発振器クロックに対して相対的なバス時間単位を調整するための、少なくとも2つの異なる倍率を利用することによって実現されることを特徴とする、請求項12に記載の方法。
- 14更なる別の切り替え条件の値に従って 、 メッセージ内 の時 間的ビット長が少なくとも2つの異なる値を取り得る前記メッセージは、前記アービトレーションフィールド内及び/又は前記コントロールフィールド内の更なる別の標識によって検出可能であり、前記更なる別の標識は、前記第1の標識と一致しうることを特徴とする、請求項 10に 記載の方法。
- 15前記更なる別の切り替え条件の前記値は、前記関与するデータ処理ユニット内で更なる別の標識に従って定められ、又は、前記第1の切り替え条件と一致し、又は、前記第1の切り替え条件から導出され、前記更なる別の切り替え条件の前記値に従って、前記受信のプロセスが、メッセージ内の前記時間的ビット長の様々な前記値に対して調整されることを特徴とする、請求項14に記載の方法。
- 16前記更なる別の標識は、前記第1の標識ビットと前記 データ長コード の第1のビットとの間に存在する更なる別の標識ビット(BRS)によって与えられることを特徴とする、請求項 14又は15に 記載の方法。
- 17少なくとも1つの追加的な状態ビットが設けられ、前記少なくとも1つの追加的な状態ビットによって、前記アプリケーションソフトウェアのために、CAN規格ISO11898-1から外れたデータ処理方法に関する情報が提供されることを特徴とする、請求項1~16のいずれか1項に記載の方法。
- 18前記少なくとも1つの追加的な状態ビットは、送信成功を知らせるための状態ビット、及び/又は、受信成功を知らせるための状態ビット、及び/又は、直近に発生したエラーの形態を知らせるための1つ以上の状態ビットを含むことを特徴とする、請求項17に記載の方法。
- 19CAN規格ISO11898-1から外れるデータ伝送方法でのエラーの発生頻度に従って、CAN規格ISO11898-1に準拠した伝送方法へと戻して切り替えられ、戻し切り替えの成功を知らせるための少なくとも1つの状態ビットが設けられることを特徴とする、請求項17又は18に記載の方法。
- 20前記少なくとも1つの一時メモリ内、及び/又は、少なくとも1つの割り当てられたメッセージメモリ内に、各前記メッセージのために利用された又は利用されるデータ伝送方法を標識付けする少なくとも1つの追加的なメッセージビットが設けられることを特徴とする、請求項1~19のいずれか1項に記載の方法。
- 21前記少なくとも1つの一時メモリ内、及び/又は、少なくとも1つの割り当てられたメッセージメモリ内に、各前記メッセージのために利用された又は利用されるデータ伝送方法を標識付けする少なくとも1つの追加的なメッセージビットが設けられ、 前記少なくとも1つの追加的なメッセージビットは、前記第1の標識又は前記更なる別の標識の前記値の少なくとも1つに対応し、又は、前記第1の標識又は前記更なる別の標識の前記値から導出され、又は、前記コントロールフィールドのビットr1又はr0のうちの少なくとも1つ、又は、前記アービトレーションフィールドのSRRに対応することを特徴とする、請求項 14~16のいずれか1項 に記載の方法。
- 22バスを介してメッセージを受信又は送信する少なくとも2つの関与するデータ処理ユニットを備えたバスシステム内での直列データ伝送のための装置であって、 前記送信されるメッセージは、CAN規格ISO11898-1に準拠した論理構造を有し、 前記論理構造は、スタートオブフレームビット、アービトレーションフィールド、コントロールフィールド、データフィールド、CRCフィールド、アクノリッジフィールド、エンドオブフレームシーケンスを含み、 前記コントロールフィールドは、前記データフィールドの長さについての情報を含むデータ長コードを含む、前記装置において、 第1の切り替え条件が存在する際には、前記メッセージの前記データフィールドは、CAN規格ISO11898-1から外れて8バイトを超えることが可能であり、 前記第1の切り替え条件が存在する際に前記データフィールドの大きさを確認するために、前記データ長コードの値は、少なくとも部分的にCAN規格ISO11898-1から外れて解釈され、 前記データフィールドとアプリケーションソフトウェアとの間のデータ転送のために、少なくとも1つの一時メモリが設けられ、前記転送されるデータ量は少なくとも、前記データフィールドの大きさが、利用される前記一時メモリの大きさと異なる場合には、データフィールドと利用される一時メモリの大きさの違いに対応して調整されることを特徴とする、装置。
- 23前記装置は、適切な手段によって、請求項2~21に記載のデータ伝送方法のうちの少なくとも1つの実施するよう構成されることを特徴とする、請求項22に記載の装置。
- 24前記適切な手段は、前記データフィールドと前記一時メモリとの間を転送されるデータ量を、データフィールドと一時メモリの大きさの違いに対応して調整するための少なくとも1つのプロトコル制御部を含むことを特徴とする、請求項23に記載の装置。
- 25前記適切な手段は、少なくとも1つの追加的な又は拡張された状態レジスタを備え、前記状態レジスタの内容は、各前記利用されるデータ伝送方法の形態及び/又は成功及び/又は結果を標識付けすることを特徴とする、請求項23又は24のいずれか1項に記載の装置。
- 26前記適切な手段は、少なくとも1つの追加的な又は拡張されたメッセージメモリ及び/又は一時メモリを備え、前記少なくとも1つの追加的な又は拡張されたメッセージメモリ及び/又は一時メモリ内では、追加的なメッセージビットが、各前記メッセージのために利用された又は利用されるデータ伝送方法を標識付けすることを特徴とする、請求項23~25のいずれか1項に記載の装置。
- 27車両又は産業施設の通常駆動において、適切なデータバスを介して接続された、前記車両又は前記産業施設の少なくとも2つの制御装置の間でデータを伝送するために利用される、請求項1~21のいずれか1項に記載の方法。
- 28車両又は産業施設の製造又は保守の間に、プログラミングを目的として適切なデータバスと接続されたプログラミングユニットと、前記データバスと接続された前記車両又は前記産業施設の少なくとも1つの制御装置と、の間でデータを伝送するために利用される、請求項1~21のいずれか1項に記載の方法。
Independent claims28
62 paragraphs, as filed
0001The present invention relates to methods and devices for serial data transmission adjusted for memory size between at least two subscribers in a series bus system.
0002For example, in the family standard ISO11898-1 ~ 5, "Controller Area Network" (CAN) and "Time Triggered CAN" (TTCAN: Time Triggered), which are referred to as the standard CAN below. An extended version of CAN called CAN) is described. The medium access control method used in CAN is based on bit-by-bit arbitration. In the case of bit-by-bit arbitration, multiple subscriber stations can simultaneously transmit data over the channels of the bus system, which does not interfere with data transmission. In addition, the subscriber station can determine the logical state (0 or 1) of the channel when transmitting the bit over the channel. If the value of the transmitted bit does not match the defined logical state of the channel, the subscriber station terminates access to the channel. In the case of CAN, bit-by-bit arbitration is usually done using identifiers in messages transmitted over the channel. After the subscriber station has fully transmitted the identifier to the channel, the subscriber station is found to have exclusive access to the channel. Therefore, the end of the transmission of the identifier corresponds to the beginning of the permitted interval in which the subscriber station can exclusively use the channel. According to the CAN protocol specification, other subscriber stations must not access the channel until the transmitting subscriber station has transmitted the check field (CRC field) of the message, i.e. send data to the channel. should not be done. Therefore, the end point of transmission of the CRC field corresponds to the end of the permitted section.
0003Bit-by-bit arbitration achieves unbroken transmission of arbitrated messages over the channel. The CAN protocol is particularly suitable for transmitting short messages under real-time conditions, in which case, with proper assignment of identifiers, particularly important messages almost always win arbitration and are successfully transmitted. Is guaranteed.
0004The amount of data transmitted and the delays allowed during transmission as modern vehicles become increasingly networked and, for example, additional systems are incorporated to improve driving safety or driving comfort. The demand for time increases. Examples include driving dynamics control systems such as ESPs (Electronic Safety Programs), driver assistance systems such as ACC (Automatic Interval Control), or driver information systems such as traffic sign detection. (For example, Vieweg + See "Bosch Automobile Handbook" by Taubner, 2011, 27th edition).
0005German Patent Application Publication No. 10311395 allows asymmetric series communication to be performed alternativeally via an asymmetric physical CAN protocol or via a symmetric physical CAN protocol. The system is described, which may provide higher data transmission rates or reliability of data transmission for asymmetric communication.
0006German Patent Application Publication No. 102007051657 proposes to utilize non-CAN compliant asymmetric and high speed data transmission in the exclusive time slot of the TTCAN protocol to increase the amount of data transmitted. There is.
0007G. Cena and A. Valenzano in "Overclocking of controller area networks" (Electrics Letters, Vol.35, No.22 (1999), S.1924), a partial range of messages for efficiently acquired data rates. Discusses the effect of overclocking the bus frequency within.
0008It turns out that the prior art does not provide satisfactory results in every respect.
<p num="0009"> In the following, the present invention and its advantages will be described with reference to the drawings and examples. The subject matter of the present invention is not limited to the examples presented and described.</p><p num="0010"> The present invention starts with the transmission of a message having a logical structure conforming to the CAN standard ISO11898-1 in a bus system having at least two involved data processing units, in which the logical structure starts of Frame Bit (Start-of-Frame-Bit), Arbitration Field, Control Field, Data Field, CRC Field, Acknowledge Field, and End of Frame Sequence (End) -of-Frame Sequenz), and the control field contains a Data Length Code that contains information about the length of the data field.</p><p num="0011"> In the present invention, the data field of the message can deviate from the CAN standard ISO11898-1 and exceed 8 bytes, and at that time, in order to confirm the size of the data field, the 4-bit data length code Data whose values are interpreted at least in part outside the CAN standard ISO 11898-1 and at least one temporary memory is provided for use and transferred for data transfer between the data field and the application software. The amount is at least a great way to be adjusted by adjusting for the difference in size between the data field and the temporary memory used, if the size of the data field is different from the size of the temporary memory used. provide. This makes it possible to continue using the application software without changing it, and even if the size of the data field may be larger than the CAN standard, it is necessary to increase the size of the communication controller unnecessarily. The advantage of not having is realized.</p><p num="0012"> Advantageously, if the size of the data field exceeds the size of the temporary memory used, typically 8 bytes, then the size of the temporary memory used from the data field of the message received over the bus. The corresponding amount of data, especially including 8 bytes, is selected according to a preset or preset selection method and transferred to temporary memory. If the size of the data field exceeds the size of the temporary memory used, the data field of the message sent over the bus will have the contents of the temporary memory preset at least one of the data fields of the message. And recorded within a preset range, the remaining range of the data field is filled according to a preset or preset method. To prevent the message length from becoming unnecessarily large, the above bits in the above-filled range of the data field of the message sent over the bus should have stuff bits in that range in accordance with the CAN standard ISO 11898-1. Filled so that it does not need to be inserted.</p><p num="0013"> By creating a unique association between the content of the data length code and the length of the data field, high flexibility is advantageously achieved with respect to the presentable size of the data field.</p><p num="0014"> In an advantageous development of the method, the expansion of the data field and the adjustment of the interpretation of the contents of the data length code are performed according to the first switching condition, and thus the present invention is in the presence of the first switching condition. It is used, but otherwise data transmission is done according to normal CAN standards. The markings in the arbitration field and / or the control field allow the message according to the invention to be distinguished from the message conforming to the CAN standard. The indicator is evaluated within the data processing unit involved to determine the first switching condition, and therefore the receiving process is adjusted for the size of the data field according to the first switching condition. This realizes the advantage that the apparatus according to the present invention can be used in both a standard CAN bus system and a new bus system according to the present invention having a potentially larger data field.</p><p num="0015"> Further, if the data field is expanded according to the present invention, it is possible to utilize the modified polynomial for the calculation of the checksum and transmit it within the CRC field. This has the advantage that the reliability of error detection is maintained even when a larger amount of data is transmitted. In a particularly advantageous embodiment, at the beginning of the message, multiple calculations of checksums are started in parallel, depending on whether one, and in some cases the same switching conditions, are met, or according to the content of the data length code. It is determined which result of one of the above calculations is used or transmitted within the CRC field. This makes it possible to send along with the message information about whether the message is transmitted according to a standard-compliant method or according to a modified method according to the invention, which is utilized in advance by the recipient. The method is not notified. Checksums for checking for correct data transmission exist for two methods and can be evaluated as needed.</p><p num="0016"> When the present invention is combined with bit length switching, for example for bits in a data field and a CRC field, a larger amount of data is accelerated and transmitted to increase the medium data transmission rate of the bus system. Another advantage is achieved. Again, it is also an advantage to combine the switching with the switching conditions and to add a corresponding indicator to the modified and transmitted message having the altered bit length.</p><p num="0017"> Each existing switching condition is communicated to the recipient by one or more indicators. In this case, at least one indicator is the first indicator bit whose position exists between the last bit of the identifier and the first bit of the data length code and is fixed in the message according to CAN standard ISO11898-1. If a bit having a value is given by the first marking bit present at that position and therefore the device according to the invention can be used in both standard CAN bus systems and new bus systems according to the invention. , Especially advantageous. Further another labeling by yet another indicator bit (BRS) is advantageously done by one bit that exists between the first indicator bit and the first bit of the data length code. As a result, the bit length can be switched independently of the CRC operation or the size of the data field, and it is possible to flexibly respond to the state of the bus system.</p><p num="0018"> It is advantageous to provide one or more additional state bits in order to know each transmission method used, and this state bit relates to a data processing method that deviates from the CAN standard ISO 11898-1 for application software. Information is provided. For example, it is possible to envision a state bit for notifying successful transmission and / or a state bit for notifying successful reception and / or a state bit for notifying the form of the most recently generated error. According to the frequency of errors in data transmission methods that deviate from CAN standard ISO11898-1, it is advantageous to switch back to CAN standard ISO11898-1 compliant transmission method and signal this with yet another state bit. It is possible.</p><p num="0019"> In the message memory and / or in the temporary memory, one or more additional message bits are advantageously provided to indicate the data transmission method used or used for each message. Here, for example, it is possible to record a sign provided in the message.</p><p num="0020"> The method can advantageously be used in normal driving of a vehicle to transmit data between at least two controllers in the vehicle connected via a suitable data bus. However, similarly during the manufacture or maintenance of the vehicle, between the programming unit connected to the appropriate data bus for programming purposes and at least one controller of the vehicle connected to the data bus. It can be used to transmit data. Similarly, the present invention can also be utilized in the industrial field, for example, when it is necessary to transmit a larger amount of data for the purpose of control. This method, in particular, if the reduced data rate during arbitration must be utilized based on the length of the transmission section so that all subscribers can gain access to the bus. , It is possible to achieve a higher data transmission rate by combining the switching of the length of the data field and the shortening of the bit length.</p><p num="0021"> Yet another advantage is that the standard CAN controller needs to be modified to a minimum in order to be able to function under the present invention. The communication controller according to the present invention, which can also function as a standard CAN controller, is slightly larger than the conventional standard CAN controller. There is no need to change the attached application program, and the advantage is already realized in terms of the speed of data transmission.</p><p num="0022"> Advantageously, a large part of CAN's conformance-test (ISO16845) is taken over. In a favorable development, the transmission method according to the invention can be combined with a complement to TTCAN (ISO11898-4).</p>
0023In the following, the present invention will be described in more detail with reference to the drawings.<figref num="1a">Two options (standard type / extended type) of the message structure in the CAN format conforming to the CAN standard ISO11898-1 by the conventional technology are shown.</figref><figref num="1b">Two similar options for message formats modified according to the invention according to an embodiment of the invention are shown.</figref><figref num="2">It shows various possibilities of how the contents of the data length code can be interpreted deviating from the CAN standard ISO11898-1 based on the present invention.</figref><figref num="3">The reception process according to the present invention at the subscriber station of the bus system according to the embodiment of the present invention is schematically shown.</figref><figref num="4">The reception process according to the present invention at the subscriber station of the bus system according to another embodiment of the present invention is schematically shown.</figref><figref num="5">For one embodiment of the present invention, a modified message format according to the present invention is additionally shown in which various bit lengths are utilized in a fixed range in the message.</figref><figref num="6">De being transferred between the data fields and application software for over data amount shows an example of the adjustment according to the present invention.</figref><figref num="7">A modified message according to the invention according to another embodiment of the invention, in which different bits are used to switch the size and bit length of the data field, and additional bits are contained within the control field. Here are two options (standard / extended) for the format of.</figref><figref num="8">A receiving process tuned for the same embodiment of the present invention, performed at a subscriber station of a bus system, is shown.</figref>
0024Figure 1a shows the structure of the message, that is, how the message is used for data transmission on the CAN bus. Two different formats are shown: "Standard" and "Extended". The method according to the invention is available in two formats in a suitable embodiment.
0025The message begins with a "Start of Frame (SOF)" bit that signals the start of the message. This is followed, first of all, by a section that helps identify the message, which allows the subscriber of the bus system to decide whether or not to receive the message. This section is called the "Arbitration Field" and contains the identifier. This is followed by a "Control Field" that specifically contains a Data Length Code. The data length code contains information about the size of the data field in the message. This is followed by the original "data field" (Data) that contains the data exchanged between the subscribers of the bus system. Field) follows. It is followed by a "CRC field" with a checksum and delimiter containing a 15-bit length, followed by two "acnoridges" that serve to signal the success of receiving a message destined for the sender. (ACK: Acknowledge) bit ", followed by. The message ends with an "End of Frame" (EOF) sequence.
0026In a standard-compliant CAN data transmission method, the data field may contain up to 8 bytes, or 64-bit data. The data length code contains 4 bits according to the standard, that is, it can take 16 different values. From this range of values, eight different values are used in today's bus systems for data fields of various sizes, from 1 to 8 bytes. A 0-byte data field is not recommended by the CAN standard and is not allowed to be larger than 8 bytes. The assignment of data length code values to the size of the data field is shown in the CAN standard column of Figure 2.
0027In Figure 1b, modified messages transmitted under the present invention, obtained from each of the two standard formats, are contrasted in a similar diagram.
0028In the modified transmission method according to the invention, the data field can exceed 8 bytes, i.e. may contain up to K bytes in the specifications shown. Unlike standard CAN, additional values that the data length code can take are used to label larger data fields. For example, it is possible to use 4 bits of the data length code to indicate a value from 0 to 15 bytes. However, other allocations are possible, for example, the value of the data length code DLC = 0b0000, which is not normally used in today's CAN messages, to yet another possible size of the data field, eg 16 bytes. It can be used for the purpose.
0029These two possibilities are shown as DLC1 and DLC2 in the table in Figure 2. In this case, the maximum value K of the data field has a value of 15 or 16. Yet another possibility is that for data length code values greater than 0b1000 up to 0b1111, the corresponding size of the data field will increase by a larger increment. An example of this case is shown in the table as DLC3. The maximum value K of the data field reaches a value of 64 bytes in this variant. Of course, yet another choice is possible, for example incrementing by 4 bytes.
0030Whether the communication of the bus system is proceeding according to the standard CAN or the method according to the present invention in order to ensure that the communication controller according to the present invention can confirm how it interprets the contents of the data length code. It is advantageous that the communication controller can autonomously detect. The possibility for this is to utilize the reserved bits in the arbitration or control field for labeling, based on which the communication controller chooses the transmission method accordingly. It is possible to derive the switching condition of. For example, the second bit of the control field, represented by r0 in Figure 1b, can be used for labeling.
0031The above settings can also be selected according to the format of the identifier. Therefore, for standard addressing, the possibility of labeling messages according to the invention is recessive, in the control field, at the position of the r0 bit, which is always dominant in the standard CAN. ) Insert EDL (Extended Data Length) bits. For extended addressing, the recessive EDL bit can be in the control field at the r1 bit, which is always dominant in standard CAN.
0032Another possibility is to utilize the SRR bit, which is received dominantly by some bus subscribers who receive the message, although the standard CAN must always send it recessively. It is also possible to evaluate the bit combination to confirm the first switching condition.
0033Yet another possibility would be to specify the use of extended formats for transmission methods modified under the present invention. The extended format message is detected by the bus subscriber by the value of the IDE bit (see Figure 1a), and at the same time, this IDE bit could represent the first switching condition. Therefore, a modified transmission method is always utilized for extended messages. Alternatively, in the extended message, the reserved bit r1 could be used to label the first switching condition or to derive the condition. However, the reserved bit is a second, as described in detail below, for switching between two or more different sizes of the data field, or for associating the value of the data length code with the size of the data field. It can also be used to derive switching conditions.
0034However, as an alternative, the method can also be used within the communication controller, which is a suitable communication controller for this purpose and is not designed for standard CAN communication. In this case, it is possible to omit the setting of the first switching condition described above, which depends on, for example, appropriate labeling of the message. In this case, the communication controller rather operates according to only one of the described methods, and correspondingly, is used only in the bus system in which such a communication controller according to the invention is used.
0035As envisioned in the present invention, it is used for Cyclic Redundancy Check (CRC) to obtain sufficient fail safety (Fehlersicherheit) when the data field of a message is expanded. Adjusting the method can also be effective. In particular, it may be advantageous to utilize, for example, other higher-order CRC polynomials and correspondingly provide a CRC field of a different size than the standard in the message modified according to the present invention. This is presented in the example shown in FIG. 1b by the fact that the CRC field of the message according to the invention has a length of L bits, where L is not the same outside the CAN standard, especially more than 15 bits. It may be large.
0036Utilization of the modified method for calculating the CRC checksum can be signaled to the bus subscriber by a marker representing a third switching condition. However, the above marking and the third switching condition may match the first marking and / or the switching condition. Again, as described above, for example, the reserved bit r0 in FIG. 1b may be useful for labeling, or the SRR bit may be utilized. The use of IDE bits in combination with the application of the present invention in extended messages or in combination with the application of the r1 bit is also considered.
0037Within a standard CAN controller, the CRC code of the transmitted CAN message is generated by a feedback shift register in which the bits transmitted in series of the message are supplied in series to its input port. The width of the shift register corresponds to the degree of the CRC polynomial. CRC coding (CRC-Codierung) is performed by combining register contents with CRC polynomials (Verknuepfung) during shift operation. When a CAN message is received, the corresponding bits received in series in the message are shifted into the CRC shift register. The CRC-Test is successful if all bits of the shift register are 0 at the end of the CRC field. Both the generation of the CRC code in the case of transmission and the CRC inspection in the case of reception are performed in hardware, and no software intervention is required. That is, the change in CRC coding has no effect on the application software.
0038In a possible embodiment, the communication controller is designed to be compatible with the standard CAN, i.e., to operate in compliance with the standard within the standard CAN bus system, while the communication controller is. Within the bus system modified under the present invention, on the one hand, it allows larger data fields in the message, and on the other hand, it also performs coordinated calculations and checks of the CRC code.
0039Since it has not yet been determined whether a CAN message conforming to the standard or a message modified based on the present invention is received at the start of receiving the message, the communication controller according to the present invention operates in parallel 2 Two CRC shift registers are implemented. If the CRC code is evaluated at the receiver after receiving the CRC delimiter, the third switching condition may be based on the labeling according to the present invention or, for example, derived from the content of the labeling or data length code. Based on this, which transmission method is used is determined, and then the shift register associated with the used transmission method is evaluated. The third switching condition may match the first switching condition regarding the size of the data field and the interpretation of the data length code, as already shown above.
0040At the beginning of message transmission, it is already determined for the sender which transmission method is used for transmission. However, it is possible that the arbitration around bus access will be lost, the initiated message will not be sent, and another message will be received instead, so again the two CRC shift registers will be in parallel. Driven.
0041Further improvements are possible with the above implementation of two CRC registers operating in parallel, ie the standard CAN protocol CRC polynomial (x15 + x14 + x10 + x8 + x7 + x4 + x3 + x1) is more than 127 bits. Designed for small message lengths. When the message transmitted based on the present invention also utilizes a longer data field, it is effective to utilize another CRC polynomial, which is particularly longer, in order to maintain transmission reliability. The message transmitted under the present invention correspondingly acquires a modified, especially longer CRC field. During drive, the communication controller dynamically switches between two CRC shift registers, namely standard CAN compliant shift registers and shift registers according to the present invention, in order to utilize each appropriate polynomial.
0042Of course, it is also possible to use more than two shift registers, and correspondingly more than two CRC polynomials, in stages, depending on the length of the data field or the desired transmission reliability. In this case, it is necessary to adjust the corresponding markings and associated switching conditions as long as compatibility with the standard CAN is maintained. For example, switching to a longer data field according to DLC1 in FIG. 2 and invoking the first switching condition characterized by the corresponding second CRC polynomial, for example, by the reserved bit r0 or SRR bit in FIG. 1b. Would be possible. For messages in extended format, additional sets of data field sizes, such as switching to DLC3 in Figure 2, and a third CRC polynomial, for example by the reserved bit r1 or IDE bit in Figure 1b, It would be possible to activate a second switching condition characterized by.
0043The first switching condition switches the corresponding interpretation of the contents of the longer possible data field and data length code, for example by the reserved bit r0 or SRR bit, and determines and relates to the third switching condition. It is also usually possible that the selection of the CRC polynomial to be evaluated for CRC inspection is made according to the contents of the data length code. The third switching condition can correspond to more than two values. For example, it would be possible to choose the size of the data field for DLC3, i.e. take a value between 0 and 64 bytes, in which case the three CRC polynomials via the appropriate shift register. , For example, a standard CRC polynomial for data fields up to 8 bytes, a second CRC polynomial for data fields up to 24 bytes, and a third CRC polynomial for data fields up to 64 bytes in parallel. It will be possible to calculate.
0044FIG. 3 is a simplified diagram showing a part of the receiving process according to the present invention, that is, how the receiving process proceeds at the subscriber station of the bus system. Here, a case where compatibility with the standard CAN is realized by adjusting the behavior of the communication controller according to the first switching condition is shown. In Figure 3, a general diagram was chosen to describe the program sequence in software, but this method is perfectly suited for implementation in hardware.
0045The subscriber station is initially ready to sample the bus unless there is communication traffic on the bus. That is, inquiry 302 waits for a dominant bit on the bus. This dominant bit represents the start of a new message.
0046As soon as the start of a new message is confirmed, in block 304, the calculation of at least two checksums calculated in parallel is started. The first checksum corresponds to the CRC operation of the standard CAN, and the second checksum is calculated according to the new method.
0047Subsequently, from step 306, another bit starting with the arbitration field, which follows the SOF bit of the message, is received. If multiple bus subscribers want to send a message, here a arbitration is made between the bus subscribers according to the standard CAN general method as to which subscriber gains access to the bus. .. The block 306 shown represents the reception of all bits until the first indicator is received or the first switching condition is determined. In the examples described, the first switching condition is determined from the arbitration field, eg, from the SRR or IDE bits, or from the control field, eg, from the reserved bits of the control field (see Figure 1). Subsequently, in block 308, additional bits of the message may be received after a particular bit of the message until various processing is performed according to a defined first switching condition. This division by various modes of processing is guaranteed by the corresponding query or branch 310, as illustrated below.
0048At branch 310, for example, after receiving the first 2 bits of the control field, there is information that communication is performed in accordance with the standard CAN according to the first switching condition (route shown by "1" in FIG. 3). If so, at step 312, another bit of the control field is read. From this additional bit, the data length code is evaluated according to standard CAN, and in step 316, the corresponding amount of data, i.e. up to 8 bytes corresponding to the data field, is received. Then, in step 320, a CRC field containing 15 bits is received. At branch 324, if there is information that the CRC checksum transmitted by the sender matches the CRC checksum determined by the receiver himself, then at block 328, the dominant Acknowledge-Bit. ) Is sent. Note that in this case, the communication is performed according to the standard CAN, so the CRC checksum conforming to the standard is compared. If no match is found, the acknowledge bit is sent recessively (at block 330). This is followed by an ACK delimiter and an EOF bit (see Figure 1b, not shown in Figure 3).
0049On the other hand, in the case of branch 310, for example, when there is information that the communication method modified based on the present invention is used according to the first switching condition after receiving the first two bits of the control field (Fig. In block 314, the path indicated by "2" in 3), another bit of the control field is read. From this result, the data length code is determined according to the new interpretation described for some examples in the table of Figure 2. At block 318, the corresponding amount of data is received, that is, up to 15 bytes for example DLC1 in the table of FIG. 2, up to 16 bytes for example DLC2, and up to 64 bytes for example DLC3. At block 322, different, especially longer CRC fields are received according to the invention. In branch 324, if there is information that the CRC checksum transmitted to the sender matches the CRC checksum determined by the receiver himself, then in this case the above comparison is different based on the present invention. Is based on, but at block 328, a dominant acknowledge bit is transmitted. If the CRC checksum transmitted to the sender does not match the CRC checksum determined by the recipient himself, the acknowledge bit is transmitted recessively (at block 330). Subsequently, in step 332 or 334, the ACK delimiter and EOF bit follow. This ends the receiving process for the message.
0050FIG. 3 shows the case where the third switching condition that determines the CRC used matches the first switching condition regarding the size of the data field and the interpretation of the data length code. That is, prior to the receipt of the CRC checksum 320 or 322, no query was made again as to which CRC was received according to the third switching condition and evaluated for branch 324. This additional query can be incorporated into the sequence, as shown in Figure 4, by simply modifying the flow diagram in Figure 3.
0051In the receiving process of FIG. 4 thus modified, after receiving the expected number of data bytes in the data field according to the information in the data length code at block 316 or 318, the third switching condition at the query or branch 410 Determines what value the has. This information can be determined, for example, from the content of the corresponding third indicator or data length code, as described above. In the example shown, there are three different values, A, B, and C, for the third switching condition. Then, according to the value of the switching condition, in blocks 420, 422, and 424, various bits of the CRC field are read, for example, 15 bits for the value A, 17 bits for the value B, and 19 bits for the value C. Is read. Subsequently, as in FIG. 3, at branch 324, the CRC checksum transmitted by the sender is checked for matching with the CRC checksum determined by the receiver himself, and further processing is performed accordingly.
0052FIG. 5 reshows two possible variations, namely the structure of a message in standard format and a message in extended format, for yet another embodiment of the transmission method according to the invention. Figure 5 shows the range of the two variations that can be switched between the two states, here called Fast-CAN-Arbitration and Fast-CAN-Data. In this example, switching between the two states reduces the bit length for some of the messages, especially for the data and CRC fields, after the arbitration is complete, and the individual bits are transmitted over the bus faster. This makes it possible to shorten the message transmission time compared to the standard-compliant method. The associated temporal bit length switching can be achieved, for example, by using at least two different multiples to adjust the bus time unit relative to the minimum time unit or the oscillator clock being driven. Is. Bit length switching and corresponding changes in magnification are also illustrated in FIG.
0053The transition between state fast CAN arbitration and state fast CAN data is a message indicator, corresponding to the above indicator signaling that the reduced bit length is used to the subscribers of the data transmission. It can be done according to another switching condition. In the embodiment shown here, the position of this indicator selected is the "reserved bit" r0 transmitted before the data length code. That is, this position is the first indicator corresponding to the first switching condition and the above first indicator indicating that a longer data field and a modified interpretation of the data length code are available. It also corresponds to the possible position and the possible position of the third indicator corresponding to the modified CRC operation.
0054Other possibilities for labeling messages according to the invention with reduced bit lengths are shown in FIG. Here, the message in which the data field can be longer (corresponding to the first indicator) and the modified CRC operation (corresponding to the third indicator) are the recessive EDL bits (extended data length). It is labeled by the EDL bit above, which enters the location of the dominantly transmitted bit by the standard CAN message, replaces the bit, or shifts the bit back by one position. For standard addressing, the EDL bit goes into a second position in the control field and shifts the always dominant r0 bit in that second position by one position. For extended addressing, in the example shown, the EDL bit is in the first position of the control field and is in that first position, reserved bit r1 which is always dominant in standard CAN. To replace. The fourth indicator announcing the use of the reduced bit length is an additional recessive BRS (Bit) to the control field of the message according to the invention labeled with the EDL bit. Rate Switch, Bit rate switching) Indicated by the insertion of bits. In the embodiment shown here, the position of the BRS bit is the 4th position (standard type addressing) or the 3rd position (extended type addressing) in the control field.
0055The message has the name "CAN FD Fast". For two possible addressing variations of the message, the standard format and the extended format, Figure 7 shows the range that can be switched between two states called fast CAN arbitration and fast CAN data. Switching between these two states reduces the bit length for the corresponding part of the message and allows individual bits to be transmitted faster over the bus, as described above. This makes it possible to shorten the message transmission time compared to the standard-compliant method. The transition between state fast CAN arbitration and fast CAN data further signals the subscriber to the data transmission that the shortened bit length will be utilized in the message with the first or third labeled EDL. Followed by another label BRS.
0056In the case shown, the first labeled EDL is followed by the second labeled BRS, but in the transmission method according to the present invention, the bit length is clearly short and the size of the data field exceeds 8 bytes. A message is transmitted that is extensible to and whose CRC is adjusted for larger data fields. In this way, an improvement in transmission reliability is achieved at the same time as a significant increase in the transmission capacity via the bus system.
0057In the example shown, the reason for the faster transmission to start shortly after the transmission of the corresponding indicator and end shortly after reaching the bit set for return switching, or to start an error-frame. It ends when it is detected.
0058FIG. 8 shows a modified receive process relative to FIG. 3, which additionally switches between state fast CAN arbitration and state fast CAN data according to the second indicator BRS. If there is information at branch 310 that the modified communication method according to the invention will be used after receiving, for example, the second bit of the control field as an recessive bit EDL, in block 408, of the control field The most recent bit is read. A bit that serves as a second indicator, eg, a fourth bit of a control field extended under the present invention, with a conceived value, BRS, for example, if received recessively, for example the sample point of the BRS bit. (Sample At Point), the state fast CAN data is entered, that is, switched to the shortened bit length (path "C"). If the BRS bit has the opposite value, that is, the dominant value in this case, the bit length is not shortened (path "B"). At block 412 or 414, the remaining bits of the control field including the data length code are received, and the data field related to the size information from the data length code is received. In block 412, it is received with a normal bit length, and in block 414, it is received with a shortened bit length. At block 416 or 418, different, especially longer CRC fields are read according to the invention. At block 418, the last bit of the CRC field, the CRC delimiter, switches back to state fast CAN arbitration at normal bit rates. Subsequently, at branch 324, as in FIG. 3, the CRC checksum transmitted by the sender is checked for a match with the CRC checksum determined by the recipient himself, and accordingly, already shown in FIG. As such, further processing is performed.
0059Faster transmissions begin, for example, immediately after the corresponding indicator, end shortly after reaching the bit defined for return switching, or end when a reason for initiating an error frame is detected.
0060This method is suitable for data transmission between at least two control devices of a vehicle connected via a suitable data bus during normal operation of the vehicle. However, it is also for data transmission between the programming unit connected to the appropriate data bus for programming purposes and at least one controller of the vehicle connected to the data bus during vehicle manufacturing or maintenance. It can be used advantageously as well. Further, in industrial automation, the present invention is used, for example, to transmit control information between distributed control units connected to each other by a bus and controlling the flow of an industrial manufacturing process. It is also possible to do. Very long bus lines can also emerge in this area, and it is also particularly advantageous to drive the bus system with relatively long bit lengths, for example 16, 32, or 64 microseconds, during the arbitration phase. There is a possibility, so the bus signal can be propagated as much as needed throughout the bus system during the arbitration process. Subsequently, as described above, it is possible to switch some of the messages to shorter bit lengths so that the medium-sized transmission rate does not become too low.
0061As described above, this method is an excellent transmission method in that the standard CAN controller needs to be changed to the minimum so that it can operate based on the present invention. The communication controller according to the present invention, which can also operate as a standard CAN controller, is slightly larger than the conventional standard CAN controller. There is no need to change the corresponding application program, and the advantage is already realized in terms of data transmission speed. By utilizing the extended size of the data field and the corresponding DLC and CRC, it is possible to further increase the data transmission speed and the adjustment in the application software is minimal. It is possible to take over a wide range of CAN-Conformance-Test (ISO16845). Further, it is also possible to combine the transmission method according to the present invention with a complement of TTCAN (ISO11898-4).
0062Fully or fully compatible with respect to the application software utilized for the data transmission methods according to the invention and the devices that implement the data transmission methods, at least for specific application purposes or at the introduction stage. It is useful to envision a working variation. The application software may be, for example, electronic stability control adjustment software for the vehicle or control software for the vehicle's internal combustion engine. That is, the application software requires a huge protection program, especially for security-critical systems, and it is therefore advantageous to be able to implement the modified data transmission device based on the present invention without modifying the application software. Is.
0063The transfer of data between the data field of the message and the application software is a temporary memory provided for this use within the communication controller, which has a predetermined size of, for example, 8 bytes in the standard CAN. It is performed via the temporary memory and the attached message memory. Temporary memory and message memory may mean a range allocated for corresponding use within a larger memory unit in the context of the present invention.
0064Correspondingly, in a system that performs data transmission according to the standard CAN, application software allows data packets up to 8 bytes in size to be sent to the data field of a CAN message, usually via a large number of message memories and temporary memory. Will be exchanged for. When the application software has not been modified, the message memory and temporary memory are left at a predetermined size of, for example, 8 bytes so as not to increase the size or chip area of the communication controller according to the present invention more than necessary. It is also possible to keep it. When the size of the data field (for example, 16 bytes) of the message according to the present invention is different from the size of the temporary memory used (for example, 8 bytes), the protocol control unit of the communication controller is set to the data field and the temporary memory. It is necessary to adjust according to the difference in size of.
0065Therefore, in yet another embodiment of the data transmission method according to the invention, which is shown in FIG. 6 with an example of a standard format message having a data field with a size of 16 bytes, with respect to the serial transmission of bits over the bus. It is envisioned that the full functionality of the invention will be performed and that only the relevant 8 bytes of user data in the data field will be transmitted. That is, when a corresponding switching condition exists, a message with, for example, a 16-byte size data field and an attached indicator is transmitted over the bus, and a correspondingly adjusted CRC. The polypoly checks the message for accuracy of transmission, while for application software 640 via, for example, temporary memory 620 in the communication controller according to the invention, and, for example, message memory 630. 8 bytes of user data are passed. In the case of transmission, the application software 640 writes 8 bytes of user data to the temporary memory 620 via, for example, yet another or identical message memory 630, and the 8 bytes of user data are preset. It is recorded in, for example, a 16-byte large data field of the transmitted message according to a preset method. Of course, it is also possible to limit the amount of temporary memory to a size different from 8 bytes, for example 6 or 4 bytes. This is especially useful when applying this limitation to application software as well. The choice of data field size of 16 bytes is understood as merely exemplary and may include, for example, values of 24, 32, or 64 bytes. Many other possibilities can be seen, for example, in Figure 2. There is a relationship between the amount of data passed from the message to the application program, or the amount of data provided by the application software for recording into the data field of the message, and the size of the temporary memory 620.
0066In this embodiment, the protocol control unit of the communication controller, for example, 8 bytes of user data from the temporary memory 620, when serializing the transmitted data, as shown by the double arrow 600 in FIG. Is positioned within the first eight serial bytes of the data field, and the other bits of the data field are preset or preset filling data, or, for example, predetermined, as shown by arrow 610 in FIG. It is possible to fill with any filling data having a bit pattern of. Here, it is effective to use a bit string that does not cause the insertion of additional stuff bits (Stuff-Bit) in accordance with the CAN standard ISO11898-1. Otherwise, the data field will grow unnecessarily. That is, for example, it is possible to insert the bit string 0b00110011 or 0b11001100 for each unused byte of the data field.
0067It is also possible to record, for example, 8 bytes of user data in the temporary memory 620 not in the first 8 bytes of the data field, but in another location in the data field or in a plurality of other ranges. The location of the user data bytes needs to be uniformly preset or preset for the bus subscriber.
0068The bus subscriber according to the present invention reads a message according to the method according to the present invention, performs, for example, a CRC inspection, and confirms accurate reception by an Acnoledge. The protocol control unit in the communication controller of the receiving bus subscriber moves the bits received in series in the message, and at that time, extracts 8 bytes of user data from, for example, a 16-byte data field, and this 8 bytes. User data is written to the temporary memory 620. This is also indicated by the double arrow 600 in FIG. The remaining filling data is discarded. That is, only 8 bytes of user data are passed to the application software 640 via the temporary memory 620 and, for example, the message memory 630. The application software 640 itself is no different than using a standard-compliant transmission method.
0069Various embodiments of the data transmission method according to the present invention, in particular, shortening the bit length within a part of the message, changing the length of the data field, changing the interpretation of the content of the data length code, and so on. That is, a fail-safe way to adjust the amount of data that is changed in multiple steps (mehrstufig), various checksums are used, or transferred is adjusted for the difference in the size of the data field and temporary memory. (fehlersicher) Further complementation is effective for realization.
0070With the appropriate state registers, for example in standard CAN, the error state (Error-Warning, Error-Passive), Bus Off (Bus) that is entered when an error occurs at the corresponding frequency during data transmission. It is guaranteed that reaching -Off)) can be read, for example by a microcontroller or application software. In addition, the success of the transmit and receive processes is signaled by a flag (TxOK, RxOK) and information is prepared for each most recent bus event (LEC: Last Error). Code, final error code). It is possible to provide some or all of the above information in multiple layers within the communication controller according to the invention, in the memory area provided for it, and thus, for example, the attached microcomputer or The application software running on the microcomputer can collect and store each piece of information separately according to the data transmission method actually executed. This is a transmission method modified for the CAN standard, for example, when the data field is longer or the bit length is shorter within the range of the message, a specific failure mode (Fehlerbild) is the transmission method of the standard CAN. It is possible to see if it occurs more often than.
0071It is possible to introduce additional error states and signal them by state bits, which permanently transfer data transmission to the standard CAN transmission method in the event of frequent errors in the changed transmission mode. Switch back and switch. Information TxOK, RxOK, and LEC can be collected separately for various data transmission methods. Alternatively, it is possible to store additional information about the LEC in which transmission mode the error occurred.
0072In addition, for the received message, record which of the possible indicators, along with which indicator the received message was received, and for the transmitted message, according to which method and with which indicator. It may be effective to individually set whether or not to be performed. To this end, certain or all received message memory and / or temporary memory can be supplemented with a plurality of additional bits corresponding to possible indicators. It is also possible to separately store information about in which state or under what switching condition each message was received in yet another bit provided for this purpose. Similarly, certain or all outgoing message memory and / or temporary memory may be provided with additional bits, to which the additional bits are labeled in a modified manner and / or corresponding to each message. It is recorded that it is sent with.
0073Finally, take advantage of the mode corresponding to the application software where the amount of data transferred between the data field of the message and the application software is limited to, for example, 8 bytes, and the correspondingly large amount of temporary memory used. It is effective to design the communication controller according to the present invention so that it can be switched between the mode optimized for data transmission utilizing the entire size of the data field and the mode optimized for data transmission by appropriate reconstruction. Can be. In this case, the corresponding savings in size or chip area cannot be achieved by using correspondingly smaller temporary memory and / or message memory, but bus subscribers who continue to use the existing application software. Within and within the bus subscribers for which new software optimized for data transmission has been created, the communication controller can be used with great flexibility.
0074This switchable communication controller sets its own mode currently in use, that is, a mode corresponding to the application software, or a mode optimized for data transmission, within the memory area provided for this purpose. , For example, should be visualized by the corresponding state bits.
0075Where the ISO standard is cited in previous descriptions of the present invention, each version of the corresponding ISO standard that is valid at the time of filing is the basis of the prior art.
9 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| JP2010258990A | Cites | Japan |
| JP2001339412A | Cites | Japan |
| JP2010272971A | Cites | Japan |
| US20070091932A1 | Cites | United States of America |
177 members in 12 offices
Priority claims7
| Document | Office | Kind | Date |
|---|---|---|---|
| 1020110175393 | Germany | – | |
| 102011017539 | Germany | A | |
| 1020110782664 | Germany | – | |
| 102011078266 | Germany | A | |
| 1020110804765 | Germany | – | |
| 102011080476 | Germany | A | |
| 2012057593 | European Patent Office (EPO) | W |
Members177
| Document | Office | Kind | |
|---|---|---|---|
| DE102011006875A1 | Germany | A1 | |
| DE102011006884A1 | Germany | A1 | |
| WO2012136545A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2012136546A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2012136547A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2012136550A1 | World Intellectual Property Organization (WIPO) | A1 | |
| DE102011017539A1 | Germany | A1 | |
| WO2012146631A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2012146649A1 | World Intellectual Property Organization (WIPO) | A1 | |
| TW201246869A | Taiwan Province of China | A | |
| DE102011078266A1 | Germany | A1 | |
| WO2013000902A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2013000911A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2013000916A1 | World Intellectual Property Organization (WIPO) | A1 | |
| TW201303574A | Taiwan Province of China | A | |
| TW201304482A | Taiwan Province of China | A | |
| DE102011122843A1 | Germany | A1 | |
| DE102011122845A1 | Germany | A1 | |
| TW201306523A | Taiwan Province of China | A | |
| DE102011080476A1 | Germany | A1 | |
| WO2013020781A1 | World Intellectual Property Organization (WIPO) | A1 | |
| TW201310246A | Taiwan Province of China | A | |
| AU2012238883A1 | Australia | A1 | |
| AU2012238884A1 | Australia | A1 | |
| CN103562900A | China | A | |
| CN103562901A | China | A | |
| EP2695073A1 | European Patent Office (EPO) | A1 | |
| EP2695074A1 | European Patent Office (EPO) | A1 | |
| EP2695075A1 | European Patent Office (EPO) | A1 | |
| EP2695076A1 | European Patent Office (EPO) | A1 | |
| AU2012277890A1 | Australia | A1 | |
| AU2012277899A1 | Australia | A1 | |
| AU2012277904A1 | Australia | A1 | |
| CN103620573A | China | A | |
| CN103620574A | China | A | |
| EP2702495A1 | European Patent Office (EPO) | A1 | |
| EP2702497A1 | European Patent Office (EPO) | A1 | |
| KR20140029431A | Republic of Korea | A | |
| KR20140029432A | Republic of Korea | A | |
| KR20140029433A | Republic of Korea | A | |
| KR20140030178A | Republic of Korea | A | |
| KR20140030213A | Republic of Korea | A | |
| KR20140030214A | Republic of Korea | A | |
| CN103649933A | China | A | |
| CN103649934A | China | A | |
| JP2014510498A | Japan | A | |
| KR20140050643A | Republic of Korea | A | |
| CN103782283A | China | A | |
| EP2726998A1 | European Patent Office (EPO) | A1 | |
| EP2726999A1 | European Patent Office (EPO) | A1 | |
| EP2727000A1 | European Patent Office (EPO) | A1 | |
| US2014129900A1 | United States of America | A1 | |
| KR20140056239A | Republic of Korea | A | |
| KR20140056240A | Republic of Korea | A | |
| KR20140058517A | Republic of Korea | A | |
| CN103827844A | China | A | |
| CN103842981A | China | A | |
| US2014156887A1 | United States of America | A1 | |
| US2014157080A1 | United States of America | A1 | |
| EP2740042A1 | European Patent Office (EPO) | A1 | |
| CN103890747A | China | A | |
| US2014177651A1 | United States of America | A1 | |
| JP2014515897A | Japan | A | |
| US2014201410A1 | United States of America | A1 | |
| JP2014518485A | Japan | A | |
| JP2014518598A | Japan | A | |
| JP2014518599A | Japan | A | |
| US2014223258A1 | United States of America | A1 | |
| JP2014520418A | Japan | A | |
| JP2014522140A | Japan | A | |
| US2014244871A1 | United States of America | A1 | |
| US2014245102A1 | United States of America | A1 | |
| US2014258571A1 | United States of America | A1 | |
| US2014258581A1 | United States of America | A1 | |
| JP2014528187A | Japan | A | |
| JP2014529918A | Japan | A | |
| JP2014531781A | Japan | A | |
| JP5702505B2 | Japan | B2 | |
| EP2695075B1 | European Patent Office (EPO) | B1 | |
| RU2013149025A | Russian Federation | A | |
| RU2013149026A | Russian Federation | A | |
| RU2013149027A | Russian Federation | A | |
| RU2013149028A | Russian Federation | A | |
| JP5723062B2This record | Japan | B2 | |
| RU2013152205A | Russian Federation | A | |
| RU2013152206A | Russian Federation | A | |
| JP5734515B2 | Japan | B2 | |
| ES2538234T3 | Spain | T3 | |
| RU2014102638A | Russian Federation | A | |
| RU2014102640A | Russian Federation | A | |
| RU2014102641A | Russian Federation | A | |
| JP5770924B2 | Japan | B2 | |
| JP5770925B2 | Japan | B2 | |
| JP5770935B2 | Japan | B2 | |
| JP2015159592A | Japan | A | |
| EP2702495B1 | European Patent Office (EPO) | B1 | |
| EP2726998B1 | European Patent Office (EPO) | B1 | |
| EP2726999B1 | European Patent Office (EPO) | B1 | |
| EP2727000B1 | European Patent Office (EPO) | B1 | |
| RU2014108166A | Russian Federation | A |
16 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 |
Numbers
- Publication
- 5723062
- Application
- 2014506854
Titles2
- Japanese
- メモリの大きさに対して調整される直列データ伝送のための方法及び装置
- English
- Methods and equipment for serial data transmission adjusted for memory size
Classification
- CPC, 8
- G06F13/4282
- H04L12/413
- H04L45/74
- H04L12/40013
- H04L12/4135
- H04L2012/40215
- G06F13/42
- G06F5/065
- IPC, 3
- H04L12 40
- H04L45 74
- H04L12 28
