ETSI TS 101 658 V1.1.1 (1999-04)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Terrestrial Trunked Radio (TETRA); Digital Advanced Wireless Service (DAWS); Logical Link Control (LLC) service description33.070.10Prizemni snopovni radio (TETRA)Terrestrial Trunked Radio (TETRA)ICS:Ta slovenski standard je istoveten z:TS 101 658 Version 1.1.1PSIST TS 101 658:2000en01-julij-2000PSIST TS 101 658:2000SLOVENSKI
STANDARD



PSIST TS 101 658:2000



TS 101 658 V1.1.1 (1999-04)Technical SpecificationTerrestrial Trunked Radio (TETRA);Digital Advanced Wireless Service (DAWS);Logical Link Control (LLC) service descriptionPSIST TS 101 658:2000



ETSITS 101 658 V1.1.1 (1999-04)2ReferenceDTS/TETRA-04033 (fco00icr.PDF)Keywordsdata, TETRAETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88Internetsecretariat@etsi.frIndividual copies of this ETSI deliverablecan be downloaded fromhttp://www.etsi.orgIf you find errors in the present document, send yourcomment to: editor@etsi.frCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1999.All rights reserved.PSIST TS 101 658:2000



ETSITS 101 658 V1.1.1 (1999-04)3ContentsIntellectual Property Rights.5Foreword.51Scope.62References.63Definitions and abbreviations.63.1Definitions.63.2Abbreviations.74Introduction.75Registration Services.85.1Base station registration.85.2Mobile station registration.95.2.1Cell selection.95.2.2Registration.95.2.3Service interruption.95.2.4Intra-network hand-over.105.2.5Inter-network hand-over.105.3De-registration.106Transport Services.116.1Link layer address resolution.116.2Packet classification.116.3Traffic measurement, policing, and shaping.117Admission Control Services.127.1Reservation creation procedure.127.2Reservation deletion procedure.137.3Reservation modification procedure, resource increase.137.4Reservation modification procedure, resource decrease.138Service Primitives.148.1Primitive Definitions.148.1.1LLC_transfer_request.148.1.2LLC_transfer_confirm.148.1.3LLC_transfer_indication.148.1.4LLC_create_protocol_request.158.1.5LLC_create_protocol_confirm.158.1.6LLC_create_protocol_indication.158.1.7LLC_delete_protocol_request.168.1.8LLC_delete_protocol_confirm.168.1.9LLC_delete_protocol_indication.168.1.10LLC_service_indication.168.2Parameter Definitions.178.2.1create_protocol_result.178.2.2delete_protocol_result.178.2.3new_service_state.178.2.4NPDU.178.2.5packet_classification_params.178.2.6protocol_instance_ID.178.2.7protocol_parameters.188.2.8protocol_type.188.2.9service_parameters.188.2.10transfer_receipt_ack.18PSIST TS 101 658:2000



ETSITS 101 658 V1.1.1 (1999-04)4Annex A (informative):The IPv4 to IPv6 Transition.19Bibliography.22History.23PSIST TS 101 658:2000



ETSITS 101 658 V1.1.1 (1999-04)5Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on theETSI Web server (http://www.etsi.org/ipr).Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)which are, or may be, or may become, essential to the present document.ForewordThis Technical Specification (TS) has been produced by ETSI Project Terrestrial Trunked Radio (TETRA).An overview of the requirements for DAWS can be found in TR 101 156.PSIST TS 101 658:2000



ETSITS 101 658 V1.1.1 (1999-04)61ScopeThe present document specifies the service requirements for the Digital Advanced Wireless Service (DAWS) LogicalLink Control (LLC) layer. The present document provides a conceptual architecture useful for specifying requirementsbut is not intended to imply a particular implementation. The present document contains preliminary LLC protocolrequirements which will be moved into the formal LLC protocol specification document (Part 6) when it is drafted.2ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the presentdocument.· References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific.· For a specific reference, subsequent revisions do not apply.· For a non-specific reference, subsequent revisions do apply.· A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.[1]TR 101 156: "Terrestrial Trunked Radio (TETRA); Technical requirements specification forDigital Advanced Wireless Service (DAWS)".[2]TS 101 659: "Terrestrial Trunked Radio (TETRA); Digital Advanced Wireless Service (DAWS);Medium Access Control (MAC); Requirements Specification".[3]Void.[4]Void.[5]IETF RFC 2211: "Specification of the Controlled-Load Network Element Service".[6]IETF RFC 2205: "Resource Reservation Protocol (RSVP) – Version 1 Functional Specification".[7]IETF RFC 2215: "General Characterization Parameters for Integrated Service Network Elements".3Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the following terms and definitions apply:base station: piece of equipment providing simultaneous, bi-directional network access to mobile stations.downlink: general term meaning "from the base station to the mobile station".flow: sequence of data packets originating from a single source and addressed to the same destination for which specialhandling by intervening routers is desired.mobile station: piece of equipment able to create and consume data but only having network access via a base station.protocol data unit: set of parameters and/or data passed from peer to peer by a protocol primitive.protocol instance: two protocol processes which exchange messages in order to transfer data from one protocol processto the other.protocol primitive: request, response, or informative message sent from peer to peer.PSIST TS 101 658:2000



ETSITS 101 658 V1.1.1 (1999-04)7protocol process: entity created to manage one end of a peer-to-peer protocol. For unidirectional data flows, a protocolprocess can be further described as either a sender process or a receiver process.service data unit: set of parameters and/or data passed between adjacent layers by a service primitive.service primitive: request, response, or informative message sent between adjacent layers.uplink: general term meaning "from the mobile station to the base station".3.2AbbreviationsFor the purposes of the present document, the following abbreviations apply:ACKAcknowledgedBEPBest-Effort PlusBSBase StationDAWSDigital Advanced Wireless ServiceDLDownlinkGWGatewayIPInternet ProtocolLLCLogical Link ControlLLC_ADMLLC Admission Control ServiceLLC_REGLLC Registration ServiceLLC_TPTLLC Transport ServiceLPDULLC Protocol Data UnitMACMedium Access ControlMSMobile StationMSHMobile Station HandleMSIMobile Station IdentifierNWKNetworkPDUProtocol Data UnitQOSQuality Of ServiceRSVPResource Reservation ProtocolSAPService Access PointSDUService Data UnitSWSwitchULUplink4IntroductionThe DAWS protocol architecture is provided in TR 101 156 [1]. The Logical Link Control (LLC) provides services tothe network layer (NWK) and requests services from the Medium Access Control (MAC) TS 101 659 [2]. The presentdocument provides the requirements the LLC service has to satisfy to operate successfully within a Digital AdvancedWireless Service (DAWS) network. As described in TR 101 156 [1], LLC functionality may be distributed acrossseveral DAWS nodes. The following prefixes will be used to specify the scope of a requirement:· LLC - the requirement applies to the LLC in general;· GW_LLC - the requirement applies to Gateway functionality;· SW_LLC - the requirement applies to Switch functionality;· BS_LLC - the requirement applies to Base Station functionality;· MS_LLC - the requirement applies to Mobile Station functionality.Figure 1 shows the architecture of the LLC for the minimum complexity DAWS network described in TR 101 156 [1].The network layer (NWK) accesses LLC services via service access points (SAPs) A and B. LLC_SAP_A is for datatransfer service primitives and LLC_SAP_B is for local control and status service primitives, including RSVPIETF RFC 2205 [6] operations.PSIST TS 101 658:2000



ETSITS 101 658 V1.1.1 (1999-04)8LLC_SAP_ALLC_SAP_BMAC_SAP_CLLC LAYERNWK LAYERMAC LAYERMAC_SAP_AMAC_SAP_BREGISTRATIONSERVICE(LLC_REG)ADMISSION CONTROLSERVICE (LLC_ADM)TRANSPORTSERVICE(LLC_TPT)Figure 1: DAWS LLC ArchitectureThe LLC accesses MAC services via service access points A, B, and C. MAC_SAP_A is for service primitives relatingto PDU transfers using an unacknowledged protocol; MAC_SAP_B is for service primitives relating to PDU transfersusing an acknowledged protocol; and MAC_SAP_C is for local control and status service primitives.Requirements for the registration, admission control, and transport services are provided in clauses 5, 6, and 7. Serviceprimitives and associated service data units are provided in clause 8. Annex A discusses the IPv4 to IPv6 transition.5Registration ServicesThe LLC registration service (LLC_REG) supports BS registration, MS registration, and de-registration operations.5.1Base station registrationEvery DAWS GW is assigned a globally unique identifier called the GWI. The GWI shall be assigned when the GW ismanufactured and shall not be dynamically alterable. The GW address space shall be administered by an industry bodyto prevent GWI address duplication among manufacturers.Every DAWS BS is assigned a globally unique identifier called the BSI. The BSI shall be assigned when the BS ismanufactured and shall not be dynamically alterable. The BSI address space shall be administered by an industry bodyto prevent BSI address duplication among manufacturers.Before a DAWS BS can provide wireless access service to a MS, the BS must register with a DAWS GW. BSregistration usually occurs immediately after BS power-on, and is composed of the following steps:1) BS_LLC sends a BS registration request message toward the GW via the next upstream switch;2) SW_LLC adds the binding (BSI, output_interface) to its routing table, and forwards the BS registrationrequest toward the GW. For simplicity, this example will assume only one upstream switch, so the next nodewill be the GW;3) GW_LLC adds the binding (BSI, output_interface) to its routing table, and sends a BS registration responsetoward the BS. The BS registration response contains the GWI of the GW;PSIST TS 101 658:2000



ETSITS 101 658 V1.1.1 (1999-04)94) SW_LLC forwards the BS registration response towards the BS;5) BS_LLC begins providing wireless access to MS within its cell. The BS regularly broadcasts the GWI of itsserving GW and its own BSI in a system information message to all MS within the serving cell. MobileStations use GWI information during the hand-over procedure to differentiate between intra-network andinter-network hand-overs.The size of the routing table within a DAWS switch is independent of the number of MS served by the DAWS network.The routing table size is proportional to the number of BS in the network.A DAWS network shall automatically correct its routing table entries if the network topology changes. Manualintervention by the system administrator shall not be required.5.2Mobile station registration5.2.1Cell selectionWhen an MS is powered on, MS_LLC_REG shall issue a request to MS_MAC_REG to do a scan of available cells andreport the results. MS_LLC_REG shall select the best cell and instruct MS_MAC_REG to camp on the cell.MS_LLC_TPT is then able to exchange PDUs with BS_LLC_TPT using the unacknowledged protocols.5.2.2RegistrationAfter cell selection, MS_LLC automatically registers with BS_LLC. MS_LLC registration with a BS involves thefollowing steps:1) MS_LLC obtains the BSI of the BS and GWI of the GW serving the BS from a system information message;2) MS_LLC sends a registration request to BS_LLC, providing its MSI;3) BS_LLC generates a MSH for the MS and adds the binding (MSI, MSH) to its registration table;4) BS_LLC generates two protocol instance identifiers for the ACK_BE_UL and a ACK_BE_DL protocolinstances;5) BS_LLC creates ACK_BE_UL and ACK_BE_DL protocol processes in BS_MAC;6) BS_LLC sends a registration response message containing the MSH and protocol instance identifiers toMS_LLC;7) MS_LLC stores its assigned MSH for future uplink and downlink signalling with the BS;8) MS_LLC creates ACK_BE_UL and ACK_BE_DL protocol processes in MS_MAC;9) MS_LLC sends a service indication message to MS_NWK indicating that LLC registration is complete,providing the registration triplet (GWI, BSI, MSI).The MS is now able to exchange PDUs with the BS using the two best-effort acknowledged protocols ACK_BE_ULand ACK_BE_DL. MS_NWK can create additional protocol instances by the procedures described in clause 7.5.2.3Service interruptionWhen MS_LLC receives a service interruption indication from MS_MAC, MS_LLC sends a service indicationinterruption to MS_NWK. MS_NWK will report the service interruption to higher layers in the protocol stack and willdiscard uplink traffic until service is restored.When MS_MAC indicates that service is restored, MS_LLC will re-register with BS_LLC and send a service indicationmessage to MS_NWK indicating that LLC service is available. The triplet (GWI, BSI, MSI) reported during the priorregistration will be reported again to MS_NWK, indicating that the serving BS and GW have not changed. If theduration of the LLC service interruption is sufficiently short, MS_NWK will not need to re-register with GW_NWK.PSIST TS 101 658:2000



ETSITS 101 658 V1.1.1 (1999-04)105.2.4Intra-network hand-overFor an intra-network hand-over, the MS loses services with a BS and re-establishes service with another BS within thesame DAWS network (i.e., both the prior and new BS have registered the same GW).When MS_LLC receives a service interruption indication from MS_MAC, MS_LLC sends a service indicationinterruption to MS_NWK. MS_NWK will report the service interruption to higher layers
...