Extension of audio / video bridging reservation protocol
17 claims: 3 independent, 14 dependent
- 1拡張したAVB予約プロトコルを用いたAVBシステムにおいて、 アプリケーションストリーム識別子またはAVBストリーム識別子を含むGARPメッセージを中継装置に送信する流出装置と、 前記GARPメッセージに従って前記AVBストリーム識別子または前記アプリケーションストリーム識別子を登録し、前記アプリケーションストリーム識別子を含むGARPメッセージを流入装置に送信する中継装置と、 前記アプリケーションストリーム識別子を含む前記GARPメッセージを介して前記アプリケーションストリーム識別子に対応するAVBストリーム識別子を割り当て、前記中継装置に予約信号を送信する前記流入装置と、 を含むことを特徴とするAVBシステム。
- 2前記中継装置は、 前記GARPメッセージから前記AVBストリーム識別子または前記アプリケーションストリーム識別子を抽出して登録し、前記GARPメッセージが前記アプリケーションストリーム識別子を含む場合、前記GARPメッセージを前記流入装置に送信することを特徴とする請求項1に記載のAVBシステム。
- 3前記予約信号は、前記アプリケーションストリーム識別子および前記アプリケーションストリーム識別子に対応する前記AVBストリーム識別子を含むことを特徴とする請求項1に記載のAVBシステム。
- 4前記中継装置は、 前記流入装置から受信された前記予約信号に基づいて前記AVBストリーム識別子および前記アプリケーションストリーム識別子をマッピングし、前記予約信号を前記流出装置に送信することを特徴とする請求項1に記載のAVBシステム。
- 5前記流出装置は、前記中継装置から受信された前記予約信号に基づいて前記AVBストリーム識別子および前記アプリケーションストリーム識別子をマッピングすることを特徴とする請求項1に記載のAVBシステム。
- 6前記GARPメッセージは、前記AVBストリーム識別子を含んで生成されたり、前記流出装置で前記AVBストリーム識別子を含まない場合、前記アプリケーションストリーム識別子を含んで生成されることを特徴とする請求項1に記載のAVBシステム。
- 7前記GARPメッセージは、前記AVBストリーム識別子または前記アプリケーションストリーム識別子のどちらの識別子を用いるかを示す属性タイプ情報を含むことを特徴とする請求項3に記載のAVBシステム。
- 8前記アプリケーションストリーム識別子は、前記AVB予約プロトコルを開始する上位階層のアプリケーションに対応し、 前記中継装置は、 前記アプリケーションストリーム識別子を登録する場合、前記アプリケーションストリーム識別子の登録情報に前記上位階層のアプリケーションに対するアプリケーションタイプを含んで登録することを特徴とする請求項1に記載のAVBシステム。
- 9前記中継装置および前記流出装置は、前記AVBストリーム識別子を含む場合、前記AVBストリーム識別子のみを用いてリソースの登録および予約のためのプロセスを遂行することを特徴とする請求項1に記載のAVBシステム。
- 10拡張したAVB予約プロトコルを用いたリソース予約方法において、 流出装置でAVBストリーム識別子を含まない場合、アプリケーションストリーム識別子を含むGARPメッセージを中継装置に送信する段階と、 前記中継装置で受信した前記GARPメッセージが含む前記アプリケーションストリーム識別子を登録して前記GARPメッセージを流入装置に送信する段階と、 前記流入装置で前記アプリケーションストリーム識別子に対応するAVBストリーム識別子を割り当てて予約信号を生成し、前記中継装置に送信する段階と、 前記中継装置で前記予約信号を用いて前記アプリケーションストリーム識別子および前記AVBストリーム識別子をマッピングし、前記予約信号を前記流出装置に送信する段階と、 を含むことを特徴とするリソース予約方法。
- 11流出装置でAVBストリーム識別子を含まない場合、アプリケーションストリーム識別子を含むGARPメッセージを中継装置に送信する前記段階は、 前記AVB予約プロトコルを開始する上位階層のアプリケーションから前記アプリケーションストリーム識別子を確認する段階と、 前記アプリケーションストリーム識別子を含むGARPメッセージを生成して前記中継装置に送信する段階と、 を含むことを特徴とする請求項10に記載のリソース予約方法。
- 12前記流出装置で前記AVBストリーム識別子を含む場合、前記AVBストリーム識別子を含むGARPメッセージを前記中継装置に送信する段階と、 前記中継装置で受信された前記GARPメッセージがAVBストリーム識別子を含む場合、前記AVBストリーム識別子を登録する段階と、 をさらに含むことを特徴とする請求項10に記載のリソース予約方法。
- 13前記予約信号は、前記アプリケーションストリーム識別子および前記アプリケーションストリーム識別子に対応する前記AVBストリーム識別子を含むことを特徴とする請求項10に記載のリソース予約方法。
- 14前記流出装置で前記中継装置から受信された前記予約信号に基づいて前記AVBストリーム識別子および前記アプリケーションストリーム識別子をマッピングする段階、 をさらに含むことを特徴とする請求項10に記載のリソース予約方法。
- 15前記アプリケーションストリーム識別子は、前記AVB予約プロトコルを開始する上位階層のアプリケーションに対応し、 前記中継装置で受信した前記GARPメッセージが含む前記アプリケーションストリーム識別子を登録して前記GARPメッセージを流入装置に送信する前記段階は、 前記アプリケーションストリーム識別子を登録する場合、前記アプリケーションストリーム識別子の登録情報に前記上位階層のアプリケーションに対するアプリケーションタイプを含んで登録する段階、 を含むことを特徴とする請求項10に記載のリソース予約方法。
- 16前記中継装置および前記流出装置は、前記AVBストリーム識別子を含む場合、前記AVBストリーム識別子のみを用いてリソースの登録および予約のためのプロセスを遂行することを特徴とする請求項10に記載のリソース予約方法。
- 17請求項10ないし16のいずれか一項の方法を実行させるためのプログラムを記録したコンピュータ読み取り可能な記録媒体。
Independent claims17
68 paragraphs, as filed
The present invention relates to an AVB system and a resource reservation method using an extended AVB (Audio / Video bridging) reservation protocol. Regarding AVB systems and resource reservation methods that carry out the registration or reservation process without extension of the application.
AVB is a technology that provides a streaming service with reduced delay in an IEEE802 network that uses time-synchronization. Such a technology uses the Resource Reservation Protocol (RSVP), which guarantees resources with a bridge for audio / video streams.
Current reservation protocols include an egress device that initiates a registration process and an ingress device that initiates an approval control process based on IEEE 802.1's Generic Attribute Registration Protocol (GARP).
The spill device uses GARP registration / deregistration to reveal its willingness to participate in the transmission of the stream. For this reason, the inflow device and the relay device need to be aware of where the potential outflow device is or how to obtain information about the outflow device.
Further, the inflow device transmits a reservation signal to the outflow device in order to perform the above-mentioned approval control to execute the resource reservation.
AVB reservation protocols are generally higher-level, such as RSVP (Resource Reservation Protocol), UPnP-AV (Universal Plug and Play-Audio / Video), or UPnP-QoS (Universal Plug and Play-Quality of Service). Since it is initiated by the application, it needs a way for the interface between the AVB Reservation Protocol and higher level applications.
FIG. 1 is a diagram for explaining a general state of an AVB system using the AVB reservation protocol according to the prior art.
As described above, the AVB reservation protocol is a two-layer reservation protocol initiated by the application 101 in the upper layer. At this time, the AVB reservation protocol can set the filtering database 103 having the group MAC address 102 as a two-layer stream identifier.
The current AVB reservation protocol requires that both the outflow device 104 and the inflow device 105 recognize the AVB stream identifier, which is a two-layer reservation protocol. Such AVB stream identifiers are format compatible with current bridge forwarding mechanisms to enable effective data forwarding, and therefore use 48-bit MAC addresses as described above.
The AVB stream identifier is generally assigned by the inflow device 105 and is known to the outflow device 104. However, the AVB reservation protocol is not involved in the transmission of the AVB stream identifier between such outflow devices 104 and inflow devices 105 and is carried out by the higher layer application 101 that initiates the AVB reservation protocol.
As described above, in the prior art, the transmission of the information associated with the AVB stream identifier between the inflow device and the outflow device is performed by the already standardized upper layer application, and therefore cannot be easily confirmed. For example, RSVP causes the AVB reservation protocol to be executed while reserving a resource in the IP hierarchy, and reserves the corresponding resource in the hierarchy associated with the AVB reservation protocol. However, RSVP does not have the property of transmitting information associated with the AVB stream identifier between the outflow device and the inflow device. That is, as described above, there is a problem that the AVB stream identifier assigned by the inflow device cannot be transmitted to the outflow device.
To solve this, it is possible to add a new signal to the AVB reservation protocol to convey the AVB stream identifier of the inflow device to the outflow device, but this adds overhead to the signal to be added and delays in stream establishment. There is a problem of bringing it.
<p> The present invention has been devised to solve the above-mentioned problems of the prior art, and proposes a new technique relating to an AVB system and a resource reservation method using an extended AVB (Audio / Video bridging) reservation protocol.</p><p> An object of the present invention is to carry out the resource registration and reservation process using the application stream identifier of a higher-level application even when the outflow device cannot recognize the AVB stream identifier.</p><p> Another object of the present invention is to carry out the registration and resource reservation process in one round trip even when the outflow device cannot recognize the AVB stream identifier.</p><p> Yet another object of the present invention is to reduce signal overhead and delay and improve performance via an AVB reservation protocol that uses a standard service interface with no additional requirements or extensions to the higher layer applications.</p>
<p> In order to achieve the above object and solve the above-mentioned problems of the prior art, an AVB system using an extended AVB reservation protocol according to an embodiment of the present invention includes a GARP (AVB stream identifier) including an application stream identifier or an AVB stream identifier. An egress device that sends a Generic Attribute Registration Protocol message to a relay device, and an ingress device that registers the AVB stream identifier or the application stream identifier according to the GARP message and injects a GARP message containing the application stream identifier. Includes a relay device for transmission to the relay device and an inflow device for assigning an AVB stream identifier corresponding to the application stream identifier via the GARP message including the application stream identifier and transmitting a reservation signal to the relay device.</p><p> Further, according to one aspect of the present invention, the relay device extracts and registers the AVB stream identifier or the application stream identifier from the GARP message, and when the GARP message includes the application stream identifier, the GARP The message can be transmitted to the inflow device.</p><p> Further, according to another aspect of the present invention, the reserved signal may include the application stream identifier and the AVB stream identifier corresponding to the application stream identifier.</p><p> Further, according to still another aspect of the present invention, the relay device maps the AVB stream identifier and the application stream identifier based on the reserved signal received from the inflow device, and causes the reserved signal to flow out. Can be sent to the device.</p><p> Further, in another aspect of the present invention, the resource reservation method using the extended AVB (Audio / Video bridging) reservation protocol relays a GARP message including an application stream identifier when the outflow device does not include an AVB stream identifier. A step of registering the application stream identifier included in the GARP message received by the relay device and transmitting the GARP message to the inflow device, and an AVB stream corresponding to the application stream identifier in the inflow device. The step of assigning an identifier to generate a reserved signal and transmitting it to the relay device, and the relay device mapping the application stream identifier and the AVB stream identifier using the reserved signal, and transmitting the reserved signal to the outflow device. Including the stage of transmission and.</p>
<p> According to the present invention, even if the outflow device cannot recognize the AVB stream identifier, the resource registration and reservation process can be performed using the application stream identifier of the application in the upper layer.</p><p> Further, according to the present invention, even when the outflow device cannot recognize the AVB stream identifier, the registration and the resource reservation process can be performed in one round trip.</p><p> Further, according to the present invention, signal overhead and delay can be suppressed and performance can be improved via an AVB reservation protocol using a standard service interface with no additional requirements or extensions to the higher layer application.</p>
Hereinafter, various embodiments according to the present invention will be described in detail with reference to the accompanying drawings.
The present invention, as described above, is to establish the current AVB reservation protocol and enable an interface between the AVB reservation protocol and higher level applications without any additional modifications.
When the outflow device or inflow device, which is the essence of the AVB reservation protocol, is executed in the upper layer application, the upper layer application may provide an application stream identifier corresponding to the upper layer application. For example, "Session object" in RSVP (Resource Reservation Protocol), "Connection ID" in UPnP-AV (Universal Plug and Play-Audio / Video), or UPnP-QoS (Universal Plug and Play-). There is a "Traffic Identifier" in Quality of Service.
However, the format of such an identifier is generally different from the AVB stream identifier for the AVB reservation protocol and is not suitable for the purpose of hierarchical data forwarding using the AVB reservation protocol. Therefore, a one-to-one mapping relationship between the AVB stream identifier and the application stream identifier is required.
FIG. 2 is a diagram for explaining a general state of the AVB system using the extended AVB reservation protocol.
If the spill device 201 recognizes the AVB stream identifier 202, it can perform the resource registration and reservation process as described in FIG. However, if the outflow device 201 cannot recognize the AVB stream identifier 202, the application stream identifier 204 may be provided to the outflow device 201 when the AVB reservation protocol is started by the application 203 in the upper layer.
Such an outflow device 201 generates a GARP (Generic Attribute Registration Protocol) message including an application stream identifier 204 and sends it to the inflow device 205. At this time, the relay device 206 first receives the above. The application stream identifier 204 included in the GARP message is registered, and the GARP message is transmitted to the inflow device 205.
Upon receiving the GARP message, the inflow device 205 assigns the corresponding AVB stream identifier 202 via the application stream identifier 204 included in the GARP message, generates a reserved signal including the AVB stream identifier 202 and the application stream identifier 204, and flows out. Send to device 201.
The relay device 206 maps the AVB stream identifier 202 to the application stream identifier 204 registered by receiving the reservation signal, and transmits the reservation signal to the outflow device 201.
The outflow device 201 can recognize that the resource registration and reservation have been completed by receiving the reservation signal. That is, the process for the registration and the resource reservation can be performed with only one round trip. Further, since the outflow device 201 has received the AVB stream identifier 202, the next time the resource registration and reservation is performed, the process for the registration and the resource reservation is directly performed via the AVB stream identifier 202. Can be carried out.
In addition to this, since the relay device 206 also contains the information mapped between the application stream identifier 204 and the AVB stream identifier 202, the application stream identifier 204 for the same higher-level application transmitted from another outflow device is used. Can directly provide the AVB stream identifier 202 to the other outflow device using the mapped information. This can reduce the overhead on the signal.
FIG. 3 is a block diagram for explaining the internal configuration of the AVB system using the extended AVB reservation protocol in one embodiment of the present invention. As shown in FIG. 3, the AVB system 300 includes an outflow device 301, a relay device 302 and an inflow device 303.
The spill device 301 sends a GARP message containing the application stream identifier or the AVB stream identifier to the relay device 302. The GARP message as described above may be generated by including the AVB stream identifier, or may be generated by including the application stream identifier when the outflow device does not include the AVB stream identifier.
That is, as described above, when the outflow device 301 cannot recognize the AVB stream identifier, the application stream identifier can be confirmed from the application in the upper layer, and the application stream identifier can be included in the GARP message and transmitted. ..
In addition, the GARP message may include attribute type information indicating whether to use the AVB stream identifier or the application stream identifier.
The relay device 302 registers the AVB stream identifier or the application stream identifier according to the GARP message, and transmits the GARP message including the application stream identifier to the inflow device 303. At this time, the relay device 302 extracts and registers the AVB stream identifier or the application stream identifier from the GARP message, and if the GARP message includes the application stream identifier, the relay device 302 sends the GARP message to the inflow device 303. Can be sent.
Further, the application stream identifier corresponds to a higher-level application that starts the AVB reservation protocol, and when the relay device 302 registers the application stream identifier as described above, the relay device 302 adds the registration information of the application stream identifier to the registration information. Register by including the application type for the upper layer application. Such an application type can subsequently facilitate a search for matching the AVB stream identifier and the application stream identifier with each other.
The inflow device 303 assigns an AVB stream identifier corresponding to the application stream identifier via the GARP message including the application stream identifier, and transmits a reservation signal to the relay device 302. At this time, the reserved signal includes the application stream identifier and the AVB stream identifier corresponding to the application stream identifier.
Further, the relay device 302 can map the AVB stream identifier and the application stream identifier based on the reserved signal received from the inflow device 303, and transmit the reserved signal to the outflow device 301.
In this way, the outflow device 301 that has received the reserved signal from the relay device 302 can map the AVB stream identifier and the application stream identifier based on the reserved signal.
If the relay device and the outflow device include the AVB stream identifier, the process for registering and reserving resources can be performed using only the AVB stream identifier. Through this, the AVB system 300 will not only be able to reduce the overhead due to the signal, but will also be able to use streams with even less delay than the "out-of-band query-and-answer" mechanism.
FIG. 4 is an example for explaining the flow of messages between the outflow device, the relay device, and the inflow device.
If the outflow device 401 cannot recognize the AVB stream identifier (stage 401), it acquires the application stream identifier from the application in the upper layer and generates a GARP message 404 containing the application stream identifier (192.168.1.2:7000). And sends it to the inflow device 402.
At this time, the relay device 403 existing between the outflow device 401 and the inflow device 402 receives the GARP message 404, registers the application stream identifier included in the GARP message 404 (step 402), and transmits it to the inflow device 402. To do.
The inflow device 402 assigns the corresponding AVB stream identifier to the application stream identifier of the received GARP message 404 (step 403), generates a reserved signal 405 including the application stream identifier and the AVB stream identifier, and relays the device. Send to 403.
Upon receiving such a reservation signal 405, the relay device 403 maps the AVB stream identifier included in the reservation signal 405 to the registered application stream identifier (step 404), and transmits the reservation signal 405 to the outflow device 401. To do.
Upon receiving the reservation signal 405 on the outflow device 401, the entire process for registering and reserving the resource is completed. After that, in the outflow device 401, the AVB stream identifier included in the reserved signal 405 can be used (step 405), and as described with reference to FIG. 1 via the GARP message 406 including the AVB stream identifier. In addition, the resource registration and reservation process of the AVB stream identifier will be performed.
FIG. 5 is an example for explaining a message flow in resource registration and reservation using a relay device including a mapped AVB stream identifier and an application stream identifier.
When the spill device 501 cannot recognize the AVB stream identifier (step 501), the spill device 501 acquires the application stream identifier from the application in the upper layer and includes the application stream identifier as described in FIG. Generate GARP message 502 and send it to the inflow device.
At this time, if a relay device 403 including the mapped AVB stream identifier and the application stream identifier exists between the outflow device 501 and the inflow device as described in FIG. 4 (step 502), the relay device 403 Generates a reservation signal 503 including the AVB stream identifier and the application stream identifier and transmits it to the outflow device 501.
Through this, the outflow device 501 can use the AVB stream identifier (step 503), resources can be registered and reserved using the GARP 504 including the AVB stream identifier, and signal overhead and stream. The delay for establishment can be suppressed.
That is, according to the present invention, even if the outflow device cannot recognize the AVB stream identifier, the resource registration and reservation process can be performed using the application stream identifier of the application in the upper layer, and once. It is also possible to carry out the registration and reservation process of the resource in a round trip.
In addition, signal overhead and delay can be suppressed and performance can be improved via an AVB reservation protocol that uses a standard service interface with no additional requirements or extensions to the higher layer applications.
FIG. 6 is a flowchart for explaining a resource reservation method using the extended AVB reservation protocol in another embodiment of the present invention.
In step 601 the spill device checks to see if it contains the AVB stream identifier, performs step 602 if it does not contain the AVB stream identifier, and performs step 607 if it contains the AVB stream identifier. To do.
At step 602, the spill device sends a GARP message containing the application stream identifier to the relay device. At this time, in step 602, the outflow device confirms the application stream identifier from the application in the upper layer that starts the AVB reservation protocol, generates a GARP message including the application stream identifier, and transmits it to the relay device. Or something.
In step 603, the relay device registers the application stream identifier included in the received GARP message and transmits the GARP message to the inflow device. At this time, the application stream identifier corresponds to the application of the upper layer that starts the AVB reservation protocol, or when the application stream identifier is registered, the application type for the application of the upper layer is added to the registration information of the application stream identifier. Or register including.
In step 604, the inflow device assigns an AVB stream identifier corresponding to the application stream identifier to generate a reservation signal and transmits it to the relay device. That is, the inflow device that starts the approval control process is started by the application of the upper layer, and at that time, the AVB stream identifier is assigned. The reserved signal also includes the application stream identifier and the AVB stream identifier corresponding to the application stream identifier.
In step 605, the relay device maps the application stream identifier and the AVB stream identifier using the reserved signal and transmits the reserved signal to the outflow device.
In step 606, the spill device maps the AVB stream identifier and the application stream identifier based on the reserved signal received from the relay device. Thus, through steps 601 to 606, the unloader completes the resource registration and reservation process, and the AVB stream identifier can be used for subsequent registration and reservation for new streams.
Further, when the relay device and the outflow device that map the AVB stream identifier and the application stream identifier include the AVB stream identifier, the AVB stream identifier is used in order to suppress the overhead for the signal and the delay for establishing the stream. Perform the process for resource registration and reservation using only.
In step 607, if the spill device includes the AVB stream identifier, it sends a GARP message containing the AVB stream identifier to the relay device.
In step 608, the relay device registers the AVB stream identifier if the received GARP message contains an AVB stream identifier.
Since the stages of stage 607, stage 608, and stages after stage 608 are the same as those described in FIG. 1, the stages after stage 608 are omitted.
In this way, even if the outflow device cannot recognize the AVB stream identifier, the resource registration and reservation process can be performed using the application stream identifier of the application in the upper layer, or the registration and the above can be performed with only one round trip. It can carry out the resource reservation process.
In addition, signal overhead and delay can be suppressed and performance can be improved via an AVB reservation protocol that uses a standard service interface with no additional requirements or extensions to the higher layer applications.
An embodiment of the present invention includes a computer-readable medium containing program instructions for performing various operations embodied by a computer. The medium may also include program instructions, data files, data structures, etc., alone or in combination. The media and program instructions may be specially designed and configured for the purposes of the present invention, or may be known and usable by those skilled in the art of computer software. Examples of computer-readable recording media include optical media such as hard disks, floppy (registered trademark) disks and magnetic tapes, optical media such as CD-ROMs and DVDs, and floppy disks. Magnetic-optical media such as floptical disks media), and hardware devices specially configured to store and execute program instructions such as ROM, RAM, flash memory, etc. The medium is also a transmission medium such as an optical or metal wire containing a carrier wave or a waveguide that transmits a signal for storing a program instruction, a data structure, or the like. Examples of program instructions include not only machine language code such as those generated by a compiler, but also high-level language code executed by a computer using an interpreter or the like. The hardware elements described above are configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.
The description of a particular embodiment of the invention is provided for purposes of illustration. These do not cover or limit the invention to the exact form disclosed, and it is clear that many modifications and modifications are possible in light of the above.
Therefore, the scope of the present invention must be defined by the scope of claims and their equivalents attached to the specification.
Although the present invention has been described by an embodiment of the present invention with reference to the accompanying drawings, the present invention does not depart from the scope of the idea of the present invention and is intended for those who have ordinary knowledge in the field to which the present invention belongs. Is not limited to embodiments of the present invention, as it can be substituted, modified and modified in a variety of ways.
<figref num="1">It is a figure for demonstrating the general appearance of the AVB system using the AVB reservation protocol in the prior art.</figref><figref num="2">It is a figure for demonstrating the general appearance of the AVB system using the extended AVB reservation protocol.</figref><figref num="3">It is a block diagram for demonstrating the internal structure of the AVB system using the extended AVB reservation protocol in one Embodiment of this invention.</figref><figref num="4">This is an example for explaining the flow of messages between the outflow device, the relay device, and the inflow device.</figref><figref num="5">This is an example for explaining the flow of messages in resource registration and reservation using a relay device including a mapped AVB stream identifier and an application stream identifier.</figref><figref num="6">It is a flowchart for demonstrating the resource reservation method using the extended AVB reservation protocol in another embodiment of this invention.</figref>
Code description
300 AVB system 301 Spill device 302 Relay device 303 Inflow device
6 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| JP11234286A | Cites | Japan |
| JP2003298593A | Cites | Japan |
6 members in 3 offices
Priority claims5
| Document | Office | Kind | Date |
|---|---|---|---|
| 1020060111713 | Republic of Korea | – | |
| 20060111713 | Republic of Korea | A | |
| 20060111713 | Republic of Korea | A | |
| 20062006111713 | – | – | – |
| KR20060111713 | – | – | – |
Members6
| Document | Office | Kind | |
|---|---|---|---|
| US2008112433A1 | United States of America | A1 | |
| KR20080043100A | Republic of Korea | A | |
| JP2008125042A | Japan | A | |
| JP4355000B2This record | Japan | B2 | |
| KR101181100B1 | Republic of Korea | B1 | |
| US8446909B2 | United States of America | B2 |
18 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Cancellation because of no payment of annual feesLAPS | LAPS | |
| 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 | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| 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 | |
| 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 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 |
Numbers
- Publication
- 4355000
- Publication, DOCDB
- 4355000
- Publication, EPODOC
- JP4355000B
- Application
- 4774
- Application, DOCDB
- 2007004774
- Application, EPODOC
- JP20070004774
Titles2
- Japanese
- 拡張したAVB予約プロトコル
- English
- Extended AVB reservation protocol
Classification
- CPC, 3
- H04L12/66
- H04L9/40
- H04L12/28
- IPC, 3
- H04L13 08
- H04L12 56
- H04L47 724
