hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.5 Data Preserved Workflow Endpoint | |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.5.1 Description | This endpoint covers the Service Provider notifying the Issuing Authority that data has been preserved according to an EPOC-PR. |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.5.2 Message contents | The contents of the Request shall be as per table 6.5.2-1 below. Table 6.5.2-1: HI-1 Objects for the Data Preserved Workflow Endpoint Verb HI-1 Object Cardinality Description Reference CREATE NotificationObject 1 Indicates that the state of the LPTaskObject status has changed to reflect the preservation of data. Clause... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.5.3 NotificationObject | The Request shall contain a CREATE Request for a NotificationObject that indicates that the data has been preserved. The fields in table 6.5.3-1 shall be present in the NotificationObject. Table 6.5.3-1: NotificationObject fields in the Data Preserved Workflow Endpoint Field Description M/C/O Reference NotificationDeta... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.6 Correspondence Endpoint | |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.6.1 Description | This endpoint is used by the Service Provider to exchange free-text correspondence with the Issuing Authority or Enforcing Authority, together with associated documentation, for one of the following purposes: • To request additional information from the relevant Authority. • To provide additional information to the rel... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.6.2 Message contents | The contents of the Request shall be as per table 6.6.2-1 below. Table 6.6.2-1: HI-1 Objects for the Correspondence Workflow Endpoint Verb HI-1 Object Cardinality Description Reference DELIVER DocumentObject 1 Document containing the correspondence. Clause 6.6.3 |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.6.3 DocumentObject | The Request shall contain at least one DELIVER Request for a DocumentObject that represents the correspondence, which shall contain the fields given in table 6.6.3-1. Table 6.6.3-1: DocumentObject fields in the Correspondence Workflow Endpoint Field Description M/C/O Reference CountryCode Shall be set to the appropriat... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.7 Confirm Withdrawal Workflow Endpoint | |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.7.1 Description | This endpoint covers the Service Provider confirming that an EPOC has been withdrawn by the Issuing Authority (see clause 5.6). |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.7.2 Message contents | The contents of the Request shall be as per table 6.7.2-1 below. ETSI ETSI TS 104 144 V1.3.1 (2026-03) 46 Table 6.7.2-1: HI-1 Objects for the Confirm Withdrawal Workflow Endpoint Verb HI-1 Object Cardinality Description Reference CREATE NotificationObject 1 Indicates that the state of the LDTaskObject status has change... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.7.3 NotificationObject | The Request shall contain a CREATE Request for a NotificationObject that indicates that the state of the Authorisation has changed to reflect the de-facto impossibility. The fields given in table 6.7.3-1 shall be present in the NotificationObject. Table 6.7.3-1: NotificationObject fields in the Confirm Withdrawal Workf... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.8 Enforcing Authority Identifier Endpoint | |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.8.1 Description | This endpoint allows a Service Provider to retrieve the identifier of the Enforcing Authority it is associated with. The Service Provider gets the identifier of the Issuing Authority when it receives a message from it, since all of the messages between Service Providers and Issuing Authorities are initiated by the Issu... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.8.2 Message contents | The Header section of this HI-1 message is different than for all the other WISP Workflow Endpoints and shall be populated as per table 6.8.2-1 below. Table 6.8.2-1: HI-1 Message Header Field Description M/C/O Reference SenderIdentifier Shall be set to a value which identifies the Service Provider, and which shall be a... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.9 Authorities Query Endpoint | |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.9.1 Description | This endpoint allows a Service Provider to retrieve the list of Authorities registered in the e-Evidence DIS. The endpoint supports the LIST operation to list the metadata about existing authorities, and the GET operation on a single authority identifier to retrieve all the information about the specified authority. |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.9.2 AuthorityObject | This object describes an Authority as registered in the Court Database (CDB) of the DIS. An Authority is a DIS actor that can assume the role of an Issuing Authority, a Validating Authority, an Enforcing Authority or any other type of Authorities. Table 6.9.2-1: AuthorityObject fields Field Description M/C/O Reference ... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 6.9.3 Message contents | The Header section of this HI-1 message is the same as for the Enforcing Authority Identifier Endpoint and different than for all the other WISP Workflow Endpoint. It shall be populated as per table 6.8.2-1. The endpoint supports: • LIST Action: The payload of the message shall be a LIST Request (see ETSI TS 103 120 [1... |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 7 Transport and security | |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 7.1 Transport | Transport shall be HTTP as per ETSI TS 103 120 [1], clause 9.3 and shall use HTTPS as per ETSI TS 103 120 [1], clause 9.3.4. See also clause 7.2 of the present document. Messages shall be encoded using XML according to ETSI TS 103 120 [1], clause 9.2.1. JSON encoding shall not be used. |
2c5adb759be990a10178f42b16bfb2d5 | 104 144 | 7.2 Security | ETSI TS 103 120 [1], clause 9.3.4 shall be followed. ETSI ETSI TS 104 144 V1.3.1 (2026-03) 49 Annex A (normative): Object Model A.1 Object Model ETSI TS 103 120 [1] defines a set of HI-1 Objects. Each of these Objects contains information about a specific part of a given workflow. ETSI TS 103 120 [1], clauses 7, 8 and ... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 1 Scope | The present document provides requirements that are specific enough to define the desired security outcomes, but flexible enough that there can be innovation and different ways for how they can be achieved. Whilst it is initially targeted towards the Telecoms Sector, the principles are designed to be industry agnostic.... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 2 References | |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 3 Definition of terms, symbols and abbreviations | |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 3.1 Terms | For the purposes of the present document, the following terms apply: internet: network of multiple, connected networks NOTE: Internetworking is the practice of connecting a computer network with other networks through the use of gateways that provide a common method of routing information packets between the networks. ... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 3.2 Symbols | Void. |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: APN Access Point Name CDS Cross Domain Solution CRL Certificate Revocation List DNS Domain Name Server DoH DNS over HTTPS DoQ DNS over QUIC DoT DNS over TLS EDR Endpoint Detection and Response Software GUI Graphical User Interface IPSec Intern... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 4 Concepts | |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 4.1 Introduction | The following concepts provide a reference to the architecture that is acceptable for a PAW system. So, "Let's dive in!". It is essential that a PAW follows the concept of 'browse down' [i.4], where a high-trust system administers a system of equal or lower trust. This means the PAW controls shall only be managed from ... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 4.1.1 Browse Down Architecture | Browse down is where the physical device has a high level of trust and administrative access into a management system and can be managed appropriately within the high trust area. To access lower-trust systems, the device would be required to cross trust boundaries which can be protected to prevent exploitation of the d... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 4.1.2 Browse Up Antipattern | The antipattern browse up is where a low-trust device is used for privileged access into a high trust environment. This could be via any means, such as VPN, Jump Box, etc. Crucially browse up means a connection is initiated from low-trust into a high-trust environment. Standard corporate devices are not suitable for pe... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 4.2 Secure Communications | To ensure the integrity, confidentiality, and authenticity of communications, all connectivity involving a PAW device shall employ strong security controls. This should include the use of authenticated, encrypted, and non-repudiable protocols for all communications that leave the PAW device. Understanding the type of c... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 5 Connectivity | |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 5.1 Minimize connectivity to external networks | In most use cases, a PAW requires connectivity to external networks or internet services. But its access to external services shall be restricted to the services that are essential for it to operate. This may include receiving updates or configurations from an MDM or carrying out administrative tasks on a cloud portal.... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 5.2 Connectivity technology | To reduce the attack surface, make sure the connectivity methods the PAW uses, such as Wi-Fi® or cellular, are adequately secured. Public Wi-Fi networks can present a major risk to a PAW device, as they often require use of a captive portal, where the local device connects directly to the local service to authenticate.... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 5.3 Securely connect to administration targets | |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 5.3.1 Introduction | A PAW needs to communicate with the systems and devices it manages and for many use cases, this could mean multiple systems or devices. Some may be less trusted or more vulnerable than others, which presents a threat to the PAW and any other system it is used to access. ETSI ETSI TS 103 994-2 V1.1.1 (2025-07) 12 Depend... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 5.3.2 Remote connectivity | Many use cases for PAWs involve connecting to a system over a network, either locally or remotely. It is important that communications from the PAW are protected from any threats on that network: • Secure protocols, such as TLS or IPSec, should be used to authenticate the systems or networks which are being connected. ... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 5.3.3 Direct connectivity | Some use cases may require direct physical connectivity to the administrated device, such as over serial or Ethernet links. When using direct physical connectivity to a system or asset, the controls on the PAW device are the only layer of security between the PAW device and the asset being managed. It is important to u... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 5.3.4 Isolated devices and systems | In many cases, a PAW which is used to manage standalone or isolated equipment is also used to manage or connect to other systems and networks. Where this is the case, the PAW device acts as a bridge between the systems and networks, even if the connections are not active at the same time. Even if a network is temporari... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 5.3.5 Less trusted systems | A system or device managed by a PAW could be considered less trusted for several reasons, for example: • it processes high-risk data; • it is one of many systems which need segregating from one another; • a third party has privileged access to it. ETSI ETSI TS 103 994-2 V1.1.1 (2025-07) 13 If one of these systems is co... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 6 Third Parties and PAWs | |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 6.1 Definitions | A third party is characterized as an individual or entity external to an organisation. This typically implies there is no direct control over the employees working on behalf of the contracting organisation. It is crucial to establish contractual agreements with any third-party company to ensure compliance with legal an... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 6.2 Apply equivalent controls to third parties | If a third party is compromised, it offers an access route to all the organisations to which they provide services. This is why third-party access is viewed as a significant risk and should be managed appropriately. To ensure that the PAW solution is an effective defence, any third party that requires access to the con... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 6.3 Third party acting as a Managed Service Provider | Engaging a third party to design, construct, and/or upkeep the privileged system poses a substantial threat to a business's operational security. The business's security is intrinsically linked to the third party's security, given their need for significant privileged access. If a PAW system is to be developed and cons... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 7 Specification | Section Specification Browse down All privileged access shall use a high trust device. High trust devices shall limit external connectivity and applications to only those required. Browse up Low trust devices shall not be used for privileged administration. Remote access services should use conditional access where app... |
55a2b1d7665a995538ef4d737dc827e7 | 103 994-2 | 8 Threats and Mitigations | There is significant risk over the communication channels between a PAW device, and its corresponding network(s), given the privileged access the device is protecting. If the device itself is well-protected, then an attacker may refocus attention towards the communications between the device and any external networks. ... |
0ba56d8f147f37fc93166bf0696e3b1b | 104 018-1 | 1 Scope | The present document provides the Protocol Implementation Conformance Statement (PICS) pro forma for the conformance test specifications for Vulnerable Road Users (VRU) Awareness Basic Service as defined in ETSI TS 103 300-3 [1] in compliance with the relevant requirements and in accordance with the relevant guidance g... |
0ba56d8f147f37fc93166bf0696e3b1b | 104 018-1 | 2 References | |
0ba56d8f147f37fc93166bf0696e3b1b | 104 018-1 | 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 a... |
0ba56d8f147f37fc93166bf0696e3b1b | 104 018-1 | 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 i... |
0ba56d8f147f37fc93166bf0696e3b1b | 104 018-1 | 3 Definition of terms, symbols and abbreviations | |
0ba56d8f147f37fc93166bf0696e3b1b | 104 018-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 300-3 [1], ISO/IEC 9646-1 [i.1] and ISO/IEC 9646-7 [i.2] apply. |
0ba56d8f147f37fc93166bf0696e3b1b | 104 018-1 | 3.2 Symbols | Void. |
0ba56d8f147f37fc93166bf0696e3b1b | 104 018-1 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 103 300-3 [1] and the following apply: CAN Controller Area Network DE Data Element ITS Intelligent Transportation Systems IUT Implementation Under Test PICS Protocol Implementation Conformance Statement SUT System Under Test VAM VRU Awareness ... |
0ba56d8f147f37fc93166bf0696e3b1b | 104 018-1 | 4 Conformance requirement concerning PICS | If it claims to conform to the present document, the actual PICS pro forma to be filled in by a supplier shall be technically equivalent to the text of the PICS pro forma given in annex A, and shall preserve the numbering, naming and ordering of the pro forma items. A PICS which conforms to the present document shall b... |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 1 Scope | The present document defines network functions which are necessary to support services and facilities provided by PLMNs. A summary of the network functions is given in Table 1, where also an indication is given whether the network must support the function. The table also indicates whether or not a function requires in... |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 1.1 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 1.2 Abbreviations | Abbreviations used in the present document are listed in GSM 01.04. |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2 Network functions for basic service provision | |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.1 Call handling | This set of functions enables the establishment of communications between a mobile subscriber and another network subscriber in one of the following types of network PSTN, ISDN, PSPDN, CSPDN and other PLMNs. |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.1.1 Call from a mobile subscriber registered in VLR | This is the normal case where the call is routed according to the dialled number. After the call, the MSC will send the charging information to the HLR, a billing entity and/or store the charging data on tapes or discs as described in Technical Specification GSM 12.05. |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.1.2 Call from a mobile subscriber not registered in VLR | When the VLR receives a request for call set-up parameters from an MSC for an MS originating call, where the MS is not registered in the VLR, the VLR shall initiate a location updating procedure towards the HLR and in response parameters are given concerning category, services and restrictions. The call is then set up ... |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.1.3 Call to a mobile subscriber | The call is routed (re-routed or forwarded) according to location data obtained from the HLR to the actual MSC and the MS is paged over the standardised radio interface. For MSs in mode of operation A and B the paging may be performed via SGSN. This optional network function is further described in the Technical Specif... |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.1.4 Call handling functions in HLR | The HLR should also support control functions for handling of supplementary services as described for each service in the GSM 03.8x series of Technical Specifications. The HLR should provide information to the gateway MSC to allow it to route calls directed to a mobile subscriber: either a Mobile Station Roaming Number... |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.1.5 Call handling functions in VLR | The VLR must provide subscriber parameters to the MSC as required for call handling. The VLR must also support control functions for handling of supplementary services as described for each service in the GSM 03.8x series of Technical Specifications. For a MS in mode of operation A or B, the VLR may optionally support ... |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.1.6 Call handling functions in MSC | The MSC must perform normal call routing and call control functions. The MSC will obtain subscriber parameters from its associated VLR. The MSC must also be capable of performing handover as defined in section 3.2. In some cases, the MSC must be able to act as a gateway MSC to provide an interface to other circuit-swit... |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.1.7 Call handling functions in SGSN | For a MS in mode of operation A or B, the SGSN may optionally support establishment and maintenance of an association with a VLR. This allows paging for a circuit switched call to be performed via SGSN. |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.2 Subscriber identity authentication | The purpose of subscriber identity authentication is defined in Technical Specification GSM 02.09. The authentication mechanism is defined in Technical Specification GSM 03.20 and corresponding procedures on the MS-BSS interface are defined in Technical Specification GSM 04.08. |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.3 Emergency call | |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.3.1 General | The land mobile system should be capable of efficient handling of emergency calls fromMS. The signalling procedures on the radio path for emergency calls are given in Technical Specification GSM 04.08. |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.3.2 Routeing | The call should be routed automatically to an appropriate emergency centre based on the geographical location of the MS(e.g. based on the identity of the cell on which the call is established). |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.4 Supplementary services | PLMN may offer supplementary services as shown in Technical Specification GSM 02.04. The support of supplementary services will require control procedures in HLRs, VLRs and MSCs in addition to the control procedure in the fixed network. The technical realisation of supplementary services is given in the GSM 03.8x serie... |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.5 Voice group services | The PLMN may offer the voice group services. These are the voice group call service (VGCS) and voice broadcast service (VBS), as shown in GSM 02.68 and GSM 02.69, respectively. The support of the voice group call and voice broadcast services will require control procedures in HLRs, VLRs, MSCs and Group Call Register (G... |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.6 Short Message Service | This set of functions allows the transfer of short messages i either direction between a mobile station and a short message service centre. More detailed information is given in Technical Specification GSM 03.40. |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.6.1 Short Message Handling functions in the HLR | The HLR should be able to provide information to allow a short message to be routed from the SMS gateway MSC to the visited MSC and/or visited SGSN and then to the required MS. |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.6.2 Short Message Handling Functions in the VLR | The VLR should provide subscriber parameters to the MSC as required for handling short messages. |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.6.3 Short Message Handling Functions in the MSC | The MSC should perform the functions of relaying short messages in both directions between the fixed network of the PLMN and the BSS. In some cases the MSC should be able to act as an SMS Gateway MSC to relay short messages from a Short Message Service Centre (SC) to a PLMN, or an SMS Interworking MSC to relay short me... |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.6.4 Short Message Handling Functions in the SGSN | The SGSN should perform the functions of relaying short messages in both directions between the fixed network of the PLMN and the BSS. The SGSN should also provide subscriber parameters required for handling the short messages relaying function. The SGSN should also download (from HLR or another SGSN) and store subscri... |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.7 Signalling information element confidentiality | A procedure should be implemented providing for the confidentiality of signalling information elements on the radio path. In Technical Specification GSM 02.09 the signalling information elements which need to be protected are given. The Encryption Key is calculated in both the MS and the network. Detailed information i... |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.8 Packet Handling | This set of functions enables routing of packets between an MS and a network host in one of the following types of network: PSPDN, networks based on the Internet Protocol (IP) and other PLMNs. |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.8.1 Packet handling functions in SGSN | The SGSN should perform the functions of routing packets in both directions between one or more GGSN’s and the BSS. The SGSN should also download (from HLR or another SGSN) and store subscriber parameters required for handling the packet routing functions. ETSI ETSI TS 100 521 V7.0.0 (1999-09) 12 (GSM 03.01 version 7.0... |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.8.2 Packet handling functions in GGSN | The GGSN should act as a gateway that provides interface(s) to other packet data networks. The GGSN should further perform the functions of routing packets in both directions between these networks and one or more SGSN’s. The GGSN should also download (from SGSN) and store subscriber parameters required for handling th... |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 2.8.3 Packet switched service functions in HLR | The HLR should provide permanent storage of subscriber data. The HLR should provide the identity of the visited SGSN to the SMS gateway MSC to allow it to route short messages directed to a mobile subscriber; further detail is given in Technical Specification GSM 03.40. |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 3 Network functions for supporting cellular operation | |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 3.1 Location registration | |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 3.1.1 Definitions | Location registration means that the PLMNs keep track of where MSs are located in the system area. The location information is stored in functional units called location registers. Functionally there are four types of location registers: - the home location register (HLR) where the current location and all subscriber p... |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 3.1.2 Procedures | Procedures related to location registration are specified in Technical Specification GSM 03.12. They comprise: i) location updating which enables the MS to inform the network that its location area has to be updated, i.e. the MS has received a location area identity which is different from that contained in its memory.... |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 3.1.3 Information stored in location registers | Information to be stored in location registers is listed in Technical Specification GSM 03.08. |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 3.2 Handover | |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 3.2.1 Definitions | The following case are required: i) handover between physical channels of the same Base Station System (BSS). This capability could be used in the following situations: - when the physical channel carrying the call is subject to interference or other disturbances; - when a physical channel or channel equipment carrying... |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 3.2.2 Procedures | The procedures are described in Technical Specification GSM 03.09. |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 3.3 Call re-establishment | Re-establishment of a call may be performed when a traffic channel (TCH) has been lost during the call, e.g. when a handover could not be completed in time. Call re-establishment is only performed on TCHs and when the call is in the connected state (see Technical Specification GSM 04.08). The procedures are specified i... |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 4 Additional network functions for call handling | |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 4.1 Queuing | As a PLMN option MS originating and/or MS terminating calls may be queued at the BSS. (NOTE: this queuing is additional to that for normal call handling). However, the following condition must be met: - for MS terminating calls the queuing must not conflict with abnormal release conditions in the fixed network. In gene... |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 4.2 Off-Air-Call-Set-Up (OACSU) | |
3e324ca7bd9a22c18382e613feac7446 | 100 521 | 4.2.1 General | OACSU may be implemented in PLMNs in order to increase the call handling capacity of the PLMN. OACSU may be implemented in PLMNs on an optional basis subject to the following conditions: i) OACSU should not be used for calls to an international number; ii) OACSU should not be used for incoming international calls, exce... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.