1、ETSI TS I01 493-4 1.1.1 (2001-07) Technical Specification Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Packet based Convergence Layer; Part 4: IEEE 1394 Bridge Specific Functions sub-layer for restricted topology 2 ETSI TS 101 493-4V1.1.1 (2001-07) Reference DTSIBRAN-0024004-4 Keywords b
2、roadband, radio, HIPERLAN, access ETSI 650 Route des Lucioles F-O6921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 O0 Fax: +33 4 93 65 47 16 Siret No 348 623 562 O0017 - NAF 742 C Association but non lucratif enregistre la Sous-prfecture de Grasse (06) No 7803/88 Important notice Individual
3、copies of the present document can be downloaded from: htt!x/w.ettlsi. orq The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document For
4、mat (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current
5、status of this and other ETSI documents is available at If you find errors in the present document, send your comment to: ed itor.etsi .fr Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction i
6、n all media. O European Telecommunications Standards Institute 2001. All rights reserved. ETSI 3 ETSI TS 101 493-4 VI . 1 . 1 (2001-07) Contents Intellectual Property Rights 5 Foreword 5 1 Scope 6 2 References 6 3 Definitions and abbreviations 7 3.1 Definitions 7 3.2 Abbreviations 9 4 Overview 9 4.1
7、 The HL2 1394 Bridge layer . 9 4.2 4.3 4.4 4.4.1 Global node IDS . 12 4.4.2 Bus Resetmet Reset . 12 4.4.3 Remote time-out 13 4.4.4 Stream operations 13 Bridge portal configuration ROM 13 Leaf bus bridge portal configuration ROM . 13 1394 bus bridge model 11 1394 Leaf-bus bridge model 11 Bridged netw
8、ork model (informative) 12 5 Bridge facilities 13 5.1 5.1.1 5.1.1.1 Bus information block 13 5.1.1.2 Bus-Dependent-Info entry . 13 5.1.1.3 Bridge-Capabilities entry 14 5.1.1.5 Bridge-Revision entry 15 Branch bus bridge portal configuration ROM . 15 Bus information block 15 HL2 Bus-dependent-Info ent
9、ry 15 5.1.2.3 Bridge-Capabilities entry 16 5.1.2.4 Bridge-Revision entry 16 Stream routing tables . 17 Cycle master adjustment packet . 18 Bridge management messages encapsulation 18 Global node IDs 18 5.1.1.4 5.1.2 5.1.2.1 5.1.2.2 HL2 Unit directory entry . 14 5.2 Bridge portal control and status r
10、egisters (CSRs) 17 5.3 5.3.1 Stream routing tables 17 5.4 Packet formats of Self-ID packet zero 17 5.5 5.6 Response packet 18 5.7 6 6.1 Global node ID allocation 18 6.1.1 Bus ID . 18 6.1.2 Virtual ID 18 6.1.2.1 6.1.2.2 6.1.2.3 6.2 7 8 Branch bus virtual ID allocation 18 Leaf bus virtual ID allocatio
11、n (Informative) 19 Virtual ID recycling (nonnative) . 19 Global node ID operation 19 Bus ID assignment Essential, orpotentially Essential, IPRs notjed to ETSI in respect OfETSIstandards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (htt:/!wvw.ets
12、i ordj r). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR O00 3 14 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to
13、 the present document. Foreword This Technical Specification (TS) has been produced by ETSI Project Broadband Radio Access Networks (BRAN). The present document is part 4 of a multi-part deliverable covering the Packet based Convergence Layer of HIPERLAN/2, as identified below: Part 1 : “Common Part
14、“; Part 2: Part 3: Part 4: Part 5: “Ethernet Service Specific Convergence Sublayer (SSCS)“; “IEEE 1394 Service Specific Convergence Sublayer (SSCS)“; “IEEE 1394 Bridge Specific Functions sub-layer for restricted topology“; “IEEE 1394 Bridge Specific Functions sub-layer for unrestricted topology“. Pa
15、rt 1, Common Part 4, describes the functionality for adapting variable length packets/frames to the fixed size used in the Data Link Control (DLC) layer. Further parts, each defining a Service Specific Convergence Sublayer (SSCS), describe the functionality required to support a certain protocol, e.
16、g. IEEE 1394 or Ethernet. The 1394 SSCSs all use the services of the Common Part 4 and the DLC 5. It is envisioned that several, independent, service specific parts will be defined in the hture as market requirements develop. ETSI 6 ETSI TS 101 493-4V1.1.1 (2001-07) 1 Scope The present document is a
17、pplicable to HIgh PErformance Radio Local Area Network Type 2 (HIPERLAN/2) equipment supporting interworking with 1394 buses. It defines the functionality required for interworking HIPERLAN/2 with IEEE 1394 buses and defines how to transfer IEEE 1394 packets over the radio interface. The present doc
18、ument specifies the 1394 leaf bus bridge functions required to transfer IEEE 1394 traffic between IEEE 1394 devices over HIPERLAN/2 wireless bridge devices. It does not address the requirements and technical characteristics for wired network interfaces at the HIPERLAN/2 device. The present document
19、uses the services provided by the Packet based convergence layer part 1 (common part, TS 101 493-1 4), part 3 (IEEE 1394 Service Specific Convergence Sub-layer, TS 101 493-3 3), and the data link control layer of HIPERLAN/2 (TS 101 761-1 5). The present document does not address the requirements and
20、 technical characteristics for conformance testing. These are covered by separate documents. 2 Re fe re nces The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publicat
21、ion andor edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. il Pl 31 IEEE Std 1394-1995: “IEEE Standard for a High Performance Serial Bus“. IEEE Std 1394a-2000: “IEEE Standard for
22、a High Performance Serial Bus-Amendment 1“. ETSI TS 101 493-3: “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Packet based convergence layer; Part 3: IEEE 1394 Service Specific Convergence Sublayer (SSCS)“. ETSI TS 101 493-1: “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Packe
23、t based Convergence Layer; Part 1 : Common Part“. ETSI TS 101 761-1: “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Data Link Control (DLC) Layer; Part 1: Basic Data Transport Functions“. ETSI Technical Working Procedures (“itto:,il this is the case when a transaction request or response
24、is echoed to the local bus. global node ID: 16-bit number that uniquely identifies a node in a net. It consists of a 1 O-bit bus ID and a 6 bit virtual ID IEC 61883: Refers to IEC 61883 SI. IEEE 1394: Refers to the IEEE Std 1394-1995 High Performance Serial Bus standard i as amended by IEEE Std 1394
25、a-2000 2, and supplemented with IEC 61883 SI. IEEE 1394.1: Refers to the IEEE Std 1394.1 High Performance Serial Bus Bridges draft standard 7. HIPERLAN/2: HIgh PErformance Radio Local Area Network Type 2, a short-range wireless LAN providing broadband local access standardized by ETSI Project BRAN H
26、L2 1394 bridge layer: Refers to the HIPERLAN 2 IEEE 1394 bridge functions sub-layer, as defined in the present document. HL2 Bus: virtual 1394 bus that is realized on a HL2 wireless network ETSI 8 ETSI TS 101 493-4V1.1.1 (2001-07) isochronous period: period that begins when a cycle start packet is s
27、ent and ends when a subaction gap is detected NOTE 5: During an isochronous period, only isochronous subactions may occur. An isochronous period begins, on average, every 125 ps. isochronous resource manager: node that is the depository of stream resource information on a bus NOTE 6: On a 1394 bus,
28、its roles are specified in IEEE 1394. On a HL2 bus, its roles are specified in the 1394 SSCS 3. isochronous subaction: within the isochronous period, either a concatenated packet or a packet and the gap that precedes it listener: application at a node that receives a stream packet local node: Serial
29、 Bus node is local with respect to another node if they are both connected to the same bus NOTE 7: This is true whether the bus does not yet have a unique bus-lD and is addressable only as the local bus, Ox3FF, or if he bus has been enumerated and assigned a bus-lD. local node ID: 16-bit number that
30、 identifies a node on a local bus NOTE 8: It consists of the 10-bit local bus ID, i.e., 3FF, and the 6-bit physical ID. net: collection of Serial Buses, joined by Serial Bus bridges NOTE 9: Each bus within the net is uniquely identified by its bus-lD. net cycle master: singular node in a net that ac
31、ts as the origin of the clock synchronization throughout the net node: device that may be addressed independently of other nodes NOTE 10:A minimal node consists of only a PHY without an enabled link. If the link and other layers are present and enabled, they are considered part of the node. physical
32、 ID: 6-bit number assigned to each node by the self-identification process that follows a bus reset (see IEEE 1394) portal: part of a Serial Bus bridge that resides on a local bus and uniquely addressable in a net NOTE 1l:Each portal presents a full set of Serial Bus CSRs, as defined in IEEE 1394 an
33、d in this document, to the connected bus. They may be multiple PHY ports for each portal. prime portal: singular portal within a net that manages assignment of bus IDS and their distribution remote node: Serial Bus node is remote with respect to another node if the nodes are connected to buses that
34、have different bus-lD s or if one or more Serial Bus bridges lie on the path between the two nodes unrestricted 1394 bridge: Serial Bus bridge capable of supporting any net topology up to 1 022 buses virtual ID: 6-bit number that is assigned by a bridge portal to each node present on the portals loc
35、al bus NOTE 12:Unlike physical IDS, virtual IDS are stable across bus resets. All the bridge portals on a bus share the same mapping from 6-bit physical ID to virtual ID. wireless 1394: Refers to a HL2 Bus as specified in 3. wireless bridge: bridge which a least one of its portals resides on a wirel
36、ess network ETSI 9 ETSI TS 101 493-4 VI .I .I (2001-07) 3.2 Ab brevi at ions For the purposes of the present document, the following abbreviations apply: BRAN CIP CL CSR ETSI HL2 IEEE IRM self-ID sscs SPH Broadband Radio Access Networks (Project) Common Isochronous Packet Convergence Layer Control a
37、nd Status Register European Telecommunications Standards Institute HiPERLAN/2 Institute of Electrical and Electronics Engineers Isochronous Resource Manager Self Identi Service Specific Convergence Sub-layer Source Packet Header 4 4.1 Overview The HL2 1394 Bridge layer The HL2 1394 bridge layer is t
38、he part 4 of the Packet based Convergence Layer. It resides on top of the 1394 SSCS, as shown in figure 1. Higher layers n- CL User SAP I Packet based Convergence Layer Pari 4: 1394 Bridge Functions Sub-layer Pari 3: IEEE 1394 Service Specific Convergence Sublayer Part 1: Common Part Figure 1: IEEE
39、1394 packet based convergence layer ETSI 10 ETSI TS 101 493-4V1.1.1 (2001-07) The net topology when applied to HIPERLAN/2 is shown in figure 2. The HIPERLAN/2 network appears as a wired-1394 bus for all the attached nodes. This bus is called a HIPERLAN2 Bus, which is often abbreviated as HL2 Bus. Re
40、garding the HL2 Bus, all wireless nodes are peers (there is no particular base station). The aim of the HL2 1394 bridge layer is to interconnect a IEEE 1394 bus and a HL2 bus. The HL2 1394 bridge layer is present in wireless bridge devices, whose architecture is described in figure 3. A A IEEE1394 B
41、us Figure 2: HL2 Bus connecting bridge and non-bridge 1394 devices Wireless Bridge Y Internal Fabric for Asynchronous Packets , I IEEE 1394 PHY I Figure 3: 1394 Wireless Bridge Model ETSI 11 ETSI TS 101 493-4V1.1.1 (2001-07) 4.2 1394 bus bridge model The purpose of the 1394 bus bridge is to solve th
42、e following issues in a single bus network. A 1394 bus bridge provides: expansion of the number of the nodes supported in a net. An IEEE 1394 bus can support up to 63 nodes. A net that contains bridges can support a significantly larger number of nodes; increase of usable bandwidth in a net. Bandwid
43、th is a shared resource on a single bus. Bandwidth needs to be allocated only on the route between the talker and the listener, and it does not require any resources in the other part of the net; improvement of stability of a net associated with bus resets. Bridge isolate local bus resets from the r
44、est of a net; 0 improvement of arbitration efficiency in a local bus by limiting the number of nodes (hops) on it. In addition, a 1394 bridge to a HL2 bus removes physical limitations of cables, and provides mobility and ease of installation. A 1394 bus bridge as many other bridges operates at the D
45、ata Link layer level: it filters out traffic so that only the relevant traffic is forwarded from one bus to another. This allows an efficient bandwidth usage on both sides of the bridge. Moreover a 1394 bus bridge also filters out bus reset, to avoid reset storms on the network. A bridge portal is a
46、 node with a dedicated EUI-64 address and its own address space on the bus to which it is connected. A bridge portal is thus compliant with IEEE 1394. It therefore responds to serial bus read, write and lock transactions as described in IEEE 1394. It recognizes new primary packet fields as described
47、 in IEEE Std 1394.1 7. A bridge portal also forwards asynchronous and isochronous packets to its Co-portal via its internal fabric according to its routing rules as described fkther in the present document. The internal fabric allows bus packets transfer from one portal to its Co-portal. The interna
48、l fabric also contains facilities to transmit the cycle clock from one portal to its Co-portal. The details of the internal fabric are out of the scope of the present document. 4.3 1394 Leaf-bus bridge model The present document focuses on the definition of a leaf bus bridge, which is a restricted t
49、opology bridge. Its functions are significantly simplified compared to that of an unrestricted 1394 bridge by imposing a constraint on the network topology. The HL2 bus is defined as a branch bus to which only leaf-bus bridges can be connected as shown in figure 4 (limited to the maximum of two bus hops). Part 5 of the Packet Based Convergence Layer (see Bibliography) will address the HL2 unrestricted topology 1394 bridge in a backward compatibility manner: leaf-bus bridges function as bus bridges in a self-sufficient manner in the absence of
