hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 8.1 Frequency bands and channel arrangement | The following channelisations shall be supported by the terminals: • 5 MHz bandwidth channels (baseline); • 625 kHz bandwidth channels; • 312,5 kHz bandwidth channels. Terminals shall be able to use any radio frequency channel available in the return link frequency band: • 1 980 MHz to 2 010 MHz. |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 8.2 Stability and accuracy requirements | Stability and accuracy are partially dependent on synchronisation as described in clause 9. |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 8.2.1 Frequency and symbol timing stability and accuracy | The RMS carrier frequency error (measured at the satellite receiver input) for all QS-CDMA carriers shall be better than 5 Hz. NOTE: QS-CDMA carriers are used for dedicated physical channels (not the RACH). The RMS chip frequency error (measured at the satellite receiver input) for all QS-CDMA carriers shall be better ... |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 8.2.2 Time alignment accuracy | Terminals shall be able to apply time alignment corrections with accuracy better than or equal to 1/16 = 0,0625 chips. |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 8.2.3 Power stability and accuracy | Terminals shall be able to apply power corrections with accuracy better than or equal to 0,2 dB. |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 8.3 Transmitter characteristics | |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 8.3.1 Power output characteristics and power class | NOTE: Typical EIRP values and power classes are defined in Part 1 [1]. |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 8.3.2 Transmit polarization | Polarization in the return services shall be either left-hand circular (LHCP) or right-hand circular (RHCP) polarization. |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 8.3.3 Unwanted Emissions | ETSI MSS standards ([i.6] for wideband and [i.7] for narrowband systems) provide extensive regulation for the unwanted emissions. Since each document applies for different bandwidths, the requirements that would apply for each channelisation would be: • 5 MHz (baseline): wideband systems requirements. • 625 and 312,5 k... |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 8.4 Power Control | The following power-control parameters need to be broadcast by the Hub periodically to all terminals in the system (statically configured unless otherwise noted): • Expected FWD link SNIR for a terminal located at the edge of coverage with the worst case G/T in clear sky conditions: ( ) dB SNIR ected FWD total exp , . ... |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 8.4.1 Open-loop Power Control for RACH | The terminal estimates the combined terminal loss, Lcomb, defined as the difference between the fading loss and the satellite transmission Pattern Advantage at its location. The calculation of the combined terminal loss is based on FWD link measurements, and is used to calculate the ULB power. The procedure is as follo... |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 8.4.2 Closed-loop Power Control for RACH | In order to adjust the terminal transmitter power for the initial DCH transmission, the Hub sends the terminal a correction based on the received ULB Es/(N0+I0). The procedure is as follows: 1) Upon receipt of an ULB with a Channel Request, the hub send an initial power correction QS CDMA P − Δ . 2) The initial DCH car... |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 9 Synchronisation | |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 9.1 General description of synchronisation system | The S-MIM synchronous access is a connection-oriented system where all QS-CDMA carriers shall be quasi-synchronous in time and frequency. Synchronisation involves two major tasks: • Timing (chip phase and frequency) synchronisation. • Carrier frequency synchronisation. The RACH provides the ability for a terminal not o... |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 9.2 Terminal requirements | The following terminals requirements shall be fulfilled: • Terminals shall use the same reference clock for the RF up-converter and base-band modulator. • The FWD link receiver tuner and base-band modules shall use the same reference clock as above. • Terminals shall never transmit if they are not locked to the satelli... |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 9.3 Synchronisation procedures | This clause defines the procedures to allow a terminal to logon on and initiate a data transmission. |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 9.3.1 Overall events sequencing | Terminal synchronisation states are defined in Table 9.1 and the terminal state flow diagram is shown in Figure 9.1, giving an overview of the overall events sequencing. In Figure 9.1, represents terminal states, represents procedures. ETSI ETSI TS 102 721-4 V1.2.1 (2013-08) 32 Table 9.1: Terminal synchronisation state... |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 9.3.2 FWD link synchronisation procedure | Following the power-up, the terminal shall proceed as detailed below: • The terminal shall first synchronise the satellite FWD link carrier and extract the FWD link data. • Control information (System tables) related to the operation of the S-MIM synchronous access shall be extracted and processed. • FWD link carrier a... |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 9.3.3 Logon procedure | After the terminal has received all System tables related to the S-MIM synchronous access, it is ready to initiate a logon, in order to be admitted to the S-MIM synchronous access and be ready to request capacity to handle traffic. The terminal shall proceed as follows: • The terminal shall transmit a logon request by ... |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 9.3.4 Capacity request procedure | Once in LOGGED_ON state, the terminal is allowed to request capacity. The capacity request procedure is either triggered by higher layers of the terminal or by the Hub, e.g. upon notification of an incoming call. The terminal shall proceed as detailed below: • The terminal shall transmit a capacity request by means of ... |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 9.3.5 Synchronisation maintenance procedure | While the terminal is in TX_ON_DATA_OFF or TX_ON_DATA_ON states, the terminal shall transmit a QS-CDMA carrier and execute the synchronisation maintenance procedure, which is detailed below: • The Hub continuously estimates synchronisation errors and Es/(N0+I0).and sends synchronisation (carrier frequency and chip phas... |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 9.3.6 Logoff procedure | Although it has not been represented in Figure 9.1 in order to make the diagram clearer, a logoff procedure is described. This procedure can be initiated by the Hub or by the terminal. When initiated by the Hub, the procedure goes as follows: • The procedure can be initiated anytime by the Hub. In this case, the Hub sh... |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 9.3.7 Transmission disable | The Hub can disable a terminal transmission by setting the Transmission disable flag to 1. The Transmission disable flag is a parameter sent to the terminal through the satellite FWD link. Along with the Transmission disable notification, a timeout TD_timeout is sent. Upon reception of a Transmission disable = 1, the t... |
3b95bb73725a95444c0a4f56a47f8c65 | 102 721-4 | 10 Physical layer measurements | Radio characteristics are measured and reported to higher layers and the network. Such measurements are for further study. ETSI ETSI TS 102 721-4 V1.2.1 (2013-08) 38 History Document history V1.1.1 December 2011 Publication V1.2.1 August 2013 Publication |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 1 Scope | The present document defines an architectural framework supporting the personalization and user profile management concepts described in EG 202 325 [i.1]. The present document addresses issues related to network requirements, functions and procedures. It also covers User Profile security and privacy issues. Capabilitie... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI ES 202 746: "Human Factors (HF); Personalization... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI EG 202 325: "Human Factors (HF); User Profi... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 3 Definitions and abbreviations | |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in EG 202 325 [i.1] and the following apply: Concealable, Removable, Available, Valuable, Enjoyable, and Disposable (CRAVED): classification scheme to determine the likelihood that a particular type of item will be the subject of theft [i.7] cont... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP AKA 3GPP Authentication and Key Agreement AA Attribute Authority AC Attribute Certificate AS Application Server ASF Application Server Function CA Certificate Authority CC/PP Composite Capability/Preference Profiles CPS Common Profile Sto... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 4 Summary of profile | The role of profiles is to enable all the devices and services used by a user to share the user's preferences and to adapt to the environment in which the device or service is invoked. NOTE 1: A detailed description of the personalization and user profile concept is to be found in EG 202 325 [i.1]. A user profile is a ... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 5 User profile management architecture requirements | |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 5.1 Profile roles | As defined in EG 202 325 [i.1] the user may play two roles: • Profile user: - role played by end users when using a profile. • Profile administrator: - role played by end users when defining or modifying a profile. The same end user can play both the user role and the administrator role. |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 5.2 Profile identification | The profile seen by the user at the device or service using the profile should be readily identifiable by the user and may therefore be identified by name, icon (or other visual mnemonic), or other user interpretable indication (as defined in ES 202 746 [1]). All instances of the profile shall share this identity but t... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 5.3 The UPM architecture model | The UPM architecture is derived from the use cases and their interaction illustrated in figure 5.1, and the class model that may be developed in figure 5.2. ETSI ETSI TS 102 747 V1.1.1 (2009-12) 14 UseContextInformation ManageProfile UseProfileData UseService Administrator ContextProvider User <<extends>> <<precedes>> ... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 5.4 Procedures | NOTE: Whilst many of the user initiated interactions outlined in this clause require an intuitive user interface, details of the user interface are not defined in the present document. |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 5.4.1 Introduction | UPM shall support the following procedures described in detail in the present document: • Profile synchronization. • Profile creation/update. • Modification of profile data according to context. • Profile deletion. The procedures listed above are considered with respect to the use case model provided in figure 5.1. The... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 5.4.2 Profile synchronization | Data values in the profile shall be updated by means of the device or service native functionality. Where values in the profile are to be exported for common application, the methods in this clause shall apply. NOTE: The term service includes those applications used for direct management of the profile as well as those... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 5.4.2.1 Synchronization conflict resolution/avoidance | Conflicts may occur in the setting of a profile data item value in the root profile storage when two (or more) profile components attempt to synchronize that profile data item where each component holds a different value for the element. To avoid this any update transaction shall lock out any other update transactions.... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 5.4.2.2 Protocol candidates for profile component synchronization | The present document does not define the detail protocol to implement the synchronization of profile components to the root profile. This clause illustrates the availability of protocols that may fulfil the requirements previously indicated. When treating UP and UPM as a means of harmonizing database content there are ... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 5.4.3 Profile creation/update/deletion | |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 5.4.3.1 Profile creation | The suite of procedures for creation/update/deletion of the profile includes the following cases: • Creation of a root profile. • Association of a root profile to service or device (creation of a profile component). ETSI ETSI TS 102 747 V1.1.1 (2009-12) 18 NOTE: A template or an existing profile can be used as the star... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 5.4.4 Update of profile data according to context | The most important task of the UPM system is to ensure that the values of the attributes of Profile-Data-Items meet the user's preferences for the current context. This shall be achieved by using the following simple algorithm (see the method named conflictResolution in ES 202 746 [1]) that sets the values of the attri... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 5.4.5 Profile deletion | A user may delete a component or an entire profile from the device or service. Deletion of a root profile where components are in use shall be prevented. When deleting a live template, the profiles created based on it will still remain, but will have to be updated individually instead of being updated through the live ... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 6 UP/UPM security | |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 6.1 UP/UPM and impact on privacy | The services and devices that together form the UP/UPM (sub) system should ensure consistency with Article 12 of Universal Declaration of Human Rights [i.13] which declares that "No one shall be subjected to arbitrary interference with his privacy, family, home or correspondence, nor to attacks upon his honour and repu... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 6.2 Key goal for UP/UPM security | For UP/UPM the intent is to ensure a set of applications can use the data in a profile, and have trust in that data, without having to establish a security relationship in advance with the user or with the data. NOTE: There will be a residual risk associated with UP/UPM and a strong likelihood of leakage of private dat... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 6.3 Risk analysis - assumptions and objectives | For the purposes of analysis the assumptions listed in table 6.2 are made with respect to UP/UPM. ETSI ETSI TS 102 747 V1.1.1 (2009-12) 21 Table 6.2: General assumptions related to UP and UPM Assumption Assumption#1 A user profile is shared between devices Assumption#2 Devices may use the same profile concurrently Assu... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 6.4 Risk analysis - functional capabilities | NOTE: The functional capabilities are derived using the guidelines given in TR 187 011 [i.5] and form a part of the ETSI TVRA approach to risk based security provisions as defined in TS 102 165-1 [i.4]. |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 6.4.1 Threats and threat agents in UP/UPM | The primary threats and attack forms to be considered in UP/UPM are: • Masquerade as UP/UPM user or as UP/UPM service provider. • Interception of UP/UPM data in transit or from storage. • Manipulation or UP/UPM data in transit or in storage. In addition the system should be able to prevent replay attacks (in this case ... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 6.4.2 Identification | Management and user actions in UPM that lead to a change in the profile should be fully accountable and therefore the invoking entity should be identified and should also be authenticated (to counter masquerade). Each invocation of a UPM and/or UP capability should follow the following simple guidelines: • The <<UPM/UP... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 6.4.3 Privacy | Privacy is inherently complex and there are a number of core functional aspects that have to be addressed. These are summarized in the bullet points that follow: • Anonymity: ensures that a user may use a resource or service without disclosing the user's identity. The requirements for Anonymity provide protection of th... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 6.4.4 Integrity (data) | Where data is transferred between any pair of collaborating entities in the context of UPM the integrity of the transferred data should be assured. If the received data is required by an invoked service capability that service capability should be terminated if there is any doubt in the integrity of the received data. ... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 6.5 Detailed security requirements | The detail security requirements are provided in the present document at an abstract level to allow them to be mapped to provisions in existing mechanisms that may be deployed in the target environment for UP/UPM. As identified in annex D the core of security is in the provision of Security Associations (SAs) and for t... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 6.5.1 Identification SA | Accurate identification of the UP user, the UP enabled devices and services, and the UP storage area is essential as a pre-condition for authentication and may be an essential pre-condition for authorization. In the general case the UP-user is a person and shall adopt the naming scheme of the system that hosts the UP/U... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 6.5.2 Authentication SA | Where the host system is the NGN and where the UP-User is identified as an NGN-user as identified in TS 184 002 [5] the authentication schemes identified for the NGN shall apply. |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 6.5.3 Authorisation SA | In order to ensure that only authorized parties can access and update the profile there shall be an authorization SA between the parties involved in the synchronization protocol, i.e. the profile service provider hosting the root profile and the device or service holding the active profile. The form of Authorisation SA... |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 6.5.4 Confidentiality SA | In order to preserve privacy of communication and to protect from exploit of intercepted data there shall be a confidentiality SA between the parties involved in the synchronization protocol, i.e. the profile service provider hosting the root profile and the device or service holding the active profile. |
609c5a3ea4b21387bbadc3fa8f3e01b7 | 102 747 | 6.5.5 Integrity SA | The UP/UPM system shall provide integrity services (generation of proof of integrity and validation of the proof) across all connections and for the data storage areas. ETSI ETSI TS 102 747 V1.1.1 (2009-12) 26 Annex A (normative): Mapping to services and networks A.1 Introduction The user profile system defines a funct... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 1 Scope | The present document covers the minimum characteristics which are considered necessary for the UICC in order to provide compliance to ETSI TS 102 622 [1]. The present document specifies the test cases for: • the HCI core as described in the first part of ETSI TS 102 622 [1]; • the contactless platform as described in t... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 2 References | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. • In the case of a reference ... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. • In the case of a reference ... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 3 Definition of terms, symbols and abbreviations | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 102 622 [1] and the following apply: allowed error response code: response code which is not ANY_OK and which is allowed for the referenced command as specified in ETSI TS 102 622 [1] non-occurrence RQ: RQ which has been extracted from ETSI TS 102 622... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 3.2 Symbols | For the purposes of the present document, the symbols given in ETSI TS 102 622 [1] and the following apply: PIPE0 the static pipe connected to the link management gate of the device under test PIPE1 the static pipe connected to the administration gate of the device under test |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 622 [1] and the following apply: ATQA Answer To reQuest of type A ATQB Answer To reQuest of type B CLT ContactLess Tunnelling DUT Device Under Test EOF End of Frame FFS For Further Study FWI Frame Waiting time Integer HCI Host Controller I... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 3.4 Void | Content of this clause has been moved to clause 3A. |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 3A Formats | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 3A.1 Format of the table of optional features | The columns in table 4.1 have the following meaning. Column Meaning Option The optional feature supported or not by the DUT. Status See clause 3A.3. Support The support columns shall be filled in by the supplier of the implementation. The following common notations, defined in ISO/IEC 9646-7 [6], are used for the suppo... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 3A.2 Format of the applicability table | The applicability of every test in table 4.2 is formally expressed by the use of Boolean expression defined in the following clause. The columns in table 4.2 have the following meaning. Column Meaning Clause The "Clause" column identifies the clause containing the test case referenced in the "Test case number and descr... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 3A.3 Status and Notations | The "Rel-x" columns show the status of the entries as follows: The following notations, defined in ISO/IEC 9646-7 [6], are used for the status column: M mandatory - the capability is required to be supported. O optional - the capability may be supported or not. N/A not applicable - in the given context, it is impossibl... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 3A.4 Format of the conformance requirements tables | The conformance requirements tables contained in the present document have the following format and meaning: Column Status Meaning Mandatory This mandatory column contains the conformance requirement number (e.g. RQ3). Optional This optional column is present when the containing clause sources conformance requirements ... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 4 Test environment | |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 4.1 Table of optional features | The device supplier shall state the support of possible options in table 4.1. See clause 3A for the format of table 4.1. Table 4.1: Options Item Option Status Support Mnemonic 1 Link management gate supported O O_LINK_MAN 2 WHITELIST contains the HID of at least one further host O O_WHITELIST_NON_EMPTY 3 Data link laye... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 4.2 Applicability table | Table 4.2 specifies the applicability of each test case to the device under test. See clause 3A for the format of table 4.2. Clause 4.5.2 should be referenced for usage of the execution requirements which are referenced in table 4.2 a) and described in table 4.2 c). Table 4.2 a): Applicability of tests Clause Test case... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.2.2 Test case 1: processing of RFU host identifier | Rel-7 M M M M M |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.3.2 Test case 1: existence of gates | Rel-7 M M M M M |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.4.2 Test case 1: static pipe deletion - administration gate | Rel-7 M M M M M |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.4.3 Test case 2: static pipe deletion - link management gate | Rel-7 C101 C101 C101 C101 C101 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.4.4 Test case 3: persistence of pipe state | Rel-7 M M M M M |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.1.4.5 Test case 4: initial pipe state | Rel-7 M M M M M |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.2.2.2 Test case 1: commands/events on pipe which is not open | Rel-7 M M M M M 5.3.1.2.1.2 Test case 1: ANY_SET_PARAMETER reception - invalid structure Rel-7 C101 C101 C101 C101 C101 5.3.1.2.1.3 Test case 2: ANY_SET_PARAMETER reception - RO registry parameter Rel-7 M M M M M 5.3.1.2.2.2 Test case 1: ANY_GET_PARAMETER reception - invalid structure Rel-7 M M M M M 5.3.1.2.3.2 Test c... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.2.2 Test case 1: response to unknown command | Rel-7 M M M M M 5.3.2.3 Test case 2: responses received out of order, previous command sent by host controller Rel-7 M M M M M |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.3.3.2 Test case 1: reception of unknown events | Rel-7 M M M M M |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.4.1.2 Test case 1: command and event support for link management gate | Rel-7 C101 C101 C101 C101 C101 5.4.1.3 Test case 2: command and event support for host administration gate Rel-7 M M M M M 5.4.2.1.1.2 Test case 1: SESSION_IDENTITY Rel-7 M M M M M 5.4.2.3.1.2 Test case 1: registry parameters Rel-7 M M M M M |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.5.1.1.3 Test case 2: ADM_NOTIFY_PIPE_CREATED from host controller | Rel-7 M M M M M |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.5.1.1.4 Test case 3: ADM_NOTIFY_PIPE_CREATED from other host | Rel-7 C102 C102 C102 C102 C102 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.5.1.1.5 Test case 4: ADM_NOTIFY_PIPE_CREATED with incorrect destination HID | Rel-7 M M M M M |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.5.1.1.6 Test case 5: unsuccessful ADM_NOTIFY_PIPE_CREATED | Rel-7 SR5 M M M M M |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.5.1.2.3 Test case 2: receiving ADM_NOTIFY_PIPE_DELETED | Rel-7 M M M M M 5.5.1.3.2 Test case 1: ADM_CLEAR_ALL_PIPE for data link layer specified in ETSI TS 102 613 [2] Rel-7 C103 C103 C103 C103 C103 5.5.1.3.3 Test case 2: ADM_CLEAR_ALL_PIPE - static pipes, dynamic pipes to host controller Rel-7 C103 C103 C103 C103 C103 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.5.1.3.4 Test case 3: ADM_CLEAR_ALL_PIPE - dynamic pipes to other host | Rel-7 C102 C102 C102 C102 C102 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.5.4.2 Test case 1: SESSION_IDENTITY not changed | Rel-7 C103 C103 C103 C103 C103 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.5.4.3 Test case 2: SESSION_IDENTITY changed | Rel-7 C103 C103 C103 C103 C103 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.5.4.4 Test case 3: activation in low power mode, no session initialization | Rel-10 N/A N/A N/A C103 C103 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.5.4.5 Test case 4: subsequent activation, no session initialization | Rel-10 N/A N/A N/A C103 C103 ETSI ETSI TS 102 695-2 V11.0.0 (2019-08) 18 Release 11 Clause Test case number and description Release Execution requirements Rel-7 UICC Rel-8 UICC Rel-9 UICC Rel-10 UICC Rel-11 UICC Support 5.5.4.6 Test case 5: activation in low power mode, ACT_POWER_MODE with FR=1, no session initializati... |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.5.5.2 Test case 1: pipe creation from host controller | Rel-7 M M M M M |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.5.5.3 Test case 2: pipe creation from another host | Rel-7 C102 C102 C102 C102 C102 |
915d49d66cb16af028532c3330e1bdcb | 102 695-2 | 5.5.5.4 Test case 3: processing of EVT_POST_DATA | Rel-7 M M M M M 5.6.3.3.4.2.2 Test case 1: Type A registry values Rel-7 SR8 C104 C104 C104 C104 C104 5.6.3.3.4.3.2 Test case 1: Type B registry values Rel-7 SR8 C105 C105 C105 C105 C105 5.6.3.3.4.5.2 Test case 1: Type F registry values Rel-7 SR8 C106 C106 C106 C106 C106 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.