Abstract

Maintenance update. Supporting ETSI member Organisations; Siemens, Alcatel, Ascom, Philips.

Status
Published
Publication Date
30-Nov-2003
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Dec-2003
Due Date
01-Dec-2003
Completion Date
01-Dec-2003

Buy Documents

Standard

SIST EN 300 175-4 V1.5.1:2003

English language (151 pages)
Preview
Preview
e-Library read for
×1 day

SIST EN 300 175-4 V1.5.1:2003 is a SIST publication of the ETSI DECT Common Interface, Part 4, for the Data Link Control (DLC) layer. It specifies how DECT carries control-plane signalling and user-plane data across the DLC layer, including framing, link control, procedures, primitives and management for fixed radio terminations, portable radio terminations and interworking units.

What does SIST EN 300 175-4 V1.5.1:2003 specify?

SIST EN 300 175-4 V1.5.1:2003 specifies the DECT Common Interface DLC layer as layer 2b of the DECT protocol stack. It is organized around two independent planes - the Control plane (C-plane) and the User plane (U-plane) - and it defines the services, frame formats, fields, procedures and management needed to move data across those planes.

The document is structured into:

  • an overview of the DLC layer and its two planes,
  • C-plane service characteristics and peer-to-peer procedures,
  • U-plane service characteristics and peer-to-peer procedures,
  • primitives to the MAC layer, NWK layer and interworking unit,
  • management procedures,
  • annexes for parameters, checksum algorithms, MAC connection states and channel-rate mapping.
AnnexWhat it covers
Annex ASystem parameters, including timer values and constants
Annex BChecksum algorithms
Annex CMAC connection states
Annex DMapping of agreed channel rates to MCS sizes
Annex EBibliography

What are the key requirements of SIST EN 300 175-4 V1.5.1:2003?

SIST EN 300 175-4 V1.5.1:2003 defines how DECT DLC links are built, identified and controlled. The most important points are the separation of C-plane and U-plane operation, the classes of link operation, the frame coding rules, the checksum and the procedures for establishing, maintaining, suspending and releasing links.

C-plane and U-plane are separate services

Clause 4 splits DLC into the C-plane for DECT signalling and the U-plane for end-to-end user information. In practice, this means signalling traffic and user traffic are handled by different service paths and can be designed, tested and managed separately.

C-plane uses three classes of operation

Clause 5 defines class U, class A and class B for the C-plane data link service. Class U is unacknowledged, class A is acknowledged single-frame operation, and class B is acknowledged multiple-frame operation. For implementers, this determines whether retransmission, acknowledgements and windowing are used.

Link identity is explicit and preserved

Clause 5 introduces the Data Link Identifier (DLI) and the LAPC states. A DLI stays constant for the whole data link, including handovers, and class B uses assigned link identifiers and an assigned link identifier/multiple-frame state. This matters because equipment must preserve the right link identity while links are established, suspended, resumed or handed over.

C-plane frames use length-based delimiting and channel-dependent fragmentation

Clause 6 defines type FA frames with address, control, length indicator, optional extended length indicator, information, fill and checksum fields. The Lc entity fragments frames differently depending on the logical channel: 8-octet fragments for CF/CLF and 5-octet fragments for CS/CLS. In practice, this tells implementers how to pack signalling data into MAC transfers and how to recover frame boundaries reliably.

The length indicator and checksum carry the framing logic

Clause 7 defines the address field, control field, length indicator, fill field and checksum field coding. The M bit marks segmentation of NWK messages, LI gives the information-field length, and the checksum combines an underlying checksum with a link signature. For users of the standard, this is the core of interoperability: both ends must code fields the same way and detect invalid frames consistently.

Link control uses standard command and response frames

Clause 7.11 defines I, RR, RNR, REJ, SABM, DM, UI, DISC and UA frames. These frames support information transfer, acknowledgement, busy indication, re-establishment and release. In practice, they are the mechanism by which a DECT DLC link behaves predictably during normal traffic and error recovery.

The U-plane is a family of optional services

Clause 4.3 and clauses 11 to 14 define LU services such as TRUP, FREL, FSWI, FEC, BRAT, SRAT, 64 kbit/s data bearer services, RAVE, EFREL and ESC. The standard also defines transmission classes for U-plane peer-to-peer operation. This lets an implementer choose the service that matches the application, from low-delay speech-related transport to more protected or adapted data transport.

What terms does SIST EN 300 175-4 V1.5.1:2003 define?

  • LAPC - the DLC layer C-plane protocol entity that provides the link-access functions for C-plane operation.
  • Lc - the lower DLC C-plane entity that buffers, fragments and routes frames to and from the MAC layer.
  • Lb - the C-plane broadcast entity that provides point-to-multipoint broadcast from FT to PT.
  • DLI - the Data Link Identifier that uniquely identifies each LAPC instance within the FT and PT context.
  • LLN - the Logical Link Number used to identify the LAPC entity associated with a frame.
  • LLME - the Lower Layer Management Entity that coordinates routing and MAC connection control.
  • TRUP - Transparent UnProtected service, one of the defined U-plane services.
  • FREL - Frame RELay service, a U-plane service with framing and checksum functions.

Who uses SIST EN 300 175-4 V1.5.1:2003?

SIST EN 300 175-4 V1.5.1:2003 is used by DECT equipment designers, protocol implementers, interoperability testers and system integrators. It is relevant to teams working on fixed radio terminations (FT), portable radio terminations (PT), radio fixed parts (RFP), repeaters, wireless relay stations and interworking units (IWU).

It is also used by quality, conformance and procurement teams that need to verify how a DECT product handles signalling links, broadcast paging, user-data transport, handover, encryption-related control and MAC connection management.

Which standards are used with SIST EN 300 175-4 V1.5.1:2003?

SIST EN 300 175-4 V1.5.1:2003 references the other parts of the DECT Common Interface series for the surrounding protocol layers:

  • EN 300 175-1 for the overall DECT Common Interface concepts and terminology
  • EN 300 175-2 for the Physical Layer (PHL)
  • EN 300 175-3 for the Medium Access Control (MAC) layer
  • EN 300 175-5 for the Network (NWK) layer
  • EN 300 175-8 for speech coding and transmission

It also draws on external references for protocol modelling and framing methods, including ITU-T Q.920, Q.921, V.42, V.110, X.200, X.210 and ISO/IEC 8073.

What does the SIST EN 300 175-4 V1.5.1:2003 document contain?

The document contains frame diagrams, field formats, command/response codings, state descriptions and service primitives for the DLC layer. It gives the detailed structure of C-plane frames, broadcast frames, U-plane frames and their peer-to-peer procedures.

It also includes primitive tables for service access points to the NWK layer, the MAC layer and the interworking unit, which is useful when mapping protocol rules into software interfaces. The annexes provide timer values, checksum algorithms, MAC connection states and channel-rate mapping, which are the practical reference points used in implementation and testing.

Buy Documents

Standard

SIST EN 300 175-4 V1.5.1:2003

English language (151 pages)
Preview
Preview
e-Library read for
×1 day

Get Certified

Connect with accredited certification bodies for this standard

BSI Group

BSI (British Standards Institution) is the business standards company that helps organizations make excellence a habit.

UKAS United Kingdom Verified

NYCE

Mexican standards and certification body.

EMA Mexico Verified

ANCE

Mexican certification and testing association.

EMA Mexico Verified

Sponsored listings

Frequently Asked Questions

SIST EN 300 175-4 V1.5.1:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 4: Data Link Control (DLC) layer". This standard covers: Maintenance update. Supporting ETSI member Organisations; Siemens, Alcatel, Ascom, Philips.

Maintenance update. Supporting ETSI member Organisations; Siemens, Alcatel, Ascom, Philips.

SIST EN 300 175-4 V1.5.1:2003 is classified under the following ICS (International Classification for Standards) categories: 33.070.30 - Digital Enhanced Cordless Telecommunications (DECT); 35.100.20 - Data link layer. The ICS classification helps identify the subject area and facilitates finding related standards.

SIST EN 300 175-4 V1.5.1:2003 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.

Standards Content (Sample)


2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 4: Data Link Control (DLC) layer35.100.20Podatkovni povezovalni slojData link layer33.070.30'(&7Digital Enhanced Cordless Telecommunications (DECT)ICS:Ta slovenski standard je istoveten z:EN 300 175-4 Version 1.5.1SIST EN 300 175-4 V1.5.1:2003en01-december-2003SIST EN 300 175-4 V1.5.1:2003SLOVENSKI
STANDARD
ETSIEN300175-4V1.5.1(2001-02)EuropeanStandard(Telecommunicationsseries)DigitalEnhancedCordlessTelecommunications(DECT);CommonInterface(CI);Part4:DataLinkControl(DLC)layerSIST EN 300 175-4 V1.5.1:2003

ETSIETSIEN300175-4V1.5.1(2001-02)2ReferenceREN/DECT-000157-4KeywordsDECT,radioETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:+33492944200Fax:+33493654716SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88ImportantnoticeIndividualcopiesofthepresentdocumentcanbedownloadedfrom:http://www.etsi.orgThepresentdocumentmaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.Usersofthepresentdocumentshouldbeawarethatthedocumentmaybesubjecttorevisionorchangeofstatus.InformationonthecurrentstatusofthisandotherETSIdocumentsisavailableathttp://www.etsi.org/tb/status/Ifyoufinderrorsinthepresentdocument,sendyourcommentto:editor@etsi.frCopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2001.Allrightsreserved.SIST EN 300 175-4 V1.5.1:2003

ETSIETSIEN300175-4V1.5.1(2001-02)3ContentsIntellectualPropertyRights.11Foreword.111Scope.122References.123Definitionsandabbreviations.133.1Definitions.133.2Abbreviations.144DataLinkControl(DLC)layeroverview.154.1General.154.2C-Planeservices.164.3U-planeservices.174.4LowerLayerManagementEntity(LLME).195C-planeservicecharacteristics.195.1Datalinkservice(LAPC+Lc).195.1.1General.195.1.2LAPCtypesofoperation.205.1.3Establishmentofinformationtransfermodes.205.1.3.1DataLinkIdentifier(DLI).205.1.3.2LAPCstates.205.2Broadcastservice(Lb).216FramestructuresforC-planeservices.226.1Datalinkserviceframestructure.226.1.1Generalframestructure.226.1.2Lcframedelimitingandtransparency.236.1.3Transmissionorder.236.1.4Routingtologicalchannels.236.1.4.1CF/CLFlogicalchannel.246.1.4.2CS/CLSlogicalchannel.246.1.5Invalidframes.256.2Broadcastserviceframestructure.256.2.1Standardframestructure.256.2.2Extendedframestructure.267ElementsofproceduresandformatsoffieldsforC-planepeer-to-peercommunication.267.1General.267.2Addressfieldformats.267.3Addressfieldparameters.277.3.1REServedbit(RES).277.3.2CommandResponse(C/R)bit.277.3.3SAPIfield.277.3.4NewLinkFlag(NLF)bit.277.3.5LLN-field.277.3.6DataLinkIdentifiers(DLI).287.4Controlfieldformats.287.5Controlfieldparameters.297.5.1Poll/Final(P/F)bit.297.5.2Multipleframeoperationvariablesandsequencenumbers.297.5.2.1Modulus.297.5.2.2SendstateVariableV(S).297.5.2.3AcknowledgestateVariableV(A).297.5.2.4SendsequenceNumberN(S).297.5.2.5ReceivestateVariableV(R).30SIST EN 300 175-4 V1.5.1:2003

ETSIETSIEN300175-4V1.5.1(2001-02)47.5.2.6ReceivesequenceNumberN(R).307.5.3Unacknowledgedoperationvariablesandsequencenumbers.307.5.4SupervisoryandUnnumberedfunctionbitsSandU.307.6Lengthindicatorfieldformat.307.7Lengthindicatorfieldparameters.307.7.1Lengthindicatorfieldextensionbit;N.307.7.2Moredatabit;M.317.7.3Lengthparameter;LI.317.7.4Extendedlengthparameter;LJJ.327.7.5Reservedbit;RES.327.8Fillfieldformat.327.9Checksumfieldformat.327.10Checksumfieldparameters.327.11Commandsandresponses.347.11.1Information(I)command.347.11.2ReceiveReady(RR)command/response.347.11.3ReceiveNotReady(RNR)command/response.357.11.4REJect(REJ)command/response.357.11.5SetAsynchronousBalancedMode(SABM)command.357.11.6DisconnectMode(DM)response.357.11.7UnnumberedInformation(UI)command.367.11.8DISConnect(DISC)command.367.11.9UnnumberedACK(UA)response.368Primitives.368.1Primitivetypes.368.2PrimitivestotheMAClayer(lowerlayer).368.3PrimitivestotheNWKlayer(higherlayer).378.3.1Parameterdefinitions.378.3.2S-SAPprimitives.388.3.2.1DL_ESTABLISHprimitive.388.3.2.2DL_RELEASEprimitive.398.3.2.3DL_DATAprimitive.398.3.2.4DL_UNIT_DATAprimitive.398.3.2.5DL_SUSPENDprimitive.398.3.2.6DL_RESUMEprimitive.408.3.2.7DL_ENC_KEYprimitive.408.3.2.8DL_ENCRYPTprimitive.408.3.2.9DL_SERVICE_MODprimitive.408.3.3B-SAPprimitives.418.3.3.1DL_BROADCASTprimitive.418.3.3.2DL_EXPEDITEDprimitive.418.4Primitivestotheinterworkingunit.418.4.1Parameterdefinitions.418.4.2LUX-SAPprimitives.428.4.2.1DL_U_DATAprimitive.428.4.2.2DL_U_UNIT_DATAprimitive.428.4.2.3DL_U_ERRORprimitive.429C-planepeer-to-peerprocedures.439.1General.439.2Pointtopointacknowledgedoperation.439.2.1ProcedurefortheuseoftheP/Fbit.439.2.1.1ClassAacknowledgedinformationtransfer.439.2.1.2ClassBacknowledgedinformationtransfer.449.2.2UseofLLN.449.2.2.1ClassAoperation.449.2.2.2ClassBoperation.449.2.3LinkestablishmentandinformationtransferinclassAoperation.449.2.3.1EstablishingclassAoperation.449.2.3.2ClassAacknowledgedinformationtransfer.459.2.3.3TransmissionofclassAI-frames.45SIST EN 300 175-4 V1.5.1:2003

ETSIETSIEN300175-4V1.5.1(2001-02)59.2.3.4ReceptionofclassAI-frames.469.2.3.5Receivingacknowledgements.469.2.3.6Waitingforacknowledgement.479.2.3.7ReleaseofclassAoperation.479.2.3.8Re-establishmentofclassAoperation.479.2.4EstablishingclassBmultipleframeoperation.489.2.4.1Overview.489.2.4.2ClassBmultipleframeestablishmentprocedures.489.2.4.3ClassBLLNassignmentprocedures.499.2.4.3.1PTestablishment.509.2.4.3.2FTestablishment.509.2.5LinkmaintenanceandinformationtransferinclassBmultipleframeoperation.509.2.5.1TransmittingI-frames.519.2.5.2ReceivingI-frames.519.2.5.2.1Pbitsetto1.519.2.5.2.2Pbitsetto0.519.2.5.3Sendingandreceivingacknowledgements.519.2.5.3.1Sendingacknowledgements.519.2.5.3.2Receivingacknowledgements.529.2.5.4ReceivingREJ-frames.529.2.5.5ReceivingRNR-frames.539.2.5.6LAPCownreceiverbusycondition.549.2.5.7Waitingacknowledgement.549.2.5.8Appropriatesupervisoryframe.559.2.6ReleaseofclassBmultipleframeoperation.559.2.7Linksuspensionandresumption.569.2.7.1Linksuspension.569.2.7.1.1ClassBacknowledgedsuspend.569.2.7.1.2Unacknowledgedsuspend.579.2.7.1.2.1ClassA.579.2.7.1.2.2ClassB.579.2.7.1.2.3ClassU.589.2.7.2ClassBlinkresumption.589.2.7.3Connectionhandover.599.2.7.3.1ClassAconnectionhandover.609.2.7.3.2ClassBconnectionhandover.619.2.7.3.3Expiryofconnectionhandovertimer.619.2.8Re-establishmentofclassBmulti-frameoperation.619.2.8.1Criteriaforre-establishment.619.2.8.2Procedure.629.2.9Exceptionhandling.629.2.9.1General.629.2.9.2ClassBexceptionconditionreportingandrecovery.639.2.9.2.1N(S)sequenceerror.639.2.9.2.2N(R)sequenceerror.639.2.9.2.3Timerrecoverycondition.639.2.9.2.4Collisionofidenticaltransmittedandreceivedcommands.639.3Unacknowledgedoperation.649.3.1UseofLLNforunacknowledgedinformationtransfer.649.3.2ClassUlinkestablishment.649.3.3Unacknowledgedinformationtransfer.649.3.3.1Transmissionofunacknowledgedinformation.649.3.3.2Receptionofunacknowledgedinformation.649.3.4Unacknowledgedrelease.649.4Broadcastoperation.659.4.1Normaloperation.659.4.1.1ProcedureintheFixedradioTermination(FT).659.4.1.2ProcedureinthePortableradioTermination(PT).659.4.2Expeditedoperation.659.4.2.1ProcedureintheFixedradioTermination(FT).659.4.2.2ProcedureinthePortableradioTermination(PT).659.5MAClayerinterfaces.66SIST EN 300 175-4 V1.5.1:2003

ETSIETSIEN300175-4V1.5.1(2001-02)69.5.1MC-SAP.669.5.1.1C-planeoverview.669.5.1.2C-planeservicedataprocedures.669.5.1.3U-planeservicedata.679.5.2MB-SAP.679.5.2.1C-planeservicedataprocedures.679.5.2.2U-planeservicedata.689.5.3MA-SAP.689.5.3.1Overview.689.5.3.2Servicedataprocedures.6810Managementprocedures.6810.1LowerLayerManagementEntity(LLME).6810.2MACconnectionmanagement.6910.2.1MACconnectionset-up.6910.2.2MACconnectionrelease.6910.2.3MACconnectionmodification.7010.2.4MACconnectionidentifiers.7010.2.4.1Overview.7010.2.4.2AdvancedMACConnectionIdentifiers(AMCI).7110.2.4.3BasicMACConnectionIdentifiers(BMCI).7110.2.4.4MACConnectionEndpointIdentifier(MCEI).7110.2.5Selectionoflogicalchannel(CSorCF).7210.3DLCC-plane(LAPC)management.7210.3.1Provisionoflinksignature.7210.3.2Routingofconnectionorientedlinks.7310.3.3Routingofconnectionlesslinks.7310.4DLCU-plane(LUX)management.7310.4.1U-planeestablishment.7310.4.2U-planerelease.7310.4.3U-planesuspendandresume.7410.5Connectionhandovermanagement.7410.6Cipheringmanagement.7510.6.1CipheringmanagementincaseswheretheNWKlayerexecutesthecipheringrelatedMMprocedure.7510.6.1.1ProvidingakeytotheMAClayer.7510.6.1.2Startingandstoppingtheciphering.7510.6.1.3Connectionhandover.7510.6.2CipheringmanagementincaseswheretheNWKlayerdoesnotexecutethecipheringrelatedMMprocedure.7511U-planeservicecharacteristics.7611.1General.7611.2LU1TRansparentUnProtectedservice(TRUP).7611.3LU2FrameRELayservice(FREL).7711.3.1General.7711.3.2Checksumoperation.7811.3.3Segmentationandtransmissionclass.7811.3.4Datatransmission.7911.3.4.1Sendsideprocedure.7911.3.4.2Receivesideprocedure.7911.4LU3FrameSWItchingservice(FSWI).7911.5LU4ForwardErrorCorrectionservice(FEC).8011.6LU5BasicRateAdaptionservice(BRAT).8011.6.1Overview.8011.6.2Protectedserviceoperation.8111.6.2.1General.8111.6.2.2Databufferingandinitialrateadaptation.8211.6.2.3Multi-channelsetmultiplexing.8311.6.2.4SegmentationofMultiplexedDataUnits(MDU).8411.6.2.5Framesequencingandadditionofcontrolandfilloctets.8411.6.2.6Frametransmission.8611.6.3Unprotectedserviceoperation.86SIST EN 300 175-4 V1.5.1:2003

ETSIETSIEN300175-4V1.5.1(2001-02)711.6.3.1General.8611.6.3.2Databufferingandinitialrateadaption.8711.6.3.3Multi-channelsetmultiplexing.8711.6.3.4SegmentationofMDUs.8811.6.3.5Frametransmission.8811.7LU6SecondaryRateAdapTion(SRAT)service.8911.7.1General.8911.8LU16ESCapeService(ESC).9011.8.1General.9011.9LU764kbit/sdatabearerservice.9011.9.1General.9011.9.2Physicallayerservice.9011.9.3MAClayerservice.9011.9.4DLClayerservice.9011.9.4.1Architecturalmodel.9011.9.4.1.1Transmit(Tx)framebuffering.9111.9.4.1.2Receive(Rx)framebuffering.9111.9.4.2Automatic-Repeat-Request(ARQ)andForwardErrorControl(FEC).9111.9.4.2.1Controlfield.9311.9.4.2.1.1Formatcontrolparametercoding.9311.9.4.2.1.2OffsetvariableV(O).9311.9.4.2.1.3TimevariablesVn(T).9311.9.4.2.1.4OffsetnumberN(O).9411.9.4.2.1.5SendstatevariableV(S).9411.9.4.2.1.6AcknowledgestatevariableV(A).9411.9.4.2.1.7SendsequencenumberN(S).9411.9.4.2.1.8ReceivestatevariableV(R).9411.9.4.2.1.9ReceivesequencenumberN(R).9511.9.4.2.2Informationfield.9511.9.4.2.3ARQchecksum.9511.9.4.3Proceduresfornormaloperation.9511.9.4.3.1Establishmentandsynchronizationprocedures.9511.9.4.3.2Activephase.9711.9.4.3.2.1Transmittingframes(firsttimetransmission).9711.9.4.3.2.2Re-transmittingframes.9811.9.4.3.2.3Receivingframes.9811.9.4.3.2.4Sendingacknowledgements.9911.9.4.3.2.5Receivingacknowledgements.9911.9.4.3.3Release.9911.9.4.4Exceptionalprocedures.9911.9.4.4.1Invalidframecondition.9911.9.4.4.2Establishment.9911.9.4.4.3Transmittingframes.9911.9.4.4.4Receivingframes.9911.9.4.4.5Sendingacknowledgements.9911.9.4.4.6Forwardingofreceiveddata.10011.9.4.4.7N(R)sequenceerror.10011.9.4.4.8N(O)sequenceerror.10011.9.4.4.9N(S)sequenceerror.10011.9.4.4.10Formaterror.10111.9.4.4.11Abnormalrelease.10111.9.4.4.12Implicitreset.10111.9.5Networklayerservice.10111.9.5.1LCEservice.10111.9.5.2CCservice.10111.10LU8service.10111.10.1Physicallayerservice.10111.10.2MAClayerservice.10111.10.3DLClayerservice.10211.11LU9-UnprotectedRateAdaptionforVseriesEquipment(RAVE)Service.10211.11.1Overview.102SIST EN 300 175-4 V1.5.1:2003

ETSIETSIEN300175-4V1.5.1(2001-02)811.11.1.1FU9framestructure.10311.11.1.1.1Generalframestructure.10311.11.1.1.2FU9bufferingprocedures.10311.11.1.1.3Connectionhandover.10311.11.1.1.4Transmissionorder.10411.11.2Alignmentsignalmanagement.10411.11.2.1General.
...