hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
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 Smart Card Application platform; e.g. Java Card, Multos, Smart Card for Windows Source code; e.g. C, Java, Visual Basic, etc. Bytecode Toolkit Applet File Applet file stored in EEPROM Execution environment Runnable (activated) applet Executed applet compile (including libraries) optimise (optional) download install activate trigger Figure 2: Flow diagram of the development of a SIM application ETSI ETSI TS 101 413 V7.1.0 (1999-07) 10 (GSM 02.19 version 7.1.0 Release 1998)
|
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 Security Applet triggering Applet security manager Activation Proactive commands P/C responses Install Uninstall APDU Interface to terminal APDU e.g. Envelopes Proactive polling, 91XX, Fetch, Proactive commands, Terminal Response File access File access SIM-API … (see NOTE 1) NOTE 1: The install / uninstall process does not form part of the API. Its requirements are outlined in subclause 7. Figure 3: SIM API Architecture In this model, the GSM data field structure is viewed as a series of data structures and data access functions to the API. In the physical model of course, they may still be stored in elementary files, but the functions will access these data as values within those data structures. The following figure mirrors the SIM API architecture, relating each part to the appropriate ETSI/GSM or ISO/IEC specification. Toolkit Applet Process ( A series of instructions requiring Toolkit commands and variables ) SIM API GSM 03.48 [4] Transport Security Mechanisms (e.g. applied to SMS Data download) GSM 11.14 [3] TLVs (Built from commands and variables) GSM 11.11 [2] Transport of TLVs (Envelope, Fetch, Terminal Response) Interaction with data (Other GSM 11.11 [2] commands) ISO/IEC 7816-3 [5] Physical interface (e.g. T=0) Figure 4: SIM API layers ETSI ETSI TS 101 413 V7.1.0 (1999-07) 11 (GSM 02.19 version 7.1.0 Release 1998) A general requirement of the SIM API is that applets should not interfere with the basic GSM services.
|
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 the file status information of the current DF; Read Binary: Read data bytes of a transparent EF; Read Record: Read data bytes of a linear fixed or cyclic EF without changing the current record pointer of any other applet / subscriber. This function may allow reading part of a record; Update Binary: Modify data bytes to a transparent EF; Update Record: Modify data bytes to a linear fixed or cyclic EF. The current record pointer of other applets / subscriber shall not be changed in case of linear fixed EF but the current record of a cyclic EF shall be changed for all other applets / subscriber. This function may allow updating part of a record; Seek: Search a record of a linear fixed file starting with a given pattern. The current record pointer of any other applet or of the subscriber session shall not be changed; Increase: Increase the value of the current record of a cyclic EF. The current record will be changed for every other applet and subscriber session. This function may not return the increased value; Rehabilitate: Rehabilitate the current EF with effect for all other applets / subscriber; Invalidate: Invalidate the current EF with effect for all other applets / subscriber.
|
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 allows the loading of applets to the SIM shall be common to all SIM API compliant SIMs. This loader shall be able to send applets to SIMs in three distinct ways: - During the personalization of the SIM, prior to the issue of the SIM to the user. - During the life of the SIM using the SIM Data Download mechanism defined in GSM 11.11 [2] and GSM 03.48 [4] or using other standardized mechanisms in the future. - During the life of the SIM using an IFD (Interface Device) or CAD (Card Accepting Device, e.g. an EPOS terminal).
|
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 transport commands to the SIM may be developed in the future. Transport commands other than ENVELOPE may be used to transport applets to the SIM if the SIM is not in an ME. ETSI ETSI TS 101 413 V7.1.0 (1999-07) 12 (GSM 02.19 version 7.1.0 Release 1998)
|
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 Triggering module Entry points to the applet shall be provided in two ways: - High level entry points, in order to have a simple programming of the SIM card - Low level entry points to support the evolution of the GSM 11.14 [3] specification (see Section 10.2) Some of the high level entry points are listed below: - Application Loading - Application Removal - Terminal Profile - Menu Selection - Short Message Reception - Cell Broadcast Short Message Reception - Call Control
|
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 Activated Deactivated Figure 6: Applet Life Cycle ETSI ETSI TS 101 413 V7.1.0 (1999-07) 13 (GSM 02.19 version 7.1.0 Release 1998)
|
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 and AVN are assigned during the applet preparation phase. The minimum requirements for the applet (such as API versions, SIM capabilities, resource requirements) shall be specified.
|
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 restrictions (e.g. maximum memory allowance) or access restrictions (e.g. limited or reduced functionality). The loading process involves four distinct phases: Arbitration, Transport, Verification and Linking. The card shall provide acknowledgement of success or failure (including error identification code) to the load server if the load server requires this.
|
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 capabilities and available memory). If this fails, the loading process shall be aborted. The applet identifiers (AIDs) and version numbers (AVNs) of any applets already installed on the SIM are compared to the AID and AVN of the applet, which is to be downloaded. If an identical applet is already installed on the SIM (i.e. both applet identifier and version number match), the phases Transport, Verification and Linking are skipped. If an applet with an identical applet identifier (AID) but different version number (AVN) is available on the SIM, that applet is removed (see subclause 7.7, Removal).
|
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 generation of applet-specific data structures in SIM memory. If the applet already exists on the SIM and is deactivated (see subclause 7.6), the installation request shall reactivate the applet. Other methods of reactivation are possible via a separate command.
|
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 between those entities. A hierarchy of keys may be bootstrapped by initializing a set of keys by the card issuer during card personalization. Additional keys may be generated, distributed using existing keys, and equipped with limited authority. Such keys may be passed on to trusted parties and subsequently used for authentication and encryption.
|
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 phases of MEs.
|
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 TLV parameters) to maximise scope without the need to extend the SIM API.
|
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 reissuing the card.
|
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 discussion within ETSI SMG9]
|
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 data with any other applet even a non-toolkit applet. The data and function sharing mechanism and the access control management shall be common to all card issuers. To ease the deployment, these requirements have the following priorities: - high: GSM SIM kernel data sharing (e.g. access to the Telecom directory), - medium: inter industry sharing mechanism between applets.
|
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 these parameters before granting an access to data.
|
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 all) of the optional GSM files. The hardware requirements are likely to be: - ROM: minimum 24K Bytes - RAM: minimum 1K Byte - EEPROM: minimum 16K Bytes ETSI ETSI TS 101 413 V7.1.0 (1999-07) 17 (GSM 02.19 version 7.1.0 Release 1998)
|
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.0 (1999-07) 18 (GSM 02.19 version 7.1.0 Release 1998) Annex A (Informative): Change History This annex lists all change requests approved for the present document by ETSI SMG. SMG# SMG tdoc SMG9 tdoc VERS CR RV PH CAT SUBJECT Resulting Version s27 98-0674 98p353 2.0.0 Approved at SMG #27 7.0.0 s29 P-99-410 9-99-203 7.0.0 A001 R98 F Technology neutrality and implementation independence of specification 7.1.0 ETSI ETSI TS 101 413 V7.1.0 (1999-07) 19 (GSM 02.19 version 7.1.0 Release 1998) History Document history V7.1.0 July 1999 Publication ISBN 2-7437-3258-X Dépôt légal : Juillet 1999
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
1 Scope
|
........................................................................................................................................................7
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
2 References
|
................................................................................................................................................7
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
3 Abbreviations
|
...........................................................................................................................................7
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
4 Overview of Multiplexing System
|
...........................................................................................................7
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5 Non Error Recovery mode Options
|
..........................................................................................................9
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.1 Service Interface Definition
|
...............................................................................................................................9
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.1.1 Service Definition Model
|
..............................................................................................................................9
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.1.2 Start up services
|
..........................................................................................................................................10
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.1.3 DLC establishment services
|
........................................................................................................................11
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.1.4 Data services
|
...............................................................................................................................................12
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.1.5 Power Control services
|
...............................................................................................................................12
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.1.5.1 Sleep services
|
........................................................................................................................................12
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.1.5.2 Wakeup services
|
...................................................................................................................................12
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.1.6 DLC Release services
|
.................................................................................................................................12
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.1.7 Close down services
|
....................................................................................................................................13
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.1.8 Control Services
|
..........................................................................................................................................13
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.1.8.1 07.10 Services
|
.......................................................................................................................................13
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.1.8.1.1 DLC parameter negotiation
|
.............................................................................................................13
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.1.8.1.2 DLC Service Negotiation service
|
....................................................................................................14
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.1.8.1.3 Test service
|
......................................................................................................................................14
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.1.8.1.4 Flow control services
|
.......................................................................................................................14
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.1.8.2 Port Emulation Services
|
........................................................................................................................15
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.1.8.2.1 Remote DLC parameter negotiation service
|
....................................................................................15
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.1.8.2.2 DLC Control Parameter service
|
......................................................................................................15
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.1.8.2.3 DLC Line status indication service
|
..................................................................................................15
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.2 Frame Structure
|
................................................................................................................................................16
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.2.1 Frame Fields
|
...............................................................................................................................................16
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.2.1.1 Flag Sequence Field
|
..............................................................................................................................16
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.2.1.2 Address Field
|
........................................................................................................................................16
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.2.1.3 Control Field
|
.........................................................................................................................................17
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.2.1.4 Information Field
|
..................................................................................................................................17
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.2.1.5 Length Indicator
|
....................................................................................................................................17
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.2.1.6 Frame Checking Sequence Field (FCS)
|
................................................................................................17
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.2.2 Format Conventions
|
....................................................................................................................................18
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.2.3 Frame Validity
|
............................................................................................................................................18
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.2.4 Frame Abort
|
................................................................................................................................................19
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.2.5 Inter-frame Fill
|
............................................................................................................................................19
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.2.6 Basic Option
|
...............................................................................................................................................19
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.2.6.1 Constraint
|
..............................................................................................................................................19
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.2.7 Advanced Option
|
........................................................................................................................................19
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.2.7.1 Control-octet transparency
|
....................................................................................................................19
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.2.7.2 Start/stop transmission - extended transparency
|
...................................................................................20
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.2.7.3 Flow-control transparency
|
....................................................................................................................20
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.2.7.4 Frame Structure
|
.....................................................................................................................................20
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.3 Frame Types
|
.....................................................................................................................................................21
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.3.1 Set Asynchronous Balanced Mode (SABM) command
|
..............................................................................21
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.3.2 Unnumbered Acknowledgement (UA) response
|
........................................................................................21
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.3.3 Disconnected Mode (DM) response
|
...........................................................................................................21 ETSI ETSI TS 101 369 V6.5.0 (2002-03) 4 3PP TS 07.10 version 6.5.0 Release 1997
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.3.4 Disconnect (DISC) command
|
.....................................................................................................................21
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.3.5 Unnumbered information with header check (UIH) command and response
|
.............................................21
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.3.6 Unnumbered Information (UI) command and response
|
.............................................................................21
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.4 Procedures and States
|
.......................................................................................................................................22
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.4.1 DLC Establishment
|
.....................................................................................................................................22
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.4.2 DLC Release
|
...............................................................................................................................................22
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.4.3 Information Transfer
|
...................................................................................................................................22
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.4.3.1 Information Data
|
...................................................................................................................................22
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.4.3.2 Priority
|
..................................................................................................................................................23
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.4.4 Frame Variables
|
..........................................................................................................................................23
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.4.4.1 Functions of the poll bit
|
........................................................................................................................23
|
b141ca6b11bc6e64f8f7100ef91258b9
|
101 369
|
5.4.4.2 Functions of the final bit
|
.......................................................................................................................23
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.