1、ETSI TR 102 163 1.1.1 (2002-12) Technical Repor Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Prof i le Imp lemen tat i on G u ide 2 ETSI TR 102 163 V1.l.l (2002-12) Reference DTRIBRAN-0020009 Keywords access, HIPERLAN, LAN, profile, protocol, radio ETSI 650 Route des Lucioles F-O6921 Sop
2、hia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 O0 Fax: +33 4 93 65 47 16 Siret No 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-prfecture de Grasse (06) No 7803/88 Important notice Individual copies of the present document can be downloaded from: http:lwmv.etsi .ar
3、q 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 Format (PDF). In case of dispute, the reference shall be the printing on ETS
4、I 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 status of this and other ETSI documents is available at ha p:/pa rta I. e
5、tsi I a rgltbistat uslstatus .as p If you find errors in the present document, send your comment to: Cori vriaht Notifica tion No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. O European Telecommuni
6、cations Standards Institute 2002. All rights reserved. DECTTM, PLUGTESTSTMand UMTSTMare Trade Marks of ETSI registered for the benefit of its Members. TIPHONTM and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI regist
7、ered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI 3 ETSI TR 102 163 V1.l.l (2002-12) Contents Intellectual Property Rights 4 Foreword . 4 Introduction 4 1 2 3 3.1 3.2 4 5 5.1 5.2 6 6.1 6.2 7 Scope 5 References 5 Definitions and abbreviations . 5 Definitions . . 5 Abbr
8、eviations . 6 Overview 6 Existing Profiles . 6 Business Profile . . 6 Home Profile . . 6 Usage 7 Device Association . 7 Allo wed Scenarios . . 9 Interoperability . 9 Annex A: Existing Profiles 10 History 12 ETSI 4 ETSI TR 102 163 V1.l.l (2002-12) Intellectual Property Rights IPRs essential or potent
9、ially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (7PRs); Essential, orpotentially Essential, I
10、PRs notlJied to ETSI in respect ofETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (5). All published ETSI deliverables shall include information which directs the reader to the above source of information. Foreword This Technical Rep
11、ort (TR) has been produced by ETSI Project Broadband Radio Access Networks (BRAN). I n t rod uct ion The term “Profile“ describes a list of mandatory features for a certain class of H/2 devices. E.g. a H/2 device supporting the “Home Profile“ has to support SSCS 1394, Direct Link, and a certain auth
12、entication mode. The Profile-Id is used to negotiate a set of features instead of negotiating each feature for itself. This approach avoids the time-consuming negotiation of each feature during association and hand-over. Each H/2 device which claims to support a certain Profile has to support the ma
13、ndatory features of the basic DLC and the mandatory features of the Profile which are stated in the appropriate document. ETSI 5 ETSI TR 102 163 V1.l.l (2002-12) 1 Scope The present document describes the Profile mechanism of HIPERLAN/2 i. 2 Re fe re nces For the purposes of this Technical Report (T
14、R) the following references apply: il ETSI TR 101 683: “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; System Overview“. 21 ETSI TS 101 493 (all parts): “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Packet based Convergence Layer“. ETSI TS 101 761-1: “Broadband Radio Access Net
15、works (BRAN); HIPERLAN Type 2; Data Link Control (DLC) Layer; Part 1 : Basic Data Transport Functions“. ETSI TS 101 761-2: “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Data Link Control (DLC) Layer; Part 2: Radio Link Control (RLC) sublayer“. ETSI TS 101 761-3: “Broadband Radio Access N
16、etworks (BRAN); HIPERLAN Type 2; Data Link Control (DLC) Layer; Part 3: Profile for Business Environment“. ETSI TS 101 761-5: “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Data Link Control (DLC) Layer; Part 5: Profile for Home Environment“. IETF RFC 2734: “IPv4 over IEEE 1394“. IETF RFC
17、 3 146: “Transmission of IPv6 Packets over IEEE 1394 Networks“. 31 41 51 61 71 SI 3 Definitions and abbreviations 3.1 De fi nit ions For the purposes of the present document, the following terms and definitions apply: Access Point (AP): device that is responsible for the centralized control of the r
18、esources in a radio cell NOTE: It is usually connected to a fixed network. Central Controller (CC): provides control functionality equivalent to that of an access point in TS 101 761-1 and TS 101 761-2 but is not necessarily attached to a fixed network Mobile Terminal (MT): device that communicates
19、with an access point or with each other via a radio link NOTE: It is typically a user terminal. Profile: selecting functions from the H/2 basic specifications NOTE: The Profile id and the Profile version number is negotiated during association and handover. Wireless Terminal (WT): H/2 home device, w
20、hich is able to associate with a CC and to communicate with the CC in the control plane and with other H/2 home devices in the user and control planes ETSI 6 ETSI TR 102 163 V1.l.l (2002-12) 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AP BRAN cc CL
21、DLC ETSI H/2 IEEE IETF MT RFC RLC sscs WT Access Point Broadband Radio Access Networks Central Controller Convergence Layer Data Link Control European Telecommunication Standard Institute HIPERLANI2 Institute of Electrical and Electronics Engineers, Inc. Internet Engineering Task Force Mobile Termin
22、al Request For Comments Radio Link Control Service Specific Convergence Sublayer Wireless Terminal 4 Overview The present document describes the use of Profiles within the H/2 standard, which were introduced in TS 101 761-2 4. A Profile specifies the operating environment (business environment, home
23、 environment), possible convergence layers and other application-specific features. Certain Profiles are defined for different operating environments. A Profile selects a set of features which are optional in the basic specification and make them mandatory for all devices supporting the specific Pro
24、file. Profiles are used to simplisl the negotiation of supported features when a device tries to associate to an H/2 network. All Profiles and the associated Profile-Ids and Profile-Versions are listed in annex B of the present document. 5 5.1 Existing Profiles Bu si ness Prof i I e The “Business Pr
25、ofile“ describes an infiastructure-based H/2 network with a dedicated AP which is also connected to the core network. The list of features which have to be implemented is specified in TS 101 761-3 5. 5.2 Home Profile The “Home Profile“ describes an adhoc H/2 network targeting audiohide0 applications
26、. The list of features which have to be implemented is specified in TS 101 761-5 6. For Internet Protocol (IP) data there are 2 options: IpOver1394 specification by IETF RFC 2734 7, IETF RFC 3146 SI on top of 1394 SSCS 2. Ethernet SSCS 2 in addition to 1394 SSCS. ETSI 7 ETSI TR 102 163 V1.l.l (2002-
27、12) 6 6.1 Usage Devi ce Association The Profiles supported by an H/2 network are announced by the AP/CC using the RLC-RBCH-ASSOCIATION message. This information is received by each MT/WT. If at least one of the announced Profiles matches a Profile supported by the device, association can be requeste
28、d. The association is requested by the MT/WT by sending an RLC-MAC-ID-ASSIGN message to the AP/CC. If there is no matching Profile, the device may still associate with the H/2 network. The AP/CC decides if the MT can associate or not. NOTE 1 : Each MT/WT may support several Profiles but shall use on
29、ly 1 Profile at a time. NOTE 2: Each AP/CC may support several Profiles. Several Profiles may be used within one H/2 network. During the association phase, the Profiles used between AP/CC and MT/WT are negotiated by using the RLC-LINK-CAPABILITY message exchange. Details on the association phase are
30、 described in 5 (see also TS 101 761-2 4). Supported Profiles: Supported Profiles: Supported Profiles: + Announcing profiles: A, I? + Requesting Association: I Profile A Confiing Association: Profile A Supported Profiles: Supported Profiles: Supported Profiles: Figure 1: Device association successfu
31、l If the Profile-Id of the MT/WT does not match the Profile-id of the AP/CC, and the MT/WT does not detect a better-suited network, the MT/WT tries to associate to the AP/CC. The AP/CC then decides during association if the MT/WT is associated or not. This decision is vendor-specific and depends on
32、the contents of the RLC-LINK-CAPABILITY message, e.g. the CL-Ids, but also depends on security considerations, etc. ETSI 8 ETSI TR 102 163 V1.l.l (2002-12) CCIAP Supported Profiles: i.$ CCIAP CCIAP Supported Profiles: Supported Profiles: w A Supported Profiles: + Announcing profile: 34 v Supported P
33、rofiles: - v Figure 2: Device association not guaranteed f 3 / WTIMT WTNT Supported Profiles: Supported Profiles: a A L J ETSI T WTIMT Supported Profiles: B J J 9 ETSI TR 102 163 V1.l.l (2002-12) 6.2 Al lowed Scenarios The first matching Profile which is sent in RLC-LINK-CAPABILITY message by the MT
34、/WT shall be used as operating Profile. Multiple Profiles can be used within one W2 network. Supported Profile: A, B Supported Profile: 13, A Supported Profiles: A, R Supported Profile: h Supported Profile: B Figure 3: Profile A and B is supported by APICC Supported Profile: A, B Supported Profile:
35、B, h Supported Profile: A ., May associate if matching CL ”. . 1 MTIWT Supported Profile: A I 1 MTIWT Supported Profile: B I Figure 4: Only Profile A is supported by APICC NOTE: (Only for Home Environment): If the CC detects that a device is not able to associate because of a missing Profile, it may
36、 introduce a cc-handover to a better suited cc-capable device. 7 I nteroperability Interoperability is granted only within one Profile. If Profile Ids do not match a device may not work within the network. ETSI 10 ETSI TR 102 163 V1.l.l (2002-12) Name Business Profile Home Profile Annex A: Profile I
37、d Version Reference Description 1 1 TS 101 761-3 Initial version of the Business Profile 2 1 TS 101 761-5 Initial version of the Home Profile (Ethernet CL, infrastructure-based) Existing Profiles l(1394 CL, adhoc, direct link) ETSI 11 ETSI TR 102 163 V1.l.l (2002-12) List of figures Figure : Device association successful . 7 Figure : Device association not guaranteed 8 Figure 3: Profile A and B is supported by APKC . 9 Figure 4: Only Profile A is supported by APKC . 9 ETSI 12 ETSI TR 102 163 V1.l.l (2002-12) vl.l.l History December 2002 Publication ETSI
