hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
e86401852833419ce79b64126702606c
|
123 054
|
5.5 Modifications in a connection
|
.......................................................................................................................... 20
|
e86401852833419ce79b64126702606c
|
123 054
|
5.5.1 Channel Mode Modify (CMM)
|
.................................................................................................................. 20
|
e86401852833419ce79b64126702606c
|
123 054
|
5.5.2 User initiated resource up- and down grading
|
............................................................................................ 21
|
e86401852833419ce79b64126702606c
|
123 054
|
5.5.3 Network Resource up- and downgrading
|
................................................................................................... 21
|
e86401852833419ce79b64126702606c
|
123 054
|
5.6 Release
|
............................................................................................................................................................. 22
|
e86401852833419ce79b64126702606c
|
123 054
|
5.7 Negotiation of parameters
|
................................................................................................................................ 22
|
e86401852833419ce79b64126702606c
|
123 054
|
5.8 Inter MSC handover
|
......................................................................................................................................... 22
|
e86401852833419ce79b64126702606c
|
123 054
|
5.9 Reset
|
................................................................................................................................................................ 22
|
e86401852833419ce79b64126702606c
|
123 054
|
6 SIWF and Supplementary Services
|
.......................................................................................................22
|
e86401852833419ce79b64126702606c
|
123 054
|
6.1 Number Identification Supplementary Services
|
.............................................................................................. 23
|
e86401852833419ce79b64126702606c
|
123 054
|
6.2 Call Offering Supplementary Services
|
............................................................................................................ 23
|
e86401852833419ce79b64126702606c
|
123 054
|
6.3 Call Waiting (CW)
|
........................................................................................................................................... 23
|
e86401852833419ce79b64126702606c
|
123 054
|
6.4 Closed User Group (CUG)
|
.............................................................................................................................. 23
|
e86401852833419ce79b64126702606c
|
123 054
|
6.5 User-to-User Supplementary Services
|
............................................................................................................. 23
|
e86401852833419ce79b64126702606c
|
123 054
|
6.6 Charging Supplementary Services
|
................................................................................................................... 23
|
e86401852833419ce79b64126702606c
|
123 054
|
6.7 Call Restrictions
|
............................................................................................................................................... 23
|
e86401852833419ce79b64126702606c
|
123 054
|
6.8 Support of Private Numbering Plan (SPNP)
|
.................................................................................................... 23
|
e86401852833419ce79b64126702606c
|
123 054
|
6.9 Call Completion on Busy Subscriber (CCBS)
|
................................................................................................. 23 ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 4 3G TS 23.054 version 3.0.0
|
e86401852833419ce79b64126702606c
|
123 054
|
7 Interaction with CAMEL
|
.......................................................................................................................23
|
e86401852833419ce79b64126702606c
|
123 054
|
8 Operation and Maintenance Aspects
|
.....................................................................................................24
|
e86401852833419ce79b64126702606c
|
123 054
|
9 Charging
|
.................................................................................................................................................24
|
e86401852833419ce79b64126702606c
|
123 054
|
10 Interception
|
............................................................................................................................................24 Annex A: Change history......................................................................................................................25 History..............................................................................................................................................................26 ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 5 3G TS 23.054 version 3.0.0 Foreword This Technical Specification has been produced by the 3GPP. This specification defines the stage 2 for the introduction of a Shared Inter Working Function within the 3GPP system. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 6 3G TS 23.054 version 3.0.0 1 Scope The present document defines the stage two description of the Shared Inter Working Function (SIWF) on Global System for Mobile communications (GSM). A stage one description does not exist because this service is not visible to the service subscribers and users. This stage two identifies the functional Capabilities and information flows needed to support the service. The signalling system protocols and switching functions needed to implement this service are defined in the relevant specifications. Interworking with other networks (e.g. PSTN) needs the presence of specific functions associated with the MSC, known as interworking functions (IWF). The IWFs depend on the type of network with which it is desired to interconnect and the type of service desired. A Shared Inter Working Function is a network function that may be used by any MSC in the same PLMN to provide interworking for a data/fax call. Whereas an IWF can only be used by its MSC, the SIWF can be used by several other network nodes e.g. any MSC within the same PLMN (the concept is not limited to a certain number of MSCs). SIWF is applied to data services in GSM Phase 2 and GSM Phase 2+ (as defined in GSM 02.02, GSM 02.03 and GSM 02.34). The usage of a SIWF requires no additional manipulation at the MS. There is an interest to have a Shared Interworking Function (SIWF) for the following reasons: - possibility to fabricate/obtain the specific functionality needed for data services in areas where data traffic is expected to be low, - handling of data calls in case of local overload of the data traffic, - quick introduction and roll-out of new data services. 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. β’ For a non-specific reference, the latest version applies. β’ A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.02: "Digital cellular telecommunications system (Phase 2+); Bearer Services (BS) supported by a GSM Public Land Mobile Network (PLMN)". [3] GSM 02.03: "Digital cellular telecommunications system (Phase 2+); Teleservices supported by a GSM Public Land Mobile Network (PLMN)". [4] GSM 02.04: "Digital cellular telecommunications system (Phase 2+); General on supplementary services". [5] GSM 02.33: "Digital cellular telecommunication system (Phase 2+); Lawful interception - Stage 1". [6] GSM 02.34: "Digital cellular telecommunication system (Phase 2+); High Speed Circuit Switched Data (HSCSD) - Stage 1". ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 7 3G TS 23.054 version 3.0.0 [8] GSM 03.34: "Digital cellular telecommunication system (Phase 2+); High Speed Circuit Switched Data (HSCSD); Stage 2 Service Description". [9] GSM 03.45: "Digital cellular telecommunications system (Phase 2+); Technical realization of facsimile group 3 transparent". [10] GSM 07.01: "Digital cellular telecommunications system (Phase 2+); General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". [11] GSM 09.05: "Digital cellular telecommunications system (Phase 2+); Interworking between the Public Land Mobile Network (PLMN) and the Packet Switched Public Data Network (PSPDN) for Packet Assembly/Disassembly facility access (PAD)". [12] GSM 09.06: "Digital cellular telecommunications system (Phase 2+); Interworking between a Public Land Mobile Network (PLMN) and a Packet Switched Public Data Network/Integrated Services Digital Network (PSPDN/ISDN) for the support of packet switched data transmission services". [13] GSM 09.07: "Digital cellular telecommunications system (Phase 2+); General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". [14] ETS 300 102-1: "Integrated Services Digital Network (ISDN); User-network interface layer 3 Specifications for basic call control". 3 Definitions and Abbreviations 3.1 Definitions For the purposes of the present document, the following definitions apply: Visited MSC: The MSC which is responsible for handling calls involving the mobile. In the description of inter-MSC handover in GSM 03.09 this is the MSC referred to as "MSC-A" (controlling MSC). K Interface: The interface between the visited MSC and an SIWFS. 3.2 Abbreviations For the purposes of the present document, the the following abbreviations apply: CD Call Direction. CDo Call Direction at Call Set-up. CDm Call Direction modify. DRM Data call Routeing Mechanism IWF Inter Working Function IWU Inter Working Unit. MSC/SIWFS An MSC with an implemented SIWF Server. SIWF Shared Interworking Function. SIWFC Shared Inter Working Function Controller. Additional functionality in the visited MSC for the support of SIWFS. SIWFS SIWF Server. SIWFS is the entity where the used IWU is located. Other abbreviations used in the present document are listed in GSM 01.04. ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 8 3G TS 23.054 version 3.0.0 4 Architecture 4.1 General An IWF provides specific functions associated with the visited MSC for the interworking with other networks. It comprises signalling and traffic channel related functions. The traffic channel related functions are provided by an Inter Working Unit (IWU). The SIWF concept is that it provides specific functions for the interworking with other networks. It comprises signalling and traffic channel related functions. Whereas the signalling related functions are associated with the visited MSC, the IWU providing the traffic channel related functions has another physical location. The entity that contains all additional functions needed in the visited MSC to provide the SIWF is called SIWF Controller (SIWFC). The entity where the IWU is located is called SIWF Server (SIWFS). The Interface between a visited MSC and a SIWFS is called the K Interface. SIWFS can be provided by a MSC (MSC/SIWFS) or by another network entity (stand alone SIWFS). Figure 1 shows the network configuration. SIWF SERVER MSC/VLR/(IWF) A interface K interface Fixed Network MS DTE BSS SIWF CONTROLLER Figure 1: Network configuration 4.2 Routeing principles The call is routed according to the following principles: - a loop i.e. DTE - MS - BSS - visited MSC - SIWF Server - visited MSC - Fixednetwork. This is applicable for both mobile originating or mobile terminating calls. This is called the Loop Method. (Figure 2) - a non-loop i.e. DTE - MS - BSS - visited MSC - SIWF Server - Fixed network. This is only applicable for mobile originating calls. This is called the Non Loop Method. (Figure 3). The signalling link between the MSC with SIWFC and the SIWFS is used for normal circuit switched signalling and for conveying additional controlling information via MAP signalling. ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 9 3G TS 23.054 version 3.0.0 SIWF SERVER MSC/VLR/(IWF) A interface Fixed Network K interface βaβ βnβ SIWF CONTROLLER Signalling link Figure 2: The Loop Method. The traffic circuits βaβ and βnβ, where βaβ is used to send and receive data between MS and SIWF Server and βnβ is used to send and receive data of the fixed network SIWF SERVER MSC/VLR/(IWF) A interface Fixed Network K interface βaβ SIWF CONTROLLER Signalling link Figure 3: The Non Loop Method. The traffic circuit βaβ is used to send and receive data between MS and SIWF Server ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 10 3G TS 23.054 version 3.0.0 4.3 Visited MSC with additional SIWF functionality (SIWFC) The visited MSC is responsible for allocation of an IWF or a SIWFS. In the case the visited MSC has the additional functions required to provide a SIWF, this additional functionality in the visited MSC is called SIWFC. SIWFC is a logical part of the MSC. The visited MSC examines IWF Capabilities based on the service request and available resources. The visited MSC comprises of functions for selection of an appropriate SIWFS and the allocation of the traffic channels depending on the SIWF type. In addition to the GSM phase 2 MSC responsibility, the visited MSC including SIWFC is responsible for: - The analysis for the selection of an appropriate SIWFS is based on the contents in the information received during call set-up. For this purpose the Visited MSC has the knowledge of routeing information to SIWFS and the service Capabilities on each SIWFS. - In addition the operator may specify conditions for redirection. - The examination results in that either the MSC/IWF is used (if such exist) or that the call is redirected to a SIWFS. - In case the analysis results in that the call shall be routed to a SIWFS, the visited MSC allocate βaβ- circuits for mobile originating calls and βnβ circuits for mobile terminating calls to be used between the MSC and the SIWFS, and establishing a connection to the SIWFS. - The MSC determines via the signalling to the SIWFS, how the call shall be routed i. e. either back to the visited MSC (loop method) or to the final destination (non loop method). This indication is sent in a MAP Procedure. - By-passing the SIWFS connection in the Speech part of Alternate services. The visited MSC may or may not contain an IWF. 4.4 SIWFS - Shared Inter Working Function Server 4.4.1 General The logical entity that contains the IWU is called SIWF Server (SIWFS). It offers IWU to remotely located MSCs. The IWU provides the traffic channel related functions. SIWFS contains also the DRM which is needed for the additional signalling between entities involved i.e. the visited MSC and the SIWFS. See figure 4. SIWFS is responsible for: - allocation of βnβ-circuit for mobile originating calls and βaβ-circuit for mobile terminating calls to be used to the MSC. - signalling interworking to ISDN, PSTN and (PS)PDN, allocation of resources towards the fixed network in case the non Loop Method is used. An operator can decide to concentrate all the data/fax traffic to one specific SIWFS. The physical location of the SIWFS can be an MSC or in another network entity. In the case the SIWFS is implemented in an MSC it is denominated MSC/SIWFS. ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 11 3G TS 23.054 version 3.0.0 SIWF DRM IWU Figure 4: The logical entity SIWFS 4.4.2 IWU The IWUs in SIWFS have the same functions as the existing IWFs The responsibility by the IWU concerns the traffic handling functions e.g. - Interworking between the rate adapted A interface frames carrying the user data and the signals on the fixed network circuits. - Data interworking in the transparent and non transparent mode e.g. modems, V.110 frames, RLP, the handling of fax protocol and handling of network based datacompression. 4.4.3 Data call Routeing Mechanism (DRM) The DRM is a logical function which supports the handling of calls in SIWFS. DRM is used for examination of service request and available resources for the support of data/fax call in SIWFS. The examination results in that either the call is accepted and that the IWU is connected or that the call is rejected. The DRM receives information whether the call is to be routed in a Loop (back to the visited MSC) or as Non Loop (directly to the final destination) via the signalling from the visited MSC. The SIWFS shall have routeing cababilities but it has no own routeing alternatives. 4.5 K Interface and Signalling The link between the visited MSC and the SIWFS supports signalling functions and functions for the transport of traffic. In addition the link supports signalling functions to control the SIWFS i.e. IWU located in the selected SIWFS. The traffic channel supports that a circuit will be used to send and receive data in the A interface format and will be called 'a' circuit. Another circuit will be used to send and receive data in the format of the fixednetwork and will be called 'n' circuit. The circuits βaβ and βnβ consist of one 64kbps channel each. The signalling channel supports e. g. ISUP i.e. the signalling between the visited MSC and the SIWFS by using e. g. ISUP. The checking and the mapping of information element parameters of the GSM 04.08 signalling take place in the visited MSC in accordance with GSM 09.07. The signalling on the K Interface requires additional controlling signalling. This signalling is handled by a MAP procedure. The MAP Procedures supports at least submission of all GSM-BC, all ISDN-BC (09.07), A-Number, B- Number and CMM. The MAP Dialogue is open throughout the call. 4.6 Fixed Network Fixed network can be any network with which GSM PLMN is interworking for data services. Requirements on fixed networks are outside the scope of the present document. ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 12 3G TS 23.054 version 3.0.0 5 Procedures 5.1 General A visited MSC uses its capabilities to direct data/fax calls to a SIWFS. This is applicable for both mobile originating and mobile terminating data calls. A loop method is used, where the data traffic is redirected from the visited MSC to the SIWFS, adapted, and then re-routed back to the visited MSC for routeing to the final destination. Mobile originated calls can also use a non-loop method i.e. the calls can be routed directly from the SIWFS to the final destination. Transit traffic through an SIWFS to another SIWFS is not allowed. The call flows in chapter 5 are all examples based on ISUP/MAP signalling. The general principle by conveying all GSM-BC, converted ISDN BC (from GSM-BC), Call Direction (CD) and associated information like HLC and LLC (not showed in the call flows) by MAP procedures from the visited MSC to the SIWFS, result in that also less intelligent signalling protocol than ISUP can be used between the visited MSC and the SIWFS e. g. TUP. The general principle result in that ISUP (or TUP) is simple used for the handling of the required PCM channels between the visited MSC and the SIWFS. 5.2 Mobile Originated calls This subclause describes the procedure used to establish a connection to the SIWFS for a Mobile Originated call. Mobile originated calls shall follow the normal call set-up procedures. No additional manipulation at the MS is needed. If the visited MSC decides to use an SIWF it uses its SIWFC to route the call towards an SIWFS. This includes: - selection of an appropriate SIWFS. - sending a request to the SIWFS. - waiting for an acknowledgement from the SIWFS. - routeing the call to the SIWFS and allocating an βaβ -circuit to this entity. The SIWFS can be accessed after the negotiation of the GSM BC parameters and the allocation of radio resources in the visited MSC. The visited MSC decides the selection of a SIWFS after the ASSIGNMENT COMPLETE has been received. The selection of an appropriate SIWFS or MSC/IWF is based - on the relevant parameters in the signalling messages (SETUP, CALL PROCEED and ASSIGNMENT COMPLETE), - on status information from IWF and SIWFS (e.g. IWU busy or congested, IWU out of order, etc.) together with normal route supervision and - on further criteriaβs that can be determined by the operator (e.g. conditions for routeing). ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 13 3G TS 23.054 version 3.0.0 The visited MSC allocate a temporary V-MSC address (V-MSC-Addr) similar to MSRN (E.164 number). This address will be used by the visited MSC to correlate the incoming IAM messages from SIWFS. The visited MSC sends a request to the selected SIWFS by means of a MAP_Provide_SIWFS_Number procedure. The MAP_Provide_SIWFS_Number procedure contains all information needed for the SIWFS to evaluate the requirement and to select and to seizure an appropriate IWU. In particular, these information are - V-MSC-Addr/B-SubscrAddr: The address (an E.164 number) where the SIWFS has to route the call. In the case of the loop method it is the address of the visited MSC and in the case of the non-loop method it is the address of the B-subscriber. - GSM-BCβ: The GSM-BC negotiated with the MS. - ISDN-BCn: The ISDN-BC mapped from the GSM-BCβ. It is used by the SIWFS to route the call and to allocate an βnβ-circuit (loop method) or a traffic channel towards the fixed network (non-loop method). - CD: Call Direction to indicate the direction at call set-up (MOC/MTC) - Chosen Channel: The Chosen Channel specifies the assigned radio channel. The visited MSC waits for the acknowledgement MAP_Provide_SIWFS_Number_Ack. The SIWFS assigns and returns a temporary SIWFS address (similar to MSRN), an E.164 number. This address will be used by the visited MSC to route the call, i.e. the IAM to the SIWFS and it will be used by the SIWFS to correlate the incoming IAM to the corresponding MAP message MAP_Provide_SIWFS_Number (i.e. Call Reference). The SIWFS sends the acknowledgement MAP_Provide_SIWFS_Number_Ack back to the visited MSC. If the acknowledgement is negative (possibly indicated via the MAP procedure), the visited MSC may release the call or it may select an alternative SIWFS. The number of routeing alternatives is an implementation issue and not a part of the present document. If the acknowledgement is positive, the visited MSC will set-up an βaβ circuit towards the SIWFS. For that it uses an appropriate ISDN-BCa and the transmission medium requirements set to β64 kbit/s unrestricted". If no valid response is received in the ISUP-signalling the visited MSC may select an alternative route to the same SIWFS, release the call or it may select an alternative SIWFS. The number of routeing alternatives is an implementation issue and not a part of the present document. Normal ISUP signalling follows. The SIWFS routes the call to the address that it has got from the visited MSC. In the case of the loop method it is the address of the visited MSC and in the case of the non-loop method it is the address of the B-subscriber. These addresses are conveyed as parameter in the message MAP_Provide_SIWFS_Number. So, the SIWFS routes the call to the visited MSC and allocates an βnβ-circuit towards the visited MSC in the case of the loop method or it routes the call directly towards the fixed network. If the call routeing is not possible it releases the call by ISUP means. Hence, the selection of the loop or non-loop method - is transparent for the SIWFS and - is controlled by the visited MSC by providing the appropriate address to the SIWFS. In case the non loop method is used for dedicated PAD or dedicated Packet Access (BS4x or BS5x) calls, the call proceeds in accordance with GSM 09.05 or GSM 09.06. Acknowledgement is sent to the visited MSC. Acknowledgement and Answer for the call may have to be generated by the SIWFS. There is one restriction: - Dual services are only supported together with the loop method. Normal ISUP signalling follows. When the SIWFS receives the ISUP Answer message it activates the IWU. In the case of a dual service the SIWFS will be selected and activated either if the first GSM-BC does not indicate speech or if in speech position and an in-call modification is ordered by the MS. ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 14 3G TS 23.054 version 3.0.0 5.2.1 Call flow MOC (Loop Method) ISDN MS V-MSC SIWFS Setup [B-SubscrAddr, GSM-BC] Call Proc [GSM-BCβ] MAP_Provide_SIWFS_Number_Req [V-MSC-Addr, GSM-BCβ, ISDN-BCn, CD, ChosenChannel] AssignmentReq[ChannelType] AssignmentComplete[ChoosenChannel] MAP_Provide_SIWFS_Number_Ack [SIWFS-Addr] IWU selection IAM [B-SubscrAddr, ISDN-BCn] ACM Answer Alerting Connect ACM Answer ACM Answer IAM [V-MSC-Addr, ISDN-BCn] Connected IAM [SIWF-Addr, ISDN-BCa] IWU activation Connect Ack Figure 5: Call flow for MOC in the case of the loop method ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 15 3G TS 23.054 version 3.0.0 5.2.2 Call flow for MOC (Non Loop Method) ISDN MS V-MSC SIWFS Setup [B-SubscrAddr, GSM-BC] Call Proc [GSM-BCβ] MAP_Provide_SIWFS_Number_Req [B-SubscrAddr, GSM-BCβ, ISDN-BCn, CD, ChosenChannel] AssignmentReq[ChannelType] AssignmentComplete[ChoosenChannel] MAP_Provide_SIWFS_Number_Ack [SIWFS-Addr] IAM [SIWFS-Addr, ISDN-BCa] IWU selection IAM [B-SubscrAddr, ISDN-BCn] Answer Alerting Connect ACM ACM Answer Connected IWU activation Connect Ack Figure 6: Call flow for MOC in the case of the non-loop method NOTE: In some PAD or PH interworking schemes (defined in GSM 09.05 and 09.06), the ISUP signals between SIWFS and ISDN are not used for Dedicated Services (Bearer Services 4x and 5x). In this case ACM and Answer have to be generated by SIWFS towards the visited MSC. 5.3 Mobile Terminated calls This subclause describes the procedure used to establish a connection to the SIWFS for a Mobile Terminated call. For MTC, the routeing is based either on associated information to call set-up (PSTN case) or contents in IAM. GMSC interrogates HLR for roaming number and HLR interrogate VLR due to the B-number. The VLR provides the MSRN in accordance with normal procedures. See GSM 09.07. If the visited MSC decides to use an SIWF it uses its SIWFC to route the call towards an SIWFS. This includes: - selection of an appropriate SIWFS; - sending a request to the SIWFS; - waiting for an acknowledgement from the SIWFS; - routeing the call to the SIWFS and allocating an βnβ -circuit to this entity. ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 16 3G TS 23.054 version 3.0.0 The SIWFS can be accessed after the negotiation of the GSM BC parameters and the allocation of radio resources in the visited MSC. The visited MSC decides the selection of a SIWFS after the ASSIGNMENT COMPLETE has been received. The usage of single or multinumbering scheme will not result in different handling of the Mobile Terminating call as the selection of the SIWFS only can be made after this procedure. The selection of an appropriate SIWFS or MSC/IWF is based - on the relevant parameters in the signalling messages (IAM, CALL CONFIRMED and ASSIGNMENT COMPLETE); - on status information from IWF and SIWFS together with normal route supervision. The visited MSC allocate a temporary V-MSC address (V-MSC-Addr) similar to MSRN (E.164 number). This address will be used by the visited MSC to correlate the incomung IAM messages from SIWFS. The visited MSC sends a request to the selected SIWFS by means of a MAP_Provide_SIWFS_Number procedure. The MAP_Provide_SIWFS_Number procedure contains all information needed for the SIWFS to evaluate the requirement and to select and to seizure an appropriate IWU. In particular, these information are - V-MSC-Addr: The address, an E.164 number, where the SIWFS has to route the call i.e. the address of the visited MSC. - GSM-BCβ: The GSM-BC negotiated with the MS. - ISDN-BCn: The ISDN-BC received from the fixed network. The ISDN-BCa used to allocate an βaβ-circuit to the visited MSC will be generated internally by using the ISDN-BCn. - CD: Call Direction to indicate the direction at call set-up (MOC/MTC) - Chosen Channel: The Chosen Channel specifies the assigned radio channel. The visited MSC waits for the acknowledgement MAP_Provide_SIWFS_Number_Ack. The SIWFS assigns and returns a temporary SIWFS address (similar to MSRN), an E.164 number. This address will be used by the visited MSC to route the call, i.e. the IAM to the SIWFS and it will be used by the SIWFS to correlate the incoming IAM to the corresponding MAP message - MAP_Provide_SIWFS_Number (i.e. Call Reference). The SIWFS sends the acknowledgement MAP_Provide_SIWFS_Number_Ack back to the visited MSC. If the acknowledgement is negative (possibly indicated via the MAP procedure), the visited MSC may release the call or it may select an alternative SIWFS. The number of routeing alternatives is an implementation issue and not a part of the present document. If the acknowledgement is positive, the visited MSC will set-up an βnβ circuit towards the SIWFS. For that it uses the ISDN-BCn received from the fixed network. If no valid response is received in the ISUP-signalling the visited MSC may select an alternative route to the same SIWFS, release the call or it may select an alternative SIWFS. The number of routeing alternatives is an implementation issue and not a part of the present document. The SIWFS routes the call to the address that it has got from the visited MSC, i.e. the address of the visited MSC. This address is conveyed as parameter in the message MAP_Provide_SIWFS_Number. So, the SIWFS routes the call to the visited MSC and allocates an βaβ-circuit towards the visited MSC. For that it uses an appropriate ISDN-BCa with the transmission medium requirements set to "64 kbit/s unrestricted". If the call routeing is not possible it releases the call by ISUP means. Normal ISUP signalling follows. Note that the signals ALERT and CONNECT are independant of the ISUP signalling between V-MSC and SIWFS. In the case that these signals are received from the MS before IAM is received from SIWFS, the V-MSC withholds the signals until IAM from SIWFS is received before sending ANSWER to SIWFS. When the SIWFS receives the ISUP Answer message it activates the IWU. In the case of a dual service, the SIWFS will be selected and activated either if the first GSM-BC does not indicate speech or if in speech position and an in-call modification is ordered by the MS. ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 17 3G TS 23.054 version 3.0.0 5.3.1 Call flow for MTC (Loop Method) MS V-MSC SIWFS Setup [B-SubscrAddr, GSM-BC] Call Conf [GSM-BCβ] MAP_Provide_SIWFS_Number req. [V-MSC-Addr, GSM BCβ, ISDN-BCa, CD, ChosenChannel] AssignmentReq[ChannelType] AssignmentComplete[ChoosenChannel] IAM [B-SubscrAddr, ISDN-BCn] MAP_Provide_SIWFS_Number resp. [SIWFS-Addr] ACM Answer ACM Answer Alerting Connect IAM [SIWFS-Addr, ISDN-BCn] IAM [V-MSC-Addr, ISDN-BCa] ACM ConnectAck Answer IWU selection Connected IWU activation Figure 7: Call flow for MTC in the case of the loop method 5.3.2 Call Flow for MTC (Non-Loop Method) The non-loop method is not defined for mobile terminated calls. 5.4 In Call Modification (ICM) This subclause describes the procedure used to handle In Call Modification (ICM). ICM is applicable for Alternate Speech/fax (TS61), Alternate Speech/data (BS61) and Speech followed by data (BS81). In general the loop between the visited MSC and the SIWFS is only established when a dual service is in data/fax mode. In the case when no resources are available at an ICM, the call will proceed in its existing mode, e.g. if no IWF resources are idle when going from speech to fax, the call will proceed in speech mode. ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 18 3G TS 23.054 version 3.0.0 5.4.1 Call in Data/Fax Mode The visited MSC that receives a MODIFY (GSM-BC, RCD) for a dual service in data/fax mode and accepts the ICM request, results in that the SIWFS connection is by-passed i.e. - the loop to SIWFS is released; - the MAP Dialogue is closed. This procedure is independent whether the call originally has been established as MOC or MTC. The parameter RCD (Reverse Call Direction) is normally transformed according to figure 8. For release it may be omitted. When receiving the next ICM (return-to-data ICM) the visited MSC re-connect the SIWFS connection in accordance with subclause 5.4.2. This SIWFS connection may not be the same as the previous one. 5.4.2 Call in Speech Mode The visited MSC that receives a MODIFY (GSM-BC, RCD) for a dual service in Speech mode and accepts the ICM request, and which decides to use an SIWF, results in that a loop to the SIWFS is established. The procedure is similar to Mobile Originated Call (Subclause 5.2) and Mobile Terminated Call (Subclause 5.3). This includes: - selection of an appropriate SIWFS; - sending a request to the SIWFS; - waiting for an acknowledgement from the SIWFS; - routeing the call to the SIWFS and allocating an βaβ or βnβ -circuit to this entity. The visited MSC decides the selection of a SIWFS after the ASSIGNMENT COMPLETE has been received. The selection of an appropriate SIWFS or MSC/IWF is based - on the relevant parameters in the signalling messages (MODIFY and ASSIGNMENT COMPLETE); - on status information from IWF and SIWFS together with normal route supervision; - on further criteriaβs that can be determined by the operator (e.g. conditions for routeing). The visited MSC allocate a temporary V-MSC address (V-MSC-Addr) similar to MSRN (E.164 number). This address will be used by the visited MSC to correlate the incoming IAM messages from SIWFS. The visited MSC sends a request to the selected SIWFS by means of a MAP_Provide_SIWFS_Number procedure. The MAP_Provide_SIWFS_Number procedure contains all information needed for the SIWFS to evaluate the requirement and to select and to seizure an appropriate IWU. In particular, these information are - V-MSC-Addr: The address, an E.164 number, where the SIWFS has to route the call i.e. the address of the visited MSC; - GSM-BC: The GSM-BC in the MODIFY MESSAGE; - ISDN-BC: The ISDN-BC mapped from the GSM-BC (MOC) or received from the fixed network (MTC); - CDm: Call Direction to indicate the direction at call set-up (MOC/MTC) for the loop. It is derived from the original call set-up direction (CDo) and from the value of the reverese data Call Direction (RCD) parameter of the MODIFY message (see figure 8). - Chosen Channel: The Chosen Channel specifies the assigned radio channel. The visited MSC waits for the acknowledgement MAP_Provide_SIWFS_Number_Ack. The SIWFS assigns and returns a temporary SIWFS address (similar to MSRN), an E.164 number. This address will be used by the visited MSC to route the call, i.e. the IAM to the SIWFS and it will be used by the SIWFS to correlate the incoming IAM to the corresponding MAP message MAP_Provide_SIWFS_Number (i.e. Call Reference). The SIWFS sends the acknowledgement MAP_Provide_SIWFS_Number_Ack back to the visited MSC. ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 19 3G TS 23.054 version 3.0.0 If the acknowledgement is negative (possibly indicated via the MAP procedure), the visited MSC may release the call or it may select an alternative SIWFS. The number of routeing alternatives is an implementation issue and not a part of the present document. If the acknowledgement is positive, the visited MSC will set-up an βaβ- circuit (if CDm = MOC) or an βnβ- circuit (if CDm = MTC) towards the SIWFS. The ISDN-BC1or ISDN-BC2 used for allocating the βnβ-circuit indicates a "UDI" connection, the transmission medium requirement for the βaβ-circuit is set to "64 kbit/s unrestricted". If no valid response is received in the ISUP-signalling the visited MSC may select an alternative route to the same SIWFS, release the call or it may select an alternative SIWFS. The number of routeing alternatives is an implementation issue and not a part of the present document. Normal ISUP signalling follows. The IAM to SIWFS contains ISDN-BC1, which is determined in accordance with figure 9. The SIWFS routes the call to the address that it has got from the visited MSC i.e. the address of the visited MSC. This address is conveyed as parameter in the message MAP_Provide_SIWFS_Number. So, the SIWFS routes the call to the visited MSC and allocates an βaβ-circuit or an βnβ circuit towards the visited MSC. The βaβ- and βnβ-circuit depends on the value CDm in the MAP_Provide_SIWFS_Number_Req. If the call routeing is not possible it releases the call by ISUP means. Normal ISUP signalling follows. The IAM to the visited MSC contains ISDN-BC2, which is determined in accordance with figure 9. When the SIWFS receives the ISUP Answer message it activates the IWU. CDo Modify RCD BC1 BC2 CDm MOC Reverse n a MTC MOC -- a n MOC MTC Reverse a n MOC MTC -- n a MTC Figure 8: Selection of the ISDN-BC1, ISDN-BC2 and CDm. These are dependant on the original Call Direction (CDo) and Reverse Call Direction Information Element (RCD-IE) of the MODIFY message ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 20 3G TS 23.054 version 3.0.0 5.4.3 Call Flow for ICM Procedure MS V-MSC SIWFS Modify [GSM-BC, RCD] MAP_Provide_SIWFS_Number_Req [V-MSC-Addr, GSM-BC, ISDN-BC, CDm, ChosenChannel] AssignmentReq[ChannelType] AssignmentComplete[ChoosenChannel] MAP_Provide_SIWFS_Number_Ack [SIWFS-Addr] ModifyComplete [GSM-BC] IWU selection ACM Answer ACM Answer IAM [V-MSC-Addr, ISDN-BC2] Connected IAM [SIWF-Addr, ISDN-BC1] IWU activation Figure 9: Call flow for In Call Modification procedure (change from speech to data/fax) 5.5 Modifications in a connection There are BSSAP messages and procedures that are relevant for the MSC/IWF and SIWFS, that are not mapped to any ISUP message. These are messages for modification on channel mode and messages for resource up- and downgrading. The MAP procedure MAP_SIWF_Signalling is used to convey these messages between the visited MSC and the SIWFS. 5.5.1 Channel Mode Modify (CMM) Channel Mode Modify (CMM) concerns TS61 and TS62. The purpose of CMM is to adjust the radio channel bit rate to match the message speed negotiated end-to-end between the fax machines. The CMM procedure is initiated by the FA/IWF. The procedures for CMM follow the procedures described in GSM 03.45. ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 21 3G TS 23.054 version 3.0.0 BSS V-MSC SIWFS MAP_SIWF_Signalling_Modify [Channel_Type] MAP_SIWF_Signalling_Modify [Chosen_Channel] AssignmentReq[ChannelType] AssignmentComplete[ChosenChannel] Figure 10: Call flow for Channel Mode Modify procedure 5.5.2 User initiated resource up- and down grading During a Non Transparent Multislot configuration the user may request the network to change the current maximum number of traffic channels and air interface user rate parameters. This procedure is described in GSM 03.34. When the visited MSC receives the changed configuration after ASSIGNMENT COMPLETE the IWU of the SIWFS is adjusted accordingly by means of MAP_SIWF_ Signalling procedure. MS/BSS V-MSC SIWFS ModifyComplete[GSM-BC] Modify[GSM-BC] MAP_SIWF_Signalling_Modify [ChosenChannel] MAP_SIWF_Signalling_Modify_Ack AssignmentReq[ChannelType] AssignmentComplete[ChosenChannel] IWU adjustment Figure 11: Call flow for user initiated resource up- and downgrading. MODIFYCOMPLETE may be sent either as shown in figure or immediately after MODIFY 5.5.3 Network Resource up- and downgrading During a call using a multislot configuration the Number of assigned traffic channels and/or the air interface user rate and/or the channel type may be modified. Also for a call using a singleslot configuration the assigned channel mode can change (e.g. from TCH/F to TCH/H or vice versa). When the visited MSC receives the changed configuration e. g. the message HANDOVER PERFORMED the IWU of the SIWFS is adjusted accordingly. ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 22 3G TS 23.054 version 3.0.0 BSS V-MSC SIWFS MAP_SIWF_Signalling_Modify [ChosenChannel] MAP_SIWF_Signalling_Ack HandoverPerformed[ChosenChannel] IWU adjustment Figure 12: Call flow for network Resource Up- and Downgrading 5.6 Release RELEASE follows the ISUP procedures. RELEASE may be initiated by either V-MSC or SIWFS by sending an ISUP REL message. The call is released and the MAP link between V-MSC and SIWFS is closed (MAP-CLOSE). 5.7 Negotiation of parameters The MSC is responsible for the negotiation and setting of parameters in accordance with GSM 07.01. The protocol on the K Interface supports the submission of all needed Bearer Capabilities (GSM and ISDN) in accordance with GSM 09.07. 5.8 Inter MSC handover In case of an inter MSC handover, the originally MSC i.e. the anchor MSC maintains the connection to and control of the SIWFS resources. Thus it is to be noted that in such cases, three MSCs are involved at the serving side of the call and the route from the MS is in the sequence MSCb-MSCa-SIWFS-MSCa- Fixed network (in the loop method case). 5.9 Reset RESET follows the ISUP procedures. RESET may be initiated by either V-MSC or SIWFS by sending an ISUP RSC message. The circuit is reseted and possible MAP link between the V-MSC and the SIWFS is closed (MAP-CLOSE). 6 SIWF and Supplementary Services Supplementary Services shall not be affected by the concept of the SIWF. The Supplementary Services applicable for data services are defined in GSM 02.04. NOTE: Supplementary Services may depend on the signalling system between visited MSC, fixed network and SIWFS. This dependence is described in other specifications and it is outside the scope of the present document. ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 23 3G TS 23.054 version 3.0.0 6.1 Number Identification Supplementary Services The parameters related to the number identification Supplementary Services are passed transparently through SIWFS as received in the signalling from visited MSC or fixed network. This is applicable for CLIP, CLIR, COLP and COLR. 6.2 Call Offering Supplementary Services In the case the call is a normal MTC and the B-subscriber does not answer, the call may be Call Forwarded on No Reply (CFNRy). This situation requires that the allocated resources are released, when the call is forwarded. CFU, CFB and CFNRc have no impact. 6.3 Call Waiting (CW) No impact. 6.4 Closed User Group (CUG) The parameters related to Closed User Group (CUG) are passed transparently through SIWFS as received in the signalling from visited MSC or fixed network. 6.5 User-to-User Supplementary Services The parameters related to User-to-User signalling are passed transparently through SIWFS as received in the signalling from visited MSC or fixed network. 6.6 Charging Supplementary Services No impact. This is applicable for AoCI and AoCC. 6.7 Call Restrictions No impact. This is applicable for the barring services e. g. BAOC, BOIC, BOIC-exHC, BAIC and BAIC-Roam. 6.8 Support of Private Numbering Plan (SPNP) No impact. 6.9 Call Completion on Busy Subscriber (CCBS) The parameters related to CCBS are passed transparently through SIWFS as received in the signalling from visited MSC or fixed networks. 7 Interaction with CAMEL Interaction with CAMEL is outside the scope of the present document. ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 24 3G TS 23.054 version 3.0.0 8 Operation and Maintenance Aspects The operators have the possibility to: - Set the parameters for conditional routeing. The following parameters can be used: A-Number, B-Number, Bearer Services and Tele Services. - Specify the routeing alternatives. 9 Charging A visited MSC, which have determined to use a SIWFS, is responsible for Charging. This is applicable both for Loop and Non Loop method. The service definition (stage 1) on Lawful Interception (GSM 02.33) states that all tele and bearer services are subject to interception. Provided that a mechanism for the interception of dataservice exists, interception is supported for both Loop or Non Loop method. ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 3GPP 3G TS 23.054 V3.0.0 (1999-05) 25 3G TS 23.054 version 3.0.0 Annex A: Change history Change history TSG CN# Spec Version CR <Phase> New Version Subject/Comment Apr 1999 GSM 03.54 6.0.0 Transferred to 3GPP CN1 CN#03 23.054 3.0.0 Approved at CN#03 ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) ETSI ETSI 26 ETSI ETSI TS 123 054 V3.0.0 (2000-01) (3G TS 23.054 version 3.0.0 Release 1999) History Document history V3.0.0 January 2000 Publication
|
25e662cc36570a64878ca898342df241
|
122 043
|
1 Scope
|
........................................................................................................................................................5
|
25e662cc36570a64878ca898342df241
|
122 043
|
2 References
|
................................................................................................................................................5
|
25e662cc36570a64878ca898342df241
|
122 043
|
2.1 Normative references
|
......................................................................................................................................... 5
|
25e662cc36570a64878ca898342df241
|
122 043
|
2.2 Informative references
|
....................................................................................................................................... 5
|
25e662cc36570a64878ca898342df241
|
122 043
|
3 Definitions and abbreviations
|
..................................................................................................................6
|
25e662cc36570a64878ca898342df241
|
122 043
|
3.1 Definitions
|
......................................................................................................................................................... 6
|
25e662cc36570a64878ca898342df241
|
122 043
|
3.3 Abbreviations
|
..................................................................................................................................................... 7
|
25e662cc36570a64878ca898342df241
|
122 043
|
4 Description
|
...............................................................................................................................................8
|
25e662cc36570a64878ca898342df241
|
122 043
|
4.1 Defining subscriber information for localised service ar
|
ea ............................................................................... 8
|
25e662cc36570a64878ca898342df241
|
122 043
|
4.2 Service Features
|
................................................................................................................................................. 8
|
25e662cc36570a64878ca898342df241
|
122 043
|
4.2.1 Localised service area indication
|
................................................................................................................. 8
|
25e662cc36570a64878ca898342df241
|
122 043
|
4.2.2 Localised service area support in idle mode (camping)
|
............................................................................... 9 4.2.3 Localised service area support in active mode (handover)........................................................................... 9
|
25e662cc36570a64878ca898342df241
|
122 043
|
4.2.4 Exclusive access
|
........................................................................................................................................... 9
|
25e662cc36570a64878ca898342df241
|
122 043
|
4.2.5 LSA only access
|
........................................................................................................................................... 9
|
25e662cc36570a64878ca898342df241
|
122 043
|
4.2.6 Preferential access
|
........................................................................................................................................ 9
|
25e662cc36570a64878ca898342df241
|
122 043
|
5 Impact on other services
|
..........................................................................................................................9
|
25e662cc36570a64878ca898342df241
|
122 043
|
5.1 General
|
............................................................................................................................................................... 9
|
25e662cc36570a64878ca898342df241
|
122 043
|
5.2 (Void)
|
.............................................................................................................................................................. 10
|
25e662cc36570a64878ca898342df241
|
122 043
|
5.3 GPRS
|
.......................................................................................................................................................... 10
|
25e662cc36570a64878ca898342df241
|
122 043
|
5.4 Call Forwarding
|
............................................................................................................................................... 10
|
25e662cc36570a64878ca898342df241
|
122 043
|
5.5 Completion of Calls to Busy Subscriber (CCBS)
|
............................................................................................ 10
|
25e662cc36570a64878ca898342df241
|
122 043
|
5 Exceptional procedures
|
..........................................................................................................................10
|
25e662cc36570a64878ca898342df241
|
122 043
|
6 Charging aspects
|
....................................................................................................................................10
|
25e662cc36570a64878ca898342df241
|
122 043
|
7 Commercial Role Model for SoLSA
|
.....................................................................................................11 Annex A: Change history......................................................................................................................12 ETSI ETSI TS 122 043 V3.1.0 (2000-06) 4 3G TS 22.043 version 3.1.0 Release 1999 Foreword This Technical Specification has been produced by the 3GPP. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; ETSI ETSI TS 122 043 V3.1.0 (2000-06) 5 3G TS 22.043 version 3.1.0 Release 1999 1 Scope This technical specification, specifies a mechanism, which can be used as a platform for providing special tariffs and/or special set of service features for certain subscribers within a regionally restricted area or areas. The motivation for this concept is to create means for network operators to build new service and tariff packages, which take into account subscriber groups and their needs. The localised service area is both an optional network feature and an optional UE feature. Usage and implementation of the different SoLSA service features may vary according to operator's service packages. This feature is not intended to replace the existing method of cell selection, cell indication and handover. βSupport of Localised service area (SoLSA)β is renamed Phase 2+ item βSupport of Home Area Priorityβ Note: The present document covers description for GERAN support only. UTRAN support will be added in latter releases. 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. - For a non-specific reference, the latest version applies. - A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. - For this Release 1999 document, references to GSM documents are for Release 1999 versions (version 8.x.y). 2.1 Normative references [1] TS 22.011: " Service accessibility ". 2.2 Informative references [3] TR 21.905: "Vocabulary for 3GPP Specifications". [4] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". ETSI ETSI TS 122 043 V3.1.0 (2000-06) 6 3G TS 22.043 version 3.1.0 Release 1999 3 Definitions and abbreviations 3.1 Definitions Localised Service Area (LSA): A localised service area consists of a cell or a number of cells within a PLMN. Cells being part of different localised service areas may have overlapping coverage areas. The cells constituting a localised service area may not necessarily provide continuous coverage. A LSA of four cells. An overlapping cell not part of LSA Figure 1: Localised Service Area Subscribed to LSA: Set of LSAs, which the user has subscribed to. Valid LSA: A LSA ,whichthe user has subscribed to and his UE can receive service. Current LSA: The LSA where a UE is receiving service. LSA Priority: Priority of subscriber's LSAs. When the user has several valid LSAs, the current LSA shall be selected by prioritising LSAs in case of overlapping LSAs. LSA "A" LSA "B" LSA "C" LSAs A, B and C are Subscribed to LSAs LSAs A and B are Valid LSAs LSA A is Current LSA = Subscriber Figure 2: Localised Service Areas LSA only access: LSA user is allowed to access PLMN within his allowed LSAs. LSA user is not allowed to receive and/or originate a call outside LSA area. ETSI ETSI TS 122 043 V3.1.0 (2000-06) 7 3G TS 22.043 version 3.1.0 Release 1999 LSA only access users are not allowed to receive and /or originate calls. LSA only access cells. All subscribed services available to user. Figure 3: LSA only access Exclusive Access: Access to exclusive access cells is restricted to defined LSA subscribers. Public cell, allowed for all users including exclusive access users. Private cell, only allowed for users with exclusive access. Figure 4: Exclusive Access Preferential Access: LSA user shall have preferential access to resources of LSA cells, compared to non-LSA users. Public cell, capacity allowed on equal basis for all users. Reserved resources for Preferential Access users. Limited capacity available to all other users. Figure 5: Preferential Access 3.3 Abbreviations For the purposes of the present document, the following abbreviations apply: LSA Localised Service Area Further abbreviations may be found in TR 21.905 [2] and GSM 01.04 [3]. ETSI ETSI TS 122 043 V3.1.0 (2000-06) 8 3G TS 22.043 version 3.1.0 Release 1999 4 Description The localised service area concept shall give the operator the basis to offer subscribers different services (e.g. tariffs or access rights) depending on the location of the subscriber. 4.1 Defining subscriber information for localised service area A subscriber can have up to 20 LSAs per PLMN. It shall be possible to assign localised service areas to subscribers. Subscriber may have service, which contains several LSAs potentially belonging to different PLMNs. There shall be means to allocate LSA priority to each subscriber independently by operator. Localised service areas for subscriber(s) may overlap, i.e. one cell may be part of several LSAs belonging to that subscriber. As an example, within a hierarchical cell structure, cells in different layers can constitute different localised service areas. A localised service area could be defined so that it is possible to establish flexible sized areas, which are applicable to - a very small localised service area ("home area" covering one or several cells dedicated e.g. to a residential subscriber or a company); or - a large area covering a part of the city (one or several location areas); or - a combination of these. Thus it is possible to use the various radio network configurations. The definition of location areas and the definition of localised service areas may be independent of each other. 4.2 Service Features Following service features are building blocks for SoLSA based services. It is up to the operator to decide which service features are required for a specific service. - Localised service area indication. - Localised service area support in idle mode (camping). - Localised service area support in active mode (handover). - LSA only access. - Exclusive access. - Preferential access. 4.2.1 Localised service area indication It shall be possible to assign a subscriber defined identifier by the operator to each LSA (alphanumeric text up to 10 characters), which can be provided to the user in idle and active mode. As a UE manufacturer option the user may assign an icon or another form of indication to each LSA. It shall be possible to indicate a change of localised service area during idle and active mode. The indication is a network option (activated/deactivated by the network). ETSI ETSI TS 122 043 V3.1.0 (2000-06) 9 3G TS 22.043 version 3.1.0 Release 1999 4.2.2 Localised service area support in idle mode (camping) The PLMN shall determine, which cells, belonging to the LSA, are to be favoured by the UE when camping. When camping on a cell in idle mode, the subscriber's mobile station shall use the information provided by the PLMN in selecting cells belonging to his localised service area. The mobile station shall have the ability to reselect a cell in a different LSA with higher priority. This favouring shall not degrade the overall service quality. There should be no extra delay in cell selection procedure. 4.2.3 Localised service area support in active mode (handover) The PLMN shall determine, which cells, belonging to the LSA, are to be favoured during active mode. The cells belonging to users LSAs shall be favoured at call setup and when handovers are carried out. This favouring shall not degrade the overall service quality. 4.2.4 Exclusive access For a cell belonging to one or more service areas and where only one or more specific subscribers shall have allowed access, other subscriberβs mobile stations shall be prevented from using the cell to obtain any service, other than TS12 (Emergency Calls). NOTE: This does not prevent other subscriber's mobile stations from camping on the cell to perform Location Updating. Handovers into cells belonging to localised service areas where only specific subscribers shall have allowed access, shall be possible to be prevented for other subscribers, if required by a SoLSA application. 4.2.5 LSA only access With access allowed only within one or more localised service areas, it shall be possible to prevent receiving and/or originating basic services from non-LSA cells. SMS and Supplementary service operations are allowed in all areas. It shall be possible to prevent handovers to cells not belonging to allowed localised service areas, if required by a SoLSA application. 4.2.6 Preferential access It shall be possible to allocate resources at call setup and during the active mode to LSA users, if required by a SoLSA application. NOTE: An example of a requirement: the last traffic channel is not allocated to non-LSA user or in case of congestion an ongoing call of a non-LSA user is released and replaced with a call of a LSA user. 5 Impact on other services 5.1 General SoLSA is not limited to specific services and there are no modifications necessary for existing services. In particular there shall be no impact to Emergency Call (TS12). LSA should be able to support all tele, bearer and supplementary services .There is no interaction to supplementary services except those specified below. ETSI ETSI TS 122 043 V3.1.0 (2000-06) 10 3G TS 22.043 version 3.1.0 Release 1999 5.2 (Void) 5.3 GPRS It shall be possible to apply SoLSA services independently to circuit switched services and to GPRS. LSA support in idle mode shall be specified for GPRS. The definition of routing areas and the definition of localised service areas shall be independent of each other. 5.4 Call Forwarding No interaction. NOTE: Operators should consider using tools such as ODB and CAMEL to control call forwarding functionality provided in conjunction with any SoLSA services. 5.5 Completion of Calls to Busy Subscriber (CCBS) LSA only access restrictions shall apply to CCBS recall. 5 Exceptional procedures None identified. 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 122 043 V3.1.0 (2000-06) 11 3G TS 22.043 version 3.1.0 Release 1999 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 commercial role model The actors of the SoLSA role model are defined below: - Home operator: The Home operator of a SoLSA subscriber is the owner of the SIM for this subscriber. As such, he is responsible for transferring the necessary SoLSA information to the subscriber SIM. He also holds the SoLSA subscriber information (e.g. in the HLR, CAMEL server, private network node). The Home operator has a commercial agreement with one or several SoLSA operators. A Home operator can be commercially the same entity as a SoLSA operator. - SoLSA operator: An operator is acting as a SoLSA operator for one SoLSA subscriber if he owns at least one Localised Service Area (LSA) for that subscriber. As such, when the user is attached to the SoLSA operator the SoLSA operator will provide the service for the SoLSA. One SoLSA operator can own a multiplicity of LSAs for a given SoLSA subscriber. A SoLSA operator has a commercial agreement with one or a multiplicity of Home operators (but maximum one per subscriber). A SoLSA operator can be commercially the same entity as the Home operator. - SoLSA subscriber: A SoLSA subscriber is a subscriber who has subscribed to one Home operator and at least one SoLSA operator (or said differently, who has an authorisation to receive services from at least one LSA). A SoLSA subscriber can have a subscription with a multiplicity of SoLSA operators. A subscriber has always a Home operator, but for example if he is allowed to have services only in LSAs, his Home operator and his SoLSA operator can be commercially the same entity. ETSI ETSI TS 122 043 V3.1.0 (2000-06) 12 3G TS 22.043 version 3.1.0 Release 1999 Annex A: Change history Change history TSG SA# Spec Versi on CR <Phase> New Version Subject/Comment Jun 1999 GSM 02.43 7.1.0 Transferred to 3GPP SA1 SA#04 22.043 3.0.0 SP-08 22.043 3.0.0 003 R99 3.1.0 Clarification of requirements and editorial changes 13 ETSI ETSI TS 122 043 V3.1.0 (2000-06) 3G TS 22.043 version 3.1.0 Release 1999 History Document history V3.0.1 January 2000 Publication V3.1.0 June 2000 Publication
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
1 Scope
|
........................................................................................................................................................ 7
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
2 References
|
................................................................................................................................................ 7
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
2.1 Normative references
|
......................................................................................................................................... 7
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
2.2 Void
|
.................................................................................................................................................................... 8
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
3 Definitions, symbols and abbreviations
|
................................................................................................... 8
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
3.1 Definitions
|
.......................................................................................................................................................... 8
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
3.2 Void
|
.................................................................................................................................................................... 8
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
3.3 Abbreviations
|
..................................................................................................................................................... 8
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
4 General requirements
|
............................................................................................................................... 8
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
5 Security requirements
|
............................................................................................................................... 8
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
5.1 File access conditions
|
......................................................................................................................................... 9
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
5.2 User authentication
|
............................................................................................................................................. 9
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
5.3 User data stored in ME
|
....................................................................................................................................... 9
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
5.4 Authentication
|
.................................................................................................................................................... 9
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
5.5 Data integrity of signalling elements
|
................................................................................................................ 10
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
5.6 User identity confidentiality
|
............................................................................................................................. 10
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
5.7 Length of security parameters
|
.......................................................................................................................... 10
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
6 Logical issues
|
......................................................................................................................................... 10
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
6.1 Application selection
|
........................................................................................................................................ 10
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
6.2 Simultaneous access
|
......................................................................................................................................... 10
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
7 Service Requirements
|
............................................................................................................................. 10
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
7.1 Void
|
.................................................................................................................................................................. 10
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
7.2 Data transfer
|
..................................................................................................................................................... 10
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
7.3 Application execution environment
|
................................................................................................................. 11
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
7.4 Profile exchange
|
............................................................................................................................................... 11
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
7.5 Version identification
|
....................................................................................................................................... 11
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
8 Physical Characteristics
|
.......................................................................................................................... 11
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
8.1 Void
|
.................................................................................................................................................................. 11
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
8.2 Void
|
.................................................................................................................................................................. 11
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
9 Electrical characteristics and transmission protocols
|
............................................................................. 11
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
9.1 Void
|
.................................................................................................................................................................. 12
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
10 Contents of the Elementary Files
|
........................................................................................................... 12
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
10.1 USIM information storage requirements
|
.......................................................................................................... 12
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
10.2 Phone Book
|
...................................................................................................................................................... 13
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
10.2.1 Support of two name fields per entry
|
.......................................................................................................... 13
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
10.2.2 Support of multiple phone numbers per entry
|
............................................................................................. 13
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
10.2.3 Support of email address
|
............................................................................................................................. 13
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
10.2.4 Support of user definable groupings
|
........................................................................................................... 13
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
10.2.5 Support of hidden entries
|
............................................................................................................................ 13
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
10.2.6 Number of entries
|
....................................................................................................................................... 13
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
10.2.7 Void
|
............................................................................................................................................................ 13
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
10.3 Storage of call details
|
....................................................................................................................................... 13
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
10.4 Void
|
.................................................................................................................................................................. 14
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
11 3G/GSM interworking
|
............................................................................................................................ 14
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
11.1 Void
|
.................................................................................................................................................................. 14 ETSI ETSI TS 121 111 V18.0.0 (2024-05) 4 3GPP TS 21.111 version 18.0.0 Release 18
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
11.2 3G subscribers in a GSM network
|
.................................................................................................................... 14
|
094ea52cbab75af19142b66f618387fa
|
121 111
|
12 Contact Manager
|
.................................................................................................................................... 14 Annex A (informative): Change history ............................................................................................... 17 History .............................................................................................................................................................. 18 ETSI ETSI TS 121 111 V18.0.0 (2024-05) 5 3GPP TS 21.111 version 18.0.0 Release 18 Foreword This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. In the present document, modal verbs have the following meanings: shall indicates a mandatory requirement to do something shall not indicates an interdiction (prohibition) to do something The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. should indicates a recommendation to do something should not indicates a recommendation not to do something may indicates permission to do something need not indicates permission not to do something The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. can indicates that something is possible cannot indicates that something is impossible The constructions "can" and "cannot" are not substitutes for "may" and "need not". will indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document will not indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document might indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document ETSI ETSI TS 121 111 V18.0.0 (2024-05) 6 3GPP TS 21.111 version 18.0.0 Release 18 might not indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document In addition: is (or any other verb in the indicative mood) indicates a statement of fact is not (or any other negative verb in the indicative mood) indicates a statement of fact The constructions "is" and "is not" do not indicate requirements. ETSI ETSI TS 121 111 V18.0.0 (2024-05) 7 3GPP TS 21.111 version 18.0.0 Release 18 1 Scope This document defines the requirements of the USIM (Universal Subscriber Identity Module) and the IC card for 3G (UICC). These are derived from the service and security requirements defined in TS 22.100 [1] and TS 22.101 [2]. The USIM is a 3G application on an IC card. It inter-operates with a 3G terminal and provides access to 3G services. This document is intended to serve as a basis for the detailed specification of the USIM and the UICC, and the interface to the 3G terminal. 2 References 2.1 Normative 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. - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. [1] 3GPP TS 22.100 v3.x.x: "UMTS phase 1" (Release 99). [2] 3GPP TS 22.101: "Service principles". [3] 3GPP TS 31.101: "UICC-Terminal Interface; Physical and Logical Characteristics". [4] Void. [5] ETSI TS 101 220: "ETSI Numbering System for AIDs". [6] 3GPP TS 31.111: "USIM Application Toolkit (USAT)". [7] 3GPP TS 33.102: "3G Security: Security Architecture". [8] 3GPP TS 51.011, Rel-4: "Specification of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface". [9] Void. [10] Void. [11] ISO/IEC 7816-3: "Information technology - Identification cards - Integrated circuit(s) cards with contacts - Part 3: Electronic signals and transmission protocols". [12] ISO/IEC 7816-4: "Identification cards - Integrated circuit cards, Part 4: Organization, security and commands for interchange". [13] Void. [14] 3GPP TS 36.306: "Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities" ETSI ETSI TS 121 111 V18.0.0 (2024-05) 8 3GPP TS 21.111 version 18.0.0 Release 18 2.2 Void 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the following definitions apply: 3.2 Void 3.3 Abbreviations For the purposes of the present document, the following abbreviations apply: ADN Abbreviated Dialling Number ATR Answer To Reset DF Dedicated File EF Elementary File ICC Integrated Circuit Card IK Integrity Key IMSI International Mobile Subscriber Identity ME Mobile Equipment MF Master File PIN Personal Identification Number PPS Protocol and Parameter Selection SIM Subscriber Identity Module USIM Universal Subscriber Identity Module 4 General requirements The UICC shall be either a removable hardware module or a non-removable separate hardware module embedded in the ME. The USIM on a UICC shall contain an identity which unambiguously identifies a subscriber. For access to 3G services, a UICC containing a valid USIM shall be present at all times, other than for emergency calls. The specifications shall support the security requirements as defined in 3GPP TS 33.102 [7]. The USIM shall provide storage for subscription and subscriber related information. The UICC/USIM may also contain applications which use the features defined in the USIM Application Toolkit specification 3GPP TS 31.111 [6]. 5 Security requirements The USIM shall be used to provide security features. If the UICC is removed from the 3G terminal, the service shall be terminated immediately. The functions of the USIM include authenticating itself to the network and vice versa, authenticating the user and providing additional security functions as defined in 3GPP TS 33.102 [7]. The USIM shall be unambiguously identified. Means shall be provided to prevent fraudulent use of stolen UICCs. It shall not be possible to access data intended for USIM internal use, e.g. authentication keys. ETSI ETSI TS 121 111 V18.0.0 (2024-05) 9 3GPP TS 21.111 version 18.0.0 Release 18 Further details of the following requirements are given in 3GPP TS 33.102 [7]. 5.1 File access conditions Actions, such as READ, UPDATE on UICC data shall be controlled by access conditions. These shall be satisfied prior to the action being performed. Since a UICC may contain multiple (3G and non-3G) applications, a flexible method of controlling file access shall be provided. 5.2 User authentication The USIM shall support means to authenticate the user, to provide, for example, protection against the use of stolen cards. For the USIM, authentication shall be performed by the verification of a numeric PIN of four (4) to eight (8) decimal digits. A function to disable user authentication may exist which may be inhibited by the application provider, in which case the user shall always use the PIN. Otherwise, the user may decide whether or not to make use of the user authentication function. If disabled, the user authentication function remains disabled until the user specifically re-enables it. Following correct PIN presentation, the ME may perform functions and actions on USIM data, which are protected by the relevant access condition. If an incorrect PIN is entered, an indication shall be given to the user. After three (3) consecutive incorrect entries the relevant PIN is blocked, i.e. functions and actions on data protected by the access condition shall no longer be possible, even if between attempts the UICC has been removed, the USIM has been deselected or the ME has been switched off. Once a PIN is blocked, further PIN verifications shall be denied. The USIM shall support a mechanism for unblocking a blocked PIN. Unblocking of a PIN is performed by using the relevant PIN Unblocking Key. PINs, but not Unblock PINs, shall be changeable by the user following correct entry of either the current PIN or Unblock PIN. The Unblock PIN shall consist of eight (8) decimal digits and shall not be changeable by the user. If an incorrect Unblock PIN is presented, an indication shall be given to the user. After ten (10) consecutive incorrect entries, the Unblock PIN shall be blocked, even if between attempts the UICC has been removed, the USIM has been deselected or the ME has been switched off. Unblocking of a blocked PIN shall not be possible. It shall not be possible to read PINs or Unblock PINs. 5.3 User data stored in ME Subject to the exception below, all user related information transferred into the ME during network operations shall be deleted from the ME after removal of the UICC, deselection of the USIM, deactivation of the ME, or following an electrical reset of the UICC. This includes any data that was transferred to the ME by USIM Application Toolkit commands. User related security codes such as PIN and Unblock PIN may only be stored by the ME during the procedures involving such a code and shall be discarded by the ME immediately after completion of the procedure. Optionally, an ME may retain some less security-sensitive data at UICC removal, USIM deselection or ME switch-off. Such data are e.g. SMS, ADN/SSC, FDN/SSC, LND. These data, when stored in the ME, shall only be readable/retrievable if the same USIM is reactivated (as determined by the IMSI). If the IMSI is retained in the ME for this purpose, it shall be stored securely and shall not be able to be read out. 5.4 Authentication A means shall be specified to mutually authenticate the USIM and the network by showing knowledge of a secret key K which is shared between and available only to the USIM and in the user's Home Environment. The method is composed ETSI ETSI TS 121 111 V18.0.0 (2024-05) 10 3GPP TS 21.111 version 18.0.0 Release 18 of a challenge/response and key establishment protocol combined with a sequence number-based one-pass protocol for network authentication. 5.5 Data integrity of signalling elements Some signalling information elements are considered sensitive and must be integrity protected. An integrity function shall be applied on certain signalling information elements transmitted between the ME and the network. The 3GPP Integrity Algorithm (UIA) is used with an Integrity Key (IK) to compute a message authentication code for a given message. The setting of IK is triggered by the authentication procedure. IK shall be stored on the USIM. 5.6 User identity confidentiality A mechanism shall be specified to provide user identity confidentiality by means of a temporary identity. 5.7 Length of security parameters In order to allow for enhancements of the security level in 3G, the following requirements shall be covered: - all security-related parameters for 3G shall be accompanied by a length indicator; - the USIM shall support variable-length security parameters. If the USIM supports the GSM security mechanisms in addition to 3G security, fixed length security parameters according to 3GPP TS 51.011 [8] shall be supported in addition. 6 Logical issues 6.1 Application selection In a multiapplication environment, a flexible application selection method is required. The application identifier defined in ETSI TS 101 220 [5] should be used for application selection. Direct application selection, including selection by partial DF name and the EFDIR concept of ISO/IEC 7816-4 [12] shall be followed. In particular, a mechanism for the ME and the UICC shall be specified in order to allow the user, when the ME is in idle mode, to select and activate one application amongst those which are available and supported by the ME (this will permit the user to choose, for instance, between 2 different USIM applications). At switch on, the last active USIM shall be automatically selected. The last active USIM shall be stored on the UICC. By default if there is no last active USIM defined in the UICC, the user shall be able to select the active USIM amongst those available on the UICC. 6.2 Simultaneous access A mechanism shall be specified for simultaneous access to several files or applications. 7 Service Requirements 7.1 Void 7.2 Data transfer A mechanism allowing highly secure transfer of applications and/or associated data to/from the UICC/USIM shall be specified in line with the requirements in 3GPP TS 22.101 [2]. This requires a secure transfer mechanism. ETSI ETSI TS 121 111 V18.0.0 (2024-05) 11 3GPP TS 21.111 version 18.0.0 Release 18 7.3 Application execution environment An application execution environment may exist on the UICC/USIM which includes functionality defined in 3GPP TS 31.111 [6]. 7.4 Profile exchange A mechanism for the ME, the USIM and the network to exchange service capabilities shall be specified. The following exchange of service capabilities may occur: - ME services capabilities may be provided to the USIM/UICC; - USIM/UICC services capabilities may be provided to the ME (and thus potentially to the network); - network services capabilities may be provided to the USIM/UICC via the ME. 7.5 Version identification A means for identification of the version of the USIM shall be provided. 8 Physical Characteristics The physical characteristics shall be in accordance with the specifications in 3GPP TS 31.101 [3]. 8.1 Void 8.2 Void 9 Electrical characteristics and transmission protocols Electronic signals and transmission protocols shall be in accordance with the specifications in 3GPP TS 31.101 [3]. The electrical specifications shall at least cover the 1.8V and 3V voltage ranges as specified in 3GPP TS 31.101 [3]. Lower voltages may be added in the future. 3G terminals and beyond shall not support 5V on the ME-UICC interface. Both ME and UICC shall support operational class indication as defined in ISO/IEC 7816-3 [11]. UICC shall support at least two consecutive voltage classes unless it has a non removable form factor. ME shall support at least two consecutive voltage classes, unless it contains a non-removable UICC or unless it supports any of the following, or a combination of: NB-IoT, GERAN EC-GSM-IoT, Category M1 of E-UTRAN enhanced-MTC and Category 1bis as specified in 3GPP TS 36.306 [14]. An ME supporting NG-RAN and containing a removable UICC shall support at least the 1.8V voltage class, and may support a second, consecutive voltage class. Both UICC and ME shall support PPS as defined in ISO/IEC 7816-3 [11] with at least the values defined in 3GPP TS 31.101 [3]. The ME shall have the capabilities of initiating a warm reset as defined in ISO/IEC 7816-3 [11]. The UICC shall support warm reset as defined in ISO/IEC 7816-3 [11]. NOTE2: The warm reset is used during a session when there is a need to restart the USIM due to internal modifications of data caused by user actions or network data downloading. The UICC may indicate in the ATR to the warm reset that the specific mode is entered automatically, using the parameters that were used prior to the warm reset. In case of a cold reset, the UICC shall enter the negotiable mode. ETSI ETSI TS 121 111 V18.0.0 (2024-05) 12 3GPP TS 21.111 version 18.0.0 Release 18 In addition to the T=0 protocol which is mandatory for the UICC and the ME, the T=1 protocol shall be mandatory for the ME. It is optional for the UICC. The speed enhancement as specified in 3GPP TS 31.101 [3] shall be supported by both the ME and the UICC. 9.1 Void 10 Contents of the Elementary Files 10.1 USIM information storage requirements The USIM shall contain information elements for 3G network operations. The USIM may contain information elements related to the subscriber, 3G services and home environment or service provider related information. The UICC shall provide storage capability for the following: - UICC related information: - IC card identification: a number uniquely identifying the UICC and the card issuer; - Preferred language(s); - Directory of applications. - USIM related information: - Administrative information: indicates mode of operation of the USIM, e.g. normal, type approval; - USIM service table: indicates which optional services are provided by the USIM; - IMSI; - Language indication; - Location information; - Cipher key (Kc) and cipher key sequence number; - Access control class(es); - Forbidden PLMNs; - Ciphering Key for GPRS; - GPRS location information; - Cell Broadcast related information; - Emergency call codes; - Phone numbers (ADN, FDN, SDN); - Short messages and related parameters; - Capability and Configuration parameters; - Higher Priority PLMN search period; - list of carrier frequencies to be used for cell selection. - Information accessible to the USIM and other applications: - ADN. In addition, the USIM shall manage and provide storage for the following information in accordance with the security requirements of clause 5: - PIN; - PIN enabled/disabled indicator; - PIN error counter; - Unblock PIN; - Unblock PIN error counter; - Data integrity keys; - Subscriber authentication keys. ETSI ETSI TS 121 111 V18.0.0 (2024-05) 13 3GPP TS 21.111 version 18.0.0 Release 18 10.2 Phone Book A Phone Book entry consists of a record in an ADN file and, optionally, additional records which are placed in different EFs. In the latter case, a mechanism shall be defined to link all records in the same Phone Book entry. These features shall be supported by the ME while their support by the UICC is optional. 10.2.1 Support of two name fields per entry The support of two name fields per entry shall be specified to allow, for example, for two different representations of the same name (for example, in Japanese characters and in Latin characters). 10.2.2 Support of multiple phone numbers per entry The support of multiple phone numbers per entry shall be specified, for example, office, home, fax, mobile or pager. In addition to that, information for identifying those attributes are needed. 10.2.3 Support of email address The support of email addresses linked to Phone Book entries shall be specified. In addition to that, information for identifying these addresses is needed. 10.2.4 Support of user definable groupings The specification shall support the grouping of Phone Book entries into groups defined by the user, for example, business and private. 10.2.5 Support of hidden entries The specification shall support means of marking Phone Book entries as "hidden". 10.2.6 Number of entries The specification shall support storage of at least 500 entries. 10.2.7 Void 10.3 Storage of call details The specification shall support provision of storage for call detail information. The call detail information consists of the following attributes: - mobile terminated calls: calling party number, date and time, calling party's name and status of call (i.e. answered or missed), duration; - mobile originated calls: called party number, date and time, called party's name and duration; - accumulated duration of preceding calls, separately for mobile originated and mobile terminated calls. Call detail attributes are optional. A value to mark them as "undefined" shall be available. NOTE 1: The calling/called party's name may be available from the Phone Book. ETSI ETSI TS 121 111 V18.0.0 (2024-05) 14 3GPP TS 21.111 version 18.0.0 Release 18 10.4 Void 11 3G/GSM interworking 11.1 Void 11.2 3G subscribers in a GSM network 3GPP TS 22.101 [2] requires that UMTS shall provide some mechanisms which permit UMTS subscribers to roam easily onto pre-UMTS systems and access the services. Thus, the specification shall allow the UICC to be used with a dual mode (GSM/ 3G) ME and a GSM ME for the provision of GSM service. 12.1 General The Contact Manager provides an interface for the management of contact information including rich content without any structural limitations. There shall be a mechanism for the ME to detect that the UICC containing the Contact Manager has changed. This mechanism may be used by the ME to ask the user whether synchronization of data between the ME and the UICC Contact Manager should occur. This clause defines the functional requirements of the Contact Manager. An ME and a 3GPP application supporting the Contact Manager shall comply with all these requirements. 12.2 Security requirements The Contact Manager may contain personal information. It shall be possible to restrict the access to this information to authorized users or entities (e.g. by binding the access to the verification of the USIM PIN). 12.4.3 Interworking with the 3G Phone Book In case both the ME and the 3GPP application support both the 3G Phone Book (i.e. as defined in clause 10.2 of the present document) and the Contact Manager the Contact Manager shall be used. There shall be a mechanism for the 3GPP application to indicate the support of the Contact Manager. 12.4.4 Content description 12.4.4.1 Number of contacts The Contact Manager specification shall not unreasonably restrict the number of contacts. 12.4.4.2 Contact structure The Contact Manager shall consist of contacts, which are made up of various fields (e.g. phone number, name, photo). A filtering mechanism according to OMA DS Field Filtering shall be supported. It shall be possible to have several instances of a field in a contact when appropriate (e.g. a contact may have two fax numbers). ETSI ETSI TS 121 111 V18.0.0 (2024-05) 15 3GPP TS 21.111 version 18.0.0 Release 18 An extensible coding scheme shall be defined which allows to describe a contact including all its fields. An existing scheme (e.g. "vcard") shall be used, if appropriate. A minimum set of field types recognised by the 3GPP application and the ME shall be defined (e.g. name, phone number, URL, Email address, address, sound, pictures, notes). It shall be possible to store and associate multimedia information (stored on the 3GPP application) with a contact (e.g. photo, logo, video, ring tone, voice tag). It shall be possible to associate an icon or a label to each contact field type (e.g. associate an icon representing a phone to the number field. "Home address" could be configured as the label of the "mailing address" field type). It shall be possible to configure the structure and the display order of the contact fields (e.g. first name then Instant Messaging address then number, etc) depending on ME capabilities. 12.4.4.3 Group management It shall be possible to define new groups (e.g. My Tennis Club). It shall be possible to pre-define groups (e.g. Friend, Work, Family and VIP). It shall be possible to store and associate multimedia information (stored on the 3GPP application) with a group (e.g. photo, logo, video, ring tone, icon). It shall be possible to bind contacts to one or several groups. 12.4.4.4 User Action Management It shall be possible to configure a list of possible actions that could be proposed to the user when the contact is selected (e.g. Launch Browser, Send SMS, Send MMS, Instant messaging, Make a voice over IP call, Make a video call, Make a conference call, Game player, Send Email). 12.4.5 Interface capabilities description An external and an internal interface to the Contact Manager shall be defined. The external interface between the Contact Manager and a UICC external entity, i.e. the ME, shall rely on a transport protocol layer that is independent of the physical interface (i.e. the ISO interface and the new high-speed interface). This is to allow the definition of one solution that can use either the existing ISO interface or the new high-speed interface. The external interface definition shall also ease interfacing the PC applications with the Contact Manager. Both the ME and the UICC shall be capable of initiating contact information synchronization based on a configurable policy.The internal interface allows other UICC resident applications to access the Contact Manager e.g. through a dedicated API. This enables the creation of additional services utilizing the Contact Manager data and properties. There shall be a mechanism for the user to allow or prevent remote access to the Contact Manager. The external and internal interface shall provide means to: - identify Contact Manager capabilities - perform the following operations on a contact or a group: create, retrieve, modify, delete, search In addition the internal interface shall provide mechanisms to: - register/deregister an UICC resident application to the Contact Manager. - allow a resident UICC application to access Contact Manager data and properties based on user permission. - allow the Contact Manager to notify events to registered UICC application and to pass event related information when applicable. Events notifying the applications shall include: - contact information is modified locally - contact information is modified remotely ETSI ETSI TS 121 111 V18.0.0 (2024-05) 16 3GPP TS 21.111 version 18.0.0 Release 18 - change of contact manager configuration 12.4.6 Efficient browsing and searching The Contact Manager interfaces should allow efficient searching and browsing of the contacts (i.e. the user experience browsing the Contact Manager should be acceptable). 12.4.7 Associated services 12.4.7.1 Memory management It shall be possible to determine the number of stored contacts and the amount of the available and used Contact Manager memory. ETSI ETSI TS 121 111 V18.0.0 (2024-05) 17 3GPP TS 21.111 version 18.0.0 Release 18 Annex A (informative): Change history The table below indicates all change requests that have been incorporated into the present document since it was initially approved by 3GPP TSG T and subsequently 3GPP TSG CT. Date TSG # TSG Doc. CR Rev Cat Subject/Comment New 1999-06 TP-03 TP-99085 Draft specification first approved at TSG-T #3 3.0.0 1999-12 TP-06 TP-99255 001 D References to new specifications and editorial changes 3.0.1 2000-04 TP-07 TP-000017 002 F Location of the UIA (3GPP integrity algorithm) aligned with 33.102 3.1.0 2000-07 TP-08 TP-000097 003 F Clarification of USIM application selection 3.2.0 TP-000097 004 F Alignment with 33.102: removal of Enhanced User Identity Confidentiality (EUIC) from R99 2000-10 TP-09 TP-000150 005 F Partial AID selection requirements 3.3.0 2001-03 TP-11 - - Issued as version 4.0.0 in order to create a complete set of specifications for release 4. The contents of version 4.0.0 are identical to the contents of version 3.3.0 4.0.0 2002-06 TP-16 - - Issued as version 5.0.0 in order to create a complete set of specifications for release 5. The contents of version 5.0.0 are identical to the contents of version 4.0.0 5.0.0 2002-09 TP-17 TP-020208 009 A Clarification on the use of the USIM and the SIM 5.1.0 2004-03 TP-23 TP-040023 010 C Update with respect to the third form factor and removal of an unused reference 6.0.0 2004-06 TP-24 TP-040100 011 D Release 6 alignment 6.1.0 2005-06 CT-28 CP-050136 015 A ISO/IEC 7816-Series Revision 6.2.0 2006-05 CT-32 CP-060349 0017 1 F Review of TS 21.111, USIM and IC Card Requirements 6.3.0 2006-09 CT-33 action item - - MCC to raise spec to Rel-7 7.0.0 2007-03 CT-35 CP-070070 0019 2 B Requirements for the Enhanced USIM phonebook 8.0.0 2007-10 Editorial correction to cover page 8.0.1 2007-12 CT-38 CP-070839 0020 2 B Completion of the requirements for the Enhanced USIM phonebook Renaming of the feature to Contact Manager. Contact Manager moved to a dedicated clause 8.1.0 2008-05 CT-40 CP-080384 0023 2 F Update and correct references and pointers to references 8.2.0 2009-12 CT-46 CP-091042 0025 2 F References update 8.3.0 2009-12 CT-46 - - - - Upgrade of the specification to Rel-9 9.0.0 2011-03 SP-51 - - - - Upgrade of the specification to Rel-10 10.0.0 2012-09 SP-57 - - - - Upgrade of the specification to Rel-11 11.0.0 2012-10 - - - - Remove hidden text 11.0.1 2014-10 SP-65 - - - - Upgrade of the specification to Rel-12 12.0.0 2015-12 Upgrade to Rel-13 13.0.0 2016-12 CT-74 CP-160789 0027 1 B Usage of non-removable UICC 14.0.0 2017-09 CT-77 CP-172064 0028 2 C Support for two voltage classes 14.1.0 2018-03 CT-79 CP-180130 0029 1 B Mandating only single voltage class support for MEs supporting NG-RAN. 15.0.0 2018-06 CT-80 CP-181158 0030 - F Correction on implementation of CR0029 15.1.0 2018-07 Correction to logo, version and date on cover page 15.1.1 2020-07 - - - - - Update to Rel-16 version (MCC) 16.0.0 2020-12 CT#903 CP-203085 A Allowing single voltage class for MEs supporting Category 1bis 16.1.0 2021-09 CT#93e CP-212091 0034 2 C Clarification of supply voltage support for NG-RAN ME 17.0.0 2024-03 - - - - - Update to Rel-18 version (MCC) 18.0.0 ETSI ETSI TS 121 111 V18.0.0 (2024-05) 18 3GPP TS 21.111 version 18.0.0 Release 18 History Document history V18.0.0 May 2024 Publication
|
64b7ea50a4f88719ff3cd3842fb0bc6e
|
119 441
|
1 Scope
|
The present document, based on the general policy requirements specified in ETSI EN 319 401 [2], specifies policy and security requirements for signature validation services operated by a TSP. NOTE 1: Beside signature validation, other signature services, like signature creation, signature augmentation or signature preservation can also be offered by TSPs. Such services can be provided as stand-alone services or combined (e.g. augmentation can be used to support a preservation service). The present document does not provide requirements on signature services beyond validation and does not provide requirements on how to combine signature related services. NOTE 2: A distinct Technical Specification (TS) provides policy and security requirements for TSP offering signature augmentation services as a stand-alone service or in complement to one of the above-mentioned services. The present document is aimed at trust services supporting the validation of digital signatures in accordance with ETSI EN 319 102-1 [3]. It takes into account the relevant requirements for signature validation application specified in ETSI TS 119 101 [1] as they relate to TSPs. It is aimed at supporting the validation of digital signatures in European and other regulatory frameworks. NOTE 3: Specifically, but not exclusively, the present document is aimed at qualified and non-qualified trust services, supporting the validation of digital signatures in accordance with the requirements of the Regulation (EU) No 910/2014 [i.1] for validation of electronic signatures and electronic seals (both advanced and qualified). Annex B complements the requirements for signature validation service providers offering a Qualified Validation Service for qualified electronic signatures or for qualified electronic seals as specified by Regulation (EU) No 910/2014 [i.1]. NOTE 4: Specifically, but not exclusively, digital signatures in the present document cover electronic signatures, advanced electronic signatures, qualified electronic signatures, electronic seals, advanced electronic seals, and qualified electronic seals as per Regulation (EU) No 910/2014 [i.1]. The present document may be used by competent bodies as the basis for confirming that an organization is trustworthy in validating digital signatures on behalf of other persons or on its own behalf. NOTE 5: See ETSI EN 319 403 [i.13] for guidance on assessment of TSP processes and services. The user's interface is outside the scope of the main TSP service. However, the present document provides in annex D recommendations for the user's interfaces (for inputting the request and to visualize the validation report). The TSP has connections with external (trust) services that can be contacted for provisioning validation information, or to relay the validation request. The present document does not put requirements on the trust service policies applied by such external services. The present document identifies specific controls needed to address specific risks associated with validation services.
|
64b7ea50a4f88719ff3cd3842fb0bc6e
|
119 441
|
2 References
| |
64b7ea50a4f88719ff3cd3842fb0bc6e
|
119 441
|
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 referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https://docbox.etsi.org/Reference/. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. ETSI ETSI TS 119 441 V1.2.1 (2023-10) 8 The following referenced documents are necessary for the application of the present document. [1] ETSI TS 119 101: "Electronic Signatures and Infrastructures (ESI); Policy and security requirements for applications for signature creation and signature validation". [2] ETSI EN 319 401: "Electronic Signatures and Infrastructures (ESI); General Policy Requirements for Trust Service Providers". [3] ETSI EN 319 102-1 (V1.3.1): "Electronic Signatures and Infrastructures (ESI); Procedures for Creation and Validation of AdES Digital Signatures; Part 1: Creation and Validation". [4] ISO/IEC 15408 parts 1 to 3: "Information technology -- Security techniques -- Evaluation criteria for IT security". [5] ISO/IEC 19790: "Information technology -- Security techniques -- Security requirements for cryptographic modules". [6] FIPS PUB 140-2: "Security Requirements for Cryptographic Modules".
|
64b7ea50a4f88719ff3cd3842fb0bc6e
|
119 441
|
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 referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. [i.2] ETSI TR 119 001: "Electronic Signatures and Infrastructures (ESI); The framework for standardization of signatures; Definitions and abbreviations". [i.3] ETSI TS 119 102-2: "Electronic Signatures and Infrastructures (ESI); Procedures for Creation and Validation of AdES Digital Signatures; Part 2: Signature Validation Report". [i.4] ETSI EN 319 122-1: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 1: Building blocks and CAdES baseline signatures". [i.5] ETSI EN 319 122-2: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 2: Extended CAdES signatures". [i.6] ETSI EN 319 132-1: "Electronic Signatures and Infrastructures (ESI); XAdES digital signatures; Part 1: Building blocks and XAdES baseline signatures". [i.7] ETSI EN 319 132-2: "Electronic Signatures and Infrastructures (ESI); XAdES digital signatures; Part 2: Extended XAdES signatures". [i.8] ETSI EN 319 142-1: "Electronic Signatures and Infrastructures (ESI); PAdES digital signatures; Part 1: Building blocks and PAdES baseline signatures". [i.9] ETSI EN 319 142-2: "Electronic Signatures and Infrastructures (ESI); PAdES digital signatures; Part 2: Additional PAdES signatures profiles". [i.10] ETSI TS 119 172-1: "Electronic Signatures and Infrastructures (ESI); Signature Policies; Part 1: Building blocks and table of contents for human readable signature policy documents". [i.11] ETSI TS 119 172-4: "Electronic Signatures and Infrastructures (ESI); Signature Policies; Part 4: Signature applicability rules (validation policy) for European qualified electronic signatures/seals using trusted lists". ETSI ETSI TS 119 441 V1.2.1 (2023-10) 9 [i.12] ETSI TS 119 442: "Electronic Signatures and Infrastructures (ESI); Protocol profiles for trust service providers providing AdES digital signature validation services". [i.13] ETSI EN 319 403: "Electronic Signatures and Infrastructures (ESI); Trust Service Provider Conformity Assessment; Requirements for conformity assessment bodies assessing Trust Service Providers". [i.14] ETSI TS 119 312: "Electronic Signatures and Infrastructures (ESI); Cryptographic Suites". [i.15] Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation). [i.16] ETSI EN 319 411-1: "Electronic Signatures and Infrastructures (ESI); Policy and security requirements for Trust Service Providers issuing certificates; Part 1: General requirements". [i.17] ETSI EN 319 411-2: "Electronic Signatures and Infrastructures (ESI); Policy and security requirements for Trust Service Providers issuing certificates; Part 2: Requirements for trust service providers issuing EU qualified certificates". [i.18] ETSI EN 319 412-4: "Electronic Signatures and Infrastructures (ESI); Certificate Profiles; Part 4: Certificate profile for web site certificates". [i.19] ETSI TS 119 172-2: "Electronic Signatures and Infrastructures (ESI); Signature Policies; Part 2: XML format for signature policies". [i.20] ETSI TS 119 172-3: "Electronic Signatures and Infrastructures (ESI); Signature Policies; Part 3: ASN.1 format for signature policies". [i.21] IETF RFC 3647: "Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework". 3 Definition of terms, symbols, abbreviations and notations
|
64b7ea50a4f88719ff3cd3842fb0bc6e
|
119 441
|
3.1 Terms
|
For the purposes of the present document, the terms given in ETSI EN 319 401 [2], ETSI TR 119 001 [i.2] and the following apply: applicability checking: determination whether a signature conform to signature applicability rules NOTE 1: The applicability checking is a broader concept than validation as covered by the present document: it is out of scope of the present document. NOTE 2: The applicability checking can be provided as an adjunct to the signature validation service defined in the present document. (signature) commitment type: signer-accepted indication of the exact implication of a digital signature (signature) creation constraint: criteria used when creating a digital signature driving application: application that uses a signature creation system to create a signature or a signature validation application in order to validate digital signatures or a signature augmentation application to augment digital signatures NOTE: In a signature validation process, the Driving Application (DA) provides AdES digital signature and other input to a Signature Validation Application (SVA). qualified validation service for qualified electronic seals: As specified in Regulation (EU) No 910/2014 [i.1], Article 40. ETSI ETSI TS 119 441 V1.2.1 (2023-10) 10 qualified validation service for qualified electronic signatures: As specified in Regulation (EU) No 910/2014 [i.1], Article 33. qualified validation service provider: SVSP that provides qualified validation service for qualified electronic seals or qualified validation service for qualified electronic signatures signature acceptance: technical verification to be performed on the signature itself or on the attributes of the signature (i.e. the "signature elements constraints") NOTE: The signature acceptance is a technical process defined and specified in ETSI EN 319 102-1 [3] and performed by a signature validation application (it is thus one part of the signature validation process). This signature validation application can be managed by a SVSP or can be a stand-alone application on the relying party environment. signature applicability rules: set of rules, applicable to one or more digital signatures, that defines the requirements for determination of whether a signature is fit for a particular business or legal purpose NOTE 1: Signature applicability rules can be implicit, or can be stated in a human readable document and/or in a machine processable from. ETSI TS 119 172-1 [i.10] can be used for this purpose. NOTE 2: Rules in general can be any elements used by a user to decide whether a signature is fit for purpose (e.g. requirements on the time of signing, on the signer identity, on qualified signatures and statements, on use the validation report, etc.). NOTE 3: Applicability rules can include for example: ο§ one or more signature validation policies containing validation constraints to be checked by the signature validation application; ο§ signature validation constraints or rules to be checked in addition to the checks carried out by the signature validation application. NOTE 4: The owner of the signature applicability rules is usually the relying party and these rules can be shared by a community. Signature applicability rules can be handled by an extension to the service provided by the SVSP that would offer applicability checking and this is out of scope of the present document. signature class: set of signatures achieving a given functionality EXAMPLE: Signature with time, signature with long term validation material, Signature providing Long Term Availability and Integrity of Validation Material are possible signature classes. signature creation device: configured software or hardware used to implement the signature creation data and to create a digital signature value signature validation: process of verifying and confirming that a digital signature is technically valid signature validation application: application that validates a signature against a signature validation policy, and that outputs a status indication (i.e. the signature validation status) and a signature validation report NOTE: The Signature Validation Application (SVA) is specified in ETSI EN 319 102-1 [3]. signature validation client: component or piece of software that implements the signature validation protocol on the user's side signature validation constraint: technical criteria against which a digital signature can be validated, e.g. as specified in ETSI EN 319 102-1 [3] EXAMPLE: Criteria can be expressed as an abstract formulation of rule, value, parameter, range and computation result. NOTE: Validation constraints can be defined in a formal signature validation policy, can be given in configuration parameter files or implied by the behaviour of the signature validation application. ETSI ETSI TS 119 441 V1.2.1 (2023-10) 11 signature validation policy: set of signature validation constraints processed or to be processed by the SVA NOTE 1: A signature validation policy is a purely technical concept. It is one of the inputs of a validation process (other inputs include the signed data and the signature) that determine the validation result (PASSED, FAILED or INDETERMINED). NOTE 2: A signature validation policy can be imposed by signature applicability rules. signature validation presentation: optional element in the signature validation process that can be used by a verifier to check the results of a validation process signature validation report: comprehensive report of the validation provided by the signature validation application to the DA and allowing the driving application and any party beyond the driving application, to inspect details of the decisions made during validation and investigate the detailed causes for the status indication provided by the signature validation application EXAMPLE: Clause 5.1.3 of ETSI EN 319 102-1 [3] specifies minimum requirements for the content of such a report and ETSI TS 119 102-2 [i.3] specifies such a report. Signature Validation Service (SVS) policy: set of rules that indicates the applicability of a signature validation service to a particular community and/or class of application with common security requirements NOTE: A SVS policy is applicable to a service; it is a specific sub-class of trust service policy as defined in ETSI EN 319 401 [2]. It relates to the quality and applicability of the service. Signature Validation Service (SVS) practice statement: statement of the practices and procedures used to address all the requirements identified for the provision of the signature validation service NOTE: A signature validation service practice statement is a trust service practice statement that is part of the SVSP's documentation (see ETSI EN 319 401 [2]). Signature Validation Service (SVS) server: component that implements the signature validation protocol and processes the signature validation on the SVSP's side signature validation status: one of the following indications: TOTAL-PASSED, TOTAL-FAILED or INDETERMINATE signature verification: process of checking the cryptographic value of a signature using signature verification data signer: entity being the creator of a digital signature user: application or human being interacting with an application on top of a signature validation client validation: process of verifying and confirming that a certificate or a digital signature is valid validation data: data that is used to validate a digital signature validation of qualified electronic seals: As specified in Regulation (EU) No 910/2014 [i.1], Article 40. validation of qualified electronic signature: As specified in Regulation (EU) No 910/2014 [i.1], Article 32. validation service: system accessible via a communication network, which validates a digital signature verifier: entity that wants to validate or verify a digital signature
|
64b7ea50a4f88719ff3cd3842fb0bc6e
|
119 441
|
3.2 Symbols
|
Void. ETSI ETSI TS 119 441 V1.2.1 (2023-10) 12
|
64b7ea50a4f88719ff3cd3842fb0bc6e
|
119 441
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in ETSI EN 319 401 [2], ETSI TR 119 001 [i.2] and the following apply: DA Driving Application OVR OVeRall PoE Proof of Existence QES Qualified Electronic Signature or Qualified Electronic Seal (Q)SCD (Qualified) Signature Creation Device QSVSP Qualified Signature Validation Service Provider SD Signer's Document SDO Signed Data Object SDR Signed Document Representation SVA Signature Validation Application SVP Signature Validation Protocol SVR Signature Validation Report SVS Signature Validation Service SVSP Signature Validation Service Provider SVSServ Signature Validation Service Server TSA Time Stamping Authority TSP Trust Service Provider VPR signature Validation PRocess
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.