hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
0133c157924a68e4b323f84043ec6472 | 101 415 | 5 Exceptional procedures | None identified. |
0133c157924a68e4b323f84043ec6472 | 101 415 | 6 Charging aspects | Based on the use of the feature "Support of Localised Service Area" it is possible to establish local tariff applications ("home zone applications"). ETSI ETSI TS 101 415 V7.3.0 (2000-07) 11 (GSM 02.43 version 7.3.0 Release 1998) |
0133c157924a68e4b323f84043ec6472 | 101 415 | 7 Commercial Role Model for SoLSA | SoLSA shall support LSAs which, do not belong to the HPLMN. To enable this the following commercial role model shall be used: SoLSA operator 3 SoLSA operator 2 Home operator SoLSA operator 1 Subscriber Subscription SIM configuration SoLSA services Subscriber info Commercial agreement LSA Definition Figure 6: SoLSA comm... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 1 Scope | The present document defines the stage one description of the Subscriber Identity Module Application Programming Interface (SIM API) internal to the SIM. Stage one is an overall service description, and does not deal with the implementation details of the API. The present document includes information applicable to net... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 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, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 3 Definitions and abbreviations | |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply. Applet: An Applet is an application built up using a number of modules which will run under the control of a virtual machine. Bytecode: Machine independent code generated by a bytecode compiler and executed by a bytecode interpreter. D... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AC Application Code AID Applet IDentifier APDU Application Protocol Data Unit API Application Programming Interface AVN Applet Version Number CA Certification Authority CAD Card Acceptance Device CHV1/2 Card Holder Verification information 1 a... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 4 Description | This document describes the high level requirements for an API for the GSM SIM. This API shall allow application programmers easy access to the functions and data described in GSM 11.11 [2] and GSM 11.14 [3], such that SIM based services can be developed and loaded onto SIMs, quickly and, if necessarily, remotely, afte... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 4.1 Design of SIM based applications using the SIM API | Figure 2 shows how SIM applications can be developed in a standard development environment and converted into an interpreted format, then loaded into the card. ETSI ETSI TS 101 413 V7.1.0 (1999-07) 9 (GSM 02.19 version 7.1.0 Release 1998) Development Environment API; e.g. Visual Basic API, C API, Java API Card Issuer S... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 4.2 SIM API Architecture | The SIM API shall consist of APIs for GSM 11.14 [3] (pro-active functions) and GSM 11.11 [2] (transport functions). Figure 3 illustrates the interactions between these APIs. Toolkit Applet 1 Applet 2 Toolkit Applet 3 Applet n Proactive command manager GSM SIM Kernel Files SIM API Framework Applet install/uninstall Secu... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 4.3 GSM file data access | The following methods shall be offered by the SIM Toolkit API: Select File: Select a file without changing the current file of any other applet or of the subscriber session. At the beginning of an entry point of an applet, the current file is the MF. This function may return the selected file information; Status: Read ... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 5 Card Interoperability | |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 5.1 Loader Requirements | There are a number of requirements for the loader which are seen as being vital to the successful deployment of SIM API based SIMs - The Applet format shall be common to all compliant SIMs, such that a card issuer can deploy SIM API based service applets to any SIM API compliant SIM. - The loader environment that allow... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 5.2 Application Transport | The transport of applications shall be transparent to the ME. Applications may be transported via several different bearers, e.g. SMS P-P, SMS-CB, USSD, GPRS etc. Transportation of applications to the SIM in a Phase 2+ SIM Application ME shall use the ENVELOPE command as specified in GSM 11.11 [2]. Other standardized t... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 6 Applet triggering | The application triggering portion of the SIM API Framework is responsible for the activation of applets, based on the APDU received by the GSM application. The inputs and outputs could be represented in the figure below : APDU Applet Triggering Menu Selected SMS Received Terminal Profile ... Figure 5: Applet Triggerin... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 7 Applet Life cycle management | The applet life cycle management concerns the applet preparation, loading, installation, registration, configuration, execution and removal/deactivation. Server Card Applet Status Preparation Arbitration Transport Verification Linking Installation Registration Activation Deactivation Removal Loaded Installed Registered... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 7.1 Applet Preparation | "Applet Preparation" refers to the optional phase of verifying the compliance of the applet code with card issuer standards. The applet is to be identified through an Applet Identification Number (AID) which is assigned through the procedure detailed in ISO/IEC 7816-5 [6] and an Applet Version Number (AVN). Both AID an... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 7.2 Loading | "Loading" refers to the process of transporting the applet code from a load server to the SIM and generating the loaded code on the SIM. The process shall be under the principle control of the card issuer, who may choose to delegate this responsibility to one or more trusted parties, possibly while imposing resource re... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 7.2.1 Arbitration | This phase is accomplished by mutual authentication between the SIM and the load server, and by establishing appropriate session keys for ensuring security during the data transfer, which is to follow. The minimum applet requirements are verified with regard to the environment present on the SIM (e.g. API version, SIM ... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 7.2.2 Transport | This stage shall encompass the transport of the data packets from the load server to the SIM, and may be done in accordance with GSM 03.48 [4] and optionally additional encryption using session keys generated/exchanged during the Arbitration phase. |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 7.2.3 Verification | This stage shall encompass the verification of the received data and may involved byte-code level or applet-specific verification. Should the verification stage fail, the applet shall be discarded. |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 7.2.4 Linking | This stage shall encompass the linking of the received code against the runtime environment present on the card. ETSI ETSI TS 101 413 V7.1.0 (1999-07) 14 (GSM 02.19 version 7.1.0 Release 1998) |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 7.3 Installation/Registration/Reactivation | This stage refers to the execution of applet-code regarding to the installation and registration of the applet with respect to the SIM/ME runtime environment. For example, this may involve the generation of an applet-specific menu entry in the ME's user interface through the appropriate SIM toolkit command, and the gen... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 7.4 Configuration | This stage may involve any necessary configuration of the applet code with regard to a particular user/set- up/environment. This stage is driven through code provided with the applet itself and may be executed repeatedly. |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 7.5 Execution | At this stage, providing the applet is activated, the applet is in a state where its execution may be triggered by any event as specified in clause 6. |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 7.6 Deactivation | This stage involves disabling the ability to execute applet code in the SIM and may be triggered by the user, the network operator or any third party, providing sufficient access rights are granted to them. Deactivation may include the release of any applet reserved resources (e.g. memory resources etc.). |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 7.7 Removal | This stage follows the deactivation of the applet and prevents the applet's reactivation. This may be followed by the release of the applet's memory. For security reasons, the memory may be overwritten by null data. |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 8 Security management | |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 8.1 Management of Applets | Security might be required during the loading of the applet from a load server onto the SIM, and the communications between the applet and any remote server during the execution of the applet code. In both cases security may involve the authentication of the communicating entities and the encryption of the data traffic... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 8.2 Applet Certification | The role of certification is to ensure that only the authorized entities are able to download an application on to the SIM. Based on this certificate, the card shall decide whether or not to accept the downloaded application. ETSI ETSI TS 101 413 V7.1.0 (1999-07) 15 (GSM 02.19 version 7.1.0 Release 1998) |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 9 API Compatibility | |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 9.1 Level of Compatibility | The commands and features supported by the API shall be as specified in the same Release year of GSM 11.11[2] and GSM 11.14[3]. |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 9.2 Compatibility at the Interface | In order to provide compatibility with the SIM/ME interface, a GSM application SIM implemented using the SIM API shall provide full functional compatibility with the structure and content of GSM 11.11 [2], GSM 11.14 [3] commands as specified in those documents. SIM implementing the API shall be compatible with all phas... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 9.3 Compatibility at the programming interface | All commands (at the functional level) shall be presented in a manner consistent with the customary or recommended use of the programming language at the programming level. The SIM API shall be provided in two ways: - an easy to use high level interface (proactive commands level), and - a low level interface (i.e. the ... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 9.4 Compatibility with other specifications | [TBD e.g. MExE and WAP] |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 10 API Extensibility | The SIM API shall support applications written for previous versions of the SIM API. There shall be means to manage versions of the SIM API. At installation of an applet the required SIM API version shall be checked as described in clause 7. The ability to extend the SIM API to add functionality may be possible without... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 10.1 Evolution of SIM / ME Interface (GSM 11.11) | As the SIM/ME interface is handled by the GSM SIM kernel any evolution of the interface may require the introduction of a new SIM API version. Older version of the SIM API would still be allowable, but would not have access to the interface enhancement. |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 10.2 Evolution of SIM Application Toolkit (GSM 11.14) | The SIM API shall provide a low-level interface to support any further releases of GSM 11.14[3]. A new version of the SIM API shall provide support for the new features at a high level interface. ETSI ETSI TS 101 413 V7.1.0 (1999-07) 16 (GSM 02.19 version 7.1.0 Release 1998) |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 10.3 Interworking with other systems | If interworking at APDU and SIM API level with other systems (e.g. MExE, WAP) require some specific functionality, it will first need to be defined either in the GSM 11.11 [2] or GSM 11.14 [3], and as a result it will be taken into account in the API specification. [Administrative command support is currently under dis... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 11 Data and Function Sharing and Access Control | |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 11.1 Sharing resources between applets | The API shall provide a secure data structure and function sharing mechanism between applets and with the GSM SIM kernel. The GSM SIM kernel should be able to share with applets: - GSM files : to get file status, read and update data field - CHV1,CHV2 : to get status. A toolkit applet shall be able to share any kind of... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 11.2 Access to data | The SIM API shall provide a way to let each applet indicate: - the shared data and functions, - the associated access functions to these data and functions, - the security or trust level required, - the accepted certification authorities, and, - the identity of the applet provider. The SIM API framework shall check all... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 12 Technology Considerations | |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 12.1 SIM hardware requirements | The SIM API requires a smart card device that is capable of implementing a virtual machine and the SIM API framework. It is seen as necessary that there is sufficient EEPROM to contain SIM Applets (either SIM toolkit applications or other SIM applications) along side the mandatory GSM files and potentially many (if not... |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 12.2 Technology limitations | |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 12.2.1 Memory Recovery | Although there is a requirement for SIM API compliant devices to allow reconfiguration, termination and removal of Applets, it is recognised that SIM API devices may not be fully capable of reclaiming the memory freed up. |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 12.3 Evolution | |
1419da2b22ba05fc229c6912f4be7b87 | 101 413 | 12.3.1 Remote Procedure Call | Some current technologies that meet the needs of the SIM API are not designed to allow RPC. Future alternative technologies may be able to support this. It is seen as a future requirement of SIM API when interacting with mobile equipment technologies such as MExE and WAP that RPC is supported. ETSI ETSI TS 101 413 V7.1... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 1 Scope | The scope of the present document is to define a multiplexing protocol between a mobile station and a terminal. The multiplexing protocol can be used to send any data, for instance voice, SMS, USSD, fax etc. The present document describes the protocol, but not the commands or data transported with it. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 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, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ABM Asynchronous Balanced Mode ERM Error-Recovery Mode DLC Data Link Connection FCS Frame Check Sequence SABM Set Asynchronous Balanced Mode UAU Unumbered Acknowledgement DM Disconnected Mode UIH Unnumbered Information with header Check UI Unn... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 4 Overview of Multiplexing System | The multiplexer provides mechanisms for conveying streams of data between TE and MS over a single start-stop framed, serial link. Figure 1 shows the arrangement of the various protocol levels and functions. The multiplexer layer provides multiplexing of data arranged in octet streams with no other framing; if the struc... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5 Non Error Recovery mode Options | This clause describes the non-error-recovery options (basic and advanced) of the multiplexer. The main are given below: - A simple set of procedures with no error recovery mechanism, for use on reliable connections. - Data transparency is provided by the HDLC mechanism (advanced option only). - A multiplexer control ch... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.1 Service Interface Definition | This clause describes the services provided by the TS 07.10 data link layer to the upper layer. The interface is specified in terms of primitives and parameters. NOTE: this clause is only for information, detailed description of the parameters is found in the following subclauses. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.1.1 Service Definition Model | The 07.10 specification is intended to define a protocol that can be used to emulate a serial port. In most systems the 07.10 will be a part of a port driver which includes a port emulation entity that must support existing communication APIs. The communication APIs vary from operating system to operating system and fr... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.1.2 Start up services | These services are used to start the TS 07.10 multiplexer operation over a serial channel. The following services are provided: TS0710_START.request (mode, system_parameters) TS0710_START.indication (mode, system_parameters) TS0710_START.response (mode, system_parameters, accept) TS0710_START.confirm (mode, system_para... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.1.3 DLC establishment services | The DLC establishment services are used to open DLC’s on the multiplexer channel. The following services are provided: TS_0710_DLC_ESTABLISHMENT.request(DLCI, system_parameters) TS_0710_DLC_ESTABLISHMENT.indication(DLCI, system_parameters) TS_0710_DLC_ESTABLISHMENT.response(DLCI, system_parameters, accept) TS_0710_DLC_... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.1.4 Data services | The data services provided are: TS_0710_DATA.request(DLCI, User_data) TS_0710_DATA.indication(DLCI, User_data) Description: The transmitting unit initiates transmission of data using the frame type specified for the chosen DLCI by means of the request primitive. The transmitted data is delivered to the upper layer of t... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.1.5 Power Control services | In some application it might be desirable for either the DTE or the DCE to enter a power saving mode with a minimum of communication activities taking place. Services that support this functionality are the Sleep services and the Wakeup services |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.1.5.1 Sleep services | TS_0710_SLEEP.request TS_0710_SLEEP.indication TS_0710_SLEEP.confirm Description: The request primitive is used to advice the receiving device that the transmitter wishes to enter a low power state. The TS 0710 layer of the receiving unit sends an indication primitive to the upper layer in order to inform that the tran... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.1.5.2 Wakeup services | TS_0710_WAKEUP.indication TS_0710_WAKEUP.response Description: The indication primitive is sent to the upper layer when the TS 0710 layer of the receiving unit receives a request to wake up from the power saving state. When the receiving device is ready to resume operation on the multiplexer channel this is indicated t... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.1.6 DLC Release services | The DLC release services are used to disconnect a DLC. The following services are provided: TS_0710_DLC_RELEASE.request(DLCI) TS_0710_DLC_RELEASE.indication(DLCI) ETSI TS 101 369 V6.3.0 (1999-03) 14 (GSM 07.10 version 6.3.0 Release 1997) Description: The request primitive is used by the upper layer in the transmitting ... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.1.7 Close down services | The Close down services are used to terminate multiplexer operation on the serial channel and resume AT mode. The services provided are: TS_0710_CLOSE.request TS_0710_CLOSE.indication Description: When the request primitive is passed to the TS 0710 layer of the transmitting device close down of the multiplexer mode is ... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.1.8.1.1 DLC parameter negotiation | These services are used to negotiate and set parameters for a specific DLC. The following services are provided: TS0710_PARNEG.request (DLC, DLC parameters) TS0710_PARNEG.indication (DLC, DLC_parameters) TS0710_PARNEG.response (DLC, DLC_parameters, accept) • TS0710_PARNEG.confirm (DLC, DLC_parameters, accept) Descripti... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.1.8.1.2 DLC Service Negotiation service | These services are used to negotiate and set a specific service on a DLC. The following services are provided: TS0710_SERVNEG.request (DLC, Service_parameters) TS0710_SERVNEG.indication (DLC, Service_parameters) TS0710_SERVNEG.response (DLC, Service parameters, accept) TS0710_SERVNEG.confirm (DLC, Service_parameters, a... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.1.8.1.3 Test service | These services are used to test the communication link between two 07.10 entities. The following services are provided: TS0710_TEST.request (Test data) TS0710_TEST.confirm (Test data) Description: The request primitive is used to request a test of the communication link. The data is sent to the remote entity, which loo... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.1.8.1.4 Flow control services | The flow control services provided are: TS_0710_FLOW.request(DLCI,State) TS_0710_FLOW.indication(DLCI, State) Description: The request primitive with State = disable disables the issuing of TS_0710_DATA.indications by the 07.10 entity. The request primitive with State = enable enables the issuing of TS_0710_DATA.indica... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.1.8.2 Port Emulation Services | |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.1.8.2.1 Remote DLC parameter negotiation service | These services are used to negotiate and set of parameters for a remote communication port. The following services are provided: TS0710_PORTNEG.request (DLC, Port_parameters) TS0710_PORTNEG.indication (DLC, Port_parameters) TS0710_PORTNEG.response (DLC, Port parameters, accept) TS0710_PORTNEG.confirm (DLC, Port_paramet... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.1.8.2.2 DLC Control Parameter service | The DLC Control Parameter service is used to convey control parameters between Port Emulation Entities. Default values should be assumed if no control parameter has been designated since the DLC has been made. This service is to control a specific DLC. It includes such as flow control, Modem signals, Break. The followi... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.1.8.2.3 DLC Line status indication service | These services are used to indicate a DLC line status to a remote port emulation entity.. The following services are provided: TS0710_PORTNEG.request (DLC, Line Status parameter) ETSI TS 101 369 V6.3.0 (1999-03) 17 (GSM 07.10 version 6.3.0 Release 1997) TS0710_PORTNEG.indication (DLC, Line Status parameter) Description... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.2 Frame Structure | All information transmitted between the TE and MS is conveyed in frames. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.2.1 Frame Fields | The frame structure is composed of an opening and a closing flag, an Address field, a Control field, an Information field and FCS field. A length indication field is present in each frame if no transparency mechanism is used for the multiplexing session. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.2.1.1 Flag Sequence Field | Each frame begins and ends with a flag sequence octet which is defined as a constant bit pattern. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.2.1.2 Address Field | The address field consists of a single octet. It contains the Data Link Connection Identifier (DLCI), the C/R bit and the address field extension bit as shown in Figure 2. Bit No. 1 2 3 4 5 6 7 8 EA C/R D L C I Figure 2: Format of Address Field The DLCI is used to identify an individual user information stream as well ... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.2.1.3 Control Field | The content of the control field defines the type of frame. The control fields of the frames used in this Specification are described in Table 2. Table 2: Coding of Control Field Frame Type 1 2 3 4 5 6 7 8 Notes SABM (Set Asynchronous Balanced Mode) 1 1 1 1 P/F 1 0 0 UA (Unnumbered Acknowledgement) 1 1 0 0 P/F 1 1 0 DM... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.2.1.4 Information Field | The information field is the payload of the frame and carries the user data and any convergence layer information. The field is octet structured. The information field is only present in I frames, UI frames and UIH frames. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.2.1.5 Length Indicator | This field is present only in case when basic option is activated. It has the following format: Bit 1 2 3 4 5 6 7 8 E/A L1 L2 L3 L4 L5 L6 L7 Figure 3: Length field, first byte The L1 to L7 bits indicates the length of the following data field. The default length is 31 bytes. According to the rule of ISO/IEC 13239:1997,... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.2.1.6 Frame Checking Sequence Field (FCS) | The FCS shall be the ones complement of the sum (modulo 2) of a) the remainder of xk (x7 + x6 + x5 + x4 + x3 + x2 + x1 + 1) divided (modulo 2) by the generator polynomial x8 + x2 + x + 1, ETSI TS 101 369 V6.3.0 (1999-03) 19 (GSM 07.10 version 6.3.0 Release 1997) where k is the number of bits in the frame existing betwe... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.2.2 Format Conventions | All transmitted characters will be sent using one start bit, eight data bits, no parity bit and one stop bit. In the field descriptions, bit 1 is transmitted first. Addresses, commands, responses and sequence numbers shall be transmitted low-order bit first (for example, the first bit of the sequence number that is tra... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.2.3 Frame Validity | An invalid frame in the frame format is one which meets any one (or more) of the following conditions: - is not properly bounded by two flags; - does not have at least three octets between flags after removal of characters inserted for transparency; - indicates presence of a transmission error in that the FCS check fai... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.2.4 Frame Abort | Aborting a frame is not supported. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.2.5 Inter-frame Fill | The time between frames shall be filled by sending continuous stop-polarity except in the case of the wake-up procedure (see subclause 5.4.7). The receiver shall also operate correctly if the time between frames is filled with flag characters. If a receiver receives more than three consecutive flags it shall begin to t... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.2.6 Basic Option | In this case, opening flag and closing flags may appear in the Information field of the frame. The flags cannot be used to determine beginning and end of a frame. A length indication for the frame must be given instead. The frame structure is then as follows: Flag Address Control Length Indicator Information FCS Flag 1... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.2.6.1 Constraint | The closing flag may also be the opening flag of the following frame. The flag value is different from the one used when the advanced option is activated. Operation on link using DC1/XON and DC3/XOFF control characters defined in ISO/IEC 646 is not supported. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.2.7 Advanced Option | If the advanced option is activated at the beginning of the multiplexing session, then it is used for all frames. This mechanism is based on a control octet transparency. It is based on a unique appearance of the opening and the closing flag in each frame. These flags will never appear in the information field of the f... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.2.7.1 Control-octet transparency | The following transparency mechanism shall be applied to each frame from address field to FCS field inclusive. The control escape octet is a transparency identifier that identifies an octet occurring within a frame to which the following transparency procedure is applied. The encoding of the control escape octet is: ET... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.2.7.2 Start/stop transmission - extended transparency | The transmitter may apply the above transparency procedure to other octets in addition to the flag and control escape octets. At present, the only other octets are flow-control characters. The procedure is described in subclause 5.2.6.3. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.2.7.3 Flow-control transparency | The flow-control transparency option provides transparency processing for the DC1/XON and DC3/XOFF control characters defined in ISO/IEC 646 (i.e., 1000100x and 1100100x, respectively, where x may be either 0 or 1). This has the effect of assuring that the octet stream does not contain values which could be interpreted... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.2.7.4 Frame Structure | The frame structure is shown in Figure 7. Note that this structure does not include information added for synchronisation (i.e. Start and stop bits) or transparency purposes. The order of transmission is from left to right. In case the Transparency mechanism is activated, the frame structure is as follows: Flag Address... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.3 Frame Types | |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.3.1 Set Asynchronous Balanced Mode (SABM) command | The SABM command shall be used to place the addressed station in the Asynchronous Balanced Mode (ABM) where all control fields shall be one octet in length. The station shall confirm acceptance of the SABM command by transmission of a UA response at the first opportunity. Upon acceptance of this command, the DLC send a... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.3.2 Unnumbered Acknowledgement (UA) response | The UA response shall be used by the station to acknowledge the receipt and acceptance of SABM and DISC commands. |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.3.3 Disconnected Mode (DM) response | The DM response shall be used to report a status where the station is logically disconnected from the data link. When in disconnected mode no commands are accepted until the disconnected mode is terminated by the receipt of a SABM command. If a DISC command is received while in disconnected mode a DM response should be... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.3.4 Disconnect (DISC) command | The DISC command shall be used to terminate an operational or initialization mode previously set by a command. It shall be used to inform one station that the other station is suspending operation and that the station should assume a logically disconnected mode. Prior to actioning the command, the receiving station sha... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.3.6 Unnumbered Information (UI) command and response | The UI command/response shall be used to send information without affecting the V(S) or V(R) variables at either station.. Reception of the UIH command/response is not sequence number verified by the data link procedures; therefore, the UIH frame may be lost if a data link exception occurs during transmission of the pr... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4 Procedures and States | |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.1 DLC Establishment | In most cases the establishment of a DLC will be initiated by the TE, however, the protocol is balanced and the initiation may come from the MS. The action taken by the higher layers of the TE upon the initiation of the establishment of a DLC from the MS is outside the scope of this specification. The station wishing t... |
cec7b714df10925975b4d70566fa8c3f | 101 369 | 5.4.2 DLC Release | The release of a DLC may be initiated by either station by the transmission of a DISC frame with the P-bit set to one. Confirmation of the DLC release is signalled by the other station sending a UA frame with the F-bit set to 1. Once the DLC has been released the stations enter disconnected mode for that particular DLC... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.