ETSI ETS 300 435 ed.1 (1996-02)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digital Enhanced Cordless Telecommunications (DECT); Data Services Profile (DSP); Base standard including interworking to connectionless networks (service types A and B, class 1)33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)33.070.30'(&7Digital Enhanced Cordless Telecommunications (DECT)ICS:Ta slovenski standard je istoveten z:ETS 300 435 E13SIST ETS 300 435:1999en01-MDQXDU19993SIST ETS 300 435:1999SLOVENSKI
STANDARD
EUROPEANETS 300 435TELECOMMUNICATIONFebruary 1996STANDARDSource: ETSI TC-RESReference: DE/RES-03031ICS:30.020, 30.060.50Key words:DECT, profile, data, LANRadio Equipment and Systems (RES);Digital European Cordless Telecommunications (DECT);Data Services Profile (DSP);Base standard including inter-Working to connectionlessnetworks (service types A and B, Class 1)ETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1996. All rights reserved.SIST ETS 300 435:1999*

Page 2ETS 300 435: February 1996Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.SIST ETS 300 435:1999

Page 3ETS 300 435: February 1996ContentsForeword.51Scope.72Normative references.73Definitions and abbreviations.83.1Definitions.83.2Abbreviations.94Description of services.104.1Reference configuration.104.2Service objectives.115PHL layer requirements.116MAC layer requirements.117DLC layer requirements.118NWK layer requirements.119Management entity requirements.1210Generic frame relay service inter-Working conventions.1211Configuration capabilities.12Annex A (normative):Implementation of the SIP protected data connectionless downlink service.14Annex B (normative):InterWorking conventions to specific networks.15B.1ISO 8802.3 (Ethernet).15B.1.1Reference configuration.15B.1.2Specific inter-Working conventions.15B.2ISO 8802.5 (token ring).16B.2.1Reference configuration.16B.2.2Specific inter-Working conventions.16Annex C (normative):Service A: FT Profile ICS Proforma.18C.1 Standardised symbols for the status column.18C.2Capabilities.18C.2.1Services.18C.2.2Service parameters.19C.2.3Protocol parameters.19C.2.4Messages.20C.2.5Message parameters.23C.2.6Functions implemented.24C.2.7Timer support.25C.2.8Procedure support.26Annex D (normative):Service A: PT Profile ICS Proforma.28SIST ETS 300 435:1999

Page 4ETS 300 435: February 1996D.1 Standardised symbols for the status column.28D.2Capabilities.28D.2.1Services.28D.2.2Service parameters.29D.2.3Protocol parameters.29D.2.4Messages.30D.2.5Message parameters.33D.2.6Functions implemented.34D.2.7Timer support.35D.2.8Procedure support.36Annex E (normative):Service B: FT Profile ICS Proforma.38E.1Standardised symbols for the status column.38E.2Capabilities.38E.2.1Services.38E.2.2Service parameters.39E.2.3Protocol parameters.39E.2.4Messages.40E.2.5Message parameters.43E.2.6Functions implemented.45E.2.7Timer support.46E.2.8Procedure support.46Annex F (normative):Service B: PT Profile ICS Proforma.48F.1Standardised symbols for the status column.48F.2Capabilities.48F.2.1Services.48F.2.2Service parameters.49F.2.3Protocol parameters.49F.2.4Messages.50F.2.5Message parameters.53F.2.6Functions implemented.55F.2.7Timer support.56F.2.8Procedure support.56History.58SIST ETS 300 435:1999

Page 5ETS 300 435: February 1996ForewordThis draft European Telecommunication Standard (ETS) has been produced by the Radio Equipment andSystems (RES) Technical Committee of the European Telecommunications Standards Institute (ETSI).Transposition datesDate of adoption of this ETS:15 December 1995Date of latest announcement of this ETS (doa):31 May 1996Date of latest publication of new National Standardor endorsement of this ETS (dop/e):30 November 1996Date of withdrawal of any conflicting National Standard (dow):30 November 1996SIST ETS 300 435:1999

Page 6ETS 300 435: February 1996Blank pageSIST ETS 300 435:1999

Page 7ETS 300 435: February 19961ScopeThis ETS defines a profile for Digital European Cordless Telecommunications (DECT) systemsconforming to ETS 300 175 [1] to [9]. It is part of a family of profiles that build upon and extend each other,aimed at the general connection of terminals supporting non-voice services to a fixed infra-structure,private and public.This ETS specifies a generic frame relay service for use within closed user groups. This service is used byother Data Services Profile (DSP) standards when providing inter-working to levels above the MediumAccess Control (MAC) layer of the attached network. Annex B contains inter-working conventions tospecific attached data networks. This includes inter-working to the MAC layer of international standardconnectionless Local Area data Networks (LANs).This ETS defines both Type A and Type B services. Type A is optimised for low power and simplicity,while Type B is optimised for high speed and throughput. Both are fully compatible and can inter-work witheach other.This ETS defines the requirements on the Physical (PHL), MAC, Data Link Control (DLC) and Network(NWK) layers of DECT.This ETS also specifies Management Entity (ME) requirements and generic inter-working conventions thatensure the efficient use of the DECT frequency spectrum.2Normative referencesThis ETS incorporates, by dated or undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this ETS only when incorporated in it by amendment or revision. For undated references the latestedition of the publication referred to apply.[1]ETS 300 175-1: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 1:Overview".[2]ETS 300 175-2: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 2: PhysicalLayer (PHL)".[3]ETS 300 175-3: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 3: MediumAccess Control (MAC) layer".[4]ETS 300 175-4: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 4: DataLink Control (DLC) layer".[5]ETS 300 175-5: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI) Part 5: Network(NWK) layer".[6]ETS 300 175-6: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI) Part 6: Identitiesand addressing".[7]ETS 300 175-7: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI) ;Part 7: Securityfeatures".[8]ETS 300 175-8: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 8: Speechcoding and transmission".SIST ETS 300 435:1999

Page 8ETS 300 435: February 1996[9]ETS 300 175-9: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT); Common Interface (CI); Part 9: PublicAccess Profile (PAP)".[10]TBR 006: "Radio Equipment and Systems (RES); Digital European CordlessTelecommunications (DECT), General terminal attachment requirements".[11]I-ETS 300 176: "Radio Equipment and Systems (RES); Digital EuropeanCordless Telecommunications (DECT), Approval test specification".[12]CEPT Recommendation T/SGT SF2 (89) 6/0: "Draft Recommendation T/SFServices and Facilities of Digital European Cordless Telecommunications".[13]ETR 043: "Radio Equipment and Systems (RES); Digital European CordlessTelecommunications (DECT) Common interface. Services and Facilitiesrequirements specification".[14]ETR 015: "Radio Equipment and Systems (RES); Digital European CordlessTelecommunications (DECT); Reference document".[15]ETR 056: "Radio Equipment and Systems (RES); Digital European CordlessTelecommunications (DECT); System description document".[16]ETR 042: "Radio Equipment and Systems (RES); Digital European CordlessTelecommunications (DECT); A guide to the DECT features that influence thetraffic capacity and the maintenance of high radio link transmission quality,including the results of simulations".[17]ISO 8802: "Information processing - Local Area Networks".3Definitions and abbreviations3.1DefinitionsFor the purposes of this ETS, the following definitions apply.Access Rights Identity (ARI): A globally unique identity that shows the access rights related to a serviceprovider. The ARI consists of an Access Rights Class (ARC) and Access Rights Details (ARD). There arethree categories of ARIs:-Primary ARI (PARI);-Secondary ARI (SARI);-Tertiary ARI (TARI).kbyte: 1 000 bytes.kbyte: 1 024 bytes.mobility class 1: Local area applications, for which terminals are pre-registered off-air with one or morespecific fixed parts, and establishment of service and user parameters is therefore implicit, according to aprofile-defined list.multiframe: A repeating sequence of 16 successive TDMA frames, that allows low rate or sporadicinformation to be multiplexed (e.g. basic system information or paging).service type A: Low speed frame relay, with a net sustainable throughput of up to 24 kbits/s, optimisedfor burst data, low power consumption and low complexity applications such as hand-portable equipment.SIST ETS 300 435:1999

Page 9ETS 300 435: February 1996service type B: High performance frame relay, with a net sustainable throughput of up to 552 kbits/s,optimised for high speed and low latency with burst data. Equipment implementation the Type B profileshall inter-operate with Type A equipment.Time Division Multiple Access (TDMA) frame: A time-division multiplex of 10 ms duration, containing24 successive full slots. A TDMA frame starts with the first bit period of full slot 0 and ends with the last bitperiod of full slot 23.3.2AbbreviationsFor the purposes of this ETS, the following abbreviations apply:ARCAccess Rights ClassARDAccess Rights DetailsARIAccess Rights IdentityBsslow Broadcast channelChigher layer control Channel (see CS and CF)CBCConnectionless Bearer ControlCFhigher layer signalling Channel (fast)C/LConnectionLessCLhigher layer ConnectionLess channel (protected; see CLS and CLF)CLFhigher layer ConnectionLess channel (fast)CLShigher layer ConnectionLess channel (slow)C/OConnection OrientedC-planeControl planeCRCCyclic Redundancy CheckCSMA/CACarrier Sense Multiple Access/Collision AvoidanceCSMA/CDCarrier Sense Multiple Access/Collision DetectionCShigher layer signalling Channel (slow)CUGClosed User GroupDECTDigital European Cordless TelecommunicationsDLCData Link ControlDNWDECT NetWorkE/U-MUXSwitch between E-type and U-type MUltipleXesFCSFrame Check SequenceFDDIFibre Distributed Data InterfaceFMIDFixed part MAC IDentityFPFixed PartFTFixed radio TerminationGFhigher layer information control channelIhigher layer Information channel (see IN and IP)INhigher layer Information channel (unprotected)IPhigher layer Information channel (protected)IPUIInternational Portable User IdentityIWFInterWorking FunctionsIWUInterWorking UnitLANLocal Area data NetworkLBNLogical Bearer NumberLCNLogical Connection Number (DLC/MAC layer)LLNLogical Link Number (DLC layer)LSBLeast Significant BitMMAC control channelMACMedium Access ControlMEManagement EntityMSBMost Significant BitMUXtime MUltipleXorsNidentities channelNOSNetwork Operating SystemOSIOpen Systems InterconnectionPPaging channelPARIPrimary Access Rights IdentityPARKPortable Access Rights KeyPDUProtocol Data UnitSIST ETS 300 435:1999

Page 10ETS 300 435: February 1996PHLPHysical LayerPMIDPortable part MAC IDentityPPPortable PartPTPortable radio TerminationQsystem information channelRFPRadio Fixed PartRFPIRadio Fixed Part IdentitySAPService Access PointSAPIService Access Point IdentifierSARISecondary Access Rights IdentitySDUService Data UnitSINhigher layer connectionless channel (unprotected)SIPhigher layer connectionless channel (protected)TARITertiary Access Rights IdentityT-MUXTail MUXTDDTime Division DuplexTDMATime Division Multiple AccessTPUITemporary Portable User IdentityU-planeUser-planeWANWide Area Network4Description of services4.1Reference configurationThe reference configuration for this profile shall be as shown in figure 1.Interworking Function Application Specific
DECT Layers (optional)DECT
A.1 or B.1 ServiceNetwork Specific
LayersApplication Specific
DECT Layers (optional)Higher
Protocol
LayersHigher
Protocol
LayersNetwork Specific
LayersDECT
A.1 or B.1 ServiceClosed
User Group
Set-up Data Figure 1: Profile reference configuration showing inter-working to a network via the generic framerelay serviceThe profile reference configuration is based upon the following principles:-inter-Working is with an external network via the generic frame relay service (service Type A or B);-inter-Working with the end system network layer or above is not a requirement of this ETS;-the set of supported Portable Parts (PPs) shall constitute a closed user group.SIST ETS 300 435:1999

Page 11ETS 300 435: February 19964.2Service objectivesThe profile has the service objectives given in tables 1 and 2, as outlined in ETR 043 [13].Table 1Offered servicesType AType BPoint-to-point Service Data Unit (SDU)transfer PP-FPYesYesPoint-to-point SDU transfer FP-PPYesYesPoint-to-multipoint SDU transfer FP-PPOptionalOptionalEncryptionOptionalOptionalTable 2PerformanceType AType BMaximum sustainable unidirectionalthroughput3 kbytes/s net24 kbits/s net69 kbytes/s net552 kbits/s netMaximum sustainable full bi-directionalthroughput3 kbytes/s net24 kbits/s net36 kbytes/s net288 kbits/s netEstablishment of PT to FT link(average)< 50 ms average< 50 ms averageEstablishment of FT to PT link(average)< 160 ms average< 50 ms averageUndetected bit error ratio< 10-10< 10-10Uncorrected error rate< 10-7< 10-7Maximum supported SDU size:1,5 Kbytes1,5 Kbytes5PHL layer requirementsFull slots shall be used. The Portable radio Termination (PT) shall be capable of operating on any one,and no more than one, physical channel in each time slot. All Radio Fixed Parts (RFPs) shall be capableof operating on at least any one physical channel in each time slot. Use of the Z-field is not defined by theDSP.6MAC layer requirementsThe minimum instance shall only require the capability to establish and maintain single-bearerconnections. The provisions of ETS 300 175-3 [3] shall be implemented with respect to the services,procedures, messages and information elements coding listed in annexes C to F. The provisions ofETS 300 175-6 [6] shall be implemented with respect to the structure and use of identities.If the Fixed Part (FP) - Portable Part (PP) point-to-multipoint service is implemented the MAC layer shall inaddition implement the protected data connectionless downlink service SIP, as defined in annex A.7DLC layer requirementsThe DLC U-plane shall be LU2 (Class 1), FU6, (see ETS 300 175-4 [4]). No C-plane functionality isrequired for the service Types A and B, mobility Class 1.If the FP-PP point-to-multipoint service is provided the DLC layer shall transmit and receive all FP-PPpoint-to-multipoint SDUs via LU2 (Class 1) and FU6a framing and segmentation and the PPs shall notsend the FU6b acknowledge frames. Such DLC frames shall be transferred via the SIP service.8NWK layer requirementsInter-operability between units shall be independent of NWK layer functionality. No, DECT NWK layerservices are required for service Types A and B, mobility Class 1.SIST ETS 300 435:1999

Page 12ETS 300 435: February 19969Management entity requirementsThe LLME shall ensure that a connection is always released, together with all its bearers, after no greaterthan 5/n seconds, where n = number of bearers, after the last non point-to-multipoint SDU in the IWUbuffer has been successfully transferred. The presence of point-to-multipoint SDUs in a buffer shall byitself neither cause the establishment nor the maintenance of a DECT connection-oriented bearer.In cases where both the PP and the FP are capable of diversity switching, the default operation in theabsence of other user intervention shall be for the FP diversity to remain in operation and for the PP todisable its diversity function.Paging shall always use the default Temporary Portable User Identity (TPUI).Bi-directional links shall be composed of two unidirectional links in opposite directions on the same MACconnection.10Generic frame relay service inter-Working conventionsAll data frames shall always be transmitted as DECT DLC layer SDUs, with the earliest bits transferredfirst in the earliest octet of the earliest U-plane segment.The DECT equipment shall be capable of supporting SDU frames of at least 1,5 Kbytes. The equipmentmay optionally support larger SDUs.Where SDU sizes larger than 1,5 Kbytes are supported by either the FT or the PT the smaller value shallbe used in communications, or if this is not possible, the FT equipment shall not allow PT equipment to beregistered.All point-to-multipoint packets shall be transmitted by the FP over the connectionless downlink, and mayalso be transmitted over previously established connections.The same International Portable User Identity (IPUI) type shall be used within a given local environment.The IPUI values shall be assigned in such a manner so as to ensure each individual IPUI is unique withinall the local environments that support it.11Configuration capabilitiesIn order to assure reliable inter-Working between devices complying with this profile in mobility Class 1, itshall be possible to install the following parameters in the FPs and/or PPs of the system. The values ofparameters referring to the PP shall be clearly indicated in the documentation of the PP, and means shallbe provided in FPs for such values to be registered. The values of parameters referring to the FP shall beclearly indicated in the documentation of the FP, and means shall be provided in PP for such values to beregistered.SIST ETS 300 435:1999

Page 13ETS 300 435: February 1996Table 3Variable parameterValueFixed(F)/Portable(P)Service associated with identityType A or BF, PNetwork associated with identitySelected from annex BF, PIPUIUnique value within localenvironmentPARIUnique value within localenvironmentFMaximum supported SDU sizeNumber of bytesF, PMulti-bearer capability1-23F, PAsymmetric capabilityYes/NoF, PDiversity capabilityYes/NoF, PFast paging availableYes/NoF, PConnectionless downlink supportedYes/NoF, PEncryption capabilityYes/NoF, PStatic cipher key64 bitsF, PA given set of values for the parameters shall be unique for the IPUI with which they are associated.SIST ETS 300 435:1999

Page 14ETS 300 435: February 1996Annex A (normative):Implementation of the SIP protected dataconnectionless downlink serviceThe SIP protected data connectionless downlink service is used by the FP-PP point-to-multipoint serviceto transfer the data frames after the LU2 (Class 1) framing and FU6a segmentation functions have beenperformed on the point-to-multipoint SDU (see clause 7). The SIP service is an application of the DECTMAC SIN service.The SIP service shall code each data frame (which shall be 32 octets long) according to the protected B-field multiplex (as defined in ETS 300 175-3 [3], subclause 6.2.1.3) and transmit the coded data as asingle SDU via the DECT MAC SIN channel.The FP shall only transmit SIP data starting at the start of a paging cycle. A PP shall understand thepresence of SIP data to be indicated by the coding BA = SIN and the PT MAC layer information = Dummyor C/L bearer. The TDMA frame immediately following the frame in which SIP data was received shall alsobe monitored to find out whether it contains SIP data. In this way SIP data shall be understood to bepresent in each subsequent TDMA frame until the BA and MAC layer information codings indicate that theSIP (SIN) data field is no longer present. No further SIP information shall then be available until the start ofthe next paging cycle.The start of a paging cycle in this context shall be that time-slot in frame 0 of a multiframe that is carryingthe start of a paging message. When paging repetition is supported by the fixed part, the number of thismultiframe shall be 0 modulo 4.SIST ETS 300 435:1999

Page 15ETS 300 435: February 1996Annex B (normative):InterWorking conventions to specific networksB.1ISO 8802.3 (Ethernet)The provisions of this clause shall apply if inter-Working to ISO 8802.3 [17] (Ethernet) LANs is provided.B.1.1Reference configurationThe reference configuration for this specific inter-Working convention shall be as shown in figure B.1.Interworking Function DECT
A.1 or B.1
Service OnlyHigher
Protocol
LayersHigher
Protocol
LayersClosed
ISO 8802.x
Physical LayerISO 8802.x
Physical LayerISO 8802.3
MAC Layer ISO 8802.3
MAC Layer DECT
A.1 or B.1
Service OnlyClosed
User Group
Set-up Data Figure B.1: Profile reference configuration showing inter-Working to ISO 8802.3 type LANsThe profile reference configuration is based upon the principles stated in subclause 4.1 and the following:-inter-Working is a bridging function with a network conforming to the ISO 8802.3 [17] standard.B.1.2Specific inter-Working conventionsThe conditions of clause 10 shall be adhered to in addition to the following.The ISO 8802.3 [17] MAC frame shall be transmitted as a single DECT DLC layer SDU beginning with theISO 8802.3 [17] MAC Destination Address and ending with the MAC Information field. For MAC frameswhich are less than 64 bytes in length, the PAD field shall not be transmitted. This mapping is shown infigure B.2.SIST ETS 300 435:1999

Page 16ETS 300 435: February 1996TimeEarliestLatestPreambleDest. AddrL InformationPAD FCS SFD Src. Addr Dest. AddrL InformationSrc. Addr ISO 8802.3 MAC frameDECT DLC SDUFigure B.2: Mapping of ISO 8802.3 MAC frames into DECT DLC SDUIPUIs of type O shall be used. The full ISO 8802.3 MAC address shall be mapped into the type O. IPUIwith the Least Significant Bit (LSB) of the ISO 8802.3 MAC address corresponding to the LSB of the IPUI.The ISO 8802 MAC source address of frames originating from the PP shall always be checked by the FPat the establishment of each connection, and frames originating from unacceptable sources shall causethe connection to be immediately released.B.2ISO 8802.5 (token ring)The provisions of this clause shall apply if inter-Working to ISO 8802.5 (token ring) LANs is provided.B.2.1Reference configurationThe reference configuration for this specific inter-Working convention shall be as shown in figure B.3.Interworking Function DECT
A.1 or B.1
Service OnlyHigher
Protocol
LayersHigher
Protocol
LayersISO 8802.x
Physical LayerISO 8802.x
Physical LayerISO 8802.5
MAC Layer ISO 8802.5
MAC Layer DECT
A.1 or B.1
Service OnlyClosed
User Group
Set-up Data Figure B.3: Profile reference configuration showing inter-Working to ISO 8802.5 type LANsThe profile reference configuration is based upon the principles stated in subclause 4.1 and the following:-inter-Working is a bridging function with a network conforming to the ISO 8802.5 standard.B.2.2Specific inter-Working conventionsAll the conditions of clause 10 shall be adhered to in addition to the following:SIST ETS 300 435:1999

Page 17ETS 300 435: February 1996The ISO 8802.5 MAC frame shall be transmitted as a single DECT DLC layer SDU beginning with the ISO8802.5 MAC Frame Control (FC) field and ending with the MAC Information field. The FP shall not sendthe token ring MAC Control frames as identified by the FC byte and it shall not send the Frame Status(FS) byte. It shall be the responsibility of the FP to inter-work these to the token ring network. Thismapping is shown in figure B.4.TimeEarliestLatestDest. AddrInformationFCS Src. Addr ISO 8802.5 MAC frameDECT DLC SDUSDELEDELRouting FSFCACDest. AddrInformationSrc. Addr Routing FCFigure B.4: Mapping of ISO 8802.4 MAC frames into DECT DLC SDUIPUIs of type O shall be used. The full ISO 8802.5 MAC address shall be mapped into the type O IPUIwith the LSB of the ISO 8802.5 MAC address corresponding to the LSB of the IPUI. The ISO 8802 [17]MAC source address of frames originating from the PP shall always be checked by the fixed part at theestablishment of each connection, and frames originating from unacceptable sources shall cause theconnection to be immediately released.SIST ETS 300 435:1999

Page 18ETS 300 435: February 1996Annex C (normative):Service A: FT Profile ICS ProformaNotwithstanding the provisions of the copyright clause related to the text of this ETS, ETSI grants thatusers of this ETS may freely reproduce the PICS proforma in this annex so that it can be used for itsintended purposes and may further publish the completed PICS.C.1 Standardised symbols for the status columnThe standardised symbols for the status column are as follows:-m or M for mandatory;-o or O for optional (Boolean);-x or X for prohibited use;-n/a, N/A or - (dash) for not applicable;-cn or Cn for conditional on the implementation of feature n;-i or I for out of scope (the capability is allowed to be implemented but is not called upon by theprofile functionality).Where reception of a message is marked as "O", this shall be understood to mean that correctunderstanding and processing of that message is optional.C1: IF Encryption supported THEN M ELSE I.C2: IF Connectionless downlink supported THEN M ELSE I.C3: IF Class 2 mobility supported THEN M ELSE I.Except when stated otherwise, the reference column refers to the relevant subclause inETS 300 175-3 [3].C.2CapabilitiesC.2.1ServicesQ.9Service supportService supportedItem no.Name of serviceRef.StatusSupport1Type 1f IN_minimum delay5.6.2.1I2Type 2f IN_normal delay5.6.2.1I3Type 3f IP_error_detection5.6.2.1I4Type 4f IP_error_correction5.6.2.1M5Type 5 IN_normal delay5.6.2.2I6Type 6 IP_error_detection5.6.2.2I7Type 7f IP_error_correction5.6.2.2I8Type 1h IN_minimum delay5.6.2.1I9Type 2h IN_normal delay5.6.2.1I10Type 3h IP_error_detection5.6.2.1I11Type 4h IP_error_correction5.6.2.1I12CS duplex5.3.1.1C313CF duplex5.3.1.1C314Downlink CLS only5.7.2.1I(continued)SIST ETS 300 435:1999

Page 19ETS 300 435: February 1996Q.9Service support (concluded)Service supportedItem no.Name of serviceRef.StatusSupport15Downlink CLF + CLS5.7.2.1I16Downlink CLS + SIN5.7.2.1C217Uplink CLF only5.7.2.2I18Uplink CLS only5.7.2.2I19Uplink without SDU5.7.2.2I20GF simplex5.3.1.3M21Fast paging11.3.3.1O22Normal paging11.3.3.1M23Low duty cycle paging11.3.3.1O24System identities11.3.2M25System information11.3.2M26Encryption6.2.3C127Fast setup11.3.3.2IC.2.2Service parametersQ.10Service parametersSupported parametersItemno.ParameterRef.StatusSupportValuesAllowedSupported1No. of bearers in T2f service5.6.2.1I2No. of bearers in T3f service5.6.2.1I3No. of bearers in T4f service5.6.2.1M14Forward bearer no. in T5 service5.6.2.2I5Special bearer no. in T5 service5.6.2.2I6Forward bearer no. in T6 service5.6.2.2I7Special bearer no. in T6 service5.6.2.2I8Forward bearer no. in T7 service5.6.2.2I9Special bearer no. in T7 service5.6.2.2IC.2.3Protocol parametersQ.11Protocol parametersProtocol parameters supportedItem no.NameRef.StatusSupportValueAllowedSupported1N20010.2M102N20110.6I3N20211.4M104N2039.2ISIST ETS 300 435:1999

Page 20ETS 300 435: February 1996C.2.4MessagesQ.12Messages in A_tailSupported messagesItemno.NameRef.SendingReceiptStatusSupportStatusSupport1TA code: CT data packet number 07.1.2C3C32TA code: CT data packet number 17.1.2C3C33TA code: identities information on connectionlessbearer7.1.2C2N/A4TA code: identities information7.1.2MM5TA code: multiframe sync. and system information7.1.2MN/A6TA code: main escape7.1.2XI7TA code: MAC layer control7.1.2MM8TA code: paging/first PT transmission7.1.2MM9BA code: U-type, IN, SIN or IP packet number 07.1.4MM10BA code: U-type, IP error detect or IP packetnumber 17.1.4MM11BA code: E-type, all CF or CLF, packet number 07.1.4C3C312BA code: E-type, all CF, packet number 17.1.4C3C313BA code: E-type, not all CF or CLF; CF packetnumber 07.1.4C3C314BA code: E-type, not all CF; CF packet number 17.1.4C3C315BA code: E-type, all MAC control7.1.4MM16BA code: no B_field7.1.4ON/A17NT information7.2.2MM18Static system information7.2.3.2MN/A19Extended RF carrier information7.2.3.3IN/A20Fixed part capabilities7.2.3.4MN/A21Extended fixed part capabilities7.2.3.5IN/A22SARI message7.2.3.6ON/A23Multi-frame number7.2.3.7C1N/A24Q-channel escape7.2.3.8IN/A25Zero length page indication7.2.4.2.3MN/A26Short page indication7.2.4.2.3MN/A27Full page indication7.2.4.2.3IN/A28Not the last 36 bits of a long page indication7.2.4.2.3IN/A29The first 36 bits of a long page indication7.2.4.2.3IN/A30The last 36 bits of a long page indication7.2.4.2.3IN/A31All of a long page indication7.2.4.2.3IN/A32PT header extend flag7.2.4.2.2MN/A33PT MAC information: fill7.2.4.3.2ON/A34PT MAC information: blind full slot7.2.4.3.3MN/A35PT MAC information: other bearer7.2.4.3.4ON/A36PT MAC information: recommended other bearer7.2.4.3.4ON/A37PT MAC information: good RFP bearer7.2.4.3.4ON/A38PT MAC information: dummy or C/L bearer position7.2.4.3.4MN/A39PT MAC information: RFP identity7.2.4.3.5IN/A40PT MAC information: dummy or C/L bearer marker7.2.4.3.7C2N/A41PT MAC information: escape7.2.4.3.6IN/A42PT MAC information: bearer handover type 00007.2.4.3.8IN/A43PT MAC information: bearer handover type 00017.2.4.3.8IN/A44PT MAC information: bearer handover type 00107.2.4.3.8IN/A45PT MAC information: bearer handover type 00117.2.4.3.8IN/A46Basic access request7.2.5.2N/AI47Basic bearer handover request7.2.5.2N/AI(continued)SIST ETS 300 435:1999

Page 21ETS 300 435: February 1996Q.12Messages in A_tailSupported messagesItemno.NameRef.SendingReceiptStatusSupportStatusSupport48Basic connection handover request7.2.5.2N/AI49Basic unconfirmed access request7.2.5.2N/AI50Basic bearer confirm7.2.5.2IN/A51Basic wait7.2.5.2.3II52Basic bearer release7.2.5.2II53Advanced access request7.2.5.3.2II54Advanced bearer handover request7.2.5.3.3II55Advanced connection handover request7.2.5.3.4II56Advanced bearer confirm7.2.5.3.6II57Advanced unconfirmed access request7.2.5.3.5II58Advanced wait7.2.5.3.7II59Advanced attributes-T request7.2.5.3.8II60Advanced attributes-T confirm7.2.5.3.8II61Advanced bandwidth-T request7.2.5.3.9II62Advanced bandwidth-T confirm7.2.5.3.9II63Advanced channel list7.2.5.3.10II64Advanced unconfirmed dummy7.2.5.3.11II65Advanced unconfirmed handover7.2.5.3.12II66Advanced bearer release7.2.5.3.13II67Transmit on the specified slot/frequency testmessage7.2.5.4.2N/AN/A68Loopback B_field test message7.2.5.4.3N/AM69Defeat antenna diversity test message7.2.5.4.4N/AM70Force bearer handover test message7.2.5.4.5N/AI71Clear test mode test message7.2.5.4.6N/AM72Single bearer antenna switch QC message7.2.5.5OO73All bearer antenna switch QC message7.2.5.5OO74Bearer handover QC message7.2.5.5II75Connection handover QC message7.2.5.5II76Single bearer frequency control QC message7.2.5.5OO77All bearer frequency control QC message7.2.5.5OO78C/L single transmission with 1 CLF segment7.2.5.6II79C/L single transmission with 2 CLF segments7.2.5.6II80C/L single transmission with 3 CLF segments7.2.5.6II81C/L single transmission with 4 CLF segments7.2.5.6II821st C/L half slot transmission with 1 CLF segment7.2.5.6II831st C/L full slot transmission with 4 CLF segment7.2.5.6II842nd C/L transmission with 1 CLF segment7.2.5.6II852nd C/L transmission with 2 CLF segment7.2.5.6II862nd C/L transmission with 3 CLF segment7.2.5.6II872nd C/L transmission with 4 CLF segment7.2.5.6II88C/L single transmission without CLF segment7.2.5.6II891st C/L transmission without CLF segment (CLSservice)7.2.5.6II90Change dummy position7.2.5.6OO91Extended system information7.2.5.6OO92Start encryption: request7.2.5.7N/AC1(continued)SIST ETS 300 435:1999

Page 22ETS 300 435: February 1996Q.12Messages in A_tail (concluded)Supported messages93Start encryption: confirm7.2.5.7C1N/A94Start encryption: grant7.2.5.7N/AC195Stop encryption: reques t7.2.5.7N/AC196Stop encryption: confirm7.2.5.7C1N/A97Stop encryption: grant7.2.5.7N/AC198First transmission for B_field setup7.2.5.8MM99M-channel escape7.2.5.9IIQ.13Messages in B_fieldSupported messagesItemno.NameRef.SendingReceiptStatusSupportStatusSupport1B_field access request7.3.3.2IM2B_field bearer handover request7.3.3.2II3B_field connection handover request7.3.3.2II4B_field unconfirmed access request7.3.3.2II5B_field bearer confirm7.3.3.3MI6B_field wait7.3.3.4MM7B_field attributes-B request7.3.3.5II8B_field attributes-B confirm7.3.3.5II9B_field bandwidth-B request7.3.3.6II10B_field bandwidth-B confirm7.3.3.6II11B_field channel list7.3.3.7II12B_field unconfirmed dummy7.3.3.8II13B_field unconfirmed handover7.3.3.9II14B_field bearer release7.3.3.10MM15B_field null message7.3.4MM16B_field single bearer antenna switch QC message7.3.5.2OO17B_field all bearer antenna switch QC message7.3.5.2OO18B_field bearer handover QC message7.3.5.2II19B_field connection handover QC message7.3.5.2II20B_field single bearer frequency control QCmessage7.3.5.2OO21B_field all bearer frequency control QC message7.3.5.2OO22B-field reset request7.3.5.3MM23B_field reset confirm7.3.5.3MM24MAC-MOD2-ACK message7.3.5.4MM25B-field request for QT field7.3.6.2N/AO26B-field QT field response7.3.6.3ON/A27B_field TARI message7.3.6.4ON/A28B_field GF data7.3.7MM29B_field M-channel escape7.3.8OOSIST ETS 300 435:1999

Page 23ETS 300 435: February 1996C.2.5Message parametersQ.14Parameters of static system information messageSupported parametersItemno.ParameterRef.StatusSupportValuesAllowedSupported1Normal-reverse7.2.3.2.2M02Slot number7.2.3.2.3M0 - 113Start position7.2.3.2.4M04Escape7.2.3.2.5M0 - 15Number of transceivers7.2.3.2.6M0 - 36Extended RF carrier flag7.2.3.2.7M07RF carriers available7.2.3.2.8M1 - 1 0238Spare7.2.3.2.11M09Carrier number7.2.3.2.10M0 - 910Spare7.2.3.2.11M011Primary receiver scan number7.2.3.2.12M0 - 9Q.15Parameters of Fixed Part Capabilities MessageEncryption capabilityItemno.ParameterRef.StatusSupportValuesAllowedSupported1Extended FP information7.2.3.4.2M0, 12Full slot7.2.3.4.2M13Frequency control7.2.3.4.2M0, 14Page repetition7.2.3.4.2M0, 15C/O setup on dummy allowed7.2.3.4.2MC2 = 06C/L uplink7.2.3.4.2M0, 17C/L downlink7.2.3.4.2MC2 = 18Basic A_field setup7.2.3.4.2M0, 19Advanced A_field setup7.2.3.4.2M0, 110B_field setup7.2.3.4.2M111CF messages7.2.3.4.2C30, 112IN_minimum_delay7.2.3.4.2M0, 113IN_normal_delay7.2.3.4.2M0, 114IP_error_detection7.2.3.4.2M0, 115IP_error_correction7.2.3.4.2M116Multibearer connection7.2.3.4.2M0The higher layer information field of the FP capabilities message is out of scope for mobility class 1applications of this profile.SIST ETS 300 435:1999

Page 24ETS 300 435: February 1996Q.20Parameters of B_field access request messageSupported parametersItemno.ParameterRef.StatusSupportValuesAllowedSupported1IBCN7.3.3.2M02Exchanged connection number8.1.1M0 - 153Logical bearer number10.2.4M0 - 154Connection type7.3.3.2M35Service type7.3.3.2M36Maximum life7.3.3.2M0 - 77Slot type7.3.3.2M0Q.24Parameters of B_field bearer confirm messageSupported parametersItemno.ParameterRef.StatusSupportValuesAllowedSupported1Exchanged connection number8.1.1M0 - 152Logical bearer number10.2.4M0 - 153Connection type7.3.3.3M34Service type7.3.3.3M35Maximum life7.3.3.3M0 - 76Slot type7.3.3.3M0Q.32Parameters of B_field bearer release messageSupported parametersItemno.ParameterRef.StatusSupportValuesAllowedSupported1Reason for release7.3.3.10M0-3 and 6-13Q.33Parameters of B_field null messageSupported parametersItemno.ParameterRef.StatusSupportValuesAllowedSupported1CF data indication7.3.4C30-4C.2.6Functions implementedQ.34Function implementedSupported functionsItemno.Function nameRef.StatusSupport1B_field data scrambling6.2.4M2B_field data unscrambling6.2.4M3R-CRC generation6.2.5.2M4R-CRC checking6.2.5.2M(continued)SIST ETS 300 435:1999

Page 25ETS 300 435: February 1996Q.34Function implemented (concluded)Supported functions5X-CRC generation6.2.5.4M6X-CRC checking6.2.5.4O7Z-CRC generationETS 300 175-2 [2]subclause 4.8I8Z-CRC checkingETS 300 175-2 [2]subclause 4.8I9D-MAP D80 field mapping6.2.1.1I10D-MAP D32 field mapping6.2.1.1M11D-MAP D08 field mapping6.2.1.1I12D-MAP D00 field mapping6.2.1.1O13A-MAP A_field mapping6.2.1.2M14E/U-MUX E80 type multiplex6.2.2.2I15E/U-MUX E32 type multiplex6.2.2.2M16E/U-MUX E08 type multiplex6.2.2.2I17E/U-MUX U80a type multiplex6.2.2.2I18E/U-MUX U80b type multiplex6.2.2.2I19E/U-MUX U32a type multiplex6.2.2.2C220E/U-MUX U32b type multiplex6.2.2.2M21E/U-MUX U08a type multiplex6.2.2.2I22E/U-MUX U08b type multiplex6.2.2.2I23C-MUX B_field full slot mode 0 multiplex6.2.2.3.1M24C-MUX B_field full slot mode 1 multiplex6.2.2.3.1C325C-MUX B_field full slot mode 2 multiplex6.2.2.3.1C326C-MUX B_field full slot mode 3 multiplex6.2.2.3.1C327C-MUX B_field full slot mode 4 multiplex6.
...