ETSI TS 102 342-2005 Digital Enhanced Cordless Telecommunications (DECT) Cordless multimedia communication system Open Data Access Profile (ODAP) (V1 2 1)《数字增强无绳通信(DECT) 无绳多媒体通信系统 _1.pdf

《ETSI TS 102 342-2005 Digital Enhanced Cordless Telecommunications (DECT) Cordless multimedia communication system Open Data Access Profile (ODAP) (V1 2 1)《数字增强无绳通信(DECT) 无绳多媒体通信系统 _1.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 102 342-2005 Digital Enhanced Cordless Telecommunications (DECT) Cordless multimedia communication system Open Data Access Profile (ODAP) (V1 2 1)《数字增强无绳通信(DECT) 无绳多媒体通信系统 _1.pdf（58页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 102 342 V1.2.1 (2005-09)Technical Specification Digital Enhanced Cordless Telecommunications (DECT);Cordless multimedia communication system;Open Data Access Profile (ODAP)ETSI ETSI TS 102 342 V1.2.1 (2005-09) 2 Reference RTS/DECT-000242 Keywords data, DECT, interworking, GAP, multimedia ET

2、SI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be

3、downloaded from: http:/www.etsi.org 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 refe

4、rence 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 status of this and other ETSI documents

5、 is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permissi

6、on. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2005. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Mark

7、s currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 102 342 V1.2.1 (2005-09) 3 Contents Intellectual Property Rights6 Foreword.6 1 Scope 7 2 References 7 3

8、Definitions, symbols and abbreviations .8 3.1 Definitions8 3.2 Symbols8 3.3 Abbreviations .9 4 General .10 5 Overview 10 6 Reference configuration .11 6.1 General .11 6.2 Example scenarios13 6.2.1 A sensor application - remote server 13 6.2.2 A fire alarm application - local server 15 7 Interoperabi

9、lity requirements .15 7.1 Feature/service definitions15 7.2 Requirements tables .15 7.2.1 ODAP service provision specific features/procedures16 7.2.2 ODAP service provision general features/services .17 8 Requirements description rules 18 9 DECT protocol elements of procedures .18 9.1 ODAP features/

10、parameters support indication/negotiation 18 9.1.1 General18 9.1.2 ODAP features support indication18 9.1.2.1 FT ODAP features support indication.19 9.1.2.1.1 FT default (mandatory) ODAP support indication19 9.1.2.1.2 FT ODAP Layer 2 protected mode support indication19 9.1.2.2 PT ODAP features suppo

11、rt indication.19 9.1.2.2.1 PT default (mandatory) ODAP support indication20 9.1.2.2.2 PT ODAP Layer 2 protected mode support indication20 9.2 ODAP call setup procedure21 9.2.1 ODAP default call setup .21 9.2.2 ODAP optional call features/parameters negotiation procedure.23 9.3 ODAP PT mode of operat

12、ion .25 9.4 ODAP subscription.26 9.5 ODAP Layer 2 protected mode 26 10 ODAP Data Framer (DF) .26 10.1 ODAP Vs. GAP U-plane requirements 26 10.1.1 Overview in the GAP U-plane requirements 26 10.1.2 Requirements of the utilization of the GAP U-plane for the purposes of the ODAP Data Framer.27 10.2 ODA

13、P Data Framer implementation requirements 28 10.2.1 General28 10.2.2 DFU10 operation requirements.28 11 ODAP media transfer .31 11.1 General .31 11.2 Hyper media transfer basic requirements .32 11.2.1 Messages specification .33 11.2.1.1 Message start-line requirements33 11.2.1.1.1 Request start-line

14、.33 ETSI ETSI TS 102 342 V1.2.1 (2005-09) 4 11.2.1.1.2 Response start-line.33 11.2.1.2 Message header requirements .33 11.2.1.3 Message-body requirements34 11.2.2 Procedures specification .34 11.3 ODAP Streaming media protocol basic requirements34 12 ODAP application communication protocol 35 12.1 A

15、pplication elements of procedures .36 12.1.1 Application procedures .36 12.1.1.1 Register .36 12.1.1.2 Submit .38 12.1.1.2.1 Client initiated submit (PT to FT) .38 12.1.1.2.2 Server initiated submit (FT to PT).38 12.1.1.3 De-register.39 12.1.1.3.1 Client initiated de-register (PT to FT) .39 12.1.1.3

16、.2 Server initiated de-register (FT to PT).39 12.1.1.4 Client configuration 39 12.1.1.5 Client alive indication .40 12.1.1.6 Client/server sleeping mode management.40 12.1.1.7 Timers .41 12.1.2 Application PDUs.41 12.1.2.1 ODAP PDU types .42 12.1.2.2 ODAP version identifier .42 12.1.2.3 Transaction

17、Identifier (TI).43 12.1.2.4 PDUs content description43 12.1.2.4.1 APP-REGISTER-REQUEST 44 12.1.2.4.2 APP-REGISTER-RESPONSE 45 12.1.2.4.3 APP-SUBMIT-REQUEST 46 12.1.2.4.4 APP-SUBMIT-RESPONSE 46 12.1.2.4.5 APP-DEREGISTER-REQUEST.47 12.1.2.4.6 APP-DEREGISTER-RESPONSE.47 12.1.2.5 PDU headers elements 47

18、 12.1.2.5.1 Client identifier47 12.1.2.5.2 Client type .48 12.1.2.5.3 Date .48 12.1.2.5.4 Reject reason code.48 12.1.2.5.5 Reject reason text 48 12.1.2.5.6 Status .49 12.1.2.5.7 To 49 12.1.2.5.8 T_alive.49 12.1.2.5.9 T_sleep 49 12.1.2.5.10 T_awake 49 12.1.2.6 PDU message body elements 50 13 External

19、 PT communication.50 13.1 AT commands 50 Annex A (normative): Alarms and sensors applications 51 A.1 Principles and assumptions 51 A.2 Procedures support requirements .51 A.3 Procedures specification.52 A.3.1 Client initiated procedures52 A.3.1.1 Alarm raise52 A.3.1.2 Alarm clear .52 A.3.1.3 Battery

20、 low indication.52 A.3.1.4 Battery OK indication.53 A.3.1.5 Sensor data send .53 A.3.2 Server initiated procedures.53 A.3.2.1 Reset procedure 53 A.3.2.2 Status request 54 A.3.2.3 Get parameter54 ETSI ETSI TS 102 342 V1.2.1 (2005-09) 5 A.3.2.4 Set parameter 55 A.3.2.5 Trace start .57 A.3.2.6 Trace st

21、op57 History 58 ETSI ETSI TS 102 342 V1.2.1 (2005-09) 6 Intellectual Property Rights IPRs essential or potentially 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

22、 can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pu

23、rsuant 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 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present d

24、ocument. Foreword This Technical Specification (TS) has been produced by ETSI Project Digital Enhanced Cordless Telecommunications (DECT). The present document is based on DECT Common Interface (CI) specification EN 300 175, parts 1 1 to 7 7, to enable DECT terminals to interwork in the public and p

25、rivate environment. In addition, for the purpose of interoperability and wherever it is found appropriate, the present document takes into consideration the requirements of: the DECT Generic Access Profile (GAP), EN 300 444 10 to enable the same DECT portable part (PT) to interwork with a DECT fixed

26、 part (FP) complying to the GAP requirements, irrespective of whether this FP provides residential, business or public access services. General attachment requirements are based on EN 301 406 11. Further details on the DECT system may be found in TR 101 178 9. ETSI ETSI TS 102 342 V1.2.1 (2005-09) 7

27、 1 Scope The present document specifies that set of technical requirements for Digital Enhanced Cordless Telecommunications (DECT) Fixed Part (FP) and DECT Portable Part (PP) necessary for the support the Open Data Access Profile (ODAP). It defines a common architecture and protocol to support home

28、and industrial sensors, alarms, telematics and other Machine-to-Machine (M2M) messages. The present document aims at ensuring low cost terminals and an easy to use application interface. It covers three interfaces: DECT air interface. The client to server ODAP application interface. Tethered PP inte

29、rface to external equipment. 2 References 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 publication and/or edition number or version number) or non-specific. For a

30、 specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. 1 ETSI EN 300 175-1: “Digital Enhanced Cordl

31、ess Telecommunications (DECT); Common Interface (CI); Part 1: Overview“. 2 ETSI EN 300 175-2: “Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 2: Physical Layer (PHL)“. 3 ETSI EN 300 175-3: “Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI);

32、Part 3: Medium Access Control (MAC) layer“. 4 ETSI EN 300 175-4: “Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 4: Data Link Control (DLC) layer“. 5 ETSI EN 300 175-5: “Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 5: Network (NWK

33、) layer“. 6 ETSI EN 300 175-6: “Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 6: Identities and addressing“. 7 ETSI EN 300 175-7: “Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 7: Security features“. 8 Void. 9 ETSI TR 101 178: “Di

34、gital Enhanced Cordless Telecommunications (DECT); A High Level Guide to the DECT Standardization“. 10 ETSI EN 300 444: “Digital Enhanced Cordless Telecommunications (DECT); Generic Access Profile (GAP)“. 11 ETSI EN 301 406: “Digital Enhanced Cordless Telecommunications (DECT); Harmonized EN for Dig

35、ital Enhanced Cordless Telecommunications (DECT) covering essential requirements under article 3.2 of the R Generic radio“. ETSI ETSI TS 102 342 V1.2.1 (2005-09) 8 12 ETSI EN 301 469: “Digital Enhanced Cordless Telecommunications (DECT); DECT Packet Radio Service (DPRS)“. 13 ETSI TR 102 179: “Digita

36、l Enhanced Cordless Telecommunications (DECT); AT command interface; High-level description“. 14 IETF RFC 2616: “Hypertext Transfer Protocol - HTTP/1.1“. 15 IETF RFC 2822: “Internet Message Format“. 16 IETF RFC 2806: “URLs for Telephone Calls“. 17 ISO/IEC 646: “Information technology - ISO 7-bit cod

37、ed character set for information interchange“. 18 ISO/IEC 8859-1: “Information technology - 8-bit single-byte coded graphic character sets - Part 1: Latin alphabet No. 1“. 19 IETF RFC 1123: “Requirements for Internet Hosts - Application and Support“. 20 IETF RFC 2396: “Uniform Resource Identifiers (

38、URI): Generic Syntax“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in EN 300 175-1 1 and the following apply: HTTP client: program that establishes HTTP connections for the purpose of sending requests HTTP server:

39、 program that accepts HTTP connections in order to service requests by sending back responses NOTE: Any given program may be capable of being both a client and a server; the use of these terms in the present document refers only to the role being performed by the program for a particular connection,

40、 rather than to the programs capabilities in general. ODAP application: implementation dependant entity tailored at the provisioning of reliable communication service NOTE: Can be used by industry specific processes for exchange of information between participants in the process and which uses an OD

41、AP bearer for the exchange of information with another ODAP application. ODAP bearer: protected, up to 28 Kbps, data transport service utilizing the 3,1 kHz teleservice specified in GAP, EN 300 444 10 ODAP client: type of ODAP application that offers direct service to an industry specific device NOT

42、E: E.g. alarm, sensor, controller, etc. for wireless exchange of information with an ODAP server. ODAP server: type of ODAP application that controls one or more ODAP clients NOTE: May provide means for informing a user for the behaviour of the devices served by the ODAP clients and allow actions to

43、 be taken upon. 3.2 Symbols For the purposes of the present document, the following symbols apply: M mandatory to support (provision mandatory, process mandatory) O optional to support (provision optional, process mandatory) I out-of-scope (provision optional, process optional) not subject for testi

44、ng C conditional to support (process mandatory) N/A not applicable (in the given context the specification makes it impossible to use this capability) ETSI ETSI TS 102 342 V1.2.1 (2005-09) 9 Provision mandatory, process mandatory means that the indicated feature service or procedure shall be impleme

45、nted as described in the present document, and may be subject to testing. Provision optional, process mandatory means that the indicated feature, service or procedure may be implemented, and if implemented, the feature, service or procedure shall be implemented as described in the present document,

46、and may be subject to testing. 3.3 Abbreviations For the purposes of the present document, the following abbreviations apply: A/N Acknowledged/Not acknowledged AC Access Code ACK ACKnowledge CA Client Application CC Call Control CI Common Interface CMC Cordless Multimedia Communication C-plane Contr

47、ol plane CRC Cyclic Redundancy Check CShigher layer signalling Channel (slow) DCK Derived Cipher Key DECT Digital Enhanced Cordless Telecommunications DF Data Framer DLC Data Link Control DPRS DECT Packet Radio Service EN European Norm ES End SystemFBNFrame Buffer (uNprotected) FP Fixed PartFR Frame

48、 Relay F-SMS Fixed line Short Message Service FT Fixed Termination GAP Generic Access Profile HTTP HyperText Transfer Protocol ID IDentity IETF Internet Engineering Task Force INhigher layer Information channel (uNprotected), (logical channels to the MAC layer) IPhigher layer Information channel (Pr

49、otected), (logical channels to the MAC layer) IP Internet Protocol IPUI International Portable User Identity IWU Inter Working Unit LAN Local Area NetworkLAPC a DLC layer C-plane protocol entity Lb a DLC layer C-plane protocol entity Lc a DLC layer C-plane protocol entity LI Length Indicator LRMS Low Rate Messaging Service LU1 LAP-U service 1 M2M Machine-to-Machine MAC Medium Access Control MM Mobility Management NWK NetWorK ODAP Open Data Access Profile PBX Private Branch eXchange PDU Protocol Data Unit PP Po